It happens that a "zypper dup" ends with a stalling download. Right now I have this Retrieving: Mesa-gallium-23.3.6-1699.369.pm. 1.x86_64.rpm ..............<51%>==============[- (2.4 KiB/s)] And if I do nothing but come back in 50 years time it will still be exactly the same. I tried "zypper ref", "zypper clean --all" nothing seems to work. The one thing that does is to go into Yast-Software and lock the package and then come back to do zypper before Yast again to unlock it (until the next time). It seems like THIS 'whaaaaatever' happens invariably with the packman repo and very ofgtyen with Mesa-xyz. Anyone know exactly WHAT the cause is, I can't even TRY countermeasures without knowing what it is. TIA
* bent fender <slowroller@trixtar.org> [03-15-24 08:49]:
It happens that a "zypper dup" ends with a stalling download. Right now I have this
Retrieving: Mesa-gallium-23.3.6-1699.369.pm. 1.x86_64.rpm ..............<51%>==============[- (2.4 KiB/s)]
And if I do nothing but come back in 50 years time it will still be exactly the same. I tried "zypper ref", "zypper clean --all" nothing seems to work. The one thing that does is to go into Yast-Software and lock the package and then come back to do zypper before Yast again to unlock it (until the next time).
It seems like THIS 'whaaaaatever' happens invariably with the packman repo and very ofgtyen with Mesa-xyz. Anyone know exactly WHAT the cause is, I can't even TRY countermeasures without knowing what it is.
have seen slow and occasionally failed downloads. to counter I now *always* download, then install. guessing you have a mirror for packman that is faulty zypper -v ref ; zypper -v dup -d -l && zypper -v dup -l -y -- (paka)Patrick Shanahan Plainfield, Indiana, USA @ptilopteri http://en.opensuse.org openSUSE Community Member facebook/ptilopteri Photos: http://wahoo.no-ip.org/piwigo paka @ IRCnet oftc
Fri, 15 Mar 2024 13:21:37 -0400 Patrick Shanahan <paka@opensuse.org> :
* bent fender <slowroller@trixtar.org> [03-15-24 08:49]:
It happens that a "zypper dup" ends with a stalling download. Right now I have this
Retrieving: Mesa-gallium-23.3.6-1699.369.pm. 1.x86_64.rpm ..............<51%>==============[- (2.4 KiB/s)]
And if I do nothing but come back in 50 years time it will still be exactly the same. I tried "zypper ref", "zypper clean --all" nothing seems to work. The one thing that does is to go into Yast-Software and lock the package and then come back to do zypper before Yast again to unlock it (until the next time).
It seems like THIS 'whaaaaatever' happens invariably with the packman repo and very ofgtyen with Mesa-xyz. Anyone know exactly WHAT the cause is, I can't even TRY countermeasures without knowing what it is.
have seen slow and occasionally failed downloads. to counter I now *always* download, then install.
guessing you have a mirror for packman that is faulty
zypper -v ref ; zypper -v dup -d -l && zypper -v dup -l -y
It got the same Mesa-gallium to hang at the same 51%. And again when I broke in with Cntrl-C it said "trying to exit cleanly" but it never did, it even blocked shutdown so I had to do it the hard way. THEN I had to flag the package "protected" in Yast, come back and finish the update and go unprotect the package in Yast. Exactly the same as always when this happens. Retrieving: Mesa-gallium-23.3.6-1699.369.pm. 1.x86_64 (packman) (745/772), 12.0 MiB Retrieving: Mesa-gallium-23.3.6-1699.369.pm. 1.x86_64.rpm ...........................<51%>===========================[/ (260.8 KiB/s)] After I unprotect it in Yast and opt to make the repo-switcharoo to packman Mesa-gallium is the ONLY remaining package to swing and if I then let Yast go for it Yast will hang with the file download.
* bent fender <slowroller@trixtar.org> [03-15-24 18:00]:
Fri, 15 Mar 2024 13:21:37 -0400 Patrick Shanahan <paka@opensuse.org> :
* bent fender <slowroller@trixtar.org> [03-15-24 08:49]:
It happens that a "zypper dup" ends with a stalling download. Right now I have this
Retrieving: Mesa-gallium-23.3.6-1699.369.pm. 1.x86_64.rpm ..............<51%>==============[- (2.4 KiB/s)]
And if I do nothing but come back in 50 years time it will still be exactly the same. I tried "zypper ref", "zypper clean --all" nothing seems to work. The one thing that does is to go into Yast-Software and lock the package and then come back to do zypper before Yast again to unlock it (until the next time).
It seems like THIS 'whaaaaatever' happens invariably with the packman repo and very ofgtyen with Mesa-xyz. Anyone know exactly WHAT the cause is, I can't even TRY countermeasures without knowing what it is.
have seen slow and occasionally failed downloads. to counter I now *always* download, then install.
guessing you have a mirror for packman that is faulty
zypper -v ref ; zypper -v dup -d -l && zypper -v dup -l -y
It got the same Mesa-gallium to hang at the same 51%. And again when I broke in with Cntrl-C it said "trying to exit cleanly" but it never did, it even blocked shutdown so I had to do it the hard way. THEN I had to flag the package "protected" in Yast, come back and finish the update and go unprotect the package in Yast. Exactly the same as always when this happens.
zypper al Mesa-gallium and later zypper rl Mesa-gallium would probably have been much easier and faster
Retrieving: Mesa-gallium-23.3.6-1699.369.pm. 1.x86_64 (packman) (745/772), 12.0 MiB Retrieving: Mesa-gallium-23.3.6-1699.369.pm. 1.x86_64.rpm ...........................<51%>===========================[/ (260.8 KiB/s)]
After I unprotect it in Yast and opt to make the repo-switcharoo to packman Mesa-gallium is the ONLY remaining package to swing and if I then let Yast go for it Yast will hang with the file download.
you should try another mirror or two for packman. I have: cat /etc/zypp/repos.d/Tumbleweed.packman.repo [Tumbleweed.packman] name=Tumbleweed.packman enabled=1 autorefresh=0 baseurl=http://ftp.gwdg.de/pub/linux/misc/packman/suse/openSUSE_Tumbleweed/ http://ftp.halifax.rwth-aachen.de/packman/suse/openSUSE_Tumbleweed/ type=rpm-md priority=70 gpgcheck=1 gpgkey=http://ftp.gwdg.de/pub/linux/misc/packman/suse/openSUSE_Tumbleweed/repodata/... http://ftp.halifax.rwth-aachen.de/packman/suse/openSUSE_Tumbleweed/repodata/... keeppackages=0 and there are more available -- (paka)Patrick Shanahan Plainfield, Indiana, USA @ptilopteri http://en.opensuse.org openSUSE Community Member facebook/ptilopteri Photos: http://wahoo.no-ip.org/piwigo paka @ IRCnet oftc
* Patrick Shanahan <paka@opensuse.org> [03-15-24 18:08]:
* bent fender <slowroller@trixtar.org> [03-15-24 18:00]:
Fri, 15 Mar 2024 13:21:37 -0400 Patrick Shanahan <paka@opensuse.org> :
* bent fender <slowroller@trixtar.org> [03-15-24 08:49]:
It happens that a "zypper dup" ends with a stalling download. Right now I have this
Retrieving: Mesa-gallium-23.3.6-1699.369.pm. 1.x86_64.rpm ..............<51%>==============[- (2.4 KiB/s)]
...
It got the same Mesa-gallium to hang at the same 51%. And again when I broke in with Cntrl-C it said "trying to exit cleanly" but it never did, it even blocked shutdown so I had to do it the hard way. THEN I had to flag the package "protected" in Yast, come back and finish the update and go unprotect the package in Yast. Exactly the same as always when this happens.
zypper al Mesa-gallium and later zypper rl Mesa-gallium
would probably have been much easier and faster
Retrieving: Mesa-gallium-23.3.6-1699.369.pm. 1.x86_64 (packman) (745/772), 12.0 MiB Retrieving: Mesa-gallium-23.3.6-1699.369.pm. 1.x86_64.rpm ...........................<51%>===========================[/ (260.8 KiB/s)]
After I unprotect it in Yast and opt to make the repo-switcharoo to packman Mesa-gallium is the ONLY remaining package to swing and if I then let Yast go for it Yast will hang with the file download.
you should try another mirror or two for packman. I have:
cat /etc/zypp/repos.d/Tumbleweed.packman.repo
[Tumbleweed.packman] name=Tumbleweed.packman enabled=1 autorefresh=0 baseurl=http://ftp.gwdg.de/pub/linux/misc/packman/suse/openSUSE_Tumbleweed/ http://ftp.halifax.rwth-aachen.de/packman/suse/openSUSE_Tumbleweed/ type=rpm-md priority=70 gpgcheck=1 gpgkey=http://ftp.gwdg.de/pub/linux/misc/packman/suse/openSUSE_Tumbleweed/repodata/... http://ftp.halifax.rwth-aachen.de/packman/suse/openSUSE_Tumbleweed/repodata/... keeppackages=0
and there are more available
another "workaround" would be to fetch subject file manually and install locally or by adding to a locally created repo (I do this). -- (paka)Patrick Shanahan Plainfield, Indiana, USA @ptilopteri http://en.opensuse.org openSUSE Community Member facebook/ptilopteri Photos: http://wahoo.no-ip.org/piwigo paka @ IRCnet oftc
Fri, 15 Mar 2024 18:28:24 -0400 Patrick Shanahan <paka@opensuse.org> :
another "workaround" would be to fetch subject file manually and install locally or by adding to a locally created repo (I do this).
I have a plain-rm-files local directory mostly for packages that are not part of the offering. OFF-TOPIC, all this discussion is making me re-evaluate my policy and I think I have come up with one that will fly. I will do a fresh install of Distro-X, immediately copy to another partition as well, both bootable/usable. Tweak one of them until everything I want works and back it up before continuing to use it WITHOUT EVER UPDATING while in use. A month later update the other copy that was never used, tweak it and then roll it into the current operational slot while the previous operational system takes a rest for a month, and so on. This would not be very different from what I'm doing now, having one or more backup images of each all the time, but it would mean a more defensive handling policy.
participants (2)
-
bent fender -
Patrick Shanahan