Bug#717176: ruby-passenger: CVE-2013-4136: insecure tmp files usage
I've prepared a debdiff that cherry-picks another upstream commit to properly fix CVE-2013-2119 and backports the two commits necessary to fix CVE-2013-4136. Cheers, Felix diff -Nru ruby-passenger-3.0.13debian/debian/changelog ruby-passenger-3.0.13debian/debian/changelog --- ruby-passenger-3.0.13debian/debian/changelog2013-05-30 12:41:00.0 +0200 +++ ruby-passenger-3.0.13debian/debian/changelog2013-07-20 19:22:25.0 +0200 @@ -1,3 +1,12 @@ +ruby-passenger (3.0.13debian-1.2) unstable; urgency=high + + * Non-maintainer upload. + * Cherry-pick another commit to properly fix CVE-2013-2119. + * Fix CVE-2013-4136: insecure tmp files usage. (Closes: #717176) +- Add CVE-2013-4136.patch, backported from upstream. + + -- Felix Geyer fge...@debian.org Sat, 20 Jul 2013 10:56:34 +0200 + ruby-passenger (3.0.13debian-1.1) unstable; urgency=low * Non-maintainer upload. diff -Nru ruby-passenger-3.0.13debian/debian/patches/CVE-2013-2119.patch ruby-passenger-3.0.13debian/debian/patches/CVE-2013-2119.patch --- ruby-passenger-3.0.13debian/debian/patches/CVE-2013-2119.patch 2013-05-30 09:31:09.0 +0200 +++ ruby-passenger-3.0.13debian/debian/patches/CVE-2013-2119.patch 2013-07-20 13:37:26.0 +0200 @@ -1,18 +1,8 @@ -From 0eaebb00f6b7327374069a7998064c68cc54e9f1 Mon Sep 17 00:00:00 2001 -From: Hongli Lai (Phusion) hon...@phusion.nl -Date: Tue, 28 May 2013 22:30:53 +0200 -Subject: [PATCH] Ensure that temporary files and directories didn't already - exist. +Description: Fix for CVE-2013-2119: insecure tmp files usage +Origin: upstream, https://github.com/phusion/passenger/commit/0eaebb00f6b7327374069a7998064c68cc54e9f1 + and https://github.com/phusion/passenger/commit/56d9d39fb522e0967acbde0bcec1afc37313ceb4 +Bug-Debian: http://bugs.debian.org/710351 - bin/passenger-install-nginx-module | 7 ++--- - lib/phusion_passenger/dependencies.rb | 32 -- - lib/phusion_passenger/standalone/command.rb| 9 +++--- - .../standalone/runtime_installer.rb| 7 ++--- - 4 files changed, 23 insertions(+), 32 deletions(-) - -diff --git a/bin/passenger-install-nginx-module b/bin/passenger-install-nginx-module -index 629240c..450252c 100755 --- a/bin/passenger-install-nginx-module +++ b/bin/passenger-install-nginx-module @@ -27,6 +27,7 @@ $LOAD_PATH.unshift(#{passenger_root}/lib) @@ -40,8 +30,6 @@ end private -diff --git a/lib/phusion_passenger/dependencies.rb b/lib/phusion_passenger/dependencies.rb -index e37a212..685b37d 100644 --- a/lib/phusion_passenger/dependencies.rb +++ b/lib/phusion_passenger/dependencies.rb @@ -22,6 +22,7 @@ @@ -136,8 +124,6 @@ end end if RUBY_PLATFORM =~ /linux/ -diff --git a/lib/phusion_passenger/standalone/command.rb b/lib/phusion_passenger/standalone/command.rb -index 8810427..b84909f 100644 --- a/lib/phusion_passenger/standalone/command.rb +++ b/lib/phusion_passenger/standalone/command.rb @@ -172,8 +172,11 @@ def determine_various_resource_locations(create_subdirs = true) @@ -163,8 +149,6 @@ if @options[:socket_file] ping_spec = [:unix, @options[:socket_file]] else -diff --git a/lib/phusion_passenger/standalone/runtime_installer.rb b/lib/phusion_passenger/standalone/runtime_installer.rb -index 730f776..31b6fd8 100644 --- a/lib/phusion_passenger/standalone/runtime_installer.rb +++ b/lib/phusion_passenger/standalone/runtime_installer.rb @@ -23,6 +23,7 @@ @@ -194,6 +178,109 @@ @plugin.call_hook(:runtime_installer_cleanup) if @plugin end --- -1.8.1.6 - +--- a/lib/phusion_passenger/platform_info.rb b/lib/phusion_passenger/platform_info.rb +@@ -21,6 +21,8 @@ + # OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN + # THE SOFTWARE. + ++require 'tmpdir' ++ + module PhusionPassenger + + # This module autodetects various platform-specific information, and +@@ -263,15 +265,12 @@ def self.try_compile(language, source, flags = nil) + else + raise ArgumentError,Unsupported language '#{language}' + end +- filename = File.join(#{tmpexedir}/passenger-compile-check-#{Process.pid}.c) +- File.open(filename, w) do |f| +- f.puts(source) +- end +- begin ++ Dir.mktmpdir(passenger., tmpexedir) do |dir| ++ filename = File.join(dir, check.c) ++ File.open(filename, w) do |f| ++ f.puts(source) ++ end + return system((#{compiler} #{flags} -c '#{filename}' -o '#{filename}.o') /dev/null 2/dev/null) +- ensure +- File.unlink(filename) rescue nil +- File.unlink(#{filename}.o) rescue nil + end +
Bug#715210: subtitleeditor: Wrong time stamp generation by [Edit]-[Insert After]
tags 715210 moreinfo thanks Hi, I can't reproduce your problem. When I use [Edit]-[Insert After] it works, see attached picture. Did I miss anything? Best, Philip attachment: subtitleeditor_insert_after.png
Bug#716801: udev: 70-persistent-net.rules isn't generated
No this is a bug. Why should interface renaming not work in virtual machines? I have the same problem. For various reasons we have always renamed our network interfaces to e0, e1, etc, both in physical and virtual machines (kvm). What is wwrong with that? /lib/udev/rules.d/75-persistent-net-generator.rules explicitly ignores virtual machine interfaces, this is probably why you call it a feature, but I fail to understand the reason behind this. Unfortunately it does not work just outcommenting the line with 52:54:00:*| 54:52:00:*, something else is working differently than in squeeze. Strangely this exception was also there in squeeze, where it somehow worked anyway. Neither in squeeze or wheezy is the file regenerated by 'udevadm trigger', since 75-persistent-net-generator.rules only receives a change action which it ignores. Strange. But in squeeze, the file is regenerated on boot if missing, not so in wheezy. I have no idea what causes it to be regenerated, or not. Any pointers appreciated. Regards Simon -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#717421: nmu: libxslt_1.1.28-1
Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: binnmu nmu libxslt_1.1.28-1 . ALL . experimental . -m Rebuild to drop libpython2.6 dependency. Hi, python-libxslt1/experimental depends on the no longer available libpython2.6. A rebuild gets rid of this dependency. The version in experimental is also not affected by the FTBFS bug #713471. Andreas -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#717422: aiccu: let the init script be somewhat useful for NetworkManager users too
Package: aiccu Version: 20070115-15.1 Severity: wishlist Dear Maintainer, the actual init script LSB headers cause the AICCU client to start earlier than NetworkManager: $ ls -1 /etc/rc2.d/S20* /etc/rc2.d/S20aiccu /etc/rc2.d/S20avahi-daemon /etc/rc2.d/S20bluetooth /etc/rc2.d/S20chrony /etc/rc2.d/S20cpufrequtils /etc/rc2.d/S20cron /etc/rc2.d/S20exim4 /etc/rc2.d/S20kerneloops /etc/rc2.d/S20network-manager [...] Because of that, on typical desktop systems relying on NM, the client starts when no network is available, then fails to resolve the TIC server address and exits: # grep -E '(aiccu|NetworkManager)' /var/log/syslog Jul 20 17:06:03 laptop aiccu[4992]: Couldn't resolve host tic.sixxs.net, service 3874 Jul 20 17:06:03 laptop aiccu[4992]: Couldn't connect to the TIC server tic.sixxs.net Jul 20 17:06:03 laptop aiccu[4992]: Couldn't retrieve first tunnel for the above reason, aborting Jul 20 17:06:03 laptop NetworkManager[5421]: info NetworkManager (version 0.9.8.0) is starting... [...] This makes the init script useless for NetworkManager users; by adding to it the LSB headers Should-Start: network-manager Should-Stop: network-manager the init script should start after NM, therefore the AICCU client should be correctly started at least when an auto connect global system connection profile (i.e. the default Auto eth0) is available, thus enabling NM users to have the tunnel automatically available at startup. The soft dependency should leave the behaviorunchangedfor non-NM users; since the connection is established only once at startup, this behavior should be compatible with the strict policiesenforced by SixXS, which forbid automatic reconnections. The only side effect would be that NM users not wanting to have the client started at every boot will have to disable AICCU_ENABLED in /etc/default/aiccu and will therefore be prevented to start the client with invoke-rc.d or running the init script directly. Thanks Maurizio Avogadro -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#707827: [python-imaging] Please enable WebP support
patch 707827 + patch thanks On Saturday 11 May 2013 16:49:00 Schrober wrote: WebP suppor tis currently not enabled for python imaging. It would be nice to have it to do some automated WebP scripting through python. The patch for the package is attacheddiff --git a/debian/changelog b/debian/changelog index 0cb88bc..d6421f1 100644 --- a/debian/changelog +++ b/debian/changelog @@ -1,3 +1,9 @@ +python-imaging (1.1.7+2.0.0-2) UNRELEASED; urgency=low + + * Build with WebP support + + -- Matthias Klose d...@debian.org Wed, 20 Mar 2013 16:44:01 -0700 + python-imaging (1.1.7+2.0.0-1) experimental; urgency=low * Pillow 2.0.0 release. diff --git a/debian/control b/debian/control index d9772a9..26a4016 100644 --- a/debian/control +++ b/debian/control @@ -7,6 +7,7 @@ Build-Depends: debhelper, tk8.5-dev, dpkg-dev (= 1.16.1~), python3-all-dev (= 3.3), python3-all-dbg, python3-setuptools, python-tk, python-tk-dbg, python3-tk, python3-tk-dbg (= 3.3), libsane-dev, libfreetype6-dev, libjpeg8-dev, zlib1g-dev, liblcms1-dev, + libwebp-dev, Build-Conflicts: python-numarray Standards-Version: 3.9.4
Bug#717423: libfontconfig1:amd64: C.UTF-8 locale causes warning to be printed on standard error
Package: libfontconfig1 Version: 2.10.2-2 Severity: normal Tags: patch When the C.UTF-8 locale is used (i.e. LC_CTYPE=C.UTF-8 or LANG=C.UTF-8), programs using fontconfig print the message Fontconfig warning: ignoring C.UTF-8: not a valid language tag on standard error serveral times. For example, Emacs prints the warning ten times during startup. The attached patch fixes the issue for me. It is based on the assumption that C.UTF-8 should be treated like the other locale names built into the C library (C and POSIX). Best regards, Martin -- System Information: Debian Release: jessie/sid APT prefers testing APT policy: (500, 'testing'), (200, 'unstable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.9-1-amd64 (SMP w/4 CPU cores) Locale: LANG=C, LC_CTYPE=C.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages libfontconfig1:amd64 depends on: ii fontconfig-config 2.10.2-2 ii libc6 2.17-7 ii libexpat1 2.1.0-4 ii libfreetype6 2.4.9-1.1 ii multiarch-support 2.17-7 libfontconfig1:amd64 recommends no packages. libfontconfig1:amd64 suggests no packages. -- no debconf information diff -Nur a/src/fclang.c b/src/fclang.c --- a/src/fclang.c 2012-10-30 01:53:37.0 +0100 +++ b/src/fclang.c 2013-07-20 19:49:14.352195363 +0200 @@ -188,6 +188,7 @@ return NULL; if (FcStrCmpIgnoreCase (lang, (const FcChar8 *)C) == 0 || + FcStrCmpIgnoreCase (lang, (const FcChar8 *)C.UTF-8) == 0 || FcStrCmpIgnoreCase (lang, (const FcChar8 *)POSIX) == 0) { result = FcStrCopy ((const FcChar8 *)en);
Bug#677727: [3.2-3.3 regression] mceusb: only every second keypress is recognised
On 10.07.2013 17:31, Moritz Muehlenhoff wrote: reassign 677727 src:linux thanks On Sun, Jul 15, 2012 at 03:25:18PM +0200, Michael Schmitt wrote: Did this issue drop under everybodys radar? :) Does this still occur with 3.9 from unstable or 3.10-rc7 from experimental? I did install 3.10-1-686-pae a few minutes ago... and yes, still the same issue. I tried asking on the lirc-ml to no avail sometime around last year, so I am lost. Seriously, what can I do to help tracking the issue down? I really can't believe I may be the only one experiencing that issue as I could reproduce it on another box. regards Michael -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#681889: libguestfs0 has too many dependencies?
To: Thomas Koch: I was forced to install vim! This is insulting for an emacs user! guestfish needs vim to implement the 'vi' command: http://libguestfs.org/guestfish.1.html#vi (and emacs to implement the 'emacs' command). I don't know why libguestfs0 would depend on this however. Seriously. The dependency list of libguestfs0 is very surprising. Could you please check whether libguestfs0 could be split up in smaller binary packages with only minimal dependencies? If that shouldn't be possible (how?), could you please add a short explanation of the dependencies in the package description and a longer one in a README.Debian? This is a pretty common question, and therefore I have added the following section to the FAQ http://libguestfs.org/guestfs-faq.1.html#libguestfs-has-a-really-long-list-of-dependencies- section: Libguestfs has a really long list of dependencies It would be possible to package libguestfs for Debian differently, and although I doubt that you'd be happier with the results, let me know if any of the alternatives suggested in that section are better for you. One thing which is unfortunately *not* possible at this time is to split libguestfs up into different capabilities, eg. enabling only XFS or NTFS by installing a particular subpackage. Having said that, in the Debian package right now there are probably dependencies which are not needed. In particular I don't think that the appliance dependencies are needed on the main package. To: Laurent Bigonville: I might be wrong here, but isn't libguestfs running all the commands into an appliance? Shouldn't all these dependencies installed only inside the appliance? Or is there a mode where libguestfs can run commands on the host? Not quite either of these. Libguestfs builds an appliance using files from the host (eg. /sbin/mkfs), then runs these commands in the appliance only, never on the host. It therefore needs them to be present on the host, so it can copy them into the appliance to run them. The supermin man page explains all this, see: http://libguestfs.org/supermin.8.html#SUPERMIN-APPLIANCES (Note that supermin was previously called febootstrap; it's the same thing) - - - I hope this at least explains some of what's going on, even if it doesn't help much :-( Rich. -- Richard Jones, Virtualization Group, Red Hat http://people.redhat.com/~rjones virt-df lists disk usage of guests without needing to install any software inside the virtual machine. Supports Linux and Windows. http://people.redhat.com/~rjones/virt-df/ -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#712439: [Pkg-systemd-maintainers] Bug#712439: systemd: encrypted swap not brought up, delays boot
On Sat, 2013-07-20 at 17:21 +0200, Michael Biebl wrote: Could you post your partition / lvm /cryptsetup layout, your fstab and crypttab. Layout as udisks sees it: /org/freedesktop/UDisks2/Manager: org.freedesktop.UDisks2.Manager: Version:2.1.0 /org/freedesktop/UDisks2/block_devices/dm_2d0: org.freedesktop.UDisks2.Block: Configuration: [('fstab', {'fsname': b'/dev/disk/by-id/dm-name-swap0', 'dir': b'none', 'type': b'swap', 'opts': b'noauto', 'freq': 0, 'passno': 0})] CryptoBackingDevice:'/' Device: /dev/dm-0 DeviceNumber: 65024 Drive: '/' HintAuto: false HintIconName: HintIgnore: false HintName: HintPartitionable: false HintSymbolicIconName: HintSystem: true Id: by-id-dm-name-swap0 IdLabel: IdType: IdUUID: IdUsage: IdVersion: MDRaid: '/' MDRaidMember: '/' PreferredDevice:/dev/mapper/swap0 ReadOnly: false Size: 2146418176 Symlinks: /dev/disk/by-id/dm-name-swap0 /dev/disk/by-id/dm-uuid-CRYPT-PLAIN-swap0 /dev/mapper/swap0 /org/freedesktop/UDisks2/block_devices/sda: org.freedesktop.UDisks2.Block: Configuration: [] CryptoBackingDevice:'/' Device: /dev/sda DeviceNumber: 2048 Drive: '/org/freedesktop/UDisks2/drives/VBOX_HARDDISK_VB64621a99_3c0955c7' HintAuto: false HintIconName: HintIgnore: false HintName: HintPartitionable: true HintSymbolicIconName: HintSystem: true Id: by-id-ata-VBOX_HARDDISK_VB64621a99-3c0955c7 IdLabel: IdType: IdUUID: IdUsage: IdVersion: MDRaid: '/' MDRaidMember: '/' PreferredDevice:/dev/sda ReadOnly: false Size: 10737418240 Symlinks: /dev/disk/by-id/ata-VBOX_HARDDISK_VB64621a99-3c0955c7 /dev/disk/by-id/scsi-SATA_VBOX_HARDDISK_VB64621a99-3c0955c7 org.freedesktop.UDisks2.PartitionTable: Type: gpt /org/freedesktop/UDisks2/block_devices/sda1: org.freedesktop.UDisks2.Block: Configuration: [] CryptoBackingDevice:'/' Device: /dev/sda1 DeviceNumber: 2049 Drive: '/org/freedesktop/UDisks2/drives/VBOX_HARDDISK_VB64621a99_3c0955c7' HintAuto: false HintIconName: HintIgnore: false HintName: HintPartitionable: true HintSymbolicIconName: HintSystem: true Id: by-id-ata-VBOX_HARDDISK_VB64621a99-3c0955c7-part1 IdLabel: IdType: IdUUID: IdUsage: IdVersion: MDRaid: '/' MDRaidMember: '/' PreferredDevice:/dev/sda1 ReadOnly: false Size: 1048576 Symlinks: /dev/disk/by-id/ata-VBOX_HARDDISK_VB64621a99-3c0955c7-part1 /dev/disk/by-id/scsi-SATA_VBOX_HARDDISK_VB64621a99-3c0955c7-part1 org.freedesktop.UDisks2.Partition: Flags: 0 IsContained:false IsContainer:false Name: Number: 1 Offset: 1048576 Size:
Bug#717424: rhash-bindings: FTBFS: sh: debian/librhash1.0-cil/DEBIAN/clilibs: No such file or directory
Package: rhash-bindings Version: 1.2.10-1 Severity: serious Justification: fails to build from source Hi, rhash-bindings fails to build in experimental: [...] debian/rules binary-indep make[1]: Entering directory `/tmp/buildd/rhash-bindings-1.2.10' BINDINGS=mono python dh binary-indep --with=python2 --with=cli dh_clistrip -i dh_cligacpolicy -i dh_cligacpolicy: Warning! No Build-Depends(-Indep) on cli-common-dev (= 0.5.7)! dh_makeclilibs -i sh: debian/librhash1.0-cil/DEBIAN/clilibs: No such file or directory dh_makeclilibs: cat debian/librhash1.0-cil.clilibs debian/librhash1.0-cil/DEBIAN/clilibs returned exit code 1 make[1]: *** [binary-indep] Error 2 make[1]: Leaving directory `/tmp/buildd/rhash-bindings-1.2.10' make: *** [binary] Error 2 dpkg-buildpackage: error: fakeroot debian/rules binary gave error exit status 2 Andreas -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#717401: sosreport: fails to install: SyntaxError: invalid syntax
On Sat, Jul 20, 2013 at 01:54:41PM +0200, Axel Beckert wrote: Package: sosreport Version: 2.3~git20130509-1 Severity: grave Dear Maintainer, sosreport fails to install on both machines where I tried to install it, 1x i386 and 1x amd64: Setting up sosreport (2.3~git20130509-1) ... File /usr/lib/python2.7/dist-packages/sos/plugins/logs.py, line 35 )] ^ SyntaxError: invalid syntax dpkg: error processing sosreport (--configure): subprocess installed post-installation script returned error exit status 101 -- System Information: Debian Release: jessie/sid APT prefers unstable APT policy: (990, 'unstable'), (900, 'testing'), (899, 'testing-proposed-updates'), (600, 'stable'), (500, 'proposed-updates'), (200, 'experimental') Architecture: i386 (i686) Kernel: Linux 3.10-1-686-pae (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 Versions of packages sosreport depends on: ii python 2.7.5-2 Thanks Axel, I will get a debian system installed this weekend and double check. I couldve swarn all CI tests were green before submitting it. Thanks for the heads up! Adam -- _ _ ___| |_ ___| |_ ___ ___ |_ -| _| . | '_| -_|_ -| |___|_| |___|_,_|___|___| adam.sto...@ubuntu.com Don't salt your green beans before you try them, some may think you make rash decisions. signature.asc Description: Digital signature
Bug#717425: nmu: avogadro_1.1.0-4
Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: binnmu nmu avogadro_1.1.0-4 . ALL . experimental . -m Rebuild for new sip4 ABI. python-avogadro/experimental depends o the no longer available sip-api-9.2, so rebuild to pick up sip-api-10.0 instead. Andreas -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#717426: nmu: ben_0.6.4
Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: binnmu nmu ben_0.6.4 . ALL . -m Rebuild against updated libtyxml-ocaml and libpcre-ocaml. libben-ocaml depends on the no longer available libpcre-ocaml-xu8a5 libtyxml-ocaml-esbp7 so rebuild to pick up the new ones. Andreas -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#706830: transition: php5 5.5
Followup-For: Bug #706830 nmu owfs_2.9p0-1 . ALL . experimental . -m Rebuild against php5 5.5 nmu zeroc-ice_3.5~beta1-4 . ALL . experimental . -m Rebuild against php5 5.5 There have been binNMUs or uploads in sid, so let's make them again installable in experimental, too. Buildability verified on amd64. Andreas -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#717427: systemd: Add handling of Message Catalogs to provide additional information for log entries
Package: systemd Version: 204-1 Severity: wishlist Tags: patch The attached patch adds handling of Message Catalog files in /usr/lib/systemd/catalog. This compiles the files from /usr/lib/systemd/catalog into a binary database, which is used by journalctl to provide additional information for log entries. journalctl only uses the binary database in /var/lib/systemd/catalog/database. Call journalctl --update-catalog in systemd.postinst and when triggered by dpkg to update the Message Catalog database. Also add systemd.postrm to remove the database on purge. See http://www.freedesktop.org/wiki/Software/systemd/catalog/ -- System Information: Debian Release: jessie/sid APT prefers unstable APT policy: (990, 'unstable'), (103, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.9.10-fglrx2 (SMP w/4 CPU cores) Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages systemd depends on: ii initscripts 2.88dsf-43 ii libacl1 2.2.52-1 ii libaudit01:1.7.18-1.1 ii libc62.17-7 ii libcap2 1:2.22-1.2 ii libcryptsetup4 2:1.6.1-1 ii libdbus-1-3 1.6.12-1 ii libgcrypt11 1.5.2-3 ii libkmod2 9-3 ii liblzma5 5.1.1alpha+20120614-2 ii libpam0g 1.1.3-9 ii libselinux1 2.1.13-2 ii libsystemd-daemon0 204-1 ii libsystemd-journal0 204-1 ii libudev1 204-1 ii libwrap0 7.6.q-24 ii udev 204-1 ii util-linux 2.20.1-5.5 Versions of packages systemd recommends: ii libpam-systemd 204-1 Versions of packages systemd suggests: pn systemd-ui none -- Configuration Files: /etc/systemd/journald.conf changed [not included] /etc/systemd/logind.conf changed [not included] -- no debconf information From d355b469246d912fa8017f3fa81bbd449b39f76d Mon Sep 17 00:00:00 2001 From: Daniel Schaal farb...@web.de Date: Sat, 20 Jul 2013 06:58:42 +0200 Subject: [PATCH] Add handling of Message Catalog files. This compiles the files from /usr/lib/systemd/catalog into a binary database, which is used by journalctl to provide additional information for log entries. journalctl only uses the binary database in /var/lib/systemd/catalog/database. Call journalctl --update-catalog in systemd.postinst and when triggered by dpkg to update the Message Catalog database. Also add systemd.postrm to remove the database on purge. See http://www.freedesktop.org/wiki/Software/systemd/catalog/ --- debian/systemd.postinst | 13 + debian/systemd.postrm | 12 debian/systemd.triggers | 1 + 3 files changed, 26 insertions(+) create mode 100644 debian/systemd.postrm create mode 100644 debian/systemd.triggers diff --git a/debian/systemd.postinst b/debian/systemd.postinst index 624cea1..77a8b55 100644 --- a/debian/systemd.postinst +++ b/debian/systemd.postinst @@ -8,6 +8,16 @@ _systemctl() { fi } +_update_catalog() { +journalctl --update-catalog || true +} + +# Update Message Catalogs database in response to dpkg trigger +if [ $1 = triggered ]; then +_update_catalog +exit 0 +fi + # Cleanup state files from the auto-enabler which we used in wheezy if dpkg --compare-versions $2 lt 204-1; then rm -f /var/lib/systemd/enabled-units @@ -69,4 +79,7 @@ fi systemd-machine-id-setup +# initial update of the Message Catalogs database +_update_catalog + #DEBHELPER# diff --git a/debian/systemd.postrm b/debian/systemd.postrm new file mode 100644 index 000..f764cdc --- /dev/null +++ b/debian/systemd.postrm @@ -0,0 +1,12 @@ +#!/bin/sh + +set -e + +case $1 in +purge) +rm -f /var/lib/systemd/catalog/database +rmdir --ignore-fail-on-non-empty /var/lib/systemd/catalog 2 /dev/null || true +;; +esac + +#DEBHELPER# diff --git a/debian/systemd.triggers b/debian/systemd.triggers new file mode 100644 index 000..69246ec --- /dev/null +++ b/debian/systemd.triggers @@ -0,0 +1 @@ +interest-noawait /usr/lib/systemd/catalog -- 1.8.3.2
Bug#717428: ITP: libgisi -- communication library for isi modems
Package: wnpp Severity: wishlist Owner: Sebastian Reichel s...@debian.org * Package name: libgisi Version : 0.1.0 Upstream Author : freesmartphone.org Team * URL : http://www.freesmartphone.org/ * License : GPL Programming Lang: C, Vala Description : communication library for isi modems This project contains the following parts: * libgisi (standalone), a low level library for communicating with ISI devices, such as the modem found in some Nokia devices. * vala bindings for libgisi. * protocol definitions and enumerations. * libgisicomm, a high level library for communicating with ISI modem devices. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#717429: Please support systemd in the initramfs
Package: systemd Version: 204-1 Severity: wishlist systemd supports running from within the initramfs, and it adds various features when doing so, such as timing support, or cleaner support for encrypted filesystems. Please consider making use of this. - Josh triplett -- System Information: Debian Release: jessie/sid APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 3.10-1-amd64 (SMP w/4 CPU cores) Locale: LANG=C.UTF-8, LC_CTYPE=C.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages systemd depends on: ii initscripts 2.88dsf-43 ii libacl1 2.2.52-1 ii libaudit01:1.7.18-1.1 ii libc62.17-7 ii libcap2 1:2.22-1.2 ii libcryptsetup4 2:1.6.1-1 ii libdbus-1-3 1.6.12-1 ii libgcrypt11 1.5.2-3 ii libkmod2 9-3 ii liblzma5 5.1.1alpha+20120614-2 ii libpam0g 1.1.3-9 ii libselinux1 2.1.13-2 ii libsystemd-daemon0 44-12 ii libsystemd-journal0 204-1 ii libudev1 204-1 ii libwrap0 7.6.q-24 ii udev 204-1 ii util-linux 2.20.1-5.5 Versions of packages systemd recommends: pn libpam-systemd none Versions of packages systemd suggests: pn systemd-ui 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#715529: can not start goobox
tags 715529 + moreinfo tags 715529 + unreproducible thanks Hello Picca, On Sun, Jul 14, 2013 at 07:14:13PM +0200, Helge Kreutzmann wrote: Hello Picca, On Wed, Jul 10, 2013 at 07:58:10AM +0200, Picca Frédéric-Emmanuel wrote: Package: goobox Version: 3.1.1-1 Severity: serious Hello, when I try to start goobox, a windows appear and almost immediately this windows is closed and goobox is stopped. So I can not start it. Thanks for your report. I'll investigate. Sorry for taking so long. My test machine is now (again) operational. I can launch goobox just fine. (The icons are not looking nice, I see about that, though). Is there anything special for your machine? How is your cd drive connected (i.e. what is /dev/cdrom or /dev/cdrom1 pointing to)? Did the previous (Wheezy) version of goobox work? Can you run other cd-players, e.g. sound-jouicer? Could you run strace goobox and send me the last say 100 lines? Thanks! Greetings Helge -- Dr. Helge Kreutzmann deb...@helgefjell.de Dipl.-Phys. http://www.helgefjell.de/debian.php 64bit GNU powered gpg signed mail preferred Help keep free software libre: http://www.ffii.de/ signature.asc Description: Digital signature
Bug#717430: libossp-uuid-perl: Long description wrongly calls Data::UUID not DFSG-free
Package: libossp-uuid-perl Version: 1.6.2-1.3 Severity: minor Long description of libossp-uuid-perl contains the following: The Debian package provides also Data::UUID interface so OSSP::uuid can be used as free replacement for non-DFSG Perl module. Data::UUID is licensed with (a derivation of) the DFSG-free NTP license. The text does not exist in upstream project description or POD files. Seemingly it originates from the time when the package was created, as its ITP (bug#283493) contains the following: The Data::UUID module is not free software (no license file) That ITP was filed in 2004, and indeed Data::UUID changelog includes this interesting entry: 1.149 Sat Nov 1 12:31 2008 - added explicit BSD license; code is basically RFC4122 + patches So apparently that text in long description of libossp-uuid-perl has been wrong since more than 4 years: Please drop that paragraph. Kind regards, - Jonas -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#717431: lua-mode: lua-indent-level safe-local-variable
Package: lua-mode Version: 20110121-1 Severity: wishlist File: /usr/share/emacs/site-lisp/lua-mode/lua-mode.el It'd be good if lua-mode.el had (put 'lua-indent-level 'safe-local-variable 'integerp) so that it's possible to have a per-file lua-indent-level like foo.lua below without being prompted The local variables list in foo.lua contains values that may not be safe (*). #!/usr/bin/lua for y=1,5 do io.write(Hello\n) end -- Local variables: -- lua-indent-level: 5 -- End: -- System Information: Debian Release: 7.0 APT prefers unstable APT policy: (990, 'unstable') Architecture: i386 (i686) Kernel: Linux 2.6.32-5-486 Locale: LANG=en_AU, LC_CTYPE=en_AU (charmap=ISO-8859-1) Shell: /bin/sh linked to /bin/dash Versions of packages lua-mode depends on: ii emacs21 [emacsen]21.4a+1-5.7 ii emacs22-gtk [emacsen]22.3+1-1.2 ii emacs23-lucid [emacsen] 23.4+1-4 ic emacs24 [emacsen]24.3+1-1 ii emacs24-lucid [emacsen] 24.3+1-1 ii xemacs21-mule [emacsen] 21.4.22-4 lua-mode recommends no packages. lua-mode suggests no packages. -- no debconf information
Bug#717432: nmu: libuuid-perl_0.02-5+exp1
Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: binnmu nmu libuuid-perl_0.02-5+exp1 . ALL . experimental . -m Rebuild against perl 5.18 dw libuuid-perl_0.02-5+exp1 . ALL . experimental . -m perl (= 5.18) perlapi-5.16.2 does no longer exist on most architectures ... Andreas -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#717429: Please support systemd in the initramfs
Am 20.07.2013 21:51, schrieb Josh Triplett: Package: systemd Version: 204-1 Severity: wishlist systemd supports running from within the initramfs, and it adds various features when doing so, such as timing support, or cleaner support for encrypted filesystems. Please consider making use of this. Most likely the wrong component. As you said, systemd supports being run from the initramfs. This most likely needs to be integrated into initramfs-tools directly. I don't think the hooks support in intramfs-tools is flexible enough that this can be done with a few hooks provided by systemd. I understand your wish, but this is not something which can be solved in the systemd package afaics. Michael -- 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#716865: Missing header file?
It looks like the 'pk_control_set_root_async' function was at some point declared in 'pk_control.h' in package 'libpackagekit-glib2-dev' but it doesn't seem to be there anymore. Also, I can't find any the symbol in the .so library from 'libpackagekit-glib2-16'. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#717433: debian cross build produces a unusable perl-dev package
Package: perl Version: 5.14.2-21 Severity: minor that was using wookey's early patches / backports for cross building and multiarch. Maybe check that with the current version again. seen with ossp-uuid # build perl bindings cd perl; \ /usr/bin/perl Makefile.PL INSTALLDIRS=vendor COMPAT=1; \ make CC=cc OPTIMIZE=; \ make test Checking if your kit is complete... Looks good Have /usr/lib/aarch64-linux-gnu/perl/5.14.2 Want /usr/lib/perl/5.14 Your perl and your Config.pm seem to have different ideas about the architecture they are running on. Perl thinks: [5.14.2] Config says: [aarch64-linux-gnu-thread-multi] This may or may not cause problems. Please check your installation of perl if you have problems building this extension. Warning: -L../.libs changed to -L/root/ossp-uuid-1.6.2/perl/../.libs Warning: -L.. changed to -L/root/ossp-uuid-1.6.2/perl/.. Writing Makefile for OSSP::uuid Writing MYMETA.yml make[2]: Entering directory `/root/ossp-uuid-1.6.2/perl' make[2]: *** No rule to make target `/usr/lib/perl/5.14/Config.pm', needed by `Makefile'. Stop. ... and libterm-size-perl ... Checking if your kit is complete... Looks good Have /usr/lib/aarch64-linux-gnu/perl/5.14.2 Want /usr/lib/perl/5.14 Your perl and your Config.pm seem to have different ideas about the architecture they are running on. Perl thinks: [5.14.2] Config says: [aarch64-linux-gnu-thread-multi] This may or may not cause problems. Please check your installation of perl if you have problems building this extension. and Config.pm has archname = 'aarch64-linux-gnu-thread-multi', -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#717429: Please support systemd in the initramfs
On Sat, Jul 20, 2013 at 10:29:18PM +0200, Michael Biebl wrote: Am 20.07.2013 21:51, schrieb Josh Triplett: Package: systemd Version: 204-1 Severity: wishlist systemd supports running from within the initramfs, and it adds various features when doing so, such as timing support, or cleaner support for encrypted filesystems. Please consider making use of this. Most likely the wrong component. As you said, systemd supports being run from the initramfs. This most likely needs to be integrated into initramfs-tools directly. I don't think the hooks support in intramfs-tools is flexible enough that this can be done with a few hooks provided by systemd. I don't know that it makes sense to integrate into initramfs-tools either, without significant rework of initramfs-tools. systemd shouldn't try to run initramfs-tools hooks; it should run service files, and it already has service files for half of what initramfs-tools normally does (cryptsetup, lvm, udev, etc). I agree that this isn't something to be solved entirely within systemd, but I do think it'll likely require changes to the systemd package as well. - Josh Triplett -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#717434: RFA: socat -- multipurpose relay for bidirectional data transfer
Package: wnpp Severity: normal X-Debbugs-CC: debian-de...@lists.debian.org I intend to orphan socat in the next few weeks and would like someone to adopt the package as it is still useful to many. I no longer have the time nor motivation/need to continue to maintain it, therefore I am formally requesting its adoption. Description-en: multipurpose relay for bidirectional data transfer Socat (for SOcket CAT) establishes two bidirectional byte streams and transfers data between them. Data channels may be files, pipes, devices (terminal or modem, etc.), or sockets (Unix, IPv4, IPv6, raw, UDP, TCP, SSL). It provides forking, logging and tracing, different modes for interprocess communication and many more options. . It can be used, for example, as a TCP relay (one-shot or daemon), as an external socksifier, as a shell interface to Unix sockets, as an IPv6 relay, as a netcat and rinetd replacement, to redirect TCP-oriented programs to a serial line, or to establish a relatively secure environment (su and chroot) for running client or server shell scripts inside network connections. Socat supports sctp as of 1.7.0. Thanks, Chris
Bug#717429: Please support systemd in the initramfs
Am 20.07.2013 22:44, schrieb Josh Triplett: I agree that this isn't something to be solved entirely within systemd, but I do think it'll likely require changes to the systemd package as well. What changes do you have in mind here? Really, this needs to be solved within the initramfs generators, afaics. Latest dracut releases have support / are designed to run systemd in the initramfs. If initramfs-tools can be changed to utilize systemd, I honestly don't know. I just think you are talking to the wrong people here. Michael -- 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#516562: Cannot find a question for phpmyadmin/dbconfig-install
Package: dbconfig-common Version: 1.8.47+nmu1 Followup-For: Bug #516562 -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Control: unmerge 516562 Control: retitle 516562 dbconfig-common: leaves debconf database in inconsistent state During my investigation of bug 476946, I encountered this problem as well. It is not the same as the merged bugs, therefore unmerging. I have not been able yet to determine when it happens exactly, but it seems that under certain conditions, the questions of a dbc controled package are unregistered, but the corresponding template is not. When that happens, you can not preseed a not yet (or not anymore) existing question as the creation of the question fails. I could fix this issue by modifying debconf-set-selection to unconditionally create a new template, as that enforces the question to be regenerated. If I do that I do get warnings about the debconf database being in an inconsistent state: debconf: warning: possible database corruption. Will attempt to repair by adding back missing question cacti/db/app-user I seem to be able to do this reproducible now by installing my package cacti with preseeding: cacti cacti/db/app-user string cacti cacti cacti/db/dbname string cacti cacti cacti/dbconfig-install boolean true cacti cacti/internal/skip-preseed boolean true cacti cacti/mysql/admin-pass password real-passwd-here cacti cacti/mysql/app-passpassword blablabla cacti cacti/webserver select apache2 and purging it afterwards after preseeding it with the same seed and letting dbc also purge the database. After that I can not preseed any normal cacti variable until I install it again. I don't assume this last state is normal to reach as I preseed an internal variable, but at least I get to the same symptom as the original bug report. I will continue to investigate. - -- System Information: Debian Release: 7.1 APT prefers stable APT policy: (500, 'stable'), (99, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.2.0-4-amd64 (SMP w/1 CPU core) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages dbconfig-common depends on: ii debconf [debconf-2.0] 1.5.49 ii ucf3.0025+nmu3 dbconfig-common recommends no packages. Versions of packages dbconfig-common suggests: ii mysql-client-5.5 [virtual-mysql-client] 5.5.31+dfsg-0+wheezy1 - -- debconf information excluded -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.12 (GNU/Linux) iQEcBAEBCAAGBQJR6vmvAAoJEJxcmesFvXUKkQ0IALKrnJ60QlZUyar3PrGt2Kym lKFWMlaVs/B+scF30X0KTV/7zpiNAGiKDZVq3GV48UuC/5BLJjZkGFkF2gbNZrR0 pqyRq1H7UlJwG3AbZKNpQFbPGHCI8M/JQCb1hWrJ1/pfFBiIsetG2VgoE7JNgiaY sYdPHxBoF6FLMKrjfn7+mxsMY2i5bX5NKnH6x+ZXezXC5Z+FfI4pq7tXiAPjoKY2 9URFy0jKAyGZYZkddePEIu+a6ROcLxw0RXXSFkKh8L32zv1VSDVyj/1nampyiK2l P9DH/Fb5JyESgzG2z0bn/HS9FXGpOaaB8ip0ODxUCVrhdHKuM2Nyqtm1NHrcfC0= =9Ldx -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#677727: [3.2-3.3 regression] mceusb: only every second keypress is recognised
On Sat, 2013-07-20 at 20:56 +0200, Michael Schmitt wrote: On 10.07.2013 17:31, Moritz Muehlenhoff wrote: reassign 677727 src:linux thanks On Sun, Jul 15, 2012 at 03:25:18PM +0200, Michael Schmitt wrote: Did this issue drop under everybodys radar? :) Does this still occur with 3.9 from unstable or 3.10-rc7 from experimental? I did install 3.10-1-686-pae a few minutes ago... and yes, still the same issue. I tried asking on the lirc-ml to no avail sometime around last year, so I am lost. Seriously, what can I do to help tracking the issue down? I really can't believe I may be the only one experiencing that issue as I could reproduce it on another box. Can you try a git bisect between v3.2 and v3.3-rc6? http://git-scm.com/book/en/Git-Tools-Debugging-with-Git#Binary-Search This requires a git checkout of the upstream kernel sources... and a lot of patience. Ben. -- Ben Hutchings Humans are not rational beings; they are rationalising beings. signature.asc Description: This is a digitally signed message part
Bug#717435: sympa: fails to install if ca-certificates trigger has never been run
Package: sympa Version: 6.1.11~dfsg-5 Severity: serious User: debian...@lists.debian.org Usertags: piuparts Hi, during a test with piuparts I noticed your package failed to install. As per definition of the release team this makes the package too buggy for a release, thus the severity. Installing sympa in a minimal system using apt-get install sympa fails, but changing this to apt-get install ca-certificates apt-get install sympa succeeds. This seems to indicate that sympa depends on a successful run of the ca-certificates trigger *before* configuring sympa ... no idea how this can be achieved. Cc:ed the ca-certificates maintainer. From the attached log (scroll to the bottom...): Setting up sympa (6.1.11~dfsg-5) ... Adding system user: sympa. invoke-rc.d: policy-rc.d denied execution of stop. /etc/sympa/sympa.conf file has been created /etc/sympa/wwsympa.conf file has been created dbconfig-common: writing config to /etc/dbconfig-common/sympa.conf Creating config file /etc/dbconfig-common/sympa.conf with new version granting access to database sympa for sympa@localhost: success. verifying access for sympa@localhost: success. creating database sympa: success. verifying database sympa exists: success. populating database via sql... done. dbconfig-common: flushing administrative password Not configuring Web server. info List::get_user_db() Sympa not setup to use DBI err Language::SetLang() Failed to setlocale(en_US) ; you either have a problem with the catalogue .mo files or you should extend available locales in your /etc/locale.gen (or /etc/sysconfig/i18n) file err Language::SetLang() Failed to setlocale(en_US) ; you either have a problem with the catalogue .mo files or you should extend available locales in your /etc/locale.gen (or /etc/sysconfig/i18n) file err Language::SetLang() Failed to setlocale(en_US) ; you either have a problem with the catalogue .mo files or you should extend available locales in your /etc/locale.gen (or /etc/sysconfig/i18n) file info Configuration file read, default log level 0 notice Upgrade::probe_db() Table list_table created in database sympa info Upgrade::probe_db() Field 'robot_exclusion' (table 'exclusion_table' ; database 'sympa') was NOT found. Attempting to add it... info Upgrade::probe_db() Field robot_exclusion added to table exclusion_table info Upgrade::probe_db() Missing expected primary key : robot_exclusion info Upgrade::probe_db() Table exclusion_table, PRIMARY KEY dropped info Upgrade::probe_db() Table exclusion_table, PRIMARY KEY set on list_exclusion,user_exclusion,robot_exclusion info Upgrade::probe_db() Field 'creation_email_list' (table 'list_table' ; database 'sympa') was NOT found. Attempting to add it... info Upgrade::probe_db() Field creation_email_list added to table list_table info Upgrade::probe_db() Field 'creation_epoch_list' (table 'list_table' ; database 'sympa') was NOT found. Attempting to add it... info Upgrade::probe_db() Field creation_epoch_list added to table list_table info Upgrade::probe_db() Field 'editors_list' (table 'list_table' ; database 'sympa') was NOT found. Attempting to add it... info Upgrade::probe_db() Field editors_list added to table list_table info Upgrade::probe_db() Field 'name_list' (table 'list_table' ; database 'sympa') was NOT found. Attempting to add it... info Upgrade::probe_db() Field name_list added to table list_table info Upgrade::probe_db() Field 'owners_list' (table 'list_table' ; database 'sympa') was NOT found. Attempting to add it... info Upgrade::probe_db() Field owners_list added to table list_table info Upgrade::probe_db() Field 'path_list' (table 'list_table' ; database 'sympa') was NOT found. Attempting to add it... info Upgrade::probe_db() Field path_list added to table list_table info Upgrade::probe_db() Field 'robot_list' (table 'list_table' ; database 'sympa') was NOT found. Attempting to add it... info Upgrade::probe_db() Field robot_list added to table list_table info Upgrade::probe_db() Field 'status_list' (table 'list_table' ; database 'sympa') was NOT found. Attempting to add it... info Upgrade::probe_db() Field status_list added to table list_table info Upgrade::probe_db() Field 'subject_list' (table 'list_table' ; database 'sympa') was NOT found. Attempting to add it... info Upgrade::probe_db() Field subject_list added to table list_table info Upgrade::probe_db() Field 'topics_list' (table 'list_table' ; database 'sympa') was NOT found. Attempting to add it... info Upgrade::probe_db() Field topics_list added to table list_table info Upgrade::probe_db() Field 'web_archive_list' (table 'list_table' ; database 'sympa') was NOT found. Attempting to add it... info Upgrade::probe_db() Field web_archive_list added to table list_table info Upgrade::probe_db() Missing expected primary key : name_list info Upgrade::probe_db() Missing expected primary key :
Bug#717436: pu: shutdown-at-night - avoid daily email from cron when enabled
Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: unblock User: debian-...@lists.debian.org Usertags: debian-edu Here is a request to approve an upload of shutdown-at-night to wheezy, to fix a bug Debian Edu would like to have fixed in our Debian Edu Wheezy release. The same fix was uploaded as version 0.11 to unstable with this changelog entry: * Quiet down cron job to wake up client to not complain when fping notice they are unavailable. We want to make sure schools using Debian Edu and enabling the power saving feature provided by shutdown-at-night do not end up filling /var/ with emails from cron. Without this fix, a message like this is printed from the wakeupclient script for every client it try to wake up: ICMP Host Unreachable from 10.0.2.2 for ICMP Echo sent to dell.intern (10.0.16.20) ICMP Host Unreachable from 10.0.2.2 for ICMP Echo sent to dell.intern (10.0.16.20) ICMP Host Unreachable from 10.0.2.2 for ICMP Echo sent to dell.intern (10.0.16.20) This is the change I want to include: Index: wakeupclients === --- wakeupclients (revision 76266) +++ wakeupclients (working copy) @@ -63,7 +63,7 @@ sub get_alive_list { my @addresses = @_; -return split(/\s+/, `fping -a @addresses`); +return split(/\s+/, `fping -a @addresses 2/dev/null`); } sub logmsg { Please let us know if this is OK before we upload, and tell us which version number to use for this upload. -- 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#717437: libdbi1: Memory leak due to incorrect test in _is_row_fetched()
Package: libdbi1 Version: 0.8.4-6 Severity: normal Tags: patch Dear Maintainer, While debugging a memory leak using libdbi when querying the same row multiple times (due to result caching), I found that it had already been fixed in the Redhat RHEL6 package libdbi-0.8.3-4.el6.src.rpm in Sep 2012. Please integrate the following patch into the Debian package, and perhaps pass on to the upstream maintainers, it does not seem to be fixed there yet. --- a/src/dbi_result.c +++ b/src/dbi_result.c @@ -1533,7 +1533,7 @@ static unsigned int _find_field(dbi_resu } static int _is_row_fetched(dbi_result_t *result, unsigned long long row) { - if (!result-rows || (row = result-numrows_matched)) return -1; + if (!result-rows || (row result-numrows_matched)) return -1; return !(result-rows[row] == NULL); } Note that in order to recompile the fixed libdbi package I also had to add openjade to the Build-Depends, as without it the build fails with a openjade: Command not found compile error, but then it works Greetings, Haegar -- System Information: Debian Release: jessie/sid APT prefers unstable APT policy: (500, 'unstable'), (500, 'oldstable'), (101, 'experimental') Architecture: i386 (x86_64) Foreign Architectures: amd64 Kernel: Linux 3.2.47-sdinet83-cut1 (SMP w/2 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash Versions of packages libdbi1 depends on: ii libc6 2.17-7 libdbi1 recommends no packages. libdbi1 suggests no packages. -- debconf-show failed -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#717383: CONFIG_INTEL_MEI and CONFIG_INTEL_MEI_ME should be modules, not built in
On Fri, 2013-07-19 at 22:31 -0700, Josh Triplett wrote: Package: src:linux Version: 3.10.1-1 Severity: normal On boot, before the prompt for my disk encryption passphrase, I get a hang for several seconds. dmesg says: [1.207889] mei_me :00:16.0: setting latency timer to 64 [1.207961] mei_me :00:16.0: irq 40 for MSI/MSI-X [1.232899] mei_me :00:16.0: wait hw ready failed. status = 0x0 [8.223861] mei_me :00:16.0: wating for mei start failed [8.223935] mei_me :00:16.0: HBM haven't started [8.224002] mei_me :00:16.0: link layer initialization failed. [8.224072] mei_me :00:16.0: init hw failure. [8.224391] mei_me :00:16.0: initialization failed. CONFIG_INTEL_MEI and CONFIG_INTEL_MEI_ME are both tristate, so why not build them as a module? These enabled a single module before 3.10 (with INTEL_MEI_ME being a bool), and no-one noticed the change. It's also a bug that the mei-me module delays boot for several seconds on hardware without an ME, but that seems like a separate bug. There seem to be several different possible failure modes; here it fails rather faster: [0.484475] mei_me :00:16.0: setting latency timer to 64 [0.484508] mei_me :00:16.0: irq 42 for MSI/MSI-X [0.509073] mei_me :00:16.0: wait hw ready failed. status = 0x0 [0.509133] mei_me :00:16.0: version message writet failed [0.509184] mei_me :00:16.0: unexpected reset: dev_state = RESETTING [0.537061] mei_me :00:16.0: wait hw ready failed. status = 0x0 [0.537115] mei_me :00:16.0: version message writet failed [0.537165] mei_me :00:16.0: unexpected reset: dev_state = RESETTING Changing it back to a module will still result in it being auto-loaded, though you can at least blacklist it as a workaround. Ben. -- Ben Hutchings Humans are not rational beings; they are rationalising beings. signature.asc Description: This is a digitally signed message part
Bug#699761: Please complete the conversion to multiarch
Hi Aurelien! 2013/7/2, Aurelien Jarno aurel...@aurel32.net: On Tue, Jul 02, 2013 at 10:59:48AM +0200, Andrey Gursky wrote: Hi Aurelien, On Mon, Feb 04, 2013 at 08:08:08PM +0100, Andrey Gursky wrote: Package: libusb-dev Version: 2:0.1.12-20+nmu1 Severity: normal It is over a year ago since libusb has been converted to multiarch (http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=528205). But the -dev package has been overseen. For that the multiarch specification should tell what to do with config scripts in /usr/bin like /usr/bin/libusb-config, which are architecture specific. Until then such a conversion is simply not possible. Hmm, somehow I'm missing your answer in my mail-box. A nice suggestion to solve similar problem came from Jay Berkenbilt (maintainer of icu) No it can't be used. The problem is that if you put libusb-config in a different package, 'libusb-config --libs' built on amd64 will still output '-L/usr/lib/x86_64-linux-gnu -lusb' when run on i386. This would be wrong. I've noticed libusb-config is just a tiny shell script. So what would speak against something like such patch: if test $echo_libs = yes; then -echo -L@libdir@ -lusb @OSLIBS@ +echo -L@prefix@/lib/`dpkg-architecture -qDEB_HOST_GNU_TYPE` -lusb @OSLIBS@ fi or even: if test $echo_libs = yes; then -echo -L@libdir@ -lusb @OSLIBS@ +echo -lusb fi just as the output of pkg-config libusb --libs Would it be enough to make the -dev package Multi-Arch: same? [1]. Could that apply in case of libusb (also libusbx 1.0.x)? This is the way to go, libusb 0.1 is deprecated and programs should start libusb 1.0 instead. libusb 1.0.x is using pkg-config, and thus can be converted easily to multiarch. In fact I have already done it for the next version, I am just waiting for it to be released (currently at rc2). Thanks for the recent update! Regarding the status of libusb-0.1. There are still 87 packages depending on libusb-0.1, compared to 81 for libusb-1.0 (in Debian testing). Despite libusb-0.1 is considered deprecated, it is still used. That's why I hope we could discuss some really cosmetic, not time consuming updates to the package. By the way, in patches there is an autoreconf one. Was it not possible to patch only .in files and then add to rules something like: configure: ... configure.in autoreconf -vfi in order to not include this huge patch? Regards, Andrey -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#717438: pdnsd RUINED
Package: pdnsd Severity: grave X-Debbugs-Cc: resolvc...@packages.debian.org Version: 1.2.9a-par-1 Pdnsd is now ignored by anything on the system trying to get an IP address. downgrading pdnsd from 1.2.9a-par-1 to 1.2.8-par-3 fixes it. (What supported package should one now instead consider migrating to?) Versions of packages pdnsd depends on: ii adduser3.113+nmu3 ii debconf [debconf-2.0] 1.5.50 ii libc6 2.17-90 Versions of packages pdnsd recommends: ii resolvconf 1.73 -- debconf information: * pdnsd/conf: Use resolvconf -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#564874: manpages: Please ship ld.so manpage
On 07/18/13 22:13, Simon Paillard wrote: Hi Michael, On Mon, Jul 15, 2013 at 01:52:56PM +0200, Michael Kerrisk (man-pages) wrote: On Sun, Apr 29, 2012 at 7:42 PM, Simon Paillard spaill...@debian.org wrote: (but no more LD_ASSUME_KERNEL). I just drafted the following for ld.so.8 in man-pages: LD_ASSUME_KERNEL (glibc since 2.2.3) Each shared library can inform the dynamic linker of the minimum kernel ABI version that it requires. (This requirement is encoded in an ELF note section that is typically named .note.ABI-tag.) At run time, the dynamic linker determines the ABI version of the running kernel and will reject loading shared libraries that specify minimum ABI versions that exceed that ABI version. LD_ASSUME_KERNEL can be used to cause the dynamic linker to assume that it is running on a system with a differ‐ ent kernel ABI version. For example, the following com‐ mand line causes the dynamic linker to assume it is run‐ ning on Linux 2.2.5 when loading the shared libraries required by myprog: $ LD_ASSUME_KERNEL=2.2.5 ./myprog On systems that provide multiple versions of a shared library (in different directories in the search path) that have different minimum kernel ABI version require‐ ments, LD_ASSUME_KERNEL can be used to select the ver‐ sion of the library that is used (dependent on the directory search order). Historically, the most common use of the LD_ASSUME_KERNEL feature was to manually select the older LinuxThreads POSIX threads implementa‐ tion on systems that provided both LinuxThreads and NPTL (which latter was typically the default on such sys‐ tems). Look okay? Looks ok, interesting information mentioned by http://people.redhat.com/alikins/troubleshooting/ are actual values to be used when switching to NPTL or olf LinuxThreads. Yes. I've never been quite sure though whether the particular kernel versions to specify for LD_ASSUME_KERNEL when selecting the threading implementation are distro-specific, so I'm reluctant to go into the detail in the page. As you note, I do hint at the 2.2.5 version in the pthreads(7): LD_ASSUME_KERNEL happens to be documented a bit in pthreads(7) too. Yes, good to remind about that. I've added a cross reference from ld.so(8) to pthreads(7). Cheers, Michael -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#717439: emacs-goodies-el: slang-mode.el slang-indent-level safe-local-variable
Package: emacs-goodies-el Version: 35.4 Severity: wishlist File: /usr/share/emacs/site-lisp/emacs-goodies-el/slang-mode.el It'd be good if slang-mode.el had (put 'slang-indent-level 'safe-local-variable 'integerp) so a per-file slang-indent-level like foo.sl below doesn't prompt The local variables list in foo.sl contains values that may not be safe (*). #!/usr/bin/slsh _for (1,3,1) { message(Hello); } % Local variables: % slang-indent-level: 5 % End: -- System Information: Debian Release: 7.0 APT prefers unstable APT policy: (990, 'unstable') Architecture: i386 (i686) Kernel: Linux 2.6.32-5-486 Locale: LANG=en_AU, LC_CTYPE=en_AU (charmap=ISO-8859-1) Shell: /bin/sh linked to /bin/dash Versions of packages emacs-goodies-el depends on: ii bash 4.2+dfsg-1 ii dpkg 1.16.10 ii emacs21 [emacsen]21.4a+1-5.7 ii emacs22-gtk [emacsen]22.3+1-1.2 ii emacs23-lucid [emacsen] 23.4+1-4 ic emacs24 [emacsen]24.3+1-1 ii emacs24-lucid [emacsen] 24.3+1-1 ii install-info 5.1.dfsg.1-3 ii xemacs21-mule [emacsen] 21.4.22-4 Versions of packages emacs-goodies-el recommends: ii dict 1.12.1+dfsg-2 ii perl-doc 5.14.2-21 ii wget 1.14-2 emacs-goodies-el suggests no packages. -- no debconf information
Bug#714092: installation-reports: wheezy install on QNAP TS-212 fails to write to flash
On Thu, 2013-07-18 at 20:50 +0100, Martin Michlmayr wrote: * Mike Miller mtmil...@ieee.org [2013-06-27 09:15]: FWIW, I successfully installed on this QNAP using a daily installer [1] running 3.9-1-kirkwood. Here is the dmesg snippet probing the flash, looks exactly like what you describe: Ben, can you please add the git comments listed here: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=714092#12 Thanks! I've added the N25Q128 IDs but didn't bother with the 256 Mbit part (not needed for this system). So this should be fixed in Debian 7.2. Ben. -- Ben Hutchings Humans are not rational beings; they are rationalising beings. signature.asc Description: This is a digitally signed message part
Bug#717437: Acknowledgement (libdbi1: Memory leak due to incorrect test in _is_row_fetched())
On Sat, 20 Jul 2013, Debian Bug Tracking System wrote: Just a small correction to my bugreport, the problem is fixed in upstream CVS (and most likely in 0.9.0) c'ya sven-haegar -- Three may keep a secret, if two of them are dead. - Ben F. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#716789: Bug #716789: dash: sometimes misbehaves when backticks are included after an || operator
In Debian bug #716789, you wrote: [cat EOF | sh || echo `echo hi` die ... fails] The cause is likely that the command substitution incorrectly uses the outer here-document state. For example, dash treats these four lines cat EOF `true hi EOF ` as a complete command that prints hi. This is incorrect: a here-document shall only be recognized after the next NEWLINE token, and the command substitution is a WORD token. So the here-document should only be read after the fourth line, and hi and EOF should be executed as commands. This problem also occurs if new-style command substitution is used. In the example in the original bug report, the old-style command substitution not containing any newline generates an end-of-file condition on the inner string. Dash then assumes that the here-document is not coming, again corrupting the outer here-document state from the inner parse. This bug was fixed in FreeBSD sh in SVN r208655. I expect it will not be completely trivial to port it over, though. -- Jilles Tjoelker -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#717383: CONFIG_INTEL_MEI and CONFIG_INTEL_MEI_ME should be modules, not built in
On Sat, Jul 20, 2013 at 10:21:48PM +0100, Ben Hutchings wrote: On Fri, 2013-07-19 at 22:31 -0700, Josh Triplett wrote: Package: src:linux Version: 3.10.1-1 Severity: normal On boot, before the prompt for my disk encryption passphrase, I get a hang for several seconds. dmesg says: [1.207889] mei_me :00:16.0: setting latency timer to 64 [1.207961] mei_me :00:16.0: irq 40 for MSI/MSI-X [1.232899] mei_me :00:16.0: wait hw ready failed. status = 0x0 [8.223861] mei_me :00:16.0: wating for mei start failed [8.223935] mei_me :00:16.0: HBM haven't started [8.224002] mei_me :00:16.0: link layer initialization failed. [8.224072] mei_me :00:16.0: init hw failure. [8.224391] mei_me :00:16.0: initialization failed. CONFIG_INTEL_MEI and CONFIG_INTEL_MEI_ME are both tristate, so why not build them as a module? These enabled a single module before 3.10 (with INTEL_MEI_ME being a bool), and no-one noticed the change. Ah, makes sense. It's also a bug that the mei-me module delays boot for several seconds on hardware without an ME, but that seems like a separate bug. There seem to be several different possible failure modes; here it fails rather faster: [0.484475] mei_me :00:16.0: setting latency timer to 64 [0.484508] mei_me :00:16.0: irq 42 for MSI/MSI-X [0.509073] mei_me :00:16.0: wait hw ready failed. status = 0x0 [0.509133] mei_me :00:16.0: version message writet failed [0.509184] mei_me :00:16.0: unexpected reset: dev_state = RESETTING [0.537061] mei_me :00:16.0: wait hw ready failed. status = 0x0 [0.537115] mei_me :00:16.0: version message writet failed [0.537165] mei_me :00:16.0: unexpected reset: dev_state = RESETTING Changing it back to a module will still result in it being auto-loaded, though you can at least blacklist it as a workaround. I'd also hope that it doesn't get added to the initramfs, so the delay can occur in parallel with the rest of booting. - Josh Triplett -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#717441: shutdown-at-night: Add support for ACPI wakeup to turn a machine back on?
Package: shutdown-at-night Version: 0.10 The current wakeup methods supported are Wake-on-lan and nvram-wakeup. Modern hardware have another method, ACPI wakeup, that could be utilized by shutdown-at-night. The details of this method is described in URL: http://www.mythtv.org/wiki/ACPI_Wakeup . We could use something like this to set it: echo 0 /sys/class/rtc/rtc0/wakealarm date -u --date Jul 1, 2008 10:32:00 +%s /sys/class/rtc/rtc0/wakealarm But to get it working, we have to disable /etc/init.d/hwclock.sh during shutdown or make sure we set the alarm after hwclock.sh is executed during shutdown. -- 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#716801: udev: 70-persistent-net.rules isn't generated
On Jul 20, Simon Lodal sim...@parknet.dk wrote: No this is a bug. Why should interface renaming not work in virtual machines? Because their names are already stable. -- ciao, Marco signature.asc Description: Digital signature
Bug#717436: Stable updates are _not_ unblocks; that's why there's a pu tag...
user release.debian@packages.debian.org usertags 717436 = pu tags 717436 + wheezy retitle 717436 pu: shutdown-at-night/0.10+deb7u1 -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#717440: sml-mode: sml-indent-level safe-local-variable
Package: sml-mode Version: 4.1-2 Severity: wishlist File: /usr/share/emacs/site-lisp/sml-mode/sml-mode.el It'd be good if sml-mode.el had (put 'sml-indent-level 'safe-local-variable 'integerp) so a per-file sml-indent-level like foo.sml below doesn't prompt The local variables list in foo.sml contains values that may not be safe (*). if true then 2 else 3 ; (* Local variables: sml-indent-level: 20 End: *) -- System Information: Debian Release: 7.0 APT prefers unstable APT policy: (990, 'unstable') Architecture: i386 (i686) Kernel: Linux 2.6.32-5-486 Locale: LANG=en_AU, LC_CTYPE=en_AU (charmap=ISO-8859-1) Shell: /bin/sh linked to /bin/dash Versions of packages sml-mode depends on: ii dpkg1.16.10 ii emacsen-common 2.0.5 ii install-info5.1.dfsg.1-3 sml-mode recommends no packages. sml-mode suggests no packages. -- no debconf information
Bug#717269: Please set CONFIG_NET_CALXEDA_XGMAC in -armmp kernel flavor
On Thu, 2013-07-18 at 18:41 +0200, Raphael Hertzog wrote: Package: src:linux Version: 3.10.1-1 Severity: wishlist I have made some tests of the Calxeda Highbank with the -armmp kernel flavor, it seems to work except for the network because CONFIG_NET_CALXEDA_XGMAC is not set. Please enable that Kconfig setting. Done. Ben. -- Ben Hutchings Humans are not rational beings; they are rationalising beings. signature.asc Description: This is a digitally signed message part
Bug#717442: debian/rules binary fails to run build target
Package: haskell-devscripts Version: 0.8.17 Severity: serious This probably affects many haskell packages, but the one I encountered it with is haskell-hinotify. Running debian/rules binary fails: debian/hlibrary.setup copy --builddir=dist-ghc --destdir=debian/tmp-inst-ghc Installing library in debian/tmp-inst-ghc/usr/lib/haskell-packages/ghc/lib/hinotify-0.3.2/ghc-7.4.1 hlibrary.setup: Error: Could not find module: System.INotify with any suffix: [hi] in the search path: [dist-ghc/build] This turns out to be because the binary target is not running the build target. Which is policy violation: Both `binary-*' targets should depend on the `build' target, or on the appropriate `build-arch' or `build-indep' target, if provided, so that the package is built if it has not been already. cdbs may be at the root of this bug -- System Information: Debian Release: jessie/sid APT prefers unstable APT policy: (500, 'unstable'), (500, 'testing') Architecture: i386 (i686) Kernel: Linux 3.9-1-686-pae (SMP w/2 CPU cores) Locale: LANG=en_US.utf8, LC_CTYPE=en_US.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages haskell-devscripts depends on: ii cdbs0.4.122 ii dctrl-tools 2.23 ii debhelper 9.20130630 ii dh-buildinfo0.9+nmu1 ii ghc 7.6.3-3 ii ghc-haddock 7.6.3-3 ii hscolour1.20.3-2 ii html-xml-utils 6.4-1 haskell-devscripts recommends no packages. haskell-devscripts suggests no packages. -- no debconf information -- see shy jo signature.asc Description: Digital signature
Bug#714906: scan-build: does not respect the TMP/TMPDIR/TEMP/TEMPDIR evironment variables
Hello, Just happening to work on scan-build those days. The issue you're reporting is failing because of this very version of scan-build : the TMPDIR POSIX standard env variable is only taken into account if (`uname` =~ /Darwin/). In a newer version of llvm-toolchain (3.3 or snapshot), this condition has been removed, therefore using libpam-tmpdir with scan-build works without any problem. The code does not use File::Temp but create paths manually instead, checking for -o option or/and TMPDIR directory. I reckon that Sylvestre does not maintain the 3.2 branch anymore, but I can be wrong. A two line patch will solve this problem anyhow. Bonus : there is still mention of this Darwin thing in the scan-build manpage (HEAD version) quoteIf this option is not specified, a directory is created in /tmp (TMPDIR on Mac OS X) to store the reports./quote This could be the object of a fixme upstream. Thanks for the report, Cheers -- Léo -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#708288: apache2: htpasswd uses crypt and not md5 as default enc
I re-tested a few versions: Found in 2.2.16-6 Fixed in 2.2.22-13 That bug was very probably repported on a different system from the one it was found. First Debian version it was fixed was 2.2.19-1 : http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=539246#30 If nobody objects, I'll merge with previous reports #539246 and #606958. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#595817: Bug#716852: RFS: libpam-ssh-agent-auth/0.9.5-2.2 [ITP]
Dear mentors, I am looking for a sponsor for my package libpam-ssh-agent-auth. I'v already sent the sponsor request previously, ref, http://lists.debian.org/package-sponsorship-requests/2013/package-sponsorship-requests-201307/msg00087.html This is a new upload. * Package name: libpam-ssh-agent-auth Version : 0.9.5-2.2 Upstream Author : Jamie Beverly soup...@sourceforge.net * URL : http://sourceforge.net/projects/pamsshagentauth/ * License : BSD License Section : libs It builds those binary packages: libpam-ssh-agent-auth - PAM Authentication via forwarded ssh-agent To access further information about this package, please visit the following URL: http://mentors.debian.net/package/libpam-ssh-agent-auth Alternatively, one can download the package with dget using this command: dget -x http://mentors.debian.net/debian/pool/main/libp/libpam-ssh-agent-auth/libpam-ssh-agent-auth_0.9.5-2.2.dsc More information about libpam-ssh-agent-auth can be obtained from http://sfxpt.wordpress.com/libpam-ssh-agent-auth/. Changes since the last upload: libpam-ssh-agent-auth (0.9.5-2.2) unstable; urgency=low * Fixes so as to build the binary package properly Regards, Tong Sun PS. Please CC me when replying. Thanks -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#716852: Fwd: Bug#716852: RFS: libpam-ssh-agent-auth/0.9.5-2.2 [ITP]
Dear mentors, I am looking for a sponsor for my package libpam-ssh-agent-auth. I'v already sent the sponsor request previously, ref, http://lists.debian.org/package-sponsorship-requests/2013/package-sponsorship-requests-201307/msg00087.html This is a new upload. * Package name: libpam-ssh-agent-auth Version : 0.9.5-2.2 Upstream Author : Jamie Beverly soup...@sourceforge.net * URL : http://sourceforge.net/projects/pamsshagentauth/ * License : BSD License Section : libs It builds those binary packages: libpam-ssh-agent-auth - PAM Authentication via forwarded ssh-agent To access further information about this package, please visit the following URL: http://mentors.debian.net/package/libpam-ssh-agent-auth Alternatively, one can download the package with dget using this command: dget -x http://mentors.debian.net/debian/pool/main/libp/libpam-ssh-agent-auth/libpam-ssh-agent-auth_0.9.5-2.2.dsc More information about libpam-ssh-agent-auth can be obtained from http://sfxpt.wordpress.com/libpam-ssh-agent-auth/. Changes since the last upload: libpam-ssh-agent-auth (0.9.5-2.2) unstable; urgency=low * Fixes so as to build the binary package properly Regards, Tong Sun PS. Please CC me when replying. Thanks -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#717443: RFP: zbackup -- A versatile deduplicating backup tool
Package: wnpp Severity: wishlist * Package name: zbackup Version : 1.1 Upstream Author : Konstantin Isakov i...@zbackup.org * URL : http://zbackup.org/ * License : GPL Programming Lang: C++ Description : A versatile deduplicating backup tool Uses a 64-bit modified Rabin-Karp rolling hash for data deduplication, and SHA256 for backup integrity check. Also features LZMA compression AES encryption. Best wishes, Bob
Bug#705519: Used deprecated symbols from libudev
Hi, Thanks for the fix in experimental. I've just filed a transition bug for libudev1, so it would be great to have a fixed bluez also in unstable. I don't think we want to entangle the libudev1 with the bluez5 transition. Could you please backport the fix from 5.5-1~exp0 for the unstable version? I can offer to NMU in case you are busy. Cheers, Michael -- 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#717444: FTBFS on armel: #error You must enable NEON instructions to use arm_neon.h
Source: pulseaudio Version: 4.0-5 Severity: serious pulseaudio currently FTBFS on armel [1] with the following error message: In file included from pulsecore/sconv_neon.c:30:0: /usr/lib/gcc/arm-linux-gnueabi/4.8/include/arm_neon.h:32:2: error: #error You must enable NEON instructions (e.g. -mfloat-abi=softfp -mfpu=neon) to use arm_neon.h #error You must enable NEON instructions (e.g. -mfloat-abi=softfp -mfpu=neon) to use arm_neon.h ^ make[4]: *** [libpulsecore_sconv_neon_la-sconv_neon.lo] Error 1 make[3]: *** [all] Error 2 make[4]: Leaving directory `/«PKGBUILDDIR»/src' make[3]: Leaving directory `/«PKGBUILDDIR»/src' make[2]: *** [all-recursive] Error 1 make[1]: *** [all] Error 2 make: *** [debian/stamp-makefile-build] Error 2 dpkg-buildpackage: error: debian/rules build-arch gave error exit status 2 Since I'd like to start the libudev1 transition whenever we get the go from the release team, it would be great to have a fixed PA package ready. Michael [1] https://buildd.debian.org/status/fetch.php?pkg=pulseaudioarch=armelver=4.0-5stamp=1374273804 -- System Information: Debian Release: jessie/sid APT prefers unstable APT policy: (500, 'unstable'), (200, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.10-1-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 -- 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#688441: 3.2.0 ext3 and ext4 failing in Xen VM domU
Hi, I’d like to confirm this bug; using linux-image-3.2.0-4-amd64 on wheezy in the domU; dom0 is 2.6.32-5-xen-amd64 on squeeze. Setting barrier=0 does not seem to help. Is there any option besides continuing to use the squeeze kernel package that is still installed from before the upgrade? Greetings, Joachim -- Joachim nomeata Breitner Debian Developer nome...@debian.org | ICQ# 74513189 | GPG-Keyid: 4743206C JID: nome...@joachim-breitner.de | http://people.debian.org/~nomeata signature.asc Description: This is a digitally signed message part
Bug#717445: pu: package ndiswrapper/1.57-1+deb7u1
Package: release.debian.org Severity: normal Tags: wheezy User: release.debian@packages.debian.org Usertags: pu Hi, there are two bugs affecting ndiswrapper-dkms that should be fixed in wheezy: * the module fails to build for a kernel that is not running (#693638) * dkms throws up during kernel upgrades (#690747) The changes are cherry-picked from 1.58-1 and adjusted for 1.57. I can do a NMU, but I'd prefer a maintainer upload fixing this. @jak (Cc:ed): Shall I push my wheezy branch to the git repo? Andreas diff -Nru ndiswrapper-1.57/debian/changelog ndiswrapper-1.57/debian/changelog --- ndiswrapper-1.57/debian/changelog 2012-03-05 16:49:17.0 +0100 +++ ndiswrapper-1.57/debian/changelog 2013-07-21 00:07:16.0 +0200 @@ -1,3 +1,13 @@ +ndiswrapper (1.57-1+deb7u1) wheezy; urgency=low + + * Non-maintainer upload. + * Cherry-pick from 1.58-1: +- Use $KERNELRELEASE as target kernel version (Closes: #693638) +- Add BUILT_MODULE_NAME to dkms config file (Workaround for: #690747) + * ndiswrapper-use-KERNELRELEASE.patch: Adjust for 1.57. + + -- Andreas Beckmann a...@debian.org Sun, 21 Jul 2013 00:06:37 +0200 + ndiswrapper (1.57-1) unstable; urgency=low * Imported Upstream version 1.57 diff -Nru ndiswrapper-1.57/debian/ndiswrapper-dkms.dkms.in ndiswrapper-1.57/debian/ndiswrapper-dkms.dkms.in --- ndiswrapper-1.57/debian/ndiswrapper-dkms.dkms.in 2012-03-05 16:49:17.0 +0100 +++ ndiswrapper-1.57/debian/ndiswrapper-dkms.dkms.in 2013-07-20 23:55:18.0 +0200 @@ -1,4 +1,5 @@ PACKAGE_NAME=ndiswrapper PACKAGE_VERSION=@VERSION@ DEST_MODULE_LOCATION[0]=/updates +BUILT_MODULE_NAME[0]=ndiswrapper AUTOINSTALL=yes diff -Nru ndiswrapper-1.57/debian/patches/ndiswrapper-use-KERNELRELEASE.patch ndiswrapper-1.57/debian/patches/ndiswrapper-use-KERNELRELEASE.patch --- ndiswrapper-1.57/debian/patches/ndiswrapper-use-KERNELRELEASE.patch 1970-01-01 01:00:00.0 +0100 +++ ndiswrapper-1.57/debian/patches/ndiswrapper-use-KERNELRELEASE.patch 2013-07-21 00:05:26.0 +0200 @@ -0,0 +1,22 @@ +From: Ben Hutchings b...@decadent.org.uk +Subject: Use $KERNELRELEASE as target kernel version +Bug-Debian: http://bugs.debian.org/693638 + +We must not assume that the running kernel version is the target +version! DKMS and later Kbuild set $KERNELRELEASE to be the target +kernel version. + +--- a/driver/Makefile b/driver/Makefile +@@ -12,7 +12,11 @@ + # By default, we try to compile the modules for the currently running + # kernel. But it's the first approximation, as we will re-read the + # version from the kernel sources. ++ifeq (,$(KERNELRELEASE)) + KVERS ?= $(shell uname -r) ++else ++KVERS ?= $(KERNELRELEASE) ++endif + + # KBUILD is the path to the Linux kernel build tree. It is usually the + # same as the kernel source tree, except when the kernel was compiled in diff -Nru ndiswrapper-1.57/debian/patches/series ndiswrapper-1.57/debian/patches/series --- ndiswrapper-1.57/debian/patches/series 2012-03-05 16:49:17.0 +0100 +++ ndiswrapper-1.57/debian/patches/series 2013-07-20 23:55:18.0 +0200 @@ -1 +1,2 @@ ndiswrapper-harden.patch +ndiswrapper-use-KERNELRELEASE.patch
Bug#688441: 3.2.0 ext3 and ext4 failing in Xen VM domU
Hi, searched some more, and it seems that the cause of the problem is a bug in the squeeze Dom0 kernel, fixed in wheezy. In case others find also this bug first: Have a look at: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=688441 Greetings, Joachim -- Joachim nomeata Breitner Debian Developer nome...@debian.org | ICQ# 74513189 | GPG-Keyid: 4743206C JID: nome...@joachim-breitner.de | http://people.debian.org/~nomeata signature.asc Description: This is a digitally signed message part
Bug#717446: icicles: autoloads for vline.el etc
Package: icicles Version: 23.0+20110910-2 Severity: wishlist File: /etc/emacs/site-start.d/50icicles.el It'd be good if 50icicles.el had autoloads for the user entrypoint commands in crosshairs.el, col-highlight and vline.el. I believe they can be used independently of the rest of icicles. In particular an autoload for vline-mode allows that mode to be restored by desktop.el. (autoload 'crosshairs crosshairs Highlight current position with crosshairs. t) (autoload 'crosshairs-mode crosshairs Toggle highlighting the current line and column. t) (autoload 'crosshairs-toggle-when-idle crosshairs Toggle highlighting the current line and column when Emacs is idle. t) (autoload 'crosshairs-flash crosshairs Highlight the current line and column temporarily. t) (autoload 'crosshairs-highlight crosshairs Echo current position and highlight it with crosshairs. t) (autoload 'column-highlight-mode col-highlight Toggle highlighting the current column. t) (autoload 'col-highlight-toggle-when-idle col-highlight Turn on or off highlighting the current column when Emacs is idle. t) (autoload 'col-highlight-set-interval col-highlight Set wait until highlight current column when Emacs is idle. t) (autoload 'col-highlight-flash col-highlight Highlight the current column for `col-highlight-period' seconds. t) (autoload 'vline-mode vline Display vertical line mode. t) (autoload 'vline-global-mode vline Toggle Vline mode in all buffers. t) -- System Information: Debian Release: 7.0 APT prefers unstable APT policy: (990, 'unstable') Architecture: i386 (i686) Kernel: Linux 2.6.32-5-486 Locale: LANG=en_AU, LC_CTYPE=en_AU (charmap=ISO-8859-1) Shell: /bin/sh linked to /bin/dash Versions of packages icicles depends on: ii emacs22-gtk [emacs22]22.3+1-1.2 ii emacs23-lucid [emacs23] 23.4+1-4 icicles recommends no packages. icicles 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#711585: [linux-image-3.9-1-loongson-2f] linux 3.9.4-1 for loongson-2f doesn't halt/reboot/suspend-disk.
Still failing with latest 3.10-1 linux image... -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#717448: apache2: Invalid command 'AuthType'
Package: apache2 Version: 2.4.4-6 Severity: important Dear Maintainer, The AuthType command seems to have been removed or is broken. This breaks package phpmyadmin and many other simple user written websites that require simple security. I found this error by simply installing apache2, php5 and phpmyadmin. root@Anum:~# service apache2 start [FAIL] Starting web server: apache2 failed! The apache2 configtest failed. Please run 'env -i LANG=C PATH=/usr/local/bin:/usr/bin:/bin /usr/sbin/apache2ctl configtest' manually and read the log file to discover problems failed! root@Anum:~# env -i LANG=C PATH=/usr/local/bin:/usr/bin:/bin /usr/sbin/apache2ctl configtest AH00526: Syntax error on line 26 of /etc/apache2/conf-enabled/phpmyadmin.conf: Invalid command 'AuthType', perhaps misspelled or defined by a module not included in the server configuration Action 'configtest' failed. The Apache error log may have more information. apachectl -t -D DUMP_MODULES AH00526: Syntax error on line 26 of /etc/apache2/conf-enabled/phpmyadmin.conf: Invalid command 'AuthType', perhaps misspelled or defined by a module not included in the server configuration Action '-t -D DUMP_MODULES' failed. The Apache error log may have more information. root@Anum:~# a2disconf phpmyadmin Conf phpmyadmin disabled. To activate the new configuration, you need to run: service apache2 reload root@Anum:~# apachectl -t -D DUMP_MODULES AH00558: apache2: Could not reliably determine the server's fully qualified domain name, using ::1. Set the 'ServerName' directive globally to suppress this message Loaded Modules: core_module (static) so_module (static) watchdog_module (static) http_module (static) log_config_module (static) logio_module (static) version_module (static) unixd_module (static) access_compat_module (shared) alias_module (shared) auth_basic_module (shared) authn_file_module (shared) authz_core_module (shared) authz_host_module (shared) authz_user_module (shared) autoindex_module (shared) deflate_module (shared) dir_module (shared) env_module (shared) filter_module (shared) mime_module (shared) mpm_prefork_module (shared) negotiation_module (shared) php5_module (shared) setenvif_module (shared) status_module (shared) As you can see it looks like I have the right modules loaded. Any ideas maybe something I'm doing wrong? or should I report it as a phpmyadmin bug? -- Package-specific info: -- System Information: Debian Release: jessie/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: amd64 (x86_64) Kernel: Linux 3.10.1 (SMP w/4 CPU cores) Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968) Shell: /bin/sh linked to /bin/dash Versions of packages apache2 depends on: ii apache2-bin 2.4.4-6 ii apache2-data 2.4.4-6 ii lsb-base 4.1+Debian12 ii mime-support 3.54 ii perl 5.14.2-21 ii procps1:3.3.8-2 Versions of packages apache2 recommends: ii ssl-cert 1.0.32 Versions of packages apache2 suggests: pn apache2-doc none pn apache2-suexec-pristine | apache2-suexec-custom none ii apache2-utils2.4.4-6 pn www-browser none Versions of packages apache2-bin depends on: ii libapr1 1.4.8-1 ii libaprutil1 1.5.2-1 ii libaprutil1-dbd-sqlite3 1.5.2-1 ii libaprutil1-ldap 1.5.2-1 ii libc62.17-7 ii libcap2 1:2.22-1.2 ii libldap-2.4-22.4.31-1+nmu2 ii liblua5.1-0 5.1.5-4 ii libpcre3 1:8.31-2 ii libssl1.0.0 1.0.1e-3 ii libxml2 2.9.1+dfsg1-2 ii perl 5.14.2-21 ii zlib1g 1:1.2.8.dfsg-1 Versions of packages apache2-bin suggests: pn apache2-doc none pn apache2-doc none pn apache2-suexec-pristine | apache2-suexec-custom none pn www-browser none Versions of packages apache2 is related to: ii apache2 2.4.4-6 ii apache2-bin 2.4.4-6 -- 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#564874: manpages: Please ship ld.so manpage
Things from my past coming back to haunt me, but if people want to keep ccing me... On Sat, Jul 20, 2013 at 10:15:25PM +0200, Michael Kerrisk wrote: Yes. I've never been quite sure though whether the particular kernel versions to specify for LD_ASSUME_KERNEL when selecting the threading implementation are distro-specific, so I'm reluctant to go into the detail in the page. As you note, I do hint at the 2.2.5 version in the pthreads(7): asuffield@cyclone:~$ readelf -n /lib/x86_64-linux-gnu/libc.so.6 Notes at offset 0x0270 with length 0x0024: Owner Data size Description GNU 0x0014 NT_GNU_BUILD_ID (unique build ID bitstring) Build ID: cddff8f45f5aa7b5ce64717e9e6ae3899f27972c Notes at offset 0x0294 with length 0x0020: Owner Data size Description GNU 0x0010 NT_GNU_ABI_TAG (ABI version tag) OS: Linux, ABI: 2.6.26 asuffield@cyclone:~$ LD_ASSUME_KERNEL=2.6.25 /bin/true /bin/true: error while loading shared libraries: libc.so.6: cannot open shared object file: No such file or directory asuffield@cyclone:~$ LD_ASSUME_KERNEL=2.6.26 /bin/true asuffield@cyclone:~$ Apparently glibc has moved on and there's nothing in wheezy that can use the old numbers. I expect other distros are similar. This information is probably only of historical interest now. The number 2.2.5 used to be special because it was the *minimum* version supported by the non-TLS libc that was shipped at the time. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#717334: network-manager-applet: provide a simple network-manager-gtk package for non-GNOME GTK-based desktops
Michael Biebl: What specifically do you mean by GNOME stuff? gnome-bluetooth, gnome-keyring, gconf... Seems to be more like an upstream feature request for a simpler NetworkManager GTK frontend / applet. For Debian, it looks like a good wontfix candidate now :) Samuel Sanchez: the current situation of network-manager-gnome is, that it depends on so many different gnome packages, that it basicly pulls all of gnome Welcome to the bug#714803 discussion: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=714803 Best wishes, Bob
Bug#717449: Generates /etc/network/interfaces config for eth0 although network-manager is installed (desktop task)
Package: netcfg Version: 1.110 Severity: important Hi, I just did a installation of 7.1 inside a VM using the desktop task, which means network-manager was installed along with it. I was surprised to find the following in /e/n/i: # The primary network interface allow-hotplug eth0 iface eth0 inet dhcp This causes the well known problem, that the interface won't be managed by network-manager. I'm remember that we had fixed that while working towards the wheezy release, so I'm surprised to find that issue in 7.1 Marking as important. I think we should address this for 7.2. Cheers, Michael -- System Information: Debian Release: jessie/sid APT prefers unstable APT policy: (500, 'unstable'), (200, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.10-1-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 -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#687086: oss4-dkms: missing dependency on dpkg-dev
Version: 4.2-build2006-2+deb7u1 Followup-For: Bug #687086 Control: severity -1 serious Build log from minimal wheezy install: DKMS make.log for oss4-4.2-build2006 for kernel 3.2.0-4-amd64 (x86_64) Sat Jul 20 22:40:02 UTC 2013 make: Entering directory `/usr/src/linux-headers-3.2.0-4-amd64' make[3]: dpkg-architecture: Command not found CC [M] /var/lib/dkms/oss4/4.2-build2006/build/core/oss_core.o In file included from /var/lib/dkms/oss4/4.2-build2006/build/core/oss_core.c:42:0: /var/lib/dkms/oss4/4.2-build2006/build/core/audio_core.h:3:20: fatal error: endian.h: No such file or directory compilation terminated. make[3]: *** [/var/lib/dkms/oss4/4.2-build2006/build/core/oss_core.o] Error 1 make[2]: *** [_module_/var/lib/dkms/oss4/4.2-build2006/build/core] Error 2 make[1]: *** [sub-make] Error 2 make: *** [all] Error 2 make: Leaving directory `/usr/src/linux-headers-3.2.0-4-amd64' Build log after adding dpkg-dev: DKMS make.log for oss4-4.2-build2006 for kernel 3.2.0-4-amd64 (x86_64) Sat Jul 20 22:48:08 UTC 2013 make: Entering directory `/usr/src/linux-headers-3.2.0-4-amd64' CC [M] /var/lib/dkms/oss4/4.2-build2006/build/core/oss_core.o In file included from /var/lib/dkms/oss4/4.2-build2006/build/core/oss_core.c:42:0: /var/lib/dkms/oss4/4.2-build2006/build/core/audio_core.h:3:20: fatal error: endian.h: No such file or directory compilation terminated. make[3]: *** [/var/lib/dkms/oss4/4.2-build2006/build/core/oss_core.o] Error 1 make[2]: *** [_module_/var/lib/dkms/oss4/4.2-build2006/build/core] Error 2 make[1]: *** [sub-make] Error 2 make: *** [all] Error 2 make: Leaving directory `/usr/src/linux-headers-3.2.0-4-amd64' So libc-dev was missing as well ... installed ... now building succeeds. Andreas -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#717334: network-manager-applet: provide a simple network-manager-gtk package for non-GNOME GTK-based desktops
Am 21.07.2013 01:03, schrieb Bob Bib: Michael Biebl: What specifically do you mean by GNOME stuff? gnome-bluetooth, gnome-keyring, gconf... I already outlined what gnome-keyring and gnome-bluetooth are required for. gconf is simply needed because nm-applet uses that as configuration systemd. And no, I won't be re-implementing that with a homegrown config file solution, because that would be stupid. So, all in all, I don't really see a point for a -gtk package, and indeed so far this is a clear wont-fix bug. I'm even tempted to just close it. Michael -- 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#717449: Acknowledgement (Generates /etc/network/interfaces config for eth0 although network-manager is installed (desktop task))
fwiw, I tested both the 7.0.0 and 7.1.0 install images, with the same result -- 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#707743: (no subject)
Any news here? Do you need help? -- Jascha Geerds j...@ekby.de -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#717450: listarchives: Please consider adding avatar support
Package: lists.debian.org Severity: wishlist Tags: patch Hi folks, having just read a thread with a bunch of replies ( 20), it occurred to me that an avatar on each page would have helped. I'm attaching a patch against an html page to show what you could use (shamelessly stolen from the BTS). Besides the float: right bit, let's see what that does: http://cdn.libravatar.org/avatar/4c078242b0a02b3f681bcc61f8a42fe0?d=http://bugs.debian.org/css/1x1.png cdn.libravatar.org is just what the BTS uses, I have no specific insight about it (besides what https://www.libravatar.org/ says…). The ID can be computed using the Gravatar::URL perl module, example: | $ perl -MGravatar::URL -e 'print gravatar_id(kibi\@debian.org), \n;' | 4c078242b0a02b3f681bcc61f8a42fe0 The 'd=' parameter is the default image to be used when there's no avatar available. Probably just a tiny empty file to drop onto lists.d.o as that was done on bugs.d.o. Thanks for considering. Mraw, KiBi. --- a/sample.html +++ b/sample.html @@ -43,6 +42,7 @@ !--X-Subject-Header-Begin-- h1Re: freemedforms amp; rpath/h1 hr +img src=http://cdn.libravatar.org/avatar/4c078242b0a02b3f681bcc61f8a42fe0?d=http://bugs.debian.org/css/1x1.png; style=float: right !--X-Subject-Header-End-- !--X-Head-of-Message-- ul
Bug#717451: Backups broken when ssh_args are set
Package:rsnapshot Version:1.3.1-4 Hi! (NB: Please keep me Cc'ed. Thanks.) I just updated my backup box and basically all of my rsnapshot jobs are failing. As it seems, a revert for a bad fix was pulled into the debian package. While the revertion of the fix will probably fix quite a few problems, it also introduces a new problem when ssh_args are set. I'm usually setting ssh_args to something like: ssh_args-p 2345 -i identify file -oBatchMode=yes The non-standard SSH port is to access a number of hosts behind a NATing router, the identity file and BatchMode should be self-explanatory. The former behavior (with the bad fix still applied results in a long command line containing rsync ... --rsh=/usr/bin/ssh my args here ... which is parsed by a shell, thus the `' around the --rsh value are eaten away. In the new behavior, the command array is supplied, which in turn *preserves* the double-quotes for the exec call to rsync. Thus, later on, it's not /usr/bin/ssh with a number of argument what's being called, but something like /usr/bin/ssh -i , which of course doesn't exist. It is non-obvious how to get ssh_args right and I think you cannot use them at all right now due to wrong quoting while the --rsh=... argument is prepared. A workaround would be to prepare proper entries in user's ~/.ssh/config file, and removing the ssh_args option alltogether. However, I think that a correct fix to this problem is to simply remove the added `' while preparing the --rsh argument for rsync in case ssh_args is set. With the new way of doing the system() call, supplying an _array_ of single options (instead of a string that needs to be parsed), these quotes are actually the root cause of rsync's wrong parsing of the --rsh option: diff --git a/rsnapshot-program.pl b/rsnapshot-program.pl index dfd7ef6..9d98de5 100755 --- a/rsnapshot-program.pl +++ b/rsnapshot-program.pl @@ -3452,7 +3452,7 @@ sub rsync_backup_point { # if we have any args for SSH, add them if ( defined($ssh_args) ) { - push( @rsync_long_args_stack, --rsh=\$config_vars{'cmd_ssh'} $ssh_args\ ); + push( @rsync_long_args_stack, --rsh=$config_vars{'cmd_ssh'} $ssh_args ); # no arguments is the default } else { (This patch is on-top of git://anonscm.debian.org/collab-maint/rsnapshot.git and applies with -40 lines offset on-top of upstream rsnapshot, too.) Thanks, Jan-Benedict -- Jan-Benedict Glaw jbg...@lug-owl.de +49-172-7608481 Signature of: Alles wird gut! ...und heute wirds schon ein bißchen besser. the second : signature.asc Description: Digital signature
Bug#717452: dosfstools: use device topology information to set sector size
Package: dosfstools Version: 3.0.16-2 Severity: wishlist Tags: upstream Hi Daniel. I hope my understanding of FAT isn't all too wrong, but AFAIU, the logical sector size (i.e. -S switch) is analogous to the block size in e.g. ext*, right? If so,.. wouldn't it make sense (for performance reasons) to try to set these to the block size of the underlying device, which in case of upcoming HDDs would be 4 KiB... Ideally, of course, mkdosfs would use device topology information (well at least on modern Linux kerne), to determine both, the ideal sector size, as well as their alignment. That would expose the necessary information even as it's modified through the different block layers, e.g.: # lsblk -t NAME ALIGNMENT MIN-IO OPT-IO PHY-SEC LOG-SEC ROTA SCHED RQ-SIZE sda 0512 0 512 5120 cfq 128 └─sda10512 0 512 5120 cfq 128 ├─vg_system-root (dm-0) 0512 0 512 5120 128 │ └─root (dm-2) 0512 0 512 5120 128 └─vg_system-swap (dm-1) 0512 0 512 5120 128 sdb 0512 0 512 5121 cfq 128 └─sdb10512 0 512 5121 cfq 128 loop0 0512 0 512 5121 128 (which here uses filesystem on top of dmcrypt, on top of LVM on top of partitions. btw: I tried to manually set the sector size to 4096 but that seems to cause troubles: # mkfs.vfat -v -S 4096 -F 32 -n ESP /dev/loop0 mkfs.vfat 3.0.16 (01 Mar 2013) Loop device does not match a floppy size, using default hd params WARNING: Not enough clusters for a 32 bit FAT! /dev/loop0 has 64 heads and 32 sectors per track, logical sector size is 4096, using 0xf8 media descriptor, with 131072 sectors; file system has 2 32-bit FATs and 8 sectors per cluster. FAT size is 16 sectors, and provides 16376 clusters. There are 32 reserved sectors. Volume ID is abde448e, volume label ESP. What's the problem here? Cheers, Chris. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#714803: Bug#717334: network-manager-applet: provide a simple network-manager-gtk package for non-GNOME GTK-based desktops
gnome-bluetooth, gnome-keyring, gconf... The dependencies on gnome-keyring and gconf I can understand and I am fine with it. Would be just to much work and would not make sense. I totally agree with that. However gnome-bluetooth a is a different story. It do be a suggest would be just fine in my opinion. I really don't see, why it must be a dependency. The openvpn, openconnect, pptp and vpnc are also only suggest and bluetooth is imho the same level of feature: nice, that it is supported, but not necessary, and thus in my understanding not a dependency. nm-applet would also work just fine without bluetooth. Do you know, how many users are really using the bluetooth-capability in the first place? I don't think, they're many. Best, Sam signature.asc Description: OpenPGP digital signature
Bug#714803: network-manager-gnome: please move gnome-bluetooth from Recommends to Suggests
Fri, 19 July 2013, 16:17 +02:00 from Michael Biebl bi...@debian.org: severity 714803 wishlist thanks Am 19.07.2013 16:08, schrieb Bob Bib: control: severity -1 normal Thu, 18 Jul 2013 23:27:05 GMT from Michael Biebl: severity 714803 wishlist thanks wishlist is a too low priority for this bug: Please respect the decision of the maintainer and stop changing it. Hi Michael, 1) you've changed this bug's severity from important to wishlist without any comment, so it looked more like an unintentional typo somewhere. 2) just to remember, here is the current problem: network-manager-gnome recommends gnome-bluetooth, gnome-bluetooth recommends gnome-control-center // which is unusable in non-GNOME3 DE's (LXDE at least), see bug#695817 gnome-control-center recommends gnome-session // which finally recommends gnome-shell AFAIK, network-manager-applet / network-manager-gnome is the only GTK frontend / applet for NetworkManager packaged in Debian, so more lightweight GTK DE's like Xfce LXDE make use of it (lxde task-xfce-desktop packages recommend it). And pulling the core of GNOME3 to make a network manager work is a nonsense. // Well, it still can be avoided on upgrade by supplying a --no-install-recommends option to APT: // # apt-get --no-install-recommends dist-upgrade Thus, I strongly suggest to move gnome-bluetooth to Suggests for network-manager-gnome package. We shouldn't fear about GNOME3 users losing Bluetooth functionality, since gnome-core, gnome-shell gnome-user-share packages currently have gnome-bluetooth in Depends! Best wishes, Bob
Bug#717449: Acknowledgement (Generates /etc/network/interfaces config for eth0 although network-manager is installed (desktop task))
The syslog from the installation can be found at http://people.debian.org/~biebl/syslog -- 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#717454: lilo should register a namespace at the EFI System Partition Subdirectory Registry
Package: lilo Version: 1:24.0-2 Severity: wishlist Tags: upstream Hi. AFAIU you're also upstream for LILO!? :) I think it cannot harm (yes I know, right now you do not support EFI, but who knows what the future brings ... and even though the whole thing is anyway just voluntary), that lilo registers it's name at the EFI System Partition Subdirectory Registry: http://www.uefi.org/specs/esp_registry I guess that probably needs to be done by some officially authorised lilo person... Cheers, Chris. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#717453: elilo: new upstream version
Package: elilo Version: 3.14-3 Severity: wishlist Hi. A new upstream vesion (3.16) seems to be available. Cheers, Chris. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#691906: ITA: avra -- Assembler for Atmel AVR microcontrollers
Control: retitle -1 ITA: avra -- Assembler for Atmel AVR microcontrollers Control: owner -1 ! -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#717334: network-manager-applet: provide a simple network-manager-gtk package for non-GNOME GTK-based desktops
control: tags -1 wontfix Samuel Sanchez: gnome-bluetooth, gnome-keyring, gconf... The dependencies on gnome-keyring and gconf I can understand and I am fine with it. Would be just to much work and would not make sense. I totally agree with that. Michael Biebl: Am 21.07.2013 01:03, schrieb Bob Bib: Michael Biebl: What specifically do you mean by GNOME stuff? gnome-bluetooth, gnome-keyring, gconf... I already outlined what gnome-keyring and gnome-bluetooth are required for. gconf is simply needed because nm-applet uses that as configuration systemd. And no, I won't be re-implementing that with a homegrown config file solution, because that would be stupid. So, all in all, I don't really see a point for a -gtk package, and indeed so far this is a clear wont-fix bug. I'm even tempted to just close it. Don't take it too serious: I hope there are some other NM developers upstream, and we're not alone with it here in Debian :) I'm currently hesitating whether to report a request for a more lightweight GTK NM client upstream... Looks like currently it's not very bloated yet to report :) I think that wontfix is already sufficient, and it's better not to close it now. IMHO, it's good to leave this bug open to monitor the future user satisfaction level for actual NM-Applet's lightness. Best wishes, Bob
Bug#717455: cups-pdf fails to configure. Message: reloading CUPS: cupsd failed!
Package: cups-pdf Version: 2.6.1-6 Severity: important Tags: d-i Dear Maintainer, *** Please consider answering these questions, where appropriate *** * What led up to the situation? installing a usb postscript printer (Samsung ML-2571N) * What exactly did you do (or not do) that was effective (or ineffective)? Printer installed and works but had to kill the cupsd postinstall script to continue with the dpkg configuration process. * What was the outcome of this action? The cupsd post install was killed and the remaining packages configured and were set up. However, dpkg continues to find that the cups-pdg has not been successfully configured. * What outcome did you expect instead? cups-pdf to configure without hanging up in an endless loop. *** End of the template - remove these lines *** -- System Information: Debian Release: 7.1 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable') Architecture: i386 (i686) Kernel: Linux 3.2.0-4-686-pae (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 Versions of packages cups-pdf depends on: ii cups1.5.3-5 ii cups-client 1.5.3-5 ii ghostscript 9.05~dfsg-6.3 ii libc6 2.13-38 ii libpaper-utils 1.1.24+nmu2 cups-pdf recommends no packages. Versions of packages cups-pdf suggests: ii system-config-printer 1.3.7-4 ii system-config-printer-kde 4:4.8.4-3 -- 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#717456: data loss adding tarball of git-annex repository
Package: git-annex Version: 4.20130521 Severity: serious git-annex has a bug that can cause data loss: http://git-annex.branchable.com/bugs/git_annex_add_removes_file_with_no_data_left/ This probably only affects adding tarballs of git-annex repositories. Which is not a completely absurd use case. -- see shy jo signature.asc Description: Digital signature
Bug#717449: Info received (Bug#717449: Acknowledgement (Generates /etc/network/interfaces config for eth0 although network-manager is installed (desktop task)))
On IRC KiBi suspected the following line [1] to be the culprit: if in-target dpkg-query -s network-manager 2/dev/null | grep -q '^Status: install ok installed'; then I ran that on the d-i console, and the check was indeed not successful. Changing that to if in-target sh -c dpkg-query -s network-manager 2/dev/null | grep -q '^Status: install ok installed'; then fixed it for me. For comfirmation, I also ran the check against a non-installed package, to be sure the test was indeed working properly. Would be great to have this fix in the next point release. Cheers, Michael [1] http://anonscm.debian.org/gitweb/?p=d-i/netcfg.git;a=blob;f=finish-install.d/55netcfg-copy-config;h=507a3cd87800e49c3b629c2c140b708e186f4893;hb=c7d87b7c6a7a91e2844757218e7162295f67e3e0#l21 -- 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#710633: bison =2.6
This is related to bison. The issue starts with bison 2.6. Stable is OK. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#717458: debian/watch file is out of date
Source: libopenobex Version: 1.5-2 Severity: wishlist Tags: patch Hello, The watch file for libopenobex is out of date and doesn't show the latest vesions that are available on sourceforge due to a new naming convention by upstream. The attached watch file fixes this problem. --Joe -- System Information: Debian Release: jessie/sid APT prefers testing APT policy: (990, 'testing'), (500, 'unstable'), (200, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.9-1-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 version=3 # find new files on sourceforge, for debscripts = 2.9 http://sf.net/openobex/openobex-(.+)-Source\.(?:zip|tar\.gz) debian uupdate http://sf.net/openobex/openobex-([0-9\.]+)\.tar\.gz debian uupdate
Bug#717457: pu: package oss4/4.2-build2006-2+deb7u2
Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: pu Hi, oss4-dkms and oss4-source have insufficient dependencies and fail to build kernel modules in a minimal system. Since the module fails to build for the current kernel in sid, I cannot verify whether some of these dpendencies are missing is sid, too. Andreas diff -Nru oss4-4.2-build2006/debian/changelog oss4-4.2-build2006/debian/changelog --- oss4-4.2-build2006/debian/changelog 2012-12-16 02:07:45.0 +0100 +++ oss4-4.2-build2006/debian/changelog 2013-07-21 02:32:37.0 +0200 @@ -1,3 +1,11 @@ +oss4 (4.2-build2006-2+deb7u2) wheezy; urgency=low + + * Non-maintainer upload. + * oss4-dkms: Add missing Depends: dpkg-dev, libc6-dev. (Closes: #687086) + * oss4-source: Add missing Depends: gcc, libc6-dev. + + -- Andreas Beckmann a...@debian.org Sun, 21 Jul 2013 01:09:22 +0200 + oss4 (4.2-build2006-2+deb7u1) testing-proposed-updates; urgency=medium * Non-maintainer upload. diff -Nru oss4-4.2-build2006/debian/control oss4-4.2-build2006/debian/control --- oss4-4.2-build2006/debian/control 2012-12-16 01:56:29.0 +0100 +++ oss4-4.2-build2006/debian/control 2013-07-21 02:32:47.0 +0200 @@ -43,7 +43,7 @@ Package: oss4-dkms Section: kernel Architecture: linux-any -Depends: ${misc:Depends}, oss4-base, dkms, linux-headers-686-pae | linux-headers-amd64 | linux-headers-generic | linux-headers +Depends: ${misc:Depends}, oss4-base, dkms, dpkg-dev, libc6-dev, linux-headers-686-pae | linux-headers-amd64 | linux-headers-generic | linux-headers Provides: oss4-modules Description: Open Sound System - DKMS module sources This package contains the source for the OSS4 kernel modules, @@ -52,7 +52,7 @@ Package: oss4-source Architecture: linux-any -Depends: ${misc:Depends}, make, debhelper, module-assistant +Depends: ${misc:Depends}, make, debhelper, module-assistant, gcc, libc6-dev Description: Open Sound System - drivers sources This package provides the source code for the OSS4 kernel modules, in a form suitable for use by module-assistant.
Bug#717459: Please package new upstream version (1.7)
Source: libopenobex Version: 1.5-2 Severity: wishlist Hello, Upstream released version 1.7 on 2013-03-06. It would be great to have this new version in Debian, as hopefully it fixes some of the outstanding bugs. Thanks, --Joe -- System Information: Debian Release: jessie/sid APT prefers testing APT policy: (990, 'testing'), (500, 'unstable'), (200, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.9-1-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 -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#687086: oss4-dkms: missing dependency on dpkg-dev
Followup-For: Bug #687086 Hi, I just asked the release team for a wheezy-pu update (#717457) with the attached patch. Once that gets approvoed, I can NMU oss4 for wheezy unless a maintainer wants to take over from here. Andreas diff -Nru oss4-4.2-build2006/debian/changelog oss4-4.2-build2006/debian/changelog --- oss4-4.2-build2006/debian/changelog 2012-12-16 02:07:45.0 +0100 +++ oss4-4.2-build2006/debian/changelog 2013-07-21 02:32:37.0 +0200 @@ -1,3 +1,11 @@ +oss4 (4.2-build2006-2+deb7u2) wheezy; urgency=low + + * Non-maintainer upload. + * oss4-dkms: Add missing Depends: dpkg-dev, libc6-dev. (Closes: #687086) + * oss4-source: Add missing Depends: gcc, libc6-dev. + + -- Andreas Beckmann a...@debian.org Sun, 21 Jul 2013 01:09:22 +0200 + oss4 (4.2-build2006-2+deb7u1) testing-proposed-updates; urgency=medium * Non-maintainer upload. diff -Nru oss4-4.2-build2006/debian/control oss4-4.2-build2006/debian/control --- oss4-4.2-build2006/debian/control 2012-12-16 01:56:29.0 +0100 +++ oss4-4.2-build2006/debian/control 2013-07-21 02:32:47.0 +0200 @@ -43,7 +43,7 @@ Package: oss4-dkms Section: kernel Architecture: linux-any -Depends: ${misc:Depends}, oss4-base, dkms, linux-headers-686-pae | linux-headers-amd64 | linux-headers-generic | linux-headers +Depends: ${misc:Depends}, oss4-base, dkms, dpkg-dev, libc6-dev, linux-headers-686-pae | linux-headers-amd64 | linux-headers-generic | linux-headers Provides: oss4-modules Description: Open Sound System - DKMS module sources This package contains the source for the OSS4 kernel modules, @@ -52,7 +52,7 @@ Package: oss4-source Architecture: linux-any -Depends: ${misc:Depends}, make, debhelper, module-assistant +Depends: ${misc:Depends}, make, debhelper, module-assistant, gcc, libc6-dev Description: Open Sound System - drivers sources This package provides the source code for the OSS4 kernel modules, in a form suitable for use by module-assistant.
Bug#717460: provide debug package for libopenobex
Source: libopenobex Version: 1.5-2 Severity: wishlist Hello, A number of people, myself included, are seeing segfaults within libopenobex. It would be great if you would provide a -dbg package containing the debugging symbols so that we can get proper backtraces. Thanks, --Joe -- System Information: Debian Release: jessie/sid APT prefers testing APT policy: (990, 'testing'), (500, 'unstable'), (200, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.9-1-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 -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#717408: Debian Bug #717408,gparted: Unable to create fat16/fat32 using dosfstools 3.0.22-1
Thank you Dmitri for reporting this problem. It appears that there was a change in dosfstool program names introduced in dosfstools 3.0.18. See the following commit: Renaming tools to sane namespace and keeping legacy symlinks in place. http://daniel-baumann.ch/gitweb/?p=software/dosfstools.git;a=commit;h=ea8f712730ceeb88560cbd5beeea368a28befab2 dosfslabel becomes fatlabel, dosfsck becomes fsck.fat, and mkdosfs becomes mkfs.fat. Since GParted uses the older names from dosfstools 3.0.17 and earlier, this name change breaks GParted FAT16 and FAT32 support. A temporary work around would be to create symbolic links for the old names. For example, something like the following commands should work: sudo ln -s /sbin/fsck.fat /sbin/dosfsck sudo ln -s /sbin/mkfs.fat /sbin/mkdosfs Regards, Curtis -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#699740: segfault in libopenobex.so.1.5.0 when sending file to phone
Package: libopenobex1 Followup-For: Bug #699740 I can confirm that this problem exists in the version of libopenobex1 currently in jessie. Also confirmed is that the patch from z7z8th ybzhao1...@gmail.com on 2013-02-04 fixes the problem. Please upload a new version that includes this patch. Thanks, --Joe -- System Information: Debian Release: jessie/sid APT prefers testing APT policy: (990, 'testing'), (500, 'unstable'), (200, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.9-1-amd64 (SMP w/4 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages libopenobex1 depends on: ii libc6 2.17-7 ii libusb-0.1-4 2:0.1.12-23.2 libopenobex1 recommends no packages. libopenobex1 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#717448: apache2: Invalid command 'AuthType'
Which version of phpmyadmin are you installing? Try $ a2enmod authn_core It fixes the same problem here. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#717462: bash-completion: all kinds of issues with the lvm2 completitions
Package: bash-completion Version: 1:2.0-1 Severity: normal Tags: upstream 1) pvcreate and vgcreate should complete to existin PV / VG names. It's usually not intended to re-create (overwrite) already existing PV / VG names, actually it even risks data loss if one accidentally completes to that and has --force given. Rather let it at the plain normal bash file completion here. 2) _units() and _sizes() functions The strings used there seems to differ from what lvm currently supports bBsSkKmMgGtTpPeE also, not all parameters seem to support all of these units, e.g. --poolmetadatasize has only bBsSkKmMgG (or perhaps that's a documentation error). 3) Direct use of programs The completions seem to make direct use of some programs (e.g. vgscan, etc.) Please use lvm command in all these cases instead, since the shortcuts may not be present 4) Many options to the different commands and attributes to vgs/pvs/lvs seem to be missing. 5) Big issue: in _volumegroups(), _physicalvolumes(), _logicalvolumes() you use vgscan, lvscan, pvscan to find out the names. This should not be done, as it also modifies the cache, which may be undesired. Why not simply using the faster, more easy to parse: pvs -o pv_name vgs -o vg_name lvs -o lv_name ? 6) The current patterns in _volumegroups(), _physicalvolumes(), _logicalvolumes() seem to be buggy anyway. E.g. the one for the LVs doesn’t match LVs which don't belong to a VG. And when doing e.g. pvremove, these are the most likely ones, one want to complete to. So I gess one needs to functions, which reports assigned and unassigned PVs and those are used depending on the command. Cheers, Chris. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#685480: libpam-mysql: on amd64: pam_mysql - non-crypt()ish MD5 hash is not supported in this build.
I could not make it work with building from source --with-openssl.. md5.h does not get detected.. What did work was to install the packages from squeeze including openssl 0.9.8 and libmysqlclient16 Hope for a better solution than the above workaround.
Bug#716839: (no subject)
Daniel, are you suggesting that the fix is to untar the upstream tar file over the top of the dpkg installed files? From a system management and stability point of view I find this option undesirable. Anyway here is a unified diff that fixes the problem with the LVM backing store and still works with the default backing store. I haven't tested other backing stores but their behaviour should be unchanged. I'd consider it highly desirable to get this patch in the Debian package so that LXC isn't broken with an LVM backing store. --- lxc-debian-wheezy 2013-07-21 01:49:25.518395282 +1000 +++ /usr/share/lxc/templates/lxc-debian-wheezy 2013-07-21 11:56:48.479221496 +1000 @@ -124,8 +124,16 @@ rootfs=$3 # make a local copy of the minidebian + # We need to behave differently if $rootfs exists and is a + # directory, as happens when we use LVM as a backing store. echo -n Copying rootfs to $rootfs... -cp -a $cache/rootfs-$arch $rootfs || return 1 + if [ -d $rootfs ] + then + cp -a $cache/rootfs-$arch/* $rootfs || return 1 + else + cp -a $cache/rootfs-$arch $rootfs || return 1 + fi + return 0 } -- Email: rob...@timetraveller.org Linux counter ID #16440 IRC: Solver (OFTC Freenode) Web: http://www.pracops.com Director, Software in the Public Interest (http://spi-inc.org/) Information is a gas -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#714092: installation-reports: wheezy install on QNAP TS-212 fails to write to flash
* Ben Hutchings b...@decadent.org.uk [2013-07-20 22:40]: I've added the N25Q128 IDs but didn't bother with the 256 Mbit part (not needed for this system). So this should be fixed in Debian 7.2. Thanks! -- Martin Michlmayr http://www.cyrius.com/ -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#717463: hangs on connection to xmpp server that does not send features
Package: haskell-network-protocol-xmpp Version: 0.4.4 Severity: minor Attached pcap shows git-annex connecting to a XMPP server. This connection hangs, because the XMPP library is expecting the server to send a features tag, which it never does. This seems to be a violation of RFC6120, which requires the features tag. However, I'm told that other XMPP clients successfully manage to connect to this server. So perhaps the haskell library could also try to finesse this somehow. I suppose it could assume that if the stream has been opened and no features tag appears within some unit of time, the server is broken, and continue with XMPP traffic as if an empty tag had been sent. More discussion here. http://git-annex.branchable.com/bugs/cannot_connect_to_xmpp_server/?updated#comment-5e59ae67fbcde3c90eb3042f1b07be24 -- see shy jo signature.asc Description: Digital signature
Bug#717464: VM hangs on boot if there are more than 7 virtio block devices
Package: seabios Version: 1.7.3-1 my zfs test VM boots without a problem if it has seven disks (1x5GB boot/OS zvol, 6 x 200M files) or less. It still works if I boot with 7 disks and then use 'virsh attach-disk' to add another virtio disk (or five. or ten). the added drives appear in the system and i can use them without any problem, including adding them to my test zpool. rebooting the VM with more than seven disks attached causes it to lock up at the BIOS screen, immediately after the Booting from Hard Disk... message. CPU utilisation of the qemu process at this point is about 90% (of one core of a Phenom II 1090T), and it stays that way until i kill the VM - i left one instance of the VM running overnight to see if it would eventually get started (nope). the only info i can find with google on block device limits suggests that kvm has a limit of 4 IDE devices and 20 virtio block devices, from an opensuse page: http://doc.opensuse.org/documentation/html/openSUSE/opensuse-kvm/cha.kvm.limits.html#sec.kvm.limits.hardware the fact that 'virsh attach-disk' works suggests that it's not a kvm/qemu limitation, anyway. craig ps: i'm not really sure if this bug belongs to qemu or to seabios. seabios seems most likely. pps: this used to work in previous versions. another zfs testing VM that I made early last year used to boot with nine virtio disks (vda ... vdi). i last booted it a few months ago. it failed to boot yesterday morning and i assumed it was a problem with the VM, so i created this new ztest vm only to encounter the same problem when i added the extra drives for the test pool. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#636778: linux-image-2.6.39-2-686-pae: NTSC video does not work with saa7164 Hauppauge board
Hi, You can close this. NTSC broadcast over the air has been abandoned in at least my region. Thanks for your efforts. Michael From: Moritz Muehlenhoff j...@inutil.org To: mpapet mpa...@yahoo.com Cc: 636...@bugs.debian.org; cont...@bugs.debian.org Sent: Thursday, July 18, 2013 9:48 AM Subject: Re: linux-image-2.6.39-2-686-pae: NTSC video does not work with saa7164 Hauppauge board reassign 636778 src:linux severity 636778 normal thanks On Fri, Aug 05, 2011 at 01:59:40PM -0700, mpapet wrote: Package: linux-2.6 Version: 2.6.39-3 Severity: important Hi, Two possible bugs: 1: Cannot play NTSC channels. Blue screen. Behavior occurs in xawtv, on the command line using ffmpeg and mythtv. Always reproduceable. 2: A scan for station signals does not detect any television stations. Possibly related to #1. An application like scantv and mythtv's tuner scan cannot detect any stations. ATSC works great. And antenna is attached. (I know because I can watch ATSC) Anecdotal information suggests NTSC might works for people who compiled a kernel from kernel.org. Does this still occur in more recent kernels? Cheers, Moritz
Bug#647877: Bug#717123: RFS: superkb/0.22-5 [ITP #647877] -- keyboard launcher with on-screen hints
Hi. I uploaded a new version for Superkb, the package for which I'm trying to get sponsorship. The new version is 0.22-5 and this is what I changed: superkb (0.22-5) unstable; urgency=low * Added lintian override for no-upstream-changelog, because it is not in English and this has been fixed upstream. Next upstream release will properly include a changelog and this override will be removed. * Fixed man page invocation to help2man for proper text in the NAME section. * Moved sample-config/superkbrc to debian/ and removed the patch. * Include sample config files under /usr/share/doc/superkb/sample-config. * Improved man page superkb.1. So, technically, the package has no more lintian --pedantic warnings unattended, and hopefully the next upstream version will have most patches directly incorporated (because upstream is me) so the package will become simpler in the future. Even though I'm asking for sponsorship, I'd really appreciate a review even if it's not sponsored. Thanks in advance. Octavio. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#717463: Acknowledgement (hangs on connection to xmpp server that does not send features)
Forgotten attachement attahced this time. Also, the server appears to be running jabberd 1.4.3. -- see shy jo annex-xmpp-connection.pcap Description: application/vnd.tcpdump.pcap signature.asc Description: Digital signature
Bug#714092: installation-reports: wheezy install on QNAP TS-212 fails to write to flash
On Sat, Jul 20, 2013 at 20:03:14 -0700, Martin Michlmayr wrote: * Ben Hutchings b...@decadent.org.uk [2013-07-20 22:40]: I've added the N25Q128 IDs but didn't bother with the 256 Mbit part (not needed for this system). So this should be fixed in Debian 7.2. Thanks! Yes, thanks very much Ben! -- mike -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org