Bug#1102690: A higher version (...) is still installed, no reflashing required

On 2025-04-12, Vagrant Cascadian wrote: > On 2025-04-12, Johannes Schauer Marin Rodrigues wrote: >> Luckily, running flash-kernel manually fixed the issue. But had I not noticed >> that /boot/boot.scr still contained a version of a kernel that I had just >> removed, my s

Bug#1096790: guix: ftbfs with GCC-15

Control: forwarded 1096790 https://issues.guix.gnu.org/77847 On 2025-02-17, Matthias Klose wrote: > g++ -DHAVE_CONFIG_H -I. -I./nix -DLOCALEDIR=\"/usr/share/locale\" -I./nix > -I./nix/libutil -I./nix -I./nix/libstore -Wdate-time -D_FORTIFY_SOURCE=2 > -Wall -std=c++11 -g -O2 > -ffile-prefix-map

Bug#1102690: A higher version (...) is still installed, no reflashing required

On 2025-04-12, Johannes Schauer Marin Rodrigues wrote: > $ apt-cache policy linux-image-arm64 > linux-image-arm64: > Installed: 6.12.19-1+reform20250322T135019Z > Candidate: 6.12.22-1+reform20250411T222458Z ... > $ sudo apt full-upgrade ... > Removing linux-headers-6.12.16-mnt-reform-arm64 > (

Bug#1091979: u-boot-menu: Fails to add fdt or fdtdir entries

On 2025-03-27, Vagrant Cascadian wrote: > On 2025-03-27, Arnaud Ferraris wrote: >> Le 26/03/2025 à 19:36, Adrian Bunk a écrit : >>> On Tue, Mar 11, 2025 at 03:27:04PM -0700, Vagrant Cascadian wrote: >>> >>> This bug needs some fixing soon (in the worst case

Bug#1036521: pygopherd: reproducible-builds: Garbled pygopherd.txt /bin/sh -> dash

hat it is not fresh in my mind... > From be277736b9fc85a7df1d76318e931ae289bc3034 Mon Sep 17 00:00:00 2001 > From: Vagrant Cascadian > Date: Sun, 21 May 2023 14:00:30 -0700 > Subject: [PATCH 2/2] Makefile: Generate pygopherd.txt with utf8. > > --- > Makefile | 2 +- > 1 file changed, 1 insertion(+),

Bug#1070449: linux-image-6.6-rockchip: zz-u-boot-menu postrm script no such file error

On 2024-05-05, John Sullivan wrote: > Package: linux-image-6.6-rockchip > Version: 6.6.16+rockchip-1 > Severity: important > X-Debbugs-Cc: jo...@debian.org > > When trying to do an upgrade on the PineTab 2, I get "cannot open > /usr/share/u-boot-menu/read-config: No such file" when the postrm scri

Bug#1091979: u-boot-menu: Fails to add fdt or fdtdir entries

On 2025-03-27, Arnaud Ferraris wrote: > Le 26/03/2025 à 19:36, Adrian Bunk a écrit : >> On Tue, Mar 11, 2025 at 03:27:04PM -0700, Vagrant Cascadian wrote: >> >> This bug needs some fixing soon (in the worst case a partial revert to >> the bookworm code), or the pa

Bug#1050968: ITP: rkbin -- Pre-built Rockchip bootloader firmware binaries (for embedded targets)

On 2023-08-31, Christopher Obbard wrote: > Package name: rkbin > Version : 0.0.0~git20230726.b4558da > Upstream Contact: Kever Yang > URL : https://github.com/rockchip-linux/rkbin > License : Copyright © 2017-2023，Rockchip Electronics Co., > Ltd. All rig

Bug#1091979: u-boot-menu: Fails to add fdt or fdtdir entries

On 2025-03-11, Vagrant Cascadian wrote: > On 2025-03-03, Vagrant Cascadian wrote: >> Looping Arnaud into the conversation, as I suspect the patches submitted >> were touching this code quite a bit: >> >> 51d120d549e5b21a19ce659c7bef578c86ed9636 Allow to automatically syn

Bug#1091979: u-boot-menu: Fails to add fdt or fdtdir entries

Control: Severity 1091979 serious Control: tags 1091979 confirmed On 2025-03-03, Vagrant Cascadian wrote: > Looping Arnaud into the conversation, as I suspect the patches submitted > were touching this code quite a bit: > > 51d120d549e5b21a19ce659c7bef578c86ed9636 Allow to automatical

Bug#1062189: simple-cdd issues

... Anyways... On 2025-03-05, Vagrant Cascadian wrote: > 在 2025/3/5 04:27, Robert Schwebel 写道: >> first of all, thanks for all of your work on build-simple-cdd, I use it >> for some years now to build fully automated boot images for my home- and >> club machines so far, and i

Bug#1062189: simple-cdd issues

Hi, 在 2025/3/5 04:27, Robert Schwebel 写道: > Hi Vagrant, > > first of all, thanks for all of your work on build-simple-cdd, I use it > for some years now to build fully automated boot images for my home- and > club machines so far, and it really made my life much easier! > > Recently I run into s

Bug#1091979: u-boot-menu: Fails to add fdt or fdtdir entries

Looping Arnaud into the conversation, as I suspect the patches submitted were touching this code quite a bit: 51d120d549e5b21a19ce659c7bef578c86ed9636 Allow to automatically sync DTBs when /boot is on a separate partition (Closes: #1025956) 96a866bc886f118de9286a00587b2e1fcf263105 read-config: ma

Bug#1068795: pympress: please make the build reproducible

With the two additional patches applied and the original patch submitted by Chris, I think pympress should build reproducibly! live well, vagrant From 9d0ea933d092b674903ce1b9c2e95e35753b7274 Mon Sep 17 00:00:00 2001 From: Vagrant Cascadian Date: Fri, 24 Jan 2025 14:43:00 -0800 Subject: [PATCH 1

Bug#1093289: guix: Remove systemd dependency

On 2025-01-17, Bardot Jerome wrote: > I not using systemd in my current system and when I want to install it it lead > to the following situation : ... > Installing: > guix > > Installing dependencies: > guile-3.0guile-bytestructures guile-git guile-json guile-sqlite3 > guile-zlib l

Bug#1008573: Bug#1032907: GnuPG ssh-agent emulation smartcard issues when connecting to server running newer OpenSSH

On 2025-01-11, Vagrant Cascadian wrote: > On 2025-01-11, Vagrant Cascadian wrote: >> On 2023-04-06, John Scott wrote: >>> It seems bugs #998728, 1008573, and #1032907 are all the same. Perhaps >>> the maintainers would like to merge them. >>> >>> Than

Bug#1008573: Bug#1032907: GnuPG ssh-agent emulation smartcard issues when connecting to server running newer OpenSSH

On 2023-04-06, John Scott wrote: > It seems bugs #998728, 1008573, and #1032907 are all the same. Perhaps > the maintainers would like to merge them. > > Thanks for your workaround, Vagrant; I found that adding > KexAlgorithms -sntrup761x25519-sha...@openssh.com > to my ~/.ssh/config allows m

Bug#1008573: Bug#1032907: GnuPG ssh-agent emulation smartcard issues when connecting to server running newer OpenSSH

On 2025-01-11, Vagrant Cascadian wrote: > On 2023-04-06, John Scott wrote: >> It seems bugs #998728, 1008573, and #1032907 are all the same. Perhaps >> the maintainers would like to merge them. >> >> Thanks for your workaround, Vagrant; I found that adding >>

Bug#1091147: arm-trusted-firmware: FTBFS on arm64: ccsOcV8D.s: Error: 1 warning, treating warnings as errors

Control: fixed 1091147 2.10.10+dfsg-1 Control: fixed 1091147 2.12.0+dfsg-1 On 2024-12-22, Lucas Nussbaum wrote: >> -MT /<>/build/g12a/debug/libc/setjmp.o -MP -c >> lib/libc/aarch64/setjmp.S -o /<>/build/g12a/debug/libc/setjmp.o >> lib/libc/aarch64/setjmp.S: Assembler messages: >> lib/libc/aarch64

Bug#1091147: arm-trusted-firmware: FTBFS on arm64: ccsOcV8D.s: Error: 1 warning, treating warnings as errors

On 2025-01-05, Matthias Klose wrote: > On 05.01.25 07:03, Vagrant Cascadian wrote: >> Not sure if this is a bug or intentional change in binutils... > > please recheck with the most recent version in unstable. I have done many builds over the course of the last few day

Bug#1091147: arm-trusted-firmware: FTBFS on arm64: ccsOcV8D.s: Error: 1 warning, treating warnings as errors

On 2025-01-04, Vagrant Cascadian wrote: > On 2024-12-22, Lucas Nussbaum wrote: >>> lib/libc/aarch64/setjmp.S: Assembler messages: >>> lib/libc/aarch64/setjmp.S:46: Warning: entity size for SHF_MERGE / >>> SHF_STRINGS not specified >>> /tmp/ccsOcV8D.s: Error:

Bug#1091147: arm-trusted-firmware: FTBFS on arm64: ccsOcV8D.s: Error: 1 warning, treating warnings as errors

On 2024-12-22, Lucas Nussbaum wrote: >> lib/libc/aarch64/setjmp.S: Assembler messages: >> lib/libc/aarch64/setjmp.S:46: Warning: entity size for SHF_MERGE / >> SHF_STRINGS not specified >> /tmp/ccsOcV8D.s: Error: 1 warning, treating warnings as errors >> make[2]: *** [Makefile:1496: >> /<>/build/

Bug#1091169: sbuild unshare mode unhappy about symlink'd tarballs

On 2024-12-30, Johannes Schauer Marin Rodrigues wrote: > I found a different solution. I was wondering how GNU tar does it and perused > its source code a bit. And then I just copied their solution. :) > > If you like, can you try this patch: > > --- /usr/share/perl5/Sbuild/ChrootUnshare.pm > +++ /

Bug#1091118: device-tree-compiler: FTBFS: libfdt_wrap.c:5599:17: error: too few arguments to function ‘SWIG_Python_AppendOutput’

Control: tags 1091118 +pending On 2024-12-23, Florian Ernst wrote: > On Sun, Dec 22, 2024 at 05:44:11PM +0100, Lucas Nussbaum wrote: >> > [...] >> > /<>/./pylibfdt/libfdt_wrap.c: In function >> > ‘_wrap_fdt_next_node’: >> > /<>/./pylibfdt/libfdt_wrap.c:5599:17: error: too few >> > arguments to f

Bug#1038845: reprotest: transition from /etc/timezone to /etc/localtime

Control: severity 1038845 important On 2023-06-21, bl...@debian.org wrote: > reprotest is currently referencing /etc/timezone without support for > /etc/localtime. /etc/timezone is a legacy interface that is Debian > specific. The cross-distro standard /etc/localtime (as a symlink to > the appropr

Bug#1076042: [PATCH aerc v2] send: avoid leaking bcc addresses to everyone

On 2024-12-20, Diederik de Haas wrote: > On Wed Dec 18, 2024 at 12:02 PM CET, Robin Jarry wrote: >> The following vulnerabilities were published for arm-trusted-firmware. >> >> CVE-2024-6563[0]: >> | Buffer Copy without Checking Size of Input ('Classic Buffer >> | Overflow') vulnerability in Renesa

Bug#1089201: debrebuild: Extra zero bytes added to .dynstr when rebuilding CMake projects

On 2024-12-07, Gioele Barabucci wrote: > On 07/12/24 06:01, Vagrant Cascadian wrote: >> On 2024-12-07, Gioele Barabucci wrote: >>> the libraries and executables of many cmake-based packages gain extra >>> zero bytes in their .dynstr ELF section when rebuilt. (This accoun

Bug#1089201: debrebuild: Extra zero bytes added to .dynstr when rebuilding CMake projects

On 2024-12-07, Gioele Barabucci wrote: > the libraries and executables of many cmake-based packages gain extra > zero bytes in their .dynstr ELF section when rebuilt. (This accounts for > about 15% of the failed rebuilds.) > > From :

Bug#1069390: fixed in guile-gnutls 4.0.0-2

On 2024-09-11, Debian Bug Tracking System wrote: > guile-gnutls (4.0.0-2) experimental; urgency=low > . >* Re-run cme update dpkg-copyright, now that #1052168 is fixed. >* Test suggested fix for FTBFS by Natanael Copa. Closes: #1069390 Any chance this could get uploaded to unstable soon?

Bug#1085097: python-roborock: please make the build reproducible

user reproducible-bui...@lists.alioth.debian.org usertags +randomness -timestamps thanks On 2024-10-14, Chris Lamb wrote: > Whilst working on the Reproducible Builds effort [0], we noticed that > python-roborock could not be built reproducibly. > > This is because most/every documentation page emb

Bug#1078871: installer: reserve first 16 MiB space in default recipes for ARM devices?

On 2024-10-25, Pascal Hambourg wrote: > On 24/10/2024 at 22:04, Diederik de Haas wrote: >> On Thu Oct 24, 2024 at 9:08 PM CEST, Holger Wansing wrote: >>> >>> here you have a device|installation, which has the legacy_boot flag >>> installed, but it did not work|boot despite of this. And you changed

Bug#991928: grub2: reproducible builds: embeds different strings depending on (obscure) locales

On 2024-10-19, James Addison wrote: > On Thu, 05 Aug 2021 15:11:02 -0700, Vagrant wrote: >> Some locales (e.g. potentially obscure locales used by reprotest) may >> cause sort order issues in embedded strings in some of the grub-*.bin >> binaries. > > I'm not 100% confident, but I believe that this

Bug#1084263: guile-git: FTBFS: make[4]: *** [Makefile:1130: tests/proxy.log] Segmentation fault

On 2024-10-07, Santiago Vila wrote: > During a rebuild of all packages in unstable, your package failed to build: ... > ;;; In procedure load-thunk-from-memory: incompatible bytecode version > ;;; WARNING: loading compiled file > /usr/lib/x86_64-linux-gnu/guile/3.0/site-ccache/bytestructures/guile

Bug#1081867: guile-ssh: FTBFS: ../../../../libguile-ssh/session-func.c:237:11: error: two or more data types in declaration specifiers

Control: tags 1081867 pending On 2024-09-15, Vagrant Cascadian wrote: > Control: forwarded 1081867 > https://github.com/artyom-poptsov/guile-ssh/issues/42 > > On 2024-09-15, Santiago Vila wrote: >> During a rebuild of all packages in unstable, your package failed to build

Bug#1082358: unreproducible timestamp in man pages

On 2024-09-20, Johannes Schauer Marin Rodrigues wrote: > │ │ ├── data.tar.xz > │ │ │ ├── data.tar > │ │ │ │ ├── ./usr/share/man/man1/buildd-abort.1.gz > │ │ │ │ │ ├── buildd-abort.1 > │ │ │ │ │ │ @@ -21,15 +21,15 @@ > │ │ │ │ │ │ .ds SCHROOT_SYSCONF_DIR /etc/schroot > │ │ │ │ │ │ .ds BUILDD_CONF

Bug#1081867: guile-ssh: FTBFS: ../../../../libguile-ssh/session-func.c:237:11: error: two or more data types in declaration specifiers

Control: forwarded 1081867 https://github.com/artyom-poptsov/guile-ssh/issues/42 On 2024-09-15, Santiago Vila wrote: > During a rebuild of all packages in unstable, your package failed to build: ... > In file included from /usr/include/libssh/callbacks.h:30, > from ../../../../li

Bug#1058905: QEMU: why not use package opensbi as dependency?

On 2024-09-10, Heinrich Schuchardt wrote: > On 9/10/24 22:25, Vagrant Cascadian wrote: >> Well, I was holding it wrong! >> >> I pushed a commit that appears to work: >> >>https://salsa.debian.org/opensbi-team/opensbi/-/commit/ >> f3a37b121cb581ac4

Bug#1081078: guix: FTBFS: FAIL: tests/store.scm - export/import several paths

Control: reassign 1081078 guile-gcrypt Control: affects 1081078 guix > On 2024-09-08, Santiago Vila wrote: >> FAIL: tests/nar.scm - restore-file-set (signed, valid) >> FAIL: tests/nar.scm - restore-file-set with directories (signed, valid) >> FAIL: tests/nar.scm - restore-file-set (corrupt) ... >>

Bug#1058905: QEMU: why not use package opensbi as dependency?

On 2024-09-10, Vagrant Cascadian wrote: > On 2024-08-27, Heinrich Schuchardt wrote: >> As a first step let us add a 32bit OpenSBI to our opensbi package as >> /usr/lib/riscv32-linux-gnu/opensbi/generic/fw_*. Debian's >> riscv64-linux-gnu-gcc can build the

Bug#1058905: QEMU: why not use package opensbi as dependency?

On 2024-08-27, Heinrich Schuchardt wrote: > As a first step let us add a 32bit OpenSBI to our opensbi package as > /usr/lib/riscv32-linux-gnu/opensbi/generic/fw_*. Debian's > riscv64-linux-gnu-gcc can build the 32bit OpenSBI when setting > PLATFORM_RISCV_XLEN=32. I would be happy to apply a pat

Bug#1081025: epoptes: implicit dependency on removed python3-distutils

Control: forwarded 1081025 https://github.com/epoptes/epoptes/issues/193 On 2024-09-06, Vagrant Cascadian wrote: > Running epoptes on debian trixie results in: > > $ epoptes > Traceback (most recent call last): > File "/usr/bin/epoptes", line 20, in >

Bug#1081025: epoptes: implicit dependency on removed python3-distutils

Package: epoptes Version: 23.08-1 Severity: serious X-Debbugs-Cc: vagr...@debian.org Running epoptes on debian trixie results in: $ epoptes Traceback (most recent call last): File "/usr/bin/epoptes", line 20, in from epoptes.ui import gui File "/usr/lib/python3/dist-packages/ep

Bug#1058905: QEMU: why not use package opensbi as dependency?

On 2023-12-18, Michael Tokarev wrote: > If we're to go this route, will ask opensbi maintainer(s) to create symlinks > to > opensbi firmware in /usr/share/qemu/ directory. This will involve > Break/Replace > of the old qemu-system-data package. I could do that with all the Breaks/Replaces dance

Bug#1079192: ModuleNotFoundError: No module named 'jaraco'

Control: affects 1079175 reprotest On 2024-08-21, Johannes Schauer Marin Rodrigues wrote: > reprotest failed on salsaci: > > https://salsa.debian.org/reform-team/reform-handbook/-/jobs/6157681 > > last lines from the log: > > Traceback (most recent call last): > File "/usr/bin/reprotest", line 3

Bug#1078849: jenkins.debian.org: diffoscope failure results in packages being marked unreproducible

On 2024-08-16, Vagrant Cascadian wrote: > Apparently, diffoscope has issues that both cause it to fail to build, > but more importantly for jenkins, fails to actually execute in a sid > environment... leading to all packages that successfully build to be > marked as unreproducible,

Bug#1078849: jenkins.debian.org: diffoscope failure results in packages being marked unreproducible

Package: jenkins.debian.org Severity: important X-Debbugs-Cc: vagr...@reproducible-builds.org Apparently, diffoscope has issues that both cause it to fail to build, but more importantly for jenkins, fails to actually execute in a sid environment... leading to all packages that successfully build t

Bug#1041359: missing daemonize causes failed to connect to `/var/guix/daemon-socket/socket'

On 2024-06-09, Johannes Schauer Marin Rodrigues wrote: > On Mon, 17 Jul 2023 16:25:58 -0700 Vagrant Cascadian > wrote: >> On 2023-07-18, Simon Josefsson wrote: >> > Hi. I was trying to build guile-gnutls via guix in a debian12 >> > container, and the sequence below

Bug#1078268: pyfai: please make the package build reproducible

user reproducible-bui...@lists.alioth.debian.org usertags 1064748 +randomness -buildpath thanks On 2024-08-09, James Addison wrote: > Usertags: buildpath cpu ... > The first cause of non-determinism is the use of temporary directory paths by > the meson-python build process; the resulting paths ar

Bug#970278: marked as done (smartlist: please make the build reproducible)

On 2024-08-07, Santiago Vila wrote: > El 6/8/24 a las 23:52, Vagrant Cascadian escribió: >> Well, I was able to reproduce a difference running one build with an >> arm64 kernel one with an armhf kernel, but have not identified exactly >> what triggers the difference... >

Bug#1078081: reprotest: Can't change modification date when invoked against packaging directory (instead of .dsc)

On 2024-08-06, Evangelos Ribeiro Tzaras wrote: > while running > $ reprotest . > > I've run into the following type of failure independent of the package > I'm trying to test: > > > dpkg-source: info: utilisation de la liste de patchs de > debian/patches/series > dpkg-source: erreur: impossible de

Bug#970278: marked as done (smartlist: please make the build reproducible)

On 2024-08-06, Vagrant Cascadian wrote: >> My hunch is differing kernel, as some of the armhf builds run with an >> arm64 kernel and some with a regular armhf kernel... I will try to do >> some more involved tests to verify if that is the issue. > > Well, I was able t

Bug#970278: marked as done (smartlist: please make the build reproducible)

On 2024-08-05, Vagrant Cascadian wrote: > On 2024-08-05, Chris Lamb wrote: >> Santiago Vila wrote: >> >>>> smartlist looks reproducible now >>> >>> Only on amd64, arm64 and i386. >> >> Ah, I didn't spot that. Unfortunately, I don&

Bug#970278: marked as done (smartlist: please make the build reproducible)

On 2024-08-05, Chris Lamb wrote: > Santiago Vila wrote: > >>> smartlist looks reproducible now >> >> Only on amd64, arm64 and i386. > > Ah, I didn't spot that. Unfortunately, I don't have armhf hardware to > hand, but perhaps Vagrant can help narrow this down a little. I was not able to reproduce

Bug#1077625: default.preseed breaks D-I's Manual disk partitioning

On 2024-07-31, Dmitry Baryshkov wrote: > On Tue, 30 Jul 2024 at 23:07, Vagrant Cascadian wrote: >> >> Control: tags 1077625 wontfix >> >> On 2024-07-30, Dmitry Baryshkov wrote: >> > It looks like the defaults present in the simple-cdd packages make &g

Bug#1077625: default.preseed breaks D-I's Manual disk partitioning

Control: tags 1077625 wontfix On 2024-07-30, Dmitry Baryshkov wrote: > It looks like the defaults present in the simple-cdd packages make > generated images fail manual disk partitioning (if I select Manual, > partman returns immediately). After commenting the `d-i > partman/choose_partition` pres

Bug#1074431: arm-trusted-firmware: CVE-2024-6287 CVE-2024-6285

Control: notfound 1074431 2.4+dfsg-2 Control: notfound 1074431 2.8.0+dfsg-1 Control: found 1074431 2.9.0+dfsg-1 On 2024-06-28, Moritz Mühlenhoff wrote: > The following vulnerabilities were published for arm-trusted-firmware. > > CVE-2024-6287[0]: > | Incorrect Calculation vulnerability in Renesas

Bug#1075593: u-boot: ftbfs with GCC-14

Control: tag 1075593 moreinfo On 2024-07-03, Matthias Klose wrote: > The full build log can be found at: > http://qa-logs.debian.net/2024/07/01/u-boot_2024.01+dfsg-5_unstable_gccexp.log > The last lines of the build log are at the end of this report. Seems like the build dependencies failed to in

Bug#963600: critcl: please make the teapot.txt files reproducible

On 2023-01-10, Chris Lamb wrote: >> critcl: please make the teapot.txt files reproducible > > My previous patch no longer makes this package reproducible; there is > an additional variation within: > > /usr/lib/tcltk/x86_64-linux-gnu/critcl_callback1/linux-x86_64/callback.so I tracked down the o

Bug#963688: neovim-qt: please make the build reproducible

On 2020-06-25, Chris Lamb wrote: > This is because it embeds the CFLAGS (via CMAKE_CXX_FLAGS) in an > "About" dialogue, and this environment variable contains the build > path via -ffile-prefix-map etc. This is still relevent, although tests.reproducible-builds.org no longer tests varied build pat

Bug#961942: mono: mono-source: Embeds time, user, group, etc. in mono-source.tar.xz

Control: severity 961942 normal On 2024-03-31, James Addison wrote: > Currently, Debian's buildd and also the Reproducible Builds team's testing > infrastructure[1] both use a fixed build path when building binary packages. > > This means that your package will pass current reproducibility tests;

Bug#1072172: ltsp-server: ltsp-build-client fails

Control: fixed 1072172 19.10-1 On 2024-05-29, Vagrant Cascadian wrote: > Version: 19.08-1 ... > Marking as done in the version that switched to the new-style LTSP. Actually, the first version actually uploaded to debian was 19.10-1, marking appropriately. live well, vagrant signatu

Bug#1072172: ltsp-server: ltsp-build-client fails

On 2024-05-29, Jim Mintha wrote: > Package: ltsp-server > Version: 5.18.12-3 > Severity: normal > > After installing the ltsp-server (and -standalone) packages I ran: > ltsp-build-client. > First time it failed with: ltsp-server, ltsp-build-client, and all ltsp 5.x components were last present

Bug#1044559: guile-lzlib: Fails to build source after successful build

Control: tag 1044559 pending On 2023-08-13, Lucas Nussbaum wrote: > This package fails to build a source package after a successful build > (dpkg-buildpackage ; dpkg-buildpackage -S). ... >> dpkg-source -b . >> dpkg-source: error: unwanted binary file: debian/build/guile-3.0/lzlib.go >> dpkg-sour

Bug#1070235: Guix fails to pull channel with SSL error

On 2024-05-02, Tomas Volf wrote: > Package: guix > Version: 1.4.0-3 > > When I invoke `guix pull' against my channel, it fails with a SSL error: > > # /usr/bin/guix pull --url=https://git.wolfsden.cz/.git/guix > Updating channel 'guix' from Git repository at > 'https://git.wolfsden.cz/.git

Bug#1021470: xsok: reproducible-builds: build path embedded in /usr/games/xsok

On 2024-05-02, Petter Reinholdtsen wrote: > [Vagrant Cascadian] >> Still appears to be an issue, though tests.reproducible-builds.org is no >> longer testing build path variations. Downgrading the severity >> accordingly. > > Hm, then I do not understand the fix. As far

Bug#1021470: xsok: reproducible-builds: build path embedded in /usr/games/xsok

Control: found 1021470 1.02-20 Control: severity 1021470 minor On 2024-05-01, Debian Bug Tracking System wrote: > From: Petter Reinholdtsen > Subject: Accepted xsok 1.02-20 (source) into unstable ... > As far as I can tell, the latest changes to the package build system > made the build reproduci

Bug#1069262: bookworm-pu: package u-boot/2023.01+dfsg-2+deb12u1

Package: release.debian.org Severity: normal Tags: bookworm User: release.debian@packages.debian.org Usertags: pu X-Debbugs-Cc: u-b...@packages.debian.org, vagr...@debian.org Control: affects -1 + src:u-boot [ Reason ] Fixes the timer clock used by various "orion" based platforms, such as She

Bug#1068890: diffoscope: --hard-timeout option

On 2024-04-16, Chris Lamb wrote: > However, I think this first iteration of --hard-timeout time has a few > things that would need ironing out first, and potentially make it not > worth implementing: > > (1) You suggest it should start again with "--max-container-depth 3", > but it would surely nee

Bug#1038845: reprotest: transition from /etc/timezone to /etc/localtime

Control: block 1038845 by 1001250 On 2023-06-21, bl...@debian.org wrote: > reprotest is currently referencing /etc/timezone without support for > /etc/localtime. /etc/timezone is a legacy interface that is Debian > specific. The cross-distro standard /etc/localtime (as a symlink to > the appropria

Bug#1068853: reprotest: SyntaxWarning: invalid escape sequence '\;'

On 2024-04-12, Fay Stegerman wrote: > * Vagrant Cascadian [2024-04-12 19:29]: >> On 2024-04-12, Holger Levsen wrote: >> > when installing reprotest 0.7.27: >> > >> > SyntaxWarning: invalid escape sequence '\;' >> > Setting up reprotest (0.

Bug#1068853: reprotest: SyntaxWarning: invalid escape sequence '\;'

On 2024-04-12, Holger Levsen wrote: > when installing reprotest 0.7.27: > > SyntaxWarning: invalid escape sequence '\;' > Setting up reprotest (0.7.27) ... > /usr/lib/python3/dist-packages/reprotest/__init__.py:360: SyntaxWarning: > invalid escape sequence '\;' > run_or_tee(['sh', '-ec', 'find %

Bug#1061137: Doesn't work on SheevaPlug

On 2024-04-12, Martin Michlmayr wrote: > * Vagrant Cascadian [2024-01-18 20:07]: >> > So we need a stable update with this change. >> >> Thanks everyone! >> >> This is a pretty trivial fix, so including in the next bookworm/stable >> point release sh

Bug#1034311: reprotest: make it easier to compare against an existing build (eg from ftp.d.o)

On 2024-03-08, Vagrant Cascadian wrote: > On 2023-04-12, Holger Levsen wrote: >> i guess reprotest maybe should grow an option to do >> --control-build /path/to/packages/ >> --vary=build_path=/use/this/build/path ... >>to make it

Bug#847805: reprotest: document/support simple reproducibility test with sbuild

On 2016-12-11, Sean Whitton wrote: > On Sun, Dec 11, 2016 at 03:12:57PM -0700, Sean Whitton wrote: >> I have sbuild properly set up on my machine, and I want to use it to >> test package reproducibility. Something like this, where PWD is an >> unpacked source package: >> >> 1) sbuild >> 2) record

Bug#1068483: Bug#882511: dpkg-buildpackage: should allow caller to force inclusion of source in buildinfo

On 2024-04-09, Guillem Jover wrote: > I've now finished the change I had in that branch, which implements > support so that dpkg-buildpackage can be passed a .dsc or a source-dir, > and in the former will first extract it, and for both then it will > change directory to the source tree. If it got p

Bug#962021: forwarded upstream

Control: fixed 962021 10.0.1-1 On 2022-04-19, Vagrant Cascadian wrote: > On 2020-07-04, Bernhard M. Wiedemann wrote: >> https://gitlab.com/graphviz/graphviz/-/merge_requests/1454 >> was easy, because I had the forked repo still around > > This was merged upstream: > &

Bug#1067952: mes: FTBFS on armhf

Control: forwarded 1067952 https://lists.gnu.org/archive/html/bug-mes/2024-01/msg8.html On 2024-03-29, Kentaro HAYASHI wrote: > mes 0.26-1 fails to build on armhf. > > FYI: > > https://buildd.debian.org/status/fetch.php?pkg=mes&arch=armhf&ver=0.26-1&stamp=1704511792&raw=0 Yeah, forwarded thi

Bug#1067850: src:kget: possible Salsa-CI reprotest misconfiguration.

On 2024-03-27, James Addison wrote: > I'd recommend removing the SALSA_CI_REPROTEST_ARGS line entirely -- which > in isolation could cause Salsa-CI reprotest to fail, due to a build-path > bug reported in #1003914 -- but also then applying the patch from that > bugreport to confirm and solve the pr

Bug#1067098: mpl-sphinx-theme: please make the build reproducible

On 2024-03-27, Andreas Tille wrote: > sorry about your work was lost. I confirm the new upstream > version in Git contains the patch. Unfortunately it needs > new dependencies. If it might help you I could upload your > NMU again. Not urgent, glad to see it is pending again! live well, vagra

Bug#1064059: U-Boot: secure boot support

On 2024-02-16, Heinrich Schuchardt wrote: > debian/patches/qemu/efi-secure-boot.patch is not a good approach to > enabling secure boot with U-Boot. Variables entered via the command line > containing the security database will be stored on file but will not be > loaded into U-Boot on the next bo

Bug#1067242: dh-builtusing: Broken "Built-Using" field with architecture-specific invocations

On 2024-03-24, nicolas.bouleng...@free.fr wrote: > Hello. > I failed to reproduce the issue on a porterbox. > > On arm64: > # dpkg-source -x u-boot_2024.01+dfsg-3.dsc > # cd u-boot_2024.01+dfsg > # patch -p1 < ../b8d394100d6f858c0e80786f7087f96c11d698c3.diff > # DEB_BUILD_PROFILES='pkg.uboot.notool

Bug#1051098: suggestion: dh-builtusing may simplify the packaging

Control: tags 1051098 - patch On 2024-03-21, Vagrant Cascadian wrote: > On 2024-03-21, Nicolas Boulenguez wrote: >>> Also filed a bug on dh-builtusing about this: >>> >>> https://bugs.debian.org/1067242 >>> >>> I look forward to an improved dh-

Bug#1067242: dh-builtusing: Broken "Built-Using" field with architecture-specific invocations

Control: found 1067242 0.0.6 I daresay 0.0.6 is even worse, it now fails to build u-boot on both arm64 (which should have dh-builtusing variables defined) and armhf (which does not have any dh-builtusing variables defined). arm64.build:dpkg-gencontrol: warning: Built-Using field of package u-boo

Bug#1066113: guix: CVE-2024-27297

Control: severity 1066113 serious On 2024-03-16, Vagrant Cascadian wrote: > On 2024-03-15, Salvatore Bonaccorso wrote: >> On Fri, Mar 15, 2024 at 11:22:52AM -0700, Vagrant Cascadian wrote: >>> On 2024-03-13, Vagrant Cascadian wrote: >>> > On 2024-03-12, Vagrant Casc

Bug#1064748: guix: FTBFS: In procedure canonicalize-path: No such file or directory

Control: fixed 1064748 1.4.0-6 Marking this as fixed in 1.4.0-6, although strictly speaking, this is only worked around by disabling the tests, so the bug should remain open. live well, vagrant signature.asc Description: PGP signature

Bug#1051098: suggestion: dh-builtusing may simplify the packaging

Control: tags 1051098 +patch On 2024-03-21, Nicolas Boulenguez wrote: >> Also filed a bug on dh-builtusing about this: >> >> https://bugs.debian.org/1067242 >> >> I look forward to an improved dh-builtusing and patch for u-boot! :) > > Thanks for reporting. > > Dh-builtusing/0.0.6 adds a regre

Bug#1051098: suggestion: dh-builtusing may simplify the packaging

Control: reopen 1051098 Control: tags 1051098 -patch On 2024-03-19, Vagrant Cascadian wrote: > On 2024-02-29, Nicolas Boulenguez wrote: >> diff --git a/debian/control b/debian/control >> index 7a6bbc31cc..c6aec92cf6 100644 >> --- a/debian/control >> +++ b/debian/

Bug#1067242: dh-builtusing: Broken "Built-Using" field with architecture-specific invocations

Package: dh-builtusing Version: 0.0.5 Severity: normal Control: affects -1 u-boot X-Debbugs-Cc: vagr...@debian.org u-boot recently switched to dh-builtusing, but it fails with architecture-specific Built-Using entries in packages that do not have the same Built-Using dependencies across architectu

Bug#1051098: suggestion: dh-builtusing may simplify the packaging

On 2024-02-29, Nicolas Boulenguez wrote: > From 27ec150b506234e1a3e24688ed400627133ab5e2 Mon Sep 17 00:00:00 2001 > From: Nicolas Boulenguez > Date: Sat, 2 Sep 2023 23:24:10 +0200 > Subject: Delegate the Built-Using field to the dh-builtusing debhelper tool > > > diff --git a/debian/control b/debi

Bug#1064863: u-boot for riscv64 as included does not work in qemu

Control: tags 1064863 - patch On 2024-02-26, Martin Cracauer wrote: > Package: u-boot-qemu > Version: 2021.01+dfsg-5 > Severity: important > Tags: patch No patch was included, removing from tags. > /usr/lib/u-boot/qemu-riscv64/u-boot.bin as included in this debian > release does not work for boo

Bug#1067098: mpl-sphinx-theme: please make the build reproducible

On 2024-03-18, Chris Lamb wrote: > Whilst working on the Reproducible Builds effort [0], we noticed that > mpl-sphinx-theme could not be built reproducibly. > > This is because it embedded the build date in the documentation: ... > --- a/debian/patches/reproducible-build.patch 1970-01-01 01:00:00.0

Bug#1063097: /usr/bin/mkimage: opens image and device trees (-d, -b) O_RDONLY, then O_RDWR, and fails if they're read-only (it doesn't write to them)

On 2024-02-05, наб wrote: > From a strace: > 1390 openat(AT_FDCWD, "/tmp/tmp.j2DX6x1MgV/Image-6.6.11.lz4", O_RDONLY) = 3 > 1390 newfstatat(3, "", {st_mode=S_IFREG|0644, st_size=12611929, ...}, > AT_EMPTY_PATH) = 0 > 1390 close(3) = 0 > 1390 openat(AT_FDCWD, "mt

Bug#1066113: guix: CVE-2024-27297

On 2024-03-15, Salvatore Bonaccorso wrote: > On Fri, Mar 15, 2024 at 11:22:52AM -0700, Vagrant Cascadian wrote: >> On 2024-03-13, Vagrant Cascadian wrote: >> > On 2024-03-12, Vagrant Cascadian wrote: >> >> On 2024-03-12, Salvatore Bonaccorso wrote: >> > I h

Bug#1066113: guix: CVE-2024-27297

On 2024-03-13, Vagrant Cascadian wrote: > On 2024-03-12, Vagrant Cascadian wrote: >> On 2024-03-12, Salvatore Bonaccorso wrote: > I have now tested an updated 1.4.x package on bookworm and a 1.2.x > package on bullseye, and the reproducer (with a small change for 1.2.x) > was abl

Bug#1066113: guix: CVE-2024-27297

On 2024-03-12, Vagrant Cascadian wrote: > On 2024-03-12, Salvatore Bonaccorso wrote: >> The following vulnerability was published for guix. >> >> CVE-2024-27297[0]: >> | Nix is a package manager for Linux and other Unix systems. A fixed- >> | output derivations o

Bug#1066113: guix: CVE-2024-27297

Control: found 1066113 1.4.0-3 Control: tags 1066113 pending On 2024-03-12, Salvatore Bonaccorso wrote: > The following vulnerability was published for guix. > > CVE-2024-27297[0]: > | Nix is a package manager for Linux and other Unix systems. A fixed- > | output derivations on Linux can send fil

Bug#1034311: reprotest: make it easier to compare against an existing build (eg from ftp.d.o)

On 2023-04-12, Holger Levsen wrote: > i guess reprotest maybe should grow an option to do > --control-build /path/to/packages/ > --vary=build_path=/use/this/build/path ... >to make it easier to use reprotest to compare against an existing > build >YES >

Bug#1064748: guix: FTBFS: In procedure canonicalize-path: No such file or directory

Control: forwarded 1064748 https://debbugs.gnu.org/69518 Control: tags 1064748 confirmed The actual failed tests are: test-name: fold-available-packages with/without cache test-name: find-packages-by-name with cache test-name: find-packages-by-name + version, with cache test-name: find-package-lo

Bug#1064998: guile-lib: broken package when cross building

On 2024-02-28, Helmut Grohne wrote: > guile-lib actually does cross build, but we still track it as cross > build failure, because the resulting package contains a build > architecture multiarch tuple and that trips post-build sanity checks. I am surprised that it actually cross builds at all... f

Bug#1064998: guile-lib: broken package when cross building

Forwarding this upstream, originally submitted in the Debian bug tracking system at: https://bugs.debian.org/1064998 On 2024-02-28, Helmut Grohne wrote: > guile-lib actually does cross build, but we still track it as cross > build failure, because the resulting package contains a build > archit

  1   2   3   4   5   6   7   8   9   10   >