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

2021-08-29 Thread Roberto C . Sánchez
I removed the top line of the change log (the security team reference), rebuilt, and re-uploaded. Thanks again for all the help and for your patience with my mistake. Regards, -Roberto -- Roberto C. Sánchez

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

2021-08-29 Thread Adam D. Barratt
On Sun, 2021-08-29 at 12:25 -0400, Roberto C. Sánchez wrote: > On Sun, Aug 29, 2021 at 05:17:02PM +0100, Adam D. Barratt wrote: > > 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:3

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

2021-08-29 Thread Roberto C . Sánchez
On Sun, Aug 29, 2021 at 05:17:02PM +0100, Adam D. Barratt wrote: > > 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 a

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

2021-08-29 Thread Adam D. Barratt
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 main

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

2021-08-27 Thread Roberto C . Sánchez
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 wi

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

2021-08-27 Thread Adam D. Barratt
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 re