Bug#677297: [rt.debian.org #3892] Re: Bug#677297: kfreebsd-8: cve-2012-0217
On mer., 2012-07-04 at 21:33 +0100, Steven Chamberlain wrote: Hi Security Team, Someone replied on RT ticket #3892 (on which I am Cc'd, but can't view it and don't know the author) the following: Careful, patch in SVN repository can't be used as-is. See: http://lists.debian.org/debian-bsd/2012/06/msg00214.html But that is not true. By then I had already committed to SVN (r4320) a corrected fix supplied by upstream, and followed up on that message with: http://lists.debian.org/debian-bsd/2012/06/msg00246.html Please let me or debian-bsd@ know if anything more is needed for a stable-security upload. Can you show us a debdiff for the package you intend to upload to stable-security? Regards, -- Yves-Alexis signature.asc Description: This is a digitally signed message part
Processed: remove bogus tag
Processing commands for cont...@bugs.debian.org: tags 666468 - unreproducible Bug #666468 [xorg-server] xorg-server: major text display problems in several apps Bug #666538 [xorg-server] xorg-server: major text display problems in several apps Bug #666564 [xorg-server] xorg-server: major text display problems in several apps Bug #666565 [xorg-server] xorg-server: major text display problems in several apps Bug #95 [xorg-server] xorg-server: major text display problems in several apps Bug #666922 [xorg-server] xorg-server: major text display problems in several apps Bug #666998 [xorg-server] xorg-server: major text display problems in several apps Bug #667033 [xorg-server] vim-gtk: Invisible text Bug #667048 [xorg-server] xorg-server: major text display problems in several apps Bug #667073 [xorg-server] xorg-server: major text display problems in several apps Bug #667445 [xorg-server] xorg-server: major text display problems in several apps Bug #667520 [xorg-server] xorg-server: major text display problems in several apps Bug #667809 [xorg-server] xorg-server: major text display problems in several apps Bug #668182 [xorg-server] [gnome-terminal] incorrect partial redraw in mc Bug #668343 [xorg-server] xserver-xorg-video-nouveau: Character rendering failures on GeForce 8600M GT with dual screen Bug #668993 [xorg-server] libgdk-pixbuf2.0-0: Font rendering corruption? Bug #672260 [xorg-server] libxrender1:amd64: transient graphical corruption on many windows after upgrade Bug #674575 [xorg-server] xorg eats CPU time Bug #674783 [xorg-server] xserver-xorg-video-nouveau: Since early 3.x kernel X became very slooow Bug #677183 [xorg-server] xorg: Video corruption Bug #679120 [xorg-server] libdrm-nouveau1a: text corruption using nouveau (not with video, images or 3d) Removed tag(s) unreproducible. Removed tag(s) unreproducible. Removed tag(s) unreproducible. Removed tag(s) unreproducible. Removed tag(s) unreproducible. Removed tag(s) unreproducible. Removed tag(s) unreproducible. Removed tag(s) unreproducible. Removed tag(s) unreproducible. Removed tag(s) unreproducible. Removed tag(s) unreproducible. Removed tag(s) unreproducible. Removed tag(s) unreproducible. Removed tag(s) unreproducible. Removed tag(s) unreproducible. Removed tag(s) unreproducible. Removed tag(s) unreproducible. Removed tag(s) unreproducible. Removed tag(s) unreproducible. Removed tag(s) unreproducible. Removed tag(s) unreproducible. thanks Stopping processing here. Please contact me if you need assistance. -- 666468: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=666468 666538: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=666538 666564: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=666564 666565: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=666565 95: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=95 666922: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=666922 666998: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=666998 667033: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=667033 667048: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=667048 667073: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=667073 667445: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=667445 667520: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=667520 667809: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=667809 668182: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=668182 668343: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=668343 668993: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=668993 672260: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=672260 674575: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=674575 674783: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=674783 677183: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=677183 679120: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=679120 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#680309: marked as done (cdbs: Copyright Check Incorrectly Checks Debian Directory)
Your message dated Thu, 5 Jul 2012 08:44:46 +0200 with message-id 20120705064446.gr9...@jones.dk and subject line Re: [Build-common-hackers] Bug#680309: cdbs: Copyright Check Incorrectly Checks Debian Directory has caused the Debian Bug report #680309, regarding cdbs: Copyright Check Incorrectly Checks Debian Directory 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.) -- 680309: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=680309 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: cdbs Version: 0.4.115 Severity: serious Justification: Causes FTBFS Dear Maintainer, * What led up to the situation? pop-before-smtp FTBFS during a rebuild test. See #674400. * What exactly did you do (or not do) that was effective (or ineffective)? Based on the build logs, it looks like CDBS copyright check is checking the Debian directory even though it says it doesn't in the same log. I updated the copyright hints to match newhings and the package built, but that only works around the issue. * What was the outcome of this action? With the workaround I could build the package locally, but that seems not to be the correct solution * What outcome did you expect instead? Since the build log says, Scanning upstream source for new/changed copyright notices (except debian subdir!)..., my expectation is that it won't scan the Debian subdir. ---End Message--- ---BeginMessage--- Hi Scott, On 12-07-04 at 05:37pm, Scott Kitterman wrote: Based on the build logs, it looks like CDBS copyright check is checking the Debian directory even though it says it doesn't in the same log. I updated the copyright hints to match newhings and the package built, but that only works around the issue. Thanks for your raising this issue. While it is true that pop-before-smtp has FTBFS, it is not caused by any released version of CDBS but instead locally included CDBS snippets. Therefore closing this as a non-bug. Regards, - Jonas -- * Jonas Smedegaard - idealist Internet-arkitekt * Tlf.: +45 40843136 Website: http://dr.jones.dk/ [x] quote me freely [ ] ask before reusing [ ] keep private signature.asc Description: Digital signature ---End Message---
Bug#617409: brasero: Brasero corrupts all blank CD-R when burning (was: additional info)
Hi, i am currently the developer of libburn and libisofs. https://bugzilla.gnome.org/show_bug.cgi?id=655601 I know about such problems, but i do not know how to get into a discussion with Brasero developers. My impression is that the libisofs plugin causes libisofs to end prematurely. libburn is less of a suspect here. I have seen burn logs where burning ends after about 50 % of the expected output was produced by libisofs. I.e. libisofs would want to write more, but for some reason libburn is urged to finish burning (or falsely decides that burning is done). https://bugs.launchpad.net/ubuntu/+source/brasero/+bug/780117 https://launchpadlibrarian.net/71440716/brasero_log.txt have: BraseroLibisofs Finished track successfully BraseroLibisofs disconnecting BraseroLibisofs from BraseroGrowisofs ... BraseroGrowisofs stdout: 3866984448/7761410048 (49.8%) @4.0x, remaining 12:06 RBU 40.9% UBU 100.0% BraseroGrowisofs called brasero_job_get_action BraseroGrowisofs called brasero_job_set_current_action BraseroGrowisofs stderr: /dev/sr0: flushing cache ... BraseroGrowisofs stderr: HUP Note that libburn is not involved here. Only libisofs. Burning is done via growisofs. Further it seems that BraseroLibisofs is the one which decides when the connection between both shall end. But in http://bugzilla-attachments.gnome.org/attachment.cgi?id=205344 the work of libisofs seems to get completed. brasero (libisofs)DEBUG : Processed 138390 of 138390 KB (100 %) So this might be two different problems. (In this run, libburn was indeed in charge of writing to media.) - I am not aware of any changes in libisofs or libburn which about a year ago could have introduced such problems. The combination of libisofs and libburn works fine in xorriso. xorriso does several backups per day for me, which then get thoroughly checked for readability and correct content. If somebody shows up who understands the code of the libisofs plugin and could make experiments, then i would be glad to help with finding the cause of the problem. Have a nice day :) Thomas -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#667755: Request unblock for aiccu 20070115-15.1
Hi, Axel Beckert uploaded a fix for the following bugs in aiccu: Bug#667755: FTBFS[kfreebsd] (serious) http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=667755 Bug#670971: Danish translation http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=670971 Please consider this packages for Wheezy, thanks. Kind Regards, Reinier -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#617409: brasero: Brasero corrupts all blank CD-R when burning (was: additional info)
Le jeudi 05 juillet 2012 à 08:47 +0200, Thomas Schmitt a écrit : Hi, i am currently the developer of libburn and libisofs. https://bugzilla.gnome.org/show_bug.cgi?id=655601 I know about such problems, but i do not know how to get into a discussion with Brasero developers. That would be brasero-list: https://mail.gnome.org/mailman/listinfo/brasero-list Cheers, -- .''`. Josselin Mouette : :' : `. `' `- -- 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#602668: libdevel-bt-perl: FTBFS on armel
Processing commands for cont...@bugs.debian.org: severity 602668 serious Bug #602668 [libdevel-bt-perl] libdevel-bt-perl: FTBFS on armel Severity set to 'serious' from 'important' tag 602668 sid Bug #602668 [libdevel-bt-perl] libdevel-bt-perl: FTBFS on armel Added tag(s) sid. thanks Stopping processing here. Please contact me if you need assistance. -- 602668: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=602668 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#667755: Request unblock for aiccu 20070115-15.1
Hi, On Thu Jul 05, 2012 at 08:51:19 +0200, Reinier Haasjes wrote: Hi, Axel Beckert uploaded a fix for the following bugs in aiccu: Bug#667755: FTBFS[kfreebsd] (serious) http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=667755 Bug#670971: Danish translation http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=670971 Please consider this packages for Wheezy, thanks. As usual sponsor for Reinier, i ACK this request. Cheers, Martin -- Martin Zobel-Helas zo...@debian.org | Debian System Administrator Debian GNU/Linux Developer | Debian Listmaster GPG key http://go.debian.net/B11B627B | GPG Fingerprint: 6B18 5642 8E41 EC89 3D5D BDBB 53B1 AC6D B11B 627B -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#617409: [Pkg-libburnia-devel] Bug#617409: brasero: Brasero corrupts all blank CD-R when burning (was: additional info)
On Thursday 05 July 2012 08:47:15 Thomas Schmitt wrote:
Hi,
Hi All,
i am currently the developer of libburn and libisofs.
https://bugzilla.gnome.org/show_bug.cgi?id=655601
I know about such problems, but i do not know how to get into a
discussion with Brasero developers.
My impression is that the libisofs plugin causes libisofs to end
prematurely. libburn is less of a suspect here.
I have seen burn logs where burning ends after about 50 % of
the expected output was produced by libisofs. I.e. libisofs would
want to write more, but for some reason libburn is urged to finish
burning (or falsely decides that burning is done).
https://bugs.launchpad.net/ubuntu/+source/brasero/+bug/780117
https://launchpadlibrarian.net/71440716/brasero_log.txt
have:
BraseroLibisofs Finished track successfully
BraseroLibisofs disconnecting BraseroLibisofs from BraseroGrowisofs
...
BraseroGrowisofs stdout: 3866984448/7761410048 (49.8%) @4.0x, remaining
12:06 RBU 40.9% UBU 100.0% BraseroGrowisofs called
brasero_job_get_action
BraseroGrowisofs called brasero_job_set_current_action
BraseroGrowisofs stderr: /dev/sr0: flushing cache
...
BraseroGrowisofs stderr: HUP
Note that libburn is not involved here. Only libisofs. Burning is done
via growisofs.
Further it seems that BraseroLibisofs is the one which decides when
the connection between both shall end.
But in
http://bugzilla-attachments.gnome.org/attachment.cgi?id=205344
the work of libisofs seems to get completed.
brasero (libisofs)DEBUG : Processed 138390 of 138390 KB (100 %)
So this might be two different problems.
(In this run, libburn was indeed in charge of writing to media.)
-
I am not aware of any changes in libisofs or libburn which about a year
ago could have introduced such problems.
The combination of libisofs and libburn works fine in xorriso.
xorriso does several backups per day for me, which then get thoroughly
checked for readability and correct content.
If somebody shows up who understands the code of the libisofs plugin
and could make experiments, then i would be glad to help with finding
the cause of the problem.
Same issue already reported long ago at:
https://mail.gnome.org/archives/brasero-list/2011-July/msg4.html
actors: libisofs and growisofs brasero plugins
symptoms: 50% finished at ~49%
Looking at the logs and the brasero plugins code, the main suspect most likely
hidden at:
1) erroneous read of growisofs std out, wrt written data, and buffer filling,
hence a premature leave might occur:
plugins/growisofs/burn-growisofs.c
static BraseroBurnResult
brasero_growisofs_read_stdout (BraseroProcess *process, const gchar *line)
{
int perc_1, perc_2;
int speed_1, speed_2;
long long b_written, b_total;
/* Newer growisofs version have a different line pattern that shows
* drive buffer filling. */
if (sscanf (line, %10lld/%lld (%4d.%1d%%) @%2d.%1dx, remaining %*d:
%*d,
b_written, b_total, perc_1, perc_2, speed_1,
speed_2) == 6) {
BraseroJobAction action;
brasero_job_get_action (BRASERO_JOB (process), action);
if (action == BRASERO_JOB_ACTION_ERASE b_written = 65536)
{
/* we nullified 65536 that's enough. A signal SIGTERM
* will be sent in process.c. That's not the best way
* to do it but it works. */
brasero_job_finished_session (BRASERO_JOB (process));
return BRASERO_BURN_OK;
}
2) premature ending of the libisofs thread:
static gpointer
brasero_libisofs_thread_started (gpointer data) {
...
if (brasero_job_get_fd_out (BRASERO_JOB (self), NULL) ==
BRASERO_BURN_OK)
brasero_libisofs_write_image_to_fd_thread (self);
...
Nothing more concrete norrowed down yet
--
pub 4096R/0E4BD0AB people.fccf.net/danchev/key pgp.mit.edu
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#680344: FTBFS: cp: cannot stat `estraierpure.jar': No such file or directory
Package: hyperestraier Severity: serious Justification: fails to build from source (but built successfully in the past) Dear Maintainer, Some architectures also need to drop building Java binding: armel armhf ia64 mipsel powerpc s390x sparc cf) these are already dropped: kfreebsd-* mips -- System Information: Debian Release: wheezy/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: i386 (i686) Kernel: Linux 2.6.32-11-pve (SMP w/8 CPU cores) Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968) Shell: /bin/sh linked to /bin/dash Versions of packages hyperestraier depends on: ii libc6 2.13-34 pn libestraier8 none pn libfcgi0ldbl none pn libqdbm14 none ii zlib1g1:1.2.7.dfsg-13 Versions of packages hyperestraier recommends: pn ppthtml none pn wv none pn xlhtml none pn xpdf-utils none hyperestraier suggests no packages. -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#680345: FTBFS: Not a CODE reference at /usr/lib/perl/5.14/DynaLoader.pm line 207.
Package: hyperestraier Severity: serious Justification: fails to build from source (but built successfully in the past) Dear Maintainer, It fails to build perl xs because of replacing CCFLAGS with dpkg-buildflags. Instead, it should be set in OPTIMIZE. -- System Information: Debian Release: wheezy/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: i386 (i686) Kernel: Linux 2.6.32-11-pve (SMP w/8 CPU cores) Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968) Shell: /bin/sh linked to /bin/dash Versions of packages hyperestraier depends on: ii libc6 2.13-34 pn libestraier8 none pn libfcgi0ldbl none pn libqdbm14 none ii zlib1g1:1.2.7.dfsg-13 Versions of packages hyperestraier recommends: pn ppthtml none pn wv none pn xlhtml none pn xpdf-utils none hyperestraier suggests no packages. -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#680349: binfmt-support: first update-binfmts --install call fails in chroot with update-binfmts: warning: unable to close /proc/sys/fs/binfmt_misc/register: Invalid argument
Package: binfmt-support Version: 2.0.8 Severity: serious User: debian...@lists.debian.org Usertags: piuparts Hi, during a test with piuparts I noticed a failure in the jarwrapper package whcih I traced to update-binfmts. To reproduce: * the host has the kernel module loaded and /proc/sys/fs/binfmt_misc is mounted, kernel: 3.2.0-2-amd64 * the chroot is a minimal sid or wheezy chroot and /proc/sys/fs/binfmt_misc is not yet mounted, but /proc is mounted * apt-get install jarwrapper [...] Setting up binfmt-support (2.0.9) ... invoke-rc.d: policy-rc.d denied execution of start. Setting up fastjar (2:0.98-3) ... Setting up jarwrapper (0.43) ... update-binfmts: warning: unable to close /proc/sys/fs/binfmt_misc/register: Invalid argument update-binfmts: warning: unable to enable binary format jarwrapper update-binfmts: exiting due to previous errors dpkg: error processing jarwrapper (--configure): subprocess installed post-installation script returned error exit status 2 Errors were encountered while processing: jarwrapper * now /proc/sys/fs/binfmt_misc got mounted and the foloowing succeeds: * dpkg --configure --pending Setting up jarwrapper (0.43) ... The problem can be reproduced inside this chroot easily: # umount /proc/sys/fs/binfmt_misc/ # update-binfmts --install jarwrapper /usr/bin/jarwrapper --magic 'PK\x03\x04' --detector /usr/bin/jardetector update-binfmts: warning: unable to close /proc/sys/fs/binfmt_misc/register: Invalid argument update-binfmts: warning: unable to enable binary format jarwrapper update-binfmts: exiting due to previous errors # update-binfmts --install jarwrapper /usr/bin/jarwrapper --magic 'PK\x03\x04' --detector /usr/bin/jardetector echo success success I'm setting the severity to serious as this breaks installation and testing of unrelated packages. (And I'll add here Affects/Found in the other packages s.t. piuparts can find this bugreport for automated classification) Looking at the code, /proc/sys/fs/binfmt_misc/register gets opened (but does not exist), then /proc/sys/fs/binfmt_misc gets mounted and brings its own /proc/sys/fs/binfmt_misc/register, thereafter the originally opened /proc/sys/fs/binfmt_misc/register no longer seems to exist and closing fails. Andreas -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#680238: Please drop libggi support
On Thu, Jul 05, 2012 at 10:49:33AM +0800, Aron Xu wrote: On Wed, Jul 4, 2012 at 10:42 PM, Moritz Muehlenhoff j...@debian.org wrote: Package: zhcon Severity: important libggi is scheduled for removal in Wheezy: http://lists.debian.org/debian-release/2012/07/msg00134.html Please disable libggi support. Cheers, Moritz Hi, I have uploaded a version with libggi disabled to unstable, would you handle freeze exceptions for zhcon, or I should do it by myself? Thanks! I'll take care of the unblock request. Cheers, Moritz -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#680351: 389-ds-base: fails to install: 10 389-ds-base/setup doesn't exist
Package: 389-ds-base Version: 1.2.11.7-2 Severity: serious User: debian...@lists.debian.org Usertags: piuparts Hi, during a test with piuparts I noticed your package failed to install. As per definition of the release team this makes the package too buggy for a release, thus the severity. From the attached log (scroll to the bottom...): Selecting previously unselected package 389-ds-base. (Reading database ... 9713 files and directories currently installed.) Unpacking 389-ds-base (from .../389-ds-base_1.2.11.7-2_amd64.deb) ... Setting up 389-ds-base (1.2.11.7-2) ... dpkg: error processing 389-ds-base (--configure): subprocess installed post-installation script returned error exit status 10 Errors were encountered while processing: 389-ds-base Since that is not really helpful, I'm setting some more debug options: # DEBCONF_DEBUG=developer dpkg --configure --pending Setting up 389-ds-base (1.2.11.7-2) ... debconf (developer): frontend started debconf (developer): frontend running, package name is 389-ds-base debconf (developer): starting /var/lib/dpkg/info/389-ds-base.config configure debconf (developer): -- INPUT high 389-ds-base/setup debconf (developer): -- 10 389-ds-base/setup doesn't exist dpkg: error processing 389-ds-base (--configure): subprocess installed post-installation script returned error exit status 10 Errors were encountered while processing: 389-ds-base This looks like a non-existing debconf template gets used. cheers, Andreas 389-ds-base_1.2.11.7-2.log.gz Description: GNU Zip compressed data
Processed: severity of 673542 is grave
Processing commands for cont...@bugs.debian.org: severity 673542 grave Bug #673542 [libpng12-0] libpng12-0_1.5.10-2 sends gdm3 and Xorg in an infinite loop, breaking the whole graphical system Bug #673645 [libpng12-0] libpng12: version PNG12_0 not found error Severity set to 'grave' from 'important' Severity set to 'grave' from 'important' thanks Stopping processing here. Please contact me if you need assistance. -- 673542: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=673542 673645: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=673645 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed: Re: E: Could not perform immediate configuration on 'phonon-backend-vlc'.
Processing commands for cont...@bugs.debian.org: severity 669278 serious Bug #669278 [phonon] please add phonon-backend-xine transitional package Bug #669878 [phonon] Could not perform immediate configuration on 'phonon-backend-vlc' Severity set to 'serious' from 'important' Severity set to 'serious' from 'important' thanks Stopping processing here. Please contact me if you need assistance. -- 669278: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=669278 669878: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=669878 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#679283: marked as done (CVE-2012-2825)
Your message dated Thu, 05 Jul 2012 09:47:39 + with message-id e1smiex-0002eh...@franck.debian.org and subject line Bug#679283: fixed in libxslt 1.1.26-13 has caused the Debian Bug report #679283, regarding CVE-2012-2825 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.) -- 679283: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=679283 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: libxslt Severity: grave Tags: security The Chrome developers found a denial of service issue in the embedded copy of libxslt, which has been assigned CVE-2012-2825: http://googlechromereleases.blogspot.de/2012/06/stable-channel-update_26.html: [$500] [127417] Medium CVE-2012-2825: Wild read in XSL handling. Credit to Nicholas Gregoire. This is fixed by the following commit: http://git.chromium.org/gitweb/?p=chromium/src.git;a=patch;h=bb7bfb81c158268fb242292b7e0fbd2d3b933d09 Cheers, Moritz ---End Message--- ---BeginMessage--- Source: libxslt Source-Version: 1.1.26-13 We believe that the bug you reported is fixed in the latest version of libxslt, which is due to be installed in the Debian FTP archive: libxslt1-dbg_1.1.26-13_amd64.deb to main/libx/libxslt/libxslt1-dbg_1.1.26-13_amd64.deb libxslt1-dev_1.1.26-13_amd64.deb to main/libx/libxslt/libxslt1-dev_1.1.26-13_amd64.deb libxslt1.1_1.1.26-13_amd64.deb to main/libx/libxslt/libxslt1.1_1.1.26-13_amd64.deb libxslt_1.1.26-13.debian.tar.gz to main/libx/libxslt/libxslt_1.1.26-13.debian.tar.gz libxslt_1.1.26-13.dsc to main/libx/libxslt/libxslt_1.1.26-13.dsc python-libxslt1-dbg_1.1.26-13_amd64.deb to main/libx/libxslt/python-libxslt1-dbg_1.1.26-13_amd64.deb python-libxslt1_1.1.26-13_amd64.deb to main/libx/libxslt/python-libxslt1_1.1.26-13_amd64.deb xsltproc_1.1.26-13_amd64.deb to main/libx/libxslt/xsltproc_1.1.26-13_amd64.deb 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. Aron Xu a...@debian.org (supplier of updated libxslt 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: Thu, 05 Jul 2012 11:09:19 +0800 Source: libxslt Binary: libxslt1.1 libxslt1-dev libxslt1-dbg xsltproc python-libxslt1 python-libxslt1-dbg Architecture: source amd64 Version: 1.1.26-13 Distribution: unstable Urgency: low Maintainer: Debian XML/SGML Group debian-xml-sgml-p...@lists.alioth.debian.org Changed-By: Aron Xu a...@debian.org Description: libxslt1-dbg - XSLT 1.0 processing library - debugging symbols libxslt1-dev - XSLT 1.0 processing library - development kit libxslt1.1 - XSLT 1.0 processing library - runtime library python-libxslt1 - Python bindings for libxslt1 python-libxslt1-dbg - Python bindings for libxslt1 (debug extension) xsltproc - XSLT 1.0 command line processor Closes: 679283 Changes: libxslt (1.1.26-13) unstable; urgency=low . * Patch to fix CVE-2012-2825 (Closes: #679283). Checksums-Sha1: 4f8b009f451f5c3d0590c1d4ad49c6d3452b63a4 1970 libxslt_1.1.26-13.dsc 9bb1fbcaf3f9d55c304f964f3e8158c1c66dd459 30490 libxslt_1.1.26-13.debian.tar.gz 09a617d1273432f096ba91824a309f50edfd7ea3 251796 libxslt1.1_1.1.26-13_amd64.deb da9938042ac3e12e10237308a4031b19d8df7734 649602 libxslt1-dev_1.1.26-13_amd64.deb ac17da9f2e293f2c10453f6fd91f22a5b04b5afc 501882 libxslt1-dbg_1.1.26-13_amd64.deb d98d4882b9a4ca07b32e5c51b7b314d427955b8a 115842 xsltproc_1.1.26-13_amd64.deb 90d99b38d61d243b1994c496e4fbd893561f0861 170512 python-libxslt1_1.1.26-13_amd64.deb 589b2e390270e37f0a3ceec1bd826dc8e79fc1fd 409606 python-libxslt1-dbg_1.1.26-13_amd64.deb Checksums-Sha256: 367b7ab79158e09103cc6bc2f01de5206481be5e64f0f4dd605c2de76f5243e5 1970 libxslt_1.1.26-13.dsc 11272bd2ab7273cb17e073f5916e8fc1084a0ddb8b84a68bdb3f5f0bca0f7cc4 30490 libxslt_1.1.26-13.debian.tar.gz 137d94f0e914a69de909da759bff1a39c8941cbceb4c5e3fc96b024393f7be1b 251796 libxslt1.1_1.1.26-13_amd64.deb 897b1b88f2773ed5e127ab6bec0dd206be0bde07f573afb0edadb9a832f24fee 649602 libxslt1-dev_1.1.26-13_amd64.deb b3c97d05fcee537b49d786348f5e683e51b8456f87f55f7181dbe765fefb6b69 501882 libxslt1-dbg_1.1.26-13_amd64.deb 94056f97f3d8abc154969d309c9529c7dd43c6dc5d37ce81558f91be59c7877b 115842
Bug#673542: libpng12-0_1.5.10-2 sends gdm3 and Xorg in an infinite loop, breaking the whole graphical system
On Thu, Jul 5, 2012 at 13:30:41 +0900, Nobuhiro Iwamatsu wrote: severity 673542 important thanks Hi, All those compat packages in 1.5.x are completely broken. libpng15-15 does not have the same ABI as libpng12-0. So making libpng12-0_1.5.10 a compat package depending on libpng15-15 and creating symlinks makes absolutely no sense. The same is true for libpng3 and the libpng12-dev package. The package depending on libpng12 will hardly work, as you have pointed out. However, this was due to be solved by transition of libpng15 altogether. Regrettably, since some packages have not been supported yet, the transition to libpng15 is not performed by wheezy. The main reason it's not being performed is that the libpng maintainers have shown time and time again that they don't know what they are doing. And I have a feeling that this is not RC bug. Your feeling is wrong. I change severity of this bug to important. And I change it back. Cheers, Julien signature.asc Description: Digital signature
Bug#617409: [Pkg-libburnia-devel] Bug#617409: brasero: Brasero corrupts all blank CD-R when burning (was: additional info)
Hi,
I'd suggest the attached patch to be applied, so we can better see what
happens to the growisofs child process.
The code unconditinally calls WEXITSTATUS (status) without making sure that
WIFEXITED has returned true. This is undefined... but whatever - a separate
issue. (also I don't actually like brasero_process_watch_child() to be
utilized like that: g_timeout_add (500, brasero_process_watch_child, process);
but this could be tweaked later)
Reporters, could you please do the following:
apt-get source brasero
apt-get build-dep brasero
put the attached patch in debian/patches/
echo check-child-status debian/patches/series
dpkg-buildpackage
and install this one... then try to reproduce the promlem, and get us the logs
so we can better see what is going on with our beloved growisofs process.
--
pub 4096R/0E4BD0AB people.fccf.net/danchev/key pgp.mit.edu
--- brasero-3.4.1.orig/libbrasero-burn/burn-process.c
+++ brasero-3.4.1/libbrasero-burn/burn-process.c
@@ -294,12 +294,27 @@ brasero_process_watch_child (gpointer da
* brasero_job_finished/_error is called before the pipes are closed so
* as to let plugins read stderr / stdout till the end and set a better
* error message or simply decide all went well, in one word override */
- priv-return_status = WEXITSTATUS (status);
+/*
+ priv-return_status = WEXITSTATUS (status);
+*/
priv-watch = 0;
priv-pid = 0;
-
+ if (WIFEXITED(status)) { /* WEXITSTATUS macro should only be used if
WIFEXITED returned true */
+ printf(process exited, status=%d\n, WEXITSTATUS(status));
+ priv-return_status = WEXITSTATUS (status);
+ BRASERO_JOB_LOG (data, process exited with status %d,
WEXITSTATUS (status));
+ }
+ else if (WIFSIGNALED(status)) {
+ printf(process killed by signal %d\n, WTERMSIG(status));
+ BRASERO_JOB_LOG (data, process killed by signal %d,
WTERMSIG(status));
+ }
+ else if (WIFSTOPPED(status)) {
+ printf(process stopped by signal %d\n, WSTOPSIG(status));
+ BRASERO_JOB_LOG (data, process stopped by signal %d,
WSTOPSIG(status));
+ }
+/*
BRASERO_JOB_LOG (data, process finished with status %i, WEXITSTATUS
(status));
-
+*/
result = brasero_process_finished (data);
if (result == BRASERO_BURN_RETRY) {
GError *error = NULL;
Processed: fixed 650703 in 290.10-1, tagging 650703, tagging 630940, tagging 567400, tagging 554169 ...
Processing commands for cont...@bugs.debian.org:
fixed 650703 290.10-1
Bug #650703 {Done: Andreas Beckmann deb...@abeckmann.de} [nvidia-settings]
nvidia-settings: Can not use X Server Display Configuration due to error
Marked as fixed in versions nvidia-settings/290.10-1.
tags 650703 - moreinfo
Bug #650703 {Done: Andreas Beckmann deb...@abeckmann.de} [nvidia-settings]
nvidia-settings: Can not use X Server Display Configuration due to error
Removed tag(s) moreinfo.
tags 630940 + wontfix
Bug #630940 {Done: Andreas Beckmann deb...@abeckmann.de}
[nvidia-kernel-legacy-96xx-dkms] nvidia-kernel-legacy-96xx-dkms: X server fails
to start using nvidia-legacy-96xx-dkms from sid
Added tag(s) wontfix.
tags 567400 + wontfix
Bug #567400 {Done: Andreas Beckmann deb...@abeckmann.de}
[nvidia-glx-legacy-96xx] python-visual doesn't work with
nvidia-glx-legacy-96xx, works with other video adapters
Added tag(s) wontfix.
tags 554169 + wontfix
Bug #554169 {Done: Andreas Beckmann deb...@abeckmann.de}
[nvidia-graphics-drivers-legacy-96xx] xserver-xorg-core: Option
AddARGBGLXVisuals in xorg.conf with nvidia driver causes improper function of
OpenGL apps
Added tag(s) wontfix.
tags 680199 + pending
Bug #680199 [fglrx-driver] fglrx-driver: [INTL:es] Spanish debconf translation
for fglrx-driver
Added tag(s) pending.
notfixed 627119 295.25-1
Bug #627119 {Done: Andreas Beckmann deb...@abeckmann.de} [nvidia-glx]
nvidia-glx ext are loaded but compiz/kde-effects causes Xserver freeze
There is no source info for the package 'nvidia-glx' at version '295.25-1' with
architecture ''
Unable to make a source version for version '295.25-1'
No longer marked as fixed in versions 295.25-1.
found 672160 1.80
Bug #672160 [console-setup] console-setup: unowned files after purge (policy
6.8, 10.8)
Marked as found in versions console-setup/1.80.
affects 679847 + ruby-hpricot
Bug #679847 [ruby-fast-xs] ruby-hpricot and ruby-fast-xs: error when trying to
install together
Added indication that 679847 affects ruby-hpricot
found 679847 ruby-hpricot/0.8.6-3
Bug #679847 [ruby-fast-xs] ruby-hpricot and ruby-fast-xs: error when trying to
install together
Marked as found in versions ruby-hpricot/0.8.6-3.
affects 680349 + jarwrapper
Bug #680349 [binfmt-support] binfmt-support: first update-binfmts --install
call fails in chroot with update-binfmts: warning: unable to close
/proc/sys/fs/binfmt_misc/register: Invalid argument
Added indication that 680349 affects jarwrapper
found 680349 jarwrapper/0.43
Bug #680349 [binfmt-support] binfmt-support: first update-binfmts --install
call fails in chroot with update-binfmts: warning: unable to close
/proc/sys/fs/binfmt_misc/register: Invalid argument
The source jarwrapper and version 0.43 do not appear to match any binary
packages
Marked as found in versions jarwrapper/0.43.
found 668751 1.0.1-1
Bug #668751 [liquidsoap] liquidsoap: unowned directory after purge:
/usr/share/liquidsoap
Marked as found in versions liquidsoap/1.0.1-1.
found 669278 kde-plasma-desktop/5:76
Bug #669278 [phonon] please add phonon-backend-xine transitional package
Bug #669878 [phonon] Could not perform immediate configuration on
'phonon-backend-vlc'
The source kde-plasma-desktop and version 5:76 do not appear to match any
binary packages
Marked as found in versions kde-plasma-desktop/5:76.
Marked as found in versions kde-plasma-desktop/5:76.
found 669278 digikam/4:2.6.0-1
Bug #669278 [phonon] please add phonon-backend-xine transitional package
Bug #669878 [phonon] Could not perform immediate configuration on
'phonon-backend-vlc'
Marked as found in versions digikam/4:2.6.0-1.
Marked as found in versions digikam/4:2.6.0-1.
found 669278 kdebase-workspace/4:4.8.4-2
Bug #669278 [phonon] please add phonon-backend-xine transitional package
Bug #669878 [phonon] Could not perform immediate configuration on
'phonon-backend-vlc'
The source kdebase-workspace and version 4:4.8.4-2 do not appear to match any
binary packages
Marked as found in versions kdebase-workspace/4:4.8.4-2.
Marked as found in versions kdebase-workspace/4:4.8.4-2.
found 669278 python-kde4/4:4.8.4-1
Bug #669278 [phonon] please add phonon-backend-xine transitional package
Bug #669878 [phonon] Could not perform immediate configuration on
'phonon-backend-vlc'
The source python-kde4 and version 4:4.8.4-1 do not appear to match any binary
packages
Marked as found in versions python-kde4/4:4.8.4-1.
Marked as found in versions python-kde4/4:4.8.4-1.
found 669278 koffice-dbg/1:2.4.2+1
Bug #669278 [phonon] please add phonon-backend-xine transitional package
Bug #669878 [phonon] Could not perform immediate configuration on
'phonon-backend-vlc'
The source koffice-dbg and version 1:2.4.2+1 do not appear to match any binary
packages
Marked as found in versions koffice-dbg/1:2.4.2+1.
Marked as found in versions koffice-dbg/1:2.4.2+1.
found 669278 kdeutils/4:4.8.4+5.76
Bug #669278 [phonon] please add phonon-backend-xine transitional package
Bug #669878 [phonon]
Bug#679981: marked as done (asus-oled-dkms: FTBFS: tries to build module immediately)
Your message dated Thu, 05 Jul 2012 10:02:09 + with message-id e1smisz-0007nb...@franck.debian.org and subject line Bug#679981: fixed in asus-oled-dkms 0.04-2 has caused the Debian Bug report #679981, regarding asus-oled-dkms: FTBFS: tries to build module immediately 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.) -- 679981: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=679981 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Source: asus-oled-dkms Version: 0.04-1 Severity: serious Justification: fails to build from source Builds of asus-oled-dkms in minimal environments are failing because they lack the kernel headers necessary to prebuild the module. However, because dkms will take care of building the module as needed on users' systems, there is no point in attempting to do so ahead of time; please override dh_auto_build to be a no-op. On a related note, I would recommend changing the package's architecture from any to all. Thanks! ---End Message--- ---BeginMessage--- Source: asus-oled-dkms Source-Version: 0.04-2 We believe that the bug you reported is fixed in the latest version of asus-oled-dkms, which is due to be installed in the Debian FTP archive: asus-oled-dkms_0.04-2.debian.tar.gz to main/a/asus-oled-dkms/asus-oled-dkms_0.04-2.debian.tar.gz asus-oled-dkms_0.04-2.dsc to main/a/asus-oled-dkms/asus-oled-dkms_0.04-2.dsc asus-oled-dkms_0.04-2_all.deb to main/a/asus-oled-dkms/asus-oled-dkms_0.04-2_all.deb 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. Roman V. Nikolaev rsha...@rambler.ru (supplier of updated asus-oled-dkms 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: RIPEMD160 Format: 1.8 Date: Thu, 05 Jul 2012 13:06:58 +0400 Source: asus-oled-dkms Binary: asus-oled-dkms Architecture: source all Version: 0.04-2 Distribution: unstable Urgency: low Maintainer: Roman V. Nikolaev rsha...@rambler.ru Changed-By: Roman V. Nikolaev rsha...@rambler.ru Description: asus-oled-dkms - Driver for Asus OLED display present in some Asus laptops Closes: 679981 Changes: asus-oled-dkms (0.04-2) unstable; urgency=low . * Apply debian patch from Evgeni Golov. Closes: #679981 Checksums-Sha1: 890d0abd466a81457446b7ef5e058cbf6bf896cb 1231 asus-oled-dkms_0.04-2.dsc dbc90bc67a7a28df646e443e9e70818972f6674e 2202 asus-oled-dkms_0.04-2.debian.tar.gz 08e5a78cb738278ada75aadd3ad6df444af30594 13592 asus-oled-dkms_0.04-2_all.deb Checksums-Sha256: c2d72a998cc6bd5f9273efa73335a356738ad3e3340d3998c9a086919f5d2648 1231 asus-oled-dkms_0.04-2.dsc a584a62452615a73e06151f7b07e45030cef77df58ddee0f8308bf4b7978e3d3 2202 asus-oled-dkms_0.04-2.debian.tar.gz aca8531cf8a5fc5d8e756341e0ed2dc6e32dd99a8fc87f935da2afcf8c56a52c 13592 asus-oled-dkms_0.04-2_all.deb Files: 53efdc2776539df2c2a21c1bbd3998f3 1231 misc optional asus-oled-dkms_0.04-2.dsc 4942d4896a2d88ed8305bc0e31a3499b 2202 misc optional asus-oled-dkms_0.04-2.debian.tar.gz 3e0a92185658b5d3cc4b471feb8e4b0d 13592 misc optional asus-oled-dkms_0.04-2_all.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.12 (GNU/Linux) iEYEAREDAAYFAk/1ZWUACgkQq4wAz/jiZTeVMwCfYUlRUXqFluxpCXbxZLXHmJ0s f0EAn3PG5uE8YbniWtBx6BixqAnr0bQw =n0Nn -END PGP SIGNATURE- ---End Message---
Bug#673469: #673469 libwebkitgtk-1.0-0: segfaults all the time on armel, javascript related
Hi, It looks like this is the relevant upstream bug (though it's not totally clear if the original reporter is on armel or armhf) I am on armel but you need to Cc me if you ask for more information. 673...@bugs.debian.org only goes to the maintainer of the package and not the submitter. -Timo -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#617409: brasero: Brasero corrupts all blank CD-R when burning (was: additional info)
Hi, Paul Menzel wrote: So unfortunately it looks like there is no list for Brasero and you need to use the GNOME Bugzilla bug tracker. Well, there is a list, the last entry is of january 2012, and it complains about the burn errors which seem to have emerged in spring 2011. https://mail.gnome.org/archives/brasero-list/2012-January/thread.html I tried to contact Brasero developers in december 2011 when i finally had implemented CD-TEXT, a feature which they missed in libburn when they adopted it. No reaction. We'd need somebody who wants to maintain at least the plugins for libisofs and libburn. I myself am a command-line guy and thus heavily unsuitable for that job. rpnpif hinted in his original message, that the media was corrupted because the wrong write speed was used. I doubt, but cannot completely outrule this for the runs which report libisofs progress up to 100 %. The drives take the speed instructions only as a hint. Then they decide what speed to use. Of course, the drive can still do it wrong, when it gets the speed request. But that would be an individual firmware flaw. Those are often related to particular types of media (brands, manufacturers). One can find out the media producer by xorriso -outdev /dev/sr0 -toc | grep 'Media product' which will tell something like CD: Media product: 97m15s35f/79m59s74f , Nan-Ya Plastics Corporation DVD: Media product: RITEK/004/48 , Ritek Corp BD: Media product: VERBATIM/IM0/0 , Mitsubishi Kagaku Media Co. If there is suspicion, that the drive does not like the media brand, then try to get some which shows a different Media product:. This might be not easy because most brands sell media from varying manufacturers. (Hint: Verbatim only sells Mitsubishi media. So if the current media are not Verbatim or Mitsubishi Kagaku then Verbatim media will surely be different from those ones. The same is mostly true vice versa.) Surely speed or media incompatibility is not the reason for those runs where libisofs progress reached only about 50 %. libisofs and libburn were not free of bugs during the last year. But none of the resolved ones would explain what Brasero users report. Thanks for that offer. Hopefully, rpnpif and Simon can chime in so that this release critical bug can be resolved. I hate to say it, but it seems to be easiest to just disable the libisofs plugin. I understand that Ubuntu already moves into that direction. xorriso could step in by its emulation of mkisofs and cdrecord (single data track only). cdrskin could step in as a more versatile emulation of cdrecord (audio, multiple tracks in one session). This would of course not have the advantages of using the two libraries with their message queues and well definded APIs. Have a nice day :) Thomas -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#617409: brasero: Brasero corrupts all blank CD-R when burning (was: additional info)
Hi, Josselin Mouette wrote: That would be brasero-list: https://mail.gnome.org/mailman/listinfo/brasero-list Is there a chance that we could work together to find out what's wrong ? If not George Danchev's patch already brings insight, that is. Released libisofs-1.2.2 would be a good test bed. Of course we could also use libisofs SVN which currently is moving towards the next release 1.2.4 and already got some testing. Have a nice day :) Thomas -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#679819: Dropping Provides field broke depending software (python-avogadro)
* Daniel Leidert daniel.leid...@wgdd.de, 2012-07-04, 22:19: python-avogadro is the only package in the archive that depends on python2.7-qt4. I think it makes more sense to fix it there than in python-qt4 and depend on a bug in poilcy, but since that's what it says, I'll fix it in python-qt4 if you prefer. I would prefer if you re-add the Provides field in python-qt4. While I'm not a fan of python:Provides, and I agree that python-avogadro should stop depending on python2.X-foo packages, removing virtual packages at this point of release cycle is not really reasonable, specially when reverse-dependencies still exist. Scott, can you add them back? -- 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: Debian Bug 676543 oolite silently exit
Processing commands for cont...@bugs.debian.org: fixed 676543 oolite/1.76.1-2 Bug #676543 [oolite] oolite silently exit on debian wheezy Marked as fixed in versions oolite/1.76.1-2. thanks Stopping processing here. Please contact me if you need assistance. -- 676543: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=676543 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#656088: gforge-web-apache2: prompting due to modified conffiles which where not modified by the user
Hi Roland, sorry, it took me a while to answer this ... On 2012-03-20 14:24, Roland Mas wrote: I'm not sure there's a way to fix that without touching the packages in stable; Touching stable is not an option, this needs to be fixed by the package in squeeze. so, while I agree this bug is valid for the squeeze-wheezy upgrade, it should be tagged as only concerning versions up to 5.1.1-2. What do you think? How does /etc/gforge/httpd.conf get created? Is there any local customization (like a hostname) by default or is it the sam efile in all installations (until customized)? If you can limit the possible files created by the package in squeeze just collect all possible md5sums of unmodified configuration files. Then in the preinst compute the md5sum of an existing /etc/gforge/httpd.conf and compare it to the list, move it aside it matching and delete the backup in postinst. This will allow installation of the clean new file without prompting. IIRC the initscripts and basefiles packages in sid do something similar for /etc/default/rcS and /etc/profile Andreas -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#679819: Dropping Provides field broke depending software (python-avogadro)
I can. Thanks for the second opinion. -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#680084: postinst script gets stuck
Hi Yann, On 07/04/12 19:56, Yann Dirson wrote: 2. the output of strace -p pid root@ppcl007:~# strace -p 3648 Process 3648 attached - interrupt to quit read(11, In that case, we'll need to know what's hidden behind file descriptor 11. You can use ls -l /proc/pid/fd/ to find out. root@nobody:~# ls -al /proc/8460/fd total 0 dr-x-- 2 root root 0 Jul 5 13:23 . dr-xr-xr-x 8 root root 0 Jul 5 13:22 .. lrwx-- 1 root root 64 Jul 5 13:24 0 - /dev/pts/0 lrwx-- 1 root root 64 Jul 5 13:24 1 - /dev/pts/0 lr-x-- 1 root root 64 Jul 5 13:24 10 - pipe:[640169] lr-x-- 1 root root 64 Jul 5 13:24 11 - pipe:[638542] lr-x-- 1 root root 64 Jul 5 13:24 12 - pipe:[640170] lrwx-- 1 root root 64 Jul 5 13:23 2 - /dev/pts/0 lrwx-- 1 root root 64 Jul 5 13:24 3 - /dev/pts/0 lrwx-- 1 root root 64 Jul 5 13:24 4 - /var/cache/debconf/config.dat lrwx-- 1 root root 64 Jul 5 13:24 5 - /var/cache/debconf/passwords.dat lrwx-- 1 root root 64 Jul 5 13:24 6 - /var/cache/debconf/templates.dat l-wx-- 1 root root 64 Jul 5 13:24 8 - pipe:[638541] lrwx-- 1 root root 64 Jul 5 13:24 9 - /dev/pts/0 You can also get info from debconf itself. Setting DEBCONF_DEBUG=developer while running dpkg can help. root@ppcl007:~# dpkg -i /var/cache/apt/archives/memtest86+_4.20-1.1_amd64.deb (Reading database ... 241701 files and directories currently installed.) Preparing to replace memtest86+ 4.20-1.1 (using .../memtest86+_4.20-1.1_amd64.deb) ... Unpacking replacement memtest86+ ... Generating grub.cfg ... Found linux image: /boot/vmlinuz-3.2.0-3-amd64 Found initrd image: /boot/initrd.img-3.2.0-3-amd64 Found memtest86+ image: /memtest86+.bin Found memtest86+ multiboot image: /memtest86+_multiboot.bin grub-probe: error: no such disk. done Setting up memtest86+ (4.20-1.1) ... debconf (developer): frontend started debconf (developer): frontend running, package name is memtest86+ debconf (developer): starting /var/lib/dpkg/info/memtest86+.config configure debconf (developer): -- INPUT medium shared/memtest86-run-lilo debconf (developer): -- 30 question skipped debconf (developer): -- GO debconf (developer): -- 0 ok debconf (developer): starting /var/lib/dpkg/info/memtest86+.postinst configure debconf (developer): -- GET shared/memtest86-run-lilo debconf (developer): -- 0 false Generating grub.cfg ... Found linux image: /boot/vmlinuz-3.2.0-3-amd64 Found initrd image: /boot/initrd.img-3.2.0-3-amd64 Found memtest86+ image: /memtest86+.bin Found memtest86+ multiboot image: /memtest86+_multiboot.bin grub-probe: error: no such disk. done Maybe some information about the disk layout helps, too: /dev/sda is the only disk installed. /dev/sda1 /boot ext4 /dev/sda2 encrypted physical volume for lvm2: /dev/mapper/pv00physical volume /dev/mapper/vg00-root / filesystem ext4 /dev/mapper/vg00-swap swap /dev/mapper/vg00-root2 empty ext4 /dev/mapper/vg00-export empty ext4 Hope this helps Regards Harri -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#679548: marked as done (opendkim silently stops when IPv6 addreses are involved)
Your message dated Thu, 05 Jul 2012 11:47:39 + with message-id e1smkx5-0002mt...@franck.debian.org and subject line Bug#679548: fixed in opendkim 2.6.2-1 has caused the Debian Bug report #679548, regarding opendkim silently stops when IPv6 addreses are involved 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.) -- 679548: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=679548 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: opendkim Version: 2.0.1+dfsg-1 Severity: grave Tags: ipv6 Justification: renders package unusable specifying PeerList199.192.231.53,2605:eb00:100:1::2085:29b0 lets opendkim stop silently when trying to start teh daemon. This happens also when disabling PeerList entirely and changing Socket inet:8891@127.0.0.1 to Socket inet:8891@::1 It seems that opendkim is not IPv6 capable and so unusable when running IPv6 enabled MTAs. -- System Information: Debian Release: 6.0.5 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 2.6.32-5-amd64 (SMP w/1 CPU core) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages opendkim depends on: ii adduser3.112+nmu2add and remove users and groups ii libc6 2.11.3-3 Embedded GNU C Library: Shared lib ii libdb4.8 4.8.30-2 Berkeley v4.8 Database Libraries [ ii libldap-2.4-2 2.4.23-7.2OpenLDAP libraries ii liblua5.1-05.1.4-5 Simple, extensible, embeddable pro ii libmilter1.0.1 8.14.3-9.4Sendmail Mail Filter API (Milter) ii libopendkim1 2.0.1+dfsg-1 Library for signing and verifying ii libssl0.9.80.9.8o-4squeeze13 SSL shared libraries ii libunbound21.4.6-1+squeeze2 library implementing DNS resolutio opendkim recommends no packages. opendkim suggests no packages. -- no debconf information ---End Message--- ---BeginMessage--- Source: opendkim Source-Version: 2.6.2-1 We believe that the bug you reported is fixed in the latest version of opendkim, which is due to be installed in the Debian FTP archive: libopendkim-dev_2.6.2-1_i386.deb to main/o/opendkim/libopendkim-dev_2.6.2-1_i386.deb libopendkim7_2.6.2-1_i386.deb to main/o/opendkim/libopendkim7_2.6.2-1_i386.deb libvbr-dev_2.6.2-1_i386.deb to main/o/opendkim/libvbr-dev_2.6.2-1_i386.deb libvbr2_2.6.2-1_i386.deb to main/o/opendkim/libvbr2_2.6.2-1_i386.deb opendkim-tools_2.6.2-1_i386.deb to main/o/opendkim/opendkim-tools_2.6.2-1_i386.deb opendkim_2.6.2-1.diff.gz to main/o/opendkim/opendkim_2.6.2-1.diff.gz opendkim_2.6.2-1.dsc to main/o/opendkim/opendkim_2.6.2-1.dsc opendkim_2.6.2-1_i386.deb to main/o/opendkim/opendkim_2.6.2-1_i386.deb opendkim_2.6.2.orig.tar.gz to main/o/opendkim/opendkim_2.6.2.orig.tar.gz 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. Scott Kitterman sc...@kitterman.com (supplier of updated opendkim 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, 02 Jul 2012 14:44:38 -0400 Source: opendkim Binary: opendkim opendkim-tools libopendkim7 libopendkim-dev libvbr2 libvbr-dev Architecture: source i386 Version: 2.6.2-1 Distribution: unstable Urgency: low Maintainer: Mike Markley m...@markley.org Changed-By: Scott Kitterman sc...@kitterman.com Description: libopendkim-dev - Headers and development libraries for the OpenDKIM library libopendkim7 - Library for signing and verifying DomainKeys Identified Mail sign libvbr-dev - Headers and development libraries for the OpenDKIM VBR library libvbr2- Library for RFC 5518 Vouch By Reference (VBR) opendkim - Milter implementation of DomainKeys Identified Mail opendkim-tools - Set of command line tools for OpenDKIM Closes: 679548 679852 Changes: opendkim (2.6.2-1) unstable; urgency=low . * New upstream release (addresses three bugs that affect the Debian package) - Fix bug #SF3539449: Clarify legal Socket values. Requested by Scott Kitterman. - Fix bug
Bug#676543: Debian Bug 676543 oolite silently exit
I keep this bug open because Georgiewskiy did not subscribe to the
upstream BTS. The attached patch reverts the libmojs-dev -
mozjs185-dev changes, hoping to get a crashing executable *and* a
meaningful backtrace.
To build 1.76.1-2, you did:
$ apt-get source --tar-only oolite
$ git clone git://anonscm.debian.org/pkg-games/oolite.git
$ cd oolite
$ grep Build-Depends -A4 debian/control
$ sudo apt-get missing_build_dependencies
$ DEB_BUILD_OPTIONS=noopt nostrip debuild -us -uc
$ sudo dpkg -i ../oolite*.deb
Now, please:
$ debuild clean
$ git status # Check that workspace is clean.
$ git checkout 7e5f3143858f0f4d38ccc501a73dd5d35a77b4d7 # Check revision.
$ patch -p1 /tmp/allow_nostrip_for_1.76.1-1.diff
$ DEB_BUILD_OPTIONS=noopt nostrip debuild -us -uc
$ sudo dpkg -i ../oolite*.deb
There is no need to test both strip/nostrip versions, they should
produce the same assembly code.
diff --git a/debian/control b/debian/control
index 0e27861..6893d75 100644
--- a/debian/control
+++ b/debian/control
@@ -7,10 +7,9 @@ Standards-Version: 3.9.3
Build-Depends: dpkg-dev (= 1.16.1), debhelper (= 9),
libsdl1.2-dev, libsdl-mixer1.2-dev,
libgnustep-base-dev, gnustep-core-devel,
- libnspr4-dev, libmozjs185-dev,
- libpng-dev, mesa-common-dev, gobjc, libffi-dev
-# Work-around: Oolite does not Build-Depend on libffi-dev, but
-# libmozjs185-dev does (reported as #).
+ libnspr4-dev, libmozjs-dev (= 2.0~),
+ libpng-dev, mesa-common-dev,
+gobjc
Homepage: http://www.oolite.org
Vcs-Git: git://git.debian.org/pkg-games/oolite.git
Vcs-Browser: http://git.debian.org/?p=pkg-games/oolite.git
diff --git a/debian/patches/debian_version_of_libmozjs.diff b/debian/patches/debian_version_of_libmozjs.diff
index a442105..40d7c38 100644
--- a/debian/patches/debian_version_of_libmozjs.diff
+++ b/debian/patches/debian_version_of_libmozjs.diff
@@ -1,24 +1,33 @@
Description: use Debian/unstable version of libmozjs
Upstream downloads libmozjs v4 from a private URL at build time.
.
- We adapt the source to use 1.8.5 packaged in Debian.
- This part of the work has been forwarded upstream
- but changes have been necessary since.
+ We adapt the source to use the version available in Debian.
+ This part of the work is forwarded upstream.
.
JSOPTION_ANONFUNFIX has been removed in mozjs, see
https://bugzilla.mozilla.org/show_bug.cgi?id=665835
.
- The main API difference is that older JSScript memory allocation
- is hidden inside the associated JSObject.
+ jsxdrapi.h does not provide C compatibility anymore.
Author: Nicolas Boulenguez nicolas.bouleng...@free.fr
Forwarded: Michael Werle mi...@michaelwerle.com
Index: b/src/Core/Scripting/OOJSScript.m
===
a/src/Core/Scripting/OOJSScript.m 2012-06-25 09:36:25.0 +0200
-+++ b/src/Core/Scripting/OOJSScript.m 2012-06-25 09:37:49.0 +0200
-@@ -58,11 +58,11 @@
+--- a/src/Core/Scripting/OOJSScript.m 2012-05-12 21:53:26.0 +0200
b/src/Core/Scripting/OOJSScript.m 2012-05-30 16:45:05.0 +0200
+@@ -22,6 +22,10 @@
+
+ */
+
++/* Work-around because jsxdrapi.h does not provide */
++/* (Objective) C compatibility anymore. */
++#define OO_CACHE_JS_SCRIPTS 0
++
+ #ifndef OO_CACHE_JS_SCRIPTS
+ #define OO_CACHE_JS_SCRIPTS 1
+ #endif
+@@ -58,11 +62,11 @@
static void AddStackToArrayReversed(NSMutableArray *array, RunningStack *stack);
@@ -33,7 +42,7 @@ Index: b/src/Core/Scripting/OOJSScript.m
#endif
static NSString *StrippedName(NSString *string);
-@@ -111,8 +111,7 @@
+@@ -111,8 +115,7 @@
{
JSContext*context = NULL;
NSString*problem = nil; // Acts as error flag.
@@ -43,7 +52,7 @@ Index: b/src/Core/Scripting/OOJSScript.m
jsval returnValue = JSVAL_VOID;
NSEnumerator *keyEnum = nil;
NSString*key = nil;
-@@ -142,7 +141,7 @@
+@@ -142,7 +145,7 @@
problem = @could not add JavaScript root object;
}
@@ -52,7 +61,7 @@ Index: b/src/Core/Scripting/OOJSScript.m
{
problem = @could not add JavaScript root object;
}
-@@ -168,7 +167,7 @@
+@@ -168,7 +171,7 @@
if (!problem)
{
OOLog(@script.javaScript.willLoad, @About to load JavaScript %@, path);
@@ -61,10 +70,12 @@ Index: b/src/Core/Scripting/OOJSScript.m
}
OOLogIndentIf(@script.javaScript.willLoad);
-@@ -205,10 +204,9 @@
+@@ -203,12 +206,9 @@
+ problem = @could not run script;
+ }
OOJSStopTimeLimiter();
-
- // We don't need the script any more - the event handlers hang around as long as the JS object exists.
+-
+- // We don't need the script any more - the event handlers hang around as long as the JS object exists.
- JS_DestroyScript(context, script);
}
@@ -73,7 +84,7 @@ Index: b/src/Core/Scripting/OOJSScript.m
sRunningStack = stackElement.back;
-@@ -620,16 +618,16 @@
+@@ -620,16 +620,16 @@
}
@@ -93,17 +104,17 @@ Index: b/src/Core/Scripting/OOJSScript.m
*outErrorMessage = nil;
#if
Bug#679819: [Python-modules-team] Bug#679819: Dropping Provides field broke depending software (python-avogadro)
sip4 will cause you the same problem. I'll take care of that too. -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#677297: [rt.debian.org #3892] Re: Bug#677297: kfreebsd-8: cve-2012-0217
On 05/07/12 07:00, Yves-Alexis Perez wrote:
Can you show us a debdiff for the package you intend to upload to
stable-security?
Hi, Please find debdiff attached.
Thank you!
Regards,
--
Steven Chamberlain
ste...@pyro.eu.org
diff -u kfreebsd-8-8.1+dfsg/debian/changelog
kfreebsd-8-8.1+dfsg/debian/changelog
--- kfreebsd-8-8.1+dfsg/debian/changelog
+++ kfreebsd-8-8.1+dfsg/debian/changelog
@@ -1,3 +1,12 @@
+kfreebsd-8 (8.1+dfsg-8+squeeze3) stable-security; urgency=medium
+
+ [ Steven Chamberlain ]
+ * Apply upstream SA-12:04.sysret patch (CVE-2012-0217) (Closes: #677297)
+- Include correction from upstream (r237241)
+ * Apply upstream EN-12:02.ipv6refcount patch (Closes: #677738)
+
+ -- GNU/kFreeBSD Maintainers debian-...@lists.debian.org Tue, 19 Jun 2012
13:18:39 +0100
+
kfreebsd-8 (8.1+dfsg-8+squeeze2) stable-security; urgency=low
* Add 000_unix_socket_overflow.diff and 918_unix_socket_overflow.diff:
diff -u kfreebsd-8-8.1+dfsg/debian/patches/series
kfreebsd-8-8.1+dfsg/debian/patches/series
--- kfreebsd-8-8.1+dfsg/debian/patches/series
+++ kfreebsd-8-8.1+dfsg/debian/patches/series
@@ -1,3 +1,5 @@
+SA-12_04.sysret.patch
+EN-12_02.ipv6refcount.patch
000_adaptive_machine_arch.diff
000_ata.diff
000_coda.diff
only in patch2:
unchanged:
--- kfreebsd-8-8.1+dfsg.orig/debian/patches/SA-12_04.sysret.patch
+++ kfreebsd-8-8.1+dfsg/debian/patches/SA-12_04.sysret.patch
@@ -0,0 +1,37 @@
+Description:
+ Correct a privilege escalation when returning from kernel if
+ running FreeBSD/amd64 on non-AMD processors. [12:04]
+ .
+ Includes a corrected patch from upstream, as the original commit to
+ RELENG_8_1 accidentally applied it to the wrong location.
+Origin: vendor, http://security.freebsd.org/patches/SA-12:04/sysret.patch
+Bug: http://security.freebsd.org/advisories/FreeBSD-SA-12:04.sysret.asc
+Bug-Debian: http://bugs.debian.org/677297
+Applied-Upstream: http://svnweb.freebsd.org/base?view=revisionrevision=237241
+
+Index: kfreebsd-8-8.1+dfsg/sys/amd64/amd64/trap.c
+===
+--- kfreebsd-8-8.1+dfsg.orig/sys/amd64/amd64/trap.c2012-06-17
13:55:31.0 +0100
kfreebsd-8-8.1+dfsg/sys/amd64/amd64/trap.c 2012-06-19 12:44:37.299956401
+0100
+@@ -1010,4 +1010,21 @@
+ STOPEVENT(p, S_SCX, sa.code);
+
+ PTRACESTOP_SC(p, td, S_PT_SCX);
++
++ /*
++ * If the user-supplied value of %rip is not a canonical
++ * address, then some CPUs will trigger a ring 0 #GP during
++ * the sysret instruction. However, the fault handler would
++ * execute with the user's %gs and %rsp in ring 0 which would
++ * not be safe. Instead, preemptively kill the thread with a
++ * SIGBUS.
++ */
++ if (td-td_frame-tf_rip = VM_MAXUSER_ADDRESS) {
++ ksiginfo_init_trap(ksi);
++ ksi.ksi_signo = SIGBUS;
++ ksi.ksi_code = BUS_OBJERR;
++ ksi.ksi_trapno = T_PROTFLT;
++ ksi.ksi_addr = (void *)td-td_frame-tf_rip;
++ trapsignal(td, ksi);
++ }
+ }
only in patch2:
unchanged:
--- kfreebsd-8-8.1+dfsg.orig/debian/patches/EN-12_02.ipv6refcount.patch
+++ kfreebsd-8-8.1+dfsg/debian/patches/EN-12_02.ipv6refcount.patch
@@ -0,0 +1,134 @@
+Description:
+ Fix reference count errors in IPv6 code. [EN-12:02]
+Origin: vendor, http://security.freebsd.org/patches/EN-12:02/ipv6refcount.patch
+Bug: http://security.freebsd.org/advisories/FreeBSD-EN-12:02.ipv6refcount.asc
+Applied-Upstream: http://svnweb.freebsd.org/base?view=revisionrevision=236953
+
+Index: kfreebsd-8-8.1+dfsg/sys/netinet6/in6.c
+===
+--- kfreebsd-8-8.1+dfsg.orig/sys/netinet6/in6.c2012-06-16
19:00:59.0 +0100
kfreebsd-8-8.1+dfsg/sys/netinet6/in6.c 2012-06-16 19:03:42.829835350
+0100
+@@ -1370,6 +1370,8 @@
+ }
+
+ cleanup:
++ if (ifa0 != NULL)
++ ifa_free(ifa0);
+
+ plen = in6_mask2len(ia-ia_prefixmask.sin6_addr, NULL); /* XXX */
+ if ((ia-ia_flags IFA_ROUTE) plen == 128) {
+@@ -1394,8 +1396,6 @@
+ return;
+ ia-ia_flags = ~IFA_ROUTE;
+ }
+- if (ifa0 != NULL)
+- ifa_free(ifa0);
+
+ in6_unlink_ifa(ia, ifp);
+ }
+@@ -1549,14 +1549,19 @@
+ hostid = IFA_IN6(ifa);
+
+ /* prefixlen must be = 64. */
+- if (64 iflr-prefixlen)
++ if (64 iflr-prefixlen) {
++ if (ifa != NULL)
++ ifa_free(ifa);
+ return EINVAL;
++ }
+ prefixlen = iflr-prefixlen;
+
+ /* hostid part must be zero. */
+ sin6 = (struct sockaddr_in6 *)iflr-addr;
+ if (sin6-sin6_addr.s6_addr32[2] != 0 ||
+
Bug#680375: trousers: fails to remove: prerm called with unknown argument `remove'
Package: trousers Version: 0.3.9-2 Severity: serious User: debian...@lists.debian.org Usertags: piuparts Hi, during a test with piuparts I noticed your package fails to remove. From the attached log (scroll to the bottom...): Removing trousers ... prerm called with unknown argument `remove' dpkg: error processing trousers (--remove): subprocess installed pre-removal script returned error exit status 1 invoke-rc.d: policy-rc.d denied execution of start. cheers, Andreas trousers_0.3.9-2.log.gz Description: GNU Zip compressed data
Bug#676815: mumble-server-web: Must depend on libapache2-mod-php5
Just don't do that. You should not depend directly on apache, but on php5 package. Also a dependency on apache2 is wrong. There are plenty of other webservers out there, which can be used instead of apache2. Just depend on something like: libapache2-mod-php5 | php5 O. -- Ondřej Surý ond...@sury.org -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#668065: Remove drupal6 in favour of drupal7?
Il giorno 04/lug/2012, alle ore 19:36, Al Nikolov ha scritto: В сообщении от Среда 04 июля 2012 17:43:17 автор Moritz Muehlenhoff написал: Al, what about the Drupal modules you've packaged? They will need to be updated or are they partly obsolete with Drupal 7? Well, yes, couple of them will be obsoleted, but most of, need to be upgraded. Hope, I can do this during the weekend after freeze. Actually, all of them contain references to drupal6 both in package names and directories (/usr/share/drupal6) so updating would require a NEW upload and with freeze already in place the will not be included in wheezy. Regards, L -- Luigi Gangitano -- lu...@debian.org -- gangit...@lugroma3.org GPG: 1024D/924C0C26: 12F8 9C03 89D3 DB4A 9972 C24A F19B A618 924C 0C26 GPG: 4096R/2BA97CED: 8D48 5A35 FF1E 6EB7 90E5 0F6D 0284 F20C 2BA9 7CED
Bug#669485: patch for glade-3 build failure because of missing gmodule
Hi! The attached patch is probably a better version of the previously posted patch. Just drop it in debian/patches/ and add it to debian/patches/series to fix the build failure. HTH -- Andreas Henriksson Description: add gmodule-2.0 to GTK_LIBS Fixes build failure reported in http://bugs.debian.org/669485 Author: Andreas Henriksson andr...@fatal.se --- glade-3-3.6.7.orig/configure.ac +++ glade-3-3.6.7/configure.ac @@ -116,7 +116,7 @@ GTK_DOC_CHECK(1.9) dnl dnl Check for gtk+ dnl -PKG_CHECK_MODULES(GTK, [gtk+-2.0 = 2.14.0 gthread-2.0 libxml-2.0 = 2.4.0]) +PKG_CHECK_MODULES(GTK, [gtk+-2.0 = 2.14.0 gthread-2.0 libxml-2.0 = 2.4.0 gmodule-2.0]) AC_SUBST(GTK_LIBS) AC_SUBST(GTK_CFLAGS)
Bug#680345: FTBFS: Not a CODE reference at /usr/lib/perl/5.14/DynaLoader.pm line 207.
Hi, for me, it fails with cp: cannot create regular file `/tmp/buildd/hyperestraier-1.4.13/debian/ruby-hyperestraier-doc/usr/share/doc/ruby-hyperestraier-doc/rubynativeapi/classes/Estraier/Result.src/M34.html': No such file or directory When I build it with -j4, and builds fine with -j1. This is pretty sure due to bad dependencies in debian/rules. Regards Evgeni -- Bruce Schneier can read and understand Perl programs. -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#659061: brasero: segfaults when creating a subfolder
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 package brasero tags 659061 +patch thanks Hi, I confirm that the bug is still present in 3.4.1-2 and that the patch solves it. The patch is a very clear 1-line addition and applies cleanly on top of 3.4.1. Regards, Thibaut. -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.8 (Darwin) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iQIcBAEBCAAGBQJP9YiIAAoJEJOUU0jg3ChAM9QP/0ERZj3xmELjvK+kavaJGGzc UA0NZW+i0a0llqW/a2KEprf4YsU+17gQAHe/Tk3BRaGIx+yA8RPe9SHgXSgsYO3u g63m+y2Zx2ExG8nUw2UE5fRgyfhXn8SjKHS8bekCK8qeFvZBT2PFLsgHH+c9n68N ZQWKIqcMkvocviavRT8gECYiI7cGIArzpfCtYuXe6xcjNUpZ15LPAnIQxbTEgIYA 4oqqylsHMrgkh8QvnlIMvIY5wee5B4YxTf7ZQZf7RSX6Kq6Bo/cvLH+8uTuoQH1h p1Wh55NA1EUoeUS8v436ouCo9GkVOvLR38NuMjRDwqqd4eSsAyURLGNBZAhTRQU0 f9WKD6VDOKZ2I9abA2D/hV+Jyr5Cj4V8teULy+4jAOlnBfAcimSgzo1Ywup7M+Qw 8cGOYdw7qJEQtubr6IJJzv23yDs42GK7y+LMsfEpw7cTnVO8TDa4vY4XxfG86WbV 2r8G6PtycYDuJUcSmdLCUm6/S5aZYmYnYJ10g0BuxEHRC/VSiepiRyP5IzU1I566 3+ucIt2dbXurhNp5RL0bUFwr/+BgvWVkzcSNKBvY9bGH1/ovPjO0t5DxR0NjOSmb wXVQXkxcllSTOnPUZ6/c/c3jm+216Z1rajDPJgykpKov94ZMPBGkHtIR0RlcQNvd tQCIr9HU6mcSxZrqdnAz =BYkP -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#672657: Not suitable for weezy
On Wed, Jul 04, 2012 at 09:40:51PM +0200, Julien Cristau wrote:
On Wed, Jul 4, 2012 at 10:58:30 +0200, Alessandro Ghedini wrote:
On Sat, May 12, 2012 at 07:26:17PM +0200, Enrico Tassi wrote:
Package: luajit
Version: 2.0.0~beta9+dfsg-2
Severity: grave
Tags: upstream
In accordance with the upstream, luajit will not be part of weezy, but
rather
be made available via backports.
Sooo, how is ulatencyd affected? It just lists libluajit-5.1-dev as an
alternative build dependency of liblua5.1-0-dev (to let people rebuild the
packages with luajit support without problems) but does not actually use
it. I
don't see this as a problem, am I wrong?
No, that looks fine.
Ok, closing (the correct bug) then.
Thanks
--
perl -E '$_=q;$/= @{[@_]};and s;\S+;inidehG ordnasselA;eg;say~~reverse'
signature.asc
Description: Digital signature
Bug#669485: glade-3 packaging in svn
Just a note for anyone stumbling across this bug report about the packaging (and a new upstream release prepared) being available in svn at: http://anonscm.debian.org/viewvc/pkg-gnome/attic/glade-3/ -- Andreas Henriksson -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#679819: [Python-modules-team] Bug#679819: Dropping Provides field broke depending software (python-avogadro)
On Thursday, July 05, 2012 07:59:19 AM Scott Kitterman wrote: sip4 will cause you the same problem. I'll take care of that too. Actually that's wrong. Sip4 is fine. -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#680351: [Pkg-fedora-ds-maintainers] Bug#680351: 389-ds-base: fails to install: 10 389-ds-base/setup doesn't exist
On 05.07.2012 12:23, Andreas Beckmann wrote: Package: 389-ds-base Version: 1.2.11.7-2 Severity: serious User: debian...@lists.debian.org Usertags: piuparts Hi, during a test with piuparts I noticed your package failed to install. As per definition of the release team this makes the package too buggy for a release, thus the severity. From the attached log (scroll to the bottom...): Selecting previously unselected package 389-ds-base. (Reading database ... 9713 files and directories currently installed.) Unpacking 389-ds-base (from .../389-ds-base_1.2.11.7-2_amd64.deb) ... Setting up 389-ds-base (1.2.11.7-2) ... dpkg: error processing 389-ds-base (--configure): subprocess installed post-installation script returned error exit status 10 Errors were encountered while processing: 389-ds-base Since that is not really helpful, I'm setting some more debug options: # DEBCONF_DEBUG=developer dpkg --configure --pending Setting up 389-ds-base (1.2.11.7-2) ... debconf (developer): frontend started debconf (developer): frontend running, package name is 389-ds-base debconf (developer): starting /var/lib/dpkg/info/389-ds-base.config configure debconf (developer): -- INPUT high 389-ds-base/setup debconf (developer): -- 10 389-ds-base/setup doesn't exist dpkg: error processing 389-ds-base (--configure): subprocess installed post-installation script returned error exit status 10 Errors were encountered while processing: 389-ds-base This looks like a non-existing debconf template gets used. ugh, fixed in git.. thanks. Verified with piuparts this time :) -- t -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed: cloning 679819
Processing commands for cont...@bugs.debian.org: clone 679819 -1 Bug #679819 [python-qt4] Dropping Provides field broke depending software (python-avogadro) Bug 679819 cloned as bug 680380 680380 was not blocked by any bugs. 680380 was blocking: 679821 Added blocking bug(s) of 680380: 679821 Warning: Unknown package 'src:python-avogadro' reassign -1 python-sip 4.13.3-2 Bug #680380 [python-qt4] Dropping Provides field broke depending software (python-avogadro) Bug reassigned from package 'python-qt4' to 'python-sip'. No longer marked as found in versions python-qt4/4.9.3-1. Ignoring request to alter fixed versions of bug #680380 to the same values previously set Bug #680380 [python-sip] Dropping Provides field broke depending software (python-avogadro) Marked as found in versions sip4/4.13.3-2. thanks Stopping processing here. Please contact me if you need assistance. -- 679819: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=679819 680380: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=680380 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed: Re: brasero: segfaults when creating a subfolder
Processing commands for cont...@bugs.debian.org: package brasero Limiting to bugs with field 'package' containing at least one of 'brasero' Limit currently set to 'package':'brasero' tags 659061 +patch Bug #659061 [brasero] brasero: segfaults when creating a subfolder Added tag(s) patch. thanks Stopping processing here. Please contact me if you need assistance. -- 659061: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=659061 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#680133: marked as done (ulatencyd: Needs to switch from luajit to lua)
Your message dated Thu, 5 Jul 2012 14:57:05 +0200
with message-id 20120705125705.GA22053@PC-Ale
and subject line Re: Bug#672657: Not suitable for weezy
has caused the Debian Bug report #680133,
regarding ulatencyd: Needs to switch from luajit to lua
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.)
--
680133: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=680133
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
---BeginMessage---
Package: luajit
Version: 2.0.0~beta9+dfsg-2
Severity: grave
Tags: upstream
In accordance with the upstream, luajit will not be part of weezy, but rather
be made available via backports.
-- System Information:
Debian Release: wheezy/sid
APT prefers unstable
APT policy: (500, 'unstable'), (500, 'testing'), (1, 'experimental')
Architecture: amd64 (x86_64)
Kernel: Linux 3.2.0-2-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_US.utf8, LC_CTYPE=en_US.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Versions of packages luajit depends on:
ii libc6 2.13-32
ii libgcc1 1:4.7.0-8
ii libluajit-5.1-common 2.0.0~beta9+dfsg-2
ii multiarch-support 2.13-32
luajit recommends no packages.
luajit suggests no packages.
-- no debconf information
---End Message---
---BeginMessage---
On Wed, Jul 04, 2012 at 09:40:51PM +0200, Julien Cristau wrote:
On Wed, Jul 4, 2012 at 10:58:30 +0200, Alessandro Ghedini wrote:
On Sat, May 12, 2012 at 07:26:17PM +0200, Enrico Tassi wrote:
Package: luajit
Version: 2.0.0~beta9+dfsg-2
Severity: grave
Tags: upstream
In accordance with the upstream, luajit will not be part of weezy, but
rather
be made available via backports.
Sooo, how is ulatencyd affected? It just lists libluajit-5.1-dev as an
alternative build dependency of liblua5.1-0-dev (to let people rebuild the
packages with luajit support without problems) but does not actually use
it. I
don't see this as a problem, am I wrong?
No, that looks fine.
Ok, closing (the correct bug) then.
Thanks
--
perl -E '$_=q;$/= @{[@_]};and s;\S+;inidehG ordnasselA;eg;say~~reverse'
signature.asc
Description: Digital signature
---End Message---
Bug#680134: marked as done (mudlet: Needs to switch from luajit to lua)
Your message dated Thu, 05 Jul 2012 12:47:22 + with message-id e1smlss-0007cm...@franck.debian.org and subject line Bug#680134: fixed in mudlet 2.0-rc12-3 has caused the Debian Bug report #680134, regarding mudlet: Needs to switch from luajit to lua 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.) -- 680134: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=680134 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: luajit Version: 2.0.0~beta9+dfsg-2 Severity: grave Tags: upstream In accordance with the upstream, luajit will not be part of weezy, but rather be made available via backports. -- System Information: Debian Release: wheezy/sid APT prefers unstable APT policy: (500, 'unstable'), (500, 'testing'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 3.2.0-2-amd64 (SMP w/4 CPU cores) Locale: LANG=en_US.utf8, LC_CTYPE=en_US.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages luajit depends on: ii libc6 2.13-32 ii libgcc1 1:4.7.0-8 ii libluajit-5.1-common 2.0.0~beta9+dfsg-2 ii multiarch-support 2.13-32 luajit recommends no packages. luajit suggests no packages. -- no debconf information ---End Message--- ---BeginMessage--- Source: mudlet Source-Version: 2.0-rc12-3 We believe that the bug you reported is fixed in the latest version of mudlet, which is due to be installed in the Debian FTP archive: mudlet_2.0-rc12-3.debian.tar.gz to main/m/mudlet/mudlet_2.0-rc12-3.debian.tar.gz mudlet_2.0-rc12-3.dsc to main/m/mudlet/mudlet_2.0-rc12-3.dsc mudlet_2.0-rc12-3_amd64.deb to main/m/mudlet/mudlet_2.0-rc12-3_amd64.deb 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 680...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Craig Small csm...@debian.org (supplier of updated mudlet 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: Wed, 04 Jul 2012 21:43:11 +1000 Source: mudlet Binary: mudlet Architecture: source amd64 Version: 2.0-rc12-3 Distribution: unstable Urgency: low Maintainer: Craig Small csm...@debian.org Changed-By: Craig Small csm...@debian.org Description: mudlet - Graphical MUD client with fast lua scripting support Closes: 680134 Changes: mudlet (2.0-rc12-3) unstable; urgency=low . * Removed dependency on luajit Closes: #680134 * Updated to standards version 3.9.3 * Updated to debhelper 9 Checksums-Sha1: cd7e77acd4df5c0e86c3a83567e07ce6f3eae32a 1976 mudlet_2.0-rc12-3.dsc a4c89d1fed935a6218827d00430ac9950ecc128a 8110 mudlet_2.0-rc12-3.debian.tar.gz c086c9a658a0aadd19716075e12adce24df3ba20 3724446 mudlet_2.0-rc12-3_amd64.deb Checksums-Sha256: 988561f85d101576fbaaf1a009e99370a0d67e5692600e40cd263d473c1dcbeb 1976 mudlet_2.0-rc12-3.dsc adbc55cff0cb5171f6c3110d6c60ef83ac95422c9aa591b679c3b69571c5a5df 8110 mudlet_2.0-rc12-3.debian.tar.gz ad3c0596e1ed2c62bfaef8f1d60f2a59ed1523d39769c1808b0142d816ed 3724446 mudlet_2.0-rc12-3_amd64.deb Files: b69816390a9a1f578fa870b9d0d2846b 1976 games extra mudlet_2.0-rc12-3.dsc 2e4dc967469d534fc5711139b4652734 8110 games extra mudlet_2.0-rc12-3.debian.tar.gz db99784ce3c6174e86798c074db5901b 3724446 games extra mudlet_2.0-rc12-3_amd64.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.12 (GNU/Linux) iQIcBAEBCAAGBQJP9YuLAAoJEDk4+WvfUP6luGIP/A08ML4nyt0q+h+/bMP4eAgv AshqOVYCK5GeFTSYzepeBwSddyXM6PI75r2LTm2sni3NTMFfbHdaV4wSyoO2wT2J ncdq/YUzg2wv9NrjWSuy+MoqM71zgDAOcU6dmE05F0OCOt8m6uXFY4za3tYH3t3H 16Wm8Hy+YWLu9ZrCbWx/RwprSEhcjXw73r+AbgMEvMb972O+iahuh5RFkqpJhtZA kGbdYOcInlSniYgIvwBzIeE6909iTTUGYaD7HT7xkErrd01DdUCIslCW2odSay2u IOrKzVr8J2RXkfJ+NXcAfhOE/OkrSiDsK4l8fNbcxozx9/d24Zfc453f+m07KQWC 0NNCoBXTzNTouSJ4NtudMaxxjdwtLBKgPFedtIc0SGPbBs/XLIAUJhZKicGHBjfg 2p7HN+wn4j3d/C4Ne8W336JwZ3lG/yJsvHzFIqy9XtAptWT8MyrUsIFTohQWFHkX 5ZKZ2w1z4XAJOULPvIVNrMnRw13m19CEb+fRSG8854keMoIcTqs7KFVIpqeh7qMv nnsaeAG2VDQZtkWq4E7rYnBdA+mXHreIZrJ29XpTrzYRqodVjr1Jk1GI/AjwPnbS YQRmVe79swMPTBiOtUXbAH5QVX0Jf3VCssFccysCqvjc46njX/FSn6pCfYloUe0M XL2mYWTN3wQIjAK3ZBwY =xkuE -END PGP SIGNATURE- ---End Message---
Bug#656088: gforge-web-apache2: prompting due to modified conffiles which where not modified by the user
Andreas Beckmann, 2012-07-05 13:34:52 +0200 : Hi Roland, Hi, sorry, it took me a while to answer this ... On 2012-03-20 14:24, Roland Mas wrote: I'm not sure there's a way to fix that without touching the packages in stable; Touching stable is not an option, this needs to be fixed by the package in squeeze. so, while I agree this bug is valid for the squeeze-wheezy upgrade, it should be tagged as only concerning versions up to 5.1.1-2. What do you think? How does /etc/gforge/httpd.conf get created? Is there any local customization (like a hostname) by default or is it the sam efile in all installations (until customized)? In 5.1 and 5.2 and beyond (ie. for wheezy), it's a standard conffile which will very rarely change from the shipped version. In 5.0 and older (ie. up until squeeze), it was generated from templates with variables filled in (including at the very least the hostname to be used by Apache for its virtual hosts). The list of templates itself was variable, since plugins could provide snippets of files that would be used when generating /etc/gforge/httpd.conf. If you can limit the possible files created by the package in squeeze just collect all possible md5sums of unmodified configuration files. I can't limit that a posteriori, I'm afraid. Even for users who installed the very minimal set of packages and didn't customize anything, there's still at least the variability of the hostname. Roland. -- Roland Mas Le weblog entièrement nu -- http://roland.entierement.nu/ Le photoblog entièrement net -- http://roland.entierement.net/ -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#629307: dasher dependency on dasher-data fixed in svn
Just a note for anyone stumbling across this bug report. It seems the package is available in svn at: http://anonscm.debian.org/viewvc/pkg-gnome/attic/dasher/ Where it has been fixed in previously suggested way... -- Andreas Henriksson -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed: notfound 680380 in 4.13.3
Processing commands for cont...@bugs.debian.org: notfound 680380 4.13.3 Bug #680380 [python-sip] Dropping Provides field broke depending software (python-avogadro) There is no source info for the package 'python-sip' at version '4.13.3' with architecture '' Unable to make a source version for version '4.13.3' No longer marked as found in versions sip4/4.13.3-2. thanks Stopping processing here. Please contact me if you need assistance. -- 680380: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=680380 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed: tagging 668740, user debian...@lists.debian.org, usertagging 676694, usertagging 677337 ...
Processing commands for cont...@bugs.debian.org:
tags 668740 - wontfix + help
Bug #668740 [dsc-statistics-collector,dsc-statistics-presenter]
dsc-statistics-{collector, presenter}: creates system user in /home
Removed tag(s) wontfix.
Bug #668740 [dsc-statistics-collector,dsc-statistics-presenter]
dsc-statistics-{collector, presenter}: creates system user in /home
Added tag(s) help.
user debian...@lists.debian.org
Setting user to debian...@lists.debian.org (was deb...@abeckmann.de).
usertags 676694 - piuparts
Bug#676694: piuparts: [install-upgrade] should first install from distribution
Usertags were: piuparts.
Usertags are now: .
usertags 677337 - piuparts
Bug#677337: piuparts: [install-upgrade-purge] should call apt-get purge, not
apt-get remove and dpkg --purge
Usertags were: piuparts.
Usertags are now: .
usertags 661312 - piuparts
Bug#661312: document+test tempdir for nodev/nosuid and error out early
Usertags were: piuparts.
Usertags are now: .
tags 661397 - moreinfo
Bug #661397 [iscsitarget] iscsitarget: prompting due to modified conffiles
which where not modified by the user
Removed tag(s) moreinfo.
tags 656088 - moreinfo
Bug #656088 [gforge-web-apache2] gforge-web-apache2: prompting due to modified
conffiles which where not modified by the user
Removed tag(s) moreinfo.
thanks
Stopping processing here.
Please contact me if you need assistance.
--
656088: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=656088
661397: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=661397
668740: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=668740
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#680380: marked as done (Dropping Provides field broke depending software (python-avogadro))
Your message dated Thu, 05 Jul 2012 09:20:41 -0400 with message-id 1437130.VptMR7clzB@scott-latitude-e6320 and subject line Bug was opened in error has caused the Debian Bug report #680380, regarding Dropping Provides field broke depending software (python-avogadro) 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.) -- 680380: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=680380 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: python-qt4 Version: 4.9.3-1 Severity: serious -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 The last upload of python-qt4 removed the Provides field. Unfortunately this breaks the installation of avogadro, which depends on python2.7-qt4. Why has this field been removed and how should this be handled now? How shall this be handlded in future removals of Provides fields in python* packages? Regards, Daniel - -- System Information: Debian Release: wheezy/sid APT prefers unstable APT policy: (850, 'unstable'), (700, 'testing'), (560, 'stable'), (110, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 3.2.0-3-amd64 (SMP w/2 CPU cores) Locale: LANG=de_DE.utf8, LC_CTYPE=de_DE.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash Versions of packages python-qt4 depends on: ii libc6 2.13-34 ii libgcc1 1:4.7.1-2 ii libpython2.7 2.7.3-1 ii libqt4-dbus 4:4.8.2-1 ii libqt4-declarative4:4.8.2-1 ii libqt4-designer 4:4.8.2-1 ii libqt4-help 4:4.8.2-1 ii libqt4-network4:4.8.2-1 ii libqt4-script 4:4.8.2-1 ii libqt4-scripttools4:4.8.2-1 ii libqt4-svg4:4.8.2-1 ii libqt4-test 4:4.8.2-1 ii libqt4-xml4:4.8.2-1 ii libqt4-xmlpatterns4:4.8.2-1 ii libqtassistantclient4 4.6.3-4 ii libqtcore44:4.8.2-1 ii libqtgui4 4:4.8.2-1 ii libqtwebkit4 2.2.1-4+b1 ii libstdc++64.7.1-2 ii python2.7.3-1 ii python-sip [sip-api-8.1] 4.13.3-2 ii python2.6 2.6.8-0.2 ii python2.7 2.7.3-1 python-qt4 recommends no packages. Versions of packages python-qt4 suggests: pn python-qt4-dbg none - -- no debconf information -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.12 (GNU/Linux) iEYEARECAAYFAk/wpi0ACgkQm0bx+wiPa4w0lgCeK89qTio3lje6udcBgmvWYEAq a+UAnRz9J4yzCGtayF8uYhNRbXtLgHw6 =pWF9 -END PGP SIGNATURE- ---End Message--- ---BeginMessage--- EOM ---End Message---
Bug#617931: gmsh: multiple licensing issues
Dear All, I don't understand if this bug is solved: I see that now gmsh depends on the OpenCASCADE Community Edition. Regards, Gabriele --- Nutzen Sie freenet Mail optimal angepasst für Ihr iPhone, Android oder Nokia Handy auch von unterwegs. Alle Infos und Download unter http://mail.freenet.de/mobile-email/index.html
Bug#656088: gforge-web-apache2: prompting due to modified conffiles which where not modified by the user
On 2012-07-05 15:15, Roland Mas wrote: I can't limit that a posteriori, I'm afraid. Even for users who installed the very minimal set of packages and didn't customize anything, there's still at least the variability of the hostname. Well, you can extract the hostname and check, whether it was modified. and you can remove the line with the hostname before running md5sum or replace it with some placeholder first: sed -e s/^HoStNaMe: $the_local_hostname/HoStNaMe: GENERIC.DEFAU.LT/ /etc/gforge/httpd.conf| md5sum Or can you just regenerate the httpd.conf in the preinst script on upgrades from pre-conffile and place it in a temporary location and compare that to the version in /etc? Andreas -- 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
Ferenc Wagner wf...@niif.hu writes: Ralf Treinen trei...@free.fr writes: Here is a list of files that are known to be shared by both packages /usr/bin/wbemcli /usr/share/man/man1/wbemcli.1.gz Hi, While in my opinion sblim-wbemcli ships the more genuine wbemcli binary (leading the search results, packaged similarly by other distros), python-pywbem certainly got there first, so I'm willing to rename the binary in sblim-wbemcli unless the python-pywbem maintainers agree to make the necessary change themselves. Btw. I even tested python-pywbem before packaging sblim-wbemcli, and the former didn't work for my purposes even after some patching due to a CIM version mismatch, if I'm not mistaken. Unfortunately, I forgot about the name clash. Hi Bernd, I was more than surprised to run into you twice in such a short time (freeipmi packaging and this bug)! How should we sort out this issue? Do you want to keep your wbemcli executable? -- Regards, Feri. -- 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 :) I was more than surprised to run into you twice in such a short time (freeipmi packaging and this bug)! you might even run into me again if you want to become a DD :D How should we sort out this issue? Do you want to keep your wbemcli executable? I would say we compare both and let the one which is more useful keep the name. Interesting would be to know if the current one is in use already. A popcon of 90 is not that high. So from a current user's POV renaming the current wbemcli is probably a bad idea... I did not yet have the time to look into the issue, I have to admit. Could you summarize the advantages/disadvantages of sblim-wbemcli over the python version? Is there a common interface? 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#666468: xorg-server: major text display problems in several apps
Hello, I encountered the same problem with debian wheezy, I solved it by installing the package xserver-xorg-video-nouveau_1.0.1-1 of debian sid. Please made a request to use this version in debian wheezy. Thanks for your work in Debian. Best regards, HacKurx www.hackurx.info -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#679761: olsrd: FTBFS[kfreebsd]: fatal error: linux/types.h: No such file or directory
Hi, looking at the debdiff between 0.6.3-2 and 0.6.3-3, it looks the following change broke it: diff -Nru olsrd-0.6.3/debian/rules olsrd-0.6.3/debian/rules --- olsrd-0.6.3/debian/rules2012-02-19 16:07:42.0 +0100 +++ olsrd-0.6.3/debian/rules2012-06-28 00:26:51.0 +0200 @@ -7,39 +7,38 @@ dh $@ override_dh_auto_build: - $(MAKE) - $(MAKE) libs + $(MAKE) OS=linux DEBUG=0 build_all $(MAKE) -C gui/linux-gtk $(MAKE) -C src/olsr_switch obviously, kfreebsd isn't linux and thus fails. Not tagging patch or anything, as I didnt try to rebuild w/o OS=linux. Enjoy Evgeni -- Bruce Schneier can read and understand Perl programs. -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#680238: Please drop libggi support
On 05/07/12 11:15, Moritz Muehlenhoff wrote: I'll take care of the unblock request. FTR, I've unblocked it. -- Mehdi -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#659061: brasero: segfaults when creating a subfolder
Le jeudi 05 juillet 2012 à 14:28 +0200, Thibaut Paumard a écrit : I confirm that the bug is still present in 3.4.1-2 and that the patch solves it. The patch is a very clear 1-line addition and applies cleanly on top of 3.4.1. Can you forward it upstream on bugzilla.gnome.org? Thanks, -- .''`. Josselin Mouette : :' : `. `' `- -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#679704: live-tools: fails to upgrade from wheezy: ln: failed to create symbolic link `/usr/bin/uptime': File exists
tags 679704 + patch
thanks
Hi,
this happens, because the preinstal uncoditionally tries to create the
symlink, w/o checking that it already is a symlink the live-uptime.
Easy reproducable via apt-get install --reinstall live-tools, no need
for an upgrade :)
Attached is a patch which moves the creation of the symlink from the
preinst (and removing of it in postrm) to the actual package (via
live-tools.links).
Upgrading 3.0.2-1 → 3.0.2-1.1 and 3.0.2-1.1 → 3.0.2-1.1 is tested,
everything else is not.
Regards
Evgeni
--
Bruce Schneier can read and understand Perl programs.
From cf828f00b1c02e873e02ce3446d948a6d747bc6c Mon Sep 17 00:00:00 2001
From: Evgeni Golov evg...@debian.org
Date: Thu, 5 Jul 2012 16:17:06 +0200
Subject: [PATCH] =?UTF-8?q?install=20the=20uptime=20=E2=86=92=20live-uptime=20?=
=?UTF-8?q?link=20in=20the=20package,=20not=20in=20preinst?=
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit
---
debian/live-tools.links |2 ++
debian/live-tools.postrm |2 --
debian/live-tools.preinst |2 --
3 files changed, 2 insertions(+), 4 deletions(-)
diff --git a/debian/live-tools.links b/debian/live-tools.links
index 5a18980..76d2d47 100644
--- a/debian/live-tools.links
+++ b/debian/live-tools.links
@@ -5,3 +5,5 @@
/usr/share/man/de/man7/live-tools.7.gz /usr/share/man/de/man1/live-system.1.gz
/usr/share/man/de/man7/live-tools.7.gz /usr/share/man/de/man1/live-toram.1.gz
/usr/share/man/de/man7/live-tools.7.gz /usr/share/man/de/man1/live-uptime.1.gz
+
+/usr/bin/live-uptime /usr/bin/uptime
diff --git a/debian/live-tools.postrm b/debian/live-tools.postrm
index 6c06daa..6618670 100644
--- a/debian/live-tools.postrm
+++ b/debian/live-tools.postrm
@@ -4,8 +4,6 @@ set -e
case ${1} in
remove)
- rm -f /usr/bin/uptime
-
dpkg-divert --package live-tools --quiet --remove --rename --divert /usr/bin/uptime.procps /usr/bin/uptime
;;
diff --git a/debian/live-tools.preinst b/debian/live-tools.preinst
index 8b02200..b505fce 100644
--- a/debian/live-tools.preinst
+++ b/debian/live-tools.preinst
@@ -5,8 +5,6 @@ set -e
case ${1} in
install|upgrade)
dpkg-divert --package live-tools --quiet --add --rename --divert /usr/bin/uptime.procps /usr/bin/uptime
-
- ln -s /usr/bin/live-uptime /usr/bin/uptime
;;
abort-upgrade)
--
1.7.10
Processed: Re: live-tools: fails to upgrade from wheezy: ln: failed to create symbolic link `/usr/bin/uptime': File exists
Processing commands for cont...@bugs.debian.org: tags 679704 + patch Bug #679704 [live-tools] live-tools: fails to upgrade from wheezy: ln: failed to create symbolic link `/usr/bin/uptime': File exists Added tag(s) patch. thanks Stopping processing here. Please contact me if you need assistance. -- 679704: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=679704 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#679665: jquery: build-deps not satisfiable in wheezy
On 30/06/12 17:45, Julien Cristau wrote: jquery build-depends on node-uglify, which is not in testing. This needs to be fixed before release somehow. A solution might be to use yui-compressor as done prior to version 1.7.2+debian-1. yui-compressor seems to be present in testing and doesn't have any (severe) bugs currently. Regards, -- Mehdi Dogguy مهدي الدڤي http://dogguy.org/ -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#680317: marked as done (Uninstallable due dependency to unexisting package: i32-libs-gtk-i386)
Your message dated Thu, 05 Jul 2012 14:47:40 + with message-id e1smnli-0004mt...@franck.debian.org and subject line Bug#680317: fixed in ia32-libs-gtk 20120705 has caused the Debian Bug report #680317, regarding Uninstallable due dependency to unexisting package: i32-libs-gtk-i386 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.) -- 680317: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=680317 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: ia32-libs-gtk Version: 20120616 Severity: serious The package ia32-libs-gtk is uninstallable due to dependency on i32-libs- gtk-i386 (missing 'a' in ia32) However, even with the correct spelling, I can't find the ia32-libs-gtk-i386 package anywhere. -- System Information: Debian Release: wheezy/sid APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.2.0-3-amd64 (SMP w/8 CPU cores) Locale: LANG=it_IT.UTF-8, LC_CTYPE=it_IT.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages ia32-libs-gtk depends on: ii ia32-libs 20120102 ii lib32asound2 1.0.25-3 ii lib32gcc1 1:4.7.1-3 ii lib32stdc++6 4.7.1-3 ii lib32z1 1:1.2.7.dfsg-13 ii libc6-i3862.13-34 ia32-libs-gtk recommends no packages. ia32-libs-gtk suggests no packages. -- no debconf information -- - |Marco Nenciarini| Debian/GNU Linux Developer - Plug Member | | mnen...@prato.linux.it | http://www.prato.linux.it/~mnencia | - Key fingerprint = FED9 69C7 9E67 21F5 7D95 5270 6864 730D F095 E5E4 ---End Message--- ---BeginMessage--- Source: ia32-libs-gtk Source-Version: 20120705 We believe that the bug you reported is fixed in the latest version of ia32-libs-gtk, which is due to be installed in the Debian FTP archive: ia32-libs-gtk_20120705.dsc to main/i/ia32-libs-gtk/ia32-libs-gtk_20120705.dsc ia32-libs-gtk_20120705.tar.gz to main/i/ia32-libs-gtk/ia32-libs-gtk_20120705.tar.gz ia32-libs-gtk_20120705_amd64.deb to main/i/ia32-libs-gtk/ia32-libs-gtk_20120705_amd64.deb 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 680...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Thijs Kinkhorst th...@debian.org (supplier of updated ia32-libs-gtk 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: Thu, 05 Jul 2012 13:39:23 + Source: ia32-libs-gtk Binary: ia32-libs-gtk ia32-libs-gtk-i386 Architecture: source amd64 Version: 20120705 Distribution: unstable Urgency: low Maintainer: Debian ia32-libs Team pkg-ia32-libs-maintain...@lists.alioth.debian.org Changed-By: Thijs Kinkhorst th...@debian.org Description: ia32-libs-gtk - Transitional package to migrate ia32-libs-gtk to multiarch ia32-libs-gtk-i386 - Transitional package to migrate ia32-libs-gtk to multiarch Closes: 680317 Changes: ia32-libs-gtk (20120705) unstable; urgency=low . * Correct typo in ia32-libs-gtk-i386 dependency (closes: #680317). Checksums-Sha1: fdcf436caa027d0214c7b4e83cce127a79e76836 1482 ia32-libs-gtk_20120705.dsc 7305a4bdbedf95bf977988af4252010b2122bb9c 19490 ia32-libs-gtk_20120705.tar.gz ee604365ee71cdb445c33f7cac263ce684ad23c9 19480 ia32-libs-gtk_20120705_amd64.deb Checksums-Sha256: e5af173dabe51c4cc14e5936a18a8761081f53e1952dd4dcfac9cbfd0c70a64b 1482 ia32-libs-gtk_20120705.dsc d5ed0dbc1fd9dc3710b1824b39282c2929fd84c2a813835eaa60fb468fc8ae69 19490 ia32-libs-gtk_20120705.tar.gz f57ca6a9e0cff8d48bb8665bf53013533cb5aa7fa17143531915183ba1e6a07a 19480 ia32-libs-gtk_20120705_amd64.deb Files: 4a2f76ccf2d5fa0e901b5bbd8a45887c 1482 oldlibs extra ia32-libs-gtk_20120705.dsc f744aee5cf2cb73b0a96e3cea33248d8 19490 oldlibs extra ia32-libs-gtk_20120705.tar.gz 87c3a8fca230c726cc3f5ffabc95ffd7 19480 oldlibs extra ia32-libs-gtk_20120705_amd64.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.12 (GNU/Linux) iQEcBAEBAgAGBQJP9Zq5AAoJEFb2GnlAHawExDAH/iZkSG/yeJOot0CFWaRfvbUv qPVSzcAn8PJtiK7rGeFserKEAjAaaqsmy8H2/rzO7DxjJBvM9pFP+vxkC2EHr3aB QmdI+MjyDrMYjWVMp98YzlNb
Bug#679704: live-tools: fails to upgrade from wheezy: ln: failed to create symbolic link `/usr/bin/uptime': File exists
tag 679704 pending thanks On 07/05/2012 04:29 PM, Evgeni Golov wrote: Attached is a patch which moves the creation of the symlink from the preinst (and removing of it in postrm) to the actual package (via live-tools.links). i'll upload something similar to this in some minutes. -- Address:Daniel Baumann, Donnerbuehlweg 3, CH-3012 Bern Email: daniel.baum...@progress-technologies.net Internet: http://people.progress-technologies.net/~daniel.baumann/ -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed: Re: Bug#679704: live-tools: fails to upgrade from wheezy: ln: failed to create symbolic link `/usr/bin/uptime': File exists
Processing commands for cont...@bugs.debian.org: tag 679704 pending Bug #679704 [live-tools] live-tools: fails to upgrade from wheezy: ln: failed to create symbolic link `/usr/bin/uptime': File exists Added tag(s) pending. thanks Stopping processing here. Please contact me if you need assistance. -- 679704: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=679704 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#679704: live-tools: fails to upgrade from wheezy: ln: failed to create symbolic link `/usr/bin/uptime': File exists
On 07/05/2012 04:56 PM, Daniel Baumann wrote: i'll upload something similar to this in some minutes. s/something similar to this/exactely that/ thanks ;) -- Address:Daniel Baumann, Donnerbuehlweg 3, CH-3012 Bern Email: daniel.baum...@progress-technologies.net Internet: http://people.progress-technologies.net/~daniel.baumann/ -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed: tagging 679672
Processing commands for cont...@bugs.debian.org: tags 679672 + pending Bug #679672 [ifupdown] ifupdown: ifup doesn't recognize aliases IPs for vlan in form ethX.Y:A Added tag(s) pending. thanks Stopping processing here. Please contact me if you need assistance. -- 679672: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=679672 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#679704: marked as done (live-tools: fails to upgrade from wheezy: ln: failed to create symbolic link `/usr/bin/uptime': File exists)
Your message dated Thu, 05 Jul 2012 15:17:38 + with message-id e1smnoi-0006pu...@franck.debian.org and subject line Bug#679704: fixed in live-tools 3.0.3-1 has caused the Debian Bug report #679704, regarding live-tools: fails to upgrade from wheezy: ln: failed to create symbolic link `/usr/bin/uptime': File exists 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.) -- 679704: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=679704 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: live-tools Version: 3.0.2-1 Severity: serious User: debian...@lists.debian.org Usertags: piuparts Hi, during a test with piuparts I noticed your package fails to upgrade from 'wheezy'. It installed fine in 'wheezy', then the upgrade to 'sid' fails. From the attached log (scroll to the bottom...): Preparing to replace live-tools 3.0.1-1 (using .../live-tools_3.0.2-1_all.deb) ... ln: failed to create symbolic link `/usr/bin/uptime': File exists dpkg: error processing /var/cache/apt/archives/live-tools_3.0.2-1_all.deb (--unpack): subprocess new pre-installation script returned error exit status 1 Errors were encountered while processing: /var/cache/apt/archives/live-tools_3.0.2-1_all.deb There wasn't any version of linux-containers installed in the chroot. cheers, Andreas live-tools_3.0.2-1.log.gz Description: GNU Zip compressed data ---End Message--- ---BeginMessage--- Source: live-tools Source-Version: 3.0.3-1 We believe that the bug you reported is fixed in the latest version of live-tools, which is due to be installed in the Debian FTP archive: live-tools_3.0.3-1.debian.tar.xz to main/l/live-tools/live-tools_3.0.3-1.debian.tar.xz live-tools_3.0.3-1.dsc to main/l/live-tools/live-tools_3.0.3-1.dsc live-tools_3.0.3-1_all.deb to main/l/live-tools/live-tools_3.0.3-1_all.deb live-tools_3.0.3.orig.tar.xz to main/l/live-tools/live-tools_3.0.3.orig.tar.xz 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. Daniel Baumann dan...@debian.org (supplier of updated live-tools 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: Thu, 05 Jul 2012 17:05:30 +0200 Source: live-tools Binary: live-tools Architecture: source all Version: 3.0.3-1 Distribution: unstable Urgency: low Maintainer: Debian Live Project debian-l...@lists.debian.org Changed-By: Daniel Baumann dan...@debian.org Description: live-tools - Debian Live - System Support Scripts Closes: 679704 Changes: live-tools (3.0.3-1) unstable; urgency=low . [ Evgeni Golov ] * Installing the uptime to live-uptime link in the package, not in preinst (Closes: #679704). Checksums-Sha1: 59f51503016e50961d7e47f7347046bed03ab0ec 1259 live-tools_3.0.3-1.dsc 0a51d0ca86b0a814dd2ba4035b443ebdc30f8eb5 16604 live-tools_3.0.3.orig.tar.xz 4a15f8806884b4d2ef69758d37b9d2b7c1600e86 3300 live-tools_3.0.3-1.debian.tar.xz f17681aa8b887b9598c1b97015453813c3ca24a8 7622 live-tools_3.0.3-1_all.deb Checksums-Sha256: 57b2f19d82f50454eb3415b81cd9c3db35a4ae8ae20c4ddf33e28c854f2b7b9f 1259 live-tools_3.0.3-1.dsc 856a6be90a443d0ba4ab7de6438e6c7edf9ecd86263c3728049164dcb7babe24 16604 live-tools_3.0.3.orig.tar.xz d8c2f9cbb32a92a8d117016faa48808e738515d934cb1070d57f82e912474b4b 3300 live-tools_3.0.3-1.debian.tar.xz a1248ed3c256dbe0d18e6b0a57cc19633714ee8330857ed65d08673b67dc5411 7622 live-tools_3.0.3-1_all.deb Files: cdee45ff0a779b182652f75a8c2b5d37 1259 misc optional live-tools_3.0.3-1.dsc fd63c3d4575e703b29fcf59dcc941856 16604 misc optional live-tools_3.0.3.orig.tar.xz 0704a60444c6392e40b66f8022c35530 3300 misc optional live-tools_3.0.3-1.debian.tar.xz 419bacc2683df358651c6d8029d10e78 7622 misc optional live-tools_3.0.3-1_all.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.10 (GNU/Linux) iEYEARECAAYFAk/1rkcACgkQ+C5cwEsrK55CJwCfTHUI1NlOAxYXRzFj4JszcXPP KqcAoMaHWSKSSykvBiMDuYF+Pol+j5Jt =MwmA -END PGP SIGNATURE- ---End Message---
Bug#680118: marked as done (spip: PHP injection fixed in new 2.1.16 upstream release)
Your message dated Thu, 05 Jul 2012 15:17:44 + with message-id e1smnoo-0006qc...@franck.debian.org and subject line Bug#680118: fixed in spip 2.1.16-1 has caused the Debian Bug report #680118, regarding spip: PHP injection fixed in new 2.1.16 upstream release 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.) -- 680118: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=680118 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: spip Version: 2.1.1-3squeeze3 Severity: grave Tags: security upstream Upstream just released a new version, fixing a PHP injection vulnerability. The stable security update is ready [rt.debian.org #3837] and I'll upload the package as soon as possible in: http://people.debian.org/~taffit/spip/spip_2.1.1-3squeeze4.dsc http://people.debian.org/~taffit/spip/spip_2.1.1-3squeeze4_all.deb -- System Information: Debian Release: 6.0.5 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'proposed-updates'), (500, 'stable'), (150, 'testing'), (120, 'unstable'), (110, 'experimental') Architecture: i386 (i686) Kernel: Linux 2.6.32-5-686 (SMP w/1 CPU core) 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 spip depends on: ii apache2-mpm-prefork [h 2.2.16-6+squeeze7 Apache HTTP Server - traditional n ii debconf [debconf-2.0] 1.5.36.1 Debian configuration management sy ii libjs-jquery 1.4.2-2 JavaScript library for dynamic web ii php-html-safe 0.10.0-1 strip down all potentially dangero ii php5 5.3.3-7+squeeze13 server-side, HTML-embedded scripti ii php5-mysql 5.3.3-7+squeeze13 MySQL module for php5 Versions of packages spip recommends: ii imagemagick 8:6.6.0.4-3+squeeze3 image manipulation programs ii mysql-server5.1.63-0+squeeze1MySQL database server (metapackage ii mysql-server-5.1 [m 5.1.63-0+squeeze1MySQL database server binaries and spip suggests no packages. -- Configuration Files: /etc/spip/apache.conf changed [not included] -- debconf information excluded ---End Message--- ---BeginMessage--- Source: spip Source-Version: 2.1.16-1 We believe that the bug you reported is fixed in the latest version of spip, which is due to be installed in the Debian FTP archive: spip_2.1.16-1.debian.tar.gz to main/s/spip/spip_2.1.16-1.debian.tar.gz spip_2.1.16-1.dsc to main/s/spip/spip_2.1.16-1.dsc spip_2.1.16-1_all.deb to main/s/spip/spip_2.1.16-1_all.deb spip_2.1.16.orig.tar.gz to main/s/spip/spip_2.1.16.orig.tar.gz 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 680...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. David Prévot taf...@debian.org (supplier of updated spip 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: Wed, 04 Jul 2012 08:42:01 -0400 Source: spip Binary: spip Architecture: source all Version: 2.1.16-1 Distribution: unstable Urgency: high Maintainer: SPIP packaging team spip-maintain...@lists.alioth.debian.org Changed-By: David Prévot taf...@debian.org Description: spip - website engine for publishing Closes: 680118 Changes: spip (2.1.16-1) unstable; urgency=high . * New upstream version: - fixes PHP injection (Closes: #680118); - fixes growing session directory; - fixes PHP 5.4 compatibility. * Update security screen file to 1.1.3. Checksums-Sha1: c104d62df8cd26ac8205de955b6f2654620c66ef 1862 spip_2.1.16-1.dsc f93820b8f9058ee39344d1dfe5e24c4e19e85ce4 3971925 spip_2.1.16.orig.tar.gz e30ce0634f83a73705b52d27b432eaa7b2807d71 62524 spip_2.1.16-1.debian.tar.gz 235baf0bfedf865806ff3188818fef3c67c6b8f5 3856668 spip_2.1.16-1_all.deb Checksums-Sha256: 703be91e3c5a74100417450f2db43af3f85fc23b315cd418390090eb1700a29b 1862 spip_2.1.16-1.dsc e86e259ffa1b3ece5a842028d2cb7116ad54d06df94cc1a07ee7c5e84f356c85 3971925 spip_2.1.16.orig.tar.gz eefc135772db59d5db49fbe64eab3bcd18ffeab5ac9d725a54e7afac658231a1 62524 spip_2.1.16-1.debian.tar.gz 5898e38610c216c95d34dbf4b5901e6cef4405a101c1905d7ffdedad91a1395b 3856668 spip_2.1.16-1_all.deb Files: 7e122bd8848539ab48ec4e457c8f1d7b 1862 web extra
Bug#680232: marked as done (fuse: FTBFS[kfreebsd]: chmod: cannot access `debian/fuse/bin/fusermount': No such file or directory)
Your message dated Thu, 05 Jul 2012 15:17:23 + with message-id e1smno3-0006on...@franck.debian.org and subject line Bug#680232: fixed in fuse 2.9.0-5 has caused the Debian Bug report #680232, regarding fuse: FTBFS[kfreebsd]: chmod: cannot access `debian/fuse/bin/fusermount': No such file or directory 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.) -- 680232: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=680232 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: src:fuse Version: 2.9.0-4 Severity: serious Tags: sid wheezy User: debian-...@lists.debian.org Usertags: kfreebsd X-Debbugs-Cc: debian-...@lists.debian.org Justification: fails to build from source (but built successfully in the past) Hi! Your package failed to build on the kfreebsd-* buildds: dh_fixperms chmod 0755 debian/fuse/bin/fusermount chmod: cannot access `debian/fuse/bin/fusermount': No such file or directory make[1]: *** [override_dh_fixperms] Error 1 Full build log at https://buildd.debian.org/status/fetch.php?pkg=fusearch=kfreebsd-amd64ver=2.9.0-4stamp=1341073533 Regards Christoph If you have further questions please mail debian-...@lists.debian.org ---End Message--- ---BeginMessage--- Source: fuse Source-Version: 2.9.0-5 We believe that the bug you reported is fixed in the latest version of fuse, which is due to be installed in the Debian FTP archive: fuse-dbg_2.9.0-5_i386.deb to main/f/fuse/fuse-dbg_2.9.0-5_i386.deb fuse-udeb_2.9.0-5_i386.udeb to main/f/fuse/fuse-udeb_2.9.0-5_i386.udeb fuse-utils_2.9.0-5_all.deb to main/f/fuse/fuse-utils_2.9.0-5_all.deb fuse_2.9.0-5.debian.tar.xz to main/f/fuse/fuse_2.9.0-5.debian.tar.xz fuse_2.9.0-5.dsc to main/f/fuse/fuse_2.9.0-5.dsc fuse_2.9.0-5_i386.deb to main/f/fuse/fuse_2.9.0-5_i386.deb libfuse-dev_2.9.0-5_i386.deb to main/f/fuse/libfuse-dev_2.9.0-5_i386.deb libfuse2-udeb_2.9.0-5_i386.udeb to main/f/fuse/libfuse2-udeb_2.9.0-5_i386.udeb libfuse2_2.9.0-5_i386.deb to main/f/fuse/libfuse2_2.9.0-5_i386.deb 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 680...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Daniel Baumann daniel.baum...@progress-technologies.net (supplier of updated fuse 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: Thu, 05 Jul 2012 16:54:23 +0200 Source: fuse Binary: fuse fuse-dbg fuse-utils libfuse2 libfuse-dev fuse-udeb libfuse2-udeb Architecture: source i386 all Version: 2.9.0-5 Distribution: unstable Urgency: low Maintainer: Daniel Baumann daniel.baum...@progress-technologies.net Changed-By: Daniel Baumann daniel.baum...@progress-technologies.net Description: fuse - Filesystem in Userspace fuse-dbg - Filesystem in Userspace fuse-udeb - Filesystem in Userspace (udeb) fuse-utils - Filesystem in Userspace (transitional package) libfuse-dev - Filesystem in Userspace (development) libfuse2 - Filesystem in Userspace (library) libfuse2-udeb - Filesystem in Userspace (library) (udeb) Closes: 680232 Changes: fuse (2.9.0-5) unstable; urgency=low . * Adjusting permission on fusermount conditionally upon build architecture (Closes: #680232). Checksums-Sha1: 4e32d1a4163eacbc71b009e5d596ab857b1653eb 1375 fuse_2.9.0-5.dsc 84206111a832af6175b0418d8d8ad963d2c50389 14084 fuse_2.9.0-5.debian.tar.xz d480acb12b795b8a252a89b3c7de6c20fd495dce 67700 fuse_2.9.0-5_i386.deb 283a8fbac83720f5d9c6c5246181588097f28a85 299040 fuse-dbg_2.9.0-5_i386.deb c58d42a6a29018bad06d62373679537afe1a768e 43944 fuse-utils_2.9.0-5_all.deb a9fd62b04843f68b7b8c83a7cdc7d820b9f6fcc4 132826 libfuse2_2.9.0-5_i386.deb 6b63a61fa905239bc14051dd78aafd972062a214 149110 libfuse-dev_2.9.0-5_i386.deb 0562d343261908c142a247ae9e9fca81887d79e6 14064 fuse-udeb_2.9.0-5_i386.udeb c451a1e099962b58354c99f07c19bb586e9fc21a 69104 libfuse2-udeb_2.9.0-5_i386.udeb Checksums-Sha256: 2e10af8087e2b3e25ab8b2032c41a38285eac391a47f689d68fe51cb46fcc322 1375 fuse_2.9.0-5.dsc e4368c6032a1c167ec243fe36ccd62b573a1680e154421d15c201524a10859d8 14084 fuse_2.9.0-5.debian.tar.xz a29b6d6a3615187b27e0129621d4d802e211c1a50ed2721f5a082a3ea0dc1c27 67700 fuse_2.9.0-5_i386.deb
Bug#616673: patch to use tempfile.mkdtemp submitted upstream
tags 616673 + patch thanks see upstream bug report for the actual patch. -- Andreas Henriksson -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed: patch to use tempfile.mkdtemp submitted upstream
Processing commands for cont...@bugs.debian.org: tags 616673 + patch Bug #616673 [rhythmbox-plugins] rhythmbox-plugins: CVE-2012-3355 Plugin context contains hardcoded path to /tmp/context/ Added tag(s) patch. thanks Stopping processing here. Please contact me if you need assistance. -- 616673: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=616673 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#666598: marked as done (albatross: FTBFS: Package ifpdf Error: Name clash, \ifpdf is already defined.)
Your message dated Thu, 05 Jul 2012 15:32:54 + with message-id e1smo34-0008jz...@franck.debian.org and subject line Bug#666598: fixed in python-old-doctools 2.5.5-2.1 has caused the Debian Bug report #666598, regarding albatross: FTBFS: Package ifpdf Error: Name clash, \ifpdf is already defined. 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.) -- 666598: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=666598 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Source: albatross Version: 1.36-5.4 Severity: serious Tags: wheezy sid User: debian...@lists.debian.org Usertags: qa-ftbfs-20120331 qa-ftbfs Justification: FTBFS on amd64 Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part: make[1]: Entering directory `/«PKGBUILDDIR»/doc' python doc_methods.py -o SimpleContext-methods.tex albatross.SimpleContext python doc_methods.py -o AppContext-methods.tex albatross.AppContext python doc_methods.py -o SimpleAppContext-methods.tex albatross.SimpleAppContext python doc_methods.py -o SessionAppContext-methods.tex albatross.SessionAppContext python doc_methods.py -o SessionFileAppContext-methods.tex albatross.SessionFileAppContext python doc_methods.py -o Application-methods.tex albatross.Application python doc_methods.py -o SimpleApp-methods.tex albatross.SimpleApp python doc_methods.py -o SimpleSessionApp-methods.tex albatross.SimpleSessionApp python doc_methods.py -o SimpleSessionFileApp-methods.tex albatross.SimpleSessionFileApp python doc_methods.py -o ModularApp-methods.tex albatross.ModularApp python doc_methods.py -o ModularSessionApp-methods.tex albatross.ModularSessionApp python doc_methods.py -o ModularSessionFileApp-methods.tex albatross.ModularSessionFileApp python doc_methods.py -o RandomModularApp-methods.tex albatross.RandomModularApp python doc_methods.py -o RandomModularSessionApp-methods.tex albatross.RandomModularSessionApp python doc_methods.py -o RandomModularSessionFileApp-methods.tex albatross.RandomModularSessionFileApp python doc_methods.py -o BranchingSessionContext-methods.tex albatross.BranchingSessionContext DISPLAY= dia -e simplecontext.eps -t eps-builtin -n -l simplecontext.dia /usr/lib/python2.7/dist-packages/gtk-2.0/gtk/__init__.py:57: GtkWarning: could not open display warnings.warn(str(e), _gtk.Warning) simplecontext.dia -- simplecontext.eps epstopdf simplecontext.eps Name main::opt_restricted used only once: possible typo at /usr/bin/epstopdf line 254. Name main::opt_version used only once: possible typo at /usr/bin/epstopdf line 288. Name main::opt_help used only once: possible typo at /usr/bin/epstopdf line 283. DISPLAY= dia -e simpleappcontext.eps -t eps-builtin -n -l simpleappcontext.dia /usr/lib/python2.7/dist-packages/gtk-2.0/gtk/__init__.py:57: GtkWarning: could not open display warnings.warn(str(e), _gtk.Warning) simpleappcontext.dia -- simpleappcontext.eps epstopdf simpleappcontext.eps Name main::opt_restricted used only once: possible typo at /usr/bin/epstopdf line 254. Name main::opt_version used only once: possible typo at /usr/bin/epstopdf line 288. Name main::opt_help used only once: possible typo at /usr/bin/epstopdf line 283. DISPLAY= dia -e simpleapp.eps -t eps-builtin -n -l simpleapp.dia /usr/lib/python2.7/dist-packages/gtk-2.0/gtk/__init__.py:57: GtkWarning: could not open display warnings.warn(str(e), _gtk.Warning) simpleapp.dia -- simpleapp.eps epstopdf simpleapp.eps Name main::opt_restricted used only once: possible typo at /usr/bin/epstopdf line 254. Name main::opt_version used only once: possible typo at /usr/bin/epstopdf line 288. Name main::opt_help used only once: possible typo at /usr/bin/epstopdf line 283. DISPLAY= dia -e twolayer.eps -t eps-builtin -n -l twolayer.dia /usr/lib/python2.7/dist-packages/gtk-2.0/gtk/__init__.py:57: GtkWarning: could not open display warnings.warn(str(e), _gtk.Warning) twolayer.dia -- twolayer.eps epstopdf twolayer.eps Name main::opt_restricted used only once: possible typo at /usr/bin/epstopdf line 254. Name main::opt_version used only once: possible typo at /usr/bin/epstopdf line 288. Name main::opt_help used only once: possible typo at /usr/bin/epstopdf line 283. DISPLAY= dia -e twolayerctx.eps -t eps-builtin -n -l twolayerctx.dia /usr/lib/python2.7/dist-packages/gtk-2.0/gtk/__init__.py:57: GtkWarning: could not open display warnings.warn(str(e), _gtk.Warning) twolayerctx.dia -- twolayerctx.eps epstopdf twolayerctx.eps Name
Bug#679665: [Pkg-javascript-devel] Bug#679665: jquery: build-deps not satisfiable in wheezy
On 12-07-05 at 04:34pm, Mehdi Dogguy wrote: On 30/06/12 17:45, Julien Cristau wrote: jquery build-depends on node-uglify, which is not in testing. This needs to be fixed before release somehow. A solution might be to use yui-compressor as done prior to version 1.7.2+debian-1. yui-compressor seems to be present in testing and doesn't have any (severe) bugs currently. No recent severe bugs may have to do with it being inferior to other compressors and therefore less tested. Few projects provide regression tests for JavaScript code, so bugs are seldom caught during build. So switching compressor now has a high risk of bugs not getting discovered before release. These are the alternatives I can see: a) Switch to yui-compressor b) Get Nodejs into Wheezy and keep using uglifyjs c) Provide only uncompressed code d) Use upstream precompressed code Both a) and b) requires changes to a bunch of packages (list shortened by some of them already been kicked from Wheezy due to this issue). Due to the risk of introducing new difficult-to-verify bugs a) is bad IMO. I prefer b) but someone needs to do the social/political task of finding an acceptable solution to the namespace clash. For some possible solutions someone then needs to implement it technically - and then arguably it is too late. So as I see it, b) is only realistic if someone succeeds in solving the namespace clash problem without needing much technical work to implement it. I consider d) DFSG-violating, but others disagree. - Jonas -- * Jonas Smedegaard - idealist Internet-arkitekt * Tlf.: +45 40843136 Website: http://dr.jones.dk/ [x] quote me freely [ ] ask before reusing [ ] keep private signature.asc Description: Digital signature
Processed: breaks asterisk
Processing commands for cont...@bugs.debian.org: severity 608228 grave Bug #608228 [asterisk-prompt-de] asterisk-prompt-de: package still uses old layout file structure Severity set to 'grave' from 'important' thanks Stopping processing here. Please contact me if you need assistance. -- 608228: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=608228 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#668239: marked as done (host key handling broken when port!=22)
Your message dated Thu, 05 Jul 2012 15:49:19 +
with message-id e1smoix-ay...@franck.debian.org
and subject line Bug#668239: fixed in paramiko 1.7.7.1-2.1
has caused the Debian Bug report #668239,
regarding host key handling broken when port!=22
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.)
--
668239: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=668239
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
---BeginMessage---
Package: python-paramiko
Version: 1.7.7.1-2
Severity: important
Tags: upstream patch
in lines 307-310 in client.py, the hostname is rewritten
to [origname]:portnumber if the port isn't 22.
this serves no useful purpose at all, and it breaks
the lookup for the host key that is attempted on the next few
lines: that now fails as the ssh known hosts format allows
hostnames or ip addresses, nothing else (and certainly
not '[hostname]:port').
result: you get a unknown server exception (unless you enable the
only-warn missing host key policy).
the attached patch removes the problematic hostname rewriting.
regards
az
--- client.py.orig 2012-04-10 11:59:19.892476651 +1000
+++ client.py 2012-04-10 11:59:58.743449158 +1000
@@ -303,11 +303,7 @@
server_key = t.get_remote_server_key()
keytype = server_key.get_name()
-
-if port == SSH_PORT:
-server_hostkey_name = hostname
-else:
-server_hostkey_name = [%s]:%d % (hostname, port)
+server_hostkey_name = hostname
our_server_key = self._system_host_keys.get(server_hostkey_name,
{}).get(keytype, None)
if our_server_key is None:
our_server_key = self._host_keys.get(server_hostkey_name,
{}).get(keytype, None)
---End Message---
---BeginMessage---
Source: paramiko
Source-Version: 1.7.7.1-2.1
We believe that the bug you reported is fixed in the latest version of
paramiko, which is due to be installed in the Debian FTP archive:
paramiko_1.7.7.1-2.1.debian.tar.gz
to main/p/paramiko/paramiko_1.7.7.1-2.1.debian.tar.gz
paramiko_1.7.7.1-2.1.dsc
to main/p/paramiko/paramiko_1.7.7.1-2.1.dsc
python-paramiko_1.7.7.1-2.1_all.deb
to main/p/paramiko/python-paramiko_1.7.7.1-2.1_all.deb
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 668...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Luk Claes l...@debian.org (supplier of updated paramiko 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: Thu, 05 Jul 2012 00:38:56 +
Source: paramiko
Binary: python-paramiko
Architecture: source all
Version: 1.7.7.1-2.1
Distribution: unstable
Urgency: low
Maintainer: Jeremy T. Bouse jbo...@debian.org
Changed-By: Luk Claes l...@debian.org
Description:
python-paramiko - Make ssh v2 connections with Python
Closes: 668239
Changes:
paramiko (1.7.7.1-2.1) unstable; urgency=low
.
* Non-maintainer upload.
* Fix broken host key handling when port != 22 (Closes: 668239)
Checksums-Sha1:
4e736544bd4cd8b83cbba0197698356e5f2ef32e 1339 paramiko_1.7.7.1-2.1.dsc
e4aa8c588c5e6f9de3dd85d8147acc2741e13b95 4111
paramiko_1.7.7.1-2.1.debian.tar.gz
ab112e2faf6913b199bb522e527ac653f5b74ec1 799756
python-paramiko_1.7.7.1-2.1_all.deb
Checksums-Sha256:
1f8b76091659144927e6dcbdd87804a2863fe7582aa835ac558f138cdaeaaa12 1339
paramiko_1.7.7.1-2.1.dsc
f397897c5755a1ec8dc7264b17eec8f8878bf32dd1502189a728e2f4d77301a7 4111
paramiko_1.7.7.1-2.1.debian.tar.gz
71375f3c11bd518dc21a5636504fb6fe9aecd62a5913480f5ab8a6816a075154 799756
python-paramiko_1.7.7.1-2.1_all.deb
Files:
c0e386a81509e350b60e3c8de45fcbca 1339 python optional paramiko_1.7.7.1-2.1.dsc
03ba3e5a9c7ce0ff715b33f76160b88f 4111 python optional
paramiko_1.7.7.1-2.1.debian.tar.gz
40e568bec76121b3f78712a7501954e8 799756 python optional
python-paramiko_1.7.7.1-2.1_all.deb
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.10 (GNU/Linux)
iEYEARECAAYFAk/1tCsACgkQ+C5cwEsrK55F9QCeIl+PIIv7CFwIInynNdGA+Vxc
SUMAoISzZJkHTgHjeokQ423dFuzdzLgU
=QcXV
-END PGP SIGNATURE-
---End Message---
Bug#679749: src:ntop: maintainer address bounces
I have resolved the issue was causing my address to bounce. -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed: closing 679749
Processing commands for cont...@bugs.debian.org: close 679749 Bug #679749 [src:ntop] src:ntop: maintainer address bounces Bug #679734 [src:ntop] Maintainer address bounces Marked Bug as done Marked Bug as done thanks Stopping processing here. Please contact me if you need assistance. -- 679734: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=679734 679749: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=679749 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#654728: marked as done (mysql-5.1: non-standard gcc/g++ used for build (gcc-4.5))
Your message dated Thu, 05 Jul 2012 15:53:12 + with message-id e1smomi-p1...@franck.debian.org and subject line Bug#680362: Removed package(s) from unstable has caused the Debian Bug report #654728, regarding mysql-5.1: non-standard gcc/g++ used for build (gcc-4.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.) -- 654728: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=654728 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: mysql-5.1 Version: 5.1.58-1 Severity: important User: debian-...@lists.debian.org Usertags: non-standard-compiler, gcc-4.5 This package builds with a non standard compiler version; please check if this package can be built with the default version of gcc/g++/gfortran. Please keep this report open until the package uses the default compiler version for the package build. The severity of this report is likely to be raised before the release, so that the gcc-4.5 package can be removed for the release. ---End Message--- ---BeginMessage--- Version: 5.1.62-1+rm Dear submitter, as the package mysql-5.1 has just been removed from the Debian archive unstable we hereby close the associated bug reports. We are sorry that we couldn't deal with your issue properly. For details on the removal, please see http://bugs.debian.org/680362 The version of this package that was in Debian prior to this removal can still be found using http://snapshot.debian.org/. This message was generated automatically; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@debian.org. Debian distribution maintenance software pp. Alexander Reichle-Schmehl (the ftpmaster behind the curtain) ---End Message---
Bug#663438: marked as done (libmysqlclient: missing symbols __aeabi_d2lz (on armel))
Your message dated Thu, 05 Jul 2012 15:53:12 + with message-id e1smomi-p1...@franck.debian.org and subject line Bug#680362: Removed package(s) from unstable has caused the Debian Bug report #663438, regarding libmysqlclient: missing symbols __aeabi_d2lz (on armel) 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.) -- 663438: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=663438 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: libmysqlclient16 Version: 5.1.61-2 Severity: critical Justification: Breaks (at least my) mail system Dear maintainers, yesterday I upgraded my armel-powered NAS and after that exim4 stop working. Evaluation showed that when I do a mailq or a restart on exim4, I get this error message: mailq: relocation error: mailq: symbol __aeabi_d2lz, version libmysqlclient_16 not defined in file libmysqlclient.so.16 with link time reference thecus:/home/tobi# /etc/init.d/exim4 restart Stopping MTA for restart:/usr/sbin/exim4: relocation error: /usr/sbin/exim4: symbol __aeabi_d2lz, version libmysqlclient_16 not defined in file libmysqlclient.so.16 with link time reference After downgrading the libmysqlclient16 to 5.1.58-1 (via snapshot.debian.org) exims works again, so I assume the cause in libmysqlclient16. (Pleae reassign the bug if you thin this is wrong) If you need further details, please let me know. coldtobi Information about exim / libmysqlclient16: (before downgrading) thecus:/home/tobi# dpkg -l exim* libmysqlclient* | grep ^ii ii exim4 4.77-1 metapackage to ease Exim MTA (v4) installation ii exim4-base 4.77-1+b1 support files for all Exim MTA (v4) packages ii exim4-config4.77-1 configuration for the Exim MTA (v4) ii exim4-daemon-heavy 4.77-1+b1 Exim MTA (v4) daemon with extended features, including exiscan-acl ii libmysqlclient-dev 5.1.61-2 MySQL database development files ii libmysqlclient165.1.61-2 MySQL database client library AFTER downgrading: thecus:/home/tobi# dpkg -l exim* libmysqlclient* | grep ^ii ii exim4 4.77-1 metapackage to ease Exim MTA (v4) installation ii exim4-base 4.77-1+b1 support files for all Exim MTA (v4) packages ii exim4-config4.77-1 configuration for the Exim MTA (v4) ii exim4-daemon-heavy 4.77-1+b1 Exim MTA (v4) daemon with extended features, including exiscan-acl ii libmysqlclient-dev 5.1.58-1 MySQL database development files ii libmysqlclient165.1.58-1 MySQL database client library -- System Information: Debian Release: wheezy/sid APT prefers testing APT policy: (900, 'testing'), (500, 'unstable'), (500, 'stable') Architecture: armel (armv5tel) Kernel: Linux 3.0.0-1-iop32x Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash Versions of packages libmysqlclient16 depends on: ii libc6 2.13-27 ii libgcc1 1:4.6.3-1 ii mysql-common 5.1.61-2 ii zlib1g1:1.2.6.dfsg-2 libmysqlclient16 recommends no packages. libmysqlclient16 suggests no packages. -- no debconf information ---End Message--- ---BeginMessage--- Version: 5.1.62-1+rm Dear submitter, as the package mysql-5.1 has just been removed from the Debian archive unstable we hereby close the associated bug reports. We are sorry that we couldn't deal with your issue properly. For details on the removal, please see http://bugs.debian.org/680362 The version of this package that was in Debian prior to this removal can still be found using http://snapshot.debian.org/. This message was generated automatically; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@debian.org. Debian distribution maintenance software pp. Alexander Reichle-Schmehl (the ftpmaster behind the curtain) ---End Message---
Bug#670438: marked as done (Multiple serious crashes after updating to MySQL 5.1.61-0+squeeze1)
Your message dated Thu, 05 Jul 2012 15:53:12 + with message-id e1smomi-p1...@franck.debian.org and subject line Bug#680362: Removed package(s) from unstable has caused the Debian Bug report #670438, regarding Multiple serious crashes after updating to MySQL 5.1.61-0+squeeze1 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.) -- 670438: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=670438 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: mysql-server-5.1 Version: 5.1.61-0+squeeze1 Severity: grave We are running multiple MySQL-Servers with master/slave-replication on Debian Squeeze 6.0. After updating the mysql packages from 5.1.49-3 to 5.1.61-0+squeeze1 the mysqld process crashes sporadically within minutes after starting. We have tested this update/behaviour on two slave machines to exclude a hardware failure. These crashes happen with the default mysql server configuration, also. After downgrading to 5.1.49-3 the slaves are running fine. I have also tried the percona mysql server builds (5.1.61) for Debian Squeeze and they are working normal, too. Testing with mysql query log enabled shows no specific query to cause the crash. Some hardware specs: Supermicro X8DT3 Mainboard, Intel Xeon E5506 CPU, 24 GB RAM, 3ware 9750 SAS-Controller Thanks in advance. The logfile /var/log/daemon.log says the following: === Apr 24 15:01:52 euros mysqld: *** glibc detected *** /usr/sbin/mysqld: double free or corruption (!prev): 0x7f466402b600 *** Apr 24 15:01:52 euros mysqld: === Backtrace: = Apr 24 15:01:52 euros mysqld: /lib/libc.so.6(+0x71bd6)[0x7f4aa6270bd6] Apr 24 15:01:52 euros mysqld: /lib/libc.so.6(cfree+0x6c)[0x7f4aa627594c] Apr 24 15:01:52 euros mysqld: /usr/sbin/mysqld(_ZN15Query_log_eventD0Ev+0x20)[0x7f4aa8005ed0] Apr 24 15:01:52 euros mysqld: /usr/sbin/mysqld(handle_slave_sql+0x835)[0x7f4aa807a255] Apr 24 15:01:52 euros mysqld: /lib/libpthread.so.0(+0x68ca)[0x7f4aa77868ca] Apr 24 15:01:52 euros mysqld: /lib/libc.so.6(clone+0x6d)[0x7f4aa62ce92d] Apr 24 15:01:52 euros mysqld: === Memory map: Apr 24 15:01:52 euros mysqld: 7f4654837000-7f46590bd000 rw-p 00:00 0 Apr 24 15:01:52 euros mysqld: 7f466400-7f46645ae000 rw-p 00:00 0 Apr 24 15:01:52 euros mysqld: 7f46645ae000-7f466800 ---p 00:00 0 Apr 24 15:01:52 euros mysqld: 7f466836e000-7f466836f000 rw-p 00:00 0 Apr 24 15:01:52 euros mysqld: 7f466836f000-7f466837 ---p 00:00 0 Apr 24 15:01:52 euros mysqld: 7f466837-7f46683b rw-p 00:00 0 Apr 24 15:01:52 euros mysqld: 7f46683b-7f46683b1000 ---p 00:00 0 Apr 24 15:01:52 euros mysqld: 7f46683b1000-7f46683f1000 rw-p 00:00 0 Apr 24 15:01:52 euros mysqld: 7f46683f1000-7f46683f2000 ---p 00:00 0 Apr 24 15:01:52 euros mysqld: 7f46683f2000-7f4668432000 rw-p 00:00 0 Apr 24 15:01:52 euros mysqld: 7f4668432000-7f4668433000 ---p 00:00 0 Apr 24 15:01:52 euros mysqld: 7f4668433000-7f4668473000 rw-p 00:00 0 Apr 24 15:01:52 euros mysqld: 7f4668473000-7f4668474000 ---p 00:00 0 Apr 24 15:01:52 euros mysqld: 7f4668474000-7f46684b4000 rw-p 00:00 0 Apr 24 15:01:52 euros mysqld: 7f46684b4000-7f46684b5000 ---p 00:00 0 Apr 24 15:01:52 euros mysqld: 7f46684b5000-7f4668cb5000 rw-p 00:00 0 Apr 24 15:01:52 euros mysqld: 7f4668cb5000-7f4668cb6000 ---p 00:00 0 Apr 24 15:01:52 euros mysqld: 7f4668cb6000-7f46694b6000 rw-p 00:00 0 Apr 24 15:01:52 euros mysqld: 7f46694b6000-7f46694b7000 ---p 00:00 0 Apr 24 15:01:52 euros mysqld: 7f46694b7000-7f4669cb7000 rw-p 00:00 0 Apr 24 15:01:52 euros mysqld: 7f4669cb7000-7f4669cb8000 ---p 00:00 0 Apr 24 15:01:52 euros mysqld: 7f4669cb8000-7f466a4b8000 rw-p 00:00 0 Apr 24 15:01:52 euros mysqld: 7f466a4b8000-7f466a4b9000 ---p 00:00 0 Apr 24 15:01:52 euros mysqld: 7f466a4b9000-7f466acb9000 rw-p 00:00 0 Apr 24 15:01:52 euros mysqld: 7f466acb9000-7f466acba000 ---p 00:00 0 Apr 24 15:01:52 euros mysqld: 7f466acba000-7f466b4ba000 rw-p 00:00 0 Apr 24 15:01:52 euros mysqld: 7f466b4ba000-7f466b4bb000 ---p 00:00 0 Apr 24 15:01:52 euros mysqld: 7f466b4bb000-7f466bcbb000 rw-p 00:00 0 Apr 24 15:01:52 euros mysqld: 7f466bcbb000-7f466bcbc000 ---p 00:00 0 Apr 24 15:01:52 euros mysqld: 7f466bcbc000-7f4aa53da000 rw-p 00:00 0 Apr 24 15:01:52 euros mysqld: 7f4aa53da000-7f4aa53e6000 r-xp fe:00 1048586/lib/libnss_files-2.11.3.so Apr 24 15:01:52 euros mysqld:
Bug#677018: marked as done (mysql-5.1: CVE-2012-2122: MySQL authentication bypass)
Your message dated Thu, 05 Jul 2012 15:53:12 + with message-id e1smomi-p1...@franck.debian.org and subject line Bug#680362: Removed package(s) from unstable has caused the Debian Bug report #677018, regarding mysql-5.1: CVE-2012-2122: MySQL authentication bypass 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.) -- 677018: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=677018 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: mysql-5.1 Version: 5.1.61-0+squeeze1 Severity: important Tags: security http://seclists.org/oss-sec/2012/q2/493 https://www.secmaniac.com/blog/2012/06/11/massive-mysql-authentication-bypass-exploit/ I haven't verified this as I do not have time at the moment. References from the email: References: MariaDB bug report: https://mariadb.atlassian.net/browse/MDEV-212 MariaDB fix: http://bazaar.launchpad.net/~maria-captains/maria/5.1/revision/3144 MySQL bug report: http://bugs.mysql.com/bug.php?id=64884 MySQL fix: http://bazaar.launchpad.net/~mysql/mysql-server/5.1/revision/3560.10.17 MySQL changelog: http://dev.mysql.com/doc/refman/5.1/en/news-5-1-63.html http://dev.mysql.com/doc/refman/5.5/en/news-5-5-24.html -- System Information: Debian Release: 6.0.5 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 3.4.1 (SMP w/8 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) (ignored: LC_ALL set to en_US.UTF-8) Shell: /bin/sh linked to /bin/dash ---End Message--- ---BeginMessage--- Version: 5.1.62-1+rm Dear submitter, as the package mysql-5.1 has just been removed from the Debian archive unstable we hereby close the associated bug reports. We are sorry that we couldn't deal with your issue properly. For details on the removal, please see http://bugs.debian.org/680362 The version of this package that was in Debian prior to this removal can still be found using http://snapshot.debian.org/. This message was generated automatically; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@debian.org. Debian distribution maintenance software pp. Alexander Reichle-Schmehl (the ftpmaster behind the curtain) ---End Message---
Bug#677057: marked as done (mysql-client-5.1: uninstallable because mysql-common Breaks: mysql-client-5.1 ( 5.5))
Your message dated Thu, 05 Jul 2012 15:53:12 + with message-id e1smomi-p1...@franck.debian.org and subject line Bug#680362: Removed package(s) from unstable has caused the Debian Bug report #677057, regarding mysql-client-5.1: uninstallable because mysql-common Breaks: mysql-client-5.1 ( 5.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.) -- 677057: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=677057 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: mysql-client-5.1 Version: 5.1.62-1 Severity: serious User: debian...@lists.debian.org Usertags: piuparts Hi, during a test with piuparts I noticed your package is no longer installable: Package: mysql-client-5.1 Source: mysql-5.1 Version: 5.1.62-1 Depends: ..., mysql-common (= 5.1.62-1), ... Package: mysql-common Source: mysql-5.5 Version: 5.5.24+dfsg-3 Breaks: ..., mysql-client-5.1 ( 5.5), ... Cheers, Andreas ---End Message--- ---BeginMessage--- Version: 5.1.62-1+rm Dear submitter, as the package mysql-5.1 has just been removed from the Debian archive unstable we hereby close the associated bug reports. We are sorry that we couldn't deal with your issue properly. For details on the removal, please see http://bugs.debian.org/680362 The version of this package that was in Debian prior to this removal can still be found using http://snapshot.debian.org/. This message was generated automatically; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@debian.org. Debian distribution maintenance software pp. Alexander Reichle-Schmehl (the ftpmaster behind the curtain) ---End Message---
Bug#674689: mimms in debian: upstream takeover
On 05/29/2012 11:26 PM, Bart Martens wrote: If there is interest in using the savannah or launchpad sites for development, I would be happy to add any interested parties as administrators to do what they wish with them. It would be nice to have the old pages link to the new page(s). Can you do that ? Or can you grant Mohammad access to do that ? Regards, Bart Martens Sorry it took a while to respond to this message. Mohammad was already listed as a project member, but I've now also marked him (and all other contributors) as administrators. That should let everyone be able to work together on using the savannah site either for development or just as a redirect. -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#676423: doxygen: new segmentation faults in version 1.8.1-1
package doxygen
tags 676423 + patch
thanks
Hi,
removeEmptyLines() segfaults on empty string.
Here comes a patch.
Regards, Thibaut.
Description: fix for 676423: new segmentation faults in version 1.8.1-1
removeEmptyLines() segfaults on empty string
Author: Thibaut Paumard paum...@users.sourceforge.net
Origin: vendor
Bug-Debian: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=676423
Forwarded: no
Last-Update: 2012-07-05
---
This patch header follows DEP-3: http://dep.debian.net/deps/dep3/
--- a/src/htmlgen.cpp
+++ b/src/htmlgen.cpp
@@ -936,6 +936,11 @@
static QCString removeEmptyLines(const QCString s)
{
BufStr out(s.length()+1);
+ if (s.length()==0)
+ {
+out.addChar('\0');
+return out.data();
+ }
char *p=s.data();
char c;
while ((c=*p++))
signature.asc
Description: OpenPGP digital signature
Processed: Re: doxygen: new segmentation faults in version 1.8.1-1
Processing commands for cont...@bugs.debian.org: package doxygen Limiting to bugs with field 'package' containing at least one of 'doxygen' Limit currently set to 'package':'doxygen' tags 676423 + patch Bug #676423 [doxygen] doxygen: new segmentation faults in version 1.8.1-1 Added tag(s) patch. thanks Stopping processing here. Please contact me if you need assistance. -- 676423: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=676423 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#676800: [Pkg-octave-devel] Bug#676800: octave-java: completely breaks octave
On Sat, Jun 09, 2012 at 12:17:48PM +, Sébastien Villemot wrote: Package: octave-java Version: 1.2.8-4 Severity: grave Tags: sid This version of octave-java completely breaks octave. Sébastien, is this the same issue we tried to debug in IRC? I wasn't able to reproduce it, and I didn't see anyone else having similar problems. Thomas -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#679665: [Pkg-javascript-devel] Bug#679665: jquery: build-deps not satisfiable in wheezy
On 05/07/12 17:38, Jonas Smedegaard wrote: On 12-07-05 at 04:34pm, Mehdi Dogguy wrote: On 30/06/12 17:45, Julien Cristau wrote: jquery build-depends on node-uglify, which is not in testing. This needs to be fixed before release somehow. A solution might be to use yui-compressor as done prior to version 1.7.2+debian-1. yui-compressor seems to be present in testing and doesn't have any (severe) bugs currently. No recent severe bugs may have to do with it being inferior to other compressors and therefore less tested. I'm not sure. Looking at the popcon stats, yui-compressor seems more popular than uglifyjs. That doesn't say anything on their quality but makes your argument mostly moot, imho. Few projects provide regression tests for JavaScript code, so bugs are seldom caught during build. So switching compressor now has a high risk of bugs not getting discovered before release. AFAICS, you are testing it using JSHint… so even if you change the compressor, you'll still be running JSHint on it, no? how does it make a difference then? or do you run any other tests? (apologies if I missed something). These are the alternatives I can see: a) Switch to yui-compressor b) Get Nodejs into Wheezy and keep using uglifyjs c) Provide only uncompressed code That would break reverse dependencies though (if there are relying in their code on jquery.min.js). d) Use upstream precompressed code Please, no. Both a) and b) requires changes to a bunch of packages (list shortened by some of them already been kicked from Wheezy due to this issue). Why a) requires changes to a bunch of packages? AIUI, we are only talking about jquery here and it already changes some bits of the build system about uglifyjs. Due to the risk of introducing new difficult-to-verify bugs a) is bad IMO. I prefer b) but someone needs to do the social/political task of finding an acceptable solution to the namespace clash. For some possible solutions someone then needs to implement it technically - and then arguably it is too late. So as I see it, b) is only realistic if someone succeeds in solving the namespace clash problem without needing much technical work to implement it. Personally, I think that fixing the nameclash should not happen during the freeze. ymmv though. After fixing that, one should wonder how to fix the remaining rc-bug (about failed tests) :) Regards, -- Mehdi -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#659061: brasero: segfaults when creating a subfolder
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 package brasero tags 659061 + upstream thanks Le 05/07/12 16:20, Josselin Mouette a écrit : Le jeudi 05 juillet 2012 à 14:28 +0200, Thibaut Paumard a écrit : I confirm that the bug is still present in 3.4.1-2 and that the patch solves it. The patch is a very clear 1-line addition and applies cleanly on top of 3.4.1. Can you forward it upstream on bugzilla.gnome.org? Thanks, Done: https://bugzilla.gnome.org/show_bug.cgi?id=679460 Regards, Thibaut. -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.8 (Darwin) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iQIcBAEBCAAGBQJP9bvBAAoJEJOUU0jg3ChAunkQAMt3KfPgiqZLPzUH8YRfg26x hOapthVI2w7bfjuvBFk1WUjCKqdIVwOdlcoiU82x8VeJTnyc/kVCBZdMhs73jlm6 wVbq81Z+qyEy35ErXN+dd31Z6oBU//UBOEWtxZ5Wg6CmuiG6z5LYDAhGetmw1SEe 96Pg0beHRz4OpSIQ456tLZ06zaI0L6FTMzEqRxX0Lmux1zx4DLYW/0zROsvW4hN0 eIbGbNUr+2SI2A+PL8FmJZ9vHwEWd2MrWPEyoZnKIbYz9lJiKhP3zRJUAlXllHvL 5HpGaiqOxpE7VXL/6pux+ZmoQsfkcfysg1SZt2ru43YQun8/+CxpYpaV2BuZEXG9 /vSDnxAS5C8fZXakRgbJZust4SjQUNE1Qmy++RBeurseZ1xWrVlbkKrtJSjdjO/u WfvCnH2nzDV80FNcWIV/EtgmLipOz3rxwkskbNlZWAGD42jq3j09mKwwYnBfhfkp 7ynrzWDsYXDi+CHaqs9PaFiTOt3aS4ifRPdQqb4Q3pCxht0JR1r1tjqNwkWfcMxt mzN7F/OYeZ+jZwkrqZVRIvHOv4ROVQ01BYlnOhCpsmfZ92b0FBqnzKlPqw3M2vdr apF0gJc7eM5YgXrOdsm/uhM1oTUSVi3HKqT43QODwMHXXV/AW/VcfvGeZmaG8SzR yItwBqvGUf5w5Bcebdbd =u3PA -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#674689: mimms in debian: upstream takeover
On Thu, Jul 05, 2012 at 10:02:40AM -0600, Wesley J. Landaker wrote: On 05/29/2012 11:26 PM, Bart Martens wrote: If there is interest in using the savannah or launchpad sites for development, I would be happy to add any interested parties as administrators to do what they wish with them. I didn't write that. It would be nice to have the old pages link to the new page(s). Can you do that ? Or can you grant Mohammad access to do that ? That is something I wrote. Regards, Bart Martens Sorry it took a while to respond to this message. No problem at all. Mohammad was already listed as a project member, but I've now also marked him (and all other contributors) as administrators. That should let everyone be able to work together on using the savannah site either for development or just as a redirect. I see that the bug is already done so this is no issue for me anymore. 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
Processed: aprsdigi: diff for NMU version 2.4.4-3.2
Processing commands for cont...@bugs.debian.org: tags 664932 + pending Bug #664932 [src:aprsdigi] aprsdigi: FTBFS: testparse.c:19:33: fatal error: netax25/kernel_ax25.h: No such file or directory Added tag(s) pending. thanks Stopping processing here. Please contact me if you need assistance. -- 664932: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=664932 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#658252: libcairo2: Text quickly becomes rectangles
I'd also like to add that I have an Nvidia card which has the same problem. I used the advice on the following post to downgrade to 1.10 and there is no more screen corruption, smudging or blurring. http://forums.debian.net/viewtopic.php?f=7t=79467 -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#664932: aprsdigi: diff for NMU version 2.4.4-3.2
tags 664932 + pending thanks Dear maintainer, I've prepared an NMU for aprsdigi (versioned as 2.4.4-3.2) and will have it uploaded soon. Cheers Luk diff -u aprsdigi-2.4.4/debian/changelog aprsdigi-2.4.4/debian/changelog --- aprsdigi-2.4.4/debian/changelog +++ aprsdigi-2.4.4/debian/changelog @@ -1,3 +1,10 @@ +aprsdigi (2.4.4-3.2) unstable; urgency=low + + * Non-maintainer upload. + * include linux/ax25.h instead of netax25/* (Closes: #664932). + + -- Luk Claes l...@debian.org Fri, 08 Jun 2012 23:23:13 +0200 + aprsdigi (2.4.4-3.1) unstable; urgency=low * Retiring - remove myself from the uploaders list. only in patch2: unchanged: --- aprsdigi-2.4.4.orig/libax25ext.c +++ aprsdigi-2.4.4/libax25ext.c @@ -9,7 +9,6 @@ #include netax25/ax25.h #include netrose/rose.h -#include netax25/axlib.h #include libax25ext.h #include string.h only in patch2: unchanged: --- aprsdigi-2.4.4.orig/aprsdigi.c +++ aprsdigi-2.4.4/aprsdigi.c @@ -53,11 +53,7 @@ #include time.h #include signal.h #include errno.h -#include netax25/kernel_ax25.h -#include netax25/kernel_rose.h -#include netax25/ax25.h -#include netax25/axlib.h -#include netax25/axconfig.h +#include linux/ax25.h #ifndef AX25_MTU #define AX25_MTU 256 #endif only in patch2: unchanged: --- aprsdigi-2.4.4.orig/aprsmon.c +++ aprsdigi-2.4.4/aprsmon.c @@ -61,11 +61,7 @@ #include time.h #include signal.h -#include netax25/kernel_ax25.h -#include netax25/kernel_rose.h -#include netax25/ax25.h -#include netax25/axlib.h -#include netax25/axconfig.h +#include linux/ax25.h #ifndef HAVE_LIBAX25_EXTENSIONS #include libax25ext.h only in patch2: unchanged: --- aprsdigi-2.4.4.orig/aprsshm.c +++ aprsdigi-2.4.4/aprsshm.c @@ -44,9 +44,7 @@ #include ctype.h #include time.h -#include netax25/ax25.h -#include netax25/axconfig.h #include aprsshm.h #define MAXPPM 10 only in patch2: unchanged: --- aprsdigi-2.4.4.orig/testmcast.c +++ aprsdigi-2.4.4/testmcast.c @@ -16,11 +16,7 @@ #include time.h #include signal.h #include errno.h -#include netax25/kernel_ax25.h -#include netax25/kernel_rose.h -#include netax25/ax25.h -#include netax25/axlib.h -#include netax25/axconfig.h +#include linux/ax25.h #ifndef AX25_MTU #define AX25_MTU 256 #endif only in patch2: unchanged: --- aprsdigi-2.4.4.orig/testparse.c +++ aprsdigi-2.4.4/testparse.c @@ -16,11 +16,7 @@ #include time.h #include signal.h #include errno.h -#include netax25/kernel_ax25.h -#include netax25/kernel_rose.h -#include netax25/ax25.h -#include netax25/axlib.h -#include netax25/axconfig.h +#include linux/ax25.h #include netdb.h #include libax25ext.h static void print_it(FILE *f,
Bug#668239: paramiko: diff for NMU version 1.7.7.1-2.1
On 07/04/2012 08:57 PM, Luk Claes wrote: tags 668239 + pending thanks Dear maintainer, I've prepared an NMU for paramiko (versioned as 1.7.7.1-2.1) and will have it uploaded soon. Cheers Luk Any reason you felt that you couldn't actually follow the process I'd already established to submit the patch to the VCS that the package is maintained out of? I purposely put the package maintenance on git.debian.org within collab-maint so that any DD could submit commits for the package back. You obviously looked at the BTS so did you not bother to check out the PTS and see it was in VCS? -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed: your mail
Processing commands for cont...@bugs.debian.org: tag 679819 + pending Bug #679819 [python-qt4] Dropping Provides field broke depending software (python-avogadro) Added tag(s) pending. thanks Stopping processing here. Please contact me if you need assistance. -- 679819: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=679819 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#679819: marked as done (Dropping Provides field broke depending software (python-avogadro))
Your message dated Thu, 05 Jul 2012 16:47:32 + with message-id e1smpdi-0006gr...@franck.debian.org and subject line Bug#679819: fixed in python-qt4 4.9.3-2 has caused the Debian Bug report #679819, regarding Dropping Provides field broke depending software (python-avogadro) 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.) -- 679819: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=679819 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: python-qt4 Version: 4.9.3-1 Severity: serious -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 The last upload of python-qt4 removed the Provides field. Unfortunately this breaks the installation of avogadro, which depends on python2.7-qt4. Why has this field been removed and how should this be handled now? How shall this be handlded in future removals of Provides fields in python* packages? Regards, Daniel - -- System Information: Debian Release: wheezy/sid APT prefers unstable APT policy: (850, 'unstable'), (700, 'testing'), (560, 'stable'), (110, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 3.2.0-3-amd64 (SMP w/2 CPU cores) Locale: LANG=de_DE.utf8, LC_CTYPE=de_DE.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash Versions of packages python-qt4 depends on: ii libc6 2.13-34 ii libgcc1 1:4.7.1-2 ii libpython2.7 2.7.3-1 ii libqt4-dbus 4:4.8.2-1 ii libqt4-declarative4:4.8.2-1 ii libqt4-designer 4:4.8.2-1 ii libqt4-help 4:4.8.2-1 ii libqt4-network4:4.8.2-1 ii libqt4-script 4:4.8.2-1 ii libqt4-scripttools4:4.8.2-1 ii libqt4-svg4:4.8.2-1 ii libqt4-test 4:4.8.2-1 ii libqt4-xml4:4.8.2-1 ii libqt4-xmlpatterns4:4.8.2-1 ii libqtassistantclient4 4.6.3-4 ii libqtcore44:4.8.2-1 ii libqtgui4 4:4.8.2-1 ii libqtwebkit4 2.2.1-4+b1 ii libstdc++64.7.1-2 ii python2.7.3-1 ii python-sip [sip-api-8.1] 4.13.3-2 ii python2.6 2.6.8-0.2 ii python2.7 2.7.3-1 python-qt4 recommends no packages. Versions of packages python-qt4 suggests: pn python-qt4-dbg none - -- no debconf information -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.12 (GNU/Linux) iEYEARECAAYFAk/wpi0ACgkQm0bx+wiPa4w0lgCeK89qTio3lje6udcBgmvWYEAq a+UAnRz9J4yzCGtayF8uYhNRbXtLgHw6 =pWF9 -END PGP SIGNATURE- ---End Message--- ---BeginMessage--- Source: python-qt4 Source-Version: 4.9.3-2 We believe that the bug you reported is fixed in the latest version of python-qt4, which is due to be installed in the Debian FTP archive: pyqt4-dev-tools_4.9.3-2_i386.deb to main/p/python-qt4/pyqt4-dev-tools_4.9.3-2_i386.deb python-qt4-dbg_4.9.3-2_i386.deb to main/p/python-qt4/python-qt4-dbg_4.9.3-2_i386.deb python-qt4-dbus-dbg_4.9.3-2_i386.deb to main/p/python-qt4/python-qt4-dbus-dbg_4.9.3-2_i386.deb python-qt4-dbus_4.9.3-2_i386.deb to main/p/python-qt4/python-qt4-dbus_4.9.3-2_i386.deb python-qt4-dev_4.9.3-2_all.deb to main/p/python-qt4/python-qt4-dev_4.9.3-2_all.deb python-qt4-doc_4.9.3-2_all.deb to main/p/python-qt4/python-qt4-doc_4.9.3-2_all.deb python-qt4-gl-dbg_4.9.3-2_i386.deb to main/p/python-qt4/python-qt4-gl-dbg_4.9.3-2_i386.deb python-qt4-gl_4.9.3-2_i386.deb to main/p/python-qt4/python-qt4-gl_4.9.3-2_i386.deb python-qt4-phonon-dbg_4.9.3-2_i386.deb to main/p/python-qt4/python-qt4-phonon-dbg_4.9.3-2_i386.deb python-qt4-phonon_4.9.3-2_i386.deb to main/p/python-qt4/python-qt4-phonon_4.9.3-2_i386.deb python-qt4-sql-dbg_4.9.3-2_i386.deb to main/p/python-qt4/python-qt4-sql-dbg_4.9.3-2_i386.deb python-qt4-sql_4.9.3-2_i386.deb to main/p/python-qt4/python-qt4-sql_4.9.3-2_i386.deb python-qt4_4.9.3-2.debian.tar.gz to main/p/python-qt4/python-qt4_4.9.3-2.debian.tar.gz python-qt4_4.9.3-2.dsc to main/p/python-qt4/python-qt4_4.9.3-2.dsc python-qt4_4.9.3-2_i386.deb to main/p/python-qt4/python-qt4_4.9.3-2_i386.deb python3-dbus.mainloop.qt-dbg_4.9.3-2_i386.deb to main/p/python-qt4/python3-dbus.mainloop.qt-dbg_4.9.3-2_i386.deb python3-dbus.mainloop.qt_4.9.3-2_i386.deb to main/p/python-qt4/python3-dbus.mainloop.qt_4.9.3-2_i386.deb python3-pyqt4-dbg_4.9.3-2_i386.deb to main/p/python-qt4/python3-pyqt4-dbg_4.9.3-2_i386.deb python3-pyqt4.phonon-dbg_4.9.3-2_i386.deb to main/p/python-qt4/python3-pyqt4.phonon-dbg_4.9.3-2_i386.deb python3-pyqt4.phonon_4.9.3-2_i386.deb to main/p/python-qt4/python3-pyqt4.phonon_4.9.3-2_i386.deb
Bug#680397: aces3: FTBFS: Times out
Source: aces3 Version: 3.0.6-4 Severity: serious Hi, Your package fails to build on a few arches, timing out in the test suite: (cd tests; OMPI_MCA_plm_rsh_agent=/bin/false csh ./runscript) Running 1.1.1.1 mpirun: killing job... E: Caught signal 'Terminated': terminating immediately -- mpirun noticed that process rank 0 with PID 9855 on node murphy exited on signal 0 (Unknown signal 0). -- mpirun: clean termination accomplished make: *** [build-arch] Terminated make[1]: *** [override_dh_auto_test] Terminated Build killed with signal TERM after 150 minutes of inactivity Kurt -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed: unblock 680380 with 679821
Processing commands for cont...@bugs.debian.org:
unblock 680380 with 679821
Bug #680380 {Done: Scott Kitterman deb...@kitterman.com} [python-sip]
Dropping Provides field broke depending software (python-avogadro)
680380 was blocked by: 679821
680380 was blocking: 679821
Removed blocking bug(s) of 680380: 679821
Warning: Unknown package 'src:python-avogadro'
thanks
Stopping processing here.
Please contact me if you need assistance.
--
680380: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=680380
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#680399: asus-oled-dkms: FTBFS: make: *** /lib/modules/2.6.32/build: No such file or directory. Stop.
Source: asus-oled-dkms Version: 0.04-1 Severity: serious Hi, Your package is failing to build with the following error: dh_auto_build -a make -j1 make[1]: Entering directory `/build/buildd-asus-oled-dkms_0.04-1-armel-RNd9kY/asus-oled-dkms-0.04' make -C /lib/modules/2.6.32/build SUBDIRS=/build/buildd-asus-oled-dkms_0.04-1-armel-RNd9kY/asus-oled-dkms-0.04 modules -w make: Entering an unknown directory make: *** /lib/modules/2.6.32/build: No such file or directory. Stop. It seems to be trying to access things for the running kernel, which is never what you want to do. Kurt -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
