Bug#906747: reprepro does not accept built files on includedsc

On Sat, 25 Aug 2018 13:25:24 +0200 Marc Haber wrote: > severity #906747 normal > thanks > > I now think that this is actually a reprepro issue, and it only applies (...) > My beef against mini-buildd is therefore reduced to the fact that it > once more hides the actual error message in the

Bug#1070111: mini-buildd wishlist: configurable periodic jobs (or: don't keep complete build results for a full year)

Hi Magnus, On Tue, 2024-04-30 at 11:40 +0200, Magnus Holmgren wrote: > Package: mini-buildd > Severity: wishlist > coded. Perhaps you've already planned to add some configurability in the > future, but more specifically I'd like to talk about the "Expire no imminent plans to make cron jobs

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 '/<>' (..) > >

Bug#1052459: mini-buildd: Problems with unnecessarily doubled slashes

Hi Magnus, On Fri, 2023-09-22 at 15:37 +0200, Magnus Holmgren wrote: > Package: mini-buildd > Version: 2.0.7~bpo12+1 > > mini-buildd requires (in Archive.clean) that all archive URLs end in > a slash. > Yet it (always?) adds another slash before 'dists' (e.g. >

Bug#1033519: debootstrap: Fails to bootstrap wheezy (please symlink script as 'archived', like squeeze)

Package: debootstrap Version: 1.0.128+nmu2 Severity: wishlist Dear Maintainer, wheezy is archived, but script (unlike, f.e. squeeze) still links to sid: --- ls -l /usr/share/debootstrap/scripts/wheezy /usr/share/debootstrap/scripts/squeeze lrwxrwxrwx 1 root root 4 Oct 19 00:49

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

Bug#1026215: python3-openssl: Fails using deprecated SSL_CTX_set_ecdh_auto which ultimately has been removed w/ p-cryptography 38

Package: python3-openssl Version: 21.0.0-1 Severity: important Dear Maintainer, since p-cryptography 38 hit unstable, this fails somewhere here File "/usr/lib/python3/dist-packages/OpenSSL/SSL.py", line 674, in __init__ using SSL_CTX_set_ecdh_auto, which is deprecated w/ at least openssl3

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

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

Bug#1007101: libjs-jquery-datatables: jquery.dataTables[.min].js files missing

Package: libjs-jquery-datatables Version: 1.11.5+dfsg-1 Severity: important Dear Maintainer, in 1.11.4+dfsg-1: --- ? dpkg -L libjs-jquery-datatables | grep jquery.dataTables /usr/share/javascript/jquery-datatables/css/jquery.dataTables.css

Bug#998068: debconf values not populated on initial install (like debootstrap) since 1.5.78

Package: debconf Version: 1.5.78 Severity: important Dear Maintainer, on initial install (for example via deboostrap), debconf values are not populated, i.e., debconf-show debconf is empty. Maybe due to fix for #989567, which seems to actually remove postinst for good w/o actually producing

Bug#981213: debrepro: fusermount -u fails in chroots

Rehi, On Wed, 27 Jan 2021 19:29:00 +0100 =?utf-8?q?Stephan_S=C3=BCrken?= < abs...@debian.org> wrote: > Package: devscripts > Version: 2.20.5 > Severity: normal > > Dear Maintainer, > > any chrooted run debrepro fails on cleanup with s.th. like: > --- > rm: cannot remove

Bug#981213: debrepro: fusermount -u fails in chroots

Package: devscripts Version: 2.20.5 Severity: normal Dear Maintainer, any chrooted run debrepro fails on cleanup with s.th. like: --- rm: cannot remove '/tmp/debrepro.WdTfiXpiIP/second/source': Device or resource busy --- This is due to fusermount -u failing w/ --- fusermount: failed to mark

Bug#981043: git-buildpackage: dch: Please support --distribution for snapshots (or at least properly document --distribution)

Package: git-buildpackage Version: 0.9.21 Severity: minor Dear Maintainer, Guido, in snapshot mode, header options --distribution (and --urgency) are deliberately not honored in-code (scripts/dch.py): --- # This must not be done for snapshots or snapshots changelog entries # will not be

Bug#981013: git-buildpackage: dch: Please don't capture stderr on debchange run

(...) > debchange may be non-interactive, showing some warning to stderr end rather "interactive" not "non-interactive"... Sorry ;), S signature.asc Description: This is a digitally signed message part

Bug#981013: git-buildpackage: dch: Please don't capture stderr on debchange run

