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?
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
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
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
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
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
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
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
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
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)
...
>>
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
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
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
>
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
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
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
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,
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
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
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
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...
>
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
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
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&
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
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
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
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
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
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
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
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;
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
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
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
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
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
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
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
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
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
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.
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 %
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
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
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
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
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:
>
&
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
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
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
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
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
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-
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
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
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
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
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/
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
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
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
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
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
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
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
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
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
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
>
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
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
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
On 2024-02-29, Sandro Tosi wrote:
> I intend to orphan the mpl-sphinx-theme package.
>
> The package description is:
> This is the official Sphinx theme for Matplotlib documentation. It extends
> the
> pydata-sphinx-theme project, but adds custom styling and a navigation bar.
> .
> This packa
Package: openssh-server
Version: 1:9.2p1-2+deb12u2
Severity: normal
X-Debbugs-Cc: Vagrant Cascadian
The default sshd_config sources configuration snippets from
/etc/ssh/sshd_config.d/*.conf in the earliest entry in the
configuration, but then defines some Debian defaults after this, which
makes
On 2024-01-27, Nilesh Patra wrote:
> On Sat, Jan 27, 2024 at 09:09:12PM +0530, Nilesh Patra wrote:
>> > The build path is embedded in /usr/bin/nmodl:
>> >
>> >
>> > https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/diffoscope-results/nmodl.html
>> >
>> > /build/1st/nmodl-0.5/obj
On 2024-01-24, Лухнов Андрей Олегович wrote:
> please consider adding OrangePI PC Plus to sunxi platforms. Changes
> are trivial, proposed platform is buildable without errors and tested
> bootable on target hardware.
>
> Required changes attached.
Would you or someone else be willing to regularly
On 2024-01-22, Лухнов Андрей Олегович wrote:
> I've quilt-refreshed patches in u-boot 2024.01+dfsg-1 to apply them
> without fuzzyness.
>
> Please find, ahem, a patch for that attached. :) (I'm not sure, if it
> is a correct method to propose a fix, though, or you could just run
> quilt refresh you
On 2024-01-22, Jose Luis Rivero wrote:
> lcm upstream released the version 1.5.0 on April 2023. It would be great to
> have it packaged and available on Debian Sid.
>
> I canhelp with code changes if the maintainer or the team are willing to
> sponsor and review them.
Well the "team" is the Debian
last working commit: 3aa14d76182dbbaf9fed4deeaf362f083b9d2f5b
>>
>> next commit, which doesn't work on Sheevaplug:
>> 5387b093cb7914b3c0404da928fa4bafdffac291
>
> Vagrant Cascadian pointed out that this issue has been fixed in:
>
> commit 9a13a76e6256c51d04f41139733dbb31755e
Control: tags 1044403 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).
...
> More information about this class of issues, included common problems and
> solutions, is available at
> ht
On 2023-01-04, Manuel Traut wrote:
> if kernel-install is called manualy the extlinux.conf file is not
> generated.
>
> This can be resolved with an .install file in /usr/lib/kernel/install.d
I uploaded a fix which calls u-boot-update from a hook in that
directory, but it does not support the newl
On 2022-12-12, Arnaud Ferraris wrote:
> It is common practice for /boot to be on a separate partition, requiring DTBs
> to be synced to this partition for u-boot to be able to access them.
Thanks for working on this!
> From: Arnaud Ferraris
> Date: Mon, 12 Dec 2022 13:57:47 +0100
> Subject: [PAT
On 2023-11-13, Arnaud Ferraris wrote:
> Le 18/05/2023 à 17:42, Vagrant Cascadian a écrit :
>>
>> Unfortunately, this will have to wait till after bookworm release,
>> currently scheduled for June.
>
> Gentle ping with the hope that you (or Jonas) have some bandwidt
On 2024-01-12, Vagrant Cascadian wrote:
> On 2024-01-12, Vagrant Cascadian wrote:
>> On 2024-01-12, Michael Fladischer wrote:
>>> I was able to boot my Hifive Unmatched Rev B board via SPI from NVME with
>>> u-boot-sifive-2023.07+dfsg-1. After upgrading to 2024.01+dfs
On 2024-01-12, Vagrant Cascadian wrote:
> On 2024-01-12, Michael Fladischer wrote:
>> I was able to boot my Hifive Unmatched Rev B board via SPI from NVME with
>> u-boot-sifive-2023.07+dfsg-1. After upgrading to 2024.01+dfsg-1 u-boot is no
>> longer able to see any NVME drive
On 2024-01-12, Michael Fladischer wrote:
> I was able to boot my Hifive Unmatched Rev B board via SPI from NVME with
> u-boot-sifive-2023.07+dfsg-1. After upgrading to 2024.01+dfsg-1 u-boot is no
> longer able to see any NVME drives:
...
>U-Boot 2024.01+dfsg-1 (Jan 10 2024 - 21:34:04 +)
>
>
On 2023-08-29, Diederik de Haas wrote:
> On 10 Jun 2023-06-10 Vagrant Cascadian wrote:
>> On 2023-06-10, Bernhard wrote:
>> > I'm interested in the Router BANANA Pi R3 from Sinovoip:
>> > https://wiki.banana-pi.org/Banana_Pi_BPI-R3
>> >
>> &g
Control: tags 1033497 confirmed
On 2023-03-26, Rainer Dorsch wrote:
> I installed bookworm on a cubox-i. After the installation was
> finished, the installed reported that it reboots now. The reboot did
> never complete tough. After I unplugged the power supply and replugged
> it, it booted normal
Control: found 977177 1.0.6-1
Hi, it seems the changes in the 1.0.5-1.1 NMU were not included in the
most recent upload... would you please consider including them?
live well,
vagrant
On 2023-12-05, Vagrant Cascadian wrote:
> On 2023-11-29, Vagrant Cascadian wrote:
>> On 2020-12-
On 2024-01-06, Heinrich Schuchardt wrote:
> I have built U-Boot from
>
> https://salsa.debian.org/debian/u-boot/-/commit/e182a8eb13eb6d1990a3d79740b71b0cc52f9f5a
> Merge branch 'debian/2024.01-rcX' into debian/latest
>
> and deployed it to these boards:
>
> StarFive VisionFive 2 v1.3B, 4 GiB
> Star
On 2024-01-05, Vagrant Cascadian wrote:
> On 2023-11-23, Andreas Henriksson wrote:
>> On Thu, Nov 23, 2023 at 08:16:43PM +0100, Tobias Heider wrote:
>>> On Thu, Nov 23, 2023 at 10:51:04AM -0800, Vagrant Cascadian wrote:
>>> > On 2023-11-23, Andreas Henriksson wrote:
On 2023-11-23, Andreas Henriksson wrote:
> On Thu, Nov 23, 2023 at 08:16:43PM +0100, Tobias Heider wrote:
>> On Thu, Nov 23, 2023 at 10:51:04AM -0800, Vagrant Cascadian wrote:
>> > On 2023-11-23, Andreas Henriksson wrote:
...
>> > > 3/ do we include patches?
>>
On 2023-12-06, Vagrant Cascadian wrote:
> I would like to submit an NMU in the near future to apply the two
> patches submitted for dustmite to fix reproducibility issues, which are
> both essentially one-line patches:
>
> #1020878: dustmite: reproducible-builds: build path embedded
@@
+crack (5.0a-13.1) unstable; urgency=medium
+
+ * Non-maintainer upload.
+
+ [ Vagrant Cascadian ]
+ * debian/Crack.make: Use dpkg-buildflags to set default CFLAGS.
+(Closes: #1021521)
+ * src/util/Makefile: Remove embedded timestamps. (Closes: #1021522)
+
+ [ Helmut Grohne ]
+ * Fix
On 2023-02-23, Chris Lamb wrote:
> This is because the gawkbug script contained the contents of the CFLAGS
> environment variable, and this can contain the full build path via/by
> embedding -ffile-prefix-map.
...
> --- a/debian/rules2023-02-23 10:40:16.745966821 -0800
> --- b/debian/rules2
On 2022-05-01, Vagrant Cascadian wrote:
> On 2022-05-01, Sebastian Andrzej Siewior wrote:
>> control: forwarded -1 https://github.com/openssl/openssl/pull/11545
>>
>> On 2022-04-20 15:46:41 [-0700], Vagrant Cascadian wrote:
>>> The compiler flags usually contain th
Version: 1:1.3.dfsg-3
On 2023-08-28, Chris Lamb wrote:
> This is because it embeds the absolute build path in the minizip and
> miniunzip scripts.
>
> A patch attached that uses sed to remove these, (although there might
> be a cleaner way to inform autotools/libtool to not do this code
> injectio
0 -0800
@@ -1,3 +1,12 @@
+psi (1.5+dfsg1-1.1) unstable; urgency=medium
+
+ * Non-maintainer upload.
+
+ [ Chris Lamb ]
+ * Make the build reproducible (Closes: #1017473)
+
+ -- Vagrant Cascadian Thu, 07 Dec 2023
13:16:09 -0800
+
psi (1.5+dfsg1-1) unstable; urgency=medium
* New upstrea
On 2022-09-27, Vagrant Cascadian wrote:
> A timezone-dependent timestamp is embedded in /usr/games/edid-decode:
>
>
> https://tests.reproducible-builds.org/debian/rb-pkg/bookworm/amd64/diffoscope-results/edid-decode.html
>
> 2022-03-29·21:29:27
> vs.
> 2022-03-30·2
On 2021-12-17, Ryan Pavlik wrote:
> Oh wow, thanks! I was trying to figure out why it wasn't reproducible even
> though it "should have" been. I'll apply this soon.
>
> On Fri, Dec 17, 2021, 6:09 PM Vagrant Cascadian <
> vagr...@reproducible-builds.org> w
1 - 100 of 1429 matches
Mail list logo
