Processed: Re: Bug#784597: xserver-xorg-core: ABI mismatch?
Processing commands for cont...@bugs.debian.org: reassign 784597 src:xserver-xorg-video-intel Bug #784597 [xserver-xorg-core] xserver-xorg-core: ABI mismatch? Bug reassigned from package 'xserver-xorg-core' to 'src:xserver-xorg-video-intel'. No longer marked as found in versions xorg-server/2:1.17.1-2. Ignoring request to alter fixed versions of bug #784597 to the same values previously set forcemerge 78 784597 Bug #78 [src:xserver-xorg-video-intel] xserver-xorg-video-intel: FTBFS with Xorg 1.17 Bug #784597 [src:xserver-xorg-video-intel] xserver-xorg-core: ABI mismatch? Set Bug forwarded-to-address to 'https://bugs.freedesktop.org/show_bug.cgi?id=84901'. Severity set to 'serious' from 'normal' Marked as fixed in versions xserver-xorg-video-intel/2:2.99.916+git20141119-1~exp1. Marked as found in versions xserver-xorg-video-intel/2:2.21.15-2. Added tag(s) sid and stretch. Merged 78 784597 thanks Stopping processing here. Please contact me if you need assistance. -- 78: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=78 784597: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=784597 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: gnome-terminal: random crash when searching for some terminal font
Processing control commands: found -1 3.14.5-1 Bug #748469 [libgtk-3-0] libgtk-3-0: random crash when searching for some font Marked as found in versions gtk+3.0/3.14.5-1. severity -1 grave Bug #748469 [libgtk-3-0] libgtk-3-0: random crash when searching for some font Severity set to 'grave' from 'important' -- 748469: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=748469 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: tagging 784625
Processing commands for cont...@bugs.debian.org: tags 784625 + upstream Bug #784625 [evolution] evolution: crash on start [Arithmetic exception in e_day_view_convert_position_in_main_canvas at e-day-view.c:8158] Added tag(s) upstream. thanks Stopping processing here. Please contact me if you need assistance. -- 784625: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=784625 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#784440: onioncat: fails to install due to insserv rejecting the script header: Service tor has to be enabled to start service onioncat
Hi, Andreas Beckmann wrote (06 May 2015 11:35:46 GMT) : Package: onioncat Version: 0.2.2+svn566-1 during a test with piuparts I noticed your package failed to install due to insserv rejecting the script header. Some notes are available from at https://wiki.debian.org/LSBInitScripts I had noticed this problem a couple hours earlier, and uploaded 0.2.2+svn566-2 with a fix. Now waiting for piuparts.d.o to catch up, to test it again and to confirm that the fix is correct :) Thanks for your QA work! 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#784258: marked as done (cpl-plugin-*-calib: fails to download from ftp://ftp.eso.org)
Your message dated Thu, 07 May 2015 09:35:01 + with message-id e1yqicr-0005se...@franck.debian.org and subject line Bug#784258: fixed in cpl-plugin-amber 4.3.3+dfsg-2 has caused the Debian Bug report #784258, regarding cpl-plugin-*-calib: fails to download from ftp://ftp.eso.org 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.) -- 784258: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=784258 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: cpl-plugin-amber-calib,cpl-plugin-giraf-calib,cpl-plugin-xshoo-calib Version: 4.3.3+dfsg-1 Severity: serious User: debian...@lists.debian.org Usertags: piuparts Hi, during a test with piuparts I noticed your package failed to install. As per definition of the release team this makes the package too buggy for a release, thus the severity. From the attached log (scroll to the bottom...): Selecting previously unselected package cpl-plugin-amber-calib. (Reading database ... (Reading database ... 7694 files and directories currently installed.) Preparing to unpack .../cpl-plugin-amber-calib_4.3.3+dfsg-1_all.deb ... Unpacking cpl-plugin-amber-calib (4.3.3+dfsg-1) ... Setting up cpl-plugin-amber-calib (4.3.3+dfsg-1) ... --2015-05-04 14:07:48-- ftp://ftp.eso.org/pub/dfs/pipelines/amber/amber-kit-4.3.3.tar.gz = '-' Resolving ftp.eso.org (ftp.eso.org)... 134.171.42.54, 134.171.42.53 Connecting to ftp.eso.org (ftp.eso.org)|134.171.42.54|:21... connected. Logging in as anonymous ... Logged in! == SYST ... done.== PWD ... done. == TYPE I ... done. == CWD (1) /pub/dfs/pipelines/amber ... done. == SIZE amber-kit-4.3.3.tar.gz ... done. == PASV ... done.== RETR amber-kit-4.3.3.tar.gz ... No such file 'amber-kit-4.3.3.tar.gz'. gzip: stdin: unexpected end of file tar: Child returned status 1 tar: Error is not recoverable: exiting now gzip: stdin: unexpected end of file tar: Child returned status 1 tar: Error is not recoverable: exiting now dpkg: error processing package cpl-plugin-amber-calib (--configure): subprocess installed post-installation script returned error exit status 2 Errors were encountered while processing: cpl-plugin-amber-calib Looks like stuff got repacked, there is e.g. ftp://ftp.eso.org/pub/dfs/pipelines/amber/amber-kit-4.3.3-1.tar.gz Same problems for the other downloader packages. cheers, Andreas cpl-plugin-amber-calib_4.3.3+dfsg-1.log.gz Description: application/gzip ---End Message--- ---BeginMessage--- Source: cpl-plugin-amber Source-Version: 4.3.3+dfsg-2 We believe that the bug you reported is fixed in the latest version of cpl-plugin-amber, 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 784...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Ole Streicher oleb...@debian.org (supplier of updated cpl-plugin-amber 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: Thu, 07 May 2015 09:56:26 +0200 Source: cpl-plugin-amber Binary: cpl-plugin-amber cpl-plugin-amber-doc cpl-plugin-amber-calib Architecture: source all amd64 Version: 4.3.3+dfsg-2 Distribution: unstable Urgency: low Maintainer: Debian Astronomy Maintainers debian-astro-maintain...@lists.alioth.debian.org Changed-By: Ole Streicher oleb...@debian.org Description: cpl-plugin-amber - ESO data reduction pipeline for AMBER cpl-plugin-amber-calib - ESO data reduction pipeline calibration data downloader for AMBER cpl-plugin-amber-doc - ESO data reduction pipeline documentation for AMBER Closes: 784258 Changes: cpl-plugin-amber (4.3.3+dfsg-2) unstable; urgency=low . * Loop over all possible upstream package names when downloading calibration data. Closes: #784258 * Add astropy dependency to CI test to make it work Checksums-Sha1: 6b0dfb2246bd1827c082d21f34986de6c12d5ff7 2359 cpl-plugin-amber_4.3.3+dfsg-2.dsc 53b3f5a290e47a7f11a8c777dcba2559b834a1da 9236 cpl-plugin-amber_4.3.3+dfsg-2.debian.tar.xz 81e361c90f27d2a82d70586cf53ad9868cdbe1e0 51412 cpl-plugin-amber-doc_4.3.3+dfsg-2_all.deb df07388b7d234ce65d95eb509a683fa07ae7a18a 13670 cpl-plugin-amber-calib_4.3.3+dfsg-2_all.deb
Processed: limit rdesktop bug to Jessie version only
Processing commands for cont...@bugs.debian.org: package rdesktop Limiting to bugs with field 'package' containing at least one of 'rdesktop' Limit currently set to 'package':'rdesktop' tags 784634 + jessie Bug #784634 [rdesktop] rdesktop: rdesktop fails to connect, segmentation fault Added tag(s) jessie. found 784634 1.8.2-1 Bug #784634 [rdesktop] rdesktop: rdesktop fails to connect, segmentation fault Marked as found in versions rdesktop/1.8.2-1. fixed 784634 1.8.3-1 Bug #784634 [rdesktop] rdesktop: rdesktop fails to connect, segmentation fault Marked as fixed in versions rdesktop/1.8.3-1. thanks Stopping processing here. Please contact me if you need assistance. -- 784634: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=784634 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#784686: pgtap: Missing pgtap for postgresql-9.3
Package: pgtap Version: 0.90.0-1 Severity: grave Dear Maintainer, pgtap 0.90.0-1 contains files configured for postgresql-9.1, and breaks in postgresql-9.3 and 9.4 create extension pgtap; ERROR: could not open extension control file This is a known problem that has been fixed in the pgtap source as of version 0.94.0 2014-01-07T01:32:36Z:https://github.com/theory/pgtap/blob/master/Changes#L45 Note this version was released more than a year ago. Could you please rev the version. Thank you, Abe
Bug#784690: addgroup: The group `docker' already exists and is not a system group. Exiting.
Package: docker.io Version: 1.6.0+dfsg1-1 Severity: grave Justification: renders package unusable Dear Maintainer, * What led up to the situation? I did install a Virtual System with jessie netinstaller as docker.com suggestes Docker is in jessie. Then I found its only in unstable. I upgraded to stretch and then to sid. apt-get install docker.io failed with addgroup: The group `docker' already exists and is not a system group. Exiting. dpkg: error processing package docker.io (--configure): subprocess installed post-installation script returned error exit status 1 Errors were encountered while processing: docker.io * What exactly did you do (or not do) that was effective (or ineffective)? I added -xv to the postinst script and these are the lines visible: root@dockertest:~# DEBCONF_DEBUG=developer dpkg --configure -a Setting up docker.io (1.6.0+dfsg1-1) ... #!/bin/sh -xv set -e + set -e case $1 in configure) if [ -z $2 ]; then addgroup --system docker fi ;; abort-*) # How'd we get here?? exit 1 ;; *) ;; esac + [ -z ] + addgroup --system docker addgroup: The group `docker' already exists and is not a system group. Exiting. dpkg: error processing package docker.io (--configure): subprocess installed post-installation script returned error exit status 1 Errors were encountered while processing: docker.io root@dockertest:~# docker is an existing group: root@dockertest:~# grep docker /etc/group cdrom:x:24:docker floppy:x:25:docker audio:x:29:docker dip:x:30:docker video:x:44:docker plugdev:x:46:docker netdev:x:108:docker bluetooth:x:114:docker docker:x:1000: root@dockertest:~# 1000 is just out of the stuff defined root@dockertest:~# grep GID /etc/login.defs GID_MIN 1000 GID_MAX 6 #SYS_GID_MIN 100 #SYS_GID_MAX 999 root@dockertest:~# work-around: root@dockertest:~# groupmod -g 900 docker root@dockertest:~# apt-get install -f docker installed. -- System Information: Debian Release: stretch/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: amd64 (x86_64) Kernel: Linux 3.16.0-4-amd64 (SMP w/1 CPU core) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages docker.io depends on: ii adduser 3.113+nmu3 ii init-system-helpers 1.23 ii iptables 1.4.21-2+b1 ii libapparmor1 2.9.0-3 ii libc62.19-18 ii libdevmapper1.02.1 2:1.02.90-2.2 ii libsqlite3-0 3.8.9-2 ii perl 5.20.2-4 Versions of packages docker.io recommends: ii aufs-tools 1:3.2+20130722-1.1 ii ca-certificates 20141019 ii cgroupfs-mount 1.2 ii git 1:2.1.4-2.1 ii xz-utils 5.1.1alpha+20120614-2+b3 Versions of packages docker.io suggests: pn btrfs-tools none pn debootstrap none pn lxc none pn rinsenone -- 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#784648: marked as done (debhelper: dh_bugfiles installs bug scripts into wrong location)
Your message dated Thu, 07 May 2015 18:33:59 + with message-id e1yqqcr-0005hg...@franck.debian.org and subject line Bug#784648: fixed in debhelper 9.20150507 has caused the Debian Bug report #784648, regarding debhelper: dh_bugfiles installs bug scripts into wrong location 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.) -- 784648: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=784648 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: debhelper Version: 9.20150502 Severity: important I rebuilt src:fbcat against the current debhelper. This was the result: $ dpkg -c fbcat_0.3-1debhelper9.201505021_i386.deb | grep '^-.*/bug/' -rw-r--r-- root/root 241 2012-05-13 22:43 ./usr/share/bug/fbcat/bug-script For comparison, the package in the archive has: $ dpkg -c fbcat_0.3-1_i386.deb | grep '^-.*/bug/' -rwxr-xr-x root/root 241 2012-05-13 22:43 ./usr/share/bug/fbcat In the new package, the bug script is installed into wrong location (should be /usr/share/bug/fbcat or /usr/share/bug/fbcat/script), and it has wrong permissions (should be executable). -- System Information: Debian Release: stretch/sid APT prefers unstable APT policy: (990, 'unstable'), (500, 'experimental') Architecture: i386 (x86_64) Foreign Architectures: amd64 Kernel: Linux 3.2.0-4-amd64 (SMP w/2 CPU cores) Locale: LANG=C, LC_CTYPE=pl_PL.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: sysvinit (via /sbin/init) Versions of packages debhelper depends on: ii binutils 2.25-7 ii dpkg 1.17.25 ii dpkg-dev 1.17.25 ii file 1:5.22+15-2 ii libdpkg-perl 1.17.25 ii man-db2.7.0.2-5 ii perl 5.20.2-4 ii po-debconf1.0.18 -- Jakub Wilk ---End Message--- ---BeginMessage--- Source: debhelper Source-Version: 9.20150507 We believe that the bug you reported is fixed in the latest version of debhelper, 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 784...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Niels Thykier ni...@thykier.net (supplier of updated debhelper 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: Thu, 07 May 2015 20:07:49 +0200 Source: debhelper Binary: debhelper Architecture: source all Version: 9.20150507 Distribution: unstable Urgency: medium Maintainer: Debhelper Maintainers debhelper-de...@lists.alioth.debian.org Changed-By: Niels Thykier ni...@thykier.net Description: debhelper - helper programs for debian/rules Closes: 784582 784648 Changes: debhelper (9.20150507) unstable; urgency=medium . [ Niels Thykier ] * dh_bugfiles: Fix regression in installing the reportbug script correctly. Thanks to Jakub Wilk for reporting. (Closes: #784648) . [ Translation updates ] * pt - Thanks to Américo Monteiro. (Closes: #784582) Checksums-Sha1: 33e82668e28d93baeb5055d5f99d4ccb80f036bf 1726 debhelper_9.20150507.dsc f7186e3c79f9a62cdab4c2e9e6ece049e3db23f1 314408 debhelper_9.20150507.tar.xz 956a98bbc69dbff74e98ba763d384291d7f3ff33 823694 debhelper_9.20150507_all.deb Checksums-Sha256: 213bf2d2bab9191bc7ae87eb70efbddc7c28282b6c12d159624da6630fe08efa 1726 debhelper_9.20150507.dsc f3b51b3c1ad87cd936d4c443f1cebf8f194ece4b998dce6544e238ce5fd5dc39 314408 debhelper_9.20150507.tar.xz 00d40fe27854b55e5d63a5dbfbc45b06f24ace116f860e8d233fb8eac3da5847 823694 debhelper_9.20150507_all.deb Files: b1e2e48fe04e7284e1b53fbcceb9bdd4 1726 devel optional debhelper_9.20150507.dsc dc9582314727cc75278c5fa0f751cb25 314408 devel optional debhelper_9.20150507.tar.xz d7829806c4ec07da6905919dfe4addca 823694 devel optional debhelper_9.20150507_all.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1 iQIcBAEBCAAGBQJVS6x7AAoJEAVLu599gGRCrggP/1gjog4m5zjCilG/Zec53Anh UkGIDr7wjeLTSgfTKtl9XsAt5BUedAJSX8JBxGDuZd46ecdeaYRM8TMvl4byDYr2 Eqh6oWtm+Tz+7OI85Dn/Hut2DPTLqvoxe0SEpwr8oI9ULMQcZPgR/NpINth2jrpD dmqznUnXBMLyeHdtEtkUaIqYVj3xKTxB6U0bQ7l1ykrTHvKHnfsUERcF1i47Saaa adWkitD+rz/C7ZW4YJR08y4VJMyKYbuEOjeCNgGuYzuPZMz7ywLIsSwZ0EhlWC+e pWIAVZ+WNDZwAVUx4kiu1nCjX9dbvQrxsdFVwt0KDPlPl91O7HVTGkIYINnHEvL2
Processed: tagging 784634
Processing commands for cont...@bugs.debian.org: # Don't use suite tags when version tracking will do tags 784634 - jessie Bug #784634 [rdesktop] rdesktop: rdesktop fails to connect, segmentation fault Removed tag(s) jessie. thanks Stopping processing here. Please contact me if you need assistance. -- 784634: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=784634 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#765124: caused by the upgrade from ruby-i18n 0.6.9 to 0.6.11
On 21/10/14 at 12:00 +0200, Cédric Boutillier wrote: Control: found -1 ruby-i18n/0.6.11-1 Control: notfound -1 ruby-i18n/0.6.9-2 Hi, It seems that this bug has been caused by the upgrade of ruby-i18n rom 0.6.9 to 0.6.11. Something broke in the determination of whic locales are available. This is likely related to the following commit: https://github.com/svenfuchs/i18n/commit/a65fffd6f0472bc413ba41809dafc6292e29d2ae I bisected it with i18n usptream and can confirm that this is needed the first bad commit. Lucas signature.asc Description: Digital signature
Bug#783861: marked as done (tuskar-common: fails to purge: ucfr: Association belongs to tuskar-common, not cinder-common)
Your message dated Thu, 07 May 2015 20:05:07 + with message-id e1yqs2d-i2...@franck.debian.org and subject line Bug#783861: fixed in tuskar 0.4.17-1 has caused the Debian Bug report #783861, regarding tuskar-common: fails to purge: ucfr: Association belongs to tuskar-common, not cinder-common 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.) -- 783861: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=783861 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: tuskar-common Version: 0.4.2-4 Severity: serious User: debian...@lists.debian.org Usertags: piuparts Hi, during a test with piuparts I noticed your package failed to purge. From the attached log (scroll to the bottom...): Removing tuskar-common (0.4.2-4) ... Purging configuration files for tuskar-common (0.4.2-4) ... ucfr: Association belongs to tuskar-common, not cinder-common ucfr: Aborting dpkg: error processing package tuskar-common (--purge): subprocess installed post-removal script returned error exit status 5 Errors were encountered while processing: tuskar-common This very much looks like a copy-and-paste error, i.e. a wrong package name, in the ucfr call (but I did not look at the maintainer scripts at all). cheers, Andreas tuskar-common_0.4.2-4.log.gz Description: application/gzip ---End Message--- ---BeginMessage--- Source: tuskar Source-Version: 0.4.17-1 We believe that the bug you reported is fixed in the latest version of tuskar, 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 783...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Thomas Goirand z...@debian.org (supplier of updated tuskar 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: Thu, 07 May 2015 15:25:42 +0200 Source: tuskar Binary: python-tuskar tuskar-common tuskar tuskar-api tuskar-manager tuskar-doc Architecture: source all Version: 0.4.17-1 Distribution: unstable Urgency: medium Maintainer: PKG OpenStack openstack-de...@lists.alioth.debian.org Changed-By: Thomas Goirand z...@debian.org Description: python-tuskar - control how and where OpenStack services are deployed - Python mo tuskar - control how and where OpenStack services are deployed - meta pack tuskar-api - control how and where OpenStack services are deployed - API serve tuskar-common - control how and where OpenStack services are deployed - common fi tuskar-doc - control how and where OpenStack services are deployed - doc tuskar-manager - control how and where OpenStack services are deployed - manager s Closes: 783861 Changes: tuskar (0.4.17-1) unstable; urgency=medium . * New upstream release. * Fixed (build-)depends for this release. * Fixed debian/tuskar-common.postrm ucfr purge (Closes: #783861). Checksums-Sha1: 2aefc4a80594f2f4c82ffe4dd702124b6141a6a8 3000 tuskar_0.4.17-1.dsc 9c1a3bf809348b1ed476678568fee7edf861d83c 121012 tuskar_0.4.17.orig.tar.xz b4a21a399b70ceca9f8f3fad00612ac4f3d89ebf 16224 tuskar_0.4.17-1.debian.tar.xz 1e03277b620cc2d62c5036ac09d5296419dc761f 92992 python-tuskar_0.4.17-1_all.deb fe56428086d03fa1da1aa89855c65b76821c91d3 23092 tuskar-common_0.4.17-1_all.deb c60b34493093eb8d5dd66c86f47c87019c5338f2 3662 tuskar_0.4.17-1_all.deb e5578b6ea6f5c09087f9b8c6d5de5969f395a37d 19158 tuskar-api_0.4.17-1_all.deb 5259104d1aad3e6c68b1c68e1b332f219e72bdbe 6384 tuskar-manager_0.4.17-1_all.deb eccb60e09e1e0df3ced5a3f7d532b76746dcb183 38512 tuskar-doc_0.4.17-1_all.deb Checksums-Sha256: a49c91160cfadac06a528587a74b6c2d41839cb266b96782edaa1ecd0bb12dbb 3000 tuskar_0.4.17-1.dsc 53e103d2e7e035a1b2a1c27dc6dbe69f534dd67cddbfd7a9c70288a175b60244 121012 tuskar_0.4.17.orig.tar.xz 6d71cc446f04936e545748edafa6910ff420f6e46932e0e8872771f33c0e68ec 16224 tuskar_0.4.17-1.debian.tar.xz 12e48a4b60eca3810328f1ebf0b62428da95fabed69cedc209f8d51284d1b70d 92992 python-tuskar_0.4.17-1_all.deb 9cb4d69e4f3cbf1dc333fd7546daefb2d916b3a0c9cf4da1b67a5f0455236286 23092 tuskar-common_0.4.17-1_all.deb e8be73884b433ca1bcdd06aa522c175ffecda1bb4fc9d0bda8a3eef60edcbf38 3662 tuskar_0.4.17-1_all.deb
Bug#784690: marked as done (addgroup: The group `docker' already exists and is not a system group. Exiting.)
Your message dated Thu, 7 May 2015 16:07:55 -0400 with message-id 20150507200755.ga13...@sol.pault.ag and subject line Re: Bug#784690: addgroup: The group `docker' already exists and is not a system group. Exiting. has caused the Debian Bug report #784690, regarding addgroup: The group `docker' already exists and is not a system group. Exiting. 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.) -- 784690: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=784690 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: docker.io Version: 1.6.0+dfsg1-1 Severity: grave Justification: renders package unusable Dear Maintainer, * What led up to the situation? I did install a Virtual System with jessie netinstaller as docker.com suggestes Docker is in jessie. Then I found its only in unstable. I upgraded to stretch and then to sid. apt-get install docker.io failed with addgroup: The group `docker' already exists and is not a system group. Exiting. dpkg: error processing package docker.io (--configure): subprocess installed post-installation script returned error exit status 1 Errors were encountered while processing: docker.io * What exactly did you do (or not do) that was effective (or ineffective)? I added -xv to the postinst script and these are the lines visible: root@dockertest:~# DEBCONF_DEBUG=developer dpkg --configure -a Setting up docker.io (1.6.0+dfsg1-1) ... #!/bin/sh -xv set -e + set -e case $1 in configure) if [ -z $2 ]; then addgroup --system docker fi ;; abort-*) # How'd we get here?? exit 1 ;; *) ;; esac + [ -z ] + addgroup --system docker addgroup: The group `docker' already exists and is not a system group. Exiting. dpkg: error processing package docker.io (--configure): subprocess installed post-installation script returned error exit status 1 Errors were encountered while processing: docker.io root@dockertest:~# docker is an existing group: root@dockertest:~# grep docker /etc/group cdrom:x:24:docker floppy:x:25:docker audio:x:29:docker dip:x:30:docker video:x:44:docker plugdev:x:46:docker netdev:x:108:docker bluetooth:x:114:docker docker:x:1000: root@dockertest:~# 1000 is just out of the stuff defined root@dockertest:~# grep GID /etc/login.defs GID_MIN 1000 GID_MAX 6 #SYS_GID_MIN 100 #SYS_GID_MAX 999 root@dockertest:~# work-around: root@dockertest:~# groupmod -g 900 docker root@dockertest:~# apt-get install -f docker installed. -- System Information: Debian Release: stretch/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: amd64 (x86_64) Kernel: Linux 3.16.0-4-amd64 (SMP w/1 CPU core) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages docker.io depends on: ii adduser 3.113+nmu3 ii init-system-helpers 1.23 ii iptables 1.4.21-2+b1 ii libapparmor1 2.9.0-3 ii libc62.19-18 ii libdevmapper1.02.1 2:1.02.90-2.2 ii libsqlite3-0 3.8.9-2 ii perl 5.20.2-4 Versions of packages docker.io recommends: ii aufs-tools 1:3.2+20130722-1.1 ii ca-certificates 20141019 ii cgroupfs-mount 1.2 ii git 1:2.1.4-2.1 ii xz-utils 5.1.1alpha+20120614-2+b3 Versions of packages docker.io suggests: pn btrfs-tools none pn debootstrap none pn lxc none pn rinsenone -- no debconf information ---End Message--- ---BeginMessage--- I'm closing this - it's not a bug. Actually, this just saved your bacon :) If there are users in a group called `docker' and it's not a system created group, they now have root on your host system (yes, *host* system). Perhaps it'd be better to have a debconf prompt. Patches welcome. It's surely not grave. Things you do to your system outside main that break packages in main isn't a bug on us ;) Closing, thanks! Paul On Thu, May 07, 2015 at 09:23:24PM +0200, Christian Hilgers wrote: Package: docker.io Version: 1.6.0+dfsg1-1 Severity: grave Justification: renders package unusable Dear Maintainer, * What led up to the situation? I did install a Virtual System with jessie netinstaller as docker.com suggestes Docker is in jessie. Then I found its only in unstable. I upgraded to stretch and then to sid. apt-get install docker.io failed with
Processed: severity of 784648 is grave
Processing commands for cont...@bugs.debian.org: severity 784648 grave Bug #784648 [debhelper] debhelper: dh_bugfiles installs bug scripts into wrong location Severity set to 'grave' from 'important' thanks Stopping processing here. Please contact me if you need assistance. -- 784648: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=784648 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: limit source to debhelper, tagging 784648
Processing commands for cont...@bugs.debian.org: limit source debhelper Limiting to bugs with field 'source' containing at least one of 'debhelper' Limit currently set to 'source':'debhelper' tags 784648 + pending Bug #784648 [debhelper] debhelper: dh_bugfiles installs bug scripts into wrong location Added tag(s) pending. thanks Stopping processing here. Please contact me if you need assistance. -- 784648: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=784648 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#726500: AMD support request for fglrx legacy driver for jessie
I have requested an updated driver using AMD's contact form: http://support.amd.com/en-us/contact/email-form Will it help if more people request the same? -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#771544: its because of tmpdir collision
On 30/11/14 at 22:19 +0530, Pirate Praveen wrote: control: severity 771544 grave this is not because of sudo, but because /tmp/ruby-uuid is already created by another user. It should add a username prefix when creating state dir. So according to the discussion in https://github.com/assaf/uuid/issues/45, this is a bug in diaspora? Are you OK with reassigning? Lucas -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#773768: marked as done (ghc: fails to install: cannot open shared object file: No such file or directory)
Your message dated Thu, 7 May 2015 23:23:17 +0200 with message-id 20150507212317.ga24...@chase.mapreri.org and subject line Re: [Pkg-haskell-maintainers] Bug#773768: jenkins reproduces this issue has caused the Debian Bug report #773768, regarding ghc: fails to install: cannot open shared object file: No such file or directory 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.) -- 773768: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=773768 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: ghc Version: 7.8.20141119-8 Severity: grave Justification: renders package unusable -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 ghc fails to install (in clean cowbuilder chroot): Setting up ghc (7.8.20141119-8) ... /usr/lib/ghc/bin/ghc: error while loading shared libraries: libHShaskeline-0.7.1.2-ghc7.8.3.20141119.so: cannot open shared object file: No such file or directory /usr/lib/ghc/bin/ghc-pkg: error while loading shared libraries: libHSterminfo-0.4.0.0-ghc7.8.3.20141119.so: cannot open shared object file: No such file or directory dpkg: error processing package ghc (--configure): subprocess installed post-installation script returned error exit status 127 Errors were encountered while processing: ghc E: Sub-process /usr/bin/dpkg returned an error code (1) - Jonas -BEGIN PGP SIGNATURE- Version: GnuPG v1 iQF8BAEBCgBmBQJUmMt1XxSAAC4AKGlzc3Vlci1mcHJAbm90YXRpb25zLm9w ZW5wZ3AuZmlmdGhob3JzZW1hbi5uZXQ3NjQ4ODQwMTIyRTJDNTBFQzUxRDQwRTI0 RUMxQjcyMjM3NEY5QkQ2AAoJEE7BtyI3T5vW4ycIAKUURV8HCHdlo0di7ry2Ld8g emR1SVMJcVGqOA8NjOPtpEw7Oin6ThgjdnwYCcxTyJ2F5DGsV9RQ2HeuyDnkbe5K 3nKElof49RIV9eXJs7XKAOay06KOWep5cy9QrhpY8j+2VOBXIqgAqikLr6CKaYKq h9mq86MWK0/LuBJTnNEt5qxugSYo7NoCpFacb1qp2MAXUtDrdLo04qPxvuJLapUP pQd3/GBzE5So/i5g6m8Vuj+o38LklEJxGpfhnVwBiFHACHbzVU/tZJP4zsRf3/w/ TJSSQB/yhpGQeOhjjOk79O7Gx6YnwnsJvuDzzb3fleaYNxpXRHnqW0GoYv5sYOQ= =BpVX -END PGP SIGNATURE- ---End Message--- ---BeginMessage--- On Sun, May 03, 2015 at 06:14:03PM +0200, Joachim Breitner wrote: thanks. I would expect /proc to be present and if not you are on your own. Even if that is an unjustified expectation, I think the linker should handle it more gracefully. yeah, a nicer error would be fine, but this is not related to ghc. So I’m inclined to close this report. Does anyone disagree? I agree, closing with this email. Thanks for your support, and even more thanks to Helmut (and the others who helped him) to track down the issue. -- regards, Mattia Rizzolo GPG Key: 66AE 2B4A FCCF 3F52 DA18 4D18 4B04 3FCD B944 4540 .''`. more about me: http://mapreri.org : :' : Launchpad user: https://launchpad.net/~mapreri `. `'` Debian QA page: https://qa.debian.org/developer.php?login=mattia `- signature.asc Description: Digital signature ---End Message---
Bug#784294: marked as done (nova-compute-ironic: fails to upgrade from 'jessie' - trying to overwrite /etc/nova/nova-compute.conf)
Your message dated Thu, 07 May 2015 22:26:43 + with message-id e1yquff-0004k7...@franck.debian.org and subject line Bug#784294: fixed in nova 2015.1.0-2 has caused the Debian Bug report #784294, regarding nova-compute-ironic: fails to upgrade from 'jessie' - trying to overwrite /etc/nova/nova-compute.conf 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.) -- 784294: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=784294 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: nova-compute-ironic Version: 2015.1.0-1 Severity: serious User: debian...@lists.debian.org Usertags: piuparts Hi, during a test with piuparts I noticed your package fails to upgrade from 'jessie'. It installed fine in 'jessie', then the upgrade to 'sid' fails because it tries to overwrite other packages files without declaring a Breaks+Replaces relation. See policy 7.6 at https://www.debian.org/doc/debian-policy/ch-relationships.html#s-replaces From the attached log (scroll to the bottom...): Selecting previously unselected package nova-compute-ironic. Preparing to unpack .../nova-compute-ironic_2015.1.0-1_all.deb ... Unpacking nova-compute-ironic (2015.1.0-1) ... dpkg: error processing archive /var/cache/apt/archives/nova-compute-ironic_2015.1.0-1_all.deb (--unpack): trying to overwrite '/etc/nova/nova-compute.conf', which is also in package nova-baremetal 2014.1.3-11 cheers, Andreas nova-baremetal=2014.1.3-11_nova-compute-ironic=2015.1.0-1.log.gz Description: application/gzip ---End Message--- ---BeginMessage--- Source: nova Source-Version: 2015.1.0-2 We believe that the bug you reported is fixed in the latest version of nova, 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 784...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Thomas Goirand z...@debian.org (supplier of updated nova 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: Thu, 07 May 2015 23:38:56 +0200 Source: nova Binary: python-nova nova-common nova-compute nova-compute-lxc nova-compute-uml nova-compute-qemu nova-compute-kvm nova-compute-ironic nova-conductor nova-cert nova-scheduler nova-volume nova-api nova-network nova-console nova-consoleauth nova-doc nova-cells nova-consoleproxy Architecture: source all Version: 2015.1.0-2 Distribution: unstable Urgency: medium Maintainer: PKG OpenStack openstack-de...@lists.alioth.debian.org Changed-By: Thomas Goirand z...@debian.org Description: nova-api - OpenStack Compute - compute API frontend nova-cells - Openstack Compute - cells nova-cert - OpenStack Compute - certificate manager nova-common - OpenStack Compute - common files nova-compute - OpenStack Compute - compute node nova-compute-ironic - OpenStack Compute - compute node (Ironic) nova-compute-kvm - OpenStack Compute - compute node (KVM) nova-compute-lxc - OpenStack Compute - compute node (LXC) nova-compute-qemu - OpenStack Compute - compute node (QEmu) nova-compute-uml - OpenStack Compute - compute node (UserModeLinux) nova-conductor - OpenStack Compute - conductor service nova-console - OpenStack Compute - console nova-consoleauth - OpenStack Compute - Console Authenticator nova-consoleproxy - OpenStack Compute - NoVNC proxy nova-doc - OpenStack Compute - documentation nova-network - OpenStack Compute - network manager nova-scheduler - OpenStack Compute - virtual machine scheduler nova-volume - OpenStack Compute - storage metapackage python-nova - OpenStack Compute - libraries Closes: 784294 Changes: nova (2015.1.0-2) unstable; urgency=medium . * Added conflicts: nova-baremetal for the nova-compute-ironic (Closes: #784294). Checksums-Sha1: bb57f08535adc43bbe01060a8ad9df155cbb1b14 4633 nova_2015.1.0-2.dsc 9678885b46770df943901f1dd9922e041904d750 89284 nova_2015.1.0-2.debian.tar.xz 2895fb63861830027c21b8998121dee1d9c3e6ed 1894588 python-nova_2015.1.0-2_all.deb dbf6a7c4b74fba188890d9e12921ae77be1bd850 76796 nova-common_2015.1.0-2_all.deb 8aece9e3d800ee0b993fb66748cefbabc0e648ea 22252 nova-compute_2015.1.0-2_all.deb 746428d2c1166029568fb8b2d1f3ca0433667a2f 16586
Processed: tagging 784701
Processing commands for cont...@bugs.debian.org: # Doesn't affect Jessie tags 784701 + sid stretch Bug #784701 [wdm] Should Build-Depend on libwraster-dev. Added tag(s) sid and stretch. thanks Stopping processing here. Please contact me if you need assistance. -- 784701: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=784701 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: tagging 784701
Processing commands for cont...@bugs.debian.org: tags 784701 + pending Bug #784701 [wdm] Should Build-Depend on libwraster-dev. Added tag(s) pending. thanks Stopping processing here. Please contact me if you need assistance. -- 784701: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=784701 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#784711: libwraster-dev: Fails to install due to file conflict with libwraster3-dev
Package: libwraster-dev Severity: serious Version: 0.95.6-1 Dear Maintainer, installing libwraster-dev fails, if libwraster3-dev is still installed as they share files with the same file name and path: Unpacking libwraster-dev (0.95.6-1) ... dpkg: error processing archive /var/cache/apt/archives/libwraster-dev_0.95.6-1_amd64.deb (--unpack): trying to overwrite '/usr/lib/libwraster.a', which is also in package libwraster3-dev 0.95.5-2+b2 dpkg-deb: error: subprocess paste was killed by signal (Broken pipe) Errors were encountered while processing: /var/cache/apt/archives/libwraster-dev_0.95.6-1_amd64.deb libwraster-dev needs according Breaks and Replaces header. Additional the Provides: libwraster-dev in libwraster-dev seems useless. It's probably a leftover from libwraster3-dev where it made sense. -- System Information: Debian Release: stretch/sid APT prefers unstable APT policy: (990, 'unstable'), (600, 'testing'), (111, 'buildd-unstable'), (111, 'buildd-experimental'), (110, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 4.0.0-trunk-amd64 (SMP w/4 CPU cores) Locale: LANG=C.UTF-8, LC_CTYPE=C.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#784701: Should Build-Depend on libwraster-dev.
Package: wdm Version: 1.28-17 Severity: serious Tags: patch Beginning with wmaker version 0.95.6-1, libwraster3-dev has been renamed to libwraster-dev. As this is a build dependency of wdm, debian/control should be updated accordingly. diff --git a/debian/control b/debian/control index 2342db0..38ac52f 100644 --- a/debian/control +++ b/debian/control @@ -14,7 +14,7 @@ Build-Depends: debhelper (= 9~), libpng-dev, libselinux1-dev [linux-any], libwings-dev, - libwraster3-dev, + libwraster-dev, libx11-dev, libxau-dev, libxdmcp-dev,
Processed: Re: Bug#784682: systemd unable to boot when snoopy is enabled
Processing control commands: reassign -1 snappy Bug #784682 [systemd] systemd unable to boot when snoopy is enabled Bug reassigned from package 'systemd' to 'snappy'. No longer marked as found in versions systemd/215-17. Ignoring request to alter fixed versions of bug #784682 to the same values previously set severity -1 serious Bug #784682 [snappy] systemd unable to boot when snoopy is enabled Severity set to 'serious' from 'normal' affects -1 systemd Bug #784682 [snappy] systemd unable to boot when snoopy is enabled Added indication that 784682 affects systemd forwarded -1 https://bugzilla.redhat.com/show_bug.cgi?id=948417 Bug #784682 [snappy] systemd unable to boot when snoopy is enabled Set Bug forwarded-to-address to 'https://bugzilla.redhat.com/show_bug.cgi?id=948417'. -- 784682: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=784682 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#784625: evolution: crash on start [Arithmetic exception in e_day_view_convert_position_in_main_canvas at e-day-view.c:8158]
Package: evolution Version: 3.12.9~git20141130.241663-1+b1 Severity: serious Forwarded: https://bugzilla.gnome.org/show_bug.cgi?id=749059 I run evolution for the first time and configured IMAP account. On start evolution crashes within seconds after showing its window: Program received signal SIGFPE, Arithmetic exception. 0x7fffd06415cf in e_day_view_convert_position_in_main_canvas (day_view=0x5819bb10, x=549, y=0, y@entry=690, day_return=0x7fffd7d0, row_return=0x7fffd7cc, event_num_return=event_num_return@entry=0x7fffd7d4) at e-day-view.c:8158 8158e-day-view.c: No such file or directory. (gdb) thread apply all bt Thread 30 (Thread 0x7fff4702a700 (LWP 11468)): #0 syscall () at ../sysdeps/unix/sysv/linux/x86_64/syscall.S:38 #1 0x73892657 in g_cond_wait_until (cond=cond@entry=0x57dafb68, mutex=mutex@entry=0x57dafb60, end_time=end_time@entry=705303038731) at /tmp/buildd/glib2.0-2.42.1/./glib/gthread-posix.c:1443 #2 0x73822a69 in g_async_queue_pop_intern_unlocked (queue=0x57dafb60, wait=wait@entry=1, end_time=705303038731) at /tmp/buildd/glib2.0-2.42.1/./glib/gasyncqueue.c:422 #3 0x738230c8 in g_async_queue_timeout_pop_unlocked (queue=optimized out, timeout=timeout@entry=50) at /tmp/buildd/glib2.0-2.42.1/./glib/gasyncqueue.c:570 #4 0x738752a0 in g_thread_pool_wait_for_new_task (pool=0x57db4380) at /tmp/buildd/glib2.0-2.42.1/./glib/gthreadpool.c:262 #5 g_thread_pool_thread_proxy (data=optimized out) at /tmp/buildd/glib2.0-2.42.1/./glib/gthreadpool.c:296 #6 0x73874935 in g_thread_proxy (data=0x7fff58002000) at /tmp/buildd/glib2.0-2.42.1/./glib/gthread.c:764 #7 0x773400a4 in start_thread (arg=0x7fff4702a700) at pthread_create.c:309 #8 0x7354104d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:111 Thread 29 (Thread 0x7fff4cf6a700 (LWP 11467)): #0 syscall () at ../sysdeps/unix/sysv/linux/x86_64/syscall.S:38 #1 0x73892657 in g_cond_wait_until (cond=cond@entry=0x57dafb68, mutex=mutex@entry=0x57dafb60, end_time=end_time@entry=705303038427) at /tmp/buildd/glib2.0-2.42.1/./glib/gthread-posix.c:1443 #2 0x73822a69 in g_async_queue_pop_intern_unlocked (queue=0x57dafb60, wait=wait@entry=1, end_time=705303038427) at /tmp/buildd/glib2.0-2.42.1/./glib/gasyncqueue.c:422 #3 0x738230c8 in g_async_queue_timeout_pop_unlocked (queue=optimized out, timeout=timeout@entry=50) at /tmp/buildd/glib2.0-2.42.1/./glib/gasyncqueue.c:570 #4 0x738752a0 in g_thread_pool_wait_for_new_task (pool=0x57db4380) at /tmp/buildd/glib2.0-2.42.1/./glib/gthreadpool.c:262 #5 g_thread_pool_thread_proxy (data=optimized out) at /tmp/buildd/glib2.0-2.42.1/./glib/gthreadpool.c:296 #6 0x73874935 in g_thread_proxy (data=0x7fff644a5230) at /tmp/buildd/glib2.0-2.42.1/./glib/gthread.c:764 #7 0x773400a4 in start_thread
Processed: Re: Bug#784548: apt-get update race condition in candidate dependency resolution
Processing control commands: severity -1 normal Bug #784548 [apt] apt-get update race condition in candidate dependency resolution Severity set to 'normal' from 'grave' merge -1 717679 Bug #784548 [apt] apt-get update race condition in candidate dependency resolution Bug #784548 [apt] apt-get update race condition in candidate dependency resolution Marked as found in versions apt/0.9.9.2. Bug #717679 [apt] apt-cache search results broken while apt-get update running Marked as found in versions apt/0.9.7.9+deb7u7. Merged 717679 784548 -- 717679: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=717679 784548: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=784548 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#784548: apt-get update race condition in candidate dependency resolution
Control: severity -1 normal Control: merge -1 717679 On Wed, May 06, 2015 at 04:39:05PM +0200, Stefan Schlesinger wrote: Justification: could cause unwanted versions to be installed without notice Severity: grave No*. At least if you are careful you have a few chances of noticing it. The -V option e.g. tells you the versions. The download progress tells you were stuff comes from. Running apt-get update on a system at the same time with other apt commands, causes apt to resolve package dependencies and policies inconsistently. Behavior causes race conditions during package cache update, resulting in altered candidate versions and you will end up with unwanted versions being installed (eg. when running 'apt-get upgrade -y’ or working with unattended-upgrades). Current stable version in Jessie - 1.0.9.8 is also affected. Every version ever in existence in the last 17 years is effected. That it survived 17 years is reason enough to not give it RC severity. Also note that you need root-rights to run 'apt-get update' (or equivalent) commands, much like you need root-rights to run 'rm -rf /'. rm got over the years safeguards to prevent this, but this will never be perfect and we are much in the same position. In the end root is the only account who can do everything, but it should be asked if that means that it should do everything. Maybe running multiple apt commands in parallel is just in general not a good idea… and btw, neither it is for dpkg or any other package management tool. Many things are heavily interlocked here working in concert to make package installation possible. Sometimes I think 'we' higherlevel parts like apt just made it too easy. On every other plattform which can be updated nobody would ever ask for running stuff in parallel, simply because those happen in total lockdown… IMO, this should either be an atomic file/directory move, once package files where downloaded successfully, or apt-get update should make use of locking as well. This isn't really about the Packages files, but about the Release files and only on a second step about all the other files apt downloads. What sounds like a trivial implementation happily explodes into a code nightmare with only slightly less edgecases than decimal places of pi. We are slowly getting better, but there is only so much you can do with the resources we have… We saw this issue affecting multiple apt commands and actions: Everyone using libapt is effected if you will, so even stuff like the typical software-center. And not all these are started and/or always working as root, so just 'locking' is not an option if you don't happen to forbid every use of libapt as non-root in the process and only allow libapt to be loaded by only one root application at the time. That would immensly cripple the useability for next to no gain… Best regards David Kalnischkies signature.asc Description: Digital signature
Bug#784645: python3-mockldap has incorrect dependency on python3-ldap3, should have on python3-ldap
Package: python3-mockldap Version: 0.2.2-3 Severity: grave Justification: renders package unusable Dear Maintainer, Even accoriding to the main description of the mockldap project on https://pypi.python.org/pypi/mockldap the inention is to provide mock replacements for the stuff normally provided by python-ldap. The python-ldap in Debian is packaged from upstream project https://pypi.python.org/pypi/python-ldap/2.4.19. The problem with that is it still seem to be compatible only with Python 2. The python3-ldap3 is Debian package based on upstream project https://pypi.python.org/pypi/ldap3/0.9.8.2 which has totally incompatible API with the above and it's based on different principles. This bug is against the incorrect dependency of python3-mockldap on python3-ldpa3, while it should depend on non-existing python3-ldap or doesn't exist at all. Such dependency confuses potential users of these tools as causes installation of incompatible Python 3 modules on the system. The only possible option to solve this problem is (quick solution) remove the package python3-mockldap as not very useful while there is no respective python3-ldap or spent some effort on porting upstream python-ldap to Python 3. The latter is not easy task as the Python 3 API to external libraries (openldap in this case) is different that in Python 2. In my case an attempt to use mockldap as part of the unit test executed in Python 3 end up in error of missing piece: ImportError: No module named 'ldap.cidict' -- System Information: Debian Release: 8.0 APT prefers stable APT policy: (990, 'stable'), (500, 'oldstable-updates'), (500, 'oldoldstable'), (500, 'stable'), (500, 'oldstable'), (50, 'unstable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.16.0-4-amd64 (SMP w/12 CPU cores) Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages python3-mockldap depends on: ii python3-funcparserlib 0.3.6-4 ii python3-ldap3 0.9.4.2-1 pn python3:anynone python3-mockldap recommends no packages. Versions of packages python3-mockldap suggests: pn python-mockldap-doc none -- 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#783822: libsane-dev: depends on libgphoto2-2-dev which no longer exists
Hi Jörg, could you please just upload the changes to unstable? Packages depending on libsane-dev etc can't be build at the moment :( I think this would also help the libgphoto2 transition[1] [1] https://release.debian.org/transitions/html/auto-libgphoto2.html Best, Philip signature.asc Description: OpenPGP digital signature
Bug#784634: rdesktop: rdesktop fails to connect, segmentation fault
Package: rdesktop Version: 1.8.2-3 Severity: grave Dear Maintainer, I have upgraded from wheezy to jessie recently including rdesktop package. After the upgrade I can't connect to Windows 7 virtual machine. All I get is the Segmentation fault message. I checked out the latest version from upstream svn (t1847, 1.8.3 + 8 commits), built it with the same options as the Debian package and it does not crash. There is still some issue because rdeskto tries to log in and I get Invalid user name message but it is still better than a crash. I bisected the history between r1806 and r1847. r1824 fixes my problem. --8---cut here---start-8--- r1824 | hean01 | 2014-08-27 14:15:21 +0200 (śro) | 4 linie Fix sigsegv while using credssp and kerberos without specifying domainname as argument. --8---cut here---end---8--- -- System Information: Debian Release: 8.0 APT prefers stable-updates APT policy: (990, 'stable-updates'), (900, 'stable') Architecture: amd64 (x86_64) Foreign Architectures: armel Kernel: Linux 3.16.0-4-amd64 (SMP w/8 CPU cores) Locale: LANG=pl_PL.UTF-8, LC_CTYPE=pl_PL.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages rdesktop depends on: ii libasound21.0.28-1 ii libc6 2.19-18 ii libgssglue1 0.4-2 ii libpcsclite1 1.8.13-1 ii libssl1.0.0 1.0.1k-3 ii libx11-6 2:1.6.2-3 ii libxrandr22:1.4.2-1+b1 rdesktop recommends no packages. Versions of packages rdesktop suggests: pn pcscd none -- no debconf information -- Łukasz Stelmach Samsung RD Institute Poland Samsung Electronics signature.asc Description: PGP signature
Processed: your mail
Processing commands for cont...@bugs.debian.org: found 784245 7.6.3-21 Bug #784245 [src:ghc] ghc: build against llvm-toolchain = 3.5 Marked as found in versions ghc/7.6.3-21. thanks Stopping processing here. Please contact me if you need assistance. -- 784245: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=784245 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#784647: libav-tools: avconv fails with Illegal Instruction
Control: reassign -1 src:libav 6:11.3-1 Control: found 783082 6:11.3-1 Control: severity 783082 grave Control: forcemerge 783082 -1 Hi Vittorio On 2015-05-07 14:51:01, Vittorio Vallero wrote: Package: libav-tools Version: 6:11.3-1 Severity: grave Justification: renders package unusable Dear Maintainer, *** Reporter, please consider answering these questions, where appropriate *** * What led up to the situation? Installing and trying to use avconv lead to the error * What exactly did you do (or not do) that was effective (or ineffective)? Tried to use the other binaries of the package like avplay * What was the outcome of this action? Running any of them returns an Illegal Instruction * What outcome did you expect instead? Normal functioning *** End of the template - remove these template lines *** Thank you for the bug report. This issue has already been reported as #783082. Please check for duplicate reports the next time. Cheers -- Sebastian Ramacher signature.asc Description: Digital signature
Processed: Re: Bug#784647: libav-tools: avconv fails with Illegal Instruction
Processing control commands:
reassign -1 src:libav 6:11.3-1
Bug #784647 [libav-tools] libav-tools: avconv fails with Illegal Instruction
Bug reassigned from package 'libav-tools' to 'src:libav'.
No longer marked as found in versions libav/6:11.3-1.
Ignoring request to alter fixed versions of bug #784647 to the same values
previously set
Bug #784647 [src:libav] libav-tools: avconv fails with Illegal Instruction
Marked as found in versions libav/6:11.3-1.
found 783082 6:11.3-1
Bug #783082 {Done: Sebastian Ramacher sramac...@debian.org} [src:libav] video
players using libav crash with 'illegal instruction' on i586
Marked as found in versions libav/6:11.3-1.
severity 783082 grave
Bug #783082 {Done: Sebastian Ramacher sramac...@debian.org} [src:libav] video
players using libav crash with 'illegal instruction' on i586
Severity set to 'grave' from 'important'
forcemerge 783082 -1
Bug #783082 {Done: Sebastian Ramacher sramac...@debian.org} [src:libav] video
players using libav crash with 'illegal instruction' on i586
Bug #784647 [src:libav] libav-tools: avconv fails with Illegal Instruction
Set Bug forwarded-to-address to
'https://bugzilla.libav.org/show_bug.cgi?id=850'.
Marked Bug as done
Marked as fixed in versions libav/6:11.3-3.
Merged 783082 784647
--
783082: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=783082
784647: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=784647
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#784720: systemd: issues SIGKILL too early (risk of data loss)
Package: systemd Version: 215-17 Severity: grave Tags: upstream fixed-in-experimental Justification: causes non-serious data loss As reported in other distros: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1448259 https://bugzilla.redhat.com/show_bug.cgi?id=1183194 https://bugzilla.redhat.com/show_bug.cgi?id=1141137 This bug has been fixed in experimental[1], but this fix needs to be cherry-picked into a Debian stable update, preferably soon enough that it can still make it to the first jessie point release (Debian 8.1). For the record, I've been personally a victim of a non-serious, but still rather annoying data loss episode most likely caused by this issue, as it matches exactly what is described in the redhat bug reports. [1] http://anonscm.debian.org/cgit/pkg-systemd/systemd.git/commit/?h=experimentalid=6068e872da -- Package-specific info: -- System Information: Debian Release: 8.0 APT prefers stable-updates APT policy: (990, 'stable-updates'), (990, 'stable'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.18.12 (SMP w/8 CPU cores) Locale: LANG=pt_BR.UTF-8, LC_CTYPE=pt_BR.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages systemd depends on: ii acl 2.2.52-2 ii adduser 3.113+nmu3 ii initscripts 2.88dsf-59 ii libacl1 2.2.52-2 ii libaudit1 1:2.4-1+b1 ii libblkid1 2.25.2-6 ii libc6 2.19-18 ii libcap2 1:2.24-8 ii libcap2-bin 1:2.24-8 ii libcryptsetup4 2:1.6.6-5 ii libgcrypt20 1.6.3-2 ii libkmod218-3 ii liblzma55.1.1alpha+20120614-2+b3 ii libpam0g1.1.8-3.1 ii libselinux1 2.3-2 ii libsystemd0 215-17 ii mount 2.25.2-6 ii sysv-rc 2.88dsf-59 ii udev215-17 ii util-linux 2.25.2-6 Versions of packages systemd recommends: ii dbus1.8.16-1 ii libpam-systemd 215-17 Versions of packages systemd suggests: ii systemd-ui 3-2 -- no debconf information -- One disk to rule them all, One disk to find them. One disk to bring them all and in the darkness grind them. In the Land of Redmond where the shadows lie. -- The Silicon Valley Tarot Henrique Holschuh -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed: reassign 770194 to ruby-i18n
Processing commands for cont...@bugs.debian.org:
reassign 770194 ruby-i18n
Bug #770194 {Done: Lucas Nussbaum lu...@debian.org} [src:ruby-stringex]
ruby-stringex: FTBFS: Test failures
Bug reassigned from package 'src:ruby-stringex' to 'ruby-i18n'.
No longer marked as found in versions ruby-stringex/2.5.2-2.
No longer marked as fixed in versions ruby-i18n/0.6.11-2.
thanks
Stopping processing here.
Please contact me if you need assistance.
--
770194: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=770194
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#784682: systemd unable to boot when snoopy is enabled
Control: reassign -1 snoopy Michael Biebl [2015-05-07 23:36 +0200]: I just came across an issue with journald being unable to start up when snoopy is enabled that prevents a Jessie/systemd installation to boot up which i reported to upstream at https://bugs.freedesktop.org/show_bug.cgi?id=90364 . This is to let you know about the issue. Maybe we need to stick a warning label somewhere. ;-) I'm going to re-assign this to snappy. This looks to me like something which needs to be addressed in the snappy package. I'm 99% sure this was meant to be reassigned to snoopy, not snappy :-) Martin -- Martin Pitt| http://www.piware.de Ubuntu Developer (www.ubuntu.com) | Debian Developer (www.debian.org) signature.asc Description: Digital signature
Processed: Re: Bug#784682: systemd unable to boot when snoopy is enabled
Processing control commands: reassign -1 snoopy Bug #784682 [snoopy] systemd unable to boot when snoopy is enabled Ignoring request to reassign bug #784682 to the same package -- 784682: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=784682 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#784720: systemd: issues SIGKILL too early (risk of data loss)
Processing control commands: fixed -1 219-8 Bug #784720 [systemd] systemd: issues SIGKILL too early (risk of data loss) Marked as fixed in versions systemd/219-8. tag -1 pending Bug #784720 [systemd] systemd: issues SIGKILL too early (risk of data loss) Added tag(s) pending. -- 784720: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=784720 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#784720: systemd: issues SIGKILL too early (risk of data loss)
Control: fixed -1 219-8 Control: tag -1 pending Hello Henrique, Henrique de Moraes Holschuh [2015-05-07 23:01 -0300]: As reported in other distros: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1448259 https://bugzilla.redhat.com/show_bug.cgi?id=1183194 https://bugzilla.redhat.com/show_bug.cgi?id=1141137 This bug has been fixed in experimental[1], but this fix needs to be cherry-picked into a Debian stable update, preferably soon enough that it can still make it to the first jessie point release (Debian 8.1). I agree, this is highly annoying up to dangerous. I cherry-picked the patch to master: http://anonscm.debian.org/cgit/pkg-systemd/systemd.git/commit/?id=00aaecd711 and also added the bug ref to experimental. Thanks, Martin -- Martin Pitt| http://www.piware.de Ubuntu Developer (www.ubuntu.com) | Debian Developer (www.debian.org) signature.asc Description: Digital signature
Bug#784726: docker.io: CVE-2015-3627 CVE-2015-3629 CVE-2015-3630 CVE-2015-3631
Source: docker.io Version: 1.6.0+dfsg1-1 Severity: grave Tags: security upstream fixed-upstream Hi, the following vulnerabilities were published for docker.io. CVE-2015-3627[0]: Insecure opening of file-descriptor 1 leading to privilege escalation CVE-2015-3629[1]: Symlink traversal on container respawn allows local privilege escalation CVE-2015-3630[2]: Read/write proc paths allow host modification information disclosure CVE-2015-3631[3]: Volume mounts allow LSM profile escalation If you fix the vulnerabilities please also make sure to include the CVE (Common Vulnerabilities Exposures) ids in your changelog entry. For further information see: [0] https://security-tracker.debian.org/tracker/CVE-2015-3627 [1] https://security-tracker.debian.org/tracker/CVE-2015-3629 [2] https://security-tracker.debian.org/tracker/CVE-2015-3630 [3] https://security-tracker.debian.org/tracker/CVE-2015-3631 [4] http://www.openwall.com/lists/oss-security/2015/05/07/10 Regards, Salvatore -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#784720: systemd: issues SIGKILL too early (risk of data loss)
On Fri, May 8, 2015, at 01:01, Martin Pitt wrote: Henrique de Moraes Holschuh [2015-05-07 23:01 -0300]: As reported in other distros: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1448259 https://bugzilla.redhat.com/show_bug.cgi?id=1183194 https://bugzilla.redhat.com/show_bug.cgi?id=1141137 This bug has been fixed in experimental[1], but this fix needs to be cherry-picked into a Debian stable update, preferably soon enough that it can still make it to the first jessie point release (Debian 8.1). I agree, this is highly annoying up to dangerous. I cherry-picked the patch to master: Thank you! -- One disk to rule them all, One disk to find them. One disk to bring them all and in the darkness grind them. In the Land of Redmond where the shadows lie. -- The Silicon Valley Tarot Henrique de Moraes Holschuh h...@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: forcibly merging 765124 770194
Processing commands for cont...@bugs.debian.org:
forcemerge 765124 770194
Bug #765124 {Done: Lucas Nussbaum lu...@debian.org} [ruby-i18n]
ruby-stringex: FTBFS: ERROR: Test ruby2.1 failed: Running tests for ruby2.1
using debian/ruby-tests.rake ...
Bug #770194 {Done: Lucas Nussbaum lu...@debian.org} [ruby-i18n]
ruby-stringex: FTBFS: Test failures
Added indication that 770194 affects ruby-stringex
Marked as fixed in versions ruby-i18n/0.6.11-2.
Marked as found in versions ruby-i18n/0.6.11-1.
Bug #765124 {Done: Lucas Nussbaum lu...@debian.org} [ruby-i18n]
ruby-stringex: FTBFS: ERROR: Test ruby2.1 failed: Running tests for ruby2.1
using debian/ruby-tests.rake ...
Added tag(s) confirmed and moreinfo.
Merged 765124 770194
thanks
Stopping processing here.
Please contact me if you need assistance.
--
765124: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=765124
770194: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=770194
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#784655: can't rebuild casablanca with newer libstdc++6 (sid)
Package: gcc-5
Version: 5.1.1-4
Severity: Serious
Justification: Package rebuild trigger a test failure.
As said, casablanca doesn't pass the testsuite anymore with libstdc++6 library.
I triggered a successful build from Stretch, and upgraded packages until I
upgraded libstdc++6
Preparing to unpack .../libstdc++6_5.1.1-4_amd64.deb ...
Unpacking libstdc++6:amd64 (5.1.1-4) over (4.9.2-10) ...
Now I have the testsuite giving some failures:
/casablanca/Release/tests/functional/http/client/connections_and_errors.cpp:94:
error: Failure in server_doesnt_exist:
CHECK_EQUAL(static_castint(std::errc::host_unreachable), _condFound.value())
where static_castint(std::errc::host_unreachable)=113 and _condFound.value()=0
FAILED
Test case connections_and_errors:server_doesnt_exist FAILED
[...]
and
/casablanca/Release/tests/functional/streams/fstreambuf_tests.cpp:148: error:
Failure in OpenForReadDoesntCreateFile1:
CHECK_EQUAL(static_castint(std::errc::no_such_file_or_directory),
_condFound.value()) where
static_castint(std::errc::no_such_file_or_directory)=2 and
_condFound.value()=0
FAILED
Test case file_buffer_tests:OpenForReadDoesntCreateFile1 FAILED
(code following from
http://anonscm.debian.org/cgit/collab-maint/casablanca.git/tree/Release/tests/functional/streams/fstreambuf_tests.cpp)
TEST(OpenForReadDoesntCreateFile1)
{
utility::string_t fname = U(OpenForReadDoesntCreateFile1.txt);
VERIFY_THROWS_SYSTEM_ERROR(OPEN_Rchar(fname).get(),
std::errc::no_such_file_or_directory);
std::ifstream is;
VERIFY_IS_NULL(is.rdbuf()-open(fname.c_str(), std::ios::in));
}
any idea for the regression?
thanks,
Gianfranco
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#784656: winbind: PANIC when trying to authenticate user
Package: winbind Version: 2:4.1.17+dfsg-2 Severity: grave We have a Debian jessie machine that is not able to authenticate a user against a Samba 4 domain controller with winbind. When the domain user tries to logon with the correct password, winbind crashes. Running winbind in debug level 10 gives us: # log.wb-CORP # [2015/05/07 10:59:03.245096, 10, pid=30054, effective(2001, 0), real(2001, 0)] ../source3/librpc/crypto/gse_krb5.c:279(fill_mem_keytab_from_secrets) ../source3/librpc/crypto/gse_krb5.c:279: no prev machine password [2015/05/07 10:59:03.245231, 10, pid=30054, effective(2001, 0), real(2001, 0)] ../source3/lib/util.c:1868(name_to_fqdn) name_to_fqdn: lookup for ABBY - abby.corp.lsexperts.de. [2015/05/07 10:59:03.245317, 1, pid=30054, effective(2001, 0), real(2001, 0)] ../source3/librpc/crypto/gse_krb5.c:416(fill_mem_keytab_from_system_keytab) ../source3/librpc/crypto/gse_krb5.c:416: krb5_kt_start_seq_get failed (Permission denied) [2015/05/07 10:59:03.245381, 0, pid=30054, effective(2001, 0), real(2001, 0)] ../lib/util/fault.c:72(fault_report) === [2015/05/07 10:59:03.246279, 0, pid=30054, effective(2001, 0), real(2001, 0)] ../lib/util/fault.c:73(fault_report) INTERNAL ERROR: Signal 11 in pid 30054 (4.1.17-Debian) Please read the Trouble-Shooting section of the Samba HOWTO [2015/05/07 10:59:03.247275, 0, pid=30054, effective(2001, 0), real(2001, 0)] ../lib/util/fault.c:75(fault_report) === [2015/05/07 10:59:03.247942, 0, pid=30054, effective(2001, 0), real(2001, 0)] ../source3/lib/util.c:785(smb_panic_s3) PANIC (pid 30054): internal error [2015/05/07 10:59:03.249204, 0, pid=30054, effective(2001, 0), real(2001, 0)] ../source3/lib/util.c:896(log_stack_trace) BACKTRACE: 27 stack frames: #0 /usr/lib/x86_64-linux-gnu/libsmbconf.so.0(log_stack_trace+0x1a) [0x7fa0f68972ca] #1 /usr/lib/x86_64-linux-gnu/libsmbconf.so.0(smb_panic_s3+0x20) [0x7fa0f68973b0] #2 /usr/lib/x86_64-linux-gnu/libsamba-util.so.0(smb_panic+0x2f) [0x7fa0fabc1caf] #3 /usr/lib/x86_64-linux-gnu/libsamba-util.so.0(+0x1cecf) [0x7fa0fabc1ecf] #4 /lib/x86_64-linux-gnu/libpthread.so.0(+0xf8d0) [0x7fa0faff18d0] #5 /usr/lib/x86_64-linux-gnu/libkrb5.so.26(krb5_storage_free+0x1) [0x7fa0f53d12a1] #6 /usr/lib/x86_64-linux-gnu/libkrb5.so.26(+0x47665) [0x7fa0f53b6665] #7 /usr/lib/x86_64-linux-gnu/samba/libgse.so.0(+0x8e06) [0x7fa0f742de06] #8 /usr/lib/x86_64-linux-gnu/samba/libgse.so.0(gse_krb5_get_server_keytab+0xeb) [0x7fa0f742e32b] #9 /usr/lib/x86_64-linux-gnu/samba/libgse.so.0(+0xb03a) [0x7fa0f743003a] #10 /usr/lib/x86_64-linux-gnu/libgensec.so.0(gensec_start_mech+0x72) [0x7fa0f78bfab2] #11 /usr/lib/x86_64-linux-gnu/libgensec.so.0(gensec_start_mech_by_oid+0x26) [0x7fa0f78bfd96] #12 /usr/sbin/winbindd(kerberos_return_pac+0x42c) [0x7fa0fb447cac] #13 /usr/sbin/winbindd(winbindd_dual_pam_auth+0x1150) [0x7fa0fb46d5a0] #14 /usr/sbin/winbindd(+0x5fd5c) [0x7fa0fb481d5c] #15 /usr/lib/x86_64-linux-gnu/libtevent.so.0(+0x92cb) [0x7fa0f48f22cb] #16 /usr/lib/x86_64-linux-gnu/libtevent.so.0(+0x7797) [0x7fa0f48f0797] #17 /usr/lib/x86_64-linux-gnu/libtevent.so.0(_tevent_loop_once+0x8d) [0x7fa0f48ecf9d] #18 /usr/sbin/winbindd(+0x620d8) [0x7fa0fb4840d8] #19 /usr/sbin/winbindd(+0x627d5) [0x7fa0fb4847d5] #20 /usr/lib/x86_64-linux-gnu/libtevent.so.0(tevent_common_loop_immediate+0xd4) [0x7fa0f48ed7c4] #21 /usr/lib/x86_64-linux-gnu/libtevent.so.0(+0x908e) [0x7fa0f48f208e] #22 /usr/lib/x86_64-linux-gnu/libtevent.so.0(+0x7797) [0x7fa0f48f0797] #23 /usr/lib/x86_64-linux-gnu/libtevent.so.0(_tevent_loop_once+0x8d) [0x7fa0f48ecf9d] #24 /usr/sbin/winbindd(main+0xad4) [0x7fa0fb447024] #25 /lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0xf5) [0x7fa0f4561b45] #26 /usr/sbin/winbindd(+0x25699) [0x7fa0fb447699] [2015/05/07 10:59:03.254728, 0, pid=30054, effective(2001, 0), real(2001, 0)] ../source3/lib/dumpcore.c:312(dump_core) unable to change to /var/log/samba/cores/winbindd refusing to dump core # log.wb-CORP # # log.winbindd # [2015/05/07 10:59:03.121241, 1, pid=30049, effective(0, 0), real(0, 0)] ../librpc/ndr/ndr.c:333(ndr_print_function_debug) wbint_LookupName: struct wbint_LookupName out: struct wbint_LookupName type : * type : SID_NAME_DOM_GRP (2) sid : * sid : S-1-5-21-1063204605-3499843724-851943503-1135 result : NT_STATUS_OK [2015/05/07 10:59:03.121463, 10, pid=30049, effective(0, 0), real(0, 0), class=winbind] ../source3/winbindd/winbindd.c:755(wb_request_done) wb_request_done[29718:LOOKUPNAME]: NT_STATUS_OK [2015/05/07 10:59:03.121570, 10, pid=30049, effective(0, 0), real(0, 0), class=winbind]
Processed: reassign 784682 to snoopy
Processing commands for cont...@bugs.debian.org: reassign 784682 snoopy Bug #784682 [snoppy] systemd unable to boot when snoopy is enabled Warning: Unknown package 'snoppy' Bug reassigned from package 'snoppy' to 'snoopy'. Ignoring request to alter found versions of bug #784682 to the same values previously set Ignoring request to alter fixed versions of bug #784682 to the same values previously set thanks Stopping processing here. Please contact me if you need assistance. -- 784682: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=784682 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#784709: os-prober prevent the upgrade to jessie
Package: os-prober Version: 1.65 Severity: critical Tags: newcomer Justification: breaks the whole system Dear Maintainer, During the upgrade (apt-get dist-upgrade) of a computer from debian7 (Wheezy) to Debian8 (Jessie) the system still runs the kernel 3.2 from Wheezy; but the os-prober version used by update-grub is already the one from Jessie... and hang. According to: https://lists.debian.org/debian-boot/2013/05/msg00077.html (and related bugs at maegia), the new os-prober (from Jessie) is unable to scan a hard-drive containing Extended partitions (like sdb4 hereafter) and locks forever (at least 90mn), locking the debian system in the middle of a dist- upgrade. Disque /dev/sdb : 1,8 TiB, 2000398934016 octets, 3907029168 secteurs Unités : secteur de 1 × 512 = 512 octets Taille de secteur (logique / physique) : 512 octets / 512 octets taille d'E/S (minimale / optimale) : 512 octets / 512 octets Type d'étiquette de disque : dos Identifiant de disque : 0x9a2578f7 Device Boot StartEndSectors Size Id Type /dev/sdb1 63 33575849 33575787 16G 82 Linux swap / Solaris /dev/sdb2 33575850 243304424 209728575 100G 83 Linux /dev/sdb3243304425 453032999 209728575 100G 83 Linux /dev/sdb4453033000 3907024064 3453991065 1,6T 5 Extended /dev/sdb5453033063 557905319 104872257 50G 83 Linux /dev/sdb6557905383 662777639 104872257 50G 83 Linux /dev/sdb766203 767649959 104872257 50G 83 Linux /dev/sdb8767650023 872522279 104872257 50G 83 Linux /dev/sdb9872522343 1082250854 209728512 100G 83 Linux /dev/sdb10 1082250918 3907024064 2824773147 1,3T 83 Linux The system was fully occupied by a mount process trying to mount /dev/sdb4. This process was uninteruptable (kill -9 being ineffective) and forced to reboot exactly at the stage grub was updating. The only solution found was to boot an external device with a rescue system and a recent kernel (3.16) to finish the dist-upgrade. One solution may have been to upgrade first the kernel via wheezy-backports packages before upgrading to Jessie. Best regards, Jerome Kieffer -- System Information: Debian Release: 8.0 APT prefers stable APT policy: (800, 'stable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.16.0-4-amd64 (SMP w/8 CPU cores) Locale: LANG=fr_FR.UTF8, LC_CTYPE=fr_FR.UTF8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash Init: systemd (via /run/systemd/system) Versions of packages os-prober depends on: ii libc6 2.19-18 os-prober recommends no packages. os-prober 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
Processed: Re: Bug#784682: systemd unable to boot when snoopy is enabled
Processing control commands: reassign -1 snoppy Bug #784682 [snappy] systemd unable to boot when snoopy is enabled Bug reassigned from package 'snappy' to 'snoppy'. Warning: Unknown package 'snoppy' Warning: Unknown package 'snoppy' Ignoring request to alter found versions of bug #784682 to the same values previously set Warning: Unknown package 'snoppy' Warning: Unknown package 'snoppy' Ignoring request to alter fixed versions of bug #784682 to the same values previously set Warning: Unknown package 'snoppy' -- 784682: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=784682 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#784682: systemd unable to boot when snoopy is enabled
Control: reassign -1 snoppy Am 07.05.2015 um 23:36 schrieb Michael Biebl: Control: reassign -1 snappy Control: severity -1 serious Control: affects -1 systemd Control: forwarded -1 https://bugzilla.redhat.com/show_bug.cgi?id=948417 Am 07.05.2015 um 19:38 schrieb Stefan Schmidt: Package: systemd Version: 215-17 I just came across an issue with journald being unable to start up when snoopy is enabled that prevents a Jessie/systemd installation to boot up which i reported to upstream at https://bugs.freedesktop.org/show_bug.cgi?id=90364 . This is to let you know about the issue. Maybe we need to stick a warning label somewhere. ;-) I'm going to re-assign this to snappy. This looks to me like something which needs to be addressed in the snappy package. Grr, snoopy, of course... -- Why is it that all of the instruments seeking intelligent life in the universe are pointed away from Earth? signature.asc Description: OpenPGP digital signature
Bug#770194: marked as done (ruby-stringex: FTBFS: Test failures)
Your message dated Thu, 07 May 2015 22:29:01 + with message-id e1yquht-0004mx...@franck.debian.org and subject line Bug#770194: fixed in ruby-i18n 0.6.11-2 has caused the Debian Bug report #770194, regarding ruby-stringex: FTBFS: Test failures 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.) -- 770194: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=770194 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Source: ruby-stringex Version: 2.5.2-2 Severity: serious From my pbuilder build log (on amd64): ... === Error: test_vulgar_fractions_conversion: ⅞(GermanYAMLLocalizationTest) I18n::InvalidLocale: :de is not a valid locale /usr/lib/ruby/vendor_ruby/i18n.rb:285:in `enforce_available_locales!' /usr/lib/ruby/vendor_ruby/i18n.rb:150:in `translate' /tmp/buildd/ruby-stringex-2.5.2/lib/stringex/localization/backend/i18n.rb:52:in `i18n_translations_for' /tmp/buildd/ruby-stringex-2.5.2/lib/stringex/localization/backend/i18n.rb:35:in `block in translations' /tmp/buildd/ruby-stringex-2.5.2/lib/stringex/localization/backend/i18n.rb:39:in `yield' /tmp/buildd/ruby-stringex-2.5.2/lib/stringex/localization/backend/i18n.rb:39:in `initial_translation' /tmp/buildd/ruby-stringex-2.5.2/lib/stringex/localization.rb:94:in `initial_translation' /tmp/buildd/ruby-stringex-2.5.2/lib/stringex/localization.rb:43:in `translate' /tmp/buildd/ruby-stringex-2.5.2/lib/stringex/localization/converter.rb:121:in `translate' /tmp/buildd/ruby-stringex-2.5.2/lib/stringex/localization/converter.rb:106:in `block in vulgar_fractions' /tmp/buildd/ruby-stringex-2.5.2/lib/stringex/localization/converter.rb:105:in `each' /tmp/buildd/ruby-stringex-2.5.2/lib/stringex/localization/converter.rb:105:in `vulgar_fractions' /tmp/buildd/ruby-stringex-2.5.2/lib/stringex/localization/converter.rb:58:in `block in translate!' /tmp/buildd/ruby-stringex-2.5.2/lib/stringex/localization/converter.rb:57:in `each' /tmp/buildd/ruby-stringex-2.5.2/lib/stringex/localization/converter.rb:57:in `translate!' /tmp/buildd/ruby-stringex-2.5.2/lib/stringex/string_extensions.rb:92:in `block in convert_vulgar_fractions' /tmp/buildd/ruby-stringex-2.5.2/lib/stringex/localization.rb:86:in `instance_exec' /tmp/buildd/ruby-stringex-2.5.2/lib/stringex/localization.rb:86:in `convert' /tmp/buildd/ruby-stringex-2.5.2/lib/stringex/string_extensions.rb:199:in `stringex_convert' /tmp/buildd/ruby-stringex-2.5.2/lib/stringex/string_extensions.rb:91:in `convert_vulgar_fractions' /tmp/buildd/ruby-stringex-2.5.2/test/unit/localization/de_test.rb:115:in `block (2 levels) in class:GermanYAMLLocalizationTest' === ...E === Error: test_assigns_locale_in_i18n_backend(LocalizationTest) I18n::InvalidLocale: :pt-BR is not a valid locale /usr/lib/ruby/vendor_ruby/i18n.rb:285:in `enforce_available_locales!' /usr/lib/ruby/vendor_ruby/i18n/config.rb:13:in `locale=' /usr/lib/ruby/vendor_ruby/i18n.rb:35:in `locale=' /tmp/buildd/ruby-stringex-2.5.2/test/unit/localization_test.rb:132:in `test_assigns_locale_in_i18n_backend' 129: 130: assert_equal :en, Stringex::Localization.locale 131: = 132: I18n.locale = other_locale 133: assert_equal other_locale, Stringex::Localization.locale 134: 135: Stringex::Localization.locale = :de === ... ... ... Finished in 5.835713975 seconds. 792 tests, 807 assertions, 0 failures, 305 errors, 0 pendings, 0 omissions, 0 notifications 61.4899% passed 135.72 tests/s, 138.29 assertions/s rake aborted! Command failed with status (1): [ruby -Ilib:lib:test -I/usr/lib/ruby/vendor_ruby /usr/lib/ruby/vendor_ruby/rake/rake_test_loader.rb test/unit/**/*_test.rb ] -e:1:in `main' Tasks: TOP = default = test (See full trace by running task with --trace) ERROR: Test ruby2.1 failed. Exiting. dh_auto_install: dh_ruby --install /tmp/buildd/ruby-stringex-2.5.2/debian/ruby-stringex returned exit code 1 debian/rules:15: recipe for target 'binary' failed make: *** [binary] Error 1 dpkg-buildpackage: error: fakeroot
Bug#784300: marked as done (telepathy-qt: FTBFS: B-D on old libssl1.0.0 no longer satisfiable)
Your message dated Thu, 07 May 2015 22:30:16 + with message-id e1yquj6-0005kv...@franck.debian.org and subject line Bug#784300: fixed in telepathy-qt 0.9.5+dfsg-3 has caused the Debian Bug report #784300, regarding telepathy-qt: FTBFS: B-D on old libssl1.0.0 no longer satisfiable 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.) -- 784300: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=784300 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Source: telepathy-qt Version: 0.9.5+dfsg-2 Severity: serious Justification: fails to build from source (but built successfully in the past) Builds of telepathy-qt against unstable have been impossible, as telepathy-qt declares a build dependency on libssl1.0.0 (= 1.0.2) but 1.0.2a-1 reached unstable before the latest telepathy-qt upload. (1.0.1k-3 is still in testing, but that's not helpful here.) Could you please make it possible to build telepathy-qt against the current libssl1.0.0 release? Thanks! ---End Message--- ---BeginMessage--- Source: telepathy-qt Source-Version: 0.9.5+dfsg-3 We believe that the bug you reported is fixed in the latest version of telepathy-qt, 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 784...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Diane Trout di...@ghic.org (supplier of updated telepathy-qt 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: Thu, 07 May 2015 13:12:05 -0700 Source: telepathy-qt Binary: libtelepathy-qt4-2 libtelepathy-qt4-farstream2 libtelepathy-qt4-dev libtelepathy-qt4-dbg libtelepathy-qt4-doc libtelepathy-qt5-0 libtelepathy-qt5-farstream0 libtelepathy-qt5-dev libtelepathy-qt5-dbg Architecture: source amd64 all Version: 0.9.5+dfsg-3 Distribution: unstable Urgency: medium Maintainer: Debian KDE Extras Team pkg-kde-ext...@lists.alioth.debian.org Changed-By: Diane Trout di...@ghic.org Description: libtelepathy-qt4-2 - Telepathy framework - Qt 4 library libtelepathy-qt4-dbg - Qt 4 Telepathy library (debug symbols) libtelepathy-qt4-dev - Qt 4 Telepathy library (headers and static library) libtelepathy-qt4-doc - Qt 4 Telepathy library (documentation) libtelepathy-qt4-farstream2 - Telepathy/Farsight integration - Qt 4 library libtelepathy-qt5-0 - Telepathy framework - Qt 5 library libtelepathy-qt5-dbg - Qt 5 Telepathy library (debug symbols) libtelepathy-qt5-dev - Qt 5 Telepathy library (headers and static library) libtelepathy-qt5-farstream0 - Telepathy/Farsight integration - Qt 5 library Closes: 784300 Changes: telepathy-qt (0.9.5+dfsg-3) unstable; urgency=medium . * Remove libssl1.0.0 version dependency (Closes: #784300) * Add myself and Michał Zając to the debian/copyright block * Update libtelepathy-qt5-0.symbols * Disable python-dbus, python-gobject build-depends as they are for disabled tests. * Move uscan --repack command out of separate script and into debian/rules Checksums-Sha1: 87aac3f4e51e046c21357a8b135f5e34a83a896c 3057 telepathy-qt_0.9.5+dfsg-3.dsc 6a93b72fb0ffdf6630996ee5fc769f76361f02a0 1784445 telepathy-qt_0.9.5+dfsg.orig.tar.gz 4d831cdc99263597d734ce7403a48f914ce3ebb3 55892 telepathy-qt_0.9.5+dfsg-3.debian.tar.xz b36ebdd8660f2c6e5c1174b192d018d3f0d1db79 1871864 libtelepathy-qt4-2_0.9.5+dfsg-3_amd64.deb abed3be4d7bda1740765921b3d096ecfecaf86a6 9702 libtelepathy-qt4-farstream2_0.9.5+dfsg-3_amd64.deb eec9fc3c64015d5119e8bb0c31bfdb5cdda3c65f 556198 libtelepathy-qt4-dev_0.9.5+dfsg-3_amd64.deb 4017b27c20bd72328ed0cc79309828580ad5a91c 16886480 libtelepathy-qt4-dbg_0.9.5+dfsg-3_amd64.deb ee74ff864ef4e7f544edd853b01cc3f739819fc1 9143798 libtelepathy-qt4-doc_0.9.5+dfsg-3_all.deb 89d77f2191a6129f16c07e105d7c562c89f56e60 1396130 libtelepathy-qt5-0_0.9.5+dfsg-3_amd64.deb b4d9c79b4367605c6eceda44007ee1a5bd30d54e 9836 libtelepathy-qt5-farstream0_0.9.5+dfsg-3_amd64.deb ae9201f1b127c937b424864a16635f3954818130 623174 libtelepathy-qt5-dev_0.9.5+dfsg-3_amd64.deb 3b05295c7ed70989faff78094e9445f0acc6795c 24716590 libtelepathy-qt5-dbg_0.9.5+dfsg-3_amd64.deb Checksums-Sha256: b4d58ba2f073b0cf305016d6067adb68dbde1b15d2f0fd6b9fdd3d5dbfa64631 3057
Bug#765124: marked as done (ruby-stringex: FTBFS: ERROR: Test ruby2.1 failed: Running tests for ruby2.1 using debian/ruby-tests.rake ...)
Your message dated Thu, 07 May 2015 22:29:01 + with message-id e1yquht-0004mr...@franck.debian.org and subject line Bug#765124: fixed in ruby-i18n 0.6.11-2 has caused the Debian Bug report #765124, regarding ruby-stringex: FTBFS: ERROR: Test ruby2.1 failed: Running tests for ruby2.1 using debian/ruby-tests.rake ... 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.) -- 765124: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=765124 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Source: ruby-stringex Version: 2.5.2-2 Severity: serious Tags: jessie sid User: debian...@lists.debian.org Usertags: qa-ftbfs-20141012 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): === ...E === Error: test_assigns_locale_in_i18n_backend(LocalizationTest) I18n::InvalidLocale: :pt-BR is not a valid locale /usr/lib/ruby/vendor_ruby/i18n.rb:285:in `enforce_available_locales!' /usr/lib/ruby/vendor_ruby/i18n/config.rb:13:in `locale=' /usr/lib/ruby/vendor_ruby/i18n.rb:35:in `locale=' /«PKGBUILDDIR»/test/unit/localization_test.rb:132:in `test_assigns_locale_in_i18n_backend' 129: 130: assert_equal :en, Stringex::Localization.locale 131: = 132: I18n.locale = other_locale 133: assert_equal other_locale, Stringex::Localization.locale 134: 135: Stringex::Localization.locale = :de === ... ... ... Finished in 8.502547586 seconds. 792 tests, 807 assertions, 0 failures, 305 errors, 0 pendings, 0 omissions, 0 notifications 61.4899% passed 93.15 tests/s, 94.91 assertions/s rake aborted! Command failed with status (1): [ruby -Ilib:lib:test -I/usr/lib/ruby/vendor_ruby /usr/lib/ruby/vendor_ruby/rake/rake_test_loader.rb test/unit/**/*_test.rb ] -e:1:in `main' 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/10/12/ruby-stringex_2.5.2-2_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: ruby-i18n Source-Version: 0.6.11-2 We believe that the bug you reported is fixed in the latest version of ruby-i18n, 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 765...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Lucas Nussbaum lu...@debian.org (supplier of updated ruby-i18n 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: Thu, 07 May 2015 22:37:30 +0200 Source: ruby-i18n Binary: ruby-i18n Architecture: source all Version: 0.6.11-2 Distribution: unstable Urgency: medium Maintainer: Debian Ruby Extras Maintainers pkg-ruby-extras-maintain...@lists.alioth.debian.org Changed-By: Lucas Nussbaum lu...@debian.org Description: ruby-i18n - I18n and localization solution for Ruby Closes: 765124 770194 Changes: ruby-i18n (0.6.11-2) unstable; urgency=medium . * Team upload. * Remove myself from Uploaders. * Add patch revert-available-locales-cache.patch. Closes: #770194, #765124 Checksums-Sha1: d896846a318dd09c9d7ac5e3a8cb81efe5f5df1f 2054 ruby-i18n_0.6.11-2.dsc dd7a06c609c6a671d53f8876b6004281137a71de 4948
Bug#781566: COPYING2 contains some armchair licensing
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi There ! Still waiting for the official release. Thanks, Jerome -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.12 (GNU/Linux) iQEcBAEBAgAGBQJVS+sOAAoJEIC/w4IMSybjf78IAJ359/cFFieg7SvJktgrwBGO 4w8rmDEyLhNK/tq8kOvJ1IlJOwpyJ0HIEXdpJ7FwvLu0dgOrxs/Wiv+VNdqgbiU4 R2xE9BEpUhUwHjOly7DBRihU0MxQIvmijISZ3+JxMJT0MiI4K8r1xiH9Upz6y4C6 DGvT6HpYg6/T4bI2Asa4fGyD1mOdp4QabM/C1aJmUOYe0WD3pi2lVgyiPb86IWmu WhO/5R2dzsSI1AyhS8cjrIqHu2pwL5mpTklGsie+EvYGBHniFRfwc4c0NmtnVMQk sDLOoF+MH/KAZvOLulwo52IY+wtJJsaaVCt9YLv1uYNWubXOEDoEZSAk/XxvTTc= =uC8K -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
Bug#784702: wmweather+: Should Build-Depend on libwraster-dev.
Package: wmweather+ Version: 2.15-1 Severity: serious Tags: patch Justification: Policy 4.2 Beginning with wmaker version 0.95.6-1, libwraster3-dev has been renamed to libwraster-dev. As this is a build dependency of wdm, debian/control should be updated accordingly. diff --git a/debian/control b/debian/control index 4be3317..c1cf0ac 100644 --- a/debian/control +++ b/debian/control @@ -2,7 +2,7 @@ Source: wmweather+ Section: x11 Priority: optional Maintainer: Martin Stigge mar...@stigge.org -Build-Depends: libpcre3-dev, libcurl4-gnutls-dev, libwraster3-dev, debhelper (= 9) +Build-Depends: libpcre3-dev, libcurl4-gnutls-dev, libwraster-dev, debhelper (= 9) Standards-Version: 3.9.6 Vcs-Browser: http://anonscm.debian.org/viewvc/collab-maint/deb-maint/wmweather%2B/ Vcs-Svn: svn://anonscm.debian.org/collab-maint/deb-maint/wmweather+/
Bug#784166: widelands: Game crashes on song change
Hello Alex, One last question: did you try to install the amd64 version specifically? I'm not sure how the multi-arch support works these days. If not, would it be easy for you to try to do it? Yes, my tests were done on my regular amd64 desktop installation. That was with widelands_18-3+b1_amd64.deb. Thank you for taking the time to look into the issue! I wish I could downgrade the libboost packages needed to compile the source code to see if the build would have the bug or not. They are not in the dependencies but are on the build-deps: https://packages.debian.org/source/jessie/widelands I am actually running Squeeze with some packages from Stretch. I did a manual build from the source code and the game runs fine, with these exact packages you listed for me. I am still suspecting the problem to be libboost (check the bug report I mentioned earlier for why) even though I can't be sure. I guess I should probably close the bug if we cannot reproduce it, since it could be due to my weird package mix? For the fun of it I tried to really reproduce the situation (qemu-VM): - installed Squeeze LTS with LXDE - added Stretch sources.list But I was not able to cleanly install widelands via apt. Trying to manually installing via dpkg led also to some (for me) unresolvable dependencies (without doing nearly half of the dist-upgrade). Therefore I am short before thinking that now your package system is in an inconsistent state. Unfortunately I got myself into a sort of a deadlock with that and need to reinstall the system from scratch. As I think you also did a libc-upgrade (2.11.3-4+deb6u5 to 2.19-18 ?) I cannot say how a downgrade of it has to be done. Probably a dist-upgrade to Jessie or Stretch could work ... (But for this to work the package system needs to be consistent - you have checked what apt-get install -f proposes?) - At least, the problem this report was opened for seems to be a result of the package mix of Squeeze and Stretch. Kind regards, Bernhard -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#784295: marked as done (neutron-lbaas-agent: fails to upgrade from 'jessie' - trying to overwrite /etc/neutron/rootwrap.d/lbaas-haproxy.filters)
Your message dated Thu, 07 May 2015 22:25:53 + with message-id e1yquer-0003z5...@franck.debian.org and subject line Bug#784295: fixed in neutron-lbaas 2015.1.0-2 has caused the Debian Bug report #784295, regarding neutron-lbaas-agent: fails to upgrade from 'jessie' - trying to overwrite /etc/neutron/rootwrap.d/lbaas-haproxy.filters 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.) -- 784295: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=784295 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: neutron-lbaas-agent Version: 2015.1.0-1 Severity: serious User: debian...@lists.debian.org Usertags: piuparts Hi, during a test with piuparts I noticed your package fails to upgrade from 'jessie'. It installed fine in 'jessie', then the upgrade to 'sid' fails because it tries to overwrite other packages files without declaring a Breaks+Replaces relation. See policy 7.6 at https://www.debian.org/doc/debian-policy/ch-relationships.html#s-replaces From the attached log (scroll to the bottom...): Selecting previously unselected package neutron-lbaas-agent. Preparing to unpack .../neutron-lbaas-agent_2015.1.0-1_all.deb ... Unpacking neutron-lbaas-agent (2015.1.0-1) ... dpkg: error processing archive /var/cache/apt/archives/neutron-lbaas-agent_2015.1.0-1_all.deb (--unpack): trying to overwrite '/etc/neutron/rootwrap.d/lbaas-haproxy.filters', which is also in package neutron-common 2014.1.3-12 cheers, Andreas neutron-common=2014.1.3-12_neutron-lbaas-agent=2015.1.0-1.log.gz Description: application/gzip ---End Message--- ---BeginMessage--- Source: neutron-lbaas Source-Version: 2015.1.0-2 We believe that the bug you reported is fixed in the latest version of neutron-lbaas, 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 784...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Thomas Goirand z...@debian.org (supplier of updated neutron-lbaas 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: Thu, 07 May 2015 23:42:47 +0200 Source: neutron-lbaas Binary: python-neutron-lbaas neutron-lbaas-agent Architecture: source all Version: 2015.1.0-2 Distribution: unstable Urgency: medium Maintainer: PKG OpenStack openstack-de...@lists.alioth.debian.org Changed-By: Thomas Goirand z...@debian.org Description: neutron-lbaas-agent - OpenStack virtual network service - lbass agent python-neutron-lbaas - OpenStack virtual network service - Python library Closes: 784295 Changes: neutron-lbaas (2015.1.0-2) unstable; urgency=medium . * Adds a Breaks+Replaces of neutron-common ( 2015.1~) to avoid clashes at upgrade time (Closes: #784295). Checksums-Sha1: 080441cf4293c196247905a8a6440efe070b5e1b 3000 neutron-lbaas_2015.1.0-2.dsc 4fddc3adb77fd1be16d6b3efa01b3f5e1702109b 3428 neutron-lbaas_2015.1.0-2.debian.tar.xz b039ca5724aadc1881790e47b9604d42ffb793a8 163558 python-neutron-lbaas_2015.1.0-2_all.deb 1983b47f4d0ce176648cdc281f7279902db60372 7920 neutron-lbaas-agent_2015.1.0-2_all.deb Checksums-Sha256: 42d64dd12e3a0f917c40698c1f1232566b4c9b112174daa4ac26409ede699f36 3000 neutron-lbaas_2015.1.0-2.dsc a357598858cf6fa676a26a7326efc46c4420e60a448454ae6bf2ede044bd0c6b 3428 neutron-lbaas_2015.1.0-2.debian.tar.xz d51c67206662ecd0f83e6f7554a3170a808deb57b58303de3b8a2a75ac1f470e 163558 python-neutron-lbaas_2015.1.0-2_all.deb cad42334023bbebefb918aa9b33c2ced9f57b7c8b67c4e3720f5f075ab1a0029 7920 neutron-lbaas-agent_2015.1.0-2_all.deb Files: 7a4b7dec64d09dc5ba120fb19593e013 3000 net optional neutron-lbaas_2015.1.0-2.dsc e0ca7793081f84d640503f5ba47ef171 3428 net optional neutron-lbaas_2015.1.0-2.debian.tar.xz d64f65170cd174f0969de668f9af6095 163558 python optional python-neutron-lbaas_2015.1.0-2_all.deb a958fe95ce4be72924b292610e04eab7 7920 net optional neutron-lbaas-agent_2015.1.0-2_all.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1 iQIcBAEBCAAGBQJVS91/AAoJENQWrRWsa0P++MEP/A0gz3dzndK5cK/3oWl1IZEV 1Zlpdoc0JsT8I9ZLVda0rZyWTAQlE/f4Dqmccl9xbElp3EcTAeSm4cD5VW4TQxHN vIyIr8tH0OXhX6WaZybn4AaIdWbfYB3IVDytcINkzoesXWrku44S1oF07s/LshhI
Processed: tagging 784709
Processing commands for cont...@bugs.debian.org: # Unlikely to be easily solved by a newcomer... tags 784709 - newcomer Bug #784709 [os-prober] os-prober prevent the upgrade to jessie Removed tag(s) newcomer. thanks Stopping processing here. Please contact me if you need assistance. -- 784709: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=784709 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#784298: marked as done (python-pygit2: FTBFS: Requirement.parse('cffi') not found)
Your message dated Thu, 07 May 2015 23:22:58 +
with message-id e1yqv86-0005g6...@franck.debian.org
and subject line Bug#784298: fixed in python-pygit2 0.21.4-2
has caused the Debian Bug report #784298,
regarding python-pygit2: FTBFS: Requirement.parse('cffi') 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.)
--
784298: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=784298
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
---BeginMessage---
Source: python-pygit2
Version: 0.21.4-1
Severity: serious
Justification: fails to build from source
Builds of python-pygit2 in minimal environments (as on the
autobuilders) have been failing:
distutils.errors.DistutilsError: Could not find suitable distribution for
Requirement.parse('cffi')
dh_auto_clean: python setup.py clean -a returned exit code 1
make: *** [clean] Error 1
debian/rules:12: recipe for target 'clean' failed
Please add python(3)-cffi to Build-Depends and double check with
pbuilder or the like that you didn't miss anything else.
Thanks!
---End Message---
---BeginMessage---
Source: python-pygit2
Source-Version: 0.21.4-2
We believe that the bug you reported is fixed in the latest version of
python-pygit2, 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 784...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Thomas Goirand z...@debian.org (supplier of updated python-pygit2 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: Thu, 07 May 2015 21:50:21 +
Source: python-pygit2
Binary: python-pygit2 python3-pygit2 python-pygit2-doc
Architecture: source amd64 all
Version: 0.21.4-2
Distribution: unstable
Urgency: medium
Maintainer: PKG OpenStack openstack-de...@lists.alioth.debian.org
Changed-By: Thomas Goirand z...@debian.org
Description:
python-pygit2 - bindings for libgit2 - Python 2.x
python-pygit2-doc - bindings for libgit2 - doc
python3-pygit2 - bindings for libgit2 - Python 3.x
Closes: 784298
Changes:
python-pygit2 (0.21.4-2) unstable; urgency=medium
.
[ Yaroslav Halchenko ]
* debian/watch
- add trailing slash to fix downloads
* debian/control
- add python{,3}-{cffi,pycparser} to build-depends (Closes: #784298).
* debian/rules
- export http{,s}_proxy to prevent any online activity during build
.
[ Thomas Goirand ]
* Uploading to unstable.
Checksums-Sha1:
1dcc4fd6cf6dec797216f641c3ba997029efda90 2289 python-pygit2_0.21.4-2.dsc
39c47f6ae15dcd14200c15e71736b9b87a4293b4 3408
python-pygit2_0.21.4-2.debian.tar.xz
e92c4326d81b705936f2b94147dae14f1b5041c0 75656 python-pygit2_0.21.4-2_amd64.deb
ff45b1eec5e7fb8c129f8934e0f3b4492f7539b7 76204
python3-pygit2_0.21.4-2_amd64.deb
76c9e1cbd23e0bfd767a9d18fcbf4c4d63366d55 305242
python-pygit2-doc_0.21.4-2_all.deb
Checksums-Sha256:
09170c5acacc301befc2e2c6b1f636b23e1092db18e9779543e4cd48197d87e0 2289
python-pygit2_0.21.4-2.dsc
ccf112126f20daa8077e31769210acd5cf03c0fa59e3e35ea5ff70b8a510bedc 3408
python-pygit2_0.21.4-2.debian.tar.xz
d82f23feb57c484b388691c70013682a2795a53708fc582ded9f79b0718990b9 75656
python-pygit2_0.21.4-2_amd64.deb
49e9511e5c6afa94f565fcad9fe3268a07a8e10828c01f711d3572a52fe23fcc 76204
python3-pygit2_0.21.4-2_amd64.deb
279917dbaccf4f25ad18f6c4d941113d2629ee79e6f30124deddd19bbac9a9c2 305242
python-pygit2-doc_0.21.4-2_all.deb
Files:
26480a868d1e3db4cb500a435a1b14d4 2289 python optional
python-pygit2_0.21.4-2.dsc
a58e8e7152820a92b655309c452d370f 3408 python optional
python-pygit2_0.21.4-2.debian.tar.xz
31ca43fa033c4a3a6094e55200f705f7 75656 python optional
python-pygit2_0.21.4-2_amd64.deb
6aa6ea61fc28734e2956a3f71fdc1189 76204 python optional
python3-pygit2_0.21.4-2_amd64.deb
7bdf5e4a8c49414af30624af2c13e88c 305242 doc optional
python-pygit2-doc_0.21.4-2_all.deb
-BEGIN PGP SIGNATURE-
Version: GnuPG v1
iQIcBAEBCAAGBQJVS+sJAAoJENQWrRWsa0P+jf0P/iRsb0elpHG+tB2YvDeP9CvR
X9/2qXkfasz/MI1afVIf3MbreiLIp4/G++HqsDyiCE+0n+tKxz1pZYUZk85x9ICb
qve9XeifQ4ynPrDtW1KNUkfG1IaWZ+TJDB1BQy93zHEdjRL2uIU12JRhiv+XvlgG
n0uruyr1NMtGl0rXKx9YspHrZ6IId2NKPGPVTPYYvj1XJctvegMTG9rxOm0iFbLr
Eo4QzZdJfAtLPFsShAe3qvZxafhLn5tQJI2UZrbtvMSAvmce/kRSx91OUcomvTRq
Bug#784597: xserver-xorg-core: ABI mismatch?
Okay, thanks. On Thu, May 7, 2015 at 3:27 AM, Vincent Cheng vch...@debian.org wrote: reassign 784597 src:xserver-xorg-video-intel forcemerge 78 784597 thanks Hi Dale, On Wed, May 6, 2015 at 5:48 PM, Dale Harris rod...@gmail.com wrote: Package: xserver-xorg-core Version: 2:1.17.1-2 Severity: normal Hi, I did an OS upgrade recently, I was noticing some problems with X windows using way too much CPU, so I thought would try reconfiguring it. However now when I do Xorg -configure, I see: (EE) module ABI major version (15) doesn't match the server's version (19) Also I notice that my video driver, xserver-xorg-video-intel, is not installed. I tried reinstalling it and I get: The following packages have unmet dependencies: xserver-xorg-video-intel : Depends: xorg-video-abi-18 So I appear to be in a bit of version problem here. Is there any suggestions on how to work around this? Or does some packages just need to be updated? This is a direct consequence of #78, i.e. xserver-xorg-video-intel failing to build against latest xserver-xorg-core in sid and thus getting removed if you blindly ran dist-upgrade (due to unfulfilled dependencies). I'll upload a fix for xserver-xorg-video-intel today/tomorrow, please install it then. Regards, Vincent -- Dale Harris rod...@maybe.org rod...@gmail.com /.-) -- 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 784656 is important
Processing commands for cont...@bugs.debian.org: severity 784656 important Bug #784656 [winbind] winbind: PANIC when trying to authenticate user Severity set to 'important' from 'grave' thanks Stopping processing here. Please contact me if you need assistance. -- 784656: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=784656 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#784655: can't rebuild casablanca with newer libstdc++6 (sid)
Hi Matthias, thanks for the quick reply are you running sid, or stretch? in plain sid the package doesn't build at all, in order to trim down the differences I started from a Stretch clean pbuilder environment, and upgraded stuff until I got the problem. is the testsuite rebuilt after the new libstdc++ installed? if yes, is the libstdc++-5-dev package upgraded as well? yes, of course the testsuite has been rebuilt, if that matters, I'm compiling with -std=c++11 flag so, to resume starting from stretch, enabling sid repository apt-get install libstdc++6 libstdc++-5-dev The following extra packages will be installed: gcc-5-base libasan2 libatomic1 libcilkrts5 libgcc-5-dev libgcc1 libgomp1 libitm1 liblsan0 libmpx0 libquadmath0 libtsan0 libubsan0 fetch casablanca and try to build. /casablanca/Release/tests/functional/streams/fstreambuf_tests.cpp:158: error: Failure in OpenForReadDoesntCreateFile2: CHECK_EQUAL(static_castint(std::errc::no_such_file_or_directory), _condFound.value()) where static_castint(std::errc::no_such_file_or_directory)=2 and _condFound.value()=0 please can you distill down a test case? the test case seems pretty generic utility::string_t fname = U(OpenForReadDoesntCreateFile2.txt); VERIFY_THROWS_SYSTEM_ERROR(OPENchar(fname, std::ios_base::in | std::ios_base::binary ).get(), std::errc::no_such_file_or_directory); std::ifstream is; VERIFY_IS_NULL(is.rdbuf()-open(fname.c_str(), std::ios::in | std::ios_base::binary)); isn't this something generic? (sorry I don't undestand too much g++ code, moreover I'm using an embedded UnitTestpp because the Debian one is too outdated) cheers, G. -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#784664: jenkins: FTBFS: error: package org.mindrot does not exist
Package: src:jenkins Version: 1.565.3-3 Severity: serious Justification: fails to build from source (but built successfully in the past) [...] [INFO] - [ERROR] COMPILATION ERROR : [INFO] - [ERROR] /tmp/buildd/jenkins-1.565.3/core/src/main/java/hudson/security/HudsonPrivateSecurityRealm.java:[61,18] error: package org.mindrot does not exist [ERROR] /tmp/buildd/jenkins-1.565.3/core/src/main/java/hudson/security/HudsonPrivateSecurityRealm.java:[61,18] error: package org.mindrot does not exist [ERROR] /tmp/buildd/jenkins-1.565.3/core/src/main/java/hudson/security/HudsonPrivateSecurityRealm.java:[645,41] error: cannot find symbol [ERROR] symbol: variable BCrypt /tmp/buildd/jenkins-1.565.3/core/src/main/java/hudson/security/HudsonPrivateSecurityRealm.java:[645,19] error: cannot find symbol [ERROR] symbol: variable BCrypt /tmp/buildd/jenkins-1.565.3/core/src/main/java/hudson/security/HudsonPrivateSecurityRealm.java:[649,19] error: cannot find symbol [INFO] 5 errors [INFO] - [INFO] [ERROR] BUILD FAILURE [INFO] [INFO] Compilation failure /tmp/buildd/jenkins-1.565.3/core/src/main/java/hudson/security/HudsonPrivateSecurityRealm.java:[61,18] error: package org.mindrot does not exist /tmp/buildd/jenkins-1.565.3/core/src/main/java/hudson/security/HudsonPrivateSecurityRealm.java:[61,18] error: package org.mindrot does not exist /tmp/buildd/jenkins-1.565.3/core/src/main/java/hudson/security/HudsonPrivateSecurityRealm.java:[645,41] error: cannot find symbol symbol: variable BCrypt /tmp/buildd/jenkins-1.565.3/core/src/main/java/hudson/security/HudsonPrivateSecurityRealm.java:[645,19] error: cannot find symbol symbol: variable BCrypt /tmp/buildd/jenkins-1.565.3/core/src/main/java/hudson/security/HudsonPrivateSecurityRealm.java:[649,19] error: cannot find symbol [INFO] [INFO] Trace org.apache.maven.BuildFailureException: Compilation failure at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:715) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecycle(DefaultLifecycleExecutor.java:556) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:535) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:387) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:348) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:180) at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:328) at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:138) at org.apache.maven.cli.MavenCli.main(MavenCli.java:362) at org.apache.maven.cli.compat.CompatibleMain.main(CompatibleMain.java:60) at org.debian.maven.Wrapper.main(Wrapper.java:89) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:606) at org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315) at org.codehaus.classworlds.Launcher.launch(Launcher.java:255) at org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430) at org.codehaus.classworlds.Launcher.main(Launcher.java:375) Caused by: org.apache.maven.plugin.CompilationFailureException: Compilation failure at org.apache.maven.plugin.AbstractCompilerMojo.execute(AbstractCompilerMojo.java:729) at org.apache.maven.plugin.CompilerMojo.execute(CompilerMojo.java:128) at org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:490) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:694) ... 18 more [INFO] [INFO] Total time: 1 minute 11 seconds [INFO] Finished at: Thu May 07 15:55:25 UTC 2015 [INFO] Final Memory: 18M/90M [INFO] /usr/share/cdbs/1/class/maven.mk:93: recipe for target 'mvn-build' failed make: *** [mvn-build] Error 1 dpkg-buildpackage: error: debian/rules build gave error exit status 2 -- System Information: Debian Release: 7.8 APT
Bug#783915: whohas: maintainer required
On Fri, 01 May 2015 10:07:57 +0100 Jonathan Wiltshire wrote: whohas upstream is at best dormant; an ITA bug remains outstanding since January 2013. This bug is to prevent migration to Stretch. The upstream git repository has been slightly active. Today I've fixed the remaining bugs filed in Debian and am in the process of consulting the various stakeholders before putting out a new release, sorting out the Debian git repository and packaging the new release for Debian. https://github.com/whohas/whohas/ -- bye, pabs https://wiki.debian.org/PaulWise signature.asc Description: This is a digitally signed message part
Bug#784587: [Pkg-utopia-maintainers] Bug#784587: network-manager: does not set up resolv.conf
On Thu, 2015-05-07 at 13:15 +0900, Norbert Preining wrote: On Thu, 07 May 2015, Michael Biebl wrote: The attached patch should fix the issue. Will poke upstream for a review and upload tomorrow. Thanks for the quick fix! Got found and fixed yesterday in nm-1-0... In git master there is no longer fallback if resolvconf fails for some reason; but the resolv.conf manager is now a config option. So we'd expect distros to ship a sub-package that drops a config snippet into /etc/NetworkManager/conf.d/ enabling resolvconf which also requires the resolvconf package itself, so that when the config option is set, resolvconf is always installed. We may need some tweaking of the default handling here, but the idea is that if the user specifically chose resolvconf and it fails, that should be a hard failure and NM shouldn't be touching resolv.conf since the user told NM not to... Dan -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#784655: can't rebuild casablanca with newer libstdc++6 (sid)
On 05/07/2015 04:14 PM, Gianfranco Costamagna wrote: Package: gcc-5 Version: 5.1.1-4 Severity: Serious Justification: Package rebuild trigger a test failure. As said, casablanca doesn't pass the testsuite anymore with libstdc++6 library. I triggered a successful build from Stretch, and upgraded packages until I upgraded libstdc++6 are you running sid, or stretch? is the testsuite rebuilt after the new libstdc++ installed? if yes, is the libstdc++-5-dev package upgraded as well? any idea for the regression? please can you distill down a test case? -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#784671: gdm3 wouldn't start until caribou path changed
Package: gdm3 Version: 3.14.1-7 Severity: grave Tags: patch Justification: renders package unusable Dear Maintainer, Recently upgraded wheezy to testing (jessie) gdm3 wouldn't start. several log messages: May 4 18:24:25 tosh gnome-session[1371]: gnome-session[1371]: WARNING: Could not parse desktop file caribou-autostart.desktop or it references a not found TryExec binary There are 2 files of this name: /etc/xdg/autostart/caribou-autostart.desktop /usr/share/gdm/greeter/autostart/caribou-autostart.desktop I changed gdm's caribou-autostart.desktop path to caribou to match xdg version /usr/share/gdm/greeter/autostart/caribou-autostart.desktop Was: Exec=/usr/lib/gdm3/caribou Now: Exec=/usr/lib/caribou/caribou Gdm starts ok now. This may explain other people's gdm start problems -- System Information: Debian Release: stretch/sid APT prefers testing APT policy: (500, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 3.16.0-4-amd64 (SMP w/2 CPU cores) Locale: LANG=en_GB.utf8, LC_CTYPE=en_GB.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages gdm3 depends on: ii accountsservice 0.6.37-3+b1 ii adduser 3.113+nmu3 ii blackbox [x-window-manager] 0.70.1-27 ii dconf-cli0.22.0-1 ii dconf-gsettings-backend 0.22.0-1 ii debconf [debconf-2.0]1.5.56 ii fluxbox [x-window-manager] 1.3.5-2 ii flwm [x-window-manager] 1.02+cvs20080422-11 ii fvwm [x-window-manager] 1:2.6.5.ds-4 ii gir1.2-gdm3 3.14.1-7 ii gnome-session [x-session-manager]3.14.0-3 ii gnome-session-bin3.14.0-3 ii gnome-session-flashback [x-session-mana 3.8.1-7 ii gnome-settings-daemon3.14.2-3 ii gnome-shell 3.14.4-1 ii gnome-terminal [x-terminal-emulator] 3.14.1-1 ii gsettings-desktop-schemas3.14.1-1 ii icewm [x-window-manager] 1.3.8+githubmod+20150412+960629d-1 ii libaccountsservice0 0.6.37-3+b1 ii libaudit11:2.4-1+b1 ii libc62.19-18 ii libcanberra-gtk3-0 0.30-2.1 ii libcanberra0 0.30-2.1 ii libgdk-pixbuf2.0-0 2.31.1-2+b1 ii libgdm1 3.14.1-7 ii libglib2.0-0 2.44.0-2 ii libglib2.0-bin 2.44.0-2 ii libgtk-3-0 3.14.5-1 ii libpam-modules 1.1.8-3.1 ii libpam-runtime 1.1.8-3.1 ii libpam-systemd 215-17 ii libpam0g 1.1.8-3.1 ii librsvg2-common 2.40.5-1 ii libselinux1 2.3-2 ii libsystemd0 215-17 ii libwrap0 7.6.q-25 ii libx11-6 2:1.6.3-1 ii libxau6 1:1.0.8-1 ii libxdmcp61:1.1.2-1 ii libxrandr2 2:1.4.2-1+b1 ii lsb-base 4.1+Debian13+nmu1 ii metacity [x-window-manager] 1:3.14.3-1 ii mutter [x-window-manager]3.14.4-2 ii policykit-1 0.105-8 ii ratpoison [x-window-manager] 1.4.8-1 ii sawfish [x-window-manager] 1:1.5.3-2.4 ii ucf 3.0030 ii wm2 [x-window-manager] 4+svn20090216-3 ii wmaker [x-window-manager]0.95.5-2+b2 ii x11-common 1:7.7+7 ii x11-xserver-utils7.7+3+b1 ii xterm [x-terminal-emulator] 318-2 Versions of packages gdm3 recommends: ii at-spi2-core 2.14.0-1 ii desktop-base 8.0.2 ii gnome-icon-theme 3.12.0-1 ii gnome-icon-theme-symbolic 3.12.0-1 ii x11-xkb-utils 7.7+1 ii xserver-xephyr 2:1.16.4-1 ii xserver-xorg 1:7.7+7 ii zenity 3.14.0-1 Versions of packages gdm3 suggests: ii gnome-orca3.14.0-4 ii libpam-gnome-keyring 3.14.0-1+b1 -- Configuration Files: /etc/gdm3/daemon.conf changed: [daemon] [security] [xdmcp] [greeter] [chooser] [debug] -- debconf information: * shared/default-x-display-manager: gdm3 gdm3/daemon_name: /usr/sbin/gdm3 -- debsums errors found: debsums: changed file /usr/share/gdm/greeter/autostart/caribou-autostart.desktop (from gdm3 package) -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact
Bug#784647: libav-tools: avconv fails with Illegal Instruction
Control: reopen -1 Control: reassign -1 libopencv-imgproc2.4 2.4.9.1+dfsg-1 On 2015-05-07 15:06:26, vittorio.vall...@libero.it wrote: Hi, I tried to run avconv in gdb and here is the result: (gdb) run Starting program: /usr/bin/avconv [Thread debugging using libthread_db enabled] Using host libthread_db library /lib/i386-linux-gnu/libthread_db.so.1. Program received signal SIGILL, Illegal instruction. 0xb6613d36 in ?? () from /usr/lib/i386-linux-gnu/libopencv_imgproc.so.2.4 So it's not a bug in libav. Reassigning to libopencv-imgproc2.4. Cheers -- Sebastian Ramacher signature.asc Description: Digital signature
Processed: Re: Bug#784647: libav-tools: avconv fails with Illegal Instruction
Processing control commands:
reopen -1
Bug #784647 {Done: Sebastian Ramacher sramac...@debian.org} [src:libav]
libav-tools: avconv fails with Illegal Instruction
'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 libav/6:11.3-3.
reassign -1 libopencv-imgproc2.4 2.4.9.1+dfsg-1
Bug #784647 [src:libav] libav-tools: avconv fails with Illegal Instruction
Bug reassigned from package 'src:libav' to 'libopencv-imgproc2.4'.
No longer marked as found in versions libav/6:11.3-1.
Ignoring request to alter fixed versions of bug #784647 to the same values
previously set
Bug #784647 [libopencv-imgproc2.4] libav-tools: avconv fails with Illegal
Instruction
Marked as found in versions opencv/2.4.9.1+dfsg-1.
--
784647: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=784647
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: unmerging 783082
Processing commands for cont...@bugs.debian.org:
unmerge 783082
Bug #783082 {Done: Sebastian Ramacher sramac...@debian.org} [src:libav] video
players using libav crash with 'illegal instruction' on i586
Bug #784647 {Done: Sebastian Ramacher sramac...@debian.org} [src:libav]
libav-tools: avconv fails with Illegal Instruction
Disconnected #783082 from all other report(s).
thanks
Stopping processing here.
Please contact me if you need assistance.
--
783082: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=783082
784647: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=784647
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#784587: [Pkg-utopia-maintainers] Bug#784587: Bug#784587: network-manager: does not set up resolv.conf
Hi Dan! Am 07.05.2015 um 18:09 schrieb Dan Williams: On Thu, 2015-05-07 at 13:15 +0900, Norbert Preining wrote: On Thu, 07 May 2015, Michael Biebl wrote: The attached patch should fix the issue. Will poke upstream for a review and upload tomorrow. Thanks for the quick fix! Got found and fixed yesterday in nm-1-0... Hm, I don't do any changes in the nm-1-0 related to that. Where those fixes not pushed? In git master there is no longer fallback if resolvconf fails for some reason; but the resolv.conf manager is now a config option. So we'd expect distros to ship a sub-package that drops a config snippet into /etc/NetworkManager/conf.d/ enabling resolvconf which also requires the resolvconf package itself, so that when the config option is set, resolvconf is always installed. We may need some tweaking of the default handling here, but the idea is that if the user specifically chose resolvconf and it fails, that should be a hard failure and NM shouldn't be touching resolv.conf since the user told NM not to... I kind of liked the if-resolvconf-found-use-it behaviour. The new behaviour will be a bit icky if I go the subpackage route due to how conffiles are handled. conffiles (config files in /etc/) are not automatically removed by dpkg if the package is removed (they are only removed on purge). So if the user uninstalles (but doesn't purge) the sub-package, the conf.d snippet will stay around and he'll get resolv.conf failures because it's no longer guaranteed the resolvconf package is installed. -- Why is it that all of the instruments seeking intelligent life in the universe are pointed away from Earth? signature.asc Description: OpenPGP digital signature
Bug#784597: marked as done (xserver-xorg-core: ABI mismatch?)
Your message dated Thu, 7 May 2015 03:07:59 -0700 with message-id caczd_tauqpkut0gksjx9k0zo0xtcavv7meencn-mdvfhnou...@mail.gmail.com and subject line Re: Bug#78: xserver-xorg-video-intel: FTBFS with Xorg 1.17 has caused the Debian Bug report #78, regarding xserver-xorg-core: ABI mismatch? 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.) -- 78: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=78 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: xserver-xorg-core Version: 2:1.17.1-2 Severity: normal Hi, I did an OS upgrade recently, I was noticing some problems with X windows using way too much CPU, so I thought would try reconfiguring it. However now when I do Xorg -configure, I see: (EE) module ABI major version (15) doesn't match the server's version (19) Also I notice that my video driver, xserver-xorg-video-intel, is not installed. I tried reinstalling it and I get: The following packages have unmet dependencies: xserver-xorg-video-intel : Depends: xorg-video-abi-18 So I appear to be in a bit of version problem here. Is there any suggestions on how to work around this? Or does some packages just need to be updated? -- Package-specific info: X server symlink status: lrwxrwxrwx 1 root root 13 Oct 12 2013 /etc/X11/X - /usr/bin/Xorg -rwxr-xr-x 1 root root 2384712 May 4 19:24 /usr/bin/Xorg VGA-compatible devices on PCI bus: -- 00:02.0 VGA compatible controller [0300]: Intel Corporation 82Q35 Express Integrated Graphics Controller [8086:29b2] (rev 02) /etc/X11/xorg.conf does not exist. /etc/X11/xorg.conf.d does not exist. /etc/modprobe.d contains no KMS configuration files. Kernel version (/proc/version): --- Linux version 3.16.0-4-amd64 (debian-ker...@lists.debian.org) (gcc version 4.8.4 (Debian 4.8.4-1) ) #1 SMP Debian 3.16.7-ckt9-3 (2015-04-23) Xorg X server log files on system: -- -rw-r--r-- 1 root root 27861 Oct 23 2013 /var/log/Xorg.1.log -rw-r--r-- 1 root root 8675 May 6 20:37 /var/log/Xorg.0.log Contents of most recent Xorg X server log file (/var/log/Xorg.0.log): - [ 88608.487] X.Org X Server 1.17.1 Release Date: 2015-02-10 [ 88608.487] X Protocol Version 11, Revision 0 [ 88608.487] Build Operating System: Linux 3.16.0-4-amd64 x86_64 Debian [ 88608.487] Current Operating System: Linux spoon 3.16.0-4-amd64 #1 SMP Debian 3.16.7-ckt9-3 (2015-04-23) x86_64 [ 88608.487] Kernel command line: BOOT_IMAGE=/vmlinuz-3.16.0-4-amd64 root=/dev/mapper/spoon--vg-root ro quiet [ 88608.488] Build Date: 04 May 2015 11:22:06PM [ 88608.488] xorg-server 2:1.17.1-2 (http://www.debian.org/support) [ 88608.488] Current version of pixman: 0.32.6 [ 88608.488]Before reporting problems, check http://wiki.x.org to make sure that you have the latest version. [ 88608.488] Markers: (--) probed, (**) from config file, (==) default setting, (++) from command line, (!!) notice, (II) informational, (WW) warning, (EE) error, (NI) not implemented, (??) unknown. [ 88608.488] (==) Log file: /var/log/Xorg.0.log, Time: Wed May 6 20:37:30 2015 [ 88608.488] (II) Loader magic: 0x7f1876e0fd80 [ 88608.488] (II) Module ABI versions: [ 88608.488]X.Org ANSI C Emulation: 0.4 [ 88608.488]X.Org Video Driver: 19.0 [ 88608.488]X.Org XInput driver : 21.0 [ 88608.488]X.Org Server Extension : 9.0 [ 88608.488] (II) xfree86: Adding drm device (/dev/dri/card0) [ 88608.489] (--) PCI:*(0:0:2:0) 8086:29b2:1028:0211 rev 2, Mem @ 0xfea0/524288, 0xd000/268435456, 0xfeb0/1048576, I/O @ 0xec90/8 [ 88608.489] (--) PCI: (0:0:2:1) 8086:29b3:1028:0211 rev 2, Mem @ 0xfea8/524288 [ 88608.490] List of video drivers: [ 88608.490]radeon [ 88608.490]qxl [ 88608.490]sisusb [ 88608.490]tdfx [ 88608.490]trident [ 88608.490]mga [ 88608.490]openchrome [ 88608.490]vmware [ 88608.490]nouveau [ 88608.490]vboxvideo [ 88608.490]vesa [ 88608.490]fbdev [ 88608.490]modesetting [ 88608.490] (II) LoadModule: radeon [ 88608.490] (II) Loading /usr/lib/xorg/modules/drivers/radeon_drv.so [ 88608.490] (II) Module radeon: vendor=X.Org Foundation [ 88608.490]compiled for 1.17.1, module version = 7.5.0 [ 88608.490]Module class: X.Org Video Driver [ 88608.490]ABI class: X.Org Video Driver, version 19.0 [ 88608.490] (II) LoadModule: qxl [ 88608.490] (II) Loading /usr/lib/xorg/modules/drivers/qxl_drv.so [ 88608.490] (II)
Bug#784444: marked as done (xserver-xorg-video-intel: FTBFS with Xorg 1.17)
Your message dated Thu, 7 May 2015 03:07:59 -0700 with message-id caczd_tauqpkut0gksjx9k0zo0xtcavv7meencn-mdvfhnou...@mail.gmail.com and subject line Re: Bug#78: xserver-xorg-video-intel: FTBFS with Xorg 1.17 has caused the Debian Bug report #78, regarding xserver-xorg-video-intel: FTBFS with Xorg 1.17 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.) -- 78: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=78 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Source: xserver-xorg-video-intel Version: 2:2.21.15-2 Severity: serious Justification: fails to build from source (but built successfully in the past) Control: notfound -1 2:2.99.917-1~exp1 With the recent upload of Xorg 1.17 to unstable, the intel driver no longer builds successfully: https://buildd.debian.org/status/fetch.php?pkg=xserver-xorg-video-intelarch=amd64ver=2%3A2.21.15-2%2Bb3stamp=1430827769 ../../../../src/sna/fb/fbcopy.c: In function 'sfbCopyPlane': ../../../../src/sna/fb/fbcopy.c:222:10: error: too many arguments to function 'miHandleExposures' return miHandleExposures(src, dst, gc, ^ In file included from ../../../../src/sna/fb/fbcopy.c:27:0: /usr/include/xorg/mi.h:224:28: note: declared here extern _X_EXPORT RegionPtr miHandleExposures(DrawablePtr /*pSrcDrawable */ , ^ make[5]: *** [libfb_la-fbcopy.lo] Error 1 The version from experimental does build successfully in an unstable chroot though. It might be possible to backport a stack of patches from master, but I suspect it might be better to switch to the 2.99.x branch as discussed in https://bugs.debian.org/748753, as Ubuntu have. S ---End Message--- ---BeginMessage--- Version: 2:2.99.917-1 Forgot to mark this as closed in d/changelog, doing so manually instead. Vincent---End Message---
Bug#784647: libav-tools: avconv fails with Illegal Instruction
Package: libav-tools Version: 6:11.3-1 Severity: grave Justification: renders package unusable Dear Maintainer, *** Reporter, please consider answering these questions, where appropriate *** * What led up to the situation? Installing and trying to use avconv lead to the error * What exactly did you do (or not do) that was effective (or ineffective)? Tried to use the other binaries of the package like avplay * What was the outcome of this action? Running any of them returns an Illegal Instruction * What outcome did you expect instead? Normal functioning *** End of the template - remove these template lines *** -- System Information: Debian Release: 8.0 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable') Architecture: i386 (i686) Kernel: Linux 3.16.0-4-586 Locale: LANG=it_IT.UTF-8, LC_CTYPE=it_IT.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages libav-tools depends on: ii dpkg 1.17.25 ii libavcodec56 6:11.3-1 ii libavdevice556:11.3-1 ii libavfilter5 6:11.3-1 ii libavformat566:11.3-1 ii libavresample2 6:11.3-1 ii libavutil54 6:11.3-1 ii libc62.19-18 ii libsdl1.2debian 1.2.15-10+b1 ii libswscale3 6:11.3-1 ii libvdpau10.8-3 ii libx11-6 2:1.6.2-3 libav-tools recommends no packages. Versions of packages libav-tools suggests: pn frei0r-plugins none -- 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#784647: libav-tools: avconv fails with Illegal Instruction
Hi, I tried to run avconv in gdb and here is the result: (gdb) run Starting program: /usr/bin/avconv [Thread debugging using libthread_db enabled] Using host libthread_db library /lib/i386-linux-gnu/libthread_db.so.1. Program received signal SIGILL, Illegal instruction. 0xb6613d36 in ?? () from /usr/lib/i386-linux-gnu/libopencv_imgproc.so.2.4 Other maybe useful info: cat /proc/cpuinfo processor : 0 vendor_id : CentaurHauls cpu family : 6 model : 7 model name : VIA Samuel 2 stepping: 3 cpu MHz : 601.390 cache size : 64 KB fdiv_bug: no f00f_bug: no coma_bug: no fpu : yes fpu_exception : yes cpuid level : 1 wp : yes flags : fpu de tsc msr cx8 mtrr pge mmx 3dnow bogomips: 1202.78 clflush size: 32 cache_alignment : 32 address sizes : 32 bits physical, 32 bits virtual power management:
Bug#784300: telepathy-qt: FTBFS: B-D on old libssl1.0.0 no longer satisfiable
tags: pending fixed: 0.9.5+dfsg-3 Hello, I'd added the B-D because of the following libssl bug and that I didn't know I could upload to experimental based just on sid. #768476 openssl: Removes symbol without SONAME bump I removed the spurious B-D and will prepare the upload in little while. Diane -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#784587: [Pkg-utopia-maintainers] Bug#784587: Bug#784587: Bug#784587: network-manager: does not set up resolv.conf
Am 07.05.2015 um 19:08 schrieb Michael Biebl: Am 07.05.2015 um 18:09 schrieb Dan Williams: On Thu, 2015-05-07 at 13:15 +0900, Norbert Preining wrote: On Thu, 07 May 2015, Michael Biebl wrote: The attached patch should fix the issue. Will poke upstream for a review and upload tomorrow. Thanks for the quick fix! Got found and fixed yesterday in nm-1-0... Hm, I don't do any changes in the nm-1-0 related to that. I don't *see* any changes in the nm-1-0 branch related to that. -- Why is it that all of the instruments seeking intelligent life in the universe are pointed away from Earth? signature.asc Description: OpenPGP digital signature
Bug#784671: gdm3 wouldn't start until caribou path changed
Am 07.05.2015 um 19:01 schrieb jmullee: Package: gdm3 Version: 3.14.1-7 Severity: grave Tags: patch Justification: renders package unusable Dear Maintainer, Recently upgraded wheezy to testing (jessie) gdm3 wouldn't start. several log messages: May 4 18:24:25 tosh gnome-session[1371]: gnome-session[1371]: WARNING: Could not parse desktop file caribou-autostart.desktop or it references a not found TryExec binary There are 2 files of this name: /etc/xdg/autostart/caribou-autostart.desktop /usr/share/gdm/greeter/autostart/caribou-autostart.desktop I changed gdm's caribou-autostart.desktop path to caribou to match xdg version /usr/share/gdm/greeter/autostart/caribou-autostart.desktop Was: Exec=/usr/lib/gdm3/caribou Now: Exec=/usr/lib/caribou/caribou Gdm starts ok now. This may explain other people's gdm start problems While I can't reproduce the start failure, this seems like an obvious error, indeed. diff --git a/data/autostart/caribou-autostart.desktop.in b/data/autostart/caribou-autostart.desktop.in index 38b3fc6..9f72d52 100644 --- a/data/autostart/caribou-autostart.desktop.in +++ b/data/autostart/caribou-autostart.desktop.in @@ -1,6 +1,6 @@ [Desktop Entry] Type=Application Name=Caribou -Exec=@LIBEXECDIR@/caribou +Exec=@LIBDIR@/caribou/caribou AutostartCondition=GSettings org.gnome.desktop.a11y.applications screen-keyboard-enabled X-GNOME-AutoRestart=true -- Why is it that all of the instruments seeking intelligent life in the universe are pointed away from Earth? signature.asc Description: OpenPGP digital signature
Bug#784009: Segmentation fault
On 2015-05-06 Niels Möller ni...@lysator.liu.se wrote: Andreas Metzler ametz...@bebt.de writes: No, that does not work. wget would be looking for unversioned references to nettle-symbols, and given the choice ot two differently versioned ones it will not prefer either over the other. I see. So for a really smooth transition from jessie and up, including partial upgrades, one would need an update with nettle-2.7.x with versioned symbols, and all packages linking explicitly with nettle rebuilt against that version (about 30 packages, if apt-cache rdepends libnettle4 is a good way to list them). And try to ensure all of these packages are upgraded *before* the packages with nettle-3.1 and current gnutls are installed. Maybe too complicated to be worth the effort? Are there any shortcuts, which improve the situation over the status quo? [...] Hello, What I originally had in mind was a a part of things listed above: 1. Update nettle-2.7.x to versioned symbols. 2. Let it propagate to sid (unstable) from testing. 3. Trigger rebuild of all rdepends, they will quickly propagate to testing, too. At this point both sid and testing (stretch) would be ready for a painless upgrade to nettle3, with no breakage in any system upgraded to this point. (And for sid/testing users imho one can expect systems being kept reasonably up to date.) 1. Upload nettle3. *Optionally* the nettle3 library packages could temporarily have a Breaks: on the list of binaries that were built against unversioned nettle-2.7.x, enforcing an upgrade to the rebuilt versions. 2. Trigger rebuild of all rdepends. 3. Wait for propagation to testing. Some months later the Breaks: can be dropped. --- This would not improve the jessie-stretch upgrade in two years. However I do not think that is that big of an issue. I guess almost all crash-candidates (direct link against a nettle library, and indirect link via another library) will involve gnutls as the library bringing in the second indirect link to nettle. jessie--stretch will include a gnutls soname change (3.4.x), which afaict solves the issue as a side-effect: Package release Depends wgetjessie libgnutls-deb0-28-libnettle4 / libnettle4 wgetstretch libgnutls30-libnettle6 / libnettle6 So there is no mixup of different nettle versions in the wget linkage possible. The effort involved would not be two bad, imho. However I am not totally sure it is worth it. Since nettle2 and nettle3 will use the same source package upgrading stretch to nettle3 will need to happen by a) rebuild everything in sid against nettle3, b) Only when all rdeps are ready to propagate at the same time to stretch (old enough, no new rc-bugs), all of them go into stretch at the same time. cu Andreas -- `What a good friend you are to him, Dr. Maturin. His other friends are so grateful to you.' `I sew his ears on from time to time, sure' -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#784587: [Pkg-utopia-maintainers] Bug#784587: Bug#784587: network-manager: does not set up resolv.conf
On Thu, 2015-05-07 at 19:08 +0200, Michael Biebl wrote: Hi Dan! Am 07.05.2015 um 18:09 schrieb Dan Williams: On Thu, 2015-05-07 at 13:15 +0900, Norbert Preining wrote: On Thu, 07 May 2015, Michael Biebl wrote: The attached patch should fix the issue. Will poke upstream for a review and upload tomorrow. Thanks for the quick fix! Got found and fixed yesterday in nm-1-0... Hm, I don't do any changes in the nm-1-0 related to that. Where those fixes not pushed? Yeah, that was it. Pushed now. In git master there is no longer fallback if resolvconf fails for some reason; but the resolv.conf manager is now a config option. So we'd expect distros to ship a sub-package that drops a config snippet into /etc/NetworkManager/conf.d/ enabling resolvconf which also requires the resolvconf package itself, so that when the config option is set, resolvconf is always installed. We may need some tweaking of the default handling here, but the idea is that if the user specifically chose resolvconf and it fails, that should be a hard failure and NM shouldn't be touching resolv.conf since the user told NM not to... I kind of liked the if-resolvconf-found-use-it behaviour. The new behaviour will be a bit icky if I go the subpackage route due to how conffiles are handled. conffiles (config files in /etc/) are not automatically removed by dpkg if the package is removed (they are only removed on purge). So if the user uninstalles (but doesn't purge) the sub-package, the conf.d snippet will stay around and he'll get resolv.conf failures because it's no longer guaranteed the resolvconf package is installed. Hmm, ok. I guess we'll have to allow fallback to writing resolvconf if the executable doesn't exist. dan -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#784587: [Pkg-utopia-maintainers] Bug#784587: Bug#784587: network-manager: does not set up resolv.conf
Am 07.05.2015 um 19:30 schrieb Dan Williams: On Thu, 2015-05-07 at 19:08 +0200, Michael Biebl wrote: Am 07.05.2015 um 18:09 schrieb Dan Williams: In git master there is no longer fallback if resolvconf fails for some reason; but the resolv.conf manager is now a config option. So we'd expect distros to ship a sub-package that drops a config snippet into /etc/NetworkManager/conf.d/ enabling resolvconf which also requires the resolvconf package itself, so that when the config option is set, resolvconf is always installed. We may need some tweaking of the default handling here, but the idea is that if the user specifically chose resolvconf and it fails, that should be a hard failure and NM shouldn't be touching resolv.conf since the user told NM not to... I kind of liked the if-resolvconf-found-use-it behaviour. The new behaviour will be a bit icky if I go the subpackage route due to how conffiles are handled. conffiles (config files in /etc/) are not automatically removed by dpkg if the package is removed (they are only removed on purge). So if the user uninstalles (but doesn't purge) the sub-package, the conf.d snippet will stay around and he'll get resolv.conf failures because it's no longer guaranteed the resolvconf package is installed. Hmm, ok. I guess we'll have to allow fallback to writing resolvconf if the executable doesn't exist. That would be nice, thanks! I think, it should only skip any fallbacks if rc-manager=resolvconf is explicitly set *and* the resolvconf binary does exist. -- Why is it that all of the instruments seeking intelligent life in the universe are pointed away from Earth? signature.asc Description: OpenPGP digital signature
