Packman horribly slow from US, 16.0KiB/s - that's 1/2 of 33.6 baud modem dial-up speed....
Devs, Not sure if packman is just out of bandwidth or what the issue is, but TW updates take forever, e.g. Retrieving: librist4-0.2.7-1699.1.pm.25.x86_64.rpm ....................................<86%>=======[| (16.0 KiB/s)] That is 1/2 of what a 33.6 dial-up modem will do over an old land-line. (it used to take Friday - Sunday to download SUSE over a modem - and pray a disconnect didn't occur :) Are there any additional resources that may help this situation? I think it is pulling from gwdg.de, but even then the pipe should be bigger than 16.0 KiB/s. Ideas? -- David C. Rankin, J.D.,P.E.
On 2024-08-28 17:43, David C. Rankin wrote:
Devs,
Not sure if packman is just out of bandwidth or what the issue is, but TW updates take forever, e.g.
Retrieving: librist4-0.2.7-1699.1.pm.25.x86_64.rpm ....................................<86%>=======[| (16.0 KiB/s)]
That is 1/2 of what a 33.6 dial-up modem will do over an old land-line. (it used to take Friday - Sunday to download SUSE over a modem - and pray a disconnect didn't occur :)
Are there any additional resources that may help this situation? I think it is pulling from gwdg.de, but even then the pipe should be bigger than 16.0 KiB/s.
Ideas?
At my end, (Montreal Canada) all the mirror sources suddenly decided to take the day off. frank@desktop-tumbleweed:~> sudo zypper dup Retrieving repository 'Double Commander (openSUSE_Tumbleweed)' metadata ...............................[error] Repository 'Double Commander (openSUSE_Tumbleweed)' is invalid. [home_Alexx2000|https://mirrorcache-us-east.opensuse.org/repositories/home:/Alexx2000/openSU...] Valid metadata not found at specified URL History: - [|] Error trying to read from 'https://mirrorcache-us-east.opensuse.org/repositories/home:/Alexx2000/openSU...' Please check if the URIs defined for this repository are pointing to a valid repository. Warning: Skipping repository 'Double Commander (openSUSE_Tumbleweed)' because of the above error. Retrieving repository 'Packman Repository' metadata ....................................................[done] Building repository 'Packman Repository' cache .........................................................[done] Retrieving repository 'lxde' metadata .................................................................[error] Repository 'lxde' is invalid. [lxde|https://mirrorcache-us-east.opensuse.org/repositories/X11:/lxde/openSUSE_Tum...] Valid metadata not found at specified URL History: - [|] Error trying to read from 'https://mirrorcache-us-east.opensuse.org/repositories/X11:/lxde/openSUSE_Tum...' Please check if the URIs defined for this repository are pointing to a valid repository. Warning: Skipping repository 'lxde' because of the above error. ^C Trying to exit gracefully... frank@desktop-tumbleweed:~> That is just a sample of what zypper is getting...it goes on to eventually cover all the repositories I have in my system...some download, other error out. The whole process takes 15 or 20 minutes when a normal zypper dup takes 5 minutes total.
On 8/28/24 5:22 PM, Frank McCormick wrote:
On 2024-08-28 17:43, David C. Rankin wrote:
Devs,
Not sure if packman is just out of bandwidth or what the issue is, but TW updates take forever, e.g.
Retrieving: librist4-0.2.7-1699.1.pm.25.x86_64.rpm ....................................<86%>=======[| (16.0 KiB/s)]
That is 1/2 of what a 33.6 dial-up modem will do over an old land-line. (it used to take Friday - Sunday to download SUSE over a modem - and pray a disconnect didn't occur :)
Are there any additional resources that may help this situation? I think it is pulling from gwdg.de, but even then the pipe should be bigger than 16.0 KiB/s.
Ideas?
At my end, (Montreal Canada) all the mirror sources suddenly decided to take the day off.
Yes, Something is FUBAR. Concrete example. I just updated yesterday before the dbus/wicked hiccup, and the update of TW today, about 24 hours later took 1:19 minutes just to download the packages: 16:22 wizard:~/dev/python/python3> sudo zypper dup Loading repository data... Reading installed packages... ... <snip> ... You may wish to restart these processes. See 'man zypper' for information about the meaning of values in the above table. No core libraries or services have been updated since the last system boot. Reboot is probably not necessary. 17:41 wizard:~/dev/python/python3> From 4:22 pm until 5:41 pm -- that's nuts. -- David C. Rankin, J.D.,P.E.
participants (2)
-
David C. Rankin -
Frank McCormick