Ximin Luo:
> This is quite an open-ended problem and there is no single "correct"
> answer. I don't even know myself what would be best, at this stage.
I think what we need to come up with now is a list of use cases. Then we
can decide which one we want to support and how easy it should be.
Is an
Ximin Luo:
> Concretely I have some suggestions:
>
> 1. instead of calling this "ignore" we call it "hide". and instead of
> "irrelevant" we say "common"/"minor"/"known"
Great suggestions! :)
> 2. diffoscope --ignore-* (or --hide-*) MUST NOT return 0 or otherwise
> give the impression that two n
Hi Axel!
Axel Beckert:
> Running
>
> $ reprotest 'dpkg-buildpackage -b'
> ../debian-paketmanagement-buch_0\~2016.06.29_all.deb
>
> from a git checkout of commit 5f069a920df4e6f20a8eb9309c20c39ad60e6132
> under X to see if my $SOURCE_DATE_EPOCH implementation in that commit is
> working correctl
Ceridwen:
> For most of the variations I've done so far, I've been either
> depending on external utilities or had POSIX-compliant ways to execute
> them. The rest of the variations pose more problems.
>
> 1. user_group. The POSIX standard includes the notion of user/group
> ids, but the only wa
Chris Lamb:
>> Could these offset differences in readelf(1) output be ignored, at least
>> optionally?
>
> Love the idea! However, my gut cautions against ignoring them. even with an
> option.
>
> Perhaps there is a perfect solution whereby we would normalise these two
> offsets to — making it u
Daniel Shahaf:
> Jérémy Bobbio wrote on Tue, Sep 20, 2016 at 13:18:49 +:
>> But why stop with images? In the precise case of the readelf output,
>> having line-oriented diff means we are carrying around a useless and
>> confusing information: the line numbers are not
Mattia Rizzolo:
> The reason we like to have a static string in there (and in jenkins we
> use the host architecture), is that otherwise diffoscope would be noisy
> about the difference in the name if we compared the .changes files […].
Would it still be the case after Satyam's work which resulted
Mattia Rizzolo:
> Next steps:
> it would be great if somebody could figure what's the real gain of
> having .dsc in Checksums-Sha256.
This is how .buildinfo files have linked a source package in an
unambiguous manner to the resulting binaries. I see how the current
specification is giving you trou
Маша Глухова:
> I believe the attached patch would provide the requested functionality.
Nice work! :)
> From: Maria Glukhova
> Date: Sat, 24 Dec 2016 12:29:57 +0200
> Subject: [PATCH] Add detection of order-only difference in plain text format.
>
> Detect if the text files' contents differ only
Chris Lamb:
> Daniel Shahaf wrote:
>
> > > +if subprocess.call(
> > > +('python3', '-c', 'import enjarify.typeinference'),
> >
> > Use sys.executable instead of hardcoding 'python3', to handle the case
> > that there's more than one python3 binary on the system?
>
> I deliberately us
Hi!
Маша Глухова:
> The reason why I did not use some algorihm like that is that it requires to
> read files for the second time. Right now, all the actual work with the
> content of the files (except for the quick check for has_same_content) is
> delegated to diff, and on big files, it occupies m
Chris Lamb:
> > I had no idea I should have installed it, and indeed I was missing it.
>
> … which is itself a bug! However, the solution is not very obvious - why
> can't really detect whether we need would benefit from fuzzy matching without
> doing said fuzzy matching!
>
> Will have a think :)
Package: diffoscope
Severity: normal
diffoscope currently doesn't know how to parse Haskell .hi files written
on big-endian architectures as such. This should be fixed.
--
Lunar.''`.
lu...@debian.org: :Ⓐ : # apt-get install anarchism
Chris Lamb:
> Mattia wrote:
> > > After a hint from doko, I've started work on an official-looking spec
> > > for SOURCE_DATE_EPOCH
> >
> > Lamby pointed out that this is not something debian-related, so it would
> > be great to have it outsite a debian.{org,net} site.
> >
> > OTOH also the howto
dpkg_1.18.3~reproducible1.dsc has just been uploaded to
https://wiki.debian.org/ReproducibleBuilds/ExperimentalToolchain
___
Reproducible-builds mailing list
Reproducible-builds@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/list
This
included Arch:all packages. If we use a single tar archive, with `gzip
--rsyncable`, I assume the difference on each mirror push will be
small. But we probably could use reproducible.debian.net to come up with
actual numbers if needed.
> > - Packages file gets a certfied-by field:
> &g
clone 797525 -1
retitle -1 diffoscope: provide option to disable fuzzy-matching
thanks
Hi!
Jakub Wilk:
> I want to use diffoscope to compare two "Multi-Arch: same" debs of the same
> version but different architecture, to see differences that will cause
> co-installation conflicts.
>
> This almos
Santiago Vila:
> The problem here is that some packages execute xgettext *every* single
> time the package is built (creating a different .pot file each time),
> and then they also perform msgmerge with the new .pot file and the
> existing .po files, creating different .po files each time.
>
> Non
Santiago Vila:
> Excluding .pot files from what is considered to be the "source" might
> be part of the problem.
See tor-monitor upstream's reaction, for example:
https://lists.alioth.debian.org/pipermail/pkg-privacy-maintainers/Week-of-Mon-20150824/15.html
Quoting Alan from there:
> I didn't
Control: retitle -1 diffoscope: implement fuzzy-matching across containers
Control: severity -1 wishlist
Michele Alessandrini:
> When comparing tar.gz or tar.bz2 archives containing text files, some
> of which different, the output is a binary diff. Perhaps it only
> applies decompression and comp
Michele Alessandrini:
> Il 02/09/2015 14:38, Jérémy Bobbio ha scritto:
> >Control: retitle -1 diffoscope: implement fuzzy-matching across containers
> >Control: severity -1 wishlist
> >
> >Michele Alessandrini:
> >>When comparing tar.gz or tar.bz2 archives cont
Control: tag -1 + pending
Jakub Wilk:
> I'd like an option for treating absent files as if they were empty, similar
> to "diff -N".
This has not been easy, but this will be in the next release
(--new-file is the switch).
--
Lunar.''`.
lu...@debian.org
retitle 788364 diffoscope: garbled output when comparing some Coreboot images
clone 788364 -1
reassign -1 libmagic1
severity -1 libmagic1 normal
retitle -1 libmagic1: misdetect Coreboot images as text files
thanks
Hi Christoph,
diffoscope is the tool that we have created as part of the “reproduci
Control: retitle -1 diffoscope: provide a way to ignore all differences in
control.tar
Jérémy Bobbio:
> Jakub Wilk:
> > I want to use diffoscope to compare two "Multi-Arch: same" debs of the same
> > version but different architecture, to see differences that will
Package: strip-nondeterminism
Severity: important
Hi!
I'm opening a bug report to track the following issue discussed on the
reproducible-builds mailing list:
Eugene Zhukov:
> On Mon, Sep 7, 2015 at 8:11 PM, Andrew Ayer wrote:
> > On Mon, 7 Sep 2015 19:49:56 +0300
> > Eugene Zhukov wrote:
> >>
[ Chris Lamb suggested to post the weekly reports that has been so far ]
[ available on Planet Debian to the mailing-list. Please tell us if]
[ you think that's not a good idea.]
What happened in the [1]reproducible builds effort this week:
Media coverag
Daniel Kahn Gillmor:
> Wiki page:
> > - EXECUTE_PROCESS(COMMAND "date" "-u" "-d @${SOURCE_DATE_EPOCH}"
> > "+%d/%m/%Y" OUTPUT_VARIABLE BUILD_DATE)
> […]
> Is there a reason above that this example code to translate from
> SOURCE_DATE_EPOCH to a build date doesn't produce ISO-8601-compliant
> dat
Ximin Luo:
> With our current .buildinfo setup, the above process is more
> complicated, because we *only* store hashes of the binary build
> environment.
I'm sorry but this is not accurate regarding the current
specification [1]. It says:
Build-Environment
List of all packages forming t
Jérémy Bobbio:
> For font compilation to be deterministic, we need a way to set the font
> modification time to a defined value instead of the current time.
>
> We thus add a new function “SetModificationTime” to the scripting language.
> It takes a single string argument looking l
dpkg_1.18.3.0~reproducible1.dsc has just been uploaded to
https://wiki.debian.org/ReproducibleBuilds/ExperimentalToolchain
___
Reproducible-builds mailing list
Reproducible-builds@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/li
Ximin Luo:
> > Implementation-wise, getting the hash of the .dsc in the .buildinfo is
> > going to be very tricky. dpkg does not know about what's available in
> > the archive. It just knows about packages which are or were installed.
> >
>
> `apt-cache showsrc [pkg]` has the right information in
Package: file
Version: 1:5.25-1
Severity: important
Hi!
The latest upload of file broke diffoscope test suite.
With file/1:5.24-2:
$ file --mime-encoding tests/data/binary1
tests/data/binary1: binary
With file/1:5.25-1:
$ file --mime-encoding tests/data/binary1
tests/data/bina
What happened in the [1]reproducible builds effort this week:
Media coverage
Nathan Willis covered [2]our DebConf15 status update in Linux
Weekly News. Access to non-LWN subscribers will be given on
Thursday 24th.
Linux Journal published a [3]more general piece last Tuesday.
U
diffoscope_36.dsc has just been uploaded to
https://wiki.debian.org/ReproducibleBuilds/ExperimentalToolchain
___
Reproducible-builds mailing list
Reproducible-builds@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/reprodu
Chris Lamb:
> I just ran into yet another package where the contents can vary
> depending on whether the tests are run or not.
>
> As an example, without tests a given Python package entirely vanilla and
> is thus reproducible in our toolchain. However, executing the tests
> creates various interm
What happened in the [1]reproducible builds effort this past week:
Toolchain fixes
* Ben Hutchings uploaded linux-tools/4.2-1 which makes the
tarball generated by genorig.py reproducible.
Packages fixed
The following 22 packages became reproducible due to changes in
their b
Santiago Vila:
> Using
>
> deb http://reproducible.alioth.debian.org/debian/ ./
>
> even the most simple package created makes lintian to complain:
> […]
I will not be able to look into this at least before the week-end. So
please beat me to it.
--
Lunar.''`.
l
Andreas Metzler:
> If we are aiming for locale agnostic builds we seem to take a
> unnecessary work intensive approach by adding
> export LC_ALL=C
> to dozens (hundreds?) of debian/rules or changing
> -sort
> +env LC_ALL= sort
> instead of simply patching dpkg-buildpackage.
Using `dpkg-buildpackag
What happened in the [1]reproducible builds effort this past week:
Toolchain fixes
Barry Warsaw uploaded wheel/0.26.0-1 which now uses
[2]SOURCE_DATE_EPOCH instead of WHEEL_FORCE_TIMESTAMP and
[3]uses time.gmtime() to avoid timezone issues. Patches by
Chris Lamb and Reiner Herrmann
dpkg_1.18.3.0~reproducible2.dsc has just been uploaded to
https://wiki.debian.org/ReproducibleBuilds/ExperimentalToolchain
___
Reproducible-builds mailing list
Reproducible-builds@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/li
retitle 801333 diffoscope: UnicodeDecodeError with
haskell-authenticate-oauth/1.5.1.1-4
clone 801333 -1
retitle -1 diffoscope: UnicodeDecodeError in test_text_option_with_file
severity -1 minor
thanks
Holger Levsen:
> someone just reported the same problem on irc: […]
It was not the same problem
Source: ognl
Version: 2.7.3-6
Severity: minor
User: reproducible-builds@lists.alioth.debian.org
Usertags: locale
Hi!
It seems that depending on the build system default character encoding,
the non-ASCII characters in org/ognl/test/QuotingTest.java might get
mistranslated.
This also prevents ongl
bnewb...@robocracy.org:
> 1. There's a statement that diffoscope "cannot detect .bin files as
> squashfs". I don't think that's accurate, I could rename .squashfs files to
> .bin and diffoscope found the magic and worked fine.
diffoscope currently recognizes Squashfs images using file(1). The
exte
Holger Levsen:
> On Freitag, 16. Oktober 2015, Santiago Vila wrote:
> > Hi. Do we expire issues (not packages) when no package currently have them?
>
> https://reproducible.debian.net/index_issues.html -> scroll down to the
> bottom.
>
> > (I would prefer to keep them).
>
> it depends, i'd say.
Santiago Vila:
> On Fri, Oct 16, 2015 at 01:40:22PM +0200, Jérémy Bobbio wrote:
> > I would say that it's better to keep any issue which other free software
> > projects might bump into.
>
> Agreed.
>
> > I know it's far from a clear guideline. In any
&
Santiago Vila:
> On Fri, Oct 16, 2015 at 03:22:34PM +0200, Jérémy Bobbio wrote:
> > I think it's sound to also remove issues due to Debian-specific
> > toolchain once it has been fixed. I don't think there's much value in
> > keeping tabs on something lik
Hi!
Esa, thanks for looking into these problems.
Esa Peuha:
> Santiago Vila:
> > For the same reason (not being build-essential), it is ok that it's
> > not pre-installed in pbuilder chroot, and in fact, usually it's not.
>
> Huh? How is the second build supposed to be able to set the locale to
Lunar:
> We already had an issue where locales-all was not providing everything
> that locales would provide. See #788352.
>
> I guess the fact that locales-all doesn't ship localedef can be
> considered as a bug. But the whole point of locales-all is that you
> don't need to build anything.
> […]
What happened in the [1]reproducible builds effort this week:
Toolchain fixes
* Scott Kitterman uploaded python3-defaults/3.4.3-7 which
changes py3versions to list versions in a consistent order.
Issue [2]reported by Santiago Vila with a tentative patch
by Chris Lamb.
What happened in the [1]reproducible builds effort this past week:
Toolchain fixes
* Stefano Rivera uploaded python-cffi/1.3.0-1 which makes the
generated code order deterministic for anonymous unions and
anonymous structs. [2]Reported by Tristan Seligmann, and
[3]fix
Rafael Laboissiere:
> I think that I found the culprit. The .oct files for octave are built using
> the mkoctfile program, as you pointed out above. This program uses default
> values for the the environment variables containing flags for the to C++
> compilation and binary link. For instance:
>
Sébastien Villemot:
> My understanding is that .oct files are stripped before creating the
> Debian package (by dh_strip). Hence they no longer contain debugging
> symbol. So removing -g at compilation time should make no difference.
The build id is generated by ld using a checksum of the whole bi
Johannes Schauer:
> Lunar:
> > Simon McVittie:
> > > BinNMUs don't upload any source at all. They instruct the autobuilders
> > > to run sbuild with some non-default options ("sbuild --binNMU=2
> > > --make-binNMU "Rebuild with foo 3" foo_1.2-3" will result in
> > > foo_1.2-3+b2_i386.changes, I thi
dpkg_1.18.4~reproducible1.dsc has just been uploaded to
https://wiki.debian.org/ReproducibleBuilds/ExperimentalToolchain
___
Reproducible-builds mailing list
Reproducible-builds@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/list
Dirk Eddelbuettel:
> One of my packages which still didn't build reproduciby is littler -- for
> which I am upstream. I rewrote the build process, and even though it produces
> a small binary (which embeds R for use in #! scripts etc) it now ships as an
> R package on CRAN. Which all build reprodu
Dirk Eddelbuettel:
> | From the quick look I had, it seems symbols are sorted in a different
> | order depending on the locale:
> |
> https://reproducible.debian.net/dbd/unstable/amd64/littler_0.3.0-2.debbindiff.html#r-cran-littler_0.3.0-2_amd64.deb/data.tar.xz/data.tar/./usr/bin/r/objdump%20--dis
Santiago Vila:
> I have very mixed feelings about this kind of patches.
>
> I fear that by modifying gcc to hide the improper usage of __DATE__
> and __TIME__, we could be removing an incentive for maintainers and
> authors to write software which is truly reproducible, i.e. we run
> the risk of p
Daniel Kahn Gillmor:
> index.html | 8
> 1 file changed, 4 insertions(+), 4 deletions(-)
Thanks, it's now live! :)
--
Lunar.''`.
lu...@debian.org: :Ⓐ : # apt-get install anarchism
`. `'`
What happened in the [1]reproducible builds effort this past week:
Toolchain fixes
Emmanuel Bourg uploaded eigenbase-resgen/1.3.0.13768-2 which
uses of the scm-safe comment style by default to make them
deterministic.
Mattia Rizzolo started a [2]new thread on debian-devel to ask a
Control: merge 805774 806149
Control: tag 805774 pending
Mattia Rizzolo:
> Seen on rb.d.n with openjfx/8u60-b27-4 on testing (trying it on unstable
> resulted with a FTBFS of the package...)
Same problem as #805774. Fixed in Git.
--
Lunar.''`.
lu...@debian.org
ree help2man by the one in the help2man package. Add
+ the required Build-Depends. The in-tree help2man doesn't support
+ SOURCE_DATE_EPOCH.
+- Set SOURCE_DATE_EPOCH to the date of the latest debian/changelog entry.
+
+ -- Jérémy Bobbio Thu, 26 Nov 2015 12:43:39 +0100
+
coreuti
Source: xz-utils
Version: 5.1.1alpha+20120614-2.1
Severity: wishlist
User: reproducible-builds@lists.alioth.debian.org
Usertags: timestamps
X-Debbugs-Cc: reproducible-builds@lists.alioth.debian.org, sanv...@debian.org
Hi!
While working on the “reproducible builds” effort [1], we have noticed
that
Source: xz-utils
Version: 5.1.1alpha+20120614-2.1
Severity: normal
User: reproducible-builds@lists.alioth.debian.org
Usertags: environment
X-Debbugs-Cc: reproducible-builds@lists.alioth.debian.org, sanv...@debian.org
Hi!
While working on the “reproducible builds” effort [1], we have noticed
that
Santiago Vila:
> Let's take cmucl as an example:
>
> Package: cmucl
> Architecture: i386 all
>
> It has "all", yes, but implicitly I take the Architecture line
> as saying that I should only try to build the "Arch: all" package
> using a i386 autobuilder.
>
>
> Does this make sense?
I think th
Santiago Vila:
> On Fri, Nov 27, 2015 at 11:12:50AM +0100, Jérémy Bobbio wrote:
> > I think the question can be phrased as: should architecture-independent
> > packages be buildable on all architectures?
> >
> > My own answer would be: yes, as long as they
Hi!
diffoscope is really growing bigger than just the Debian community, so
it felt better to create a dedicated mailing-list.
Please subscribe: https://lists.reproducible-builds.org/listinfo/diffoscope
--
Lunar.''`.
lu...@debian.org: :Ⓐ : #
Joachim Breitner:
> Multi-file HTML output
Really great idea. :) Thanks for the initial patch!
> +parser.add_argument('--jquery', metavar='url', dest='jquery_url',
> +help='link to the jquery url, with --html-dir. By
> default, a symlink to /usr/share/javascript/j
Axel Beckert:
> there seems to be a missing "" on https://diffoscope.org/ behind
> the link to http://brew.sh/. Well, actually it's a "" which
> behaves like a missing one.
Just fixed it. Thanks!
--
Lunar.''`.
lu...@debian.org: :Ⓐ : # apt-ge
Mike Hommey:
> It would be useful for diffoscope to output differences in omni.ja files as
> for other Zip files, instead of ending up with a diff of an hexdump.
>
> The attached patch implements a minimal support for this. It however doesn't
> look at the difference in the `preload` value.
Great
Control: tag -1 + pending
Mike Hommey:
> When there are differences in symbols-related sections of ELF files,
> symbols can be truncated if they are long enough. That happens often
> with C++ mangled symbols.
>
> The following patch fixes the issue: […]
Applied, thanks!
--
Lunar
Control: tag -1 + pending
Mattia Rizzolo:
> Seen on rb.d.n, with several packages, e.g.
> dhcpdump/1.8-2 on testing/amd64
> console-data/2:1.12-5 on testing/amd64
>
>
> Wed Dec 16 01:52:13 UTC 2015 - diffoscope 43 will be used to compare the two
> builds:
> Traceback (most recent call last):
>
Close: tag -1 + pending
Mike Hommey:
> Looking at the HTML in the HTML output, one can see that it is needlessly
> large.
>
> Specifically, there appears to be a lot of e.g.
> following each other, without even a separation between them. This conflates
> the amount of memory necessary for brows
Control: tag -1 + pending
Mike Hommey:
> On Tue, Dec 15, 2015 at 04:31:46PM +0100, Jérémy Bobbio wrote:
> > Mike Hommey:
> > > It would be useful for diffoscope to output differences in omni.ja files
> > > as
> > > for other Zip files, instead of
Mike Hommey:
> Here's another easy win, attached.
Nice. Commited. :)
--
Lunar.''`.
lu...@debian.org: :Ⓐ : # apt-get install anarchism
`. `'`
`-
signature.asc
Des
Esa Peuha:
> While we are at it, let's convert HTML character entity references
> (which each use 6-8 characters and as many bytes in the HTML file)
> to actual characters (which UTF-8 encodes as 2-3 bytes). Since all
> diffoscope output files are peppered with abundant amounts of these
> things, t
Control: tag -1 + pending
Mike Hommey:
>* What led up to the situation?
>
> Comparing two directories
>
>* What exactly did you do (or not do) that was effective (or
> ineffective)?
>
> Ran `diffoscope --html output.html a b` where a and b are directories
> containing
> more or le
Control: tag -1 + pending
Mike Hommey:
> Attached here is two files that can be compared directly, exposing the
> same problem. That's essentially the output of tar --full-time -tvf on
> both tarballs from the original bug report.
>
> The following patch fixes the numbering issue:
> […]
Commited
Control: tag -1 + pending
Mattia Rizzolo:
> TypeError: unorderable types: bytes() < str()
I've pushed a fix. Thanks for the report.
(This only appeared when the default encoding was not Unicode-aware.)
--
Lunar.''`.
lu...@debian.org: :Ⓐ :
Control: tag -1 + pending
Mike Hommey:
>* What was the outcome of this action?
>
> A 533KB HTML file that, considering its size, doesn't contain much
> differences.
> Yet, while processing this, the diffoscope process (not its children readelf,
> objdump or diff processes) sucked more than 4
kson
+.\" Copyright © 2000 Wichert Akkerman
+.\" Copyright © 2008-2010 Raphaël Hertzog
+.\" Copyright © 2006-2014 Guillem Jover
+.\" Copyright © 2015 Jérémy Bobbio
+.\"
+.\" This is free software; you can redistribute it and/or modify
+.\" it under the terms of
dpkg_1.18.5~reproducible1.dsc has just been uploaded to
https://wiki.debian.org/ReproducibleBuilds/ExperimentalToolchain
___
Reproducible-builds mailing list
Reproducible-builds@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/list
reassign 759886 dpkg-dev
retitle 759886 dpkg-dev: please make mtimes of packaged files deterministic
thanks
Hi!
The attached patch series is an attempt to make the mtimes of packaged
files deterministic. It is taken from the `pu/reproducible_builds`
dpkg branch maintained by the “reproducible bui
Jérémy Bobbio:
> dpkg_1.18.5~reproducible1.dsc has just been uploaded to
> https://wiki.debian.org/ReproducibleBuilds/ExperimentalToolchain
With this upload, we should not need a modified debhelper anymore. :)
See #759886.
--
Lunar.''`.
Manoj Srivastava:
> I was trying to import the new version of make into unstable, and
> I discovered that t/10 tests about the archive related part of makes
> test suite failed. The reason was a change in the behaviour of ar,
> which is now configured with --enable-deterministic-archives
Hi Mike!
Mike Hommey:
> When comparing large ELF binaries, some minor differences can end up hurting
> the visibility of more important differences.
>
> Specifically, objdump --disassemble displays symbols+offsets for addresses
> it derives from IP-relative addressing, like the following:
>
>
Control: tag -1 + pending
Mike Hommey:
> However, if each debug section was compared individually, that give more
> chance for diffoscope to work. (--debug-dump takes values allowing to treat
> each debug section independently)
Implemented by Dhole and currently available in the master branch.
-
Hi Mike,
Mike Hommey:
> When comparing ELF files, the following commands are used:
> - readelf --all
> - readelf --debug-dump
> - objdump --disassemble --full-contents
>
> objdump --disassemble --full-contents is actually redundant in itself. For
> example, it will dump both an hexdump and a disa
variable. More information at:
+ https://reproducible-builds.org/specs/source-date-epoch/
+Author: Jérémy Bobbio
+Last-Update: 2016-01-23
+
+--- libgcrypt20-1.6.4.orig/configure.ac
libgcrypt20-1.6.4/configure.ac
+@@ -1993,7 +1993,7 @@ changequote([,])dnl
+ BUILD_FILEVERSION="${BUI
Control: tag -1 + pending
Mattia Rizzolo:
> File "/usr/lib/python3.5/encodings/ascii.py", line 26, in decode
> return codecs.ascii_decode(input, self.errors)[0]
> UnicodeDecodeError: 'ascii' codec can't decode byte 0xc3 in position 95:
> ordinal not in range(128)
Fixed in 00b26a6.
--
Lun
Control: tag -1 + pending
Mattia Rizzolo:
> File "/usr/lib/python3/dist-packages/diffoscope/comparators/debian.py",
> line 185, in recognizes
> for d in buildinfo.get('Checksums-Sha256'):
> TypeError: 'NoneType' object is not iterable
Already fixed in af6bcf80.
--
Lunar
Source: findutils
Version: 4.6.0-2
Severity: important
User: reproducible-builds@lists.alioth.debian.org
Usertag: ftbfs
Hi!
findutils will FTBFS due to test errors if fr_FR or a couple other
locales are installed. The failing tests are test-mbrtowc{1,2,3,4}.sh.
The log contains:
test-mbrtowc
Control: tag -1 + patch
Raphael Hertzog:
> On Mon, 14 Dec 2015, Raphael Hertzog wrote:
> > Your analysis is correct but dh_strip_nondeterminisn should detect the
> > signature and avoid messing up with the file in that case.
> >
> > That's what this bug is about.
>
> And we got another case wher
Jérémy Bobbio:
> The attached patch will enable dpkg-buildpackage to create .buildinfo
> files as specified on the Debian wiki [1]. They have two main purposes:
>
> * recording information about the system environment used during a
>particular build—versions of the bui
Source: glib2.0
Version: 2.46.2-3
Severity: wishlist
Tags: patch
User: reproducible-builds@lists.alioth.debian.org
Usertags: locale
Hi!
While working on the “reproducible builds” effort [1], we have noticed
that glib2.0 could not be built reproducibly.
The attached patch ensure that functions ar
libxslt_1.1.28-2.1.0~reproducible2.dsc has just been uploaded to
https://wiki.debian.org/ReproducibleBuilds/ExperimentalToolchain
___
Reproducible-builds mailing list
Reproducible-builds@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mai
Source: libxml++2.6
Version: 2.40.1-1
Severity: wishlist
Tags: patch
User: reproducible-builds@lists.alioth.debian.org
Usertags: environment
Hi!
While working on the “reproducible builds” effort [1], we have noticed
that libxml++2.6 could not be built reproducibly.
The reason is that the entire
Source: libsm
Version: 2:1.2.2-1
Severity: wishlist
Tags: patch
User: reproducible-builds@lists.alioth.debian.org
Usertags: locale
Hi!
While working on the “reproducible builds” effort [1], we have noticed
that libsm could not be built reproducibly.
The attached patch makes sure the text documen
Guillem Jover:
> I've some pending changes I'll be committing to master or a separate
> branch, that I'd like to be tested on the reproducible setup (ideally
> against the already generated and pre-existing reproducible binaries),
> if that's possible, I'll ask about that when those land, I just ne
Helmut Grohne:
> Even though I cannot reproduce the issue at hand, I think that the code
> adding automatic debug symbols looks fishy to me. It appears to recurse
> over /tmp here and that looks very wrong to me.
I don't understand what you mean by that. Could you provide be (at least
some) of the
Guillem Jover:
> > One of the main change is that `.buildinfo` should now be named with an
> > arbitrary identifier. By default this defaults to $HOSTNAME-$TIMESTAMP
> > but can be set to an arbitrary value by the `--buildinfo-identifier`
> > command line flag.
>
> Hmmm, leaking the hostname seems
1 - 100 of 503 matches
Mail list logo
