Hello,
On Mon, 4 Feb 2019 09:53:56 +1100 Ben Finney <bign...@debian.org> wrote:
> Control: retitle -1 schroot: emits many messages “Alias ‘[...]’ already
> associated with ‘[...]’ chroot”
> Control: found -1 schroot/1.6.10-6+b1
>
> On 03-Feb-2019, Johannes Schauer wrote:
> > it seems that this message comes from schroot and not sbuild. Thus,
> > reassigning.
>
> Thanks. I am also altering the metadata for the version of ‘schroot’
> installed.
I ran into the same problem myself today, and found this bug report.
The problem started after I have added a second sbuild chroot with the
following command:
sudo sbuild-debian-developer-setup --suite=stable
And, thanks to your hint that the issue is actually schroot related, I
found in /etc/schroot/chroot.d/ two config files
unstable-amd64-build-XXXXXX and stable-amd64-build-XXXXXX, both
created by sbuild-debian-developer-setup. And, sure enough, both
files contain the line
aliases=UNRELEASED,sid
which is correct for unstable but inappropriate for stable. schroot's
"Alias already associated" warnings are valid. The actual bug is
found somewhere else, from whomever or from whatever command that
created those schroot chroot.d config files.
And, sure enough, we can find in /usr/bin/sbuild-debian-developer-setup:
https://sources.debian.org/src/sbuild/0.80.0/bin/sbuild-debian-developer-setup/#L56-L57
when it calls sbuild-createchroot, it indiscriminately adds the flags
--alias=UNRELEASED
--alias=sid
which are appropriate for unstable only.
So, perhaps this bug should be re-assigned to the
sbuild-debian-developer-setup binary package? :-)
Cheers,
Anthony