Package: git-buildpackage Version: 0.9.21 Severity: minor Tags: patch Dear Maintainer, Guido, debchange may be non-interactive, showing some warning to stderr end expecting [RETURN] on stdin to continue. Capturing stderr leads to stopping without showing any clue why or what to do. For example:

Bug#980735: dput-ng: Please add ftps (RFC 4217, not sftp) support

Package: dput-ng Version: 1.31 Severity: wishlist Tags: patch Dear Maintainer(s), this adds a new method "ftps" following RFC 4217 with ftplib.FTP_TLS (py standard library). Patch is in this salsa merge request: https://salsa.debian.org/debian/dput-ng/-/merge_requests/14 Thanks for

Bug#980468: dput: Please add ftps (RFC 4217, not sftp) support

Package: dput Version: 1.1.0 Severity: wishlist Tags: patch Dear Maintainer, Ben, this adds a new method "ftps" following RFC 4217 with ftplib.FTP_TLS (py standard library). Patch is in this salsa merge request: https://salsa.debian.org/debian/dput/-/merge_requests/4 Thanks for considering!

Bug#955277: buster-pu: package mini-buildd/1.0.36

Hi Adam, On Sun, 2020-11-22 at 18:30 +, Adam D. Barratt wrote: > Control: tags -1 -moreinfo +confirmed > > Hi, > > Apologies for having somehow missed your earlier reply. > > On Tue, 2020-04-28 at 08:51 +0200, Stephan Sürken wrote: (...) > Please go ahead. thx, u

Bug#955277: buster-pu: package mini-buildd/1.0.36

cessful builds w/ sbuild >= +0.77) (Fixes: #951641) + + -- Stephan Sürken Tue, 28 Apr 2020 08:18:54 +0200 + mini-buildd (1.0.36) unstable; urgency=medium * [9a29242] source.py: wizards: Update signing keys for unstable + diff -Nru mini-buildd-1.0.36/debian/gbp.conf mini-buildd-1.0.36+deb1

Bug#951641: mini-buildd: MD5 conflict with doc packages when compiling "any" arch

Hi Marc, On Wed, 2020-03-18 at 14:42 +0100, Marc Leeman wrote: (...) > Thanks for the pointer. > > I've applied the patch and restarted the service. I could recompile > openjdk-8 without problem; it seems that this was the problem. great! Fwiw, afaik all packages failing to build (their 'all'

Bug#951641: mini-buildd: MD5 conflict with doc packages when compiling "any" arch

Hi Marc, On Thu, 2020-03-12 at 11:15 +0100, Marc Leeman wrote: > This is the status of the openjdk-8 build: as the log confirms, the > i386 packages got inserted, while the amd64 not due to the md5 > conflict since both are creating the same openjdk-8-source_8u242-b04- > 2~company10+6_all.deb >

Bug#951641: mini-buildd: MD5 conflict with doc packages when compiling "any" arch

Hi Marc, On Fri, 2020-02-21 at 11:54 +0100, Marc Leeman wrote: > > Could it be that there is some config option that is still wreaking > havoc after having been disabled. Fwiw, there is this 'inconvenience' bug: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=838393 So just be sure to

Bug#951641: mini-buildd: MD5 conflict with doc packages when compiling "any" arch

Hi Marc, On Wed, 2020-02-19 at 12:17 +0100, Marc Leeman wrote: (...) > older platforms) and amd64 (current). I've come accross the following > while backporting GStreamer 1.14.4 from buster to stretch. just tried it here with no issues. Ftr, I did a portext to stretch with

Bug#934978: mini-buildd: Does not function behind a NAT router

Hi Daniel, On Fri, 2019-08-23 at 22:07 +0200, Stephan Sürken wrote: > On Mon, 2019-08-19 at 23:06 -0700, Daniel Schepler wrote: > > On Mon, Aug 19, 2019 at 12:25 PM Stephan Sürken (...) > Fwiw, I did all the tests with 1.0.x. I now see that you are testing > 1.1.x ;) -- but the s

Bug#934978: mini-buildd: Does not function behind a NAT router

On Mon, 2019-08-19 at 23:06 -0700, Daniel Schepler wrote: > On Mon, Aug 19, 2019 at 12:25 PM Stephan Sürken > wrote: > > I am not quite getting it ;), I guess I need more information here. > > > > What's the 'Hostname' entry of the 'Daemon' instance? > > localh

