Large zipper dup stalling at ghc packages

6500 item update is stalling at ghc packages. See below.
Alternatives to me seem to be wait another day, or remove ghc items then reinstall later. Simply ignoring the ghc items does not let install of other items proceed.

In cache ghc-time-1.14-1.2.x86_64.rpm                                                                                                    (635/6582), 300.3 KiB    
In cache ghc-th-compat-0.1.7-1.2.x86_64.rpm                                                                                              (636/6582),  19.7 KiB    
In cache ghc-tagged-0.8.10-2.2.x86_64.rpm                                                                                                (637/6582),  40.5 KiB    
In cache ghc-primitive-0.9.1.0-2.2.x86_64.rpm                                                                                            (638/6582), 137.6 KiB    
In cache ghc-exceptions-0.10.12-1.2.x86_64.rpm                                                                                           (639/6582),  74.7 KiB    
Retrieving: ghc-containers-0.7-1.2.x86_64 (repo-oss)                                                                                     (640/6582), 636.2 KiB    
Retrieving: ghc-containers-0.7-1.2.x86_64.rpm .........................................................................................................[not found]
Retrieving: ghc-containers-0.7-1.2.x86_64.rpm .........................................................................................................[not found]
Retrieving: ghc-containers-0.7-1.2.x86_64.rpm .........................................................................................................[not found]
Retrieving: ghc-containers-0.7-1.2.x86_64.rpm .........................................................................................................[not found]
Retrieving: ghc-containers-0.7-1.2.x86_64.rpm ...............................................................................................[error (200.5 KiB/s)]
Failed to provide Package ghc-containers-0.7-1.2.x86_64 (repo-oss). Do you want to retry retrieval?

