On Tue, May 21, 2024 at 01:21:10PM -0700, Vagrant Cascadian wrote:
> I am hoping to schedule some Non-Maintainer Uploads (NMU) sprints,
> starting with two thursdays from now...
yay!
though I won't be able to join on June 6th. what's the other Thursday
you have in mind?
> Unapplied patches:
>
On Tue, May 14, 2024 at 11:43:29AM +0100, Chris Lamb wrote:
> Ah, I was hoping that the systemd slice apparatus would be able to
> contain any traceback, but now that I think of it, being OOM-killed is
> not quite the same as CPython-level crash (and thus traceback).
:)
> >
On Wed, May 08, 2024 at 03:07:00PM +0100, Chris Lamb wrote:
> Hm, I can't seem to reproduce the crash with these files. In the first
> instance, can you paste a traceback or similar of the crash in
> question? Maybe it is fixable just from that without having to find
> and upload more files, etc.
Package: diffoscope
Version: 264
Severity: normal
X-Debbugs-Cc: team+pkg...@tracker.debian.org
Dear Maintainer,
diffoscope crashes when comparing the build results of src:dasel. To make it
more fun, src:dasel is only unreproducible on i386 (out of our four tested
archs, amd64/i386/arm64/armhf)
On Tue, Apr 16, 2024 at 04:51:09PM +0100, Chris Lamb wrote:
> Just to say that I am totally on board with the idea of ensuring we
> get _something_ out of diffoscope on tests.reproducible-builds.org.
:) great!
> Way better than 250 timeouts.
Package: libscout
Version: 2.3.2-3
Severity: normal
X-Debbugs-Cc: reproducible-builds@alioth-lists.debian.net, Fay Stegerman
Dear Maintainer,
a few days ago I filed "#1068705: diffoscope crashes on libscout 2.3.2-3 build
on unstable but not bullseye" which then led Fay Stegerman to discover
On Mon, Apr 15, 2024 at 03:00:42PM +0200, Fay Stegerman wrote:
> > (thanks again!), am I correct to assume that thus there's no need
> > to file a seperate bug against libscout?
> It's generating a broken ZIP file with duplicate entries. It really shouldn't
> be doing that, regardless of whether
Hi again,
I've got two remaining questions about libscout (and diffoscope)
On Thu, Apr 11, 2024 at 01:48:18AM +0200, Fay Stegerman wrote:
> unzip does seem to extract all the files, though it errors out. Not sure what
> diffoscope should do here. This is definitely a broken ZIP file. That bug
Package: diffoscope
Version: 264
Severity: wishlist
Dear Maintainer,
currenlty diffoscope has a --timeout option
--timeout SECONDS
Best-effort attempt at a global timeout in seconds. If enabled,
diffoscope will not recurse into any further sub-archives
after
On Fri, Apr 12, 2024 at 10:29:07AM -0700, Vagrant Cascadian wrote:
> How exactly did you get this error?
upgrading my sid schroot. just confirmed the bug by removing it there
and installing it again. then I mounted /proc but the bug is still
there. /dev is also populated, though /usr/bin/mount
Package: reprotest
Version: 0.7.27
Severity: important
Dear Maintainer,
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 '\;'
On Thu, Apr 11, 2024 at 11:28:19AM +0100, Chris Lamb wrote:
[...]
> Applied in Git with attribution taken from your email.
[...]
> Fixed as well. And it adds a nice comment displaying the issue.
awesome, thank you both!
--
cheers,
Holger
⢀⣴⠾⠻⢶⣦⠀
⣾⠁⢠⠒⠀⣿⡁
On Thu, Apr 11, 2024 at 01:48:18AM +0200, Fay Stegerman wrote:
> Salsa is probably better for figuring out what to do next, but I get these
> mails
> too :)
:)
> The libscout.jar has duplicate ZIP entries in the central directory, pointing
> to
> the same actual entry in the ZIP. So the
On Wed, Apr 10, 2024 at 06:12:21PM +0100, Chris Lamb wrote:
> Holger Levsen wrote:
>
> > when building libscout 2.3.2-3 on current unstable, the result is also
> > unreproducible, but diffoscope crashes when analysing the diff.
> I think this is somewhat related to:
>
package: diffoscope
version: 263
hi,
diffoscope 263 crashes on libscout 2.3.2-3 build on unstable but not bullseye:
libscout 2.3.2-3 is part of bullseye (but neither bookworm nor trixie) and
builds unreproducible there and diffoscope is able to show a diff.
when building libscout 2.3.2-3 on
package: diffoscope
version: 240
hi,
crashing diffoscope in under 2min (the package build takes 42sec here).
$ apt source golang-github-stvp-tempredis
$ sudo pbuilder build golang-github-stvp-tempredis_0.0~git20231107.8a695b6-1.dsc
$ mkdir p1 ; mv /var/cache/pbuilder/unstable/result/* p1/
$
On Sat, Dec 16, 2023 at 06:23:46PM +, Paul Gevers wrote:
> During the wonderful mini-DebConf at Cambridge, the Release Team had a sprint
> and other discussions. Some of the discussed topics are worth sharing, so here
> we go.
[...]
> Reproducibility migration policy
>
On Thu, Dec 07, 2023 at 12:40:35PM +0100, Paul Gevers wrote:
> On 07-12-2023 12:20, Adrian Bunk wrote:
> > On Thu, Dec 07, 2023 at 11:18:42AM +0100, Paul Gevers wrote:
> > > I hope that in several hours,
> > > https://release.debian.org/britney/excuses_s-p-u.html will have the
> > > answer.
Hi Adrian,
thanks for bringing this to our attention!
On Sun, Dec 03, 2023 at 11:27:04PM +0200, Adrian Bunk wrote:
> Architecture: source amd64
>
> Should this be binNMU'ed on amd64 before the release?
I think so, yes.
> Maintainer-built binaries are not supposed to be in main.
yup.
> There
On Thu, Nov 16, 2023 at 03:20:12PM +0100, Jan-Benedict Glaw wrote:
> When a program cannot really continue its expected flow, I'm all for a
> stackdump and hard-crashing afterwards!
*g*
> So... Stack dumps and crashing is quite okay. We don't expect our
> parents or grandparents to use it, do
On Thu, Nov 16, 2023 at 01:56:05PM +, Chris Lamb wrote:
> > I think there is definitly an UI bug in diffoscope here. If/when diffoscope
> > runs out of memory, it should state that clearly and not throw 42 lines of
> > traceback at the user.
> Good idea. I've added that here:
>
>
On Wed, Nov 15, 2023 at 07:00:16PM +0100, Mattia Rizzolo wrote:
> I disagree with this: I believe we should at least keep testing until
> oldstable is handed over to the LTS team and the Release Team will stop
> touching it (which I believe will happen around the next Summer).
and fwiw, for
On Wed, Nov 15, 2023 at 07:00:16PM +0100, Mattia Rizzolo wrote:
> On Wed, Nov 15, 2023 at 05:15:50PM +0000, Holger Levsen wrote:
> > Tomorrow I intend to also disable testing Debian bullseye which
> > development ceased in August 2021.
> I disagree with this: I believe we sh
hi,
eleven days ago I disabled testing Debian buster on tests.r-b.o/debian
and noone really complained nor noticed.
Tomorrow I intend to also disable testing Debian bullseye which
development ceased in August 2021.
The current stable Debian release is bookworm, released in June 2023
and
On Wed, Nov 15, 2023 at 01:31:26PM +, Chris Lamb wrote:
> I would be more than willing to conclude that this is an issue in
> tests.reproducible-builds.org setup. However, I am actually seeing
> these test files when I build locally as well — and my patch
> consequently fixes the "problem".
On Wed, Nov 15, 2023 at 02:30:05PM +, Chris Lamb wrote:
> Holger Levsen wrote:
> > https://jenkins.debian.net/job/reproducible_netbsd/1029/console
> > contains this, which IMO should not happen and is an issue in
> > diffoscope:
> >
> > Traceback (most recent
On Mon, Nov 06, 2023 at 10:42:05AM +, Chris Lamb wrote:
> Christos Zoulas wrote:
>
> > For weeks now there is no useful output from diffoscope. Is there anything I
> > can do to help debug the issue?
> >
> > tests.reproducible-builds.org[eeB]
> > Wed 1 Nov 23:35:09 UTC 2023 -
Hi Santiago,
On Wed, Oct 18, 2023 at 12:59:56PM +0200, Santiago Vila wrote:
> The build logs contain a lot of messages like this one:
> 504 Gateway Timeout [IP: redacted-the-ip-of-the-proxy 3128]
we're currently experiencing some disturbances, see #1052257
for a small glimpse into the
On Thu, Oct 12, 2023 at 11:36:38PM -0700, Vagrant Cascadian wrote:
> The original btrfs based one now has snapshots as far back as july 2023
> up to the present, and is currently 974GB. So, that looks like overall
> about 330GB growth per month, roughly.
neato!
--
cheers,
Holger
hi,
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...)
so on Sep 23rd I made diffoscope
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.a
this didnt really help:
mosh last connect some 50m ago:
13 109 19:00:30 up 6:41, 3 users, load average: 151.64, 205.31, 156.09
10 112 19:01:00 up 6
hi,
from #debian-reproducible just now:
and there we go again, first mosh connection lost after disabling i386
workers.
* | h01ger sighs. at least i was hopeful for a few hours
while running diffoscope on an armhf deb
so I've powercycled the machine and also disabled the armhf
package: diffoscope
version: 240
severity: important
x-debbugs-cc: reproducible-bui...@lists.alioth.debian.org
hi,
On Tue, Sep 05, 2023 at 10:05:58PM +0200, FC Stegerman wrote:
> It worked (and was probably needed) before as the "--" was interpreted
> by schroot, not diffoscope. So the solution
hi,
Debian CI builds should be "fully" back now. Will see if the main node
handles this better...
--
cheers,
Holger
⢀⣴⠾⠻⢶⣦⠀
⣾⠁⢠⠒⠀⣿⡁ holger@(debian|reproducible-builds|layer-acht).org
⢿⡄⠘⠷⠚⠋⠀ OpenPGP: B8BF54137B09D35CF026FE9D 091AB856069AAA1C
⠈⠳⣄
:wq
signature.asc
Description:
On Tue, Sep 05, 2023 at 09:51:47AM +, Holger Levsen wrote:
> I've implemented & deployed this now. Hoping not to see very high loads again
> soon...
[11:58] < h01ger> debian CI builders are back
[13:15] < h01ger> though it doesnt work:
[13:15] < h01ger&g
On Sat, Sep 02, 2023 at 12:59:45PM +, Holger Levsen wrote:
> My next attempt will be to run diffoscope from bookworm, instead of running
> diffoscope from sid in a schroot.
I've implemented & deployed this now. Hoping not to see very high loads again
soon...
--
cheers,
On Thu, Aug 31, 2023 at 11:07:28AM -0700, Chris Lamb wrote:
> > what has changed in July is that this host was upgraded to bookworm. what
> > also has changed is that diffoscope was upgraded (constantly to the sid
> > version), though I don't see any relevant changes in changelog.
> I can't think
On Tue, Aug 29, 2023 at 07:05:05PM +, Holger Levsen wrote:
> fwiw, at 18:48:18 UTC jenkins.d.n had a load of 3.79 (with 23 cores),
> then mosh lost connection for 12min, then at 19:00:03 the load was 155.37,
> then at 19:01:09 the load was 60.10, a min later the load was 25.
>
&g
On Tue, Aug 29, 2023 at 06:47:44PM +, Holger Levsen wrote:
> On Tue, Aug 29, 2023 at 10:26:58AM +0000, Holger Levsen wrote:
> > this is #1050784, fwiw. re-enabling our CI will have to wait until it's
> > fixed.
> #1050784 has been fixed, all 62 pbuilder unstable and exper
On Tue, Aug 29, 2023 at 10:26:58AM +, Holger Levsen wrote:
> this is #1050784, fwiw. re-enabling our CI will have to wait until it's fixed.
#1050784 has been fixed, all 62 pbuilder unstable and experimental base.tgz's
have been recreated and the CI builds have been reenabled by
package: snapshot.debian.org
severity: important
x-debbugs-cc: debian-de...@lists.debian.org,
reproducible-bui...@lists.alioth.debian.org
Hi,
filing this as a bug report, again, because the problem has become worse
than when #1031628 was filed and since snapshot.d.o is part of the central
On Tue, Aug 29, 2023 at 10:11:34AM +, Holger Levsen wrote:
> the latest usrmerge/debianutils breakage is:
>
> Unpacking debianutils (5.10) over (5.9) ...
> Setting up debianutils (5.10) ...
> ln: failed to create symbolic link '/usr/bin/run-parts': File exists
> dpkg: error
hi,
from #debian-reproducible just now:
< h01ger> i've disabled the r-b builds to see if jenkins also acts up
(=gets a load of >200 and stops responding to pings even)
when builds and thus diffoscope runs are disabled. i'll
probably keep this this way for a few
On Wed, Jul 26, 2023 at 07:03:36PM +0100, Peter Blackman wrote:
> I'd prefer to reschedule for qt6ct.
done. c-evo-dh already looks good. I hope I'll have time for some more
debugging soon, so asunder will also be retried soon!
--
cheers,
Holger
⢀⣴⠾⠻⢶⣦⠀
⣾⠁⢠⠒⠀⣿⡁
On Tue, Jul 25, 2023 at 10:04:46AM -0700, Vagrant Cascadian wrote:
> Looks like the whole archive is rebuilt roughly every 2 to 2.5 months.
>
> As you noticed, new versions get priority, and FTBFS *should* get
> scheduled more often, as well... but who knows, sometimes things fall
> into
On Sat, Jun 17, 2023 at 02:08:20PM -0700, Vagrant Cascadian wrote:
> From what I recall looking at the log posted in irc it might be
> sufficient to "apt autoremove usrmerge" after the fact, as usrmerge is
> not really reversible... e.g. the /bin -> /usr/bin and other symlinks
> should continue to
hi,
first: i've temporarily disabled testing usrmerge variation last
night as this broke our builds, because the .buildinfo files vary
(usrmerge installed or not), causing basically all builds to fail.
second: this has been happening since a few weeks, I still don't
get why this suddenly stopped
Hi Jan,
On Thu, Jun 15, 2023 at 07:56:15PM +0200, Jan-Benedict Glaw wrote:
> I'm currently deep-diving into NetBSD's repro builds and looking at
> https://salsa.debian.org/qa/jenkins.debian.net/-/blob/master/bin/reproducible_netbsd.sh,
> I found some oddities that may make it blind to some
hi,
so we are testing trixie now as well, and thus the following question came
up on #debian-reproducible:
helmut: until now, we have varied whether the usrmerge package is
installed, when testing bookworm, unstable & experimental. shall we
keep varying this for bookworm?
On Sat, Jun 03, 2023 at 02:08:12PM +0200, Evangelos Ribeiro Tzaras wrote:
> [1]21386 killed diffoscope --debug
> l5-phosh-{1,2}/mobian-librem5-phosh-20230603.img
fwiw, I can reproduce this bug on bullseye and unstable, with and without
--no-default-limits.
--
cheers,
Holger
hi,
thanks Evangelos, for filing this bug and providing the images exposing it to
https://fortysixandtwo.eu/upload/mobian-librem5-phosh-20230603-{1,2}.img now.
--
cheers,
Holger
⢀⣴⠾⠻⢶⣦⠀
⣾⠁⢠⠒⠀⣿⡁ holger@(debian|reproducible-builds|layer-acht).org
⢿⡄⠘⠷⠚⠋⠀ OpenPGP:
hey,
On Tue, Apr 25, 2023 at 07:56:45PM +0200, Mattia Rizzolo wrote:
> Today I've fully "archived" stretch on our test website.
\o/ & thank you.
> The stats are still in
> https://tests.reproducible-builds.org/debian/index_oldsuites.html and
> should stay there indefinitely.
>
> Also, the data
package: distro-info
severity: wishlist
x-debbugs-cc: reproducible-bui...@lists.alioth.debian.org
affects: extrepo-data, developers-reference
hi!
On Fri, Apr 14, 2023 at 12:24:52PM -0700, Vagrant Cascadian wrote:
> On 2023-04-14, Holger Levsen wrote:
> > i'm wondering whether distro-in
On Fri, Jan 13, 2023 at 06:49:48PM +0100, Holger Levsen wrote:
> since some years, tracker.d.o is thankfully showing results from
> https://tests.reproducible-builds.org/debian - which was and is awesome!
> However, these are just continious integration test results and
> not based on
Package: reprotest
Version: 0.7.23
Severity: wishlist
Dear Maintainer,
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
hi,
like in previous weeks, we'd like to do another Debian NMU sprint
tomorrow, Tuesday, January 24 at 16 UTC.
IRC:
irc.oftc.net #debian-reproducible
Unapplied patches:
https://udd.debian.org/bugs/?release=sid=only=ign=ign=ign=1
Documentation about performing NMUs:
On Fri, Jan 13, 2023 at 06:49:48PM +0100, Holger Levsen wrote:
> But there is a new service, which rebuilds packages and compares the results
> against the binaries we publish at ftp.d.o, which is
> https://rebuild.notset.fr/debian
pollo: hmpf, i ment https://rebuild.notset.fr/
than
Package: tracker.debian.org
Severity: normal
X-Debbugs-Cc: frederic.pier...@qubes-os.org,
reproducible-bui...@lists.alioth.debian.org
Dear Maintainer,
since some years, tracker.d.o is thankfully showing results from
https://tests.reproducible-builds.org/debian - which was and is awesome!
hi Vagrant,
On Sun, Nov 20, 2022 at 04:28:10PM -0800, Vagrant Cascadian wrote:
> Since the previous sprints were fun and productive, I am planning on
> doing NMU sprints every Thursday in December (1st, 8th, 15th, 22nd,
> 29th). We are planning on meeting on irc.oftc.net in the
>
Package: diffoscope
Version: 222
Severity: wishlist
Dear diffoscope maintainers,
since this Thursday src:coreboot is finally (*) in unstable and thus cbfstool
is finally there too (via binary:coreboot-utils), see
Hi Phil,
On Wed, Sep 14, 2022 at 04:00:04PM +0200, Philip Hands wrote:
> I suggest adding a 'nocheck' variation, that sets DEB_BUILD_OPTIONS=nocheck
> during the build, and enabling it by default.
[...]
> Option 2) is what I'm suggesting making into a default variation.
[...]
> If nothing else it
Package: cdebootstrap
Version: 0.7.8
Severity: wishlist
X-Debbugs-Cc: reproducible-bui...@lists.alioth.debian.org
Dear Maintainer,
using cdebootstrap 0.7.8 it's possible to reproducible bootstrap Debian,
provided one does three extra steps:
1. rm /var/log/dpkg.log /var/log/alternatives.log
Package: debootstrap
Version: 1.0.127
Severity: wishlist
X-Debbugs-Cc: reproducible-bui...@lists.alioth.debian.org
Dear Maintainer,
using debootstrap 1.0.127 it's possible to reproducible bootstrap Debian,
provided one does three extra steps:
1. rm /var/log/dpkg.log /var/log/alternatives.log
On Fri, May 27, 2022 at 08:36:44AM +0800, Paul Wise wrote:
> On Thu, 2022-05-26 at 14:00 +0100, Chris Lamb wrote:
> > What I was trying to say is that we would need enough riscv64
> > computing power to build all of Debian in good time... where "good
> > time" is loosely defined as being able to
merge 961064 1012035 993339
severity 961064 important
tags 961064 + help newcomer
thanks
On Sun, May 29, 2022 at 08:26:18PM +0200, Samuel Thibault wrote:
> Zhang Boyang, le dim. 29 mai 2022 14:10:35 +0800, a ecrit:
> > I found Salsa CI reprotest on my repo fails when "FAKETIME variation:
> >
On Sat, May 28, 2022 at 09:53:22AM +0200, Mattia Rizzolo wrote:
> Actually IIRC I should have already configured the repository in a way
> that all DD can freely push to it! :)
has this already been documented and announced as well? our monthly newsletter
and also debian developer mininews come
On Tue, Apr 12, 2022 at 09:37:07AM -0700, Vagrant Cascadian wrote:
> I've noticed nearly all of the packages marked
> "randomness_in_r_rdb_rds_databases" actaully appear to be not random at
> all, but rather a deterministic result derived from the build path:
>
> ~1200 packages that FTBR in
Hi Santiago,
On Tue, Mar 08, 2022 at 11:06:32AM +0100, Santiago R.R. wrote:
> Could reprotest have an --append-build-command option please?
yes, please. patches most welcome, too! ;)
--
cheers,
Holger
⢀⣴⠾⠻⢶⣦⠀
⣾⠁⢠⠒⠀⣿⡁ holger@(debian|reproducible-builds|layer-acht).org
⢿⡄⠘⠷⠚⠋⠀
Hey Otto,
On Mon, Feb 21, 2022 at 09:49:36PM -0800, Otto Kekäläinen wrote:
> Finally mariadb-10.6 builds fully reproducibility in Debian unstable:
[...]
wheeeh, thats great, congrats & thanks for sharing!
--
cheers,
Holger
⢀⣴⠾⠻⢶⣦⠀
⣾⠁⢠⠒⠀⣿⡁
On Sun, Feb 13, 2022 at 02:13:10PM -0800, Vagrant Cascadian wrote:
> Curious to hear your thoughts!
I'd just like to comment with three rather general comments:
a.) thanks for bringing this up here, Vagrant.
b.) solving this seems to be a requirement for getting the build-essential
package
hi,
as we had quite some false positives recently, I've rescheduled all
packages tested unreproducible on bookworm:
- 2749 packages for amd64
- 2958 packges for arm64
- 2800 packges for armhf
- 2501 packges for i386
So in 24-48h things should be back to normal again.
--
cheers,
On Fri, Feb 04, 2022 at 09:18:56AM -0800, Vagrant Cascadian wrote:
> I don't think selecting a locale at random is a good idea; this means
> sometimes a build might succeed with reprotest and sometimes not,
> depending on which locale happens to be randomly selected.
agreed.
> Secondly, I think
hi,
the mail below showed up on debian-de...@lists.debian.org today and I
think we should formulate our ideas where Debian should be improved to
make r-b a reality. I'm thinking about infrastructual changes and process
changes, and not really so much about fixing individual packages.
So I've set
hi,
On Sat, Oct 30, 2021 at 11:51:45AM +0100, Chris Lamb wrote:
> Neat. Okay, so I've just run the testsuite against file 1:5.41-1 in
> experimental and everything appears to pass.
while this is great, shouldn't we run these automatically? :)
Package: lintian
Version: 2.109.0
Severity: normal
X-Debbugs-Cc: reproducible-bui...@lists.alioth.debian.org
Dear Maintainer,
lintian fails to unpack the current strip-nondeterminism source package,
and thus also fails to properly check the package:
$ schroot -- lintian --info --pedantic
On Mon, Oct 04, 2021 at 10:54:19PM +, Holger Levsen wrote:
> On Mon, Oct 04, 2021 at 10:34:03PM -, Chris Lamb wrote:
> > Sorry for the slight delay; been under the weather over the weekend. Anyway,
> > please review the draft for September's Reproducible Builds repo
hi,
On Mon, Oct 04, 2021 at 10:34:03PM -, Chris Lamb wrote:
> Sorry for the slight delay; been under the weather over the weekend. Anyway,
> please review the draft for September's Reproducible Builds report:
> https://reproducible-builds.org/reports/2021-09/?draft
jenkins is also not
hi,
given that https://debian.notset.fr/rebuild/results/unstable.amd64.html is
really nice already and knowing that I wont have much time in the next two
weeks (and really wanting to show real results for Debian now...) it occurred
to me that we could point the dns entry for
Hi Chris,
thanks for your bugreport, but it seems to me that reprotest is not failing
but rather producing failure results when rebuilding your package. Is that
correct? If so, it's not a bug in reprotest... :)
On Mon, Aug 30, 2021 at 09:33:26PM -0400, Christopher Talbot wrote:
> On Mon,
Hi Adrian,
On Mon, Aug 30, 2021 at 12:16:40PM +0300, Adrian Bunk wrote:
> there are currently several reproducible-only build failures due to
> export LANG="C" in the first build.
>
> Would it be OK to set LANG to C.UTF-8 or en_US.UTF-8 in the first build
> instead?
>
> Building under
& Bookworm - where we come from and where we are
going
Speaker: Holger Levsen
Language: English
Track: Introduction to Free Software & Debian
Type: Long talk (45 minutes)
Room: Talks 1
Time: Aug 24 (Tue): 19:00 UTC
Duration: 0:45
In this talk Holger Levsen will give an update on Reproducibl
hi,
On Tue, Aug 17, 2021 at 10:18:22AM +, Holger Levsen wrote:
> It will take some more hours until the first bookworm packages will be tested,
> due to the way scheduling etc works. Then, at least the dashboard will still
> miss the bookworm graphs... IOW: expect some things to
On Tue, Aug 17, 2021 at 03:41:47PM +0200, Mattia Rizzolo wrote:
> May I recommend we do *not* enable this on the r-b builders, as I'm
> positive it would break quite a few things here and there.
hmm...
> Rather, it
> would be perfect for aws' comparative rebuilds. Now, who is the
> contact
On Tue, Aug 17, 2021 at 12:21:08PM +0200, Mattia Rizzolo wrote:
> Hopefully it was easy enough to follow what we did last time with
> buster.
we're not done yet... (see TODO in jdn.git)
> Shall we officially drop stretch now? (perhaps move them to some r/o
> place, or drop the completely?)
hi,
I've just deployed this commit:
jenkins.debian.net master 1c5b2ef Holger Levsen TODO
bin/reproducible_scheduler.py * reproducible Debian: start scheduling tests for
bookworm * https://deb.li/3U8D4
It will take some more hours until the first bookworm packages will be tested,
due
On Sun, Aug 15, 2021 at 12:16:39AM +0100, Simon McVittie wrote:
> The failure mode we have sometimes seen is packages that were built in
> a merged-/usr chroot not working on a non-merged-/usr system, although
> that's detected by the reproducible-builds infrastructure and is already
> considered
On Sat, Aug 14, 2021 at 04:01:34PM +0200, Roland Clobus wrote:
> > (A side question: can you confirm whether diffoscope is running as
> > root or not in your particular Jenkins test? I don't want to
> > misinterpret the logs.)
> I'm 99.9% sure that I'm not running as root, because I would have
On Tue, Aug 10, 2021 at 02:08:11PM +0100, Chris Lamb wrote:
> Still, the bugs I did file were 'useful' in the sense that it was the
> impetus to do some real-world research in the first place. In that
> sense, I am *very* much +1 an archive rebuild for this; from my
> initial investigations by
hi,
from #reproducible-debian today:
< nthykier> It looks like we have started filing bugs for cmake packages to
have them use "-DCMAKE_SKIP_RPATH=ON", which is included in
debhelper compat 14 (not stable)
< nthykier> FWIW: I am still ready to make that option the
Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: unblock
x-debbugs-cc: reproducible-bui...@lists.alioth.debian.org
Hi,
I'm wondering whether it makes sense to unblock strip-nondeterminism 1.12.0-1,
which has been uploaded on 2021-05-07 and which
Package: diffoscope
Version: 177
Severity: normal
x-debbugs-cc: Roland Clobus
Dear Maintainer,
https://jenkins.debian.net/job/reproducible_debian_live_build_cinnamon_bullseye/lastFailedBuild/consoleFull
shows a failure to run diffoscope on a cinnamon libe-build hybris.iso:
+ timeout 30m nice
Hi Chris,
On Tue, Jun 08, 2021 at 09:21:20AM +0100, Chris Lamb wrote:
> > So I'd like to suggest to postpone the next upload until diffoscope 177 has
> > migrated in 16 days (or some issue pops up which warrants an upload).
> Yep. :)
great!
> > strip-nondeterminism OTOH has been in unstable
hi,
in the last months there has been roughly a diffoscope upload per week, which
is quite fantastic! However with the recent change of the migration rules
for bullseye to migration delays of 20 days, this means that diffoscope
doesn't migrate to bullseye anymore even though the package has
On Wed, Mar 31, 2021 at 04:56:50PM +0200, Frédéric Pierret wrote:
> > would it be possible to whitelist his IP 92.188.110.153 so it doesn't get
> > throttled when accessing snapshot.d.o?
> This would be awesome that if I could download smoothly and gently directly.
indeed!
> Please note that we
hi,
On Sat, Mar 06, 2021 at 11:31:51AM +0100, Frédéric Pierret wrote:
> Following topic from lists on working on developing tool for creating a
> mirror of snapshot.d.o, is it possible to have an export of the raw
> PostgreSQL tables of snapshot.d.o (38.7 GiB) somewhere for helping us
> in
On Mon, Mar 01, 2021 at 06:12:39PM +0100, Julien Cristau wrote:
> On Sat, Feb 27, 2021 at 02:09:08PM +0000, Holger Levsen wrote:
> > It's possible to work around them partly/sometimes, but it seems clear by
> > now that using snapshot.d.o *as it is* doesn't scale for our use ca
Hi,
snapshot.debian.org is an awesome service for the wider free software community
and especially for those working on reproducible builds. Sadly accessing *many*
packages from it is limited and troublesome (see below for bug numbers), thus
we (mostly Frédéric Pierret and myself) came up with
On Mon, Feb 08, 2021 at 05:55:04PM -, Chris Lamb wrote:
> That provides some of the contents of the directories; thanks. Can you
> also provide some of the contents of the "argv" files? These should
> contain the actual command-line passed to diffoscope and, as part of
> that, the crucial
control: reopen -1
thanks
hi,
On Sat, Jan 30, 2021 at 01:12:03PM +, Chris Lamb wrote:
> * New features and bugfixes:
> - Explicitly remove our top-level temporary directory.
> (Closes: #981123, reproducible-builds/diffoscope#234)
we are still seeing temporary directories not
Hi Chris,
On Fri, Nov 20, 2020 at 01:07:02PM -, Chris Lamb wrote:
> > building diffoscope 161 results in the following lintian warnings and errors
> > which we should fix, because also tests should ship their sources (in
> > general,
> > there are some exceptions...)
> This has been a work
1 - 100 of 204 matches
Mail list logo
