Processed: Re: Bug#767999: base-files: fails to install with pre-jessie debootstrap
Processing control commands: reassign -1 base-passwd Bug #767999 [dpkg] dpkg: Correct fix breaks bogus assumptions in old debootstrap Bug reassigned from package 'dpkg' to 'base-passwd'. No longer marked as found in versions dpkg/1.17.21 and dpkg/1.17.20. Ignoring request to alter fixed versions of bug #767999 to the same values previously set retitle -1 makes base-files fail to install during bootstrap Bug #767999 [base-passwd] dpkg: Correct fix breaks bogus assumptions in old debootstrap Changed Bug title to 'makes base-files fail to install during bootstrap' from 'dpkg: Correct fix breaks bogus assumptions in old debootstrap' found -1 3.5.36 Bug #767999 [base-passwd] makes base-files fail to install during bootstrap Marked as found in versions base-passwd/3.5.36. fixed -1 3.5.37 Bug #767999 [base-passwd] makes base-files fail to install during bootstrap Marked as fixed in versions base-passwd/3.5.37. -- 767999: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=767999 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#768533: ImportError: cannot import name HTTPSConnection
Package: reportbug Version: 6.6.0 Severity: grave $ reportbug --template apt-show-versions Traceback (most recent call last): File /usr/bin/reportbug, line 38, in module from reportbug import utils File /usr/lib/python2.7/dist-packages/reportbug/utils.py, line 70, in module import debbugs File /usr/lib/python2.7/dist-packages/reportbug/debbugs.py, line 40, in module import debianbts File /usr/lib/pymodules/python2.7/debianbts.py, line 33, in module import SOAPpy File /usr/lib/python2.7/dist-packages/SOAPpy/__init__.py, line 5, in module from Client import * File /usr/lib/python2.7/dist-packages/SOAPpy/Client.py, line 59, in module from Parser import parseSOAPRPC File /usr/lib/python2.7/dist-packages/SOAPpy/Parser.py, line 10, in module from wstools.XMLname import fromXMLname File /usr/lib/python2.7/dist-packages/wstools/__init__.py, line 6, in module import WSDLTools File /usr/lib/python2.7/dist-packages/wstools/WSDLTools.py, line 15, in module from Utility import Collection, CollectionNS, DOM, ElementProxy, basejoin File /usr/lib/python2.7/dist-packages/wstools/Utility.py, line 30, in module from httplib import HTTPConnection, HTTPSConnection ImportError: cannot import name HTTPSConnection -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#768535: reportbug : Cannot import name HTTPSConnection
Package: reportbug Version: 6.6.0 Severity: grave Hi, reportbug cannot be launch. It show a stacktrace : Traceback (most recent call last): File /usr/bin/reportbug, line 38, in module from reportbug import utils File /usr/lib/python2.7/dist-packages/reportbug/utils.py, line 70, in module import debbugs File /usr/lib/python2.7/dist-packages/reportbug/debbugs.py, line 40, in module import debianbts File /usr/lib/pymodules/python2.7/debianbts.py, line 33, in module import SOAPpy File /usr/lib/python2.7/dist-packages/SOAPpy/__init__.py, line 5, in module from Client import * File /usr/lib/python2.7/dist-packages/SOAPpy/Client.py, line 59, in module from Parser import parseSOAPRPC File /usr/lib/python2.7/dist-packages/SOAPpy/Parser.py, line 10, in module from wstools.XMLname import fromXMLname File /usr/lib/python2.7/dist-packages/wstools/__init__.py, line 6, in module import WSDLTools File /usr/lib/python2.7/dist-packages/wstools/WSDLTools.py, line 15, in module from Utility import Collection, CollectionNS, DOM, ElementProxy, basejoin File /usr/lib/python2.7/dist-packages/wstools/Utility.py, line 30, in module from httplib import HTTPConnection, HTTPSConnection ImportError: cannot import name HTTPSConnection == Additional information : dpkg --list reportbug Desired=Unknown/Install/Remove/Purge/Hold | Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend |/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad) ||/ NameVersionArchitecture Description +++-===-==-==-=== ii reportbug 6.6.0 all reports bugs in the Debian distribution dpkg --status reportbug Package: reportbug Status: install ok installed Priority: standard Section: utils Installed-Size: 222 Maintainer: Reportbug Maintainers reportbug-ma...@lists.alioth.debian.org Architecture: all Version: 6.6.0 Depends: python, python:any (= 2.6~), apt, python-reportbug (= 6.6.0) Suggests: postfix | exim4 | mail-transport-agent, gnupg | pgp, debconf-utils ( 1.1.0), debsums (= 2.0.47), file ( 1.30), dlocate, python-urwid, python-gtk2, python-vte, python-gtkspell, xdg-utils, emacs23-bin-common | emacs24-bin-common, claws-mail (= 3.8.0) Conffiles: /etc/reportbug.conf 17b8e0850fa74d18b96ce5856321de0d Description: reports bugs in the Debian distribution reportbug is a tool designed to make the reporting of bugs in Debian and derived distributions relatively painless. Its features include: . * Integration with mutt and mh/nmh mail readers. * Access to outstanding bug reports to make it easier to identify whether problems have already been reported. * Automatic checking for newer versions of packages. * Optional automatic verification of integrity of packages via debsums. * Support for following-up on outstanding reports. * Optional PGP/GnuPG integration. . reportbug is designed to be used on systems with an installed mail transport agent, like exim or sendmail; however, you can edit the configuration file and send reports using any available mail server. . This package also includes the querybts script for browsing the Debian bug tracking system. Homepage: http://alioth.debian.org/projects/reportbug/ signature.asc Description: This is a digitally signed message part
Bug#767999: base-files: fails to install with pre-jessie debootstrap
Control: reassign -1 base-passwd Control: retitle -1 makes base-files fail to install during bootstrap Control: found -1 3.5.36 Control: fixed -1 3.5.37 On Fri, Nov 07, 2014 at 07:47:42PM +, Michael Tautschnig wrote: First of all thanks to everyone for the efforts to fix these problems. It seems we've now got fixes in place both in (c)debootstrap and base-passwd, so hopefully we're fine for the next few releases... :-) So we're done. This is not a bug in dpkg, so it has no purpose staying assigned there. Changed debootstrap already migrated to testing, so let's mark the fixed version of base-passwd to make sure the fix gets to jessie. Meow! -- // If you believe in so-called intellectual property, please immediately // cease using counterfeit alphabets. Instead, contact the nearest temple // of Amon, whose priests will provide you with scribal services for all // your writing needs, for Reasonable and Non-Discriminatory prices. -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#768149: [Pkg-ime-devel] ibus-table-extraphrase: RC, remove this? (Chinese related data)
Please go ahead with the rebuild or just request a binNMU. Thanks! Aron -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed (with 5 errors): your mail
Processing commands for cont...@bugs.debian.org: severity 768522 serious Bug #768522 [libcurl3] libcurl3 (version 7.38.0-3) relocation error Severity set to 'serious' from 'important' Hi dear maintainer, Unknown command or malformed arguments to command. sorry for making this bug serious, but I honestly feel that breaking reverse Unknown command or malformed arguments to command. dependencies after the freeze shouldn't be allowed. Unknown command or malformed arguments to command. Since of the urgency high, and the unblock agreeded I'm bumping the severity Unknown command or malformed arguments to command. just to be sure we can find a fix prior to break testing packages, Unknown command or malformed arguments to command. Too many unknown commands, stopping here. Please contact me if you need assistance. -- 768522: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=768522 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#768266: marked as done (libmyproxy-doc: unhandled symlink to directory conversion: /usr/share/doc/PACKAGE)
Your message dated Sat, 08 Nov 2014 06:19:13 + with message-id e1xmzmf-0007xq...@franck.debian.org and subject line Bug#768266: fixed in myproxy 6.0-2 has caused the Debian Bug report #768266, regarding libmyproxy-doc: unhandled symlink to directory conversion: /usr/share/doc/PACKAGE 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.) -- 768266: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=768266 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: libmyproxy-doc Version: 6.0-1 Severity: serious User: debian...@lists.debian.org Usertags: piuparts Hi, an upgrade test with piuparts revealed that your package installs files over existing symlinks and possibly overwrites files owned by other packages. This usually means an old version of the package shipped a symlink but that was later replaced by a real (and non-empty) directory. This kind of overwriting another package's files cannot be detected by dpkg. This was observed on the following upgrade paths: wheezy jessie For /usr/share/doc/PACKAGE this may not be problematic as long as both packages are installed, ship byte-for-byte identical files and are upgraded in lockstep. But once one of the involved packages gets removed, the other one will lose its documentation files, too, including the copyright file, which is a violation of Policy 12.5: http://www.debian.org/doc/debian-policy/ch-docs.html#s-copyrightfile For other overwritten locations anything interesting may happen. Note that dpkg intentionally does not replace directories with symlinks and vice versa, you need the maintainer scripts to do this. See in particular the end of point 4 in http://www.debian.org/doc/debian-policy/ch-maintainerscripts.html#s-unpackphase It is recommended to use the dpkg-maintscript-helper commands 'dir_to_symlink' and 'symlink_to_dir' (available since dpkg 1.17.2) to perform the conversion, ideally using d/$PACKAGE.mainstscript. See dpkg-maintscript-helper(1) and dh_installdeb(1) for details. From the attached log (usually somewhere in the middle...): 1m28.2s ERROR: FAIL: silently overwrites files via directory symlinks: /usr/share/doc/libmyproxy-doc/changelog.Debian.gz (libmyproxy-doc) != /usr/share/doc/libmyproxy-dev/changelog.Debian.gz (libmyproxy-dev:amd64) /usr/share/doc/libmyproxy-doc/copyright (libmyproxy-doc) != /usr/share/doc/libmyproxy-dev/copyright (libmyproxy-dev:amd64) cheers, Andreas libmyproxy-doc_6.0-1.log.gz Description: application/gzip ---End Message--- ---BeginMessage--- Source: myproxy Source-Version: 6.0-2 We believe that the bug you reported is fixed in the latest version of myproxy, 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 768...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Mattias Ellert mattias.ell...@fysast.uu.se (supplier of updated myproxy 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: Fri, 07 Nov 2014 23:51:15 +0100 Source: myproxy Binary: myproxy libmyproxy6 libmyproxy-dev myproxy-server myproxy-admin libmyproxy-doc libmyproxy-dbg myproxy-dbg Architecture: source amd64 all Version: 6.0-2 Distribution: unstable Urgency: medium Maintainer: Mattias Ellert mattias.ell...@fysast.uu.se Changed-By: Mattias Ellert mattias.ell...@fysast.uu.se Description: libmyproxy-dbg - Credential Management Service Debug Symbols libmyproxy-dev - Credential Management Service Development libmyproxy-doc - Credential Management Service Documentation libmyproxy6 - Credential Management Service Library myproxy- Credential Management Service Client myproxy-admin - Credential Management Service Administration Tools myproxy-dbg - Credential Management Service Debug Symbols myproxy-server - Credential Management Service Server Closes: 768266 Changes: myproxy (6.0-2) unstable; urgency=medium . * Properly handle symlink-to-dir conversion in doc package (Closes: #768266) * Enable TLS - debian's openssl has disabled SSLv3 by default Checksums-Sha1: f4accbe22b8aa2ccb87e6a0d607e3daa295289fb 2703 myproxy_6.0-2.dsc 18d18f5d291cade110721adf95a426854657d014 9860 myproxy_6.0-2.debian.tar.xz
Bug#768276: marked as done (voms-doc: unhandled symlink to directory conversion: /usr/share/doc/PACKAGE)
Your message dated Sat, 08 Nov 2014 07:48:49 + with message-id e1xn0ln-0003zc...@franck.debian.org and subject line Bug#768276: fixed in voms 2.0.11-4 has caused the Debian Bug report #768276, regarding voms-doc: unhandled symlink to directory conversion: /usr/share/doc/PACKAGE 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.) -- 768276: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=768276 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: voms-doc Version: 2.0.11-3 Severity: serious User: debian...@lists.debian.org Usertags: piuparts Hi, an upgrade test with piuparts revealed that your package installs files over existing symlinks and possibly overwrites files owned by other packages. This usually means an old version of the package shipped a symlink but that was later replaced by a real (and non-empty) directory. This kind of overwriting another package's files cannot be detected by dpkg. This was observed on the following upgrade paths: wheezy - jessie For /usr/share/doc/PACKAGE this may not be problematic as long as both packages are installed, ship byte-for-byte identical files and are upgraded in lockstep. But once one of the involved packages gets removed, the other one will lose its documentation files, too, including the copyright file, which is a violation of Policy 12.5: http://www.debian.org/doc/debian-policy/ch-docs.html#s-copyrightfile For other overwritten locations anything interesting may happen. Note that dpkg intentionally does not replace directories with symlinks and vice versa, you need the maintainer scripts to do this. See in particular the end of point 4 in http://www.debian.org/doc/debian-policy/ch-maintainerscripts.html#s-unpackphase It is recommended to use the dpkg-maintscript-helper commands 'dir_to_symlink' and 'symlink_to_dir' (available since dpkg 1.17.2) to perform the conversion, ideally using d/$PACKAGE.mainstscript. See dpkg-maintscript-helper(1) and dh_installdeb(1) for details. From the attached log (usually somewhere in the middle...): 0m56.6s ERROR: FAIL: silently overwrites files via directory symlinks: /usr/share/doc/voms-doc/changelog.Debian.gz (voms-doc) != /usr/share/doc/voms-dev/changelog.Debian.gz (voms-dev) /usr/share/doc/voms-doc/changelog.gz (voms-doc) != /usr/share/doc/voms-dev/changelog.gz (voms-dev) /usr/share/doc/voms-doc/copyright (voms-doc) != /usr/share/doc/voms-dev/copyright (voms-dev) cheers, Andreas voms-doc_2.0.11-3.log.gz Description: application/gzip ---End Message--- ---BeginMessage--- Source: voms Source-Version: 2.0.11-4 We believe that the bug you reported is fixed in the latest version of voms, 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 768...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Mattias Ellert mattias.ell...@fysast.uu.se (supplier of updated voms 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: Sat, 08 Nov 2014 07:19:30 +0100 Source: voms Binary: libvomsapi1 voms-clients voms-dev voms-doc voms-server voms-dbg Architecture: source amd64 all Version: 2.0.11-4 Distribution: unstable Urgency: medium Maintainer: Mattias Ellert mattias.ell...@fysast.uu.se Changed-By: Mattias Ellert mattias.ell...@fysast.uu.se Description: libvomsapi1 - Virtual Organization Membership Service C++ API voms-clients - Virtual Organization Membership Service Clients voms-dbg - Virtual Organization Membership Service - Debug Symbols voms-dev - Virtual Organization Membership Service C++ API Development Files voms-doc - Virtual Organization Membership Service Documentation Files voms-server - Virtual Organization Membership Service Server Closes: 768276 Changes: voms (2.0.11-4) unstable; urgency=medium . * Properly handle symlink-to-dir conversion in doc package (Closes: #768276) Checksums-Sha1: 135863172e70fc6f1ea7760e7bf3fdb706a12c9b 2239 voms_2.0.11-4.dsc 574b8c198f987f9b38a4c7fbbaf56092e855a77a 9176 voms_2.0.11-4.debian.tar.xz b8dc1a26dfeb0786f871011407b55a9cf55f0a22 152054 libvomsapi1_2.0.11-4_amd64.deb 43a768015ef2d4521dc448931f6f369a46b3df53 122926
Processed: Re: [gprbuild] GFDL non free file with front cover
Processing control commands:
reopen -1 !
Bug #708942 {Done: Nicolas Boulenguez nico...@debian.org} [gprbuild]
[gprbuild] GFDL non free file with front cover
'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
Changed Bug submitter to 'Nicolas Boulenguez nico...@debian.org' from
'bastien ROUCARIES roucaries.bast...@gmail.com'
No longer marked as fixed in versions gprbuild/2011-4.
--
708942: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=708942
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#708942: [gprbuild] GFDL non free file with front cover
Source: gprbuild Followup-For: Bug #708942 Control: reopen -1 ! A recent clarification [1] by upstream authors makes it explicit that the documentation *is* licensed under the GFDL with invariant sections, and must be removed from Debian. [1] https://lists.debian.org/debian-ada/2014/10/msg00023.html -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#768476: As it also break reportbug filling bug is complicated;-)
I found cmake was broken because curl was broken and discovered this bug. Trying to report the bug reportbug itself was broken! File /usr/lib/python2.7/dist-packages/wstools/Utility.py, line 30, in module from httplib import HTTPConnection, HTTPSConnection ImportError: cannot import name HTTPSConnection So please put a conflicts with libcurl at least to avoid upgrading! -- eric -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#732300: info
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 With up-to-date jessie I can reproduce this issue with following commands. I think input device is correct, but not sure. If I run cat /dev/input/eventX I can see data in the terminal when I type something, but it is not the text I was writing. 1) logkeys --export-keymap=keymap.txt logkeys --start --keymap=keymap --output=output.txt echo abcdefghijklmnopqrstuvwxyz logkeys --kill 2) logkeys --start --output=output.txt echo abcdefghijklmnopqrstuvwxyz logkeys --kill - --- Henri Salo -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.12 (GNU/Linux) iEYEARECAAYFAlRd5fMACgkQXf6hBi6kbk+MKwCfSu0W+ftSvAjlRpUaJSLqPs1/ MHAAn3Mrq0vxgtzLzg+5LekpeZ3egG38 =+Ba4 -END PGP SIGNATURE- -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed: jessie
Processing commands for cont...@bugs.debian.org:
tags 768149 + sid jessie
Bug #768149 [ibus-table-extraphrase] ibus-table-extraphrase: Need to be rebuild
with ibus-table 1.9.1
Added tag(s) sid and jessie.
tags 768522 + sid jessie
Bug #768522 [libcurl3] libcurl3 (version 7.38.0-3) relocation error
Added tag(s) sid and jessie.
tags 767832 + sid jessie
Bug #767832 [initramfs-tools] Initramfs provided in initramfs-tools_0.118_all
won’t automount luks partitions at boot
Added tag(s) sid and jessie.
tags 768011 + sid jessie
Bug #768011 {Done: Andreas Tille ti...@debian.org} [blends-dev] blends-dev:
Dependencies from non-free or unstable can be included by accident
Added tag(s) sid and jessie.
tags 767379 + sid jessie
Bug #767379 {Done: Scott Howard showard...@gmail.com} [src:eagle]
libjpeg62-turbo provides libjpeg62, but no version for it
Added tag(s) sid and jessie.
tags 761210 + sid jessie
Bug #761210 {Done: Hideki Yamane henr...@debian.org} [g-wrap] g-wrap: please
migrate to guile-2.0
Added tag(s) sid and jessie.
tags 767554 + sid jessie
Bug #767554 [python-persistent,python-zodb] python-persistent and python-zodb:
error when trying to install together
Added tag(s) sid and jessie.
tags 767559 + sid jessie
Bug #767559 [geoip-database-contrib] geoip-database-extra,
geoip-database-contrib: error when trying to install together
Added tag(s) sid and jessie.
tags 767675 + sid jessie
Bug #767675 [libx52pro0] libx52pro0: fails to install: subprocess installed
post-installation script returned error exit status 2
Added tag(s) sid and jessie.
#767675: it installs fine on wheezy, but not on jessie+sid despite having the
same version...
End of message, stopping processing here.
Please contact me if you need assistance.
--
761210: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=761210
767379: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=767379
767554: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=767554
767559: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=767559
767675: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=767675
767832: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=767832
768011: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=768011
768149: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=768149
768522: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=768522
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#768543: ImportError: /usr/lib/python2.7/lib-dynload/_ssl.i386-linux-gnu.so: symbol SSLv3_method, version OPENSSL_1.0.0 not defined in file libssl.so.1.0.0 with link time reference
Package: libpython2.7
Severity: grave
Version: 2.7.8-11
$ youtube-dl --version
Traceback (most recent call last):
File /usr/bin/youtube-dl, line 9, in module
load_entry_point('youtube-dl==2014.10.30', 'console_scripts',
'youtube-dl')()
File /usr/lib/python2.7/dist-packages/pkg_resources.py, line 356, in
load_entry_point
return get_distribution(dist).load_entry_point(group, name)
File /usr/lib/python2.7/dist-packages/pkg_resources.py, line 2476, in
load_entry_point
return ep.load()
File /usr/lib/python2.7/dist-packages/pkg_resources.py, line 2190, in load
['__name__'])
File /usr/lib/python2.7/dist-packages/youtube_dl/__init__.py, line 13, in
module
from .options import (
File /usr/lib/python2.7/dist-packages/youtube_dl/options.py, line 8, in
module
from .utils import (
File /usr/lib/python2.7/dist-packages/youtube_dl/utils.py, line 22, in
module
import ssl
File /usr/lib/python2.7/ssl.py, line 97, in module
import _ssl # if we can't import it, let the error propagate
ImportError: /usr/lib/python2.7/lib-dynload/_ssl.i386-linux-gnu.so: symbol
SSLv3_method, version OPENSSL_1.0.0 not defined in file libssl.so.1.0.0 with
link time reference
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed: merging 768533 768535
Processing commands for cont...@bugs.debian.org: merge 768533 768535 Bug #768533 [reportbug] ImportError: cannot import name HTTPSConnection Bug #768535 [reportbug] reportbug : Cannot import name HTTPSConnection Merged 768533 768535 thanks Stopping processing here. Please contact me if you need assistance. -- 768533: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=768533 768535: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=768535 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed: Re: Bug#768112: fixed in slurm-llnl 14.03.9-4
Processing control commands:
reopen -1
Bug #768112 {Done: Gennaro Oliva oliv...@na.icar.cnr.it} [slurm-client]
slurm-client: fails to upgrade from 'wheezy' - trying to overwrite
/usr/bin/sinfo
'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 slurm-llnl/14.03.9-4.
--
768112: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=768112
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#768112: fixed in slurm-llnl 14.03.9-4
Control: reopen -1 On 2014-11-06 10:21, Gennaro Oliva wrote: Source: slurm-llnl Source-Version: 14.03.9-4 We believe that the bug you reported is fixed in the latest version of slurm-llnl, which is due to be installed in the Debian FTP archive. [...] slurm-llnl (14.03.9-4) unstable; urgency=medium . * Declaring slurm-client conflict with sinfo (Closes: #768112) No. Please re-read policy (specifically 10.1) - you don't get to conflict with other packages just because you both want to use the same file path. Regards, Adam -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#768543: ImportError: /usr/lib/python2.7/lib-dynload/_ssl.i386-linux-gnu.so: symbol SSLv3_method, version OPENSSL_1.0.0 not defined in file libssl.so.1.0.0 with link time reference
Control: tags -1 moreinfo unreproducible
On Sat, 08 Nov 2014 17:48:28 +0800 =?utf-8?B?56mN5Li55bC8?= Dan Jacobson
jida...@jidanni.org wrote:
Package: libpython2.7
Severity: grave
Version: 2.7.8-11
$ youtube-dl --version
Traceback (most recent call last):
File /usr/bin/youtube-dl, line 9, in module
load_entry_point('youtube-dl==2014.10.30', 'console_scripts',
'youtube-dl')()
File /usr/lib/python2.7/dist-packages/pkg_resources.py, line 356, in
load_entry_point
return get_distribution(dist).load_entry_point(group, name)
File /usr/lib/python2.7/dist-packages/pkg_resources.py, line 2476, in
load_entry_point
return ep.load()
File /usr/lib/python2.7/dist-packages/pkg_resources.py, line 2190, in load
['__name__'])
File /usr/lib/python2.7/dist-packages/youtube_dl/__init__.py, line 13, in
module
from .options import (
File /usr/lib/python2.7/dist-packages/youtube_dl/options.py, line 8, in
module
from .utils import (
File /usr/lib/python2.7/dist-packages/youtube_dl/utils.py, line 22, in
module
import ssl
File /usr/lib/python2.7/ssl.py, line 97, in module
import _ssl # if we can't import it, let the error propagate
ImportError: /usr/lib/python2.7/lib-dynload/_ssl.i386-linux-gnu.so: symbol
SSLv3_method, version OPENSSL_1.0.0 not defined in file libssl.so.1.0.0 with
link time reference
Hi,
I cannot reproduce this; what version of openssl do you have installed?
If it is the version in experimental, then that is probably the reason
for your issue (but it does not affect sid nor testing).
~Niels
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed: Re: ImportError: /usr/lib/python2.7/lib-dynload/_ssl.i386-linux-gnu.so: symbol SSLv3_method, version OPENSSL_1.0.0 not defined in file libssl.so.1.0.0 with link time reference
Processing control commands: tags -1 moreinfo unreproducible Bug #768543 [libpython2.7] ImportError: /usr/lib/python2.7/lib-dynload/_ssl.i386-linux-gnu.so: symbol SSLv3_method, version OPENSSL_1.0.0 not defined in file libssl.so.1.0.0 with link time reference Added tag(s) unreproducible and moreinfo. -- 768543: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=768543 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed: severity of 768543 is important
Processing commands for cont...@bugs.debian.org: severity 768543 important Bug #768543 [libpython2.7] ImportError: /usr/lib/python2.7/lib-dynload/_ssl.i386-linux-gnu.so: symbol SSLv3_method, version OPENSSL_1.0.0 not defined in file libssl.so.1.0.0 with link time reference Severity set to 'important' from 'grave' thanks Stopping processing here. Please contact me if you need assistance. -- 768543: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=768543 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#768547: gnat-gps-doc: wrong license for user guide (GPL instead of GFDL)
Package: gnat-gps-doc Severity: serious Justification: license issue The file docs/users_guide/license.rst in the pristine upstream tarball contains the GFDL. It is included by docs/users_guide/index.rst, which mentions no invariant parts or cover texts, so the documentation complies to the DFSG. However.. Upstream authors used to claim that all the whole archive was licensed under the GPL, though some obsolete boilerplates were telling a different story. The Debian .orig archive used to be repackaged to clarify this issue. A recent statement [1] by upstream authors makes it explicit that the documentation *is* licensed under the GFDL. [1] https://lists.debian.org/debian-ada/2014/10/msg00023.html It seems that gnat-gps must be repackaged again with the correct licensing. Maybe this is the opportunity to also remove the embedded copy of libgnatcoll lying in the gnatlib/ subdirectory (see debian/TODO). -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#768522: libcurl3 (version 7.38.0-3) relocation error
Control: tags -1 + moreinfo Control: found -1 7.38.0-3 On 2014-11-08 2:12, Jos van Wolput wrote: After upgrading libcurl3 from version 7.38.0-2 to 7.38.0-3 boinc-client (dep: libcurl3) is no longer running because of the following error in libcurl3: --- relocation error: /usr/lib/x86_64-linux-gnu/libcurl.so.4: symbol SSLv3_client_method, version OPENSSL_1.0.0 not defined in file libssl.so.1.0.0 with link time reference --- Reverting libcurl3 to version 7.38.0-2 (testing) fixes this issue. Given: -- System Information: Debian Release: jessie/sid + experimental which version of libssl1.0.0 do you have installed? If it's 1.0.2 from experimental, does downgrading to unstable's version help? Regards, Adam -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed: Re: libcurl3 (version 7.38.0-3) relocation error
Processing control commands: tags -1 + moreinfo Bug #768522 [libcurl3] libcurl3 (version 7.38.0-3) relocation error Added tag(s) moreinfo. found -1 7.38.0-3 Bug #768522 [libcurl3] libcurl3 (version 7.38.0-3) relocation error Marked as found in versions curl/7.38.0-3. -- 768522: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=768522 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed: Re: Bug#768509: debian-edu-config: After upgrading a Wheezy main-server to Debian 7.7 the Gosa gui fails to connect to LDAP
Processing control commands: severity -1 serious Bug #768509 [debian-edu-config] debian-edu-config: After upgrading a Wheezy main-server to Debian 7.7 the Gosa gui fails to connect to LDAP Severity set to 'serious' from 'important' notfound -1 1.813 Bug #768509 [debian-edu-config] debian-edu-config: After upgrading a Wheezy main-server to Debian 7.7 the Gosa gui fails to connect to LDAP Ignoring request to alter found versions of bug #768509 to the same values previously set -- 768509: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=768509 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#765722: CVE-2014-3660 libxml2 billion laugh variant
Hi,
I looked at this bug (kind-of randomly looking through RC bugs).
The current status is:
- fixed in unstable with a new upstream version
- that new upstream version was aged/2
- however, an RC bug (#766884) was found in that new upstream version
- in the upstream bug[1] for #766884, the upstream author says
'it's not gonna be simple :-('
:-(
A good strategy is probably to see if the upstream bug get fixed soon,
migrate the fixed new upstream if that's the case, and issue a targetted
fix for #765722 if that's not the case.
However, maybe the release team prefers a targetted fix anyway?
(I did not really understand if the fix for #765722 is related to the
introduction of #766884. But I believe they are independant)
[1] https://bugzilla.gnome.org/show_bug.cgi?id=737840
Lucas
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed: tagging 767850
Processing commands for cont...@bugs.debian.org: tags 767850 + pending Bug #767850 [apache2] apache2: unhandled symlink to directory conversion: /usr/share/doc/apache2 Added tag(s) pending. thanks Stopping processing here. Please contact me if you need assistance. -- 767850: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=767850 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#767850: apache2: unhandled symlink to directory conversion: /usr/share/doc/apache2
Thanks for the report. The doc symlinks will be fixed in the next upload. But the errors about conf files seem to be false positives. The upgraded apache2.2-common package does not contain any of those files anymore. Therefore it is correct that they are missing. On Sunday 02 November 2014 23:55:11, Andreas Beckmann wrote: And there are more problems but I didn't have time to look at them in detail: 1m36.2s ERROR: FAIL: debsums reports modifications inside the chroot: debsums: missing file /etc/apache2/mods-available/imagemap.load (from apache2.2-common package) debsums: missing file /etc/apache2/mods-available/cern_meta.load (from apache2.2-common package) debsums: missing file /etc/apache2/mods-available/authz_default.load (from apache2.2-common package) debsums: missing file /etc/apache2/sites-available/default-ssl (from apache2.2-common package) debsums: missing file /etc/apache2/mods-available/disk_cache.load (from apache2.2-common package) debsums: missing file /etc/apache2/mods-available/disk_cache.conf (from apache2.2-common package) debsums: missing file /etc/apache2/conf.d/charset (from apache2.2-common package) debsums: missing file /etc/apache2/sites-available/default (from apache2.2-common package) debsums: missing file /etc/apache2/mods-available/authn_default.load (from apache2.2-common package) debsums: missing file /etc/bash_completion.d/apache2.2-common (from apache2.2-common package) debsums: missing file /etc/apache2/conf.d/security (from apache2.2-common package) debsums: missing file /etc/apache2/conf.d/other-vhosts-access-log (from apache2.2-common package) debsums: missing file /etc/apache2/mods-available/mem_cache.conf (from apache2.2-common package) debsums: missing file /etc/apache2/mods-available/authn_alias.load (from apache2.2-common package) debsums: missing file /etc/apache2/mods-available/mem_cache.load (from apache2.2-common package) debsums: missing file /etc/apache2/conf.d/localized-error-pages (from apache2.2-common package) -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#768522: libcurl3 (version 7.38.0-3) relocation error
On 11/08/2014 06:24 PM, Adam D. Barratt wrote: Given: -- System Information: Debian Release: jessie/sid + experimental which version of libssl1.0.0 do you have installed? If it's 1.0.2 from experimental, does downgrading to unstable's version help? I did have installed libssl1.0.0 version 1.0.2~beta3-1 from experimental, downgrading to 1.0.1j-1 (unstable) and installing libcurl3 (version 7.38.0-3) fixes this issue. Thanks! Jos v.Wolput -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#768522: libcurl3 (version 7.38.0-3) relocation error
Control: forcemerge 768476 -1 Control: affects -1 + libcurl3 On 2014-11-08 11:10, Jos van Wolput wrote: On 11/08/2014 06:24 PM, Adam D. Barratt wrote: Given: -- System Information: Debian Release: jessie/sid + experimental which version of libssl1.0.0 do you have installed? If it's 1.0.2 from experimental, does downgrading to unstable's version help? I did have installed libssl1.0.0 version 1.0.2~beta3-1 from experimental, downgrading to 1.0.1j-1 (unstable) and installing libcurl3 (version 7.38.0-3) fixes this issue. Thanks for the confirmation; I'm merging this with an existing report. Regards Adam -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed (with 1 errors): Re: libcurl3 (version 7.38.0-3) relocation error
Processing control commands: forcemerge 768476 -1 Bug #768476 [openssl] openssl 1.0.2~beta3-1: relocation error in libraries depending on libssl.so Unable to merge bugs because: package of #768522 is 'libcurl3' not 'openssl' Failed to forcibly merge 768476: Did not alter merged bugs affects -1 + libcurl3 Bug #768522 [libcurl3] libcurl3 (version 7.38.0-3) relocation error Added indication that 768522 affects libcurl3 -- 768476: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=768476 768522: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=768522 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#768149: marked as done (ibus-table-extraphrase: Need to be rebuild with ibus-table 1.9.1)
Your message dated Sat, 08 Nov 2014 11:33:48 + with message-id e1xn4h6-kg...@franck.debian.org and subject line Bug#768149: fixed in ibus-table-extraphrase 1.2.0.20100305-2 has caused the Debian Bug report #768149, regarding ibus-table-extraphrase: Need to be rebuild with ibus-table 1.9.1 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.) -- 768149: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=768149 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: ibus-table-extraphrase Version: 1.2.0.20100305-1 Severity: normal Question: Is this package still useful? Now some ibus-table-* has -big data. Action required for jessie: * rebuild with new ibus-table 1.9.1 * add dependency to ibus-table (=1.9.1~) * add this to IME Packaging Team * Fix 1 data in table as in 1.3.9.20110826 Long story: Since this package was not listed in IME Packaging Team, I overlooked this one when uploading ibus-table 1.9.1. Another reason was that this package is missing dependency to ibus-table and fdid not shoow up in my search: $ apt-cache rdepends ibus-table ibus-table Reverse Depends: ibus-table-yawerty ibus-table-viqr ibus-table-translit-ua ibus-table-translit ibus-table-thai ibus-table-rustrad ibus-table-latex ibus-table-ipa-x-sampa ibus-table-emoji ibus-table-compose ibus-table-cns11643 ibus-table-yong ibus-table-wubi ibus-table-wu ibus-table-stroke5 ibus-table-scj6 ibus-table-quick5 ibus-table-quick3 ibus-table-quick-classic ibus-table-jyutping ibus-table-erbi-qs ibus-table-erbi ibus-table-easy-big ibus-table-cantonhk ibus-table-cantonese ibus-table-cangjie5 ibus-table-cangjie3 ibus-table-cangjie-big ibus-table-array30 (Thse are generated from ibus-table-chinese and ibus-table-others) ibus-table 1.9.1 requires all conversion data packages depending on ibus-table to be rebuild. That's minimum needed for this package to be usable on jessie. Also, I see new upstream release: https://code.google.com/p/ibus/downloads/list bus-table-extraphrase-1.3.9.20110826.tar.gz ibus-table-extraphrase Source Code Chinese 1.3 As I understand, some people moved repo to github, but: https://github.com/acevery/ibus-table-extraphrase https://github.com/kaio/ibus-table-extraphrase (copy of above) on Feb 19, 2009 1.1.0.20090219 … on Jan 3, 2009 0.1.2.20090102 … on Dec 7, 2008 0.1.2.20090101 … These are all older than one we have in the archive: 1.2.0.20100305-1 So, the latest is one on code.google.com 1.3.9.20110826 Let's see what have changed (in non-autogenerated files): == Single data temoval and version bump. diff -Nru ibus-table-extraphrase-1.2.0.20100305/configure.ac ibus-table-extraphrase-1.3.9.20110826/configure.ac --- ibus-table-extraphrase-1.2.0.20100305/configure.ac 2010-03-05 09:38:34.0 +0900 +++ ibus-table-extraphrase-1.3.9.20110826/configure.ac 2011-08-26 19:43:55.0 +0900 @@ -25,8 +25,8 @@ m4_define([package_name], [ibus-table-extraphrase]) m4_define([ibus_released], [0]) m4_define([ibus_major_version], [1]) -m4_define([ibus_minor_version], [2]) -m4_define([ibus_micro_version], [0]) +m4_define([ibus_minor_version], [3]) +m4_define([ibus_micro_version], [9]) m4_define(ibus_maybe_datestamp, m4_esyscmd([if test x]ibus_released[ != x1; then date +.%Y%m%d | tr -d '\n\r'; fi])) diff -Nru ibus-table-extraphrase-1.2.0.20100305/data/extra_phrase.txt ibus-table-extraphrase-1.3.9.20110826/data/extra_phrase.txt --- ibus-table-extraphrase-1.2.0.20100305/data/extra_phrase.txt 2010-01-08 11:01:37.0 +0900 +++ ibus-table-extraphrase-1.3.9.20110826/data/extra_phrase.txt 2011-08-25 07:34:24.0 +0900 @@ -302604,7 +302604,6 @@ 頭痛 1340 頭痛醫頭 39400 頭痛醫頭腳痛醫腳 84300 -頭發 593000 頭皮 320 頭皮屑269000 頭盔 893000 Considering all these, it is good idea to apply this bug fix if new upload is made. (Also add this to IME group) Osamu -- System Information: Debian Release: jessie/sid APT prefers testing-updates APT policy: (500, 'testing-updates'), (500, 'unstable'), (500, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 3.16-3-amd64 (SMP w/4 CPU cores) Locale: LANG=en_US.utf8, LC_CTYPE=en_US.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash -- no debconf information ---End Message--- ---BeginMessage--- Source: ibus-table-extraphrase Source-Version: 1.2.0.20100305-2 We believe that the bug you reported is fixed in the latest version of ibus-table-extraphrase, which is due to be installed in the Debian FTP archive. A summary of the
Processed: reassign 768522 to openssl, forcibly merging 768476 768522, affects 768522
Processing commands for cont...@bugs.debian.org: reassign 768522 openssl Bug #768522 [libcurl3] libcurl3 (version 7.38.0-3) relocation error Bug reassigned from package 'libcurl3' to 'openssl'. No longer marked as found in versions curl/7.38.0-3. Ignoring request to alter fixed versions of bug #768522 to the same values previously set forcemerge 768476 768522 Bug #768476 [openssl] openssl 1.0.2~beta3-1: relocation error in libraries depending on libssl.so Bug #768476 [openssl] openssl 1.0.2~beta3-1: relocation error in libraries depending on libssl.so Added tag(s) sid, moreinfo, and jessie. Bug #768522 [openssl] libcurl3 (version 7.38.0-3) relocation error Severity set to 'grave' from 'serious' Removed indication that 768522 affects libcurl3 Marked as found in versions openssl/1.0.2~beta3-1. Merged 768476 768522 affects 768522 + libcurl3 Bug #768522 [openssl] libcurl3 (version 7.38.0-3) relocation error Bug #768476 [openssl] openssl 1.0.2~beta3-1: relocation error in libraries depending on libssl.so Added indication that 768522 affects libcurl3 Added indication that 768476 affects libcurl3 thanks Stopping processing here. Please contact me if you need assistance. -- 768476: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=768476 768522: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=768522 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#757588: #757588: sysvinit-core: installation fails when systemd is present
I was unable to reproduce this with the current sysvinit package in jessie (2.88dsf-57). What I did: * installed wheezy in a VM * altered /etc/apt/sources.list adding jessie URLs * apt-get update * apt-get install apt dpkg locales * apt dist-upgrade * reboot At this point the system was running with systemd. * apt install sysvinit-core (nothing odd here, installation went normally) * reboot At this point the system was running with sysvinit. Sorry for not providing logs from the susvinit-core installation, I was unable to get the serial console of the VM to work. HTH, dam -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#768475: evince: segfault on trying to open a pdf
I can confirm this happens with *all* pdfs I have tried (20+). I can attach an
example if you want, but that'd just be doing a find / -name *.pdf | head -1
so I'm not sure it matters :-)
Backtrace as requested:
[alver@Crusoe ~]$ gdb evince
GNU gdb (Debian 7.7.1+dfsg-3) 7.7.1
Copyright (C) 2014 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 evince...(no debugging symbols found)...done.
(gdb) run altairz80_doc.pdf
Starting program: /usr/bin/evince altairz80_doc.pdf
[Thread debugging using libthread_db enabled]
Using host libthread_db library /lib/x86_64-linux-gnu/libthread_db.so.1.
[New Thread 0x7fffee08d700 (LWP 30810)]
[New Thread 0x7fffed88c700 (LWP 30811)]
[New Thread 0x7fffec974700 (LWP 30816)]
[New Thread 0x7fffdfd04700 (LWP 30817)]
[New Thread 0x7fffdf2e3700 (LWP 30818)]
[New Thread 0x7fffdeae2700 (LWP 30819)]
[New Thread 0x7fffde2e1700 (LWP 30820)]
[New Thread 0x7fffddae0700 (LWP 30821)]
[New Thread 0x7fffdd2df700 (LWP 30822)]
[New Thread 0x7fffdcade700 (LWP 30823)]
[New Thread 0x7fffc7fff700 (LWP 30824)]
[New Thread 0x7fffc77fe700 (LWP 30825)]
[New Thread 0x7fffc6ffd700 (LWP 30826)]
(evince:30806): EvinceDocument-WARNING **:
/usr/lib/x86_64-linux-gnu/libpoppler-glib.so.8: undefined symbol:
_ZN7GfxFont16getAlternateNameEPKc
Program received signal SIGSEGV, Segmentation fault.
[Switching to Thread 0x7fffc6ffd700 (LWP 30826)]
0x0001f576 in ?? ()
(gdb) bt full
#0 0x0001f576 in ?? ()
No symbol table info available.
#1 0x7fffc65c5637 in poppler_document_new_from_file () from
/usr/lib/x86_64-linux-gnu/libpoppler-glib.so.8
No symbol table info available.
#2 0x7fffdc0d7a2b in ?? () from
/usr/lib/evince/4/backends/libpdfdocument.so
No symbol table info available.
#3 0x77bb7ef7 in ev_document_load () from /usr/lib/libevdocument3.so.4
No symbol table info available.
#4 0x77bb9cfb in ev_document_factory_get_document () from
/usr/lib/libevdocument3.so.4
No symbol table info available.
#5 0x7796ac6d in ?? () from /usr/lib/libevview3.so.3
No symbol table info available.
#6 0x7796c1ea in ?? () from /usr/lib/libevview3.so.3
No symbol table info available.
#7 0x74df3925 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
No symbol table info available.
#8 0x746520a4 in start_thread (arg=0x7fffc6ffd700) at
pthread_create.c:309
__res = optimized out
pd = 0x7fffc6ffd700
now = optimized out
unwind_buf = {cancel_jmp_buf = {{jmp_buf = {140736532043520,
-2297013931208070973, 1, 140737354125408, 140737301657808, 140736532043520,
2297064510323173571, 2297035052063795395}, mask_was_saved =
0}}, priv = {pad = {0x0, 0x0, 0x0, 0x0}, data = {prev = 0x0,
cleanup = 0x0, canceltype = 0}}}
not_first_call = optimized out
pagesize_m1 = optimized out
sp = optimized out
freesize = optimized out
__PRETTY_FUNCTION__ = start_thread
#9 0x74387c2d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:111
No locals.
(gdb) quit
A debugging session is active.
Inferior 1 [process 30806] will be killed.
Quit anyway? (y or n) y
[alver@Crusoe ~]$ dpkg -l evince
Desired=Unknown/Install/Remove/Purge/Hold
| Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend
|/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad)
||/ NameVersion Architecture
Description
+++-===---
ii evince 3.14.1-1 amd64
Document (PostScript, PDF) viewer
signature.asc
Description: Digital signature
Processed: tagging 768522
Processing commands for cont...@bugs.debian.org: tags 768522 - moreinfo sid jessie Bug #768522 [openssl] libcurl3 (version 7.38.0-3) relocation error Bug #768476 [openssl] openssl 1.0.2~beta3-1: relocation error in libraries depending on libssl.so Removed tag(s) sid, jessie, and moreinfo. Removed tag(s) sid, jessie, and moreinfo. thanks Stopping processing here. Please contact me if you need assistance. -- 768476: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=768476 768522: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=768522 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#764792: marked as done (x11-apps: xman not rendering any pages (zsoelim: not found))
Your message dated Sat, 08 Nov 2014 12:19:08 + with message-id e1xn4yy-000689...@franck.debian.org and subject line Bug#764792: fixed in x11-apps 7.7+4 has caused the Debian Bug report #764792, regarding x11-apps: xman not rendering any pages (zsoelim: not found) 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.) -- 764792: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=764792 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: x11-apps Version: 7.7+3 Severity: important Dear Maintainer, I was trying out xman on my jessie system, and it turns out it won't render any pages at all. I notice that when I start xman from a terminal, I see sh: 1: zsoelim: not found in the terminal when I tell it to load a man page. Some checking shows that zsoelim was in man-db in wheezy, but that no longer seems to be the case with man-db in jessie on AMD64. -- System Information: Debian Release: jessie/sid APT prefers testing-updates APT policy: (500, 'testing-updates'), (500, 'testing') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.16-2-amd64 (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 Versions of packages x11-apps depends on: ii cpp 4:4.9.1-1 ii libc62.19-11 ii libpng12-0 1.2.50-2 ii libsm6 2:1.2.2-1 ii libx11-6 2:1.6.2-3 ii libxaw7 2:1.0.12-2 ii libxcursor1 1:1.1.14-1 ii libxext6 2:1.3.2-1 ii libxft2 2.3.2-1 ii libxkbfile1 1:1.0.8-1 ii libxmu6 2:1.1.2-1 ii libxmuu1 2:1.1.2-1 ii libxrender1 1:0.9.8-1 ii libxt6 1:1.1.4-1 Versions of packages x11-apps recommends: ii xbitmaps 1.1.1-2 Versions of packages x11-apps suggests: ii mesa-utils 8.2.0-1 -- no debconf information ---End Message--- ---BeginMessage--- Source: x11-apps Source-Version: 7.7+4 We believe that the bug you reported is fixed in the latest version of x11-apps, 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 764...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Julien Cristau jcris...@debian.org (supplier of updated x11-apps 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: Sat, 08 Nov 2014 11:21:37 + Source: x11-apps Binary: x11-apps Architecture: source Version: 7.7+4 Distribution: sid Urgency: medium Maintainer: Debian X Strike Force debia...@lists.debian.org Changed-By: Julien Cristau jcris...@debian.org Description: x11-apps - X applications Closes: 764792 Changes: x11-apps (7.7+4) unstable; urgency=medium . * Use man -l instead of trying to do man's job badly, and failing to find zsoelim because it's been moved out of $PATH (closes: #764792). Thanks to Lee Cremeans for the report and to Colin Watson for suggesting a fix. * Start using dh-autoreconf since we need to patch the build system. Checksums-Sha1: c9f48024d8c1afb352b74398c542e96445c52b45 1901 x11-apps_7.7+4.dsc 159741c1cb5e0ab72dbaf3ec287dd882ee6d9b34 4399329 x11-apps_7.7+4.tar.gz Checksums-Sha256: f4e1d2bf48049e9f3243fe321d3da3d5a835c15cce0acfdbd1030bb70d7470e3 1901 x11-apps_7.7+4.dsc e5923804fdb3dfef2e265df6e0c97240de607acd1d8990ed6e628f154d8d9e7b 4399329 x11-apps_7.7+4.tar.gz Files: 36f0e78f6e10edb59ab27f7d53101bfb 1901 x11 optional x11-apps_7.7+4.dsc 66a053f2ef812362f240dee2cb238e61 4399329 x11 optional x11-apps_7.7+4.tar.gz -BEGIN PGP SIGNATURE- Version: GnuPG v1 iQIcBAEBCAAGBQJUXga9AAoJEDEBgAUJBeQMyS0QAIw5QZoKOMqZzQNRDmLjBvsW v2qtfvgoeeptAK/qe5Z3DaxoOmVgR010XEptuOFHU0renxp36X4JKHfOXaFqIJY3 sY72W9uxJNOGoZUk/K8E83Ieys6/OBLDnlRZjPS+HHwy0YNWwIkjAG4rdf8Ap7VJ QLhuD1mFMVSOmgEkxX0HEvFmWDPPf2txqbixHQLXGmIvKn/a+MscqRh91anAo5qJ BGJbPQrl41zd3glfZ7XxlCoaB4CVrzUGNdG6yvMnHehIvGntGWuGFk8aiD5nxFxe RoUbeK0Hl1XooLakpFInJEZknMT/I5NRqSq0gUs9Dlgidamlw62n/8CYYNKgDsIA UgBMYtYgnU3MJ1GJQ/jVzsW0lkoOHTnwkGwS1hCjPsdNrRSZPzPlV1clvDB1yzei 6jKQF5vm7K/o7/PRi8/t6/XNrbOVPWt9bEuZ/OPatCNi1C8PNCPQw7F5k/L/BCj3 1N0JkQkFL5ZiDr7ZtTVV2rKusJU8/9VuP6bDy79+RdFeeMHgDTiiOJ4EbJa4zO2t H82+HLrBqHtbKRGOb8s860X3XLQGul1xifSXQgmYPS9qwcl6sbPYHrKNxHGS+KK+
Bug#736825: missing licenses in debian/copyright
Hi, On Mon, Jan 27, 2014 at 10:43:53AM +0100, Thorsten Alteholz wrote: please update debian/copyright of this package. For example doc/pattern_tools/svgfig.py is GPLv2+, modules/features2d/src/mser.cpp is partly GPL. There might be others around. This part still needs to be done. The license of files in modules/highgui/src/files_Qt/Milky/* does restrict the usage of some icons, which makes them non-free. These files were removed in opencv 2.4.8+dfsg1-1 Cheers, Ivo -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#768533: ImportError: cannot import name HTTPSConnection
Control: severity -1 important Hi, On Sat, Nov 08, 2014 at 02:50:44PM +0800, 積丹尼 Dan Jacobson wrote: Package: reportbug Version: 6.6.0 Severity: grave $ reportbug --template apt-show-versions Traceback (most recent call last): File /usr/bin/reportbug, line 38, in module from reportbug import utils File /usr/lib/python2.7/dist-packages/reportbug/utils.py, line 70, in module import debbugs File /usr/lib/python2.7/dist-packages/reportbug/debbugs.py, line 40, in module import debianbts File /usr/lib/pymodules/python2.7/debianbts.py, line 33, in module import SOAPpy File /usr/lib/python2.7/dist-packages/SOAPpy/__init__.py, line 5, in module from Client import * File /usr/lib/python2.7/dist-packages/SOAPpy/Client.py, line 59, in module from Parser import parseSOAPRPC File /usr/lib/python2.7/dist-packages/SOAPpy/Parser.py, line 10, in module from wstools.XMLname import fromXMLname File /usr/lib/python2.7/dist-packages/wstools/__init__.py, line 6, in module import WSDLTools File /usr/lib/python2.7/dist-packages/wstools/WSDLTools.py, line 15, in module from Utility import Collection, CollectionNS, DOM, ElementProxy, basejoin File /usr/lib/python2.7/dist-packages/wstools/Utility.py, line 30, in module from httplib import HTTPConnection, HTTPSConnection ImportError: cannot import name HTTPSConnection I guess you have openssl installed from experimental? I cannot reproduce this in unstable, but can be done if openssl is installed from experimental. Regards, Salvatore -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed: Re: Bug#768533: ImportError: cannot import name HTTPSConnection
Processing control commands: severity -1 important Bug #768533 [reportbug] ImportError: cannot import name HTTPSConnection Bug #768535 [reportbug] reportbug : Cannot import name HTTPSConnection Severity set to 'important' from 'grave' Severity set to 'important' from 'grave' -- 768533: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=768533 768535: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=768535 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed: blcr: diff for NMU version 0.8.5-2.2
Processing control commands:
tags 714045 + patch
Bug #714045 {Done: Alan Woodland awoodl...@debian.org} [blcr-dkms] blcr-dkms:
blcr module is not built on kernel 3.9.1
Bug #746038 {Done: Alan Woodland awoodl...@debian.org} [blcr-dkms]
linux-headers-amd64: configure error in linux-headers
Added tag(s) patch.
Added tag(s) patch.
tags 714045 + pending
Bug #714045 {Done: Alan Woodland awoodl...@debian.org} [blcr-dkms] blcr-dkms:
blcr module is not built on kernel 3.9.1
Bug #746038 {Done: Alan Woodland awoodl...@debian.org} [blcr-dkms]
linux-headers-amd64: configure error in linux-headers
Added tag(s) pending.
Added tag(s) pending.
--
714045: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=714045
746038: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=746038
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#714045: blcr: diff for NMU version 0.8.5-2.2
Control: tags 714045 + patch
Control: tags 714045 + pending
Dear maintainer,
I've prepared an NMU for blcr (versioned as 0.8.5-2.2) and
uploaded it to DELAYED/5. Please feel free to tell me if I
should delay it longer.
Cheers,
Julien
diff -Nru blcr-0.8.5/debian/changelog blcr-0.8.5/debian/changelog
--- blcr-0.8.5/debian/changelog 2013-11-18 13:25:55.0 +
+++ blcr-0.8.5/debian/changelog 2014-11-07 11:47:34.0 +
@@ -1,3 +1,11 @@
+blcr (0.8.5-2.2) unstable; urgency=medium
+
+ * Non-maintainer upload.
+ * Don't ship dkms package, it's not compatible with linux 3.16
+(closes: #714045).
+
+ -- Julien Cristau jcris...@debian.org Fri, 07 Nov 2014 11:47:33 +
+
blcr (0.8.5-2.1) unstable; urgency=high
* Non-maintainer upload.
diff -Nru blcr-0.8.5/debian/control blcr-0.8.5/debian/control
--- blcr-0.8.5/debian/control 2013-11-18 13:25:51.0 +
+++ blcr-0.8.5/debian/control 2014-11-07 11:36:19.0 +
@@ -121,19 +121,3 @@
applications that work with BLCR.
.
-Package: blcr-dkms
-Architecture: all
-Section: kernel
-Depends: dkms, make, ${misc:Depends}
-Recommends: blcr-util, linux-headers-686-pae | linux-headers-amd64 | linux-headers-generic
-Replaces: blcr-source
-Description: DKMS support for BLCR kernel module
- This package provides integration with the DKMS infrastructure for
- automatically building out of tree kernel modules.
- .
- BLCR (Berkeley Lab Checkpoint/Restart) allows programs running on
- Linux to be checkpointed (written entirely to a file), and then
- later restarted.
- .
-
-
diff -Nru blcr-0.8.5/debian/rules blcr-0.8.5/debian/rules
--- blcr-0.8.5/debian/rules 2013-02-01 21:24:15.0 +
+++ blcr-0.8.5/debian/rules 2014-11-07 11:37:52.0 +
@@ -40,7 +40,6 @@
# Name of the source package
psource:=blcr-source
-dkmssource:=blcr-dkms
# The short upstream name, used for the module source directory
sname:=blcr
@@ -120,7 +119,6 @@
dh_installdirs
# Create the directories to install the source into
dh_installdirs -p$(psource) usr/src/modules/$(sname)
- dh_installdirs -p$(dkmssource) usr/src/$(sname)-$(version)
#usr/src/modules/$(sname)/include
dh_installdirs
@@ -162,27 +160,6 @@
cd debian/$(psource)/usr/src tar ch modules | bzip2 -9 $(sname).tar.bz2 rm -rf modules
- # Base the DKMS source on the blcr.tar.bz2 that we ship!
- cd $(CURDIR)/debian/$(dkmssource)/usr/src/$(sname)-$(version) tar --strip-components=2 -xjf $(CURDIR)/debian/$(psource)/usr/src/blcr.tar.bz2
-
- # we don't ship -source anymore, so delete it!
- -rm -rf $(CURDIR)/debian/$(psource)/
-
- # clean up the shipped source
- # Tests should be executable
- find $(CURDIR)/debian/$(dkmssource)/usr/src/$(sname)-$(version)/tests/ -iname '*.sh' -exec chmod a+x {} \;
- # we don't duplicate this everywhere, it's in /usr/share/doc
- find $(CURDIR)/debian/$(dkmssource)/ -name 'license.txt' -exec rm {} \;
- cd $(CURDIR)/debian/$(dkmssource)/usr/src/$(sname)-$(version)/ rm COPYING COPYING.LIB LICENSE.txt
- # make more things executable that should be
- cd $(CURDIR)/debian/$(dkmssource)/usr/src/$(sname)-$(version)/ chmod a+x contrib/cr_depmod debian/conf.mk etc/blcr.rc
- # make some things *not* executable
- cd $(CURDIR)/debian/$(dkmssource)/usr/src/$(sname)-$(version)/ chmod a-x vmadump4/vmadump_sparc.c cr_module/arch/sparc/cr_arch.h
-
- sed -e 's/[@]VERSION[@]/$(version)/' debian/dkms.conf.in \
- debian/$(dkmssource)/usr/src/$(sname)-$(version)/dkms.conf
-
-
dh_installdocs
signature.asc
Description: Digital signature
Bug#757588: #757588: sysvinit-core: installation fails when systemd is present
Thank you for your message. It is clear to me that the current sysvinit package underwent changes since August... I am not happy with the way this bug, marked as critical, was dealt with: it took 3 months to be attended to and if it was not the case that I knew enough to repair the Debian installation using a live CD, I would be forced 3 months ago to install everything from scratch. Should I forget Debian and use some other distribution? Regards, Miguel Filgueiras Damyan Ivanov d...@debian.org wrote: I was unable to reproduce this with the current sysvinit package in jessie (2.88dsf-57). What I did: * installed wheezy in a VM * altered /etc/apt/sources.list adding jessie URLs * apt-get update * apt-get install apt dpkg locales * apt dist-upgrade * reboot At this point the system was running with systemd. * apt install sysvinit-core (nothing odd here, installation went normally) * reboot At this point the system was running with sysvinit. Sorry for not providing logs from the susvinit-core installation, I was unable to get the serial console of the VM to work. HTH, dam -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#766251: marked as done (flightgear fails to start with *** stack smashing detected ***)
Your message dated Sat, 08 Nov 2014 12:58:48 +
with message-id e1xn5bm-0002gp...@franck.debian.org
and subject line Bug#766251: fixed in flightgear-data 3.0.0-2
has caused the Debian Bug report #766251,
regarding flightgear fails to start with *** stack smashing detected ***
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.)
--
766251: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=766251
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
---BeginMessage---
Package: flightgear-data-base
Version: 3.0.0-1
Severity: grave
Justification: renders package unusable
Control: tags -1 patch
A fresh install (no .fgfs) of amd64 flightgear in current jessie or
current sid fails to start:
Program received signal SIGABRT, Aborted.
0x71d6f077 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 full
#0 0x71d6f077 in __GI_raise (sig=sig@entry=6) at
../nptl/sysdeps/unix/sysv/linux/raise.c:56
resultvar = 0
pid = 25441
selftid = 25441
#1 0x71d70458 in __GI_abort () at abort.c:89
save_stage = 2
act = {__sigaction_handler = {sa_handler = 0x3020702d77722030,
sa_sigaction = 0x3020702d77722030}, sa_mask = {__val =
{2319406791620833328, 2319389199435444272, 2314885530818453536,
2314885530818453536, 2314885530818453536, 6731583338252032800,
7378697629483820554, 3472328296331896422, 7378697629483806000,
3472609797883717222, 2337500343188860976, 3472328296227680304,
3467824696768081952, 2314885530818453536, 2314885530818453536,
140737488344416}}, sa_flags = 60, sa_restorer = 0x7fffd660}
sigs = {__val = {32, 0 repeats 15 times}}
#2 0x71dacfb4 in __libc_message (do_abort=do_abort@entry=2,
fmt=fmt@entry=0x71e9d60b *** %s ***: %s terminated\n) at
../sysdeps/posix/libc_fatal.c:175
ap = {{gp_offset = 32, fp_offset = 32767, overflow_arg_area =
0x7fffd670, reg_save_area = 0x7fffd600}}
fd = 18
on_2 = optimized out
list = optimized out
nlist = optimized out
cp = optimized out
written = optimized out
#3 0x71e300a7 in __GI___fortify_fail
(msg=msg@entry=0x71e9d5f3 stack smashing detected) at
fortify_fail.c:31
No locals.
#4 0x71e30070 in __stack_chk_fail () at stack_chk_fail.c:28
No locals.
#5 0x76c99569 in simgear::PredicateExpressionint,
std::equal_to::eval (this=0xb6d9e70, value=optimized out,
b=optimized out) at
/build/simgear-mmipqT/simgear-3.0.0/simgear/structure/SGExpression.hxx:1184
No locals.
#6 0x770b1e72 in getValue (binding=0x7fffd730,
this=optimized out) at
/build/simgear-mmipqT/simgear-3.0.0/simgear/structure/SGExpression.hxx:126
value = true
#7 simgear::AndExpression::eval (this=0xb6da340, value=@0x7fffd750:
true, b=0x7fffd730) at
/build/simgear-mmipqT/simgear-3.0.0/simgear/structure/SGExpression.hxx:1266
i = 0
#8 0x770afd03 in getValue (binding=0x7fffd730,
this=optimized out) at
/build/simgear-mmipqT/simgear-3.0.0/simgear/structure/SGExpression.hxx:126
value = true
#9 simgear::Technique::validateInContext (this=0xb6d9bc0, gc=optimized
out) at
/build/simgear-mmipqT/simgear-3.0.0/simgear/scene/material/Technique.cxx:122
oldVal = simgear::Technique::QUERY_IN_PROGRESS
binding = {simgear::expression::Binding = {_vptr.Binding =
0x7742e670 vtable for
simgear::expression::FixedLengthBinding1+16}, _bindings = {{typeTag =
simgear::expression::INT, val = {boolVal = false, intVal = 0, floatVal =
0, doubleVal = 0
contextId = 0
newVal = simgear::Technique::INVALID
#10 0x751ef556 in osg::GraphicsContext::runOperations() () from
/usr/lib/x86_64-linux-gnu/libosg.so.100
No symbol table info available.
#11 0x758a2d08 in osgViewer::ViewerBase::renderingTraversals()
() from /usr/lib/x86_64-linux-gnu/libosgViewer.so.100
No symbol table info available.
#12 0x00b989ea in fgOSMainLoop() ()
No symbol table info available.
#13 0x005f94ee in fgMainInit(int, char**) ()
No symbol table info available.
#14 0x005a00ff in main ()
No symbol table info available.
It looks like the problem is casting simgear::ConvertExpressiondouble,
float* (derived from SGExpressiondouble*,
simgear/structure/SGExpression.hxx:11xx) to SGExpressionint*:
(gdb) frame 5
#5 0x76c99569 in simgear::PredicateExpressionint,
std::equal_to::eval (this=0xb6d9e70, value=optimized out,
b=optimized out) at
Bug#744698: [fontmatrix] [DFSG] missing source
Hi, I've investigated this issue: - help/js/jquery.js = can find code.jquery.com - help/js/jquery.jtabs.pack.js = missing this version - src/graphic-resources/html-css/fontmatrix.js = can find code.jquery.com I cannot find jquery.jtabs.pack.js at anywhere but can get version 0.3 at http://vanity.enavu.com/download/ It maybe okay to include it if it works. and also another issue... Now running lintian... E: fontmatrix source: license-problem-cc-by-nc-sa src/icons/application-fontmatrix-vectors.svg E: fontmatrix source: license-problem-cc-by-nc-sa src/icons/application-fontmatrix-systray-vectors.svg E: fontmatrix source: license-problem-cc-by-nc-sa src/graphic-resources/about-vectors.svg :-( -- Regards, Hideki Yamane henrich @ debian.or.jp/org http://wiki.debian.org/HidekiYamane -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#765540: grub2: grub fails with error: 'grub_term_highlight_color' not found
I just hit this bug while upgrading from 2.00-22 to 2.02~beta2-15. I believe #743477 is a duplicate of this bug. The current behavior breaks an existing functional boot simply by noninteractively upgrading grub-pc, which happens in an apt-get upgrade and/or dist-upgrade. If this happens on a noninteractive upgrade from wheezy to jessie, it would be a very serious release blocker. By its definition, this should be a critical bug. Steps to reproduce: - Deploy this jessie vagrant box: https://downloads.sourceforge.net/project/vagrantboxjessie/debian80.box (or any box with grub 2.00-22) - apt-get update - DEBIAN_FRONTEND=noninteractive apt-get -y install grub-pc - reboot The DEBIAN_FRONTEND=noninteractive is there to reproduce what happenes during provisioning automation (ansible/puppet/salt/chef etc). An example vagrantfile is here: http://paste.debian.net/130854/ The workaround is to do a grub-install --recheck /dev/sda after upgrading the package. Due to the nature of deployable images like this, the install_devices from debconf will likely never match the newly created drive; even in cases where it is using /dev/sda it may be that an image would get deployed with virtio and the booted drive would end up being /dev/vda. For reference, the output of debconf-get-selections | grep -i grub before upgrading grub-pc packages: /usr/bin/debconf-get-selections |grep -i grub grub-pc grub-pc/chainload_from_menu.lst boolean true # Writing GRUB to boot device failed - continue? grub-pc grub-pc/install_devices_failed boolean false grub-pc grub-pc/kopt_extracted boolean false # Hide the GRUB timeout grub-pc grub-pc/hidden_timeout boolean false # GRUB install devices: grub-pc grub-pc/install_devices multiselect /dev/disk/by-id/ata-VBOX_HARDDISK_VB4950a3eb-80192436 grub-pc grub2/linux_cmdline_default string quiet # Remove GRUB 2 from /boot/grub? grub-pc grub-pc/postrm_purge_boot_grub boolean false # Writing GRUB to boot device failed - try again? grub-pc grub-pc/install_devices_failed_upgrade boolean true grub-pc grub2/linux_cmdline string debian-installer=en_US grub-pc grub2/kfreebsd_cmdline string # GRUB timeout grub-pc grub-pc/timeout string 5 # /boot/grub/device.map has been regenerated grub-pc grub2/device_map_regeneratednote # Continue without installing GRUB? grub-pc grub-pc/install_devices_empty boolean false # GRUB install devices: grub-pc grub-pc/install_devices_disks_changed multiselect grub-pc grub2/kfreebsd_cmdline_default string quiet # Finish conversion to GRUB 2 now? grub-pc grub-pc/mixed_legacy_and_grub2 boolean true And after upgrading: grub-pc grub-pc/kopt_extracted boolean false # GRUB install devices: grub-pc grub-pc/install_devices multiselect /dev/disk/by-id/ata-VBOX_HARDDISK_VB4950a3eb-80192436 grub-pc grub2/linux_cmdline_default string quiet # GRUB install devices: grub-pc grub-pc/install_devices_disks_changed multiselect /dev/disk/by-id/ata-VBOX_HARDDISK_VB4950a3eb-80192436 # /boot/grub/device.map has been regenerated grub-pc grub2/device_map_regeneratednote # Remove GRUB 2 from /boot/grub? grub-pc grub-pc/postrm_purge_boot_grub boolean false grub-pc grub2/kfreebsd_cmdline string grub-pc grub-pc/chainload_from_menu.lst boolean true # Continue without installing GRUB? grub-pc grub-pc/install_devices_empty boolean false # Finish conversion to GRUB 2 now? grub-pc grub-pc/mixed_legacy_and_grub2 boolean true grub-pc grub2/kfreebsd_cmdline_default string quiet grub-pc grub2/linux_cmdline string debian-installer=en_US # Writing GRUB to boot device failed - try again? grub-pc grub-pc/install_devices_failed_upgrade boolean true # What do you want to do about modified configuration file grub? # GRUB timeout; for internal use grub-pc grub-pc/timeout string 0 # Hide the GRUB timeout; for internal use grub-pc grub-pc/hidden_timeout boolean false # Writing GRUB to boot device failed - continue? grub-pc grub-pc/install_devices_failed boolean false -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed: closing 767999
Processing commands for cont...@bugs.debian.org: # close; it was re-opened by re-assign close 767999 Bug #767999 [base-passwd] makes base-files fail to install during bootstrap Marked Bug as done thanks Stopping processing here. Please contact me if you need assistance. -- 767999: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=767999 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#768581: opal: FTBFS in experimental: error: 'CodecID' has not been declared
Package: opal Version: 3.12.8~dfsg-1 Severity: serious Justification: fails to build from source (but built successfully in the past) Hi, opal/experimental fails to build in a current sid+experimental environment, see https://buildd.debian.org/status/fetch.php?pkg=opalarch=arm64ver=3.12.8~dfsg-1stamp=1414123156 [CC] .common/dyna.cxx In file included from ../common/ffmpeg.cxx:41:0: .../common/ffmpeg.h:123:30: error: 'CodecID' has not been declared virtual bool InitEncoder(CodecID codecId); ^ .../common/ffmpeg.h:124:30: error: 'CodecID' has not been declared virtual bool InitDecoder(CodecID codecId); ^ I could reproduce this rebuilding it for amd64 locally. Andreas -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#768583: libqinfinity: Build-Depends on unavailable libinfinity-0.5-dev
Package: libqinfinity Version: 1:0.5.1-1 Severity: serious B-D uninstallable in sid/experimental -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed: your mail
Processing commands for cont...@bugs.debian.org: severity 719519 grave Bug #719519 [lua-json] lua-json: Current version of lua-json conflicts with lpeg Severity set to 'grave' from 'normal' thanks Stopping processing here. Please contact me if you need assistance. -- 719519: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=719519 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#708781: fix for non-free files in autoconf packages
On Sat, 08 Nov 2014 at 13:34:59 +, Simon McVittie wrote: On Sat, 01 Nov 2014 at 18:55:58 -0400, Michael Gilbert wrote: A patch for the autoconf rc issues is available in bug #695704 for autoconf2.59. Thanks, I've made a similar change to autoconf2.64. I will upload a package with the attached nmudiff to DELAYED/2 when I have confirmed that gcc-4.9 can compile successfully in an sbuild chroot with my autoconf2.64 injected into it. I noticed that #619719 is also open with a patch, severity:important, so I combined the two patches and uploaded to DELAYED/5 instead. The BTS might reject or delay the above email because the attachment is rather huge. Sorry about that, I hand't realised just how large it was. I attach a filtered version here; the diffstat is accurate but the deletion of the non-free files is not shown in the actual diff. I forgot to mention for anyone interested in these bugs that my version of the source and binary packages, including the repacked orig.tar.gz, can be obtained here: https://www.pseudorandom.co.uk/~smcv/20141108autoconf/ Regards, S diffstat for autoconf2.64-2.64 autoconf2.64-2.64+dfsg debian/changelog| 14 debian/patches/03_no_autoconf.info.diff | 92 debian/patches/series |1 debian/rules|3 doc/autoconf.info |23225 -- doc/autoconf.texi |24121 6 files changed, 109 insertions(+), 47347 deletions(-) [The diff for doc/autoconf.info and doc/autoconf.texi consists of deleting the entire files -smcv] diff -Nru autoconf2.64-2.64/debian/changelog autoconf2.64-2.64+dfsg/debian/changelog --- autoconf2.64-2.64/debian/changelog 2014-11-08 14:26:20.0 + +++ autoconf2.64-2.64+dfsg/debian/changelog 2014-11-08 14:26:20.0 + @@ -1,3 +1,17 @@ +autoconf2.64 (2.64+dfsg-0.1) unstable; urgency=medium + + * Non-maintainer upload. + + [ Jonathan Nieder ] + * debian/rules: CONFIG_SHELL=/bin/bash, fixing FTBFS with future dash +versions (Closes: #619719) + + [ Simon McVittie ] + * Remove unused and non-DFSG-Free doc/autoconf.* (Closes: #708781) + * Add patch to not try to compile them + + -- Simon McVittie s...@debian.org Fri, 07 Nov 2014 19:08:03 + + autoconf2.64 (2.64-3) unstable; urgency=low * Update local patch for 2.64. diff -Nru autoconf2.64-2.64/debian/patches/03_no_autoconf.info.diff autoconf2.64-2.64+dfsg/debian/patches/03_no_autoconf.info.diff --- autoconf2.64-2.64/debian/patches/03_no_autoconf.info.diff 1970-01-01 01:00:00.0 +0100 +++ autoconf2.64-2.64+dfsg/debian/patches/03_no_autoconf.info.diff 2014-11-08 14:26:20.0 + @@ -0,0 +1,92 @@ +From: Simon McVittie s...@debian.org +Subject: Do not build autoconf.info any more + +Based on a patch by David Prévot taf...@debian.org for autoconf2.59. + +Bug-Debian: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=708781 +Forwarded: not-needed + +--- autoconf2.64-2.64/doc/Makefile.am 2009-03-16 14:37:04.0 + autoconf2.64-2.64+dfsg/doc/Makefile.am 2014-11-07 18:50:35.180407944 + +@@ -20,7 +20,7 @@ + TEXI2HTML_FLAGS = -split_chapter + TEXINFO_TEX = ../build-aux/texinfo.tex + +-info_TEXINFOS = autoconf.texi standards.texi ++info_TEXINFOS = standards.texi + autoconf_TEXINFOS = fdl.texi install.texi + standards_TEXINFOS = fdl.texi gnu-oids.texi make-stds.texi + +--- autoconf2.64-2.64/doc/Makefile.in 2009-07-27 04:28:44.0 +0100 autoconf2.64-2.64+dfsg/doc/Makefile.in 2014-11-07 18:52:06.345226181 + +@@ -50,9 +67,8 @@ + PRE_UNINSTALL = : + POST_UNINSTALL = : + subdir = doc +-DIST_COMMON = $(autoconf_TEXINFOS) $(srcdir)/Makefile.am \ +- $(srcdir)/Makefile.in $(srcdir)/stamp-vti \ +- $(srcdir)/version.texi $(standards_TEXINFOS) ++DIST_COMMON = $(srcdir)/Makefile.am $(srcdir)/Makefile.in \ ++ $(standards_TEXINFOS) + ACLOCAL_M4 = $(top_srcdir)/aclocal.m4 + am__aclocal_m4_deps = $(top_srcdir)/m4/m4.m4 \ + $(top_srcdir)/m4/make-case.m4 $(top_srcdir)/configure.ac +@@ -63,13 +79,13 @@ + CONFIG_CLEAN_VPATH_FILES = + SOURCES = + DIST_SOURCES = +-INFO_DEPS = $(srcdir)/autoconf.info $(srcdir)/standards.info ++INFO_DEPS = $(srcdir)/standards.info + am__TEXINFO_TEX_DIR = $(srcdir)/../build-aux +-DVIS = autoconf.dvi standards.dvi +-PDFS = autoconf.pdf standards.pdf +-PSS = autoconf.ps standards.ps +-HTMLS = autoconf.html standards.html +-TEXINFOS = autoconf.texi standards.texi ++DVIS = standards.dvi ++PDFS = standards.pdf ++PSS = standards.ps ++HTMLS = standards.html ++TEXINFOS = standards.texi + TEXI2DVI = texi2dvi + TEXI2PDF = $(TEXI2DVI) --pdf --batch + MAKEINFOHTML = $(MAKEINFO) --html +@@ -189,7 +216,7 @@ + AM_MAKEINFOFLAGS = --no-split + TEXI2HTML_FLAGS = -split_chapter + TEXINFO_TEX = ../build-aux/texinfo.tex +-info_TEXINFOS = autoconf.texi standards.texi ++info_TEXINFOS = standards.texi + autoconf_TEXINFOS = fdl.texi install.texi + standards_TEXINFOS
Processed: tagging 768212
Processing commands for cont...@bugs.debian.org: tags 768212 + pending Bug #768212 [aces3-data] aces3-data: fails to upgrade from 'wheezy' - trying to overwrite /usr/share/aces3/GENBAS Added tag(s) pending. thanks Stopping processing here. Please contact me if you need assistance. -- 768212: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=768212 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#719519: (no subject)
severity 719519 grave thanks Raising this bug to grave because lua-json is currently unusable: $ lua Lua 5.2.3 Copyright (C) 1994-2013 Lua.org, PUC-Rio json = require(json) /usr/share/lua/5.2/json/decode/strings.lua:97: loop body may accept empty string stack traceback: [C]: in function '__pow' /usr/share/lua/5.2/json/decode/strings.lua:97: in function 'buildCaptureString' /usr/share/lua/5.2/json/decode/strings.lua:118: in function 'generateLexer' /usr/share/lua/5.2/json/decode.lua:123: in function 'buildDecoder' /usr/share/lua/5.2/json/decode.lua:130: in main chunk [C]: in function 'require' /usr/share/lua/5.2/json.lua:5: in main chunk [C]: in function 'require' stdin:1: in main chunk [C]: in ? print(json) nil -- System Information: Debian Release: jessie/sid APT prefers testing APT policy: (200, 'testing'), (170, 'unstable'), (150, 'testing-proposed-updates'), (150, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.14-2-amd64 (SMP w/2 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages lua-json depends on: ii lua-lpeg 0.12-1 lua-json recommends no packages. lua-json suggests no packages. -- no debconf information -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#768541: AttributeError: 'module' object has no attribute 'POP3_SSL'
On 08/11/14 09:30, 積丹尼 Dan Jacobson wrote: Package: python2.7 Version: 2.7.8-11 Severity: grave $ getmail --version Traceback (most recent call last): File /usr/bin/getmail, line 58, in module from getmailcore import __version__, retrievers, destinations, filters, \ File /usr/lib/python2.7/dist-packages/getmailcore/retrievers.py, line 45, in module from getmailcore._retrieverbases import * File /usr/lib/python2.7/dist-packages/getmailcore/_retrieverbases.py, line 266, in module class POP3_SSL_EXTENDED(poplib.POP3_SSL): AttributeError: 'module' object has no attribute 'POP3_SSL' emilio@titan:~$ python Python 2.7.8 (default, Oct 18 2014, 12:50:18) [GCC 4.9.1] on linux2 Type help, copyright, credits or license for more information. import poplib poplib.POP3_SSL class poplib.POP3_SSL at 0x7f27f4ac18d8 ii python2.72.7.8-11amd64 Interactive high-level object-oriented language (version 2.7) What version of openssl do you have? This sounds like you have the experimental version, which disabled SSL3 support because it's insecure. Thus this is not a bug that affects jessie or sid. Emilio -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#768112: fixed in slurm-llnl 14.03.9-4
Le 2014-11-08 10:53, Adam D. Barratt a écrit : Control: reopen -1 On 2014-11-06 10:21, Gennaro Oliva wrote: Source: slurm-llnl Source-Version: 14.03.9-4 We believe that the bug you reported is fixed in the latest version of slurm-llnl, which is due to be installed in the Debian FTP archive. [...] slurm-llnl (14.03.9-4) unstable; urgency=medium . * Declaring slurm-client conflict with sinfo (Closes: #768112) No. Please re-read policy (specifically 10.1) - you don't get to conflict with other packages just because you both want to use the same file path. I think that Gennaro fixed it that way because we were aware of this issue (which is here since before Lenny, fwiw) and we agreed with Gaudenz (sinfo's co-maintainer) to find a real solution to implement in Jessie+1. Gaudenz has also some trouble contacting the other co-maintainer of sinfo and wasn't able to explain its name. So we were a bit stuck. Besides, since the conflicts is already present in previous releases of Debian and since we need to support upgrades, don't we need a conflicts statement anyway? (Maybe a versioned one if the situation is sorted out before the freeze but still) So, is it acceptable to keep this workaround for Jessie and work on a better one for Jessie+1? That way, we hope to find time enough time to work this in coordination with both upstreams. Kind regards, -- Mehdi -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#765424: libpam-mount: Fails to run mount: invalid option -- '-p'
Hi, additional info for anyone who wants this package to be part of Jessie and dig this further: cryptoloop (losetup) support was dropped from util-linux 2.24.2-1. This change propagated into unstable via 2.25.1-3, that was uploaded on 2014-10-05. So indeed, the mount -p option isn't available anymore. Cheers, -- intrigeri -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#754000: marked as done (doxymacs: please switch to emacs24)
Your message dated Sat, 08 Nov 2014 15:27:26 +
with message-id e1xn7vc-0005vf...@franck.debian.org
and subject line Bug#754000: fixed in doxymacs 1.8.0-6.1
has caused the Debian Bug report #754000,
regarding doxymacs: please switch to emacs24
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.)
--
754000: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=754000
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
---BeginMessage---
Source: doxymacs
Severity: normal
Tags: patch
User: r...@debian.org
Usertags: emacs24
Control: block 753885 by -1
Dear maintainer,
we're hoping to remove emacs23 from unstable/testing in future:
https://bugs.debian.org/753885
Please migrate your dependencies to emacs | emacsen (or whatever's
more appropriate for your package) as soon as possible. The attached
patch may help.
Thanks for considering.
--
mass bug filer on behalf of Rob Browning, emacs maintainer
--- debian/control.orig 2014-07-06 13:26:36.520411252 +0200
+++ debian/control 2014-07-06 13:26:47.592547841 +0200
@@ -2,14 +2,14 @@
Section: devel
Priority: optional
Maintainer: Otavio Salvador ota...@debian.org
-Build-Depends: debhelper ( 7), emacs23 | emacsen, libxml2-dev
+Build-Depends: debhelper ( 7), emacs | emacsen, libxml2-dev
Standards-Version: 3.7.3
Vcs-Git: git://git.debian.org/git/collab-maint/doxymacs.git
Vcs-Browser: http://git.debian.org/?p=collab-maint/doxymacs.git
Package: doxymacs
Architecture: any
-Depends: ${shlibs:Depends}, emacs23 | emacsen
+Depends: ${shlibs:Depends}, emacs | emacsen
Recommends: doxygen
Description: elisp package for making doxygen usage easier under Emacs
The purpose of the doxymacs project is to create a elisp package that
---End Message---
---BeginMessage---
Source: doxymacs
Source-Version: 1.8.0-6.1
We believe that the bug you reported is fixed in the latest version of
doxymacs, 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 754...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Joao Eriberto Mota Filho eribe...@debian.org (supplier of updated doxymacs
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: Sat, 08 Nov 2014 10:00:24 -0200
Source: doxymacs
Binary: doxymacs
Architecture: source amd64
Version: 1.8.0-6.1
Distribution: unstable
Urgency: medium
Maintainer: Otavio Salvador ota...@debian.org
Changed-By: Joao Eriberto Mota Filho eribe...@debian.org
Description:
doxymacs - elisp package for making doxygen usage easier under Emacs
Closes: 754000 754841
Changes:
doxymacs (1.8.0-6.1) unstable; urgency=medium
.
* Non-maintainer upload.
* Fix a FTBFS caused by an unmet dependency. (Closes: #754000, #754841)
Checksums-Sha1:
4d891f1eb8a2a52f3448c1fc4304b496ae2a53ad 1774 doxymacs_1.8.0-6.1.dsc
f40f2b9aa021e363ea37dd5addfe90916ad3129f 3410 doxymacs_1.8.0-6.1.diff.gz
342eabf5a53c8bb4dcd7ba86c9e2634f558c36d3 42056 doxymacs_1.8.0-6.1_amd64.deb
Checksums-Sha256:
19af49feb035898c82b064bc44bcfd99969c296aec72b326be212e16314263a5 1774
doxymacs_1.8.0-6.1.dsc
00a8890846431ecb8a02c6c41d6e779cbd4ba24014dcd368c2f50c43e92d42c6 3410
doxymacs_1.8.0-6.1.diff.gz
f51841bfd511e6f3bbdb8f5e7f78358eb308ecc6f5fab569df0fae99ec7e6ae5 42056
doxymacs_1.8.0-6.1_amd64.deb
Files:
d97d887c4a7c13be232066b15f1660e0 1774 devel optional doxymacs_1.8.0-6.1.dsc
7336b141c30c90a4af4fd565f0c7f19a 3410 devel optional doxymacs_1.8.0-6.1.diff.gz
8b8e9dcbd1596bfd784809c112678a6e 42056 devel optional
doxymacs_1.8.0-6.1_amd64.deb
-BEGIN PGP SIGNATURE-
Version: GnuPG v1
iQIcBAEBAgAGBQJUXiA4AAoJEN5juccE6+nvigcP/inmb5yyDjn6tjqvoddvEUMi
m9hY4mo9hLtNMSyW7GwrXwZ6cr3/fmONTaMTe2pi3xTY/GHKO2Ok1++/jG8tMoP3
/xUFlaofDeO5+AOrDFJhWEK/R7oz6zVS0/QyKCh3mVFNPnDeDXF+4sfW5EizbzaX
Q09JdDBsspfU1ncfpyOFEsvnqCZQa1OR6ZtHbdbicwvjCj1GmHxvG4CjFvc6OkRJ
6thVBVHcNC+Vi8XLW/F8K1B6qvylwR2rhMl1LzgOe0wieUZrlvTL90g+OJUrm2e0
Lcz1GFGi9t2FjH6/poyJjN24oJW8wv+nxH3RWdUyHlIQdDeRLf9MxcPPg073dKMf
ktr9kUAJ1z2QpM/eA/hONpOfnjRD8qH+cqvC8S7jrUbqgWYqs6rD7bJFI4D+WWSj
vTm+eBYnkXG4toOwXAqx/qr+7cI9xSLAIFPL5YO/DHU9xhM4TkENVty4y3AJUb6t
bCy30E4HSZEWjuXcbO/YZqC3qolk/lc3qXpj08jyaTyz5IUaW/k9gah3SXgECPwu
Bug#766273: picosat and undertaker: error when trying to install together
On 2014-10-21 19:53, Michael Tautschnig wrote: Hi undertaker maintainers/uploaders, [...] Here is a list of files that are known to be shared by both packages (according to the Contents file for sid/amd64, which may be slightly out of sync): /usr/bin/picomus [...] I wasn't even aware that undertaker was in Debian, and the same might hold for you as far as picosat is concerned. Anyway, in the interest of code de-duplication, could undertaker be changed to use the separate picosat package instead of the one shipped as part of the source tree? That was the case when we initially uploaded undertaker to debian AFAIR (or it was the plan at least). We had to abandon this scheme because we switched to a newer version of picosat that changed API. Stefan you just finished your Master thesis that worked a lot on how undertaker uses the sat checker. Maybe you can give us some insight here? Thanks, Reinhard -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#766273: picosat and undertaker: error when trying to install together
Hi, we have an in-tree variant of the PicoSAT because the newer, reentrant version of picosat is around 30% slower for our usage than the one we're currently using (936). However, the picomus export is done for compatibility reasons. The output format was changed several times and the version 954 and 959 have some problems with argument passing and reading from stdin. These problems are solved with 960 but 960 was just released a few weeks ago. So we could use either 936 or 960 and i thought hat was a elegant way to solve the problem. But i didn't think it might cause conflicts here. Stefan 2014-11-08 16:18 GMT+01:00 Reinhard Tartler siret...@tauware.de: On 2014-10-21 19:53, Michael Tautschnig wrote: Hi undertaker maintainers/uploaders, [...] Here is a list of files that are known to be shared by both packages (according to the Contents file for sid/amd64, which may be slightly out of sync): /usr/bin/picomus [...] I wasn't even aware that undertaker was in Debian, and the same might hold for you as far as picosat is concerned. Anyway, in the interest of code de-duplication, could undertaker be changed to use the separate picosat package instead of the one shipped as part of the source tree? That was the case when we initially uploaded undertaker to debian AFAIR (or it was the plan at least). We had to abandon this scheme because we switched to a newer version of picosat that changed API. Stefan you just finished your Master thesis that worked a lot on how undertaker uses the sat checker. Maybe you can give us some insight here? Thanks, Reinhard -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#766849: gnome-shell responds and renders hazardously
Hi, dAgeCKo wrote (07 Nov 2014 19:49:50 GMT) : Here is joined the output of what you asked. Looks like the proprietary nvidia driver is being used. Can you reproduce this bug with the free nouveau driver? Cheers, -- intrigeri -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed: tagging 767280
Processing commands for cont...@bugs.debian.org: tags 767280 + moreinfo Bug #767280 [gnome-session] gnome-session: screen freezes after login Added tag(s) moreinfo. thanks Stopping processing here. Please contact me if you need assistance. -- 767280: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=767280 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#768597: libgtkada: GFDL non free file with front cover
Source: libgtkada Severity: serious Justification: license issue A recent clarification [1] by upstream authors makes it explicit that files under docs/gtkada_ug/ *are* licensed under the GFDL with invariant sections, and must be removed from Debian. [1] https://lists.debian.org/debian-ada/2014/10/msg00023.html -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#768463: marked as done (FTBFS: Failed autobuilding of package)
Your message dated Sat, 08 Nov 2014 15:52:35 + with message-id e1xn8jx-000139...@franck.debian.org and subject line Bug#768463: fixed in kadu 1.2-1 has caused the Debian Bug report #768463, regarding FTBFS: Failed autobuilding of package 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.) -- 768463: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=768463 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: kadu Version: 1.1-1 Severity: serious Tags: jessie sid User: debian...@lists.debian.org Usertags: qa-ftbfs-20141107 qa-ftbfs Justification: FTBFS on amd64 Hi! During a rebuild of all packages in sid, your package failed to build on amd64. On i386 is the same, but on armhf is build fine. -- -- ** -- * Kadu is now successfully installed * -- ** -- -- Thanks for choosing Kadu Communicator and ENJOY!!! -- -- Kadu Team -- make[1]: Leaving directory '/tmp/buildd/kadu-1.1/build-dir' cp /tmp/buildd/kadu-1.1/debian/tmp/usr/share/kadu/ChangeLog debian/kadu/usr/share/doc/kadu/about-changes-tab.txt # Rmove some cruft rm -f /tmp/buildd/kadu-1.1/debian/tmp/usr/share/kadu/modules/data/osd_hints/License # Remove RPATH from all the plugins chrpath -d debian/tmp/usr/lib/x86_64-linux-gnu/kadu/plugins/*.so dh_install -s dpkg-buildpackage: error: fakeroot debian/rules binary gave error exit status 2 E: Failed autobuilding of package -- System Information: Debian Release: jessie/sid APT prefers testing APT policy: (500, 'testing'), (500, 'stable'), (300, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.16.0-4-amd64 (SMP w/4 CPU cores) Locale: LANG=pl_PL.utf8, LC_CTYPE=pl_PL.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages kadu depends on: ii kadu-common 1.1-1 ii libc62.19-12 ii libenchant1c2a 1.6.0-10.1 ii libgadu3 1:1.12.0-5 ii libgcc1 1:4.9.2-1 ii libgcrypt20 1.6.2-4 ii libidn11 1.29-1 ii libindicate-qt1 0.2.5.91-5 ii libkadu 1.1-1 ii libmpdclient22.9-1 ii libotr5 4.1.0-1 ii libphonon4 4:4.8.0-3 ii libqca2 2.0.3-6 ii libqca2-plugin-ossl 2.0.0~beta3-2 ii libqt4-dbus 4:4.8.6+git64-g5dc8b2b+dfsg-2+b1 ii libqt4-declarative 4:4.8.6+git64-g5dc8b2b+dfsg-2+b1 ii libqt4-network 4:4.8.6+git64-g5dc8b2b+dfsg-2+b1 ii libqt4-script4:4.8.6+git64-g5dc8b2b+dfsg-2+b1 ii libqt4-sql 4:4.8.6+git64-g5dc8b2b+dfsg-2+b1 ii libqt4-sql-sqlite4:4.8.6+git64-g5dc8b2b+dfsg-2+b1 ii libqt4-svg 4:4.8.6+git64-g5dc8b2b+dfsg-2+b1 ii libqt4-xml 4:4.8.6+git64-g5dc8b2b+dfsg-2+b1 ii libqt4-xmlpatterns 4:4.8.6+git64-g5dc8b2b+dfsg-2+b1 ii libqtcore4 4:4.8.6+git64-g5dc8b2b+dfsg-2+b1 ii libqtgui44:4.8.6+git64-g5dc8b2b+dfsg-2+b1 ii libqtwebkit4 2.3.4.dfsg-3 ii libstdc++6 4.9.2-1 ii libx11-6 2:1.6.2-3 ii libxext6 2:1.3.3-1 ii libxss1 1:1.2.2-1 ii multiarch-support2.19-12 ii phonon 4:4.8.0-3 ii zlib1g 1:1.2.8.dfsg-2 kadu recommends no packages. Versions of packages kadu suggests: ii kadu-themes 1.1-1 -- no debconf information ---End Message--- ---BeginMessage--- Source: kadu Source-Version: 1.2-1 We believe that the bug you reported is fixed in the latest version of kadu, 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 768...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Patryk Cisek pat...@debian.org (supplier of updated kadu 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: Sat, 08 Nov 2014 15:17:42 +0100 Source: kadu Binary: kadu libkadu kadu-common kadu-dev kadu-themes Architecture: source amd64 all Version: 1.2-1 Distribution: unstable Urgency: medium Maintainer: Patryk Cisek pat...@debian.org Changed-By: Patryk Cisek pat...@debian.org Description: kadu - Gadu-Gadu/XMPP client for X11 kadu-common -
Bug#766462: with plymouth installed, I don't get any gettys on my VCs
Hi, Peter Palfrader wrote (06 Nov 2014 20:48:15 GMT) : On Thu, 06 Nov 2014, Peter Palfrader wrote: Did that, didn't get a logfile. } weasel@defiant:/var/log$ cat /proc/cmdline } BOOT_IMAGE=/vmlinuz-3.16-3-amd64 root=/dev/mapper/vg0-root ro splash quiet plymouth.debug } weasel@defiant:/var/log$ ls -l pl* } zsh: no matches found: pl* Strange. I do get /var/log/plymouth-debug.log when booting with plymouth.debug (current sid, amd64, plymouth 0.9.0-8). Maybe the content of /etc/plymouth/plymouthd.conf, and the output of these commands, would tell us more: for service in log quit quit-wait read-write start ; do systemctl status plymouth-$service.service done (after booting with splash plymouth.debug) Cheers, -- intrigeri -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#719519: marked as done (lua-json: Current version of lua-json conflicts with lpeg)
Your message dated Sat, 08 Nov 2014 15:56:26 + with message-id e1xn8ng-0001hw...@franck.debian.org and subject line Bug#719519: fixed in lua-json 1.3.2-1 has caused the Debian Bug report #719519, regarding lua-json: Current version of lua-json conflicts with lpeg 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.) -- 719519: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=719519 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: lua-json Version: 1.3-1 Severity: normal Dear Maintainer, My current version of lua-json does not play well with lua-lpeg. This is a known upstream problem. See this bug report: https://github.com/harningt/luajson/issues/27 The issue was since fixed upstream. Currently, attempting to load lua-json with lua-lpeg will result in the following error message on my Debian system: llua_load: /usr/share/lua/5.1/json/decode/strings.lua:102: loop body may accept empty string Please consider updating to the next minor version (1.3.2) of lua-json, which fixes this issue. My current lua-lpeg version is 0.12-1. The relevant upstream changelogs are: luajson v1.3.1 Release Notes User Visible Changes This release does not introduce many changes. François Perrad kindly produced patches to make it work better with Lua 5.2 and handle strict modes. It also introduces additional documentation about what varieties of Lua have been tested. luajson v1.3.2 Release Notes User Visible Changes One of the main changes in this release is compatibility with LPeg 0.12 and more sane _ENV manipulation to avoid problems in strict environments. The documentation has also been updated to reflect the behavior of the often-used 'merge' utility to avoid surprises in behavior. Thanks for maintaining lua-json! Cheers, A. -- System Information: Debian Release: jessie/sid APT prefers unstable APT policy: (600, 'unstable'), (500, 'stable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.10-2-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 Versions of packages lua-json depends on: ii lua-lpeg 0.12-1 lua-json recommends no packages. lua-json suggests no packages. -- no debconf information ---End Message--- ---BeginMessage--- Source: lua-json Source-Version: 1.3.2-1 We believe that the bug you reported is fixed in the latest version of lua-json, 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 719...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Bernd Zeimetz b...@debian.org (supplier of updated lua-json 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: Sat, 08 Nov 2014 16:31:39 +0100 Source: lua-json Binary: lua-json Architecture: source all Version: 1.3.2-1 Distribution: unstable Urgency: medium Maintainer: Bernd Zeimetz b...@debian.org Changed-By: Bernd Zeimetz b...@debian.org Description: lua-json - JSON decoder/encoder for Lua Closes: 719519 Changes: lua-json (1.3.2-1) unstable; urgency=medium . * [25eb09ad] Merge branch 'upstream' Closes: #719519 Merging upstream version 1.3.2 which is a bugfix release to make luajson work with lpeg again. It also sets _ENV to nil using local _ENV = nil to avoid global writing. Documentation and tests were updated accordingly and enhanced. * [b2bdecd4] Remove transitional package. Checksums-Sha1: 163d70d66b8f4bddd508350768e29930844728e9 1825 lua-json_1.3.2-1.dsc 3d74ee46f9873fe91e9bbfc0dc6efb54c87358eb 41575 lua-json_1.3.2.orig.tar.gz a8a9f8a2a56cdedcbf509076d5c4049815d7b910 2712 lua-json_1.3.2-1.debian.tar.xz e417a40394188a748d37daa08e452a84357c7825 27066 lua-json_1.3.2-1_all.deb Checksums-Sha256: eaa669631eafe088ffab03001d860b88f05efc7674ccf47122e2d77e4d4d9942 1825 lua-json_1.3.2-1.dsc b9e93f10ad800c5d526a2134f2fad98ec8732c92c352952b5e06aec787936afe 41575 lua-json_1.3.2.orig.tar.gz 86c2fe40995d85cb2e7ecd1487f30cec508e3f6bab8c7bd5fde4d0acd4a30bdf 2712 lua-json_1.3.2-1.debian.tar.xz
Bug#761565: marked as done (serf: FTBFS: TypeError: Directory /usr/include/mit-krb5 found where file expected)
Your message dated Sat, 08 Nov 2014 15:57:28 +
with message-id e1xn8og-0001ya...@franck.debian.org
and subject line Bug#760804: fixed in scons 2.3.1-2
has caused the Debian Bug report #760804,
regarding serf: FTBFS: TypeError: Directory /usr/include/mit-krb5 found where
file expected
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.)
--
760804: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=760804
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
---BeginMessage---
Source: serf
Version: 1.3.7-1
Severity: serious
Tags: jessie sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20140913 qa-ftbfs
Justification: FTBFS on amd64
Hi,
During a rebuild of all packages in sid, your package failed to build on
amd64.
Relevant part (hopefully):
debian/rules build
QUILT_PATCHES=debian/patches \
quilt --quiltrc /dev/null push -a || test $? = 2
Applying patch libtool
patching file SConstruct
Now at patch libtool
touch debian/stamp-patched
dh_testdir
scons GSSAPI=/usr CFLAGS=-g -O2 -fstack-protector-strong -Wformat
-Werror=format-security CPPFLAGS=-D_FORTIFY_SOURCE=2
LINKFLAGS=-Wl,-z,relro -Wl,-z,defs -Wl,--as-needed
scons: Reading SConscript files ...
TypeError: Directory /usr/include/mit-krb5 found where file expected.:
File /«PKGBUILDDIR»/SConstruct, line 360:
env.ParseConfig('$GSSAPI --cflags gssapi')
File /usr/lib/scons/SCons/Environment.py, line 1555:
return function(self, self.backtick(command))
File /usr/lib/scons/SCons/Environment.py, line 1550:
return env.MergeFlags(cmd, unique)
File /usr/lib/scons/SCons/Environment.py, line 814:
args = self.ParseFlags(args)
File /usr/lib/scons/SCons/Environment.py, line 800:
do_parse(arg)
File /usr/lib/scons/SCons/Environment.py, line 730:
dict['LIBS'].append(self.fs.File(arg))
File /usr/lib/scons/SCons/Node/FS.py, line 1340:
return self._lookup(name, directory, File, create)
File /usr/lib/scons/SCons/Node/FS.py, line 1319:
return root._lookup_abs(p, fsclass, create)
File /usr/lib/scons/SCons/Node/FS.py, line 2216:
result.diskcheck_match()
File /usr/lib/scons/SCons/Node/FS.py, line 2362:
Directory %s found where file expected.)
File /usr/lib/scons/SCons/Node/FS.py, line 385:
return self.func(*args, **kw)
File /usr/lib/scons/SCons/Node/FS.py, line 406:
raise TypeError(errorfmt % node.abspath)
make: *** [debian/stamp-build] Error 2
The full build log is available from:
http://aws-logs.debian.net/ftbfs-logs/2014/09/13/serf_1.3.7-1_unstable.log
A list of current common problems and possible solutions is available at
http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute!
About the archive rebuild: The rebuild was done on EC2 VM instances from
Amazon Web Services, using a clean, minimal and up-to-date chroot. Every
failed build was retried once to eliminate random failures.
---End Message---
---BeginMessage---
Source: scons
Source-Version: 2.3.1-2
We believe that the bug you reported is fixed in the latest version of
scons, 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 760...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Jörg Frings-Fürst deb...@jff-webhosting.net (supplier of updated scons
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: Sat, 08 Nov 2014 10:40:32 +0100
Source: scons
Binary: scons
Architecture: source all
Version: 2.3.1-2
Distribution: unstable
Urgency: medium
Maintainer: Jörg Frings-Fürst deb...@jff-webhosting.net
Changed-By: Jörg Frings-Fürst deb...@jff-webhosting.net
Description:
scons - replacement for make
Closes: 755496 760804 761565
Changes:
scons (2.3.1-2) unstable; urgency=medium
.
* New maintainer (Closes: #755496).
* debian/control:
- Set myself as maintainer.
- Set László Böszörményi as co-maintainer.
* Add debian/patch/scons-isystem.patch (Closes: #760804, #761565)
- add -isystem support to scons
Thanks to James McCoy james...@debian.org!
Checksums-Sha1:
3999ebba649a74521894f5b6d41312d2cf9e8b61 1886 scons_2.3.1-2.dsc
775e715e49fe5fd8e1d29551a296fdc9267509e7 499037
Bug#761565: marked as done (serf: FTBFS: TypeError: Directory /usr/include/mit-krb5 found where file expected)
Your message dated Sat, 08 Nov 2014 15:57:28 +
with message-id e1xn8og-0001yg...@franck.debian.org
and subject line Bug#761565: fixed in scons 2.3.1-2
has caused the Debian Bug report #761565,
regarding serf: FTBFS: TypeError: Directory /usr/include/mit-krb5 found where
file expected
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.)
--
761565: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=761565
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
---BeginMessage---
Source: serf
Version: 1.3.7-1
Severity: serious
Tags: jessie sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20140913 qa-ftbfs
Justification: FTBFS on amd64
Hi,
During a rebuild of all packages in sid, your package failed to build on
amd64.
Relevant part (hopefully):
debian/rules build
QUILT_PATCHES=debian/patches \
quilt --quiltrc /dev/null push -a || test $? = 2
Applying patch libtool
patching file SConstruct
Now at patch libtool
touch debian/stamp-patched
dh_testdir
scons GSSAPI=/usr CFLAGS=-g -O2 -fstack-protector-strong -Wformat
-Werror=format-security CPPFLAGS=-D_FORTIFY_SOURCE=2
LINKFLAGS=-Wl,-z,relro -Wl,-z,defs -Wl,--as-needed
scons: Reading SConscript files ...
TypeError: Directory /usr/include/mit-krb5 found where file expected.:
File /«PKGBUILDDIR»/SConstruct, line 360:
env.ParseConfig('$GSSAPI --cflags gssapi')
File /usr/lib/scons/SCons/Environment.py, line 1555:
return function(self, self.backtick(command))
File /usr/lib/scons/SCons/Environment.py, line 1550:
return env.MergeFlags(cmd, unique)
File /usr/lib/scons/SCons/Environment.py, line 814:
args = self.ParseFlags(args)
File /usr/lib/scons/SCons/Environment.py, line 800:
do_parse(arg)
File /usr/lib/scons/SCons/Environment.py, line 730:
dict['LIBS'].append(self.fs.File(arg))
File /usr/lib/scons/SCons/Node/FS.py, line 1340:
return self._lookup(name, directory, File, create)
File /usr/lib/scons/SCons/Node/FS.py, line 1319:
return root._lookup_abs(p, fsclass, create)
File /usr/lib/scons/SCons/Node/FS.py, line 2216:
result.diskcheck_match()
File /usr/lib/scons/SCons/Node/FS.py, line 2362:
Directory %s found where file expected.)
File /usr/lib/scons/SCons/Node/FS.py, line 385:
return self.func(*args, **kw)
File /usr/lib/scons/SCons/Node/FS.py, line 406:
raise TypeError(errorfmt % node.abspath)
make: *** [debian/stamp-build] Error 2
The full build log is available from:
http://aws-logs.debian.net/ftbfs-logs/2014/09/13/serf_1.3.7-1_unstable.log
A list of current common problems and possible solutions is available at
http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute!
About the archive rebuild: The rebuild was done on EC2 VM instances from
Amazon Web Services, using a clean, minimal and up-to-date chroot. Every
failed build was retried once to eliminate random failures.
---End Message---
---BeginMessage---
Source: scons
Source-Version: 2.3.1-2
We believe that the bug you reported is fixed in the latest version of
scons, 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 761...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Jörg Frings-Fürst deb...@jff-webhosting.net (supplier of updated scons
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: Sat, 08 Nov 2014 10:40:32 +0100
Source: scons
Binary: scons
Architecture: source all
Version: 2.3.1-2
Distribution: unstable
Urgency: medium
Maintainer: Jörg Frings-Fürst deb...@jff-webhosting.net
Changed-By: Jörg Frings-Fürst deb...@jff-webhosting.net
Description:
scons - replacement for make
Closes: 755496 760804 761565
Changes:
scons (2.3.1-2) unstable; urgency=medium
.
* New maintainer (Closes: #755496).
* debian/control:
- Set myself as maintainer.
- Set László Böszörményi as co-maintainer.
* Add debian/patch/scons-isystem.patch (Closes: #760804, #761565)
- add -isystem support to scons
Thanks to James McCoy james...@debian.org!
Checksums-Sha1:
3999ebba649a74521894f5b6d41312d2cf9e8b61 1886 scons_2.3.1-2.dsc
775e715e49fe5fd8e1d29551a296fdc9267509e7 499037
Bug#765671: marked as done (serf: FTBFS - TypeError: Directory /usr/include/mit-krb5 found where file expected.)
Your message dated Sat, 08 Nov 2014 15:57:28 +
with message-id e1xn8og-0001ya...@franck.debian.org
and subject line Bug#760804: fixed in scons 2.3.1-2
has caused the Debian Bug report #760804,
regarding serf: FTBFS - TypeError: Directory /usr/include/mit-krb5 found where
file expected.
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.)
--
760804: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=760804
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
---BeginMessage---
Package: serf
Version: 1.3.7-1
Severity: serious
Usertags: goto-cc
During a rebuild of all Debian packages in a clean sid chroot (using cowbuilder
and pbuilder) the build failed with the following error.
[...]
dh_testdir
scons GSSAPI=/usr CFLAGS=-g -O2 -fstack-protector-strong -Wformat
-Werror=format-security CPPFLAGS=-D_FORTIFY_SOURCE=2 LINKFLAGS=-Wl,-z,relro
-Wl,-z,defs -Wl,--as-needed
scons: Reading SConscript files ...
TypeError: Directory /usr/include/mit-krb5 found where file expected.:
File /srv/jenkins-slave/workspace/sid-goto-cc-serf/serf-1.3.7/SConstruct,
line 360:
env.ParseConfig('$GSSAPI --cflags gssapi')
File /usr/lib/scons/SCons/Environment.py, line 1555:
return function(self, self.backtick(command))
File /usr/lib/scons/SCons/Environment.py, line 1550:
return env.MergeFlags(cmd, unique)
File /usr/lib/scons/SCons/Environment.py, line 814:
args = self.ParseFlags(args)
File /usr/lib/scons/SCons/Environment.py, line 800:
do_parse(arg)
File /usr/lib/scons/SCons/Environment.py, line 730:
dict['LIBS'].append(self.fs.File(arg))
File /usr/lib/scons/SCons/Node/FS.py, line 1340:
return self._lookup(name, directory, File, create)
File /usr/lib/scons/SCons/Node/FS.py, line 1319:
return root._lookup_abs(p, fsclass, create)
File /usr/lib/scons/SCons/Node/FS.py, line 2216:
result.diskcheck_match()
File /usr/lib/scons/SCons/Node/FS.py, line 2362:
Directory %s found where file expected.)
File /usr/lib/scons/SCons/Node/FS.py, line 385:
return self.func(*args, **kw)
File /usr/lib/scons/SCons/Node/FS.py, line 406:
raise TypeError(errorfmt % node.abspath)
debian/rules:26: recipe for target 'debian/stamp-build' failed
make: *** [debian/stamp-build] Error 2
The full build log is attached; please do let me know if the problem is
unreproducible, in which case I shall try to investigate further. It seems,
however, that the s390 build fails with exactly the same error.
Best,
Michael
serf-build-log.txt.gz
Description: application/gunzip
pgpJcVIZARVoh.pgp
Description: PGP signature
---End Message---
---BeginMessage---
Source: scons
Source-Version: 2.3.1-2
We believe that the bug you reported is fixed in the latest version of
scons, 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 760...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Jörg Frings-Fürst deb...@jff-webhosting.net (supplier of updated scons
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: Sat, 08 Nov 2014 10:40:32 +0100
Source: scons
Binary: scons
Architecture: source all
Version: 2.3.1-2
Distribution: unstable
Urgency: medium
Maintainer: Jörg Frings-Fürst deb...@jff-webhosting.net
Changed-By: Jörg Frings-Fürst deb...@jff-webhosting.net
Description:
scons - replacement for make
Closes: 755496 760804 761565
Changes:
scons (2.3.1-2) unstable; urgency=medium
.
* New maintainer (Closes: #755496).
* debian/control:
- Set myself as maintainer.
- Set László Böszörményi as co-maintainer.
* Add debian/patch/scons-isystem.patch (Closes: #760804, #761565)
- add -isystem support to scons
Thanks to James McCoy james...@debian.org!
Checksums-Sha1:
3999ebba649a74521894f5b6d41312d2cf9e8b61 1886 scons_2.3.1-2.dsc
775e715e49fe5fd8e1d29551a296fdc9267509e7 499037 scons_2.3.1.orig.tar.gz
cd421dab4603916934dcde3669153d5cbbe2df73 100532 scons_2.3.1-2.debian.tar.xz
c50057f61ac8dcc5cd8ebf49f62457f82e37c9b9 518336 scons_2.3.1-2_all.deb
Checksums-Sha256:
f4f5402bc4a8bf1a07c1ad8f17de2500f9396a301b39901398825d8ac5473e12 1886
scons_2.3.1-2.dsc
Bug#760804: marked as done (serf: FTBFS: Directory /usr/include/mit-krb5 found where file expected.)
Your message dated Sat, 08 Nov 2014 15:57:28 +
with message-id e1xn8og-0001ya...@franck.debian.org
and subject line Bug#760804: fixed in scons 2.3.1-2
has caused the Debian Bug report #760804,
regarding serf: FTBFS: Directory /usr/include/mit-krb5 found where file
expected.
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.)
--
760804: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=760804
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
---BeginMessage---
Source: serf
Version: 1.3.7-1
Severity: serious
From my pbuilder build log:
...
scons GSSAPI=/usr CFLAGS=-g -O2 -fstack-protector-strong -Wformat
-Werror=format-security CPPFLAGS=-D_FORTIFY_SOURCE=2 LINKFLAGS=-Wl,-z,relro
-Wl,-z,defs -Wl,--as-needed
scons: Reading SConscript files ...
TypeError: Directory /usr/include/mit-krb5 found where file expected.:
File /tmp/buildd/serf-1.3.7/SConstruct, line 360:
env.ParseConfig('$GSSAPI --cflags gssapi')
File /usr/lib/scons/SCons/Environment.py, line 1555:
return function(self, self.backtick(command))
File /usr/lib/scons/SCons/Environment.py, line 1550:
return env.MergeFlags(cmd, unique)
File /usr/lib/scons/SCons/Environment.py, line 814:
args = self.ParseFlags(args)
File /usr/lib/scons/SCons/Environment.py, line 800:
do_parse(arg)
File /usr/lib/scons/SCons/Environment.py, line 730:
dict['LIBS'].append(self.fs.File(arg))
File /usr/lib/scons/SCons/Node/FS.py, line 1340:
return self._lookup(name, directory, File, create)
File /usr/lib/scons/SCons/Node/FS.py, line 1319:
return root._lookup_abs(p, fsclass, create)
File /usr/lib/scons/SCons/Node/FS.py, line 2216:
result.diskcheck_match()
File /usr/lib/scons/SCons/Node/FS.py, line 2362:
Directory %s found where file expected.)
File /usr/lib/scons/SCons/Node/FS.py, line 385:
return self.func(*args, **kw)
File /usr/lib/scons/SCons/Node/FS.py, line 406:
raise TypeError(errorfmt % node.abspath)
debian/rules:26: recipe for target 'debian/stamp-build' failed
make: *** [debian/stamp-build] Error 2
dpkg-buildpackage: error: debian/rules build gave error exit status 2
--
Daniel Schepler
---End Message---
---BeginMessage---
Source: scons
Source-Version: 2.3.1-2
We believe that the bug you reported is fixed in the latest version of
scons, 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 760...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Jörg Frings-Fürst deb...@jff-webhosting.net (supplier of updated scons
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: Sat, 08 Nov 2014 10:40:32 +0100
Source: scons
Binary: scons
Architecture: source all
Version: 2.3.1-2
Distribution: unstable
Urgency: medium
Maintainer: Jörg Frings-Fürst deb...@jff-webhosting.net
Changed-By: Jörg Frings-Fürst deb...@jff-webhosting.net
Description:
scons - replacement for make
Closes: 755496 760804 761565
Changes:
scons (2.3.1-2) unstable; urgency=medium
.
* New maintainer (Closes: #755496).
* debian/control:
- Set myself as maintainer.
- Set László Böszörményi as co-maintainer.
* Add debian/patch/scons-isystem.patch (Closes: #760804, #761565)
- add -isystem support to scons
Thanks to James McCoy james...@debian.org!
Checksums-Sha1:
3999ebba649a74521894f5b6d41312d2cf9e8b61 1886 scons_2.3.1-2.dsc
775e715e49fe5fd8e1d29551a296fdc9267509e7 499037 scons_2.3.1.orig.tar.gz
cd421dab4603916934dcde3669153d5cbbe2df73 100532 scons_2.3.1-2.debian.tar.xz
c50057f61ac8dcc5cd8ebf49f62457f82e37c9b9 518336 scons_2.3.1-2_all.deb
Checksums-Sha256:
f4f5402bc4a8bf1a07c1ad8f17de2500f9396a301b39901398825d8ac5473e12 1886
scons_2.3.1-2.dsc
091ab468f8e6084c30f3ae9fd48828e3884021401cfef4b713d13161ba120201 499037
scons_2.3.1.orig.tar.gz
ba8cebfa034445b9c71eb5ee71bee758c93bfda8b3f41a670797d92bb93366f3 100532
scons_2.3.1-2.debian.tar.xz
f15051003cf309eda7ab1b7699cb14a6dc15e2b726d7a823321faa6d442da132 518336
scons_2.3.1-2_all.deb
Files:
8a1a53dc7f7d8d808a4fb8b10bb3ef45 1886 devel optional scons_2.3.1-2.dsc
60a3cfb98b661df9f4406c61b5686bd7 499037 devel optional scons_2.3.1.orig.tar.gz
4968afcfd0dc36651748c37e2f25f1f5
Bug#765671: marked as done (serf: FTBFS - TypeError: Directory /usr/include/mit-krb5 found where file expected.)
Your message dated Sat, 08 Nov 2014 15:57:28 +
with message-id e1xn8og-0001yg...@franck.debian.org
and subject line Bug#761565: fixed in scons 2.3.1-2
has caused the Debian Bug report #761565,
regarding serf: FTBFS - TypeError: Directory /usr/include/mit-krb5 found where
file expected.
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.)
--
761565: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=761565
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
---BeginMessage---
Package: serf
Version: 1.3.7-1
Severity: serious
Usertags: goto-cc
During a rebuild of all Debian packages in a clean sid chroot (using cowbuilder
and pbuilder) the build failed with the following error.
[...]
dh_testdir
scons GSSAPI=/usr CFLAGS=-g -O2 -fstack-protector-strong -Wformat
-Werror=format-security CPPFLAGS=-D_FORTIFY_SOURCE=2 LINKFLAGS=-Wl,-z,relro
-Wl,-z,defs -Wl,--as-needed
scons: Reading SConscript files ...
TypeError: Directory /usr/include/mit-krb5 found where file expected.:
File /srv/jenkins-slave/workspace/sid-goto-cc-serf/serf-1.3.7/SConstruct,
line 360:
env.ParseConfig('$GSSAPI --cflags gssapi')
File /usr/lib/scons/SCons/Environment.py, line 1555:
return function(self, self.backtick(command))
File /usr/lib/scons/SCons/Environment.py, line 1550:
return env.MergeFlags(cmd, unique)
File /usr/lib/scons/SCons/Environment.py, line 814:
args = self.ParseFlags(args)
File /usr/lib/scons/SCons/Environment.py, line 800:
do_parse(arg)
File /usr/lib/scons/SCons/Environment.py, line 730:
dict['LIBS'].append(self.fs.File(arg))
File /usr/lib/scons/SCons/Node/FS.py, line 1340:
return self._lookup(name, directory, File, create)
File /usr/lib/scons/SCons/Node/FS.py, line 1319:
return root._lookup_abs(p, fsclass, create)
File /usr/lib/scons/SCons/Node/FS.py, line 2216:
result.diskcheck_match()
File /usr/lib/scons/SCons/Node/FS.py, line 2362:
Directory %s found where file expected.)
File /usr/lib/scons/SCons/Node/FS.py, line 385:
return self.func(*args, **kw)
File /usr/lib/scons/SCons/Node/FS.py, line 406:
raise TypeError(errorfmt % node.abspath)
debian/rules:26: recipe for target 'debian/stamp-build' failed
make: *** [debian/stamp-build] Error 2
The full build log is attached; please do let me know if the problem is
unreproducible, in which case I shall try to investigate further. It seems,
however, that the s390 build fails with exactly the same error.
Best,
Michael
serf-build-log.txt.gz
Description: application/gunzip
pgpRTRdUsS1h8.pgp
Description: PGP signature
---End Message---
---BeginMessage---
Source: scons
Source-Version: 2.3.1-2
We believe that the bug you reported is fixed in the latest version of
scons, 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 761...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Jörg Frings-Fürst deb...@jff-webhosting.net (supplier of updated scons
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: Sat, 08 Nov 2014 10:40:32 +0100
Source: scons
Binary: scons
Architecture: source all
Version: 2.3.1-2
Distribution: unstable
Urgency: medium
Maintainer: Jörg Frings-Fürst deb...@jff-webhosting.net
Changed-By: Jörg Frings-Fürst deb...@jff-webhosting.net
Description:
scons - replacement for make
Closes: 755496 760804 761565
Changes:
scons (2.3.1-2) unstable; urgency=medium
.
* New maintainer (Closes: #755496).
* debian/control:
- Set myself as maintainer.
- Set László Böszörményi as co-maintainer.
* Add debian/patch/scons-isystem.patch (Closes: #760804, #761565)
- add -isystem support to scons
Thanks to James McCoy james...@debian.org!
Checksums-Sha1:
3999ebba649a74521894f5b6d41312d2cf9e8b61 1886 scons_2.3.1-2.dsc
775e715e49fe5fd8e1d29551a296fdc9267509e7 499037 scons_2.3.1.orig.tar.gz
cd421dab4603916934dcde3669153d5cbbe2df73 100532 scons_2.3.1-2.debian.tar.xz
c50057f61ac8dcc5cd8ebf49f62457f82e37c9b9 518336 scons_2.3.1-2_all.deb
Checksums-Sha256:
f4f5402bc4a8bf1a07c1ad8f17de2500f9396a301b39901398825d8ac5473e12 1886
scons_2.3.1-2.dsc
Bug#760804: marked as done (serf: FTBFS: Directory /usr/include/mit-krb5 found where file expected.)
Your message dated Sat, 08 Nov 2014 15:57:28 +
with message-id e1xn8og-0001yg...@franck.debian.org
and subject line Bug#761565: fixed in scons 2.3.1-2
has caused the Debian Bug report #761565,
regarding serf: FTBFS: Directory /usr/include/mit-krb5 found where file
expected.
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.)
--
761565: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=761565
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
---BeginMessage---
Source: serf
Version: 1.3.7-1
Severity: serious
From my pbuilder build log:
...
scons GSSAPI=/usr CFLAGS=-g -O2 -fstack-protector-strong -Wformat
-Werror=format-security CPPFLAGS=-D_FORTIFY_SOURCE=2 LINKFLAGS=-Wl,-z,relro
-Wl,-z,defs -Wl,--as-needed
scons: Reading SConscript files ...
TypeError: Directory /usr/include/mit-krb5 found where file expected.:
File /tmp/buildd/serf-1.3.7/SConstruct, line 360:
env.ParseConfig('$GSSAPI --cflags gssapi')
File /usr/lib/scons/SCons/Environment.py, line 1555:
return function(self, self.backtick(command))
File /usr/lib/scons/SCons/Environment.py, line 1550:
return env.MergeFlags(cmd, unique)
File /usr/lib/scons/SCons/Environment.py, line 814:
args = self.ParseFlags(args)
File /usr/lib/scons/SCons/Environment.py, line 800:
do_parse(arg)
File /usr/lib/scons/SCons/Environment.py, line 730:
dict['LIBS'].append(self.fs.File(arg))
File /usr/lib/scons/SCons/Node/FS.py, line 1340:
return self._lookup(name, directory, File, create)
File /usr/lib/scons/SCons/Node/FS.py, line 1319:
return root._lookup_abs(p, fsclass, create)
File /usr/lib/scons/SCons/Node/FS.py, line 2216:
result.diskcheck_match()
File /usr/lib/scons/SCons/Node/FS.py, line 2362:
Directory %s found where file expected.)
File /usr/lib/scons/SCons/Node/FS.py, line 385:
return self.func(*args, **kw)
File /usr/lib/scons/SCons/Node/FS.py, line 406:
raise TypeError(errorfmt % node.abspath)
debian/rules:26: recipe for target 'debian/stamp-build' failed
make: *** [debian/stamp-build] Error 2
dpkg-buildpackage: error: debian/rules build gave error exit status 2
--
Daniel Schepler
---End Message---
---BeginMessage---
Source: scons
Source-Version: 2.3.1-2
We believe that the bug you reported is fixed in the latest version of
scons, 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 761...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Jörg Frings-Fürst deb...@jff-webhosting.net (supplier of updated scons
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: Sat, 08 Nov 2014 10:40:32 +0100
Source: scons
Binary: scons
Architecture: source all
Version: 2.3.1-2
Distribution: unstable
Urgency: medium
Maintainer: Jörg Frings-Fürst deb...@jff-webhosting.net
Changed-By: Jörg Frings-Fürst deb...@jff-webhosting.net
Description:
scons - replacement for make
Closes: 755496 760804 761565
Changes:
scons (2.3.1-2) unstable; urgency=medium
.
* New maintainer (Closes: #755496).
* debian/control:
- Set myself as maintainer.
- Set László Böszörményi as co-maintainer.
* Add debian/patch/scons-isystem.patch (Closes: #760804, #761565)
- add -isystem support to scons
Thanks to James McCoy james...@debian.org!
Checksums-Sha1:
3999ebba649a74521894f5b6d41312d2cf9e8b61 1886 scons_2.3.1-2.dsc
775e715e49fe5fd8e1d29551a296fdc9267509e7 499037 scons_2.3.1.orig.tar.gz
cd421dab4603916934dcde3669153d5cbbe2df73 100532 scons_2.3.1-2.debian.tar.xz
c50057f61ac8dcc5cd8ebf49f62457f82e37c9b9 518336 scons_2.3.1-2_all.deb
Checksums-Sha256:
f4f5402bc4a8bf1a07c1ad8f17de2500f9396a301b39901398825d8ac5473e12 1886
scons_2.3.1-2.dsc
091ab468f8e6084c30f3ae9fd48828e3884021401cfef4b713d13161ba120201 499037
scons_2.3.1.orig.tar.gz
ba8cebfa034445b9c71eb5ee71bee758c93bfda8b3f41a670797d92bb93366f3 100532
scons_2.3.1-2.debian.tar.xz
f15051003cf309eda7ab1b7699cb14a6dc15e2b726d7a823321faa6d442da132 518336
scons_2.3.1-2_all.deb
Files:
8a1a53dc7f7d8d808a4fb8b10bb3ef45 1886 devel optional scons_2.3.1-2.dsc
60a3cfb98b661df9f4406c61b5686bd7 499037 devel optional scons_2.3.1.orig.tar.gz
4968afcfd0dc36651748c37e2f25f1f5
Bug#768599: man-db: cycle found while processing triggers:
package: man-db severity: serious x-debbugs-cc: debian-d...@lists.debian.org Hi, I'm not 100% sure the following issue is caused by man-db, please reassign appropriatly if it is not. https://jenkins.debian.net/job/chroot-installation_wheezy_install_education- networked_upgrade_to_jessie/2/console Setting up startpar (0.59-3) ... Installing new version of config file /etc/init/startpar-bridge.conf ... dpkg: cycle found while processing triggers: chain of packages whose triggers are or may be responsible: man-db - man-db packages' pending triggers which are or may be unresolvable: man-db: /usr/share/man dpkg: error processing package man-db (--configure): triggers looping, abandoned Setting up sysvinit-utils (2.88dsf-57) ... Errors were encountered while processing: man-db E: Sub-process /usr/bin/dpkg returned an error code (1) cheers, Holger signature.asc Description: This is a digitally signed message part.
Bug#768598: font-config: cycle found while processing triggers
package: font-config severity: serious x-debbugs-cc: debian-d...@lists.debian.org Hi, I'm not 100% sure the following issue is caused by font-config, please reassign appropriatly if it is not. https://jenkins.debian.net/job/chroot-installation_wheezy_install_education- desktop-kde_upgrade_to_jessie/2//console Setting up libgl1-mesa-glx:amd64 (10.3.2-1) ... dpkg: cycle found while processing triggers: chain of packages whose triggers are or may be responsible: fontconfig - fontconfig packages' pending triggers which are or may be unresolvable: fontconfig: /usr/share/fonts shared-mime-info: /usr/share/mime/packages libc-bin: ldconfig gconf2: /usr/share/gconf/schemas dpkg: error processing package fontconfig (--configure): triggers looping, abandoned Setting up fontconfig-config (2.11.0-6.1) ... cheers, Holger signature.asc Description: This is a digitally signed message part.
Bug#768600: readahead-fedora: cycle found while processing triggers
package: readahead-fedora severity: serious x-debbugs-cc: debian-d...@lists.debian.org Hi, I'm not 100% sure the following issue is caused by readahead-fedora, please reassign appropriatly if it is not. (eg or is it man-db?) https://jenkins.debian.net/job/chroot-installation_wheezy_install_education- standalone_upgrade_to_jessie/2/console found the following problem: Processing triggers for man-db (2.7.0.2-2) ... dpkg: cycle found while processing triggers: chain of packages whose triggers are or may be responsible: readahead-fedora - readahead-fedora packages' pending triggers which are or may be unresolvable: fontconfig: /usr/share/fonts readahead-fedora: /etc/init.d dpkg: error processing package fontconfig (--configure): triggers looping, abandoned dpkg: ../../src/packages.c:226: process_queue: Assertion `dependtry = 4' failed. sh: 1: /usr/sbin/update-alternatives: not found E: Sub-process /usr/bin/dpkg exited unexpectedly https://jenkins.debian.net/job/chroot-installation_wheezy_install_education- desktop-gnome_upgrade_to_jessie/2//console shows a very similar error: Processing triggers for man-db (2.7.0.2-2) ... dpkg: cycle found while processing triggers: chain of packages whose triggers are or may be responsible: readahead-fedora - readahead-fedora packages' pending triggers which are or may be unresolvable: gnome-menus: /usr/share/applications readahead-fedora: /etc/init.d gconf2: /usr/share/gconf/defaults dpkg: error processing package gnome-menus (--configure): triggers looping, abandoned dpkg: ../../src/packages.c:226: process_queue: Assertion `dependtry = 4' failed. sh: 1: /usr/sbin/update-alternatives: not found https://jenkins.debian.net/job/chroot-installation_wheezy_install_education- common_upgrade_to_jessie/2//console shows another error: Processing triggers for man-db (2.7.0.2-2) ... dpkg: cycle found while processing triggers: chain of packages whose triggers are or may be responsible: readahead-fedora - readahead-fedora packages' pending triggers which are or may be unresolvable: readahead-fedora: /etc/init.d dpkg: error processing package readahead-fedora (--configure): triggers looping, abandoned [...] Errors were encountered while processing: readahead-fedora E: Sub-process /usr/bin/dpkg returned an error code (1) cheers, Holger signature.asc Description: This is a digitally signed message part.
Processed: tagging 768541
Processing commands for cont...@bugs.debian.org: tags 768541 + moreinfo Bug #768541 [python2.7] AttributeError: 'module' object has no attribute 'POP3_SSL' Added tag(s) moreinfo. thanks Stopping processing here. Please contact me if you need assistance. -- 768541: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=768541 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#765010: Please include latest version of usbmuxd in JEssie
Hi, The version of usbmuxd currently inunstable 1.0.8+git20140527.e72f2f7-1 is the only one among those provided by Debian that lets one use Linux with aniOS 7 or later device, because of the tru_st dialog issue. As I understand it, this versionof usbmuxd does not compileon kfreesd, but please let the versions for the other platforms gointo Jessie. Thanks a lot, Shérab. -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#708942: marked as done ([gprbuild] GFDL non free file with front cover)
Your message dated Sat, 08 Nov 2014 16:22:37 + with message-id e1xn8mb-0005jt...@franck.debian.org and subject line Bug#708942: fixed in gprbuild 2014dfsg-1 has caused the Debian Bug report #708942, regarding [gprbuild] GFDL non free file with front cover 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.) -- 708942: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=708942 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: gprbuild user: debian...@lists.debian.org usertags: gfdl-invariant severity: serious The files have front cover and thus non free: doc/gprbuild_ug.texi doc/html/gprbuild_ug.html doc/info/gprbuild_ug.info doc/txt/gprbuild_ug.txt Thanks Bastien ---End Message--- ---BeginMessage--- Source: gprbuild Source-Version: 2014dfsg-1 We believe that the bug you reported is fixed in the latest version of gprbuild, 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 708...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Nicolas Boulenguez nico...@debian.org (supplier of updated gprbuild 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: Sat, 08 Nov 2014 12:15:55 +0100 Source: gprbuild Binary: gprbuild gprbuild-doc Architecture: source all Version: 2014dfsg-1 Distribution: unstable Urgency: medium Maintainer: Nicolas Boulenguez nico...@debian.org Changed-By: Nicolas Boulenguez nico...@debian.org Description: gprbuild - multi-language extensible build tool gprbuild-doc - multi-language extensible build tool (documentation) Closes: 708942 Changes: gprbuild (2014dfsg-1) unstable; urgency=medium . * Repackage without GFDL documentation. Closes: #708942. - copyright: use Files-Excluded to remove the doc/subdir. Do not provide license stanza for removed doc/texiplus.tex. - control: not installing gprbuild_gps.xml at all fixes #768214 better than the Break/Replace dependencies introduced by 2014-5. - rules, gprbuild-doc.*, patches/*: do not build or install docs. - gprbuild-doc.examples: as install-indep does nothing, take examples from examples/* directly instead of debian/tmp/*. - update descriptions: control, gprbuild.1, README.source, README.Debian. - re-enable some source lintian checks related to GFDL. * gprbuild-doc.TODO: postpone unrelated changes for after the freeze. Checksums-Sha1: 92e9ed6a5cd20d902f88b2ec54c028552e19c0c2 2104 gprbuild_2014dfsg-1.dsc 39c51527d176b851643e06ba942f1467786cb44a 1499247 gprbuild_2014dfsg.orig.tar.gz 70b3c9418aed3a195c4a179a630fe7b2dd31a051 16912 gprbuild_2014dfsg-1.debian.tar.xz 3b2fc4ec858338b1c82021343fd1e652d6dd0d2b 56216 gprbuild-doc_2014dfsg-1_all.deb Checksums-Sha256: 4e29deb4c6f8a362ee35ac39eb724f5903d2aeadfe47e08d21dbf01bac6374f5 2104 gprbuild_2014dfsg-1.dsc 409fe34d78a59ae27be1ecd55259e2816a46bd92a5bce458cab4c7807694674f 1499247 gprbuild_2014dfsg.orig.tar.gz 62e5f30b2809d728444c41e47d33df5f71b370495e27b6e41675db5b9e5d2f0d 16912 gprbuild_2014dfsg-1.debian.tar.xz 6bbacfc2836286ec5448c5367cdb2bc5ed59ffad834792d7fea6859ee47f95fd 56216 gprbuild-doc_2014dfsg-1_all.deb Files: 21011f7a7e52ae4a68bfc3a304429289 2104 devel optional gprbuild_2014dfsg-1.dsc e681f01ecc4365b11821299c030fa0c9 1499247 devel optional gprbuild_2014dfsg.orig.tar.gz 44885ab75eb539fa434081f15ffc0df1 16912 devel optional gprbuild_2014dfsg-1.debian.tar.xz ebcc569508697072ebdc906743ae271c 56216 doc optional gprbuild-doc_2014dfsg-1_all.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1 iQIcBAEBCAAGBQJUXj7hAAoJELUqnPRJDfyN+b8P/31owBlNjTWKdyNRJz4b6/8R /xNXxJwMn6ZsRjPU8bwjyP6OwgkFAW7OLbiIeIPlJHAi1eKTYSGp+W0KmfNx3gEm FrwYbNNj00jzfv/UGHQ7xmW9bccS5eFqztPXgm6fCHuvbGy0nR7QbjIUbg1cn6KO gWW+JFVgr8bUqi/L+Rl+VBu5uzqyP6hmqw+WBmFnheOu+GFLVWhMHtgSvqYFS1Rp buOtShYjey3XIB7KlfNvK+zbbQ+CuvjTjXG3Gr4Xi+nnUMkWOFtk7KjumN3PZ8fe krTnRZxyKra45znpvH09C8aH3AgxdkbjMtAf+8q5o0iS1QkCfeDS9mDb+J6R366t mTX5/D4+hA9ouEGgOQywltgp/5HnuF0Iticyd7vLjeHcIiUWg/xksqYbeShTGNX/ K0kI4q0dlqL7I0a3ZY6AQ+qy3klQEsK1CyWLloMfhgUmiR32kSefRKieuYr68NER /A9jL2eZ6NkkZFlhyWyRwQPXJg2tiMYMtHNgQpVSsyTnUgvRYDOkyvaE4x092y5Z
Bug#766754: marked as done (gdb: FTBFS: GDB_TARGET value is not a valid Debian architecture)
Your message dated Sat, 08 Nov 2014 16:22:04 + with message-id e1xn8m4-0005f4...@franck.debian.org and subject line Bug#766754: fixed in gdb 7.7.1+dfsg-4 has caused the Debian Bug report #766754, regarding gdb: FTBFS: GDB_TARGET value is not a valid Debian architecture 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.) -- 766754: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=766754 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Source: gdb Version: 7.7.1+dfsg-3 Severity: serious From my pbuilder build log: ... fakeroot debian/rules clean debian/rules:59: *** GDB_TARGET value is not a valid Debian architecture. Stop. dpkg-buildpackage: error: fakeroot debian/rules clean gave error exit status 2 -- Daniel Schepler ---End Message--- ---BeginMessage--- Source: gdb Source-Version: 7.7.1+dfsg-4 We believe that the bug you reported is fixed in the latest version of gdb, 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. Hector Oron zu...@debian.org (supplier of updated gdb 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: Fri, 07 Nov 2014 17:05:49 +0100 Source: gdb Binary: gdb gdb-minimal gdb64 gdb-multiarch gdbserver gdb-source gdb-dbg Architecture: source all i386 Version: 7.7.1+dfsg-4 Distribution: unstable Urgency: medium Maintainer: Héctor Orón Martínez zu...@debian.org Changed-By: Hector Oron zu...@debian.org Description: gdb- GNU Debugger gdb-dbg- GNU Debugger (debug package) gdb-minimal - GNU Debugger (minimal version) gdb-multiarch - GNU Debugger (with support for multiple architectures) gdb-source - GNU Debugger (source) gdb64 - GNU Debugger (64-bit) gdbserver - GNU Debugger (remote server) Closes: 766754 Changes: gdb (7.7.1+dfsg-4) unstable; urgency=medium . * d/rules: fix FTBFS on newer dpkg changes. (Closes: #766754) * d/sanitize-gdb.sh: Don't assume input is .tar.bz2 Checksums-Sha1: afc8cd44f05c9888f5bee37f1b3cf69e1e129be0 2783 gdb_7.7.1+dfsg-4.dsc e98a9893418384057e18045651ebdeb9d5fffa44 70656 gdb_7.7.1+dfsg-4.debian.tar.xz a9361e6fa93c94d2c5efdbf97f26bb029f05631e 24080402 gdb-source_7.7.1+dfsg-4_all.deb a5fc4d783a1379c5615292d3794f3f448571fea0 2184138 gdb_7.7.1+dfsg-4_i386.deb afc442726dcef153da13d7000fec62536dec6da0 1965506 gdb-minimal_7.7.1+dfsg-4_i386.deb a0bfd7efadb9edafc3716f519e21ab75673bd345 1667020 gdb64_7.7.1+dfsg-4_i386.deb eab35d21a47e215ad90613b42c4d6b0310bf6781 3036476 gdb-multiarch_7.7.1+dfsg-4_i386.deb 6a2258e21e3eba0dbb03c3d19ce8e5d7ef7eb014 255174 gdbserver_7.7.1+dfsg-4_i386.deb 87deaa3e3a9ab3bda3ef6cfa34caa2e626136bff 15110780 gdb-dbg_7.7.1+dfsg-4_i386.deb Checksums-Sha256: 5281b8b175ad101732c6e52972f5e2f0cb6f23b8bc887c5243cca627e90fe5c1 2783 gdb_7.7.1+dfsg-4.dsc a94198935432170eeabdeda2b062e069ec0b8fca209950470fb15667d86bea03 70656 gdb_7.7.1+dfsg-4.debian.tar.xz 79039fd209ec3040705d9eaab3d4762128e9e3319d05fa9274c74547e38da293 24080402 gdb-source_7.7.1+dfsg-4_all.deb 648e4f5e92003eb19c92c773993fabe65d8ba2b22cfe087a429b17327335e187 2184138 gdb_7.7.1+dfsg-4_i386.deb 163beba4ab8f3d6afbc8138b4f7d232bbf46cb71c9e313515a6d8f224a2bb0ac 1965506 gdb-minimal_7.7.1+dfsg-4_i386.deb 9b814756dcff431897a9e4e487a69be4174251cb87521a38a49f1fb9a19b5fb8 1667020 gdb64_7.7.1+dfsg-4_i386.deb 2c16bfcc9a2aa39a95f791f7d16e17d662f0efcea22094247113385a295dacb0 3036476 gdb-multiarch_7.7.1+dfsg-4_i386.deb 008826423eb70c8a17c57b90793cfdf9e7c5ee91a4391a56ddbd532e98f39ce6 255174 gdbserver_7.7.1+dfsg-4_i386.deb 7fcd43ea216e8e15e867679ace1235928da40f8958373f2bf104839cb07adbc1 15110780 gdb-dbg_7.7.1+dfsg-4_i386.deb Files: 4c8509c031373cb1c30466c007067f1a 2783 devel optional gdb_7.7.1+dfsg-4.dsc 9891cd0341ba632bf76b2e3e70a8f6db 70656 devel optional gdb_7.7.1+dfsg-4.debian.tar.xz 00fdcff22ee62d6b1ace8d99ba076f41 24080402 devel optional gdb-source_7.7.1+dfsg-4_all.deb 1b15c1338b95b16f7ef3c5bdda365913 2184138 devel optional gdb_7.7.1+dfsg-4_i386.deb b45ead7479322d2e2a0810ce11c8653d 1965506 devel optional gdb-minimal_7.7.1+dfsg-4_i386.deb 1b82adf909455e7a5a49bcfdc0769d60
Bug#768599: man-db: cycle found while processing triggers:
On 08/11/14 16:05, Holger Levsen wrote: package: man-db severity: serious x-debbugs-cc: debian-d...@lists.debian.org Hi, I'm not 100% sure the following issue is caused by man-db, please reassign appropriatly if it is not. https://jenkins.debian.net/job/chroot-installation_wheezy_install_education- networked_upgrade_to_jessie/2/console Setting up startpar (0.59-3) ... Installing new version of config file /etc/init/startpar-bridge.conf ... dpkg: cycle found while processing triggers: chain of packages whose triggers are or may be responsible: man-db - man-db packages' pending triggers which are or may be unresolvable: man-db: /usr/share/man dpkg: error processing package man-db (--configure): triggers looping, abandoned Setting up sysvinit-utils (2.88dsf-57) ... Errors were encountered while processing: man-db E: Sub-process /usr/bin/dpkg returned an error code (1) This is probably because that was running dpkg 1.16.15, which suffers from bugs such as #765434. So I think this is a fixed bug in dpkg and can be closed. Emilio -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#768599: man-db: cycle found while processing triggers:
On Sat, Nov 08, 2014 at 04:50:36PM +, Emilio Pozuelo Monfort wrote: This is probably because that was running dpkg 1.16.15, which suffers from bugs such as #765434. I thought that at first, but doesn't the log show it configuring dpkg 1.17.21 and then starting a new dpkg run well before it gets to this point? -- Colin Watson [cjwat...@debian.org] -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#768599: man-db: cycle found while processing triggers:
Control: reassign -1 dpkg 1.17.21 On Sat, Nov 08, 2014 at 04:05:17PM +, Holger Levsen wrote: package: man-db severity: serious x-debbugs-cc: debian-d...@lists.debian.org Hi, I'm not 100% sure the following issue is caused by man-db, please reassign appropriatly if it is not. https://jenkins.debian.net/job/chroot-installation_wheezy_install_education- networked_upgrade_to_jessie/2/console Setting up startpar (0.59-3) ... Installing new version of config file /etc/init/startpar-bridge.conf ... dpkg: cycle found while processing triggers: chain of packages whose triggers are or may be responsible: man-db - man-db packages' pending triggers which are or may be unresolvable: man-db: /usr/share/man dpkg: error processing package man-db (--configure): triggers looping, abandoned Setting up sysvinit-utils (2.88dsf-57) ... Errors were encountered while processing: man-db E: Sub-process /usr/bin/dpkg returned an error code (1) This has got to be a dpkg bug. There's no good reason for a package not to be able to trigger itself, and this has worked for ages. -- Colin Watson [cjwat...@debian.org] -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed: Re: Bug#768599: man-db: cycle found while processing triggers:
Processing control commands: reassign -1 dpkg 1.17.21 Bug #768599 [man-db] man-db: cycle found while processing triggers: Bug reassigned from package 'man-db' to 'dpkg'. Ignoring request to alter found versions of bug #768599 to the same values previously set Ignoring request to alter fixed versions of bug #768599 to the same values previously set Bug #768599 [dpkg] man-db: cycle found while processing triggers: Marked as found in versions dpkg/1.17.21. -- 768599: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=768599 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#767401: marked as done (pandas: FTBFS on several archs)
Your message dated Sat, 8 Nov 2014 22:00:35 +0500 with message-id 20141108170035.ga28...@belkar.wrar.name and subject line Re: Bug#767401: pandas: FTBFS on several archs has caused the Debian Bug report #767401, regarding pandas: FTBFS on several archs 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.) -- 767401: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=767401 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- package: pandas version: 0.15.0-1 severity: serious Hi, The latest upload of pandas fails on a number of architectures, but it built fine before. This prevents migration to testing. https://buildd.debian.org/status/package.php?p=pandas Cheers, Ivo ---End Message--- ---BeginMessage--- Version: 0.15.0-2 According to https://buildd.debian.org/status/package.php?p=pandas the package version 0.15.0-2 builds fine on all release arches. -- WBR, wRAR signature.asc Description: Digital signature ---End Message---
Bug#768203: sblim-wbemcli: fails to upgrade from 'wheezy' - trying to overwrite /usr/bin/wbemcli
Andreas Beckmann a...@debian.org and Bernd Zeimetz be...@bzed.de writes: Breaks: python-pywbem ( 0.8.0~dev650-1~) Replaces: python-pywbem ( 0.8.0~dev650-1~) OK. Footnote 53 brought up an example with a file being moved between related packages, which made me read more into Breaks+Replaces than there is. Thanks for patiently explaining the obvious. I added these lines and uploaded to mentors: https://mentors.debian.net/package/sblim-wbemcli (Too bad I missed the new upstream release just before the freeze.) Would one of you please sponsor it into unstable? I'll ask for a freeze exception once it landed. -- Thanks, Feri. -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#767400: python3-websocket: patches
Hi,
Patch disabling shipping the tests module, should be pushed upstream
as well.
--- setup.py 2014-11-08 15:32:01.138317096 +
+++ ../websocket-client-0.18.0-orig/setup.py 2014-09-03 23:23:30.0 +0100
@@ -36,8 +36,9 @@
keywords='websockets',
scripts=[bin/wsdump.py],
install_requires=install_requires,
-packages=[websocket],
+packages=[tests, websocket],
package_data={
+'tests': ['data/*.txt'],
'websocket': [cacert.pem]
},
)
This allows cleaning up the rules file, patch:
--- debian/rules 2014-11-08 15:26:36.789584171 +
+++ ../websocket-client-0.18.0-orig/debian/rules 2014-08-20 23:09:14.0 +0100
@@ -8,4 +8,5 @@
override_dh_install:
mv $(CURDIR)/debian/python-websocket/usr/bin/wsdump.py $(CURDIR)/debian/python-websocket/usr/bin/wsdump
mv $(CURDIR)/debian/python3-websocket/usr/bin/wsdump.py $(CURDIR)/debian/python3-websocket/usr/bin/wsdump3
+ rm -r $(CURDIR)/debian/python-websocket/usr/lib/python*/dist-packages/tests
dh_install
Bug#766492: libecap: FTBFS: Makefile.am: error: required file './NEWS' not found
Control: tags -1 + patch upstream On Thu, Oct 23, 2014 at 04:30:14PM +0200, Sebastian Ramacher wrote: | Makefile.am: installing './INSTALL' | Makefile.am: error: required file './NEWS' not found | Makefile.am: error: required file './AUTHORS' not found | Makefile.am: error: required file './ChangeLog' not found | Makefile.am: installing './COPYING' using GNU General Public License v3 file | Makefile.am: Consider adding the COPYING file to the version control system | Makefile.am: for your code, to avoid questions about which license your project uses | automake: warning: autoconf input should be named 'configure.ac', not 'configure.in' | autoreconf: automake failed with exit status: 1 | dh_autoreconf: autoreconf -f -i returned exit code 1 | make: *** [debian/autoreconf.after] Error 2 This is one of cases where the package FTBFS on all arches but still the maintainer has uploaded some binary, apparently built from something different from the uploaded source. The debdiff is attached, I'm ready to do a NMU if the maintainer doesn't have time. You should send the patch to the upstream too. -- WBR, wRAR diff -Nru libecap-0.2.0/debian/changelog libecap-0.2.0/debian/changelog --- libecap-0.2.0/debian/changelog 2014-10-21 15:43:41.0 +0600 +++ libecap-0.2.0/debian/changelog 2014-11-08 22:14:11.0 +0500 @@ -1,3 +1,10 @@ +libecap (0.2.0-2.1) unstable; urgency=medium + + * Non-maintainer upload. + * Enable 'foreign' automake option (Closes: #766492). + + -- Andrey Rahmatullin w...@debian.org Sat, 08 Nov 2014 22:12:47 +0500 + libecap (0.2.0-2) unstable; urgency=low * Fix FTBFS on new ports, thanks to Breno Leitao (Closes: #748292) diff -Nru libecap-0.2.0/debian/patches/automake-foreign.patch libecap-0.2.0/debian/patches/automake-foreign.patch --- libecap-0.2.0/debian/patches/automake-foreign.patch 1970-01-01 05:00:00.0 +0500 +++ libecap-0.2.0/debian/patches/automake-foreign.patch 2014-11-08 22:11:44.0 +0500 @@ -0,0 +1,16 @@ +Description: Set the foreign option for automake +Author: Andrey Rahmatullin w...@debian.org +Bug-Debian: https://bugs.debian.org/766492 +Last-Update: 2014-11-08 + +--- libecap-0.2.0.orig/configure.in libecap-0.2.0/configure.in +@@ -14,7 +14,7 @@ AC_CONFIG_SRCDIR([src/libecap/adapter/se + AC_CONFIG_HEADERS(src/libecap/common/ac-autoconf.h) + AX_PREFIX_CONFIG_H(src/libecap/common/autoconf.h) + +-AM_INIT_AUTOMAKE([nostdinc]) ++AM_INIT_AUTOMAKE([nostdinc foreign]) + AM_MAINTAINER_MODE + + LT_INIT diff -Nru libecap-0.2.0/debian/patches/series libecap-0.2.0/debian/patches/series --- libecap-0.2.0/debian/patches/series 1970-01-01 05:00:00.0 +0500 +++ libecap-0.2.0/debian/patches/series 2014-11-08 22:05:56.0 +0500 @@ -0,0 +1 @@ +automake-foreign.patch signature.asc Description: Digital signature
Bug#768203: sblim-wbemcli: fails to upgrade from 'wheezy' - trying to overwrite /usr/bin/wbemcli
On 2014-11-08 18:05, Ferenc Wagner wrote: there is. Thanks for patiently explaining the obvious. I added these lines and uploaded to mentors: Would one of you please sponsor it into unstable? I'll ask for a freeze exception once it landed. Uploaded with a slightly more verbose changelog entry: ... that shipped /usr/bin/wbemcli, too. Andreas -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed: Re: Bug#766492: libecap: FTBFS: Makefile.am: error: required file './NEWS' not found
Processing control commands: tags -1 + patch upstream Bug #766492 [src:libecap] libecap: FTBFS: Makefile.am: error: required file './NEWS' not found Added tag(s) upstream and patch. -- 766492: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=766492 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed: reassign 766943 to systemd
Processing commands for cont...@bugs.debian.org: reassign 766943 systemd Bug #766943 [ifupdown] systemd: server no longer gets networking after switching to systemd Bug reassigned from package 'ifupdown' to 'systemd'. Ignoring request to alter found versions of bug #766943 to the same values previously set Ignoring request to alter fixed versions of bug #766943 to the same values previously set thanks Stopping processing here. Please contact me if you need assistance. -- 766943: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=766943 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#768203: marked as done (sblim-wbemcli: fails to upgrade from 'wheezy' - trying to overwrite /usr/bin/wbemcli)
Your message dated Sat, 08 Nov 2014 17:39:15 + with message-id e1xn9yl-0001ee...@franck.debian.org and subject line Bug#768203: fixed in sblim-wbemcli 1.6.2-9 has caused the Debian Bug report #768203, regarding sblim-wbemcli: fails to upgrade from 'wheezy' - trying to overwrite /usr/bin/wbemcli 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.) -- 768203: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=768203 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: sblim-wbemcli Version: 1.6.2-8 Severity: serious User: debian...@lists.debian.org Usertags: piuparts Hi, during a test with piuparts I noticed your package fails to upgrade from 'wheezy'. It installed fine in 'wheezy', then the upgrade to 'jessie' fails because it tries to overwrite other packages files without declaring a Breaks+Replaces relation. See policy 7.6 at http://www.debian.org/doc/debian-policy/ch-relationships.html#s-replaces From the attached log (scroll to the bottom...): Selecting previously unselected package sblim-wbemcli. Unpacking sblim-wbemcli (from .../sblim-wbemcli_1.6.2-8_amd64.deb) ... dpkg: error processing /var/cache/apt/archives/sblim-wbemcli_1.6.2-8_amd64.deb (--unpack): trying to overwrite '/usr/bin/wbemcli', which is also in package python-pywbem 0.7.0-4 dpkg-deb: error: subprocess paste was killed by signal (Broken pipe) Errors were encountered while processing: /var/cache/apt/archives/sblim-wbemcli_1.6.2-8_amd64.deb cheers, Andreas python-pywbem=0.7.0-4_sblim-wbemcli=1.6.2-8.log.gz Description: application/gzip ---End Message--- ---BeginMessage--- Source: sblim-wbemcli Source-Version: 1.6.2-9 We believe that the bug you reported is fixed in the latest version of sblim-wbemcli, 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 768...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Ferenc Wágner wf...@niif.hu (supplier of updated sblim-wbemcli 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: Sat, 08 Nov 2014 17:09:21 +0100 Source: sblim-wbemcli Binary: sblim-wbemcli sblim-wbemcli-dbg Architecture: source Version: 1.6.2-9 Distribution: unstable Urgency: medium Maintainer: Ferenc Wágner wf...@niif.hu Changed-By: Ferenc Wágner wf...@niif.hu Description: sblim-wbemcli - WBEM Command Line Interface for CIMOM access sblim-wbemcli-dbg - debugging symbols for sblim-wbemcli Closes: 768203 Changes: sblim-wbemcli (1.6.2-9) unstable; urgency=medium . * Declare Breaks+Replaces python-pywbem ( 0.8.0~dev650-1~) that shipped /usr/bin/wbemcli, too. (Closes: #768203) Checksums-Sha1: 54293dd70ddf1e763268a100e6418d7c0d607b4d 1888 sblim-wbemcli_1.6.2-9.dsc 1fd37c514cb7ba4c4f90d7ec10e17455bd6ec48e 9066 sblim-wbemcli_1.6.2-9.debian.tar.bz2 Checksums-Sha256: 185b9a39df25aa3f5cd20e4f7173d97e0c78761a606ff7d1c96f8e84f165c8dd 1888 sblim-wbemcli_1.6.2-9.dsc c029f310a1676a679146fbcaae442eecaecd08379b56b0273f62736e4f2ace65 9066 sblim-wbemcli_1.6.2-9.debian.tar.bz2 Files: 36029cee5505adc20c1f78248b1defd9 1888 admin optional sblim-wbemcli_1.6.2-9.dsc a1f4796fb64a26aab36bcc4f3df8631e 9066 admin optional sblim-wbemcli_1.6.2-9.debian.tar.bz2 -BEGIN PGP SIGNATURE- Version: GnuPG v1 iQIcBAEBCAAGBQJUXk/4AAoJEF+zP5NZ6e0IIkkP/RH2hOeZENh2US5B3bK6+FRX 5QyHbERVAaSRl3/8Gc3L+c1ytUhNXP0SrBDH8uOsnmCyocEoXE3fFHqDYuI/ZaUW IsizLLXpvHWigNJt1y/Z5NRkRkFRfMgzEbtBsDhMqsKwAg1DX7cMM3KGR1laGQsZ w8fFYn741GfAVuZebYQ4n9SoQco3WV1dEeRSCHx8BxvYD7WN3uWYh/CpxpkaTQQK Hsx4xCM5u56HbdHLFavagW54eWgJ9aJJHDMJxyjYb09OIBi9xmgj5MIJqz3cIf0t PwbLsSt9ZYEdgX1rFPRHK76hPwgMCEBylWOUskn7ZqLU72lf6WLb8zwPDy6uZSYE cZpdr3B2IaW/XxYhOLYyEp2xPViN38q3M9ngGo+C4QacGjAkVu9kXc9DEti4wVaY peLrtspx70vnCKSf4KEWnPVcBUskqI/Fn/3mgOQY+DDqg636e8oVkc7WPJp96OMT sU3+iM2QMWwuHOXdTK7J0rhWl5oB3btM78LpH/FIva1xJLmhrJUXIiAYzuatuUjC iVQ3JELYQ/J8FwlpqNdzIOYIwYpJ3qLQ+ttCoq56Gt4oxX9YEoGhGrTWplSu8ez0 0fQA6HKmfnCptmqe1Ej9pS3K3htFJjxVyDcz3yFxKm6bae20BwxspJd825bCm84y gIUplv41UeeToah6DUg+ =f10Q -END PGP SIGNATUREEnd Message---
Processed: retitle 759949 to help_fr.docbook:292: parser error
Processing commands for cont...@bugs.debian.org: retitle 759949 help_fr.docbook:292: parser error Bug #759949 [src:kwave] kwave: FTBFS: rsvg missing Changed Bug title to 'help_fr.docbook:292: parser error' from 'kwave: FTBFS: rsvg missing' thanks Stopping processing here. Please contact me if you need assistance. -- 759949: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=759949 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#768599: man-db: cycle found while processing triggers:
Hi! On Sat, 2014-11-08 at 16:56:33 +, Colin Watson wrote: Control: reassign -1 dpkg 1.17.21 On Sat, Nov 08, 2014 at 04:05:17PM +, Holger Levsen wrote: package: man-db severity: serious x-debbugs-cc: debian-d...@lists.debian.org I'm not 100% sure the following issue is caused by man-db, please reassign appropriatly if it is not. https://jenkins.debian.net/job/chroot-installation_wheezy_install_education- networked_upgrade_to_jessie/2/console Setting up startpar (0.59-3) ... Installing new version of config file /etc/init/startpar-bridge.conf ... dpkg: cycle found while processing triggers: chain of packages whose triggers are or may be responsible: man-db - man-db packages' pending triggers which are or may be unresolvable: man-db: /usr/share/man dpkg: error processing package man-db (--configure): triggers looping, abandoned Setting up sysvinit-utils (2.88dsf-57) ... Errors were encountered while processing: man-db E: Sub-process /usr/bin/dpkg returned an error code (1) This has got to be a dpkg bug. There's no good reason for a package not to be able to trigger itself, and this has worked for ages. That's because (according to the log), the man-db package being triggered (version 2.6.2-1) is the one still using the awaiting interest directive, which got switched to interest-noawait in 2.6.3-6. I'll have to add Breaks for any such packages. :/ But I'm not sure how much that might make the upgrade more difficult, as dpkg contains already many Breaks/Conflicts. Thanks, Guillem -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#766943: reassign 766943 to systemd
On Sat, 2014-11-08 at 18:20 +0100, Andrew Shadura wrote: I don't think it's right that the bug is assigned at ifupdown. Neither ifupdown nor its init scripts make any assumptions regarding init system being used, so I don't see how is it more helpful to have me dealing with this, but not systemd maintainers. I'd be happy to apply a fix if one appears at some point, but to me it looks more like there's something elsewhere. Well but you remember the other two bugs, which are more or less similar and which also happened when I was still using sysvinit? btw: One more thing about the issue itself. Even the sleep seems not to prevent that some daemons do not fully bind to their configured addresses or not start at all. Kinda weird the whole thing... smime.p7s Description: S/MIME cryptographic signature
Bug#766273: picosat and undertaker: error when trying to install together
On Sat, Nov 08, 2014 at 16:37:18 +0100, Stefan Hengelein wrote: Hi, we have an in-tree variant of the PicoSAT because the newer, reentrant version of picosat is around 30% slower for our usage than the one we're currently using (936). However, the picomus export is done for compatibility reasons. The output format was changed several times and the version 954 and 959 have some problems with argument passing and reading from stdin. These problems are solved with 960 but 960 was just released a few weeks ago. So we could use either 936 or 960 and i thought hat was a elegant way to solve the problem. But i didn't think it might cause conflicts here. [...] So would it help if I upgraded picosat to version 960? I suppose we might get an unblock as 1) picosat shouldn't disrupt any other packages and 2) we'd be fixing an RC bug. Please just let me know, I'm happy to upgrade. Best, Michael pgpGiKc5ebUgQ.pgp Description: PGP signature
Bug#768203: sblim-wbemcli: fails to upgrade from 'wheezy' - trying to overwrite /usr/bin/wbemcli
Thanks much. Unblock request filed as #768610. -- Feri. -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed: limit source to rubberband, tagging 768270
Processing commands for cont...@bugs.debian.org: limit source rubberband Limiting to bugs with field 'source' containing at least one of 'rubberband' Limit currently set to 'source':'rubberband' tags 768270 + pending Bug #768270 [librubberband-dev,rubberband-ladspa,rubberband-vamp] librubberband-dev: unhandled symlink to directory conversion: /usr/share/doc/PACKAGE Added tag(s) pending. thanks Stopping processing here. Please contact me if you need assistance. -- 768270: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=768270 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#766273: picosat and undertaker: error when trying to install together
That doesn't sound like a bad idea at all. I'm not sure if going via unstable or experimental is best at this point, but either way, this would allow us preparing a package that links against the system picosat again. Reinhard On November 8, 2014 12:47:45 PM EST, Michael Tautschnig m...@debian.org wrote: On Sat, Nov 08, 2014 at 16:37:18 +0100, Stefan Hengelein wrote: Hi, we have an in-tree variant of the PicoSAT because the newer, reentrant version of picosat is around 30% slower for our usage than the one we're currently using (936). However, the picomus export is done for compatibility reasons. The output format was changed several times and the version 954 and 959 have some problems with argument passing and reading from stdin. These problems are solved with 960 but 960 was just released a few weeks ago. So we could use either 936 or 960 and i thought hat was a elegant way to solve the problem. But i didn't think it might cause conflicts here. [...] So would it help if I upgraded picosat to version 960? I suppose we might get an unblock as 1) picosat shouldn't disrupt any other packages and 2) we'd be fixing an RC bug. Please just let me know, I'm happy to upgrade. Best, Michael -- Diese Nachricht wurde von meinem Android-Mobiltelefon mit K-9 Mail gesendet.
Bug#768612: ruby-bogus: FTBFS in jessie: build-dependency not installable: ruby-activerecord-nulldb-adapter
Source: ruby-bogus Version: 0.1.5-2 Severity: serious Tags: jessie sid User: debian...@lists.debian.org Usertags: qa-ftbfs-20141108 qa-ftbfs Justification: FTBFS in jessie on amd64 Hi, During a rebuild of all packages in jessie (in a jessie chroot, not a sid chroot), your package failed to build on amd64. Relevant part (hopefully): ┌──┐ │ Install ruby-bogus build dependencies (apt-based resolver) │ └──┘ Installing build dependencies Reading package lists... Building dependency tree... Reading state information... Some packages could not be installed. This may mean that you have requested an impossible situation or if you are using the unstable distribution that some required packages have not yet been created or been moved out of Incoming. The following information may help to resolve the situation: The following packages have unmet dependencies: sbuild-build-depends-ruby-bogus-dummy : Depends: ruby-activerecord-nulldb-adapter but it is not installable E: Unable to correct problems, you have held broken packages. apt-get failed. The full build log is available from: http://aws-logs.debian.net/ftbfs-logs/2014/11/08/ruby-bogus_0.1.5-2_jessie.log A list of current common problems and possible solutions is available at http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute! About the archive rebuild: The rebuild was done on EC2 VM instances from Amazon Web Services, using a clean, minimal and up-to-date chroot. Every failed build was retried once to eliminate random failures. -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#768619: proofgeneral: FTBFS in jessie: build-dependency not installable: emacs23-nox
Source: proofgeneral Version: 4.3~pre131011-0.1 Severity: serious Tags: jessie sid User: debian...@lists.debian.org Usertags: qa-ftbfs-20141108 qa-ftbfs Justification: FTBFS in jessie on amd64 Hi, During a rebuild of all packages in jessie (in a jessie chroot, not a sid chroot), your package failed to build on amd64. Relevant part (hopefully): ┌──┐ │ Install proofgeneral build dependencies (apt-based resolver) │ └──┘ Installing build dependencies Reading package lists... Building dependency tree... Reading state information... Some packages could not be installed. This may mean that you have requested an impossible situation or if you are using the unstable distribution that some required packages have not yet been created or been moved out of Incoming. The following information may help to resolve the situation: The following packages have unmet dependencies: sbuild-build-depends-proofgeneral-dummy : Depends: emacs23-nox but it is not installable E: Unable to correct problems, you have held broken packages. apt-get failed. The full build log is available from: http://aws-logs.debian.net/ftbfs-logs/2014/11/08/proofgeneral_4.3~pre131011-0.1_jessie.log A list of current common problems and possible solutions is available at http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute! About the archive rebuild: The rebuild was done on EC2 VM instances from Amazon Web Services, using a clean, minimal and up-to-date chroot. Every failed build was retried once to eliminate random failures. -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#768615: ruby-pygments.rb: FTBFS in jessie: ERROR: Test ruby2.1 failed: Running tests for ruby2.1 using debian/ruby-tests.rb...
Source: ruby-pygments.rb
Version: 0.5.4~ds1-1
Severity: serious
Tags: jessie sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20141108 qa-ftbfs
Justification: FTBFS in jessie on amd64
Hi,
During a rebuild of all packages in jessie (in a jessie chroot, not a
sid chroot), your package failed to build on amd64.
Relevant part (hopefully):
Running tests for ruby2.1 using debian/ruby-tests.rb...
Run options:
# Running tests:
FE..
Finished tests in 10.040664s, 4.7806 tests/s, 9.5611 assertions/s.
1) Failure:
PygmentsHighlightTest#test_highlight_works_with_larger_files
[/«PKGBUILDDIR»/test/test_pygments.rb:35]:
454107 expected but was
455203.
2) Error:
PygmentsHighlightTest#test_highlight_works_with_single_character_input:
MentosError: Traceback (most recent call last):
File /«PKGBUILDDIR»/lib/pygments/mentos.py, line 304, in start
res = self.get_data(method, lexer, args, kwargs, text)
File /«PKGBUILDDIR»/lib/pygments/mentos.py, line 172, in get_data
res = self.highlight_text(text, lexer, formatter_name, args,
_convert_keys(opts))
File /«PKGBUILDDIR»/lib/pygments/mentos.py, line 123, in highlight_text
lexer = self.return_lexer(lexer, args, kwargs, code)
File /«PKGBUILDDIR»/lib/pygments/mentos.py, line 103, in return_lexer
return lexers.guess_lexer(code, **inputs)
File /usr/lib/python2.7/dist-packages/pygments/lexers/__init__.py, line
250, in guess_lexer
raise ClassNotFound('no lexer matching the text found')
ClassNotFound: no lexer matching the text found
/«PKGBUILDDIR»/lib/pygments/popen.rb:386:in `header_to_json'
/«PKGBUILDDIR»/lib/pygments/popen.rb:268:in `handle_header_and_return'
/«PKGBUILDDIR»/lib/pygments/popen.rb:243:in `block in mentos'
/usr/lib/ruby/2.1.0/timeout.rb:91:in `block in timeout'
/usr/lib/ruby/2.1.0/timeout.rb:35:in `block in catch'
/usr/lib/ruby/2.1.0/timeout.rb:35:in `catch'
/usr/lib/ruby/2.1.0/timeout.rb:35:in `catch'
/usr/lib/ruby/2.1.0/timeout.rb:106:in `timeout'
/«PKGBUILDDIR»/lib/pygments/popen.rb:214:in `mentos'
/«PKGBUILDDIR»/lib/pygments/popen.rb:197:in `highlight'
/«PKGBUILDDIR»/test/test_pygments.rb:91:in
`test_highlight_works_with_single_character_input'
/usr/lib/ruby/2.1.0/minitest/unit.rb:1265:in `run'
/usr/lib/ruby/2.1.0/test/unit/testcase.rb:17:in `run'
/usr/lib/ruby/2.1.0/minitest/unit.rb:940:in `block in _run_suite'
/usr/lib/ruby/2.1.0/minitest/unit.rb:933:in `map'
/usr/lib/ruby/2.1.0/minitest/unit.rb:933:in `_run_suite'
/usr/lib/ruby/2.1.0/test/unit.rb:663:in `block in _run_suites'
/usr/lib/ruby/2.1.0/test/unit.rb:661:in `each'
/usr/lib/ruby/2.1.0/test/unit.rb:661:in `_run_suites'
/usr/lib/ruby/2.1.0/minitest/unit.rb:884:in `_run_anything'
/usr/lib/ruby/2.1.0/minitest/unit.rb:1092:in `run_tests'
/usr/lib/ruby/2.1.0/minitest/unit.rb:1079:in `block in _run'
/usr/lib/ruby/2.1.0/minitest/unit.rb:1078:in `each'
/usr/lib/ruby/2.1.0/minitest/unit.rb:1078:in `_run'
/usr/lib/ruby/2.1.0/minitest/unit.rb:1066:in `run'
/usr/lib/ruby/2.1.0/test/unit.rb:27:in `run'
/usr/lib/ruby/2.1.0/test/unit.rb:780:in `run'
/usr/lib/ruby/2.1.0/test/unit.rb:372:in `block (2 levels) in autorun'
/usr/lib/ruby/2.1.0/test/unit.rb:33:in `run_once'
/usr/lib/ruby/2.1.0/test/unit.rb:371:in `block in autorun'
48 tests, 96 assertions, 1 failures, 1 errors, 0 skips
ruby -v: ruby 2.1.4p265 (2014-10-27) [x86_64-linux-gnu]
rake aborted!
Command failed with status (2): [ruby -Ilib -rubygems
-I/usr/lib/ruby/vendor_ruby
/usr/lib/ruby/vendor_ruby/rake/rake_test_loader.rb test/test_pygments.rb ]
Tasks: TOP = default = test
(See full trace by running task with --trace)
ERROR: Test ruby2.1 failed:
The full build log is available from:
http://aws-logs.debian.net/ftbfs-logs/2014/11/08/ruby-pygments.rb_0.5.4~ds1-1_jessie.log
A list of current common problems and possible solutions is available at
http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute!
About the archive rebuild: The rebuild was done on EC2 VM instances from
Amazon Web Services, using a clean, minimal and up-to-date chroot. Every
failed build was retried once to eliminate random failures.
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#768616: dbuskit: FTBFS in jessie: cp: cannot stat 'debian/tmp/usr/lib/GNUstep/Frameworks/DBusKit.framework/Resources': No such file or directory
Source: dbuskit Version: 0.1.1-1 Severity: serious Tags: jessie sid User: debian...@lists.debian.org Usertags: qa-ftbfs-20141108 qa-ftbfs Justification: FTBFS in jessie on amd64 Hi, During a rebuild of all packages in jessie (in a jessie chroot, not a sid chroot), your package failed to build on amd64. Relevant part (hopefully): make[1]: Entering directory '/«PKGBUILDDIR»' This is gnustep-make 2.6.6. Type 'make print-gnustep-make-help' for help. Making all in Source ... Making build-headers for framework DBusKit... Making all for framework DBusKit... make[4]: Nothing to be done for 'internal-framework-compile'. Making all in Tools ... ln -s ../Source/DBusKit.framework/Versions/Current/Headers DBusKit Making all for tool dk_make_protocol... make[5]: Nothing to be done for 'internal-tool-compile'. Making all in Documentation ... Making all for doc DBusKit... make[3]: Nothing to be done for 'internal-doc-all'. Making all for textdoc INSTALL... make[3]: Nothing to be done for 'internal-textdoc-all'. Making all for textdoc README... make[3]: Nothing to be done for 'internal-textdoc-all'. Making all for textdoc ANNOUNCE... make[3]: Nothing to be done for 'internal-textdoc-all'. Making install in Source ... Making install for framework DBusKit... Creating /«PKGBUILDDIR»/debian/tmp//usr/lib/GNUstep/Frameworks... Creating /«PKGBUILDDIR»/debian/tmp//usr/include/GNUstep... Installing framework DBusKit... Installing headers... Making install in Tools ... Making install for tool dk_make_protocol... Creating /«PKGBUILDDIR»/debian/tmp//usr/bin/ Installing tool dk_make_protocol... Making install in Documentation ... Making install for doc DBusKit... Creating /«PKGBUILDDIR»/debian/tmp//usr/share/GNUstep/Documentation/Developer/DBusKit/ProgrammingManual... Creating /«PKGBUILDDIR»/debian/tmp//usr/share/info... if [ -f DBusKit.pdf ]; then \ /usr/bin/install -c -p -m 644 DBusKit.pdf \ /«PKGBUILDDIR»/debian/tmp//usr/share/GNUstep/Documentation/Developer/DBusKit/ProgrammingManual; \ fi if [ -f DBusKit.info ]; then \ /usr/bin/install -c -p -m 644 DBusKit.info* /«PKGBUILDDIR»/debian/tmp//usr/share/info; \ fi if [ -f iDBusKit/DBusKit_toc.html ]; then \ /usr/bin/install -c -p -m 644 DBusKit/DBusKit_*.html \ /«PKGBUILDDIR»/debian/tmp//usr/share/GNUstep/Documentation/Developer/DBusKit/ProgrammingManual; \ fi if [ -f DBusKit/DBusKit.html ]; then \ /usr/bin/install -c -p -m 644 DBusKit/DBusKit.html \ /«PKGBUILDDIR»/debian/tmp//usr/share/GNUstep/Documentation/Developer/DBusKit/ProgrammingManual; \ /usr/bin/install -c -p -m 644 DBusKit/DBusKit_*.html \ /«PKGBUILDDIR»/debian/tmp//usr/share/GNUstep/Documentation/Developer/DBusKit/ProgrammingManual || true; \ fi if [ -f DBusKit/index.html ]; then \ /usr/share/GNUstep/Makefiles/mkinstalldirs /«PKGBUILDDIR»/debian/tmp//usr/share/GNUstep/Documentation/Developer/DBusKit/ProgrammingManual/DBusKit; \ /usr/bin/install -c -p -m 644 DBusKit/*.html \ /«PKGBUILDDIR»/debian/tmp//usr/share/GNUstep/Documentation/Developer/DBusKit/ProgrammingManual/DBusKit; \ fi Installing doc DBusKit... Making install for textdoc INSTALL... Creating /«PKGBUILDDIR»/debian/tmp//usr/share/GNUstep/Documentation/Developer/DBusKit/ReleaseNotes/0.1.1... Making install for textdoc README... Making install for textdoc ANNOUNCE... rm -rf /«PKGBUILDDIR»/debian/tmp//usr/share/GNUstep/Documentation/Developer/DBusKit/Reference /usr/share/GNUstep/Makefiles/mkinstalldirs /«PKGBUILDDIR»/debian/tmp//usr/share/GNUstep/Documentation/Developer/DBusKit/Reference (cd Reference; tar cf - .) | \ (cd /«PKGBUILDDIR»/debian/tmp//usr/share/GNUstep/Documentation/Developer/DBusKit/Reference; tar xf -) make[1]: Leaving directory '/«PKGBUILDDIR»' dh_install cp: cannot stat 'debian/tmp/usr/lib/GNUstep/Frameworks/DBusKit.framework/Resources': No such file or directory dh_install: cp -a debian/tmp/usr/lib/GNUstep/Frameworks/DBusKit.framework/Resources debian/libdbuskit0//usr/lib/GNUstep/Frameworks/DBusKit.framework/ returned exit code 1 debian/rules:12: recipe for target 'binary' failed make: *** [binary] Error 2 The full build log is available from: http://aws-logs.debian.net/ftbfs-logs/2014/11/08/dbuskit_0.1.1-1_jessie.log A list of current common problems and possible solutions is available at http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute! About the archive rebuild: The rebuild was done on EC2 VM instances from Amazon Web Services, using a clean, minimal and up-to-date chroot. Every failed build was retried once to eliminate random failures. -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
