Bug#691078: motion keeps restarting after recent upgrade, and appears unable to find some av codec
On Tue, 06 Nov 2012 21:52:17 -0500, H. S. wrote: > I reinstalled the system, however, motion was not happy with the > target directory permissions. Once I fixed that, it started to work > properly. Nice! > In short, on a freshly installed Wheezy system, motion now works fine. > > Next up, I usually change my distro to "testing" ... Wheezy is the current testing already :) Cheers, gregor -- .''`. Homepage: http://info.comodo.priv.at/ - OpenPGP key 0xBB3A68018649AA06 : :' : Debian GNU/Linux user, admin, and developer - http://www.debian.org/ `. `' Member of VIBE!AT & SPI, fellow of the Free Software Foundation Europe `- BOFH excuse #332: suboptimal routing experience -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#685251: Severity as important
On 11/07/2012 07:10 AM, Cyril Brulebois wrote: > Control: severity -1 serious > > Thomas Goirand (02/11/2012): >> Since this affects only the ryu agent, and doesn't render the full >> Quantum package unusable (you can still continue to use it with >> OpenVSwitch), I've set this bug's severity as important. >> >> Never the less, it shall be fixed... > > You do know that mailing the bug doesn't mail the submitter, and is > considered bad style? I believe that an experienced DD like Jakub can subscribe to the bug if he wants to. > Anyway, the bug is reported against the quantum-plugin-ryu-agent > package, and it looks to me that if the ryu agent “only” is affected, > this whole package is unusable; ICBW though. Well, the binary package quantum-plugin-ryu-agent is affected indeed, but I believe this is the view of the whole Openstack packaging team, that having just one of the pluggins being broken isn't a reason good enough for completely removing Quantum from Wheezy, which otherwise seem to work properly (for example using OpenVSwitch). More over, I don't think any of the members of the Openstack packaging team has access to a Ryu hardware in order to test this pluggin. Your thoughts? Thomas -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#692523: cm-super: changelog.Debian.gz could be for wrong version
Package: cm-super Version: 0.3.4-6 Severity: serious Dear Maintainer, Since this package's doc dir is just a symlink to the one for cm-super-minimal, the changelog.Debian.gz file comes from that package. However, this package doesn't depend on an identical version of that package, so it could be the wrong version. Under the usual interpretation of policy, this violates the directive that binary packages MUST install a copy of debian/changelog (see section 12.7), since a different version of the package would certainly have a non-identical changelog. -- 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 cm-super depends on: ii cm-super-minimal 0.3.4-6 ii dpkg 1.16.9 ii pfb2t1c2pfb0.3-9 ii tex-common 3.13 ii texlive-latex-recommended 2012.20120611-5 cm-super recommends no packages. cm-super suggests no packages. -- no debconf information -- Hi! I'm a .signature virus! Copy me into your ~/.signature to help me spread! -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#691078: motion keeps restarting after recent upgrade, and appears unable to find some av codec
Correction: I reinstalled the system, however, motion was not happy with the target directory permissions. Once I fixed that, it started to work properly. In short, on a freshly installed Wheezy system, motion now works fine. Next up, I usually change my distro to "testing" ... will do so with my fingers crossed in a day or two. Thanks. On Tue, Nov 6, 2012 at 11:38 AM, gregor herrmann wrote: > Control: tag -1 - moreinfo > >> >> [UPGRADE] ffmpeg:amd64 7:0.11.1-dmo5 -> 7:1.0-dmo1 >> >> [UPGRADE] gstreamer0.10-ffmpeg:amd64 0.10.13-5 -> 1:0.10.13-dmo1 >> >> [UPGRADE] libxine2-ffmpeg:amd64 1.2.2-4 -> 1:1.2.2-dmo3 >> >> [UPGRADE] libavcodec54:amd64 7:0.11.1-dmo5 -> 7:1.0-dmo1 >> >> [UPGRADE] libavdevice54:amd64 7:0.11.1-dmo5 -> 7:1.0-dmo1 >> >> [UPGRADE] libavformat54:amd64 7:0.11.1-dmo5 -> 7:1.0-dmo1 >> >> [UPGRADE] libavutil51:amd64 7:0.11.1-dmo5 -> 7:1.0-dmo1 >> > -dmoN means that you are using packages from deb-multimedia.org. >> > Do you have the same problem when you use the packages from Debian >> > proper? >> Just reinstalled my whole system. On this newly installed and updated >> wheezy system, motion doesn't even start capturing properly! > > Thanks for checking! > >> I am using the same conf file I was using till several days ago when >> it was working fine. Now when I start motion, it just spits out the >> initialization lines on the prompt and then does nothing at all. With >> the above dmo1 packages it was at least capturing some image, albeit >> at a much slower rate. > > Ok, now we at least know that there is a real problem in some Debian > package. Sorry that it won't be me who tackles it, but at least that > step is done. > > > Cheers, > gregor > > -- > .''`. Homepage: http://info.comodo.priv.at/ - OpenPGP key 0xBB3A68018649AA06 > : :' : Debian GNU/Linux user, admin, and developer - http://www.debian.org/ > `. `' Member of VIBE!AT & SPI, fellow of the Free Software Foundation Europe >`- NP: Eric Clapton: After Midnight -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Processed: tagging 692411
Processing commands for cont...@bugs.debian.org: > tags 692411 + pending Bug #692411 [src:linux] linux: fix for the ext4 corruption issue is in 3.6.6 Added tag(s) pending. > thanks Stopping processing here. Please contact me if you need assistance. -- 692411: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=692411 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#669918: Fixed?
I guess my problem is fixed. I am not able anymore to reproduce that bug on my system using kmail Version: 4:4.4.11.1+l10n-3+b1 --- Daniel Koch GPG: 83DE 2C48 5A9F 9992 843A 0EAD 3B2D 7E8F 13F4 9C39 -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Processed: reassign 692500 to src:linux, severity of 692500 is serious, forcibly merging 692500 689268
Processing commands for cont...@bugs.debian.org: > reassign 692500 src:linux 3.2.32-1 Bug #692500 [linux-image-amd64] [linux-image-amd64] system freezes with Ivy Brigde CPU Bug reassigned from package 'linux-image-amd64' to 'src:linux'. No longer marked as found in versions linux-latest/46. Ignoring request to alter fixed versions of bug #692500 to the same values previously set Bug #692500 [src:linux] [linux-image-amd64] system freezes with Ivy Brigde CPU Marked as found in versions linux/3.2.32-1. > severity 692500 serious Bug #692500 [src:linux] [linux-image-amd64] system freezes with Ivy Brigde CPU Severity set to 'serious' from 'critical' > forcemerge 692500 689268 Bug #692500 [src:linux] [linux-image-amd64] system freezes with Ivy Brigde CPU Bug #689268 [src:linux] linux-image-3.2.0-3-amd64: Intel HD 4000 (Ivy Bridge) graphics freeze Severity set to 'serious' from 'important' Bug #692500 [src:linux] [linux-image-amd64] system freezes with Ivy Brigde CPU Marked as fixed in versions linux-2.6/3.3.6-1~experimental.1 and linux/3.5.5-1~experimental.1. Marked as found in versions linux/3.2.23-1. Merged 689268 692500 > thanks Stopping processing here. Please contact me if you need assistance. -- 689268: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=689268 692500: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=692500 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#692342: apt-move move command deletes all files without moving them
control: tag -1 confirmed Confirming that "apt-move get && apt-move move" behaves like this. Building and installing 4.2.27-1 on wheezy doesn't help. Testing on squeeze, it does work. Best wishes, Mike -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Processed: re: apt-move move command deletes all files without moving them
Processing control commands: > tag -1 confirmed Bug #692342 [apt-move] apt-move move command deletes all files without moving them Added tag(s) confirmed. -- 692342: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=692342 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#688259: marked as done (zangband: modifies shipped files during postinst, overwrites score file on upgrade)
Your message dated Tue, 06 Nov 2012 23:32:53 + with message-id and subject line Bug#688259: fixed in zangband 1:2.7.5pre1-5 has caused the Debian Bug report #688259, regarding zangband: modifies shipped files during postinst, overwrites score file on upgrade 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.) -- 688259: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=688259 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: zangband Version: 1:2.7.5pre1-4 Severity: serious User: debian...@lists.debian.org Usertags: piuparts Hi, during a test with piuparts I noticed your package modifies some of teh files it ships. debsums reports modification of the following files, from the attached log (scroll to the bottom...): debsums: missing file /var/games/zangband/data/misc.raw (from zangband package) debsums: missing file /var/games/zangband/data/k_info.raw (from zangband package) debsums: missing file /var/games/zangband/data/v_info.raw (from zangband package) debsums: missing file /var/games/zangband/data/f_info.raw (from zangband package) debsums: missing file /var/games/zangband/data/e_info.raw (from zangband package) debsums: missing file /var/games/zangband/data/r_info.raw (from zangband package) debsums: missing file /var/games/zangband/data/a_info.raw (from zangband package) There is no need to ship these files if they get reinitialized in the postinst script anyway. Looking at the postinst and the file list in more detail, I also noticed that the score file is overwritten with an empty file on every upgrade/reinstallation. Also static_datadir is set wrongly to /usr/share/games/zangband which makes the postinst not do its job properly (it just touches a file called '*.raw' - yes, an asterisk in the filename). Probably static_datadir=/usr/share/games/zangband/lib would be correct. cheers, Andreas zangband_1:2.7.5pre1-4.log.gz Description: GNU Zip compressed data --- End Message --- --- Begin Message --- Source: zangband Source-Version: 1:2.7.5pre1-5 We believe that the bug you reported is fixed in the latest version of zangband, 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 688...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Drew Parsons (supplier of updated zangband 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: SHA1 Format: 1.8 Date: Wed, 07 Nov 2012 08:29:55 +1100 Source: zangband Binary: zangband zangband-data Architecture: source all amd64 Version: 1:2.7.5pre1-5 Distribution: unstable Urgency: low Maintainer: Drew Parsons Changed-By: Drew Parsons Description: zangband - A single-player, text-based, roguelike game zangband-data - A single-player, text-based, roguelike game (datafiles) Closes: 688259 Changes: zangband (1:2.7.5pre1-5) unstable; urgency=low . * Fix wrong $static_datadir path in zangband.postinst file to avoid deletion of *.raw files in /var/games/zangband/data. Thanks, Markus Koschany. Closes: #688259. * Fixed Lintian warnings: - debhelper-but-no-misc-depends - patch-system-but-no-source-readme - debian-rules-missing-recommended-target - dh-clean-k-is-deprecated * override lintian warning description-synopsis-starts-with-article * debhelper compat 9 * Standards-Version: 3.9.4 Checksums-Sha1: a16b4242a5390f33e2ac4f8a011578125b3c9a42 1233 zangband_2.7.5pre1-5.dsc a6753288725f7009799327c79fd56e504210d26c 106497 zangband_2.7.5pre1-5.diff.gz c069c3ad54df5d6d2152655b2041e5ba5f4fe23e 1085072 zangband-data_2.7.5pre1-5_all.deb bdf2fa060a832f8963990e2ec421c94e4ae56a4a 915958 zangband_2.7.5pre1-5_amd64.deb Checksums-Sha256: a1bdc3eb1168d86fc580ae637f1a4869bd896603f95b7fbfe8d41dfd2e370eea 1233 zangband_2.7.5pre1-5.dsc 87145e940718fed13340b17930188845782c94fe3d5f8bc8647cf6f0154e40ee 106497 zangband_2.7.5pre1-5.diff.gz c58c824015868f638397d76bf12d60416aeebec51a2bd38a1bb40b863759e923 1085072 zangband-data_2.7.5pre1-5_all.deb bad8a62be85daf2799e2907cb12089908aa862300997c6bf51fdfdded002bae4 915958 zangband_2.7.5pre1-5_amd64.deb Files: 0ba78affd7f01b53fa988595b5fe4c26 1233 non-free/games optional zangband_2
Bug#688259: zangband: modifies shipped files during postinst
On Tue, 2012-11-06 at 19:54 +0100, Niels Thykier wrote: > > Drew, if you still intend to upload a fix for this bug, please do it > sooner rather than later. Otherwise, consider asking someone to > NMU/fix this package for you. Uploaded. Thanks for your patience. Markus, I left some hardening lintian warnings for you :) Rewriting a completely new debian/rules to use dh is possibly the simplest way to fix it. With the file permissions lintian warning, I understand the one zangband uses is desirable for sharing high scores among multiple players, but I haven't checked thoroughly. Drew -- 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#685251: Severity as important
Processing control commands: > severity -1 serious Bug #685251 [quantum-plugin-ryu-agent] quantum-plugin-ryu-agent: ImportError: No module named ryu.agent.ryu_quantum_agent / ryu.app Severity set to 'serious' from 'important' -- 685251: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=685251 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#690128: inn2: conffile disappearing during squeeze->wheezy upgrade: /etc/news/motd.news
On Wed, 10 Oct 2012 13:41:15 +0200, Julien ÉLIE wrote: > /etc/news/motd.nnrpd and /etc/news/motd.innd are two new conf files > shipped with INN 2.5.3. > /etc/news/motd.news is no longer used. > During a fresh install, motd.nnrpd and motd.innd are the two files shipped > in the inn2 tarball. > During an update, motd.innd is not installed. And motd.news (if present) > is moved to motd.nnrpd. So motd.nnrpd can be present or not. I looked at what happens with different versions, and what the package does: squeeze: root@jadzia:/# ls -la /etc/news/motd* -rw-r--r-- 1 root root 239 Dec 30 2010 /etc/news/motd.news wheezy (upgrade from squeeze): root@jadzia:/# ls -la /etc/news/motd* -rw-r--r-- 1 root root 239 Dec 30 2010 /etc/news/motd.nnrpd wheezy (fresh install): root@jadzia:/# ls -la /etc/news/motd* ls: cannot access /etc/news/motd*: No such file or directory In the current version, motd.innd and motd.nnrpd are installed only as examples. So both of them are missing in /etc/news for fresh installs. On upgrades, innupgrade is called from the postinst and renames motd.news to motd.nnrpd, and motd.innd is not installed. (No idea at the moment how to represent the move done via innupgrade with dpkg-maintscript-helper.) Cheers, gregor -- .''`. Homepage: http://info.comodo.priv.at/ - OpenPGP key 0xBB3A68018649AA06 : :' : Debian GNU/Linux user, admin, and developer - http://www.debian.org/ `. `' Member of VIBE!AT & SPI, fellow of the Free Software Foundation Europe `- NP: Flying Pickets: Take My Breath Away signature.asc Description: Digital signature
Bug#692062: marked as done (enigmail FTBFS)
Your message dated Tue, 06 Nov 2012 22:17:36 + with message-id and subject line Bug#692062: fixed in enigmail 2:1.4.5+id16-1 has caused the Debian Bug report #692062, regarding enigmail FTBFS 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.) -- 692062: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=692062 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: enigmail Version: 2:1.4.1exp-1 Severity: serious engimail FTBFS with icedove 16.0.2-1 ---snip--- [...] /usr/lib/icedove-devel/include/mozilla/Mutex.h:184:29: error: expected ‘,’ or ‘...’ before ‘MOZ_GUARD_OBJECT_NOTIFIER_PARAM’ /usr/lib/icedove-devel/include/mozilla/Mutex.h:205:5: error: ‘MOZ_DECL_USE_GUARD_OBJECT_NOTIFIER’ does not name a type /usr/lib/icedove-devel/include/mozilla/Mutex.h: In constructor ‘mozilla::BaseAutoUnlock::BaseAutoUnlock(T&)’: /usr/lib/icedove-devel/include/mozilla/Mutex.h:187:9: error: ‘MOZ_GUARD_OBJECT_NOTIFIER_INIT’ was not declared in this scope make[8]: *** [nsPipeTransport.o] Error 1 make[8]: Leaving directory `/home/daniel/enigmail/extensions/enigmail/ipc/src' make[7]: *** [libs] Error 2 make[7]: Leaving directory `/home/daniel/enigmail/extensions/enigmail/ipc' make[6]: *** [libs] Error 2 make[6]: Leaving directory `/home/daniel/enigmail/extensions/enigmail' make[5]: *** [enigmail_libs] Error 2 make[5]: Leaving directory `/home/daniel/enigmail/extensions' make[4]: *** [libs_tier_app] Error 2 make[4]: Leaving directory `/home/daniel/enigmail' make[3]: *** [tier_app] Error 2 make[3]: Leaving directory `/home/daniel/enigmail' make[2]: *** [default] Error 2 make[2]: Leaving directory `/home/daniel/enigmail' dh_auto_build: make -j1 returned exit code 2 make[1]: *** [override_dh_auto_build] Error 2 make[1]: Leaving directory `/home/daniel/enigmail' make: *** [binary] Error 2 dpkg-buildpackage: error: fakeroot debian/rules binary gave error exit status 2 ---snap--- -- Address:Daniel Baumann, Donnerbuehlweg 3, CH-3012 Bern Email: daniel.baum...@progress-technologies.net Internet: http://people.progress-technologies.net/~daniel.baumann/ --- End Message --- --- Begin Message --- Source: enigmail Source-Version: 2:1.4.5+id16-1 We believe that the bug you reported is fixed in the latest version of enigmail, 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 692...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Willi Mann (supplier of updated enigmail 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: Tue, 06 Nov 2012 22:58:32 +0100 Source: enigmail Binary: enigmail Architecture: source amd64 Version: 2:1.4.5+id16-1 Distribution: experimental Urgency: low Maintainer: Alexander Sack Changed-By: Willi Mann Description: enigmail - GPG support for Thunderbird and Debian Icedove Closes: 692062 Changes: enigmail (2:1.4.5+id16-1) experimental; urgency=low . * pack-upstream.sh: Add script to properly pack tarball * Imported Upstream version 1.4.5+id16 (closes: #692062) * d/control: Update dependencies * Refresh patches Checksums-Sha1: 81849126a606fcb57d237828bfad71786b62a32f 1906 enigmail_1.4.5+id16-1.dsc 894ddd17d5c99da5959857ea9a4ff47ce16840db 2374777 enigmail_1.4.5+id16.orig.tar.gz c945d658b072ee9e691e6c49857804727c2ed376 21419 enigmail_1.4.5+id16-1.diff.gz 66138db10c33cf32cbe0856776252ab12a197a7b 1325574 enigmail_1.4.5+id16-1_amd64.deb Checksums-Sha256: dcea2f934f826aad3ce5e7cc6f1c3d75e1259c0422a923a4857598d839301a51 1906 enigmail_1.4.5+id16-1.dsc e7642fb6067085cd6226b8fe51aefbb01a8f9f835c24ca552caffa13fa0d197a 2374777 enigmail_1.4.5+id16.orig.tar.gz 38d5a1a0f5f8dd3fad0808328f4aaa97db8880a28872e81e8ab87b56791ca521 21419 enigmail_1.4.5+id16-1.diff.gz f3389ba134c559af363db0b0b262489149b556d5c8245bdd4c8eefcc831d3375 1325574 enigmail_1.4.5+id16-1_amd64.deb Files: 7a0c5ae2e382b6b9a2ff69de255b013b 1906 mail optional enigmail_1.4.5+id16-1.dsc 3cb18c9b6184b4b9a129ff81160324aa 2374777 mail optional enigmail_1.4.5+id16.orig.tar.gz 9a97f2442dcbdc1f9e338bbb42ad6597 21419 mail optional enigmail_1.4.5+id16-1.diff.gz 130959ebc983799d3f2932fa2889d187 1325574 mail optional enig
Bug#692295: I've observed this, too, but cannot reproduce
While trying to reproduce this, I was able to observe it once, but then unable to reproduce further. The only explanation I can think of right now is some edge case related to upgrading the package. I was unable to reproduce that either, however. In any case, the working version of this package (1.2.0-2) should be *unfrozen* for wheezy, because shipping 1.2.0-1 with wheezy would mean shipping a broken package that cannot be installed unattended without additional measures. -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#692500: [linux-image-amd64] system freezes with Ivy Brigde CPU
Package: linux-image-amd64 Version: 3.2+46 Severity: critical --- Please enter the report below this line. --- Several users reported system freezes with a Wheezy beta. See this thread: http://forums.debian.net/viewtopic.php?f=10&t=85533 I experienced this problem multiple times per day with the following setup: - CPU is Intel(R) Core(TM) i7-3770K CPU @ 3.50GHz - Linux Kernel 3.2.0-2 from the Wheezy repository - I am using the onboard GPU By searching the internet I came to the conclusion that it is a problem with the Linux Kernel and the Ivy Bridge GPU as mentioned here (see "Stability fixes for hard hangs on Ivy Bridge platform"): http://intellinuxgraphics.org/2012.02.html The upstream commit that fixes this problem is fb046853ad66e64c96a2598f3fdd4cf5fbabc0d1. So kernel >= 3.5 should no longer have this problem. After running the upstream kernel 3.6.3 for several days I can confirm that switching to a newer kernel version fixed the problem in my case. --- System information. --- Architecture: amd64 Kernel: Linux 3.6.3-upstream Debian Release: wheezy/sid 500 testing security.debian.org 500 testing mirror.1und1.de --- Package information. --- Depends (Version) | Installed -+-=== linux-image-3.2.0-4-amd64 | 3.2.32-1 Package's Recommends field is empty. Package's Suggests field is empty. -- 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#692492: ITO: Orphaning audit package
Processing commands for cont...@bugs.debian.org: > severity 692492 normal Bug #692492 [auditd] ITO: Orphaning audit package Severity set to 'normal' from 'serious' > thanks Stopping processing here. Please contact me if you need assistance. -- 692492: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=692492 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#692492: ITO: Orphaning audit package
severity 692492 normal thanks On Tue, Nov 06, 2012 at 08:01:54PM +0100, Laurent Bigonville wrote: > Package: auditd > Severity: serious > Version: 1:1.7.18-1.1 "serious" severity refers to bugs that are blockers for a release. A missing maintainer is not a serious bug. The other serious bug stands on its own - but does not impact the release because it only applies to experimental. Please do not inflate the severity of bug reports, this causes extra work for release tracking. > I've tried to enter in contact with Philipp Matthias regarding the > status of the audit package. I've sent a first mail a bit more than a > month ago and a second one 15 days later. But I unfortunately didn't > get any answer so far. And where did you cc: this mail for a public record, to what address did you send it, and what was written in this mail that should give the maintainer reason to prioritize responding to it? Private mails should not be a justification for expedited orphaning of packages. With this bug report you have *now* used a proper channel for notifying the maintainer that you want to salvage the package; so the clock starts now, not whenever your private mail was sent. > I'm planning to orphan (and upload my changes for experimental) "soon" > if nobody objects. Are you deliberately ignoring the ongoing discussion on debian-devel about why "nobody objects" is not an acceptable standard for orphaning packages? According to LDAP, the maintainer has been active in the BTS as recently as two days ago. An NMU for a serious bug is obviously ok (including in experimental), but you can consider this an objection to any such "soon" orphaning. -- Steve Langasek Give me a lever long enough and a Free OS Debian Developer to set it on, and I can move the world. Ubuntu Developerhttp://www.debian.org/ slanga...@ubuntu.com vor...@debian.org signature.asc Description: Digital signature
Bug#688140: file-rc: File-rc doesn't restore rcX.d dirs at remove, breaks sysv-rc installation.
On Wednesday, 19. September 2012 21:05:03 Piotr Borkowski wrote: > File-rc doesn't restore rcX.d dirs at remove. This breaks sysv-rc > legacy_bootordering postinst function. After sysv-rc installation this > leads to empty rcX.d dirs and broken system. Maybe file-rc should call I can reproduce this problem in piuparts distupgrade tests, e.g. setup squeeze (or wheezy) chroot switch to file-rc distupgrade to wheezy (or sid) switch back to sysv-rc but not within a distro: setup a squeeze (or wheezy or sid) chroot switch to file-rc switch back to sysv-rc curiously it also happens after a wheezy->sid distuprade, even if the versions of sysv-rc and file-rc are the same in both sid and wheezy Andreas -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#676141: marked as done (rt4-extension-assettracker: fails to upgrade from wheezy: updating database schema for 1.2.4...command failed with code 2)
Your message dated Tue, 06 Nov 2012 20:43:26 +0100 with message-id <5099685e.1000...@thykier.net> and subject line Re: Bug#676141: rt4-extension-assettracker:, fails to upgrade from wheezy: updating database schema for 1.2.4...command, failed with code 2 has caused the Debian Bug report #676141, regarding rt4-extension-assettracker: fails to upgrade from wheezy: updating database schema for 1.2.4...command failed with code 2 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.) -- 676141: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=676141 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: rt4-extension-assettracker Version: 2.0.0~b2-4 Severity: serious User: debian...@lists.debian.org Usertags: piuparts Hi, during a test with piuparts I noticed your package fails to upgrade from 'wheezy'. It installed fine in 'wheezy', then the upgrade to 'sid' fails. >From the attached log (scroll to the bottom...): Setting up rt4-extension-assettracker (2.0.0~b2-4) ... upgrading the RT database for Asset Tracker updating database schema for 1.2.4...command failed with code 2 postinst script aborted dpkg: error processing rt4-extension-assettracker (--configure): subprocess installed post-installation script returned error exit status 1 Errors were encountered while processing: rt4-extension-assettracker cheers, Andreas rt4-extension-assettracker_2.0.0~b2-4.log.gz Description: GNU Zip compressed data --- End Message --- --- Begin Message --- On 2012-11-06 20:21, Andreas Beckmann wrote: > Control: fixed -1 2.0.0~b2-5 > > On 2012-11-06 19:49, Niels Thykier wrote: >> Currently rt4-extension-assettracker is considered an RC-buggy leaf >> package[0] and will eventually be removed from testing unless this RC >> bug is dealt with (fixed, downgraded etc.). > > cannot reproduce this problem with piuparts :-) > > this was recently added: > > rt-extension-assettracker (2.0.0~b2-5) unstable; urgency=low > * Miscellaneous bugfixes from upstream repository > > [...] > > and schema.mysql looks like a good candidate for fixing such a thing :-) > > > Andreas Okay, thanks. I will close the bug then. Thank you, ~Niels--- End Message ---
Bug#690409: [php-maint] Bug#690409: php5-xcache: upgrades clobber local changes to xcache.ini
On 11/01/2012 12:51 AM, intrigeri wrote: > I am not sure this would > be suitable for a freeze exception, if it does not fix a RC bug. You don't need a bug to be RC to ask for a freeze exception. It's often allowed (and welcome) to fix non-RC bugs! Just get in touch with the release team to check. My guts are telling me that this kind of fix would be accepted easily. Thomas -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#676141: rt4-extension-assettracker:, fails to upgrade from wheezy: updating database schema for 1.2.4...command, failed with code 2
Control: fixed -1 2.0.0~b2-5 On 2012-11-06 19:49, Niels Thykier wrote: > Currently rt4-extension-assettracker is considered an RC-buggy leaf > package[0] and will eventually be removed from testing unless this RC > bug is dealt with (fixed, downgraded etc.). cannot reproduce this problem with piuparts :-) this was recently added: rt-extension-assettracker (2.0.0~b2-5) unstable; urgency=low * Miscellaneous bugfixes from upstream repository $ diffstat debian/patches/misc-bugfixes etc/schema.mysql | 16 +- html/AssetTracker/Admin/Elements/ObjectCustomFields |3 - html/AssetTracker/Elements/AddLinks |5 ++- html/AssetTracker/Elements/SelectAssets |2 - html/AssetTracker/Elements/SelectType|3 - html/AssetTracker/Search/Bulk.html |2 - html/AssetTracker/Search/Results.html|4 ++ html/Callbacks/AssetTracker/Elements/Tabs/Privileged |8 ++--- html/Search/Asset.html |6 +++ lib/RTx/AssetTracker/Assets_Overlay.pm | 20 lib/RTx/AssetTracker/Transaction_Overlay.pm | 30 +++ 11 files changed, 66 insertions(+), 33 deletions(-) and schema.mysql looks like a good candidate for fixing such a thing :-) Andreas -- 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#676141: rt4-extension-assettracker:, fails to upgrade from wheezy: updating database schema for 1.2.4...command, failed with code 2
Processing control commands: > fixed -1 2.0.0~b2-5 Bug #676141 [rt4-extension-assettracker] rt4-extension-assettracker: fails to upgrade from wheezy: updating database schema for 1.2.4...command failed with code 2 Marked as fixed in versions rt-extension-assettracker/2.0.0~b2-5. -- 676141: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=676141 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#692492: ITO: Orphaning audit package
Package: auditd Severity: serious Version: 1:1.7.18-1.1 Hi, I've tried to enter in contact with Philipp Matthias regarding the status of the audit package. I've sent a first mail a bit more than a month ago and a second one 15 days later. But I unfortunately didn't get any answer so far. The last maintainer upload for this package has been done a bit more than a year ago. In the mean time, there was an attempt of NMU to upgrade the package to a newer version (which has been reverted by a 3rd party) and an other NMU (with maintainer approval) to experimental. This version in experimental has currently a 'serious' bug (see #682251). I've prepared an upload for experimental that would fix several issues (including the serious bug) and cleaned up a bit the package. The git repository can be found at: http://git.bigon.be/?p=user/bigon/audit.git;a=summary I'm planning to orphan (and upload my changes for experimental) "soon" if nobody objects. Cheers Laurent Bigonville signature.asc Description: PGP signature
Bug#688259: zangband: modifies shipped files during postinst
Hi, Currently zangband is considered an RC-buggy leaf package[0] and will eventually be removed from testing unless this RC bug is dealt with (fixed, downgraded etc.). Mind you, the deadline listed in [0] is in the past. If I hadn't by chance noticed Drew's mail claiming he would upload a patch, zangband would have been removed like 21 other packages. Drew, if you still intend to upload a fix for this bug, please do it sooner rather than later. Otherwise, consider asking someone to NMU/fix this package for you. ~Niels [0] https://lists.debian.org/debian-devel/2012/10/msg00373.html -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#676141: [request-tracker-maintainers] Bug#676141: rt4-extension-assettracker:, fails to upgrade from wheezy: updating database schema for 1.2.4...command, failed with code 2
Hi, Currently rt4-extension-assettracker is considered an RC-buggy leaf package[0] and will eventually be removed from testing unless this RC bug is dealt with (fixed, downgraded etc.). Mind you, the deadline listed in [0] is in the past. If I hadn't by chance noticed Bradley's mail claiming it is unreproducible, rt4-extension-assettracker would have been removed like 21 other packages. If this bug is unreproducible, please consider tagging it as such and consider downgrading it. Alternatively close it if it has been fixed now. ~Niels [0] https://lists.debian.org/debian-devel/2012/10/msg00373.html -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Processed: tagging 689864
Processing commands for cont...@bugs.debian.org:
> tags 689864 + pending
Bug #689864 {Done: Ben Hutchings } [linux-image-amd64]
linux-image-amd64: Depends un unavailable package
Added tag(s) pending.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
689864: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=689864
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: tagging 688222
Processing commands for cont...@bugs.debian.org:
> tags 688222 + pending
Bug #688222 {Done: Ben Hutchings } [linux-latest] needs
update for 3.2.30-1
Added tag(s) pending.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
688222: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=688222
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#691078: motion keeps restarting after recent upgrade, and appears unable to find some av codec
Processing control commands: > tag -1 - moreinfo Bug #691078 [motion] motion keeps restarting after recent upgrade, and appears unable to find some av codec Removed tag(s) moreinfo. -- 691078: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=691078 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#691078: motion keeps restarting after recent upgrade, and appears unable to find some av codec
Control: tag -1 - moreinfo > >> [UPGRADE] ffmpeg:amd64 7:0.11.1-dmo5 -> 7:1.0-dmo1 > >> [UPGRADE] gstreamer0.10-ffmpeg:amd64 0.10.13-5 -> 1:0.10.13-dmo1 > >> [UPGRADE] libxine2-ffmpeg:amd64 1.2.2-4 -> 1:1.2.2-dmo3 > >> [UPGRADE] libavcodec54:amd64 7:0.11.1-dmo5 -> 7:1.0-dmo1 > >> [UPGRADE] libavdevice54:amd64 7:0.11.1-dmo5 -> 7:1.0-dmo1 > >> [UPGRADE] libavformat54:amd64 7:0.11.1-dmo5 -> 7:1.0-dmo1 > >> [UPGRADE] libavutil51:amd64 7:0.11.1-dmo5 -> 7:1.0-dmo1 > > -dmoN means that you are using packages from deb-multimedia.org. > > Do you have the same problem when you use the packages from Debian > > proper? > Just reinstalled my whole system. On this newly installed and updated > wheezy system, motion doesn't even start capturing properly! Thanks for checking! > I am using the same conf file I was using till several days ago when > it was working fine. Now when I start motion, it just spits out the > initialization lines on the prompt and then does nothing at all. With > the above dmo1 packages it was at least capturing some image, albeit > at a much slower rate. Ok, now we at least know that there is a real problem in some Debian package. Sorry that it won't be me who tackles it, but at least that step is done. Cheers, gregor -- .''`. Homepage: http://info.comodo.priv.at/ - OpenPGP key 0xBB3A68018649AA06 : :' : Debian GNU/Linux user, admin, and developer - http://www.debian.org/ `. `' Member of VIBE!AT & SPI, fellow of the Free Software Foundation Europe `- NP: Eric Clapton: After Midnight signature.asc Description: Digital signature
Bug#682050: Semantics of known_hosts
As far as I can gather from readin sshd(8) and the source code (get_hostfile_hostname_ipaddr in upstream's openssh-6.1p1), at most two key lookups are performed: (a) [Only for protocol version 1] One for the ip address of the remote host, with put_host_port(ntop, port) (b) One for the hostname. (1) If it is an HostKeyAlias, just look for the hostname, (2) else for put_host_port(hostname, port). In the bugzilla entry #910 [1], I found that a fallback option (look for hostname only, if (b.2) fails) was discussed, but if I understand it correctly, this never was included. I also mailed the OpenSSH mailing list to confirm that my analysis is correct [2]. [1] https://bugzilla.mindrot.org/show_bug.cgi?id=910 [2] http://marc.info/?l=openssh-unix-dev&m=135221834426513&w=2 -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#692472: ncpfs - Fails with Cannot convert kernel release "3.6-trunk-amd64" to number
Package: ncpfs Version: 2.2.6-8 Severity: grave ncpmount fails on current Debian kernels with: | Cannot convert kernel release "3.6-trunk-amd64" to number It expects three digits, but this is not longer the case. Bastian -- System Information: Debian Release: wheezy/sid APT prefers testing APT policy: (990, 'testing'), (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.6-trunk-amd64 (SMP w/4 CPU cores) Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#692471: ncpfs - Fails to build to times
Package: ncpfs Version: 2.2.6-8 Severity: serious ncpfs fails to build again: | dpkg-source: info: using options from ncpfs-2.2.6/debian/source/options: --compression=bzip2 --compression-level=9 | dpkg-source: info: using source format `3.0 (quilt)' | dpkg-source: info: building ncpfs using existing ./ncpfs_2.2.6.orig.tar.gz | dpkg-source: warning: ignoring deletion of file config.sub | dpkg-source: warning: ignoring deletion of file config.guess | dpkg-source: warning: ignoring deletion of file po/de.gmo | dpkg-source: warning: ignoring deletion of file po/remove-potcdate.sed | dpkg-source: info: local changes detected, the modified files are: | ncpfs-2.2.6/include/private/libncp-atomic.h | dpkg-source: error: aborting due to unexpected upstream changes, see /tmp/ncpfs_2.2.6-8.1.diff.BkkHwN Bastian -- System Information: Debian Release: wheezy/sid APT prefers testing APT policy: (990, 'testing'), (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.6-trunk-amd64 (SMP w/4 CPU cores) Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#692470: ncpfs - ncpmount fiddles with /etc/mtab
Package: ncpfs Version: 2.2.6-8 Severity: serious ncpmount tries to fiddle with /etc/mtab and gives weird warnings about it. /etc/mtab is a symlink since some time. | Can't get /etc/mtab~ lock file Bastian -- System Information: Debian Release: wheezy/sid APT prefers testing APT policy: (990, 'testing'), (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.6-trunk-amd64 (SMP w/4 CPU cores) Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#692448: marked as done (qemu: system crash on 'libaio1' removal)
Your message dated Tue, 6 Nov 2012 16:57:19 +0200 with message-id and subject line Re: Bug#692448: qemu: system crash on 'libaio1' removal has caused the Debian Bug report #692448, regarding qemu: system crash on 'libaio1' removal 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.) -- 692448: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=692448 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: qemu Version: 0.12.5+dfsg-3squeeze2 Severity: serious Hi, I've just had a system crash a few seconds after I removed 'libaio1 package (declared orphan by deborphan). On KVM systems this is not a problem because its a dependency of qemu-kvm. But on Xen systems (+libvirtd) this package is useless and 'qemu' is enough. I believe 'qemu' should also depend on 'libaio1'. Another alternative is to add the dependency on 'xen-qemu-dm*' packages. Cheers -- System Information: Debian Release: 6.0.6 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 2.6.32-5-xen-amd64 (SMP w/8 CPU cores) Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968) Shell: /bin/sh linked to /bin/dash Versions of packages qemu depends on: ii qemu-system0.12.5+dfsg-3squeeze2 QEMU full system emulation binarie ii qemu-user 0.12.5+dfsg-3squeeze2 QEMU user mode emulation binaries ii qemu-utils 0.12.5+dfsg-3squeeze2 QEMU utilities qemu recommends no packages. Versions of packages qemu suggests: pn qemu-user-static (no description available) -- no debconf information --- End Message --- --- Begin Message --- 2012/11/6 Michael Tokarev : > I think it is time to close this bugreport. Ok. It could have been a bad timing or some other monster (ie. a Dell OMSA restart at the same time). Thanks--- End Message ---
Bug#661471: NMU v2 (was: Re: Bug#661471: bug 661471 gnome-accessibility-themes)
On Tue, Nov 6, 2012 at 9:09 PM, Theppitak Karoonboonyanan wrote: > Re-uploaded to DELAYED/2. The debdiff. Regards, -- Theppitak Karoonboonyanan http://linux.thai.net/~thep/ gnome-themes-standard_3.4.2-2.1.debdiff Description: Binary data
Bug#661471: NMU v2 (was: Re: Bug#661471: bug 661471 gnome-accessibility-themes)
On Tue, Nov 6, 2012 at 8:09 PM, Theppitak Karoonboonyanan wrote: > On Tue, Nov 6, 2012 at 7:53 PM, Michael Biebl wrote: > >> The gnome-themes-standard-common binary package is superfluous. >> Afaics the gettext translations are only required to translate the >> index.theme and background.xml files where the translations are directly >> embedded, so you don't actually need to install the .mo files. >> >> I would thus suggest to simply drop gnome-themes-standard-common. > > I had also found it out before seeing your message. So, I've cancelled the > NMU. > > Anyway, I also stumbled upon this lintian info: > > I: gnome-themes-standard: arch-dep-package-has-big-usr-share 3549kB 99% > > That made me plan to move the non-engine parts into -common instead. > What do you think? > >> Please also make gnome-theme-standard depend on gnome-accessibility-themes. > > OK. I didn't think normal users want those a11y themes, so I hadn't added the > dependency. Will do it now as you suggest, anyway. > >> Also, gnome-accessibility-themes needs a Breaks along with the Replaces. > > OK. Re-uploaded to DELAYED/2. Regards, -- Theppitak Karoonboonyanan http://linux.thai.net/~thep/ -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#692448: qemu: system crash on 'libaio1' removal
On 06.11.2012 17:39, Teodor MICU wrote: > 2012/11/6 Michael Tokarev : >> So, can you start it again when libaio1 is NOT installed? > > Yes, I was able to start the VMs again after the libaio1 removal. I'm > not sure about the full Xen system -- I can't test now. In this case you really do not need/use libaio1, and there's no bug. Why it crashed is another question, again, I can only guess it was a bad luck - like your xen crashed right at the time when your dpkg were removing libaio1 (eg, it triggered some "correct" timing or system load or something else). On qemu side, everything is declared exactly as it should be. Qemu package does not use libaio1 and libaio1 is not listed in dependencies -- this is exactly how things were supposed to be and how they are now. Note again: even removing a library which is actually in use will NOT result in the application in question crashing. I think it is time to close this bugreport. Thanks, /mjt -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#692448: qemu: system crash on 'libaio1' removal
2012/11/6 Michael Tokarev : > So, can you start it again when libaio1 is NOT installed? Yes, I was able to start the VMs again after the libaio1 removal. I'm not sure about the full Xen system -- I can't test now. Cheers -- 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#689790: msva-perl: modifies conffiles during upgrade from squeeze (policy 10.7.3): /etc/X11/Xsession.d/70monkeysphere_use-validation-agent
Processing control commands: > notfound -1 0.8-2 Bug #689790 [msva-perl] msva-perl: modifies conffiles during upgrade from squeeze (policy 10.7.3): /etc/X11/Xsession.d/70monkeysphere_use-validation-agent No longer marked as found in versions msva-perl/0.8-2. > notfound -1 0.9.1-1 Bug #689790 [msva-perl] msva-perl: modifies conffiles during upgrade from squeeze (policy 10.7.3): /etc/X11/Xsession.d/70monkeysphere_use-validation-agent No longer marked as found in versions msva-perl/0.9.1-1. > close -1 Bug #689790 [msva-perl] msva-perl: modifies conffiles during upgrade from squeeze (policy 10.7.3): /etc/X11/Xsession.d/70monkeysphere_use-validation-agent Marked Bug as done -- 689790: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=689790 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#689790: msva-perl: modifies conffiles during upgrade from squeeze (policy 10.7.3): /etc/X11/Xsession.d/70monkeysphere_use-validation-agent
Control: notfound -1 0.8-2 Control: notfound -1 0.9.1-1 Control: close -1 On 2012-10-07 01:41, Daniel Kahn Gillmor wrote: > On 10/06/2012 06:09 PM, Andreas Beckmann wrote: > > [ ... incredible debugging saga snipped ... ] > >> going to look into dpkg :-) >> >> ... and suggesting a one-line fix :-) > > wow. thanks! I'll keep an eye on this. if you have any suggestions > for things you think i should improve, please let me know. > > much appreciation for tracking this down. no longer reproducible after the fixed dpkg has reached testing Andreas -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#692448: qemu: system crash on 'libaio1' removal
On 06.11.2012 17:02, Teodor MICU wrote: > 2012/11/6 Michael Tokarev : >> On 06.11.2012 15:40, Teodor wrote: >>> I've just had a system crash a few seconds after I removed 'libaio1 >>> package (declared orphan by deborphan). >> >> What kind of crash? Crash of what, exactly? What you were running? > > Debian Linux 6.0 (amd64) on top of Xen 4.0 hypervisor. > > reboot system boot 2.6.32-5-xen-amd Tue Nov 6 02:59 - 05:01 (02:02) > root pts/2vpn-120.DOMAIN Tue Nov 6 02:27 - crash (00:32) So, can you start it again when libaio1 is NOT installed? Note that after you remove a library - any library - applications linked against it will continue running just fine. You wont be able to start new applications linked to this library, -- that's for sure, but already running will continue, since the library will still be in memory and on disk (but deleted). >> None of qemu-system or qemu-user binaries are linked with libaio. >> libaio1 is not used and hence not needed. >> >> Note that qemu package - against which you filed the bugreport - >> is a meta-package, it does not use any library at all. > > # aptitude why qemu > i xen-qemu-dm-4.0 Depends qemu-system | qemu qemu depends on qemu-system. I don't know what xen-qemu-dm-4.0 uses for its qemu component. I think it too comes with integrated qemu, just another variant of it (like qemu-kvm is yet another variant). > # aptitude why libaio1 > i libvirt-bin Recommends qemu-kvm | qemu (>= 0.9.1) > p qemu-kvmDependslibaio1 So libaio1 is used only by qemu-kvm (correctly), not by any other installed packages. Which is exactly what I tried to say initially. > Maybe qemu is not the right package, then which is the right pkg? I dunno - in particular, I don't know how xen uses qemu and if it uses its own copy or not. I can _guess_ this dependency is only for some support files, not for qemu-system binaries, but that's just a guess. >>> On KVM systems this is not >>> a problem because its a dependency of qemu-kvm. But on Xen systems >>> (+libvirtd) this package is useless and 'qemu' is enough. >> >> Which package is useless? > > qemu-kvm is useless on a Xen hypervisor. Ah ok. I guess qemu-system is also useless, if not some support files included in there. >> xen-qemu-dm* packages are not relevant for qemu. >> >> Please describe your issue in a bit more details. Currently >> what you wrote makes no sense, sorry. > > Do you need more info? I don't see any issue so far. Especially since you're having issue with xen which - most likely - does not use separate qemu package at all. Thanks, /mjt -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#661471: NMU v2 (was: Re: Bug#661471: bug 661471 gnome-accessibility-themes)
On Tue, Nov 6, 2012 at 7:53 PM, Michael Biebl wrote: > The gnome-themes-standard-common binary package is superfluous. > Afaics the gettext translations are only required to translate the > index.theme and background.xml files where the translations are directly > embedded, so you don't actually need to install the .mo files. > > I would thus suggest to simply drop gnome-themes-standard-common. I had also found it out before seeing your message. So, I've cancelled the NMU. Anyway, I also stumbled upon this lintian info: I: gnome-themes-standard: arch-dep-package-has-big-usr-share 3549kB 99% That made me plan to move the non-engine parts into -common instead. What do you think? > Please also make gnome-theme-standard depend on gnome-accessibility-themes. OK. I didn't think normal users want those a11y themes, so I hadn't added the dependency. Will do it now as you suggest, anyway. > Also, gnome-accessibility-themes needs a Breaks along with the Replaces. OK. Regards, -- Theppitak Karoonboonyanan http://linux.thai.net/~thep/ -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#692448: qemu: system crash on 'libaio1' removal
2012/11/6 Michael Tokarev : > On 06.11.2012 15:40, Teodor wrote: >> I've just had a system crash a few seconds after I removed 'libaio1 >> package (declared orphan by deborphan). > > What kind of crash? Crash of what, exactly? What you were running? Debian Linux 6.0 (amd64) on top of Xen 4.0 hypervisor. reboot system boot 2.6.32-5-xen-amd Tue Nov 6 02:59 - 05:01 (02:02) root pts/2vpn-120.DOMAIN Tue Nov 6 02:27 - crash (00:32) > None of qemu-system or qemu-user binaries are linked with libaio. > libaio1 is not used and hence not needed. > > Note that qemu package - against which you filed the bugreport - > is a meta-package, it does not use any library at all. # aptitude why qemu i xen-qemu-dm-4.0 Depends qemu-system | qemu # aptitude why libaio1 i libvirt-bin Recommends qemu-kvm | qemu (>= 0.9.1) p qemu-kvmDependslibaio1 Maybe qemu is not the right package, then which is the right pkg? >> On KVM systems this is not >> a problem because its a dependency of qemu-kvm. But on Xen systems >> (+libvirtd) this package is useless and 'qemu' is enough. > > Which package is useless? qemu-kvm is useless on a Xen hypervisor. > xen-qemu-dm* packages are not relevant for qemu. > > Please describe your issue in a bit more details. Currently > what you wrote makes no sense, sorry. Do you need more info? Cheers -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#661471: NMU v2 (was: Re: Bug#661471: bug 661471 gnome-accessibility-themes)
On 06.11.2012 12:05, Theppitak Karoonboonyanan wrote: > On Wed, Oct 31, 2012 at 5:34 PM, Theppitak Karoonboonyanan > wrote: >> On Wed, Aug 29, 2012 at 10:35 PM, Theppitak Karoonboonyanan >> wrote: >>> On Mon, Aug 13, 2012 at 3:01 PM, Theppitak Karoonboonyanan >>> wrote: So, I agree with splitting the gnome-accessibility-themes binary. >>> >>> Any progress? If not, I'm proposing another NMU, which: >>> - Splits a11y themes into gnome-accessibility-themes binary >>> - Splits the shared translation files into gnome-themes-standard-common >>> - Makes both theme packages depend on -common >>> - Declares gnome-accessibility-themes and gnome-themes-standard-common >>> as Replaces: the old gnome-themes-standard >>> - Drops Replaces: from gnome-themes-standard >>> >>> Debdiff is attached. >>> >>> However, some warnings are found during the upgrade test: >>> >>> ---8<--- >>> Preparing to replace gnome-themes-standard 3.4.2-1 (using >>> gnome-themes-standard_3.4.2-1.1_amd64.deb) ... >>> Unpacking replacement gnome-themes-standard ... >>> dpkg: warning: unable to delete old directory >>> '/usr/share/icons/HighContrast': Directory not empty >>> dpkg: warning: unable to delete old directory >>> '/usr/share/icons/LowContrast': Directory not empty >>> dpkg: warning: unable to delete old directory >>> '/usr/share/icons/HighContrastInverse': Directory not empty >>> ---8<--- >>> >>> The remaining files in these directories are "icon-theme.cache". >>> Any suggestion on how to clear them properly? >> >> It seems this does not happen with clean installs. So, it may not be an >> issue. >> Could I do the NMU, then? > > Uploaded to DELAYED/2. > > Without response for a long time, I assume it's qualified NMU, despite the > intrusive change. The gnome-themes-standard-common binary package is superfluous. Afaics the gettext translations are only required to translate the index.theme and background.xml files where the translations are directly embedded, so you don't actually need to install the .mo files. I would thus suggest to simply drop gnome-themes-standard-common. Please also make gnome-theme-standard depend on gnome-accessibility-themes. Also, gnome-accessibility-themes needs a Breaks along with the Replaces. -- Why is it that all of the instruments seeking intelligent life in the universe are pointed away from Earth? signature.asc Description: OpenPGP digital signature
Bug#684713: marked as done (parted: support for partitioned MD devices)
Your message dated Tue, 6 Nov 2012 12:25:45 + with message-id <20121106122545.ga32...@riva.dynamic.greenend.org.uk> and subject line Re: Bug#684713: bug 684713 - support for partitioned MD devices has caused the Debian Bug report #684713, regarding parted: support for partitioned MD devices 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.) -- 684713: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=684713 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: parted Version: 2.3-10 Severity: serious Tags: patch wheezy sid Background: I have added support to the debian installer for installation on Intel Matrix Raid (imsm) arrays as supported by mdadm (I'll be submitting patches to debian-boot soon). When installing on such an array, partitions are created directly on the array (e.g. /dev/md0). Before kernel 2.6.28, partitionable md arrays were seperate from 'normal' md arrays (different dev_t's), but since 2.6.28 that has been consolidated. However, there is one minor oversight/bug in the kernel: the sysfs "range" key is still set to "1" for md arrays. That means libparted thinks that it's not possible to partition that device, where in fact it is. The attached patch reckognizes that situation: if running on a kernel >= 2.6.28, and the device is a PED_DEVICE_MD, and the sysfs 'range' key is set to '1', _device_get_partition_range() returns MAX_NUM_PARTS instead. Please consider this patch for wheezy. Suggested changelog entry: * starting at kernel 2.6.28, MD devices can be partitioned, but the sysfs "range" key only shows support for one partition/device. Ignore that setting if it's set to "1" and the kernel version is >= 2.6.28. Mike. Index: parted-2.3/libparted/arch/linux.c === --- parted-2.3.orig/libparted/arch/linux.c 2010-05-10 10:57:54.0 + +++ parted-2.3/libparted/arch/linux.c 2012-08-05 13:24:14.449768577 + @@ -2415,6 +2415,11 @@ ok = fscanf(fp, "%d", &range) == 1; fclose(fp); + /* starting at 2.6.28 partitions are OK but "range" doesn't show it */ + if (dev->type == PED_DEVICE_MD && range == 1 && + _get_linux_version() >= KERNEL_VERSION (2,6,28)) + ok = 0; + /* (range <= 0) is none sense.*/ return ok && range > 0 ? range : MAX_NUM_PARTS; } --- End Message --- --- Begin Message --- Source: parted Source-Version: 2.3-11 On Wed, Sep 05, 2012 at 05:27:04PM +0200, Miquel van Smoorenburg wrote: > Is anyone planning to upload a new parted version to the > archive anytime soon? If not, I'll probably do an NMU to fix > bug 684713. Thanks for this NMU, and sorry for the very delayed response. I've pushed your change to our git repository. Closing this bug now since (I assume) the earlier BTS snafu meant that it didn't get closed properly earlier. -- Colin Watson [cjwat...@debian.org]--- End Message ---
Bug#692455: jspwiki: modifies conffiles (policy 10.7.3): /etc/jspwiki/jspwiki.properties
Package: jspwiki Version: 2.8.0-5 Severity: serious User: debian...@lists.debian.org Usertags: piuparts Hi, during a test with piuparts I noticed your package modifies conffiles. This is forbidden by the policy, see http://www.debian.org/doc/debian-policy/ch-files.html#s-config-files 10.7.3: "[...] The easy way to achieve this behavior is to make the configuration file a conffile. [...] This implies that the default version will be part of the package distribution, and must not be modified by the maintainer scripts during installation (or at any other time)." Note that once a package ships a modified version of that conffile, dpkg will prompt the user for an action how to handle the upgrade of this modified conffile (that was not modified by the user). Further in 10.7.3: "[...] must not ask unnecessary questions (particularly during upgrades) [...]" If a configuration file is customized by a maintainer script after having asked some debconf questions, it may not be marked as a conffile. Instead a template could be installed in /usr/share and used by the postinst script to fill in the custom values and create (or update) the configuration file (preserving any user modifications!). This file must be removed during postrm purge. ucf(1) may help with these tasks. See also http://wiki.debian.org/DpkgConffileHandling In https://lists.debian.org/debian-devel/2012/09/msg00412.html and followups it has been agreed that these bugs are to be filed with severity serious. debsums reports modification of the following files, from the attached log (scroll to the bottom...): /etc/jspwiki/jspwiki.properties cheers, Andreas jspwiki_2.8.0-5.log.gz Description: GNU Zip compressed data
Processed: Re: jspwiki does depend on tomcat6
Processing control commands: > notfound -1 2.8.0-5 Bug #656153 [jspwiki] jspwiki: postinst failure: chown: invalid user: `tomcat6' No longer marked as found in versions jspwiki/2.8.0-5. > fixed -1 2.8.0-5 Bug #656153 [jspwiki] jspwiki: postinst failure: chown: invalid user: `tomcat6' Marked as fixed in versions jspwiki/2.8.0-5. > close -1 Bug #656153 [jspwiki] jspwiki: postinst failure: chown: invalid user: `tomcat6' Marked Bug as done -- 656153: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=656153 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#656153: jspwiki does depend on tomcat6
Control: notfound -1 2.8.0-5 Control: fixed -1 2.8.0-5 Control: close -1 On Tuesday, 10. July 2012 05:38:06 tony mancill wrote: > In looking into this, I was confused to discover that the latest version > of jspwiki 2.8.0-5 uploaded to unstable actually does depend on tomcat6, > but didn't close #656153 in the changelog. (This is certainly my So let's close this bug properly. The found in -5 seems to be spurious, I cannot reproduce it. Andreas -- 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#692448: qemu: system crash on 'libaio1' removal
Processing control commands: > tags -1 unreproducible moreinfo Bug #692448 [qemu] qemu: system crash on 'libaio1' removal Added tag(s) unreproducible and moreinfo. -- 692448: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=692448 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#692448: qemu: system crash on 'libaio1' removal
Control: tags -1 unreproducible moreinfo On 06.11.2012 15:40, Teodor wrote: > Package: qemu > Version: 0.12.5+dfsg-3squeeze2 > Severity: serious > > Hi, > > I've just had a system crash a few seconds after I removed 'libaio1 > package (declared orphan by deborphan). What kind of crash? Crash of what, exactly? What you were running? None of qemu-system or qemu-user binaries are linked with libaio. libaio1 is not used and hence not needed. Note that qemu package - against which you filed the bugreport - is a meta-package, it does not use any library at all. > On KVM systems this is not > a problem because its a dependency of qemu-kvm. But on Xen systems > (+libvirtd) this package is useless and 'qemu' is enough. Which package is useless? > I believe 'qemu' should also depend on 'libaio1'. qemu can be made dependent on libaio1 if it were linked with libaio1. For this, it needs to contain at least one binary, which it does not. Note that library dependencies are automatic in debian -- once a binary is linked with a library, the corresponding dependency is reflected in the package control information, so the only thing necessary to do is to actually _use_ the library. > Another alternative > is to add the dependency on 'xen-qemu-dm*' packages. xen-qemu-dm* packages are not relevant for qemu. Please describe your issue in a bit more details. Currently what you wrote makes no sense, sorry. /mjt -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#692448: qemu: system crash on 'libaio1' removal
Package: qemu Version: 0.12.5+dfsg-3squeeze2 Severity: serious Hi, I've just had a system crash a few seconds after I removed 'libaio1 package (declared orphan by deborphan). On KVM systems this is not a problem because its a dependency of qemu-kvm. But on Xen systems (+libvirtd) this package is useless and 'qemu' is enough. I believe 'qemu' should also depend on 'libaio1'. Another alternative is to add the dependency on 'xen-qemu-dm*' packages. Cheers -- System Information: Debian Release: 6.0.6 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 2.6.32-5-xen-amd64 (SMP w/8 CPU cores) Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968) Shell: /bin/sh linked to /bin/dash Versions of packages qemu depends on: ii qemu-system0.12.5+dfsg-3squeeze2 QEMU full system emulation binarie ii qemu-user 0.12.5+dfsg-3squeeze2 QEMU user mode emulation binaries ii qemu-utils 0.12.5+dfsg-3squeeze2 QEMU utilities qemu recommends no packages. Versions of packages qemu suggests: pn qemu-user-static (no description available) -- 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#661471: NMU v2 (was: Re: Bug#661471: bug 661471 gnome-accessibility-themes)
On Wed, Oct 31, 2012 at 5:34 PM, Theppitak Karoonboonyanan wrote: > On Wed, Aug 29, 2012 at 10:35 PM, Theppitak Karoonboonyanan > wrote: >> On Mon, Aug 13, 2012 at 3:01 PM, Theppitak Karoonboonyanan >> wrote: >>> So, I agree with splitting the gnome-accessibility-themes binary. >> >> Any progress? If not, I'm proposing another NMU, which: >> - Splits a11y themes into gnome-accessibility-themes binary >> - Splits the shared translation files into gnome-themes-standard-common >> - Makes both theme packages depend on -common >> - Declares gnome-accessibility-themes and gnome-themes-standard-common >> as Replaces: the old gnome-themes-standard >> - Drops Replaces: from gnome-themes-standard >> >> Debdiff is attached. >> >> However, some warnings are found during the upgrade test: >> >> ---8<--- >> Preparing to replace gnome-themes-standard 3.4.2-1 (using >> gnome-themes-standard_3.4.2-1.1_amd64.deb) ... >> Unpacking replacement gnome-themes-standard ... >> dpkg: warning: unable to delete old directory >> '/usr/share/icons/HighContrast': Directory not empty >> dpkg: warning: unable to delete old directory >> '/usr/share/icons/LowContrast': Directory not empty >> dpkg: warning: unable to delete old directory >> '/usr/share/icons/HighContrastInverse': Directory not empty >> ---8<--- >> >> The remaining files in these directories are "icon-theme.cache". >> Any suggestion on how to clear them properly? > > It seems this does not happen with clean installs. So, it may not be an issue. > Could I do the NMU, then? Uploaded to DELAYED/2. Without response for a long time, I assume it's qualified NMU, despite the intrusive change. Regards, -- Theppitak Karoonboonyanan http://linux.thai.net/~thep/ -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#689257: marked as done (roundup: deletes conffiles during postrm remove (policy 10.7.3))
Your message dated Tue, 06 Nov 2012 10:47:38 + with message-id and subject line Bug#689257: fixed in roundup 1.4.20-1.1 has caused the Debian Bug report #689257, regarding roundup: deletes conffiles during postrm remove (policy 10.7.3) 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.) -- 689257: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=689257 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: roundup Version: 1.4.20-1 Severity: serious User: debian...@lists.debian.org Usertags: piuparts Hi, during a test with piuparts I noticed your package deletes the conffiles /etc/init.d/roundup-dirs and /etc/init.d/roundup during postrm remove. This is forbidden by policy 10.7.3: http://www.debian.org/doc/debian-policy/ch-files.html#s-config-files "[...] configuration files must be preserved when the package is removed, and only deleted when the package is purged [...]" As conffiles are not restored on a subsequent reinstallation (deleting a conffile is a local customization and will be preserved on upgrades etc., they will be missing after this sequence: install roundup remove roundup install roundup >From the attached log: 0m44.9s ERROR: FAIL: debsums reports modifications inside the chroot: debsums: missing file /etc/init.d/roundup-dirs (from roundup package) debsums: missing file /etc/init.d/roundup (from roundup package) Cheers, Andreas roundup_1.4.20-1.log.gz Description: GNU Zip compressed data --- End Message --- --- Begin Message --- Source: roundup Source-Version: 1.4.20-1.1 We believe that the bug you reported is fixed in the latest version of roundup, 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 689...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Salvatore Bonaccorso (supplier of updated roundup 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: SHA512 Format: 1.8 Date: Wed, 10 Oct 2012 16:07:43 +0200 Source: roundup Binary: roundup Architecture: source all Version: 1.4.20-1.1 Distribution: unstable Urgency: low Maintainer: Kai Storbeck Changed-By: Salvatore Bonaccorso Description: roundup- an issue-tracking system Closes: 689257 Changes: roundup (1.4.20-1.1) unstable; urgency=low . * Non-maintainer upload. * Remove conffiles only on purge. Fix "deletes conffiles during postrm remove (policy 10.7.3)" as roundup removed /etc/init.d/roundup, /etc/init.d/roundup-dirs and init script links also on remove, abort-install and disappear calls to postrm. (Closes: #689257) Checksums-Sha1: 14596d07a2207d5ef5a93baed9753644f95c746b 1779 roundup_1.4.20-1.1.dsc d64d41e78ad2cb306b36b804a764e8d79b40b0f7 64179 roundup_1.4.20-1.1.debian.tar.gz 9697f08777d192c15d4c5f074a99721fc4f8bca6 1527072 roundup_1.4.20-1.1_all.deb Checksums-Sha256: 16372dcf58ec0f8a52993ee167f06375d3554f21637c73e9fa5f6f3cb334ddd4 1779 roundup_1.4.20-1.1.dsc bb3e0b9833931a405c0c9ee2f41683c306269912f4b1e6f2742e892797352636 64179 roundup_1.4.20-1.1.debian.tar.gz 7b8af4407e942a032611950c028904fd3d31d64d4c6872214f500dff3768782b 1527072 roundup_1.4.20-1.1_all.deb Files: bffd873fee18768911d676c92245ee90 1779 web optional roundup_1.4.20-1.1.dsc 5c2c6972306cd386cdf6b44164ed312c 64179 web optional roundup_1.4.20-1.1.debian.tar.gz 674b0e63d216e017cc24d288e73da810 1527072 web optional roundup_1.4.20-1.1_all.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.12 (GNU/Linux) iQIcBAEBCgAGBQJQlkJNAAoJEHidbwV/2GP+fAwQAJm5Gqu9PYt/DcNwRcwgyUT8 H4fundIBQZFGhwxN68Pf9bztbfUS2HEYh0VxkRH/TVc5+SUxdO16bxK2PkfmqQ+m ktobF+ucSC0yEWqLB6h7y3SviF/bTDRUGyHo8fjq0mHP+7jfmJ0z9jOBwFAgb55+ 2kdRNvT2m1ToXJ6+ii0HwJ4g+8t/RYcs18NPanL/yq0rh8bfv3CzP3G/YOqqFW88 ZJL6/6vO4PJV9WoG6WmNFe2D4I2CBxoA4eKoQ4kskBNRnkOYE034BMRDZ8mL/tHA +MnvtzvQEnW2gd1qu+LNQVvrMtXUJCUFwcYKpw29NvwPklaA3BuJyGUwtQ2tHTQo jvZXxz6muRJy+tX7djK6KskoiXrTu7zAwRpxgV69V+hvkoSu1kMJvUUuuaVuKEtk CZ+nroPSjdcmpcrzr7V7vTvgvZnkwW1QcqipbfHHXhgU3qViFoZW1bz4aYGHlR7t j0MGMRlYbbNeNuBOspRaLfQsEac85yhFde1+sojYEqXfu8Z2pv7nhJht23HOhjsq xar2IFDyFgE5SJNJ12WwNQisWQ8p2IO+6I5NXXNjepmb+UxVwcJfGMjuQLWq8Ls5 nujk6jdWFOZbNrPvyLplzXeF5ppDBSKQN2JQPs2pPuhitmLACecCJ70uWwHck0QB Na5fv0kus8Bwn0QanSfr =5Hc
Bug#692440: tomcat7: CVE-2012-2733 CVE-2012-3439
Package: tomcat7 Severity: grave Tags: security Justification: user security hole Please see http://tomcat.apache.org/security-7.html Since Wheezy is frozen, please apply isolated security fixes instead of updating to a new upstream release. Cheers, Moritz -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#692439: tomcat6: CVE-2012-2733 CVE-2012-3439
Package: tomcat6 Severity: grave Tags: security Justification: user security hole Please see http://tomcat.apache.org/security-6.html Since Wheezy is frozen, please apply isolated security fixes and do not update to a new upstream release. BTW, is it really necessary to have both tomcat6 and tomcat7 in Wheezy? Shouldn't tomcat6 be dropped in favour of tomcat7? Cheers, Moritz -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#692435: gegl: CVE-2012-4433 - Integer overflow, leading to heap-based buffer overflow by parsing PPM image headers
Package: gegl Severity: grave Tags: security Justification: user security hole Hi, please see : http://seclists.org/oss-sec/2012/q4/215 Can you confirm if any of the Debian packages are affected? Cheers, luciano -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#692434: yui: CVE-2012-5475 - YUI 2.x security issue regarding embedded SWF files
Package: yui Severity: grave Tags: security Justification: user security hole Hi, please see : http://www.yuiblog.com/blog/2012/10/30/security-announcement-swf-vulnerability- in-yui-2/ Are vulnerable versions in Debian? Cheers, luciano -- 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#692429: libpython3.3-dev: fatal error: pyconfig.h: No such file or directory
Processing commands for cont...@bugs.debian.org: > reassign 692429 blender Bug #692429 [libpython3.3-dev] libpython3.3-dev: fatal error: pyconfig.h: No such file or directory Bug reassigned from package 'libpython3.3-dev' to 'blender'. No longer marked as found in versions python3.3/3.3.0-2. Ignoring request to alter fixed versions of bug #692429 to the same values previously set > severity 692429 important Bug #692429 [blender] libpython3.3-dev: fatal error: pyconfig.h: No such file or directory Severity set to 'important' from 'grave' > thanks Stopping processing here. Please contact me if you need assistance. -- 692429: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=692429 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#692429: libpython3.3-dev: fatal error: pyconfig.h: No such file or directory
reassign 692429 blender severity 692429 important thanks Am 06.11.2012 07:10, schrieb IRIE Shinsuke: > Package: libpython3.3-dev > Version: 3.3.0-2 > Severity: grave > > I attempted to build Blender trunk using python3.3-dev but got the > following error: > > [ 58%] Building C object > source/blender/python/intern/CMakeFiles/bf_python.dir/gpu.c.o > In file included from > /home/irie/Subversion/Blender/blender/source/blender/python/intern/gpu.c:40:0: > /usr/include/python3.3m/Python.h:8:22: fatal error: pyconfig.h: No such file > or directory > compilation terminated. > > > '#include "pyconfig.h"' in Python.h assumed that pyconfig.h is in > /usr/include/python3.3m, but it's actually placed in > /usr/include/x86_64-linux-gnu/python3.3m. > > Probably most of all programs using libpython3.3 cannot be built for > this bug. no, only these which use home-grown configure tests. Please use python3.3-config --includes or pkgconfig. -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Processed: reassign 674156 to glib-2.0
Processing commands for cont...@bugs.debian.org: > reassign 674156 glib-2.0 Bug #674156 [gstreamer0.10-plugins-good] gstreamer0.10-plugins-good: rtpmp2tpay not working on some architectures Bug reassigned from package 'gstreamer0.10-plugins-good' to 'glib-2.0'. Warning: Unknown package 'glib-2.0' Warning: Unknown package 'glib-2.0' No longer marked as found in versions gst-plugins-good0.10/0.10.31-2. Warning: Unknown package 'glib-2.0' Warning: Unknown package 'glib-2.0' Ignoring request to alter fixed versions of bug #674156 to the same values previously set Warning: Unknown package 'glib-2.0' > thanks Stopping processing here. Please contact me if you need assistance. -- 674156: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=674156 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#674156: alignment issue
reassign 674156 glib-2.0
thanks,
On Fri, Oct 19, 2012 at 10:32:46PM +0900, Koichi Akabe wrote:
> > (gst-plugin-scanner:961): GLib-GObject-WARNING **: specified instance
> > size for type `GstRtpAC3Depay' is smaller than the parent type's
> > `GstBaseRTPDepayload' instance size
Digging through this it turned out that GStaticMutex changed size since
squeeze... When running the following test program:
#include
#include
#define SIZE(x) printf (#x ": %"G_GSIZE_FORMAT"\n", sizeof (x))
int
main (int argc, char **argv)
{
SIZE (GMutex *);
SIZE (double);
SIZE (pthread_mutex_t);
SIZE (GStaticMutex);
SIZE (GStaticRecMutex);
SIZE (struct { GMutex *a; union { char pad[24] ; char d; }; });
return 0;
}
On squeeze (armel):
GMutex *: 4
double: 8
pthread_mutex_t: 24
GStaticMutex: 32
GStaticRecMutex: 48
struct { GMutex *a; union { char pad[24] ; double d; }; }: 32
On wheezy (armel):
GMutex *: 4
double: 8
pthread_mutex_t: 24
GStaticMutex: 28
GStaticRecMutex: 40
struct { GMutex *a; union { char pad[24] ; double d; }; }: 32
Digging futher and futher on squeese GStaticMutex was defined as:
struct _GStaticMutex
{
struct _GMutex *runtime_mutex;
union {
char pad[24];
double dummy_double;
void *dummy_pointer;
long dummy_long;
} static_mutex;
};
While on wheezy:
typedef struct
{
GMutex *mutex;
#ifndef G_OS_WIN32
/* only for ABI compatibility reasons */
pthread_mutex_t unused;
#endif
} GStaticMutex;
Even though both pthread_mutex_t and the earlier union are 24 bytes themselves,
because of the double in the union it gets aligned to a multiple of 8 on ARM,
causing 4 bytes of extra padding to be added. Which in turns makes the old
GStaticMutex struct 4 bytes bigger then the current one...
This obviously breaks ABI on these platforms, not only of glib but also of
libraries which have a GStaticMutex embedded in their public structs in some
way.
I'm not sure what to do at this point... One option would be to patch
glib-2.0 so it's at least ABI compatible again with squeeze again, but it's
unlikely other distributions would follow (so we would be incompatible with
others). On the other hand this might not matter so much for arm.
Whatever we do, we do need to ensure that all affected software gets compiled
against whatever final solution we pick.
--
The light of a hundred stars does not equal the light of the moon.
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Processed: notfound 678786 haskell-llvm-base/3.0.1.0-1
Processing commands for cont...@bugs.debian.org:
> notfound 678786 haskell-llvm-base/3.0.1.0-1
Bug #678786 {Done: Joachim Breitner }
[src:haskell-llvm-base] haskell-llvm-base: FTBFS: error: 'class
llvm::SMDiagnostic' has no member named 'Print'
No longer marked as found in versions haskell-llvm-base/3.0.1.0-1.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
678786: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=678786
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#692367: [Pkg-gmagick-im-team] Bug#692367: patches
On Mon, Nov 5, 2012 at 10:28 PM, Vincent Danen wrote: > Would it be possible to get the patches noted to fix these flaws? Other > distros would be interested in it as well (as would upstream, I > imagine). Has this been reported upstream yet? They have been fixed upstream. it is only a backport. The backport are joined here > -- > Vincent Danen / Red Hat Security Response Team > ___ > Pkg-gmagick-im-team mailing list > pkg-gmagick-im-t...@lists.alioth.debian.org > http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-gmagick-im-team 0005-Memory-leak-after-setjmp-used-variable-need-to-be-vo.patch Description: Binary data 0006-Fix-a-memory-leak-in-webp-handling.patch Description: Binary data 0007-Magick-fix-a-memory-leak.patch Description: Binary data
