Hi Marc, On Mi, 2015-06-17 at 19:20 +0200, Marc Haber wrote:
> this happens after trying to install mini-buildd 1.0.6: > mh@spinturn:~$ dpkg --list mini-buildd > Desired=Unknown/Install/Remove/Purge/Hold > | Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend > |/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad) > ||/ Name Version Architecture Description > +++-======================-================-================-================================================= > iF mini-buildd 1.0.6 all minimal build > daemon - daemon > mh@spinturn:~$ sudo dpkg --configure -a > Setting up mini-buildd (1.0.6) ... > addgroup: The group `mini-buildd' already exists as a system group. Exiting. > usermod: no changes > usermod: no changes > The user `mini-buildd' is already a member of `sbuild'. > Setting admin password...Traceback (most recent call last): > File "/usr/sbin/mini-buildd", line 16, in <module> > import daemon.pidlockfile > File "/usr/lib/pymodules/python2.7/daemon/pidlockfile.py", line 33, in > <module> > class PIDLockFile(LinkFileLock, object): > TypeError: Error when calling the metaclass bases > function() argument 1 must be code, not str alas ;). This error has been brought in by new python-lockfile (which is used by python-daemon). What's more, a new python-daemon with incompatible API changes is coming (currently stuck in NEW). So as a quick answer: under sid/stretch, downgrading python-lockfile to the jessie/stable version would fix it -- and it would also proof that this is actually your problem. Ben already provided patches for mini-buildd for the new python-daemon API; this will be coming soon and will eventually fully fix this problem. Sorry for the inconvenience ;), Fwiw, I will continue to provide jessie backports for 1.0.x, and I really recommend using that for production use. Hth! Stephan -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
