Bug#796907: vte3: should be removed, obsoleted by src:vte2.91
Source: vte3 Severity: serious The src:vte3 and packages built from it should be removed ASAP. It is obsoleted by src:vte2.91 and all reverse dependencies should move to using that (eg. via build-dep on libvte-2.91-dev instead of libvte-2.90-dev). This bug report should help keep src:vte3 out of testing once that's possible and hopefully also alert some reverse dep maintainers about this via http://packages.qa.debian.org so that the removal can happen before Stretch. Regards, Andreas Henriksson
Bug#796891: libvtk6-dev: Reference to non-existant vtkGUISupportQtModule.h in /usr/include/vtk-6.2/QVTKWidget.h
tags 796891 +pending severity 796891 important thanks
Bug#781103: Fix confirmed
Simply upgrading the package restores a working Wacom setup in GNOME. Fix confirmed; thank you! -- Andrew Chadwick
Bug#796908: Should not be released with Stretch, replaced by gnome-desktop3
Source: gnome-desktop Version: 2.32.1-2 Severity: serious Filing this bug with RC severity, to make sure we don't release gnome-desktop with Stretch. Bugs against all reverse-dependencies have been filed. -- System Information: Debian Release: stretch/sid APT prefers unstable APT policy: (500, 'unstable'), (200, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.1.0-2-amd64 (SMP w/4 CPU cores) Locale: LANG=de_DE.utf8, LC_CTYPE=de_DE.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system)
Processed: Re: Bug#796891: libvtk6-dev: Reference to non-existant vtkGUISupportQtModule.h in /usr/include/vtk-6.2/QVTKWidget.h
Processing commands for cont...@bugs.debian.org: tags 796891 +pending Bug #796891 [libvtk6-dev] libvtk6-dev: Reference to non-existant vtkGUISupportQtModule.h in /usr/include/vtk-6.2/QVTKWidget.h Added tag(s) pending. severity 796891 important Bug #796891 [libvtk6-dev] libvtk6-dev: Reference to non-existant vtkGUISupportQtModule.h in /usr/include/vtk-6.2/QVTKWidget.h Severity set to 'important' from 'grave' thanks Stopping processing here. Please contact me if you need assistance. -- 796891: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=796891 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#796715: coinor-osi: working diff
On Tue, Aug 25, 2015 at 3:46 AM, Rene Engelhard r...@debian.org wrote: Either you can upload it yourself or I can do a team upload, whatever you prefer. Thanks for figuring this out, I don't currently have the time to work through the transition. Team upload would be appreciated. Best, Miles
Processed: Re: Bug#796422: libopengl-image-perl: FTBFS: perl5/5.20/auto/OpenGL/OpenGL.so: undefined symbol: glResizeBuffersMESA
Processing control commands: tag -1 + confirmed Bug #796422 [src:libopengl-image-perl] libopengl-image-perl: FTBFS: perl5/5.20/auto/OpenGL/OpenGL.so: undefined symbol: glResizeBuffersMESA Added tag(s) confirmed. block -1 with 795741 Bug #796422 [src:libopengl-image-perl] libopengl-image-perl: FTBFS: perl5/5.20/auto/OpenGL/OpenGL.so: undefined symbol: glResizeBuffersMESA 796422 was not blocked by any bugs. 796422 was not blocking any bugs. Added blocking bug(s) of 796422: 795741 -- 796422: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=796422 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: tagging 795741
Processing commands for cont...@bugs.debian.org: tags 795741 + confirmed Bug #795741 [libopengl-perl] libopengl-perl: FTBFS: undefined symbol: glResizeBuffersMESA Added tag(s) confirmed. thanks Stopping processing here. Please contact me if you need assistance. -- 795741: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=795741 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#796902: python-scipy: FTBFS: dh: unable to load addon sphinxdoc
Source: python-scipy Version: 0.16.0-1 Severity: serious Justification: fails to build from source (but built successfully in the past) Builds of python-scipy in minimal environments geared for building only its architecture-dependent binary packages have been failing with errors along the lines of dpkg-buildpackage: host architecture arm64 fakeroot debian/rules clean dh clean --with python2,python3,sphinxdoc dh: unable to load addon sphinxdoc: Can't locate Debian/Debhelper/Sequence/sphinxdoc.pm in @INC (you may need to install the Debian::Debhelper::Sequence::sphinxdoc module) (@INC contains: /etc/perl /usr/local/lib/aarch64-linux-gnu/perl/5.20.2 /usr/local/share/perl/5.20.2 /usr/lib/aarch64-linux-gnu/perl5/5.20 /usr/share/perl5 /usr/lib/aarch64-linux-gnu/perl/5.20 /usr/share/perl/5.20 /usr/local/lib/site_perl .) at (eval 5) line 2. BEGIN failed--compilation aborted at (eval 5) line 2. make: *** [clean] Error 2 debian/rules:16: recipe for target 'clean' failed Please either conditionalize the use of --with sphinxdoc appropriately or move python-sphinx from Build-Depends-Indep to Build-Depends. Thanks!
Bug#796422: libopengl-image-perl: FTBFS: perl5/5.20/auto/OpenGL/OpenGL.so: undefined symbol: glResizeBuffersMESA
Control: tag -1 + confirmed Control: block -1 with 795741 On Fri, 21 Aug 2015 20:57:34 +0100, Chris Lamb wrote: Source: libopengl-image-perl Version: 1.03-1 Severity: serious Justification: fails to build from source User: reproducible-bui...@lists.alioth.debian.org Usertags: ftbfs X-Debbugs-Cc: reproducible-bui...@lists.alioth.debian.org Dear Maintainer, libopengl-image-perl fails to build from source in unstable/amd64: [..] make -j1 test TEST_VERBOSE=1 make[1]: Entering directory '/tmp/buildd/libopengl-image-perl-1.03' PERL_DL_NONLAZY=1 /usr/bin/perl -MExtUtils::Command::MM -MTest::Harness -e undef *Test::Harness::Switches; test_harness(1, 'blib/lib', 'blib/arch') t/*.t Can't load '/usr/lib/x86_64-linux-gnu/perl5/5.20/auto/OpenGL/OpenGL.so' for module OpenGL: /usr/lib/x86_64-linux-gnu/perl5/5.20/auto/OpenGL/OpenGL.so: undefined symbol: glResizeBuffersMESA at /usr/lib/x86_64-linux-gnu/perl/5.20/DynaLoader.pm line 187. at t/OpenGL-Image.t line 3. Compilation failed in require at t/OpenGL-Image.t line 3. BEGIN failed--compilation aborted at t/OpenGL-Image.t line 3. t/OpenGL-Image.t .. Dubious, test returned 2 (wstat 512, 0x200) No subtests run This looks like fallout from / a duplicate of #795741. Cheers, gregor -- .''`. Homepage: http://info.comodo.priv.at/ - OpenPGP key 0xBB3A68018649AA06 : :' : Debian GNU/Linux user, admin, and developer - https://www.debian.org/ `. `' Member of VIBE!AT SPI, fellow of the Free Software Foundation Europe `- NP: Rolling Stones: Catfish signature.asc Description: Digital Signature
Bug#793604: gammaray: FTBFS against VTK 6.2
On Sat, 25 Jul 2015 15:17:40 +0200 Andreas Beckmann a...@debian.org wrote: Source: gammaray Version: 2.2.1-1 Severity: serious Justification: fails to build from source (but built successfully in the past) As can be seen on https://buildd.debian.org/status/package.php?p=gammaraysuite=unstable gammaray does no longer build against VTK 6.2 and had test failures on many platform on the last attempt that still used VTK 6.1 The immediate problem in the bug is solved by adding libvtk6-qt-dev to build- depends, but I'm unsure about getting the package to build, so I'll leave it and work on something else. Scott K
Processed: Re: Bug#777601: systemd: Loosing LXC memory cgroups after service install
Processing commands for cont...@bugs.debian.org:
unarchive 777601
Bug #777601 {Done: Martin Pitt mp...@debian.org} [systemd] systemd: Loosing
LXC memory cgroups after service install
Unarchived Bug 777601
thanks
Stopping processing here.
Please contact me if you need assistance.
--
777601: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=777601
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Processed: Re: Bug#779803: smuxi performs autoconnect on first startup
Processing control commands: tags 779803 + fixed pending Bug #779803 [smuxi] smuxi performs autoconnect on first startup Added tag(s) fixed and pending. -- 779803: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=779803 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#796400: [pkg-go] Bug#796400: Bug#796400: golang-github-jacobsa-ratelimit: Non-determistically FTBFS due to unreliable timing in tests
On Tue, Aug 25, 2015 at 7:13 PM, Chris Lamb la...@debian.org wrote: Sure. Are you able to modify the test before running it on the relevant system and find a timing that works reliably? lamby, do I have access to the system on which the tests don’t pass? I fear gaining access to this machine would serve no real purpose; the solution here is not to bump the values so that the test is less flaky - the test would remain non-determistic and thus this bug would remain unresolved IMHO, even though it might be harder to trigger. As a concept, I have no problem with automated solutions to point out potential performance regressions, but having a testsuite that fails I don’t think the intention of the test in question is to point out performance regressions, so while I agree with your general statement about flakyness in general, I’m not convinced it applies here. non-determinstically is generally perceived to be a Bad Idea in software engineering. Perhaps some sort of switch or environment variable can be introduced to enable them so that they do not get in the way of the regular build. Regards, -- ,''`. : :' : Chris Lamb `. `'` la...@debian.org / chris-lamb.co.uk `- -- Best regards, Michael
Bug#796907: vte3: should be removed, obsoleted by src:vte2.91
Am 25.08.2015 um 19:33 schrieb Andreas Henriksson: Source: vte3 Severity: serious The src:vte3 and packages built from it should be removed ASAP. It is obsoleted by src:vte2.91 and all reverse dependencies should move to using that (eg. via build-dep on libvte-2.91-dev instead of libvte-2.90-dev). This bug report should help keep src:vte3 out of testing once that's possible and hopefully also alert some reverse dep maintainers about this via http://packages.qa.debian.org so that the removal can happen before Stretch. Bugs have already been filed, so I'm posting this for completeness sake: https://bugs.debian.org/cgi-bin/pkgreport.cgi?users=pkg-gnome-maintain...@lists.alioth.debian.org;tag=vte3-removal -- Why is it that all of the instruments seeking intelligent life in the universe are pointed away from Earth? signature.asc Description: OpenPGP digital signature
Bug#796891: libvtk6-dev: Reference to non-existant vtkGUISupportQtModule.h in /usr/include/vtk-6.2/QVTKWidget.h
My reading of this split out is that all the users of the Qt parts of VTK will need to update their build-depends. I think it would be appropriate to file bugs against the relevant packages so they know. Scott K On Tuesday, August 25, 2015 05:14:04 PM Anton Gladky wrote: I think the second option should be better. Anton 2015-08-25 16:49 GMT+02:00 Scott Kitterman deb...@kitterman.com: So does that mean that libvtk6-dev should depend on libvtk6-qt-dev or perhaps /usr/include/vtk-6.2/QVTKWidget.h should move there as well? Scott K On Tuesday, August 25, 2015 04:26:23 PM Anton Gladky wrote: It is in libvtk6-qt-dev [1]. [1] https://packages.debian.org/sid/amd64/libvtk6-qt-dev/filelist Anton 2015-08-25 15:44 GMT+02:00 Scott Kitterman deb...@kitterman.com: Package: libvtk6-dev Version: 6.2.0+dfsg1-3 Severity: grave Tags: upstream Justification: renders package unusable I was trying to build a newer version of gammaray locally to see if it would build with vtk6 and the build failed with this error: In file included from /tmp/buildd/gammaray-2.3.0/plugins/objectvisualizer/vtkwidget.h:31:0, from /tmp/buildd/gammaray-2.3.0/plugins/objectvisualizer/objectvisualizerwidget.cpp:30: /usr/include/vtk-6.2/QVTKWidget.h:39:55: fatal error: vtkGUISupportQtModule.h: No such file or directory compilation
Bug#790777: Building with sbuild?
* Jelmer Vernooij jel...@debian.org [2015-08-22 22:45]: Are you building with sbuild? You are possibly hitting http://bugs.debian.org/750593 I was using sbuild but I also see it in a normal chroot. Are you saying you don't see it? -- Martin Michlmayr Linux for HP Helion, Hewlett-Packard
Bug#796892: ftp.debian.org: Broken Sources.bz2 file for at least 3 repositories
This is causing me sadness as well.
Processed: block 765380 with 796845
Processing commands for cont...@bugs.debian.org: block 765380 with 796845 Bug #765380 [src:gcc-4.8] gcc-4.8: do not ship with Jessie+1 765380 was not blocked by any bugs. 765380 was not blocking any bugs. Added blocking bug(s) of 765380: 796845 thanks Stopping processing here. Please contact me if you need assistance. -- 765380: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=765380 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: reopen as it blocks perl 5.22
Processing commands for cont...@bugs.debian.org:
# This is fixed in experimental. In order that it shows up as a perl
# 5.22 blocker, reopen the bugreport
reopen 790532
Bug #790532 {Done: intrigeri intrig...@debian.org} [libgtk2-perl] FTBFS:
t/GdkWindow.t crashes perl
'reopen' may be inappropriate when a bug has been closed with a version;
all fixed versions will be cleared, and you may need to re-add them.
Bug reopened
No longer marked as fixed in versions libgtk2-perl/2:1.2496-1.
thanks
Stopping processing here.
Please contact me if you need assistance.
--
790532: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=790532
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Processed: retitle 790532 to libgtk2-perl: FTBFS: t/GdkWindow.t crashes per
Processing commands for cont...@bugs.debian.org: retitle 790532 libgtk2-perl: FTBFS: t/GdkWindow.t crashes per Bug #790532 [libgtk2-perl] FTBFS: t/GdkWindow.t crashes perl Changed Bug title to 'libgtk2-perl: FTBFS: t/GdkWindow.t crashes per' from 'FTBFS: t/GdkWindow.t crashes perl' thanks Stopping processing here. Please contact me if you need assistance. -- 790532: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=790532 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#796893: cpuset: cset program not functional in Debian 8 due to change of file paths.
Package: cpuset Version: 1.5.6-4 Severity: grave Justification: renders package unusable Dear Maintainer, I was looking into setting up a cset shield in order to move kernel threads off of an isolated CPU when I ran into this: ``` $ sudo cset shield -v cset: ** [Errno 2] No such file or directory: '/cpusets//cpus' $ sudo cset shield -c 1-3 cset: ** [Errno 2] No such file or directory: '/cpusets//cpus' ``` None of the invocations I have tried have said anyhting different. The reason for is (I think) described here: https://code.google.com/p/cpuset/issues/detail?id=10 The upstream bug is several years old, which is worrying. I although this is not directly a debian related issue, I am filiing in case it is possible for the Debian team to locally patch. As it stands cset is not functional on Debian 8. Thanks -- System Information: Debian Release: 8.1 APT prefers stable-updates APT policy: (500, 'stable-updates'), (200, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 3.16.0-4-amd64 (SMP w/4 CPU cores) Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages cpuset depends on: ii python 2.7.9-1 pn python:any none cpuset recommends no packages. cpuset suggests no packages. -- no debconf information
Processed: fixed 790532 in 2:1.2496-1
Processing commands for cont...@bugs.debian.org: fixed 790532 2:1.2496-1 Bug #790532 [libgtk2-perl] FTBFS: t/GdkWindow.t crashes perl Marked as fixed in versions libgtk2-perl/2:1.2496-1. thanks Stopping processing here. Please contact me if you need assistance. -- 790532: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=790532 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#796891: libvtk6-dev: Reference to non-existant vtkGUISupportQtModule.h in /usr/include/vtk-6.2/QVTKWidget.h
So does that mean that libvtk6-dev should depend on libvtk6-qt-dev or perhaps /usr/include/vtk-6.2/QVTKWidget.h should move there as well? Scott K On Tuesday, August 25, 2015 04:26:23 PM Anton Gladky wrote: It is in libvtk6-qt-dev [1]. [1] https://packages.debian.org/sid/amd64/libvtk6-qt-dev/filelist Anton 2015-08-25 15:44 GMT+02:00 Scott Kitterman deb...@kitterman.com: Package: libvtk6-dev Version: 6.2.0+dfsg1-3 Severity: grave Tags: upstream Justification: renders package unusable I was trying to build a newer version of gammaray locally to see if it would build with vtk6 and the build failed with this error: In file included from /tmp/buildd/gammaray-2.3.0/plugins/objectvisualizer/vtkwidget.h:31:0, from /tmp/buildd/gammaray-2.3.0/plugins/objectvisualizer/objectvisualizerwidget.cpp:30: /usr/include/vtk-6.2/QVTKWidget.h:39:55: fatal error: vtkGUISupportQtModule.h: No such file or directory compilation
Bug#795972: marked as done (python-oslotest: FTBFS: AttributeError: assert_any_calls)
Your message dated Tue, 25 Aug 2015 15:28:17 +
with message-id e1zug93-0007z9...@franck.debian.org
and subject line Bug#795972: fixed in python-oslotest 1.5.1-2
has caused the Debian Bug report #795972,
regarding python-oslotest: FTBFS: AttributeError: assert_any_calls
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 ow...@bugs.debian.org
immediately.)
--
795972: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=795972
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
---BeginMessage---
Source: python-oslotest
Version: 1.5.1-1
Severity: serious
Justification: fails to build from source
User: reproducible-bui...@lists.alioth.debian.org
Usertags: ftbfs
X-Debbugs-Cc: reproducible-bui...@lists.alioth.debian.org
Dear Maintainer,
python-oslotest fails to build from source on unstable/amd64:
[..]
==
FAIL:
tests.unit.test_base.TestBaseTestCase.test_fake_logs_with_log_cap
tests.unit.test_base.TestBaseTestCase.test_fake_logs_with_log_cap
--
_StringException: Traceback (most recent call last):
File /usr/lib/python2.7/dist-packages/mock/mock.py, line 1305, in
patched
return func(*args, **keywargs)
File tests/unit/test_base.py, line 82, in
test_fake_logs_with_log_cap
env_get_mock.assert_any_calls('OS_DEBUG')
File /usr/lib/python2.7/dist-packages/mock/mock.py, line 721, in
__getattr__
raise AttributeError(name)
AttributeError: assert_any_calls
==
FAIL: process-returncode
process-returncode
--
_StringException: returncode 1
==
FAIL: tests.unit.test_base.TestBaseTestCase.test_fake_logs_with_debug
tests.unit.test_base.TestBaseTestCase.test_fake_logs_with_debug
--
_StringException: Traceback (most recent call last):
File /usr/lib/python2.7/dist-packages/mock/mock.py, line 1305, in
patched
return func(*args, **keywargs)
File tests/unit/test_base.py, line 69, in
test_fake_logs_with_debug
env_get_mock.assert_any_calls('OS_DEBUG')
File /usr/lib/python2.7/dist-packages/mock/mock.py, line 721, in
__getattr__
raise AttributeError(name)
AttributeError: assert_any_calls
==
FAIL: process-returncode
process-returncode
--
_StringException: returncode 1
==
FAIL: tests.unit.test_base.TestBaseTestCase.test_fake_logs_default
tests.unit.test_base.TestBaseTestCase.test_fake_logs_default
--
_StringException: Traceback (most recent call last):
File /usr/lib/python2.7/dist-packages/mock/mock.py, line 1305, in
patched
return func(*args, **keywargs)
File tests/unit/test_base.py, line 58, in test_fake_logs_default
env_get_mock.assert_any_calls('OS_DEBUG')
File /usr/lib/python2.7/dist-packages/mock/mock.py, line 721, in
__getattr__
raise AttributeError(name)
AttributeError: assert_any_calls
==
FAIL: process-returncode
process-returncode
--
_StringException: returncode 1
--
Ran 22 tests in 1.377s
FAILED (failures=6)
debian/rules:33: recipe for target 'override_dh_auto_test' failed
make[1]: *** [override_dh_auto_test] Error 1
make[1]: Leaving directory '/tmp/buildd/python-oslotest-1.5.1'
debian/rules:12: 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/python-oslotest_1.5.1-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: Mon Aug 10 15:33:46 GMT+12 2015
I: pbuilder-time-stamp: 1439264026
I:
Bug#795128: marked as done (python-barbicanclient: FTBFS: test_delete_checks_status_code: AttributeError: assert_called)
Your message dated Tue, 25 Aug 2015 15:27:57 + with message-id e1zug8j-0007q5...@franck.debian.org and subject line Bug#795128: fixed in python-barbicanclient 3.0.3-2 has caused the Debian Bug report #795128, regarding python-barbicanclient: FTBFS: test_delete_checks_status_code: AttributeError: assert_called 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 ow...@bugs.debian.org immediately.) -- 795128: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=795128 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Source: python-barbicanclient Version: 3.0.3-1 Severity: serious Justification: fails to build from source Tags: sid User: reproducible-bui...@lists.alioth.debian.org Usertags: ftbfs X-Debbugs-CC: reproducible-bui...@lists.alioth.debian.org Dear Maintainer, The package fails to build: == FAIL: barbicanclient.tests.test_client.WhenTestingClientDelete.test_delete_checks_status_code barbicanclient.tests.test_client.WhenTestingClientDelete.test_delete_checks_status_code -- _StringException: Traceback (most recent call last): File barbicanclient/tests/test_client.py, line 210, in test_delete_checks_status_code self.httpclient._check_status_code.assert_called() File /usr/lib/python2.7/dist-packages/mock/mock.py, line 721, in __getattr__ raise AttributeError(name) AttributeError: assert_called == FAIL: barbicanclient.tests.test_client.WhenTestingClientGet.test_get_checks_status_code barbicanclient.tests.test_client.WhenTestingClientGet.test_get_checks_status_code -- _StringException: Traceback (most recent call last): File barbicanclient/tests/test_client.py, line 160, in test_get_checks_status_code self.httpclient._check_status_code.assert_called() File /usr/lib/python2.7/dist-packages/mock/mock.py, line 721, in __getattr__ raise AttributeError(name) AttributeError: assert_called ... == FAIL: process-returncode process-returncode -- _StringException: returncode 1 ... Ran 106 tests in 0.689s FAILED (failures=5) Full build log: https://reproducible.debian.net/rb-pkg/unstable/amd64/python-barbicanclient.html -- System Information: Debian Release: stretch/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: amd64 (x86_64) Kernel: Linux 3.19.0-23-generic (SMP w/8 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) ---End Message--- ---BeginMessage--- Source: python-barbicanclient Source-Version: 3.0.3-2 We believe that the bug you reported is fixed in the latest version of python-barbicanclient, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 795...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Thomas Goirand z...@debian.org (supplier of updated python-barbicanclient package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Tue, 25 Aug 2015 14:32:38 + Source: python-barbicanclient Binary: python-barbicanclient Architecture: source all Version: 3.0.3-2 Distribution: unstable Urgency: medium Maintainer: PKG OpenStack openstack-de...@lists.alioth.debian.org Changed-By: Thomas Goirand z...@debian.org Description: python-barbicanclient - OpenStack Key Management API client - Python 2.x Closes: 795128 Changes: python-barbicanclient (3.0.3-2) unstable; urgency=medium . * Disabled tests which fails with python-mock = 1.3 (Closes: #795128). Checksums-Sha1: 32f0b1b8972c67db0d8559133831d6c9c4adfb1d 2551 python-barbicanclient_3.0.3-2.dsc 10d0a5fcce507b23948030d22c111d52f5cdc978 2704 python-barbicanclient_3.0.3-2.debian.tar.xz ef26f73cbfafed1893ee12e32b944ec918d45119 59326 python-barbicanclient_3.0.3-2_all.deb Checksums-Sha256:
Bug#796889: marked as done (python-xlib: UnicodeDecodeError on instantiating Xlib.xauth.Xauthority)
Your message dated Tue, 25 Aug 2015 15:28:23 +
with message-id e1zug99-00080o...@franck.debian.org
and subject line Bug#796889: fixed in python-xlib 0.14+20091101-5
has caused the Debian Bug report #796889,
regarding python-xlib: UnicodeDecodeError on instantiating Xlib.xauth.Xauthority
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 ow...@bugs.debian.org
immediately.)
--
796889: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=796889
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
---BeginMessage---
Package: python-xlib
Version: 0.14+20091101-4
Severity: grave
Justification: renders package unusable
Dear Maintainer,
After upgrading python-xlib (or python3-xlib) to 0.14+20091101-3 (or -4),
attempting to instantiate an Xauthority instance (eg. via attempting to get a
Display()) fails with a UnicodeDecodeError:
$ python
Python 2.7.10 (default, Jul 1 2015, 10:54:53)
[GCC 4.9.2] on linux2
Type help, copyright, credits or license for more information.
from Xlib import xauth
xauth.Xauthority()
Traceback (most recent call last):
File stdin, line 1, in module
File /usr/lib/python2.7/dist-packages/Xlib/xauth.py, line 84, in __init__
self.entries.append((family, addr.decode('UTF-8'),
File /usr/lib/python2.7/encodings/utf_8.py, line 16, in decode
return codecs.utf_8_decode(input, errors, True)
UnicodeDecodeError: 'utf8' codec can't decode byte 0xac in position 0: invalid
start byte
Following the logic of Xauthority.__init__ indicates my ~/.Xauthority file has:
raw[4:8] # first addr
'\xac\x11\x11\x89'
Downgrading to 0.14+20091101-1 from Jessie fixes the issue:
$ python
Python 2.7.10 (default, Jul 1 2015, 10:54:53)
[GCC 4.9.2] on linux2
Type help, copyright, credits or license for more information.
from Xlib import xauth
xauth.Xauthority()
Xlib.xauth.Xauthority instance at 0x7fd2656ec8c0
-- System Information:
Debian Release: stretch/sid
APT prefers testing
APT policy: (900, 'testing'), (500, 'testing-updates'), (500, 'unstable'),
(1, 'experimental')
Architecture: amd64 (x86_64)
Kernel: Linux 4.1.0-1-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
Versions of packages python-xlib depends on:
pn python:any none
python-xlib recommends no packages.
python-xlib suggests no packages.
-- no debconf information
---End Message---
---BeginMessage---
Source: python-xlib
Source-Version: 0.14+20091101-5
We believe that the bug you reported is fixed in the latest version of
python-xlib, which is due to be installed in the Debian FTP archive.
A summary of the changes between this version and the previous one is
attached.
Thank you for reporting the bug, which will now be closed. If you
have further comments please address them to 796...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Andrew Shadura andre...@debian.org (supplier of updated python-xlib package)
(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Format: 1.8
Date: Tue, 25 Aug 2015 16:18:06 +0200
Source: python-xlib
Binary: python-xlib python3-xlib
Architecture: source
Version: 0.14+20091101-5
Distribution: unstable
Urgency: medium
Maintainer: Debian Python Modules Team
python-modules-t...@lists.alioth.debian.org
Changed-By: Andrew Shadura andre...@debian.org
Description:
python-xlib - interface for Python to the X11 protocol
python3-xlib - interface for Python 3 to the X11 protocol
Closes: 796889
Changes:
python-xlib (0.14+20091101-5) unstable; urgency=medium
.
* Fix LP: #1482844 properly: lp1432889.patch is incompatible with
fix-auth-lp1482844.patch (Closes: #796889).
Checksums-Sha1:
ee3381796a691c1ce84170cbab33a2f4a87f2770 2183 python-xlib_0.14+20091101-5.dsc
2e17fd9af434cd3c6d9d9ca3328f515a4d726fcb 54728
python-xlib_0.14+20091101-5.debian.tar.xz
Checksums-Sha256:
149feb8c7a4fa27803349682064d2303b9355a736501308e611d4c78351ec4ac 2183
python-xlib_0.14+20091101-5.dsc
0432dff8237c0eefc037b4cc6a02f2491cc5af298566b6c1e86e6670ff9ed4bb 54728
python-xlib_0.14+20091101-5.debian.tar.xz
Files:
1a32792c76e7578089a96357c604d82b 2183 python optional
python-xlib_0.14+20091101-5.dsc
e3462d690f0e15e7a8d1b8bfba8dc2f8 54728 python optional
python-xlib_0.14+20091101-5.debian.tar.xz
-BEGIN PGP SIGNATURE-
Version: GnuPG v1
Processed: forcibly merging 795028 796900, fixed 795028 in 0.7.1~exp1-1~apt1.1~exp9
Processing commands for cont...@bugs.debian.org: forcemerge 795028 796900 Bug #795028 [aptitude] aptitude: junk in package names with dependency resolver Bug #795150 [aptitude] aptitude: Aptitude displays garbage on screen during resolving Bug #796090 [aptitude] screen garbage on Resolve Dependencies display Bug #796504 [aptitude] aptitude: package titles appear as garbage text in Resolve Dep. window Bug #796900 [aptitude] aptitude: display of resolution options is completely broken Severity set to 'normal' from 'serious' Added tag(s) pending and fixed-upstream. Bug #795150 [aptitude] aptitude: Aptitude displays garbage on screen during resolving Bug #796090 [aptitude] screen garbage on Resolve Dependencies display Bug #796504 [aptitude] aptitude: package titles appear as garbage text in Resolve Dep. window Merged 795028 795150 796090 796504 796900 fixed 795028 0.7.1~exp1-1~apt1.1~exp9 Bug #795028 [aptitude] aptitude: junk in package names with dependency resolver Bug #795150 [aptitude] aptitude: Aptitude displays garbage on screen during resolving Bug #796090 [aptitude] screen garbage on Resolve Dependencies display Bug #796504 [aptitude] aptitude: package titles appear as garbage text in Resolve Dep. window Bug #796900 [aptitude] aptitude: display of resolution options is completely broken Marked as fixed in versions aptitude/0.7.1~exp1-1~apt1.1~exp9. Marked as fixed in versions aptitude/0.7.1~exp1-1~apt1.1~exp9. Marked as fixed in versions aptitude/0.7.1~exp1-1~apt1.1~exp9. Marked as fixed in versions aptitude/0.7.1~exp1-1~apt1.1~exp9. Marked as fixed in versions aptitude/0.7.1~exp1-1~apt1.1~exp9. thanks Stopping processing here. Please contact me if you need assistance. -- 795028: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=795028 795150: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=795150 796090: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=796090 796504: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=796504 796900: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=796900 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#796891: libvtk6-dev: Reference to non-existant vtkGUISupportQtModule.h in /usr/include/vtk-6.2/QVTKWidget.h
It is in libvtk6-qt-dev [1]. [1] https://packages.debian.org/sid/amd64/libvtk6-qt-dev/filelist Anton 2015-08-25 15:44 GMT+02:00 Scott Kitterman deb...@kitterman.com: Package: libvtk6-dev Version: 6.2.0+dfsg1-3 Severity: grave Tags: upstream Justification: renders package unusable I was trying to build a newer version of gammaray locally to see if it would build with vtk6 and the build failed with this error: In file included from /tmp/buildd/gammaray-2.3.0/plugins/objectvisualizer/vtkwidget.h:31:0, from /tmp/buildd/gammaray-2.3.0/plugins/objectvisualizer/objectvisualizerwidget.cpp:30: /usr/include/vtk-6.2/QVTKWidget.h:39:55: fatal error: vtkGUISupportQtModule.h: No such file or directory compilation terminated. plugins/objectvisualizer/CMakeFiles/gammaray_objectvisualizer_ui_plugin.dir/build.make:57: recipe for target 'plugins/objectvisualizer/CMakeFiles/gammaray_objectvisualizer_ui_plugin.dir/objectvisualizerwidget.cpp.o' failed make[4]: *** [plugins/objectvisualizer/CMakeFiles/gammaray_objectvisualizer_ui_plugin.dir/objectvisualizerwidget.cpp.o] Error 1 make[4]: Leaving directory '/tmp/buildd/gammaray-2.3.0/obj-qt5' CMakeFiles/Makefile2:3257: recipe for target 'plugins/objectvisualizer/CMakeFiles/gammaray_objectvisualizer_ui_plugin.dir/all' failed make[3]: *** [plugins/objectvisualizer/CMakeFiles/gammaray_objectvisualizer_ui_plugin.dir/all] Error 2 make[3]: Leaving directory '/tmp/buildd/gammaray-2.3.0/obj-qt5' Makefile:149: recipe for target 'all' failed make[2]: *** [all] Error 2 make[2]: Leaving directory '/tmp/buildd/gammaray-2.3.0/obj-qt5' dh_auto_build: make -j1 returned exit code 2 debian/rules:17: recipe for target 'override_dh_auto_build' failed make[1]: *** [override_dh_auto_build] Error 2 make[1]: Leaving directory '/tmp/buildd/gammaray-2.3.0' debian/rules:10: recipe for target 'build' failed make: *** [build] Error 2 dpkg-buildpackage: error: debian/rules build gave error exit status 2 I checked in the installed QVTKWidget.h and line 39 says: #include vtkGUISupportQtModule.h // For export macro but it's not there: ls /usr/include/vtk-6.2/vtkGUISupportQtModule.h ls: cannot access /usr/include/vtk-6.2/vtkGUISupportQtModule.h: No such file or directory It's not listed here either: https://packages.debian.org/sid/amd64/libvtk6-dev/filelist -- debian-science-maintainers mailing list debian-science-maintain...@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/debian-science-maintainers
Processed: Re: Bug#792206: apt-cacher: modifies conffiles (policy 10.7.3): /etc/default/apt-cacher
Processing commands for cont...@bugs.debian.org:
package apt-cacher
Limiting to bugs with field 'package' containing at least one of 'apt-cacher'
Limit currently set to 'package':'apt-cacher'
tags 792206 - unreproducible
Bug #792206 {Done: Mark Hindley m...@hindley.org.uk} [apt-cacher] apt-cacher:
modifies conffiles (policy 10.7.3): /etc/default/apt-cacher
Bug #688890 {Done: Mark Hindley m...@hindley.org.uk} [apt-cacher] apt-cacher:
modifies conffiles (policy 10.7.3): /etc/default/apt-cacher
Removed tag(s) unreproducible.
Removed tag(s) unreproducible.
tags 792206 - moreinfo
Bug #792206 {Done: Mark Hindley m...@hindley.org.uk} [apt-cacher] apt-cacher:
modifies conffiles (policy 10.7.3): /etc/default/apt-cacher
Bug #688890 {Done: Mark Hindley m...@hindley.org.uk} [apt-cacher] apt-cacher:
modifies conffiles (policy 10.7.3): /etc/default/apt-cacher
Removed tag(s) moreinfo.
Removed tag(s) moreinfo.
thanks
Stopping processing here.
Please contact me if you need assistance.
--
688890: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=688890
792206: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=792206
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Bug#760853: Jitsi still uninstallable
I have the same problem, trying to install jitsi from sid, using apt-pinning, the system is jessie otherwise. My /etc/apt/preferences.d/98jitsi file is as follows: ``` Package: jitsi Pin: release a=unstable Pin-Priority: 1000 Package: * Pin: release a=jessie Pin-Priority: 500 Package: * Pin: release a=unstable Pin-Priority: 400 Package: * Pin: release a=experimental Pin-Priority: 300 ``` The error I get when using sudo apt-get -t unstable install jitsi is: ``` The following packages have unmet dependencies: jitsi : Depends: libjitsi (= 415-0) but it is not installable Depends: libjitsi-jni (= 415-0) but it is not installable E: Unable to correct problems, you have held broken packages. ``` -Milos
Bug#796898: python-pykmip: Remove Depends and Build-Depends on python3-enum34
Source: python-pykmip Severity: serious -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Dear Maintainer, python-pykmip currently includes Depends and Build-Depends on python3-enum34. This package is incompatible with Python 3.5 and unnecessary for Python 3.4 since the stdlib already contains the package 'enum' which is the importable name in both cases. python3-enum34 has been removed from the archive for Stretch. Please remove these dependencies. - -- System Information: Debian Release: stretch/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: amd64 (x86_64) Kernel: Linux 4.1.0-2-amd64 (SMP w/1 CPU core) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) -BEGIN PGP SIGNATURE- Version: GnuPG v1 iQIcBAEBCAAGBQJV3IcfAAoJEBJutWOnSwa/410QAKa0jrDH00Ai6zy8cZxTDBuh qwj8uitaWj0TbksidBin17O7Fbu+5rVyCVNZSCc4gutv+WlOMZRoXWWyUuOeonZX HmQsMGTkBFCdVvWehiENjtlTcR1olTZZtDBL6EHFr54r5r+qNqPBaLx6cgf6c+xP 8C0jSegRT/PHbC5qNfghJ/7B2DoknQLG0A9MBp9NYS8RMjUXQ2ChomGw0TigQgt1 RV+AdNnviAilJZ+9rOlUn9LyUjctl1mqaYluOkD/21KOGlK/861H1fiaNoAZWnGx ICkYwLARAj4MWPUWOdIMnKr/3cJzsfiqrd481JI3pmNGI8ubHAndJoBzFA2M4j9D s7AkgHE4nSaTW/rRvaI5v2L3mPcPq3xbAuB6rcpUqLr3HxX/aKKV9GOKH5+tem18 qQYhx7LtiF7OuWfq5GlpoWhI6FIygGI8nLG3gO1QauxLJpVNaLiHS41AilXY1SRz uBcCj/+DI+dFEn5UVwn4F4meGR+BduFknNidXh9TcZQ7VpHwef4N7JqsWIQBZar6 yolb/ZQbYZw0rB+ixhdH9HY+2l88aY+S91aNkPbsv56ANydiTwSog+xppdrzKxvC 9IYyGQcRM2CB4MgGScDxQtnKYlXhgdEonxcQ6R9/hLj/BEgxl96N5dlgr8SyRqco dW/lHbxPQvY0IlyR7sEH =FdaX -END PGP SIGNATURE-
Bug#796891: libvtk6-dev: Reference to non-existant vtkGUISupportQtModule.h in /usr/include/vtk-6.2/QVTKWidget.h
Package: libvtk6-dev Version: 6.2.0+dfsg1-3 Severity: grave Tags: upstream Justification: renders package unusable I was trying to build a newer version of gammaray locally to see if it would build with vtk6 and the build failed with this error: In file included from /tmp/buildd/gammaray-2.3.0/plugins/objectvisualizer/vtkwidget.h:31:0, from /tmp/buildd/gammaray-2.3.0/plugins/objectvisualizer/objectvisualizerwidget.cpp:30: /usr/include/vtk-6.2/QVTKWidget.h:39:55: fatal error: vtkGUISupportQtModule.h: No such file or directory compilation terminated. plugins/objectvisualizer/CMakeFiles/gammaray_objectvisualizer_ui_plugin.dir/build.make:57: recipe for target 'plugins/objectvisualizer/CMakeFiles/gammaray_objectvisualizer_ui_plugin.dir/objectvisualizerwidget.cpp.o' failed make[4]: *** [plugins/objectvisualizer/CMakeFiles/gammaray_objectvisualizer_ui_plugin.dir/objectvisualizerwidget.cpp.o] Error 1 make[4]: Leaving directory '/tmp/buildd/gammaray-2.3.0/obj-qt5' CMakeFiles/Makefile2:3257: recipe for target 'plugins/objectvisualizer/CMakeFiles/gammaray_objectvisualizer_ui_plugin.dir/all' failed make[3]: *** [plugins/objectvisualizer/CMakeFiles/gammaray_objectvisualizer_ui_plugin.dir/all] Error 2 make[3]: Leaving directory '/tmp/buildd/gammaray-2.3.0/obj-qt5' Makefile:149: recipe for target 'all' failed make[2]: *** [all] Error 2 make[2]: Leaving directory '/tmp/buildd/gammaray-2.3.0/obj-qt5' dh_auto_build: make -j1 returned exit code 2 debian/rules:17: recipe for target 'override_dh_auto_build' failed make[1]: *** [override_dh_auto_build] Error 2 make[1]: Leaving directory '/tmp/buildd/gammaray-2.3.0' debian/rules:10: recipe for target 'build' failed make: *** [build] Error 2 dpkg-buildpackage: error: debian/rules build gave error exit status 2 I checked in the installed QVTKWidget.h and line 39 says: #include vtkGUISupportQtModule.h // For export macro but it's not there: ls /usr/include/vtk-6.2/vtkGUISupportQtModule.h ls: cannot access /usr/include/vtk-6.2/vtkGUISupportQtModule.h: No such file or directory It's not listed here either: https://packages.debian.org/sid/amd64/libvtk6-dev/filelist
Processed: retitle 790532 to libgtk2-perl: FTBFS: t/GdkWindow.t crashes perl
Processing commands for cont...@bugs.debian.org: retitle 790532 libgtk2-perl: FTBFS: t/GdkWindow.t crashes perl Bug #790532 [libgtk2-perl] libgtk2-perl: FTBFS: t/GdkWindow.t crashes per Changed Bug title to 'libgtk2-perl: FTBFS: t/GdkWindow.t crashes perl' from 'libgtk2-perl: FTBFS: t/GdkWindow.t crashes per' thanks Stopping processing here. Please contact me if you need assistance. -- 790532: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=790532 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#792053: prometheus: FTBFS w/ test suite errors
found 792053 0.15.1+ds-1 notfixed 792053 0.15.1+ds-1 thanks Aaron M. Ucko u...@debian.org writes: Builds of prometheus on those architectures on which its build dependencies are available (so far just armel, armhf, and i386, aside from amd64) have been failing with assorted test suite errors: I'm happy to confirm that 0.15.1+ds-1 fixes the original errors. However, new ones have cropped up, per https://buildd.debian.org/status/logs.php?pkg=prometheusver=0.15.1%2Bds-1 : TestEvictAndLoadChunkDescsType0 fails on armhf, and TestEvictAndLoadChunkDescsType1 fails on armel and i386. Could you please take another look? Incidentally, I did not explicitly request an update to a new upstream release (though I certainly don't object!), so best practice would have been to note in the changelog what this bug report was actually about. You'll get a chance yet. ;-) Thanks! -- Aaron M. Ucko, KB1CJC (amu at alum.mit.edu, ucko at debian.org) http://www.mit.edu/~amu/ | http://stuff.mit.edu/cgi/finger/?a...@monk.mit.edu
Processed: Re: prometheus: FTBFS w/ test suite errors
Processing commands for cont...@bugs.debian.org:
found 792053 0.15.1+ds-1
Bug #792053 {Done: Martín Ferrari tin...@debian.org} [src:prometheus]
prometheus: FTBFS w/ test suite errors
Marked as found in versions prometheus/0.15.1+ds-1; no longer marked as fixed
in versions prometheus/0.15.1+ds-1 and reopened.
notfixed 792053 0.15.1+ds-1
Bug #792053 [src:prometheus] prometheus: FTBFS w/ test suite errors
Ignoring request to alter fixed versions of bug #792053 to the same values
previously set
thanks
Stopping processing here.
Please contact me if you need assistance.
--
792053: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=792053
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Bug#796891: libvtk6-dev: Reference to non-existant vtkGUISupportQtModule.h in /usr/include/vtk-6.2/QVTKWidget.h
I think the second option should be better. Anton 2015-08-25 16:49 GMT+02:00 Scott Kitterman deb...@kitterman.com: So does that mean that libvtk6-dev should depend on libvtk6-qt-dev or perhaps /usr/include/vtk-6.2/QVTKWidget.h should move there as well? Scott K On Tuesday, August 25, 2015 04:26:23 PM Anton Gladky wrote: It is in libvtk6-qt-dev [1]. [1] https://packages.debian.org/sid/amd64/libvtk6-qt-dev/filelist Anton 2015-08-25 15:44 GMT+02:00 Scott Kitterman deb...@kitterman.com: Package: libvtk6-dev Version: 6.2.0+dfsg1-3 Severity: grave Tags: upstream Justification: renders package unusable I was trying to build a newer version of gammaray locally to see if it would build with vtk6 and the build failed with this error: In file included from /tmp/buildd/gammaray-2.3.0/plugins/objectvisualizer/vtkwidget.h:31:0, from /tmp/buildd/gammaray-2.3.0/plugins/objectvisualizer/objectvisualizerwidget.cpp:30: /usr/include/vtk-6.2/QVTKWidget.h:39:55: fatal error: vtkGUISupportQtModule.h: No such file or directory compilation -- debian-science-maintainers mailing list debian-science-maintain...@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/debian-science-maintainers
Bug#796892: ftp.debian.org: Broken Sources.bz2 file for at least 3 repositories
Package: ftp.debian.org Severity: grave tracker.debian.org has been failing to import new source packages for 4 days. I have such failures during apt-get update: [...] FetchFailedException: W:Failed to fetch file:/srv/mirrors/debian/dists/jessie-backports/main/source/Sources Hash Sum mismatch , W:Failed to fetch file:/srv/mirrors/debian/dists/jessie-backports/non-free/source/Sources Hash Sum mismatch , W:Failed to fetch file:/srv/mirrors/debian/dists/proposed-updates/main/source/Sources Hash Sum mismatch , E:Some index files failed to download. They have been ignored, or old ones used instead. Double checking everything with the corresponding Release file I noticed this: The size/checksums of the uncompressed Sources entry does not match the file that you get when you uncompress the .bz2 file. When you uncompress the .xz file then you have the expected content and it matches the data of the uncompressed entry in Release. In both cases, the size/checksum of the .bz2 and .xz file matches the data from the Release file. hertzog@ticharich:/srv/tracker.debian.org/distro-tracker$ bzip2 -dc /srv/mirrors/debian/dists/proposed-updates/main/source/Sources.bz2 /tmp/Sources hertzog@ticharich:/srv/tracker.debian.org/distro-tracker$ md5sum /tmp/Sources a1d3ad43e13bf3bd1ffc9a25b572c17a /tmp/Sources hertzog@ticharich:/srv/tracker.debian.org/distro-tracker$ grep main/source/Sources$ /srv/mirrors/debian/dists/proposed-updates/Release 653093668be2c8f6cb884a553c7ab7bf 430108 main/source/Sources 39e40dd8616c7819bbb20486015766d440832afc 430108 main/source/Sources 033f74594208451e9fdb9083608b5fe43d00444e8ee4aaf2e04b1332b6b6002d 430108 main/source/Sources hertzog@ticharich:/srv/tracker.debian.org/distro-tracker$ ls -l /tmp/Sources -rw-r--r-- 1 hertzog Debian 418824 août 25 13:23 /tmp/Sources hertzog@ticharich:/srv/tracker.debian.org/distro-tracker$ xz -dc /srv/mirrors/debian/dists/proposed-updates/main/source/Sources.xz /tmp/Sources hertzog@ticharich:/srv/tracker.debian.org/distro-tracker$ ls -l /tmp/Sources -rw-r--r-- 1 hertzog Debian 430108 août 25 13:40 /tmp/Sources hertzog@ticharich:/srv/tracker.debian.org/distro-tracker$ md5sum /tmp/Sources 653093668be2c8f6cb884a553c7ab7bf /tmp/Sources So it looks like the Sources.bz2 is stale for a few repositories...
Processed: Re: Bug#792206: apt-cacher: modifies conffiles (policy 10.7.3): /etc/default/apt-cacher
Processing commands for cont...@bugs.debian.org:
package apt-cacher
Limiting to bugs with field 'package' containing at least one of 'apt-cacher'
Limit currently set to 'package':'apt-cacher'
unarchive 688890
Bug #688890 {Done: Mark Hindley m...@hindley.org.uk} [apt-cacher] apt-cacher:
modifies conffiles (policy 10.7.3): /etc/default/apt-cacher
Unarchived Bug 688890
forcemerge 688890 792206
Bug #688890 {Done: Mark Hindley m...@hindley.org.uk} [apt-cacher] apt-cacher:
modifies conffiles (policy 10.7.3): /etc/default/apt-cacher
Bug #792206 [apt-cacher] apt-cacher: modifies conffiles (policy 10.7.3):
/etc/default/apt-cacher
Severity set to 'serious' from 'normal'
Marked Bug as done
Marked as found in versions apt-cacher/1.7.5 and apt-cacher/1.7.4.
Bug #688890 {Done: Mark Hindley m...@hindley.org.uk} [apt-cacher] apt-cacher:
modifies conffiles (policy 10.7.3): /etc/default/apt-cacher
Marked as found in versions apt-cacher/1.7.11.
Added tag(s) unreproducible and moreinfo.
Merged 688890 792206
thanks
Stopping processing here.
Please contact me if you need assistance.
--
688890: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=688890
792206: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=792206
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Bug#796900: aptitude: display of resolution options is completely broken
Package: aptitude Version: 0.7-1+b1 Severity: serious Justification: unusable Dear aptitude maintainers, since the update to the +b1 version and a general libstdc++ upgrade orgy, the aptitude on my computer is now more or less broken. When ever there is a conflict/problem (red status line, suggesting resolutions) and I go into the examine screen with 'e', the list of packages to be examined is completely messed up. Not *one* package name is readable (see attached screenshot). This is 100% reproducible, and independent of terminals, I tried gnome-terminal and roxterm. I have no idea what/who is the culprit here, but on my system everything is set to UTF8, as usual. All the best Norbert -- Package-specific info: Terminal: xterm $DISPLAY is set. which aptitude: /usr/bin/aptitude aptitude version information: aptitude 0.7 compiled at Aug 7 2015 19:34:17 Compiler: g++ 5.2.1 20150730 Compiled against: apt version 4.16.0 NCurses version 5.9 libsigc++ version: 2.4.1 Gtk+ support disabled. Qt support disabled. Current library versions: NCurses version: ncurses 6.0.20150810 cwidget version: 0.5.17 Apt version: 4.16.0 aptitude linkage: linux-vdso.so.1 (0x7ffd388b8000) libapt-pkg.so.4.16 = /usr/lib/x86_64-linux-gnu/libapt-pkg.so.4.16 (0x7fafed668000) libncursesw.so.5 = /lib/x86_64-linux-gnu/libncursesw.so.5 (0x7fafed438000) libtinfo.so.5 = /lib/x86_64-linux-gnu/libtinfo.so.5 (0x7fafed20d000) libsigc-2.0.so.0 = /usr/lib/x86_64-linux-gnu/libsigc-2.0.so.0 (0x7fafed007000) libcwidget.so.3 = /usr/lib/x86_64-linux-gnu/libcwidget.so.3 (0x7fafecd08000) libsqlite3.so.0 = /usr/lib/x86_64-linux-gnu/libsqlite3.so.0 (0x7fafeca3a000) libboost_iostreams.so.1.58.0 = /usr/lib/x86_64-linux-gnu/libboost_iostreams.so.1.58.0 (0x7fafec821000) libxapian.so.22 = /usr/lib/libxapian.so.22 (0x7fafec41f000) libpthread.so.0 = /lib/x86_64-linux-gnu/libpthread.so.0 (0x7fafec201000) libstdc++.so.6 = /usr/lib/x86_64-linux-gnu/libstdc++.so.6 (0x7fafebe86000) libm.so.6 = /lib/x86_64-linux-gnu/libm.so.6 (0x7fafebb85000) libgcc_s.so.1 = /lib/x86_64-linux-gnu/libgcc_s.so.1 (0x7fafeb96e000) libc.so.6 = /lib/x86_64-linux-gnu/libc.so.6 (0x7fafeb5c5000) libutil.so.1 = /lib/x86_64-linux-gnu/libutil.so.1 (0x7fafeb3c2000) libdl.so.2 = /lib/x86_64-linux-gnu/libdl.so.2 (0x7fafeb1bd000) libz.so.1 = /lib/x86_64-linux-gnu/libz.so.1 (0x7fafeafa2000) libbz2.so.1.0 = /lib/x86_64-linux-gnu/libbz2.so.1.0 (0x7fafead92000) liblzma.so.5 = /lib/x86_64-linux-gnu/liblzma.so.5 (0x7fafeab6e000) librt.so.1 = /lib/x86_64-linux-gnu/librt.so.1 (0x7fafea966000) libuuid.so.1 = /lib/x86_64-linux-gnu/libuuid.so.1 (0x7fafea76) /lib64/ld-linux-x86-64.so.2 (0x560eeff0d000) -- System Information: Debian Release: stretch/sid APT prefers unstable APT policy: (500, 'unstable'), (300, 'testing'), (200, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.2.0-rc7+ (SMP w/4 CPU cores; PREEMPT) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages aptitude depends on: ii aptitude-common 0.7-1 ii libapt-pkg4.161.0.10.2 ii libboost-iostreams1.58.0 1.58.0+dfsg-3 ii libc6 2.19-19 ii libcwidget3v5 0.5.17-4 ii libgcc1 1:5.2.1-15 ii libncursesw5 6.0+20150810-1 ii libsigc++-2.0-0v5 2.4.1-2 ii libsqlite3-0 3.8.11.1-1 ii libstdc++65.2.1-15 ii libtinfo5 6.0+20150810-1 ii libxapian22v5 1.2.21-1.2 Versions of packages aptitude recommends: pn aptitude-doc-en | aptitude-doc none ii libparse-debianchangelog-perl 1.2.0-7 ii sensible-utils 0.0.9 Versions of packages aptitude suggests: ii apt-xapian-index 0.47 pn debtags none pn tasksel none -- no debconf information
Bug#791276: marked as done (shiboken: library transition may be needed when GCC 5 is the default)
Your message dated Tue, 25 Aug 2015 16:00:15 + with message-id e1zugdz-0005ob...@franck.debian.org and subject line Bug#791276: fixed in shiboken 1.2.2-2 has caused the Debian Bug report #791276, regarding shiboken: library transition may be needed when GCC 5 is the default 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 ow...@bugs.debian.org immediately.) -- 791276: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=791276 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: src:shiboken Version: 1.2.2-1 Severity: important Tags: sid stretch User: debian-...@lists.debian.org Usertags: libstdc++-cxx11 Background [1]: libstdc++6 introduces a new ABI to conform to the C++11 standard, but keeps the old ABI to not break existing binaries. Packages which are built with g++-5 from experimental (not the one from testing/unstable) are using the new ABI. Libraries built from this source package export some of the new __cxx11 or B5cxx11 symbols, and dropping other symbols. If these symbols are part of the API of the library, then this rebuild with g++-5 will trigger a transition for the library. What is needed: - Rebuild the library using g++/g++-5 from experimental. Note that most likely all C++ libraries within the build dependencies need a rebuild too. You can find the log for a rebuild in https://people.debian.org/~doko/logs/gcc5-20150701/ Search for BEGIN GCC CXX11 in the log. - Decide if the symbols matching __cxx11 or B5cxx11 are part of the library API, and are used by the reverse dependencies of the library. - If there are no symbols matching __cxx11 or B5cxx11 in the symbols forming the library API, you should close this issue with a short explanation. - If there are no reverse dependencies, it should be the package maintainers decision if a transition is needed. However this might break software which is not in the Debian archive, and built against these packages. - If a library transition is needed, please prepare for the change. Rename the library package, append v5 to the name of the package (e.g. libfoo2 - libfoo2v5). Such a change can be avoided, if you have a soversion bump and you upload this version instead of the renamed package. Prepare a patch and attach it to this issue (mark this issue with patch), so that it is possible to NMU such a package. We'll probably have more than hundred transitions triggered. Then reassign the issue to release.debian.org and properly tag it as a transition issue, by sending an email to cont...@bugs.debian.org: user release.debian@packages.debian.org usertag this issue + transition block this issue by 790756 reassign this issue release.debian.org - If unsure if a transition is needed, please tag the issue with help to ask for feedback from other Debian developers. The libstdc++6 transition will be a large one, and it will come with a lot of pain. Please help it by preparing the follow-up transitions. [1] https://wiki.debian.org/GCC5#libstdc.2B-.2B-_ABI_transition ---End Message--- ---BeginMessage--- Source: shiboken Source-Version: 1.2.2-2 We believe that the bug you reported is fixed in the latest version of shiboken, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 791...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Didier Raboud o...@debian.org (supplier of updated shiboken package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Mon, 24 Aug 2015 17:40:32 +0200 Source: shiboken Binary: shiboken shiboken-doc libshiboken1.2v5 libshiboken-py3-1.2v5 libshiboken-dev shiboken-dbg Architecture: source amd64 all Version: 1.2.2-2 Distribution: unstable Urgency: medium Maintainer: Debian Python Modules Team python-modules-t...@lists.alioth.debian.org Changed-By: Didier Raboud o...@debian.org Description: libshiboken-dev - development files for the shiboken bindings generator library libshiboken-py3-1.2v5 - CPython3 bindings generator for C++ libraries - shared library libshiboken1.2v5 - CPython bindings generator for C++ libraries - shared library shiboken - CPython
Bug#778118: marked as done (shiboken: ftbfs with GCC-5)
Your message dated Tue, 25 Aug 2015 16:00:15 + with message-id e1zugdz-0005ov...@franck.debian.org and subject line Bug#778118: fixed in shiboken 1.2.2-2 has caused the Debian Bug report #778118, regarding shiboken: ftbfs with GCC-5 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 ow...@bugs.debian.org immediately.) -- 778118: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=778118 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: src:shiboken Version: 1.2.2-1 Severity: normal Tags: sid stretch User: debian-...@lists.debian.org Usertags: ftbfs-gcc-5 Please keep this issue open in the bug tracker for the package it was filed for. If a fix in another package is required, please file a bug for the other package (or clone), and add a block in this package. Please keep the issue open until the package can be built in a follow-up test rebuild. The package fails to build in a test rebuild on at least amd64 with gcc-5/g++-5, but succeeds to build with gcc-4.9/g++-4.9. The severity of this report may be raised before the stretch release. The full build log can be found at: http://people.debian.org/~doko/logs/gcc5-20150205/shiboken_1.2.2-1_unstable_gcc5.log The last lines of the build log are at the end of this report. To build with GCC 5, either set CC=gcc-5 CXX=g++-5 explicitly, or install the gcc, g++, gfortran, ... packages from experimental. apt-get -t experimental install g++ Common build failures are C11 as the default C mode, new warnings resulting in build failures with -Werror turned on, or new/dropped symbols in Debian symbols files. For other C/C++ related build failures see the porting guide at http://gcc.gnu.org/gcc-5/porting_to.html [...] - (optional=templinst)_ZNSt4listIP9SbkObjectSaIS1_EED2Ev@Base 1.0.4 - (optional=templinst)_ZNSt4listIP9SbkObjectSaIS1_EEaSERKS3_@Base 1.0.0~beta2 - (optional=templinst)_ZNSt4pairIKP13SbkObjectTypeSt4listIS1_SaIS1_EEED1Ev@Base 1.0.0~beta3 - (optional=templinst)_ZNSt4pairIKP13SbkObjectTypeSt4listIS1_SaIS1_EEED2Ev@Base 1.1.2 - (optional=templinst)_ZNSt4pairIKSsPN8Shiboken12TypeResolverEED1Ev@Base 1.1.2 - (optional=templinst)_ZNSt4pairIKSsPN8Shiboken12TypeResolverEED2Ev@Base 1.1.2 - (optional=templinst)_ZNSt4pairIKSsSt4listIP9SbkObjectSaIS3_EEED1Ev@Base 1.0.0~beta2 - (optional=templinst)_ZNSt4pairIKSsSt4listIP9SbkObjectSaIS3_EEED2Ev@Base 1.0.0~beta3 - (optional=templinst)_ZNSt8_Rb_treeIP11_typeobjectSt4pairIKS1_SsESt10_Select1stIS4_ESt4lessIS1_ESaIS4_EE8_M_eraseEPSt13_Rb_tree_nodeIS4_E@Base 1.0.5 - (optional=templinst)_ZNSt8_Rb_treeIP7_objectS1_St9_IdentityIS1_ESt4lessIS1_ESaIS1_EE16_M_insert_uniqueERKS1_@Base 1.0.9 - (optional=templinst)_ZNSt8_Rb_treeIP7_objectS1_St9_IdentityIS1_ESt4lessIS1_ESaIS1_EE8_M_eraseEPSt13_Rb_tree_nodeIS1_E@Base 1.0.9 - (optional=templinst)_ZNSt8_Rb_treeIP9SbkObjectS1_St9_IdentityIS1_ESt4lessIS1_ESaIS1_EE10_M_insert_EPKSt18_Rb_tree_node_baseSA_RKS1_@Base 1.0.0~beta5 +#MISSING: 1.2.2-1# (optional=templinst)_ZNSt4listIP7_objectSaIS1_EEaSERKS3_@Base 1.0.4 +#MISSING: 1.2.2-1# (optional=templinst)_ZNSt4listIP9SbkObjectSaIS1_EED1Ev@Base 1.0.0~beta3 +#MISSING: 1.2.2-1# (optional=templinst)_ZNSt4listIP9SbkObjectSaIS1_EED2Ev@Base 1.0.4 +#MISSING: 1.2.2-1# (optional=templinst)_ZNSt4listIP9SbkObjectSaIS1_EEaSERKS3_@Base 1.0.0~beta2 +#MISSING: 1.2.2-1# (optional=templinst)_ZNSt4pairIKP13SbkObjectTypeSt4listIS1_SaIS1_EEED1Ev@Base 1.0.0~beta3 +#MISSING: 1.2.2-1# (optional=templinst)_ZNSt4pairIKP13SbkObjectTypeSt4listIS1_SaIS1_EEED2Ev@Base 1.1.2 +#MISSING: 1.2.2-1# (optional=templinst)_ZNSt4pairIKSsPN8Shiboken12TypeResolverEED1Ev@Base 1.1.2 +#MISSING: 1.2.2-1# (optional=templinst)_ZNSt4pairIKSsPN8Shiboken12TypeResolverEED2Ev@Base 1.1.2 +#MISSING: 1.2.2-1# (optional=templinst)_ZNSt4pairIKSsSt4listIP9SbkObjectSaIS3_EEED1Ev@Base 1.0.0~beta2 +#MISSING: 1.2.2-1# (optional=templinst)_ZNSt4pairIKSsSt4listIP9SbkObjectSaIS3_EEED2Ev@Base 1.0.0~beta3 +#MISSING: 1.2.2-1# (optional=templinst)_ZNSt8_Rb_treeIP11_typeobjectSt4pairIKS1_SsESt10_Select1stIS4_ESt4lessIS1_ESaIS4_EE8_M_eraseEPSt13_Rb_tree_nodeIS4_E@Base 1.0.5 +#MISSING: 1.2.2-1# (optional=templinst)_ZNSt8_Rb_treeIP7_objectS1_St9_IdentityIS1_ESt4lessIS1_ESaIS1_EE16_M_insert_uniqueERKS1_@Base 1.0.9 +#MISSING: 1.2.2-1# (optional=templinst)_ZNSt8_Rb_treeIP7_objectS1_St9_IdentityIS1_ESt4lessIS1_ESaIS1_EE8_M_eraseEPSt13_Rb_tree_nodeIS1_E@Base 1.0.9 +#MISSING: 1.2.2-1# (optional=templinst)_ZNSt8_Rb_treeIP9SbkObjectS1_St9_IdentityIS1_ESt4lessIS1_ESaIS1_EE10_M_insert_EPKSt18_Rb_tree_node_baseSA_RKS1_@Base 1.0.0~beta5
Bug#777601: systemd: Loosing LXC memory cgroups after service install
On Tue, 25 Aug 2015 18:41:59 +0200 Luca Bruno lethalma...@gmail.com wrote: I've tried this patch and looks like adding another bug to me. Please confirm what I'm experiencing. It's true, it does not remove cgroups created by systemd, but then it doesn't cleanup cgroups that systemd created either. Correction, sorry for the confusing wording: It's true, it does not remove cgroups *not* created by systemd, but then it doesn't cleanup cgroups that systemd created either.
Processed: tagging 796422
Processing commands for cont...@bugs.debian.org: tags 796422 + sid stretch Bug #796422 [src:libopengl-image-perl] libopengl-image-perl: FTBFS: perl5/5.20/auto/OpenGL/OpenGL.so: undefined symbol: glResizeBuffersMESA Added tag(s) stretch and sid. thanks Stopping processing here. Please contact me if you need assistance. -- 796422: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=796422 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#777601: systemd: Loosing LXC memory cgroups after service install
Control: unarchive -1 On Thu, 12 Feb 2015 15:43:30 +0100 Martin Pitt mp...@debian.org wrote: Hello again, so the patch that got proposed at http://lists.freedesktop.org/archives/systemd-devel/2014-September/023276.html actually makes a lot of sense: This makes systemd only clean up cgroups that it created by itself, and thus won't clean up empty ones in other controllers that LXC created. I tested this and committed this for the experimental branch for now: http://anonscm.debian.org/cgit/pkg-systemd/systemd.git/commit/?h=experimentalid=286ef78fd I'd like to see this out in the wild for some time before applying it to jessie, though. I'm also still interested in what the actual impact of that is -- critical seems rather inflated? Losing empty cgroups doesn't sound that dangerous after all, aside from the LXC warnings when shutting down a container? Thanks, I've tried this patch and looks like adding another bug to me. Please confirm what I'm experiencing. It's true, it does not remove cgroups created by systemd, but then it doesn't cleanup cgroups that systemd created either. Example: 1) set MemoryLimit to a service, the memory limit will appear in the cgroups 2) unset MemoryLimit to the same service, reload daemon, restart, disable, re-enable, whatever... but the memory limit will NOT disappear from the cgroups Seems wrong and possibly worse to me. Best regards,
Bug#796874: gtkspellmm: transition needed for g++-5 ABI
Hi Simon, thanks again for taking care of this transition - it's really appreciated! I think I fixed the package, could you have a look and sponsor it if it fits for you? http://anonscm.debian.org/cgit/collab-maint/gtkspellmm.git Thanks, Philip signature.asc Description: OpenPGP digital signature
Bug#779803: smuxi performs autoconnect on first startup
Control: tags 779803 + fixed pending Upstream fix to not reveal realname: https://github.com/meebey/smuxi/commit/f21cc42e087e93f621b1a368770f46e41d6cff2f trivial on purpose in order to not introduce regressions signature.asc Description: OpenPGP digital signature
Bug#796863: libassa3.5-5v5 and libassa-3.5-5v5: error when trying to install together
* Riley Baird (bm-2cvqnduybau5do2dfjtrn7zbaj246s4...@bitmessage.ch) wrote: This is listed in the FTP master's cruft report, so if I'm correct, it shouldn't be necessary to request a removal from unstable. Yeah and you have the right conflicts/replaces. I'm surprised it's complaining about this. -- Eric Dorland e...@kuroneko.ca 43CF 1228 F726 FD5B 474C E962 C256 FBD5 0022 1E93 signature.asc Description: Digital signature
Bug#777833: digikam: ftbfs with GCC-5 (patch)
tags 777833 patch thanks Hello all, I tried to rebuild digikam on sid today. The current version still misses libsoprano-dev dependency and fails with: make[3]: *** No rule to make target '/usr/lib/libsoprano.so', needed by 'lib/libkvkontakte.so.1.0.0'. Stop. Once a build-time dependency on libsoprano-dev was declared, I was able to compile digikam on a sid sbuild, it linked against the new opencv-*2.4v5 libraries. - Danny diff -Nru digikam-4.4.0/debian/control digikam-4.4.0/debian/control --- digikam-4.4.0/debian/control2014-11-15 17:37:35.0 +0100 +++ digikam-4.4.0/debian/control2015-08-10 14:51:04.0 +0200 @@ -6,6 +6,7 @@ Build-Depends: debhelper (= 9), pkg-kde-tools (= 0.9), pkg-config, cmake (= 2.6.2), doxygen, kdelibs5-dev, kdepimlibs5-dev, + libsoprano-dev, libmarble-dev, libkipi-dev (= 4:4.12), libkexiv2-dev (= 4:4.12), libkdcraw-dev (= 4:4.12), libksane-dev, baloo-dev, libkfilemetadata-dev,
Bug#792206: apt-cacher: modifies conffiles (policy 10.7.3): /etc/default/apt-cacher
package apt-cacher notfound 792206 1.7.11 thanks
Processed: Re: Bug#792206: apt-cacher: modifies conffiles (policy 10.7.3): /etc/default/apt-cacher
Processing commands for cont...@bugs.debian.org:
package apt-cacher
Limiting to bugs with field 'package' containing at least one of 'apt-cacher'
Limit currently set to 'package':'apt-cacher'
notfound 792206 1.7.11
Bug #792206 {Done: Mark Hindley m...@hindley.org.uk} [apt-cacher] apt-cacher:
modifies conffiles (policy 10.7.3): /etc/default/apt-cacher
Bug #688890 {Done: Mark Hindley m...@hindley.org.uk} [apt-cacher] apt-cacher:
modifies conffiles (policy 10.7.3): /etc/default/apt-cacher
No longer marked as found in versions apt-cacher/1.7.11.
No longer marked as found in versions apt-cacher/1.7.11.
thanks
Stopping processing here.
Please contact me if you need assistance.
--
688890: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=688890
792206: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=792206
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Bug#796400: [pkg-go] Bug#796400: Bug#796400: golang-github-jacobsa-ratelimit: Non-determistically FTBFS due to unreliable timing in tests
Sure. Are you able to modify the test before running it on the relevant system and find a timing that works reliably? lamby, do I have access to the system on which the tests don’t pass? I fear gaining access to this machine would serve no real purpose; the solution here is not to bump the values so that the test is less flaky - the test would remain non-determistic and thus this bug would remain unresolved IMHO, even though it might be harder to trigger. As a concept, I have no problem with automated solutions to point out potential performance regressions, but having a testsuite that fails non-determinstically is generally perceived to be a Bad Idea in software engineering. Perhaps some sort of switch or environment variable can be introduced to enable them so that they do not get in the way of the regular build. Regards, -- ,''`. : :' : Chris Lamb `. `'` la...@debian.org / chris-lamb.co.uk `-
Bug#777601: systemd: Loosing LXC memory cgroups after service install
Am 25.08.2015 um 18:41 schrieb Luca Bruno: I've tried this patch and looks like adding another bug to me. Please confirm what I'm experiencing. It's true, it does not remove cgroups created by systemd, but then it doesn't cleanup cgroups that systemd created either. Example: 1) set MemoryLimit to a service, the memory limit will appear in the cgroups 2) unset MemoryLimit to the same service, reload daemon, restart, disable, re-enable, whatever... but the memory limit will NOT disappear from the cgroups Seems wrong and possibly worse to me. Please raise your issue upstream -- Why is it that all of the instruments seeking intelligent life in the universe are pointed away from Earth? signature.asc Description: OpenPGP digital signature
Bug#777953: marked as done (libkolabxml: ftbfs with GCC-5)
Your message dated Tue, 25 Aug 2015 22:04:46 -0700 with message-id 2932562.1HvEW72JP9@myrada and subject line ftbfs with GCC-5 has caused the Debian Bug report #777953, regarding libkolabxml: ftbfs with GCC-5 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 ow...@bugs.debian.org immediately.) -- 777953: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=777953 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: src:libkolabxml Version: 1.0.2-2 Severity: normal Tags: sid stretch User: debian-...@lists.debian.org Usertags: ftbfs-gcc-5 Please keep this issue open in the bug tracker for the package it was filed for. If a fix in another package is required, please file a bug for the other package (or clone), and add a block in this package. Please keep the issue open until the package can be built in a follow-up test rebuild. The package fails to build in a test rebuild on at least amd64 with gcc-5/g++-5, but succeeds to build with gcc-4.9/g++-4.9. The severity of this report may be raised before the stretch release. The full build log can be found at: http://people.debian.org/~doko/logs/gcc5-20150205/libkolabxml_1.0.2-2_unstable_gcc5.log The last lines of the build log are at the end of this report. To build with GCC 5, either set CC=gcc-5 CXX=g++-5 explicitly, or install the gcc, g++, gfortran, ... packages from experimental. apt-get -t experimental install g++ Common build failures are C11 as the default C mode, new warnings resulting in build failures with -Werror turned on, or new/dropped symbols in Debian symbols files. For other C/C++ related build failures see the porting guide at http://gcc.gnu.org/gcc-5/porting_to.html [...] + _ZNSt8_Rb_treeIPKN3xsd3cxx4tree8identityESt4pairIKS5_PNS2_5_typeEESt10_Select1stISA_ENS8_19identity_comparatorESaISA_EE10_M_insert_INSF_11_Alloc_nodeEEESt17_Rb_tree_iteratorISA_EPSt18_Rb_tree_node_baseSL_RKSA_RT_@Base 1.0.2-2 (optional=templinst)_ZNSt8_Rb_treeIPKN3xsd3cxx4tree8identityESt4pairIKS5_PNS2_5_typeEESt10_Select1stISA_ENS8_19identity_comparatorESaISA_EE11equal_rangeERS7_@Base 1.0.1 (optional=templinst)_ZNSt8_Rb_treeIPKN3xsd3cxx4tree8identityESt4pairIKS5_PNS2_5_typeEESt10_Select1stISA_ENS8_19identity_comparatorESaISA_EE16_M_insert_uniqueERKSA_@Base 1.0.1 (optional=templinst)_ZNSt8_Rb_treeIPKN3xsd3cxx4tree8identityESt4pairIKS5_PNS2_5_typeEESt10_Select1stISA_ENS8_19identity_comparatorESaISA_EE24_M_get_insert_unique_posERS7_@Base 1.0.1 @@ -7560,9 +7681,10 @@ (optional=templinst)_ZNSt8_Rb_treeIPKSt9type_infoSt4pairIKS2_N3xsd3cxx4tree19type_serializer_mapIcE9type_infoEESt10_Select1stISB_ENS9_18type_id_comparatorESaISB_EE24_M_get_insert_unique_posERS4_@Base 1.0.1 (optional=templinst|arch=alpha amd64 hppa hurd-i386 i386 kfreebsd-amd64 kfreebsd-i386 mips mipsel powerpc s390x sparc x32)_ZNSt8_Rb_treeIPKSt9type_infoSt4pairIKS2_N3xsd3cxx4tree19type_serializer_mapIcE9type_infoEESt10_Select1stISB_ENS9_18type_id_comparatorESaISB_EE29_M_get_insert_hint_unique_posESt23_Rb_tree_const_iteratorISB_ERS4_@Base 1.0.1 (optional=templinst)_ZNSt8_Rb_treeIPKSt9type_infoSt4pairIKS2_N3xsd3cxx4tree19type_serializer_mapIcE9type_infoEESt10_Select1stISB_ENS9_18type_id_comparatorESaISB_EE5eraseERS4_@Base 1.0.1 - (optional=templinst)_ZNSt8_Rb_treeIPKSt9type_infoSt4pairIKS2_N3xsd3cxx4tree19type_serializer_mapIcE9type_infoEESt10_Select1stISB_ENS9_18type_id_comparatorESaISB_EE7_M_copyEPKSt13_Rb_tree_nodeISB_EPSI_@Base 1.0.1 +#MISSING: 1.0.2-2# (optional=templinst)_ZNSt8_Rb_treeIPKSt9type_infoSt4pairIKS2_N3xsd3cxx4tree19type_serializer_mapIcE9type_infoEESt10_Select1stISB_ENS9_18type_id_comparatorESaISB_EE7_M_copyEPKSt13_Rb_tree_nodeISB_EPSI_@Base 1.0.1 + _ZNSt8_Rb_treeIPKSt9type_infoSt4pairIKS2_N3xsd3cxx4tree19type_serializer_mapIcE9type_infoEESt10_Select1stISB_ENS9_18type_id_comparatorESaISB_EE7_M_copyINSG_11_Alloc_nodeEEEPSt13_Rb_tree_nodeISB_EPKSK_SL_RT_@Base 1.0.2-2 (optional=templinst)_ZNSt8_Rb_treeIPKSt9type_infoSt4pairIKS2_N3xsd3cxx4tree19type_serializer_mapIcE9type_infoEESt10_Select1stISB_ENS9_18type_id_comparatorESaISB_EE8_M_eraseEPSt13_Rb_tree_nodeISB_E@Base 1.0.1 - (optional=templinst)_ZNSt8_Rb_treeISsSt4pairIKSsN3xsd3cxx3xml3dom14namespace_infoIcEEESt10_Select1stIS8_ESt4lessISsESaIS8_EE10_M_insert_EPSt18_Rb_tree_node_baseSG_RKS8_@Base 1.0.1 +#MISSING: 1.0.2-2# (optional=templinst)_ZNSt8_Rb_treeISsSt4pairIKSsN3xsd3cxx3xml3dom14namespace_infoIcEEESt10_Select1stIS8_ESt4lessISsESaIS8_EE10_M_insert_EPSt18_Rb_tree_node_baseSG_RKS8_@Base 1.0.1 (optional=templinst|arch=alpha armel armhf hurd-i386 i386 kfreebsd-i386 mips mipsel powerpc s390x
Bug#796949: piuparts: Missing Build-Depends on python-lzma
Source: piuparts
Version: 0.65
Severity: serious
Justification: fails to build from source
User: reproducible-bui...@lists.alioth.debian.org
Usertags: ftbfs
X-Debbugs-Cc: reproducible-bui...@lists.alioth.debian.org
Dear Maintainer,
piuparts fails to build from source in unstable/amd64 due
to missing Build-Depends on python-lzma:
[..]
==
ERROR: Failure: ImportError (No module named lzma)
--
Traceback (most recent call last):
File /usr/lib/python2.7/dist-packages/nose/loader.py, line 420, in
loadTestsFromName
addr.filename, addr.module)
File /usr/lib/python2.7/dist-packages/nose/importer.py, line 47,
in importFromPath
return self.importFromDir(dir_path, fqname)
File /usr/lib/python2.7/dist-packages/nose/importer.py, line 94,
in importFromDir
mod = load_module(part_fqname, fh, filename, desc)
File /tmp/buildd/piuparts-0.65/tests/test_pkgsummary.py, line 8,
in module
import piupartslib.pkgsummary as pkgsummary
File /tmp/buildd/piuparts-0.65/piupartslib/__init__.py, line 22,
in module
import lzma
ImportError: No module named lzma
--
Ran 5 tests in 0.111s
FAILED (errors=5)
Makefile:149: recipe for target 'check' failed
make[1]: *** [check] Error 1
make[1]: Leaving directory '/tmp/buildd/piuparts-0.65'
dh_auto_test: make -j1 check returned exit code 2
debian/rules:7: 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/piuparts_0.65.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 Aug 25 07:35:51 GMT+12 2015
I: pbuilder-time-stamp: 1440531351
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 pbuilder-ma...@lists.alioth.debian.org
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.20120909~), python (= 2.7), python-debian,
python-apt, python-distro-info, python-nose, python-debianbts, python-yaml,
python-mox3, asciidoc, git, xmlto
dpkg-deb: building package 'pbuilder-satisfydepends-dummy' in
'/tmp/satisfydepends-aptitude/pbuilder-satisfydepends-dummy.deb'.
Selecting previously unselected package pbuilder-satisfydepends-dummy.
(Reading database ... 20247 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 (= 2.7); however:
Package python is not installed.
pbuilder-satisfydepends-dummy depends on python-debian; however:
Package python-debian is not installed.
pbuilder-satisfydepends-dummy depends on python-apt; however:
Package python-apt is not installed.
pbuilder-satisfydepends-dummy depends on python-distro-info; however:
Package python-distro-info is not installed.
pbuilder-satisfydepends-dummy depends on python-nose; however:
Package python-nose is not installed.
pbuilder-satisfydepends-dummy depends on python-debianbts; however:
Package python-debianbts is not installed.
pbuilder-satisfydepends-dummy depends on python-yaml; however:
Package python-yaml is not installed.
pbuilder-satisfydepends-dummy depends on python-mox3; however:
Package python-mox3 is not installed.
pbuilder-satisfydepends-dummy depends on asciidoc; however:
Package as
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:
asciidoc{a} ca-certificates{a} distro-info-data{a} docbook-xml{a}
docbook-xsl{a} git{a} git-man{a} libapt-inst1.7{a}
Processed: your mail
Processing commands for cont...@bugs.debian.org: fixed 795623 2.6.0 Bug #795623 [src:jackson-datatype-joda] jackson-datatype-joda: FTBFS under some locales (eg. fr_CH.UTF-8) The source 'jackson-datatype-joda' and version '2.6.0' do not appear to match any binary packages Marked as fixed in versions jackson-datatype-joda/2.6.0. End of message, stopping processing here. Please contact me if you need assistance. -- 795623: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=795623 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#796298: tcplay: FTBFS: CMake Error at CMakeLists.txt:30 (message): Could not find the devmapper library
On Fri, Aug 21, 2015 at 10:10 AM, Chris Lamb la...@debian.org wrote: Source: tcplay Version: 1.1-2 Severity: serious Justification: fails to build from source CMake Error at CMakeLists.txt:30 (message): Could not find the devmapper library From a cursory glance, devmapper.pc specifies Requires.Private librt, which doesn't have a librt.pc (which is likely correct as it's meant to be linked statically? I'll leave it to you). You are right in the sense that without 'Requires.private:' the devmapper library is found correctly. On the other hand I don't think static linking is mandatory as libdevmapper.so.* exists and is under /lib (no need to have /usr mounted, can be used in emergency shells as well). Can be a cmake issue? Will investigate further. Laszlo/GCS
Bug#796950: NameError: global name 're' is not defined
Package: obnam
Version: 1.15-1
Severity: grave
Justification: renders package unusable
Dear Maintainer,
I was attempting to run obnam backup and received the following python stack
trace.
Traceback (most recent call last):
File /usr/lib/python2.7/dist-packages/cliapp/app.py, line 189, in _run
self.process_args(args)
File /usr/lib/python2.7/dist-packages/obnamlib/app.py, line 206, in
process_args
self.hooks.call('config-loaded')
File /usr/lib/python2.7/dist-packages/obnamlib/hooks.py, line 188, in call
self.hooks[name].call_callbacks(*args, **kwargs)
File /usr/lib/python2.7/dist-packages/obnamlib/hooks.py, line 65, in
call_callbacks
callback(*args, **kwargs)
File /usr/lib/python2.7/dist-
packages/obnamlib/plugins/exclude_pathnames_plugin.py, line 57, in
config_loaded
self.compile_exclusion_patterns()
File /usr/lib/python2.7/dist-
packages/obnamlib/plugins/exclude_pathnames_plugin.py, line 81, in
compile_exclusion_patterns
self.compile_regexps(regexps, self.pathname_excluder.exclude_regexp)
File /usr/lib/python2.7/dist-
packages/obnamlib/plugins/exclude_pathnames_plugin.py, line 97, in
compile_regexps
except re.error as e:
NameError: global name 're' is not defined
Looking at exclude_pathnames_plugin.py it does call except re.error and I
couldn't find a corresponding import re. So something seems wrong.
Attached are the modifications I made to exclude_pathnames_plugin in order to
get it to work.
--- /tmp/exclude_pathnames_plugin.py 2015-08-25 22:27:42.290914865 -0700
+++ /usr/lib/python2.7/dist-packages/obnamlib/plugins/exclude_pathnames_plugin.py 2015-08-25 22:27:13.923549566 -0700
@@ -18,8 +18,9 @@
import logging
import os
import stat
import time
+import re
import obnamlib
@@ -93,11 +94,11 @@
logging.debug('Regular expression: %s', regexp)
try:
compiler(regexp)
except re.error as e:
-msg = ('error compiling regular expression %s: %s' % (x, e))
+msg = ('error compiling regular expression %s: %s' % (regexp, e))
logging.error(msg)
-self.progress.error(msg)
+#self.progress.error(msg)
def read_patterns_from_files(self, filenames):
patterns = []
for filename in filenames:
Bug#795014: marked as done (libadplug-2.2.1-0 broke ABI in binNMU due to libstdc++6 transition)
Your message dated Wed, 26 Aug 2015 12:23:39 +0800 with message-id 20150826042339.GB15010@adam-laptop and subject line Re: Bug#795014: Info received (Bug#795014: fixed in adplug 2.2.1+dfsg3-0.3) has caused the Debian Bug report #795014, regarding libadplug-2.2.1-0 broke ABI in binNMU due to libstdc++6 transition 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 ow...@bugs.debian.org immediately.) -- 795014: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=795014 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: mpd Version: 0.19.10-1+b2 Severity: grave Justification: renders package unusable Dear Maintainer, After dist-upgrade, mpd does not start anymore in unstable; indeed, running /usr/bin/mpd yields: /usr/bin/mpd: symbol lookup error: /usr/bin/mpd: undefined symbol: _ZN7CAdPlug7factoryERKSsP4CoplRK8CPlayersRK13CFileProvider All DSOs required by mpd are present on the system: $ LANG=C ldd /usr/bin/mpd | grep 'found' $ After a short investigation, it appears the missing symbol is supposed to be found in /usr/lib/libadplug-2.2.1.so.0; alas, there is a symbol name mismatch: * mpd requires _ZN7CAdPlug7factoryERKSsP4CoplRK8CPlayersRK13CFileProvider * libadplug-2.2.1.so.0 provides _ZN7CAdPlug7factoryERKNSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEEP4CoplRK8CPlayersRK13CFileProvider The latter statement can be checked using readelf: $ readelf --wide --symbols /usr/lib/libadplug-2.2.1.so.0 | grep _ZN7CAdPlug7factory 358: 000247d0 692 FUNCGLOBAL DEFAULT 11 _ZN7CAdPlug7factoryERKNSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEEP4CoplRK8CPlayersRK13CFileProvider This behaviour was observed with packages: * mpd: 0.19.10-1+b2 * libadplug-2.2.1-0: 2.2.1+dfsg3-0.2+b1 I am unsure whether the fix should occur in mpd or libadplug, so I reported this bug for mpd, as it is rendered unusable by the issue. -- System Information: Debian Release: stretch/sid APT prefers unstable APT policy: (500, 'unstable'), (500, 'stable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.1.0-1-amd64 (SMP w/8 CPU cores) Locale: LANG=en_US.ISO-8859-15, LC_CTYPE=en_US.ISO-8859-15 (charmap=ISO-8859-15) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages mpd depends on: ii adduser 3.113+nmu3 ii init-system-helpers 1.23 ii libadplug-2.2.1-0 2.2.1+dfsg3-0.2+b1 ii libao41.1.0-3 ii libasound21.0.29-1 ii libaudiofile1 0.3.6-2+b1 ii libavahi-client3 0.6.31-5 ii libavahi-common3 0.6.31-5 ii libavcodec-ffmpeg56 7:2.7.2-1 ii libavformat-ffmpeg56 7:2.7.2-1 ii libavutil-ffmpeg547:2.7.2-1 ii libbz2-1.01.0.6-8 ii libc6 2.19-19 ii libcdio-cdda1 0.83-4.2 ii libcdio-paranoia1 0.83-4.2 ii libcdio13 0.83-4.2 ii libcurl3-gnutls 7.43.0-1 ii libdbus-1-3 1.8.20-1 ii libexpat1 2.1.0-7 ii libfaad2 2.8.0~cvs20150510-1 ii libflac8 1.3.1-4 ii libfluidsynth11.1.6-2 ii libglib2.0-0 2.44.1-1.1 ii libgme0 0.5.5-2.1 ii libicu52 52.1-10 ii libid3tag00.15.1b-11 ii libiso9660-8 0.83-4.2 ii libjack0 [libjack-0.116] 1:0.124.1+20140122git5013bed0-3 ii libmad0 0.15.1b-8 ii libmikmod33.3.7-1 ii libmms0 0.6.2-4 ii libmodplug1 1:0.8.8.5-1 ii libmp3lame0 3.99.5+repack1-9 ii libmpcdec62:0.1~r459-4.1 ii libmpdclient2 2.9-1 ii libmpg123-0 1.22.2-1 ii libnfs8 1.9.7-2 ii libogg0 1.3.2-1 ii libopenal11:1.16.0-3 ii libopus0 1.1-2 ii libpulse0 6.0-5 ii libresid-builder0c2a 2.1.1-14 ii libroar2 1.0~beta11-3 ii libsamplerate00.1.8-8 ii libshout3 2.3.1-3 ii libsidplay2 2.1.1-14 ii libsidutils0 2.1.1-14 ii libsmbclient 2:4.1.17+dfsg-4 ii libsndfile1 1.0.25-9.1 ii libsoxr0 0.1.1-1 ii libsqlite3-0 3.8.11.1-1 ii libstdc++65.2.1-14 ii libsystemd0 224-1 ii libupnp6 1:1.6.19+git20141001-1 ii libvorbis0a 1.3.4-2 ii libvorbisenc2 1.3.4-2 ii libvorbisfile31.3.4-2 ii
Bug#794581: Happened again! Argh!
On Tue, 25 Aug 2015 18:42:11 -0400 Scott Kitterman deb...@kitterman.com wrote: You should only have to downgrade breeze. Today's rebuild of kdecorations should resolve its problems. So downgrade breeze to the testing version and upgrade kdecorations to the +b1 version. So confirmed, thank you. This is technically my fault for mixing testing and sid packages, so I owe you all an apology. Having said that, will things be relatively stable for the next little while? I'm missing my window decorations now, but that's another bug that I hope will auto-correct with the next batch of packages entering testing. At least I can work around that and use my desktop again.
Bug#789875: subsurface: FTBFS in experimental
On Tue, 2015-08-25 at 17:55 -0700, Dirk Hohndel wrote: Being called stupid and arrogant is usually not a great conversation opener, but hey, I've been called worse. Well I should have probably immediately apologised along the way, just for the sake of politeness... But the believe to know it much better than everyone else apparently does qualifies quite well for arrogance. And intentionally trying/wishing to keep the distros, while these are at the same time the major and preferred way of software distribution for the whole community where oneself comes from... for sure you know the German saying an dem Ast sägen auf dem man sitzt... so I guess that qualifies quite well for not making the smartest decisions. And because of those decades of proven philisophy Linux has taken over the desktop, correct? And become the #1 targeted platform of all major desktop applications. Well the reason for this is for sure not that we have proper package management systems and repositories... something which especially the Windows world never really managed to do and which causes them quite some problems - while everything which has them (or the proprietary/evil versions of them, aka appstores) is quite successful with them. And apart from that,... if one wants to be like Windows or like Mac, than the best is probably just to use these, ain't it? I guess many people in the FLOSS world are actually quite happy with Linux not having the 99% market share. As the past has sown over and over again (even within FLOSS, take GNOME as an exmaple): software with a too high market share tend to get evil, broken or are simply targeted towards end-end-end-users and no longer professionally usable. Sorry, that was snarky and I had promised myself not to be snarky but to be constructive. So let's strike that last comment. Yeah,... let's not go into completely unrelated topics... No, we have binaries available for Ubuntu, Fedora, OpenSUSE, Mint, and, of course, Debian. Then your download page is probably out of date, which still claims: Linux The Subsurface team is starting to make our own dedicated binaries available for a number of Linux versions. It apparently misses Fedora and Mint, and Debian seems to be simply the *buntu package? Anyway,... I probably can't speak for all possible users but I'm quite sure I'm not alone in not using such binaries by principle. That's why distros exist, that people don't have to maintain/upgrade/etc. all software themselves. Not to talk about the security nightmares that your model of software distribution brings along. So looking at my stats 4x as many Debian users are using the binaries we provide than the binaries that used to come with the distribution. But as a matter of fact both of those combined are less than 1% of our user base. And how do you get your stats? Making stats which are actually representative and don't just show what one wants to see isn't that easy. popcon is probably no guarantee, as it's not installed per default. End even if representative statistics would show that the upstream binaries are used more than the distro ones, than the reason may just be the artificial ones you've created yourself, by making subsurface difficult to package and thus outdated in distros. And of course for the vast majority of our libraries we use the system installed ones so the users do indeed benefit from any security updates that will happen in the distribution. Security isn't just in terms of up-to-date 3rd party libraries. subsurface itself may have vulnerabilities and it wouldn't be the first project whose website gets hacked and has forged binaries distributed. An application should be able to bring its own libraries for those libraries that it is so tightly coupled with that it makes no sense to allow random combinations. So today Subsurface prefers to run against our own branch of libdivecoputer and our own branch of libmarblewidget and requires the very VERY latest libgit2 (0.23) and libgrantlee (5.0.0). I think you're surely not the only program which has tightly coupled 3rd party libraries - yet other projects apoarently manage to properly deal with that... Either they find a way to better cooperate with the 3rd party libs respective upstreams and get their needs into that code (as it could perhaps be done with libdivecomputer),... or they take over / fork an anyway slowly maintained project (again, libdivecomputer?),... or they simply use other libraries which better serve there needs (Robert complained about libmarble beeing buggy[0] - why not just using something much simpler? marble seems to be anyway overkill for something like subsurface). And even *if* you say that a fork is really needed for certain libs, why not doing it properly? As Salvo said, The problem is caused by the fact that subsurface forked some libraries and made them incompatible, without changing the name. This isn't just bad, it's also quite hostile
Bug#796874: marked as done (gtkspellmm: transition needed for g++-5 ABI)
Your message dated Wed, 26 Aug 2015 05:00:11 + with message-id e1zusol-0002ma...@franck.debian.org and subject line Bug#796874: fixed in gtkspellmm 3.0.3+dfsg-2 has caused the Debian Bug report #796874, regarding gtkspellmm: transition needed for g++-5 ABI 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 ow...@bugs.debian.org immediately.) -- 796874: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=796874 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Source: gtkspellmm Version: 3.0.3+dfsg-1 Severity: serious Justification: ABI break Background[1]: libstdc++6 introduces a new ABI to conform to the C++11 standard, but keeps the old ABI to not break existing binaries. Packages which are built with g++-5 from experimental (not the one from testing/unstable) are using the new ABI. Libraries built from this source package export some of the new __cxx11 or B5cxx11 symbols, dropping other symbols. If these symbols are part of the API of the library, then this rebuild with g++-5 will trigger a transition for the library. In the case of gtkspellmm, Glib::ustring appears in header files that get installed; Glib::ustring has a std::string as a data member, resulting in sizeof(Glib::ustring) changing, so it seems very likely that a transition is needed. This will look a lot like the one for gstreamermm-1.0. I'm happy to sponsor or NMU as required. S ---End Message--- ---BeginMessage--- Source: gtkspellmm Source-Version: 3.0.3+dfsg-2 We believe that the bug you reported is fixed in the latest version of gtkspellmm, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 796...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Philip Rinn ri...@inventati.org (supplier of updated gtkspellmm package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Tue, 25 Aug 2015 18:24:10 +0200 Source: gtkspellmm Binary: libgtkspellmm-3.0-0v5 libgtkspellmm-3.0-dev libgtkspellmm-3.0-doc Architecture: all amd64 source Version: 3.0.3+dfsg-2 Distribution: unstable Urgency: medium Maintainer: Philip Rinn ri...@inventati.org Changed-By: Philip Rinn ri...@inventati.org Closes: 796874 Description: libgtkspellmm-3.0-0v5 - C++ wrapper library for GtkSpell (shared libraries) libgtkspellmm-3.0-dev - C++ wrapper library for GtkSpell (development files) libgtkspellmm-3.0-doc - C++ wrappers for GtkSpell (documentation) Changes: gtkspellmm (3.0.3+dfsg-2) unstable; urgency=medium . * Rename library for g++-5 transition (closes: #796874): - Add Conflicts/Replaces for the old library - Bump build-dependencies to g++-5-transitioned versions * Bump Standards-Version to 3.9.6 (no changes necessary) * Generate docs without timestamps to make the build reproducible Checksums-Sha1: 65486d956dec368d49ee8f8edff0ce3220ff0405 2150 gtkspellmm_3.0.3+dfsg-2.dsc b1aceb7fe6da0b29b209775132d48a34693b330b 4320 gtkspellmm_3.0.3+dfsg-2.debian.tar.xz 971cce4d5ce19790b2debc9df729fa9afd8ddd96 10710 libgtkspellmm-3.0-0v5_3.0.3+dfsg-2_amd64.deb aa18b2d458aad38d3e99aa2d838153551274b39b 6190 libgtkspellmm-3.0-dev_3.0.3+dfsg-2_amd64.deb 1d4d3ca093f8453697967427d4312373aad08c76 70988 libgtkspellmm-3.0-doc_3.0.3+dfsg-2_all.deb Checksums-Sha256: 273611db2ebed8c5efea2cf7af780cce56a11e7d54f94e763dab63836947a1df 2150 gtkspellmm_3.0.3+dfsg-2.dsc 3dec3da4cf56b81d758254f32a2c493e1928c796c064df79b1eb5b54b43861bf 4320 gtkspellmm_3.0.3+dfsg-2.debian.tar.xz f5c522f26eb20c0d5400a96694fa8bfb968b5dd1526bed6b56616dbb0986cf0d 10710 libgtkspellmm-3.0-0v5_3.0.3+dfsg-2_amd64.deb 0b528d3026f2cee47cf5ddce05294ecedd0bbb44424f830d56ca290407be0b33 6190 libgtkspellmm-3.0-dev_3.0.3+dfsg-2_amd64.deb 07c8900af4e97771a61fd8e3b8699127b20915bdf50d48695cd0c1107048ff15 70988 libgtkspellmm-3.0-doc_3.0.3+dfsg-2_all.deb Files: ae6e75663cee2eb52c33cd8b7a271e73 2150 libs optional gtkspellmm_3.0.3+dfsg-2.dsc 9319b0942aee22b8f3a87e179364950e 4320 libs optional gtkspellmm_3.0.3+dfsg-2.debian.tar.xz d9670220a3832e078b586e1fcd19e744 10710 libs optional libgtkspellmm-3.0-0v5_3.0.3+dfsg-2_amd64.deb a0ea228f6c8a690590f962d839d70a13 6190 libdevel optional libgtkspellmm-3.0-dev_3.0.3+dfsg-2_amd64.deb
Bug#796676: amarok: Amarok won't start
Hello, Is there any chance that you could install 2.8.0-3+b1 installs from sid? or possibly you could try 2.8.0-3 from snapshots.debian.org http://snapshot.debian.org/archive/debian/20150727T034022Z/pool/main/a/amarok/ (Depending on which side of the libstdc++6 transition you're on.) amarok 2.8.0-2 was built using libmysqld-pic 5.5 and at some point mysql 5.6 components started showing up which could cause a crash. Diane On Sun, 23 Aug 2015 15:31:45 +0200 adrian adr...@gmail.com wrote: Package: amarok Version: 2.8.0-2.1+b2 Severity: grave Justification: renders package unusable Dear maintainer As soon as I open amarok I get: QDBusConnection: session D-Bus connection created before QCoreApplication. Application may misbehave. QDBusConnection: session D-Bus connection created before QCoreApplication. Application may misbehave. unnamed app(8305): Communication problem with amarok , it probably crashed. Error message was: org.freedesktop.DBus.Error.NoReply : Message did not receive a reply (timeout by message bus) KCrash: Application 'amarok' crashing... KCrash: Attempting to start /usr/lib/kde4/libexec/drkonqi from kdeinit KCrash: Connect sock_file=/home/user/.kde/socket-PC/kdeinit4__0 I have tried reinstalling, removing and deleting ~/.kde/share/apps/amarok folder with no success -- System Information: Debian Release: stretch/sid APT prefers testing APT policy: (500, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 4.1.0-2-amd64 (SMP w/4 CPU cores) Locale: LANG=es_ES.UTF-8, LC_CTYPE=es_ES.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages amarok depends on: ii amarok-common 2.8.0-2.1 ii amarok-utils 2.8.0-2.1+b2 ii kde-runtime 4:4.14.2-2 ii libaio1 0.3.110-1 ii libavcodec-ffmpeg56 7:2.7.2-1 ii libavformat-ffmpeg56 7:2.7.2-1 ii libavutil-ffmpeg547:2.7.2-1 ii libc6 2.19-19 ii libcurl3-gnutls 7.44.0-1 ii libgcrypt20 1.6.3-2 ii libgdk-pixbuf2.0-02.31.5-1 ii libgl1-mesa-glx [libgl1] 10.6.4-1 ii libglib2.0-0 2.44.1-1.1 ii libgpod4 0.8.3-1.1+b3 ii libkcmutils4 4:4.14.2-5 ii libkdecore5 4:4.14.2-5 ii libkdeui5 4:4.14.2-5 ii libkdewebkit5 4:4.14.2-5 ii libkdnssd44:4.14.2-5 ii libkfile4 4:4.14.2-5 ii libkio5 4:4.14.2-5
Bug#796400: [pkg-go] Bug#796400: Bug#796400: golang-github-jacobsa-ratelimit: Non-determistically FTBFS due to unreliable timing in tests
On Mon, Aug 24, 2015 at 3:32 PM, Aaron Jacobs jaco...@google.com wrote: On Mon, Aug 24, 2015 at 4:37 PM, Michael Stapelberg stapelb...@debian.org Could the timing requirements be relaxed to make it less flaky? Sure. Are you able to modify the test before running it on the relevant system and find a timing that works reliably? lamby, do I have access to the system on which the tests don’t pass? I don’t think giving up is a good idea :). FWIW, just to be clear, it’s not that vendoring is not supported, it’s a conscious decision by Debian to avoid it. Also, AFAICT, other distributions (like Fedora) are following the same model, so I don’t think Debian is different in this regard. If you have trouble getting the software into Debian, you’ll likely have trouble getting it into any of the other big distributions, too. (I understand about vendoring; it's a philosophical difference.) The model we've chosen is distributing binaries from our own apt and yum repos: https://github.com/googlecloudplatform/gcsfuse/blob/master/docs/installing.md I'm totally fine with you finishing this off for the official debian repo if you want to, but I wanted to be clear about the situation from our end. It seems to me that there’s little value in making gcsfuse available in Debian when the officially recommended way of installing it is from a third-party repository. I’ll think about how to proceed; moving in either direction is work, and leaving things as they are means bloating our repository and control files shipped to users for no good reason. -- Best regards, Michael
Bug#796763: slurmd cannot be started under systemd
Hello Remi, HM You are completely right. And I have no real excuse Maybe except that IMHO synchronization of two different configuration files (slurm.conf and slurm(ctl)d.service) might be not a good idea. Thanks for your reply. From my point of view the bug can be closed. Sorry for filing the report. Kind regards Andre
Bug#796108: [PKG-Openstack-devel] Bug#796108: CVE-2015-5694 CVE-2015-5695
On Aug/21, Thomas Goirand wrote: Should I prepare a security upload for Jessie, or do it through the release team oversight? Hi Thomas, CVE-2015-5695 is not that severe, so this should go through a PU request. I'll mark the issue as no-dsa in the tracker. Cheers, --Seb
Processed: your mail
Processing commands for cont...@bugs.debian.org: notfound 714686 llvm-toolchain-snapshot/1:3.8~svn245286-1 Bug #714686 [src:llvm-toolchain-snapshot] llvm-toolchain-snapshot should stay in unstable No longer marked as found in versions llvm-toolchain-snapshot/1:3.8~svn245286-1. tags 714686 -jessie Bug #714686 [src:llvm-toolchain-snapshot] llvm-toolchain-snapshot should stay in unstable Removed tag(s) jessie. thanks Stopping processing here. Please contact me if you need assistance. -- 714686: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=714686 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#796863: libassa3.5-5v5 and libassa-3.5-5v5: error when trying to install together
This is listed in the FTP master's cruft report, so if I'm correct, it shouldn't be necessary to request a removal from unstable. pgpKtU0FUkC7M.pgp Description: PGP signature
Bug#796160: marked as done (python-pykmip: FTBFS: Test certificates expired)
Your message dated Tue, 25 Aug 2015 20:29:53 +0200 with message-id 55dcb421.2050...@debian.org and subject line Last upload fixed this has caused the Debian Bug report #796160, regarding python-pykmip: FTBFS: Test certificates expired 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 ow...@bugs.debian.org immediately.) -- 796160: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=796160 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Source: python-pykmip Version: 0.3.1-1 Severity: serious Justification: fails to build from source User: reproducible-bui...@lists.alioth.debian.org Usertags: ftbfs X-Debbugs-Cc: reproducible-bui...@lists.alioth.debian.org Dear Maintainer, python-pykmip fails to build from source on unstable/amd64 as the test certificates have expired: $ openssl x509 -in kmip/demos/certs/server.crt -text -noout | grep 'Not After' Not After : Aug 19 04:20:33 2015 GMT Build log: [..] === FAILURES === TestKMIPClientIntegration.test_create _ NOTE: Incompatible Exception Representation, displaying natively: _StringException: Traceback (most recent call last): File /tmp/buildd/python-pykmip-0.3.1/kmip/tests/services/test_kmip_client.py, line 122, in setUp raise e SSLError: [SSL: CERTIFICATE_VERIFY_FAILED] certificate verify failed (_ssl.c:590) - Captured stdout call - 2015-08-19 02:36:41,281 - kmip.core.config_helper - DEBUG - Using config file at /tmp/buildd/python-pykmip-0.3.1/kmip/kmipconfig.ini 2015-08-19 02:36:41,281 - kmip.core.config_helper - DEBUG - Using given value '127.0.0.1' for host 2015-08-19 02:36:41,281 - kmip.core.config_helper - DEBUG - Using given value '9090' for port 2015-08-19 02:36:41,282 - kmip.core.config_helper - DEBUG - Using given value '/tmp/buildd/python-pykmip-0.3.1/kmip/demos/certs/server.key' for keyfile 2015-08-19 02:36:41,282 - kmip.core.config_helper - DEBUG - Using given value '/tmp/buildd/python-pykmip-0.3.1/kmip/demos/certs/server.crt' for certfile 2015-08-19 02:36:41,282 - kmip.core.config_helper - DEBUG - Using given value 'CERT_NONE' for cert_reqs 2015-08-19 02:36:41,282 - kmip.core.config_helper - DEBUG - Using given value 'PROTOCOL_SSLv23' for ssl_version 2015-08-19 02:36:41,282 - kmip.core.config_helper - DEBUG - Using given value 'None' for ca_certs 2015-08-19 02:36:41,282 - kmip.core.config_helper - DEBUG - Using given value 'True' for do_handshake_on_connect 2015-08-19 02:36:41,282 - kmip.core.config_helper - DEBUG - Using given value 'True' for suppress_ragged_eofs 2015-08-19 02:36:41,282 - __main__ - INFO - Starting the KMIP server 2015-08-19 02:36:42,167 - kmip.core.config_helper - DEBUG - Using config file at /tmp/buildd/python-pykmip-0.3.1/kmip/kmipconfig.ini 2015-08-19 02:36:42,168 - kmip.core.config_helper - DEBUG - Using value '127.0.0.1' from configuration file /tmp/buildd/python-pykmip-0.3.1/kmip/kmipconfig.ini for host 2015-08-19 02:36:42,169 - kmip.core.config_helper - DEBUG - Using given value '9090' for port 2015-08-19 02:36:42,169 - kmip.core.config_helper - DEBUG - Using value 'None' from configuration file /tmp/buildd/python-pykmip-0.3.1/kmip/kmipconfig.ini for keyfile 2015-08-19 02:36:42,169 - kmip.core.config_helper - DEBUG - Using value 'None' from configuration file /tmp/buildd/python-pykmip-0.3.1/kmip/kmipconfig.ini for certfile 2015-08-19 02:36:42,170 - kmip.core.config_helper - DEBUG - Using value 'CERT_REQUIRED' from configuration file /tmp/buildd/python-pykmip-0.3.1/kmip/kmipconfig.ini for cert_reqs 2015-08-19 02:36:42,170 - kmip.core.config_helper - DEBUG - Using value 'PROTOCOL_SSLv23' from configuration file /tmp/buildd/python-pykmip-0.3.1/kmip/kmipconfig.ini for ssl_version 2015-08-19 02:36:42,170 - kmip.core.config_helper - DEBUG - Using given value '/tmp/buildd/python-pykmip-0.3.1/kmip/demos/certs/server.crt' for ca_certs 2015-08-19 02:36:42,171 - kmip.core.config_helper - DEBUG - Using value 'True' from configuration file /tmp/buildd/python-pykmip-0.3.1/kmip/kmipconfig.ini for do_handshake_on_connect 2015-08-19 02:36:42,171 - kmip.core.config_helper - DEBUG - Using value 'True' from configuration file /tmp/buildd/python-pykmip-0.3.1/kmip/kmipconfig.ini for suppress_ragged_eofs 2015-08-19 02:36:42,171 - kmip.core.config_helper - DEBUG - Using value 'None' from configuration file
Bug#787471: marked as done (how-can-i-help: does not start if ~/.cache/how-can-i-help/how-can-i-help.json.gz doesn't exist)
Your message dated Tue, 25 Aug 2015 18:32:05 + with message-id e1zuj0v-s3...@franck.debian.org and subject line Bug#787471: fixed in how-can-i-help 10+deb8u1 has caused the Debian Bug report #787471, regarding how-can-i-help: does not start if ~/.cache/how-can-i-help/how-can-i-help.json.gz doesn't exist 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 ow...@bugs.debian.org immediately.) -- 787471: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=787471 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: how-can-i-help Version: 10 Severity: grave Justification: renders package unusable Dear Maintainer, People running how-can-i-help for the first time are greeted with the following: /usr/bin/how-can-i-help:135:in `open': No such file or directory @ rb_sysopen - /home/steve/.cache/how-can-i-help/how-can-i-help.json.gz (Errno::ENOENT) from /usr/bin/how-can-i-help:135:in `main' Given the target audience it's rather unfortunate :-(. Regards, Stephen -- System Information: Debian Release: stretch/sid APT prefers testing APT policy: (500, 'testing'), (500, 'stable'), (200, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.16.0-4-amd64 (SMP w/8 CPU cores) Locale: LANG=en_GB.utf8, LC_CTYPE=en_GB.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages how-can-i-help depends on: ii ruby 1:2.1.5+z ii ruby-debian 0.3.9 ii ruby-json1.8.2-1 how-can-i-help recommends no packages. how-can-i-help suggests no packages. -- no debconf information ---End Message--- ---BeginMessage--- Source: how-can-i-help Source-Version: 10+deb8u1 We believe that the bug you reported is fixed in the latest version of how-can-i-help, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 787...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Tomasz Nitecki t...@tnnn.pl (supplier of updated how-can-i-help package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Tue, 18 Aug 2015 13:33:32 +0200 Source: how-can-i-help Binary: how-can-i-help Architecture: source all Version: 10+deb8u1 Distribution: jessie Urgency: medium Maintainer: Tomasz Nitecki t...@tnnn.pl Changed-By: Tomasz Nitecki t...@tnnn.pl Description: how-can-i-help - show opportunities for contributing to Debian Closes: 787471 Changes: how-can-i-help (10+deb8u1) jessie; urgency=medium . * Change hcih data source from http to https. Since the http is not supported by UDD anymore, older hcih versions won't be able to work. (Closes: #787471) Patch from Stephen Kitt sk...@debian.org * Added gbp configuration pointing to jessie branch. Checksums-Sha1: 2812afd757307e80e9b7900aa6187222b08087c1 1665 how-can-i-help_10+deb8u1.dsc c27e01f95e1c5e4c838dd65cf4d2d3b8903396d7 9236 how-can-i-help_10+deb8u1.tar.xz 760301ee1c9a6a3e9ccc134a93baab177cf51936 10066 how-can-i-help_10+deb8u1_all.deb Checksums-Sha256: 4f1d784708f23dc707984fb7c6bbdcee1239fc7959a9494debba0d2baa056d3b 1665 how-can-i-help_10+deb8u1.dsc 8eef5da3e591548af0d54934ec7f40f117837cf15d9bb30230d7fcedbc255eb3 9236 how-can-i-help_10+deb8u1.tar.xz c59f98039423d387df1b880b11e1c263ef5cdc469f567f84fe140c0b63de3bd4 10066 how-can-i-help_10+deb8u1_all.deb Files: 65350caf99fa7baa2846702589ebf221 1665 devel optional how-can-i-help_10+deb8u1.dsc dc5d3d8e56da325ea5a6fb23321fcc17 9236 devel optional how-can-i-help_10+deb8u1.tar.xz 7eb55601a469f55195f1014b59c2150f 10066 devel optional how-can-i-help_10+deb8u1_all.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1 iQIVAwUBVdd5XzkUtTL0376ZAQovuQ/+OrnyJ5haWy0DmYfXn+rP694H1wTXx147 ZLlGAcB4PAgARuQriRH7r0AZ/5B1kTBcYW3HV5Q/2PDGK7w506g39gTTqZzTmIwh p9uXSITLpCwLzBb0SE2nlN41GzvILg+en+EQnqV55bgcVxuO9WC3WRq0gvyGbSsD WB0OaYB6W/dcQ8tZxtNw0zjnkFnqdcjKf9pWmKDSf7AL4vd0YNfYzdQU7gQ2m0jj BWZ9bj+0dCBMVplfTy8FUGBk/h4beD+92CpMqAuuEMao/nzd0SiqJSraIeWt9e8p LIdvMnguoBCR5vZ0how27embgdQGWcQiGhO1g3Ci/qgYKZEoy3aeszKSklnegYoK fHpSPLhRwL4wQNrd7Kko4y3ElB8orpxHllohgmNNKmehXH1ZO3zifa+j02s+l96R pCA4vFQCPtL564vDzum89HX7JNpjcyKb0ASiSO2B8WudpvvPrfYxsqFcusoIpsFU
Bug#790984: marked as done (blitz++: library transition may be needed when GCC 5 is the default)
Your message dated Tue, 25 Aug 2015 19:00:10 + with message-id e1zujs6-0006ez...@franck.debian.org and subject line Bug#790984: fixed in blitz++ 1:0.10-3.3 has caused the Debian Bug report #790984, regarding blitz++: library transition may be needed when GCC 5 is the default 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 ow...@bugs.debian.org immediately.) -- 790984: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=790984 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: src:blitz++ Version: 0.10-3.2 Severity: important Tags: sid stretch User: debian-...@lists.debian.org Usertags: libstdc++-cxx11 Background [1]: libstdc++6 introduces a new ABI to conform to the C++11 standard, but keeps the old ABI to not break existing binaries. Packages which are built with g++-5 from experimental (not the one from testing/unstable) are using the new ABI. Libraries built from this source package export some of the new __cxx11 or B5cxx11 symbols, and dropping other symbols. If these symbols are part of the API of the library, then this rebuild with g++-5 will trigger a transition for the library. What is needed: - Rebuild the library using g++/g++-5 from experimental. Note that most likely all C++ libraries within the build dependencies need a rebuild too. You can find the log for a rebuild in https://people.debian.org/~doko/logs/gcc5-20150701/ Search for BEGIN GCC CXX11 in the log. - Decide if the symbols matching __cxx11 or B5cxx11 are part of the library API, and are used by the reverse dependencies of the library. - If there are no symbols matching __cxx11 or B5cxx11 in the symbols forming the library API, you should close this issue with a short explanation. - If there are no reverse dependencies, it should be the package maintainers decision if a transition is needed. However this might break software which is not in the Debian archive, and built against these packages. - If a library transition is needed, please prepare for the change. Rename the library package, append v5 to the name of the package (e.g. libfoo2 - libfoo2v5). Such a change can be avoided, if you have a soversion bump and you upload this version instead of the renamed package. Prepare a patch and attach it to this issue (mark this issue with patch), so that it is possible to NMU such a package. We'll probably have more than hundred transitions triggered. Then reassign the issue to release.debian.org and properly tag it as a transition issue, by sending an email to cont...@bugs.debian.org: user release.debian@packages.debian.org usertag this issue + transition block this issue by 790756 reassign this issue release.debian.org - If unsure if a transition is needed, please tag the issue with help to ask for feedback from other Debian developers. The libstdc++6 transition will be a large one, and it will come with a lot of pain. Please help it by preparing the follow-up transitions. [1] https://wiki.debian.org/GCC5#libstdc.2B-.2B-_ABI_transition ---End Message--- ---BeginMessage--- Source: blitz++ Source-Version: 1:0.10-3.3 We believe that the bug you reported is fixed in the latest version of blitz++, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 790...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Simon McVittie s...@debian.org (supplier of updated blitz++ package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Sun, 23 Aug 2015 14:46:54 +0100 Source: blitz++ Binary: libblitz0v5 libblitz0-dev libblitz-doc Architecture: all amd64 source Version: 1:0.10-3.3 Distribution: unstable Urgency: medium Maintainer: Debian Science Team debian-science-maintain...@lists.alioth.debian.org Changed-By: Simon McVittie s...@debian.org Closes: 790984 Description: libblitz0-dev - C++ template class library for scientific computing libblitz0v5 - C++ template class library for scientific computing libblitz-doc - C++ template class library for scientific computing Changes: blitz++ (1:0.10-3.3) unstable; urgency=medium . * Non-maintainer upload. * Rename library to
Bug#782750: make-dfsg: FTBFS: features/archives test fails
On 2015-08-22 11:51, Aurelien Jarno wrote: control: tag -1 + patch On 2015-08-03 23:04, Aurelien Jarno wrote: On 2015-04-17 11:28, Edmund Grimley Evans wrote: Source: make-dfsg Version: 4.0-8.1 When building with binutils 2.25-6, the version currently in unstable, it fails to build. The output is: features/archives ... FAILED (3/10 passed) It's clear what's happening here. This entry in the changelog for binutils (2.25-6) explains it: * Configure with --enable-deterministic-archives. Closes: #774429. Files are added to archives with a zero timestamp so make then adds them again, unexpectedly. However, I'm not sure how you'll want to fix this. Weaken the test somehow? I have just noted that ar has the 'U' option to disable deterministic archives. This would allow to still test this part of make. Unfortunately ar doesn't take arguments, but rather a list of modifiers which need to be in the same argument, so we can't use an alias to force this. We could also have done that using a shell function, but POSIX shells do not provide a way to export shell functions. We can still do it by using a wrapper called ar and changing PATH to point first to the directory containing the wrapper. That's a bit more ugly though. You'll find below a patch using this approach. I would like to see this longstanding issue fixed soon, so I offer to do an NMU in a few days, unless someone opposes. I have just done an NMU to fix this longstanding issue. Please find the diff attached. Aurelien -- Aurelien Jarno GPG: 4096R/1DDD8C9B aurel...@aurel32.net http://www.aurel32.net diff -Nru make-dfsg-4.0/debian/changelog make-dfsg-4.0/debian/changelog --- make-dfsg-4.0/debian/changelog 2015-01-17 19:30:55.0 +0100 +++ make-dfsg-4.0/debian/changelog 2015-08-25 20:05:51.0 +0200 @@ -1,3 +1,11 @@ +make-dfsg (4.0-8.2) unstable; urgency=medium + + * Non-maintainer upload. + * Use a wrapper in the testsuite for ar to force it to not run in +deterministic mode (Closes: #782750). + + -- Aurelien Jarno aure...@debian.org Tue, 25 Aug 2015 20:05:48 +0200 + make-dfsg (4.0-8.1) unstable; urgency=medium * Non-maintainer upload. diff -Nru make-dfsg-4.0/debian/rules make-dfsg-4.0/debian/rules --- make-dfsg-4.0/debian/rules 2014-06-14 01:13:45.0 +0200 +++ make-dfsg-4.0/debian/rules 2015-08-22 11:24:45.0 +0200 @@ -45,10 +45,10 @@ override_dh_auto_test: ifneq (,$(filter make-guile, $(shell dh_listpackages))) - dh_auto_test --parallel -B$(BUILDDIR_GUILE) + PATH=$(CURDIR)/debian/wrappers:$$PATH dh_auto_test --parallel -B$(BUILDDIR_GUILE) endif ifneq (,$(filter make, $(shell dh_listpackages))) - dh_auto_test --parallel -B$(BUILDDIR_NORMAL) + PATH=$(CURDIR)/debian/wrappers:$$PATH dh_auto_test --parallel -B$(BUILDDIR_NORMAL) endif override_dh_auto_install: diff -Nru make-dfsg-4.0/debian/wrappers/ar make-dfsg-4.0/debian/wrappers/ar --- make-dfsg-4.0/debian/wrappers/ar 1970-01-01 01:00:00.0 +0100 +++ make-dfsg-4.0/debian/wrappers/ar 2015-08-22 11:27:38.0 +0200 @@ -0,0 +1,6 @@ +#!/bin/sh + +# Force ar to not run in deterministic mode, as the testsuite relies +# on UID, GID, timestamp and file mode values to be correctly stored. + +exec /usr/bin/ar U$@ signature.asc Description: Digital signature
Processed: Re: Bug#796715: coinor-osi: working diff
Processing commands for cont...@bugs.debian.org: tag 796715 + pending Bug #796715 [src:coinor-osi] coinor-osi: library transition needed with GCC 5 as default Added tag(s) pending. thanks Stopping processing here. Please contact me if you need assistance. -- 796715: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=796715 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#796715: coinor-osi: working diff
tag 796715 + pending thanks Hi, On Tue, Aug 25, 2015 at 12:05:05PM -0600, Miles Lubin wrote: On Tue, Aug 25, 2015 at 3:46 AM, Rene Engelhard r...@debian.org wrote: Either you can upload it yourself or I can do a team upload, whatever you prefer. Thanks for figuring this out, I don't currently have the time to work through the transition. Team upload would be appreciated. Ok. Done. (The Third version). Regards, Rene
Bug#796898: marked as done (python-pykmip: Remove Depends and Build-Depends on python3-enum34)
Your message dated Tue, 25 Aug 2015 18:20:54 + with message-id e1zuiq6-0006zp...@franck.debian.org and subject line Bug#796898: fixed in python-pykmip 0.3.1-2 has caused the Debian Bug report #796898, regarding python-pykmip: Remove Depends and Build-Depends on python3-enum34 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 ow...@bugs.debian.org immediately.) -- 796898: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=796898 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Source: python-pykmip Severity: serious -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Dear Maintainer, python-pykmip currently includes Depends and Build-Depends on python3-enum34. This package is incompatible with Python 3.5 and unnecessary for Python 3.4 since the stdlib already contains the package 'enum' which is the importable name in both cases. python3-enum34 has been removed from the archive for Stretch. Please remove these dependencies. - -- System Information: Debian Release: stretch/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: amd64 (x86_64) Kernel: Linux 4.1.0-2-amd64 (SMP w/1 CPU core) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) -BEGIN PGP SIGNATURE- Version: GnuPG v1 iQIcBAEBCAAGBQJV3IcfAAoJEBJutWOnSwa/410QAKa0jrDH00Ai6zy8cZxTDBuh qwj8uitaWj0TbksidBin17O7Fbu+5rVyCVNZSCc4gutv+WlOMZRoXWWyUuOeonZX HmQsMGTkBFCdVvWehiENjtlTcR1olTZZtDBL6EHFr54r5r+qNqPBaLx6cgf6c+xP 8C0jSegRT/PHbC5qNfghJ/7B2DoknQLG0A9MBp9NYS8RMjUXQ2ChomGw0TigQgt1 RV+AdNnviAilJZ+9rOlUn9LyUjctl1mqaYluOkD/21KOGlK/861H1fiaNoAZWnGx ICkYwLARAj4MWPUWOdIMnKr/3cJzsfiqrd481JI3pmNGI8ubHAndJoBzFA2M4j9D s7AkgHE4nSaTW/rRvaI5v2L3mPcPq3xbAuB6rcpUqLr3HxX/aKKV9GOKH5+tem18 qQYhx7LtiF7OuWfq5GlpoWhI6FIygGI8nLG3gO1QauxLJpVNaLiHS41AilXY1SRz uBcCj/+DI+dFEn5UVwn4F4meGR+BduFknNidXh9TcZQ7VpHwef4N7JqsWIQBZar6 yolb/ZQbYZw0rB+ixhdH9HY+2l88aY+S91aNkPbsv56ANydiTwSog+xppdrzKxvC 9IYyGQcRM2CB4MgGScDxQtnKYlXhgdEonxcQ6R9/hLj/BEgxl96N5dlgr8SyRqco dW/lHbxPQvY0IlyR7sEH =FdaX -END PGP SIGNATURE- ---End Message--- ---BeginMessage--- Source: python-pykmip Source-Version: 0.3.1-2 We believe that the bug you reported is fixed in the latest version of python-pykmip, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 796...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Thomas Goirand z...@debian.org (supplier of updated python-pykmip package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Tue, 25 Aug 2015 17:57:55 + Source: python-pykmip Binary: python-pykmip python3-pykmip Architecture: source all Version: 0.3.1-2 Distribution: unstable Urgency: medium Maintainer: PKG OpenStack openstack-de...@lists.alioth.debian.org Changed-By: Thomas Goirand z...@debian.org Description: python-pykmip - implementation of the Key Management Interoperability Protocol - python3-pykmip - KMIP v1.1 library - Python 3.x Closes: 796898 Changes: python-pykmip (0.3.1-2) unstable; urgency=medium . * Removed (build-)dependency on python3-enum34 (Closes: #796898). * Allow unit tests to fail. * Using github tag instead of broken PyPi URL in watch file. Checksums-Sha1: 5e73ad312fb0b00fd4221426cf82137c3dc33c2d 2489 python-pykmip_0.3.1-2.dsc 43f4712930528aad4806cff7115a8c05c7502d3d 2720 python-pykmip_0.3.1-2.debian.tar.xz 371e9d74a03893f6144bbee6ef5ce09c6fe80e63 54088 python-pykmip_0.3.1-2_all.deb fd8d709a5685dbed811e3bf2d7bb5d352e72e148 51068 python3-pykmip_0.3.1-2_all.deb Checksums-Sha256: 2e4cf7b1541255c3991606aa577e5e6733fecf51f9bfed2701886b512c06155b 2489 python-pykmip_0.3.1-2.dsc 43e34e1c72e8257cfd307260ae13fe8950799ac850870feceb3f1ed2fac39015 2720 python-pykmip_0.3.1-2.debian.tar.xz 740efa0fc0c20773df259e4a3fae9733f023555d993aac1d2d090cbb7c6a0c49 54088 python-pykmip_0.3.1-2_all.deb 1b26702391d9ebd25693eaa8482f6494f41defd775e7670f83472b693f7c7828 51068 python3-pykmip_0.3.1-2_all.deb Files: 69c7a59b231001f95c0b8ac02777892e 2489 python optional python-pykmip_0.3.1-2.dsc 3fcb608496297b2a33e285a05ff0d9f4 2720 python optional python-pykmip_0.3.1-2.debian.tar.xz
Bug#796460: marked as done (python-glanceclient: FTBFS: AttributeError: assert_called_once)
Your message dated Tue, 25 Aug 2015 18:34:35 +
with message-id e1zuj3l-0001wz...@franck.debian.org
and subject line Bug#796460: fixed in python-glanceclient 1:0.17.1-2
has caused the Debian Bug report #796460,
regarding python-glanceclient: FTBFS: AttributeError: assert_called_once
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 ow...@bugs.debian.org
immediately.)
--
796460: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=796460
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
---BeginMessage---
Source: python-glanceclient
Version: 1:0.17.1-1
Severity: serious
Justification: fails to build from source
Tags: sid stretch
User: reproducible-bui...@lists.alioth.debian.org
Usertags: ftbfs
X-Debbugs-CC: reproducible-bui...@lists.alioth.debian.org
Dear Maintainer,
The package fails to build:
==
FAIL: tests.test_ssl.TestVerifiedHTTPSConnection.test_ssl_cert_cname_wildcard
tests.test_ssl.TestVerifiedHTTPSConnection.test_ssl_cert_cname_wildcard
--
_StringException: Traceback (most recent call last):
File tests/test_ssl.py, line 280, in test_ssl_cert_cname_wildcard
self.fail('Unexpected exception.')
File /usr/lib/python2.7/unittest/case.py, line 410, in fail
raise self.failureException(msg)
AssertionError: Unexpected exception.
==
FAIL:
tests.test_ssl.TestVerifiedHTTPSConnection.test_ssl_cert_subject_alt_name_wildcard
tests.test_ssl.TestVerifiedHTTPSConnection.test_ssl_cert_subject_alt_name_wildcard
--
_StringException: Traceback (most recent call last):
File tests/test_ssl.py, line 316, in test_ssl_cert_subject_alt_name_wildcard
self.fail('Unexpected exception.')
File /usr/lib/python2.7/unittest/case.py, line 410, in fail
raise self.failureException(msg)
AssertionError: Unexpected exception.
==
FAIL: tests.v2.test_shell_v2.ShellV2Test.test_do_md_resource_type_list
tests.v2.test_shell_v2.ShellV2Test.test_do_md_resource_type_list
--
_StringException: Traceback (most recent call last):
File tests/v2/test_shell_v2.py, line 811, in test_do_md_resource_type_list
mocked_list.assert_called_once()
File /usr/lib/python2.7/dist-packages/mock/mock.py, line 721, in __getattr__
raise AttributeError(name)
AttributeError: assert_called_once
==
FAIL: process-returncode
process-returncode
--
_StringException: returncode 1
--
Ran 363 tests in 3.622s
FAILED (failures=4)
Full build log:
https://reproducible.debian.net/rb-pkg/unstable/amd64/python-glanceclient.html
-- System Information:
Debian Release: stretch/sid
APT prefers unstable
APT policy: (500, 'unstable')
Architecture: amd64 (x86_64)
Kernel: Linux 3.19.0-23-generic (SMP w/8 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
---End Message---
---BeginMessage---
Source: python-glanceclient
Source-Version: 1:0.17.1-2
We believe that the bug you reported is fixed in the latest version of
python-glanceclient, which is due to be installed in the Debian FTP archive.
A summary of the changes between this version and the previous one is
attached.
Thank you for reporting the bug, which will now be closed. If you
have further comments please address them to 796...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Thomas Goirand z...@debian.org (supplier of updated python-glanceclient
package)
(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Format: 1.8
Date: Tue, 25 Aug 2015 18:21:20 +
Source: python-glanceclient
Binary: python-glanceclient
Architecture: source all
Version: 1:0.17.1-2
Distribution: unstable
Urgency: medium
Maintainer: PKG OpenStack openstack-de...@lists.alioth.debian.org
Changed-By: Thomas Goirand z...@debian.org
Description:
python-glanceclient - Client library for Openstack glance
Bug#796463: marked as done (python-muranoclient: FTBFS: AttributeError: assert_called_once)
Your message dated Tue, 25 Aug 2015 18:34:42 + with message-id e1zuj3s-0001gv...@franck.debian.org and subject line Bug#796463: fixed in python-muranoclient 0.5.9-2 has caused the Debian Bug report #796463, regarding python-muranoclient: FTBFS: AttributeError: assert_called_once 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 ow...@bugs.debian.org immediately.) -- 796463: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=796463 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Source: python-muranoclient Version: 0.5.9-1 Severity: serious Justification: fails to build from source Tags: sid User: reproducible-bui...@lists.alioth.debian.org Usertags: ftbfs X-Debbugs-CC: reproducible-bui...@lists.alioth.debian.org Dear Maintainer, The package fails to build: == FAIL: muranoclient.tests.test_shell.ShellPackagesOperations.test_deployments_show muranoclient.tests.test_shell.ShellPackagesOperations.test_deployments_show -- _StringException: Traceback (most recent call last): File /usr/lib/python2.7/dist-packages/mock/mock.py, line 1305, in patched return func(*args, **keywargs) File muranoclient/tests/test_shell.py, line 301, in test_deployments_show self.client.deployments.list.assert_called_once() File /usr/lib/python2.7/dist-packages/mock/mock.py, line 721, in __getattr__ raise AttributeError(name) AttributeError: assert_called_once Traceback (most recent call last): _StringException: Empty attachments: stderr stdout Traceback (most recent call last): File /usr/lib/python2.7/dist-packages/mock/mock.py, line 1305, in patched return func(*args, **keywargs) File muranoclient/tests/test_shell.py, line 301, in test_deployments_show self.client.deployments.list.assert_called_once() File /usr/lib/python2.7/dist-packages/mock/mock.py, line 721, in __getattr__ raise AttributeError(name) AttributeError: assert_called_once Traceback (most recent call last): _StringException: Empty attachments: stderr stdout Traceback (most recent call last): File /usr/lib/python2.7/dist-packages/mock/mock.py, line 1305, in patched return func(*args, **keywargs) File muranoclient/tests/test_shell.py, line 301, in test_deployments_show self.client.deployments.list.assert_called_once() File /usr/lib/python2.7/dist-packages/mock/mock.py, line 721, in __getattr__ raise AttributeError(name) AttributeError: assert_called_once .. -- Ran 130 tests in 1.455s FAILED (failures=9) Full build log: https://reproducible.debian.net/rb-pkg/unstable/amd64/python-muranoclient.html -- System Information: Debian Release: stretch/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: amd64 (x86_64) Kernel: Linux 3.19.0-23-generic (SMP w/8 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) ---End Message--- ---BeginMessage--- Source: python-muranoclient Source-Version: 0.5.9-2 We believe that the bug you reported is fixed in the latest version of python-muranoclient, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 796...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Thomas Goirand z...@debian.org (supplier of updated python-muranoclient package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Tue, 25 Aug 2015 18:10:28 + Source: python-muranoclient Binary: python-muranoclient python-muranoclient-doc Architecture: source all Version: 0.5.9-2 Distribution: unstable Urgency: medium Maintainer: PKG OpenStack openstack-de...@lists.alioth.debian.org Changed-By: Thomas Goirand z...@debian.org Description: python-muranoclient - cloud-ready application catalog - Python 2.x client module python-muranoclient-doc - cloud-ready application catalog - client doc Closes: 796463 Changes: python-muranoclient (0.5.9-2) unstable; urgency=medium . * Disable unit tests failing with mock = 1.3 (Closes: #796463).
Bug#796803: marked as done (dh-lua: Missing Build-Depends on txt2man)
Your message dated Tue, 25 Aug 2015 09:19:14 +
with message-id e1zuanu-gv...@franck.debian.org
and subject line Bug#796803: fixed in dh-lua 23
has caused the Debian Bug report #796803,
regarding dh-lua: Missing Build-Depends on txt2man
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 ow...@bugs.debian.org
immediately.)
--
796803: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=796803
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
---BeginMessage---
Source: dh-lua
Version: 22
Severity: serious
Justification: fails to build from source
User: reproducible-bui...@lists.alioth.debian.org
Usertags: ftbfs
X-Debbugs-Cc: reproducible-bui...@lists.alioth.debian.org
Dear Maintainer,
dh-lua fails to build from source in unstable/amd64 due
to missing Build-Depends on txt2man:
[..]
dh_auto_build
make -j1
make[1]: Entering directory '/tmp/buildd/dh-lua-22'
txt2man -d `dpkg-parsechangelog -S date`\
-v -r lua-any -t lua-any 1 \
man/lua-any.1.txt man/lua-any.1
/bin/sh: 1: txt2man: not found
Makefile:41: recipe for target 'man/lua-any.1' failed
make[1]: *** [man/lua-any.1] Error 127
make[1]: Leaving directory '/tmp/buildd/dh-lua-22'
dh_auto_build: make -j1 returned exit code 2
debian/rules:4: 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/dh-lua_22.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: Sun Aug 23 21:31:09 GMT+12 2015
I: pbuilder-time-stamp: 1440408669
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 pbuilder-ma...@lists.alioth.debian.org
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.0.0), markdown, perl
dpkg-deb: building package 'pbuilder-satisfydepends-dummy' in
'/tmp/satisfydepends-aptitude/pbuilder-satisfydepends-dummy.deb'.
Selecting previously unselected package pbuilder-satisfydepends-dummy.
(Reading database ... 20247 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 markdown; however:
Package markdown is not installed.
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:
markdown{a}
0 packages upgraded, 1 newly installed, 0 to remove and 0 not upgraded.
Need to get 19.0 kB of archives. After unpacking 98.3 kB will be used.
Writing extended state information...
Get: 1 http://ftp.de.debian.org/debian/ unstable/main markdown all 1.0.1-7
[19.0 kB]
Fetched 19.0 kB in 0s (575 kB/s)
debconf: delaying package configuration, since apt-utils is not installed
Selecting previously unselected package markdown.
(Reading database ...
(Reading database ... 5%
(Reading database ... 10%
(Reading database ... 15%
(Reading database ... 20%
(Reading database ... 25%
(Reading database ... 30%
(Reading database ... 35%
(Reading database ... 40%
(Reading database ... 45%
(Reading database ... 50%
(Reading database ... 55%
(Reading database ... 60%
(Reading database ... 65%
(Reading database ... 70%
(Reading database ... 75%
(Reading database ... 80%
(Reading database ... 85%
(Reading database ... 90%
(Reading database ... 95%
(Reading database ... 100%
(Reading database ... 20247 files and directories currently installed.)
Preparing to
Bug#796715: coinor-osi: working diff
Hi again,
I looked at this one given it's a r-dep of coinmp and thus other coin-* stuff,
which in turn is one of LibreOffice Calc :) and prepared the following patch.
Unfortunately, this then fails its tests.
(I guess that's why you tagged the bug help? There's no explanation, so..)
[...]
No idea what that means, maybe it needs other COIN stuff also be rebuilt
first?
Indeed, I forgot to upgrade the already NMUed coinutils. With that it works.
So here's a new patch with the build-dependency bumped.
Either you can upload it yourself or I can do a team upload, whatever you
prefer.
Regards,
Rene
diff -Nru coinor-osi-0.106.9/debian/changelog coinor-osi-0.106.9/debian/changelog
--- coinor-osi-0.106.9/debian/changelog 2014-09-04 13:54:26.0 +0200
+++ coinor-osi-0.106.9/debian/changelog 2015-08-25 11:36:43.0 +0200
@@ -1,3 +1,11 @@
+coinor-osi (0.106.9-2) unstable; urgency=medium
+
+ * libstdc++6 transtion: rename coinor-libosi1 to coinor-libosi1v5
+(closes: #796715)
+ * bump coinor-libcoinutils-dev build-dep
+
+ -- Rene Engelhard r...@debian.org Tue, 25 Aug 2015 11:36:35 +0200
+
coinor-osi (0.106.9-1) unstable; urgency=low
* New upstream version.
diff -Nru coinor-osi-0.106.9/debian/coinor-libosi1.install coinor-osi-0.106.9/debian/coinor-libosi1.install
--- coinor-osi-0.106.9/debian/coinor-libosi1.install 2013-09-18 09:45:42.0 +0200
+++ coinor-osi-0.106.9/debian/coinor-libosi1.install 1970-01-01 01:00:00.0 +0100
@@ -1 +0,0 @@
-debian/tmp/usr/lib/*/lib*.so.*
diff -Nru coinor-osi-0.106.9/debian/coinor-libosi1.lintian-overrides coinor-osi-0.106.9/debian/coinor-libosi1.lintian-overrides
--- coinor-osi-0.106.9/debian/coinor-libosi1.lintian-overrides 2013-09-18 09:45:42.0 +0200
+++ coinor-osi-0.106.9/debian/coinor-libosi1.lintian-overrides 1970-01-01 01:00:00.0 +0100
@@ -1 +0,0 @@
-coinor-libosi1: package-name-doesnt-match-sonames libOsi1 libOsiCommonTests1
diff -Nru coinor-osi-0.106.9/debian/coinor-libosi1v5.install coinor-osi-0.106.9/debian/coinor-libosi1v5.install
--- coinor-osi-0.106.9/debian/coinor-libosi1v5.install 1970-01-01 01:00:00.0 +0100
+++ coinor-osi-0.106.9/debian/coinor-libosi1v5.install 2013-09-18 09:45:42.0 +0200
@@ -0,0 +1 @@
+debian/tmp/usr/lib/*/lib*.so.*
diff -Nru coinor-osi-0.106.9/debian/coinor-libosi1v5.lintian-overrides coinor-osi-0.106.9/debian/coinor-libosi1v5.lintian-overrides
--- coinor-osi-0.106.9/debian/coinor-libosi1v5.lintian-overrides 1970-01-01 01:00:00.0 +0100
+++ coinor-osi-0.106.9/debian/coinor-libosi1v5.lintian-overrides 2013-09-18 09:45:42.0 +0200
@@ -0,0 +1 @@
+coinor-libosi1: package-name-doesnt-match-sonames libOsi1 libOsiCommonTests1
diff -Nru coinor-osi-0.106.9/debian/control coinor-osi-0.106.9/debian/control
--- coinor-osi-0.106.9/debian/control 2014-09-04 13:54:26.0 +0200
+++ coinor-osi-0.106.9/debian/control 2015-08-25 11:36:07.0 +0200
@@ -4,15 +4,16 @@
Maintainer: Debian Science Team debian-science-maintain...@lists.alioth.debian.org
Uploaders: Miles Lubin miles.lu...@gmail.com
Build-Depends: debhelper (= 9), doxygen, graphviz,
- coinor-libcoinutils-dev (= 2.9.15), pkg-config, zlib1g-dev, libbz2-dev, autotools-dev
+ coinor-libcoinutils-dev (= 2.9.15-3.1), pkg-config, zlib1g-dev, libbz2-dev, autotools-dev
Standards-Version: 3.9.5
Vcs-Git: git://anonscm.debian.org/debian-science/packages/coinor-osi.git
Vcs-Browser: http://anonscm.debian.org/gitweb/?p=debian-science/packages/coinor-osi.git
Homepage: https://projects.coin-or.org/Osi
-Package: coinor-libosi1
+Package: coinor-libosi1v5
Architecture: any
Depends: ${shlibs:Depends}, ${misc:Depends}
+Conflicts: coinor-libosi1
Description: COIN-OR Open Solver Interface
Osi (Open Solver Interface) provides an abstract C++ base class to a generic
linear programming (LP) solver, along with derived classes for specific
@@ -29,7 +30,7 @@
Package: coinor-libosi-dev
Section: libdevel
Architecture: any
-Depends: ${shlibs:Depends}, ${misc:Depends}, coinor-libosi1 (= ${binary:Version})
+Depends: ${shlibs:Depends}, ${misc:Depends}, coinor-libosi1v5 (= ${binary:Version})
Description: COIN-OR Open Solver Interface (developer files)
Osi (Open Solver Interface) provides an abstract C++ base class to a generic
linear programming (LP) solver, along with derived classes for specific
@@ -60,7 +61,7 @@
Package: coinor-libosi1-dbg
Section: debug
Architecture: any
-Depends: ${shlibs:Depends}, ${misc:Depends}, coinor-libosi1 (= ${binary:Version})
+Depends: ${shlibs:Depends}, ${misc:Depends}, coinor-libosi1v5 (= ${binary:Version})
Description: COIN-OR Open Solver Interface (debug symbols)
Osi (Open Solver Interface) provides an abstract C++ base class to a generic
linear programming (LP) solver, along with derived classes for specific
Bug#795850: marked as done (pdfgrep: FTBFS: pdfgrep.cc:429: undefined reference to `poppler::version_string[abi:cxx11]()')
Your message dated Tue, 25 Aug 2015 12:02:35 +0200 with message-id 87zj1fd6tg@anonymous.siccegge.de and subject line Not a bug in pdfgrep has caused the Debian Bug report #795850, regarding pdfgrep: FTBFS: pdfgrep.cc:429: undefined reference to `poppler::version_string[abi:cxx11]()' 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 ow...@bugs.debian.org immediately.) -- 795850: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=795850 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Source: pdfgrep Version: 1.4.0-2 Severity: serious Justification: fails to build from source User: reproducible-bui...@lists.alioth.debian.org Usertags: ftbfs X-Debbugs-Cc: reproducible-bui...@lists.alioth.debian.org Dear Maintainer, pdfgrep fails to build from source on unstable/amd64: [..] dh_auto_build make -j1 make[1]: Entering directory '/tmp/buildd/pdfgrep-1.4.0' make all-recursive make[2]: Entering directory '/tmp/buildd/pdfgrep-1.4.0' Making all in src make[3]: Entering directory '/tmp/buildd/pdfgrep-1.4.0/src' g++ -DHAVE_CONFIG_H -I. -I.. -I/usr/include/poppler/cpp -I/usr/include/poppler-Wdate-time -D_FORTIFY_SOURCE=2 -g -O2 -fstack-protector-strong -Wformat -Werror=format-security -std=c++11 -c -o pdfgrep.o pdfgrep.cc pdfgrep.cc: In function 'int search_in_document(poppler::document*, const string, Regengine)': pdfgrep.cc:185:8: warning: 'templateclass class std::auto_ptr' is deprecated [-Wdeprecated-declarations] std::auto_ptrpoppler::page doc_page(doc-create_page(i - 1)); ^ In file included from /usr/include/c++/5/memory:81:0, from pdfgrep.cc:54: /usr/include/c++/5/bits/unique_ptr.h:49:28: note: declared here templatetypename class auto_ptr; ^ g++ -DHAVE_CONFIG_H -I. -I.. -I/usr/include/poppler/cpp -I/usr/include/poppler-Wdate-time -D_FORTIFY_SOURCE=2 -g -O2 -fstack-protector-strong -Wformat -Werror=format-security -std=c++11 -c -o output.o output.cc g++ -DHAVE_CONFIG_H -I. -I.. -I/usr/include/poppler/cpp -I/usr/include/poppler-Wdate-time -D_FORTIFY_SOURCE=2 -g -O2 -fstack-protector-strong -Wformat -Werror=format-security -std=c++11 -c -o exclude.o exclude.cc g++ -DHAVE_CONFIG_H -I. -I.. -I/usr/include/poppler/cpp -I/usr/include/poppler-Wdate-time -D_FORTIFY_SOURCE=2 -g -O2 -fstack-protector-strong -Wformat -Werror=format-security -std=c++11 -c -o regengine.o regengine.cc g++ -g -O2 -fstack-protector-strong -Wformat -Werror=format-security -std=c++11 -Wl,-z,relro -o pdfgrep pdfgrep.o output.o exclude.o regengine.o -lpoppler-cpp -lpcre pdfgrep.o: In function `print_version()': /tmp/buildd/pdfgrep-1.4.0/src/pdfgrep.cc:429: undefined reference to `poppler::version_string[abi:cxx11]()' pdfgrep.o: In function `do_search_in_document(std::__cxx11::basic_stringchar, std::char_traitschar, std::allocatorchar const, std::__cxx11::basic_stringchar, std::char_traitschar, std::allocatorchar const, Regengine, bool)': /tmp/buildd/pdfgrep-1.4.0/src/pdfgrep.cc:463: undefined reference to `poppler::document::load_from_file(std::__cxx11::basic_stringchar, std::char_traitschar, std::allocatorchar const, std::__cxx11::basic_stringchar, std::char_traitschar, std::allocatorchar const, std::__cxx11::basic_stringchar, std::char_traitschar, std::allocatorchar const)' collect2: error: ld returned 1 exit status Makefile:276: recipe for target 'pdfgrep' failed make[3]: *** [pdfgrep] Error 1 make[3]: Leaving directory '/tmp/buildd/pdfgrep-1.4.0/src' Makefile:296: recipe for target 'all-recursive' failed make[2]: *** [all-recursive] Error 1 make[2]: Leaving directory '/tmp/buildd/pdfgrep-1.4.0' Makefile:236: recipe for target 'all' failed make[1]: *** [all] Error 2 make[1]: Leaving directory '/tmp/buildd/pdfgrep-1.4.0' dh_auto_build: make -j1 returned exit code 2 debian/rules:4: 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/pdfgrep_1.4.0-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: Fri Aug 14 13:03:23 GMT+12 2015 I: pbuilder-time-stamp: 1439600603 I: Building the build Environment I: extracting base tarball
Bug#796405: marked as done (unattended-upgrades: FTBFS: test_pep8_clean: AssertionError: 1 != 0)
Your message dated Tue, 25 Aug 2015 09:23:47 +
with message-id e1zuasj-0001cf...@franck.debian.org
and subject line Bug#796405: fixed in unattended-upgrades 0.86.3
has caused the Debian Bug report #796405,
regarding unattended-upgrades: FTBFS: test_pep8_clean: AssertionError: 1 != 0
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 ow...@bugs.debian.org
immediately.)
--
796405: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=796405
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
---BeginMessage---
Source: unattended-upgrades
Version: 0.86.2
Severity: serious
Justification: fails to build from source
User: reproducible-bui...@lists.alioth.debian.org
Usertags: ftbfs
X-Debbugs-Cc: reproducible-bui...@lists.alioth.debian.org
Dear Maintainer,
unattended-upgrades fails to build from source in unstable/amd64:
[..]
==
FAIL: test_pep8_clean (__main__.PackagePep8TestCase)
--
Traceback (most recent call last):
File ./test_pep8.py, line 20, in test_pep8_clean
[pep8, --repeat, --ignore=%s % IGNORE] + targets), 0)
AssertionError: 1 != 0
--
Ran 1 test in 1.343s
FAILED (failures=1)
Makefile:6: recipe for target 'check' failed
[..]
The full build log is attached or can be viewed here:
https://reproducible.debian.net/logs/unstable/amd64/unattended-upgrades_0.86.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: Fri Aug 21 06:23:05 GMT+12 2015
I: pbuilder-time-stamp: 1440181385
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 pbuilder-ma...@lists.alioth.debian.org
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 (= 7.0.50~), po-debconf, python (= 2.6.6-3~),
python3-distutils-extra, python3-setuptools, python-dev, python3-dev,
python-coverage, pep8, pyflakes, python-apt, python3-apt, python-mock,
python3-mock, lsb-release, dh-systemd (= 1.5)
dpkg-deb: building package 'pbuilder-satisfydepends-dummy' in
'/tmp/satisfydepends-aptitude/pbuilder-satisfydepends-dummy.deb'.
Selecting previously unselected package pbuilder-satisfydepends-dummy.
(Reading database ... 20247 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 (= 2.6.6-3~); however:
Package python is not installed.
pbuilder-satisfydepends-dummy depends on python3-distutils-extra; however:
Package python3-distutils-extra is not installed.
pbuilder-satisfydepends-dummy depends on python3-setuptools; however:
Package python3-setuptools is not installed.
pbuilder-satisfydepends-dummy depends on python-dev; however:
Package python-dev is not installed.
pbuilder-satisfydepends-dummy depends on python3-dev; however:
Package python3-dev is not installed.
pbuilder-satisfydepends-dummy depends on python-coverage; however:
Package python-coverage is not installed.
pbuilder-satisfydepends-dummy depends on pep8; however:
Package pep8 is not installed.
pbuilder-satisfydepends-dummy depends on pyflakes; however:
Package pyflakes is not installed.
pbuilder-satisfydepends-dummy depends on python-apt; however:
Packa
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}
Bug#796753: marked as done (FTBFS: tries to download from PyPI)
Your message dated Tue, 25 Aug 2015 09:23:17 +
with message-id e1zuarp-0001em...@franck.debian.org
and subject line Bug#796753: fixed in python-django-pyscss 1.0.3-4
has caused the Debian Bug report #796753,
regarding FTBFS: tries to download from PyPI
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 ow...@bugs.debian.org
immediately.)
--
796753: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=796753
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
---BeginMessage---
Package: python-django-pyscss
Version: 2.0.2-1
Severity: serious
Justification: fails to build from source
User: python-dja...@packages.debian.org
Usertags: django18
Hello,
During a test rebuild of packages dependent on python-django for the upcoming
Django 1.8 transition, your package failed to build from source.
This rebuild was done against unstable on an amd64 system, under python-django
1.7.9-1.
The log from the build is attached. Relevant portions enclosed below.
-- Luke Faraone
=== Testing with python2.7
running test
Searching for mock
Reading https://pypi.python.org/simple/mock/
Download error on https://pypi.python.org/simple/mock/: [SSL:
CERTIFICATE_VERIFY_FAILED] certificate verify failed (_ssl.c:590) -- Some
packages may not be found!
Couldn't find index page for 'mock' (maybe misspelled?)
Scanning index of all packages (this may take a while)
Reading https://pypi.python.org/simple/
Download error on https://pypi.python.org/simple/: [SSL:
CERTIFICATE_VERIFY_FAILED] certificate verify failed (_ssl.c:590) -- Some
packages may not be found!
No local packages or download links found for mock
error: Could not find suitable distribution for Requirement.parse('mock')
make[1]: *** [override_dh_auto_test] Error 1
debian/rules:29: recipe for target 'override_dh_auto_test' failed
make[1]: Leaving directory '/«PKGBUILDDIR»'
make: *** [build] Error 2
debian/rules:10: recipe for target 'build' failed
dpkg-buildpackage: error: debian/rules build gave error exit status 2
python-django-pyscss_2.0.2-1_amd64.build
Description: inode/symlink
---End Message---
---BeginMessage---
Source: python-django-pyscss
Source-Version: 1.0.3-4
We believe that the bug you reported is fixed in the latest version of
python-django-pyscss, which is due to be installed in the Debian FTP archive.
A summary of the changes between this version and the previous one is
attached.
Thank you for reporting the bug, which will now be closed. If you
have further comments please address them to 796...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Thomas Goirand z...@debian.org (supplier of updated python-django-pyscss
package)
(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Format: 1.8
Date: Mon, 24 Aug 2015 17:21:16 +0200
Source: python-django-pyscss
Binary: python-django-pyscss
Architecture: source all
Version: 1.0.3-4
Distribution: unstable
Urgency: medium
Maintainer: PKG OpenStack openstack-de...@lists.alioth.debian.org
Changed-By: Thomas Goirand z...@debian.org
Description:
python-django-pyscss - makes it easier to use PySCSS in Django
Closes: 796753
Changes:
python-django-pyscss (1.0.3-4) unstable; urgency=medium
.
* Added missing dependency for python-mock (Closes: #796753).
* Move some stuff from Build-Depends to Build-Depends-Indep.
* Added dh-python as build-depends.
* Disabling unit test at build time for now.
Checksums-Sha1:
45e60ccd7d934162cd777ca145ac3183b3e52194 2249 python-django-pyscss_1.0.3-4.dsc
c2561b9e093ae12e732d136b7d67c236463699e6 4156
python-django-pyscss_1.0.3-4.debian.tar.xz
662c4bbc4e90df6369e30e24a672492e1195ebd6 8560
python-django-pyscss_1.0.3-4_all.deb
Checksums-Sha256:
a1aca4fa97cc3423b719cd24c40554bbc4949b69622bbaa89d61019f5d93df83 2249
python-django-pyscss_1.0.3-4.dsc
4f278001bcb9df1fc94281217d1673c2eeff9aa014d3955582659d51b3c84401 4156
python-django-pyscss_1.0.3-4.debian.tar.xz
b290f85da43f9ae73aac882b501984e492bad380ddc7855a8bde0a8e7e7f0d17 8560
python-django-pyscss_1.0.3-4_all.deb
Files:
c5cfc189ff9a7d13164f8fb5cc63bf02 2249 python optional
python-django-pyscss_1.0.3-4.dsc
60af89a9ca2e44bcd6642647220f56f2 4156 python optional
python-django-pyscss_1.0.3-4.debian.tar.xz
b1f847679d0dc6dee64308d7a3622b59 8560 python optional
python-django-pyscss_1.0.3-4_all.deb
-BEGIN PGP SIGNATURE-
Version: GnuPG v1
Bug#792407: marked as done (spice-gtk: please drop unneeded libspice-server-dev dependencies from libspice-client-glib-2.0-dev)
Your message dated Tue, 25 Aug 2015 09:23:37 + with message-id e1zuas9-0001xg...@franck.debian.org and subject line Bug#792407: fixed in spice-gtk 0.28-1.1 has caused the Debian Bug report #792407, regarding spice-gtk: please drop unneeded libspice-server-dev dependencies from libspice-client-glib-2.0-dev 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 ow...@bugs.debian.org immediately.) -- 792407: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=792407 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Source: spice-gtk Severity: important libspice-server-dev dependencies from libspice-client-glib-2.0-dev is not needed based on my tests and looking other distros (fedora if I remember good). It block for virt-viewer build require unneeded spice-server, I already built virt-viewer (and used with spice) successful on armhf removing libspice-server-dev dependencies from libspice-client-glib-2.0-dev. It block also migration to testing of latest build. Thanks for any reply and sorry for my bad english. ---End Message--- ---BeginMessage--- Source: spice-gtk Source-Version: 0.28-1.1 We believe that the bug you reported is fixed in the latest version of spice-gtk, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 792...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Laurent Bigonville bi...@debian.org (supplier of updated spice-gtk package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Mon, 24 Aug 2015 20:57:27 +0200 Source: spice-gtk Binary: spice-client-gtk spice-client-gtk-dbg spice-client-glib-usb-acl-helper spice-client-glib-usb-acl-helper-dbg libspice-client-glib-2.0-8 gir1.2-spice-client-glib-2.0 libspice-client-glib-2.0-dev libspice-client-gtk-2.0-4 gir1.2-spice-client-gtk-2.0 libspice-client-gtk-2.0-dev libspice-client-gtk-3.0-4 gir1.2-spice-client-gtk-3.0 libspice-client-gtk-3.0-dev python-spice-client-gtk python-spice-client-gtk-dbg spice-gtk-dbg Architecture: source amd64 Version: 0.28-1.1 Distribution: unstable Urgency: medium Maintainer: Liang Guo guoli...@debian.org Changed-By: Laurent Bigonville bi...@debian.org Description: gir1.2-spice-client-glib-2.0 - GObject for communicating with Spice servers (GObject-Introspecti gir1.2-spice-client-gtk-2.0 - GTK2 widget for SPICE clients (GObject-Introspection) gir1.2-spice-client-gtk-3.0 - GTK3 widget for SPICE clients (GObject-Introspection) libspice-client-glib-2.0-8 - GObject for communicating with Spice servers (runtime library) libspice-client-glib-2.0-dev - GObject for communicating with Spice servers (development files) libspice-client-gtk-2.0-4 - GTK2 widget for SPICE clients (runtime library) libspice-client-gtk-2.0-dev - GTK2 widget for SPICE clients (development files) libspice-client-gtk-3.0-4 - GTK3 widget for SPICE clients (runtime library) libspice-client-gtk-3.0-dev - GTK3 widget for SPICE clients (development files) python-spice-client-gtk - GTK2 widget for SPICE clients (Python binding) python-spice-client-gtk-dbg - GTK2 widget for SPICE clients (Python binding symbols) spice-client-glib-usb-acl-helper - Helper tool to validate usb ACLs spice-client-glib-usb-acl-helper-dbg - Helper tool to validate usb ACLs(debug symbols) spice-client-gtk - Simple clients for interacting with SPICE servers spice-client-gtk-dbg - Simple clients for interacting with SPICE servers(debug symbols) spice-gtk-dbg - Debugging symbols for spice-gtk packages Closes: 786835 792407 Changes: spice-gtk (0.28-1.1) unstable; urgency=medium . * Non-maintainer upload. * Drop libspice-server-dev dependencies from libspice-client-glib-2.0-dev it's not needed and block the migration to testing because it's not available on some architectures (Closes: #792407) * Enable smartcard support (Closes: #786835) Checksums-Sha1: 9ccc93cf7bd751afb2663781d658a4ecb41240f0 3372 spice-gtk_0.28-1.1.dsc 0e47e01ac106d2f0e100fe45071e418e00c458f2 11964 spice-gtk_0.28-1.1.debian.tar.xz d955ae4a6f354f8d04c6642874bebb8afdbaac8c 142716 gir1.2-spice-client-glib-2.0_0.28-1.1_amd64.deb 0c2e86eb52eb0294c2802b81a18cafd414bc3a4f 137410
Processed: coinor-osi: diff for gcc5 transition; fails the tests though
Processing control commands: tags 796715 + patch Bug #796715 [src:coinor-osi] coinor-osi: library transition needed with GCC 5 as default Added tag(s) patch. -- 796715: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=796715 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#796715: coinor-osi: diff for gcc5 transition; fails the tests though
Control: tags 796715 + patch Dear maintainer, Hi, I looked at this one given it's a r-dep of coinmp and thus other coin-* stuff, which in turn is one of LibreOffice Calc :) and prepared the following patch. Unfortunately, this then fails its tests. (I guess that's why you tagged the bug help? There's no explanation, so..) Log: creating unitTest ./unitTest -mpsDir=`echo /usr/share/coin/Data/Sample` Testing OsiRowCut with OsiTestSolverInterface *** Error in `/home/rene/coinor-osi-0.106.9/test/.libs/lt-unitTest': free(): invalid pointer: 0x7f23c64c84f0 *** Coin0001I At line 29 NAME EXAMPLE Coin0001I At line 30 ROWS Coin0001I At line 37 COLUMNS Coin0001I At line 55 RHS Coin0001I At line 61 RANGES Coin0001I At line 64 BOUNDS Coin0001I At line 70 ENDATA Coin0002I Problem EXAMPLE has 5 rows, 8 columns and 14 elements Makefile:687: recipe for target 'test' failed make[2]: *** [test] Aborted make[2]: Leaving directory '/home/rene/coinor-osi-0.106.9/test' Makefile:907: recipe for target 'test' failed make[1]: *** [test] Error 2 make[1]: Leaving directory '/home/rene/coinor-osi-0.106.9' dh_auto_test: make -j1 test returned exit code 2 debian/rules:21: recipe for target 'build' failed make: *** [build] Error 2 dpkg-buildpackage: error: debian/rules build gave error exit status 2 debuild: fatal error at line 1374: dpkg-buildpackage -rfakeroot -D -us -uc -b failed After hacking a set -x into ./unitTest I see + exec /home/rene/coinor-osi-0.106.9/test/.libs/lt-unitTest -mpsDir=/usr/share/coin/Data/Sample called so (sid)rene@frodo:~/coinor-osi-0.106.9/test$ gdb /home/rene/coinor-osi-0.106.9/test/.libs/lt-unitTest GNU gdb (Debian 7.9.1-1) 7.9.1 Copyright (C) 2015 Free Software Foundation, Inc. License GPLv3+: GNU GPL version 3 or later http://gnu.org/licenses/gpl.html This is free software: you are free to change and redistribute it. There is NO WARRANTY, to the extent permitted by law. Type show copying and show warranty for details. This GDB was configured as x86_64-linux-gnu. Type show configuration for configuration details. For bug reporting instructions, please see: http://www.gnu.org/software/gdb/bugs/. Find the GDB manual and other documentation resources online at: http://www.gnu.org/software/gdb/documentation/. For help, type help. Type apropos word to search for commands related to word... Reading symbols from /home/rene/coinor-osi-0.106.9/test/.libs/lt-unitTest...done. (gdb) run -mpsDir=/usr/share/coin/Data/Sample Starting program: /home/rene/coinor-osi-0.106.9/test/.libs/lt-unitTest -mpsDir=/usr/share/coin/Data/Sample Testing OsiRowCut with OsiTestSolverInterface Coin0001I At line 29 NAME EXAMPLE Coin0001I At line 30 ROWS Coin0001I At line 37 COLUMNS Coin0001I At line 55 RHS Coin0001I At line 61 RANGES Coin0001I At line 64 BOUNDS Coin0001I At line 70 ENDATA Coin0002I Problem EXAMPLE has 5 rows, 8 columns and 14 elements *** Error in `/home/rene/coinor-osi-0.106.9/test/.libs/lt-unitTest': free(): invalid pointer: 0x7646e4f0 *** Program received signal SIGABRT, Aborted. 0x75b54107 in __GI_raise (sig=sig@entry=6) at ../nptl/sysdeps/unix/sysv/linux/raise.c:56 56 ../nptl/sysdeps/unix/sysv/linux/raise.c: No such file or directory. (gdb) bt #0 0x75b54107 in __GI_raise (sig=sig@entry=6) at ../nptl/sysdeps/unix/sysv/linux/raise.c:56 #1 0x75b554e8 in __GI_abort () at abort.c:89 #2 0x75b92214 in __libc_message (do_abort=do_abort@entry=1, fmt=fmt@entry=0x75c85000 *** Error in `%s': %s: 0x%s ***\n) at ../sysdeps/posix/libc_fatal.c:175 #3 0x75b979ee in malloc_printerr (action=1, str=0x75c810be free(): invalid pointer, ptr=optimized out) at malloc.c:4996 #4 0x75b986f6 in _int_free (av=optimized out, p=optimized out, have_lock=0) at malloc.c:3840 #5 0x0041812d in deallocate (this=0x646088, __p=optimized out) at /usr/include/c++/5/ext/new_allocator.h:110 #6 deallocate (__a=..., __n=optimized out, __p=optimized out) at /usr/include/c++/5/ext/alloc_traits.h:185 #7 _M_destroy (__size=optimized out, this=0x646088) at /usr/include/c++/5/bits/basic_string.h:185 #8 _M_dispose (this=0x646088) at /usr/include/c++/5/bits/basic_string.h:180 #9 ~basic_string (this=0x646088, __in_chrg=optimized out) at /usr/include/c++/5/bits/basic_string.h:544 #10 CoinError::~CoinError (this=0x646020, __in_chrg=optimized out) at /usr/include/coin/CoinError.hpp:142 #11 0x7646c87f in ?? () from /usr/lib/x86_64-linux-gnu/libstdc++.so.6 #12 0x77689627 in CoinPackedVector::gutsOfSetVector(int, int const*, double const*, bool, char const*) () from /usr/lib/x86_64-linux-gnu/libCoinUtils.so.3 #13 0x77b816b5 in OsiRowCutUnitTest (baseSiP=baseSiP@entry= 0x7fffe0e0, mpsDir=/usr/share/coin/Data/Sample/) at OsiRowCutTest.cpp:270 #14 0x00407009 in main (argc=optimized out, argv=0x7fffe368) at unitTest.cpp:177 (gdb) No idea what that
Bug#796874: gtkspellmm: transition needed for g++-5 ABI
Source: gtkspellmm Version: 3.0.3+dfsg-1 Severity: serious Justification: ABI break Background[1]: libstdc++6 introduces a new ABI to conform to the C++11 standard, but keeps the old ABI to not break existing binaries. Packages which are built with g++-5 from experimental (not the one from testing/unstable) are using the new ABI. Libraries built from this source package export some of the new __cxx11 or B5cxx11 symbols, dropping other symbols. If these symbols are part of the API of the library, then this rebuild with g++-5 will trigger a transition for the library. In the case of gtkspellmm, Glib::ustring appears in header files that get installed; Glib::ustring has a std::string as a data member, resulting in sizeof(Glib::ustring) changing, so it seems very likely that a transition is needed. This will look a lot like the one for gstreamermm-1.0. I'm happy to sponsor or NMU as required. S
Processed (with 1 errors): some stuff
Processing commands for cont...@bugs.debian.org: user reproducible-bui...@lists.alioth.debian.org Setting user to reproducible-bui...@lists.alioth.debian.org (was mat...@mapreri.org). usertags 789038 + ftbfs There were no usertags set. Usertags are now: ftbfs. usertags 778176 + ftbfs There were no usertags set. Usertags are now: ftbfs. usertags 91 + ftbfs There were no usertags set. Usertags are now: ftbfs. forcemerge 765321 767439 Bug #765321 [src:pyzmq] pyzmq: FTBFS on arm64 Unable to merge bugs because: package of #767439 is 'python-zmq' not 'src:pyzmq' Failed to forcibly merge 765321: Did not alter merged bugs. severity 749208 serious Bug #749208 [kitchen] kitchen: FTBFS as tests fail Severity set to 'serious' from 'normal' usertags 795609 + ftbfs There were no usertags set. Usertags are now: ftbfs. usertags 795590 + ftbfs There were no usertags set. Usertags are now: ftbfs. usertags 795589 + ftbfs There were no usertags set. Usertags are now: ftbfs. usertags 795588 + ftbfs There were no usertags set. Usertags are now: ftbfs. usertags 795587 + ftbfs There were no usertags set. Usertags are now: ftbfs. usertags 795586 + ftbfs There were no usertags set. Usertags are now: ftbfs. usertags 795585 + ftbfs There were no usertags set. Usertags are now: ftbfs. usertags 795584 + ftbfs There were no usertags set. Usertags are now: ftbfs. usertags 795582 + ftbfs There were no usertags set. Usertags are now: ftbfs. usertags 795580 + ftbfs There were no usertags set. Usertags are now: ftbfs. usertags 795579 + ftbfs There were no usertags set. Usertags are now: ftbfs. usertags 795523 + ftbfs There were no usertags set. Usertags are now: ftbfs. usertags 795521 + ftbfs There were no usertags set. Usertags are now: ftbfs. usertags 795520 + ftbfs There were no usertags set. Usertags are now: ftbfs. usertags 795515 + ftbfs There were no usertags set. Usertags are now: ftbfs. usertags 795511 + ftbfs There were no usertags set. Usertags are now: ftbfs. usertags 795508 + ftbfs There were no usertags set. Usertags are now: ftbfs. usertags 795206 + ftbfs There were no usertags set. Usertags are now: ftbfs. usertags 794027 + ftbfs There were no usertags set. Usertags are now: ftbfs. usertags 791866 + ftbfs There were no usertags set. Usertags are now: ftbfs. usertags 791541 + ftbfs There were no usertags set. Usertags are now: ftbfs. usertags 789093 + ftbfs There were no usertags set. Usertags are now: ftbfs. usertags 795691 + ftbfs There were no usertags set. Usertags are now: ftbfs. usertags 795712 + ftbfs There were no usertags set. Usertags are now: ftbfs. usertags 795714 + ftbfs There were no usertags set. Usertags are now: ftbfs. usertags 795715 + ftbfs There were no usertags set. Usertags are now: ftbfs. usertags 795717 + ftbfs There were no usertags set. Usertags are now: ftbfs. usertags 795724 + ftbfs There were no usertags set. Usertags are now: ftbfs. usertags 795726 + ftbfs There were no usertags set. Usertags are now: ftbfs. usertags 795728 + ftbfs There were no usertags set. Usertags are now: ftbfs. usertags 795729 + ftbfs There were no usertags set. Usertags are now: ftbfs. usertags 795741 + ftbfs There were no usertags set. Usertags are now: ftbfs. thanks Stopping processing here. Please contact me if you need assistance. -- 749208: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=749208 765321: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=765321 767439: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=767439 795741: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=795741 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#766884: libxml2 broken in sid for months already
Hi, On Thu, 20 Aug 2015, Vincent Lefevre wrote: I completely agree that libxml2 should be reverted to 2.9.1 (I have never used 2.9.2 due to this bug). I just did this. And IMHO, the new package should probably break libxml-libxml-perl 2.0116+dfsg-4 due to an annoying and useless test of the versions in the Perl module (bug 783610). So, libxml-libxml-perl should be rebuilt against libxml2 2.9.1, which would make bug 783610 no longer appear in most cases. But not this. We should just ask for bin-NMU of libxml-libxml-perl once the new libxml2 is built. Can you take care of this? https://wiki.debian.org/binNMU (You can do it immediately if you combine it with appropriate dep-wait) Cheers, -- Raphaël Hertzog ◈ Debian Developer Support Debian LTS: http://www.freexian.com/services/debian-lts.html Learn to master Debian: http://debian-handbook.info/get/
Bug#793630: groovy 1.8.6 and libcommons-cli-java 1.3.1 FTBFS
On Wed, 29 Jul 2015 10:49:12 -0300 Miguel Landaeta nomad...@debian.org wrote: On Wed, Jul 29, 2015 at 10:00:16AM +0100, Russel Winder wrote: Emmanuel, Miguel, Hi Russel, Apache Groovy 1.x series is no longer maintained. All effort is now on the Apache Groovy 2.4.x and 2.5-SNAPSHOT versions. If Debian is to remove Commons CLI 1.2 then I suggest removing the groovy package since the groovy2 package is in place already, and is the right version for Debian to go with. That's right. We are no longer maintaining Groovy 1.x although we have several packages depending on it and our latest Debian stable release still includes groovy 1.x. I stumbled upon this bug due to my attempt to fix CVE-2015-3253 in unstable for groovy 1.8.6 (the published fix is relevant for all groovy versions since 1.7.0). I expect to remove groovy eventually but in the meantime we are applying only security bug fixes. We are working on groovy2 now. Hi all, I suggest to ask the release team for an exception and to provide the security fix via testing-proposed-updates. The CVE-fix appears to be straightforward and could be uploaded afterwards to stable-proposed-updates. We shouldn't invest too much time in groovy 1.x anymore. I think the time is better spent on trying to switch all r-deps from groovy 1.x to 2.x as soon as possible and getting rid of this package. Regards, Markus signature.asc Description: OpenPGP digital signature
Bug#794581: Happened again! Argh!
On Tuesday, August 25, 2015 05:40:35 PM Borden Rhodes wrote: So I ran aptitude dist-upgrade on my stretch box this afternoon. It updated libkdecorations2-5 and libkdecorations2private5 both to 4:5.3.2-2+b1. It also upgraded libkf5archive5 to 5.12.0-1+b1, along with 40 other packages which I don't think are related to this problem. Once again, KDE krashes as it did before. However, since breeze is already at the sid version, I can't upgrade it. How do I get my desktop back? Could the the kf5 libraries be held in sid and sent to testing in such a way that these breakages don't occur? If it weren't for the earlier advice to update breeze, I'd still be out of an operating system. This is no good! Now that kdecoration has been rebuilt in testing, downgrade to the testing version of breeze. One way to downgrade would be to manually download the 4:5.3.2-2 packages from breeze that you have installed from http://http.debian.net/debian/pool/main/b/breeze (that will redirect to a ~nearby mirror) and manually install them with dpkg. Scott K
Bug#796909: python3-pies: Don't Depend on python3-enum34
Package: python3-pies Severity: serious -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Dear Maintainer, python3-enum34 binary package has been removed from the archive, because all supported versions of Python 3 already include the stdlib enum package, and enum34 is no longer compatible with Python 3.5. python3-pies Depends on it though. Please remove the dependency (it's fine for python-pies to Depend on python-enum34). % apt-cache show python3-pies | grep Depends Depends: python3-enum34, python3:any (= 3.3.2-2~) - -- System Information: Debian Release: stretch/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: amd64 (x86_64) Kernel: Linux 4.1.0-2-amd64 (SMP w/1 CPU core) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) -BEGIN PGP SIGNATURE- Version: GnuPG v1 iQIcBAEBCAAGBQJV3LL1AAoJEBJutWOnSwa/UxwP+gKAE+oyMFqB/0gRmQAibUP1 GXyEtqhO9yDAeM4Hy9uSgdLIhw/tUWEsdhFcOsKjUFPoNkc4nQlgKr6MYT6MsuFD 11yuvNIFJKnaarGUViIotRgWzli4OvcZ9W2TKrff+zCLpnZUo+Q5UxZFWU5HRstr 7xEbjXzRNCMrrHQgU42KALZSM8V7Gyt7XVSzzTnQufKzTgGtICs4trXV7otmitJN ZHrp44W+LQRO2y7rnOglxHq/lrJBLLGushiCWy8p58I0fsLQIA0nlufEOqPZgOFc /IQ3it/ERvLAk4hO0NHxZSMOyOWAOhU5MQm0uQ09uEQAeb6LMLkVx5jZfHyQ69/Q crY22dfJTEuIW/mu35Pr0iMkzCJxAtDPsAr0cXI0pV6rFAKs2jxereXbvFiayg7/ eUfxz2kEyhUZuu8o7y1FvCzaO1YKQNH/Js/Y9e8GkdTZs3MGjC2kPYJ9w0XWTyRP KEffvm6/Fll0ddvv9IcCuePDmACJswGcRoONK4jb/xjLjOENciKj/OuGQwBSZboK sDH5dJvAD2UK/VoVq+TRcRaAhiCoC5NheUTnxsoAdnAMjUObmu0sdRGvqU0JzWns nfJAJ1mLyL++3qVXIfkn3gAjzUQR0xoaYG5//kvduDTDw99FjGQABdZ5wceJQEcP F6MGP6bapA57NIgTkl/w =tao4 -END PGP SIGNATURE-
Bug#782750: marked as done (make-dfsg: FTBFS: features/archives test fails)
Your message dated Tue, 25 Aug 2015 18:34:16 + with message-id e1zuj32-0001mx...@franck.debian.org and subject line Bug#782750: fixed in make-dfsg 4.0-8.2 has caused the Debian Bug report #782750, regarding make-dfsg: FTBFS: features/archives test fails 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 ow...@bugs.debian.org immediately.) -- 782750: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=782750 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Source: make-dfsg Version: 4.0-8.1 When building with binutils 2.25-6, the version currently in unstable, it fails to build. The output is: features/archives ... FAILED (3/10 passed) It's clear what's happening here. This entry in the changelog for binutils (2.25-6) explains it: * Configure with --enable-deterministic-archives. Closes: #774429. Files are added to archives with a zero timestamp so make then adds them again, unexpectedly. However, I'm not sure how you'll want to fix this. Weaken the test somehow? ---End Message--- ---BeginMessage--- Source: make-dfsg Source-Version: 4.0-8.2 We believe that the bug you reported is fixed in the latest version of make-dfsg, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 782...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Aurelien Jarno aure...@debian.org (supplier of updated make-dfsg package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.8 Date: Tue, 25 Aug 2015 20:05:48 +0200 Source: make-dfsg Binary: make make-guile Architecture: source Version: 4.0-8.2 Distribution: unstable Urgency: medium Maintainer: Manoj Srivastava sriva...@debian.org Changed-By: Aurelien Jarno aure...@debian.org Description: make - utility for directing compilation make-guile - utility for directing compilation with guile support Closes: 782750 Changes: make-dfsg (4.0-8.2) unstable; urgency=medium . * Non-maintainer upload. * Use a wrapper in the testsuite for ar to force it to not run in deterministic mode (Closes: #782750). Checksums-Sha1: 7928ea23b3f6302d1ce2eb5cb8f4c8052ade06fe 2019 make-dfsg_4.0-8.2.dsc ae3f828909b14a826de1ef783f8ead0952580faa 42392 make-dfsg_4.0-8.2.debian.tar.xz Checksums-Sha256: c2944f164e3bd92ad867cf3b4cf05914bc2ce2eb536c28db38c760d90029b42b 2019 make-dfsg_4.0-8.2.dsc d8512134ca9b8b5432dc87fa2e03de658b872797ea2fcafcb54c6a05755271ca 42392 make-dfsg_4.0-8.2.debian.tar.xz Files: 76c4db9569101c1060e08848e83d6d9c 2019 devel standard make-dfsg_4.0-8.2.dsc 5888451346542c80b26a7ed3121ef9f5 42392 devel standard make-dfsg_4.0-8.2.debian.tar.xz -BEGIN PGP SIGNATURE- Version: GnuPG v1 iQIcBAEBAgAGBQJV3LGfAAoJELqceAYd3YybPPIP/0LmHFtMumk88jDyA6Zz3K0y RZfQtexp3OKZJLRoCavWCDnDkTXNmZOYROS5YApLllLM7PDCeEVXjytG91Uzu1CS 0q1otlgwLxBnZY5qzc5/o0ZuyM+6JB2Sfw2psDwV18lAhAlvKbdFYZttWGQzY6oD i8UlAnQ9Pyz3b+rF5D2jPNp3uL+8SJNQPpl+jxaKgNKYW/ylO7SC42qSiJzCVZSf ZFmulgoUDtO1If4GoABtizIKcG7bUO4pPcJw8UFl/bCHyRRBhYDGxcbwEvagnmAp bUCYh9M8vOhxu+vvlzUKh6ReI6YecYkb53A8vyvrcMLx73hWvDunJBU0CS9w+4zf bVzC8/exnEGIqWHw8QJg+xRSOG6RfRvLzdIC1FPkp2Wzebnk0wJfyWZmXJk21/ek LoCuoZJ8k+pTs1EVmS4Eq/zAidHiSNmSfgU24Ua89iadvpDRDfnV6ePVEVAnnDpL UYoeR1J2ECoHHTZzTThDw3LBn2pN374hnqzakWu9rUztEd6EuN/ye9cWRzXAdLFF 0PODc2PJEo02AN4DP5bknY7Pc+U+Ho6eZGtAlBLY/mk4LFHRg02yZdmewmVp3yc0 QuV2uylSM402ldOYUehg7LHE5CH9aa7vrXwbqeen+E4+jFWxCseynjWgrfzwMNss Jx1O85d9NuiOQyKfZ+hv =vFjq -END PGP SIGNATUREEnd Message---
Bug#794581: Happened again! Argh!
On Tue, 25 Aug 2015 17:40:35 -0400 Borden Rhodes j...@bordenrhodes.com wrote: How do I get my desktop back? Downgrade breeze to 4:5.3.2-2, libkdecorations2-5 and libkdecorations2private5 to 4:5.3.2-1.
Bug#793961: Update on TimGM6mb bug?
Any news on this bug? It looks like quite a simple fix, I would do it myself but I don't know how to use the debian git system (I have only ever used github before). Best, Jack
Bug#766884: marked as done (libxml2: validity error : ID ... already defined errors with xmllint --noent)
Your message dated Tue, 25 Aug 2015 22:21:45 + with message-id e1zumbb-0003g0...@franck.debian.org and subject line Bug#766884: fixed in libxml2 2.9.2+really2.9.1+dfsg1-0.1 has caused the Debian Bug report #766884, regarding libxml2: validity error : ID ... already defined errors with xmllint --noent 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 ow...@bugs.debian.org immediately.) -- 766884: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=766884 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: libxml2 Version: 2.9.2+dfsg1-1 Severity: grave Justification: renders package unusable A major regression: when I use the --valid xmllint option, I get lots of validity error : ID ... already defined errors. If you can't reproduce the error, I'll try to provide a simple testcase (my files are huge). -- System Information: Debian Release: jessie/sid APT prefers unstable APT policy: (500, 'unstable'), (500, 'testing'), (500, 'stable'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.16-3-amd64 (SMP w/2 CPU cores) Locale: LANG=POSIX, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages libxml2 depends on: ii libc6 2.19-12 ii liblzma5 5.1.1alpha+20120614-2 ii multiarch-support 2.19-12 ii zlib1g 1:1.2.8.dfsg-2 Versions of packages libxml2 recommends: ii xml-core 0.13+nmu2 libxml2 suggests no packages. -- debconf-show failed ---End Message--- ---BeginMessage--- Source: libxml2 Source-Version: 2.9.2+really2.9.1+dfsg1-0.1 We believe that the bug you reported is fixed in the latest version of libxml2, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 766...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Raphaël Hertzog hert...@debian.org (supplier of updated libxml2 package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Tue, 25 Aug 2015 22:31:29 +0200 Source: libxml2 Binary: libxml2 libxml2-utils libxml2-utils-dbg libxml2-dev libxml2-dbg libxml2-doc python-libxml2 python-libxml2-dbg Architecture: source amd64 all Version: 2.9.2+really2.9.1+dfsg1-0.1 Distribution: unstable Urgency: medium Maintainer: Debian XML/SGML Group debian-xml-sgml-p...@lists.alioth.debian.org Changed-By: Raphaël Hertzog hert...@debian.org Description: libxml2- GNOME XML library libxml2-dbg - Debugging symbols for the GNOME XML library libxml2-dev - Development files for the GNOME XML library libxml2-doc - Documentation for the GNOME XML library libxml2-utils - XML utilities libxml2-utils-dbg - XML utilities (debug extension) python-libxml2 - Python bindings for the GNOME XML library python-libxml2-dbg - Python bindings for the GNOME XML library (debug extension) Closes: 766884 782782 782985 783010 Changes: libxml2 (2.9.2+really2.9.1+dfsg1-0.1) unstable; urgency=medium . * Non-maintainer upload. * Go back to 2.9.1+dfsg1 upstream sources so that xmllint works again. Closes: #766884 * Restore all patches available in 2.9.1+dfsg1-5 in stretch, ensuring CVE-2014-3660 is fixed too. * Fix 3 security issues by adding 4 patches: - CVE-2015-1819: The xmlreader in libxml allows remote attackers to cause a denial of service (memory consumption) via crafted XML data, related to an XML Entity Expansion (XEE) attack. Closes: #782782 - Out-of-bounds access when parsing unclosed HTML comment https://bugzilla.gnome.org/show_bug.cgi?id=746048 Closes: #782985 - Out-of-bounds memory access https://bugzilla.gnome.org/show_bug.cgi?id=744980 Closes: #783010 * Add dh-python to Build-Depends for dh_python2 Checksums-Sha1: a64ba3b2d1e0a8d751d04b17027e3a52bafdb203 2375 libxml2_2.9.2+really2.9.1+dfsg1-0.1.dsc 357366e7afc9dd03ba883c605d5c369decb2b2e1 3793894 libxml2_2.9.2+really2.9.1+dfsg1.orig.tar.gz ee0b0aa9016e5b4fb2540c9e313da13cfadbc59d 44304 libxml2_2.9.2+really2.9.1+dfsg1-0.1.debian.tar.xz 0ce53f22f8b37fa2c53bfa990539e68175b6defe 1725594 libxml2-dbg_2.9.2+really2.9.1+dfsg1-0.1_amd64.deb d90a5a909dda1a468ee8dabd0ce461371f247a84 798456
Bug#777981: marked as done (lightdm: ftbfs with GCC-5)
Your message dated Tue, 25 Aug 2015 19:20:47 + with message-id e1zujm3-0001qv...@franck.debian.org and subject line Bug#777981: fixed in lightdm 1.14.2-2 has caused the Debian Bug report #777981, regarding lightdm: ftbfs with GCC-5 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 ow...@bugs.debian.org immediately.) -- 777981: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=777981 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: src:lightdm Version: 1.10.3-3 Severity: normal Tags: sid stretch User: debian-...@lists.debian.org Usertags: ftbfs-gcc-5 Please keep this issue open in the bug tracker for the package it was filed for. If a fix in another package is required, please file a bug for the other package (or clone), and add a block in this package. Please keep the issue open until the package can be built in a follow-up test rebuild. The package fails to build in a test rebuild on at least amd64 with gcc-5/g++-5, but succeeds to build with gcc-4.9/g++-4.9. The severity of this report may be raised before the stretch release. The full build log can be found at: http://people.debian.org/~doko/logs/gcc5-20150205/lightdm_1.10.3-3_unstable_gcc5.log The last lines of the build log are at the end of this report. To build with GCC 5, either set CC=gcc-5 CXX=g++-5 explicitly, or install the gcc, g++, gfortran, ... packages from experimental. apt-get -t experimental install g++ Common build failures are C11 as the default C mode, new warnings resulting in build failures with -Werror turned on, or new/dropped symbols in Debian symbols files. For other C/C++ related build failures see the porting guide at http://gcc.gnu.org/gcc-5/porting_to.html [...] dh_lintian -a -O--parallel dh_perl -a -O--parallel dh_link -a -O--parallel dh_compress -a -O--parallel dh_fixperms -a -O--parallel dh_strip -a -O--parallel dh_makeshlibs -a -O--parallel dpkg-gensymbols: warning: some symbols or patterns disappeared in the symbols file: see diff output below dpkg-gensymbols: warning: debian/liblightdm-qt-3-0/DEBIAN/symbols doesn't match completely debian/liblightdm-qt-3-0.symbols --- debian/liblightdm-qt-3-0.symbols (liblightdm-qt-3-0_1.10.3-3_amd64) +++ dpkg-gensymbolsFaa8y8 2015-02-07 10:13:57.279515278 + @@ -1,6 +1,6 @@ liblightdm-qt-3.so.0 liblightdm-qt-3-0 #MINVER# - _ZN10QByteArrayD1Ev@Base 1.8.7 - _ZN10QByteArrayD2Ev@Base 1.8.7 +#MISSING: 1.10.3-3# _ZN10QByteArrayD1Ev@Base 1.8.7 +#MISSING: 1.10.3-3# _ZN10QByteArrayD2Ev@Base 1.8.7 _ZN10QDBusErrorD1Ev@Base 1.8.7 _ZN10QDBusErrorD2Ev@Base 1.8.7 _ZN10QDBusReplyI7QStringED1Ev@Base 1.8.7 @@ -13,19 +13,19 @@ _ZN5QHashIi10QByteArrayE11deleteNode2EPN9QHashData4NodeE@Base 1.8.7 _ZN5QHashIi10QByteArrayE13detach_helperEv@Base 1.8.7 _ZN5QHashIi10QByteArrayE13duplicateNodeEPN9QHashData4NodeEPv@Base 1.8.7 - _ZN5QHashIi10QByteArrayED1Ev@Base 1.8.7 - _ZN5QHashIi10QByteArrayED2Ev@Base 1.8.7 +#MISSING: 1.10.3-3# _ZN5QHashIi10QByteArrayED1Ev@Base 1.8.7 +#MISSING: 1.10.3-3# _ZN5QHashIi10QByteArrayED2Ev@Base 1.8.7 _ZN5QListI11SessionItemE18detach_helper_growEii@Base 1.8.7 _ZN5QListI11SessionItemE6appendERKS0_@Base 1.8.7 _ZN5QListI8UserItemE13detach_helperEi@Base 1.8.7 _ZN5QListI8UserItemE18detach_helper_growEii@Base 1.8.7 _ZN5QListI8UserItemE6appendERKS0_@Base 1.8.7 - _ZN5QListI8UserItemED1Ev@Base 1.8.7 - _ZN5QListI8UserItemED2Ev@Base 1.8.7 +#MISSING: 1.10.3-3# _ZN5QListI8UserItemED1Ev@Base 1.8.7 +#MISSING: 1.10.3-3# _ZN5QListI8UserItemED2Ev@Base 1.8.7 _ZN6QDebugD1Ev@Base 1.8.7 _ZN6QDebugD2Ev@Base 1.8.7 - _ZN7QStringD1Ev@Base 1.8.7 - _ZN7QStringD2Ev@Base 1.8.7 +#MISSING: 1.10.3-3# _ZN7QStringD1Ev@Base 1.8.7 +#MISSING: 1.10.3-3# _ZN7QStringD2Ev@Base 1.8.7 _ZN8QLightDM10UsersModel11qt_metacallEN11QMetaObject4CallEiPPv@Base 1.8.7 _ZN8QLightDM10UsersModel11qt_metacastEPKc@Base 1.8.7 _ZN8QLightDM10UsersModel16staticMetaObjectE@Base 1.8.7 dh_makeshlibs: failing due to earlier errors make: *** [binary-arch] Error 2 debian/rules:24: recipe for target 'binary-arch' failed dpkg-buildpackage: error: fakeroot debian/rules binary-arch gave error exit status 2 ---End Message--- ---BeginMessage--- Source: lightdm Source-Version: 1.14.2-2 We believe that the bug you reported is fixed in the latest version of lightdm, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 777...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate.
Bug#795617: marked as done (foodcritic: FTBFS: invalid option: -f)
Your message dated Tue, 25 Aug 2015 19:34:37 + with message-id e1zujzr-0004vz...@franck.debian.org and subject line Bug#795617: fixed in foodcritic 4.0.0-2 has caused the Debian Bug report #795617, regarding foodcritic: FTBFS: invalid option: -f 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 ow...@bugs.debian.org immediately.) -- 795617: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=795617 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Source: foodcritic Version: 4.0.0-1 Severity: serious Justification: fails to build from source Dear Maintainer, foodcritic fails to build from source on unstable/amd64: [..] /usr/bin/ruby2.1 /usr/bin/gem2deb-test-runner ┌──┐ │ Run tests for ruby2.1 from debian/ruby-tests.rake │ └──┘ RUBYLIB=/tmp/buildd/foodcritic-4.0.0/debian/foodcritic/usr/lib/ruby/vendor_ruby:. rake2.1 -f debian/ruby-tests.rake Run options: --seed 64717 [..] 688 scenarios (688 passed) 2223 steps (2223 passed) 0m42.038s invalid option: -f minitest options: -h, --help Display this help. -s, --seed SEED Sets random seed. Also via env. Eg: SEED=n rake -v, --verboseVerbose. Show progress processing files. -n, --name PATTERN Filter run on /regexp/ or string. Known extensions: pride -p, --pride Pride. Show your testing pride! ERROR: Test ruby2.1 failed. Exiting. dh_auto_install: dh_ruby --install /tmp/buildd/foodcritic-4.0.0/debian/foodcritic returned exit code 1 debian/rules:4: recipe for target 'binary' failed make: *** [binary] Error 1 dpkg-buildpackage: error: fakeroot debian/rules binary gave error exit status 2 [..] The full build log is attached or can be viewed here: https://reproducible.debian.net/rbuild/unstable/amd64/foodcritic_4.0.0-1.rbuild.log.gz Regards, -- ,''`. : :' : Chris Lamb `. `'` la...@debian.org / chris-lamb.co.uk `- Starting to build foodcritic/unstable on 2015-07-26 14:22 The jenkins build log is/was available at https://jenkins.debian.net/job/reproducible_builder_gamma/57507/console Reading package lists... Building dependency tree... Reading state information... NOTICE: 'foodcritic' packaging is maintained in the 'Git' version control system at: git://anonscm.debian.org/pkg-ruby-extras/foodcritic.git Need to get 336 kB of source archives. Get:1 http://ftp.de.debian.org/debian/ unstable/main foodcritic 4.0.0-1 (dsc) [2214 B] Get:2 http://ftp.de.debian.org/debian/ unstable/main foodcritic 4.0.0-1 (tar) [329 kB] Get:3 http://ftp.de.debian.org/debian/ unstable/main foodcritic 4.0.0-1 (diff) [4748 B] Fetched 336 kB in 0s (1120 kB/s) Download complete and in download only mode -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 3.0 (quilt) Source: foodcritic Binary: foodcritic Architecture: all Version: 4.0.0-1 Maintainer: Debian Ruby Extras Maintainers pkg-ruby-extras-maintain...@lists.alioth.debian.org Uploaders: Stefano Rivera stefa...@debian.org Homepage: http://acrmp.github.com/foodcritic Standards-Version: 3.9.6 Vcs-Browser: http://anonscm.debian.org/gitweb/?p=pkg-ruby-extras/foodcritic.git;a=summary Vcs-Git: git://anonscm.debian.org/pkg-ruby-extras/foodcritic.git Build-Depends: chef, cucumber (= 1.2.1), debhelper (= 8.1~), gem2deb (= 0.3.1~), rake, ruby-aruba (= 0.4.11), ruby-erubis, ruby-gherkin (= 2.11.7), ruby-minitest (= 3.3.0), ruby-nokogiri (= 1.5.4), ruby-ronn, ruby-treetop (= 1.4.10), ruby-yajl (= 1.1.0) Package-List: foodcritic deb ruby optional arch=all Checksums-Sha1: 59dc7d6979bbe7096533d421013a9add36d4d7cd 328958 foodcritic_4.0.0.orig.tar.gz 3ab158d847442a15e24183c8fbc3374ea8d8a92e 4748 foodcritic_4.0.0-1.debian.tar.xz Checksums-Sha256: f0880b8a852cba869d384f8acf66c6090cb009c7a8373daace795becdf57c623 328958 foodcritic_4.0.0.orig.tar.gz 9c7c8c47b98f2c24fb819ec90535ccd6801c984e8d69ce1c786dd3722741a2e2 4748 foodcritic_4.0.0-1.debian.tar.xz Files: e68c2867b63b4033c107cc6da15eaf38 328958 foodcritic_4.0.0.orig.tar.gz 9992dbd50a06671d940e5f995f6f4cb4 4748 foodcritic_4.0.0-1.debian.tar.xz Ruby-Versions: all -BEGIN PGP SIGNATURE- Version: GnuPG v1 iQIcBAEBCgAGBQJUSghIAAoJEACQ/CG1zRrMRrkQAI+SO+1YCpfpF+qE69n44u9G g5KNEGajO9epb9ns8cdUjUxePRuG0Fnu5XWOa/rs3RA7lh2Q2YIduT00cDO6Py3X
Bug#791782: marked as done (FTBFS: /usr/bin/rspec: [BUG] Segmentation fault at 0x00000000000000 (ruby2.2))
Your message dated Tue, 25 Aug 2015 19:36:20 + with message-id e1zuk16-0005iu...@franck.debian.org and subject line Bug#791782: fixed in ruby-patron 0.4.20-1 has caused the Debian Bug report #791782, regarding FTBFS: /usr/bin/rspec: [BUG] Segmentation fault at 0x00 (ruby2.2) 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 ow...@bugs.debian.org immediately.) -- 791782: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=791782 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Source: ruby-patron Version: 0.4.18-2 Severity: serious Justification: fails to build from source Dear Maintainer, your package ruby-patron currently FTBFS in unstable. Hopefully relevant snippet: /usr/bin/rspec: [BUG] Segmentation fault at 0x00 ruby 2.2.2p95 (2015-04-13) [x86_64-linux-gnu] -- Control frame information --- c:0001 p: s:0002 E:001f50 TOP[FINISH] -- Machine register context RIP: 0x7f816c55f23a RBP: 0x00c1 RSP: 0x7ffc45dd2bc0 RAX: 0x007f816d5ed5f000 RBX: 0x026ce97f RCX: 0x00b8 RDX: 0x0800 RDI: 0x7f816c889620 RSI: 0x R8: 0x0198ad10 R9: 0x R10: 0x7ffc45dd2c68 R11: 0x7f816c650c70 R12: 0x7f816c889620 R13: 0x026cea40 R14: 0x0070 R15: 0x7ffc45dd2c98 EFL: 0x00010202 -- C level backtrace information --- Killed /usr/bin/ruby2.2 /usr/bin/rspec --pattern ./spec/\*\*/\*_spec.rb failed ERROR: Test ruby2.2 failed. Exiting. dh_auto_install: dh_ruby --install /«PKGBUILDDIR»/debian/ruby-patron returned exit code 1 make: *** [binary] Error 1 sbuild (Debian sbuild) 0.65.2 (24 Mar 2015) on sxl.home.zeha.at ╔══╗ ║ ruby-patron 0.4.18-2 (amd64) 08 Jul 2015 12:54 ║ ╚══╝ Package: ruby-patron Version: 0.4.18-2 Source Version: 0.4.18-2 Distribution: sid Machine Architecture: amd64 Host Architecture: amd64 Build Architecture: amd64 I: NOTICE: Log filtering will replace 'build/ruby-patron-CGPci9/ruby-patron-0.4.18' with '«PKGBUILDDIR»' I: NOTICE: Log filtering will replace 'build/ruby-patron-CGPci9' with '«BUILDDIR»' I: NOTICE: Log filtering will replace 'var/lib/schroot/mount/sid-amd64-sbuild-c8ba39f7-725d-4335-a64d-521f352327f6' with '«CHROOT»' ┌──┐ │ Update chroot│ └──┘ Get:1 http://ftp.at.debian.org sid InRelease [204 kB] Get:2 http://ftp.at.debian.org sid/main Sources/DiffIndex [7876 B] Get:3 http://ftp.at.debian.org sid/main amd64 Packages/DiffIndex [7876 B] Get:4 http://ftp.at.debian.org sid/main Translation-en/DiffIndex [7876 B] Get:5 http://ftp.at.debian.org sid/main 2015-07-01-2039.58.pdiff [18.5 kB] Get:6 http://ftp.at.debian.org sid/main 2015-07-02-0242.54.pdiff [16.2 kB] Get:7 http://ftp.at.debian.org sid/main 2015-07-02-0843.38.pdiff [7440 B] Get:8 http://ftp.at.debian.org sid/main 2015-07-02-1442.16.pdiff [11.6 kB] Get:9 http://ftp.at.debian.org sid/main 2015-07-02-2043.11.pdiff [20.4 kB] Get:10 http://ftp.at.debian.org sid/main 2015-07-03-0245.09.pdiff [6119 B] Get:11 http://ftp.at.debian.org sid/main 2015-07-03-0843.41.pdiff [24.5 kB] Get:12 http://ftp.at.debian.org sid/main 2015-07-03-1444.58.pdiff [13.1 kB] Get:13 http://ftp.at.debian.org sid/main 2015-07-03-2044.28.pdiff [10.5 kB] Get:14 http://ftp.at.debian.org sid/main 2015-07-04-0246.30.pdiff [7778 B] Get:15 http://ftp.at.debian.org sid/main 2015-07-04-0845.59.pdiff [5651 B] Get:16 http://ftp.at.debian.org sid/main 2015-07-04-1446.01.pdiff [4838 B] Get:17 http://ftp.at.debian.org sid/main 2015-07-04-2045.12.pdiff [14.4 kB] Get:18 http://ftp.at.debian.org sid/main 2015-07-05-0244.24.pdiff [14.9 kB] Get:19 http://ftp.at.debian.org sid/main 2015-07-05-0844.23.pdiff [4527 B] Get:20 http://ftp.at.debian.org sid/main 2015-07-05-1446.24.pdiff [5631 B] Get:21 http://ftp.at.debian.org sid/main 2015-07-05-2043.54.pdiff [17.5 kB] Get:22 http://ftp.at.debian.org sid/main 2015-07-06-0248.36.pdiff [6837 B] Get:23 http://ftp.at.debian.org sid/main 2015-07-06-0845.38.pdiff [4425 B] Get:24 http://ftp.at.debian.org sid/main 2015-07-06-1445.53.pdiff [6251 B] Get:25 http://ftp.at.debian.org sid/main
Bug#795741: marked as done (libopengl-perl: FTBFS: undefined symbol: glResizeBuffersMESA)
Your message dated Tue, 25 Aug 2015 19:49:36 + with message-id e1zukdw-0007sg...@franck.debian.org and subject line Bug#795741: fixed in libopengl-perl 0.6704+dfsg-2 has caused the Debian Bug report #795741, regarding libopengl-perl: FTBFS: undefined symbol: glResizeBuffersMESA 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 ow...@bugs.debian.org immediately.) -- 795741: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=795741 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: libopengl-perl Version: 0.6704+dfsg-1 Severity: serious X-Debbugs-Cc: libgl1-mesa-...@packages.debian.org As noticed by the reproducible builds CI setup, this package fails to build on current sid. # Failed test 'require OpenGL;' # at t/00_require.t line 3. # Tried to require 'OpenGL'. # Error: Can't load '/«BUILDDIR»/libopengl-perl-0.6704+dfsg/blib/arch/auto/OpenGL/OpenGL.so' for module OpenGL: /«BUILDDIR»/libopengl-perl-0.6704+dfsg/blib/arch/auto/OpenGL/OpenGL.so: undefined symbol: glResizeBuffersMESA at /usr/lib/x86_64-linux-gnu/perl/5.20/DynaLoader.pm line 187. It looks like mesa 10.6 dropped a bunch of symbols without changing the SONAME. Copying the maintainer. Was this an intentional ABI break? On current sid, without rebuilding anything: # PERL_DL_NONLAZY=1 perl -e 'use OpenGL' Can't load '/usr/lib/x86_64-linux-gnu/perl5/5.20/auto/OpenGL/OpenGL.so' for module OpenGL: /usr/lib/x86_64-linux-gnu/perl5/5.20/auto/OpenGL/OpenGL.so: undefined symbol: glResizeBuffersMESA at /usr/lib/x86_64-linux-gnu/perl/5.20/DynaLoader.pm line 187. This is also http://sourceforge.net/p/pogl/bugs/21/ https://bugzilla.redhat.com/show_bug.cgi?id=1224294 which have the attached patch that deletes references to the removed symbols. Even with that applied, I suppose at least some Breaks entries would be in order? -- Niko Tyni nt...@debian.org From e83b9048c43cbcbdaeb287dd571ab7e277e19979 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Petr=20P=C3=ADsa=C5=99?= ppi...@redhat.com Date: Mon, 8 Jun 2015 17:06:52 +0200 Subject: [PATCH] Delete functions removed from Mesa MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit mesa-libGL between 10.6.0-0.devel.5.51e3453 and 10.6.0-0.devel.6.5a55f68 removed these functions: glWindowPos4dMESA glWindowPos4iMESA glWindowPos3iMESA glWindowPos2dMESA glWindowPos2iMESA glWindowPos3dMESA glResizeBuffersMESA https://bugzilla.redhat.com/show_bug.cgi?id=1224738 https://bugzilla.redhat.com/show_bug.cgi?id=1224294 Signed-off-by: Petr Písař ppi...@redhat.com --- pogl_gl_Vert_Multi.xs | 54 --- 1 file changed, 54 deletions(-) diff --git a/pogl_gl_Vert_Multi.xs b/pogl_gl_Vert_Multi.xs index e360e5c..4e8a010 100644 --- a/pogl_gl_Vert_Multi.xs +++ b/pogl_gl_Vert_Multi.xs @@ -359,60 +359,6 @@ glEdgeFlagPointerEXT_oga(oga) #endif -#ifdef GL_MESA_window_pos - -#// glWindowPos2iMESA($x, $y); -void -glWindowPos2iMESA(x, y) - GLint x - GLint y - -#// glWindowPos2dMESA($x, $y); -void -glWindowPos2dMESA(x, y) - GLdoublex - GLdoubley - -#// glWindowPos3iMESA($x, $y, $z); -void -glWindowPos3iMESA(x, y, z) - GLint x - GLint y - GLint z - -#// glWindowPos3dMESA($x, $y, $z); -void -glWindowPos3dMESA(x, y, z) - GLdoublex - GLdoubley - GLdoublez - -#// glWindowPos4iMESA($x, $y, $z, $w); -void -glWindowPos4iMESA(x, y, z, w) - GLint x - GLint y - GLint z - GLint w - -#// glWindowPos4dMESA($x, $y, $z, $w); -void -glWindowPos4dMESA(x, y, z, w) - GLdoublex - GLdoubley - GLdoublez - GLdoublew - -#endif - -#ifdef GL_MESA_resize_buffers - -#// glResizeBuffersMESA(); -void -glResizeBuffersMESA() - -#endif - #ifdef GL_ARB_draw_buffers #//# glDrawBuffersARB_c($n,(CPTR)buffers); -- 2.1.0 ---End Message--- ---BeginMessage--- Source: libopengl-perl Source-Version: 0.6704+dfsg-2 We believe that the bug you reported is fixed in the latest version of libopengl-perl, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 795...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Niko Tyni nt...@debian.org (supplier of updated libopengl-perl package) (This message was generated
Bug#796917: snappy1.0.3-java: dependency on libsnappy1
Source: snappy1.0.3-java Version: 1.0.3-rc3~dfsg-5 Severity: serious libsnappy1 is being replaced by libsnappy1v5. Your arch:all package has a hardcoded dependency on the former (how does that even work?). Cheers, Julien signature.asc Description: Digital signature
