Bug#695318: linux-image-3.6-trunk-amd64: sdhci driver fails to interact with Ricoh e823 devices
On Fri, 2012-12-07 at 01:19 +0100, Arno Töll wrote: Package: src:linux Version: 3.6.8-1~experimental.1 Severity: normal The Ricoh e823:1180 5-in-1 card reader, mounted in my Thinkpad 420s notebook is quite unusable for me on Linux despite of being claimed by the sdhci (sdhci_pci) driver. Inserting a SDHC card into the card slot I get [...] Did this driver work in any earlier kernel version? Ben. -- Ben Hutchings Computers are not intelligent. They only think they are. signature.asc Description: This is a digitally signed message part
Bug#695318: linux-image-3.6-trunk-amd64: sdhci driver fails to interact with Ricoh e823 devices
On 07.12.2012 02:27, Ben Hutchings wrote: Did this driver work in any earlier kernel version? I tried it with both, 3.5 and 3.6 kernels. I have no other kernels installed on system. If you suspect a regression in a particular version let me know which version I shall test. However, if my problem is the same as reported to Ubuntu, it also affects at very least (their) kernels in version 3.0 and 2.6.38, according to LP #965280 and #773524 respectively. -- with kind regards, Arno Töll IRC: daemonkeeper on Freenode/OFTC GnuPG Key-ID: 0x9D80F36D signature.asc Description: OpenPGP digital signature
Bug#695188: multi Bug#123456 in email subject breaks thread
On Fri, Dec 7, 2012 at 4:18 AM, Don Armstrong d...@debian.org wrote: On Thu, 06 Dec 2012, YunQiang Su wrote: See this please. http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=687396 Maybe BTS is confused by mailing list tag like [buildd-tools-devel] Ah, ok. In general, the BTS should figure out mailing list tags if the list headers are still intact. If not, it assumes that you knew what you were doing, and leaves them alone. [It's sort of dangerous to assume that anything in brackets is a mailing list tag, which is why Debbugs doesn't strip them; it's also kind of annoying for mailing I don't ask to strip mailing list tag, I means that we shouldn't add #687396 twice. Detect whether subject has #687396 (The same as current bug number, not bug#.*), if it already has one, don't add it twice. lists to add them, as this information is trivially available in the message headers, but then again, not everyone sees those message headers.] Don Armstrong -- Three little words. (In order of importance.) █ █ ▌ ▞▀▖▌ ▌▛▀▘ █ ▌ ▌ ▌▝▞ ▛▀ you █ ▀▀▘▝▀ ▘ ▀▀▘ █ -- hugh macleod Three Words http://www.donarmstrong.com http://rzlab.ucr.edu -- YunQiang Su -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#695321: tpu: evolvotron/0.6.1-1+wheezy1 (pre-approval)
Control: tag -1 + confirmed Hi, On Fri, 7 Dec 2012 02:00:19 +0100 Axel Beckert a...@debian.org wrote: http://bugs.debian.org/683010 (FTBFS on ia64) was filed against evolvotron/0.6.1-2 before it could enter testing, so it never migrated. Nevertheless, 0.6.1-1 from testing is also affected, i.e. the bug was triggered by some toolchain change. I've just uploaded 0.6.2-1 to unstable (including the found fix for #683010) and it built fine on all architectures including ia64: https://buildd.debian.org/status/package.php?p=evolvotron As discussed with Philipp Kern, I've prepared an upload of 0.6.1-1+wheezy1 to testing-proposed-updates to fix that issue also in Wheezy. The proposed update just includes the fix for #683010 [1], and a change in the maintainer field [2] because I've just adopted that package. please attach a debdiff next time. We don't like going to gitweb pages and love having the diff in the mailbox for reference. That said: please go ahead (with the diff from [1], also attached for reference). Kind regards Philipp Kern [1] http://anonscm.debian.org/gitweb/?p=collab-maint/evolvotron.git;a=commitdiff_plain;h=86923eb7;hp=8ed004e From: Axel Beckert a...@deuxchevaux.org Date: Fri, 7 Dec 2012 00:06:42 + (+0100) Subject: Maintainer changed (see #691820) X-Git-Url: http://anonscm.debian.org/gitweb/?p=collab-maint%2Fevolvotron.git;a=commitdiff_plain;h=86923eb7;hp=8ed004e Maintainer changed (see #691820) --- diff --git a/debian/changelog b/debian/changelog index d7c630c..de6be9d 100644 --- a/debian/changelog +++ b/debian/changelog @@ -1,3 +1,11 @@ +evolvotron (0.6.1-1+wheezy1) testing-proposed-updates; urgency=low + + * Use Makefile instead of (not built) config.status as target. Fixes +FTBFS on ia64 (Closes: #683010) + * Maintainer changed (see #691820) + + -- Axel Beckert a...@debian.org Thu, 06 Dec 2012 01:29:50 + + evolvotron (0.6.1-1) unstable; urgency=low * New upstream version. diff --git a/debian/control b/debian/control index 2551a4a..27cac39 100644 --- a/debian/control +++ b/debian/control @@ -1,7 +1,7 @@ Source: evolvotron Section: graphics Priority: optional -Maintainer: Gürkan Sengün gur...@phys.ethz.ch +Maintainer: Axel Beckert a...@debian.org Build-Depends: debhelper (= 7), libqt4-dev, libboost-dev, libboost-serialization-dev Standards-Version: 3.8.3 Homepage: http://www.bottlenose.demon.co.uk/share/evolvotron/ diff --git a/debian/rules b/debian/rules index 1dfe9e6..2f2fb0f 100755 --- a/debian/rules +++ b/debian/rules @@ -10,13 +10,13 @@ else CFLAGS += -O2 endif -config.status: configure +Makefile: configure dh_testdir QTDIR=/usr/lib/qt3 ./configure CFLAGS=$(CFLAGS) LDFLAGS=-Wl,-z,defs build: build-stamp -build-stamp: config.status +build-stamp: Makefile dh_testdir $(MAKE) touch $@ signature.asc Description: PGP signature
Bug#695322: unblock: speech-dispatcher/0.7.1-6.2
Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: unblock
Hello,
Could you unblock package speech-dispatcher?
There was a missing breaks/replaces for some files moved between
speech-dispatcher and libspeechd-dev, leading to an upgrade issue, thus
the control change below.
A user also reported that the mbrola output introduced by the newer
upstream version 0.7.1 (wheezy had 0.7) is very bogus, making the mbrola
output just unusable, and provided a one-liner fix that only changes the
mbrola output support, see espeak-mbrola-generic.conf.patch.
unblock speech-dispatcher/0.7.1-6.2
diff -Nru speech-dispatcher-0.7.1/debian/changelog
speech-dispatcher-0.7.1/debian/changelog
--- speech-dispatcher-0.7.1/debian/changelog2012-02-17 16:16:36.0
+0100
+++ speech-dispatcher-0.7.1/debian/changelog2012-12-07 02:14:24.0
+0100
@@ -1,3 +1,14 @@
+speech-dispatcher (0.7.1-6.2) unstable; urgency=low
+
+ * Non-maintainer upload.
+ * control: Add break/replace for move of libsdaudio.{a,so} from
+speech-dispatcher to libspeechd-dev, thanks Andreas Beckmann for the
+report patch; closes: #694295.
+ * patches/espeak-mbrola-generic.conf.patch: Add patch from Mau to fix mbrola
+generic output; closes: #665382.
+
+ -- Samuel Thibault sthiba...@debian.org Fri, 07 Dec 2012 01:28:18 +0100
+
speech-dispatcher (0.7.1-6.1) unstable; urgency=low
* Non-maintainer upload.
diff -Nru speech-dispatcher-0.7.1/debian/control
speech-dispatcher-0.7.1/debian/control
--- speech-dispatcher-0.7.1/debian/control 2012-02-17 15:48:15.0
+0100
+++ speech-dispatcher-0.7.1/debian/control 2012-12-07 01:43:23.0
+0100
@@ -51,6 +51,8 @@
Priority: extra
Depends: libspeechd2 (= ${binary:Version}), ${misc:Depends}
Suggests: speech-dispatcher
+Breaks: speech-dispatcher ( 0.7.1-6)
+Replaces: speech-dispatcher ( 0.7.1-6)
Description: Speech Dispatcher: Development libraries and header files
Speech Dispatcher provides a device independent layer for speech synthesis.
It supports various software and hardware speech synthesizers as
diff -Nru
speech-dispatcher-0.7.1/debian/patches/espeak-mbrola-generic.conf.patch
speech-dispatcher-0.7.1/debian/patches/espeak-mbrola-generic.conf.patch
--- speech-dispatcher-0.7.1/debian/patches/espeak-mbrola-generic.conf.patch
1970-01-01 01:00:00.0 +0100
+++ speech-dispatcher-0.7.1/debian/patches/espeak-mbrola-generic.conf.patch
2012-12-07 01:59:33.0 +0100
@@ -0,0 +1,11 @@
+--- a/config/modules/espeak-mbrola-generic.conf.orig 2011-04-27
12:01:16.0 +0200
b/config/modules/espeak-mbrola-generic.conf2012-03-21
17:25:44.066763025 +0100
+@@ -18,7 +18,7 @@
+ # can modify this value, see other parameters).
+ # The command can be split into more lines, if necessary, using '\'.
+ GenericExecuteSynth \
+-echo \'$DATA\' | espeak -v mb-$VOICE $PUNCT -s $RATE -a $VOLUME | mbrola -v
$VOLUME -e /usr/share/mbrola/$VOICE/$VOICE - -.au | $PLAY_COMMAND
++echo \'$DATA\' | espeak -v mb-$VOICE -s $RATE -p $PITCH $PUNCT -q --stdin
--pho | mbrola -v $VOLUME -e /usr/share/mbrola/$VOICE/$VOICE - -.au |
$PLAY_COMMAND
+
+ # The following three items control punctuation levels None, Some, and All.
+ # Each of these values will be substituted into the $PUNCT variable depending
diff -Nru speech-dispatcher-0.7.1/debian/patches/series
speech-dispatcher-0.7.1/debian/patches/series
--- speech-dispatcher-0.7.1/debian/patches/series 2012-02-17
15:47:10.0 +0100
+++ speech-dispatcher-0.7.1/debian/patches/series 2012-12-07
02:00:25.0 +0100
@@ -4,3 +4,4 @@
build-doc.patch
procname.patch
pico-generic.patch
+espeak-mbrola-generic.conf.patch
-- System Information:
Debian Release: wheezy/sid
APT prefers testing
APT policy: (990, 'testing'), (500, 'unstable'), (500, 'stable'), (1,
'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 3.0.4 (SMP w/8 CPU cores)
Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash
--
Samuel
--- christ gives channel operator status to Dieu
-+- #ens-mim and hell -+-
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#649878:
This may be completely unrelated, but I was having a similar error. I looked through some of the various errors I was receiving and noticed it was trying to load projects from my Java only version of Eclipse. I changed the workspace to a new workspace for CDT and it fixed the problem. -- DJ Qix JD Ballard Boise, ID
Bug#695318: linux-image-3.6-trunk-amd64: sdhci driver fails to interact with Ricoh e823 devices
On Fri, 2012-12-07 at 02:31 +0100, Arno Töll wrote: On 07.12.2012 02:27, Ben Hutchings wrote: Did this driver work in any earlier kernel version? I tried it with both, 3.5 and 3.6 kernels. I have no other kernels installed on system. If you suspect a regression in a particular version let me know which version I shall test. However, if my problem is the same as reported to Ubuntu, it also affects at very least (their) kernels in version 3.0 and 2.6.38, according to LP #965280 and #773524 respectively. There are also some similar bug reports on bugzilla.kernel.org: https://bugzilla.kernel.org/show_bug.cgi?id=43370 https://bugzilla.kernel.org/show_bug.cgi?id=50011 Do either of those seem to match what you're seeing? Ben. -- Ben Hutchings Computers are not intelligent. They only think they are. signature.asc Description: This is a digitally signed message part
Bug#695323: icedove: error occurred while creating a message compose window
Package: icedove Version: 17.0-1 Severity: normal When trying to forward certain messages, I receive the following: An error occurred while creating a message compose window. Please try again. In the error console I see: Timestamp: 07.12.2012 03.15.57 Error: [Exception... Component returned failure code: 0x80520006 (NS_ERROR_FILE_TARGET_DOES_NOT_EXIST) [nsIFile.copyTo] nsresult: 0x80520006 (NS_ERROR_FILE_TARGET_DOES_NOT_EXIST) location: JS frame :: chrome://messenger/content/messengercompose/MsgComposeCommands.js :: AddAttachments :: line 3596 data: no] Source File: chrome://messenger/content/messengercompose/MsgComposeCommands.js Line: 2419 After clicking the OK button for the error message, the following is logged: Timestamp: 07.12.2012 03.15.59 Error: NS_ERROR_FAILURE: Component returned failure code: 0x80004005 (NS_ERROR_FAILURE) [nsIMsgCompose.UnregisterStateListener] Source File: chrome://messenger/content/messengercompose/MsgComposeCommands.js Line: 2459 On the messages that inhibit this problem, reply and reply-to-all work fine but forward will not. So far the unforwardable messages have from RIPE (Notification of RIPE Database changes) and I have only seen this problem with these messages from RIPE. I can reproduce this with 10.0.10-1, 10.0.11-1, and 17.0-1. I can still reproduce it with a clean profile (these messages are located in an IMAP-enabled account). I cannot, however, reproduce it with the upstream Thunderbird downloaded from mozilla.org, with Thunderbird in an Ubuntu 12.10 VM, nor with Thunderbird in a Windows VM. -- System Information: Debian Release: wheezy/sid APT prefers testing APT policy: (990, 'testing'), (500, 'stable'), (50, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.2.0-4-amd64 (SMP w/6 CPU cores) Locale: LANG=fi_FI.UTF-8, LC_CTYPE=fi_FI.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages icedove depends on: ii debianutils 4.3.2 ii fontconfig2.9.0-7 ii libasound21.0.25-4 ii libatk1.0-0 2.4.0-2 ii libc6 2.13-37 ii libcairo2 1.12.2-2 ii libdbus-1-3 1.6.8-1 ii libdbus-glib-1-2 0.100-1 ii libevent-2.0-52.0.19-stable-3 ii libffi5 3.0.10-3 ii libfontconfig12.9.0-7 ii libfreetype6 2.4.9-1 ii libgcc1 1:4.7.2-4 ii libgdk-pixbuf2.0-02.26.1-1 ii libglib2.0-0 2.33.12+really2.32.4-3 ii libgtk2.0-0 2.24.10-2 ii libhunspell-1.3-0 1.3.2-4 ii libjpeg8 8d-1 ii libnspr4 2:4.9.2-1 ii libnss3 2:3.13.6-1 ii libnss3-1d2:3.13.6-1 ii libpango1.0-0 1.30.0-1 ii libpixman-1-0 0.26.0-3 ii libsqlite3-0 3.7.13-1 ii libstartup-notification0 0.12-1 ii libstdc++64.7.2-4 ii libvpx1 1.1.0-1 ii libx11-6 2:1.5.0-1 ii libxext6 2:1.3.1-2 ii libxrender1 1:0.9.7-1 ii libxt61:1.1.3-1 ii psmisc22.19-1 ii zlib1g1:1.2.7.dfsg-13 Versions of packages icedove recommends: ii hunspell-eu-es [hunspell-dictionary] 0.4.20081029-6 ii myspell-en-gb [myspell-dictionary]1:3.3.0-4 ii myspell-en-us [myspell-dictionary]1:3.3.0-4 ii myspell-fi [myspell-dictionary] 0.7-18 Versions of packages icedove suggests: ii fonts-lyx 2.0.3-3 ii libgssapi-krb5-2 1.10.1+dfsg-3 -- no debconf information -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#692529: ITP: gateone -- HTML5 web-based terminal emulator and ssh client
I quickly browsed around a bit. The killall() function in gateone/utils.py looks kind of scary. It seems to kill all processes that contain python and gateone.py in their name. This should match emacs -nw python.txt gateone.py and might be a mild security issue too: for session in sessions: if session in cmdline: try: os.kill(pid, signal.SIGTERM) except OSError: pass # PID is already dead--great elif 'python' in cmdline: if 'gateone.py' in cmdline: try: os.kill(pid, signal.SIGTERM) except OSError: pass # PID is already dead--great Perhaps gateone could use cgroups? I am the author of Gate One. You know what would be great? If you reported this issue! ;) I just pushed a commit to the Github repo ( https://github.com/liftoff/GateOne) to make the killall function a _lot_ more explicit. However, like you said it probably wouldn't have been much of an issue in the real world (no reports of, gateone.py killed my emacs session! yet =). I'll see if I can make a 1.2 or 1.1.1 release soon with the fix included. Please let me know if you encounter anything else like this. Also, it doesn't hurt to open an issue in the tracker (next time =): https://github.com/liftoff/GateOne/issues -- Dan McDougall - Chief Executive Officer and Developer Liftoff Software ✈ Your flight to the cloud is now boarding.
Bug#693774: ITP: grub-finnix -- Build a Finnix bootloader stanza on GRUB 2 systems
On 12/02/2012 03:54 AM, Marco d'Itri wrote: postinst I can read in /etc/default/grub-finnix, check if FINNIX_ISO is set, and if not, mention that it must be configured from /etc/default/grub-finnix. Please don't! This way you will annoy everybody on every new install. It would be much better if you could e.g. automatically set FINNIX_ISO in postinst to the most recent file matching /boot/finnix-*.iso. I meant a simple echo warning, not a blocking db_input notification. Still, I can appreciate not cluttering dpkg output, so I have removed that. On your suggestion, I added to ability to check for /boot/finnix-*.iso or any Finnix ISOs in /boot/finnix and update /etc/default/grub-finnix, but then removed it. I didn't like the idea of postinst arbitrarily modifying a conffile, so now /etc/default/grub-finnix just contains /boot/finnix by default. If it exists and contains Finnix ISOs, it will be processed. If not, nothing will happen. FYI, the bzr repo URL changed slightly from my original post, it is now: https://code.launchpad.net/~finnix/finnix/grub-finnix-pkg RF signature.asc Description: OpenPGP digital signature
Bug#695324: libwine-dev: Description doesn't mention tools or manpages
Package: libwine-dev Version: 1.4.1-4 Severity: normal Dear Maintainer, The description field of libwine-dev says: , | Description: Windows API implementation - development files | Wine is a free MS-Windows API implementation. | This is still a work in progress and many applications may still not work. | . | This package provides the C header files. ` While this is true, it neglects to mention that this package also contains: * The programs winedump, winegcc, winemaker, wmc, winebuild, widl, and wrc. * (stubby) manpages for the Windows API. -- 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 libwine-dev depends on: ii libc6 2.13-37 ii libc6-dev 2.13-37 ii libgettextpo0 0.18.1.1-9 ii libwine1.4.1-4 libwine-dev recommends no packages. Versions of packages libwine-dev suggests: ii wine-doc 1.0.0-1 -- no debconf information -- 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#449480: closed by Julien Cristau jcris...@debian.org (Bug#408666: fixed in xterm 287-1)
OK the .deb showed up this morning. However one still sees only one character of $ echo 絕對 絕對 The other is still a square. XTERM_VERSION=XTerm(287) Locale: LANG=zh_TW.UTF-8, LC_CTYPE=zh_TW.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash Versions of packages xterm depends on: ii libc6 2.13-37 ii libfontconfig1 2.9.0-7 ii libice6 2:1.0.8-2 ii libtinfo5 5.9-10 ii libutempter01.1.5-4 ii libx11-62:1.5.0-1 ii libxaw7 2:1.0.10-2 ii libxft2 2.3.1-1 ii libxmu6 2:1.1.1-1 ii libxpm4 1:3.5.10-1 ii libxt6 1:1.1.3-1 ii xbitmaps1.1.1-2 -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#677650: Here's a patch that APPEARS to work
I don't know Ruby AT ALL, but I did a bit of googling and this appears
to make unhide.rb work with 1.9:
--- unhide.rb.orig 2012-12-06 23:53:57.0 -0500
+++ unhide.rb 2012-12-06 23:52:51.0 -0500
@@ -29,7 +29,11 @@
# Support for libc functions not covered by the standard Ruby
# libraries
module LibC
- extend DL::Importable
+ if RUBY_VERSION =~ /^1\.8/
+extend DL::Importable
+ else
+extend DL::Importer
+ end
dlload libc.so.6
# PID scanning functions
@@ -147,7 +151,7 @@
$ps_pids[pid]
}],
- [/proc, proc { |pid|
+ [/proc, lambda { |pid|
# Is there a /proc entry for this pid?
unless File.directory?(/proc/#{pid})
break
The first hunk changes from DL::Importable to DL::Importer on versions
above 1.8. Since the only method actually used is extern(), and
the only change in 1.9 is addition optional flags, that's
all the change yo need.
Patch stolen from
https://github.com/mwotton/Hubris/commit/84515473e079e36f799b8210b424d61b7248798a
The second hunk deals with what appears to be a core change between
1.8 and 1.9. In 1.8, proc was an alias for lambda. In 1.9, there's a
difference: lambda creates a new function scope (which things like break
and return can jump to), while proc does not (so break and return try
to return from the caller's scope)
Explained at:
http://www.skorks.com/2010/05/ruby-procs-and-lambdas-and-the-difference-between-them/#difference
http://stackoverflow.com/questions/626/when-to-use-lambda-when-to-use-proc-new
http://railspikes.com/2008/9/8/lambda-in-ruby-1-9
The other methods don't use break or return, so there's no need to
change them. (I presume proc has somewhat less overhead.)
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#695325: document workaround for omitted script run_email2trac in package trac-email2trac
Package: trac-email2trac Version: 1.0 Severity: normal The trac-email2trac package is missing the run_email2trac script. It is not strictly necessary but the workaround should be documented in the man pages for email2trac. -- System Information: Debian Release: 6.0.4 APT prefers stable APT policy: (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 2.6.32-5-amd64 (SMP w/1 CPU core) Locale: LANG=en_US.utf8, LC_CTYPE=en_US.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#685716: debirf: have network-dhcp use a variable to control device
On 09/06/2012 04:04 PM, Matt Taggart wrote: It would be nice if you could set a kernel command line variable to control the device too. That way you could use the same debirf image and just set the device at boot time, rather than needing to build separate images. It could function similar to the way that the serial-console stuff works where the cmdline is checked and if something is set then it does the right thing. This sounds like a much better approach to me, and i would be happy to adopt a patch that implements it. I haven't had the time to work on this recently, unfortunately. --dkg -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#695250: tomcat6: CVE-2012-4534 CVE-2012-4431 CVE-2012-3546
On 12/05/2012 11:43 PM, Moritz Muehlenhoff wrote: Package: tomcat6 Severity: grave Tags: security Justification: user security hole More Tomcat security issues have been disclosed: http://tomcat.apache.org/security-6.html The page contains links to the upstream fixes. BTW, is there a specific reason why both tomcat6 and tomcat7 are present in Wheezy? This will duplicate all efforts for security updates in Wheezy. Hi Moritz, I have an updated package that includes the patches for these 3 CVEs and am doing some smoke-testing now. But before I upload, I have a question about what is permissible to include in the upload. I'd like to rename the patches that were included in the 6.0.35-5+nmu1 upload so they follow the same naming convention as the other patches in the package and include the origin patch header. (As you point out, after all, we'll be supporting this package for a long time to come.) Also, I'd like to quilt refresh the patches in the package, as they're getting a bit fuzzy. So, no substantive or real packaging changes, but the interdiff will be a bit larger. Is that okay, or should I upload with only the new patches for the CVEs applied? Regarding tomcat6 and tomcat7, although they are certainly related, they implement different versions of the servlet and JSP specifications [1], and there are a number still organizations running applications developed for/tested on tomcat6 in production. There is a migration guide for going from 6.x to 7.x that must be taken into consideration [2]. But specifically for Debian, there are still a number of packages in wheezy that depend explicitly on tomcat6 and/or libservlet2.5-java. According to popcon, tomcat6 is about 5x more popular than tomcat7, and libservlet2.5 is quite popular indeed [3,4]. Thank you, tony [1] http://tomcat.apache.org/whichversion.html [2] http://tomcat.apache.org/migration-7.html [3] http://qa.debian.org/popcon.php?package=tomcat6 [4] http://qa.debian.org/popcon.php?package=tomcat7 signature.asc Description: OpenPGP digital signature
Bug#695326: cloud-init: improved package descritpion
package: cloud-init severity: wishlist Please add this to the package description: On Donnerstag, 6. Dezember 2012, Brian Gupta wrote: Q: What is cloud-init? A: Cloud-init is a framework written in Python for handling EC2 userdata to configure a newly instantiated EC2 instance. See upstream project for more details: https://help.ubuntu.com/community/CloudInit (ar least the first sentence of this answer.) thanks Brian, for starting this FAQ! cheers, Holger -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#466181: tagging 466181
Hi Samuel, On Thu, December 6, 2012 21:13, Samuel Bronson wrote: tags 466181 + security Why are you adding this tag? The last message in the bug log has a clear statement from the security team that the tag is not warranted for this bug. Cheers, Thijs -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#640499: libxvmc: please add multiarch support
On 2012-12-07 00:43, Carlos Alberto Lopez Perez wrote: MultiArch support is a release goal, and the fix for this bug is clearly not invasive nor big: $ curl -s 'http://bugs.debian.org/cgi-bin/bugreport.cgi?msg=5;filename=0001-build-for-multiarch.patch;att=1;bug=640499' | diffstat 5 files changed, 15 insertions(+), 8 deletions(-) Where is the problem? What prevents the release team allowing this upload for Wheezy? There is a solution that only involves changes to nvidia-graphics-drivers, waiting for approval: splitting libxvmcnvidia1 from libgl1-nvidia-glx: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=688953 new upstream stable branch release http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=688698 Andreas -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#695327: add README.Debian with pointers
package: cloud-init severity: wishlist x-debbugs-cc: debian-cl...@lists.debian.org Hi Clint, On Freitag, 7. Dezember 2012, Clint Byrum wrote: The functionality I need can probably be done in ~100 lines of sh, plus I really couldnt figure out how to use cloud-init at all, so... here i go. Perhaps I missed where the functionality you want isn't handled by cloud-init? Actually, it seems I missed what cloud-init is useful for. (Also see #695326) So maybe add this to README.Debian, together with other pointers, how to use it such a cloud setup with user-data?! The way to use it without EC2 or OpenStack is documented in doc/sources/nocloud/README Basically, you put meta-data into /var/lib/cloud/seed/nocloud/meta-data. This is described in doc/examples/seed/. This file is where you set things like hostname and install authorized_keys. Then to do further system configuration a cloud-config stanza goes in /var/lib/cloud/seed/nocloud/user-data The capabilities of cloud-config are best discovered in doc/examples/cloud-config.txt Thanks, this was very useful. This idea that all I need is a 100 line shell script makes sense if your focus is narrow, but cloud-init has grown out of the idea that a single generic interface for doing first-boot initialization of a clean image is more useful than many many 100 line shell scripts. of course. cheers, Holger -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#692563: Existing Makefile and OpenEmbedded recipie
I just discovered that there is some work done here: http://gitorious.org/angstrom/openembedded/trees/caa6067f7faf33200681c75843ce2e059cb1c0b4/recipes/librcf but it is for an old version (0.4).
Bug#695328: [testing/wheezy] UEFI installed system fails to boot
Package: installation-reports Boot method: USB memory stick Image version: http://cdimage.debian.org/cdimage/daily-builds/daily/arch-latest/amd64/iso-cd/debian-testing-amd64-netinst.iso dated 2012-12-07T04:21 Date: 2012-12-07T22:00-08:00 Machine: Intel DH77EB motherboard, latest firmware, version 0097 (dated 2012-10-31) Processor: Intel Core i7-3770 Memory: 32 GB Partitions: the installer's use the whole disk default (efi boot partition, ext4 root, swap) Output of lspci -knn (or lspci -nn): (output taken using grml 2012.05) 00:00.0 Host bridge [0600]: Intel Corporation 3rd Gen Core processor DRAM Controller [8086:0150] (rev 09) Subsystem: Intel Corporation Device [8086:2032] Kernel driver in use: agpgart-intel 00:02.0 VGA compatible controller [0300]: Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0162] (rev 09) Subsystem: Intel Corporation Device [8086:2032] Kernel driver in use: i915 00:14.0 USB controller [0c03]: Intel Corporation 7 Series Chipset Family USB xHCI Host Controller [8086:1e31] (rev 04) Subsystem: Intel Corporation Device [8086:2032] Kernel driver in use: xhci_hcd 00:16.0 Communication controller [0780]: Intel Corporation 7 Series Chipset Family MEI Controller #1 [8086:1e3a] (rev 04) Subsystem: Intel Corporation Device [8086:2032] 00:19.0 Ethernet controller [0200]: Intel Corporation 82579V Gigabit Network Connection [8086:1503] (rev 04) Subsystem: Intel Corporation Device [8086:2032] Kernel driver in use: e1000e 00:1a.0 USB controller [0c03]: Intel Corporation 7 Series Chipset Family USB Enhanced Host Controller #2 [8086:1e2d] (rev 04) Subsystem: Intel Corporation Device [8086:2032] Kernel driver in use: ehci_hcd 00:1b.0 Audio device [0403]: Intel Corporation 7 Series Chipset Family High Definition Audio Controller [8086:1e20] (rev 04) Subsystem: Intel Corporation Device [8086:2032] Kernel driver in use: snd_hda_intel 00:1d.0 USB controller [0c03]: Intel Corporation 7 Series Chipset Family USB Enhanced Host Controller #1 [8086:1e26] (rev 04) Subsystem: Intel Corporation Device [8086:2032] Kernel driver in use: ehci_hcd 00:1f.0 ISA bridge [0601]: Intel Corporation H77 Express Chipset LPC Controller [8086:1e4a] (rev 04) Subsystem: Intel Corporation Device [8086:2032] 00:1f.2 SATA controller [0106]: Intel Corporation 7 Series Chipset Family 6-port SATA AHCI Controller [8086:1e02] (rev 04) Subsystem: Intel Corporation Device [8086:2032] Kernel driver in use: ahci 00:1f.3 SMBus [0c05]: Intel Corporation 7 Series Chipset Family SMBus Controller [8086:1e22] (rev 04) Subsystem: Intel Corporation Device [8086:2032] Base System Installation Checklist: [O] = OK, [E] = Error (please elaborate below), [ ] = didn't try it Initial boot: [O] Detect network card:[O] Configure network: [O] Detect CD: [ ] Load installer modules: [O] Detect hard drives: [O] Partition hard drives: [O] Install base system:[O] Clock/timezone setup: [O] User/password setup:[O] Install tasks: [O] Install boot loader:[O] Overall install:[E] Comments/Problems: Installer booted into EFI bootloader, and I used the graphical installer. Installation goes fine, but the resulting system does not boot. The computer acts as if there is no bootable disk (please insert boot disk). Ubuntu 12.10 installs and boots using UEFI fine. I suspect a problem with the EFI NVRAM boot entry that the Debian Installer creates, as reported by efibootmgr. It looked quite different from what Ubuntu created (unfortunately I didn't save the output), but I think the Ubuntu entry had a /boot/efi path in it. The motherboard is set to the default of try EFI booting first, and fall back to legacy BIOS. Booting into rescue mode and running modprobe efivars ; efibootmgr --verbose gives this output: BootCurrent: 0003 Timeout: 1 seconds BootOrder: ,0003,0001,0002 Boot* debianVendor(99e275e7-75a0-4b37-a2e6-c5385e6c00cb,) Boot0001* SATA : PORT 6G 0 : INTEL SSDSC2CW120A3 : PART 0 : Boot Drive BIOS(2,0,00)AMBO Boot0002* USB : 0.00 : PART 0 : Boot Drive BIOS(2,0,00)AMBO Boot0003* UEFI : USB : 0.00 : PART 1 : OS Bootloader ACPI(a0341d0,0)PCI(1d,0)USB(1,0)USB(1,0)HD(2,6f000,380,73bb6f1a)AMBO How can I help debug this further? -- Kenyon Ralph signature.asc Description: Digital signature
Bug#695295: blazeblogger: my variable $head masks earlier declaration in same scope at /usr/bin/blaze-edit line 336.
Hi Joromir On Thu, Dec 06, 2012 at 11:57:42PM +0100, Jaromir Hradilek wrote: On 12/06/2012 07:33 PM, Salvatore Bonaccorso wrote: Package: blazeblogger Version: 1.2.0-3 Severity: minor -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Hi Angel Running blazeblogger 1.2.0-3 in wheezy produces the following e.g on blaze edit, $ blaze edit --help my variable $head masks earlier declaration in same scope at /usr/bin/blaze-edit line 336. Usage: blaze-edit [-fpqCPV] [-b DIRECTORY] [-E EDITOR] ID blaze-edit -h|-v -b, --blogdir DIRECTORY specify a directory in which the BlazeBlogger repository is placed -E, --editor EDITOR specify an external text editor -p, --page edit a page -P, --post edit a blog post -f, --force create an empty source file in case it does not already exist -C, --no-processor disable processing the blog post or page with an external application -q, --quiet do not display unnecessary messages -V, --verbose display all messages -h, --help display this help and exit -v, --version display version information and exit $ Not futher looked at it. [...] Hi Salvatore, Thank you very much for taking the time to report this issue. This is actually fixed upstream in commit ea748e5 (that is, in the development version of the tool). Is there any way I can help with releasing an updated version of the blazeblogger package with this issue fixed? Would it help Debian packagers if I released an upstream bug fix update with this patch applied? Thank you for the fast reply, Jaromir, haven't looked at upstream git if this was already fixed. Regarding an update: We are quite late in the stage of the freeze for the upcoming wheezy release and the Release Team has strengtened the rules for the unblock requests, see [1]. Saying that means, an update would only be allowed if the issue is at least important and would be done via unstable (in this case it's possible). Am I right that blaze edit still works, and only issues this warning? Or ist there something I'm missing right now? [1]: http://release.debian.org/wheezy/freeze_policy.html Regards, Salvatore signature.asc Description: Digital signature
Bug#695329: twms: Please remove python-psyco from Suggests
Source: twms
Version: 0.03e-2
Severity: wishlist
Hi,
python-psyco is not already provided by Debian.
Please remove python-psyco from Suggests.
Best regards,
Nobuhiro
--
Nobuhiro Iwamatsu
iwamatsu at {nigauri.org / debian.org}
GPG ID: 40AD1FA6
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
