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 - diffoscop
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 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". Mor
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 basicall
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
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 rebuil
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:
>
> https://sal
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 w
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, 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.
aweso
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
> =
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/
$ sud
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 curr
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:
>
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 "over
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
⢀⣴⠾⠻⢶⣦⠀
⣾⠁⢠⠒⠀⣿⡁ holger@(debian|reproducible-b
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 '\;'
run_or_
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 fai
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 X
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
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 w
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 tha
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.
https://tests.reproducible-builds.org/debian/stats_bre
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) an
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.
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).
:)
> > https://tests.reprodu
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:
>
source: diffoscope
severity: serious
justification: kaboom
forwarded: https://salsa.debian.org/reproducible-builds/diffoscope/-/issues/389
On Sun, Aug 18, 2024 at 07:10:45AM +, Holger Levsen wrote:
> On Sat, Aug 17, 2024 at 09:08:27PM +, FC (Fay) Stegerman (@obfusk) wrote:
> >
Package: devscripts
Version: 2.23.7-87-g6f7811f0
Severity: normal
User: devscri...@packages.debian.org
Usertags: debrebuild
X-Debbugs-Cc: jo...@debian.org, reproducible-builds@alioth-lists.debian.net
Dear josch,
when trying to use debrebuild from the debrebuild branch, this fails for
me very ear
Package: devscripts
Version: 2.23.7-78-gee16294f
Severity: normal
User: devscri...@packages.debian.org
Usertags: debrebuild
X-Debbugs-Cc: jo...@debian.org, reproducible-builds@alioth-lists.debian.net
Dear josch,
when trying to use debrebuild from the main branch and when using a proxy
to cause le
Package: devscripts
Version: 2.23.7-78-gee16294f
Severity: normal
User: devscri...@packages.debian.org
Usertags: debrebuild
X-Debbugs-Cc: jo...@debian.org, reproducible-builds@alioth-lists.debian.net
Dear josch,
when trying to use debrebuild from the main branch this fails for me like
this:
holg
On Thu, Nov 28, 2024 at 10:06:47AM +, Debian FTP Masters wrote:
> Source: ecbuild
> Changes:
> ecbuild (3.9.0-2) unstable; urgency=medium
>* Drop dh-buildinfo as redundant
thank you! :)
--
cheers,
Holger
⢀⣴⠾⠻⢶⣦⠀
⣾⠁⢠⠒⠀⣿⡁ holger@(debian|reproducible-builds|layer-acht).org
⢿⡄
On Mon, Jan 30, 2017 at 02:47:45PM +0100, Johannes Schauer wrote:
> > (the sbuild maintainer reads the above list which has been cc:ed so he
> > should be able to comment…)
>
> You were talking about buildd-tools-de...@lists.alioth.debian.org
yes
> You forgot to CC that one (I understood that wa
On Mon, Jan 30, 2017 at 01:10:12PM +0100, Mattia Rizzolo wrote:
> > Would reproducible-bui...@lists.alioth.debian.org be the correct mailing
> > list to discuss this?
the debian-buildd list or a bug against sbuild might be more
appropriate…
(the sbuild maintainer reads the above list which has b
On Sat, May 13, 2017 at 05:52:04PM +0200, Mattia Rizzolo wrote:
> On Sat, May 13, 2017 at 03:44:57PM +0100, Chris Lamb wrote:
> > a) Has anything changed in the meantime?
>
> Yes: sbuild stopped repeating the changelog time taking it from the last
> entry, and will instead generate a new timestam
On Sat, May 13, 2017 at 10:48:18PM +0200, Aurelien Jarno wrote:
> The above change should now be deployed on most jessie based buildds,
> it's only missing on the buildds that are currently down.
cool, thank you!
--
cheers,
Holger
signature.asc
Description: Digital signature
_
On Wed, Nov 27, 2024 at 06:31:22PM +0100, Bill Allombert wrote:
> Replace dh_buildinfo by a script that just print a warning but does not
> actually
> generate the file, then ask for binNMU ?
> Update the description to mention the problem.
why pamper it over if we can fix it?
--
cheers,
On Wed, Nov 27, 2024 at 02:04:03PM +0100, Chris Hofstaedtler wrote:
> IIRC you said in some other thread that dh-buildinfo is causing you
> issues. If that is the case (= if I'm not misremembering), an upload
> that "defuses" dh-buildinfo would immediately solve the issue.
>
> And then maintainers
On Wed, Nov 27, 2024 at 07:17:24PM +0100, Santiago Vila wrote:
> Because the fix you have in mind involves bothering a lot of people,
> or worse, a few people with a lot of work, while the intermediate
> status proposed by Bill fixes all the undesired effects you
> have listed before.
but then I w
On Wed, Nov 27, 2024 at 10:49:05AM +, Debian FTP Masters wrote:
> Date: Wed, 27 Nov 2024 11:18:55 +0100
> Source: debian-multimedia
> [...]
> Changes:
> debian-multimedia (0.12) unstable; urgency=medium
>* Task devel: Do not suggest dh-buildinfo (bug #1068809 asking for removal)
> [...]
On Wed, Nov 27, 2024 at 12:11:23PM +0100, Alexandre Detiste wrote:
> Don't forget the 311 build-depends ...
> $ reverse-depends -l -b dh-buildinfo | wc -l
> 311
so /usr/bin/reverse-depends was the tool I was looking for, thank you!
I've now installed ubuntu-dev-tools...
> These would need a MB
On Wed, Nov 27, 2024 at 12:00:40PM +, Bill Allombert wrote:
> Upload a version of dh_buildinfo that does nothing be output a warning
> 'warning: db_buildinfo is obsolete, please remove from Build-Depends'.
I certainly wouldn't mind anyone doing this.
(I also doubt many people would see and ac
Hi Andreas,
On Wed, Nov 27, 2024 at 11:04:04AM +0100, Andreas Tille wrote:
> Today dh-buildinfo appeared as a candidate for the Bug of the Day[1].
> In bug #1068809 the reporter suggested to "consider deprecating and
> removing the package". For me the reasons are perfectly valid and
> thus I che
Hi,
I've not much to add except...
On Wed, Dec 04, 2024 at 10:05:38PM +0100, Simon Josefsson wrote:
> Another feature idempotent rebuilds may help with is to re-bootstrap the
> entire Debian trixie+X release from another operating system like Guix
> or macOS. Rebuilding all packages in trixie+X
On Wed, Dec 18, 2024 at 10:51:28AM +, Chris Lamb wrote:
> I like the idea of varying nocheck, or at least exploring the concept.
same here.
> From personal experience, I think it will actually cause a
> surprisingly large number of packages to become unreproducible. Many
> many packages gene
On Wed, Jan 22, 2025 at 02:24:57PM +0200, Sergey Ponomarev wrote:
> The 1980-02-01 was chosen as a default reproducible date in many tools
> like Gradle and Maven (any others?).
> Could you mention it on the page
> https://reproducible-builds.org/docs/timestamps/
> We need to put rationale why the
201 - 246 of 246 matches
Mail list logo
