[buildd-tools-devel] Bug#559659: sbuild: Targets unstable even when dealing with experimental stuff

[Cyril Brulebois]

Package: sbuild
Version: 0.59.0-1
Severity: serious
Justification: Fucked my uploads.

Hi,

firstly, I'm aware of #529281, and I believe this might be different.

I really don't see why the resulting distribution should be “unstable”
when one uses:
$ sbuild -c experimental-amd64-sbuild -s -A foo.dsc

And when:
 - the chroot name is experimental-…
 - the chroot setup says nothing about unstable or sid[1].
 - the distribution is set to experimental (which is ignored, which is
   the subject of #529281, if I understood it correctly).

[1]:
| $ sudo cat /etc/schroot/chroot.d/experimental-amd64-sbuild
| [experimental-amd64-sbuild]
| type=directory
| description=Debian experimental/amd64 autobuilder
| location=/home/cyril/opt/experimental-amd64-sbuild
| priority=3
| groups=root,sbuild
| root-groups=root,sbuild
| run-setup-scripts=true
| run-exec-scripts=true

So, WTH setting the distribution to “unstable”? Looks like I've got 30+
packages in the wrong distribution now. Not good. Really not.

If you really want to force people setting (manually) the distribution,
just refuse to proceed if no distribution was specified.

The current behaviour sounds insane to me, hence this RC bug.

Mraw,
KiBi.