Bug#774415: #774415: devscripts: please add the srebuild wrapper for reproducible builds
Curious, was the srebuild the one as featured in the debian-rebuilder-setup[1] repository or the upstream one? I don't think we've faced much build issues on our side... Cheers! -Santiago [1] https://salsa.debian.org/reproducible-builds/debian-rebuilder-setup On Mon, Oct 07, 2019 at 06:03:08PM +, Matt Bearup wrote: > I have to second the issues with srebuild. We invested a lot of time to > utilize this tool in our rebuilds but faced consistent build failures. > The best explanation I could find was that the snapshots referred to in the > .buildinfo files had expired. That's not conclusive (the output wasn't clear > on the cause of failure) nor is expired repo metadata the fault of srebuild > per se. But the issue was nonetheless a blocker. > PBuilder is the most consistent build tool we've seen thus far, will have to > investigate debrebuild as well. > > Matt Bearup > Software Developer – CEH, CISSP, GCUX > Microsoft Azure Compute Linux signature.asc Description: PGP signature
Bug#774415: #774415: devscripts: please add the srebuild wrapper for reproducible builds
Hello Everyone, On Mon, Oct 07, 2019 at 02:49:27PM +0200, Johannes Schauer wrote: > Copious snipping performed here > The srebuild script suffers from many problems (see above). I would advice > against using it in favour of debrebuild. If you want something that works > "most or even half the time" then I think that debrebuild is what you want. > Feel free to ask me if you have any questions about the script. > On the rebuilder side, would this work as a drop-in replacement? how does it handle fetching dependencies from the debian archive and such? Cheers! -Santiago signature.asc Description: PGP signature
Bug#934137: securesystemslib ftbfs in sid
On Mon, Aug 12, 2019 at 02:26:26PM +, Holger Levsen wrote: > On Mon, Aug 12, 2019 at 04:17:46PM +0200, Lukas Puehringer wrote: > > Hooray, thanks! I just applied the same "override_dh_auto_test" patch [1] to > > in-toto, whose tests will also only be available with the next upstream > > release. > > yay! > > > The freshly built package is available on mentors [2]. > > yay! > > > And there are similar build instructions for in-toto, which take into > > account > > that the securesystemslib dependency might be fed to sbuild via > > --extra-package > > [3]. > > this won't work on the buildds, they cannot access packages in NEW. so > we need to wait until securesystemslib made it through... I wonder, in arch we build from git so that the tests are available. Wouldn't that be preferrable on the debian side too? Cheers! -Santiago. signature.asc Description: PGP signature
Bug#873157: diffoscope: Support the new fork of python-progressbar
Package: diffoscope Version: 85 Severity: wishlist Tags: upstream Dear Maintainer, While trying to install/use diffoscope from pip (or the Arch Linux package), I realized that the --progress flag triggers a crash. The reason as to why this happens is that there are two forks of the python-progressbar package available, whith slightly different api's. The one being used by Debian[1] seems to be an abandoned version (without any updates in two years), whereas there exists a more actively-developed alternative[2] (possible a takeover). This issue has also been brought up to the maintainers of python-progressbar, who are evaluating this upstream change[3]. An arch user suggested a fairly minimal patch to fix it[4], and there is an more-elaborate descrption of the API change on the comments of this bug report[5]. It'd be nice if diffoscope was made aware of these versions and possibly choose the right one depending on which one is available. Thanks! -Santiago. [1] https://github.com/niltonvolpato/python-progressbar [2] https://github.com/WoLpH/python-progressbar [3] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=839149 [4] http://codepad.org/oIr6JudF [5] https://bugs.archlinux.org/task/53505 -- System Information: Debian Release: 9.1 APT prefers stable APT policy: (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 4.12.7-coreos (SMP w/8 CPU cores) Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968), LANGUAGE=C (charmap=ANSI_X3.4-1968) Shell: /bin/sh linked to /usr/bin/dash Init: unable to detect Versions of packages diffoscope depends on: ii python33.5.3-1 pn python3-libarchive-c pn python3-magic ii python3-pkg-resources 33.1.1-1 Versions of packages diffoscope recommends: pn acl pn apktool pn binutils-multiarch ii bzip2 1.0.6-8.1 pn caca-utils pn colord pn default-jdk-headless | default-jdk | java-sdk pn enjarify pn fontforge-extras pn fp-utils pn genisoimage pn gettext pn ghc pn ghostscript pn gnupg pn imagemagick pn jsbeautifier pn llvm pn mono-utils pn openssh-client pn pdftk pn poppler-utils pn python3-argcomplete ii python3-debian 0.1.30 pn python3-guestfs pn python3-progressbar pn python3-rpm pn python3-tlsh pn rpm2cpio pn sng pn sqlite3 pn squashfs-tools pn unzip pn xxd | vim-common ii xz-utils 5.2.2-1.2+b1 Versions of packages diffoscope suggests: pn libjs-jquery
