Re: SHA* digests in checksums.yaml.gz

2018-03-05 Thread Cédric Boutillier
Hi! Thanks for the feedback. I've just uploaded gem2deb 0.38 with that change and other commits from Antonio about ruby2.5. Cheers, Cédric

Re: SHA* digests in checksums.yaml.gz

2018-03-04 Thread Michael Moll
Hi, On Sat, Mar 03, 2018 at 02:46:19PM +0100, Cédric Boutillier wrote: > I've just pushed a branch on Salsa called 'sha_digests' with a proposed > change. I've just removed SHA1 and replaced it with SHA256, and check > that at least one of SHA256/SHA512 is available in checksums.yaml. > >

Re: SHA* digests in checksums.yaml.gz

2018-03-03 Thread Cédric Boutillier
On Thu, Feb 22, 2018 at 02:13:47PM -0300, Antonio Terceiro wrote: > On Tue, Feb 20, 2018 at 04:32:25PM +0100, Cédric Boutillier wrote: [...] > > > > I am considering adding Digest::SHA256 to the list of digests tested in > > gem2tgz and skip the checksum computation if the digest name is not a >

Re: SHA* digests in checksums.yaml.gz

2018-02-22 Thread Antonio Terceiro
On Tue, Feb 20, 2018 at 04:32:25PM +0100, Cédric Boutillier wrote: > Hi, > > When trying to package some dependencies for a new version of Nanoc, I > noticed that some gems start to ship SHA256 digests instead of SHA1 in > addition to SHA512. > This happens for example with the ddmetrics gem >

SHA* digests in checksums.yaml.gz

2018-02-22 Thread Cédric Boutillier
Hi, When trying to package some dependencies for a new version of Nanoc, I noticed that some gems start to ship SHA256 digests instead of SHA1 in addition to SHA512. This happens for example with the ddmetrics gem https://rubygems.org/gems/ddmetrics As a consequence, gem2deb fails on such gems