Lost .asc file in archive by not referencing it in an upload (Was: Re: OpenSSL updates)
- To: debian-dpkg@lists.debian.org
- Cc: Salvatore Bonaccorso <carnil@debian.org>, Kurt Roeckx <kurt@roeckx.be>
- Subject: Lost .asc file in archive by not referencing it in an upload (Was: Re: OpenSSL updates)
- From: Sebastian Andrzej Siewior <sebastian@breakpoint.cc>
- Date: Sun, 8 Apr 2018 13:58:53 +0200
- Message-id: <[🔎] 20180408115852.a6vfamomlknnjyhy@mikejones.breakpoint.cc>
- In-reply-to: <20180329140932.d5fikxeu6wniilsu@lorien.valinor.li>
- References: <20180327225503.4zr6p6azojgbhfqn@breakpoint.cc> <20180328050545.bbwf666tovlpa36f@lorien.valinor.li> <20180328123443.kftntx5dmqawvt6i@breakpoint.cc> <20180328181437.GF1809@roeckx.be> <20180328193927.GA28658@eldamar.local> <20180329115546.vyotapoosqamxogy@breakpoint.cc> <20180329140932.d5fikxeu6wniilsu@lorien.valinor.li>
-security +dpkg
On 2018-03-29 16:09:32 [+0200], Salvatore Bonaccorso wrote:
> Hi,
Hi,
> One was rejected, because:
>
> openssl1.0_1.0.2l-2+deb9u3.dsc: Refers to non-existing file 'openssl1.0_1.0.2l.orig.tar.gz.asc'
> Perhaps you need to include the file in your upload?
the 9u1 upload did not have the .asc file referenced and so it got lost. What
could be done to avoid such mistakes in the future?
Would it make sense to let dak reject uploads for uploads of the same upstream
version when the .dsc files does not reference the .asc anymore? Or would it
better to teach dpkg-source to fail (based on a config switch) if the .asc
file is missing.
> Regards,
> Salvatore
Sebastian
Reply to: