On Sat, Aug 03, 2019 at 04:08:14PM +0100, Adam D. Barratt wrote:
>
> I assume this is simply a case of an outdated chroot pointing at
> "stable" or similar. The net effect is that the upload ended up in NEW
> (presumably as buster's e2fsprogs builds additional binary packages
> relative to stretch). I've asked ftp-master to reject that upload.
>
> I'm not sure whether you were intending to fix this in stretch or
> buster, but this should either be 1.43.4-2+deb9u1 for stretch, or
> 1.44.5-1+deb10u1 targetted at buster.
It's an outdated chroot plus me being confused. It was supposed to be
1.44.5-1+deb10u1 targetted at buster. That's actually what *sources*
are; but the changelog and chroot it was built against was stretch.
*Sigh*.
I'll go away, fix the changelog and rebuild it now. Do you prefer
whether we just close this bug as invalid, and I'll open a new one, or
should we retitle this bug and append to it? I don't have strong
preferences either way.
Cheers,
- Ted
