Re: [Reproducible-builds] package uploaded to our repo
On Thu, Oct 08, 2015 at 05:39:53PM +, Jérémy Bobbio wrote: > dpkg_1.18.3.0~reproducible2.dsc has just been uploaded [...] Note: This release finally fixes the duplicate-files-in-control.tar.gz problem I reported a few days ago: http://lists.alioth.debian.org/pipermail/reproducible-builds/Week-of-Mon-20150928/003440.html Thanks. ___ Reproducible-builds mailing list Reproducible-builds@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/reproducible-builds
[Reproducible-builds] Bug#801333: [diffoscope] UnicodeDecodeError with haskell-authenticate-oauth/1.5.1.1-4
Package: diffoscope Version: 36 seen in rb.d.n: in experimental, haskell-authenticate-oauth/1.5.1.1-4: Traceback (most recent call last): File "/usr/lib/python3/dist-packages/diffoscope/__main__.py", line 137, in main sys.exit(run_diffoscope(parsed_args)) File "/usr/lib/python3/dist-packages/diffoscope/__main__.py", line 114, in run_diffoscope parsed_args.file1, parsed_args.file2) File "/usr/lib/python3/dist-packages/diffoscope/comparators/__init__.py", line 81, in compare_root_paths return compare_files(file1, file2) File "/usr/lib/python3/dist-packages/diffoscope/comparators/__init__.py", line 98, in compare_files return file1.compare(file2, source) File "/usr/lib/python3/dist-packages/diffoscope/comparators/binary.py", line 78, in wrapper return original_method(self, other, *args, **kwargs) File "/usr/lib/python3/dist-packages/diffoscope/comparators/binary.py", line 176, in compare difference = self._compare_using_details(other, source) File "/usr/lib/python3/dist-packages/diffoscope/comparators/binary.py", line 149, in _compare_using_details details = [d for d in self.compare_details(other, source) if d is not None] File "/usr/lib/python3/dist-packages/diffoscope/comparators/binary.py", line 78, in wrapper return original_method(self, other, *args, **kwargs) File "/usr/lib/python3/dist-packages/diffoscope/comparators/debian.py", line 143, in compare_details differences.extend(my_container.compare(other_container)) File "/usr/lib/python3/dist-packages/diffoscope/comparators/utils.py", line 199, in compare return list(starmap(diffoscope.comparators.compare_commented_files, self.comparisons(other))) File "/usr/lib/python3/dist-packages/diffoscope/comparators/__init__.py", line 101, in compare_commented_files difference = compare_files(file1, file2, source=source) File "/usr/lib/python3/dist-packages/diffoscope/comparators/__init__.py", line 98, in compare_files return file1.compare(file2, source) File "/usr/lib/python3/dist-packages/diffoscope/comparators/binary.py", line 78, in wrapper return original_method(self, other, *args, **kwargs) File "/usr/lib/python3/dist-packages/diffoscope/comparators/binary.py", line 176, in compare difference = self._compare_using_details(other, source) File "/usr/lib/python3/dist-packages/diffoscope/comparators/binary.py", line 149, in _compare_using_details details = [d for d in self.compare_details(other, source) if d is not None] File "/usr/lib/python3/dist-packages/diffoscope/comparators/binary.py", line 78, in wrapper return original_method(self, other, *args, **kwargs) File "/usr/lib/python3/dist-packages/diffoscope/comparators/deb.py", line 84, in compare_details differences.extend(my_container.compare(other_container)) File "/usr/lib/python3/dist-packages/diffoscope/comparators/utils.py", line 199, in compare return list(starmap(diffoscope.comparators.compare_commented_files, self.comparisons(other))) File "/usr/lib/python3/dist-packages/diffoscope/comparators/__init__.py", line 101, in compare_commented_files difference = compare_files(file1, file2, source=source) File "/usr/lib/python3/dist-packages/diffoscope/comparators/__init__.py", line 98, in compare_files return file1.compare(file2, source) File "/usr/lib/python3/dist-packages/diffoscope/comparators/binary.py", line 78, in wrapper return original_method(self, other, *args, **kwargs) File "/usr/lib/python3/dist-packages/diffoscope/comparators/binary.py", line 176, in compare difference = self._compare_using_details(other, source) File "/usr/lib/python3/dist-packages/diffoscope/comparators/binary.py", line 149, in _compare_using_details details = [d for d in self.compare_details(other, source) if d is not None] File "/usr/lib/python3/dist-packages/diffoscope/comparators/binary.py", line 78, in wrapper return original_method(self, other, *args, **kwargs) File "/usr/lib/python3/dist-packages/diffoscope/comparators/xz.py", line 69, in compare_details return my_container.compare(other_container) File "/usr/lib/python3/dist-packages/diffoscope/comparators/utils.py", line 199, in compare return list(starmap(diffoscope.comparators.compare_commented_files, self.comparisons(other))) File "/usr/lib/python3/dist-packages/diffoscope/comparators/__init__.py", line 101, in compare_commented_files difference = compare_files(file1, file2, source=source) File "/usr/lib/python3/dist-packages/diffoscope/comparators/__init__.py", line 98, in compare_files return file1.compare(file2, source) File "/usr/lib/python3/dist-packages/diffoscope/comparators/binary.py", line 78, in wrapper return original_method(self, other, *args, **kwargs) File "/usr/lib/python3/dist-packages/diffoscope/comparators/binary.py", line 176, in compare difference = self._compare_using_details(other, source) File "/usr/lib/python3/dist-packages/
[Reproducible-builds] package uploaded to our repo
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/listinfo/reproducible-builds
Re: [Reproducible-builds] Build environment changes between build1 and build2
On Donnerstag, 8. Oktober 2015, Holger Levsen wrote: > btw, the build results today are also still broken: seems I've fixed this by now. signature.asc Description: This is a digitally signed message part. ___ Reproducible-builds mailing list Reproducible-builds@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/reproducible-builds
Re: [Reproducible-builds] Build environment changes between build1 and build2
Hi, On Donnerstag, 8. Oktober 2015, Santiago Vila wrote: > If we are unable to reproduce the environment to begin with, i.e. if > we don't even give the package the opportunity to show that it's > reproducible, then it is not the package's fault, and I see no reason > to mark it as unreproducible. agreed. I've just applied a fix so that in these cases the package will be rescheduled, instead of being marked unreproducible. cheers, Holger signature.asc Description: This is a digitally signed message part. ___ Reproducible-builds mailing list Reproducible-builds@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/reproducible-builds
Re: [Reproducible-builds] Build environment changes between build1 and build2
On Thu, Oct 08, 2015 at 03:25:38PM +, Santiago Vila wrote: > under the "same" environment (build-depends) Sorry, I really meant "installed packages and their versions" here. ___ Reproducible-builds mailing list Reproducible-builds@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/reproducible-builds
Re: [Reproducible-builds] Build environment changes between build1 and build2
On Thu, Oct 08, 2015 at 03:01:34PM +, Mattia Rizzolo wrote: > If that fields differs again [...] it just gives up and mark the > package as unreproducible The last item (mark as unreproducible) does not seem right to me. A package is said to be reproducible when you build it two times under the "same" environment (build-depends) and the result is the same. If we are unable to reproduce the environment to begin with, i.e. if we don't even give the package the opportunity to show that it's reproducible, then it is not the package's fault, and I see no reason to mark it as unreproducible. Thanks. ___ Reproducible-builds mailing list Reproducible-builds@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/reproducible-builds
Re: [Reproducible-builds] Build environment changes between build1 and build2
On Thu, Oct 08, 2015 at 04:55:35PM +0200, Holger Levsen wrote: > Hi, > > On Donnerstag, 8. Oktober 2015, Santiago Vila wrote: > > I've seen several cases where a package is considered not reproducible > > just because the build environment changed between build1 and build2. > > this should not happen… end of the story. If it happens, its a bug in the CI. > > and today it also happened because of adding the new builders... (i'll spare > myself explaining the exact details, just we dont add builders every day, so > meh.) > > > However, I can think of some workarounds: > > yes, we too… > > I'm sorry but I'm severely overloaded and these problems are well known, well > discussed and being worked on. Explaining them here again, just takes away > time to work on these issues. Well, long story short: the build script compares the two .buildinfo just after the build and if Build-Environment differes it re-runs the build a 3rd time. If that fields differs again (this might be the case for very long running builds that spawn several dinstall and different toolchain packages change during the day) it just gives up and mark the package as unreproducible > It might be helpful to join irc to discuss with us in realtime. Agree, be assured discussing some stuff on IRC is really quicker than email. Though when it comes to #debian-reproducible following everything might be sometimes annoying due to the volume of the chats, but imho is still worthwhile :) -- regards, Mattia Rizzolo GPG Key: 66AE 2B4A FCCF 3F52 DA18 4D18 4B04 3FCD B944 4540 .''`. more about me: http://mapreri.org : :' : Launchpad user: https://launchpad.net/~mapreri `. `'` Debian QA page: https://qa.debian.org/developer.php?login=mattia `- signature.asc Description: PGP signature ___ Reproducible-builds mailing list Reproducible-builds@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/reproducible-builds
Re: [Reproducible-builds] Build environment changes between build1 and build2
Hi, btw, the build results today are also still broken: context: https://reproducible.debian.net/unstable/amd64/sagasu [16:23] < h01ger> | something looks very fishy here [16:24] < h01ger> | but i dont get what [16:25] < h01ger> | the diffoscope diff of the unreproducible builds .buildinfo files look fine, and so does the .buildinfo file itself [16:25] < h01ger> | debhelper (= 9.20151005.0~reproducible2), [16:25] < h01ger> | dpkg (= 1.18.3.0~reproducible1), [16:25] < h01ger> | dpkg-dev (= 1.18.3.0~reproducible1), [16:26] < h01ger> | there are also still reproducible builds happening, eg https://reproducible.debian.net/rb-pkg/unstable/amd64/doc-linux-hr.html from 10min ago I will probably not time to debug this today. Help welcome. cheers, Holger signature.asc Description: This is a digitally signed message part. ___ Reproducible-builds mailing list Reproducible-builds@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/reproducible-builds
Re: [Reproducible-builds] Build environment changes between build1 and build2
Hi, On Donnerstag, 8. Oktober 2015, Santiago Vila wrote: > I've seen several cases where a package is considered not reproducible > just because the build environment changed between build1 and build2. this should not happen… end of the story. If it happens, its a bug in the CI. and today it also happened because of adding the new builders... (i'll spare myself explaining the exact details, just we dont add builders every day, so meh.) > However, I can think of some workarounds: yes, we too… I'm sorry but I'm severely overloaded and these problems are well known, well discussed and being worked on. Explaining them here again, just takes away time to work on these issues. It might be helpful to join irc to discuss with us in realtime. cheers, Holger signature.asc Description: This is a digitally signed message part. ___ Reproducible-builds mailing list Reproducible-builds@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/reproducible-builds
[Reproducible-builds] Build environment changes between build1 and build2
Hi. I've seen several cases where a package is considered not reproducible just because the build environment changed between build1 and build2. It would be great if, by design, this did never happen, but I understand this will not be easy to implement. However, I can think of some workarounds: * If the only difference is in the buildinfo files, consider that the package is reproducible. * If the buildinfo files differ, discard everything and put the package in the queue again. * Do not start any build for some amount of time before the mirror pulse, to avoid either build1 or build2 to happen in the middle of a mirror sync. The problem with this is that we don't know when the mirror sync will happen. * Start build1 and build2 at the same time in different jobs (this is not such a silly idea considering that we have a lot of processors). * Make build1 and build2 in the same job (not in two independent ones). Hopefully, the build-dependencies installed for build1 will serve for build2 as well, since the source package is still the same. Just do not remove them between build1 and build2. Sorry not to be a programmer myself, but I hope some of these ideas make some sense. Thanks. ___ Reproducible-builds mailing list Reproducible-builds@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/reproducible-builds
