Bug#767037: Grub EFI fallback - patches for review
On Mon, 2014-12-01 at 13:57 +, Steve McIntyre wrote:
Starting with grub-install-fallback.patch:
From e384e597914b6e1b1dcbf96ef6782cf9bcc2313b Mon Sep 17 00:00:00 2001
debian/patches/grub-install-extra-removable.patch | 115
++
Could you send this to grub-de...@gnu.org? Or at least provide a commit
log for the upstream bit inline in the patch for whoever does end up
forwarding it.
+@@ -829,6 +838,27 @@ fill_core_services (const char *core_ser
+ free (sysv_plist);
+ }
+
++static void
++also_install_removable(const char *src, const char *base_efidir, const char
*efi_suffix_upper)
++{
++ char *efi_file = NULL;
++ char *dst = NULL;
++ char *dir = NULL;
++
++ if (!efi_suffix_upper)
++grub_util_error (%s, _(You've found a bug));
There are one or two of these in the upstream code base already, but it
is a bit unfriendly to the bug-reported/triagger.
I see an existing instance of
_(you found a bug ... (%s:%d)\n), file, line)
which is a bit nicer at least. Plain old assert() sees some usage too.
The Debian-specific bits all look sensible to me, FWIW. There will be a
minor conflict with the patches in #770412 but nothing insurmountable.
[...]
+ also depend on this path. If so, uou will need to ensure that GRUB is
Typo: uou.
Ian.
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#767037: Grub EFI fallback - patches for review
On Mon, 2014-12-01 at 13:57 +, Steve McIntyre wrote:
grub-installer-rescue-UEFI-removable.patch:
diff --git a/debian/grub-installer.templates b/debian/grub-installer.templates
index e439ad0..a6af2ec 100644
--- a/debian/grub-installer.templates
+++ b/debian/grub-installer.templates
@@ -209,6 +209,21 @@ Type: text
# :sl1:
_Description: Updating /etc/kernel-img.conf...
+Template: grub-installer/progress/step_force_efi
Perhaps add _removable at the end of the name?
I didn't review the text since that seems to have been done already.
diff --git a/rescue.d/81grub-efi-force-removable
b/rescue.d/81grub-efi-force-removable
I don't know much about rescue mode, is this offering an automatic fixup
for this issue? Does it appear in a menu to be selected rather than
asking everyone booting rescue on an EFI system?
+mountvirtfs () {
+ fstype=$1
+ path=$2
+ if grep -q [[:space:]]$fstype\$ /proc/filesystems \
+ ! grep -q ^[^ ]\+ \+$path /proc/mounts; then
+ mkdir -p $path || \
+ die grub-installer/mounterr Error creating $path
+ mount -t $fstype $fstype $path || \
+ die grub-installer/mounterr Error mounting $path
+ trap umount $path HUP INT QUIT KILL PIPE TERM EXIT
trap doesn't stack, does it? You call mountvirtfs twice, so only the
second umount will actually happen on error.
Also you umount explicitly on the exit path, but don't cancel this trap,
so I guess you'll see some noise from umount the second time.
I know we've established that in-target isn't widely used in this
particular bit of code -- but it does take care of all this sort of
thing automatically and (presumably!) correctly, as well as being only a
single place to fix if it is wrong (e.g. in-target handles BSD
explicitly too).
+log Mounting filesystems
+# If we're installing grub-efi, it wants /sys mounted in the
+# target. Maybe /proc too?
+mountvirtfs proc /target/proc
+mountvirtfs sysfs /target/sys
+chroot /target mount /boot/efi || true
+
+db_progress STEP 1
+db_progress INFO grub-installer/progress/step_install_loader
+# Do the installation now
+log Running grub-install
+if ! chroot /target grub-install --force-extra-removable; then
The main invocation would invoke this with a --target=foo-efi. Not
sure if this matters or not.
In order to avoid having to repeat all the logic twice perhaps you could
arrange to do the debconf-set-selections thing first and then run
dpkg-reconfigure or something in the target to force the main postinst
to rerun and reinstall?
+ db_input critical grub-installer/grub-install-failed || true
+ db_go || true
+ db_progress STOP
+ exit 1
You don't umount /target/boot/efi on this path.
Ian.
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#771719: tcplay: does not support discs with 4k sectors
Hi László, Yes, it seems it was fixed in 2.0, but it has a somewhat unclear license. Ouch. Do you have a pointer to the issue? I've backported the fix for 1.1. But don't have any 4k discs nearby, can you test it for me? You should build it for yourself[1] and only in the last chance use my own binary packages for amd64[2] or i386[3]. Since I'm going to run this stuff as root, I'd prefer to have some cryptographic evidence that this is actually the version you are trying to send me. Your server doesn't seem to do https. I tried getting the source of the package as it is currently in Debian (to verify the upstream part, and then diff the debian part), but dget says verification failed. Once I got it build, I can sure test it, but it may be until Thursday that I have access to the disc *and* time to do this. Kind regards Ralf -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#770918: marked as done (flac: CVE-2014-8962/CVE-2014-9028: heap buffer overflows)
Your message dated Tue, 02 Dec 2014 09:20:39 + with message-id e1xvjdp-0001bu...@franck.debian.org and subject line Bug#770918: fixed in flac 1.3.1-1 has caused the Debian Bug report #770918, regarding flac: CVE-2014-8962/CVE-2014-9028: heap buffer overflows to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 770918: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=770918 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: flac Version: 1.3.0-2+b1 Severity: serious Tags: security From: http://lists.xiph.org/pipermail/flac-dev/2014-November/005226.html Google Security Team member, Michele Spagnuolo, recently found two potential problems in the FLAC code base. They are : CVE-2014-9028 : Heap buffer write overflow CVE-2014-8962 : Heap buffer read overflow For Linux distributions, the specific fixes for these two CVEs are available from Git here: https://git.xiph.org/?p=flac.git;a=commit;h=fcf0ba06ae12ccd7c67cee3c8d948df15f946b85 https://git.xiph.org/?p=flac.git;a=commit;h=5b3033a2b355068c11fe637e14ac742d273f076e and are simple enough that they should apply cleanly to the last official release 1.3.0 and possibly even the previous one, 1.2.1. A pre-release (version 1.3.1pre1) for the next version which includes these fixes and more is available here: http://downloads.xiph.org/releases/flac/beta/ A full release (version 1.3.1) will be available in the next couple of days. -- System Information: Debian Release: jessie/sid APT prefers testing APT policy: (900, 'testing'), (800, 'unstable'), (500, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.17-rc5-amd64 (SMP w/4 CPU cores) Locale: LANG=en_AU.UTF-8, LC_CTYPE=en_AU.UTF-8 (charmap=UTF-8) (ignored: LC_ALL set to en_AU.UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages flac depends on: ii libc6 2.19-13 ii libflac8 1.3.0-2+b1 flac recommends no packages. flac suggests no packages. -- no debconf information ---End Message--- ---BeginMessage--- Source: flac Source-Version: 1.3.1-1 We believe that the bug you reported is fixed in the latest version of flac, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 770...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Fabian Greffrath fabian+deb...@greffrath.com (supplier of updated flac package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Mon, 01 Dec 2014 18:32:57 +0100 Source: flac Binary: flac libflac8 libflac-doc libflac-dev libflac++6 libflac++-dev Architecture: source amd64 all Version: 1.3.1-1 Distribution: experimental Urgency: medium Maintainer: Debian Multimedia Maintainers pkg-multimedia-maintain...@lists.alioth.debian.org Changed-By: Fabian Greffrath fabian+deb...@greffrath.com Description: flac - Free Lossless Audio Codec - command line tools libflac++-dev - Free Lossless Audio Codec - C++ development library libflac++6 - Free Lossless Audio Codec - C++ runtime library libflac-dev - Free Lossless Audio Codec - C development library libflac-doc - Free Lossless Audio Codec - library documentation libflac8 - Free Lossless Audio Codec - runtime C library Closes: 770918 Changes: flac (1.3.1-1) experimental; urgency=medium . [ Jackson Doak ] * Disable silent rules * Enable hardening * Add symbols files . [ Fabian Greffrath ] * Adapt debian/watch file to reflect actual upstream versioning scheme. * Imported Upstream version 1.3.1 + Fixes CVE-2014-8962 and CVE-2014-9028 (Closes: #770918). + Support for 3DNOW! optimizations has been removed. + Localized RU documentation has been removed. * Drop patches applied upstream. * Backport patch from upstream GIT to fix another input validation bug. * Fix privacy-breach-logo and privacy-breach-w3c-valid-html lintian errors. * In debian/rules, remove the override_dh_makeshlibs rule for the symbols files to have effect. * Update, improve and convert debian/copyright to machine-readable format. * Bump Standards-Version to 3.9.6. Checksums-Sha1:
Bug#766308: marked as done (Fails to purge: /var/lib/dpkg/info/mdadm.postrm: 9: /usr/share/debconf/confmodule: DEBIAN_HAS_FRONTEND: parameter not set)
Your message dated Tue, 02 Dec 2014 09:22:07 + with message-id e1xvjep-0001ub...@franck.debian.org and subject line Bug#766308: fixed in mdadm 3.3.2-3 has caused the Debian Bug report #766308, regarding Fails to purge: /var/lib/dpkg/info/mdadm.postrm: 9: /usr/share/debconf/confmodule: DEBIAN_HAS_FRONTEND: parameter not set to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 766308: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=766308 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: mdadm Version: 3.3.2-2 Severity: serious SUMMARY: set -u breaks debconf. You can't have it in effect in your postrm when sourcing it. DETAILS: root@Heisenberg:~# dpkg --purge mdadm (Reading database ... 313312 files and directories currently installed.) Removing mdadm (3.3.2-2) ... Purging configuration files for mdadm (3.3.2-2) ... /var/lib/dpkg/info/mdadm.postrm: 9: /usr/share/debconf/confmodule: DEBIAN_HAS_FRONTEND: parameter not set dpkg: error processing package mdadm (--purge): subprocess installed post-removal script returned error exit status 2 Errors were encountered while processing: mdadm root@Heisenberg:~# Adding set -x to the top of the postrm (editing the file in /var/lib/dpkg/info), shows that it's blowing up here: # Automatically added by dh_installdebconf if [ $1 = purge ] [ -e /usr/share/debconf/confmodule ]; then --- . /usr/share/debconf/confmodule --- db_purge fi And that's because you have set -ue at the top of the script, the -u being the problem. Once I remove that, the package purges successfully. -- System Information: Debian Release: jessie/sid APT prefers testing APT policy: (500, 'testing'), (150, 'unstable'), (125, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.16-3-amd64 (SMP w/2 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages mdadm depends on: ii debconf 1.5.53 ii initscripts 2.88dsf-53.4 ii libc62.19-11 ii lsb-base 4.1+Debian13 ii udev 215-5+b1 Versions of packages mdadm recommends: ii exim4-daemon-light [mail-transport-agent] 4.84-2 ii module-init-tools 18-3 mdadm suggests no packages. ---End Message--- ---BeginMessage--- Source: mdadm Source-Version: 3.3.2-3 We believe that the bug you reported is fixed in the latest version of mdadm, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 766...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Michael Tokarev m...@tls.msk.ru (supplier of updated mdadm package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.8 Date: Fri, 28 Nov 2014 09:55:14 +0300 Source: mdadm Binary: mdadm mdadm-udeb Architecture: source amd64 Version: 3.3.2-3 Distribution: unstable Urgency: medium Maintainer: Debian mdadm maintainers pkg-mdadm-de...@lists.alioth.debian.org Changed-By: Michael Tokarev m...@tls.msk.ru Description: mdadm - tool to administer Linux MD arrays (software RAID) mdadm-udeb - tool to administer Linux MD arrays (software RAID) (udeb) Closes: 764036 764647 766308 766416 Changes: mdadm (3.3.2-3) unstable; urgency=medium . * remove /var/lib/mdadm dir in postinst to clean up from old pkg, remove config files on purge (restore extraneous cleanup from last change) (Closes: #764036) * remove set -u (error on unset variables) from maintscripts (Closes: #766308) * rebuildmap-strip-local-host-name-from-device-name.patch - a patch from upstream fixing a bug when mdadm have to re-create device nodes after assembling arrays (eg, when switching from initramfs without preserving /dev and /run), to choose the same device names as when doing inital assembly * readlink-path.patch: readlink is in /bin not /usr/bin on debian (Closes: #766416) * mdmonitor-service-simplify.diff: simplify mdmonitor.service systemd file, do not try to read non-existing files (Closes: #764647) Checksums-Sha1: b35d0b9ae4391a5cff56722b4907749c672a1b58 1626 mdadm_3.3.2-3.dsc
Processed: notfound 771739 in 215-7
Processing commands for cont...@bugs.debian.org: notfound 771739 215-7 Bug #771739 [systemd] could not start nodm with systemd 217-1 or 217-2 Ignoring request to alter found versions of bug #771739 to the same values previously set thanks Stopping processing here. Please contact me if you need assistance. -- 771739: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=771739 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#771778: squid3: Pinger segfault with libc
Package: squid3
Version: 3.4.8-2
Severity: critical
Justification: breaks the whole system
Dear Maintainer,
*** Please consider answering these questions, where appropriate ***
* What led up to the situation?
* What exactly did you do (or not do) that was effective (or
ineffective)?
* What was the outcome of this action?
* What outcome did you expect instead?
*** End of the template - remove these lines ***
-- System Information:
Debian Release: 7.7
APT prefers stable-updates
APT policy: (500, 'stable-updates'), (500, 'stable')
Architecture: amd64 (x86_64)
Kernel: Linux 3.2.0-4-amd64 (SMP w/8 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Versions of packages squid3 depends on:
ii adduser 3.113+nmu3
ii libc62.13-38+deb7u6
ii libcap2 1:2.22-1.2
ii libcomerr2 1.42.5-1.1
ii libdb5.1 5.1.29-5
ii libecap2 0.2.0-1
ii libexpat12.1.0-1+deb7u1
ii libgcc1 1:4.7.2-5
ii libgssapi-krb5-2 1.10.1+dfsg-5+deb7u2
ii libk5crypto3 1.10.1+dfsg-5+deb7u2
ii libkrb5-31.10.1+dfsg-5+deb7u2
ii libldap-2.4-22.4.31-1+nmu2
ii libltdl7 2.4.2-1.1
ii libnetfilter-conntrack3 1.0.1-1
ii libnettle4 2.7.1-3
ii libpam0g 1.1.3-7.1
ii libsasl2-2 2.1.25.dfsg1-6+deb7u1
ii libstdc++6 4.7.2-5
ii libxml2 2.8.0+dfsg1-7+wheezy2
ii logrotate3.8.1-4
ii lsb-base 4.1+Debian8+deb7u1
ii netbase 5.0
ii squid3-common3.4.8-2
squid3 recommends no packages.
Versions of packages squid3 suggests:
pn resolvconf none
pn smbclientnone
ii squid-cgi3.4.8-2
ii squid-purge 3.4.8-2
ii squidclient 3.4.8-2
ii ufw 0.31.1-2
pn winbindd none
-- Configuration Files:
/etc/logrotate.d/squid3 changed:
/var/log/squid3/*.log {
daily
compress
delaycompress
rotate 14
missingok
nocreate
sharedscripts
postrotate
test ! -e /var/run/squid3.pid || test ! -x /usr/sbin/squid3 ||
/usr/sbin/squid3 -k rotate
endscript
}
/etc/squid3/errorpage.css changed:
/*
Stylesheet for Squid Error pages
Adapted from design by Free CSS Templates
http://www.freecsstemplates.org
Released for free under a Creative Commons Attribution 2.5 License
*/
/* Page basics */
* {
font-family: verdana, sans-serif;
}
html body {
margin: 0;
padding: 0;
background: #efefef;
font-size: 12px;
color: #1e1e1e;
}
/* Page displayed title area */
margin-left: 15px;
padding: 10px;
padding-left: 100px;
background: url('http://rtd-proxy1.rotterdam.bazuin.nl/Artwork/SN.png')
no-repeat left;
}
/* initial title */
color: #00;
}
color: #00;
}
/* special event: FTP success page titles */
background-color:#00ff00;
width:100%;
}
/* Page displayed body content area */
padding: 10px;
background: #ff;
}
/* General text */
p {
}
/* error brief description */
}
/* some data which may have caused the problem */
}
/* the error message received from the system or other software */
}
pre {
font-family:sans-serif;
}
/* special event: FTP / Gopher directory listing */
font-family: courier;
color: black;
font-size: 10pt;
}
margin-left: 2%;
margin-right: 2%;
}
border-bottom: groove;
}
width: 50px;
text-align: right;
padding-right: 5px;
}
/* horizontal lines */
hr {
margin: 0;
}
/* page displayed footer area */
font-size: 9px;
padding-left: 10px;
}
/etc/squid3/squid.conf changed:
include /etc/squid3/conf.d/*.conf
/etc/ufw/applications.d/squid3 changed:
[Squid]
title=Squid proxy cache
description=Internet object cache (WWW proxy cache)
ports=2048,3128,3130,3401,4827,8080/tcp
-- no debconf information
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#728113: smartmontools still broken
I have just tried running smartctl with the updated binutils version 2.24.90.20141201-1, however the bug is still there. $ smartctl -a /dev/sda Inconsistency detected by ld.so: dl-version.c: 224: _dl_check_map_versions: Assertion `needed != ((void *)0)' failed! br, Thomas -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#728113: smartmontools still broken
On Tue, Dec 02, 2014 at 11:02:27AM +0100, Thomas Prokosch wrote: I have just tried running smartctl with the updated binutils version 2.24.90.20141201-1, however the bug is still there. $ smartctl -a /dev/sda Inconsistency detected by ld.so: dl-version.c: 224: _dl_check_map_versions: Assertion `needed != ((void *)0)' failed! Please note that you need to rebuild the package for the error to go away. Kurt -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#771779: libc6: dpkg error trying to install libc6:mips and libc6:mipsel together
Package: libc6 Version: 2.19-13 Severity: serious Hi, When I try to install libc6:mips and libc6:mipsel together, I get the following error: Preconfiguring packages ... Selecting previously unselected package libc6:mips. (Reading database ... 216565 files and directories currently installed.) Preparing to unpack .../libc6_2.19-13_mips.deb ... Unpacking libc6:mips (2.19-13) ... Selecting previously unselected package libgcc1:mips. Preparing to unpack .../libgcc1_1%3a4.9.2-4_mips.deb ... Unpacking libgcc1:mips (1:4.9.2-4) ... Preparing to unpack .../libc6_2.19-13_mipsel.deb ... Unpacking libc6:mipsel (2.19-13) ... dpkg: error processing archive /var/cache/apt/archives/libc6_2.19-13_mipsel.deb (--unpack): trying to overwrite shared '/lib/ld.so.1', which is different from other instances of package libc6:mipsel Selecting previously unselected package libgcc1:mipsel. Preparing to unpack .../libgcc1_1%3a4.9.2-4_mipsel.deb ... Unpacking libgcc1:mipsel (1:4.9.2-4) ... Errors were encountered while processing: /var/cache/apt/archives/libc6_2.19-13_mipsel.deb E: Sub-process /usr/bin/dpkg returned an error code (1) Failed to perform requested operation on package. Trying to recover: dpkg: dependency problems prevent configuration of libgcc1:mipsel: libgcc1:mipsel depends on libc6 (= 2.2.4); however: Package libc6:mipsel is not installed. dpkg: error processing package libgcc1:mipsel (--configure): dependency problems - leaving unconfigured Setting up libc6:mips (2.19-13) ... Setting up libgcc1:mips (1:4.9.2-4) ... Processing triggers for libc-bin (2.19-13) ... Errors were encountered while processing: libgcc1:mipsel Thanks, James -- System Information: Debian Release: 8.0 APT prefers unstable APT policy: (500, 'unstable'), (500, 'testing'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 mips mipsel Kernel: Linux 3.16.0-4-amd64 (SMP w/4 CPU cores) Locale: LANG=en_GB.utf8, LC_CTYPE=en_GB.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#771778: Acknowledgement (squid3: Pinger segfault with libc)
extra info. This is on debian wheezy, squid recompiled from jesse with icap and i did rebuild to a deb : squidclamav 6.11 bug 760303, which looks like it. The bugcheck is : 2014/12/02 06:00:10 kid1| NETDB state saved; 633 entries, 2 msec 2014/12/02 06:25:04 kid1| Closing Pinger socket on FD 26 2014/12/02 06:25:18| Pinger exiting. *** glibc detected *** (pinger): free(): invalid next size (normal): 0x7fb19ba45df0 *** === Backtrace: = /lib/x86_64-linux-gnu/libc.so.6(+0x76a16)[0x7fb1987b6a16] /lib/x86_64-linux-gnu/libc.so.6(cfree+0x6c)[0x7fb1987bb7bc] /usr/lib/x86_64-linux-gnu/libstdc++.so.6(_ZNSt19basic_ostringstreamIcSt11char_traitsIcESaIcEED0Ev+0xa6)[0x7fb19900dae6] (pinger)(+0x8d99)[0x7fb19a108d99] (pinger)(+0x59c5)[0x7fb19a1059c5] (pinger)(main+0x2a0)[0x7fb19a104550] /lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0xfd)[0x7fb19875eead] (pinger)(+0x50a9)[0x7fb19a1050a9] === Memory map: 7fb19400-7fb194021000 rw-p 00:00 0 7fb194021000-7fb19800 ---p 00:00 0 7fb19811-7fb198116000 r-xp ca:01 134270 /usr/lib/libnfnetlink.so.0.2.0 7fb198116000-7fb198315000 ---p 6000 ca:01 134270 /usr/lib/libnfnetlink.so.0.2.0 7fb198315000-7fb198316000 rw-p 5000 ca:01 134270 /usr/lib/libnfnetlink.so.0.2.0 7fb198318000-7fb19831c000 r-xp ca:01 44 /lib/x86_64-linux-gnu/libattr.so.1.1.0 7fb19831c000-7fb19851b000 ---p 4000 ca:01 44 /lib/x86_64-linux-gnu/libattr.so.1.1.0 7fb19851b000-7fb19851c000 r--p 3000 ca:01 44 /lib/x86_64-linux-gnu/libattr.so.1.1.0 7fb19851c000-7fb19851d000 rw-p 4000 ca:01 44 /lib/x86_64-linux-gnu/libattr.so.1.1.0 7fb19852-7fb198537000 r-xp ca:01 64 /lib/x86_64-linux-gnu/libpthread-2.13.so 7fb198537000-7fb198736000 ---p 00017000 ca:01 64 /lib/x86_64-linux-gnu/libpthread-2.13.so 7fb198736000-7fb198737000 r--p 00016000 ca:01 64 /lib/x86_64-linux-gnu/libpthread-2.13.so 7fb198737000-7fb198738000 rw-p 00017000 ca:01 64 /lib/x86_64-linux-gnu/libpthread-2.13.so 7fb198738000-7fb19873c000 rw-p 00:00 0 7fb19873f000-7fb19874 rw-p 00:00 0 7fb19874-7fb1988c2000 r-xp ca:01 3330 /lib/x86_64-linux-gnu/libc-2.13.so 7fb1988c2000-7fb198ac2000 ---p 00182000 ca:01 3330 /lib/x86_64-linux-gnu/libc-2.13.so 7fb198ac2000-7fb198ac6000 r--p 00182000 ca:01 3330 /lib/x86_64-linux-gnu/libc-2.13.so 7fb198ac6000-7fb198ac7000 rw-p 00186000 ca:01 3330 /lib/x86_64-linux-gnu/libc-2.13.so 7fb198ac7000-7fb198acc000 rw-p 00:00 0 7fb198ad-7fb198ae5000 r-xp ca:01 15 /lib/x86_64-linux-gnu/libgcc_s.so.1 7fb198ae5000-7fb198ce5000 ---p 00015000 ca:01 15 /lib/x86_64-linux-gnu/libgcc_s.so.1 7fb198ce5000-7fb198ce6000 rw-p 00015000 ca:01 15 /lib/x86_64-linux-gnu/libgcc_s.so.1 7fb198ce8000-7fb198d69000 r-xp ca:01 3335 /lib/x86_64-linux-gnu/libm-2.13.so 7fb198d69000-7fb198f68000 ---p 00081000 ca:01 3335 /lib/x86_64-linux-gnu/libm-2.13.so 7fb198f68000-7fb198f69000 r--p 0008 ca:01 3335 /lib/x86_64-linux-gnu/libm-2.13.so 7fb198f69000-7fb198f6a000 rw-p 00081000 ca:01 3335 /lib/x86_64-linux-gnu/libm-2.13.so 7fb198f7-7fb199058000 r-xp ca:01 133196 /usr/lib/x86_64-linux-gnu/libstdc++.so.6.0.17 7fb199058000-7fb199258000 ---p 000e8000 ca:01 133196 /usr/lib/x86_64-linux-gnu/libstdc++.so.6.0.17 7fb199258000-7fb19926 r--p 000e8000 ca:01 133196 /usr/lib/x86_64-linux-gnu/libstdc++.so.6.0.17 7fb19926-7fb199262000 rw-p 000f ca:01 133196 /usr/lib/x86_64-linux-gnu/libstdc++.so.6.0.17 7fb199262000-7fb199277000 rw-p 00:00 0 7fb199278000-7fb19927a000 r-xp ca:01 /lib/x86_64-linux-gnu/libdl-2.13.so 7fb19927a000-7fb19947a000 ---p 2000 ca:01 /lib/x86_64-linux-gnu/libdl-2.13.so 7fb19947a000-7fb19947b000 r--p 2000 ca:01 /lib/x86_64-linux-gnu/libdl-2.13.so 7fb19947b000-7fb19947c000 rw-p 3000 ca:01 /lib/x86_64-linux-gnu/libdl-2.13.so 7fb19948-7fb199487000 r-xp ca:01 3348 /lib/x86_64-linux-gnu/librt-2.13.so 7fb199487000-7fb199686000 ---p 7000 ca:01 3348 /lib/x86_64-linux-gnu/librt-2.13.so 7fb199686000-7fb199687000 r--p 6000 ca:01 3348 /lib/x86_64-linux-gnu/librt-2.13.so 7fb199687000-7fb199688000 rw-p 7000 ca:01 3348
Processed: closing 768369
Processing commands for cont...@bugs.debian.org: close 768369 Bug #768369 [libjpeg62-turbo] libjpeg-turbo: CVE-2014-9092: [DOS] Stack smashing Marked Bug as done thanks Stopping processing here. Please contact me if you need assistance. -- 768369: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=768369 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#771739: could not start nodm with systemd 217-1 or 217-2
Am 02.12.2014 um 06:48 schrieb Martin Pitt: 積丹尼 Dan Jacobson [2014-12-02 13:36 +0800]: # cat /etc/X11/default-display-manager cat: /etc/X11/default-display-manager: No such file or directory Indeed, nodm doesn't use this file at all, nor does it conflict with any other window manager. So installing nodm together with gdm, lightdm, kdm, etc. will just result in a disaster :-( Didier, I'm afraid we have to exclude nodm from your DM masking -- I don't see a way how we can fix this without actually fixing nodm. I'm not sure if the generator is a good idea. I played around with that idea a long time ago but discarded it again. It also changes the behaviour of the insserv generator, which no longer generates dependencies if native units exist. At the current stage, I don't think these patches should be merged as is for master. Didier, Martin: could you elaborate what those patches try to fix? -- 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
Processed: moreinfo
Processing control commands: tags -1 + moreinfo Bug #771685 [lvm2] lvm2: system fails to boot when using lvm2 with upstart Added tag(s) moreinfo. -- 771685: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=771685 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed: moreinfo
Processing control commands: tags -1 + moreinfo Bug #771685 [lvm2] lvm2: system fails to boot when using lvm2 with upstart Ignoring request to alter tags of bug #771685 to the same tags previously set -- 771685: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=771685 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#771685: moreinfo
control: tags -1 + moreinfo Hi, why did you mark this bug as found in the wheezy version of lvm2 if you found this bug on jessie? cheers, Holger signature.asc Description: This is a digitally signed message part.
Bug#771739: could not start nodm with systemd 217-1 or 217-2
Le 02/12/2014 12:28, Michael Biebl a écrit : Am 02.12.2014 um 06:48 schrieb Martin Pitt: 積丹尼 Dan Jacobson [2014-12-02 13:36 +0800]: # cat /etc/X11/default-display-manager cat: /etc/X11/default-display-manager: No such file or directory Indeed, nodm doesn't use this file at all, nor does it conflict with any other window manager. So installing nodm together with gdm, lightdm, kdm, etc. will just result in a disaster :-( Didier, I'm afraid we have to exclude nodm from your DM masking -- I don't see a way how we can fix this without actually fixing nodm. I'm not sure if the generator is a good idea. I played around with that idea a long time ago but discarded it again. It seems the way Lennart advertised the use of a default configuration (like in /e/X/d-d-m) keeping in sync with Aliases like display-manager.service. It also changes the behaviour of the insserv generator, which no longer generates dependencies if native units exist. systemd does that itself as well anyway (I didn't put that on the overriding stack on purpose). I can condition that masking for display-manager only if you feel more comfortable that way. Note that this patch modification is for jessie-only and should be removed as being useless as soon as all dms ship systemd units. At the current stage, I don't think these patches should be merged as is for master. Didier, Martin: could you elaborate what those patches try to fix? This is to fix multiple bug reports where people don't have (or have multiple) dm services starting. Also, it enables people changing manually /e/X/d-d-m to not reboot in a state where no dm is started. The use case is to ensure that display-manager.service will always points to a systemd service that will be runnable (if any). Meaning that we won't have failing units due to ExecStartPre failing and having that shell execution, or disable them if there is an init dm matching. It's going to enable us as well to migrate to Alias=display-manager.service one dm service after another instead in jessie+1 than doing the transition in a batch. Precise behavior in coordination to the 2 generators is: - if /etc/X11/default-display-manager matches a systemd unit and matches display-manager.service: - noop on the systemd side, mask all dms sysvinit not matching a systemd unit - if /etc/X11/default-display-manager matches systemd unit and but doesn't match what's pointed by display-manager.service: - we ensure display-manager.service transiantly points to correct systemd unit, we mask all dms sysvinit not matching a systemd unit - if /etc/X11/default-display-manager matches a non systemd unit: - we transiently mask display-manager.service (so no systemd unit startup) and mask all sysvinit dm scripts, but the one matching /etc/X11/default-display-manager - if no /etc/X11/default-display-manager: - we even don't look at the systemd side (we hope there will be one display-manager.service matching at least one), we mask all sysvinit dm scripts The last case is what is at fault here. I would suggest that we change the patch: - if /etc/X11/default-display-manager matches anything at all or doesn't exist, we avoid masking any sysvinit dm script if there is no display-manager.service matching a real service file. Didier -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#771789: libpcp-pmda-perl: uninstallable on i386: depends on perlapi-5.18.2
Package: libpcp-pmda-perl Version: 3.10.1 Severity: grave This package cannot be installed on i386: # apt-get install -q libpcp-pmda-perl Reading package lists... Building dependency tree... Reading state information... Some packages could not be installed. This may mean that you have requested an impossible situation or if you are using the unstable distribution that some required packages have not yet been created or been moved out of Incoming. The following information may help to resolve the situation: The following packages have unmet dependencies: libpcp-pmda-perl : Depends: perlapi-5.18.2 but it is not installable E: Unable to correct problems, you have held broken packages. -- Jakub Wilk -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#770174: salt-common: service module doesn't work for init scripts
Package: salt-minion Version: 2014.1.13+ds-2 Followup-For: Bug #770174 Dear Maintainer, after fixing service.status (many thanks) service.enabled seems to need also a fix: # salt-call service.enabled shinken [INFO] Executing command 'systemctl is-enabled shinken.service' in directory '/root' [ERROR ] Command 'systemctl is-enabled shinken.service' failed with return code: 1 [ERROR ] output: Failed to get unit file state for shinken.service: No such file or directory local: False As after a reboot shinken is running and this is also told by service shinken status, the above result is wrong and should be True. Thanks, greetins Hermann -- System Information: Debian Release: jessie/sid APT prefers testing-updates APT policy: (500, 'testing-updates'), (500, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 3.16.0-4-amd64 (SMP w/2 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 salt-minion depends on: ii dctrl-tools 2.23 ii init-system-helpers 1.22 ii python-crypto2.6.1-5+b2 ii python-m2crypto 0.21.1-3 ii python-msgpack 0.4.2-1 ii python-zmq 14.4.0-1 pn python:any none ii salt-common 2014.1.13+ds-2 Versions of packages salt-minion recommends: ii debconf-utils 1.5.54 ii dmidecode 2.12-3 Versions of packages salt-minion suggests: pn python-augeas none -- no debconf information -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#770133: stable affected
found 2.1-2
thanks
gcalcli --version
gcalcli v2.1 (Eric Davis)
gcalcli list
Traceback (most recent call last):
File /usr/bin/gcalcli, line 1524, in module
BowChickaWowWow()
File /usr/bin/gcalcli, line 1426, in BowChickaWowWow
borderColor=borderColor)
File /usr/bin/gcalcli, line 345, in __init__
self.allCals = self.gcal.GetAllCalendarsFeed()
File /usr/lib/python2.7/dist-packages/gdata/calendar/service.py,
line 81, in GetAllCalendarsFeed
return self.Get(uri,
converter=gdata.calendar.CalendarListFeedFromString)
File /usr/lib/python2.7/dist-packages/gdata/service.py, line
1107, in Get
'reason': server_response.reason, 'body': result_body}
gdata.service.RequestError: {'status': 403, 'body':
'HTML\nHEAD\nTITLEForbidden/TITLE\n/HEAD\nBODY
BGCOLOR=#FF TEXT=#00\nH1Forbidden/H1\nH2Error
403/H2\n/BODY\n/HTML\n', 'reason': 'Forbidden'}
No LSB modules are available.
Distributor ID: Debian
Description:Debian GNU/Linux 7.7 (wheezy)
Release:7.7
Codename: wheezy
--
Christian Hilgers ch...@familie-hilgers.com
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed: found 770133 in 2.1-2
Processing commands for cont...@bugs.debian.org: found 770133 2.1-2 Bug #770133 [gcalcli] gcalcli 2.x is no longer compatible with google's api Marked as found in versions gcalcli/2.1-2. thanks Stopping processing here. Please contact me if you need assistance. -- 770133: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=770133 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#771739: could not start nodm with systemd 217-1 or 217-2
Am 02.12.2014 um 13:06 schrieb Didier Roche: This is to fix multiple bug reports where people don't have (or have multiple) dm services starting. Can you provide links to such bug reports so we have a bit of a context? -- 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#771792: xul-ext-gcontactsync: gContactSync fails with Please login before trying to sync contacts
Package: xul-ext-gcontactsync Version: 1.0.0-1 Severity: grave Justification: renders package unusable Dear Maintainer, After the recent upgrade to the xul-ext-gnome-keyring package, Icedove appears to be storing the credentials of its account in the GNOME keyring and once the keyring is created and the passwords are stored in it, this gcontactsync add-on throws the error Please login before trying to sync contacts and fails. Version of xul-ext-gnome-keyring: 0.6.11-3 icedove: 31.2.0-1 -- System Information: Debian Release: 8.0 APT prefers unstable APT policy: (500, 'unstable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.16.0-4-amd64 (SMP w/2 CPU cores) Locale: LANG=en_IN.utf8, LC_CTYPE=en_IN.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages xul-ext-gcontactsync depends on: ii icedove 31.2.0-1 xul-ext-gcontactsync recommends no packages. xul-ext-gcontactsync suggests no packages. -- debconf-show failed -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed: Severity fix
Processing commands for cont...@bugs.debian.org: severity 770313 important Bug #770313 [dolibarr] dolibarr: CVE-2014-7137 Severity set to 'important' from 'grave' -- Stopping processing here. Please contact me if you need assistance. -- 770313: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=770313 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#771126: libav/tests/lena.pnm: also not mentioned in debian/copyright
On Fri, Nov 28, 2014 at 1:34 AM, Niels Thykier ni...@thykier.net wrote: Control: tags -1 -wheezy-ignore On 2014-11-27 23:23, Jonas Smedegaard wrote: Quoting Niels Thykier (2014-11-27 22:14:25) [...] In prior similar bugreport https://bugs.debian.org/760171#10 - referenced from https://bugs.debian.org/771191#10 - distribution is documented as permitted only for research and education which I interpret as unacceptable for Debian. [...] - Jonas FTR, this whole business feel incredibly silly. lena.pnm has become the *de-facto* standard image for every CS student to do his graphics courses homework on, and is generally considered to public domain, even without proper documentation. The copyright holder is going to have a very hard time enforcing his right if he wanted to prevent distribution of the image, in particular the low-quality scan that is being used in the Libav source package. Also, even according to https://en.wikipedia.org/wiki/File:Lenna.png#Licensing, the holder is not interested in that to begin with. - I mean, really, don't we have more important things to do? Nevertheless, lena.pnm lacks proper licensing and some argue it violates the DFSG, so I've taken the effort (and ridicule!) to replace lena.pnm upstream with a new image reference.pnm, which I have personally taken this summer and upon Jonas' suggestion provide it under the expat license. This required to update all test reference patterns, which took most of the effort and is basically not verifiable. Jonas, would you mind taking over from here and upload https://libav.org/releases/libav-11.1.tar.xz to unstable? Otherwise I can see if I can get to that this weekend. Regarding stable: I've backported this change back to release/0.8 upstream. In the past, the security team has accepted libav point releases in wheezy-security, and I trust that this is also an acceptable change. It will be part of the next upload to stable-security. (this may take some more weeks, as libav has been notified about a couple of more CVEs, which need to be tested, fixed and verified, which is incredibly laborsome to do correctly). Does this plan work for everyone? -- regards, Reinhard -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#771739: could not start nodm with systemd 217-1 or 217-2
Le 02/12/2014 13:44, Michael Biebl a écrit : Am 02.12.2014 um 13:06 schrieb Didier Roche: This is to fix multiple bug reports where people don't have (or have multiple) dm services starting. Can you provide links to such bug reports so we have a bit of a context? Sure: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=748668 and http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=770404 in particular. Those generators will enable in jessie+1 to implement something like in http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=764607 without needing all DM to transition to this scheme. -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#770941: nova-common - Overrides database config in nova.conf
Control: tags -1 patch Control: reopen 770944 On Tue, Nov 25, 2014 at 12:37:56PM +0100, Bastian Blank wrote: This violates §10.7.3 of the Debian policy: local changes must be preserved. Patch that never resets the connection setting on upgrade. Bastian -- Bastian Blank Berater Telefon: +49 2161 / 4643-194 E-Mail: bastian.bl...@credativ.de credativ GmbH, HRB Mönchengladbach 12080, USt-ID-Nummer: DE204566209 Hohenzollernstr. 133, 41061 Mönchengladbach Geschäftsführung: Dr. Michael Meskes, Jörg Folz, Sascha Heuer diff -Nru nova-2014.1.3/debian/changelog nova-2014.1.3/debian/changelog --- nova-2014.1.3/debian/changelog 2014-11-11 20:52:52.0 + +++ nova-2014.1.3/debian/changelog 2014-12-02 12:20:03.0 + @@ -1,3 +1,9 @@ +nova (2014.1.3-6dbc1) UNRELEASED; urgency=medium + + * Don't reset database config. + + -- Bastian Blank wa...@debian.org Tue, 02 Dec 2014 12:19:45 + + nova (2014.1.3-6) unstable; urgency=high [ Mehdi Abaakouk ] diff -Nru nova-2014.1.3/debian/nova-common.postinst.in nova-2014.1.3/debian/nova-common.postinst.in --- nova-2014.1.3/debian/nova-common.postinst.in2014-11-11 20:52:52.0 + +++ nova-2014.1.3/debian/nova-common.postinst.in2014-12-02 12:27:36.0 + @@ -76,7 +76,9 @@ pkgos_write_new_conf nova logging.conf # Tweak config files depending on debconf answers - pkgos_dbc_postinst /etc/nova/nova.conf database connection nova $@ + if [ -z $2 ] || [ $1 = reconfigure ]; then + pkgos_dbc_postinst /etc/nova/nova.conf database connection nova $@ + fi pkgos_rabbit_write_conf /etc/nova/nova.conf DEFAULT nova manage_nova_api_field manage_nova_my_ip_field
Processed: Re: nova-common - Overrides database config in nova.conf
Processing control commands:
tags -1 patch
Bug #770941 [nova-common] nova-common - Overrides database config in nova.conf
Added tag(s) patch.
reopen 770944
Bug #770944 {Done: Thomas Goirand z...@debian.org} [neutron-common] Overrides
database config in nova.conf
Bug reopened
Ignoring request to alter fixed versions of bug #770944 to the same values
previously set
--
770941: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=770941
770944: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=770944
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#771739: could not start nodm with systemd 217-1 or 217-2
Am 02.12.2014 um 14:17 schrieb Didier Roche: Le 02/12/2014 13:44, Michael Biebl a écrit : Am 02.12.2014 um 13:06 schrieb Didier Roche: This is to fix multiple bug reports where people don't have (or have multiple) dm services starting. Can you provide links to such bug reports so we have a bit of a context? Sure: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=748668 and http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=770404 in particular. Those are bugs in the lxdm and slim packages and need to be fixed there. Trying to workaround that in systemd looks like the wrong approach. Those generators will enable in jessie+1 to implement something like in http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=764607 without needing all DM to transition to this scheme. What exactly do you mean with this scheme? Are you referring to having native .service files ship an Alias=display-manager.service in their [Install] section? -- 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#771739: could not start nodm with systemd 217-1 or 217-2
Le 02/12/2014 14:33, Michael Biebl a écrit : Am 02.12.2014 um 14:17 schrieb Didier Roche: Le 02/12/2014 13:44, Michael Biebl a écrit : Am 02.12.2014 um 13:06 schrieb Didier Roche: This is to fix multiple bug reports where people don't have (or have multiple) dm services starting. Can you provide links to such bug reports so we have a bit of a context? Sure: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=748668 and http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=770404 in particular. Those are bugs in the lxdm and slim packages and need to be fixed there. Trying to workaround that in systemd looks like the wrong approach. Hence my first patch about it, however, bigon asked the release team which nacked doing this for jessie. That's why I'm telling this patch is intended to be a bandaid until we get there. Those generators will enable in jessie+1 to implement something like in http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=764607 without needing all DM to transition to this scheme. What exactly do you mean with this scheme? Are you referring to having native .service files ship an Alias=display-manager.service in their [Install] section? Exactly, as intended upstream and done in other distributions. -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#771685: moreinfo
Hello Sorry I did not properly checked the version that was written in the bug report. It was caused by writing report from computer with debian wheezy. I have tried to create logical volume on instalation done without lvm a then i used one noncritical partition as base for lvm. After change of partition type with fdisk to LVM partition i used pvcreate to initialize i for creating virtual group a then logical volume. The i used mke2fs to create filesystem on created lv volume. Reboot with this configuration had stopped on unknown reason. Debug on kernel command line did not show information to leading to solving this problem. I also tried lvm2.conf file from https://bitbucket.org/CameronNemo/upstart-jobs/src/2090612200fa588412e3fe22aec5ba3747ae88d2/lvm2.conf?at=master, creating script in initramfs-tools with vgchange -ay. Other solution may be that i write jobs for upstart my self, but first i want to know if there is a other solution or bug in packages involved in boot process. I really dont know which component is causing this. Hope this helps in solving this issue. Thank You Have a nice day ewew 2014-12-02 12:51 GMT+01:00 Holger Levsen hol...@layer-acht.org: control: tags -1 + moreinfo Hi, why did you mark this bug as found in the wheezy version of lvm2 if you found this bug on jessie? cheers, Holger
Bug#771794: pip silently removes/updates system provided python packages
Package: python-pip Version: 1.5.6-3 Severity: serious Tags: sid jessie pip currently silently removes/updates system provided python packages when used on the system python. This is only seen when a user calls pip with administrator rights, but it makes debian python packages somehow useless. Upstream is aware of the issue. With distutils and setuptools patched to install into safe locations in the distro, it is unfortunate that the next tool adds such features, and doesn't even warn the user. For jessie I suggest to just disable pip when used on the system python, unless a new option --yes-i-want-to-screw-up-my-system-python is given. -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#771685: moreinfo
control: notfound -1 2.02.95-8 control: found -1 2.02.111-2 control: tags -1 - moreinfo On Dienstag, 2. Dezember 2014, a a wrote: Sorry I did not properly checked the version that was written in the bug report. It was caused by writing report from computer with debian wheezy. I have tried to create logical volume on instalation done without lvm a then i used one noncritical partition as base for lvm. After change of partition type with fdisk to LVM partition i used pvcreate to initialize i for creating virtual group a then logical volume. The i used mke2fs to create filesystem on created lv volume. Reboot with this configuration had stopped on unknown reason. Debug on kernel command line did not show information to leading to solving this problem. I also tried lvm2.conf file from https://bitbucket.org/CameronNemo/upstart-jobs/src/2090612200fa588412e3fe22 aec5ba3747ae88d2/lvm2.conf?at=master, creating script in initramfs-tools with vgchange -ay. Other solution may be that i write jobs for upstart my self, but first i want to know if there is a other solution or bug in packages involved in boot process. I really dont know which component is causing this. Hope this helps in solving this issue. Thank You Have a nice day thanks for the updates! have a nice day too! :) signature.asc Description: This is a digitally signed message part.
Processed: Re: Bug#771685: moreinfo
Processing control commands: notfound -1 2.02.95-8 Bug #771685 [lvm2] lvm2: system fails to boot when using lvm2 with upstart No longer marked as found in versions lvm2/2.02.95-8. found -1 2.02.111-2 Bug #771685 [lvm2] lvm2: system fails to boot when using lvm2 with upstart Marked as found in versions lvm2/2.02.111-2. tags -1 - moreinfo Bug #771685 [lvm2] lvm2: system fails to boot when using lvm2 with upstart Removed tag(s) moreinfo. -- 771685: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=771685 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#771797: liblldb-3.5: does not ship SONAME link /usr/lib/triplet/liblldb.so.1 - liblldb-3.5.so.1
Package: liblldb-3.5 Version: 1:3.5-6 Severity: serious User: debian...@lists.debian.org Usertags: piuparts Hi, during a test with piuparts I noticed your package does not ship the SONAME link for its library (Policy 8.1). That link got created later by ldconfig. The package ships liblldb-3.5.so - liblldb-3.5.so.1 liblldb-3.5.so.1 but the SONAME is liblldb.so.1 Setting the severity to serious since this file was previously shipped by at least one other package (lldb-3.3) but liblldb-3.5 misses appropriate Breaks/Conflicts+Replaces. (#769113) https://packages.debian.org/search?suite=sidarch=anymode=pathsearchon=contentskeywords=liblldb.so.1 The LLVM SONAMES look quite messy, but this seems to be resolved finally in 3.6 which changes the SONAME to liblldb-3.6.so. In this context it is even more important to ship that link and have appropriate Conflicts. From the attached log (scroll to the bottom...): 0m48.2s DEBUG: Starting command: ['chroot', '/tmp/piupartss/tmpkOV8jD', 'tmp/scripts/pre_remove_40_find_unowned_lib_links'] 0m51.6s DUMP: UNOWNED SYMLINK /usr/lib/x86_64-linux-gnu/liblldb.so.1 - liblldb-3.5.so.1 0m51.6s DEBUG: Command ok: ['chroot', '/tmp/piupartss/tmpkOV8jD', 'tmp/scripts/pre_remove_40_find_unowned_lib_links'] cheers, Andreas liblldb-3.5_1:3.5-6.log.gz Description: application/gzip
Bug#771794: [Python-modules-team] Bug#771794: pip silently removes/updates system provided python packages
Quoting Matthias Klose d...@debian.org: For jessie I suggest to just disable pip when used on the system python, unless a new option --yes-i-want-to-screw-up-my-system-python is given. How about disabling pip for uid 0 altogether? -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#770425: Fixes for debian stable ?
Hi, The upstream release was on Nov 20, it's been almost 2 weeks and the bug seem kind of serious. Any chance to do a quick fix and then continue to discuss changing wordpress version in stable ? Or any ETA on when the fixes will come to stable ? I've manually applied the workaround suggested here[1], although it doesn't seem ideal. But seems to fix the attacks reported here[2] and here[3] at least. Thanks a lot, Rodrigo [1]: http://klikki.fi/adv/wordpress.html [2]: http://klikki.fi/unquote/ [3]: http://klikki.fi/adv/wordpress_update.html -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#771126: libav/tests/lena.pnm: also not mentioned in debian/copyright
Quoting Reinhard Tartler (2014-12-02 14:11:19) On 2014-11-27 23:23, Jonas Smedegaard wrote: In prior similar bugreport https://bugs.debian.org/760171#10 - referenced from https://bugs.debian.org/771191#10 - distribution is documented as permitted only for research and education which I interpret as unacceptable for Debian. FTR, this whole business feel incredibly silly. Welcome to the Real World: Some stuff is incredibly stupid, yet Real. lena.pnm has become the *de-facto* standard image for every CS student to do his graphics courses homework on, Proprietary operating systems, word processors and spreadsheet editors have become the *de-facto* standard e.g. for most public servants in the World. Incredibly silly as free (and technically superior) alternatives exist. But this bugreport is about DFSG... The copyright holder is going to have a very hard time enforcing his right if he wanted to prevent distribution of the image, DFSG is is about Debian respecting copyright and licensing (no matter if difficult for copyright holders to defend or enforce their rights). (perhaps you confuse copyright and licensing with trademarks or patents, in some cases considered irrelevant for Debian to care about) Jonas, would you mind taking over from here and upload https://libav.org/releases/libav-11.1.tar.xz to unstable? I don't mind doing the technical work of packaging, but prefer if someone else takes to dialogue with release team about freeze exception, as I don't have the stomach for that (no blame on the release team for that!). I also don't mind doing the additional technical work of cherry-picking only the fix for this bug and apply to 6:11-2 currently targeted Jessie. Which of those to do would probably need input from the person willing to do the negotiation with release team, however. So I await someone volunteering for that (and while waiting will prepare that new upstream release, and if noone have appeared before done release it targeted experimental). - Jonas -- * Jonas Smedegaard - idealist Internet-arkitekt * Tlf.: +45 40843136 Website: http://dr.jones.dk/ [x] quote me freely [ ] ask before reusing [ ] keep private signature.asc Description: signature
Bug#771800: designate-central: fails to purge: ucfr: Association belongs to designate-common, not cinder-common
Package: designate-central Version: 2014.1-12 Severity: serious User: debian...@lists.debian.org Usertags: piuparts Hi, during a test with piuparts I noticed your package failed to purge. From the attached log (scroll to the bottom...): Removing designate-common (2014.1-12) ... Purging configuration files for designate-common (2014.1-12) ... ucfr: Association belongs to designate-common, not cinder-common ucfr: Aborting dpkg: error processing package designate-common (--purge): subprocess installed post-removal script returned error exit status 5 Errors were encountered while processing: designate-common Setting the severity to serious since that cannot be worked around (like having ucf installed at purge time which obviously is the case here). cheers, Andreas designate-central_2014.1-12.log.gz Description: application/gzip
Bug#768998: marked as done (kadu-mime-tex: FTBFS on all arches)
Your message dated Tue, 2 Dec 2014 15:32:32 +0100 with message-id b2d079f5-c445-49cc-a017-1c01434e5...@prezu.one.pl and subject line Closing bug has caused the Debian Bug report #768998, regarding kadu-mime-tex: FTBFS on all arches to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 768998: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=768998 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Source: kadu-mime-tex Version: 1.0-2 Severity: serious Justification: FTBFS *** /home/zumbi/bin/ftbfs-armel Hello, Your package fails to build from source on Debian autobuilder network. Please check your package build logs at: https://buildd.debian.org/status/package.php?p=kadu-mime-texsuite=sid Best regards -- System Information: Debian Release: jessie/sid APT prefers unstable APT policy: (900, 'unstable') Architecture: i386 (i686) Kernel: Linux 3.14-2-686-pae (SMP w/4 CPU cores) Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash ---End Message--- ---BeginMessage--- Version: 1.0-2 This bug was caused by #767010, which has been dealt with recently. --- Patryk Cisek---End Message---
Bug#771797: liblldb-3.5: does not ship SONAME link /usr/lib/triplet/liblldb.so.1 - liblldb-3.5.so.1
On 02/12/2014 06:13, Andreas Beckmann wrote: Package: liblldb-3.5 Version: 1:3.5-6 Severity: serious User: debian...@lists.debian.org Usertags: piuparts Hi, during a test with piuparts I noticed your package does not ship the SONAME link for its library (Policy 8.1). That link got created later by ldconfig. The package ships liblldb-3.5.so - liblldb-3.5.so.1 liblldb-3.5.so.1 but the SONAME is liblldb.so.1 Setting the severity to serious since this file was previously shipped by at least one other package (lldb-3.3) but liblldb-3.5 misses appropriate Breaks/Conflicts+Replaces. (#769113) Not sure I understand the severity. This is a different package from lldb-3.3. Thanks Sylvestre -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed: Re: Bug#771749: cyrus-{common, imapd}-2.4: unhandled symlink to directory conversion: /usr/share/doc/PACKAGE
Processing control commands:
tags -1 +help
Bug #771749 [cyrus-imapd-2.4,cyrus-common-2.4] cyrus-{common, imapd}-2.4:
unhandled symlink to directory conversion: /usr/share/doc/PACKAGE
Added tag(s) help.
--
771749: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=771749
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#771749: cyrus-{common, imapd}-2.4: unhandled symlink to directory conversion: /usr/share/doc/PACKAGE
Control: tags -1 +help Hi Andreas, I am out of clues how to fix that in a general manner. I guess I just can't support upgrades from testing versions and from wheezy versions at the same time. I will just aim to have the upgrades from wheezy right and fix the most of jessie-to-jessie upgrades. And I just regret of ever using --link-doc more and more. Would you be able to test upgrades from wheezy to unstable with -10 quickly? O. On Tue, Dec 2, 2014, at 02:58, Andreas Beckmann wrote: Package: cyrus-imapd-2.4,cyrus-common-2.4 Version: 2.4.17+caldav~beta10-8 Severity: serious User: debian...@lists.debian.org Usertags: piuparts Hi, an upgrade test with piuparts revealed that your package installs files over existing symlinks and possibly overwrites files owned by other packages. This usually means an old version of the package shipped a symlink but that was later replaced by a real (and non-empty) directory. This kind of overwriting another package's files cannot be detected by dpkg. This was observed on the following upgrade paths: wheezy - jessie (2.4.17+caldav~beta10-8) wheezy - sid (2.4.17+caldav~beta10-9) For /usr/share/doc/PACKAGE this may not be problematic as long as both packages are installed, ship byte-for-byte identical files and are upgraded in lockstep. But once one of the involved packages gets removed, the other one will lose its documentation files, too, including the copyright file, which is a violation of Policy 12.5: https://www.debian.org/doc/debian-policy/ch-docs.html#s-copyrightfile For other overwritten locations anything interesting may happen. Note that dpkg intentionally does not replace directories with symlinks and vice versa, you need the maintainer scripts to do this. See in particular the end of point 4 in https://www.debian.org/doc/debian-policy/ch-maintainerscripts.html#s-unpackphase It is recommended to use the dpkg-maintscript-helper commands 'dir_to_symlink' and 'symlink_to_dir' (available since dpkg 1.17.2) to perform the conversion, ideally using d/$PACKAGE.mainstscript. See dpkg-maintscript-helper(1) and dh_installdeb(1) for details. From the attached log (usually somewhere in the middle...): 4m16.8s ERROR: FAIL: silently overwrites files via directory symlinks: /usr/share/doc/cyrus-common-2.4/changelog.Debian.gz (cyrus-common-2.4) != /usr/share/doc/cyrus-common/changelog.Debian.gz (cyrus-common) /usr/share/doc/cyrus-common-2.4/copyright (cyrus-common-2.4) != /usr/share/doc/cyrus-common/copyright (cyrus-common) /usr/share/doc/cyrus-imapd-2.4/copyright (cyrus-imapd-2.4) != /usr/share/doc/cyrus-common/copyright (cyrus-common) There may be more packages failing, but these cannot be tested by piuparts due to cyrus-common-2.4 already failing ... cheers, Andreas ___ Pkg-Cyrus-imapd-Debian-devel mailing list pkg-cyrus-imapd-debian-de...@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-cyrus-imapd-debian-devel Email had 1 attachment: + cyrus-imapd-2.4_2.4.17+caldav~beta10-8.log.gz 42k (application/gzip) -- Ondřej Surý ond...@sury.org Knot DNS (https://www.knot-dns.cz/) – a high-performance DNS server -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#719943: marked as done (makedumpfile: fails to dump kernel log, continually appends the line [ 0.000000] to dmesg file)
Your message dated Tue, 02 Dec 2014 15:19:40 + with message-id e1xvpeq-kl...@franck.debian.org and subject line Bug#719943: fixed in makedumpfile 1:1.5.3-2 has caused the Debian Bug report #719943, regarding makedumpfile: fails to dump kernel log, continually appends the line [0.00] to dmesg file to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 719943: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=719943 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: makedumpfile Version: 1.5.4-1 Severity: grave Justification: renders package unusable Dear Maintainer, There seems to be a serious issue with makedumpfile that causes it to fail to dump the kernel log when collecting crash dump information. Instead, the program continues to run indefinitely, continually appending the line [ 0.00] to the file as it seems to attempt to dump the log, which, if left alone for any considerable length of time, can rapidly result in a very large, entirely useless dmesg dump file. I have been trying to collect crash dump information for a crash that's triggered whenever Folding@Home's FahCore_a4 attempts to resume an in-progress work unit, however, every crash dump I've collected has had this problem. The main dump file seems to be dumped without a problem (though crash identifies it as a partial dump, possibly due to the kernel log being dumped into a separate file). I hope you can look into this issue and hopefully it can be sorted out soon. -- System Information: Debian Release: jessie/sid APT prefers experimental APT policy: (650, 'experimental'), (650, 'unstable'), (600, 'testing'), (500, 'saucy-updates'), (500, 'saucy-security'), (500, 'saucy') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.11-rc4-amd64 (SMP w/2 CPU cores) Locale: LANG=en_CA.utf8, LC_CTYPE=en_CA.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages makedumpfile depends on: ii libbz2-1.0 1.0.6-5 ii libc6 2.17-92 ii libdw1 0.156-1 ii libelf1 0.156-1 ii perl5.14.2-21 ii zlib1g 1:1.2.8.dfsg-1 Versions of packages makedumpfile recommends: ii crash7.0.1-3 ii kexec-tools 1:2.0.3-4 makedumpfile suggests no packages. -- no debconf information ---End Message--- ---BeginMessage--- Source: makedumpfile Source-Version: 1:1.5.3-2 We believe that the bug you reported is fixed in the latest version of makedumpfile, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 719...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Louis Bouchard louis.bouch...@ubuntu.com (supplier of updated makedumpfile package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Mon, 02 Dec 2014 15:17:43 +0100 Source: makedumpfile Binary: makedumpfile kdump-tools Architecture: source amd64 all Version: 1:1.5.3-2 Distribution: unstable Urgency: medium Maintainer: John Wright j...@debian.org Changed-By: Louis Bouchard louis.bouch...@ubuntu.com Description: kdump-tools - scripts and tools for automating kdump (Linux crash dumps) makedumpfile - VMcore extraction tool Closes: 719943 771210 Changes: makedumpfile (1:1.5.3-2) unstable; urgency=medium . * Adapt to kernel 3.16 changes in symbols : - Work around removal of struct vmlist in kernel 3.16 - Fix dump_dmesg accordingly - Backported commits are : 759b78c, cee64e3, 8145e41, e203095, 150b58eb, 846ab2e, 1202589, 8a0236c, 9d38132, e24dc53 Closes: #719943 * Implement systemd service and correct mechanism to capture kernel dumps under systemd control Closes: #771210 Checksums-Sha1: 1d1e08dfdcd89eedf75e92f55c1c8bb83fa181c3 2075 makedumpfile_1.5.3-2.dsc 1480ffa900407f15c006ac9eecc8a4201c33d489 18196 makedumpfile_1.5.3-2.debian.tar.xz 541c4d2fc385ddf917629b625f9f89c89c06b25c 120874 makedumpfile_1.5.3-2_amd64.deb 23bcfc8aa8bc3ffcc6336ffa70465f5e69d7da2b 18192 kdump-tools_1.5.3-2_all.deb Checksums-Sha256: 842e60fc9b47ee39bb32ad60d1a50b18a6d94f16a762f038ca53dd68c1c72d2b 2075 makedumpfile_1.5.3-2.dsc dbec4ded6a209b7beadb832266851de4f3380faa0505cc4995c7cdb7ce0b9942 18196
Bug#771749: cyrus-{common, imapd}-2.4: unhandled symlink to directory conversion: /usr/share/doc/PACKAGE
On 2014-12-02 16:05, Ondřej Surý wrote: I am out of clues how to fix that in a general manner. I guess I just can't support upgrades from testing versions and from wheezy versions at the same time. That should not be impossible ... At least for one of the packages (IIRC -imapd-2.4) I had checked and there were no dpkg-maint-script-helper calls ... so that wasn't an erroneus use. There must have been some added to other packages for the missing copyright files ... I will just aim to have the upgrades from wheezy right and fix the most of jessie-to-jessie upgrades. And I just regret of ever using --link-doc more and more. When did you start and stop using it? And on which packages? Would you be able to test upgrades from wheezy to unstable with -10 quickly? If you put the .debs (amd64) together with a Packages file somewhere I can start my piuparts engine on it :-) (I can test upgrades from any release in the archive to any other release but using the new packages instead. Release includes testing, sid, ...) Andreas -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#769236: marked as done (android-platform-frameworks-base: FTBFS in jessie/i386: libutils.so: undefined reference to `android_atomic_or')
Your message dated Tue, 02 Dec 2014 15:19:28 + with message-id e1xvpee-gb...@franck.debian.org and subject line Bug#769236: fixed in android-platform-frameworks-base 21-2 has caused the Debian Bug report #769236, regarding android-platform-frameworks-base: FTBFS in jessie/i386: libutils.so: undefined reference to `android_atomic_or' to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 769236: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=769236 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Source: android-platform-frameworks-base Version: 21-1 Severity: serious Tags: jessie sid User: debian...@lists.debian.org Usertags: qa-ftbfs-20141112 qa-ftbfs Justification: FTBFS in jessie on i386 Hi, During a rebuild of all packages in jessie (in a jessie chroot, not a sid chroot), your package failed to build on i386. Relevant part (hopefully): g++ -fPIC -Wl,-rpath=/usr/lib/android -Wl,-z,relro -o aapt AaptAssets.o Command.o CrunchCache.o FileFinder.o Main.o Package.o StringPool.o XMLNode.o ResourceFilter.o ResourceTable.o Images.o Resource.o SourcePos.o ZipEntry.o ZipFile.o -lrt -ldl -lpthread -lz -lexpat -lpng -L/usr/lib/android -lcutils -lhost -llog -lutils -L../../libs/androidfw -landroidfw /usr/lib/android/libutils.so: undefined reference to `android_atomic_or' /usr/lib/android/libutils.so: undefined reference to `android_atomic_dec' /usr/lib/android/libutils.so: undefined reference to `android_atomic_inc' /usr/lib/android/libutils.so: undefined reference to `android_atomic_release_cas' /usr/lib/android/libutils.so: undefined reference to `android_atomic_add' collect2: error: ld returned 1 exit status The full build log is available from: http://aws-logs.debian.net/ftbfs-logs/2014/11/12/android-platform-frameworks-base_21-1_jessie-i386.log A list of current common problems and possible solutions is available at http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute! About the archive rebuild: The rebuild was done on EC2 VM instances from Amazon Web Services, using a clean, minimal and up-to-date chroot. Every failed build was retried once to eliminate random failures. ---End Message--- ---BeginMessage--- Source: android-platform-frameworks-base Source-Version: 21-2 We believe that the bug you reported is fixed in the latest version of android-platform-frameworks-base, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 769...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Hans-Christoph Steiner h...@eds.org (supplier of updated android-platform-frameworks-base package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Tue, 02 Dec 2014 14:36:42 +0100 Source: android-platform-frameworks-base Binary: android-libandroidfw android-libandroidfw-dev aapt Architecture: source amd64 Version: 21-2 Distribution: unstable Urgency: low Maintainer: Android tools Maintainer android-tools-de...@lists.alioth.debian.org Changed-By: Hans-Christoph Steiner h...@eds.org Description: aapt - Android Asset Packaging Tool android-libandroidfw - Android utility library android-libandroidfw-dev - Android utility library - Development files Closes: 768821 769236 Changes: android-platform-frameworks-base (21-2) unstable; urgency=low . * add versions to shlibs so dh can do dep detection (Closes: #768821) (Closes: #769236) * set Android Tools team as Maintainer * fix installation of aapt bash completion rules Checksums-Sha1: 9c36fa08f34d49b7de3c95fd5478063adafda958 2563 android-platform-frameworks-base_21-2.dsc 07669d92e0e4334a95cb6f4a0b60ea61be33d1e7 12924 android-platform-frameworks-base_21-2.debian.tar.xz 73180d1e66d24909db2eee6dacebdf776a424707 112644 android-libandroidfw_21-2_amd64.deb e4732527500b202c377a727f9d6d7d5fe2d4f31d 158378 android-libandroidfw-dev_21-2_amd64.deb c97d82c0f882351b0a1930dd0d4c5ccf98fec9bf 256488 aapt_21-2_amd64.deb Checksums-Sha256: 45c59f33cc66dd586dad3ca14a7da79dc9c91e4740af6ecb944a1fbdc2973faf 2563 android-platform-frameworks-base_21-2.dsc ecbe456d5c3e18a15bfee0cc9900bbb18b317890b76b8469224df8b1b21fee7c 12924
Bug#769534: marked as done (phabricator: fails to install: Usage Exception: Specify a value to set the key 'mysql.user' to.)
Your message dated Tue, 02 Dec 2014 15:20:13 + with message-id e1xvpfn-so...@franck.debian.org and subject line Bug#769534: fixed in phabricator 0~git20141130-1 has caused the Debian Bug report #769534, regarding phabricator: fails to install: Usage Exception: Specify a value to set the key 'mysql.user' to. to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 769534: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=769534 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: phabricator Version: 0~git20141101-1 Severity: serious User: debian...@lists.debian.org Usertags: piuparts Hi, during a test with piuparts I noticed your package failed to install. As per definition of the release team this makes the package too buggy for a release, thus the severity. From the attached log (scroll to the bottom...): Selecting previously unselected package phabricator. (Reading database ... 12507 files and directories currently installed.) Preparing to unpack .../phabricator_0~git20141101-1_all.deb ... Unpacking phabricator (0~git20141101-1) ... Setting up phabricator (0~git20141101-1) ... Creating config file /etc/apache2/conf-available/phabricator.conf with new version Creating config file /etc/lighttpd/conf-available/20-phabricator.conf with new version Creating config file /etc/nginx/sites-available/phabricator.conf with new version adduser: Warning: The home directory `/var/lib/phabricator' does not belong to the user you are currently creating. Set 'mysql.host' in local configuration. Usage Exception: Specify a value to set the key 'mysql.user' to. dpkg: error processing package phabricator (--configure): subprocess installed post-installation script returned error exit status 77 Errors were encountered while processing: phabricator cheers, Andreas phabricator_0~git20141101-1.log.gz Description: application/gzip ---End Message--- ---BeginMessage--- Source: phabricator Source-Version: 0~git20141130-1 We believe that the bug you reported is fixed in the latest version of phabricator, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 769...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Richard Sellam richard.sel...@orvidia.fr (supplier of updated phabricator package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Sun, 30 Nov 2014 23:52:12 +0100 Source: phabricator Binary: libphutil arcanist phabricator Architecture: source all Version: 0~git20141130-1 Distribution: unstable Urgency: medium Maintainer: Richard Sellam richard.sel...@orvidia.fr Changed-By: Richard Sellam richard.sel...@orvidia.fr Description: arcanist - Command line interface for Phabricator (review platform) libphutil - Shared library for Arcanist and Phabricator phabricator - Software engineering platform Closes: 768201 768965 769534 769615 771597 Changes: phabricator (0~git20141130-1) unstable; urgency=medium . * New upstream version * avoid mysql configuration in postinst if no credential provided (closes: #769534) * added portuguese to debconf translations (closes: #769615) * added german to debconf translations (closes: #768965) * added logrotate on phd log files * fixed po-debconf messages inconsistencies (closes: #768201) * added dutch to debconf translations (closes: #771597) Checksums-Sha1: a9692c72672e6f501af81e494f3abcf1571228bc 2645 phabricator_0~git20141130-1.dsc 36aecca928b380865c7bbf016e27d4f6fcce8241 378268 phabricator_0~git20141130.orig-arcanist.tar.xz 968d636995020137f67ecdfedcf53bec4c101eec 520044 phabricator_0~git20141130.orig-libphutil.tar.xz 19aa7f64f5dd020551cc882aa30d8047e8a72b03 3930424 phabricator_0~git20141130.orig.tar.xz a182a63a9acb397a786341e172c388646ff5c445 25276 phabricator_0~git20141130-1.debian.tar.xz ae7358f95cd80bbf0238817a75f1d66ae83d754a 543188 libphutil_0~git20141130-1_all.deb 2791f497926eb62fc75f338b1959ad3bfb44da5e 402582 arcanist_0~git20141130-1_all.deb dbcf6e61c710cba948a984ab6f3334051f5f37b7 4084012 phabricator_0~git20141130-1_all.deb Checksums-Sha256:
Bug#771210: marked as done (kdump-tools fails to complete when run with systemd)
Your message dated Tue, 02 Dec 2014 15:19:40 + with message-id e1xvpeq-kr...@franck.debian.org and subject line Bug#771210: fixed in makedumpfile 1:1.5.3-2 has caused the Debian Bug report #771210, regarding kdump-tools fails to complete when run with systemd to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 771210: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=771210 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: kdump-tools Version: 1.5.3-1 Severity: normal Dear Maintainer, When used in the current version of Jessie, the kdump-tools sysVinit script fails to complete correctly. kdump-tools should be converted to systemd to avoid this situation. It also triggers bug #719943, since the version in testing remained at 1.5.3. -- System Information: Debian Release: jessie/sid APT prefers testing-updates APT policy: (500, 'testing-updates'), (500, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 3.16-2-amd64 (SMP w/2 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages kdump-tools depends on: ii kexec-tools 1:2.0.7-3 ii makedumpfile 1.5.3-1 kdump-tools recommends no packages. kdump-tools suggests no packages. -- Configuration Files: /etc/default/kdump-tools changed [not included] /etc/init.d/kdump-tools [Errno 2] No such file or directory: u'/etc/init.d/kdump-tools' -- no debconf information ---End Message--- ---BeginMessage--- Source: makedumpfile Source-Version: 1:1.5.3-2 We believe that the bug you reported is fixed in the latest version of makedumpfile, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 771...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Louis Bouchard louis.bouch...@ubuntu.com (supplier of updated makedumpfile package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Mon, 02 Dec 2014 15:17:43 +0100 Source: makedumpfile Binary: makedumpfile kdump-tools Architecture: source amd64 all Version: 1:1.5.3-2 Distribution: unstable Urgency: medium Maintainer: John Wright j...@debian.org Changed-By: Louis Bouchard louis.bouch...@ubuntu.com Description: kdump-tools - scripts and tools for automating kdump (Linux crash dumps) makedumpfile - VMcore extraction tool Closes: 719943 771210 Changes: makedumpfile (1:1.5.3-2) unstable; urgency=medium . * Adapt to kernel 3.16 changes in symbols : - Work around removal of struct vmlist in kernel 3.16 - Fix dump_dmesg accordingly - Backported commits are : 759b78c, cee64e3, 8145e41, e203095, 150b58eb, 846ab2e, 1202589, 8a0236c, 9d38132, e24dc53 Closes: #719943 * Implement systemd service and correct mechanism to capture kernel dumps under systemd control Closes: #771210 Checksums-Sha1: 1d1e08dfdcd89eedf75e92f55c1c8bb83fa181c3 2075 makedumpfile_1.5.3-2.dsc 1480ffa900407f15c006ac9eecc8a4201c33d489 18196 makedumpfile_1.5.3-2.debian.tar.xz 541c4d2fc385ddf917629b625f9f89c89c06b25c 120874 makedumpfile_1.5.3-2_amd64.deb 23bcfc8aa8bc3ffcc6336ffa70465f5e69d7da2b 18192 kdump-tools_1.5.3-2_all.deb Checksums-Sha256: 842e60fc9b47ee39bb32ad60d1a50b18a6d94f16a762f038ca53dd68c1c72d2b 2075 makedumpfile_1.5.3-2.dsc dbec4ded6a209b7beadb832266851de4f3380faa0505cc4995c7cdb7ce0b9942 18196 makedumpfile_1.5.3-2.debian.tar.xz 6d4fc9deea6c0818ab690d9424d0a87b17e92ff24dd171d34d6beda853a60902 120874 makedumpfile_1.5.3-2_amd64.deb d8ed7129a9fcb1e37ebbc6d4e36641916f03d2978f7ebd99f577526bba45403e 18192 kdump-tools_1.5.3-2_all.deb Files: 04c93bd6fa96e26c326dfe58d7572174 2075 devel optional makedumpfile_1.5.3-2.dsc 736178e15705c93c211aafac01fa8cc8 18196 devel optional makedumpfile_1.5.3-2.debian.tar.xz e8fc0ea439638f5b23cad4d38faf2c0a 120874 devel optional makedumpfile_1.5.3-2_amd64.deb 83eed36d3c1d726903550ffc84de6a80 18192 devel optional kdump-tools_1.5.3-2_all.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1 iQIcBAEBCAAGBQJUfczzAAoJEIs9hnyCPnphmi0QAJ6WF34n4O4q1cYhjIA8TIVF 82XpLjQt7PqphbLPYWNASKfTfAdcwBvuOdO8TlFJfsXWv+KYRKrDevPmHCcBHw/F aYEwziBuMQ15MuhgG+q5lmReZNK1NkiPKBYRxBPxUQDzeT+Apmh5Nm/3roULf6W5
Bug#771809: missing /usr/lib/python* code renders package unusable
Package: heat-cfntools Version: 1.2.7-1 Severity: grave We should do: echo /usr/lib/python* debian/heat-cfntools.install, otherwise, the command line tools don't work. I'm uploading a fix soon. Thomas Goirand (zigo) -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed: Re: [Pkg-mozext-maintainers] Bug#771792: xul-ext-gcontactsync: gContactSync fails with Please login before trying to sync contacts
Processing commands for cont...@bugs.debian.org: severity 771792 important Bug #771792 [xul-ext-gcontactsync] xul-ext-gcontactsync: gContactSync fails with Please login before trying to sync contacts Severity set to 'important' from 'grave' thanks Stopping processing here. Please contact me if you need assistance. -- 771792: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=771792 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#771792: [Pkg-mozext-maintainers] Bug#771792: xul-ext-gcontactsync: gContactSync fails with Please login before trying to sync contacts
severity 771792 important thanks On Tue, Dec 02, 2014 at 06:25:17PM +0530, L. Guruprasad wrote: Severity: grave Justification: renders package unusable ... xul-ext-gnome-keyring: 0.6.11-3 icedove: 31.2.0-1 As you're saying yourself the problem appears only when another add-on is installed, that means the package is not unusable by itself and thus the bug is not grave. And yes, there are people like myself who do not use xul-ext-gnome-keyring together with xul-ext-gcontactsync. Michael -- Michael Meskes Michael at Fam-Meskes dot De, Michael at Meskes dot (De|Com|Net|Org) Michael at BorussiaFan dot De, Meskes at (Debian|Postgresql) dot Org Jabber: michael.meskes at gmail dot com VfL Borussia! Força Barça! Go SF 49ers! Use Debian GNU/Linux, PostgreSQL -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed: tagging 771739
Processing commands for cont...@bugs.debian.org: tags 771739 + pending Bug #771739 [systemd] could not start nodm with systemd 217-1 or 217-2 Added tag(s) pending. thanks Stopping processing here. Please contact me if you need assistance. -- 771739: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=771739 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#771809: marked as done (missing /usr/lib/python* code renders package unusable)
Your message dated Tue, 02 Dec 2014 16:03:53 + with message-id e1xvpvd-0005tu...@franck.debian.org and subject line Bug#771809: fixed in heat-cfntools 1.2.7-2 has caused the Debian Bug report #771809, regarding missing /usr/lib/python* code renders package unusable to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 771809: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=771809 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: heat-cfntools Version: 1.2.7-1 Severity: grave We should do: echo /usr/lib/python* debian/heat-cfntools.install, otherwise, the command line tools don't work. I'm uploading a fix soon. Thomas Goirand (zigo) ---End Message--- ---BeginMessage--- Source: heat-cfntools Source-Version: 1.2.7-2 We believe that the bug you reported is fixed in the latest version of heat-cfntools, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 771...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Thomas Goirand z...@debian.org (supplier of updated heat-cfntools package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Tue, 02 Dec 2014 23:41:46 +0800 Source: heat-cfntools Binary: heat-cfntools Architecture: source all Version: 1.2.7-2 Distribution: unstable Urgency: medium Maintainer: PKG OpenStack openstack-de...@lists.alioth.debian.org Changed-By: Thomas Goirand z...@debian.org Description: heat-cfntools - Tools required to be installed on Heat provisioned cloud Closes: 771809 Changes: heat-cfntools (1.2.7-2) unstable; urgency=medium . * Added missing /usr/lib/python* in the package (Closes: #771809). Checksums-Sha1: 392702bd482f96c87a33190703a42eb459751072 2309 heat-cfntools_1.2.7-2.dsc 4b52fc60b32d2462bad0899bfa184655cc8d4aa1 55300 heat-cfntools_1.2.7-2.debian.tar.xz 32a06aeb16bba5b58001588e10c863248746a088 89966 heat-cfntools_1.2.7-2_all.deb Checksums-Sha256: e5d7373cb607e9fe18b46d504ca7f9de16cbe9ce9e25bf283865909ac948258c 2309 heat-cfntools_1.2.7-2.dsc b7ab9ad1b4868cc843988d0eafeda459c63ca42ee969c187b02e531b2e399a8d 55300 heat-cfntools_1.2.7-2.debian.tar.xz 76e958677a4c4028709ceeb09947823f0f47c045bf7523e4a095f8d544c3 89966 heat-cfntools_1.2.7-2_all.deb Files: 2f25693600900d4a8688104368e77407 2309 python optional heat-cfntools_1.2.7-2.dsc b3b52acc1e6238716f1810650d44bdf9 55300 python optional heat-cfntools_1.2.7-2.debian.tar.xz 68b1cf04f86e926510022d8eb8891085 89966 python optional heat-cfntools_1.2.7-2_all.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1 iQIcBAEBCAAGBQJUfeGHAAoJENQWrRWsa0P+jIoP/38gEXGdT7vgwyAceACMOVfq 9YSIXANAUh4z6pLlXo4h5rVZRSOw20RPjvcevq6eESS9BK+Q9Ed2nLddSDXjjnfo 0ffDB1JAsW9GsiEh9xG6CqNex0Q0zaxyOwRlWfAIOQP7xBZVgt7s6Ln0+HBGfzoo iM+QNiQvqcK6duCOJKD5UO7OAgknbeuUMKCJHHTslk0GNYP5YKcQLCvacYN62vE0 Oy8mowsKlmWz8dyck5HLK4JUIZEwYJbuW/7m9Lo26J6EnFHPtHwlAMs1n4FYKNqB 5XAUC4Oqhb/K5GLXp9unhOxEZ3HgswgCCBk741od+6XHSTTvor259rz61eMikx5Y SvzmVCSEDd0513iBvKZzF5bNBtNyXbkhhHjLi7P9yjlAcJMmtWOU3zdjiiYgnboI 2mDM0rsJ0JQF7nqsX6Bh9cbRnNVWemBBLKOLw8zy0dqixPpYlRNrPq1GuBHUt9fi kTl+Cev4JITJjdPXp+WUm+jvyvlC73Kuim6Bm+JLS1vpF0Q68hUIW/fArmH3JMGj Lxq7PcW1m3oic/mUNVrQG3wxYVGJ371gJS6YLqvWd66zWyjuF/8GySoS/36NPywV B0QGs5GtQnI/5a6BgH5PdqzHnLt2sYeRwAozi6r33hQpXH953CaAjT9FdCYgSmpo s/GKE86mGHglXo7/Bh4M =Nit2 -END PGP SIGNATUREEnd Message---
Bug#771739: could not start nodm with systemd 217-1 or 217-2
Michael Biebl [2014-12-02 14:33 +0100]: Those are bugs in the lxdm and slim packages and need to be fixed there. That'd be my preference too, TBH, but it was already n'acked by the RT. Maybe we can reopen this, though. Trying to workaround that in systemd looks like the wrong approach. The whole configure your default DM has become horribly complicated in Debian :-( sysvinit and systemd both have their own ways of enabling/disabling services, and on top of that we still have this /etc/X11/default-display-manager thing which potentially collides/disagrees with those, so I don't think there ever is a way to get this right. But with the current situation of having to support multiple inits and multiple DMs, I think that /etc/X11/default-display-manager should be the configuration which trumps systemctl enable/update-rc.d disable/enable, and thus we need some central place to tell how to translate that file to a particular boot sequence. So while the DM packages certainly should be fixed to get a proper unit, that still wouldn't completely fix the problems here -- we still need something to sync /e/X/d-d-m with the init system specific enabling/disabling. So the idea of that generator isn't too bad or only a workaround IMHO. However, it's been shown to be quite complex, so before we land this in jessie I'd like to give it some more maturing in experimental. If it turns out to cause more damage than good, we can rip it out again and say *sigh* don't do that then, if people try to be too clever with configuring their DMs.. But Michael, I don't want to go over your head here. If you don't like this at all, then let's stop this right away instead of risking more debugging/work on this? Thanks, Martin -- Martin Pitt| http://www.piware.de Ubuntu Developer (www.ubuntu.com) | Debian Developer (www.debian.org) signature.asc Description: Digital signature
Bug#771573: marked as done (cups: Millions of symlinks to .ppd file created in /tmp)
Your message dated Tue, 02 Dec 2014 17:11:12 +0100 with message-id 3610219.L0Lm9WivlB@gyllingar and subject line Re: Bug#771573: cups: Millions of symlinks to .ppd file created in /tmp has caused the Debian Bug report #771573, regarding cups: Millions of symlinks to .ppd file created in /tmp to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 771573: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=771573 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: cups Version: 1.7.5-5 Severity: critical Justification: breaks the whole system A few days ago, I was using my laptop at the house of a family member, and needed to print something. I clicked through the add printer dialogs (in Gnome) and the printer was detected, added, and my document printed just fine. [And let me interrupt this bug report to congratulate everyone involved. This operation used to be quite painful in the past---it's great that it can go so smoothly now.] Then, yesterday I noticed that my laptop was acting in an uncharacteristically sluggish way. There was a strange delay of several seconds between launching an application and its window first appearing. It was clear that there wasn't any excessive CPU utilization, so this felf IO related, but it wasn't obvious to me what was going on. Eventually, this morning I decided to see if a reboot would bring my system back to normal. It didn't. Instead, the system failed to boot. I was greeted with a boot message saying: a start job is running for Create Volatile files and directories This message was accompanied by a timer [ 10s / no limit ] and the timer just continued ticking off time. I let it sit for 2 or 3 minutes before giving up and deciding it was never going to boot. I duckduckgo'ed the message and found the following Debian forum threads from last month: http://forums.debian.net/viewtopic.php?f=10t=118008 I was able to at least boot to a shell by editing my linux option within grub, changing ro to rw init=/bin/bash. At this point I could investigate /tmp, where I found over 6 million symlinks of apparently automatically-generated hexadecimal digits, all linking to the same .ppd file. The target of these symlinks had the same name as the printer model which I had added a few days ago. I successfully got my system to reboot again after deleting all of the symlinks: cd /tmp find . -name '5477*' | xargs rm On the next reboot the a start job is running for Create Volatile files and directories did pause and count up for a few seconds, (perhaps 4 or 5), but then proceeded to boot. I went into the printer settings and deleted the printer, (I'm no longer at that family-member's house and shouldn't need to print to that queue again any time soon). I've also verified that /tmp/ now only contains a single symlink to a .ppd file, (corresponding to the one remaining print queue that I do use on a regular basis). So I still don't know much about what process went wild and created millions of symlinks, but it's definitely a bug that can result in some pretty painful side effects. I looked through the bugs in cups and didn't see any talking about symlinks or /tmp so I hope this isn't a duplicate bug entry. If the bug is known to be fixed in subsequent versions, that will be great to know. If not, if there is anything I can do to debug further, I will be happy to do so. (If I had noticed the errant process creating the many symlinks while my systerm was still usable, then I certainly could have done some more investigation.) Please let me know what further information I might be able to provide that would be useful. Thanks, -Carl -- System Information: Debian Release: jessie/sid APT prefers unstable APT policy: (500, 'unstable'), (500, 'oldstable'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.16-3-amd64 (SMP w/4 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages cups depends on: ii cups-client1.7.5-5 ii cups-common1.7.5-5 ii cups-core-drivers 1.7.5-5 ii cups-daemon1.7.5-5 ii cups-filters 1.0.61-2 ii cups-ppdc 1.7.5-5 ii cups-server-common 1.7.5-5 ii debconf [debconf-2.0] 1.5.53 ii ghostscript9.06~dfsg-1.1+b1 ii libavahi-client3 0.6.31-4 ii libavahi-common3 0.6.31-4 ii libc-bin 2.19-11 ii libc6 2.19-11 ii libcups2 1.7.5-5 ii libcupscgi1
Bug#750521: acknowledgement of reception of RC bug report in scim from Debian maintainer
On 02.12.2014 15:35, Rolf Leggewie wrote: This is a quick heads-up to let everyone know that I am looking into this as well as to kindly request help from others. I shall write more as I progress with this ticket. OK, while I was not able to download a live CD for Jessie to test in a clean environment I was able to verify the following on my main computer. export GTK_IM_MODULE=scim;echo GETPIN | pinentry-gtk-2 fails This is the subject of this ticket export GTK_IM_MODULE=;echo GETPIN | pinentry-gtk-2 WORKS because it bypasses scim completely export GTK_IM_MODULE=scim;echo GETPIN | pinentry-qt4 WORKS Only the GTK2 version of the program is affected which leads me to believe this might have something to do with a GTK2/GTK3 incompatibility. I can type just fine in gjots2, though, which is also a GTK2 program. export GTK_IM_MODULE=;echo GETPIN | pinentry-curses FAILS suggesting there is something essentially wrong with pinentry as well -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#771749: cyrus-{common, imapd}-2.4: unhandled symlink to directory conversion: /usr/share/doc/PACKAGE
Hi, On Tue, Dec 2, 2014, at 16:17, Andreas Beckmann wrote: On 2014-12-02 16:05, Ondřej Surý wrote: I am out of clues how to fix that in a general manner. I guess I just can't support upgrades from testing versions and from wheezy versions at the same time. That should not be impossible ... At least for one of the packages (IIRC -imapd-2.4) I had checked and there were no dpkg-maint-script-helper calls ... so that wasn't an erroneus use. There must have been some added to other packages for the missing copyright files ... Yeah, I noticed that too. That's probably something that got created by testing jessie-sid migration, and I forgot to test wheezy-sid at the same time. I will just aim to have the upgrades from wheezy right and fix the most of jessie-to-jessie upgrades. And I just regret of ever using --link-doc more and more. When did you start and stop using it? And on which packages? There was so many changes back and forth that I have no idea now :). I sort of solved it by listing all cases I was able to think of into *.maintscript files :). Would you be able to test upgrades from wheezy to unstable with -10 quickly? If you put the .debs (amd64) together with a Packages file somewhere I can start my piuparts engine on it :-) (I can test upgrades from any release in the archive to any other release but using the new packages instead. Release includes testing, sid, ...) I found another problem. When you use absolute path for old_path it doesn't work in case of multiple symlink indirects, e.g. cyrus-imapd-cyrus-imapd-2.4-cyrus-common-2.4. So I have changed this into relative path, so it triggers correctly. wheezy-sid currently ends with: Setting up cyrus-imapd (2.4.17+caldav~beta10-10) ... Setting up cyrus-pop3d (2.4.17+caldav~beta10-10) ... Setting up cyrus-replication (2.4.17+caldav~beta10-10) ... Setting up cyrus-replication-2.4 (2.4.17+caldav~beta10-10) ... Setting up cyrus-imapd-2.4 (2.4.17+caldav~beta10-10) ... Setting up cyrus-pop3d-2.4 (2.4.17+caldav~beta10-10) ... Setting up cyrus-murder (2.4.17+caldav~beta10-10) ... Setting up cyrus-murder-2.4 (2.4.17+caldav~beta10-10) ... Setting up libcyrus-imap-perl (2.4.17+caldav~beta10-10) ... Setting up libcyrus-imap-perl24 (2.4.17+caldav~beta10-10) ... Setting up cyrus-dev (2.4.17+caldav~beta10-10) ... Setting up cyrus-dev-2.4 (2.4.17+caldav~beta10-10) ... Setting up cyrus-nntpd (2.4.17+caldav~beta10-10) ... Setting up cyrus-nntpd-2.4 (2.4.17+caldav~beta10-10) ... Setting up libfile-fcntllock-perl (0.22-1+b1) ... Setting up cyrus-admin (2.4.17+caldav~beta10-10) ... Setting up cyrus-admin-2.4 (2.4.17+caldav~beta10-10) ... Setting up cyrus-caldav (2.4.17+caldav~beta10-10) ... Setting up cyrus-caldav-2.4 (2.4.17+caldav~beta10-10) ... root@lettie:/tmp# ls -ld /usr/share/doc/*cyrus* drwxr-xr-x 2 root root 4096 Dec 2 16:06 /usr/share/doc/cyrus-admin drwxr-xr-x 2 root root 4096 Dec 2 16:06 /usr/share/doc/cyrus-admin-2.4 drwxr-xr-x 2 root root 4096 Dec 2 16:06 /usr/share/doc/cyrus-caldav drwxr-xr-x 2 root root 4096 Dec 2 16:06 /usr/share/doc/cyrus-caldav-2.4 drwxr-xr-x 2 root root 4096 Dec 2 16:06 /usr/share/doc/cyrus-clients drwxr-xr-x 2 root root 4096 Dec 2 16:06 /usr/share/doc/cyrus-clients-2.4 drwxr-xr-x 2 root root 4096 Dec 2 16:06 /usr/share/doc/cyrus-common drwxr-xr-x 2 root root 4096 Dec 2 16:05 /usr/share/doc/cyrus-common-2.4 drwxr-xr-x 2 root root 4096 Dec 2 16:05 /usr/share/doc/cyrus-dev drwxr-xr-x 2 root root 4096 Dec 2 16:05 /usr/share/doc/cyrus-dev-2.4 drwxr-xr-x 5 root root 4096 Dec 2 16:06 /usr/share/doc/cyrus-doc drwxr-xr-x 2 root root 4096 Dec 2 16:06 /usr/share/doc/cyrus-doc-2.4 drwxr-xr-x 2 root root 4096 Dec 2 16:05 /usr/share/doc/cyrus-imapd drwxr-xr-x 2 root root 4096 Dec 2 16:05 /usr/share/doc/cyrus-imapd-2.4 drwxr-xr-x 2 root root 4096 Dec 2 16:05 /usr/share/doc/cyrus-murder drwxr-xr-x 2 root root 4096 Dec 2 16:05 /usr/share/doc/cyrus-murder-2.4 drwxr-xr-x 2 root root 4096 Dec 2 16:05 /usr/share/doc/cyrus-nntpd drwxr-xr-x 2 root root 4096 Dec 2 16:05 /usr/share/doc/cyrus-nntpd-2.4 drwxr-xr-x 2 root root 4096 Dec 2 16:05 /usr/share/doc/cyrus-pop3d drwxr-xr-x 2 root root 4096 Dec 2 16:05 /usr/share/doc/cyrus-pop3d-2.4 drwxr-xr-x 2 root root 4096 Dec 2 16:05 /usr/share/doc/cyrus-replication drwxr-xr-x 2 root root 4096 Dec 2 16:05 /usr/share/doc/cyrus-replication-2.4 drwxr-xr-x 2 root root 4096 Dec 2 16:05 /usr/share/doc/libcyrus-imap-perl drwxr-xr-x 2 root root 4096 Dec 2 16:05 /usr/share/doc/libcyrus-imap-perl24 Looks good, right? :) O. -- Ondřej Surý ond...@sury.org Knot DNS (https://www.knot-dns.cz/) – a high-performance DNS server -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#771739: marked as done (could not start nodm with systemd 217-1 or 217-2)
Your message dated Tue, 02 Dec 2014 16:19:59 + with message-id e1xvqbd-er...@franck.debian.org and subject line Bug#771739: fixed in systemd 217-3 has caused the Debian Bug report #771739, regarding could not start nodm with systemd 217-1 or 217-2 to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 771739: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=771739 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: systemd Version: 217-2 Severity: grave Could not start nodm with systemd 217-1 or 217-2. ---End Message--- ---BeginMessage--- Source: systemd Source-Version: 217-3 We believe that the bug you reported is fixed in the latest version of systemd, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 771...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Martin Pitt mp...@debian.org (supplier of updated systemd package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Tue, 02 Dec 2014 16:53:36 +0100 Source: systemd Binary: systemd systemd-sysv libpam-systemd libsystemd0 libsystemd-dev libsystemd-login0 libsystemd-login-dev libsystemd-daemon0 libsystemd-daemon-dev libsystemd-journal0 libsystemd-journal-dev libsystemd-id128-0 libsystemd-id128-dev udev libudev1 libudev-dev udev-udeb libudev1-udeb libgudev-1.0-0 gir1.2-gudev-1.0 libgudev-1.0-dev python3-systemd systemd-dbg Architecture: source amd64 Version: 217-3 Distribution: experimental Urgency: medium Maintainer: Debian systemd Maintainers pkg-systemd-maintain...@lists.alioth.debian.org Changed-By: Martin Pitt mp...@debian.org Description: gir1.2-gudev-1.0 - libgudev-1.0 introspection data libgudev-1.0-0 - GObject-based wrapper library for libudev libgudev-1.0-dev - libgudev-1.0 development files libpam-systemd - system and service manager - PAM module libsystemd-daemon-dev - systemd utility library (transitional package) libsystemd-daemon0 - systemd utility library (deprecated) libsystemd-dev - systemd utility library - development files libsystemd-id128-0 - systemd 128 bit ID utility library (deprecated) libsystemd-id128-dev - systemd 128 bit ID utility library (transitional package) libsystemd-journal-dev - systemd journal utility library (transitional package) libsystemd-journal0 - systemd journal utility library (deprecated) libsystemd-login-dev - systemd login utility library (transitional package) libsystemd-login0 - systemd login utility library (deprecated) libsystemd0 - systemd utility library libudev-dev - libudev development files libudev1 - libudev shared library libudev1-udeb - libudev shared library (udeb) python3-systemd - Python 3 bindings for systemd systemd- system and service manager systemd-dbg - system and service manager (debug symbols) systemd-sysv - system and service manager - SysV links udev - /dev/ and hotplug management daemon udev-udeb - /dev/ and hotplug management daemon (udeb) Closes: 771498 771739 Changes: systemd (217-3) experimental; urgency=medium . [ Martin Pitt ] * systemd.bug-script: Really capture stderr of systemd-delta. (Closes: #771498) * boot-and-services autopkgtest: Give test apparmor job some time to actually finish. . [ Didier Roche ] * updated debian/patches/insserv.conf-generator.patch: - if /etc/X11/default-display-manager doesn't match a systemd unit (or doesn't exist), be less agressive about what to mask: we let all sysvinit-only display-manager units enabled to fallback to previous behavior and let them starting. (Closes: #771739) Checksums-Sha1: ab65791e6bb28d194124948f8edfb9154c786473 4103 systemd_217-3.dsc 90f674413b3cc2e049ed669a9c8535809df75312 138460 systemd_217-3.debian.tar.xz eddd3713290a4a63aa720f92d1e5d01848d3dc6f 2898800 systemd_217-3_amd64.deb 43c337780cf81974a182dddb0e4d0bc0b037ef0e 31174 systemd-sysv_217-3_amd64.deb 7456fe898b6ca20b96dc8f479aa3c9ab7d3d01c7 121734 libpam-systemd_217-3_amd64.deb 891c3eec012c6f292a2a522ac183be26291f5b03 85040 libsystemd0_217-3_amd64.deb e3e5f4b59934861ff60c8d8fba6b5b7fe34cb8fa 91792 libsystemd-dev_217-3_amd64.deb
Bug#771749: cyrus-{common, imapd}-2.4: unhandled symlink to directory conversion: /usr/share/doc/PACKAGE
Hi again, On Tue, Dec 2, 2014, at 16:17, Andreas Beckmann wrote: When did you start and stop using it? And on which packages? I have just realized that I have: cyrus-imapd-2.4_2.4.16-4+deb7u2_amd64.changes cyrus-imapd-2.4_2.4.17+caldav~beta10-10_amd64.changes cyrus-imapd-2.4_2.4.17+caldav~beta10-1_amd64.changes cyrus-imapd-2.4_2.4.17+caldav~beta10-2_amd64.changes cyrus-imapd-2.4_2.4.17+caldav~beta10-3_amd64.changes cyrus-imapd-2.4_2.4.17+caldav~beta10-4_amd64.changes cyrus-imapd-2.4_2.4.17+caldav~beta10-5_amd64.changes cyrus-imapd-2.4_2.4.17+caldav~beta10-6_amd64.changes cyrus-imapd-2.4_2.4.17+caldav~beta10-7_amd64.changes cyrus-imapd-2.4_2.4.17+caldav~beta10-8_amd64.changes cyrus-imapd-2.4_2.4.17+caldav~beta10-9_amd64.changes cyrus-imapd-2.4_2.4.17+caldav~beta9-10_amd64.changes cyrus-imapd-2.4_2.4.17+caldav~beta9-11_amd64.changes cyrus-imapd-2.4_2.4.17+caldav~beta9-12~1.gbp72113b_amd64.changes cyrus-imapd-2.4_2.4.17+caldav~beta9-12_amd64.changes cyrus-imapd-2.4_2.4.17+caldav~beta9-2_amd64.changes cyrus-imapd-2.4_2.4.17+caldav~beta9-3_amd64.changes cyrus-imapd-2.4_2.4.17+caldav~beta9-4_amd64.changes cyrus-imapd-2.4_2.4.17+caldav~beta9-5_amd64.changes cyrus-imapd-2.4_2.4.17+caldav~beta9-6_amd64.changes cyrus-imapd-2.4_2.4.17+caldav~beta9-7_amd64.changes cyrus-imapd-2.4_2.4.17+caldav~beta9-8_amd64.changes cyrus-imapd-2.4_2.4.17+caldav~beta9-9_amd64.changes on my local disk, so I will try to check for possible symlinks that could have existed in testing and sid. But not today. O. -- Ondřej Surý ond...@sury.org Knot DNS (https://www.knot-dns.cz/) – a high-performance DNS server -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#771749: marked as done (cyrus-{common, imapd}-2.4: unhandled symlink to directory conversion: /usr/share/doc/PACKAGE)
Your message dated Tue, 02 Dec 2014 16:34:19 +
with message-id e1xvqp5-0002k8...@franck.debian.org
and subject line Bug#771749: fixed in cyrus-imapd-2.4 2.4.17+caldav~beta10-10
has caused the Debian Bug report #771749,
regarding cyrus-{common, imapd}-2.4: unhandled symlink to directory conversion:
/usr/share/doc/PACKAGE
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
771749: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=771749
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
---BeginMessage---
Package: cyrus-imapd-2.4,cyrus-common-2.4
Version: 2.4.17+caldav~beta10-8
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts
Hi,
an upgrade test with piuparts revealed that your package installs files
over existing symlinks and possibly overwrites files owned by other
packages. This usually means an old version of the package shipped a
symlink but that was later replaced by a real (and non-empty)
directory. This kind of overwriting another package's files cannot be
detected by dpkg.
This was observed on the following upgrade paths:
wheezy - jessie (2.4.17+caldav~beta10-8)
wheezy - sid (2.4.17+caldav~beta10-9)
For /usr/share/doc/PACKAGE this may not be problematic as long as both
packages are installed, ship byte-for-byte identical files and are
upgraded in lockstep. But once one of the involved packages gets
removed, the other one will lose its documentation files, too,
including the copyright file, which is a violation of Policy 12.5:
https://www.debian.org/doc/debian-policy/ch-docs.html#s-copyrightfile
For other overwritten locations anything interesting may happen.
Note that dpkg intentionally does not replace directories with symlinks
and vice versa, you need the maintainer scripts to do this.
See in particular the end of point 4 in
https://www.debian.org/doc/debian-policy/ch-maintainerscripts.html#s-unpackphase
It is recommended to use the dpkg-maintscript-helper commands
'dir_to_symlink' and 'symlink_to_dir' (available since dpkg 1.17.2)
to perform the conversion, ideally using d/$PACKAGE.mainstscript.
See dpkg-maintscript-helper(1) and dh_installdeb(1) for details.
From the attached log (usually somewhere in the middle...):
4m16.8s ERROR: FAIL: silently overwrites files via directory symlinks:
/usr/share/doc/cyrus-common-2.4/changelog.Debian.gz (cyrus-common-2.4) !=
/usr/share/doc/cyrus-common/changelog.Debian.gz (cyrus-common)
/usr/share/doc/cyrus-common-2.4/copyright (cyrus-common-2.4) !=
/usr/share/doc/cyrus-common/copyright (cyrus-common)
/usr/share/doc/cyrus-imapd-2.4/copyright (cyrus-imapd-2.4) !=
/usr/share/doc/cyrus-common/copyright (cyrus-common)
There may be more packages failing, but these cannot be tested by piuparts
due to cyrus-common-2.4 already failing ...
cheers,
Andreas
cyrus-imapd-2.4_2.4.17+caldav~beta10-8.log.gz
Description: application/gzip
---End Message---
---BeginMessage---
Source: cyrus-imapd-2.4
Source-Version: 2.4.17+caldav~beta10-10
We believe that the bug you reported is fixed in the latest version of
cyrus-imapd-2.4, which is due to be installed in the Debian FTP archive.
A summary of the changes between this version and the previous one is
attached.
Thank you for reporting the bug, which will now be closed. If you
have further comments please address them to 771...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Ondřej Surý ond...@debian.org (supplier of updated cyrus-imapd-2.4 package)
(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Format: 1.8
Date: Tue, 02 Dec 2014 15:47:18 +0100
Source: cyrus-imapd-2.4
Binary: cyrus-common cyrus-doc cyrus-imapd cyrus-pop3d cyrus-admin cyrus-murder
cyrus-replication cyrus-nntpd cyrus-caldav cyrus-clients cyrus-dev
libcyrus-imap-perl cyrus-common-2.4 cyrus-doc-2.4 cyrus-imapd-2.4
cyrus-pop3d-2.4 cyrus-admin-2.4 cyrus-murder-2.4 cyrus-replication-2.4
cyrus-nntpd-2.4 cyrus-caldav-2.4 cyrus-clients-2.4 cyrus-dev-2.4
libcyrus-imap-perl24
Architecture: source amd64 all
Version: 2.4.17+caldav~beta10-10
Distribution: unstable
Urgency: medium
Maintainer: Debian Cyrus Team
pkg-cyrus-imapd-debian-de...@lists.alioth.debian.org
Changed-By: Ondřej Surý ond...@debian.org
Description:
cyrus-admin - Cyrus mail system - administration tools
cyrus-admin-2.4 - Cyrus mail system - administration tools [dummy package]
Bug#750521: acknowledgement of reception of RC bug report in scim from Debian maintainer
On 03.12.2014 00:25, Rolf Leggewie wrote: export GTK_IM_MODULE=;echo GETPIN | pinentry-curses FAILS suggesting there is something essentially wrong with pinentry as well I got confused about what Ximin had written about pinentry-curses since later on he mentioned only pinentry-gtk2, but here is the update on pinentry-curses. export GTK_IM_MODULE=scim mytty=$(tty); echo GETPIN | pinentry-curses --ttyname=$mytty WORKS, but at least here doesn't invoke scim and thus no CJKV or other input. Only simple entry of ASCII and similar character is possible. Contrary to my statement above, pinentry-curses seems to be generally working as expected. -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#750521: acknowledgement of reception of RC bug report in scim from Debian maintainer
On 03.12.2014 00:25, Rolf Leggewie wrote: export GTK_IM_MODULE=;echo GETPIN | pinentry-curses FAILS suggesting there is something essentially wrong with pinentry as well I got confused about what Ximin had written about pinentry-curses since later on he mentioned only pinentry-gtk2, but here is the update on pinentry-curses. export GTK_IM_MODULE=scim mytty=$(tty); echo GETPIN | pinentry-curses --ttyname=$mytty WORKS, but at least here doesn't invoke scim and thus no CJKV or other input. Only simple entry of ASCII and similar character is possible. Contrary to my statement above, pinentry-curses seems to be generally working as expected. -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#750521: acknowledgement of reception of RC bug report in scim from Debian maintainer
On 12/02/2014 11:40 AM, Rolf Leggewie wrote: Contrary to my statement above, pinentry-curses seems to be generally working as expected. yep, i think this report is specifically about something broken in the interaction between pinentry-gtk2 and scim. I note that setting the GTK_IM_MODULE environment might not be relevant for pinentry-qt4 at all, because qt4 probably doesn't inspect the GTK_* environment variables. So we're left with the following narrow buggy test case: echo GETPIN | GTK_IM_MODULE=scim pinentry-gtk-2 thanks for tracking it down further, Rolf. --dkg signature.asc Description: OpenPGP digital signature
Bug#771794: [Python-modules-team] Bug#771794: pip silently removes/updates system provided python packages
I'd very much prefer it if you didn't do this. This *is* going to break things for people and it's going to cause a bunch of confusion. --- Donald Stufft PGP: 7C6B 7C5D 5E2B 6356 A926 F04F 6E3C BCE9 3372 DCFA -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#771749: cyrus-{common, imapd}-2.4: unhandled symlink to directory conversion: /usr/share/doc/PACKAGE
Please test -11 when it hits the archive/incoming/... debdiff looks big, but only few old links were missing, but I sorted the maintscripts, so it can be easily compared for missing stuff. O. On Tue, Dec 2, 2014, at 17:28, Ondřej Surý wrote: Hi again, On Tue, Dec 2, 2014, at 16:17, Andreas Beckmann wrote: When did you start and stop using it? And on which packages? I have just realized that I have: cyrus-imapd-2.4_2.4.16-4+deb7u2_amd64.changes cyrus-imapd-2.4_2.4.17+caldav~beta10-10_amd64.changes cyrus-imapd-2.4_2.4.17+caldav~beta10-1_amd64.changes cyrus-imapd-2.4_2.4.17+caldav~beta10-2_amd64.changes cyrus-imapd-2.4_2.4.17+caldav~beta10-3_amd64.changes cyrus-imapd-2.4_2.4.17+caldav~beta10-4_amd64.changes cyrus-imapd-2.4_2.4.17+caldav~beta10-5_amd64.changes cyrus-imapd-2.4_2.4.17+caldav~beta10-6_amd64.changes cyrus-imapd-2.4_2.4.17+caldav~beta10-7_amd64.changes cyrus-imapd-2.4_2.4.17+caldav~beta10-8_amd64.changes cyrus-imapd-2.4_2.4.17+caldav~beta10-9_amd64.changes cyrus-imapd-2.4_2.4.17+caldav~beta9-10_amd64.changes cyrus-imapd-2.4_2.4.17+caldav~beta9-11_amd64.changes cyrus-imapd-2.4_2.4.17+caldav~beta9-12~1.gbp72113b_amd64.changes cyrus-imapd-2.4_2.4.17+caldav~beta9-12_amd64.changes cyrus-imapd-2.4_2.4.17+caldav~beta9-2_amd64.changes cyrus-imapd-2.4_2.4.17+caldav~beta9-3_amd64.changes cyrus-imapd-2.4_2.4.17+caldav~beta9-4_amd64.changes cyrus-imapd-2.4_2.4.17+caldav~beta9-5_amd64.changes cyrus-imapd-2.4_2.4.17+caldav~beta9-6_amd64.changes cyrus-imapd-2.4_2.4.17+caldav~beta9-7_amd64.changes cyrus-imapd-2.4_2.4.17+caldav~beta9-8_amd64.changes cyrus-imapd-2.4_2.4.17+caldav~beta9-9_amd64.changes on my local disk, so I will try to check for possible symlinks that could have existed in testing and sid. But not today. O. -- Ondřej Surý ond...@sury.org Knot DNS (https://www.knot-dns.cz/) – a high-performance DNS server ___ Pkg-Cyrus-imapd-Debian-devel mailing list pkg-cyrus-imapd-debian-de...@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-cyrus-imapd-debian-devel -- Ondřej Surý ond...@sury.org Knot DNS (https://www.knot-dns.cz/) – a high-performance DNS server -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#750521: acknowledgement of reception of RC bug report in scim from Debian maintainer
On 03.12.2014 00:49, Daniel Kahn Gillmor wrote: On 12/02/2014 11:40 AM, Rolf Leggewie wrote: Contrary to my statement above, pinentry-curses seems to be generally working as expected. yep, i think this report is specifically about something broken in the interaction between pinentry-gtk2 and scim. Yep, and it turns out to be a VERY old problem indeed (still reading up on it). It's from at least 2007 or most likely even 2006! http://thread.gmane.org/gmane.comp.encryption.gpg.devel/14423 https://bugzilla.novell.com/show_bug.cgi?id=330073 The people at Novell came to the conclusion that the problem needs to be fixed in upstream pinentry-gtk-2. Unfortunately the reference link is 404 now and even web.archive.org does not have a backup copy of it. I note that setting the GTK_IM_MODULE environment might not be relevant for pinentry-qt4 at all, because qt4 probably doesn't inspect the GTK_* environment variables. My bad. Obviously, that should read QT_IM_MODULE which I have set to scim as default. It still is the (known) case that pinentry-qt4 works. This provides a good workaround for anyone affected by this issue. -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#771794: [Python-modules-team] Bug#771794: Bug#771794: pip silently removes/updates system provided python packages
On 12/02/2014 11:51 AM, Donald Stufft wrote: I'd very much prefer it if you didn't do this. This *is* going to break things for people and it's going to cause a bunch of confusion. It's not clear to me which side you're arguing for. can you clarify which action is going to break things for people and cause a bunch of confusion? If pip silently removes/updates system-provided python packages, that is likely to break things and cause a bunch of confusion, no? alternately, if pip verbosely refuses to run as uid 0, that's at least a non-silent failure. (though it certainly will break things and frustrate some people) --dkg signature.asc Description: OpenPGP digital signature
Bug#750521: acknowledgement of reception of RC bug report in scim from Debian maintainer
Control: reassign -1 pinentry-gtk2 On 03.12.2014 01:14, Rolf Leggewie wrote: yep, i think this report is specifically about something broken in the interaction between pinentry-gtk2 and scim. Yep, and it turns out to be a VERY old problem indeed (still reading up on it). It's from at least 2007 or most likely even 2006! http://thread.gmane.org/gmane.comp.encryption.gpg.devel/14423 https://bugzilla.novell.com/show_bug.cgi?id=330073 The people at Novell came to the conclusion that the problem needs to be fixed in upstream pinentry-gtk-2. After reading through the gnupg-devel mailing list over on gmane.org, specifically http://thread.gmane.org/gmane.comp.encryption.gpg.devel/14423/focus=14461 I am reassigning this back to the pinentry package. That thread has some indication that some work was done upstream but there is also an entry from 2009 indicating the problem is still present and that mail never received a response. -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed: Re: acknowledgement of reception of RC bug report in scim from Debian maintainer
Processing control commands: reassign -1 pinentry-gtk2 Bug #750521 [scim-gtk-immodule] scim-gtk-immodule breaks pinentry-gtk2 and impairs gnome-keyring Bug reassigned from package 'scim-gtk-immodule' to 'pinentry-gtk2'. No longer marked as found in versions scim/1.4.14-6. Ignoring request to alter fixed versions of bug #750521 to the same values previously set -- 750521: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=750521 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#771794: [Python-modules-team] Bug#771794: Bug#771794: pip silently removes/updates system provided python packages
On Dec 2, 2014, at 12:25 PM, Daniel Kahn Gillmor d...@fifthhorseman.net wrote: On 12/02/2014 11:51 AM, Donald Stufft wrote: I'd very much prefer it if you didn't do this. This *is* going to break things for people and it's going to cause a bunch of confusion. It's not clear to me which side you're arguing for. can you clarify which action is going to break things for people and cause a bunch of confusion? If pip silently removes/updates system-provided python packages, that is likely to break things and cause a bunch of confusion, no? alternately, if pip verbosely refuses to run as uid 0, that's at least a non-silent failure. (though it certainly will break things and frustrate some people) --dkg I’m saying don’t make the change. There are major software systems that rely on the ability to install things as root using pip. Chef, puppet, etc. It’s also going to cause a bunch of confusion because all of a sudden pip is going to have a vastly different behavior if it’s running on Debian vs if it’s running somewhere else. That’s going to blow back on us (the pip maintainers) as we get bug reports from people who assume we broke their use cases for pip. We (pip maintainers) recognize this can cause issues and we’d like to arrive a solution that solves this issue without introducing major divergence between various platforms and with respect towards the use cases that need or require that ability. It’s somewhat of a thorny problems to do it correctly, we’re a fairly small team with limited time, and we have bigger issues of concern that have taken a front seat. --- Donald Stufft PGP: 7C6B 7C5D 5E2B 6356 A926 F04F 6E3C BCE9 3372 DCFA -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#771830: Fails to execute at all
Package: systemd-cron Version: 1.3.1+ds1-2 Severity: grave Here are relevant lines from output of dmesg-command: [ 21.059257] EXT4-fs (sdb1): mounted filesystem with ordered data mode. Opts: (null) [ 21.520730] systemd[1]: /usr appears to be on its own filesytem and is not already mounted. This is not a supported setup. Some things will probably break (sometimes even silently) in mysterious ways. Consult http://freedesktop.org/wiki/Software/systemd/separate-usr-is-broken for more information. *[ 21.577570] systemd[123]: Failed to execute /lib/systemd/system-generators/systemd-crontab-generator: No such file or directory *[ 21.578059] systemd[122]: /lib/systemd/system-generators/systemd-crontab-generator failed with error code 1. [ 22.225613] fuse init (API version 7.23) Maybe problem is this: /usr is not mounted when it tries to run that command. That command is actually python script. Its shebang line is this: #!/usr/bin/python Is it really so necessary to run that /lib/systemd/system-generators/systemd-crontab-generator when /usr is not mounted yet? How about running that command by hand after boot?: -=*[ROOT ZSH]*=- root@juhtolv | Tue 02 Dec 2014 19:43:37 | 8404 | pts/1.1 /root # /lib/systemd/system-generators/systemd-crontab-generator Traceback (most recent call last): File /lib/systemd/system-generators/systemd-crontab-generator, line 19, in module TARGER_DIR = sys.argv[1] IndexError: list index out of range [1]6032 exit 1 /lib/systemd/system-generators/systemd-crontab-generator -=*[ROOT ZSH]*=- root@juhtolv | Tue 02 Dec 2014 19:43:59 | 8405 | pts/1.1 /root # /lib/systemd/system-generators/systemd-crontab-generator /etc/crontab Traceback (most recent call last): File /lib/systemd/system-generators/systemd-crontab-generator, line 32, in module os.makedirs(TIMERS_DIR) File /usr/lib/python2.7/os.py, line 157, in makedirs mkdir(name, mode) OSError: [Errno 20] Not a directory: '/etc/crontab/cron.target.wants' [1]6094 exit 1 /lib/systemd/system-generators/systemd-crontab-generator /etc/crontab Is that command really so stupid, that it only accepts folders and not files? If so, why /etc/crontab is menationed in FILES-section of man page of systemd-crontab-generator ? -- System Information: Debian Release: jessie/sid APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'testing'), (500, 'stable') Architecture: i386 (i686) Kernel: Linux 3.16.0-4-686-pae (SMP w/1 CPU core) Locale: LANG=fi_FI.utf8, LC_CTYPE=fi_FI.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages systemd-cron depends on: ii init-system-helpers 1.22 ii python 2.7.8-2 pn python:any none ii systemd-sysv 215-6 systemd-cron recommends no packages. systemd-cron suggests no packages. -- Configuration Files: /etc/crontab changed: SHELL=/bin/sh PATH=/usr/local/sbin:/usr/local/bin:/sbin:/bin:/usr/sbin:/usr/bin @reboot /usr/bin/screen -wipe /dev/null 21 ; /usr/bin/screen -U -d -m 01 04 * * * /root/scripts/emptypartial.sh 01 05 * * * /root/scripts/emptypartial.sh 01 06 * * * /root/scripts/emptypartial.sh 01 07 * * * /root/scripts/emptypartial.sh 01 12 * * * /root/scripts/emptypartial.sh 01 01 * * 1 /bin/echo '/usr/bin/time -v /usr/bin/nice -n 20 /usr/local/sbin/juhtolv-backup.sh' | batch 01 02 * * 1 /bin/echo '/usr/bin/time -v /usr/bin/nice -n 20 /usr/local/sbin/juhtolv-backup2.sh' | batch 01 01 * * 2 /bin/echo '/usr/bin/time -v /usr/bin/nice -n 20 /usr/local/sbin/juhtolv-backup.sh' | batch 01 02 * * 2 /bin/echo '/usr/bin/time -v /usr/bin/nice -n 20 /usr/local/sbin/juhtolv-backup2.sh' | batch 01 01 * * 3 /bin/echo '/usr/bin/time -v /usr/bin/nice -n 20 /usr/local/sbin/juhtolv-backup.sh' | batch 01 02 * * 3 /bin/echo '/usr/bin/time -v /usr/bin/nice -n 20 /usr/local/sbin/juhtolv-backup2.sh' | batch 01 01 * * 4 /bin/echo '/usr/bin/time -v /usr/bin/nice -n 20 /usr/local/sbin/juhtolv-backup.sh' | batch 01 02 * * 4 /bin/echo '/usr/bin/time -v /usr/bin/nice -n 20 /usr/local/sbin/juhtolv-backup2.sh' | batch 01 01 * * 5 /bin/echo '/usr/bin/time -v /usr/bin/nice -n 20 /usr/local/sbin/juhtolv-backup.sh' | batch 01 02 * * 5 /bin/echo '/usr/bin/time -v /usr/bin/nice -n 20 /usr/local/sbin/juhtolv-backup2.sh' | batch 01 01 * * 6 /bin/echo '/usr/bin/time -v /usr/bin/nice -n 20 /usr/local/sbin/juhtolv-backup.sh' | batch 01 02 * * 6 /bin/echo '/usr/bin/time -v /usr/bin/nice -n 20 /usr/local/sbin/juhtolv-backup2.sh' | batch 01 01 * * 7 /bin/echo '/usr/bin/time -v /usr/bin/nice -n 20 /usr/local/sbin/juhtolv-backup.sh' | batch 01 02 * * 7 /bin/echo '/usr/bin/time -v /usr/bin/nice -n 20 /usr/local/sbin/juhtolv-backup2.sh' | batch -- no debconf information -- Juhapekka naula Tolvanen * http colon slash slash iki dot fi slash juhtolv Quidquid Latine dictum sit altum videtur. -- To UNSUBSCRIBE, email
Bug#771126: marked as done (libav/lena.pnm: non-DFSG free + not mentioned in copyright)
Your message dated Tue, 02 Dec 2014 18:04:35 + with message-id e1xvror-0005u4...@franck.debian.org and subject line Bug#771126: fixed in libav 6:11.1-1~exp1 has caused the Debian Bug report #771126, regarding libav/lena.pnm: non-DFSG free + not mentioned in copyright to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 771126: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=771126 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Source: libav Severity: serious Tags: upstream Justification: Policy 2.2.1 -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 It was made aware at lists.debian.org/54764bf5.2090...@googlemail.com that the source of libav contains image file tests/lena.pnm which lacks licensing (and is well known to not be in the public domain). - Jonas -BEGIN PGP SIGNATURE- Version: GnuPG v1 iQF8BAEBCgBmBQJUdmaZXxSAAC4AKGlzc3Vlci1mcHJAbm90YXRpb25zLm9w ZW5wZ3AuZmlmdGhob3JzZW1hbi5uZXQ3NjQ4ODQwMTIyRTJDNTBFQzUxRDQwRTI0 RUMxQjcyMjM3NEY5QkQ2AAoJEE7BtyI3T5vW28oIAKX/xV4MUJdxjXRUjy3um6Yi 62UhjzReqwoWzZa69dZNfR1wSjIycyZVLogTQ7DARNXudW/Ov9mgl4BgU0MACE0h EcM7eSZH21AsXEnFypzYGXVhiUSENtti7S01S7GQSGQUm+LnEYvYv9cI7saoa4y7 esytjPlkcYZRB1lQb07jsC2Qz/hjHNx3HvBqeUbgGcKMymTkFI7C2lu3NYPcmMxc z3BHl3rcJk3q8TvrNgsbx674F91C22Cg8KwWTLZl0pTbFwTc1XuOQV1A0aBUeHx4 fFN59R31SBmsY7RBfDl9w4fvMBXmsMtEjbiE/Pie0XESCsrjrSwCOhmepTXoxSA= =HDmN -END PGP SIGNATURE- ---End Message--- ---BeginMessage--- Source: libav Source-Version: 6:11.1-1~exp1 We believe that the bug you reported is fixed in the latest version of libav, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 771...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Jonas Smedegaard d...@jones.dk (supplier of updated libav package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Tue, 02 Dec 2014 16:37:04 +0100 Source: libav Binary: libav-tools libav-dbg libav-doc libavutil54 libavcodec56 libavdevice55 libavformat56 libavfilter5 libswscale3 libavutil-dev libavcodec-dev libavdevice-dev libavformat-dev libavfilter-dev libswscale-dev libavresample-dev libavresample2 libavcodec-extra-56 libavcodec-extra Architecture: source all amd64 Version: 6:11.1-1~exp1 Distribution: experimental Urgency: medium Maintainer: Debian Multimedia Maintainers pkg-multimedia-maintain...@lists.alioth.debian.org Changed-By: Jonas Smedegaard d...@jones.dk Description: libav-dbg - Debug symbols for Libav related packages libav-doc - Documentation of the Libav API libav-tools - Multimedia player, encoder and transcoder libavcodec-dev - Development files for libavcodec libavcodec-extra - Libav codec library (additional codecs meta-package) libavcodec-extra-56 - Libav codec library (additional codecs) libavcodec56 - Libav codec library libavdevice-dev - Development files for libavdevice libavdevice55 - Libav device handling library libavfilter-dev - Development files for libavfilter libavfilter5 - Libav video filtering library libavformat-dev - Development files for libavformat libavformat56 - Libav file format library libavresample-dev - Development files for libavresample libavresample2 - Libav audio resampling library libavutil-dev - Development files for libavutil libavutil54 - Libav utility library libswscale-dev - Development files for libswscale libswscale3 - Libav video scaling library Closes: 771126 Changes: libav (6:11.1-1~exp1) experimental; urgency=medium . [ upstream ] * New release. + Replace lena.pnm. Closes: bug#771126. + Treat all '*.pnm' files as non-text file. + opusdec: Ensure all substreams have same number of coded samples. + lavu: Fix memory leaks by using a mutex instead of atomics. + lavu: Add wrappers for the pthreads mutex API. + mp3enc: Fix a triggerable assert. + resample: Avoid off-by-1 errors in PTS calcs. + imc: Fix order of operations in coefficients read. + hevc_mvs: Ensure to always initialize the temporal MV fully. + hevc_mvs: Initialize the temporal MV in case of missing ref. + h264: Reset ret to avoid propagating minor failures. + hevc: Initialize
Bug#727800: kmail: KMail goes bonkers following Qt update
I contacted Upstream and although they're too busy right now he offered this clue, in response to my bug description. Diane [Diane] With akonadiconsole under job tracker I can see a vast number of SpecialCollectionsRequestJob's being scheduled and with the query browser see a bunch of Select ... from CollectionTable queries being generated. Screenshot of query browser posted: https://bugs.debian.org/cgi-bin/bugreport.cgi?msg=40;filename=akonadi-quer ie s.png;att=1;bug=727800 I can stop the loop by restarting akonadi, though I'm not sure if that's the best solution to this. Would you have any suggestions? [upstream] From a quick look I'd say the problem is the part when the migrator tries to replace the local maildir resource, created as a requirement for the maildispatcher, with the resource it has just created for the user's previously used folder structure. It might be possible to disable that through a configuration option, but I can't remember with certainty. signature.asc Description: This is a digitally signed message part.
Processed: Re: Bug#771830: Fails to execute at all
Processing control commands: tag -1 + wontfix Bug #771830 [systemd-cron] Fails to execute at all Added tag(s) wontfix. severity -1 normal Bug #771830 [systemd-cron] Fails to execute at all Severity set to 'normal' from 'grave' -- 771830: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=771830 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#771830: Fails to execute at all
control: tag -1 + wontfix control: severity -1 normal Hi, The generator must follow a special set of rules defined here: http://www.freedesktop.org/wiki/Software/systemd/Generators/ One of those is that they are the first thing run by systemd; even before /usr is mounted. This can't be changed. By runnning, you can see the generator as the blue spot: $ systemd-analyze plot /tmp/boot.svg $ xdg-open /tmp/boot.svg One workaround to your problem would be to replace /lib/systemd/system-generators/systemd-crontab-generator by a shell script that calls the real generator (move it to /lib/systemd/systemd-cron/ ) only if /usr is mounted and python avaible + do a systemctl daemon-reload systemctl restart cron.target in /etc/rc.local I could even publish this script in our 'contrib' folder https://github.com/systemd-cron/systemd-cron/tree/master/contrib but wouldn't made it the default. [ 21.520730] systemd[1]: /usr appears to be on its own filesytem and is not already mounted. This is not a supported setup. systemd warned you :-| /usr is not mounted when it tries to run that command. That command is actually python script. Its shebang line is this: #!/usr/bin/python Is it really so necessary to run that /lib/systemd/system-generators/systemd-crontab-generator when /usr is not mounted yet? The first run is unconditional; the generator schedules a second run of itself if /var is a separate partition (I use this setup). How about running that command by hand after boot?: This should never run by hand; It should allways be called by systemctl daemon-reload Alexandre Detiste -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#771794: (no subject)
For reference: https://github.com/pypa/pip/issues/1668 -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#765129: tcos: diff for NMU version 0.89.93+nmu1
El 24/11/14 a las 15:28, Jonathan Wiltshire escribió: On Mon, Nov 24, 2014 at 12:05:21AM +0100, Mario Izquierdo Rodríguez wrote: El 23/11/14 a las 19:40, Jonathan Wiltshire escribió: Control: tags 765129 + pending Dear maintainer, I've prepared an NMU for tcos (versioned as 0.89.93+nmu1) and uploaded it to DELAYED/2. Please feel free to tell me if I should delay it longer. Regards. Hi, thanks for NMU, I'm not a DD and I have a new package but no sponsor for upload. How about preparing a maintainer upload and I'll sponsor it for you? Hi Jonathan. I had prepared new TCOS package: http://mariodebian.com/debian-packages/tcos_0.89.97.dsc Only sources (not binary) Can you upload it? Thanks in advance. -- Mario Izquierdo Rodríguez http://mariodebian.com -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#771794: pip silently removes/updates system provided python packages
On Tuesday, December 02, 2014 12:37:40 PM Donald Stufft wrote: On Dec 2, 2014, at 12:25 PM, Daniel Kahn Gillmor d...@fifthhorseman.net wrote: On 12/02/2014 11:51 AM, Donald Stufft wrote: I'd very much prefer it if you didn't do this. This *is* going to break things for people and it's going to cause a bunch of confusion. It's not clear to me which side you're arguing for. can you clarify which action is going to break things for people and cause a bunch of confusion? If pip silently removes/updates system-provided python packages, that is likely to break things and cause a bunch of confusion, no? alternately, if pip verbosely refuses to run as uid 0, that's at least a non-silent failure. (though it certainly will break things and frustrate some people) --dkg I’m saying don’t make the change. There are major software systems that rely on the ability to install things as root using pip. Chef, puppet, etc. It’s also going to cause a bunch of confusion because all of a sudden pip is going to have a vastly different behavior if it’s running on Debian vs if it’s running somewhere else. That’s going to blow back on us (the pip maintainers) as we get bug reports from people who assume we broke their use cases for pip. We (pip maintainers) recognize this can cause issues and we’d like to arrive a solution that solves this issue without introducing major divergence between various platforms and with respect towards the use cases that need or require that ability. It’s somewhat of a thorny problems to do it correctly, we’re a fairly small team with limited time, and we have bigger issues of concern that have taken a front seat. In the meantime, we have a release to get out the door, so wait for upstream to figure it out in TBD timeframe isn't a particularly palatable option. As package maintainers, I think we have a limited set of options available: 1. Do nothing for now. Maybe upstream figures out something in time to get a fix in for Jessie. Maybe the release team decides to ignore the bug for Jessie. Maybe the release team removes pip for Jessie. 2. Disable root/system use. 3. Make install as --user default and require some suitable named option for root/system install. 4. Install as root by default if permissions allow, but default to --user if not instead of just erroring out. As upstream, do you have a preference if it's not #1? Are there other options that would be better? Scott K -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#771768: antiword: CVE-2014-8123: buffer overflow of of atPPSlist[].szName[]
On Tue, Dec 02, 2014 at 08:35:40AM +0100, Salvatore Bonaccorso wrote: the following vulnerability was published for antiword. CVE-2014-8123[0]: buffer overflow of atPPSlist[].szName[] We're actually already carrying a patch to address this buffer overflow - 10_fix_buffer_overflow_wordole_c.dpatch, added in 0.37-5 back in June 2009: http://sources.debian.net/src/antiword/0.37-10/debian/patches/10_fix_buffer_overflow_wordole_c.patch/ Reported in: https://bugs.debian.org/407015 I'm not going to just close this though, as the check in our patch is but the new patch uses =. I'll dig into if the equality condition results in an overflow, but the scope for exploiting this in Debian is going to be rather more limited than in upstream 0.37. Cheers, Olly -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#771794: pip silently removes/updates system provided python packages
I'm on my phone so forgive my formatting. 4, 3, 2 I think in order of best to worst in my opinion. I have another question. If we fix this in the upcoming pip 6 release what is the chances of getting an exception for pip 6 in the freeze? If I can solve the problem in pip proper and keep the delta between different platforms smaller I can juggle around priorities and push the other big ticket thing I was working on till another release. I have more questions regarding what a good upstream solution looks like but I'll touch on those when I'm back at my desk. On Dec 2, 2014, at 3:41 PM, Scott Kitterman deb...@kitterman.com wrote: On Tuesday, December 02, 2014 12:37:40 PM Donald Stufft wrote: On Dec 2, 2014, at 12:25 PM, Daniel Kahn Gillmor d...@fifthhorseman.net wrote: On 12/02/2014 11:51 AM, Donald Stufft wrote: I'd very much prefer it if you didn't do this. This *is* going to break things for people and it's going to cause a bunch of confusion. It's not clear to me which side you're arguing for. can you clarify which action is going to break things for people and cause a bunch of confusion? If pip silently removes/updates system-provided python packages, that is likely to break things and cause a bunch of confusion, no? alternately, if pip verbosely refuses to run as uid 0, that's at least a non-silent failure. (though it certainly will break things and frustrate some people) --dkg I’m saying don’t make the change. There are major software systems that rely on the ability to install things as root using pip. Chef, puppet, etc. It’s also going to cause a bunch of confusion because all of a sudden pip is going to have a vastly different behavior if it’s running on Debian vs if it’s running somewhere else. That’s going to blow back on us (the pip maintainers) as we get bug reports from people who assume we broke their use cases for pip. We (pip maintainers) recognize this can cause issues and we’d like to arrive a solution that solves this issue without introducing major divergence between various platforms and with respect towards the use cases that need or require that ability. It’s somewhat of a thorny problems to do it correctly, we’re a fairly small team with limited time, and we have bigger issues of concern that have taken a front seat. In the meantime, we have a release to get out the door, so wait for upstream to figure it out in TBD timeframe isn't a particularly palatable option. As package maintainers, I think we have a limited set of options available: 1. Do nothing for now. Maybe upstream figures out something in time to get a fix in for Jessie. Maybe the release team decides to ignore the bug for Jessie. Maybe the release team removes pip for Jessie. 2. Disable root/system use. 3. Make install as --user default and require some suitable named option for root/system install. 4. Install as root by default if permissions allow, but default to --user if not instead of just erroring out. As upstream, do you have a preference if it's not #1? Are there other options that would be better? Scott K -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#770412: marked as done (grub-xen: fails to install in a chroot)
Your message dated Tue, 02 Dec 2014 21:19:39 + with message-id e1xvurd-0002oh...@franck.debian.org and subject line Bug#770412: fixed in grub2 2.02~beta2-17 has caused the Debian Bug report #770412, regarding grub-xen: fails to install in a chroot to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 770412: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=770412 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: grub-xen Version: 2.02~beta2-16 Severity: serious User: debian...@lists.debian.org Usertags: piuparts Hi, during a test with piuparts I noticed your package failed to install. As per definition of the release team this makes the package too buggy for a release, thus the severity. From the attached log (scroll to the bottom...): Selecting previously unselected package grub-xen. (Reading database ... 8098 files and directories currently installed.) Preparing to unpack .../grub-xen_2.02~beta2-16_amd64.deb ... Unpacking grub-xen (2.02~beta2-16) ... Setting up grub-xen (2.02~beta2-16) ... Creating config file /etc/default/grub with new version Installing for x86_64-xen platform. grub-install: error: cannot find a device for /boot/grub (is /dev mounted?). dpkg: error processing package grub-xen (--configure): subprocess installed post-installation script returned error exit status 1 Errors were encountered while processing: grub-xen cheers, Andreas grub-xen_2.02~beta2-16.log.gz Description: application/gzip ---End Message--- ---BeginMessage--- Source: grub2 Source-Version: 2.02~beta2-17 We believe that the bug you reported is fixed in the latest version of grub2, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 770...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Ian Campbell i...@debian.org (supplier of updated grub2 package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Sun, 30 Nov 2014 17:15:21 + Source: grub2 Binary: grub2 grub-linuxbios grub-efi grub-common grub2-common grub-emu grub-emu-dbg grub-pc-bin grub-pc-dbg grub-pc grub-rescue-pc grub-coreboot-bin grub-coreboot-dbg grub-coreboot grub-efi-ia32-bin grub-efi-ia32-dbg grub-efi-ia32 grub-efi-amd64-bin grub-efi-amd64-dbg grub-efi-amd64 grub-efi-ia64-bin grub-efi-ia64-dbg grub-efi-ia64 grub-efi-arm-bin grub-efi-arm-dbg grub-efi-arm grub-efi-arm64-bin grub-efi-arm64-dbg grub-efi-arm64 grub-ieee1275-bin grub-ieee1275-dbg grub-ieee1275 grub-firmware-qemu grub-uboot-bin grub-uboot-dbg grub-uboot grub-xen-bin grub-xen-dbg grub-xen grub-xen-host grub-yeeloong-bin grub-yeeloong-dbg grub-yeeloong grub-theme-starfield grub-mount-udeb Architecture: source Version: 2.02~beta2-17 Distribution: unstable Urgency: medium Maintainer: GRUB Maintainers pkg-grub-de...@lists.alioth.debian.org Changed-By: Ian Campbell i...@debian.org Description: grub-common - GRand Unified Bootloader (common files) grub-coreboot - GRand Unified Bootloader, version 2 (Coreboot version) grub-coreboot-bin - GRand Unified Bootloader, version 2 (Coreboot binaries) grub-coreboot-dbg - GRand Unified Bootloader, version 2 (Coreboot debug files) grub-efi - GRand Unified Bootloader, version 2 (dummy package) grub-efi-amd64 - GRand Unified Bootloader, version 2 (EFI-AMD64 version) grub-efi-amd64-bin - GRand Unified Bootloader, version 2 (EFI-AMD64 binaries) grub-efi-amd64-dbg - GRand Unified Bootloader, version 2 (EFI-AMD64 debug files) grub-efi-arm - GRand Unified Bootloader, version 2 (ARM UEFI version) grub-efi-arm-bin - GRand Unified Bootloader, version 2 (ARM UEFI binaries) grub-efi-arm-dbg - GRand Unified Bootloader, version 2 (ARM UEFI debug files) grub-efi-arm64 - GRand Unified Bootloader, version 2 (ARM64 UEFI version) grub-efi-arm64-bin - GRand Unified Bootloader, version 2 (ARM64 UEFI binaries) grub-efi-arm64-dbg - GRand Unified Bootloader, version 2 (ARM64 UEFI debug files) grub-efi-ia32 - GRand Unified Bootloader, version 2 (EFI-IA32 version) grub-efi-ia32-bin - GRand Unified Bootloader, version 2 (EFI-IA32 binaries) grub-efi-ia32-dbg - GRand Unified Bootloader, version 2 (EFI-IA32 debug files)
Bug#771852: package not installable due to postinst syntax error
Package: mdadm Version: 3.3.2-3 Severity: serious Tags: patch Hi Installing mdadm 3.3.2-3 fails with the following error Setting up mdadm (3.3.2-3) ... W: mdadm: failed to load MD subsystem. Generating mdadm.conf... done (failed to scan arrays; /proc probably not mounted). rm: unrecognized option '--ignore-fail-on-non-empty' Try 'rm --help' for more information. dpkg: error processing package mdadm (--configure): subprocess installed post-installation script returned error exit status 1 as rm(1) doesn't support --ignore-fail-on-non-empty as parameter. However simply switching this to rmdir --ignore-fail-on-non-empty is not successful either, as /var/lib/mdadm doesn't exist on systems where mdadm hasn't been installed before (and rmdir --ignore-fail-on-non-empty does exit with an error code, if the directoy which it is supposed to remove doesn't exist). There are two alternatives to fix this, either by ignoring all bugs from rmdir, e.g. rmdir --ignore-fail-on-non-empty /var/lib/mdadm || : or by checking if the directory in question exists beforehand. --- mdadm-3.3.2/debian/mdadm.postinst +++ mdadm-3.3.2/debian/mdadm.postinst @@ -100,7 +100,9 @@ if dpkg --compare-versions $2 le 3.3.2-1; then rm -f /var/lib/mdadm/CONF-UNCHECKED /var/lib/mdadm/mdadm.conf-generated - rm --ignore-fail-on-non-empty /var/lib/mdadm + if [ -d /var/lib/mdadm ]; then +rmdir --ignore-fail-on-non-empty /var/lib/mdadm + fi fi ;; esac Regards Stefan Lippers-Hollmann -- System Information: Debian Release: 8.0 APT prefers unstable APT policy: (500, 'unstable') Architecture: amd64 (x86_64) Kernel: Linux 3.18.0-rc7-aptosid-amd64 (SMP w/8 CPU cores; PREEMPT) Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash signature.asc Description: This is a digitally signed message part.
Bug#767367: nvidia-opencl-icd dependencies
what would happen to an Nvidia-hardware-only system with nvidia kernel module (which blacklists the nouveau kernel module) + nouveau graphics userspace, which under [nvidia-kernel-dkms Recommends: nvidia-driver | libcuda1] would be the result of trying to install OpenCL on a previously nouveau-using system. Did you test this (i.e. apt-get install nvidia-opencl-icd libcuda1 with Nvidia hardware but no already-installed *nvidia* packages)? https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=751082#27 suggests the result is no graphics. (Having it be a Recommends: nvidia-driver rather than a hard Depends already allows the headless GPGPU case, and cutting nvidia-opencl-icd - libcuda1 is enough to fix the original accidental nvidia-opencl-icd on inappropriate hardware problem.) -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#771794: pip silently removes/updates system provided python packages
On Tuesday, December 02, 2014 04:15:05 PM Donald Stufft wrote: ... I have another question. If we fix this in the upcoming pip 6 release what is the chances of getting an exception for pip 6 in the freeze? If I can solve the problem in pip proper and keep the delta between different platforms smaller I can juggle around priorities and push the other big ticket thing I was working on till another release. ... The deadline for getting Important (i.e. not Serious/Grave/Critical) bug fixes unblocked for Jessie is December 5th (that's uploaded to Debian and the release team has reviewed and unblocked it). Unless the next release is ~nothing but fixes for important/release critical bugs, the chance is approximately zero. Scott K -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#750521: acknowledgement of reception of RC bug report in scim from Debian maintainer
Control: tags 750521 + upstream Control: forwarded 750521 https://bugs.g10code.com/gnupg/issue1777 Hi Rolf-- On 12/02/2014 12:26 PM, Rolf Leggewie wrote: Control: reassign -1 pinentry-gtk2 On 03.12.2014 01:14, Rolf Leggewie wrote: yep, i think this report is specifically about something broken in the interaction between pinentry-gtk2 and scim. Yep, and it turns out to be a VERY old problem indeed (still reading up on it). It's from at least 2007 or most likely even 2006! http://thread.gmane.org/gmane.comp.encryption.gpg.devel/14423 https://bugzilla.novell.com/show_bug.cgi?id=330073 The people at Novell came to the conclusion that the problem needs to be fixed in upstream pinentry-gtk-2. After reading through the gnupg-devel mailing list over on gmane.org, specifically http://thread.gmane.org/gmane.comp.encryption.gpg.devel/14423/focus=14461 I am reassigning this back to the pinentry package. That thread has some indication that some work was done upstream but there is also an entry from 2009 indicating the problem is still present and that mail never received a response. Thanks for doing the background research for this and reporting it here. I agree with the reassignment to pinentry-gtk2, and i've forwarded the message to the upstream bugtracker. Regards, --dkg signature.asc Description: OpenPGP digital signature
Processed: Re: acknowledgement of reception of RC bug report in scim from Debian maintainer
Processing control commands: tags 750521 + upstream Bug #750521 [pinentry-gtk2] scim-gtk-immodule breaks pinentry-gtk2 and impairs gnome-keyring Added tag(s) upstream. forwarded 750521 https://bugs.g10code.com/gnupg/issue1777 Bug #750521 [pinentry-gtk2] scim-gtk-immodule breaks pinentry-gtk2 and impairs gnome-keyring Set Bug forwarded-to-address to 'https://bugs.g10code.com/gnupg/issue1777'. -- 750521: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=750521 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#771768: marked as done (antiword: CVE-2014-8123: buffer overflow of of atPPSlist[].szName[] )
Your message dated Tue, 2 Dec 2014 21:51:19 + with message-id 20141202215119.ga17...@survex.com and subject line Re: Bug#771768: antiword: CVE-2014-8123: buffer overflow of of atPPSlist[].szName[] has caused the Debian Bug report #771768, regarding antiword: CVE-2014-8123: buffer overflow of of atPPSlist[].szName[] to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 771768: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=771768 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Source: antiword Version: 0.37-6 Severity: grave Tags: security upstream patch Hi, the following vulnerability was published for antiword. CVE-2014-8123[0]: buffer overflow of atPPSlist[].szName[] If you fix the vulnerability please also make sure to include the CVE (Common Vulnerabilities Exposures) id in your changelog entry. For further information see: [0] https://security-tracker.debian.org/tracker/CVE-2014-8123 [1] https://bugzilla.redhat.com/show_bug.cgi?id=1169665 [2] http://seclists.org/oss-sec/2014/q4/870 Regards, Salvatore ---End Message--- ---BeginMessage--- Control: notfound -1 0.37-6 Control: found -1 0.37-1 Control: fixed -1 0.37-5 On Tue, Dec 02, 2014 at 08:59:28PM +, Olly Betts wrote: On Tue, Dec 02, 2014 at 08:35:40AM +0100, Salvatore Bonaccorso wrote: the following vulnerability was published for antiword. CVE-2014-8123[0]: buffer overflow of atPPSlist[].szName[] We're actually already carrying a patch to address this buffer overflow - 10_fix_buffer_overflow_wordole_c.dpatch, added in 0.37-5 back in June 2009: http://sources.debian.net/src/antiword/0.37-10/debian/patches/10_fix_buffer_overflow_wordole_c.patch/ Reported in: https://bugs.debian.org/407015 I'm not going to just close this though, as the check in our patch is but the new patch uses =. I'll dig into if the equality condition results in an overflow, but the scope for exploiting this in Debian is going to be rather more limited than in upstream 0.37. OK, reviewing the code, the check we already have is fine - in fact the new patch's check is one character too strict (but in a safe way). Oldstable has 0.37-6, so this is already fixed in all supported Debian versions. I pinged carnil on IRC, and he said to just close if the patch we have is enough. Cheers, Olly---End Message---
Bug#771794: pip silently removes/updates system provided python packages
On Dec 2, 2014, at 4:47 PM, Scott Kitterman deb...@kitterman.com wrote: On Tuesday, December 02, 2014 04:15:05 PM Donald Stufft wrote: ... I have another question. If we fix this in the upcoming pip 6 release what is the chances of getting an exception for pip 6 in the freeze? If I can solve the problem in pip proper and keep the delta between different platforms smaller I can juggle around priorities and push the other big ticket thing I was working on till another release. ... The deadline for getting Important (i.e. not Serious/Grave/Critical) bug fixes unblocked for Jessie is December 5th (that's uploaded to Debian and the release team has reviewed and unblocked it). Unless the next release is ~nothing but fixes for important/release critical bugs, the chance is approximately zero. Scott K This bug is marked “Serious” right? So if I understand correctly a new version isn’t acceptable, even to fix a Serious issue, unless it only fixes items that are allowed within whatever phase the release process is in? --- Donald Stufft PGP: 7C6B 7C5D 5E2B 6356 A926 F04F 6E3C BCE9 3372 DCFA -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed: notfound 771768 in 0.37-6, found 771768 in 0.37-1, fixed 771768 in 0.37-5
Processing commands for cont...@bugs.debian.org:
notfound 771768 0.37-6
Bug #771768 {Done: Olly Betts o...@survex.com} [src:antiword] antiword:
CVE-2014-8123: buffer overflow of of atPPSlist[].szName[]
No longer marked as found in versions antiword/0.37-6.
found 771768 0.37-1
Bug #771768 {Done: Olly Betts o...@survex.com} [src:antiword] antiword:
CVE-2014-8123: buffer overflow of of atPPSlist[].szName[]
Marked as found in versions antiword/0.37-1 and reopened.
fixed 771768 0.37-5
Bug #771768 [src:antiword] antiword: CVE-2014-8123: buffer overflow of of
atPPSlist[].szName[]
Marked as fixed in versions antiword/0.37-5.
thanks
Stopping processing here.
Please contact me if you need assistance.
--
771768: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=771768
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#771794: pip silently removes/updates system provided python packages
On Tuesday, December 02, 2014 04:54:37 PM Donald Stufft wrote: On Dec 2, 2014, at 4:47 PM, Scott Kitterman deb...@kitterman.com wrote: On Tuesday, December 02, 2014 04:15:05 PM Donald Stufft wrote: ... I have another question. If we fix this in the upcoming pip 6 release what is the chances of getting an exception for pip 6 in the freeze? If I can solve the problem in pip proper and keep the delta between different platforms smaller I can juggle around priorities and push the other big ticket thing I was working on till another release. ... The deadline for getting Important (i.e. not Serious/Grave/Critical) bug fixes unblocked for Jessie is December 5th (that's uploaded to Debian and the release team has reviewed and unblocked it). Unless the next release is ~nothing but fixes for important/release critical bugs, the chance is approximately zero. Scott K This bug is marked “Serious” right? So if I understand correctly a new version isn’t acceptable, even to fix a Serious issue, unless it only fixes items that are allowed within whatever phase the release process is in? A new release would be acceptable if it only fixed release critical stuff. The problem comes in where a new release fixes something serious and other stuff. Scott K -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed: closing 771768
Processing commands for cont...@bugs.debian.org: # Re-close, was re-opened by correcting found version close 771768 Bug #771768 [src:antiword] antiword: CVE-2014-8123: buffer overflow of of atPPSlist[].szName[] Marked Bug as done thanks Stopping processing here. Please contact me if you need assistance. -- 771768: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=771768 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#767564: marked as done (libblitz-doc: fails to upgrade from 'testing' - trying to overwrite /usr/share/info/blitz.info.gz)
Your message dated Tue, 02 Dec 2014 22:03:50 + with message-id e1xvvxy-eo...@franck.debian.org and subject line Bug#767564: fixed in blitz++ 1:0.10-3.2 has caused the Debian Bug report #767564, regarding libblitz-doc: fails to upgrade from 'testing' - trying to overwrite /usr/share/info/blitz.info.gz to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 767564: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=767564 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: libblitz-doc Version: 1:0.10-2 Severity: serious User: debian...@lists.debian.org Usertags: piuparts Hi, during a test with piuparts I noticed your package fails to upgrade from 'testing'. It installed fine in 'testing', then the upgrade to 'sid' fails because it tries to overwrite other packages files without declaring a Breaks+Replaces relation. See policy 7.6 at http://www.debian.org/doc/debian-policy/ch-relationships.html#s-replaces From the attached log (scroll to the bottom...): Selecting previously unselected package libblitz-doc. Preparing to unpack .../libblitz-doc_1%3a0.10-2_all.deb ... Unpacking libblitz-doc (1:0.10-2) ... dpkg: error processing archive /var/cache/apt/archives/libblitz-doc_1%3a0.10-2_all.deb (--unpack): trying to overwrite '/usr/share/info/blitz.info.gz', which is also in package libblitz0ldbl 1:0.10-1 dpkg-deb: error: subprocess paste was killed by signal (Broken pipe) Errors were encountered while processing: /var/cache/apt/archives/libblitz-doc_1%3a0.10-2_all.deb cheers, Andreas libblitz0ldbl=1%0.10-1_libblitz-doc=1%0.10-2.log.gz Description: application/gzip ---End Message--- ---BeginMessage--- Source: blitz++ Source-Version: 1:0.10-3.2 We believe that the bug you reported is fixed in the latest version of blitz++, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 767...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Jonathan Wiltshire j...@debian.org (supplier of updated blitz++ package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.8 Date: Tue, 02 Dec 2014 21:37:08 + Source: blitz++ Binary: libblitz0ldbl libblitz0-dev libblitz-doc Architecture: source all Version: 1:0.10-3.2 Distribution: unstable Urgency: medium Maintainer: Debian Science Team debian-science-maintain...@lists.alioth.debian.org Changed-By: Jonathan Wiltshire j...@debian.org Description: libblitz-doc - C++ template class library for scientific computing libblitz0-dev - C++ template class library for scientific computing libblitz0ldbl - C++ template class library for scientific computing Closes: 767564 Changes: blitz++ (1:0.10-3.2) unstable; urgency=medium . * Non-maintainer upload. * Add missing epoch to conflicts/replaces versions (really Closes: #767564) Checksums-Sha1: 7ebced68b148a24a82db07f925e0eff285d91b0d 2290 blitz++_0.10-3.2.dsc 9f650a814eb5f4e4aca59cecec294c42c97f5f88 15368 blitz++_0.10-3.2.debian.tar.xz f40f95bca074223eaf6fc13c8513828418278c8d 876624 libblitz-doc_0.10-3.2_all.deb Checksums-Sha256: bc598b559a01808c046cc00d4bcb38c7cf0c5ffcf50088b599d589cb3631aa58 2290 blitz++_0.10-3.2.dsc 550d1378ce408b41f8151e9e32ba00bbdc224f56caab1cb218e4e0a11c943a78 15368 blitz++_0.10-3.2.debian.tar.xz 26e3a72a4d2a35ab760a2a5400fda8f101d778d9cbeb761eece41f810f6351b2 876624 libblitz-doc_0.10-3.2_all.deb Files: df7b8e30dcd4c2c58bb0b33a3dd4af40 2290 devel optional blitz++_0.10-3.2.dsc eb3dbbe55d47868d27ac17894870ea89 15368 devel optional blitz++_0.10-3.2.debian.tar.xz c5f6317499043867031cafdace22041e 876624 doc optional libblitz-doc_0.10-3.2_all.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1 iQIcBAEBAgAGBQJUfjUkAAoJEFC7AtTIpr9hYsMP/j8vp6dFZOeawXt8yN1XRoZt BVJuyC2OkTZvXI+NHIskXiUvvlBMcN1MI4mo7pTaqfaOmj9O3sMP0xBj7NJqDvMS qYfuR2BsF4OXWQhu77tdDpVE0Hvpa+TTYKxZzccgz+Spi06xgYFkXmijxWT+6gDc 6Ed5ZAZV/GQCW+tlNnMuwJUgwQhDbHjFT3VhOuYmmlNLM2z8NZYx8KIG7Xo5fkBt 9T8wiiKItoyhN2fwNdCcGbMNc1R0T6JWS2r6mEUaunRVmey8iFwxiC/AYj7zmXSr L3zZK2t7l8oW3Lq5K2GFfzkSsjHetyTrxcZi9qKEIj7bJlsOiPb4Jcco97m0f+lZ h1+DG+X0qP3FhqaCJvROkGdmSNBmdLlddYuAqI1GlNfrYaPwZMvuAEGESI/FNAah
Processed: retitle 771768 to antiword: CVE-2014-8123: buffer overflow of atPPSlist[].szName[]
Processing commands for cont...@bugs.debian.org:
retitle 771768 antiword: CVE-2014-8123: buffer overflow of
atPPSlist[].szName[]
Bug #771768 {Done: Olly Betts o...@survex.com} [src:antiword] antiword:
CVE-2014-8123: buffer overflow of of atPPSlist[].szName[]
Changed Bug title to 'antiword: CVE-2014-8123: buffer overflow of
atPPSlist[].szName[]' from 'antiword: CVE-2014-8123: buffer overflow of of
atPPSlist[].szName[] '
thanks
Stopping processing here.
Please contact me if you need assistance.
--
771768: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=771768
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#771794: pip silently removes/updates system provided python packages
On Dec 2, 2014, at 5:03 PM, Scott Kitterman deb...@kitterman.com wrote: On Tuesday, December 02, 2014 04:54:37 PM Donald Stufft wrote: On Dec 2, 2014, at 4:47 PM, Scott Kitterman deb...@kitterman.com wrote: On Tuesday, December 02, 2014 04:15:05 PM Donald Stufft wrote: ... I have another question. If we fix this in the upcoming pip 6 release what is the chances of getting an exception for pip 6 in the freeze? If I can solve the problem in pip proper and keep the delta between different platforms smaller I can juggle around priorities and push the other big ticket thing I was working on till another release. ... The deadline for getting Important (i.e. not Serious/Grave/Critical) bug fixes unblocked for Jessie is December 5th (that's uploaded to Debian and the release team has reviewed and unblocked it). Unless the next release is ~nothing but fixes for important/release critical bugs, the chance is approximately zero. Scott K This bug is marked “Serious” right? So if I understand correctly a new version isn’t acceptable, even to fix a Serious issue, unless it only fixes items that are allowed within whatever phase the release process is in? A new release would be acceptable if it only fixed release critical stuff. The problem comes in where a new release fixes something serious and other stuff. Scott K Ok, so anything from upstream will need to be backported to 1.5.x then, which might be a pain but I don’t think undoable. We reorganized some stuff but it shouldn’t be impossible. Would a patch for this issue need to be done and uploaded and unblocked by the Dec 5th? Or Since it’s a “Serious” issue is there a longer deadline? What’s the chances of accepting the status quo for Jessie and having an upstream fix in Jessie+1? This isn’t a *new* problem, it exists in stable and oldstable as well and it wasn’t unknown to be a problem previously (there’s another ticket about making —user the default in BTS which references this fact over a year ago). I’m not sure what would make it all of a sudden a dire problem in Jesse, so if we can wait till Jesse+1 and I can get a stakeholder to sit down with me and sort out what a solution *needs* from the Debian side of things I can make sure a fix does land in the next pip release which will be out far in advance of Jessie+1. --- Donald Stufft PGP: 7C6B 7C5D 5E2B 6356 A926 F04F 6E3C BCE9 3372 DCFA -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#771126: Bug#771191: Bug#771126: libav/tests/lena.pnm: also not mentioned in debian/copyright
Le 2 déc. 2014 14:15, Reinhard Tartler siret...@gmail.com a écrit : On Fri, Nov 28, 2014 at 1:34 AM, Niels Thykier ni...@thykier.net wrote: Control: tags -1 -wheezy-ignore On 2014-11-27 23:23, Jonas Smedegaard wrote: Quoting Niels Thykier (2014-11-27 22:14:25) [...] In prior similar bugreport https://bugs.debian.org/760171#10 - referenced from https://bugs.debian.org/771191#10 - distribution is documented as permitted only for research and education which I interpret as unacceptable for Debian. [...] - Jonas FTR, this whole business feel incredibly silly. lena.pnm has become the *de-facto* standard image for every CS student to do his graphics courses homework on, and is generally considered to public domain, And offencive (sexist) for 50% of the population the women... Bastien even without proper documentation. The copyright holder is going to have a very hard time enforcing his right if he wanted to prevent distribution of the image, in particular the low-quality scan that is being used in the Libav source package. Also, even according to https://en.wikipedia.org/wiki/File:Lenna.png#Licensing, the holder is not interested in that to begin with. - I mean, really, don't we have more important things to do? Nevertheless, lena.pnm lacks proper licensing and some argue it violates the DFSG, so I've taken the effort (and ridicule!) to replace lena.pnm upstream with a new image reference.pnm, which I have personally taken this summer and upon Jonas' suggestion provide it under the expat license. This required to update all test reference patterns, which took most of the effort and is basically not verifiable. Jonas, would you mind taking over from here and upload https://libav.org/releases/libav-11.1.tar.xz to unstable? Otherwise I can see if I can get to that this weekend. Regarding stable: I've backported this change back to release/0.8 upstream. In the past, the security team has accepted libav point releases in wheezy-security, and I trust that this is also an acceptable change. It will be part of the next upload to stable-security. (this may take some more weeks, as libav has been notified about a couple of more CVEs, which need to be tested, fixed and verified, which is incredibly laborsome to do correctly). Does this plan work for everyone? -- regards, Reinhard
Processed: severity postgres
Processing commands for cont...@bugs.debian.org: severity 770941 wishlist Bug #770941 [nova-common] nova-common - Overrides database config in nova.conf Severity set to 'wishlist' from 'serious' severity 770944 wishlist Bug #770944 [neutron-common] Overrides database config in nova.conf Severity set to 'wishlist' from 'serious' End of message, stopping processing here. Please contact me if you need assistance. -- 770941: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=770941 770944: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=770944 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#771647: marked as done (libphobos-4.9-dev and libphobos-4.8-dev: error when trying to install together)
- Runtime library for GNU Objective-C applications (x32 debug symbo libx32quadmath0 - GCC Quad-Precision Math Library (x32) libx32quadmath0-dbg - GCC Quad-Precision Math Library (x32 debug symbols) libx32stdc++-4.9-dev - GNU Standard C++ Library v3 (development files) libx32stdc++6 - GNU Standard C++ Library v3 (x32) libx32stdc++6-4.9-dbg - GNU Standard C++ Library v3 (debugging files) libx32ubsan0 - UBSan -- undefined behaviour sanitizer (x32) libx32ubsan0-dbg - UBSan -- undefined behaviour sanitizer (x32 debug symbols) Closes: 770843 771647 771654 Changes: gcc-4.9 (4.9.2-5) unstable; urgency=medium . * Update to SVN 20141202 (r218271) from the gcc-4_9-branch. - Fix PR middle-end/64111 (ice), PR ipa/63551 (wrong code). PR libstdc++/64102 (closes: #770843), PR target/64115 (powerpc). * Move libphobos2.a into the gcc_lib_dir. Closes: #771647. * Fix typo in last powerpcspe patch. Closes: #771654. Checksums-Sha1: e8dfed0bd4887520a7f54de69aa60d4d79a1a405 18578 gcc-4.9_4.9.2-5.dsc 2818bce8a8a8deddbcfca65a3307abad0dc42a49 815734 gcc-4.9_4.9.2-5.diff.gz 9c35e9d353eaaa457ba0dbe3d5cc22fa9c7e1aeb 74263496 gcc-4.9-source_4.9.2-5_all.deb 65a500b9f43f364272e6d5786c2fab8061af8b12 10349114 gcj-4.9-jre-lib_4.9.2-5_all.deb 674f4594a04b403a9d6a04ff29521e5814b03b95 11661592 gcj-4.9-source_4.9.2-5_all.deb b8e6a05383146685f3fec28a3b1fa0d454e411d5 18873500 libgcj-doc_4.9.2-5_all.deb ae3be66c3535455599a8da810276ff2d0b1c0178 8050176 libstdc++-4.9-doc_4.9.2-5_all.deb b53ee012d911953736bdcbdb43a61de30d7eab42 1443908 gcc-4.9-locales_4.9.2-5_all.deb feae279292a356aa45b80be5beee498c07b1ecb4 159090 gcc-4.9-base_4.9.2-5_amd64.deb e2c3782a8749cef9d8a399a06f689d9418bcb65e 39472 libgcc1_4.9.2-5_amd64.deb b664b84cb6fbc34b927efc8ac260e3002be0 85402 libgcc1-dbg_4.9.2-5_amd64.deb 02479316a70debeb9056518efe1f71ecd353c08b 2066900 libgcc-4.9-dev_4.9.2-5_amd64.deb 59f12ca2ccb5eb81b8a0aa940e87959db490909f 47936 lib32gcc1_4.9.2-5_amd64.deb bef05a0cb666a89dae81f2d52ac85f8da606a6bf 84388 lib32gcc1-dbg_4.9.2-5_amd64.deb 46114f632992259a89cd8dcadd23d0e2de6e4121 1913526 lib32gcc-4.9-dev_4.9.2-5_amd64.deb 0859123df9f25d35bcb38a41c88fe32117a0c4c4 38662 libx32gcc1_4.9.2-5_amd64.deb 13a1deff5fcf0663148fc3c3f1b9a42826422d07 83210 libx32gcc1-dbg_4.9.2-5_amd64.deb 95450dfcba52682947b9b047136fe8380939ea6d 1777660 libx32gcc-4.9-dev_4.9.2-5_amd64.deb f52f53325d7565bea0913a0e56bf86faa4404d0c 129088 libquadmath0_4.9.2-5_amd64.deb e5d1d6d50c99c0943c2cc8375c842a1cb4430aad 146590 libquadmath0-dbg_4.9.2-5_amd64.deb df4552623f6168fd130f3a6dec6ba3365846b561 193288 lib32quadmath0_4.9.2-5_amd64.deb ca13d91eabe78c260743410ed12e4d4509425c2c 154124 lib32quadmath0-dbg_4.9.2-5_amd64.deb a1b7cd06ce7c34185daa071a695c8c8d2053257d 131840 libx32quadmath0_4.9.2-5_amd64.deb f4e1a03f3a419c68ebcda22cbc2a82670c3395fe 149660 libx32quadmath0-dbg_4.9.2-5_amd64.deb 5da876c2ab68ef7ee89dfbd3ca523d6951417f40 37818 libgomp1_4.9.2-5_amd64.deb d39bc6708c84031ba6affda9569d2e67552a58bd 86400 libgomp1-dbg_4.9.2-5_amd64.deb 7dd679d942baddbaa4b5188ea8ed02cb874256c2 40398 lib32gomp1_4.9.2-5_amd64.deb 45b31dd433449882eabca867935479f700f433e9 84492 lib32gomp1-dbg_4.9.2-5_amd64.deb e5479d84eb020c7c34bc906d7a68658b56d8fcd9 36956 libx32gomp1_4.9.2-5_amd64.deb 62fc55bd4d84508b1c0daebea7ce8e10afca1f3b 84112 libx32gomp1-dbg_4.9.2-5_amd64.deb 938ff953d12e9f4ab6ee4f406a2cb0f3ee659ac8 29226 libitm1_4.9.2-5_amd64.deb 255996b75eb793cdbee3cfa7e963b8cb02ee7005 191260 libitm1-dbg_4.9.2-5_amd64.deb 57205aba42994ffc31eb7c37e2f9b9a80d8745f9 31294 lib32itm1_4.9.2-5_amd64.deb efe007bfd794d2dc66bfb61e539b9262fa6be0c2 183346 lib32itm1-dbg_4.9.2-5_amd64.deb b0a0d62e105c0fd371ddc0ddb71a460d407890ba 28708 libx32itm1_4.9.2-5_amd64.deb f15143609109a1ed3562b4d730a268905b3c36b1 181188 libx32itm1-dbg_4.9.2-5_amd64.deb 6fa074a95ac536f924ff0103f2eac3ed6b245a39 9002 libatomic1_4.9.2-5_amd64.deb b172bd530e62fd68fe6fc9ec783d2b9b4f982bf3 16054 libatomic1-dbg_4.9.2-5_amd64.deb fdcd3f3e31500edd40431cab2e9b585a2dffd5eb 8612 lib32atomic1_4.9.2-5_amd64.deb 3967e8ab25d78d7fe2c298b28d0c8644d9d36ac4 13462 lib32atomic1-dbg_4.9.2-5_amd64.deb 1d6f09ba4addda3fe6be2c7411acd960eb5b38f1 8986 libx32atomic1_4.9.2-5_amd64.deb 4ccd59f3377044cd897b02d6b5ea6b92799df0b6 15560 libx32atomic1-dbg_4.9.2-5_amd64.deb 0148699f1fd838d1bd8a0ece7f4f8ca212498453 5164474 cpp-4.9_4.9.2-5_amd64.deb 979320467294b6917af3916532edbbb9cff81708 58026 fixincludes_4.9.2-5_amd64.deb c0040210669167c1c46c2f5b822f4de75cab8aae 972 gobjc++-4.9-multilib_4.9.2-5_amd64.deb 83a745aba1dbe4e6656d1b865136335790256ee6 5400462 gobjc++-4.9_4.9.2-5_amd64.deb e8f0954ee11acb2a4149d7047e2a8c0980193935 978 gobjc-4.9-multilib_4.9.2-5_amd64.deb 57579325e1dfc7e02c6d212b746b2befe8520cb2 4990508 gobjc-4.9_4.9.2-5_amd64.deb cb29638107dc3a58892c44218835fe7849a9137d 112212 libobjc4_4.9.2-5_amd64.deb 03c00d7b42e30a289dd97ef83cee41acdad27dee 207960 libobjc4-dbg_4.9.2-5_amd64.deb cb7f11cd2b755c802382a9883631752c713bb643
Bug#771794: pip silently removes/updates system provided python packages
On Tuesday, December 02, 2014 05:17:48 PM Donald Stufft wrote: On Dec 2, 2014, at 5:03 PM, Scott Kitterman deb...@kitterman.com wrote: On Tuesday, December 02, 2014 04:54:37 PM Donald Stufft wrote: On Dec 2, 2014, at 4:47 PM, Scott Kitterman deb...@kitterman.com wrote: On Tuesday, December 02, 2014 04:15:05 PM Donald Stufft wrote: ... I have another question. If we fix this in the upcoming pip 6 release what is the chances of getting an exception for pip 6 in the freeze? If I can solve the problem in pip proper and keep the delta between different platforms smaller I can juggle around priorities and push the other big ticket thing I was working on till another release. ... The deadline for getting Important (i.e. not Serious/Grave/Critical) bug fixes unblocked for Jessie is December 5th (that's uploaded to Debian and the release team has reviewed and unblocked it). Unless the next release is ~nothing but fixes for important/release critical bugs, the chance is approximately zero. Scott K This bug is marked “Serious” right? So if I understand correctly a new version isn’t acceptable, even to fix a Serious issue, unless it only fixes items that are allowed within whatever phase the release process is in? A new release would be acceptable if it only fixed release critical stuff. The problem comes in where a new release fixes something serious and other stuff. Scott K Ok, so anything from upstream will need to be backported to 1.5.x then, which might be a pain but I don’t think undoable. We reorganized some stuff but it shouldn’t be impossible. Would a patch for this issue need to be done and uploaded and unblocked by the Dec 5th? Or Since it’s a “Serious” issue is there a longer deadline? What’s the chances of accepting the status quo for Jessie and having an upstream fix in Jessie+1? This isn’t a *new* problem, it exists in stable and oldstable as well and it wasn’t unknown to be a problem previously (there’s another ticket about making —user the default in BTS which references this fact over a year ago). I’m not sure what would make it all of a sudden a dire problem in Jesse, so if we can wait till Jesse+1 and I can get a stakeholder to sit down with me and sort out what a solution *needs* from the Debian side of things I can make sure a fix does land in the next pip release which will be out far in advance of Jessie+1. Assuming the maintainer doesn't decide to downgrade the bug (which I think is unlikely and a number of people would object to, so I think we can ignore it as a possibility), the decision to ignore the bug for Jessie belongs with the release team. If we choose not to fix it (and there's no Non-Maintainer Upload), then they will decide to either remove the package or ignore the bug. Since this particular issue is release critical, the December 5th deadline isn't relevant to a targeted fix just for this issue. Scott K -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#771789: [pcp] Bug#771789: libpcp-pmda-perl: uninstallable on i386: depends on perlapi-5.18.2
Hi Jakub, - Original Message - [...] The following packages have unmet dependencies: libpcp-pmda-perl : Depends: perlapi-5.18.2 but it is not installable E: Unable to correct problems, you have held broken packages. Oh, I have an outdated perl installation here - have upgraded it now, will be fixed by the next upload. Thanks! -- Nathan -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#771461: /var/state/samhain/
On Tue, Dec 02, 2014 at 01:23:13AM +0100, Andrea Claudi wrote: Hi, This patch should fix the problem, moving the non-volatile state for the samhain package to /var/lib/samhain. The patch creates the directory for new installations but it is worth noticing that the /var/state/samhain/ contains valid information that has to be preserved over upgrades (otherwise, the integrity database would be regenerated and not kept). Please, tell me if I need to fix something to make this acceptable. I'm committing your patch to Samhain's GIT but have made some adjustments. I will test upgrades from previous versions and if all goes well I'll upload a new package soon. Regards Javier signature.asc Description: Digital signature