Bug#934978: mini-buildd: Does not function behind a NAT router

Hi Daniel, On Sat, 2019-08-17 at 08:53 -0700, Daniel Schepler wrote: > Package: mini-buildd > Version: 1.1.18 > Severity: wishlist > > I think I've gotten my local mini-buildd instance mostly set up. But > now, when I try to upload to it to do a test build, I get a failure > along the lines of:

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

Bug#924077: mini-buildd: sbuild-update has no option --keygen

Hi "itd", On Sat, 2019-03-09 at 12:31 +0100, i...@firemail.cc wrote: > Package: mini-buildd > Version: 1.0.36 > Severity: normal > Tags: upstream > > Dear Maintainer, > > sbuild (>= 0.77.0) no longer supports `sbuild-update` option ` > --keygen`  ups yes - thx for the hint. It's really time

Bug#922614: mini-buildd: Doesn't actually call sbuild with --jobs option

choice here. I did some research ;), and it seems I changed it from --jobs to env back in 2013 due to <=etch compatibility issues: commit 355893eb0202f507246569a0b922e89474f27369 Author: Stephan Sürken Date:   Thu Jan 3 17:02:26 2013 +0100 builder: Use env. DEB_BUILD_OPTIONS='paral

Bug#922675: segfault on dir chroot prepare (in sqlite)

Hi Marc, On Tue, 2019-02-19 at 11:34 +0100, Marc Haber wrote: > Package: mini-buildd > Version: 1.0.36 > Severity: important > > Hi, > > I log in to my mini-buildd instance, start configuring, call up the > Dir > chroots, mark one, click on "prepare". The browser immediately > returns a >

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

Bug#858988: python-cherrypy3: https request error An unexpected TLS packet was recieved

Hi Gerald, On Wed, 29 Mar 2017 12:58:21 +0200 Gerald Hansen wrote: > Package: python-cherrypy3 > Version: 3.5.0-2build1 > Severity: normal >  > Dear Maintainer, >  > I try to use salt-api with cherrypi and ssl encryption. > But the Debian version of cherrypy3

Bug#855321: ui-auto: please deprecate or remove ui-auto-rsign and option to use debrsign

On Tue, 2018-01-02 at 11:48 -0500, Daniel Kahn Gillmor wrote: > The places you mention sound reasonable to me, though. 1.2.10-1 is now underway. Fwiw, relevant change is visible here: https://sourceforge.net/p/ui-auto/ui-auto/ci/b656b4778c8a7b8b7b2212ba43b3f6a2f79ebc73/ (...) > Finally, if you

Bug#886126: mini-buildd: using alt.files as keyring backend is highly impractical

Hi "ydirson", On Tue, 2018-01-02 at 16:09 +0100, ydir...@free.fr wrote: > Package: mini-buildd > Version: 1.0.29 > > With no external keyring software installed, python-keyring defaults > to alt.files, and the impact > on scripting (eg. launching auto-setup for a test) is quite high: > > * have

Bug#855321: ui-auto: please deprecate or remove ui-auto-rsign and option to use debrsign

Hi Daniel, On Thu, 2017-02-16 at 13:54 -0500, Daniel Kahn Gillmor wrote: > Package: ui-auto > Version: 1.2.9 (...) > the debrsign workflow isn't a particularly safe one (see discussion > on > https://bugs.debian.org/855282 and https://bugs.debian.org/855320). > > ui-auto should not encourage

Bug#867592: mini-buildd: "500 Internal Server Error" when trying to add an uploader's gpg pubkey

Hi Frank, On Mon, 2017-09-11 at 16:30 +0200, Frank Doepper wrote: > Am 11.09.17 um 15:09 schrieb Stephan Sürken: > > > commit a37e69c2bc8371b57531f4e65e0b271bc3b20617 (HEAD -> master) > > However, I don't know if or how the other logs/findings you posted > > her

Bug#867592: mini-buildd: "500 Internal Server Error" when trying to add an uploader's gpg pubkey

Hi Frank, On Fri, 2017-09-01 at 17:57 +0200, Frank Doepper wrote: > Am 23.08.17 um 12:06 schrieb Stephan Sürken: > > > If the problem persists, could you enable "debug logging" > > Yeah, I have sent you some backtraces yesterday. actually, there is/was a

Bug#867592: mini-buildd: "500 Internal Server Error" when trying to add an uploader's gpg pubkey

