[Reproducible-builds] Bug#797855: spice-gtk:spice-common/common/generated_* not reliably generated from source
Source: spice-gtk Version: 0.29-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 Hi, The spice-common/common/generated_* files are not reliably regenerated from source. Depending on the timezone of the build system, the package may FTBFS as the `spice-common/python_modules/codegen.py` tool used to regenerate these files requires python-six which is not included in the Build-Depends. (ie. I don't believe simply including python-six as a build-dependency entirely resolves the issue) Here's the build running in, for example, TZ=/usr/share/zoneinfo/Etc/GMT-14 [..] Making all in common make[5]: Entering directory '/tmp/buildd/spice-gtk-0.29/build-gtk3/spice-common/common' GEN generated_client_demarshallers.c Traceback (most recent call last): File "../spice_codegen.py", line 7, in from python_modules import spice_parser File "/tmp/buildd/spice-gtk-0.29/build-gtk3/spice-common/python_modules/spice_parser.py", line 10, in from . import ptypes File "/tmp/buildd/spice-gtk-0.29/build-gtk3/spice-common/python_modules/ptypes.py", line 1, in from . import codegen File "/tmp/buildd/spice-gtk-0.29/build-gtk3/spice-common/python_modules/codegen.py", line 2, in import six ImportError: No module named six Makefile:788: recipe for target 'generated_client_demarshallers.c' failed make[5]: *** [generated_client_demarshallers.c] Error 1 make[5]: Leaving directory '/tmp/buildd/spice-gtk-0.29/build-gtk3/spice-common/common' Makefile:444: recipe for target 'all-recursive' failed make[4]: *** [all-recursive] Error 1 make[4]: Leaving directory '/tmp/buildd/spice-gtk-0.29/build-gtk3/spice-common' Makefile:376: recipe for target 'all' failed make[3]: *** [all] Error 2 make[3]: Leaving directory '/tmp/buildd/spice-gtk-0.29/build-gtk3/spice-common' Makefile:667: recipe for target 'all-recursive' failed make[2]: *** [all-recursive] Error 1 make[2]: Leaving directory '/tmp/buildd/spice-gtk-0.29/build-gtk3' Makefile:570: recipe for target 'all' failed make[1]: *** [all] Error 2 make[1]: Leaving directory '/tmp/buildd/spice-gtk-0.29/build-gtk3' debian/rules:42: recipe for target 'build-gtk3-stamp' failed make: *** [build-gtk3-stamp] Error 2 dpkg-buildpackage: error: debian/rules build gave error exit status 2 [..] The full build log is attached or can be viewed here: https://reproducible.debian.net/logs/unstable/amd64/spice-gtk_0.29-1.build2.log.gz Regards, -- ,''`. : :' : Chris Lamb `. `'` la...@debian.org / chris-lamb.co.uk `- ___ Reproducible-builds mailing list Reproducible-builds@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/reproducible-builds
[Reproducible-builds] Bug#797854: libsixel: Missing Build-Depends on python
Source: libsixel
Version: 1.5.2-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
Tags: patch
Dear Maintainer,
libsixel fails to build from source in unstable/amd64 due
to missing Build-Depends on python:
[..]
configure:15220: checking for a Python interpreter with version >= 2.3
configure:15237: python -c import sys # split strings by '.' and
convert to numeric. Append some zeros # because we need at least 4
digits for the hex conversion. # map returns an iterator in Python 3.0
and a list in 2.x minver = list(map(int, '2.3'.split('.'))) + [0, 0,
0] minverhex = 0 # xrange is not present in Python 3.0 and range
returns an iterator for i in list(range(0, 4)): minverhex = (minverhex
<< 8) + minver[i] sys.exit(sys.hexversion < minverhex)
./configure: line 15238: python: command not found
configure:15240: $? = 127
configure:15237: python2 -c import sys # split strings by '.' and
convert to numeric. Append some zeros # because we need at least 4
digits for the hex conversion. # map returns an iterator in Python 3.0
and a list in 2.x minver = list(map(int, '2.3'.split('.'))) + [0, 0,
0] minverhex = 0 # xrange is not present in Python 3.0 and range
returns an iterator for i in list(range(0, 4)): minverhex = (minverhex
<< 8) + minver[i] sys.exit(sys.hexversion < minverhex)
./configure: line 15238: python2: command not found
configure:15240: $? = 127
configure:15237: python3 -c import sys # split strings by '.' and
convert to numeric. Append some zeros # because we need at least 4
digits for the hex conversion. # map returns an iterator in Python 3.0
and a list in 2.x minver = list(map(int, '2.3'.split('.'))) + [0, 0,
0] minverhex = 0 # xrange is not present in Python 3.0 and range
returns an iterator for i in list(range(0, 4)): minverhex = (minverhex
<< 8) + minver[i] sys.exit(sys.hexversion < minverhex)
./configure: line 15238: python3: command not found
configure:15240: $? = 127
configure:15237: python3.3 -c import sys # split strings by '.' and
convert to numeric. Append some zeros # because we need at least 4
digits for the hex conversion. # map returns an iterator in Python 3.0
and a list in 2.x minver = list(map(int, '2.3'.split('.'))) + [0, 0,
0] minverhex = 0 # xrange is not present in Python 3.0 and range
returns an iterator for i in list(range(0, 4)): minverhex = (minverhex
<< 8) + minver[i] sys.exit(sys.hexversion < minverhex)
./configure: line 15238: python3.3: command not found
configure:15240: $? = 127
configure:15237: python3.2 -c import sys # split strings by '.' and
convert to numeric. Append some zeros # because we need at least 4
digits for the hex conversion. # map returns an iterator in Python 3.0
and a list in 2.x minver = list(map(int, '2.3'.split('.'))) + [0, 0,
0] minverhex = 0 # xrange is not present in Python 3.0 and range
returns an iterator for i in list(range(0, 4)): minverhex = (minverhex
<< 8) + minver[i] sys.exit(sys.hexversion < minverhex)
./configure: line 15238: python3.2: command not found
configure:15240: $? = 127
configure:15237: python3.1 -c import sys # split strings by '.' and
convert to numeric. Append some zeros # because we need at least 4
digits for the hex conversion. # map returns an iterator in Python 3.0
and a list in 2.x minver = list(map(int, '2.3'.split('.'))) + [0, 0,
0] minverhex = 0 # xrange is not present in Python 3.0 and range
returns an iterator for i in list(range(0, 4)): minverhex = (minverhex
<< 8) + minver[i] sys.exit(sys.hexversion < minverhex)
./configure: line 15238: python3.1: command not found
configure:15240: $? = 127
configure:15237: python3.0 -c import sys # split strings by '.' and
convert to numeric. Append some zeros # because we need at least 4
digits for the hex conversion. # map returns an iterator in Python 3.0
and a list in 2.x minver = list(map(int, '2.3'.split('.'))) + [0, 0,
0] minverhex = 0 # xrange is not present in Python 3.0 and range
returns an iterator for i in list(range(0, 4)): minverhex = (minverhex
<< 8) + minver[i] sys.exit(sys.hexversion < minverhex)
./configure: line 15238: python3.0: command not found
configure:15240: $? = 127
configure:15237: python2.7 -c import sys # split strings by '.' and
convert to numeric. Append some zeros # because we need at least 4
digits for the hex conversion. # map returns an iterator in Python 3.0
and a list in 2.x minver = list(map(int, '2.3'.split('.'))) + [0, 0,
0] minverhex = 0 # xrange is not present in Python 3.0 and range
returns an iterator for i in list(range(0, 4)): minverhex = (minverhex
<< 8) + minver[i] sys.exit(sys.hexversion < minverhex)
./configure: line 15238: python2.7: command not found
configure:15240: $? = 127
configure:15237: python2.6 -c import sys # split strings by '.' and
conv
[Reproducible-builds] Bug#797759: Bug#797759: Bug#797759: diffoscope: tar.gz and tar.bz2 archives compared wrongly
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 containing text files, some > >>of which different, the output is a binary diff. Perhaps it only > >>applies decompression and compares the two tar files, instead of their > >>contents? > > > >That can be implemented by adding support for fuzzy-matching across > >containers. This would also detect and compare properly a file being > >compressed from one version to the next. > > > >It's doable. The trickiest part in my mind so far is where to attach > >them in the tree of differences. > > > > But isn't reading files inside archives a main feature of diffoscope? It is. But .gz and .bz2 are two different file formats and diffoscope treat them as such. It's like switching from .tar to .zip. It's quite a difference and diffoscope will not blindly compare their content currently. Trust me, fuzzy matching accross containers is doable and will solve exactly this problem, but also others. -- Lunar.''`. lu...@debian.org: :Ⓐ : # apt-get install anarchism `. `'` `- signature.asc Description: Digital signature ___ Reproducible-builds mailing list Reproducible-builds@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/reproducible-builds
[Reproducible-builds] Bug#797759: Bug#797759: diffoscope: tar.gz and tar.bz2 archives compared wrongly
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 containing text files, some of which different, the output is a binary diff. Perhaps it only applies decompression and compares the two tar files, instead of their contents? That can be implemented by adding support for fuzzy-matching across containers. This would also detect and compare properly a file being compressed from one version to the next. It's doable. The trickiest part in my mind so far is where to attach them in the tree of differences. But isn't reading files inside archives a main feature of diffoscope? ___ Reproducible-builds mailing list Reproducible-builds@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/reproducible-builds
[Reproducible-builds] [PATCH] As a special probably temporary case, use our non-Debian URL for specs.
Hi, Please merge from the "use-dot-org-for-specs-for-now" branch of https://github.com/lamby/jenkins.debian.net: commit 33aaf58455f742e466f191452cfb162227ea65d5 Author: Chris Lamb Date: Wed Sep 2 15:29:45 2015 +0100 As a special probably temporary case, use our non-Debian URL for specs. Mostly to avoid "Debian" in the URL. Signed-off-by: Chris Lamb bin/reproducible_common.sh | 1 + bin/reproducible_html_specs.sh | 2 +- 2 files changed, 2 insertions(+), 1 deletion(-) Regards, -- ,''`. : :' : Chris Lamb `. `'` la...@debian.org / chris-lamb.co.uk `- ___ Reproducible-builds mailing list Reproducible-builds@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/reproducible-builds
[Reproducible-builds] Processed: Re: Bug#797781: diffoscope does not seem to work with schroot
Processing commands for cont...@bugs.debian.org: > reassign 797781 schroot Bug #797781 [diffoscope] diffoscope does not seem to work with schroot Bug reassigned from package 'diffoscope' to 'schroot'. No longer marked as found in versions diffoscope/31. Ignoring request to alter fixed versions of bug #797781 to the same values previously set > retitle 797781 /dev/shm line is commented out by default but it's required by > a lot of stuff Bug #797781 [schroot] diffoscope does not seem to work with schroot Changed Bug title to '/dev/shm line is commented out by default but it's required by a lot of stuff' from 'diffoscope does not seem to work with schroot' > thanks Stopping processing here. Please contact me if you need assistance. -- 797781: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=797781 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ___ Reproducible-builds mailing list Reproducible-builds@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/reproducible-builds
Re: [Reproducible-builds] SOURCE_DATE_EPOCH specification document
> I'll wait a few days, proof-read a more few times and then declare it > published. I declare this version 1.0: https://reproducible-builds.org/specs/source-date-epoch/ I completely gutted what we had previously as I felt the justifications were -- at best -- a distraction. A sincere thank-you to all; even if your own literal words do not remain in the document, it was extremely vital to the process. Regards, -- ,''`. : :' : Chris Lamb `. `'` la...@debian.org / chris-lamb.co.uk `- ___ Reproducible-builds mailing list Reproducible-builds@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/reproducible-builds
Re: [Reproducible-builds] Bug#797781: Bug#797781: diffoscope does not seem to work with schroot
On Wed, Sep 02, 2015 at 02:08:42PM +, Mattia Rizzolo wrote: > Well, quite a lot of stuff requires shm nowadays. > > Consider that we rb people run diffoscope inside scrhoot, and it just > works. We have > > /dev/shm/dev/shmnonerw,bind 0 0 > > in /etc/schroot/default/fstab. > > > Personally I'd not consider this a diffoscope bug. Thanks, will reassign to schroot, then. Packages should have sane defaults. ___ Reproducible-builds mailing list Reproducible-builds@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/reproducible-builds
[Reproducible-builds] Bug#797781: Bug#797781: diffoscope does not seem to work with schroot
On Wed, Sep 02, 2015 at 01:41:23PM +, Santiago Vila wrote: > Package: diffoscope > Version: 31 > > Greetings. I'm running jessie with several chroots created with > schroot. As a normal user, I do this: > > schroot -c sid > diffoscope some.deb someother.deb > > and this is the result: > > CRITICAL /dev/shm is not available or not on a tmpfs. Unable to create > semaphore. > > I believe such error is not supposed to happen. Well, quite a lot of stuff requires shm nowadays. Consider that we rb people run diffoscope inside scrhoot, and it just works. We have /dev/shm/dev/shmnonerw,bind 0 0 in /etc/schroot/default/fstab. Personally I'd not consider this a diffoscope bug. -- 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: Digital signature ___ Reproducible-builds mailing list Reproducible-builds@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/reproducible-builds
[Reproducible-builds] Bug#797781: diffoscope does not seem to work with schroot
Package: diffoscope Version: 31 Greetings. I'm running jessie with several chroots created with schroot. As a normal user, I do this: schroot -c sid diffoscope some.deb someother.deb and this is the result: CRITICAL /dev/shm is not available or not on a tmpfs. Unable to create semaphore. I believe such error is not supposed to happen. 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#797777: ntopng: Missing Build-Depends on pkg-config
Source: ntopng
Version: 1.2.1+dfsg1-2
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
Tags: patch
Dear Maintainer,
ntopng fails to build from source in unstable/amd64 due to missing
Build-Depends on pkg-config:
[..]
dh_auto_build
make -j1
make[2]: Entering directory '/tmp/buildd/ntopng-1.2.1+dfsg1'
/bin/sh: 1: pkg-config: not found
/bin/sh: 1: pkg-config: not found
/bin/sh: 1: pkg-config: not found
/bin/sh: 1: pkg-config: not found
/bin/sh: 1: pkg-config: not found
/bin/sh: 1: pkg-config: not found
/bin/sh: 1: pkg-config: not found
/bin/sh: 1: pkg-config: not found
/bin/sh: 1: pkg-config: not found
svn co https://svn.ntop.org/svn/ntop/trunk/nDPI/
make[2]: svn: Command not found
Makefile:136: recipe for target 'nDPI' failed
make[2]: *** [nDPI] Error 127
make[2]: Leaving directory '/tmp/buildd/ntopng-1.2.1+dfsg1'
dh_auto_build: make -j1 returned exit code 2
debian/rules:13: recipe for target 'override_dh_auto_build' failed
make[1]: *** [override_dh_auto_build] Error 2
make[1]: Leaving directory '/tmp/buildd/ntopng-1.2.1+dfsg1'
debian/rules:10: recipe for target 'build' failed
make: *** [build] Error 2
dpkg-buildpackage: error: debian/rules build gave error exit status 2
[..]
The full build log is attached or can be viewed here:
https://reproducible.debian.net/logs/unstable/amd64/ntopng_1.2.1+dfsg1-2.build1.log.gz
Regards,
--
,''`.
: :' : Chris Lamb
`. `'` la...@debian.org / chris-lamb.co.uk
`-
I: using fakeroot in build.
I: pbuilder: network access will be disabled during build
I: Current time: Tue Sep 1 08:04:44 GMT+12 2015
I: pbuilder-time-stamp: 1441137884
I: Building the build Environment
I: extracting base tarball [/var/cache/pbuilder/unstable-reproducible-base.tgz]
I: creating local configuration
I: copying local configuration
I: mounting /proc filesystem
I: mounting /run/shm filesystem
I: mounting /dev/pts filesystem
I: Mounting /dev/shm
I: Mounting /sys
I: policy-rc.d already exists
I: Installing the build-deps
-> Attempting to satisfy build-dependencies
-> Creating pbuilder-satisfydepends-dummy package
Package: pbuilder-satisfydepends-dummy
Version: 0.invalid.0
Architecture: amd64
Maintainer: Debian Pbuilder Team
Description: Dummy package to satisfy dependencies with aptitude - created by
pbuilder
This package was created automatically by pbuilder to satisfy the
build-dependencies of the package being currently built.
Depends: debhelper (>= 9.0.0), dh-autoreconf, dh-systemd (>= 1.5), dpkg (>=
1.15.7.2), coffeescript, libgeoip-dev, libhiredis-dev, libjson-c-dev,
libluajit-5.1-dev, libndpi-dev (>= 1.4.0+svn8032), libpcap-dev, librrd-dev,
libsqlite3-dev, libzmq3-dev
dpkg-deb: building package 'pbuilder-satisfydepends-dummy' in
'/tmp/satisfydepends-aptitude/pbuilder-satisfydepends-dummy.deb'.
Selecting previously unselected package pbuilder-satisfydepends-dummy.
(Reading database ... 20255 files and directories currently installed.)
Preparing to unpack .../pbuilder-satisfydepends-dummy.deb ...
Unpacking pbuilder-satisfydepends-dummy (0.invalid.0) ...
dpkg: pbuilder-satisfydepends-dummy: dependency problems, but configuring
anyway as you requested:
pbuilder-satisfydepends-dummy depends on dh-autoreconf; however:
Package dh-autoreconf is not installed.
pbuilder-satisfydepends-dummy depends on dh-systemd (>= 1.5); however:
Package dh-systemd is not installed.
pbuilder-satisfydepends-dummy depends on coffeescript; however:
Package coffeescript is not installed.
pbuilder-satisfydepends-dummy depends on libgeoip-dev; however:
Package libgeoip-dev is not installed.
pbuilder-satisfydepends-dummy depends on libhiredis-dev; however:
Package libhiredis-dev is not installed.
pbuilder-satisfydepends-dummy depends on libjson-c-dev; however:
Package libjson-c-dev is not installed.
pbuilder-satisfydepends-dummy depends on libluajit-5.1-dev; however:
Package libluajit-5.1-dev is not installed.
pbuilder-satisfydepends-dummy depends on libndpi-dev (>= 1.4.0+svn8032);
however:
Package libndpi-dev is not installed.
pbuilder-satisfydepends-dummy depends on
Setting up pbuilder-satisfydepends-dummy (0.invalid.0) ...
Reading package lists...
Building dependency tree...
Reading state information...
Initializing package states...
Writing extended state information...
Building tag database...
The following NEW packages will be installed:
autoconf{a} automake{a} autopoint{a} autotools-dev{a} coffeescript{a}
dh-autoreconf{a} dh-systemd{a} fontconfig{a} fontconfig-config{a}
fonts-dejavu-core{a} geoip-bin{a} libc-ares2{a} libcairo2{a}
libdatrie1{a} libdbi1{a} libexpat1{a} libfontconfig1{a} libfreetype6{a}
libgeoip-dev{a} libgeoip1{a} libgraphite2-3{a} libharfbuzz0b{a}
libhiredis-dev{a} libhiredis0.13{a} libjson-c-dev{a} libjson-c2{a}
libl
[Reproducible-builds] Bug#797776: pygpgme: FTBFS: Ran 55 tests in 54.866s: FAILED (failures=2, errors=2)
Source: pygpgme
Version: 0.3-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,
pygpgme fails to build from source in unstable/amd64:
[..]
==
ERROR: test_sign_with_passphrase_cb
(tests.test_passphrase.PassphraseTestCase)
--
Traceback (most recent call last):
File "/tmp/buildd/pygpgme-0.3/tests/test_passphrase.py", line 60, in
test_sign_with_passphrase_cb
key = ctx.get_key('EFB052B4230BBBC51914BCBB54DCBBC8DBFB9EB3')
GpgmeError: (7, 16383, u'End of file')
==
ERROR: test_sign_without_passphrase_cb
(tests.test_passphrase.PassphraseTestCase)
--
Traceback (most recent call last):
File "/tmp/buildd/pygpgme-0.3/tests/test_passphrase.py", line 37, in
test_sign_without_passphrase_cb
key = ctx.get_key('EFB052B4230BBBC51914BCBB54DCBBC8DBFB9EB3')
GpgmeError: (7, 16383, u'End of file')
==
FAIL: test_import_concat (tests.test_import.ImportTestCase)
--
Traceback (most recent call last):
File "/tmp/buildd/pygpgme-0.3/tests/test_import.py", line 105, in
test_import_concat
self.assertEqual(result.considered, 3)
AssertionError: 5 != 3
==
FAIL: test_import_secret_file (tests.test_import.ImportTestCase)
--
Traceback (most recent call last):
File "/tmp/buildd/pygpgme-0.3/tests/test_import.py", line 58, in
test_import_secret_file
self.assertEqual(result.considered, 1)
AssertionError: 3 != 1
--
Ran 55 tests in 54.866s
FAILED (failures=2, errors=2)
Makefile:7: recipe for target 'check' failed
make[2]: *** [check] Error 1
make[2]: Leaving directory '/tmp/buildd/pygpgme-0.3'
debian/rules:27: recipe for target 'test-python2.7' failed
make[1]: *** [test-python2.7] Error 2
make[1]: Leaving directory '/tmp/buildd/pygpgme-0.3'
debian/rules:64: recipe for target 'build' failed
make: *** [build] Error 2
dpkg-buildpackage: error: debian/rules build gave error exit status 2
[..]
The full build log is attached or can be viewed here:
https://reproducible.debian.net/logs/unstable/amd64/pygpgme_0.3-1.build1.log.gz
Regards,
--
,''`.
: :' : Chris Lamb
`. `'` la...@debian.org / chris-lamb.co.uk
`-
I: using fakeroot in build.
I: pbuilder: network access will be disabled during build
I: Current time: Wed Sep 2 00:06:14 GMT+12 2015
I: pbuilder-time-stamp: 1441195574
I: Building the build Environment
I: extracting base tarball [/var/cache/pbuilder/unstable-reproducible-base.tgz]
I: creating local configuration
I: copying local configuration
I: mounting /proc filesystem
I: mounting /run/shm filesystem
I: mounting /dev/pts filesystem
I: Mounting /dev/shm
I: Mounting /sys
I: policy-rc.d already exists
I: Installing the build-deps
-> Attempting to satisfy build-dependencies
-> Creating pbuilder-satisfydepends-dummy package
Package: pbuilder-satisfydepends-dummy
Version: 0.invalid.0
Architecture: amd64
Maintainer: Debian Pbuilder Team
Description: Dummy package to satisfy dependencies with aptitude - created by
pbuilder
This package was created automatically by pbuilder to satisfy the
build-dependencies of the package being currently built.
Depends: debhelper (>= 8.1.0~), python-all-dev (>= 2.6.6-3~), python3-all-dev,
libgpgme11-dev, python-all-dbg (>= 2.6.6-3~), python3-all-dbg, gnupg
dpkg-deb: building package 'pbuilder-satisfydepends-dummy' in
'/tmp/satisfydepends-aptitude/pbuilder-satisfydepends-dummy.deb'.
Selecting previously unselected package pbuilder-satisfydepends-dummy.
(Reading database ... 20255 files and directories currently installed.)
Preparing to unpack .../pbuilder-satisfydepends-dummy.deb ...
Unpacking pbuilder-satisfydepends-dummy (0.invalid.0) ...
dpkg: pbuilder-satisfydepends-dummy: dependency problems, but configuring
anyway as you requested:
pbuilder-satisfydepends-dummy depends on python-all-dev (>= 2.6.6-3~); however:
Package python-all-dev is not installed.
pbuilder-satisfydepends-dummy depends on python3-all-dev; however:
Package python3-all-dev is not installed.
pbuilder-satisfydepends-dummy depends on libgpgme11-dev; however:
Package libgpgme11-dev is not installed.
pbuilder-satisfydepends-dummy depends on python-all-dbg (>= 2.6.6-3~); however:
Package python-all-dbg
[Reproducible-builds] Processed: pending
Processing commands for cont...@bugs.debian.org: > tag 797557 + pending Bug #797557 [diffoscope] diffoscope: provide option to disable fuzzy-matching Added tag(s) pending. > thanks Stopping processing here. Please contact me if you need assistance. -- 797557: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=797557 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ___ Reproducible-builds mailing list Reproducible-builds@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/reproducible-builds
[Reproducible-builds] Processed: Re: Bug#797759: diffoscope: tar.gz and tar.bz2 archives compared wrongly
Processing control commands: > retitle -1 diffoscope: implement fuzzy-matching across containers Bug #797759 [diffoscope] diffoscope: tar.gz and tar.bz2 archives compared wrongly Changed Bug title to 'diffoscope: implement fuzzy-matching across containers' from 'diffoscope: tar.gz and tar.bz2 archives compared wrongly' > severity -1 wishlist Bug #797759 [diffoscope] diffoscope: implement fuzzy-matching across containers Severity set to 'wishlist' from 'important' -- 797759: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=797759 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ___ Reproducible-builds mailing list Reproducible-builds@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/reproducible-builds
[Reproducible-builds] Bug#797759: Bug#797759: diffoscope: tar.gz and tar.bz2 archives compared wrongly
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 compares the two tar files, instead of their > contents? That can be implemented by adding support for fuzzy-matching across containers. This would also detect and compare properly a file being compressed from one version to the next. It's doable. The trickiest part in my mind so far is where to attach them in the tree of differences. -- Lunar.''`. lu...@debian.org: :Ⓐ : # apt-get install anarchism `. `'` `- signature.asc Description: Digital signature ___ Reproducible-builds mailing list Reproducible-builds@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/reproducible-builds
[Reproducible-builds] Bug#797759: diffoscope: tar.gz and tar.bz2 archives compared wrongly
Package: diffoscope Version: 31 Severity: important 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 compares the two tar files, instead of their contents? -- System Information: Debian Release: stretch/sid APT prefers testing APT policy: (500, 'testing') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.0.0-2-amd64 (SMP w/4 CPU cores) Locale: LANG=it_IT.utf8, LC_CTYPE=it_IT.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages diffoscope depends on: ii python 2.7.9-1 ii python-debian0.1.27 ii python-libarchive-c 2.1-3 ii python-magic 1:5.22+15-2 ii python-rpm 4.12.0.1+dfsg1-3 ii python-tlsh 3.2.1+20150727-1 pn python:any Versions of packages diffoscope recommends: ii acl 2.2.52-2 pn binutils-multiarch ii bzip2 1.0.6-8 ii cpio 2.11+dfsg-4.1 ii default-jdk [java-sdk]2:1.7-52 pn fontforge-extras ii genisoimage 9:1.1.11-3 ii gettext 0.19.4-1 pn ghc ii gnupg 1.4.19-5 pn mono-utils ii openjdk-7-jdk [java-sdk] 7u75-2.5.4-2 ii pdftk 2.02-3 ii poppler-utils 0.26.5-3 ii rpm2cpio 4.12.0.1+dfsg1-3 pn sng ii sqlite3 3.8.11.1-1 pn squashfs-tools ii unzip 6.0-18 ii vim-common2:7.4.826-1 ii xz-utils 5.1.1alpha+20120614-2.1 diffoscope suggests no packages. -- no debconf information ___ Reproducible-builds mailing list Reproducible-builds@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/reproducible-builds
[Reproducible-builds] Processed: pending
Processing commands for cont...@bugs.debian.org: > tag 796196 + pending Bug #796196 [diffoscope] strip .py suffix from diffoscope within sources repo as well Added tag(s) pending. > thanks Stopping processing here. Please contact me if you need assistance. -- 796196: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=796196 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ___ Reproducible-builds mailing list Reproducible-builds@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/reproducible-builds
Re: [Reproducible-builds] Bug#792687: gettext: please support timestamps from environment
On Tue, Sep 01, 2015 at 06:28:28PM +0200, Jérémy Bobbio wrote: > 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 add the .pot in git because it's generated at build time. > > Adding it duplicates info and adds the risk that it's not up-to-date. Well, upstream authors using autoconf in their projects usually don't put the autogenerated "configure" script in the git repository (which I understand), but they include it in the release tarball. I think .pot files belong to the same class of files that belong to release tarballs, i.e. the kind of files that (normally) should not be created at build time because they are already there. > I'd be happy to hear more arguments for/against. Yes, so would I. Maybe I should ask the author. ___ Reproducible-builds mailing list Reproducible-builds@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/reproducible-builds
