Bug#1052822: mini-buildd: FTBFS: make[1]: *** [debian/rules:11: override_dh_auto_build] Error 25
Hi Lucas, On Tue, 2023-09-26 at 14:43 +0200, Lucas Nussbaum wrote: > Source: mini-buildd > Version: 2.0.8 > Severity: serious (..) > During a rebuild of all packages in sid, your package failed to build > on amd64. (..) > Relevant part (hopefully): > > make[1]: Entering directory '/<>' (..) > > hostname: Name or service not known is ``hostname [-f]`` not working in the build environment? I see that ``m-b-self-signed-cerificate --help`` fails, which would add up. Also, 2.0.8 was a source-only upload and already 'got thru' previously. Hth! Stephan signature.asc Description: This is a digitally signed message part
Bug#1026843: Not suitable for testing yet (due to outstanding migration tests)
Package: mini-buildd Version: 1.9.112 Severity: serious While working quite well already on a new setup, some crucial testing has not yet been fully done yet -- especially * migration tests (i.e., upgrading an existing installation from 1.0.x->2.0.x) * new 'setup' system's maintenance facilities I.e., I don't recommend upgrading production systems just yet, please wait for a proper 2.0.x release. Thanks! Stephan -- System Information: Debian Release: bookworm/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: amd64 (x86_64) Kernel: Linux 6.0.0-0.deb11.2-amd64 (SMP w/16 CPU threads; PREEMPT) Kernel taint flags: TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8) (ignored: LC_ALL set to C.UTF-8), LANGUAGE not set Shell: /bin/sh linked to /usr/bin/dash Init: unable to detect Versions of packages mini-buildd depends on: ii adduser3.129 ii debconf [debconf-2.0] 1.5.80 ii debootstrap1.0.128+nmu2 ii devscripts 2.22.2 ii dirmngr2.2.40-1 ii dpkg-dev 1.21.13 ii gnupg 2.2.40-1 ii init-system-helpers1.65.2 ii python33.10.6-3 ii python3-mini-buildd1.9.112 ii python3-pyftpdlib 1.5.7-2 ii reprepro 5.3.1-1 ii sbuild 0.84.2 ii schroot1.6.13-3+b1 ii sudo 1.9.11p3-2 ii sysvinit-utils [lsb-base] 3.06-2 ii zstd 1.5.2+dfsg-1 Versions of packages mini-buildd recommends: ii arch-test0.19-1 ii autopkgtest 5.27 ii lintian 2.115.3 ii mini-buildd-doc 1.9.112 ii piuparts 1.1.5 ii python3-apt 2.5.0 Versions of packages mini-buildd suggests: ii binfmt-support 2.2.2-2 ii btrfs-progs 6.0.2-1 ii debian-archive-keyring 2021.1.1 ii haveged 1.9.14-1+b1 ii lvm22.03.16-2 ii openssl 3.0.7-1 ii qemu-user-static1:7.2+dfsg-1 ii ubuntu-keyring 2020.06.17.1-1 -- Configuration Files: /etc/default/mini-buildd changed [not included] /etc/sudoers.d/mini-buildd-sudoers [Errno 13] Permission denied: '/etc/sudoers.d/mini-buildd-sudoers' -- debconf information excluded
Bug#937049: mini-buildd: Python2 removal in sid/bullseye
Hi Bastian, On Tue, 2022-11-29 at 21:09 +0100, Bastian Germann wrote: > Why don't you move the experimental to unstable now? well, some crucial tests (especially on upgrading) are unfortunately still pending. Uploading to unstable always marked "ok to use" in that respect, however... > The unstable mini.buildd version is not usable but is now the last reverse > dependency of python-setuptools > (sphinx and nuitka only have it as optional alternatives). as it seems to cause big pain elsewhere, I will prepare the next upload (within "days" ;) for unstable (with a blocking RC bug if need be). Hth! S signature.asc Description: This is a digitally signed message part
Bug#937049: mini-buildd: Python2 removal in sid/bullseye
Hi Moritz, On Fri, 2022-10-28 at 00:12 +0200, Moritz Mühlenhoff wrote: > Am Fri, Aug 30, 2019 at 07:26:40AM + schrieb Matthias Klose: > > Package: src:mini-buildd > > Version: 1.0.41 > > Severity: normal > > Tags: sid bullseye > > User: debian-pyt...@lists.debian.org > > Usertags: py2removal > > > > Python2 becomes end-of-live upstream, and Debian aims to remove > > Python2 from the distribution, as discussed in > > https://lists.debian.org/debian-python/2019/07/msg00080.html > > How close is the 2.x branch in experimental from being a replacement? > python2 will be dropped in bookworm and also removed from the archive. it's taking way too long already ;), but I am still quite confident to be able to upload to unstable this year, i.e., before Debian freeze/bookworm. Hth! S
Bug#933751: mini-buildd (build-)depends on cruft package.
Hi Peter, On Fri, 2019-08-02 at 22:11 +0100, Peter Michael Green wrote: > Package: mini-buildd > Version: 1.0.41 > Severity: serious > > python-mini-buildd depends on and the mini-buildd source package > build-depends on the python-django-registration binary package which > is > no longer built by the python-django-registration source package. yes, or 'python2 django', for that matter ;). I guess it will be removed from testing soon: http://mini-buildd.installiert.net/articles/10x-maintenance-moved-to-hellfield-archive.html > I notice this already seems to be fixed in experimental, are there > any > blockers for uploading the experimental version to unstable? The branch uploaded to experimental is development, and should not be used for production. I am pressing for a release asap (~months), then everything will be fine again ;). Hth! S
Bug#898850: ui-utilcpp: FTBFS: syntax error in configure script
Hi Sven, On Wed, 2018-05-16 at 17:26 +0200, Sven Joachim wrote: > Source: ui-utilcpp > Version: 1.8.5-2 > Severity: serious > > Your package FTBFS everywhere[1], the reason being that the configure Ups yes, thanks for the hint ;). I did not thoroughly check on this after the hasty post-salsa upload... Thx! S
Bug#836851: marked as pending
tag 836851 pending thanks Hello, Bug #836851 reported by you has been fixed in the Git repository. You can see the changelog below, and you can check the diff of the fix at: http://git.debian.org/?p=python-modules/packages/python-django-registration.git;a=commitdiff;h=76f68f4 --- commit 76f68f4738c01120c91e2255488670ade63a5db3 Author: Stephan Sürken <abs...@debian.org> Date: Thu Sep 29 18:10:06 2016 + changelog: Prepare 2.1.2-3. diff --git a/debian/changelog b/debian/changelog index af55596..ea9f227 100644 --- a/debian/changelog +++ b/debian/changelog @@ -1,3 +1,11 @@ +python-django-registration (2.1.2-3) unstable; urgency=medium + + [ Chris Lamb ] + * [9f8bc14] Add missing Breaks & Replaces clause after -doc split +(Closes: #836851) + + -- Stephan Sürken <abs...@debian.org> Thu, 29 Sep 2016 18:09:32 + + python-django-registration (2.1.2-2) unstable; urgency=medium * [347c14a] rules: Make po cleanup work for multiple packages.
Bug#834683: [pkg-gnupg-maint] Bug#834683: fixed in mini-buildd 1.0.17
Hi Santiago, On Mo, 2016-09-12 at 21:34 +0100, Santiago Vila wrote: (...) > > Lastly, one other option for gnupg at least is to patch upstream to > > use > > --debug-quick-random in the build-time test. > > > > do any of these options sound more appealing than the others? > I didn't know about --debug-quick-random, it seems perfect to me. > > Stephan, do you think it would be possible to patch mini-buildd so > that --debug-quick-random is added to gnupg command line, but only > when the package is doing the tests following the build? fwiw, I quickly tested '--debug-quick-random', and it does the trick, albeit for 2.1 only. So I unfortunately cannot use it (needing to support 1.4 still as well). I am now doing the doctest with pre-built keys, so this is will hopefully finally settle this issue with the next upload. Btw, it's only now that I actually grasp your initial problem was about entropy all along ;). I just blatantly assumed your initial bug report was about the doctest failing due to GPG 2.1 (which it did at the time, entropy or not). Thx, S
Bug#834683: [pkg-gnupg-maint] Bug#834683: fixed in mini-buildd 1.0.17
Rehi, On Mo, 2016-09-12 at 21:34 +0100, Santiago Vila wrote: > On Mon, Sep 12, 2016 at 07:34:09PM +0200, Daniel Kahn Gillmor wrote: > > > > > An even easier approach might be to do the following within the > > build: > > > > * ln -sf /dev/urandom /dev/random > > > > why would we need the blocking kernel RNG in the buildd anyway? > Either that, or maybe a build-depends on a package specifically > created to do that (as I'm not sure we could really ask all buildd > operators to make the symlink permanently). > > A good solution should be automatic and not need manual intervention, > and should be independent of the machine on which the build is done. Exactly ;). > > Lastly, one other option for gnupg at least is to patch upstream to > > use > > --debug-quick-random in the build-time test. > > > > do any of these options sound more appealing than the others? > I didn't know about --debug-quick-random, it seems perfect to me. > > Stephan, do you think it would be possible to patch mini-buildd so > that --debug-quick-random is added to gnupg command line, but only > when the package is doing the tests following the build? Yeah, I will check this out (though it's not an option to gpg directly, afair). Or maybe going with a pre-generated key. Thx, S
Bug#834683: [pkg-gnupg-maint] Bug#834683: fixed in mini-buildd 1.0.17
Hi Daniel, Santiago, thx for the answer; I am not 100% satisfied, though ;). For me, it actually boils down to what notion we have: (1) The builder hosts must provide reasonable entropy. (2) Software testsuites generally must work fine even with low entropy. In the past, I tended to go with (1) (which is one of the reasons mini- buildd recommends haveged). So I guess just going for both for now ;), so I will check how I can improve that specific doctest in mini-buildd. I am still sort of wondering how other testsuites behave in this respect (like gnupg, gcrypt)? Thx! S
Bug#834683: fixed in mini-buildd 1.0.17
Hi Santiago, On So, 2016-09-11 at 11:37 +0200, Santiago Vila wrote: (...) > This is the changelog entry you wrote: > > > * [8ee94bc] gnupg.py: Add extra method to get sec user id. Fixes > doctest > > for GPG 2.1. Thanks to Santiago Vila (Closes: 834683) > > If this is only intended to work with gnupg 2, please add > Build-Depends: gnupg (>= 2) so that autobuilders testing packages in > stretch do not even try to build it with gnupg version 1. no, this should work for both, 1.4 and 2.1. > OTOH, if this is intended to work with both gnupg 1 and gnupg 2 > (for example, if you intend this to be backported to jessie), > then the problem is still here. Yes, I do ;). And I did test it under jessie, and also the package build under stretch. > The error message: (...) > suggests to me that there is not enough entropy to generate a key. If entropy actually is the problem, it should have always been there for all 1.0.x versions (having that doctest). > (I don't know how to fix that, sorry, maybe an additional > build-depends on some package which wraps accesses to /dev/random to > make them faster, if such package exists). > > The full build log is attached. > > This time I only tried to build it once, but since the problem was > not > supposed to always happen, it is probably correct to say that the > FTBFS-randomness has not been eliminated. Ok, agree, this does add some randomness [which I usually mitigate running something like haveged on the builder host]. I guess this generally means automated tests depending on some entropy must be avoided? Anyway, I don't have a good solution either right now; maybe someone already has? Will look around eventually ;) Thx, S
Bug#790274: python-pyftpdlib: FTBFS: Failure in test_on_incomplete_file_sent
Hi Daniel, Andreas, On Fri, 17 Jul 2015 00:47:55 +0200 Andreas Beckmann a...@debian.org wrote: Followup-For: Bug #790274 Similar failure while rebuilding in a clean jessie pbuilder environment: [...] [...] File /usr/lib/python2.7/multiprocessing/synchronize.py, line 147, in __init__ SemLock.__init__(self, SEMAPHORE, 1, 1) File /usr/lib/python2.7/multiprocessing/synchronize.py, line 75, in __init__ sl = self._semlock = _multiprocessing.SemLock(kind, value, maxvalue) OSError: [Errno 13] Permission denied debian/rules:8: recipe for target 'override_dh_auto_test' failed make[1]: *** [override_dh_auto_test] Error 1 make[1]: Leaving directory '/tmp/buildd/python-pyftpdlib-1.2.0' debian/rules:4: recipe for target 'build' failed make: *** [build] Error 2 dpkg-buildpackage: error: debian/rules build gave error exit status 2 this very much sounds like it was build in a builder env with shared memory broken. I just retested that it builds fine in clean build environments for sid, jessie, and stretch. So I guess you both have run into (at least some variant of) https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=728096 and this is not in python-pyftpdlib. Could you please check, and downgrade the severity if you agree? Thx! S -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#793888: ui-gxmlcpp includes autogenerated files that cannot be rebuilt from source
On Sa, 2015-08-01 at 19:46 +0200, Johannes Schauer wrote: Hi, (...) I reported it like that because I was not able to recreate ./configure and aclocal.m4 from source. When I deleted both files and tried to regenerate them, I ran into an error and I also got an error when I tried to rebuild with `dh --with autoreconf`. This made me believe that ./configure and aclocal.m4 can *not* be built from source. so this does not work even _with_ ui-auto installed? Thx, S -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#793888: ui-gxmlcpp includes autogenerated files that cannot be rebuilt from source
Hi Johannes! On Di, 2015-07-28 at 17:31 +0200, Johannes Schauer wrote: Source: ui-gxmlcpp Version: 1.4.3-1 Severity: serious Justification: Policy 2.2.1 (...) the source package for ui-gxmlcpp includes a ./configure and ../aclocal.m4 without including their source. If ./configure and ../aclocal.m4 are removed, then the package cannot be built anymore. For example, the current aclocal.m4 contains parts of ui-auto but ui-gxmlcpp does not build depend on that package. Please add the missing bits so that this source package can be built from source again and does not require autogenerated scripts like ../configure and ./aclocal.m4. Ok, switching to autoreconf (with b-d on ui-auto) is an option I will consider. Could you ponder a bit more why you think this is a policy violation? It seems a bit harsh considering how autotools work, and everything can be rebuild within Debian/main -- but maybe I missed something ;). Thanks! Stephan -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#764595: mini-buildd: Can't GPG-verify changes files (since python-debian-0.1.23)
Package: mini-buildd
Version: 1.0.4
Severity: grave
Justification: renders package unusable
A reminder to myself, and for those wondering...
grave: As this basically prevents any package building.
Will be fixed asap, see
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=764380
Workarounds:
(1)
Downgrade to python-debian 0.1.23
(2)
diff --git a/mini_buildd/ftpd.py b/mini_buildd/ftpd.py
index d763b32..46769a7 100644
--- a/mini_buildd/ftpd.py
+++ b/mini_buildd/ftpd.py
@@ -42,7 +42,7 @@ class Incoming(object):
if cls.is_changes(changes_file):
LOG.debug(Checking: {c}.format(c=changes_file))
try:
-for fd in
debian.deb822.Changes(mini_buildd.misc.open_utf8(changes_file)).get(Files,
[]):
+for fd in debian.deb822.Changes(open(changes_file,
r)).get(Files, []):
valid_files.append(fd[name])
LOG.debug(Valid: {c}.format(c=fd[name]))
-- System Information:
Debian Release: jessie/sid
APT prefers unstable
APT policy: (500, 'unstable'), (500, 'testing'), (1, 'experimental')
Architecture: amd64 (x86_64)
Kernel: Linux 3.16-0.bpo.2-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Versions of packages mini-buildd depends on:
ii adduser 3.113+nmu3
ii debconf [debconf-2.0] 1.5.53
ii debootstrap 1.0.63
ii devscripts 2.14.7
ii dpkg-dev1.17.16
ii gnupg 1.4.18-4
ii libjs-jquery1.7.2+dfsg-3.2
ii libjs-sphinxdoc 1.2.3+dfsg-1
ii lintian 2.5.28
ii mini-buildd-common 1.0.4
ii python-cherrypy33.5.0-1
ii python-daemon 1.5.5-1
ii python-django 1.7-2
ii python-django-extensions1.3.10-1
ii python-django-registration 1.0+dfsg-2
ii python-mini-buildd 1.0.4
ii python-pyftpdlib1.2.0-1
pn python:any none
ii reprepro4.16.0-1
ii sbuild 0.64.3-2
ii schroot 1.6.10-1+b1
ii sudo1.8.10p3-1
Versions of packages mini-buildd recommends:
ii python-apt 0.9.3.10
Versions of packages mini-buildd suggests:
pn binfmt-supportnone
ii debootstrap 1.0.63
pn haveged none
pn lvm2 none
pn qemu-user-static none
-- Configuration Files:
/etc/default/mini-buildd changed [not included]
/etc/sudoers.d/mini-buildd-sudoers [Errno 13] Permission denied:
u'/etc/sudoers.d/mini-buildd-sudoers'
-- debconf information excluded
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#764617: mini-buildd: Chroot build setup broken (since sbuild-0.63.3)
Package: mini-buildd Version: 1.0.4 Severity: grave Justification: renders package unusable FTR: In sbuild-0.63.3 this bug has been fixed: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=607228 Unfortunately, the workaround in mini-buildd for that bug now actually breaks mini-buildd now the bug is fixed ;). Upcoming release will have the workaround removed, of course, and eventually close this. In the meantime, the workaround to make the obsoleted workaround work again is to install any sbuild 0.63.3. Hth, S -- System Information: Debian Release: jessie/sid APT prefers unstable APT policy: (500, 'unstable'), (500, 'testing'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 3.16-0.bpo.2-amd64 (SMP w/4 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages mini-buildd depends on: ii adduser 3.113+nmu3 ii debconf [debconf-2.0] 1.5.53 ii debootstrap 1.0.63 ii devscripts 2.14.7 ii dpkg-dev1.17.16 ii gnupg 1.4.18-4 ii libjs-jquery1.7.2+dfsg-3.2 ii libjs-sphinxdoc 1.2.3+dfsg-1 ii lintian 2.5.28 ii mini-buildd-common 1.0.4 ii python-cherrypy33.5.0-1 ii python-daemon 1.5.5-1 ii python-django 1.7-2 ii python-django-extensions1.3.10-1 ii python-django-registration 1.0+dfsg-2 ii python-mini-buildd 1.0.4 ii python-pyftpdlib1.2.0-1 pn python:any none ii reprepro4.16.0-1 ii sbuild 0.64.3-2 ii schroot 1.6.10-1+b1 ii sudo1.8.10p3-1 Versions of packages mini-buildd recommends: ii python-apt 0.9.3.10 Versions of packages mini-buildd suggests: pn binfmt-supportnone ii debootstrap 1.0.63 pn haveged none pn lvm2 none pn qemu-user-static none -- Configuration Files: /etc/default/mini-buildd changed [not included] /etc/sudoers.d/mini-buildd-sudoers [Errno 13] Permission denied: u'/etc/sudoers.d/mini-buildd-sudoers' -- debconf information excluded -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#632955: For the record
Hi, last but not least, some clarification on these rc bugs: Unfortunately, both bugs (632955 656746) can't be fixed in 0.8.x, as they are by design -- it does 'it all' on package configuration/installation time, which usually needs human interaction. Furthermore, secret keys are generated which might also just stall if the system lacks entropy. Fortunately, this is all irrelevant for the upcoming 1.0.0* version, now (waiting) in experimental. 0.8.x will not see further updates in Debian; I will eventually provide a special 0.8.x 'PPD' for that for installations that really don't want to upgrade (would become really relevant for wheezy+1, however ;). HtH, Stephan -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#660939: add info
Hi, tagged fixed-in-experimental. ftr, both issues are definitely fixed in 1.0.0, alpha3 (still in NEW, though). HtH, Stephan -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#592592: mini-buildd: sbuild configuration uses old style pgp_options
Package: mini-buildd Severity: grave Justification: renders package unusable Hi, in .sbuildrc, pgp_options used to be just a string; the version in sid/squeeze uses an array. This essentially makes all builds fail. Please replace $pgp_options = -us -k\Mini-Buildd Automatic Signing Key\; by $pgp_options = ['-us', '-k Mini-Buildd Automatic Signing Key']; and update the sbuild depends (as the new variant does not work for older sbuilds). Thx, Stephan -- System Information: Debian Release: squeeze/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: amd64 (x86_64) Kernel: Linux 2.6.32-bpo.5-amd64 (SMP w/2 CPU cores) Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#592599: mini-buildd: mbd-qa-check broken by bash4
Package: mini-buildd Severity: grave Justification: renders package unusable Hi, (at least) the mbd-qa-check relies on error handling behaviour of bash =3. More precisely, a snippet like this --- set -e ( false ) RET=$? --- would just continue with the subshell's retval in variable RET in bash3, but error-exit in bash4 after the sub shell. At least the construct in mbd-qa-check suffers this problem (lines 349ff). This essentially breaks mosts builds (i.e., those with warning in any of the checks). Thx, Stephan -- System Information: Debian Release: squeeze/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: amd64 (x86_64) Kernel: Linux 2.6.32-bpo.5-amd64 (SMP w/2 CPU cores) Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
