Bug#993134: buster-pu: package shiro/1.3.2-4+deb10u1

["Adam D. Barratt" <adam@adam-barratt.org.uk>]

On Fri, 2021-08-27 at 15:47 -0400, Roberto C.Sánchez wrote:
> On Fri, Aug 27, 2021 at 08:33:44PM +0100, Adam D. Barratt wrote:
> > On Fri, 2021-08-27 at 13:45 -0400, Roberto C. Sanchez wrote:
> > > I have prepared an update for shiro in buster.  This has been
> > > coordinated with the package maintainer and at the recommendation
> > > of
> > > the
> > > security team and with their concurrence, it is being proposed
> > > for
> > > the
> > > next buster point release.
> > 
> > +shiro (1.3.2-4+deb10u1) buster; urgency=medium
> > +
> > +  * Non-maintainer upload by the Security Team.
> > 
> > fwiw, I at least find it a little confusing to have debdiffs claim
> > to
> > be uploads by the Security Team when they were neither produced (so
> > far
> > as I can tell) nor uploaded by that team, nor released via the
> > security
> > archive.
> > 
> Quite right.  I originally prepared the uploads as security updates,
> but then changed course to the point release route.  Would you like
> to REJECT the uploads and I can upload again with a fixed changelog?

As it turns out, the bullseye upload is still sat on upload.d.o,
because:

Aug 29 15:31:17 processing /shiro_1.3.2-4+deb11u1_source.changes
Aug 29 15:31:17 shiro_1.3.2.orig.tar.xz doesn't exist (ignored for now)

My assumption is that both of your .changes reference the same
.orig.tar.xz. If they were uploaded close together, then the queue
daemon will have removed the .orig from the queue together with the
files from the buster upload, thus stranding the bullseye upload. To
avoid this, either space the uploads further apart, or don't include
the .orig in more than one of them - in fact, if the upstream tarball
is the same as is already in the archive, you don't need to include it
in either.

In this case, you'll either need to dcut the remaining files from the
previous upload, or wait for the queue daemon to delete them on its
own.

I've flagged the buster upload for rejection, once dak notices, so feel
free to re-upload that once you receive the rejection confirmation (and
bullseye once it times out, or you dcut it).

Regards,

Adam