Hi Frank, On Tue, 2017-08-22 at 13:33 +0200, Frank Doepper wrote: > Am 16.08.17 um 17:09 schrieb Stephan Sürken: > > > Just to be clear: We are talking about "Manage Account/Manage > > Profile/Set New Key" via the web interface? > > I'm talking about > http

Bug#867592: mini-buildd: "500 Internal Server Error" when trying to add an uploader's gpg pubkey

On Mon, 2017-08-14 at 18:06 +0200, Frank Doepper wrote: > Am 25.07.17 um 14:16 schrieb Stephan Sürken: > > > thx for testing experimental ;). > > > > However, I could not produce this (with the current master branch). > > > > Could you try if 1.1.4

Bug#867592: mini-buildd: "500 Internal Server Error" when trying to add an uploader's gpg pubkey

Hi Frank, On Fri, 2017-07-07 at 18:09 +0200, Frank Doepper wrote: > Package: mini-buildd > Version: 1.1.3 > Severity: normal > > When trying to add a new uploader's gpg key via web admin, "500 > Internal > Server Error: Sorry, something went wrong" is the result. I would > expect > the key to be

Bug#836193: Improper handling of arch all only package

On Mi, 2017-02-08 at 15:33 +0200, Konstantinos Margaritis wrote: > Στις 08-02-2017, ημέρα Τετ, και ώρα 14:14 +0100, ο/η Stephan Sürken > έγραψε: (...) > > It seems it's just a "correctly failing build" -- please check your > > build log ;) > Argh, hate it w

Bug#836193: Improper handling of arch all only package

Hi Konstantinos, On Mi, 2017-02-08 at 14:27 +0200, Konstantinos Margaritis wrote: > Στις 08-02-2017, ημέρα Τετ, και ώρα 11:51 +0100, ο/η Stephan Sürken (...) > > ) might be helpful, too. > Ok, I stripped all but the debian directory and renamed the relevant > name variables, th

Bug#836193: Improper handling of arch all only package

On Mi, 2017-02-08 at 11:51 +0100, Stephan Sürken wrote: > Hi Konstantinos, (...) > ) might be helpful, too. Also, it would be (easy and) helpful if you can just build the test packages, and report whether test package 'mbd-test-archall' also fails on your setup. Thx!

Bug#836193: Improper handling of arch all only package

Hi Konstantinos, On Di, 2017-02-07 at 16:32 +0200, Konstantinos Margaritis wrote: (...) > I am attaching a sample dsc (I hope you only need the dsc and not the > rest of the files, because it's an internal debian package and I had hmm ic. I fear only a complete Debian Source Package would be

Bug#854480: reprepro && detached upstream signatures

Hi Frank, all, fwiw, a colleague of mine just debugged this (with patch), and added a bug report on reprepro: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=854480 Fwiw2, this feature came in with --- dpkg (1.18.5) unstable; urgency=medium   (...)   * Perl modules: (...) - Allow

Bug#836193: Improper handling of arch all only package

Hi Konstantinos, On Di, 2017-02-07 at 12:57 +0200, Konstantinos Margaritis wrote: > Hello, > > I just wanted to say that I was able to reproduce this bug on a > stretch > based system (mini-buildd 1.0.29), building 2 arches, i386/amd64, > where >  i386 is optional and amd64 builder builds

Bug#849551: spurious "internal error building" related to gpg

Hi Marc, On Fr, 2016-12-30 at 13:57 +0100, Marc Haber wrote: > On Fri, Dec 30, 2016 at 01:26:09PM +0100, Stephan Sürken wrote: (...) > That would be: > > > > Dec 28 13:44:29 spinturn mini_buildd.call (0114): > > WARNING : ? gpg.. (stderr): gpg: can't c

Bug#849551: spurious "internal error building" related to gpg

On Do, 2016-12-29 at 19:48 +0100, Marc Haber wrote: > On Thu, Dec 29, 2016 at 07:40:27PM +0100, Stephan Sürken wrote: > > > > On Do, 2016-12-29 at 18:41 +0100, Marc Haber wrote: > > > > > > i can grep for "0041" to find the complete log for th

Bug#849551: spurious "internal error building" related to gpg

On Do, 2016-12-29 at 18:41 +0100, Marc Haber wrote: (...) > If I have the error message: > > Dec 28 14:35:22 spinturn mini_buildd.builder  (0041): > ERROR   : Internal error building: Call failed with retval 2: 'gpg -- > homedir /var/lib/mini-buildd/.gnupg --display-charset UTF-8

Bug#849544: bind mount for home directory needed if not on root fs

On Mi, 2016-12-28 at 13:13 +0100, Marc Haber wrote: > Package: mini-buildd > Version: 1.0.27 > Severity: normal (...) > My current fix is not a real fix since /etc/schroot/mini-buildd/fstab > is likely to be overwritten with the next mini-buildd update. > > How would a local admin make

Bug#849547: clicking retry on a failed build will result in an immediate reject

On Do, 2016-12-29 at 18:36 +0100, Marc Haber wrote: > On Thu, Dec 29, 2016 at 06:09:25PM +0100, Stephan Sürken wrote: > > > > Could it be you are running with reprepro < 5? (#843402) > No, I pulled the version from experimental. I am out of guesses, then ;). Fwiw, I have

Bug#849551: spurious "internal error building" related to gpg

Hi, On Mi, 2016-12-28 at 14:22 +0100, Marc Haber wrote: (...) > again and uploaded again. This time the build went through just fine. I have previously seen similar behavior too, but not any more for quite some time. I had the impression this was a temporary behavior of some version of the

Bug#849547: clicking retry on a failed build will result in an immediate reject

Hi, On Do, 2016-12-29 at 17:24 +0100, Marc Haber wrote: (...) > > > packages being built correctly with the armhf build failing. > > with armhf being set up as optional arch? > Probably not. It is not really optional, I didn't notice that armhf > was offline. it rather should be; else

Bug#849547: clicking retry on a failed build will result in an immediate reject

Hi Marc, On Mi, 2016-12-28 at 13:35 +0100, Marc Haber wrote: (...) > When I uploaded a package to mini-buildd, I didn't notice that my > armhf builder was being offline. This resulted in the i386 and amd64 > packages being built correctly with the armhf build failing. with armhf being set up as

Bug#843402: Fwd: reprepro_5.0.0-1_amd64.changes ACCEPTED into experimental

Hi Bernhard, On Do, 2016-12-22 at 10:28 +0100, Bernhard R. Link wrote: > I'd appreciate if those invovled could test the version of reprepro > currently in experimental. I plan to upload 5.0.1 to unstable with > some additional smaller things to unstable tomorrow (Friday) evening > (UTC). great!

Bug#827339: Please revert patch for cmd, and fix default pattern

On Di, 2016-11-22 at 11:33 +0100, Patrick Matthäi wrote: (...) > Thanks for your effort! I have just uploaded 1.0.3-3. > > Would you (Stephan) be so kindly and upload it to jessie-bpo, if > there > are no new problems with it? I will be on vacation before it may ent fwiw, I did just port this.

Bug#802689: please consider allowing to switch off lintian for architectures

Hi Marc, On Do, 2015-10-22 at 18:27 +0200, Marc Haber wrote: > Source: mini-buildd > Version: 1.0.7 > Severity: wishlist (...) > Please consider implementing a possibility to say "don't run lintian > on this architecture" or "dont run lintian on builds done by this > builder". fwiw, 1.0.26 now

Bug#843402: reprepro cannot handle .changes files that reference .buildinfo files

On Tue, 22 Nov 2016 19:08:06 +0100 =?utf-8?q?Sl=C3=A1vek_Banko?= wrote: > Dne út 22. listopadu 2016 Stephan Sürken napsal(a): (...) > without "Tracking", buildinfo files are not processed - "reprepro include"  > ignores them. >  > With "Tracking: minimal" (without

Bug#827339: Please revert patch for cmd, and fix default pattern

Hi Patrick, On Di, 2016-11-22 at 11:33 +0100, Patrick Matthäi wrote: (...) > > S > Thanks for your effort! I have just uploaded 1.0.3-3. ok, thx! > Would you (Stephan) be so kindly and upload it to jessie-bpo, if > there > are no new problems with it? I will be on vacation before it may >

Bug#843402: reprepro cannot handle .changes files that reference .buildinfo files

Hi Slavek, On Tue, 22 Nov 2016 00:31:47 +0100 =?utf-8?q?Sl=C3=A1vek_Banko?= wrote: (...) > When I use "reprepro include", I got: (...) > Aborted >  > Buildinfo files are generated by dpkg 1.18.15 (already included in  > Stretch). Tracking is set to: minimal

Bug#843608: mini-buildd: reprepro not recognizing .buildinfo file, causing upload failure

Hi Boyuan! On Di, 2016-11-08 at 22:38 +0800, Boyuan Yang wrote: > 在 2016年11月8日星期二 CST 下午3:31:49，您写道： (...) > The only truth is that mini-buildd with dpkg >= 1.18.11 will stop > working, and  > it should be fixed *somehow* *somewhere* before this bug gets closed. Fwiw, there is now a patch

Bug#843402: reprepro cannot handle .changes files that reference .buildinfo files

Hi Guillem, all, On Fri, 18 Nov 2016 14:21:08 +0100 Guillem Jover wrote: (..) > Ok, Michael Prokop deployed it on jenkins.grml.org and retriggered at > least the dpkg jobs and they seem to work now. I've fixed an inversion > logic error in the previous patch and I'm

Bug#827339: Please revert patch for cmd, and fix default pattern

Hi Patrick, On Mo, 2016-11-21 at 10:12 +0100, Patrick Matthäi wrote: (...) > > S > Ok so adding patch > https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=827339#34 and drop > current patch 01-grep-syntax-error ? sure, that would be my suggestion. For your Debian patch, you should maybe only

Bug#827339: Please revert patch for cmd, and fix default pattern

Hi, On Fr, 2016-11-18 at 17:01 +0100, Patrick Matthäi wrote: > Am 17.11.2016 um 18:52 schrieb Stephan Sürken: > > > > Hi Patrick, > > > > On Do, 2016-11-17 at 15:40 +0100, Patrick Matthäi wrote: > > (...) > > > > > > Then the question is

Bug#827339: Please revert patch for cmd, and fix default pattern

Hi Patrick, On Do, 2016-11-17 at 15:40 +0100, Patrick Matthäi wrote: (...) > Then the question is, why it does not work on Jessies grep? did you overlook my comment? Or are my findings wrong? Thx! S

Bug#827339: Please revert patch for cmd, and fix default pattern

Hi all, On Do, 2016-11-10 at 22:09 +0100, Thomas Liske wrote: (...) > this is a negative lookbehind assertion - quoting from perlre(1): (...) Afaics, the hardcoded default value for err-pattern falsely uses HTML entities. These are needed in the XML config obviously, but not in getXPropStr()

Bug#843608: mini-buildd: reprepro not recognizing .buildinfo file, causing upload failure

Hi Boyuan, On Di, 2016-11-08 at 13:51 +0800, Boyuan Yang wrote: > Source: mini-buildd > Severity: important > Tags: upstream > > Upstream bug #843402. I have tagged that reprepro bug as "affecting mini-buildd". mini-buildd can't do anything about that, really. Do you have any reasons to have

Bug#832643: mini-buildd: Please provide options for repository structure similar to official repo

Hi Boyuan again, On So, 2016-10-23 at 20:50 +0200, Stephan Sürken wrote: > Hi Boyuan, > > On So, 2016-10-23 at 15:53 +0800, Boyuan Yang wrote: > (...) > > > > Several months have passed since last update. Still I think this is > > something (...) > No, I don'

Bug#827339: Please revert patch for cmd, and fix default pattern

Hi Evgeni, Patrick, fwiw (probably this is already worked on), i have fixed up my system by * reverting 01-grep-syntax-error.diff This actually totally breaks things, as this now uses "P" as pattern, practically matching always: -- grep -aiqseP "$AD_HIST_ERRPATTERN" "$AD_HIST_PATH/typescript"

Bug#832643: mini-buildd: Please provide options for repository structure similar to official repo

Hi Boyuan, On So, 2016-10-23 at 15:53 +0800, Boyuan Yang wrote: (...) > Several months have passed since last update. Still I think this is > something (...) > Just as the log says in the previous email (20160731), we would meet > > Package

Bug#838393: PCA on a repository insufficient to update uploaders

Hi Sam, On Mi, 2016-09-21 at 13:05 -0400, Sam Hartman wrote: > So, I can see a couple of easy fixes: > > 1) have _uploaders be a class variable rather than an instance > variable > > or > > 2) store a list ofweakrefs to extant demon objects > > then provide a class method to invalidate all

Bug#809127: links to still-building package log broken

Hi Marc, On So, 2015-12-27 at 13:43 +0100, Marc Haber wrote: (...) > When a package is still building, it shows up directly on the > mini-buildd web page without having to unfold the packager's package > list (by clicking on "Last packages: 100 (show)". > > In this state, build logs for

Bug#831750: mini-buildd: Poor support for reverse proxy when working with apache

Hi Boyuan, On Di, 2016-07-19 at 09:55 +0800, Boyuan Yang wrote: > Source: mini-buildd > Version: 1.0.12 > Severity: normal (...) > However, someone may want to setup using reverse proxy. For example, > let > "https://mywebsite.com/debian/buildd/; proxy_pass to > "http://localhost:8066/;. > For

Bug#836193: Improper handling of arch all only package

Hi Sam! On Mi, 2016-08-31 at 06:50 -0400, Sam Hartman wrote: > package: mini-buildd > version: 1.0.12 > severity: normal > > I uploaded  the source of an arch all package (no arch any in the > resulting build) and got: > > 2016-08-30 22:06:57,398 mini_buildd.packager (0039):(...)

Bug#837537: "Mkdir: file exists" error if any debootstrap file download failed

Hi Boyuan! On Mi, 2016-09-14 at 10:43 +0800, Boyuan Yang wrote: (...) > to download *once*. The dir-chroot creating process should either > fail > immediately or re-run the debootstrap process again with a warning > sent to the logger, > but it just continued as if everything is fine *until*

Bug#838388: debootstrap: Fails to strap squeeze since 1.0.83

Hi Ansgar, On Mi, 2016-09-21 at 00:18 +0200, Ansgar Burchardt wrote: (...) > Ansgar Burchardt writes: (...) > > Only adding -k for newer distributions (i.e. the ones that merged- > > /usr > > supports) should work around the problem. > I pushed a patch implementing this to my debootstrap >

Bug#838393: PCA on a repository insufficient to update uploaders

Hi Sam, On Di, 2016-09-20 at 15:40 -0400, Sam Hartman wrote: (...) > I've found that I need to restart the demon (I used systemctl, > although > perhaps starting/stopping the daemon in the web interface would have > been sufficient). > > > It looks like what's happening is that the cache

Bug#838388: debootstrap: Fails to strap squeeze since 1.0.83

Hi Julien, On Di, 2016-09-20 at 21:09 +0200, Julien Cristau wrote: (...) > > It always exits here with exit code 2, without any further error > > message (not even when using --verbose). > > > There should be a log inside the target directory. ah, sure ;). debootstrap/debootstrap.log says:

Bug#836156: improper handling of source+binary changes triggering binary builds

Hi Sam, On Di, 2016-09-06 at 08:27 -0400, Sam Hartman wrote: (...) > I don't know.  We normally do source only uploads. > Actually, it may be arch all handling.  The package in question only > produced an arch all binary. > So, the most direct thing to test would be a binary+source upload of >

Bug#820699: possible upcoming incompatibility with schroot 1.7

Hi Marc, On Mo, 2016-04-11 at 15:54 +0200, Marc Haber wrote: (...) > So please be advised to check compatiblity with schroot 1.7. thx. I checked, and it's indeed not compatible ;). However, I will not try to fix this right now, rather avoid it for the moment: control: Dep: Avoid schroot >=

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

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

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

Bug#837537: "Mkdir: file exists" error if any debootstrap file download failed

Hi Boyuan, On Mo, 2016-09-12 at 18:08 +0800, Boyuan Yang wrote: > Package: python-mini-buildd > Version: 1.0.18 > Severity: normal > > I upgraded my Debian build machine to sid for latest 1.0.18 and found > it > impossible to create any dir chroots. (...) do I understand you correctly that the

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

Bug#836737: [buildd-tools-devel] Bug#836737: libsbuild-perl: aptitude resolver fails for non-multiarch chroots

