Re: Need better release validation documentation/strategy.

2022-04-09 Thread Bob Friesenhahn
On Fri, 8 Apr 2022, ckeader wrote: The key server network as we knew it is dead and buried, and I would not expect any of them to provide complete or indeed reliable information. This article explains why: https://gist.github.com/rjhansen/67ab921ffb4084c865b3618d6955275f. There was some

Re: Need better release validation documentation/strategy.

2022-04-09 Thread ckeader
> For some reason key servers are not very helpful these days with some > of them offering distorted behavior or appearing to be severely > overloaded. It may be that the key server used by default by Ubuntu > Linux imposes additional limitations such as regarding exposing email >

Re: Need better release validation documentation/strategy.

2022-04-08 Thread Bob Friesenhahn
On Fri, 8 Apr 2022, Jim Meyering wrote: On Fri, Apr 8, 2022 at 6:30 AM Bob Friesenhahn wrote: Today I saw an announcement for a new version of gzip. It provided lots of data for how to verify the downloaded tarballs. I recently saw a very similar announcement for a new version of libtool. I

Re: Need better release validation documentation/strategy.

2022-04-08 Thread Jim Meyering
On Fri, Apr 8, 2022 at 6:30 AM Bob Friesenhahn wrote: > Today I saw an announcement for a new version of gzip. It provided > lots of data for how to verify the downloaded tarballs. I recently > saw a very similar announcement for a new version of libtool. I am not > sure where the template of

Re: Need better release validation documentation/strategy.

2022-04-08 Thread Carlos O'Donell
On 4/8/22 09:30, Bob Friesenhahn wrote: > Today I saw an announcement for a new version of gzip. It provided > lots of data for how to verify the downloaded tarballs. I recently > saw a very similar announcement for a new version of libtool. I am > not sure where the template of this