[openSUSE:repo-oss|http://cdn.opensuse.org/tumbleweed/repo/oss] Can't provide file './x86_64/ghc-containers-0.7-1.2.x86_64.rpm' from repository 'openSUSE:repo-oss'
History:
 - Downloaded data exceeded the expected filesize '636.2 KiB' of 'http://cdn.opensuse.org/tumbleweed/repo/oss/x86_64/ghc-containers-0.7-1.2.x86_64.rpm'.
 - Can't provide ./x86_64/ghc-containers-0.7-1.2.x86_64.rpm
Abort, retry, ignore? [a/r/i] (a): n
: Invalid answer 'n'.
[a/r/i] (a): a
Problem occurred during or after installation or removal of packages:
Installation has been aborted as directed.
Please see the above error message for a hint.
tom@mydesktop: ~ $ 

thanks, tom kosvic

Do you use ghc?

I have, in the past, used ghc to compile some software that required it. I think it was an astronomy package. Not in current use

tom kosvic

If it’s not needed, can always remove?

As already mentioned in your former thread from two month ago…here some steps how to do basic system housekeeping:

right, removal was one alternative but perhaps log jam might clear in a day or so.

tom kosvic

This is weird. I uninstalled all the ghc files (apptox 200) using zypper but zypper dup keeps looking for them.

I re-ran the zypper dup update again and it still wanted to install the same ghc files and got hung at the same place. I did a zypper ref to see if that might clear the situation but it did not.

I did a reboot. I ran sudo zypper dup again and the ghc files were trying to be installed for the update but they had been previously removed.

I did a zypper clean hoping that would remove the ghc inputs but it did not.

I don’t know what is triggering the ghc installs.

tom kozvic

There will be some that requires it… zypper al ghc-* and see what happens.

om@mydesktop: ~ $ sudo zypper al ghc-*
Specified lock has been successfully added.
tom@mydesktop: ~ $ 

@malcolmlewis , the lock out ghc files worked. Retrieving of 6300 files completed. There were an additional 200 ghc files in the original dup.

Installation is proceedig. Will take a couple of hours.

I wonder why just deleting the ghc files was not enough to take them out of play?

thanks, tom kosvic

Now try zypper -vvv dup, likely show some additional packages that need ghc packages…

Will run, zypper -vvv dup, but will be a long wait for zypper to finish the dup task.

tom kosvic

@tckosvic If nothing showed up when you ran the zypper dup then no need to run again.

I suspect that whatever you used in the past just needed the compiler and not anything ghc- related.

Nothing to do as a result of of dup. But I still don’t know what is trying to get ghc files installed.

If the ghc file are “Available” but locked it looks like they will install on nexr dup if I unlock them.

thanks, tom kosvic

tom@mydesktop: ~ $ sudo zypper dup
Refreshing service 'NVIDIA'.
Refreshing service 'openSUSE'.
Loading repository data...
Reading installed packages...
Warning: You are about to do a distribution upgrade with all enabled repositories. Make sure these repositories are compatible before you continue. See 'man zypper' for more information about this command.
Computing distribution upgrade...

The following 1914 items are locked and will not be changed by any action:
 Available:
  akonadi ghc-adjunctions ghc-adjunctions-devel ghc-adjunctions-doc ghc-adjunctions-prof ghc-aeson ghc-aeson-devel ghc-aeson-doc ghc-aeson-pretty ghc-aeson-pretty-devel ghc-aeson-pretty-doc
  ghc-aeson-pretty-prof ghc-aeson-prof ghc-alsa-core ghc-alsa-core-devel ghc-alsa-core-doc ghc-alsa-core-prof ghc-alsa-mixer ghc-alsa-mixer-devel ghc-alsa-mixer-doc ghc-alsa-mixer-prof
  ghc-ansi-terminal ghc-ansi-terminal-devel ghc-ansi-terminal-doc ghc-ansi-terminal-prof ghc-ansi-terminal-types ghc-ansi-terminal-types-devel ghc-ansi-terminal-types-doc
  ghc-ansi-terminal-types-prof ghc-appar ghc-appar-devel ghc-appar-doc ghc-appar-prof ghc-array ghc-array-devel ghc-array-doc ghc-array-prof ghc-asciidoc ghc-asciidoc-devel ghc-asciidoc-doc
  ghc-asciidoc-prof ghc-asn1-encoding ghc-asn1-encoding-devel ghc-asn1-encoding-doc ghc-asn1-encoding-prof ghc-asn1-parse ghc-asn1-parse-devel ghc-asn1-parse-doc ghc-asn1-parse-prof
  ghc-asn1-types ghc-asn1-types-devel ghc-asn1-types-doc ghc-asn1-types-prof ghc-assoc ghc-assoc-devel ghc-assoc-doc ghc-assoc-prof ghc-async ghc-async-devel ghc-async-doc ghc-async-prof
  ghc-atomic-counter ghc-atomic-counter-devel ghc-atomic-counter-doc ghc-atomic-counter-prof ghc-attoparsec ghc-attoparsec-aeson ghc-attoparsec-aeson-devel ghc-attoparsec-aeson-doc
  ghc-attoparsec-aeson-prof ghc-attoparsec-devel ghc-attoparsec-doc ghc-attoparsec-prof ghc-authenticate-oauth ghc-authenticate-oauth-devel ghc-authenticate-oauth-doc
  ghc-authenticate-oauth-prof ghc-auto-update ghc-auto-update-devel ghc-auto-update-doc ghc-auto-update-prof ghc-aws ghc-aws-devel ghc-aws-doc ghc-aws-prof ghc-base ghc-base16
  ghc-base16-bytestring ghc-base16-bytestring-devel ghc-base16-bytestring-doc ghc-base16-bytestring-prof ghc-base16-devel ghc-base16-doc ghc-base16-prof ghc-base64 ghc-base64-bytestring
  ghc-base64-bytestring-devel ghc-base64-bytestring-doc ghc-base64-bytestring-prof ghc-base64-devel ... and 1810 more items.
 Installed:
  terminfo terminfo-base terminfo-iterm terminfo-screen
 Run 'zypper locks -s' to see the complete list of locked items.
Nothing to do.
tom@mydesktop: ~ $ 

That’s just showing the locked packages, nothing to worry about… I remove and lock all the -lang files here, so I have 3300 plus items locked :wink:

I purged (removed ) all the lang files a week or so ago.

I also tried to uninstall all the 32bit files but that removed “steam” that I’d like to keep. So I have steam with a couple of hundred 32bit files.

thanks for help. tom kosvic

Thanks all. I had a similar error as OP when updating and using zypper al ghc-* allowed me to proceed.

Ok, we have found two people at least, who use or did use ghc compiler.

It is a side issue but really the main root issue, but how would we report ghc downloading problem in the right direction? Is this a bug or just a repo issue that will eventually get solved with time?

Sorry. if you think this should be a separate thread.

thanks, tom kosvic

Remove the locks zypper rl ghc-* and run a zypper -vvv dup again, does it try to install them again? If so, you need to work out which installed package(s) are requring one or more of the ghc-* packages…

I got a “nothing to do”. I guess I can conclude that there is nothing installed that need ghc* files.
I won’t install it again until needed for some other compile.

I will give this a solved.

thanks, tom kosvic

tom@mydesktop: ~ $ sudo zypper rl ghc-*
1 lock has been successfully removed.
tom@mydesktop: ~ $ szd
Refreshing service 'NVIDIA'.
Refreshing service 'openSUSE'.
Loading repository data...
Reading installed packages...
Warning: You are about to do a distribution upgrade with all enabled repositories. Make sure these repositories are compatible before you continue. See 'man zypper' for more information about this command.
Computing distribution upgrade...

The following 7 items are locked and will not be changed by any action:
 Available:
  akonadi pattern:kde_pim vlc-beta
 Installed:
  terminfo terminfo-base terminfo-iterm terminfo-screen
Nothing to do.
tom@mydesktop: