Bug#784413: ITP: php-horde-idna -- IDNA backend normalization package
Package: wnpp Severity: wishlist Owner: Mathieu Parent math.par...@gmail.com Package name: Horde_Idna Version : 1.0.4 Upstream Author : Michael Slusarz URL : http://horde.org/ License : BSD-2-Clause Programming Lang: PHP Description : IDNA backend normalization package Normalized access to various backends providing IDNA (Internationalized Domain Names in Applications) support. I'm packaging this as part of Horde5 packaging. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#784410: ITP: php-math-biginteger -- Usage: /usr/share/pkg-php-tools/scripts/phppkginfo [options] package|package_type|channel|summary|description|maintainers dir|package.xml /usr/share/pkg-
Package: wnpp Severity: wishlist Owner: Mathieu Parent math.par...@gmail.com Package name: Usage: /usr/share/pkg-php-tools/scripts/phppkginfo [options] package|package_type|channel|summary|description|maintainers dir|package.xml /usr/share/pkg-php-tools/scripts/phppkginfo [options] date|version|license|changelog|all|hasphpscript dir|package.xml /usr/share/pkg-php-tools/scripts/phppkginfo [options] debian_deps dir|package.xml /usr/share/pkg-php-tools/scripts/phppkginfo [options] debian_pkgname channel_url pear_name /usr/share/pkg-php-tools/scripts/phppkginfo [options] debian_version version /usr/share/pkg-php-tools/scripts/phppkginfo [options] channel_name|channel_summary|channel_alias channel.xml /usr/share/pkg-php-tools/scripts/phppkginfo [options] composer_... dir|composer.json PEAR package commands: package - Name of package package_type- Type of package (php|extsrc|extbin|zendextsrc|zendextbin|bundle|false) channel - PEAR channel URL summary - Short summary of package description - Long description of package maintainers - Comma separated list of maintainers date- Date of release version - Version of package license - License of package changelog - Full changelog of package all - print_r() of complete package file hasphpscript- Check if package contains files of type 'script' debian_deps - Print dependencies as Debian control fields debian_pkgname - Translate a PEAR package name to a Debian package name debian_version - Translate a PEAR version to a Debian version PEAR channel commands: channel_name- Get channel name channel_summary - Get channel summary channel_alias - Get channel alias Composer commands: composer_name- Get Composer package name composer_description - Get Composer package description composer_version - Get Composer package version composer_type- Get Composer package type composer_keywords- Get Composer package keywords composer_homepage- Get Composer package homepage composer_time- Get Composer package time composer_license - Get Composer package license composer_authors - Get Composer package authors composer_support - Get Composer package support composer_require - Get Composer package require composer_require_dev - Get Composer package require_dev composer_conflict- Get Composer package conflict composer_replace - Get Composer package replace composer_provide - Get Composer package provide composer_suggest - Get Composer package suggest composer_autoload- Get Composer package autoload composer_config - Get Composer package config composer_substvars - Debian substvars from Composer package arguments: dir - Directory containing package.xml, package2.xml or composer.json file options: -d - print debug to STDERR Version : Usage: /usr/share/pkg-php-tools/scripts/phppkginfo [options] package|package_type|channel|summary|description|maintainers dir|package.xml /usr/share/pkg-php-tools/scripts/phppkginfo [options] date|version|license|changelog|all|hasphpscript dir|package.xml /usr/share/pkg-php-tools/scripts/phppkginfo [options] debian_deps dir|package.xml /usr/share/pkg-php-tools/scripts/phppkginfo [options] debian_pkgname channel_url pear_name /usr/share/pkg-php-tools/scripts/phppkginfo [options] debian_version version /usr/share/pkg-php-tools/scripts/phppkginfo [options] channel_name|channel_summary|channel_alias channel.xml /usr/share/pkg-php-tools/scripts/phppkginfo [options] composer_... dir|composer.json PEAR package commands: package - Name of package package_type- Type of package (php|extsrc|extbin|zendextsrc|zendextbin|bundle|false) channel - PEAR channel URL summary - Short summary of package description - Long description of package maintainers - Comma separated list of maintainers date- Date of release version - Version of package license - License of package changelog - Full changelog of package all - print_r() of complete package file hasphpscript- Check if package contains files of type 'script' debian_deps - Print dependencies as Debian control fields debian_pkgname - Translate a PEAR package name to a Debian package name debian_version - Translate a PEAR version to a Debian version PEAR channel commands: channel_name- Get channel name channel_summary - Get channel summary channel_alias - Get channel alias Composer commands: composer_name- Get Composer package name composer_description - Get Composer package description composer_version - Get Composer package version composer_type- Get Composer package type
Bug#784411: ITP: php-horde-idna -- IDNA backend normalization package
Package: wnpp Severity: wishlist Owner: Mathieu Parent math.par...@gmail.com Package name: Horde_Idna Version : 1.0.4 Upstream Author : Michael Slusarz URL : http://horde.org/ License : BSD-2-Clause Programming Lang: PHP Description : IDNA backend normalization package Normalized access to various backends providing IDNA (Internationalized Domain Names in Applications) support. I'm packaging this as part of Horde5 packaging. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#784409: ITP: php-phpseclib-sourceforge-file-asn1 -- Usage: /usr/share/pkg-php-tools/scripts/phppkginfo [options] package|package_type|channel|summary|description|maintainers dir|package.xml
Package: wnpp Severity: wishlist Owner: Mathieu Parent math.par...@gmail.com Package name: Usage: /usr/share/pkg-php-tools/scripts/phppkginfo [options] package|package_type|channel|summary|description|maintainers dir|package.xml /usr/share/pkg-php-tools/scripts/phppkginfo [options] date|version|license|changelog|all|hasphpscript dir|package.xml /usr/share/pkg-php-tools/scripts/phppkginfo [options] debian_deps dir|package.xml /usr/share/pkg-php-tools/scripts/phppkginfo [options] debian_pkgname channel_url pear_name /usr/share/pkg-php-tools/scripts/phppkginfo [options] debian_version version /usr/share/pkg-php-tools/scripts/phppkginfo [options] channel_name|channel_summary|channel_alias channel.xml /usr/share/pkg-php-tools/scripts/phppkginfo [options] composer_... dir|composer.json PEAR package commands: package - Name of package package_type- Type of package (php|extsrc|extbin|zendextsrc|zendextbin|bundle|false) channel - PEAR channel URL summary - Short summary of package description - Long description of package maintainers - Comma separated list of maintainers date- Date of release version - Version of package license - License of package changelog - Full changelog of package all - print_r() of complete package file hasphpscript- Check if package contains files of type 'script' debian_deps - Print dependencies as Debian control fields debian_pkgname - Translate a PEAR package name to a Debian package name debian_version - Translate a PEAR version to a Debian version PEAR channel commands: channel_name- Get channel name channel_summary - Get channel summary channel_alias - Get channel alias Composer commands: composer_name- Get Composer package name composer_description - Get Composer package description composer_version - Get Composer package version composer_type- Get Composer package type composer_keywords- Get Composer package keywords composer_homepage- Get Composer package homepage composer_time- Get Composer package time composer_license - Get Composer package license composer_authors - Get Composer package authors composer_support - Get Composer package support composer_require - Get Composer package require composer_require_dev - Get Composer package require_dev composer_conflict- Get Composer package conflict composer_replace - Get Composer package replace composer_provide - Get Composer package provide composer_suggest - Get Composer package suggest composer_autoload- Get Composer package autoload composer_config - Get Composer package config composer_substvars - Debian substvars from Composer package arguments: dir - Directory containing package.xml, package2.xml or composer.json file options: -d - print debug to STDERR Version : Usage: /usr/share/pkg-php-tools/scripts/phppkginfo [options] package|package_type|channel|summary|description|maintainers dir|package.xml /usr/share/pkg-php-tools/scripts/phppkginfo [options] date|version|license|changelog|all|hasphpscript dir|package.xml /usr/share/pkg-php-tools/scripts/phppkginfo [options] debian_deps dir|package.xml /usr/share/pkg-php-tools/scripts/phppkginfo [options] debian_pkgname channel_url pear_name /usr/share/pkg-php-tools/scripts/phppkginfo [options] debian_version version /usr/share/pkg-php-tools/scripts/phppkginfo [options] channel_name|channel_summary|channel_alias channel.xml /usr/share/pkg-php-tools/scripts/phppkginfo [options] composer_... dir|composer.json PEAR package commands: package - Name of package package_type- Type of package (php|extsrc|extbin|zendextsrc|zendextbin|bundle|false) channel - PEAR channel URL summary - Short summary of package description - Long description of package maintainers - Comma separated list of maintainers date- Date of release version - Version of package license - License of package changelog - Full changelog of package all - print_r() of complete package file hasphpscript- Check if package contains files of type 'script' debian_deps - Print dependencies as Debian control fields debian_pkgname - Translate a PEAR package name to a Debian package name debian_version - Translate a PEAR version to a Debian version PEAR channel commands: channel_name- Get channel name channel_summary - Get channel summary channel_alias - Get channel alias Composer commands: composer_name- Get Composer package name composer_description - Get Composer package description composer_version - Get Composer package version composer_type- Get Composer package type
Bug#784412: ITP: php-horde-managesieve -- Client library for ManageSieve
Package: wnpp Severity: wishlist Owner: Mathieu Parent math.par...@gmail.com Package name: Horde_ManageSieve Version : 1.0.0alpha1 Upstream Author : Jan Schneider URL : http://horde.org/ License : BSD Programming Lang: PHP Description : Client library for ManageSieve This library implements the ManageSieve protocol (RFC 5804). I'm packaging this as part of Horde5 packaging. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#784415: ITP: php-math-biginteger -- Usage: /usr/share/pkg-php-tools/scripts/phppkginfo [options] package|package_type|channel|summary|description|maintainers dir|package.xml /usr/share/pkg-
Package: wnpp Severity: wishlist Owner: Mathieu Parent math.par...@gmail.com Package name: Usage: /usr/share/pkg-php-tools/scripts/phppkginfo [options] package|package_type|channel|summary|description|maintainers dir|package.xml /usr/share/pkg-php-tools/scripts/phppkginfo [options] date|version|license|changelog|all|hasphpscript dir|package.xml /usr/share/pkg-php-tools/scripts/phppkginfo [options] debian_deps dir|package.xml /usr/share/pkg-php-tools/scripts/phppkginfo [options] debian_pkgname channel_url pear_name /usr/share/pkg-php-tools/scripts/phppkginfo [options] debian_version version /usr/share/pkg-php-tools/scripts/phppkginfo [options] channel_name|channel_summary|channel_alias channel.xml /usr/share/pkg-php-tools/scripts/phppkginfo [options] composer_... dir|composer.json PEAR package commands: package - Name of package package_type- Type of package (php|extsrc|extbin|zendextsrc|zendextbin|bundle|false) channel - PEAR channel URL summary - Short summary of package description - Long description of package maintainers - Comma separated list of maintainers date- Date of release version - Version of package license - License of package changelog - Full changelog of package all - print_r() of complete package file hasphpscript- Check if package contains files of type 'script' debian_deps - Print dependencies as Debian control fields debian_pkgname - Translate a PEAR package name to a Debian package name debian_version - Translate a PEAR version to a Debian version PEAR channel commands: channel_name- Get channel name channel_summary - Get channel summary channel_alias - Get channel alias Composer commands: composer_name- Get Composer package name composer_description - Get Composer package description composer_version - Get Composer package version composer_type- Get Composer package type composer_keywords- Get Composer package keywords composer_homepage- Get Composer package homepage composer_time- Get Composer package time composer_license - Get Composer package license composer_authors - Get Composer package authors composer_support - Get Composer package support composer_require - Get Composer package require composer_require_dev - Get Composer package require_dev composer_conflict- Get Composer package conflict composer_replace - Get Composer package replace composer_provide - Get Composer package provide composer_suggest - Get Composer package suggest composer_autoload- Get Composer package autoload composer_config - Get Composer package config composer_substvars - Debian substvars from Composer package arguments: dir - Directory containing package.xml, package2.xml or composer.json file options: -d - print debug to STDERR Version : Usage: /usr/share/pkg-php-tools/scripts/phppkginfo [options] package|package_type|channel|summary|description|maintainers dir|package.xml /usr/share/pkg-php-tools/scripts/phppkginfo [options] date|version|license|changelog|all|hasphpscript dir|package.xml /usr/share/pkg-php-tools/scripts/phppkginfo [options] debian_deps dir|package.xml /usr/share/pkg-php-tools/scripts/phppkginfo [options] debian_pkgname channel_url pear_name /usr/share/pkg-php-tools/scripts/phppkginfo [options] debian_version version /usr/share/pkg-php-tools/scripts/phppkginfo [options] channel_name|channel_summary|channel_alias channel.xml /usr/share/pkg-php-tools/scripts/phppkginfo [options] composer_... dir|composer.json PEAR package commands: package - Name of package package_type- Type of package (php|extsrc|extbin|zendextsrc|zendextbin|bundle|false) channel - PEAR channel URL summary - Short summary of package description - Long description of package maintainers - Comma separated list of maintainers date- Date of release version - Version of package license - License of package changelog - Full changelog of package all - print_r() of complete package file hasphpscript- Check if package contains files of type 'script' debian_deps - Print dependencies as Debian control fields debian_pkgname - Translate a PEAR package name to a Debian package name debian_version - Translate a PEAR version to a Debian version PEAR channel commands: channel_name- Get channel name channel_summary - Get channel summary channel_alias - Get channel alias Composer commands: composer_name- Get Composer package name composer_description - Get Composer package description composer_version - Get Composer package version composer_type- Get Composer package type
Bug#784414: ITP: php-horde-managesieve -- Client library for ManageSieve
Package: wnpp Severity: wishlist Owner: Mathieu Parent math.par...@gmail.com Package name: Horde_ManageSieve Version : 1.0.0alpha1 Upstream Author : Jan Schneider URL : http://horde.org/ License : BSD Programming Lang: PHP Description : Client library for ManageSieve This library implements the ManageSieve protocol (RFC 5804). I'm packaging this as part of Horde5 packaging. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#784416: ITP: php-phpseclib-sourceforge-file-asn1 -- Usage: /usr/share/pkg-php-tools/scripts/phppkginfo [options] package|package_type|channel|summary|description|maintainers dir|package.xml
Package: wnpp Severity: wishlist Owner: Mathieu Parent math.par...@gmail.com Package name: Usage: /usr/share/pkg-php-tools/scripts/phppkginfo [options] package|package_type|channel|summary|description|maintainers dir|package.xml /usr/share/pkg-php-tools/scripts/phppkginfo [options] date|version|license|changelog|all|hasphpscript dir|package.xml /usr/share/pkg-php-tools/scripts/phppkginfo [options] debian_deps dir|package.xml /usr/share/pkg-php-tools/scripts/phppkginfo [options] debian_pkgname channel_url pear_name /usr/share/pkg-php-tools/scripts/phppkginfo [options] debian_version version /usr/share/pkg-php-tools/scripts/phppkginfo [options] channel_name|channel_summary|channel_alias channel.xml /usr/share/pkg-php-tools/scripts/phppkginfo [options] composer_... dir|composer.json PEAR package commands: package - Name of package package_type- Type of package (php|extsrc|extbin|zendextsrc|zendextbin|bundle|false) channel - PEAR channel URL summary - Short summary of package description - Long description of package maintainers - Comma separated list of maintainers date- Date of release version - Version of package license - License of package changelog - Full changelog of package all - print_r() of complete package file hasphpscript- Check if package contains files of type 'script' debian_deps - Print dependencies as Debian control fields debian_pkgname - Translate a PEAR package name to a Debian package name debian_version - Translate a PEAR version to a Debian version PEAR channel commands: channel_name- Get channel name channel_summary - Get channel summary channel_alias - Get channel alias Composer commands: composer_name- Get Composer package name composer_description - Get Composer package description composer_version - Get Composer package version composer_type- Get Composer package type composer_keywords- Get Composer package keywords composer_homepage- Get Composer package homepage composer_time- Get Composer package time composer_license - Get Composer package license composer_authors - Get Composer package authors composer_support - Get Composer package support composer_require - Get Composer package require composer_require_dev - Get Composer package require_dev composer_conflict- Get Composer package conflict composer_replace - Get Composer package replace composer_provide - Get Composer package provide composer_suggest - Get Composer package suggest composer_autoload- Get Composer package autoload composer_config - Get Composer package config composer_substvars - Debian substvars from Composer package arguments: dir - Directory containing package.xml, package2.xml or composer.json file options: -d - print debug to STDERR Version : Usage: /usr/share/pkg-php-tools/scripts/phppkginfo [options] package|package_type|channel|summary|description|maintainers dir|package.xml /usr/share/pkg-php-tools/scripts/phppkginfo [options] date|version|license|changelog|all|hasphpscript dir|package.xml /usr/share/pkg-php-tools/scripts/phppkginfo [options] debian_deps dir|package.xml /usr/share/pkg-php-tools/scripts/phppkginfo [options] debian_pkgname channel_url pear_name /usr/share/pkg-php-tools/scripts/phppkginfo [options] debian_version version /usr/share/pkg-php-tools/scripts/phppkginfo [options] channel_name|channel_summary|channel_alias channel.xml /usr/share/pkg-php-tools/scripts/phppkginfo [options] composer_... dir|composer.json PEAR package commands: package - Name of package package_type- Type of package (php|extsrc|extbin|zendextsrc|zendextbin|bundle|false) channel - PEAR channel URL summary - Short summary of package description - Long description of package maintainers - Comma separated list of maintainers date- Date of release version - Version of package license - License of package changelog - Full changelog of package all - print_r() of complete package file hasphpscript- Check if package contains files of type 'script' debian_deps - Print dependencies as Debian control fields debian_pkgname - Translate a PEAR package name to a Debian package name debian_version - Translate a PEAR version to a Debian version PEAR channel commands: channel_name- Get channel name channel_summary - Get channel summary channel_alias - Get channel alias Composer commands: composer_name- Get Composer package name composer_description - Get Composer package description composer_version - Get Composer package version composer_type- Get Composer package type
Bug#784421: Hibernate does not work
Package: kde-workspace Version: 4:4.11.13-2 Severity: normal On a fresh jessie install, hibernate writes to disk then power off the laptop. However at restart, it reads the disk, then reboot. systemctl hibernate works, so the underlying mechanism should be Ok. -- System Information: Debian Release: 8.0 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 3.16.0-4-amd64 (SMP w/8 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages kde-workspace depends on: ii freespacenotifier 4:4.11.13-2 ii kde-window-manager 4:4.11.13-2 ii kde-workspace-bin 4:4.11.13-2 ii klipper 4:4.11.13-2 ii ksysguard 4:4.11.13-2 ii systemsettings 4:4.11.13-2 Versions of packages kde-workspace recommends: ii kdm 4:4.11.13-2 ii kinfocenter 4:4.11.13-2 ii kmenuedit4:4.11.13-2 kde-workspace 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#783237: CVE-2014-9462
Hi Alessandro,
On Sat, May 02, 2015 at 09:04:42AM +0100, Javi Merino wrote:
On Fri, May 01, 2015 at 08:53:28PM +0200, Alessandro Ghedini wrote:
On Fri, May 01, 2015 at 07:16:07PM +0100, Javi Merino wrote:
On Fri, Apr 24, 2015 at 01:21:56PM +0200, Moritz Muehlenhoff wrote:
Package: mercurial
Severity: important
Tags: security
Please see
http://chargen.matasano.com/chargen/2015/3/17/this-new-vulnerability-mercurial-command-injection-cve-2014-9462.html
Fix:
http://selenic.com/hg/rev/e3f30068d2eb
[...]
Also, the vulnerability seems to affect the wheezy version as well, could
you
please prepare an upload targeting wheezy-security as well?
I've prepared an upload for wheezy-security, find the diff below. Can
I upload it to security-master?
Index: debian/changelog
===
--- debian/changelog(revisión: 11643)
+++ debian/changelog(copia de trabajo)
@@ -1,3 +1,11 @@
+mercurial (2.2.2-4+deb7u1) wheezy-security; urgency=high
+
+ * Fix CVE-2014-9462 by adding patch
+from_upstream__sshpeer_more_thorough_shell_quoting.patch (Closes:
+#783237)
+
+ -- Javi Merino vi...@debian.org Wed, 06 May 2015 08:09:26 +0100
+
mercurial (2.2.2-4) stable; urgency=high
* Security update for CVE-2014-9390: errors in handling case-sensitive
Index: debian/patches/series
===
--- debian/patches/series (revisión: 11643)
+++ debian/patches/series (copia de trabajo)
@@ -14,3 +14,4 @@
from_upstream__encoding_add_hfsignoreclean_to_clean_out_HFS-ignored_characters.patch
from_upstream__pathauditor_check_for_codepoints_ignored_on_OS_X.patch
from_upstream__pathauditor_check_for_Windows_shortname_aliases.patch
+from_upstream__sshpeer_more_thorough_shell_quoting.patch
Index: debian/patches/from_upstream__sshpeer_more_thorough_shell_quoting.patch
===
--- debian/patches/from_upstream__sshpeer_more_thorough_shell_quoting.patch
(revisión: 0)
+++ debian/patches/from_upstream__sshpeer_more_thorough_shell_quoting.patch
(revisión: 11901)
@@ -0,0 +1,29 @@
+Origin: http://selenic.com/hg/rev/e3f30068d2eb
+Bug-Debian: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=783237
+Description: sshpeer: more thorough shell quoting
+ This fixes CVE-2014-9462
+Applied-Upstream: 3.2.4
+
+--- a/mercurial/sshrepo.py
b/mercurial/sshrepo.py
+@@ -20,6 +20,8 @@ class remotelock(object):
+ self.release()
+
+ def _serverquote(s):
++if not s:
++return s
+ '''quote a string for the remote shell ... which we assume is sh'''
+ if re.match('[a-zA-Z0-9@%_+=:,./-]*$', s):
+ return s
+@@ -44,7 +46,10 @@ class sshrepository(wireproto.wirereposi
+ sshcmd = self.ui.config(ui, ssh, ssh)
+ remotecmd = self.ui.config(ui, remotecmd, hg)
+
+-args = util.sshargs(sshcmd, self.host, self.user, self.port)
++args = util.sshargs(sshcmd,
++_serverquote(self.host),
++_serverquote(self.user),
++_serverquote(self.port))
+
+ if create:
+ cmd = '%s %s %s' % (sshcmd, args,
signature.asc
Description: Digital signature
Bug#784429: ITP: python-xstatic-angular-lrdragndrop -- Angular-Lrdragndrop 1.0.2 (XStatic packaging standard)
Package: wnpp Severity: wishlist Owner: Thomas Goirand z...@debian.org * Package name: python-xstatic-angular-lrdragndrop Version : 1.0.2.2 Upstream Author : Thai Tran tqt...@us.ibm.com * URL : https://github.com/stackforge/xstatic-angular-lrdragndrop * License : Apache-2.0 Programming Lang: Python Description : Angular-Lrdragndrop 1.0.2 (XStatic packaging standard) XStatic is a Python web development tool for handling required static data files from external projects, such as CSS, images, and JavaScript. It provides a lightweight infrastructure to manage them via Python modules that your app can depend on in a portable, virtualenv-friendly way instead of using embedded copies. . This package contains the Python 2 3 module support for Angular-Lrdragndrop. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#784430: Regression: Running lynx to access a https doesn't success
Package: libgnutls-deb0-28 Version: 3.3.15-1 Severity: normal Running lynx -source www.kernel.org gives: Looking up www.kernel.org Making HTTP connection to www.kernel.org Sending HTTP request. HTTP request sent; waiting for response. HTTP/1.1 301 Moved Permanently Data transfer complete HTTP/1.1 301 Moved Permanently Using https://www.kernel.org/ Looking up www.kernel.org Making HTTPS connection to www.kernel.org Retrying connection without TLS. Looking up www.kernel.org Making HTTPS connection to www.kernel.org Alert!: Unable to make secure connection to remote host. Reverting gnutls to 3.3.14-2 succeeded. Attached is a stracelog. -- Elimar -- System Information: Debian Release: stretch/sid APT prefers unstable APT policy: (990, 'unstable'), (1, 'experimental') Architecture: i386 (i686) Kernel: Linux 3.14.31-baumbart-lxtec-i686 (SMP w/2 CPU cores) Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash Init: sysvinit (via /sbin/init) Versions of packages libgnutls-deb0-28 depends on: ii libc62.19-18 ii libgmp10 2:6.0.0+dfsg-6 ii libhogweed2 2.7.1-5 ii libnettle4 2.7.1-5 ii libp11-kit0 0.23.1-2 ii libtasn1-6 4.5-2 ii zlib1g 1:1.2.8.dfsg-2+b1 libgnutls-deb0-28 recommends no packages. Versions of packages libgnutls-deb0-28 suggests: ii gnutls-bin 3.3.15-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#784239: transition: xfce 4.12
Control: tags -1 confirmed On 04/05/15 13:34, Yves-Alexis Perez wrote: we'd like to upload Xfce 4.12 to unstable. It currently sits in experimental since few weeks, and seems to work just fine. Go ahead. Emilio -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#770672: gnome-packagekit: FTBFS without docbook: reference to entity REFENTRY for which no system identifier could be generated
On Mon, Dec 01, 2014 at 11:49:18AM -0800, Daniel Schepler wrote: Looking back at the bug report, it seems I forgot to mention something important: I was able to reproduce this in a pbuilder chroot installing from the official archive, but manually installing the build dependencies in such a way that docbook wasn't pulled in, then unplugging the network cable and running the build. If it's possible to satisfy the Build-Depends but have the build fail, that's still a serious bug, whether or not it happens with the default way pbuilder and/or sbuild satisfies the Build-Depends. I also hit this issue on none official environment, without network access. It built fine after adding `docbook' as build dependency as Daniel suggested. I concur severity should at least be serious for this one bug. Regards, -- Hector Oron signature.asc Description: Digital signature
Bug#742723: Fwd: Re: CrashMail II doesn't work on debian jessie
Control: found -1 1.5-1 -- Forwarded Message -- Subject: Re: CrashMail II doesn't work on debian jessie Date: Monday, May 04, 2015, 05:30:04 PM From: VS tvw...@yandex.ru To: j...@rocasa.us 04.05.2015 16:37, Robert James Clay пишет: Hi Vladislav! On Sunday, May 03, 2015 03:51:12 AM you wrote: Hello Jame! CrashMail II doesn't work on debian jessie. Error: Failed to read message #1 in JAM messagebase /home/fido/areas/3bfe0095 So, this was with version 1.5? And was this the 64 bit version? I ask because I have seen or have heard of issues with the 64 bit version that do not seem to be in the 32 bit version. Yes, that is 64 bit Debian Jessie. $ crashmail version This is CrashMail II version 1.5 Message #1 was created by golded plus and/or msged te in a Jam message base. And were either or both of those, 32 bit versions? I've checked it only by GoldedPlus 64 bit and Msged TE 64bit compiled both by myself. I ask because I found that the most recent statically built version of GoldEd I could find was 32 bit build, and most of my systems are 64 bit this days; so I've been planning to try building my own packages for GoldEd so I'd have both a 32 bit and 64 bit version available of it for use and testing. (Haven't worked with MsgEd for quite some time...) Also I can't switch on debug mode for logging. You mean, by setting the LogLevel to 6? Yes If so; what are you expecting that you are not seeing? I haven't noticed big difference between LogLevel 3 and LogLevel 6. That is why I've decided LogLevel 6 didn't work. (Note; that is the setting I use...) Please check! Original crashmail has these errors too. Which version do you mean when you said original? v0.71? No. Crashmail 1.5. Not deb-packet, but compiled by myself. http://sourceforge.net/projects/crashmail.ftnapps.p/files/1.5/crashmail-1.5.tar.gz/download By the way - I have my old JAM message base from 2002 year. It was made by crashecho (not crashmail). There weren't any errors when I worked with it in 2002. But now, when I scan it by crashmail II and have this error for the each echo-conference in my JAM Base - Failed to read message #2 (#3,#4,#5...#11) in JAM messagebase /home/fido/areas/3bfe0095. Messages from #2 to #5 have this error but messages #1 and #11 ... #20 are OK. I've thought - my jam messagebase is broken. And simply have made one message by GoldedPlus and MSGED TE in a new JAM base. I got the same error - Failed to read message #1 in JAM messagebase /home/fido/areas/3bfe0095 That is why I think - that is problem of crashmail II. Thanks for your reply. Best regards, Vladislav - -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#759008:
Control: User debian-h...@lists.debian.org Control: Usertag -1 +hurd Hi guys, Isn't the priorty our users? So what is most favourable for them? IMHO: NOT having a TONS of software available not avialble due to this bug is more severe than the bear some increased risk (There be dragons) that something breaks. So from my perspective, it is worth taking the risk. Because only then bug reports will come in *if* anything breaks. We'll only learn if we try. hurd is not a release arch, so even if that gives you bug reports, it won't impact libtdb1. Dear maintainer, please reconsider with the user's perspective I tried to gave you above. Just my 0,02€ Thanks for considering. -- tobi signature.asc Description: This is a digitally signed message part
Bug#784433: Package 'nam' needs tcl8.6 to run but depends on tcl8.5
Package: nam Version: 1.15 The package nam requires tcl8.6 for running. But, it installs tcl8.5 along with it (i.e tcl8.5 is a dependency of nam). So, even if tcl8.6 is installed, tcl8.5 gets loaded for nam. Since tcl8.5 is a dependency of nam, manually removing it also removes nam. This is the error that is generated nam: [code omitted because of length] : version conflict for package Tcl: have 8.5.17, need 8.6 while executing package require Tcl 8.6 So, please change the dependency of nam to tcl8.6 -- Regards Balasankar C http://balasankarc.in -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#783062: meld scrolls into the wrong direction
Hi Balint, of course I tried the suggested xmodmap line. It seems to fix the scroll direction for meld on Jessie, but now the scroll direction for all other apps is not natural anymore (including meld on Wheezy, emacs and xterm and firefox and ... on all platforms). Sorry to say, but the workaround doesn't. If you think this is a GTK issue, then please reassign. I would highly appreciate a meld without GTK. Thanx in advance Harri -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#754121:
reassign: -1 aiccu Am 06.05.2015 um 04:43 schrieb Daniel Albers: This is a critical bug of either aiccu or systemd as explained by Pascal. Assigning also to systemd as the aiccu maintainer considers this a systemd bug, although I think message #26 546673f0.1040...@localhost.localdomain.org already points to the proper fix for aiccu. Jeroen Massar is not listed as maintainer of the aiccu package and I don't see any explanation which would hint at a bug in systemd. Therefor re-assigning back to aiccu. From a quick look at the package, it seems to install a init script which depends on $network and an if-up.d hook which restarts the aiccu init script as part of /etc/init.d/networking. /etc/init.d/networking itself provides $network, so there is a dead lock, since systemd evaluates dependencies at runtime. Reinier, if you need help with getting this sorted out, please contact the pkg-systemd team. Is there a reason, aiccu needs to be restarted on ifup? Does it need that to pick up new network interfaces? The better fix is, to make aiccu network hotplug aware (e.g. via rtnetlink) [1]. This would also mean, aiccu would work better ootb with other networking tools or if the network is configured manually. [1] http://www.freedesktop.org/wiki/Software/systemd/NetworkTarget/ -- Why is it that all of the instruments seeking intelligent life in the universe are pointed away from Earth? signature.asc Description: OpenPGP digital signature
Bug#784431: nsca-ng-server: fails to start with systemd because /var/run/nsca-ng is missing
Package: nsca-ng-server Version: 1.4-1 Severity: grave Justification: renders package unusable -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 After reboot, the nsca-ng-server service does not start because it cannot write its pid file to /var/run/nsca-ng. This is the default location in the shipped configuration. There is a diff between the init script and the systemd unit in that the init script adds an extra flag (-P) specifying a writable pid file that overrides the path from the config. The systemd unit does not pass this flag on start so nsca-ng tries to use the pid file defined in the config file. I'd propose aligning the ssytemd unit with the init script and passing the same -P flag. -BEGIN PGP SIGNATURE- Version: GnuPG v1 iQJOBAEBCAA4BQJVSdqDMRpodHRwczovL3d3dy5kb21pbmlrLWdlb3JnZS5kZS9n cGctcG9saWN5LnR4dC5hc2MACgkQt5o8FqDE8pZ6/hAAle+4vhhY+gpH04M3lzZ/ MrdBoNEhFiRj1yEBzD2+noklcwEUtxaUD5CchgLZOaVmpxo2CMRY9Vi6sP529cfh uQ9gnb0Em+nu/iKROMVZFyApmcISIYdcPnAQjSoymT6HqrXxF5rmN+hU449XSp7c EnvD7k8NFRGj7p8vdEPruVab+/sCUcHzK243ecvZzTvx+xniA15/Es7UUicqqYSK AU7x47DQjCv9JWMlgu5QM421r1yAZSXhbCBeb6I7w+ARIcVmseHoiuq0a8b8iDGK gBIqcwBxReoQFUI+yBJ80aqPOErmSqTQdde83BNfaadk5l7CwhysTJwrniJfSfnK HlEz+QaX0WCOellRQNEOSfo0ye2VxIU3YhQZ+Avwgzc+Hs2bwy0i+ULDNQu7LlmH y/jiJrIKWR8JSLEq/yBEyOvLmgbeN5xyTktBXzzXbv9lFE+HW4vI//H3eWxJ1QzD TAkpfdKfqhcYrEhDJjc8mCTSdBtJ1nsvJ8H9uDfy2tHv9WDKjeYZ7vC7MSOa3TtQ QNRzxhOJobs9tDWaFhuNjmxJgun2iBZmFyn7F+YUt9++EqPUz7V/+CJFTG+MR92Q F/fE6wJHBTVw0hHAisofgkeezf5QMU1hHJUPseUs02cOmybor+n4G+FcPSqsFm1C q9J4ccc4vVwZXFTCC/xBBKg= =3qBL -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#784386: gnome-shell doesn't show applications from /var/lib/menu-xdg/applications/menu-xdg/
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On 06-05-15 02:04, Michael Biebl wrote: Please file a bug against gltron to provide a proper .desktop file. Already there: bug #737910. -BEGIN PGP SIGNATURE- Version: GnuPG v2 iQIcBAEBCAAGBQJVSdvCAAoJEN/62Bl2F+8ZqgQP/iDi9kcGMPDlWauqb50VUW4P bDAHUxii6PwGexoGnCwIO0iihkbWUevo/6Cpv77pb4KQIg68ROT+T8kAGoRdULz+ 0ST8pZjYVCy0Wc5JJMssPKhNRZm3YyPRzZnDOwwbbjRkO0c8ws0A9RDq0a/t8tiH q9rjMdahlLWlZDkGzbOfjw+rzd1Pwy/+6/3ss/hOgvAvNuxokNPlJkJ6zRNHcNYo WJ45ENalPNfiJyhMgFudbZUe3zhGavmC5DOFmtY2r8byqd4p1LueAGDh4+xlYBhK DC2j9XPiSygXr6vuabYITbQJQcDmzqL2pfURlYuaKdf5+F0kcTgt6Sv1zrTSc/yQ IaNjPyhmJUKMKS1xTHQQ98UdX7d3QOc2TZ7odaxjgEhNnKpQJb1+LNlfhHA1T6yM vCgxpMxJpcZV+MTabJrbcg+4jO1WVsYiQJ+jvVnjc9sgOKwow3B68JAs7g050yJX OCYungMJ2M094KMG4OBN+iRMxGMlvvUzoSfBBxc4MO9RU8XqoNn7sQHlHc93RPU9 luFxqK2ksgu+FXaM8A85lz8tl4yw0s8Z9klREv5BZ/nZUlxBG+G3oXuAuf5S2zUu 589H84uIf8ABPg2gPq3kX1fG7hq4RFAYZGFF7xU/Tc/I+iQizWSgkwGxr3uMwwnk PQI7gb+eIM4oE2djm8c7 =l/RC -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#782364: linux-image-3.16.0-4-armmp: please configure drivers for both Cubox i4pro real time clocks
OK, How will I identify the upload when I see it? The box is running Debian/Sid and I do regular updates. So presumably, I’ll see a “linux-image-3.16.0-4-armmp” package go by sometime soon? And I’ll know I’ve got it when I see two /dev/rtc* devices? As for “rbtho...@cube.rcthomas.org” — I’m afraid it’s bogus. I had exim4 configured wrong when I submitted the original bugreport /-:. I’m subscribed to the bugreport with my proper address (“rbtho...@pobox.com”) now; so you can either just send stuff for me to the bugreport directly or to the “@pobox.com” address, and delete (or simply ignore) “rbtho...@cube.rcthomas.org” whenever it raises its head. Thanks! This has been an interesting and educational discussion! Rick On May 6, 2015, at 1:01 AM, Ian Campbell i...@debian.org wrote: On Sat, 2015-05-02 at 17:21 +0100, Ian Campbell wrote: We typically build RTCs statically (for this sort of reason) so it seems like the right thing for us to do here is to build both in. Which I've now done in SVN. Rick, please test the next upload. Also, Rick, I'm getting messages from my MTA about not being able to deliver to rbtho...@cube.rcthomas.org, it's been queuing/retrying since the weekend and says I shouldn't worry, but I thought I'd mention it since I was here. Exim logs say: 2015-05-06 06:48:50 1YoZqj-0002JC-G0 == rbtho...@cube.rcthomas.org R=dnslookup T=remote_smtp defer (-53): retry time not reached for any host Hopefully you will see this via some other route. Ian. -- To unsubscribe, send mail to 782364-unsubscr...@bugs.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#782364: linux-image-3.16.0-4-armmp: please configure drivers for both Cubox i4pro real time clocks
Control: submitter -1 Rick Thomas rbtho...@pobox.com On Wed, 2015-05-06 at 03:00 -0700, Rick Thomas wrote: OK, How will I identify the upload when I see it? The box is running Debian/Sid and I do regular updates. So presumably, I’ll see a “linux-image-3.16.0-4-armmp” package go by sometime soon? I think the next thing to hit Sid will be some 4.0.x per https://lists.debian.org/debian-kernel/2015/05/msg00047.html I also committed to the Jessie branch so eventually (I don't know when) a new 3.16 based thing should appear in jessie-proposed-updates (staging area for a point release). I'm not sure if the BTS will say anything when this happens nor how else one might get notified. It would be preferable to test the thing in Sid before the upload to jessie-proposed-updates And I’ll know I’ve got it when I see two /dev/rtc* devices? Yes, I suppose. As for “rbtho...@cube.rcthomas.org” — I’m afraid it’s bogus. I had exim4 configured wrong when I submitted the original bugreport /-:. I’m subscribed to the bugreport with my proper address (“rbtho...@pobox.com”) now; so you can either just send stuff for me to the bugreport directly or to the “@pobox.com” address, and delete (or simply ignore) “rbtho...@cube.rcthomas.org” whenever it raises its head. I think the line at the top should have reset the submitter to your proper address too. If you wanted to do that yourself you could use ! as a shorthand for the address in the From: line. Ian. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#783459: dnsmasq: Wheezy regression caused by CVE-2015-3294/2.62-3+deb7u2 w/ bind-interfaces
Hi Ian,
On Wed, May 06, 2015 at 08:48:53AM +0100, Ian Campbell wrote:
Package: dnsmasq
Followup-For: Bug #783459
Dear Maintainer,
After upgrading to 2.62-3+deb7u2 on Wheezy/armel dnsmasq now fails to start
with:
root@yog-sothoth:~# dpkg -i dnsmasq*2.62-3+deb7u2*.deb
(Reading database ... 25941 files and directories currently installed.)
Preparing to replace dnsmasq 2.62-3+deb7u1 (using
dnsmasq_2.62-3+deb7u2_all.deb) ...
Unpacking replacement dnsmasq ...
Preparing to replace dnsmasq-base 2.62-3+deb7u1 (using
dnsmasq-base_2.62-3+deb7u2_armel.deb) ...
Unpacking replacement dnsmasq-base ...
Setting up dnsmasq-base (2.62-3+deb7u2) ...
Processing triggers for man-db ...
Setting up dnsmasq (2.62-3+deb7u2) ...
insserv: warning: current stop runlevel(s) (1) of script `dnsmasq'
overrides LSB defaults (0 1 6).
[] Restarting DNS forwarder and DHCP server: dnsmasq
dnsmasq: failed to set SO_REUSE{ADDR|PORT} on DHCP socket: Protocol not
available
failed!
invoke-rc.d: initscript dnsmasq, action restart failed.
root@yog-sothoth:~#
Downgrading back to 2.62-3+deb7u1 makes things work again.
Searching around there are various (mostly a few year old) reports of this
which are related to the use of the bind-interfaces option which I had enabled
in /etc/dnsmasq.conf since dnsmasq runs on a router with multiple interfaces.
For now I've disabled bind-interfaces, although I'm not entirely happy with
that since it exposes dnsmasq to traffic from the outside Internet, even if it
is to be discarded.
I just tried to replicate that configuration and set up a wheezy VM up with two
interfaces eth0, eth1, and set the following modifications:
interface=eth1
bind-interfaces
domain=example.com
dhcp-range=192.168.1.128,192.168.1.255,12h
But so far I was not able to reproduce the problem, but only from a quit
re-check (and in particular not the same arch as well).
cut-cut-cut-cut-cut-cut-
root@dnsmasq-test:~# dpkg-query -f '${Package} ${Version}\n' -W dnsmasq
dnsmasq-base
dnsmasq 2.62-3+deb7u1
dnsmasq-base 2.62-3+deb7u1
root@dnsmasq-test:~# cat /etc/dnsmasq.d/regression.conf
interface=eth1
bind-interfaces
domain=example.com
dhcp-range=192.168.1.128,192.168.1.255,12h
root@dnsmasq-test:~# ip link show
1: lo: LOOPBACK,UP,LOWER_UP mtu 16436 qdisc noqueue state UNKNOWN mode DEFAULT
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
2: eth0: BROADCAST,MULTICAST,UP,LOWER_UP mtu 1500 qdisc pfifo_fast state UP
mode DEFAULT qlen 1000
link/ether 52:54:00:95:ed:78 brd ff:ff:ff:ff:ff:ff
3: eth1: BROADCAST,MULTICAST,UP,LOWER_UP mtu 1500 qdisc pfifo_fast state UP
mode DEFAULT qlen 1000
link/ether 52:54:00:50:46:5a brd ff:ff:ff:ff:ff:ff
root@dnsmasq-test:~# apt-get install dnsmasq dnsmasq-base
Reading package lists... Done
Building dependency tree
Reading state information... Done
Suggested packages:
resolvconf
The following packages will be upgraded:
dnsmasq dnsmasq-base
2 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
Need to get 387 kB of archives.
After this operation, 0 B of additional disk space will be used.
Get:1 http://security.debian.org/ wheezy/updates/main dnsmasq-base amd64
2.62-3+deb7u2 [370 kB]
Get:2 http://security.debian.org/ wheezy/updates/main dnsmasq all 2.62-3+deb7u2
[16.3 kB]
Fetched 387 kB in 0s (1,789 kB/s)
(Reading database ... 18634 files and directories currently installed.)
Preparing to replace dnsmasq-base 2.62-3+deb7u1 (using
.../dnsmasq-base_2.62-3+deb7u2_amd64.deb) ...
Unpacking replacement dnsmasq-base ...
Preparing to replace dnsmasq 2.62-3+deb7u1 (using
.../dnsmasq_2.62-3+deb7u2_all.deb) ...
Unpacking replacement dnsmasq ...
Processing triggers for man-db ...
Setting up dnsmasq-base (2.62-3+deb7u2) ...
Setting up dnsmasq (2.62-3+deb7u2) ...
Restarting DNS forwarder and DHCP server: dnsmasq.
root@dnsmasq-test:~#
cut-cut-cut-cut-cut-cut-
Regards,
Salvatore
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#784430: Regression: Running lynx to access a https doesn't success
* Elimar Riesebieter riese...@lxtec.de [2015-05-06 10:54 +0200]:
Package: libgnutls-deb0-28
Version: 3.3.15-1
Severity: normal
[...]
Attached is a stracelog.
Elimar
--
.~.
/V\ L I N U X
/( )\ Phear the Penguin
^^-^^
execve(/usr/bin/lynx, [lynx, -source, www.kernel.org], [/* 85 vars */])
= 0
brk(0) = 0xb7829000
access(/etc/ld.so.nohwcap, F_OK) = -1 ENOENT (No such file or directory)
mmap2(NULL, 8192, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) =
0xb75f7000
access(/etc/ld.so.preload, R_OK) = -1 ENOENT (No such file or directory)
open(/etc/ld.so.cache, O_RDONLY|O_CLOEXEC) = 3
fstat64(3, {st_mode=S_IFREG|0644, st_size=28008, ...}) = 0
mmap2(NULL, 28008, PROT_READ, MAP_PRIVATE, 3, 0) = 0xb75f
close(3)= 0
access(/etc/ld.so.nohwcap, F_OK) = -1 ENOENT (No such file or directory)
open(/lib/i386-linux-gnu/libz.so.1, O_RDONLY|O_CLOEXEC) = 3
read(3,
\177ELF\1\1\1\0\0\0\0\0\0\0\0\0\3\0\3\0\1\0\0\0\360\30\0\0004\0\0\0..., 512)
= 512
fstat64(3, {st_mode=S_IFREG|0644, st_size=112284, ...}) = 0
mmap2(NULL, 114952, PROT_READ|PROT_EXEC, MAP_PRIVATE|MAP_DENYWRITE, 3, 0) =
0xb75d3000
mmap2(0xb75ed000, 12288, PROT_READ|PROT_WRITE,
MAP_PRIVATE|MAP_FIXED|MAP_DENYWRITE, 3, 0x19000) = 0xb75ed000
close(3)= 0
access(/etc/ld.so.nohwcap, F_OK) = -1 ENOENT (No such file or directory)
open(/lib/i386-linux-gnu/libbz2.so.1.0, O_RDONLY|O_CLOEXEC) = 3
read(3, \177ELF\1\1\1\0\0\0\0\0\0\0\0\0\3\0\3\0\1\0\0\0P\20\0\0004\0\0\0...,
512) = 512
fstat64(3, {st_mode=S_IFREG|0644, st_size=74228, ...}) = 0
mmap2(NULL, 77060, PROT_READ|PROT_EXEC, MAP_PRIVATE|MAP_DENYWRITE, 3, 0) =
0xb75c
mmap2(0xb75d, 12288, PROT_READ|PROT_WRITE,
MAP_PRIVATE|MAP_FIXED|MAP_DENYWRITE, 3, 0xf000) = 0xb75d
close(3)= 0
access(/etc/ld.so.nohwcap, F_OK) = -1 ENOENT (No such file or directory)
open(/usr/lib/i386-linux-gnu/libidn.so.11, O_RDONLY|O_CLOEXEC) = 3
read(3,
\177ELF\1\1\1\0\0\0\0\0\0\0\0\0\3\0\3\0\1\0\0\0\220\35\0\0004\0\0\0..., 512)
= 512
fstat64(3, {st_mode=S_IFREG|0644, st_size=210448, ...}) = 0
mmap2(NULL, 4096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) =
0xb75bf000
mmap2(NULL, 213224, PROT_READ|PROT_EXEC, MAP_PRIVATE|MAP_DENYWRITE, 3, 0) =
0xb758a000
mmap2(0xb75bc000, 12288, PROT_READ|PROT_WRITE,
MAP_PRIVATE|MAP_FIXED|MAP_DENYWRITE, 3, 0x31000) = 0xb75bc000
close(3)= 0
access(/etc/ld.so.nohwcap, F_OK) = -1 ENOENT (No such file or directory)
open(/lib/i386-linux-gnu/libncursesw.so.5, O_RDONLY|O_CLOEXEC) = 3
read(3, \177ELF\1\1\1\0\0\0\0\0\0\0\0\0\3\0\3\0\1\0\0\0\220a\0\0004\0\0\0...,
512) = 512
fstat64(3, {st_mode=S_IFREG|0644, st_size=239916, ...}) = 0
mmap2(NULL, 243208, PROT_READ|PROT_EXEC, MAP_PRIVATE|MAP_DENYWRITE, 3, 0) =
0xb754e000
mmap2(0xb7588000, 8192, PROT_READ|PROT_WRITE,
MAP_PRIVATE|MAP_FIXED|MAP_DENYWRITE, 3, 0x39000) = 0xb7588000
close(3)= 0
access(/etc/ld.so.nohwcap, F_OK) = -1 ENOENT (No such file or directory)
open(/lib/i386-linux-gnu/libtinfo.so.5, O_RDONLY|O_CLOEXEC) = 3
read(3, \177ELF\1\1\1\0\0\0\0\0\0\0\0\0\3\0\3\0\1\0\0\0\300^\0\0004\0\0\0...,
512) = 512
fstat64(3, {st_mode=S_IFREG|0644, st_size=141676, ...}) = 0
mmap2(NULL, 141612, PROT_READ|PROT_EXEC, MAP_PRIVATE|MAP_DENYWRITE, 3, 0) =
0xb752b000
mmap2(0xb754b000, 12288, PROT_READ|PROT_WRITE,
MAP_PRIVATE|MAP_FIXED|MAP_DENYWRITE, 3, 0x2) = 0xb754b000
close(3)= 0
access(/etc/ld.so.nohwcap, F_OK) = -1 ENOENT (No such file or directory)
open(/usr/lib/i386-linux-gnu/libgnutls-deb0.so.28, O_RDONLY|O_CLOEXEC) = 3
read(3, \177ELF\1\1\1\0\0\0\0\0\0\0\0\0\3\0\3\0\1\0\0\0@\214\1\0004\0\0\0...,
512) = 512
fstat64(3, {st_mode=S_IFREG|0644, st_size=1328864, ...}) = 0
mmap2(NULL, 1334976, PROT_READ|PROT_EXEC, MAP_PRIVATE|MAP_DENYWRITE, 3, 0) =
0xb73e5000
mmap2(0xb7522000, 36864, PROT_READ|PROT_WRITE,
MAP_PRIVATE|MAP_FIXED|MAP_DENYWRITE, 3, 0x13c000) = 0xb7522000
close(3)= 0
access(/etc/ld.so.nohwcap, F_OK) = -1 ENOENT (No such file or directory)
open(/lib/i386-linux-gnu/libbsd.so.0, O_RDONLY|O_CLOEXEC) = 3
read(3,
\177ELF\1\1\1\0\0\0\0\0\0\0\0\0\3\0\3\0\1\0\0\0\260\\0\0004\0\0\0..., 512) =
512
fstat64(3, {st_mode=S_IFREG|0644, st_size=63396, ...}) = 0
mmap2(NULL, 69668, PROT_READ|PROT_EXEC, MAP_PRIVATE|MAP_DENYWRITE, 3, 0) =
0xb73d3000
mmap2(0xb73e2000, 8192, PROT_READ|PROT_WRITE,
MAP_PRIVATE|MAP_FIXED|MAP_DENYWRITE, 3, 0xe000) = 0xb73e2000
mmap2(0xb73e4000, 36, PROT_READ|PROT_WRITE,
MAP_PRIVATE|MAP_FIXED|MAP_ANONYMOUS, -1, 0) = 0xb73e4000
close(3)= 0
access(/etc/ld.so.nohwcap, F_OK) = -1 ENOENT (No such file or directory)
open(/lib/i386-linux-gnu/libc.so.6, O_RDONLY|O_CLOEXEC) = 3
read(3,
\177ELF\1\1\1\0\0\0\0\0\0\0\0\0\3\0\3\0\1\0\0\0\200\230\1\0004\0\0\0...,
Bug#784434: base: Sometimes permanent hard disk activity in one second intervals after logged in as non-root user
/at-spi2-core/at-spi2-registryd --use-gnome-session gmr 1085 1025 1 09:49 ?00:01:05 /usr/lib/gnome-settings-daemon/gnome-settings-daemon gmr 1101 1 0 09:49 ?00:00:00 /usr/lib/gvfs/gvfsd gmr 1104 1 0 09:49 ?00:00:00 /usr/bin/pulseaudio --start gmr 1109 1 0 09:49 ?00:00:00 /usr/lib/gvfs/gvfsd-fuse /run/user/1000/gvfs -f -o big_writes gmr 1121 1 0 09:49 ?00:00:00 /usr/lib/gvfs/gvfs-udisks2-volume-monitor root 1123 1 0 09:49 ?00:00:01 /usr/lib/udisks2/udisksd --no-debug gmr 1132 1 0 09:49 ?00:00:00 /usr/lib/gvfs/gvfs-afc-volume-monitor gmr 1137 1 0 09:49 ?00:00:00 /usr/lib/gvfs/gvfs-goa-volume-monitor gmr 1140 1 0 09:49 ?00:00:01 /usr/lib/gnome-online-accounts/goa-daemon gmr 1146 1 0 09:49 ?00:00:00 /usr/lib/telepathy/mission-control-5 gmr 1149 1 0 09:49 ?00:00:00 /usr/lib/gvfs/gvfs-gphoto2-volume-monitor gmr 1153 1 0 09:49 ?00:00:00 /usr/lib/gvfs/gvfs-mtp-volume-monitor gmr 1161 1 0 09:49 ?00:00:00 /usr/lib/gnome-settings-daemon/gsd-printer gmr 1178 1 0 09:49 ?00:00:00 /bin/sh /usr/bin/start-pulseaudio-x11 gmr 1179 1178 0 09:49 ?00:00:00 /usr/bin/xprop -root -spy gmr 1180 1025 32 09:49 ?00:35:22 /usr/bin/gnome-shell gmr 1200 1 0 09:49 ?00:00:00 /usr/lib/gnome-shell/gnome-shell-calendar-server gmr 1212 1 0 09:49 ?00:00:00 /usr/lib/evolution/evolution-source-registry gmr 1215 1025 0 09:49 ?00:00:00 /usr/lib/evolution/3.12/evolution-alarm-notify gmr 1217 1025 0 09:49 ?00:00:00 /usr/bin/python /usr/share/system-config-printer/applet.py gmr 1226 1025 0 09:49 ?00:00:00 /usr/lib/tracker/tracker-miner-user-guides gmr 1229 1 0 09:49 ?00:00:02 /usr/lib/tracker/tracker-store gmr 1230 1025 0 09:49 ?00:00:00 /usr/lib/tracker/tracker-miner-apps gmr 1231 1025 0 09:49 ?00:00:04 nautilus -n gmr 1232 1025 0 09:49 ?00:00:00 /usr/lib/tracker/tracker-extract gmr 1242 1 0 09:49 ?00:00:00 /usr/lib/evolution/evolution-calendar-factory gmr 1243 1025 0 09:49 ?00:00:01 /usr/lib/tracker/tracker-miner-fs gmr 1251 1025 0 09:49 ?00:00:00 nm-applet gmr 1292 1 0 09:49 ?00:00:00 /usr/lib/i386-linux-gnu/gconf/gconfd-2 gmr 1296 1 0 09:49 ?00:00:00 /usr/lib/gvfs/gvfsd-trash --spawner :1.8 /org/gtk/gvfs/exec_spaw/0 gmr 1319 1 0 09:49 ?00:00:00 /usr/lib/gvfs/gvfsd-burn --spawner :1.8 /org/gtk/gvfs/exec_spaw/1 gmr 1339 1 0 09:49 ?00:00:01 /usr/lib/gvfs/gvfsd-metadata root 1570 2 0 10:03 ?00:00:38 [kworker/3:2] gmr 1607 1 0 10:07 ?00:00:00 /usr/lib/dconf/dconf-service root 1618 2 0 10:08 ?00:00:38 [kworker/2:1] root 1650 32431 0 11:37 pts/100:00:00 ps -ef root 1941 2 0 10:48 ?00:00:00 [kworker/2:2] root 8542 2 0 10:57 ?00:00:00 [kworker/u8:0] root 17643 2 0 11:09 ?00:00:00 [kworker/0:0] root 25251 2 0 11:21 ?00:00:00 [kworker/u8:2] gmr 27780 1 0 11:25 ?00:00:03 /usr/lib/gnome-terminal/gnome-terminal-server gmr 27783 27780 0 11:25 ?00:00:00 gnome-pty-helper gmr 27785 27780 0 11:25 pts/000:00:00 /bin/bash gmr 27881 27785 0 11:25 pts/000:00:00 /usr/bin/python /usr/bin/reportbug gmr 29875 27881 0 11:29 pts/000:00:00 sh -c /usr/bin/sensible-editor '/tmp/reportbug-base-20150506-27881-ZjOvTb' gmr 29876 29875 0 11:29 pts/000:00:00 /bin/sh /usr/bin/sensible-editor /tmp/reportbug-base-20150506-27881-ZjOvTb gmr 29884 29876 0 11:29 pts/000:00:01 /bin/nano /tmp/reportbug-base-20150506-27881-ZjOvTb gmr 32382 27780 0 11:34 pts/100:00:00 bash root 32411 32382 0 11:34 pts/100:00:00 su - root 32431 32411 0 11:34 pts/100:00:00 -su To get rid of the problem, that means to get an inactive hard disk again, I tried the following: 1. I just changed to another user. Result: NO success ! Therefore I logged off from this second user and went back to the original user gmr. 2. Then I logged off as user gmr. Result: SUCCESS! The internal hard disk was quiet again directly after logging off. Now the processes are: UIDPID PPID C STIME TTY TIME CMD root 1 0 0 09:48 ?00:00:01 /sbin/init root 2 0 0 09:48 ?00:00:00 [kthreadd] root 3 2 1 09:48 ?00:01:21 [ksoftirqd/0] root 5 2 0 09:48 ?00:00:00 [kworker/0:0H] root 7 2 0 09:48 ?00:01:03 [rcu_sched] root 8 2 0 09:48 ?00:00:00 [rcu_bh] root 9
Bug#783089: Workaround
Le 2015-05-05 16:52, Cyril Brulebois a écrit : jean-y...@lenhof.eu.org jean-y...@lenhof.eu.org (2015-05-05): As a workaround, you can : - Boot on the Debian CD - Select Rescue - Change to a terminal - cd /tmp - ar x /cdrom/pool/main/l/linux/linux-image-3.16.0-4-amd64_3.16.7-ckt7-1_amd64.deb - xzcat data.tar.xz - cd /tmp/lib/modules/3.16.0-4-amd64/kernel/drivers/md/ - insmod raid10.ko - insmod dm-raid.ko - change back to first console and select your root lv So sure it is only the udeb lacking this kernel module. I will work to produce a little patch to the good udeb kernel package. They are produced by src:linux, you should only have to update a list, possibly debian/installer/modules/md-modules? Mraw, KiBi. Yep, I think so... I'm looking at it now. The question is how to rebuilt a debian CD after. Will a replacement of kernel package and udeb kernel package in the pool/l/linux will be sufficient ? If not is there a description of how to rebuilt the debian CD anywhere ? Moreover, I think that dm-thin-pool.ko, dm-persistent-data.ko, and dm-bio-prison.ko should also be added to have thin provisionning support in rescue mode/during installation. Regards, -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#761403: CAP_KILL
Peter Palfrader wea...@debian.org writes: On Wed, 06 May 2015, Arto Jantunen wrote: I was planning to move to Type=notify + User=debian-tor + RuntimeDirectory=/var/run/tor in the service file, and a separate config instead of the current tor-service-defaults-torrc (without PidFile, RunAsDaemon and User) as the next step after that. I assume moving the User to the service file would work only because we give Tor CAP_NET_BIND_SERVICE, right? Yes, that would be the plan. I haven't tested this (yet), though. Why would we want to set RuntimeDirectory? If User is set in the service file instead of torrc that would work, and would liberate us from needing to manually do the same thing with ExecStartPre. Having Type=notify instead of simple will require modifying Tor accordingly, correct? Nope, all of the changes are there upstream. Enabling it requires adding a build-dep on libsystemd-dev, though (this one I have tested). Also, purely stylistic, I think I'd prefer we make our own service file in debian/ rather than patching upstream's. Oh, ok. I'll switch to that instead. -- Arto Jantunen -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#762968: NMU patch for -1.1
Package: dnssec-trigger Followup-For: Bug #762968 The NMU is now in the archives and already supersseeded by normal uploads. Closing. -- tobi -- System Information: Debian Release: 8.0 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.16.0-4-amd64 (SMP w/4 CPU cores) Locale: LANG=de_DE.utf8, LC_CTYPE=de_DE.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#784386: gnome-shell doesn't show applications from /var/lib/menu-xdg/applications/menu-xdg/
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On 06-05-15 02:04, Michael Biebl wrote: Am 06.05.2015 um 00:51 schrieb Dennis van Dok: Shouldn't gnome shell be set up to read entries from /var/lib/menu-xdg/applications/menu-xdg as well? This is by design. What menu(-xdg) dumps there is basically unusable and makes a complete mess of the GNOME menu. So we decided to not show menu-xdg generated .desktop files. IIRC, KDE has gone the same way. OK, thanks for clearing that up. I couldn't find any information about how GNOME under Debian finds applications. Please file a bug against gltron to provide a proper .desktop file. It worked before, but now it's apparently broken. Dennis -BEGIN PGP SIGNATURE- Version: GnuPG v2 iQIcBAEBCAAGBQJVSdqvAAoJEN/62Bl2F+8ZBzEP/ifdVeOqOgs2jEzLNdezxTeA reDgEwXWmqyAnslB+dQ5Pjaxy4beHVrxnbI72pM6LfxDAiRu559ies/ZY+iZfnmq ZfpRWnH7bDtArWAMCRpztFC1FeSalvRBWLBq3oXL/176rORowXyiiyGrmH18td0v Pik4OAZz8jOl9n1Ykty+eC0nDINxQpMga7EqOwQ6daIJhNhqGUbYGj3hW4ktogYY Qk2q86uwNPebWaEu++xLok8bokouUD7VA2oZ6+SCJz7eKkkjG7iB+rDe2rEekGff tz35dePS1Iyp0s/Bvd3QzQKiGn7g7A5ok/dz8Avl4gd4JIX+a6I8ndfiXm8ZNtpC /We0+ZrXF0elGYf8G9HlAxD/ybtavbQj3COoHjOwnJOrDgbtxdqiDc2p2auCx/WW YM4EoAdYcq0CQv6Kj4FIcCsGtyT2su4NnojPdXg+V8vBVzqx6ci46AFvcrZfbf8K KE5A5hckKSQVGUfsZrlMx6QNtncDWbgmJNf53s1XmwMl0BLMD7esreNEz520hdhc zb3tPswCA310ope0718cPAS8XJr4sfWhiqzyhPF5Qalwnvn96L2crenqLaSSzdd6 5soQGM1DmYU1KPrANAs537fzjakOdcmuScES3jlgscruwV5rfmSrBf+jD0wTbfGz X6vWRp34nFcDa6ceHSdq =u0ba -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#784432: FTBS when build under /usr
Source: qtwebkit
Version: 2.3.4.dfsg-3
Severity: normal
Tags: patch
Hey,
When building qtwebkit in a directory under /usr (e.g. /usr/src) the following
compiler error occurs:
In file included from
/usr/src/packages/BUILD/qtwebkit-2.3.4.dfsg/Source/WebKit/qt/declarative/qdeclarativewebview_p.h:29:0,
from
/usr/src/packages/BUILD/qtwebkit-2.3.4.dfsg/Source/WebKit/qt/declarative/qdeclarativewebview.cpp:21:
../../../../include/QtWebKit/qgraphicswebview.h:1:81: fatal error:
../../../../../../../../../../Source/WebKit/qt/Api/qgraphicswebview.h: No such
file or directory
#include
../../../../../../../../../../Source/WebKit/qt/Api/qgraphicswebview.h
^
compilation terminated.
This turns out to be because syncqt-4.8 generated incorrect relative paths due
to this section of code:
sub fixPaths {
my ($file, $dir) = @_;
$dir =~ s=^$quoted_basedir/=$out_basedir/= if(!($basedir eq
$out_basedir));
dir being the full path to the source files, basedir /usr, when dir doesn't
start with /usr this is a noop, but if it is the /usr part gets replaced and
things break...
Patch attached to fix this
--- a/Tools/qmake/syncqt-4.8
+++ b/Tools/qmake/syncqt-4.8
@@ -353,7 +353,6 @@
##
sub fixPaths {
my ($file, $dir) = @_;
-$dir =~ s=^$quoted_basedir/=$out_basedir/= if(!($basedir eq $out_basedir));
$file =~ s=\\=/=g;
$dir =~ s=\\=/=g;
Bug#783606: [Pkg-ltsp-devel] Bug#783606: Host not saved into known_hosts
[Petr Šťastný] I just dug more deeply into this problem. First problem: I found that pam_sshauth reads /etc/ssh/ssh_known_hosts, which is not mentioned in manual page and I was not able to figure auth which known_hosts file is used. I had to have a look into source code. Good to hear that it is reading the global file. Second problem: pam_sshauth seems not to write anything into /etc/ssh/ssh_known_hosts although manual page states that If contacting a host for which we don't have an entry in known_hosts, ask, via the pam prompts, if you'd like to trust this host, and add it to your known_hosts file. The default will be to fail the authentication. I interpret this information as it should add the host into ssh_known_hosts when I say yes. But there is nothing about saving the host key in pam_sshauth's source code. Good to see that it is not writing in the global file. I suspect it should be made clear in the documentation. That global file should be updated out of band like you describe here: Third and main problem: pam_sshauth does not work with hashed known_hosts entries, which is default behavior in Debian Jessie (at least, I don't know the situation in previous releases). If I create /etc/ssh/ssh_known_hosts manually using the following command, it works: ssh-keyscan X.X.X.X /etc/ssh/ssh_known_hosts But this (which is Debian Jessie default) does not work (host name/address output is hashed) - pam_sshauth ignore these entries: ssh-keyscan -H X.X.X.X /etc/ssh/ssh_known_hosts I guess this is the real missing feature here. The pam module should understand the same global known_hosts file as the ssh client. I would also suggest to change the documentation to document that the ssh host to use MUST be listed in /etc/ssh/ssh_known_hosts, and remove the prompt about adding the host key to a file. -- Happy hacking Petter Reinholdtsen -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#783406: [Pkg-xfce-devel] Bug#783406: More info
Control: tag -1 moreinfo On mer., 2015-05-06 at 07:13 +0200, Raphaël Halimi wrote: Le 05/05/2015 22:05, Yves-Alexis Perez a écrit : If I can provide more useful info, please tell me how. Try to get a diff with logs from a working case? Alas, in my backups from wheezy I didn't find anything relevant. I can't find fprintd logs, apart of dbus activating the service, like : ./syslog:Apr 25 20:40:46 solaris dbus[3130]: [system] Activating service name='net.reactivated.Fprint' (using servicehelper) ./syslog:Apr 25 20:40:46 solaris dbus[3130]: [system] Successfully activated service 'net.reactivated.Fprint' Then try to investigate by downgrading relevant packages (like lightdm, pam modules or fprint libraries)? There's not much we can do here without that kind of information. Regards, -- Yves-Alexis signature.asc Description: This is a digitally signed message part
Bug#784424: ruby-test-unit: missing dependency on power_assert gem
Package: ruby-test-unit Version: 3.0.9-2 Severity: serious Hi, ruby-test-unit seems to miss a dependency on power_assert: $ ruby -e gem 'test-unit' /usr/lib/ruby/2.1.0/rubygems/dependency.rb:298:in `to_specs': Could not find 'power_assert' (= 0) among 15 total gem(s) (Gem::LoadError) from /usr/lib/ruby/2.1.0/rubygems/specification.rb:1295:in `block in activate_dependencies' from /usr/lib/ruby/2.1.0/rubygems/specification.rb:1284:in `each' from /usr/lib/ruby/2.1.0/rubygems/specification.rb:1284:in `activate_dependencies' from /usr/lib/ruby/2.1.0/rubygems/specification.rb:1266:in `activate' from /usr/lib/ruby/2.1.0/rubygems/core_ext/kernel_gem.rb:54:in `gem' from -e:1:in `main' This doesn't show up when doing: require 'test/unit' because of: (in /usr/lib/ruby/vendor_ruby/test/unit/assertions.rb) begin require 'power_assert' rescue LoadError, SyntaxError end I wonder if this should be added as a default test to all libraries? - Lucas -- System Information: Debian Release: 8.0 APT prefers stable APT policy: (990, 'stable'), (500, 'stable-updates'), (500, 'oldstable'), (300, 'unstable'), (150, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.19.0-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 Init: systemd (via /run/systemd/system) Versions of packages ruby-test-unit depends on: ii ruby1:2.1.5 ii ruby2.1 [ruby-interpreter] 2.1.5-2+deb8u1 ruby-test-unit recommends no packages. ruby-test-unit 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#783089: Workaround, amendum
Le 2015-05-05 18:56, Geert Stappers a écrit : On Tue, May 05, 2015 at 04:11:14PM +0200, jean-y...@lenhof.eu.org wrote: Hi, As a workaround, you can : - Boot on the Debian CD - Select Rescue - Change to a terminal - cd /tmp - ar x /cdrom/pool/main/l/linux/linux-image-3.16.0-4-amd64_3.16.7-ckt7-1_amd64.deb - xzcat data.tar.xz * - cd /tmp/lib/modules/3.16.0-4-amd64/kernel/drivers/md/ - insmod raid10.ko - insmod dm-raid.ko - change back to first console and select your root lv FWIW: I think that at '*' has to be something like tar xf data.tar Groeten Geert Stappers Hum...Hum... True that I forget something... my bad. This should be more something like this : xzcat data.tar.xz|tar xvf - Regards, JYL -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#783237: CVE-2014-9462
On May/06, Javi Merino wrote: I've prepared an upload for wheezy-security, find the diff below. Can I upload it to security-master? It looks fine to me. This one will need -sa as well. Cheers, --Seb -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#783459: dnsmasq: Wheezy regression caused by CVE-2015-3294/2.62-3+deb7u2 w/ bind-interfaces
Package: dnsmasq
Followup-For: Bug #783459
Dear Maintainer,
After upgrading to 2.62-3+deb7u2 on Wheezy/armel dnsmasq now fails to start
with:
root@yog-sothoth:~# dpkg -i dnsmasq*2.62-3+deb7u2*.deb
(Reading database ... 25941 files and directories currently installed.)
Preparing to replace dnsmasq 2.62-3+deb7u1 (using
dnsmasq_2.62-3+deb7u2_all.deb) ...
Unpacking replacement dnsmasq ...
Preparing to replace dnsmasq-base 2.62-3+deb7u1 (using
dnsmasq-base_2.62-3+deb7u2_armel.deb) ...
Unpacking replacement dnsmasq-base ...
Setting up dnsmasq-base (2.62-3+deb7u2) ...
Processing triggers for man-db ...
Setting up dnsmasq (2.62-3+deb7u2) ...
insserv: warning: current stop runlevel(s) (1) of script `dnsmasq'
overrides LSB defaults (0 1 6).
[] Restarting DNS forwarder and DHCP server: dnsmasq
dnsmasq: failed to set SO_REUSE{ADDR|PORT} on DHCP socket: Protocol not
available
failed!
invoke-rc.d: initscript dnsmasq, action restart failed.
root@yog-sothoth:~#
Downgrading back to 2.62-3+deb7u1 makes things work again.
Searching around there are various (mostly a few year old) reports of this
which are related to the use of the bind-interfaces option which I had enabled
in /etc/dnsmasq.conf since dnsmasq runs on a router with multiple interfaces.
For now I've disabled bind-interfaces, although I'm not entirely happy with
that since it exposes dnsmasq to traffic from the outside Internet, even if it
is to be discarded.
Ian.
-- System Information:
Debian Release: 7.8
APT prefers oldstable
APT policy: (990, 'oldstable'), (500, 'oldstable-updates')
Architecture: armel (armv5tel)
Kernel: Linux 3.2.0-4-kirkwood
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 dnsmasq depends on:
ii adduser 3.113+nmu3
ii dnsmasq-base 2.62-3+deb7u1
ii netbase 5.0
dnsmasq recommends no packages.
Versions of packages dnsmasq suggests:
pn resolvconf none
-- Configuration Files:
/etc/dnsmasq.conf changed:
interface=eth0
bind-interfaces
domain=hellion.org.uk
dhcp-range=192.168.1.128,192.168.1.255,12h
-- 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#784423: [xtrkcad] Wrong turnoutname
Package: xtrkcad Version: 1:4.0.2-2+b1 Severity: normal --- Please enter the report below this line. --- The Märklin right turnout 5119 is named Left Turnout R360 30°. This is very confusing, e.g. when creating a parts list. It probably should be Right Turnout R360 30°. I do not know if the issue is fixed in the current upstream version 4.2.0. Philipp --- System information. --- Architecture: amd64 Kernel: Linux 3.16.0-4-amd64 Debian Release: 8.0 500 unstableftp.de.debian.org 500 testing ftp.de.debian.org 1 experimentalftp.de.debian.org --- Package information. --- Depends (Version) | Installed ==-+- libatk1.0-0(= 1.12.4) | 2.14.0-1 libc6 (= 2.7) | libcairo2 (= 1.2.4) | libfontconfig1 (= 2.8.0) | libfreetype6(= 2.2.1) | libgdk-pixbuf2.0-0 (= 2.22.0) | libglib2.0-0 (= 2.16.0) | libgtk2.0-0 (= 2.8.0) | libpango1.0-0 (= 1.14.0) | libsoup2.4-1(= 2.4.0) | libwebkitgtk-1.0-0 (= 1.3.10) | libx11-6 | Package's Recommends field is empty. Package's Suggests field is empty. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#781121: totem: upstream bug
retitle 781121 totem - does not start on nvidia driver - X Window System error thanks
Bug#784303: mitmproxy: missing dependencies on python-configargparse, python-tornado = 4.0.2, python-netlib = 0.11.2
tag 784303 + confirmed
block 784303 779035
thanks
Ouch. I've ITP'ed python-configargparse, and will follow up on the
python-tornado front.
In the meantime, the version in testing is the best fallback option.
Cheers,
--Seb
On May/04, Vagrant Cascadian wrote:
Package: mitmproxy
Version: 0.11.3-1
Severity: serious
Justification: Policy 3.5
Thanks for maintaining mitmproxy!
Unfortunately, it's uninstallable as python-configargparse is a
dependency of mitmproxy, but is not yet available in the archive.
Even after manually building a local copy of python-cofigargparse, it
fails to run:
Traceback (most recent call last):
File /usr/bin/mitmproxy, line 2, in module
from libmproxy.main import mitmproxy
File /usr/lib/python2.7/dist-packages/libmproxy/main.py, line 6, in
module
from . import version, cmdline
File /usr/lib/python2.7/dist-packages/libmproxy/cmdline.py, line 6, in
module
from . import filt, utils, version
File /usr/lib/python2.7/dist-packages/libmproxy/filt.py, line 37, in
module
from .protocol.http import decoded
File /usr/lib/python2.7/dist-packages/libmproxy/protocol/__init__.py,
line 1, in module
from .primitives import *
File /usr/lib/python2.7/dist-packages/libmproxy/protocol/primitives.py,
line 6, in module
from ..proxy.connection import ClientConnection, ServerConnection
File /usr/lib/python2.7/dist-packages/libmproxy/proxy/__init__.py, line
1, in module
from .primitives import *
File /usr/lib/python2.7/dist-packages/libmproxy/proxy/primitives.py, line
2, in module
from netlib import socks
ImportError: cannot import name socks
As it requires a versioned dependency on python-netlib =0.11.2.
But that's still not enough to fix the issue:
Traceback (most recent call last):
File /usr/bin/mitmproxy, line 3, in module
mitmproxy()
File /usr/lib/python2.7/dist-packages/libmproxy/main.py, line 79, in
mitmproxy
from . import console
File /usr/lib/python2.7/dist-packages/libmproxy/console/__init__.py, line
5, in module
from .. import controller, utils, flow, script, proxy
File /usr/lib/python2.7/dist-packages/libmproxy/flow.py, line 13, in
module
from .onboarding import app
File /usr/lib/python2.7/dist-packages/libmproxy/onboarding/app.py, line
14, in module
class Adapter(tornado.wsgi.WSGIAdapter):
AttributeError: 'module' object has no attribute 'WSGIAdapter'
As mitmproxy requires a versioned dependency on python-tornado =4.0.2
which is also not yet available in the archive...
These and possibly other versioned dependencies are defined in
setup.py:
deps = {
netlib=%s, %s % (version.MINORVERSION, version.NEXT_MINORVERSION),
pyasn10.1.2,
pyOpenSSL=0.14,
tornado=4.0.2,
configargparse=0.9.3
}
script_deps = {
mitmproxy: {
urwid=1.1,
lxml=3.3.6,
Pillow=2.3.0,
},
mitmdump: set()
}
Though it looks like all the other versioned deps defined there are
available in Debian.
live well,
vagrant
-- System Information:
Debian Release: 8.0
APT prefers stable-updates
APT policy: (500, 'stable-updates'), (500, 'stable'), (120, 'unstable'),
(1, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386, armhf
Kernel: Linux 3.16.0-4-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_US.utf8, LC_CTYPE=en_US.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
Versions of packages mitmproxy depends on:
ii python 2.7.9-1
ii python-configargparse 0.9.3-1~20150222~2
ii python-flask 0.10.1-2
ii python-imaging 2.6.1-2
ii python-lxml3.4.0-1
ii python-netlib 0.10-2
ii python-openssl 0.14-1
ii python-pil 2.6.1-2
ii python-pyasn1 0.1.7-1
ii python-tornado 3.2.2-1.1
ii python-urwid 1.2.1-2+b1
mitmproxy recommends no packages.
mitmproxy 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#761403: CAP_KILL
Peter Palfrader wea...@debian.org writes: On Wed, 06 May 2015, Arto Jantunen wrote: ++Type = forking I'm not sure why we'd continue to detach when running under systemd. My plan was to do this in stages, starting with a service file that works the same way as the current init script, working with the same configuration that is currently used. I was planning to move to Type=notify + User=debian-tor + RuntimeDirectory=/var/run/tor in the service file, and a separate config instead of the current tor-service-defaults-torrc (without PidFile, RunAsDaemon and User) as the next step after that. -- Arto Jantunen -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#784426: smtm: dies at start
Package: smtm
Version: 1.6.10
Severity: grave
Justification: renders package unusable
Dear Maintainer,
Since the middle of april 2015 smtm stopped working.
Tested on different machines (wheezy and jessie) and two different users.
at launch the program stops without starting the tk inteface, logging the
following errors:
Use of uninitialized value in join or string at /usr/bin/smtm line 435.
Use of uninitialized value in uc at /usr/bin/smtm line 435.
Use of uninitialized value in join or string at /usr/bin/smtm line 435.
Use of uninitialized value in uc at /usr/bin/smtm line 435.
Use of uninitialized value in join or string at /usr/bin/smtm line 435.
Use of uninitialized value in uc at /usr/bin/smtm line 435.
Use of uninitialized value in join or string at /usr/bin/smtm line 435.
Use of uninitialized value in uc at /usr/bin/smtm line 435.
Use of uninitialized value in join or string at /usr/bin/smtm line 435.
Use of uninitialized value in uc at /usr/bin/smtm line 435.
Use of uninitialized value in join or string at /usr/bin/smtm line 435.
Use of uninitialized value in uc at /usr/bin/smtm line 435.
Use of uninitialized value in join or string at /usr/bin/smtm line 435.
Use of uninitialized value in uc at /usr/bin/smtm line 435.
Use of uninitialized value in join or string at /usr/bin/smtm line 435.
Use of uninitialized value in uc at /usr/bin/smtm line 435.
Use of uninitialized value in join or string at /usr/bin/smtm line 435.
Use of uninitialized value in uc at /usr/bin/smtm line 435.
Use of uninitialized value in join or string at /usr/bin/smtm line 435.
Use of uninitialized value in uc at /usr/bin/smtm line 435.
Use of uninitialized value in join or string at /usr/bin/smtm line 435.
Use of uninitialized value in uc at /usr/bin/smtm line 435.
Use of uninitialized value in join or string at /usr/bin/smtm line 435.
Use of uninitialized value in uc at /usr/bin/smtm line 435.
Use of uninitialized value in join or string at /usr/bin/smtm line 435.
Use of uninitialized value in uc at /usr/bin/smtm line 435.
Use of uninitialized value in join or string at /usr/bin/smtm line 435.
Use of uninitialized value in uc at /usr/bin/smtm line 435.
Use of uninitialized value in split at /usr/bin/smtm line 495.
Use of uninitialized value in split at /usr/bin/smtm line 495.
Use of uninitialized value in split at /usr/bin/smtm line 495.
Use of uninitialized value in split at /usr/bin/smtm line 495.
Use of uninitialized value in split at /usr/bin/smtm line 495.
Use of uninitialized value $arr[0] in uc at /usr/bin/smtm line 478.
Use of uninitialized value in hash element at /usr/bin/smtm line 486.
Use of uninitialized value in split at /usr/bin/smtm line 495.
Use of uninitialized value in split at /usr/bin/smtm line 495.
Use of uninitialized value in split at /usr/bin/smtm line 495.
Use of uninitialized value in split at /usr/bin/smtm line 495.
Argument }table {font-size:inherit isn't numeric in multiplication (*) at
/usr/bin/smtm line 488.
Argument text-align:center isn't numeric in multiplication (*) at
/usr/bin/smtm line 489.
Argument clean isn't numeric in multiplication (*) at /usr/bin/smtm line 491.
Use of uninitialized value in split at /usr/bin/smtm line 495.
Use of uninitialized value in split at /usr/bin/smtm line 495.
Use of uninitialized value in split at /usr/bin/smtm line 495.
Use of uninitialized value in split at /usr/bin/smtm line 495.
Use of uninitialized value in split at /usr/bin/smtm line 495.
Use of uninitialized value in split at /usr/bin/smtm line 495.
Use of uninitialized value in split at /usr/bin/smtm line 495.
Use of uninitialized value in split at /usr/bin/smtm line 495.
Use of uninitialized value in split at /usr/bin/smtm line 495.
Use of uninitialized value in split at /usr/bin/smtm line 495.
Argument }p isn't numeric in multiplication (*) at /usr/bin/smtm line 488.
Argument vertical-align:middle isn't numeric in multiplication (*) at
/usr/bin/smtm line 489.
Argument clean isn't numeric in multiplication (*) at /usr/bin/smtm line 491.
Use of uninitialized value in split at /usr/bin/smtm line 495.
Use of uninitialized value in split at /usr/bin/smtm line 495.
Use of uninitialized value in split at /usr/bin/smtm line 495.
Use of uninitialized value in split at /usr/bin/smtm line 495.
Argument form {margin:0 isn't numeric in numeric gt () at /usr/bin/smtm
line 595.
Argument font:x-small isn't numeric in numeric gt () at /usr/bin/smtm line
595.e of uninitialized value in string comparison (cmp) at /usr/bin/smtm line
351.
Use of uninitialized value in string comparison (cmp) at /usr/bin/smtm line
351.
Use of uninitialized value in string comparison (cmp) at /usr/bin/smtm line
351.
Use of uninitialized value in string comparison (cmp) at /usr/bin/smtm line
351.
Use of uninitialized value $b[0] in hash element at /usr/bin/smtm line 349.
Use of uninitialized value in string comparison (cmp) at /usr/bin/smtm line
351.
Use of uninitialized value in string comparison (cmp) at /usr/bin/smtm line
351.
Bug#773462: Second data point confirming the described issue
Hi, I experienced this issue as well, in the final jessie release. Same version 0.9.3.4-2 of plasma-nm that was in the original bug report, but network-manager is 0.9.10.0-7 rather than 0.9.10.0-3. Running jessie and jessie-updates on amd64 (with i386 known to dpkg). The mentioned workaround of setting the password in the Connection editor settings window succeeds for me, even though it was failing for the original submitter on December 18 after previously working. The difference in network-manager version numbers probably explain this. As in the original report, I have KDE configured not to use kwallet. Version sanity check: I've confirmed with apt-show-versions that all packages on my system match the up-to-date versions from jessie or jessie-updates, with a very few clearly irrelevant exceptions (e.g. google-chrome and a 3.18 kernel from pre-jessie Debian experimental). - Jimmy Kaplowitz ji...@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#714484: brasero: wrong size calculation on some audio files in audio project.
Package: brasero Version: 3.11.4-1.1 Followup-For: Bug #714484 Dear Maintainer, *** Reporter, please consider answering these questions, where appropriate *** * What led up to the situation? trying to make audio cd from flac files * What exactly did you do (or not do) that was effective (or ineffective)? nothing, i don't know why those files get wrong time * What was the outcome of this action? cd corupted * What outcome did you expect instead? to get time properly and burn correctly. audio project: some audio get wrong time, about 6 sec. so capacity of disc get wrong so burning says successfully but get corupted, some files get written, some only those 6 sec and others not at all. -- System Information: Debian Release: 8.0 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 3.16.0-4-amd64 (SMP w/2 CPU cores) Locale: LANG=en_IE.utf8, LC_CTYPE=en_IE.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages brasero depends on: ii brasero-common 3.11.4-1.1 ii gnome-icon-theme3.12.0-1 ii gstreamer1.0-plugins-base 1.4.4-2 ii gvfs1.22.2-1 ii libatk1.0-0 2.14.0-1 ii libbrasero-media3-1 3.11.4-1.1 ii libc6 2.19-18 ii libcairo-gobject2 1.14.0-2.1 ii libcairo2 1.14.0-2.1 ii libgdk-pixbuf2.0-0 2.31.1-2+b1 ii libglib2.0-02.42.1-1 ii libgstreamer-plugins-base1.0-0 1.4.4-2 ii libgstreamer1.0-0 1.4.4-2 ii libgtk-3-0 3.14.5-1 ii libice6 2:1.0.9-1+b1 ii libnautilus-extension1a 3.14.1-2 ii libpango-1.0-0 1.36.8-3 ii libpangocairo-1.0-0 1.36.8-3 ii libsm6 2:1.2.2-1+b1 ii libtotem-plparser18 3.10.3-1 ii libtracker-sparql-1.0-0 1.2.4-2 ii libxml2 2.9.1+dfsg1-5 Versions of packages brasero recommends: ii brasero-cdrkit 3.11.4-1.1 ii yelp3.14.1-1 Versions of packages brasero suggests: pn libdvdcss2 none ii tracker 1.2.4-2 pn vcdimager 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#784428: mlocates contain spurious temp file /var/lib/mlocate/mlocate.db.######
Package: mlocate
Version: 0.26-1
Severity: minor
Dear Maintainer,
Mlocate'db lists it's temporary version of itselfs
it found while building itself ('mlocate -ception').
This precise file shouldn't be listed in the database.
tchet@antec:~/git/cruft-ng$ locate mlocate.db
/usr/share/man/man5/mlocate.db.5.gz
/var/lib/mlocate/mlocate.db
/var/lib/mlocate/mlocate.db.bgMIIs
Alexandre
-- System Information:
Debian Release: stretch/sid
APT prefers testing
APT policy: (501, 'testing'), (450, 'unstable'), (400, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 3.19.0-trunk-amd64 (SMP w/6 CPU cores)
Locale: LANG=fr_BE.UTF-8, LC_CTYPE=fr_BE.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
Versions of packages mlocate depends on:
ii adduser 3.113+nmu3
ii libc62.19-18
mlocate recommends no packages.
mlocate suggests no packages.
-- Configuration Files:
/etc/updatedb.conf changed:
PRUNE_BIND_MOUNTS=yes
PRUNEPATHS=/tmp /media
PRUNEFS=NFS nfs nfs4 rpc_pipefs afs binfmt_misc proc smbfs autofs iso9660
ncpfs coda devpts ftpfs devfs devtmpfs mfs shfs sysfs cifs lustre tmpfs usbfs
udf fuse.glusterfs fuse.sshfs curlftpfs
-- 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#784422: ITP: diaspora-gems-compat -- provide gems for diaspora when corresponding deb package is incompatible
package: wnpp severity: wishlist currently bootstrap-sass in debian is 3.x and which is incompatible with bootstrap-sass 2.x. diaspora upstream is planning to port to 3.x but it will take time. This is a temporary arrangement. Maintaining ruby-bootstrap2 is not worth the effort. signature.asc Description: OpenPGP digital signature
Bug#782364: linux-image-3.16.0-4-armmp: please configure drivers for both Cubox i4pro real time clocks
On Sat, 2015-05-02 at 17:21 +0100, Ian Campbell wrote: We typically build RTCs statically (for this sort of reason) so it seems like the right thing for us to do here is to build both in. Which I've now done in SVN. Rick, please test the next upload. Also, Rick, I'm getting messages from my MTA about not being able to deliver to rbtho...@cube.rcthomas.org, it's been queuing/retrying since the weekend and says I shouldn't worry, but I thought I'd mention it since I was here. Exim logs say: 2015-05-06 06:48:50 1YoZqj-0002JC-G0 == rbtho...@cube.rcthomas.org R=dnslookup T=remote_smtp defer (-53): retry time not reached for any host Hopefully you will see this via some other route. Ian. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#783984: mkvinfo: src/EbmlElement.cpp:472: ...: Assertion `ElementPosition SizePosition' failed.
Hey, Moritz are you aware of this bug ? No. I'd appreciate it if you or the original poster could file an issue in my issue tracker on Github[1] so that I don't forget about it. Note that the file is not a valid Matroska file. For one, it contains an empty EBML head, meaning that it doesn't even contain a DocType. mkvinfo shouldn't crash on such files, of course, but be prepared for the fix to simply print »This is not a Matroska file and can therefore not be read by this program.« :) Kind regards, mosu pgpLvFJsevMID.pgp Description: PGP signature
Bug#761403: CAP_KILL
On Wed, 06 May 2015, Arto Jantunen wrote: Peter Palfrader wea...@debian.org writes: On Wed, 06 May 2015, Arto Jantunen wrote: ++Type = forking I'm not sure why we'd continue to detach when running under systemd. My plan was to do this in stages, starting with a service file that works the same way as the current init script, working with the same configuration that is currently used. I was planning to move to Type=notify + User=debian-tor + RuntimeDirectory=/var/run/tor in the service file, and a separate config instead of the current tor-service-defaults-torrc (without PidFile, RunAsDaemon and User) as the next step after that. I assume moving the User to the service file would work only because we give Tor CAP_NET_BIND_SERVICE, right? Why would we want to set RuntimeDirectory? Having Type=notify instead of simple will require modifying Tor accordingly, correct? Also, purely stylistic, I think I'd prefer we make our own service file in debian/ rather than patching upstream's. Thanks for your help, weasel -- | .''`. ** Debian ** Peter Palfrader | : :' : The universal http://www.palfrader.org/ | `. `' Operating System | `-http://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#784419: ITP: php-math-biginteger -- Usage: /usr/share/pkg-php-tools/scripts/phppkginfo [options] package|package_type|channel|summary|description|maintainers dir|package.xml /usr/share/pkg-
Package: wnpp Severity: wishlist Owner: Mathieu Parent math.par...@gmail.com Package name: Usage: /usr/share/pkg-php-tools/scripts/phppkginfo [options] package|package_type|channel|summary|description|maintainers dir|package.xml /usr/share/pkg-php-tools/scripts/phppkginfo [options] date|version|license|changelog|all|hasphpscript dir|package.xml /usr/share/pkg-php-tools/scripts/phppkginfo [options] debian_deps dir|package.xml /usr/share/pkg-php-tools/scripts/phppkginfo [options] debian_pkgname channel_url pear_name /usr/share/pkg-php-tools/scripts/phppkginfo [options] debian_version version /usr/share/pkg-php-tools/scripts/phppkginfo [options] channel_name|channel_summary|channel_alias channel.xml /usr/share/pkg-php-tools/scripts/phppkginfo [options] composer_... dir|composer.json PEAR package commands: package - Name of package package_type- Type of package (php|extsrc|extbin|zendextsrc|zendextbin|bundle|false) channel - PEAR channel URL summary - Short summary of package description - Long description of package maintainers - Comma separated list of maintainers date- Date of release version - Version of package license - License of package changelog - Full changelog of package all - print_r() of complete package file hasphpscript- Check if package contains files of type 'script' debian_deps - Print dependencies as Debian control fields debian_pkgname - Translate a PEAR package name to a Debian package name debian_version - Translate a PEAR version to a Debian version PEAR channel commands: channel_name- Get channel name channel_summary - Get channel summary channel_alias - Get channel alias Composer commands: composer_name- Get Composer package name composer_description - Get Composer package description composer_version - Get Composer package version composer_type- Get Composer package type composer_keywords- Get Composer package keywords composer_homepage- Get Composer package homepage composer_time- Get Composer package time composer_license - Get Composer package license composer_authors - Get Composer package authors composer_support - Get Composer package support composer_require - Get Composer package require composer_require_dev - Get Composer package require_dev composer_conflict- Get Composer package conflict composer_replace - Get Composer package replace composer_provide - Get Composer package provide composer_suggest - Get Composer package suggest composer_autoload- Get Composer package autoload composer_config - Get Composer package config composer_substvars - Debian substvars from Composer package arguments: dir - Directory containing package.xml, package2.xml or composer.json file options: -d - print debug to STDERR Version : Usage: /usr/share/pkg-php-tools/scripts/phppkginfo [options] package|package_type|channel|summary|description|maintainers dir|package.xml /usr/share/pkg-php-tools/scripts/phppkginfo [options] date|version|license|changelog|all|hasphpscript dir|package.xml /usr/share/pkg-php-tools/scripts/phppkginfo [options] debian_deps dir|package.xml /usr/share/pkg-php-tools/scripts/phppkginfo [options] debian_pkgname channel_url pear_name /usr/share/pkg-php-tools/scripts/phppkginfo [options] debian_version version /usr/share/pkg-php-tools/scripts/phppkginfo [options] channel_name|channel_summary|channel_alias channel.xml /usr/share/pkg-php-tools/scripts/phppkginfo [options] composer_... dir|composer.json PEAR package commands: package - Name of package package_type- Type of package (php|extsrc|extbin|zendextsrc|zendextbin|bundle|false) channel - PEAR channel URL summary - Short summary of package description - Long description of package maintainers - Comma separated list of maintainers date- Date of release version - Version of package license - License of package changelog - Full changelog of package all - print_r() of complete package file hasphpscript- Check if package contains files of type 'script' debian_deps - Print dependencies as Debian control fields debian_pkgname - Translate a PEAR package name to a Debian package name debian_version - Translate a PEAR version to a Debian version PEAR channel commands: channel_name- Get channel name channel_summary - Get channel summary channel_alias - Get channel alias Composer commands: composer_name- Get Composer package name composer_description - Get Composer package description composer_version - Get Composer package version composer_type- Get Composer package type
Bug#784420: ITP: php-phpseclib-sourceforge-file-asn1 -- Usage: /usr/share/pkg-php-tools/scripts/phppkginfo [options] package|package_type|channel|summary|description|maintainers dir|package.xml
Package: wnpp Severity: wishlist Owner: Mathieu Parent math.par...@gmail.com Package name: Usage: /usr/share/pkg-php-tools/scripts/phppkginfo [options] package|package_type|channel|summary|description|maintainers dir|package.xml /usr/share/pkg-php-tools/scripts/phppkginfo [options] date|version|license|changelog|all|hasphpscript dir|package.xml /usr/share/pkg-php-tools/scripts/phppkginfo [options] debian_deps dir|package.xml /usr/share/pkg-php-tools/scripts/phppkginfo [options] debian_pkgname channel_url pear_name /usr/share/pkg-php-tools/scripts/phppkginfo [options] debian_version version /usr/share/pkg-php-tools/scripts/phppkginfo [options] channel_name|channel_summary|channel_alias channel.xml /usr/share/pkg-php-tools/scripts/phppkginfo [options] composer_... dir|composer.json PEAR package commands: package - Name of package package_type- Type of package (php|extsrc|extbin|zendextsrc|zendextbin|bundle|false) channel - PEAR channel URL summary - Short summary of package description - Long description of package maintainers - Comma separated list of maintainers date- Date of release version - Version of package license - License of package changelog - Full changelog of package all - print_r() of complete package file hasphpscript- Check if package contains files of type 'script' debian_deps - Print dependencies as Debian control fields debian_pkgname - Translate a PEAR package name to a Debian package name debian_version - Translate a PEAR version to a Debian version PEAR channel commands: channel_name- Get channel name channel_summary - Get channel summary channel_alias - Get channel alias Composer commands: composer_name- Get Composer package name composer_description - Get Composer package description composer_version - Get Composer package version composer_type- Get Composer package type composer_keywords- Get Composer package keywords composer_homepage- Get Composer package homepage composer_time- Get Composer package time composer_license - Get Composer package license composer_authors - Get Composer package authors composer_support - Get Composer package support composer_require - Get Composer package require composer_require_dev - Get Composer package require_dev composer_conflict- Get Composer package conflict composer_replace - Get Composer package replace composer_provide - Get Composer package provide composer_suggest - Get Composer package suggest composer_autoload- Get Composer package autoload composer_config - Get Composer package config composer_substvars - Debian substvars from Composer package arguments: dir - Directory containing package.xml, package2.xml or composer.json file options: -d - print debug to STDERR Version : Usage: /usr/share/pkg-php-tools/scripts/phppkginfo [options] package|package_type|channel|summary|description|maintainers dir|package.xml /usr/share/pkg-php-tools/scripts/phppkginfo [options] date|version|license|changelog|all|hasphpscript dir|package.xml /usr/share/pkg-php-tools/scripts/phppkginfo [options] debian_deps dir|package.xml /usr/share/pkg-php-tools/scripts/phppkginfo [options] debian_pkgname channel_url pear_name /usr/share/pkg-php-tools/scripts/phppkginfo [options] debian_version version /usr/share/pkg-php-tools/scripts/phppkginfo [options] channel_name|channel_summary|channel_alias channel.xml /usr/share/pkg-php-tools/scripts/phppkginfo [options] composer_... dir|composer.json PEAR package commands: package - Name of package package_type- Type of package (php|extsrc|extbin|zendextsrc|zendextbin|bundle|false) channel - PEAR channel URL summary - Short summary of package description - Long description of package maintainers - Comma separated list of maintainers date- Date of release version - Version of package license - License of package changelog - Full changelog of package all - print_r() of complete package file hasphpscript- Check if package contains files of type 'script' debian_deps - Print dependencies as Debian control fields debian_pkgname - Translate a PEAR package name to a Debian package name debian_version - Translate a PEAR version to a Debian version PEAR channel commands: channel_name- Get channel name channel_summary - Get channel summary channel_alias - Get channel alias Composer commands: composer_name- Get Composer package name composer_description - Get Composer package description composer_version - Get Composer package version composer_type- Get Composer package type
Bug#784418: ITP: php-horde-managesieve -- Client library for ManageSieve
Package: wnpp Severity: wishlist Owner: Mathieu Parent math.par...@gmail.com Package name: Horde_ManageSieve Version : 1.0.0alpha1 Upstream Author : Jan Schneider URL : http://horde.org/ License : BSD Programming Lang: PHP Description : Client library for ManageSieve This library implements the ManageSieve protocol (RFC 5804). I'm packaging this as part of Horde5 packaging. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#784417: ITP: php-horde-idna -- IDNA backend normalization package
Package: wnpp Severity: wishlist Owner: Mathieu Parent math.par...@gmail.com Package name: Horde_Idna Version : 1.0.4 Upstream Author : Michael Slusarz URL : http://horde.org/ License : BSD-2-Clause Programming Lang: PHP Description : IDNA backend normalization package Normalized access to various backends providing IDNA (Internationalized Domain Names in Applications) support. I'm packaging this as part of Horde5 packaging. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#781121: totem: upstream bug
forwarded 781121 https://bugzilla.gnome.org/show_bug.cgi?id=747489 tag 781121 upstream thanks
Bug#784425: xsd: [xsd] FTBS on hurd due to PATH_MAX
Source: xsd Version: 4.0.0-1 Severity: wishlist Tags: newcomer User: debian-h...@lists.debian.org Usertags: hurd Dear Maintainer, Please provide a patch to enable building on hurd, even if it not a release arch. Thanks! (Tagging as newcomer, as to my experience PTAH_MAX issues are suitable for this.) See https://www.gnu.org/software/hurd/community/gsoc/project_ideas/maxpath.html and http://www.gnu.org/software/hurd/hurd/porting/guidelines.html for more information about PATH_MAX and other portability issued. (Tagging as newcomer, as to my experience PTAH_MAX issues are suitable for this.) Thanks! -- tobi -- System Information: Debian Release: 8.0 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.16.0-4-amd64 (SMP w/4 CPU cores) Locale: LANG=de_DE.utf8, LC_CTYPE=de_DE.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#784427: virt-manager: unsupported configuration: spicevmc not supported in this QEMU binary
Package: virt-manager
Version: 1:1.0.1-5
Severity: normal
Tags: upstream
Dear Maintainer,
virt-manager cannot create VMs when connected to some older libvirt-bin
versions due to the lack of configuration options to chose vnc over spice.
I'm using virt-manager in jessie to adminstrate an Ubuntu 12.04 libvirt-bin
0.9.8-2ubuntu17.20. The older libvirt installation does not yet support spice.
I used virt-manager to successfully connect via ssh+qemu and I can successcully
start/stop those VMs. But when attempting to create a new one:
Connection - New)
Connection: myserver (QEMU/KVM)
Chose ho you would like to install the operating system: Local install media
(ISO image or CDROM)
Use ISO image: /var/lib/libvirt/images/debian-8.0.0-amd64-netinst.iso
OS type: Linux
Version: Debian Wheezy (od later)
Memory (RAM): 1024
CPUs: 1
Enable storage for this virtual machine: True
Select managed or other existing storage: /dev/myvgname/mylvname
I get:
Unable to complete install: 'unsupported configuration: spicevmc not supported
in this QEMU binary'
Traceback (most recent call last):
File /usr/share/virt-manager/virtManager/asyncjob.py, line 91, in cb_wrapper
callback(asyncjob, *args, **kwargs)
File /usr/share/virt-manager/virtManager/create.py, line 1787, in do_install
guest.start_install(meter=meter)
File /usr/share/virt-manager/virtinst/guest.py, line 403, in start_install
noboot)
File /usr/share/virt-manager/virtinst/guest.py, line 467, in _create_guest
dom = self.conn.createLinux(start_xml or final_xml, 0)
File /usr/lib/python2.7/dist-packages/libvirt.py, line 3440, in createLinux
if ret is None:raise libvirtError('virDomainCreateLinux() failed',
conn=self)
libvirtError: unsupported configuration: spicevmc not supported in this QEMU
binary
I am aware that the libvirt server does not support spice but I was not able to
select vnc as the graphics configuration. I also noticed that I was never
asked for the name of the vm-entry, but I guess that would be another bug
report.
I suppose that this is an upstream issue, so I have tagged the report as such,
but I haven't verified it since I'm a bit at a loss on how I wold successfully
install an upstream version of virt-manager with the correct versions of it's
dependancies.
I believe the fix would be to add the configuration options the UI to
explicitly set the graphics settings. I'm not sure how to go about the channel
settings which locally also refer to spice settings, but do not appear in the
setting of the older server.
*** End of the template - remove these template lines ***
-- System Information:
Debian Release: 8.0
APT prefers stable-updates
APT policy: (500, 'stable-updates'), (500, 'stable')
Architecture: amd64 (x86_64)
Kernel: Linux 3.16.0-4-amd64 (SMP w/8 CPU cores)
Locale: LANG=de_AT.utf8, LC_CTYPE=de_AT.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
Versions of packages virt-manager depends on:
ii dconf-gsettings-backend [gsettings-backend] 0.22.0-1
ii gconf2 3.2.6-3
ii gir1.2-gtk-3.0 3.14.5-1
ii gir1.2-gtk-vnc-2.0 0.5.3-1.3
ii gir1.2-libvirt-glib-1.0 0.1.9-4
ii gir1.2-vte-2.90 1:0.36.3-1
ii librsvg2-common 2.40.5-1
ii python-dbus 1.2.0-2+b3
ii python-gi3.14.0-1
ii python-gi-cairo 3.14.0-1
ii python-ipaddr2.1.11-2
ii python-libvirt 1.2.9-1
ii python-urlgrabber3.9.1-4.1
pn python2.7:anynone
pn python:any none
ii virtinst 1:1.0.1-5
Versions of packages virt-manager recommends:
ii gir1.2-spice-client-gtk-3.0 0.25-1+b1
ii gnome-icon-theme 3.12.0-1
ii libvirt-daemon-system1.2.9-9
Versions of packages virt-manager suggests:
ii gnome-keyring3.14.0-1+b1
ii python-gnomekeyring 2.32.0+dfsg-3
pn python-guestfs none
pn ssh-askpass none
ii virt-viewer 1.0-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#783686:
Attached a debdiff to fix this bug. You can also grab directly the build on DebOMatic if you want. http://debomatic-i386.debian.net/distribution#unstable/llvm-toolchain-3.4/3.4.2-14/buildlog or here http://debomatic-amd64.debian.net/distribution#unstable/llvm-toolchain-3.4/3.4.2-14 cheers, Gianfranco debdiff Description: Binary data
Bug#783089: Workaround, amendum
On Wed, May 06, 2015 at 10:01:29AM +0200, jean-y...@lenhof.eu.org wrote: Le 2015-05-05 18:56, Geert Stappers a écrit: FWIW: I think that at '*' has to be something like tar xf data.tar Hum...Hum... True that I forget something... my bad. This should be more something like this : xzcat data.tar.xz | tar xvf - Yes. Minor advice make it xzcat data.tar.xz | tar xf - So without the verbose option. Groeten Geert Stappers -- Leven en laten leven -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#757633: Edit blueman-sendto to kill obexd
To terminate obexd after file transfer to make obex-data-server receive again, add to the blueman-master/apps/blueman-sendto the following: from subprocess import check_output class SendTo: def do_send(self): def on_result(sender, res): ret = check_output([pidof,obexd]) os.system(kill + ret) Gtk.main_quit() -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#783089: Workaround
jean-y...@lenhof.eu.org jean-y...@lenhof.eu.org (2015-05-06): Yep, I think so... I'm looking at it now. The question is how to rebuilt a debian CD after. Will a replacement of kernel package and udeb kernel package in the pool/l/linux will be sufficient ? You're going to end up with GPG check issues if you do so. If not is there a description of how to rebuilt the debian CD anywhere? I'd suggest, assuming you're working on jessie: 1. debcheckout debian-installer 2. install build-depends 3. drop updated kernel udebs under build/localudebs 4. build a monolithic image with: make -C build build_monolithic USE_UDEBS_FROM=jessie 5. check in build/dest/MANIFEST.udebs that the said udebs were successfully used during the build 6. use the generated build/dest/monolithic/mini.iso Moreover, I think that dm-thin-pool.ko, dm-persistent-data.ko, and dm-bio-prison.ko should also be added to have thin provisionning support in rescue mode/during installation. (TBH I'm not familiar with all those things.) Mraw, KiBi. signature.asc Description: Digital signature
Bug#784426: smtm: dies at start
On 6 May 2015 at 09:25, Ivan Rossi wrote:
| Package: smtm
| Version: 1.6.10
| Severity: grave
| Justification: renders package unusable
|
| Dear Maintainer,
|
|
| Since the middle of april 2015 smtm stopped working.
I doubt the middle of April part.
Finance::YahooQuote needed, and got, a fix on April 29, thanks to a
contributed patch. Please see
http://dirk.eddelbuettel.com/blog/2015/04/29#yahooquote_0.25
and adjust YahooQuote.pm accordingly, and then report back. Over here, smtm
works fine with it.
Dirk
| Tested on different machines (wheezy and jessie) and two different users.
|
| at launch the program stops without starting the tk inteface, logging the
| following errors:
|
|
| Use of uninitialized value in join or string at /usr/bin/smtm line 435.
| Use of uninitialized value in uc at /usr/bin/smtm line 435.
| Use of uninitialized value in join or string at /usr/bin/smtm line 435.
| Use of uninitialized value in uc at /usr/bin/smtm line 435.
| Use of uninitialized value in join or string at /usr/bin/smtm line 435.
| Use of uninitialized value in uc at /usr/bin/smtm line 435.
| Use of uninitialized value in join or string at /usr/bin/smtm line 435.
| Use of uninitialized value in uc at /usr/bin/smtm line 435.
| Use of uninitialized value in join or string at /usr/bin/smtm line 435.
| Use of uninitialized value in uc at /usr/bin/smtm line 435.
| Use of uninitialized value in join or string at /usr/bin/smtm line 435.
| Use of uninitialized value in uc at /usr/bin/smtm line 435.
| Use of uninitialized value in join or string at /usr/bin/smtm line 435.
| Use of uninitialized value in uc at /usr/bin/smtm line 435.
| Use of uninitialized value in join or string at /usr/bin/smtm line 435.
| Use of uninitialized value in uc at /usr/bin/smtm line 435.
| Use of uninitialized value in join or string at /usr/bin/smtm line 435.
| Use of uninitialized value in uc at /usr/bin/smtm line 435.
| Use of uninitialized value in join or string at /usr/bin/smtm line 435.
| Use of uninitialized value in uc at /usr/bin/smtm line 435.
| Use of uninitialized value in join or string at /usr/bin/smtm line 435.
| Use of uninitialized value in uc at /usr/bin/smtm line 435.
| Use of uninitialized value in join or string at /usr/bin/smtm line 435.
| Use of uninitialized value in uc at /usr/bin/smtm line 435.
| Use of uninitialized value in join or string at /usr/bin/smtm line 435.
| Use of uninitialized value in uc at /usr/bin/smtm line 435.
| Use of uninitialized value in join or string at /usr/bin/smtm line 435.
| Use of uninitialized value in uc at /usr/bin/smtm line 435.
| Use of uninitialized value in split at /usr/bin/smtm line 495.
| Use of uninitialized value in split at /usr/bin/smtm line 495.
| Use of uninitialized value in split at /usr/bin/smtm line 495.
| Use of uninitialized value in split at /usr/bin/smtm line 495.
| Use of uninitialized value in split at /usr/bin/smtm line 495.
| Use of uninitialized value $arr[0] in uc at /usr/bin/smtm line 478.
| Use of uninitialized value in hash element at /usr/bin/smtm line 486.
| Use of uninitialized value in split at /usr/bin/smtm line 495.
| Use of uninitialized value in split at /usr/bin/smtm line 495.
| Use of uninitialized value in split at /usr/bin/smtm line 495.
| Use of uninitialized value in split at /usr/bin/smtm line 495.
| Argument }table {font-size:inherit isn't numeric in multiplication (*) at
| /usr/bin/smtm line 488.
| Argument text-align:center isn't numeric in multiplication (*) at
| /usr/bin/smtm line 489.
| Argument clean isn't numeric in multiplication (*) at /usr/bin/smtm line
491.
| Use of uninitialized value in split at /usr/bin/smtm line 495.
| Use of uninitialized value in split at /usr/bin/smtm line 495.
| Use of uninitialized value in split at /usr/bin/smtm line 495.
| Use of uninitialized value in split at /usr/bin/smtm line 495.
| Use of uninitialized value in split at /usr/bin/smtm line 495.
| Use of uninitialized value in split at /usr/bin/smtm line 495.
| Use of uninitialized value in split at /usr/bin/smtm line 495.
| Use of uninitialized value in split at /usr/bin/smtm line 495.
| Use of uninitialized value in split at /usr/bin/smtm line 495.
| Use of uninitialized value in split at /usr/bin/smtm line 495.
| Argument }p isn't numeric in multiplication (*) at /usr/bin/smtm line 488.
| Argument vertical-align:middle isn't numeric in multiplication (*) at
| /usr/bin/smtm line 489.
| Argument clean isn't numeric in multiplication (*) at /usr/bin/smtm line
491.
| Use of uninitialized value in split at /usr/bin/smtm line 495.
| Use of uninitialized value in split at /usr/bin/smtm line 495.
| Use of uninitialized value in split at /usr/bin/smtm line 495.
| Use of uninitialized value in split at /usr/bin/smtm line 495.
| Argument form {margin:0 isn't numeric in numeric gt () at /usr/bin/smtm
| line 595.
| Argument font:x-small isn't numeric in numeric gt () at /usr/bin/smtm line
| 595.e of uninitialized value in string comparison
Bug#784218: piuparts: Please document how to test upgrades of split packages
On 2015-05-04 11:15, Fabian Greffrath wrote: no, but it gave some valuable pointers and I think our concerns are similar enough to merge both bugs. However, even after dozens of retries with different parameters, I Would have been helpful to give these command lines ... didn't get it to do what I expected. It either straightforward installed the package from the local repo, because that had the higher version number 1.0-2 (if used with the -a option) or it persisted to install only the package from the Debian mirror, because of the game=1.0-1 command line passed over to apt-get. I did not get it to first install the package from the Debian mirror, then upgrade to the package from the local repo. That is definitively possible to test ... --distupgrade-to-testdebs will be needed, perhaps with one or two -d distro options (even '-d sid -d sid' could work) Andreas -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#780495: libgit2-dev: package new version
Shawn Landden sh...@churchofgit.com writes: git2go, the libgit2 go bindings, only support v22+ Could you please package v22, thanks. Sorry for the late reply, I'm building this now should be uploaded in the next couple of days. I was waiting for Jessie release. -- Cheers, Russell -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#784423: [xtrkcad] Wrong turnoutname
This has been fixed upstream as of this patch: http://sourceforge.net/p/xtrkcad-fork/xtrkcad/ci/5a0aeebf10d7cab3327acec6e494ebca98d9cb0f/ signature.asc Description: Digital signature
Bug#754121:
On 2015-05-06 12:29, Michael Biebl wrote: reassign: -1 aiccu Am 06.05.2015 um 04:43 schrieb Daniel Albers: This is a critical bug of either aiccu or systemd as explained by Pascal. Assigning also to systemd as the aiccu maintainer considers this a systemd bug, although I think message #26 546673f0.1040...@localhost.localdomain.org already points to the proper fix for aiccu. Jeroen Massar is not listed as maintainer of the aiccu package Apologies for not being able to get a DD-bit. I am only the person that designed and implemented aiccu, for the rest indeed, that is totally a useless thing in the Debian universe, why care about the original author of the code. and I don't see any explanation which would hint at a bug in systemd. Adding systemd to it all started causing problems. But that is indeed likely just a symptom. systemd is all magic as this bug shows. As you point out though the 'ifup.d' script might be the cause of the whole problem though. See also bug #689584 where I've noted that that script should not exist. Therefor re-assigning back to aiccu. I think it should be re-assigned to Debian then as the problem lies there as that is where the modifications where made and well, Debian is the entity that can really resolve this. From a quick look at the package, it seems to install a init script which depends on $network and an if-up.d hook which restarts the aiccu init script as part of /etc/init.d/networking. /etc/init.d/networking itself provides $network, so there is a dead lock, since systemd evaluates dependencies at runtime. Should such a dead lock at least not be clearly noted in a log or similar? Reinier, if you need help with getting this sorted out, please contact the pkg-systemd team. He does not want to maintain the package: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=692465 Thus all those problems will remain. And without a DD-bit, nobody can resolve this problem. Is there a reason, aiccu needs to be restarted on ifup? Absolutely not. There is no need to *EVER* restart AICCU. The protocols are made for handling dynamic networks. Unfortunately Debian package maintainers seem to think they know better hence instead of listening to the original author of the code and the persons who run the SixXS service (hint: same people :) things are changed anyway. Nothing we can do about these problems. That is a Debian issue. See also amongst others: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=689584 https://bugs.launchpad.net/ubuntu/+source/aiccu/+bug/223825 Note that Debian is not the only entity who does not get this, OpenWRT is another such entity, and heck even ZyXEL still does not understand the concept. Does it need that to pick up new network interfaces? No. The AYIYA protocol is made for handling network changes. The better fix is, to make aiccu network hotplug aware (e.g. via rtnetlink) [1]. Why would AICCU need to know about interfaces? This would also mean, aiccu would work better ootb with other networking tools or if the network is configured manually. It already works fine in those situations. Greets, Jeroen -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#754121:
Hi Jeroen, Am 06.05.2015 um 13:06 schrieb Jeroen Massar: On 2015-05-06 12:29, Michael Biebl wrote: reassign: -1 aiccu Am 06.05.2015 um 04:43 schrieb Daniel Albers: This is a critical bug of either aiccu or systemd as explained by Pascal. Assigning also to systemd as the aiccu maintainer considers this a systemd bug, although I think message #26 546673f0.1040...@localhost.localdomain.org already points to the proper fix for aiccu. Jeroen Massar is not listed as maintainer of the aiccu package Apologies for not being able to get a DD-bit. I am only the person that designed and implemented aiccu, for the rest indeed, that is totally a useless thing in the Debian universe, why care about the original author of the code. Well, the currently listed maintainer is Reinier and he hasn't officially orphaned the package. This should probably be corrected, now that you pointed me to #692465 I wasn't aware of your role regarding this package/software when reading #754121, especially upstream. This was not meant as an offense. So my apologies if this came across the wrong way. But that is indeed likely just a symptom. systemd is all magic as this bug shows. As you point out though the 'ifup.d' script might be the cause of the whole problem though. See also bug #689584 where I've noted that that script should not exist. Therefor re-assigning back to aiccu. I think it should be re-assigned to Debian then as the problem lies there as that is where the modifications where made and well, Debian is the entity that can really resolve this. I think what should happen, is that the package is properly orphaned and then someone can pick it up. If you (or your team at SixXS) is interested in having aiccu properly maintained in Debian, you could try to adopt the package after it has been orphaned and get it uploaded to the archive via a sponsored upload. See http://mentors.debian.net/ Reinier, if you need help with getting this sorted out, please contact the pkg-systemd team. He does not want to maintain the package: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=692465 Thus all those problems will remain. Ok, understood, see above. And without a DD-bit, nobody can resolve this problem. Is there a reason, aiccu needs to be restarted on ifup? Absolutely not. There is no need to *EVER* restart AICCU. The protocols are made for handling dynamic networks. Thanks for the clarification. I just noticed, that aiccu actually no longer installs the ifup hook. But since the if-up hook is a conffile, it's not automatically removed on upgrades, so needs to be dealt with explicitly. See https://wiki.debian.org/DpkgConffileHandling I also noticed, that the aiccu package installs a pm-utils hook, which restarts the aiccu service on suspend/resume. I guess this one could go as well? Unfortunately Debian package maintainers seem to think they know better hence instead of listening to the original author of the code and the persons who run the SixXS service (hint: same people :) things are changed anyway. See above, if you feel like taking over maintainership of the package, this would be appreciated. -- Why is it that all of the instruments seeking intelligent life in the universe are pointed away from Earth? signature.asc Description: OpenPGP digital signature
Bug#784215: strongswan-nm: network-manager-strongswan unavailable
See #759826: network-manager-strongswan didn't compile on Jessie. The fix was too late to be included into the release. The current network-manager-strongswan in testing builds fine on Jessie. I am hoping to do an upload to jessie-backports. Regards Harri -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#784440: onioncat: fails to install due to insserv rejecting the script header: Service tor has to be enabled to start service onioncat
Package: onioncat Version: 0.2.2+svn566-1 Severity: serious User: debian...@lists.debian.org Usertags: piuparts Hi, during a test with piuparts I noticed your package failed to install due to insserv rejecting the script header. Some notes are available from at https://wiki.debian.org/LSBInitScripts From the attached log (scroll to the bottom...): Selecting previously unselected package onioncat. (Reading database ... (Reading database ... 7436 files and directories currently installed.) Preparing to unpack .../onioncat_0.2.2+svn566-1_amd64.deb ... Unpacking onioncat (0.2.2+svn566-1) ... Processing triggers for systemd (215-17) ... Setting up onioncat (0.2.2+svn566-1) ... adding onioncat user... insserv: Service tor has to be enabled to start service onioncat insserv: exiting now! update-rc.d: error: insserv rejected the script header dpkg: error processing package onioncat (--configure): subprocess installed post-installation script returned error exit status 1 Processing triggers for systemd (215-17) ... Errors were encountered while processing: onioncat cheers, Andreas onioncat_0.2.2+svn566-1.log.gz Description: application/gzip
Bug#783459: dnsmasq: Wheezy regression caused by CVE-2015-3294/2.62-3+deb7u2 w/ bind-interfaces
On Wed, 06 May 2015 11:30:35 +0100 Ian Campbell i...@debian.org wrote: I've just noticed that running kernel on the machine is 3.2.57-3+deb7u1 which is quite out of date wrt point releases etc. Looking at the changelog there have been dozens of stable update fixes, one of which might be relevant here. I'll reboot when I get home and see if perhaps that fixes the issue. I have the same problem, but my machine uses 3.2.68: #uname -a Linux lacie 3.2.0-4-kirkwood #1 Debian 3.2.68-1+deb7u1 armv5tel GNU/Linux I had to comment the bind-interfaces line from /etc/dnsmasq.conf in order to make it start. Bye -- Luca -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#754121:
On 2015-05-06 13:26, Michael Biebl wrote: Hi Jeroen, Am 06.05.2015 um 13:06 schrieb Jeroen Massar: On 2015-05-06 12:29, Michael Biebl wrote: reassign: -1 aiccu Am 06.05.2015 um 04:43 schrieb Daniel Albers: This is a critical bug of either aiccu or systemd as explained by Pascal. Assigning also to systemd as the aiccu maintainer considers this a systemd bug, although I think message #26 546673f0.1040...@localhost.localdomain.org already points to the proper fix for aiccu. Jeroen Massar is not listed as maintainer of the aiccu package Apologies for not being able to get a DD-bit. I am only the person that designed and implemented aiccu, for the rest indeed, that is totally a useless thing in the Debian universe, why care about the original author of the code. Well, the currently listed maintainer is Reinier and he hasn't officially orphaned the package. This should probably be corrected, now that you pointed me to #692465 I wasn't aware of your role regarding this package/software when reading #754121, especially upstream. This was not meant as an offense. So my apologies if this came across the wrong way. No worries, it is an easy oversight to make. Unfortunately many distributions have the issue of not acknowledging upstream. For instance https://tracker.debian.org/pkg/aiccu has nowhere a note where the upstream is. There is a 'homepage' link, but there is no 'upstream contact' which would make things easier and might even enforce a better communication between a package maintainer and the actual authors of the code in where the maintainer would ask before making changing instead of just doing so and then causing more problems. But that is indeed likely just a symptom. systemd is all magic as this bug shows. As you point out though the 'ifup.d' script might be the cause of the whole problem though. See also bug #689584 where I've noted that that script should not exist. Therefor re-assigning back to aiccu. I think it should be re-assigned to Debian then as the problem lies there as that is where the modifications where made and well, Debian is the entity that can really resolve this. I think what should happen, is that the package is properly orphaned and then someone can pick it up. If you (or your team at SixXS) is interested in having aiccu properly maintained in Debian, you could try to adopt the package after it has been orphaned and get it uploaded to the archive via a sponsored upload. See http://mentors.debian.net/ I've suggested this before. Unfortunately it seems the politics are large; unfortunate side effect of large projects. Reinier, if you need help with getting this sorted out, please contact the pkg-systemd team. He does not want to maintain the package: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=692465 Thus all those problems will remain. Ok, understood, see above. And without a DD-bit, nobody can resolve this problem. Is there a reason, aiccu needs to be restarted on ifup? Absolutely not. There is no need to *EVER* restart AICCU. The protocols are made for handling dynamic networks. Thanks for the clarification. I just noticed, that aiccu actually no longer installs the ifup hook. But since the if-up hook is a conffile, it's not automatically removed on upgrades, so needs to be dealt with explicitly. See https://wiki.debian.org/DpkgConffileHandling I also noticed, that the aiccu package installs a pm-utils hook, which restarts the aiccu service on suspend/resume. I guess this one could go as well? As filed some 3 years ago: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=689584 As you can see, without DD-bit, little power one retains over the code one produces. Oh and of course, this carries to every distribution that derives from Debian including Ubuntu. Unfortunately Debian package maintainers seem to think they know better hence instead of listening to the original author of the code and the persons who run the SixXS service (hint: same people :) things are changed anyway. See above, if you feel like taking over maintainership of the package, this would be appreciated. Attempted that before. Failed. Please note that the fun part of this all is that we originally packaged AICCU and then somebody took all that work and just stuck it into Debian at one point (which was awesome, as then it worked, not so awesome when things get broken on purpose though...) Greets, Jeroen -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#754121:
On 2015-05-06 13:47, Michael Biebl wrote: Am 06.05.2015 um 13:44 schrieb Jeroen Massar: On 2015-05-06 13:26, Michael Biebl wrote: See above, if you feel like taking over maintainership of the package, this would be appreciated. Attempted that before. Failed. Please note that the fun part of this all is that we originally packaged AICCU and then somebody took all that work and just stuck it into Debian at one point (which was awesome, as then it worked, not so awesome when things get broken on purpose though...) FYI: I just poked the MIA team [1], to get the package orphaned. Let's see what happens. Thx! Greets, Jeroen -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#782364: linux-image-3.16.0-4-armmp: please configure drivers for both Cubox i4pro real time clocks
On May 6, 2015, at 3:27 AM, Ian Campbell i...@debian.org wrote: It would be preferable to test the thing in Sid before the upload to jessie-proposed-updates I’ll keep an eye out for it. But I don’t have one of the cubox models without the battery-backed RTC, so I won’t be able to test that case. Is there anyone out there in debian-arm land with an appropriate test box? Enjoy! Rick -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#784238: systemd: emergency.service restart leads to unusable system
clone 784238 -1 reassign -1 needrestart retitle -1 please don't restart emergency.service/rescue.service thanks Am 04.05.2015 um 13:45 schrieb Michael Biebl: Am 04.05.2015 um 13:41 schrieb Michael Biebl: control: severity -1 important control: tags -1 - security Am 04.05.2015 um 13:15 schrieb Bernd Zeimetz: Severity: critical Package: systemd Tags: security Restarting emergency.service (as done by needsrestart) within the emergency.service leads to a prompt for the root password to enter maintenance, but neither entering a valid password nor pressing ctrl+d results into a login shell. Why do you run needrestart in emergency mode? @needrestart maintainers: can you give us some background on this, does needrestart really restart emergency.service while it's being active? That would be a bit like pulling the rug while you're standing on it. Cloning this bug for needrestart. needrestart shouldn't restart emergency.service (or rescue.service) while you are logged in using the shell. -- Why is it that all of the instruments seeking intelligent life in the universe are pointed away from Earth? signature.asc Description: OpenPGP digital signature
Bug#784438: ITP: autosubmit -- Manage weather and climate experiments on supercomputers
Package: wnpp Severity: wishlist Owner: Alastair McKinstry mckins...@debian.org * Package name: autosubmit Version : 3.0.0rc8 Upstream Author : Domingo Manubens-Gil domingo.manub...@ic3.cat * URL : https://autosubmit.ic3.cat * License : GPLv3 Programming Lang: Python Description : Manage weather and climate experiments on supercomputers Autosubmit: a versatile tool to manage Weather and Climate Experiments in diverse Supercomputing Environments . Autosubmit is a tool to create, manage and monitor experiments using Computing Clusters, HPC's and Supercomputers remotely via ssh. This will also need pydotplus to be packaged first. It is planned that this will be added to debian-science / Debian Meteorology -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#784426: smtm: dies at start
reassign 784426 libfinance-yahooquote-perl
severity normal
quit
On 6 May 2015 at 09:25, Ivan Rossi wrote:
| Package: smtm
| Version: 1.6.10
| Severity: grave
| Justification: renders package unusable
|
| Dear Maintainer,
|
|
| Since the middle of april 2015 smtm stopped working.
| Tested on different machines (wheezy and jessie) and two different users.
|
| at launch the program stops without starting the tk inteface, logging the
| following errors:
|
|
| Use of uninitialized value in join or string at /usr/bin/smtm line 435.
| Use of uninitialized value in uc at /usr/bin/smtm line 435.
| Use of uninitialized value in join or string at /usr/bin/smtm line 435.
| Use of uninitialized value in uc at /usr/bin/smtm line 435.
| Use of uninitialized value in join or string at /usr/bin/smtm line 435.
| Use of uninitialized value in uc at /usr/bin/smtm line 435.
| Use of uninitialized value in join or string at /usr/bin/smtm line 435.
| Use of uninitialized value in uc at /usr/bin/smtm line 435.
| Use of uninitialized value in join or string at /usr/bin/smtm line 435.
| Use of uninitialized value in uc at /usr/bin/smtm line 435.
| Use of uninitialized value in join or string at /usr/bin/smtm line 435.
| Use of uninitialized value in uc at /usr/bin/smtm line 435.
| Use of uninitialized value in join or string at /usr/bin/smtm line 435.
| Use of uninitialized value in uc at /usr/bin/smtm line 435.
| Use of uninitialized value in join or string at /usr/bin/smtm line 435.
| Use of uninitialized value in uc at /usr/bin/smtm line 435.
| Use of uninitialized value in join or string at /usr/bin/smtm line 435.
| Use of uninitialized value in uc at /usr/bin/smtm line 435.
| Use of uninitialized value in join or string at /usr/bin/smtm line 435.
| Use of uninitialized value in uc at /usr/bin/smtm line 435.
| Use of uninitialized value in join or string at /usr/bin/smtm line 435.
| Use of uninitialized value in uc at /usr/bin/smtm line 435.
| Use of uninitialized value in join or string at /usr/bin/smtm line 435.
| Use of uninitialized value in uc at /usr/bin/smtm line 435.
| Use of uninitialized value in join or string at /usr/bin/smtm line 435.
| Use of uninitialized value in uc at /usr/bin/smtm line 435.
| Use of uninitialized value in join or string at /usr/bin/smtm line 435.
| Use of uninitialized value in uc at /usr/bin/smtm line 435.
| Use of uninitialized value in split at /usr/bin/smtm line 495.
| Use of uninitialized value in split at /usr/bin/smtm line 495.
| Use of uninitialized value in split at /usr/bin/smtm line 495.
| Use of uninitialized value in split at /usr/bin/smtm line 495.
| Use of uninitialized value in split at /usr/bin/smtm line 495.
| Use of uninitialized value $arr[0] in uc at /usr/bin/smtm line 478.
| Use of uninitialized value in hash element at /usr/bin/smtm line 486.
| Use of uninitialized value in split at /usr/bin/smtm line 495.
| Use of uninitialized value in split at /usr/bin/smtm line 495.
| Use of uninitialized value in split at /usr/bin/smtm line 495.
| Use of uninitialized value in split at /usr/bin/smtm line 495.
| Argument }table {font-size:inherit isn't numeric in multiplication (*) at
| /usr/bin/smtm line 488.
| Argument text-align:center isn't numeric in multiplication (*) at
| /usr/bin/smtm line 489.
| Argument clean isn't numeric in multiplication (*) at /usr/bin/smtm line
491.
| Use of uninitialized value in split at /usr/bin/smtm line 495.
| Use of uninitialized value in split at /usr/bin/smtm line 495.
| Use of uninitialized value in split at /usr/bin/smtm line 495.
| Use of uninitialized value in split at /usr/bin/smtm line 495.
| Use of uninitialized value in split at /usr/bin/smtm line 495.
| Use of uninitialized value in split at /usr/bin/smtm line 495.
| Use of uninitialized value in split at /usr/bin/smtm line 495.
| Use of uninitialized value in split at /usr/bin/smtm line 495.
| Use of uninitialized value in split at /usr/bin/smtm line 495.
| Use of uninitialized value in split at /usr/bin/smtm line 495.
| Argument }p isn't numeric in multiplication (*) at /usr/bin/smtm line 488.
| Argument vertical-align:middle isn't numeric in multiplication (*) at
| /usr/bin/smtm line 489.
| Argument clean isn't numeric in multiplication (*) at /usr/bin/smtm line
491.
| Use of uninitialized value in split at /usr/bin/smtm line 495.
| Use of uninitialized value in split at /usr/bin/smtm line 495.
| Use of uninitialized value in split at /usr/bin/smtm line 495.
| Use of uninitialized value in split at /usr/bin/smtm line 495.
| Argument form {margin:0 isn't numeric in numeric gt () at /usr/bin/smtm
| line 595.
| Argument font:x-small isn't numeric in numeric gt () at /usr/bin/smtm line
| 595.e of uninitialized value in string comparison (cmp) at /usr/bin/smtm line
| 351.
| Use of uninitialized value in string comparison (cmp) at /usr/bin/smtm line
| 351.
| Use of uninitialized value in string comparison (cmp) at /usr/bin/smtm line
| 351.
| Use of uninitialized value in
Bug#784439: uglifyjs version failing
2015-05-06 13:31 GMT+02:00 Pau Garcia i Quiles pgqui...@elpauer.org: Package: node-uglify Version: 2.4.15-1 Trying to find out the version of uglifyjs on your system fails: $ uglifyjs --version module.js:340 throw err; ^ Error: Cannot find module '../package.json' at Function.Module._resolveFilename (module.js:338:15) at Function.Module._load (module.js:280:25) at Module.require (module.js:364:17) at require (module.js:380:17) at Object.anonymous (/usr/bin/uglifyjs:118:16) at Module._compile (module.js:456:26) at Object.Module._extensions..js (module.js:474:10) at Module.load (module.js:356:32) at Function.Module._load (module.js:312:12) at Function.Module.runMain (module.js:497:10) The package.json file does exist: $ dpkg -L node-uglify /. /usr /usr/lib /usr/lib/nodejs /usr/lib/nodejs/uglify-js /usr/lib/nodejs/uglify-js/transform.js /usr/lib/nodejs/uglify-js/utils.js /usr/lib/nodejs/uglify-js/output.js /usr/lib/nodejs/uglify-js/index.js /usr/lib/nodejs/uglify-js/compress.js /usr/lib/nodejs/uglify-js/scope.js /usr/lib/nodejs/uglify-js/sourcemap.js /usr/lib/nodejs/uglify-js/ast.js /usr/lib/nodejs/uglify-js/mozilla-ast.js /usr/lib/nodejs/uglify-js/package.json /usr/lib/nodejs/uglify-js/parse.js /usr/share /usr/share/man /usr/share/man/man1 /usr/share/man/man1/uglifyjs.1.gz /usr/share/doc /usr/share/doc/node-uglify /usr/share/doc/node-uglify/copyright /usr/share/doc/node-uglify/README.md.gz /usr/share/doc/node-uglify/changelog.Debian.gz /usr/bin /usr/bin/uglifyjs Problem is /usr/bin/uglifyjs looks for it in the wrong place: $ grep package.json /usr/bin/uglifyjs var json = require(../package.json); Hi there, that's why it's usually simpler and safer to install original hierarchy with - package.json - lib/* in /usr/lib/nodejs/uglify-js, instead of changing it and not installing package.json. Regards, Jérémy.
Bug#784442: libnb-platform18-java: FTBFS in sid
Package: libnb-platform-java Version: 7.4+dfsg1-2 Severity: serious Tags: stretch sid Hi, libnb-platform18-java fails to build from source in sid. This is mainly due to the recents updates of the Felix and OSGi build-dependencies. The build already fails in the dh_auto_clean override step. I will try to update this package. Markus -- System Information: Debian Release: stretch/sid APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 3.16.0-4-amd64 (SMP w/2 CPU cores) Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: unable to detect -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#783459: dnsmasq: Wheezy regression caused by CVE-2015-3294/2.62-3+deb7u2 w/ bind-interfaces
On Wed, 2015-05-06 at 11:34 +0200, Salvatore Bonaccorso wrote: I just tried to replicate that configuration and set up a wheezy VM up with two interfaces eth0, eth1, and set the following modifications: interface=eth1 bind-interfaces domain=example.com dhcp-range=192.168.1.128,192.168.1.255,12h But so far I was not able to reproduce the problem, but only from a quit re-check (and in particular not the same arch as well). Thanks for checking/trying. I've just noticed that running kernel on the machine is 3.2.57-3+deb7u1 which is quite out of date wrt point releases etc. Looking at the changelog there have been dozens of stable update fixes, one of which might be relevant here. I'll reboot when I get home and see if perhaps that fixes the issue. Ian. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#784435: please complain loudly about bugs in /etc/crypttab
Package: cryptsetup Version: 2:1.6.6-5 I spent way too much time about a lost UUID= in /etc/crypttab. It would be very helpful if cryptroot-hook complains about errors in this file. Silently ignoring bad config lines is not helpful. Thanx in advance Harri -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#784238: systemd: emergency.service restart leads to unusable system
Am 04.05.2015 um 13:15 schrieb Bernd Zeimetz: Even worse, pressing enter shows the prompt from the former shell and I'm able to get 'bash ... command not found errors' This looks like a bug in /sbin/sulogin, which does not properly cleanup it's children, when being killed. Our /sbin/sulogin implementation comes from sysvinit-utils while apparently most other distros use /sbin/sulogin from util-linux nowadays. I think we can workaround that by letting systemd do the process cleanup and using KillMode=mixed (currently it uses KillMode=process, which means it leaves the cleanup to the main process). Bernd, please copy /lib/systemd/system/emergency.service to /etc/systemd/system/emergency.service and change KillMode=process to KillMode=mixed. When you are in the emergency shell, restarting emergency.service should now also kill the running bash shell. Before you try to systemctl restart emergency.service, you can start a debug shell on tty9 via systemctl start debug-shell.service where you can switch to, if something goes wrong. Please confirm, if this fixes your issue or not. -- Why is it that all of the instruments seeking intelligent life in the universe are pointed away from Earth? signature.asc Description: OpenPGP digital signature
Bug#784436: security-tracker: contradictory status information on security-tracker.debian.org
Package: security-tracker Severity: normal On https://security-tracker.debian.org/tracker/CVE-2014-3660 I can see: Release Version Status jessie2.9.1+dfsg1-5 fixed stretch 2.9.1+dfsg1-5 vulnerable i.e. the same version of the package is listed both as fixed and vulnerable! According to bug 765722, it should be fixed. This is very confusing for the user who wants to know whether some installed package is vulnerable or not. -- System Information: Debian Release: stretch/sid APT prefers unstable APT policy: (500, 'unstable'), (500, 'testing'), (500, 'stable'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.16.0-4-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 Init: sysvinit (via /sbin/init) -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#784439: uglifyjs version failing
Package: node-uglify Version: 2.4.15-1 Trying to find out the version of uglifyjs on your system fails: $ uglifyjs --version module.js:340 throw err; ^ Error: Cannot find module '../package.json' at Function.Module._resolveFilename (module.js:338:15) at Function.Module._load (module.js:280:25) at Module.require (module.js:364:17) at require (module.js:380:17) at Object.anonymous (/usr/bin/uglifyjs:118:16) at Module._compile (module.js:456:26) at Object.Module._extensions..js (module.js:474:10) at Module.load (module.js:356:32) at Function.Module._load (module.js:312:12) at Function.Module.runMain (module.js:497:10) The package.json file does exist: $ dpkg -L node-uglify /. /usr /usr/lib /usr/lib/nodejs /usr/lib/nodejs/uglify-js /usr/lib/nodejs/uglify-js/transform.js /usr/lib/nodejs/uglify-js/utils.js /usr/lib/nodejs/uglify-js/output.js /usr/lib/nodejs/uglify-js/index.js /usr/lib/nodejs/uglify-js/compress.js /usr/lib/nodejs/uglify-js/scope.js /usr/lib/nodejs/uglify-js/sourcemap.js /usr/lib/nodejs/uglify-js/ast.js /usr/lib/nodejs/uglify-js/mozilla-ast.js /usr/lib/nodejs/uglify-js/package.json /usr/lib/nodejs/uglify-js/parse.js /usr/share /usr/share/man /usr/share/man/man1 /usr/share/man/man1/uglifyjs.1.gz /usr/share/doc /usr/share/doc/node-uglify /usr/share/doc/node-uglify/copyright /usr/share/doc/node-uglify/README.md.gz /usr/share/doc/node-uglify/changelog.Debian.gz /usr/bin /usr/bin/uglifyjs Problem is /usr/bin/uglifyjs looks for it in the wrong place: $ grep package.json /usr/bin/uglifyjs var json = require(../package.json); -- Pau Garcia i Quiles http://www.elpauer.org (Due to my workload, I may need 10 days to answer) -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#784438: ITP: autosubmit -- Manage weather and climate experiments on supercomputers
Le 06/05/2015 13:05, Alastair McKinstry a écrit : Package: wnpp Severity: wishlist Owner: Alastair McKinstry mckins...@debian.org * Package name: autosubmit Dear Alastair, the package name sounds too generic. Why not ic3-autosubmit for instance? Just my 2c. Kind regards, Thibaut. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#784441: grahpite-web: Please backport fix to ignore trailing args in aliasByMetric()
Package: grahpite-web
Version: 0.9.12+debian-7
Severity: normal
Tags: upstream patch
Dear Maintainer,
If one want's to eg. consolidateBy(max) and also want to have some nice
looking legends one would normally use aliasByMetric, but it does not
work as intended in the debian version.
It is already fixed upstream and backported to the 0.9.x by the
graphite-web people themself, please apply this patch in debian too.
# bug description
Graphite query:
aliasByMetric(consolidateBy(collectd.$S.interface-eth0.if_octets.*, 'max'))
produced labels: `rx, 'max')` and `tx, 'max')`
desired labels: `rx` and `tx`
Please backport the fix to ignore trailing args in aliasByMetric().
Graphite-web issue (already merged on 25.8.2014):
https://github.com/graphite-project/graphite-web/pull/885
Graphite-web patch:
https://github.com/obfuscurity/graphite-web/commit/7fc74b830824691b5e0c8d421200976543b9f47a
# patch: webapp/graphite/render/functions.py: @@ def aliasByMetric
-series.name = series.name.split('.')[-1]
+series.name = series.name.split('.')[-1].split(',')[0]
Michael Gebetsroither
-- System Information:
Debian Release: jessie/sid
APT prefers stable
APT policy: (990, 'stable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 3.16.0-4-amd64 (SMP w/2 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash
Init: sysvinit (via /sbin/init)
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#784319: [Pkg-nagios-devel] Bug#784319: Bug#784319: Segfault when running check_dhcp
FWIW, it worked. Here is the dpatch I created: --- SNIP --- #! /bin/sh /usr/share/dpatch/dpatch-run ## 10_check_dhcp.dpatch by aheinl...@gmx.com ## ## All lines beginning with `## DP:' are a description of the patch. ## DP: No description. @DPATCH@ diff -urNad '--exclude=CVS' '--exclude=.svn' '--exclude=.git' '--exclude=.arch' '--exclude=.hg' '--exclude=_darcs' '--exclude=.bzr' monitoring-plugins-2.1.1~/plugins-root/check_dhcp.c monitoring-plugins-2.1.1/plugins-root/check_dhcp.c --- monitoring-plugins-2.1.1~/plugins-root/check_dhcp.c2014-12-02 04:36:29.0 + +++ monitoring-plugins-2.1.1/plugins-root/check_dhcp.c2015-05-06 12:19:24.772947737 + @@ -323,7 +323,8 @@ #elif defined(__bsd__) /* King 2004see ACKNOWLEDGEMENTS */ -int mib[6], len; +int mib[6]; +size_tlen; char*buf; unsigned char *ptr; struct if_msghdr*ifm; @@ -1182,7 +1183,7 @@ } } -return i; +return i+1; } --- SNIP --- -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#784446: backup-manager: Current incremental backup implementation can cause data loss
Package: backup-manager Version: 0.7.10.1-2 Severity: grave Justification: renders package unusable Dear Maintainer, I had suspected for a while there was an issue with the way backup-manager handles incremental backups. The issue is related with the way older archives are deleted when BM_ARCHIVE_TTL is reached. I now have built a (albeit crude) test suite, attached, to test that behaviour, and as I feared, backup-manager causes data loss. I strongly urge anyone using backup-manager to avoid using tarball-incremental mode until this bug is sorted out. backup-manager purges backup files that are older than today minus BM_ARCHIVE_TTL days. For incremental tarballs, it will, however, never delete the latest master backup until a new master will have been created - but it will delete incrementals in between the said master and TODAY minus BM_ARCHIVE_TTL. Note that new masters will be only created if we are precisely on BM_TARBALLINC_MASTERDATEVALUE [day of the week or day of the month]. If the backup happens another day, it will do an incremental backup, based on the backup-name.incremental.bin data file, regardless of whether the current master backup is older than BM_ARCHIVE_TTL or not. However, incremental.bin is not updated following the deletion of previous incremental tarballs in between the old master and the new incremental. Therefore the new incremental backups do not store everything required to maintain backup consistency. So one can have a very old master, some recent incremental backups, and a very big 'hole' in between - and all files created in that 'hole' will be lost if one tries to restore from the incremental (also all files modified in that period will be reverted to the version stored in the old master). The situation is very likely to happen: - if you automate backups every day, if and only if BM_ARCHIVE_TTL 7 (for weekly masters) or BM_ARCHIVE_TTL 31 (for monthly masters), since that would be the situation where incrementals would be deleted before a new master is created, - if you automate backups weekly with a BM_TARBALLINC_MASTERDATETYPE set to monthly as BM_TARBALLINC_MASTERDATEVALUE may be missed, - if you do manual backups and forget to start it regularly on the day you have set the master archive creation. I enclose to this bug report a test suite containing: - in bindir/ : a set of scripts that override /bin/date in order to simulate several days of a given week - in bindir/ : two one-line modifications of /usr/sbin/backup-manager [line 36] and /usr/bin/backup-manager-purge [line 244] which were unfortunately necessary to call the special date instead of the standard perl time() - two empty test directories testdir/ and backupdir/ - a custom backup-manager.conf used by the test script, with BM_ARCHIVE_TTL set to 2, which should be modified by the tester (some paths to change) - a test.sh script that should be modified (TESTDIR, BACKUPNAME to be changed) in order to run it test.sh simulates a week going from monday to friday, with a master backup set to monday. It generates or modifies files in testdir/ prior to each backup to simulate file system changes, and those files are stored consecutively as master and incremental backups into backupdir/ On monday: - it creates three files, never_modified.txt with contents never modified; modified_every_day.txt, modified_until_tuesday.txt with monday as their content. - calls backup-manager On tuesday: - it creates created_tuesday.txt with content created tuesday, and writes tuesday as the content of modified_until_tuesday.txt and modified_every_day.txt - calls backup-manager On wednesday: - writes wednesday as the content of modified_every_day.txt - calls bm On thursday: - calls bm On friday: - idem The test script then unpack all the backups that should be in the directory according to the behaviour of backup-manager explained above, considering BM_ARCHIVE_TTL is set to 2 for testing purposes, in that order: the master backup of monday, the incremental backup of thursday, the incremental backup of friday. it then compares the resulting files with the files in testdir/ What is expected: the restored backup should contain: never_modified.txt with content never modified modified_until_tuesday.txt with content tuesday created_tuesday.txt with content created tuesday modified_every_day.txt with content friday What actually happens: the restored backup contains: never_modified.txt with content never modified modified_until_tuesday.txt with content monday modified_every_day.txt with content friday There are several ways to resolve this issue: - either do not delete any incremental backups as long as a new master has not been created, even if they are over BM_ARCHIVE_TTL - figure out a way to update backupname.incremental.bin when deleting the old in-between incrementals so that its content reflects that deletion - force the generation of a new master as soon as the current one is older than BM_ARCHIVE_TTL, even if
Bug#784319: [Pkg-nagios-devel] Bug#784319: Bug#784319: Bug#784319: Segfault when running check_dhcp
-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Hi Andreas, Am 06.05.15 um 14:43 schrieb Andreas Heinlein: FWIW, it worked. cool! Could please send me over your output from your shell with the fixed binary? Many thanks, Jan. - -- Never write mail to w...@spamfalle.info, you have been warned! - -BEGIN GEEK CODE BLOCK- Version: 3.12 GIT d-- s+: a C+++ UL P+ L+++ E--- W+++ N+++ o++ K++ w--- O M V- PS PE Y++ PGP++ t-- 5 X R tv- b+ DI D+ G++ e++ h r+++ y - --END GEEK CODE BLOCK-- -BEGIN PGP SIGNATURE- Version: GnuPG/MacGPG2 v2.0.22 (Darwin) Comment: GPGTools - https://gpgtools.org iQIcBAEBCgAGBQJVShDwAAoJEAxwVXtaBlE+kgYP/AxSVxNPvvN8a/gO0o6jlqAq BGEYzaWsDr+5fKSnxqAHT4lsf2cRys0pSTq2Ac9IgRhT4P7FZA0zuX8TtmoHcqXu 6G91oahVdAUSy3qbc6xRetORQdb68C2g7Z5RPWuGI5v63P+HFAdVEHNXDqWd8H+T JR0Oh+tbPxvEQ1DzpYHzJ2Z3hYJEKVGZJMTB08mFSKaFf+kLAkKvUyJQcUGtsjff 3TD1IQpvqHBw3+R2bswabxB1EQgp/YUhQsWodB84h5O7/cMgv2+zpzs/1YAKZv2K SAtCX5uCTTeGZ8+0ofGFTex1qH72xcqdSe7cyOcqRmevDDvd43I6bpB/tMbOJumA 1T1bC/UXIhUwrhCIwJYax1dgw4txnKmr70Dms/PTnQGReMOiyXgYT6MHney1SAIa qy9SCwhrROa3aexqp/AaV2mXm8yEygkfMbmZ8SVs9/LWI/wNWsHKPScSN6nIsd7T gShiYpihSnLc4QFZbTgAXCKXArP4DYqrUEn/uzHad4ZVLA1USL6YlxBrfjys0e2V bh5Dr4vR41BxuB1yKsSRl81zWxaDqAgPSAO6LXt2+TnXlcMevDJBuBKlX32QIdNN yraZrANpzGNXd1mgruAJFmyn6itkHKEkvzledI1PclKvLfNvbQGpJZ9YIkxAjde7 8Y3K4fNrAy7dsZvUFCA+ =t9ge -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#759656: [PATCH] mmc: card: not access RPMB partition for normal read and write
On 05/06/2015 03:06 PM, Ulf Hansson wrote: On 12 August 2014 at 06:01, Yunpeng Gao yunpeng@intel.com wrote: From: Chuanxiao Dong chuanxiao.d...@intel.com Sorry for the delay and thanks! ah thanks. Is it likely you go via my patches for mmc-utils in the new few days? Kind regards Uffe Sebastian -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#784535: Further information
/var/log/ejabberd # tail -f ./ejabberd.log
2015-05-06 16:12:39.448 [info] 0.7.0 Application asn1 started on node
ejabberd@talk
2015-05-06 16:12:39.449 [info] 0.7.0 Application public_key started on
node ejabberd@talk
2015-05-06 16:12:39.544 [info] 0.7.0 Application ssl started on node
ejabberd@talk
2015-05-06 16:12:39.647 [info] 0.7.0 Application p1_yaml started on
node ejabberd@talk
2015-05-06 16:12:39.890 [info] 0.7.0 Application p1_tls started on
node ejabberd@talk
2015-05-06 16:12:40.099 [info] 0.7.0 Application p1_xml started on
node ejabberd@talk
2015-05-06 16:12:40.244 [info] 0.7.0 Application p1_stringprep started
on node ejabberd@talk
2015-05-06 16:12:40.372 [info] 0.7.0 Application p1_zlib started on
node ejabberd@talk
2015-05-06 16:12:40.467 [info] 0.7.0 Application p1_cache_tab started
on node ejabberd@talk
2015-05-06 16:12:41.516 [info] 0.7.0 Application mnesia started on
node ejabberd@talk
2015-05-06 16:12:48.886 [info]
0.354.0@ejabberd_config:prepare_opt_val:582 Configuration problem:
** Option: {ldap_dn_filter,global}
** Invalid value: [{(entrydn=cn=%u,dc=%d,ou=accounts,dc=cac2s),[]}]
** Using as fallback: {undefined,[]}
2015-05-06 16:12:48.910 [info] 0.355.0@eldap:connect_bind:1106 LDAP
connection on ldap.cac2s.net:389
2015-05-06 16:12:48.913 [info] 0.356.0@eldap:connect_bind:1106 LDAP
connection on ldap.cac2s.net:389
2015-05-06 16:12:48.948 [info] 0.38.0@cyrsasl_digest:start:57 FQDN
used to check DIGEST-MD5 SASL authentication: talk
2015-05-06 16:12:49.259 [info] 0.7.0 Application p1_iconv started on
node ejabberd@talk
2015-05-06 16:12:49.491 [info] 0.451.0@eldap:connect_bind:1106 LDAP
connection on ldap.cac2s.net:389
2015-05-06 16:12:49.500 [info]
0.453.0@ejabberd_listener:listen_tcp:194 Reusing listening port for 5222
2015-05-06 16:12:49.502 [info]
0.454.0@ejabberd_listener:listen_tcp:194 Reusing listening port for 5269
2015-05-06 16:12:49.503 [info]
0.455.0@ejabberd_listener:listen_tcp:194 Reusing listening port for
2015-05-06 16:12:49.505 [info]
0.456.0@ejabberd_listener:listen_tcp:194 Reusing listening port for 5556
2015-05-06 16:12:49.507 [info]
0.458.0@ejabberd_listener:listen_tcp:194 Reusing listening port for 4560
2015-05-06 16:12:49.508 [info]
0.459.0@ejabberd_listener:listen_tcp:194 Reusing listening port for 5280
2015-05-06 16:12:49.508 [info] 0.38.0@ejabberd_app:start:69 ejabberd
14.07 is started in the node ejabberd@talk
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#784538: file-rc: please make the package build reproducible
Source: file-rc Version: 0.8.16 Severity: wishlist Tags: patch User: reproducible-bui...@lists.alioth.debian.org Usertags: umask Hi! While working on the “reproducible builds” effort [1], we have noticed that file-rc could not be built reproducibly. The attached patch replaces the `grep`+`mv` by `sed -i` to keep the file permissions identical even with different umasks. Once applied, file-rc can be built reproducibly in our current experimental framework. [1]: https://wiki.debian.org/ReproducibleBuilds -- Lunar.''`. lu...@debian.org: :Ⓐ : # apt-get install anarchism `. `'` `- diff -Nru file-rc-0.8.16/debian/changelog file-rc-0.8.16.0~reproducible1/debian/changelog --- file-rc-0.8.16/debian/changelog 2013-05-24 06:02:40.0 + +++ file-rc-0.8.16.0~reproducible1/debian/changelog 2015-05-06 13:43:38.0 + @@ -1,3 +1,10 @@ +file-rc (0.8.16.0~reproducible1) UNRELEASED; urgency=low + + * Use `sed -i` to keep permisions when modifying conffiles list. +This makes the result identical with different umasks. + + -- Jérémy Bobbio lu...@debian.org Wed, 06 May 2015 13:42:47 + + file-rc (0.8.16) unstable; urgency=low [ Colin Watson ] diff -Nru file-rc-0.8.16/debian/rules file-rc-0.8.16.0~reproducible1/debian/rules --- file-rc-0.8.16/debian/rules 2012-07-02 20:47:12.0 + +++ file-rc-0.8.16.0~reproducible1/debian/rules 2015-05-06 13:47:19.0 + @@ -64,9 +64,7 @@ dh_installdeb # Workaround to avoid rc, rcS and README from /etc/init.d being # conffiles: - grep -v /etc/init.d/ $(debroot)/DEBIAN/conffiles \ - $(debroot)/DEBIAN/conffiles.tmp - mv $(debroot)/DEBIAN/conffiles.tmp $(debroot)/DEBIAN/conffiles + sed -e '\,/etc/init.d/,d' -i $(debroot)/DEBIAN/conffiles # dh_perl dh_gencontrol dh_md5sums signature.asc Description: Digital signature
Bug#784532: [swift-im] Qt4's WebKit removal
Thanks for the heads-up. Upstream (also us) will be releasing a 3.0 version of Swift before too long, which supports Qt5, so we’ll work to get that packaged and submitted as soon as the upstream is released. In the meantime we could conceivably upload a build of one of the 3.0 betas to get over the problem more immediately, if there’s a need for that? /K -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#784542: Unneeded and unreachable man page symlink /usr/share/man/man3/.3ssl.gz
-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Package: libssl-doc Version: 1.0.2a-1 Severity: minor The package installs /usr/share/man/man3/.3ssl.gz as a symlink to SSL_CTX_use_serverinfo.3ssl.gz. That file is unneeded and unreachable by man. - -- System Information: Debian Release: stretch/sid APT prefers unstable APT policy: (800, 'unstable'), (110, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.19.5 (SMP w/8 CPU cores) Locale: LANG=de_DE, LC_CTYPE=de_DE (charmap=ISO-8859-1) (ignored: LC_ALL set to de_DE) Shell: /bin/sh linked to /bin/dash Init: sysvinit (via /sbin/init) - -- Klaus Ethgen http://www.ethgen.ch/ pub 4096R/4E20AF1C 2011-05-16 Klaus Ethgen kl...@ethgen.de Fingerprint: 85D4 CA42 952C 949B 1753 62B3 79D0 B06F 4E20 AF1C -BEGIN PGP SIGNATURE- Version: GnuPG v1 iQGcBAEBCgAGBQJVSh00AAoJEKZ8CrGAGfasL4EL/2nNWbf4fdSfgwGPQvvJAvt9 PcOaaJV8ALKSL97iQ0zzAIIq8E4WxNp1FRrPL22Dw8RB46KnnEmWUT7HVzCHD0ut 4fFoD44Jlrq559RwggmEc1zlMTj9rkWupXzaMkaHWNL2vCvUuHa713Cp6xAQY7P8 RwEtOVlcivMTAXc5QV0sHjJoULVM6wDCTrGwV1n41xeCUKjjsfec6K43KX062op/ d9lLRBXNzquJRCcQjhlUWuug7DatqVElJAFwdBliIcloZD23r/na88LeJfmMdGOS LvbIiNz+AlGrYyhF45rJPkY5O7KetENA0ZaZ65jaqkKZw5FeRjUGR4wEoicHqfX0 yx91vJpo8CILo5ydrG5pyn65AsZ5lEh98va+U4LS1WRPbST1n7LgbkwBl3OwHLn4 JZMVy5Ww03LeVPmbS1yGE9eQxbkJC1fl0K1e191q/+2IVUTenICP39fa/yBNcmFD elOzyrz+hrYpEsQH3zJR70v2l5+d9Kju5sz7/VSJ8w== =fyNS -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#784541: yasm: please make the package build reproducible
Source: yasm
Version: 1.3.0-2
Severity: wishlist
Tags: patch
User: reproducible-bui...@lists.alioth.debian.org
Usertags: timestamps
Hi!
While working on the “reproducible builds” effort [1], we have noticed
that yasm could not be built reproducibly.
The attached patch removes the build date from the version strings.
Once applied, yasm can be built reproducibly in our current experimental
framework.
[1]: https://wiki.debian.org/ReproducibleBuilds
--
Lunar.''`.
lu...@debian.org: :Ⓐ : # apt-get install anarchism
`. `'`
`-
diff -Nru yasm-1.3.0/debian/changelog yasm-1.3.0/debian/changelog
--- yasm-1.3.0/debian/changelog 2015-05-03 21:00:33.0 +
+++ yasm-1.3.0/debian/changelog 2015-05-06 14:02:59.0 +
@@ -1,3 +1,11 @@
+yasm (1.3.0-2.0~reproducible1) UNRELEASED; urgency=low
+
+ * Make the package build reproducible:
+- 110_remove_build_date.diff: remove compilation date from
+ version strings.
+
+ -- Jérémy Bobbio lu...@debian.org Wed, 06 May 2015 14:00:31 +
+
yasm (1.3.0-2) unstable; urgency=medium
* 100_ytasm_parsing_error.diff: fix more bugs in argument parsing.
diff -Nru yasm-1.3.0/debian/patches/110_remove_build_date.diff yasm-1.3.0/debian/patches/110_remove_build_date.diff
--- yasm-1.3.0/debian/patches/110_remove_build_date.diff 1970-01-01 00:00:00.0 +
+++ yasm-1.3.0/debian/patches/110_remove_build_date.diff 2015-05-06 14:04:29.0 +
@@ -0,0 +1,37 @@
+Description: Remove build date from version strings
+ In order to make the package build reproducibly, we remove the compilation
+ date from the version strings. At least in the context of Debian we know
+ the exact source code and we record the build environment. Both are more
+ meaningful information.
+Author: Jérémy Bobbio lu...@debian.org
+
+--- yasm-1.3.0.orig/frontends/tasm/tasm.c
yasm-1.3.0/frontends/tasm/tasm.c
+@@ -228,7 +228,6 @@ static opt_option options[] =
+ /* version message */
+ /*@observer@*/ static const char *version_msg[] = {
+ PACKAGE_STRING,
+-Compiled on __DATE__ .,
+ Copyright (c) 2001-2010 Peter Johnson and other Yasm developers.,
+ Run yasm --license for licensing overview and summary.
+ };
+--- yasm-1.3.0.orig/frontends/vsyasm/vsyasm.c
yasm-1.3.0/frontends/vsyasm/vsyasm.c
+@@ -220,7 +220,6 @@ static opt_option options[] =
+ /* version message */
+ /*@observer@*/ static const char *version_msg[] = {
+ PACKAGE_STRING,
+-Compiled on __DATE__ .,
+ Copyright (c) 2001-2010 Peter Johnson and other Yasm developers.,
+ Run yasm --license for licensing overview and summary.
+ };
+--- yasm-1.3.0.orig/frontends/yasm/yasm.c
yasm-1.3.0/frontends/yasm/yasm.c
+@@ -217,7 +217,6 @@ static opt_option options[] =
+ /* version message */
+ /*@observer@*/ static const char *version_msg[] = {
+ PACKAGE_STRING,
+-Compiled on __DATE__ .,
+ Copyright (c) 2001-2014 Peter Johnson and other Yasm developers.,
+ Run yasm --license for licensing overview and summary.
+ };
diff -Nru yasm-1.3.0/debian/patches/series yasm-1.3.0/debian/patches/series
--- yasm-1.3.0/debian/patches/series 2015-05-03 19:58:07.0 +
+++ yasm-1.3.0/debian/patches/series 2015-05-06 14:03:09.0 +
@@ -1 +1,2 @@
100_ytasm_parsing_error.diff
+110_remove_build_date.diff
signature.asc
Description: Digital signature
Bug#784540: recollindex always indexes /tmp despite being given a different path
Package: recoll Version: 1.20.3-2 Severity: important File: /usr/bin/recollindex recollindex -c someconfdir some/path used to index to index some/path. Since upgrading from 1.17.3-2 to 1.20.3-2 it indexes /tmp instead. It seems that the new version does not provide any means to index files outside /tmp. If this observation is wrong, please downgrade the severity of this bug. Helmut -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#784218: piuparts: Please document how to test upgrades of split packages
Am Mittwoch, den 06.05.2015, 13:18 +0200 schrieb Andreas Beckmann: Would have been helpful to give these command lines ... Sure, sorry. $ grep piuparts ~/.bash_history [...] sudo piuparts ../chocolate-doom_2.1.0-2_amd64.changes sudo piuparts ../chocolate-doom_2.1.0-2_amd64.deb ../chocolate-common_2.1.0-2_amd64.deb sudo piuparts -d unstable ../chocolate-doom_2.1.0-2_amd64.changes reportbug piuparts [...] sudo piuparts --bindmount /tmp/repo --testdebs-repo /tmp/repo --distupgrade-to-testdebs -a chocolate-doom sudo piuparts --bindmount /tmp/repo --testdebs-repo /tmp/repo --distupgrade-to-testdebs --do-not-verify-signatures -a chocolate-doom sudo piuparts --bindmount /tmp/repo --testdebs-repo /tmp/repo --distupgrade-to-testdebs --do-not-verify-signatures --install-recommends -a chocolate-doom sudo piuparts --bindmount /tmp/repo --testdebs-repo /tmp/repo --distupgrade-to-testdebs --do-not-verify-signatures --install-recommends -a -d sid chocolate-doom sudo piuparts --bindmount /tmp/repo --testdebs-repo /tmp/repo --distupgrade-to-testdebs --do-not-verify-signatures --install-recommends -a -d stable chocolate-doom sudo piuparts --bindmount /tmp/repo --testdebs-repo /tmp/repo --distupgrade-to-testdebs --do-not-verify-signatures --install-recommends chocolate-doom_2.1.0-1_amd64.changes Please note that chocolate-doom_2.1.0-1 is the version currently in sid and -2 is the version I prepared locally. In this version the package has been split from 1 into 5 binary packages. If you need more information about the package, please find it prepared here: http://anonscm.debian.org/cgit/pkg-games/chocolate-doom.git --distupgrade-to-testdebs will be needed, perhaps with one or two -d distro options (even '-d sid -d sid' could work) As you can see from the command lines I posted above, I already tried various combinations of these parameters. The symptoms were always the same: With the -a parameter, apt always preferred to install the local package with the higher package revision. When passed the .changes file, apt was always forced to install exactly this specific version by passing the =$version suffix. - Fabian signature.asc Description: This is a digitally signed message part
Bug#784443: Cmake FindSSL module doesn't work anymore
Package: cmake Version: 3.0.2-1 Severity: Serious I Cmake maintainers, I honestly don't know where the bug belongs to, but I'm reporting against cmake. In my opinion this bug is becoming serious, since something in unstable changed and broke the builds the problem seems to be actually in the FindSSL.cmake module: = if (UNIX) find_package(PkgConfig QUIET) pkg_check_modules(_OPENSSL QUIET openssl) endif () this means that pkg-config should be available on the system, otherwise it will fail with something like: CMake Error at /usr/share/cmake-3.0/Modules/FindOpenSSL.cmake:293 (list): list GET given empty list Call Stack (most recent call first): CMakeLists.txt:86 (find_package) CMake Error at /usr/share/cmake-3.0/Modules/FindOpenSSL.cmake:294 (list): list GET given empty list Call Stack (most recent call first): CMakeLists.txt:86 (find_package) CMake Error at /usr/share/cmake-3.0/Modules/FindOpenSSL.cmake:296 (list): list GET given empty list Call Stack (most recent call first): CMakeLists.txt:86 (find_package) CMake Error at /usr/share/cmake-3.0/Modules/FindOpenSSL.cmake:298 (list): list GET given empty list Call Stack (most recent call first): CMakeLists.txt:86 (find_package) CMake Error at /usr/share/cmake-3.0/Modules/FindPackageHandleStandardArgs.cmake:136 (message): Could NOT find OpenSSL, try to set the path to OpenSSL root folder in the system variable OPENSSL_ROOT_DIR: Found unsuitable version .0.0`, but required is at least 1.0.0 (found /usr/lib/x86_64-linux-gnu/libssl.so;/usr/lib/x86_64-linux-gnu/libcrypto.so) Call Stack (most recent call first): /usr/share/cmake-3.0/Modules/FindPackageHandleStandardArgs.cmake:341 (_FPHSA_FAILURE_MESSAGE) /usr/share/cmake-3.0/Modules/FindOpenSSL.cmake:318 (find_package_handle_standard_args) CMakeLists.txt:86 (find_package) I guess with the old openssl some fallback code was in place, leading to the find of the version. Now with openssl 1.0.2a-1 in unstable/testing rebuild of the packages using it has become impossible. I'm adding manually pkg-config as B-D of casablanca package, but I think this should be a runtime dependency of cmake. (please forgive me and downgrade the bug if my analysis is actually wrong) cheers, Gianfranco -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#784330: game-data-packager without arguments refuses to run due to Python error
Le mardi 5 mai 2015, 19:37:36 Simon McVittie a écrit :
On 05/05/15 15:18, Alexandre Detiste wrote:
Would something like this be ok ?
+longname = self.longname.replace('ł','l')
Ugh, I'd rather not special-case the non-ASCII characters that happen to
appear in the names of games that we support...
Ok, it's ugly, but at least it's hidden in a function in util.py;
this function is also called by check_syntax.py .
but perhaps this is a necessary evil in the short term.
I had been updating the same system since 2002,
and was stuck with Latin-1 encoding;
it was quite a bit of work to rename all the files to uft8,
I understand some people never bother to change the locale.
This patch only implement ascii vs utf8; people still
using Latin-2 (Eastern European) encoding will
be served ascii Soltys too.
Proper handling would need a
str.encode(sys.stdout.encoding) in a try/except
block + testing with this locale configured; for little gain.
Having the wrapper shell script set something like
PYTHONIOENCODING=:replace if it detects
the C locale might also be a
reasonable workaround.
That replaces the characters with '?'s
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#783705: xserver-xorg-video-radeon: Weird X wakeup problem since Jessie upgrade
On Tue, May 05, 2015 at 09:06:40AM -0400, Alex Deucher wrote: On Wed, Apr 29, 2015 at 7:45 AM, Steve McIntyre st...@einval.com wrote: Package: xserver-xorg-video-radeon Version: 1:7.5.0-1 Severity: normal Hi folks, I upgrade my main office desktop to Jessie on Monday, and just about evrrything worked really well - just half a dozen oro so config files needed merging with new upstream etc. Painless! However, I'm now seeing a really odd problem with X on my machine. I've got an AMD graphics card, which Xorg.0.log tells me is a RADEON(0): Chipset: PITCAIRN (ChipID = 0x6810) and a DP+ connection to a lovely 27 NEC monitor. It works just fine when I'm using it, *but* when I leave it overnight and come in the next morning it doesn't want to wake up properly. I'm locking the screen with Xscreensaver and then turning off the monitor as I leave. In the morning, I turn on the screen and I don't get a display at all. I've wiggled the mouse, hit numlock on the keybard (the numlock led illuminates fine), etc., but no display. I've seen this kind of thing happen in the past on some machines, so I switch to VT1 and back to see if that helps. Still no display at all, either on console or under X. I log in remotely and I can see that the Xorg.0.log file has been updated with mode lines for the monitor, suggesting things have just woken up fine. But still no display. Here's the really weird thing: at this point, the monitor has basically locked up. It won't respond to the power/input/menu butttons at all, and is still showing the blue LED that says I have signal rather than switching to the amber no signal warning. Therefore, I can only assume there's a problem here with some weird invalid DP signal being produced. Yesterday, I gave up and rebooted after a few minutes - I had work to do. Today, I started searching for any other reports like this using my laptop. About ten minutes later while I was doing this (approximately, wasn't paying massive attention at this point), my desktop screen suddenly came to life and now it's working OK. I have no idea of where to even start debugging this. Help! If this is a regression, what previous version was working correctly? I was using an up-to-date wheezy installation previously, so that would be 1:6.14.4-8. Does the problem only happen when you physically power off the monitor? Ah, yes! In fact, it's the act of physically powering off the monitor that's the problem here. I can reproduce immediately by doing that. Last night, I locked the screen and left the monitor on and things were still working fine this morning when I came in. Does it come back ok when you let dpms kick in? Pass - I disabled dpms ages ago for unrelated reasons... How about when you physically disconnect the monitor from the computer? I tried that - if I unplugged the cable from the monitor, the monitor started responding to button presses ok but as soon as I reconnected it locked up again and still no display. Also, what screensavers are you using? There may be a problematic GL screensaver that's causing a GPU lockup. Can you try forcing a single known stable screensaver? I just use bumps under xscreensaver, and I've had that configured for years. -- Steve McIntyre, Cambridge, UK.st...@einval.com Can't keep my eyes from the circling sky, Tongue-tied twisted, Just an earth-bound misfit, I... -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#765522: ITP: elixir-lang
Control: retitle -1 ITP: elixir-lang -- dynamic, functional language on top of the Erlang VM Hi, is there any progress with this? I have an elixir packaging mostly ready at git://anonscm.debian.org/collab-maint/elixir-lang.git Do you mind if I take this over? I'm fine if any of you want to comaintain. -- Antonio Terceiro terce...@debian.org signature.asc Description: Digital signature
Bug#784447: x265: upstream has released x265 1.6 encoder please package it
Package: x265 Version: 1.5-1 Severity: wishlist Dear Maintainer, It seems the same date the a 1.6 release was also released. Please package it. It is at http://ftp.videolan.org/pub/videolan/x265/ Look forward to the new release. -- System Information: Debian Release: 8.0 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable'), (1, 'experimental'), (1, 'unstable'), (1, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 3.16.0-4-amd64 (SMP w/2 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages x265 depends on: ii libc6 2.19-18 ii libstdc++6 5.1.1-4 ii libx265-43 1.5-1 x265 recommends no packages. x265 suggests no packages. -- no debconf information -- Regards, Shirish Agarwal शिरीष अग्रवाल My quotes in this email licensed under CC 3.0 http://creativecommons.org/licenses/by-nc/3.0/ http://flossexperiences.wordpress.com EB80 462B 08E1 A0DE A73A 2C2F 9F3D C7A4 E1C4 D2D8 -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
