Bug#639744: Compromised certificates for *.google.com issued by DigiNotar Root CA
On lun., 2011-08-29 at 20:24 -0700, Josh Triplett wrote:
On Mon, Aug 29, 2011 at 08:32:40PM -0500, Raphael Geissert wrote:
On Monday 29 August 2011 20:19:11 Josh Triplett wrote:
Does OpenSSL not have any facility for a system-wide revocation
list?
No, I already checked that back when the Comodo hack occurred.
Every application needs to manually load the revocation lists, just
like they
need to manually check the trust chain and all the other
this-should-all-be-
done-in-just-one-place things.
I understand that they'd have to manually load the lists, but perhaps
it
would make sense to standardize a location from which they should load
them? Does OpenSSL or GnuTLS have any concept of a revocation store
format, similar to a certificate store, or would this need some
special-purpose custom format?
And it'd be nice if nss could share that store...
nss apps are more or less starting to use a {/etc/,~/.}pki/nssdb/ which
can be shared accross apps (though I only know about evolution using it
right now).
By the way, shouldn't this bug be clone to libnss3-1d (and maybe
iceweasel and icedove if they ship the certificates themselves)?
Regards,
--
Yves-Alexis
signature.asc
Description: This is a digitally signed message part
Bug#629204: Fixed version ready for test
Hi, I've written a patch that seems to work with both gnustep-base/1.20 and 1.22. I'm waiting for upstream's approval [1], it can be grabbed here [2] if anyone wants to test it. Cheers, Federico [1] http://lists.gnu.org/archive/html/gnustep-dev/2011-08/msg00095.html [2] git://git.debian.org/pkg-gnustep/gnustep-dl2.git -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#638817: (no subject)
I do not fully understand what the issue is, but I think that it is an issue with libnotify rather than gnome-settings-daemon. I'm not sure if it was a libnotify update that broke this package or gnome-settings-daemon broke itself. Running gnome-settings-daemon as root appears to be a workaround, and allows the gtk2 themes to be loaded. I can also confirm this. -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#637689:
Hi, I made some changes in the Control file and I issued a new release, it built with no problems with pbuilder in a clean environment (I packaged for sid, squeeze and lucid), actually I have some problem building for a different architecture (amd64), I couldn't work it out, maybe I've got some wrong settings, can you check it for me please? A stupid question ;), what shall I do with the new release (nautic-1.3-6) source code? witch site shall I post it ? Regards Giovanni Enas -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed: qgo: diff for NMU version 1.5.4-r3-2.1
Processing commands for cont...@bugs.debian.org: tags 565092 + pending Bug #565092 [qgo] qgo: ftbfs with gcc-4.5 Added tag(s) pending. thanks Stopping processing here. Please contact me if you need assistance. -- 565092: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=565092 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#565092: qgo: diff for NMU version 1.5.4-r3-2.1
tags 565092 + pending
thanks
Dear maintainer,
I've prepared an NMU for qgo (versioned as 1.5.4-r3-2.1) and
uploaded it to DELAYED/10. Please feel free to tell me if I
should delay it longer.
Laurent.
diff -u qgo-1.5.4-r3/debian/changelog qgo-1.5.4-r3/debian/changelog
--- qgo-1.5.4-r3/debian/changelog
+++ qgo-1.5.4-r3/debian/changelog
@@ -1,3 +1,10 @@
+qgo (1.5.4-r3-2.1) unstable; urgency=low
+
+ * Non-maintainer upload.
+ * Fix g++-4.5 FTBFS, thanks Andreas Moog for the patch (closes: #565092).
+
+ -- Laurent Fousse lfou...@debian.org Tue, 30 Aug 2011 09:03:34 +0200
+
qgo (1.5.4-r3-2) unstable; urgency=low
* fix MimeType in qgo.desktop (closes: #534132 , closes: #535673)
diff -u qgo-1.5.4-r3/debian/patches/00list qgo-1.5.4-r3/debian/patches/00list
--- qgo-1.5.4-r3/debian/patches/00list
+++ qgo-1.5.4-r3/debian/patches/00list
@@ -5,0 +6 @@
+06_ftbfs_gcc45.dpatch
only in patch2:
unchanged:
--- qgo-1.5.4-r3.orig/debian/patches/06_ftbfs_gcc45.dpatch
+++ qgo-1.5.4-r3/debian/patches/06_ftbfs_gcc45.dpatch
@@ -0,0 +1,205 @@
+#! /bin/sh /usr/share/dpatch/dpatch-run
+## Description: fix builiding with gcc4.5
+## Origin/Author: Ubuntu
+## Bug: http://bugs.launchpad.net/bugs/756004
+## 06_ftbfs_gcc45.dpatch by Andreas Moog am...@ubuntu.com
+##
+## All lines beginning with `## DP:' are a description of the patch.
+## DP: fix build with gcc 4.5
+
+@DPATCH@
+diff -urNad '--exclude=CVS' '--exclude=.svn' '--exclude=.git' '--exclude=.arch' '--exclude=.hg' '--exclude=_darcs' '--exclude=.bzr' qgo-1.5.4-r3~/src/gamedialog.cpp qgo-1.5.4-r3/src/gamedialog.cpp
+--- qgo-1.5.4-r3~/src/gamedialog.cpp 2011-04-12 20:03:12.0 +0200
qgo-1.5.4-r3/src/gamedialog.cpp 2011-04-12 20:03:15.640382627 +0200
+@@ -512,7 +512,7 @@
+ if (handicapSpin-value() != val.toInt())
+ {
+ handicapSpin-setValue(val.toInt());
+- handicapSpin-setPaletteBackgroundColor(QColor::QColor(cyan));
++ handicapSpin-setPaletteBackgroundColor(QColor(cyan));
+ }
+ else
+ handicapSpin-unsetPalette();
+@@ -521,7 +521,7 @@
+ if (boardSizeSpin-value() != val.toInt())
+ {
+ boardSizeSpin-setValue(val.toInt());
+- boardSizeSpin-setPaletteBackgroundColor(QColor::QColor(cyan));
++ boardSizeSpin-setPaletteBackgroundColor(QColor(cyan));
+ }
+ else
+ boardSizeSpin-unsetPalette();
+@@ -530,7 +530,7 @@
+ if (timeSpin-value() != val.toInt()/60)
+ {
+ timeSpin-setValue(val.toInt()/60);
+- timeSpin-setPaletteBackgroundColor(QColor::QColor(cyan));
++ timeSpin-setPaletteBackgroundColor(QColor(cyan));
+ }
+ else
+ timeSpin-unsetPalette();
+@@ -539,7 +539,7 @@
+ if (byoTimeSpin-value() != val.toInt()/60)
+ {
+ byoTimeSpin-setValue(val.toInt()/60);
+- byoTimeSpin-setPaletteBackgroundColor(QColor::QColor(cyan));
++ byoTimeSpin-setPaletteBackgroundColor(QColor(cyan));
+ }
+ else
+ byoTimeSpin-unsetPalette();
+@@ -550,25 +550,25 @@
+ val = element(line,0, );
+ if ( !(play_nigiri_button-isChecked()) (val == N))
+ {
+- play_nigiri_button-setPaletteBackgroundColor(QColor::QColor(cyan));
+- play_white_button-setPaletteBackgroundColor(QColor::QColor(cyan));
+- play_black_button-setPaletteBackgroundColor(QColor::QColor(cyan));
++ play_nigiri_button-setPaletteBackgroundColor(QColor(cyan));
++ play_white_button-setPaletteBackgroundColor(QColor(cyan));
++ play_black_button-setPaletteBackgroundColor(QColor(cyan));
+ play_nigiri_button-setChecked(true);
+
+ }
+ else if ( (play_black_button-isChecked()) (val == B))
+ {
+- play_nigiri_button-setPaletteBackgroundColor(QColor::QColor(cyan));
+- play_white_button-setPaletteBackgroundColor(QColor::QColor(cyan));
+- play_black_button-setPaletteBackgroundColor(QColor::QColor(cyan));
++ play_nigiri_button-setPaletteBackgroundColor(QColor(cyan));
++ play_white_button-setPaletteBackgroundColor(QColor(cyan));
++ play_black_button-setPaletteBackgroundColor(QColor(cyan));
+ play_white_button-setChecked(true);
+
+ }
+ else if ( (play_white_button-isChecked()) (val == W))
+ {
+- play_nigiri_button-setPaletteBackgroundColor(QColor::QColor(cyan));
+- play_white_button-setPaletteBackgroundColor(QColor::QColor(cyan));
+- play_black_button-setPaletteBackgroundColor(QColor::QColor(cyan));
++ play_nigiri_button-setPaletteBackgroundColor(QColor(cyan));
++ play_white_button-setPaletteBackgroundColor(QColor(cyan));
++ play_black_button-setPaletteBackgroundColor(QColor(cyan));
+ play_black_button-setChecked(true);
+
+ }
+diff -urNad '--exclude=CVS' '--exclude=.svn' '--exclude=.git' '--exclude=.arch' '--exclude=.hg' '--exclude=_darcs' '--exclude=.bzr' qgo-1.5.4-r3~/src/mainwin.cpp qgo-1.5.4-r3/src/mainwin.cpp
+--- qgo-1.5.4-r3~/src/mainwin.cpp 2011-04-12 20:03:12.0 +0200
qgo-1.5.4-r3/src/mainwin.cpp 2011-04-12 20:03:15.640382627 +0200
+@@ -68,35 +68,35 @@
+ {
+
+
+- prefsIcon= QPixmap::QPixmap(qembed_findImage(package_settings));//QPixmap(ICON_PREFS);
++ prefsIcon=
Bug#639772: slrn: FTBFS: checking for the slang library and header files ... no
Source: slrn
Version: 1.0.0~pre18-1.1
Severity: serious
Justification: FTBFS
Tags: patch
Hi,
slrn FTBFS on latest unstable.
I confirmed on amd64/cowbuilder.
And you can see build log following.
armhf:
http://buildd.debian-ports.org/status/fetch.php?pkg=slrnarch=armhfver=1.0.0%7Epre18-1.1%2Bb2stamp=1314291701
sh4:
http://buildd.debian-ports.org/status/fetch.php?pkg=slrnarch=sh4ver=1.0.0%7Epre18-1.1%2Bb1stamp=1314321508
-
checking for an implementation of va_copy()... yes
checking for an implementation of __va_copy()... yes
checking whether va_lists can be copied by value... no
checking for ncurses5-config... /usr/bin/ncurses5-config
checking for terminfo... yes
checking for the slang library and header files ... no
configure: error: unable to find the slang library and header file slang.h
This file contains any messages produced by compilers while
running configure, to aid debugging if configure makes a mistake.
-
I attached full log.
Could you check your packge?
Best regards,
Nobuhiro
--
Nobuhiro Iwamatsu
iwamatsu at {nigauri.org / debian.org}
GPG ID: 40AD1FA6
slrn_1.0.0~pre18-1.1_amd64.build.gz
Description: GNU Zip compressed data
Bug#639733: wordpress: Wordpress breaks TinyMCE install
tags 639733 moreinfo unreproducible thanks Hi, On 08/29/2011 08:43 PM, Laurens Blankers wrote: Upgrading from 3.0.5+dfsg-1 to 3.2.1+dfsg-1 causes plugin files to be written to /usr/share/tinymce which is partily symlinked from /usr/share/wordpress/wp-includes/js/tinymce/ this in turns causes TinyMCE to BREAK on Firefox 6 and Chrome 13. Which in turn breaks applications such as Roundcube hence the critical severity. Wordpress should NEVER write files in another packages directory! The only way to fix this is to force the removal of tinymce manually delete the directory and then reinstall tinymce. I can't reproduce this, could you show me which plugins are written in /usr/share/tinymce please? Cheers, Giuseppe. signature.asc Description: OpenPGP digital signature
Processed: Re: Bug#639733: wordpress: Wordpress breaks TinyMCE install
Processing commands for cont...@bugs.debian.org: tags 639733 moreinfo unreproducible Bug #639733 [wordpress] wordpress: Wordpress breaks TinyMCE install Added tag(s) unreproducible and moreinfo. thanks Stopping processing here. Please contact me if you need assistance. -- 639733: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=639733 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#638294: Blocked upgrade of libdap11
On Fri, Aug 26, 2011 at 08:08:06PM +0200, Julien Cristau wrote: On Fri, Aug 26, 2011 at 11:43:10 +0100, Alastair McKinstry wrote: Hi, I have an experimental libdap11 package to fix this in Experimental. Can the release team please review this ? Package: libdap11 Conflicts: libdap10 Breaks: libdap10 Replaces: libdap10 Why? None of this seems necessary unless I'm missing something. Package: libdapclient3 Conflicts: libdap10 I think this should have Replaces (and possibly Breaks instead of Conflicts). Same with libdapserver7. Cheers, Julien So what? Some reverse build-deps like gdal are still waiting in the dark for a rebuild ... -- Francesco P. Lovergine -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#638294: Blocked upgrade of libdap11
On Tue, Aug 30, 2011 at 11:37:31 +0200, Francesco P. Lovergine wrote: On Fri, Aug 26, 2011 at 08:08:06PM +0200, Julien Cristau wrote: On Fri, Aug 26, 2011 at 11:43:10 +0100, Alastair McKinstry wrote: Hi, I have an experimental libdap11 package to fix this in Experimental. Can the release team please review this ? Package: libdap11 Conflicts: libdap10 Breaks: libdap10 Replaces: libdap10 Why? None of this seems necessary unless I'm missing something. Package: libdapclient3 Conflicts: libdap10 I think this should have Replaces (and possibly Breaks instead of Conflicts). Same with libdapserver7. Cheers, Julien So what? Some reverse build-deps like gdal are still waiting in the dark for a rebuild ... Last I checked the API change in new libdap makes gdal 1.7 unbuildable anyway, so that will need a source upload. Cheers, Julien -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#638294: Blocked upgrade of libdap11
On Tue, Aug 30, 2011 at 11:39:40AM +0200, Julien Cristau wrote: So what? Some reverse build-deps like gdal are still waiting in the dark for a rebuild ... Last I checked the API change in new libdap makes gdal 1.7 unbuildable anyway, so that will need a source upload. Thanks, let me check about that. Alastair, should I consider the current libdap version in unstable or the experimental one to prepare a fix? -- Francesco P. Lovergine -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#636883: Updated package on mentors.debian.net
Hello, I have prepared a QA upload that addresses this issue. The package can be found on mentors.debian.net: http://mentors.debian.net/package/cvsconnect It can be downloaded using dget: dget -x http://mentors.debian.net/debian/pool/main/c/cvsconnect/cvsconnect_0.1.cvs20001202-2.dsc I have sent a request for sponsorship to the debian-mentors mailing list. Regards, -- Jeroen Schot -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#618135: fslview: uninstallable in sid
On Tue, Aug 30, 2011 at 01:13:21AM +0100, Colin Watson wrote: On Tue, Jun 07, 2011 at 03:05:33PM -0400, Michael Hanke wrote: On Tue, Jun 07, 2011 at 08:43:15PM +0200, Ralf Treinen wrote: This bug (#618135) makes fslview also uninstallable in sid, on any architecture, since: fslview (= 3.1.8+4.1.6-2) depends on missing: - libvtk5.4 Upstream informed me that a qt4 port is about to become available. This will also finally make qwt4 packages in Debian obsolete (libqwt4c2, libqwt-dev). I hope, a 618135-close is only days away... Is there any news on this? It's been quite a few days. :-) I wish there would be. It will come, but any ETA prediction I got so far turned out to be wrong. At this point there is little I can do. Sorry, Michael -- Michael Hanke http://mih.voxindeserto.de -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#629787: marked as done (wiipdf: FTBFS: build-dependency not installable: libcwiid1-dev)
Your message dated Tue, 30 Aug 2011 10:47:46 + with message-id e1qylr8-dq...@franck.debian.org and subject line Bug#629787: fixed in wiipdf 1.4-2 has caused the Debian Bug report #629787, regarding wiipdf: FTBFS: build-dependency not installable: libcwiid1-dev to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 629787: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=629787 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Source: wiipdf Version: 1.4-1 Severity: serious Tags: wheezy sid User: debian...@lists.debian.org Usertags: qa-ftbfs-20110607 qa-ftbfs Justification: FTBFS on amd64 Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part: ┌──┐ │ Install wiipdf build dependencies (apt-based resolver) │ └──┘ Installing build dependencies Reading package lists... Building dependency tree... Reading state information... Some packages could not be installed. This may mean that you have requested an impossible situation or if you are using the unstable distribution that some required packages have not yet been created or been moved out of Incoming. The following information may help to resolve the situation: The following packages have unmet dependencies: sbuild-build-depends-wiipdf-dummy : Depends: libcwiid1-dev but it is not installable E: Broken packages The full build log is available from: http://people.debian.org/~lucas/logs/2011/06/07/wiipdf_1.4-1_lsid64.buildlog A list of current common problems and possible solutions is available at http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute! About the archive rebuild: The rebuild was done on about 50 AMD64 nodes of the Grid'5000 platform, using a clean chroot. Internet was not accessible from the build systems. -- | Lucas Nussbaum | lu...@lucas-nussbaum.net http://www.lucas-nussbaum.net/ | | jabber: lu...@nussbaum.fr GPG: 1024D/023B3F4F | ---End Message--- ---BeginMessage--- Source: wiipdf Source-Version: 1.4-2 We believe that the bug you reported is fixed in the latest version of wiipdf, which is due to be installed in the Debian FTP archive: wiipdf_1.4-2.diff.gz to main/w/wiipdf/wiipdf_1.4-2.diff.gz wiipdf_1.4-2.dsc to main/w/wiipdf/wiipdf_1.4-2.dsc wiipdf_1.4-2_amd64.deb to main/w/wiipdf/wiipdf_1.4-2_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 629...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Michael Stapelberg mich...@stapelberg.de (supplier of updated wiipdf package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Tue, 30 Aug 2011 12:23:45 +0200 Source: wiipdf Binary: wiipdf Architecture: source amd64 Version: 1.4-2 Distribution: unstable Urgency: low Maintainer: Michael Stapelberg mich...@stapelberg.de Changed-By: Michael Stapelberg mich...@stapelberg.de Description: wiipdf - present a PDF file using your wiimote Closes: 629787 Changes: wiipdf (1.4-2) unstable; urgency=low . * Fix FTBFS by changing libcwiid1-dev to libcwiid-dev (Closes: #629787) * Bump standards version to 3.9.2 Checksums-Sha1: 1a604f0645c68ffebb5a7935122601c52545a769 1646 wiipdf_1.4-2.dsc 0a0637a444637e041316a4367592cfc8cab0a03d 2897 wiipdf_1.4.orig.tar.gz 4e12e9c10b207a68f27167e4010b2c8ae381deee 2806 wiipdf_1.4-2.diff.gz 60428a62e52ba09d1f02ae8179ca04af92c02088 6922 wiipdf_1.4-2_amd64.deb Checksums-Sha256: 47e14e95ad2c4b2d0fb3b502ec86af8d721a2ca3ae4da3fc6a2a556a1c6bc497 1646 wiipdf_1.4-2.dsc 67b8ae0ade5a2f81721a055c04d07990faad86f7131a6fa1af85f8e954363556 2897 wiipdf_1.4.orig.tar.gz d5581a78c4ece4ad0a4bce41346020bd0b182b57e83ca7d6772c1cd7a10a3e4c 2806 wiipdf_1.4-2.diff.gz 98d8112215c5b6b581f3961937d59d9856285887cc4090dc28e91859c7d27811 6922 wiipdf_1.4-2_amd64.deb Files: 967881087cb6937d7c88a290b8124a60 1646 utils optional wiipdf_1.4-2.dsc 836a11479cd90538df86955c1e5323c5 2897 utils optional wiipdf_1.4.orig.tar.gz 1637ab426a2f1eb96bb414d7b3a9fafe 2806 utils optional wiipdf_1.4-2.diff.gz
Processed: forcibly merging 583273 583275
Processing commands for cont...@bugs.debian.org: forcemerge 583273 583275 Bug#583273: flegita: Crashes on startup Bug#583275: flegita: segfaults while/after detecting devices Forcibly Merged 583273 583275. thanks Stopping processing here. Please contact me if you need assistance. -- 583275: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=583275 583273: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=583273 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#593139: ruby1.9.1 hangs again
Would you have time to turn that into a (tested ;) ) patch?
With attached patch on top of 1.9.3~preview1+svn33077-3
make test
#244 test_fork.rb:51:in `top (required)':
a = []
trap(:INT) { a.push(1) }
trap(:TERM) { a.push(2) }
pid = $$
begin
fork do
sleep 0.5
Process.kill(:INT, pid)
Process.kill(:TERM, pid)
end
sleep 1
a.sort
rescue NotImplementedError
[1, 2]
end
#= [] (expected [1, 2]) [ruby-dev:44005] [Ruby 1.9 - Bug #4950]
#934 test_thread.rb:389:in `top (required)':
open(zzz.rb, w) do |f|
f.puts -END
begin
m = Mutex.new
Thread.new { m.lock; sleep 1 }
sleep 0.3
parent = Thread.current
Thread.new do
sleep 0.3
begin
fork { GC.start }
rescue Exception
parent.raise $!
end
end
m.lock
pid, status = Process.wait2
$result = status.success? ? :ok : :ng
rescue NotImplementedError
$result = :ok
end
END
end
require ./zzz.rb
$result
#= (expected ok)
FAIL 2/937 tests failed
make: *** [yes-btest-ruby] Error 1
--- ruby1.9.1-1.9.3~preview1+svn33077.orig/thread_pthread.c
+++ ruby1.9.1-1.9.3~preview1+svn33077/thread_pthread.c
@@ -1045,6 +1045,36 @@ static pthread_t timer_thread_id;
static int timer_thread_pipe[2] = {-1, -1};
static int timer_thread_pipe_owner_process;
+#if 0
+static inline int
+timer_thread_running() {
+ return timer_thread_pipe_owner_process == getpid() ? 1 : 0;
+}
+
+static inline void timer_thread_set() {
+timer_thread_pipe_owner_process = getpid();
+}
+
+RUBY_FUNC_EXPORTED
+void timer_thread_child_at_fork() {
+};
+
+#else
+static inline int
+timer_thread_running() {
+ return timer_thread_pipe_owner_process;
+}
+
+static inline void timer_thread_set() {
+timer_thread_pipe_owner_process = 1;
+}
+
+RUBY_FUNC_EXPORTED
+void timer_thread_child_at_fork() {
+timer_thread_pipe_owner_process = 0;
+};
+#endif
+
#define TT_DEBUG 0
#define WRITE_CONST(fd, str) (void)(write((fd),(str),sizeof(str)-1)0)
@@ -1056,7 +1086,7 @@ rb_thread_wakeup_timer_thread(void)
ssize_t result;
/* already opened */
-if (timer_thread_pipe_owner_process == getpid()) {
+if (timer_thread_running()) {
const char *buff = !;
retry:
if ((result = write(timer_thread_pipe[1], buff, 1)) = 0) {
@@ -1199,7 +1229,7 @@ rb_thread_create_timer_thread(void)
#endif
/* communication pipe with timer thread and signal handler */
- if (timer_thread_pipe_owner_process != getpid()) {
+ if (!timer_thread_running()) {
if (timer_thread_pipe[0] != -1) {
/* close pipe of parent process */
close_communication_pipe();
@@ -1229,7 +1259,7 @@ rb_thread_create_timer_thread(void)
#endif /* defined(HAVE_FCNTL) defined(F_GETFL) defined(F_SETFL) */
/* validate pipe on this process */
- timer_thread_pipe_owner_process = getpid();
+ timer_thread_set();
}
/* create timer thread */
--- ruby1.9.1-1.9.3~preview1+svn33077.orig/main.c
+++ ruby1.9.1-1.9.3~preview1+svn33077/main.c
@@ -21,6 +22,8 @@
RUBY_GLOBAL_SETUP
+extern void timer_thread_child_at_fork();
+
int
main(int argc, char **argv)
{
@@ -31,6 +34,10 @@ main(int argc, char **argv)
setlocale(LC_CTYPE, );
#endif
+#if 1
+pthread_atfork(NULL, NULL, timer_thread_child_at_fork);
+#endif
+
ruby_sysinit(argc, argv);
{
RUBY_INIT_STACK;
Bug#639778: conky requires packages outside main for compilation (was: Re: conky rejected from backports)
Hi! * Aron Xu a...@debian.org [2011-08-30 13:14:59 CEST]: Sorry, I am on vacation, but I can be online sometimes... I didn't see where is your bug report on BTS, I think it would be better to roll in ftp-masters to the discussions then, so they have a chance to explain why it was accepted, and why buildds enable contrib by default even if building main packages. Because ftp masters are only human too, and can make mistakes. Given that there is no log of the discussion that dererk had with the unnamed ftpmaster, this is very unfortunate, but mistakes happen. That doesn't mean that this it was rightfully granted, and the policy is crystal clear on this, like Vincent Bernat quoted already in bugreport 579102 in message #129, and like I quoted again with the opening of 639778. I don't see any need for bringing in any ftp master for explaining a clear statement from the policy that packages in main aren't allowed to build-depend on packages outside of main. Thanks, Rhonda -- Fühlst du dich mutlos, fass endlich Mut, los | Fühlst du dich hilflos, geh raus und hilf, los| Wir sind Helden Fühlst du dich machtlos, geh raus und mach, los | 23.55: Alles auf Anfang Fühlst du dich haltlos, such Halt und lass los| -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#638002: Fixed upstream in 0.2.30
tags 638002 fixed-upstream thanks The bug had been fixed in version 0.2.30. The relevant changeset is: http://hg.marmaro.de/masqmail/rev/e507c854a63e meillo -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed: Fixed upstream in 0.2.30
Processing commands for cont...@bugs.debian.org: tags 638002 fixed-upstream Bug #638002 [masqmail] Improper seteuid() calls in src/log.c and src/masqmail.c Added tag(s) fixed-upstream. thanks Stopping processing here. Please contact me if you need assistance. -- 638002: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=638002 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#639778: conky requires packages outside main for compilation (was: Re: conky rejected from backports)
On Tue, Aug 30, 2011 at 19:45, Gerfried Fuchs rho...@debian.org wrote: Hi! * Aron Xu a...@debian.org [2011-08-30 13:14:59 CEST]: Sorry, I am on vacation, but I can be online sometimes... I didn't see where is your bug report on BTS, I think it would be better to roll in ftp-masters to the discussions then, so they have a chance to explain why it was accepted, and why buildds enable contrib by default even if building main packages. Because ftp masters are only human too, and can make mistakes. Given that there is no log of the discussion that dererk had with the unnamed ftpmaster, this is very unfortunate, but mistakes happen. Yes, I agree they are only human, but I think we need to know why they do this, if they are exactly wrong (according to the Policy, they are definitely wrong) we need to help them avoid similar problems in the future. That doesn't mean that this it was rightfully granted, and the policy is crystal clear on this, like Vincent Bernat quoted already in bugreport 579102 in message #129, and like I quoted again with the opening of 639778. I don't see any need for bringing in any ftp master for explaining a clear statement from the policy that packages in main aren't allowed to build-depend on packages outside of main. As commented above, we don't need them to interpret or explain Policy, but at least I myself want them to explain why they chose to accept packages like this, and why the buildds have contrib enabled by default for main packages. -- Regards, Aron Xu -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#639801: postgresql-filedump-8.4 and postgresql-filedump: error when trying to install together
Package: postgresql-filedump,postgresql-filedump-8.4 Version: postgresql-filedump/9.0.0-1 Version: postgresql-filedump-8.4/8.4.0-1 Severity: serious User: trei...@debian.org Usertags: edos-file-overwrite Date: 2011-08-30 Architecture: amd64 Distribution: sid Hi, automatic installation tests of packages that share a file and at the same time do not conflict by their package dependency relationships has detected the following problem: WARNING: The following packages cannot be authenticated! postgresql-filedump postgresql-filedump-8.4 Authentication warning overridden. Can not write log, openpty() failed (/dev/pts not mounted?) Selecting previously deselected package postgresql-filedump. (Reading database ... 10663 files and directories currently installed.) Unpacking postgresql-filedump (from .../postgresql-filedump_9.0.0-1_amd64.deb) ... Selecting previously deselected package postgresql-filedump-8.4. Unpacking postgresql-filedump-8.4 (from .../postgresql-filedump-8.4_8.4.0-1_amd64.deb) ... dpkg: error processing /var/cache/apt/archives/postgresql-filedump-8.4_8.4.0-1_amd64.deb (--unpack): trying to overwrite '/usr/lib/postgresql/8.4/bin/pg_filedump', which is also in package postgresql-filedump 9.0.0-1 configured to not write apport reports Errors were encountered while processing: /var/cache/apt/archives/postgresql-filedump-8.4_8.4.0-1_amd64.deb E: Sub-process /usr/bin/dpkg returned an error code (1) This is a serious bug as it makes installation fail, and violates sections 7.6.1 and 10.1 of the policy. An optimal solution would consist in only one of the packages installing that file, and renaming or removing the file in the other package. Depending on the circumstances you might also consider Replace relations or file diversions. If the conflicting situation cannot be resolved then, as a last resort, the two packages have to declare a mutual Conflict. Please take into account that Replaces, Conflicts and diversions should only be used when packages provide different implementations for the same functionality. Here is a list of files that are known to be shared by both packages (according to the Contents file for sid/amd64, which may be slightly out of sync): /usr/lib/postgresql/8.4/bin/pg_filedump This bug is assigned to both packages. If you, the maintainers of the two packages in question, have agreed on which of the packages will resolve the problem please reassign the bug to that package. You may also register in the BTS that the other package is affected by the bug. -Ralf. PS: for more information about the detection of file overwrite errors of this kind see http://edos.debian.net/file-overwrites/. -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed: severity of 638936 is important
Processing commands for cont...@bugs.debian.org: severity 638936 important Bug #638936 [evolution] evolution hangs after upgrade Severity set to 'important' from 'serious' thanks Stopping processing here. Please contact me if you need assistance. -- 638936: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=638936 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#639778: conky requires packages outside main for compilation (was: Re: conky rejected from backports)
Hi again. * Aron Xu a...@debian.org [2011-08-30 13:51:26 CEST]: On Tue, Aug 30, 2011 at 19:45, Gerfried Fuchs rho...@debian.org wrote: Because ftp masters are only human too, and can make mistakes. Given that there is no log of the discussion that dererk had with the unnamed ftpmaster, this is very unfortunate, but mistakes happen. Yes, I agree they are only human, but I think we need to know why they do this, if they are exactly wrong (according to the Policy, they are definitely wrong) we need to help them avoid similar problems in the future. If we would be able to explain why we do mistakes the world could be a much better place indeed! Unfortunately I fear that the ftpmasters aren't any better at explaining why they do mistakes than anyone else. As commented above, we don't need them to interpret or explain Policy, Thanks, so it's clear that conky has to return to contrib it seems. Thanks for the agreement on that grounds. but at least I myself want them to explain why they chose to accept packages like this, and why the buildds have contrib enabled by default for main packages. See above, explaining mistakes would solve much more than this issue for mankind. E.g. I don't ask for an explenation for why there is a Changed-By: foo...@debian.org entry in one of the conky upload changes files because it doesn't change anything. Sending them a notification though does help (and you can be assured that I discussed it with parts of the ftp team). And the buildds seem to have contrib enabled because there are some corner cases where contrib packages do not depend on non-free software (like in the case of conky) for compiling and thus can be automatically built. I think a seperation of this into different chroots might make sense, on the other hand, that's out of scope for this ticket and should be discussed with the buildd admins. The scope of this bugreport should be getting the policy violation fixed, not for general conceptual mistakes that happen in completely different areas, so please keep it related to the bugreport, or move further discussions along that lines to a more suiting place. My intention is to get conky in a releaseable shape again, which it currently because of this issue isn't. Thanks, Rhonda -- Fühlst du dich mutlos, fass endlich Mut, los | Fühlst du dich hilflos, geh raus und hilf, los| Wir sind Helden Fühlst du dich machtlos, geh raus und mach, los | 23.55: Alles auf Anfang Fühlst du dich haltlos, such Halt und lass los| -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#633789: marked as done (guake: Guake doesnt start at all)
Your message dated Tue, 30 Aug 2011 12:32:14 + with message-id e1qynue-0004lw...@franck.debian.org and subject line Bug#633789: fixed in guake 0.4.2-6 has caused the Debian Bug report #633789, regarding guake: Guake doesnt start at all 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.) -- 633789: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=633789 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: guake Version: 0.4.2-5 Justification: renders package unusable Severity: grave Hi everyone, There is a problem with my version of guake, i get this issue : Traceback (most recent call last): File /usr/lib/guake/guake.py, line 1353, in module if not main(): File /usr/lib/guake/guake.py, line 1296, in main instance = Guake() File /usr/lib/guake/guake.py, line 649, in __init__ notification.show() glib.GError: Unable to connect to server According this topic ( https://bbs.archlinux.org/viewtopic.php?pid=856702 ), the problem comes of the version of libnotify when it is greater than 5. However, there is only the v5 version of libnotify, even in the stable tree of Debian. If you want more informations, don't hesitate to contact me. Bests, Eloi -- System Information: Debian Release: wheezy/sid APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'lucid'), (500, 'unstable'), (500, 'stable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 3.0.0-rc6-amd64 (SMP w/4 CPU cores) Locale: LANG=fr_FR.utf8, LC_CTYPE=fr_FR.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages guake depends on: ii gconf22.32.4-1 GNOME configuration database syste ii libatk1.0-0 2.0.1-2ATK accessibility toolkit ii libc6 2.13-10Embedded GNU C Library: Shared lib ii libcairo2 1.10.2-6 The Cairo 2D vector graphics libra ii libfontconfig12.8.0-3generic font configuration library ii libfreetype6 2.4.4-2FreeType 2 font engine, shared lib ii libgdk-pixbuf2.0-02.23.5-1 GDK Pixbuf library ii libglib2.0-0 2.28.6-1 The GLib library of C routines ii libgtk2.0-0 2.24.4-3 The GTK+ graphical user interface ii libpango1.0-0 1.28.4-1 Layout and rendering of internatio ii libpython2.6 2.6.7-3Shared Python runtime library (ver ii libx11-6 2:1.4.3-2 X11 client-side library ii notification-daemon 0.5.0-3daemon to displays passive pop-up ii python2.6.7-1interactive high-level object-orie ii python-dbus 0.84.0-1 simple interprocess messaging syst ii python-gconf 2.28.1-3 Python bindings for the GConf conf ii python-glade2 2.24.0-2 GTK+ bindings: Glade support ii python-notify 0.1.1-2+b3 Python bindings for libnotify ii python-vte1:0.28.1-2 Python bindings for the VTE widget guake recommends no packages. guake suggests no packages. -- no debconf information ---End Message--- ---BeginMessage--- Source: guake Source-Version: 0.4.2-6 We believe that the bug you reported is fixed in the latest version of guake, which is due to be installed in the Debian FTP archive: guake_0.4.2-6.debian.tar.gz to main/g/guake/guake_0.4.2-6.debian.tar.gz guake_0.4.2-6.dsc to main/g/guake/guake_0.4.2-6.dsc guake_0.4.2-6_i386.deb to main/g/guake/guake_0.4.2-6_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 633...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Sylvestre Ledru sylves...@debian.org (supplier of updated guake 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: Tue, 30 Aug 2011 13:54:50 +0200 Source: guake Binary: guake Architecture: source i386 Version: 0.4.2-6 Distribution: unstable Urgency: low Maintainer: Sylvestre Ledru sylves...@debian.org Changed-By: Sylvestre Ledru sylves...@debian.org Description: guake - Drop-down terminal for GNOME Desktop Environment Closes: 633789 Changes: guake (0.4.2-6) unstable;
Bug#639560: marked as done (symbol changes)
Your message dated Tue, 30 Aug 2011 13:17:23 + with message-id e1qyobv-fv...@franck.debian.org and subject line Bug#639560: fixed in libast 0.7-6 has caused the Debian Bug report #639560, regarding symbol changes 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.) -- 639560: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=639560 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: libast Version: 0.7-5 Severity: serious The package FTBFS'es on mips, powerpc, s390, sparc and the inofficial ports s390x and powerpcspe because of changes in the symbol set wrt the symbols file: --- debian/libast2.symbols (libast2_0.7-5_mips) +++ dpkg-gensymbolsqBZbvb 2011-08-26 17:23:07.0 + @@ -286,7 +286,7 @@ spifhash_fnv@Base 0.7 spifhash_jenkins32@Base 0.7 spifhash_jenkins@Base 0.7 - spifhash_jenkinsLE@Base 0.7 +#MISSING: 0.7-5# spifhash_jenkinsLE@Base 0.7 spifhash_one_at_a_time@Base 0.7 spifhash_rotating@Base 0.7 spifmem_calloc@Base 0.7 @@ -314,6 +314,8 @@ spiftool_hex_dump@Base 0.7 spiftool_join@Base 0.7 spiftool_num_words@Base 0.7 + spiftool_regexp_match@Base 0.7-5 + spiftool_regexp_match_r@Base 0.7-5 spiftool_safe_str@Base 0.7 spiftool_safe_strncat@Base 0.7 spiftool_safe_strncpy@Base 0.7 dh_makeshlibs: dpkg-gensymbols -plibast2 -Idebian/libast2.symbols -Pdebian/libast2 -edebian/libast2/usr/lib/mips-linux-gnu/libast.so.2.0.1 ---End Message--- ---BeginMessage--- Source: libast Source-Version: 0.7-6 We believe that the bug you reported is fixed in the latest version of libast, which is due to be installed in the Debian FTP archive: libast2-dev_0.7-6_amd64.deb to main/liba/libast/libast2-dev_0.7-6_amd64.deb libast2_0.7-6_amd64.deb to main/liba/libast/libast2_0.7-6_amd64.deb libast_0.7-6.debian.tar.gz to main/liba/libast/libast_0.7-6.debian.tar.gz libast_0.7-6.dsc to main/liba/libast/libast_0.7-6.dsc 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 639...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Regis Boudin re...@debian.org (supplier of updated libast 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: Tue, 30 Aug 2011 13:55:36 +0100 Source: libast Binary: libast2 libast2-dev Architecture: source amd64 Version: 0.7-6 Distribution: unstable Urgency: low Maintainer: Debian QA Group packa...@qa.debian.org Changed-By: Regis Boudin re...@debian.org Description: libast2- Library of Assorted Spiffy Things libast2-dev - libast2 development files Closes: 639560 Changes: libast (0.7-6) unstable; urgency=low . * QA upload. * Pass --with-regexp=posix to have have a consistent build with the spiftool_regexp_match and spiftool_regexp_match_r symbols exported. * Stop shipping libast2.symbols for now, as the symbols list is not consistent between little and big endian architectures, and there is no official way to deal with it yet. Closes: #639560. Checksums-Sha1: 545e17baa99dcb07010f7ca7d5e54e3836e7dfb5 1071 libast_0.7-6.dsc 545bf1ee76c30629874f2efed2d3f368c22bb81c 4527 libast_0.7-6.debian.tar.gz 0fa966eadc9f4c68cd60f3738f77087bd11a7c9c 101782 libast2_0.7-6_amd64.deb 6f5185946ce582aa0ca8037e298b2583ea32b3aa 174764 libast2-dev_0.7-6_amd64.deb Checksums-Sha256: 9998fe499d42eef477ae32ebc62562c7f553b7ab659f9bec0d114eabdca6d91d 1071 libast_0.7-6.dsc 5d7296eef2d812de3d69e3a0f6ec80866678821c189ef4f805490aa9d1f01cf0 4527 libast_0.7-6.debian.tar.gz e15636cdd66c9a4f06bf09a0211ba36761be4806b31e42c93e2a18c457e6e8eb 101782 libast2_0.7-6_amd64.deb 6b53b445c1ad9a24213c6b179793d2d7b36a2f332defd7da2ee5a8bd76febb93 174764 libast2-dev_0.7-6_amd64.deb Files: 2cd1a7030c17ef410b1e61713e4273b0 1071 libs optional libast_0.7-6.dsc 75bc9ede735661bd0ffb8494db6efa8b 4527 libs optional libast_0.7-6.debian.tar.gz 93707f7aaa61e5a61ef03103b5d5abef 101782 libs optional libast2_0.7-6_amd64.deb 68556105c66e907e125f71304b4836c9 174764 libdevel optional libast2-dev_0.7-6_amd64.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.11 (GNU/Linux) iEYEARECAAYFAk5c4GUACgkQVE17sLEtWVrR3QCg1zlcpM4T38/LBHTdOHrOpXZa atkAoMGnqNpn66fWtZeT92EeGWhN2xX9 =mZWw -END PGP SIGNATURE- ---End Message---
Bug#639801: postgresql-filedump-8.4 and postgresql-filedump: error when trying to install together
Removal request for postgresql-filedump-8.4 is already filed. Michael -- Michael Meskes Michael at Fam-Meskes dot De, Michael at Meskes dot (De|Com|Net|Org) Michael at BorussiaFan dot De, Meskes at (Debian|Postgresql) dot Org Jabber: michael.meskes at googlemail dot com VfL Borussia! Força Barça! Go SF 49ers! Use Debian GNU/Linux, PostgreSQL -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#593139: ruby1.9.1 hangs again
On 30/08/11 at 13:52 +0200, Petr Salinger wrote:
Would you have time to turn that into a (tested ;) ) patch?
With attached patch on top of 1.9.3~preview1+svn33077-3
make test
Thanks!
Could you try make test-all ? While some failures and errors are
expected, it stresses the interpreter a bit more, so it's a good way to
check that it doesn't block.
#244 test_fork.rb:51:in `top (required)':
a = []
trap(:INT) { a.push(1) }
trap(:TERM) { a.push(2) }
pid = $$
begin
fork do
sleep 0.5
Process.kill(:INT, pid)
Process.kill(:TERM, pid)
end
sleep 1
a.sort
rescue NotImplementedError
[1, 2]
end
#= [] (expected [1, 2]) [ruby-dev:44005] [Ruby 1.9 - Bug #4950]
Err. This is fairly simple, and should not fail.
Could you try this version:
---
a = []
trap(:INT) { puts INT recvd ; a.push(1) }
trap(:TERM) { puts TERM recvd ; a.push(2) }
pid = $$
puts parent pid: #{pid}
begin
fork do
puts child pid: #{$$}
sleep 0.5
Process.kill(:INT, pid)
Process.kill(:TERM, pid)
puts signals sent.
end
sleep 1
a.sort
p a
rescue NotImplementedError
[1, 2]
end
#934 test_thread.rb:389:in `top (required)':
open(zzz.rb, w) do |f|
f.puts -END
begin
m = Mutex.new
Thread.new { m.lock; sleep 1 }
sleep 0.3
parent = Thread.current
Thread.new do
sleep 0.3
begin
fork { GC.start }
rescue Exception
parent.raise $!
end
end
m.lock
pid, status = Process.wait2
$result = status.success? ? :ok : :ng
rescue NotImplementedError
$result = :ok
end
END
end
require ./zzz.rb
$result
#= (expected ok)
FAIL 2/937 tests failed
make: *** [yes-btest-ruby] Error 1
Very strange. What about this script?
--
m = Mutex.new
Thread.new { m.lock; sleep 3 ; puts after m.lock in thread }
sleep 1
m.lock
puts after m.lock
--
Lucas
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#635126: status of ruby 1.9.1 wrt porting
On Mon, Aug 29, 2011 at 11:48:34PM +0200, Lucas Nussbaum wrote: Ruby 1.9.3 is going to be released in september, and is a candidate for the default ruby version in wheezy. A snapshot is available in experimental. Now is an ideal time to work on porting issues and get the fixes integrated upstream. Ruby has a fairly large test suite, which makes finding problems easy, but exercises the threading library in interesting ways. Most of the issues are reproducible by re-building the Debian package. Use make make test to get a shorter build. Here is the current complete list of issues I'm aware of. My time will be very limited in the coming weeks, but I will try my best to provide help. [armel,sparc] FTBFS due to miscompilation with -ftree-sra (inc. in -O3). See http://bugs.debian.org/635126. Currently worked-around by using -fno-tree-sra. Other packages might be affected. - FIXED from ruby1.9.1's POV, but you really want to look at this for other packages. [armel] I've just seen that now that this one is fixed, the test suite segfaults. See https://buildd.debian.org/status/fetch.php?pkg=ruby1.9.1arch=armelver=1.9.3~preview1%2Bsvn33077-1stamp=1314634969 search for 'TestFiber#test_many_fibers'. 'make test-all' to reproduce. Failures during test-all are currently not fatal. The remaining ones needs more investigation, but I don't think that they are arch-specific. I'd like to make test-all failures fatal at some point. Building on armhf seemed to go fine, and running some of the examples looked good too. -- Len Sorensen -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#620550: Please advice about symbols versioning (was Re: How to close bug #620550?
On Sat, Aug 13, 2011 at 11:57 PM, Satoru KURASHIKI wrote: I guess there is no PHP code which using GDBM code. If there is, they had falled into troubles after php switched to link from gdbm to qdbm, because PHP source package also doesn't include hovel.h. I think that I should care the people who has been using qdbm and gdbm interface for their published/non-published programs. (provide alternative package, only notice, and so on..) On Thu, 25 Aug 2011 21:55:13 +0900, Satoru KURASHIKI wrote: I've just uploaded updated qdbm package to mentors.debian.net, and asked for its review to my sponsor. (I simply drop symbols, and don't touch its versions.) I'm glad if you try this package to check it (will solve the problem). I just built the package from the git source on mentors.debian.net, installed it on the server we first encountered the problem on and our mod_perl code that uses GDBM is working fine now. Thanks for your attention to this bug. Keith. -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed: reassign 639004 to bzr
Processing commands for cont...@bugs.debian.org: reassign 639004 bzr Bug #639004 [src:trac-bzr] trac-bzr: FTBFS: tests fail Bug reassigned from package 'src:trac-bzr' to 'bzr'. Bug No longer marked as found in versions trac-bzr/0.4.2+bzr117-2. thanks Stopping processing here. Please contact me if you need assistance. -- 639004: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=639004 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#618477: munin-graph: undefined symbol g_slice_alloc
tags 618477 + unreproducable moreinfo severity 618477 normal Hi Zsolt, your bug report is very tense, please provide more information! Also I've never seen an undefined symbol g_slice_alloc error with munin on lenny... On Dienstag, 15. März 2011, Zsolt Tovis wrote: Versions of packages munin depends on: ii adduser 3.110 add and remove users and groups pn libdigest-md5-perl none (no description available) ii libhtml-template-perl2.9-1 HTML::Template : A module for usin ii librrds-perl 1.3.1-4 Time-series data storage and displ pn libstorable-perl none (no description available) ii perl [libtime-hires-perl 5.10.0-19lenny3 Larry Wall's Practical Extraction ii perl-modules 5.10.0-19lenny3 Core Perl modules ii rrdtool 1.3.1-4 Time-series data storage and displ why did you purge libdigest-md5-perl and libstorable-perl ? Can you try installing them again..?! /usr/bin/perl: symbol lookup error: /usr/lib/libpango-1.0.so.0: undefined symbol: g_slice_alloc are you using any backports or versions from squeeze on that system? apt-show-versions should help you to find out. cheers, Holger -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed (with 6 errors): Re: Bug#618477: munin-graph: undefined symbol g_slice_alloc
Processing commands for cont...@bugs.debian.org: tags 618477 + unreproducable moreinfo Unknown tag/s: unreproducable. Recognized are: patch wontfix moreinfo unreproducible fixed potato woody sid help security upstream pending sarge sarge-ignore experimental d-i confirmed ipv6 lfs fixed-in-experimental fixed-upstream l10n etch etch-ignore lenny lenny-ignore squeeze squeeze-ignore wheezy wheezy-ignore. Bug #618477 [munin] munin-graph: undefined symbol g_slice_alloc Added tag(s) moreinfo. severity 618477 normal Bug #618477 [munin] munin-graph: undefined symbol g_slice_alloc Severity set to 'normal' from 'critical' Hi Zsolt, Unknown command or malformed arguments to command. your bug report is very tense, please provide more information! Unknown command or malformed arguments to command. Also I've never seen an undefined symbol g_slice_alloc error with munin on Unknown command or malformed arguments to command. lenny... Unknown command or malformed arguments to command. On Dienstag, 15. März 2011, Zsolt Tovis wrote: Unknown command or malformed arguments to command. Too many unknown commands, stopping here. Please contact me if you need assistance. -- 618477: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=618477 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#638214: Fails to build from source: libqwt5-qt4-dev no longer exists
Thank you for the update. I spent a little while trying to port to qwt6, it's good to know qwt5 is still an option. I'll see if there's anything I can do about this ICE... -Adam On Mon, 2011-08-29 at 19:02 +0200, Moritz Mühlenhoff wrote: retitle 638214 FTBFS: ICE on amd64 thanks On Wed, Aug 17, 2011 at 08:29:26PM +0200, Moritz Muehlenhoff wrote: Package: elmer Severity: serious Hi, It's currently impossible to build elmerfem from source: dpkg-buildpackage: source package elmerfem dpkg-buildpackage: source version 6.1.0.svn.5272.dfsg-1 dpkg-buildpackage: source changed by Adam C. Powell, IV hazel...@debian.org dpkg-buildpackage: host architecture amd64 dpkg-source --before-build elmerfem-6.1.0.svn.5272.dfsg dpkg-checkbuilddeps: Unmet build dependencies: libqwt5-qt4-dev dpkg-buildpackage: warning: Build dependencies/conflicts unsatisfied; aborting. dpkg-buildpackage: warning: (Use -d flag to override.) libqwt5-qt4-dev no longer exists in the archive, switching to libqwt-dev isn't sufficient, I received the following error: libqwt5-qt4-dev has been restored by the libqwt maintainer, but I'm now running into an ICE with GCC 4.6: . -I/usr/include -DFULL_INDUCTION -DUSE_ARPACK -I/usr/include/mpi -DHAVE_MUMPS ExchangeCorrelations.src ExchangeCorrelations.f90 gfortran -I/home/jmm/deb/libav/elmerfem-6.1.0.svn.5272.dfsg/debian/tmp/usr/include -fPIC -m64 -fPIC -fPIC -I. -Ibinio -I/usr/include/mpi -I/usr/include -c ExchangeCorrelations.f90 gcc -DHAVE_CONFIG_H -I. -I.. -I/home/jmm/deb/libav/elmerfem-6.1.0.svn.5272.dfsg/debian/tmp/usr/include -I/usr/include/freetype2 -I/usr/include/mpi -g -O2 -I/home/jmm/deb/libav/elmerfem-6.1.0.svn.5272.dfsg/debian/tmp/usr/include -fPIC -m64 -fPIC -fPIC -I/usr/include -I/usr/include/mpi -MT SolveHypre.o -MD -MP -MF .deps/SolveHypre.Tpo -c -o SolveHypre.o SolveHypre.c mv -f .deps/SolveHypre.Tpo .deps/SolveHypre.Po gcc -DHAVE_CONFIG_H -I. -I.. -I/home/jmm/deb/libav/elmerfem-6.1.0.svn.5272.dfsg/debian/tmp/usr/include -I/usr/include/freetype2 -I/usr/include/mpi -g -O2 -I/home/jmm/deb/libav/elmerfem-6.1.0.svn.5272.dfsg/debian/tmp/usr/include -fPIC -m64 -fPIC -fPIC -I/usr/include -I/usr/include/mpi -MT SolveSuperLU.o -MD -MP -MF .deps/SolveSuperLU.Tpo -c -o SolveSuperLU.o SolveSuperLU.c mv -f .deps/SolveSuperLU.Tpo .deps/SolveSuperLU.Po gcc -DHAVE_CONFIG_H -I. -I.. -I/home/jmm/deb/libav/elmerfem-6.1.0.svn.5272.dfsg/debian/tmp/usr/include -I/usr/include/freetype2 -I/usr/include/mpi -g -O2 -I/home/jmm/deb/libav/elmerfem-6.1.0.svn.5272.dfsg/debian/tmp/usr/include -fPIC -m64 -fPIC -fPIC -I/usr/include -I/usr/include/mpi -MT umf4_f77wrapper.o -MD -MP -MF .deps/umf4_f77wrapper.Tpo -c -o umf4_f77wrapper.o umf4_f77wrapper.c mv -f .deps/umf4_f77wrapper.Tpo .deps/umf4_f77wrapper.Po /lib/cpp -I/home/jmm/deb/libav/elmerfem-6.1.0.svn.5272.dfsg/debian/tmp/usr/include -DCONTIG=,CONTIGUOUS -P -traditional-cpp -I. -I/usr/include -DFULL_INDUCTION -DUSE_ARPACK -I/usr/include/mpi -DHAVE_MUMPS VankaCreate.src VankaCreate.f90 gfortran -I/home/jmm/deb/libav/elmerfem-6.1.0.svn.5272.dfsg/debian/tmp/usr/include -fPIC -m64 -fPIC -fPIC -I. -Ibinio -I/usr/include/mpi -I/usr/include -c VankaCreate.f90 f951: internal compiler error: Speicherzugriffsfehler Please submit a full bug report, with preprocessed source if appropriate. See file:///usr/share/doc/gcc-4.6/README.Bugs for instructions. make[4]: *** [VankaCreate.o] Fehler 1 make[4]: Leaving directory `/home/jmm/deb/libav/elmerfem-6.1.0.svn.5272.dfsg/fem/src' make[3]: *** [all-recursive] Fehler 1 make[3]: Leaving directory `/home/jmm/deb/libav/elmerfem-6.1.0.svn.5272.dfsg/fem/src' make[2]: *** [all-recursive] Fehler 1 make[2]: Leaving directory `/home/jmm/deb/libav/elmerfem-6.1.0.svn.5272.dfsg/fem' make[1]: *** [all] Fehler 2 make[1]: Leaving directory `/home/jmm/deb/libav/elmerfem-6.1.0.svn.5272.dfsg/fem' make: *** [stamp-build] Fehler 2 dpkg-buildpackage: Fehler: Fehler-Exitstatus von debian/rules build war 2 Cheers, Moritz -- GPG fingerprint: D54D 1AEE B11C CE9B A02B C5DD 526F 01E8 564E E4B6 Engineering consulting with open source tools http://www.opennovation.com/ signature.asc Description: This is a digitally signed message part
Bug#611361: Pending fixes for bugs in the libjifty-plugin-chart-perl package
tag 611361 + pending thanks Some bugs in the libjifty-plugin-chart-perl package are closed in revision be3c84332613394a13df6703b868391dfb4f5dfa in branch 'master' by gregor herrmann The full diff can be seen at http://anonscm.debian.org/gitweb/?p=pkg-perl/packages/libjifty-plugin-chart-perl.git;a=commitdiff;h=be3c843 Commit message: Bump (build) dependency on libjifty-perl to = 1.10518+dfsg. Closes: #611361 -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed: Pending fixes for bugs in the libjifty-plugin-chart-perl package
Processing commands for cont...@bugs.debian.org: tag 611361 + pending Bug #611361 [src:libjifty-plugin-chart-perl] libjifty-plugin-chart-perl: FTBFS due to failing test Added tag(s) pending. thanks Stopping processing here. Please contact me if you need assistance. -- 611361: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=611361 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#633789: xfce4-notifyd
Hi, I found (here: https://bugs.archlinux.org/task/24054) that installing xfce4-notifyd could solve the problem. I tryed and it seems to solve the problem too. -- Christophe Monniez d-fe...@swing.be www.d-fence.be - www.lnx4n6.be -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#639718: [Pkg-haskell-maintainers] Bug#639718: haskell-http-types: FTBFS: hlibrary.setup: At least the following dependencies are missing: case-insensitive ==0.2.*
Hi Clint, this FTBFS bug Am Montag, den 29.08.2011, 19:23 +0200 schrieb Christoph Egger: Configuring http-types-0.6.5... hlibrary.setup: At least the following dependencies are missing: case-insensitive ==0.2.* make: *** [dist-ghc] Error 1 was caused because the Debian package dependencies don’t fully match the version constraint as specified in the .cabal file. Please make sure that the build-depends precisely reflect the requirements of the Haskell library. I’m fixing this by upgrading to the newer http-types version, and fixing the Build-Depends. See the commit message if you not sure what I am talking about :-) Nevertheless, thanks for your work, Joachim -- Joachim nomeata Breitner Debian Developer nome...@debian.org | ICQ# 74513189 | GPG-Keyid: 4743206C JID: nome...@joachim-breitner.de | http://people.debian.org/~nomeata signature.asc Description: This is a digitally signed message part
Bug#625411: tla: I can't reproduce this bug
Hi, This package is building ok for me. I am using gcc version 4.6.1-8 in a pbuilder environment. Lookink at the logs, I think it is not using -Werror option. Maybe I'm missing something or we can close this bug? Thanks for your work! Mònica -- 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: severity 610483 grave Bug #610483 [gmameui] gmameui: misc problems Severity set to 'grave' from 'important' End of message, stopping processing here. Please contact me if you need assistance. -- 610483: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=610483 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed: fixed in svn
Processing commands for cont...@bugs.debian.org: tags 619399 + pending Bug #619399 [munin] munin shouldn't recreate apache conf on every update Added tag(s) pending. thanks Stopping processing here. Please contact me if you need assistance. -- 619399: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=619399 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#639744: Compromised certificates for *.google.com issued by DigiNotar Root CA
On Tuesday 30 August 2011 01:08:29 Yves-Alexis Perez wrote: On lun., 2011-08-29 at 20:24 -0700, Josh Triplett wrote: I understand that they'd have to manually load the lists, but perhaps it would make sense to standardize a location from which they should load them? Does OpenSSL or GnuTLS have any concept of a revocation store format, similar to a certificate store, or would this need some special-purpose custom format? AFAIR they only know about CRL (Certificate Revocation List,) which only allows for one issuer per-file. What I can't tell for sure from the documentation is whether OpenSSL and GnuTLS do check the CRL's validity (signature and time.) It doesn't seem like they do. This is relevant if we were to ship them in ca-certificates. And it'd be nice if nss could share that store... [...] By the way, shouldn't this bug be clone to libnss3-1d (and maybe iceweasel and icedove if they ship the certificates themselves)? Perhaps it's time to start a discussion as to how we can properly deal with all this mess: * Multiple packages shipping their own certificates list * Probably no app except web browsers support CRLs and/or OCSP * configuration Yves, do you know how the CRL stuff is handled in nss? Cheers, -- Raphael Geissert - Debian Developer www.debian.org - get.debian.net -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed: severity of 559767 is important
Processing commands for cont...@bugs.debian.org: # no reason for severity serious severity 559767 important Bug #559767 [java3d] java3d: FTBFS on armel: install: cannot stat `j3d-core/build/default/opt/native/libj3dcore-ogl.so': No such file or directory Severity set to 'important' from 'serious' thanks Stopping processing here. Please contact me if you need assistance. -- 559767: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=559767 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#593139: ruby1.9.1 hangs again
Could you try this version:
---
a = []
trap(:INT) { puts INT recvd ; a.push(1) }
trap(:TERM) { puts TERM recvd ; a.push(2) }
pid = $$
puts parent pid: #{pid}
begin
fork do
puts child pid: #{$$}
sleep 0.5
Process.kill(:INT, pid)
Process.kill(:TERM, pid)
puts signals sent.
end
sleep 1
a.sort
p a
rescue NotImplementedError
[1, 2]
end
parent pid: 44147
child pid: 44150
signals sent.
[]
According to ktrace, signals are sent to parent pid.
It might be related to our pid semantic, each thread have different pid.
The signal cannot be received by a different thread.
#934 test_thread.rb:389:in `top (required)':
open(zzz.rb, w) do |f|
f.puts -END
begin
m = Mutex.new
Thread.new { m.lock; sleep 1 }
sleep 0.3
parent = Thread.current
Thread.new do
sleep 0.3
begin
fork { GC.start }
rescue Exception
parent.raise $!
end
end
m.lock
pid, status = Process.wait2
$result = status.success? ? :ok : :ng
rescue NotImplementedError
$result = :ok
end
END
end
require ./zzz.rb
$result
#= (expected ok)
FAIL 2/937 tests failed
make: *** [yes-btest-ruby] Error 1
Very strange. What about this script?
May be not.
For what should Process.wait2 wait ?
The fork of garbage collector and wait2 seems be by a different thread,
which with our pthread implementration does not work.
--
m = Mutex.new
Thread.new { m.lock; sleep 3 ; puts after m.lock in thread }
sleep 1
m.lock
puts after m.lock
--
after m.lock in thread
after m.lock
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#619399: marked as done (munin shouldn't recreate apache conf on every update)
Your message dated Tue, 30 Aug 2011 18:18:30 + with message-id e1qystk-0004by...@franck.debian.org and subject line Bug#619399: fixed in munin 1.4.6-1 has caused the Debian Bug report #619399, regarding munin shouldn't recreate apache conf on every update 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.) -- 619399: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=619399 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: munin Version: 1.4.5-3 Severity: normal When installing munin for the first time, it does create a link ln -s /etc/munin/apache.conf /etc/apache2/conf.d/munin The problem is that the creation is made in the configure part of the postinst, without any test on wether it's or not an upgrade If a local admin removes /etc/apache2/conf.d/munin with a simple rm , on the nest upgrade of the package, the link will be made again. This should not be, as a package should not touch the configuration made by an admin. So the link should only be made on primo install (inside the [ -z $2 ] test ) and not on any configure. -- System Information: Debian Release: 6.0 APT prefers stable APT policy: (500, 'stable') Architecture: i386 (i686) Kernel: Linux 2.6.32-5-686 (SMP w/1 CPU core) Locale: LANG=fr_FR.utf8, LC_CTYPE=fr_FR.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash ---End Message--- ---BeginMessage--- Source: munin Source-Version: 1.4.6-1 We believe that the bug you reported is fixed in the latest version of munin, which is due to be installed in the Debian FTP archive: munin-common_1.4.6-1_all.deb to main/m/munin/munin-common_1.4.6-1_all.deb munin-java-plugins_1.4.6-1_all.deb to main/m/munin/munin-java-plugins_1.4.6-1_all.deb munin-node_1.4.6-1_all.deb to main/m/munin/munin-node_1.4.6-1_all.deb munin-plugins-extra_1.4.6-1_all.deb to main/m/munin/munin-plugins-extra_1.4.6-1_all.deb munin_1.4.6-1.diff.gz to main/m/munin/munin_1.4.6-1.diff.gz munin_1.4.6-1.dsc to main/m/munin/munin_1.4.6-1.dsc munin_1.4.6-1_all.deb to main/m/munin/munin_1.4.6-1_all.deb munin_1.4.6.orig.tar.gz to main/m/munin/munin_1.4.6.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 619...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Holger Levsen hol...@debian.org (supplier of updated munin 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: Tue, 30 Aug 2011 19:55:52 +0200 Source: munin Binary: munin-node munin-plugins-extra munin-java-plugins munin munin-common Architecture: source all Version: 1.4.6-1 Distribution: unstable Urgency: low Maintainer: Munin Debian Maintainers munin-deb-ma...@linpro.no Changed-By: Holger Levsen hol...@debian.org Description: munin - network-wide graphing framework (grapher/gatherer) munin-common - network-wide graphing framework (common) munin-java-plugins - network-wide graphing framework (java plugins for node) munin-node - network-wide graphing framework (node) munin-plugins-extra - network-wide graphing framework (user contributed plugins for nod Closes: 553528 573750 592842 596026 601200 601505 609241 612108 613029 615226 619399 639745 Changes: munin (1.4.6-1) unstable; urgency=low . * New upstream release (Closes: #639745), closing several bugs in munin: - munin-limits hangs when more than one contact is used (Closes: #553528) - cgi/fastcgi: Use GMT time zone in Last-Modeader (Closes: #601200) - include patch to fix empty list of plugins (Closes: #609241) and in munin-node: - bind9_rndc plugin: version number gate fails (Closes: #573750) - bind9 plugin: doesn't work at all (Closes: #612108) - cidr_allow does not assume implicit /32 (Closes: #592842) ↝- make slapd_ autoconf work, support anonymous bind, and env.server variable (Closes: #596026) - exim munin does weird things (Closes: #601505) - Use selective tls per node in munin master (Closes: #615226) - IPv6 functionality in ip_ plugin assumes /bin/sh being bash (Closes: #613029) Also drop debian/patches/102-snort-bashism.patch as this is included upstream now. * munin.postinst: only create link from /etc/munin/apache.conf to
Processed (with 1 errors): Re: Bug#624666: vlc: security update breaks mp3 support
Processing commands for cont...@bugs.debian.org: Version: 1.1.3-1 Unknown command or malformed arguments to command. notfound 624666 1.1.3-1 Bug #624666 [vlc] vlc: security update breaks mp3 support Bug #624669 [vlc] vlc: broken after 0.8.6.h-4+lenny3 Ignoring request to alter found versions of bug #624666 to the same values previously set Ignoring request to alter found versions of bug #624669 to the same values previously set notfound 624666 1.1.11-2 Bug #624666 [vlc] vlc: security update breaks mp3 support Bug #624669 [vlc] vlc: broken after 0.8.6.h-4+lenny3 Ignoring request to alter found versions of bug #624666 to the same values previously set Ignoring request to alter found versions of bug #624669 to the same values previously set stop Stopping processing here. Please contact me if you need assistance. -- 624666: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=624666 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 639828
Processing commands for cont...@bugs.debian.org: tags 639828 + confirmed Bug #639828 [access-modifier-checker] FTBFS: POM 'org.apache.maven.plugins:maven-plugin-plugin' not found in repository Added tag(s) confirmed. thanks Stopping processing here. Please contact me if you need assistance. -- 639828: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=639828 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#593139: ruby1.9.1 hangs again
On 30/08/11 at 20:18 +0200, Petr Salinger wrote:
Could you try this version:
---
a = []
trap(:INT) { puts INT recvd ; a.push(1) }
trap(:TERM) { puts TERM recvd ; a.push(2) }
pid = $$
puts parent pid: #{pid}
begin
fork do
puts child pid: #{$$}
sleep 0.5
Process.kill(:INT, pid)
Process.kill(:TERM, pid)
puts signals sent.
end
sleep 1
a.sort
p a
rescue NotImplementedError
[1, 2]
end
parent pid: 44147
child pid: 44150
signals sent.
[]
According to ktrace, signals are sent to parent pid.
It might be related to our pid semantic, each thread have different pid.
The signal cannot be received by a different thread.
Arg. If I remember correctly, ruby expects signals to be handled by one
specific thread of the interpreter. Since they have different pids, it's
possible that they are not sent to the right thread.
#934 test_thread.rb:389:in `top (required)':
open(zzz.rb, w) do |f|
f.puts -END
begin
m = Mutex.new
Thread.new { m.lock; sleep 1 }
sleep 0.3
parent = Thread.current
Thread.new do
sleep 0.3
begin
fork { GC.start }
rescue Exception
parent.raise $!
end
end
m.lock
pid, status = Process.wait2
$result = status.success? ? :ok : :ng
rescue NotImplementedError
$result = :ok
end
END
end
require ./zzz.rb
$result
#= (expected ok)
FAIL 2/937 tests failed
make: *** [yes-btest-ruby] Error 1
Very strange. What about this script?
May be not.
For what should Process.wait2 wait ?
The fork of garbage collector and wait2 seems be by a different thread,
which with our pthread implementration does not work.
Indeed.
So, I don't know what to do.
How likely are those problems to be fixed in kfreebsd?
- Lucas
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#593139: ruby1.9.1 hangs again
Could you try make test-all ? While some failures and errors are expected, it stresses the interpreter a bit more, so it's a good way to check that it doesn't block. Under sid, it fails to start, probably due to multiarch changes of libc location: /build/manual/ruby1.9.1-1.9.3~preview1+svn33077/.ext/common/dl/import.rb:227:in `import_function': cannot find the function: strcpy() (DL::DLError) from /build/manual/ruby1.9.1-1.9.3~preview1+svn33077/.ext/common/dl/import.rb:133:in `extern' from /build/manual/ruby1.9.1-1.9.3~preview1+svn33077/test/dl/test_import.rb:12:in `module:LIBC' from /build/manual/ruby1.9.1-1.9.3~preview1+svn33077/test/dl/test_import.rb:5:in `module:DL' Under squeeze runs up to TestDRbCore#test_03 = 0.06 s = . TestDRbCore#test_04 = /opt/sid/build/manual/ruby1.9.1-1.9.3~preview1+svn33077/lib/timeout.rb:61: SEGV received in SEGV handler [BUG] Segmentation fault ruby 1.9.3dev (2011-08-26) [x86_64-kfreebsd-gnu] -- Control frame information --- c:0004 p: s:0011 b:0011 l:10 d:10 CFUNC :sleep c:0003 p:0014 s:0007 b:0007 l:001c10 d:06 BLOCK /opt/sid/build/manual/ruby1.9.1-1.9.3~preview1+svn33077/lib/timeout.rb:61 c:0002 p: s:0004 b:0004 l:03 d:03 FINISH c:0001 p: s:0002 b:0002 l:01 d:01 TOP -- Ruby level backtrace information /opt/sid/build/manual/ruby1.9.1-1.9.3~preview1+svn33077/lib/timeout.rb:61:in `block in timeout' /opt/sid/build/manual/ruby1.9.1-1.9.3~preview1+svn33077/lib/timeout.rb:61:in `sleep' -- C level backtrace information --- /opt/sid/build/manual/ruby1.9.1-1.9.3~preview1+svn33077/libruby-1.9.1.so.1.9(+0x15256f) [0x80097256f] vm_dump.c:796 /opt/sid/build/manual/ruby1.9.1-1.9.3~preview1+svn33077/libruby-1.9.1.so.1.9(+0x59754) [0x800879754] error.c:258 /opt/sid/build/manual/ruby1.9.1-1.9.3~preview1+svn33077/libruby-1.9.1.so.1.9(rb_bug+0xb8) [0x8008798c8] error.c:277 /opt/sid/build/manual/ruby1.9.1-1.9.3~preview1+svn33077/libruby-1.9.1.so.1.9(+0xf0cd5) [0x800910cd5] signal.c:609 /lib/libpthread.so.0(+0xc244) [0x800c31244] [0x7fc3] -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#639801: postgresql-filedump-8.4 and postgresql-filedump: error when trying to install together
On Tue, Aug 30, 2011 at 15:27:26 +0200, Michael Meskes wrote: Removal request for postgresql-filedump-8.4 is already filed. The package is in squeeze, though, so Conflicts/Replaces are needed if there are file overlaps with its replacement. Cheers, Julien -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#537572: Still the same with gnome-settings-daemon 2.30.2-4
Hi, FWIW amid the reports merged with this one, there is one person using i386 and another using mipsel. I don't know for i386 and mipsel, but here are my investigations for ia64. From the point of view of fixing this in binutils, it would be _very_ helpful to have a collection of object files and e.g. two linker command lines that should produce the same binary but do not. At the moment, a person investigating this has to get to know the gnome-settings-daemon build system and it is hard to debug or pass upstream. Alternatively, if this is a regression than a regression range would be helpful. gnome-settings-daemon first appears (at least on ia64) in Debian 5.0 Lenny. So I started with a fresh Lenny install on a spare HDD. From there, the older binutils package that I can install without breaking the whole system is binutils_2.17cvs20070426-1_ia64. Guess what? This old version already produces a broken gnome-settings-daemon with -z flag passed to the linker, and a working one without the flag :-( For further debugging, I can thus provide the locally rebuilt (with binutils_2.17cvs20070426-1_ia64) gnome-settings-daemon_2.22.2.1-2_ia64.deb binary packages with and without -z flag passed to linker. I've also kept the build directories of these two packages if preferred. As an alternative, I can also provide these packages but from a daily-updated Debian Testing Wheezy install, with up-to-date binutils and gnome-settings-daemon packages if preferred. About the gnome-settings-daemon build system, maybe Josselin can give us a clue? I have no idea how it works. Best regards, Émeric -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#638294: Blocked upgrade of libdap11
Use the version in unstable to build against. A header file and not just a symbol were removed; i'm not sure whats involved in making gdal build against it. To my understanding, no other package directly uses libdap, but rather links it via gdal, but they will need to be rebuilt once gdal is fixed. It would be good if --as-needed was used to remove this false dependency. regards Alastair On 2011-08-30 10:56, Francesco P. Lovergine wrote: On Tue, Aug 30, 2011 at 11:39:40AM +0200, Julien Cristau wrote: So what? Some reverse build-deps like gdal are still waiting in the dark for a rebuild ... Last I checked the API change in new libdap makes gdal 1.7 unbuildable anyway, so that will need a source upload. Thanks, let me check about that. Alastair, should I consider the current libdap version in unstable or the experimental one to prepare a fix? -- Alastair McKinstry ,alast...@sceal.ie ,mckins...@debian.org http://blog.sceal.ie Anyone who believes exponential growth can go on forever in a finite world is either a madman or an economist - Kenneth Boulter, Economist. -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#639744: Compromised certificates for *.google.com issued by DigiNotar Root CA
On mar., 2011-08-30 at 12:29 -0500, Raphael Geissert wrote: On Tuesday 30 August 2011 01:08:29 Yves-Alexis Perez wrote: On lun., 2011-08-29 at 20:24 -0700, Josh Triplett wrote: I understand that they'd have to manually load the lists, but perhaps it would make sense to standardize a location from which they should load them? Does OpenSSL or GnuTLS have any concept of a revocation store format, similar to a certificate store, or would this need some special-purpose custom format? AFAIR they only know about CRL (Certificate Revocation List,) which only allows for one issuer per-file. What I can't tell for sure from the documentation is whether OpenSSL and GnuTLS do check the CRL's validity (signature and time.) It doesn't seem like they do. This is relevant if we were to ship them in ca-certificates. And it'd be nice if nss could share that store... [...] By the way, shouldn't this bug be clone to libnss3-1d (and maybe iceweasel and icedove if they ship the certificates themselves)? Perhaps it's time to start a discussion as to how we can properly deal with all this mess: * Multiple packages shipping their own certificates list * Probably no app except web browsers support CRLs and/or OCSP * configuration Yves, do you know how the CRL stuff is handled in nss? (my first name is Yves-Alexis :) I have no idea. There's a crlutil (http://www.mozilla.org/projects/security/pki/nss/tools/crlutil.html) but it works on previous database version (bdb, cert8.db and key3.db) while at least evolution now uses the shared sqlite db (cert9.db and key4.db, see https://wiki.mozilla.org/NSS_Shared_DB). Maybe Mike has some more ideas (adding him to CC:) Regards, -- Yves-Alexis signature.asc Description: This is a digitally signed message part
Bug#616273: marked as done (openturns: replace doxygen and texlive-* build dependencies with doxygen-latex)
Your message dated Tue, 30 Aug 2011 22:12:43 +0200 with message-id cajr1dlrxuspd-nhdl_bdrcbhv7xidjdpbaz8xebhudxmu4e...@mail.gmail.com and subject line Fixed with new upstream upload has caused the Debian Bug report #616273, regarding openturns: replace doxygen and texlive-* build dependencies with doxygen-latex 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.) -- 616273: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=616273 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: src:openturns Version: 0.13.2-8 Severity: minor User: d...@debian.org Usertag: doxygen-latex The package build-depends on doxygen and one or more of the texlive-* packages, likely it is building some latex/pdf docs using a doxygen.sty generated by doxygen. The doxygen.sty generated by doxygen-1.7.3 now depends on even more macros, so instead of adding more texlive-* dependencies to doxygen, or adding the texlive-* packages to the build dependencies of each source package, a new doxygen-latex package was introduced, depending on all required packages used by doxygen.sty. . If the package builds such documentation, please build-depend on doxygen-latex. If not, please close the report as invalid. ---End Message--- ---BeginMessage--- Fixed with new upstream upload ---End Message---
Bug#624975: marked as done (openturns: FTBFS: StorageManager.hxx:394:13: error: 'ptrdiff_t' does not name a type)
Your message dated Tue, 30 Aug 2011 22:13:43 +0200 with message-id cajr1dltmmtshujqnxjdfptuldialwnghgdiptnzadqmi17z...@mail.gmail.com and subject line Fixed with latest upstream release has caused the Debian Bug report #624975, regarding openturns: FTBFS: StorageManager.hxx:394:13: error: 'ptrdiff_t' does not name a type 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.) -- 624975: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=624975 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Source: openturns Version: 0.13.2-8 Severity: serious Tags: wheezy sid User: debian...@lists.debian.org Usertags: qa-ftbfs-20110502 qa-ftbfs Justification: FTBFS on amd64 Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part: /bin/bash ../../../libtool --tag=CXX --mode=compile x86_64-linux-gnu-g++ -DHAVE_CONFIG_H -I. -I../../../include -I../../../include -I../../../include -DNDEBUG -DINSTALL_PATH=\/usr\ -DDATA_PATH=\/usr/share\ -DSYSCONFIG_PATH=\/etc\ -DLIBINSTALL_PATH=\/usr/lib/openturns\ -I/usr/include/libxml2 -I/usr/include -DOT_DEBUG_LEVEL=3 -DNDEBUG -pthread -g -O2 -c -o libOTCommon_la-PersistentObject.lo `test -f 'PersistentObject.cxx' || echo './'`PersistentObject.cxx libtool: compile: x86_64-linux-gnu-g++ -DHAVE_CONFIG_H -I. -I../../../include -I../../../include -I../../../include -DNDEBUG -DINSTALL_PATH=\/usr\ -DDATA_PATH=\/usr/share\ -DSYSCONFIG_PATH=\/etc\ -DLIBINSTALL_PATH=\/usr/lib/openturns\ -I/usr/include/libxml2 -I/usr/include -DOT_DEBUG_LEVEL=3 -DNDEBUG -pthread -g -O2 -c PersistentObject.cxx -fPIC -DPIC -o .libs/libOTCommon_la-PersistentObject.o In file included from PersistentObject.hxx:31:0, from PersistentObject.cxx:26: StorageManager.hxx:394:13: error: 'ptrdiff_t' does not name a type make[5]: *** [libOTCommon_la-PersistentObject.lo] Error 1 The full build log is available from: http://people.debian.org/~lucas/logs/2011/05/02/openturns_0.13.2-8_lsid64.buildlog A list of current common problems and possible solutions is available at http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute! About the archive rebuild: The rebuild was done on about 50 AMD64 nodes of the Grid'5000 platform, using a clean chroot. Internet was not accessible from the build systems. -- | Lucas Nussbaum | lu...@lucas-nussbaum.net http://www.lucas-nussbaum.net/ | | jabber: lu...@nussbaum.fr GPG: 1024D/023B3F4F | ---End Message--- ---BeginMessage--- -- Debian Developer - member of Debian Science http://wiki.debian.org/DebianScience Prof. at Univ. Grenoble in Applied Math. http://ljk.imag.fr/membres/Christophe.Prudhomme/ ---End Message---
Processed: severity for 639833
Processing commands for cont...@bugs.debian.org: severity 639833 serious Bug #639833 [ocsinventory-reports] ocsinventory-reports: Distribution of files incompatible with the GPL Severity set to 'serious' from 'normal' thanks Stopping processing here. Please contact me if you need assistance. -- 639833: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=639833 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#639744: Compromised certificates for *.google.com issued by DigiNotar Root CA
On Tue, Aug 30, 2011 at 09:58:18PM +0200, Yves-Alexis Perez wrote: On mar., 2011-08-30 at 12:29 -0500, Raphael Geissert wrote: On Tuesday 30 August 2011 01:08:29 Yves-Alexis Perez wrote: On lun., 2011-08-29 at 20:24 -0700, Josh Triplett wrote: I understand that they'd have to manually load the lists, but perhaps it would make sense to standardize a location from which they should load them? Does OpenSSL or GnuTLS have any concept of a revocation store format, similar to a certificate store, or would this need some special-purpose custom format? AFAIR they only know about CRL (Certificate Revocation List,) which only allows for one issuer per-file. What I can't tell for sure from the documentation is whether OpenSSL and GnuTLS do check the CRL's validity (signature and time.) It doesn't seem like they do. This is relevant if we were to ship them in ca-certificates. And it'd be nice if nss could share that store... [...] By the way, shouldn't this bug be clone to libnss3-1d (and maybe iceweasel and icedove if they ship the certificates themselves)? Perhaps it's time to start a discussion as to how we can properly deal with all this mess: * Multiple packages shipping their own certificates list * Probably no app except web browsers support CRLs and/or OCSP * configuration Yves, do you know how the CRL stuff is handled in nss? (my first name is Yves-Alexis :) I have no idea. There's a crlutil (http://www.mozilla.org/projects/security/pki/nss/tools/crlutil.html) but it works on previous database version (bdb, cert8.db and key3.db) while at least evolution now uses the shared sqlite db (cert9.db and key4.db, see https://wiki.mozilla.org/NSS_Shared_DB). The NSS tools are supposed to work with whatever database version you use, since they use NSS ;) That being said, there is a huge problem with mitigation in basically all the SSL libraries. There simply is no way to handle the current situation[1] without modifying applications. Mike 1. Several fraudulent certificates whose fingerprint is unknown signed with several different intermediate certs that are cross-signed by other safe CAs (aiui). -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#639744: Compromised certificates for *.google.com issued by DigiNotar Root CA
On mar., 2011-08-30 at 22:48 +0200, Mike Hommey wrote: 1. Several fraudulent certificates whose fingerprint is unknown signed with several different intermediate certs that are cross-signed by other safe CAs (aiui). I missed that. What is the source for that? (i looked at the mozilla bug earlier but it lacks that level of precision) -- Yves-Alexis signature.asc Description: This is a digitally signed message part
Bug#566128: marked as done (squishdot: Depends on removed zope2.10)
Your message dated Tue, 30 Aug 2011 21:05:36 + with message-id e1qyvv2-0006o6...@franck.debian.org and subject line Bug#636046: Removed package(s) from unstable has caused the Debian Bug report #566128, regarding squishdot: Depends on removed zope2.10 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.) -- 566128: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=566128 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: squishdot Version: 1.5.0-6 Severity: serious Hi, squishdot depends on one of zope2.10 | zope2.9 | zope2.8 | zope2.7. However, with the removal of zope2.10 from the archive, it is now uninstallable, as none of the listed packages are in Debian. Regards, Adam ---End Message--- ---BeginMessage--- Version: 1.5.0-6.1+rm Dear submitter, as the package squishdot 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/636046 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. Luca Falavigna (the ftpmaster behind the curtain) ---End Message---
Bug#613361: marked as done (zope-tinytableplus: uninstallable in sid)
Your message dated Tue, 30 Aug 2011 21:07:56 + with message-id e1qyvxi-0007gg...@franck.debian.org and subject line Bug#631386: Removed package(s) from unstable has caused the Debian Bug report #613361, regarding zope-tinytableplus: uninstallable in sid 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.) -- 613361: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=613361 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: zope-tinytableplus Version: 0.9-19 Severity: serious Hi, zope was removed from sid a while back so your package is not installable. Cheers, Julien ---End Message--- ---BeginMessage--- Version: 0.9-19+rm Dear submitter, as the package zope-tinytableplus 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/631386 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. Luca Falavigna (the ftpmaster behind the curtain) ---End Message---
Bug#639801: marked as done (postgresql-filedump-8.4 and postgresql-filedump: error when trying to install together)
Your message dated Tue, 30 Aug 2011 21:08:43 + with message-id e1qyvy3-0007m2...@franck.debian.org and subject line Bug#639804: Removed package(s) from unstable has caused the Debian Bug report #639801, regarding postgresql-filedump-8.4 and postgresql-filedump: error when trying to install together 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.) -- 639801: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=639801 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: postgresql-filedump,postgresql-filedump-8.4 Version: postgresql-filedump/9.0.0-1 Version: postgresql-filedump-8.4/8.4.0-1 Severity: serious User: trei...@debian.org Usertags: edos-file-overwrite Date: 2011-08-30 Architecture: amd64 Distribution: sid Hi, automatic installation tests of packages that share a file and at the same time do not conflict by their package dependency relationships has detected the following problem: WARNING: The following packages cannot be authenticated! postgresql-filedump postgresql-filedump-8.4 Authentication warning overridden. Can not write log, openpty() failed (/dev/pts not mounted?) Selecting previously deselected package postgresql-filedump. (Reading database ... 10663 files and directories currently installed.) Unpacking postgresql-filedump (from .../postgresql-filedump_9.0.0-1_amd64.deb) ... Selecting previously deselected package postgresql-filedump-8.4. Unpacking postgresql-filedump-8.4 (from .../postgresql-filedump-8.4_8.4.0-1_amd64.deb) ... dpkg: error processing /var/cache/apt/archives/postgresql-filedump-8.4_8.4.0-1_amd64.deb (--unpack): trying to overwrite '/usr/lib/postgresql/8.4/bin/pg_filedump', which is also in package postgresql-filedump 9.0.0-1 configured to not write apport reports Errors were encountered while processing: /var/cache/apt/archives/postgresql-filedump-8.4_8.4.0-1_amd64.deb E: Sub-process /usr/bin/dpkg returned an error code (1) This is a serious bug as it makes installation fail, and violates sections 7.6.1 and 10.1 of the policy. An optimal solution would consist in only one of the packages installing that file, and renaming or removing the file in the other package. Depending on the circumstances you might also consider Replace relations or file diversions. If the conflicting situation cannot be resolved then, as a last resort, the two packages have to declare a mutual Conflict. Please take into account that Replaces, Conflicts and diversions should only be used when packages provide different implementations for the same functionality. Here is a list of files that are known to be shared by both packages (according to the Contents file for sid/amd64, which may be slightly out of sync): /usr/lib/postgresql/8.4/bin/pg_filedump This bug is assigned to both packages. If you, the maintainers of the two packages in question, have agreed on which of the packages will resolve the problem please reassign the bug to that package. You may also register in the BTS that the other package is affected by the bug. -Ralf. PS: for more information about the detection of file overwrite errors of this kind see http://edos.debian.net/file-overwrites/. ---End Message--- ---BeginMessage--- Version: 8.4.0-1+rm Dear submitter, as the package postgresql-filedump-8.4 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/639804 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. Luca Falavigna (the ftpmaster behind the curtain) ---End Message---
Bug#639711: marked as done (w3c-markup-validator: misdetects version of HTML::Template)
Your message dated Tue, 30 Aug 2011 21:33:57 + with message-id e1qyvwt-0003d5...@franck.debian.org and subject line Bug#639711: fixed in w3c-markup-validator 1.2+dfsg-2 has caused the Debian Bug report #639711, regarding w3c-markup-validator: misdetects version of HTML::Template 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.) -- 639711: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=639711 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: w3c-markup-validator Version: 1.2+dfsg-1 Severity: normal Hi. Here's what I get : $ /usr/lib/cgi-bin/w3c-markup-validator/check Status: 500 Content-type: text/html h1Software error:/h1 preHTML::Template version 2.6 required--this is only version 2.10 at /usr/lib/cgi-bin/w3c-markup-validator/check line 56. BEGIN failed--compilation aborted at /usr/lib/cgi-bin/w3c-markup-validator/check line 56. /pre p For help, please send mail to this site's webmaster, giving this error message and the time and date of the error. /p [Mon Aug 29 17:59:58 2011] check: HTML::Template version 2.6 required--this is only version 2.10 at /usr/lib/cgi-bin/w3c-markup-validator/check line 56. [Mon Aug 29 17:59:58 2011] check: BEGIN failed--compilation aborted at /usr/lib/cgi-bin/w3c-markup-validator/check line 56. Uh... it detects 2.10 2.6, is it ? Hope this helps, -- System Information: Debian Release: wheezy/sid APT prefers testing APT policy: (900, 'testing'), (300, 'stable') Architecture: i386 (i686) Kernel: Linux 3.0.0-1-686-pae (SMP w/2 CPU cores) Locale: LANG=fr_FR.utf8, LC_CTYPE=fr_FR.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages w3c-markup-validator depends on: ii apache2 2.2.19-1Apache HTTP Server metapackage ii apache2-mpm-prefork [apache2 2.2.19-1Apache HTTP Server - traditional n ii libconfig-general-perl 2.50-1 Generic Configuration Module ii libencode-hanextra-perl 0.23-2+b1 perl module providing extra sets o ii libhtml-encoding-perl0.61-1 perl module determining the encodi ii libhtml-parser-perl 3.68-1+b1 collection of modules that parse H ii libhtml-template-perl2.10-1 module for using HTML Templates wi ii libjson-perl 2.53-1 module for manipulating JSON-forma ii libnet-ip-perl 1.25-3 Perl extension for manipulating IP ii libset-intspan-perl 1.16-1 module to manage sets of integers ii libsgml-parser-opensp-perl 0.994-2 OpenSP Parser of SGML documents ii libtext-iconv-perl 1.7-4 converts between character sets in ii liburi-perl 1.59-1 module to manipulate and access UR ii libwww-perl 6.02-1 simple and consistent interface to ii libxml-libxml-perl 1.84+dfsg-1 Perl interface to the libxml2 libr ii perl 5.12.4-4Larry Wall's Practical Extraction ii w3c-sgml-lib 1.2-1 w3.org DTD and catalog files Versions of packages w3c-markup-validator recommends: ii libhtml-tidy-perl 1.50-1+b1 module for (X)HTML validation Versions of packages w3c-markup-validator suggests: ii libtest-html-w3c-perl 0.03-2 wrapper around W3C HTML validation ii libwebservice-validator-html- 0.27-1 Perl interface to access the W3C's pn libxml-path-perl none (no description available) -- debconf-show failed ---End Message--- ---BeginMessage--- Source: w3c-markup-validator Source-Version: 1.2+dfsg-2 We believe that the bug you reported is fixed in the latest version of w3c-markup-validator, which is due to be installed in the Debian FTP archive: w3c-markup-validator_1.2+dfsg-2.debian.tar.gz to main/w/w3c-markup-validator/w3c-markup-validator_1.2+dfsg-2.debian.tar.gz w3c-markup-validator_1.2+dfsg-2.dsc to main/w/w3c-markup-validator/w3c-markup-validator_1.2+dfsg-2.dsc w3c-markup-validator_1.2+dfsg-2_all.deb to main/w/w3c-markup-validator/w3c-markup-validator_1.2+dfsg-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 639...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Nicholas Bamber nicho...@periapt.co.uk (supplier of updated w3c-markup-validator package) (This message was generated automatically at their request; if you believe that there is a problem with it please
Bug#637688: [mercurial] unable to reproduce bug
On Thu, Aug 18, 2011 at 3:31 PM, Julien Cristau jcris...@debian.org wrote: On Thu, Aug 18, 2011 at 14:12:17 -0400, Simon wrote: On 2011-08-16 03:49, Javi Merino wrote: Hi Chris, BTW in case this may help, I'm including the output of the following command: $ ls -ld /usr/lib/python2.6/site-packages ls: cannot access /usr/lib/python2.6/site-packages: No such file or directory a symlink to dist-packages/ That's utterly broken. Did you create that symlink? Cheers, Julien yes, and removed it when i sent you the previous email ;). -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#639828: FTBFS: POM 'org.apache.maven.plugins:maven-plugin-plugin' not found in repository
tag 639828 + pending thanks On Tue, Aug 30, 2011 at 06:41:11PM +0200, Laurent Fousse wrote: Package: access-modifier-checker Version: 1.0-1 Severity: serious Justification: fails to build from source Your package fails to build from source: It is already fixed in git. -- Miguel Landaeta, miguel at miguel.cc secure email with PGP 0x7D8967E9 available at http://keyserver.pgp.com/ Faith means not wanting to know what is true. -- Nietzsche signature.asc Description: Digital signature
Processed: Re: FTBFS: POM 'org.apache.maven.plugins:maven-plugin-plugin' not found in repository
Processing commands for cont...@bugs.debian.org: tag 639828 + pending Bug #639828 [access-modifier-checker] FTBFS: POM 'org.apache.maven.plugins:maven-plugin-plugin' not found in repository Added tag(s) pending. thanks Stopping processing here. Please contact me if you need assistance. -- 639828: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=639828 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#639853: openjdk-6-jre = 6b23~pre8-2 breaks josm
Package: josm Version: 0.0.svn4064-3 Severity: grave Justification: renders package unusable The latest version of openjdk-6-jre is multiarch aware, which means the path of the jre has changed. This breaks /usr/bin/josm: + set -e ++ readlink -n -f /etc/alternatives/java + ALTERNATIVE_JDK=/usr/lib/jvm/java-6-openjdk-i386/jre/bin/java + dpkg --get-selections openjdk-6-jre + grep 'install$' + JAVA_CMDS='/bin/java /usr/lib/jvm/java-6-openjdk/bin/java /usr/lib/jvm/java-6-sun/bin/java' + JAVA_OPTS=' -Djava.net.preferIPv4Stack=true -Djava.net.useSystemProxies=true' + for jcmd in '$JAVA_CMDS' ++ readlink -n -f /bin/java + '[' z/usr/lib/jvm/java-6-openjdk-i386/jre/bin/java = z/bin/java ']' + for jcmd in '$JAVA_CMDS' ++ readlink -n -f /usr/lib/jvm/java-6-openjdk/bin/java + '[' z/usr/lib/jvm/java-6-openjdk-i386/jre/bin/java = z ']' + for jcmd in '$JAVA_CMDS' ++ readlink -n -f /usr/lib/jvm/java-6-sun/bin/java + '[' z/usr/lib/jvm/java-6-openjdk-i386/jre/bin/java = z ']' + for jcmd in '$JAVA_CMDS' + '[' -x /bin/java -a -z '' ']' + for jcmd in '$JAVA_CMDS' + '[' -x /usr/lib/jvm/java-6-openjdk/bin/java -a -z '' ']' + for jcmd in '$JAVA_CMDS' + '[' -x /usr/lib/jvm/java-6-sun/bin/java -a -z '' ']' + '[' '' ']' + echo 'No valid JVM found to run JOSM.' + exit 1 -- System Information: Debian Release: wheezy/sid APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') Architecture: i386 (i686) Kernel: Linux 3.0.0-1-686-pae (SMP w/2 CPU cores) Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages josm depends on: ii libgettext-commons-java 0.9.6-2 Java classes for internationalizat ii libmetadata-extractor-j 2.3.1+dfsg-2 JPEG metadata extraction framework ii liboauth-signpost-java 1.2.1.1-1simple OAuth message signing for J ii openjdk-6-jre 6b23~pre8-2 OpenJDK Java runtime, using Hotspo ii openstreetmap-map-icons 1:0.0.svn23763-1 Collection of map icons (classic s Versions of packages josm recommends: ii josm-plugins 0.0.svn25935-1 Plugins for JOSM ii webkit-image-gtk 0.0.svn25399-2 generate images from webpages - GT josm suggests no packages. -- no debconf information -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#639859: apt-build fails to build packages ; it conflicts with apt
Package: apt-build Version: 0.12.38 Severity: grave Tags: sid wheezy patch Justification: renders package unusable Trying to install a package with apt-build, for example: # apt-build install hello it fails with: W: Failed to fetch file:/var/cache/apt-build/repository/dists/apt-build/Release Unable to find expected entry 'main/binary-amd64/Packages' in Release file (Wrong sources.list entry or malformed file) E: Some index files failed to download. They have been ignored, or old ones used instead. Reading package lists... Done E: The value 'apt-build' is invalid for APT::Default-Release as such a release is not available in the sources Subsequently, 'apt-get update' gives: W: Failed to fetch file:/var/cache/apt-build/repository/dists/apt-build/Release Unable to find expected entry 'main/binary-amd64/Packages' in Release file (Wrong sources.list entry or malformed file) E: Some index files failed to download. They have been ignored, or old ones used instead. I erased /var/cache/apt-build and applied the following patch to get rid of this problem: --- diff -Naur apt-build-0.12.38.orig/apt-build apt-build-0.12.38/apt-build --- apt-build-0.12.38.orig/apt-build2008-07-01 08:29:43.0 +0200 +++ apt-build-0.12.38/apt-build 2011-08-30 23:55:39.0 +0200 @@ -101,9 +101,9 @@ update-source - Update all sources and rebuild them remove- Remove packages build-repository - Rebuild the repository - clean-sources - Clean up all object files in source directories clean-build - Erase downloaded packages and temporary build files - clean-repository - Erase downloaded packages and temporary build files + clean-repository - Erase built packages + clean-sources - Clean up all object files in source directories world - Rebuild and reinstall all packages on your system info - Build-related package information @@ -337,10 +337,10 @@ chdir $conf-repository_dir; my $arch = $_config-get(APT::Architecture); -system ln -s . main unless -e main; -system ln -s . apt-build unless -e apt-build; -system ln -s . dists unless -e dists; -system ln -s . binary-$arch unless -e binary-$arch; +system mkdir dists unless -e dists; +system mkdir dists/apt-build unless -e dists/apt-build; +system mkdir dists/apt-build/main unless -e dists/apt-build/main; +system ln -s ../../.. dists/apt-build/main/binary-$arch unless -e dists/apt-build/main/binary-$arch; make_release_file() unless -e Release; system apt-ftparchive packages . | gzip -9 Packages.gz; diff -Naur apt-build-0.12.38.orig/debian/postinst apt-build-0.12.38/debian/postinst --- apt-build-0.12.38.orig/debian/postinst 2011-03-13 16:55:00.0 +0100 +++ apt-build-0.12.38/debian/postinst 2011-08-31 01:19:41.0 +0200 @@ -79,13 +79,8 @@ # Create repository_dir if [ ! -e $repository_dir ]; then - mkdir -p $repository_dir - cd $repository_dir - ln -s . stable - ln -s . dists - ln -s . apt-build - ln -s . main - ln -s . binary-`dpkg --print-architecture` + mkdir -p $repository_dir/dists/apt-build/main + ln -s ../../.. $repository_dir/dists/apt-build/main/binary-`dpkg --print-architecture` fi sed s/__arch__/`dpkg --print-architecture`/ /usr/share/apt-build/Release $repository_dir/Release --- Unfortunately, it doesn't solve the problem. apt-get update keeps saying: E: The value 'apt-build' is invalid for APT::Default-Release as such a release is not available in the sources Maybe an apt bug rather than an apt-build bug ? -- System Information: Debian Release: wheezy/sid APT prefers testing APT policy: (800, 'testing'), (750, 'stable'), (500, 'oldstable'), (50, 'experimental'), (50, 'unstable') Architecture: amd64 (x86_64) Kernel: Linux 3.0.0-1-amd64 (SMP w/2 CPU cores) Locale: LANG=fr_FR.utf-8, LC_CTYPE=fr_FR.utf-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash Versions of packages apt-build depends on: ii apt 0.8.15.6 Advanced front-end for dpkg ii apt-utils 0.8.15.6 APT utility programs ii debconf [debconf-2.0] 1.5.40 Debian configuration management sy ii devscripts2.11.0 scripts to make the life of a Debi ii dpkg-dev 1.16.0.3 Debian package development tools ii g++ 4:4.6.1-2 GNU C++ compiler ii gcc 4:4.6.1-2 GNU C compiler ii libappconfig-perl 1.56-2 Perl module for configuration file ii libapt-pkg-perl 0.1.24+b2 Perl interface to libapt-pkg ii libc6 2.13-16Embedded GNU C Library: Shared
Bug#639860: open-vm-tools: vmware-toolbox and vmware-user binaries are missing
Package: open-vm-tools Version: 2:8.4.2+2011.08.21-471295-1 Severity: grave Justification: renders package unusable The new open-vm-tools package omits, ironically, the vmware tools. Specifically, at the very least, /usr/bin/vmware-toolbox /usr/bin/vmware-user are missing. Without the ability to control the vmware tools, there's not much point in having them. -- System Information: Debian Release: wheezy/sid APT prefers unstable APT policy: (990, 'unstable') Architecture: i386 (i686) Kernel: Linux 3.0.0-1-686-pae (SMP w/1 CPU core) Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968) Shell: /bin/sh linked to /bin/bash Versions of packages open-vm-tools depends on: ii libc6 2.13-18Embedded GNU C Library: Shared lib ii libfuse2 2.8.5-4Filesystem in Userspace (library) pn libgcc1 none (no description available) ii libglib2.0-0 2.28.6-1 The GLib library of C routines ii libicu44 4.4.2-2International Components for Unico pn libstdc++6none (no description available) Versions of packages open-vm-tools recommends: ii ethtool 1:3.0-1 display or change Ethernet device ii open-vm-sour 2:8.4.2+2011.08.21-471295-1 Source for VMware guest systems dr ii zerofree 1.0.1-2 zero free blocks from ext2/3 file- Versions of packages open-vm-tools suggests: ii open-vm-tool 2:8.4.2+2011.08.21-471295-1 tools and components for VMware gu -- Configuration Files: /etc/vmware-tools/tools.conf changed: /etc/xdg/autostart/vmware-user.desktop [Errno 2] No such file or directory: u'/etc/xdg/autostart/vmware-user.desktop' -- no debconf information -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#635321: Unable to reproduce with soundtouch 1.6.0-1 or 1.6.0-2
Hello: Today I tried to reproduce this bug but I could not do it. I also could not find a change in soundtouch BPM routines from 1.5.0 to 1.6.0 that could have caused it. Here is a log of what I did but I cut out some of the verbose: $ apt-cache policy libsoundtouch0 | grep Installed Installed: 1.6.0-2 $ sudo apt-get install banshee -qq $ apt-cache policy banshee | grep Installed Installed: 2.0.1-4+b2 $ banshee [Info 21:06:18.659] Running Banshee 2.0.1: [Debian GNU/Linux unstable (sid) (linux-gnu, x86_64) @ 2011-08-28 13:30:52 UTC] snip $ sudo apt-get install -t experimental banshee -qq $ apt-cache policy banshee | grep Installed Installed: 2.1.3-1 $ banshee [Info 21:07:13.017] Running Banshee 2.1.3: [Debian GNU/Linux unstable (sid) (linux-gnu, x86_64) @ 2011-08-25 13:36:14 BST] snip $ rm -rf ~/.config/banshee-1/ I went to http://snapshot.debian.org/package/soundtouch/1.6.0-1/#libsoundtouch0_1.6.0-1 and installed the 1.6.0-1 as originally reported. $ sudo dpkg -i libsoundtouch0_1.6.0-1_amd64.deb $ sudo apt-get install banshee/sid -qq $ apt-cache policy libsoundtouch0 | grep Installed Installed: 1.6.0-1 $ apt-cache policy banshee | grep Installed Installed: 2.0.1-4+b2 $ banshee [Info 21:08:58.164] Running Banshee 2.0.1: [Debian GNU/Linux unstable (sid) (linux-gnu, x86_64) @ 2011-08-28 13:30:52 UTC] snip $ sudo apt-get install -t experimental banshee -qq $ apt-cache policy banshee | grep Installed Installed: 2.1.3-1 $ banshee [Info 21:09:59.268] Running Banshee 2.1.3: [Debian GNU/Linux unstable (sid) (linux-gnu, x86_64) @ 2011-08-25 13:36:14 BST] snip $ apt-cache policy libsoundtouch0 | grep Installed Installed: 1.6.0-1 $ apt-cache policy banshee | grep Installed Installed: 2.1.3-1 Both soundtouch 1.6.0-1 and 1.6.0-2 worked fine with Banshee from sid and experimental. For a final test I tried the version that was originally reported: $ rm -rf ~/.config/banshee-1/ $ sudo dpkg -i libgdata1.7-cil_1.7.0.1-1_all.deb banshee_2.1.0-1_amd64.deb libmtp8_1.0.6-7_amd64.deb $ banshee [Info 21:32:02.028] Running Banshee 2.1.0: [Debian GNU/Linux unstable (sid) (linux-gnu, x86_64) @ 2011-05-17 11:03:27 UTC] snip $ apt-cache policy libsoundtouch0 | grep Installed Installed: 1.6.0-1 $ apt-cache policy banshee | grep Installed Installed: 2.1.0-1 So the current 2.0.1, the reported 2.1.0-1 and the current version from experimental seem to work with a current and up to date system. I guess that there was a different package that caused the original crash and that package got updated again and the original issue was resolved. If the original submitter could confirm it would help. Hope this helps, Miguel -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#639744: marked as done (Compromised certificates for *.google.com issued by DigiNotar Root CA)
Your message dated Wed, 31 Aug 2011 02:47:56 + with message-id e1qyaqk-00045n...@franck.debian.org and subject line Bug#639744: fixed in ca-certificates 20110502+nmu1 has caused the Debian Bug report #639744, regarding Compromised certificates for *.google.com issued by DigiNotar Root CA 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.) -- 639744: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=639744 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: ca-certificates Version: 20110502 Severity: critical Tags: security Please see the following: https://bugzilla.mozilla.org/show_bug.cgi?id=682956 http://pastebin.com/ff7Yg663 http://pastebin.com/SwCZqskV (or just search current news for DigiNotar, optionally in conjunction with gmail or google.) Whatever resolution Mozilla and others end up with (revocation of the certificate or of the entire CA), ca-certificates will likely need to do the same. - Josh Triplett ---End Message--- ---BeginMessage--- Source: ca-certificates Source-Version: 20110502+nmu1 We believe that the bug you reported is fixed in the latest version of ca-certificates, which is due to be installed in the Debian FTP archive: ca-certificates_20110502+nmu1.dsc to main/c/ca-certificates/ca-certificates_20110502+nmu1.dsc ca-certificates_20110502+nmu1.tar.gz to main/c/ca-certificates/ca-certificates_20110502+nmu1.tar.gz ca-certificates_20110502+nmu1_all.deb to main/c/ca-certificates/ca-certificates_20110502+nmu1_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 639...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Raphael Geissert geiss...@debian.org (supplier of updated ca-certificates 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: Tue, 30 Aug 2011 21:00:55 -0500 Source: ca-certificates Binary: ca-certificates Architecture: source all Version: 20110502+nmu1 Distribution: unstable Urgency: high Maintainer: Debian QA Group packa...@qa.debian.org Changed-By: Raphael Geissert geiss...@debian.org Description: ca-certificates - Common CA certificates Closes: 639744 Changes: ca-certificates (20110502+nmu1) unstable; urgency=high . * Non-maintainer upload by the Security Team. * Blacklist DigiNotar Root CA (Closes: #639744) Checksums-Sha1: b00627a9ffade9f740d120b5752fe0d407de0138 820 ca-certificates_20110502+nmu1.dsc 63943f2203893cb8f7ae2f8ec3a29ad121d3593c 276132 ca-certificates_20110502+nmu1.tar.gz 141c8bf62f46043c52442d9bb58cc9bf74ed1b4c 174242 ca-certificates_20110502+nmu1_all.deb Checksums-Sha256: f89e12fedc5bfe6d160f4380e5c4a6f1a6ea8a27ecb4724d4f072c570de71a3c 820 ca-certificates_20110502+nmu1.dsc 32349782ed419d88924f69e3feb1755a045dc15b8d0cfd15cdd9176f0596997d 276132 ca-certificates_20110502+nmu1.tar.gz d44284ee9b733b9890a54516f66b68a382ac5fb2c0bdceafed4cf229aa3b05a1 174242 ca-certificates_20110502+nmu1_all.deb Files: e4c5e4bb5bba6508898bcbfe8eda802a 820 misc optional ca-certificates_20110502+nmu1.dsc 13aed718a5cdd05b4086c93dafd4e1e2 276132 misc optional ca-certificates_20110502+nmu1.tar.gz 97e5972d2ef2531667e83df78a8f83a8 174242 misc optional ca-certificates_20110502+nmu1_all.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.11 (GNU/Linux) iEYEARECAAYFAk5dmcAACgkQYy49rUbZzlpZaACdEQpbuSDddjgSXwyZYdg/UPhm 7+kAn1EU6LRHjCRO1e0wbBHfeL0COLC+ =qQMo -END PGP SIGNATURE- ---End Message---
Bug#638219: marked as done (bzr-builddeb: FTBFS: IOError: [Errno 20] Not a directory)
Your message dated Wed, 31 Aug 2011 02:47:37 + with message-id e1qyaq1-000404...@franck.debian.org and subject line Bug#638219: fixed in bzr-builddeb 2.7.8 has caused the Debian Bug report #638219, regarding bzr-builddeb: FTBFS: IOError: [Errno 20] Not a 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.) -- 638219: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=638219 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Source: bzr-builddeb Version: 2.7.7 Severity: serious Justification: fails to build from source bzr-builddeb FTBFS in unstable: | | Text attachment: traceback | | Traceback (most recent call last): | File /usr/lib/python2.7/dist-packages/testtools/runtest.py, line 169, in _run_user | return fn(*args, **kwargs) | File /usr/lib/python2.7/dist-packages/testtools/testcase.py, line 540, in _run_test_method | return self._get_test_method()() | File /build/bzr-builddeb-l5szVk/bzr-builddeb-2.7.7/tests/test_repack_tarball.py, line 133, in test_repack_tarball_with_target_dir_not_dir | self.new_tarball, target_dir=target_dir) | File /usr/lib/python2.7/dist-packages/bzrlib/tests/__init__.py, line 1486, in assertRaises | callableObj(*args, **kwargs) | File /build/bzr-builddeb-l5szVk/bzr-builddeb-2.7.7/repack_tarball.py, line 266, in repack_tarball | _repack_directory(target_transport, new_name, source_name) | File /build/bzr-builddeb-l5szVk/bzr-builddeb-2.7.7/repack_tarball.py, line 191, in _repack_directory | target_f = target_transport.open_write_stream(new_name) | File /usr/lib/python2.7/dist-packages/bzrlib/transport/local.py, line 331, in open_write_stream | handle = osutils.open_file(abspath, 'wb') | IOError: [Errno 20] Not a directory: u'/tmp/testbzr-2lQUSO.tmp/bzrlib.plugins.builddeb.tests.test_repack_tarball.TestRepackTarball.test_repack_tarball_with_target_dir_not_dir(dir)/work/tarballs/package_0.2.orig.tar.gz' | | | bzrlib.plugins.builddeb.tests.test_repack_tarball.TestRepackTarball.test_repack_tarball_with_target_dir_not_dir(.tar.gz)ERROR 7ms | Text attachment: log | | | | Text attachment: traceback-1 | | Traceback (most recent call last): | File /usr/lib/python2.7/dist-packages/testtools/runtest.py, line 169, in _run_user | return fn(*args, **kwargs) | File /usr/lib/python2.7/dist-packages/testtools/testcase.py, line 540, in _run_test_method | return self._get_test_method()() | File /build/bzr-builddeb-l5szVk/bzr-builddeb-2.7.7/tests/test_repack_tarball.py, line 133, in test_repack_tarball_with_target_dir_not_dir | self.new_tarball, target_dir=target_dir) | File /usr/lib/python2.7/dist-packages/bzrlib/tests/__init__.py, line 1486, in assertRaises | callableObj(*args, **kwargs) | File /build/bzr-builddeb-l5szVk/bzr-builddeb-2.7.7/repack_tarball.py, line 268, in repack_tarball | _repack_other(target_transport, new_name, source_name) | File /build/bzr-builddeb-l5szVk/bzr-builddeb-2.7.7/repack_tarball.py, line 209, in _repack_other | target_f = target_transport.open_write_stream(new_name) | File /usr/lib/python2.7/dist-packages/bzrlib/transport/local.py, line 331, in open_write_stream | handle = osutils.open_file(abspath, 'wb') | IOError: [Errno 20] Not a directory: u'/tmp/testbzr-2lQUSO.tmp/bzrlib.plugins.builddeb.tests.test_repack_tarball.TestRepackTarball.test_repack_tarball_with_target_dir_not_dir(.tar.gz)/work/tarballs/package_0.2.orig.tar.gz' | | | bzrlib.plugins.builddeb.tests.test_repack_tarball.TestRepackTarball.test_repack_tarball_with_target_dir_not_dir(.tar.bz2)ERROR 7ms | Text attachment: log | | | | Text attachment: traceback-2 | | Traceback (most recent call last): | File /usr/lib/python2.7/dist-packages/testtools/runtest.py, line 169, in _run_user | return fn(*args, **kwargs) | File /usr/lib/python2.7/dist-packages/testtools/testcase.py, line 540, in _run_test_method | return self._get_test_method()() | File /build/bzr-builddeb-l5szVk/bzr-builddeb-2.7.7/tests/test_repack_tarball.py, line 133, in test_repack_tarball_with_target_dir_not_dir | self.new_tarball, target_dir=target_dir) | File /usr/lib/python2.7/dist-packages/bzrlib/tests/__init__.py, line 1486, in assertRaises | callableObj(*args, **kwargs) | File /build/bzr-builddeb-l5szVk/bzr-builddeb-2.7.7/repack_tarball.py, line 268, in repack_tarball | _repack_other(target_transport, new_name, source_name) | File
Bug#639744: Compromised certificates for *.google.com issued by DigiNotar Root CA
On Tuesday 30 August 2011 15:48:11 Mike Hommey wrote: On Tue, Aug 30, 2011 at 09:58:18PM +0200, Yves-Alexis Perez wrote: On mar., 2011-08-30 at 12:29 -0500, Raphael Geissert wrote: What I can't tell for sure from the documentation is whether OpenSSL and GnuTLS do check the CRL's validity (signature and time.) It doesn't seem like they do. This is relevant if we were to ship them in ca-certificates. Mike, without digging into the documentation I found this reference [2] regarding NSS and its CRL support. Do you know if any of what is said on that email has changed? namely how 'next update' dates are handled. [2]http://www.mail-archive.com/mozilla-crypto@mozilla.org/msg00890.html Yves, do you know how the CRL stuff is handled in nss? (my first name is Yves-Alexis :) Oops, sorry. Please accept my apologies. That being said, there is a huge problem with mitigation in basically all the SSL libraries. There simply is no way to handle the current situation[1] without modifying applications. [...] 1. Several fraudulent certificates whose fingerprint is unknown signed with several different intermediate certs that are cross-signed by other safe CAs (aiui). Oh. Well, first thing first, I've NMUed ca-certs to remove the DigiNotar Root CA and will probably release a DSA with the change too (I'm afraid it will give a false sense of security.) What is to be done next should probably be discussed in -devel and have input from external people. Cheers, -- Raphael Geissert - Debian Developer www.debian.org - get.debian.net -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#639744: Compromised certificates for *.google.com issued by DigiNotar Root CA
On Tue, Aug 30, 2011 at 10:48:11PM +0200, Mike Hommey wrote: On Tue, Aug 30, 2011 at 09:58:18PM +0200, Yves-Alexis Perez wrote: On mar., 2011-08-30 at 12:29 -0500, Raphael Geissert wrote: On Tuesday 30 August 2011 01:08:29 Yves-Alexis Perez wrote: On lun., 2011-08-29 at 20:24 -0700, Josh Triplett wrote: I understand that they'd have to manually load the lists, but perhaps it would make sense to standardize a location from which they should load them? Does OpenSSL or GnuTLS have any concept of a revocation store format, similar to a certificate store, or would this need some special-purpose custom format? AFAIR they only know about CRL (Certificate Revocation List,) which only allows for one issuer per-file. What I can't tell for sure from the documentation is whether OpenSSL and GnuTLS do check the CRL's validity (signature and time.) It doesn't seem like they do. This is relevant if we were to ship them in ca-certificates. And it'd be nice if nss could share that store... [...] By the way, shouldn't this bug be clone to libnss3-1d (and maybe iceweasel and icedove if they ship the certificates themselves)? Perhaps it's time to start a discussion as to how we can properly deal with all this mess: * Multiple packages shipping their own certificates list * Probably no app except web browsers support CRLs and/or OCSP * configuration Yves, do you know how the CRL stuff is handled in nss? (my first name is Yves-Alexis :) I have no idea. There's a crlutil (http://www.mozilla.org/projects/security/pki/nss/tools/crlutil.html) but it works on previous database version (bdb, cert8.db and key3.db) while at least evolution now uses the shared sqlite db (cert9.db and key4.db, see https://wiki.mozilla.org/NSS_Shared_DB). The NSS tools are supposed to work with whatever database version you use, since they use NSS ;) That being said, there is a huge problem with mitigation in basically all the SSL libraries. There simply is no way to handle the current situation[1] without modifying applications. Mike 1. Several fraudulent certificates whose fingerprint is unknown signed with several different intermediate certs that are cross-signed by other safe CAs (aiui). So, I'll put that on tiredness. That'd be several fraudulent certificates which fingerprint is unknown (thus even CRL, OCSP and blacklists can't do anything), and the mitigation involves several different intermediate certs that are cross-signed, which makes it kind of hard. Plus, there is the problem that untrusting the DigiNotar root untrusts a separate PKI used by the Dutch government. Add to the above that untrusting a root still allows users to override in applications, and we have no central way to not allow that. Aiui, the mozilla update is going to block overrides as well, but that involves the application side. NSS won't deal with that. Mike -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#639744: Compromised certificates for *.google.com issued by DigiNotar Root CA
On Wed, Aug 31, 2011 at 06:26:26AM +0200, Mike Hommey wrote: On Tue, Aug 30, 2011 at 10:48:11PM +0200, Mike Hommey wrote: On Tue, Aug 30, 2011 at 09:58:18PM +0200, Yves-Alexis Perez wrote: On mar., 2011-08-30 at 12:29 -0500, Raphael Geissert wrote: On Tuesday 30 August 2011 01:08:29 Yves-Alexis Perez wrote: On lun., 2011-08-29 at 20:24 -0700, Josh Triplett wrote: I understand that they'd have to manually load the lists, but perhaps it would make sense to standardize a location from which they should load them? Does OpenSSL or GnuTLS have any concept of a revocation store format, similar to a certificate store, or would this need some special-purpose custom format? AFAIR they only know about CRL (Certificate Revocation List,) which only allows for one issuer per-file. What I can't tell for sure from the documentation is whether OpenSSL and GnuTLS do check the CRL's validity (signature and time.) It doesn't seem like they do. This is relevant if we were to ship them in ca-certificates. And it'd be nice if nss could share that store... [...] By the way, shouldn't this bug be clone to libnss3-1d (and maybe iceweasel and icedove if they ship the certificates themselves)? Perhaps it's time to start a discussion as to how we can properly deal with all this mess: * Multiple packages shipping their own certificates list * Probably no app except web browsers support CRLs and/or OCSP * configuration Yves, do you know how the CRL stuff is handled in nss? (my first name is Yves-Alexis :) I have no idea. There's a crlutil (http://www.mozilla.org/projects/security/pki/nss/tools/crlutil.html) but it works on previous database version (bdb, cert8.db and key3.db) while at least evolution now uses the shared sqlite db (cert9.db and key4.db, see https://wiki.mozilla.org/NSS_Shared_DB). The NSS tools are supposed to work with whatever database version you use, since they use NSS ;) That being said, there is a huge problem with mitigation in basically all the SSL libraries. There simply is no way to handle the current situation[1] without modifying applications. Mike 1. Several fraudulent certificates whose fingerprint is unknown signed with several different intermediate certs that are cross-signed by other safe CAs (aiui). So, I'll put that on tiredness. That'd be several fraudulent certificates which fingerprint is unknown (thus even CRL, OCSP and blacklists can't do anything), and the mitigation involves several different intermediate certs that are cross-signed, which makes it kind of hard. Plus, there is the problem that untrusting the DigiNotar root untrusts a separate PKI used by the Dutch government. Add to the above that untrusting a root still allows users to override in applications, and we have no central way to not allow that. Aiui, the mozilla update is going to block overrides as well, but that involves the application side. NSS won't deal with that. See https://bugzilla.mozilla.org/show_bug.cgi?id=682927 which is now open. Mike -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed: reassign 639852 to libgnomevfs2-0, forcibly merging 626076 639852
Processing commands for cont...@bugs.debian.org: reassign 639852 libgnomevfs2-0 Bug #639852 [iceweasel] iceweasel crashes on attempt run config editor Bug reassigned from package 'iceweasel' to 'libgnomevfs2-0'. Bug No longer marked as found in versions iceweasel/5.0-6. forcemerge 626076 639852 Bug#626076: Firefox crashes, error message: libfile.so: undefined symbol: gnome_vfs_unescape_string Bug#639852: iceweasel crashes on attempt run config editor Bug#637359: iceweasel: exits when I open download window Bug#637960: [iceweasel] Crash when download anything from internet Bug#638023: iceweasel: Iceweasel crash while saving image to disk Bug#638065: [iceweasel] crash when accessing Preference/General tab (undefined symbol: gnome_vfs_unescape_string) Bug#638892: iceweasel crash when I press to save a file Bug#639457: iceweasel: Symbol lookup error (gnome_vfs_unescape_string) Bug#639746: iceweasel: Crashes on preferences/general or preferences/applications tab Forcibly Merged 626076 637359 637960 638023 638065 638892 639457 639746 639852. thanks Stopping processing here. Please contact me if you need assistance. -- 639746: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=639746 638892: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=638892 626076: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=626076 639457: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=639457 637359: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=637359 637960: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=637960 638065: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=638065 639852: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=639852 638023: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=638023 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: forcibly merging 636514 637948
Processing commands for cont...@bugs.debian.org: forcemerge 636514 637948 Bug#636514: icedtea-plugin: obsolete (and unneeded?) dependency on xulrunner-1.9.1 Bug#637948: icedtea-plugin (testing) depends on obsolete package. Forcibly Merged 636514 637948. thanks Stopping processing here. Please contact me if you need assistance. -- 637948: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=637948 636514: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=636514 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#639744: Compromised certificates for *.google.com issued by DigiNotar Root CA
On Tue, Aug 30, 2011 at 10:49:04PM -0500, Raphael Geissert wrote: On Tuesday 30 August 2011 15:48:11 Mike Hommey wrote: On Tue, Aug 30, 2011 at 09:58:18PM +0200, Yves-Alexis Perez wrote: On mar., 2011-08-30 at 12:29 -0500, Raphael Geissert wrote: What I can't tell for sure from the documentation is whether OpenSSL and GnuTLS do check the CRL's validity (signature and time.) It doesn't seem like they do. This is relevant if we were to ship them in ca-certificates. Mike, without digging into the documentation I found this reference [2] regarding NSS and its CRL support. Do you know if any of what is said on that email has changed? namely how 'next update' dates are handled. [2]http://www.mail-archive.com/mozilla-crypto@mozilla.org/msg00890.html I think CRL handling is still mostly manual work. I don't know much more though. Mike -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
