Nicholas,
> > There is no need defend, provide proof, or even explain yourself
> > here - I was the one who built & uploaded this package, and even
> > apologise for doing so in my previous message.
> >
> > I believe you have either misread or misinterpreted the "just an
> > FYI" element of me
On Sun, Oct 21, 2018 at 05:06:34PM -0400, Chris Lamb wrote:
> Nicholas,
>
> > 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.
>
Nicholas,
> 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.
[snip]
There is no need defend, provide proof, or even explain yourself
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.
>
>
Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: binnmu
nmu btrfs-progs_4.17-1~bpo9+1 . amd64 . stretch-backports . -m "Rebuild in a
clean stretch environment."
The maintainer uploaded binaries apparently were built on sid/buster,
since
5 matches
Mail list logo
