Hi,
On Sun, Oct 21, 2018 at 04:01:54PM -0400, Chris Lamb wrote:
> Ivo et al.,
>
> > > The maintainer uploaded binaries apparently were built on sid/buster,
> > > since python3-btrfsutil depends on python3 (<< 3.7), python3 (>= 3.6~)
> >
> > The package wasn't uploaded by the maintainer.
>
> Oh, apologies for that. I'm not sure quite how that happened as it
> was fairly clear it was destined for stable-backports (see #897072).
>
> > I'm adding a Cc to the sponsor.
>
> I'm adding a Cc to the requestor of said upload as an FYI.
Thank you for CCing me. I build everything in a clean chroot and have
taken care to configure my workflow so that every build or upload
requires an explicit target dist and errors if anything doesn't match.
Eg: backport-to-stretch builds in a clean chroot that only pulls in
deps from stretch-backports if necessary, and I have separate dput
targets for unstable, stretch-backports, and mentors.
Proof: https://drive.google.com/open?id=19u2PGPxMeK1ZISwi0iqKcm3nuRzs7XBp
After I find the time to integrate rmadison into backport-to-stretch
(aka: script-to-prevent-human-error) I'll share it in the hopes that
it will be useful to others. Thanks to Chris Lamb for suggesting
using it to generate -v${latest_version_available_in_stable}. :-)
Andreas and Ivo, thank you for catching this and scheduling the rebuild.
Cheers,
Nicholas
Attachment:
signature.asc
Description: PGP signature