her distros that package
sbuild without inheriting the packaging from Debian...
Curiously tests.reproducible-builds.org did not catch this, although it
may be checking different locales, or setting locales through alternate
mechanisms...
live well,
vagrant
signature.asc
Description: PGP signature
/../../../libguile-ssh/session-func.c:243:1: warning: control reaches end
> of non-void function [-Wreturn-type]
>243 | }
>| ^
This appears due to the update of libssh to 0.11.x. 0.10.x still built
fine when I checked a couple weeks ago, when I forwarded the issue
upstream.
live well,
vagrant
signature.asc
Description: PGP signature
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
least,
so I uploaded a new version of guile-gcrypt to trigger a rebuild.
live well,
vagrant
signature.asc
Description: PGP signature
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
default to build/platform even
when passing O= ... or more ugly, cleaning the directory in-between
invocations?
It would be nice to get this settled, though! :)
live well,
vagrant
signature.asc
Description: PGP signature
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
>
python3-stdlib-extensions-3124-1-source-into-unstable/
live well,
vagrant
signature.asc
Description: PGP signature
ther case, if either changes a name of one of the relevent files,
there would have to be coordination across packages... I guess it just
depends on which is less likely to change? :)
live well,
vagrant
signature.asc
Description: PGP signature
> ModuleNotFoundError: No module named 'jaraco'
jaraco is not called directly in any of reprotest's code...
This seems to be related to https://bugs.debian.org/1079175 which should
be fixed in the newly uploaded setuptools 73.0.0-1...
live well,
vagrant
signature.asc
Description: PGP signature
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,
/rb-pkg/unstable/amd64/vtwm.html
... I went and downloaded the vtwm artifacts only to find that they were
bit-for-bit reproducible.
live well,
vagrant
signature.asc
Description: PGP signature
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
s used during the
build.
I think "randomness" would be a more appropriate usertag here, and have
adjusted appropriately.
Thanks for working on the fix!
live well,
vagrant
signature.asc
Description: PGP signature
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...
>
with LC_ALL=C.UTF-8 locale if it still spits out errors? :)
reprotest's use of faketime tends to trigger issues with patch
systems...
live well,
vagrant
signature.asc
Description: PGP signature
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 th
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
out the line in default.preseed, or
possibly a better idea provide another simple-cdd profile that sets a
different value for this particular question.
live well,
vagrant
signature.asc
Description: PGP signature
an bookworm and bullseye, none of the affected
targets are actually built, although the source code contains the issue.
The targets are built in later versions, starting with 2.9.0+dfsg-1 and
2.10.0+dfsg-1+b1 currently in trixie and sid.
Marking versions appropriately.
live well,
vagrant
s
boot depends on cross-toolchains which were not yet available?
Please re-run the tests when the cross-toolchains become available.
live well,
vagrant
signature.asc
Description: PGP signature
pkgPID.CLOCKSECONDS]
Though I would guess this is not appropriate for typical runtime use.
live well,
vagrant
signature.asc
Description: PGP signature
tests varied build paths.
The patch needs a trivial refresh, but I can confirm that it still fixes
the issue.
I would like to perform an NMU fixing this in the near future, unless
there are outstanding objections.
live well,
vagrant
signature.asc
Description: PGP signature
cibility issues, but significantly
reducing the diff would be really helpful to resolve the remaining
issues.
Given the lack of comment the last four years, I propose to NMU this
soon.
live well,
vagrant
signature.asc
Description: PGP signature
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
r in any distro.
The current LTSP support is available in Debian as the "ltsp" package,
see:
https://ltsp.org/docs/
live well,
vagrant
signature.asc
Description: PGP signature
it:
https://salsa.debian.org/debian/guile-lzlib/-/commit/206654cca36977e64e97ef12096c3a86a5338835
live well,
vagrant
signature.asc
Description: PGP signature
, running on physical
> server
> machine.
You seem to also be lacking the recent security update for guix
(e.g. 1.4.0-3+deb12u1), please test that version also, just in case
there is some weird hidden versioned dependency conflict (e.g. if
guile-gnutls was built against a different ve
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
or possibly by enabling
salsa-ci pipelines, or building twice with sbuild, which currently
randomizes the build path by default.
live well,
vagrant
signature.asc
Description: PGP signature
o real effect on the resulting package.
[ Other info ]
Thanks!
live well,
vagrant
signature.asc
Description: PGP signature
ictions as well: not just --max-container-depth. For
> instance, excluding external commands like readelf and objdump that
> you know to be slow.
Ah, yes, knowing the common time sinks would be tremendously helpful!
live well,
vagrant
signature.asc
Description: PGP signature
ing in a qemu virtual machine, although
that is currently broken, so needs to be fixed somehow to remove
/etc/timezone.
live well,
vagrant
signature.asc
Description: PGP signature
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.
y default, give --min-cpus
to increase this.
WARNING:reprotest.build:IGNORING user_group variation; supply more usergroups
with --variations=user_group.available+=USER1:GROUP1;USER2:GROUP2 or
alternatively, suppress this warning with --variations=-user_group
WARNING:reprotest.build:Not using sudo for domain_host; your build may fail.
See man page for other options.
WARNING:reprotest.build:Be sure to `echo 1 >
/proc/sys/kernel/unprivileged_userns_clone` if on a Debian system.
--- /tmp/tmp4vqq6736/control
+++ /tmp/tmp4vqq6736/experiment-1
│ --- /tmp/tmp4vqq6736/control/source-root
├── +++ /tmp/tmp4vqq6736/experiment-1/source-root
│ │ --- /tmp/tmp4vqq6736/control/source-root/date
│ ├── +++ /tmp/tmp4vqq6736/experiment-1/source-root/date
│ │ @@ -1 +1 @@
│ │ +L 13 apr 2024 07:27:01 GMT
│ │ -Fri Apr 12 05:27:01 GMT 2024
live well,
vagrant
signature.asc
Description: PGP signature
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
re-reprotest
It is definitely quite rough around the edges and there are some caveats
that limit the functionality, but can do some of what you were looking
for.
live well,
vagrant
signature.asc
Description: PGP signature
ducible builds! And just for good measure,
thanks!
live well,
vagrant
signature.asc
Description: PGP signature
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:
>
&
1792&raw=0
Yeah, forwarded this upstream in January, but have not yet found a fix.
live well,
vagrant
signature.asc
Description: PGP signature
eam/pipeline/#adding-extra-arguments-to-reprotest
In short, switching to:
SALSA_CI_REPROTEST_ARGS: '--vary=-build_path'
I think this behaves more like people would expect, e.g. disabling build
path variations and not anything else.
live well,
vagrant
signature.asc
Description: PGP signature
!
live well,
vagrant
signature.asc
Description: PGP signature
I packages provide secure boot. Hence I suggest to simply
> drop patch debian/patches/qemu/efi-secure-boot.patch.
Any thoughts on this, Luca, as the provider of the original merge
request:
https://salsa.debian.org/debian/u-boot/-/merge_requests/24
Thanks!
live well,
vagrant
signature.asc
Description: PGP signature
st re-ran the tests again, and they still fail for me:
https://people.debian.org/~vagrant/dh-builtusing-issues/u-boot_2024.01+dfsg-4~0~20240324~0_arm64-2024-03-24T20:22:28Z.build.zst
https://people.debian.org/~vagrant/dh-builtusing-issues/u-boot_2024.01+dfsg-4~0~20240324~0_armhf-2024-03-24T20:21:58Z.build.zst
live well,
vagrant
signature.asc
Description: PGP signature
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-
ror: parsing package 'u-boot-sunxi' Built-Using
field: [arm64],
armhf.build- [arm64],
live well,
vagrant
signature.asc
Description: PGP signature
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
For u-boot, no patch is necessary. Just revert the reversal :-)
Re-added the patch tag, although strictly speaking it should now have a
versioned dependency... :)
Will probably wait till u-boot migrates to testing to re-apply the
patch... but will do so eventually.
live well,
vagrant
signature.asc
Description: PGP signature
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/
Leaving out the architecture qualifiers worked before switching to
dh-builtusing, though it did issue warnings in the build log about empty
variables.
Thanks for dh-builtusing, despite this hopefully small bump along the
road!
live well,
vagrant
signature.asc
Description: PGP signature
ltusing manpage, looks like it *should*
work ... so an inconsistency between documentation and implementation.
live well,
vagrant
es this work with current versions of u-boot in Debian, e.g. u-boot
2023.01+dfsg-2 from debian bookworm/stable or 2024.01+dfsg-1 from debian
trixie/testing?
live well,
vagrant
signature.asc
Description: PGP signature
0 +0100
> --- b/debian/patches/series 2024-03-18 12:59:16.218124536 +
> @@ -0,0 +1 @@
> +reproducible-build.patch
FWIW, I uploaded an NMU fixing this based on your earlier patch, but it
was reverted when the maintainer attempted to orphan the package without
incorporating the NMU...
https://bugs.debian.org/1005826
https://bugs.debian.org/1065042
live well,
vagrant
signature.asc
Description: PGP signature
but as we can see here, it doesn't write to it anyway.
> (Nor should it, given this is an input file.)
>
> Please turn this into an O_RDONLY.
It would be helpful to list the exact command you are running, although
best to take this upstream.
live well,
vagrant
signature.asc
Description: PGP signature
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
rg/en/blog/2024/fixed-output-derivation-sandbox-bypass-cve-2024-27297/
I have not yet had a chance to actually verify the fix on locally built
Debian packages, but all three releases do successfully build with the
patches applied.
live well,
vagrant
signature.asc
Description: PGP signature
builds/reprotest/-/commits/wip-specify-build-path?ref_type=heads
:)
live well,
vagrant
signature.asc
Description: PGP signature
-locations with cache
live well,
vagrant
signature.asc
Description: PGP signature
.0 GUILE=/usr/bin/guile-3.0 GUILD=/usr/bin/guild-3.0
returne
d exit code 1
live well,
vagrant
>
> The root cause of the failure lies in the way the ccache directory is
> determined. There are actually several ways this is being done during
> configure - some of which work correct
E_SITE_CCACHE)
> - ])
> + [AC_REQUIRE([GUILE_SITE_DIR])])
Would the guile-lib developers consider merging this? Are there any
use-cases where this is inappropriate?
Thanks!
live well,
vagrant
signature.asc
Description: PGP signature
am subscribed due to the previous NMU for
reproducible builds, and those changes do not appear to be included...
live well,
vagrant
signature.asc
Description: PGP signature
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
-ci do not test build paths, so strictly
speaking, the bug may still be there, though maybe lower priority, as
tests.reproducible-builds.org also stopped testing build paths.
live well,
vagrant
signature.asc
Description: PGP signature
board-specific regressions
are unfortunately all too common in u-boot and it is helpful to find
those regressions early.
live well,
vagrant
signature.asc
Description: PGP signature
just run
> quilt refresh yourself)
Since the patches apply with "quilt push --fuzz=0 -a" I do not think
this is currently needed.
Is there something I am missing?
live well,
vagrant
signature.asc
Description: PGP signature
to sponsor, this has some
helpful information and infrastructure:
https://mentors.debian.net/
live well,
vagrant
signature.asc
Description: PGP signature
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
t;
>> E: Command 'cd /<> && runuser -u user42 -- dpkg-buildpackage
>> --sanitize-env -us -uc -rfakeroot -S' failed to run.
Pushed a fix to git:
https://github.com/epoptes/epoptes/commit/57e25218637dd9d2264fd876c50dacdd10778e51
live well,
vagrant
signature.asc
Description: PGP signature
nd /etc/kernel/post*.d/ hooks.
live well,
vagrant
signature.asc
Description: PGP signature
ot;"" 4
> This variable specifies the unversioned stem of paths
> where U\-BOOT should look for the flattened device tree binaries.
> -Default is '/usr/lib/linux-image-'.
> +Default is '/usr/lib/linux-image-', or '/dtb-' when u\-boot\-update
> +detec
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
opensbi, which was fairly recently upgraded,
although I *thought* I tested opensbi 1.4-1 with the ~rc6 build I had
done...
Hrm. Will look a little deeper.
I doubt it ws the removed
unmatched-prevent-relocating-initrd-and-fdt.patch, as it is not even
detecting the NVMe device... and the sym
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
t, it booted normally, therefore the functionality of the system is
> not affected and it is a minor issue.
I have also seen this on several occasions as well, marking as
confirmed.
live well,
vagrant
signature.asc
Description: PGP signature
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-
weather to bump the dependency, as OpenSBI is now v1.4 in
unstable, so it should default to that version going forward...
live well,
vagrant
signature.asc
Description: PGP signature
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
otest or sbuild still do out of the
box, so it would be nice to get fixed regardless.
live well,
vagrant
signature.asc
Description: PGP signature
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
ot do this code
> injection).
I am unable to locally reproduce the issue with the current version in
Debian, marking as done.
While tests.reproducible-builds.org also confirms no unreproducibility
results for this version, it no longer tests for build path related
issues.
live well,
vagrant
signatu
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
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&
+ stdout.writeln("DustMite build (", source, "), built with ",
__VENDOR__, " ", __VERSION__);
live well,
vagrant
signature.asc
Description: PGP signature
complicated veresion that only does
this when SOURCE_DATE_EPOCH is set.
Maybe it could be applied to the debian mtools package to at least give
it some real-world testing? :)
live well,
vagrant
signature.asc
Description: PGP signature
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
1 - 100 of 1452 matches
Mail list logo