On Mo, 2016-09-05 at 13:22 +0200, Johannes Schauer wrote: > Control: tag -1 + pending (...) > > Hoping for review && consideration... > supporting unsupported old releases is no problem if I get patches > which are as > simple and without negative side effects as this one. > > Applied locally

Bug#834329: gpg key handling with sbuild 0.70 broken

Hi Marc, On So, 2016-08-14 at 16:07 +0200, Marc Haber wrote: > Source: mini-buildd > Version: 1.0.14 > Severity: normal (...) > I am not sure whether this is a bug in mini-buildd or in sbuild. > Hence, the "normal" severity. > > Building packages fails starting with the second build of an >

Bug#833340: mini-buildd: please make the build reproducible

Chris, Boyang, On Fr, 2016-08-05 at 17:09 +0200, Stephan Sürken wrote: (...) > > > > > > (Did you see my patch?) > > Really sorry I overlook the last several lines. It is a good > > solution. > hmm thanks ;). However, I already did a patch (actually before the

Bug#833340: mini-buildd: please make the build reproducible

Hi guys, On Mi, 2016-08-03 at 23:46 +0800, Boyuan Yang wrote: > 2016-08-03 23:34 GMT+08:00 Chris Lamb : > > > > I deliberately expand it immediately after command-line parsing to > > avoid this. > > > > (Did you see my patch?) > Really sorry I overlook the last several lines.

Bug#832643: mini-buildd: Please provide options for repository structure similar to official repo

Hi Boyuan, On Do, 2016-07-28 at 09:47 +0800, Boyuan Yang wrote: > Source: mini-buildd > Version: 1.0.14 > Severity: wishlist > > I got a little bit confused when first heard of the CODENAME-ID- > SUITE[-ROLLBACK] distuibution name. That is weird. I understand that > there may > be multiple

Bug#831749: mini-buildd: Unable to build any package due to missing gnupg in chroot environment of sid/stretch

Hi Boyuan, On Di, 2016-07-19 at 09:44 +0800, Boyuan Yang wrote: > Source: mini-buildd > Version: 1.0.12 > Severity: important > Tags: upstream > > On newly deployed mini-buildd, the default chroot environment for > stretch/sid > lacks gpg/gpg2. > As a result, `apt-key` cannot run and causes

Bug#824385: debian/initramfs-tools.bash-completion: Wrong path after 56dfe39 (breaks completion)

Hi Ben, On So, 2016-05-15 at 11:02 +0100, Ben Hutchings wrote: (...) > > (not sure why 'dh_bash-completion' eats this in the 1st place, > > though;): > It actually installs debian/initramfs-tools.bash-completion rather > than > the files listed there.  This is... not very helpful.  It's sort-of

Bug#820692: please document how to activate skip_if_keep_in_debug

Hi Marc, On Mo, 2016-04-11 at 15:18 +0200, Marc Haber wrote: > Package: mini-buildd > Version: 1.0.11 > Severity: wishlist > > Hi, > > changes.py says: > (...) > mini_buildd.misc.skip_if_keep_in_debug(os.remove, f_abs) > > When debugging (which is unfortunately the case way

Bug#808554: Patch

Rehi, On Mo, 2016-02-15 at 18:13 +0100, Stephan Sürken wrote: > Hi Maintainers/Reporter, > > please consider the attached patch, which fixes the bug for me. > > [Not sure if it's correct to fix up the profile like that though, so > please check this.] please use this revised

Bug#808554: Patch

Hi Maintainers/Reporter, please consider the attached patch, which fixes the bug for me. [Not sure if it's correct to fix up the profile like that though, so please check this.] Hth! Stephan From 0842876bfaec827b6b2e7131633eb7c54711d6a0 Mon Sep 17 00:00:00 2001 From:

Bug#673443: Please add option to use btrfs snapshots instead of LVM snapshots [patch]

Hi Katsuhiko, On Mi, 2015-12-16 at 00:18 -1000, Katsuhiko Nishimra wrote: > Tags: patch > > Hi, > > I've wrote a patch to implement this feature and am attaching it. > I haven't find any fault through test deployment, > but would you please review this closely? just a short heads up: Thanks

Bug#785785: mini-buildd: fails to upgrade: “Unable to change process owner ([Errno 1] Operation not permitted)”

Hi Ben, thanks for the additional information... On Mi, 2016-01-20 at 15:10 +1100, Ben Finney wrote: > Control: found -1 mini-buildd/1.0.9 > Control: retitle -1 mini-buildd: fails to upgrade: Unable to change process > owner ([Errno 1] Operation not permitted) ...but I am still puzzled by this

Bug#797592: is aptitude intentionally not installed in build chroots?

Hi Marc, On Mo, 2015-08-31 at 21:09 +0200, Marc Haber wrote: > Source: mini-buildd > Severity: wishlist > > Hi, > > I have just noticed that a build chroot does not have aptitude > installed. If the aptitude resolver is used, this results in aptitude > being installed over and over for every

Bug#806182: Will fix python-django-registration RCs shortly (Was: Re: Request to join DPMT && python-django-registration)

Hi James, On Mi, 2016-01-06 at 07:13 -0600, James Bennett wrote: > Stephan Sürken wrote: > > Let's see if I got this right: > > > > django-registration is actually no longer discontinued, and now lives at > > > > https://github.com/ubernostrum/django-regist

  1   2   3   >