Bug#684373: marked as done (spamassassin: fails to install, purge, and install again)
Your message dated Tue, 14 Aug 2012 06:04:49 + with message-id and subject line Bug#684373: fixed in spamassassin 3.3.2-4 has caused the Debian Bug report #684373, regarding spamassassin: fails to install, purge, and install again 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.) -- 684373: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=684373 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: spamassassin Version: 3.3.2-3.1 Severity: serious User: debian...@lists.debian.org Usertags: piuparts Hi, during a test with piuparts I noticed your package failed to install, remove+purge, and install again. Like a plain failure on initial install this makes the package too buggy for a release, thus the severity. This is often a problem with the home directory of a system user: the user is not deleted during purge (which is fine), but the home directory is removed. Since the user already exists on the next installation, adduser won't recreate the home. >From the attached log (scroll to the bottom...): [...] 1m32.7s INFO: Reinstalling after purge [...] Selecting previously unselected package spamassassin. (Reading database ... 9417 files and directories currently installed.) Unpacking spamassassin (from .../spamassassin_3.3.2-3.1_all.deb) ... Setting up spamassassin (3.3.2-3.1) ... chown: cannot access `/var/lib/spamassassin': No such file or directory dpkg: error processing spamassassin (--configure): subprocess installed post-installation script returned error exit status 1 Errors were encountered while processing: spamassassin cheers, Andreas spamassassin_3.3.2-3.1.log.gz Description: GNU Zip compressed data --- End Message --- --- Begin Message --- Source: spamassassin Source-Version: 3.3.2-4 We believe that the bug you reported is fixed in the latest version of spamassassin, 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 684...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. no...@debian.org (supplier of updated spamassassin 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: Mon, 13 Aug 2012 21:37:11 -0700 Source: spamassassin Binary: spamassassin spamc Architecture: source all i386 Version: 3.3.2-4 Distribution: unstable Urgency: low Maintainer: Noah Meyerhans Changed-By: no...@debian.org Description: spamassassin - Perl-based spam filter using text analysis spamc - Client for SpamAssassin spam filtering daemon Closes: 683431 684373 684709 Changes: spamassassin (3.3.2-4) unstable; urgency=low . * Incorporate upstream's fix for a bug where malformed multipart MIME messages would bypass URIBL rules. (Closes: #684709) * Update standards version to 3.9.3 (no changes) . spamassassin (3.3.2-3.2) unstable; urgency=low . * Non-maintainer upload. * debian/spamassassin.postinst: Create /var/lib/spamassassin. Closes: #684373. . spamassassin (3.3.2-3.1) unstable; urgency=low . * Non-maintainer upload. * move GPG.KEY out of /usr/share/doc per §12.3(Closes: #683431) Checksums-Sha1: e6790ebe35c9398d0b5dbfac273f095d5f8b0874 1463 spamassassin_3.3.2-4.dsc eec892f80d381de203d5af20456029daeddaa595 39338 spamassassin_3.3.2-4.debian.tar.gz 28dece9bb73b5fe4ae0b3a6b86e69d9cb719f5a1 1268900 spamassassin_3.3.2-4_all.deb 6f9688035a687bb9482abf35a77097115a0366b9 75770 spamc_3.3.2-4_i386.deb Checksums-Sha256: c9545858168d9ecb418655ca21467f21e3e1d4325554a96afcb27deaad860ab1 1463 spamassassin_3.3.2-4.dsc 251ccb416148cfde837c3233f3b72be850bcc24f1ab0c6cad2149aba7c95b05d 39338 spamassassin_3.3.2-4.debian.tar.gz 243174c26e0deb8bde31b620641e59f8d5155bce11358cfd20888756fd6d4dfa 1268900 spamassassin_3.3.2-4_all.deb 1590d6295d3196aaa51413a51b2822af8937f8ebbe4b5f7b88b4e6c690fedda4 75770 spamc_3.3.2-4_i386.deb Files: 69ae8c3414939afe1d9861688f51bb1d 1463 mail optional spamassassin_3.3.2-4.dsc 165179b1c72823e70e7ad7a6f4adb194 39338 mail optional spamassassin_3.3.2-4.debian.tar.gz e191ed880b863fa4948c09bae8ab7f66 1268900 mail optional spamassassin_3.3.2-4_all.deb 363ebd1b4b68a99b700482fed32c55ab 75770 mail optional spamc_3.3.2-4_i386.deb -BEGI
Bug#644392: marked as done (dspam truncates mail)
Your message dated Tue, 14 Aug 2012 06:03:01 + with message-id and subject line Bug#644392: fixed in dspam 3.10.2+dfsg-2 has caused the Debian Bug report #644392, regarding dspam truncates mail 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.) -- 644392: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=644392 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: dspam Version: 3.10.1+dfs Severity: critical Justification: causes serious data loss I have discovered that dspam is truncating inbound email after it has been scanned. Please consider the size field (S=) in the following exim log entries: 2011-10-05 01:58:48 1RBGky-0007w4-3k <= linux-omap-ow...@vger.kernel.org H=mail2.jellyfishnet.co.uk [93.91.20.10] P=esmtps X=TLS1.0:RSA_ARCFOUR_MD5:16 S=6021 id=2a3dcf3da181ad40bde86a3150b27b6b03b4fb3...@dbde02.ent.ti.com 2011-10-05 01:58:48 1RBGky-0007wE-9z <= linux-omap-ow...@vger.kernel.org U=dspam P=spam-scanned S=3591 id=2a3dcf3da181ad40bde86a3150b27b6b03b4fb3...@dbde02.ent.ti.com 2011-10-05 01:58:48 1RBGky-0007w4-3k => guralp R=spamscan T=spamcheck 2011-10-05 01:58:48 1RBGky-0007w4-3k Completed As you can see, there is a significant drop in size between the mail being received from a remote SMTP server (6021 bytes) and after it has been scanned by DSPAM (3591 bytes). The mail as it should be is visible here: http://article.gmane.org/gmane.linux.ports.arm.omap/65281 The mail as I received it ends after the word "earlier" and immediately before the period. I can of course provide a copy as written in my .maildir on request. -- System Information: Debian Release: 6.0.2 APT prefers stable APT policy: (1001, 'stable'), (500, 'stable-updates') Architecture: amd64 (x86_64) Kernel: Linux 2.6.32-5-amd64 (SMP w/4 CPU cores) Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash --- End Message --- --- Begin Message --- Source: dspam Source-Version: 3.10.2+dfsg-2 We believe that the bug you reported is fixed in the latest version of dspam, 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 644...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Thomas Preud'homme (supplier of updated dspam 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: Mon, 13 Aug 2012 16:13:05 +0800 Source: dspam Binary: dspam dspam-webfrontend libdspam7 libdspam7-dev libdspam7-drv-hash libdspam7-drv-pgsql libdspam7-drv-mysql libdspam7-drv-sqlite3 dspam-doc dspam-dbg libdspam7-dbg Architecture: source amd64 all Version: 3.10.2+dfsg-2 Distribution: unstable Urgency: low Maintainer: Debian DSPAM Maintainers Changed-By: Thomas Preud'homme Description: dspam - Scalable, fast and statistical anti-spam filter dspam-dbg - debugging symbols for dspam dspam-doc - Documentation for DSPAM anti-spam filter dspam-webfrontend - Webfrontend for DSPAM anti-spam filter libdspam7 - Core message processing and classification functionality for DSPA libdspam7-dbg - debugging symbols for DSPAM related libraries libdspam7-dev - Development headers for libdspam libdspam7-drv-hash - Hash backend for DSPAM anti-spam filter libdspam7-drv-mysql - MySQL backend for DSPAM anti-spam filter libdspam7-drv-pgsql - PostgreSQL backend for DSPAM anti-spam filter libdspam7-drv-sqlite3 - sqlite3 backend for DSPAM anti-spam filter Closes: 644392 Changes: dspam (3.10.2+dfsg-2) unstable; urgency=low . [ Thomas Preud'homme ] * Team upload. * Cherry-pick patch from upstream to recommend using -oi when using dspam with exim (Closes: #644392). . [ Paul Tagliamonte ] * Although this changelog is signed by Tom, this upload has been signed by me. Tom prepared this upload, but is remote (and without his GPG key), so these changes have been reviewed and uploaded by me. Checksums-Sha1: 8801f38ee0127caaadd87340907757fba62ddc92 2601 dspam_3.10.2+dfsg-2.dsc ac8853d533272e3536ae3113222e0584cbda8842 1046174 dspam_3.10.2+dfsg.orig.tar.gz b29af06d3d5ab310188a2134a0dde3cb9874f366 65268 dspam_3.10.2+dfsg-2.debian.tar.gz df9312ccfa38f345b1deaafcad7bffaf05a52e73 432262 dspam_3.10.2+d
Bug#683431: marked as done (spamassassin: requires GPG.KEY in /usr/share/doc/spamassassin to function)
Your message dated Tue, 14 Aug 2012 06:04:49 + with message-id and subject line Bug#683431: fixed in spamassassin 3.3.2-4 has caused the Debian Bug report #683431, regarding spamassassin: requires GPG.KEY in /usr/share/doc/spamassassin to function 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.) -- 683431: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=683431 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: spamassassin Version: 3.3.2-3 Severity: serious Justification: Policy 12.3 Dear Maintainer, Your package fails to install when /usr/share/doc/spamassassin is not installed (I use dpkg-excludes: "path-exclude=/usr/share/doc/*") >From Policy §12.3 Packages must not require the existence of any files in >/usr/share/doc/ in order to function " http://www.debian.org/doc/debian-policy/ch-docs.html#s12.3 Setting up spamassassin (3.3.2-3) ... Installing new version of config file /etc/cron.daily/spamassassin ... Adding system user `debian-spamd' (UID 120) ... Adding new group `debian-spamd' (GID 121) ... Adding new user `debian-spamd' (UID 120) with group `debian-spamd' ... Creating home directory `/var/lib/spamassassin' ... gpg: can't open `/usr/share/doc/spamassassin/GPG.KEY': No such file or directory dpkg: error processing spamassassin (--configure): subprocess installed post-installation script returned error exit status 2 Setting up spamc (3.3.2-3) ... Errors were encountered while processing: spamassassin -- System Information: Debian Release: wheezy APT prefers testing APT policy: (990, 'testing') Architecture: armel (armv5tel) Kernel: Linux 3.4.0-tomoyo-6-gfd64aac (PREEMPT) Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968) Shell: /bin/sh linked to /bin/dash Versions of packages spamassassin depends on: ii adduser 3.113+nmu3 pn libarchive-tar-perl ii libhtml-parser-perl 3.69-2em1 ii libnet-dns-perl 0.66-2+b2em1 ii libnetaddr-ip-perl 4.062+dfsg-1 ii libsocket6-perl 0.23-1+b2 ii libsys-hostname-long-perl 1.4-2 ii libwww-perl 6.04-1em1 ii perl5.14.2-12 ii perl-modules [libio-zlib-perl] 5.14.2-12 Versions of packages spamassassin recommends: ii gcc4:4.6.3-7 ii gnupg 1.4.12-4+b1 ii libc6-dev 2.13-33 pn libio-socket-inet6-perl ii libmail-spf-perl 2.8.0-1 ii make 3.82-1 ii perl [libsys-syslog-perl] 5.14.2-12 pn re2c ii spamc 3.3.2-3 Versions of packages spamassassin suggests: pn libdbi-perl ii libio-socket-ssl-perl 1.76-1 pn libmail-dkim-perl pn libnet-ident-perl ii perl [libcompress-zlib-perl] 5.14.2-12 pn pyzor pn razor -- no debconf information --- End Message --- --- Begin Message --- Source: spamassassin Source-Version: 3.3.2-4 We believe that the bug you reported is fixed in the latest version of spamassassin, 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 683...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. no...@debian.org (supplier of updated spamassassin 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: Mon, 13 Aug 2012 21:37:11 -0700 Source: spamassassin Binary: spamassassin spamc Architecture: source all i386 Version: 3.3.2-4 Distribution: unstable Urgency: low Maintainer: Noah Meyerhans Changed-By: no...@debian.org Description: spamassassin - Perl-based spam filter using text analysis spamc - Client for SpamAssassin spam filtering daemon Closes: 683431 684373 684709 Changes: spamassassin (3.3.2-4) unstable; urgency=low . * Incorporate upstream's fix for a bug where malformed multipart MIME messages would bypass URIBL rules. (Closes: #684709) * Update standards version to 3.9.3 (no changes) . spamassassin (3.3.2-3.2) unstable; urgency=low . * Non-maintainer upload. * debian/spamassassin.postinst: Create /var/lib/s
Bug#644392: marked as done (dspam truncates mail)
Your message dated Tue, 14 Aug 2012 06:02:51 + with message-id and subject line Bug#644392: fixed in dspam 3.10.1+dfsg-5 has caused the Debian Bug report #644392, regarding dspam truncates mail 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.) -- 644392: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=644392 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: dspam Version: 3.10.1+dfs Severity: critical Justification: causes serious data loss I have discovered that dspam is truncating inbound email after it has been scanned. Please consider the size field (S=) in the following exim log entries: 2011-10-05 01:58:48 1RBGky-0007w4-3k <= linux-omap-ow...@vger.kernel.org H=mail2.jellyfishnet.co.uk [93.91.20.10] P=esmtps X=TLS1.0:RSA_ARCFOUR_MD5:16 S=6021 id=2a3dcf3da181ad40bde86a3150b27b6b03b4fb3...@dbde02.ent.ti.com 2011-10-05 01:58:48 1RBGky-0007wE-9z <= linux-omap-ow...@vger.kernel.org U=dspam P=spam-scanned S=3591 id=2a3dcf3da181ad40bde86a3150b27b6b03b4fb3...@dbde02.ent.ti.com 2011-10-05 01:58:48 1RBGky-0007w4-3k => guralp R=spamscan T=spamcheck 2011-10-05 01:58:48 1RBGky-0007w4-3k Completed As you can see, there is a significant drop in size between the mail being received from a remote SMTP server (6021 bytes) and after it has been scanned by DSPAM (3591 bytes). The mail as it should be is visible here: http://article.gmane.org/gmane.linux.ports.arm.omap/65281 The mail as I received it ends after the word "earlier" and immediately before the period. I can of course provide a copy as written in my .maildir on request. -- System Information: Debian Release: 6.0.2 APT prefers stable APT policy: (1001, 'stable'), (500, 'stable-updates') Architecture: amd64 (x86_64) Kernel: Linux 2.6.32-5-amd64 (SMP w/4 CPU cores) Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash --- End Message --- --- Begin Message --- Source: dspam Source-Version: 3.10.1+dfsg-5 We believe that the bug you reported is fixed in the latest version of dspam, 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 644...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Thomas Preud'homme (supplier of updated dspam 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: Mon, 13 Aug 2012 15:20:48 +0800 Source: dspam Binary: dspam dspam-webfrontend libdspam7 libdspam7-dev libdspam7-drv-hash libdspam7-drv-pgsql libdspam7-drv-mysql libdspam7-drv-sqlite3 dspam-doc dspam-dbg libdspam7-dbg Architecture: source amd64 all Version: 3.10.1+dfsg-5 Distribution: testing-proposed-updates Urgency: low Maintainer: Debian DSPAM Maintainers Changed-By: Thomas Preud'homme Description: dspam - Scalable, fast and statistical anti-spam filter dspam-dbg - debugging symbols for dspam dspam-doc - Documentation for DSPAM anti-spam filter dspam-webfrontend - Webfrontend for DSPAM anti-spam filter libdspam7 - Core message processing and classification functionality for DSPA libdspam7-dbg - debugging symbols for DSPAM related libraries libdspam7-dev - Development headers for libdspam libdspam7-drv-hash - Hash backend for DSPAM anti-spam filter libdspam7-drv-mysql - MySQL backend for DSPAM anti-spam filter libdspam7-drv-pgsql - PostgreSQL backend for DSPAM anti-spam filter libdspam7-drv-sqlite3 - sqlite3 backend for DSPAM anti-spam filter Closes: 644392 669993 Changes: dspam (3.10.1+dfsg-5) testing-proposed-updates; urgency=low . [ Thomas Preud'homme ] * Team upload. * Upload via testing-proposed-updates as unstable contains a new upstream version. * Cherry-pick patch from upstream to recommend using -oi when using dspam with exim (Closes: #644392). * Remove multiarch support for libdspam7-dev as it contains an header with arch-specific contents (Closes: #669993). . [ Paul Tagliamonte ] * Although this changelog is signed by Tom, this upload has been signed by me. Tom prepared this upload, but is remote (and without his GPG key), so these changes have been reviewed and uploaded by me. Checksums-Sha1: 79872326022dfc58612dab0cb2c7607eb3340393
Processed: Re: Bug#684776: dpkg incorrectly complains about conffile contents being different for MA packages
Processing control commands: > found -1 dpkg/1.16.2 Bug #684776 [dpkg] dpkg incorrectly complains about conffile contents being different for MA packages Marked as found in versions dpkg/1.16.2. > severity -1 serious Bug #684776 [dpkg] dpkg incorrectly complains about conffile contents being different for MA packages Severity set to 'serious' from 'normal' -- 684776: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=684776 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#673185: gnome-shell: segfault in libaccountsservice.so.0.0.0
On Sat, Aug 4, 2012 at 4:55 PM, Lukasz Szybalski wrote: > Hello, > Where can I download the updated .deb packages? I need to test if this bug > fixes the following two grave bugs: > > #683092 and #683155 > > Can you point me to a link with .deb files so I can manually install it > and confirm the bugs are related or not?: > > Thank you, > Lucas > Dissregard...my issues got resolved in 683092 after purging and reinstalling gnome-shell. Thanks, Lucas
Processed: Move bug to other package?
Processing commands for cont...@bugs.debian.org: > reassign 670945 apache2.2-bin Bug #670945 [libapache2-mod-php5] libapache2-mod-php5: Bug #589384 breaks default behaviour for MultiViews Bug reassigned from package 'libapache2-mod-php5' to 'apache2.2-bin'. No longer marked as found in versions php5/5.4.0-3. Ignoring request to alter fixed versions of bug #670945 to the same values previously set > severity 670945 serious Bug #670945 [apache2.2-bin] libapache2-mod-php5: Bug #589384 breaks default behaviour for MultiViews Severity set to 'serious' from 'important' > End of message, stopping processing here. Please contact me if you need assistance. -- 670945: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=670945 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#674089: mime-support: removed application/x-httpd-* can lead to immense security problems
Le Tue, Aug 14, 2012 at 02:27:33AM +0200, Christoph Anton Mitterer a écrit : > > Question: Can any other webservers use mod_php? If so, they _might_ be > vulnerable, as the supplied Apache config snippet probably doesn't apply > to them. > Most people I know run either CGI (if just security > counts) or FPM (if security and/or performance counts)... > > If upgrading to Wheezy would unconditionally break these systems, > No,... this is not necessarily the case,.. if people have e.g. set their > own handlers/mime-times for php in apache. Hi again, I have the following questions for the PHP maintainers. 1) Can libapache2-mod-php5 be vulnerable ? 2) The user base of php5-cgi is thousands (see Popcon URL below). What feedback did you have from Sid and Wheezy users ? http://qa.debian.org/popcon-graph.php?packages=php5-cgi+libapache2-mod-php5&show_vote=on&from_date=&to_date=&hlght_date=&date_fmt=%25Y-%25m&beenhere=1 3) Will upgrading unconditionally break sites using php5-cgi with Apache ? 4) Would you like to implement some of Christoph's suggestion or add a NEWs file to php5-cgi ? On mime-support's side, I will not add a NEWs file, as it would interrupt the installation of tens of thousands of systems which do not run PHP. After your answer, I propose to send a brief summary to debian-release and debian-devel, proposing reassign the bug to the release notes with the same severity. Have a nice day, -- Charles Plessy Co-maintainer of the mime-support package Tsurumi, Kanagawa, Japan -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#674089: mime-support: removed application/x-httpd-* can lead to immense security problems
On Tue, 2012-08-14 at 08:06 +0900, Charles Plessy wrote: > + You should also be aware, that a server deployed in CGI mode is open > + to several possible vulnerabilities, see upstream CGI security page > + to learn ow to defend yourself from such attacks: > + http://www.php.net/manual/en/security.cgi-bin.php I doubt that this is a good idea,... to teach our users that the only mode (CGI/FCGI) that can be made somehow secure from an operational point of view, would be not. With respect to the site you refer to: The educated reader will quickly see, that 1/2 are simply about a problem that the CGI interpreter _would_ read any files... and how to prevent this. Well... but it never does,... given that cgi.force_redirect is set. (3) doc_root/user_dir should apply to the other SAPIs as well... The same is true for (4)... if you are stupid enough to put your mod_php libs into the web tree... well then no one can help you. > + Action application/x-php /cgi-bin/php5-cgi > + > + AddType application/x-php php > + See my really elaborate discussion on how this should be securely set (and how it can be optimised in contrast to the above) at the bug over at php5-common, which I've mentioned several times now... It get's boring to explain this over and over again,... honestly :( > For the release note, I think that it would have to clearly indicate that this > only impacts the system running PHP scripts via the CGI package, This depends... The mod_php packages ship their own, more or less secure (again, see my bug at php5-common) config snippet for Apache (!), that already registers it's own handler. So mod_php/Apache = safe. php-cgi = will be safe when the proposed steps are implemented. Question: Can any other webservers use mod_php? If so, they _might_ be vulnerable, as the supplied Apache config snippet probably doesn't apply to them. > which in my > understanding are the minority. Do we really know? Most people I know run either CGI (if just security counts) or FPM (if security and/or performance counts)... And apart from that question, I don't think a minority deserved less security, just because being a minority ;) > If upgrading to Wheezy would unconditionally break these systems, No,... this is not necessarily the case,.. if people have e.g. set their own handlers/mime-times for php in apache. As you can see... there is not a single scenario or case where problems necessarily occur. Which is why I proposed before to add this not only to the release notes, but also to the NEWS files of php5-common and mime-types. To be honest (and this is not meant against you, Charles), I'm quite upset to see how things like this issue are handled. First, a feeling for security seem to be missing, and if something is not a typical attack on a binary, but insecurity on a higher level like dangerous configuration, it seems to be not considered as security problem. People argue forth and back for weeks, whether some text is too much at some place or whether a safety catch option at some place (that is not required under normal circumstances but might protect under bad situations) can be added per default or not. In the meantime, all those using testing/sid may have some problems... and in the real world, there are people using testing or even sid on their servers. Now I noticed that problem and fixed it on all my systems by deploying secure and even optimised Apache configs, which I then suggested Ondrej to add to his documentation for the benefit of all. Again, a not yet ended discussion, which really feels like a pain in the ar**. Okay,... so much ranting from my side ;-) But seriously,... I guess I've said what I'd do with respect to release-notes/NEWS files several times now,... and also what I'd put into php5-common for documentation and how I'd improve mod_php's default config snippet. So all I have to say is said... and unless someone has specific technical questions, I'd like to back out from that discussion. Cheers, Chris. smime.p7s Description: S/MIME cryptographic signature
Bug#674089: mime-support: removed application/x-httpd-* can lead to immense security problems
Hi Christoph and PHP maintainers, my answers follow this long quote about a possible release note. For those in CC, please tell if you do not want to get copies anymore. Le Mon, Aug 13, 2012 at 01:44:23AM +0200, Christoph Anton Mitterer a écrit : > > What about: > --- > mime-types package dropped non-standard definitions for PHP that might > affect any systems using PHP > --- > The package mime-types has dropped the following non-standard > definitions: > application/x-httpd-phpphtml pht php > application/x-httpd-php-source phps > application/x-httpd-php3 php3 > application/x-httpd-php3-preprocessed php3p > application/x-httpd-php4 php4 > application/x-httpd-php5 php5 > > Systems, especially webservers (including but possibly not limited to > the Apache HTTPD Server) may have used this to mark files as having the > a PHP Internet Media Type (commonly known as MIME type). > They may have used it further, to determine that such files are to be > interpreted by PHP rather than served as normal files. > > If a webserver would not consider these files to be interpreted anymore > this would have at least the following effects: > - PHP web programs/sites no longer work > - PHP files are directly exposed, which may be a security problem > > > In order to avoid any problems, read the README.Debian from the > php5-common package on how to correctly configure PHP (examples are > provided for the Apache HTTPD Server) and take care, that and PHP files > intended to be interpreted are recognised as such (typically by adding > MIME-Type or handler definitions in the webserver configuration). > > More information can be found in bug #674089 and partially in #674205. > --- > > As you can see, I personally would put the burden of explaining how to > (securely) configure PHP to the PHP packages... > I have some discussions about that with Ondřej in #674205 ... I'm not > yet fully happy with it (see there)... and although he closed the bug > and said he'd have applied some of my proposals, I could not yet find > these changes there. I think that the changes are the following: - index 26fe076..99c37c6 100644 (file) --- a/debian/php5-common.README.Debian +++ b/debian/php5-common.README.Debian @@ -78,6 +78,11 @@ PHP 5 CGI and Apache HTTP Server installed side-by-side and both were automatically enabled, the results would be a bit confusing, obviously. + You should also be aware, that a server deployed in CGI mode is open + to several possible vulnerabilities, see upstream CGI security page + to learn ow to defend yourself from such attacks: + http://www.php.net/manual/en/security.cgi-bin.php + To use php5-cgi with Apache HTTP Server: 1) activate CGI (it's on by default in default debian setups) a) If using the prefork MPM, use 'a2enmod cgi' @@ -86,8 +91,10 @@ PHP 5 CGI and Apache HTTP Server 3) Add the following to a config snippet in /etc/apache2/conf.d ScriptAlias /cgi-bin/php5-cgi /usr/lib/cgi-bin/php5 - Action php5-cgi /cgi-bin/php5-cgi - AddHandler php5-cgi .php + Action application/x-php /cgi-bin/php5-cgi + + AddType application/x-php php + Note: more modern way of doing this is to install php5-fpm package @@ -140,4 +147,4 @@ Further documentation, errata, misc. If after reading the documentation in this file you still have unanswered questions, that's a good next place to go. - -- Ondřej Surý , Sun, 8 Apr 2012 22:00:59 +0200 + -- Ondřej Surý , Mon, 6 Aug 2012 12:49:51 +0200 - For the release note, I think that it would have to clearly indicate that this only impacts the system running PHP scripts via the CGI package, which in my understanding are the minority. If upgrading to Wheezy would unconditionally break these systems, then I think that a NEWS file in php5-cgi would be an important complement, as it would interrupt the upgrades ran in standard conditions. Have a nice day, -- Charles Plessy Tsurumi, Kanagawa, Japan -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#684748: [arduino] unable to use ethernet library
On Mon, Aug 13, 2012 at 11:20 AM, Scott Howard wrote: >> Using the Arduino compiler under VirtualBOX I compile successfully the >> code meanwhile using the Debian package I got the followings errors: > > It looks like a problem with gcc 4.7.0 that Debian recently switched > to [1, 2]. Debian Arduino is using the patches from here [3]. Hakan, > could you look at bugs.debian.org/684748 and see if anything simple > jumps out at you with this error? Source is here [4]. I'm travelling > and can't look too closely at it. Thank you! > > Cheers, > Scott it's related to the change to IPAddress.h, that was changed because of gcc 4.7. We also will have to upate W5100*. i posted a comment at [1] agreeing with a poster that has a similar problem. It call comes down to the fact that IPAddress.h and .cpp: "Poor code quality here. The 4-octet class member is forcibly type-punned to an incompatible type in several places. This hack forces gcc to disable an entire class of optimisations. The new compiler automatically enables strict-aliasing when size optimisations are selected so we get told about this. The fix is to declare the 4-octet member as a union so it can be used in a type-safe manner." [1] http://andybrown.me.uk/wk/2012/04/28/avr-gcc-4-7-0-and-avr-libc-1-8-0-compiled-for-windows/ -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#684619: [nullmailer] Debconf prompts for info that might contain password, saves to world-readable file
On Mon, Aug 13, 2012 at 05:45:40PM +, Bart Martens wrote: > Hi Nick, > > Why not simply use touch and chmod ? > > | touch file.txt > | chmod 600 file.txt > | echo secret > file.txt It's still susceptible to reading, by someone opening the file inbetween the touch and the chmod. Admittedly a much narrower window of insecurity but still there. Nick -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Processed: update
Processing commands for cont...@bugs.debian.org: > retitle 684781 nvidia-glx: CVE-2012-4225: exploitable privilege escalation Bug #684781 [nvidia-glx] nvidia-glx: exploitable privilege escalation Changed Bug title to 'nvidia-glx: CVE-2012-4225: exploitable privilege escalation' from 'nvidia-glx: exploitable privilege escalation' > End of message, stopping processing here. Please contact me if you need assistance. -- 684781: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=684781 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#684788: emacs24-lucid: segfaults on startup
Package: emacs24-lucid Version: 24.1+1-4 Severity: grave Hello, emacs24 (lucid) segfault on startup, here is gdb backtrace: (gdb) bt #0 0xb7f01228 in XtInitializeWidgetClass () from /usr/lib/i386-linux-gnu/libXt.so.6 #1 0xb7f01d68 in _XtCreateWidget () from /usr/lib/i386-linux-gnu/libXt.so.6 #2 0xb7f02056 in XtCreateWidget () from /usr/lib/i386-linux-gnu/libXt.so.6 #3 0x0810d5f4 in ?? () #4 0x0810e8fd in ?? () #5 0x081a4f38 in ?? () #6 0x081dba6c in ?? () #7 0x081a4975 in ?? () #8 0x081a4d43 in ?? () #9 0x081dba6c in ?? () #10 0x081a4975 in ?? () #11 0x081a4d43 in ?? () #12 0x081dba6c in ?? () #13 0x081a4975 in ?? () #14 0x081a4d43 in ?? () #15 0x081dba6c in ?? () #16 0x081a49d4 in ?? () #17 0x081a4d43 in ?? () #18 0x081dba6c in ?? () #19 0x081a49d4 in ?? () #20 0x081a3e56 in ?? () #21 0x081a41be in ?? () #22 0x081a6dbd in ?? () #23 0x081357a9 in ?? () #24 0x081a32e0 in ?? () #25 0x08135ff5 in ?? () #26 0x081a320b in ?? () #27 0x0813697c in ?? () #28 0x08136c8d in ?? () #29 0x08056cc5 in ?? () #30 0xb6deee46 in __libc_start_main () from /lib/i386-linux-gnu/i686/cmov/libc.so.6 #31 0x08057a5d in ?? () -- System Information: Debian Release: wheezy/sid APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'unstable'), (500, 'stable'), (1, 'experimental') Architecture: i386 (i686) Kernel: Linux 3.2.0-3-686-pae (SMP w/4 CPU cores) Locale: LANG=pl_PL.UTF-8, LC_CTYPE=pl_PL.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash Versions of packages emacs24-lucid depends on: ii emacs24-bin-common 24.1+1-4 ii libasound2 1.0.25-4 ii libc6 2.13-35 ii libcairo2 1.12.2-2 ii libdbus-1-3 1.6.2-2 ii libfontconfig1 2.9.0-7 ii libfreetype62.4.9-1 ii libgdk-pixbuf2.0-0 2.26.1-1 ii libgif4 4.1.6-9.1 ii libglib2.0-02.32.3-1 ii libgnutls26 2.12.20-1 ii libgomp14.7.1-6 ii libgpm2 1.20.4-6 ii libice6 2:1.0.8-2 ii libjpeg88d-1 ii libm17n-0 1.6.3-2 ii libmagickcore5 8:6.7.7.10-3 ii libmagickwand5 8:6.7.7.10-3 ii libncurses5 5.9-10 ii libotf0 0.9.12-2 ii libpng12-0 1.2.49-2 ii librsvg2-2 2.36.1-1 ii libselinux1 2.1.9-5 ii libsm6 2:1.2.1-2 ii libtiff43.9.6-7 ii libtinfo5 5.9-10 ii libx11-62:1.5.0-1 ii libxext62:1.3.1-2 ii libxft2 2.3.1-1 ii libxml2 2.8.0+dfsg1-5 ii libxmu6 2:1.1.1-1 ii libxpm4 1:3.5.10-1 ii libxrender1 1:0.9.7-1 ii libxt6 1:1.1.3-1 ii xaw3dg 1.5+E-18.2 ii zlib1g 1:1.2.7.dfsg-13 emacs24-lucid recommends no packages. Versions of packages emacs24-lucid suggests: pn emacs24-common-non-dfsg -- 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#679607: python-pywbem and sblim-wbemcli: error when trying to install together
Hi, > Although I've already lost any hope of getting sblim-wbemcli into wheezy > due to this bug (I didn't know its freeze exception would expire), I'd > still appreciate your feedback on the matter, if you can spare the time. sorry for the delay :( Actually I've already submitted a patch to python-wbem to rename the cli, but stumbled upon another bug asking to add more of the example code stuff - so i think its actively used already. I think we should implement a bit more sophisticated way which at least informs people about the change. Maybe a NEWS.Debian entry in pywbem is enough. Not sure :( Cheers, Bernd -- Bernd ZeimetzDebian GNU/Linux Developer http://bzed.dehttp://www.debian.org GPG Fingerprint: ECA1 E3F2 8E11 2432 D485 DD95 EB36 171A 6FF9 435F -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#684781: nvidia-glx: exploitable privilege escalation
Hi Andreas Only one additional information to your report: On Mon, Aug 13, 2012 at 09:27:44PM +0200, Andreas Beckmann wrote: > Package: nvidia-glx > Version: 195.36.31-6 > Severity: grave > Tags: security > Justification: user security hole > > There is another privilege escalation in the Nvidia binary driver. > Nvidia Advisory: http://nvidia.custhelp.com/app/answers/detail/a_id/3140 > Initial disclosure of the vulnerability: > http://permalink.gmane.org/gmane.comp.security.full-disclosure/86747 > CVE not assigned or unknown CVE ist now assigned[1]: CVE-2012-4225 [1]: http://www.openwall.com/lists/oss-security/2012/08/08/4 Regards, Salvatore signature.asc Description: Digital signature
Bug#684781: nvidia-glx: exploitable privilege escalation
Package: nvidia-glx Version: 195.36.31-6 Severity: grave Tags: security Justification: user security hole There is another privilege escalation in the Nvidia binary driver. Nvidia Advisory: http://nvidia.custhelp.com/app/answers/detail/a_id/3140 Initial disclosure of the vulnerability: http://permalink.gmane.org/gmane.comp.security.full-disclosure/86747 CVE not assigned or unknown affected: squeeze nvidia-graphics-drivers (195.36.31-6, 195.36.31-6squeeze1) nvidia-graphics-modules (195.36.31+2, 195.36.31+3) nvidia-graphics-drivers-legacy-173xx (173.14.27-2) squeeze-backports nvidia-graphics-drivers (295.59-1~bpo60+1) nvidia-graphics-drivers-legacy-173xx (173.14.35-1~bpo60+1) wheezy/sid nvidia-graphics-drivers (302.17-3) nvidia-graphics-modules (302.17+1, 302.17+2) nvidia-graphics-drivers-legacy-173xx (173.14.35-2) probably unaffected: nvidia-graphics-drivers-legacy-96xx (squeeze only) fixed (according to Nvidia Advisory): 304.32 (beta) experimental (304.32-1) 295.71 (long term stable branch) patch for older versions available, but may disable some fucntionality (e.g. CUDA debugger) Andreas -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#682631: Bug#682634: Bug#682631: linaro-image-tools: FTBFS: AttributeError: 'tuple' object has no attribute 'major'
Hi
Only some more results to this bugreport.
On Fri, Aug 10, 2012 at 04:47:33PM +0200, gregor herrmann wrote:
> On Fri, 10 Aug 2012 15:52:43 +0200, Salvatore Bonaccorso wrote:
>
> > What I do not yet understand, is why it still uses python2.6 for both
> > packages: at least nautilus-image-manipulator depends on python, which
> > now defaults to 2.7, so some other dependencies brings in python2.6?
>
> In the chroot when the build fails:
>
> # aptitude why python2.6
> i pbuilder-satisfydepends-dummy Depends python-nose
> i A python-nose Depends python2.6
>
> But then again, it also shouldn't fail if python2.6 is installed by
> accident on the build system.
>
> > But again, I only did a first look so my initial disclaimer still
> > holds :)
>
> Same here :)
If I apply to the package the change we discussed[1] now the packages
linaro-image-tools and nautilus-image-manipulator FTBFS in unstable
with:
cut-cut-cut-cut-cut-cut-
dpkg-buildpackage: source package linaro-image-tools
dpkg-buildpackage: source version 2012.06-1
dpkg-buildpackage: source changed by Fathi Boudra
dpkg-buildpackage: host architecture amd64
dpkg-source --before-build linaro-image-tools-2012.06
debian/rules clean
dh clean --with python2
dh_testdir
dh_auto_clean
running clean
'build/lib.linux-x86_64-2.6' does not exist -- can't clean it
'build/bdist.linux-x86_64' does not exist -- can't clean it
'build/scripts-2.6' does not exist -- can't clean it
WARNING: the following files are not recognized by DistUtilsExtra.auto:
Traceback (most recent call last):
File "setup.py", line 21, in
"linaro-hwpack-replace"],
File "/usr/lib/python2.6/dist-packages/DistUtilsExtra/auto.py", line 109, in
setup
f_loc = f.decode('ascii', errors='ignore')
TypeError: decode() takes no keyword arguments
dh_auto_clean: python2.6 setup.py clean -a returned exit code 1
make: *** [clean] Error 1
dpkg-buildpackage: error: debian/rules clean gave error exit status 2
cut-cut-cut-cut-cut-cut-
[1]: See attached patch.
> > Thanks for looking too at it Gregor.
>
> The perl group makes an expidition into python land? Let's see if
> this is successful :)
:-).
Regards,
Salvatore
Description: Use sys.version_info[0] instead of sys.version_info.major
Use sys.version_info[0] instead of sys.version_info.major for backwards
compatibility to python2.6.
Author: Salvatore Bonaccorso
Bug-Debian: http://bugs.debian.org/682631
--- python-distutils-extra-2.35.orig/DistUtilsExtra/auto.py
+++ python-distutils-extra-2.35/DistUtilsExtra/auto.py
@@ -104,7 +104,7 @@ def setup(**attrs):
enc = locale.getpreferredencoding()
for f in sorted(src):
# ensure that we can always print the file name
-if(sys.version_info.major < 3):
+if(sys.version_info[0] < 3):
# hack to make this work with Python 2
f_loc = f.decode('ascii', errors='ignore')
else:
@@ -387,7 +387,7 @@ def __add_imports(imports, file, attrs):
with open(file, 'rb') as f:
# send binary blob for python2, otherwise sending an unicode object with
# "encoding" directive makes ast triggering an exception in python2
-if(sys.version_info.major < 3):
+if(sys.version_info[0] < 3):
file_content = f.read()
else:
file_content = f.read().decode('UTF-8')
signature.asc
Description: Digital signature
Bug#684779: pytimechart: missing dependency on python-gtk2
Package: pytimechart
Version: 1.0.0~rc1-2
Severity: serious
Justification: Policy 3.5
In a minimal chroot:
$ pytimechart
Traceback (most recent call last):
File "/usr/bin/pytimechart", line 9, in
load_entry_point('pytimechart==1.0.0.rc1', 'gui_scripts', 'pytimechart')()
File "/usr/lib/python2.7/dist-packages/pkg_resources.py", line 337, in
load_entry_point
return get_distribution(dist).load_entry_point(group, name)
File "/usr/lib/python2.7/dist-packages/pkg_resources.py", line 2279, in
load_entry_point
return ep.load()
File "/usr/lib/python2.7/dist-packages/pkg_resources.py", line 1989, in load
entry = __import__(self.module_name, globals(),globals(), ['__name__'])
File "/usr/lib/python2.7/dist-packages/timechart/timechart.py", line 24, in
from gtk import rc_parse, MenuBar
ImportError: No module named gtk
-- System Information:
Debian Release: wheezy/sid
APT prefers unstable
APT policy: (990, 'unstable')
Architecture: i386 (i686)
Kernel: Linux 3.2.0-3-686-pae (SMP w/1 CPU core)
Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968)
Shell: /bin/sh linked to /bin/dash
Versions of packages pytimechart depends on:
ii python2.7.3-2
ii python-chaco 4.1.0-1
ii python-enthoughtbase 3.1.0-2
ii python-wxgtk2.8 2.8.12.1-11
ii python2.6 2.6.8-0.2
ii python2.7 2.7.3-2
--
Jakub Wilk
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#684778: pythontracer: missing dependency on python-gtk2
Package: pythontracer Version: 8.10.16-1+b1 Severity: serious Justification: Policy 3.5 In a minimal chroot: $ pytracefile Traceback (most recent call last): File "/usr/bin/pytracefile", line 10, in import pytracerview File "/usr/lib/pymodules/python2.7/pytracerview.py", line 3, in import gtk ImportError: No module named gtk -- System Information: Debian Release: wheezy/sid APT prefers unstable APT policy: (990, 'unstable') Architecture: i386 (i686) Kernel: Linux 3.2.0-3-686-pae (SMP w/1 CPU core) Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968) Shell: /bin/sh linked to /bin/dash Versions of packages pythontracer depends on: ii libc6 2.13-35 ii python 2.7.3-2 ii python-support 1.0.15 -- Jakub Wilk -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#650359: segmentation fault gmpc
I'll push the following fix ASAP. It disables the whole LyrDB plugin, which does not seem to work anymore. -- Etienne Millon From: Etienne Millon Date: Mon, 13 Aug 2012 19:52:50 +0200 Subject: Disable LyrDB lyrics provider LyrDB.com makes gmpc segfault, and there are other lyrics providers so disabling it is a net profit. Bug-Debian: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=650359 --- src/Tools/plugin-man.c |3 --- 1 file changed, 3 deletions(-) diff --git a/src/Tools/plugin-man.c b/src/Tools/plugin-man.c index 621bb00..197bcbd 100644 --- a/src/Tools/plugin-man.c +++ b/src/Tools/plugin-man.c @@ -116,9 +116,6 @@ void plugin_manager_load_internal_plugins(void) gmpc_provider_render_cover_new(), 0, NULL); plugin_add_new((GmpcPluginBase *) -gmpc_provider_lyr_db_new(), -0, NULL); -plugin_add_new((GmpcPluginBase *) gmpc_provider_chart_lyrics_new(), 0, NULL); }
Bug#679433: marked as done (boinc-app-seti: FTBFS: build depends on unavailable libboinc-app-dev)
Your message dated Mon, 13 Aug 2012 17:47:40 + with message-id and subject line Bug#679757: fixed in boinc-app-seti 6.12~svn1306-2 has caused the Debian Bug report #679757, regarding boinc-app-seti: FTBFS: build depends on unavailable libboinc-app-dev 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.) -- 679757: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=679757 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: boinc-app-seti Version: 6.12~svn1306-1 Severity: serious Justification: fails to build from source (but built successfully in the past) Automatic builds of boinc-app-seti are failing because it declares a build dependency on libboinc-app-dev, which is completely unavailable AFAICT. (I don't even see it in NEW or experimental.) Listing boinc-dev as an alternative doesn't help, because Debian's autobuilders are generally configured to ignore alternative build dependencies for the sake of consistency. (They consider them only when explicit architecture tags rule out preferred alternatives.) Could you please adjust boinc-app-seti's build dependencies to leave off libboinc-app-dev, or at least favor boinc-dev? Thanks! --- End Message --- --- Begin Message --- Source: boinc-app-seti Source-Version: 6.12~svn1306-2 We believe that the bug you reported is fixed in the latest version of boinc-app-seti, 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 679...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Steffen Moeller (supplier of updated boinc-app-seti 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: Sun, 12 Aug 2012 00:31:34 +0200 Source: boinc-app-seti Binary: boinc-app-seti boinc-app-seti-dbg Architecture: source amd64 Version: 6.12~svn1306-2 Distribution: unstable Urgency: low Maintainer: Debian BOINC Maintainers Changed-By: Steffen Moeller Description: boinc-app-seti - SETI@home application for the BOINC client boinc-app-seti-dbg - debug symbols for SETI@home Closes: 674248 679757 Changes: boinc-app-seti (6.12~svn1306-2) unstable; urgency=low . * debian/rules: auto_clean improved. * increased verbosity of stderr * someone somewhen changed build-dependency to boinc-dev (from libboinc-app-dev) (Closes: #679757). * fixes crash on amd64 as it seems (Closes: #674248) Checksums-Sha1: 2409224eb22710b49d143ec499f6c075aa7549d8 1618 boinc-app-seti_6.12~svn1306-2.dsc 0b77ae1a367da8415b22988caca7d80174b26550 13679 boinc-app-seti_6.12~svn1306-2.debian.tar.gz 5db0e1957ddd3638657301d1cf514eed0867910a 330598 boinc-app-seti_6.12~svn1306-2_amd64.deb 7d93f5cbf84b46088f34b546db85b0215a878b42 2297188 boinc-app-seti-dbg_6.12~svn1306-2_amd64.deb Checksums-Sha256: aa0c9a8a09b2c5b38866be059f7b401081b256b98a70708e1a38d1d85bb51647 1618 boinc-app-seti_6.12~svn1306-2.dsc 8d3095d456a943154d69c3223f36e219d86d88295ea65291509bdcc1786c7068 13679 boinc-app-seti_6.12~svn1306-2.debian.tar.gz 0e5337240ae6894a584f41fabdcb5240bb757d2b76ca3622901768716a72a40a 330598 boinc-app-seti_6.12~svn1306-2_amd64.deb 830ab60436d330183872a8b18646e3de9f14528cdc5b2ca999a071af8375b140 2297188 boinc-app-seti-dbg_6.12~svn1306-2_amd64.deb Files: 2fc0dd59add14dbc949fbc47d7d778c6 1618 science extra boinc-app-seti_6.12~svn1306-2.dsc f5acfccbe8fc8aecbdb7888f926c6103 13679 science extra boinc-app-seti_6.12~svn1306-2.debian.tar.gz 67367094eda4f4bae0b7fc50c26df1cd 330598 science extra boinc-app-seti_6.12~svn1306-2_amd64.deb 5f83ae856057340b891ac320e88517f4 2297188 debug extra boinc-app-seti-dbg_6.12~svn1306-2_amd64.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.12 (GNU/Linux) iEYEARECAAYFAlApOrgACgkQ02K2KlS5mJAH/ACeLJojRCy4R3j7jS1ihjFFLt5P zfgAnAl3ZcGeA2YFuTfS7hOWrCeDKfy7 =RCpd -END PGP SIGNATURE End Message ---
Bug#679757: marked as done (boinc-app-seti: FTBFS: E: Unable to locate package libboinc-app-dev)
Your message dated Mon, 13 Aug 2012 17:47:40 + with message-id and subject line Bug#679757: fixed in boinc-app-seti 6.12~svn1306-2 has caused the Debian Bug report #679757, regarding boinc-app-seti: FTBFS: E: Unable to locate package libboinc-app-dev 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.) -- 679757: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=679757 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:boinc-app-seti Version: 6.12~svn1306-1 Severity: serious Tags: sid wheezy Justification: fails to build from source (but built successfully in the past) Hi! Your package failed to build on the buildds: E: Unable to locate package libboinc-app-dev Regards Christoph -- 9FED 5C6C E206 B70A 5857 70CA 9655 22B9 D49A E731 Debian Developer | Lisp Hacker | CaCert Assurer --- End Message --- --- Begin Message --- Source: boinc-app-seti Source-Version: 6.12~svn1306-2 We believe that the bug you reported is fixed in the latest version of boinc-app-seti, 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 679...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Steffen Moeller (supplier of updated boinc-app-seti 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: Sun, 12 Aug 2012 00:31:34 +0200 Source: boinc-app-seti Binary: boinc-app-seti boinc-app-seti-dbg Architecture: source amd64 Version: 6.12~svn1306-2 Distribution: unstable Urgency: low Maintainer: Debian BOINC Maintainers Changed-By: Steffen Moeller Description: boinc-app-seti - SETI@home application for the BOINC client boinc-app-seti-dbg - debug symbols for SETI@home Closes: 674248 679757 Changes: boinc-app-seti (6.12~svn1306-2) unstable; urgency=low . * debian/rules: auto_clean improved. * increased verbosity of stderr * someone somewhen changed build-dependency to boinc-dev (from libboinc-app-dev) (Closes: #679757). * fixes crash on amd64 as it seems (Closes: #674248) Checksums-Sha1: 2409224eb22710b49d143ec499f6c075aa7549d8 1618 boinc-app-seti_6.12~svn1306-2.dsc 0b77ae1a367da8415b22988caca7d80174b26550 13679 boinc-app-seti_6.12~svn1306-2.debian.tar.gz 5db0e1957ddd3638657301d1cf514eed0867910a 330598 boinc-app-seti_6.12~svn1306-2_amd64.deb 7d93f5cbf84b46088f34b546db85b0215a878b42 2297188 boinc-app-seti-dbg_6.12~svn1306-2_amd64.deb Checksums-Sha256: aa0c9a8a09b2c5b38866be059f7b401081b256b98a70708e1a38d1d85bb51647 1618 boinc-app-seti_6.12~svn1306-2.dsc 8d3095d456a943154d69c3223f36e219d86d88295ea65291509bdcc1786c7068 13679 boinc-app-seti_6.12~svn1306-2.debian.tar.gz 0e5337240ae6894a584f41fabdcb5240bb757d2b76ca3622901768716a72a40a 330598 boinc-app-seti_6.12~svn1306-2_amd64.deb 830ab60436d330183872a8b18646e3de9f14528cdc5b2ca999a071af8375b140 2297188 boinc-app-seti-dbg_6.12~svn1306-2_amd64.deb Files: 2fc0dd59add14dbc949fbc47d7d778c6 1618 science extra boinc-app-seti_6.12~svn1306-2.dsc f5acfccbe8fc8aecbdb7888f926c6103 13679 science extra boinc-app-seti_6.12~svn1306-2.debian.tar.gz 67367094eda4f4bae0b7fc50c26df1cd 330598 science extra boinc-app-seti_6.12~svn1306-2_amd64.deb 5f83ae856057340b891ac320e88517f4 2297188 debug extra boinc-app-seti-dbg_6.12~svn1306-2_amd64.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.12 (GNU/Linux) iEYEARECAAYFAlApOrgACgkQ02K2KlS5mJAH/ACeLJojRCy4R3j7jS1ihjFFLt5P zfgAnAl3ZcGeA2YFuTfS7hOWrCeDKfy7 =RCpd -END PGP SIGNATURE End Message ---
Bug#684619: [nullmailer] Debconf prompts for info that might contain password, saves to world-readable file
Hi Nick, Why not simply use touch and chmod ? | touch file.txt | chmod 600 file.txt | echo secret > file.txt Regards, Bart Martens -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#679454: marked as done (gwibber: Gwibber fails to start wtih python 2.7)
Your message dated Mon, 13 Aug 2012 17:00:22 + with message-id and subject line Bug#679454: fixed in gwibber 3.5.2-1 has caused the Debian Bug report #679454, regarding gwibber: Gwibber fails to start wtih python 2.7 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.) -- 679454: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=679454 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: gwibber Version: 3.0.0.1-2.1 Severity: important Gwibber service is running, and notifications are showing up, but Gwibber itself fails on startup: ~$ gwibber -d Traceback (most recent call last): File "/usr/bin/gwibber", line 55, in from gwibber import client File "/usr/lib/pymodules/python2.7/gwibber/client.py", line 3, in import gtk, gobject, gwui, util, actions, json, gconf File "/usr/lib/pymodules/python2.7/gwibber/gwui.py", line 33, in if "gwibber" not in urlparse.uses_query: AttributeError: 'module' object has no attribute 'uses_query' -- System Information: Debian Release: wheezy/sid APT prefers testing APT policy: (990, 'testing'), (500, 'unstable'), (250, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.2.0-2-amd64 (SMP w/4 CPU cores) Locale: LANG=de_DE.utf8, LC_CTYPE=de_DE.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages gwibber depends on: ii gnome-keyring 3.4.1-4 ii gwibber-service 3.0.0.1-2.1 ii libjs-jquery 1.7.2+debian-2 ii librsvg2-22.36.1-1 ii librsvg2-common 2.36.1-1 ii python2.7.3~rc2-1 ii python-dbus 1.1.0-1 ii python-egenix-mxdatetime 3.2.1-1.1 ii python-gconf 2.28.1+dfsg-1 ii python-gtk2 2.24.0-3 ii python-gtkspell 2.25.3-12 ii python-imaging1.1.7-4 ii python-mako 0.7.0-1 ii python-oauth 1.0.1-3 ii python-simplejson 2.5.2-1 ii python-support1.0.14 ii python-webkit 1.1.8-2 ii python-wnck 2.32.0+dfsg-2+b1 ii python-xdg0.19-4 gwibber recommends no packages. Versions of packages gwibber suggests: pn gwibber-service-buzz pn gwibber-service-digg pn gwibber-service-flickr pn gwibber-service-foursquare pn gwibber-service-friendfeed pn gwibber-service-pingfm pn gwibber-service-qaiku pn gwibber-service-statusnet ii gwibber-themes 3.0.0.1-2.1 -- no debconf information --- End Message --- --- Begin Message --- Source: gwibber Source-Version: 3.5.2-1 We believe that the bug you reported is fixed in the latest version of gwibber, 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 679...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Kartik Mistry (supplier of updated gwibber 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: Mon, 30 Jul 2012 22:10:12 +0530 Source: gwibber Binary: gwibber gwibber-service gwibber-service-facebook gwibber-service-twitter gwibber-service-identica gwibber-service-flickr gwibber-service-statusnet gwibber-service-foursquare libgwibber2 libgwibber-gtk2 libgwibber-dev libgwibber-gtk-dev gir1.2-gwibber-0.2 gir1.2-gwibber-gtk-0.2 Architecture: source amd64 all Version: 3.5.2-1 Distribution: experimental Urgency: low Maintainer: David Riebenbauer Changed-By: Kartik Mistry Description: gir1.2-gwibber-0.2 - typelib file for libgwibber2 gir1.2-gwibber-gtk-0.2 - Typelib file for libgwibber-gtk2 gwibber- Open source social networking client for GNOME gwibber-service - Open source social networking client for GNOME (service) gwibber-service-facebook - Facebook plugin for Gwibber gwibber-service-flickr - Flickr plugin for Gwibber gwibber-service-foursquare - Foursquare plugin for Gwibber gwibber-service-identica - Identi.ca plugin for Gwibber gwibber-service-statusnet - Status.Net plugin for Gwibber gwibber-service-twitter - Twitter plugin for Gwibber libgwibber-dev - Gwibber - shared library (development) libgwibber-gtk-dev - Gwibber - shared library (GTK2 develo
Processed: mediathekview: finds only 1376 out of 57537 movies
Processing commands for cont...@bugs.debian.org: > tags 681680 patch Bug #681680 [mediathekview] mediathekview: finds only 1376 out of 57537 movies Added tag(s) patch. > thanks Stopping processing here. Please contact me if you need assistance. -- 681680: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=681680 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#677361: marked as done (rubrica: FTBFS on kfreebsd-any & hurd-i386 due to rpath)
Your message dated Mon, 13 Aug 2012 16:02:56 +
with message-id
and subject line Bug#677361: fixed in rubrica 2.0-1.3
has caused the Debian Bug report #677361,
regarding rubrica: FTBFS on kfreebsd-any & hurd-i386 due to rpath
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.)
--
677361: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=677361
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: rubrica
Version: 2.0-1.2
Severity: serious
Justification: FTBFS
Tags: patch
User: debian-h...@lists.debian.org
Usertags: hurd
Hello,
rubrica currently FTBFS on kfreebsd and hurd-i386 due to libtool
spuriously adding an rpath to /usr/lib/${DEB_HOST_MULTIARCH}. This was
fixed upstream, rubrica just needs to use libtoolize or autoreconf.
Thanks,
Samuel
-- System Information:
Debian Release: wheezy/sid
APT prefers testing
APT policy: (990, 'testing'), (500, 'unstable'), (500, 'stable'), (1,
'experimental')
Architecture: amd64 (x86_64)
Kernel: Linux 3.0.4 (SMP w/8 CPU cores)
Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash
--
Samuel Thibault
FYLG> Tiens, vlà une URL qui va bien :
FYLG> ftp://127.0.0.1/WaReZ/NiouZeS/WinDoZe/NeWSMoNGeR/SuPeR
c'est gentil sauf que l'adresse ne fonctionne pas sa me fais une erreur
-+- Furtif in Guide du Neuneu Usenet : -+-
--
Samuel
> Il [e2fsck] a bien démarré, mais il m'a rendu la main aussitot en me
> disant "houlala, c'est pas beau à voir votre truc, je préfèrerai que
> vous teniez vous même la tronçonneuse" (traduction libre)
NC in Guide du linuxien pervers : "Bien configurer sa tronçonneuse."
--- End Message ---
--- Begin Message ---
Source: rubrica
Source-Version: 2.0-1.3
We believe that the bug you reported is fixed in the latest version of
rubrica, 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 677...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
gregor herrmann (supplier of updated rubrica 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, 11 Aug 2012 17:47:04 +0200
Source: rubrica
Binary: rubrica
Architecture: source amd64
Version: 2.0-1.3
Distribution: unstable
Urgency: low
Maintainer: Sebastien Bacher
Changed-By: gregor herrmann
Description:
rubrica- An addressbook for the GNOME desktop
Closes: 677361
Changes:
rubrica (2.0-1.3) unstable; urgency=low
.
* Non-maintainer upload.
* Fix "FTBFS on kfreebsd-any & hurd-i386 due to rpath":
- autoreconf: include dh-autoreconf CDBS snippet und build-depend on
dh-autoreconf
- add additional build dependencies needed after autoreconfing: intltool,
gtk-doc-tools
Thanks to Samuel Thibault for the bug report.
(Closes: #677361)
Checksums-Sha1:
80537df10ded95d43538696a2584685064ea3c61 1783 rubrica_2.0-1.3.dsc
a2847dcc646af6e2f7ac45fe36876fe0ac877ff2 3984 rubrica_2.0-1.3.diff.gz
1ee50237075c236d6249ccd9554f751918d540c8 330672 rubrica_2.0-1.3_amd64.deb
Checksums-Sha256:
f08b6efbefc3a5d917dbb94eb9a677505905c7416d78e02f59d35a585ade2188 1783
rubrica_2.0-1.3.dsc
44cad65a28cf18111e946d5f3574418e67568718607e449b9f23b5d1dd961fb6 3984
rubrica_2.0-1.3.diff.gz
d337f13e4ca779a0ed2b824d73f927b8456efb6d1e5b18aee745afcfe495 330672
rubrica_2.0-1.3_amd64.deb
Files:
1ecf585c7419510e0b36c261a01a5182 1783 x11 optional rubrica_2.0-1.3.dsc
b0bad3dea88b872f2b80a3c9c49e8b8b 3984 x11 optional rubrica_2.0-1.3.diff.gz
db65e9f35a1cb9a29bf5f4a1c22c1a79 330672 x11 optional rubrica_2.0-1.3_amd64.deb
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.12 (GNU/Linux)
iQIcBAEBCAAGBQJQJn7NAAoJELs6aAGGSaoG0vcP/3WFMwytdIfvYUWOYb5p/ZHb
Hu5Il4v3OHT8hEUyXowjvmntaNzdD5o3FSXjzhco+6toCRH1+G6TOCQgKYtWzarD
+qyGAH591O5OIGLhP78Auq9Mr6FgjD4ruxhAfaGDOOiLL9YULsweLMONa7razmet
DXtl4dQChiVRHZxr6Q0IFF/2uUclM+ffQbAEI7Fxw0nzWr6XLkCdH0o3WxONCzzv
J8cJuo64OnVPvLXxhQRHJRpVQmOfnv4uGdYOQ1AFYPxSlYCg3LHLDaAZXC0EaLbj
ZYc79vbzhhfVtiB5VRzKejvbkRANIcpa39TqmmdQDOKkVjKki/8TBaEkQxB7IEL3
lktqOJtxLhlCbuKHYT1NSjdT2tFUKWdizkkBiZON/Nswy9PnwZmJ15FIl73HRO/L
vppqBdcy/VMY/VdsBDiNiXXgQPZSNfnKWr2MqdLLM4DuocsvpPd6XkzbdY4780h7
3IEFrBGF6Rxyijn/n9KNcBCSuE7tFZRHMXbq5eFUCK707GCM
Bug#684708: mdadm: support external metadata arrays correctly
On 13.08.2012 19:40, Dmitrijs Ledkovs wrote: > On 13/08/12 16:31, Michael Tokarev wrote: [] >> Well. Sort of. mdmon utility is supposed to be used in the initramfs, >> with support of taking over, etc. But this is apparently due to defects >> in some filesystems (I guess it is ext[34]fs), which performs writes >> even if asked to do a read-only mount. I still don't see a reason why >> a _cleanly_ shut down system should have issues booting - I don't know >> which case Miquel referred to above when saying that a system does not >> boot. >> > > Well... based on the patch, my guess is that because the shutdown does > not wait for raid to be synchronised the filesystem ends up being dirty > after a "clean" shut down, hence to reliable boot you should (not must) > have mdmon with rootfs on external metadata raid. Nononono. The _filesystem_ will most likely be clean. The raid array is not. > Can we include mdmon conditionally, if rootfs is on external metadata raid? There's no reason for that. mdmon is automatically started by mdadm if needed. >> BTW, is it still the case that ext4 performs writes behind the scenes >> even if asked for read-only mount? I think I've seen some fixes in >> this area, but it might be me dreaming. > > True. Maybe we should ask Ted? =) For this very question - including mdmon into initramfs - i really want to understand the underlying problem - whenever we're talking about ext[34]fs which applies journal even for readonly mount and STILL doing so in 3.2 kernel (wheezy), or something else -- in other words, if this is really necessary. I guess it wont _hurt_ to include it (*), after all, initramfs can sometimes be used as a small rescue system to modify the real root before it gets switched to. But I really want to see what is the problem we're dealing with. (*) ofcourse it needs to be verified - the takeover after booting into real system. I can't do it, since I don't have any spare system right now to install debian onto imsm array. I can only verify that the new takeover does not harm regular boot process without imsm arrays. This change - mdmon in initramfs - might be included to wheezy, it isn't a dramatic change. But I still don't think it is a good idea in general -- using native md arrays is a much better way. Due to the last statement, I'm not sure the severity of this bugreport is justified. /mjt -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Processed: tagging 684702, found 682574 in live-tools/3.0.3-1, notfound 682574 in live-utils/3.0.3-1 ...
Processing commands for cont...@bugs.debian.org:
> tags 684702 + pending
Bug #684702 [fglrx-legacy-driver] fglrx-legacy-driver dispalay a "AMD Testing
use only" watermark on the bottom right corner
Added tag(s) pending.
> found 682574 live-tools/3.0.3-1
Bug #682574 {Done: Daniel Baumann } [live-tools,procps]
live-tools, procps: live-tools and procps must consistently handle
/usr/bin/uptime
Marked as found in versions live-tools/3.0.3-1.
> notfound 682574 live-utils/3.0.3-1
Bug #682574 {Done: Daniel Baumann } [live-tools,procps]
live-tools, procps: live-tools and procps must consistently handle
/usr/bin/uptime
The source live-utils and version 3.0.3-1 do not appear to match any binary
packages
No longer marked as found in versions live-utils/3.0.3-1.
> affects 671711 + mono-tools monodoc-clutter-manual octave-vrml liblapack3
> libblas3 octave src:octave src:monodoc-browser
Bug #671711 [dpkg] monodoc-browser: fails to upgrade from 'testing'
Bug #678848 [dpkg] liblapack3: octave has upgrade problems: liblapack.so.3gf:
cannot open shared object file: No such file or directory
Added indication that 671711 affects src:octave
Added indication that 678848 affects src:octave
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
671711: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=671711
678848: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=678848
682574: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=682574
684702: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=684702
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#684708: mdadm: support external metadata arrays correctly
On 13/08/12 16:31, Michael Tokarev wrote: > On 13.08.2012 18:20, Dmitrijs Ledkovs wrote: >> On 13/08/12 12:43, Michael Tokarev wrote: >>> On 13.08.2012 14:10, Miquel van Smoorenburg wrote: Package: mdadm Version: 3.2.5-1 Severity: serious Tags: patch wheezy sid The initramfs hook supplied by mdadm doesn't install mdmon. Also, mdmon is not included in the .udeb for the installer. This means that if you have an array with external metadata (ddf or, more widely used, imsm - Intel Matrix Raid) that it will come up readonly. This causes the installer to hang or the system not being able to boot if root is on that array. >>> >>> I'm not sure this is the right course of actions -- speaking of the >>> initramfs part, not about the d-i part. >>> >>> Why the system is not being able to boot if root is on such an array? >> >> I disagree with Michael, and agree with Miquel. mdmon is needed in the >> initramfs and I wanted to propose it's inclusion myself as well. >> >> Reading mdmon(8) section START UP AND SHUTDOWN, I am convinced that >> mdmon is required when rootfs is on an external metadata array. Does it >> make sense to you, Michael? > > Well. Sort of. mdmon utility is supposed to be used in the initramfs, > with support of taking over, etc. But this is apparently due to defects > in some filesystems (I guess it is ext[34]fs), which performs writes > even if asked to do a read-only mount. I still don't see a reason why > a _cleanly_ shut down system should have issues booting - I don't know > which case Miquel referred to above when saying that a system does not > boot. > Well... based on the patch, my guess is that because the shutdown does not wait for raid to be synchronised the filesystem ends up being dirty after a "clean" shut down, hence to reliable boot you should (not must) have mdmon with rootfs on external metadata raid. Can we include mdmon conditionally, if rootfs is on external metadata raid? > BTW, is it still the case that ext4 performs writes behind the scenes > even if asked for read-only mount? I think I've seen some fixes in > this area, but it might be me dreaming. > True. Maybe we should ask Ted? =) -- Regards, Dmitrijs. -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#684708: mdadm: support external metadata arrays correctly
On 13.08.2012 18:20, Dmitrijs Ledkovs wrote: > On 13/08/12 12:43, Michael Tokarev wrote: >> On 13.08.2012 14:10, Miquel van Smoorenburg wrote: >>> Package: mdadm >>> Version: 3.2.5-1 >>> Severity: serious >>> Tags: patch wheezy sid >>> >>> The initramfs hook supplied by mdadm doesn't install mdmon. Also, mdmon >>> is not included in the .udeb for the installer. >>> >>> This means that if you have an array with external metadata (ddf or, >>> more widely used, imsm - Intel Matrix Raid) that it will come up >>> readonly. This causes the installer to hang or the system not being >>> able to boot if root is on that array. >> >> I'm not sure this is the right course of actions -- speaking of the >> initramfs part, not about the d-i part. >> >> Why the system is not being able to boot if root is on such an array? > > I disagree with Michael, and agree with Miquel. mdmon is needed in the > initramfs and I wanted to propose it's inclusion myself as well. > > Reading mdmon(8) section START UP AND SHUTDOWN, I am convinced that > mdmon is required when rootfs is on an external metadata array. Does it > make sense to you, Michael? Well. Sort of. mdmon utility is supposed to be used in the initramfs, with support of taking over, etc. But this is apparently due to defects in some filesystems (I guess it is ext[34]fs), which performs writes even if asked to do a read-only mount. I still don't see a reason why a _cleanly_ shut down system should have issues booting - I don't know which case Miquel referred to above when saying that a system does not boot. BTW, is it still the case that ext4 performs writes behind the scenes even if asked for read-only mount? I think I've seen some fixes in this area, but it might be me dreaming. 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#679607: python-pywbem and sblim-wbemcli: error when trying to install together
Hi Bernd, Although I've already lost any hope of getting sblim-wbemcli into wheezy due to this bug (I didn't know its freeze exception would expire), I'd still appreciate your feedback on the matter, if you can spare the time. -- Thanks, Feri. -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#684748: [arduino] unable to use ethernet library
On Mon, Aug 13, 2012 at 10:40 AM, Marco Righi wrote:
> Package: arduino
> Version: 1:1.0.1+dfsg-4
> Severity: grave
>
> --- Please enter the report below this line. ---
> Hi,
> I try to compile the Arduino example
>
> #include
> #include
>
> // the media access control (ethernet hardware) address for the shield:
> byte mac[] = { 0xDE, 0xAD, 0xBE, 0xEF, 0xFE, 0xED };
> //the IP address for the shield:
> byte ip[] = { 10, 0, 0, 177 };
>
> void setup()
> {
> Ethernet.begin(mac, ip);
> }
>
> void loop () {}
>
> that I copy from
>
> http://arduino.cc/en/Reference/EthernetBegin
>
> I patched it adding the line
>
> #include
>
> Using the Arduino compiler under VirtualBOX I compile successfully the
> code meanwhile using the Debian package I got the followings errors:
It looks like a problem with gcc 4.7.0 that Debian recently switched
to [1, 2]. Debian Arduino is using the patches from here [3]. Hakan,
could you look at bugs.debian.org/684748 and see if anything simple
jumps out at you with this error? Source is here [4]. I'm travelling
and can't look too closely at it. Thank you!
Cheers,
Scott
[1] http://packages.qa.debian.org/g/gcc-avr.html
[2] http://arduino.cc/forum/index.php?topic=116542.0
[3]
http://andybrown.me.uk/wk/2012/04/28/avr-gcc-4-7-0-and-avr-libc-1-8-0-compiled-for-windows/
[4]
http://anonscm.debian.org/gitweb/?p=collab-maint/arduino.git;a=tree;f=libraries/Ethernet;h=e638934e692b79aaf75a49311684cc45593fb8e9;hb=HEAD
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#679561: marked as done (pegasus-wms FTBFS with new subversion)
Your message dated Mon, 13 Aug 2012 15:17:59 +
with message-id
and subject line Bug#679561: fixed in pegasus-wms 4.0.1+dfsg-7
has caused the Debian Bug report #679561,
regarding pegasus-wms FTBFS with new subversion
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.)
--
679561: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=679561
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: pegasus-wms
Version: 4.0.1+dfsg-6
Severity: serious
Tags: patch
pegasus-wms FTBFS with the new subversion
[exec] g++ -ffor-scope -Wall -O2 -m64 -ggdb
-DMACHINE_SPECIFIC=linux -DLINUX -DMAJOR=2
-DHAS_SVNVERSION=\"Unversioned directory\" pegasus-keg.cc -c -o
pegasus-keg.o
[exec] g++-4.7.real: error: directory": No such file or directory
This bug does not currently affect wheezy but jcristu has said that the
new subversion may be allowed in and that therefore we should assume
issues caused by it are rc for wheezy.
The cause is that the new version of subversion returns "Unversioned
directory" in response to svnversion . in a non-svn directory, this
breaks the build proces due to an inability to handle spaces in this
field, the attached patch fixes this by not defining -DHAS_SVNVERSION
if svnversion . reutrns "Unversioned directory".
Patch is attatched just add it to the quilt series.
Description: fix build with new subversion
Recent versions of subversion return "Unversioned directory" in response
to svnversion . in a non-svn directory, this breaks the build process
due to an inability to handle spaces in this field, the attached patch
fixes this by not defining -DHAS_SVNVERSION if svnversion . reutrns
"Unversioned directory"
Author: Peter Michael Green
---
The information above should follow the Patch Tagging Guidelines, please
checkout http://dep.debian.net/deps/dep3/ to learn about the format. Here
are templates for supplementary fields that you might want to add:
Origin: ,
Bug:
Bug-Debian: http://bugs.debian.org/
Bug-Ubuntu: https://launchpad.net/bugs/
Forwarded:
Reviewed-By:
Last-Update:
--- pegasus-wms-4.0.1+dfsg.orig/src/tools/pegasus-keg/Makefile
+++ pegasus-wms-4.0.1+dfsg/src/tools/pegasus-keg/Makefile
@@ -129,8 +129,10 @@ CONDOR_CXX = $(CONDOR) $(CXX)
SVNVERSION = $(shell svnversion . 2>> /dev/null)
ifneq (,${SVNVERSION})
+ifneq (Unversioned directory,${SVNVERSION})
CXXFLAGS += -DHAS_SVNVERSION=\"${SVNVERSION}\"
endif
+endif
# add large file support
ifneq (,${LFS_CFLAGS})
--- End Message ---
--- Begin Message ---
Source: pegasus-wms
Source-Version: 4.0.1+dfsg-7
We believe that the bug you reported is fixed in the latest version of
pegasus-wms, 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 679...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Mats Rynge (supplier of updated pegasus-wms 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: Mon, 13 Aug 2012 07:38:33 -0700
Source: pegasus-wms
Binary: pegasus-wms pegasus-wms-doc
Architecture: source amd64 all
Version: 4.0.1+dfsg-7
Distribution: unstable
Urgency: low
Maintainer: Mats Rynge
Changed-By: Mats Rynge
Description:
pegasus-wms - Scientific workflow management system for Condor
pegasus-wms-doc - Scientific workflow management system for Condor - data files
Closes: 679561 682148
Changes:
pegasus-wms (4.0.1+dfsg-7) unstable; urgency=low
.
* Fixed FTBFS problem with Subversion 1.7 (closes: #679561)
* Fixed Python 2.7.3 problem with uses_query - this affected several
Pegasus command line tools (closes: #682148)
Checksums-Sha1:
7fdca095dec0ac4ff3bef3fb81a9613731adcb63 1442 pegasus-wms_4.0.1+dfsg-7.dsc
1a5ce0785dc738364e84d553c1218c80ff64eea8 78305
pegasus-wms_4.0.1+dfsg-7.debian.tar.gz
c55ff1829d8a4891f8f29af298d013d4f8fa276b 2692090
pegasus-wms_4.0.1+dfsg-7_amd64.deb
84768a827eccb31c026272004f613d6373e662c5 19248342
pegasus-wms-doc_4.0.1+dfsg-7_all.deb
Checksums-Sha256:
1e43c7a19d87d00ca63778807736d6472434e2ea2b72f152f89436b66b509817 1442
pegasus-wms_4.0.1+dfsg-7.dsc
8c5b1ab341e93c2356cad2bb2d2ab9eb1ec4f80538a600b7ac9a63ebaa9bcc44 78305
pegasus-wms_4.0.1+dfsg-7.debian.tar.gz
ef2bf
Bug#674386: supercollider: FTBFS: scons: *** No SConstruct file found.
2012/8/13 Felipe Sateler : > On Sun, Aug 12, 2012 at 5:37 PM, Dan S wrote: >> 2012/8/12 peter green : I'd like to mark this as "won't fix" because we're dropping the scons build system. The latest version of supercollider 3.5.x (which I'm currently asking debian-multimedia maintainers to upload) uses cmake instead which is much less mess. >>> >>> Supercollider 1:3.5.2-1 was uploaded just before the freeze deadline, >>> however >>> it did not migrate to testing due to build failures. >>> >>> So if supercollider is going to release with wheezy you either need to open >>> discussions with the release team about either getting a freeze exception >>> for >>> the version in sid or making a TPU upload to fix the scons build system in >>> the wheezy package >> >> Thanks. I'm not very familiar with debian processes so I'd appreciate >> guidance from pkg-multimedia-maintainers on this. I don't know how to >> do either of the things you describe, or which is better. (What's >> TPU?) In git I made a branch "3.4debianfixes" which potentially >> contains a fix for the scons issue. > > The basic process is described by Raphael Hertzhog at [1]. The > description, however, does not describe the current issue. What > happens if testing is frozen, there is a bug in the package in > testing, and there is a newer release in unstable? There are three > options: > > 1. Remove the software from testing (and therefore, from the next > stable release). > 2. Somehow convince the release team that the new version in unstable > should migrate to testing. > 3. Upload a localized fix to testing-proposed-updates (TPU for short, > a special "distribution" meant for fixes that cannot go through > unstable). > > > Each option has its benefits and drawbacks. The release team usually > prefers option 3. Rewriting the choices for our current situation, we > have: > > 1. Do not release supercollider in wheezy > 2. Somehow convince the rt that 3.5 should migrate. > 3. Ship 3.4 with the fix, via an upload to tpu. > > > As I see it, there are significant drawbacks with the standard option > (n° 3), because I'm not quite sure if 3.4 offers the best experience > for users. However, I'd prefer if you (Dan) made this call, because > you know sc much better, and thus can make a more informed decision. > At this point, option 2 looks very unlikely, though. We can try to do > it, but it is more likely that we will end up doing either 1 or 3. But > we need to be clear on which one to do. As discussed, 3.4 is not a fantastic package, but it does provide the core language+server, so option 1 seems pointless when bug #674386 apparently has a fix we can go straight for. I don't have any strong motivation to go into negotiations with the RT for option 2: although 3.4 is less than ideal, once it's shipped we can focus on making the 3.5 sid package great. So I suggest let's go for TPU. Dan -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#684758: libphone-utils0-dbg: /usr/share/doc/libphone-utils0-dbg empty after squeeze->wheezy upgrade
Package: libphone-utils0-dbg Version: 0.1+git20110523-1 Severity: serious Justification: Policy 12.5 User: debian...@lists.debian.org Usertags: piuparts Hi, during an experimental test with piuparts I noticed that the copyright file of your package disappears after a squeeze->wheezy dist-upgrade. /usr/share/doc/$PACKAGE/ is an empty directory afterwards. On a fresh wheezy installation, it is a symlink instead. cheers, Andreas -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#684619: [nullmailer] Debconf prompts for info that might contain password, saves to world-readable file
At 08:54 +0100 13 Aug 2012, Nick Leverton wrote: Thanks for the very good catch on this one. The package is ready to upload but needs a sponsor. Would you be able to spare a bit more time to upload the fix for me, please ? Sorry I'm not a Debian Developer, so I can't upload packages. -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#684755: [arduino] UPDATE INFROMATION unable to use ethernet library
Package: arduino
Version: 1:1.0.1+dfsg-4
Severity: grave
--- Please enter the report below this line. ---
Hi,
the package
http://arduino.googlecode.com/files/arduino-1.0.1-linux64.tgz
compiles correctly the code. Follow the previous e-mail
._._._._._._._._._._._._._._._._._._._._._._._._._._._._
Hi,
I try to compile the Arduino example
#include
#include
// the media access control (ethernet hardware) address for the shield:
byte mac[] = { 0xDE, 0xAD, 0xBE, 0xEF, 0xFE, 0xED };
//the IP address for the shield:
byte ip[] = { 10, 0, 0, 177 };
void setup()
{
Ethernet.begin(mac, ip);
}
void loop () {}
that I copy from
http://arduino.cc/en/Reference/EthernetBegin
I patched it adding the line
#include
Using the Arduino compiler under VirtualBOX I compile successfully the
code meanwhile using the Debian package I got the followings errors:
/usr/share/arduino/libraries/Ethernet/Ethernet.cpp: In member function
‘void EthernetClass::begin(uint8_t*, IPAddress, IPAddress, IPAddress,
IPAddress)’:
/usr/share/arduino/libraries/Ethernet/Ethernet.cpp:64:39: error: no
matching function for call to
‘W5100Class::setIPAddress(IPAddress::&)’
/usr/share/arduino/libraries/Ethernet/Ethernet.cpp:64:39: note:
candidate is:
In file included from
/usr/share/arduino/libraries/Ethernet/Ethernet.cpp:1:0:
/usr/share/arduino/libraries/Ethernet/utility/w5100.h:392:6: note: void
W5100Class::setIPAddress(uint8_t*)
/usr/share/arduino/libraries/Ethernet/utility/w5100.h:392:6: note: no
known conversion for argument 1 from ‘IPAddress::’ to
‘uint8_t* {aka unsigned char*}’
/usr/share/arduino/libraries/Ethernet/Ethernet.cpp:65:38: error: no
matching function for call to
‘W5100Class::setGatewayIp(IPAddress::&)’
/usr/share/arduino/libraries/Ethernet/Ethernet.cpp:65:38: note:
candidate is:
In file included from
/usr/share/arduino/libraries/Ethernet/Ethernet.cpp:1:0:
/usr/share/arduino/libraries/Ethernet/utility/w5100.h:368:6: note: void
W5100Class::setGatewayIp(uint8_t*)
/usr/share/arduino/libraries/Ethernet/utility/w5100.h:368:6: note: no
known conversion for argument 1 from ‘IPAddress::’ to
‘uint8_t* {aka unsigned char*}’
/usr/share/arduino/libraries/Ethernet/Ethernet.cpp:66:38: error: no
matching function for call to
‘W5100Class::setSubnetMask(IPAddress::&)’
/usr/share/arduino/libraries/Ethernet/Ethernet.cpp:66:38: note:
candidate is:
In file included from
/usr/share/arduino/libraries/Ethernet/Ethernet.cpp:1:0:
/usr/share/arduino/libraries/Ethernet/utility/w5100.h:376:6: note: void
W5100Class::setSubnetMask(uint8_t*)
/usr/share/arduino/libraries/Ethernet/utility/w5100.h:376:6: note: no
known conversion for argument 1 from ‘IPAddress::’ to
‘uint8_t* {aka unsigned char*}’
Thanks in advance
Marco Righi
--- System information. ---
Architecture: amd64
Kernel: Linux 3.2.0-3-amd64
Debian Release: wheezy/sid
500 wheezy linux.dropbox.com
500 testing www.debian-multimedia.org
500 testing security.debian.org
500 testing http.us.debian.org
500 testing ftp.fr.debian.org
500 stable repo.wuala.com
500 stable ftp2.de.debian.org
500 stable apt.spideroak.com
500 squeeze www.lamaresh.net
500 oneiric ppa.launchpad.net
--- Package information. ---
Depends(Version) | Installed
-+-===
default-jre | 1:1.6-47
OR java6-runtime|
libjna-java | 3.2.7-4
librxtx-java (>= 2.2pre2-3) | 2.2pre2-11
arduino-core (= 1:1.0.1+dfsg-4) | 1:1.0.1+dfsg-4
Recommends (Version) | Installed
==-+-===
extra-xdg-menus| 1.0-4
policykit-1| 0.105-1
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
Bug#684754: python-surfer: missing dependency on python-matplotlib
Package: python-surfer Version: 0.3+git15-gae6cbb1-1 Severity: serious Justification: Policy 3.5 In a minimal chroot: $ python -c 'import surfer' Traceback (most recent call last): File "", line 1, in File "/usr/lib/pymodules/python2.7/surfer/__init__.py", line 2, in from viz import Brain, TimeViewer File "/usr/lib/pymodules/python2.7/surfer/viz.py", line 8, in from matplotlib.colors import colorConverter ImportError: No module named matplotlib.colors -- System Information: Debian Release: wheezy/sid APT prefers unstable APT policy: (990, 'unstable') Architecture: i386 (i686) Kernel: Linux 3.2.0-3-686-pae (SMP w/1 CPU core) Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968) Shell: /bin/sh linked to /bin/dash Versions of packages python-surfer depends on: ii ipython 0.13-1 ii mayavi2 4.1.0-1 ii python 2.7.3-2 ii python-imaging 1.1.7-4 ii python-nibabel 1.2.2-1 ii python-numpy 1:1.6.2-1 ii python-scipy 0.10.1+dfsg1-4 ii python-support 1.0.15 ii python2.7 [python-argparse] 2.7.3-2 -- Jakub Wilk -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#684708: mdadm: support external metadata arrays correctly
also sprach Dmitrijs Ledkovs [2012.08.13.1620 +0200]: > Agree, sounds risky but doing this right is worth the effort. Yes, but it's definitely too late for wheezy. I suggest that we wait until wheezy is out and then push a new mdadm to unstable. -- martin | http://madduck.net/ | http://two.sentenc.es/ "there was silence for a moment, and then out of the scrambled mess of arthur's brain crawled some words." -- hitchhiker's guide to the galaxy spamtraps: madduck.bo...@madduck.net digital_signature_gpg.asc Description: Digital signature (see http://martin-krafft.net/gpg/sig-policy/999bbcc4/current)
Bug#680685: update on bug 680685
David Bremner, 2012-07-31 15:43-0300: It turns out that racket upstream will probably deprecate the binary planet in the next upstream release, and claims that "raco planet" is the now preferred interface. So, although I still think this is really a bug in planet-venus, it could also make sense to just remove the planet binary from racket. That would probably be the easiest. Not the most just way to solve this conflict, but the easiest. I believe we have two options here: 1. Rename planet-venus:/usr/bin/planet to /usr/bin/planet-venus (or perhaps to /usr/bin/venus) Pro: * This is what should have been done from the beginning. This is only a theoretical advantage though Con: * Will break the cron scripts of all the users of planet-venus. This can be dealt with by documenting it in a NEWS file and probably in the release notes too, but it would be annoying nevertheless, especially to lazy admins. :-) 2. Remove racket:/usr/bin/planet Pro: * This anticipates the ypstream decision. This is only a theoretical advantage too. Con: * It will annoy users, who would be annoyed by the upstream decision for the next release anyway. -- ,--. : /` ) Tanguy Ortolo | `-'Debian Developer \_ signature.asc Description: Digital signature
Bug#674386: supercollider: FTBFS: scons: *** No SConstruct file found.
On Sun, Aug 12, 2012 at 5:37 PM, Dan S wrote: > 2012/8/12 peter green : >>> >>> I'd like to mark this as "won't fix" because we're dropping the scons >>> build system. The latest version of supercollider 3.5.x (which I'm >>> currently asking debian-multimedia maintainers to upload) uses cmake >>> instead which is much less mess. >>> >> >> Supercollider 1:3.5.2-1 was uploaded just before the freeze deadline, >> however >> it did not migrate to testing due to build failures. >> >> So if supercollider is going to release with wheezy you either need to open >> discussions with the release team about either getting a freeze exception >> for >> the version in sid or making a TPU upload to fix the scons build system in >> the wheezy package > > Thanks. I'm not very familiar with debian processes so I'd appreciate > guidance from pkg-multimedia-maintainers on this. I don't know how to > do either of the things you describe, or which is better. (What's > TPU?) In git I made a branch "3.4debianfixes" which potentially > contains a fix for the scons issue. The basic process is described by Raphael Hertzhog at [1]. The description, however, does not describe the current issue. What happens if testing is frozen, there is a bug in the package in testing, and there is a newer release in unstable? There are three options: 1. Remove the software from testing (and therefore, from the next stable release). 2. Somehow convince the release team that the new version in unstable should migrate to testing. 3. Upload a localized fix to testing-proposed-updates (TPU for short, a special "distribution" meant for fixes that cannot go through unstable). Each option has its benefits and drawbacks. The release team usually prefers option 3. Rewriting the choices for our current situation, we have: 1. Do not release supercollider in wheezy 2. Somehow convince the rt that 3.5 should migrate. 3. Ship 3.4 with the fix, via an upload to tpu. As I see it, there are significant drawbacks with the standard option (n° 3), because I'm not quite sure if 3.4 offers the best experience for users. However, I'd prefer if you (Dan) made this call, because you know sc much better, and thus can make a more informed decision. At this point, option 2 looks very unlikely, though. We can try to do it, but it is more likely that we will end up doing either 1 or 3. But we need to be clear on which one to do. [1] http://raphaelhertzog.com/2010/10/18/understanding-debians-release-process/ -- Saludos, Felipe Sateler -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#684748: [arduino] unable to use ethernet library
Package: arduino
Version: 1:1.0.1+dfsg-4
Severity: grave
--- Please enter the report below this line. ---
Hi,
I try to compile the Arduino example
#include
#include
// the media access control (ethernet hardware) address for the shield:
byte mac[] = { 0xDE, 0xAD, 0xBE, 0xEF, 0xFE, 0xED };
//the IP address for the shield:
byte ip[] = { 10, 0, 0, 177 };
void setup()
{
Ethernet.begin(mac, ip);
}
void loop () {}
that I copy from
http://arduino.cc/en/Reference/EthernetBegin
I patched it adding the line
#include
Using the Arduino compiler under VirtualBOX I compile successfully the
code meanwhile using the Debian package I got the followings errors:
/usr/share/arduino/libraries/Ethernet/Ethernet.cpp: In member function
‘void EthernetClass::begin(uint8_t*, IPAddress, IPAddress, IPAddress,
IPAddress)’:
/usr/share/arduino/libraries/Ethernet/Ethernet.cpp:64:39: error: no
matching function for call to
‘W5100Class::setIPAddress(IPAddress::&)’
/usr/share/arduino/libraries/Ethernet/Ethernet.cpp:64:39: note:
candidate is:
In file included from
/usr/share/arduino/libraries/Ethernet/Ethernet.cpp:1:0:
/usr/share/arduino/libraries/Ethernet/utility/w5100.h:392:6: note: void
W5100Class::setIPAddress(uint8_t*)
/usr/share/arduino/libraries/Ethernet/utility/w5100.h:392:6: note: no
known conversion for argument 1 from ‘IPAddress::’ to
‘uint8_t* {aka unsigned char*}’
/usr/share/arduino/libraries/Ethernet/Ethernet.cpp:65:38: error: no
matching function for call to
‘W5100Class::setGatewayIp(IPAddress::&)’
/usr/share/arduino/libraries/Ethernet/Ethernet.cpp:65:38: note:
candidate is:
In file included from
/usr/share/arduino/libraries/Ethernet/Ethernet.cpp:1:0:
/usr/share/arduino/libraries/Ethernet/utility/w5100.h:368:6: note: void
W5100Class::setGatewayIp(uint8_t*)
/usr/share/arduino/libraries/Ethernet/utility/w5100.h:368:6: note: no
known conversion for argument 1 from ‘IPAddress::’ to
‘uint8_t* {aka unsigned char*}’
/usr/share/arduino/libraries/Ethernet/Ethernet.cpp:66:38: error: no
matching function for call to
‘W5100Class::setSubnetMask(IPAddress::&)’
/usr/share/arduino/libraries/Ethernet/Ethernet.cpp:66:38: note:
candidate is:
In file included from
/usr/share/arduino/libraries/Ethernet/Ethernet.cpp:1:0:
/usr/share/arduino/libraries/Ethernet/utility/w5100.h:376:6: note: void
W5100Class::setSubnetMask(uint8_t*)
/usr/share/arduino/libraries/Ethernet/utility/w5100.h:376:6: note: no
known conversion for argument 1 from ‘IPAddress::’ to
‘uint8_t* {aka unsigned char*}’
Thanks in advance
Marco Righi
--- System information. ---
Architecture: amd64
Kernel: Linux 3.2.0-3-amd64
Debian Release: wheezy/sid
500 wheezy linux.dropbox.com
500 testing www.debian-multimedia.org
500 testing security.debian.org
500 testing http.us.debian.org
500 testing ftp.fr.debian.org
500 stable repo.wuala.com
500 stable ftp2.de.debian.org
500 stable apt.spideroak.com
500 squeeze www.lamaresh.net
500 oneiric ppa.launchpad.net
--- Package information. ---
Depends(Version) | Installed
-+-===
default-jre | 1:1.6-47
OR java6-runtime|
libjna-java | 3.2.7-4
librxtx-java (>= 2.2pre2-3) | 2.2pre2-11
arduino-core (= 1:1.0.1+dfsg-4) | 1:1.0.1+dfsg-4
Recommends (Version) | Installed
==-+-===
extra-xdg-menus| 1.0-4
policykit-1| 0.105-1
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
Bug#672959: kfreebsd-*: panic: vm_fault_copy_wired
Hi, I ran into that on Saturday, too. Roger Leigh wrote: > > > I guess this is reproducible by simply installing Debian/kFreeBSD AMD64 > > > on a virtual machine and forcing and unclean shutdown (killing the qemu > > > process when the virtual machine is running). It seems so, yes. It seems triggered by an unclean FS, yes. Was able to reproduce it with 8.2, 8.3 and 9.0 kernels. (Couldn't get the 10.0 kernel to boot at all, but that's another story, not yet reported though.) > This bug is still RC for wheezy. And justifiably so. > It really needs looking at by a kfreebsd expert, if someone could > take a look at this. Will do. Regards, Axel -- ,''`. | Axel Beckert , http://people.debian.org/~abe/ : :' : | Debian Developer, ftp.ch.debian.org Admin `. `' | 1024D: F067 EA27 26B9 C3FC 1486 202E C09E 1D89 9593 0EDE `-| 4096R: 2517 B724 C5F6 CA99 5329 6E61 2FF9 CD59 6126 16B5 -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Processed: tagging 681060
Processing commands for cont...@bugs.debian.org: > tags 681060 + upstream Bug #681060 [abiword] abiword: Crash when copying Unicode text from Firefox Added tag(s) upstream. > thanks Stopping processing here. Please contact me if you need assistance. -- 681060: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=681060 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#684708: mdadm: support external metadata arrays correctly
On 13/08/12 12:43, Michael Tokarev wrote: > On 13.08.2012 14:10, Miquel van Smoorenburg wrote: >> Package: mdadm >> Version: 3.2.5-1 >> Severity: serious >> Tags: patch wheezy sid >> >> The initramfs hook supplied by mdadm doesn't install mdmon. Also, mdmon >> is not included in the .udeb for the installer. >> >> This means that if you have an array with external metadata (ddf or, >> more widely used, imsm - Intel Matrix Raid) that it will come up >> readonly. This causes the installer to hang or the system not being >> able to boot if root is on that array. > > I'm not sure this is the right course of actions -- speaking of the > initramfs part, not about the d-i part. > > Why the system is not being able to boot if root is on such an array? I disagree with Michael, and agree with Miquel. mdmon is needed in the initramfs and I wanted to propose it's inclusion myself as well. Reading mdmon(8) section START UP AND SHUTDOWN, I am convinced that mdmon is required when rootfs is on an external metadata array. Does it make sense to you, Michael? >> The attached patch does a couple of things: >> >> - it makes sure mdadm is included in the initramfs and the udeb package s/mdadm/mdmon/ as mdadm was available already ;-) > > Sure it is needed in the d-i (udeb), because d-i have to write the > system to it. But I'm not convinced it is needed in the initramfs. > ok. >> - it adds a mdadm-waitidle script that runs just before reboot/halt. For all >> arrays that are still running, it sets safe_mode_delay to a low version, >> sets sync_action to idle, and waits for the array(s) to go idle. >> This is needed so that the array is clean, otherwise it will start >> to resync at the next boot. > > This is risky - we may never finish shutdown. This is especially risky > for things like raid - eg, stalled raid (resync) thread (we've seen > these more than once) -- in such cases current code will shut down, > but with this wait it wont anymore. Especially useful for remote > systems. Such an approach should be tested with extra care, I'm > not sure we have resources to do that for wheezy. Generally it is a > good idea I think. > Agree, sounds risky but doing this right is worth the effort. >> - it adds 2 lines of code to mdmon.c so that it symlinks its pidfile >> into /run/sendsigs.omit.d - mdmon should not be killed at shutdown, >> we still need it after the rootfs has been unmounted. > > And I'm not sure this is needed, either: it can trivially be done in > the initscript. > No patching of mdmon is required. We simply need MDMON_DIR configure option to be set to /run/sendsigs.omit.d. -- Regards, Dmitrijs. -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#684736: melange: ImportError: No module named melange
Package: melange Version: 1:2012.1-2 Severity: serious None of the binaries provided by melange start in a minimal chroot: $ melange-delete-deallocated-ips Traceback (most recent call last): File "/usr/bin/melange-delete-deallocated-ips", line 48, in from melange import ipv4 ImportError: No module named melange $ melange-manage Traceback (most recent call last): File "/usr/bin/melange-manage", line 38, in from melange import ipv4 ImportError: No module named melange $ melange-server Traceback (most recent call last): File "/usr/bin/melange-server", line 38, in from melange import ipv4 ImportError: No module named melange -- System Information: Debian Release: wheezy/sid APT prefers unstable APT policy: (990, 'unstable') Architecture: i386 (i686) Kernel: Linux 3.2.0-3-686-pae (SMP w/1 CPU core) Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968) Shell: /bin/sh linked to /bin/dash Versions of packages melange depends on: ii adduser 3.113+nmu3 ii python 2.7.3-2 -- Jakub Wilk -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#684735: unblock: ganglia (security)
Control: severity -1 normal Control: user release.debian@packages.debian.org Control: usertags -1 unblock On 13.08.2012 14:53, Daniel Pocock wrote: Package: release.debian.org Severity: grave release.d.o unblocks bugs are not RC; severity lowered. - there is a security vulnerability - this unblock has inherited the `grave' severity from the other bug: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=683584 - 3.3.6 and 3.3.7 also contain essential fixes for memory leak and seg fault issues - the 3.3 branch is a stable branch that doesn't contain aggressive changes or new features - I have made up the 3.3.x series upstream releases myself so I have seen all the changes - the package changes can be browsed in the VCS: http://git.debian.org/?p=collab-maint/ganglia.git;a=summary - the detailed log of upstream changes can be browsed in github: https://github.com/ganglia/ganglia-web/commits/release/3.3 Please could we have a full source debdiff for a proposed upload as part of this bug log? It makes it far clearer what was requested to be acked and what was (or wasn't) acked. Regards, Adam -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Processed (with 2 errors): Re: Bug#684735: unblock: ganglia (security)
Processing control commands: > severity -1 normal Bug #684735 [release.debian.org] unblock: ganglia (security) Severity set to 'normal' from 'grave' > user release.debian@packages.debian.org > usertags -1 unblock -- 684735: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=684735 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#684735: unblock: ganglia (security)
Package: release.debian.org Severity: grave Tags: security Short summary of request: please give authorization to a) upload ganglia 3.3.8-1 to unstable b) unblocking 3.3.8-1 to wheezy after appropriate cooling-off period Longer summary: - there is a security vulnerability - this unblock has inherited the `grave' severity from the other bug: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=683584 - 3.3.6 and 3.3.7 also contain essential fixes for memory leak and seg fault issues - the 3.3 branch is a stable branch that doesn't contain aggressive changes or new features - I have made up the 3.3.x series upstream releases myself so I have seen all the changes - the package changes can be browsed in the VCS: http://git.debian.org/?p=collab-maint/ganglia.git;a=summary - the detailed log of upstream changes can be browsed in github: https://github.com/ganglia/ganglia-web/commits/release/3.3 Regards, Daniel -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#683584: security update ready for wheezy
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 I've now done the following: - - create an upstream 3.3.8 release which includes only the security fix - - imported 3.3.8 into the Debian git VCS: 94324d5e11f1332c0f5adecf17a709 - - update the changelog and control file - - I've added myself as uploader (I am DM and not DD), Stu, can you please verify that this is OK? - - I will also send the unblock request now - - I have NOT made a tag in git - whoever does the upload must make the tag Since 3.3.5 was uploaded into Debian, upstream 3.3.6 and 3.3.7 were released upstream with essential fixes for memory leak and segmentation fault issues. Upstream is not keen to support Ganglia in Debian without these essential fixes. They have been deliberately cherry picked onto a stable 3.3.x series release branch due to their critical nature. In future, the 3.3 branch will only contain the most critical and security related fixes, so it is suitable for Debian wheezy to take releases from the branch without making local patches. Also note that lintian complains a lot because upstream has a submodule with debian artifacts, they are not used at all for the Debian package itself and they should probably be filtered out next time we run git-import-orig -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.12 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iQIcBAEBCAAGBQJQKQUjAAoJEOm1uwJp1aqDYHEP/3HHIBG61goQFfv4uILCUCOy hTpLqc/VzOyTp8yLnXAeRkVB4w++5EsqDHyAtoZkmm1spvsABLmtrmMlRJOmIq4r ShCGRoXQpxR9opPevygccO2CRq+HsTmZJBzS+tNY7mKmsvnABD/3Kh+kt/rtfRP4 g/fwiaGaWcvqRmJawL+piHpvLDF4Iac14aWHqOluesHULKmeQTQnqWVS5KXR6/oI nU0fYOJH81tGp/D3HeHZHSXntrcijFHLMRqNMm9xsrFuA/utfUMLF5gWo44GAlOw Jb+9J2WEGK4F3/BPpwdZZP115/3rJjcaoZ/mXxLGWRh3fypTZvKf/qewnAgqFEQQ p9z2iZtaamRjvjvWuQQlwM/Ak/1XKSobx93kNbwR6+wflYe8JqMJqyqKEiTWCT6s pr42m7usYD2WrfVXG/Sgn2nWoZ+W9Cmu65eotG4Q4fUbM4zLHWrmLZmOxvA1glCh Cp+i3gBQ1h6ac/ZknszyjT4GxzCOqGn76mXyBBiY2e1BYfevJ3LqsTYClpapsd2n 1bsg4XJV/ERoFRgASK6ltRB7uYp3bNly/iwurvwh4I809bwkG6pcVw2FgoRg7k// BMImTeKlmUFs7E4MetdmEnNHSP7TQNHpv/27vKRB8ZOGQj1XbmRZK9s8vzGGYhRf yOAsMzE/eRPm1jmBiNrI =D8JR -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#684733: pyhoca-gui: ImportError: No module named pyhoca.wxgui.basepath
Package: pyhoca-gui Version: 0.2.0.3-1 Severity: grave Justification: renders package unusable pyhoca-gui does not start: $ pyhoca-gui /usr/bin/pyhoca-gui:63: UserWarning: libevent version mismatch: system version is '2.0.19-stable' but this gevent is compiled against '2.0.16-stable' import gevent Traceback (most recent call last): File "/usr/bin/pyhoca-gui", line 96, in from pyhoca.wxgui.basepath import locale_basepath ImportError: No module named pyhoca.wxgui.basepath -- System Information: Debian Release: wheezy/sid APT prefers unstable APT policy: (990, 'unstable') Architecture: i386 (i686) Kernel: Linux 3.2.0-3-686-pae (SMP w/1 CPU core) Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968) Shell: /bin/sh linked to /bin/dash Versions of packages pyhoca-gui depends on: ii gnome-colors-common 5.5.1-1 ii python 2.7.3-2 ii python-notify0.1.1-3 ii python-setproctitle 1.0.1-1+b1 ii python-support 1.0.15 ii python-wxtools 2.8.12.1-11 ii python-x2go 0.2.0.8-1 ii python2.7 [python-argparse] 2.7.3-2 ii wx-common2.8.12.1-11 -- Jakub Wilk -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#684734: pyhoca-cli: ImportError: No module named pyhoca.cli
Package: pyhoca-cli Version: 0.2.0.3-1 Severity: grave Justification: renders package unusable pyhoca-cli doesn't start: $ pyhoca-cli /usr/lib/python2.7/dist-packages/x2go/__init__.py:183: UserWarning: libevent version mismatch: system version is '2.0.19-stable' but this gevent is compiled against '2.0.16-stable' from gevent import monkey Traceback (most recent call last): File "/usr/bin/pyhoca-cli", line 105, in from pyhoca.cli import current_home, PyHocaCLI, runtime_error ImportError: No module named pyhoca.cli -- System Information: Debian Release: wheezy/sid APT prefers unstable APT policy: (990, 'unstable') Architecture: i386 (i686) Kernel: Linux 3.2.0-3-686-pae (SMP w/1 CPU core) Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968) Shell: /bin/sh linked to /bin/dash Versions of packages pyhoca-cli depends on: ii python 2.7.3-2 ii python-setproctitle 1.0.1-1+b1 ii python-x2go 0.2.0.8-1 ii python2.7 [python-argparse] 2.7.3-2 -- Jakub Wilk -- 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#684654: [fglrx-legacy-driver] Xorg shows blank screen with fglrx legacy driver
Processing control commands: > severity 684654 important Bug #684654 [fglrx-legacy-driver] [fglrx-legacy-driver] Xorg shows blank screen with fglrx legacy driver Bug #684655 [fglrx-legacy-driver] [fglrx-legacy-driver] Xorg shows blank screen with fglrx legacy driver Severity set to 'important' from 'grave' Severity set to 'important' from 'grave' -- 684654: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=684654 684655: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=684655 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#684654: [fglrx-legacy-driver] Xorg shows blank screen with fglrx legacy driver
Control: severity 684654 important Hi Beojan, On 2012-08-12 20:03, Beojan Stanislaus wrote: > On Sunday 12 August 2012 19:12:04 Andreas Beckmann wrote: >> Please try the 3.2 kernel from wheezy/sid and the non-rt flavor. > I have, and the bug described persists. Please report this problem to AMD: http://ati.cchtml.com/ This does not look like a packaging problem, so there is not much we can do about this in Debian. On the other hand we got several reports of people successfully running the legacy driver, so I'm downgrading the severity of this bug to important. You might also try the older Xorg versions available in squeeze-backports (or even squeeze). Andreas -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#684552: Not a version in Debian
Hi James! Running apt-rdepends -r clementine reveals that clementine in Debian depends on libprojectm2 which in turn depends on libglew1.7. Nothing in the Debian package depends on libglew1.5. So you either have a local/foreign (as in non Debian oficial) installation of either clementine or libprojectm2. I'm so closing this bug as invalid. Kinds regards, Lisandro. -- 18: Como se pueden evitar los problemas de alimentacion electrica * No coma cerca de un enchufe Damian Nadales http://mx.grulic.org.ar/lurker/message/20080307.141449.a70fb2fc.es.html Lisandro Damián Nicanor Pérez Meyer http://perezmeyer.com.ar/ http://perezmeyer.blogspot.com/ signature.asc Description: This is a digitally signed message part.
Bug#684552: marked as done (clementine: does not start: error while loading shared libraries: libGLEW.so.1.5)
Your message dated Mon, 13 Aug 2012 10:13:36 -0300 with message-id <201208131013.43392.perezme...@gmail.com> and subject line Not a version in Debian has caused the Debian Bug report #684552, regarding clementine: does not start: error while loading shared libraries: libGLEW.so.1.5 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.) -- 684552: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=684552 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: clementine Version: 1.0.1+dfsg-2+b1 Severity: grave Justification: renders package unusable Dear Maintainer, Clementine is no longer starting. running "clementine" at the command line returns the following error clementine: error while loading shared libraries: libGLEW.so.1.5: cannot open shared object file: No such file or directory My system has libglew1.7 installed (no libglew1.5) I tried creating a symlink /usr/lib/x86_64-linux-gnu/libGLEW.so.1.5 pointing to /usr/lib/x86_64-linux-gnu/libGLEW.so.1.7, but I get the following error clementine: error while loading shared libraries: libCg.so: cannot open shared object file: No such file or directory Reinstalling clementine was ineffective. Failed to build from source with the following command: $ apt-get -b source clementine with an error in src/CMakeFiles/clementine_lib.dir/visualisations/projectmvisualisation.cpp.o Regards, James -- System Information: Debian Release: wheezy/sid APT prefers testing APT policy: (500, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 3.2.0-3-amd64 (SMP w/2 CPU cores) Locale: LANG=en_AU.UTF-8, LC_CTYPE=en_AU.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages clementine depends on: ii gstreamer0.10-plugins-base 0.10.36-1 ii gstreamer0.10-plugins-good 0.10.31-3 ii gstreamer0.10-plugins-ugly 0.10.19-2+b2 ii libc62.13-33 ii libcdio130.83-4 ii libchromaprint0 0.6-2 ii libechonest1.2 1.2.1-1 ii libgcc1 1:4.7.1-2 ii libgdk-pixbuf2.0-0 2.26.1-1 ii libglib2.0-0 2.32.3-1 ii libgpod4 0.8.2-6 ii libgstreamer-plugins-base0.10-0 0.10.36-1 ii libgstreamer0.10-0 0.10.36-1 ii libimobiledevice21.1.1-4 ii libindicate-qt1 0.2.5.91-5 ii liblastfm0 0.4.0~git20090710-2 ii libmtp9 1.1.3-35-g0ece104-2 ii libplist11.8-1 ii libprojectm2 2.1.0+dfsg-1 ii libqjson00.7.1-6 ii libqt4-dbus 4:4.8.2-1 ii libqt4-network 4:4.8.2-1 ii libqt4-opengl4:4.8.2-1 ii libqt4-sql 4:4.8.2-1 ii libqt4-sql-sqlite4:4.8.2-1 ii libqt4-xml 4:4.8.2-1 ii libqtcore4 4:4.8.2-1 ii libqtgui44:4.8.2-1 ii libqxt-gui0 0.6.1-6 ii libstdc++6 4.7.1-2 ii libtag1c2a 1.7.2-1 ii libusb-1.0-0 2:1.0.11-1 ii libusbmuxd1 1.0.7-2 ii libx11-6 2:1.5.0-1 ii libxml2 2.8.0+dfsg1-5 ii projectm-data2.1.0+dfsg-1 ii zlib1g 1:1.2.7.dfsg-13 Versions of packages clementine recommends: ii gstreamer0.10-alsa0.10.36-1 ii gstreamer0.10-pulseaudio 0.10.31-3 clementine suggests no packages. -- no debconf information --- End Message --- --- Begin Message --- Hi James! Running apt-rdepends -r clementine reveals that clementine in Debian depends on libprojectm2 which in turn depends on libglew1.7. Nothing in the Debian package depends on libglew1.5. So you either have a local/foreign (as in non Debian oficial) installation of either clementine or libprojectm2. I'm so closing this bug as invalid. Kinds regards, Lisandro. -- 18: Como se pueden evitar los problemas de alimentacion electrica * No coma cerca de un enchufe Damian Nadales http://mx.grulic.org.ar/lurker/message/20080307.141449.a70fb2fc.es.html Lisandro Damián Nicanor Pérez Meyer http://perezmeyer.com.ar/ http://perezmeyer.blogspot.com/ signature.asc Description: This is a digitally signed message part. --- End Message ---
Bug#684722: w3af: Does not start : " pybloomfiltermmap is a required dependency"
Package: w3af Version: 1.1svn5547-1 Severity: grave Tags: upstream Justification: renders package unusable Dear Maintainer, When I launch "w3af" I get the following messages : Additional information: pybloomfiltermmap is a required dependency in *nix systems,in order to install it please run the following commands:sudo apt-get install python2.6-dev sudo easy_install pybloomfiltermmap System stats : - Python-2.6-dev is installed OK apt-get install python2.6-dev Reading package lists... Done Building dependency tree Reading state information... Done python2.6-dev is already the newest version. 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. - easy_install pybloomfiltermmap is OK : easy_install pybloomfiltermmap Searching for pybloomfiltermmap Best match: pybloomfiltermmap 0.3.2 Processing pybloomfiltermmap-0.3.2-py2.6-linux-x86_64.egg pybloomfiltermmap 0.3.2 is already the active version in easy-install.pth Using /usr/local/lib/python2.6/dist-packages/pybloomfiltermmap-0.3.2-py2.6 -linux-x86_64.egg Processing dependencies for pybloomfiltermmap Finished processing dependencies for pybloomfiltermmap Regards JP P -- System Information: Debian Release: wheezy/sid APT prefers unstable APT policy: (500, 'unstable'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 3.5.0-x (SMP w/4 CPU cores) Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages w3af depends on: ii graphviz 2.26.3-12 ii python 2.7.3-2 ii python-gtk22.24.0-3 ii python-gtksourceview2 2.10.1-2 ii python-support 1.0.15 ii w3af-console 1.1svn5547-1 w3af recommends no packages. w3af 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
Processed: wishlist
Processing commands for cont...@bugs.debian.org: > severity 684607 wishlist Bug #684607 [schroot] schroot could give usefull errormessages on ENOSPC Severity set to 'wishlist' from 'grave' > thanks Stopping processing here. Please contact me if you need assistance. -- 684607: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=684607 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#684720: apt-mirror crashes on line 473
Package: apt-mirror Version: 0.4.8-3 Severity: grave Justification: renders package unusable Apt-mirror crashes every time I run it. I have reinstalled the package and installed it on a different machine with default mirrors.list but I still get the same error. The output is: $ sudo -u apt-mirror /usr/bin/apt-mirror Downloading 22 index files using 20 threads... Begin time: Mon Aug 13 13:27:14 2012 [20]... [19]... [18]... [17]... [16]... [15]... [14]... [13]... [12]... [11]... [10]... [9]... [8]... [7]... [6]... [5]... [4]... [3]... [2]... [1]... [0]... End time: Mon Aug 13 13:27:14 2012 Proceed indexes: [Sapt-mirror: invalid Sources format at /usr/bin/apt-mirror line 473, line 6920. It does not matter if I'm running as root, normal user or the apt-mirror user. regards //Rikard -- Information: Debian Release: 6.0.5 APT prefers stable APT policy: (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 2.6.32-5-amd64 (SMP w/16 CPU cores) Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968) Shell: /bin/sh linked to /bin/dash Versions of packages apt-mirror depends on: ii adduser3.112+nmu2add and remove users and groups ii perl 5.10.1-17squeeze3 Larry Wall's Practical Extraction ii perl-modules 5.10.1-17squeeze3 Core Perl modules ii wget 1.12-2.1 retrieves files from the web apt-mirror recommends no packages. apt-mirror 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#684607: Chroot setup failed: stage=setup-start
retitle 684607 schroot could give usefull errormessages on ENOSPC severity 684607 whishlist kthxbye Hi! This was indeed lack of disk-space on the partition the chroots live on, sorry for the confusion. Might however be usefull to give a more concrete hint on what is failing ;-) Regards Christoph -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#684708: mdadm: support external metadata arrays correctly
On 13.08.2012 14:10, Miquel van Smoorenburg wrote: > Package: mdadm > Version: 3.2.5-1 > Severity: serious > Tags: patch wheezy sid > > The initramfs hook supplied by mdadm doesn't install mdmon. Also, mdmon > is not included in the .udeb for the installer. > > This means that if you have an array with external metadata (ddf or, > more widely used, imsm - Intel Matrix Raid) that it will come up > readonly. This causes the installer to hang or the system not being > able to boot if root is on that array. I'm not sure this is the right course of actions -- speaking of the initramfs part, not about the d-i part. What's wrong with the array being started read-only? Root filesystem has always been mounted readonly in initrd/initramfs. There's no fsck tool included in initramfs. Once we switch to real root, we may start mdmon and remount filesystem(s) read-write as appropriate, after fsck'ing them etc. Why the system is not being able to boot if root is on such an array? > The attached patch does a couple of things: > > - it makes sure mdadm is included in the initramfs and the udeb package Sure it is needed in the d-i (udeb), because d-i have to write the system to it. But I'm not convinced it is needed in the initramfs. > - it adds a mdadm-waitidle script that runs just before reboot/halt. For all > arrays that are still running, it sets safe_mode_delay to a low version, > sets sync_action to idle, and waits for the array(s) to go idle. > This is needed so that the array is clean, otherwise it will start > to resync at the next boot. This is risky - we may never finish shutdown. This is especially risky for things like raid - eg, stalled raid (resync) thread (we've seen these more than once) -- in such cases current code will shut down, but with this wait it wont anymore. Especially useful for remote systems. Such an approach should be tested with extra care, I'm not sure we have resources to do that for wheezy. Generally it is a good idea I think. > - it adds 2 lines of code to mdmon.c so that it symlinks its pidfile > into /run/sendsigs.omit.d - mdmon should not be killed at shutdown, > we still need it after the rootfs has been unmounted. And I'm not sure this is needed, either: it can trivially be done in the initscript. > I have added support for installation on Intel Matrix raid (imsm) > arrays using mdadm to d-i, and I'll be sending patches to the debian-boot > list soon. Please consider this patch for inclusion in wheezy. So far I think the only real change there is the inclusion of mdmon to the udeb, the other changes are a bit questionable for wheezy. 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#639472: marked as done (pgsql-asn1oid: Please move from postgresql-8.4 to postgresql-9.1)
Your message dated Mon, 13 Aug 2012 13:29:07 +0200 with message-id <5028e503.7040...@hogyros.de> and subject line Fixed in 0.0.20100818-2 has caused the Debian Bug report #639472, regarding pgsql-asn1oid: Please move from postgresql-8.4 to postgresql-9.1 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.) -- 639472: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=639472 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: pgsql-asn1oid Version: 0.0.20100818-1 Severity: important User: mp...@debian.org Usertags: psql-8.4-deprecation Hello, as announced recently [1] we want to move Debian unstable/testing to postgresql-9.1 and drop postgresql-8.4 and -9.0 completely. Please rebuild this package against postgresql-server-dev-9.1 instead of -8.4, or consider just using postgresql-server-dev-all. Thank you in advance! Martin [1] http://lists.alioth.debian.org/pipermail/pkg-postgresql-public/2011-August/000570.html -- Martin Pitt| http://www.piware.de Ubuntu Developer (www.ubuntu.com) | Debian Developer (www.debian.org) signature.asc Description: Digital signature --- End Message --- --- Begin Message --- -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 The latest upload, version 0.0.20100818-2 fixed both of these bugs. Simon -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.12 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iJwEAQECAAYFAlAo5QIACgkQ0sfeulffv7tHQwP/fLubn7A7bYyMfByUFjrXkWj3 g6QH+22DIYJKtEtPsOYh+J1cHfYYnVP920Pi0f+nTOHJW5kkbhh9C47nhjlpYTBI RpLNLpakiyUeKjAr19M1tJrbxvCsBBnngJnw8IJSdgdrXFKIbxMs/utYywE+AcBE ZPcvSoBVrFFTGvsbHiY= =eM34 -END PGP SIGNATURE End Message ---
Bug#599725: marked as done (pgsql-asn1oid: FTBFS: *** No rule to make target `/usr/lib/postgresql/9.0/lib/pgxs/src/makefiles/pgxs.mk'. Stop.)
Your message dated Mon, 13 Aug 2012 13:29:07 +0200 with message-id <5028e503.7040...@hogyros.de> and subject line Fixed in 0.0.20100818-2 has caused the Debian Bug report #599725, regarding pgsql-asn1oid: FTBFS: *** No rule to make target `/usr/lib/postgresql/9.0/lib/pgxs/src/makefiles/pgxs.mk'. Stop. 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.) -- 599725: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=599725 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: pgsql-asn1oid Version: 0.0.20100818-1 Severity: serious > > sbuild (Debian sbuild) 0.60.0 (23 Feb 2010) on porpora.debian.org > > ╔══╗ > ║ pgsql-asn1oid 0.0.20100818-1 (powerpc) 10 Oct 2010 > 13:59 ║ > ╚══╝ [...] > dpkg-buildpackage: host architecture powerpc > /usr/bin/fakeroot debian/rules clean > dh clean >dh_testdir >dh_auto_clean >dh_clean > debian/rules build > dh build >dh_testdir >dh_auto_configure >dh_auto_build > Makefile:7: /usr/lib/postgresql/9.0/lib/pgxs/src/makefiles/pgxs.mk: No such > file or directory > make[1]: Entering directory > `/build/buildd-pgsql-asn1oid_0.0.20100818-1-powerpc-gUrPaB/pgsql-asn1oid-0.0.20100818' > make[1]: *** No rule to make target > `/usr/lib/postgresql/9.0/lib/pgxs/src/makefiles/pgxs.mk'. Stop. > make[1]: Leaving directory > `/build/buildd-pgsql-asn1oid_0.0.20100818-1-powerpc-gUrPaB/pgsql-asn1oid-0.0.20100818' > dh_auto_build: make -j1 returned exit code 2 > make: *** [build] Error 2 > dpkg-buildpackage: error: debian/rules build gave error exit status 2 > > Build finished at 20101010-1401 > FAILED [dpkg-buildpackage died] > > Purging > /var/lib/schroot/mount/sid-powerpc-sbuild-ebb543c3-b0bb-4a05-b17a-7dab94210e5a/build/buildd-pgsql-asn1oid_0.0.20100818-1-powerpc-gUrPaB > Not removing build depends: cloned chroot in use > > Finished at 20101010-1401 > Build needed 00:01:29, 84k disc space signature.asc Description: Digital signature --- End Message --- --- Begin Message --- -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 The latest upload, version 0.0.20100818-2 fixed both of these bugs. Simon -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.12 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iJwEAQECAAYFAlAo5QIACgkQ0sfeulffv7tHQwP/fLubn7A7bYyMfByUFjrXkWj3 g6QH+22DIYJKtEtPsOYh+J1cHfYYnVP920Pi0f+nTOHJW5kkbhh9C47nhjlpYTBI RpLNLpakiyUeKjAr19M1tJrbxvCsBBnngJnw8IJSdgdrXFKIbxMs/utYywE+AcBE ZPcvSoBVrFFTGvsbHiY= =eM34 -END PGP SIGNATURE End Message ---
Processed (with 1 errors): Re: Bug#684607: Chroot setup failed: stage=setup-start
Processing commands for cont...@bugs.debian.org: > retitle 684607 schroot could give usefull errormessages on ENOSPC Bug #684607 [schroot] Chroot setup failed: stage=setup-start Changed Bug title to 'schroot could give usefull errormessages on ENOSPC' from 'Chroot setup failed: stage=setup-start' > severity 684607 whishlist Severity level `whishlist' is not known. Recognized are: critical, grave, serious, important, normal, minor, wishlist, fixed. > kthxbye Stopping processing here. Please contact me if you need assistance. -- 684607: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=684607 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: found 682631 in 2.34-1
Processing commands for cont...@bugs.debian.org: > found 682631 2.34-1 Bug #682631 [python-distutils-extra] linaro-image-tools: FTBFS: AttributeError: 'tuple' object has no attribute 'major' Bug #682634 [python-distutils-extra] nautilus-image-manipulator: FTBFS: AttributeError: 'tuple' object has no attribute 'major' Marked as found in versions python-distutils-extra/2.34-1. Marked as found in versions python-distutils-extra/2.34-1. > thanks Stopping processing here. Please contact me if you need assistance. -- 682631: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=682631 682634: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=682634 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#684713: parted: support for partitioned MD devices
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; }
Bug#684708: mdadm: support external metadata arrays correctly
Package: mdadm
Version: 3.2.5-1
Severity: serious
Tags: patch wheezy sid
The initramfs hook supplied by mdadm doesn't install mdmon. Also, mdmon
is not included in the .udeb for the installer.
This means that if you have an array with external metadata (ddf or,
more widely used, imsm - Intel Matrix Raid) that it will come up
readonly. This causes the installer to hang or the system not being
able to boot if root is on that array.
The attached patch does a couple of things:
- it makes sure mdadm is included in the initramfs and the udeb package
- it adds a mdadm-waitidle script that runs just before reboot/halt. For all
arrays that are still running, it sets safe_mode_delay to a low version,
sets sync_action to idle, and waits for the array(s) to go idle.
This is needed so that the array is clean, otherwise it will start
to resync at the next boot.
- it adds 2 lines of code to mdmon.c so that it symlinks its pidfile
into /run/sendsigs.omit.d - mdmon should not be killed at shutdown,
we still need it after the rootfs has been unmounted.
I have added support for installation on Intel Matrix raid (imsm)
arrays using mdadm to d-i, and I'll be sending patches to the debian-boot
list soon. Please consider this patch for inclusion in wheezy.
Mike.
Binary files orig/mdadm-3.2.5/debian/.rules.swp and mdadm-3.2.5/debian/.rules.swp differ
diff -ruN orig/mdadm-3.2.5/debian/changelog mdadm-3.2.5/debian/changelog
--- orig/mdadm-3.2.5/debian/changelog 2012-05-25 20:05:23.0 +0200
+++ mdadm-3.2.5/debian/changelog 2012-08-06 23:30:04.171100029 +0200
@@ -1,3 +1,14 @@
+mdadm (3.2.5-1+1) unstable; urgency=low
+
+ * also install mdmon in udeb and initramfs, so imsm arrays work
+ * mdmon now automatically makes a symlink in /run/sendsigs.omit.d to its pidfile
+ * create /run/sendsigs.omit.d/ in local-top script
+ * add script mdadm-waitidle that runs just before reboot/halt. For all
+arrays that are still running, it sets safe_mode_delay to a low version,
+sets sync_action to idle, and waits for the array(s) to go idle.
+
+ -- Miquel van Smoorenburg Mon, 06 Aug 2012 23:29:32 +0200
+
mdadm (3.2.5-1) unstable; urgency=low
[ Michael Tokarev ]
diff -ruN orig/mdadm-3.2.5/debian/initramfs/hook mdadm-3.2.5/debian/initramfs/hook
--- orig/mdadm-3.2.5/debian/initramfs/hook 2012-05-25 19:31:37.0 +0200
+++ mdadm-3.2.5/debian/initramfs/hook 2012-08-02 00:32:50.925671675 +0200
@@ -49,6 +49,7 @@
}
MDADM=/sbin/mdadm
+MDMON=/sbin/mdmon
[ -x "$MDADM" ] || exit 0
[ -r /usr/share/initramfs-tools/hook-functions ] || exit 0
@@ -56,6 +57,7 @@
# copy the binary as early as possible
copy_exec $MDADM /sbin
+copy_exec $MDMON /sbin
# copy all modules into the initramfs, just for safety.
# we copy raid456 / raid5+raid6 because the hook script just won't do
diff -ruN orig/mdadm-3.2.5/debian/initramfs/script.local-top mdadm-3.2.5/debian/initramfs/script.local-top
--- orig/mdadm-3.2.5/debian/initramfs/script.local-top 2012-05-10 22:22:16.0 +0200
+++ mdadm-3.2.5/debian/initramfs/script.local-top 2012-08-06 17:32:30.162720885 +0200
@@ -53,6 +53,9 @@
# handle /dev/md/X nodes
mkdir -p /dev/md
+# mdmon wants this directory to exist
+mkdir -p /run/sendsigs.omit.d
+
CONFIG=/etc/mdadm/mdadm.conf
# in case the hook failed to install a configuration file, this is our last
# attempt... the "emergency procedure"...
diff -ruN orig/mdadm-3.2.5/debian/mdadm-waitidle mdadm-3.2.5/debian/mdadm-waitidle
--- orig/mdadm-3.2.5/debian/mdadm-waitidle 1970-01-01 01:00:00.0 +0100
+++ mdadm-3.2.5/debian/mdadm-waitidle 2012-08-06 23:49:22.138176669 +0200
@@ -0,0 +1,76 @@
+#!/bin/sh
+### BEGIN INIT INFO
+# Provides: mdadm-waitidle
+# Required-Start:
+# Required-Stop:
+# Should-Stop: halt reboot kexec
+# X-Stop-After: umountroot
+# Default-Start:
+# Default-Stop: 0 6
+# Short-Description: Wait for MD arrays to become idle
+# Description: This script waits until all MD arrays are
+#in idle and synced state before halt/reboot.
+### END INIT INFO
+#
+set -eu
+
+. /lib/lsb/init-functions
+
+case "${1:-}" in
+ start)
+;;
+ stop)
+cd /sys/block
+for md in md*
+do
+ if [ -d "$md/md/" ]
+ then
+if [ -w $md/md/safe_mode_delay ]; then
+ echo 0.05 > $md/md/safe_mode_delay ||:
+fi
+if [ -w $md/md/sync_action ]; then
+ echo idle > $md/md/sync_action ||:
+fi
+array_found=1
+ fi
+done
+[ -z "$array_found" ] && exit 0
+
+log_action_begin_msg "Waiting for MD arrays to become idle"
+sync
+start=`date +%s`
+secs=0
+while [ $secs -lt 10 ]
+do
+ secs=$((`date +%s` - $start))
+ active=
+ for md in md*
+ do
+# We wait for normal writes, but not too long for resyncs/rebuilds.
+state="`cat $md/md/array_state 2>/dev/null || echo unknown`"
+sync="`cat $md/md/sync_action 2>/dev/null || echo idle`"
+if [
Bug#681979: python3.3-minimal: fails to purge: subprocess installed post-removal script returned error exit status 1
tags 681979 + moreinfo thanks >>From the attached log (scroll to the bottom...): > > Removing python3.3-minimal ... > Purging configuration files for python3.3-minimal ... > dpkg: error processing python3.3-minimal (--purge): >subprocess installed post-removal script returned error exit status 1 > Errors were encountered while processing: >python3.3-minimal > > Adding set -x to the postrm: > > Removing python3.3-minimal ... > Purging configuration files for python3.3-minimal ... > + [ purge = remove ] > + [ purge = purge ] > + find /usr/lib/python3.3 -depth -type d -empty > + rm -f /etc/python3.3/site.py /etc/python3.3/sitecustomize.py > + rmdir --ignore-fail-on-non-empty /etc/python3.3 > dpkg: error processing python3.3-minimal (--purge): >subprocess installed post-removal script returned error exit status 1 > Errors were encountered while processing: >python3.3-minimal> which files are still left in /etc/python3.3? -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#680291: xml2rfc: fails to install, remove, distupgrade, and install again
Hi, On 04/07 10:16, Andreas Beckmann wrote: > during a test with piuparts I noticed your package failed to install > (in 'squeeze'), remove (but not purge), distupgrade to 'wheezy', > and install again. > Before the second installation the package is in config-files-remaining > state. The configuration is remaining from the last version that was > successfully configured - which is from the previous release. > > Like a plain failure on initial install this makes the package too buggy > for a release, thus the severity. This seems to be related to the changes introduced to dh_installcatalogs (see #477751). Helmut, I took the liberty to put you in CC as you probably have some hints for how to proceed? Note that other packages might show the same behavior reported here: docbook-website comes to mind. Thanks, Emanuele -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Processed: severity of 684698 is serious
Processing commands for cont...@bugs.debian.org: > severity 684698 serious Bug #684698 [ifupdown] ifupdown: ifup incorrectly ups vlan interfaces using ip link Severity set to 'serious' from 'important' > thanks Stopping processing here. Please contact me if you need assistance. -- 684698: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=684698 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#684479: marked as done (wheezy: Network File Services are major issue in Wheezy.)
Your message dated Mon, 13 Aug 2012 11:19:47 +0200 with message-id <201208131119.48187.hol...@layer-acht.org> and subject line Re: Processed: Re: Bug#684479: wheezy: Network File Services are major issue in Wheezy. has caused the Debian Bug report #684479, regarding wheezy: Network File Services are major issue in Wheezy. 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.) -- 684479: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=684479 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: wheezy Version: Wheezy Severity: serious Justification: required Dear Maintainer, *** Please consider answering these questions, where appropriate *** * What led up to the situation? Network File services hung up the fresh Wheezy startup. * What exactly did you do (or not do) that was effective (or ineffective)? I had to boot in rescue mode, then removed NFS related packages. * What was the outcome of this action? Wheezy boots up like Squeeze did before * What outcome did you expect instead? *** End of the template - remove these lines *** Also /etc/pm/sleep.d/56nfs script file that I made for NFS months ago prevented pm-suspend. On Squeeze it won't affect suspend action at all. Simply removing the file from /etc/pm/sleep.d directory solved non-suspend problem at least in my system. -- System Information: Debian Release: wheezy/sid APT prefers unstable APT policy: (500, 'unstable'), (500, 'testing'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 3.2.0-3-amd64 (SMP w/2 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash --- End Message --- --- Begin Message --- Hi, closing this bug as you could not demonstrate which package caused your bug and I also highly suspect your suspen-script caused this. Feel free to provide evidence there is a real bug. cheers, Holger--- End Message ---
Processed: Re: Bug#684479: wheezy: Network File Services are major issue in Wheezy.
Processing commands for cont...@bugs.debian.org: > reassign 684479 general Bug #684479 [wheezy] wheezy: Network File Services are major issue in Wheezy. Warning: Unknown package 'wheezy' Bug reassigned from package 'wheezy' to 'general'. No longer marked as found in versions Wheezy. Ignoring request to alter fixed versions of bug #684479 to the same values previously set > thanks Stopping processing here. Please contact me if you need assistance. -- 684479: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=684479 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#684479: wheezy: Network File Services are major issue in Wheezy.
reassign 684479 general thanks Hughe Chung writes: > Package: wheezy > Version: Wheezy When filing bugs, especially with reportbug, please make sure you file it against a package that exist, or a pseudo-package reportbug knows about, otherwise your report will not end up sent to the maintainers. I have reassigned your report to 'general' for now, lacking a better idea. -- |8] -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#661471: bug 661471 gnome-accessibility-themes
On Fri, 27 Jul 2012 15:11:30 Jeremy Bicha wrote: > On Tue Jul 10, 2012 at 14:34:34 theppi...@gmail.com wrote: > > On Tue, Jul 10, 2012 at 8:23 PM, Michael Biebl wrote: > > > I think the alternative Martin proposed is to build > > > gnome-accessibility-themes from the gnome-themes-standard source package. > > > > I have also tried it already, but it required the outdated gtk-engines-3.pc. > > See message #28 in the bug log. > > I believe you misunderstand. In Ubuntu almost a year ago, I split > gnome-themes-standard into two binary packages: gnome-themes-standard > and gnome-accessibility-themes. We then dropped the > gnome-themes source package that used to provide > gnome-accessibility-themes. It works pretty well for Ubuntu as we want > to ship the HighContrast themes but not Adwaita due to space You're right. I missed the "from the gnome-themes-standard source package" part in Michael's message. Sorry. So, I agree with splitting the gnome-accessibility-themes binary. 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#684619: [nullmailer] Debconf prompts for info that might contain password, saves to world-readable file
Hi, Thanks for the very good catch on this one. The package is ready to upload but needs a sponsor. Would you be able to spare a bit more time to upload the fix for me, please ? Source is dgettable from http://mentors.debian.net/debian/pool/main/n/nullmailer/nullmailer_1.11-2.dsc If you're busy then thanks for your valuable contribution to the package already, Nick Leverton Debdiff: diff -Nru nullmailer-1.11/debian/changelog nullmailer-1.11/debian/changelog --- nullmailer-1.11/debian/changelog2012-06-16 16:36:28.0 +0100 +++ nullmailer-1.11/debian/changelog2012-08-11 23:55:36.0 +0100 @@ -1,3 +1,9 @@ +nullmailer (1:1.11-2) unstable; urgency=low + + * Make 'remotes' not world-readable (Closes: #684619) + + -- Nick Leverton Sat, 11 Aug 2012 23:54:55 +0100 + nullmailer (1:1.11-1) unstable; urgency=low * New upstream release diff -Nru nullmailer-1.11/debian/postinst nullmailer-1.11/debian/postinst --- nullmailer-1.11/debian/postinst 2012-05-16 08:25:36.0 +0100 +++ nullmailer-1.11/debian/postinst 2012-08-12 20:23:46.0 +0100 @@ -24,10 +24,14 @@ fi db_get nullmailer/relayhost + # securely create nullmailer/remotes with mode 0600 + R=$( tempfile -d /etc/nullmailer -p nullm ) echo "$RET" | sed -r -e ':a s/(\[[^]:]*):/\1=/; ta' \ -e 's/[[:space:]]*:[[:space:]]*/\n/g' \ -e ':b s/(\[[^]=]*)=/\1:/; tb' \ --e 's/[][]//g' > /etc/nullmailer/remotes +-e 's/[][]//g' >> $R + chown mail:mail $R + mv $R /etc/nullmailer/remotes db_get nullmailer/adminaddr if [ "$RET" ]; then -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
