Bug#587749: Upstream fixes available
Hi,
How is the status of this bug now?
The version of the upstream package is 0.8.2 and I think it works good.
--
Koichi Akabe
vbkaisetsu at {gmail.com, debian.or.jp}
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#682233: mpt2sas: kernel crash under load with hanged disks
George Shuklin wrote: > I think that problem is specific to LSI drivers, not to linux-raid, > because same tests with Adaptec (aacraid) and few onboard HBAs show > no signs of crashing (hanged disks is just marked as 'failed' and > all systems behave as expected). Thanks. Very useful. [...] > linux-3.0 do have mpt2sas 08.100.00.02 and linux-3.2 do have 10.100.00.00 Between 3.0 and 3.2.12, the mpt2sas driver had 30 patches. That would be an interesting test: could you try a current kernel with the mpt2sas driver from 3.0.y? It works like this: 0. prerequisites: apt-get install git build-essential 1. get the kernel history, if you don't already have it: git clone \ git://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git 2. fetch point releases: cd linux git remote add stable \ git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable.git git fetch stable 3. configure, build, test: git checkout origin/master cp /boot/config-$(uname -r) .config; # current configuration scripts/config --disable DEBUG_INFO make localmodconfig; # optional: minimize configuration make deb-pkg; # optionally with -j for parallel build dpkg -i ../; # as root reboot ... test test test ... Hopefully it reproduces the bug. So 4. try the mpt2sas driver from 3.0.y: cd linux git checkout stable/linux-3.0.y -- drivers/scsi/mpt2sas make deb-pkg; # maybe with -j4 dpkg -i ../ reboot ... test ... Jonathan -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#686524: qemu-kvm: guests won't start until input to console is made
Control: tag 686524 + unreproducible On 03.09.2012 01:58, Timo Weingärtner wrote: [] >> Please try reproducing it without libvirt. Maybe removing -M pc-0.12 >> will help with that. > > Without the libvirt magic it doesn't use 100% CPU but it won't boot either. > > I removed pc-0.12 from libvirt's config, now it uses pc-1.1 and still hangs > until console input. I can't reproduce this problem here. For me, it always starts booting. I tried previous version (1.1.0) and there it works too. What's the "minimal" command line to trigger this? Will it happen with simple kvm -nodefaults -serial file:/tmp/serial -nographics -kernel .. -append console=ttyS0 ? Also, does it happen with different guest kernel (-kernel option) ? Marking as unreproducible for now... Thanks! /mjt -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Processed: Re: Bug#686524: qemu-kvm: guests won't start until input to console is made
Processing control commands: > tag 686524 + unreproducible Bug #686524 [qemu-kvm] qemu-kvm: guests won't start until input to console is made Added tag(s) unreproducible. -- 686524: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=686524 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#685743: marked as done (pax-britannica: broken freedesktop menu file)
Your message dated Mon, 03 Sep 2012 04:02:36 +
with message-id
and subject line Bug#685743: fixed in pax-britannica 1.0.0-2
has caused the Debian Bug report #685743,
regarding pax-britannica: broken freedesktop menu file
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
685743: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=685743
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: pax-britannica
Version: 1.0.0-1
Severity: important
The freedesktop menu file is completely broken, it refers to a file that
does not exist and isn't even related to the package:
guest@morrison:~$ grep Exec /usr/share/applications/pax-britannica.desktop
Exec=/usr/games/fooview
guest@morrison:~$ ls /usr/games/fooview
ls: cannot access /usr/games/fooview: No such file or directory
guest@morrison:~$ apt-file search fooview
guest@morrison:~$
In addition the desktop file is not a valid freedesktop menu file:
guest@morrison:~$ desktop-file-validate
/usr/share/applications/pax-britannica.desktop
/usr/share/applications/pax-britannica.desktop: error: value "Game;ActionGame"
for string list key "Categories" in group "Desktop Entry" does not have a
semicolon (';') as trailing character
--
bye,
pabs
http://wiki.debian.org/PaulWise
signature.asc
Description: This is a digitally signed message part
--- End Message ---
--- Begin Message ---
Source: pax-britannica
Source-Version: 1.0.0-2
We believe that the bug you reported is fixed in the latest version of
pax-britannica, which is due to be installed in the Debian FTP archive.
A summary of the changes between this version and the previous one is
attached.
Thank you for reporting the bug, which will now be closed. If you
have further comments please address them to 685...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Joe Nahmias (supplier of updated pax-britannica package)
(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@debian.org)
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Format: 1.8
Date: Sun, 02 Sep 2012 23:26:33 -0400
Source: pax-britannica
Binary: pax-britannica pax-britannica-data
Architecture: source amd64 all
Version: 1.0.0-2
Distribution: unstable
Urgency: low
Maintainer: Joe Nahmias
Changed-By: Joe Nahmias
Description:
pax-britannica - one-button multi-player real-time strategy game
pax-britannica-data - data files for pax-britannica game
Closes: 685743
Changes:
pax-britannica (1.0.0-2) unstable; urgency=low
.
* fix desktop entry, closes: #685743.
* enhance menu to include icon and hints
Checksums-Sha1:
7b8bac2b91abb5ec77aa4d09e506fa7a418bf0e1 2492 pax-britannica_1.0.0-2.dsc
2542c57f7b1dbab26605e39580abc29b337feb00 52019
pax-britannica_1.0.0-2.debian.tar.gz
ea3c6d8f39616fa80295fb35d1c7f1303834d098 156170
pax-britannica_1.0.0-2_amd64.deb
c00ddd8b82996403017e57ceab1b23cbcaeca39c 8790756
pax-britannica-data_1.0.0-2_all.deb
Checksums-Sha256:
a73d1dff4a2d11dcbd55a6997f9f85e4e60acb36f459e8a100c2d9ed20dc5a28 2492
pax-britannica_1.0.0-2.dsc
b7f1252a4fa25a2bc5372d468573153ece4f322d3e00a695d4e728486e0f7073 52019
pax-britannica_1.0.0-2.debian.tar.gz
303934a60ada516971fb50f4c5b98d8632f52e93020040a7d1c29c47a094c0a5 156170
pax-britannica_1.0.0-2_amd64.deb
b3ddd914557fcdbebcd7f6a442825436ee643f69bcc897ac5b60d927df1dca75 8790756
pax-britannica-data_1.0.0-2_all.deb
Files:
91f8995e49250cf35ab551a52fc8a43d 2492 games optional pax-britannica_1.0.0-2.dsc
2169f16ffa89bc35257021f7aa0df752 52019 games optional
pax-britannica_1.0.0-2.debian.tar.gz
84e5ad1d4cda3383f28799f25ee87f45 156170 games optional
pax-britannica_1.0.0-2_amd64.deb
f619420b6318e5d485fb65b2292592aa 8790756 games optional
pax-britannica-data_1.0.0-2_all.deb
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.12 (GNU/Linux)
iQIcBAEBCAAGBQJQRCiDAAoJELEb2RkHmjuY/VQP/0F6TnqmEw1ncDzcsT0X0zee
z5I0EEGz1a7R7hNj2B8nMhHyXBheZXca9bQRXqrM+1BwwWYwG1r99nV77R5aB0Co
DUNPqQHP1rSW11MQkzyPF7u/8qQ9aXinXTcYhXmAg+qYjQ2oSL15Zs4ORCmj4CGF
XUOd3hdwL6eqqsRN0oQvPtBPKhntKIDggTb2Bnq6557lNJL6ptD1pbId49rbpBSw
Cup6xoZEeX0bnTgCGtxE4hW/9tYXxXURGBnpT88j6L52//qYGrJka61qWXysMumK
JDfkUVMnxSnEQg8kROm4bxt+bcmCGv7Ljy+XHGMxMR9ZiHgVCaw2ibUG0wDL5GSj
olWKFL3XVJuxhRCUUBpF8T+b0YnHNI+VVPx5Wt0kwzyfR2TAVbVanC8/tBtFVrxk
E7/E9NHA/y6CAeJDFgK71Mf15WJwI0VL3/5yqCtSrj3H8HT2nZTQK/oGZ8ujg4DF
uRO84McpxdB7NcBbVHIxs5KYCKTn5B8FmQ9FPODq7SJIIqHQED0Q9D+/YbugAf0z
gEHD3rZ7jRQc5CROFcw7mju8os+D+3zxn9IamiJM0jlnqaE7Irh
Bug#682233: mpt2sas: kernel crash under load with hanged disks
I think that problem is specific to LSI drivers, not to linux-raid, because same tests with Adaptec (aacraid) and few onboard HBAs show no signs of crashing (hanged disks is just marked as 'failed' and all systems behave as expected). I'll try to bisect it at 3.5, but I think it's kinda simple to say where problem is: linux-3.0 do have mpt2sas 08.100.00.02 and linux-3.2 do have 10.100.00.00 And note, that mpt2sas do have strange behavior in linux-2.6.32 (version 02.100.03.00) under highload. On 03.09.2012 06:30, Jonathan Nieder wrote: George Shuklin wrote: We've tested it with vanilla 3.2.12, problem was same. Thanks for the quick feedback. Please send a summary of symptoms to linux-r...@vger.kernel.org, cc-ing Neil Brown and either me or this bug log so we can track it. Be sure to mention: - steps to reproduce, expected result, actual result, and how the difference indicates a bug (should be simple enough --- the summary you sent here would work fine) - which kernel versions you have tested and what happened with each - full "dmesg" output from booting and reproducing the bug, as an attachment - any other weird symptoms or observations - what you would be able to do to track it down (can you run commands if provided? try patches? bisect to find which commit introduced the regression?) If we're lucky, the symptoms will ring a bell for Neil or someone else on-list or someone will have an idea for a test to try to track it down further. Otherwise, the best we can do is probably to bisect to find which specific change introduced the bug, as described at [1]. Regards, Jonathan [1] http://kernel-handbook.alioth.debian.org/ch-bugs.html#s9.2.1 -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#682233: mpt2sas: kernel crash under load with hanged disks
George Shuklin wrote: > We've tested it with vanilla 3.2.12, problem was same. Thanks for the quick feedback. Please send a summary of symptoms to linux-r...@vger.kernel.org, cc-ing Neil Brown and either me or this bug log so we can track it. Be sure to mention: - steps to reproduce, expected result, actual result, and how the difference indicates a bug (should be simple enough --- the summary you sent here would work fine) - which kernel versions you have tested and what happened with each - full "dmesg" output from booting and reproducing the bug, as an attachment - any other weird symptoms or observations - what you would be able to do to track it down (can you run commands if provided? try patches? bisect to find which commit introduced the regression?) If we're lucky, the symptoms will ring a bell for Neil or someone else on-list or someone will have an idea for a test to try to track it down further. Otherwise, the best we can do is probably to bisect to find which specific change introduced the bug, as described at [1]. Regards, Jonathan [1] http://kernel-handbook.alioth.debian.org/ch-bugs.html#s9.2.1 -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Processed: Re: mpt2sas: kernel crash under load with hanged disks
Processing commands for cont...@bugs.debian.org: > # upstream 3.2.12 actually, but close enough > found 682233 linux-2.6/3.2.12-1 Bug #682233 [src:linux] mpt2sas: kernel crash under load with hanged disks Marked as found in versions linux-2.6/3.2.12-1. > End of message, stopping processing here. Please contact me if you need assistance. -- 682233: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=682233 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#682233: mpt2sas: kernel crash under load with hanged disks
We've tested it with vanilla 3.2.12, problem was same. On 03.09.2012 06:01, Jonathan Nieder wrote: Hi George, George Shuklin wrote: Tags: upstream Which upstream version did you test? [...] That bug found in 3.2 and 3.3 versions of kernel, but not reproducing in 3.0. [...] 1) Set up large raid10. 2) Start it rebuild 3) run addition io on raid (dd if=/dev/md0 of=/dev/md0) 4) Somehow make to slow down IO on two or more disks. We found that bug in wild with normal load, but following scripts allows to see it in few minutes: [...] end_request: I/O error, dev sdf, sector 729088 [ cut here ] kernel BUG at [...]/linux-3.4.4/drivers/scsi/scsi_lib.c:1154! [...] Pid: 343, comm: kworker/5:1 Not tainted 3.4-trunk-amd64 #1 Supermicro X8DTN+-F/X8DTN+-F [...] Call Trace: [] ? sd_prep_fn+0x2e9/0xb8e [sd_mod] [] ? cfq_dispatch_requests+0x722/0x880 [] ? create_io_context+0x5a/0x5a [] ? blk_peek_request+0xcf/0x1ac [...] Code: 85 c0 74 1d 48 8b 00 48 85 c0 74 15 48 8b 40 48 48 85 c0 74 0c 48 89 ee 48 89 df ff d0 85 c0 75 44 66 83 bd e0 00 00 00 00 75 02<0f> 0b 48 89 ee 48 89 df e8 62 ec ff ff 48 85 c0 48 89 c2 74 20 RIP [] scsi_setup_fs_cmnd+0x45/0x83 [scsi_mod] Thanks for a clear report, and sorry for the slow reply. This is "BUG_ON(!req->nr_phys_segments)". Smells similar to [1], which bisected to v3.1-rc1~131^2~31 and was fixed by v3.2.2~91 (md/raid1: perform bad-block tests for WriteMostly devices too, 2012-01-09), aka v3.3-rc3~3^2~2. But that wouldn't explain triggering the same trace in a 3.4.y kernel. Is this reproducible with 3.5.2 or newer from experimental? Which 3.2.y kernel did you use to experience it? Curious, Jonathan [1] http://thread.gmane.org/gmane.linux.raid/36732 -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#682233: mpt2sas: kernel crash under load with hanged disks
Hi George, George Shuklin wrote: > Tags: upstream Which upstream version did you test? [...] > That bug found in 3.2 and 3.3 versions of kernel, but not > reproducing in 3.0. [...] > 1) Set up large raid10. > 2) Start it rebuild > 3) run addition io on raid (dd if=/dev/md0 of=/dev/md0) > 4) Somehow make to slow down IO on two or more disks. We found that > bug in wild with normal load, but following scripts allows to see it > in few minutes: [...] > end_request: I/O error, dev sdf, sector 729088 > [ cut here ] > kernel BUG at [...]/linux-3.4.4/drivers/scsi/scsi_lib.c:1154! [...] > Pid: 343, comm: kworker/5:1 Not tainted 3.4-trunk-amd64 #1 Supermicro > X8DTN+-F/X8DTN+-F [...] > Call Trace: > [] ? sd_prep_fn+0x2e9/0xb8e [sd_mod] > [] ? cfq_dispatch_requests+0x722/0x880 > [] ? create_io_context+0x5a/0x5a > [] ? blk_peek_request+0xcf/0x1ac [...] > Code: 85 c0 74 1d 48 8b 00 48 85 c0 74 15 48 8b 40 48 48 85 c0 74 0c 48 89 ee > 48 89 df ff d0 85 c0 75 44 66 83 bd e0 00 00 00 00 75 02 <0f> 0b 48 89 ee 48 > 89 df e8 62 ec ff ff 48 85 c0 48 89 c2 74 20 > RIP [] scsi_setup_fs_cmnd+0x45/0x83 [scsi_mod] Thanks for a clear report, and sorry for the slow reply. This is "BUG_ON(!req->nr_phys_segments)". Smells similar to [1], which bisected to v3.1-rc1~131^2~31 and was fixed by v3.2.2~91 (md/raid1: perform bad-block tests for WriteMostly devices too, 2012-01-09), aka v3.3-rc3~3^2~2. But that wouldn't explain triggering the same trace in a 3.4.y kernel. Is this reproducible with 3.5.2 or newer from experimental? Which 3.2.y kernel did you use to experience it? Curious, Jonathan [1] http://thread.gmane.org/gmane.linux.raid/36732 -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#686356: aspcud and clasp 2.1
On Sat, Sep 01, 2012 at 01:17:12PM +0200, Roland Kaminski wrote: > In fact this is trivial. It is just an option that has slightly changed and > is > no longer recognized by clasp-2.1. Thanks a lot for the patch! > Benjamin takes the version numbering > seriously: if the minor or major version changes, then there might be changes > that break backwards compatibility. This is a very good practice! > Btw. our latest competition submission should (hopefully) be much better than > the old aspcud and I guess we can drop clasp 2.0 support then. yes, newer versions of aspcud would go into sid, and there we will have clasp 2.1, so the support for clasp 2.0 will be no longer needed then. Thanks -Ralf. -- Ralf Treinen Laboratoire Preuves, Programmes et Systèmes Université Paris Diderot, Paris, France. http://www.pps.univ-paris-diderot.fr/~treinen/ => New email address: trei...@pps.univ-paris-diderot.fr <= -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#686543: netcat.c:1797:16: error: expected ')' before 'DEBIAN_VERSION'
Package: netcat-traditional Version: 1.10-40 Severity: serious Justification: fails to build from source (but built successfully in the past) The source package `netcat-traditional' does not build, make dies this way: $ make linux make -e nc XFLAGS='-DLINUX' STATIC=-static make[1]: Entering directory `/tmp/build/netcat-1.10' gcc -O -DLINUX -static -o nc netcat.c netcat.c: In function 'helpme': netcat.c:1797:16: error: expected ')' before 'DEBIAN_VERSION' make[1]: *** [nc] Error 1 make[1]: Leaving directory `/tmp/build/netcat-1.10' make: *** [linux] Error 2 I am not very familiar with the Debian package build process. In debian/rules a DFLAGS='... -DDEBIAN_VERSION...' is used, if I try that one, the error ist the same: $ make linux DFLAGS='-DDEBIAN_VERSION="foo"' ... netcat.c: In function 'helpme': netcat.c:1783:3: error: expected ')' before 'foo' ... So maybe DEBIAN_VERSION usually contains some magic to concatenate the strings with the constant (rather not), or this patch is broken. Cheers, Tech -- System Information: Debian Release: wheezy/sid APT prefers testing APT policy: (500, 'testing') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.2.0-3-amd64 (SMP w/4 CPU cores) Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=ANSI_X3.4-1968) (ignored: LC_ALL set to C) Shell: /bin/sh linked to /bin/dash Versions of packages netcat-traditional depends on: ii libc6 2.13-35 netcat-traditional recommends no packages. netcat-traditional suggests no packages. -- no debconf information -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#686524: qemu-kvm: guests won't start until input to console is made
Hallo Michael Tokarev, 2012-09-02 um 20:55:36 schriebst Du: > Control: tag 686524 + moreinfo > > On 02.09.2012 22:34, Timo Weingärtner wrote: > > Package: qemu-kvm > > Version: 1.1.1+dfsg-1 > > Severity: grave > > Justification: renders package unusable > > Well, it is usable for lots of people. > > > After starting the guest with "virsh start router" the kvm process uses > > 100% CPU. In "virsh console router" nothing happens until I press enter, > > then the guest starts booting. "echo > /dev/pts/$number" also works > > here. > > > > When bootet the guest's clock is behind by the time between the "virsh > > start" and the input to the guest's console. > > How this bug is different from #685314 and #680719 (which is the same > thing)? Note both are fixed in the version you're reporting this bug > against, and verified. I'm not saying it is the same bug and it is > fixed, I'm trying to understand how your is different. > > > kvm command (libvirt-generated): > Please try reproducing it without libvirt. Maybe removing -M pc-0.12 > will help with that. Without the libvirt magic it doesn't use 100% CPU but it won't boot either. I removed pc-0.12 from libvirt's config, now it uses pc-1.1 and still hangs until console input. Grüße Timo signature.asc Description: This is a digitally signed message part.
Processed: fparser will be removed
Processing commands for cont...@bugs.debian.org: > tags 683021 - help Bug #683021 [src:fparser] FTBFS on arm*: multiple definition of `typeinfo for FunctionParserBase::FunctionWrapper' Removed tag(s) help. > thanks Stopping processing here. Please contact me if you need assistance. -- 683021: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=683021 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#682905: can't import signatures
Some further observations. I tried running strace against the icedove
process
This is what I see after clicking `Import OpenPGP signature'
Notice that between the open() and close(), there is no write operation?
access("/tmp", W_OK)= 0
open("/tmp/0x6C6580E77BD756C4.3.signed-by-0xD929F2992BEF0A33",
O_WRONLY|O_CREAT|O_EXCL|O_TRUNC, 0600) = 68
close(68) = 0
poll([{fd=5, events=POLLIN|POLLOUT}], 1, -1) = 1 ([{fd=5,
revents=POLLIN|POLLOUT}])
I've also referred to the icedove troubleshooting wiki
http://wiki.debian.org/Icedove#Debugging
but running in debug mode didn't reveal anything else about the problem.
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#682905: can't import signatures from caff
Hi, People are sending me signatures with caff and I can't import them Enigmail prompts for my password and decrypts the messages OK When I click the attachment, right click, and select "Import OpenPGP key" I just get the error "key importing failed" and "No valid armored OpenPGP data block found" In the mail window, it says that the attachment is 2.3KB If I right click the attachment and save it, a file is created with about 2.3KB of OpenPGP data in it. All the debug logs have already been sent in a Debian bug report - can anyone comment on this or suggesting anything else I can try? http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=682905 Regards, Daniel -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Processed: Re: Bug#674324: ruby-net-sftp: FTBFS: test failed
Processing commands for cont...@bugs.debian.org: > forwarded 674324 > http://net-ssh.lighthouseapp.com/projects/36253-net-ssh/tickets/62-net-sftp-fails-with-mocha-0113 Bug #674324 [src:ruby-net-sftp] ruby-net-sftp: FTBFS: test failed Set Bug forwarded-to-address to 'http://net-ssh.lighthouseapp.com/projects/36253-net-ssh/tickets/62-net-sftp-fails-with-mocha-0113'. > thanks Stopping processing here. Please contact me if you need assistance. -- 674324: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=674324 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#674324: ruby-net-sftp: FTBFS: test failed
forwarded 674324 http://net-ssh.lighthouseapp.com/projects/36253-net-ssh/tickets/62-net-sftp-fails-with-mocha-0113 thanks On 01/09/12 at 10:20 +0200, Emanuele Rocca wrote: > It looks like the changes introduced in recent upstream versions of > ruby-mocha are breaking ruby-net-sftp's tests. Indeed. It fails with ruby-mocha 0.11.3, but works with 0.10.3 and 0.10.5. I'm not very familiar with ruby-mocha, so I don't know if the package is actually doing something wrong. Could someone in debian-ruby@ take a closer look? I've fowarded the bug upstream (to net-sftp) in the meantime. Lucas -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#657751: gdm3: 657751: patch to fix purging when gdm3 is running
Hi Looking at wheezy bugs to be fixed I stumbled over #657751 in gdm3. Sergio, are you able to repoduce this with current version in wheezy? I tried to reproduce this via an installation in a VM, login in a user and then purging gdm3. The removal went without the problems described. [But anyway, Paul already did an analysis which in any case (even not triggered here) should further 'stabilize' the possible purge process for gdm3.] Thoughts? Regards, Salvatore signature.asc Description: Digital signature
Processed: Re: Processed: fixed 686524 in 1.0+dfsg-11
Processing commands for cont...@bugs.debian.org: > notfixed 686524 1.0+dfsg-11 Bug #686524 [qemu-kvm] qemu-kvm: guests won't start until input to console is made No longer marked as fixed in versions qemu-kvm/1.0+dfsg-11. > notfound 686524 1.0+dfsg-11 Bug #686524 [qemu-kvm] qemu-kvm: guests won't start until input to console is made Ignoring request to alter found versions of bug #686524 to the same values previously set > thanks Stopping processing here. Please contact me if you need assistance. -- 686524: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=686524 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Processed: fixed 686524 in 1.0+dfsg-11
Processing commands for cont...@bugs.debian.org: > fixed 686524 1.0+dfsg-11 Bug #686524 [qemu-kvm] qemu-kvm: guests won't start until input to console is made Marked as fixed in versions qemu-kvm/1.0+dfsg-11. > thanks Stopping processing here. Please contact me if you need assistance. -- 686524: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=686524 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Processed: Re: Bug#686524: qemu-kvm: guests won't start until input to console is made
Processing control commands: > tag 686524 + moreinfo Bug #686524 [qemu-kvm] qemu-kvm: guests won't start until input to console is made Added tag(s) moreinfo. -- 686524: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=686524 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#686524: qemu-kvm: guests won't start until input to console is made
Control: tag 686524 + moreinfo On 02.09.2012 22:34, Timo Weingärtner wrote: > Package: qemu-kvm > Version: 1.1.1+dfsg-1 > Severity: grave > Justification: renders package unusable Well, it is usable for lots of people. > After starting the guest with "virsh start router" the kvm process uses > 100% CPU. In "virsh console router" nothing happens until I press enter, > then the guest starts booting. "echo > /dev/pts/$number" also works > here. > > When bootet the guest's clock is behind by the time between the "virsh > start" and the input to the guest's console. How this bug is different from #685314 and #680719 (which is the same thing)? Note both are fixed in the version you're reporting this bug against, and verified. I'm not saying it is the same bug and it is fixed, I'm trying to understand how your is different. > kvm command (libvirt-generated): > /usr/bin/kvm -S -M pc-0.12 -enable-kvm -m 128 -smp > 1,sockets=1,cores=1,threads=1 -name router -uuid > d24ccdfa-201a-eda6-65e7-43b0b29c94ba -nographic -nodefconfig -nodefaults > -chardev > socket,id=charmonitor,path=/var/lib/libvirt/qemu/router.monitor,server,nowait > -mon chardev=charmonitor,id=monitor,mode=control -rtc base=utc -no-shutdown > -kernel /boot/kvm-router/vmlinuz -append root=/dev/vda ro console=ttyS0 > -device piix3-usb-uhci,id=usb,bus=pci.0,addr=0x1.0x2 -drive > file=/dev/vg/vm_router_root,if=none,id=drive-virtio-disk0,format=raw -device > virtio-blk-pci,scsi=off,bus=pci.0,addr=0x4,drive=drive-virtio-disk0,id=virtio-disk0,bootindex=1 > -drive file=/dev/vg/vm_router_swap,if=none,id=drive-virtio-disk1,format=raw > -device > virtio-blk-pci,scsi=off,bus=pci.0,addr=0x5,drive=drive-virtio-disk1,id=virtio-disk1 > -netdev tap,ifname=vm_router,script=/bin/true,id=hostnet0 -device > virtio-net-pci,netdev=hostnet0,id=net0,mac=02:84:00:00:00:01,bus=pci.0,addr=0x3 > -chardev pty,id=charserial0 -device isa-s e > rial,chardev=charserial0,id=serial0 -device > i6300esb,id=watchdog0,bus=pci.0,addr=0x7 -watchdog-action reset -device > virtio-balloon-pci,id=balloon0,bus=pci.0,addr=0x6 Please try reproducing it without libvirt. Maybe removing -M pc-0.12 will help with that. Thanks, /mjt -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Processed: found 686524 in 1.1.0+dfsg-3, notfound 686524 in 1.0+dfsg-11
Processing commands for cont...@bugs.debian.org: > found 686524 1.1.0+dfsg-3 Bug #686524 [qemu-kvm] qemu-kvm: guests won't start until input to console is made Marked as found in versions qemu-kvm/1.1.0+dfsg-3. > notfound 686524 1.0+dfsg-11 Bug #686524 [qemu-kvm] qemu-kvm: guests won't start until input to console is made Ignoring request to alter found versions of bug #686524 to the same values previously set > thanks Stopping processing here. Please contact me if you need assistance. -- 686524: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=686524 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#686524: qemu-kvm: guests won't start until input to console is made
Package: qemu-kvm Version: 1.1.1+dfsg-1 Severity: grave Justification: renders package unusable After starting the guest with "virsh start router" the kvm process uses 100% CPU. In "virsh console router" nothing happens until I press enter, then the guest starts booting. "echo > /dev/pts/$number" also works here. When bootet the guest's clock is behind by the time between the "virsh start" and the input to the guest's console. kvm command (libvirt-generated): /usr/bin/kvm -S -M pc-0.12 -enable-kvm -m 128 -smp 1,sockets=1,cores=1,threads=1 -name router -uuid d24ccdfa-201a-eda6-65e7-43b0b29c94ba -nographic -nodefconfig -nodefaults -chardev socket,id=charmonitor,path=/var/lib/libvirt/qemu/router.monitor,server,nowait -mon chardev=charmonitor,id=monitor,mode=control -rtc base=utc -no-shutdown -kernel /boot/kvm-router/vmlinuz -append root=/dev/vda ro console=ttyS0 -device piix3-usb-uhci,id=usb,bus=pci.0,addr=0x1.0x2 -drive file=/dev/vg/vm_router_root,if=none,id=drive-virtio-disk0,format=raw -device virtio-blk-pci,scsi=off,bus=pci.0,addr=0x4,drive=drive-virtio-disk0,id=virtio-disk0,bootindex=1 -drive file=/dev/vg/vm_router_swap,if=none,id=drive-virtio-disk1,format=raw -device virtio-blk-pci,scsi=off,bus=pci.0,addr=0x5,drive=drive-virtio-disk1,id=virtio-disk1 -netdev tap,ifname=vm_router,script=/bin/true,id=hostnet0 -device virtio-net-pci,netdev=hostnet0,id=net0,mac=02:84:00:00:00:01,bus=pci.0,addr=0x3 -chardev pty,id=charserial0 -devic e isa-serial,chardev=charserial0,id=serial0 -device i6300esb,id=watchdog0,bus=pci.0,addr=0x7 -watchdog-action reset -device virtio-balloon-pci,id=balloon0,bus=pci.0,addr=0x6 -- Package-specific info: /proc/cpuinfo: processor : 0 vendor_id : AuthenticAMD cpu family : 15 model : 75 model name : AMD Athlon(tm) 64 X2 Dual Core Processor 4200+ stepping: 2 microcode : 0x62 cpu MHz : 1000.000 cache size : 512 KB physical id : 0 siblings: 2 core id : 0 cpu cores : 2 apicid : 0 initial apicid : 0 fpu : yes fpu_exception : yes cpuid level : 1 wp : yes flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush mmx fxsr sse sse2 ht syscall nx mmxext fxsr_opt rdtscp lm 3dnowext 3dnow rep_good nopl extd_apicid pni cx16 lahf_lm cmp_legacy svm extapic cr8_legacy bogomips: 2009.37 TLB size: 1024 4K pages clflush size: 64 cache_alignment : 64 address sizes : 40 bits physical, 48 bits virtual power management: ts fid vid ttp tm stc processor : 1 vendor_id : AuthenticAMD cpu family : 15 model : 75 model name : AMD Athlon(tm) 64 X2 Dual Core Processor 4200+ stepping: 2 microcode : 0x62 cpu MHz : 1000.000 cache size : 512 KB physical id : 0 siblings: 2 core id : 1 cpu cores : 2 apicid : 1 initial apicid : 1 fpu : yes fpu_exception : yes cpuid level : 1 wp : yes flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush mmx fxsr sse sse2 ht syscall nx mmxext fxsr_opt rdtscp lm 3dnowext 3dnow rep_good nopl extd_apicid pni cx16 lahf_lm cmp_legacy svm extapic cr8_legacy bogomips: 2009.37 TLB size: 1024 4K pages clflush size: 64 cache_alignment : 64 address sizes : 40 bits physical, 48 bits virtual power management: ts fid vid ttp tm stc -- System Information: Debian Release: wheezy/sid APT prefers testing APT policy: (890, 'testing'), (880, 'unstable') Architecture: amd64 (x86_64) Kernel: Linux 3.2.0-3-amd64 (SMP w/2 CPU cores) Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages qemu-kvm depends on: ii adduser 3.113+nmu3 ii ipxe-qemu 1.0.0+git-20120202.f6840ba-3 ii libaio1 0.3.109-3 ii libasound2 1.0.25-4 ii libbluetooth3 4.99-2 ii libbrlapi0.54.4-4 ii libc6 2.13-35 ii libcurl3-gnutls 7.26.0-1 ii libglib2.0-02.32.3-1 ii libgnutls26 2.12.20-1 ii libiscsi1 1.4.0-3 ii libjpeg88d-1 ii libncurses5 5.9-10 ii libpng12-0 1.2.49-1 ii libpulse0 2.0-6 ii libsasl2-2 2.1.25.dfsg1-5 ii libsdl1.2debian 1.2.15-5 ii libspice-server10.11.0-1 ii libtinfo5 5.9-10 ii libusbredirparser0 0.4.3-2 ii libuuid12.20.1-5.1 ii libvdeplug2 2.3.2-4 ii libx11-62:1.5.0-1 ii python 2.7.3~rc2-1 ii qemu-keymaps1.1.0+dfsg-1 ii qemu-utils 1.1.0+dfsg-1 ii seabios 1.7.0-1 ii vgabios 0.7a-3 ii zlib1g 1:1.2.7.dfsg-13 Versions of packages qemu-kvm recommends: ii bridge-utils 1.5-4 ii iproute 20120521-3 Versions of packages qemu-kvm suggests: pn debootstrap ii samba
Bug#646537: marked as done (slbackup-php: please test your package with smarty3)
Your message dated Sun, 02 Sep 2012 17:33:20 + with message-id and subject line Bug#646537: fixed in slbackup-php 0.4.3-2 has caused the Debian Bug report #646537, regarding slbackup-php: please test your package with smarty3 to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 646537: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=646537 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: slbackup-php Severity: minor Dear Maintainer, Smarty and Smarty3 will be merged soon, please consider to test your package with the 3.x series. Thank you. Cheers, --- End Message --- --- Begin Message --- Source: slbackup-php Source-Version: 0.4.3-2 We believe that the bug you reported is fixed in the latest version of slbackup-php, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 646...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Mike Gabriel (supplier of updated slbackup-php package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Sat, 01 Sep 2012 21:54:58 +0200 Source: slbackup-php Binary: slbackup-php Architecture: source all Version: 0.4.3-2 Distribution: unstable Urgency: low Maintainer: Debian Edu Packaging Team Changed-By: Mike Gabriel Description: slbackup-php - Web-based administration tool for slbackup Closes: 646537 670095 Changes: slbackup-php (0.4.3-2) unstable; urgency=low . * Rebuild package based on Debian version 0.3-3, only cherry-picking minimal changes from Debian version 0.4.3-1 of this package, as requested by the Debian release team. This reduction of changes is to make a transition of slbackup-php 0.4.3 into wheezy possible. * Drop of complete patch series which was needed for 0.3-3. * Cherry-picks from 0.4.3-1: + New maintainer, package becomes team-maintained: Debian Edu Packaging Team. + New upstream version. (Closes: #646537, #670095) + Run debconf-updatepo during /debian/rules build, not clean. Makes slbackup-php buildable with git-buildpackage. + Let URL in /debian/slbackup-php.desktop point to http://localhost/slbackup-php. Checksums-Sha1: 020e4c67a64796426683ef76816660fdec2a93b3 1934 slbackup-php_0.4.3-2.dsc 8c6152b9df252c8748b8956d886e1d996c8a816c 3529 slbackup-php_0.4.3-2.diff.gz d18534058f195be4a56d448f01fe0d01d2481464 25720 slbackup-php_0.4.3-2_all.deb Checksums-Sha256: 0c0b86471c28d2ecb8c5391efbc152637fe1deecafed490b92f424f9956e262f 1934 slbackup-php_0.4.3-2.dsc 3ff162ec0a670277092270fdc12dd2ee28a9994e7035e77f9bc2c74c8f52b500 3529 slbackup-php_0.4.3-2.diff.gz 82c1a7e8234a879d8ab960cc39f102c0ab54aa0a65fc1df019b1ae9278ffcf05 25720 slbackup-php_0.4.3-2_all.deb Files: 50a123db8a6db9c65ecda3a907051c77 1934 misc optional slbackup-php_0.4.3-2.dsc f37e1858b89349330e5ab5d1a252d4fe 3529 misc optional slbackup-php_0.4.3-2.diff.gz 4020a559d69e0d5942ba1cfab855d32a 25720 misc optional slbackup-php_0.4.3-2_all.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.12 (GNU/Linux) iQIcBAEBCAAGBQJQQ5XvAAoJEKtkX0BihqfQv5MQALYrGcGrLcAIKbASasM4GGE3 bLWGtcxaJFCxvkV4VS6zdsU4PgpYa/+Hb/mjvsCgxdENUQ8QIs6VUcUajmPNVmAO cXwWYxrP4tWoTqks4QngdqY/JqgutxJ9QKzqTs48HrsfLZdPL65pp9katDROI6fH JOMMrv1jWQQ7q7J2gA+MPmjKFWVcdc3Yfg49ofi20kCQBs1pAbbqPwoKDTaQipcq aBxJFvmd6LPXY1Jbt/jBsW/bsjzXrhOIDid6NL7cfn2b5goAG6e9FCwZmVBDgemJ OqezOOSEC9I8b2Y6FrX3wq8khZW5zcCtbqjsjABKr29udBrYc6TF11xfJMMtvHU9 YbxmcSy0YWDCaS7UjzKSSwK7eAV3RMkyUrCMTjgcHrdOwzQjStAyEYNlxpYckSdK UhBpdKRLmrPRBLS6WMaQ6UlZZxcpdwPv84sgM7cl/sxrLuFUwNa6nrlKPHXcU1qS cngQl0bFhqaU9U/291i4cqrU3XuM+Y4hcHDaCYEFBTx4VXW3kMn8AEK6o3/2zwK5 E+RfnZU4hSATQNAAM7zzl7WS4ted2ghdMzl/pJGhfMUhyS9pj1MdqG7dTP5v5n5T +wvYBeZwXzJGND0xmJxt0AGavGmIl6uICCI+s2G6isQUI0dEsp8soYV10e8RizaQ C0TlzZTfWfhBxOqjTqiN =dEN4 -END PGP SIGNATURE End Message ---
Processed: retitle
Processing commands for cont...@bugs.debian.org: > retitle 686330 mediawiki: Multiple security issues > CVE-2012-4377,CVE-2012-4378,CVE-2012-4379,CVE-2012-4380,CVE-2012-4381,CVE-2012-4382 Bug #686330 [mediawiki] mediawiki: Multiple security issues Changed Bug title to 'mediawiki: Multiple security issues CVE-2012-4377,CVE-2012-4378,CVE-2012-4379,CVE-2012-4380,CVE-2012-4381,CVE-2012-4382' from 'mediawiki: Multiple security issues' > End of message, stopping processing here. Please contact me if you need assistance. -- 686330: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=686330 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Processed: your mail
Processing commands for cont...@bugs.debian.org: > affects 686085 imagemagick Bug #686085 [graphicsmagick] FTBS imagemagick build on sparc Added indication that 686085 affects imagemagick > thanks Stopping processing here. Please contact me if you need assistance. -- 686085: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=686085 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#685581: inn: CVE-2012-3523 prone to STARTTLS plaintext command injection
Hi Marco, Or does it mean that a security release should be made for previous versions still maintained by the Debian project? It should be, yes. (At least, if you think that it should be fixed.) I do not believe taking time to fix it on older versions of INN is worthwhile. Not much harm can be done in NNTP when this security hole is exploited. Usually, authentication and/or host checks are required for sensitive newsgroups. (Also note that once a user has been authenticated, STARTTLS is no longer available.) If other people think this vulnerability can be harmful, please speak up! -- Julien ÉLIE « – Nous parlerons quand l'interprète dormira. [Bong !] – Il dort. On peut parler. » (Astérix) -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#680846: marked as done (ruby-compass: FTBFS: ERROR: Test "require-rubygems" failed. Exiting.)
Your message dated Sun, 02 Sep 2012 13:32:42 + with message-id and subject line Bug#680846: fixed in ruby-compass 0.12.2~dfsg-2 has caused the Debian Bug report #680846, regarding ruby-compass: FTBFS: ERROR: Test "require-rubygems" failed. Exiting. to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 680846: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=680846 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: ruby-compass Version: 0.12.2~dfsg-1 Severity: serious Tags: wheezy sid User: debian...@lists.debian.org Usertags: qa-ftbfs-20120708 qa-ftbfs Justification: FTBFS on amd64 Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part: > fakeroot debian/rules binary > test -x debian/rules > dh_testroot > dh_prep > dh_installdirs -A > mkdir -p "." > dh_ruby --configure > /usr/lib/ruby/vendor_ruby/gem2deb.rb:17: warning: setting > Encoding.default_external > touch debian/stamp-ruby-gem-configure > dh_ruby --build > /usr/lib/ruby/vendor_ruby/gem2deb.rb:17: warning: setting > Encoding.default_external > touch debian/stamp-ruby-gem-build > dh_ruby --install > /usr/lib/ruby/vendor_ruby/gem2deb.rb:17: warning: setting > Encoding.default_external > Entering dh_ruby --install > install -d /«PKGBUILDDIR»/debian/ruby-compass/usr/bin > install -D -m755 bin/compass > /«PKGBUILDDIR»/debian/ruby-compass/usr/bin/compass > install -d /«PKGBUILDDIR»/debian/ruby-compass/usr/lib/ruby/vendor_ruby > install -D -m644 lib/compass.rb > /«PKGBUILDDIR»/debian/ruby-compass/usr/lib/ruby/vendor_ruby/compass.rb > install -D -m644 lib/compass/frameworks.rb > /«PKGBUILDDIR»/debian/ruby-compass/usr/lib/ruby/vendor_ruby/compass/frameworks.rb > install -D -m644 lib/compass/dependencies.rb > /«PKGBUILDDIR»/debian/ruby-compass/usr/lib/ruby/vendor_ruby/compass/dependencies.rb > install -D -m644 lib/compass/validator.rb > /«PKGBUILDDIR»/debian/ruby-compass/usr/lib/ruby/vendor_ruby/compass/validator.rb > install -D -m644 lib/compass/version.rb > /«PKGBUILDDIR»/debian/ruby-compass/usr/lib/ruby/vendor_ruby/compass/version.rb > install -D -m644 lib/compass/installers/bare_installer.rb > /«PKGBUILDDIR»/debian/ruby-compass/usr/lib/ruby/vendor_ruby/compass/installers/bare_installer.rb > install -D -m644 lib/compass/installers/manifest.rb > /«PKGBUILDDIR»/debian/ruby-compass/usr/lib/ruby/vendor_ruby/compass/installers/manifest.rb > install -D -m644 lib/compass/installers/manifest_installer.rb > /«PKGBUILDDIR»/debian/ruby-compass/usr/lib/ruby/vendor_ruby/compass/installers/manifest_installer.rb > install -D -m644 lib/compass/installers/template_context.rb > /«PKGBUILDDIR»/debian/ruby-compass/usr/lib/ruby/vendor_ruby/compass/installers/template_context.rb > install -D -m644 lib/compass/installers/base.rb > /«PKGBUILDDIR»/debian/ruby-compass/usr/lib/ruby/vendor_ruby/compass/installers/base.rb > install -D -m644 lib/compass/exec/project_options_parser.rb > /«PKGBUILDDIR»/debian/ruby-compass/usr/lib/ruby/vendor_ruby/compass/exec/project_options_parser.rb > install -D -m644 lib/compass/exec/global_options_parser.rb > /«PKGBUILDDIR»/debian/ruby-compass/usr/lib/ruby/vendor_ruby/compass/exec/global_options_parser.rb > install -D -m644 lib/compass/exec/switch_ui.rb > /«PKGBUILDDIR»/debian/ruby-compass/usr/lib/ruby/vendor_ruby/compass/exec/switch_ui.rb > install -D -m644 lib/compass/exec/sub_command_ui.rb > /«PKGBUILDDIR»/debian/ruby-compass/usr/lib/ruby/vendor_ruby/compass/exec/sub_command_ui.rb > install -D -m644 lib/compass/exec/command_option_parser.rb > /«PKGBUILDDIR»/debian/ruby-compass/usr/lib/ruby/vendor_ruby/compass/exec/command_option_parser.rb > install -D -m644 lib/compass/exec/helpers.rb > /«PKGBUILDDIR»/debian/ruby-compass/usr/lib/ruby/vendor_ruby/compass/exec/helpers.rb > install -D -m644 lib/compass/sprite_importer.rb > /«PKGBUILDDIR»/debian/ruby-compass/usr/lib/ruby/vendor_ruby/compass/sprite_importer.rb > install -D -m644 lib/compass/configuration/data.rb > /«PKGBUILDDIR»/debian/ruby-compass/usr/lib/ruby/vendor_ruby/compass/configuration/data.rb > install -D -m644 lib/compass/configuration/file_data.rb > /«PKGBUILDDIR»/debian/ruby-compass/usr/lib/ruby/vendor_ruby/compass/configuration/file_data.rb > install -D -m644 lib/compass/configuration/adapters.rb > /«PKGBUILDDIR»/debian/ruby-compass/usr/lib/ruby/vendor_ruby/compass/configuration/adapters.rb > install -D -m644 lib/compass/configuration/serialization.rb > /«PKGBUILDDIR»/debian/ruby-compass/usr/lib/ruby/vendor_ruby/compass/configuration/serialization.rb > install -D -m644 lib/compass/configur
Bug#679409: lightdm: Fails to start on boot, invoke-rc.d lightdm start fails
On dim., 2012-08-19 at 12:53 -0700, Steve Langasek wrote: > None of the above. It's a bug in lightdm, for shipping an upstart job with > no start condition. I have no idea why this is done; the upstart job used > in Ubuntu for lightdm doesn't look anything like this. > > Now, there's a good chance that "fixing" the lightdm upstart job to have a > correct start condition still won't work, because several of the > prerequisite events are not yet available at start time with the upstart in > Debian. I'm planning to fix this ASAP for wheezy, having spoken with Neil > McGovern at DebConf and gotten provisional release team sign-off, but it's > not absolutely certain this will go in or when. In the meantime, I believe > the correct fix is for the lightdm package to drop its upstart job. Note that the upstart job is the upstream one, untouched, afaict. I can do the removal (pending RT upload) if it's the best way to do fix the bug. Regards, -- Yves-Alexis signature.asc Description: This is a digitally signed message part
Bug#685694: libmatio: diff for NMU version 1.3.4-3.1
Hey Sylvestre On Sun, Sep 02, 2012 at 10:16:09AM +0200, Sylvestre Ledru wrote: > Le 01/09/2012 13:33, Salvatore Bonaccorso a écrit : > > Dear Sylvestre > > > > A rebuild of the libmatio-doc would suffice here, as Sebastien noted. > > Is it fine for you to upload a 'no changes' upload or would you like > > to do it yourself? > > > > This would fix RC bug #685694. > > > OK. Sounds great. :) (even if I don't like "no-changes" upload when I > don't know why it failed before ... > > Don't hesitate to NMU with a 0 delay (or I can do the upload, no worries) I'm fine with leaving the upload to you if you have time! Btw, I agree with you on first part. Do you maybe still have your build logs available from the upload? Could you check which doxygen(-latex) version was used then at the time of the upload? Would anyway be interesting to know :) Regards, Salvatore signature.asc Description: Digital signature
Bug#579227: Looks like we should drop jscoverage for squeeze
I'm not aware of any alternative for javascript coverage packaged in debian. So if possible I would like to keep it in unstable.
Bug#686495: libpcre3: Very large value for re_nsub
Package: libpcre3 Version: 1:8.30-5 Severity: grave Tags: patch Justification: causes non-serious data loss Dear Maintainer, when compiling the regular expression regex_t rx; regcomp(&rx, "^(\\(\\))? *(.*)$", 0) I get the large value 140733193388034 for rx.re_nsub. As this value is often used afterwards in malloc this normally leads to the termination of the programm (either because of the segfault or due to the assumption of no free memory), so unsaved data gets lost. The problem is well known (http://www.exim.org/lurker/message/20120822.143744.147fd5d2.de.html) and a patch exists (http://bugs.exim.org/attachment.cgi?id=586). I can confirm that the patch works. Please consider applying the patch. Cheers Patrick -- System Information: Debian Release: wheezy/sid APT prefers testing APT policy: (900, 'testing'), (500, 'testing-proposed-updates'), (500, 'stable-updates'), (400, 'unstable') Architecture: amd64 (x86_64) Kernel: Linux 3.2.0-3-amd64 (SMP w/6 CPU cores) Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages libpcre3 depends on: ii libc6 2.13-35 ii multiarch-support 2.13-35 libpcre3 recommends no packages. libpcre3 suggests no packages. -- no debconf information -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#686484: chowning pid directory and writing there as root may lead to security issue
On 02.09.2012 13:40, Simon Kelley wrote: [] > The explanation for the current state of affairs is here: > > http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=508560 Oh. I tried to find why/when this subdir appeared, but failed. The changelog mentions PID in uppercase ;) I'm sorry about this, knowing that I'd have much more useful bugreport. > /var/run/dnsmasq is owned by user dnsmasq so that dnsmasq can unlink the pid > file when it shuts down, even though at that point it is running as user > "dnsmasq", not as user "root". This is a very general issue with daemons dropping privileges and their pidfiles. Each package solves it in its own way. Some forks a worker process which does setuid(), with a root-owned babysitter waiting for it to exit and clean the pidfile. Some keeps the pidfile open and truncates (not unlinking) it on exit. And some merely ignores this issue. And I think this 3rd option is the best in this case. The daemon itself does not _use_ the pidfile, it merely writes the pidfile. And tools like start-stop-daemon usually check /proc/$PID/exe or equivalent for the right executable, so, even if we'll leave the stale pidfile, no harm will be done at all. #508560 has minor severity, and I think it is just cosmetic thing. Note: having user-writable /var/run/FOO subdir, or keeping /var/run/FOO.pid open after dropping privileges are both, well, risky, since in both cases the process in question gains more privileges than actually necessary. It only needs to REMOVE (or clear) one file, but it can fill whole /var/run, or write some garbage to the pid file to trick the startup script (run as root) to execute some evil code. So I think just stopping caring (and reintroducing #508560) is the best thing to do. And by moving the pidfile back to /var/run/ we're back to the documented place and to no need for extra args. (But such "moving back", if choosen, should be done carefully -- the initscript may need to continue providing /var/run/dnsmasq/ dir, now without chowning it, since old config may need it. Sigh.) Answering to the other your email: O_EXCL exist, yes, but we still have more privs (with writable subdir in /var/run/) than necessary. Not as dangerous as current way, but still a bit too many. Thank you! /mjt -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#686258: Please allow translation of all debconf templates
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On 01/09/12 19:49, David Prévot wrote: > Hi Rodolfo, > > Le 30/08/2012 14:48, David Prévot a écrit : >> Le 30/08/2012 13:41, "Rodolfo García Peñas (kix)" a écrit : >>> On 30/08/2012 18:01, David Prévot wrote: Package: uswsusp > >> I would advise to only take care of this issue, i.e, apply the >> simple patch proposed in the bug report, run debconf-updatepo, >> and send a call for translation (that is what I'm proposing help >> for). > > Just done that. I'll ping you back in a about a week with a > debdiff including all up to date translations. > > Regards > > David > Ok, done. I will wait the translators. Thanks for your help. OTOH I have some (2) returned emails of tranlators: First: The original message was received at Sun, 2 Sep 2012 11:46:41 +0200 from localhost [127.0.0.1] - The following addresses had permanent fatal errors - (reason: 550 Unrouteable address) - Transcript of session follows - ... while talking to master.debian.org.: >>> RCPT To: <<< 550 Unrouteable address 550 5.1.1 ... User unknown >>> DATA <<< 503-All RCPT commands were rejected with this error: <<< 503-Unrouteable address <<< 503 valid RCPT command must precede DATA Second: in chào Rodolfo GarcíaPeñas (kix) , Chúng tôi viết thư để thông báo cho bạn biết rằng nhóm mà bạn đang cố tìm cách liên hệ (vi-vn) có thể không tồn tại hoặc bạn có thể không được phép đăng bài vào nhóm. Một số chi tiết khác về lý do bạn không thể đăng bài: * Có thể bạn viết hoặc định dạng tên nhóm không đúng. * Chủ nhóm có thể đã xóa nhóm này. * Có thể bạn cần tham gia nhóm trước khi được phép đăng bài. * Nhóm này có thể không mở để đăng bài. Nếu bạn có câu hỏi liên quan đến nhóm Google này hoặc bất kỳ nhóm Google nào khác, hãy truy cập Trung tâm Trợ giúp tại http://groups.google.com/support/?hl=vi_US. Xin cảm ơn, Google Groups Thanks a lot, Best regards, kix - -- ||// //\\// Rodolfo "kix" Garcia ||\\// //\\ http://www.kix.es/ -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.12 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iQIcBAEBCAAGBQJQQyvbAAoJEHsfVJByt0kjCAgP/3cCS/vJG+samm+G0KNwM+TV nBLC8fcCAJvKRPdl9T7LhJ37lBrWP7029HIa2goKs7DgkNydK0o9lOC3RbjU+dE0 6S2dkoKPzcCYeJyfE6BAV32KOd7i3jJc0tkk0ZsbCWs3XGlNNw5QZCFllvPc4Xvy KEv5Y//ZWLGuB5f4ikrkb1/GL7c5dgo6Mdc8zXwnC7Ue7A8nbth2okl2en04H79q 6UDU3On/nVipJ+sicCt0lYtQZJ+Lu+A7Ubm9VicXMl1Uuk7lbb/NWBtUEhM0VSGZ 426YlwRAK4DS7QCDPUteJ7GI94l6eGc+eXKODyeqv1E4WSAt/L7VKWw4V/vTDCie 7apbb+m2rKspg5m0w7yqo2UFxXwcWLfDIR1S9mv8WgMbJ7iWyX1VN8f0Zmrj/S9g CQeiZg458naROopIyaycns91/b88GFOdoIUu9zdEk90IC5BDpmb7JACVe1we/K2B 7pRK+TiG+TSGSE1yeyF8U49vU+p2r1qKLg4oEpFS48mRZtTUAuE9W7dqRE/YW/+a Mh01BAjSYJVUYgtaD36RGbvzCjikMS4hJDv7dhTPKL+Y1PSDjUkL7RnQy5hZwOnh f+KkCRyhlZ6iB3Md2Y+HfTZNEPQr78xvMuEOUWYQr20Da7MyrJLIOrLDBLlJ9zXu yRe+WqbzpYzmLT9YT4Ei =RYFQ -END PGP SIGNATURE- -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#686484: chowning pid directory and writing there as root may lead to security issue
On 02/09/12 08:44, Michael Tokarev wrote: Package: dnsmasq Version: 2.55-2 Severity: serious Tags: security Ignore my previous question: currently educating myself about O_EXCL Simon. -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Processed: your mail
Processing commands for cont...@bugs.debian.org: > forwarded 677929 > https://sourceforge.net/tracker/?func=detail&atid=422030&aid=3540052&group_id=38414 Bug #677929 [python-docutils] python-docutils: remote copy of MathJax needed to render maths Set Bug forwarded-to-address to 'https://sourceforge.net/tracker/?func=detail&atid=422030&aid=3540052&group_id=38414'. > thanks Stopping processing here. Please contact me if you need assistance. -- 677929: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=677929 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#686484: chowning pid directory and writing there as root may lead to security issue
On 02/09/12 08:44, Michael Tokarev wrote:
Package: dnsmasq
Version: 2.55-2
Severity: serious
Tags: security
The initscript (and postinst script) of dnsmasq creates /var/run/dnsmasq
directory and chowns it to dnsmasq:nogroup. However, dnsmasq daemon writes
the pidfile (which apparently is the only file there) as root user. Here's
the code which does this (in src/dnsmasq.c):
FILE *pidfile;
/* only complain if started as root */
if ((pidfile = fopen(daemon->runfile, "w")))
{
fprintf(pidfile, "%d\n", (int) getpid());
fclose(pidfile);
}
So there's no checking for this file to exist, being a symlink etc.
This way, we effectively making dnsmasq user equal to root: dnsmasq
user can (sym)link /var/run/dnsmasq/dnsmasq.pid to, say, /etc/shadow,
and it will be overwitten the next time dnsmasq (re)starts. This is
obviously wrong.
The only good side of this is that dnsmasq writes only controlled data
to this file (its pid, as per above), so the damage is minimal, ie,
only a denial of service, not gain of service (hence Severity is only
"serious").
Besides, documentation says the pid file is /var/run/dnsmasq.pid, not
/var/run/dnsmasq/dnsmasq.pid - it is the initscript which sets the option
"behind the scenes". Also, there's no mentions in the changelog about
WHY pid file is in this location. And more, it one can change the user
dnsmasq runs as.
It looks like this pidfile stuff needs to be removed entirely (moving
it to a subdir silently and chowning that subdir to dnsmasq user).
Thanks,
/mjt
The explanation for the current state of affairs is here:
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=508560
/var/run/dnsmasq is owned by user dnsmasq so that dnsmasq can unlink the
pid file when it shuts down, even though at that point it is running as
user "dnsmasq", not as user "root".
I can see a couple of ways of fixing this, without just removing the
whole edifice, but neither are perfect.
1) stat the pid file and check for symlinks, etc (or just unlink it)
just before creating the new one. There's a race between the unlink and
the creation though - an attacker could create the symlink then.
2) Create the pid file after changing user. That works fine in this
case, but not in the default case when dnsmasq writes to
/var/run/dnsmasq.pid and then changes to user "nobody". The behaviour
would therefore need to be enabled by a special config option or risk
breaking nearly every dnsmasq installation other than Debian/Ubunutu.
Simon.
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#685694: libmatio: diff for NMU version 1.3.4-3.1
Le 01/09/2012 13:33, Salvatore Bonaccorso a écrit : > Dear Sylvestre > > A rebuild of the libmatio-doc would suffice here, as Sebastien noted. > Is it fine for you to upload a 'no changes' upload or would you like > to do it yourself? > > This would fix RC bug #685694. > OK. Sounds great. :) (even if I don't like "no-changes" upload when I don't know why it failed before ... Don't hesitate to NMU with a 0 delay (or I can do the upload, no worries) Thanks, S -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#579227: Looks like we should drop jscoverage for squeeze
Sure, it doesn't seem upstream is actively developing it anymore. On Sep 2, 2012 1:39 AM, "David Prévot" wrote: > Control: found -1 0.3.1-1 > > Hi, > > On Sat, Nov 13, 2010 at 08:51:40PM +0100, Johan Euphrosine wrote: > > On Sat, Nov 13, 2010 at 8:39 PM, Enrico Zini > wrote: > > > Hello, > > > > > > thank you for maintaining jscoverage. > > > > > > jscoverage 0.3.1-1 is currently in squeeze and sid and has RC bugs open > > > against it. > > > > > > Considering that the package has a very small number of users, that > > > we're supposed to release fairly soon, and that this issue looks not > > > that easy to solve, it may be a good idea to just remove > > > jscoverage from testing and deal with this comfortably in unstable. > > > > > > Would it make sense for you? > > > > Sure, > > > > The only RC bugs known to me is #579227, > > > > Last time I pinged upstream about it, he said that it would require a > > rewrite of some key part of jscoverage in order to use the new parser > > API in spidermonkey and remove the embedded copy. > > > > I think it is a good idea to remove jscoverage from testing if it > > blocks squeeze release, and I will keep updating the unstable package > > when upstream publish a new major version. > > It seems jscoverage 0.3.1-1 currently in testing (and Squeeze) also > shipped an embedded code copy of libmozjs, so it may be sensible to > actually remove it from testing as suggested two years ago, and maybe > from Squeeze too. > > Regards > > David > > >
Bug#686484: chowning pid directory and writing there as root may lead to security issue
Package: dnsmasq
Version: 2.55-2
Severity: serious
Tags: security
The initscript (and postinst script) of dnsmasq creates /var/run/dnsmasq
directory and chowns it to dnsmasq:nogroup. However, dnsmasq daemon writes
the pidfile (which apparently is the only file there) as root user. Here's
the code which does this (in src/dnsmasq.c):
FILE *pidfile;
/* only complain if started as root */
if ((pidfile = fopen(daemon->runfile, "w")))
{
fprintf(pidfile, "%d\n", (int) getpid());
fclose(pidfile);
}
So there's no checking for this file to exist, being a symlink etc.
This way, we effectively making dnsmasq user equal to root: dnsmasq
user can (sym)link /var/run/dnsmasq/dnsmasq.pid to, say, /etc/shadow,
and it will be overwitten the next time dnsmasq (re)starts. This is
obviously wrong.
The only good side of this is that dnsmasq writes only controlled data
to this file (its pid, as per above), so the damage is minimal, ie,
only a denial of service, not gain of service (hence Severity is only
"serious").
Besides, documentation says the pid file is /var/run/dnsmasq.pid, not
/var/run/dnsmasq/dnsmasq.pid - it is the initscript which sets the option
"behind the scenes". Also, there's no mentions in the changelog about
WHY pid file is in this location. And more, it one can change the user
dnsmasq runs as.
It looks like this pidfile stuff needs to be removed entirely (moving
it to a subdir silently and chowning that subdir to dnsmasq user).
Thanks,
/mjt
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
