Bug#768922: [Debian-ha-maintainers] pacemaker in jessie
the libqb0 version 0.17.0-2 compiled on jessie out of the box. so that should be quick and easy. who is going to do it? In https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=768922#35 Jonathan Wiltshire (member of the release team) stated that migrating libqb isn't an option. And the pacemaker reversion did not happen either. Lacking direction, other people couldn't do anything about this either. Ok. but what i do not understand: as it seems libqb is only used by pacemaker and its daemons only anyway. so even if it is not as clean as one would wish for: why cant we still have it? as i said: it compiled fine and with that library all the pacemaker stuff seems to work well. i would say it is better to have pacemaker then to not have it in the distribution... mond -- ~~ .Franz Schaefer GPG KeyID: CFA2F632 .. +43 699 106 14 590 +43 720502048 Fingerprint: 57C2 C0CC ... schae...@mond.at 6F0A 54C7 0D88 D37E ... http://www.mond.at/ C17C CB16 CFA2 F632 -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#780101: marked as done (librest: Invalid pointer dereference)
Your message dated Mon, 09 Mar 2015 13:34:33 + with message-id e1yuxpj-0007rc...@franck.debian.org and subject line Bug#780101: fixed in librest 0.7.92-3 has caused the Debian Bug report #780101, regarding librest: Invalid pointer dereference 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.) -- 780101: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=780101 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: librest Severity: grave Tags: security Justification: user security hole The following fix was identified to be a security-relevant: https://bugzilla.gnome.org/show_bug.cgi?id=742644 Please see Florian's CVE request for further information: http://www.openwall.com/lists/oss-security/2015/03/04/6 Fix: https://git.gnome.org/browse/librest/commit/?id=b50ace7738ea038 Cheers, Moritz ---End Message--- ---BeginMessage--- Source: librest Source-Version: 0.7.92-3 We believe that the bug you reported is fixed in the latest version of librest, 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 780...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Ying-Chun Liu (PaulLiu) paul...@debian.org (supplier of updated librest 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: Mon, 09 Mar 2015 21:01:02 +0800 Source: librest Binary: librest-0.7-0 librest-0.7-0-dbg librest-dev gir1.2-rest-0.7 librest-doc librest-extras-0.7-0 librest-extras-dev gir1.2-rest-extras-0.7 Architecture: source i386 all Version: 0.7.92-3 Distribution: unstable Urgency: medium Maintainer: Ying-Chun Liu (PaulLiu) paul...@debian.org Changed-By: Ying-Chun Liu (PaulLiu) paul...@debian.org Description: gir1.2-rest-0.7 - REST service access library (introspection files) gir1.2-rest-extras-0.7 - REST service access library extra components (introspectionfiles) librest-0.7-0 - REST service access library librest-0.7-0-dbg - REST service access library (Debug files) librest-dev - REST service access library (development headers) librest-doc - REST service access library (documentation) librest-extras-0.7-0 - REST service access library extra components librest-extras-dev - REST service access library extra components (development headers Closes: 780101 Changes: librest (0.7.92-3) unstable; urgency=medium . * Add debian/patches/03_fix_invalid_pointer_reference.patch - fix invalid pointer dereference (Closes: #780101) Checksums-Sha1: 3f42f2083fcf95234f26a36cca84570a10c57b1f 2435 librest_0.7.92-3.dsc 46051789e24909e81d3066300c5097f419b63d9a 7064 librest_0.7.92-3.debian.tar.xz 9936c5b326e9f170c299a24fb3a68ebcb1c6e4d6 34510 librest-0.7-0_0.7.92-3_i386.deb 562b155ca1e5bb7775563a22c941a1d480b33c20 92930 librest-0.7-0-dbg_0.7.92-3_i386.deb 62e83d185c0bd40cd2c42861e49595c7fa9bfc75 30650 librest-dev_0.7.92-3_i386.deb 3cd8829a40f5fe1ce74582391354ea789df176de 9470 gir1.2-rest-0.7_0.7.92-3_i386.deb 55a52f0e08345ece1353aa917b2764c13b0ef1e9 36576 librest-doc_0.7.92-3_all.deb f4bad6a66149d4f37321552ac54da9a2066a93d6 15270 librest-extras-0.7-0_0.7.92-3_i386.deb b0beea99c9e021894d478f5f57d824115ebe72b2 9260 librest-extras-dev_0.7.92-3_i386.deb 13d275cd318e89867b283df93cd7f48be4639c14 6224 gir1.2-rest-extras-0.7_0.7.92-3_i386.deb Checksums-Sha256: 740036f34964ebb87e7bb3a25cf4e44e25c02a263d05f5fc81d5e7deaadce662 2435 librest_0.7.92-3.dsc 6cb8c1b6db64c624892b4baab68035aedc69ac371a8282ffc1fc2febae2ac393 7064 librest_0.7.92-3.debian.tar.xz 4ade8af4bb3602feb8380cfd1b13360def0a56d9a43695c55f4c3edc179b2926 34510 librest-0.7-0_0.7.92-3_i386.deb 1fb0db7537e73cc27317ee573015c2d598e5468a7034e59628212c251d6c300f 92930 librest-0.7-0-dbg_0.7.92-3_i386.deb 149bb8eb61a1dd80841dfdde0e59e9578116ea3bae010a358b79a171a8588bbd 30650 librest-dev_0.7.92-3_i386.deb 20464177ddfd158558e894df0fb712d0d04a57c155da3819a2c172a280798684 9470 gir1.2-rest-0.7_0.7.92-3_i386.deb 73920a3385a5ebf61d9f412d3573322dceddb97ebe064194bb4441f52564e547 36576 librest-doc_0.7.92-3_all.deb 605232877aa689bad4a053f7c5b4f21c7119b9b0591e04a7c1f6381107a57e68 15270 librest-extras-0.7-0_0.7.92-3_i386.deb
Bug#779048: libjpeg-turbo: Migration of jpeg-progs from Wheezy to Jessie
Hmm, there's something fishy going on.
Installing jhead (Depends: libjpeg-progs) on wheezy and dist-upgrading
to jessie tries to remove jhead instead of pulling libjpeg-turbo-progs.
Installing jhead manually after dist-upgrade works fine.
Looks like we will need transitional package after all to satisfy
dependency resolver correctly :(.
O.
On Sun, Mar 8, 2015, at 19:58, Ondřej Surý wrote:
On Sun, Mar 8, 2015, at 17:47, Niels Thykier wrote:
On 2015-03-08 16:47, Ondřej Surý wrote:
Hi Niels,
what if I just do:
Package: libjpeg62-turbo
[...]
Conflicts: libjpeg-progs ( 2:0), libjpeg-progs ( 1:0)
(or more precise Conflicts: libjpeg-progs ( ${binary:Version},
libjpeg-progs ( ${binary:Version})
That should push libjpeg-progs from other sources out
Cheers,
Ondrej
[...]
Seems reasonable at first glance. Can you upload that to tpu
Done.
(with a no-change upload to sid to ensure the tpu version is = than sid)?
Done. (Since we are stuck to t-p-u now, I could probably bring 1.4.0
from experimental to unstable now, but let's leave it after the dust
settles...)
That way we force Wheezy (and testing) to force migrate into turbo
without breaking co-installability with libjpeg's progs (and therefore
avoid any political fall-out with other interested parties).
We should definitely solve this after jessie is out.
It will leave unstable users with the current progs. However, I
consider that less of a problem, given they can pull updates to that
implementation via unstable (unlike pure Jessie users).
True.
O.
--
Ondřej Surý ond...@sury.org
Knot DNS (https://www.knot-dns.cz/) – a high-performance DNS server
--
Ondřej Surý ond...@sury.org
Knot DNS (https://www.knot-dns.cz/) – a high-performance DNS server
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#775842: marked as done (moodle: Multiple security issues)
Your message dated Mon, 09 Mar 2015 12:04:35 + with message-id e1yuwqf-0005gg...@franck.debian.org and subject line Bug#775842: fixed in moodle 2.7.5+dfsg-3 has caused the Debian Bug report #775842, regarding moodle: Multiple security issues 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.) -- 775842: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=775842 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: moodle Severity: grave Tags: security Justification: user security hole The current Moodle package in the archive is affected by multiple security issues: Cheers, Moritz https://security-tracker.debian.org/tracker/CVE-2015-0218 https://security-tracker.debian.org/tracker/CVE-2015-0217 https://security-tracker.debian.org/tracker/CVE-2015-0216 https://security-tracker.debian.org/tracker/CVE-2015-0215 https://security-tracker.debian.org/tracker/CVE-2015-0214 https://security-tracker.debian.org/tracker/CVE-2015-0213 https://security-tracker.debian.org/tracker/CVE-2015-0212 https://security-tracker.debian.org/tracker/CVE-2015-0211 https://security-tracker.debian.org/tracker/CVE-2014-9059 https://security-tracker.debian.org/tracker/CVE-2014-7848 https://security-tracker.debian.org/tracker/CVE-2014-7847 https://security-tracker.debian.org/tracker/CVE-2014-7846 https://security-tracker.debian.org/tracker/CVE-2014-7845 https://security-tracker.debian.org/tracker/CVE-2014-7838 https://security-tracker.debian.org/tracker/CVE-2014-7837 https://security-tracker.debian.org/tracker/CVE-2014-7836 https://security-tracker.debian.org/tracker/CVE-2014-7835 https://security-tracker.debian.org/tracker/CVE-2014-7834 https://security-tracker.debian.org/tracker/CVE-2014-7833 https://security-tracker.debian.org/tracker/CVE-2014-7832 https://security-tracker.debian.org/tracker/CVE-2014-7831 https://security-tracker.debian.org/tracker/CVE-2014-7830 https://security-tracker.debian.org/tracker/CVE-2014-4172 https://security-tracker.debian.org/tracker/CVE-2014-3617 https://security-tracker.debian.org/tracker/CVE-2014-3553 https://security-tracker.debian.org/tracker/CVE-2014-3551 https://security-tracker.debian.org/tracker/CVE-2014-3548 https://security-tracker.debian.org/tracker/CVE-2014-3547 https://security-tracker.debian.org/tracker/CVE-2014-3546 https://security-tracker.debian.org/tracker/CVE-2014-3545 https://security-tracker.debian.org/tracker/CVE-2014-3544 https://security-tracker.debian.org/tracker/CVE-2014-3543 https://security-tracker.debian.org/tracker/CVE-2014-3542 https://security-tracker.debian.org/tracker/CVE-2014-3541 https://security-tracker.debian.org/tracker/CVE-2014-2054 https://security-tracker.debian.org/tracker/CVE-2013-3630 ---End Message--- ---BeginMessage--- Source: moodle Source-Version: 2.7.5+dfsg-3 We believe that the bug you reported is fixed in the latest version of moodle, 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 775...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Joost van Baal-Ilić joos...@debian.org (supplier of updated moodle 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: Mon, 09 Mar 2015 12:56:41 +0100 Source: moodle Binary: moodle Architecture: source all Version: 2.7.5+dfsg-3 Distribution: unstable Urgency: high Maintainer: Moodle Packaging Team pkg-moodle-maintain...@lists.alioth.debian.org Changed-By: Joost van Baal-Ilić joos...@debian.org Description: moodle - course management system for online learning Closes: 775842 Changes: moodle (2.7.5+dfsg-3) unstable; urgency=high . * debian/README.Debian: add authors and dates, in order to make status more clear. * debian/watch: (trying to) get it working again, with revamped moodle.org website. * debian/changelog: add even more CVE-numbers to entry 2.7.5+dfsg-1. * For the record, https://security-tracker.debian.org/tracker/CVE-2013-3630 will not get fixed: it's not a bug: the attack can only get launched by an administrator, and administrators need to be trusted. See also Debian bug #775842. * Fix CVE-2014-4172 and CVE-2014-2054: - debian/rules, debian/control:
Bug#780102: libjbcrypt-java: CVE-2015-0886
Thank you for the report Moritz. According to the Bugzilla report the issue happens when BCrypt.gensalt() is called with the value 31. jenkins is the only package using this library and it calls this method with no parameter [1], the default value being 10 [2]. So I don't think this issue is critical for Jessie. Emmanuel Bourg [1] https://sources.debian.net/src/jenkins/1.565.3-3/core/src/main/java/hudson/security/HudsonPrivateSecurityRealm.java/#L645 [2] https://sources.debian.net/src/libjbcrypt-java/0.3-4/BCrypt.java/#L66 -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed: found 780101 in 0.7.92-2
Processing commands for cont...@bugs.debian.org: found 780101 0.7.92-2 Bug #780101 [librest] librest: Invalid pointer dereference There is no source info for the package 'librest' at version '0.7.92-2' with architecture '' Unable to make a source version for version '0.7.92-2' Marked as found in versions 0.7.92-2. thanks Stopping processing here. Please contact me if you need assistance. -- 780101: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=780101 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#779825: no port attached to webserver
Hello. Maybe you don't have IPv6 at all configured, not even in the lo interface? Whats the output of ip -6 addr? Thanks! -- Ivan Baldo - iba...@adinet.com.uy - http://ibaldo.codigolibre.net/ From Montevideo, Uruguay, at the south of South America. Freelance programmer and GNU/Linux system administrator, hire me! Alternatives: iba...@codigolibre.net - http://go.to/ibaldo -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed: tagging 780101
Processing commands for cont...@bugs.debian.org: tags 780101 + upstream fixed-upstream Bug #780101 [librest] librest: Invalid pointer dereference Added tag(s) upstream and fixed-upstream. thanks Stopping processing here. Please contact me if you need assistance. -- 780101: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=780101 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#779825: no port attached to webserver
Hi Ivan, The output is :- $ ip -6 addr $ On 3/9/15, Ivan Baldo iba...@adinet.com.uy wrote: Hello. Maybe you don't have IPv6 at all configured, not even in the lo interface? Whats the output of ip -6 addr? Thanks! -- Ivan Baldo - iba...@adinet.com.uy - http://ibaldo.codigolibre.net/ From Montevideo, Uruguay, at the south of South America. Freelance programmer and GNU/Linux system administrator, hire me! Alternatives: iba...@codigolibre.net - http://go.to/ibaldo -- Regards, Shirish Agarwal शिरीष अग्रवाल My quotes in this email licensed under CC 3.0 http://creativecommons.org/licenses/by-nc/3.0/ http://flossexperiences.wordpress.com EB80 462B 08E1 A0DE A73A 2C2F 9F3D C7A4 E1C4 D2D8 -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#780101: unblock: librest/0.7.92-3
Package: release.debian.org User: release.debian@packages.debian.org Usertags: unblock Severity: normal Please unblock package librest (explain the reason for the unblock here) # explain why you want this change included. Bug numbers are a must. I fix RC bug #780101 (grave) # include the changelog entry/entries in the request librest (0.7.92-3) unstable; urgency=medium * Add debian/patches/03_fix_invalid_pointer_reference.patch - fix invalid pointer dereference (Closes: #780101) -- Ying-Chun Liu (PaulLiu) paul...@debian.org Mon, 09 Mar 2015 21:01:02 +0800 # include a debdiff between the testing version of the package and the version you uploaded (or is about to upload) As attachment. (include/attach the debdiff against the package in testing) unblock librest/0.7.92-3 -- System Information: Debian Release: 8.0 APT prefers testing APT policy: (500, 'testing') Architecture: i386 (i686) Kernel: Linux 3.16.0-4-686-pae (SMP w/2 CPU cores) Locale: LANG=C, LC_CTYPE=C (charmap=UTF-8) (ignored: LC_ALL set to zh_TW.UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) -- PaulLiu (劉穎駿) E-mail: Ying-Chun Liu (PaulLiu) paul...@debian.org diff -Nru librest-0.7.92/debian/changelog librest-0.7.92/debian/changelog --- librest-0.7.92/debian/changelog 2014-10-23 22:40:41.0 +0800 +++ librest-0.7.92/debian/changelog 2015-03-09 21:01:56.0 +0800 @@ -1,3 +1,10 @@ +librest (0.7.92-3) unstable; urgency=medium + + * Add debian/patches/03_fix_invalid_pointer_reference.patch +- fix invalid pointer dereference (Closes: #780101) + + -- Ying-Chun Liu (PaulLiu) paul...@debian.org Mon, 09 Mar 2015 21:01:02 +0800 + librest (0.7.92-2) unstable; urgency=medium * Add debian/patches/02_thread-tests-sleep-for-server-to-start.patch diff -Nru librest-0.7.92/debian/patches/03_fix_invalid_pointer_reference.patch librest-0.7.92/debian/patches/03_fix_invalid_pointer_reference.patch --- librest-0.7.92/debian/patches/03_fix_invalid_pointer_reference.patch 1970-01-01 08:00:00.0 +0800 +++ librest-0.7.92/debian/patches/03_fix_invalid_pointer_reference.patch 2015-03-09 21:00:57.0 +0800 @@ -0,0 +1,18 @@ +From: Christophe Fergeau cferg...@redhat.com +Description: oauth: Add missing include + This fixes a compilation warning about a missing prototype. +Origin: upstream, https://git.gnome.org/browse/librest/commit/?id=b50ace7738ea038 +Bug: https://bugzilla.gnome.org/show_bug.cgi?id=742644 +Bug-Debian: https://bugs.debian.org/780101 +Index: librest-0.7.92/rest/oauth-proxy-call.c +=== +--- librest-0.7.92.orig/rest/oauth-proxy-call.c librest-0.7.92/rest/oauth-proxy-call.c +@@ -25,6 +25,7 @@ + #include rest/rest-proxy-call.h + #include oauth-proxy-call.h + #include oauth-proxy-private.h ++#include rest-proxy-call-private.h + #include sha1.h + + G_DEFINE_TYPE (OAuthProxyCall, oauth_proxy_call, REST_TYPE_PROXY_CALL) diff -Nru librest-0.7.92/debian/patches/series librest-0.7.92/debian/patches/series --- librest-0.7.92/debian/patches/series 2014-10-23 22:30:42.0 +0800 +++ librest-0.7.92/debian/patches/series 2015-03-09 20:56:35.0 +0800 @@ -1,2 +1,3 @@ 01_disable-network-tests.patch 02_thread-tests-sleep-for-server-to-start.patch +03_fix_invalid_pointer_reference.patch signature.asc Description: OpenPGP digital signature
Bug#779825: no port attached to webserver
Hello Shirish! Good news, thats it, you don't have IPv6 at all configured, not even for the loopback interface, which is a pretty non standard setup nowadays so be careful, other services could act badly. I don't know what the Policy document says about this situation, but shouldn't the install succeed even if Nginx couldn't be started? For example, suppose that I want to remove all IPv6 support from a server, I think the package should install correctly anyway and let me fix the configuration later myself to avoid listening on IPv6 and listen only in IPv4. Or what happens if I have something else listening on port 80 (a reverse proxy for example) and I want to install Nginx and then change it to listen on port 81 instead? This is not a bug on _installation_ but on _startup_, there's a difference. Of course this is my own personal opinion and haven't read the Policy document in years... Thanks all, have a great day everybody! El 09/03/15 a las 09:59, shirish शिरीष escibió: Hi Ivan, The output is :- $ ip -6 addr $ On 3/9/15, Ivan Baldo iba...@adinet.com.uy wrote: Hello. Maybe you don't have IPv6 at all configured, not even in the lo interface? Whats the output of ip -6 addr? Thanks! -- Ivan Baldo - iba...@adinet.com.uy - http://ibaldo.codigolibre.net/ From Montevideo, Uruguay, at the south of South America. Freelance programmer and GNU/Linux system administrator, hire me! Alternatives: iba...@codigolibre.net - http://go.to/ibaldo -- Ivan Baldo - iba...@adinet.com.uy - http://ibaldo.codigolibre.net/ From Montevideo, Uruguay, at the south of South America. Freelance programmer and GNU/Linux system administrator, hire me! Alternatives: iba...@codigolibre.net - http://go.to/ibaldo -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#780101: librest: Invalid pointer dereference
Moritz Muehlenhoff 於 2015年03月09日 18:31 寫道: Package: librest Severity: grave Tags: security Justification: user security hole The following fix was identified to be a security-relevant: https://bugzilla.gnome.org/show_bug.cgi?id=742644 Please see Florian's CVE request for further information: http://www.openwall.com/lists/oss-security/2015/03/04/6 Fix: https://git.gnome.org/browse/librest/commit/?id=b50ace7738ea038 Cheers, Moritz I'll fix this soon. -- PaulLiu (劉穎駿) E-mail: Ying-Chun Liu (PaulLiu) paul...@debian.org diff -Nru librest-0.7.92/debian/changelog librest-0.7.92/debian/changelog --- librest-0.7.92/debian/changelog 2014-10-23 22:40:41.0 +0800 +++ librest-0.7.92/debian/changelog 2015-03-09 21:01:56.0 +0800 @@ -1,3 +1,10 @@ +librest (0.7.92-3) unstable; urgency=medium + + * Add debian/patches/03_fix_invalid_pointer_reference.patch +- fix invalid pointer dereference (Closes: #780101) + + -- Ying-Chun Liu (PaulLiu) paul...@debian.org Mon, 09 Mar 2015 21:01:02 +0800 + librest (0.7.92-2) unstable; urgency=medium * Add debian/patches/02_thread-tests-sleep-for-server-to-start.patch diff -Nru librest-0.7.92/debian/patches/03_fix_invalid_pointer_reference.patch librest-0.7.92/debian/patches/03_fix_invalid_pointer_reference.patch --- librest-0.7.92/debian/patches/03_fix_invalid_pointer_reference.patch 1970-01-01 08:00:00.0 +0800 +++ librest-0.7.92/debian/patches/03_fix_invalid_pointer_reference.patch 2015-03-09 21:00:57.0 +0800 @@ -0,0 +1,18 @@ +From: Christophe Fergeau cferg...@redhat.com +Description: oauth: Add missing include + This fixes a compilation warning about a missing prototype. +Origin: upstream, https://git.gnome.org/browse/librest/commit/?id=b50ace7738ea038 +Bug: https://bugzilla.gnome.org/show_bug.cgi?id=742644 +Bug-Debian: https://bugs.debian.org/780101 +Index: librest-0.7.92/rest/oauth-proxy-call.c +=== +--- librest-0.7.92.orig/rest/oauth-proxy-call.c librest-0.7.92/rest/oauth-proxy-call.c +@@ -25,6 +25,7 @@ + #include rest/rest-proxy-call.h + #include oauth-proxy-call.h + #include oauth-proxy-private.h ++#include rest-proxy-call-private.h + #include sha1.h + + G_DEFINE_TYPE (OAuthProxyCall, oauth_proxy_call, REST_TYPE_PROXY_CALL) diff -Nru librest-0.7.92/debian/patches/series librest-0.7.92/debian/patches/series --- librest-0.7.92/debian/patches/series 2014-10-23 22:30:42.0 +0800 +++ librest-0.7.92/debian/patches/series 2015-03-09 20:56:35.0 +0800 @@ -1,2 +1,3 @@ 01_disable-network-tests.patch 02_thread-tests-sleep-for-server-to-start.patch +03_fix_invalid_pointer_reference.patch signature.asc Description: OpenPGP digital signature
Bug#775630: closing 775630
close 775630 thanks See http://lists.alioth.debian.org/pipermail/pkg-mysql-maint/2015-March/007624.html -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed: closing 775630
Processing commands for cont...@bugs.debian.org: close 775630 Bug #775630 [src:mysql-5.5] mysql-5.5: FTBFS in jessie: make[4]: *** [CMakeFiles/abi_check] Error 1 Marked Bug as done thanks Stopping processing here. Please contact me if you need assistance. -- 775630: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=775630 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#760998: [Pkg-utopia-maintainers] Bug#760998: Acknowledgement (network-manager: auto restarts)
On Mon, 2015-03-09 at 09:13 +0100, Michael Biebl wrote: Am 19.02.2015 um 07:35 schrieb Kurt Roeckx: severity 760998 serious thanks At this point I'm unable to stop network manager and keep it stopped. Now I have 0.9.10.0-6. The log file shows: NetworkManager[15359]: info exiting (success) systemd[1]: Stopped Network Manager. dbus[658]: [system] Activating via systemd: service name='org.freedesktop.NetworkManager' unit='dbus-org.freedesktop.NetworkManager.service' systemd[1]: Starting Network Manager... dbus[658]: [system] Successfully activated service 'org.freedesktop.nm_dispatcher' systemd[1]: Started Network Manager Script Dispatcher Service. NetworkManager[20467]: info NetworkManager (version 0.9.10.0) is starting... I assume something else restarts it, but I have no idea what. Is there some way to debug this so I can reassign it? It's most likely D-Bus activated, e.g. by nm-applet. Atm, you need to run systemctl disable NetworkManager.service; systemctl stop NetworkManager.service; do stuff; systemctl start NetworkManager.service; systemctl enable NetworkManager.service. Dan, is dropping the D-Bus autoactivation safe, i.e. removing /usr/share/dbus-1/system-services/org.freedesktop.NetworkManager.service? Yeah, it's safe, though it might slightly slow your bootup for some reason I don't remember. Something about not being able to parallelize bootup, because if something calls NM methods via D-Bus, systemd won't be able to activate NM and block the receiving process until NM starts, so the receiving process will just get an error instead of waiting. But I guess that's supposed to be the current situation too with our Exec=/bin/false hack that hasn't worked in a while. It's worth a try to remove that file, and change the systemd unit file's [install] section to remove the Alias. Let me know if that breaks bootup horribly or something? Dan -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#760998: [Pkg-utopia-maintainers] Bug#760998: Bug#760998: Acknowledgement (network-manager: auto restarts)
Thanks for the reply Dan! Am 09.03.2015 um 15:41 schrieb Dan Williams: On Mon, 2015-03-09 at 09:13 +0100, Michael Biebl wrote: Dan, is dropping the D-Bus autoactivation safe, i.e. removing /usr/share/dbus-1/system-services/org.freedesktop.NetworkManager.service? Yeah, it's safe, though it might slightly slow your bootup for some reason I don't remember. Something about not being able to parallelize bootup, because if something calls NM methods via D-Bus, systemd won't be able to activate NM and block the receiving process until NM starts, so the receiving process will just get an error instead of waiting. But I guess that's supposed to be the current situation too with our Exec=/bin/false hack that hasn't worked in a while. It's worth a try to remove that file, and change the systemd unit file's [install] section to remove the Alias. Let me know if that breaks bootup horribly or something? I guess I'll do that then. If it's only about a slight speed improvement, I think we can live with that. I wasn't sure, if some clients (like gdm) would fail, if the NM D-Bus name is not present. -- 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#779931: [Pkg-utopia-maintainers] Bug#779931: sk_disk_check_sleep_mode: Operation not supported for USB3 HDD docking based on JMicron 152d:0551
On Fri, 06 Mar 2015 16:06:24 0100 Michael Biebl wrote: If checking the SMART state of the sleeping disk resets the USB connection, then this sounds like a kernel bug. I've just tried to install a lot of kernels (from 3.2.65 to 3.19) but I've always seen the reset of the USB connection while the HDs were mounted. I've also tried to install the new versions of udisks2 (2.1.4-1 and 2.1.5-1) because I've seen a workaround to this issue (IS: #1281588) but using these versions I noticed other serious issues (for ex. I can't mount a partition when the HDs are gone to sleep mode). If the problem is the kernel, can you suggest me a way to debug this issue? Thanks... Gianluca Connetti gratis il mondo con la nuova indoona: hai la chat, le chiamate, le video chiamate e persino le chiamate di gruppo. E chiami gratis anche i numeri fissi e mobili nel mondo! Scarica subito l’app Vai su https://www.indoona.com/ -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#779825: no port attached to webserver
Ok, decided to check current Debian Policy Manual and there isn't a specific mention of what to do when starting a service after dpkg's configuration phase and that service fails. So I guess is up to maintainers of this package to decide. For what is worth, I vote for just continuing anyway and let the sysadmin fix it later, since it surely will see that the webserver isn't starting... Thanks for your consideration! El 09/03/15 a las 10:14, Ivan Baldo escibió: Hello Shirish! Good news, thats it, you don't have IPv6 at all configured, not even for the loopback interface, which is a pretty non standard setup nowadays so be careful, other services could act badly. I don't know what the Policy document says about this situation, but shouldn't the install succeed even if Nginx couldn't be started? For example, suppose that I want to remove all IPv6 support from a server, I think the package should install correctly anyway and let me fix the configuration later myself to avoid listening on IPv6 and listen only in IPv4. Or what happens if I have something else listening on port 80 (a reverse proxy for example) and I want to install Nginx and then change it to listen on port 81 instead? This is not a bug on _installation_ but on _startup_, there's a difference. Of course this is my own personal opinion and haven't read the Policy document in years... Thanks all, have a great day everybody! El 09/03/15 a las 09:59, shirish शिरीष escibió: Hi Ivan, The output is :- $ ip -6 addr $ On 3/9/15, Ivan Baldo iba...@adinet.com.uy wrote: Hello. Maybe you don't have IPv6 at all configured, not even in the lo interface? Whats the output of ip -6 addr? Thanks! -- Ivan Baldo - iba...@adinet.com.uy - http://ibaldo.codigolibre.net/ From Montevideo, Uruguay, at the south of South America. Freelance programmer and GNU/Linux system administrator, hire me! Alternatives: iba...@codigolibre.net - http://go.to/ibaldo -- Ivan Baldo - iba...@adinet.com.uy - http://ibaldo.codigolibre.net/ From Montevideo, Uruguay, at the south of South America. Freelance programmer and GNU/Linux system administrator, hire me! Alternatives: iba...@codigolibre.net - http://go.to/ibaldo -- 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#774643: verify_active_connections is not present in ruby-activerecord 4.1.8
Processing control commands: severity -1 serious Bug #774643 [puppetmaster] Lacking support of exported resources Severity set to 'serious' from 'important' -- 774643: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=774643 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#779112: marked as done (libjnr-constants-java, libconstantine-java: error when trying to install together)
Your message dated Mon, 9 Mar 2015 16:11:29 + with message-id 1f3cfa9e-e967-484d-9f06-9822dfe6c...@hp.com and subject line has caused the Debian Bug report #779112, regarding libjnr-constants-java, libconstantine-java: error when trying to install together 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.) -- 779112: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=779112 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: libjnr-constants-java,libconstantine-java Severity: serious User: trei...@debian.org Usertags: edos-file-overwrite Architecture: amd64 Distribution: sid + experimental Hi, automatic installation tests of packages that share a file and at the same time do not conflict by their package dependency relationships has detected the following problem: Selecting previously unselected package libconstantine-java. Preparing to unpack .../libconstantine-java_0.8.5-1_all.deb ... Unpacking libconstantine-java (0.8.5-1) ... dpkg: error processing archive /var/cache/apt/archives/libconstantine-java_0.8.5-1_all.deb (--unpack): trying to overwrite '/usr/share/java/jnr-constants.jar', which is also in package libjnr-constants-java 0.8.6-2 dpkg-deb: error: subprocess paste was killed by signal (Broken pipe) Errors were encountered while processing: /var/cache/apt/archives/libconstantine-java_0.8.5-1_all.deb This is a serious bug as it makes installation fail, and violates sections 7.6.1 and 10.1 of the policy. An optimal solution would consist in only one of the packages installing that file, and renaming or removing the file in the other package. Depending on the circumstances you might also consider Replace relations or file diversions. If the conflicting situation cannot be resolved then, as a last resort, the two packages have to declare a mutual Conflict. Please take into account that Replaces, Conflicts and diversions should only be used when packages provide different implementations for the same functionality. Here is a list of files that are known to be shared by both packages (according to the Contents file for sid/amd64, which may be slightly out of sync): usr/share/java/constantine.jar usr/share/java/jnr-constants.jar usr/share/java/libconstantine.jar usr/share/maven-repo/com/github/jnr/jnr-constants/debian/jnr-constants-debian.jar usr/share/maven-repo/com/github/jnr/jnr-constants/debian/jnr-constants-debian.pom This bug is assigned to both packages. If you, the maintainers of the two packages in question, have agreed on which of the packages will resolve the problem please reassign the bug to that package. You may also register in the BTS that the other package is affected by the bug. Cheers, Andreas PS: for more information about the detection of file overwrite errors of this kind see https://qa.debian.org/dose/file-overwrites.html libjnr-constants-java=0.8.6-2_libconstantine-java=0.8.5-1.log.gz Description: application/gzip ---End Message--- ---BeginMessage--- Closed, this time for sure, by upload of jnr-constants 0.8.6-4.---End Message---
Processed: [bts-link] source package src:lnav
Processing commands for cont...@bugs.debian.org: # # bts-link upstream status pull for source package src:lnav # see http://lists.debian.org/debian-devel-announce/2006/05/msg1.html # user bts-link-upstr...@lists.alioth.debian.org Setting user to bts-link-upstr...@lists.alioth.debian.org (was bts-link-de...@lists.alioth.debian.org). # remote status report for #771203 (http://bugs.debian.org/771203) # Bug title: lnav: FTBFS on mips, powerpc and s390x # * https://github.com/tstack/lnav/issues/123 # * remote status changed: open - closed # * closed upstream tags 771203 + fixed-upstream Bug #771203 [src:lnav] lnav: FTBFS on mips, powerpc and s390x Added tag(s) fixed-upstream. usertags 771203 - status-open Usertags were: status-open. Usertags are now: . usertags 771203 + status-closed There were no usertags set. Usertags are now: status-closed. thanks Stopping processing here. Please contact me if you need assistance. -- 771203: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=771203 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#780139: CVE-2015-0885
Package: checkpw
Severity: grave
Tags: security
Hi Gerrit,
please see
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2015-0885
(feel free to lower the severity, I don't know checkpw myself)
I'm attaching a cleaned-up diff between the 1.03 and 1.02 releases.
Cheers,
Moritz
diff -Naur checkpw-1.02/checkapoppw.c checkpw-1.03/checkapoppw.c
--- checkpw-1.02/checkapoppw.c 2002-01-07 08:25:10.0 +0100
+++ checkpw-1.03/checkapoppw.c 2015-02-21 00:42:57.0 +0100
@@ -85,7 +85,7 @@
pw = getpwnam(login);
if (pw) break;
if (errno == error_txtbsy) die(111);
-for (; ext != login *ext != '-'; --ext);
+do {--ext;} while (ext != login *ext != '-');
if (ext == login) die(1);
if (i) login[i] = '-';
i = ext - login;
diff -Naur checkpw-1.02/checkpw.c checkpw-1.03/checkpw.c
--- checkpw-1.02/checkpw.c 2002-01-07 08:23:51.0 +0100
+++ checkpw-1.03/checkpw.c 2015-02-21 00:42:33.0 +0100
@@ -71,7 +71,7 @@
pw = getpwnam(login);
if (pw) break;
if (errno == error_txtbsy) die(111);
-for (; ext != login *ext != '-'; --ext);
+do {--ext;} while (ext != login *ext != '-');
if (ext == login) die(1);
if (i) login[i] = '-';
i = ext - login;
Bug#746885: nget: ftbfs with GCC-4.9
Dear maintainer, I would like to share a patch that I wrote today, which, applied together with other Debian nget patches, allows nget to be built with gcc-4.9.x. To explain things a little, the problem was due to the overloaded template function new_comparison expecting either 'RetType (ClassType::*member)' or 'RetType (ClassType::*memberf)(void)' as the first argument, while it actually received 'RetType (ClassType::*memberf)(void) const' (e.g, in line 200). Probably (just a guess), earlier gcc versions accepted implicit conversion in such cases (or somehow treated these types as one), but gcc 4.9.x clearly does not. -- Best regards, Alex Potapenko nget-0.27.1-gcc49.patch Description: Binary data
Bug#780101: Bug#780119: unblock: librest/0.7.92-3
On 2015-03-09 14:41, Ying-Chun Liu (PaulLiu) wrote: Package: release.debian.org User: release.debian@packages.debian.org Usertags: unblock Severity: normal Please unblock package librest (explain the reason for the unblock here) # explain why you want this change included. Bug numbers are a must. I fix RC bug #780101 (grave) # include the changelog entry/entries in the request librest (0.7.92-3) unstable; urgency=medium * Add debian/patches/03_fix_invalid_pointer_reference.patch - fix invalid pointer dereference (Closes: #780101) -- Ying-Chun Liu (PaulLiu) paul...@debian.org Mon, 09 Mar 2015 21:01:02 +0800 # include a debdiff between the testing version of the package and the version you uploaded (or is about to upload) As attachment. (include/attach the debdiff against the package in testing) unblock librest/0.7.92-3 [...] Thanks, excellent report! I have unblocked the package. ~Niels -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#779825: no port attached to webserver
at bottom :- On 3/9/15, Ivan Baldo iba...@adinet.com.uy wrote: Ok, decided to check current Debian Policy Manual and there isn't a specific mention of what to do when starting a service after dpkg's configuration phase and that service fails. So I guess is up to maintainers of this package to decide. For what is worth, I vote for just continuing anyway and let the sysadmin fix it later, since it surely will see that the webserver isn't starting... Thanks for your consideration! El 09/03/15 a las 10:14, Ivan Baldo escibió: Hello Shirish! Good news, thats it, you don't have IPv6 at all configured, not even for the loopback interface, which is a pretty non standard setup nowadays so be careful, other services could act badly. I don't know what the Policy document says about this situation, but shouldn't the install succeed even if Nginx couldn't be started? For example, suppose that I want to remove all IPv6 support from a server, I think the package should install correctly anyway and let me fix the configuration later myself to avoid listening on IPv6 and listen only in IPv4. Or what happens if I have something else listening on port 80 (a reverse proxy for example) and I want to install Nginx and then change it to listen on port 81 instead? This is not a bug on _installation_ but on _startup_, there's a difference. Of course this is my own personal opinion and haven't read the Policy document in years... Thanks all, have a great day everybody! Hi all, Can everybody (i.e. Ivan, Norbert and Kartik) can you all reproduce the issue if IPv6 is not set does the installation and configuration fail in that condition. It would be nice if people see if they run into the same issue, then we found the root cause. @Kartik, please see if the issue happens if IPv6 is not configured. If it is please re-word the bug title, rework the severity if you think it should not be an RC bug or/and patch the package. Please let me know what do you want to do so I know what action I need to take my end - a. Wait for you to package a patched version. b. Think of how I can get IPv6 only on the loopback interface 'lo' . This is how I had done it https://wiki.debian.org/DebianIPv6#How_to_turn_off_IPv6 basically ~$ cat /etc/default/grub | grep ipv6 GRUB_CMDLINE_LINUX_DEFAULT=ipv6.disable=1 init=/lib/systemd/systemd -- Regards, Shirish Agarwal शिरीष अग्रवाल My quotes in this email licensed under CC 3.0 http://creativecommons.org/licenses/by-nc/3.0/ http://flossexperiences.wordpress.com EB80 462B 08E1 A0DE A73A 2C2F 9F3D C7A4 E1C4 D2D8 -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#775877: gnome-session: No mouse pointer after login
On 06/03/15 10:00, Simon McVittie wrote:
On Tue, 20 Jan 2015 at 21:43:09 -0500, Aron Podrigal wrote:
Jan 20 16:46:18 jessie gnome-session[1888]:
GLib-GIO:ERROR:/tmp/buildd/glib2.0-2.42.1/./gio/gdbusconnection.c:4231:invoke_set_property_in_idle_cb:
assertion failed: (error != NULL)
This seems likely to be the problem: gnome-settings-daemon crashed with
an assertion failure.
gdbusconnection.c:4231 is the last of the lines I've quoted here:
if (!data-vtable-set_property (data-connection,
g_dbus_message_get_sender (data-message),
g_dbus_message_get_path (data-message),
data-interface_info-name,
data-property_name,
value,
error,
data-user_data))
{
gchar *dbus_error_name;
g_assert (error != NULL);
So the bug here is that something, somewhere in the
gnome-settings-daemon process, has a set_property() callback
that fails without correctly setting the error.
Searching the gnome-settings-daemon source code, the only obvious
possibility is in the power plugin. Aron, please try this and see
whether it works better for you:
https://people.debian.org/~smcv/gnome-settings-daemon_3.14.2-2+smcv1_amd64.deb
Regards,
S
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#776911: gnome-shell: fails to start on i386 when [Mesa was] built with llvm-3.5
On 09/03/15 20:57, Julien Cristau wrote: On Thu, Feb 26, 2015 at 08:54:10 +, Simon McVittie wrote: Context for Mesa maintainers: #775235 is that gnome-shell crashes in an i386 VM with its default choice of emulated CPU, with LLVM ERROR: Do not know how to split the result of this operator!. ... The merged bug #770130 is that gnome-shell crashes on an unknown i386 [...] with Cogl-ERROR **: Failed to create texture 2d due to size/format constraints. The other merged bug #776911 is that gnome-shell crashes on an unknown i386 with Cogl-ERROR **: Failed to create texture 2d due to size/format constraints; that looks like the same thing as #770130. Sounds like there are at least two different issues that should be split... Perhaps. Michael, could you elaborate on your reasoning for believing that #775235 (reproducible, in a VM, presumably with llvmpipe) is the same bug as #770130 (on real hardware, seems to be with i915-family graphics)? #776911 (on real hardware, appears to be with i915-family graphics) looks quite a lot like #770130: both involve Intel graphics chips encountering a pipe A underrun, and GNOME Shell crashing with Cogl-ERROR **: Failed to create texture 2d due to size/format constraints. S -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#776063: marked as done (dbus fails to upgrade rendering entire apt unusable)
Your message dated Mon, 9 Mar 2015 22:19:12 +0100 with message-id 20150309211912.GA8298@crossbow and subject line Close resolved trigger loop bugs has caused the Debian Bug report #771428, regarding dbus fails to upgrade rendering entire apt unusable 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.) -- 771428: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=771428 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: dbus Version: 1.8.12-1 Severity: critical Decided to upgrade my jessie/sid system today to see if remedy for hangouts not working came about (#770659) and upgrade failed because of dbus. Here is an output of (sudo apt-get -f install -y 21 | xsel -i) and I marked with critical severity since now I can't use apt for anything (like build-dep): Reading package lists... Building dependency tree... Reading state information... Correcting dependencies... Done The following packages were automatically installed and are no longer required: glx-alternative-nvidia gnome-js-common libc6-i386 libfreenect0.2 libicc2 libimdi0 libjansson4 libllvm3.4 libnvidia-compiler libqqwing2 libseed-gtk3-0 libtorque2 libts-0.0-0 libxnvctrl0 linux-image-3.16-2-amd64 linux-image-3.16-3-amd64 nvidia-kernel-common nvidia-modprobe nvidia-opencl-common nvidia-support python3-packagekit tsconf Use 'apt-get autoremove' to remove them. The following extra packages will be installed: libpam-systemd The following packages will be upgraded: libpam-systemd Reading changelogs... 1 upgraded, 0 newly installed, 0 to remove and 236 not upgraded. 18 not fully installed or removed. Need to get 0 B/120 kB of archives. After this operation, 4,096 B disk space will be freed. dpkg: dependency problems prevent processing triggers for dbus: dbus depends on libdbus-1-3 (= 1.7.6); however: Package libdbus-1-3:amd64 is not configured yet. dpkg: error processing package dbus (--configure): dependency problems - leaving triggers unprocessed dpkg: dependency problems prevent processing triggers for dbus: dbus depends on libdbus-1-3 (= 1.7.6); however: Package libdbus-1-3:amd64 is not configured yet. dpkg: error processing package dbus (--configure): dependency problems - leaving triggers unprocessed dpkg: dependency problems prevent processing triggers for dbus: dbus depends on libdbus-1-3 (= 1.7.6); however: Package libdbus-1-3:amd64 is not configured yet. dpkg: error processing package dbus (--configure): dependency problems - leaving triggers unprocessed dpkg: dependency problems prevent processing triggers for dbus: dbus depends on libdbus-1-3 (= 1.7.6); however: Package libdbus-1-3:amd64 is not configured yet. dpkg: error processing package dbus (--configure): dependency problems - leaving triggers unprocessed dpkg: dependency problems prevent processing triggers for dbus: dbus depends on libdbus-1-3 (= 1.7.6); however: Package libdbus-1-3:amd64 is not configured yet. dpkg: error processing package dbus (--configure): dependency problems - leaving triggers unprocessed dpkg: dependency problems prevent processing triggers for dbus: dbus depends on libdbus-1-3 (= 1.7.6); however: Package libdbus-1-3:amd64 is not configured yet. dpkg: error processing package dbus (--configure): dependency problems - leaving triggers unprocessed dpkg: dependency problems prevent processing triggers for dbus: dbus depends on libdbus-1-3 (= 1.7.6); however: Package libdbus-1-3:amd64 is not configured yet. dpkg: error processing package dbus (--configure): dependency problems - leaving triggers unprocessed dpkg: dependency problems prevent processing triggers for dbus: dbus depends on libdbus-1-3 (= 1.7.6); however: Package libdbus-1-3:amd64 is not configured yet. dpkg: error processing package dbus (--configure): dependency problems - leaving triggers unprocessed dpkg: dependency problems prevent processing triggers for dbus: dbus depends on libdbus-1-3 (= 1.7.6); however: Package libdbus-1-3:amd64 is not configured yet. dpkg: error processing package dbus (--configure): dependency problems - leaving triggers unprocessed dpkg: dependency problems prevent processing triggers for dbus: dbus depends on libdbus-1-3 (= 1.7.6); however: Package libdbus-1-3:amd64 is not configured yet. dpkg: error processing package dbus (--configure): dependency problems - leaving triggers unprocessed dpkg: dependency problems prevent processing triggers for dbus: dbus depends on libdbus-1-3 (= 1.7.6); however: Package libdbus-1-3:amd64 is not
Bug#779933: marked as done (python-qgis: fails to install, trying to overwrite other packages files: /usr/lib/python2.7/dist-packages/pyspatialite/dump.py)
Your message dated Mon, 09 Mar 2015 19:35:40 + with message-id e1yv3sm-0003px...@franck.debian.org and subject line Bug#779933: fixed in qgis 2.8.1+dfsg1-1~exp2 has caused the Debian Bug report #779933, regarding python-qgis: fails to install, trying to overwrite other packages files: /usr/lib/python2.7/dist-packages/pyspatialite/dump.py 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.) -- 779933: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=779933 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: python-qgis Version: 2.8.1+dfsg1-1~exp1 Severity: serious User: debian...@lists.debian.org Usertags: piuparts Hi, during a test with piuparts I noticed your package failed to install because it tries to overwrite other packages files without declaring a Breaks+Replaces relation. See policy 7.6 at https://www.debian.org/doc/debian-policy/ch-relationships.html#s-replaces From the attached log (scroll to the bottom...): Selecting previously unselected package python-qgis. (Reading database ... 16341 files and directories currently installed.) Preparing to unpack .../python-qgis_2.8.1+dfsg1-1~exp1_amd64.deb ... Unpacking python-qgis (2.8.1+dfsg1-1~exp1) ... dpkg: error processing archive /var/cache/apt/archives/python-qgis_2.8.1+dfsg1-1~exp1_amd64.deb (--unpack): trying to overwrite '/usr/lib/python2.7/dist-packages/pyspatialite/dump.py', which is also in package python-pyspatialite 3.0.1-6 Errors were encountered while processing: /var/cache/apt/archives/python-qgis_2.8.1+dfsg1-1~exp1_amd64.deb cheers, Andreas python-qgis_2.8.1+dfsg1-1~exp1.log.gz Description: application/gzip ---End Message--- ---BeginMessage--- Source: qgis Source-Version: 2.8.1+dfsg1-1~exp2 We believe that the bug you reported is fixed in the latest version of qgis, 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 779...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Bas Couwenberg sebas...@debian.org (supplier of updated qgis 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: Mon, 09 Mar 2015 19:19:27 +0100 Source: qgis Binary: qgis qgis-common libqgis-core2.8.1 libqgis-gui2.8.1 libqgis-analysis2.8.1 libqgis-networkanalysis2.8.1 libqgisgrass2.8.1 libqgispython2.8.1 libqgis-customwidgets libqgis-server2.8.1 libqgis-dev qgis-plugin-grass qgis-plugin-grass-common qgis-plugin-globe qgis-plugin-globe-common python-qgis python-qgis-common qgis-providers qgis-providers-common qgis-server qgis-api-doc Architecture: source amd64 all Version: 2.8.1+dfsg1-1~exp2 Distribution: experimental Urgency: medium Maintainer: Debian GIS Project pkg-grass-de...@lists.alioth.debian.org Changed-By: Bas Couwenberg sebas...@debian.org Description: libqgis-analysis2.8.1 - QGIS - shared analysis library libqgis-core2.8.1 - QGIS - shared core library libqgis-customwidgets - QGIS custom widgets for Qt Designer libqgis-dev - QGIS - development files libqgis-gui2.8.1 - QGIS - shared gui library libqgis-networkanalysis2.8.1 - QGIS - shared network analysis library libqgis-server2.8.1 - QGIS - shared server library libqgisgrass2.8.1 - QGIS - shared grass library libqgispython2.8.1 - QGIS - shared Python library python-qgis - Python bindings to QGIS python-qgis-common - Python bindings to QGIS - architecture-independent files qgis - Geographic Information System (GIS) qgis-api-doc - QGIS API documentation qgis-common - QGIS - architecture-independent data qgis-plugin-globe - OSG globe plugin for QGIS qgis-plugin-globe-common - OSG globe plugin for QGIS - architecture-independent data qgis-plugin-grass - GRASS plugin for QGIS qgis-plugin-grass-common - GRASS plugin for QGIS - architecture-independent data qgis-providers - collection of data providers to QGIS qgis-providers-common - collection of data providers to QGIS - architecture-independent f qgis-server - QGIS server providing various OGC services Closes: 779933 Changes: qgis (2.8.1+dfsg1-1~exp2) experimental; urgency=medium . * Don't build internal PySpatiaLite, use Debian package instead. (closes: #779933) * Add patch to fix
Bug#775662: marked as done (oss4: Insufficient validation of USB device descriptors)
Your message dated Mon, 09 Mar 2015 19:50:08 + with message-id e1yv3gm-0005cp...@franck.debian.org and subject line Bug#775662: fixed in oss4 4.2-build2010-2 has caused the Debian Bug report #775662, regarding oss4: Insufficient validation of USB device descriptors 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.) -- 775662: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=775662 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Source: oss4 Version: 4.2-build2006-2 Severity: critical Tags: security [This was originally sent to the security team in 2012 but didn't go further than that. However, the code has not changed at all since then.] In kernel/drv/oss_usb/oss_usb.c: - count_source_controls(), add_controls_for_mixer(), add_controls_for_proc(), add_controls_for_selector(), translate_feature_mask_usb2(), translate_feature_mask(), add_controls_for_feature(), traverse_source_controls(), traverse_target_controls(), setup_legacy_mixer(), get_feature_mask(), mixer_dump() and ossusb_init_audioctl() do not check that descriptors are as long as expected. - setup_legacy_mixer() does not reject invalid source unit numbers. These are arbitrary unsigned bytes but used as an index within an array of length 40. In kernel/drv/oss_usb/ossusb_audio.c: - prepare_altsetting() does not reject altsetting descriptors with an invalid terminal link unit number. - setup_format_I() and setup_format_II() do not check that descriptors are as long as expected. In kernel/drv/oss_usb/ossusb_midi.c: - ossusb_init_midistream() does not check that descriptors are as long as expected. (It requires that an altsetting descriptor is at least 3 bytes long, but may use more than that.) While unit numbers are validated in some places, validation is inconsistent and probably wrong: if (un-source = 0 un-source devc-nunits) if (*d 0 *d devc-nunits) if (portc-terminal_link 0 portc-terminal_link = devc-nunits) An invalid USB device descriptor may cause memory corruption or a crash. I didn't find any case where the driver would copy a lot of data from the device descriptor, but I know people manage to exploit bugs for privilege escalation even though they provide only very limited control over the data to be written. [I just noticed another bug in count_source_controls(): un = devc-units[unit]; d = un-desc; if (un == NULL) return 0; It's a bit late to be checking for a null pointer here. Thankfully this shouldn't cause anything worse than a crash on Linux.] Ben. -- Ben Hutchings The generation of random numbers is too important to be left to chance. - Robert Coveyou signature.asc Description: This is a digitally signed message part ---End Message--- ---BeginMessage--- Source: oss4 Source-Version: 4.2-build2010-2 We believe that the bug you reported is fixed in the latest version of oss4, 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 775...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Samuel Thibault sthiba...@debian.org (supplier of updated oss4 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: Mon, 09 Mar 2015 20:16:31 +0100 Source: oss4 Binary: oss4-base oss4-gtk oss4-dkms oss4-source oss4-dev liboss4-salsa2 liboss4-salsa-dev liboss4-salsa-asound2 Architecture: source all amd64 Version: 4.2-build2010-2 Distribution: unstable Urgency: medium Maintainer: Debian OSS4 Maintainers pkg-oss4-maintain...@lists.alioth.debian.org Changed-By: Samuel Thibault sthiba...@debian.org Description: liboss4-salsa-asound2 - OSS to Alsa compatibility library - binary compatibility symlink liboss4-salsa-dev - OSS to Alsa compatibility library -- development files liboss4-salsa2 - OSS to Alsa compatibility library oss4-base - Open Sound System - base package oss4-dev - Open Sound System - development files oss4-dkms - Open Sound System - DKMS module sources oss4-gtk - Open Sound System - simple GTK2-based mixer control oss4-source - Open Sound System - drivers sources Closes: 775662 Changes: oss4
Processed: bug 775877 is forwarded to https://bugzilla.gnome.org/show_bug.cgi?id=745920
Processing commands for cont...@bugs.debian.org: forwarded 775877 https://bugzilla.gnome.org/show_bug.cgi?id=745920 Bug #775877 [gnome-session] gnome-session: No mouse pointer after login Set Bug forwarded-to-address to 'https://bugzilla.gnome.org/show_bug.cgi?id=745920'. thanks Stopping processing here. Please contact me if you need assistance. -- 775877: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=775877 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed: reassign 775877 to gnome-settings-daemon, found 775877 in 3.14.2-2
Processing commands for cont...@bugs.debian.org: reassign 775877 gnome-settings-daemon Bug #775877 [gnome-session] gnome-session: No mouse pointer after login Bug reassigned from package 'gnome-session' to 'gnome-settings-daemon'. No longer marked as found in versions gnome-session/3.14.0-2. Ignoring request to alter fixed versions of bug #775877 to the same values previously set found 775877 3.14.2-2 Bug #775877 [gnome-settings-daemon] gnome-session: No mouse pointer after login Marked as found in versions gnome-settings-daemon/3.14.2-2. thanks Stopping processing here. Please contact me if you need assistance. -- 775877: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=775877 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#771428: marked as done (apt tries to configure dbus before libdbus-1-3, fails to upgrade)
Your message dated Mon, 9 Mar 2015 22:19:12 +0100 with message-id 20150309211912.GA8298@crossbow and subject line Close resolved trigger loop bugs has caused the Debian Bug report #771428, regarding apt tries to configure dbus before libdbus-1-3, fails to upgrade 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.) -- 771428: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=771428 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: apt Version: 1.0.9.3 Severity: important Dear Maintainer, I'm not sure this should be reported against apt or the involved packages, but since it's the configuration ordering I'm taking a guess at the package manager. I had an issue where an apt full-upgrade (sid-sid) failed without further notice like this: ### (...) Unpacking systemd-sysv (215-7) over (215-6) ... E: Sub-process /usr/bin/dpkg returned an error code (1) ### and then when trying apt-get install -f failed with ### (...) dpkg: dependency problems prevent processing triggers for dbus: dbus depends on libdbus-1-3 (= 1.7.6); however: Package libdbus-1-3:amd64 is not configured yet. dpkg: error processing package dbus (--configure): dependency problems - leaving triggers unprocessed dpkg: dependency problems prevent processing triggers for dbus: dbus depends on libdbus-1-3 (= 1.7.6); however: Package libdbus-1-3:amd64 is not configured yet. (repeats...) dpkg: too many errors, stopping Processing triggers for man-db (2.7.0.2-3) ... Processing triggers for libc-bin (2.19-13) ... Errors were encountered while processing: dbus dbus dbus (repeats...) Processing was halted because there were too many errors. E: Sub-process /usr/bin/dpkg returned an error code (1) ### Which is re-occuring on consecutive apt-get install -f. I needed to manually run dpkg --configure libdbus-1-3:amd64 and then everything seemed to go though ok. The full shell log of actions mentioned are attached. -- Package-specific info: -- apt-config dump -- APT ; APT::Architecture amd64; APT::Build-Essential ; APT::Build-Essential:: build-essential; APT::Install-Recommends 1; APT::Install-Suggests 0; APT::Authentication ; APT::Authentication::TrustCDROM true; APT::NeverAutoRemove ; APT::NeverAutoRemove:: ^firmware-linux.*; APT::NeverAutoRemove:: ^linux-firmware$; APT::NeverAutoRemove:: ^linux-image-3\.16\.0-4-amd64$; APT::NeverAutoRemove:: ^linux-image-3\.16-3-amd64$; APT::NeverAutoRemove:: ^linux-headers-3\.16\.0-4-amd64$; APT::NeverAutoRemove:: ^linux-headers-3\.16-3-amd64$; APT::NeverAutoRemove:: ^linux-image-extra-3\.16\.0-4-amd64$; APT::NeverAutoRemove:: ^linux-image-extra-3\.16-3-amd64$; APT::NeverAutoRemove:: ^linux-signed-image-3\.16\.0-4-amd64$; APT::NeverAutoRemove:: ^linux-signed-image-3\.16-3-amd64$; APT::NeverAutoRemove:: ^kfreebsd-image-3\.16\.0-4-amd64$; APT::NeverAutoRemove:: ^kfreebsd-image-3\.16-3-amd64$; APT::NeverAutoRemove:: ^kfreebsd-headers-3\.16\.0-4-amd64$; APT::NeverAutoRemove:: ^kfreebsd-headers-3\.16-3-amd64$; APT::NeverAutoRemove:: ^gnumach-image-3\.16\.0-4-amd64$; APT::NeverAutoRemove:: ^gnumach-image-3\.16-3-amd64$; APT::NeverAutoRemove:: ^.*-modules-3\.16\.0-4-amd64$; APT::NeverAutoRemove:: ^.*-modules-3\.16-3-amd64$; APT::NeverAutoRemove:: ^.*-kernel-3\.16\.0-4-amd64$; APT::NeverAutoRemove:: ^.*-kernel-3\.16-3-amd64$; APT::NeverAutoRemove:: ^linux-backports-modules-.*-3\.16\.0-4-amd64$; APT::NeverAutoRemove:: ^linux-backports-modules-.*-3\.16-3-amd64$; APT::NeverAutoRemove:: ^linux-tools-3\.16\.0-4-amd64$; APT::NeverAutoRemove:: ^linux-tools-3\.16-3-amd64$; APT::VersionedKernelPackages ; APT::VersionedKernelPackages:: linux-image; APT::VersionedKernelPackages:: linux-headers; APT::VersionedKernelPackages:: linux-image-extra; APT::VersionedKernelPackages:: linux-signed-image; APT::VersionedKernelPackages:: kfreebsd-image; APT::VersionedKernelPackages:: kfreebsd-headers; APT::VersionedKernelPackages:: gnumach-image; APT::VersionedKernelPackages:: .*-modules; APT::VersionedKernelPackages:: .*-kernel; APT::VersionedKernelPackages:: linux-backports-modules-.*; APT::VersionedKernelPackages:: linux-tools; APT::Never-MarkAuto-Sections ; APT::Never-MarkAuto-Sections:: metapackages; APT::Never-MarkAuto-Sections:: restricted/metapackages; APT::Never-MarkAuto-Sections:: universe/metapackages; APT::Never-MarkAuto-Sections:: multiverse/metapackages; APT::Never-MarkAuto-Sections:: oldlibs; APT::Never-MarkAuto-Sections:: restricted/oldlibs; APT::Never-MarkAuto-Sections:: universe/oldlibs; APT::Never-MarkAuto-Sections:: multiverse/oldlibs; APT::Update ; APT::Update::Post-Invoke-Success ;
Bug#774124: marked as done (apt tries to configure dbus before libdbus, fails to upgrade)
Your message dated Mon, 9 Mar 2015 22:19:12 +0100 with message-id 20150309211912.GA8298@crossbow and subject line Close resolved trigger loop bugs has caused the Debian Bug report #771428, regarding apt tries to configure dbus before libdbus, fails to upgrade 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.) -- 771428: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=771428 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: dbus Version: 1.8.12-3 Severity: normal When upgrading from 1.8.12-1 to 1.8.12-3 I get following errors (and dbus is not upgraded) dpkg: dependency problems prevent processing triggers for dbus: dbus depends on libdbus-1-3 (= 1.7.6); however: Package libdbus-1-3:amd64 is not configured yet. dpkg: error processing package dbus (--configure): dependency problems - leaving triggers unprocessed dpkg: dependency problems prevent processing triggers for dbus: dbus depends on libdbus-1-3 (= 1.7.6); however: Package libdbus-1-3:amd64 is not configured yet. dpkg: error processing package dbus (--configure): dependency problems - leaving triggers unprocessed dpkg: dependency problems prevent processing triggers for dbus: dbus depends on libdbus-1-3 (= 1.7.6); however: Package libdbus-1-3:amd64 is not configured yet. dpkg: error processing package dbus (--configure): dependency problems - leaving triggers unprocessed dpkg: dependency problems prevent processing triggers for dbus: dbus depends on libdbus-1-3 (= 1.7.6); however: Package libdbus-1-3:amd64 is not configured yet. dpkg: error processing package dbus (--configure): dependency problems - leaving triggers unprocessed dpkg: dependency problems prevent processing triggers for dbus: dbus depends on libdbus-1-3 (= 1.7.6); however: Package libdbus-1-3:amd64 is not configured yet. dpkg: error processing package dbus (--configure): dependency problems - leaving triggers unprocessed dpkg: dependency problems prevent processing triggers for dbus: dbus depends on libdbus-1-3 (= 1.7.6); however: Package libdbus-1-3:amd64 is not configured yet. dpkg: error processing package dbus (--configure): dependency problems - leaving triggers unprocessed dpkg: dependency problems prevent processing triggers for dbus: dbus depends on libdbus-1-3 (= 1.7.6); however: Package libdbus-1-3:amd64 is not configured yet. dpkg: error processing package dbus (--configure): dependency problems - leaving triggers unprocessed dpkg: dependency problems prevent processing triggers for dbus: dbus depends on libdbus-1-3 (= 1.7.6); however: Package libdbus-1-3:amd64 is not configured yet. dpkg: error processing package dbus (--configure): dependency problems - leaving triggers unprocessed dpkg: dependency problems prevent processing triggers for dbus: dbus depends on libdbus-1-3 (= 1.7.6); however: Package libdbus-1-3:amd64 is not configured yet. dpkg: error processing package dbus (--configure): dependency problems - leaving triggers unprocessed dpkg: dependency problems prevent processing triggers for dbus: dbus depends on libdbus-1-3 (= 1.7.6); however: Package libdbus-1-3:amd64 is not configured yet. dpkg: error processing package dbus (--configure): dependency problems - leaving triggers unprocessed dpkg: dependency problems prevent processing triggers for dbus: dbus depends on libdbus-1-3 (= 1.7.6); however: Package libdbus-1-3:amd64 is not configured yet. dpkg: error processing package dbus (--configure): dependency problems - leaving triggers unprocessed dpkg: dependency problems prevent processing triggers for dbus: dbus depends on libdbus-1-3 (= 1.7.6); however: Package libdbus-1-3:amd64 is not configured yet. dpkg: error processing package dbus (--configure): dependency problems - leaving triggers unprocessed dpkg: dependency problems prevent processing triggers for dbus: dbus depends on libdbus-1-3 (= 1.7.6); however: Package libdbus-1-3:amd64 is not configured yet. dpkg: error processing package dbus (--configure): dependency problems - leaving triggers unprocessed dpkg: dependency problems prevent processing triggers for dbus: dbus depends on libdbus-1-3 (= 1.7.6); however: Package libdbus-1-3:amd64 is not configured yet. dpkg: error processing package dbus (--configure): dependency problems - leaving triggers unprocessed dpkg: dependency problems prevent processing triggers for dbus: dbus depends on libdbus-1-3 (= 1.7.6); however: Package libdbus-1-3:amd64 is not configured yet. dpkg: error processing package dbus (--configure): dependency problems - leaving triggers
Bug#776910: marked as done (apt: upgrade from wheezy to jessie breaks in the middle)
Your message dated Mon, 9 Mar 2015 22:19:12 +0100 with message-id 20150309211912.GA8298@crossbow and subject line Close resolved trigger loop bugs has caused the Debian Bug report #776910, regarding apt: upgrade from wheezy to jessie breaks in the middle 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.) -- 776910: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=776910 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: apt Version: 1.0.9.6 Severity: grave Tags: newcomer Justification: renders package unusable My guess is that some limit on number of errors was taken into account unneceserly during an upgrade - upgrades are expected to rise trancient errors. -- Package-specific info: -- apt-config dump -- APT ; APT::Architecture i386; APT::Build-Essential ; APT::Build-Essential:: build-essential; APT::Install-Recommends 1; APT::Install-Suggests 0; APT::NeverAutoRemove ; APT::NeverAutoRemove:: ^firmware-linux.*; APT::NeverAutoRemove:: ^linux-firmware$; APT::NeverAutoRemove:: ^linux-image-3\.16\.0-4-586$; APT::NeverAutoRemove:: ^linux-image-3\.2\.0-4-486$; APT::NeverAutoRemove:: ^linux-headers-3\.16\.0-4-586$; APT::NeverAutoRemove:: ^linux-headers-3\.2\.0-4-486$; APT::NeverAutoRemove:: ^linux-image-extra-3\.16\.0-4-586$; APT::NeverAutoRemove:: ^linux-image-extra-3\.2\.0-4-486$; APT::NeverAutoRemove:: ^linux-signed-image-3\.16\.0-4-586$; APT::NeverAutoRemove:: ^linux-signed-image-3\.2\.0-4-486$; APT::NeverAutoRemove:: ^kfreebsd-image-3\.16\.0-4-586$; APT::NeverAutoRemove:: ^kfreebsd-image-3\.2\.0-4-486$; APT::NeverAutoRemove:: ^kfreebsd-headers-3\.16\.0-4-586$; APT::NeverAutoRemove:: ^kfreebsd-headers-3\.2\.0-4-486$; APT::NeverAutoRemove:: ^gnumach-image-3\.16\.0-4-586$; APT::NeverAutoRemove:: ^gnumach-image-3\.2\.0-4-486$; APT::NeverAutoRemove:: ^.*-modules-3\.16\.0-4-586$; APT::NeverAutoRemove:: ^.*-modules-3\.2\.0-4-486$; APT::NeverAutoRemove:: ^.*-kernel-3\.16\.0-4-586$; APT::NeverAutoRemove:: ^.*-kernel-3\.2\.0-4-486$; APT::NeverAutoRemove:: ^linux-backports-modules-.*-3\.16\.0-4-586$; APT::NeverAutoRemove:: ^linux-backports-modules-.*-3\.2\.0-4-486$; APT::NeverAutoRemove:: ^linux-tools-3\.16\.0-4-586$; APT::NeverAutoRemove:: ^linux-tools-3\.2\.0-4-486$; APT::NeverAutoRemove:: ^postgresql-; APT::VersionedKernelPackages ; APT::VersionedKernelPackages:: linux-image; APT::VersionedKernelPackages:: linux-headers; APT::VersionedKernelPackages:: linux-image-extra; APT::VersionedKernelPackages:: linux-signed-image; APT::VersionedKernelPackages:: kfreebsd-image; APT::VersionedKernelPackages:: kfreebsd-headers; APT::VersionedKernelPackages:: gnumach-image; APT::VersionedKernelPackages:: .*-modules; APT::VersionedKernelPackages:: .*-kernel; APT::VersionedKernelPackages:: linux-backports-modules-.*; APT::VersionedKernelPackages:: linux-tools; APT::Never-MarkAuto-Sections ; APT::Never-MarkAuto-Sections:: metapackages; APT::Never-MarkAuto-Sections:: restricted/metapackages; APT::Never-MarkAuto-Sections:: universe/metapackages; APT::Never-MarkAuto-Sections:: multiverse/metapackages; APT::Never-MarkAuto-Sections:: oldlibs; APT::Never-MarkAuto-Sections:: restricted/oldlibs; APT::Never-MarkAuto-Sections:: universe/oldlibs; APT::Never-MarkAuto-Sections:: multiverse/oldlibs; APT::Update ; APT::Update::Post-Invoke-Success ; APT::Update::Post-Invoke-Success:: [ ! -f /var/run/dbus/system_bus_socket ] || /usr/bin/dbus-send --system --dest=org.debian.apt --type=signal /org/debian/apt org.debian.apt.CacheChanged || true; APT::Update::Post-Invoke-Success:: /usr/bin/test -e /usr/share/dbus-1/system-services/org.freedesktop.PackageKit.service /usr/bin/test -S /var/run/dbus/system_bus_socket /usr/bin/gdbus call --system --dest org.freedesktop.PackageKit --object-path /org/freedesktop/PackageKit --timeout 4 --method org.freedesktop.PackageKit.StateHasChanged cache-update /dev/null; /bin/echo /dev/null; APT::Immediate-Configure 1; APT::Default-Release jessie; APT::Architectures ; APT::Architectures:: i386; APT::Compressor ; APT::Compressor::. ; APT::Compressor::.::Name .; APT::Compressor::.::Extension ; APT::Compressor::.::Binary ; APT::Compressor::.::Cost 1; APT::Compressor::gzip ; APT::Compressor::gzip::Name gzip; APT::Compressor::gzip::Extension .gz; APT::Compressor::gzip::Binary gzip; APT::Compressor::gzip::Cost 2; APT::Compressor::gzip::CompressArg ; APT::Compressor::gzip::CompressArg:: -9n; APT::Compressor::gzip::UncompressArg ; APT::Compressor::gzip::UncompressArg:: -d; APT::Compressor::bzip2 ; APT::Compressor::bzip2::Name bzip2; APT::Compressor::bzip2::Extension .bz2;
Bug#776744: [Pkg-utopia-maintainers] Bug#776744: policykit-1: use current libmozjs-24.0-dev | libmozjs185-dev
Am 09.03.2015 um 21:35 schrieb Alf Gaida: Package: policykit-1 Followup-For: Bug #776744 Dear Maintainer, please use currend build dependencies - maybe the fallback to libmozjs185-dev might be a good idea. diff --git a/debian/control b/debian/control index 482f3a4..89ba49f 100644 --- a/debian/control +++ b/debian/control @@ -10,7 +10,7 @@ Build-Depends: debhelper (= 9), libexpat1-dev, libpam0g-dev, libselinux1-dev [linux-any], - libmozjs-17.0-dev, + libmozjs-24.0-dev|libmozjs185-dev, Changing the build-depends is not sufficient. Someone will actually need to port the source code to mozjs 24. -- 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#776911: gnome-shell: fails to start on i386 when [Mesa was] built with llvm-3.5
On Sun, 8 Mar 2015 20:02:00 + (UTC) intrigeri intrig...@debian.org wrote: I've rebuilt the mesa package with the patch from https://freedesktop.org/patch/34445/, and it fixes things for me, at least with `-cpu qemu32'. I've asked the other Tails developer (Cc'd), who is also experiencing this bug, to try and reproduce my results. The patch to mesa is definitely an improvement but some qemu CPU types still fail. The host system has an AMD FX-6100 CPU. . --- These did not work without the patch and they're still not working. * SandyBridge * Broadwell * Haswell * Westmere * Nehalem * Penryn These worked previously and still work after the patch. * host * kvm64 * Opteron_G1 * Opteron_G2 * Opteron_G3 * Opteron_G4 * Opteron_G5 * phenom These failed previously but they work with the patched mesa. * core2duo * coreduo * Conroe * n270 * qemu32 I'll attach logs later. pgp5jzMbDbJf0.pgp Description: OpenPGP digital signature
Bug#779799: marked as done (linux: Older patches causing FTBFS on armhf)
Your message dated Mon, 09 Mar 2015 22:00:10 + with message-id e1yv5ic-0007yh...@franck.debian.org and subject line Bug#779799: fixed in linux 3.19.1-1~exp1 has caused the Debian Bug report #779799, regarding linux: Older patches causing FTBFS on armhf 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.) -- 779799: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=779799 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Source: linux Version: 3.19-1~exp1 Justification: fails to build from source Severity: serious Hello, The two patches: features/arm/dts-sun7i-Add-spi0_pins_a-pinctrl-setting.patch features/arm/dts-sun7i-Add-uart3_pins_b-pinctrl-setting.patch are no longer needed in 3.19-1~exp1 because they were accepted upstream in v3.19 as these commits: 2dad53b54a 0510e4b52a Keeping the patches means getting duplicate nodes in the device tree which causes this build failure on armhf: https://buildd.debian.org/status/fetch.php?pkg=linuxarch=armhfver=3.19-1~exp1stamp=1424044478 Please could you remove the patches from the next experimental version? Thanks a lot, B.R. Oake. -- System Information: Debian Release: 8.0 APT prefers testing-updates APT policy: (500, 'testing-updates'), (500, 'testing') Architecture: armhf (armv7l) Kernel: Linux 3.16.0-4-armmp (SMP w/2 CPU cores) Locale: LANG=en_GB.utf8, LC_CTYPE=en_GB.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) ---End Message--- ---BeginMessage--- Source: linux Source-Version: 3.19.1-1~exp1 We believe that the bug you reported is fixed in the latest version of linux, 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 779...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Ben Hutchings b...@decadent.org.uk (supplier of updated linux 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, 08 Mar 2015 15:29:45 + Source: linux Binary: linux-source-3.19 linux-doc-3.19 linux-manual-3.19 linux-support-3.19.0-trunk linux-libc-dev linux-headers-3.19.0-trunk-all linux-headers-3.19.0-trunk-all-alpha kernel-image-3.19.0-trunk-alpha-generic-di nic-modules-3.19.0-trunk-alpha-generic-di nic-wireless-modules-3.19.0-trunk-alpha-generic-di nic-shared-modules-3.19.0-trunk-alpha-generic-di serial-modules-3.19.0-trunk-alpha-generic-di usb-serial-modules-3.19.0-trunk-alpha-generic-di ppp-modules-3.19.0-trunk-alpha-generic-di pata-modules-3.19.0-trunk-alpha-generic-di cdrom-core-modules-3.19.0-trunk-alpha-generic-di scsi-core-modules-3.19.0-trunk-alpha-generic-di scsi-modules-3.19.0-trunk-alpha-generic-di scsi-common-modules-3.19.0-trunk-alpha-generic-di scsi-extra-modules-3.19.0-trunk-alpha-generic-di loop-modules-3.19.0-trunk-alpha-generic-di btrfs-modules-3.19.0-trunk-alpha-generic-di ext4-modules-3.19.0-trunk-alpha-generic-di isofs-modules-3.19.0-trunk-alpha-generic-di jfs-modules-3.19.0-trunk-alpha-generic-di xfs-modules-3.19.0-trunk-alpha-generic-di fat-modules-3.19.0-trunk-alpha-generic-di md-modules-3.19.0-trunk-alpha-generic-di multipath-modules-3.19.0-trunk-alpha-generic-di usb-modules-3.19.0-trunk-alpha-generic-di usb-storage-modules-3.19.0-trunk-alpha-generic-di fb-modules-3.19.0-trunk-alpha-generic-di input-modules-3.19.0-trunk-alpha-generic-di event-modules-3.19.0-trunk-alpha-generic-di mouse-modules-3.19.0-trunk-alpha-generic-di nic-pcmcia-modules-3.19.0-trunk-alpha-generic-di pcmcia-modules-3.19.0-trunk-alpha-generic-di nic-usb-modules-3.19.0-trunk-alpha-generic-di sata-modules-3.19.0-trunk-alpha-generic-di core-modules-3.19.0-trunk-alpha-generic-di crc-modules-3.19.0-trunk-alpha-generic-di crypto-modules-3.19.0-trunk-alpha-generic-di crypto-dm-modules-3.19.0-trunk-alpha-generic-di ata-modules-3.19.0-trunk-alpha-generic-di nbd-modules-3.19.0-trunk-alpha-generic-di squashfs-modules-3.19.0-trunk-alpha-generic-di virtio-modules-3.19.0-trunk-alpha-generic-di zlib-modules-3.19.0-trunk-alpha-generic-di fuse-modules-3.19.0-trunk-alpha-generic-di srm-modules-3.19.0-trunk-alpha-generic-di linux-headers-3.19.0-trunk-common linux-image-3.19.0-trunk-alpha-generic
Bug#776744: [Pkg-utopia-maintainers] Bug#776744: Bug#776744: policykit-1: use current libmozjs-24.0-dev | libmozjs185-dev
Am 09.03.2015 um 21:43 schrieb Michael Biebl: Am 09.03.2015 um 21:35 schrieb Alf Gaida: - libmozjs-17.0-dev, + libmozjs-24.0-dev|libmozjs185-dev, Changing the build-depends is not sufficient. Someone will actually need to port the source code to mozjs 24. That aside, the correct Build-Depends would be libmozjs-24-dev -- 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#776911: gnome-shell: fails to start on i386 when [Mesa was] built with llvm-3.5
On Sun, 8 Mar 2015 20:02:00 + (UTC) intrigeri intrig...@debian.org wrote: I've rebuilt the mesa package with the patch from https://freedesktop.org/patch/34445/, and it fixes things for me, at least with `-cpu qemu32'. I've asked the other Tails developer (Cc'd), who is also experiencing this bug, to try and reproduce my results. The patch to mesa is definitely an improvement but some qemu CPU types still fail. The host system has an AMD FX-6100 CPU. . --- These did not work without the patch and they're still not working. * SandyBridge * Broadwell * Haswell * Westmere * Nehalem * Penryn These worked previously and still work after the patch. * host * kvm64 * Opteron_G1 * Opteron_G2 * Opteron_G3 * Opteron_G4 * Opteron_G5 * phenom These failed previously but they work with the patched mesa. * core2duo * coreduo * Conroe * n270 * qemu32 I'll attach logs later. pgpvZMO1Yhx4G.pgp Description: OpenPGP digital signature
Bug#776911: gnome-shell: fails to start on i386 when [Mesa was] built with llvm-3.5
On 09/03/15 19:09, kytv wrote: The host system has an AMD FX-6100 CPU. ... These did not work without the patch and they're still not working. * SandyBridge * Broadwell * Haswell * Westmere * Nehalem * Penryn Those are all rather modern Intel CPUs. It would not surprise me at all if they had CPU features that are not supported by your host system: AMD CPUs usually support the latest version of AMD-originated features and a somewhat older version of Intel-originated features, and vice versa. You can check via /proc/cpuinfo on the host and the VM. For instance, here's the Sandy Bridge CPU on my laptop: flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx rdtscp lm constant_tsc arch_perfmon pebs bts nopl xtopology nonstop_tsc aperfmperf eagerfpu pni pclmulqdq dtes64 monitor ds_cpl vmx smx est tm2 ssse3 cx16 xtpr pdcm pcid sse4_1 sse4_2 x2apic popcnt tsc_deadline_timer aes xsave avx lahf_lm ida arat epb xsaveopt pln pts dtherm tpr_shadow vnmi flexpriority ept vpid If your host CPU is missing any of those features, then emulating a SandyBridge CPU in your VM is probably an invalid configuration. S -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#776911: gnome-shell: fails to start on i386 when [Mesa was] built with llvm-3.5
On Thu, Feb 26, 2015 at 08:54:10 +, Simon McVittie wrote: Adding mesa@packages to Cc since I suspect #775235 needs reassigning to Mesa, perhaps along with its merged bugs #770130, #776911. Context for Mesa maintainers: #775235 is that gnome-shell crashes in an i386 VM with its default choice of emulated CPU, with LLVM ERROR: Do not know how to split the result of this operator!. See https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=775235#10 for full backtrace. The merged bug #770130 is that gnome-shell crashes on an unknown i386 (probably relatively old, since it has 82830M/MG integrated graphics, which Wikipedia says is a Pentium III-M chipset) with Cogl-ERROR **: Failed to create texture 2d due to size/format constraints. Oddly, this only happens for non-power-of-two textures in the gnome-shell run by the actual user, not by the gnome-shell used for the gdm login prompt (even though both use non-power-of-two textures). Michael Gilbert merged this with #775235 and #776911 without comment; I'm not sure of the reasoning for believing that #775235 and #770130 is the same thing. The other merged bug #776911 is that gnome-shell crashes on an unknown i386 with Cogl-ERROR **: Failed to create texture 2d due to size/format constraints; that looks like the same thing as #770130. Sounds like there are at least two different issues that should be split... Cheers, Julien signature.asc Description: Digital signature
Bug#780093: [Pkg-libvirt-maintainers] Bug#780093: libvirt: error: unsupported configuration: QEMU 2.1.2 is too new for help parsing
On Mon, Mar 09, 2015 at 10:05:02AM +0100, Thorsten Glaser wrote: Package: libvirt-clients Version: 1.2.9-9 Severity: grave Justification: renders package unusable tglase@tglase:~ $ virsh -c qemu:///system start MirBSD error: Failed to start domain MirBSD error: unsupported configuration: QEMU 2.1.2 is too new for help parsing That is because it should use the more reliable QMP probing. Are you wrapping qemu/kvm by a skript or something? Does virsh capabilities show the same error? Anything in the daemon logs (if not please try increasing the debug level). Cheers, -- Guido -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#776746:
Related ubuntu bug report https://bugs.launchpad.net/debian/+source/gnome-session/+bug/1251281 Related Gnome bug report https://bugzilla.gnome.org/show_bug.cgi?id=731173 -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed: tagging 775662
Processing commands for cont...@bugs.debian.org: tags 775662 + pending Bug #775662 [src:oss4] oss4: Insufficient validation of USB device descriptors Added tag(s) pending. thanks Stopping processing here. Please contact me if you need assistance. -- 775662: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=775662 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#780145: not appropriate for jessie
Package: python-cream Severity: serious Version: 0.5.3-1 The python-cream package from the Cream Melange project is currently not suitable for Debian jessie, thus marking it with a RC bug. No further action has to be taken for now, except waiting for its automatic removal from jessie. 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 pgpqEGgfvomWN.pgp Description: Digitale PGP-Signatur
Processed: found 780139 in 1.02-1, tagging 780139
Processing commands for cont...@bugs.debian.org: found 780139 1.02-1 Bug #780139 [checkpw] CVE-2015-0885 Marked as found in versions checkpw/1.02-1. tags 780139 + upstream fixed-upstream Bug #780139 [checkpw] CVE-2015-0885 Added tag(s) upstream and fixed-upstream. thanks Stopping processing here. Please contact me if you need assistance. -- 780139: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=780139 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#779909: marked as done (389-ds-base: CVE-2014-8105 CVE-2014-8112)
Your message dated Mon, 09 Mar 2015 19:33:47 + with message-id e1yv3qx-0002np...@franck.debian.org and subject line Bug#779909: fixed in 389-ds-base 1.3.3.5-4 has caused the Debian Bug report #779909, regarding 389-ds-base: CVE-2014-8105 CVE-2014-8112 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.) -- 779909: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=779909 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: 389-ds-base Severity: grave Tags: security Justification: user security hole Hi, please see https://bugzilla.redhat.com/show_bug.cgi?id=CVE-2014-8112 https://bugzilla.redhat.com/show_bug.cgi?id=CVE-2014-8105 Cheers, Moritz ---End Message--- ---BeginMessage--- Source: 389-ds-base Source-Version: 1.3.3.5-4 We believe that the bug you reported is fixed in the latest version of 389-ds-base, 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 779...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Timo Aaltonen tjaal...@debian.org (supplier of updated 389-ds-base 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: Mon, 09 Mar 2015 10:53:03 +0200 Source: 389-ds-base Binary: 389-ds 389-ds-base-libs 389-ds-base-libs-dbg 389-ds-base-dev 389-ds-base 389-ds-base-dbg Architecture: source all amd64 Version: 1.3.3.5-4 Distribution: unstable Urgency: medium Maintainer: Debian 389ds Team pkg-fedora-ds-maintain...@lists.alioth.debian.org Changed-By: Timo Aaltonen tjaal...@debian.org Description: 389-ds - 389 Directory Server suite - metapackage 389-ds-base - 389 Directory Server suite - server 389-ds-base-dbg - 389 Directory Server suite - server debugging symbols 389-ds-base-dev - 389 Directory Server suite - development files 389-ds-base-libs - 389 Directory Server suite - libraries 389-ds-base-libs-dbg - 389 Directory Server suite - library debugging symbols Closes: 779909 Changes: 389-ds-base (1.3.3.5-4) unstable; urgency=medium . * Security fixes (Closes: #779909) - cve-2014-8105.diff: Fix for CVE-2014-8105 - cve-2014-8112.diff: Fix for CVE-2014-8112 Checksums-Sha1: d264a387bc5d00f61c9755ac269915d80c4d543a 2578 389-ds-base_1.3.3.5-4.dsc bb43dc34bde87175c169cccb9981999f263c0c03 3273753 389-ds-base_1.3.3.5.orig.tar.bz2 81b313ec7d8bf62435246e99e46805b5562db0e4 25092 389-ds-base_1.3.3.5-4.debian.tar.xz 09ade6d2f9269287e662828bcbad588f425af0f5 15238 389-ds_1.3.3.5-4_all.deb a8c78cce4ebec290e22e8bf04a0673688666526e 387892 389-ds-base-libs_1.3.3.5-4_amd64.deb 1e14f0ea541bb96838fdfbacfd7cabebd3cf9780 1280628 389-ds-base-libs-dbg_1.3.3.5-4_amd64.deb 8de208e09b3bdc3529863552a166feea523b0f99 68400 389-ds-base-dev_1.3.3.5-4_amd64.deb f8e90b7c79c006360f7e527cb33f6e7c18fc6ecb 1457312 389-ds-base_1.3.3.5-4_amd64.deb 94307eeaf705127f9c35d13b35c9c18869ef2415 4176344 389-ds-base-dbg_1.3.3.5-4_amd64.deb Checksums-Sha256: c92376ffbede58cd9f30c6c5f704a19fb22f55f9808b11f3b3e6999e47d89dde 2578 389-ds-base_1.3.3.5-4.dsc 85f69e65909f7a8286717290f699e61be89c6534e926bcb5b4a6644f950e8827 3273753 389-ds-base_1.3.3.5.orig.tar.bz2 abdf75ef6cd65cdd6bc182d6414039f785b4e810ddf489ffeb741e5ba7c95ed2 25092 389-ds-base_1.3.3.5-4.debian.tar.xz ab8464c1771e5524a87bbc8ca22788bb73f18ef189c9a954dee5769c87ccfc11 15238 389-ds_1.3.3.5-4_all.deb 24b6c98fa53a5a4a7e3a9944bb4583801b79340893f2674ed3aee26ef32d9e53 387892 389-ds-base-libs_1.3.3.5-4_amd64.deb 0adc8e48b5de5a86a3d6009c04f7064d9838ecf03ec4c45c8ba45c61544ac0f2 1280628 389-ds-base-libs-dbg_1.3.3.5-4_amd64.deb 8190b68d81562d8b3fb3e56a7d93b636f0d024c246842e944b36cb3fa555d59a 68400 389-ds-base-dev_1.3.3.5-4_amd64.deb cdecd2acc2dd479db4d9a39dcf90f0fb435e109bca951b811146f9874394cf00 1457312 389-ds-base_1.3.3.5-4_amd64.deb d9e510899768f0601cf868839559e8d5d55d14cdb9276182532fbaf4bd0a0f44 4176344 389-ds-base-dbg_1.3.3.5-4_amd64.deb Files: f9be061e55b796adcf7c4c1211bb338c 2578 net optional 389-ds-base_1.3.3.5-4.dsc 84869d46184039fce976b858e663232e 3273753 net optional 389-ds-base_1.3.3.5.orig.tar.bz2 f10a520176844014f2625a673cd79d74 25092 net optional 389-ds-base_1.3.3.5-4.debian.tar.xz f14605761db1668b8132cca293127d6d
Bug#780146: not appropriate for jessie
Package: cream-melange Version: 0.5.2-2 Severity: serious The cream-melange package from the Cream Melange project is currently not suitable for Debian jessie, thus marking it with a RC bug. No further action has to be taken for now, except waiting for its automatic removal from jessie. 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 pgp50BMKWet0l.pgp Description: Digitale PGP-Signatur
Bug#776744: policykit-1: use current libmozjs-24.0-dev | libmozjs185-dev
Package: policykit-1 Followup-For: Bug #776744 Dear Maintainer, please use currend build dependencies - maybe the fallback to libmozjs185-dev might be a good idea. diff --git a/debian/control b/debian/control index 482f3a4..89ba49f 100644 --- a/debian/control +++ b/debian/control @@ -10,7 +10,7 @@ Build-Depends: debhelper (= 9), libexpat1-dev, libpam0g-dev, libselinux1-dev [linux-any], - libmozjs-17.0-dev, + libmozjs-24.0-dev|libmozjs185-dev, gtk-doc-tools, xsltproc, libgirepository1.0-dev (= 0.9.12), cheers Alf -- System Information: Debian Release: 8.0 APT prefers buildd-unstable APT policy: (500, 'buildd-unstable'), (500, 'unstable'), (500, 'testing'), (3, 'experimental'), (1, 'buildd-experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.18-3-ck-amd64 (SMP w/4 CPU cores; PREEMPT) Locale: LANG=de_DE.utf8, LC_CTYPE=de_DE.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages policykit-1 depends on: ii adduser3.113+nmu3 ii dbus 1.8.16-1 ii libc6 2.19-15 ii libexpat1 2.1.0-6+b3 ii libglib2.0-0 2.42.1-1 ii libmozjs185-1.01.8.5-1.0.0+dfsg-4.3 ii libnspr4 2:4.10.7-1 ii libnspr4-0d2:4.10.7-1 ii libpam-systemd 219-4 ii libpam0g 1.1.8-3.1 ii libpolkit-agent-1-00.112-4.1 ii libpolkit-gobject-1-0 0.112-4.1 ii libsystemd0219-4 policykit-1 recommends no packages. policykit-1 suggests no packages. -- Configuration Files: /etc/polkit-1/rules.d/40-debian-sudo.rules [Errno 13] Keine Berechtigung: u'/etc/polkit-1/rules.d/40-debian-sudo.rules' /etc/polkit-1/rules.d/50-default.rules [Errno 13] Keine Berechtigung: u'/etc/polkit-1/rules.d/50-default.rules' -- 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#775877: gnome-session: No mouse pointer after login
On 09/03/15 23:41, Podrigal, Aron wrote: The missing mouse pointer however perhaps is not a bug in gnome-session. Its probably somewhere in gnome-settings-daemon As I said already: Searching the gnome-settings-daemon source code, the only obvious possibility is in the power plugin. Aron, please try this and see whether it works better for you: https://people.debian.org/~smcv/gnome-settings-daemon_3.14.2-2+smcv1_amd64.deb If you can still reproduce this problem with your current version of g-s-d, please try that one, which I think might fix it. If you can't reproduce this issue, then it probably shouldn't be considered grave severity. Thanks, S -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#710321: marked as done (task: didn't handle conffile rename correctly)
Your message dated Mon, 09 Mar 2015 22:19:54 + with message-id e1yv61j-00033x...@franck.debian.org and subject line Bug#710321: fixed in task 2.4.1+dfsg-3 has caused the Debian Bug report #710321, regarding task: didn't handle conffile rename correctly 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.) -- 710321: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=710321 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Source: task Version: 2.1.2-1 Severity: serious Justification: Policy 10.7.3 task_2.0.0-1 ships this conffile: /etc/bash_completion.d/task task_2.1.2-1 ships it as: /etc/bash_completion.d/task.sh Unfortunately, I forgot to add maintainer scripts to deal with this rename. As a consequence, users who upgraded the package have now both of the files on disk. :( My current plan how to fix this: 1) Revert to the original filename: /etc/bash_completion.d/task 2) rm_conffile /etc/bash_completion.d/task.sh It's not ideal, but I don't think any extra complexity is worth the effort, given that the broken package has been in unstable for less than 3 weeks. If anybody has a better idea, please speak up! -- Jakub Wilk ---End Message--- ---BeginMessage--- Source: task Source-Version: 2.4.1+dfsg-3 We believe that the bug you reported is fixed in the latest version of task, 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 710...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Sebastien Badia s...@sebian.fr (supplier of updated task 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, 07 Mar 2015 23:27:50 +0100 Source: task Binary: taskwarrior task Architecture: source amd64 Version: 2.4.1+dfsg-3 Distribution: unstable Urgency: medium Maintainer: Sebastien Badia s...@sebian.fr Changed-By: Sebastien Badia s...@sebian.fr Description: task - feature-rich console based todo list manager - transitional packa taskwarrior - feature-rich console based todo list manager Closes: 710321 779914 Changes: task (2.4.1+dfsg-3) unstable; urgency=medium . * Re-introduce Jakub fix for bash completion file (closes: #710321): + Rename /etc/bash_completion.d/task.sh back as /etc/bash_completion.d/task + Update debian/rules accordingly. + Add debian/maintscript to let dh_installdeb add maintainer script snippets to remove the old file, Debian version 2.4.1-1 was accidentally uploaded to unstable. * Fix install step (re-add rc files) (Closes: #779914). Checksums-Sha1: 199b5988c5fcdfe0706679a1a90fd7dc66dc0fd7 2021 task_2.4.1+dfsg-3.dsc 95306e05ec373c42a3f1e699f90c36d1ac0b65ee 16380 task_2.4.1+dfsg-3.debian.tar.xz Checksums-Sha256: 9eb5375cf6f5b8152327f0f89e321ec0fb68b612fed22dfcdb552295fad7ea7c 2021 task_2.4.1+dfsg-3.dsc 52faa2b75c8f634441d17e616511226fce390de0e3f3061039b27ff9ecaa0365 16380 task_2.4.1+dfsg-3.debian.tar.xz Files: 4076f4903d655498f8cd98ca0d68beb4 2021 utils optional task_2.4.1+dfsg-3.dsc 36cf0788c060f372a669605d7c78d139 16380 utils optional task_2.4.1+dfsg-3.debian.tar.xz -BEGIN PGP SIGNATURE- Version: GnuPG v1 iQIcBAEBCAAGBQJU/hnRAAoJEJFk+h0XvV02glAP/2i1zFM8sb+Ul1nJFfOYoKBZ i2KVenQk3M6rCCw90g7qfEB9OJpwCYrkU/XZ50fYcJW6qOaRNkvj3h5rz01ZHsvn cr/cVoXqZAAKfDp/O5haGOB8iVGuJlJfNG60dHr+gIdIiuJgaP5hnULx1J5Bbjor SOM30OkT0R6Q74a1bdF4QxBywR5YSonLnNM1DV6NC9HaOMzWvW3exYIOEb3rxZrP JzXUTL5Aes4vtlZcJjD5KkNXANWj0W+aObvbBDsTz+3tqYN/6QIxdLBydJcVd23A wuDTCIcgPXzoQ+YuTuirX05IocY8KVynSJEBxBeVtTJPqw+2jhBWdUxE2CiJDJ6x ZZK5tOfocKiZ5JHVZ0BH/4ICyvodf//CEAOsAPddv4AVVhNuU2q9+53JTmIHO58d cK7kMnL8ZcV3XZCmEXrkaydmIgIcyYHxqWyWnIaManxPU/zMczXaDuNxJ4jl9fec IcQavIivqNJ1qvvxH9ISJDwryMldRS7JHXKITv+C2rgEDuzTarArhLvHhwKvarLI Faj3yud70jIj1uysvmwdxWSK488oFp+uCaVM+tR0MLvMgLi8j9xSq9fwU2u9Bbis WpfhnJiLvcBb89kxunqp8/N/pZncT4zcj6JodlVjY/adKnWG5NmDWw65Xifklnxg 3kS9459k0OBGS9jzLhYF =bSae -END PGP SIGNATUREEnd Message---
Bug#775877: gnome-session: No mouse pointer after login
Hi Simon, sorry for my late response, That issue seems like its gone
already for a while, I did not notice when exactly. It has been some time
and I've had some updates to some other packages. The missing mouse pointer
however perhaps is not a bug in gnome-session. Its probably somewhere in
gnome-settings-daemon, however I tried running it with --debug but did not
notice any special log entries leading to this.
If you can advise where and how to look for, I will definitely try to find
the problem.
Thanks
On Mon, Mar 9, 2015 at 4:50 PM, Simon McVittie s...@debian.org wrote:
On 06/03/15 10:00, Simon McVittie wrote:
On Tue, 20 Jan 2015 at 21:43:09 -0500, Aron Podrigal wrote:
Jan 20 16:46:18 jessie gnome-session[1888]:
GLib-GIO:ERROR:/tmp/buildd/glib2.0-2.42.1/./gio/gdbusconnection.c:4231:invoke_set_property_in_idle_cb:
assertion failed: (error != NULL)
This seems likely to be the problem: gnome-settings-daemon crashed with
an assertion failure.
gdbusconnection.c:4231 is the last of the lines I've quoted here:
if (!data-vtable-set_property (data-connection,
g_dbus_message_get_sender
(data-message),
g_dbus_message_get_path (data-message),
data-interface_info-name,
data-property_name,
value,
error,
data-user_data))
{
gchar *dbus_error_name;
g_assert (error != NULL);
So the bug here is that something, somewhere in the
gnome-settings-daemon process, has a set_property() callback
that fails without correctly setting the error.
Searching the gnome-settings-daemon source code, the only obvious
possibility is in the power plugin. Aron, please try this and see
whether it works better for you:
https://people.debian.org/~smcv/gnome-settings-daemon_3.14.2-2+smcv1_amd64.deb
Regards,
S
Processed: tag 778828
Processing commands for cont...@bugs.debian.org: tags 778828 patch Bug #778828 [dmsetup] dmsetup: please add Breaks: live-tools ( 4.0.1-1) Added tag(s) patch. thanks Stopping processing here. Please contact me if you need assistance. -- 778828: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=778828 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#780093: [Pkg-libvirt-maintainers] Bug#780093: libvirt: error: unsupported configuration: QEMU 2.1.2 is too new for help parsing
On Mon, 9 Mar 2015, Guido Günther wrote:
wrapping qemu/kvm by a skript or something?
Yes, necessarily:
tglase@tglase:~ $ virsh -c qemu:///system dumpxml MirBSD | fgrep emul
emulator/usr/local/bin/qemu-in-chroot/emulator
tglase@tglase:~ $ cat /usr/local/bin/qemu-in-chroot
#!/bin/sh
exec schroot -c sid-amd64 -u root -- qemu-system-x86_64 -enable-kvm $@
Otherwise I cannot assign more than 2047 MiB RAM.
*But*:
tglase@tglase:~ $ virsh -c qemu:///system dumpxml SuSE_Linux_1.0 | fgrep emul
emulator/usr/bin/kvm/emulator
tglase@tglase:~ $ virsh -c qemu:///system start SuSE_Linux_1.0
error: Failed to start domain SuSE_Linux_1.0
error: unsupported configuration: QEMU 2.1.2 is too new for help parsing
So this also happens for VMs created by virt-manager and
then untouched.
Does
virsh capabilities
show the same error?
No, it shows a bunch of XML things (capabilities/{host,guest}/…).
bye,
//mirabilos
--
tarent solutions GmbH
Rochusstraße 2-4, D-53123 Bonn • http://www.tarent.de/
Tel: +49 228 54881-393 • Fax: +49 228 54881-235
HRB 5168 (AG Bonn) • USt-ID (VAT): DE122264941
Geschäftsführer: Dr. Stefan Barth, Kai Ebenrett, Boris Esser, Alexander Steeg
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#713177: marked as done (osmosis-plugin-borderextract: FTBFS: /«PKGBUILDDIR»/src/main/java/com/generalbytes/osmosis/borderextract/EntityHelper.java:[81,34] cannot find symbol)
Your message dated Mon, 09 Mar 2015 23:02:13 +
with message-id e1yv6gf-00027l...@franck.debian.org
and subject line Bug#773973: Removed package(s) from unstable
has caused the Debian Bug report #713177,
regarding osmosis-plugin-borderextract: FTBFS:
/«PKGBUILDDIR»/src/main/java/com/generalbytes/osmosis/borderextract/EntityHelper.java:[81,34]
cannot find symbol
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.)
--
713177: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=713177
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
---BeginMessage---
Source: osmosis-plugin-borderextract
Version: 1.3-1
Severity: serious
Tags: jessie sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20130620 qa-ftbfs
Justification: FTBFS on amd64
Hi,
During a rebuild of all packages in sid, your package failed to build on
amd64.
Relevant part:
make[1]: Entering directory `/«PKGBUILDDIR»'
mh_patchpom --no-parent -posmosis-plugin-borderextract pom.xml
mvn -o -s /etc/maven2/settings-debian.xml \
-Dmaven.test.skip=false package
[INFO]
NOTE: Maven is executing in offline mode. Any artifacts not already in your
local
repository will be inaccessible.
[INFO] Scanning for projects...
[INFO]
[INFO] Building borderextract
[INFO]task-segment: [package]
[INFO]
[INFO] [resources:resources {execution: default-resources}]
[INFO] Using 'UTF-8' encoding to copy filtered resources.
[INFO] Copying 1 resource
[INFO] [compiler:compile {execution: default-compile}]
[INFO] Compiling 14 source files to /«PKGBUILDDIR»/target/classes
[INFO]
[ERROR] BUILD FAILURE
[INFO]
[INFO] Compilation failure
/«PKGBUILDDIR»/src/main/java/com/generalbytes/osmosis/borderextract/BaseBorderListener.java:[33,23]
cannot find symbol
symbol : class Nullable
location: package javax.annotation
/«PKGBUILDDIR»/src/main/java/com/generalbytes/osmosis/borderextract/PolygonExporter.java:[25,23]
cannot find symbol
symbol : class Nonnull
location: package javax.annotation
/«PKGBUILDDIR»/src/main/java/com/generalbytes/osmosis/borderextract/PolyBorderListener.java:[31,23]
cannot find symbol
symbol : class Nonnull
location: package javax.annotation
/«PKGBUILDDIR»/src/main/java/com/generalbytes/osmosis/borderextract/EntityHelper.java:[34,23]
cannot find symbol
symbol : class Nonnull
location: package javax.annotation
/«PKGBUILDDIR»/src/main/java/com/generalbytes/osmosis/borderextract/PolygonExporter.java:[42,23]
cannot find symbol
symbol : class Nonnull
location: interface com.generalbytes.osmosis.borderextract.PolygonExporter
/«PKGBUILDDIR»/src/main/java/com/generalbytes/osmosis/borderextract/PolygonExporter.java:[42,46]
cannot find symbol
symbol : class Nonnull
location: interface com.generalbytes.osmosis.borderextract.PolygonExporter
/«PKGBUILDDIR»/src/main/java/com/generalbytes/osmosis/borderextract/PolygonExporter.java:[42,72]
cannot find symbol
symbol : class Nonnull
location: interface com.generalbytes.osmosis.borderextract.PolygonExporter
/«PKGBUILDDIR»/src/main/java/com/generalbytes/osmosis/borderextract/BaseBorderListener.java:[282,35]
cannot find symbol
symbol : class Nullable
location: class com.generalbytes.osmosis.borderextract.BaseBorderListener.Role
/«PKGBUILDDIR»/src/main/java/com/generalbytes/osmosis/borderextract/PolyBorderListener.java:[84,30]
cannot find symbol
symbol : class Nonnull
location: class com.generalbytes.osmosis.borderextract.PolyBorderListener
/«PKGBUILDDIR»/src/main/java/com/generalbytes/osmosis/borderextract/PolyBorderListener.java:[84,53]
cannot find symbol
symbol : class Nonnull
location: class com.generalbytes.osmosis.borderextract.PolyBorderListener
/«PKGBUILDDIR»/src/main/java/com/generalbytes/osmosis/borderextract/PolyBorderListener.java:[84,79]
cannot find symbol
symbol : class Nonnull
location: class com.generalbytes.osmosis.borderextract.PolyBorderListener
/«PKGBUILDDIR»/src/main/java/com/generalbytes/osmosis/borderextract/EntityHelper.java:[81,34]
cannot find symbol
symbol : class Nonnull
location: class com.generalbytes.osmosis.borderextract.EntityHelper
[INFO]
[INFO] For more information, run Maven with the -e switch
[INFO]
Bug#773973: marked as done (RM: osmosis-plugin-borderextract -- NPOASR; RC-buggy; inactive upstream)
Your message dated Mon, 09 Mar 2015 23:02:07 + with message-id e1yv6gz-00027i...@franck.debian.org and subject line Bug#773973: Removed package(s) from unstable has caused the Debian Bug report #773973, regarding RM: osmosis-plugin-borderextract -- NPOASR; RC-buggy; inactive upstream 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.) -- 773973: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=773973 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: src:osmosis-plugin-borderextract Version: 1.3-1 Severity: grave Justification: renders package unusable Dear Maintainer, osmosis-plugin-borderextract is not compatible with the current (upstream) osmosis version and has not seen any activity for over two years. The package has an unfixed RC bug (#713177) about the inability to build. This bug is unfixed for over a year. Since upstream doesn't develop the software anymore, and no-one in Debian actively maintains the package, the package should be removed from the archive. The package has never been part of a stable release, and was removed from testing after only five months. If there are no objections, I'll reassign this issue to ftp.debian.org for processing by the FTP masters. Kind Regards, Bas ---End Message--- ---BeginMessage--- We believe that the bug you reported is now fixed; the following package(s) have been removed from unstable: osmosis-plugin-borderextract | 1.3-1 | source, all --- Reason --- NPOASR; RC-buggy; inactive upstream -- Note that the package(s) have simply been removed from the tag database and may (or may not) still be in the pool; this is not a bug. The package(s) will be physically removed automatically when no suite references them (and in the case of source, when no binary references it). Please also remember that the changes have been done on the master archive and will not propagate to any mirrors until the next dinstall run at the earliest. Packages are usually not removed from testing by hand. Testing tracks unstable and will automatically remove packages which were removed from unstable when removing them from testing causes no dependency problems. The release team can force a removal from testing if it is really needed, please contact them if this should be the case. We try to close bugs which have been reported against this package automatically. But please check all old bugs, if they were closed correctly or should have been re-assigned to another package. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 773...@bugs.debian.org. The full log for this bug can be viewed at https://bugs.debian.org/773973 This message was generated automatically; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org. Debian distribution maintenance software pp. Scott Kitterman (the ftpmaster behind the curtain)---End Message---
Bug#780101: librest: Invalid pointer dereference
Package: librest Severity: grave Tags: security Justification: user security hole The following fix was identified to be a security-relevant: https://bugzilla.gnome.org/show_bug.cgi?id=742644 Please see Florian's CVE request for further information: http://www.openwall.com/lists/oss-security/2015/03/04/6 Fix: https://git.gnome.org/browse/librest/commit/?id=b50ace7738ea038 Cheers, Moritz -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#780102: libjbcrypt-java: CVE-2015-0886
Package: libjbcrypt-java Severity: grave Tags: security Justification: user security hole Hi, please see https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2015-0886 http://www.mindrot.org/projects/jBCrypt/news/rel04.html https://bugzilla.mindrot.org/show_bug.cgi?id=2097 Cheers, Moritz -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#776746: gnome-session: GNOME crashes during a remote desktop access
* gnome-session should put different text on the oh no! message if the problem is really your X server is not sufficiently capable to run GNOME * xrdp should allow session-selection, so remote users can select a non-compositing environment like LXDE or XFCE even if GNOME is the default * xrdp, or whatever Xserver it uses behind the scenes (Xvnc?), should support the Composite extension If this is considered as xrdp's bug, the 3rd option should be best way to fully fix this issue. But if it's considered as GNOME's bug, probably it should be patched to make GNOME 3 support non-compositing environment and this may better then modifying xrdp because this is a GNOME 3 ONLY issue and not xrdp's fault. Xrdp works well with other desktop environments. Gaotx
Bug#779784: git-extras: fresh-branch deletes everything without asking
On Mon, 9 Mar 2015 22:20:39 -0400 Andrew Starr-Bochicchio a...@debian.org wrote: I submitted a pull request for this upstream: https://github.com/tj/git-extras/pull/322 And it was very quickly merged. Proposed NMU debdiff attached. 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 bts779784.debdiff Description: Binary data
Bug#779784: git-extras: fresh-branch deletes everything without asking
tag patch thanks Hi, I submitted a pull request for this upstream: https://github.com/tj/git-extras/pull/322 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: tagging 779784
Processing commands for cont...@bugs.debian.org: tags 779784 + patch Bug #779784 [git-extras] git-extras: fresh-branch deletes everything without asking Added tag(s) patch. thanks Stopping processing here. Please contact me if you need assistance. -- 779784: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=779784 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#760998: [Pkg-utopia-maintainers] Bug#760998: Acknowledgement (network-manager: auto restarts)
Am 09.03.2015 um 09:19 schrieb Kurt Roeckx: On Mon, Mar 09, 2015 at 09:13:31AM +0100, Michael Biebl wrote: Am 19.02.2015 um 07:35 schrieb Kurt Roeckx: severity 760998 serious thanks At this point I'm unable to stop network manager and keep it stopped. Now I have 0.9.10.0-6. The log file shows: NetworkManager[15359]: info exiting (success) systemd[1]: Stopped Network Manager. dbus[658]: [system] Activating via systemd: service name='org.freedesktop.NetworkManager' unit='dbus-org.freedesktop.NetworkManager.service' systemd[1]: Starting Network Manager... dbus[658]: [system] Successfully activated service 'org.freedesktop.nm_dispatcher' systemd[1]: Started Network Manager Script Dispatcher Service. NetworkManager[20467]: info NetworkManager (version 0.9.10.0) is starting... I assume something else restarts it, but I have no idea what. Is there some way to debug this so I can reassign it? It's most likely D-Bus activated, e.g. by nm-applet. I killed nm-applet and that didn't fix it. X isn't even running anymore. Well, from your logs it looked like some client accessed the org.freedesktop.NetworkManager D-Bus interface, triggering the service start. nm-applet was only my first guess. There are various other NM client, including nmcli and nmtui for the command line. Atm, you need to run systemctl disable NetworkManager.service; systemctl stop NetworkManager.service; do stuff; systemctl start NetworkManager.service; systemctl enable NetworkManager.service. I did that with network-manager instead of NetworkManager.service, could that be why that didn't work for me? Not sure. When you run systemctl disable NetworkManager.service, did it remove the /etc/systemd/system/dbus-org.freedesktop.NetworkManager.service symlink? -- 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#760998: [Pkg-utopia-maintainers] Bug#760998: Acknowledgement (network-manager: auto restarts)
On Mon, Mar 09, 2015 at 09:23:22AM +0100, Michael Biebl wrote: Not sure. When you run systemctl disable NetworkManager.service, did it remove the /etc/systemd/system/dbus-org.freedesktop.NetworkManager.service symlink? It shows: # systemctl disable network-manager Synchronizing state for network-manager.service with sysvinit using update-rc.d... Executing /usr/sbin/update-rc.d network-manager defaults Executing /usr/sbin/update-rc.d network-manager disable insserv: warning: current start runlevel(s) (empty) of script `network-manager' overrides LSB defaults (2 3 4 5). insserv: warning: current stop runlevel(s) (0 1 2 3 4 5 6) of script `network-manager' overrides LSB defaults (0 1 6). # ls -l /etc/systemd/system/dbus-org.freedesktop.NetworkManager.service lrwxrwxrwx 1 root root 42 May 23 2014 /etc/systemd/system/dbus-org.freedesktop.NetworkManager.service - /lib/systemd/system/NetworkManager.service While the other shows: # systemctl disable NetworkManager.service Removed symlink /etc/systemd/system/dbus-org.freedesktop.nm-dispatcher.service. Removed symlink /etc/systemd/system/multi-user.target.wants/NetworkManager.service. Removed symlink /etc/systemd/system/dbus-org.freedesktop.NetworkManager.service. Kurt -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed: found 760998 in 0.9.10.0-6
Processing commands for cont...@bugs.debian.org: found 760998 0.9.10.0-6 Bug #760998 [network-manager] network-manager: auto restarts Marked as found in versions network-manager/0.9.10.0-6. thanks Stopping processing here. Please contact me if you need assistance. -- 760998: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=760998 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#760998: Acknowledgement (network-manager: auto restarts)
On Thu, Feb 19, 2015 at 07:35:16AM +0100, Kurt Roeckx wrote: I assume something else restarts it, but I have no idea what. Is there some way to debug this so I can reassign it? I had to go and stop dbus to be able to get my network up. I tried disabling network-manager but even that doesn't seem to help. Kurt -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#760998: [Pkg-utopia-maintainers] Bug#760998: Acknowledgement (network-manager: auto restarts)
Am 19.02.2015 um 07:35 schrieb Kurt Roeckx: severity 760998 serious thanks At this point I'm unable to stop network manager and keep it stopped. Now I have 0.9.10.0-6. The log file shows: NetworkManager[15359]: info exiting (success) systemd[1]: Stopped Network Manager. dbus[658]: [system] Activating via systemd: service name='org.freedesktop.NetworkManager' unit='dbus-org.freedesktop.NetworkManager.service' systemd[1]: Starting Network Manager... dbus[658]: [system] Successfully activated service 'org.freedesktop.nm_dispatcher' systemd[1]: Started Network Manager Script Dispatcher Service. NetworkManager[20467]: info NetworkManager (version 0.9.10.0) is starting... I assume something else restarts it, but I have no idea what. Is there some way to debug this so I can reassign it? It's most likely D-Bus activated, e.g. by nm-applet. Atm, you need to run systemctl disable NetworkManager.service; systemctl stop NetworkManager.service; do stuff; systemctl start NetworkManager.service; systemctl enable NetworkManager.service. Dan, is dropping the D-Bus autoactivation safe, i.e. removing /usr/share/dbus-1/system-services/org.freedesktop.NetworkManager.service? -- 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#760998: [Pkg-utopia-maintainers] Bug#760998: Acknowledgement (network-manager: auto restarts)
On Mon, Mar 09, 2015 at 09:13:31AM +0100, Michael Biebl wrote: Am 19.02.2015 um 07:35 schrieb Kurt Roeckx: severity 760998 serious thanks At this point I'm unable to stop network manager and keep it stopped. Now I have 0.9.10.0-6. The log file shows: NetworkManager[15359]: info exiting (success) systemd[1]: Stopped Network Manager. dbus[658]: [system] Activating via systemd: service name='org.freedesktop.NetworkManager' unit='dbus-org.freedesktop.NetworkManager.service' systemd[1]: Starting Network Manager... dbus[658]: [system] Successfully activated service 'org.freedesktop.nm_dispatcher' systemd[1]: Started Network Manager Script Dispatcher Service. NetworkManager[20467]: info NetworkManager (version 0.9.10.0) is starting... I assume something else restarts it, but I have no idea what. Is there some way to debug this so I can reassign it? It's most likely D-Bus activated, e.g. by nm-applet. I killed nm-applet and that didn't fix it. X isn't even running anymore. Atm, you need to run systemctl disable NetworkManager.service; systemctl stop NetworkManager.service; do stuff; systemctl start NetworkManager.service; systemctl enable NetworkManager.service. I did that with network-manager instead of NetworkManager.service, could that be why that didn't work for me? Kurt -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#779825: no port attached to webserver
at bottom :-
On 3/9/15, Kartik Mistry kartik.mis...@gmail.com wrote:
On Mon, Mar 9, 2015 at 12:08 PM, shirish शिरीष shirisha...@gmail.com
wrote:
AFA /etc/nginx/nginx.conf test failure is concerned, I haven't changed
anything at that file, it's in the default state.
It should not fail if in default state,
_ ~/ sudo /usr/sbin/nginx -t
nginx: the configuration file /etc/nginx/nginx.conf syntax is ok
nginx: configuration file /etc/nginx/nginx.conf test is successful
--
Kartik Mistry/કાર્તિક મિસ્ત્રી | IRC: kart_
{kartikm, 0x1f1f}.wordpress.com
I am guessing the reason for that is none of the packages which nginx
needs to be is installed.
$ apt-file search /usr/sbin/nginx
nginx-extras: /usr/sbin/nginx
nginx-full: /usr/sbin/nginx
nginx-light: /usr/sbin/nginx
I had a look at all the packages which are broken, the few which are
broken are those which depend on network-manager and my system is good
enough with dhcp. This shouldn't affect anything on nginx, at least
the depends don't show network-manager anywhere.
$ ps aux | grep dhcp
root 635 0.0 0.0 25388 136 ?Ss 13:39 0:00
dhclient -v -pf /run/dhclient.eth0.pid -lf
/var/lib/dhcp/dhclient.eth0.leases eth0
root 717 0.0 0.0 2538816 ?Ss 13:39 0:00
dhclient -v -pf /run/dhclient.eth0.pid -lf
/var/lib/dhcp/dhclient.eth0.leases eth0
root 769 0.0 0.0 25388 204 ?Ss 13:39 0:00
dhclient -v -pf /run/dhclient.eth0.pid -lf
/var/lib/dhcp/dhclient.eth0.leases eth0
shirish 6542 0.0 0.1 12724 2156 pts/2S+ 13:57 0:00 grep
--color=auto dhcp
Just showing the depends which nginx-full shows.
Depends: nginx-common (= 1.6.2-5), libc6 (= 2.14), libexpat1 (=
2.0.1), libgd3 (= 2.1.0~alpha~), libgeoip1, libpam0g (= 0.99.7.1),
libpcre3 (= 8.35), libssl1.0.0 (= 1.0.1), libxml2 (= 2.7.4),
libxslt1.1 (= 1.1.25), zlib1g (= 1:1.2.0)
--
Regards,
Shirish Agarwal शिरीष अग्रवाल
My quotes in this email licensed under CC 3.0
http://creativecommons.org/licenses/by-nc/3.0/
http://flossexperiences.wordpress.com
EB80 462B 08E1 A0DE A73A 2C2F 9F3D C7A4 E1C4 D2D8
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#780093: libvirt: error: unsupported configuration: QEMU 2.1.2 is too new for help parsing
Package: libvirt-clients Version: 1.2.9-9 Severity: grave Justification: renders package unusable tglase@tglase:~ $ virsh -c qemu:///system start MirBSD error: Failed to start domain MirBSD error: unsupported configuration: QEMU 2.1.2 is too new for help parsing This with qemu (= 1:2.1+dfsg-11). -- System Information: Debian Release: 8.0 APT prefers unreleased APT policy: (500, 'unreleased'), (500, 'buildd-unstable'), (500, 'unstable') Architecture: x32 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.16.0-4-amd64 (SMP w/4 CPU cores) Locale: LANG=C, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/lksh Init: sysvinit (via /sbin/init) Versions of packages libvirt-clients depends on: ii libapparmor12.9.0-3 ii libaudit1 1:2.4-1+b1 ii libavahi-client30.6.31-4+b2 ii libavahi-common30.6.31-4+b2 ii libc6 2.19-15 ii libcap-ng0 0.7.4-2 ii libdbus-1-3 1.8.16-1 ii libdevmapper1.02.1 2:1.02.90-2.1 ii libgnutls-deb0-28 3.3.8-6 ii libnl-3-200 3.2.24-2 ii libnl-route-3-200 3.2.24-2 ii libreadline66.3-8 ii libsasl2-2 2.1.26.dfsg1-12 ii libselinux1 2.3-2 ii libssh2-1 1.4.3-4 ii libsystemd0 215-12 ii libvirt01.2.9-9 pn libxml2 none ii libyajl22.1.0-2 libvirt-clients recommends no packages. Versions of packages libvirt-clients suggests: ii libvirt-daemon 1.2.9-9 -- 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: tagging 779048
Processing commands for cont...@bugs.debian.org:
tags 779048 + jessie
Bug #779048 {Done: Ondřej Surý ond...@debian.org} [src:libjpeg-turbo]
libjpeg-turbo: Migration of jpeg-progs from Wheezy to Jessie
Added tag(s) jessie.
thanks
Stopping processing here.
Please contact me if you need assistance.
--
779048: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=779048
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#779825: no port attached to webserver
Hi all, First of all thank you Norbert Fischer and Kartik for jumping on this quickly. For some reason I am not subscribed to the bug even though I reported this, hence have tried to subscribe to it let's see what happens. I had a look at the questions asked :- a. Have you made an aptitude update and aptitude safe-upgrade with non-CD sources before trying to install nginx? Ans. This is actually a wheezy install which was updated to jessie about a year back or so. So, in answer to your question, yes have done multiple rounds of aptitude update and aptitude safe-upgrade and do it whenever I have free time. This is a mixed system with majority of packages from testing, a few from sid or experimental (browsers mainly). b. Also, are there any broken packages on your system? You can try detecting and fixing those by issuing: aptitude -f install. Ans. - I would try this but shouldn't aptitude say that at the end as well. I am in the middle of a big update (kernel binaries, grub and few other other things) so will try that at the end. Although I do remember aptitude telling if something is off at the very end, as of the last aptitude run it showed me the following at the very end :- Current status: 42 updates [-40]. AFAIK this does conclude that there are no broken packages, but as have shared above will still try to run it after the end of the aptitude run to see explicitly if there are any broken packages. c. Have you already started another web server which has been bound to TCP port 80? You should stop any of those services beforehand. Bound ports can be seen by issuing sudo netstat -ntlp which also gives you the name of the service. Ans - I was running apache but had purged it as well as got rid of all the configuration files I could find in accordance to that. I ran sudo netstat -ntlp but unfortunately I didn't find either apache/httpd or anything else that was bound to port 80 :( d. Are there any related entries in /var/log/nginx/error.log? If the start script for nginx fails, there's probably some information in the error.log. Ans - There was nothing in error.log but did see some errors in error.log.1 :- /var/log/nginx# cat error.log.1 2015/03/05 14:56:39 [emerg] 24761#0: socket() [::]:80 failed (97: Address family not supported by protocol) 2015/03/05 14:56:46 [emerg] 25074#0: socket() [::]:80 failed (97: Address family not supported by protocol) umm could it be because I am using ipv4 and not ipv6 (My ISP has not moved to IPv6 and guess it will be a long time before they do.) Other than that, see no reason for the above error logs. e. Checking /var/log/syslog and /var/log/messages could give helpful messages as well. Ans. - I found the same errors in /var/log/syslog as well :- $ sudo zcat /var/log/syslog.2.gz | grep 'nginx' Mar 5 14:48:33 debian nginx[19817]: nginx: [emerg] socket() [::]:80 failed (97: Address family not supported by protocol) Mar 5 14:48:33 debian nginx[19817]: nginx: configuration file /etc/nginx/nginx.conf test failed Mar 5 14:48:40 debian nginx[20214]: nginx: [emerg] socket() [::]:80 failed (97: Address family not supported by protocol) Mar 5 14:48:40 debian nginx[20214]: nginx: configuration file /etc/nginx/nginx.conf test failed Mar 5 14:56:39 debian nginx[24761]: nginx: [emerg] socket() [::]:80 failed (97: Address family not supported by protocol) Mar 5 14:56:39 debian nginx[24761]: nginx: configuration file /etc/nginx/nginx.conf test failed Mar 5 14:56:46 debian nginx[25074]: nginx: [emerg] socket() [::]:80 failed (97: Address family not supported by protocol) Mar 5 14:56:46 debian nginx[25074]: nginx: configuration file /etc/nginx/nginx.conf test failed I grepped through all of /var/log/messages but didn't file anything useful. AFA /etc/nginx/nginx.conf test failure is concerned, I haven't changed anything at that file, it's in the default state. Please let me know if any more info. is needed. -- Regards, Shirish Agarwal शिरीष अग्रवाल My quotes in this email licensed under CC 3.0 http://creativecommons.org/licenses/by-nc/3.0/ http://flossexperiences.wordpress.com EB80 462B 08E1 A0DE A73A 2C2F 9F3D C7A4 E1C4 D2D8 -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#779825: no port attached to webserver
On Mon, Mar 9, 2015 at 12:08 PM, shirish शिरीष shirisha...@gmail.com wrote:
AFA /etc/nginx/nginx.conf test failure is concerned, I haven't changed
anything at that file, it's in the default state.
It should not fail if in default state,
_ ~/ sudo /usr/sbin/nginx -t
nginx: the configuration file /etc/nginx/nginx.conf syntax is ok
nginx: configuration file /etc/nginx/nginx.conf test is successful
--
Kartik Mistry/કાર્તિક મિસ્ત્રી | IRC: kart_
{kartikm, 0x1f1f}.wordpress.com
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed: jessie
Processing commands for cont...@bugs.debian.org:
tags 771617 + sid jessie
Bug #771617 {Done: Cyril Brulebois k...@debian.org} [partman-base] installer
beta 2: jessie parted_server segfault on AMD Athlon64
Bug #773274 {Done: Cyril Brulebois k...@debian.org} [partman-base]
installation-reports: parted_server segfault
Bug #778773 {Done: Cyril Brulebois k...@debian.org} [partman-base] Jessie RC1
Installer parted server segfault
Added tag(s) sid and jessie.
Added tag(s) sid and jessie.
Added tag(s) sid and jessie.
tags 771485 + sid jessie
Bug #771485 {Done: Cyril Brulebois k...@debian.org} [partman-base]
installation-reports: Installation disk scan hangs at 81% with LVM inside crypt
partition
Added tag(s) sid and jessie.
tags 779551 + sid jessie
Bug #779551 [devtodo] devtodo: FTBFS, should Build-Depends on libtool-bin
Added tag(s) sid and jessie.
End of message, stopping processing here.
Please contact me if you need assistance.
--
771485: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=771485
771617: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=771617
773274: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=773274
778773: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=778773
779551: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=779551
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#771485: Processed: jessie
Hi Cyril, On Montag, 9. März 2015, Cyril Brulebois wrote: It would really be nice if one could stop pretending bugs don't affect wheezy without at least trying to argument as to why that would be the case. I think I will stop this work instead. If you're too annoyed by this I'm sorry. cheers, Holger signature.asc Description: This is a digitally signed message part.
Bug#768922: [Debian-ha-maintainers] pacemaker in jessie
franz schaefer schae...@mond.at writes: As many of us, see https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=768922. thanks for the link. so from the discussion there the only reason that libqb0 is not newer is that it did not work on kfreebsd which is no longer important as this is droped from beeing fully suported anyway. so the only thing left is to compile libqb0 version 0.17.0-2 which is in sid now for jessie and then the pacemaker 1.1.10+git20130802-4.1 version that was in jessie until recently will work just fine the libqb0 version 0.17.0-2 compiled on jessie out of the box. so that should be quick and easy. who is going to do it? In https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=768922#35 Jonathan Wiltshire (member of the release team) stated that migrating libqb isn't an option. And the pacemaker reversion did not happen either. Lacking direction, other people couldn't do anything about this either. Though in retrospect, I feel like we would have had enough time for migrating libqb after all. It's really sad we got nowhere instead. I'm turning towards getting a fresh cluster stack backported into jessie instead. -- Regards, Feri. -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed: please confirm this bug with zoneminder from Debian
Processing control commands: tags -1 moreinfo Bug #779254 [zoneminder] Zoneminder is partially installed; won't install and won't be removed Added tag(s) moreinfo. severity -1 important Bug #779254 [zoneminder] Zoneminder is partially installed; won't install and won't be removed Severity set to 'important' from 'grave' -- 779254: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=779254 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#779254: please confirm this bug with zoneminder from Debian
control: tags -1 moreinfo control: severity -1 important Hi John, you submitted this bug against a zoneminder version which is not in Debian. Can you please confirm that this bug also applies with versions of zoneminder from Debian? Downgrading the severity until then... cheers, Holger signature.asc Description: This is a digitally signed message part.
Processed: Re: Processed: jessie
Processing control commands:
tag 771617 - sid jessie
Bug #771617 {Done: Cyril Brulebois k...@debian.org} [partman-base] installer
beta 2: jessie parted_server segfault on AMD Athlon64
Bug #773274 {Done: Cyril Brulebois k...@debian.org} [partman-base]
installation-reports: parted_server segfault
Bug #778773 {Done: Cyril Brulebois k...@debian.org} [partman-base] Jessie RC1
Installer parted server segfault
Ignoring request to alter tags of bug #771617 to the same tags previously set
Ignoring request to alter tags of bug #773274 to the same tags previously set
Ignoring request to alter tags of bug #778773 to the same tags previously set
tag 771485 - sid jessie
Bug #771485 {Done: Cyril Brulebois k...@debian.org} [partman-base]
installation-reports: Installation disk scan hangs at 81% with LVM inside crypt
partition
Ignoring request to alter tags of bug #771485 to the same tags previously set
--
771485: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=771485
771617: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=771617
773274: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=773274
778773: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=778773
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: Processed: jessie
Processing control commands:
tag 771617 - sid jessie
Bug #771617 {Done: Cyril Brulebois k...@debian.org} [partman-base] installer
beta 2: jessie parted_server segfault on AMD Athlon64
Bug #773274 {Done: Cyril Brulebois k...@debian.org} [partman-base]
installation-reports: parted_server segfault
Bug #778773 {Done: Cyril Brulebois k...@debian.org} [partman-base] Jessie RC1
Installer parted server segfault
Removed tag(s) sid and jessie.
Removed tag(s) sid and jessie.
Removed tag(s) sid and jessie.
tag 771485 - sid jessie
Bug #771485 {Done: Cyril Brulebois k...@debian.org} [partman-base]
installation-reports: Installation disk scan hangs at 81% with LVM inside crypt
partition
Removed tag(s) sid and jessie.
--
771485: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=771485
771617: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=771617
773274: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=773274
778773: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=778773
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#771485: Processed: jessie
Control: tag 771617 - sid jessie
Control: tag 771485 - sid jessie
Debian Bug Tracking System ow...@bugs.debian.org (2015-03-09):
Processing commands for cont...@bugs.debian.org:
tags 771617 + sid jessie
Bug #771617 {Done: Cyril Brulebois k...@debian.org} [partman-base]
installer beta 2: jessie parted_server segfault on AMD Athlon64
Bug #773274 {Done: Cyril Brulebois k...@debian.org} [partman-base]
installation-reports: parted_server segfault
Bug #778773 {Done: Cyril Brulebois k...@debian.org} [partman-base] Jessie
RC1 Installer parted server segfault
Added tag(s) sid and jessie.
Added tag(s) sid and jessie.
Added tag(s) sid and jessie.
tags 771485 + sid jessie
Bug #771485 {Done: Cyril Brulebois k...@debian.org} [partman-base]
installation-reports: Installation disk scan hangs at 81% with LVM inside
crypt partition
Added tag(s) sid and jessie.
The offending code being there since 2009, I'm pretty sure that
considering pushing a fix for wheezy might be worth it…
It would really be nice if one could stop pretending bugs don't affect
wheezy without at least trying to argument as to why that would be the
case.
KiBi.
signature.asc
Description: Digital signature
Bug#771485: Processed: jessie
Holger Levsen hol...@layer-acht.org (2015-03-09): Hi Cyril, On Montag, 9. März 2015, Cyril Brulebois wrote: It would really be nice if one could stop pretending bugs don't affect wheezy without at least trying to argument as to why that would be the case. I think I will stop this work instead. If you're too annoyed by this I'm sorry. Well, what happened in #757413 doesn't fill me with joy indeed. And now the same happens with these bug reports a few hours after that… Regardless of whether I'm annoyed, I think it would be much more constructive and straightforward to ask when you're not sure. Having tags go back forth (possibly several times) isn't a very productive way of spending everybody's time. KiBi. signature.asc Description: Digital signature
