Bug#696913: llvm-3.2-dev: consider saving disk space by not shipping two identical copies of libLLVM-3.2.so.1
Package: llvm-3.2-dev Version: 3.2-2 Severity: wishlist I noticed that my system has two copies of the same 21 MB shared library: $ stat /usr/lib/x86_64-linux-gnu/libLLVM-3.2.so.1 /usr/lib/llvm-3.2/lib/libLLVM-3.2.so.1 File: ‘/usr/lib/x86_64-linux-gnu/libLLVM-3.2.so.1’ Size: 21325112Blocks: 41712 IO Block: 4096 regular file Device: ca30h/51760dInode: 786465 Links: 1 Access: (0644/-rw-r--r--) Uid: (0/root) Gid: (0/root) Access: 2012-12-29 10:08:51.0 +0200 Modify: 2012-12-24 08:56:06.0 +0200 Change: 2012-12-29 10:08:57.0 +0200 Birth: - File: ‘/usr/lib/llvm-3.2/lib/libLLVM-3.2.so.1’ Size: 21325112Blocks: 41712 IO Block: 4096 regular file Device: ca30h/51760dInode: 197452 Links: 1 Access: (0644/-rw-r--r--) Uid: (0/root) Gid: (0/root) Access: 2012-12-29 10:08:51.0 +0200 Modify: 2012-12-24 08:56:32.0 +0200 Change: 2012-12-29 10:09:01.0 +0200 Birth: - $ md5sum /usr/lib/x86_64-linux-gnu/libLLVM-3.2.so.1 /usr/lib/llvm-3.2/lib/libLLVM-3.2.so.1 1ffd5aff8dc0f39cc17b604ea25aa796 /usr/lib/x86_64-linux-gnu/libLLVM-3.2.so.1 1ffd5aff8dc0f39cc17b604ea25aa796 /usr/lib/llvm-3.2/lib/libLLVM-3.2.so.1 $ dpkg -S /usr/lib/x86_64-linux-gnu/libLLVM-3.2.so.1 /usr/lib/llvm-3.2/lib/libLLVM-3.2.so.1 libllvm3.2:amd64: /usr/lib/x86_64-linux-gnu/libLLVM-3.2.so.1 llvm-3.2-dev: /usr/lib/llvm-3.2/lib/libLLVM-3.2.so.1 Is this a bug? Would it be possible to save disk space by only shipping one copy? -- System Information: Debian Release: wheezy/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: amd64 (x86_64) Kernel: Linux 2.6.32-5-amd64 (SMP w/6 CPU cores) Locale: LANG=C, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash Versions of packages llvm-3.2-dev depends on: ii libc6 2.13-37 ii libffi-dev 3.0.10-3 ii libffi5 3.0.10-3 ii libgcc1 1:4.7.2-4 ii libstdc++6 4.7.2-4 ii llvm-3.23.2-2 llvm-3.2-dev recommends no packages. llvm-3.2-dev suggests no packages. -- no debconf information -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#696914: unzip mangles filenames with no option to switch it off
Package: unzip Version: 6.0-8 Severity: normal I often receive zip files with japanese (or other cjk) filenames encoded in a variety of formats, usually gbk or cp932. With older versions of unzip (5.x), I could specify the encoding of the filenames, which wasn't optimal, but let me recover filenames (either by specifying the correct encoding, or using latin1 to get the raw filenames and converting myself). Unzip 6.x seems to mangle all these filenames into mojibake, and there doesn't seem to be any option to switch this off. Here is an example zip file, created with minizip in a locale using latin1 encoding: http://data.plan9.de/gbk.zip It contains a directory that happens to be the gbk-encoded filename 写真集, hex d0b4d5e6bcaf, which also happens to be a valid latin1 filename. The expectation for unzip would be to create a directory with that exact name, regardless of the gbk encoding, because the filename is also a valid latin1 filename. minizip and 7z both create this filename, but unzip mangles it to: f0a669b52bbb (hex). neither -U, nor -UU, nor -L seem to have any effect on this. In fact, it seems unzip mangles all filenames containing filenames containing 127 codes that aren't valid utf-8 now. -- System Information: Debian Release: wheezy/sid APT prefers stable APT policy: (990, 'stable'), (500, 'unstable'), (500, 'testing'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 3.2.0-4-amd64 (SMP w/4 CPU cores) Locale: LANG=C, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash Versions of packages unzip depends on: ii libbz2-1.01.0.6-4high-quality block-sorting file co ii libc6 2.13-37Embedded GNU C Library: Shared lib unzip recommends no packages. Versions of packages unzip suggests: ii zip 3.0-3 Archiver for .zip files -- 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#696736: Insecure permissions on database files
Hi Carl Reading trough the code a bit: On Sat, Dec 29, 2012 at 08:56:07AM +0100, Salvatore Bonaccorso wrote: http://www.openwall.com/lists/oss-security/2012/11/16/2 http://people.canonical.com/~ubuntu-security/cve/2012/CVE-2012-5577.html http://people.canonical.com/~ubuntu-security/cve/2012/CVE-2012-5578.html These seems to be introduced in upstream 0.9.1 by fixing: * CryptedFileKeyring now uses PBKDF2 to derive the key from the user's password and a random hash. The IV is chosen randomly as well. All the stored passwords are encrypted at once. Any keyrings using the old format will be automatically converted to the new format (but will no longer be compatible with 0.9 and earlier). The user's password is no longer limited to 32 characters. PyCrypto 2.5 or greater is now required for this keyring. which is [1,2]. If I see it correctly introduced with commit[3], changed at least to current form in [4]. [1]: http://bugs.debian.org/675379 (CVE-2012-4571) [2]: https://bugs.launchpad.net/ubuntu/+source/python-keyring/+bug/1004845 [3]: https://bitbucket.org/kang/python-keyring-lib/commits/576e21ab1e6dba1cfb13a1112841798679c21057 [4]: https://bitbucket.org/kang/python-keyring-lib/commits/7b324f00f28d28afb9be371f0f4088d385cc15f2 Does this looks correct? So if wheezy will get a fix for CVE-2012-4571, then it also needs the above fixes. Regards, Salvatore signature.asc Description: Digital signature
Bug#696912: libperl-critic-perl: Documentation::RequirePodLinksIncludeText is obsolete
Hi Russ On Fri, Dec 28, 2012 at 11:43:14PM -0800, Russ Allbery wrote: (I know this should to go RT, but I'm out of brain for the day. I'll forward it to RT probably tomorrow if someone doesn't beat me to it.) Forwarded to the RT: http://rt.cpan.org/Public/Bug/Display.html?id=82321 Regards, Salvatore signature.asc Description: Digital signature
Bug#696836: RFP: libmath-pari-perl -- Perl bindings for PARI
Hi On Sat, Dec 29, 2012 at 02:26:52AM +0100, gregor herrmann wrote: Crypt::RSA Here we have #532839 (I haven't looked if it stills needs Math::Pari) Short note on that. Even if I have the ITP, as soon it's possible (or packaging the alternative) and I would not do it, please take over (as long it's maintained under the Debian Perl Group umbrella ;-)). Regards, Salvatore signature.asc Description: Digital signature
Bug#685251: [Openstack-devel] Fixing Debian bug #685251 for the ryu plugin in Openstack
Hi Julien I have now finally got enough time to actually do this backport. I have attached the proposal as a diff file. If you accept this change I will upload it to testing-proposed-updates. I do not know if this kind of change requires work from ftp-masters as it actually removes binary packages. This time the change is minimal and do not include anything from 2012.1-6. Thanks for your consideration. // Ola PS. I made a mistake in the analysis of -6 version. It was not uploaded before the freeze, it was checked in to git before that but was never uploaded until much later (by Loic). DS. On Wed, Nov 14, 2012 at 04:39:20PM +0800, Thomas Goirand wrote: On 11/14/2012 05:30 AM, Ola Lundqvist wrote: Hi Thomas and Julien The 2012.1-6 upload was done before the freeze That isn't right. The freeze date was the 30th of June, while the package was uploaded by Loic on the 6th of July. See the PTS: http://packages.qa.debian.org/q/quantum.html Though your changes were committed to our Git on Alioth before the freeze (on the 28th of June). and the plan was to have it included in testing before the freeze. Apparently that did not happen. I was under the impression that the freeze would be to uploads after the freeze, not to the packages that had not yet done the transition. Apparently I was wrong, and if that have cause this problem, I'm sorry for that. You were right, but the package was uploaded *after* the freeze. Which is the sole reason why it didn't migrate to Wheezy (well, that, and the fact you didn't ask for an unblock...). We did not have any bug report about the issues for that change. Instead I did those changes in order to solve problems that were similar to issues in other packages. It was more of a cleanup work in order to avoid bug reports in the future. We did have issues with the conflicts, replaces, breaks in other packages and if I remember correctly they were important also for this package. It is some time since I did this so I do not remember all the details. I do agree that the provides/conflicts/replaces/breaks fixes should be in Wheezy. I think the 2012.1-6 upload was a good thing for the package, especially for upgrade from earlier versions. That is however not such a big problem for this release as it has not been part of stable before. It may be an issue for later releases though. From a release team perspective I understand that you do not want large last minute changes to packages. I can not motivate the change to be that strong to be forced in. If you want I can make a proposed patch based on the changes Thomas made for 2012.1-7 and void the changes for 2012.1-6. YES! Please do so and deal with the unblock for your changes. :) It by the way would be nice and save time if the release team was telling what part of the changes are rejected and for what reason. Cheers, Thomas -- --- 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 / --- diff -uNr quantum-2012.1-olaorig/debian/changelog quantum-2012.1/debian/changelog --- quantum-2012.1-olaorig/debian/changelog 2012-06-12 18:15:41.0 + +++ quantum-2012.1/debian/changelog 2012-12-29 08:50:07.943438606 + @@ -1,3 +1,12 @@ +quantum (2012.1-5wheezy1) testing-proposed-updates; urgency=high + + * Non-maintainer upload. + * Backport of the removal of ryu app from 2012.1-7. Closes: #685251. +This needs to go directly to testing as the changes in 2012.1-6 is +too excessive. + + -- Ola Lundqvist o...@debian.org Sat, 29 Dec 2012 08:38:07 + + quantum (2012.1-5) unstable; urgency=low * Really fix upgrade from version lt 2012.1-2. Closes: #672170 diff -uNr quantum-2012.1-olaorig/debian/changelog~ quantum-2012.1/debian/changelog~ --- quantum-2012.1-olaorig/debian/changelog~ 1970-01-01 00:00:00.0 + +++ quantum-2012.1/debian/changelog~ 2012-12-29 08:48:38.295455277 + @@ -0,0 +1,182 @@ +quantum (2012.1-5wheezy1) testing-proposed-updates; urgency=high + + * Non-maintainer upload. + * Backport of the removal of ryu app from 2012.1-7. Closes: #685251. + + -- Ola Lundqvist o...@debian.org Sat, 29 Dec 2012 08:38:07 + + +quantum (2012.1-5) unstable; urgency=low + + * Really fix upgrade from version lt 2012.1-2. Closes: #672170 + * Tiny changes in packages description to make lintian happy + * Add missing upstream man pages + * Add patches description to make lintian happy + * Install man pages + + -- Mehdi Abaakouk sil...@sileht.net Wed, 23 May 2012 00:25:14 +0200 + +quantum (2012.1-4) unstable; urgency=low + + * Fix upgrade from version lt 2012.1-2. Closes: #672170
Bug#696530: menu-xdg: Populates XDG user directory with system entriesi
On Sat, Dec 29, 2012 at 02:22:45AM +0100, Josselin Mouette wrote: tag 696530 + patch kthxbye Le samedi 29 décembre 2012 à 02:17 +0100, Josselin Mouette a écrit : I have suggested two very simple fixes. For the sake of completeness, let’s add a patch for one of them. What does it do ? Cheers, -- Bill. ballo...@debian.org Imagine a large red swirl here. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#696530: menu-xdg: Populates XDG user directory with system entriesi
On Sat, Dec 29, 2012 at 02:17:18AM +0100, Josselin Mouette wrote: Le samedi 29 décembre 2012 à 00:31 +0100, Bill Allombert a écrit : I am resetting the severity to wishlist because this behaviour is compliant with the menu documentation, the Debian menu subpolicy, and the XDG menu specification. http://standards.freedesktop.org/menu-spec/menu-spec-latest.html#locations Now of course you can find an interpretation where this means applications installed by root can end up in $XDG_DATA_HOME, because this wasn’t written by a lawyer. If that is what you seek, maybe we should get the specification amended to make this explicit, but anyway the spirit of the specification is already very clear. The XDG menu specification allows the user to install entries that duplicate entries in the root directory. That what running update-menus as a user is doing, no more no less. Cheers, -- Bill. ballo...@debian.org Imagine a large red swirl here. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#696915: unblock: inkscape/0.48.3.1-1.2
Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: unblock Please unblock package inkscape inkscape 0.48.3.1-1.2 contains just one fix to fix the vulnerability CVE-2012-5656 (Debian #696485). Since this is the first NMU for inkscape and the changes of the previous NMU have not yet been committed to the inkscape packaging VCS [1], I am including a set of 4 patches which constitute the changes from 0.48.3.1-1 to 0.48.3.1-1.1 and from 0.48.3.1-1.1 to 0.48.3.1-1.2. Relevant for this unblock are the last two patches only, since the version of inkscape in testing is 0.48.3.1-1.1. I am only including the first two patches so that anyone is able to view the changes as compared to HEAD of the packaging VCS [1]. Relevant bug is #696485 [2]. unblock inkscape/0.48.3.1-1.2 Cheers, Adrian [1] git://git.debian.org/git/collab-maint/inkscape.git [2] http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=696485 -- System Information: Debian Release: 7.0 APT prefers testing APT policy: (500, 'testing'), (100, 'unstable'), (1, 'experimental') 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) (ignored: LC_ALL set to en_US.UTF-8) Shell: /bin/sh linked to /bin/dash From 3a8117fa7d075eb8db0aee2fa45f59252f1cb02d Mon Sep 17 00:00:00 2001 From: Pino Toscano p...@debian.org Date: Mon, 24 Dec 2012 00:54:40 +0100 Subject: [PATCH 1/4] - switch the libpng12-dev build dependency to libpng-dev (Closes: #662378) - add the libpoppler-private-dev build dependency (Closes: #660987) --- debian/control |3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/debian/control b/debian/control index f54b02e..50990b7 100644 --- a/debian/control +++ b/debian/control @@ -22,7 +22,8 @@ Build-Depends: autoconf, liblcms1-dev, libmagick++-dev, libpango1.0-dev, - libpng12-dev, + libpng-dev, + libpoppler-private-dev, libpoppler-glib-dev, libpopt-dev, libsigc++-2.0-dev (= 2.0.16-2), -- 1.7.10.4 From 5a34d3a6f6b0b0d958710e47a4bec61b4a408ad4 Mon Sep 17 00:00:00 2001 From: Pino Toscano p...@debian.org Date: Mon, 24 Dec 2012 00:57:42 +0100 Subject: [PATCH 2/4] Update Debian changelog for 0.48.3.1-1.1. --- debian/changelog |8 1 file changed, 8 insertions(+) diff --git a/debian/changelog b/debian/changelog index 4f92cf4..d1fdf41 100644 --- a/debian/changelog +++ b/debian/changelog @@ -1,3 +1,11 @@ +inkscape (0.48.3.1-1.1) unstable; urgency=low + + * Non-maintainer upload. + * Switch the libpng12-dev build dependency to libpng-dev (closes: #662378) + * Add the libpoppler-private-dev build dependency (closes: #660987) + + -- Pino Toscano p...@debian.org Fri, 15 Jun 2012 16:40:22 +0200 + inkscape (0.48.3.1-1) unstable; urgency=low * [cb1a6e2] delete 01-libwpg0.2.dpatch since proper patch appied upstream -- 1.7.10.4 From 0a512032d7b98b3e89201d84fb7e09d25add40e9 Mon Sep 17 00:00:00 2001 From: John Paul Adrian Glaubitz glaub...@physik.fu-berlin.de Date: Mon, 24 Dec 2012 00:58:35 +0100 Subject: [PATCH 3/4] Add Debian patch to fix vulnerability CVE-2012-5656. --- debian/patches/03-CVE-2012-5656.diff | 75 ++ debian/patches/series|1 + 2 files changed, 76 insertions(+) create mode 100644 debian/patches/03-CVE-2012-5656.diff diff --git a/debian/patches/03-CVE-2012-5656.diff b/debian/patches/03-CVE-2012-5656.diff new file mode 100644 index 000..c787ed4 --- /dev/null +++ b/debian/patches/03-CVE-2012-5656.diff @@ -0,0 +1,75 @@ +From eaa98e6b71d66195f0ca76358b85cca64d611fd9 Mon Sep 17 00:00:00 2001 +From: John Paul Adrian Glaubitz glaub...@physik.fu-berlin.de +Date: Sun, 23 Dec 2012 18:22:16 +0100 +Subject: [PATCH] Apply changes from upstream svn commit 11931 to fix + CVE-2012-5656. + +--- + src/preferences-skeleton.h|4 + src/ui/dialog/ocaldialogs.cpp | 10 -- + src/xml/repr-io.cpp |8 +++- + 3 files changed, 19 insertions(+), 3 deletions(-) + +diff --git a/src/preferences-skeleton.h b/src/preferences-skeleton.h +index 32f4b7c..e4dd2c8 100644 +--- a/src/preferences-skeleton.h b/src/preferences-skeleton.h +@@ -315,6 +315,10 @@ static char const preferences_skeleton[] = +clips=\16711935\ // 00ff00ff +masks=\65535\/\n // 0x + group id=\svgoutput\ usenamedcolors=\0\ numericprecision=\8\ minimumexponent=\-8\ inlineattrs=\0\ indent=\2\ allowrelativecoordinates=\1\ forcerepeatcommands=\0\/\n ++group id=\externalresources\\n ++ group id=\xml\ ++ allow_net_access=\0\/\n ++/group\n + group id=\forkgradientvectors\ value=\1\/\n + group id=\iconrender\ named_nodelay=\0\/\n + group id=\autosave\ enable=\0\ interval=\10\ path=\\ max=\10\/\n +diff --git
Bug#696915: unblock: inkscape/0.48.3.1-1.2
On Sat, Dec 29, 2012 at 10:31:55 +0100, John Paul Adrian Glaubitz wrote: Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: unblock Please unblock package inkscape NAK. The NMUed source package is native and contains a git tree, please fix that. Cheers, Julien signature.asc Description: Digital signature
Bug#696915: unblock: inkscape/0.48.3.1-1.2
On Sat, Dec 29, 2012 at 10:54:21AM +0100, Julien Cristau wrote: On Sat, Dec 29, 2012 at 10:31:55 +0100, John Paul Adrian Glaubitz wrote: Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: unblock Please unblock package inkscape NAK. The NMUed source package is native and contains a git tree, please fix that. True, I wasn't paying attention to the lintian checks when building the package with pbuilder. Since there is another issue with inkscape which seems to be RC-relevant, I'm going to fix the source package as well. Sorry for the mess. 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 -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#696530: menu-xdg: Populates XDG user directory with system entriesi
Le samedi 29 décembre 2012 à 10:09 +0100, Bill Allombert a écrit : For the sake of completeness, let’s add a patch for one of them. What does it do ? It makes it easy to blacklist all Debian entries at once (what we need to do in gnome-shell). On second thought, it needs another change in debian-menu.menu to avoid duplicating all entries at the toplevel: --- /etc/xdg/menus/debian-menu.menu 2012-10-29 10:55:55.0 +0100 +++ /tmp/debian-menu.menu 2012-12-29 11:04:13.099793320 +0100 @@ -6,6 +6,7 @@ DirectoryDir/var/lib/menu-xdg/desktop-directories/menu-xdg/DirectoryDir NameDebian/Name Directorydebian.directory/Directory +OnlyUnallocated/ Include CategoryX-Debian/Category /Include Le samedi 29 décembre 2012 à 10:16 +0100, Bill Allombert a écrit : The XDG menu specification allows the user to install entries that duplicate entries in the root directory. That what running update-menus as a user is doing, no more no less. You might have become a good lawyer. 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#684186: UPower does not send line_power_ACAD events
'upower --monitor' shows that the battery status is updated every 30
seconds ('device changed') while the ac adapter status will never be
updated.
When I plug in/out the ac adapter I get a message 'daemon changed' next
time the battery status gets updated; after that 'on battery' shows the
correct status (ac adapter plugged in: 'no', ac adapter plugged out:
'yes'). However, since the status of
device /org/freedesktop/UPower/devices/line_power_ACAD isn't correct,
action on critical battery won't be fired when the ac adapter was
plugged at boot time.
'udevadm monitor --kernel --udev' shows that the kernel (and udev) never
sends an event for none of the two devices (ac adapter battery). It
seems like UPower forces a battery status update every 30 seconds while
it doesn't force a status update for the ac adapter.
Maybe it would make sense if UPower would force an update not only for
the battery but also for the ac adapter.
signature.asc
Description: This is a digitally signed message part
Bug#690908: unblock: libdatetime-timezone-perl/1.51-1+2012g
On Fri, Oct 19, 2012 at 02:56:23 +0200, gregor herrmann wrote: Please unblock package libdatetime-timezone-perl 1.51-1+2012g. Unblocked 1:1.56-1+2012j. Cheers, Julien signature.asc Description: Digital signature
Bug#696040: gnome-shell: Gnome-shell 3.4.2-4 memory leak
Le vendredi 28 décembre 2012 à 14:10 -0500, Hashem Nasarat a écrit : Also, does gnome-shell in experimental still have this memory leak? If 3.4.2-3 doesn't exhibit this leak, it must be that 30_lockup_gc.path applied in 3.4.2-4 is the cause of this, right? Thank you, Captain Obvious. -- .''`. 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#664068: USB MIDI keyboard fails to initialize
# approximating (3.6.5 upstream)
found 664068 linux/3.6.4-1~experimental.1
# v3.8-rc1~29^2~45 (ALSA: usb-audio: Fix missing autopm for MIDI
# input, 2012-12-03), which is part of 3.2.36-rc1
tags 664068 + upstream patch fixed-upstream moreinfo
quit
Olivier MATZ wrote:
Here are the results of the tests, done on a kernel 3.6.5.
1/ vanilla kernel, AUTOSUSPEND_USBID_BLACKLIST=
0% of success among 5 tests
Thanks again for the quick testing.
Please test the attached patch series against a 3.2.y or 3.7.y kernel,
for example following the instructions from [1].
Regards,
Jonathan
[1] http://kernel-handbook.alioth.debian.org/ch-common-tasks.html#s4.2.2
or the corresponding page from the debian-kernel-handbook package
From: Takashi Iwai ti...@suse.de
Date: Mon, 3 Dec 2012 11:12:46 +0100
Subject: ALSA: usb-audio: Avoid autopm calls after disconnection
commit 59866da9e4ae54819e3c4e0a8f426bdb0c2ef993 upstream.
Add a similar protection against the disconnection race and the
invalid use of usb instance after disconnection, as well as we've done
for the USB audio PCM.
Bugzilla: https://bugzilla.kernel.org/show_bug.cgi?id=51201
Reviewd-by: Clemens Ladisch clem...@ladisch.de
Tested-by: Clemens Ladisch clem...@ladisch.de
Signed-off-by: Takashi Iwai ti...@suse.de
Signed-off-by: Ben Hutchings b...@decadent.org.uk
Signed-off-by: Jonathan Nieder jrnie...@gmail.com
---
sound/usb/midi.c | 23 ++-
1 file changed, 22 insertions(+), 1 deletion(-)
diff --git a/sound/usb/midi.c b/sound/usb/midi.c
index eeefbce3873c..c0054ee9389b 100644
--- a/sound/usb/midi.c
+++ b/sound/usb/midi.c
@@ -116,6 +116,7 @@ struct snd_usb_midi {
struct list_head list;
struct timer_list error_timer;
spinlock_t disc_lock;
+ struct rw_semaphore disc_rwsem;
struct mutex mutex;
u32 usb_id;
int next_midi_device;
@@ -1038,6 +1039,12 @@ static void substream_open(struct snd_rawmidi_substream
*substream, int open)
struct snd_usb_midi* umidi = substream-rmidi-private_data;
struct snd_kcontrol *ctl;
+ down_read(umidi-disc_rwsem);
+ if (umidi-disconnected) {
+ up_read(umidi-disc_rwsem);
+ return;
+ }
+
mutex_lock(umidi-mutex);
if (open) {
if (umidi-opened++ == 0 umidi-roland_load_ctl) {
@@ -1056,6 +1063,7 @@ static void substream_open(struct snd_rawmidi_substream
*substream, int open)
}
}
mutex_unlock(umidi-mutex);
+ up_read(umidi-disc_rwsem);
}
static int snd_usbmidi_output_open(struct snd_rawmidi_substream *substream)
@@ -1076,8 +1084,15 @@ static int snd_usbmidi_output_open(struct
snd_rawmidi_substream *substream)
snd_BUG();
return -ENXIO;
}
+
+ down_read(umidi-disc_rwsem);
+ if (umidi-disconnected) {
+ up_read(umidi-disc_rwsem);
+ return -ENODEV;
+ }
err = usb_autopm_get_interface(umidi-iface);
port-autopm_reference = err = 0;
+ up_read(umidi-disc_rwsem);
if (err 0 err != -EACCES)
return -EIO;
substream-runtime-private_data = port;
@@ -1092,8 +1107,10 @@ static int snd_usbmidi_output_close(struct
snd_rawmidi_substream *substream)
struct usbmidi_out_port *port = substream-runtime-private_data;
substream_open(substream, 0);
- if (port-autopm_reference)
+ down_read(umidi-disc_rwsem);
+ if (!umidi-disconnected port-autopm_reference)
usb_autopm_put_interface(umidi-iface);
+ up_read(umidi-disc_rwsem);
return 0;
}
@@ -1403,9 +1420,12 @@ void snd_usbmidi_disconnect(struct list_head* p)
* a timer may submit an URB. To reliably break the cycle
* a flag under lock must be used
*/
+ down_write(umidi-disc_rwsem);
spin_lock_irq(umidi-disc_lock);
umidi-disconnected = 1;
spin_unlock_irq(umidi-disc_lock);
+ up_write(umidi-disc_rwsem);
+
for (i = 0; i MIDI_MAX_ENDPOINTS; ++i) {
struct snd_usb_midi_endpoint* ep = umidi-endpoints[i];
if (ep-out)
@@ -2117,6 +2137,7 @@ int snd_usbmidi_create(struct snd_card *card,
umidi-usb_protocol_ops = snd_usbmidi_standard_ops;
init_timer(umidi-error_timer);
spin_lock_init(umidi-disc_lock);
+ init_rwsem(umidi-disc_rwsem);
mutex_init(umidi-mutex);
umidi-usb_id = USB_ID(le16_to_cpu(umidi-dev-descriptor.idVendor),
le16_to_cpu(umidi-dev-descriptor.idProduct));
--
1.8.1.rc3
From: Takashi Iwai ti...@suse.de
Date: Mon, 3 Dec 2012 11:30:50 +0100
Subject: ALSA: usb-audio: Fix missing autopm for MIDI input
commit f5f165418cabf2218eb466c0e94693b8b1aee88b upstream.
The commit [88a8516a: ALSA: usbaudio: implement USB autosuspend] added
the support of autopm for USB MIDI output, but it didn't take the MIDI
input into account.
This patch adds
Bug#685251: [Openstack-devel] Fixing Debian bug #685251 for the ryu plugin in Openstack
On 12/29/2012 04:57 PM, Ola Lundqvist wrote: Hi Julien I have now finally got enough time to actually do this backport. I have attached the proposal as a diff file. If you accept this change I will upload it to testing-proposed-updates. I do not know if this kind of change requires work from ftp-masters as it actually removes binary packages. This time the change is minimal and do not include anything from 2012.1-6. Thanks for your consideration. // Ola Hi, There's quite a few problems in your diff file. The next 3 points would be what I believe the release team would answer, the last point is specific to the Openstack packaging team. * Could you please send again the debdiff, but *WITHOUT* your *~ backup files? Probably you should have carefully read it before replying like this to the release team who is already overloaded with Debian tasks. That's the kind of joke they don't really like... * I don't think there's the need to use testing-proposed-updates. Uploading to SID will be just fine, as anyway, we haven't uploaded anything newer in SID which would pose a problem, and that we use Experimental for Folsom. (in other words: nothing prevents uploading to SID, and when we upload there it's in the hope it migrates to testing) * There is already a version -6 in SID. So you should really upload 2012.1-7, not 2012.1-5wheezy1, which is the scheme for security uploads in Debian Stable. * Our Git already contains entries for -6 and -7. Please use that, modifying the candidate version -7, and do not get out of sync with our Git please, otherwise it's going to be a nightmare! Also, this issue has been pending for 6 months! I do appreciate that you finally decide to work on it, even that late. But I continue to refuse to take the responsibility for it. The main mistake, IMO, was to leave the issue as-is, doing nothing to fix it. So you and Loic should really take the responsibility for the upload, and make sure it's in a correct shape *in time* for the release. I surely would feel bad if Quantum had to be removed from Wheezy. Please don't leave this pending again. 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#696884: enigmail 1.5 is available upstream
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Hi! Am 2012-12-28 19:41, schrieb Daniel Kahn Gillmor: Package: enigmail Version: 2:1.4.6+id17-1 Severity: wishlist As of a few days ago, enigmail 1.5 is available upstream. if we could have it in experimental, that'd be great! Uploaded. Is the enigmail debian packaging being tracked in some sort of public revision control system in a way that other packagers could collaborate? I'm not seeing how to get cleanly from upstream's source tarballs to debian's orig.tar.gz, for example. I'm using a git repository that is currently not published anywhere. It would not be a problem to publish it. However, the current situation for creating the orig tarball is a mess because I rely on a bazaar repo from the Ubuntu mozilla maintainers that contains the stripped down sources of Thunderbird to build enigmail and a self-written script to merge in the enigmail sources. There is also a d/rules target left from the Ubuntu people. Unfortunately this target does not verify the authenticity of the enigmail tarball but deletes it immediately, so I created my own script and check the authenticity manually (I did not remove that target because it would add further differences as compared to the Ubuntu version) Additionally, there is no guarantee that what the Ubuntu repo contains really builds. For icedove 17, what the repo contained did not build and needed a patch. I hope that this situation changes when we move to an icedove version that allows enigmail to work without any further binary components - that's one of the reasons why I have not invested time to make this situation more collaboration-friendly, another one is that nobody showed interest in collaborating. WM -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.12 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iQIcBAEBCAAGBQJQ3smLAAoJEIy+IZx0V22BDVQP/jX3tyXWBKLTFny34J40xEjT 71HyP4CtLjnGvKtrVyLKn5RrAPY+dMuGdpE5XHmQr22XjgZsotTUC9wQ0oyFDjCo QMaYi8okg14vfebcxuw3MVJn5o2fTc56kExitzJIqLI5lSHW8km39ANb6V2LFROk lWwvhx/nE1JzvNhHgc60VX3YIAZ6D3Z8ht0UbEanF1i9NiRQ0LCwAk4fUDed0Pkq MACC0XhkgEbXv1XILAMQVgyI6mBvxaS5sEBz4hf0lxaUbru2OFt9Ko7iqRTQ2B/B /e8NkvXHUl54aBlW99cOUugmsJo+xESvU/3yoR5dJLyHH5gEXwSYJo3N4Kl/O+u4 uhFqHlAFkDjLFNQQdhRew9OaMCyPZ3ZdiRK9HVIGFKpjBAXISFXh5zl0d+lLt+T7 LL74rnTI5k891Xczwcmve0dY9H86zKq7IqDCTmLE/kSkQVcmkNhAvghr5aFdzzZv h/6Cdt0VSeiLfHYMAswLj2Qb2wFpXh165FxXUAGS8ibX0d6AMcOro4xovdBOPjAG SEYjjwYG4UT9cvuaJOrxmieUo8lhGpywNkTzkq1RQqzSzFxmYVhDqwLxMkbKxAbr mb7u1snx7RAQ7XpsnO8pUyBUg+R7ZPkBv/ldR9RAZx3NnxvycUQ3bl9hS7L0vih6 W372OWBkOvPbUIoCTYTd =lQTm -END PGP SIGNATURE- -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#696417: pdfopt: crash on some input PDF file
Confirmed:
$ apt-cache policy ghostscript
ghostscript:
Installed: 9.05~dfsg-6.3
Candidate: 9.05~dfsg-6.3
Version table:
*** 9.05~dfsg-6.3 0
500 http://ftp.fr.debian.org/debian/ sid/main amd64 Packages
100 /var/lib/dpkg/status
$ pdftop test.pdf bla.pdf
Error reading a content stream. The page may be incomplete.
Error: /typecheck in --setfileposition--
Operand stack:
--nostringval-- 13 0 9047 13 9047 343 17
--nostringval-- --nostringval--
Execution stack:
%interp_exit .runexec2 --nostringval-- --nostringval--
--nostringval-- 2 %stopped_push --nostringval--
--nostringval-- --nostringval-- false 1 %stopped_push 1910
1 3 %oparray_pop 1909 1 3 %oparray_pop 1893 1 3
%oparray_pop 1787 1 3 %oparray_pop --nostringval--
%errorexec_pop .runexec2 --nostringval-- --nostringval--
--nostringval-- 2 %stopped_push --nostringval--
--nostringval-- --nostringval-- --nostringval-- --nostringval--
8680 --nostringval-- --nostringval-- %array_continue
--nostringval-- --nostringval-- %array_continue --nostringval--
Dictionary stack:
--dict:1163/1684(ro)(G)-- --dict:1/20(G)-- --dict:116/200(L)--
--dict:76/200(G)-- --dict:291/300(ro)(G)-- --dict:20/31(L)--
--dict:37/40(L)--
Current allocation mode is local
Last OS error: No such file or directory
Current file position is 38334
GPL Ghostscript 9.05: Unrecoverable error, exit code 1
Thanks
On Fri, Dec 21, 2012 at 12:54 PM, Bastien ROUCARIES
roucaries.bast...@gmail.com wrote:
Could you try to reproduce with unstable version?
Le 20 déc. 2012 16:18, Mathieu Malaterre ma...@debian.org a écrit :
Package: ghostscript
Version: 8.71~dfsg2-9
Severity: important
File: /usr/bin/pdfopt
I was trying to compress a PDF file generated from my HP/Scanner. The file
is reported as:
$ pdfinfo
Title: /tmp/simple-scan-J7U3PW.pdf
Producer: ImageMagick 6.6.0-4 2012-05-02 Q16
http://www.imagemagick.org
CreationDate: Thu Dec 20 15:36:45 2012
ModDate:Thu Dec 20 15:36:45 2012
Tagged: no
Pages: 1
Encrypted: no
Page size: 611.76 x 841.44 pts
File size: 1715008 bytes
Optimized: no
PDF version:1.3
This PDF makes pdfopt crashes with:
Error: /typecheck in --setfileposition--
Operand stack:
--nostringval-- 13 0 1714253 13 1714253 77 3348
--nostringval-- --nostringval--
Execution stack:
%interp_exit .runexec2 --nostringval-- --nostringval--
--nostringval-- 2 %stopped_push --nostringval-- --nostringval--
--nostringval-- false 1 %stopped_push 1910 1 3 %oparray_pop
1909 1 3 %oparray_pop 1893 1 3 %oparray_pop 1787 1 3
%oparray_pop --nostringval-- %errorexec_pop .runexec2
--nostringval-- --nostringval-- --nostringval-- 2 %stopped_push
--nostringval-- --nostringval-- --nostringval-- --nostringval--
--nostringval-- 1711312 --nostringval-- --nostringval--
%array_continue --nostringval-- --nostringval-- %array_continue
--nostringval--
Dictionary stack:
--dict:1163/1684(ro)(G)-- --dict:1/20(G)-- --dict:116/200(L)--
--dict:76/200(G)-- --dict:291/300(ro)(G)-- --dict:20/31(L)--
--dict:37/40(L)--
Current allocation mode is local
Last OS error: No such file or directory
Current file position is 38334
GPL Ghostscript 9.05: Unrecoverable error, exit code 1
There is one easy way to reproduce with any PDF generated by imagemagick:
$ sudo apt-get install imagemagick
$ convert -size 611x841 xc:white test.pdf
I am attaching test.pdf to this bug report, just in case.
Thanks
-- System Information:
Debian Release: 6.0.6
APT prefers stable-updates
APT policy: (500, 'stable-updates'), (500, 'stable'), (200, 'testing'),
(100, 'unstable')
Architecture: amd64 (x86_64)
Kernel: Linux 3.2.0-0.bpo.3-amd64 (SMP w/8 CPU cores)
Locale: LANG=en_US.utf8, LC_CTYPE=en_US.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Versions of packages ghostscript depends on:
ii debconf [de 1.5.36.1 Debian configuration
management sy
ii debianutils 3.4 Miscellaneous utilities
specific t
ii gsfonts 1:8.11+urwcyr1.0.7~pre44-4.2 Fonts for the Ghostscript
interpre
ii libc6 2.11.3-4 Embedded GNU C Library:
Shared lib
ii libgs8 8.71~dfsg2-9 The Ghostscript
PostScript/PDF int
ghostscript recommends no packages.
ghostscript suggests no packages.
-- debconf-show failed
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#696916: zangband: debian/copyright inaccurate by rewording
Package: zangband Severity: serious Version: 1:2.7.5pre1-6 The file debian/copyright contains this : The copyright is free for any use except commercial profit making. However this phrase is not used in the upstream licenses. Please don't reword licenses. See verbatim copy on this page: http://www.debian.org/doc/debian-policy/ch-docs.html#s-copyrightfile -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#696917: roxterm does not handle quotes in URLs correctly
Source: roxterm
Version: 2.6.5-1
Severity: grave
Tags: security
When trying to click on an URL inside the roxterm window that contains
a single quote ('), the resulting command sent to the shell includes
this quote and is interpreted by the shell, for example:
http://example.com/quote'here
will be handled as
x-www-browser 'http://example.com/quote'here'
In this example, shell will complain that there's no closing quote before
the end of command, but I can guess this can be (ab)used for some more
interesting scenarious, like to spawn commands unexpectedly:
http://example.com/one'foo|bar'two
or the like. The charset allowed in this context does not contain space
and tab, so it isn't directly possible to run some even more interesting
commands (like rm -rf /), but it is enough for a good exploit already.
I think this issue deserves a CVE#.
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#696918: unblock: freetype/2.4.9-1.1
Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: unblock
Hi Release Team
Please unblock package freetype (but we can wait first the two day
period to have the changes in unstable witouh an already granted
unblock).
The upload fixes three CVEs for freetype, see #696691:
CVE-2012-5668: NULL Pointer Dereference in bdf_free_font.
CVE-2012-5669: Out-of-bounds read in _bdf_parse_glyphs.
CVE-2012-5670: Out-of-bounds write in _bdf_parse_glyphs.
The package also provides a udeb, so this needs an explicit ACK by
Cyril?
I have attached the full debdiff against the current version in
testing.
unblock freetype/2.4.9-1.1
Many thanks for your work, and
Regards,
Salvatore
Base version: freetype_2.4.9-1 from testing
Target version: freetype_2.4.9-1.1 from unstable
Hints in place:
== freeze
# These udebs can be handled directly by britney
# but are currently blocked at the d-i RM's request
block-udeb freetype
debian/patches-freetype/savannah-bug-37905.patch | 26 +++
debian/patches-freetype/savannah-bug-37906.patch | 26 +++
debian/patches-freetype/savannah-bug-37907.patch | 24 +
freetype-2.4.9/debian/changelog | 16 ++
freetype-2.4.9/debian/patches-freetype/series|3 ++
5 files changed, 95 insertions(+)
diff -u freetype-2.4.9/debian/changelog freetype-2.4.9/debian/changelog
--- freetype-2.4.9/debian/changelog
+++ freetype-2.4.9/debian/changelog
@@ -1,3 +1,19 @@
+freetype (2.4.9-1.1) unstable; urgency=high
+
+ * Non-maintainer upload.
+Upload ACKed by Steve Langasek vor...@debian.org on #debian-devel.
+ * Add savannah-bug-37905.patch patch
+[SECURITY] CVE-2012-5668: NULL Pointer Dereference in bdf_free_font.
+(Closes: #696691)
+ * Add savannah-bug-37906.patch patch
+[SECURITY] CVE-2012-5669: Out-of-bounds read in _bdf_parse_glyphs.
+(Closes: #696691)
+ * Add savannah-bug-37907.patch patch
+[SECURITY] CVE-2012-5670: Out-of-bounds write in _bdf_parse_glyphs.
+(Closes: #696691)
+
+ -- Salvatore Bonaccorso car...@debian.org Fri, 28 Dec 2012 21:32:28 +0100
+
freetype (2.4.9-1) unstable; urgency=low
* New upstream release
diff -u freetype-2.4.9/debian/patches-freetype/series
freetype-2.4.9/debian/patches-freetype/series
--- freetype-2.4.9/debian/patches-freetype/series
+++ freetype-2.4.9/debian/patches-freetype/series
@@ -5,0 +6,3 @@
+savannah-bug-37905.patch
+savannah-bug-37906.patch
+savannah-bug-37907.patch
only in patch2:
unchanged:
--- freetype-2.4.9.orig/debian/patches-freetype/savannah-bug-37905.patch
+++ freetype-2.4.9/debian/patches-freetype/savannah-bug-37905.patch
@@ -0,0 +1,26 @@
+From 9b6b5754b57c12b820e01305eb69b8863a161e5a Mon Sep 17 00:00:00 2001
+From: Werner Lemberg w...@gnu.org
+Date: Sat, 15 Dec 2012 00:34:41 +
+Subject: [bdf] Fix Savannah bug #37905.
+
+* src/bdf/bdflib.c (_bdf_parse_start): Reset `props_size' to zero in
+case of allocation error; this value gets used in a loop in
+`bdf_free_font'.
+---
+diff --git a/src/bdf/bdflib.c b/src/bdf/bdflib.c
+index ed08a6e..8d7f9a0 100644
+--- a/src/bdf/bdflib.c
b/src/bdf/bdflib.c
+@@ -2169,7 +2169,10 @@
+ p-cnt = p-font-props_size = _bdf_atoul( p-list.field[1], 0, 10 );
+
+ if ( FT_NEW_ARRAY( p-font-props, p-cnt ) )
++ {
++p-font-props_size = 0;
+ goto Exit;
++ }
+
+ p-flags |= _BDF_PROPS;
+ *next = _bdf_parse_properties;
+--
+cgit v0.9.0.2
only in patch2:
unchanged:
--- freetype-2.4.9.orig/debian/patches-freetype/savannah-bug-37907.patch
+++ freetype-2.4.9/debian/patches-freetype/savannah-bug-37907.patch
@@ -0,0 +1,24 @@
+From 7f2e4f4f553f6836be7683f66226afac3fa979b8 Mon Sep 17 00:00:00 2001
+From: Werner Lemberg w...@gnu.org
+Date: Sat, 15 Dec 2012 08:39:41 +
+Subject: [bdf] Fix Savannah bug #37907.
+
+* src/bdf/bdflib.c (_bdf_parse_glyphs) ENCODING: Normalize
+negative second parameter of `ENCODING' field also.
+---
+diff --git a/src/bdf/bdflib.c b/src/bdf/bdflib.c
+index f9c06ca..365e671 100644
+--- a/src/bdf/bdflib.c
b/src/bdf/bdflib.c
+@@ -1624,6 +1624,9 @@
+ if ( p-glyph_enc == -1 p-list.used 2 )
+ p-glyph_enc = _bdf_atol( p-list.field[2], 0, 10 );
+
++ if ( p-glyph_enc -1 )
++p-glyph_enc = -1;
++
+ FT_TRACE4(( DBGMSG2, p-glyph_enc ));
+
+ /* Check that the encoding is in the Unicode range because */
+--
+cgit v0.9.0.2
only in patch2:
unchanged:
--- freetype-2.4.9.orig/debian/patches-freetype/savannah-bug-37906.patch
+++ freetype-2.4.9/debian/patches-freetype/savannah-bug-37906.patch
@@ -0,0 +1,26 @@
+From 07bdb6e289c7954e2a533039dc93c1c136099d2d Mon Sep 17 00:00:00 2001
+From: Werner Lemberg w...@gnu.org
+Date: Sat, 15 Dec 2012 01:02:23 +
+Subject: [bdf] Fix Savannah bug #37906.
+
+* src/bdf/bdflib.c (_bdf_parse_glyphs): Use correct array size for
+checking `glyph_enc'.
+---
+diff --git a/src/bdf/bdflib.c
Bug#689154: unblock: gnunet/0.9.3-4
Sorry for the delay in getting back to you... On Sun, Dec 2, 2012 at 18:55:56 +0100, Bertrand Marc wrote: Last thing: gnunet-0.9.3-4 was uploaded to unstable with fixes for a lot of not-RC bugs. So I guess I need to prepare a new version targeting testing-proposed-updates ? No, the changes you want to see in wheezy can still go to unstable, reverting the extra stuff in -4. Cheers, Julien signature.asc Description: Digital signature
Bug#691696: [Python-apps-team] Getting Trac 0.12.4 into wheezy?
On Sun, Nov 11, 2012 at 12:51:47 +0100, Arthur de Jong wrote: I don't think trac-spamfilter works though with this version (but also doesn't work with 0.12.3-1, see #691696). I think #691696 should be RC and trac-spamfilter should probably be removed from wheezy. I've just upgraded the severity of that bug and added a remove hint. Cheers, Julien signature.asc Description: Digital signature
Bug#696919: zangband: incomplete debian/copyright
Package: zangband Severity: serious Version: 1:2.7.5pre1-6 The file debian/copyright is not complete, because there are additional copyright holders and licenses not yet mentioned in debian/copyright. See for example lua.h and readdib.c. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#696920: briquolo: incomplete debian/copyright
Package: briquolo Severity: serious Version: 0.5.7-3 The file debian/copyright is not complete, see for example data/data/DejaVuSans.ttf (DejaVuSans.ttf-LICENSE) and intl/localcharset.c (LGPL2+). -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#654341: inkscape reads .eps files from /tmp instead of the current directory
Hi I have asked if this warrants a CVE and if one can be assigned. If so I will then update it here. Here is the temporary entry in the security-tracker: https://security-tracker.debian.org/tracker/TEMP-0654341-9198B9 p.s.: A user might be tricked also to save the open file and loose data, by overwriting the file in current directory by the content found in the /tmp file. Regards, Salvatore signature.asc Description: Digital signature
Bug#696921: lxc-ps fails when /bin/sh is symlink to /bin/dash - repeat of #694448
Package: lxc Version: 0.9.0~alpha2-1 Severity: important Dear Maintainer, This is a repeat of closed bug #694448 - the fix to that bug report has been reverted. Issue is: # lxc-ps /usr/bin/lxc-ps: 64: /usr/bin/lxc-ps: [[: not found /usr/bin/lxc-ps: 100: /usr/bin/lxc-ps: declare: not found /usr/bin/lxc-ps: 104: /usr/bin/lxc-ps: Syntax error: ( unexpected (expecting fi) The shebang is #!/bin/sh and /bin/sh is a link to /bin/dash (default on Debian systems). [[ is not valid in dash. declare is a bash shell builtin but not in dash. A fix is to change to change the shebang to #!/bin/bash Regards, Gary -- System Information: Debian Release: 7.0 APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 3.2.0-4-amd64 (SMP w/2 CPU cores) Locale: LANG=en_GB.ISO-8859-15, LC_CTYPE=en_GB.ISO-8859-15 (charmap=ISO-8859-15) Shell: /bin/sh linked to /bin/dash Versions of packages lxc depends on: ii debconf [debconf-2.0] 1.5.49 ii libapparmor1 2.7.103-4 ii libc6 2.13-37 ii libcap21:2.22-1.2 ii multiarch-support 2.13-37 Versions of packages lxc recommends: ii debootstrap 1.0.46 ii libcap2-bin 1:2.22-1.2 Versions of packages lxc suggests: ii rsync 3.0.9-4 -- Configuration Files: /etc/lxc/lxc.conf changed [not included] -- debconf information: lxc/shutdown: /usr/bin/lxc-halt * lxc/directory: /lxc lxc/title: lxc/auto: true -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#690574: oss4-base: depends on linux-sound-base
Package: oss4-dkms Version: 4.2-build2007-2 Followup-For: Bug #690574 Hello, the upgrade to not-linux-soud-base fails. The links pointing to linux-sound-base are considered modified conffiles and not removed. OSS4 does not load then. # ls -l /etc/modprobe.d/*oss* lrwxrwxrwx 1 root root 41 Jun 7 2012 /etc/modprobe.d/blacklist-oss.conf - /lib/linux-sound-base/noOSS.modprobe.conf -rw-r--r-- 1 root root 70 Dec 4 2009 /etc/modprobe.d/oss4-base.conf lrwxrwxrwx 1 root root 42 May 17 2012 /etc/modprobe.d/oss4-base_noALSA.conf - /lib/linux-sound-base/noALSA.modprobe.conf -rw-r--r-- 1 root root 3916 Dec 16 02:08 /etc/modprobe.d/oss4-base_noALSA.conf.dpkg-new lrwxrwxrwx 1 root root 41 May 17 2012 /etc/modprobe.d/oss4-base_noOSS3.conf - /lib/linux-sound-base/noOSS.modprobe.conf -rw-r--r-- 1 root root 1059 Dec 16 02:08 /etc/modprobe.d/oss4-base_noOSS3.conf.dpkg-new -rw-r--r-- 1 root root 356 Jun 7 2012 /etc/modprobe.d/oss-compat.conf -- System Information: Debian Release: 7.0 APT prefers testing APT policy: (990, 'testing'), (171, 'unstable'), (151, 'experimental'), (121, 'precise-updates'), (121, 'precise-security'), (121, 'precise'), (101, 'stable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.7.1-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 oss4-dkms depends on: ii dkms 2.2.0.3-1.2 ii dpkg-dev 1.16.9 ii linux-headers-3.0.0-14 [linux-headers] 3.0.0-14.23 ii linux-headers-3.0.0-14-server [linux-headers] 3.0.0-14.23 ii linux-headers-3.0.0-15 [linux-headers] 3.0.0-15.26 ii linux-headers-3.0.0-15-server [linux-headers] 3.0.0-15.26 ii linux-headers-3.0.0-16 [linux-headers] 3.0.0-16.29 ii linux-headers-3.0.0-16-server [linux-headers] 3.0.0-16.29 ii linux-headers-3.1.0-1-amd64 [linux-headers]3.1.6-1 ii linux-headers-3.2.0-24 [linux-headers] 3.2.0-24.39 ii linux-headers-3.6.4-amd64 [linux-headers] 3.6.4-amd64-10.00.Custom ii linux-headers-3.7.0-rc3-amd64 [linux-headers] 3.7.0-rc3-amd64-10.00.Custom ii linux-headers-3.7.1-amd64 [linux-headers] 1 ii oss4-base 4.2-build2006-2+deb7u1 oss4-dkms recommends no packages. oss4-dkms 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#696820: Error: open(/var/mail/USER) failed: Permission denied
Quoting Jaldhar H. Vyas (2012-12-29 02:52:15) On Sat, 29 Dec 2012, Jonas Smedegaard wrote: Latest package release changed /etc/dovecot/conf.d/10-mail.conf to hardcode mail_location to use mbox and /var/mail as mailspool. Upstream default of leaving that variable undefined is to try both mbox and Maildir. But I can't do that. See #693114. So I had to pick something as a default and mbox in /var/mail is the lowest common denominator. Arrgh - I was hit by bug#693621 (NEWS file not registered). - 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#696917: roxterm does not handle quotes in URLs correctly
Control: severity -1 normal
Control: tags -1 - security
29.12.2012 15:49, Michael Tokarev wrote:
Source: roxterm
Version: 2.6.5-1
Severity: grave
Tags: security
When trying to click on an URL inside the roxterm window that contains
a single quote ('), the resulting command sent to the shell includes
this quote and is interpreted by the shell, for example:
http://example.com/quote'here
will be handled as
x-www-browser 'http://example.com/quote'here'
In this example, shell will complain that there's no closing quote before
the end of command, but I can guess this can be (ab)used for some more
interesting scenarious, like to spawn commands unexpectedly:
http://example.com/one'foo|bar'two
After trying to exploit this, followed by the code analisis, I found out
that this is not the case.
roxterm indeed constructs the command line in a single string, and adds
single quotes around the URL. But next thing it does is to call
g_shell_parse_argv() on the resulting string, to create argv[] array.
And this is this function - g_shell_parse_argv() from glib - which
complains about unbalanced quotes. No shell or external command run
is actually involved here. So I don't think this issue is exploitable.
The bug is present still, since it errors out on certain URLs instead of
displaying them, but it is not a security issue anymore, as I initially
thought.
Downgrading severity and untagging accordingly.
I think the easiest fix will be to disallow single quotes in URLs just
like double quotes are currently handled (so that a single quote will
be treated as end of URL). Yes, this way it wont be possible to use
URLs with quotes in them, like
http://en.wikipedia.org/wiki/What_we've_got_here_is_(a)_failure_to_communicate
but it's a minor issue in my opinion.
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#696899: RFS: premake4/4.3-1 [ITP] -- cross-platform build script generator
Hi Vincent,
Thanks for your feedback. I have made all the changes you suggested
and re-uploaded. I modified your patch slightly to add bsd to the
linux configuration in the premake4.lua. It doesn't matter too much
for the package build as the Makefile is already pre-generated but was
needed for submitting to upstream.
Cheers,
Cameron.
On 29 December 2012 17:35, Vincent Cheng vincentc1...@gmail.com wrote:
Hi Cameron,
On Fri, Dec 28, 2012 at 4:09 PM, Cameron Hart c...@bitshifter.net.nz wrote:
Package: sponsorship-requests
Severity: wishlist
Dear mentors,
I am looking for a sponsor for my package premake4
* Package name: premake4
Version : 4.3-1
Upstream Author : Jason Perkins and individual contributors
* URL : http://industriousone.com/premake
* License : BSD
Section : devel
snip
IANADD, but here's a brief review:
- debian/patches/rename-changelog.diff is entirely the wrong way to
rename a changelog (and it results in a really large diff, yuck). If
you were using dh, the following does what you want:
override_dh_installchangelogs:
dh_installchangelogs CHANGES.txt
I'm not sure about cdbs since I rarely use it, but I believe you can
use DEB_INSTALL_CHANGELOGS_ALL to accomplish the same thing.
- The following patch should fix the build failure on
kfreebsd-{i386,amd64} (I don't have a kfreebsd VM to test with right
now, sorry). Please forward upstream.
--- a/src/host/premake.h
+++ b/src/host/premake.h
@@ -15,7 +15,7 @@
#if defined(__linux__)
#define PLATFORM_LINUX(1)
#define PLATFORM_STRING linux
-#elif defined(__FreeBSD__) || defined(__NetBSD__) || defined(__OpenBSD__)
+#elif defined(__FreeBSD__) || defined(__NetBSD__) ||
defined(__OpenBSD__) || defined(__FreeBSD_kernel__)
#define PLATFORM_BSD (1)
#define PLATFORM_STRING bsd
#elif defined(__APPLE__) defined(__MACH__)
- A few pedantic notes on debian/copyright. Consider using the SPDX
names, i.e. BSD-3-clause instead of just BSD, and Expat instead of
MIT. Also, you may (or may not) want to consider using a more
permissive license for your Debian packaging files (BSD/MIT to match
upstream instead of GPL), to make it possible for e.g. upstream to
take patches applied to your package in Debian.
Regards,
Vincent
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#563376: Towards Debian bug #563376
Hello, Harald. I've faced the same bug you reported: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=563376 kernel-package: Cross-compile builds wrong architecture in kernel_headers but it hasn't been fixed (for 3 years :(). Have you got some workaround of self-made patch to cope with this issue? Thanks in advance. Regards, post-factum -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#696922: kernel-package: kernel-headers does not include linux/limits.h
Package: kernel-package
Version: 12.036+nmu3
Severity: normal
Hello,
oss4 build includes this code to fish limits.h from the kernel headers:
test ! -e /lib/modules/${kernelver}/build/include/linux/limits.h || cp
/lib/modules/${kernelver}/build/include/linux/limits.h
${dkms_tree}/${PACKAGE_NAME}/${PACKAGE_VERSION}/build/core ; \
test ! -e
/lib/modules/${kernelver}/source/include/linux/limits.h || cp
/lib/modules/${kernelver}/source/include/linux/limits.h
${dkms_tree}/${PACKAGE_NAME}/${PACKAGE_VERSION}/build/core ;
This fails with kernel-package generated kernel-headers package.
-- System Information:
Debian Release: 7.0
APT prefers testing
APT policy: (990, 'testing'), (171, 'unstable'), (151, 'experimental'), (121,
'precise-updates'), (121, 'precise-security'), (121, 'precise'), (101, 'stable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 3.7.1-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 kernel-package depends on:
ii binutils 2.22-7.1
ii build-essential11.5ubuntu2.1
ii debianutils4.3.2
ii file 5.11-2
ii gettext0.18.1.1-9
ii make 3.81-8.2
ii module-init-tools 9-2
ii po-debconf 1.0.16+nmu2ubuntu1
ii util-linux 2.20.1-5.3
Versions of packages kernel-package recommends:
ii cpio 2.11-8
Versions of packages kernel-package suggests:
pn btrfs-tools none
ii bzip2 1.0.6-4
pn docbook-utils none
ii e2fsprogs 1.42.5-1
pn grub | grub2none
ii initramfs-tools [linux-initramfs-tool] 0.109
pn jfsutilsnone
pn libncurses-dev none
ii linux-source-3.6 [linux-source] 3.6.9-1~experimental.1
pn mcelog none
ii oprofile0.9.6-1.3ubuntu1
pn pcmciautils none
ii ppp 2.4.5-5.1+b1
ii procps 1:3.3.3-2
pn quota none
pn reiserfsprogs none
pn squashfs-tools none
ii udev175-7
pn xfsprogsnone
pn xmlto 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#695508: udd: bugs.cgi - bugs filed against multiple packages is not associated with a source
On 10/12/12 at 00:20 +0100, Ivo De Decker wrote:
Hi Niels,
On Sun, Dec 09, 2012 at 01:22:39PM +0100, Niels Thykier wrote:
The bug #694368 is filed against libfuzzy2, libfuzzy-dev (src:
ssdeep). At least in the view [1], this means that the package
column gets the PTS link wrong. It links to p.qa.d.o/libfuzzy2 and
p.qa.d.o/libfuzzy-dev (respectively), but it should have linked to
p.qa.d.o/ssdeep in both cases. This is not a huge problem as the
PTS fixes this with a redirect, but ...
I suspect also causes bugs.cgi not discovering the unblock hint for
ssdeep. On a related note; as ssdeep is unblocked the package will
problably migrate in a week (causing the example disappear from the
view). Let me know if I should find more information before then.
This bug isn't caused by the cgi, but by the import script. In
bugs_gatherer.pl (l 218):
my $srcpkg;
if ($bug{package} =~ /^src:(.*)/)
{
$srcpkg = $1;
} else {
$srcpkg = exists($pkgsrc{$bug{package}}) ? $pkgsrc{$bug{package}} :
$bug{package};
}
For the bug mentioned, the package is libfuzzy2,libfuzzy-dev. There is no
corresponding source package, so in the database the source package also is
libfuzzy2,libfuzzy-dev. The package should be split in parts and those parts
should be converted to source packages.
I could try to create a patch, but I don't know where to get the data to do
the test, so I'll leave that to someone else.
Hi,
If you could write a basic patch, I could try to test it myself.
Alternatively, you could get the BTS data using rsync:
$ rsync bugs-mirror.debian.org::
bts-spool-db[bugs-mirror.debian.org] active bug spool
bts-spool-archive [bugs-mirror.debian.org] archived bug spool
bts-spool-index [bugs-mirror.debian.org] bug index files
bts-versions[bugs-mirror.debian.org] bts package version information
But I'm not sure it's worth the trouble.
If the import is fixed, the cgi probably still won't do the right thing if the
bug is filed against different source packages (or binary packages in
different source packages). I don't know if there are examples like that.
There are, unfortunately.
Lucas
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#695543: bugs.cgi: also show removal requests
On 14/12/12 at 17:50 +0100, Ivo De Decker wrote: Control: retitle -1 bugs.cgi: show unblock and removal requests based on usertags Hi, On Mon, Dec 10, 2012 at 12:28:02AM +0100, Ivo De Decker wrote: In bugs.cgi the unblock requests are shown based on bugs against release.debian.org that match '^unblock (package)'. A number of unblock requests have a (slightly) different title. They all (should) have an unblock usertag, so the unblock requests can be found based on that usertag. That way, more unblock can be found and displayed. The attached patch (on top of the previous one) also show removal requests (from testing and unstable). (also applied) Lucas -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#693206: vavoom: Let's install the glvis utility
Am 24.12.2012 04:36, schrieb gustavo panizzo gfa: http://www.vavoom-engine.com/glvis.php says you don't need to use glbsp first. It does not say so explicitely. It merely says that it first searches for a GWA file (the one that glbsp creates) and if that does not exist it will *assume* that the WAD file already contains the GL nodes. i'm using your patch to build vavoom, where you able to use glvis? Yes, I was able to use it on i386-linux when I introduced the change to include it in the package. However, now that I tried it again today, I also received a segfault similar to the one that you posted. It works flawlessly when rebuilt without -D_FORTIFY_SOURCE=2, so maybe we should replace the offending strcpy() calls with more secure alternatives (e.g. strncpy()). - Fabian PS: I disagree with some of the changes that you recently introduced into the packaging GIT: 1) There is already a README file for glvis in utils/glvis/glvis.txt, so why introduce a new one? 2) The addition of . and / to the -iwaddir parameter was in no way limited to Boom compatibility. It is, however, strictly needed to run the freedoom wrapper in Debian, which relies on this feature in the boom wrapper. But why should it not be possible to run e.g. the doom wrapper with an Iwad given as a relative or absolute path name? 3) You introduced new wrappers e.g. for doom2. Was this in any way arranged with other Doom source ports in Debian? -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#435702: adopt
If no one else wants it, I can adopt this package. I would plan to integrate available sensible upstream mods (see git://github.com/barak/x2x branch master for a kitchen sink merge) and update the packaging. --Barak. -- Barak A. Pearlmutter ba...@cs.nuim.ie Hamilton Institute Dept Comp Sci, NUI Maynooth, Co. Kildare, Ireland http://www.bcl.hamilton.ie/~barak/ -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#678042: seabios - Please enable Xen support
Updated debian seabios package to 1.7.1 (on personal repository for now), tested with wheezy and xen-unstable and is working. Package repository: https://github.com/Fantu/pkg-seabios Changelog of my build: --- seabios (1.7.1-0.1) experimental; urgency=low * Non-maintainer upload * New upstream release 1.7.1 featuring xen support (Closes: #678042) * Removed debian/patches/fix-==-in-shell.patch (applied upstream). * Updated debian/optionrom from qemu 1.3.0 keeping debian changes. -- Fabio Fantoni fabio.fant...@heliman.it Thu, 28 Dec 2012 16:18:06 +0100 --- Could be uploaded into Debian and hence enabling qemu upstream into xen on experimental repository? -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#695423: unblock: cups/1.5.3-2.9
Control: retitle -1 unblock: cups/1.5.3-2.11.1 Le vendredi, 28 décembre 2012 14.39:36, Didier 'OdyX' Raboud a écrit : Le vendredi, 28 décembre 2012 10.27:32, Julien Cristau a écrit : Well, it's at least as large as the input string, but potentially with no space for the terminating nul character, AIUI. Good catch! I'll upload a new cups 1.5.3-2.11 with that fix. What is the good way to Depend on libc 2.13 across all our architectures ? Depends: libc-bin (= 2.13). Uploaded 1.5.3-2.11 with your requested changes, thanks again for your review! Actually, 1.5.3-2.11 was a broken upload (shame on me), I re-uploaded 1.5.3-2.11.1 without the spurious patch file. Cheers, OdyX signature.asc Description: This is a digitally signed message part.
Bug#696923: apt: Localized version of apt(8) ist not installed
Package: apt Version: 0.9.7.7 Severity: minor Tags: l10n helge@sneo:~$ dpkg -L apt | grep man | grep 8 | grep -v - /usr/share/man/pl/man8 /usr/share/man/es/man8 /usr/share/man/de/man8 /usr/share/man/pt/man8 /usr/share/man/fr/man8 /usr/share/man/ja/man8 /usr/share/man/man8 /usr/share/man/man8/apt.8.gz However, de, es, fr and pt fully translated the man pages, including apt(8). -- System Information: Debian Release: 7.0 APT prefers testing APT policy: (500, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 3.2.28sneo.02-grsec (SMP w/6 CPU cores) Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8) (ignored: LC_ALL set to de_DE.UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages apt depends on: ii debian-archive-keyring 2012.4 ii gnupg 1.4.12-6 ii libapt-pkg4.12 0.9.7.7 ii libc6 2.13-37 ii libgcc1 1:4.7.2-4 ii libstdc++6 4.7.2-4 apt recommends no packages. Versions of packages apt suggests: pn apt-doc none ii aptitude0.6.8.2-1 ii dpkg-dev1.16.9 ii python-apt 0.8.8.1 ii synaptic0.75.12 ii xz-utils5.1.1alpha+20120614-2 -- no debconf information -- Dr. Helge Kreutzmann deb...@helgefjell.de Dipl.-Phys. http://www.helgefjell.de/debian.php 64bit GNU powered gpg signed mail preferred Help keep free software libre: http://www.ffii.de/ signature.asc Description: Digital signature
Bug#696924: inkscape: uses quilt as patch system, README.source mentions dpatch
Source: inkscape Version: 0.48.3.1-1 Severity: minor -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Hi Clearly only minor. In 0.48.3.1-1 upload the patch system was switched from dpatch to quilt. debian/README.source still mentions dpatch. Should either be corrected, or maybe convert package to '3.0 (quilt)' source package format (after the wheezy release). Regards, Salvatore - -- System Information: Debian Release: 7.0 APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 2.6.32-5-amd64 (SMP w/8 CPU cores) Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968) Shell: /bin/sh linked to /bin/dash -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.12 (GNU/Linux) iQIcBAEBCgAGBQJQ3uodAAoJEHidbwV/2GP+zysP/jW0iaM2Y0wkX6LGu2Z1bMGC kjtQsbHQpBE2IKNBzr2MY7aZcAV/w8CglX7VIKMnaCCwtlRV6rNXj/e2ljXuowai 4oMz8apH1g+qFm9L5cXff5owtrt3pmG7ksEzyy5jYj2Q6wVs3+XyiKBAWn6KlUzd pKvp1kyBlmt97v+DnRF2PUV0vo0a+MX08BPwvU4PTLBPE7vdC6i1xeBxOd3RNkOL uvo6XRmy7Jw/iWN2/rhC628EhgZSDHCbV3iDq+sdwqpGUqcO2yla+vWPSJxK9LfU UVOgoOQhOY1T1dFLZ7mLZ+ULNTvNcJzbRXOebgolZvAalXECIbZfK3skoRsqzLhi WBVq18MuBbGlDMlg/aXU86VhHkMDfq7Zt5PMkIbQcsfVqDATpGT4WH9yFxSxONLv nnffRuWEblcE1Suyq/PvwvY+wH6Y3R/njEHBoq+zbvlzv3kECV1yxyw97ubq+Xzw xgcVfTq66XBQOfYCid6IX8GlNNfTVfP4JYMhB4NV76iEZQrYgokS0+W92rzw5vtW 7yyxvF8kz2T0JmZ/bSbd23G3ElPmltZHxuGRQAGVR5NRhcYJ5WlUZPtFee0tgRwz Zu26UBivZdiAmimW1noOY+wEXpu4Qh5rQx18HXGosCAOnpzS47Zg8AvcYMD/O8hE EdVMPLCSR5bkAiGgpy/3 =7386 -END PGP SIGNATURE- -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#693621: Please add _new_ NEWS entry mentioning those older virtually silenced NEWS entries
reopen 693621 retitle 693621 dovecot: important changes not duely noted in NEWS severity 693621 serious thanks The fix done so far virtually hides serious news, because the NEWS entries was silenced by a newer version getting introduced into unstable/testing before. The proper fix, I believe, is (in addition to the already corrected NEWS file name) to add an additionally NEWS entry warning that older news may have been accidentally silenced. This new NEWS entry obviously needs to be tied to the version when that entry is added, not the older version when the NEWS file was renamed (to not get exact same problem once more). Arguably severity of this is lower, but since the proper fix is quite lightweight it might be reasonable to argue the case to the release team. - 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#696925: [linux-image-3.2.0-4-amd64] please backport iguanair driver from kernel 3.8
Package: linux-image-3.2.0-4-amd64 Severity: normal --- Please enter the report below this line. --- Hi, the driver for iguanair (rc subsystem) is not working until kernel version 3.7. There had been an update which should be easy to backport. normal installation would be, rebuild/patch lirc for iguanair support install userspace driver both steps are only provided for ubuntu. with this backported driver iguanair will work with the standard lirc daemon packaged in debian, without the need of any userspace support daemons (which are only provided for ubuntu) greetings --- System information. --- Architecture: amd64 Kernel: Linux 3.6.11-iwlwifi-1-g67bf613 Debian Release: 7.0 500 unstable ftp.at.debian.org 500 testing ftp.at.debian.org 500 stable dl.google.com 500 stable apt.multi24.com 500 natty ppa.launchpad.net 500 lucid ppa.launchpad.net --- Package information. --- Package's Depends field is empty. Package's Recommends field is empty. Package's Suggests field is empty. -- Dipl.-Inf. Univ. Florian Reitmeir E-Mail: n...@multi24.com Tel: +43 512 209040 Fax: +43 512 209040 10 HP: http://net.multi24.com Leopoldstrasse 63 6020 Innsbruck / Austria
Bug#696926: dovecot update breaks with tcpwrap
Package: dovecot-core Version: 1:2.1.7-6 Severity: grave Hello, the new version 1:2.1.7-6 lacks support for tcpwrappers. Despite the mention in the NEWS file, it does not contain a /usr/lib/dovecot/tcpwrap and is obviously not compiled with tcpwrap support: dovecot --build-options Build options: ioloop=epoll notify=inotify ipv6 openssl io_block_size=8192 Mail storages: shared mdbox sdbox maildir mbox cydir imapc pop3c raw SQL driver plugins: mysql postgresql sqlite Passdb: checkpassword ldap pam passwd passwd-file shadow sql Userdb: checkpassword ldap(plugin) nss passwd prefetch passwd-file sql This breaks existing installations, as it even fails to install. Thanks for fixing it. Bye, Joerg signature.asc Description: Digital signature
Bug#433568: add vlan support
On Sat, Dec 29, 2012 at 08:34:27AM +0100, Christian PERRIER wrote: Taking over KiBi's hat, I would say there is no chance this makes it to wheezy. And taking mine, too, with several addition to localization bits. The debconf templates need minor edits to compleltely fit with the writing style we're using elsewhere...and they add 8 stringsand we have 56 complete translations (more than we *ever* had). I'd say that this is something that must be preseeded and if anything it would show errors in English. So I'm not too concerned about that. But if we agree that it is useful to show netcfg/use_vlan in jessie in expert mode, we can do that too. Kind regards Philipp Kern signature.asc Description: Digital signature
Bug#589304: ITA: jabberd2 -- Jabber instant messenger server
Hi, I cleaned up the code a little bit. Solved a bunch of lintian warnings. I tried to create a git repository on git.debian.org pkg-jabberd2 in /git. But didnt had the permission for it. Please check the changes and let me know if something need to be changed. Greetings, Willem On Wed, 2012-12-26 at 20:50 -0200, Thadeu Lima de Souza Cascardo wrote: On Wed, Dec 26, 2012 at 12:53:53AM +0100, Willem van den Akker wrote: Hi, I havent received any response about my ITA message for Jabberd2 (see below). It seems the current maintainer is MIA. Is it possible someone of the pkg-xmpp-devel group can reply? I would like to adopt it, but must get a chance to get so ;) Greetings, Willem Hi, Willem. Jorge Salamero used to be the main maintainer of jabberd2. I accepted to be a comaintainer in the xmpp team, which has seen most work coming from Marcelo Metal on some Javascript XMPP packages. I have no problems with you either working with us on a common repository as a team to maintain jabberd2, or adopting it entirely. Of course, we'd rather see it as a community maintainership, using the xmpp infrastructure as it is already setup. Do you have a git repository with your changes? Regards. Thadeu Cascardo. On Thu, 2012-12-20 at 23:28 +0100, Willem van den Akker wrote: Package: wnpp Severity: normal X-Debbugs-CC: debian-de...@lists.debian.org Hi, I am interested in adopting jabberd2. Now a new version of udns is uploaded into unstable, I hope we can update jabberd2 also. I have placed a new version online: https://mentors.debian.net/package/jabberd2 I hope you can check if it is valid and upload if it is. If not, I will correct it ;) Greetings, Willem vdAkker signature.asc Description: This is a digitally signed message part
Bug#696820: Error: open(/var/mail/USER) failed: Permission denied
Quoting Jonas Smedegaard (2012-12-29 13:25:59) Quoting Jaldhar H. Vyas (2012-12-29 02:52:15) On Sat, 29 Dec 2012, Jonas Smedegaard wrote: Latest package release changed /etc/dovecot/conf.d/10-mail.conf to hardcode mail_location to use mbox and /var/mail as mailspool. Upstream default of leaving that variable undefined is to try both mbox and Maildir. But I can't do that. See #693114. So I had to pick something as a default and mbox in /var/mail is the lowest common denominator. Arrgh - I was hit by bug#693621 (NEWS file not registered). ...but something else must be going on as well: That change warned about in that accidentally silenced NEWS entry is way old, and what I did yesterday on multiple machines was update from 1:2.1.7-2. Seems to me that if I chose in earlier updates to keep my settings (as I suspect many would do, since that worked just fine!) the update process should have warned me about changing that file - it didn't! So regardless of that NEWS bug (which I have now reopened) I believe something is wrong here too. - 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#696927: unblock: ferm/2.1-5
Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: unblock
Please unblock package ferm
Unfortunatly the fix for the domain handling in -4 wasn't complete and
resulted in #696130 which hitted several users. I prepared a fix
for the (picked from upstreams git).
The debdiff is fairly small:
diff --git a/debian/changelog b/debian/changelog
index d5ba908..0d97810 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,3 +1,11 @@
+ferm (2.1-5) unstable; urgency=low
+
+ * [f4e216a] Backport a fix from 2.1.2 which fixes a regression from the
+ domain (ip ip6) fix introduced in 2.1.1 (backported to 2.1-4)
+ (Closes: #696130)
+
+ -- Alexander Wirt formo...@debian.org Sat, 29 Dec 2012 11:30:56 +0100
+
ferm (2.1-4) unstable; urgency=low
* [4ede608] Backport a patch that fixes a regression in functions containing
diff --git a/src/ferm b/src/ferm
index 2214969..a97fae1 100755
--- a/src/ferm
+++ b/src/ferm
@@ -2044,6 +2044,7 @@ sub enter($$) {
my $old_line = $script-{line};
my $old_handle = $script-{handle};
my $old_tokens = $script-{tokens};
+my $old_base_level = $script-{base_level};
unshift @$old_tokens, make_line_token($script-{line});
delete $script-{handle};
@@ -2051,10 +2052,12 @@ sub enter($$) {
my %inner;
new_level(%inner, \%rule);
set_domain(%inner, $domain) or next;
+$script-{base_level} = 0;
$script-{tokens} = [ @$tokens ];
enter(0, \%inner);
}
+$script-{base_level} = $old_base_level;
$script-{tokens} = $old_tokens;
$script-{handle} = $old_handle;
$script-{line} = $old_line;
Thanks in advance
Alex
unblock ferm/2.1-5
-- System Information:
Debian Release: 7.0
APT prefers unstable
APT policy: (500, 'unstable'), (1, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 3.8.0-rc1+ (SMP w/4 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#678042: seabios - Please enable Xen support
29.12.2012 16:59, Fabio Fantoni wrote: Updated debian seabios package to 1.7.1 (on personal repository for now), tested with wheezy and xen-unstable and is working. Package repository: https://github.com/Fantu/pkg-seabios Hmm. This repository contains just 2 commits: initial import with seabios 1.7.1 and Updated debian/optionrom from qemu 1.3.0 keeping debian changes This is definitely not the way how it can be imported into debian repository, all changes needs to be re-done again -- unless there's a way which I don't see. Changelog of my build: --- seabios (1.7.1-0.1) experimental; urgency=low * Non-maintainer upload * New upstream release 1.7.1 featuring xen support (Closes: #678042) 1.7.1 needs a few more fixes on top, which are unrelated to xen but should be present for qemu. It does not mean it isn't a good idea to update it now anyway. * Removed debian/patches/fix-==-in-shell.patch (applied upstream). * Updated debian/optionrom from qemu 1.3.0 keeping debian changes. Which debian changes is that? Could be uploaded into Debian and hence enabling qemu upstream into xen on experimental repository? Yes, we basically forgot about this stuff already, it's a good idea to ping us so we'll start doing things again. I'm looking at it now. 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#685251: [Openstack-devel] Fixing Debian bug #685251 for the ryu plugin in Openstack
Hi Thomas (and Julien) Thanks for the ckeck. See answers below. On Sat, Dec 29, 2012 at 06:38:20PM +0800, Thomas Goirand wrote: On 12/29/2012 04:57 PM, Ola Lundqvist wrote: Hi Julien I have now finally got enough time to actually do this backport. I have attached the proposal as a diff file. If you accept this change I will upload it to testing-proposed-updates. I do not know if this kind of change requires work from ftp-masters as it actually removes binary packages. This time the change is minimal and do not include anything from 2012.1-6. Thanks for your consideration. // Ola Hi, There's quite a few problems in your diff file. The next 3 points would be what I believe the release team would answer, the last point is specific to the Openstack packaging team. * Could you please send again the debdiff, but *WITHOUT* your *~ backup files? Probably you should have carefully read it before replying like this to the release team who is already overloaded with Debian tasks. That's the kind of joke they don't really like... Doh! I thought I did that before generating the diff. Sorry for that. New file attached. * I don't think there's the need to use testing-proposed-updates. Uploading to SID will be just fine, as anyway, we haven't uploaded anything newer in SID which would pose a problem, and that we use Experimental for Folsom. (in other words: nothing prevents uploading to SID, and when we upload there it's in the hope it migrates to testing) No that won't work because the changes in -6 should remain. It is a good change. And no I do not want to first upload a -7 version and than a new -8 with the changes in -6 because then I have to have a very complicated replaces rules in the control file which we really should avoid. * There is already a version -6 in SID. So you should really upload 2012.1-7, not 2012.1-5wheezy1, which is the scheme for security uploads in Debian Stable. Same answer as above. I have followed the instructions in http://www.debian.org/doc/manuals/developers-reference/pkgs.html chapter 5.13.3. Version numbers are usually selected by adding the codename of the testing distribution and a running number, like 1.2squeeze1 for the first upload through testing-proposed-updates of package version 1.2. This is just as valid for testing uploads as for stable uploads. * Our Git already contains entries for -6 and -7. Please use that, modifying the candidate version -7, and do not get out of sync with our Git please, otherwise it's going to be a nightmare! The -7 version is what I have used to backport from. I have taken your changes and re-done them for testing only. I do understand that we should have unstable development in git. The reason I have made a branch here is to have this fix for testing only. Same reason as above. I can make a branch in git as well if you want. I do not see the point in that though. I'll upload -7 at the same time. I mistakenly thought it was already uploaded by you. Sorry for that. Also, this issue has been pending for 6 months! I do appreciate that you finally decide to work on it, even that late. But I continue to refuse to take the responsibility for it. The main mistake, IMO, was to leave the issue as-is, doing nothing to fix it. So you and Loic should really take the responsibility for the upload, and make sure it's in a correct shape *in time* for the release. I surely would feel bad if Quantum had to be removed from Wheezy. Please don't leave this pending again. I do not want to start a flamewar but I do want to explain what has happend. Please take what I write below just as facts. I'm sorry for this issue being pending. First of all it is 3.5 months (not 6), secondly I have asked about your opintion on this matter without response and that explains more than 2 months. 18 Aug: Bug reported 24 Aug: Explained the situation and asked about your opinion. 7 Oct: Asked again as a reminder. 01 Nov: You responded. 01 Nov: I responded that it was not fixed in -6. ... 09 Nov: You provide the diff. ... today: I provide the backport. But yes it has been pending and I'm sorry for that. Life have been a bit busy lately though. // Ola Cheers, Thomas -- --- 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 / --- -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#685251: [Openstack-devel] Fixing Debian bug #685251 for the ryu plugin in Openstack
Sorry. Forgot to attach the new diff. // Ola On Sat, Dec 29, 2012 at 02:22:01PM +0100, Ola Lundqvist wrote: Hi Thomas (and Julien) Thanks for the ckeck. See answers below. On Sat, Dec 29, 2012 at 06:38:20PM +0800, Thomas Goirand wrote: On 12/29/2012 04:57 PM, Ola Lundqvist wrote: Hi Julien I have now finally got enough time to actually do this backport. I have attached the proposal as a diff file. If you accept this change I will upload it to testing-proposed-updates. I do not know if this kind of change requires work from ftp-masters as it actually removes binary packages. This time the change is minimal and do not include anything from 2012.1-6. Thanks for your consideration. // Ola Hi, There's quite a few problems in your diff file. The next 3 points would be what I believe the release team would answer, the last point is specific to the Openstack packaging team. * Could you please send again the debdiff, but *WITHOUT* your *~ backup files? Probably you should have carefully read it before replying like this to the release team who is already overloaded with Debian tasks. That's the kind of joke they don't really like... Doh! I thought I did that before generating the diff. Sorry for that. New file attached. * I don't think there's the need to use testing-proposed-updates. Uploading to SID will be just fine, as anyway, we haven't uploaded anything newer in SID which would pose a problem, and that we use Experimental for Folsom. (in other words: nothing prevents uploading to SID, and when we upload there it's in the hope it migrates to testing) No that won't work because the changes in -6 should remain. It is a good change. And no I do not want to first upload a -7 version and than a new -8 with the changes in -6 because then I have to have a very complicated replaces rules in the control file which we really should avoid. * There is already a version -6 in SID. So you should really upload 2012.1-7, not 2012.1-5wheezy1, which is the scheme for security uploads in Debian Stable. Same answer as above. I have followed the instructions in http://www.debian.org/doc/manuals/developers-reference/pkgs.html chapter 5.13.3. Version numbers are usually selected by adding the codename of the testing distribution and a running number, like 1.2squeeze1 for the first upload through testing-proposed-updates of package version 1.2. This is just as valid for testing uploads as for stable uploads. * Our Git already contains entries for -6 and -7. Please use that, modifying the candidate version -7, and do not get out of sync with our Git please, otherwise it's going to be a nightmare! The -7 version is what I have used to backport from. I have taken your changes and re-done them for testing only. I do understand that we should have unstable development in git. The reason I have made a branch here is to have this fix for testing only. Same reason as above. I can make a branch in git as well if you want. I do not see the point in that though. I'll upload -7 at the same time. I mistakenly thought it was already uploaded by you. Sorry for that. Also, this issue has been pending for 6 months! I do appreciate that you finally decide to work on it, even that late. But I continue to refuse to take the responsibility for it. The main mistake, IMO, was to leave the issue as-is, doing nothing to fix it. So you and Loic should really take the responsibility for the upload, and make sure it's in a correct shape *in time* for the release. I surely would feel bad if Quantum had to be removed from Wheezy. Please don't leave this pending again. I do not want to start a flamewar but I do want to explain what has happend. Please take what I write below just as facts. I'm sorry for this issue being pending. First of all it is 3.5 months (not 6), secondly I have asked about your opintion on this matter without response and that explains more than 2 months. 18 Aug: Bug reported 24 Aug: Explained the situation and asked about your opinion. 7 Oct: Asked again as a reminder. 01 Nov: You responded. 01 Nov: I responded that it was not fixed in -6. ... 09 Nov: You provide the diff. ... today: I provide the backport. But yes it has been pending and I'm sorry for that. Life have been a bit busy lately though. // Ola Cheers, Thomas -- --- 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 / --- -- --- Inguza Technology AB --- MSc in Information Technology / o...@inguza.com
Bug#688738: Unfixed RC bug and unable to install updated package
There is no link to a VCS for the docbookwiki packaging in the PTS, but
from a debdiff, the changes to the postinst appear to be the problem:
-dpkg-maintscript-helper mv_conffile /etc/apache2/conf.d/docbookwiki
/etc/apache2/conf.available/docbookwiki 0.9.2-2 docbookwiki -- $@
+if [ -d /usr/share/docbookwiki/content/SVN/repository ]
+then
+mv /usr/share/docbookwiki/content/SVN/repository /var/lib/docbookwiki
+else
+ /usr/bin/svnadmin create /var/lib/docbookwiki
+ /usr/bin/svnadmin load --quiet /var/lib/docbookwiki
/usr/share/docbookwiki/content/SVN/svn.dump
This is a waste of time on new installations because of the later
cleanup script and only creates a repository, not the working copy that
the later scripts actually need:
svn: E155007: '/var/lib/docbookwiki/docbookwiki_guide_en.xml' is not a working
copy
svn: E155007: '/var/lib/docbookwiki/media' is not a working copy
svn: E155007: '/var/lib/docbookwiki/media/docbookwiki_guide' is not a working
copy
svn: E155007: '/var/lib/docbookwiki/media/docbookwiki_guide' is not a working
copy
svn is correct here, /var/lib/docbookwiki/ is not a working copy, it is
the repository itself - an svn checkout needs to be made somewhere in /var/lib/
+fi
+ln -s /var/lib/docbookwiki /usr/share/docbookwiki/content/SVN/repository
This should be conditional on /usr/share/docbookwiki/content/SVN/repository not
already existing.
The init.sh script called later does the svnadmin call wrongly later:
### if no repository argument is given, create a local repository
if [ $repository = ]
then
# create it if it does not exist
if [ ! -d 'repository' ]
then
svnadmin create $(pwd)/repository #create
fi
repository=file://$(pwd)/repository
fi
+dpkg-maintscript-helper mv_conffile /etc/apache2/conf.d/docbookwiki
/etc/apache2/conf-available/docbookwiki 0.9.2-2 docbookwiki -- $@
+if [ -e /usr/share/apache2/apache2-maintscript-helper ] ; then
+. /usr/share/apache2/apache2-maintscript-helper
+apache2_invoke enconf docbookwiki
+elif dpkg-query -f '${Version}' -W 'apache2.2-common' /dev/null 21 ;
then
+# if the configuration uses IfVersion uncomment the next line
+# a2enmod -q version
+[ -d /etc/apache2/conf.d/ ] [ ! -L
/etc/apache2/conf.d/docbookwiki.conf ] ln -s
../conf-available/docbookwiki.conf /etc/apache2/conf.d/docbookwiki.conf
+fi
if [ ! -d /usr/share/docbookwiki/content/books ]; then
# This is a new installation
db_get docbookwiki/setup_password
su -c install/set_su_passwd.sh $RET ; \
content/clean.sh all ; \
content/SVN/init.sh ; \
0: Those calls should be put into a single separate script, packaged in the
debian/ directory and installed into /var/lib/docbookwiki/init/ or similar so
that set -e can be used (and set -x during debugging).
1: the init.sh call should use /var/lib/docbookwiki
2: Due to the symlink, clean.sh does rm -rf /var/lib/docbookwiki
The bigger problem is that the package still modified shipped files,
irrespective of what happens with the svndump because the init scripts
are still called from /usr/share/ and write files to /usr/share (like
svn_cfg.txt):
root@sylvester:/home/docbookwiki-0.9.2# dpkg -S
/usr/share/docbookwiki/content/SVN/svn_cfg.txt
dpkg-query: no path found matching pattern
/usr/share/docbookwiki/content/SVN/svn_cfg.txt
That file and all the files like it *must* be in /var/lib/docbookwiki
to be able to close this bug.
This bug isn't about simply putting a directory under /var and then
operating the rest of the package on /usr/share via a symlink. This
needs to be fixed properly by getting the upstream package to use /var
whenever it is dealing with modifiable / modified data during all
stages: installation, configuration, operation, upgrade and purge.
This would include moving /usr/share/docbookwiki/content/books
into /var/lib/ as well as this is generated data.
docbookwiki must treat /usr/share as read-only during operation *and
setup* with only dpkg putting files or directories beneath that
mountpoint. Essentially, once dpkg -X has completed, I see no reason
why a wiki engine should expect to have write permissions on /usr - those
writes go into /var/.
There are also upstream problems with the init.sh script:
### create the directories 'trunk/media/' in the svn repository
svn mkdir $repository/trunk/ -m ''
svn mkdir $repository/trunk/media/ -m ''
svn mkdir /var/lib/docbookwiki//trunk/ -m ''
svn: E205009: Local, non-commit operations do not take a log message or
revision properties
This prevents the init.sh from using set -e and therefore prevents
other errors from being caught elsewhere.
Worse, the mkdir call is made *before* the export:
### checkout trunk to svn_dir
rm -rf $svn_dir
echo Checking out '$repository/trunk/' in '$svn_dir'
svn checkout $repository/trunk/ $svn_dir
Sorry, but at this point I gave up. docbookwiki would appear to be in a
very bad
Bug#696926: dovecot update breaks with tcpwrap
Control: severity -1 wishlist Control: retitle -1 dovecot: want tcp wrapper support back On Sat, Dec 29, 2012 at 14:06:40 +0100, Joerg Dorchain wrote: Package: dovecot-core Version: 1:2.1.7-6 Severity: grave Hello, the new version 1:2.1.7-6 lacks support for tcpwrappers. Despite the mention in the NEWS file, it does not contain a /usr/lib/dovecot/tcpwrap and is obviously not compiled with tcpwrap support: dovecot --build-options Build options: ioloop=epoll notify=inotify ipv6 openssl io_block_size=8192 Mail storages: shared mdbox sdbox maildir mbox cydir imapc pop3c raw SQL driver plugins: mysql postgresql sqlite Passdb: checkpassword ldap pam passwd passwd-file shadow sql Userdb: checkpassword ldap(plugin) nss passwd prefetch passwd-file sql This breaks existing installations, as it even fails to install. This is on purpose. Jaldhar, I guess the mention of tcp wrapper support in NEWS.Debian should go away though. Cheers, Julien signature.asc Description: Digital signature
Bug#696928: Please provide IPv6 MX for mail connectivity
Package: bugs.debian.org Severity: wishlist Hello, as I am owning an IPv6-only sytem, I have a vital interest that I am able to submit bug report also from that system. Today (29.12.2012) there is no MX with an record available. Thank you for setting up one. Bye, Joerg -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#696929: docbook-xsl-ns 1.78.0 has been released
Package: docbook-xsl-ns Version: 1.76.1+dfsg-1 Severity: normal Dear Maintainer, Version 1.78.0 of the Docbook5 XSL stylesheets (already two minor version numbers higher than what Debian packages at the time of writing) has been released: http://sourceforge.net/projects/docbook/files/docbook-xsl-ns/ Please make this available to Debian users. -- System Information: Debian Release: 7.0 APT prefers unstable APT policy: (500, 'unstable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.6.6 (SMP w/4 CPU cores) Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages docbook-xsl-ns depends on: ii xml-core 0.13+nmu2 Versions of packages docbook-xsl-ns recommends: ii docbook5-xml 5.0-2 Versions of packages docbook-xsl-ns suggests: pn dbtoepubnone ii docbook-xsl-doc-html [docbook-xsl-doc] 1.76.1-1 ii docbook-xsl-saxon 1.00.dfsg.1-5 ii fop 1:1.0.dfsg2-6 ii libsaxon-java 1:6.5.5-8 ii libxalan2-java 2.7.1-7 pn libxslthl-java none ii xalan 1.10-6 -- no debconf information -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#696930: RM: docbookwiki -- RoQA; Broken fix for RC bug makes package uninstallable, modifies files in /usr in postinst
Package: ftp.debian.org Severity: normal I've had a look into the problems behind #688738 and the broken fix for #688738 which causes #694138. As outlined in #688738, the original RC bug (shipping and committing to a subversion repository in /usr/share) was a specific instance of the docbookwiki package writing to /usr/share during installation. The fix for #688738 does not fix the problem (it merely puts the modified files in /usr/share under a symlink pointing to /var/ and then allows other files in /usr/share to still be modified). The broken fix also directly causes the second RC bug: #694138. I've spotted upstream problems in the management of the internal SVN repository as well as the problems introduced for the fix. There has been no comment on the broken fix for #688738, nor on #694138 and I do not see a sane route to fixing the package properly without rewriting large sections of management code in the package, both upstream and Debian. Please remove docbookwiki from Debian. thanks. -- Neil Williams = codeh...@debian.org -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#696918: unblock: freetype/2.4.9-1.1
Control: tags -1 + confirmed d-i On Sat, 2012-12-29 at 12:51 +0100, Salvatore Bonaccorso wrote: Please unblock package freetype (but we can wait first the two day period to have the changes in unstable witouh an already granted unblock). The upload fixes three CVEs for freetype, see #696691: CVE-2012-5668: NULL Pointer Dereference in bdf_free_font. CVE-2012-5669: Out-of-bounds read in _bdf_parse_glyphs. CVE-2012-5670: Out-of-bounds write in _bdf_parse_glyphs. The package also provides a udeb, so this needs an explicit ACK by Cyril? Yep. Unblocked pending the ack; thanks. 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#685726: linux-image-3.2.0-3-amd64: return error when trying to format image file (mkfs -t ext4 file.img)
On Wed, 2012-12-26 at 01:27 +0400, Nikita Gubenko wrote: Guys, any update on this bug? Can reproduce on 3.2.0-4-amd64 with vhd image. We're still waiting for someone to report results after applying the patches from http://bugs.debian.org/685726#42. Ben. -- Ben Hutchings It is easier to change the specification to fit the program than vice versa. signature.asc Description: This is a digitally signed message part
Bug#681016: [release.debian.org] unblock: dotlrn/2.5.0+dfsg-8
On Sun, 2012-12-16 at 19:46 +0100, Hector Romojaro wrote: El dom, 09-12-2012 a las 16:52 +, Adam D. Barratt escribió: Apologies for the long delay in getting back to you about this; it managed to slip under the radar somehow. Please go ahead with the upload; thanks. It is Ok, thanks for taking a look at this and accepting the changes. I have already asked my sponsor Frankie for upload, and I will apply those changes to the openacs package as well, and also to both openacs and dotlrn packages in unstable. Thanks. Is there an ETA for that? 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#692791: #692791: CVE-2012-5519 Security update towards Squeeze ?
Le vendredi, 28 décembre 2012 19.39:33, Moritz Mühlenhoff a écrit : On Fri, Dec 28, 2012 at 06:40:29PM +0100, Didier 'OdyX' Raboud wrote: Le jeudi, 27 décembre 2012 20.43:12, Moritz Mühlenhoff a écrit : AFAICS can there haven't been any regressions, can we should go ahead with the update now. EPARSE I meant: No regressions in sid - We can proceed with stable Uploaded to unembargoed as 1.4.4-7+squeeze2. The code is on http://anonscm.debian.org/gitweb/?p=pkg- cups/cups.git;a=shortlog;h=refs/heads/master-squeeze Cheers, OdyX signature.asc Description: This is a digitally signed message part.
Bug#693263: qcontrol: wheezy version of qcontrol does not support --direct
Package: qcontrol Followup-For: Bug #693263 Dear Maintainer, the qcontrol initramfs script /usr/share/initramfs-tools/scripts/init-bottom/qcontrol tries to execute /sbin/qcontrol --direct watchdog off but the wheezy version (0.4.2-7+wheezy1) does not know about the --direct switch, so the script is pretty useless and the system reboots after 5 minutes. Installing the sid package (0.4.2+svn-r40-3) helped. HW is a QNAP TS-419 II. Hanno -- System Information: Debian Release: 7.0 APT prefers testing-updates APT policy: (500, 'testing-updates'), (500, 'testing') Architecture: armel (armv5tel) Kernel: Linux 3.2.0-4-kirkwood Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968) Shell: /bin/sh linked to /bin/dash Versions of packages qcontrol depends on: ii libc62.13-37 ii liblua5.1-0 5.1.5-4 ii udev 175-7 qcontrol recommends no packages. qcontrol 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#696662: rt2800pci_mcu_status no hardware response due to radio enabled to early
Control: severity -1 normal Control: tag -1 patch I'm downgrading this because the error seems to be easily recoverable. The upstream commits that should fix this are: commit 09a3311c1a061bda809ff78c512855f3b71dcd6b Author: Jakub Kicinski kubak...@wp.pl Date: Wed Feb 22 21:58:57 2012 +0100 rt2800: Add documentation on MCU requests commit e8b461c37717d6b5c071c4924845884a86c20752 Author: Jakub Kicinski kubak...@wp.pl Date: Wed Feb 22 21:58:58 2012 +0100 rt2800pci: Fix 'Error - MCU request failed' during initialization However there have been several other changes to hardware initialisation and it may be necessary to pick more of them to avoid a regression. I'm not intending to work on this. Ben. -- Ben Hutchings It is easier to change the specification to fit the program than vice versa. signature.asc Description: This is a digitally signed message part
Bug#696931: calendarserver: PostgreSQL connection DB bootstrapping
Package: calendarserver Version: 3.2+dfsg-5 Severity: normal Dear Maintainer, I've been experiencing with caldavd on a local PostgreSQL database, and found several issues that can be easily fixed or circumvented. I'm not really able to decide how much of that really should be fixed upstream. It can be for sure fixed by packaging or documentation. (postgresql-9.1, version 9.1.7-1 from wheezy, but that should really not matter) 1) Peer connection caldavd.plist extract: !-- Database connection -- keyUseDatabase/key true/ keyDBType/key stringpostgres/string keyDSN/key string:caldavd:caldavd:::/string It seems that the initial DB connection gets done while system user is still 'root'. Subsequent ones are done with 'caldavd'. Found a reference to it in upstream mailing list: http://lists.macosforge.org/pipermail/calendarserver-dev/2012-November/001564.html This can be circumvented by letting root perform peer connections as role 'caldavd' through pg_ident.conf 2) Database bootstrap The parameters of /usr/bin/calendarserver_bootstrap_database are entirely hardcoded to values that are wrong in the Debian setting Actual source is in /usr/lib/python2.7/dist-packages/calendarserver/tools/bootstrapdatabase.py Extract: CONNECTNAME = _postgres USERNAME = caldav DATABASENAME = caldav SCHEMAFILE= /usr/share/caldavd/lib/python/txdav/common/datastore/sql_schema/current.sql What this script does is simply create role database, then load of the SCHEMAFILE SQL source file. On a Debian system, the default PostgreSQL superuser is 'postgres', and that file lies at /usr/lib/python2.7/dist-packages/txdav/common/datastore/sql_schema/current.sql With the Debian way of installing python packages means that it should not be hardcoded to that location either. I've been able to bootstrap my database by loading that file manually, calendarserver seems to work fine, but the bootstrap script seems to also be able to perform updates, so that it really should be fixed in some way. Thank you for your attention -- System Information: Debian Release: 7.0 APT prefers unstable APT policy: (500, 'unstable'), (500, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 3.2.0-4-amd64 (SMP w/4 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages calendarserver depends on: ii adduser3.113+nmu3 ii libc6 2.13-37 ii lsb-base 4.1+Debian9 ii memcached 1.4.13-0.1 ii python 2.7.3-3 ii python-dateutil1.5+dfsg-0.1 ii python-kerberos1.1+svn4895-1+b2 ii python-openssl 0.13-2 ii python-plist 1.8-1 ii python-pycalendar 2.0~svn188-1 ii python-pygresql1:4.0-3 ii python-pysqlite2 2.6.3-3 ii python-sqlparse0.1.4-1 ii python-twisted-conch 1:12.0.0-1 ii python-twisted-core12.0.0-1 ii python-twisted-mail12.0.0-1 ii python-twisted-web 12.0.0-1 ii python-twisted-words 12.0.0-1 ii python-xattr 0.6.4-2 ii python-zope.interface 3.6.1-3 ii ssl-cert 1.0.32 Versions of packages calendarserver recommends: ii python-ldap 2.4.10-1 ii python-pam 0.4.2-13 calendarserver suggests no packages. -- Configuration Files: /etc/caldavd/accounts.xml changed: ?xml version=1.0 encoding=utf-8? !-- Copyright (c) 2006-2010 Apple Inc. All rights reserved. Licensed under the Apache License, Version 2.0 (the License); you may not use this file except in compliance with the License. You may obtain a copy of the License at http://www.apache.org/licenses/LICENSE-2.0 Unless required by applicable law or agreed to in writing, software distributed under the License is distributed on an AS IS BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. See the License for the specific language governing permissions and limitations under the License. -- !DOCTYPE accounts SYSTEM accounts.dtd accounts realm=Test Realm user uidadmin/uid guidADMIN/guid passwordadmin/password nameSuper User/name /user user uidtest/uid passwordtest/password nameTest User/name /user group uidusers/uid passwordusers/password nameUsers Group/name members member type=userstest/member /members /group location uidmercury/uid passwordmercury/password nameMecury Conference Room, Building 1, 2nd Floor/name /location /accounts /etc/caldavd/caldavd.plist changed: ?xml version=1.0 encoding=UTF-8? !-- Copyright (c) 2006-2011 Apple Inc. All rights reserved. Licensed under the Apache License, Version 2.0 (the License); you may not use this file except in compliance with the License. You may obtain a copy of the License at http://www.apache.org/licenses/LICENSE-2.0 Unless required by applicable law or agreed to in writing, software distributed under the
Bug#693263: qcontrol: wheezy version of qcontrol does not support --direct
On Sat, 2012-12-29 at 14:36 +0100, Hanno Hecker wrote: the qcontrol initramfs script /usr/share/initramfs-tools/scripts/init-bottom/qcontrol tries to execute /sbin/qcontrol --direct watchdog off but the wheezy version (0.4.2-7+wheezy1) does not know about the --direct switch, so the script is pretty useless and the system reboots after 5 minutes. Thanks for the report, I don't have any hardware with a watchdog which has Debian installed just yet so I missed this during the backport. Please could you try reinstalling 0.4.2-7+wheezy1 and replacing the script with the attached version which uses the qcommand wrapper instead of the current thing. Then run update-initramfs -u (I think this runs flash-kernel automatically, if not you may need to do it by hand) and reboot. qcommand is probably right thing to use even in the Sid version, although qcontrol --direct happens to work too. I also made it use qcommand -t to check for supported hardware. Ian. -- Ian Campbell An ounce of hypocrisy is worth a pound of ambition. -- Michael Korda init-bottom Description: application/shellscript signature.asc Description: This is a digitally signed message part
Bug#248397: Subject: Re: GRUB 2 RFH
Hello Colin, Thanks. Will start looking in to the bugs. Started looking at the grub webpage. Will try out a few bugs fixes. http://packages.qa.debian.org/g/grub.html A wiki would be really handy on how to setup. http://en.wikipedia.org/wiki/GNU_GRUB -- Regards Martin Naughton On Fri, Dec 28, 2012 at 7:10 AM, Colin Watson cjwat...@debian.org wrote: On Wed, Dec 12, 2012 at 11:53:54AM +, Martin Naughton wrote: Do you still need help. Me and another guy are interested in helping. Can you indicate if you still need help. We are not DD yet but we are learning. We can help with the testing of grub and fix bugs while you can develop the application. If not help is needed can the ticket be closed? GRUB package maintenance in Debian still certainly needs help; while we've generally managed to keep one primary maintainer (I came along well after this RFH was initially filed, and have been the most active on the team for the last couple of years), Debian really ought to be able to manage a team with a higher bus factor for its principal boot loader. We suffered from that this summer when I had some temporary motivation problems; if another developer had been sufficiently active and able to step in it's possible that we'd be shipping wheezy with GRUB 2.00 rather than 1.99. You can certainly help out with testing and fixing individual bugs without having to ask in advance (as long as you don't actually close bugs without asking) - just mail the BTS as appropriate. I do think we need more DDs involved, though. Jonathan is right that we need some kind of wiki documentation here. I'll see if I can carve out some time soon to write up a skeleton of such a thing ... -- Colin Watson [cjwat...@debian.org]
Bug#693485: Re[2]: Bug#693485: keyboard-configuration: XKBLAYOUT, XKBOPTIONS values manually set in /etc/default/keyboard lost on upgrade
On Fri, Dec 28, 2012 at 01:32:50AM +0400, Bob Bib wrote: OK, but the output is a little bit too verbose (see it attached). Good. I think this will be an exciting reading. Anton Zinoviev -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#693263: qcontrol: wheezy version of qcontrol does not support --direct
* Ian Campbell i...@hellion.org.uk [2012-12-29 14:20]: qcommand is probably right thing to use even in the Sid version, I believe qcommand only exists in the udeb, so this won't work. Might be better to backport --direct instead. -- Martin Michlmayr http://www.cyrius.com/ -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#692249: sata boot+grub unknown filesystem without boot=on
Control: tags -1 + moreinfo unreproducible 04.11.2012 08:49, Gianluigi Tiesi wrote: Package: qemu-kvm Severity: minor Hi, I've noticed my kvm warns about using boot=on so I've decided to find some documentation, as I found boot=on enables extboot option rom removed upstream because seabios can boot directly from sata. References in #652447, perhaps I was able to boot as linux vm from a scsi disk using latest seabios code without using lsi proprietary rom (maybe they implemented scsi boot). if I run: vm -m 1024 -snapshot -device ahci,id=ahci0,bus=pci.0,addr=0x5 -drive file=/dev/sda,if=none,id=drive-sata0-0-0,format=raw,boot=on -device ide-hd,bus=ahci0.0,drive=drive-sata0-0-0,id=sata0-0-0 This is not scsi, this is ahci, FWIW. kvm complains about deprecated boot=on, grub loads and it can boot but if I run: kvm -m 1024 -snapshot -device ahci,id=ahci0,bus=pci.0,addr=0x5 -drive file=/dev/sda,if=none,id=drive-sata0-0-0,format=raw -device ide-hd,bus=ahci0.0,drive=drive-sata0-0-0,id=sata0-0-0 grub loads but it's unable to identify the filesystem Well. Which version of seabios is that? I'm asking because this does not boot at all with current seabios+qemu-kvm from wheezy: guest bios does not find any boot device. If in your case guest bios finds the boot device and loads grub, it must be some other version of either qemu-kvm or seabios. But at any rate, you forgot one more parameter: it is bootindex. Try this: kvm -m 1024 -snapshot \ -device ahci,id=ahci0,bus=pci.0,addr=0x5 \ -drive file=/dev/sda,if=none,id=drive-sata0-0-0,format=raw \ -device ide-hd,bus=ahci0.0,drive=drive-sata0-0-0,id=sata0-0-0,bootindex=0 This works here just fine. Does it answer your question/issue? sda4 is ext4, and I'm trying to boot my windows from my linux maybe seabios it's unable to correcly map whole drive? Nope, it is completely unrelated. For any virtual disk drive given by qemu to the guest - no matter at all which it is on the host - the guest (including the bios) sees it just like a regular disk drive. It is up to qemu to make the host representation of it completely transparent, and qemu does a good job in there. 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#693263: qcontrol: wheezy version of qcontrol does not support --direct
On Sat, 2012-12-29 at 14:48 +, Martin Michlmayr wrote: * Ian Campbell i...@hellion.org.uk [2012-12-29 14:20]: qcommand is probably right thing to use even in the Sid version, I believe qcommand only exists in the udeb, so this won't work. Might be better to backport --direct instead. oops, I checked but I looked into the installed initrd instead of a proper one. I was a bit surprised to see it there but I should have double checked! Backporting --direct is a lot of code. For wheezy I'd rather add qcommand, or something equivalent, to the initramfs hooks. Ian. -- Ian Campbell So far we've managed to avoid turning Perl into APL. :-) -- Larry Wall in 199702251904.laa28...@wall.org signature.asc Description: This is a digitally signed message part
Bug#693839: debian-installer: kernel install fails on armel buffalo linkstation pro, missing uboot-mkimage
Quoting Cyril Brulebois (k...@debian.org): Hi, and thanks for your report. u-boot-tools is only in “Suggests” for flash-kernel, while your situation suggests it might be better to have it in “Recommends”. What do others think? Well, I even moved it to Depends in my commit. I'm not sure it is a good idea to rely on Recommends being installed if the mkimage program is required in some situations. I'm ready to upload flash-kernel with that fix. signature.asc Description: Digital signature
Bug#695131: Even important, this bug is not release critical
severity 695131 important thanks As much as I understand Aoki-san's wish to get this bug fixed, I don't think it fits the definition of a release critical bug. Even more because the purpose of g-c-c is not only configuring USB printers. So, a failure in this feature doesn't make the package completely unsuitable. TO understand this, just think about this : would you be OK if the said package is removed from wheezy? In case a fix exists, I think it is still possible for maintainers to try asking for a freeze exception. If the fix is not too invasive, they might very well get it. As a consequence of this reasoning, I think it's wiser to downgrade this bug. -- signature.asc Description: Digital signature
Bug#696907: RFS: mosquitto/0.15-2 [RC]
Hi, On Sat, Dec 29, 2012 at 3:59 AM, David Prévot taf...@debian.org wrote: doesn't seem in line with the current freeze policy [0], Rule #1: “do not make changes to the package that are not related to fixing the bugs in question […] this implies *not* […] Changing debhelper compat version” I agree, that should've been obvious. I've uploaded a new version that doesn't include the unrelated changes. Regards, Roger -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#693263: qcontrol: wheezy version of qcontrol does not support --direct
On Sat, 2012-12-29 at 14:48 +, Martin Michlmayr wrote: * Ian Campbell i...@hellion.org.uk [2012-12-29 14:20]: qcommand is probably right thing to use even in the Sid version, I believe qcommand only exists in the udeb, so this won't work. Might be better to backport --direct instead. One second thoughts this looks like a pretty small patch when isolated from the big upstream resyncs. Let me investigate further. Ian. -- Ian Campbell After 14 non-maintainer releases, I'm the S-Lang non-maintainer. -- Ray Dassen signature.asc Description: This is a digitally signed message part
Bug#521391: ifrench: changing back from ITA to O
retitle 521391 ITA: ifrench -- The French dictionary for ispell (Hydro-Quebec version) owner 521391 ! thanks On Tue, Dec 11, 2012 at 01:00:32AM +, Frank Lichtenheld wrote: This is an automatic email to change the status of ifrench back from ITA (Intent to Adopt) to O (Orphaned), because this bug hasn't seen any activity during the last 6 months. As previously stated, I'll upload ifrench with my name in the maintainer field whenever it next needs another upload, at the moment it's bug free, hasn't changed upstream in eons, and requires no maintenance. Until then, it'll have to stay as an ITA; only changing the maintainer field isn't worth an upload. Best wishes, Ryan -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#685625: libgeom: may cause segfault of grub-probe
If it's a question of minimal impact to fix the specific crash that
grub-probe encounters, then there are two more minimal ways to fix this
specific problem that come to mind:
replace reallocf with realloc---but in the unlikely case that realloc
fails, it doesn't deallocate the argument (this is the point of
reallocf)
explicitly declare reallocf instead of using the bsd/ header:
void *reallocf(void *, size_t)
however, I don't think either of these is better than the approach I
originally proposed, to add a #include directive that matches the one in
the reallocf manpage that debian ships.
(dropping the -Werror= flag addition would of course make it a bit more
minimal; it might avoid an FTBFS in the future, but if it's an FTBFS
that would point right at another crashing bug, well, it might be a
bonus rather than a detriment to FTBFS)
Being unfamiliar with the culture and practices of Debian, I can't speak
to whether a more invasive ('overlay') approach is appropriate or not in
light of the present freeze, but it seems that Guillem Jover has
concerns about doing that at this moment.
The machine where I originally encountered the trouble isn't yet in
production, so if there's an alternate fix proposed soon I'll be happy
to test it out. On the other hand, I think the presence or absence of
the implicit declaration warning is enough to indicate whether the bug
is present under any given fix...
Jeff
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#690908: unblock: libdatetime-timezone-perl/1.51-1+2012g
gregor herrmann wrote (29 Dec 2012 00:02:17 GMT) : Exactly (neither shipped nor used). Thanks, removing the moreinfo tag. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#690066: Bug really RC?
severity 690066 important thanks I don't think this bug is release critical. The right severity, for me, seems to be important. OK, one could argue about dataloss but someone opening a file created in a format that is not native to LO, then modifying the file, then saving it.should not yell for dataloss if (s)he hasn't kept a copy of the original file somewhere. Hence downgrading. Feel free to raise the severity if you disagree, but there are probably more important bugs to focus on. -- signature.asc Description: Digital signature
Bug#696932: dselect: doesn't show extended description in lower pane
Package: dselect Version: 1.16.9 Severity: important Hi, I did a clean install from wheezy DI beta4, then installed dselect via apt-get install dselect. When I started dselect on the linux console, the lower pane did not show the extended description. Only the package name and its brief description are shown, the remainder of the lower pane is filled with whitespace. I tried using the i command to toggle the verbosity of the display in the lower pane, the dependency information is then cycled through as occurs normally, however, the extended description is not included in any of the cycled through displays. The only locale that I have installed is en_us.utf8, and I have not made any other configuration changes after the install. Note, I am submitting this bug from my squeeze system, however, this bug is against the wheezy version. Thanks, Jeffrey Sheinberg -- System Information: Debian Release: 6.0.6 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'proposed-updates'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 3.2.0-0.bpo.4-amd64 (SMP w/2 CPU cores) Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968) Shell: /bin/sh linked to /bin/dash Versions of packages dselect depends on: ii dpkg 1.15.8.13 Debian package management system ii libc6 2.11.3-4 Embedded GNU C Library: Shared lib ii libgcc1 1:4.4.5-8 GCC support library ii libncursesw5 5.7+20100313-5 shared libraries for terminal hand ii libstdc++64.4.5-8The GNU Standard C++ Library v3 dselect recommends no packages. Versions of packages dselect suggests: ii perl 5.10.1-17squeeze4 Larry Wall's Practical Extraction -- 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#685625: libgeom: may cause segfault of grub-probe
On Fri, 2012-12-28 at 19:44:41 -0800, Christoph Egger wrote: I see there's a patch in this bug report. Do you think this is a solution for wheezy? If so I'd volunteer to upload a new version of freebsd-libs I've checked now the interaction of the libbsd-overlay and freebsd-glue, and they do not play well. Consequently that would require way more changes than the proposed patch, so even if I've not tested it, it would seem to be the better solution for now given the freeze. Moving the -Werror line one up would reduce the diff by 1, but that's pretty much insignificant, so regardless of that: Acked-by: Guillem Jover guil...@debian.org I'll add missing stuff to libbsd, and for jessie I'll make freebsd-glue play well with the overlay, once that's fixed the other packages can be switched back to use the overlay. Thanks, Guillem -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#690902: More information needed to handle this bug...anyway, it is not release critical
tags 690902 moreinfo severity 690902 normal thanks I don't think that gnome-shell segfaulting randomly only for one user (no other user reported this) should be RC. Anyway, if you want this bug to be dealt with, you need to follow advices that have been given in the bug log: Check /home/YOURUSER/.xsession-errors or /home/YOURUSER/.xsession-errors.old for relevant error messages. Post them here. Take care as this log can frequently contain sensitive information logged by some applications. You could try creating a new user on the computer and try reproducing the problem with it. If the problem does not happen then it could be some settings under your other account. -- signature.asc Description: Digital signature
Bug#696907: RFS: mosquitto/0.15-2 [RC]
Hi Roger, Le 29/12/2012 11:21, Roger Light a écrit : I've uploaded a new version that doesn't include the unrelated changes. Thanks, the three RC-bug fixes are pretty straightforward, but the DEP-3 headers don't contain an Applied-Upstream field. Since you seem involved upstream, are those fixes not applied upstream because of a rewrite of those parts in the current code? If not, could you please point to the related upstream commits? I'd prefer if someone already familiar with the codebase, or at least using MQTT, would be willing to review the changes and upload it. If that doesn't happen, feel free to ping me back in about a week. Regards David signature.asc Description: OpenPGP digital signature
Bug#678042: seabios - Please enable Xen support
Il 29/12/2012 14:25, Michael Tokarev ha scritto: 29.12.2012 16:59, Fabio Fantoni wrote: Updated debian seabios package to 1.7.1 (on personal repository for now), tested with wheezy and xen-unstable and is working. Package repository: https://github.com/Fantu/pkg-seabios Hmm. This repository contains just 2 commits: initial import with seabios 1.7.1 and Updated debian/optionrom from qemu 1.3.0 keeping debian changes This is definitely not the way how it can be imported into debian repository, all changes needs to be re-done again -- unless there's a way which I don't see. Changelog of my build: --- seabios (1.7.1-0.1) experimental; urgency=low * Non-maintainer upload * New upstream release 1.7.1 featuring xen support (Closes: #678042) 1.7.1 needs a few more fixes on top, which are unrelated to xen but should be present for qemu. It does not mean it isn't a good idea to update it now anyway. * Removed debian/patches/fix-==-in-shell.patch (applied upstream). * Updated debian/optionrom from qemu 1.3.0 keeping debian changes. Which debian changes is that? Could be uploaded into Debian and hence enabling qemu upstream into xen on experimental repository? Yes, we basically forgot about this stuff already, it's a good idea to ping us so we'll start doing things again. I'm looking at it now. Thanks! /mjt Thanks for reply. I have taken debian folder from sid package, if you want simple see/update repository override debian folder of debian seabios repository, if there will be a problem tell me and I'll redo all forking repository from debian, updating seabios upstream to 1.7.1, ovveriding debian folder and doing commit, so you can see all my changes in one commit and also use that commit for update debian repository. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#695770: Shouldn't builds just be reattempted for python-2.6?
Subject says it all. I'm tempted to think that at least the mips and i386 failures were just a transient failure and the builds should just be reattempted. But I may be mistaken -- signature.asc Description: Digital signature
Bug#646704: Bug severity is too high
severity 646704 important thanks This bug doesn't fit the definition of serious as it only shows up for a precise set of installation types, those not being the most common, particularly when people use the Live CD to install. Downgrading to important as per the definition of improtant severity. -- signature.asc Description: Digital signature
Bug#614348: grub-legacy: Debian version of GRUB 0.97 won't boot Windows 7 (reboots computer)
Hello Laszlo, Has the recent grub patch fixed this problem? -- Regards Martin Naughton
Bug#248397: Subject: Re: GRUB 2 RFH
Hello Colin, Been looking at the grub2 for debian aswell. Is the help required with grub 1 or grub 2? i thought grub 1 was being dropped? http://packages.qa.debian.org/g/grub2.html -- Regards Martin Naughton
Bug#678042: seabios - Please enable Xen support
29.12.2012 19:52, Fabio Fantoni wrote: [] I have taken debian folder from sid package, if you want simple see/update repository override debian folder of debian seabios repository, if there will be a problem tell me and I'll redo all forking repository from debian, updating seabios upstream to 1.7.1, ovveriding debian folder and doing commit, so you can see all my changes in one commit and also use that commit for update debian repository. I just uploaded seabios_1.7.1-1 to unstable - is that okay with you? 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#696933: ITP: lanyfs-utils -- Userspace utilities for Lanyard FS (LanyFS)
Package: wnpp Severity: wishlist Owner: chrysn chr...@fsfe.org * Package name: lanyfs-utils Version : 1.4 Upstream Author : Dan Luedtke m...@danrl.de * URL : https://www.nonattached.net/lanyfs/ * License : GPL or BSD 3-clause Programming Lang: C Description : Userspace utilities for Lanyard FS (LanyFS) lanyfs-utils contains the userspace utilities required for operating a LanyFS file system, ie. mkfs.lanyfs and detectfs.lanyfs. the lanyfs file system is in the progress of being upstreamed to mainline linux; i think having the packages early would be a good idea as it helps both attract early adaptors and people working on kernel integration. packaging-wise, lanyfs-utils is pretty trivial; it's just a makefile generating the binaries. my current package uses debhelper with minimal overrides to find the makefile. signature.asc Description: Digital signature
Bug#688738: Fwd: Bug#688738: Unfixed RC bug and unable to install updated package
FYI
Begin forwarded message:
From: Dashamir Hoxha dashoho...@gmail.com
Subject: Re: Bug#688738: Unfixed RC bug and unable to install updated package
Date: 29 December 2012 11:27:51 PM GMT+08:00
To: Jeremy Malcolm jer...@malcolm.id.au
Hi Jeremy,
Thanks for letting me know.
I think that it should be removed from Debian, because it is on a dead end.
The framework used to build it is old and can be understood and used only
by me. Which means that nobody can potentially help me for maintaining and
improving it. Which means that it cannot be fixed and improved. And also
nobody is using it anyway (not even me myself).
Instead, I have been thinking about rewriting some parts of docbookwiki as
Drupal modules. Drupal is also old and a bloated framework, but there are
lots of developers using it, it is still being maintained and developed,
it is modular, etc.
One thing that can be imported from docbookwiki is the wiki syntax, which
I find more powerful than the other wikis that I have seen (maybe I am
biased).
Another thing is the idea of generating and exporting documents in
docbook format.
Keeping the history of changes (revisions), permission control etc. maybe are
not so important, or maybe Drupal has its own tools for managing them.
Best regards,
Dashamir
--
Jeremy Malcolm PhD LLB (Hons) B Com
Internet and Open Source lawyer, consumer advocate and geek
host -t NAPTR 5.9.8.5.2.8.2.2.1.0.6.e164.org|awk -F! '{print $3}'
Bug#678042: seabios - Please enable Xen support
Il 29/12/2012 17:09, Michael Tokarev ha scritto: 29.12.2012 19:52, Fabio Fantoni wrote: [] I have taken debian folder from sid package, if you want simple see/update repository override debian folder of debian seabios repository, if there will be a problem tell me and I'll redo all forking repository from debian, updating seabios upstream to 1.7.1, ovveriding debian folder and doing commit, so you can see all my changes in one commit and also use that commit for update debian repository. I just uploaded seabios_1.7.1-1 to unstable - is that okay with you? Thanks, /mjt Yes thanks, I not have time to test it now but if same update that I did then working with xen 4.3 and probably also xen 4.2. Your have also improved changelog and control file. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#696934: Missing pure-ftpd.conf file of pure-ftpd?
Package: pure-ftpd Version: 1.0.28-3+squeeze1 Hello, I want to change default umask for pure-ftpd but It seems pure-ftpd.conf file is missing after installation of pure-ftpd on: root@debian:/etc/pure-ftpd# uname -a Linux debian 2.6.32-5-686 #1 SMP Sun Sep 23 09:49:36 UTC 2012 i686 GNU/Linux At least i can't find it anymore and i can't set default umask for file/folder operations throught pure-ftpd. What i'm missing? Thanks in advance. root@debian:/etc/pure-ftpd# dpkg --get-selections|grep pure pure-ftpd install pure-ftpd-commoninstall root@debian:/etc/pure-ftpd# dpkg --get-selections|grep pure pure-ftpd install pure-ftpd-commoninstall root@debian:/etc/pure-ftpd# apt-cache show pure-ftpd Package: pure-ftpd Priority: optional Section: net Installed-Size: 468 Maintainer: Stefan Hornburg (Racke) ra...@linuxia.de Architecture: i386 Version: 1.0.28-3+squeeze1 Replaces: ftp-server Provides: ftp-server Depends: lsb-base (= 3.2-14), openbsd-inetd | inet-superserver, pure-ftpd-common (= 1.0.28-3+squeeze1), libc6 (= 2.3.3), libcap2 (= 2.10), libpam0g (= 0.99.7.1), libssl0.9.8 (= 0.9.8m-1) Conflicts: ftp-server Filename: pool/main/p/pure-ftpd/pure-ftpd_1.0.28-3+squeeze1_i386.deb Size: 154742 MD5sum: 6d9522cbeb99fb3b4135540f93c87271 SHA1: e7373510312a5c0e84d1b15703a73b49f5af92ff SHA256: 77ed7e3852548dbacfc03505257e93d427d77be5800b475f176ca40d35b0f1c2 Description: Secure and efficient FTP server Free, secure, production-quality and standard-conformant FTP server. Features include chrooted home directories, virtual domains, built-in 'ls', anti-warez system, configurable ports for passive downloads, FXP protocol, bandwidth throttling, ratios, fortune files, Apache-like log files, fast standalone mode, atomic uploads, text / HTML / XML real-time status report, virtual users, virtual quotas, privilege separation, SSL/TLS and more. Homepage: http://www.pureftpd.org/ Tag: interface::daemon, network::server, protocol::ftp, protocol::ssl, role::program, works-with::file root@debian:/etc/pure-ftpd# ls -liahR * 35402 -rw-r--r-- 1 root root 230 Jan 17 2012 pureftpd-dir-aliases 35420 -rw--- 1 root root 101 Dec 29 10:07 pureftpd.passwd 35278 -rw--- 1 root root 2.2K Dec 29 10:07 pureftpd.pdb auth: total 8.0K 35415 drwxr-xr-x 2 root root 4.0K Dec 29 09:59 . 35401 drwxr-xr-x 5 root root 4.0K Dec 29 10:07 .. 35403 lrwxrwxrwx 1 root root 26 Dec 29 09:58 50pure - /etc/pure-ftpd/conf/PureDB conf: total 36K 35404 drwxr-xr-x 2 root root 4.0K Dec 29 09:36 . 35401 drwxr-xr-x 5 root root 4.0K Dec 29 10:07 .. 35412 -rw-r--r-- 1 root root 36 Jan 17 2012 AltLog 35413 -rw-r--r-- 1 root root6 Jan 17 2012 FSCharset 35409 -rw-r--r-- 1 root root5 Jan 17 2012 MinUID 35410 -rw-r--r-- 1 root root4 Jan 17 2012 NoAnonymous 35408 -rw-r--r-- 1 root root4 Jan 17 2012 PAMAuthentication 35411 -rw-r--r-- 1 root root 28 Jan 17 2012 PureDB 35406 -rw-r--r-- 1 root root3 Jan 17 2012 UnixAuthentication db: total 8.0K 35414 drwxr-xr-x 2 root root 4.0K Jan 17 2012 . 35401 drwxr-xr-x 5 root root 4.0K Dec 29 10:07 .. root@debian:/etc/pure-ftpd# ps aux|grep pure root 2887 0.0 0.0 5444 652 ?Ss 10:07 0:00 pure-ftpd (SERVER) root 3053 0.0 0.0 3304 772 pts/0S+ 11:05 0:00 grep pure root@debian:/etc/pure-ftpd# lsof -c pure-ftpd COMMANDPID USER FD TYPE DEVICE SIZE/OFF NODE NAME pure-ftpd 2887 root cwdDIR8,1 4096 2 / pure-ftpd 2887 root rtdDIR8,1 4096 2 / pure-ftpd 2887 root txtREG8,1 135624 8345 /usr/sbin/pure-ftpd pure-ftpd 2887 root memREG8,1 1527584 270188 /usr/lib/locale/locale-archive pure-ftpd 2887 root memREG8,114888 529395 /lib/libattr.so.1.1.0 pure-ftpd 2887 root memREG8,179980 254877 /usr/lib/libz.so.1.2.3.4 pure-ftpd 2887 root memREG8,1 1327556 539192 /lib/i686/cmov/libc-2.11.3.so pure-ftpd 2887 root memREG8,143360 529415 /lib/libpam.so.0.82.2 pure-ftpd 2887 root memREG8,113456 531180 /lib/libcap.so.2.19 pure-ftpd 2887 root memREG8,1 9736 539173 /lib/i686/cmov/libdl-2.11.3.so pure-ftpd 2887 root memREG8,138360 539177 /lib/i686/cmov/libcrypt-2.11.3.so pure-ftpd 2887 root memREG8,1 1393052 269289 /usr/lib/i686/cmov/libcrypto.so.0.9.8 pure-ftpd 2887 root memREG8,1 302040 269290 /usr/lib/i686/cmov/libssl.so.0.9.8 pure-ftpd 2887 root memREG8,1 118060 529376 /lib/ld-2.11.3.so pure-ftpd 2887 root0r CHR1,3 0t0545 /dev/null pure-ftpd 2887 root1w CHR1,3 0t0545 /dev/null pure-ftpd 2887 root2w CHR1,3 0t0545 /dev/null pure-ftpd 2887 root3u unix 0xf6307c00 0t0 9852 socket
Bug#696935: hobbit-plugins: proposed new client plugin to test dns service on clients
Package: hobbit-plugins
Version: 20121226+db1
Severity: wishlist
Tags: patch
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
I found it easier to start from scratch using Hobbit.pm than to port
the old bb-dnsquery.pl to xymon, so here is the result.
Warning, Xymon newb.
Also, I didn't mess with changelog in this patch, since it seemed to
create more complications than it eliminated.
- -- System Information:
Debian Release: wheezy/sid
APT prefers testing
APT policy: (900, 'testing')
Architecture: amd64 (x86_64)
Kernel: Linux 3.2.0-3-amd64 (SMP w/8 CPU cores)
Locale: LANG=en_CA.UTF-8, LC_CTYPE=en_CA.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Versions of packages hobbit-plugins depends on:
ii dpkg 1.16.9
ii xymon-client 4.3.7-1
Versions of packages hobbit-plugins recommends:
ii dctrl-tools 2.22.2
ii libsysadm-install-perl 0.39-1
ii lsb-release 4.1+Debian8
ii lsof4.86+dfsg-1
ii sudo1.8.5p2-1
Versions of packages hobbit-plugins suggests:
ii bzr2.6.0~bzr6526-1
ii debsums2.0.52
pn fping none
ii git1:1.7.10.4-1+wheezy1
pn ipmitool none
pn libdbd-pg-perl none
ii libfile-slurp-perl .19-1
ii libnet-dns-perl0.66-2+b2
pn libnet-tftp-perl none
pn libpoe-component-irc-perl none
ii mercurial 2.2.2-1
ii ntp1:4.2.6.p5+dfsg-2
ii subversion 1.7.5-1
- -- Configuration Files:
/etc/sudoers.d/hobbit [Errno 13] Permission denied: u'/etc/sudoers.d/hobbit'
/etc/sudoers.d/xymon [Errno 13] Permission denied: u'/etc/sudoers.d/xymon'
- -- no debconf information
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.12 (GNU/Linux)
iJwEAQECAAYFAlDfGpgACgkQTiiN/0Um85koMwP/Z+c+q9A8PesJG1W7AIHfG/NU
IX+ETaL7NgINxhJy6xu/jrr+JssvPY1sHFEvTLyKjY6jvGRR6R4b0BAY79gKX7Ah
62mcOR2aD6v4gPPHO/wAvAVxwTR74l90+90XXEsTNa2VxKgQbkmeFjkA880vwcXp
BGb3EU1co5Cw+zSrkWY=
=rWEf
-END PGP SIGNATURE-
From a24833a6179ab835476a19b4694d2a0a7eed1249 Mon Sep 17 00:00:00 2001
From: David Bremner brem...@debian.org
Date: Sat, 29 Dec 2012 11:58:49 -0400
Subject: [PATCH] Add new client-side plugin, dnsq
There is an optional config file /etc/xymon/dnsq that is not installed
by the package, since there are defaults.
---
client-ext/dnsq | 70 +++
clientlaunch.d/dnsq.cfg |6
debian/control |2 +-
3 files changed, 77 insertions(+), 1 deletion(-)
create mode 100644 client-ext/dnsq
create mode 100644 clientlaunch.d/dnsq.cfg
diff --git a/client-ext/dnsq b/client-ext/dnsq
new file mode 100644
index 000..723366a
--- /dev/null
+++ b/client-ext/dnsq
@@ -0,0 +1,70 @@
+#!/usr/bin/perl -w
+
+# Copyright (C) 2012 David Bremner brem...@debian.org
+#
+# Permission is hereby granted, free of charge, to any person obtaining
+# a copy of this software and associated documentation files (the
+# Software), to deal in the Software without restriction, including
+# without limitation the rights to use, copy, modify, merge, publish,
+# distribute, sublicense, and/or sell copies of the Software, and to
+# permit persons to whom the Software is furnished to do so, subject to
+# the following conditions:
+#
+# The above copyright notice and this permission notice shall be
+# included in all copies or substantial portions of the Software.
+#
+# THE SOFTWARE IS PROVIDED AS IS, WITHOUT WARRANTY OF ANY KIND,
+# EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF
+# MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND
+# NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE
+# LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION
+# OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION
+# WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.
+
+# CONFIGURATION:
+#
+# Optionally, create a file /etc/xymon/dnsq containing names to
+# lookup, one per line
+
+use strict;
+use English;
+use Hobbit;
+use Net::DNS;
+use File::Slurp;
+
+sub fail {
+my $bb = shift;
+$bb-color_line('red', $@);
+exit;
+}
+
+my $config_file = /etc/xymon/dnsq;
+
+$ENV{'PATH'} = '/bin:/sbin:/usr/bin:/usr/sbin';
+delete @ENV{'IFS', 'CDPATH', 'ENV', 'BASH_ENV'};
+
+my @queries;
+
+if (-f $config_file) {
+@queries = read_file($config_file, chomp = 1);
+} else {
+@queries=qw(www.debian.org kernel.org aws.amazon.com www.google.com);
+}
+
+my $bb = new Hobbit ('dnsq');
+
+my $res = new Net::DNS::Resolver;
+fail ($bb, No resolver) unless ($res);
+
+foreach my $name (@queries) {
+my $packet = $res-search($name);
+if (defined($packet)) {
+ my $out = join( , $name, map { $_- rdatastr; } $packet-answer() );
+ $bb-color_line('green', $out.\n);
+} else {
+ $bb-color_line('red', $name failed);
+}
+}
+
+$bb-add_color ('green');
Bug#693147: Upstream released Twitter API 1.1 version
Hi Stephen, On Fri, December 28, 2012 22:15, Stephen Michael Kellat wrote: Okay. Cameron released TTYtter 2.1.0 as of 27 December 2012 which complies with Twitter API 1.1.[1] Twitter notes on their calendar that the drop dead date for Twitter API 1.0 is 5 March 2013.[2] Cameron notes that all previous versions of TTYtter will cease to work with Twitter as of that date due to Twitter's API deprecation. Also noted is that Term::ReadLine::TTYtter, which currently is packaged with the script in Debian, would have to be bumped up to a new version as the currently packaged version will not play nice with the new version of the script. The new upstream is done and Wheezy remains in freeze. The questions now: 1. Will the Release Team grant an exception since Twitter announced the major shift in API through an API deprecation on 16 August 2012 after the freeze kicked off on 30 June 2012? 2. If the Release Team will not grant an exception, can the package be pulled from shipping with Wheezy since it will likely be unusable shortly after Wheezy being released in 2013? 3. Do we have any idea if the other Twitter clients that are in the package archive are going to be ready for this API deprecation or will other packages be encountering issues if we ship them? This would be something more for the Release Team to consider than for the current bug. The new TTYtter 2.1.0 release is as of now available in Debian unstable. I have considered the options for this bug. I find that option 1 seems highly unlikely since it indeed means to allow a freeze exception for not only a new upstream release but a complete upstream new branch (2.1 vs 2.0). Besides that the package also requires upgrading Term::Readline::TTYtter to 1.4. I believe we best discount this option. Option two is certainly at our disposal. I doubt however that we should ask for removal from wheezy. Firstly, because it still works now, and we can always pull it from wheezy later when the API indeed is discontinued. And secondly, because TTYtter may still be useful for non-Twitter usage. Most notably identi.ca, which is used extensively in the free software world. So I'm inclined to go for the following path: a. Fix the problem in unstable. That has now been done. b. Lower this bug to severity 'important', to not require removal of TTYtter from Wheezy now or in the future. c. Invest effort to ensure that a version that supports Twitter is available for Wheezy. This can be done after release via Debian Backports or via the Stable Updates suite. If we change our mind on the 'b' step, we can always ask for removal later, we do not lose that option. Cheers, Thijs -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#696926: dovecot update breaks with tcpwrap
On Sat, Dec 29, 2012 at 02:29:01PM +0100, Julien Cristau wrote: This breaks existing installations, as it even fails to install. This is on purpose. Jaldhar, I guess the mention of tcp wrapper support Can you please add a bit of explanation what would be bad about tcpwrapper support? It does not hurt, adds 10k to the package, and in case of dovecot needs to be explicitly enabled in the configuration. Besides, silently breaking existing installation on upgrade without mentioning is a bug, not a wishlist item. Bye, Joerg signature.asc Description: Digital signature
Bug#696926: dovecot update breaks with tcpwrap
On Sat, Dec 29, 2012 at 17:25:48 +0100, Joerg Dorchain wrote: On Sat, Dec 29, 2012 at 02:29:01PM +0100, Julien Cristau wrote: This breaks existing installations, as it even fails to install. This is on purpose. Jaldhar, I guess the mention of tcp wrapper support Can you please add a bit of explanation what would be bad about tcpwrapper support? It does not hurt, adds 10k to the package, and in case of dovecot needs to be explicitly enabled in the configuration. It's a new feature, and as such not appropriate during a freeze. I don't know that it doesn't hurt, and don't want to go read the code to find out. Besides, silently breaking existing installation on upgrade without mentioning is a bug, not a wishlist item. You're running unstable, you can deal with breakage. It's mentioned both in the package changelog and in http://www.braincells.com/debian/index.cgi/search/item=285 Cheers, Julien signature.asc Description: Digital signature
Bug#685625: libgeom: may cause segfault of grub-probe
Hi, I agree that libbsd and freebsd-glue seem to conflict with each other, but neither one of them by itself has everything needed for freebsd-libs. So Jeff's patch is the least intrusive way to fix this, and that's what we have to go with at this late stage. It fixes a bug we're seeing now and is unlikely to introduce more... I can provide a similar patch for freebsd-utils which has the same issues, but the only problem I could confirm yet was a segfault in ifconfig bridge configuration (#696514) due to it. I propose adding the -Werror part of the patch into Wheezy as well. If it does trigger a FTBFS, it's because we missed something, or something wrong with the build environment that we need to know about. We might need to drop it someday for a new upstream release but hopefully not. Regards, -- Steven Chamberlain ste...@pyro.eu.org -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#695500: debian-installer-7.0-netboot-kfreebsd-amd64: does not boot from pxe
Hi Michael, Michael Tsang mikl...@gmail.com (09/12/2012): I cannot boot the installer from pxe. GRUB says prefix is not set and dies. It seems to be a configuration bug. I see now that the prefix is not set message appears very quickly, before GRUB switches into graphical mode. It seems harmless, because at the GRUB command line the prefix is correctly set. My guess is that the machine booting via PXE was unable to show the GRUB menu properly. For example, if some kind of console redirection was being used. This can be worked around by simply removing this file from the TFTP server: debian-installer/kfreebsd-amd64/font.pf2 And GRUB should fall back to text mode. Regards, -- Steven Chamberlain ste...@pyro.eu.org -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#696936: gnome-shell: Gnome shell hangs after login
Package: gnome-shell Version: 3.4.2-3 Severity: important Dear Maintainer, Sometimes (about every fourth of fifth time) directly after logging in the gnome shell is displayed but the user notification area only shows an 'x' mark and the whole desktop is not responsive. The only way to fix it is to go to another tty and kill that user's X-session. I think this is a blocking error. -- System Information: Debian Release: 7.0 APT prefers testing-updates APT policy: (500, 'testing-updates'), (500, 'testing-proposed-updates'), (500, 'testing') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.2.0-4-amd64 (SMP w/8 CPU cores) Locale: LANG=nl_NL.utf8, LC_CTYPE=nl_NL.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages gnome-shell depends on: ii dconf-gsettings-backend [gsettings-backend] 0.12.1-3 ii gconf-service3.2.5-1+build1 ii gir1.2-accountsservice-1.0 0.6.21-7 ii gir1.2-atk-1.0 2.4.0-2 ii gir1.2-caribou-1.0 0.4.4-1 ii gir1.2-clutter-1.0 1.10.8-2 ii gir1.2-cogl-1.0 1.10.2-6 ii gir1.2-coglpango-1.0 1.10.2-6 ii gir1.2-folks-0.6 0.6.9-1+b1 ii gir1.2-freedesktop 1.32.1-1 ii gir1.2-gconf-2.0 3.2.5-1+build1 ii gir1.2-gcr-3 3.4.1-3 ii gir1.2-gdesktopenums-3.0 3.4.2-3 ii gir1.2-gdkpixbuf-2.0 2.26.1-1 ii gir1.2-gee-1.0 0.6.4-2 ii gir1.2-gkbd-3.0 3.4.0.2-1 ii gir1.2-glib-2.0 1.32.1-1 ii gir1.2-gmenu-3.0 3.4.2-5 ii gir1.2-gnomebluetooth-1.03.4.2-1 ii gir1.2-gtk-3.0 3.4.2-4 ii gir1.2-json-1.0 0.14.2-1 ii gir1.2-mutter-3.03.4.1-5 ii gir1.2-networkmanager-1.00.9.4.0-6 ii gir1.2-pango-1.0 1.30.0-1 ii gir1.2-polkit-1.00.105-1 ii gir1.2-soup-2.4 2.38.1-2 ii gir1.2-telepathyglib-0.120.18.2-2 ii gir1.2-telepathylogger-0.2 0.4.0-1 ii gir1.2-upowerglib-1.00.9.17-1 ii gjs 1.32.0-2 ii gnome-bluetooth 3.4.2-1 ii gnome-icon-theme-symbolic3.4.0-2 ii gnome-settings-daemon3.4.2+git20120925.a4c817-2 ii gnome-shell-common 3.4.2-3 ii gnome-themes-standard3.4.2-2.1 ii gsettings-desktop-schemas3.4.2-3 ii libatk1.0-0 2.4.0-2 ii libc62.13-37 ii libcairo-gobject21.12.2-2 ii libcairo21.12.2-2 ii libcanberra0 0.28-6 ii libclutter-1.0-0 1.10.8-2 ii libcogl-pango0 1.10.2-6 ii libcogl9 1.10.2-6 ii libcroco30.6.6-2 ii libdbus-1-3 1.6.8-1 ii libdbus-glib-1-2 0.100-1 ii libebook-1.2-13 3.4.4-1 ii libecal-1.2-11 3.4.4-1 ii libedataserver-1.2-163.4.4-1 ii libedataserverui-3.0-1 3.4.4-1 ii libffi5 3.0.10-3 ii libfolks25 0.6.9-1+b1 ii libgck-1-0 3.4.1-3 ii libgconf-2-4 3.2.5-1+build1 ii libgcr-3-1 3.4.1-3 ii libgdk-pixbuf2.0-0 2.26.1-1 ii libgee2 0.6.4-2 ii libgirepository-1.0-11.32.1-1 ii libgjs0b [libgjs0-libmozjs185-1.0] 1.32.0-2 ii libgl1-mesa-glx [libgl1] 8.0.5-3 ii libglib2.0-0 2.33.12+really2.32.4-3 ii libgnome-keyring03.4.1-1 ii libgnome-menu-3-03.4.2-5 ii libgstreamer0.10-0 0.10.36-1 ii libgtk-3-0 3.4.2-4 ii libical0 0.48-2 ii libjson-glib-1.0-0 0.14.2-1 ii libmozjs185-1.0 1.8.5-1.0.0+dfsg-4 ii libmutter0 3.4.1-5 ii libnm-glib4 0.9.4.0-6 ii libnm-util2
Bug#690066: Bug really RC?
Christian PERRIER bubu...@debian.org writes: OK, one could argue about dataloss but someone opening a file created in a format that is not native to LO, then modifying the file, then saving it.should not yell for dataloss if (s)he hasn't kept a copy of the original file somewhere. I disagree with this reasoning more than with the severity. The UI suggests you might lose some formatting by saving in non-native format, not that it might delete most of your content. Clearly supporting non-native file formats is a pain, but upstream has chosen to try to make that seamless (rather than an import/export workflow which would have less chance of eating the user's data). Of course, sufficiently paranoid backups mitigate most data loss bugs. That doesn't make the software which requires such backups any less broken. Hence downgrading. Feel free to raise the severity if you disagree, but there are probably more important bugs to focus on. Well, given Rene has already said he waits for upstream, I don't think that makes any difference as far as actually getting the bug fixed. In the end I guess nobody seriously suggests removing LO from wheezy, OTOH, maybe a wheezy-ignore tag would be more appropriate? -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
