Bug#732674: uwsgi-plugin-jvm-openjdk-6: bogus rpath
Package: uwsgi-plugin-jvm-openjdk-6 Version: 1.9.17.1-5 Severity: important /usr/lib/uwsgi/plugins/jvm_openjdk6_plugin.so has the following rpath: /usr/lib/jvm/java-6-openjdk-i386/jre/lib/i386/server/ The quotation marks are part of the path! This is certainly not what you wanted. -- Jakub Wilk -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#732675: pure-ftpd: invalid PTR hostnames without corresponding A/AAAA forward entry in logfile
Package: pure-ftpd Version: 1.0.36-1.1 Severity: normal Dear Maintainer, During a security incident with a compromised FTP account I needed to lookup the IP address inside the /var/log/messages log file. Issue: When the foreign host has set bad DNS entries, for example $ORIGIN 2.0.192.in-addr.arpa. 45 IN PTR customer.example.net. 46 IN PTR customer.example.net. 47 IN PTR customer.example.net. $ORIGIN example.net. ; there is no customer IN A record then I get a log entry like Dec 19 10:13:06 kundwebs pure-ftpd: (?@customer.example.net) [WARNING] Authentication failed for user [user001] instead Dec 19 10:13:06 kundwebs pure-ftpd: (?@192.0.2.45) [WARNING] Authentication failed for user [user001] Needed fix: pure-ftpd always must also resolve the host name received from the PTR record in forward direction to ensure that it is not a bogus hostname, i.e. they must be identical. In all cases of wrong DNS configuration, pure-ftpd always must show the naked IP address even if DontResolv=no is set. Workaround by myself: DNS resolution disabled, i.e. echo yes /etc/pure-ftpd/conf/DontResolve To the Debian package maintainers: I recommend to set this behaviour as the package default. -- System Information: Debian Release: 7.2 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable') Architecture: i386 (i686) Kernel: Linux 3.2.0-4-686-pae (SMP w/1 CPU core) Locale: LANG=de_CH.UTF-8, LC_CTYPE=de_CH.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages pure-ftpd depends on: ii libc6 2.13-38 ii libcap2 1:2.22-1.2 ii libpam0g 1.1.3-7.1 ii libssl1.0.0 1.0.1e-2 ii lsb-base 4.1+Debian8+deb7u1 ii openbsd-inetd [inet-superserver] 0.20091229-2 ii pure-ftpd-common 1.0.36-1.1 pure-ftpd recommends no packages. pure-ftpd suggests no packages. -- no debconf information -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#732676: flashplugin-nonfree: Please leave the nosse2 option
Package: flashplugin-nonfree Version: 1:3.4 Severity: wishlist Tags: upstream Dear Maintainer, After update I noticed flash website weren't working; I tried with: # update-flashplugin-nonfree --install Version 11.2.202.332 needs sse2 and this system doesn't have that. It's ok, but when I give: # update-flashplugin-nonfree --nosse2 --install It complains about option --nosse2 I looked at the changelog and one of the points is: * Removed option nosse2. Please leave this option, if possible, to allow automatically install/update of flash plugin; manual intervention is always possible. Thanks. Francesco -- Package-specific info: Debian version: jessie/sid Architecture: i386 Package version: 1:3.4 MD5 checksums: 208968bb1109e8627fa3c08b43814bee /var/cache/flashplugin-nonfree/get-upstream-version.pl 37d99a0fdad1e8da7834a3d586d5b607 /var/cache/flashplugin-nonfree/install_flash_player_10_linux.tar.gz 8793bf636c58c6a273cbf008e0f73e7e /var/cache/flashplugin-nonfree/install_flash_player_11_linux.i386.tar.gz 946f25a67c1bab8c170d786429b00f8d /var/cache/flashplugin-nonfree/install_flash_player_11_linux_i386.tar.gz md5sum: /usr/lib/flashplugin-nonfree/libflashplayer.so: No such file or directory Alternatives: update-alternatives: error: no alternatives for flash-mozilla.so ls: cannot access /usr/lib/mozilla/plugins/flash-mozilla.so: No such file or directory /usr/lib/mozilla/plugins/flash-mozilla.so: ERROR: cannot open `/usr/lib/mozilla/plugins/flash-mozilla.so' (No such file or directory) -- System Information: Debian Release: jessie/sid Architecture: i386 (i686) Kernel: Linux 3.11-2-686-pae (SMP w/1 CPU core) Locale: LANG=it_IT.UTF-8, LC_CTYPE=it_IT.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages flashplugin-nonfree depends on: ii binutils 2.23.91.20131123-1 ii debconf [debconf-2.0] 1.5.52 ii gnupg 1.4.15-1.1 ii libatk1.0-02.10.0-2 ii libcairo2 1.12.16-2 ii libcurl3-gnutls7.34.0-1 ii libfontconfig1 2.11.0-2 ii libfreetype6 2.5.1-1 ii libgcc11:4.8.2-5 ii libglib2.0-0 2.36.4-1 ii libgtk2.0-02.24.22-1 ii libnspr4 2:4.10.2-1 ii libnss32:3.15.3.1-1 ii libpango1.0-0 1.36.0-1+b1 ii libstdc++6 4.8.2-5 ii libx11-6 2:1.6.2-1 ii libxext6 2:1.3.2-1 ii libxt6 1:1.1.4-1 ii wget 1.14-5 flashplugin-nonfree recommends no packages. Versions of packages flashplugin-nonfree suggests: pn flashplugin-nonfree-extrasound none ii fonts-dejavu2.33+svn2514-3 ii hal 0.5.14-8 ii iceweasel 17.0.10esr-1~deb7u1 ii konqueror-nsplugins 4:4.11.3-1 ii ttf-mscorefonts-installer 3.5 ii ttf-xfree86-nonfree 4.2.1-3.1 -- no debconf information -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#732677: RFS: ruby-specinfra/0.0.16-1 [ITP]
Package: sponsorship-requests Severity: wishlist User: debian-de...@debian.or.jp Usertags: debianjp Control: block 732350 by -1 Dear mentors, I am looking for a sponsor for my package ruby-specinfra * Package name: ruby-specinfra Version : 0.0.16-1 Upstream Author : Gosuke Miyashita gosukena...@gmail.com * URL : https://github.com/serverspec/specinfra * License : MIT Section : ruby It builds those binary packages: ruby-specinfra - Common layer for serverspec and configspec To access further information about this package, please visit the following URL: http://mentors.debian.net/package/ruby-specinfra Alternatively, one can download the package with dget using this command: dget -x http://mentors.debian.net/debian/pool/main/r/ruby-specinfra/ruby-specinfra_0.0.16-1.dsc More information about this can be obtained from https://github.com/serverspec/specinfra Regards, KURASHIKI Satoru -- System Information: Debian Release: jessie/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: i386 (i686) Kernel: Linux 2.6.32-20-pve (SMP w/8 CPU cores) Locale: LANG=C, LC_CTYPE=ja_JP.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#732678: git-buildpackage -A calls lintian with the wrong .changes file
Package: git-buildpackage Version: 0.6.7 Severity: normal When you build with git-buildpackage -A, dpkg-buildpackage will generate an *_all.changes file but git-buildpackages will still try to call lintian with an *_arch.changes file. This results in this: Now running lintian... warning: linux-kali_3.12.3-1~kali2_amd64.changes cannot be processed. warning: It is not a valid lab query and it is not an existing file. Finished running lintian. -- System Information: Debian Release: jessie/sid APT prefers unstable APT policy: (500, 'unstable'), (500, 'testing'), (500, 'stable'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.11-2-amd64 (SMP w/4 CPU cores) Locale: LANG=fr_FR.utf8, LC_CTYPE=fr_FR.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages git-buildpackage depends on: ii devscripts2.13.8 ii git 1:1.8.5.1-1 ii man-db2.6.5-2 ii python2.7.5-5 ii python-dateutil 1.5+dfsg-0.1 ii python-pkg-resources 1.4.2-1 Versions of packages git-buildpackage recommends: ii cowbuilder0.73 ii pristine-tar 1.30 Versions of packages git-buildpackage suggests: ii python-notify 0.1.1-3 ii unzip 6.0-10 -- no debconf information -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#732679: test_nodes.ElementTests.test_empty fails for py3: • != \\u2022
Package: python-docutils Version: 0.11-2 Hello, Since recently [1], python-docutils' python3 test fail [2], most likely since the update of python3 from 3.3.2 to 3.3.3: == FAIL: test_empty (__main__.ElementTests) -- Traceback (most recent call last): File test3/test_nodes.py, line 95, in test_empty AssertionError: 'Element mark=•/' != 'Element mark=\\u2022/' - Element mark=•/ ?^ + Element mark=\u2022/ ?^^ This is with LANG=en_US.UTF-8 or C.UTF-8. With the C locale (ASCII only), I get AssertionError: 'Element mark=\u2022/' != 'Element mark=\\u2022/' instead. The quickest way to reproduce this is $ python3 setup.py build --build-lib=build/py3/ $ python3 test3/test_nodes.py ElementTests.test_empty (just tested in a clean and up to date sid schroot.) The most likely cause is the 2to3 conversion of the test. The original code alreaydy differs between 2 and 3: if sys.version_info (3,): self.assertEqual(str(element), 'Element mark=\\u2022/') else: self.assertEqual(str(element), 'Element mark=\u2022/') But in test3/, 2to3 mangles this to if sys.version_info (3,): self.assertEqual(str(element), 'Element mark=\\u2022/') else: self.assertEqual(str(element), 'Element mark=\\u2022/') I. e. exactly the same for both python versions. If I un-break the additional \, then \u2022 is in fact the right representation of •, and the test works again. I'm not sure whether this is an overzealous 2to3 conversion, or whether 2to3 is actually right. FTR, tests with python2 work with both C and C.UTF-8. Thanks for considering, Martin [1] https://jenkins.qa.ubuntu.com/job/trusty-adt-python-docutils/? [2] https://jenkins.qa.ubuntu.com/job/trusty-adt-python-docutils/4/ARCH=i386,label=adt/artifact/results/dsc0t-python3-docutils-stdout -- Martin Pitt| http://www.piware.de Ubuntu Developer (www.ubuntu.com) | Debian Developer (www.debian.org) -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#732677: RFS: ruby-specinfra/0.0.16-1 [ITP]
On Fri, Dec 20, 2013 at 06:00:33PM +0900, KURASHIKI Satoru wrote: I am looking for a sponsor for my package ruby-specinfra * Package name: ruby-specinfra Version : 0.0.16-1 Upstream Author : Gosuke Miyashita gosukena...@gmail.com * URL : https://github.com/serverspec/specinfra * License : MIT Section : ruby checked and uploaded. -- Regards, dai GPG Fingerprint = 0B29 D88E 42E6 B765 B8D8 EA50 7839 619D D439 668E signature.asc Description: Digital signature
Bug#732603: ITP: python-daemonize -- Python module for writing system daemons
Control: tag -1 wontfix Hi all, On Fr 20 Dez 2013 03:02:06 CET, Zbigniew Jędrzejewski-Szmek wrote: On Thu, Dec 19, 2013 at 10:19:55AM +, Neil Williams wrote: On Thu, 19 Dec 2013 10:46:02 +0100 Mike Gabriel mike.gabr...@das-netzwerkteam.de wrote: Package: wnpp Severity: wishlist Owner: Mike Gabriel mike.gabr...@das-netzwerkteam.de * Package name: python-daemonize Version : 2.2.1 Upstream Author : Ilya Otyutskiy ilya.otyuts...@icloud.com * URL : http://pypi.python.org/pypi/daemonize * License : Expat Programming Lang: Python Description : Python module for writing system daemons How does this compare to python-daemon which already exists in Debian and which does the same job? Hi, this probably should wait until [1] is resolved. Nevertheless, looking at http://daemonize.sourceforge.net/daemonize.txt, this package is racy: the parent exits before child is ready (or even executed). This means that it cannot be used to reliably start a dameon. A nice write-up of what is necessary is in [2]. [1] http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=727708 [2] http://www.freedesktop.org/software/systemd/man/daemon.html I have just asked on #debian-ftp to reject my already uploaded package as I also have found a couple of issues with python-daemonize after several more tests (stderr not cleanly closed, exception when a process exits cleanly and the method registered with atexit is evoked, etc.). Meanwhile I could implement my code project using python-daemon and it indeed works much cleaner!!! 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 pgpXzsBjg3fHL.pgp Description: Digitale PGP-Signatur
Bug#732680: insanity is no longer maintained upstream
Package: gst-qa-system Severity: serious Hi, please get the insanity/gst-qa-system package removed from Debian. It is no longer maintained upstream since years and there never was a release. This was mostly an experiment if such an approach can lead to useful results or not, and it failed. This should've never been in Debian at all. Best regards, Sebastian signature.asc Description: This is a digitally signed message part
Bug#732681: gnat-4.8: FTBFS on hurd-i386
Source: gnat-4.8 Version: 4.8.2-5 Severity: important Tags: patch User: debian-h...@lists.debian.org Usertags: hurd Hi, Currently gnat-4.8 FTBFS on GNU/Hurd, see https://buildd.debian.org/status/fetch.php?pkg=gnat-4.8arch=hurd-i386ver=4.8.2-5stamp=1387071188 Attached are four patches enabling the build again: 1) debian_patches_ada-kfreebsd.diff.update: a one line update to the kfreebsd patch to avoid including termio.h which does not exist. 2) debian_patches_gcc_ada_gcc-interface_Makefile.in.diff.update: an update to the patch for adding Hurd support: now both s-osinte-*.adb and s-taprop-*.ads are using the posix versions. 3) debian_patches_ada-s-osinte-gnu.ads.diff: An updated version of the OS Specific interface: s-osinte-gnu.ads 4) debian_rules.patch.diff: A modification of rules.patch to reflect that posix versions are used for the files in 2) above. Of course the generated debian/patches/series file will change accordingly. The first three patches can be proposed upstream when verified that more packages build and work properly with the 4.8 version. Currently only music123 and gcc-mingw-w64 build-depend on gnat-4.8, They have been built w/o problems. Thanks! --- a/debian/patches/ada-kfreebsd.diff 2013-10-31 22:31:40.0 +0100 +++ b/debian/patches/ada-kfreebsd.diff 2013-11-13 01:43:04.0 +0100 @@ -8,7 +8,7 @@ /* On some system termio is either absent or including it will disable termios (HP-UX) */ #if ! defined (__hpux__) ! defined (FREEBSD) \ -+! defined (__FreeBSD_kernel__) \ ++! defined (__FreeBSD_kernel__) ! defined (__GNU__) \ ! defined (__APPLE__) ! defined(__rtems__) # include termio.h #endif --- a/debianpatches/gcc/ada/gcc-interface_Makefile.in.diff 2013-12-17 18:26:05.0 +0100 +++ b/debian/patches/gcc/ada/gcc-interface_Makefile.in.diff 2013-12-17 18:26:53.0 +0100 @@ -11,10 +11,10 @@ + a-numaux.adsa-numaux-x86.ads \ + s-inmaop.adbs-inmaop-posix.adb \ + s-intman.adbs-intman-posix.adb \ -+ s-osinte.adbs-osinte-gnu.adb \ ++ s-osinte.adbs-osinte-posix.adb \ + s-osinte.adss-osinte-gnu.ads \ + s-osprim.adbs-osprim-posix.adb \ -+ s-taprop.adbs-taprop-gnu.adb \ ++ s-taprop.adbs-taprop-posix.adb \ + s-taspri.adss-taspri-posix.ads \ + s-tpopsp.adbs-tpopsp-posix-foreign.adb \ + system.adssystem-freebsd-x86.ads --- /dev/null 2012-01-30 20:41:15.189616186 +0100 +++ b/src/gcc/ada/s-osinte-gnu.ads 2012-04-11 19:34:45.0 +0200 @@ -0,0 +1,813 @@ +-- +-- -- +--GNU ADA RUN-TIME LIBRARY (GNARL) COMPONENTS -- +-- -- +-- S Y S T E M . O S _ I N T E R F A C E -- +-- -- +-- S p e c -- +-- -- +-- Copyright (C) 1991-1994, Florida State University-- +-- Copyright (C) 1995-2011, Free Software Foundation, Inc. -- +-- -- +-- GNARL is free software; you can redistribute it and/or modify it under -- +-- terms of the GNU General Public License as published by the Free Soft- -- +-- ware Foundation; either version 2, or (at your option) any later ver- -- +-- sion. GNARL is distributed in the hope that it will be useful, but WITH- -- +-- OUT ANY WARRANTY; without even the implied warranty of MERCHANTABILITY -- +-- or FITNESS FOR A PARTICULAR PURPOSE. See the GNU General Public License -- +-- for more details. You should have received a copy of the GNU General -- +-- Public License distributed with GNARL; see file COPYING. If not, write -- +-- to the Free Software Foundation, 51 Franklin Street, Fifth Floor, -- +-- Boston, MA 02110-1301, USA. -- +-- -- +-- As a special exception, if other files instantiate generics from this -- +-- unit, or you link this unit with other files to produce an executable, -- +-- this unit does not by itself cause the resulting executable to be -- +-- covered by the GNU General Public License. This exception does not -- +-- however invalidate any other reasons why the executable file might be -- +-- covered by the GNU Public License. -- +-- -- +-- GNARL was developed by the GNARL team at Florida State University. -- +-- Extensive contributions were provided by Ada Core Technologies, Inc. -- +--
Bug#714984: It works :)
Hi Mathieu, I installed the patch: it worked like a charm. For me the bug is SOLVED Thank you -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#732679: test_nodes.ElementTests.test_empty fails for py3: • != \\u2022
tag 732679 patch user ubuntu-de...@lists.ubuntu.com usertags 732679 origin-ubuntu ubuntu-patch trusty thanks I uploaded this diff to Ubuntu which just built (i. e. tests run during package build), and I locally tested it with autopkgtest and in sid. Thanks for considering, Martin -- Martin Pitt| http://www.piware.de Ubuntu Developer (www.ubuntu.com) | Debian Developer (www.debian.org) diff -Nru python-docutils-0.11/debian/changelog python-docutils-0.11/debian/changelog --- python-docutils-0.11/debian/changelog 2013-09-09 22:59:15.0 +0200 +++ python-docutils-0.11/debian/changelog 2013-12-20 10:32:05.0 +0100 @@ -1,3 +1,13 @@ +python-docutils (0.11-2ubuntu1) trusty; urgency=medium + + * Add fix_element_test.diff: Since Python 3.3.3, 2to3 changes our already +existing Python3 specific test for the dot (•) symbol to a double-slash +like in the Python 2 version, breaking the test. Use the actual Unicode +symbol to prevent 2to3 from doing that, instead of \u2022. +(Closes: #732679) + + -- Martin Pitt martin.p...@ubuntu.com Fri, 20 Dec 2013 10:24:09 +0100 + python-docutils (0.11-2) unstable; urgency=low [ Michael Schutte ] diff -Nru python-docutils-0.11/debian/patches/fix_element_test.diff python-docutils-0.11/debian/patches/fix_element_test.diff --- python-docutils-0.11/debian/patches/fix_element_test.diff 1970-01-01 01:00:00.0 +0100 +++ python-docutils-0.11/debian/patches/fix_element_test.diff 2013-12-20 10:32:05.0 +0100 @@ -0,0 +1,17 @@ +Description: Since Python 3.3.3, 2to3 changes our already existing Python3 specific test for the dot (•) symbol to a double-slash like in the Python 2 version, breaking the test. Use the actual Unicode symbol to prevent 2to3 from doing that, instead of \u2022. +Author: Martin Pitt martin.p...@ubuntu.com +Bug-Debian: http://bugs.debian.org/732679 + +Index: python-docutils-0.11/test/test_nodes.py +=== +--- python-docutils-0.11.orig/test/test_nodes.py 2013-12-20 10:18:46.558264159 +0100 python-docutils-0.11/test/test_nodes.py2013-12-20 10:23:56.834258030 +0100 +@@ -92,7 +92,7 @@ + if sys.version_info (3,): + self.assertEqual(str(element), 'Element mark=\\u2022/') + else: +-self.assertEqual(str(element), 'Element mark=\u2022/') ++self.assertEqual(str(element), 'Element mark=•/') + dom = element.asdom() + self.assertEqual(dom.toxml(), u'Element mark=\u2022/') + dom.unlink() diff -Nru python-docutils-0.11/debian/patches/series python-docutils-0.11/debian/patches/series --- python-docutils-0.11/debian/patches/series 2013-08-05 16:35:22.0 +0200 +++ python-docutils-0.11/debian/patches/series 2013-12-20 10:32:05.0 +0100 @@ -11,3 +11,4 @@ no-local-roman.diff rst2odt_prepstyles-elementtree.diff odt-writer-ascii-filenames.diff +fix_element_test.diff
Bug#714984: It works :)
Control: tag -1 - pending On Fri, Dec 20, 2013 at 10:47 AM, Giorgio Quattrone g.quattr...@cineca.it wrote: Hi Mathieu, I installed the patch: it worked like a charm. For me the bug is SOLVED Jay, Could you please do a stable upload ? thanks much -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#732682: lintian: warn explicitly about relative rpath
Package: lintian Version: 2.5.20 Severity: wishlist Consider the following tags: binary-or-shlib-defines-rpath usr/bin/foo1 /usr/lib/foobar binary-or-shlib-defines-rpath usr/bin/foo2 /usr/lib/foobar binary-or-shlib-defines-rpath usr/bin/foo3 usr/lib/foobar They all look awfully similar, and it's not obvious that rpaths for foo2 and foo3 are not absolute. I'd like Lintian to emit a different tag (let's say binary-or-shlib-defines-relative-rpath) if rpath is not absolute. See also bug #732674. -- Jakub Wilk -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#732683: ITP: golang-gnuflag -- Go library for GNU-style flag syntax
Package: wnpp Severity: wishlist Owner: James Page james.p...@ubuntu.com * Package name: golang-gnuflag Version : 0.1~ * URL : http://launchpad.net/gnuflag License:: BSD Programming Lang: Go Description : Go library for GNU-style flag syntax This package is a fork of the standard Go flag package that supports GNU-style flag syntax. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#732684: ITP: golang-mgo -- Go library for MongoDB
Package: wnpp Severity: wishlist Owner: James Page james.p...@ubuntu.com * Package name: golang-mgo Version : 0.1~ * URL : http://labix.org/mgo * License : BSD Programming Lang: Go Description : Go library for MongoDB mgo (pronounced as mango) is a MongoDB driver for the Go language that implements a rich and well tested selection of features under a very simple API following standard Go idioms. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#732685: [regression] comedilib ships old comedi-calibrate
Package: src:comedilib Version: 0.10.1-1 The update from 0.10.0 to 0.10.1 brought a new version of comedi-calibrate which is actually a _very_ old version (from 2007). I think the mistake comes from the fact that there is no up-to-date tarball of comedi-calibrate at http://www.comedi.org/download/. comedi_calibrate-1.tar.gz is this really old version from 2007. The only way I know to get a tarball from the latest comedi-calibrate is via git: http://comedi.org/git?p=comedi/comedi_calibrate.git;a=snapshot;h=refs/heads/master;sf=tgz Note that actually, not change has been made to comedi-calibrate since the one released with comedi 0.10.0. Cheers, Éric PS: There is also another little problem in the debian/ directory brought by the upgrade to 0.10.1. debian/03-bison.path and debian/series should probably not be there. The actual used files are in debian/patches/ -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#732643: [buildd-tools-devel] Bug#732643: I just discovered this is a duplicate of bug 675512
forcemerge 732643 675512 thanks On Thu, Dec 19, 2013 at 11:10:39AM -0800, Zach Carter wrote: Feel free to mark this as a duplicate of http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=675512 No problem, thanks. I'll try to get to this as part of the 1.7.x development stuff in the new year. In this specific case, to you want to give permissions to the other user at the time of creating the snapshot, or later on? We might need to provide for both use cases, but the former is probably simpler since we can just write out the session file with the updated permissions, rather than doing edits after session creation (which is still possible, but will probably need more command-line options to enable). Thanks, Roger -- .''`. Roger Leigh : :' : Debian GNU/Linuxhttp://people.debian.org/~rleigh/ `. `' schroot and sbuild http://alioth.debian.org/projects/buildd-tools `-GPG Public Key F33D 281D 470A B443 6756 147C 07B3 C8BC 4083 E800 -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#732679: test_nodes.ElementTests.test_empty fails for py3: • != \\u2022
Hey Jakub, Jakub Wilk [2013-12-20 10:36 +0100]: The last line should have probably been: self.assertEqual(str(element), u'Element mark=\u2022/') [...] ...then it would be correctly converted to: self.assertEqual(str(element), 'Element mark=\u2022/') Ah, that's even more elegant indeed. In the past it worked only by accident, due to a bug: http://bugs.python.org/issue18037 Thanks for pointing out the root cause! Martin -- Martin Pitt| http://www.piware.de Ubuntu Developer (www.ubuntu.com) | Debian Developer (www.debian.org) -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#732679: test_nodes.ElementTests.test_empty fails for py3: • != \\u2022
Control: severity -1 serious The bug makes the package FTBFS, so I bumped severity. The most likely cause is the 2to3 conversion of the test. The original code alreaydy differs between 2 and 3: if sys.version_info (3,): self.assertEqual(str(element), 'Element mark=\\u2022/') else: self.assertEqual(str(element), 'Element mark=\u2022/') The last line should have probably been: self.assertEqual(str(element), u'Element mark=\u2022/') But in test3/, 2to3 mangles this to if sys.version_info (3,): self.assertEqual(str(element), 'Element mark=\\u2022/') else: self.assertEqual(str(element), 'Element mark=\\u2022/') ...then it would be correctly converted to: self.assertEqual(str(element), 'Element mark=\u2022/') In the past it worked only by accident, due to a bug: http://bugs.python.org/issue18037 -- Jakub Wilk -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#732686: Vcs-Browser control field typo
Source: python-fuse Version: 2:0.2.1-8 The line in debian/control reading Vcs-Browser: http://anonscm.debian.org/git/collab-maint/python-fuse.git has a bad URL; it should read Vcs-Browser: http://anonscm.debian.org/gitweb/?p=collab-maint/python-fuse.git Also, that repository is slightly broken: you need to push a branch (preferably master), otherwise gitweb and git clone get confused. Cheers, --Barak. -- Barak A. Pearlmutter Hamilton Institute Dept Comp Sci, NUI Maynooth, Co. Kildare, Ireland http://www.bcl.hamilton.ie/~barak/ -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#732247: grub-xen: Package description doesn't explain if this package is thought for DomUs or Dom0s
On Mon, Dec 16, 2013 at 12:48:40AM +0100, Axel Beckert wrote: the current package description of grub-xen leaves open if this package is thought for DomUs (guest machines) or Dom0s (host machines): This package contains a version of GRUB that has been built for use with the Xen hypervisor (i.e. PV-GRUB). I though suspect it's for use within a DomU (c.f. http://wiki.xen.org/wiki/PvGrub), so I suggest a more verbose description like this: This package contains a version of GRUB that has been built for use inside Xen guest domains (DomUs), i.e. for use with PV-GRUB. . It does not need to be installed on the Xen Dom0. It's actually both; the intention is that you can install it within a domU so that it always matches the grub.cfg there, and also have a copy in dom0 to replace the old PV-GRUB. (In either case it will run in the domU context.) The configuration code is still evolving, though, so some assembly is still required. Mind if I park this bug temporarily until the configuration is a bit more established? -- Colin Watson [cjwat...@debian.org] -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#714928: Bug#732668: /bin/sed: can't read /usr/lib/libgobject-2.0.la: No such file or directory
On 20/12/13 05:55, Fabián Bonetti wrote: /bin/sed: can't read /usr/lib/libgobject-2.0.la: No such file or directory The nonexistence of this file is not a bug in glib. Packages that need to compile against libgobject-2.0 should use pkg-config and/or libtool, both of which cope gracefully with missing .la files. Distributions should not ship .la files, at least not for libraries in /usr: they are actively harmful. Context: https://wiki.debian.org/ReleaseGoals/LAFileRemoval S -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#732688: git-buildpackage: git-import-orig fails if source tarball contains .git configuration file
Package: git-buildpackage Version: 0.6.7 Severity: normal Steps to reproduce == pull-debian-source -d python-librabbitmq mkdir python-librabbitmq cd python-librabbitmq git-import-dscs --pristine-tar ../python-librabbitmq_1.0.1-1.dsc Error message = gbp:info: Tag upstream/1.0.1 not found, importing Upstream tarball gbp:error: Git command failed: Error running git add: fatal: Not a git repository: rabbitmq-codegen/../.git/modules/rabbitmq-codegen gbp:error: Failed to import '[...]/python-librabbitmq_1.0.1-1.dsc' Analysis The upstream tarball contains the file rabbitmq-codegen/.git that contains the line gitdir: ../.git/modules/rabbitmq-codegen. git-buildpackage uses this git configuration file instead of just ignoring it. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#718730: Please update xkb to version 2.8
On Thu, Dec 19, 2013 at 22:00:26 +0400, Dmitry Shachnev wrote: On Thu, Dec 19, 2013 at 3:54 PM, Julien Cristau jcris...@debian.org wrote: Merged, thanks. I'll try to upload soon. Thanks. Note that it won’t build from Git tree because contents of upstream tarball are different from contents of upstream Git. That shouldn't be an issue, unless the differences are in binary files. That’s one of the reasons why I prefer Debian-dir-only Git branches. I backed out the 3.0 (quilt) switch though. I am fine with that, but why? See above... Cheers, Julien -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#732687: debian-maintainers: Gnome doesn't work after update.
Package: debian-maintainers Severity: normal Dear Maintainer, *** Please consider answering these questions, where appropriate *** Hello, yesterday I installed debian security updates 7, which saw several of Xorg is included. Well today to start as usual gnome told me that he had not charged either. I had the new desk, and now only charge me the classic. Other problem is that when I enter facebook or similar sites, the session is closed and no further leads me to the home screen of debian. I have a nvidia gt320m graphics and have installed the private driver before upgrading and worked very well. I searched to see if someone else happened to him and I have found no results. *** End of the template - remove these lines *** -- System Information: Debian Release: 7.3 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 3.2.0-4-amd64 (SMP w/4 CPU cores) Locale: LANG=es_ES.utf8, LC_CTYPE=es_ES.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#732689: ipset: kernel panic when adding ip to bitmap:ip
Package: ipset Version: 6.12.1-1 Severity: important # ipset create ipv4_ch bitmap:ip range 0.0.0.0/0 # ipset list [ another previously defined hash:net set. No problem with that. ] Name: ipv4_ch Type: bitmap:ip Header: range 0.0.0.0-255.255.255.255 Size in memory: 120 References: 0 Members: # ipset add ipv4_ch 5.1.96.0/21 Message from syslogd@pe1 at Dec 20 12:14:53 ... kernel:[3088568.395819] Oops: 0002 [#1] SMP Message from syslogd@pe1 at Dec 20 12:14:53 ... kernel:[3088568.398495] Stack: Message from syslogd@pe1 at Dec 20 12:14:53 ... kernel:[3088568.398495] Call Trace: Message from syslogd@pe1 at Dec 20 12:14:53 ... kernel:[3088568.398495] Code: 31 c0 48 85 ff 74 19 48 81 ff ff ff ff 7f b0 01 74 0e 48 8b 05 e7 af 1e e1 48 29 f8 48 c1 e8 3f c3 48 8b 47 40 0f b7 16 48 8b 00 f0 0f ab 10 19 d2 83 fa 01 19 c0 f7 d0 25 f9 ef ff ff c3 48 8b Message from syslogd@pe1 at Dec 20 12:14:53 ... kernel:[3088568.398495] CR2: 0c10 Message from syslogd@pe1 at Dec 20 12:14:53 ... kernel:[3088568.428341] Kernel panic - not syncing: Fatal exception in interrupt That's all. The machine hung completely and needed a hard reset. -- System Information: Debian Release: 7.3 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.2.0-4-amd64 (SMP w/4 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages ipset depends on: ii iptables 1.4.14-3.1 ii libc6 2.13-38 ii libipset2 6.12.1-1 ipset recommends no packages. ipset suggests no packages. -- no debconf information -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#732690: acpi-support: Adding support for i3lock
Package: acpi-support Version: 0.141-2 Severity: wishlist Dear Maintainer, please add support for i3lock in lib/screenblank. It is in /usr/bin/i3lock and can be started like xtrlock. I'm sorry I couldn't include a patch, as I couldn't figure out how to create one for a patch file. Best regards, Andre Bubel -- System Information: Debian Release: jessie/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.11-2-amd64 (SMP w/8 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) (ignored: LC_ALL set to en_US.UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages acpi-support depends on: ii acpi-fakekey 0.141-2 ii acpi-support-base 0.141-2 ii acpid 1:2.0.20-1 ii lsb-base 4.1+Debian12 ii pm-utils 1.4.1-13 ii x11-xserver-utils 7.7+1 Versions of packages acpi-support recommends: ii rfkill0.5-1 ii xscreensaver 5.23-1 Versions of packages acpi-support suggests: pn radeontool none ii vbetool 1.1-3 pn xinput none -- Configuration Files: /etc/default/acpi-support changed [not included] -- no debconf information -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#732247: grub-xen: Package description doesn't explain if this package is thought for DomUs or Dom0s
Hi Colin, Colin Watson wrote: On Mon, Dec 16, 2013 at 12:48:40AM +0100, Axel Beckert wrote: the current package description of grub-xen leaves open if this package is thought for DomUs (guest machines) or Dom0s (host machines): This package contains a version of GRUB that has been built for use with the Xen hypervisor (i.e. PV-GRUB). I though suspect it's for use within a DomU [...] It's actually both; Oh, ok. the intention is that you can install it within a domU so that it always matches the grub.cfg there, and also have a copy in dom0 to replace the old PV-GRUB. That's surprising. IIRC pv-grub-menu is a relative new package and there were some issues with pv-grub support in Debian's Xen in the past. Didn't know that pv-grub is already deprecated again. (Haven't yet started playing with it. :-) The configuration code is still evolving, though, so some assembly is still required. OK. Planned to play around it with on my Xen test box at work after the season's holidays. Mind if I park this bug temporarily until the configuration is a bit more established? Not at all! I gyess it serves perfectly as reminder to rework the description once the package stabilizes. :-) Thanks for the feedback! Regards, Axel -- ,''`. | Axel Beckert a...@debian.org, http://people.debian.org/~abe/ : :' : | Debian Developer, ftp.ch.debian.org Admin `. `' | 1024D: F067 EA27 26B9 C3FC 1486 202E C09E 1D89 9593 0EDE `-| 4096R: 2517 B724 C5F6 CA99 5329 6E61 2FF9 CD59 6126 16B5 -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#732247: grub-xen: Package description doesn't explain if this package is thought for DomUs or Dom0s
On Fri, Dec 20, 2013 at 01:03:49PM +0100, Axel Beckert wrote: Colin Watson wrote: the intention is that you can install it within a domU so that it always matches the grub.cfg there, and also have a copy in dom0 to replace the old PV-GRUB. That's surprising. IIRC pv-grub-menu is a relative new package and there were some issues with pv-grub support in Debian's Xen in the past. Didn't know that pv-grub is already deprecated again. (Haven't yet started playing with it. :-) Well, PV-GRUB was based on GRUB Legacy, so in some sense its underlying code has been deprecated for years. It's just that until recently there hasn't been a viable replacement (other than PyGRUB, which has fundamental security issues because it parses the domU's filesystem in the dom0). If you want a sense of the general direction here, see https://lists.gnu.org/archive/html/grub-devel/2013-12/msg00184.html and thread, although I need to entirely rework the patch set. Cheers, -- Colin Watson [cjwat...@debian.org] -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#732691: Pressing alignment or Ctrl+G only results in a dialog with a cancel button
Package: gentle Version: 1.9+cvs20100605+dfsg1-2 Severity: normal Dear Maintainer, Steps to reproduce: 1. Start GENtle. 2. Open Tools- Alignment (Or press Ctrl+g). Expected outcome: Dialog with alignment options. Actual outcome: A dialog pops up, but it only contains a Cancel button. (It seems like it contains more controls, but they are obscured by the Cancel button) (This was originally reported in Ubuntu as https://bugs.launchpad.net/ubuntu/+source/gentle/+bug/713273) -- System Information: Debian Release: jessie/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: i386 (i686) Kernel: Linux 3.11-2-686-pae (SMP w/1 CPU core) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages gentle depends on: ii libc6 2.17-97 ii libgcc1 1:4.8.2-10 ii libmysqlclient18 5.5.33+dfsg-1 ii libsqlite02.8.17-9 ii libsqlite3-0 3.8.2-1 ii libstdc++64.8.2-10 ii libtinyxml2.6.2 2.6.2-2 ii libwxbase2.8-02.8.12.1+dfsg-2 ii libwxgtk2.8-0 2.8.12.1+dfsg-2 Versions of packages gentle recommends: ii clustalw 2.1+lgpl-4 gentle suggests no packages. -- no debconf information -- mvh / best regards Hans Joachim http://desserud.org -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#732692: loading radeonkms results in unusable screen
Package: kfreebsd-image-10.0-0-amd64 Version: 10.0~svn259404-1 Severity: important Loading radeonkms (without non-free firmware) in my Radeon HD 2400 PRO (RV610 chip, PCI id 0x1002 / 0x94c3) results in unusable screen, full of color noise. It seems that while this doesn't apply to all the cards, there are some where the driver becomes completely unusable unless the firmware blobs are loaded. This situation seems completely unworkable. Unless someone has a better idea, I'll remove radeonkms from the Debian package. I just can't see any advantage in shipping it: Users who want the firmware blobs can install kfreebsd-downloader-10, and users who refuse to install non-free firmware will be better served by VESA than by a crippled driver. -- Robert Millan -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#728304: for schroot backend allow to run tests as user while installation steps as root
Hello Yaroslav, Yaroslav Halchenko [2013-10-30 8:48 -0400]: Adding user's login to root-users configuration of schroot allows autopkgtest to invoke apt-get with necessary privileges, but then tests also run under root user, instead of the original user Please note that you can have this behaviour with the current autopkgtest if you explicitly specify the --user $USER adt-run option. Then it'll use root to install dependencies and $USER to run tests. There already was a test to make sure that works, I just committed some extended tests that also make sure that dependency installation still works with --user, and that needs-root is respected properly. Indeed the test gets run as root if you call adt-run as normal user with the schroot runner. It should default to running them as the calling user instead. I'll devote this bug report to this. Thanks, Martin -- Martin Pitt| http://www.piware.de Ubuntu Developer (www.ubuntu.com) | Debian Developer (www.debian.org) -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#732693: unable to setup DHCP in kfreebsd-11
Package: kfreebsd-image-11.0-0-amd64 Version: 11.0~svn259528-2 Severity: grave On 20/12/2013 11:05, Markus Koschany wrote: Unfortunately ip4 networking doesn't work anymore with freebsd 11 but works fine when I use kfreebsd-image-9.2-1. The em0 interface is up but I don't get a DHCP lease. It seems that is another issue to look into. I got that, too. IIRC there was some error with ioctls in ifconfig. Fortunately it's kfreebsd-11 only. If you've got spare time to do some tests, it would help to know which version of the kfreebsd-11 package introduced this bug. -- Robert Millan -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#475327: evince maps window with incorrect size
Control: found -1 3.10.0-1 On 2008-04-09 22:43:05 -0400, Ivan Jager wrote: I'm having some trouble reproducing this, but here is what happened: 1. I clicked on a pdf in galeon, and let it open it with evince. 2. Evince popped up and got placed by the window manager (AFAICT) 3. Evince loaded the document, and resized itself, such that it's placement was stupid. (a good chunk of it ended up on the other monitor) I can reproduce this for documents that are opened for the first time with evince. I use fvwm's ActivePlacement feature. The problem is that evince doesn't provide the correct window size to the window manager early enough. This is the same problem as with gnuplot-qt using the qt terminal: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=668956 When I try to reproduce it, it now opens the window with it's previous geometry, and stays that way after loading the PDF. After further experimentation, it seems that it uses the previous geometry for a document of the same page size (remembering multiple geometry - page_size mappings) and only does the stupid resizing when it encounters a document with a new page size. Actually evince (at least 3.10.0-1) seems to remember the filename, not the page size, which is also stupid. $ evince file1.pdf [evince does the stupid resize (a)] $ evince file1.pdf [evince has remembered the window position for (a)] $ cp file1.pdf foo.pdf $ evince foo.pdf [evince does the stupid resize (b)] $ evince file2.pdf [evince does the stupid resize (c)] $ cp file2.pdf foo.pdf $ evince foo.pdf [evince uses the remembered window position for (b)] This makes no sense, as the document is completely unrelated! Sorry, but I think xpdf does the right thing here... Yes (trying evince since xpdf no longer works with newer fontconfig...). -- Vincent Lefèvre vinc...@vinc17.net - Web: http://www.vinc17.net/ 100% accessible validated (X)HTML - Blog: http://www.vinc17.net/blog/ Work: CR INRIA - computer arithmetic / AriC project (LIP, ENS-Lyon) -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#732694: scribus: Insert - Frame rendering leads to pdflatex error message
Package: scribus Version: 1.4.2.dfsg+r18267-1 Severity: normal Dear Maintainer, Steps to reproduce: 1. Start scribus and select a new document. 2. Select Insert-Insert Render Frame. 3. Click and drag to create a rectangle. After creating the rectangle, I get an error message with the following message: The application pdflatex --interaction nonstopmode failed to start! Please check the path: (Oddly enough, no path is printed though.) At the same time I get the following error in the terminal: RENDER FRAME: latexError(): Running the application pdflatex --interaction nonstopmode failed! 0 (Originally reported to Ubuntu as https://bugs.launchpad.net/ubuntu/+source/scribus/+bug/915388) -- System Information: Debian Release: jessie/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: i386 (i686) Kernel: Linux 3.11-2-686-pae (SMP w/1 CPU core) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages scribus depends on: ii ghostscript9.05~dfsg-8+b1 ii libc6 2.17-97 ii libcairo2 1.12.16-2 ii libcups2 1.6.4-2 ii libfontconfig1 2.11.0-2 ii libfreetype6 2.5.1-2 ii libgcc11:4.8.2-10 ii libhunspell-1.3-0 1.3.2-6 ii libhyphen0 2.8.6-3 ii libjpeg8 8d-2 ii liblcms1 1.19.dfsg-1.2+b1 ii libpodofo0.9.0 0.9.0-1.1+b1 ii libpython2.7 2.7.6-3 ii libqt4-network 4:4.8.5+git192-g085f851+dfsg-2 ii libqt4-xml 4:4.8.5+git192-g085f851+dfsg-2 ii libqtcore4 4:4.8.5+git192-g085f851+dfsg-2 ii libqtgui4 4:4.8.5+git192-g085f851+dfsg-2 ii libstdc++6 4.8.2-10 ii libtiff4 3.9.7-3 ii libxml22.9.1+dfsg1-3 ii python 2.7.5-5 ii python-tk 2.7.5-1 ii zlib1g 1:1.2.8.dfsg-1 Versions of packages scribus recommends: ii cups-bsd 1.6.4-2 ii xfonts-scalable 1:1.0.3-1 Versions of packages scribus suggests: pn icc-profiles none pn scribus-template none -- no debconf information -- mvh / best regards Hans Joachim http://desserud.org -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#732666: [Pkg-libvirt-maintainers] Bug#732666: libvirt-bin: special device cgroup_memory does not exist
On Fri, 20 Dec 2013 08:07:51 +0100, Guido Günther wrote: You need cgroup_enable=memory on the kernel command line to enable the memory cgroup. Could you check if this fixes your problem as well? If so we should add some run time detection. Yes, adding this to the command line allows the mount to work and libvirtd starts up again. Thanks, -- mike -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#732578: Issue after conversion of AppArmor package to dh(1) and Multi-Arch
Hi Steve, Steve Langasek wrote (19 Dec 2013 18:28:09 GMT) : I haven't seen this issue and don't have any ideas, no. The package in Ubuntu doesn't have this problem. Indeed, libapparmor-perl 2.8.0-0ubuntu35 for i386 does ship the file we're missing. Is it reproducible in a clean build on i386? Yes, the i386 binary package that exposes this issue was built on the Debian buildd network: https://buildd.debian.org/status/fetch.php?pkg=apparmorarch=i386ver=2.8.0-3stamp=1386964661 ... but the source package currently FTBFS in my pbuilder sid i386 and amd64 chroots (same for 2.8.0-0ubuntu35, FWIW), so I can't confirm this issues is still current. I will report the FTBFS separately. Otherwise, I would suggest looking for any debian/rules delta between the Debian and Ubuntu packages at this point, since it was from Ubuntu that Kees grabbed my changes. Sure, this is way to go. Kees, I think I'm done with the initial investigation. May you please take over from this point? Thank you, Steve, for your help! Cheers, -- intrigeri | GnuPG key @ https://gaffer.ptitcanardnoir.org/intrigeri/intrigeri.asc | OTR fingerprint @ https://gaffer.ptitcanardnoir.org/intrigeri/otr.asc -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#732405: prima: FTBFS (TIFF_VERSION undeclared)
tags 732405 +fixed-upstream thanks From a quick google this appears to be fixed upstream, unfortunately the bug report does not appear to have a link to the fix. https://rt.cpan.org/Public/Bug/Display.html?ShowHeaders=1;id=77087 -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#515865: running evince foo.pdf from command line doesn't open new window
Control: found -1 3.10.0-1 On 2009-03-23 16:46:07 -0500, Joseph Maher wrote: Le mardi 17 février 2009 à 20:44 -0600, Joseph Maher a écrit : and then run it again, you don't get a second window, and your focus gets shifted to the first, even if it is on a completely different desktop... I think this is expected, as opening another window for the same document is counterproductive. How do you think it should behave? I preferred the original behaviour, opening a new window on the current desktop - I sometimes wish to look at different parts of the same document on different desktops... Ditto. This also means that the -f (--fullscreen) option doesn't work if the file is already open in evince somewhere. The control of the behavior could be an option. -- Vincent Lefèvre vinc...@vinc17.net - Web: http://www.vinc17.net/ 100% accessible validated (X)HTML - Blog: http://www.vinc17.net/blog/ Work: CR INRIA - computer arithmetic / AriC project (LIP, ENS-Lyon) -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#519590: Snort - bug in Jessie - similar to 519590
update on information should be attached regards Richard A Lough Subject: Re: snort: Snort now uses all available CPU cycles contiuously Followup-For: Bug #519590 Package: snort Version: 2.9.5.3-3 Dear Maintainer, *** Please consider answering these questions, where appropriate *** * What led up to the situation? My best guess is that my upgrade to this version caused the bug to appear. * What exactly did you do (or not do) that was effective (or ineffective)? I downgraded to the version of snort currently available from Debian|wheezy * What was the outcome of this action? On the current, installed version of snort, one cpu runs at near 100% continuously with nothing appearing in the log. If I change the interface from eth1 to eth0 (eth0 is unused) the cpu cycles fall to near zero. I have tried different linux kernels, none seemed to help. Reverting to the snort version available from wheezy restores normal operation, as far as I can tell. -- System Information: Debian Release: jessie/sid APT prefers testing APT policy: (500, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 3.11.8 (SMP w/4 CPU cores) Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages snort depends on: pn adduser none pn debconf | debconf-2.0none pn libc6none pn libdaq0 none pn libdumbnet1 none pn libpcap0.8 none pn libpcre3 none pn logrotatenone pn net-toolsnone pn rsyslog | system-log-daemon none ii snort-common 2.9.5.3-3 ii snort-common-libraries 2.9.5.3-3 ii snort-rules-default 2.9.5.3-3 pn zlib1g none Versions of packages snort recommends: pn iproute2 none Versions of packages snort suggests: pn snort-doc none -- debconf information: snort/invalid_interface: * snort/send_stats: true * snort/stats_treshold: 1 snort/disable_promiscuous: false * snort/startup: boot * snort/stats_rcpt: root snort/config_parameters: * snort/address_range: 192.168.1.0/24 snort/please_restart_manually: * snort/interface: eth1 snort/options:
Bug#732696: os-prober: Fails to detect new package-management Haiku builds
Package: os-prober Version: 1.63 Severity: important Tags: patch Haiku's new package management builds have changed the way the kernel and boot sector is laid out, and os-prober's detection routines no longer detect such Haiku partitions. Currently package management builds are only available in nightly releases but there should be an official release Real Soon Now, and package management should become the norm. It'd be nice to get this fixed before this happens. I enclose a patch which should fix this (to be applied to /usr/lib/os- probes/mounted/83haiku). -- System Information: Debian Release: 7.2 APT prefers stable APT policy: (990, 'stable'), (500, 'sid'), (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.2.0-4-amd64 (SMP w/8 CPU cores) Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages os-prober depends on: ii libc6 2.17-97 os-prober recommends no packages. os-prober suggests no packages. -- no debconf information --- /usr/lib/os-probes/mounted/83haiku 2012-08-22 19:21:32.0 +0100 +++ /tmp/83haiku 2013-12-20 12:17:29.143209425 + @@ -13,18 +13,34 @@ *) debug $partition is not a BeFS partition: exiting; exit 1 ;; esac -if head -c 512 $partition | grep -qs system.haiku_loader; then +if head -c 512 $partition | grep -qs 'system.*haiku_loader'; then debug Stage 1 bootloader found else debug Stage 1 bootloader not found: exiting exit 1 fi -if system=$(item_in_dir system $mpoint) +system=$(item_in_dir system $mpoint) +packages=$(item_in_dir packages $mpoint/$system) +found= +if [ $system != ] item_in_dir -q haiku_loader $mpoint/$system (item_in_dir -q kernel_x86 $mpoint/$system || item_in_dir -q kernel_x86_64 $mpoint/$system) then + found=1 +fi + +if [ $found = ] [ $packages != ] + item_in_dir -q haiku_loader\-.* $mpoint/$system/$packages + (item_in_dir -q haiku_x86\-.* $mpoint/$system/$packages || + item_in_dir -q haiku_x86_64\-.* $mpoint/$system/$packages) +then + found=1 +fi + +if [ $found != ] +then debug Stage 2 bootloader and kernel found label=$(count_next_label Haiku) result $partition:Haiku:$label:chain signature.asc Description: OpenPGP digital signature
Bug#732697: /usr/sbin/dibbler-client: dibbler_client: segfaults in TClntCfgMgr::validateConfig
Package: dibbler-client
Version: 1.0.0~rc1-1
Severity: serious
File: /usr/sbin/dibbler-client
Tags: ipv6
Justification: Policy 3.3
Each time I start dibbler-client, it terminates with a segmentation fault.
Compiling with debug symbols and starting with GDB I get:
# gdb --args dibbler-client run
GNU gdb (GDB) 7.6.1 (Debian 7.6.1-1)
...
Reading symbols from /usr/sbin/dibbler-client...Reading symbols from
/usr/lib/debug/.build-id/00/e3a4d011a15fdf6c9c425ab9d7cfc1d8e1a168.debug...done.
done.
(gdb) run
Starting program: /usr/sbin/dibbler-client run
[tcsetpgrp failed in terminal_inferior: Unpassender IOCTL (I/O-Control) für das
Gerät]
warning: no loadable sections found in added symbol-file system-supplied DSO at
0x77ffa000
[tcsetpgrp failed in terminal_inferior: Unpassender IOCTL (I/O-Control) für das
Gerät]
warning: Could not load shared library symbols for linux-vdso.so.1.
Do you need set solib-search-path or set sysroot?
[tcsetpgrp failed in terminal_inferior: Unpassender IOCTL (I/O-Control) für das
Gerät]
[Thread debugging using libthread_db enabled]
Using host libthread_db library /lib/x86_64-linux-gnu/libthread_db.so.1.
[tcsetpgrp failed in terminal_inferior: Unpassender IOCTL (I/O-Control) für das
Gerät]
| Dibbler - a portable DHCPv6, version 1.0.0RC1 (CLIENT, Linux port)
| Authors : Tomasz Mrugalskithomson(at)klub.com.pl,Marek
Senderskimsend(at)o2.pl
| Licence : GNU GPL v2 only. Developed at Gdansk University of Technology.
| Homepage: http://klub.com.pl/dhcpv6/
2013.12.20 12:54:56 Client Warning Pid file found (pid=4676, file
/var/lib/dibbler/client.pid), but process 4676 does not exist.
2013.12.20 12:54:56 Client NoticeMy pid (32038) is stored in
/var/lib/dibbler/client.pid
2013.12.20 12:54:56 Client NoticeDetected iface eth0/2,
MAC=90:2b:34:a0:08:48.
2013.12.20 12:54:56 Client NoticeDetected iface lo/1, MAC=00:00:00:00:00:00.
2013.12.20 12:54:56 Client NoticeParsing /etc/dibbler/client.conf config
file...
2013.12.20 12:54:56 Client Debug Parsing /etc/dibbler/client.conf done,
result=0
2013.12.20 12:54:56 Client Debug 1 interface(s) specified in
/etc/dibbler/client.conf
2013.12.20 12:54:56 Client Info Interface eth0/2 configuration has been
loaded.
Program received signal SIGSEGV, Segmentation fault.
TClntCfgMgr::validateConfig (this=this@entry=0x6f4da0) at ClntCfgMgr.cpp:530
530 if (digests[0] != DIGEST_HMAC_MD5) {
(gdb) bt
#0 TClntCfgMgr::validateConfig (this=this@entry=0x6f4da0) at ClntCfgMgr.cpp:530
#1 0x00447428 in TClntCfgMgr::parseConfigFile
(this=this@entry=0x6f4da0, cfgFile=...) at ClntCfgMgr.cpp:135
#2 0x00447695 in TClntCfgMgr::TClntCfgMgr (this=0x6f4da0, cfgFile=...)
at ClntCfgMgr.cpp:62
#3 0x004478e1 in TClntCfgMgr::instanceCreate (cfgFile=...) at
ClntCfgMgr.cpp:47
#4 0x00408d12 in TDHCPClient::TDHCPClient (this=0x7fffe460,
config=...) at ./Misc/DHCPClient.cpp:41
#5 0x004075d3 in run () at ./Port-linux/dibbler-client.cpp:87
#6 0x00405d9f in main (argc=optimized out, argv=optimized out) at
./Port-linux/dibbler-client.cpp:153
-- System Information:
Debian Release: jessie/sid
APT prefers testing
APT policy: (990, 'testing'), (500, 'unstable'), (1, 'experimental')
Architecture: amd64 (x86_64)
Kernel: Linux 3.12-rc7-amd64 (SMP w/6 CPU cores)
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Versions of packages dibbler-client depends on:
ii debconf [debconf-2.0] 1.5.52
ii libc6 2.17-93
ii libgcc11:4.8.2-1
ii libstdc++6 4.8.2-1
ii ucf3.0027+nmu1
Versions of packages dibbler-client recommends:
ii dibbler-doc 0.8.2-1
ii resolvconf 1.74
dibbler-client suggests no packages.
-- Configuration Files:
/etc/init.d/dibbler-client changed:
PATH=/usr/local/sbin:/usr/local/bin:/sbin:/bin:/usr/sbin:/usr/bin
DAEMON=/usr/sbin/dibbler-client
NAME=dibbler-client
DESC=DHCPv6 client
DAEMON_OPTS=run
test -x $DAEMON || exit 0
if [ -f /etc/default/dibbler ] ; then
. /etc/default/dibbler
fi
set -e
case $1 in
start)
echo -n Starting $DESC:
$DAEMON start 21 /dev/null
echo $NAME.
;;
stop)
echo -n Stopping $DESC:
($DAEMON stop 21 /dev/null || true)
echo $NAME.
;;
status)
echo Status $DESC: $NAME
$DAEMON status
;;
#reload)
#
# If the daemon can reload its config files on the fly
# for example by sending it SIGHUP, do it here.
#
# If the daemon responds to changes in its config file
# directly anyway, make this a do-nothing entry.
#
# echo Reloading $DESC configuration files.
# start-stop-daemon --stop --signal 1 --quiet --pidfile \
# /var/run/$NAME.pid --exec $DAEMON
#;;
restart|force-reload)
#
# If the reload option is
Bug#732698: gemdropx: Fails to start (Failure loading sampleinfo)
Package: gemdropx Version: 0.9-6 Severity: important Dear Maintainer, When I attempt to start gemdropx, I only get the following error message: $ gemdropx Couldn't load /usr/share/games/gemdropx/sounds/2force.xm: Failure loading sampleinfo Just in case, I double-checked with the frozen-bubble package which also use libsdl-mixer1.2 for sound and that works fine. -- System Information: Debian Release: jessie/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: i386 (i686) Kernel: Linux 3.11-2-686-pae (SMP w/1 CPU core) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages gemdropx depends on: ii libc62.17-97 ii libsdl-mixer1.2 1.2.12-9 ii libsdl1.2debian 1.2.15-8 gemdropx recommends no packages. gemdropx suggests no packages. -- no debconf information -- mvh / best regards Hans Joachim http://desserud.org -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#732623: [Pkg-xfce-devel] Bug#732623: lightdm-gtk-greeter: Hibernate and Restart buttons disappear after first login/logout
-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 On Thu, Dec 19, 2013 at 03:09:01PM +0100, Vincent Lefevre wrote: Package: lightdm-gtk-greeter Version: 1.6.1-4 Severity: normal Initially the following buttons are present in the top-right menu: Suspend Hibernate Restart... Shutdown... But after the first login/logout, the Hibernate and Restart ones disappear. I don't see any reason for that. Another user got the same problem: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=728361#203 Yeah, actually Pascal replied (privately, to limit noise) later that: Hi again, I do not send this to the BTS because it becomes really irrelevant with regards to bug 728361 and this is just for information. After logout, the logind session is marked as closing, but is not cleaned because gpg-agent is still running. Killing the gpg-agent process allows cleaning completely the session. I will report to the gnupg-agent package maintainer. I have no idea if he actually reported that to gnupg maintainers. Regards, - -- Yves-Alexis Perez -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.15 (GNU/Linux) iQEcBAEBCgAGBQJStEAaAAoJEG3bU/KmdcCl0DwH/Re6wYlBlXpjT1qJErxIVvmC 42aF8kqQbsR8FNHJ25N0W9iCk1xn8EsA6Tyn99M3s3Qm4ko6tzr6AnVkIOPtpRQZ Kk6lCm95/XC5jniNRPunCYAZR86Eglcgn8dBDpyGGoMubrN3cHLGIb3vxTn45hI+ 1k92QNs+w2hlec3hwd5LRp4XeDac4lb0sg5SCqbFn/6flUNJusG2bf84noHurc6n UP7TTH5v0EPz7rqV4Fwu4zMqECCG2HKPozIqWLfy0v2dAxVsAueAsaFJcRrFiyhO iSLa6VpuQbYyWqikh7GHu1f192C+m0UkH+JjUzIaZzXQttkG4kFybOnlVt2JpnY= =wsqW -END PGP SIGNATURE- -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#732699: org-mode: 8.2.1-2 upgrade from 8.2.1-1 doesn't perform well
Package: org-mode Version: 8.2.1-2 Severity: important Hi. Since I upgraded to today's upstream version (8.2.1-2 upgraded after 8.2.1-1), emacs23 can't find org-mode from org-mode package and falls back at v. 6.33x :-( Having removed org-mode, $ sudo dpkg -i org-mode_8.2.1-1_all.deb [sudo] password for olivier: no talloc stackframe at ../source3/param/loadparm.c:4831, leaking memory dpkg : erreur : base de données d'état de dpkg est verrouillé par un autre processus olivier@inf-8660:~/org-mode$ sudo dpkg -i org-mode_8.2.1-1_all.deb Sélection du paquet org-mode précédemment désélectionné. (Lecture de la base de données... 402811 fichiers et répertoires déjà installés.) Dépaquetage de org-mode (à partir de org-mode_8.2.1-1_all.deb) ... Paramétrage de org-mode (8.2.1-1) ... given is experimental at /usr/lib/emacsen-common/emacs-package-install line 43. when is experimental at /usr/lib/emacsen-common/emacs-package-install line 45. when is experimental at /usr/lib/emacsen-common/emacs-package-install line 46. Install org-mode for emacs Install org-mode for emacs23 install/org-mode: Handling install for emacsen flavor emacs23, logged in /tmp/elc_4CIOcm.log install/org-mode: Deleting /tmp/elc_4CIOcm.log Install org-mode for emacs24 install/org-mode: Handling install for emacsen flavor emacs24, logged in /tmp/elc_3XTn3u.log install/org-mode: Deleting /tmp/elc_3XTn3u.log It works (/usr/share/emacs23/site-lisp/org-mode is populated). Upgrading : # aptitude Reading changelogs... Done (Reading database ... 403017 files and directories currently installed.) Preparing to replace org-mode 8.2.1-1 (using .../org-mode_8.2.1-2_all.deb) ... Remove org-mode for emacs Remove org-mode for emacs23 remove/org-mode: purging byte-compiled files for emacs23 Remove org-mode for emacs24 remove/org-mode: purging byte-compiled files for emacs24 Unpacking replacement org-mode ... Setting up org-mode (8.2.1-2) ... Some new locales have appeared on your system: $ ls -alrt /usr/share/emacs23/site-lisp/org-mode ls: cannot access /usr/share/emacs23/site-lisp/org-mode: No such file or directory Hope this helps. Best regards, -- System Information: Debian Release: jessie/sid APT prefers testing APT policy: (900, 'testing') Architecture: i386 (i686) Kernel: Linux 3.11-2-686-pae (SMP w/2 CPU cores) Locale: LANG=fr_FR.utf8, LC_CTYPE=fr_FR.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages org-mode depends on: ii emacs23 23.4+1-4.1 ii emacs24 24.3+1-2 Versions of packages org-mode recommends: ii texlive-generic-recommended 2013.20131112-1 ii texlive-latex-recommended2013.20131112-1 Versions of packages org-mode suggests: pn ditaa none ii easypg 0.0.16-2.1 -- no debconf information -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#519590: snort - Jessie - update to bug report 519590
Hi, update on bug report is attached regards Richard A Lough Subject: Re: snort: Snort now uses all available CPU cycles contiuously Followup-For: Bug #519590 Package: snort Version: 2.9.5.3-3 Dear Maintainer, *** Please consider answering these questions, where appropriate *** * What led up to the situation? My best guess is that my upgrade to this version caused the bug to appear. * What exactly did you do (or not do) that was effective (or ineffective)? I downgraded to the version of snort currently available from Debian|wheezy * What was the outcome of this action? On the current, installed version of snort, one cpu runs at near 100% continuously with nothing appearing in the log. If I change the interface from eth1 to eth0 (eth0 is unused) the cpu cycles fall to near zero. I have tried different linux kernels, none seemed to help. Reverting to the snort version available from wheezy restores normal operation, as far as I can tell. -- System Information: Debian Release: jessie/sid APT prefers testing APT policy: (500, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 3.11.8 (SMP w/4 CPU cores) Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages snort depends on: pn adduser none pn debconf | debconf-2.0none pn libc6none pn libdaq0 none pn libdumbnet1 none pn libpcap0.8 none pn libpcre3 none pn logrotatenone pn net-toolsnone pn rsyslog | system-log-daemon none ii snort-common 2.9.5.3-3 ii snort-common-libraries 2.9.5.3-3 ii snort-rules-default 2.9.5.3-3 pn zlib1g none Versions of packages snort recommends: pn iproute2 none Versions of packages snort suggests: pn snort-doc none -- debconf information: snort/invalid_interface: * snort/send_stats: true * snort/stats_treshold: 1 snort/disable_promiscuous: false * snort/startup: boot * snort/stats_rcpt: root snort/config_parameters: * snort/address_range: 192.168.1.0/24 snort/please_restart_manually: * snort/interface: eth1 snort/options:
Bug#732700: ITP: libgit-repository-plugin-log-perl -- Git::Repository plugin adding log items
Package: wnpp Owner: gregor herrmann gre...@debian.org Severity: wishlist X-Debbugs-CC: debian-de...@lists.debian.org,debian-p...@lists.debian.org * Package name: libgit-repository-plugin-log-perl Version : 1.310 Upstream Author : Philippe Bruhat (BooK) b...@cpan.org * URL : https://metacpan.org/release/Git-Repository-Plugin-Log * License : Artistic or GPL-1+ Programming Lang: Perl Description : Git::Repository plugin adding log items Git::Repository::Plugin::Log adds a log() method to Git::Repository, which will return Git::Repository::Log objects representing the commit information provided by `git log`. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#732699: org-mode: 8.2.1-2 upgrade from 8.2.1-1 doesn't perform well
On Fri, Dec 20, 2013 at 02:03:46PM +0100, Olivier Berger wrote: Upgrading : # aptitude Reading changelogs... Done (Reading database ... 403017 files and directories currently installed.) Preparing to replace org-mode 8.2.1-1 (using .../org-mode_8.2.1-2_all.deb) ... Remove org-mode for emacs Remove org-mode for emacs23 remove/org-mode: purging byte-compiled files for emacs23 Remove org-mode for emacs24 remove/org-mode: purging byte-compiled files for emacs24 Unpacking replacement org-mode ... Setting up org-mode (8.2.1-2) ... Some new locales have appeared on your system: $ ls -alrt /usr/share/emacs23/site-lisp/org-mode ls: cannot access /usr/share/emacs23/site-lisp/org-mode: No such file or directory FWIW, the scripts seem to differ between the 2 revisions : $ diff -irbw org-mode_8.2.1-1_all org-mode_8.2.1-2_all diff -irbw org-mode_8.2.1-1_all/control org-mode_8.2.1-2_all/control 2c2 Version: 8.2.1-1 --- Version: 8.2.1-2 6a7 Recommends: texlive-generic-recommended, texlive-latex-recommended diff -irbw org-mode_8.2.1-1_all/md5sums org-mode_8.2.1-2_all/md5sums 4c4 bac6ef89d17fd4727200409290d6bffe usr/share/doc/org-mode/changelog.Debian.gz --- 826cf4353c52ca7d0e0c929b510c8640 usr/share/doc/org-mode/changelog.Debian.gz diff -irbw org-mode_8.2.1-1_all/postinst org-mode_8.2.1-2_all/postinst 4c4 if [ $1 = configure ] [ -x /usr/lib/emacsen-common/emacs-package-install ] --- if [ $1 = configure ] [ -e /var/lib/emacsen-common/state/package/installed/emacsen-common ] 6c6 /usr/lib/emacsen-common/emacs-package-install org-mode --- /usr/lib/emacsen-common/emacs-package-install --postinst org-mode Only in org-mode_8.2.1-2_all: preinst diff -irbw org-mode_8.2.1-1_all/prerm org-mode_8.2.1-2_all/prerm 4,5c4,5 if [ -x /usr/lib/emacsen-common/emacs-package-remove ] ; then /usr/lib/emacsen-common/emacs-package-remove org-mode --- if [ -e /var/lib/emacsen-common/state/package/installed/emacsen-common ] ; then /usr/lib/emacsen-common/emacs-package-remove --prerm org-mode Binary files org-mode_8.2.1-1_all/usr/share/doc/org-mode/changelog.Debian.gz and org-mode_8.2.1-2_all/usr/share/doc/org-mode/changelog.Debian.gz differ This probably explains the failing postinst... Hope this helps. Best regards, -- Olivier BERGER http://www-public.telecom-sudparis.eu/~berger_o/ - OpenPGP-Id: 2048R/5819D7E8 Ingenieur Recherche - Dept INF Institut Mines-Telecom, Telecom SudParis, Evry (France) -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#732355: asterisk: Two Asterisk security issues
On Tue, Dec 17, 2013 at 06:17:09PM +0100, Moritz Muehlenhoff wrote:
On Tue, Dec 17, 2013 at 05:55:14PM +0200, Tzafrir Cohen wrote:
On Tue, Dec 17, 2013 at 07:33:53AM +0100, Moritz Muehlenhoff wrote:
Package: asterisk
Severity: grave
Tags: security
Hi,
please see
http://downloads.asterisk.org/pub/security/AST-2013-006.html and
http://downloads.asterisk.org/pub/security/AST-2013-007.html
Looking at them. At first glance: both of them also affect 1.6.2 from
old-stable. AST-2013-007 introduces a new configuration item and we have
to see what the sane default for it should be.
I think we should follow upstream and keep live_dangerously activated
We can add a note to the advisory what setting must be tweaked.
Attached are debdiffs for oldstable and stable uploads. I couldn't find
CVE entries.
I added an extra bug fix to help me patch the issue, for a bug that is
marginally a remote crash bug:
https://issues.asterisk.org/jira/browse/ASTERISK-20658
(Asterisk Realtime means getting some of Asterisk's configuration from a
database)
More on AST-2013-007:
(maybe shorten it a bit?)
Asterisk employs in its dialplan and varois other places a syntax for
varable expantion: ${VAR} expands the value of ${VAR}. Similarly there
are also some functions that use a similar syntax: ${RANDOM(5)} or
${CUT(20-30-40,-,2)}. Some are more potent, however such as SHELL
(run a shell command and return the output).
The variables were primarily meant for the Asterisk dialplan, but may be
accessed through several other interfaces. For instance, the AMI
(Asterisk Manager Interface) provides a GetVar command. This will also
expand functions.
With the fix for AST-2013-007, a new knob was added in order to allow
the system adminitrator to disable expantion of dangerous functions
(such as SHELL()) from any interface which is not the dialplan. In
Stable and Oldstable this knob is disabled by default. To enable it add
the following line to the section '[options]' in
/etc/asterisk/asterisk.conf (and restart asterisk)
live_dangerously = no
--
Tzafrir Cohen
icq#16849755 jabber:tzafrir.co...@xorcom.com
+972-50-7952406 mailto:tzafrir.co...@xorcom.com
http://www.xorcom.com
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#732695: AppArmor 2.8.0-{3,0ubuntu35} fails to build from source on current Debian sid
Hi, I have reported this FTBFS against the AppArmor Debian package there: http://bugs.debian.org/732695 Dear upstream, any hint? Cheers, -- intrigeri | GnuPG key @ https://gaffer.ptitcanardnoir.org/intrigeri/intrigeri.asc | OTR fingerprint @ https://gaffer.ptitcanardnoir.org/intrigeri/otr.asc -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#732570: libarch-perl should be removed
Hi, Adrian Bunk wrote: Package: libarch-perl Version: 0.5.2-1 Severity: normal GNU arch is dead since 2006, and I seriously doubt that anyone is still using libarch-perl. Popcon is steadily descreasing in the past 5 years, but there are a few votes, so there are definitely people using the package actively: http://qa.debian.org/popcon-graph.php?packages=libarch-perl The reasoning seems nevertheless comprehensible -- at least from the point of someone who never used tla. I though have to point out that there are no other open bug reports against libarch-perl and there were no bug reports in the past year either: http://qa.debian.org/data/bts/graphs/liba/libarch-perl.png So I think it should probably stay until tla itself is about to be removed as it does no harm if it stays. Regards, Axel -- ,''`. | Axel Beckert a...@debian.org, http://people.debian.org/~abe/ : :' : | Debian Developer, ftp.ch.debian.org Admin `. `' | 1024D: F067 EA27 26B9 C3FC 1486 202E C09E 1D89 9593 0EDE `-| 4096R: 2517 B724 C5F6 CA99 5329 6E61 2FF9 CD59 6126 16B5 -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#732570: libarch-perl should be removed
Hi again, Axel Beckert wrote: Adrian Bunk wrote: Package: libarch-perl [...] GNU arch is dead since 2006, and I seriously doubt that anyone is still using libarch-perl. Popcon is steadily descreasing in the past 5 years, but there are a few votes, so there are definitely people using the package actively: http://qa.debian.org/popcon-graph.php?packages=libarch-perl Despite I had the feeling that GNU Arch is dead, too, popcon of the tla shows a more or less constantly increasing graph of installations: http://qa.debian.org/popcon.php?package=tla So it looks rather undead on a first glance. But the votes seem constant over the years: http://qa.debian.org/popcon-graph.php?packages=tla Regards, Axel -- ,''`. | Axel Beckert a...@debian.org, http://people.debian.org/~abe/ : :' : | Debian Developer, ftp.ch.debian.org Admin `. `' | 1024D: F067 EA27 26B9 C3FC 1486 202E C09E 1D89 9593 0EDE `-| 4096R: 2517 B724 C5F6 CA99 5329 6E61 2FF9 CD59 6126 16B5 -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#732703: python3.4: cannot create a virtualenv
Package: python3.4 Version: 3.4~b1-2 Severity: normal Hi, It's not currently possible to create a virtualenv with the built-in venv module and python3.4. When I try the command pyvenv-3.4 directory, I've got the following output : Error: Command '['directory/bin/python3.4', '-Im', 'ensurepip', '--upgrade', '--default-pip']' returned non-zero exit status 1 When I try the command myself, I've got : directory/bin/python3.4: No module named ensurepip It's really a pip related issue as creating the venv without pip works : pyvenv-3.4 --without-pip directory Thanks -- System Information: Debian Release: jessie/sid APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.12-trunk-amd64 (SMP w/4 CPU cores) Locale: LANG=fr_FR.utf8, LC_CTYPE=fr_FR.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages python3.4 depends on: ii libpython3.4-stdlib 3.4~b1-2 ii mime-support 3.54 ii python3.4-minimal3.4~b1-2 python3.4 recommends no packages. Versions of packages python3.4 suggests: ii binutils 2.24-2 pn python3.4-doc none -- no debconf information -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#732704: evince: remembered window position is incorrect: window is slightly shifted
Package: evince Version: 3.10.0-1+b1 Severity: normal evince remembers the window position, but it appears that the window is sometimes slightly shifted. Apparently it always occurs when: 1. opening a file 2. moving or resizing the window [position 2] 3. quitting 4. reopening [position 4] i.e. position 2 and position 4 are different. This occurs at least with fvwm. The bug is very similar to http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=649132 which occurs for one of the GnuCash windows (its main window is not affected by this problem), at least with fvwm and twm. It seems that the shift more or less corresponds to the left window border (horizontal shift to the right) and to the top window border + height of the window title (vertical shift to the bottom). -- System Information: Debian Release: jessie/sid APT prefers unstable APT policy: (500, 'unstable'), (500, 'testing'), (500, 'stable'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.11-2-amd64 (SMP w/8 CPU cores) Locale: LANG=POSIX, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages evince depends on: ii evince-common 3.10.0-1 ii gnome-icon-theme-symbolic 3.10.1-1 ii libatk1.0-02.10.0-2 ii libc6 2.17-97 ii libcairo-gobject2 1.12.16-2 ii libcairo2 1.12.16-2 ii libevdocument3-4 3.10.0-1+b1 ii libevview3-3 3.10.0-1+b1 ii libgail-3-03.8.6-1 ii libgdk-pixbuf2.0-0 2.28.2-1+b1 ii libglib2.0-0 2.36.4-1 ii libgtk-3-0 3.8.6-1 ii libice62:1.0.8-2 ii libnautilus-extension1a3.8.2-2 ii libpango-1.0-0 1.36.0-1+b1 ii libpangocairo-1.0-01.36.0-1+b1 ii libsecret-1-0 0.15-2 ii libsm6 2:1.2.1-2 ii libx11-6 2:1.6.2-1 ii libxml22.9.1+dfsg1-3 ii shared-mime-info 1.0-1+b1 ii zlib1g 1:1.2.8.dfsg-1 Versions of packages evince recommends: ii dbus-x11 1.6.18-2 ii gvfs 1.16.3-1+b2 Versions of packages evince suggests: ii nautilus 3.8.2-2 ii poppler-data 0.4.6-4 pn unrar none -- no debconf information -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#732706: ITP: yrmcds -- memcached compatible KVS with master/slave replication
Package: wnpp Severity: wishlist Owner: Kouhei Maeda mkou...@palmtb.net * Package name: yrmcds Version : 1.0.0 Upstream Author : Cybozu * URL : http://cybozu.github.io/yrmcds/ * License : BSD Programming Lang: C++ Description : memcached compatible KVS with master/slave replication yrmcds is a memory object caching system with master/slave replication and server-side locking. Since its protocol is perfectly compatible with that of memcached, yrmcds can be used as a drop-in replacement for memcached. . A companion client library libyrmcds and a PHP extension are also available. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#732705: gnupg: Patch for CVE-2013-4576 not being applied in 1.4.15-2
Package: gnupg Severity: normal Tags: security gnupg 1.4.15-2 claims to fix CVE-2013-4576, but the patch isn't actually being applied during build. It is in the wrong directory, and isn't listed in the series file. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#732659: [Pkg-octave-devel] Bug#732659: octave: fails to load uint8 variables from text files
Control: tags 732659 upstream confirmed Control: forwarded 732659 https://savannah.gnu.org/bugs/index.php?40980 * Kacper Gutowski mwgam...@gmail.com [2013-12-20 04:28]: Package: octave Version: 3.6.4-4+b1 Severity: normal When a variable of class uint8 is saved in the default text format, it's actually written out in binary (one byte per element) instead of plain text like every other type. I don't know whether this is intended or not, but file containing such variable can be loaded only if said variable had no elements of values 9, 10, 11, 12, 13, or 32. These correspond to white characters in ASCII and apparently load gets confused by them. Minimal example to reproduce the problem: hyper% octave -q --no-init-file octave:1 a = uint8(10); octave:2 save 'a' a octave:3 load 'a' error: load: failed to load scalar constant error: load: trouble reading ascii file 'a' error: load: reading file a octave:3 Thank you for this bug report. This is a real bug and is also present in version 3.8.0-rc1. This is an upstream problem and I forwarded your bug report to the bug tracker of the Octave project at Savannah.gnu.org. Best, Rafael -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#732707: dibbler: please provide debug symbol packages
Package: dibbler
Version: 1.0.0~rc1-1
Severity: wishlist
Tags: ipv6 patch
Please apply the attached patches to generate debug symbol packages for
dibbler_client, dibbler_server, dibbler_relay
-- System Information:
Debian Release: jessie/sid
APT prefers testing
APT policy: (990, 'testing'), (500, 'unstable'), (1, 'experimental')
Architecture: amd64 (x86_64)
Kernel: Linux 3.12-rc7-amd64 (SMP w/6 CPU cores)
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
diff -Nru dibbler-1.0.0~rc1/debian/control dibbler-1.0.0~rc1/debian/control
--- dibbler-1.0.0~rc1/debian/control 2013-12-10 11:28:07.0 +0100
+++ dibbler-1.0.0~rc1/debian/control 2013-12-20 12:27:41.0 +0100
@@ -18,6 +18,21 @@
supported. This package allows IPv6 hosts to be automatically
configured on the network.
+Package: dibbler-server-dbg
+Architecture: any
+Section: debug
+Priority: extra
+Depends: dibbler-server (=${binary:Version}), ${misc:Depends}
+Recommends: dibbler-doc
+Homepage: http://klub.com.pl/dhcpv6/
+Description: portable DHCPv6 server
+ The Dibbler server supports both stateful (i.e. IPv6 address
+ granting) as well as stateless (i.e. options granting)
+ auto-configuration modes of the DHCPv6 protocol. Relays are also
+ supported. This package allows IPv6 hosts to be automatically
+ configured on the network.
+ This package contains the debugging symbols for dibbler-server.
+
Package: dibbler-client
Architecture: any
Depends: ${shlibs:Depends}, ${misc:Depends}, ucf
@@ -31,6 +46,22 @@
option renewal. Installing Dibbler allows obtaining IPv6 addresses and
options from a DHCPv6 server.
+Package: dibbler-client-dbg
+Architecture: any
+Section: debug
+Priority: extra
+Depends: dibbler-client (=${binary:Version}), ${misc:Depends}
+Recommends: dibbler-doc, resolvconf
+Homepage: http://klub.com.pl/dhcpv6/
+Description: portable DHCPv6 client
+ The Dibbler client supports both stateful (i.e. IPv6 address
+ granting) as well as stateless (i.e. option granting)
+ auto-configuration modes of the DHCPv6 protocol. Besides basic
+ capabilities, it supports various DHCPv6 extensions, for instance
+ option renewal. Installing Dibbler allows obtaining IPv6 addresses and
+ options from a DHCPv6 server.
+ This package contains the debugging symbols for dibbler-client.
+
Package: dibbler-relay
Architecture: any
Depends: ${shlibs:Depends}, ${misc:Depends}
@@ -42,6 +73,20 @@
one server. Installing Dibbler relay allows serving multiple, not
physically connected, links with one DHCPv6 server.
+Package: dibbler-relay-dbg
+Architecture: any
+Section: debug
+Priority: extra
+Depends: dibbler-relay (=${binary:Version}), ${misc:Depends}
+Recommends: dibbler-doc
+Homepage: http://klub.com.pl/dhcpv6/
+Description: portable DHCPv6 relay
+ Relays are used as proxies between servers and clients. Their main
+ advantage is the ability to support multiple remote links using only
+ one server. Installing Dibbler relay allows serving multiple, not
+ physically connected, links with one DHCPv6 server.
+ This package contains the debugging symbols for dibbler-relay.
+
Package: dibbler-doc
Architecture: all
Section: doc
diff -Nru dibbler-1.0.0~rc1/debian/rules dibbler-1.0.0~rc1/debian/rules
--- dibbler-1.0.0~rc1/debian/rules 2013-12-10 10:03:33.0 +0100
+++ dibbler-1.0.0~rc1/debian/rules 2013-12-20 12:52:11.0 +0100
@@ -6,6 +6,11 @@
# This has to be exported to make some magic below work.
export DH_OPTIONS
+.PHONY: override_dh_strip
+override_dh_strip:
+ dh_strip -pdibbler-server --dbg-package=dibbler-server-dbg
+ dh_strip -pdibbler-client --dbg-package=dibbler-client-dbg
+ dh_strip -pdibbler-relay --dbg-package=dibbler-relay-dbg
%:
dh $@ --with autotools_dev
Bug#732623: about gpg-agent issue
Hi Yves-Alexis, Sorry not to inform you, I finally did not report to gnupg because it seems to be known upstream (xfce4 side), see: https://bugzilla.xfce.org/show_bug.cgi?id=8792 Consequently it is not worth an entry into the BTS. Disabling gpg-agent from xfce4-session solves that problem. One needs to use hidden xfce4-session options (http://docs.xfce.org/xfce/xfce4-session/advanced). I have the hibernate/suspend buttons in greeter working currently but I am not sure this gpg-agent issue it is related to the bug reported here. Regards Pascal Dormeau -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#728304: for schroot backend allow to run tests as user while installation steps as root
Martin Pitt mar...@piware.de wrote: Hello Yaroslav, Yaroslav Halchenko [2013-10-30 8:48 -0400]: Adding user's login to root-users configuration of schroot allows autopkgtest to invoke apt-get with necessary privileges, but then tests also run under root user, instead of the original user Please note that you can have this behaviour with the current autopkgtest if you explicitly specify the --user $USER adt-run option. Then it'll use root to install dependencies and $USER to run tests. There already was a test to make sure that works, I just committed some extended tests that also make sure that dependency installation still works with --user, and that needs-root is respected properly. Great, thank you for detailed response Indeed the test gets run as root if you call adt-run as normal user with the schroot runner. It should default to running them as the calling user instead. I'll devote this bug report to this. Thanks again -- Sent from a phone which beats iPhone. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#732623: [Pkg-xfce-devel] Bug#732623: lightdm-gtk-greeter: Hibernate and Restart buttons disappear after first login/logout
On 2013-12-20 14:03:28 +0100, Yves-Alexis Perez wrote: On Thu, Dec 19, 2013 at 03:09:01PM +0100, Vincent Lefevre wrote: [...] But after the first login/logout, the Hibernate and Restart ones disappear. I don't see any reason for that. Another user got the same problem: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=728361#203 Yeah, actually Pascal replied (privately, to limit noise) later that: Hi again, I do not send this to the BTS because it becomes really irrelevant with regards to bug 728361 and this is just for information. After logout, the logind session is marked as closing, but is not cleaned because gpg-agent is still running. Killing the gpg-agent process allows cleaning completely the session. I will report to the gnupg-agent package maintainer. I have no idea if he actually reported that to gnupg maintainers. It seems unrelated: when I log out, the gpg-agent process is killed as expected. Even if I kill this process manually before logging out, I still get the same problem. -- Vincent Lefèvre vinc...@vinc17.net - Web: http://www.vinc17.net/ 100% accessible validated (X)HTML - Blog: http://www.vinc17.net/blog/ Work: CR INRIA - computer arithmetic / AriC project (LIP, ENS-Lyon) -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#732697: /usr/sbin/dibbler-client: dibbler_client: segfaults in TClntCfgMgr::validateConfig
On 20.12.2013 13:58, Peter Poeschl wrote:
Package: dibbler-client
Version: 1.0.0~rc1-1
Severity: serious
File: /usr/sbin/dibbler-client
Tags: ipv6
Justification: Policy 3.3
Each time I start dibbler-client, it terminates with a segmentation fault.
Compiling with debug symbols and starting with GDB I get:
# gdb --args dibbler-client run
GNU gdb (GDB) 7.6.1 (Debian 7.6.1-1)
...
Reading symbols from /usr/sbin/dibbler-client...Reading symbols from
/usr/lib/debug/.build-id/00/e3a4d011a15fdf6c9c425ab9d7cfc1d8e1a168.debug...done.
done.
(gdb) run
Starting program: /usr/sbin/dibbler-client run
[tcsetpgrp failed in terminal_inferior: Unpassender IOCTL (I/O-Control) für
das Gerät]
warning: no loadable sections found in added symbol-file system-supplied DSO
at 0x77ffa000
[tcsetpgrp failed in terminal_inferior: Unpassender IOCTL (I/O-Control) für
das Gerät]
warning: Could not load shared library symbols for linux-vdso.so.1.
Do you need set solib-search-path or set sysroot?
[tcsetpgrp failed in terminal_inferior: Unpassender IOCTL (I/O-Control) für
das Gerät]
[Thread debugging using libthread_db enabled]
Using host libthread_db library /lib/x86_64-linux-gnu/libthread_db.so.1.
[tcsetpgrp failed in terminal_inferior: Unpassender IOCTL (I/O-Control) für
das Gerät]
| Dibbler - a portable DHCPv6, version 1.0.0RC1 (CLIENT, Linux port)
| Authors : Tomasz Mrugalskithomson(at)klub.com.pl,Marek
Senderskimsend(at)o2.pl
| Licence : GNU GPL v2 only. Developed at Gdansk University of Technology.
| Homepage: http://klub.com.pl/dhcpv6/
2013.12.20 12:54:56 Client Warning Pid file found (pid=4676, file
/var/lib/dibbler/client.pid), but process 4676 does not exist.
2013.12.20 12:54:56 Client NoticeMy pid (32038) is stored in
/var/lib/dibbler/client.pid
2013.12.20 12:54:56 Client NoticeDetected iface eth0/2,
MAC=90:2b:34:a0:08:48.
2013.12.20 12:54:56 Client NoticeDetected iface lo/1,
MAC=00:00:00:00:00:00.
2013.12.20 12:54:56 Client NoticeParsing /etc/dibbler/client.conf config
file...
2013.12.20 12:54:56 Client Debug Parsing /etc/dibbler/client.conf done,
result=0
2013.12.20 12:54:56 Client Debug 1 interface(s) specified in
/etc/dibbler/client.conf
2013.12.20 12:54:56 Client Info Interface eth0/2 configuration has been
loaded.
Program received signal SIGSEGV, Segmentation fault.
TClntCfgMgr::validateConfig (this=this@entry=0x6f4da0) at ClntCfgMgr.cpp:530
530 if (digests[0] != DIGEST_HMAC_MD5) {
(gdb) bt
#0 TClntCfgMgr::validateConfig (this=this@entry=0x6f4da0) at
ClntCfgMgr.cpp:530
#1 0x00447428 in TClntCfgMgr::parseConfigFile
(this=this@entry=0x6f4da0, cfgFile=...) at ClntCfgMgr.cpp:135
#2 0x00447695 in TClntCfgMgr::TClntCfgMgr (this=0x6f4da0,
cfgFile=...) at ClntCfgMgr.cpp:62
#3 0x004478e1 in TClntCfgMgr::instanceCreate (cfgFile=...) at
ClntCfgMgr.cpp:47
#4 0x00408d12 in TDHCPClient::TDHCPClient (this=0x7fffe460,
config=...) at ./Misc/DHCPClient.cpp:41
#5 0x004075d3 in run () at ./Port-linux/dibbler-client.cpp:87
#6 0x00405d9f in main (argc=optimized out, argv=optimized out)
at ./Port-linux/dibbler-client.cpp:153
Thanks for this bug report. I'm an original Dibbler author, and used to
be also Debian package maintainer (I'm not one anymore). There is a fix
on master that is likely to address your segfault. Can you please
confirm if the latest master from
https://github.com/tomaszmrugalski/dibbler solves the problem?
If it does, I'll need to release 1.0.0RC2 and then ask Debian maintainer
to package it. Does that sound like a plan?
Tomek Mrugalski
Dibbler author
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#732623: [Pkg-xfce-devel] Bug#732623: lightdm-gtk-greeter: Hibernate and Restart buttons disappear after first login/logout
-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 On Fri, Dec 20, 2013 at 03:11:00PM +0100, Vincent Lefevre wrote: It seems unrelated: when I log out, the gpg-agent process is killed as expected. Even if I kill this process manually before logging out, I still get the same problem. Then I have no idea, maybe check what logind session are listed at that point? Regards, - -- Yves-Alexis -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.15 (GNU/Linux) iQEcBAEBCgAGBQJStFIDAAoJEG3bU/KmdcClhhIH/RPpDf0WE4OsZZm9dN80+frQ 5RAPftN3UckUVpRDn/vA3L6Ru8eFocCCqdf93NyKkmNvvIfTasxwPwRpufXYDjL6 9fDNSPeojbIwGj8Gvo23vjEK7MyOyDZiWuW1R8duvZx+EKwpJVOI3pJCGihqvFay bf1oMrK4VmzX+4w1+ahdwsHBjXzy4880s8uGtzZC0fJL/7YWdPloxvz9cxZYyXPW 5WChS/hcFxEWAFm/gO+U3R7YWwiJ3Tz4L+XntVYQVfzSSED3Hdk7VCg9/dLYIwM5 RzW+KeOburcVpp4BOO11sF6tFRf7SEh0UyiKstRtxf1czKAZ0akgVaQ6EMjUHqE= =VuJJ -END PGP SIGNATURE- -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#732708: jenkins: CVE-2013-5573
Package: jenkins Severity: important Tags: security Please see http://seclists.org/fulldisclosure/2013/Dec/159 -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#732623: about gpg-agent issue
On Fri, Dec 20, 2013 at 02:58:27PM +0100, pdorm...@free.fr wrote: Hi Yves-Alexis, Sorry not to inform you, I finally did not report to gnupg because it seems to be known upstream (xfce4 side), see: https://bugzilla.xfce.org/show_bug.cgi?id=8792 Consequently it is not worth an entry into the BTS. Disabling gpg-agent from xfce4-session solves that problem. One needs to use hidden xfce4-session options (http://docs.xfce.org/xfce/xfce4-session/advanced). Ho, I thought it was the gpg-agent launched by /etc/X11/Xsession.d and not the one launched by xfce4-session. I have the hibernate/suspend buttons in greeter working currently but I am not sure this gpg-agent issue it is related to the bug reported here. Ok. -- Yves-Alexis -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#732709: TIFF5 transition
Package: insighttoolkit
Severity: serious
Version: 3.20.1+git20120521-3
ITK fails to compile with recent TIFF:
/«BUILDDIR»/insighttoolkit-3.20.1+git20120521/Code/IO/itkTIFFImageIO.cxx:1869:78:
error: cannot convert 'const TIFFField* {aka const _TIFFField*}' to
'const TIFFFieldInfo*' in initialization
const TIFFFieldInfo *fld = TIFFFieldWithTag( m_InternalImage-m_Image, tag );
See:
http://buildd.debian-ports.org/status/fetch.php?pkg=insighttoolkitarch=ppc64ver=3.20.1%2Bgit20120521-3%2Bb1stamp=1387344656
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#732709: Acknowledgement (TIFF5 transition)
Control: tag -1 fixed-upstream patch http://itk.org/gitweb?p=ITK.git;a=commitdiff_plain;h=563abcab25aeff7099de0712a8735c58d14602fb -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#725143: Bug#728521: ogre-1.9 / gcc-4.8
Hi, 2013/11/30 Rebecca N. Palmer r.pal...@bham.ac.uk: Control: severity 728521 normal Control: merge 725143 728521 I think that your attempt to merge the bugs failed. It's OK to keep them separate because they are slightly different, so it doesn't matter. It's now official that gcc 4.8 will be required in jessie [1], so this is now not an RC (and could even be closed altogether, though that isn't my decision to make; the current non-working attempts to select gcc-4.8 are ugly, but harmless wherever 4.8+ is the default). s390x are currently switching to 4.8 [2], so another try once they have should fix the out of date on s390x testing blocker. [1] http://lists.debian.org/debian-devel-announce/2013/11/msg7.html [2] http://lists.debian.org/debian-devel/2013/11/msg00449.html It's been built successfully in s390x and most other arches (at least the ones where it was present before with src:ogre-1.9) so I think that it will migrate to testing by the end of the year. I think that the best solution is to let things be and let the arches catch up with GCC 4.8, I've already been similar reports affecting packages much more important than OGRE so I think that they will forced to move on quickly. I am not keen on depending on two different versions of a compiler for general as well as specific reasons for this case: - the fact that 4.8 it's not the default in some arches it indicates already some kind of problem with that version, so if it remains unfixed and cannot become the default, maybe the package hits precisely the problems that make GCC not be the default (OGRE's source is quite big in terms of LoC, memory needed for compilation, storage, etc; and takes many hours to compile in most of the arches) - 4.6 is comparatively quite old, especially for C++ (OGRE's implementation language) and the latest revisions of the language. Any minor revision .bugfix could introduce syntax that old compilers choke with. - The solution of gcc-default (= 4.8) | gcc-4.8 would have been nice if not because of the problem with buildds (I thought that it would already have been fixed, it's an old problem). But the contrary is not so nice because when GCC 4.9 becomes the default (it can happen before summer, unless Release Managers want 4.8 for jessie) the package will need an update just because of its dependencies; while there's sometimes more than a year [1] between updates to OGRE package and for good reasons (need to go through NEW queue due to changes in names of binary packages; tax on the infrastructure; etc). [1] [2013-09-04] Accepted 1.8.0+dfsg1-5 in unstable (low) (Manuel A. Fernandez Montecelo) [2013-08-01] Accepted 1.8.0+dfsg1-4 in unstable (low) (Manuel A. Fernandez Montecelo) So as I said, I think that it's better let things be and the problem will solve itself plenty of time ahead of the freeze. Reverse-depends can ask to remove old versions of packages from testing in problematic arches to get their new version to migrate. Virtually nobody will be using OGRE or their packages in those arches anyway. Cheers. -- Manuel A. Fernandez Montecelo manuel.montez...@gmail.com -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#732123: usage of stanza not compatible with ordinary English
Hi Ian, = Definition = I agree that the word 'stanza' is somewhat of an uncommon term in the realm of computing, however there is precedent in the domain of XML [1]. The usage in that spec admittedly implies a sense of plurality and yet an XML element could of course span multiple lines but actually represent an empty value: message message/ According to wiktionary and Websters [2], stanza can also mean a division or simply a poetic unit without prescribing a minimum length (as the OED does). I suspect (?) Scott might have been thinking along those lines when he adopted the term. = Multi-line singular stanzas in Upstart = Note that even those singular Upstart stanzas such as 'author' and 'console' can span multiple lines using the usual back-slashing technique if so required: console \ \ \ log author \ \ james That facility again lends weight to the use of the term for any type of Upstart stanza; each stanza is a logical unit the encapsulates certain meta-data or requirements for the job environment. = Occurrences of the term in the code = Interestingly, aside from the man pages, there are only 2 occurrences of the word stanza in the code that users will ever see: 1) init --help|grep -iB1 stanza (reformatted below) --default-console=VALUE default value for console stanza Clearly, this would be trivial to change if required. 2) The error Unknown stanza resulting from failing to parse an invalid job configuration file. This error comes not from Upstart but from the dependent libnih which actually performs the safe parsing of all the Upstart job configuration files. I'm not convinced we should change libnih. In fact, it is Scott we'd really need to convince since the stanza code in libnih has been around since ~2007 fwics. = Proposed Plan = In summary, would you be happy if we defined 'stanza' more clearly in the manual pages, making reference to terms such as 'command' and 'keyword' and giving examples of single-line and multi-line stanzas so there is no misunderstanding as to what is meant by the term? Kind regards, James. [1] - http://xmpp.org/rfcs/rfc3920.html#stanzas [2] - http://en.wiktionary.org/wiki/stanza -- James Hunt #upstart on freenode http://upstart.ubuntu.com/cookbook https://lists.ubuntu.com/mailman/listinfo/upstart-devel -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#732710: openssl: rdrand should be disabled by default
Package: openssl
Version: 1.0.1e-4
Severity: normal
Tags: patch
User: ubuntu-de...@lists.ubuntu.com
Usertags: origin-ubuntu trusty ubuntu-patch
*** /tmp/tmpVmJEAg/bug_body
OpenSSL uses rdrand exclusively if it is available.
http://seclists.org/fulldisclosure/2013/Dec/99
http://wiki.openssl.org/index.php/Library_Initialization#ENGINEs_and_RDRAND
Upstream has changed this behaviour.
In Ubuntu, the attached patch was applied to achieve the following:
* debian/patches/no_default_rdrand.patch: Don't use rdrand engine as
default unless explicitly requested.
Thanks for considering the patch.
-- System Information:
Debian Release: wheezy/sid
APT prefers saucy-updates
APT policy: (500, 'saucy-updates'), (500, 'saucy-security'), (500,
'saucy-proposed'), (500, 'saucy'), (100, 'saucy-backports')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 3.11.0-15-generic (SMP w/4 CPU cores)
Locale: LANG=en_CA.UTF-8, LC_CTYPE=en_CA.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
diff -Nru openssl-1.0.1e/debian/changelog openssl-1.0.1e/debian/changelog
diff -Nru openssl-1.0.1e/debian/patches/no_default_rdrand.patch openssl-1.0.1e/debian/patches/no_default_rdrand.patch
--- openssl-1.0.1e/debian/patches/no_default_rdrand.patch 1969-12-31 19:00:00.0 -0500
+++ openssl-1.0.1e/debian/patches/no_default_rdrand.patch 2013-12-19 15:39:17.0 -0500
@@ -0,0 +1,25 @@
+From 8f68678989a198ead3ab59a698302ecb0f1c8fb1 Mon Sep 17 00:00:00 2001
+From: Dr. Stephen Henson st...@openssl.org
+Date: Wed, 11 Dec 2013 14:45:12 +
+Subject: [PATCH] Don't use rdrand engine as default unless explicitly
+ requested.
+
+---
+ crypto/engine/eng_rdrand.c |1 +
+ 1 file changed, 1 insertion(+)
+
+diff --git a/crypto/engine/eng_rdrand.c b/crypto/engine/eng_rdrand.c
+index a9ba5ae..4e9e91d 100644
+--- a/crypto/engine/eng_rdrand.c
b/crypto/engine/eng_rdrand.c
+@@ -104,6 +104,7 @@ static int bind_helper(ENGINE *e)
+ {
+ if (!ENGINE_set_id(e, engine_e_rdrand_id) ||
+ !ENGINE_set_name(e, engine_e_rdrand_name) ||
++!ENGINE_set_flags(e, ENGINE_FLAGS_NO_REGISTER_ALL) ||
+ !ENGINE_set_init_function(e, rdrand_init) ||
+ !ENGINE_set_RAND(e, rdrand_meth) )
+ return 0;
+--
+1.7.9.5
+
diff -Nru openssl-1.0.1e/debian/patches/series openssl-1.0.1e/debian/patches/series
--- openssl-1.0.1e/debian/patches/series 2013-12-04 12:34:19.0 -0500
+++ openssl-1.0.1e/debian/patches/series 2013-12-19 15:39:17.0 -0500
@@ -43,3 +43,4 @@
arm64-support
openssl-1.0.1e-env-zlib.patch -p1
ppc64-support
+no_default_rdrand.patch
Bug#732711: libxcb-cursor-dev: Missing dependency on libxcb-image0-dev
Package: libxcb-cursor-dev Version: 0.1.1-1 Severity: normal Tags: patch Hello, I get a similar error as in #723750 when executing the following command in a clean chroot environment: $ pkg-config --libs --static xcb-cursor Package xcb-image was not found in the pkg-config search path. Perhaps you should add the directory containing `xcb-image.pc' to the PKG_CONFIG_PATH environment variable Package 'xcb-image', required by 'XCB cursor library', not found AFAIU, all the -dev packages from Requires.private *and* Requires .pc file should be in libxcb-cursor-dev Depends (eg not only renderutil): + libxcb-image0-dev + libxcb-render-util0-dev + libxcb-render0-dev + libxcb1-dev Cheers, Arnaud -- System Information: Debian Release: jessie/sid APT prefers unstable APT policy: (500, 'unstable'), (500, 'testing'), (500, 'stable'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.12-trunk-amd64 (SMP w/4 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages libxcb-cursor-dev depends on: ii libxcb-cursor0 0.1.1-1 ii libxcb-render-util0-dev 0.3.8-1.1 libxcb-cursor-dev recommends no packages. libxcb-cursor-dev suggests no packages. -- no debconf information -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#732697: /usr/sbin/dibbler-client: dibbler_client: segfaults in TClntCfgMgr::validateConfig
Hi Tomasz, Thanks for this bug report. I'm an original Dibbler author, and used to be also Debian package maintainer (I'm not one anymore). There is a fix on master that is likely to address your segfault. Yeah, found it. I've amended the Debian bugreport with a ref to your bugzilla. Can you please confirm if the latest master from https://github.com/tomaszmrugalski/dibbler solves the problem? Confirmed. If it does, I'll need to release 1.0.0RC2 and then ask Debian maintainer to package it. Does that sound like a plan? Looking good, thanks for the fast response. Regards, Peter -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#725143: Bug#728521: ogre-1.9 / gcc-4.8
2013/12/20 Manuel A. Fernandez Montecelo manuel.montez...@gmail.com: - The solution of gcc-default (= 4.8) | gcc-4.8 would have been nice if not because of the problem with buildds (I thought that it would already have been fixed, it's an old problem). But the contrary is not so nice because when GCC 4.9 becomes the default (it can happen before summer, unless Release Managers want 4.8 for jessie) the package will need an update just because of its dependencies; while there's sometimes more than a year [1] between updates to OGRE package and for good reasons (need to go through NEW queue due to changes in names of binary packages; tax on the infrastructure; etc). [1] [2013-09-04] Accepted 1.8.0+dfsg1-5 in unstable (low) (Manuel A. Fernandez Montecelo) [2013-08-01] Accepted 1.8.0+dfsg1-4 in unstable (low) (Manuel A. Fernandez Montecelo) Mmmm, I meant this one (not a full year, but you get the idea): [2013-08-01] Accepted 1.8.0+dfsg1-4 in unstable (low) (Manuel A. Fernandez Montecelo) [2012-11-13] Accepted 1.8.0+dfsg1-3 in unstable (low) (Manuel A. Fernandez Montecelo) So, any opinion about my previous reasoning, for or against? Cheers. -- Manuel A. Fernandez Montecelo manuel.montez...@gmail.com -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#732127: Does setuid also set the group(s) ? It should.
Hi Ian, I've updated the man pages on this point (fixed in r1580): http://bazaar.launchpad.net/~upstart-devel/upstart/trunk/revision/1580 Kind regards, James. -- James Hunt #upstart on freenode http://upstart.ubuntu.com/cookbook https://lists.ubuntu.com/mailman/listinfo/upstart-devel -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#732355: asterisk: Two Asterisk security issues
On Fri, Dec 20, 2013 at 03:14:00PM +0200, Tzafrir Cohen wrote: On Tue, Dec 17, 2013 at 06:17:09PM +0100, Moritz Muehlenhoff wrote: On Tue, Dec 17, 2013 at 05:55:14PM +0200, Tzafrir Cohen wrote: On Tue, Dec 17, 2013 at 07:33:53AM +0100, Moritz Muehlenhoff wrote: Package: asterisk Severity: grave Tags: security Hi, please see http://downloads.asterisk.org/pub/security/AST-2013-006.html and http://downloads.asterisk.org/pub/security/AST-2013-007.html Looking at them. At first glance: both of them also affect 1.6.2 from old-stable. AST-2013-007 introduces a new configuration item and we have to see what the sane default for it should be. I think we should follow upstream and keep live_dangerously activated We can add a note to the advisory what setting must be tweaked. Attached are debdiffs for oldstable and stable uploads. I couldn't find CVE entries. Please adjust the distribution lines to oldstable-security and stable-security and upload to security-master. Have you been able to test these on a live system? Cheers, Moritz -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#732709: Acknowledgement (TIFF5 transition)
Control: tag -1 - patch Even taking the minimal patch does not work: $ patch -F 40 -p5 --dry-run ../../gitweb\?p=ITK.git\;a=commitdiff_plain\;h=563abcab25aeff7099de0712a8735c58d14602fb patching file itkTIFFImageIO.cxx Hunk #1 FAILED at 44. Hunk #2 FAILED at 60. Hunk #3 succeeded at 291 with fuzz 3 (offset -12 lines). Hunk #4 succeeded at 445 with fuzz 3 (offset -11 lines). Hunk #5 FAILED at 1625. Hunk #6 succeeded at 1697 with fuzz 1 (offset -16 lines). Hunk #7 FAILED at 1897. Hunk #8 FAILED at 1915. 5 out of 8 hunks FAILED -- saving rejects to file itkTIFFImageIO.cxx.rej -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#714984: It works :)
Mathieu Malaterre ma...@debian.org wrote: Control: tag -1 - pending On Fri, Dec 20, 2013 at 10:47 AM, Giorgio Quattrone g.quattr...@cineca.it wrote: Hi Mathieu, I installed the patch: it worked like a charm. For me the bug is SOLVED Jay, Could you please do a stable upload ? thanks much Yes, I'll prepare a stable upload. Thanks for taking this one all the way across the finish line. -- Jay Berkenbilt q...@debian.org -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#714984: permission to do a vips upload to proposed-updates (bug 714984)
Details are in bug 714984. There's a small bug in vips in wheezy that prevents jpeg compression from working right in some cases. This severely impacts the use of vips for certain types of work. The problem seems to be related to the jpeg transition, but upstream provided a small patch. Mathieu Malaterre ma...@debian.org did a great job of reporting the problem upstream, testing it, and having another user test it, so I think this is ready for a stable upload. If you are okay with it, I will prepare an upload, build against wheezy, and upload to proposed-updates. Any objections? Note that the current vips in jessie and sid are not affected by this problem, nor is the version in squeeze. This problem only affects the version in wheezy. -- Jay Berkenbilt q...@debian.org -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#732678: git-buildpackage -A calls lintian with the wrong .changes file
On Fri, Dec 20, 2013 at 10:01:22AM +0100, Raphaël Hertzog wrote: Package: git-buildpackage Version: 0.6.7 Severity: normal When you build with git-buildpackage -A, dpkg-buildpackage will generate an *_all.changes file but git-buildpackages will still try to call lintian with an *_arch.changes file. This results in this: Hmm...while we don't support -A yet I still wonder why this happens since it should fall back to _source.changes instead. I know it's still incorrect but it certainly shouldn't check the arch specific file. Can you attach (or mail me directly) the full build output with --git-verbose please. Do you have any better ideas than checking the dpkg-buildpackage command line for -A to detect wheter we need arch or all? I'd be so cool if dpkg-buildpackage would have a nice way to communicate back such information to build tools. Cheers, -- Guido Now running lintian... warning: linux-kali_3.12.3-1~kali2_amd64.changes cannot be processed. warning: It is not a valid lab query and it is not an existing file. Finished running lintian. -- System Information: Debian Release: jessie/sid APT prefers unstable APT policy: (500, 'unstable'), (500, 'testing'), (500, 'stable'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.11-2-amd64 (SMP w/4 CPU cores) Locale: LANG=fr_FR.utf8, LC_CTYPE=fr_FR.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages git-buildpackage depends on: ii devscripts2.13.8 ii git 1:1.8.5.1-1 ii man-db2.6.5-2 ii python2.7.5-5 ii python-dateutil 1.5+dfsg-0.1 ii python-pkg-resources 1.4.2-1 Versions of packages git-buildpackage recommends: ii cowbuilder0.73 ii pristine-tar 1.30 Versions of packages git-buildpackage suggests: ii python-notify 0.1.1-3 ii unzip 6.0-10 -- no debconf information -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#732688: git-buildpackage: git-import-orig fails if source tarball contains .git configuration file
On Fri, Dec 20, 2013 at 12:53:34PM +0100, Benjamin Drung wrote: Package: git-buildpackage Version: 0.6.7 Severity: normal Steps to reproduce == pull-debian-source -d python-librabbitmq mkdir python-librabbitmq cd python-librabbitmq git-import-dscs --pristine-tar ../python-librabbitmq_1.0.1-1.dsc Error message = gbp:info: Tag upstream/1.0.1 not found, importing Upstream tarball gbp:error: Git command failed: Error running git add: fatal: Not a git repository: rabbitmq-codegen/../.git/modules/rabbitmq-codegen gbp:error: Failed to import '[...]/python-librabbitmq_1.0.1-1.dsc' Analysis The upstream tarball contains the file rabbitmq-codegen/.git that contains the line gitdir: ../.git/modules/rabbitmq-codegen. git-buildpackage uses this git configuration file instead of just ignoring it. We have a --filter option to ignore such files. I'm not a big fan of ignoring any files silently but we should at least complain beforehand instead of failing in the middle of the import. Cheers, -- Guido -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#732712: denyhosts should not be released with jessie
Package: denyhosts Version: 2.6-10 Severity: serious Tags: jessie sid security Dear Maintainer, We, the Debian security team, believe that denyhosts should not be released with Debian jessie and further releases for the following reasons: * There are unaddressed security issues (e.g. #692229). * The tool is dead upstream (last release 2008). * There is a viable alternative, fail2ban, that provides the same or increased feature set. For these reasons we deem denyhosts unsupportable during the jessie release cycle. If you agree with this reasoning, please send the following commands to the control interface of the bug tracking system to remove the package from Debian sid as well: retitle -1 RM: denyhosts -- RoM severity -1 normal reassign -1 ftp.debian.org Helmut -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#714984: permission to do a vips upload to proposed-updates (bug 714984)
Resent previous message to correct address for debian-release -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#731097: Awesome 3.5 in Debian Sid
Hello, Julien Danjou a...@debian.org writes: On Fri, Dec 20 2013, Marco Patzer wrote: I'd like to know when awesome 3.5 will slip from experimental to unstable. It's been in experimental since quite a while now. Is something holding it back? Yeah I think there's a libxcb cursor missing in sid or something. Adding Arnaud in Cc as he knows better. Sorry for the lag. I have just uploaded 3.5.2 to experimental, but not unstable because of #1155[0] which makes Awesome 3.5.x totally unuseable for me and seems to be still there. Unfortunately, I haven't had time to investigate seriously this issue with Uli... Cheers, -- Arnaud Fontaine [0] https://awesome.naquadah.org/bugs/index.php?do=detailstask_id=1155 -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#732125: upstart-events(7) title is misleading
Hi Ian, As suggested, I've moved the appropriate sections to init(8) upstream as commit r1581: http://bazaar.launchpad.net/~upstart-devel/upstart/trunk/revision/1581 Note that upstart-events(7) is an Ubuntu+Debian-specific man page so debian/manpages/upstart-events.7 will need to be tweaked in Debian to: 1) Remove the Job States and Job Lifecycle sections from upstart-events.7. 2) Remove reference to Table 6 in the Event Summary section. I've already done this in Ubuntu as commit r1532: http://bazaar.launchpad.net/~ubuntu-branches/ubuntu/trusty/upstart/trusty/revision/1532 Kind regards, James. -- James Hunt #upstart on freenode http://upstart.ubuntu.com/cookbook https://lists.ubuntu.com/mailman/listinfo/upstart-devel -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#732677: RFS: ruby-specinfra/0.0.16-1 [ITP]
hi, On Fri, Dec 20, 2013 at 6:15 PM, d...@debian.org wrote: checked and uploaded. Thanks! regards, -- KURASHIKI Satoru
Bug#732144: Bug#731357: opu: package librsvg/2.26.3-2
Hi again,
Found another case where it didn't work as expected. Updated,
attached, patch should do it.
Cheers,
--
Raphael Geissert - Debian Developer
www.debian.org - get.debian.net
Index: librsvg-2.26.3/rsvg-image.c
===
--- librsvg-2.26.3.orig/rsvg-image.c 2013-12-20 14:28:57.731991069 +0100
+++ librsvg-2.26.3/rsvg-image.c 2013-12-20 14:38:59.384692376 +0100
@@ -325,22 +325,7 @@ rsvg_acquire_vfs_resource (const char *f
file = g_file_new_for_uri (filename);
-if (!(res = g_file_load_contents (file, NULL, data, size, NULL, error))) {
-if (base_uri != NULL) {
-GFile *base;
-
-rsvg_free_error (error);
-
-g_object_unref (file);
-
-base = g_file_new_for_uri (base_uri);
-file = g_file_resolve_relative_path (base, filename);
-g_object_unref (base);
-
-res = g_file_load_contents (file, NULL, data, size, NULL, error);
-}
-}
-
+res = g_file_load_contents (file, NULL, data, size, NULL, error);
g_object_unref (file);
if (res) {
@@ -356,23 +341,136 @@ rsvg_acquire_vfs_resource (const char *f
}
#endif
+/* Partial origin-based policy, based on the one implemented in f01aded72c38f0e1 */
+gboolean
+_rsvg_acquire_xlink_allow_load (const char *href, const char *base_uri, GError ** err)
+{
+char *base_scheme = NULL, *href_scheme = NULL;
+
+if (base_uri)
+base_scheme = g_uri_parse_scheme (base_uri);
+if (href)
+href_scheme = g_uri_parse_scheme (href);
+
+/* Not a valid URI */
+if (href_scheme == NULL)
+goto deny;
+
+/* Allow loads of data: from any location */
+if (g_str_equal (href_scheme, data))
+goto allow;
+
+/* no valid base URI */
+if (base_scheme == NULL)
+goto deny;
+
+/* Deny loads from differing URI schemes */
+if (href_scheme == NULL || !g_str_equal (href_scheme, base_scheme))
+goto deny;
+
+/* resource: is allowed to load anything from other resources */
+if (g_str_equal (href_scheme, resource))
+goto allow;
+
+/* Non-file: isn't allowed to load anything */
+if (!g_str_equal (href_scheme, file))
+goto deny;
+
+/* no local-file policy is applied here */
+
+allow:
+free(base_scheme);
+free(href_scheme);
+return TRUE;
+
+deny:
+free(base_scheme);
+free(href_scheme);
+g_set_error (err, G_IO_ERROR, G_IO_ERROR_PERMISSION_DENIED,
+ File may not link to URI \%s\, href);
+return FALSE;
+}
+
GByteArray *
_rsvg_acquire_xlink_href_resource (const char *href, const char *base_uri, GError ** err)
{
GByteArray *arr = NULL;
+char *base_scheme = NULL, *href_scheme = NULL;
+char *href_uri = NULL;
+#ifndef HAVE_GIO
+/* to be used ONLY for the policy check */
+GString *href_uri_str = NULL;
+#endif
if (!(href *href))
return NULL;
-if (!strncmp (href, data:, 5))
+if (base_uri)
+base_scheme = g_uri_parse_scheme (base_uri);
+if (href)
+href_scheme = g_uri_parse_scheme (href);
+
+if (href_scheme g_str_equal (href_scheme, data))
arr = rsvg_acquire_base64_resource (href, NULL);
+if (arr)
+goto done;
-if (!arr)
+#ifdef HAVE_GIO
+/* if href is not a URI already, turn it into one based on base_uri */
+if (href_scheme == NULL) {
+GFile *file, *base, *parentless_base;
+base = g_file_new_for_uri (base_uri);
+/* now strip the file name: */
+parentless_base = g_file_get_parent (base);
+file = g_file_resolve_relative_path (parentless_base, href);
+
+g_object_unref (base);
+g_object_unref (parentless_base);
+href_uri = g_file_get_uri(file);
+g_object_unref (file);
+} else {
+href_uri = strdup (href);
+if (!href_uri) /* FIXME: better handling failure */
+goto done;
+}
+#else
+if (href_scheme == NULL) {
+href_uri_str = g_string_new(href);
+if (base_scheme) {
+/* try to turn href into a uri */
+g_string_prepend (href_uri_str, ://);
+g_string_prepend (href_uri_str, base_scheme);
+/* no need to free, as href_scheme is NULL, remember? */
+href_scheme = strdup (base_scheme);
+if (!href_scheme) /* FIXME: better handling failure */
+goto done;
+} else
+goto done;
+} else {
+href_uri_str = g_string_new(href);
+}
+href_uri = href_uri_str-str;
+#endif
+
+if (!_rsvg_acquire_xlink_allow_load(href_uri, base_uri, err))
+goto done;
+
+#ifdef HAVE_GIO
+arr = rsvg_acquire_vfs_resource (href_uri, base_uri, NULL);
+#else
+/* href must be a path for fopen() to work */
+if (g_str_equal (href_scheme, file))
arr = rsvg_acquire_file_resource (href, base_uri, NULL);
+#endif
+
+done:
+free(href_scheme);
+
Bug#702882:
reopen 702882 thanks Logs states: https://buildd.debian.org/status/fetch.php?pkg=igrapharch=i386ver=0.6.5-4stamp=1387553594 [...] checking for f77_alloc_ in -lf2c... no checking for f77_alloc in -lf2c... no checking for F77_ALLOC_ in -lf2c... no checking for F77_ALLOC in -lf2c... no not found [...] dpkg-shlibdeps: warning: package could avoid a useless dependency if debian/libigraph0/usr/lib/i386-linux-gnu/libigraph.so.0.0.0 was not linked against libf2c.so.2 (it uses none of the library's symbols) dh_installdeb -a -O--parallel -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#727708: Quick upstart and systemd feature comparison
On Wed, Dec 18, 2013 at 06:59:50PM -0800, Russ Allbery wrote: Features that systemd provides that I didn't see in upstart (please correct me if I'm wrong): * StandardError=syslog. This would be *so nice* for *so many things*. Particularly for running Java applications, which are very bad about not sending everything to syslog even when one tries to write them to do so. I would start using this immediately. There are various external programs that can do this, but with sysvinit you have to set up the pipelines yourself and worry about the programs dying, whereas systemd takes care of all of that. It would be a straightforward incremental change on top of the existing logging support in Upstart. I'm not sure it's such a great idea to have some logs going to /var/log/upstart and some going via syslog, however; the resulting user/admin confusion may outweigh any benefit from supporting syslog. Are you actually looking for syslog per se here, or are you primarily interested in logging of stderr generally? Upstart already does that by default, it just logs it to /var/log/upstart instead of to syslog (for reasons of avoiding a dependency on on external daemon for debuggability). -- Steve Langasek Give me a lever long enough and a Free OS Debian Developer to set it on, and I can move the world. Ubuntu Developerhttp://www.debian.org/ slanga...@ubuntu.com vor...@debian.org signature.asc Description: Digital signature
Bug#732713: dh-python testsuite fails (wrong assumptions about symlink handling)
Package: dh-python Version: 1.20131021-2 Severity: important The dh-python package in Debian has its test suite disabled via debian/rules, with a 'FIXME' comment. The reason for this, it appears, is that t201 is completely broken wrt the actual symlink handling in dh-python. tests/t201/Makefile includes the following check: [ `readlink debian/python-foo/usr/lib/python$(DPY)/dist-packages/foo/absolute_link_to_tmp` = /tmp ] [ `readlink debian/python-foo/usr/lib/python$(DPY)/dist-packages/foo/link_to_parent_dir` = .. ] But dh_python2 unconditionally moves symlinks from /usr/lib/python* to /usr/share/pyshared, replacing them with relative symlinks in the original directory. for package, pdetails in dh.packages.items(): [...] if not private_dir: share(package, stats, options)d exists(pyshared_dir): I don't know which of these you consider correct, but they're obviously inconsistent, which makes it impossible to use the test suite for the purpose of detecting regressions in the code. I'm happy to provide a patch if you can tell me which should be changed, the code or the test. Bypassing this check gives me a subsequent failure in tests t202, t204, and t206 because of hard-coded references to python2.6 that are easily fixed, and presumably would have been noticed if the testsuite hadn't been disabled in the package. -- Steve Langasek Give me a lever long enough and a Free OS Debian Developer to set it on, and I can move the world. Ubuntu Developerhttp://www.debian.org/ slanga...@ubuntu.com vor...@debian.org signature.asc Description: Digital signature
Bug#727708: upstart upstream maintenance practices
Hi Russ, On Thu, Dec 19, 2013 at 11:19:37AM -0800, Russ Allbery wrote: Could someone (Steve, most likely) provide a bit of background for how upstart upstream maintenance works and relates to its packaging? This question is prompted by a few different things, set off by looking at the SELinux support since this is something I expect to start looking at for my day job. From there, I found that the SELinux context support in upstart is somewhat limited, but more interestingly is being maintained as a patch in the Debian package. (But maybe that's because the Debian packaging is one version behind?) I then looked at the Ubuntu patch for upstart and was rather surprised to find that it's quite large (although a lot of that is regeneration of the Autotools files -- can I recommend dh-autoreconf?). There appear to be substantive code changes in Ubuntu's packaging of upstart that aren't upstream, which surprised me. How does this all work? How do changes flow from Debian and Ubuntu packaging into upstream, and why would the packaging be carrying substantial local patches for software that's maintained upstream by (at least as I understand it) the same project? Is there a separate policy about what goes into upstream that precludes things that aren't considered fully baked? I'm attaching the full delta against upstream currently in the Ubuntu packaging VCS branch, for reference. FWIW, I'm not sure which version you were looking at, but the current version of the Ubuntu package (1.11-0ubuntu1) does not include any delta against autogenerated autotools files (and does use dh-autoreconf). Also FWIW, the attached patch includes changes not yet released to Ubuntu (actually, just an update to sync the packaging with the version in Debian). The attached delta is generated from: bzr diff -pa/:b/ -r tag:upstream-1.11 lp:ubuntu/upstart | filterdiff -x '**/debian/**' plus a bit of postprocessing. I've dissected the current delta and provided an explanation below for each bit, but the short answer to your question is yes: there are different policies for upstream vs. the Ubuntu package. Although efforts are made to keep the distro delta as small as possible, changes are sometimes applied to the package before they're in a state that they can be included in upstream in the interest of expediency. As for Upstart and Ubuntu being maintained by the same project: if Upstart were intended to be Ubuntu's init system, it would be reasonable to do all of the maintenance on a single upstream branch. But it was never intended to be Ubuntu's init system, but rather the init system, and as there are other downstreams besides Ubuntu, care is taken to not embed Ubuntu-specific policy upstream. So while there is some delta between Ubuntu and upstream right now, the delta between Debian and Ubuntu packages has been the greater focus of attention and has posed the greater maintenance challenge while trying to converge Ubuntu's packaging (which made reasonable assumptions of Upstart-everywhere) with Debian's (which did not). Now for the current delta, the changes here consist of a few different things: - Changes to core jobs for integration with Debian/Ubuntu. E.g., conf/rc-sysinit.conf is changed to refer to 'filesystem' and 'static-network-up' events that are provided by components external to upstart (mountall and ifupdown respectively). They are deemed inappropriate for upstream, because upstream upstart shouldn't have dependencies on distro-specific implementations. Likewise, conf/rc.conf has 'emits' lines added for documentation, which are only true when using a version of initscripts that includes upstart integration. - References to the Debian/Ubuntu-specific upstart-events(7) manpage, which describes event policy as it exists here. Not upstreamable for the same reason as the job changes; none of this applies to other users of upstart (e.g.: RHEL6, Chrome OS). - SELinux support. This was accepted as a distro patch in Debian, but has not been submitted under Canonical's contributor licensing agreement, so at present is not suitable for inclusion upstream per the upstream contribution policy. We are happy to carry such patches in the Debian/Ubuntu packaging delta where appropriate, though of course would prefer that such changes be mergeable upstream. - A minor build fix for configure.ac, to make the test suite function correctly under make -j. This is needed on systems with newer automake, and incompatible with systems with older automake, so carried as a distro patch for now. - A patch to disable apparmor in containers and liveCDs. This patch is from a member of the Ubuntu security team. I'm not sure why it's not upstreamed, but it's a minor patch and not at the top of my todo list to resolve. - A patch to work around https://bugs.launchpad.net/ubuntu/+source/upstart/+bug/1058356, which I believe will be
Bug#732623: lightdm-gtk-greeter: Hibernate and Restart buttons disappear after first login/logout
Control: reassign -1 lightdm 1.8.5-2
Control: retitle -1 lightdm_get_can_hibernate and lightdm_get_can_restart
return FALSE after first login/logout
On 2013-12-19 15:09:01 +0100, Vincent Lefevre wrote:
Package: lightdm-gtk-greeter
Version: 1.6.1-4
Severity: normal
Initially the following buttons are present in the top-right menu:
Suspend
Hibernate
Restart...
Shutdown...
But after the first login/logout, the Hibernate and Restart ones
disappear. I don't see any reason for that.
This is not a bug in lightdm-gtk-greeter itself, as the greeter
just calls the lightdm_get_can_* functions to decide whether the
menu items should be visible or not.
If I modify the liblightdm-gobject/power.c lightdm file to return
TRUE in all these functions, the problem no longer occurs. So, this
confirms that the problem comes from there. Thus reassigning.
I've tried to add some debug messages in these functions, but they
do not appear in the log files! I've attached the patch I've used.
--
Vincent Lefèvre vinc...@vinc17.net - Web: http://www.vinc17.net/
100% accessible validated (X)HTML - Blog: http://www.vinc17.net/blog/
Work: CR INRIA - computer arithmetic / AriC project (LIP, ENS-Lyon)
--- liblightdm-gobject/power.c 2013-10-09 05:16:00.0 +0200
+++ liblightdm-gobject/power.c 2013-12-20 16:13:29.559203457 +0100
@@ -88,6 +88,7 @@
gboolean can_suspend = FALSE;
GVariant *r;
+g_debug (lightdm_get_can_suspend: calling login1_call_function
(CanSuspend));
r = login1_call_function (CanSuspend, NULL, NULL);
if (r)
{
@@ -96,18 +97,23 @@
{
g_variant_get (r, (s), result);
can_suspend = g_strcmp0 (result, yes) == 0;
+g_debug (lightdm_get_can_suspend: can_suspend == %d via
login1_call_function, (int) can_suspend);
}
}
else
{
+g_debug (lightdm_get_can_suspend: calling upower_call_function
(SuspendAllowed));
r = upower_call_function (SuspendAllowed, NULL);
if (r g_variant_is_of_type (r, G_VARIANT_TYPE ((b
+{
g_variant_get (r, (b), can_suspend);
+g_debug (lightdm_get_can_suspend: can_suspend == %d via
upower_call_function, (int) can_suspend);
+}
}
if (r)
g_variant_unref (r);
-return can_suspend;
+return TRUE;
}
/**
@@ -153,6 +159,7 @@
gboolean can_hibernate = FALSE;
GVariant *r;
+g_debug (lightdm_get_can_hibernate: calling login1_call_function
(CanHibernate));
r = login1_call_function (CanHibernate, NULL, NULL);
if (r)
{
@@ -161,18 +168,23 @@
{
g_variant_get (r, (s), result);
can_hibernate = g_strcmp0 (result, yes) == 0;
+g_debug (lightdm_get_can_hibernate: can_hibernate == %d via
login1_call_function, (int) can_hibernate);
}
}
else
{
+g_debug (lightdm_get_can_hibernate: calling upower_call_function
(HibernateAllowed));
r = upower_call_function (HibernateAllowed, NULL);
if (r g_variant_is_of_type (r, G_VARIANT_TYPE ((b
+{
g_variant_get (r, (b), can_hibernate);
+g_debug (lightdm_get_can_hibernate: can_hibernate == %d via
upower_call_function, (int) can_hibernate);
+}
}
if (r)
g_variant_unref (r);
-return can_hibernate;
+return TRUE;
}
/**
@@ -248,6 +260,7 @@
gboolean can_restart = FALSE;
GVariant *r;
+g_debug (lightdm_get_can_restart: calling login1_call_function
(CanReboot));
r = login1_call_function (CanReboot, NULL, NULL);
if (r)
{
@@ -256,18 +269,23 @@
{
g_variant_get (r, (s), result);
can_restart = g_strcmp0 (result, yes) == 0;
+g_debug (lightdm_get_can_restart: can_restart == %d via
login1_call_function, (int) can_restart);
}
}
else
{
+g_debug (lightdm_get_can_restart: calling ck_call_function
(CanRestart));
r = ck_call_function (CanRestart, NULL);
if (r g_variant_is_of_type (r, G_VARIANT_TYPE ((b
+{
g_variant_get (r, (b), can_restart);
+g_debug (lightdm_get_can_restart: can_restart == %d via
ck_call_function, (int) can_restart);
+}
}
if (r)
g_variant_unref (r);
-return can_restart;
+return TRUE;
}
/**
@@ -310,6 +328,7 @@
gboolean can_shutdown = FALSE;
GVariant *r;
+g_debug (lightdm_get_can_shutdown: calling login1_call_function
(CanPowerOff));
r = login1_call_function (CanPowerOff, NULL, NULL);
if (r)
{
@@ -318,18 +337,23 @@
{
g_variant_get (r, (s), result);
can_shutdown = g_strcmp0 (result, yes) == 0;
+g_debug (lightdm_get_can_shutdown: can_shutdown == %d via
login1_call_function, (int) can_shutdown);
}
}
else
{
+g_debug (lightdm_get_can_shutdown: calling ck_call_function
Bug#727708: systemd jessie - jessie+1 upgrade problems
On Thu, Dec 19, 2013 at 11:26:19PM +0100, Josselin Mouette wrote: Le jeudi 19 décembre 2013 à 12:35 -0800, Steve Langasek a écrit : The reasons for not upgrading to the current version of logind aren't to do with any fragility of the existing glue code (the systemd-shim package), but because logind 205 has a new dependency on systemd as cgroup manager, which is architecturally incompatible with other consumers of cgroups in the ecosystem. This needs to be resolved before logind v205 can reasonably be adopted, because it's broken by design and needs to be worked around. The new logind is not “broken by design”. Using the cgroups tree is the most correct and secure way to identify which processes are permitted to access specific devices or services. You might disagree with the idea of a single cgroups manager or prefer a less secure mechanism in order to handle corner cases (that have yet to be described), but that doesn’t make the design less correct. The design which claims this role for systemd-as-pid-1, and which does not adequately address use cases of other existing cgroups consumers in the ecosystem (lmctfy, lxc) is broken by design. Having a single cgroup writer in userspace is fine. Coupling it to systemd in this manner is not. -- Steve Langasek Give me a lever long enough and a Free OS Debian Developer to set it on, and I can move the world. Ubuntu Developerhttp://www.debian.org/ slanga...@ubuntu.com vor...@debian.org signature.asc Description: Digital signature
Bug#732715: liblist-moreutils-perl: Attempt to free unreferenced scalar in some use cases of List::MoreUtils::part
Package: liblist-moreutils-perl
Version: 0.33-1+b2
Severity: normal
Dear Maintainer,
This is quite weird. If the code used in `part`
* is built using given..when
* does a return after a match on the first value of the list
the code will result in the dreaded Attempt to free unreferenced scalar
message. Reproducer (tested on amd64 and i386):
{{{
#!/usr/bin/perl
use 5.010;
use List::MoreUtils;
my @files = (
'foo',
'bar',
);
my @groups = List::MoreUtils::part (
sub {
given ($_) {
when ('foo') {
return 0; # this return is evil
}
default {
return 1; # this one does no harm
}
}
},
@files,
);
}}}
Output:
{{{
given is experimental at reproducer line 13.
when is experimental at reproducer line 14.
Attempt to free unreferenced scalar: SV 0x1c1ae98, Perl interpreter: 0x1c18010.
}}}
There is more than one workaround: Omit the return keyword.
Rewriting the code to return outside the given..when block does
the trick, too. The pure Perl implementation does the right thing,
too.
As said before, the message is triggered by the way the code block
is left for the first list element of the list processed, in other
words, this one
{{{
when ('bar') {
1;
}
default {
return 0;
}
}}}
is affected, too.
So I think somebody should take a look into that. I'm concerned the
observation is just a symptom of a bigger problem like data
corruption.
-- System Information:
Debian Release: jessie/sid
APT prefers testing
APT policy: (500, 'testing')
Architecture: amd64 (x86_64)
Kernel: Linux 3.10.24 (SMP w/4 CPU cores; PREEMPT)
Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968)
Shell: /bin/sh linked to /bin/dash
Versions of packages liblist-moreutils-perl depends on:
ii libc6 2.17-97
ii perl5.18.1-5
ii perl-base [perlapi-5.18.1] 5.18.1-5
liblist-moreutils-perl recommends no packages.
liblist-moreutils-perl suggests no packages.
-- no debconf information
signature.asc
Description: Digital signature
Bug#732714: ca-certificates: New version of certdata.txt distrusts AC DG Tresor SSL CA
Package: ca-certificates Severity: normal Tags: security Mozilla has released nss 3.15.3.1 that specifically distrusts the AC DG Tresor SSL CA. ca-certificates needs to be updated to the new certdata.txt. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#732678: git-buildpackage -A calls lintian with the wrong .changes file
On Fri, Dec 20, 2013 at 04:05:14PM +0100, Guido Günther wrote: Can you attach (or mail me directly) the full build output with --git-verbose please. [..snip..] Scratch that, patch forthcoming. Do you have any better ideas than checking the dpkg-buildpackage command line for -A to detect wheter we need arch or all? I'd be so cool if dpkg-buildpackage would have a nice way to communicate back such information to build tools. This still holds though. Cheers, -- Guido -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#732678: [git-buildpackage/master] Determine changes file name based on dpkg-buildpackage options
tag 732678 pending thanks Date: Fri Dec 20 17:01:17 2013 +0100 Author: Guido Günther a...@sigxcpu.org Commit ID: eec8ce3e2f35d6f06a5ddb9b4a6f264a1ecf4bca Commit URL: https://honk.sigxcpu.org/gitweb/?p=git-buildpackage.git;a=commitdiff;h=eec8ce3e2f35d6f06a5ddb9b4a6f264a1ecf4bca Patch URL: https://honk.sigxcpu.org/gitweb/?p=git-buildpackage.git;a=commitdiff_plain;h=eec8ce3e2f35d6f06a5ddb9b4a6f264a1ecf4bca Determine changes file name based on dpkg-buildpackage options Closes: #732678 -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#732716: RFP: weave-minimal -- lightweight firefox weave/sync server
Package: wnpp Severity: wishlist * Package name: weave-minimal Version : 1.4 Upstream Author : Martin Zimmermann i...@posativ.org * URL : https://github.com/posativ/weave-minimal * License : MIT Programming Lang: Python Description : lightweight firefox weave/sync server a Firefox Sync Server that just works: This is a lightweight implementation of Mozillas' User API v1.0 and Storage API v1.1 without LDAP, MySQL, Redis etc. overhead. It is multi users capable and depends only on werkzeug. I mean, really lightweight and really simple to install. No hg-attack clone fetch fail apt-get install. It just works. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#732064: lapack depends on specific blas implementation
2013/12/19, Sébastien Villemot sebast...@debian.org: Le mardi 17 décembre 2013 à 16:47 +0100, Andrey Gursky a écrit : Sebastien, thanks for pointing this out. I've also got caught in the same trap. But this would mean a trade-off, since openblas's version of lapack is just striped away for now. Should I open a new bug for openblas or could it be, that optimizations of openblas's lapack are not significant enough? My understanding is that OpenBLAS does not provide a specialized version of LAPACK. It just gives the possibility of bundling LAPACK within the libopenblas.a, which is uninteresting for us. But I have not investigated this too much, so if OpenBLAS provides a customized LAPACK as ATLAS does, then please open a wishlist bug against openblas. I just was confused by the thread [1], where an opinion(?) was expressed: Now, because the both ATLAS and OpenBLAS versions of LAPACK have some functions overridden with more efficient versions... Now comparing OpenBLAS.git and lapack-3.5.0 yields: ... Only in OpenBLAS.git/lapack: getf2 Only in OpenBLAS.git/lapack: getrf Only in OpenBLAS.git/lapack: getri Only in OpenBLAS.git/lapack: getrs ... Only in OpenBLAS.git/lapack: laswp Only in OpenBLAS.git/lapack: lauu2 Only in OpenBLAS.git/lapack: lauum ... Only in OpenBLAS.git/lapack: potf2 Only in OpenBLAS.git/lapack: potrf Only in OpenBLAS.git/lapack: trti2 Only in OpenBLAS.git/lapack: trtri I'm wondering, whether lapack interface could be remaining general modified in a way, atlas and openblas could use it without changing. Or the things are more complicated? When you use the general LAPACK in Debian, you still benefit from ATLAS and OpenBLAS optimizations everytime LAPACK calls a BLAS function. Does this answer your question? Yes, I was surprised, that besides a BLAS optimization an optimization of LAPACK is also needed. Considering at least a statement from ATLAS FAQ [2]: The provided LAPACK routines utilize a recursive algorithm that should yield reliably better results than the more common staticly-blocked algorithms. and it seems the ATLAS LAPACK is not a patched general netlib LAPACK at all. Anyway, I believe, this bug report belongs to be merged with the one you've mentioned (#576972). [1] https://fedorahosted.org/fpc/ticket/352 [2] http://math-atlas.sourceforge.net/faq.html#optcomp -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#722217: legacy304 also
What version of dpkg are you using? Could it be this problem? dpkg (1.17.5) unstable; urgency=low [ Guillem Jover ] [...] * Fix segfault in update-alternatives when adding or renaming slaves for an existing alternative. Regression introduced in dpkg 1.17.2. Closes: #731710 dpkg 1.16.12 from jessie/testing Brent
