On Sat, 2020-01-11 at 03:02 +0000, Filipe Laíns via arch-general wrote:
> On Sat, 2020-01-11 at 02:57 +0000, Shadrock Uhuru via arch-general
> wrote:
> > 	Error verifying signature: parse error
> > --gbecqo27lfuqy6h2
> > Content-Type: text/plain; charset=utf-8; format=flowed
> > Content-Disposition: inline
> > 
> > i have a server that has not been booted since 2017,
> > i tried upgrading with pacman -Syu,
> > i have post the screen output at 
> > http://paste.openstack.org/show/788264/
> > i thought adding Eli Schwartz' personal repository to  pacman.conf
> > would have allowed the upgrade with his Binary builds of pacman-
> > static.
> > is my problem still to do with the xz to zstd change or something
> > different ?
> > 
> > shadrock
> > 
> > --gbecqo27lfuqy6h2--
> 
> Update the keyring first. The keys used to package those package aren't
> in the machine.
* or at least aren't trusted

> $ pacman -S archlinux-keyring
> $ pacman -Syu
> 
> Filipe Laíns

On 11-01-2020 10:09, Georg wrote:

You can use the ALA [0] to update to a specific date. Pick a date not too far before the first zst packages roll in, update (keyring first) and then you should be able to use the current mirrors.

[0] https://wiki.archlinux.org/index.php/Arch_Linux_Archive#How_to_restore_all_p...

I agree with georg about using the ALA, but not about picking a recent date. Shadrock, before doing any updates I suggest you backup your system and reboot. This will allow you to verify whether your start point is in good condition. check the news items after your last reboot , https://www.archlinux.org/news/ Verify which items that require manual intervention apply to your system. If yes, use a date just before the news item and set the ALA to that date. Update, reboot, solve problems (if any) then set the ala data just after the news date and Update, reboot, solve problems (if any) . repeat for all news items This will allow you to break 2+ years of updates / reboots in small pieces. LW

Op za 11 jan. 2020 15:05 schreef Mr.Elendig <mrelendig@har-ikkje.net>:

On 11/01/2020 03:57, Shadrock Uhuru via arch-general wrote:

...

i have a server that has not been booted since 2017, i tried upgrading with pacman -Syu, i have post the screen output at http://paste.openstack.org/show/788264/ i thought adding Eli Schwartz' personal repository to pacman.conf would have allowed the upgrade with his Binary builds of pacman-static. is my problem still to do with the xz to zstd change or something different ?

Personally I would backup the data/configuration, do a clean reinstall and then restore the data and update/port the configurations as needed.

I've had good fairly good experience in upgrading an old Arch install the past. Make a full backup, try the upgrade (both pacman-static and the keyring are probably pre-requisites) and just solve any errors/warnings one at the time. If it really fails or takes too long, use your backup. If the server is in any way important, perhaps restoring the backup to a VM first is an option? Mvg, Guus Snijders