[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#863206: marked as done (whitedune: please make the build reproducible (buildpath))

Your message dated Tue, 09 Dec 2025 12:11:22 +0000
with message-id <[🔎] E1vSwYs-003RCr-0a@fasolo.debian.org>
and subject line Bug#1114505: Removed package(s) from unstable
has caused the Debian Bug report #863206,
regarding whitedune: please make the build reproducible (buildpath)
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@bugs.debian.org
immediately.)


-- 
863206: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=863206
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message --- 
Source: whitedune
Version: 0.30.10-2.1
Severity: wishlist
User: reproducible-builds@lists.alioth.debian.org
Usertags: buildpath
X-Debbugs-Cc: reproducible-bugs@lists.alioth.debian.org

Hi!

While working on the “reproducible builds” effort [1], we have noticed
that whitedune could not be built reproducibly.  One of the reasons for
that is that it embeds the basename of the build directory as a string
literal in the resultant artifacts, through the batch/getversion.sh and
batch/replaceversion.sh scripts.  The artifacts are therefore different
when the build directory is named "whitedune-*" versus when it is,
say, "blackhill-*".

You can see the results here:
.
    https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/whitedune.html
    (last hunk in the .rodata section)

An easy fix would be to make replace the entirety of getversion.sh with
a `dpkg-parsechangelog -SVersion` invocation, and similarly for replaceversion.sh;
however, this solution would not be upstreamable.  A better solution
would be for upstream to obtain the version number in some other way on
all platforms (the version number doesn't appear anywhere in the tree,
other than debian/changelog and packager/debian/changelog).

How would you like to proceed?

Cheers,

Daniel

 [1]: https://wiki.debian.org/ReproducibleBuilds

--- End Message ---
--- Begin Message --- 
Version: 0.30.10-2.2+rm

Dear submitter,

as the package whitedune has just been removed from the Debian archive
unstable we hereby close the associated bug reports.  We are sorry
that we couldn't deal with your issue properly.

For details on the removal, please see https://bugs.debian.org/1114505

The version of this package that was in Debian prior to this removal
can still be found using https://snapshot.debian.org/.

Please note that the changes have been done on the master archive and
will not propagate to any mirrors until the next dinstall run at the
earliest.

This message was generated automatically; if you believe that there is
a problem with it please contact the archive administrators by mailing
ftpmaster@ftp-master.debian.org.

Debian distribution maintenance software
pp.
Thorsten Alteholz (the ftpmaster behind the curtain)

--- End Message ---
Reply to: