I just wanted to confirm that the 300-500KiB I was getting in download was
normal or if I had missed something on the wiki page. Even if slow, the
archive is invaluable for circumstances just like this, and I can understand
why limiting the download may help create a balance for the use of the arc
On 5/13/22 8:15 AM, Mikau via arch-general wrote:
>> The rollback worked flawlessly, but is there anything that can be
>> done to help the download rate? Due to the ICU 7.0->7.1 update, there
>> were 368 packages in 1.3GiB to download. At 300->500KiB it took
>> forever.
>
> Have you tried using
On 5/13/22 3:24 AM, mpan via arch-general wrote:
>> The rollback worked flawlessly, but is there anything that can be done to
>> help the download rate? Due to the ICU 7.0->7.1 update, there were 368
>> packages in 1.3GiB to download. At 300->500KiB it took forever.
> Did you use ArchLinux Arc
> The rollback worked flawlessly, but is there anything that can be
> done to help the download rate? Due to the ICU 7.0->7.1 update, there
> were 368 packages in 1.3GiB to download. At 300->500KiB it took
> forever.
Have you tried using the mirrors
(https://{europe,asia,america}.archive.pkgbuil
The rollback worked flawlessly, but is there anything that can be done to
help the download rate? Due to the ICU 7.0->7.1 update, there were 368
packages in 1.3GiB to download. At 300->500KiB it took forever.
Did you use ArchLinux Archive? It’s meant for solving crisis
situations, not for ev
Arch folks,
Had the need to do a first rollback to 3/15/22 for a samba bug report on
4.16 failure to discover [homes]
(https://bugzilla.samba.org/show_bug.cgi?id=15062).
The rollback worked flawlessly, but is there anything that can be done to
help the download rate? Due to the ICU 7.0->7.1 u
