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
>>
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
>
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
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
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
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
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.7.27) ...
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
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)
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
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=armhf=0.26-1=1704511792=0
Yeah, forwarded this upstream in
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
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,
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
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
> #
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
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
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
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
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
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
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,
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
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
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:
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...
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
>
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
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
>> >
>> >
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
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
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
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 9a13a76e6256c51d04f41139733dbb31755e8d30
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
>
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
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:
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
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
>> >
>> > Th
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
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
>
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 p
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/rules
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
>
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> wrote:
...
On 2021-12-26, Vagrant Cascadian wrote:
> There are two result.xml files shipped in the .deb package which contain
> timestamp, timing, and hostname information about the build environment:
>
> ./usr/lib/python3/dist-packages/build/testing/report.xml
>
> -tests="218&
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 in
/usr/bin/dustmite
debian/rules:
+EXTRA_DFLAGS +=
On 2023-05-02, Chris Lamb wrote:
>> I came across timestamp differences in FAT filesystem images while
>> trying to build debian-installer with debrepro (among many other
>> things), and tracked it down to mmd/mcopy calls. Here's a short reproducer:
>
> Ah, interesting! And your reproducer is
0
@@ -1,3 +1,12 @@
+mpl-sphinx-theme (3.5.0-1.1) unstable; urgency=medium
+
+ * Non-maintainer upload.
+
+ [ Chris Lamb ]
+ * Make the documentation build reproducibly (Closes: #1005826)
+
+ -- Vagrant Cascadian Wed, 06 Dec 2023
15:59:56 -0800
+
mpl-sphinx-theme (3.5.0-1) unstable; urgen
On 2023-12-01, Vagrant Cascadian wrote:
> On 2021-10-06, Chris Lamb wrote:
>> This is due to the use of the LIBINPUT_QUIRKS_DIR macro which includes
>> the absolute build path.
>>
>> It is not entirely clear (during a very brief look) when/where this
>> value i
On 2023-11-30, Vagrant Cascadian wrote:
> On 2021-07-09, Vagrant Cascadian wrote:
>> From 88b66063c5f02ba48f2fc9cfa2ae6cc42c950cc8 Mon Sep 17 00:00:00 2001
>> From: Vagrant Cascadian
>> Date: Fri, 9 Jul 2021 15:13:24 +
>> Subject: [PATCH] Use the build date fr
On 2023-11-30, Vagrant Cascadian wrote:
> On 2022-08-05, Vagrant Cascadian wrote:
>> On 2022-08-05, Vagrant Cascadian wrote:
>>> On 2022-08-05, Francesco P. Lovergine wrote:
>>>> On Sun, Jul 17, 2022 at 01:52:46PM +0100, Simon McVittie wrote:
>>>>>O
Control: notfixed 1024286 1.3.1+repack1-6
On 2022-11-16, Vagrant Cascadian wrote:
> The build path and binary paths are embedded in
> /usr/share/doc/lcm-doc/examples/Makefile:
>
>
> https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/diffoscope-results/lcm.htm
:25:42.0 -0800
+++ lirc-0.10.1/debian/changelog2023-12-05 15:52:45.0 -0800
@@ -1,3 +1,28 @@
+lirc (0.10.1-7.3) unstable; urgency=medium
+
+ [ Vagrant Cascadian ]
+ * Non-maintainer upload.
+ * tools: Do not embed build date and kernel version in various files.
+(Closes
On 2023-11-29, Vagrant Cascadian wrote:
> On 2020-12-12, Simon McVittie wrote:
>> On Fri, 11 Dec 2020 at 20:45:09 -0800, Vagrant Cascadian wrote:
> With the patch, I managed to produce a bit-for-bit identical
> skeletonmm.tar.xz with the patch applied, both in a test environment
&g
On 2023-11-28, Vagrant Cascadian wrote:
> On 2017-04-17, Chris Lamb wrote:
>> This is due to it capturing the buildpath in some automatically
>> generated documentation. It appears safe to simply delete the manpages
>> in question as they are a) private APIs and b) kinda te
y on it anyways.
I would like to perform an NMU in the near future, unless there are
objections?
live well,
vagrant
From 6b78d6697661c497ae4ff2a3bbf1eea53ae60ccc Mon Sep 17 00:00:00 2001
From: Vagrant Cascadian
Date: Fri, 1 Dec 2023 14:17:20 -0800
Subject: [PATCH] tools: Remove references to L
On 2021-03-02, Chris Lamb wrote:
> Whilst working on the Reproducible Builds effort [0] we noticed that
> python-scrapy could not be built reproducibly.
>
> This is because it uses the current build year when building the
> documentation which, of course, changes depending which year you
> build
On 2021-07-09, Vagrant Cascadian wrote:
> From 88b66063c5f02ba48f2fc9cfa2ae6cc42c950cc8 Mon Sep 17 00:00:00 2001
> From: Vagrant Cascadian
> Date: Fri, 9 Jul 2021 15:13:24 +
> Subject: [PATCH] Use the build date from SOURCE_DATE_EPOCH if set, falling
> back to current
Control: tags 751341 - patch
On 2014-06-11, Hans-Christoph Steiner wrote:
> diff --git a/debian/control b/debian/control
> index 60be58a..11c718a 100644
> --- a/debian/control
> +++ b/debian/control
> @@ -4,6 +4,8 @@ Priority: optional
> Maintainer: Bastian Blank
> Build-Depends: debhelper (>>
Control: retitle 983138 ypserv: /bin/sh symlink triggers differences in pwupdate
On 2022-08-05, Vagrant Cascadian wrote:
> On 2022-08-05, Vagrant Cascadian wrote:
>> On 2022-08-05, Francesco P. Lovergine wrote:
>>> On Sun, Jul 17, 2022 at 01:52:46PM +0100, Simon McVittie wrote:
On 2021-01-01, Vagrant Cascadian wrote:
> The lirc package ships a /usr/share/lirc/lirc-VERSION.tar.gz tarball.
>
> This tarball contains timestamps produced during the build, can be
> affected by the umask of the build environment.
>
>
> https://tests.reproducible-bui
On 2020-12-12, Simon McVittie wrote:
> On Fri, 11 Dec 2020 at 20:45:09 -0800, Vagrant Cascadian wrote:
>> If anyone has a better handle on python's tarfile mode handling code, it
>> might be worth taking a closer look. I'm not entirely sure how the file
>> modes work in
p-2.0.9_src_ccrtp_.9_src_ccrtp_.3.gz
usr/share/man/man9/_build_libccrtp-eppWJD_libccrtp-2.0.9_src_.9_src_.3.gz
I intend to NMU this package in the near future to fix this issue if I
do not hear otherwise.
live well,
vagrant
From ffa35c9ca2ac9dcc0c78b7d604011a2faee25db0 Mon Sep 17 00:00:00 2001
On 2023-11-28, harr...@gmx.ph wrote:
> On 27/11/2023 20:12, Vagrant Cascadian (@vagrant) wrote on salsa:
>>Thanks! Looks good to me, could you add (Closes: #XXX) on the first line of
>>the commit?
...
> Thanks for agreeing to the merge request. I've added the Closes: note.
On 2023-11-23, Andreas Henriksson wrote:
> I'm opening this bug report to discuss the potential of building another
> u-boot variant in a new binary package from src:u-boot for "Apple
> Silicon" machines.
Thanks! I am guessing this class of hardware may represent a much larger
community than many
On 2023-10-02, Heinrich Schuchardt wrote:
> U-Boot v2023.10 has been released. It provides sufficient support for
> the StarFive Visionfive 2 board.
Thanks!
> I would suggest to package it as u-boot-starfive.
I will probably wait until u-boot 2023.10 lands in Debian before
uploading a new
On 2023-09-26, Lucas Nussbaum wrote:
> During a rebuild of all packages in sid, your package failed to build
> on amd64.
>
>
> Relevant part (hopefully):
...
>> cc1: error: ‘-fcf-protection=full’ is not supported for this target
>> make[3]: *** [/<>/Makefile:1816: include/generated/env.in]
>>
ng kuttypy!
live well,
vagrant
From 25b7eeb2072424c31b21ceea5ae95d583faa5bcd Mon Sep 17 00:00:00 2001
From: Vagrant Cascadian
Date: Tue, 14 Nov 2023 15:34:37 -0800
Subject: [PATCH] Makefile: Split echo call into multiple lines to avoid
shell-dependent handling of "\n".
https://tests.rep
t; Date: Thu, 26 Oct 2023 19:53:53 +0700
>
> Thank you, this patch was applied upstream [1].
>
> [1] https://github.com/tboox/tbox/pull/219
>
> --
> Lance Lin
> GPG Fingerprint: 4A31 DB5A 1EE4 096C 8739 9880 9036 4929 4C33 F9B7
> From: Vagrant Cascadian
> Subject: tb
On 2023-10-11, Johannes Schauer Marin Rodrigues wrote:
> installing u-boot-menu does not create /boot/extlinux/extlinux.conf. Is
> there a reason for that? It gets triggered as expected when kernels get
> installed or upgraded but the postinst does not contain a codepath that
> gets triggered just
On 2023-10-11, Hubert Tonneau wrote:
> Diederik de Haas wrote:
>> Did the situation improve with version 2023.01 as released with Bookworm?
...
> I upgraded the Pinebook pro to Debian Bookworm, and it means
> u-boot-rockchip package version 2023.01+dfsg-2 (january 18 2023).
Did you manually
On 2023-09-27, Holger Levsen wrote:
> On Wed, Sep 20, 2023 at 12:25:36PM +, Holger Levsen wrote:
>> so I've powercycled the machine and also disabled the armhf workers now.
>> (under the (weak) assumption that this bug is mostly trigged when running
>> diffoscope on 32bit .debs...)
Most
Package: apt
Version: 2.6.1
Severity: wishlist
X-Debbugs-Cc: vagr...@reproducible-builds.org
Thanks for maintaining apt! I use it all the time!
No idea how difficult this would be to implement, but...
It would be nice to be able to download content (e.g. .deb or .dsc)
normally downloadable via
Control: merge 1043571 1051721
On 2023-09-11, Sietze van Buuren wrote:
> When building a default bookworm dist image using the command
> `build-simple-cdd`
> on a bookworm system, simple-cdd is able to successfully build the
> image. However, when using this image to install a new system, the
On 2023-08-31, Chris Lamb wrote:
> 2. The jtreg.jar file was being generated with 444 (read-only)
> permissions. This meant that strip-determinism could not fixup the
> file modification times of the files within that archive. It was
> actually printing: "dh_strip_nondeterminism: warning: Ignoring
On 2023-08-31, Christopher Obbard wrote:
> Let me rephrase myself. My suggestion is to ship in u-boot-rockchip U-Boot
> for these devices
> *without* any closed bits and ship rkbin in non-free-firmware in
> non-free-firmware.
>
> We need to simply combine those into an image file to flash to the
On 2023-08-30, Diederik de Haas wrote:
> On Wednesday, 30 August 2023 16:35:46 CEST Vagrant Cascadian wrote:
>> > I also recall seeing references to a `rk3568_ddr_1056MHz_v1.18.bin` file
>> > from https://github.com/rockchip-linux/rkbin/tree/master/bin/rk35. AFAIK
>&
On 2023-08-30, Diederik de Haas wrote:
> On Wednesday, 30 August 2023 00:41:18 CEST you wrote:
>> On 2023-08-29, Diederik de Haas wrote:
>> > Upstream recently added support for the following Pine64 Quartz64 devices:
>> > - Quartz64 Model A
>> > - Quartz64 Model B
>> > - SoQuartz on Model A board
1 - 100 of 3263 matches
Mail list logo
