Bug#933764: buster-pu: package e2fsprogs/1.44.5-1+deb10u1
On Sat, 2019-08-03 at 13:08 -0400, Theodore Y. Ts'o wrote:
> 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.
Re-using this bug is fine; I'll get the metadata fixed up.
On Sat, 2019-08-03 at 15:46 -0400, Theodore Y. Ts'o wrote:
> Oh, one more question --- should I be doing a source-only, or binary
> push when I push to buster-proposed-updates.
Either works fine. If you go the source-only route, please make sure
the .changes is _not_ named _amd64.changes or similar, as that will
complicate things for the buildd upload.
> I'm a bit confused about whether it will be going into the NEW queue,
> and hence require a binary push, or a source-only build because
> that's the new hotness and it's required for promotions to testing.
While there is a holding suite in front of p-u named "stable-new", it's
not NEW in the ftp-master sense, and there's generally no reason for an
update to stable to hit NEW. The previous one only did because some of
the binary packages you uploaded don't exist in stretch.
Regards,
Adam
Reply to: