Re: [arch-general] how to upgrade 2017 server ?

2020-01-10 Thread Filipe Laíns via arch-general
On Sat, 2020-01-11 at 03:02 +, Filipe Laíns via arch-general wrote: > On Sat, 2020-01-11 at 02:57 +, Shadrock Uhuru via arch-general > wrote: > > Error verifying signature: parse error > > --gbecqo27lfuqy6h2 > > Content-Type: text/plain; charset=utf-8; format=flowed > > Content-Disposit

Re: [arch-general] how to upgrade 2017 server ?

2020-01-10 Thread Filipe Laíns via arch-general
On Sat, 2020-01-11 at 02:57 +, 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 up

Re: [arch-general] how to upgrade 2017 server ?

2020-01-10 Thread Chris Billington via arch-general
Pacman static will likely help, but you'll need to actually install it and use it, i.e.: sudo pacman -S pacman-static sudo pacman-static -Syu On Sat, Jan 11, 2020 at 1:57 PM Shadrock Uhuru via arch-general < arch-general@archlinux.org> wrote: > i have a server that has not been booted since 2017

[arch-general] how to upgrade 2017 server ?

2020-01-10 Thread Shadrock Uhuru via arch-general
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-stati

[arch-general] tzdata, about dir /usr/share/zoneinfo-leaps

2020-01-10 Thread Yi Zheng via arch-general
Hi, all I found that there is a 'new' dir /usr/share/zoneinfo-leaps It includes files almost the same ones in /usr/share/zoneinfo/right/ I checked the md5 of every files under those two dir. And found that they are the same ones. The only exception is /usr/share/zoneinfo/right/US/Pacific-New, w

Re: [arch-general] [aur-general] Sha256sum unexpected behaviour

2020-01-10 Thread Iyán Méndez Veiga
> Anyone got some idea why this might happen? makepkg --printsrcinfo does not compute anything, it just extracts the information from the PKGBUILD file. This is used to generate the .SRCINFO file. makepkg --geninteg, on the other hand, downloads all the files in source array, computes the checks

Re: [arch-general] Sha256sum unexpected behaviour

2020-01-10 Thread WorMzy Tykashi via arch-general
On 10 January 2020 08:27:11 GMT, Leonidas Spyropoulos via arch-general wrote: >Hello, > >I got a weird issue with sha256sum behaviour. When creating the package >with makepkg --geninteg I get a hash and when trying to build it with >makepkg the hash fails. The interesting bit is --ptintsrcinfo

Re: [arch-general] Sha256sum unexpected behaviour

2020-01-10 Thread Tinu Weber
On Fri, Jan 10, 2020 at 08:27:11 +, Leonidas Spyropoulos via arch-general wrote: > Hello, > > I got a weird issue with sha256sum behaviour. When creating the package > with makepkg --geninteg I get a hash and when trying to build it with > makepkg the hash fails. The interesting bit is --ptin

[arch-general] Sha256sum unexpected behaviour

2020-01-10 Thread Leonidas Spyropoulos via arch-general
Hello, I got a weird issue with sha256sum behaviour. When creating the package with makepkg --geninteg I get a hash and when trying to build it with makepkg the hash fails. The interesting bit is --ptintsrcinfo comes up with a different hash. Anyone got some idea why this might happen? See below