Re: sbuild should use build date as binnmu changelog date

Hi Ian and reproducible-builds folks, On Wed, 9 Nov 2016 12:03:48 + Ian Jackson wrote: > Currently, when adding a changelog stanza for a binnmu (or when appending to > the version number is requested for another reason), sbuild uses the existing > source

Re: misleading timestamps in binnmus

Ian Jackson (2016-11-09): > What version of sbuild do buildds run ? Ie, supposing that this is > fixed in sbuild in stretch, will this be fixed on the buildds ? Or do > we need to update jessie, or what ? sbuild on buildds uses a specific version of sbuild, for

Re: misleading timestamps in binnmus

On Tue, Nov 08, 2016 at 10:41:09PM +, Ian Jackson wrote: > Is this a recommended recipe ? AIUI a buildd doing a binnmu will not > modify the debian/changelog file. Are you sure? When last I checked, this was not true (it may have changed since, however). -- < ron> I mean, the main

Bug#843811: strip-nondeterminism: does not strip nondeterminism from /SYM64/ ar entries

Package: strip-nondeterminism Version: 0.028-1 Severity: important Dear Maintainer, strip-nondeterminism does not strip the /SYM64/ timestamp from the attached files, which are produced by building the glibc source package. This is probably also a bug in binutils, but I will need to check the

Re: Bug#843073: dpkg-shlibdeps: broken on i386 with merged /usr

Hi Michael, On Wed, Nov 09, 2016 at 07:16:53PM +0100, Michael Biebl wrote: > > https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/systemd.html > Do you also have builds for i386? (which this issue is about, amd64 is fine) yes, they are linked from that url as well, though you can

Bug#843797: koji: FTBFS: help2man: can't get `--help' info from ./cli/koji

Source: koji Version: 1.10.0-1 Severity: serious Justification: fails to build from source User: reproducible-builds@lists.alioth.debian.org Usertags: ftbfs X-Debbugs-Cc: reproducible-builds@lists.alioth.debian.org Dear Maintainer, koji fails to build from source in unstable/amd64: […]

Bug#843796: civicrm: FTBFS: dh_linktree: link destination debian/civicrm-common/usr/share/civicrm/bower_components/jquery-ui/themes/smoothness/images is a directory

Source: civicrm Version: 4.7.8+dfsg-1 Severity: serious Justification: fails to build from source User: reproducible-builds@lists.alioth.debian.org Usertags: ftbfs X-Debbugs-Cc: reproducible-builds@lists.alioth.debian.org Dear Maintainer, civicrm fails to build from source in unstable/amd64:

Bug#843776: dpkg-buildpackage should set LC_COLLATE=C.UTF-8

Package: dpkg-dev Version: 1.18.12 According to POSIX, the meaning of glob patterns is unspecified in locales other than `the POSIX locale'. [1] It's not easy to see from the spec, but the relevant env var is LC_COLLATE. Many package build rules, dh rules, etc., rely on shell globbing. This

Re: misleading timestamps in binnmus

Thanks to everyone who has provided information. I have summarised it in #843773, against sbuild. What version of sbuild do buildds run ? Ie, supposing that this is fixed in sbuild in stretch, will this be fixed on the buildds ? Or do we need to update jessie, or what ? Ian. -- Ian Jackson

Re: misleading timestamps in binnmus

Hi! On Wed, 2016-11-09 at 11:16:09 +, Ian Jackson wrote: > Sven Joachim writes ("Re: misleading timestamps in binnmus"): > > I'm afraid I don't really have a good suggestion. Using current date > > would work but obviously break reproducibility, and any other date seems > > arbitrary. > > I

Re: misleading timestamps in binnmus

(CCing reproducible-builds again:) Sven Joachim writes ("Re: misleading timestamps in binnmus"): > I'm afraid I don't really have a good suggestion. Using current date > would work but obviously break reproducibility, and any other date seems > arbitrary. I don't understand why using the