Bug#770648: hiredis: FTBFS: Test failure
Alrighty, talking this over with Alessandro he made the case that we should keep tests that don't rely on *external *network connections. See e.g. https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=753944 which makes the case for a loopback interface in pbuilder. Tobi, to that effect I modified your patch to keep the tests that work fine with localhost thus pass in pbuilder. Also, I feel like the serious severity is overstating the issue given that 0.11.0-4 builds fine in buildd/sbuild. Alessandro pointed out the periodic rebuilds would have revealed this issue otherwise. If there are no objections I'd like to propose we adjust the severity of this bug to normal leave the fix for this particular bug until after the Jessie freeze. Otherwise, I can reach out to the release team to get the hiredis package unblocked work through getting a new package uploaded with the pbuilder fixes nocheck support. On Mon, Nov 24, 2014 at 4:32 AM, Tobias Frost t...@frost.de wrote: On Mon, 24 Nov 2014 00:45:04 -0800 Tom Lee deb...@tomlee.co wrote: Alrighty, patch applied pbuilder's clean. Now just waiting on Alessandro to review my changes push the package. On master here if you want to try things out in the interim: git:// anonscm.debian.org/collab-maint/hiredis.git Daniel, I also added support for DEB_BUILD_OPTS=nocheck since it caused you additional grief. Tobi, I haven't bothered addressing the pid file etc. in /tmp just yet, but I'll take a look at that sometime soon. Please remember we are in freeze: Both those changes are not covered by the freeze policy as they are not targeting RC bugs. As the DEB_BUILD_OPTIONS=nocheck is already committed, I suggest you ask on #debian-release if that they could accept this. The /tmp thing is unimportant now, and can be fixed for Stretch, (if you want to fix it) -- tobi -- *Tom Lee */ http://tomlee.co / @tglee http://twitter.com/tglee
Bug#771452: Copied bucket
I suspect this is because you copied the objects into a new bucket, but did not include the associated metadata. Which tool did you use to do the copy, and how did you call it? I used the AWS command line tools: aws s3 sync s3://src-bucket s3://dest-bucket It did fail part way through the transfer, so I restarted it with the same command. When you use the S3 Management Console (https://console.aws.amazon.com/s3/home) to look at the s3ql_metadata object in the original bucket and the copy, does it have the same metadata? While the s3ql_metadata file is there, in the new bucket it is missing all of the keys except the Content-Type. Not sure whether this means the fsck without cached data trashed it, or if amazon's sync was trashing the transfered data because I used it incorrectly or it is broken somehow. Shannon C. Dealy | DeaTech Research Inc. de...@deatech.com |- Custom Software Development - USA Phone: +1 800-467-5820 |- Natural Building Instruction - numbers : +1 541-929-4089 |www.deatech.com -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#767564: libblitz-doc: fails to upgrade from 'testing' - trying to overwrite /usr/share/info/blitz.info.gz
Package: libblitz-doc Version: 1:0.10-3.1 Followup-For: Bug #767564 Dear Maintainer, the version number used in break+replaces is wrong, it is missing the epoch. So I got today: Unpacking libblitz-doc (1:0.10-3.1) over (1:0.10-1) ... dpkg: error processing archive /var/cache/apt/archives/libblitz-doc_1%3a0.10-3.1_all.deb (--unpack): trying to overwrite '/usr/share/info/blitz.info.gz', which is also in package libblitz0ldbl 1:0.10-1 -- System Information: Debian Release: jessie/sid APT prefers testing APT policy: (500, 'testing'), (500, 'stable'), (50, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 armhf powerpc ppc64el arm64 s390x Kernel: Linux 3.16.0-4-amd64 (SMP w/8 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages libblitz-doc depends on: ii libjs-jquery 1.7.2+dfsg-3.2 libblitz-doc recommends no packages. libblitz-doc suggests no packages. -- no debconf information -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#771499: [weboob] boobank not usable because of SSLv3 errors
Package: weboob Version: 1.0-1 Severity: grave Hi, boobank is not anymore usable on my PC : adrien ~/ $ boobank ls 2014-11-30 10:08:14,148:ERROR:weboob:1.0:ouiboube.py:450:load_backends Unable to load module cragr: 'module' object has no attribute 'PROTOCOL_SSLv3' 2014-11-30 10:08:14,150:ERROR:weboob:1.0:ouiboube.py:450:load_backends Unable to load module banquepopulaire: 'module' object has no attribute 'PROTOCOL_SSLv3' 2014-11-30 10:08:14,153:ERROR:weboob:1.0:ouiboube.py:450:load_backends Unable to load module bnporc: 'module' object has no attribute 'PROTOCOL_SSLv3' 2014-11-30 10:08:14,155:ERROR:weboob:1.0:ouiboube.py:450:load_backends Unable to load module caissedepargne: 'module' object has no attribute 'PROTOCOL_SSLv3' Warning: there is currently no configured backend for boobank If you need more information, please let me know. Regards, Adrien --- System information. --- Architecture: amd64 Kernel: Linux 3.16.0-4-amd64 Debian Release: jessie/sid 500 unstableftp.fr.debian.org 500 testing-updates ftp.fr.debian.org 500 testing security.debian.org 500 testing ftp.fr.debian.org 1 experimentalftp.fr.debian.org --- Package information. --- Depends (Version) | Installed =-+-=== python (= 2.7) | 2.7.8-2 python ( 2.8) | 2.7.8-2 python-weboob (= 0.i-3) | 1.0-1 python-html2text | 2014.9.25-1 python-prettytable| 0.7.2-3 Recommends(Version) | Installed ===-+-=== python-termcolor| 1.1.0-1 Package's Suggests field is empty. signature.asc Description: This is a digitally signed message part.
Bug#771500: darcsweb: postinst uses /usr/share/doc content (Policy 12.3): /usr/share/doc/darcsweb/examples/darcsweb.conf
Package: darcsweb Version: 1.1-3.1 Severity: serious User: debian...@lists.debian.org Usertags: piuparts Hi, a test with piuparts revealed that your package uses files from /usr/share/doc in its maintainer scripts which is a violation of Policy 12.3: Packages must not require the existence of any files in /usr/share/doc/ in order to function. https://www.debian.org/doc/debian-policy/ch-docs.html#s12.3 These files must be moved to /usr/share/$PACKAGE and may be symlinked from /usr/share/doc/$PACKAGE. This piuparts test prevents the installation of (most) files into /usr/share/doc with 'dpkg --path-exclude=...'. From the attached log (scroll to the bottom...): Selecting previously unselected package darcsweb. (Reading database ... 8445 files and directories currently installed.) Preparing to unpack .../darcsweb_1.1-3.1_all.deb ... Unpacking darcsweb (1.1-3.1) ... Setting up darcsweb (1.1-3.1) ... install: cannot stat '/usr/share/doc/darcsweb/examples/darcsweb.conf': No such file or directory dpkg: error processing package darcsweb (--configure): subprocess installed post-installation script returned error exit status 1 Errors were encountered while processing: darcsweb Cheers, Andreas darcsweb_1.1-3.1.log.gz Description: application/gzip
Bug#771501: pygopherd: postinst uses /usr/share/doc content (Policy 12.3): /usr/share/doc/pygopherd/examples/gophermap
Package: pygopherd Version: 2.0.18.3+nmu3 Severity: serious User: debian...@lists.debian.org Usertags: piuparts Hi, a test with piuparts revealed that your package uses files from /usr/share/doc in its maintainer scripts which is a violation of Policy 12.3: Packages must not require the existence of any files in /usr/share/doc/ in order to function. https://www.debian.org/doc/debian-policy/ch-docs.html#s12.3 These files must be moved to /usr/share/$PACKAGE and may be symlinked from /usr/share/doc/$PACKAGE. This piuparts test prevents the installation of (most) files into /usr/share/doc with 'dpkg --path-exclude=...'. From the attached log (scroll to the bottom...): Selecting previously unselected package pygopherd. (Reading database ... 8452 files and directories currently installed.) Preparing to unpack .../pygopherd_2.0.18.3+nmu3_all.deb ... Unpacking pygopherd (2.0.18.3+nmu3) ... Setting up pygopherd (2.0.18.3+nmu3) ... Adding system user `gopher' (UID 150) ... Adding new group `gopher' (GID 151) ... Adding new user `gopher' (UID 150) with group `gopher' ... Creating home directory `/var/gopher' ... cp: cannot stat '/usr/share/doc/pygopherd/examples/gophermap': No such file or directory dpkg: error processing package pygopherd (--configure): subprocess installed post-installation script returned error exit status 1 Errors were encountered while processing: pygopherd Cheers, Andreas pygopherd_2.0.18.3+nmu3.log.gz Description: application/gzip
Processed: Re: Bug#771471: scribus: Hyphenation in Scribus still doesn't work
Processing control commands: severity -1 important Bug #771471 [scribus] scribus: Hyphenation in Scribus still doesn't work Severity set to 'important' from 'grave' -- 771471: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=771471 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#771471: scribus: Hyphenation in Scribus still doesn't work
Control: severity -1 important On Nov 29, 2014 11:33 PM, Ondra Kudlík deb...@orthank.net wrote: Package: scribus Version: 1.4.4+dfsg1-2+b1 Severity: grave Justification: renders package unusable Accroding to me severity is grave as Scribus is now unusable for multiple languages (we know about Spanish and Czech but probably much more). I know that only hyphenation is not working but Scribus is desktop publishing software and without hyphenation it simply can't do its job. The hyphenator could be an important part of scribus, but no so important.
Processed: apt-listchanges users on wheezy will be thankful
Processing commands for cont...@bugs.debian.org:
tags 766601 + sid jessie
Bug #766601 {Done: Matthias Klose d...@ubuntu.com} [openjdk-7-jre-headless]
openjdk-7-jre-headless: still depending on libjpeg8?
Added tag(s) sid and jessie.
End of message, stopping processing here.
Please contact me if you need assistance.
--
766601: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=766601
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: found 771287 in 215-6
Processing commands for cont...@bugs.debian.org: found 771287 215-6 Bug #771287 [systemd] systemd: Multiple DMs can be started at the same time or none under systemd Marked as found in versions systemd/215-6. thanks Stopping processing here. Please contact me if you need assistance. -- 771287: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=771287 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: found 771287 in 215-1
Processing commands for cont...@bugs.debian.org: found 771287 215-1 Bug #771287 [systemd] systemd: Multiple DMs can be started at the same time or none under systemd Marked as found in versions systemd/215-1. thanks Stopping processing here. Please contact me if you need assistance. -- 771287: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=771287 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#771503: Remove package web2ldap
Processing commands for cont...@bugs.debian.org: severity #771503 serious Bug #771503 [web2ldap] Remove package web2ldap Severity set to 'serious' from 'normal' thanks Stopping processing here. Please contact me if you need assistance. -- 771503: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=771503 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed: severity of 771505 is serious
Processing commands for cont...@bugs.debian.org: severity 771505 serious Bug #771505 [python-weblib] Remove package python-weblib Severity set to 'serious' from 'normal' thanks Stopping processing here. Please contact me if you need assistance. -- 771505: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=771505 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#768998: Bug#767010: kadu-dev: KaduTargets.cmake hardcodes amd64 path
kadu-mime-tex should be rebuild by bin-nmu with kadu = 1.2-2 it fix
that bug. For example now is build fine on armhf:
dpkg-gencontrol: warning: File::FcntlLock not available; using flock
which is not NFS-safe
dpkg-gencontrol: warning: package kadu-mime-tex: unused substitution
variable ${misc:Pre-Depends}
dh_md5sums
dh_builddeb
dpkg-deb: building package `kadu-mime-tex' in
`../kadu-mime-tex_1.0-2_armhf.deb'.
dpkg-genchanges ../kadu-mime-tex_1.0-2_armhf.changes
dpkg-genchanges: not including original source code in upload
dpkg-source --after-build kadu-mime-tex-1.0
dpkg-buildpackage: binary and diff upload (original source NOT included)
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed: reopening 605303, severity of 605303 is grave
Processing commands for cont...@bugs.debian.org:
reopen 605303
Bug #605303 {Done: Kartik Mistry kar...@debian.org} [gwibber] [gwibber] does
not start
'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 gwibber/3.5.2-1.
severity 605303 grave
Bug #605303 [gwibber] [gwibber] does not start
Severity set to 'grave' from 'important'
thanks
Stopping processing here.
Please contact me if you need assistance.
--
605303: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=605303
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#605303: [gwibber] does not start
Package: gwibber Version: 3.0.0.1-2.2 Followup-For: Bug #605303 -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 The bug may have been fixed in experimental, but it is an RC bug in jessie/sid. Please backport the fix, as the version from experimental will not enter jessie. - -- System Information: Debian Release: jessie/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.16.0-4-amd64 (SMP w/2 CPU cores) Locale: LANG=C, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages gwibber depends on: ii gnome-keyring 3.14.0-1+b1 ii gwibber-service 3.0.0.1-2.2 ii libjs-jquery 2.1.1-1 ii librsvg2-22.40.5-1 ii librsvg2-common 2.40.5-1 ii python2.7.8-2 ii python-dbus 1.2.0-2+b3 ii python-egenix-mxdatetime 3.2.8-1 ii python-gconf 2.28.1+dfsg-1.1 ii python-gtk2 2.24.0-4 ii python-gtkspell 2.25.3-13 ii python-imaging2.6.1-1 ii python-mako 1.0.0+dfsg-0.1 ii python-oauth 1.0.1-4 ii python-simplejson 3.6.5-1 ii python-support1.0.15 ii python-webkit 1.1.8-3 ii python-wnck 2.32.0+dfsg-3 ii python-xdg0.25-4 gwibber recommends no packages. Versions of packages gwibber suggests: pn gwibber-service-buzznone pn gwibber-service-diggnone pn gwibber-service-flickr none pn gwibber-service-foursquare none pn gwibber-service-friendfeed none pn gwibber-service-pingfm none pn gwibber-service-qaiku none pn gwibber-service-statusnet none pn gwibber-themes none - -- no debconf information -BEGIN PGP SIGNATURE- Version: GnuPG v1 iQIcBAEBAgAGBQJUev4FAAoJELeaPBagxPKWyasP/2G5qOdNw9UDFY2OGiRjM+KN fW1d4gw1lZgEmMPycqxIBAjCr1yGVaWK4PRkekgp9wr2Ft/XbQs1gvHuA7pATQwF nB9csQeYiS7C4WC/lcbSeVaE4Exn0JWUfUqW1y6GVZX3hqNfiqMWokP+IXRydxeN sc8BcYguwm72O2qsn9GMpRjMR0ube1T3sM5Ny0qITyZw2RV1BWe5kB9tXsc2SJZ3 d67oNL5VRdAAMUc765TpKN3bLOAy9Q2AIYnj7GhYrMRdpl9kKJ200VTJlgPCrdsD cwOyvirL8SIFe6bJAIq7E5FH5Y68yW7CICKNSGBHlYK8dUhNd5EwiTn6D7WqK+/w sWcOWEfs8PuUueKII2vURgKxfjo11H45WLh7HY4VXfF62Ta52YTsLCk+DhTINXLg 1I793USGip0xtOTkQHUlg6EEhsFjLilEw6Lc3UWnMNMxdmTN+0jcJLts8e13N1S+ 4z0cMGTJomrlRRdsTQJ708qUZonJ+/PrFOVB0yB4nvvvQRrrETLu98iVmUPrQrBO 4R1eTHNJoaEIunFfUwa3TP4D0VsuW6qTA0pcaPNLf8ULpOLxnRSv0Q3eWfRGDjKX mHSj7+yPG512dG9pzWL92AvE1YSfJRYUrgd68gwfyz4aikeVWIF+irl/QJVKbN1s d7FJboxC5Xx3wPMuinSV =2h/u -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#771503: Remove package web2ldap
Marc, I hope you understand that this is not meant as personal offense. It's just facing the fact that it's too hard to keep up for the maintainer in the current situation. Ok? Ciao, Michael. smime.p7s Description: S/MIME Cryptographic Signature
Bug#771515: monodevelop-nunit: Plugin is not installed properly and does not work
Package: monodevelop-nunit Version: 4.0.12+dfsg-5 Severity: grave Justification: renders package unusable Dear Maintainer, the monodevelop-nunit package as it is in Jessie currently is not usable: After installing it, the plugin does not apepar in monodevelop. Manually runnng mdtool shows: $ mdtool setup reg-build MonoDevelop Add-in Setup Utility WARNING: [MonoDevelop.NUnit,4.0.12] Could not load some add-in assemblies: Could not find file /usr/lib/monodevelop/AddIns/NUnit/nunit.core.dll ERROR: There was an error while scanning assembly: /usr/lib/monodevelop/AddIns/NUnit/nunit.core.interfaces.dll (Could not find file /usr/lib/monodevelop/AddIns/NUnit/nunit.core.interfaces.dll) ERROR: There was an error while scanning assembly: /usr/lib/monodevelop/AddIns/NUnit/nunit.framework.dll (Could not find file /usr/lib/monodevelop/AddIns/NUnit/nunit.framework.dll) ERROR: There was an error while scanning assembly: /usr/lib/monodevelop/AddIns/NUnit/nunit.mocks.dll (Could not find file /usr/lib/monodevelop/AddIns/NUnit/nunit.mocks.dll) ERROR: There was an error while scanning assembly: /usr/lib/monodevelop/AddIns/NUnit/nunit.util.dll (Could not find file /usr/lib/monodevelop/AddIns/NUnit/nunit.util.dll) (and then the tool hangs, it does not terminate) Checking the installed files shows the reason: The following symlinks are dead: lrwxrwxrwx1 root root 42 Sep 22 11:21 /usr/lib/monodevelop/AddIns/NUnit/nunit.core.dll - ../../../cli/nunit.core-2.6/nunit.core.dll lrwxrwxrwx1 root root 64 Sep 22 11:21 /usr/lib/monodevelop/AddIns/NUnit/nunit.core.interfaces.dll - ../../../cli/nunit.core.interfaces-2.6/nunit.core.interfaces.dll lrwxrwxrwx1 root root 52 Sep 22 11:21 /usr/lib/monodevelop/AddIns/NUnit/nunit.framework.dll - ../../../cli/nunit.framework-2.6/nunit.framework.dll lrwxrwxrwx1 root root 44 Sep 22 11:21 /usr/lib/monodevelop/AddIns/NUnit/nunit.mocks.dll - ../../../cli/nunit.mocks-2.6/nunit.mocks.dll lrwxrwxrwx1 root root 42 Sep 22 11:21 /usr/lib/monodevelop/AddIns/NUnit/nunit.util.dll - ../../../cli/nunit.util-2.6/nunit.util.dll Upgrading to the version in unstable fixes the problem, but that doesn't really help - as is, monodevelop-nunit is clearly unfit for a release with Jessie. Kind regards Ralf -- System Information: Debian Release: jessie/sid APT prefers testing APT policy: (990, 'testing'), (100, 'unstable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.17.0+ (SMP w/4 CPU cores) Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages monodevelop-nunit depends on: ii libglib2.0-cil 2.12.10-5 ii libgtk2.0-cil 2.12.10-5 ii libmono-addins0.2-cil 1.0+git20130406.adcd75b-3 ii libmono-cairo4.0-cil 3.2.8+dfsg-8 ii libmono-corlib4.5-cil 3.2.8+dfsg-8 ii libmono-posix4.0-cil 3.2.8+dfsg-8 ii libmono-system-core4.0-cil 3.2.8+dfsg-8 ii libmono-system-xml-linq4.0-cil 3.2.8+dfsg-8 ii libmono-system-xml4.0-cil 3.2.8+dfsg-8 ii libmono-system4.0-cil 3.2.8+dfsg-8 ii libnunit-core-interfaces2.6.3-cil 2.6.3+dfsg-1 ii libnunit-core2.6.3-cil 2.6.3+dfsg-1 ii libnunit-framework2.6.3-cil2.6.3+dfsg-1 ii libnunit-util2.6.3-cil 2.6.3+dfsg-1 ii monodevelop4.0.12+dfsg-5 monodevelop-nunit recommends no packages. monodevelop-nunit suggests no packages. -- no debconf information -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#771499: [weboob] boobank not usable because of SSLv3 errors
Hi, That's because of this patch introduced few days ago on python: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=768611 I'm going to add a patch on the weboob package to disable use of PROTOCOL_SSLv3 constant. Romain -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#769554: [Pkg-haskell-maintainers] Bug#769554: libghc-authenticate-doc: package fails to upgrade properly from wheezy
Hi Lucas, I uploaded ghc-7.6.3-20, which hopefully fixes or mitigates this issue. Can you trigger a re-check of these somehow? Or should I just wait for the normal course of things and see if you file a new report? Am Freitag, den 14.11.2014, 13:37 +0100 schrieb Lucas Nussbaum: The same error affects other haskell packages, so I'm only filing it once, on that package, for now: $ grep -lr 'haddock: error while loading shared libraries: libffi.so.6:' . |grep log libghc-edison-core-doc_jessie_upgrade.log libghc-tagstream-conduit-doc_jessie_upgrade.log libghc-persistent-sqlite-doc_jessie_upgrade.log libghc-yesod-auth-doc_jessie_upgrade.log libghc-yesod-test-doc_jessie_upgrade.log libghc-persistent-template-doc_jessie_upgrade.log libghc-yesod-form-doc_jessie_upgrade.log libghc-csv-conduit-doc_jessie_upgrade.log libghc-wai-app-file-cgi-doc_jessie_upgrade.log libghc-html-conduit-doc_jessie_upgrade.log libghc-github-doc_jessie_upgrade.log libghc-yesod-default-doc_jessie_upgrade.log libghc-edison-api-doc_jessie_upgrade.log libghc-warp-doc_jessie_upgrade.log libghc-persistent-doc_jessie_upgrade.log libghc-free-doc_jessie_upgrade.log libghc-warp-tls-doc_jessie_upgrade.log libghc-data-lens-doc_jessie_upgrade.log libghc-yesod-persistent-doc_jessie_upgrade.log libghc-yesod-static-doc_jessie_upgrade.log libghc-keys-doc_jessie_upgrade.log libghc-xml-conduit-doc_jessie_upgrade.log libghc-yesod-doc_jessie_upgrade.log libghc-wai-extra-doc_jessie_upgrade.log libghc-http-conduit-doc_jessie_upgrade.log libghc-authenticate-doc_jessie_upgrade.log libghc-yesod-core-doc_jessie_upgrade.log Greetings, Joachim -- Joachim nomeata Breitner Debian Developer nome...@debian.org | ICQ# 74513189 | GPG-Keyid: F0FBF51F JID: nome...@joachim-breitner.de | http://people.debian.org/~nomeata signature.asc Description: This is a digitally signed message part
Bug#770648: hiredis: FTBFS: Test failure
Am Sonntag, den 30.11.2014, 00:21 -0800 schrieb Tom Lee: Alrighty, talking this over with Alessandro he made the case that we should keep tests that don't rely on external network connections. See e.g. https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=753944 which makes the case for a loopback interface in pbuilder. Tobi, to that effect I modified your patch to keep the tests that work fine with localhost thus pass in pbuilder. I'm ok with everything that fixes this bug :) Note that the above pbuilder bug is not closed yet; also buildds using AFAIK a sbuilder setup. https://wiki.debian.org/buildd explicitly says not to expect *any* network interface to be available. Of course, it could have been changed recently, but I'm not aware of this. A test-upload to expermental maybe could give some hint if your patch is enough? Also, I feel like the serious severity is overstating the issue given that 0.11.0-4 builds fine in buildd/sbuild. Alessandro pointed out the periodic rebuilds would have revealed this issue otherwise. If there are no objections I'd like to propose we adjust the severity of this bug to normal leave the fix for this particular bug until after the Jessie freeze. Here I can reprodcue the FTBFS locally with pbuilder 0.215+nmu3, so I disagree. It maybe has not been detected *yet*? Otherwise, I can reach out to the release team to get the hiredis package unblocked work through getting a new package uploaded with the pbuilder fixes nocheck support. -- tobi dpkg-checkbuilddeps: Unmet build dependencies: redis-server (= 2:2.4.2-2) W: Unmet build-dependency in source dpkg-buildpackage: source package hiredis dpkg-buildpackage: source version 0.11.0-4 dpkg-buildpackage: source distribution unstable dpkg-buildpackage: source changed by Tom Lee deb...@tomlee.co dpkg-source --before-build hiredis-0.11.0 dpkg-checkbuilddeps: Unmet build dependencies: redis-server (= 2:2.4.2-2) dpkg-buildpackage: warning: build dependencies/conflicts unsatisfied; aborting dpkg-buildpackage: warning: (Use -d flag to override.) dpkg-buildpackage: warning: this is currently a non-fatal warning with -S, but will probably become fatal in the future fakeroot debian/rules clean dh clean dh_testdir dh_auto_clean make[1]: Entering directory '/home/tobi/workspace/deb/tmp/hiredis-0.11.0' rm -rf libhiredis.so libhiredis.a hiredis-example hiredis-test hiredis-example* *.o *.gcda *.gcno *.gcov hiredis.pc make[1]: Leaving directory '/home/tobi/workspace/deb/tmp/hiredis-0.11.0' dh_clean dpkg-source -b hiredis-0.11.0 dpkg-source: info: using source format `3.0 (quilt)' dpkg-source: info: building hiredis using existing ./hiredis_0.11.0.orig.tar.gz dpkg-source: info: building hiredis in hiredis_0.11.0-4.debian.tar.xz dpkg-source: info: building hiredis in hiredis_0.11.0-4.dsc dpkg-genchanges -S ../hiredis_0.11.0-4_source.changes dpkg-genchanges: not including original source code in upload dpkg-source --after-build hiredis-0.11.0 dpkg-buildpackage: binary and diff upload (original source NOT included) I: using fakeroot in build. I: pbuilder: network access will be disabled during build I: Current time: Sun Nov 30 15:02:06 CET 2014 I: pbuilder-time-stamp: 1417356126 I: Building the build Environment I: extracting base tarball [/var/cache/pbuilder/sid-amd64-base.tgz] I: creating local configuration I: copying local configuration I: mounting /proc filesystem I: mounting /run/shm filesystem I: mounting /dev/pts filesystem I: Mounting /home/tobi/pbuilder_repo/deps I: Mounting /var/cache/pbuilder/ccache I: policy-rc.d already exists I: Obtaining the cached apt archive contents I: Setting up ccache I: Installing the build-deps I: user script /var/cache/pbuilder/build//21192/tmp/hooks/D05deps starting # debs in /home/tobi/pbuild_repp/deps # Ign file: ./ InRelease Ign file: ./ Release.gpg Ign file: ./ Release Ign file: ./ Translation-en Get:1 http://thecus:3142 sid InRelease [242 kB] Get:2 http://thecus:3142 sid/main amd64 Packages/DiffIndex [7876 B] Get:3 http://thecus:3142 sid/contrib amd64 Packages/DiffIndex [7819 B] Get:4 http://thecus:3142 sid/non-free amd64 Packages/DiffIndex [7819 B] Get:5 http://thecus:3142 sid/contrib Translation-en/DiffIndex [7819 B] Get:6 http://thecus:3142 sid/main Translation-en/DiffIndex [7876 B] Get:7 http://thecus:3142 sid/non-free Translation-en/DiffIndex [7819 B] Get:8 http://thecus:3142 sid/main amd64 2014-11-27-0842.42.pdiff [1347 B] Get:9 http://thecus:3142 sid/main amd64 2014-11-27-1440.37.pdiff [2523 B] Get:10 http://thecus:3142 sid/main amd64 2014-11-27-2041.46.pdiff [14.0 kB] Get:11 http://thecus:3142 sid/main amd64 2014-11-28-0244.44.pdiff [10.7 kB] Get:12 http://thecus:3142 sid/main amd64 2014-11-28-0842.12.pdiff [7300 B] Get:13 http://thecus:3142 sid/main amd64 2014-11-28-1443.38.pdiff [4627 B] Get:14 http://thecus:3142 sid/main amd64 2014-11-28-2041.49.pdiff [8704 B] Get:15 http://thecus:3142 sid/main amd64 2014-11-29-0242.06.pdiff [31.1 kB]
Bug#769554: [Pkg-haskell-maintainers] Bug#769554: libghc-authenticate-doc: package fails to upgrade properly from wheezy
On 30/11/14 at 14:17 +0100, Joachim Breitner wrote: Hi Lucas, I uploaded ghc-7.6.3-20, which hopefully fixes or mitigates this issue. Can you trigger a re-check of these somehow? Or should I just wait for the normal course of things and see if you file a new report? Hi Joachim, It's quite painful to do partial rebuilds ... I will probably try to do another rebuild soon, so it's easier for me to just wait for it. Lucas signature.asc Description: Digital signature
Processed: maven: FTBFS: maven-install-plugin or one of its dependencies could not be resolved
Processing control commands: tags -1 patch Bug #770608 [src:maven] maven: FTBFS: maven-install-plugin or one of its dependencies could not be resolved Added tag(s) patch. -- 770608: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=770608 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#770608: maven: FTBFS: maven-install-plugin or one of its dependencies could not be resolved
Control: tags -1 patch Hi Daniel, This RC bug is threatening the removal of quite a number of Java packages that depend on maven. I've reproduced the issue you reported in an up-to-date sid chroot. During the maven-compile phase the build attempts to download maven-install-plugin-2.3.pom which fails due to no network in the chroot. The maven-install-plugin package in Debian was updated to 2.4-1, so the build dependency doesn't satisfy the pom.xml version anymore. I've updated the plugin versions to match the versions in Debian, see the attached patch that fixes the build for me. Debian Java Maintainers, Since we're post-freeze, I don't think the changes for -2 currently in git will be acceptable to the Release Team (because of the Standards-Version bump), so I've applied my patch to -1 as currently in the archive. Will you upload a fixed maven package and request an unblock, or shall I NMU it and contact the Release Team? Kind Regards, Bas -- GPG Key ID: 4096R/E88D4AF1 Fingerprint: 8182 DE41 7056 408D 6146 50D1 6750 F10A E88D 4AF1 From 10871803a3fe63dbc0bd64cdd27033d32f2a5268 Mon Sep 17 00:00:00 2001 From: Bas Couwenberg sebas...@xs4all.nl Date: Sun, 30 Nov 2014 14:50:28 +0100 Subject: Bump plugin versions to match version in Debian. --- debian/changelog| 8 debian/maven.buildRules | 4 +- debian/maven.rules | 4 +- debian/patches/plugins_version.diff | 80 ++--- 4 files changed, 52 insertions(+), 44 deletions(-) diff --git a/debian/changelog b/debian/changelog index 07785b8..86c08e4 100644 --- a/debian/changelog +++ b/debian/changelog @@ -1,3 +1,11 @@ +maven (3.0.5-1.1) UNRELEASED; urgency=medium + + * Non-maintainer upload. + * Bump plugin versions to match version in Debian. +(closes: #770608) + + -- Bas Couwenberg sebas...@xs4all.nl Sun, 30 Nov 2014 15:31:53 +0100 + maven (3.0.5-1) unstable; urgency=low * Team upload. diff --git a/debian/maven.buildRules b/debian/maven.buildRules index 0f42dae..c57477f 100644 --- a/debian/maven.buildRules +++ b/debian/maven.buildRules @@ -17,8 +17,8 @@ org.codehaus.plexus plexus-component-annotations * s/.*/1.5.5/ * * org.apache.maven.plugins maven-clean-plugin * s/.*/2.3/ * * org.apache.maven.plugins maven-resources-plugin * s/.*/2.3/ * * org.apache.maven.plugins maven-surefire-plugin * s/.*/2.10/ * * -org.apache.maven.plugins maven-jar-plugin * s/.*/2.2/ * * -org.apache.maven.plugins maven-compiler-plugin * s/.*/2.0.2/ * * +org.apache.maven.plugins maven-jar-plugin * s/.*/2.4/ * * +org.apache.maven.plugins maven-compiler-plugin * s/.*/2.5.1/ * * org.apache.maven apache-maven pom s/.*/3.0.5/ * * org.apache.maven maven-aether-provider jar s/.*/3.0.5/ * * diff --git a/debian/maven.rules b/debian/maven.rules index c4b1e67..24eac4c 100644 --- a/debian/maven.rules +++ b/debian/maven.rules @@ -17,8 +17,8 @@ org.codehaus.plexus plexus-component-annotations * s/.*/1.5.5/ * * org.apache.maven.plugins maven-clean-plugin * s/.*/2.3/ * * org.apache.maven.plugins maven-resources-plugin * s/.*/2.3/ * * org.apache.maven.plugins maven-surefire-plugin * s/.*/2.10/ * * -org.apache.maven.plugins maven-jar-plugin * s/.*/2.2/ * * -org.apache.maven.plugins maven-compiler-plugin * s/.*/2.0.2/ * * +org.apache.maven.plugins maven-jar-plugin * s/.*/2.4/ * * +org.apache.maven.plugins maven-compiler-plugin * s/.*/2.5.1/ * * org.apache.maven apache-maven pom s/.*/3.x/ * * org.apache.maven maven-aether-provider jar s/.*/3.x/ * * diff --git a/debian/patches/plugins_version.diff b/debian/patches/plugins_version.diff index e7cf9e0..2a356f1 100644 --- a/debian/patches/plugins_version.diff +++ b/debian/patches/plugins_version.diff @@ -6,16 +6,16 @@ Last-Update: 2012-01-21 Forwarded: not-needed --- a/maven-core/src/main/resources/META-INF/plexus/artifact-handlers.xml +++ b/maven-core/src/main/resources/META-INF/plexus/artifact-handlers.xml -@@ -55,7 +55,7 @@ +@@ -55,7 +55,7 @@ problem. !-- START SNIPPET: pom-lifecycle -- phases install -org.apache.maven.plugins:maven-install-plugin:2.3.1:install -+org.apache.maven.plugins:maven-install-plugin:2.3:install ++org.apache.maven.plugins:maven-install-plugin:2.4:install /install deploy org.apache.maven.plugins:maven-deploy-plugin:2.7:deploy -@@ -91,25 +91,25 @@ +@@ -91,25 +91,25 @@ problem. !-- START SNIPPET: jar-lifecycle -- phases process-resources @@ -24,7 +24,7 @@ Forwarded: not-needed /process-resources compile -org.apache.maven.plugins:maven-compiler-plugin:2.3.2:compile -+org.apache.maven.plugins:maven-compiler-plugin:2.0.2:compile ++org.apache.maven.plugins:maven-compiler-plugin:2.5.1:compile /compile
Bug#768998: Bug#767010: kadu-dev: KaduTargets.cmake hardcodes amd64 path
On Sun, 30 Nov 2014 11:41:11 +0100, Mateusz Łukasik wrote:
kadu-mime-tex should be rebuild by bin-nmu with kadu = 1.2-2 it fix that
bug. For example now is build fine on armhf:
dpkg-gencontrol: warning: File::FcntlLock not available; using flock which
is not NFS-safe
dpkg-gencontrol: warning: package kadu-mime-tex: unused substitution
variable ${misc:Pre-Depends}
dh_md5sums
dh_builddeb
dpkg-deb: building package `kadu-mime-tex' in
`../kadu-mime-tex_1.0-2_armhf.deb'.
dpkg-genchanges ../kadu-mime-tex_1.0-2_armhf.changes
dpkg-genchanges: not including original source code in upload
dpkg-source --after-build kadu-mime-tex-1.0
dpkg-buildpackage: binary and diff upload (original source NOT included)
So, let's request a giveback on all arches except amd64 (where the
package built):
gb kadu-mime-tex_1.0-2 . ALL -amd64
Cheers,
gregor
--
.''`. Homepage: http://info.comodo.priv.at/ - OpenPGP key 0xBB3A68018649AA06
: :' : Debian GNU/Linux user, admin, and developer - http://www.debian.org/
`. `' Member of VIBE!AT SPI, fellow of the Free Software Foundation Europe
`- NP: Tanita Tikaram: Twist In My Sobriety
signature.asc
Description: Digital Signature
Bug#771544: ruby-uuid trying to open /root/.ruby-uuid file and failing with permission denied error
package: ruby-uuid
version: 2.3.7-2
severity: grave
when trying to start diaspora following steps detailed at
https://wiki.debian.org/Diaspora it fails with following message
10:18:48 sidekiq.1 | 2014-11-30T15:18:48.368Z 8702 TID-2zdvo INFO:
Booting Sidekiq 3.2.6 with redis options {:namespace=nil}
10:18:48 sidekiq.1 | Permission denied @ rb_sysopen - /root/.ruby-uuid
10:18:48 sidekiq.1 | /usr/lib/ruby/vendor_ruby/uuid.rb:270:in `initialize'
10:18:48 sidekiq.1 | /usr/lib/ruby/vendor_ruby/uuid.rb:270:in `open'
10:18:48 sidekiq.1 | /usr/lib/ruby/vendor_ruby/uuid.rb:270:in `initialize'
10:18:48 sidekiq.1 | /usr/lib/ruby/vendor_ruby/uuid.rb:139:in `new'
10:18:48 sidekiq.1 | /usr/lib/ruby/vendor_ruby/uuid.rb:139:in `generator'
10:18:48 sidekiq.1 |
/usr/share/diaspora/config/initializers/sidekiq.rb:51:in `block in top
(required)'
10:18:48 sidekiq.1 | /usr/lib/ruby/vendor_ruby/sidekiq.rb:53:in
`configure_server'
signature.asc
Description: OpenPGP digital signature
Bug#771544: it happens when using sudo -u user
in /usr/lib/ruby/vendor_ruby/uuid.rb:189
@state_file = File.expand_path('.ruby-uuid', '~')
this become /root/.ruby-uuid when running sudo -u diaspora as root.
signature.asc
Description: OpenPGP digital signature
Processed: severity of 754692 is important
Processing commands for cont...@bugs.debian.org: severity 754692 important Bug #754692 [src:libqb] libqb: sometimes FTBFS: testsuite races Severity set to 'important' from 'serious' thanks Stopping processing here. Please contact me if you need assistance. -- 754692: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=754692 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: submited upstream bug
Processing commands for cont...@bugs.debian.org: forwarded 771544 https://github.com/assaf/uuid/issues/45 Bug #771544 [ruby-uuid] ruby-uuid trying to open /root/.ruby-uuid file and failing with permission denied error Set Bug forwarded-to-address to 'https://github.com/assaf/uuid/issues/45'. severity 771544 normal Bug #771544 [ruby-uuid] ruby-uuid trying to open /root/.ruby-uuid file and failing with permission denied error Severity set to 'normal' from 'grave' thanks Stopping processing here. Please contact me if you need assistance. -- 771544: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=771544 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#768741: phlipple: FTBFS in jessie: ld: engine.o: undefined reference to symbol 'cos@@GLIBC_2.2.5'
Hi Miriam, Miriam Ruiz mir...@debian.org writes: I'll upload newer versions this afternoon :) zaz has already been uploaded. Do you still plan to upload phlipple? I can do the upload if needed. Thanks, Vincent -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#770932: marked as done (ruby2.1: CVE-2014-8090)
Your message dated Sun, 30 Nov 2014 16:35:25 + with message-id e1xv7t3-0004ev...@franck.debian.org and subject line Bug#770932: fixed in ruby2.1 2.1.5-1 has caused the Debian Bug report #770932, regarding ruby2.1: CVE-2014-8090 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.) -- 770932: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=770932 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: ruby2.1 Severity: grave Tags: security Hi, please see https://www.ruby-lang.org/en/news/2014/11/13/rexml-dos-cve-2014-8090/ for details. Cheers, Moritz ---End Message--- ---BeginMessage--- Source: ruby2.1 Source-Version: 2.1.5-1 We believe that the bug you reported is fixed in the latest version of ruby2.1, 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 770...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Antonio Terceiro terce...@debian.org (supplier of updated ruby2.1 package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Sat, 29 Nov 2014 12:30:39 -0200 Source: ruby2.1 Binary: ruby2.1 libruby2.1 ruby2.1-dev ruby2.1-doc ruby2.1-tcltk Architecture: source all Version: 2.1.5-1 Distribution: unstable Urgency: medium Maintainer: Antonio Terceiro terce...@debian.org Changed-By: Antonio Terceiro terce...@debian.org Description: libruby2.1 - Libraries necessary to run Ruby 2.1 ruby2.1- Interpreter of object-oriented scripting language Ruby ruby2.1-dev - Header files for compiling extension modules for the Ruby 2.1 ruby2.1-doc - Documentation for Ruby 2.1 ruby2.1-tcltk - Ruby/Tk for Ruby 2.1 Closes: 769731 770932 Changes: ruby2.1 (2.1.5-1) unstable; urgency=medium . * New upstream release - Fixes CVE-2014-8090 Another Denial of Service XML Expansion (Closes: #770932) - Fixes build on SPARC (Closes: #769731) Checksums-Sha1: f9fd6ab53d5621b88669489f1f0861eae8b0208d 2406 ruby2.1_2.1.5-1.dsc 4c70a84f0e88f553235b3e0c2619c193251d4652 8026484 ruby2.1_2.1.5.orig.tar.xz 28899f94e1f1dc4aa47e9b3261a86ea762430d63 84196 ruby2.1_2.1.5-1.debian.tar.xz 02f939f5cf7d1e87e6a7e26dd6e2f76da1026179 3367516 ruby2.1-doc_2.1.5-1_all.deb Checksums-Sha256: fe8372daa73dc839fad1115344c1309dfb08c7eec54f859beee0b2dcb89a73c7 2406 ruby2.1_2.1.5-1.dsc 0f8d9b15b38ee8b9a59dd9504404789cd8941da2c3ea079535e24f95e0f7ddc1 8026484 ruby2.1_2.1.5.orig.tar.xz f295e218e7487abd642eab49652a630ac93810a8b53f233258d0b60ebfe14e24 84196 ruby2.1_2.1.5-1.debian.tar.xz 95e20cd3d2a6205590de2ebc920a7036851612faf3f682ac141f520a9e93ac93 3367516 ruby2.1-doc_2.1.5-1_all.deb Files: 102cad39a14eb3e03355cffec60c5c48 2406 ruby extra ruby2.1_2.1.5-1.dsc 1fe7f8fe73a3deba9363f391c1083e94 8026484 ruby extra ruby2.1_2.1.5.orig.tar.xz 80c2ddf893e9193263066b61f07de76b 84196 ruby extra ruby2.1_2.1.5-1.debian.tar.xz 1bf221581175f72e3f7cb407b1e13bd0 3367516 doc extra ruby2.1-doc_2.1.5-1_all.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1 iQIcBAEBCAAGBQJUezJqAAoJEPwNsbvNRgveeycQAIotq1aI+POaeztiVjWfYxaL uwlOaj7ZKfvVmriAKVt7/O5I0jEXiKCY4nth4PckhXlf7J69coA7z/XJeIDqUjVu apPipTgpRUXzAtgMUEeuXEfCjJ/H3DRKJNOlToZJ/y5jUgZGh5rP1bNzuMJYclxS aSaW4wCNrM3Vy+RZK2xBIcqsrpimyvHfecTgFBwy2FdReb7aAg238uXyvNTakwae Np1YS9u+n5lDCx7+uQ3QqvFncZpFhlJDiBg+CURj4Mhm7+45oGKg3TY6bodx1m0z 0CosJ64FSZfyw6bn3/IPoTJYj5QejolL4T/VthxFEUj/8KcoL2jCTK3o4ZyGYaHc vOGKNvDJvczNLqES2jIkG+rlbM6tG8xf55geSiZJpzBYvtTDQdy2T0/eaBXzEN/x 2kGqV4T0s/ULUimSvPntmiaLYnoTRhwxDvnXHPV0ph/1hK6NTFh/CcylHlbH0vvp HQ1em600W20vAqqkDgDUbKzEg9F8zBc4O7qN75WeOhnmQfQ2vqUXDb5+WgIeXEa9 GBnsx3vIpfWBUxZkc+AeVgZHXHmQ9kOTD1F/bwp3NOM4MLGOizGC6CbqYMNXAOuB yKZX3IQHttERyy9di1A4vtf63X9LcbYW8PxPmco5qEFR0sMZNdoCzY13MK+bq3ep RFgocP1xStoegd1QFZiz =P5ol -END PGP SIGNATUREEnd Message---
Bug#770648: hiredis: FTBFS: Test failure
On dom, nov 30, 2014 at 03:06:55 +0100, Tobias Frost wrote: Am Sonntag, den 30.11.2014, 00:21 -0800 schrieb Tom Lee: Alrighty, talking this over with Alessandro he made the case that we should keep tests that don't rely on external network connections. See e.g. https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=753944 which makes the case for a loopback interface in pbuilder. Tobi, to that effect I modified your patch to keep the tests that work fine with localhost thus pass in pbuilder. I'm ok with everything that fixes this bug :) Note that the above pbuilder bug is not closed yet; pbuilder does create a loopback interface with USENETWORK=no, but, according to that bug report, it still has problems... which makes me wonder, what if this FTBFS is actually caused by a bug in pbuilder? also buildds using AFAIK a sbuilder setup. https://wiki.debian.org/buildd explicitly says not to expect *any* network interface to be available. The part about missing a loopback was actually removed from that page years ago [0]. Not to mention that disabling valuable and working (at least on the Debian buildds) tests over a matter of policy (and a confusing one at that) seems silly to me. All buildds provide at least a loopback interface or hiredis (and many other packages) would have never been able to build in the past. And pbuilder somehow screws this up. A test-upload to expermental maybe could give some hint if your patch is enough? I don't see how an upload would be useful in this case. hiredis is not failing to build on the buildds, and a new upload (even without patch) would only confirm that. Also, I feel like the serious severity is overstating the issue given that 0.11.0-4 builds fine in buildd/sbuild. Alessandro pointed out the periodic rebuilds would have revealed this issue otherwise. If there are no objections I'd like to propose we adjust the severity of this bug to normal leave the fix for this particular bug until after the Jessie freeze. Here I can reprodcue the FTBFS locally with pbuilder 0.215+nmu3, so I disagree. It maybe has not been detected *yet*? What does this yet even mean? Except inside pbuilder, hiredis builds fine [1]. The fact that it fails *only* inside pbuilder (and the fact that hiredis is not the only package in this situation) suggests that this is indeed a pbuilder bug. I really don't see how this is release critical in any way on the part of the hiredis package. Cheers [0] https://wiki.debian.org/buildd?action=diffrev1=11rev2=12 [1] https://buildd.debian.org/status/package.php?p=hiredissuite=unstable signature.asc Description: Digital signature
Processed: its because of tmpdir collision
Processing control commands: severity 771544 grave Bug #771544 [ruby-uuid] ruby-uuid trying to open /root/.ruby-uuid file and failing with permission denied error Severity set to 'grave' from 'normal' -- 771544: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=771544 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#770608: maven: FTBFS: maven-install-plugin or one of its dependencies could not be resolved
Thank you very much for the patch Sebastiaan, we are going to include it in the next upload. Emmanuel Bourg -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed: found 770932 in 2.1.4-1
Processing commands for cont...@bugs.debian.org:
found 770932 2.1.4-1
Bug #770932 {Done: Antonio Terceiro terce...@debian.org} [ruby2.1] ruby2.1:
CVE-2014-8090
Marked as found in versions ruby2.1/2.1.4-1.
thanks
Stopping processing here.
Please contact me if you need assistance.
--
770932: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=770932
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#771555: gnome-keyring Iceweasel plugin cannot be disabled
Package: gnome-keyring Version: 3.14.0-1+b1 Severity: grave Tags: upstream Justification: renders package unusable Dear Maintainer, After updating to GNOME 3.14, Iceweasel keeps asking to create a keyring named mozilla and won't take no for an answer. This behaviour is presumably caused by the GNOME keyring integration browser plugin. This plugin cannot be disabled; its status remains as GNOME Keyring integration will be disabled after you restart Iceweasel even after the entire system has been restarted! This renders Iceweasel unusable in conjunction with GNOME. -- System Information: Debian Release: 8.0 APT prefers unstable APT policy: (500, 'unstable') Architecture: amd64 (x86_64) Kernel: Linux 3.16.0-4-amd64 (SMP w/8 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages gnome-keyring depends on: ii dbus-x11 1.8.12-1 ii dconf-gsettings-backend [gsettings-backend] 0.22.0-1 ii gcr 3.14.0-2 ii libc62.19-13 ii libcap-ng0 0.7.4-2 ii libcap2-bin 1:2.24-6 ii libdbus-1-3 1.8.12-1 ii libgck-1-0 3.14.0-2 ii libgcr-base-3-1 3.14.0-2 ii libgcrypt20 1.6.2-4 ii libglib2.0-0 2.42.1-1 ii p11-kit 0.20.7-1 Versions of packages gnome-keyring recommends: ii libpam-gnome-keyring 3.14.0-1+b1 gnome-keyring 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: reassign 771555 to xul-ext-gnome-keyring
Processing commands for cont...@bugs.debian.org: reassign 771555 xul-ext-gnome-keyring Bug #771555 [gnome-keyring] gnome-keyring Iceweasel plugin cannot be disabled Bug reassigned from package 'gnome-keyring' to 'xul-ext-gnome-keyring'. No longer marked as found in versions gnome-keyring/3.14.0-1. Ignoring request to alter fixed versions of bug #771555 to the same values previously set thanks Stopping processing here. Please contact me if you need assistance. -- 771555: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=771555 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#769554: [Pkg-haskell-maintainers] Bug#769554: libghc-authenticate-doc: package fails to upgrade properly from wheezy
Hi, Am Sonntag, den 30.11.2014, 15:14 +0100 schrieb Lucas Nussbaum: It's quite painful to do partial rebuilds ... I will probably try to do another rebuild soon, so it's easier for me to just wait for it. perfect, thanks. Greetings, Joachim -- Joachim nomeata Breitner Debian Developer nome...@debian.org | ICQ# 74513189 | GPG-Keyid: F0FBF51F JID: nome...@joachim-breitner.de | http://people.debian.org/~nomeata signature.asc Description: This is a digitally signed message part
Bug#770648: hiredis: FTBFS: Test failure
On Sun, 30 Nov 2014 17:36:04 +0100, Alessandro Ghedini wrote: On dom, nov 30, 2014 at 03:06:55 +0100, Tobias Frost wrote: Am Sonntag, den 30.11.2014, 00:21 -0800 schrieb Tom Lee: Also, I feel like the serious severity is overstating the issue given that 0.11.0-4 builds fine in buildd/sbuild. Alessandro pointed out the periodic rebuilds would have revealed this issue otherwise. If there are no objections I'd like to propose we adjust the severity of this bug to normal leave the fix for this particular bug until after the Jessie freeze. Here I can reprodcue the FTBFS locally with pbuilder 0.215+nmu3, so I disagree. It maybe has not been detected *yet*? What does this yet even mean? Except inside pbuilder, hiredis builds fine [1]. The fact that it fails *only* inside pbuilder (and the fact that hiredis is not the only package in this situation) suggests that this is indeed a pbuilder bug. I really don't see how this is release critical in any way on the part of the hiredis package. While I tend to agree in general, here's an additional data point: I rebuilt 0.11.0-4 in my sid amd64 cowbuilder chroot, which has USENETWORK=yes (due to #753944) but firewalls off everything except localhost during build. And in this environment I see a test failure: make check make[2]: Entering directory '/tmp/buildd/hiredis-0.11.0' echo \ daemonize yes\n \ pidfile /tmp/hiredis-test-redis.pid\n \ port 56379\n \ bind 127.0.0.1\n \ unixsocket /tmp/hiredis-test-redis.sock \ | redis-server - ./hiredis-test -h 127.0.0.1 -p 56379 -s /tmp/hiredis-test-redis.sock || \ ( kill `cat /tmp/hiredis-test-redis.pid` false ) #01 Format command without interpolation: PASSED #02 Format command with %s string interpolation: PASSED #03 Format command with %s and an empty string: PASSED #04 Format command with an empty string in between proper interpolations: PASSED #05 Format command with %b string interpolation: PASSED #06 Format command with %b and an empty string: PASSED #07 Format command with literal %: PASSED #08 Format command with printf-delegation (int): PASSED #09 Format command with printf-delegation (char): PASSED #10 Format command with printf-delegation (short): PASSED #11 Format command with printf-delegation (long): PASSED #12 Format command with printf-delegation (long long): PASSED #13 Format command with printf-delegation (unsigned int): PASSED #14 Format command with printf-delegation (unsigned char): PASSED #15 Format command with printf-delegation (unsigned short): PASSED #16 Format command with printf-delegation (unsigned long): PASSED #17 Format command with printf-delegation (unsigned long long): PASSED #18 Format command with printf-delegation (float): PASSED #19 Format command with printf-delegation (double): PASSED #20 Format command with invalid printf format: PASSED #21 Format command by passing argc/argv without lengths: PASSED #22 Format command by passing argc/argv with lengths: PASSED #23 Error handling in reply parser: PASSED #24 Memory cleanup in reply parser: PASSED #25 Set error on nested multi bulks with depth 7: PASSED #26 Works with NULL functions for reply: PASSED #27 Works when a single newline (\r\n) covers two calls to feed: PASSED #28 Don't reset state after protocol error: PASSED #29 Don't do empty allocation for empty multi bulk: PASSED #30 Returns error when host cannot be resolved: FAILED #31 Returns error when the unix socket path doesn't accept connections: PASSED [..] which seems to be the same as what Daniel originally reported. Adding a printf statement to test.c shows: #30 Returns error when host cannot be resolved: FAILED ERROR: Temporary failure in name resolution test.c currently looks for Name or service not known or Can't resolve: idontexist.local but not for what I get here ... Not sure what the best way forward is; adding a test for Temporary failure in name resolution might be an option (and works unsurprisingly): #v+ --- a/test.c +++ b/test.c @@ -286,7 +286,8 @@ c = redisConnect((char*)idontexist.local, 6379); test_cond(c-err == REDIS_ERR_OTHER (strcmp(c-errstr,Name or service not known) == 0 || - strcmp(c-errstr,Can't resolve: idontexist.local) == 0)); + strcmp(c-errstr,Can't resolve: idontexist.local) == 0 || + strcmp(c-errstr,Temporary failure in name resolution) == 0)); redisFree(c); /*test(Returns error when the port is not open: ); #v- But maybe there are better ways to fix this. Cheers, gregor -- .''`. Homepage: http://info.comodo.priv.at/ - OpenPGP key 0xBB3A68018649AA06 : :' : Debian GNU/Linux user, admin, and developer - http://www.debian.org/ `. `' Member of VIBE!AT SPI, fellow of the Free Software Foundation Europe `- NP: Spider Murphy Gang: Rock'n Roll Rendevouz signature.asc Description: Digital Signature
Bug#771452: Copied bucket
On 11/30/2014 12:50 AM, Shannon Dealy wrote: I suspect this is because you copied the objects into a new bucket, but did not include the associated metadata. Which tool did you use to do the copy, and how did you call it? I used the AWS command line tools: aws s3 sync s3://src-bucket s3://dest-bucket It did fail part way through the transfer, so I restarted it with the same command. When you use the S3 Management Console (https://console.aws.amazon.com/s3/home) to look at the s3ql_metadata object in the original bucket and the copy, does it have the same metadata? While the s3ql_metadata file is there, in the new bucket it is missing all of the keys except the Content-Type. Not sure whether this means the fsck without cached data trashed it, or if amazon's sync was trashing the transfered data because I used it incorrectly or it is broken somehow. I think you have to blame the aws tool for this one. If you think fsck.s3ql is at fault, that's easy enough to check: just run the sync command again and see if the metadata is present before running fsck.s3ql. I don't know if that's a bug in aws, or if you're using it incorrectly, but gsutil is able to copy buckets including metadata (in case you want to try that). Best, -Nikolaus -- GPG encrypted emails preferred. Key id: 0xD113FCAC3C4E599F Fingerprint: ED31 791B 2C5C 1613 AF38 8B8A D113 FCAC 3C4E 599F »Time flies like an arrow, fruit flies like a Banana.« -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#770648: hiredis: FTBFS: Test failure
Talked this over with the release team on #debian-release, they agree it's a serious bug indicated that they'd prefer the fix to be something more along the lines of what Gregor is suggesting. I feel like the test should call out the fact it's skipped not passed, but otherwise imagine it would look the same. I'll open a bug against release.debian.org get this resolved -- thanks everyone! On Sun, Nov 30, 2014 at 10:17 AM, gregor herrmann gre...@debian.org wrote: On Sun, 30 Nov 2014 17:36:04 +0100, Alessandro Ghedini wrote: On dom, nov 30, 2014 at 03:06:55 +0100, Tobias Frost wrote: Am Sonntag, den 30.11.2014, 00:21 -0800 schrieb Tom Lee: Also, I feel like the serious severity is overstating the issue given that 0.11.0-4 builds fine in buildd/sbuild. Alessandro pointed out the periodic rebuilds would have revealed this issue otherwise. If there are no objections I'd like to propose we adjust the severity of this bug to normal leave the fix for this particular bug until after the Jessie freeze. Here I can reprodcue the FTBFS locally with pbuilder 0.215+nmu3, so I disagree. It maybe has not been detected *yet*? What does this yet even mean? Except inside pbuilder, hiredis builds fine [1]. The fact that it fails *only* inside pbuilder (and the fact that hiredis is not the only package in this situation) suggests that this is indeed a pbuilder bug. I really don't see how this is release critical in any way on the part of the hiredis package. While I tend to agree in general, here's an additional data point: I rebuilt 0.11.0-4 in my sid amd64 cowbuilder chroot, which has USENETWORK=yes (due to #753944) but firewalls off everything except localhost during build. And in this environment I see a test failure: make check make[2]: Entering directory '/tmp/buildd/hiredis-0.11.0' echo \ daemonize yes\n \ pidfile /tmp/hiredis-test-redis.pid\n \ port 56379\n \ bind 127.0.0.1\n \ unixsocket /tmp/hiredis-test-redis.sock \ | redis-server - ./hiredis-test -h 127.0.0.1 -p 56379 -s /tmp/hiredis-test-redis.sock || \ ( kill `cat /tmp/hiredis-test-redis.pid` false ) #01 Format command without interpolation: PASSED #02 Format command with %s string interpolation: PASSED #03 Format command with %s and an empty string: PASSED #04 Format command with an empty string in between proper interpolations: PASSED #05 Format command with %b string interpolation: PASSED #06 Format command with %b and an empty string: PASSED #07 Format command with literal %: PASSED #08 Format command with printf-delegation (int): PASSED #09 Format command with printf-delegation (char): PASSED #10 Format command with printf-delegation (short): PASSED #11 Format command with printf-delegation (long): PASSED #12 Format command with printf-delegation (long long): PASSED #13 Format command with printf-delegation (unsigned int): PASSED #14 Format command with printf-delegation (unsigned char): PASSED #15 Format command with printf-delegation (unsigned short): PASSED #16 Format command with printf-delegation (unsigned long): PASSED #17 Format command with printf-delegation (unsigned long long): PASSED #18 Format command with printf-delegation (float): PASSED #19 Format command with printf-delegation (double): PASSED #20 Format command with invalid printf format: PASSED #21 Format command by passing argc/argv without lengths: PASSED #22 Format command by passing argc/argv with lengths: PASSED #23 Error handling in reply parser: PASSED #24 Memory cleanup in reply parser: PASSED #25 Set error on nested multi bulks with depth 7: PASSED #26 Works with NULL functions for reply: PASSED #27 Works when a single newline (\r\n) covers two calls to feed: PASSED #28 Don't reset state after protocol error: PASSED #29 Don't do empty allocation for empty multi bulk: PASSED #30 Returns error when host cannot be resolved: FAILED #31 Returns error when the unix socket path doesn't accept connections: PASSED [..] which seems to be the same as what Daniel originally reported. Adding a printf statement to test.c shows: #30 Returns error when host cannot be resolved: FAILED ERROR: Temporary failure in name resolution test.c currently looks for Name or service not known or Can't resolve: idontexist.local but not for what I get here ... Not sure what the best way forward is; adding a test for Temporary failure in name resolution might be an option (and works unsurprisingly): #v+ --- a/test.c +++ b/test.c @@ -286,7 +286,8 @@ c = redisConnect((char*)idontexist.local, 6379); test_cond(c-err == REDIS_ERR_OTHER (strcmp(c-errstr,Name or service not known) == 0 || - strcmp(c-errstr,Can't resolve: idontexist.local) == 0)); + strcmp(c-errstr,Can't resolve: idontexist.local) == 0 || + strcmp(c-errstr,Temporary failure in name resolution) == 0)); redisFree(c);
Bug#768741: phlipple: FTBFS in jessie: ld: engine.o: undefined reference to symbol 'cos@@GLIBC_2.2.5'
I thought I had already uploaded it yeah, go ahead if I didn't Miry 2014-11-30 17:29 GMT+01:00 Vincent Legout vinc...@legout.info: Hi Miriam, Miriam Ruiz mir...@debian.org writes: I'll upload newer versions this afternoon :) zaz has already been uploaded. Do you still plan to upload phlipple? I can do the upload if needed. Thanks, Vincent -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#771561: systemd package is missing dependency on Linux kernel (linux-image?)
Package: systemd Version: 204-8 Severity: serious Dear Maintainer, according to upstream, systemd depends on the Linux kernel being in use. Quote http://cgit.freedesktop.org/systemd/systemd/tree/README?id=v215: Linux kernel = 3.0 Linux kernel = 3.3 for loop device partition support features with nspawn Linux kernel = 3.8 for Smack support According to Lennart Poettering, future systemd versions are going to depend on specific Linux kernel versions. For evidence, see this email from Lennart http://lists.freedesktop.org/archives/systemd-devel/2014-May/019657.html: To make this clear, we expect that systemd and kernels are updated in lockstep. We explicitly do not support really old kernels with really new systemd. So far we had the focus to support up to 2y old kernels (which means 3.4 right now), but even that should be taken with a grain of salt, as we already made clear that soon after kdbus is merged into the kernel we'll probably make a hard requirement on it from the systemd side. See also bug #770876, where udev device enumeration in Xorg does not work with Linux kernel 3.2, but does work with Linux kernel 3.16. Introducing a versioned dependency of systemd on a Linux kernel =3.4 could prevent breakage when upgrading from Wheezy, which comes with Linux kernel 3.2. I have marked this bug serious after reading the RC issues document at https://release.debian.org/testing/rc_policy.txt, according to this: Packages must include a Depends: line listing any other packages they require for operation, unless those packages are marked Essential: yes. I could not determine if the package linux-image is marked essential, as it seems to be an entirely virtual package. I have no idea how / if Debian can handle versioned dependencies with virtual packages anyway. -- Package-specific info: -- System Information: Debian Release: jessie/sid APT prefers testing APT policy: (500, 'testing') Architecture: i386 (i686) Kernel: Linux 3.13-1-686-pae (SMP w/1 CPU core) Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages systemd depends on: ii acl 2.2.52-2 ii adduser 3.113+nmu3 ii initscripts 2.88dsf-57 ii libacl1 2.2.52-2 ii libaudit11:2.4-1 ii libc62.19-13 ii libcap2 1:2.24-6 ii libcap2-bin 1:2.24-6 ii libcryptsetup4 2:1.6.6-3 ii libdbus-1-3 1.8.10-1 ii libgcrypt11 1.5.4-3 ii libkmod2 18-3 ii liblzma5 5.1.1alpha+20120614-2+b1 ii libpam0g 1.1.8-3.1 ii libselinux1 2.3-2 ii libsystemd-daemon0 204-8 ii libsystemd-journal0 204-8 ii libsystemd-login0204-8 ii libudev1 204-8 ii libwrap0 7.6.q-25 ii sysv-rc 2.88dsf-53.4 ii udev 204-8 ii util-linux 2.20.1-5.11 Versions of packages systemd recommends: ii libpam-systemd 204-8 Versions of packages systemd suggests: pn systemd-ui none -- Configuration Files: /etc/systemd/logind.conf changed [not included] -- no debconf information 0 overridden configuration files found. == /var/lib/systemd/deb-systemd-helper-enabled/NetworkManager-dispatcher.service.dsh-also == /etc/systemd/system/dbus-org.freedesktop.nm-dispatcher.service == /var/lib/systemd/deb-systemd-helper-enabled/acpid.service.dsh-also == /etc/systemd/system/multi-user.target.wants/acpid.service == /var/lib/systemd/deb-systemd-helper-enabled/smartd.service.dsh-also == /etc/systemd/system/multi-user.target.wants/smartd.service == /var/lib/systemd/deb-systemd-helper-enabled/dbus-org.freedesktop.nm-dispatcher.service == == /var/lib/systemd/deb-systemd-helper-enabled/anacron.service.dsh-also == /etc/systemd/system/multi-user.target.wants/anacron.service == /var/lib/systemd/deb-systemd-helper-enabled/sockets.target.wants/avahi-daemon.socket == == /var/lib/systemd/deb-systemd-helper-enabled/sockets.target.wants/lvm2-lvmetad.socket == == /var/lib/systemd/deb-systemd-helper-enabled/sockets.target.wants/acpid.socket == == /var/lib/systemd/deb-systemd-helper-enabled/dbus-org.freedesktop.ModemManager1.service == == /var/lib/systemd/deb-systemd-helper-enabled/epmd.service.dsh-also == /etc/systemd/system/sockets.target.wants/epmd.socket /etc/systemd/system/multi-user.target.wants/epmd.service == /var/lib/systemd/deb-systemd-helper-enabled/binfmt-support.service.dsh-also == /etc/systemd/system/multi-user.target.wants/binfmt-support.service == /var/lib/systemd/deb-systemd-helper-enabled/atd.service.dsh-also == /etc/systemd/system/multi-user.target.wants/atd.service == /var/lib/systemd/deb-systemd-helper-enabled/multi-user.target.wants/openvpn.service == == /var/lib/systemd/deb-systemd-helper-enabled/multi-user.target.wants/lxc.service == == /var/lib/systemd/deb-systemd-helper-enabled/multi-user.target.wants/anacron.service == ==
Processed: reassign 767803 to src:nvidia-graphics-drivers, forcibly merging 769072 767803
Processing commands for cont...@bugs.debian.org: reassign 767803 src:nvidia-graphics-drivers Bug #767803 [glx-diversions] gdm3: After update Gdm3 displays Oh No! Something has gone wrong Bug reassigned from package 'glx-diversions' to 'src:nvidia-graphics-drivers'. No longer marked as found in versions glx-alternatives/0.5.1. Ignoring request to alter fixed versions of bug #767803 to the same values previously set forcemerge 769072 767803 Bug #769072 [src:nvidia-graphics-drivers] Broken graphics due to libgl1-nvidia-glx auto-install on non-nvidia hardware Bug #767367 [src:nvidia-graphics-drivers] gnome-shell: Gnome shell refusing to start on intel graphics 3rd gen Bug #769191 [src:nvidia-graphics-drivers] Broken graphics due to libgl1-nvidia-glx auto-install on non-nvidia hardware Bug #769481 [src:nvidia-graphics-drivers] Broken graphics due to libgl1-nvidia-glx auto-install on non-nvidia hardware Bug #770588 [src:nvidia-graphics-drivers] Broken graphics due to libgl1-nvidia-glx auto-install on non-nvidia hardware Bug #767803 [src:nvidia-graphics-drivers] gdm3: After update Gdm3 displays Oh No! Something has gone wrong Severity set to 'critical' from 'important' Summary recorded from message bug 767803 message Added indication that 767803 affects xorg,glx-diversions,gnome-shell,xserver-xorg,gdm3 Marked as found in versions nvidia-graphics-drivers/340.46-2. Added tag(s) sid and jessie. Bug #767367 [src:nvidia-graphics-drivers] gnome-shell: Gnome shell refusing to start on intel graphics 3rd gen Bug #769191 [src:nvidia-graphics-drivers] Broken graphics due to libgl1-nvidia-glx auto-install on non-nvidia hardware Bug #769481 [src:nvidia-graphics-drivers] Broken graphics due to libgl1-nvidia-glx auto-install on non-nvidia hardware Bug #770588 [src:nvidia-graphics-drivers] Broken graphics due to libgl1-nvidia-glx auto-install on non-nvidia hardware Merged 767367 767803 769072 769191 769481 770588 thanks Stopping processing here. Please contact me if you need assistance. -- 767367: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=767367 767803: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=767803 769072: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=769072 769191: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=769191 769481: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=769481 770588: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=770588 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#770648: hiredis: FTBFS: Test failure
On Sun, 30 Nov 2014 10:51:56 -0800, Tom Lee wrote: Talked this over with the release team on #debian-release, Except that noone who responded is a member of the release team :) Cheers, gregor -- .''`. Homepage: http://info.comodo.priv.at/ - OpenPGP key 0xBB3A68018649AA06 : :' : Debian GNU/Linux user, admin, and developer - http://www.debian.org/ `. `' Member of VIBE!AT SPI, fellow of the Free Software Foundation Europe `- NP: Cat Stevens: I Love My Dog signature.asc Description: Digital Signature
Bug#771561: systemd: please remove /etc/fstab from bug report
Package: systemd Version: 204-8 Followup-For: Bug #771561 Dear Maintainer, This bug contains the contents of my /etc/fstab. I was never asked for this. I already found bug #743158. “We don't know, so assume yes.” is not consent. Please remove the /etc/fstab from the bug report. I will never again report bugs against systemd. -- Package-specific info: -- System Information: Debian Release: jessie/sid APT prefers testing APT policy: (500, 'testing') Architecture: i386 (i686) Kernel: Linux 3.13-1-686-pae (SMP w/1 CPU core) Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages systemd depends on: ii acl 2.2.52-2 ii adduser 3.113+nmu3 ii initscripts 2.88dsf-57 ii libacl1 2.2.52-2 ii libaudit11:2.4-1 ii libc62.19-13 ii libcap2 1:2.24-6 ii libcap2-bin 1:2.24-6 ii libcryptsetup4 2:1.6.6-3 ii libdbus-1-3 1.8.10-1 ii libgcrypt11 1.5.4-3 ii libkmod2 18-3 ii liblzma5 5.1.1alpha+20120614-2+b1 ii libpam0g 1.1.8-3.1 ii libselinux1 2.3-2 ii libsystemd-daemon0 204-8 ii libsystemd-journal0 204-8 ii libsystemd-login0204-8 ii libudev1 204-8 ii libwrap0 7.6.q-25 ii sysv-rc 2.88dsf-53.4 ii udev 204-8 ii util-linux 2.20.1-5.11 Versions of packages systemd recommends: ii libpam-systemd 204-8 Versions of packages systemd suggests: pn systemd-ui none -- Configuration Files: /etc/systemd/logind.conf changed [not included] -- no debconf information 0 overridden configuration files found. == /var/lib/systemd/deb-systemd-helper-enabled/NetworkManager-dispatcher.service.dsh-also == /etc/systemd/system/dbus-org.freedesktop.nm-dispatcher.service == /var/lib/systemd/deb-systemd-helper-enabled/acpid.service.dsh-also == /etc/systemd/system/multi-user.target.wants/acpid.service == /var/lib/systemd/deb-systemd-helper-enabled/smartd.service.dsh-also == /etc/systemd/system/multi-user.target.wants/smartd.service == /var/lib/systemd/deb-systemd-helper-enabled/dbus-org.freedesktop.nm-dispatcher.service == == /var/lib/systemd/deb-systemd-helper-enabled/anacron.service.dsh-also == /etc/systemd/system/multi-user.target.wants/anacron.service == /var/lib/systemd/deb-systemd-helper-enabled/sockets.target.wants/avahi-daemon.socket == == /var/lib/systemd/deb-systemd-helper-enabled/sockets.target.wants/lvm2-lvmetad.socket == == /var/lib/systemd/deb-systemd-helper-enabled/sockets.target.wants/acpid.socket == == /var/lib/systemd/deb-systemd-helper-enabled/dbus-org.freedesktop.ModemManager1.service == == /var/lib/systemd/deb-systemd-helper-enabled/epmd.service.dsh-also == /etc/systemd/system/sockets.target.wants/epmd.socket /etc/systemd/system/multi-user.target.wants/epmd.service == /var/lib/systemd/deb-systemd-helper-enabled/binfmt-support.service.dsh-also == /etc/systemd/system/multi-user.target.wants/binfmt-support.service == /var/lib/systemd/deb-systemd-helper-enabled/atd.service.dsh-also == /etc/systemd/system/multi-user.target.wants/atd.service == /var/lib/systemd/deb-systemd-helper-enabled/multi-user.target.wants/openvpn.service == == /var/lib/systemd/deb-systemd-helper-enabled/multi-user.target.wants/lxc.service == == /var/lib/systemd/deb-systemd-helper-enabled/multi-user.target.wants/anacron.service == == /var/lib/systemd/deb-systemd-helper-enabled/multi-user.target.wants/smartd.service == == /var/lib/systemd/deb-systemd-helper-enabled/multi-user.target.wants/NetworkManager.service == == /var/lib/systemd/deb-systemd-helper-enabled/multi-user.target.wants/cron.service == == /var/lib/systemd/deb-systemd-helper-enabled/multi-user.target.wants/pppd-dns.service == == /var/lib/systemd/deb-systemd-helper-enabled/multi-user.target.wants/binfmt-support.service == == /var/lib/systemd/deb-systemd-helper-enabled/multi-user.target.wants/lm-sensors.service == == /var/lib/systemd/deb-systemd-helper-enabled/multi-user.target.wants/ModemManager.service == == /var/lib/systemd/deb-systemd-helper-enabled/multi-user.target.wants/rsyslog.service == == /var/lib/systemd/deb-systemd-helper-enabled/multi-user.target.wants/avahi-daemon.service == == /var/lib/systemd/deb-systemd-helper-enabled/multi-user.target.wants/atd.service == == /var/lib/systemd/deb-systemd-helper-enabled/local-fs.target.wants/lvm2-activation-early.service == == /var/lib/systemd/deb-systemd-helper-enabled/local-fs.target.wants/lvm2-activation.service == == /var/lib/systemd/deb-systemd-helper-enabled/dbus-org.freedesktop.NetworkManager.service == == /var/lib/systemd/deb-systemd-helper-enabled/cron.service.dsh-also == /etc/systemd/system/multi-user.target.wants/cron.service == /var/lib/systemd/deb-systemd-helper-enabled/lvm2-activation.service.dsh-also ==
Bug#771561: marked as done (systemd package is missing dependency on Linux kernel (linux-image?))
Your message dated Sun, 30 Nov 2014 19:27:03 + with message-id 1417375623.7215.122.ca...@decadent.org.uk and subject line Re: systemd package is missing dependency on Linux kernel (linux-image?) has caused the Debian Bug report #771561, regarding systemd package is missing dependency on Linux kernel (linux-image?) 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.) -- 771561: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=771561 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: systemd Version: 204-8 Severity: serious Dear Maintainer, according to upstream, systemd depends on the Linux kernel being in use. Quote http://cgit.freedesktop.org/systemd/systemd/tree/README?id=v215: Linux kernel = 3.0 Linux kernel = 3.3 for loop device partition support features with nspawn Linux kernel = 3.8 for Smack support According to Lennart Poettering, future systemd versions are going to depend on specific Linux kernel versions. For evidence, see this email from Lennart http://lists.freedesktop.org/archives/systemd-devel/2014-May/019657.html: To make this clear, we expect that systemd and kernels are updated in lockstep. We explicitly do not support really old kernels with really new systemd. So far we had the focus to support up to 2y old kernels (which means 3.4 right now), but even that should be taken with a grain of salt, as we already made clear that soon after kdbus is merged into the kernel we'll probably make a hard requirement on it from the systemd side. See also bug #770876, where udev device enumeration in Xorg does not work with Linux kernel 3.2, but does work with Linux kernel 3.16. Introducing a versioned dependency of systemd on a Linux kernel =3.4 could prevent breakage when upgrading from Wheezy, which comes with Linux kernel 3.2. I have marked this bug serious after reading the RC issues document at https://release.debian.org/testing/rc_policy.txt, according to this: Packages must include a Depends: line listing any other packages they require for operation, unless those packages are marked Essential: yes. I could not determine if the package linux-image is marked essential, as it seems to be an entirely virtual package. I have no idea how / if Debian can handle versioned dependencies with virtual packages anyway. -- Package-specific info: -- System Information: Debian Release: jessie/sid APT prefers testing APT policy: (500, 'testing') Architecture: i386 (i686) Kernel: Linux 3.13-1-686-pae (SMP w/1 CPU core) Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages systemd depends on: ii acl 2.2.52-2 ii adduser 3.113+nmu3 ii initscripts 2.88dsf-57 ii libacl1 2.2.52-2 ii libaudit11:2.4-1 ii libc62.19-13 ii libcap2 1:2.24-6 ii libcap2-bin 1:2.24-6 ii libcryptsetup4 2:1.6.6-3 ii libdbus-1-3 1.8.10-1 ii libgcrypt11 1.5.4-3 ii libkmod2 18-3 ii liblzma5 5.1.1alpha+20120614-2+b1 ii libpam0g 1.1.8-3.1 ii libselinux1 2.3-2 ii libsystemd-daemon0 204-8 ii libsystemd-journal0 204-8 ii libsystemd-login0204-8 ii libudev1 204-8 ii libwrap0 7.6.q-25 ii sysv-rc 2.88dsf-53.4 ii udev 204-8 ii util-linux 2.20.1-5.11 Versions of packages systemd recommends: ii libpam-systemd 204-8 Versions of packages systemd suggests: pn systemd-ui none -- Configuration Files: /etc/systemd/logind.conf changed [not included] -- no debconf information 0 overridden configuration files found. == /var/lib/systemd/deb-systemd-helper-enabled/NetworkManager-dispatcher.service.dsh-also == /etc/systemd/system/dbus-org.freedesktop.nm-dispatcher.service == /var/lib/systemd/deb-systemd-helper-enabled/acpid.service.dsh-also == /etc/systemd/system/multi-user.target.wants/acpid.service == /var/lib/systemd/deb-systemd-helper-enabled/smartd.service.dsh-also == /etc/systemd/system/multi-user.target.wants/smartd.service == /var/lib/systemd/deb-systemd-helper-enabled/dbus-org.freedesktop.nm-dispatcher.service == == /var/lib/systemd/deb-systemd-helper-enabled/anacron.service.dsh-also == /etc/systemd/system/multi-user.target.wants/anacron.service == /var/lib/systemd/deb-systemd-helper-enabled/sockets.target.wants/avahi-daemon.socket == == /var/lib/systemd/deb-systemd-helper-enabled/sockets.target.wants/lvm2-lvmetad.socket == ==
Processed: Bug#769947 marked as pending
Processing commands for cont...@bugs.debian.org: tag 769947 pending Bug #769947 [mate-terminal] mate-terminal: Segfaults after update Added tag(s) pending. thanks Stopping processing here. Please contact me if you need assistance. -- 769947: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=769947 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#771561: Bug:#771561: systemd: please remove /etc/fstab from bug report
Dear BTS maintainers, Nils (CC'ed) have requested the removal of an attached file from bug report, see below (#771561, BCC'ed to avoid duplicate requests to you). The file is attached to #771561, comment #5. Thanks, ~Niels On Sun, 30 Nov 2014 20:16:28 +0100 Nils Dagsson Moskopp nils+debian-report...@dieweltistgarnichtso.net wrote: Package: systemd Version: 204-8 Followup-For: Bug #771561 Dear Maintainer, This bug contains the contents of my /etc/fstab. I was never asked for this. I already found bug #743158. âWe don't know, so assume yes.â is not consent. Please remove the /etc/fstab from the bug report. I will never again report bugs against systemd. [...] -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#769947: mate-terminal: Segfaults after update
Hi Ben On Fr 28 Nov 2014 23:25:02 CET, Ben Whyall wrote: Package: mate-terminal Version: 1.8.1+dfsg1-2 Followup-For: Bug #769947 Hi Mike I built the package using the provided debian source and applying the patch referenced above in terminal.c and i can confirm that i dont get the error on trying to start a mate terminal. Ben Thanks for testing this. I have just uploaded a new mate-terminal package version with that patch applied. Mike -- DAS-NETZWERKTEAM mike gabriel, herweg 7, 24357 fleckeby fon: +49 (1520) 1976 148 GnuPG Key ID 0x25771B31 mail: mike.gabr...@das-netzwerkteam.de, http://das-netzwerkteam.de freeBusy: https://mail.das-netzwerkteam.de/freebusy/m.gabriel%40das-netzwerkteam.de.xfb pgpQDrWm99oRz.pgp Description: Digitale PGP-Signatur
Bug#769947: marked as pending
tag 769947 pending thanks Hello, Bug #769947 reported by you has been fixed in the Git repository. You can see the changelog below, and you can check the diff of the fix at: http://git.debian.org/?p=pkg-mate/mate-terminal.git;a=commitdiff;h=446380f --- commit 446380ffed66faaf04e6160bad0249b0e408f3a0 Author: Mike Gabriel mike.gabr...@das-netzwerkteam.de Date: Sun Nov 30 20:28:50 2014 +0100 upload to unstable (debian/1.8.1+dfsg1-3) diff --git a/debian/changelog b/debian/changelog index 9971f39..db52f0f 100644 --- a/debian/changelog +++ b/debian/changelog @@ -1,3 +1,12 @@ +mate-terminal (1.8.1+dfsg1-3) unstable; urgency=medium + + * debian/patches: ++ Add 1002_fix-occasional-segfaults-at-session-startup.patch. + Fix segfaults for mate-terminal in non-standard setups if started + during session startup. (Closes: #769947). + + -- Mike Gabriel sunwea...@debian.org Sun, 30 Nov 2014 20:25:38 +0100 + mate-terminal (1.8.1+dfsg1-2) unstable; urgency=medium * A changelog fixup upload. The below two changes have already been -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#769481: marked as done (Broken graphics due to libgl1-nvidia-glx auto-install on non-nvidia hardware)
Your message dated Sun, 30 Nov 2014 19:34:02 +
with message-id e1xvafu-00025s...@franck.debian.org
and subject line Bug#769072: fixed in nvidia-graphics-drivers 340.46-6
has caused the Debian Bug report #769072,
regarding Broken graphics due to libgl1-nvidia-glx auto-install on non-nvidia
hardware
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.)
--
769072: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=769072
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
---BeginMessage---
Package: wine
Version: 1.6.2-16
Severity: critical
--- Please enter the report below this line. ---
Hi,
before my last upgrade my computer executed Irfanview and Evernote (with
some little problem).
After the last update, Irfanview and Evernote freeze (see attachment).
The main chage during the last upgrade is the passage from nouveau to
nvidia propietary drivers (istalle by synaptic using ufficial
repositories). The computer has a G86 [GeForce 8500 GT] [10DE:421]. I
need GLX in order to use blender.
I have another computer computer with the same video card that does not
presents problems.
Each computer uses an intel CPU (they are defferent each other)
Please write me if you need more information.
--- System information. ---
Architecture: amd64
Kernel: Linux 3.16.0-4-amd64
Debian Release: jessie/sid
500 testing-updates ftp.it.debian.org
500 testing www.deb-multimedia.org
500 testing security.debian.org
500 testing ftp.it.debian.org
500 testing apt.jenslody.de
500 stable repo.wuala.com
500 stable apt.spideroak.com
500 sid linux.dropbox.com
500 debian packages.linuxmint.com
100 jessie-backports ftp.it.debian.org
--- Package information. ---
Depends (Version) | Installed
=-+-==
file | 1:5.20-2
wine64 (= 1.6.2-8) | 1.6.2-16
OR wine32 (= 1.6.2-8) | 1.6.2-16
Package's Recommends field is empty.
Suggests (Version) | Installed
-+-===
wine-doc | 1.0.0-1
binfmt-support | 2.1.5-1
ttf-mscorefonts-installer|
winbind |
avscan |
OR klamav |
OR clamav | 0.98.5~rc1+dfsg-3
---End Message---
---BeginMessage---
Source: nvidia-graphics-drivers
Source-Version: 340.46-6
We believe that the bug you reported is fixed in the latest version of
nvidia-graphics-drivers, 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 769...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Andreas Beckmann a...@debian.org (supplier of updated nvidia-graphics-drivers
package)
(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Format: 1.8
Date: Sun, 30 Nov 2014 20:08:09 +0100
Source: nvidia-graphics-drivers
Binary: nvidia-driver nvidia-driver-bin nvidia-glx xserver-xorg-video-nvidia
libgl1-nvidia-glx libgl1-nvidia-glx-i386 libegl1-nvidia libgles1-nvidia
libgles2-nvidia libnvidia-eglcore nvidia-alternative nvidia-kernel-dkms
nvidia-kernel-source nvidia-vdpau-driver nvidia-smi nvidia-cuda-mps libcuda1
libcuda1-i386 libnvidia-compiler libnvcuvid1 libnvidia-encode1 libnvidia-ifr1
libnvidia-fbc1 libnvidia-ml1 nvidia-opencl-common nvidia-opencl-icd
nvidia-libopencl1 nvidia-detect
Architecture: source
Version: 340.46-6
Distribution: unstable
Urgency: medium
Maintainer: Debian NVIDIA Maintainers pkg-nvidia-de...@lists.alioth.debian.org
Changed-By: Andreas Beckmann a...@debian.org
Description:
libcuda1 - NVIDIA CUDA Driver Library
libcuda1-i386 - NVIDIA CUDA 32-bit runtime library${nvidia:LegacyDesc}
libegl1-nvidia - NVIDIA binary EGL libraries${nvidia:LegacyDesc}
libgl1-nvidia-glx - NVIDIA binary OpenGL libraries${nvidia:LegacyDesc}
libgl1-nvidia-glx-i386 - NVIDIA binary OpenGL 32-bit
libraries${nvidia:LegacyDesc}
libgles1-nvidia - NVIDIA binary OpenGL|ES 1.x libraries${nvidia:LegacyDesc}
libgles2-nvidia - NVIDIA binary OpenGL|ES 2.x
Bug#767367: marked as done (gnome-shell: Gnome shell refusing to start on intel graphics 3rd gen)
Your message dated Sun, 30 Nov 2014 19:34:02 + with message-id e1xvafu-00025s...@franck.debian.org and subject line Bug#769072: fixed in nvidia-graphics-drivers 340.46-6 has caused the Debian Bug report #769072, regarding gnome-shell: Gnome shell refusing to start on intel graphics 3rd gen 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.) -- 769072: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=769072 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: gnome-shell Version: 3.14.1-1 Severity: important Dear Maintainer, after the graphic drivers update on testing at the beginning of the week gnome-shell refuses to load, prompting the message Oh no sthg has gone wrong. Syslog messages indicate that 3D support is missing, even though everything was working properly before the update: org.a11y.Bus[5333]: Activating service name='org.a11y.atspi.Registry' org.a11y.Bus[5333]: Successfully activated service 'org.a11y.atspi.Registry' org.a11y.atspi.Registry[5340]: SpiRegistry daemon is running with well-known name - org.a11y.atspi.Registry /usr/bin/dbus-launch[5329]: Xlib: extension GLX missing on display :0. /usr/bin/dbus-launch[5329]: Xlib: extension GLX missing on display :0. /usr/bin/dbus-launch[5329]: Xlib: extension GLX missing on display :0. /usr/bin/dbus-launch[5329]: gnome-session-is-accelerated: No hardware 3D support. A 'gnome-shell -d :0 -r' returns the following errors: Xlib: extension GLX missing on display :0. libEGL warning: GLX/DRI2 is not supported libEGL warning: DRI2: failed to authenticate The i915 is loaded and i don't know what else to check... Could point me in the right direction to get gnome back? xserver-xorg-video-intel version: 2:2.21.15-2+b2 I don't know if this bug is related to gnome-shell or the driver update. But in any case gnome does not seem to try to switch to a fallback mode with no 3d enabled, is this normal? Thanks a lot for your work, Merlini Adrien -- System Information: Debian Release: jessie/sid APT prefers testing-updates APT policy: (500, 'testing-updates'), (500, 'testing') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.16-3-amd64 (SMP w/4 CPU cores) Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages gnome-shell depends on: ii dconf-gsettings-backend [gsettings-backend] 0.22.0-1 ii evolution-data-server3.12.7.1-1 ii gir1.2-accountsservice-1.0 0.6.37-3+b1 ii gir1.2-atspi-2.0 2.14.0-1 ii gir1.2-caribou-1.0 0.4.15-1 ii gir1.2-clutter-1.0 1.20.0-1 ii gir1.2-freedesktop 1.42.0-2.2 ii gir1.2-gcr-3 3.14.0-2 ii gir1.2-gdesktopenums-3.0 3.14.1-1 ii gir1.2-gdm3 3.14.1-1 ii gir1.2-gkbd-3.0 3.6.0-1 ii gir1.2-glib-2.0 1.42.0-2.2 ii gir1.2-gnomebluetooth-1.03.14.0-1 ii gir1.2-gnomedesktop-3.0 3.14.1-1 ii gir1.2-gtk-3.0 3.14.3-1 ii gir1.2-ibus-1.0 1.5.8-3 ii gir1.2-mutter-3.03.14.1-1 ii gir1.2-networkmanager-1.00.9.10.0-3 ii gir1.2-nmgtk-1.0 0.9.10.0-2 ii gir1.2-pango-1.0 1.36.8-2 ii gir1.2-polkit-1.00.105-7 ii gir1.2-soup-2.4 2.48.0-1 ii gir1.2-telepathyglib-0.120.24.1-1 ii gir1.2-telepathylogger-0.2 0.8.1-1 ii gir1.2-upowerglib-1.00.99.1-3 ii gjs 1.42.0-1 ii gnome-backgrounds3.14.1-1 ii gnome-icon-theme-symbolic3.12.0-1 ii gnome-settings-daemon3.14.1-1 ii gnome-shell-common 3.14.1-1 ii gnome-themes-standard3.14.0-1 ii gsettings-desktop-schemas3.14.1-1 ii libatk-bridge2.0-0 2.14.0-2 ii libatk1.0-0 2.14.0-1 ii libc62.19-12 ii libcairo21.12.16-5 ii libcanberra-gtk3-0 0.30-2.1 ii libcanberra0 0.30-2.1 ii libclutter-1.0-0
Bug#769947: marked as done (mate-terminal: Segfaults after update)
Your message dated Sun, 30 Nov 2014 19:33:49 +
with message-id e1xvafh-00024u...@franck.debian.org
and subject line Bug#769947: fixed in mate-terminal 1.8.1+dfsg1-3
has caused the Debian Bug report #769947,
regarding mate-terminal: Segfaults after update
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.)
--
769947: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=769947
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
---BeginMessage---
Package: mate-terminal
Version: 1.8.1+dfsg1-2
Severity: important
Hi,
After my latest apt-get upgrade, mate-terminal segfaults on start.
$ gdb mate-terminal
GNU gdb (Debian 7.7.1+dfsg-5) 7.7.1
(gdb) run
Starting program: /usr/bin/mate-terminal [Thread debugging using
libthread_db enabled]
Using host libthread_db library /lib/x86_64-linux-gnu/libthread_db.so.1.
Program received signal SIGSEGV, Segmentation fault.
get_initial_workspace () at terminal.c:539
539 terminal.c: No such file or directory.
(gdb) where
#0 get_initial_workspace () at terminal.c:539
#1 main (argc=1, argv=0x7fffe388) at terminal.c:645
(gdb) continue
Continuing.
Program terminated with signal SIGSEGV, Segmentation fault.
The program no longer exists.
(gdb) where
No stack.
(gdb) quit
(I'm afraid my gdb skills are pretty much non-existent)
Cheers,
Alex
-- System Information:
Debian Release: jessie/sid
APT prefers testing
APT policy: (500, 'testing')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 3.16-2-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Versions of packages mate-terminal depends on:
ii libatk1.0-0 2.14.0-1
ii libc6 2.19-13
ii libcairo2 1.14.0-2.1
ii libdconf1 0.22.0-1
ii libfontconfig12.11.0-6.1
ii libfreetype6 2.5.2-2
ii libgdk-pixbuf2.0-02.31.1-2+b1
ii libglib2.0-0 2.42.0-2
ii libgtk2.0-0 2.24.25-1
ii libice6 2:1.0.9-1
ii libpango-1.0-01.36.8-2
ii libpangocairo-1.0-0 1.36.8-2
ii libpangoft2-1.0-0 1.36.8-2
ii libsm62:1.2.2-1
ii libvte9 1:0.28.2-5
ii libx11-6 2:1.6.2-3
ii libxext6 2:1.3.3-1
ii mate-desktop-common 1.8.1+dfsg1-2
ii mate-terminal-common 1.8.1+dfsg1-2
pn python:anynone
mate-terminal recommends no packages.
mate-terminal suggests no packages.
-- no debconf information
--
___mail: alex at corcoles dot net
{~._.~} ICQ: 66791436
( Y )MSN: koalillo at fastmail dot fm
()~*~()Y!: koalillo
(_)-(_) http://alex.corcoles.net/
---End Message---
---BeginMessage---
Source: mate-terminal
Source-Version: 1.8.1+dfsg1-3
We believe that the bug you reported is fixed in the latest version of
mate-terminal, 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 769...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Mike Gabriel sunwea...@debian.org (supplier of updated mate-terminal package)
(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Format: 1.8
Date: Sun, 30 Nov 2014 20:25:38 +0100
Source: mate-terminal
Binary: mate-terminal mate-terminal-common mate-terminal-dbg
Architecture: source amd64 all
Version: 1.8.1+dfsg1-3
Distribution: unstable
Urgency: medium
Maintainer: MATE Packaging Team pkg-mate-t...@lists.alioth.debian.org
Changed-By: Mike Gabriel sunwea...@debian.org
Description:
mate-terminal - MATE terminal emulator application
mate-terminal-common - MATE terminal emulator application (common files)
mate-terminal-dbg - MATE terminal emulator application (debugging symbols)
Closes: 769947
Changes:
mate-terminal (1.8.1+dfsg1-3) unstable; urgency=medium
.
* debian/patches:
+ Add 1002_fix-occasional-segfaults-at-session-startup.patch.
Fix segfaults for mate-terminal in non-standard setups if started
during session startup. (Closes: #769947).
Checksums-Sha1:
c0bece8f059e53a89215e9cf30b3a612633651a2 2481 mate-terminal_1.8.1+dfsg1-3.dsc
2727b81e50b5d0f1c5b805f092e5b626707d6223 6084
mate-terminal_1.8.1+dfsg1-3.debian.tar.xz
Bug#767803: marked as done (gdm3: After update Gdm3 displays Oh No! Something has gone wrong)
Your message dated Sun, 30 Nov 2014 19:34:02 + with message-id e1xvafu-00025s...@franck.debian.org and subject line Bug#769072: fixed in nvidia-graphics-drivers 340.46-6 has caused the Debian Bug report #769072, regarding gdm3: After update Gdm3 displays Oh No! Something has gone wrong 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.) -- 769072: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=769072 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: gdm3 Version: 3.14.1-1 Severity: important Dear Maintainer, I use Gdm3 and Mate. After the update of my testing (I usually done once a week), at the next boot Gdm3 crach and displays: Oh No! Something has gone wrong Gdm3 has been updated from 3.14.0-1 to 3.14.1-1. To start a graphical session I installed Lightdm and I configured as the default display manager. In Lightdm if I chose a Gnome session, I return to the screen lightdm but without the interface, I have only the wallpaper. By choosing a Mate session, the desktop starts normally. In the file .xsession-errors: Xsession: X session started for fredo at dimanche 2 novembre 2014, 11:08:55 (UTC+0100) localuser:fredo being added to access control list ** (gnome-session-check-accelerated:1714): WARNING **: Couldn't register with accessibility bus: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken. Xlib: extension GLX missing on display :0. Xlib: extension GLX missing on display :0. Xlib: extension GLX missing on display :0. gnome-session-is-accelerated: No hardware 3D support. Xlib: extension GLX missing on display :0. gnome-session-check-accelerated: Helper exited with code 256 ** (gnome-session-check-accelerated:1716): WARNING **: Couldn't register with accessibility bus: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken. Xlib: extension GLX missing on display :0. Xlib: extension GLX missing on display :0. Xlib: extension GLX missing on display :0. gnome-session-is-accelerated: No hardware 3D support. Xlib: extension GLX missing on display :0. gnome-session-check-accelerated: Helper exited with code 256 ** (process:1660): WARNING **: software acceleration check failed: Child process exited with code 1 XIO: fatal IO error 11 (Ressource temporairement non disponible) on X server :0 after 40 requests (40 known processed) with 1 events remaining. Regards. -- System Information: Debian Release: jessie/sid APT prefers testing-updates APT policy: (500, 'testing-updates'), (500, 'stable-updates'), (500, 'testing'), (500, 'stable') Architecture: i386 (i686) Kernel: Linux 3.16-3-686-pae (SMP w/1 CPU core) Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages gdm3 depends on: ii accountsservice 0.6.37-3+b1 ii adduser 3.113+nmu3 ii dconf-cli0.22.0-1 ii dconf-gsettings-backend 0.22.0-1 ii debconf [debconf-2.0]1.5.53 ii eterm [x-terminal-emulator] 0.9.6-1 ii gir1.2-gdm3 3.14.1-1 ii gnome-session [x-session-manager]3.14.0-2 ii gnome-session-bin3.14.0-2 ii gnome-session-flashback [x-session-manager] 3.8.1-6 ii gnome-settings-daemon3.14.1-1 ii gnome-shell 3.14.1-1 ii gnome-terminal [x-terminal-emulator] 3.14.1-1 ii gsettings-desktop-schemas3.14.1-1 ii libaccountsservice0 0.6.37-3+b1 ii libaudit11:2.4-1 ii libc62.19-12 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-1 ii libglib2.0-0 2.42.0-2 ii libglib2.0-bin 2.42.0-2 ii libgtk-3-0 3.14.3-1 ii libpam-modules 1.1.8-3.1 ii libpam-runtime 1.1.8-3.1 ii
Bug#769072: marked as done (Broken graphics due to libgl1-nvidia-glx auto-install on non-nvidia hardware)
Your message dated Sun, 30 Nov 2014 19:34:02 + with message-id e1xvafu-00025s...@franck.debian.org and subject line Bug#769072: fixed in nvidia-graphics-drivers 340.46-6 has caused the Debian Bug report #769072, regarding Broken graphics due to libgl1-nvidia-glx auto-install on non-nvidia hardware 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.) -- 769072: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=769072 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: gnome-shell Version: 3.14.1-1 Severity: grave I have this problem after an upgrade made a week or so. Unfortunately I haven't analysed the problem immediately, because of an urgent work to do I've just started to use the computer remotely with ssh. I vaguely remember a message saying something about configuring a video driver, which unfortunatelu I did not write down. I've looked for it in apt log but was unable to find it. Are all the apt messages stored somewhere? The files ~/.cache/gdm/session.log and ~/.cache/gdm/session.log.old are older than the problem, new files are not created. On another partition of the very computer I made a fresh install of jessie and it works OK. How to pin down the differences in the configuration? My working system has more packages installed, but the packages possibly relevant to the problem seems the same on both installation. I will appreciate very much your help. Janusz -- System Information: Debian Release: jessie/sid APT prefers testing APT policy: (500, 'testing') Architecture: i386 (i686) Kernel: Linux 3.16-3-686-pae (SMP w/2 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages gnome-shell depends on: ii dconf-gsettings-backend [gsettings-backend] 0.22.0-1 ii evolution-data-server3.12.7.1-1 ii gir1.2-accountsservice-1.0 0.6.37-3+b1 ii gir1.2-atspi-2.0 2.14.0-1 ii gir1.2-caribou-1.0 0.4.15-1 ii gir1.2-clutter-1.0 1.20.0-1 ii gir1.2-freedesktop 1.42.0-2.2 ii gir1.2-gcr-3 3.14.0-2 ii gir1.2-gdesktopenums-3.0 3.14.1-1 ii gir1.2-gdm3 3.14.1-1 ii gir1.2-gkbd-3.0 3.6.0-1 ii gir1.2-glib-2.0 1.42.0-2.2 ii gir1.2-gnomebluetooth-1.03.14.0-1 ii gir1.2-gnomedesktop-3.0 3.14.1-1 ii gir1.2-gtk-3.0 3.14.4-1 ii gir1.2-ibus-1.0 1.5.9-1 ii gir1.2-mutter-3.03.14.1-2 ii gir1.2-networkmanager-1.00.9.10.0-3 ii gir1.2-nmgtk-1.0 0.9.10.0-2 ii gir1.2-pango-1.0 1.36.8-2 ii gir1.2-polkit-1.00.105-7 ii gir1.2-soup-2.4 2.48.0-1 ii gir1.2-telepathyglib-0.120.24.1-1 ii gir1.2-telepathylogger-0.2 0.8.1-1 ii gir1.2-upowerglib-1.00.99.1-3 ii gjs 1.42.0-1 ii gnome-backgrounds3.14.1-1 ii gnome-icon-theme-symbolic3.12.0-1 ii gnome-settings-daemon3.14.1-1 ii gnome-shell-common 3.14.1-1 ii gnome-themes-standard3.14.0-1 ii gsettings-desktop-schemas3.14.1-1 ii libatk-bridge2.0-0 2.14.0-2 ii libatk1.0-0 2.14.0-1 ii libc62.19-12 ii libcairo21.14.0-2.1 ii libcanberra-gtk3-0 0.30-2.1 ii libcanberra0 0.30-2.1 ii libclutter-1.0-0 1.20.0-1 ii libcogl-pango20 1.18.2-2 ii libcogl201.18.2-2 ii libcroco30.6.8-3 ii libdbus-glib-1-2 0.102-1 ii libecal-1.2-16 3.12.7.1-1 ii libedataserver-1.2-183.12.7.1-1 ii libgcr-base-3-1 3.14.0-2 ii libgdk-pixbuf2.0-0 2.31.1-2+b1 ii libgirepository-1.0-11.42.0-2.2 ii libgjs0e [libgjs0-libmozjs-24-0]
Bug#767676: marked as done (ola-rdm-tests: fails to install: subprocess installed post-installation script returned error exit status 10)
Your message dated Sun, 30 Nov 2014 19:49:02 + with message-id e1xvauq-0003su...@franck.debian.org and subject line Bug#767676: fixed in ola 0.9.1-1.1 has caused the Debian Bug report #767676, regarding ola-rdm-tests: fails to install: subprocess installed post-installation script returned error exit status 10 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.) -- 767676: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=767676 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: ola-rdm-tests Version: 0.9.1-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 ola-rdm-tests. (Reading database ... 8847 files and directories currently installed.) Preparing to unpack .../ola-rdm-tests_0.9.1-1_all.deb ... Unpacking ola-rdm-tests (0.9.1-1) ... Setting up ola-rdm-tests (0.9.1-1) ... dpkg: error processing package ola-rdm-tests (--configure): subprocess installed post-installation script returned error exit status 10 Errors were encountered while processing: ola-rdm-tests cheers, Andreas ---End Message--- ---BeginMessage--- Source: ola Source-Version: 0.9.1-1.1 We believe that the bug you reported is fixed in the latest version of ola, 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 767...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Jean Baptiste Favre deb...@jbfavre.org (supplier of updated ola 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: Sun, 16 Nov 2014 17:44:18 +0100 Source: ola Binary: libola-dev ola-python ola-rdm-tests ola libola1 Architecture: source amd64 all Version: 0.9.1-1.1 Distribution: unstable Urgency: medium Maintainer: Wouter Verhelst wou...@debian.org Changed-By: Jean Baptiste Favre deb...@jbfavre.org Description: libola-dev - Open Lighting Architecture - development libraries libola1- Open Lighting Architecture - shared libraries ola- Open Lighting Architecture ola-python - Open Lighting Architecture - Python Classes ola-rdm-tests - Open Lighting Architecture - RDM Responder Tests Closes: 767676 769331 769670 Changes: ola (0.9.1-1.1) unstable; urgency=medium . * Non-maintainer upload * Remove debconf calls from ola-rdm-tests postinst (Closes: #767676) * Ship /etc/ola within ola ola-rdm-tests packages (Closes: #769331) * Add a patch which fix failing test when running in pbuilder (Closes: #769670) * Fix other important issues: - Remove the check for $RUN_DAEMON from both init scripts olad and rdm_test_server (Package maintainer disagree about this way of controling service) - Remove ola-rdm-tests postinst since its only purpose was to provide /etc/default/ola-rdm-tests - Add postrm scripts for packages ola ola-rdm-tests to fully remove configuration files so that piuparts tests can pass Checksums-Sha1: 97f86ff712790fab9d447f236a10b79a57854e40 2226 ola_0.9.1-1.1.dsc 015047b7a8a69b552545e5d4d93f867942c8b770 328316 ola_0.9.1-1.1.debian.tar.xz 08aa942165567b4a7086b218c650f5cb50638056 1635244 libola-dev_0.9.1-1.1_amd64.deb 5944b689902031512b986ca1ffe59f16e09c11b7 39300 ola-python_0.9.1-1.1_all.deb a15a72b76cf21a98ed06097838cb29674f13d2b0 163346 ola-rdm-tests_0.9.1-1.1_all.deb e8884a76b3a6663a2e9435b03cafb758bbcbd735 233234 ola_0.9.1-1.1_amd64.deb 713a4645687ce370d82e0155cfe77096397580c6 1315902 libola1_0.9.1-1.1_amd64.deb Checksums-Sha256: 475bc251c618572aab62ea120ca607ef09245023edc2f45ad33a17248a2ccadb 2226 ola_0.9.1-1.1.dsc cdd5b80fe90fe6e8e56995c0c59b9b9805e05b0c0ec415eee4df52334b6470fe 328316 ola_0.9.1-1.1.debian.tar.xz 63f29e67368717a41c27dee6c212a1eaaaf7f1f3d260735a4215a657d930758c 1635244 libola-dev_0.9.1-1.1_amd64.deb 83d9c6c7ec4277b3bfe7f8a4423f0a96bc1f87991be28bae6f57783cb0a32f36 39300 ola-python_0.9.1-1.1_all.deb
Bug#769670: marked as done (ola-rdm-tests: FTBFS in a sid chroot with pbuilder (no network))
Your message dated Sun, 30 Nov 2014 19:49:02 + with message-id e1xvauq-0003t6...@franck.debian.org and subject line Bug#769670: fixed in ola 0.9.1-1.1 has caused the Debian Bug report #769670, regarding ola-rdm-tests: FTBFS in a sid chroot with pbuilder (no network) 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.) -- 769670: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=769670 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: ola-rdm-tests Version: 0.9.1-1 Severity: serious Justification: fails to build from source (but built successfully in the past) Dear Maintainer, see pbuilder log below: InterfacePickerTest.cpp:67:Assertion Test name: InterfacePickerTest::testGetInterfaces assertion failed - Expression: interfaces.size() 0 Failures !!! Run: 21 Failure total: 1 Failures: 1 Errors: 0 FAIL: NetworkTester .AdvancedTCPConnectorTest.cpp:360: listening on 127.0.0.1:52114 AdvancedTCPConnectorTest.cpp:389: Connection from 127.0.0.1:58866 AdvancedTCPConnector.cpp:191: TCP Connection established to 127.0.0.1:52114 .AdvancedTCPConnectorTest.cpp:360: listening on 127.0.0.1:57687 [...] make[1]: Leaving directory '/tmp/buildd/ola-0.9.1' dh_auto_test: make -j1 check returned exit code 2 debian/rules:13: recipe for target 'build' failed make: *** [build] Error 2 dpkg-buildpackage: error: debian/rules build gave error exit status 2 E: Failed autobuilding of package -- System Information: Debian Release: jessie/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: amd64 (x86_64) Foreign Architectures: i386 i3asdf Kernel: Linux 3.16-3-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/dash ---End Message--- ---BeginMessage--- Source: ola Source-Version: 0.9.1-1.1 We believe that the bug you reported is fixed in the latest version of ola, 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 769...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Jean Baptiste Favre deb...@jbfavre.org (supplier of updated ola 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: Sun, 16 Nov 2014 17:44:18 +0100 Source: ola Binary: libola-dev ola-python ola-rdm-tests ola libola1 Architecture: source amd64 all Version: 0.9.1-1.1 Distribution: unstable Urgency: medium Maintainer: Wouter Verhelst wou...@debian.org Changed-By: Jean Baptiste Favre deb...@jbfavre.org Description: libola-dev - Open Lighting Architecture - development libraries libola1- Open Lighting Architecture - shared libraries ola- Open Lighting Architecture ola-python - Open Lighting Architecture - Python Classes ola-rdm-tests - Open Lighting Architecture - RDM Responder Tests Closes: 767676 769331 769670 Changes: ola (0.9.1-1.1) unstable; urgency=medium . * Non-maintainer upload * Remove debconf calls from ola-rdm-tests postinst (Closes: #767676) * Ship /etc/ola within ola ola-rdm-tests packages (Closes: #769331) * Add a patch which fix failing test when running in pbuilder (Closes: #769670) * Fix other important issues: - Remove the check for $RUN_DAEMON from both init scripts olad and rdm_test_server (Package maintainer disagree about this way of controling service) - Remove ola-rdm-tests postinst since its only purpose was to provide /etc/default/ola-rdm-tests - Add postrm scripts for packages ola ola-rdm-tests to fully remove configuration files so that piuparts tests can pass Checksums-Sha1: 97f86ff712790fab9d447f236a10b79a57854e40 2226 ola_0.9.1-1.1.dsc 015047b7a8a69b552545e5d4d93f867942c8b770 328316 ola_0.9.1-1.1.debian.tar.xz 08aa942165567b4a7086b218c650f5cb50638056 1635244 libola-dev_0.9.1-1.1_amd64.deb 5944b689902031512b986ca1ffe59f16e09c11b7 39300 ola-python_0.9.1-1.1_all.deb a15a72b76cf21a98ed06097838cb29674f13d2b0 163346 ola-rdm-tests_0.9.1-1.1_all.deb e8884a76b3a6663a2e9435b03cafb758bbcbd735 233234 ola_0.9.1-1.1_amd64.deb 713a4645687ce370d82e0155cfe77096397580c6 1315902 libola1_0.9.1-1.1_amd64.deb Checksums-Sha256:
Processed: Re: Bug#769947: mate-terminal: Segfaults after update
Processing control commands:
tag -1 - moreinfo
Bug #769947 {Done: Mike Gabriel sunwea...@debian.org} [mate-terminal]
mate-terminal: Segfaults after update
Removed tag(s) moreinfo.
--
769947: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=769947
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#769947: mate-terminal: Segfaults after update
Control: tag -1 - moreinfo On So 30 Nov 2014 20:30:05 CET, Mike Gabriel wrote: Thanks for testing this. I have just uploaded a new mate-terminal package version with that patch applied. removing the moreinfo tag... Mike -- DAS-NETZWERKTEAM mike gabriel, herweg 7, 24357 fleckeby fon: +49 (1520) 1976 148 GnuPG Key ID 0x25771B31 mail: mike.gabr...@das-netzwerkteam.de, http://das-netzwerkteam.de freeBusy: https://mail.das-netzwerkteam.de/freebusy/m.gabriel%40das-netzwerkteam.de.xfb pgpX8et_RH2cq.pgp Description: Digitale PGP-Signatur
Bug#771452: Copied bucket
On Sun, 30 Nov 2014, Nikolaus Rath wrote: On 11/30/2014 12:50 AM, Shannon Dealy wrote: I suspect this is because you copied the objects into a new bucket, but did not include the associated metadata. Which tool did you use to do the copy, and how did you call it? I used the AWS command line tools: aws s3 sync s3://src-bucket s3://dest-bucket It did fail part way through the transfer, so I restarted it with the same command. When you use the S3 Management Console (https://console.aws.amazon.com/s3/home) to look at the s3ql_metadata object in the original bucket and the copy, does it have the same metadata? While the s3ql_metadata file is there, in the new bucket it is missing all of the keys except the Content-Type. Not sure whether this means the fsck without cached data trashed it, or if amazon's sync was trashing the transfered data because I used it incorrectly or it is broken somehow. I think you have to blame the aws tool for this one. If you think fsck.s3ql is at fault, that's easy enough to check: just run the sync command again and see if the metadata is present before running fsck.s3ql. I don't know if that's a bug in aws, or if you're using it incorrectly, but gsutil is able to copy buckets including metadata (in case you want to try that). Poking around, it appears that the metadata was lost only on the s3ql_metadata files, so I deleted them and ran the aws s3 sync command again. The new files again were missing the metadata, so I just copied the 13 s3ql_metadata files using the aws console, and this time the metadata was preserved. I didn't see anything special about these files with regard to permissions or other information, is there anything special about how these files are created/stored on S3? If not, then possibly simply having metadata in the filename may cause the aws s3 sync command to lose the file metadata. In any case, once I replaced the s3ql_metadata files I was able to run fsck.s3ql on the copy of the file system bucket without the local data cache and it resulted in exactly the same failure mode/exception PRIMARY KEY must be unique. Will take a look at gsutil, thanks for the suggestion. FWIW. Regards, Shannon C. Dealy | DeaTech Research Inc. de...@deatech.com |- Custom Software Development - USA Phone: +1 800-467-5820 |- Natural Building Instruction - numbers : +1 541-929-4089 |www.deatech.com -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#771573: cups: Millions of symlinks to .ppd file created in /tmp
Package: cups Version: 1.7.5-5 Severity: critical Justification: breaks the whole system A few days ago, I was using my laptop at the house of a family member, and needed to print something. I clicked through the add printer dialogs (in Gnome) and the printer was detected, added, and my document printed just fine. [And let me interrupt this bug report to congratulate everyone involved. This operation used to be quite painful in the past---it's great that it can go so smoothly now.] Then, yesterday I noticed that my laptop was acting in an uncharacteristically sluggish way. There was a strange delay of several seconds between launching an application and its window first appearing. It was clear that there wasn't any excessive CPU utilization, so this felf IO related, but it wasn't obvious to me what was going on. Eventually, this morning I decided to see if a reboot would bring my system back to normal. It didn't. Instead, the system failed to boot. I was greeted with a boot message saying: a start job is running for Create Volatile files and directories This message was accompanied by a timer [ 10s / no limit ] and the timer just continued ticking off time. I let it sit for 2 or 3 minutes before giving up and deciding it was never going to boot. I duckduckgo'ed the message and found the following Debian forum threads from last month: http://forums.debian.net/viewtopic.php?f=10t=118008 I was able to at least boot to a shell by editing my linux option within grub, changing ro to rw init=/bin/bash. At this point I could investigate /tmp, where I found over 6 million symlinks of apparently automatically-generated hexadecimal digits, all linking to the same .ppd file. The target of these symlinks had the same name as the printer model which I had added a few days ago. I successfully got my system to reboot again after deleting all of the symlinks: cd /tmp find . -name '5477*' | xargs rm On the next reboot the a start job is running for Create Volatile files and directories did pause and count up for a few seconds, (perhaps 4 or 5), but then proceeded to boot. I went into the printer settings and deleted the printer, (I'm no longer at that family-member's house and shouldn't need to print to that queue again any time soon). I've also verified that /tmp/ now only contains a single symlink to a .ppd file, (corresponding to the one remaining print queue that I do use on a regular basis). So I still don't know much about what process went wild and created millions of symlinks, but it's definitely a bug that can result in some pretty painful side effects. I looked through the bugs in cups and didn't see any talking about symlinks or /tmp so I hope this isn't a duplicate bug entry. If the bug is known to be fixed in subsequent versions, that will be great to know. If not, if there is anything I can do to debug further, I will be happy to do so. (If I had noticed the errant process creating the many symlinks while my systerm was still usable, then I certainly could have done some more investigation.) Please let me know what further information I might be able to provide that would be useful. Thanks, -Carl -- System Information: Debian Release: jessie/sid APT prefers unstable APT policy: (500, 'unstable'), (500, 'oldstable'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.16-3-amd64 (SMP w/4 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages cups depends on: ii cups-client1.7.5-5 ii cups-common1.7.5-5 ii cups-core-drivers 1.7.5-5 ii cups-daemon1.7.5-5 ii cups-filters 1.0.61-2 ii cups-ppdc 1.7.5-5 ii cups-server-common 1.7.5-5 ii debconf [debconf-2.0] 1.5.53 ii ghostscript9.06~dfsg-1.1+b1 ii libavahi-client3 0.6.31-4 ii libavahi-common3 0.6.31-4 ii libc-bin 2.19-11 ii libc6 2.19-11 ii libcups2 1.7.5-5 ii libcupscgi11.7.5-5 ii libcupsimage2 1.7.5-5 ii libcupsmime1 1.7.5-5 ii libcupsppdc1 1.7.5-5 ii libgcc11:4.9.1-18 ii libstdc++6 4.9.1-18 ii libusb-1.0-0 2:1.0.19-1 ii lsb-base 4.1+Debian13+nmu1 ii poppler-utils 0.26.5-2 ii procps 2:3.3.9-8 Versions of packages cups recommends: ii avahi-daemon 0.6.31-4 ii colord 1.2.1-1+b1 ii cups-filters [ghostscript-cups] 1.0.61-2 ii printer-driver-gutenprint5.2.10-3 Versions of packages cups suggests: pn cups-bsd none ii cups-pdf 2.6.1-14 ii foomatic-db-compressed-ppds [foomatic-db] 20141016-1 ii hplip 3.14.6-1+b1 ii printer-driver-cups-pdf [cups-pdf]
Bug#771341: Bug#771549: fail2ban: init script refuses to start after a crash
On Sun, 30 Nov 2014, Frédéric Brière wrote: Package: fail2ban Version: 0.9.1-1 Severity: normal I've had fail2ban segfaulting yesterday (in libsqlite3; probably not worth a bug report, since I couldn't reproduce it). Anyway, fail2ban is no longer running[*], so let's restart it: Hi Frédéric, yeah -- thanks for filing and confirming the issue on a sid box -- segfault issue is known to fail2ban upstream https://github.com/fail2ban/fail2ban/issues/844 and I have reported it against sqlite3 in debian (CCed with this as a confirmation of replication on sid): https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=771341 There is some anecdotal evidence that recently merged upstream https://github.com/fail2ban/fail2ban/pull/839 might somehow be a workaround for the segfault. # service fail2ban start [] Starting authentication failure monitor: fail2ban[] Socket file /var/[FAILail2ban/fail2ban.sock is present ... failed! failed! Yeah, I doubt it had the occasion to remove the socked file before segfaulting. Nevertheless, the process is no longer running: # kill -0 `cat /var/run/fail2ban/fail2ban.pid` bash: kill: (24147) - No such process Shouldn't the init script automatically ignore/remove the socket file if the process in the PID file is no longer running? Isn't that what PID files are for? This is probably the first time I remember having to manually do something before restarting a server after a simple crash. [*] Maybe this wouldn't be a problem if I was running systemd? :) this was intended as a feature -- fail2ban was so stable that abnormal crash, leaving pid/socket behind, was treated as a warning sign that something went really wrong and it requires admin attention to troubleshoot/fix configuration etc. There is a 'force-start' command you could use to consciously ignore the fact that fail2ban has crashed. -- Yaroslav O. Halchenko, Ph.D. http://neuro.debian.net http://www.pymvpa.org http://www.fail2ban.org Research Scientist,Psychological and Brain Sciences Dept. Dartmouth College, 419 Moore Hall, Hinman Box 6207, Hanover, NH 03755 Phone: +1 (603) 646-9834 Fax: +1 (603) 646-1419 WWW: http://www.linkedin.com/in/yarik -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#771561: closed by Ben Hutchings b...@decadent.org.uk (Re: systemd package is missing dependency on Linux kernel (linux-image?))
What course of action would do propose to ensure that systemd is always upgraded in lockstep with the kernel version? Maybe have a versioned ”Breaks” entry for systemd regarding older Linux kernel versions? -- Nils Dagsson Moskopp // erlehmann http://dieweltistgarnichtso.net pgpnhyTuGSU3K.pgp Description: PGP signature
Processed: severity of 771561 is wishlist
Processing commands for cont...@bugs.debian.org:
severity 771561 wishlist
Bug #771561 {Done: Ben Hutchings b...@decadent.org.uk} [systemd] systemd
package is missing dependency on Linux kernel (linux-image?)
Severity set to 'wishlist' from 'serious'
thanks
Stopping processing here.
Please contact me if you need assistance.
--
771561: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=771561
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#771561: systemd: please remove /etc/fstab from bug report
Am 30.11.2014 um 20:16 schrieb Nils Dagsson Moskopp: Package: systemd Version: 204-8 Followup-For: Bug #771561 Dear Maintainer, This bug contains the contents of my /etc/fstab. I was never asked for this. I already found bug #743158. “We don't know, so assume yes.” is not consent. You are asked, here is the complete text: Providing additional information can help diagnose problems with systemd. Specifically, this would include: - fstab configuration (copy of /etc/fstab). - local modifications of unit files (output of systemd-delta). - state of running services and units (output of systemd-analzye dump). - enabled/disabled state of installed services. If this information is not relevant for your bug report or you have privacy concerns, please choose no. I think this should address the concern sufficiently. This question was added as part of 215-3. -- 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#771561: closed by Ben Hutchings b...@decadent.org.uk (Re: systemd package is missing dependency on Linux kernel (linux-image?))
2014-11-30 21:01 GMT+01:00 Nils Dagsson Moskopp n...@dieweltistgarnichtso.net: What course of action would do propose to ensure that systemd is always upgraded in lockstep with the kernel version? Maybe have a versioned ”Breaks” entry for systemd regarding older Linux kernel versions? Unfortunately, you can't ensure that - people might still boot an older kernel, or compile their own kernel and run that instead of what we ship with Debian. The best thing would IMHO be a check in systemd to abort boot with a meaningful message in case an unsupported (= too old) kernel is used. Also, the systemd package can only be updated if the kernel providing features it needs is set as default (this still wound't solve the case of partial upgrades though). Cheers, Matthias -- I welcome VSRE emails. See http://vsre.info/ -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#770648: hiredis: FTBFS: Test failure
D'oh :) There I go making assumptions. All the same, I feel like we can argue back and forth about the severity of this issue but we've got a potential fix ready to go. Might as well get the release team involved -- if we can arrange an unblock the whole issue is moot. On Sun, Nov 30, 2014 at 11:00 AM, gregor herrmann gre...@debian.org wrote: On Sun, 30 Nov 2014 10:51:56 -0800, Tom Lee wrote: Talked this over with the release team on #debian-release, Except that noone who responded is a member of the release team :) Cheers, gregor -- .''`. Homepage: http://info.comodo.priv.at/ - OpenPGP key 0xBB3A68018649AA06 : :' : Debian GNU/Linux user, admin, and developer - http://www.debian.org/ `. `' Member of VIBE!AT SPI, fellow of the Free Software Foundation Europe `- NP: Cat Stevens: I Love My Dog -BEGIN PGP SIGNATURE- Version: GnuPG v1 iQJ8BAEBCgBmBQJUe2l0XxSAAC4AKGlzc3Vlci1mcHJAbm90YXRpb25zLm9w ZW5wZ3AuZmlmdGhob3JzZW1hbi5uZXREMUUxMzE2RTkzQTc2MEE4MTA0RDg1RkFC QjNBNjgwMTg2NDlBQTA2AAoJELs6aAGGSaoGscoQAJIK0qNAR4/HTYvVRo7barIC ZK9EombbjP8kK+iNoX2lAhDhawJgwEJ7fUOWtcjG4rjamYsSGI9HKB9abu7Brqhb nap+NS5NKFctfdQP2zSn9AXpu8TWwzdC73a5BOAs3Msr6T2BHcKX+e8xcdXj77xc FFtvcPUcFLzBtCxZA+wBrWWvPn+ZJAVIKhcoxf/85JFpfmbGyjHdwiwq9XoTgfHu f5esudD3UjSzYYDpMf1fgWbdfG3E1CDmbfNsuBMAmnp4TUUGlL5MiaFjIMggBk/f M8K9TuLah/I8/kTLNfoWjQ74+q6WJI3GySXPpHdmHny+wltY92gs0d7mea3pzov/ UiIMGUpO5kwX6CwL3mN9wFkhSbjEy6kBrUTBnDgXsH2ktGjn6bbjnDl8Tn++Idnz iLfDVStzlDtihg12zxT2gthoiFx7YcYFOlQSo6wxwDoOFUM0zJmuv1rov919UaQ4 5GJhHD4CWG1oFEn/s/7z+aOrjb39X2cF1OQa8FzqYTnmBTd+vwSLNNP4S2ipOKJU hTWb6cov7xpZwdxZJfOCzWX3PJEuxDHZZjLHWQy0QNdkeEJouEe6edMdb//tYQEk vDCplr7xZfcVbJ2ALz0uiKWyOaP48AB0r8MED7T1e8qwxEBp1LqS1AQA87NNsNgA G0q+Hrl4KbKUVI8I2RDO =6Enz -END PGP SIGNATURE- -- *Tom Lee */ http://tomlee.co / @tglee http://twitter.com/tglee
Bug#770390: marked as done (Crash with SIGSEGV in `e_alert_response`)
Your message dated Sun, 30 Nov 2014 21:21:38 + with message-id e1xvbw2-0007zg...@franck.debian.org and subject line Bug#770390: fixed in evolution 3.12.9~git20141130.241663-1 has caused the Debian Bug report #770390, regarding Crash with SIGSEGV in `e_alert_response` 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.) -- 770390: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=770390 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: evolution Version: 3.12.7-1 Severity: grave Tags: upstream fixed-upstream Control: forwarded -1 https://bugzilla.gnome.org/show_bug.cgi?id=739605 Dear Debian folks, Evolution crashes frequently with a segmentation fault. Program received signal SIGSEGV, Segmentation fault. 0xb7db5ef3 in e_alert_response (alert=0x891a9e70, response_id=-7) at e-alert.c:945 The issue has been fixed upstream, so it’d be great if the commit c0d144b (Remove alert buttons on the alert bar hide) [1] could be applied to the Debian version or if Evolution 3.12.8 could be included in Debian. Thanks, Paul [1] https://git.gnome.org/browse/evolution/commit/?id=c0d144b -- System Information: Debian Release: jessie/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: i386 (i686) Kernel: Linux 3.16.0-4-686-pae (SMP w/2 CPU cores) Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash Versions of packages evolution depends on: ii dbus 1.8.10-1+auth1 ii debconf [debconf-2.0] 1.5.53 ii evolution-common 3.12.7-1 ii evolution-data-server 3.12.7.1-2 ii gnome-icon-theme 3.12.0-1 ii libatk1.0-02.14.0-1 ii libc6 2.19-13 ii libcamel-1.2-493.12.7.1-2 ii libclutter-gtk-1.0-0 1.6.0-1 ii libecal-1.2-16 3.12.7.1-2 ii libedataserver-1.2-18 3.12.7.1-2 ii libevolution 3.12.7-1 ii libglib2.0-0 2.42.1-1 ii libgtk-3-0 3.14.5-1 ii libical1 1.0-1.1 ii libnotify4 0.7.6-2 ii libsoup2.4-1 2.48.0-1 ii libwebkitgtk-3.0-0 2.4.7-2 ii libxml22.9.2+dfsg1-1 ii psmisc 22.21-2 Versions of packages evolution recommends: ii bogofilter 1.2.4+dfsg1-3 ii evolution-plugins 3.12.7-1 ii spamassassin 3.4.0-3 ii yelp 3.14.1-1 Versions of packages evolution suggests: pn evolution-ews none ii evolution-plugins-experimental 3.12.7-1 ii gnupg 1.4.18-4 ii network-manager 0.9.10.0-3 -- debconf information excluded signature.asc Description: This is a digitally signed message part ---End Message--- ---BeginMessage--- Source: evolution Source-Version: 3.12.9~git20141130.241663-1 We believe that the bug you reported is fixed in the latest version of evolution, 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 770...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Josselin Mouette j...@debian.org (supplier of updated evolution 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: Sun, 30 Nov 2014 19:08:57 +0100 Source: evolution Binary: evolution libevolution evolution-common evolution-dev evolution-dbg evolution-plugins evolution-plugins-experimental Architecture: source all amd64 Version: 3.12.9~git20141130.241663-1 Distribution: unstable Urgency: medium Maintainer: Debian Evolution Maintainers pkg-evolution-maintain...@lists.alioth.debian.org Changed-By: Josselin Mouette j...@debian.org Description: evolution - groupware suite with mail client and organizer evolution-common - architecture independent files for Evolution evolution-dbg - debugging symbols for Evolution evolution-dev - development library files for Evolution evolution-plugins - standard plugins for Evolution evolution-plugins-experimental - experimental plugins for Evolution libevolution - evolution libraries Closes: 770390 Changes: evolution (3.12.9~git20141130.241663-1) unstable; urgency=medium . * New upstream git snapshot from stable branch, includes only bugfixes and
Bug#770648: hiredis: FTBFS: Test failure
Rather than add to the overhead of getting this change accepted, I'm going
to roll back the DEB_BUILD_OPTS=nocheck change given it's unrelated to this
bug (per the freeze policy
https://release.debian.org/jessie/freeze_policy.html). I'll roll it back in
after the freeze.
Proposed change to 0.11.0-4 looks like this:
$ debdiff ~/Source/hiredis_0.11.0-4.dsc ../hiredis_0.11.0-5.dsc
gpgv: Signature made Sun 30 Nov 2014 01:12:44 PM PST using RSA key ID
6C6608D1
gpgv: Can't check signature: public key not found
dpkg-source: warning: failed to verify signature on
/home/tom/Source/debian/hiredis_0.11.0-5.dsc
diff -Nru hiredis-0.11.0/debian/changelog hiredis-0.11.0/debian/changelog
--- hiredis-0.11.0/debian/changelog 2014-10-03 20:30:13.0 -0700
+++ hiredis-0.11.0/debian/changelog 2014-11-30 13:09:15.0 -0800
@@ -1,3 +1,9 @@
+hiredis (0.11.0-5) unstable; urgency=medium
+
+ * Disable a network test failing in pbuilder (closes: #770648)
+
+ -- Tom Lee deb...@tomlee.co Mon, 24 Nov 2014 00:17:31 -0800
+
hiredis (0.11.0-4) unstable; urgency=medium
* Symlinks for cmake 3.0 (closes: #758548)
diff -Nru hiredis-0.11.0/debian/patches/04_disable-network-tests.patch
hiredis-0.11.0/debian/patches/04_disable-network-tests.patch
--- hiredis-0.11.0/debian/patches/04_disable-network-tests.patch
1969-12-31 16:00:00.0 -0800
+++ hiredis-0.11.0/debian/patches/04_disable-network-tests.patch
2014-11-29 22:36:40.0 -0800
@@ -0,0 +1,25 @@
+Description: Disable Returns error when host cannot be resolved
+ This patch disables a test that relies on the presence of a
+ network connection.
+Author: Tobias Frost t...@debian.org
+---
+This patch header follows DEP-3: http://dep.debian.net/deps/dep3/
+--- a/test.c
b/test.c
+@@ -282,12 +282,16 @@
+ static void test_blocking_connection_errors(void) {
+ redisContext *c;
+
++#if 0
+ test(Returns error when host cannot be resolved: );
+ c = redisConnect((char*)idontexist.local, 6379);
+ test_cond(c-err == REDIS_ERR_OTHER
+ (strcmp(c-errstr,Name or service not known) == 0 ||
+ strcmp(c-errstr,Can't resolve: idontexist.local) == 0));
+ redisFree(c);
++#else
++test(SKIPPED: Returns error when host cannot be resolved\n);
++#endif
+
+ /*test(Returns error when the port is not open: );
+ c = redisConnect((char*)localhost, 1);
diff -Nru hiredis-0.11.0/debian/patches/series
hiredis-0.11.0/debian/patches/series
--- hiredis-0.11.0/debian/patches/series2014-10-03
20:30:13.0 -0700
+++ hiredis-0.11.0/debian/patches/series2014-11-24
00:11:32.0 -0800
@@ -1,3 +1,4 @@
01_use-proper-destdir.patch
02_disable-failing-test.patch
03_pkgconfig-cmake.patch
+04_disable-network-tests.patch
On Sun, Nov 30, 2014 at 12:59 PM, Tom Lee deb...@tomlee.co wrote:
D'oh :) There I go making assumptions.
All the same, I feel like we can argue back and forth about the severity
of this issue but we've got a potential fix ready to go. Might as well get
the release team involved -- if we can arrange an unblock the whole issue
is moot.
On Sun, Nov 30, 2014 at 11:00 AM, gregor herrmann gre...@debian.org
wrote:
On Sun, 30 Nov 2014 10:51:56 -0800, Tom Lee wrote:
Talked this over with the release team on #debian-release,
Except that noone who responded is a member of the release team :)
Cheers,
gregor
--
.''`. Homepage: http://info.comodo.priv.at/ - OpenPGP key
0xBB3A68018649AA06
: :' : Debian GNU/Linux user, admin, and developer -
http://www.debian.org/
`. `' Member of VIBE!AT SPI, fellow of the Free Software Foundation
Europe
`- NP: Cat Stevens: I Love My Dog
-BEGIN PGP SIGNATURE-
Version: GnuPG v1
iQJ8BAEBCgBmBQJUe2l0XxSAAC4AKGlzc3Vlci1mcHJAbm90YXRpb25zLm9w
ZW5wZ3AuZmlmdGhob3JzZW1hbi5uZXREMUUxMzE2RTkzQTc2MEE4MTA0RDg1RkFC
QjNBNjgwMTg2NDlBQTA2AAoJELs6aAGGSaoGscoQAJIK0qNAR4/HTYvVRo7barIC
ZK9EombbjP8kK+iNoX2lAhDhawJgwEJ7fUOWtcjG4rjamYsSGI9HKB9abu7Brqhb
nap+NS5NKFctfdQP2zSn9AXpu8TWwzdC73a5BOAs3Msr6T2BHcKX+e8xcdXj77xc
FFtvcPUcFLzBtCxZA+wBrWWvPn+ZJAVIKhcoxf/85JFpfmbGyjHdwiwq9XoTgfHu
f5esudD3UjSzYYDpMf1fgWbdfG3E1CDmbfNsuBMAmnp4TUUGlL5MiaFjIMggBk/f
M8K9TuLah/I8/kTLNfoWjQ74+q6WJI3GySXPpHdmHny+wltY92gs0d7mea3pzov/
UiIMGUpO5kwX6CwL3mN9wFkhSbjEy6kBrUTBnDgXsH2ktGjn6bbjnDl8Tn++Idnz
iLfDVStzlDtihg12zxT2gthoiFx7YcYFOlQSo6wxwDoOFUM0zJmuv1rov919UaQ4
5GJhHD4CWG1oFEn/s/7z+aOrjb39X2cF1OQa8FzqYTnmBTd+vwSLNNP4S2ipOKJU
hTWb6cov7xpZwdxZJfOCzWX3PJEuxDHZZjLHWQy0QNdkeEJouEe6edMdb//tYQEk
vDCplr7xZfcVbJ2ALz0uiKWyOaP48AB0r8MED7T1e8qwxEBp1LqS1AQA87NNsNgA
G0q+Hrl4KbKUVI8I2RDO
=6Enz
-END PGP SIGNATURE-
--
*Tom Lee */ http://tomlee.co / @tglee http://twitter.com/tglee
--
*Tom Lee */ http://tomlee.co / @tglee http://twitter.com/tglee
Bug#769791: wine32 doesn't work after fresh install
control: forcemerge 771104 -1 On Sun, Nov 16, 2014 at 8:38 AM, Andreas Barth wrote: wine32 doesn't start anymore after upgrade with a clean directory. This is a duplicate of #739863 which had been closed in wine-unstable which had been removed from unstable afterwards, so this bug is present in testing. I did a clean install, and found wine not working as described, but the root cause is #771104 (some missing i386 dependencies), not #739863. Best wishes, Mike -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed (with 1 errors): Re: Bug#769791: wine32 doesn't work after fresh install
Processing control commands: forcemerge 771104 -1 Bug #771104 [wine] [wine] wine is no more usable Bug #769473 [wine] wine: starts in a tiny and inoperable window Unable to merge bugs because: package of #769791 is 'wine32' not 'wine' Failed to forcibly merge 771104: Did not alter merged bugs -- 769473: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=769473 769791: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=769791 771104: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=771104 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#770648: hiredis: FTBFS: Test failure
On Sun, Nov 30, 2014 at 07:17:46PM +0100, gregor herrmann wrote: On Sun, 30 Nov 2014 17:36:04 +0100, Alessandro Ghedini wrote: On dom, nov 30, 2014 at 03:06:55 +0100, Tobias Frost wrote: Am Sonntag, den 30.11.2014, 00:21 -0800 schrieb Tom Lee: Also, I feel like the serious severity is overstating the issue given that 0.11.0-4 builds fine in buildd/sbuild. Alessandro pointed out the periodic rebuilds would have revealed this issue otherwise. If there are no objections I'd like to propose we adjust the severity of this bug to normal leave the fix for this particular bug until after the Jessie freeze. Here I can reprodcue the FTBFS locally with pbuilder 0.215+nmu3, so I disagree. It maybe has not been detected *yet*? What does this yet even mean? Except inside pbuilder, hiredis builds fine [1]. The fact that it fails *only* inside pbuilder (and the fact that hiredis is not the only package in this situation) suggests that this is indeed a pbuilder bug. I really don't see how this is release critical in any way on the part of the hiredis package. While I tend to agree in general, here's an additional data point: I rebuilt 0.11.0-4 in my sid amd64 cowbuilder chroot, which has USENETWORK=yes (due to #753944) but firewalls off everything except localhost during build. And in this environment I see a test failure: Ok, so I think the whole problem is that /etc/resolv.conf lists non-local name servers, but the build environment can't actually reach them (because of USENETWORK=no or the firewall). This is, I think, the exact same problem as #759799 (which is btw severity: important). If the consensus is that this should be fixed in the affected packages (e.g. by disabling the tests), I'm all for it, but I really think that the effort should go into fixing pbuilder, since who knows how many packages are actually affected by this. A simple and stupid solution would be to turn off DNS name lookups completely inside the build environment if USENETWORK=no (e.g. by fiddling with /etc/nsswitch.conf), but I'm not sure if that's really applicable to pbuilder. Not sure what the best way forward is; adding a test for Temporary failure in name resolution might be an option (and works unsurprisingly): #v+ --- a/test.c +++ b/test.c @@ -286,7 +286,8 @@ c = redisConnect((char*)idontexist.local, 6379); test_cond(c-err == REDIS_ERR_OTHER (strcmp(c-errstr,Name or service not known) == 0 || - strcmp(c-errstr,Can't resolve: idontexist.local) == 0)); + strcmp(c-errstr,Can't resolve: idontexist.local) == 0 || + strcmp(c-errstr,Temporary failure in name resolution) == 0)); redisFree(c); /*test(Returns error when the port is not open: ); #v- But maybe there are better ways to fix this. That would make the test kinda useless, but I guess it's no worse than disabling it completely. Cheers signature.asc Description: Digital signature
Bug#759935: marked as done (bluefish: FTBFS: *** error: gettext infrastructure mismatch: using a Makefile.in.in from gettext version 0.18 but the autoconf macros are from gettext version 0.19)
Your message dated Sun, 30 Nov 2014 21:49:13 + with message-id e1xvcmj-000335...@franck.debian.org and subject line Bug#759935: fixed in bluefish 2.2.6-2 has caused the Debian Bug report #759935, regarding bluefish: FTBFS: *** error: gettext infrastructure mismatch: using a Makefile.in.in from gettext version 0.18 but the autoconf macros are from gettext version 0.19 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.) -- 759935: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=759935 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Source: bluefish Version: 2.2.6-1 Severity: serious Tags: jessie sid User: debian...@lists.debian.org Usertags: qa-ftbfs-20140830 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): make[5]: Entering directory '/«PKGBUILDDIR»/src/plugin_about' Making all in po make[6]: Entering directory '/«PKGBUILDDIR»/src/plugin_about/po' *** error: gettext infrastructure mismatch: using a Makefile.in.in from gettext version 0.18 but the autoconf macros are from gettext version 0.19 Makefile:120: recipe for target 'check-macro-version' failed make[6]: *** [check-macro-version] Error 1 The full build log is available from: http://aws-logs.debian.net/ftbfs-logs/2014/08/30/bluefish_2.2.6-1_unstable.log A list of current common problems and possible solutions is available at http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute! About the archive rebuild: The rebuild was done on EC2 VM instances from Amazon Web Services, using a clean, minimal and up-to-date chroot. Every failed build was retried once to eliminate random failures. The build was done with DEB_BUILD_OPTIONS=parallel=4, so if your packaging tries to support this, it might be a good idea to explore whether this might be the cause of the failure. ---End Message--- ---BeginMessage--- Source: bluefish Source-Version: 2.2.6-2 We believe that the bug you reported is fixed in the latest version of bluefish, 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 759...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Daniel Leidert dleid...@debian.org (supplier of updated bluefish package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Sat, 29 Nov 2014 20:32:08 +0100 Source: bluefish Binary: bluefish bluefish-plugins bluefish-data bluefish-dbg Architecture: source amd64 all Version: 2.2.6-2 Distribution: unstable Urgency: medium Maintainer: Daniel Leidert dleid...@debian.org Changed-By: Daniel Leidert dleid...@debian.org Description: bluefish - advanced Gtk+ text editor for web and software development bluefish-data - advanced Gtk+ text editor (data) bluefish-dbg - advanced Gtk+ text editor (debugging symbols) bluefish-plugins - advanced Gtk+ text editor (plugins) Closes: 747963 752234 759935 Changes: bluefish (2.2.6-2) unstable; urgency=medium . * debian/rules: Added override_dh_autoreconf target and run the upstream autogen.sh script to fix the FTBFS reported in #759935. * debian/patches/747963_fix_conflicting_declarations.patch: Added. - Fixed a conflicting function declaration (closes: #747963). * debian/patches/752234_fix_chromium_command.patch: Added. - Fixed chromium command (closes: #752234). * debian/patches/759935_autogen.patch: Added. - Added the autogen.sh script from upstream (closes: #759935). Checksums-Sha1: 95397104f8688d18e920250670dea171e4df1346 2296 bluefish_2.2.6-2.dsc 9cc0c27549f3c6786baa72a920830a8f7b905161 23100 bluefish_2.2.6-2.debian.tar.xz 5a3becf59710e63d808636049898782434f3ea21 267810 bluefish_2.2.6-2_amd64.deb 668d33c65e09db6b6c26b9446cfc1d2c6ea08f39 187640 bluefish-plugins_2.2.6-2_amd64.deb 0e9c0c6329c1b9be59616236a6f12b6a98d3af09 2183482 bluefish-data_2.2.6-2_all.deb 89f6ee6c0ce868815f85f6eceaea86c947de4f7b 850750 bluefish-dbg_2.2.6-2_amd64.deb Checksums-Sha256: 3b98270819fdc366b083d946558f94d45f51852aa9a4bfc9367e1691f522c05d 2296 bluefish_2.2.6-2.dsc 684ab39942a562bbe2594d220dbe7cdd0c1e9fa9d95e650267808652f25bb120 23100
Processed: your mail
Processing commands for cont...@bugs.debian.org: reassign 769791 wine Bug #769791 [wine32] wine32 doesn't work after fresh install Bug reassigned from package 'wine32' to 'wine'. No longer marked as found in versions wine/1.6.2-16. Ignoring request to alter fixed versions of bug #769791 to the same values previously set forcemerge 771104 769791 Bug #771104 [wine] [wine] wine is no more usable Bug #769473 [wine] wine: starts in a tiny and inoperable window Bug #769791 [wine] wine32 doesn't work after fresh install Severity set to 'grave' from 'serious' Marked as found in versions wine/1.6.2-16. Bug #769473 [wine] wine: starts in a tiny and inoperable window Merged 769473 769791 771104 thanks Stopping processing here. Please contact me if you need assistance. -- 769473: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=769473 769791: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=769791 771104: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=771104 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#770648: hiredis: FTBFS: Test failure
On Sun, Nov 30, 2014 at 1:31 PM, Alessandro Ghedini gh...@debian.org wrote: This is, I think, the exact same problem as #759799 (which is btw severity: important). If the consensus is that this should be fixed in the affected packages (e.g. by disabling the tests), I'm all for it, but I really think that the effort should go into fixing pbuilder, since who knows how many packages are actually affected by this. Agreed, but I'm going to get the release team involved to get this sorted out given hiredis has been flagged for auto-removal in Jessie as a result of this bug. Specifically, I'm requesting an unblock for 0.11.0-5 alongside a request for clarification RE: the severity of this bug. I suspect they're going to need to see 0.11.0-5 in unstable to make the unblock happen, but if you like we can wait for them to comment on the unblock request. Not sure what the best way forward is; adding a test for Temporary failure in name resolution might be an option (and works unsurprisingly): #v+ --- a/test.c +++ b/test.c @@ -286,7 +286,8 @@ c = redisConnect((char*)idontexist.local, 6379); test_cond(c-err == REDIS_ERR_OTHER (strcmp(c-errstr,Name or service not known) == 0 || - strcmp(c-errstr,Can't resolve: idontexist.local) == 0)); + strcmp(c-errstr,Can't resolve: idontexist.local) == 0 || + strcmp(c-errstr,Temporary failure in name resolution) == 0)); redisFree(c); /*test(Returns error when the port is not open: ); #v- But maybe there are better ways to fix this. That would make the test kinda useless, but I guess it's no worse than disabling it completely. I don't mind this approach if we call out the fact the test was skipped rather than silently passed, but at that point it's providing the same value as a test that's been completely disabled ... keeping Tobias' original patch for now. -- *Tom Lee */ http://tomlee.co / @tglee http://twitter.com/tglee
Bug#769216: fixed in django-guardian 1.2.4+git20141127-0.1
On 29 November 2014 at 20:06, Ivo De Decker iv...@debian.org wrote: * Fix test errors. Closes: #769216. It looks like you closed the wrong bug. You probably meant #763222 Yes, it does look like I stuffed up; apologies:-( Thanks for fixing this up. -- Brian May b...@debian.org
Bug#770648: hiredis: FTBFS: Test failure
On Sun, 30 Nov 2014 22:31:20 +0100, Alessandro Ghedini wrote: On Sun, Nov 30, 2014 at 07:17:46PM +0100, gregor herrmann wrote: On Sun, 30 Nov 2014 17:36:04 +0100, Alessandro Ghedini wrote: What does this yet even mean? Except inside pbuilder, hiredis builds fine [1]. The fact that it fails *only* inside pbuilder (and the fact that hiredis is not the only package in this situation) suggests that this is indeed a pbuilder bug. I really don't see how this is release critical in any way on the part of the hiredis package. While I tend to agree in general, here's an additional data point: I rebuilt 0.11.0-4 in my sid amd64 cowbuilder chroot, which has USENETWORK=yes (due to #753944) but firewalls off everything except localhost during build. And in this environment I see a test failure: Ok, so I think the whole problem is that /etc/resolv.conf lists non-local name servers, but the build environment can't actually reach them (because of USENETWORK=no or the firewall). Sounds plausible. That fact that pbuilder copies /etc/resolv.conf into the chroot each time also does not help :/ This is, I think, the exact same problem as #759799 (which is btw severity: important). If the consensus is that this should be fixed in the affected packages (e.g. by disabling the tests), I'm all for it, but I really think that the effort should go into fixing pbuilder, since who knows how many packages are actually affected by this. I don't know how many packages are affected but it's not the first time I've seen questions around USENETWORK= coming up in recent bug reports. - #769670 being one of them e.g. A simple and stupid solution would be to turn off DNS name lookups completely inside the build environment if USENETWORK=no (e.g. by fiddling with /etc/nsswitch.conf), but I'm not sure if that's really applicable to pbuilder. Hm, don't know :) But this should go into #753944 anyway. (CC'd) Cheers, gregor -- .''`. Homepage: http://info.comodo.priv.at/ - OpenPGP key 0xBB3A68018649AA06 : :' : Debian GNU/Linux user, admin, and developer - http://www.debian.org/ `. `' Member of VIBE!AT SPI, fellow of the Free Software Foundation Europe `- NP: Rolling Stones: Sleepy signature.asc Description: Digital Signature
Bug#770648: Bug#753944: Bug#770648: hiredis: FTBFS: Test failure
gregor herrmann dixit: That fact that pbuilder copies /etc/resolv.conf into the chroot each time also does not help :/ Ouch. How about if USENETWORK=no then CHROOT/etc/resolv.conf is created with values sane for that? Can you do the NMU? A simple and stupid solution would be to turn off DNS name lookups completely inside the build environment if USENETWORK=no (e.g. by fiddling with /etc/nsswitch.conf), but I'm not sure if that's really applicable to pbuilder. Hm, don't know :) Good question. Maybe it should *also* generate a sane nsswitch.conf because the one from the host system is not normally applicable (but idk if it copies that as well). But IMHO it definitely should not blindly copy resolv.conf. bye, //mirabilos -- “Having a smoking section in a restaurant is like having a peeing section in a swimming pool.” -- Edward Burr -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#771213: [debian-mysql] Bug#771213: mariadb-server-10.0: file conflict with mysql-client-5.5
Thanks for reporting this! I mysql-5.5/5.6 the mysql_plugin is part of the client package: mysql-client-5.6.install:usr/bin/mysql_plugin mysql-client-5.6.manpages:debian/tmp/usr/share/man/man1/mysql_plugin.1 In MariaDB it is part of server package: mariadb-server-10.0.install:usr/bin/mysql_plugin mariadb-server-10.0.manpages:debian/tmp/usr/share/man/man1/mysql_plugin.1 As this command controls what plugins the server loads, I think the proper location indeed is in the server package (as upstream did) and I will not change it, instead I added breaks/replaces to overwrite file ( https://www.debian.org/doc/debian-policy/ch-relationships.html#s7.6.1) in commit http://anonscm.debian.org/cgit/pkg-mysql/mariadb-10.0.git/commit/?id=7bda76751754145a66239c8f9fd343d47fd1c1b0 This fix will be uploaded once 10.0.15 it is finalized for Debian.
Bug#770648: Bug#753944: Bug#770648: hiredis: FTBFS: Test failure
On Sun, 30 Nov 2014 22:23:13 +, Thorsten Glaser wrote: gregor herrmann dixit: That fact that pbuilder copies /etc/resolv.conf into the chroot each time also does not help :/ Ouch. How about if USENETWORK=no then CHROOT/etc/resolv.conf is created with values sane for that? Can you do the NMU? What would these sane values be? A simple and stupid solution would be to turn off DNS name lookups completely inside the build environment if USENETWORK=no (e.g. by fiddling with /etc/nsswitch.conf), but I'm not sure if that's really applicable to pbuilder. Hm, don't know :) Good question. Maybe it should *also* generate a sane nsswitch.conf because the one from the host system is not normally applicable (but idk if it copies that as well). But IMHO it definitely should not blindly copy resolv.conf. Looks like /etc/nsswitch.conf is not copied (i.e. if I change it in the host system and enter the chroot, the changes are not there). Cheers, gregor -- .''`. Homepage: http://info.comodo.priv.at/ - OpenPGP key 0xBB3A68018649AA06 : :' : Debian GNU/Linux user, admin, and developer - http://www.debian.org/ `. `' Member of VIBE!AT SPI, fellow of the Free Software Foundation Europe `- NP: Beatles signature.asc Description: Digital Signature
Bug#768741: marked as done (phlipple: FTBFS in jessie: ld: engine.o: undefined reference to symbol 'cos@@GLIBC_2.2.5')
Your message dated Sun, 30 Nov 2014 22:36:26 + with message-id e1xvd6q-0002yh...@franck.debian.org and subject line Bug#768741: fixed in phlipple 0.8.5-2 has caused the Debian Bug report #768741, regarding phlipple: FTBFS in jessie: ld: engine.o: undefined reference to symbol 'cos@@GLIBC_2.2.5' to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 768741: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=768741 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Source: phlipple Version: 0.8.5-1 Severity: serious Tags: jessie sid User: debian...@lists.debian.org Usertags: qa-ftbfs-20141108 qa-ftbfs Justification: FTBFS in jessie on amd64 Hi, During a rebuild of all packages in jessie (in a jessie chroot, not a sid chroot), your package failed to build on amd64. Relevant part (hopefully): gcc -std=gnu99 -Wall -g -g -O2 -fstack-protector-strong -Wformat -Werror=format-security -D_FORTIFY_SOURCE=2 -Wl,-z,relro -Wl,-z,defs -Wl,-as-needed -Wl,--no-undefined -o phlipple camera.o engine.o game.o gfxconstants.o gradientrenderer.o interpolator.o levels.o main.o mainscreen.o osinterface_sdl.o phlipplerootscene.o quad.o quadrenderer.o scenes.o settings.o textrenderer.o texture.o vertex.o -lSDL -lvorbisfile -lGLEW -lGLU -lGL-lGLU -lGL -lSDL_mixer -lSDL_image /usr/bin/ld: engine.o: undefined reference to symbol 'cos@@GLIBC_2.2.5' //lib/x86_64-linux-gnu/libm.so.6: error adding symbols: DSO missing from command line collect2: error: ld returned 1 exit status The full build log is available from: http://aws-logs.debian.net/ftbfs-logs/2014/11/08/phlipple_0.8.5-1_jessie.log A list of current common problems and possible solutions is available at http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute! About the archive rebuild: The rebuild was done on EC2 VM instances from Amazon Web Services, using a clean, minimal and up-to-date chroot. Every failed build was retried once to eliminate random failures. ---End Message--- ---BeginMessage--- Source: phlipple Source-Version: 0.8.5-2 We believe that the bug you reported is fixed in the latest version of phlipple, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 768...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Peter Pentchev r...@ringlet.net (supplier of updated phlipple package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Mon, 10 Nov 2014 11:23:55 +0200 Source: phlipple Binary: phlipple phlipple-data phlipple-dbg Architecture: source all amd64 Version: 0.8.5-2 Distribution: unstable Urgency: medium Maintainer: Debian Games Team pkg-games-de...@lists.alioth.debian.org Changed-By: Peter Pentchev r...@ringlet.net Description: phlipple - reduce 3D shapes to a single square phlipple-data - reduce 3D shapes to a single square - game data phlipple-dbg - reduce 3D shapes to a single square - debug Closes: 768741 Changes: phlipple (0.8.5-2) unstable; urgency=medium . [ Peter Pentchev ] * Team upload. * Add the libm patch to link with -lm for cos(3). Closes: #768741 . [ Miriam Ruiz ] * Upgraded Standards-Version from 3.9.4 to 3.9.6 * Added Peter Pentchev r...@ringlet.net to Uploaders. Checksums-Sha1: 769432fe5da0bad1a55f20ac5eb0f96a2345fa03 2204 phlipple_0.8.5-2.dsc e8c4845fefed700f43f35a320717ed43640e1d36 42580 phlipple_0.8.5-2.debian.tar.bz2 c97f00c0d0b8589adcf83024671a97b38872a4e4 2553230 phlipple-data_0.8.5-2_all.deb e83e0b79fd2692078b4327ab1f9bfbd2ff7187f5 41234 phlipple_0.8.5-2_amd64.deb 3d2ec109e09fadb79360cb608ece0963b0d8dfae 80876 phlipple-dbg_0.8.5-2_amd64.deb Checksums-Sha256: 7c27187f52a6a9a781f5e7e2781ee3b909c142488feda89778e14727e5ea4217 2204 phlipple_0.8.5-2.dsc ae5a815efa23445be98d44d270bbeb5ed277c97c14964771fa0fcad6277536bb 42580 phlipple_0.8.5-2.debian.tar.bz2 3fb35fcd8101a7373378442506506072c91a2eb58db9bea4326c87248824fa88 2553230 phlipple-data_0.8.5-2_all.deb ac2c238b56229c8712685f387490744e5e6fd514df027cd52b1d798fb64ca9fb 41234 phlipple_0.8.5-2_amd64.deb 468bff47b30d9c39c56f0885a9eb9c90bed3e828ec2b5f5260e791d6d12784f7 80876 phlipple-dbg_0.8.5-2_amd64.deb Files:
Bug#768741: phlipple: FTBFS in jessie: ld: engine.o: undefined reference to symbol 'cos@@GLIBC_2.2.5'
Miriam Ruiz mir...@debian.org writes: I thought I had already uploaded it yeah, go ahead if I didn't Uploaded. Peter, can you please request an unblock? Thanks, Vincent signature.asc Description: PGP signature
Bug#758533: [Pkg-utopia-maintainers] Bug#758533: network-manager: wifi connected, internet connection does not work
Control: tag -1 + fixed-upstream Hi, On Fri, 22 Aug 2014 01:38:26 +0200 Michael Biebl bi...@debian.org wrote: Am 21.08.2014 20:26, schrieb Russ Allbery: Aug 21 10:33:19 wanderer NetworkManager[642]: info dhclient started with pid 17691 Aug 21 10:33:19 wanderer NetworkManager[642]: info Activation (wlan0) Stage 3 of 5 (IP Configure Start) complete. Aug 21 10:33:19 wanderer dhclient: Internet Systems Consortium DHCP Client 4.3.1 Aug 21 10:33:19 wanderer NetworkManager[642]: info (wlan0): DHCPv4 client pid 17691 exited with status -1 Aug 21 10:33:19 wanderer NetworkManager[642]: warn DHCP client died abnormally Downgrading network-manager to 0.9.10.0-1 fixes the problem. It looks like something went wrong with the NMU. Copying Micah. Russ, we just discussed this issue. It's most likely caused by a systemd update where we restart journald in postinst. That somehow seems to break the stdout-jounal forwarding, e.g. from NM to its dhclient child process If you restart NetworkManager.service, this will reset the state and fix the issue. By downgrading to -1, you triggered such a restart of NetworkManager, so the downgrade is a red herring. To reproduce the problem, you can simply run systemctl restart systemd-journald.service and then try to re-connect a NM connection and you'll experience the same issue even with -1. I've just been hit by this bug. The RedHat BTS says it is fixed upstream since september: https://bugzilla.redhat.com/show_bug.cgi?id=1136836#c3 Thanks, _g signature.asc Description: OpenPGP digital signature
Processed: Re: [Pkg-utopia-maintainers] Bug#758533: network-manager: wifi connected, internet connection does not work
Processing control commands: tag -1 + fixed-upstream Bug #758533 [network-manager] network-manager: restarting journald breaks dhclient: DHCPv4 client pid (...) exited with status -1 Bug #756144 [network-manager] network-manager: restarting journald breaks dhclient: DHCPv4 client pid (...) exited with status -1 Bug #758534 [network-manager] network-manager: restarting journald breaks dhclient: DHCPv4 client pid (...) exited with status -1 Added tag(s) fixed-upstream. Added tag(s) fixed-upstream. Added tag(s) fixed-upstream. -- 756144: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=756144 758533: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=758533 758534: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=758534 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#770425: Possibility of update to 4.x
On Sat, 2014-11-29 at 14:53 +1100, Craig Small wrote: Hi Nick, The security update will only be 3.6.1 with the 4.7.4-4.7.5 patches. It's difficult balancing act really but the whole purpose of the security updates is just to update for security. It's not ideal for certain situations. The proposed update went to the security team a few minutes ago and should mean an update for wordpress in wheezy will be out today. Thanks for that. Doesn't actually concern me which solution was picked, as long as one was chosen and implemented reasonably quickly (I'll stick with the 4.x packages I now have anyway). Cheers, Nick -- Nick Phillips / nick.phill...@otago.ac.nz / 03 479 4195 # These statements are mine, not those of the University of Otago
Bug#770648: Bug#753944: Bug#770648: hiredis: FTBFS: Test failure
gregor herrmann dixit: Ouch. How about if USENETWORK=no then CHROOT/etc/resolv.conf is created with values sane for that? Can you do the NMU? What would these sane values be? I guess, no nameserver. On BSD, a single line “lookup file”, but I think glibc’s syntax differs. Best to ask one of the src:glibc maintainers, methinks. Looks like /etc/nsswitch.conf is not copied (i.e. if I change it in the host system and enter the chroot, the changes are not there). Hm okay. That means “lookup file dns” IIRC (no Linux system at hand right now), which should be fine with no nameservers given, so we need not touch that file, AIUI. bye, //mirabilos -- “It is inappropriate to require that a time represented as seconds since the Epoch precisely represent the number of seconds between the referenced time and the Epoch.” -- IEEE Std 1003.1b-1993 (POSIX) Section B.2.2.2 -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#770647: marked as done (double free in libclamunrar_iface + memory leak in read_block())
Your message dated Sun, 30 Nov 2014 23:17:05 + with message-id e1xvdjl-0007so...@franck.debian.org and subject line Bug#770647: fixed in libclamunrar 0.98.5-0+deb7u1 has caused the Debian Bug report #770647, regarding double free in libclamunrar_iface + memory leak in read_block() 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.) -- 770647: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=770647 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: libclamunrar Version: 0.96.4-1 Severity: serious Tags: security pending The debian security tracker references a problem (clamav: double-free error libclamunrar_iface/unrar_iface.c) which it learned from http://www.openwall.com/lists/oss-security/2013/11/29/6 This got marked as fixed in Debian because the Clamav version we use a high enough version. However the file / part of code is not used from the clamav package but from the libclamunrar package instead. It is split into another package due to the non-free license of the unrar code. To double check, the report mentions the file unrar_iface.c. If you check the buildlog of the clamav package you won't find it together with gcc. If you check libclamunrar's buildlog then you will see it. Also if you check libclamunrar_iface.so.6.1.20 you will find the function named libclamunrar_iface_LTX_unrar_extract_next_prepare which is part of the libclamunrar package. To conclude: this problem as such is still not fixed in Wheezy. The only clamunrar related change between 0.98.1-1 and 0.98.5-1 is a memory leak fix in read_block(). For that reason and to keep it in sync with the clamav package I would prefer to have the 0.98.5 version in Wheezy. Sebastian ---End Message--- ---BeginMessage--- Source: libclamunrar Source-Version: 0.98.5-0+deb7u1 We believe that the bug you reported is fixed in the latest version of libclamunrar, 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 770...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Sebastian Andrzej Siewior sebast...@breakpoint.cc (supplier of updated libclamunrar package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Tue, 25 Nov 2014 22:01:13 +0100 Source: libclamunrar Binary: libclamunrar6 Architecture: source amd64 Version: 0.98.5-0+deb7u1 Distribution: stable Urgency: medium Maintainer: ClamAV Team pkg-clamav-de...@lists.alioth.debian.org Changed-By: Sebastian Andrzej Siewior sebast...@breakpoint.cc Description: libclamunrar6 - anti-virus utility for Unix - unrar support Closes: 727917 741080 770647 Changes: libclamunrar (0.98.5-0+deb7u1) stable; urgency=medium . [ Sebastian Andrzej Siewior ] * Update to new upstream version. - Finaly address double-free error exists within the unrar_extract_next_prepare() (Closes: #770647) * redo rules files to something smaller like we do have in the clamav package. * Do autoreconf before configure (closes: #727917). * Enable hardened build flags (closes: #741080). * Remove all .la files (clamd works without them). * Add VCS-* tags. * Add myself as uploader. * Remove *.so files (lintian warning). * Add a symbol file. * Bumb standards version to 3.9.1 after made the required changes. * Drop automake workaround, the bug was fixed. * Fix LFS support using the same approach as clamav for compatibility and correctness . [ Scott Kitterman ] * Add build-dep on libssl-dev, needed for configure even if not used in libclamunrar * Update debian/copyright to add openssl exception per COPYING Checksums-Sha1: 823ce7b6fc5a60542c99cbae87679e3d1733585a 2147 libclamunrar_0.98.5-0+deb7u1.dsc 6d4a3441e142002ffdaa76ad313bc018985e1999 304828 libclamunrar_0.98.5.orig.tar.xz 5fcac87cba7af54f5cfeb6885e078b8c0b2e59fd 4861 libclamunrar_0.98.5-0+deb7u1.debian.tar.gz f498b377a3d6e11e09394b9166c739bf4b820378 37528 libclamunrar6_0.98.5-0+deb7u1_amd64.deb Checksums-Sha256: a772861a6d5af5aa6a82c3067d151666da2ba03291397de121b2084672713cbc 2147 libclamunrar_0.98.5-0+deb7u1.dsc 3d957d584bee260f11c7b5b211899c4cacfc3849b1d0485b3f21eb2d4aac 304828
Bug#771293: marked as done (bluedevil requires bluez-obexd)
Your message dated Sun, 30 Nov 2014 23:19:08 + with message-id e1xvdlk-0008qc...@franck.debian.org and subject line Bug#771293: fixed in bluedevil 2.0~rc1-44-gb7697a7-3 has caused the Debian Bug report #771293, regarding bluedevil requires bluez-obexd 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.) -- 771293: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=771293 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: bluedevil Version: 2.0~rc1-44-gb7697a7-2 Severity: serious Hi, In adding to #771116, it seems that, after looking at the code, bluedevil really requires bluez-obexd. bluedevil uses interfaces like org.bluez.Agent*1* which are only provided by bluez-obexd, obexd-client and obex-data-server are only provding org.bluez.Agent (without the 1). Cheers, Laurent Bigonville -- System Information: Debian Release: jessie/sid APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.16.0-4-amd64 (SMP w/8 CPU cores) Locale: LANG=fr_BE.utf8, LC_CTYPE=fr_BE.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash ---End Message--- ---BeginMessage--- Source: bluedevil Source-Version: 2.0~rc1-44-gb7697a7-3 We believe that the bug you reported is fixed in the latest version of bluedevil, 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 771...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Scott Kitterman sc...@kitterman.com (supplier of updated bluedevil package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Sun, 30 Nov 2014 17:52:59 -0500 Source: bluedevil Binary: bluedevil Architecture: source i386 Version: 2.0~rc1-44-gb7697a7-3 Distribution: unstable Urgency: medium Maintainer: Debian KDE Extras Team pkg-kde-ext...@lists.alioth.debian.org Changed-By: Scott Kitterman sc...@kitterman.com Description: bluedevil - KDE Bluetooth stack Closes: 771116 771293 Changes: bluedevil (2.0~rc1-44-gb7697a7-3) unstable; urgency=medium . * Team upload. * Correct depends on bluez-obexd (Closes: #771116, #771293) Checksums-Sha1: 7a1ca88747bc93f4a3c6463209d16f3b7c5097e6 2317 bluedevil_2.0~rc1-44-gb7697a7-3.dsc 2471ad906d9f51dcc213dd7bf0777c98751ce48d 4520 bluedevil_2.0~rc1-44-gb7697a7-3.debian.tar.xz 6bf8376fde5cb2d698bd58e0bad6f8c8201e2349 266872 bluedevil_2.0~rc1-44-gb7697a7-3_i386.deb Checksums-Sha256: c958f6e2bb65e2647fbaf88a161d2b674ca224d2b1e91890978a988308257264 2317 bluedevil_2.0~rc1-44-gb7697a7-3.dsc 15598cd44d98e045d4c5f4765e3f5a1fd6d086c3fb0f5307073828513f3fb9fb 4520 bluedevil_2.0~rc1-44-gb7697a7-3.debian.tar.xz 35a81e78e8dea0ab44cb08712ccf577db34e2e91bf310a3b6da9f56e95c1b4a3 266872 bluedevil_2.0~rc1-44-gb7697a7-3_i386.deb Files: 0b7131654c9c24bbea91257f13279b38 2317 net optional bluedevil_2.0~rc1-44-gb7697a7-3.dsc 5da4a7b3a60e1553949c7f1f5aa0062e 4520 net optional bluedevil_2.0~rc1-44-gb7697a7-3.debian.tar.xz 28a89f40b674cff8a6c34fa00f226ff3 266872 net optional bluedevil_2.0~rc1-44-gb7697a7-3_i386.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1 iQIcBAEBCAAGBQJUe6NgAAoJEHjX3vua1ZrxYoMP/10bwY3xnT1eO7x8IWBIbzaB iYo3CbXStKnbgb6hB3GaOkpe+zrgQuFngBTEQq7EXS51hNmakNHLfRk6tAFCxG+d ZmMIEkO3FWW3j2xa2CL9CxH5s9Z9f2038DMGDy6pVZDC6gBdl/CqYcNRlpZeBYBE vH8+TNZ881s8jcmy3n/zbIBGPTIOSQOCPLxQdRFzjgHx7Jef0MC0rTuYE8LBa3Xv mYnHL+C5yFuW/F8emmiVY4JBwi4sS0QTz81zDmefypMpGTKCKEvsGPQnbbFyMGVP Tu4NhuQSgUAPbkHp+ylZNmgs9URG5dF9xiSxdKoXoi6kr1jBU1kmio2qeWiyxJI3 UwspMXgr62UYbnHnxzhOCoT+YL/gDdvXcEH42QPoxbvKTxWNe+vQ5SHAoxk+NOQU Q+b4W37qNYWwz8P5gRpi7Dk1BMBiOw85Z6e5iTViumKiIYFdRDRBmqWMUfTHmLCg G978h6hXE9RSfGDqzcJ+lk1a5Ogqra/QJK8iEooeHc+HjeCpQypBwqiMYYJz25d7 d1NG/IQAKd5HLsO16VzysmOxU0qBWKFKRLxXtOVPy9On3SxmArPmVUR5nna0Pqg8 2AKfBUh8XZIvupfuYWxskaZNL7fscB8lLJsWGkkKrhkXFOU0uu4etGkxfCS32o8y TZ24CndDsKqYIC7The06 =S2+9 -END PGP SIGNATUREEnd Message---
Bug#771116: marked as done ([bluedevil] Typo in a dependency - bluez-obezd instead of bluez-obexd)
Your message dated Sun, 30 Nov 2014 23:19:08 + with message-id e1xvdlk-0008q6...@franck.debian.org and subject line Bug#771116: fixed in bluedevil 2.0~rc1-44-gb7697a7-3 has caused the Debian Bug report #771116, regarding [bluedevil] Typo in a dependency - bluez-obezd instead of bluez-obexd 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.) -- 771116: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=771116 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: bluedevil Version: 2.0~rc1-44-gb7697a7-2 Severity: normal --- Please enter the report below this line. --- While rebuilding bluedevil for Tanglu I saw a typo in the dependencies of package bluedevil in debian/control: Package: bluedevil Architecture: linux-any Depends: bluez (= 5), obex-data-server, bluez-obezd | obexd-client, ^ | should be bluez-obexd Regards, Thomas Funk --- System information. --- Architecture: amd64 Kernel: Linux 3.16-3-amd64 Debian Release: 7.5 --- Package information. --- Depends (Version) | Installed ===-+-=== kde-runtime | 4:4.14.2-1 libbluedevil1(= 1.9.3) | 1.9.3-1 libc6 (= 2.14) | 2.19-9 libkdecore5 (= 4:4.4.4-2~) | 4:4.14.2-3 libkdeui5 (= 4:4.7.0) | 4:4.14.2-3 libkfile4(= 4:4.4) | 4:4.14.2-3 libkio5 (= 4:4.5.85) | 4:4.14.2-3 libqt4-dbus(= 4:4.6.1) | 4:4.8.6+git64-g5dc8b2b+dfsg-2 libqtcore4 (= 4:4.7.0~beta1) | 4:4.8.6+git64-g5dc8b2b+dfsg-2 libqtgui4 (= 4:4.8.0) | 4:4.8.6+git64-g5dc8b2b+dfsg-2 libstdc++6 (= 4.2.1) | 4.9.1-12 bluez | 5.23-1 obexd-client| 0.48-2b1 obex-data-server| 0.4.6-0tanglu1 Package's Recommends field is empty. Suggests (Version) | Installed ==-+-=== pulseaudio-module-bluetooth| 5.0-2tanglu1 OR bluez-alsa | 4.101-3 ---End Message--- ---BeginMessage--- Source: bluedevil Source-Version: 2.0~rc1-44-gb7697a7-3 We believe that the bug you reported is fixed in the latest version of bluedevil, 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 771...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Scott Kitterman sc...@kitterman.com (supplier of updated bluedevil package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Sun, 30 Nov 2014 17:52:59 -0500 Source: bluedevil Binary: bluedevil Architecture: source i386 Version: 2.0~rc1-44-gb7697a7-3 Distribution: unstable Urgency: medium Maintainer: Debian KDE Extras Team pkg-kde-ext...@lists.alioth.debian.org Changed-By: Scott Kitterman sc...@kitterman.com Description: bluedevil - KDE Bluetooth stack Closes: 771116 771293 Changes: bluedevil (2.0~rc1-44-gb7697a7-3) unstable; urgency=medium . * Team upload. * Correct depends on bluez-obexd (Closes: #771116, #771293) Checksums-Sha1: 7a1ca88747bc93f4a3c6463209d16f3b7c5097e6 2317 bluedevil_2.0~rc1-44-gb7697a7-3.dsc 2471ad906d9f51dcc213dd7bf0777c98751ce48d 4520 bluedevil_2.0~rc1-44-gb7697a7-3.debian.tar.xz 6bf8376fde5cb2d698bd58e0bad6f8c8201e2349 266872 bluedevil_2.0~rc1-44-gb7697a7-3_i386.deb Checksums-Sha256: c958f6e2bb65e2647fbaf88a161d2b674ca224d2b1e91890978a988308257264 2317 bluedevil_2.0~rc1-44-gb7697a7-3.dsc 15598cd44d98e045d4c5f4765e3f5a1fd6d086c3fb0f5307073828513f3fb9fb 4520 bluedevil_2.0~rc1-44-gb7697a7-3.debian.tar.xz 35a81e78e8dea0ab44cb08712ccf577db34e2e91bf310a3b6da9f56e95c1b4a3 266872 bluedevil_2.0~rc1-44-gb7697a7-3_i386.deb Files: 0b7131654c9c24bbea91257f13279b38 2317 net optional bluedevil_2.0~rc1-44-gb7697a7-3.dsc 5da4a7b3a60e1553949c7f1f5aa0062e 4520 net optional bluedevil_2.0~rc1-44-gb7697a7-3.debian.tar.xz 28a89f40b674cff8a6c34fa00f226ff3 266872 net optional bluedevil_2.0~rc1-44-gb7697a7-3_i386.deb -BEGIN PGP
Bug#762789: marked as done (ppp: CVE-2014-3158: Integer overflow in option parsing)
Your message dated Sun, 30 Nov 2014 23:17:12 + with message-id e1xvdjs-0007uo...@franck.debian.org and subject line Bug#762789: fixed in ppp 2.4.5-5.1+deb7u1 has caused the Debian Bug report #762789, regarding ppp: CVE-2014-3158: Integer overflow in option parsing 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.) -- 762789: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=762789 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: ppp Severity: grave Tags: security Hi, the following vulnerability was published for ppp. CVE-2014-3158[0]: Potential integer overflow in option parsing This is fixed in this commit https://github.com/paulusmack/ppp/commit/7658e8257183f062dc01f87969c140707c7e52cb and in the 2.4.7 upstream release. If you fix the vulnerability please also make sure to include the CVE (Common Vulnerabilities Exposures) id in your changelog entry. For further information see: [0] http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2014-3158 https://security-tracker.debian.org/tracker/CVE-2014-3158 http://marc.info/?l=linux-pppm=140764978420764 Please adjust the affected versions in the BTS as needed. Cheers, -- Raphaël Hertzog ◈ Debian Developer Discover the Debian Administrator's Handbook: → http://debian-handbook.info/get/ ---End Message--- ---BeginMessage--- Source: ppp Source-Version: 2.4.5-5.1+deb7u1 We believe that the bug you reported is fixed in the latest version of ppp, 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 762...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Sebastien Delafond s...@debian.org (supplier of updated ppp 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: Fri, 28 Nov 2014 09:49:28 +0100 Source: ppp Binary: ppp ppp-udeb ppp-dev Architecture: source all amd64 Version: 2.4.5-5.1+deb7u1 Distribution: wheezy-security Urgency: medium Maintainer: Marco d'Itri m...@linux.it Changed-By: Sebastien Delafond s...@debian.org Description: ppp- Point-to-Point Protocol (PPP) - daemon ppp-dev- Point-to-Point Protocol (PPP) - development files ppp-udeb - Point-to-Point Protocol (PPP) - package for Debian Installer (udeb) Closes: 762789 Changes: ppp (2.4.5-5.1+deb7u1) wheezy-security; urgency=medium . * Non-maintainer upload by the Security Team (thanks to Pierre Schweitzer pie...@reactos.org for preparing the update). * Fix CVE-2014-3158: integer overflow which may allow overwrite security-relevant variables (Closes: #762789). Checksums-Sha1: fa8d9c42f20eead98fe3d9053a2e6ccd087b2911 1412 ppp_2.4.5-5.1+deb7u1.dsc cb977b31584e3488e08a643aaa672fdb229d2e78 684342 ppp_2.4.5.orig.tar.gz 3d3b79b36dcc967cb605c76ebcb3c393cc5878c3 96877 ppp_2.4.5-5.1+deb7u1.diff.gz 519f4b04df2cbf504bb9a70f7e50d216f49210df 57194 ppp-dev_2.4.5-5.1+deb7u1_all.deb 0c6f9fd2fa2dee685cff044944e332e8987db79a 380810 ppp_2.4.5-5.1+deb7u1_amd64.deb 468453bf2de8f0e2a30106f149e5d9aa47789c5e 112454 ppp-udeb_2.4.5-5.1+deb7u1_amd64.udeb Checksums-Sha256: eeb418bbbf42ce579bbc0984927c14ee8bfa6d68e39e5af52214b398237233ed 1412 ppp_2.4.5-5.1+deb7u1.dsc 43317afec9299f9920b96f840414c977f0385410202d48e56d2fdb8230003505 684342 ppp_2.4.5.orig.tar.gz e1e19cef43f235bd657b9fea68a17d8faa19f97bd32e0e8e1b69fa61a05fb449 96877 ppp_2.4.5-5.1+deb7u1.diff.gz c043b4eb11da765a11ff26500901388180685c51c310956b89b2b7738d7ee9be 57194 ppp-dev_2.4.5-5.1+deb7u1_all.deb 0c74caa1418019d8352a1750f1db32f0d6c9024191d28b17324c78642e5f6fe3 380810 ppp_2.4.5-5.1+deb7u1_amd64.deb b71dc1adc6f3e8fdbcf288e0f5c369b8ed20729b6f3e533717538548a1e97ef3 112454 ppp-udeb_2.4.5-5.1+deb7u1_amd64.udeb Files: 988620c88831781181eb2ad9e3edcc22 1412 admin optional ppp_2.4.5-5.1+deb7u1.dsc 4621bc56167b6953ec4071043fe0ec57 684342 admin optional ppp_2.4.5.orig.tar.gz d6069a42908e69d4ecb7df32af27cb3e 96877 admin optional ppp_2.4.5-5.1+deb7u1.diff.gz 4b46acb465c9d1d9700d8b4986e32df9 57194 devel extra ppp-dev_2.4.5-5.1+deb7u1_all.deb 59edd4b76fc05e2f953c232bcefd0297 380810 admin optional ppp_2.4.5-5.1+deb7u1_amd64.deb 4b0344e9bdda447caee49fe62ad13c02 112454 debian-installer optional
Bug#770972: marked as done (libksba: CVE-2014-9087: buffer overflow in ksba_oid_to_str)
Your message dated Sun, 30 Nov 2014 23:17:06 + with message-id e1xvdjm-0007t8...@franck.debian.org and subject line Bug#770972: fixed in libksba 1.2.0-2+deb7u1 has caused the Debian Bug report #770972, regarding libksba: CVE-2014-9087: buffer overflow in ksba_oid_to_str 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.) -- 770972: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=770972 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Source: libksba Version: 1.3.1-1 Severity: grave Tags: security upstream patch fixed-upstream Hi all, Today a new upstream release for Libksba was announced, addressing in particular the following: Impact of the security bug == By using special crafted S/MIME messages or ECC based OpenPGP data, it is possible to create a buffer overflow. The bug is not easy to exploit because there only 80 possible values which can be used to overwrite memory. However, a denial of service is possible and someone may come up with other clever attacks. Thus this should be fix. Affected versions: All Libksba versions 1.3.2 Background: Yesterday Hanno Böck found an invalid memory access in the 2.1 branch of GnuPG by conveying a malformed OID as part of an ECC key. It turned out that this bug has also been in libksba ever since and affects at least gpgsm and dirmngr. The code to convert an OID to its string representation has an obvious error of not considering an invalid encoding for arc-2. A first byte of 0x80 can be used to make a value of less then 80 and we then subtract 80 from it as required by the OID encoding rules. Due to the use of an unsigned integer this results in a pretty long value which won't fit anymore into the allocated buffer. The actual fix for lib Libksba is commit f715b9e. Announce: http://lists.gnupg.org/pipermail/gnupg-announce/2014q4/000359.html Upstream fix: http://git.gnupg.org/cgi-bin/gitweb.cgi?p=libksba.git;a=commit;h=f715b9e156dfa99ae829fc694e5a0abd23ef97d7 Regards, Salvatore ---End Message--- ---BeginMessage--- Source: libksba Source-Version: 1.2.0-2+deb7u1 We believe that the bug you reported is fixed in the latest version of libksba, 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 770...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Salvatore Bonaccorso car...@debian.org (supplier of updated libksba 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: Wed, 26 Nov 2014 09:09:22 +0100 Source: libksba Binary: libksba-dev libksba8 Architecture: source amd64 Version: 1.2.0-2+deb7u1 Distribution: wheezy-security Urgency: high Maintainer: Debian GnuTLS Maintainers pkg-gnutls-ma...@lists.alioth.debian.org Changed-By: Salvatore Bonaccorso car...@debian.org Description: libksba-dev - X.509 and CMS support library - development files libksba8 - X.509 and CMS support library Closes: 770972 Changes: libksba (1.2.0-2+deb7u1) wheezy-security; urgency=high . * Non-maintainer upload by the Security Team. * Add 0001-Fix-buffer-overflow-in-ksba_oid_to_str.patch patch. CVE-2014-9087: Fix buffer overflow in ksba_oid_to_str. (Closes: #770972) Checksums-Sha1: f52ccf52ff7391b21082415df77ba4e1971b596d 2159 libksba_1.2.0-2+deb7u1.dsc 0c4e593464b9dec6f53c728c375d54a095658230 588323 libksba_1.2.0.orig.tar.bz2 f8d9dca81dd96c2f52f781c10d2bfbd70b7fd030 7179 libksba_1.2.0-2+deb7u1.debian.tar.gz 60bb1c8bb402b8c0a56a63dd5b6647f71fb96c52 163948 libksba-dev_1.2.0-2+deb7u1_amd64.deb 96cd019f9699650eec3a2d355c94b45d821df1fc 109010 libksba8_1.2.0-2+deb7u1_amd64.deb Checksums-Sha256: a14f0e7b0fe62b1a89b4e64b57705ce21239b1612cebaed41abc0c1291d7e4f0 2159 libksba_1.2.0-2+deb7u1.dsc 09afce65b03d027cbec10d21464f4f651cdfd269e38b404f83e48d3e2a3c934b 588323 libksba_1.2.0.orig.tar.bz2 f0d18f12555c0908821c0fd5dc39c7599b16cc5af5a44088d9c008edb8113e6f 7179 libksba_1.2.0-2+deb7u1.debian.tar.gz fb36e8111cb9a62249f8cd8a8d09010f136af05337c685d8e163eefa6bf3a41d 163948 libksba-dev_1.2.0-2+deb7u1_amd64.deb b67af83cafd253be0ed7ae644704d9ef780bc697a7b4ae8faab62919b08adabb 109010 libksba8_1.2.0-2+deb7u1_amd64.deb Files:
Bug#771104: marked as done ([wine] wine is no more usable)
Your message dated Sun, 30 Nov 2014 23:49:57 + with message-id e1xvefz-0003yn...@franck.debian.org and subject line Bug#771104: fixed in wine 1.6.2-17 has caused the Debian Bug report #771104, regarding [wine] wine is no more usable 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.) -- 771104: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=771104 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: wine Version: 1.6.2-16 Severity: grave --- Please enter the report below this line. --- Dear Maintainer, the current version of wine is not usable anymore. Starting any program with wine results in the output of error messages of the form Wine cannot find the FreeType font library. To enable Wine to use TrueType fonts please install a version of FreeType greater than or equal to 2.0.5. http://www.freetype.org . . . Wine cannot find the ncurses library (libncurses.so.5). Wine cannot find the FreeType font library. To enable Wine to use TrueType fonts please install a version of FreeType greater than or equal to 2.0.5. But all the packages mentioned in the error messages are installed: sudo aptitude search (?installed)freetype i A libfreetype6 - Schrift-Engine FreeType 2 - Laufzeitbibliothek i A libfreetype6-dev - Schrift-Prozessor FreeType 2, Entwicklungsdateien sudo aptitude search (?installed)libncurses i libncurses5 - Gemeinsam benutzte Bibliotheken für Terminalsteuerung i A libncurses5-dev - Ncurses-Bibliotheken für Entwickler i libncursesw5 - Bibliotheken für Terminalsteuerung (Unterstützung für Multibyte-Zeichen) Furthermore, wine used to work properly in a previous version, but I can't remember which version it was. Let me know if further information is required. Kind regards, Georgios --- System information. --- Architecture: amd64 Kernel: Linux 3.16.0-4-amd64 Foreign Architectures: i386 Debian Release: jessie/sid 500 testing-updates ftp.de.debian.org 500 testing security.debian.org 500 testing ftp.de.debian.org 500 stable deb.opera.com 100 jessie-backports ftp.de.debian.org --- Package information. --- Package's Depends field is empty. Package's Recommends field is empty. Package's Suggests field is empty. ---End Message--- ---BeginMessage--- Source: wine Source-Version: 1.6.2-17 We believe that the bug you reported is fixed in the latest version of wine, 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 771...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Michael Gilbert mgilb...@debian.org (supplier of updated wine 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: Sun, 30 Nov 2014 21:04:09 + Source: wine Binary: wine wine-binfmt wine32 wine64 wine32-dev-tools wine32-tools wine64-dev-tools wine64-tools libwine-dev libwine-dbg libwine wine-bin wine64-bin libwine-alsa libwine-bin libwine-capi libwine-cms libwine-gl libwine-gphoto2 libwine-ldap libwine-openal libwine-oss libwine-print libwine-sane Architecture: source Version: 1.6.2-17 Distribution: unstable Urgency: medium Maintainer: Debian Wine Party pkg-wine-pa...@lists.alioth.debian.org Changed-By: Michael Gilbert mgilb...@debian.org Description: libwine- Windows API implementation - library libwine-alsa - Windows API implementation - ALSA sound module libwine-bin - Windows API implementation - system services libwine-capi - Windows API implementation - ISDN module libwine-cms - Windows API implementation - color management module libwine-dbg - Windows API implementation - debugging symbols libwine-dev - Windows API implementation - development files libwine-gl - Windows API implementation - OpenGL module libwine-gphoto2 - Windows API implementation - camera module
Bug#769791: marked as done (wine32 doesn't work after fresh install)
Your message dated Sun, 30 Nov 2014 23:49:57 + with message-id e1xvefz-0003yn...@franck.debian.org and subject line Bug#771104: fixed in wine 1.6.2-17 has caused the Debian Bug report #771104, regarding wine32 doesn't work after fresh install 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.) -- 771104: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=771104 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: wine32 Version: 1.6.2-16 Severity: serious Hi, wine32 doesn't start anymore after upgrade with a clean directory. This is a duplicate of #739863 which had been closed in wine-unstable which had been removed from unstable afterwards, so this bug is present in testing. Andi ---End Message--- ---BeginMessage--- Source: wine Source-Version: 1.6.2-17 We believe that the bug you reported is fixed in the latest version of wine, 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 771...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Michael Gilbert mgilb...@debian.org (supplier of updated wine 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: Sun, 30 Nov 2014 21:04:09 + Source: wine Binary: wine wine-binfmt wine32 wine64 wine32-dev-tools wine32-tools wine64-dev-tools wine64-tools libwine-dev libwine-dbg libwine wine-bin wine64-bin libwine-alsa libwine-bin libwine-capi libwine-cms libwine-gl libwine-gphoto2 libwine-ldap libwine-openal libwine-oss libwine-print libwine-sane Architecture: source Version: 1.6.2-17 Distribution: unstable Urgency: medium Maintainer: Debian Wine Party pkg-wine-pa...@lists.alioth.debian.org Changed-By: Michael Gilbert mgilb...@debian.org Description: libwine- Windows API implementation - library libwine-alsa - Windows API implementation - ALSA sound module libwine-bin - Windows API implementation - system services libwine-capi - Windows API implementation - ISDN module libwine-cms - Windows API implementation - color management module libwine-dbg - Windows API implementation - debugging symbols libwine-dev - Windows API implementation - development files libwine-gl - Windows API implementation - OpenGL module libwine-gphoto2 - Windows API implementation - camera module libwine-ldap - Windows API implementation - LDAP module libwine-openal - Windows API implementation - OpenAL module libwine-oss - Windows API implementation - OSS sound module libwine-print - Windows API implementation - printing module libwine-sane - Windows API implementation - scanner module wine - Windows API implementation - standard suite wine-bin - Windows API implementation - binaries wine-binfmt - Windows API implementation - binfmt support wine32 - Windows API implementation - 32-bit binary loader wine32-dev-tools - Windows API implementation - 32-bit developer tools wine32-tools - Windows API implementation - 32-bit developer tools wine64 - Windows API implementation - 64-bit binary loader wine64-bin - Windows API implementation - 64-bit helper wine64-dev-tools - Windows API implementation - 64-bit developer tools wine64-tools - Windows API implementation - 64-bit developer tools Closes: 766028 769233 771104 Changes: wine (1.6.2-17) unstable; urgency=medium . * Add libgl1-mesa-dri dependency to wine32 (closes: #766028). * Add ncurses and freetype dependencies to wine32 (closes: #771104). * Add binfmt-support dependency to wine-binfmt and document binfmt setup in README.debian (closes: #769233). Checksums-Sha1: 6e514da981caf77f912b80641a4d4ffdfd311dbb 4951 wine_1.6.2-17.dsc c13583063d87cf7ac1afd24a39f69535556bb884 59660 wine_1.6.2-17.debian.tar.xz Checksums-Sha256: 97dc52dd019f7924989bfeccd8d948bd7ff04f07f720db4a968384e21526cda2 4951 wine_1.6.2-17.dsc c04cb9670242e7edb88fb8ac63b44b474add87c9ea3364137d74ac19a1b55d2b 59660 wine_1.6.2-17.debian.tar.xz Files: b740c9c68d8151fa41d5e992ca036b52 4951 otherosfs optional wine_1.6.2-17.dsc 8a6f2043998da3d5f9f117e40e189e8f 59660 otherosfs optional wine_1.6.2-17.debian.tar.xz -BEGIN PGP SIGNATURE- Version: GnuPG v1
Bug#769473: marked as done (wine: starts in a tiny and inoperable window)
Your message dated Sun, 30 Nov 2014 23:49:57 +
with message-id e1xvefz-0003yn...@franck.debian.org
and subject line Bug#771104: fixed in wine 1.6.2-17
has caused the Debian Bug report #771104,
regarding wine: starts in a tiny and inoperable window
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.)
--
771104: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=771104
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
---BeginMessage---
Package: wine
Version: 1.6.2-16
Severity: important
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Dear Maintainer,
Don't know if this problem comes from the last update, but it worked in version
1.6.2-8. I didn't test it for a month.
I tried creating a new wineprefix and running wine winecfg and this is the
output:
josgalo@pc-debian:~$ wine winecfg
wine: created the configuration directory '/home/josgalo/.wine-new'
Wine cannot find the FreeType font library. To enable Wine to
use TrueType fonts please install a version of FreeType greater than
or equal to 2.0.5.
After that a tiny window appears but I can't do anything. Also shows up in the
panel. I'm using Xfce.
Closing from the panel and trying again with winecfg alone I get this:
josgalo@pc-debian:~$ winecfg
Wine cannot find the FreeType font library. To enable Wine to
use TrueType fonts please install a version of FreeType greater than
or equal to 2.0.5.
http://www.freetype.org
Wine cannot find the ncurses library (libncurses.so.5).
Wine cannot find the FreeType font library. To enable Wine to
use TrueType fonts please install a version of FreeType greater than
or equal to 2.0.5.
http://www.freetype.org
err:wincodecs:PngEncoder_CreateInstance Failed writing PNG because unable to
find libpng12.so.0
fixme:ole:CoCreateInstance no instance created for interface
{0103-a8f2-4877-ba0a-fd2b6645fb94} of class {27949969-876a-
41d7-9447-568f6a35a4dc}, hres is 0x80004005
err:menubuilder:convert_to_native_icon error 0x80004005 creating bitmap encoder
I think I have the required libraries installed:
josgalo@pc-debian:~$ sudo aptitude search (?installed)freetype
[sudo] password for josgalo:
i A libfreetype6- motor de tipografías de FreeType
2, archivos de b
i A libfreetype6-dev- FreeType 2 font engine,
development files
josgalo@pc-debian:~$ sudo aptitude search (?installed)ncurses
i libncurses5 - Bibliotecas compartidas para el
tratamiento del t
i libncurses5-dev - developer's libraries for ncurses
i libncursesw5- Bibliotecas compartidas para el
tratamiento del t
i ncurses-base- Definiciones de tipo de
terminales básicas
i ncurses-bin - Programas relacionados con el
terminal y las pági
i ncurses-term- Definiciones adicionales de tipos
de terminal
josgalo@pc-debian:~$ sudo aptitude search (?installed)libpng
i A libpng12-0 - Biblioteca de png, ejecutable
i A libpng12-dev- PNG library - development
Tell me if I can give you more information.
Thank you!
- -- System Information:
Debian Release: jessie/sid
APT prefers testing
APT policy: (500, 'testing')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 3.16.0-4-amd64 (SMP w/4 CPU cores)
Locale: LANG=es_ES.utf8, LC_CTYPE=es_ES.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Versions of packages wine depends on:
ii file1:5.20-2
ii wine32 1.6.2-16
wine recommends no packages.
Versions of packages wine suggests:
pn avscan | klamav | clamav none
pn binfmt-support none
pn ttf-mscorefonts-installer none
pn winbindnone
- -- no debconf information
-BEGIN PGP SIGNATURE-
Version: GnuPG v1
iQIcBAEBAgAGBQJUZSPfAAoJEOIKRzyRbfJG2p8P/jxSv7UMs2pAzuvdG6hgmpLc
bIg0rUplKKs3/hnTLKECj0nSKyf7HLq4i/iHEQtqfvAREzdnOSmfIwJc+5/BOrXW
RQObcvRKEodF0qOOyBelPgYqF5y2QSa1BJgos5BGfhjg3hvI514hWwgRpWCBklsl
JP2fCxkfFccpA5dTi9GD00x/mA8r+A0gWn0SIWbrExvJJBZdOwm8H0Wn5CcaiMSH
Hx3A7o3DH/zpj86yh5H0OfBQ0bUpPHl1kByWc4rIWsQXhXCDlHOQzPUTxlfukTlW
veINN8kYDdEL2ZU8YGSNPdReq0BFxYtXd0/x9wQXS7zamR/NTAYiATTELDVMwbMX
8o5jhBTOSsVL9qbQHi7L3OJzGHdH5Q7Cpwo6/OnCR6kg8Q68USyUIqUaWoczGirt
fxoB+IplAie1IJ4IQiYqe0CVkHDobO+nd7VWWSptGXB76meFciYgRXnsIkK8uReq
HVtvi0kb0Aj/ZVr0Jv96R1RxAYaWxAfCyZxPpVCZGIfnNzQ3kB/ofZfKfPkg1TgM
NMMn4K71pfF3RANLGWX/837tADZqnrwerGSQtCF9Zpzm0P/QXOvvoTYJXAw6IlJY
U+cua7H0BD9lg8PDTcLDTmiCvMSAHFj2uMbsk5P3rvWiPPAjfvZ1APyDKAKuSnNF
scYfZUlYgHmlI/XyehPb
=Ziba
Bug#771612: python-txzookeeper: unhandled symlink to directory conversion: /usr/share/doc/PACKAGE
Package: python-txzookeeper Version: 0.9.8-1 Severity: serious User: debian...@lists.debian.org Usertags: piuparts Hi, an upgrade test with piuparts revealed that your package installs files over existing symlinks and possibly overwrites files owned by other packages. This usually means an old version of the package shipped a symlink but that was later replaced by a real (and non-empty) directory. This kind of overwriting another package's files cannot be detected by dpkg. This was observed on the following upgrade paths: wheezy - jessie For /usr/share/doc/PACKAGE this may not be problematic as long as both packages are installed, ship byte-for-byte identical files and are upgraded in lockstep. But once one of the involved packages gets removed, the other one will lose its documentation files, too, including the copyright file, which is a violation of Policy 12.5: https://www.debian.org/doc/debian-policy/ch-docs.html#s-copyrightfile For other overwritten locations anything interesting may happen. Note that dpkg intentionally does not replace directories with symlinks and vice versa, you need the maintainer scripts to do this. See in particular the end of point 4 in https://www.debian.org/doc/debian-policy/ch-maintainerscripts.html#s-unpackphase It is recommended to use the dpkg-maintscript-helper commands 'dir_to_symlink' and 'symlink_to_dir' (available since dpkg 1.17.2) to perform the conversion, ideally using d/$PACKAGE.mainstscript. See dpkg-maintscript-helper(1) and dh_installdeb(1) for details. From the attached log (usually somewhere in the middle...): 0m57.9s ERROR: FAIL: silently overwrites files via directory symlinks: /usr/share/doc/python-zookeeper/changelog.Debian.gz (python-zookeeper) != /usr/share/doc/libzookeeper-mt2/changelog.Debian.gz (libzookeeper-mt2:amd64) /usr/share/doc/python-zookeeper/changelog.gz (python-zookeeper) != /usr/share/doc/libzookeeper-mt2/changelog.gz (libzookeeper-mt2:amd64) /usr/share/doc/python-zookeeper/copyright (python-zookeeper) != /usr/share/doc/libzookeeper-mt2/copyright (libzookeeper-mt2:amd64) cheers, Andreas python-txzookeeper_0.9.8-1.log.gz Description: application/gzip
Bug#734505: Can we close twitter-recess bug #734505?
still doesn't work for me in current unstable. The less version is still the same.
Processed: Re: Bug#768245: opendnssec-enforcer-{sqlite3, mysql}: unhandled symlink to directory conversion: /usr/share/doc/PACKAGE
Processing control commands:
found -1 1:1.4.6-4
Bug #768245 {Done: Ondřej Surý ond...@debian.org}
[opendnssec-enforcer-sqlite3,opendnssec-enforcer-mysql]
opendnssec-enforcer-{sqlite3, mysql}: unhandled symlink to directory
conversion: /usr/share/doc/PACKAGE
Marked as found in versions opendnssec/1:1.4.6-4; no longer marked as fixed in
versions opendnssec/1:1.4.6-4 and reopened.
severity -1 serious
Bug #768245 [opendnssec-enforcer-sqlite3,opendnssec-enforcer-mysql]
opendnssec-enforcer-{sqlite3, mysql}: unhandled symlink to directory
conversion: /usr/share/doc/PACKAGE
Severity set to 'serious' from 'important'
tag -1 - moreinfo
Bug #768245 [opendnssec-enforcer-sqlite3,opendnssec-enforcer-mysql]
opendnssec-enforcer-{sqlite3, mysql}: unhandled symlink to directory
conversion: /usr/share/doc/PACKAGE
Removed tag(s) moreinfo.
--
768245: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=768245
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#771612: #771612 python-txzookeeper: unhandled symlink to directory conversion: /usr/share/doc/PACKAGE
reassign 771612 python-zookeeper 3.4.5+dfsg-1 thanks From the attached log (usually somewhere in the middle...): 0m57.9s ERROR: FAIL: silently overwrites files via directory symlinks: /usr/share/doc/python-zookeeper/changelog.Debian.gz (python-zookeeper) != /usr/share/doc/libzookeeper-mt2/changelog.Debian.gz (libzookeeper-mt2:amd64) /usr/share/doc/python-zookeeper/changelog.gz (python-zookeeper) != /usr/share/doc/libzookeeper-mt2/changelog.gz (libzookeeper-mt2:amd64) /usr/share/doc/python-zookeeper/copyright (python-zookeeper) != /usr/share/doc/libzookeeper-mt2/copyright (libzookeeper-mt2:amd64) AFAICT, this was assigned to the wrong package. Reassigning to python-zookeeper Thanks! -- Andrew Starr-Bochicchio Ubuntu Developer https://launchpad.net/~andrewsomething Debian Developer http://qa.debian.org/developer.php?login=asb PGP/GPG Key ID: D53FDCB1 -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed: #771612 python-txzookeeper: unhandled symlink to directory conversion: /usr/share/doc/PACKAGE
Processing commands for cont...@bugs.debian.org: reassign 771612 python-zookeeper 3.4.5+dfsg-1 Bug #771612 [python-txzookeeper] python-txzookeeper: unhandled symlink to directory conversion: /usr/share/doc/PACKAGE Bug reassigned from package 'python-txzookeeper' to 'python-zookeeper'. No longer marked as found in versions txzookeeper/0.9.8-1. Ignoring request to alter fixed versions of bug #771612 to the same values previously set Bug #771612 [python-zookeeper] python-txzookeeper: unhandled symlink to directory conversion: /usr/share/doc/PACKAGE Marked as found in versions zookeeper/3.4.5+dfsg-1. thanks Stopping processing here. Please contact me if you need assistance. -- 771612: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=771612 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
