Reproducible Builds in March 2025🔹

2025-04-11 Thread Chris Lamb
o ⬋ ⬊ March 2025 in Reproducible Builds o o ⬊ ⬋ https://reproducible-builds.org/reports/2025-03/ o Welcome t

Bug#1102658: marked as done (diffoscope: Tests fail with OpenSSH 10.0p1)

2025-04-11 Thread Debian Bug Tracking System
Your message dated Fri, 11 Apr 2025 19:34:19 + with message-id and subject line Bug#1102658: fixed in diffoscope 294 has caused the Debian Bug report #1102658, regarding diffoscope: Tests fail with OpenSSH 10.0p1 to be marked as done. This means that you claim that the problem has been dealt

Re: deprecation of buildinfo.debian.net (NOT buildinfos.debian.net)

2025-04-11 Thread Chris Lamb
Holger Levsen wrote: > ok, cool. I've just pushed the branch deprecate-service with "7096703: > deprecate > buildinfo.debian.net as it has been superseeded by buildinfos.debian.net" > to the github repo, where I set the shutdown date to June 1st 2025. Merged, and this is now live. :) >> Appr

diffoscope_294_amd64.changes ACCEPTED into unstable

2025-04-11 Thread Debian FTP Masters
Thank you for your contribution to Debian. Accepted: -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Fri, 11 Apr 2025 12:22:46 -0700 Source: diffoscope Built-For-Profiles: nocheck Architecture: source Version: 294 Distribution: unstable Urgency: medium Maintainer: Reproducibl

Bug#1102658: diffoscope: Tests fail with OpenSSH 10.0p1

2025-04-11 Thread Chris Lamb
tags 1102658 + pending thanks Colin Watson wrote: > I haven't dug through far enough to know exactly what the problem is, > but the above clearly doesn't make sense. Please could you have a look? Sure! Looks like you found a longstanding and hidden mistake where a bunch of tests for ">" were n

Processed: Re: Bug#1102658: diffoscope: Tests fail with OpenSSH 10.0p1

2025-04-11 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > tags 1102658 + pending Bug #1102658 [src:diffoscope] diffoscope: Tests fail with OpenSSH 10.0p1 Added tag(s) pending. > thanks Stopping processing here. Please contact me if you need assistance. -- 1102658: https://bugs.debian.org/cgi-bin/bugrep

Processing of diffoscope_294_amd64.changes

2025-04-11 Thread Debian FTP Masters
diffoscope_294_amd64.changes uploaded successfully to localhost along with the files: diffoscope_294.dsc diffoscope_294.tar.xz diffoscope_294_amd64.buildinfo Greetings, Your Debian queue daemon (running on host usper.debian.org) ___ Repro

Bug#1102658: diffoscope: Tests fail with OpenSSH 10.0p1

2025-04-11 Thread Colin Watson
Source: diffoscope Version: 293 Severity: important I'm preparing an upload of OpenSSH 10.0p1 to unstable, and while testing it I found that diffoscope's tests fail as follows: _ test_diff12 __ differences12 = [] @skip_

Re: nocheck vs reproducible-builds

2025-04-11 Thread Santiago Vila
Ok, I see that Holger replied to that ten minutes ago in this list in another thread which I missed... So, nevermind. ___ Reproducible-builds mailing list Reproducible-builds@alioth-lists.debian.net https://alioth-lists.debian.net/cgi-bin/mailman/listi

nocheck vs reproducible-builds

2025-04-11 Thread Santiago Vila
Hello. I'm currently building trixie with nocheck. Some packages do this in the install target and it fails: cp some-test-files some-doc-directory A simple ifeq would make nocheck to work again, but then the package would not build the same with nocheck and without nocheck. Technically that wo

Re: Build with DEB_BUILD_OPTIONS="nocheck" when testing for reproducibility?

2025-04-11 Thread Holger Levsen
hi, On Sat, Mar 22, 2025 at 12:50:51PM -0700, Vagrant Cascadian wrote: > Off of the top of my head, binutils and gcc intentionally embed the > results of test suites into a .deb ... and some unintentionally embed > test suite results. This only lists a few that we have found where it is > pretty o

Re: deprecation of buildinfo.debian.net (NOT buildinfos.debian.net)

2025-04-11 Thread Holger Levsen
Hi, reviving this somewhat old thread. On Fri, Mar 21, 2025 at 03:20:47PM +, Chris Lamb wrote: > >> Before everything, though, we might simply disable the virtual machine > >> and replace it with a static HTML page along the lines of, "We plan to > >> shut this down, so if this has broken som