Bug#767019: xscreensaver: postinst overwrites /etc/X11/app-defaults/XScreenSaver without asking
control: tag -1 -patch + * Non-maintainer upload. + * Remove old cruft in maitainer script, not compliant +with policy of the day: +- xscreensaver.preinst snippet used for lenny-squeeze + transition (move configuration file). +- xscreensaver*.post* snippet used for potato-woody + transition (rm symlink /usr/doc/xscreensaver + and rm symlink + /usr/X11R6/lib/X11/app-defaults/XScreenSaver and + /etc/X11/app-defaults/XScreenSaver + and dpkg-divert stuff) + * Bug fix: postinst overwrites /etc/X11/app-defaults/XScreenSaver +without asking, thanks to Bjørn Mork (Closes: #767019). There are far too many changes not related to the RC bug. The release team will very likely to reject this. See their freeze policy. if [ -L /etc/X11/app-defaults/XScreenSaver ]; then if [ $(readlink /etc/X11/app-defaults/XScreenSaver) = XScreenSaver-nogl -o \ $(readlink /etc/X11/app-defaults/XScreenSaver) = XScreenSaver-gl]; then rm /etc/X11/app-defaults/XScreenSaver fi This doesn't handle the case where the user intentionally had both xscreensaver-gl and xscreensaver installed, and manually set the symlink to XscreenSaver-nogl. Best wishes, Mike -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#773550: autoremoval problem on gnome wheezy to jessie upgrades
Le vendredi 19 décembre 2014 à 20:55 +0100, Holger Levsen a écrit : - the apt-get upgrade step from wheezy to jessie is fine (lots of packages kept back, lots upgraded) - the apt-get dist-upgrade step then removes many packages, from the log: This one looks fine. - then, apt-get dist-upgrade is redone, listing many many candiates for autoremoval and from the log: Most of these candidates look fine to me. They are packages removed from the dependency tree of the “gnome” metapackage in jessie, and there’s nothing wrong with that. Except for libreoffice. Which brings us to the java problems, mostly related to LO as well. dpkg: libdb5.1-java: dependency problems, but removing anyway as you requested: libdb-java depends on libdb5.1-java (= 5.1.25-7~). - and then finally, apt-get autoremove is done, which now removes way too much and fails when it try to remove sudo. (This failure to remove sudo is a feature and not subject of this bug report..) I see. This didnt happen 2 weeks ago, and IMO also shouldn't^must not happen. I've just not really an idea where the bug comes from... This is because nothing in GNOME depends on sudo/gksu anymore. And this was the way sudo was kept in the dependency tree. Given the usefulness of this package, but its absence of relation to GNOME, I think a dependency on sudo should be added to task-desktop. Would it be OK to reassign? Cheers, -- .''`. Josselin Mouette : :' : `. `' `- -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#772217: fixed in cmtk 3.2.2-1.1
On Mon, Dec 15, 2014 at 11:06 PM, Torsten Rohlfing wrote: Thanks from me as well. It seems that your patch is more sophisticated than my upstream fix (which essentially just switches the scripts shebang to /bin/bash). Please let me know if you want me to deploy your patch instead. It would be more convenient since the debian package will have to maintain a difference from upstream if that isn't done. I'll go ahead with the nmu. Best wishes, Mike -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#773578: intel-microcode: Message after updating refers to README.Debian w/o .gz
Package: intel-microcode Version: 1.20140624.1 Severity: minor Dear Maintainer, In the update message: Refer to /usr/share/doc/intel-microcode/README.Debian for details. The file is named README.Debian.gz -- System Information: Debian Release: 7.7 APT prefers proposed-updates APT policy: (500, 'proposed-updates'), (500, 'stable') Architecture: i386 (i686) Kernel: Linux 3.12-0.bpo.1-486 Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash intel-microcode depends on no packages. Versions of packages intel-microcode recommends: ii iucode-tool 0.8.3-2 intel-microcode suggests no packages. -- no debconf information -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#773473: [PATCH] * sm/gpgsm.c: (parse_keyserver_line) return false on 'fail'.
--
If something in the keyserver_line failed, parse_keyserver_line would free
'server', but then return it afterwards, leading to a use-after-free.
sm/gpgsm.c, in the function main() correctly checks whether the return of
parse_keyserver_line is false.
---
sm/gpgsm.c | 1 +
1 file changed, 1 insertion(+)
diff --git a/sm/gpgsm.c b/sm/gpgsm.c
index 3398d17..75c0b4d 100644
--- a/sm/gpgsm.c
+++ b/sm/gpgsm.c
@@ -862,6 +862,7 @@ parse_keyserver_line (char *line,
{
log_info (_(%s:%u: skipping this line\n), filename, lineno);
keyserver_list_free (server);
+ return 0;
}
return server;
--
1.9.1
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#767037: Grub EFI fallback - patches for review
Hi, one option that doesn't seem to have been considered would be to create a separate package (let's call it UEFIx) that installs an UEFI binary to EFI/boot/bootx64.efi. That binary could then do what the UEFI BIOS should've done (i.e. look at the EFI vars for bootorder, bootnext, etc and then go on to load the right bootloader). That way you'll have a solution that'll work across the different bootloaders (grub-efi, gummiboot, etc), requires no changes to existing bootloaders and which will only have an effect if explicitly installed (adding d-i rescue code to optionally install the package should be pretty straightforward as well). It also means that efibootmgr will work as expected on both buggy and non-buggy machines. I realize you're alredy pretty well ahead on a different solution and that it's late in the Jessie game, but I thought I should at least throw this idea into the ring (it's basically what Matthew originally suggested in http://mjg59.dreamwidth.org/4125.html). -- David Härdeman -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#773579: fontypython should be ported to wx 3.0 (yes, again)
Package: fontypython Version: 0.4.4-1.2 Severity: grave When I fixed #765487, I missed #757886, that is, the fact that the transition from 2.8 to 3.0 (of fontypython) had not been spontaneous. As a consequence of this, I assumed Depends were OK, which they are not, and the current package is useless. As a consequence of this (probably), I also missed #755757. (applause) So using wx 2.8 is not an option in jessie, and the original bug must be solved. Olly, in #757886 you state that everything seems to be fine... can you confirm with wxpython3.0 3.0.1.1+dfsg-2 ? -- System Information: Debian Release: 8.0 APT prefers testing APT policy: (650, 'testing'), (600, 'unstable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.16.0-4-amd64 (SMP w/2 CPU cores) Locale: LANG=it_IT.utf8, LC_CTYPE=it_IT.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages fontypython depends on: ii python-imaging 2.6.1-1 ii python-wxgtk3.0 3.0.1.1+dfsg-2 fontypython recommends no packages. fontypython suggests no packages. -- no debconf information -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#772233: bashism in /bin/sh script
Hi, 2014-12-19 22:51 GMT+01:00 Holger Levsen hol...@layer-acht.org: On Freitag, 19. Dezember 2014, Balint Reczey wrote: If you don't have time I would happily prepare an NMU with the fix. Please go ahead. Thanks! I just performed the NMU to DELAYED/2 with the attached patch. Cheers, Balint diff -Nru gnunet-0.10.1/debian/changelog gnunet-0.10.1/debian/changelog --- gnunet-0.10.1/debian/changelog 2014-10-15 21:44:30.0 +0200 +++ gnunet-0.10.1/debian/changelog 2014-12-20 10:00:17.0 +0100 @@ -1,3 +1,12 @@ +gnunet (0.10.1-2.1) unstable; urgency=medium + + * Non-maintainer upload. + + [Raphael Geissert] + * Fix bashisms (Closes: #772233) + + -- Balint Reczey bal...@balintreczey.hu Sat, 20 Dec 2014 09:59:13 +0100 + gnunet (0.10.1-2) unstable; urgency=medium * Put the upstream signing key in debian/upstream/signing-key.asc and remove diff -Nru gnunet-0.10.1/debian/patches/fix-bashism.patch gnunet-0.10.1/debian/patches/fix-bashism.patch --- gnunet-0.10.1/debian/patches/fix-bashism.patch 1970-01-01 01:00:00.0 +0100 +++ gnunet-0.10.1/debian/patches/fix-bashism.patch 2014-12-20 09:59:07.0 +0100 @@ -0,0 +1,54 @@ +Description: fix bashisms +Bug: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=7772233 +Author: Raphael Geissert geiss...@debian.org +Forwarded: https://gnunet.org/bugs/view.php?id=3588 + +Index: gnunet-0.10.1-2/src/gns/gnunet-gns-proxy-setup-ca +=== +--- gnunet-0.10.1-2/src/gns/gnunet-gns-proxy-setup-ca gnunet-0.10.1-2/src/gns/gnunet-gns-proxy-setup-ca +@@ -7,9 +7,9 @@ + options='' + while getopts c: opt; do + case $opt in + c) ++ options=$options -c $OPTARG +- options+=-c $OPTARG + ;; + \?) + echo Invalid option: -$OPTARG 2 + exit 1 +@@ -38,16 +38,16 @@ + for f in ~/.mozilla/firefox/*.default + do + if [ -d $f ]; then + echo Importing CA info Firefox $f ++certutil -D -n GNS Proxy CA -d ~/.mozilla/firefox/*.default /dev/null 21 +-certutil -D -n GNS Proxy CA -d ~/.mozilla/firefox/*.default /dev/null 21 + certutil -A -n GNS Proxy CA -t CT,, -d ~/.mozilla/firefox/*.default $GNSCERT + fi + done + + if [ -d ~/.pki/nssdb ]; then + echo Importing CA into Chrome ++ certutil -D -n GNS Proxy CA -d ~/.pki/nssdb /dev/null 21 +- certutil -D -n GNS Proxy CA -d ~/.pki/nssdb /dev/null 21 + certutil -A -n GNS Proxy CA -t CT,, -d ~/.pki/nssdb $GNSCERT + fi + + +Index: gnunet-0.10.1-2/contrib/gnunet-gns-import.sh +=== +--- gnunet-0.10.1-2/contrib/gnunet-gns-import.sh gnunet-0.10.1-2/contrib/gnunet-gns-import.sh +@@ -25,9 +25,9 @@ + + while getopts c: opt; do + case $opt in + c) ++ options=$options -c $OPTARG +- options+=-c $OPTARG + ;; + \?) + echo Invalid option: -$OPTARG 2 + exit 1 diff -Nru gnunet-0.10.1/debian/patches/series gnunet-0.10.1/debian/patches/series --- gnunet-0.10.1/debian/patches/series 2014-10-15 21:41:21.0 +0200 +++ gnunet-0.10.1/debian/patches/series 2014-12-20 09:44:17.0 +0100 @@ -3,3 +3,4 @@ typos.diff noinst_set.diff kfreebsd_malloc_np.patch +fix-bashism.patch
Bug#772233: bashism in /bin/sh script
2014-12-20 10:30 GMT+01:00 Bálint Réczey bal...@balintreczey.hu: Hi, 2014-12-19 22:51 GMT+01:00 Holger Levsen hol...@layer-acht.org: On Freitag, 19. Dezember 2014, Balint Reczey wrote: If you don't have time I would happily prepare an NMU with the fix. Please go ahead. Thanks! I just performed the NMU to DELAYED/2 with the attached patch. I made a typo in the bug number, please see the fixed patch attached. I also reuploaded the package to DELAYED/2. Cheers, Balint diff -Nru gnunet-0.10.1/debian/changelog gnunet-0.10.1/debian/changelog --- gnunet-0.10.1/debian/changelog 2014-10-15 21:44:30.0 +0200 +++ gnunet-0.10.1/debian/changelog 2014-12-20 10:00:17.0 +0100 @@ -1,3 +1,12 @@ +gnunet (0.10.1-2.1) unstable; urgency=medium + + * Non-maintainer upload. + + [Raphael Geissert] + * Fix bashisms (Closes: #772233) + + -- Balint Reczey bal...@balintreczey.hu Sat, 20 Dec 2014 09:59:13 +0100 + gnunet (0.10.1-2) unstable; urgency=medium * Put the upstream signing key in debian/upstream/signing-key.asc and remove diff -Nru gnunet-0.10.1/debian/patches/fix-bashism.patch gnunet-0.10.1/debian/patches/fix-bashism.patch --- gnunet-0.10.1/debian/patches/fix-bashism.patch 1970-01-01 01:00:00.0 +0100 +++ gnunet-0.10.1/debian/patches/fix-bashism.patch 2014-12-20 10:34:36.0 +0100 @@ -0,0 +1,54 @@ +Description: fix bashisms +Bug: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=772233 +Author: Raphael Geissert geiss...@debian.org +Forwarded: https://gnunet.org/bugs/view.php?id=3588 + +Index: gnunet-0.10.1-2/src/gns/gnunet-gns-proxy-setup-ca +=== +--- gnunet-0.10.1-2/src/gns/gnunet-gns-proxy-setup-ca gnunet-0.10.1-2/src/gns/gnunet-gns-proxy-setup-ca +@@ -7,9 +7,9 @@ + options='' + while getopts c: opt; do + case $opt in + c) ++ options=$options -c $OPTARG +- options+=-c $OPTARG + ;; + \?) + echo Invalid option: -$OPTARG 2 + exit 1 +@@ -38,16 +38,16 @@ + for f in ~/.mozilla/firefox/*.default + do + if [ -d $f ]; then + echo Importing CA info Firefox $f ++certutil -D -n GNS Proxy CA -d ~/.mozilla/firefox/*.default /dev/null 21 +-certutil -D -n GNS Proxy CA -d ~/.mozilla/firefox/*.default /dev/null 21 + certutil -A -n GNS Proxy CA -t CT,, -d ~/.mozilla/firefox/*.default $GNSCERT + fi + done + + if [ -d ~/.pki/nssdb ]; then + echo Importing CA into Chrome ++ certutil -D -n GNS Proxy CA -d ~/.pki/nssdb /dev/null 21 +- certutil -D -n GNS Proxy CA -d ~/.pki/nssdb /dev/null 21 + certutil -A -n GNS Proxy CA -t CT,, -d ~/.pki/nssdb $GNSCERT + fi + + +Index: gnunet-0.10.1-2/contrib/gnunet-gns-import.sh +=== +--- gnunet-0.10.1-2/contrib/gnunet-gns-import.sh gnunet-0.10.1-2/contrib/gnunet-gns-import.sh +@@ -25,9 +25,9 @@ + + while getopts c: opt; do + case $opt in + c) ++ options=$options -c $OPTARG +- options+=-c $OPTARG + ;; + \?) + echo Invalid option: -$OPTARG 2 + exit 1 diff -Nru gnunet-0.10.1/debian/patches/series gnunet-0.10.1/debian/patches/series --- gnunet-0.10.1/debian/patches/series 2014-10-15 21:41:21.0 +0200 +++ gnunet-0.10.1/debian/patches/series 2014-12-20 09:44:17.0 +0100 @@ -3,3 +3,4 @@ typos.diff noinst_set.diff kfreebsd_malloc_np.patch +fix-bashism.patch
Bug#760385: Fix for CVE-2014-5256
Hi Mike, On Fri, 19 Dec 2014 21:11:10 -0500 Michael Gilbert mgilb...@debian.org wrote: control: severity -1 important There is no security support for libv8 in jessie, so security issues aren't RC. Could you please add some links to explain that? I was about to fix this issue in an NMU after double-checking the fix. Cheers, Balint -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#760385: Fix for CVE-2014-5256
On Sat, Dec 20, 2014 at 4:59 AM, Balint Reczey wrote: Hi Mike, On Fri, 19 Dec 2014 21:11:10 -0500 Michael Gilbert wrote: control: severity -1 important There is no security support for libv8 in jessie, so security issues aren't RC. Could you please add some links to explain that? I was about to fix this issue in an NMU after double-checking the fix. Severity doesn't say anything about whether or not a bugs can be fixed, so you can still do that. Anyway it was decided recently on the security team ml. Best wishes, Mike -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#760385: Fix for CVE-2014-5256
Quoting Michael Gilbert (2014-12-20 03:11:10) control: severity -1 important There is no security support for libv8 in jessie, so security issues aren't RC. Lack of support do not change severity. Seems more appropriate to then tag as *-ignore instead. - 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#773189: [Pkg-libvirt-maintainers] Bug#773189: libvirt-daemon: Haswell microcode update breaks CPU detection
On Tue, Dec 16, 2014 at 01:34:12PM +0100, Guido Günther wrote: On Mon, Dec 15, 2014 at 06:56:19PM +0100, intrigeri wrote: hi, Chris Boot wrote (15 Dec 2014 12:39:52 GMT) : The intel-microcode 3.20140913.1 update disables TSX-NI (transactional memory instructions). When a server running libvirt is rebooted with this update, libvirt no longer considers the machine to have a Haswell CPU: dietrich ~ # virsh capabilities | grep -A1 'archx86_64' archx86_64/arch modelSandyBridge/model This causes a problem as any VMs that require a Haswell CPU, which would have worked previously, now fail to start altogether. Commenting out the two cpuinfo flags relevant to TSX-NI from /usr/share/libvirt/cpu_map.xml fixes this for me: FWIW, I've been suffering from the symptoms of that issue for a few weeks. I guessed it was caused by that microcode update, but had no time to report it. *If* that's a regression since Wheezy, I think it would qualify as RC, since VMs that started just fine previously now fail to come up at boot. The workaround (in the package) is tiny, and makes sense to me: if Intel themselves now consider that Haswell CPUs have no TSX-NI, then libvirt's view of what's a Haswell CPU should be updated. OTOH, the user-side workaround (copy host CPU model) is easy enough too, although a bit painful to discover initially for many users I guess. Shall we ask the release team if they would happily unblock this change for Jessie? I think we should. I've submitted it upstream to get some feadback and make this a safe change and thanks to both of you! Following upstream's reasoning: https://www.redhat.com/archives/libvir-list/2014-December/msg00950.html I'm inclinded to tag this wontfix since we'd otherwise change behaviour in regard to other distros. We could add a HaswellDebian2 in ase we want that featureset codified as well. Cheers, -- Guido -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#773561: Installing xen-linux-system-amd64 on jessie fails
On Sat, 2014-12-20 at 00:57 +0100, Sydney Meyer wrote: Job for xen.service failed. See 'systemctl status xen.service' and 'journalctl -xn' for details. Please can you provide the output of these two commands while in this state. Ian. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#760385: lowering severity of bugs not tracked by release team
Quoting Michael Gilbert (2014-12-20 11:06:47) On Sat, Dec 20, 2014 at 4:59 AM, Balint Reczey wrote: On Fri, 19 Dec 2014 21:11:10 -0500 Michael Gilbert wrote: control: severity -1 important There is no security support for libv8 in jessie, so security issues aren't RC. Could you please add some links to explain that? I was about to fix this issue in an NMU after double-checking the fix. Severity doesn't say anything about whether or not a bugs can be fixed, so you can still do that. Anyway it was decided recently on the security team ml. I find it sensible for the security team to give up on maintaining some packages - and I find it great to try communicate that to our users by use of the debian-security-support package. Just now I learned from above bugreport that the security team also actively *lower* bugreports to avoid them being treated as release candidate, for packages not maintained by the security team. That I find a horrible approach: Severity of a bug is independent on whether it will be fixed or not. The more proper tag to use is *-ignore, IMO. Please let us not hide problems! - 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#773579: fontypython should be ported to wx 3.0 (yes, again)
On Sat, Dec 20, 2014 at 10:10:53AM +0100, Pietro Battiston wrote: When I fixed #765487, I missed #757886, that is, the fact that the transition from 2.8 to 3.0 (of fontypython) had not been spontaneous. As a consequence of this, I assumed Depends were OK, which they are not, and the current package is useless. As a consequence of this (probably), I also missed #755757. (applause) So using wx 2.8 is not an option in jessie, and the original bug must be solved. Or we don't release jessie with fontypython - you say in #765487 that it seems pretty abandoned upstream. It does seem like people are actually still using it though, judging from the comments in that ticket. Olly, in #757886 you state that everything seems to be fine... can you confirm with wxpython3.0 3.0.1.1+dfsg-2 ? Will retest it when I have a suitable machine in front of me. But the error messages in #765487 do seem to indicate how to solve the problem: .../src/common/stdpbase.cpp(62): assert traits failed in Get(): create wxApp before calling this i.e. make sure that the wxApp object is created before this code gets called. Cheers, Olly -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#773465: unblock: exim4/4.84-5
On Fri, Dec 19, 2014 at 18:43:46 +0100, Andreas Metzler wrote:
On 2014-12-19 Julien Cristau jcris...@debian.org wrote:
On Thu, Dec 18, 2014 at 18:59:35 +0100, Andreas Metzler wrote:
+ * Change the init script's restart order from { regenerate_config;
stop;
+start ; } to { stop; regenerate_config; start ; }. (Thanks, Jakub
Warmuz)
+Closes: #768874
Does this mean that, if there's an error in the config, exim could be
left stopped by the init script restart action, where previously the
user would be notified of the error before stopping the daemon?
Good point.
I can either back out this change for jessie and re-upload or can
upload a better fix. - I guess I will add a something like --dry-run to
/usr/sbin/update-exim4.conf.
Which of these options would you prefer?
I'm not sure, so I'm happy to trust your judgement on that, just wanted
to raise the potential issue.
Cheers,
Julien
signature.asc
Description: Digital signature
Bug#760385: lowering severity of bugs not tracked by release team
[sent again, cc correct list address this time] Quoting Michael Gilbert (2014-12-20 11:06:47) On Sat, Dec 20, 2014 at 4:59 AM, Balint Reczey wrote: On Fri, 19 Dec 2014 21:11:10 -0500 Michael Gilbert wrote: control: severity -1 important There is no security support for libv8 in jessie, so security issues aren't RC. Could you please add some links to explain that? I was about to fix this issue in an NMU after double-checking the fix. Severity doesn't say anything about whether or not a bugs can be fixed, so you can still do that. Anyway it was decided recently on the security team ml. I find it sensible for the security team to give up on maintaining some packages - and I find it great to try communicate that to our users by use of the debian-security-support package. Just now I learned from above bugreport that the security team also actively *lower* bugreports to avoid them being treated as release candidate, for packages not maintained by the security team. That I find a horrible approach: Severity of a bug is independent on whether it will be fixed or not. The more proper tag to use is *-ignore, IMO. Please let us not hide problems! - 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#773580: lzo2: FTBFS on mips powerpc s390x
package: lzo2 version: 2.08-1.1 severity: serious Hi, The latest upload of lzo2 failed on mips, powerpc, s390x (and sparc). This will prevent migration to jessie. https://buildd.debian.org/status/package.php?p=lzo2suite=sid Cheers, Ivo -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#773580: lzo2: FTBFS on mips powerpc s390x
On 20/12/14 10:57, Ivo De Decker wrote: The latest upload of lzo2 failed on mips, powerpc, s390x (and sparc). In other words, on big-endian architectures (where byteswapping to fetch a LE value is not just a memcpy). This seems likely to be a regression caused by the patch that I NMU'd; I'll look into it when I get a chance. S -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#773318: clamav dies/hangs
Hi James, On 19.12.2014 23:07, James Cloos wrote: AC == Andreas Cadhalpun andreas.cadhal...@googlemail.com writes: AC You mean it crashed? AC Please provide excerpts of /var/log/clamav/clamav.log and AC /var/log/syslog from around the time of the crashes. Yes, the clamd process quit, so the milter process was rejecting all incoming mail with a 4xx try again reply. In each case the last thing logged to clamav.log before I restarted clamd was just a Reading databases from /var/lib/clamav line. So it looks like it died during a reload, since: Database correctly reloaded did not get logged. Indeed. It seems like one of the unofficial signature databases caused clamd to crash during reload. It would be great, if you could determine which one that was, so that the problem can be reproduced. AC If you can reproduce the crashes, please install clamav-dbg and use AC gdb to provide a backtrace of the crashes. I removed the clamav-milter call to keep mail flowing; I'll turn it back on on one of them this weekend. Thanks. Best regards, Andreas -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#773041: Bug#773318: clamav dies/hangs
Control: tags 773041 security Control: severity 773041 grave Justification: causes remote denial of service Hi James, On 19.12.2014 23:12, James Cloos wrote: Even w/ the milter not called, one of the MXs has one clamd thread consuming 100% cpu right now. gdb says: #0 0x7fd0b4791ed0 in ?? () from /usr/lib/x86_64-linux-gnu/libmspack.so.0 #1 0x7fd0b47863ea in ?? () from /usr/lib/x86_64-linux-gnu/libmspack.so.0 #2 0x7fd0b55c1e26 in cli_scanmscab (ctx=0x7fd096dfb6b0, sfx_offset=256) at libmspack.c:384 #3 0x7fd0b5597aa0 in magic_scandesc (ctx=0x7fd096dfb6b0, type=CL_TYPE_ANY) at scanners.c:2703 #4 0x7fd0b5598059 in cli_base_scandesc (desc=12, ctx=0x7fd096dfb6b0, type=CL_TYPE_ANY) at scanners.c:3051 #5 0x7fd0b559bf33 in fileblobScan (fb=0x7fd088003910) at blob.c:641 #6 0x7fd0b559c01d in fileblobScanAndDestroy (fb=fb@entry=0x7fd088003910) at blob.c:399 #7 0x7fd0b55a08db in do_multipart (mainMessage=0x0, messages=optimized out, i=optimized out, rc=0x7fd096dfa35c, mctx=0x7fd096dfa420, messageIn=optimized out, tptr=0x7fd096dfa360, recursion_level=0) at mbox.c:3712 #8 0x7fd0b55a0019 in parseEmailBody (messageIn=0x7fd095df4000, messageIn@entry=0x7fd088004940, textIn=0x100, textIn@entry=0x0, mctx=0x7fd0880047b1, recursion_level=32512, recursion_level@entry=0) at mbox.c:1533 #9 0x7fd0b55a1232 in cli_parse_mbox ( dir=dir@entry=0x7fd088000e50 /tmp/clamav-4b94ddbad0a132b5af6d2f6db3a76e40.tmp, ctx=ctx@entry=0x7fd096dfb6b0) at mbox.c:508 #10 0x7fd0b55a1b1a in cli_mbox ( dir=dir@entry=0x7fd088000e50 /tmp/clamav-4b94ddbad0a132b5af6d2f6db3a76e40.tmp, ctx=ctx@entry=0x7fd096dfb6b0) at mbox.c:309 #11 0x7fd0b5579218 in cli_scanmail (ctx=0x7fd096dfb6b0) at scanners.c:1702 Thanks for the backtrace! As it shows that clamd hangs in libmspack, I think this is bug #773041 [1]. A possible fix is mentioned in [2]. We'll have to include it in the libmspack copy embedded in clamav, which is used in wheezy. Best regards, Andreas 1: https://bugs.debian.org/773041 2: https://bugs.debian.org/773041#8 -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#773581: unblock: vim-addon-mw-utils/0.1-5
Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: unblock
Please unblock package vim-addon-mw-utils
Fix for RC bug #773184. The changes since version 0.1-4 are tiny and they
consist of:
* Addedd vim-addon-mw-utils.dirs and deleted vim-addon-mw-utils.postrm
to prevent the removal of directories owned by vim-common
(Closes: #773184)
$ debdiff vim-addon-mw-utils_0.1-4_all.deb vim-addon-mw-utils_0.1-5_all.deb
[The following lists of changes regard files as different if they have
different names, permissions or owners.]
Files in first .deb but not in second
-
-rwxr-xr-x root/root DEBIAN/postrm
Control files: lines which differ (wdiff format)
Installed-Size: [-88-] {+107+}
Version: [-0.1-4-] {+0.1-5+}
http://anonscm.debian.org/cgit/collab-maint/vim-addon-mw-
utils.git/commit/?id=5131ae8be7b5a05ada40154511e0d0e98502f8ba
unblock vim-addon-mw-utils/0.1-5
-- 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/4 CPU cores)
Locale: LANG=it_IT.utf8, LC_CTYPE=it_IT.utf8 (charmap=UTF-8)
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#760385: lowering severity of bugs not tracked by release team
On Sat, 2014-12-20 at 11:48 +0100, Jonas Smedegaard wrote: [sent again, cc correct list address this time] Quoting Michael Gilbert (2014-12-20 11:06:47) On Sat, Dec 20, 2014 at 4:59 AM, Balint Reczey wrote: On Fri, 19 Dec 2014 21:11:10 -0500 Michael Gilbert wrote: control: severity -1 important There is no security support for libv8 in jessie, so security issues aren't RC. Could you please add some links to explain that? I was about to fix this issue in an NMU after double-checking the fix. Severity doesn't say anything about whether or not a bugs can be fixed, so you can still do that. Anyway it was decided recently on the security team ml. I'm not aware of it having been decided that the security team were the arbiters of release criticality in such situations. I find it sensible for the security team to give up on maintaining some packages - and I find it great to try communicate that to our users by use of the debian-security-support package. Just now I learned from above bugreport that the security team also actively *lower* bugreports to avoid them being treated as release candidate, for packages not maintained by the security team. That I find a horrible approach: Severity of a bug is independent on whether it will be fixed or not. The more proper tag to use is *-ignore, IMO. The setting of -ignore by people other the Release Team (or those who have previously discussed doing so, e.g. for certain classes of bug in stable) is still wrong. Regards, Adam -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#773583: vim-tlib: purging removes directories owned by vim-common: /var/lib/vim/addons/, /var/lib/vim/
Package: vim-tlib Version: 1.12-2 Severity: serious Justification: Policy 6.8 Hi, same problem of bug #773184. This part of the postrm is faulty: case $1 in purge) if [ -d /var/lib/vim/addons/samples/ ]; then rmdir -p --ignore-fail-on-non-empty /var/lib/vim/addons/samples || : fi ;; I'm uploading the fixed package. -- 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/4 CPU cores) Locale: LANG=it_IT.utf8, LC_CTYPE=it_IT.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages vim-tlib depends on: ii vim2:7.4.488-3 ii vim-addon-manager 0.5.3 ii vim-gnome [vim]2:7.4.488-3 vim-tlib recommends no packages. vim-tlib suggests no packages. -- no debconf information -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#763269: upgrade-system: Want to remove required package in Debian Edu
2014-09-29 1:07 GMT+03:00 Martin-Éric Racine martin-eric.rac...@iki.fi: 2014-09-28 21:32 GMT+03:00 Petter Reinholdtsen p...@hungry.com: Package: upgrade-system Version: 1.7.0.0 Severity: wishlist User: debian-...@lists.debian.org Usertags: debian-edu Hi. I've tested upgrade-system in Debian Edu Jessie, and am surprised it want to remove education-common, which is a package we want to have installed on all Debian Edu systems. But I am unable to figure out why it want to remove it. Can upgrade-system be changed to keep the education-common package? Here is a test run: root@skolelinuxtest:~# upgrade-system 1) Updating package lists: I: Package lists updated. 2) Checking for upgradable packages: I: No upgradable package to install. 3) Checking for orphan packages: I: Purging orphan packages... Reading package lists... Done Building dependency tree Reading state information... Done The following packages will be REMOVED: attr* education-common* libboost-iostreams1.54.0* libhdb9-heimdal* libkdc2-heimdal* python-dnspython* samba* samba-dsdb-modules* samba-vfs-modules* tdb-tools* 0 upgraded, 0 newly installed, 10 to remove and 0 not upgraded. After this operation, 15.0 MB disk space will be freed. Do you want to continue? [Y/n] n Abort. 4) Cleaning package cache. I: System upgrade completed. root@skolelinuxtest:~# How can this problem be debugged? By manually running 'deborphan' with the default options found in /etc/upgrade-system.conf and adjusting those options according to your own needs. Petter, Have you found upgrade-system.conf options that solved your problem? -- Martin-Éric -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/debian-bugs-dist
Bug#773189: [Pkg-libvirt-maintainers] Bug#773189: libvirt-daemon: Haswell microcode update breaks CPU detection
Hi, Guido Günther wrote (20 Dec 2014 10:27:18 GMT) : Following upstream's reasoning: https://www.redhat.com/archives/libvir-list/2014-December/msg00950.html I'm inclinded to tag this wontfix since we'd otherwise change behaviour in regard to other distros. Agreed. We could add a HaswellDebian2 in ase we want that featureset codified as well. I don't think it's worth the hassle: users will need to take some manual action anyway, so they can as well switch to model=copyhost or whatever it's called. However, it's maybe worth adding a few lines about microcode updates vs. CPU features in README.Debian? (Ideally, the microcode package's NEWS.Debian would have done so, but now it's too late so the best place to clarify what's happening seems to be the libvirt package itself, no?) Cheers, -- intrigeri -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#745901: fglrx-driver: fglrx update crashes totem, gdm, gnome-session and anything that uses clutter
On 2014-12-20 00:27, Craig Small wrote: On Wed, Dec 17, 2014 at 11:32:33PM +0100, Andreas Beckmann wrote: I just uploaded 1:14.12-1 to experimental - please give it a try. Do you know if it does, or should, fix the missing mouse pointer problem too? For me that's the more worrying problem. The reason two reports so far that the mouse cursor problem persists :-( -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#773584: nautilus: no open with menu for directory
Package: nautilus Version: 3.14.1-2 Severity: normal There is no open with menu entry if right-clicking on directories. -- System Information: Debian Release: 8.0 APT prefers testing-updates APT policy: (500, 'testing-updates'), (500, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 3.16.0-4-amd64 (SMP w/4 CPU cores) Locale: LANG=de_DE.utf8, LC_CTYPE=de_DE.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages nautilus depends on: ii desktop-file-utils 0.22-1 ii gsettings-desktop-schemas 3.14.1-1 ii gvfs 1.22.2-1 ii libatk1.0-02.14.0-1 ii libc6 2.19-13 ii libcairo-gobject2 1.14.0-2.1 ii libcairo2 1.14.0-2.1 ii libexempi3 2.2.1-2 ii libexif12 0.6.21-2 ii libgail-3-03.14.5-1 ii libgdk-pixbuf2.0-0 2.31.1-2+b1 ii libglib2.0-0 2.42.1-1 ii libglib2.0-data2.42.1-1 ii libgnome-desktop-3-10 3.14.1-1 ii libgtk-3-0 3.14.5-1 ii libnautilus-extension1a3.14.1-2 ii libnotify4 0.7.6-2 ii libpango-1.0-0 1.36.8-3 ii libpangocairo-1.0-01.36.8-3 ii libselinux12.3-2 ii libtracker-sparql-1.0-01.2.4-1 ii libx11-6 2:1.6.2-3 ii libxml22.9.1+dfsg1-4 ii nautilus-data 3.14.1-2 ii shared-mime-info 1.3-1 Versions of packages nautilus recommends: ii eject 2.1.5+deb1+cvs20081104-13.1 ii gnome-icon-theme-symbolic 3.12.0-1 ii gnome-sushi3.12.0-2+b1 ii gvfs-backends 1.22.2-1 ii librsvg2-common2.40.5-1 Versions of packages nautilus suggests: ii brasero 3.11.4-1 ii eog 3.14.1-1 ii evince [pdf-viewer] 3.14.1-1 ii totem3.14.0-2 ii tracker 1.2.4-1 ii xdg-user-dirs0.15-2 -- no debconf information -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#769657: Patch
On 12/18/2014 11:38 PM, Jean-Louis Dupond wrote: Hi, Attached you can find a patch that resolves this problem. The patch pipes the mysqldump output directly to bzip2/gzip. Because of this you don't need to have alot of free diskspace to hold the uncompressed .sql file while dumping the database. Please consider to add this in the automysqlbackup package. Thx Jean-Louis Hi Jean-Louis, Thanks for this patch. However, I wont be able to process it before Jessie is released, as there's very little chance that it will be accepted for an unblock by the release team (this is a new feature, not a bug fix...). Cheers, Thomas -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#773585: php-elisp: Wrong indention of function arguments in subsequent lines
Package: php-elisp
Version: 1.13.5-1
Severity: normal
Dear Maintainer,
the current version of php-mode indents function arguments that are
written in subsequent lines in as follows:
$var = array('value 0',
'value 1',
'value 2');
An earlier version of php-mode indented the same code different and
much better:
$var = array('value 0',
'value 1',
'value 2');
Please forward this upstream and/or restore the old behaviour
Regards
Joey
Versions of packages php-elisp depends on:
ii emacs22 [emacsen] 22.3+1-1.2
ii emacs23 [emacsen] 23.4+1-4.1+b1
Versions of packages php-elisp recommends:
pn speedbar none
Versions of packages php-elisp suggests:
ii php5 5.6.3+dfsg-1
ii php5-cli 5.6.3+dfsg-1
-- no debconf information
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#773585: php-elisp: Wrong indention of function arguments in subsequent lines
Hi
Please try drupal mode or any other of the variants.
I think the command is enable-(mode name)
/ Ola
Inguza Technology AB
Sent from a phone
Den 20 dec 2014 13:30 skrev Joey Schulze j...@infodrom.org:
Package: php-elisp
Version: 1.13.5-1
Severity: normal
Dear Maintainer,
the current version of php-mode indents function arguments that are
written in subsequent lines in as follows:
$var = array('value 0',
'value 1',
'value 2');
An earlier version of php-mode indented the same code different and
much better:
$var = array('value 0',
'value 1',
'value 2');
Please forward this upstream and/or restore the old behaviour
Regards
Joey
Versions of packages php-elisp depends on:
ii emacs22 [emacsen] 22.3+1-1.2
ii emacs23 [emacsen] 23.4+1-4.1+b1
Versions of packages php-elisp recommends:
pn speedbar none
Versions of packages php-elisp suggests:
ii php5 5.6.3+dfsg-1
ii php5-cli 5.6.3+dfsg-1
-- no debconf information
Bug#284752: Seems fixed
Seems to be fixed in 1.13.5-1 and before. Regards Joey -- In the beginning was the word, and the word was content-type: text/plain Please always Cc to me when replying to me on the lists. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#283839: Seems fixed
This problem seems to be fixed in 1.13.5-1 and the version before as well. Regards Joey -- In the beginning was the word, and the word was content-type: text/plain Please always Cc to me when replying to me on the lists. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#773586: phoneuid: doesn't start or crashes during startup - probably due to problem in phonefsod
Package: phoneuid Version: 0.1+git20130505-1 Severity: grave Justification: renders package unusable Dear Maintainer, This is sort of a continuation of #766114 which to me seems rightfully closed. There are four things to note in advance please: 1. I'm not sure whether phoneuid is the correct package to file this report against. It could be anywhere in this chain: fso-deviced - phonefsod - phoneuid - phoneui-apps 2. apt doesn't install recommends or suggests on this system by default: # cat /etc/apt/apt.conf APT::Install-Recommends 0; APT::Install-Suggests 0; 3. The automatic screen-blanking that's done by (I think) phonefsod works fine, however the lock screen with the slider (by phoneui-apps) doesn't come up. 4. I tested this first with sysvinit, then with systemd as the init system, but didn't see any differences. All of the following outputs are with systemd. After installing phoneui-apps and trying to start any of the apps (e.g. phoneui-quick-settings), no app window comes up. There's an strace output further down. The problem seems to be that phoneuid is either not starting or dying in the process: # cat phonefsod.log 2014.12.20 11:50:38.551544 [phonefsod] MESSAGE: phonefsod-0.1.0 is in startup mode as user(root) 2014.12.20 11:50:38.765655 [phonefsod] MESSAGE: Inhibiting suspend during startup phase (max 360s) 2014.12.20 11:51:03.876434 [phonefsod] WARNING: failed to connect to /org/freesmartphone/GSM/Device: Error calling StartServiceByName for org.freesmartphone.ogsmd: GDBus.Error:org.freedesktop.DBus.Error.TimedOut: Activation of org.freesmartphone.ogsmd timed out 2014.12.20 11:51:28.909052 [phonefsod] WARNING: failed to connect to /org/freesmartphone/GSM/Device: Error calling StartServiceByName for org.freesmartphone.ogsmd: GDBus.Error:org.freedesktop.DBus.Error.TimedOut: Activation of org.freesmartphone.ogsmd timed out 2014.12.20 11:51:53.955090 [phonefsod] WARNING: failed to connect to /org/freesmartphone/GSM/Device: Error calling StartServiceByName for org.freesmartphone.ogsmd: Timeout was reached 2014.12.20 11:52:18.983082 [phonefsod] WARNING: failed to connect to /org/freesmartphone/GSM/Device: Error calling StartServiceByName for org.freesmartphone.ogsmd: GDBus.Error:org.freedesktop.DBus.Error.TimedOut: Activation of org.freesmartphone.ogsmd timed out 2014.12.20 11:52:44.015819 [phonefsod] WARNING: failed to connect to /org/freesmartphone/GSM/Device: Error calling StartServiceByName for org.freesmartphone.ogsmd: GDBus.Error:org.freedesktop.DBus.Error.TimedOut: Activation of org.freesmartphone.ogsmd timed out 2014.12.20 11:52:44.091402 [phonefsod] MESSAGE: !!! ouch, phoneuid is gone - telephony won't work anymore !!! /var/log/phoneuid.log was not created when the process was started during boot. This is from a manual start as root after killing the original process: # cat phoneuid.log 2014.12.20 13:22:42.087796 [phoneuid] MESSAGE: Using log level 'INFO' 2014.12.20 13:22:42.088528 [libphone-ui]MESSAGE: Loading phoneuid 2014.12.20 13:22:42.423247 [libphone-ui]CRITICAL: No such file or directory 2014.12.20 13:23:07.495138 [libphone-ui]WARNING: failed to connect to /org/freesmartphone/GSM/Device: Error calling StartServiceByName for org.freesmartphone.ogsmd: GDBus.Error:org.freedesktop.DBus.Error.TimedOut: Activation of org.freesmartphone.ogsmd timed out 2014.12.20 13:23:32.524630 [libphone-ui]WARNING: failed to connect to /org/freesmartphone/GSM/Device: Error calling StartServiceByName for org.freesmartphone.ogsmd: GDBus.Error:org.freedesktop.DBus.Error.TimedOut: Activation of org.freesmartphone.ogsmd timed out 2014.12.20 13:23:57.563633 [libphone-ui]WARNING: failed to connect to /org/freesmartphone/GSM/Device: Error calling StartServiceByName for org.freesmartphone.ogsmd: GDBus.Error:org.freedesktop.DBus.Error.TimedOut: Activation of org.freesmartphone.ogsmd timed out for reference: # dpkg --get-selections | grep n900 fso-deviced-n900install fso-gsmd-n900 install # cat fsodeviced.log 2014-12-20T10:50:35.873901Z [INFO] fsodeviced : Binary launched successful (FsoFrameworkFileLogger created as theLogger) 2014-12-20T10:50:36.026062Z [INFO] Kernel26Display /sys/class/backlight/acx565akm: Created w/ max brightness = 255, smooth up = false, smooth down = false 2014-12-20T10:50:36.034088Z [INFO] Kernel26Led /sys/class/leds/lp5523:kb1: ^^^ supports the following triggers: '[none] timer heartbeat mmc0 mmc1 bq27200-0-charging-or-full bq27200-0-charging bq27200-0-full bq27200-0-charging-blink-full-solid isp1704-online bq24150a-4-online' 2014-12-20T10:50:36.034332Z [INFO] Kernel26Led /sys/class/leds/lp5523:kb1: Created 2014-12-20T10:50:36.035858Z [INFO] Kernel26Led /sys/class/leds/lp5523:kb2: ^^^ supports the following triggers: '[none] timer heartbeat mmc0 mmc1 bq27200-0-charging-or-full bq27200-0-charging bq27200-0-full
Bug#773582: xfwm4: Horizontal lines tearing when moving windows or watching video
Package: xfwm4 Dear Maintainer, I have the latest official debian stable release installed on three different machines with different graphic cards (intel,nvidia) and XFCE as the default DE through the installer. All of them have the same issue: Horizontal lines tearing when moving windows or watching video. I try to enable/disable xfwm's compositor but nothing change. Installing and using other compositor such as compton, solves the problem (Only some performance issues remain). So i suppose this is a xfwm4 bug? -- System Information: Debian Release: 7.7 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.2.0-4-amd64 (SMP w/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 xfwm4 depends on: ii libc6 2.19-13 ii libdbus-glib-1-2 0.100.2-1 ii libgdk-pixbuf2.0-02.26.1-1 ii libglib2.0-0 2.33.12+really2.32.4-5 ii libgtk2.0-0 2.24.10-2 ii libpango1.0-0 1.30.0-1 ii libstartup-notification0 0.12-1 ii libwnck22 2.30.7-1 ii libx11-6 2:1.5.0-1+deb7u1 ii libxcomposite11:0.4.3-2 ii libxdamage1 1:1.1.3-2 ii libxext6 2:1.3.1-2+deb7u1 ii libxfce4ui-1-04.8.1-1 ii libxfce4util4 4.8.2-1 ii libxfconf-0-2 4.8.1-1 ii libxfixes31:5.0-4+deb7u1 ii libxrandr22:1.3.2-2+deb7u1 ii libxrender1 1:0.9.7-1+deb7u1 Versions of packages xfwm4 recommends: ii librsvg2-common 2.36.1-2 ii xfwm4-themes 4.6.0-3 Versions of packages xfwm4 suggests: ii xfce4 4.8.0.3 -- no debconf information -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#773318: clamav dies/hangs
Hi, On Sat, Dec 20, 2014 at 12:12:13PM +0100, Andreas Cadhalpun wrote: Control: tags 773041 security Control: severity 773041 grave Justification: causes remote denial of service For info, I saw this a few days ago and reported it to the security team. It is indeed available in the wild, and is caused by the malformed CAB file. The version in wheezy and wheezy-updates will need separate fixes, as they change how they use libmspack, though the actual fix seems to be fairly trivial. The version in sid/jessie uses the packaged libmspack, so it'll need fixing there. As it shows that clamd hangs in libmspack, I think this is bug #773041 [1]. A possible fix is mentioned in [2]. We'll have to include it in the libmspack copy embedded in clamav, which is used in wheezy. 1: https://bugs.debian.org/773041 2: https://bugs.debian.org/773041#8 Thanks, Neil signature.asc Description: Digital signature
Bug#773587: grub-imageboot: Document how to boot a Debian live image
Package: grub-imageboot Version: 0.6 Severity: wishlist Tags: patch Dear Maintainer, when trying to boot a Debian live image it is not obvious how to achieve it. Therefore I have attached a patch for the README.Debian to include a hint on the findiso kernel commandline parameter. Kind regards, Kai Harries -- System Information: Debian Release: 8.0 APT prefers testing-updates APT policy: (500, 'testing-updates'), (500, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 3.16.0-4-amd64 (SMP w/4 CPU cores) Locale: LANG=en_US.utf8, LC_CTYPE=en_US.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages grub-imageboot depends on: ii grub-pc 2.02~beta2-18 ii syslinux-common 3:6.03+dfsg-4 grub-imageboot recommends no packages. grub-imageboot suggests no packages. -- no debconf information --- /usr/share/doc/grub-imageboot/README.Debian 2011-12-23 00:36:12.0 +0100 +++ README.Debian 2014-12-20 10:58:27.684700976 +0100 @@ -14,3 +14,7 @@ If you need special options to boot your images see $IMAGEOPTS and $ISOOPTS in /etc/default/grub-imageboot.conf. + +If you want to boot a Debian live image, you may need to append +findiso=/boot/images/NameOfYour.iso to the kernel command line in the +boot loader of your image.
Bug#773463: jasper: CVE-2014-8137 CVE-2014-8138
Control: tags -1 + patch
Hi Roland,
On Sat, Dec 20, 2014 at 06:08:54AM +0100, Salvatore Bonaccorso wrote:
I will try to work again (as for the previous update) on the
wheezy-security update. As the patches will be mostly the same I could
also do again the unstable upload too. Just let me know!
Here the actual patches plus debdiff used for wheezy-security.
Regards,
Salvatore
diff -Nru jasper-1.900.1/debian/changelog jasper-1.900.1/debian/changelog
--- jasper-1.900.1/debian/changelog 2014-11-28 23:12:21.0 +0100
+++ jasper-1.900.1/debian/changelog 2014-12-20 08:46:40.0 +0100
@@ -1,3 +1,13 @@
+jasper (1.900.1-13+deb7u2) wheezy-security; urgency=high
+
+ * Non-maintainer upload by the Security Team.
+ * Add 05-CVE-2014-8137.patch patch.
+CVE-2014-8137: double-free in in jas_iccattrval_destroy(). (Closes:
#773463)
+ * Add 06-CVE-2014-8138.patch patch.
+CVE-2014-8138: heap overflow in jp2_decode(). (Closes: #773463)
+
+ -- Salvatore Bonaccorso car...@debian.org Sat, 20 Dec 2014 08:42:19 +0100
+
jasper (1.900.1-13+deb7u1) wheezy-security; urgency=high
* Non-maintainer upload by the Security Team.
diff -Nru jasper-1.900.1/debian/patches/05-CVE-2014-8137.patch
jasper-1.900.1/debian/patches/05-CVE-2014-8137.patch
--- jasper-1.900.1/debian/patches/05-CVE-2014-8137.patch1970-01-01
01:00:00.0 +0100
+++ jasper-1.900.1/debian/patches/05-CVE-2014-8137.patch2014-12-20
08:46:40.0 +0100
@@ -0,0 +1,66 @@
+Description: CVE-2014-8137: double-free in in jas_iccattrval_destroy()
+Origin: vendor, https://bugzilla.redhat.com/attachment.cgi?id=967283,
+ https://bugzilla.redhat.com/attachment.cgi?id=967284
+Bug-Debian: https://bugs.debian.org/773463
+Bug-RedHat: https://bugzilla.redhat.com/show_bug.cgi?id=1173157
+Forwarded: no
+Author: Tomas Hoger tho...@redhat.com
+Last-Update: 2014-12-20
+
+--- a/src/libjasper/base/jas_icc.c
b/src/libjasper/base/jas_icc.c
+@@ -1010,7 +1010,6 @@ static int jas_icccurv_input(jas_iccattr
+ return 0;
+
+ error:
+- jas_icccurv_destroy(attrval);
+ return -1;
+ }
+
+@@ -1128,7 +1127,6 @@ static int jas_icctxtdesc_input(jas_icca
+ #endif
+ return 0;
+ error:
+- jas_icctxtdesc_destroy(attrval);
+ return -1;
+ }
+
+@@ -1207,8 +1205,6 @@ static int jas_icctxt_input(jas_iccattrv
+ goto error;
+ return 0;
+ error:
+- if (txt-string)
+- jas_free(txt-string);
+ return -1;
+ }
+
+@@ -1329,7 +1325,6 @@ static int jas_icclut8_input(jas_iccattr
+ goto error;
+ return 0;
+ error:
+- jas_icclut8_destroy(attrval);
+ return -1;
+ }
+
+@@ -1498,7 +1493,6 @@ static int jas_icclut16_input(jas_iccatt
+ goto error;
+ return 0;
+ error:
+- jas_icclut16_destroy(attrval);
+ return -1;
+ }
+
+--- a/src/libjasper/jp2/jp2_dec.c
b/src/libjasper/jp2/jp2_dec.c
+@@ -291,7 +291,10 @@ jas_image_t *jp2_decode(jas_stream_t *in
+ case JP2_COLR_ICC:
+ iccprof = jas_iccprof_createfrombuf(dec-colr-data.colr.iccp,
+ dec-colr-data.colr.iccplen);
+- assert(iccprof);
++ if (!iccprof) {
++ jas_eprintf(error: failed to parse ICC profile\n);
++ goto error;
++ }
+ jas_iccprof_gethdr(iccprof, icchdr);
+ jas_eprintf(ICC Profile CS %08x\n, icchdr.colorspc);
+ jas_image_setclrspc(dec-image, fromiccpcs(icchdr.colorspc));
diff -Nru jasper-1.900.1/debian/patches/06-CVE-2014-8138.patch
jasper-1.900.1/debian/patches/06-CVE-2014-8138.patch
--- jasper-1.900.1/debian/patches/06-CVE-2014-8138.patch1970-01-01
01:00:00.0 +0100
+++ jasper-1.900.1/debian/patches/06-CVE-2014-8138.patch2014-12-20
08:46:40.0 +0100
@@ -0,0 +1,22 @@
+Description: CVE-2014-8138: heap overflow in jp2_decode()
+Origin: vendor, https://bugzilla.redhat.com/attachment.cgi?id=967280
+Bug-Debian: https://bugs.debian.org/773463
+Bug-RedHat: https://bugzilla.redhat.com/show_bug.cgi?id=1173162
+Forwarded: no
+Author: Tomas Hoger tho...@redhat.com
+Last-Update: 2014-12-20
+
+--- a/src/libjasper/jp2/jp2_dec.c
b/src/libjasper/jp2/jp2_dec.c
+@@ -389,6 +389,11 @@ jas_image_t *jp2_decode(jas_stream_t *in
+ /* Determine the type of each component. */
+ if (dec-cdef) {
+ for (i = 0; i dec-numchans; ++i) {
++ /* Is the channel number reasonable? */
++ if (dec-cdef-data.cdef.ents[i].channo =
dec-numchans) {
++ jas_eprintf(error: invalid channel number in
CDEF box\n);
++ goto error;
++ }
+ jas_image_setcmpttype(dec-image,
+
dec-chantocmptlut[dec-cdef-data.cdef.ents[i].channo],
+ jp2_getct(jas_image_clrspc(dec-image),
diff -Nru
Bug#773588: libav-tools: spectrum visualisation does not respect window manager
Package: libav-tools Version: 6:11-2 Severity: minor Tags: upstream Hi, I use a tiling window manager (ratpoison), and when using avplay, the visualisation is not scaled to the window size until the window is hidden and shown again. This is typical behaviour for programs that do not handle the case when their window placement hints are ignored. Simon -- System Information: Debian Release: 8.0 APT prefers testing APT policy: (990, 'testing') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.16.0-4-amd64 (SMP w/8 CPU cores) Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: sysvinit (via /sbin/init) Versions of packages libav-tools depends on: ii dpkg 1.17.21 ii libavcodec56 6:11-2 ii libavdevice556:11-2 ii libavfilter5 6:11-2 ii libavformat566:11-2 ii libavresample2 6:11-2 ii libavutil54 6:11-2 ii libc62.19-13 ii libsdl1.2debian 1.2.15-10+b1 ii libswscale3 6:11-2 ii libvdpau10.8-3 ii libx11-6 2:1.6.2-3 libav-tools recommends no packages. Versions of packages libav-tools suggests: pn frei0r-plugins none -- Configuration Files: /etc/avserver.conf 43e9d812fb6ca7464d13eec57d6b3c17 [Errno 2] Datei oder Verzeichnis nicht gefunden: u'/etc/avserver.conf 43e9d812fb6ca7464d13eec57d6b3c17' -- no debconf information -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#773589: baobab does not show mounted devices
Package: baobab Version: 3.14.1-1 Severity: important Starting baobab without parameters shows up only root-filesystem, unmounted drives and my personal folder. If I walk to the mountpoints (/home and some are subfolders of /mnt) within baobab there seems to be nothing mounted, what maybe wanted, but since I cannot see mounted drives in the main screen it is not possible to analyze them. If I start baobab mountpoint with mountpoint one of the subfolders within /mnt everything works fine. -- System Information: Debian Release: 8.0 APT prefers testing-updates APT policy: (500, 'testing-updates'), (500, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 3.16.0-4-amd64 (SMP w/4 CPU cores) Locale: LANG=de_DE.utf8, LC_CTYPE=de_DE.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages baobab depends on: ii dconf-gsettings-backend [gsettings-backend] 0.22.0-1 ii libatk1.0-0 2.14.0-1 ii libc62.19-13 ii libcairo-gobject21.14.0-2.1 ii libcairo21.14.0-2.1 ii libgdk-pixbuf2.0-0 2.31.1-2+b1 ii libglib2.0-0 2.42.1-1 ii libgtk-3-0 3.14.5-1 ii libpango-1.0-0 1.36.8-3 ii libpangocairo-1.0-0 1.36.8-3 Versions of packages baobab recommends: ii yelp 3.14.1-1 baobab suggests no packages. -- no debconf information -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#773590: g++-4.9: incorrectly compiles moc on sparc
Package: g++-4.9
Version: 4.9.2-8
Control: affects -1 src:qtbase-opensource-src
Dear gcc maintainers,
In qtbase-opensource-src 5.4.0+dfsg, src/tools/moc/main.cpp contains the
following code:
if (output.size()) { // output file specified
out = fopen(QFile::encodeName(output).constData(), w); // create
output file
if (!out)
{
fprintf(stderr, moc: Cannot create %s\n,
QFile::encodeName(output).constData());
return 1;
}
} else { // use stdout
out = stdout;
}
However, when moc is compiled, it behaves very strangely in this place:
* fopen does not seem to be called at all (at least there is no corresponding
open syscall in strace output), so `out' remains a null pointer.
* Only the %s\n part is printed to stderr, without the moc: Cannot create
part.
An example can be seen in qtbase-opensource-src/experimental build log.
A relevant part of it (simplified):
../bin/moc animation/qabstractanimation.h -o .moc/moc_qabstractanimation.cpp
.moc/moc_qabstractanimation.cpp
make[3]: *** [.moc/moc_qabstractanimation.cpp] Error 1
The last `write' call in strace output is:
write(2, .moc/moc_qabstractanimation.cpp\n, 32) = 32
This only happens on sparc architecture.
Unfortunately, I did not manage to reproduce this with a smaller example, but
I can reliably reproduce this with moc on smetana.debian.org.
--
Dmitry Shachnev
signature.asc
Description: OpenPGP digital signature
Bug#773591: new patch(1) in jessie refuses to work on symlinks
Package: patch Version: 2.7.1-6 Severity: important patch(1) utility in jessie refuses to work on symlinks. When the file to be patched is a symlink, it produces the following error message: File FOO is not a regular file -- refusing to patch 1 out of 1 hunk ignored -- saving rejects to file FOO.rej This makes patch(1) basically useless for many our users. The problem is that our workflow is hugely based around local patching of symlinked trees. For example, given an original linux kernel source tree, symlink it to a temp directory (maybe on a separate tmpfs) apply some local patch and build it (with ccache). wheezy version of patch(1) just replaced a symlink with a patched file and all was well. jessie version just refuses to work. For now I downgraded patch(1) package to the one from wheezy and added an apt-preferencs pin for it. Thanks, /mjt -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#773585: php-elisp: Wrong indention of function arguments in subsequent lines
Hi Ola! Ola Lundqvist wrote: Hi Please try drupal mode or any other of the variants. How? I think the command is enable-(mode name) In interactive mode M-x shows: Possible completions are: enable-command enable-flow-control enable-theme Regards Joey -- In the beginning was the word, and the word was content-type: text/plain Please always Cc to me when replying to me on the lists. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#773589: additional information (baobab does not show mounted devices)
I just noticed that if I start baobab with sudo, I can see those partitions which are mounted in /media or have mountoption user in fstab. Further investigation showed up that this even works if I start baobab with sudo -u user where user is the same as logged in, so it is obvious that it has to do something with the environment: If I unset DBUS_SESSION_BUS_ADDRESS before starting baobab it works with all partitions with option 'user' or 'users' in fstab (not works if they are mounted with 'default') Hope that helps. Regards Michael -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#773592: systemd: /etc/rc.local compatibility
Am 20.12.2014 um 15:32 schrieb Adrian: Package: systemd Version: 215-7 Severity: normal Dear maintainer I get failed to start /etc/rc.local compatibility at boot. Can you post the contents of /etc/rc.local? What do you get if you run # /etc/rc.local # echo $? If you get that message, it means, the script failed to execute. You should find that failure and fix that to make the error message go away. -- 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#773592: systemd: /etc/rc.local compatibility
Am 20.12.2014 um 15:32 schrieb Adrian: I have two similar rc.local.service files. rc-local.service and rc.local.service are the same files. rc.local.service is simply a symlink to rc-local.service. This symlink was added because the old sysv init script is named /etc/init.d/rc.local -- 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#767019: xscreensaver: postinst overwrites /etc/X11/app-defaults/XScreenSaver without asking
On Sat, Dec 20, 2014 at 9:02 AM, Michael Gilbert wrote: if [ -L /etc/X11/app-defaults/XScreenSaver ]; then if [ $(readlink /etc/X11/app-defaults/XScreenSaver) = XScreenSaver-nogl -o \ $(readlink /etc/X11/app-defaults/XScreenSaver) = XScreenSaver-gl]; then rm /etc/X11/app-defaults/XScreenSaver fi This doesn't handle the case where the user intentionally had both xscreensaver-gl and xscreensaver installed, and manually set the symlink to XscreenSaver-nogl. I suppose it would be best to treat XscreenSaver-nogl and XscreenSaver-gl as conffiles. But I am not sure about the symlink. It could fit something like update-alternatives, but that is not meant for configuration files, right? Best regards, Tormod -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#773593: missing source for qprint.c
Source: qprint Version: 1.1.dfsg-1 Severity: serious Justification: Policy §2.2 qprint.c was automatically generated from qprint.w, but the latter is not included in the .orig.tar. NB, this is a regression: qprint.w is included in the source tarball for qprint_1.0.dfsg.2. -- Jakub Wilk -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#772471: closed by Michael Gilbert mgilb...@debian.org (Re: Bug#772471: chromium crash on startup)
I would say that there is still a problem with debian packaging in that it allows this chromium version to be installed in a kernel earlier than 2.16, although the result is of no value since the new chromium will not work. Perhaps for versions 39.0.2171 and higher of chromium, the debian package should also require a kernel version at least 3.16. This would be a rigorous way of implementing the requirement that people running into this problem should upgrade their kernel. [ I was able to avoid this issue by patching the debian source to avoid this check, as it currently does in chromium.org for this version, and rebuilding on my 32 bit linux with the additional flags: defines+= remove_webcore_debug_symbols=1 \ component=shared_library \ although at some later point will have to upgrade my kernel to 3.16.] thanks, --jack - Original Message - From: Debian Bug Tracking System ow...@bugs.debian.org To: js jsh...@yahoo.com Cc: Sent: Friday, December 19, 2014 7:45 PM Subject: Bug#772471 closed by Michael Gilbert mgilb...@debian.org (Re: Bug#772471: chromium crash on startup) This is an automatic notification regarding your Bug report which was filed against the chromium package: #772471: chromium: sandbox issue with nvidia driver It has been closed by Michael Gilbert mgilb...@debian.org. Their explanation is attached below along with your original report. If this explanation is unsatisfactory and you have not received a better one in a separate message then please contact Michael Gilbert mgilb...@debian.org by replying to this email. -- 772471: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=772471 Debian Bug Tracking System Contact ow...@bugs.debian.org with problemsOn Thu, Dec 18, 2014 at 8:35 AM, JS wrote: It was caused by including a check for error codes for non-existent system calls that is not in chromium; see below. This issue is in the debian 3.14 kernel and has been fixed in the 3.16 kernel. Thanks a bunch for digging into this! So the moral of the story is that chromium won't work on kernels patched for CVE-2014-4508 and don't include a particular regression bugfix. The debian 3.16 and newer kernels are known to include that bugfix, so users running into this problem should start there. Best wishes, Mike Package: chromium Version: 39.0.2171.71-2 Severity: important Dear Maintainer, = After upgrade to chromium:i386 39.0.2171.71-2 from chromium:i386 38.0.2125.101-1, chromium now crashes every time on startup with the error: FATAL:sandbox_bpf.cc(502)] Check failed: -1 == rv (-1 vs. 354) Note that google-chrome-stable 39.0.2171.71-1 works correctly on the same computer. I am also using the proprietary nvidia driver 340.46-1, which has been mentioned in some chromium threads (see references in code.google.com bug report below), although the 38.0.2125.101 chromium worked fine with this nvidia driver. submitted chromium bug report: http://code.google.com/p/chromium/issues/detail?id=439795thanks=439795ts=1417965276 = -- System Information: Debian Release: jessie/sid APT prefers testing APT policy: (500, 'testing') Architecture: i386 (i686) Kernel: Linux 3.14-1-686-pae (SMP w/6 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 chromium depends on: ... -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#764451: libpam-mount: Fails to run mount: invalid option -- '-p'
Hi On 18/12/14 20:07, Christian Kastner wrote: would you be willing to upload the fix to DELAYED/5 so that we can see this bug closed soon? Yes, I just did. Regards, -- .''`. Philipp Huebner debala...@debian.org : :' : pgp fp: 6719 25C5 B8CD E74A 5225 3DF9 E5CA 8C49 25E4 205F `. `'` `- signature.asc Description: OpenPGP digital signature
Bug#701680: Confirmation Re: [djmount] Segfault when attempting to read a file
I don't know how to reply on the Debian Bug report logs. I want to confirm that I too had segfaults using djmount on amd64. Applying the patch suggested by Bernhard Übelacker [004-avoid-crash-by-using-size_t.patch (text/x-patch, attachment)] solved the problem for me. -- Tim Davenport Gatlinburg, Tennessee USA -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#773592: systemd: /etc/rc.local compatibility
Ok thanks for the quick response. The problem was the script itself. It was returning 1 instead of 0. You can close the bug. 2014-12-20 15:45 GMT+01:00 Michael Biebl bi...@debian.org: Am 20.12.2014 um 15:32 schrieb Adrian: I have two similar rc.local.service files. rc-local.service and rc.local.service are the same files. rc.local.service is simply a symlink to rc-local.service. This symlink was added because the old sysv init script is named /etc/init.d/rc.local -- Why is it that all of the instruments seeking intelligent life in the universe are pointed away from Earth?
Bug#701680: Confirmation Re: [djmount] Segfault when attempting to read a file
On 12/20/2014 04:09 PM, Timothy Davenport wrote:
I don't know how to reply on the Debian Bug report logs.
Just include bug number@bugs.debian.org in the CC of your mail.
I want to confirm that I too had segfaults using djmount on amd64.
Applying the patch suggested by Bernhard Übelacker
[004-avoid-crash-by-using-size_t.patch (text/x-patch, attachment)]
solved the problem for me.
Sounds great. I am already preparing an NMU of djmount and would
upload the package to DELAYED or right away, depending on what
Dario thinks. If I won't hear back from Dario anytime soon, I
will upload to DELAYED/5 as this fixes an RC bug which would affect
Jessie if not addressed.
Attaching the debdiff of my suggested NMU in any case.
Cheers,
Adrian
--
.''`. John Paul Adrian Glaubitz
: :' : Debian Developer - glaub...@debian.org
`. `' Freie Universitaet Berlin - glaub...@physik.fu-berlin.de
`-GPG: 62FF 8A75 84E0 2956 9546 0006 7426 3B37 F5B5 F913
diff -Nru djmount-0.71/debian/changelog djmount-0.71/debian/changelog
--- djmount-0.71/debian/changelog 2013-01-21 22:05:45.0 +0100
+++ djmount-0.71/debian/changelog 2014-12-20 16:34:43.0 +0100
@@ -1,3 +1,13 @@
+djmount (0.71-6.1) unstable; urgency=medium
+
+ * Non-maintainer upload.
+ * debian/patches:
++ Added: 004-avoid-crash-by-using-size_t.patch:
+ - Fixes segfault on 64-bit architectures when reading files
+ from a mounted DLNA share (Closes: #674753, #701680).
+
+ -- John Paul Adrian Glaubitz glaub...@physik.fu-berlin.de Sat, 20 Dec 2014 16:30:13 +0100
+
djmount (0.71-6) unstable; urgency=low
* debian/control:
diff -Nru djmount-0.71/debian/patches/004-avoid-crash-by-using-size_t.patch djmount-0.71/debian/patches/004-avoid-crash-by-using-size_t.patch
--- djmount-0.71/debian/patches/004-avoid-crash-by-using-size_t.patch 1970-01-01 01:00:00.0 +0100
+++ djmount-0.71/debian/patches/004-avoid-crash-by-using-size_t.patch 2014-12-20 16:29:35.0 +0100
@@ -0,0 +1,16 @@
+Description: Avoid crash by using size_t instead of unsigned int
+Author: Bernhard Ãbelacker bernha...@vr-web.de
+Bug-Debian: https://bugs.debian.org/701680
+Last-Update: 2014-12-12
+
+--- djmount-0.71.orig/djmount/file_buffer.c
djmount-0.71/djmount/file_buffer.c
+@@ -212,7 +212,7 @@ FileBuffer_Read (FileBuffer* file, char*
+ * to return the exact number of bytes requested.
+ */
+ do {
+- unsigned int read_size = size - n;
++ size_t read_size = size - n;
+ if (n 0) {
+ Log_Printf (LOG_DEBUG,
+ UpnpReadHttpGet loop ! url '%s'
diff -Nru djmount-0.71/debian/patches/series djmount-0.71/debian/patches/series
--- djmount-0.71/debian/patches/series 2013-01-21 22:05:45.0 +0100
+++ djmount-0.71/debian/patches/series 2014-12-20 16:30:04.0 +0100
@@ -2,3 +2,4 @@
000_djmount.1.diff
001-libupnp-1.6.6.diff
002-libupnp-1.6.13.diff
+004-avoid-crash-by-using-size_t.patch
Bug#770659: seems to be related to using the Debian srtp library
I did some tests to track this down a bit. starting chromium with --enable-logging --v=4 I do get this in my .config/chromium/chrome_debug.log: [49:62:1219/210401:VERBOSE3:channel.cc(783)] Installing keys from DTLS-SRTP on audio RTP [49:62:1219/210401:VERBOSE1:srtpfilter.cc(699)] Failed to init SRTP, err=5 [49:62:1219/210401:VERBOSE2:channel.cc(853)] DTLS-SRTP key installation failed So the problem seems to be somewhere in or related to srtp. I had a quick look at the corresponding code, but I'm not sure what is the problem there. The error message from my log comes from here: http://sources.debian.net/src/chromium-browser/39.0.2171.71-2/third_party/libjingle/source/talk/session/media/srtpfilter.cc/#L699 and is the return value of the srtp_init() function from the srtp source here: http://sources.debian.net/src/srtp/1.4.5~20130609~dfsg-1.1/srtp/srtp.c/#L1235 The functions crypto_kernel_init() and crypto_kernel_load_debug_module() can be found here: http://sources.debian.net/src/srtp/1.4.5~20130609~dfsg-1.1/crypto/kernel/crypto_kernel.c/ I couldn't see any obvious problem there but I only had a very rough look at the code. So suspecting this might be caused by the system srtp library I disabled it by removing use_system_libsrtp=1 from the debian/rules file and got a chromium with working webrtc. At the moment I have no idea where the real problem is or how it should be fixed, this is just what I found out so far. It might also be the case that it's not chromium or srtp's fault but the real cause of this problem is somewhere else. Probably someone with more knowledge on all this should have a look at it. Some things I also noticed that might be of interest. I did a build of chromium-browser-37.0.2062.120 on jessie and it also seems to be affected by this bug. If I remember correctly I did test chromium 37 (not sure anymore which versions, but I think all that went to the Debian archive) from snapshots.debian.org some time ago and they all worked. I also tested chromium from an Ubuntu live stick and webrtc does work there. However as far as I could see this the build of chromium on Ubuntu doesn't use any system libraries. signature.asc Description: This is a digitally signed message part.
Bug#773594: qprint: invalid sign escape still produces output
Package: qprint Version: 1.0.dfsg.2-2 Severity: minor Sometimes qprint -d produces output, even though the input consists entirely of invalid sign escapes: $ printf '=m4' | qprint -d | hd Error: bad equal sign escape =m4 at byte 0 (0x0) of input. f4|.| 0001 -- System Information: Debian Release: 8.0 APT prefers unstable APT policy: (990, 'unstable'), (500, 'experimental') Architecture: i386 (x86_64) Foreign Architectures: amd64 Kernel: Linux 3.2.0-4-amd64 (SMP w/2 CPU cores) Locale: LANG=C, LC_CTYPE=pl_PL.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: sysvinit (via /sbin/init) Versions of packages qprint depends on: ii libc6 2.19-13 -- Jakub Wilk -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#765109: fglrx-driver: Black screen after xorg startup
Working properly now and portal is even faster than when using standard amd packaged drivers. Thanks for the update! Vitor
Bug#701680: Confirmation Re: [djmount] Segfault when attempting to read a file
On 12/20/2014 04:41 PM, John Paul Adrian Glaubitz wrote:
Attaching the debdiff of my suggested NMU in any case.
Attaching a revised version as my first patch contained a formatting
error in the debian/changelog file.
Cheers,
Adrian
--
.''`. John Paul Adrian Glaubitz
: :' : Debian Developer - glaub...@debian.org
`. `' Freie Universitaet Berlin - glaub...@physik.fu-berlin.de
`-GPG: 62FF 8A75 84E0 2956 9546 0006 7426 3B37 F5B5 F913
diff -Nru djmount-0.71/debian/changelog djmount-0.71/debian/changelog
--- djmount-0.71/debian/changelog 2013-01-21 22:05:45.0 +0100
+++ djmount-0.71/debian/changelog 2014-12-20 16:47:53.0 +0100
@@ -1,3 +1,13 @@
+djmount (0.71-6.1) unstable; urgency=medium
+
+ * Non-maintainer upload.
+ * debian/patches:
++ Added: 004-avoid-crash-by-using-size_t.patch:
+ - Fixes segfault on 64-bit architectures when reading files
+from a mounted DLNA share (Closes: #674753, #701680).
+
+ -- John Paul Adrian Glaubitz glaub...@physik.fu-berlin.de Sat, 20 Dec 2014 16:30:13 +0100
+
djmount (0.71-6) unstable; urgency=low
* debian/control:
diff -Nru djmount-0.71/debian/patches/004-avoid-crash-by-using-size_t.patch djmount-0.71/debian/patches/004-avoid-crash-by-using-size_t.patch
--- djmount-0.71/debian/patches/004-avoid-crash-by-using-size_t.patch 1970-01-01 01:00:00.0 +0100
+++ djmount-0.71/debian/patches/004-avoid-crash-by-using-size_t.patch 2014-12-20 16:29:35.0 +0100
@@ -0,0 +1,16 @@
+Description: Avoid crash by using size_t instead of unsigned int
+Author: Bernhard Ãbelacker bernha...@vr-web.de
+Bug-Debian: https://bugs.debian.org/701680
+Last-Update: 2014-12-12
+
+--- djmount-0.71.orig/djmount/file_buffer.c
djmount-0.71/djmount/file_buffer.c
+@@ -212,7 +212,7 @@ FileBuffer_Read (FileBuffer* file, char*
+ * to return the exact number of bytes requested.
+ */
+ do {
+- unsigned int read_size = size - n;
++ size_t read_size = size - n;
+ if (n 0) {
+ Log_Printf (LOG_DEBUG,
+ UpnpReadHttpGet loop ! url '%s'
diff -Nru djmount-0.71/debian/patches/series djmount-0.71/debian/patches/series
--- djmount-0.71/debian/patches/series 2013-01-21 22:05:45.0 +0100
+++ djmount-0.71/debian/patches/series 2014-12-20 16:30:04.0 +0100
@@ -2,3 +2,4 @@
000_djmount.1.diff
001-libupnp-1.6.6.diff
002-libupnp-1.6.13.diff
+004-avoid-crash-by-using-size_t.patch
Bug#773595: qprint: bogus error message on invalid 2-byte escape sequence
Package: qprint Version: 1.1.dfsg-1 Severity: minor This is a variation of #773185 that is still not fixed in 1.1: $ printf '=a' | qprint -d Error: bad equal sign escape = 0x61 0x at byte 18446744073709551615 (0x) of input. -- System Information: Debian Release: 8.0 APT prefers unstable APT policy: (990, 'unstable'), (500, 'experimental') Architecture: i386 (x86_64) Foreign Architectures: amd64 Kernel: Linux 3.2.0-4-amd64 (SMP w/2 CPU cores) Locale: LANG=C, LC_CTYPE=pl_PL.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: sysvinit (via /sbin/init) Versions of packages qprint depends on: ii libc6 2.19-13 -- Jakub Wilk -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#773473: [Pkg-gnupg-maint] Bug#773473: [PATCH] * sm/gpgsm.c: (parse_keyserver_line) return false on 'fail'.
Hi Joshua--
On 12/20/2014 03:45 AM, Joshua Rogers wrote:
--
If something in the keyserver_line failed, parse_keyserver_line would free
'server', but then return it afterwards, leading to a use-after-free.
sm/gpgsm.c, in the function main() correctly checks whether the return of
parse_keyserver_line is false.
---
sm/gpgsm.c | 1 +
1 file changed, 1 insertion(+)
diff --git a/sm/gpgsm.c b/sm/gpgsm.c
index 3398d17..75c0b4d 100644
--- a/sm/gpgsm.c
+++ b/sm/gpgsm.c
@@ -862,6 +862,7 @@ parse_keyserver_line (char *line,
{
log_info (_(%s:%u: skipping this line\n), filename, lineno);
keyserver_list_free (server);
+ return 0;
}
return server;
Since the return value of parse_keyserver_line is a
struct keyserver_spec *, it's probably cleaner to represent it as NULL,
instead of 0.
This is functionally no different, of course, but it makes it clearer
what's going on.
(alternately, you could just set
server = NULL;
and let the final line of the function return it)
--dkg
signature.asc
Description: OpenPGP digital signature
Bug#773596: gajim: fails to connect when doing kerberos authentication (no fallback to password prompt)
Package: gajim
Version: 0.16-1
Severity: normal
Dear Maintainer,
when I have a valid Kerberos TGT and start gajim, it fails to
connect to the xmpp-server but prints the following error:
Traceback (most recent call last):
File /usr/lib/python2.7/dist-packages/nbxmpp/dispatcher_nb.py, line 497, in
dispatch
handler['func'](session, stanza)
File /usr/lib/python2.7/dist-packages/nbxmpp/auth_nb.py, line 304, in
SASLHandler
data=base64.b64decode(incoming_data.encode('utf-8')).decode('utf-8')
File /usr/lib/python2.7/encodings/utf_8.py, line 16, in decode
return codecs.utf_8_decode(input, errors, True)
UnicodeDecodeError: 'utf8' codec can't decode byte 0x81 in position 1: invalid
start byte
klist shows that it already obtained new tickets for the xmpp-server.
This same setup works fine on a system running debian 7.7 with gajim
0.15.1-4-1.
If I remove my TGT and start gajim anew, it asks me for a password and then
connects
successfully.
Apart from the real problem that caused this traceback, I think gajim should
catch
such errors and fall back to prompting for a password if external
authentication
failed.
Thanks,
Thomas
-- System Information:
Debian Release: 8.0
APT prefers testing-updates
APT policy: (500, 'testing-updates'), (500, 'testing')
Architecture: amd64 (x86_64)
Kernel: Linux 3.16.0-4-amd64 (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
Init: systemd (via /run/systemd/system)
Versions of packages gajim depends on:
ii dbus 1.8.12-1
ii dnsutils 1:9.9.5.dfsg-6
ii python-dbus1.2.0-2+b3
ii python-gtk22.24.0-4
ii python-nbxmpp 0.5.1-2
pn python:any none
Versions of packages gajim recommends:
ii ca-certificates 20141019
ii notification-daemon 0.7.6-2
ii python-crypto2.6.1-5+b2
ii python-openssl 0.14-1
ii python-pyasn10.1.7-1
Versions of packages gajim suggests:
ii aspell-en [aspell-dictionary] 7.1-0-1.1
ii avahi-daemon 0.6.31-4+b2
pn dvipng none
ii gnome-keyring 3.14.0-1+b1
pn gstreamer0.10-plugins-ugly none
pn kwalletcli none
pn libgtkspell0 none
ii libxss11:1.2.2-1
pn nautilus-sendtonone
pn network-managernone
pn python-avahi none
pn python-farstream none
pn python-gconf none
pn python-gnome2 none
pn python-gnomekeyringnone
pn python-gupnp-igd none
ii python-kerberos1.1.5-0.1
ii python-pycurl 7.19.5-3
pn texlive-latex-base none
-- no debconf information
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#773552: graphicsmagick-imagemagick-compat: convert to cmyk leaves k channel empty
After private discussion with Michael (and an exchange of image files) it has been determined that the main problem he encountered is that GraphicsMagick identify was not properly computing statistics for the Black channel of CMYK images so only 0 was reported. This is fixed by Mercurial changeset 2739f0e0813d. Other factors encountered were that the default rendering intent is different between ImageMagick and GraphicsMagick, ImageMagick is a Q16 build while GraphicMagick is a Q8 build, and ImageMagick tries to preserve the original JPEG quality settings by default, whereas GraphicsMagick does not. Bob On Fri, 19 Dec 2014, Michael Below wrote: Package: graphicsmagick-imagemagick-compat Severity: normal Dear Maintainer, I tried to use convert from graphicsmagick to convert an AdobeRGB image to CMYK, using the ECI profile ISOcoated_v2_300_eci.icc from the ECI website. It converted the image to use only the CMY colors, not CMYK. The K channel was there, but it was empty. Now I have converted the same image with the same ICC profile using the original imagemagick convert (6.8.9-9 Q16), and the K channel is doing it's part, with a max value of 0.959 and a mean of 0.797 (so it's not like the image has no black). It looks like the conversion that is labelled CMYK converts only to CMY. That would be misleading (there is a seperate option for CMY). If CMYK can't be supported right now, please consider adding a warning, so that people don't produce botched CMYK conversions. Imagemagick is actually the recommended linux tool for that, so it is likely people will try to use graphicsmagick for it. Thanks for your effort! Michael -- System Information: Debian Release: 8.0 APT prefers testing APT policy: (900, 'testing'), (500, 'stable-updates'), (500, 'proposed-updates'), (500, 'stable'), (10, 'unstable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.16.0-4-amd64 (SMP w/4 CPU cores) Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash Init: systemd (via /run/systemd/system) Versions of packages graphicsmagick-imagemagick-compat depends on: ii graphicsmagick 1.3.20-3+b1 ii html2ps 1.0b7-1 graphicsmagick-imagemagick-compat recommends no packages. graphicsmagick-imagemagick-compat suggests no packages. -- Bob Friesenhahn bfrie...@simple.dallas.tx.us, http://www.simplesystems.org/users/bfriesen/ GraphicsMagick Maintainer,http://www.GraphicsMagick.org/ -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#773597: unblock: vim-tlib/1.12-3
Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: unblock Please unblock package vim-tlib Fix for RC bug #773583. The changes since version 1.12-2 are tiny and they consist of: * Added vim-tlib.dirs and deleted vim-tlib.postrm to prevent the removal of directories owned by vim-common (Closes: #773583) $ debdiff vim-tlib_1.12-2.dsc vim-tlib_1.12-3.dsc gpgv: Signature made Thu 10 Jul 2014 12:43:00 PM CEST using DSA key ID 78398A01 gpgv: Can't check signature: public key not found dpkg-source: warning: failed to verify signature on /tmp/vim-tlib_1.12-2.dsc diff -Nru vim-tlib-1.12/debian/changelog vim-tlib-1.12/debian/changelog --- vim-tlib-1.12/debian/changelog 2014-07-10 12:42:11.0 +0200 +++ vim-tlib-1.12/debian/changelog 2014-12-20 13:04:18.0 +0100 @@ -1,3 +1,11 @@ +vim-tlib (1.12-3) unstable; urgency=medium + + * Added vim-tlib.dirs and deleted vim-tlib.postrm to prevent the removal +of directories owned by vim-common +(Closes: #773583) + + -- Andrea Capriotti capri...@debian.org Sat, 20 Dec 2014 12:57:05 +0100 + vim-tlib (1.12-2) unstable; urgency=low * Updated the Vcs field in debian/control diff -Nru vim-tlib-1.12/debian/vim-tlib.dirs vim-tlib-1.12/debian/vim-tlib.dirs --- vim-tlib-1.12/debian/vim-tlib.dirs 1970-01-01 01:00:00.0 +0100 +++ vim-tlib-1.12/debian/vim-tlib.dirs 2014-12-17 02:26:59.0 +0100 @@ -0,0 +1 @@ +var/lib/vim/addons/samples/ diff -Nru vim-tlib-1.12/debian/vim-tlib.postrm vim-tlib-1.12/debian/vim- tlib.postrm --- vim-tlib-1.12/debian/vim-tlib.postrm2014-07-09 15:20:06.0 +0200 +++ vim-tlib-1.12/debian/vim-tlib.postrm1970-01-01 01:00:00.0 +0100 @@ -1,43 +0,0 @@ -#!/bin/sh -# postrm script for vim-tlib -# -# see: dh_installdeb(1) - -set -e - -# summary of how this script can be called: -#* postrm `remove' -#* postrm `purge' -#* old-postrm `upgrade' new-version -#* new-postrm `failed-upgrade' old-version -#* new-postrm `abort-install' -#* new-postrm `abort-install' old-version -#* new-postrm `abort-upgrade' old-version -#* disappearer's-postrm `disappear' overwriter -# overwriter-version -# for details, see http://www.debian.org/doc/debian-policy/ or -# the debian-policy package - - -case $1 in -purge) -if [ -d /var/lib/vim/addons/samples/ ]; then - rmdir -p --ignore-fail-on-non-empty /var/lib/vim/addons/samples || : -fi -;; - -remove|upgrade|failed-upgrade|abort-install|abort-upgrade|disappear) -;; - -*) -echo postrm called with unknown argument \`$1' 2 -exit 1 -;; -esac - -# dh_installdeb will replace this with shell code automatically -# generated by other debhelper scripts. Note: I replaced my key (RT #5533) -- https://tracker.debian.org/news/669149 http://anonscm.debian.org/cgit/collab-maint/vim- tlib.git/commit/?id=f91107598be9f77aa173e18c393a132f5d66c39b unblock vim-tlib/1.12-3 -- 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/4 CPU cores) Locale: LANG=it_IT.utf8, LC_CTYPE=it_IT.utf8 (charmap=UTF-8) -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#773598: postgresql-common: [INTL:es] Spanish po-debconf translation
Package: postgresql-common
Version: 164
Priority: wishlist
Tags: l10n patch
Please find attached the updated version of the po translation into
Spanish.
--
Free Software Foundation Associate Member #9537
Manuel Venturi Porras Peralta
vent...@member.fsf.org
# postgresql-common po-debconf translation to spanish
# Copyright (C) 2006 Software in the Public Interest, SPI Inc.
# This file is distributed under the same license as the postgresql-common
# package.
#
# Changes:
# - Initial translation
# Javier Fernández-Sanguino , 2006
# - Updated
# Javier Fernández-Sanguino , 2007-2008
# Manuel Venturi Porras Peralta vent...@openmailbox.org, 2014.
#
# Traductores, si no conoce el formato PO, merece la pena leer la
# documentación de gettext, especialmente las secciones dedicadas a este
# formato, por ejemplo ejecutando:
# info -n '(gettext)PO Files'
# info -n '(gettext)Header Entry'
#
# Equipo de traducción al español, por favor lean antes de traducir
# los siguientes documentos:
#
# - El proyecto de traducción de Debian al español
# http://www.debian.org/intl/spanish/
# especialmente las notas y normas de traducción en
# http://www.debian.org/intl/spanish/notas
#
# - La guÃa de traducción de po's de debconf:
# /usr/share/doc/po-debconf/README-trans
# o http://www.debian.org/intl/l10n/po-debconf/README-trans
#
# Si tiene dudas o consultas sobre esta traducción consulte con el último
# traductor (campo Last-Translator) y ponga en copia a la lista de
# traducción de Debian al español (debian-l10n-span...@lists.debian.org)
#
#
msgid
msgstr
Project-Id-Version: postgresql-common 68\n
Report-Msgid-Bugs-To: postgresql-com...@packages.debian.org\n
POT-Creation-Date: 2014-05-20 11:16+0200\n
PO-Revision-Date: 2014-11-22 12:59+0100\n
Last-Translator: Manuel \Venturi\ Porras Peralta venturi@openmailbox.
org\n
Language-Team: Español; Castellano debian-l10n-span...@lists.debian.org\n
Language: es\n
MIME-Version: 1.0\n
Content-Type: text/plain; charset=UTF-8\n
Content-Transfer-Encoding: 8bit\n
X-POFile-SpellExtra: PostgreSQL oldversion clúster stop pgdropcluster\n
X-POFile-SpellExtra: client old main clústers pgupgradecluster latest\n
X-POFile-SpellExtra: postgresql\n
Plural-Forms: nplurals=2; plural=(n != 1);\n
X-Generator: Gtranslator 2.91.6\n
#. Type: error
#. Description
#: ../postgresql-common.templates:2001
msgid Obsolete major version ${old}
msgstr Versión principal ${old} obsoleta
#. Type: error
#. Description
#: ../postgresql-common.templates:2001
msgid
The PostgreSQL version ${old} is obsolete, but the server or client packages
are still installed. Please install the latest packages (postgresql-
${latest} and postgresql-client-${latest}) and upgrade the existing
${oldversion} clusters with pg_upgradecluster (see manpage).
msgstr
La versión de PostgreSQL ${old} está obsoleta, pero el paquete del cliente o
del servidor aún están instalados. Debe instalar las últimas versiones de
los paquetes (postgresql-${latest} y postgresql-client-${latest}) y
actualizar sus clústers ${oldversion} con la orden
«pg_upgradecluster» (consulte la página del manual).
#. Type: error
#. Description
#: ../postgresql-common.templates:2001
msgid
Please be aware that the installation of postgresql-${latest} will
automatically create a default cluster ${latest}/main. If you want to
upgrade the ${old}/main cluster, you need to remove the already existing
${latest} cluster (pg_dropcluster --stop ${latest} main, see manpage for
details).
msgstr
Tenga en cuenta que la instalación de postgresql-${latest} creará
automáticamente un clúster por omisión ${latest}/main. Tiene que borrar el
clúster ${latest} existente («pg_dropcluster --stop ${latest}) si desea
actualizar el clúster ${old}/main, consulte la página de manual para conocer
los detalles.
#. Type: error
#. Description
#: ../postgresql-common.templates:2001
msgid
The old server and client packages are no longer supported. After the
existing clusters are upgraded, the postgresql-${old} and postgresql-client-
${old} packages should be removed.
msgstr
Ya no se da soporte a los paquetes antiguos de cliente y servidor. DeberÃa
eliminar los paquetes postgresql-${old} y postgresql-client-${old} después
de actualizar los clústers que tenga.
#. Type: error
#. Description
#: ../postgresql-common.templates:2001
msgid
Please see /usr/share/doc/postgresql-common/README.Debian.gz for details.
msgstr
Para más información consulte «/usr/share/doc/postgresql-common/README.
Debian.gz».
#. Type: boolean
#. Description
#: ../postgresql-common.templates:3001
msgid Enable SSL by default in new PostgreSQL clusters?
msgstr
¿Desea activar SSL como predeterminado en los nuevos clústers de PostgreSQL?
#. Type: boolean
#. Description
#: ../postgresql-common.templates:3001
msgid
PostgreSQL supports SSL-encrypted connections. This is usually a good thing.
However, if the database is solely accessed
Bug#773599: syslinux: [INTL:es] Spanish po translation
Package: syslinux Version: 3:6.03+dfsg-4 Priority: wishlist Tags: l10n patch Please find attached the updated version of the po translation into Spanish. -- Free Software Foundation Associate Member #9537 Manuel Venturi Porras Peralta vent...@member.fsf.org # syslinux po-debconf translation to Spanish # Copyright 2014 Manuel Venturi Porras Peralta vent...@openmailbox.org # This file is distributed under the same license as the syslinux package. # # Changes: # - Initial translation # # Traductores, si no conocen el formato PO, merece la pena leer la # documentación de gettext, especialmente las secciones dedicadas a este # formato, por ejemplo ejecutando: # info -n '(gettext)PO Files' # info -n '(gettext)Header Entry' # # Equipo de traducción al español, por favor lean antes de traducir # los siguientes documentos: # # - El proyecto de traducción de Debian al español # http://www.debian.org/intl/spanish/coordinacion # especialmente las notas de traducción en # http://www.debian.org/intl/spanish/notas # # - La guÃa de traducción de po's de debconf: # /usr/share/doc/po-debconf/README-trans # o http://www.debian.org/intl/l10n/po-debconf/README-trans # Manuel Venturi Porras Peralta vent...@openmailbox.org, 2014. # msgid msgstr Project-Id-Version: syslinux\n Report-Msgid-Bugs-To: sysli...@packages.debian.org\n POT-Creation-Date: 2014-08-24 00:12+0200\n PO-Revision-Date: 2014-11-23 22:41+0100\n Last-Translator: Manuel \Venturi\ Porras Peralta venturi@openmailbox. org\n Language-Team: Español; Castellano debian-l10n-span...@lists.debian.org\n Language: \n MIME-Version: 1.0\n Content-Type: text/plain; charset=UTF-8\n Content-Transfer-Encoding: 8bit\n Plural-Forms: nplurals=2; plural=(n != 1);\n X-Generator: Gtranslator 2.91.6\n #. Type: title #. Description #: ../extlinux.templates:1001 msgid EXTLINUX msgstr EXTLINUX #. Type: note #. Description #: ../extlinux.templates:2001 msgid No bootloader integration code anymore msgstr Ya no hay código de integración del gestor de arranque #. Type: note #. Description #: ../extlinux.templates:2001 msgid The extlinux package does not ship bootloader integration anymore. msgstr El paquete extlinux ya no incluye la integración del gestor de arranque. #. Type: note #. Description #: ../extlinux.templates:2001 msgid If you are upgrading to this version of EXTLINUX your system will not boot any longer if EXTLINUX was the only configured bootloader. Please install GRUB. msgstr Si está actualizando a esta versión de EXTLINUX, el sistema ya no iniciará si EXTLINUX era el único gestor de arranque configurado. Instale GRUB. signature.asc Description: OpenPGP digital signature
Bug#773600: syslinux: [INTL:es] Spanish po translation
Package: syslinux Version: 3:6.03+dfsg-4 Priority: wishlist Tags: l10n patch Please find attached the updated version of the po translation into Spanish. Last submission was mistaken, sorry. -- Free Software Foundation Associate Member #9537 Manuel Venturi Porras Peralta vent...@member.fsf.org # syslinux po-debconf translation to Spanish # Copyright 2014 Manuel Venturi Porras Peralta vent...@openmailbox.org # This file is distributed under the same license as the syslinux package. # # Changes: # - Initial translation # Manuel Venturi Porras Peralta vent...@openmailbox.org, 2014. # # Traductores, si no conocen el formato PO, merece la pena leer la # documentación de gettext, especialmente las secciones dedicadas a este # formato, por ejemplo ejecutando: # info -n '(gettext)PO Files' # info -n '(gettext)Header Entry' # # Equipo de traducción al español, por favor lean antes de traducir # los siguientes documentos: # # - El proyecto de traducción de Debian al español # http://www.debian.org/intl/spanish/coordinacion # especialmente las notas de traducción en # http://www.debian.org/intl/spanish/notas # # - La guÃa de traducción de po's de debconf: # /usr/share/doc/po-debconf/README-trans # o http://www.debian.org/intl/l10n/po-debconf/README-trans # msgid msgstr Project-Id-Version: syslinux\n Report-Msgid-Bugs-To: sysli...@packages.debian.org\n POT-Creation-Date: 2014-08-24 00:12+0200\n PO-Revision-Date: 2014-11-23 22:41+0100\n Last-Translator: Manuel \Venturi\ Porras Peralta venturi@openmailbox. org\n Language-Team: Español; Castellano debian-l10n-span...@lists.debian.org\n Language: es\n MIME-Version: 1.0\n Content-Type: text/plain; charset=UTF-8\n Content-Transfer-Encoding: 8bit\n Plural-Forms: nplurals=2; plural=(n != 1);\n X-Generator: Gtranslator 2.91.6\n #. Type: title #. Description #: ../extlinux.templates:1001 msgid EXTLINUX msgstr EXTLINUX #. Type: note #. Description #: ../extlinux.templates:2001 msgid No bootloader integration code anymore msgstr Ya no hay código de integración del gestor de arranque #. Type: note #. Description #: ../extlinux.templates:2001 msgid The extlinux package does not ship bootloader integration anymore. msgstr El paquete extlinux ya no incluye la integración del gestor de arranque. #. Type: note #. Description #: ../extlinux.templates:2001 msgid If you are upgrading to this version of EXTLINUX your system will not boot any longer if EXTLINUX was the only configured bootloader. Please install GRUB. msgstr Si está actualizando a esta versión de EXTLINUX, el sistema ya no iniciará si EXTLINUX era el único gestor de arranque configurado. Instale GRUB. signature.asc Description: OpenPGP digital signature
Bug#773601: openssl: [INTL:es] Spanish po translation
Package: openssl
Version: 1.0.1j-1
Priority: wishlist
Tags: l10n patch
Please find attached the updated version of the po translation into
Spanish.
--
Free Software Foundation Associate Member #9537
Manuel Venturi Porras Peralta
vent...@member.fsf.org
# openssl translation to spanish
# Copyright (C) 2004 Software in the Public Interest
# This file is distributed under the same license as the openssl package.
#
# Changes:
# - Initial translation
# Lucas Wall kthu...@kadath.com.ar, 2004
#
# - Last revision
# Manuel Porras Peralta «Venturi», 2007
# Maximiliano MarÃn, 2007
# Manuel Venturi Porras Peralta vent...@openmailbox.org, 2014.
#
# Traductores, si no conoce el formato PO, merece la pena leer la
# documentación de gettext, especialmente las secciones dedicadas a este
# formato, por ejemplo ejecutando:
# info -n '(gettext)PO Files'
# info -n '(gettext)Header Entry'
#
# Equipo de traducción al español, por favor lean antes de traducir
# los siguientes documentos:
#
# - El proyecto de traducción de Debian al español
# http://www.debian.org/intl/spanish/coordinacion
# especialmente las notas de traducción en
# http://www.debian.org/intl/spanish/notas
#
# - La guÃa de traducción de po's de debconf:
# /usr/share/doc/po-debconf/README-trans
# o http://www.debian.org/intl/l10n/po-debconf/README-trans
#
#
msgid
msgstr
Project-Id-Version: openssl 0.9.7d-3\n
Report-Msgid-Bugs-To: open...@packages.debian.org\n
POT-Creation-Date: 2010-12-13 20:31+0100\n
PO-Revision-Date: 2014-12-02 18:29+0100\n
Last-Translator: Manuel «Venturi» Porras Peralta vent...@openmailbox.org\n
Language-Team: es debian-l10n-span...@lists.debian.org\n
Language: es\n
MIME-Version: 1.0\n
Content-Type: text/plain; charset=UTF-8\n
Content-Transfer-Encoding: 8bit\n
Plural-Forms: nplurals=2; plural=(n != 1);\n
X-Generator: Poedit 1.6.10\n
#. Type: string
#. Description
#: ../libssl1.0.0.templates:1001
msgid Services to restart to make them use the new libraries:
msgstr
Servicios que tienen que reiniciarse para que usen las nuevas bibliotecas:
#. Type: string
#. Description
#: ../libssl1.0.0.templates:1001
msgid
This release of OpenSSL fixes some security issues. Services will not use
these fixes until they are restarted. Please note that restarting the SSH
server (sshd) should not affect any existing connections.
msgstr
Esta versión de OpenSSL corrige algunos problemas de seguridad. Los
servicios no aplicarán estas correcciones hasta que se reinicien. Tenga en
cuenta que reiniciar el servicio SSH (sshd) no deberÃa afectar a ninguna de
las conexiones existentes.
#. Type: string
#. Description
#: ../libssl1.0.0.templates:1001
msgid
Please check the list of detected services that need to be restarted and
correct it, if needed. The services names must be identical to the
initialization script names in /etc/init.d and separated by spaces. No
services will be restarted if the list is empty.
msgstr
Compruebe la lista de los servicios detectados que necesitan reiniciarse y
corrÃjala si fuera necesario. Los nombres de los servicios deben ser
idénticos a los nombres de los programas de inicio en «/etc/init.d» y deben
estar separados por espacios. No se reiniciará ningún servicio si deja la
lista en blanco.
#. Type: string
#. Description
#: ../libssl1.0.0.templates:1001
msgid
Any service that later fails unexpectedly after this upgrade should be
restarted. It is recommended to reboot this host to avoid any SSL-related
trouble.
msgstr
DeberÃa reiniciar cualquier servicio que tras haber actualizado, falle
inesperadamente. Se recomienda reiniciar el sistema para evitar cualquier
problema relacionado con SSL.
#. Type: error
#. Description
#: ../libssl1.0.0.templates:2001
msgid Failure restarting some services for OpenSSL upgrade
msgstr Fallo al reiniciar algunos servicios por la actualización de OpenSSL
#. Type: error
#. Description
#. This paragraph is followed by a (non translatable) paragraph containing
#. a list of services that could not be restarted
#: ../libssl1.0.0.templates:2001
msgid
The following services could not be restarted for the OpenSSL library
upgrade:
msgstr
No fue posible reiniciar los servicios indicados a continuación por la
actualización de la biblioteca de OpenSSL:
#. Type: error
#. Description
#: ../libssl1.0.0.templates:2001
msgid
You will need to start these manually by running '/etc/init.d/service
start'.
msgstr
Tendrá que iniciarlos manualmente ejecutando « /etc/init.d/servicio start
».
#~ msgid ${services}
#~ msgstr ${services}
signature.asc
Description: OpenPGP digital signature
Bug#773602: Support for unquoted empty environment strings
Package: cron
Version: 3.0pl1-127
Severity: wishlist
Tags: patch
I recently had a Bad Time because the following syntax to specify an
empty environment variable is not supported:
VAR=
Rather, it should be:
VAR=
This is, of course, well-documented (!) but it would be a little more
user-friendly if this Just Worked. This is especially so as it is
not--in my experience--widespread practice to quote non-empty variables,
so one is likely to simply remove the *value* resulting in an invalid
file.. which is then not executed whatsoever.
Patch attached. (An alternative solution would be to test *c within the
EQ1 case, but this looked inferior when I tried it IMHO.)
Regards,
--
,''`.
: :' : Chris Lamb
`. `'` la...@debian.org / chris-lamb.co.uk
`-
diff --git a/crontab.5 b/crontab.5
index 66ba2e4..c0041a1 100644
--- a/crontab.5
+++ b/crontab.5
@@ -55,7 +55,7 @@ The
.I value
string may be placed in quotes (single or double, but matching) to preserve
leading or trailing blanks. To define an empty variable, quotes
-.B must
+can
be used. The
.I value
string is
diff --git a/env.c b/env.c
index 76238ce..6644d6b 100644
--- a/env.c
+++ b/env.c
@@ -231,7 +231,8 @@ load_env(envstr, f)
abort();
}
}
- if (state != FINI !(state == VALUE !quotechar)) {
+ if (state != FINI !(state == VALUE !quotechar)
+!(state == EQ2 !quotechar)) {
Debug(DPARS, (load_env, not an env var, state = %d\n, state))
fseek(f, filepos, 0);
Set_LineNum(fileline);
Bug#763269: upgrade-system: Want to remove required package in Debian Edu
[Martin-Éric Racine] Petter, Hi. :) Have you found upgrade-system.conf options that solved your problem? Sorry, I have not had time to investigate. Too much going on outside Debian at the moment. -- Happy hacking Petter Reinholdtsen -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#763279: same problem here
Hello Multimedia Maintainers Guiseppe, I'm seeing the same problem as Guiseppe here. When playing the german version of the DVD Up (in German Oben), I get the same error as Giuseppe: libdvdnav: Suspected RCE Region Protection!!! [mpeg2video @ 0x7fe67c0a06e0] releasing zombie picture [mpeg2video @ 0x7fe67c0a06e0] releasing zombie picture vlc: src/searching.c:566: dvdnav_get_position: Zusicherung »(signed)*pos != -1« nicht erfüllt. And then vlc dies. Other notable things that I see on the command line while the DVD is playing: 7fe67c0ac4a8] dvdnav demux error: This is probably an Arccos Protected DVD. This could take time... Thanks, *t
Bug#773603: libcppnetlib-dev: arch-dependent file in Multi-Arch: same package
Package: libcppnetlib-dev Version: 0.11.1+dfsg1-1 Severity: important User: multiarch-de...@lists.alioth.debian.org Usertags: multiarch libcppnetlib-dev is marked as Multi-Arch: same, but the following file is architecture-dependent: /usr/lib/cmake/cppnetlib/cppnetlibTargets-none.cmake An example diff between i386 and amd64 is attached. -- Jakub Wilk diff -ur libcppnetlib-dev_0.11.1+dfsg1-1_i386/usr/lib/cmake/cppnetlib/cppnetlibTargets-none.cmake libcppnetlib-dev_0.11.1+dfsg1-1_amd64/usr/lib/cmake/cppnetlib/cppnetlibTargets-none.cmake --- libcppnetlib-dev_0.11.1+dfsg1-1_i386/usr/lib/cmake/cppnetlib/cppnetlibTargets-none.cmake 2014-12-19 23:53:08.0 +0100 +++ libcppnetlib-dev_0.11.1+dfsg1-1_amd64/usr/lib/cmake/cppnetlib/cppnetlibTargets-none.cmake 2014-12-19 22:54:52.0 +0100 @@ -8,33 +8,33 @@ # Import target cppnetlib-uri for configuration None set_property(TARGET cppnetlib-uri APPEND PROPERTY IMPORTED_CONFIGURATIONS NONE) set_target_properties(cppnetlib-uri PROPERTIES - IMPORTED_LOCATION_NONE /usr/lib/i386-linux-gnu/libcppnetlib-uri.so.0.11.1 + IMPORTED_LOCATION_NONE /usr/lib/x86_64-linux-gnu/libcppnetlib-uri.so.0.11.1 IMPORTED_SONAME_NONE libcppnetlib-uri.so.0 ) list(APPEND _IMPORT_CHECK_TARGETS cppnetlib-uri ) -list(APPEND _IMPORT_CHECK_FILES_FOR_cppnetlib-uri /usr/lib/i386-linux-gnu/libcppnetlib-uri.so.0.11.1 ) +list(APPEND _IMPORT_CHECK_FILES_FOR_cppnetlib-uri /usr/lib/x86_64-linux-gnu/libcppnetlib-uri.so.0.11.1 ) # Import target cppnetlib-server-parsers for configuration None set_property(TARGET cppnetlib-server-parsers APPEND PROPERTY IMPORTED_CONFIGURATIONS NONE) set_target_properties(cppnetlib-server-parsers PROPERTIES - IMPORTED_LOCATION_NONE /usr/lib/i386-linux-gnu/libcppnetlib-server-parsers.so.0.11.1 + IMPORTED_LOCATION_NONE /usr/lib/x86_64-linux-gnu/libcppnetlib-server-parsers.so.0.11.1 IMPORTED_SONAME_NONE libcppnetlib-server-parsers.so.0 ) list(APPEND _IMPORT_CHECK_TARGETS cppnetlib-server-parsers ) -list(APPEND _IMPORT_CHECK_FILES_FOR_cppnetlib-server-parsers /usr/lib/i386-linux-gnu/libcppnetlib-server-parsers.so.0.11.1 ) +list(APPEND _IMPORT_CHECK_FILES_FOR_cppnetlib-server-parsers /usr/lib/x86_64-linux-gnu/libcppnetlib-server-parsers.so.0.11.1 ) # Import target cppnetlib-client-connections for configuration None set_property(TARGET cppnetlib-client-connections APPEND PROPERTY IMPORTED_CONFIGURATIONS NONE) set_target_properties(cppnetlib-client-connections PROPERTIES - IMPORTED_LINK_INTERFACE_LIBRARIES_NONE /usr/lib/i386-linux-gnu/libssl.so;/usr/lib/i386-linux-gnu/libcrypto.so - IMPORTED_LOCATION_NONE /usr/lib/i386-linux-gnu/libcppnetlib-client-connections.so.0.11.1 + IMPORTED_LINK_INTERFACE_LIBRARIES_NONE /usr/lib/x86_64-linux-gnu/libssl.so;/usr/lib/x86_64-linux-gnu/libcrypto.so + IMPORTED_LOCATION_NONE /usr/lib/x86_64-linux-gnu/libcppnetlib-client-connections.so.0.11.1 IMPORTED_SONAME_NONE libcppnetlib-client-connections.so.0 ) list(APPEND _IMPORT_CHECK_TARGETS cppnetlib-client-connections ) -list(APPEND _IMPORT_CHECK_FILES_FOR_cppnetlib-client-connections /usr/lib/i386-linux-gnu/libcppnetlib-client-connections.so.0.11.1 ) +list(APPEND _IMPORT_CHECK_FILES_FOR_cppnetlib-client-connections /usr/lib/x86_64-linux-gnu/libcppnetlib-client-connections.so.0.11.1 ) # Commands beyond this point should not need to know the version. set(CMAKE_IMPORT_FILE_VERSION)
Bug#773523: [PATCH] * dirmngr/ldapserver.c (ldapserver_parse_one) return NULL on 'fail'.
--
If something inside the ldapserver_parse_one function failed, 'server' would be
freed, then returned, leading to a use-after-free.
This code is likely copied from sm/gpgsm.c, which was also susceptible to this
bug.
---
dirmngr/ldapserver.c | 1 +
1 file changed, 1 insertion(+)
diff --git a/dirmngr/ldapserver.c b/dirmngr/ldapserver.c
index 0752d95..318d3b0 100644
--- a/dirmngr/ldapserver.c
+++ b/dirmngr/ldapserver.c
@@ -125,6 +125,7 @@ ldapserver_parse_one (char *line,
{
log_info (_(%s:%u: skipping this line\n), filename, lineno);
ldapserver_list_free (server);
+ server = NULL;
}
return server;
--
1.9.1
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#773604: nmu: smartmontools_6.3+svn4002-2+b1
Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: binnmu nmu smartmontools_6.3+svn4002-2+b1 . ALL . -m Rebuild against new binutils 2.24.90.20141219-1 see #728529 In order to resolve #728529, #728113, a binNMU on smartmontools_6.3+svn4002-2 was performed before. However, that binNMU was performed using an old version of binutils (ex:- 2.24.90.20141128-1 on amd64). So the bug in #728113 is still present. More info on the previous binNMU is at #772798. Could you please schedule another binNMU for smartmontools in Sid using the latest version of binutils (in Sid) 2.24.90.20141219-1 ? -- System Information: Debian Release: jessie/sid APT prefers testing APT policy: (500, 'testing'), (500, 'stable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.14-2-amd64 (SMP w/2 CPU cores) -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#771887: nut-client: Does not install cleanly
On Wed, 03 Dec 2014 08:52:39 +0100 Matthias Urlichs matth...@urlichs.de wrote: Package: nut-client Version: 2.7.2-1+b3 Severity: serious Justification: 10.7.3 An unconfigured package is expected to not fail installation. Setting up nut-client (2.7.2-1+b3) ... Job for nut-monitor.service failed. See systemctl status nut-monitor.service and journalctl -xe for details. invoke-rc.d: initscript nut-client, action start failed. dpkg: error processing package nut-client (--configure): subprocess installed post-installation script returned error exit status 1 Errors were encountered while processing: nut-client Press Return to continue. This is probably because you need to configure nut before it is able to start successfully. The systemd services nut ships do not take into account /etc/nut/nut.conf (which by default is set to none, which is supposed to disable all the services). Not exactly sure how to go about adding these types of checks to the systemd service... perhaps it would be easier to just remove the systemd services and leave the init scripts, at least for now. -- Cameron Norman
Bug#773585: php-elisp: Wrong indention of function arguments in subsequent lines
I'll check. Inguza Technology AB Sent from a phone Den 20 dec 2014 14:57 skrev Martin Schulze j...@infodrom.org: Hi Ola! Ola Lundqvist wrote: Hi Please try drupal mode or any other of the variants. How? I think the command is enable-(mode name) In interactive mode M-x shows: Possible completions are: enable-command enable-flow-control enable-theme Regards Joey -- In the beginning was the word, and the word was content-type: text/plain Please always Cc to me when replying to me on the lists.
Bug#773605: unblock: maven/3.0.5-2
Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: unblock Dear Release Team: Please consider unblocking package maven. This upload addreses #770608, an RC FTBFS bug caused by dependent library updates since the previous upload of maven. In addition to maven itself, this upload addresses other pending auto-removals from jessie: saxonhe java-comment-preprocessor jaxb polyglot-maven sisu-maven-plugin gradle resteasy lucene4 elasticsearch eclipse-aether multiverse-core The debdiff against the current version of the package in testing is attached. Thank you, tony (on behalf of the Debian Java team) unblock maven/3.0.5-2 -- System Information: Debian Release: 8.0 APT prefers testing APT policy: (900, 'testing'), (300, 'unstable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.16.0-4-amd64 (SMP w/4 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) diff -Nru maven-3.0.5/debian/changelog maven-3.0.5/debian/changelog --- maven-3.0.5/debian/changelog 2013-10-21 13:50:14.0 -0700 +++ maven-3.0.5/debian/changelog 2014-12-20 08:52:22.0 -0800 @@ -1,3 +1,16 @@ +maven (3.0.5-2) unstable; urgency=medium + + [ Emmanuel Bourg ] + * Team upload. + * Standards-Version updated to 3.9.6 (no changes) + * Update Vcs-Browser and Homepage fields. + + [ tony mancill ] + * Apply patch from Bas Couwenberg to bump plugin versions to +match version in Debian. (Closes: #770608) + + -- tony mancill tmanc...@debian.org Sat, 20 Dec 2014 08:52:09 -0800 + maven (3.0.5-1) unstable; urgency=low * Team upload. diff -Nru maven-3.0.5/debian/control maven-3.0.5/debian/control --- maven-3.0.5/debian/control 2013-10-21 13:50:14.0 -0700 +++ maven-3.0.5/debian/control 2014-12-20 08:52:22.0 -0800 @@ -27,10 +27,10 @@ maven-ant-helper, maven-repo-helper Build-Depends: ant, cdbs, debhelper (= 9), default-jdk -Standards-Version: 3.9.4 -Homepage: http://maven.apache.org/ +Standards-Version: 3.9.6 Vcs-Git: git://anonscm.debian.org/pkg-java/maven.git -Vcs-Browser: http://anonscm.debian.org/gitweb/?p=pkg-java/maven.git +Vcs-Browser: http://anonscm.debian.org/cgit/pkg-java/maven.git +Homepage: http://maven.apache.org Package: maven Architecture: all diff -Nru maven-3.0.5/debian/maven.buildRules maven-3.0.5/debian/maven.buildRules --- maven-3.0.5/debian/maven.buildRules 2013-10-21 13:50:14.0 -0700 +++ maven-3.0.5/debian/maven.buildRules 2014-12-20 08:52:22.0 -0800 @@ -17,8 +17,8 @@ org.apache.maven.plugins maven-clean-plugin * s/.*/2.3/ * * org.apache.maven.plugins maven-resources-plugin * s/.*/2.3/ * * org.apache.maven.plugins maven-surefire-plugin * s/.*/2.10/ * * -org.apache.maven.plugins maven-jar-plugin * s/.*/2.2/ * * -org.apache.maven.plugins maven-compiler-plugin * s/.*/2.0.2/ * * +org.apache.maven.plugins maven-jar-plugin * s/.*/2.4/ * * +org.apache.maven.plugins maven-compiler-plugin * s/.*/2.5.1/ * * org.apache.maven apache-maven pom s/.*/3.0.5/ * * org.apache.maven maven-aether-provider jar s/.*/3.0.5/ * * diff -Nru maven-3.0.5/debian/maven.rules maven-3.0.5/debian/maven.rules --- maven-3.0.5/debian/maven.rules 2013-10-21 13:50:14.0 -0700 +++ maven-3.0.5/debian/maven.rules 2014-12-20 08:52:22.0 -0800 @@ -17,8 +17,8 @@ org.apache.maven.plugins maven-clean-plugin * s/.*/2.3/ * * org.apache.maven.plugins maven-resources-plugin * s/.*/2.3/ * * org.apache.maven.plugins maven-surefire-plugin * s/.*/2.10/ * * -org.apache.maven.plugins maven-jar-plugin * s/.*/2.2/ * * -org.apache.maven.plugins maven-compiler-plugin * s/.*/2.0.2/ * * +org.apache.maven.plugins maven-jar-plugin * s/.*/2.4/ * * +org.apache.maven.plugins maven-compiler-plugin * s/.*/2.5.1/ * * org.apache.maven apache-maven pom s/.*/3.x/ * * org.apache.maven maven-aether-provider jar s/.*/3.x/ * * diff -Nru maven-3.0.5/debian/patches/plugins_version.diff maven-3.0.5/debian/patches/plugins_version.diff --- maven-3.0.5/debian/patches/plugins_version.diff 2013-10-21 13:50:14.0 -0700 +++ maven-3.0.5/debian/patches/plugins_version.diff 2014-12-20 08:52:22.0 -0800 @@ -6,16 +6,16 @@ Forwarded: not-needed --- a/maven-core/src/main/resources/META-INF/plexus/artifact-handlers.xml +++ b/maven-core/src/main/resources/META-INF/plexus/artifact-handlers.xml -@@ -55,7 +55,7 @@ +@@ -55,7 +55,7 @@ problem. !-- START SNIPPET: pom-lifecycle -- phases install -org.apache.maven.plugins:maven-install-plugin:2.3.1:install -+org.apache.maven.plugins:maven-install-plugin:2.3:install ++org.apache.maven.plugins:maven-install-plugin:2.4:install /install deploy
Bug#773606: reportbug: confusing instructions when trying to file a binNMU
Package: reportbug Version: 6.6.1 Severity: normal Dear Maintainer, When trying to request a binNMU using the gtk2 interface, I found the text in one of the menus to be confusing. The issue is not present in the text interface. To reproduce rajulocal@hogwarts:~$ reportbug -u gtk2 release.debian.org Hit Continue - select binnmu line, hit continue - Enter smartmontools for the package name, hit continue - Select This is the correct version At this point, the menu displayed is Is this request for specific architectures? This removal is for all architectures. This is a partial (specific architectures) removal. This is confusing a bit since I was requesting for a binNMU and not a package removal. The issue is not present when using the text interface. Here the interaction looks as follows: rajulocal@hogwarts:~/chess$ reportbug -u text release.debian.org *** Welcome to reportbug. Use ? for help at prompts. *** Note: bug reports are publicly archived (including the email address of the submitter). Detected character set: UTF-8 Please change your locale if this is incorrect. Using 'Kamaraju Kusumanchi kamar...@gmail.com' as your from address. Will send report to Debian (per lsb_release). What sort of request is this? (If none of these things mean anything to you, or you are trying to report a bug in an existing package, please press Enter to exit reportbug.) 1 binnmu binNMU requests 2 britney testing migration script bugs 3 other None of the other options 4 rm Stable/Testing removal requests 5 squeeze-pu squeeze proposed updates requests 6 transition transition tracking 7 unblock unblock requests 8 wheezy-pu wheezy proposed updates requests Choose the request type: 1 Please enter the name of the package: smartmontools Checking status database... Latest version seems to be 6.3+svn4002-2+b1, is this the proper one ? [Y|n|?]? y Is this request for specific architectures? [y|N|?]? N binNMU changelog entry: Here are the uncommented lines of my ~/.reportbugrc rajulocal@hogwarts:~$ stuff.pl ~/.reportbugrc reportbug_version 6.4.4 mode novice ui gtk2 email kamar...@gmail.com no-cc header X-Debbugs-CC: kamar...@gmail.com smtphost reportbug.debian.org -- Package-specific info: ** Environment settings: INTERFACE=gtk2 ** /home/rajulocal/.reportbugrc: reportbug_version 6.4.4 mode novice ui gtk2 email kamar...@gmail.com no-cc header X-Debbugs-CC: kamar...@gmail.com smtphost reportbug.debian.org -- System Information: Debian Release: jessie/sid APT prefers testing APT policy: (500, 'testing'), (500, 'stable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.14-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 Init: sysvinit (via /sbin/init) Versions of packages reportbug depends on: ii apt 0.9.16.1 ii python2.7.5-5 ii python-reportbug 6.6.1 pn python:anynone reportbug recommends no packages. Versions of packages reportbug suggests: pn claws-mail none pn debconf-utils none pn debsumsnone ii dlocate1.02+nmu3 pn emacs23-bin-common | emacs24-bin-commonnone ii exim4 4.84-2 ii exim4-daemon-light [mail-transport-agent] 4.84-2 ii file 1:5.20-2 ii gnupg 1.4.16-1.1 ii python-gtk22.24.0-3+b1 ii python-gtkspell2.25.3-13 pn python-urwid none ii python-vte 1:0.28.2-5 ii xdg-utils 1.1.0~rc1+git20111210-7.1 Versions of packages python-reportbug depends on: ii apt 0.9.16.1 ii python-debian 0.1.21+nmu2 ii python-debianbts 1.12 pn python:anynone python-reportbug suggests no packages. -- no debconf information -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#773607: autofs uses nonportable -s option, mounting fails
Package: autofs Version: 5.0.7-3 Severity: normal Dear Maintainer, * 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 *** After an upgrade a while ago, autofs was no longer able to mount ntfs (ntfs-3g) filesystems. I only tracked this down today, and this is due to autofs using the -s mount option although it's not supported by ntfs. Specifically, this map entry: dosc -fstype=ntfs,iocharset=utf8,codepage=850,shortname=mixed,utf8,dmask=077,fmask=177 :/dev/disk/by-label/WIN7 can be mounted manually: mount -t ntfs -oiocharset=utf8,codepage=850,shortname=mixed,utf8,dmask=077,fmask=177 /dev/disk/by-label/WIN7 /mnt but trying to enter dosc gives bash: cd: .../dosc: No such file or directory. strace'ing autofs reveals the reason: [pid 4237] execve(/sbin/mount.ntfs, [/sbin/mount.ntfs, /dev/sda1, /fs/dosc, -s, -o, rw,iocharset=utf8,codepage=850,shortname=mixed,utf8,dmask=077,fmask=177], [/* 19 vars */]) = 0 the -s option doesn't exist for mount.ntfs - the mount manpage documents that -s isn't supported by all filesystems (and in fact, might be supported only by nfs): # /sbin/mount.ntfs /dev/sda1 /fs/dosc -s -o rw,iocharset=utf8,codepage=850,shortname=mixed,utf8,dmask=077,fmask=177 ntfs-3g: Unknown option '-s'. I looked at the autofs manpage, but it wasn't immediatelly clear why it would add -s by default, or whether this is overridable. It definitely worked in the past, so this must be a relatively recent change. -- System Information: Debian Release: 7.5 APT prefers stable APT policy: (990, 'stable'), (500, 'unstable'), (500, 'testing'), (500, 'oldstable'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.16-3-amd64 (SMP w/12 CPU cores) Locale: LANG=C, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash Versions of packages autofs depends on: ii libc6 2.19-1 ii libxml22.9.1+dfsg1-4 ii multiarch-support 2.13-38+deb7u4 ii ucf3.0025+nmu3 Versions of packages autofs recommends: ii kmod 18-2 ii module-init-tools 9-3 ii nfs-common 1:1.2.6-4 autofs suggests no packages. -- debconf information excluded -- debsums errors found: debsums: changed file /usr/lib/x86_64-linux-gnu/autofs/mount_bind.so (from autofs package) -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#763279: same problem here
On Sat, 20 Dec 2014, Tomas Pospisek wrote: I'm seeing the same problem as Guiseppe here. When playing the german version of the DVD Up (in German Oben), I get the same error as Giuseppe: libdvdnav: Suspected RCE Region Protection!!! [mpeg2video @ 0x7fe67c0a06e0] releasing zombie picture [mpeg2video @ 0x7fe67c0a06e0] releasing zombie picture vlc: src/searching.c:566: dvdnav_get_position: Zusicherung »(signed)*pos != -1« nicht erfüllt. And then vlc dies. I've checked out libvdnav on commit/HEAD= eaf2c44 from the git repo, copied the debian directory into it, and rebuilt the library and can confirm, that it fixes the problem above. Guiseppe, would you like me to send you the resulting debian package? *t [1] http://git.videolan.org/?p=libdvdnav.git;a=log [2] git clone git://git.videolan.org/libdvdnav.git
Bug#773580: lzo2: FTBFS on mips powerpc s390x
Control: tags 773580 + patch pending
On Sat, 20 Dec 2014 at 11:06:56 +, Simon McVittie wrote:
On 20/12/14 10:57, Ivo De Decker wrote:
The latest upload of lzo2 failed on mips, powerpc, s390x (and sparc).
In other words, on big-endian architectures (where byteswapping to fetch
a LE value is not just a memcpy).
Fixed, build-tested (including regression tests) on amd64, armel,
powerpc, s390x and sparc, and tested for the original bug on armel.
I attach the diff since the last maintainer upload, the diff since my
previous NMU, and the updated patch. I'll upload the NMU shortly.
S
diffstat for lzo2-2.08 lzo2-2.08
changelog | 13
+
patches/0001-Conditionally-replace-reinvention-of-memcpy-with-cal.patch | 82
++
2 files changed, 68 insertions(+), 27 deletions(-)
diff -Nru lzo2-2.08/debian/changelog lzo2-2.08/debian/changelog
--- lzo2-2.08/debian/changelog 2014-12-16 23:35:43.0 +
+++ lzo2-2.08/debian/changelog 2014-12-20 17:50:47.0 +
@@ -1,3 +1,16 @@
+lzo2 (2.08-1.2) unstable; urgency=low
+
+ * Non-maintainer upload.
+ * Adjust patch from previous upload so the modern C code path still
+defines some typedefs: lzo_memops_TU1p is a pointer to unsigned byte
+(used by the byteswapping implementation on non-powerpc big-endian
+architectures), and lzo_memops_TU2p and lzo_memops_TU4p
+are pointers to unsigned 2- and 4-byte quantities (needed by the
+powerpc assembler implementation). Together, these fix FTBFS on
+big-endian platforms. (Closes: #773580)
+
+ -- Simon McVittie s...@debian.org Sat, 20 Dec 2014 17:50:38 +
+
lzo2 (2.08-1.1) unstable; urgency=low
* Non-maintainer upload.
diff -Nru
lzo2-2.08/debian/patches/0001-Conditionally-replace-reinvention-of-memcpy-with-cal.patch
lzo2-2.08/debian/patches/0001-Conditionally-replace-reinvention-of-memcpy-with-cal.patch
---
lzo2-2.08/debian/patches/0001-Conditionally-replace-reinvention-of-memcpy-with-cal.patch
2014-12-16 23:35:43.0 +
+++
lzo2-2.08/debian/patches/0001-Conditionally-replace-reinvention-of-memcpy-with-cal.patch
2014-12-20 17:50:47.0 +
@@ -1,5 +1,5 @@
From: Simon McVittie s...@debian.org
-Date: Tue, 16 Dec 2014 23:35:27 +
+Date: Sat, 20 Dec 2014 17:50:27 +
Subject: Conditionally replace reinvention of memcpy() with calls to memcpy()
gcc already knows how to inline memcpy calls with constant n,
@@ -16,16 +16,16 @@
Bug-Debian: https://bugs.debian.org/757037
---
- minilzo/minilzo.c | 64 ---
+ minilzo/minilzo.c | 76 ++-
src/lzo_conf.h| 2 --
- src/lzo_func.h| 55 ++-
- 3 files changed, 97 insertions(+), 24 deletions(-)
+ src/lzo_func.h| 71 +++
+ 3 files changed, 125 insertions(+), 24 deletions(-)
diff --git a/minilzo/minilzo.c b/minilzo/minilzo.c
-index ab2be5f..7e15646 100644
+index ab2be5f..146b383 100644
--- a/minilzo/minilzo.c
+++ b/minilzo/minilzo.c
-@@ -3354,6 +3354,37 @@ lzo_bitops_unused_funcs(void)
+@@ -3354,6 +3354,49 @@ lzo_bitops_unused_funcs(void)
LZO_UNUSED_FUNC(lzo_bitops_unused_funcs);
}
@@ -38,6 +38,18 @@
+ * (C11 draft 1570, paragraph 6.5.7) so they are safe for this use */
+typedef unsigned char *lzo_memops_TU1p;
+
++/* Used by powerpc assembler implementations of byteswapping */
++#if (LZO_OPT_UNALIGNED16)
++typedef lzo_uint16_t __lzo_may_alias lzo_memops_TU2;
++typedef lzo_memops_TU2 *lzo_memops_TU2p;
++#endif
++
++/* Used by powerpc assembler implementations of byteswapping */
++#if (LZO_OPT_UNALIGNED32)
++typedef lzo_uint32_t __lzo_may_alias lzo_memops_TU4;
++typedef lzo_memops_TU4 *lzo_memops_TU4p;
++#endif
++
+#define LZO_MEMOPS_SET1(dd,cc) memset(dd, cc, 1)
+#define LZO_MEMOPS_SET2(dd,cc) memset(dd, cc, 2)
+#define LZO_MEMOPS_SET3(dd,cc) memset(dd, cc, 3)
@@ -63,7 +75,7 @@
#if defined(__lzo_alignof) !(LZO_CFG_NO_UNALIGNED)
#ifndef __lzo_memops_tcheck
#define __lzo_memops_tcheck(t,a,b) ((void)0, sizeof(t) == (a)
__lzo_alignof(t) == (b))
-@@ -3523,6 +3554,8 @@
LZO_COMPILE_TIME_ASSERT_HEADER(sizeof(*(lzo_memops_TU8p)0)==8)
+@@ -3523,6 +3566,8 @@
LZO_COMPILE_TIME_ASSERT_HEADER(sizeof(*(lzo_memops_TU8p)0)==8)
if ((void)0, n__n 0) do { *d__n++ = *s__n++; } while (--n__n 0); \
LZO_BLOCK_END
@@ -72,7 +84,7 @@
__lzo_static_forceinline lzo_uint16_t lzo_memops_get_le16(const lzo_voidp ss)
{
lzo_uint16_t v;
-@@ -3539,7 +3572,7 @@ __lzo_static_forceinline lzo_uint16_t
lzo_memops_get_le16(const lzo_voidp ss)
+@@ -3539,7 +3584,7 @@ __lzo_static_forceinline lzo_uint16_t
lzo_memops_get_le16(const lzo_voidp ss)
#endif
return v;
}
@@ -81,7 +93,7 @@
#define LZO_MEMOPS_GET_LE16(ss)* (const lzo_memops_TU2p) (const
lzo_memops_TU0p) (ss)
#else
#define
Bug#773509: mono-runtime-dbg: missing debug symbols from mono-runtime-dbg
On Vi, 19 dec 14, 10:58:40, Jo Shields wrote: Source: mono-runtime-dbg Version: 3.2.1+dfsg-1 Justification: renders package unusable Severity: grave ... -- System Information: Debian Release: jessie/sid APT prefers trusty-updates APT policy: (500, 'trusty-updates'), (500, 'trusty-security'), (500, 'trusty'), (100, 'trusty-backports') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.13.0-43-generic (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 Besides the wrong (source) package (which is easily fixable) you seem to be reporting this bug against a versions that is not available in Debian. Are you sure this bug also applies to the (most recent) Debian version of the package? You seem to be running Ubuntu. Kind regards, Andrei -- looking after bugs reported against wrong or inexistent packages -- http://wiki.debian.org/FAQsFromDebianUser Offtopic discussions among Debian users and developers: http://lists.alioth.debian.org/mailman/listinfo/d-community-offtopic http://nuvreauspam.ro/gpg-transition.txt signature.asc Description: Digital signature
Bug#773464: /opt/google/chrome/google-chrome: gnome restarts during chrome start attempt (same happens for system settings)
On Jo, 18 dec 14, 18:33:14, Pawel Skrzypek wrote: Package: google-chrome-stable Version: 39.0.2171.95-1 Severity: important File: /opt/google/chrome/google-chrome This is package is not from Debian. Please report any issues with it to where you obtained it from. Kind regards, Andrei -- http://wiki.debian.org/FAQsFromDebianUser Offtopic discussions among Debian users and developers: http://lists.alioth.debian.org/mailman/listinfo/d-community-offtopic http://nuvreauspam.ro/gpg-transition.txt signature.asc Description: Digital signature
Bug#760385: Fix for CVE-2014-5256
Hi Mike, On Sat, 20 Dec 2014 05:06:47 -0500 Michael Gilbert mgilb...@debian.org wrote: On Sat, Dec 20, 2014 at 4:59 AM, Balint Reczey wrote: Hi Mike, On Fri, 19 Dec 2014 21:11:10 -0500 Michael Gilbert wrote: control: severity -1 important There is no security support for libv8 in jessie, so security issues aren't RC. Could you please add some links to explain that? I was about to fix this issue in an NMU after double-checking the fix. Severity doesn't say anything about whether or not a bugs can be fixed, so you can still do that. Anyway it was decided recently on I beg to disagree here. According to freeze policy [1] only targeted fixes for RC bugs are considered to be accepted without pre-approval to testing now. Fixes to unstable which won't be accepted to testing are also discouraged during the freeze. Those implies that decreasing the severity _does_ affect if a bug should be fixed. Please restore the severity of this bug since it is about security flaw and let the Release Team decide if they want to see a vulnerable libv8 in Jessie. BTW the fix seems to be trivial and since I'm in the JavaScript team I can actually fix it in a normal maintainer upload. the security team ml. Please provide a link to a public resource to let others understand the reasoning. Thanks, Balint [1] https://release.debian.org/jessie/freeze_policy.html -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#773608: unblock: heirloom-mailx/12.5-3.1
Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: unblock Hi Release Team! I prepared an upload for heirloom-mailx with the same patches as used by Florian for doing the DSA-3105-1[1], see also #773417[2]. [1] https://www.debian.org/security/2014/dsa-3105 [2] https://bugs.debian.org/773417 The changelog entry reads as: heirloom-mailx (12.5-3.1) unstable; urgency=high * Non-maintainer upload. * Apply patches from Red Hat (Florian Weimer) to address command execution issues (Closes: #773417): + 0011-outof-Introduce-expandaddr-flag.patch Disable command execution in email addresses (CVE-2014-7844) + 0012-unpack-Disable-option-processing-for-email-addresses.patch + 0013-fio.c-Unconditionally-require-wordexp-support.patch + 0014-globname-Invoke-wordexp-with-WRDE_NOCMD.patch (CVE-2004-2771) -- Salvatore Bonaccorso car...@debian.org Sat, 20 Dec 2014 06:55:53 +0100 I attached also the complete debdiff to this request. Could you consider an unblock of heirloom-mailx to testing, so that we have the same fixes also in jessie? unblock heirloom-mailx/12.5-3.1 Regards, Salvatore diff -Nru heirloom-mailx-12.5/debian/changelog heirloom-mailx-12.5/debian/changelog --- heirloom-mailx-12.5/debian/changelog 2014-09-12 20:31:33.0 +0200 +++ heirloom-mailx-12.5/debian/changelog 2014-12-20 07:16:54.0 +0100 @@ -1,3 +1,16 @@ +heirloom-mailx (12.5-3.1) unstable; urgency=high + + * Non-maintainer upload. + * Apply patches from Red Hat (Florian Weimer) to address command +execution issues (Closes: #773417): ++ 0011-outof-Introduce-expandaddr-flag.patch + Disable command execution in email addresses (CVE-2014-7844) ++ 0012-unpack-Disable-option-processing-for-email-addresses.patch ++ 0013-fio.c-Unconditionally-require-wordexp-support.patch ++ 0014-globname-Invoke-wordexp-with-WRDE_NOCMD.patch (CVE-2004-2771) + + -- Salvatore Bonaccorso car...@debian.org Sat, 20 Dec 2014 06:55:53 +0100 + heirloom-mailx (12.5-3) unstable; urgency=low * Modernized the package diff -Nru heirloom-mailx-12.5/debian/patches/0011-outof-Introduce-expandaddr-flag.patch heirloom-mailx-12.5/debian/patches/0011-outof-Introduce-expandaddr-flag.patch --- heirloom-mailx-12.5/debian/patches/0011-outof-Introduce-expandaddr-flag.patch 1970-01-01 01:00:00.0 +0100 +++ heirloom-mailx-12.5/debian/patches/0011-outof-Introduce-expandaddr-flag.patch 2014-12-20 07:16:54.0 +0100 @@ -0,0 +1,65 @@ +From 9984ae5cb0ea0d61df1612b06952a61323c083d9 Mon Sep 17 00:00:00 2001 +From: Florian Weimer fwei...@redhat.com +Date: Mon, 17 Nov 2014 11:13:38 +0100 +Subject: [PATCH 1/4] outof: Introduce expandaddr flag + +Document that address expansion is disabled unless the expandaddr +binary option is set. + +This has been assigned CVE-2014-7844 for BSD mailx, but it is not +a vulnerability in Heirloom mailx because this feature was documented. +--- + mailx.1 | 14 ++ + names.c | 3 +++ + 2 files changed, 17 insertions(+) + +diff --git a/mailx.1 b/mailx.1 +index 70a7859..22a171b 100644 +--- a/mailx.1 b/mailx.1 +@@ -656,6 +656,14 @@ but any reply returned to the machine + will have the system wide alias expanded + as all mail goes through sendmail. + .SS Recipient address specifications ++If the ++.I expandaddr ++option is not set (the default), recipient addresses must be names of ++local mailboxes or Internet mail addresses. ++.PP ++If the ++.I expandaddr ++option is set, the following rules apply: + When an address is used to name a recipient + (in any of To, Cc, or Bcc), + names of local mail folders +@@ -2391,6 +2399,12 @@ and exits immediately. + If this option is set, + \fImailx\fR starts even with an empty mailbox. + .TP ++.B expandaddr ++Causes ++.I mailx ++to expand message recipient addresses, as explained in the section, ++Recipient address specifications. ++.TP + .B flipr + Exchanges the + .I Respond +diff --git a/names.c b/names.c +index 66e976b..c69560f 100644 +--- a/names.c b/names.c +@@ -268,6 +268,9 @@ outof(struct name *names, FILE *fo, struct header *hp) + FILE *fout, *fin; + int ispipe; + ++ if (value(expandaddr) == NULL) ++ return names; ++ + top = names; + np = names; + time(now); +-- +1.9.3 + + diff -Nru heirloom-mailx-12.5/debian/patches/0012-unpack-Disable-option-processing-for-email-addresses.patch heirloom-mailx-12.5/debian/patches/0012-unpack-Disable-option-processing-for-email-addresses.patch --- heirloom-mailx-12.5/debian/patches/0012-unpack-Disable-option-processing-for-email-addresses.patch 1970-01-01 01:00:00.0 +0100 +++ heirloom-mailx-12.5/debian/patches/0012-unpack-Disable-option-processing-for-email-addresses.patch 2014-12-20 07:16:54.0 +0100 @@ -0,0 +1,75 @@ +From e34e2ac67b80497080ebecccec40c3b61456167d Mon Sep 17 00:00:00 2001 +From: Florian Weimer fwei...@redhat.com +Date: Mon, 17 Nov 2014 11:14:06 +0100 +Subject: [PATCH 2/4] unpack: Disable option
Bug#773609: virtualbox: freezes and reads disk forever with fresh install of a debian jessie VM
Package: virtualbox Version: 4.3.20-dfsg-1 Severity: important Dear Maintainer, This is an issue on both 4.3.18 (current testing vb version) and 4.3.20 to which I upgraded. There is a problem with installing debian on a new VM. I downloaded jessie's small installer (debian-jessie-DI-b2-i386-netinst.iso) and installed debian. The install completed (I did a minimum install: just standard utilities and openssh-server selected at tasksel). The VM rebooted after completing the install and then without any command the VM froze and the disk reads without stopping. I let it over 20 minutes and it was still reading. During that time the VM console was frozen as well as the Virtualbox manager. I killed both and then tried to start the VM again: Both are frozen, showing the dialog box saying: starting virtual machine, and the disk reads without stop. I tried the whole procedure over 3 times: Everytime the same. I even tried to snapshot the machine during the new install. I took during the install several snapshots without problem, but after the dialog of setting up partitions etc I pressed the snap button and the VM as well as the VB manager froze, and the disk started reading without stopping. I don't think its a disk fault (I/O errors etc) because kernel would show something and in addition I tried reading the VM file (vdi) and it is read without problem. All I see in the kernel is: [22743.183679] nspr-3: sending ioctl 5393 to a partition! [22743.183711] nspr-3: sending ioctl 5393 to a partition! [23138.751661] nspr-2: sending ioctl 5393 to a partition! [23138.751695] nspr-2: sending ioctl 5393 to a partition! [23138.884456] nspr-2: sending ioctl 5393 to a partition! [23138.884502] nspr-2: sending ioctl 5393 to a partition! [23144.899777] nspr-2: sending ioctl 5393 to a partition! [23144.899818] nspr-2: sending ioctl 5393 to a partition! I attach the VBox.log. I hope I was clear. Thanks! Giorgos -- System Information: Debian Release: 8.0 APT prefers testing-updates APT policy: (500, 'testing-updates'), (500, 'testing'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.16.0-4-amd64 (SMP w/2 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages virtualbox depends on: ii adduser 3.113+nmu3 ii dpkg 1.17.21 ii libc62.19-13 ii libcurl3-gnutls 7.38.0-3 ii libgcc1 1:4.9.1-19 ii libgsoap52.8.17-1 ii libpng12-0 1.2.50-2+b2 ii libpython2.7 2.7.8-11 ii libsdl1.2debian 1.2.15-10+b1 ii libssl1.0.0 1.0.1j-1 ii libstdc++6 4.9.1-19 ii libvncserver00.9.9+dfsg-6.1 ii libvpx1 1.3.0-3 ii libx11-6 2:1.6.2-3 ii libxcursor1 1:1.1.14-1+b1 ii libxext6 2:1.3.3-1 ii libxml2 2.9.1+dfsg1-4 ii libxmu6 2:1.1.2-1 ii libxt6 1:1.1.4-1+b1 ii python 2.7.8-2 ii python2.72.7.8-11 ii zlib1g 1:1.2.8.dfsg-2+b1 Versions of packages virtualbox recommends: ii libgl1-mesa-glx [libgl1] 10.3.2-1 ii libqt4-opengl 4:4.8.6+git64-g5dc8b2b+dfsg-2+b1 ii libqtcore44:4.8.6+git64-g5dc8b2b+dfsg-2+b1 ii libqtgui4 4:4.8.6+git64-g5dc8b2b+dfsg-2+b1 ii virtualbox-dkms 4.3.20-dfsg-1 ii virtualbox-qt 4.3.20-dfsg-1 Versions of packages virtualbox suggests: pn vde2none ii virtualbox-guest-additions-iso 4.3.18-1 -- no debconf information VBox.log.bz2 Description: BZip2 compressed data
Bug#773092: grub-efi-amd64: grub efi installation failure
On 12/20/2014 08:34 AM, Steve McIntyre wrote: Control: tag -1 +patch Here's a tested patch. Linux lookups on VFAT are not as intelligent as you'd hope in terms of matching filenames despite case changes. Instead, I've added more code to do directory lookups and do case-insensitive matching by hand. This will now work regardless of the silliness of any existing filenames, and will default to all-caps on creation if they don't already exist. The patch fixes the reported problem. Thanks Steve. -- Ritesh Raj Sarraf | http://people.debian.org/~rrs Debian - The Universal Operating System signature.asc Description: OpenPGP digital signature
Bug#773609: virtualbox: freezes and reads disk forever with fresh install of a debian jessie VM
On 12/21/2014 12:23 AM, Giorgos Pallas wrote: This is an issue on both 4.3.18 (current testing vb version) and 4.3.20 to which I upgraded. There is a problem with installing debian on a new VM. I downloaded jessie's small installer (debian-jessie-DI-b2-i386-netinst.iso) and installed debian. The install completed (I did a minimum install: just standard utilities and openssh-server selected at tasksel). The VM rebooted after completing the install and then without any command the VM froze and the disk reads without stopping. I let it over 20 minutes and it was still reading. During that time the VM console was frozen as well as the Virtualbox manager. I killed both and then tried to start the VM again: Both are frozen, showing the dialog box saying: starting virtual machine, and the disk reads without stop. I tried the whole procedure over 3 times: Everytime the same. I even tried to snapshot the machine during the new install. I took during the install several snapshots without problem, but after the dialog of setting up partitions etc I pressed the snap button and the VM as well as the VB manager froze, and the disk started reading without stopping. I don't think its a disk fault (I/O errors etc) because kernel would show something and in addition I tried reading the VM file (vdi) and it is read without problem. How much memory have you allocated to the Guest VM ? -- Ritesh Raj Sarraf | http://people.debian.org/~rrs Debian - The Universal Operating System signature.asc Description: OpenPGP digital signature
Bug#773610: libapache2-svn: apache2 restart failed: mod_dav_svn.so: undefined symbol:, dav_svn__new_error
Package: libapache2-svn Version: 1.6.17dfsg-4+deb7u7 Severity: grave Justification: renders package unusable The wheezy-security upload breaks libapache2-svn in exactly the same way as the previous upload 1.6.17dfsg-4+deb7u5, which was fixed in 1.6.17dfsg-4+deb7u6, see bug number 741314 for more details. service apache2 start [ ok ] Starting web server: apache2. apache2: Syntax error on line 244 of /etc/apache2/apache2.conf: Syntax error on line 2 of /etc/apache2/mods-enabled/dav_svn.load: Cannot load /usr/lib/apache2/modules/mod_dav_svn.so into server: /usr/lib/apache2/modules/mod_dav_svn.so: undefined symbol: dav_svn__new_error Arne Nordmark -- 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/4 CPU cores) Locale: LANG=sv_SE.UTF-8, LC_CTYPE=sv_SE.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#773561: Installing xen-linux-system-amd64 on jessie fails
Hello Ian, systemctl status xen.service gives: root@jessie:/home/sydney# systemctl status xen.service ● xen.service - LSB: Xen daemons Loaded: loaded (/etc/init.d/xen) Active: failed (Result: exit-code) since Sat 2014-12-20 20:42:30 CET; 11s ago Process: 4796 ExecStart=/etc/init.d/xen start (code=exited, status=255) Dec 20 20:42:30 jessie xen[4796]: Starting Xen daemons: xenfs (warning). Dec 20 20:42:30 jessie systemd[1]: xen.service: control process exited, code=exited status=255 Dec 20 20:42:30 jessie systemd[1]: Failed to start LSB: Xen daemons. Dec 20 20:42:30 jessie systemd[1]: Unit xen.service entered failed state. journalctl -xn gives: root@jessie:/home/sydney# journalctl -xn -- Logs begin at Sat 2014-12-20 20:40:10 CET, end at Sat 2014-12-20 20:42:30 CET. -- Dec 20 20:42:27 jessie kernel: hfsplus: unable to find HFS+ superblock Dec 20 20:42:27 jessie kernel: qnx4: no qnx4 filesystem (no root dir). Dec 20 20:42:27 jessie kernel: You didn't specify the type of your ufs filesystem mount -t ufs -o ufstype=sun|sunx86|44bsd|ufs2|5xbsd|old|hp|nextstep|nextstep-cd|openstep ... WARNING Wrong ufstype may corrupt your filesystem, default is ufstype=old Dec 20 20:42:27 jessie kernel: hfs: can't find a HFS filesystem on dev xvda2 Dec 20 20:42:27 jessie os-prober[4747]: debug: /dev/xvda5: is active swap Dec 20 20:42:30 jessie kernel: xen:xen_evtchn: Event-channel device installed Dec 20 20:42:30 jessie xen[4796]: Starting Xen daemons: xenfs (warning). Dec 20 20:42:30 jessie systemd[1]: xen.service: control process exited, code=exited status=255 Dec 20 20:42:30 jessie systemd[1]: Failed to start LSB: Xen daemons. -- Subject: Unit xen.service has failed -- Defined-By: systemd -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel -- -- Unit xen.service has failed. -- -- The result is failed. Dec 20 20:42:30 jessie systemd[1]: Unit xen.service entered failed state. On 20 Dec 2014, at 11:29, Ian Campbell i...@debian.org wrote: On Sat, 2014-12-20 at 00:57 +0100, Sydney Meyer wrote: Job for xen.service failed. See 'systemctl status xen.service' and 'journalctl -xn' for details. Please can you provide the output of these two commands while in this state. Ian. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#773610: libapache2-svn: apache2 restart failed: mod_dav_svn.so: undefined symbol:, dav_svn__new_error
* Arne Nordmark: The wheezy-security upload breaks libapache2-svn in exactly the same way as the previous upload 1.6.17dfsg-4+deb7u5, which was fixed in 1.6.17dfsg-4+deb7u6, see bug number 741314 for more details. Ugh, I'm building this now myself and will upload another version if it passes basic testing. (The build seems to disable all warnings, unfortuantely.) -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#683110: gphoto: Patch available for USB 3.0 problems
hi, this bug should have been reported against libgphoto2. anyway, i checked and i believe the upstream fixed it. and this report(683110) is tagged 'fixed-upstream. i don't know the exact version but i will tag it as done. regards, -- Herbert Parentes Fortes Neto (hpfn) -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#760385: lowering severity of bugs not tracked by release team
On Sat, Dec 20, 2014 at 6:15 AM, Adam D. Barratt wrote: On Sat, 2014-12-20 at 11:48 +0100, Jonas Smedegaard wrote: [sent again, cc correct list address this time] Quoting Michael Gilbert (2014-12-20 11:06:47) On Sat, Dec 20, 2014 at 4:59 AM, Balint Reczey wrote: On Fri, 19 Dec 2014 21:11:10 -0500 Michael Gilbert wrote: control: severity -1 important There is no security support for libv8 in jessie, so security issues aren't RC. Could you please add some links to explain that? I was about to fix this issue in an NMU after double-checking the fix. Severity doesn't say anything about whether or not a bugs can be fixed, so you can still do that. Anyway it was decided recently on the security team ml. I'm not aware of it having been decided that the security team were the arbiters of release criticality in such situations. The severity was bumped to grave by Moritz about a month ago, likely to get the libv8 maintainers to actually pay attention to their vast volume of unaddressed security issues. Now that it's been decided that libv8 won't get security support in jessie, it seems perfectly reasonable to move back to the original severity, which is important. I find it sensible for the security team to give up on maintaining some packages - and I find it great to try communicate that to our users by use of the debian-security-support package. Just now I learned from above bugreport that the security team also actively *lower* bugreports to avoid them being treated as release candidate, for packages not maintained by the security team. That I find a horrible approach: Severity of a bug is independent on whether it will be fixed or not. The more proper tag to use is *-ignore, IMO. The release team will still consider important bug fixes, you just need to ask for a pre-unblock. Best wishes, Mike -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#773611: Fwd: RFS: histring/1.1.1-1 [ITP] - general purpose highlighting tool
Package: sponsorship-requests Severity: wishlist Dear mentors, Please sponsor for my newly uploaded package histring. It's a general purpose highlighting tool that works with arbitrary input text file (e.g. all sorts of log files), and highlight different keywords in different colours (e.g., warnings and errors are highlighted with different colours). You can use this single small tool to replace all kinds of special purpose log parsing tools, and it can do much more, like highlighting results from vcsdiff, etc. E.g., http://sfxpt.wordpress.com/2013/06/02/highlighting-strings-in-text-output-with-histring/ Once again, I am looking for a sponsor for my newly upgraded package histring. It's *lintian clean*, and without any build problems. Ref http://mentors.debian.net/package/histring * Package name: histring Version : 1.1.1-1 * URL : https://github.com/suntong001/histring * License : GPL-2.0+ Section : utils It builds those binary packages: histring - highlight strings using ANSI terminal escape sequences To access further information about this package, please visit the following URL: http://mentors.debian.net/package/histring Alternatively, one can download the package with dget using this command: dget -x http://mentors.debian.net/debian/pool/main/h/histring/histring_1.1.1-1.dsc More information about hello can be obtained from http://sfxpt.wordpress.com/2014/11/30/use-new-dbab-to-set-proxy-automatically/#advantages. Thanks Best Regards, Tong Sun -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#773612: network-manager: No valid IPv4 config information received (pptp), after connection established
Package: network-manager Version: 0.9.10.0-4 Severity: important Tags: upstream Dear Maintainer, Cannot establish VPN with pptp - any of the setting lead to the same result (default/split route, only resources..., automatic DNS). However, these settings do work on Ubuntu 12.04. After pptp connection is established, NM refuses to add IPv4 settings, noting: unspecific failure Log snippets: Dec 20 20:51:29 pico NetworkManager[659]: ** Message: nm-pptp-ppp-plugin: (nm_phasechange): status 6 / phase 'authenticate' Dec 20 20:51:29 pico NetworkManager[659]: ** Message: nm-pptp-ppp-plugin: (get_credentials): passwd-hook, requesting credentials... Dec 20 20:51:29 pico NetworkManager[659]: ** Message: nm-pptp-ppp-plugin: (get_credentials): got credentials from NetworkManager-pptp Dec 20 20:51:31 pico pppd[2661]: CHAP authentication succeeded Dec 20 20:51:31 pico NetworkManager[659]: CHAP authentication succeeded Dec 20 20:51:31 pico NetworkManager[659]: ** Message: nm-pptp-ppp-plugin: (nm_phasechange): status 8 / phase 'network' Dec 20 20:51:31 pico pppd[2661]: MPPE 128-bit stateless compression enabled Dec 20 20:51:31 pico NetworkManager[659]: MPPE 128-bit stateless compression enabled Dec 20 20:51:32 pico pppd[2661]: local IP address 192.168.221.2 Dec 20 20:51:32 pico pppd[2661]: remote IP address 192.168.221.1 Dec 20 20:51:32 pico pppd[2661]: primary DNS address 192.168.204.14 Dec 20 20:51:32 pico pppd[2661]: secondary DNS address 192.168.204.237 Dec 20 20:51:32 pico NetworkManager[659]: local IP address 192.168.221.2 Dec 20 20:51:32 pico NetworkManager[659]: remote IP address 192.168.221.1 Dec 20 20:51:32 pico NetworkManager[659]: primary DNS address 192.168.204.14 Dec 20 20:51:32 pico NetworkManager[659]: secondary DNS address 192.168.204.237 Dec 20 20:51:32 pico NetworkManager[659]: ** Message: nm-pptp-ppp-plugin: (nm_phasechange): status 9 / phase 'running' Dec 20 20:51:32 pico NetworkManager[659]: ** Message: nm-pptp-ppp-plugin: (nm_ip_up): ip-up event Dec 20 20:51:32 pico NetworkManager[659]: ** Message: nm-pptp-ppp-plugin: (nm_ip_up): sending Ip4Config to NetworkManager-pptp... Dec 20 20:51:32 pico NetworkManager[659]: info VPN connection 'Berlin' (IP4 Config Get) reply received from old-style plugin. Dec 20 20:51:32 pico NetworkManager[659]: info VPN Gateway: 212.144.118.2 Dec 20 20:51:32 pico NetworkManager[659]: info Tunnel Device: ppp0 Dec 20 20:51:32 pico NetworkManager[659]: info IPv4 configuration: Dec 20 20:51:32 pico NetworkManager[659]: info Internal Address: 192.168.221.2 Dec 20 20:51:32 pico NetworkManager[659]: info Internal Prefix: 32 Dec 20 20:51:32 pico NetworkManager[659]: info Internal Point-to-Point Address: 192.168.221.1 Dec 20 20:51:32 pico NetworkManager[659]: info Maximum Segment Size (MSS): 0 Dec 20 20:51:32 pico NetworkManager[659]: info Static Route: 192.168.192.0/20 Next Hop: 192.168.204.113 Dec 20 20:51:32 pico NetworkManager[659]: info Forbid Default Route: yes Dec 20 20:51:32 pico NetworkManager[659]: info Internal DNS: 192.168.204.12 Dec 20 20:51:32 pico NetworkManager[659]: info Internal DNS: 192.168.204.237 Dec 20 20:51:32 pico NetworkManager[659]: info DNS Domain: '(none)' Dec 20 20:51:32 pico NetworkManager[659]: info No IPv6 configuration Dec 20 20:51:32 pico NetworkManager[659]: error [1419105092.058788] [platform /nm-linux-platform.c:1714] add_object(): Netlink error adding 192.168.192.0/20 via 192.168.204.113 dev ppp0 metric 1024 mss 0 src user: Unspecific failure Dec 20 20:51:32 pico NetworkManager[659]: warn VPN connection 'Berlin' did not receive valid IP config information. Dec 20 20:51:32 pico pppd[2661]: Terminating on signal 15 -- System Information: Debian Release: 8.0 APT prefers testing APT policy: (900, 'testing'), (500, 'testing-updates'), (500, 'testing-proposed-updates') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.16.0-4-amd64 (SMP w/2 CPU cores) Locale: LANG=en_US.utf8, LC_CTYPE=en_US.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages network-manager depends on: ii adduser3.113+nmu3 ii dbus 1.8.12-1 ii init-system-helpers1.22 ii isc-dhcp-client4.3.1-5 ii libc6 2.19-13 ii libdbus-1-31.8.12-1 ii libdbus-glib-1-2 0.102-1 ii libgcrypt201.6.2-4+b1 ii libglib2.0-0 2.42.1-1 ii libgnutls-deb0-28 3.3.8-5 ii libgudev-1.0-0 215-7 ii libmm-glib01.4.0-1 ii libndp01.4-2 ii libnewt0.520.52.17-1+b1 ii libnl-3-2003.2.24-2 ii libnl-genl-3-200 3.2.24-2 ii libnl-route-3-200 3.2.24-2 ii libnm-glib40.9.10.0-4 ii libnm-util20.9.10.0-4 ii libpam-systemd 215-7 ii libpolkit-gobject-1-0 0.105-8 ii libreadline6 6.3-8+b2 ii libsoup2.4-1 2.48.0-1 ii libsystemd0215-7 ii libteamdctl0
Bug#773613: users-admin: group name limited to 16 characters
Package: gnome-system-tools Version: 3.0.0-4 Severity: normal Dear Maintainer, I am reporting the issue described in Launchpad #1371854 upstream as I can reproduce it on Debian with gnome-system-tools-3.0.0-4. In users-admin (a.k.a. Users Settings), under Manage Groups/Group Settings, while the listed groups available may have more than 16 characters, when viewing a group's properties the Group name field in Basic Settings only shows the first 16 characters (e.g. chrome-remote-desktop is truncated as chrome-remote-de). Additionally, this prevents creating a group with a name longer than 16 characters using users-admin. (I understand that the system limit may have been 16 characters historically; man groupadd reports it is currently 32 characters.) -- System Information: Debian Release: 8.0 APT prefers testing-updates APT policy: (500, 'testing-updates'), (500, 'testing') Architecture: powerpc (ppc) Kernel: Linux 3.16.0-4-powerpc Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages gnome-system-tools depends on: ii dconf-gsettings-backend [gsettings-backend] 0.22.0-1 ii libatk1.0-0 2.14.0-1 ii libc62.19-13 ii libcairo-gobject21.14.0-2.1 ii libcairo21.14.0-2.1 ii libdbus-1-3 1.8.12-1 ii libgdk-pixbuf2.0-0 2.31.1-2+b1 ii libglib2.0-0 2.42.1-1 ii libgtk-3-0 3.14.5-1 ii liboobs-1-5 3.0.0-2 ii libpango-1.0-0 1.36.8-3 ii libpangocairo-1.0-0 1.36.8-3 ii libpolkit-gobject-1-00.105-8 ii lxsession [policykit-1-gnome]0.5.1-2 ii policykit-1-gnome0.105-2 gnome-system-tools recommends no packages. Versions of packages gnome-system-tools suggests: pn gnome-control-center none ii ntp 1:4.2.6.p5+dfsg-3.1+b1 -- no debconf information -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#773585: php-elisp: Wrong indention of function arguments in subsequent lines
Hi Now I have checked. I missed the php- prefix. The interactive mode M-x commands are: php-enable-...-coding-style In at least drupal coding style it works as you expect. I do not know why it does not work that way with the other ones. // Ola On Sat, Dec 20, 2014 at 2:53 PM, Martin Schulze j...@infodrom.org wrote: Hi Ola! Ola Lundqvist wrote: Hi Please try drupal mode or any other of the variants. How? I think the command is enable-(mode name) In interactive mode M-x shows: Possible completions are: enable-command enable-flow-control enable-theme Regards Joey -- In the beginning was the word, and the word was content-type: text/plain Please always Cc to me when replying to me on the lists. -- --- Inguza Technology AB --- MSc in Information Technology / o...@inguza.comAnnebergsslingan 37\ | o...@debian.org 654 65 KARLSTAD| | http://inguza.com/Mobile: +46 (0)70-332 1551 | \ gpg/f.p.: 7090 A92B 18FE 7994 0C36 4FE4 18A1 B1CF 0FE5 3DD9 / ---
Bug#772113: glances segfault
Hello, Upstream version 2.2 is available with fixed issues. I will package this new version soon. 2014-12-05 10:01 GMT+01:00 Raphael raph...@encr.es: Package: glances Version: 2.1.1-1 Severity: important Hi, After a period of time glances tends to segfault with File /usr/lib/python3/dist-packages/glances/core/glances_stats.py, line 130, in update self.__update__(input_stats) File /usr/lib/python3/dist-packages/glances/core/glances_stats.py, line 121, in __update__ self._plugins[p].update() File /usr/lib/python3/dist-packages/glances/plugins/glances_processcount.py, line 55, in update glances_processes.update() File /usr/lib/python3/dist-packages/glances/core/glances_processes.py, line 339, in update self.processcount[str(proc.status())] += 1 File /usr/lib/python3/dist-packages/psutil/__init__.py, line 555, in status return self._proc.status() File /usr/lib/python3/dist-packages/psutil/_pslinux.py, line 704, in wrapper raise NoSuchProcess(self.pid, self._name) psutil.NoSuchProcess: process no longer exists (pid=1135, name='byobu-status') Seems it's a know problem, corrected upstream : https://github.com/nicolargo/glances/issues/421 https://github.com/nicolargo/glances/issues/414 Thanks Raphael -- 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-3-amd64 (SMP w/8 CPU cores) Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash Versions of packages glances depends on: ii adduser3.113+nmu3 ii lsb-base 4.1+Debian13+nmu1 ii python33.4.2-1 ii python3-pkg-resources 5.5.1-1 ii python3-psutil 2.1.1-1+b1 pn python3:anynone Versions of packages glances recommends: ii hddtemp 0.3-beta15-52 ii lm-sensors 1:3.3.5-2 ii python3-bottle 0.12.7-1 pn python3-jinja2 none ii python3-pysnmp4 4.2.5-1 glances suggests no packages. -- no debconf information -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#773614: users-admin: Change User Password can hang when password is too simple
Package: gnome-system-tools Version: 3.0.0-4 Severity: normal Dear Maintainer, I am reporting the issue described at Launchpad #1299138 (originally reported by user intherye) upstream as I can reproduce it on Debian with gnome-system-tools-3.0.0-4. When attempting to change the password in users-admin (a.k.a. User Settings) to a password that is too simple (e.g. a12345), the Change User Password dialog will report Password too simple on the first try, but will hang on the second try. The dialog can be closed, and one can return to User Settings without the password having changed. However, when users-admin is run from OS X over ssh -Y, it DOES NOT hang (always reports Password too simple; using OS X 10.10.1, OpenSSH_6.7p1, OpenSSL 1.0.1j 15 Oct 2014 for macports, and XQuartz 2.7.8_beta1). -- System Information: Debian Release: 8.0 APT prefers testing-updates APT policy: (500, 'testing-updates'), (500, 'testing') Architecture: powerpc (ppc) Kernel: Linux 3.16.0-4-powerpc Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages gnome-system-tools depends on: ii dconf-gsettings-backend [gsettings-backend] 0.22.0-1 ii libatk1.0-0 2.14.0-1 ii libc62.19-13 ii libcairo-gobject21.14.0-2.1 ii libcairo21.14.0-2.1 ii libdbus-1-3 1.8.12-1 ii libgdk-pixbuf2.0-0 2.31.1-2+b1 ii libglib2.0-0 2.42.1-1 ii libgtk-3-0 3.14.5-1 ii liboobs-1-5 3.0.0-2 ii libpango-1.0-0 1.36.8-3 ii libpangocairo-1.0-0 1.36.8-3 ii libpolkit-gobject-1-00.105-8 ii lxsession [policykit-1-gnome]0.5.1-2 ii policykit-1-gnome0.105-2 gnome-system-tools recommends no packages. Versions of packages gnome-system-tools suggests: pn gnome-control-center none ii ntp 1:4.2.6.p5+dfsg-3.1+b1 -- no debconf information -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#773615: [pynagram] Does not start if a greek wordlist file is added.
Package: pynagram Version: 1.0.1-1 Severity: normal Tags: l10n --- Please enter the report below this line. --- After adding a greek wordlist, pynagram does not start. To recreate do the following: Create a greek word-list with the following line $ aspell -d el dump master | aspell -l el expand words-el400k.txt then add the world-list to pynagram using menu Game-Wordlists and save. Quit the game and then try to start it again... The game does not start. Workaround: Delete ~/.pynagram/config.txt Start pynagram (default config.txt file is created) --- System information. --- Architecture: amd64 Kernel: Linux 3.16.0-4-amd64 Debian Release: 8.0 500 testing security.debian.org 500 testing ftp.gr.debian.org 500 stable downloads.sourceforge.net 500 stable dl.google.com --- Package information. --- Package's Depends field is empty. Package's Recommends field is empty. Package's Suggests field is empty.
Bug#763279: same problem here
On Sat, 20 Dec 2014, Tomas Pospisek wrote: On Sat, 20 Dec 2014, Tomas Pospisek wrote: I'm seeing the same problem as Guiseppe here. When playing the german version of the DVD Up (in German Oben), I get the same error as Giuseppe: libdvdnav: Suspected RCE Region Protection!!! [mpeg2video @ 0x7fe67c0a06e0] releasing zombie picture [mpeg2video @ 0x7fe67c0a06e0] releasing zombie picture vlc: src/searching.c:566: dvdnav_get_position: Zusicherung »(signed)*pos != -1« nicht erfüllt. And then vlc dies. I've checked out libvdnav on commit/HEAD= eaf2c44 from the git repo, copied the debian directory into it, and rebuilt the library and can confirm, that it fixes the problem above. That said, even with the git version, when playing the DVD in vlc, vlc is loosing track of the point in time inside the video and loosing sound time and again. So it's quite cumbersome to watch DVDs in vlc. Alas, I have not found any other software yet, where watchin DVDs is possible in Debian. Current mplayer from jessie is only showing a black window and mpv doesn't seem to be able to find the beginning of the movie... Haven't checked with other players yet. *t
