Processed: your mail
Processing commands for cont...@bugs.debian.org:
> tag 673659 + pending
Bug #673659 {Done: Didier Raboud } [src:pyside] pyside: FTBFS
in sid: missing symbols
Added tag(s) pending.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
673659: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=673659
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#674341: mpfi: FTBFS: tests failed
Hello Lucas,
On Thu, May 24, 2012 at 2:54 AM, Lucas Nussbaum
wrote:
>> /bin/bash: line 5: 19652 Segmentation fault ${dir}$tst
>> FAIL: tsub_fr
Thanks for your report. I think this bug was fixed upstream in 1.5.1.
I'll upgrade soonish.
Laurent.
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#674510: nova-common: fails to remove: missing dependency on sqlite3?
Package: nova-common Version: 2012.1-4 Severity: serious User: debian...@lists.debian.org Usertags: piuparts Hi, during a test with piuparts I noticed your package fails to remove. >From the attached log (scroll to the bottom...): apt-get remove ... nova-common [...] Removing nova-common ... dbconfig-common: dumping sqlite3 database nova.sqlite to /var/tmp/nova-common.nova.sqlite.2012-05-24-20.09.sqlite3.pPrdZq. sanity check failed for sqlite3. error encountered dumping database: No sqlite3 client to execute. (have you installed the sqlite3 package?) dbconfig-common: nova-common remove: aborted. dpkg: error processing nova-common (--remove): subprocess installed pre-removal script returned error exit status 1 cheers, Andreas nova-common_2012.1-4.log.gz Description: GNU Zip compressed data
Bug#674460: initscripts: prompting due to modified conffiles which were not modified by the user
Hi Roger,
thanks for looking into this.
Prompting the user for some essential/required package converting a
config file to a conffile would probably annoy many users (and would
require bad workarounds for tools like piuparts ...).
On 2012-05-25 00:52, Roger Leigh wrote:
> So how best to avoid the prompt? I guess in the preinst we
> could, if the md5sum matches one of the above 79 sums, we can
> replace it with the current version, moving it to .dpkg-old.
> Along with a suitable warning.
>
> I'm not sure this case is really covered by the existing
> Dpkg conffile handling cases.
The "config file" to "conffile" case is not well supported by any tools
so far.
Probably this is something that could be done by dpkg-maintscript-helper
in the future once it is clear how to do it safely.
So if you come up with some generic maintainer script snippets other
maintainers probably would be thankful. Recently base-files wanted to
make /etc/profile a conffile (but reverted because of a missing solution
how to avoid prompting) and sudo does it as well (using exactly one
md5sum covering only upgrades from squeeze, nothing older).
If moving /etc/default/rcS to .dpkg-{old,bak,foo} in the preinst is not
safe unless a new one is installed immediately, a copy of the new
version will have to be embedded in the preinst script ... another
reason to generate that part of the maintainer script code+data ...
Andreas
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#674504: swift-im and swift: error when trying to install together
Package: swift,swift-im Version: swift/1.4.8-1 Version: swift-im/2.0~beta1+dev26-1 Severity: serious User: trei...@debian.org Usertags: edos-file-overwrite Date: 2012-05-25 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! libpcre3 libxml2 libxau6 x11-common libice6 libsm6 libxdmcp6 libxcb1 libx11-data libx11-6 libxt6 libaudio2 libdbus-1-3 libexpat1 libffi5 libfreetype6 ucf ttf-dejavu-core fontconfig-config libfontconfig1 libglib2.0-0 libgstreamer0.10-0 liborc-0.4-0 iso-codes libgstreamer-plugins-base0.10-0 libicu48 libjpeg8 liblcms1 libmng1 libpng12-0 libqtcore4 libqt4-xml qdbus libqt4-dbus libqt4-network fontconfig libjbig0 libtiff4 libxext6 libxrender1 libqtgui4 libqtwebkit4 libxss1 mime-support python2.7-minimal python2.7 python-minimal python python-support libboost-date-time1.49.0 libboost-system1.49.0 libboost-filesystem1.49.0 libboost-program-options1.49.0 libboost-regex1.49.0 libboost-signals1.49.0 libboost-thread1.49.0 libjs-jquery libjs-underscore libjs-sphinxdoc libswiften2 python-greenlet python-eventlet python-netifaces python-openssl python-pkg-resources python-pastedeploy python-setuptools python-simplejson python-webob python-xattr python-swift swift swift-im Extracting templates from packages: 41% Extracting templates from packages: 82% Extracting templates from packages: 100% Preconfiguring packages ... Authentication warning overridden. Can not write log, openpty() failed (/dev/pts not mounted?) Selecting previously unselected package libpcre3:amd64. (Reading database ... 10575 files and directories currently installed.) Unpacking libpcre3:amd64 (from .../libpcre3_1%3a8.30-5_amd64.deb) ... Selecting previously unselected package libxml2:amd64. Unpacking libxml2:amd64 (from .../libxml2_2.7.8.dfsg-9.1_amd64.deb) ... Selecting previously unselected package libxau6:amd64. Unpacking libxau6:amd64 (from .../libxau6_1%3a1.0.7-1_amd64.deb) ... Selecting previously unselected package x11-common. Unpacking x11-common (from .../x11-common_1%3a7.6+13_all.deb) ... Selecting previously unselected package libice6:amd64. Unpacking libice6:amd64 (from .../libice6_2%3a1.0.8-2_amd64.deb) ... Selecting previously unselected package libsm6:amd64. Unpacking libsm6:amd64 (from .../libsm6_2%3a1.2.1-2_amd64.deb) ... Selecting previously unselected package libxdmcp6:amd64. Unpacking libxdmcp6:amd64 (from .../libxdmcp6_1%3a1.1.1-1_amd64.deb) ... Selecting previously unselected package libxcb1:amd64. Unpacking libxcb1:amd64 (from .../libxcb1_1.8.1-1_amd64.deb) ... Selecting previously unselected package libx11-data. Unpacking libx11-data (from .../libx11-data_2%3a1.4.99.901-2_all.deb) ... Selecting previously unselected package libx11-6:amd64. Unpacking libx11-6:amd64 (from .../libx11-6_2%3a1.4.99.901-2_amd64.deb) ... Selecting previously unselected package libxt6:amd64. Unpacking libxt6:amd64 (from .../libxt6_1%3a1.1.3-1_amd64.deb) ... Selecting previously unselected package libaudio2:amd64. Unpacking libaudio2:amd64 (from .../libaudio2_1.9.3-5_amd64.deb) ... Selecting previously unselected package libdbus-1-3:amd64. Unpacking libdbus-1-3:amd64 (from .../libdbus-1-3_1.5.12-1_amd64.deb) ... Selecting previously unselected package libexpat1:amd64. Unpacking libexpat1:amd64 (from .../libexpat1_2.1.0-1_amd64.deb) ... Selecting previously unselected package libffi5:amd64. Unpacking libffi5:amd64 (from .../libffi5_3.0.10-3_amd64.deb) ... Selecting previously unselected package libfreetype6:amd64. Unpacking libfreetype6:amd64 (from .../libfreetype6_2.4.9-1_amd64.deb) ... Selecting previously unselected package ucf. Unpacking ucf (from .../ucf_3.0025+nmu3_all.deb) ... Moving old data out of the way Selecting previously unselected package ttf-dejavu-core. Unpacking ttf-dejavu-core (from .../ttf-dejavu-core_2.33-2_all.deb) ... Selecting previously unselected package fontconfig-config. Unpacking fontconfig-config (from .../fontconfig-config_2.9.0-5_all.deb) ... Selecting previously unselected package libfontconfig1:amd64. Unpacking libfontconfig1:amd64 (from .../libfontconfig1_2.9.0-5_amd64.deb) ... Selecting previously unselected package libglib2.0-0:amd64. Unpacking libglib2.0-0:amd64 (from .../libglib2.0-0_2.32.3-1_amd64.deb) ... Selecting previously unselected package libgstreamer0.10-0:amd64. Unpacking libgstreamer0.10-0:amd64 (from .../libgstreamer0.10-0_0.10.36-1_amd64.deb) ... Selecting previously unselected package liborc-0.4-0:amd64. Unpacking liborc-0.4-0:amd64 (from .../liborc-0.4-0_1%3a0.4.16-2_amd64.deb) ... Selecting previously unselected package iso-codes. Unpacking iso-codes (from .../iso-codes_3.35-1_all.deb) ... Selecting previously unselected package libgstreamer-plugins-base0.10-0:amd64. Unpacking libgstreamer-plugins-base0.10-0:amd64 (from .../li
Bug#669435: marked as done (mokomaze: FTBFS: configure.ac:19: error: possibly undefined macro: AM_GLIB_GNU_GETTEXT)
Your message dated Fri, 25 May 2012 04:02:27 + with message-id and subject line Bug#669435: fixed in mokomaze 0.5.5+git8+dfsg0-3 has caused the Debian Bug report #669435, regarding mokomaze: FTBFS: configure.ac:19: error: possibly undefined macro: AM_GLIB_GNU_GETTEXT 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.) -- 669435: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=669435 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: mokomaze Version: 0.5.5+git8+dfsg0-2 Severity: serious Tags: wheezy sid User: debian...@lists.debian.org Usertags: qa-ftbfs-20120419 qa-ftbfs Justification: FTBFS on amd64 Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part: > debian/rules build > autoreconf -vfi > autoreconf: Entering directory `.' > autoreconf: configure.ac: not using Gettext > autoreconf: running: aclocal --force > configure.ac:19: warning: macro `AM_GLIB_GNU_GETTEXT' not found in library > autoreconf: configure.ac: tracing > autoreconf: running: libtoolize --copy --force > libtoolize: putting auxiliary files in `.'. > libtoolize: copying file `./ltmain.sh' > libtoolize: Consider adding `AC_CONFIG_MACRO_DIR([m4])' to configure.ac and > libtoolize: rerunning libtoolize, to keep the correct libtool macros in-tree. > libtoolize: Consider adding `-I m4' to ACLOCAL_AMFLAGS in Makefile.am. > configure.ac:19: warning: macro `AM_GLIB_GNU_GETTEXT' not found in library > autoreconf: running: /usr/bin/autoconf --force > configure.ac:19: error: possibly undefined macro: AM_GLIB_GNU_GETTEXT > If this token and others are legitimate, please use m4_pattern_allow. > See the Autoconf documentation. > autoreconf: /usr/bin/autoconf failed with exit status: 1 > make: *** [build-stamp] Error 1 The full build log is available from: http://people.debian.org/~lucas/logs/2012/04/19/mokomaze_0.5.5+git8+dfsg0-2_unstable.log 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. --- End Message --- --- Begin Message --- Source: mokomaze Source-Version: 0.5.5+git8+dfsg0-3 We believe that the bug you reported is fixed in the latest version of mokomaze, which is due to be installed in the Debian FTP archive: mokomaze_0.5.5+git8+dfsg0-3.diff.gz to main/m/mokomaze/mokomaze_0.5.5+git8+dfsg0-3.diff.gz mokomaze_0.5.5+git8+dfsg0-3.dsc to main/m/mokomaze/mokomaze_0.5.5+git8+dfsg0-3.dsc mokomaze_0.5.5+git8+dfsg0-3_amd64.deb to main/m/mokomaze/mokomaze_0.5.5+git8+dfsg0-3_amd64.deb A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 669...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Paul Wise (supplier of updated mokomaze package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Fri, 25 May 2012 11:46:40 +0800 Source: mokomaze Binary: mokomaze Architecture: source amd64 Version: 0.5.5+git8+dfsg0-3 Distribution: unstable Urgency: low Maintainer: Debian FreeSmartphone.Org Team Changed-By: Paul Wise Description: mokomaze - Ball in labyrinth game for the OpenMoko FreeRunner Closes: 669435 Changes: mokomaze (0.5.5+git8+dfsg0-3) unstable; urgency=low . * Add missing build-dep on libglib2.0-dev (Closes: #669435) * Fix the Homepage again Checksums-Sha1: 5e512bd4ef2c371aad13977bd4daf9c9f87b35e4 2196 mokomaze_0.5.5+git8+dfsg0-3.dsc afd853a05962bfc66a5165bec16988f4547037b5 548272 mokomaze_0.5.5+git8+dfsg0-3.diff.gz 3b08cfdee03d46087625456c5f4b644b157c648c 516608 mokomaze_0.5.5+git8+dfsg0-3_amd64.deb Checksums-Sha256: 4d616d0b23caa29d97574d3ddfd5f96d04fa79b5a1084afd5c4d0add984077b9 2196 mokomaze_0.5.5+git8+dfsg0-3.dsc c723c25f86d72b4dd22e7a521d358a0266e1114dd002a9532acb012b8f70dc99 548272 mokomaze_0.5.5+git8+dfsg0-3.diff.gz 8eeb35d0de3317b20ff16bed8de2bbcfb5f224ede4f09e16f439ac3d23d45ce7 516608 mokomaze_0.5.5+git8+dfsg0-3_amd64.deb Files: 6b80b630c31c891e4277a7280daef4c9 2196 games extra mokomaze_0.5.5+git8+dfsg0-3.dsc c8cf30b435efb008bf866
Processed: tagging 669435
Processing commands for cont...@bugs.debian.org: > # no patch available > tags 669435 - patch Bug #669435 [src:mokomaze] mokomaze: FTBFS: configure.ac:19: error: possibly undefined macro: AM_GLIB_GNU_GETTEXT Removed tag(s) patch. > thanks Stopping processing here. Please contact me if you need assistance. -- 669435: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=669435 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#674471: FTBFS: (armel, sparc) error when testing
tags 674471 + patch
thanks
Osamu Aoki writes:
> This package does not build on armel which is release architecture
> (and sparc).
>
> https://buildd.debian.org/status/fetch.php?pkg=libskk&arch=armel&ver=0.0.12-1&stamp=1333795311
>
>
> **
> ERROR:cdb-dict.c:23:cdb_dict: assertion failed (len == 2): (0 == 2)
> /bin/bash: line 5: 27443 Aborted G_DEBUG=gc-friendly
> G_SLICE=,always-malloc LIBSKK_DATA_PATH=.. /bin/bash ../libtool
> --mode=execute ${dir}$tst
> /libskk/cdb-dict: FAIL: cdb-dict
> ...
> ==
> 1 of 8 tests failed
Thanks. It seems to be an ARM alignment issue (patch attached). I'll
upload a new package soon.
>From fbbea6190782da447caddc903cbc31a0d8676f38 Mon Sep 17 00:00:00 2001
From: Daiki Ueno
Date: Fri, 25 May 2012 11:19:43 +0900
Subject: [PATCH] cdb: make sure that integer does not stride across 4-byte
alignments
Fixes Debian bug#674471.
---
libskk/cdb-dict.vala |5 -
1 file changed, 4 insertions(+), 1 deletion(-)
diff --git a/libskk/cdb-dict.vala b/libskk/cdb-dict.vala
index a5a49fa..db2c99b 100644
--- a/libskk/cdb-dict.vala
+++ b/libskk/cdb-dict.vala
@@ -51,7 +51,10 @@ namespace Skk {
}
static uint32 read_uint32 (uint8 *p) {
-return uint32.from_little_endian (*((uint32 *) p));
+// Make sure that Q does not stride across 4-byte
+// alignment on ARM (Debian bug#674471).
+uint8 q[4] = (uint8[]) p;
+return uint32.from_little_endian (*((uint32 *) q));
}
/**
--
1.7.10.1
Regards,
--
Daiki Ueno
Bug#673594: ruby1.8: FTBFS[kfreebsd-*]: test-all hangs/segfaults
clone 673594 -1 severity -1 important retitle -1 ruby1.8: threaded code segfaults under kfreebsd-* tags 673594 + pending thanks Hi Steven, Steven Chamberlain escreveu isso aí: > Whereas the buildds experience hangs during some tests, I see segfaults > instead. This sometimes happens even before the first test has been run. > > This small Ruby testcase results in segfault 50% of the time under > ruby1.8 1.8.7.358-2, but always succeeds with ruby1.9.1 1.9.3.0-2: > > > require 'thread' > > Thread.new do > > foo = "bar" > > end > > (Measured out of 100 runs, on kfreebsd-i386 with 4-way SMP) > > Attached are outputs from ktrace for a success and from a failure; then > I've tried to diff them. There seems to be a race whereby thread0 tries > to call thr_kill on thread2, but if that happens too late thread2 will > trigger a segfault instead. Thanks for the patch. I am preparing an upload to workaround the test timeout and make the FTBFS go away ASAP. If you can prepare a patch to fix the race condition, please attach it to the new bug report which I am creating by cloning this one. -- Antonio Terceiro signature.asc Description: Digital signature
Processed: Re: Bug#623578 closed by Matthias Klose (Bug#623578: fixed in gadfly 1.0.0-15)
Processing commands for cont...@bugs.debian.org:
> reopen 623578
Bug #623578 {Done: Matthias Klose } [gadfly] gadfly: build
wrong version of the packaging during a binNMU
'reopen' may be inappropriate when a bug has been closed with a version;
all fixed versions will be cleared, and you may need to re-add them.
Bug reopened
No longer marked as fixed in versions gadfly/1.0.0-15.
> found 623578 1.0.0-15
Bug #623578 [gadfly] gadfly: build wrong version of the packaging during a
binNMU
Marked as found in versions gadfly/1.0.0-15.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
623578: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=623578
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#623578: closed by Matthias Klose (Bug#623578: fixed in gadfly 1.0.0-15)
reopen 623578 found 623578 1.0.0-15 thanks Debian Bug Tracking System, le Thu 21 Apr 2011 18:51:09 +, a écrit : > #623578: gadfly: build wrong version of the packaging during a binNMU > > It has been closed by Matthias Klose . Err, no, the bug is still there, binNMUs still get built wrongly: drwxr-xr-x 7 samy samy 300 mai 25 02:58 gadfly-1.0.0/ -rw-r--r-- 1 samy samy 65K mai 25 02:58 python-kjbuckets_1.0.0-15_amd64.deb -rw-r--r-- 1 samy samy 896 mai 25 02:58 gadfly_1.0.0-15+b1_amd64.changes This is apparently due to this: dh_gencontrol -a -- -v'$(kjb_version)' Why setting that particular version and not let it use the changelog version? Samuel -- 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 674479 is important
Processing commands for cont...@bugs.debian.org: > severity 674479 important Bug #674479 [libldap-2.4-2] libldap-2.4-2: Please include OpenLDAP ITS#7167 patch Severity set to 'important' from 'critical' > thanks Stopping processing here. Please contact me if you need assistance. -- 674479: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=674479 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#674479: libldap-2.4-2: Please include OpenLDAP ITS#7167 patch
Package: libldap-2.4-2 Version: 2.4.28-1.3 Severity: critical Tags: upstream Justification: breaks the whole system Hi, Please include the patch from OpenLDAP ITS#7167 (not sure whether it's a in a released version yet) to unbreak the system. Without this patch, logins on systems using sssd (with libpam-sss) are completely broken. Wouter -- System Information: Debian Release: wheezy/sid APT prefers testing APT policy: (990, 'testing'), (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 3.1.0-1-amd64 (SMP w/2 CPU cores) Locale: LANG=nl_NL.UTF-8, LC_CTYPE=nl_NL.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages libldap-2.4-2 depends on: ii libc6 2.13-32 ii libgcrypt111.5.0-3 ii libgnutls262.12.19-1 ii libsasl2-2 2.1.25.dfsg1-4 ii multiarch-support 2.13-32 libldap-2.4-2 recommends no packages. libldap-2.4-2 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#674460: initscripts: prompting due to modified conffiles which were not modified by the user
On Thu, May 24, 2012 at 10:20:35PM +0100, Roger Leigh wrote: > On Thu, May 24, 2012 at 09:50:51PM +0200, Andreas Beckmann wrote: > > during a test with piuparts I noticed your package failed the piuparts > > upgrade test because dpkg detected a conffile as being modified and then > > prompted the user for an action. As there is no user input, this fails. > > But this is not the real problem, the real problem is that this prompt > > shows up in the first place, as there was nobody modifying this conffile > > at all, the package has just been installed and upgraded... > > > > This is a violation of policy 10.7.3, see > > http://www.debian.org/doc/debian-policy/ch-files.html#s10.7.3, > > which says "[These scripts handling conffiles] must not ask unnecessary > > questions (particularly during upgrades), and must otherwise be good > > citizens." > > > > Configuration file `/etc/default/rcS' > > > > This was observed on a distupgrade from sid to experimental. > > There needs to be a way to detect if /etc/default/rcS is "unmodified" > > (and there are probably a lot of different unmodified variants that > > should allow seamless upgrades) before it's made a conffile. > > rcS was previously not a conffile, and was modified by the installer > to set the UTC setting. In the last few releases, we temporarily > managed it using ucf. But now the UTC setting is gone (migrated to > /etc/adjtime), there's no reason why it can't be a regular conffile. > > If the issue is that we don't detect earlier "unmodified" forms, > we can potentially handle this case with a list of md5sums. > However... given that a number of different scripts edit this > including > - debian-installer clock-setup > - util-linux maintainer scripts > - initscripts maintainer scripts > - potentially others, I'd need to check > the number of combinations is not trivial to deal with, given that > we need every variant/ordering of every rcS version ever provided, > given that the base file is only ever installed once, on initial > installation. > > We can look at doing this though. OK, so I've generated a set of potential unmodified candidates to consider (attached). So we have the md5sums of 79 unique files which could be potentially considered unmodified. This is all versions of rcS (from git, back to 2005), with all combinations of the following: - UTC set to yes or no - UTC obsoleted - RAM* and EDITMOTD obsoleted (done together) So how best to avoid the prompt? I guess in the preinst we could, if the md5sum matches one of the above 79 sums, we can replace it with the current version, moving it to .dpkg-old. Along with a suitable warning. I'm not sure this case is really covered by the existing Dpkg conffile handling cases. Regards, Roger -- .''`. Roger Leigh : :' : Debian GNU/Linuxhttp://people.debian.org/~rleigh/ `. `' schroot and sbuild http://alioth.debian.org/projects/buildd-tools `-GPG Public Key F33D 281D 470A B443 6756 147C 07B3 C8BC 4083 E800 sysvinit-rcS.tar.xz Description: Binary data
Bug#669386: marked as done (plywood: unowned file /usr/local/share/texmf/ls-R after purge (policy 6.8, 9.1.2))
Your message dated Thu, 24 May 2012 22:49:00 + with message-id and subject line Bug#669386: fixed in plywood 0.5.11+nmu2 has caused the Debian Bug report #669386, regarding plywood: unowned file /usr/local/share/texmf/ls-R after purge (policy 6.8, 9.1.2) to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 669386: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=669386 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: plywood Version: 0.5.11+nmu1 Severity: serious User: debian...@lists.debian.org Usertags: piuparts Hi, during a test with piuparts I noticed your package left unowned files on the system after purge, which is a violation of policy 6.8: http://www.debian.org/doc/debian-policy/ch-maintainerscripts.html#s-removedetails As putting files into /usr/local is also a violation of http://www.debian.org/doc/debian-policy/ch-opersys.html#s9.1.2 I'm setting the severity to serious. >From the attached log (scroll to the bottom...): 0m53.8s ERROR: FAIL: Package purging left files on system: /usr/local/share/texmf/not owned /usr/local/share/texmf/ls-Rnot owned This problem is usually caused by running mktexlsr (or texhash) without path arguments from a maintainer script. The recommende solution is to switch to use dh_installtex and have this generate most (or perhaps even all) of the maintainer scripts content. Otherwise run mktexlsr with the tree as argument where the package installs its files, which is usually mktexlsr /usr/share/texmf There has been some further discussion about these bugs in this thread: http://lists.debian.org/debian-tex-maint/2012/04/msg00306.html Please have a look at the Debian-TeX-Policy (in the tex-common package) for the current practice of handling TeX packages. For further TeX packaging related questions contact debian-tex-ma...@lists.debian.org cheers, Andreas plywood_0.5.11+nmu1.log.gz Description: GNU Zip compressed data --- End Message --- --- Begin Message --- Source: plywood Source-Version: 0.5.11+nmu2 We believe that the bug you reported is fixed in the latest version of plywood, which is due to be installed in the Debian FTP archive: plywood_0.5.11+nmu2.dsc to main/p/plywood/plywood_0.5.11+nmu2.dsc plywood_0.5.11+nmu2.tar.gz to main/p/plywood/plywood_0.5.11+nmu2.tar.gz plywood_0.5.11+nmu2_all.deb to main/p/plywood/plywood_0.5.11+nmu2_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 669...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Matej Vela (supplier of updated plywood 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, 22 May 2012 22:30:43 +0100 Source: plywood Binary: plywood Architecture: source all Version: 0.5.11+nmu2 Distribution: unstable Urgency: low Maintainer: Monty Taylor Changed-By: Matej Vela Description: plywood- Playwriting typing and typesetting help Closes: 601483 645257 669386 Changes: plywood (0.5.11+nmu2) unstable; urgency=low . * Non-maintainer upload. * Use dh_installtex rather than mktexlsr directly. Closes: #669386. * Update dependencies for wheezy: - Depend on python-pkg-resources. Closes: #645257. - Depend on emacs23 | emacsen instead of emacs21 | emacs20 | emacsen. - Suggest ghostscript instead of gs. Closes: #601483. Checksums-Sha1: 33b8a01c6c7c9a32cb19f179be27fab8d522894b 896 plywood_0.5.11+nmu2.dsc 36b771afbfb83c35e1a2288d9f7aa2df84e72d37 121742 plywood_0.5.11+nmu2.tar.gz 65f1672eafbdb1f03f4b19215d23d2466f2a6f2d 55734 plywood_0.5.11+nmu2_all.deb Checksums-Sha256: b8bb7fa16f4b19602ddaf26ce5d2813ad2bad51f4b284b1fa06fdecd98463e0e 896 plywood_0.5.11+nmu2.dsc 8f9d866359723e81779adbd008e6ce75bb029807821ed79544e5516be4b314eb 121742 plywood_0.5.11+nmu2.tar.gz 081ec333861ecfb3fd8908729da0c1e1a22fdf9f868c86277c18a51b1ac30e83 55734 plywood_0.5.11+nmu2_all.deb Files: 35a6419977179fcd9eb630bd32324838 896 text optional plywood_0.5.11+nmu2.dsc 4e0068d2e0f0786d99ae225dc2545db2 121742 text optional plywood_0.5.11+nmu2.tar.gz 44d90c64698d7faa192e005089fa5ae2 55734 text optional plywood_0.5.11+nmu2_all.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.12 (GNU/Linux) iEYEARECAAYFAk+8D2MAC
Bug#673681: marked as done (eegdev; FTBFS[kfreebsd]: testsuite failure)
Your message dated Thu, 24 May 2012 22:33:12 + with message-id and subject line Bug#673681: fixed in eegdev 0.2-3 has caused the Debian Bug report #673681, regarding eegdev; FTBFS[kfreebsd]: testsuite failure 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.) -- 673681: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=673681 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:eegdev Version: 0.2-1 Severity: serious Tags: sid wheezy User: debian-...@lists.debian.org Usertags: kfreebsd X-Debbugs-Cc: debian-...@lists.debian.org Justification: fails to build from source (but built successfully in the past) Hi! Your package failed to build on the kfreebsd-* buildds: make check-TESTS make[4]: Entering directory `/build/buildd-eegdev_0.2-1-kfreebsd-i386-LGFJWW/eegdev-0.2/tests' PASS: verify-cast.sh PASS: verifysplit PASS: syseegfile *** glibc detected *** /build/buildd-eegdev_0.2-1-kfreebsd-i386-LGFJWW/eegdev-0.2/tests/.libs/lt-sysbiosemi: double free or corruption (out): 0xbfbfdf98 *** Testing biosemi with float data type Aborted (core dumped) *** glibc detected *** /build/buildd-eegdev_0.2-1-kfreebsd-i386-LGFJWW/eegdev-0.2/tests/.libs/lt-sysbiosemi: double free or corruption (out): 0xbfbfdf98 *** Testing biosemi with double data type Aborted (core dumped) FAIL: testfakeact2.sh Testing tobiia PASS: testfaketobiia.sh = 1 of 5 tests failed Please report to nicolas.bourd...@epfl.ch = Full build log at https://buildd.debian.org/status/fetch.php?pkg=eegdev&arch=kfreebsd-i386&ver=0.2-1&stamp=1337329119 Regards Christoph If you have further questions please mail debian-...@lists.debian.org -- 9FED 5C6C E206 B70A 5857 70CA 9655 22B9 D49A E731 Debian Developer | Lisp Hacker | CaCert Assurer --- End Message --- --- Begin Message --- Source: eegdev Source-Version: 0.2-3 We believe that the bug you reported is fixed in the latest version of eegdev, which is due to be installed in the Debian FTP archive: eegdev-plugins-free_0.2-3_amd64.deb to main/e/eegdev/eegdev-plugins-free_0.2-3_amd64.deb eegdev_0.2-3.debian.tar.gz to main/e/eegdev/eegdev_0.2-3.debian.tar.gz eegdev_0.2-3.dsc to main/e/eegdev/eegdev_0.2-3.dsc libeegdev-dev_0.2-3_amd64.deb to main/e/eegdev/libeegdev-dev_0.2-3_amd64.deb libeegdev0-dbg_0.2-3_amd64.deb to main/e/eegdev/libeegdev0-dbg_0.2-3_amd64.deb libeegdev0_0.2-3_amd64.deb to main/e/eegdev/libeegdev0_0.2-3_amd64.deb A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 673...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Nicolas Bourdaud (supplier of updated eegdev package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.8 Date: Wed, 23 May 2012 16:04:42 +0200 Source: eegdev Binary: libeegdev0 eegdev-plugins-free libeegdev-dev libeegdev0-dbg Architecture: source amd64 Version: 0.2-3 Distribution: unstable Urgency: low Maintainer: Nicolas Bourdaud Changed-By: Nicolas Bourdaud Description: eegdev-plugins-free - Biosignal acquisition device library (free plugins) libeegdev-dev - Biosignal acquisition device library (Developement files) libeegdev0 - Biosignal acquisition device library libeegdev0-dbg - Biosignal acquisition device library (Debugging symbols) Closes: 673681 Changes: eegdev (0.2-3) unstable; urgency=low . * Fix hangups when closing biosemi. (Closes: #673681) - new patch fix-biosemi-close-hangups.patch Checksums-Sha1: b550f31c00606fb9e69577dfba6e30e9258743d4 1451 eegdev_0.2-3.dsc 68cd1a8683db623c7d76bdc1f2aece8693091f2d 8465 eegdev_0.2-3.debian.tar.gz 62f465f7e305e3634baafd8b16a0361ac034ca7f 46080 libeegdev0_0.2-3_amd64.deb 734fb00adcd97fa0f3a4bf3c91421922de563671 29082 eegdev-plugins-free_0.2-3_amd64.deb 4a958927d60fa16a8c72830312f33a6765c67856 22410 libeegdev-dev_0.2-3_amd64.deb 4a3719f86de077dbaaff2b33b3a5868ac61b9692 166244 libeegdev0-dbg_0.2-3_amd64.deb Checksums-Sha256: 6a92839261a39e2ee39b64c4c8362be5f20341630de938552184b2591ff9c3d4 1451 eegdev_0.2-3.dsc 06897f2f075a28efa7cab7cd5d674500ad8f307d9985e0921939c4c756af1dcf 8465 eegdev_0.2-3.debian.tar.gz 100b78b8c76812a073f9b1efb878c97ab59
Processed: forgot to put second closed bug into commit message/changelog entry...
Processing commands for cont...@bugs.debian.org: > fixed 672414 1.2.3-0.2 Bug #672414 [wine] FTBFS on kfreebsd-i386 Marked as fixed in versions wine/1.2.3-0.2. > thank you Stopping processing here. Please contact me if you need assistance. -- 672414: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=672414 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#674419: gnome-shell: segfaults in libaccountservice
On Do, 24 Mai 2012, Michael Biebl wrote:
> reassign 674419 libaccountsservice0
> forcemerge 673185 674419
Indeed, thanks.
Best wishes
Norbert
Norbert Preiningpreining@{jaist.ac.jp, logic.at, debian.org}
JAIST, Japan TeX Live & Debian Developer
DSA: 0x09C5B094 fp: 14DF 2E6C 0307 BE6D AD76 A9C0 D2BF 4AA3 09C5 B094
FLODIGARRY (n. Scots)
An ankle-length gabardine or oilskin tarpaulin worn by deep-sea
herring fishermen in Arbroath and publicans in Glasgow.
--- Douglas Adams, The Meaning of Liff
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#655330: installation of ca-certificates-java silently fails
Damien Raude-Morvan (24/05/2012): > Since some uploades, java-[67]-openjdk doesn't set nssLibraryDirectory > anymore (it then default to search path of dllopen - like any other > program). Hah! A sane behaviour, at last. I guess that's all I was hoping for. Just didn't find a satisfactory way to work around it (not enough a java guy to do that on my own…). > I've done some more tests of squeeze -> wheezy/sid upgrade and can't > reproduce this issue with current ca-certificate-java and openjdk-6. > So I'm now closing this issue, feel free to reopen if you can > reproduce it with other mean. I won't be able to check right now, but what you're saying looks very good, thanks for the notice! Mraw, KiBi. signature.asc Description: Digital signature
Bug#674358: marked as done (gmsh: FTBFS: array.hpp:374:7: error: 'SetSize' was not declared in this scope, and no declarations were found by argument-dependent lookup at the point of instantiation [-f
Your message dated Thu, 24 May 2012 22:09:24 + with message-id and subject line Bug#674358: fixed in gmsh 2.5.1~beta2~svn12143~dfsg-1 has caused the Debian Bug report #674358, regarding gmsh: FTBFS: array.hpp:374:7: error: 'SetSize' was not declared in this scope, and no declarations were found by argument-dependent lookup at the point of instantiation [-fpermissive] 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.) -- 674358: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=674358 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: gmsh Version: 2.5.1~beta2~svn11845~dfsg-2 Severity: serious Tags: wheezy sid User: debian...@lists.debian.org Usertags: qa-ftbfs-20120524 qa-ftbfs Justification: FTBFS on amd64 Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part: > /usr/bin/c++ -DNO_PARALLEL_THREADS -DNOTCL -DHAVE_NO_OCC_CONFIG_H -D_OCC64 > -DOCCGEOMETRY -DMPICH_SKIP_MPICXX -DOMPI_SKIP_MPICXX -fopenmp -lmpi -fPIC > -Wall -g -O2 -fstack-protector --param=ssp-buffer-size=4 -Wformat > -Werror=format-security -O2 -g -I"/«PKGBUILDDIR»/contrib/mpeg_encode/headers" > -I"/«PKGBUILDDIR»/contrib/lbfgs" > -I"/«PKGBUILDDIR»/contrib/DiscreteIntegration" > -I"/«PKGBUILDDIR»/contrib/MathEx" -I"/«PKGBUILDDIR»/contrib/Chaco/main" > -I"/«PKGBUILDDIR»/contrib/rtree" -I"/«PKGBUILDDIR»/contrib/voro++/src" > -I"/«PKGBUILDDIR»/contrib/blossom/MATCH" > -I"/«PKGBUILDDIR»/contrib/blossom/concorde97" > -I"/«PKGBUILDDIR»/contrib/blossom/concorde97/INCLUDE" > -I"/«PKGBUILDDIR»/contrib/Netgen" > -I"/«PKGBUILDDIR»/contrib/Netgen/libsrc/include" > -I"/«PKGBUILDDIR»/contrib/Netgen/nglib" -I"/«PKGBUILDDIR»/contrib/bamg" > -I"/«PKGBUILDDIR»/contrib/bamg/bamglib" > -I"/«PKGBUILDDIR»/contrib/mmg3d/build/sources" > -I"/«PKGBUILDDIR»/contrib/Salome" -I"/«PKGBUILDDIR»/Common" > -I"/«PKGBUILDDIR»/Fltk" -I"/«PKGBUILDDIR»/Geo" -I"/«PKGBUILDDIR»/Graphics" > -I"/«PKGBUILDDIR»/Mesh" -I"/«PKGBUILDDIR»/Solver" -I"/«PKGBUILDDIR»/Numeric" > -I"/«PKGBUILDDIR»/Parser" -I"/«PKGBUILDDIR»/Plugin" -I"/«PKGBUILDDIR»/Post" > -I"/«PKGBUILDDIR»/Qt" -I/usr/include/FL/images -I/usr/include/jpeg > -I/usr/include/zlib -I/usr/include/png -I/usr/include/ANN -I/usr/include/gmm > -I/usr/lib/petscdir/3.2/include > -I/usr/lib/petscdir/3.2/linux-gnu-c-opt/include -I/usr/include/slepc > -I/usr/lib/slepcdir/3.2/linux-gnu-c-opt/include > -I/usr/lib/oce-0.9.1/../../include/oce -I/usr/include/mpi > -I"/«PKGBUILDDIR»/debian/build/Common"-Wall -o > CMakeFiles/gmsh.dir/contrib/Netgen/libsrc/meshing/ruler2.cpp.o -c > "/«PKGBUILDDIR»/contrib/Netgen/libsrc/meshing/ruler2.cpp" > In file included from > /«PKGBUILDDIR»/contrib/Netgen/libsrc/include/../general/myadt.hpp:26:0, > from > /«PKGBUILDDIR»/contrib/Netgen/libsrc/meshing/../include/myadt.hpp:1, > from > /«PKGBUILDDIR»/contrib/Netgen/libsrc/meshing/meshing.hpp:6, > from > /«PKGBUILDDIR»/contrib/Netgen/libsrc/meshing/ruler2.cpp:2: > /«PKGBUILDDIR»/contrib/Netgen/libsrc/include/../general/array.hpp: In > instantiation of 'netgen::ArrayMem& netgen::ArrayMem S>::operator=(const netgen::FlatArray&) [with T = netgen::Point2d; int S = > 100; netgen::ArrayMem = netgen::ArrayMem]': > /«PKGBUILDDIR»/contrib/Netgen/libsrc/meshing/ruler2.cpp:672:61: required > from here > /«PKGBUILDDIR»/contrib/Netgen/libsrc/include/../general/array.hpp:374:7: > error: 'SetSize' was not declared in this scope, and no declarations were > found by argument-dependent lookup at the point of instantiation > [-fpermissive] > /«PKGBUILDDIR»/contrib/Netgen/libsrc/include/../general/array.hpp:374:7: > note: declarations in dependent base 'netgen::Array' are not > found by unqualified lookup > /«PKGBUILDDIR»/contrib/Netgen/libsrc/include/../general/array.hpp:374:7: > note: use 'this->SetSize' instead > /«PKGBUILDDIR»/contrib/Netgen/libsrc/include/../general/array.hpp: In > instantiation of 'netgen::ArrayMem& netgen::ArrayMem S>::operator=(const netgen::FlatArray&) [with T =
Bug#672859: marked as done (wwsympa.fcgi fails to check download/delete permissions properly)
Your message dated Thu, 24 May 2012 22:06:01 +
with message-id
and subject line Bug#672893: fixed in sympa 6.0.1+dfsg-4+squeeze1
has caused the Debian Bug report #672893,
regarding wwsympa.fcgi fails to check download/delete permissions properly
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.)
--
672893: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=672893
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: sympa
Version: 6.0.1+dfsg-4
Severity: grave
Sympa versions <6.1.11 have a severe security issue where any user can
download or delete the archives of a mailing list if they know the name
of the list.
Debian has been tracking it at
http://security-tracker.debian.org/tracker/CVE-2012-2352
I'm attaching a patch (taken from upstream commit:
https://sourcesup.renater.fr/scm/viewvc.php/branches/sympa-6.0-branch/wwsympa/wwsympa.fcgi.in?root=sympa&pathrev=7358
) that fixes the problem
-- System Information:
Debian Release: 6.0.4
APT prefers stable
APT policy: (800, 'stable'), (650, 'testing'), (500, 'stable-updates')
Architecture: amd64 (x86_64)
Kernel: Linux 2.6.32-5-amd64 (SMP w/2 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=el_GR.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
--- wwsympa.fcgi2012-05-14 11:53:36.0 +0300
+++ wwsympa.fcgi2012-05-14 11:55:09.0 +0300
@@ -15956,6 +15956,11 @@
sub do_arc_manage {
&wwslog('info', "do_arc_manage ($in{'list'})");
+ ## Access Control
+ unless (defined &check_authz('do_arc', 'web_archive.access')) {
+ return undef;
+ }
+
my $search_base = $wwsconf->{'arc_path'}.'/'.$list->get_list_id();
opendir ARC, "$search_base";
foreach my $dir (sort {$b cmp $a} grep(!/^\./,readdir ARC)) {
@@ -15972,6 +15977,11 @@
sub do_arc_download {
&wwslog('info', "do_arc_download ($in{'list'})");
+
+ ## Access Control
+ unless (defined &check_authz('do_arc', 'web_archive.access')) {
+ return undef;
+ }
##zip file name:listname_archives.zip
my $zip_file_name = $in{'list'}.'_archives.zip';
@@ -16072,6 +16082,11 @@
my @abs_dirs;
&wwslog('info', "do_arc_delete ($in{'list'})");
+
+ ## Access Control
+ unless (defined &check_authz('do_arc', 'web_archive.access')) {
+ return undef;
+ }
unless (defined $in{'directories'}){
&report::reject_report_web('user','select_month',{},$param->{'action'});
--- End Message ---
--- Begin Message ---
Source: sympa
Source-Version: 6.0.1+dfsg-4+squeeze1
We believe that the bug you reported is fixed in the latest version of
sympa, which is due to be installed in the Debian FTP archive:
sympa_6.0.1+dfsg-4+squeeze1.debian.tar.gz
to main/s/sympa/sympa_6.0.1+dfsg-4+squeeze1.debian.tar.gz
sympa_6.0.1+dfsg-4+squeeze1.dsc
to main/s/sympa/sympa_6.0.1+dfsg-4+squeeze1.dsc
sympa_6.0.1+dfsg-4+squeeze1_amd64.deb
to main/s/sympa/sympa_6.0.1+dfsg-4+squeeze1_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 672...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Emmanuel Bouthenot (supplier of updated sympa package)
(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@debian.org)
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Format: 1.8
Date: Sat, 19 May 2012 15:49:55 +
Source: sympa
Binary: sympa
Architecture: source amd64
Version: 6.0.1+dfsg-4+squeeze1
Distribution: stable-security
Urgency: high
Maintainer: Debian Sympa team
Changed-By: Emmanuel Bouthenot
Description:
sympa - Modern mailing list manager
Closes: 672893
Changes:
sympa (6.0.1+dfsg-4+squeeze1) stable-security; urgency=high
.
* Fix CVE-2012-2352: Possibility to bypass the authorization mechanisms in
the archive management page of wwsympa (Closes: #672893)
Checksums-Sha1:
162c35d2e518c77807208e80e0d57e87af495a93 2580 sympa_6.0.1+dfsg-4+squeeze1.dsc
9efaf6c3531c635ba935ec589545584e36228a60 4675743 sympa_6.0.1+dfsg.orig.tar.gz
f60592589f92c13532f4b675b6b344c1f969e047 108365
sympa_6.0.1+dfsg-4+squeeze1.debian.tar.gz
fc4a079368cdbcd7a7fd18ffd399fe88f567e6db 2524590
sympa_6.0.1+dfsg-4+squeeze1_amd64.deb
Checksums-Sha256:
e1b5e06327d23f210762ae7c22c6c4211f0e667eb39644aeb170a174e
Bug#672893: marked as done (security: private archives available to all)
Your message dated Thu, 24 May 2012 22:06:01 +
with message-id
and subject line Bug#672893: fixed in sympa 6.0.1+dfsg-4+squeeze1
has caused the Debian Bug report #672893,
regarding security: private archives available to 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.)
--
672893: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=672893
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: sympa
Version: 6.0.1+dfsg-4
Severity: grave
Tags: security patch
Justification: user security hole
It is possible to open the archive management ("arc_manage") page
for any list, even those set to only be available to members,
giving anyone the option to download the archive, or delete the
archive.
http://www.sympa.org/distribution/latest-stable/NEWS
Patch for the version in stable:
https://sourcesup.renater.fr/scm/viewvc.php/branches/sympa-6.0-branch/wwsympa/wwsympa.fcgi.in?root=sympa&r1=6706&r2=7358&pathrev=7358
Please reference CVE-2012-2352 in any changelogs addressing this issue.
micah
System Information:
Debian Release: wheezy/sid
Architecture: amd64 (x86_64)
Kernel: Linux 3.2.0-1-amd64 (SMP w/2 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
--- End Message ---
--- Begin Message ---
Source: sympa
Source-Version: 6.0.1+dfsg-4+squeeze1
We believe that the bug you reported is fixed in the latest version of
sympa, which is due to be installed in the Debian FTP archive:
sympa_6.0.1+dfsg-4+squeeze1.debian.tar.gz
to main/s/sympa/sympa_6.0.1+dfsg-4+squeeze1.debian.tar.gz
sympa_6.0.1+dfsg-4+squeeze1.dsc
to main/s/sympa/sympa_6.0.1+dfsg-4+squeeze1.dsc
sympa_6.0.1+dfsg-4+squeeze1_amd64.deb
to main/s/sympa/sympa_6.0.1+dfsg-4+squeeze1_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 672...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Emmanuel Bouthenot (supplier of updated sympa package)
(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@debian.org)
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Format: 1.8
Date: Sat, 19 May 2012 15:49:55 +
Source: sympa
Binary: sympa
Architecture: source amd64
Version: 6.0.1+dfsg-4+squeeze1
Distribution: stable-security
Urgency: high
Maintainer: Debian Sympa team
Changed-By: Emmanuel Bouthenot
Description:
sympa - Modern mailing list manager
Closes: 672893
Changes:
sympa (6.0.1+dfsg-4+squeeze1) stable-security; urgency=high
.
* Fix CVE-2012-2352: Possibility to bypass the authorization mechanisms in
the archive management page of wwsympa (Closes: #672893)
Checksums-Sha1:
162c35d2e518c77807208e80e0d57e87af495a93 2580 sympa_6.0.1+dfsg-4+squeeze1.dsc
9efaf6c3531c635ba935ec589545584e36228a60 4675743 sympa_6.0.1+dfsg.orig.tar.gz
f60592589f92c13532f4b675b6b344c1f969e047 108365
sympa_6.0.1+dfsg-4+squeeze1.debian.tar.gz
fc4a079368cdbcd7a7fd18ffd399fe88f567e6db 2524590
sympa_6.0.1+dfsg-4+squeeze1_amd64.deb
Checksums-Sha256:
e1b5e06327d23f210762ae7c22c6c4211f0e667eb39644aeb170a174e60e93ae 2580
sympa_6.0.1+dfsg-4+squeeze1.dsc
a5637ff0d870c0d266fcbadaf6a45c3d0f7dd3397e413a7731b62ad34a6d2e6b 4675743
sympa_6.0.1+dfsg.orig.tar.gz
8f3e39b68ad8c30c90577cd9a514e356725691cf5b150982d1381437c39583e5 108365
sympa_6.0.1+dfsg-4+squeeze1.debian.tar.gz
6569d4ad481bec65f4af39230334b960bdc8a3bc0e85ee5aac79f91b48e3d380 2524590
sympa_6.0.1+dfsg-4+squeeze1_amd64.deb
Files:
43de70f43a457e8415a8411eb5af7ee6 2580 mail optional
sympa_6.0.1+dfsg-4+squeeze1.dsc
fe14224f015aa79dee67979e65f8a988 4675743 mail optional
sympa_6.0.1+dfsg.orig.tar.gz
857d6fcabba5325330874e859bef60ca 108365 mail optional
sympa_6.0.1+dfsg-4+squeeze1.debian.tar.gz
3c66d31c7c7afa879165043097b480e5 2524590 mail optional
sympa_6.0.1+dfsg-4+squeeze1_amd64.deb
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.12 (GNU/Linux)
iQIcBAEBCgAGBQJPuRUiAAoJEEsHdyOSnULDeIgP/26ryNFJsr4uHKdN0uI/AfJ4
pnIM3zCWTEK1svlrL8w6GsAcji9ij3McMV701G7LKGimBpGD8yR/qvRuMaJbUyCh
gHjoVMQwlvaWv81QMtVbgFgWA3HD9UVTcjJp0NAkz/5Wc/zRPzXWdMmy3smq5yRU
Pb4bBH5l3t7shMEgpHvApIlY0BcScZ3bbx7KIJ+dfZDjbrYFWr8/ZP9DrHuGkhD8
QbeRphwZQBTuDDm73Ewqu933kKnHKyu0KrZzw8uhU/2Lf1qp39HxV02GI2Hz/OAb
dKNVQ4WTEP/tveqoaJOkS+9wuudrnRaZKXWDu73v0j/pEkTXS+b5BWnAEGa2EuBE
rz9Z09jSKfjsrwPXOVjMHkOD5x3jYdAevvmcwgUZzfsXZTC
Bug#674228: openvas-plugins-dfsg: FTBFS: missing build-deps
On Thu, May 24, 2012 at 01:03:27AM +0200, Cyril Brulebois wrote: > $subject says it all: > | [ "clean" = "audit-plugins" ] || dh clean --with quilt > | dh: unable to load addon quilt: Can't locate > Debian/Debhelper/Sequence/quilt.pm in @INC (@INC contains: /etc/perl > /usr/local/lib/perl/5.14.2 /usr/local/share/perl/5.14.2 /usr/lib/perl5 > /usr/share/perl5 /usr/lib/perl/5.14 /usr/share/perl/5.14 > /usr/local/lib/site_perl .) at (eval 18) line 2. > | BEGIN failed--compilation aborted at (eval 18) line 2. > | > | make: *** [clean] Error 2 > A build-depends: on quilt is missin in debian/control, I will add it. Regards Javier signature.asc Description: Digital signature
Bug#674471: FTBFS: (armel, sparc) error when testing
Package: libskk
Version: 0.0.12-1
Severity: serious
Justification: FTBFS
This package does not build on armel which is release architecture
(and sparc).
https://buildd.debian.org/status/fetch.php?pkg=libskk&arch=armel&ver=0.0.12-1&stamp=1333795311
**
ERROR:cdb-dict.c:23:cdb_dict: assertion failed (len == 2): (0 == 2)
/bin/bash: line 5: 27443 Aborted G_DEBUG=gc-friendly
G_SLICE=,always-malloc LIBSKK_DATA_PATH=.. /bin/bash ../libtool --mode=execute
${dir}$tst
/libskk/cdb-dict: FAIL: cdb-dict
...
==
1 of 8 tests failed
-- System Information:
Debian Release: wheezy/sid
APT prefers unstable
APT policy: (500, 'unstable'), (10, 'experimental')
Architecture: amd64 (x86_64)
Kernel: Linux 3.3.0-trunk-amd64 (SMP w/8 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#672577: marked as done (wine: File conflict with old package wine-gecko-1.0.0)
Your message dated Thu, 24 May 2012 21:48:42 + with message-id and subject line Bug#672577: fixed in wine 1.2.3-0.2 has caused the Debian Bug report #672577, regarding wine: File conflict with old package wine-gecko-1.0.0 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.) -- 672577: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=672577 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: wine-bin Version: 1.2.3-0.1 Severity: serious Hi, S'està desempaquetant el reemplaçament de wine-bin… dpkg: s'ha produït un error en processar /var/cache/apt/archives/wine-bin_1.2.3-0.1_amd64.deb (--unpack): s'està intentant sobreescriure «/usr/share/wine/gecko/wine_gecko-1.0.0-x86.cab», que també està en el paquet wine-gecko-1.0.0 1.0.0+dfsg-1 Or, translated: "trying to overwrite, etc, etc." I'm not sure where this wine-gecko thing came from, I guess it's an ancient stray package in my system, but a Breaks or Conflicts would be good. Thanks, Jordi -- System Information: Debian Release: wheezy/sid APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 3.2.0-2-amd64 (SMP w/2 CPU cores) Locale: LANG=ca_ES.UTF-8@valencia, LC_CTYPE=ca_ES.UTF-8@valencia (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages wine depends on: ii libwine-alsa 1.2.3-0.1 ii libwine-cms 1.2.3-0.1 ii libwine-gl 1.2.3-0.1 ii libwine-gphoto2 1.2.3-0.1 ii libwine-ldap 1.2.3-0.1 ii libwine-openal 1.2.3-0.1 ii libwine-print1.2.3-0.1 ii libwine-sane 1.2.3-0.1 ii wine-bin 1.2.3-0.1 Versions of packages wine recommends: ii fonts-liberation [ttf-liberation] 1.07.2-2 ii ttf-liberation 1.07.2-2 Versions of packages wine suggests: pn avscan | klamav | clamav pn binfmt-support 2.0.8 pn ttf-mscorefonts-installer pn winbind pn wine-doc Versions of packages libwine depends on: ii ia32-libs 20120102 ii lib32z1 1:1.2.7.dfsg-1 ii libc6-i386 2.13-32 Versions of packages libwine suggests: pn wine-doc -- no debconf information --- End Message --- --- Begin Message --- Source: wine Source-Version: 1.2.3-0.2 We believe that the bug you reported is fixed in the latest version of wine, which is due to be installed in the Debian FTP archive: libwine-alsa_1.2.3-0.2_amd64.deb to main/w/wine/libwine-alsa_1.2.3-0.2_amd64.deb libwine-bin_1.2.3-0.2_amd64.deb to main/w/wine/libwine-bin_1.2.3-0.2_amd64.deb libwine-capi_1.2.3-0.2_amd64.deb to main/w/wine/libwine-capi_1.2.3-0.2_amd64.deb libwine-cms_1.2.3-0.2_amd64.deb to main/w/wine/libwine-cms_1.2.3-0.2_amd64.deb libwine-dbg_1.2.3-0.2_amd64.deb to main/w/wine/libwine-dbg_1.2.3-0.2_amd64.deb libwine-dev_1.2.3-0.2_amd64.deb to main/w/wine/libwine-dev_1.2.3-0.2_amd64.deb libwine-esd_1.2.3-0.2_amd64.deb to main/w/wine/libwine-esd_1.2.3-0.2_amd64.deb libwine-gl_1.2.3-0.2_amd64.deb to main/w/wine/libwine-gl_1.2.3-0.2_amd64.deb libwine-gphoto2_1.2.3-0.2_amd64.deb to main/w/wine/libwine-gphoto2_1.2.3-0.2_amd64.deb libwine-jack_1.2.3-0.2_amd64.deb to main/w/wine/libwine-jack_1.2.3-0.2_amd64.deb libwine-ldap_1.2.3-0.2_amd64.deb to main/w/wine/libwine-ldap_1.2.3-0.2_amd64.deb libwine-nas_1.2.3-0.2_amd64.deb to main/w/wine/libwine-nas_1.2.3-0.2_amd64.deb libwine-openal_1.2.3-0.2_amd64.deb to main/w/wine/libwine-openal_1.2.3-0.2_amd64.deb libwine-oss_1.2.3-0.2_amd64.deb to main/w/wine/libwine-oss_1.2.3-0.2_amd64.deb libwine-print_1.2.3-0.2_amd64.deb to main/w/wine/libwine-print_1.2.3-0.2_amd64.deb libwine-sane_1.2.3-0.2_amd64.deb to main/w/wine/libwine-sane_1.2.3-0.2_amd64.deb libwine_1.2.3-0.2_amd64.deb to main/w/wine/libwine_1.2.3-0.2_amd64.deb wine-bin_1.2.3-0.2_amd64.deb to main/w/wine/wine-bin_1.2.3-0.2_amd64.deb wine_1.2.3-0.2.diff.gz to main/w/wine/wine_1.2.3-0.2.diff.gz wine_1.2.3-0.2.dsc to main/w/wine/wine_1.2.3-0.2.dsc wine_1.2.3-0.2_amd64.deb to main/w/wine/wine_1.2.3-0.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 672...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Hilko Bengen (supplier of updated wine 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.o
Bug#672035: [Swig-user] Using own string class
> At ZNC we have an own string class CString, which is inherited from
> std::string.
> The goal is to use it as a just string in target languages.
>
> How to do that properly?
When you use a string class derived from std::string, the main problem tends to
be that SWIG's built-in typemaps refer to std::string explicitly, but that's
unnecessary. For some target languages (at least C# and Java) if you simply
make a copy of the typemap with std::string changed to $*1_ltype, then you can
%apply those typemaps to your derived class. For example, here are the
corrected typemaps for Java:
namespace std {
// Changed lines are marked "//fixed"
%typemap(in) const string &
%{ if(!$input) {
SWIG_JavaThrowException(jenv, SWIG_JavaNullPointerException, "String param
cannot be null");
return $null;
}
const char *$1_pstr = (const char *)jenv->GetStringUTFChars($input, 0);
if (!$1_pstr) return $null;
$*1_ltype $1_str($1_pstr); //fixed
$1 = &$1_str;
jenv->ReleaseStringUTFChars($input, $1_pstr); %}
%typemap(directorout,warning=SWIGWARN_TYPEMAP_THREAD_UNSAFE_MSG) const string &
%{ if(!$input) {
SWIG_JavaThrowException(jenv, SWIG_JavaNullPointerException, "String param
cannot be null");
return $null;
}
const char *$1_pstr = (const char *)jenv->GetStringUTFChars($input, 0);
if (!$1_pstr) return $null;
/* possible thread/reentrant code problem */
static $1_ltype $1_str; //fixed
$1_str = $1_pstr;
$result = &$1_str;
jenv->ReleaseStringUTFChars($input, $1_pstr); %}
} // namespace std
Then you use %apply to support your custom string too:
%apply std::string { CString }
%apply std::string& { CString& } // [not supported in Java]
%apply const std::string& { const CString& }
Bug#673544: marked as done (openturns: FTBFS on s390: 'ptrdiff_t& {aka int&}' vs. 'long int')
Your message dated Thu, 24 May 2012 21:35:27 +
with message-id
and subject line Bug#673544: fixed in swig2.0 2.0.6-1
has caused the Debian Bug report #673544,
regarding openturns: FTBFS on s390: 'ptrdiff_t& {aka int&}' vs. 'long int'
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.)
--
673544: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=673544
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: openturns
Version: 1.0-2
Severity: serious
Justification: FTBFS
Hi,
your package no longer builds on s390:
|
/build/buildd-openturns_1.0-2-s390-WUP9uL/openturns-1.0/obj-s390-linux-gnu/python/src/common_modulePYTHON_wrap.cxx:4146:5:
error: invalid initialization of reference of type 'ptrdiff_t& {aka int&}'
from expression of type 'long int'
Full build log:
https://buildd.debian.org/status/fetch.php?pkg=openturns&arch=s390&ver=1.0-2&stamp=1337413625
Mraw,
KiBi.
--- End Message ---
--- Begin Message ---
Source: swig2.0
Source-Version: 2.0.6-1
We believe that the bug you reported is fixed in the latest version of
swig2.0, which is due to be installed in the Debian FTP archive:
swig-doc_2.0.6-1_all.deb
to main/s/swig2.0/swig-doc_2.0.6-1_all.deb
swig-examples_2.0.6-1_all.deb
to main/s/swig2.0/swig-examples_2.0.6-1_all.deb
swig2.0-doc_2.0.6-1_all.deb
to main/s/swig2.0/swig2.0-doc_2.0.6-1_all.deb
swig2.0-examples_2.0.6-1_all.deb
to main/s/swig2.0/swig2.0-examples_2.0.6-1_all.deb
swig2.0_2.0.6-1.debian.tar.gz
to main/s/swig2.0/swig2.0_2.0.6-1.debian.tar.gz
swig2.0_2.0.6-1.dsc
to main/s/swig2.0/swig2.0_2.0.6-1.dsc
swig2.0_2.0.6-1_amd64.deb
to main/s/swig2.0/swig2.0_2.0.6-1_amd64.deb
swig2.0_2.0.6.orig.tar.gz
to main/s/swig2.0/swig2.0_2.0.6.orig.tar.gz
swig_2.0.6-1_amd64.deb
to main/s/swig2.0/swig_2.0.6-1_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 673...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Torsten Landschoff (supplier of updated swig2.0 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, 22 May 2012 00:23:15 +0200
Source: swig2.0
Binary: swig swig2.0 swig-examples swig2.0-examples swig-doc swig2.0-doc
Architecture: source all amd64
Version: 2.0.6-1
Distribution: unstable
Urgency: low
Maintainer: Torsten Landschoff
Changed-By: Torsten Landschoff
Description:
swig - Generate scripting interfaces to C/C++ code
swig-doc - HTML documentation for SWIG
swig-examples - Examples for applications of SWIG
swig2.0- Generate scripting interfaces to C/C++ code
swig2.0-doc - HTML documentation for SWIG
swig2.0-examples - Examples for applications of SWIG
Closes: 673544
Changes:
swig2.0 (2.0.6-1) unstable; urgency=low
.
* Merge upstream changes for 2.0.6.
+ Includes patches to slicing bugs (closes: #673544).
* debian/control: Narrow the dependency of swig on swig2.0 to require
the newest version as suggested by Andreas Metzler.
Checksums-Sha1:
a03a5ce4bff9fc628e9f7bebe965e909442a8b45 1654 swig2.0_2.0.6-1.dsc
8e27a735d1f53be2e3d8d8473a3847e89ba89da8 5277387 swig2.0_2.0.6.orig.tar.gz
97231e8639ebb92455f462ae8cab0d2b48c49019 17405 swig2.0_2.0.6-1.debian.tar.gz
5bdf20ed8772d6958cccd5e0743b52a7f379deca 271302 swig-examples_2.0.6-1_all.deb
ee9ebda3a672981778d9112a17ad5b76622f0e21 1275826
swig2.0-examples_2.0.6-1_all.deb
8ace2211c9fee3cd6fb9213f65af77f83b6154c1 271290 swig-doc_2.0.6-1_all.deb
93a0ebf3948a7213d80a4b036d1caab184732921 2798362 swig2.0-doc_2.0.6-1_all.deb
98537fcc2f6a577c8960517a7feebcbb498dab3b 276632 swig_2.0.6-1_amd64.deb
1ff57938e01335ab6a27288c5872da36da8e634d 1423652 swig2.0_2.0.6-1_amd64.deb
Checksums-Sha256:
bc5c90c23f77e53e482e9c02df3690d69a8f7f6d88d0617de936eb62c5434166 1654
swig2.0_2.0.6-1.dsc
dd376331dd76899736852881f0fc5ba874b0d79e88a5bd9b366bcb20e7fbb17d 5277387
swig2.0_2.0.6.orig.tar.gz
5fdba42a48ba0082f78fd6e040080c468fdd8bfceb8ea1ebff23ee1635303bac 17405
swig2.0_2.0.6-1.debian.tar.gz
7304f740c8a18d21133235e9face09f6d4a390289e050b6d97e56d88e215 271302
swig-examples_2.0.6-1_all.deb
86d131237a7c6ebbf99e77ab1e90457e7fc709aa39cd4dbba9e3f077b61a5741 1275826
swig2.0-examples_2.0.6-1_all.deb
64c3898e5d4491c734c93ac2a8e35891649247463e73af0b9e9de5
Processed: Re: Bug#665054: dwarves-dfsg: FTBFS: make[3]: *** No rule to make target `/usr/lib/libdw.so', needed by `codiff'. Stop.
Processing commands for cont...@bugs.debian.org: > tags 665054 + confirmed Bug #665054 [src:dwarves-dfsg] dwarves-dfsg: FTBFS: make[3]: *** No rule to make target `/usr/lib/libdw.so', needed by `codiff'. Stop. Added tag(s) confirmed. > thanks Stopping processing here. Please contact me if you need assistance. -- 665054: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=665054 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#665054: dwarves-dfsg: FTBFS: make[3]: *** No rule to make target `/usr/lib/libdw.so', needed by `codiff'. Stop.
tags 665054 + confirmed thanks On 22/03/2012 13:24, Lucas Nussbaum wrote: > Relevant part: >> make[3]: Entering directory `/«PKGBUILDDIR»/debian/build' >> /usr/bin/cmake -E cmake_progress_report >> /«PKGBUILDDIR»/debian/build/CMakeFiles 1 >> [ 50%] Building C object CMakeFiles/codiff.dir/codiff.o >> /usr/bin/gcc -D_GNU_SOURCE -DDWARVES_VERSION=\"v1.9\" -Wall -g -O2 >> -I/«PKGBUILDDIR»/debian/build -I/«PKGBUILDDIR»-o >> CMakeFiles/codiff.dir/codiff.o -c /«PKGBUILDDIR»/codiff.c >> /«PKGBUILDDIR»/codiff.c: In function 'main': >> /«PKGBUILDDIR»/codiff.c:740:8: warning: variable 'filenames' set but not >> used [-Wunused-but-set-variable] >> make[3]: *** No rule to make target `/usr/lib/libdw.so', needed by `codiff'. >> Stop. >> make[3]: Leaving directory `/«PKGBUILDDIR»/debian/build' >> make[2]: *** [CMakeFiles/codiff.dir/all] Error 2 dwarves compilation needs to be tweaked for multiarch. Thanks, Regards, Thomas -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#672016: marked as done (kdemultimedia: FTBFS: ../../juk/stringhash.h:36:9: error: 'contains' was not declared in this scope, and no declarations were found by argument-dependent lookup at the poin
Your message dated Thu, 24 May 2012 21:33:50 + with message-id and subject line Bug#672016: fixed in kdemultimedia 4:4.7.4-3 has caused the Debian Bug report #672016, regarding kdemultimedia: FTBFS: ../../juk/stringhash.h:36:9: error: 'contains' was not declared in this scope, and no declarations were found by argument-dependent lookup at the point of instantiation [-fpermissive] 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.) -- 672016: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=672016 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: kdemultimedia Version: 4:4.7.4-2 Severity: serious Tags: wheezy sid User: debian...@lists.debian.org Usertags: qa-ftbfs-20120508 qa-ftbfs Justification: FTBFS on amd64 Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part: > /usr/bin/c++ -fPIC -g -O2 -fstack-protector --param=ssp-buffer-size=4 > -Wformat -Werror=format-security -Wnon-virtual-dtor -Wno-long-long -ansi > -Wundef -Wcast-align -Wchar-subscripts -Wall -W -Wpointer-arith > -Wformat-security -fno-exceptions -DQT_NO_EXCEPTIONS -fno-check-new > -fno-common -Woverloaded-virtual -fno-threadsafe-statics -fvisibility=hidden > -Werror=return-type -fvisibility-inlines-hidden -fexceptions > -UQT_NO_EXCEPTIONS -DNDEBUG -DQT_NO_DEBUG -Wl,--enable-new-dtags > -Wl,--fatal-warnings -Wl,--no-undefined -lc -Wl,-z,relro -Wl,--as-needed > -Wl,--no-undefined -shared -Wl,-soname,libkcddb.so.4 -o > ../lib/libkcddb.so.4.7.0 CMakeFiles/kcddb.dir/kcddb_automoc.o > CMakeFiles/kcddb.dir/musicbrainz/musicbrainzlookup.o > CMakeFiles/kcddb.dir/musicbrainz/asyncmusicbrainzlookup.o > CMakeFiles/kcddb.dir/cache.o CMakeFiles/kcddb.dir/cdinfo.o > CMakeFiles/kcddb.dir/kcddbconfig.o CMakeFiles/kcddb.dir/client.o > CMakeFiles/kcddb.dir/kcddb.o CMakeFiles/kcddb.dir/cddb.o > CMakeFiles/kcddb.dir/lookup.o CMakeFiles/kcddb.dir/cddbplookup.o > CMakeFiles/kcddb.dir/synccddbplookup.o > CMakeFiles/kcddb.dir/asynccddbplookup.o CMakeFiles/kcddb.dir/httplookup.o > CMakeFiles/kcddb.dir/synchttplookup.o CMakeFiles/kcddb.dir/asynchttplookup.o > CMakeFiles/kcddb.dir/smtpsubmit.o CMakeFiles/kcddb.dir/asyncsmtpsubmit.o > CMakeFiles/kcddb.dir/syncsmtpsubmit.o CMakeFiles/kcddb.dir/submit.o > CMakeFiles/kcddb.dir/sites.o CMakeFiles/kcddb.dir/httpsubmit.o > CMakeFiles/kcddb.dir/asynchttpsubmit.o CMakeFiles/kcddb.dir/synchttpsubmit.o > CMakeFiles/kcddb.dir/categories.o CMakeFiles/kcddb.dir/genres.o > CMakeFiles/kcddb.dir/cdinfodialog.o > CMakeFiles/kcddb.dir/cdinfoencodingwidget.o CMakeFiles/kcddb.dir/configbase.o > /usr/lib/libkdeui.so.5.7.0 /usr/lib/libkio.so.5.7.0 -lmusicbrainz3 > /usr/lib/x86_64-linux-gnu/libQtNetwork.so > /usr/lib/x86_64-linux-gnu/libQtXml.so /usr/lib/libkdeui.so.5.7.0 > /usr/lib/x86_64-linux-gnu/libQtGui.so /usr/lib/x86_64-linux-gnu/libQtSvg.so > /usr/lib/libkdecore.so.5.7.0 /usr/lib/x86_64-linux-gnu/libQtDBus.so > /usr/lib/x86_64-linux-gnu/libQtCore.so > /usr/bin/cmake -E cmake_progress_report > /«PKGBUILDDIR»/obj-x86_64-linux-gnu/CMakeFiles > In file included from ../../juk/playlist.h:30:0, > from ../../juk/historyplaylist.h:21, > from ../../juk/historyplaylist.cpp:16: > ../../juk/stringhash.h: In instantiation of 'bool Hash::insert(const T&) > [with T = QString]': > ../../juk/playlist.h:752:5: required from 'ItemType* > Playlist::createItem(const FileHandle&, Q3ListViewItem*, bool) [with ItemType > = HistoryPlaylistItem]' > ../../juk/historyplaylist.cpp:54:78: required from here > ../../juk/stringhash.h:36:9: error: 'contains' was not declared in this > scope, and no declarations were found by argument-dependent lookup at the > point of instantiation [-fpermissive] > ../../juk/stringhash.h:36:9: note: declarations in dependent base > 'QSet' are not found by unqualified lookup > ../../juk/stringhash.h:36:9: note: use 'this->contains' instead > [ 64%] Building CXX object kmix/CMakeFiles/kdeinit_kmix.dir/gui/mdwenum.o > cd kmix && /usr/bin/c++ -Dkdeinit_kmix_EXPORTS -D_BSD_SOURCE > -D_XOPEN_SOURCE=500 -D_BSD_SOURCE -DQT_NO_STL -DQT_NO_CAST_TO_ASCII > -D_REENTRANT -DKDE_DEPRECATED_WARNINGS -DKDE4_CMAKE_TOPLEVEL_DIR_LENGTH=27 > -D_XOPEN_SOURCE=500 -D_BSD_SOURCE -DQT_NO_STL -DQT_NO_CAST_TO_ASCII > -D_REENTRANT -DKDE_DEPRECATED_WARNINGS -DKDE4_CMAKE_TOPLEVEL_DIR_LENGTH=27 -g > -O2 -fstack-protector --param=ssp-buffer-size=4 -Wformat > -Werror=format-security -Wnon-virtual-dtor -Wno-long-long -ansi -Wundef > -Wcast-align -Wchar-subscripts -Wall -W -Wpointer-arith -Wformat-security >
Bug#674385: marked as done (libcpan-mini-perl: FTBFS: tests failed)
Your message dated Thu, 24 May 2012 21:34:05 + with message-id and subject line Bug#674385: fixed in libcpan-mini-perl 1.111008-3 has caused the Debian Bug report #674385, regarding libcpan-mini-perl: FTBFS: tests failed 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.) -- 674385: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=674385 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: libcpan-mini-perl Version: 1.111008-2 Severity: serious Tags: wheezy sid User: debian...@lists.debian.org Usertags: qa-ftbfs-20120524 qa-ftbfs Justification: FTBFS on amd64 Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part: > make[2]: Entering directory `/«PKGBUILDDIR»' > PERL_DL_NONLAZY=1 /usr/bin/perl "-MExtUtils::Command::MM" "-e" > "test_harness(0, 'blib/lib', 'blib/arch')" t/*.t > # Testing CPAN::Mini 1.111008 > t/00-load.t . ok > couldn't determine your home directory! set HOME env variable at > /«PKGBUILDDIR»/blib/lib/CPAN/Mini/App.pm line 90 > # Child (defaults) exited without calling finalize() > > # Failed test 'defaults' > # at /usr/share/perl/5.14/Test/Builder.pm line 252. > # Tests were run but no plan was declared and done_testing() was not seen. > t/app.t . > Dubious, test returned 2 (wstat 512, 0x200) > Failed 1/1 subtests > t/config-file.t . ok > t/filter.t .. ok > t/release-pod-syntax.t .. skipped: these tests are for release candidate > testing > > Test Summary Report > --- > t/app.t (Wstat: 512 Tests: 1 Failed: 1) > Failed test: 1 > Non-zero exit status: 2 > Parse errors: No plan found in TAP output > Files=5, Tests=39, 1 wallclock secs ( 0.03 usr 0.04 sys + 0.67 cusr 0.11 > csys = 0.85 CPU) > Result: FAIL > Failed 1/5 test programs. 1/39 subtests failed. > make[2]: *** [test_dynamic] Error 255 The full build log is available from: http://people.debian.org/~lucas/logs/2012/05/24/libcpan-mini-perl_1.111008-2_unstable.log 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. --- End Message --- --- Begin Message --- Source: libcpan-mini-perl Source-Version: 1.111008-3 We believe that the bug you reported is fixed in the latest version of libcpan-mini-perl, which is due to be installed in the Debian FTP archive: libcpan-mini-perl_1.111008-3.debian.tar.gz to main/libc/libcpan-mini-perl/libcpan-mini-perl_1.111008-3.debian.tar.gz libcpan-mini-perl_1.111008-3.dsc to main/libc/libcpan-mini-perl/libcpan-mini-perl_1.111008-3.dsc libcpan-mini-perl_1.111008-3_all.deb to main/libc/libcpan-mini-perl/libcpan-mini-perl_1.111008-3_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 674...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Salvatore Bonaccorso (supplier of updated libcpan-mini-perl 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: Thu, 24 May 2012 23:21:36 +0200 Source: libcpan-mini-perl Binary: libcpan-mini-perl Architecture: source all Version: 1.111008-3 Distribution: unstable Urgency: low Maintainer: Debian Perl Group Changed-By: Salvatore Bonaccorso Description: libcpan-mini-perl - module for creating a minimal mirror of CPAN Closes: 674385 Changes: libcpan-mini-perl (1.111008-3) unstable; urgency=low . * Team upload. * Add always-return-tempdir-from-config_dir.patch patch. Fix FTBFS "libcpan-mini-perl: FTBFS: tests failed". Return always the created tempdir explicitly. (Closes: #674385) Checksums-Sha1: 8862bfd8c2ed99452c2386341807f6e18c0c7dcb 2230 libcpan-mini-perl_1.111008-3.dsc 1b19986c9104f4429c692171c5a0a1316440b788 3379 libcpan-mini-perl_1.111008-3.debian.tar.gz bebf65b292b26cf5d337d5ea0
Processed: Pending fixes for bugs in the libcpan-mini-perl package
Processing commands for cont...@bugs.debian.org: > tag 674385 + pending Bug #674385 [src:libcpan-mini-perl] libcpan-mini-perl: FTBFS: tests failed Added tag(s) pending. > thanks Stopping processing here. Please contact me if you need assistance. -- 674385: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=674385 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#674385: Pending fixes for bugs in the libcpan-mini-perl package
tag 674385 + pending thanks Some bugs in the libcpan-mini-perl package are closed in revision 1cae1cd35b466d969df376841976ea8b07fe68ee in branch 'master' by Salvatore Bonaccorso The full diff can be seen at http://anonscm.debian.org/gitweb/?p=pkg-perl/packages/libcpan-mini-perl.git;a=commitdiff;h=1cae1cd Commit message: Add always-return-tempdir-from-config_dir.patch patch Fix FTBFS "libcpan-mini-perl: FTBFS: tests failed". Return always the created tempdir explicitly. Closes: #674385 -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#674460: initscripts: prompting due to modified conffiles which were not modified by the user
On Thu, May 24, 2012 at 09:50:51PM +0200, Andreas Beckmann wrote: > during a test with piuparts I noticed your package failed the piuparts > upgrade test because dpkg detected a conffile as being modified and then > prompted the user for an action. As there is no user input, this fails. > But this is not the real problem, the real problem is that this prompt > shows up in the first place, as there was nobody modifying this conffile > at all, the package has just been installed and upgraded... > > This is a violation of policy 10.7.3, see > http://www.debian.org/doc/debian-policy/ch-files.html#s10.7.3, > which says "[These scripts handling conffiles] must not ask unnecessary > questions (particularly during upgrades), and must otherwise be good > citizens." > > Configuration file `/etc/default/rcS' > > This was observed on a distupgrade from sid to experimental. > There needs to be a way to detect if /etc/default/rcS is "unmodified" > (and there are probably a lot of different unmodified variants that > should allow seamless upgrades) before it's made a conffile. rcS was previously not a conffile, and was modified by the installer to set the UTC setting. In the last few releases, we temporarily managed it using ucf. But now the UTC setting is gone (migrated to /etc/adjtime), there's no reason why it can't be a regular conffile. If the issue is that we don't detect earlier "unmodified" forms, we can potentially handle this case with a list of md5sums. However... given that a number of different scripts edit this including - debian-installer clock-setup - util-linux maintainer scripts - initscripts maintainer scripts - potentially others, I'd need to check the number of combinations is not trivial to deal with, given that we need every variant/ordering of every rcS version ever provided, given that the base file is only ever installed once, on initial installation. We can look at doing this though. Regards, Roger -- .''`. Roger Leigh : :' : Debian GNU/Linuxhttp://people.debian.org/~rleigh/ `. `' schroot and sbuild http://alioth.debian.org/projects/buildd-tools `-GPG Public Key F33D 281D 470A B443 6756 147C 07B3 C8BC 4083 E800 -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#674011: marked as done (puppetmaster-passenger: fails to remove: puppetmaster-passenger.postrm: a2dissite: not found)
Your message dated Thu, 24 May 2012 21:09:07 + with message-id and subject line Bug#674011: fixed in puppet 3.0.0~rc2-1 has caused the Debian Bug report #674011, regarding puppetmaster-passenger: fails to remove: puppetmaster-passenger.postrm: a2dissite: not found 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.) -- 674011: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=674011 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: puppetmaster-passenger Version: 3.0.0~rc1-1 Severity: serious User: debian...@lists.debian.org Usertags: piuparts Hi, during a test with piuparts I noticed your package fails to remove. >From the attached log (scroll to the bottom...): Removing puppetmaster-passenger ... /var/lib/dpkg/info/puppetmaster-passenger.postrm: 16: /var/lib/dpkg/info/puppetmaster-passenger.postrm: a2dissite: not found dpkg: error processing puppetmaster-passenger (--purge): subprocess installed post-removal script returned error exit status 127 Errors were encountered while processing: puppetmaster-passenger cheers, Andreas puppetmaster-passenger_3.0.0~rc1-1.log.gz Description: GNU Zip compressed data --- End Message --- --- Begin Message --- Source: puppet Source-Version: 3.0.0~rc2-1 We believe that the bug you reported is fixed in the latest version of puppet, which is due to be installed in the Debian FTP archive: puppet-common_3.0.0~rc2-1_all.deb to main/p/puppet/puppet-common_3.0.0~rc2-1_all.deb puppet-el_3.0.0~rc2-1_all.deb to main/p/puppet/puppet-el_3.0.0~rc2-1_all.deb puppet-testsuite_3.0.0~rc2-1_all.deb to main/p/puppet/puppet-testsuite_3.0.0~rc2-1_all.deb puppet_3.0.0~rc2-1.debian.tar.gz to main/p/puppet/puppet_3.0.0~rc2-1.debian.tar.gz puppet_3.0.0~rc2-1.dsc to main/p/puppet/puppet_3.0.0~rc2-1.dsc puppet_3.0.0~rc2-1_all.deb to main/p/puppet/puppet_3.0.0~rc2-1_all.deb puppet_3.0.0~rc2.orig.tar.gz to main/p/puppet/puppet_3.0.0~rc2.orig.tar.gz puppetmaster-common_3.0.0~rc2-1_all.deb to main/p/puppet/puppetmaster-common_3.0.0~rc2-1_all.deb puppetmaster-passenger_3.0.0~rc2-1_all.deb to main/p/puppet/puppetmaster-passenger_3.0.0~rc2-1_all.deb puppetmaster_3.0.0~rc2-1_all.deb to main/p/puppet/puppetmaster_3.0.0~rc2-1_all.deb vim-puppet_3.0.0~rc2-1_all.deb to main/p/puppet/vim-puppet_3.0.0~rc2-1_all.deb A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 674...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Stig Sandbeck Mathisen (supplier of updated puppet package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.8 Date: Thu, 24 May 2012 21:58:39 +0200 Source: puppet Binary: puppet-common puppet puppetmaster-common puppetmaster puppetmaster-passenger vim-puppet puppet-el puppet-testsuite Architecture: source all Version: 3.0.0~rc2-1 Distribution: experimental Urgency: low Maintainer: Puppet Package Maintainers Changed-By: Stig Sandbeck Mathisen Description: puppet - Centralized configuration management - agent startup and compatib puppet-common - Centralized configuration management puppet-el - syntax highlighting for puppet manifests in emacs puppet-testsuite - Centralized configuration management - test suite puppetmaster - Centralized configuration management - master startup and compati puppetmaster-common - Puppet master common scripts puppetmaster-passenger - Centralised configuration management - master setup to run under vim-puppet - syntax highlighting for puppet manifests in vim Closes: 673970 674011 Changes: puppet (3.0.0~rc2-1) experimental; urgency=low . * Imported Upstream version 3.0.0~rc2 * Rename configuration file /etc/apache2/sites-available/puppetmaster to puppetmaster.conf to match apache2 policy change (Closes: #673970) * Check if a2dissite is present for postrm (Closes: #674011) * Workaround apache2 a2* utils API change to stay compatible to both apache 2.2 and 2.4 * Add description to no-rubygems patch * Add lintian override for unit tests having hashbang, and not being executable * Refactor puppetmaster-passenger postinst and postrm scripts Checksums-Sha1: a83d2268b759f4ffc5c8127f4a88392a8c04b015 1859 puppet_3.0.0~rc2-1.dsc 64ffe11622
Bug#673970: marked as done (puppetmaster-passenger: fails to install: ERROR: Site puppetmaster does not exist!)
Your message dated Thu, 24 May 2012 21:09:07 + with message-id and subject line Bug#673970: fixed in puppet 3.0.0~rc2-1 has caused the Debian Bug report #673970, regarding puppetmaster-passenger: fails to install: ERROR: Site puppetmaster does not exist! 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.) -- 673970: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=673970 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: puppetmaster-passenger Version: 3.0.0~rc1-1 Severity: serious User: debian...@lists.debian.org Usertags: piuparts Hi, during a test with piuparts I noticed your package failed to install. As per definition of the release team this makes the package too buggy for a release, thus the severity. >From the attached log (scroll to the bottom...): Setting up puppetmaster-passenger (3.0.0~rc1-1) ... Signed certificate request for ca Rebuilding inventory file myhost.domain.example.com has a waiting certificate request Signed certificate request for myhost.domain.example.com Removing file Puppet::SSL::CertificateRequest myhost.domain.example.com at '/var/lib/puppet/ssl/ca/requests/myhost.domain.example.com.pem' Removing file Puppet::SSL::CertificateRequest myhost.domain.example.com at '/var/lib/puppet/ssl/certificate_requests/myhost.domain.example.com.pem' Considering dependency setenvif for ssl: Module setenvif already enabled Considering dependency mime for ssl: Module mime already enabled Considering dependency socache_shmcb for ssl: Enabling module socache_shmcb. Enabling module ssl. See /usr/share/doc/apache2/README.Debian.gz on how to configure SSL and create self-signed certificates. To activate the new configuration, you need to run: service apache2 restart Enabling module headers. To activate the new configuration, you need to run: service apache2 restart ERROR: Site puppetmaster does not exist! dpkg: error processing puppetmaster-passenger (--configure): subprocess installed post-installation script returned error exit status 1 Errors were encountered while processing: puppetmaster-passenger Note that no services are running (forbidden by policy-rc.d) in the chroot where piuparts performs the test. cheers, Andreas puppetmaster-passenger_3.0.0~rc1-1.log.gz Description: GNU Zip compressed data --- End Message --- --- Begin Message --- Source: puppet Source-Version: 3.0.0~rc2-1 We believe that the bug you reported is fixed in the latest version of puppet, which is due to be installed in the Debian FTP archive: puppet-common_3.0.0~rc2-1_all.deb to main/p/puppet/puppet-common_3.0.0~rc2-1_all.deb puppet-el_3.0.0~rc2-1_all.deb to main/p/puppet/puppet-el_3.0.0~rc2-1_all.deb puppet-testsuite_3.0.0~rc2-1_all.deb to main/p/puppet/puppet-testsuite_3.0.0~rc2-1_all.deb puppet_3.0.0~rc2-1.debian.tar.gz to main/p/puppet/puppet_3.0.0~rc2-1.debian.tar.gz puppet_3.0.0~rc2-1.dsc to main/p/puppet/puppet_3.0.0~rc2-1.dsc puppet_3.0.0~rc2-1_all.deb to main/p/puppet/puppet_3.0.0~rc2-1_all.deb puppet_3.0.0~rc2.orig.tar.gz to main/p/puppet/puppet_3.0.0~rc2.orig.tar.gz puppetmaster-common_3.0.0~rc2-1_all.deb to main/p/puppet/puppetmaster-common_3.0.0~rc2-1_all.deb puppetmaster-passenger_3.0.0~rc2-1_all.deb to main/p/puppet/puppetmaster-passenger_3.0.0~rc2-1_all.deb puppetmaster_3.0.0~rc2-1_all.deb to main/p/puppet/puppetmaster_3.0.0~rc2-1_all.deb vim-puppet_3.0.0~rc2-1_all.deb to main/p/puppet/vim-puppet_3.0.0~rc2-1_all.deb A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 673...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Stig Sandbeck Mathisen (supplier of updated puppet package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.8 Date: Thu, 24 May 2012 21:58:39 +0200 Source: puppet Binary: puppet-common puppet puppetmaster-common puppetmaster puppetmaster-passenger vim-puppet puppet-el puppet-testsuite Architecture: source all Version: 3.0.0~rc2-1 Distribution: experimental Urgency: low Maintainer: Puppet Package Maintainers Changed-By: Stig Sandbeck Mathisen Description: puppet - Centralized configuration management - agent startup and compatib puppet-common - Centralized c
Bug#673766: marked as done (CVE-2012-2337: IP addresses in sudoers with netmask may match additional hosts)
Your message dated Thu, 24 May 2012 21:09:40 + with message-id and subject line Bug#673766: fixed in sudo 1.8.3p2-1.1 has caused the Debian Bug report #673766, regarding CVE-2012-2337: IP addresses in sudoers with netmask may match additional hosts 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.) -- 673766: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=673766 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: sudo Severity: grave Tags: security Please see http://www.sudo.ws/sudo/alerts/netmask.html Cheers, Moritz --- End Message --- --- Begin Message --- Source: sudo Source-Version: 1.8.3p2-1.1 We believe that the bug you reported is fixed in the latest version of sudo, which is due to be installed in the Debian FTP archive: sudo-ldap_1.8.3p2-1.1_amd64.deb to main/s/sudo/sudo-ldap_1.8.3p2-1.1_amd64.deb sudo_1.8.3p2-1.1.debian.tar.gz to main/s/sudo/sudo_1.8.3p2-1.1.debian.tar.gz sudo_1.8.3p2-1.1.dsc to main/s/sudo/sudo_1.8.3p2-1.1.dsc sudo_1.8.3p2-1.1_amd64.deb to main/s/sudo/sudo_1.8.3p2-1.1_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 673...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Dmitrijs Ledkovs (supplier of updated sudo 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, 22 May 2012 12:23:00 +0100 Source: sudo Binary: sudo sudo-ldap Architecture: source amd64 Version: 1.8.3p2-1.1 Distribution: unstable Urgency: high Maintainer: Bdale Garbee Changed-By: Dmitrijs Ledkovs Description: sudo - Provide limited super user privileges to specific users sudo-ldap - Provide limited super user privileges to specific users Closes: 673766 Changes: sudo (1.8.3p2-1.1) unstable; urgency=high . * Non-maintainer upload. * SECURITY UPDATE: Properly handle netmasks in sudoers Host and Host_List values (LP: #1000276, Closes: #673766, CVE-2012-2337) - debian/patches/CVE-2012-2337.patch: Don't perform IPv6 checks on IPv4 addresses. Based on upstream patch. Checksums-Sha1: d64a4d0d9600401479ff991f043ef7ea6c9aa170 1873 sudo_1.8.3p2-1.1.dsc 3009fb7249cdc71330518370ace2d2747226a62a 22640 sudo_1.8.3p2-1.1.debian.tar.gz e53578ce82d0c0ac42ecfaca09899df72b4606d4 681172 sudo_1.8.3p2-1.1_amd64.deb 18c11dddfb813dd521e02a13c3f253363dbfdef5 707290 sudo-ldap_1.8.3p2-1.1_amd64.deb Checksums-Sha256: 47d4a2e1096fbd4316d0c6dd55f0c3a8694cab38606566ae305ec2d1bc8a5ced 1873 sudo_1.8.3p2-1.1.dsc 3987b471b0b93ca3bf9c75221a8a1dea88de570bf4c357fd23b89843458f0fa2 22640 sudo_1.8.3p2-1.1.debian.tar.gz 5eb1c80261f67bd4dfa93b0455b9104c73f1efa8b410ec740e3431b0a1296d55 681172 sudo_1.8.3p2-1.1_amd64.deb 5d25914386d3a4778972a393f613e146f244ecd90de64d7e9b283d2b933122ca 707290 sudo-ldap_1.8.3p2-1.1_amd64.deb Files: 73c50a9c9c05f3586ec2fea48db7fe92 1873 admin optional sudo_1.8.3p2-1.1.dsc 11bd4c9f1f275fe05a240964aff6bb91 22640 admin optional sudo_1.8.3p2-1.1.debian.tar.gz 03f6b2045610e3c46f98f535fb9ea4e5 681172 admin optional sudo_1.8.3p2-1.1_amd64.deb 9d7f365e762ec2f353ff846a89b2bbac 707290 admin optional sudo-ldap_1.8.3p2-1.1_amd64.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.11 (GNU/Linux) iQIcBAEBCAAGBQJPvpJLAAoJEIh7YGGLPBau7SAQAJNDV9EeyDFJn6Wo0ZbRRIM6 AuAVCFIcpuz0DciK9hF3SnEQhHTd8mPzI4pw4aqUNoOVsWZrd1XTJodyhbeVLxmx SkyI8IsR5NpjiOsGnr66XE5Orky6dUgqgHqNgjA0Svs/AfcgFGGz2BQrHQSC5xC/ A2CMjYJQzfRbWnnqp3r5lBcFstpHfH8taSi4vwl3uwKnK0xm6vBJRkF4NwyFhLI3 yc1x/MRzCAOQQ89tl+eUFD0har52luSfHqTOn5WFHyb0f3K3ce2rPyQ9FJ5aOE9y c2bteTxUQmxGN1bDAP0DQdykwRJi+AzZvWGcG0+OUvE6BiVKbYKz1F386MUyLq0B C4oUY90wiyzdHBri4YU/armF9GNAQDVUUMKyJ9k/ZacgZ1V2H3OfvefDp0sgTaMz drGYBs38aOVzayWJx2L1BYyCB2Yzr9U5nSyNtau4yb9xhEaw0MVikT3gICttkxMk SBVuyepHeCXURz5H913kF7SiZzjMQuWKV7xwgx3hAgi5K6rx/78QOO9dGYb3VcLU o4peRurz2BdCI2GKoV0BzPF1ZRD7bVOhdY+VDC1ghFuZirof0bZYh19mZUAcuqB5 MMGGXBlFQA/j9+nOPZxdUfs0ayJjEeHsw4D2KryT7fxdEOAzehbICHzcPl3S63g3 uCONOjtoNJIoy/M8n3Ge =ykBa -END PGP SIGNATURE- --- End Message ---
Bug#666865: Unarchive: The problem still persists
Hi, On 24.05.2012 19:12, micah anderson wrote: >> Do you have a way of testing this? I've set up something that I believe >> should let the messages through based on the X-Loop header, but need to >> test that it is working. > > There was a mistake in what was done, but that has been fixed now. Well, basically I will reply to you through the BTS. If my message reaches you, the problem seems fixed (pretending you didn't whitelist me explicitly given I'm the only one to complain :>). -- with kind regards, Arno Töll IRC: daemonkeeper on Freenode/OFTC GnuPG Key-ID: 0x9D80F36D signature.asc Description: OpenPGP digital signature
Bug#674093: marked as done (libdivecomputer: FTBFS: libdivecomputer-dev missing files (usr/lib/lib*.a), aborting)
Your message dated Thu, 24 May 2012 21:07:03 + with message-id and subject line Bug#674093: fixed in libdivecomputer 0.1.0-3 has caused the Debian Bug report #674093, regarding libdivecomputer: FTBFS: libdivecomputer-dev missing files (usr/lib/lib*.a), aborting 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.) -- 674093: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=674093 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: libdivecomputer Version: 0.1.0-1 Severity: serious Justification: fails to build from source Builds of libdivecomputer with modern versions of Debhelper fail, because Debhelper supplies a multiarch-compatible libdir whereas debian/*.install still expects the traditional /usr/lib: test -z "/usr/lib/i386-linux-gnu" || /bin/mkdir -p "/.../libdivecomputer-0.1.0/debian/tmp/usr/lib/i386-linux-gnu" /bin/bash ../libtool --mode=install /usr/bin/install -c libdivecomputer.la '/.../libdivecomputer-0.1.0/debian/tmp/usr/lib/i386-linux-gnu' [...] libtool: install: warning: remember to run `libtool --finish /usr/lib/i386-linux-gnu' [...] test -z "/usr/lib/i386-linux-gnu/pkgconfig" || /bin/mkdir -p "/.../libdivecomputer-0.1.0/debian/tmp/usr/lib/i386-linux-gnu/pkgconfig" /usr/bin/install -c -m 644 libdivecomputer.pc '/.../libdivecomputer-0.1.0/debian/tmp/usr/lib/i386-linux-gnu/pkgconfig' dh_install -a dh_install: libdivecomputer-dev missing files (usr/lib/lib*.a), aborting make: *** [binary-arch] Error 255 Could you please adjust debian/*.install to account for populating architecture-specific subdirectories? Thanks! --- End Message --- --- Begin Message --- Source: libdivecomputer Source-Version: 0.1.0-3 We believe that the bug you reported is fixed in the latest version of libdivecomputer, which is due to be installed in the Debian FTP archive: libdivecomputer-dev_0.1.0-3_amd64.deb to main/libd/libdivecomputer/libdivecomputer-dev_0.1.0-3_amd64.deb libdivecomputer0_0.1.0-3_amd64.deb to main/libd/libdivecomputer/libdivecomputer0_0.1.0-3_amd64.deb libdivecomputer_0.1.0-3.debian.tar.gz to main/libd/libdivecomputer/libdivecomputer_0.1.0-3.debian.tar.gz libdivecomputer_0.1.0-3.dsc to main/libd/libdivecomputer/libdivecomputer_0.1.0-3.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 674...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Khalid El Fathi (supplier of updated libdivecomputer package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Wed, 23 May 2012 21:47:46 +0200 Source: libdivecomputer Binary: libdivecomputer-dev libdivecomputer0 Architecture: source amd64 Version: 0.1.0-3 Distribution: unstable Urgency: low Maintainer: Khalid El Fathi Changed-By: Khalid El Fathi Description: libdivecomputer-dev - dive computer interface library - development files libdivecomputer0 - dive computer interface library Closes: 674093 Changes: libdivecomputer (0.1.0-3) unstable; urgency=low . * Fix FTBFS and convert packaging to Multi-Arch (Closes: #674093) * debian/control - Add fields "Pre-Depends" for multiarch support * debian/*.install - Convert to Multi-Arch * debian/rules - Remove override build Checksums-Sha1: 9f7ac61999c47b4a11f951a60d67a8a78e8cb0f1 2035 libdivecomputer_0.1.0-3.dsc f99cf4d532117dd1d29b3a2a2c83108bff59019e 6599 libdivecomputer_0.1.0-3.debian.tar.gz 197a16e01f144def4d1dd13e8787374b94461e19 116404 libdivecomputer-dev_0.1.0-3_amd64.deb 6173e5bf567fe344bc17835fd5420e86ee659695 94376 libdivecomputer0_0.1.0-3_amd64.deb Checksums-Sha256: 6638ff26b00c721aa7a1294ab13ea9f9749c5560f6357a42c51fa6fb35589974 2035 libdivecomputer_0.1.0-3.dsc d2a4ab890886b0689a9de43b964062d3d555647bc699a21b29af8139eb5d 6599 libdivecomputer_0.1.0-3.debian.tar.gz 0cd76011abd6b5c3ce4856e196bea9cbbb5e49df5b9b075ec95f5f571c047766 116404 libdivecomputer-dev_0.1.0-3_amd64.deb a98f72ff2622da7ab5dedd3fc22dc474936eec53502d81e05e98780bfb597827 94376 libdivecomputer0_0.1.0-3_amd64.deb Files: 4b035e8eb0822593f846e57ce2b16bb4 2035 libs extra libdivecomputer_0.1.0-3.dsc 686560f5cd44cdd19b6a864158f16ef0 6599 libs extra libdivecomputer_0.1.0-3.debian.tar.gz 7498e34beacea614374c
Processed: [bts-link] source package meshlab
Processing commands for cont...@bugs.debian.org: > # > # bts-link upstream status pull for source package meshlab > # see http://lists.debian.org/debian-devel-announce/2006/05/msg1.html > # > user bts-link-upstr...@lists.alioth.debian.org Setting user to bts-link-upstr...@lists.alioth.debian.org (was bts-link-de...@lists.alioth.debian.org). > # remote status report for #667276 (http://bugs.debian.org/667276) > # Bug title: meshlab: ftbfs with GCC-4.7 > # * http://sourceforge.net/tracker/?func=detail&aid=3474158 > # * remote status changed: (?) -> Closed > # * closed upstream > tags 667276 + fixed-upstream Bug #667276 [meshlab] meshlab: ftbfs with GCC-4.7 Added tag(s) fixed-upstream. > usertags 667276 + status-Closed Bug#667276: meshlab: ftbfs with GCC-4.7 There were no usertags set. Usertags are now: status-Closed. > thanks Stopping processing here. Please contact me if you need assistance. -- 667276: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=667276 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: [bts-link] source package telepathy-qt4
Processing commands for cont...@bugs.debian.org: > # > # bts-link upstream status pull for source package telepathy-qt4 > # see http://lists.debian.org/debian-devel-announce/2006/05/msg1.html > # > user bts-link-upstr...@lists.alioth.debian.org Setting user to bts-link-upstr...@lists.alioth.debian.org (was bts-link-de...@lists.alioth.debian.org). > # remote status report for #667391 (http://bugs.debian.org/667391) > # Bug title: telepathy-qt4: ftbfs with GCC-4.7 > # * https://bugs.freedesktop.org/show_bug.cgi?id=50204 > # * remote status changed: (?) -> RESOLVED > # * remote resolution changed: (?) -> FIXED > # * closed upstream > tags 667391 + fixed-upstream Bug #667391 [telepathy-qt4] telepathy-qt4: ftbfs with GCC-4.7 Added tag(s) fixed-upstream. > usertags 667391 + status-RESOLVED resolution-FIXED Bug#667391: telepathy-qt4: ftbfs with GCC-4.7 There were no usertags set. Usertags are now: status-RESOLVED resolution-FIXED. > thanks Stopping processing here. Please contact me if you need assistance. -- 667391: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=667391 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#665754: marked as done (ca-certificates: reconfiguration creates links in "/")
Your message dated Thu, 24 May 2012 21:02:13 + with message-id and subject line Bug#665754: fixed in ca-certificates-java 20120524 has caused the Debian Bug report #665754, regarding ca-certificates: reconfiguration creates links in "/" 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.) -- 665754: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=665754 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: ca-certificates Version: 20120212 Severity: serious Dear Maintainer, the command "dpkg-reconfigure ca-certificates" produces the links "/libnss3.so" and "/libsoftokn3.so". This is due to a bug in the script "/etc/ca-certificates/update.d/jks-keystore": in the script the file "/etc/java-6-openjdk/security/nss.cfg" is searched for the term "nssLibraryDirectory" which is only to be found in "/etc/java-6-openjdk/security/nss-amd64.cfg" on my system. Therefore, the variable "nssjdk" stays empty resulting in the command ln -sf /usr/lib/x86_64-linux-gnu/libnss3.so / ln -sf /usr/lib/x86_64-linux-gnu/nss/libsoftokn3.so / A remedy seems to me, e.g., to do the search in "/etc/java-6-openjdk/security/nss*.cfg" (using a wildcard in the file name). -- Best regards, Jörg-Volker. -- System Information: Debian Release: wheezy/sid APT prefers testing APT policy: (600, 'testing'), (500, 'unstable'), (5, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 3.2.13 (SMP w/2 CPU cores) Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968) Shell: /bin/sh linked to /bin/dash Versions of packages ca-certificates depends on: ii debconf [debconf-2.0] 1.5.41 ii openssl1.0.0h-1 ca-certificates recommends no packages. ca-certificates suggests no packages. --- End Message --- --- Begin Message --- Source: ca-certificates-java Source-Version: 20120524 We believe that the bug you reported is fixed in the latest version of ca-certificates-java, which is due to be installed in the Debian FTP archive: ca-certificates-java_20120524.dsc to main/c/ca-certificates-java/ca-certificates-java_20120524.dsc ca-certificates-java_20120524.tar.gz to main/c/ca-certificates-java/ca-certificates-java_20120524.tar.gz ca-certificates-java_20120524_all.deb to main/c/ca-certificates-java/ca-certificates-java_20120524_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 665...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Damien Raude-Morvan (supplier of updated ca-certificates-java 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, 22 May 2012 23:41:41 +0200 Source: ca-certificates-java Binary: ca-certificates-java Architecture: source all Version: 20120524 Distribution: sid Urgency: low Maintainer: Debian Java Maintainers Changed-By: Damien Raude-Morvan Description: ca-certificates-java - Common CA certificates (JKS keystore) Closes: 665749 665754 Changes: ca-certificates-java (20120524) unstable; urgency=low . [ Marc Deslauriers ] * debian/preinst, debian/postinst: remove the 20110912ubuntu1 work-around since it is no longer needed. * debian/postinst: don't put a symlink in / if jvm doesn't contain nss configuration. (Closes: #665754, #665749). * debian/postinst: force migration to new alias names again. The migration was supposed to occur on upgrades to Oneiric, but failed because of an NSS error. * debian/postinst: forcibly remove diginotar cert. It could be left behind under certain circumstances. (LP: #920758) * debian/postinst: also look for jvm in multiarch locations (LP: #962378) * debian/postinst: retrigger first_install to properly get cert store. . [ James Page ] * d/rules: Ensure java is built with source/target == 1.6 for backwards compatibility with openjdk-6. . [ Damien Raude-Morvan ] * Sync handling of nss.cfg between debian/jks-keystore.hook.in and debian/postinst.in. * Merge changes from Ubuntu (Thanks to James Page and Marc Deslauriers). * Improve handling of certificate wit
Bug#665749: marked as done (ca-certificates-java: postinst script generates link /libnss3.so)
Your message dated Thu, 24 May 2012 21:02:13 + with message-id and subject line Bug#665754: fixed in ca-certificates-java 20120524 has caused the Debian Bug report #665754, regarding ca-certificates-java: postinst script generates link /libnss3.so 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.) -- 665754: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=665754 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: ca-certificates-java Version: 20120225 Severity: serious Dear Maintainer, the postinst script of package "ca-certificate-java" seems to me bogus: in the function "first_install()" the file "/etc/java-6-openjdk/security/nss.cfg" is searched for the term "nssLibraryDirectory" which is only to be found in "/etc/java-6-openjdk/security/nss-amd64.cfg" on my system. Therefore, the variable "nssjdk" stays empty resulting in the command ln -sf /usr/lib/x86_64-linux-gnu/libnss3.so /libnss3.so Doesn't this link in "/" violate the debian policy? -- Best regards, Jörg-Volker. -- System Information: Debian Release: wheezy/sid APT prefers testing APT policy: (600, 'testing'), (500, 'unstable'), (5, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 3.2.13 (SMP w/2 CPU cores) Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968) Shell: /bin/sh linked to /bin/dash Versions of packages ca-certificates-java depends on: ii ca-certificates 20120212 ii default-jre-headless [java6-runtime-headless]1:1.6-47 ii libnss3-1d 3.13.3-1 ii openjdk-6-jre-headless [java6-runtime-headless] 6b24-1.11.1-3 ca-certificates-java recommends no packages. ca-certificates-java suggests no packages. -- Configuration Files: /etc/default/cacerts [Errno 13] Permission denied: u'/etc/default/cacerts' -- no debconf information --- End Message --- --- Begin Message --- Source: ca-certificates-java Source-Version: 20120524 We believe that the bug you reported is fixed in the latest version of ca-certificates-java, which is due to be installed in the Debian FTP archive: ca-certificates-java_20120524.dsc to main/c/ca-certificates-java/ca-certificates-java_20120524.dsc ca-certificates-java_20120524.tar.gz to main/c/ca-certificates-java/ca-certificates-java_20120524.tar.gz ca-certificates-java_20120524_all.deb to main/c/ca-certificates-java/ca-certificates-java_20120524_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 665...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Damien Raude-Morvan (supplier of updated ca-certificates-java 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, 22 May 2012 23:41:41 +0200 Source: ca-certificates-java Binary: ca-certificates-java Architecture: source all Version: 20120524 Distribution: sid Urgency: low Maintainer: Debian Java Maintainers Changed-By: Damien Raude-Morvan Description: ca-certificates-java - Common CA certificates (JKS keystore) Closes: 665749 665754 Changes: ca-certificates-java (20120524) unstable; urgency=low . [ Marc Deslauriers ] * debian/preinst, debian/postinst: remove the 20110912ubuntu1 work-around since it is no longer needed. * debian/postinst: don't put a symlink in / if jvm doesn't contain nss configuration. (Closes: #665754, #665749). * debian/postinst: force migration to new alias names again. The migration was supposed to occur on upgrades to Oneiric, but failed because of an NSS error. * debian/postinst: forcibly remove diginotar cert. It could be left behind under certain circumstances. (LP: #920758) * debian/postinst: also look for jvm in multiarch locations (LP: #962378) * debian/postinst: retrigger first_install to properly get cert store. . [ James Page ] * d/rules: Ensure java is built with source/target == 1.6 for backwards compatibility with openjdk-6. . [ Damien Raude-Morvan ] * Sync handling of nss.cfg between debian/jks-keystore.hook.in and debian/postinst.in. * Merge changes from Ubuntu (Tha
Bug#665754: marked as done (ca-certificates: reconfiguration creates links in "/")
Your message dated Thu, 24 May 2012 21:02:13 + with message-id and subject line Bug#665749: fixed in ca-certificates-java 20120524 has caused the Debian Bug report #665749, regarding ca-certificates: reconfiguration creates links in "/" 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.) -- 665749: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=665749 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: ca-certificates Version: 20120212 Severity: serious Dear Maintainer, the command "dpkg-reconfigure ca-certificates" produces the links "/libnss3.so" and "/libsoftokn3.so". This is due to a bug in the script "/etc/ca-certificates/update.d/jks-keystore": in the script the file "/etc/java-6-openjdk/security/nss.cfg" is searched for the term "nssLibraryDirectory" which is only to be found in "/etc/java-6-openjdk/security/nss-amd64.cfg" on my system. Therefore, the variable "nssjdk" stays empty resulting in the command ln -sf /usr/lib/x86_64-linux-gnu/libnss3.so / ln -sf /usr/lib/x86_64-linux-gnu/nss/libsoftokn3.so / A remedy seems to me, e.g., to do the search in "/etc/java-6-openjdk/security/nss*.cfg" (using a wildcard in the file name). -- Best regards, Jörg-Volker. -- System Information: Debian Release: wheezy/sid APT prefers testing APT policy: (600, 'testing'), (500, 'unstable'), (5, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 3.2.13 (SMP w/2 CPU cores) Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968) Shell: /bin/sh linked to /bin/dash Versions of packages ca-certificates depends on: ii debconf [debconf-2.0] 1.5.41 ii openssl1.0.0h-1 ca-certificates recommends no packages. ca-certificates suggests no packages. --- End Message --- --- Begin Message --- Source: ca-certificates-java Source-Version: 20120524 We believe that the bug you reported is fixed in the latest version of ca-certificates-java, which is due to be installed in the Debian FTP archive: ca-certificates-java_20120524.dsc to main/c/ca-certificates-java/ca-certificates-java_20120524.dsc ca-certificates-java_20120524.tar.gz to main/c/ca-certificates-java/ca-certificates-java_20120524.tar.gz ca-certificates-java_20120524_all.deb to main/c/ca-certificates-java/ca-certificates-java_20120524_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 665...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Damien Raude-Morvan (supplier of updated ca-certificates-java 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, 22 May 2012 23:41:41 +0200 Source: ca-certificates-java Binary: ca-certificates-java Architecture: source all Version: 20120524 Distribution: sid Urgency: low Maintainer: Debian Java Maintainers Changed-By: Damien Raude-Morvan Description: ca-certificates-java - Common CA certificates (JKS keystore) Closes: 665749 665754 Changes: ca-certificates-java (20120524) unstable; urgency=low . [ Marc Deslauriers ] * debian/preinst, debian/postinst: remove the 20110912ubuntu1 work-around since it is no longer needed. * debian/postinst: don't put a symlink in / if jvm doesn't contain nss configuration. (Closes: #665754, #665749). * debian/postinst: force migration to new alias names again. The migration was supposed to occur on upgrades to Oneiric, but failed because of an NSS error. * debian/postinst: forcibly remove diginotar cert. It could be left behind under certain circumstances. (LP: #920758) * debian/postinst: also look for jvm in multiarch locations (LP: #962378) * debian/postinst: retrigger first_install to properly get cert store. . [ James Page ] * d/rules: Ensure java is built with source/target == 1.6 for backwards compatibility with openjdk-6. . [ Damien Raude-Morvan ] * Sync handling of nss.cfg between debian/jks-keystore.hook.in and debian/postinst.in. * Merge changes from Ubuntu (Thanks to James Page and Marc Deslauriers). * Improve handling of certificate wit
Bug#665749: marked as done (ca-certificates-java: postinst script generates link /libnss3.so)
Your message dated Thu, 24 May 2012 21:02:13 + with message-id and subject line Bug#665749: fixed in ca-certificates-java 20120524 has caused the Debian Bug report #665749, regarding ca-certificates-java: postinst script generates link /libnss3.so 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.) -- 665749: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=665749 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: ca-certificates-java Version: 20120225 Severity: serious Dear Maintainer, the postinst script of package "ca-certificate-java" seems to me bogus: in the function "first_install()" the file "/etc/java-6-openjdk/security/nss.cfg" is searched for the term "nssLibraryDirectory" which is only to be found in "/etc/java-6-openjdk/security/nss-amd64.cfg" on my system. Therefore, the variable "nssjdk" stays empty resulting in the command ln -sf /usr/lib/x86_64-linux-gnu/libnss3.so /libnss3.so Doesn't this link in "/" violate the debian policy? -- Best regards, Jörg-Volker. -- System Information: Debian Release: wheezy/sid APT prefers testing APT policy: (600, 'testing'), (500, 'unstable'), (5, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 3.2.13 (SMP w/2 CPU cores) Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968) Shell: /bin/sh linked to /bin/dash Versions of packages ca-certificates-java depends on: ii ca-certificates 20120212 ii default-jre-headless [java6-runtime-headless]1:1.6-47 ii libnss3-1d 3.13.3-1 ii openjdk-6-jre-headless [java6-runtime-headless] 6b24-1.11.1-3 ca-certificates-java recommends no packages. ca-certificates-java suggests no packages. -- Configuration Files: /etc/default/cacerts [Errno 13] Permission denied: u'/etc/default/cacerts' -- no debconf information --- End Message --- --- Begin Message --- Source: ca-certificates-java Source-Version: 20120524 We believe that the bug you reported is fixed in the latest version of ca-certificates-java, which is due to be installed in the Debian FTP archive: ca-certificates-java_20120524.dsc to main/c/ca-certificates-java/ca-certificates-java_20120524.dsc ca-certificates-java_20120524.tar.gz to main/c/ca-certificates-java/ca-certificates-java_20120524.tar.gz ca-certificates-java_20120524_all.deb to main/c/ca-certificates-java/ca-certificates-java_20120524_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 665...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Damien Raude-Morvan (supplier of updated ca-certificates-java 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, 22 May 2012 23:41:41 +0200 Source: ca-certificates-java Binary: ca-certificates-java Architecture: source all Version: 20120524 Distribution: sid Urgency: low Maintainer: Debian Java Maintainers Changed-By: Damien Raude-Morvan Description: ca-certificates-java - Common CA certificates (JKS keystore) Closes: 665749 665754 Changes: ca-certificates-java (20120524) unstable; urgency=low . [ Marc Deslauriers ] * debian/preinst, debian/postinst: remove the 20110912ubuntu1 work-around since it is no longer needed. * debian/postinst: don't put a symlink in / if jvm doesn't contain nss configuration. (Closes: #665754, #665749). * debian/postinst: force migration to new alias names again. The migration was supposed to occur on upgrades to Oneiric, but failed because of an NSS error. * debian/postinst: forcibly remove diginotar cert. It could be left behind under certain circumstances. (LP: #920758) * debian/postinst: also look for jvm in multiarch locations (LP: #962378) * debian/postinst: retrigger first_install to properly get cert store. . [ James Page ] * d/rules: Ensure java is built with source/target == 1.6 for backwards compatibility with openjdk-6. . [ Damien Raude-Morvan ] * Sync handling of nss.cfg between debian/jks-keystore.hook.in and debian/postinst.in. * Merge changes from Ubuntu (Tha
Bug#672678: (cryptmount #672678) unmet dependency on libdevmapper
[Taking this off of -release] On Thu, 24 May 2012, Laszlo Boszormenyi (GCS) wrote: > I'm the sponsor of Richard, the maintainer of cryptmount. He has > fixed this issue some days ago and asked me about to upload that. > However it changes old debian/copyright entries. He changes the > 'closes: #xxx reason' lines to 'reason, closes: #xxx' ones. It's a > bit unclear for me if it's advised or not. Can't recall any policy > about this, but AFAICR, it should not be changed. In short, may I > upload the package despite the altering of changelog wording? In general, it's better not to muck with historical changelog entries, but it doesn't really matter. [As a side note, it'd be useful to send these sorts of things to the bug log and tag them pending, so other people don't come by and spend time NMUing unnecessarily.] Also, not sure why lvm removed the Provides: libdevmapper... probably shouldn't have been done, but if cryptmount is the only thing affected, not much harm done. Don Armstrong -- Show me your flowcharts and conceal your tables, and I shall continue to be mystified. Show me your tables, and I won't usually need your flowcharts; they'll be obvious. -- Fredrick P. Brooks Jr., The Mythical Man Month http://www.donarmstrong.com http://rzlab.ucr.edu -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Processed: r2120 - in mysql-5.5/branches/wheezy/debian: . patches
Processing commands for cont...@bugs.debian.org: > tags 674210 pending Bug #674210 [mysql-5.5] FTBS: when build directory contains: '+' Added tag(s) pending. > thanks Stopping processing here. Please contact me if you need assistance. -- 674210: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=674210 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#674328: mediatomb: FTBFS: conftest.c:131: undefined reference to `_doprnt'
Hello: >From the provided logs I can see: Get:107 http://localhost/debian/ unstable/main libmysqlclient-dev amd64 5.5.23-2 [1178 kB] checking mysql libs... -L/usr/lib/x86_64-linux-gnu -lmysqlclient_r -lpthread -lz -lm -lrt -lssl -lcrypto -ldl checking mysql.h usability... yes checking mysql.h presence... yes checking for mysql.h... yes checking for mysql_init... no configure: error: unable to configure mysql support This is supposed to be fixed in libmysqlclient-dev (>= 5.5.23+dfsg-1) but https://buildd.debian.org/status/package.php?p=mysql-5.5 shows that this packages FTBFS in amd64. I just compiled the package in a clean and updated amd64 chroot and using the workaround of adding libssl-dev as a build-dependency made it compile fine. This bug should fix itself whenever the mysql package gets fixed. Merging with the original report. 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
Processed: your mail
Processing commands for cont...@bugs.debian.org: > reassign 672824 src:mediatomb Bug #672824 [mediatomb] mediatomb: FTBFS on sid: checking for mysql_init... no Bug reassigned from package 'mediatomb' to 'src:mediatomb'. No longer marked as found in versions mediatomb/0.12.1-4. Ignoring request to alter fixed versions of bug #672824 to the same values previously set > forcemerge 672824 674328 Bug #672824 [src:mediatomb] mediatomb: FTBFS on sid: checking for mysql_init... no Bug #674328 [src:mediatomb] mediatomb: FTBFS: conftest.c:131: undefined reference to `_doprnt' 671115 was blocked by: 672765 673528 673260 673161 667428 673183 673263 668232 649638 650058 673153 649955 651110 672824 650060 672714 666331 672619 672950 673264 672716 672621 672816 651317 674210 672207 673262 672588 671115 was blocking: 672928 Added blocking bug(s) of 671115: 674328 674328 was not blocked by any bugs. 674328 was blocking: 671115 Added blocking bug(s) of 674328: 590905, 604887, and 590906 674328 was blocked by: 590905 604887 590906 674328 was blocking: 671115 Ignoring request to alter blocking bugs of bug #674328 to the same blocks previously set 674328 was blocked by: 590905 604887 590906 674328 was blocking: 671115 Ignoring request to alter blocking bugs of bug #674328 to the same blocks previously set Bug #672824 [src:mediatomb] mediatomb: FTBFS on sid: checking for mysql_init... no Marked as found in versions mediatomb/0.12.1-4. Added tag(s) sid and wheezy. Merged 672824 674328 > thanks Stopping processing here. Please contact me if you need assistance. -- 671115: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=671115 672824: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=672824 674328: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=674328 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#673736: closed by Khalid El Fathi (Bug#673736: fixed in libdivecomputer 0.1.0-2)
Hi Ralf, On 05/23/2012 09:56 PM, Ralf Treinen wrote: > thanks for fixing that, but please tell in the changelog what precisely you > did to fix that file overwrite (like renaming this file to that, or not > installing this file in that package, or something else ?) This is done for the next release. Cheers, Khalid. -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Processed (with 1 errors): 674...@bugs.debian.org,lu...@lucas-nussbaum.net
Processing commands for cont...@bugs.debian.org:
> forcemerge 672824 674328
Bug #672824 [mediatomb] mediatomb: FTBFS on sid: checking for mysql_init... no
Unable to merge bugs because:
package of #674328 is 'src:mediatomb' not 'mediatomb'
Failed to forcibly merge 672824: Did not alter merged bugs
Debbugs::Control::set_merged('transcript', 'GLOB(0x1cf58f0)',
'requester', 'Miguel A. Col\x{c3}\x{b3}n V\x{c3}\x{a9}lez
', 'request_addr', 'cont...@bugs.debian.org',
'request_msgid',
' thanks
Stopping processing here.
Please contact me if you need assistance.
--
672824: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=672824
674328: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=674328
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#672035: [Swig-user] Using own string class
We do the same thing here, we just use basic in/out typemaps.
E.g.
%typemap(out) YString
{
$result = PyString_FromString((char *)static_cast($1));
}
%typemap(in) const YString &
{
$1 = new YString(PyString_AsString($input));
}
-Original Message-
From: Alexey Sokolov [mailto:ale...@asokolov.org]
Sent: Thursday, May 24, 2012 2:46 PM
To: swig-u...@lists.sourceforge.net; 672...@bugs.debian.org
Subject: [Swig-user] Using own string class
Hello!
At ZNC we have an own string class CString, which is inherited from std::string.
The goal is to use it as a just string in target languages.
How to do that properly?
When I was writing modperl and modpython ZNC modules, I used an approach
described at http://old.nabble.com/Forward-declaration-error--td24064356.html
Used "swig -E" on std_string.i, got a long file as a result, cleaned it up and
changed all occurences of std::string to CString.
It worked fine before SWIG 2.0.5, but in 2.0.5 it started to give errors while
generating sources for modpython:
/usr/share/swig/2.0.6/std/std_pair.i:31: Error: Can't copy typemap
(directorout) std::pair< CString,CString > = std::pair< CString,CString
> &DIRECTOROUT
/usr/share/swig/2.0.6/std/std_pair.i:31: Error: Can't copy typemap (in)
std::pair< CString,CString > *INPUT = std::pair< CString,CString > *INOUT
/usr/share/swig/2.0.6/std/std_pair.i:31: Error: Can't copy typemap (in)
std::pair< CString,CString > &INPUT = std::pair< CString,CString > &INOUT
/usr/share/swig/2.0.6/std/std_pair.i:31: Error: Can't copy typemap
(typecheck) std::pair< CString,CString > *INPUT = std::pair< CString,CString >
*INOUT
/usr/share/swig/2.0.6/std/std_pair.i:31: Error: Can't copy typemap
(typecheck) std::pair< CString,CString > &INPUT = std::pair< CString,CString >
&INOUT
/usr/share/swig/2.0.6/std/std_pair.i:31: Error: Can't copy typemap
(argout) std::pair< CString,CString > *OUTPUT = std::pair< CString,CString >
*INOUT
/usr/share/swig/2.0.6/std/std_pair.i:31: Error: Can't copy typemap
(argout) std::pair< CString,CString > &OUTPUT = std::pair< CString,CString >
&INOUT
/usr/share/swig/2.0.6/std/std_pair.i:31: Error: Can't copy typemap
(typecheck) std::pair< CString,CString > *INPUT = std::pair< CString,CString >
*INOUT
/usr/share/swig/2.0.6/std/std_pair.i:31: Error: Can't copy typemap
(typecheck) std::pair< CString,CString > &INPUT = std::pair< CString,CString >
&INOUT
/usr/share/swig/2.0.6/std/std_pair.i:31: Error: Can't copy typemap
(freearg) std::pair< CString,CString > *INPUT = std::pair< CString,CString >
*INOUT
/usr/share/swig/2.0.6/std/std_pair.i:31: Error: Can't copy typemap
(freearg) std::pair< CString,CString > &INPUT = std::pair< CString,CString >
&INOUT
Sending copy of the letter to 672...@bugs.debian.org Also there is related
issue #174 on github/znc.
--
Best regards,
Alexey "DarthGandalf" Sokolov
'Like' us on Facebook for exclusive content and other resources on all
Barracuda Networks solutions.
Visit http://barracudanetworks.com/facebook
Bug#623882: error installing certs with non-ascii characters in their names
Hi Miguel, Le samedi 29 octobre 2011 21:08:36, Miguel Landaeta a écrit : > Is this really fixed? > > I ask because I still can see some warnings or errors when > ca-certificates-java install certificates with non-ascii filenames: > > [snip] > > Setting up ca-certificates-java (20110912) ... > Adding debian:Taiwan_GRCA.pem > Adding debian:Digital_Signature_Trust_Co._Global_CA_1.pem > Adding debian:AddTrust_Qualified_Certificates_Root.pem > Adding debian:NetLock_Notary_=Class_A=_Root.pem > Adding debian:ValiCert_Class_1_VA.pem > Adding debian:signet_ca3_pem.pem > Adding debian:UTN_USERFirst_Hardware_Root_CA.pem > Warning: there was a problem reading the certificate file > /etc/ssl/certs/T??B??TAK_UEKAE_K??k_Sertifika_Hizmet_Sa??lay??c??s??_-_S?? > r??m_3.pem. Message: > /etc/ssl/certs/T??B??TAK_UEKAE_K??k_Sertifika_Hizmet_Sa??lay??c??s??_-_S?? > r??m_3.pem (No such file or directory) Adding debian:cacert.org.pem > Warning: there was a problem reading the certificate file > /etc/ssl/certs/Certinomis_-_Autorit??_Racine.pem. Message: > /etc/ssl/certs/Certinomis_-_Autorit??_Racine.pem (No such file or > directory) Adding > debian:Verisign_Class_4_Public_Primary_Certification_Authority_-_G2.pem > Adding debian:Certplus_Class_2_Primary_CA.pem > Warning: there was a problem reading the certificate file > /etc/ssl/certs/AC_Ra??z_Certic??mara_S.A..pem. Message: > /etc/ssl/certs/AC_Ra??z_Certic??mara_S.A..pem (No such file or directory) I've improved existing fix for encoding issues into 20120524 upload, so you might not see this warning anymore :) Cheers, -- Damien signature.asc Description: This is a digitally signed message part.
Bug#655330: marked as done (installation of ca-certificates-java silently fails)
Your message dated Thu, 24 May 2012 22:10:08 +0200 with message-id <201205242210.12121.draz...@debian.org> and subject line Re: Bug#655330: installation of ca-certificates-java silently fails has caused the Debian Bug report #655330, regarding installation of ca-certificates-java silently fails 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.) -- 655330: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=655330 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: ca-certificates-java Version: 20111223 Severity: grave Happens when updating from squeeze. During installation, the following is printed: Setting up ca-certificates-java (20111223) ...Installing new version of config file /etc/ca-certificates/update.d/jks-keystore ...Exception in thread "main" java.security.ProviderException: Could not initialize NSS at sun.security.pkcs11.SunPKCS11.(SunPKCS11.java:201) at sun.security.pkcs11.SunPKCS11.(SunPKCS11.java:103) at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method) at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:57) at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45) at java.lang.reflect.Constructor.newInstance(Constructor.java:532) at sun.security.jca.ProviderConfig$3.run(ProviderConfig.java:262) at sun.security.jca.ProviderConfig$3.run(ProviderConfig.java:244) at java.security.AccessController.doPrivileged(Native Method) at sun.security.jca.ProviderConfig.doLoadProvider(ProviderConfig.java:244) at sun.security.jca.ProviderConfig.getProvider(ProviderConfig.java:224) at sun.security.jca.ProviderList.getProvider(ProviderList.java:232) at sun.security.jca.ProviderList.getService(ProviderList.java:330) at sun.security.jca.GetInstance.getInstance(GetInstance.java:157) at java.security.Security.getImpl(Security.java:696) at java.security.AlgorithmParameters.getInstance(AlgorithmParameters.java:130) at sun.security.x509.AlgorithmId.decodeParams(AlgorithmId.java:121) at sun.security.x509.AlgorithmId.(AlgorithmId.java:114) at sun.security.x509.AlgorithmId.parse(AlgorithmId.java:381) at sun.security.x509.X509Key.parse(X509Key.java:168) at sun.security.x509.CertificateX509Key.(CertificateX509Key.java:75) at sun.security.x509.X509CertInfo.parse(X509CertInfo.java:705) at sun.security.x509.X509CertInfo.(X509CertInfo.java:169) at sun.security.x509.X509CertImpl.parse(X509CertImpl.java:1747) at sun.security.x509.X509CertImpl.(X509CertImpl.java:196) at sun.security.provider.X509Factory.engineGenerateCertificate(X509Factory.java:107) at java.security.cert.CertificateFactory.generateCertificate(CertificateFactory.java:322) at sun.security.provider.JavaKeyStore.engineLoad(JavaKeyStore.java:763) at sun.security.provider.JavaKeyStore$JKS.engineLoad(JavaKeyStore.java:55) at java.security.KeyStore.load(KeyStore.java:1201) at UpdateCertificates.createKeyStore(UpdateCertificates.java:65) at UpdateCertificates.main(UpdateCertificates.java:51)Caused by: java.io.FileNotFoundException: /usr/lib/libnss3.so at sun.security.pkcs11.Secmod.initialize(Secmod.java:186) at sun.security.pkcs11.SunPKCS11.(SunPKCS11.java:197) ... 31 moredone. --- End Message --- --- Begin Message --- Hi Cyril, Le samedi 18 février 2012 17:27:00, Cyril Brulebois a écrit : > Cyril Brulebois (18/02/2012): > > I'll try and debug it further soon. > > That wasn't too hard: switching from stable's to testing's libnss3-1d, > its .so switches from /usr/lib to /usr/lib/; given > nssLibraryDirectory is written to /etc/java-6-openjdk/security/nss.cfg > only when first_install is run, you don't get to notice the location > change. I'm not sure how to best fix that though. Since some uploades, java-[67]-openjdk doesn't set nssLibraryDirectory anymore (it then default to search path of dllopen - like any other program). I've done some more tests of squeeze -> wheezy/sid upgrade and can't reproduce this issue with current ca-certificate-java and openjdk-6. So I'm now closing this issue, feel free to reopen if you can reproduce it with other mean. Cheers, -- Damien - Debian Developper http://wiki.debian.org/DamienRaudeMorvan signature.asc Description: This is a digitally signed message part. --- End Message ---
Bug#674460: initscripts: prompting due to modified conffiles which were not modified by the user
Package: initscripts Version: 2.88dsf-25 Severity: serious User: debian...@lists.debian.org Usertags: piuparts Hi, during a test with piuparts I noticed your package failed the piuparts upgrade test because dpkg detected a conffile as being modified and then prompted the user for an action. As there is no user input, this fails. But this is not the real problem, the real problem is that this prompt shows up in the first place, as there was nobody modifying this conffile at all, the package has just been installed and upgraded... This is a violation of policy 10.7.3, see http://www.debian.org/doc/debian-policy/ch-files.html#s10.7.3, which says "[These scripts handling conffiles] must not ask unnecessary questions (particularly during upgrades), and must otherwise be good citizens." http://wiki.debian.org/DpkgConffileHandling should help with figuring out how to do this properly. In http://lists.debian.org/debian-devel/2009/08/msg00675.html and followups it has been agreed that these bugs are to be filed with severity serious. >From the attached log (scroll to the bottom...): Preparing to replace initscripts 2.88dsf-22.1 (using .../initscripts_2.88dsf-25_amd64.deb) ... Removing unmodified and obsolete conffile /etc/init.d/mountoverflowtmp ... Removing unmodified and obsolete conffile /etc/init.d/bootlogs ... Unpacking replacement initscripts ... Setting up initscripts (2.88dsf-25) ... Installing new version of config file /etc/init.d/bootmisc.sh ... Installing new version of config file /etc/init.d/mountall.sh ... Installing new version of config file /etc/init.d/mountall-bootclean.sh ... Installing new version of config file /etc/init.d/mountnfs-bootclean.sh ... Installing new version of config file /etc/init.d/mountdevsubfs.sh ... Installing new version of config file /etc/init.d/mountkernfs.sh ... Installing new version of config file /etc/init.d/umountnfs.sh ... Installing new version of config file /etc/init.d/urandom ... Configuration file `/etc/default/rcS' ==> File on system created by you or by a script. ==> File also in package provided by package maintainer. What would you like to do about it ? Your options are: Y or I : install the package maintainer's version N or O : keep your currently-installed version D : show the differences between the versions Z : start a shell to examine the situation The default action is to keep your current version. *** rcS (Y/I/N/O/D/Z) [default=N] ? dpkg: error processing initscripts (--configure): EOF on stdin at conffile prompt Errors were encountered while processing: initscripts This was observed on a distupgrade from sid to experimental. There needs to be a way to detect if /etc/default/rcS is "unmodified" (and there are probably a lot of different unmodified variants that should allow seamless upgrades) before it's made a conffile. cheers, Andreas dose-distcheck_2.9.16~rc1-1.log.gz Description: GNU Zip compressed data
Bug#672035: Using own string class
Hello! At ZNC we have an own string class CString, which is inherited from std::string. The goal is to use it as a just string in target languages. How to do that properly? When I was writing modperl and modpython ZNC modules, I used an approach described at http://old.nabble.com/Forward-declaration-error--td24064356.html Used "swig -E" on std_string.i, got a long file as a result, cleaned it up and changed all occurences of std::string to CString. It worked fine before SWIG 2.0.5, but in 2.0.5 it started to give errors while generating sources for modpython: /usr/share/swig/2.0.6/std/std_pair.i:31: Error: Can't copy typemap (directorout) std::pair< CString,CString > = std::pair< CString,CString > &DIRECTOROUT /usr/share/swig/2.0.6/std/std_pair.i:31: Error: Can't copy typemap (in) std::pair< CString,CString > *INPUT = std::pair< CString,CString > *INOUT /usr/share/swig/2.0.6/std/std_pair.i:31: Error: Can't copy typemap (in) std::pair< CString,CString > &INPUT = std::pair< CString,CString > &INOUT /usr/share/swig/2.0.6/std/std_pair.i:31: Error: Can't copy typemap (typecheck) std::pair< CString,CString > *INPUT = std::pair< CString,CString > *INOUT /usr/share/swig/2.0.6/std/std_pair.i:31: Error: Can't copy typemap (typecheck) std::pair< CString,CString > &INPUT = std::pair< CString,CString > &INOUT /usr/share/swig/2.0.6/std/std_pair.i:31: Error: Can't copy typemap (argout) std::pair< CString,CString > *OUTPUT = std::pair< CString,CString > *INOUT /usr/share/swig/2.0.6/std/std_pair.i:31: Error: Can't copy typemap (argout) std::pair< CString,CString > &OUTPUT = std::pair< CString,CString > &INOUT /usr/share/swig/2.0.6/std/std_pair.i:31: Error: Can't copy typemap (typecheck) std::pair< CString,CString > *INPUT = std::pair< CString,CString > *INOUT /usr/share/swig/2.0.6/std/std_pair.i:31: Error: Can't copy typemap (typecheck) std::pair< CString,CString > &INPUT = std::pair< CString,CString > &INOUT /usr/share/swig/2.0.6/std/std_pair.i:31: Error: Can't copy typemap (freearg) std::pair< CString,CString > *INPUT = std::pair< CString,CString > *INOUT /usr/share/swig/2.0.6/std/std_pair.i:31: Error: Can't copy typemap (freearg) std::pair< CString,CString > &INPUT = std::pair< CString,CString > &INOUT Sending copy of the letter to 672...@bugs.debian.org Also there is related issue #174 on github/znc. -- Best regards, Alexey "DarthGandalf" Sokolov signature.asc Description: OpenPGP digital signature
Bug#672678: (cryptmount #672678) unmet dependency on libdevmapper
Hi all, On Thu, 2012-05-24 at 02:50 +0300, Touko Korpela wrote: > On Wed, May 23, 2012 at 11:31:33PM +0300, Touko Korpela wrote: > > This bug blocks lvm2 from migrating to testing. Maybe cryptmount should > > temporarily removed from testing? Or are tools wrong, and lvm2 update > > don't make situation any worse than it's now? > > Has release managers opinion about this? I'm the sponsor of Richard, the maintainer of cryptmount. He has fixed this issue some days ago and asked me about to upload that. However it changes old debian/copyright entries. He changes the 'closes: #xxx reason' lines to 'reason, closes: #xxx' ones. It's a bit unclear for me if it's advised or not. Can't recall any policy about this, but AFAICR, it should not be changed. In short, may I upload the package despite the altering of changelog wording? Regards, Laszlo/GCS -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#674395: libdbd-mysql-perl: FTBFS: ld: cannot find -lssl
Yeah the SSL stuff should have gone away now. (Except for the moment on amd64 where a Perl regular expression messed things up. ;-) ) On 24/05/12 13:38, gregor herrmann wrote: On Thu, 24 May 2012 14:23:17 +0200, Salvatore Bonaccorso wrote: Can confirm this, and adding libssl-dev to Build-Depends solves the FTBFS. I haven't looked yet, but this seems new ... Can this be related to changes in libmysqlclient-dev from 5.1 to 5.5? http://packages.debian.org/changelogs/pool/main/m/mysql-5.5/current/changelog mentions SSL stuff at some points ... (Random factoid: Lucas' rebuild was against libmysqlclient-dev 5.5.23-2, yesterday 5.5.23+dfsg-1 was uploaded with the changelog entry: * Revert having libssl-dev as a build dependency and changed WITH_SSL option to 'bundled' from 'yes' (Closes: #590905) and (Closes: #673865) ) Luckily periapt is involved here and there and might know better what's going on :) Cheers, gregor -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#674346: marked as done (soprano: FTBFS: /bin/sh: 1: docs/html/installdox: not found)
Your message dated Thu, 24 May 2012 18:33:36 + with message-id and subject line Bug#674346: fixed in soprano 2.7.6+dfsg.1-1 has caused the Debian Bug report #674346, regarding soprano: FTBFS: /bin/sh: 1: docs/html/installdox: not found 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.) -- 674346: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=674346 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: soprano Version: 2.7.5+dfsg.1-1 Severity: serious Tags: wheezy sid User: debian...@lists.debian.org Usertags: qa-ftbfs-20120524 qa-ftbfs Justification: FTBFS on amd64 Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part: > make[4]: Entering directory `/«BUILDDIR»/soprano-2.7.5+dfsg.1/Build' > /usr/bin/cmake -E cmake_progress_report > /«BUILDDIR»/soprano-2.7.5+dfsg.1/Build/CMakeFiles > [ 0%] Building Soprano API docs... > /usr/bin/doxygen Doxyfile > warning: Tag `SHOW_DIRECTORIES' at line 72 of file Doxyfile has become > obsolete. > To avoid this warning please remove this line from your configuration file or > upgrade it using "doxygen -u" > warning: Tag `HTML_ALIGN_MEMBERS' at line 163 of file Doxyfile has become > obsolete. > To avoid this warning please remove this line from your configuration file or > upgrade it using "doxygen -u" > warning: Included by graph for 'soprano_export.h' not generated, too many > nodes. Consider increasing DOT_GRAPH_MAX_NODES. > /«BUILDDIR»/soprano-2.7.5+dfsg.1/Mainpage.dox:117: warning: unable to resolve > reference to `soprano_backend_redland' for \ref command > /«BUILDDIR»/soprano-2.7.5+dfsg.1/Mainpage.dox:118: warning: unable to resolve > reference to `soprano_backend_sesame2' for \ref command > /«BUILDDIR»/soprano-2.7.5+dfsg.1/soprano/node.h:473: warning: The following > parameters of Soprano::Node::fromN3(const QString &n3, N3ParserFlags > flags=NoFlags) are not documented: > parameter 'flags' > /«BUILDDIR»/soprano-2.7.5+dfsg.1/soprano/node.h:487: warning: The following > parameters of Soprano::Node::fromN3Stream(QTextStream &stream, N3ParserFlags > flags=NoFlags) are not documented: > parameter 'flags' > /«BUILDDIR»/soprano-2.7.5+dfsg.1/client/sparql/sparqlmodel.h:150: warning: > Found unknown command `\reimpl' > /«BUILDDIR»/soprano-2.7.5+dfsg.1/client/sparql/sparqlmodel.h:201: warning: > Found unknown command `\reimpl' > /«BUILDDIR»/soprano-2.7.5+dfsg.1/client/sparql/sparqlmodel.h:206: warning: > argument 'statement' of command @param is not found in the argument list of > Soprano::Client::SparqlModel::listContextsAsync() const > /«BUILDDIR»/soprano-2.7.5+dfsg.1/client/sparql/sparqlmodel.h:218: warning: > Found unknown command `\reimpl' > /«BUILDDIR»/soprano-2.7.5+dfsg.1/client/sparql/sparqlmodel.h:223: warning: > Found unknown command `\reimpl' > /«BUILDDIR»/soprano-2.7.5+dfsg.1/soprano/util/asyncmodel.h:332: warning: > Found unknown command `\reimplemented' > /«BUILDDIR»/soprano-2.7.5+dfsg.1/soprano/util/asyncmodel.h:342: warning: > Found unknown command `\reimplemented' > /«BUILDDIR»/soprano-2.7.5+dfsg.1/soprano/util/asyncmodel.h:352: warning: > Found unknown command `\reimplemented' > /«BUILDDIR»/soprano-2.7.5+dfsg.1/soprano/vocabulary/xesam.h:1241: warning: > Found unknown command `\server' > docs/html/installdox -q -l qt4.tag@/usr/share/qt4/doc/html docs/html/*.html > /bin/sh: 1: docs/html/installdox: not found > make[4]: *** [CMakeFiles/apidox] Error 127 The full build log is available from: http://people.debian.org/~lucas/logs/2012/05/24/soprano_2.7.5+dfsg.1-1_unstable.log 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. --- End Message --- --- Begin Message --- Source: soprano Source-Version: 2.7.6+dfsg.1-1 We believe that the bug you reported is fixed in the latest version of soprano, which is due to be installed in the Debian FTP archive: libsoprano-dbg_2.7.6+dfsg.1-1_amd64.deb to main/s/soprano/libsoprano-dbg_2.7.6+dfsg.1-1_amd64.deb libsoprano-dev_2.7.6+dfsg.1-1_amd64.deb to main/s
Bug#674451: openstack-dashboard: Compilation failed on: http://localhost:8083/syspanel/
Package: openstack-dashboard
Version: 2012.1-4
Severity: grave
Justification: renders package unusable
Dear Maintainer,
*** Please consider answering these questions, where appropriate ***
* What led up to the situation?
* What exactly did you do (or not do) that was effective (or
ineffective)?
* What was the outcome of this action?
* What outcome did you expect instead?
*** End of the template - remove these lines ***
- When I connect with my web navigatpr and authentify myself, on:
http://localhost:8083 (The login page !)
The the dashbord fail the compilation with:
===8<
==
TypeError at /syspanel/
string indices must be integers, not str
Request Method: GET
Request URL:http://localhost:8083/syspanel/
Django Version: 1.4
Exception Type: TypeError
Exception Value:
string indices must be integers, not str
Exception Location:
/usr/lib/python2.7/dist-packages/novaclient/base.py in _list, line 76
Python Executable: /usr/bin/python
Python Version: 2.7.3
Python Path:
['/usr/share/openstack-dashboard/openstack_dashboard/wsgi/../..',
'/usr/local/lib/python2.7/dist-packages/multiprocessing-2.6.2.1-py2.7-linux-x86_64.egg',
'/usr/lib/python2.7',
'/usr/lib/python2.7/plat-linux2',
'/usr/lib/python2.7/lib-tk',
'/usr/lib/python2.7/lib-old',
'/usr/lib/python2.7/lib-dynload',
'/usr/local/lib/python2.7/dist-packages',
'/usr/lib/python2.7/dist-packages',
'/usr/lib/python2.7/dist-packages/PIL',
'/usr/lib/python2.7/dist-packages/gst-0.10',
'/usr/lib/python2.7/dist-packages/gtk-2.0',
'/usr/lib/pymodules/python2.7',
'/usr/lib/python2.7/dist-packages/wx-2.8-gtk2-unicode',
'/usr/share/openstack-dashboard/openstack_dashboard']
Server time: jeu, 24 Mai 2012 19:56:46 +0200
==8<===
If you want more output, tell me !
Thanks for the reply and the follow-up.
Best Regards,
Michael Chlon.
-- System Information:
Debian Release: wheezy/sid
APT prefers testing
APT policy: (999, 'testing'), (995, 'unstable'), (975, 'stable'), (500,
'stable-updates'), (500, 'sid'), (1, 'experimental')
Architecture: amd64 (x86_64)
Kernel: Linux 3.2.0-2-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/bash
Versions of packages openstack-dashboard depends on:
ii adduser3.113+nmu1
ii libjs-jquery 1.7.1-1
ii python 2.7.2-10
ii python-cloudfiles 1.7.9.2-1
ii python-django 1.4-1
ii python-django-horizon 2012.1-4
ii python-django-nose 0.1.3-1
ii python-iso8601 0.1.4-2
ii python-keystoneclient 2012.1-2
ii python-openstackx 0~dev20111219-1
openstack-dashboard recommends no packages.
openstack-dashboard suggests no packages.
-- Configuration Files:
/etc/openstack-dashboard/local_settings.py changed:
import os
from django.utils.translation import ugettext_lazy as _
QUANTUM_ENABLED = False
DEBUG = True
TEMPLATE_DEBUG = DEBUG
PROD = False
USE_SSL = False
SECRET_KEY = 'elj1IWiLoWHgcyYxFVLj7cM5rGOOxWl0'
LOCAL_PATH = os.path.dirname(os.path.abspath(__file__))
CACHE_BACKEND = 'locmem://'
EMAIL_BACKEND = 'django.core.mail.backends.console.EmailBackend'
OPENSTACK_HOST = "127.0.0.1"
OPENSTACK_KEYSTONE_URL = "http://%s:5000/v2.0"; % OPENSTACK_HOST
OPENSTACK_KEYSTONE_DEFAULT_ROLE = "Member"
OPENSTACK_KEYSTONE_BACKEND = {
'name': 'native',
'can_edit_user': True
}
API_RESULT_LIMIT = 1000
LOGGING = {
'version': 1,
# When set to True this will disable all logging except
# for loggers specified in this configuration dictionary. Note that
# if nothing is specified here and disable_existing_loggers is True,
# django.db.backends will still log unless it is disabled explicitly.
'disable_existing_loggers': False,
'handlers': {
'null': {
'level': 'DEBUG',
'class': 'django.utils.log.NullHandler',
},
'console': {
# Set the level to "DEBUG" for verbose output logging.
'level': 'INFO',
'class': 'logging.StreamHandler',
},
},
'loggers': {
# Logging from django.db.backends is VERY verbose, send to null
# by default.
'django.db.backends': {
'handlers': ['null'],
'propagate': False,
},
'horizon': {
'handlers': ['console'],
'propagate': False,
},
'novaclient': {
'handlers': ['console'],
'propagate': False,
},
'keystoneclient': {
'handlers': ['console'],
'propagate': False,
Bug#674448: CVE-2012-2098
Package: libcommons-compress-java Version: 1.2-1 Severity: grave Tags: security Please see https://commons.apache.org/compress/security.html Fixed in 1.4.1. This doesn't warrant a DSA, but you could fix it through a point update for Squeeze 6.0.6. Cheers, Moritz -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#674447: CVE-2012-2391
Package: haproxy Severity: grave Tags: security Please see here for details and a patch: https://secunia.com/advisories/49261/ http://haproxy.1wt.eu/download/1.4/src/CHANGELOG http://haproxy.1wt.eu/git?p=haproxy-1.4.git;a=commit;h=30297cb17147a8d339eb160226bcc08c91d9530b Can you please check, whether stable is affected? Cheers, Moritz -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Processed: Re: Bug#674358: gmsh: FTBFS: array.hpp:374:7: error: 'SetSize' was not declared in this scope, and no declarations were found by argument-dependent lookup at the point of instantiation [-fp
Processing commands for cont...@bugs.debian.org: > tags 674358 fixed-upstream Bug #674358 [src:gmsh] gmsh: FTBFS: array.hpp:374:7: error: 'SetSize' was not declared in this scope, and no declarations were found by argument-dependent lookup at the point of instantiation [-fpermissive] Added tag(s) fixed-upstream. > thanks Stopping processing here. Please contact me if you need assistance. -- 674358: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=674358 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: cryptmount: diff for NMU version 4.3-1.1
Processing commands for cont...@bugs.debian.org: > tags 672678 + pending Bug #672678 [cryptmount] cryptmount: unmet dependency on libdevmapper Added tag(s) pending. > thanks Stopping processing here. Please contact me if you need assistance. -- 672678: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=672678 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#674358: gmsh: FTBFS: array.hpp:374:7: error: 'SetSize' was not declared in this scope, and no declarations were found by argument-dependent lookup at the point of instantiation [-fpermissive]
tags 674358 fixed-upstream thanks Thanks, Christophe, for the very quick fix. I will upload a new version from svn. Anton -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#672678: cryptmount: diff for NMU version 4.3-1.1
tags 672678 + pending
thanks
Dear maintainer,
I've prepared an NMU for cryptmount (versioned as 4.3-1.1) and
uploaded it to DELAYED/2. Please feel free to tell me if I
should delay it longer.
Regards.
Don Armstrong
--
LEADERSHIP -- A form of self-preservation exhibited by people with
autodestructive imaginations in order to ensure that when it comes to
the crunch it'll be someone else's bones which go crack and not their
own.
-- The HipCrime Vocab by Chad C. Mulligan
(John Brunner _Stand On Zanzibar_ p256-7)
http://www.donarmstrong.com http://rzlab.ucr.edu
diff -Nru cryptmount-4.3/debian/changelog cryptmount-4.3/debian/changelog
--- cryptmount-4.3/debian/changelog 2012-03-17 11:53:15.0 -0700
+++ cryptmount-4.3/debian/changelog 2012-05-23 15:24:20.0 -0700
@@ -1,3 +1,11 @@
+cryptmount (4.3-1.1) unstable; urgency=low
+
+ * Non-Maintainer upload
+ * Remove unnecessary dependency on libdevmapper which is no longer
+provided by libdevmapper1.02.1. (Closes: #672678)
+
+ -- Don Armstrong Wed, 23 May 2012 15:16:45 -0700
+
cryptmount (4.3-1) unstable; urgency=low
* Closes: bug#641476 (Setting owner permissions on mounting vfat partitions)
diff -Nru cryptmount-4.3/debian/control cryptmount-4.3/debian/control
--- cryptmount-4.3/debian/control 2012-02-23 12:23:29.0 -0800
+++ cryptmount-4.3/debian/control 2012-05-23 15:15:40.0 -0700
@@ -8,7 +8,7 @@
Package: cryptmount
Architecture: any
-Depends: ${shlibs:Depends}, ${misc:Depends}, libdevmapper
+Depends: ${shlibs:Depends}, ${misc:Depends}
Recommends: udev
Suggests: openssl, dmsetup
Description: Management of encrypted file systems
Bug#674297: marked as done (girara: FTBFS: rm: cannot remove `doc/html/installdox': No such file or directory)
Your message dated Thu, 24 May 2012 17:48:09 + with message-id and subject line Bug#674297: fixed in girara 0.1.2-3 has caused the Debian Bug report #674297, regarding girara: FTBFS: rm: cannot remove `doc/html/installdox': No such file or directory to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 674297: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=674297 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: girara Version: 0.1.2-2 Severity: serious Tags: wheezy sid User: debian...@lists.debian.org Usertags: qa-ftbfs-20120524 qa-ftbfs Justification: FTBFS on amd64 Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part: > make[2]: Entering directory `/«PKGBUILDDIR»' > doxygen Doxyfile > make[2]: Leaving directory `/«PKGBUILDDIR»' > rm doc/html/installdox doc/html/jquery.js > rm: cannot remove `doc/html/installdox': No such file or directory > make[1]: *** [override_dh_auto_build-indep] Error 1 The full build log is available from: http://people.debian.org/~lucas/logs/2012/05/24/girara_0.1.2-2_unstable.log 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. --- End Message --- --- Begin Message --- Source: girara Source-Version: 0.1.2-3 We believe that the bug you reported is fixed in the latest version of girara, which is due to be installed in the Debian FTP archive: girara_0.1.2-3.debian.tar.gz to main/g/girara/girara_0.1.2-3.debian.tar.gz girara_0.1.2-3.dsc to main/g/girara/girara_0.1.2-3.dsc libgirara-doc_0.1.2-3_all.deb to main/g/girara/libgirara-doc_0.1.2-3_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 674...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Sebastian Ramacher (supplier of updated girara 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: Thu, 24 May 2012 19:24:25 +0200 Source: girara Binary: libgirara-gtk2-0 libgirara-gtk3-0 libgirara-dbg libgirara-dev libgirara-doc Architecture: source all Version: 0.1.2-3 Distribution: unstable Urgency: low Maintainer: Sebastian Ramacher Changed-By: Sebastian Ramacher Description: libgirara-dbg - library for minimalistic user interfaces (debugging symbols) libgirara-dev - library for minimalistic user interfaces (development files) libgirara-doc - library for minimalistic user interfaces (documentation) libgirara-gtk2-0 - library for minimalistic user interfaces (shared libraries, GTK+ libgirara-gtk3-0 - library for minimalistic user interfaces (shared libraries, GTK+ Closes: 674297 Changes: girara (0.1.2-3) unstable; urgency=low . [ Sebastian Ramacher ] * debian/rules: - Call rm with -f to remove installdox since doxygen 1.8.1-1 stopped to generate it. Thanks to Lucas Nussbaum for the report. (Closes: #674297) - Call xvfb-run with -a to prevent FTBFS if there is already another xvfb instance running. . [ Jakub Wilk ] * Add DM-Upload-Allowed. Checksums-Sha1: efea75b2a883570623727ded7ada1e9fdb61e188 2075 girara_0.1.2-3.dsc 2af84f2d908aaa23d2ea0048daf16ee022b7099b 12348 girara_0.1.2-3.debian.tar.gz 877fcae2a68ec32b09189212868260ae3e2b261a 361370 libgirara-doc_0.1.2-3_all.deb Checksums-Sha256: ca76142682541912ac7e49dbf21c7127a3cf3d13bc6912d324b1310edd5e7bec 2075 girara_0.1.2-3.dsc 134b589405923b855f9d1e5790a01350a22d51e294a481110785044f46c57055 12348 girara_0.1.2-3.debian.tar.gz 01d55a04e5993f2046b914089d1a87115379c405105818e1b2f6de4b134f3fc2 361370 libgirara-doc_0.1.2-3_all.deb Files: d6c7dc83ebc68c4a64650a763dcea7c4 2075 libs optional girara_0.1.2-3.dsc 0b3864b76c57f85e091eac97a9a6effc 12348 libs optional girara_0.1.2-3.debian.tar.gz 81496905f053cf8675d710948539cb98 361370 doc optional libgirara-doc_0.1.2-3_all.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.12 (GNU/Linux) iQIcBAEBCAAGBQJPvnDzAAoJEC1Os6YBV
Processed (with 1 errors): reassign 667040 to xorg-server, forcibly merging 666468 667040
Processing commands for cont...@bugs.debian.org:
> reassign 667040 xorg-server
Bug #667040 [libcairo2] libgtk-3-0: Broken text rendering
Bug reassigned from package 'libcairo2' to 'xorg-server'.
No longer marked as found in versions cairo/1.12.0-2.
Ignoring request to alter fixed versions of bug #667040 to the same values
previously set
> forcemerge 666468 667040
Bug #666468 [xorg-server] xorg-server: major text display problems in several
apps
Bug #666538 [xorg-server] xorg-server: major text display problems in several
apps
Bug #666564 [xorg-server] xorg-server: major text display problems in several
apps
Bug #666565 [xorg-server] xorg-server: major text display problems in several
apps
Bug #95 [xorg-server] xorg-server: major text display problems in several
apps
Bug #666922 [xorg-server] xorg-server: major text display problems in several
apps
Bug #666998 [xorg-server] xorg-server: major text display problems in several
apps
Bug #667048 [xorg-server] xorg-server: major text display problems in several
apps
Bug #667073 [xorg-server] xorg-server: major text display problems in several
apps
Bug #667445 [xorg-server] xorg-server: major text display problems in several
apps
Bug #667520 [xorg-server] xorg-server: major text display problems in several
apps
Bug #667809 [xorg-server] xorg-server: major text display problems in several
apps
Bug #668182 [xorg-server] [gnome-terminal] incorrect partial redraw in mc
Bug #668343 [xorg-server] xserver-xorg-video-nouveau: Character rendering
failures on GeForce 8600M GT with dual screen
Bug #668993 [xorg-server] libgdk-pixbuf2.0-0: Font rendering corruption?
Bug #672260 [xorg-server] libxrender1:amd64: transient graphical corruption on
many windows after upgrade
Bug #667040 [xorg-server] libgtk-3-0: Broken text rendering
Set Bug forwarded-to-address to
'https://bugs.freedesktop.org/show_bug.cgi?id=47266'.
Failed to forcibly merge 666468: It is nonsensical for a bug to block itself
(or a merged partner): 667040
Debbugs::Control::set_blocks('bug', 667040, 'block', 667040, 'add', 1,
'request_msgid', '<1337880198-2546-bts-jcris...@debian.org>',
'request_replyto', ...) called at /usr/local/lib/site_perl/Debbugs/Control.pm
line 2117
Debbugs::Control::set_merged('transcript', 'GLOB(0x279fb28)',
'requester', 'Julien Cristau ', 'request_addr',
'cont...@bugs.debian.org', 'request_msgid',
'<1337880198-2546-bts-jcris...@debian.org>', 'request_subject', ...) called at
/usr/lib/debbugs/service line 887
eval {...} called at /usr/lib/debbugs/service line 886
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
666468: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=666468
666538: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=666538
666564: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=666564
666565: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=666565
95: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=95
666922: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=666922
666998: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=666998
667040: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=667040
667048: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=667048
667073: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=667073
667445: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=667445
667520: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=667520
667809: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=667809
668182: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=668182
668343: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=668343
668993: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=668993
672260: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=672260
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#673970: [Pkg-puppet-devel] Bug#673970: puppetmaster-passenger: fails to install: ERROR: Site puppetmaster does not exist!
Andreas Beckmann writes: > during a test with piuparts I noticed your package failed to install. > As per definition of the release team this makes the package too buggy > for a release, thus the severity. Found the bug. :) The apache2 version in experimental, which was installed by piuparts alongside with the puppet packages, has changed the behaviour of the utility "a2ensite" used to enable and disable apache2 virtualhosts, or "sites". It now requires files in /etc/apache2/sites-available/ to end with ".conf", but the puppetmaster virtualhost file is just called "puppetmaster". This was changed by commit http://anonscm.debian.org/gitweb/?p=pkg-apache/apache2.git;a=commit;h=8827a9b754d95e6f23eac5c07fdfc80c8f99356c, which closed the bug http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=605535 -- Stig Sandbeck Mathisen -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#666865: Unarchive: The problem still persists
micah anderson writes: > Arno Töll writes: >> Hello, >> >> reopening the bug as the problem still persists. > > Do you have a way of testing this? I've set up something that I believe > should let the messages through based on the X-Loop header, but need to > test that it is working. There was a mistake in what was done, but that has been fixed now. micah -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Processed: unmerging 667040, notfound 658252 in 1.12.0-2, notfound 667040 in 1.10.2-6.2 ...
Processing commands for cont...@bugs.debian.org: > # yay for merging unrelated bugs > unmerge 667040 Bug #667040 [libcairo2] libgtk-3-0: Broken text rendering Bug #658252 [libcairo2] libcairo2: Text quickly becomes rectangles Disconnected #667040 from all other report(s). > notfound 658252 1.12.0-2 Bug #658252 [libcairo2] libcairo2: Text quickly becomes rectangles No longer marked as found in versions cairo/1.12.0-2. > notfound 667040 1.10.2-6.2 Bug #667040 [libcairo2] libgtk-3-0: Broken text rendering No longer marked as found in versions cairo/1.10.2-6.2. > found 667040 1.12.0-2 Bug #667040 [libcairo2] libgtk-3-0: Broken text rendering Marked as found in versions cairo/1.12.0-2. > unblock 658252 with 666565 666564 667445 668993 666538 667809 666998 666922 > 668343 666468 95 667520 667048 668190 672260 667073 669629 668172 668182 Bug #658252 [libcairo2] libcairo2: Text quickly becomes rectangles 658252 was blocked by: 666565 666564 667445 668993 666538 667809 666998 666922 668343 666468 95 667520 667048 668190 672260 667073 669629 668172 668182 658252 was not blocking any bugs. Removed blocking bug(s) of 658252: 666565, 666564, 667445, 666538, 668993, 667809, 666998, 666922, 668343, 666468, 95, 667520, 668190, 667048, 667073, 672260, 669629, 668172, and 668182 > thanks Stopping processing here. Please contact me if you need assistance. -- 658252: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=658252 667040: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=667040 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#674438: liblhasa-dev: please depend on liblhasa0
On Thu, May 24, 2012 at 12:05:31PM -0400, Aaron M. Ucko wrote: > Please correct liblhasa-dev to depend on liblhasa0 to keep liblhasa.so > from potentially dangling. > > Thanks! Oops! Thanks for pointing this out. I've just uploaded a fix. -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Processed: tagging 671948
Processing commands for cont...@bugs.debian.org: > tags 671948 + pending Bug #671948 [src:atlas-cpp] atlas-cpp: FTBFS: symbols errors Added tag(s) pending. > thanks Stopping processing here. Please contact me if you need assistance. -- 671948: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=671948 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#674438: marked as done (liblhasa-dev: please depend on liblhasa0)
Your message dated Thu, 24 May 2012 16:34:11 + with message-id and subject line Bug#674438: fixed in lhasa 0.0.6-2 has caused the Debian Bug report #674438, regarding liblhasa-dev: please depend on liblhasa0 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.) -- 674438: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=674438 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: liblhasa-dev Version: 0.0.6-1 Severity: serious Justification: Policy 8.4 Please correct liblhasa-dev to depend on liblhasa0 to keep liblhasa.so from potentially dangling. Thanks! -- System Information: Debian Release: wheezy/sid APT prefers testing APT policy: (500, 'testing'), (500, 'stable'), (300, 'unstable') Architecture: amd64 (x86_64) Kernel: Linux 3.2.0-2-amd64 (SMP w/4 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash -- no debconf information --- End Message --- --- Begin Message --- Source: lhasa Source-Version: 0.0.6-2 We believe that the bug you reported is fixed in the latest version of lhasa, which is due to be installed in the Debian FTP archive: lhasa_0.0.6-2.diff.gz to main/l/lhasa/lhasa_0.0.6-2.diff.gz lhasa_0.0.6-2.dsc to main/l/lhasa/lhasa_0.0.6-2.dsc lhasa_0.0.6-2_amd64.deb to main/l/lhasa/lhasa_0.0.6-2_amd64.deb liblhasa-dev_0.0.6-2_amd64.deb to main/l/lhasa/liblhasa-dev_0.0.6-2_amd64.deb liblhasa0_0.0.6-2_amd64.deb to main/l/lhasa/liblhasa0_0.0.6-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 674...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Jon Dowland (supplier of updated lhasa 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: Thu, 24 May 2012 17:14:47 +0100 Source: lhasa Binary: lhasa liblhasa-dev liblhasa0 Architecture: source amd64 Version: 0.0.6-2 Distribution: unstable Urgency: low Maintainer: Jon Dowland Changed-By: Jon Dowland Description: lhasa - lzh archive decompressor liblhasa-dev - lzh decompression library - development files liblhasa0 - lzh archive decompression library Closes: 674438 Changes: lhasa (0.0.6-2) unstable; urgency=low . * correct liblhasa-dev to depend on liblhasa0. Thanks Aaron M. Ucko. Closes: #674438. Checksums-Sha1: 41a839d7c83c7a36c8cc1aa91ebae3f612ab7ff8 1931 lhasa_0.0.6-2.dsc df90234f5ebd5a17a1643220407edde6584605f4 2193 lhasa_0.0.6-2.diff.gz 60cc1c1ccd743a106bb2f7cac487d781e9b062ba 13446 lhasa_0.0.6-2_amd64.deb 2b9c4ec74b0932682b4de1d33407fe7f021dc80c 27616 liblhasa-dev_0.0.6-2_amd64.deb 34a6108357470b457b59e48dc25e3a98a923adc6 21312 liblhasa0_0.0.6-2_amd64.deb Checksums-Sha256: f3673a544a43d8c4cbd1112e811f1a93d408ebf42b8872b6286b61692e5dd60a 1931 lhasa_0.0.6-2.dsc e4a160032b7e68327b8fccd8632a246fc8da4824af1a6f50f450cdbf9a67f1d2 2193 lhasa_0.0.6-2.diff.gz 268d4c270cc6a29eddbbebc6093d7cf32a0a297d0c69fb34f9edc2496d4d9d99 13446 lhasa_0.0.6-2_amd64.deb 8193e93267d408e2951d75f7aed9e7ca0eff87efd0546b5485235c402321ddcc 27616 liblhasa-dev_0.0.6-2_amd64.deb e18171071414446b2bba7d00250ca236835eec2baf230c1ddfa750e58d0959f7 21312 liblhasa0_0.0.6-2_amd64.deb Files: e8ec288fda887969d7c43c816f61ed5b 1931 utils optional lhasa_0.0.6-2.dsc 4032c9a08afeb189cf08332dd6f933d0 2193 utils optional lhasa_0.0.6-2.diff.gz a32d730a9dfda1950e245d01c4bf959d 13446 utils optional lhasa_0.0.6-2_amd64.deb afb8fd8cb50b0555f0571a86e449b904 27616 libdevel optional liblhasa-dev_0.0.6-2_amd64.deb ec141109a6c1bd823e6ac175122ca566 21312 libs optional liblhasa0_0.0.6-2_amd64.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.12 (GNU/Linux) iQIcBAEBCAAGBQJPvmEHAAoJEAkHQJYGMWAP+wWe5oljXC1AuKXN6DklJpWB j3ZdxVASLHSqBOoCqswadwuns3KRbDeyWhBVQsNe90+WFov0i4Ri85Mwew7mUL5G tGVaj1S/ySBrKzoEuC3nn9fwnnO3vkqW4u1cHQlmr3z/sdqD7GG9cRrdyQ9aU2oh sbfv4n4PoioTpepqTCvdovan3urNvJVQ9yH/Msvny4HBcwoiEl+abf4EgyqhXqa4 5ADN1wA2ZsdFArtDV2Gczt48dHyRoIMr4A0DOe1avleM3SMLg2AGdC/W18b3uJ+C /fyFi8tkWrQqjT2LCnQmXF0LKwf2aOq3mP39bY4C/kLVLbyZzGIapbR0b5uacXZ7 iQr/V8Va3+fsWQA7HGQ6RHWeVRQNANrPCcNAoODMxs7dgoexA34mIa7bx+MggrAr wMkRQilyCmSjhYFEdKXCgVSsRL/qGaxkl7QPAyDfnEXGkvZLdJEat9TtTZHug/H9 45pCFsejFm/0rTBPaD8XUF2FLpGa8haJKbrJ6cl+JfRe2ZZZH9uEe+3mk3i+3VPN
Processed: Re: Bug#674042: python-django-pipeline: breaks python-pipeline
Processing commands for cont...@bugs.debian.org: > tag #674042 + confirmed Bug #674042 [python-django-pipeline] python-django-pipeline: breaks python-pipeline Added tag(s) confirmed. > thanks Stopping processing here. Please contact me if you need assistance. -- 674042: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=674042 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#674042: python-django-pipeline: breaks python-pipeline
tag #674042 + confirmed thanks On Tue, May 22, 2012 at 07:42:32PM +0200, Jakub Wilk wrote: > Package: python-django-pipeline > Version: 1.2.2.1-1 > Severity: grave > > If you install python-pipeline and python-django-pipeline together, > the former stops working completely. > > (I did point this out in my review, but you apparently didn't care. > Thanks for wasting my time!) > Hi, First of all, sorry. I really was not going to waste your time. Also your review was pretty helpful and once package was reviewed by uploader, there were no more issues... Upload happens so quickly... I've second time tried to ping upstream dev and hoping that this will be solved without any debian-specific changes. Otherwise I'll try to find the best possible solution for this. Sorry again and thanks a lot for your help with reviewing of this package. -- WBR, Dmitry signature.asc Description: Digital signature
Bug#666865: Unarchive: The problem still persists
Arno Töll writes: > Hello, > > reopening the bug as the problem still persists. Do you have a way of testing this? I've set up something that I believe should let the messages through based on the X-Loop header, but need to test that it is working. micah -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#660471: marked as done (FTBFS on mipsel: 'UTMPX_FILE' undeclared here)
Your message dated Thu, 24 May 2012 18:05:19 +0200 with message-id <87ehq9zhs0@x4.delysid.org> and subject line Fixed in 1.8-6 has caused the Debian Bug report #660471, regarding FTBFS on mipsel: 'UTMPX_FILE' undeclared here 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.) -- 660471: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=660471 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: screader Version: 1.8-5.2 Severity: serious Justification: fails to build from source screader fails to build from source on mipsel, but built in the past: utmp.c:71:26: error: 'UTMPX_FILE' undeclared here (not in a function) utmp.c: In function 'RemoveLoginSlot': utmp.c:284:12: error: 'struct __exit_status' has no member named 'e_termination' utmp.c:284:3: warning: statement with no effect [-Wunused-value] utmp.c:285:12: error: 'struct __exit_status' has no member named 'e_exit' utmp.c:285:3: warning: statement with no effect [-Wunused-value] https://buildd.debian.org/status/fetch.php?pkg=screader&arch=mipsel&ver=1.8-5.2&stamp=1326297827 --- End Message --- --- Begin Message --- Hi. This bug has been fixed with 1.8-6, however, that version had another issue, so since 1.8-7 there is a version of screader for mispel again. -- CYa, ⡍⠁⠗⠊⠕ | Debian Developer http://debian.org/> .''`. | Get my public key via finger mlang/k...@db.debian.org : :' : | 1024D/7FC1A0854909BCCDBE6C102DDFFC022A6B113E44 `. `' `- http://delysid.org/> http://www.staff.tugraz.at/mlang/> --- End Message ---
Bug#674438: liblhasa-dev: please depend on liblhasa0
Package: liblhasa-dev Version: 0.0.6-1 Severity: serious Justification: Policy 8.4 Please correct liblhasa-dev to depend on liblhasa0 to keep liblhasa.so from potentially dangling. Thanks! -- System Information: Debian Release: wheezy/sid APT prefers testing APT policy: (500, 'testing'), (500, 'stable'), (300, 'unstable') Architecture: amd64 (x86_64) Kernel: Linux 3.2.0-2-amd64 (SMP w/4 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash -- 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#674301: marked as done (libplack-middleware-reverseproxy-perl: FTBFS: tests failed)
Your message dated Thu, 24 May 2012 16:03:19 + with message-id and subject line Bug#674301: fixed in libplack-middleware-reverseproxy-perl 0.13-1 has caused the Debian Bug report #674301, regarding libplack-middleware-reverseproxy-perl: FTBFS: tests failed 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.) -- 674301: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=674301 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: libplack-middleware-reverseproxy-perl Version: 0.11-1 Severity: serious Tags: wheezy sid User: debian...@lists.debian.org Usertags: qa-ftbfs-20120524 qa-ftbfs Justification: FTBFS on amd64 Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part: > make[1]: Entering directory `/«PKGBUILDDIR»' > PERL_DL_NONLAZY=1 /usr/bin/perl "-MExtUtils::Command::MM" "-e" > "test_harness(0, 'inc', 'blib/lib', 'blib/arch')" t/*.t > t/00_compile.t ok > > # Failed test 'with https of uri' > # at t/reverseproxy.t line 33. > # got: 'https://example.com/?foo=bar' > # expected: 'https://example.com:80/?foo=bar' > > # Failed test 'with https of base' > # at t/reverseproxy.t line 33. > # got: 'https://example.com/' > # expected: 'https://example.com:80/' > > # Failed test 'https with HTTP_X_FORWARDED_PROTO of uri' > # at t/reverseproxy.t line 33. > # got: 'https://example.com/?foo=bar' > # expected: 'https://example.com:80/?foo=bar' > > # Failed test 'https with HTTP_X_FORWARDED_PROTO of base' > # at t/reverseproxy.t line 33. > # got: 'https://example.com/' > # expected: 'https://example.com:80/' > # Looks like you failed 4 tests of 39. > t/reverseproxy.t .. > Dubious, test returned 4 (wstat 1024, 0x400) > Failed 1/2 test programs. 4/40 subtests failed. > Failed 4/39 subtests > > Test Summary Report > --- > t/reverseproxy.t (Wstat: 1024 Tests: 39 Failed: 4) > Failed tests: 2-3, 9-10 > Non-zero exit status: 4 > Files=2, Tests=40, 0 wallclock secs ( 0.01 usr 0.04 sys + 0.28 cusr 0.02 > csys = 0.35 CPU) > Result: FAIL > make[1]: *** [test_dynamic] Error 4 The full build log is available from: http://people.debian.org/~lucas/logs/2012/05/24/libplack-middleware-reverseproxy-perl_0.11-1_unstable.log 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. --- End Message --- --- Begin Message --- Source: libplack-middleware-reverseproxy-perl Source-Version: 0.13-1 We believe that the bug you reported is fixed in the latest version of libplack-middleware-reverseproxy-perl, which is due to be installed in the Debian FTP archive: libplack-middleware-reverseproxy-perl_0.13-1.debian.tar.gz to main/libp/libplack-middleware-reverseproxy-perl/libplack-middleware-reverseproxy-perl_0.13-1.debian.tar.gz libplack-middleware-reverseproxy-perl_0.13-1.dsc to main/libp/libplack-middleware-reverseproxy-perl/libplack-middleware-reverseproxy-perl_0.13-1.dsc libplack-middleware-reverseproxy-perl_0.13-1_all.deb to main/libp/libplack-middleware-reverseproxy-perl/libplack-middleware-reverseproxy-perl_0.13-1_all.deb libplack-middleware-reverseproxy-perl_0.13.orig.tar.gz to main/libp/libplack-middleware-reverseproxy-perl/libplack-middleware-reverseproxy-perl_0.13.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 674...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. gregor herrmann (supplier of updated libplack-middleware-reverseproxy-perl 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: Thu, 24 May 2012 17:49:58 +0200 Source: libplac
Processed: bug 674301 is forwarded to https://rt.cpan.org/Public/Bug/Display.html?id=77158, tagging 674301
Processing commands for cont...@bugs.debian.org: > forwarded 674301 https://rt.cpan.org/Public/Bug/Display.html?id=77158 Bug #674301 [src:libplack-middleware-reverseproxy-perl] libplack-middleware-reverseproxy-perl: FTBFS: tests failed Set Bug forwarded-to-address to 'https://rt.cpan.org/Public/Bug/Display.html?id=77158'. > # in 0.12 apparently > tags 674301 + confirmed upstream fixed-upstream Bug #674301 [src:libplack-middleware-reverseproxy-perl] libplack-middleware-reverseproxy-perl: FTBFS: tests failed Added tag(s) upstream, confirmed, and fixed-upstream. > thanks Stopping processing here. Please contact me if you need assistance. -- 674301: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=674301 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#674433: Acknowledgement (No longer builds on non-Linux)
Btw, I generally support the idea of adding systemd support, especially shipping .service files. As for session tracking via systemd-logind: We do have several components in the GNOME stack which currently depend on ConsoleKit for session tracking but can be built with systemd-logind support. Not all of them support a runtime fallback, i.e. if you enable systemd support, ConsoleKit support will be disabled. That's why we decided to stay with ConsoleKit session tracking for wheezy for all our packages within the GNOME team, as systemd-logind requires systemd to PID 1, and we didn't want to enforce such a change short before the wheezy freeze :-) We will re-evaluate this decission once wheezy+1 is open for development. Btw, I'm running systemd myself and never experienced the crash in libaccountsservice so far. I'm wondering if #673185 affects people not running systemd? Michael -- Why is it that all of the instruments seeking intelligent life in the universe are pointed away from Earth? signature.asc Description: OpenPGP digital signature
Bug#674385: libcpan-mini-perl: FTBFS: tests failed
On Thu, 24 May 2012 11:48:16 +0200, Lucas Nussbaum wrote:
> > couldn't determine your home directory! set HOME env variable at
> > /«PKGBUILDDIR»/blib/lib/CPAN/Mini/App.pm line 90
> > # Child (defaults) exited without calling finalize()
> >
> > # Failed test 'defaults'
> > # at /usr/share/perl/5.14/Test/Builder.pm line 252.
> > # Tests were run but no plan was declared and done_testing() was not seen.
> > t/app.t .
Grmpf.
I thought I had fixed this in #38 / 1.111008-2.
But it seems $ENV{HOME} gets reset in the test.
At the moment I don't really understand the details ... :/
Cheers,
gregor
--
.''`. Homepage: http://info.comodo.priv.at/ - OpenPGP key 0xBB3A68018649AA06
: :' : Debian GNU/Linux user, admin, and developer - http://www.debian.org/
`. `' Member of VIBE!AT & SPI, fellow of the Free Software Foundation Europe
`- NP: Tori Amos: Cornflake Girl
signature.asc
Description: Digital signature
Processed: Re: Bug#674105: lxappearance-obconf: please version alternative B-D on lxappearance
Processing commands for cont...@bugs.debian.org: > retitle 674105 lxappearance-obconf: please update lxappearance(-dev) B-D Bug #674105 [src:lxappearance-obconf] lxappearance-obconf: please version alternative B-D on lxappearance Changed Bug title to 'lxappearance-obconf: please update lxappearance(-dev) B-D' from 'lxappearance-obconf: please version alternative B-D on lxappearance' > thanks Stopping processing here. Please contact me if you need assistance. -- 674105: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=674105 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#674105: lxappearance-obconf: please version alternative B-D on lxappearance
retitle 674105 lxappearance-obconf: please update lxappearance(-dev) B-D thanks "Aaron M. Ucko" writes: > Build-Depends: ... lxappearance-dev | lxappearance (>= 0.5.1-3~), ... > > (assuming the next upload will feature the merge). As Samuel Thibault pointed out in #674103, the merge already occurred in 0.5.2-1, which I'd overlooked because I mostly take packages from testing. As such, and given that lxappearance neglects to provide lxappearance-dev, please also go ahead and switch the alternatives' order: Build-Depends: ... lxappearance (>= 0.5.2) | lxappearance-dev, ... Thanks! -- Aaron M. Ucko, KB1CJC (amu at alum.mit.edu, ucko at debian.org) http://www.mit.edu/~amu/ | http://stuff.mit.edu/cgi/finger/?a...@monk.mit.edu -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#674364: marked as done (php-xml-serializer: FTBFS: test failed)
Your message dated Thu, 24 May 2012 15:18:31 +
with message-id
and subject line Bug#674364: fixed in php-xml-serializer 0.20.2-2
has caused the Debian Bug report #674364,
regarding php-xml-serializer: FTBFS: test failed
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.)
--
674364: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=674364
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: php-xml-serializer
Version: 0.20.2-1
Severity: serious
Tags: wheezy sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20120524 qa-ftbfs
Justification: FTBFS on amd64
Hi,
During a rebuild of all packages in sid, your package failed to build on
amd64.
Relevant part:
> make[1]: Entering directory `/«PKGBUILDDIR»'
> dh_link -O--buildsystem=phppear
> chmod +x ./debian/tests_run
> ./debian/tests_run
> PHP Warning: require_once(XML/Parser.php): failed to open stream: No such
> file or directory in
> /«PKGBUILDDIR»/XML_Serializer-0.20.2/XML/Unserializer.php on line 58
> PHP Stack trace:
> PHP 1. {main}() /usr/bin/phpunit:0
> PHP 2. PHPUnit_TextUI_Command::main() /usr/bin/phpunit:46
> PHP 3. PHPUnit_TextUI_Command->run()
> /usr/share/php/PHPUnit/TextUI/Command.php:130
> PHP 4. PHPUnit_Runner_BaseTestRunner->getTest()
> /usr/share/php/PHPUnit/TextUI/Command.php:150
> PHP 5. PHPUnit_Runner_BaseTestRunner->loadSuiteClass()
> /usr/share/php/PHPUnit/Runner/BaseTestRunner.php:104
> PHP 6. PHPUnit_Runner_StandardTestSuiteLoader->load()
> /usr/share/php/PHPUnit/Runner/BaseTestRunner.php:168
> PHP 7. PHPUnit_Util_Fileloader::checkAndLoad()
> /usr/share/php/PHPUnit/Runner/StandardTestSuiteLoader.php:78
> PHP 8. PHPUnit_Util_Fileloader::load()
> /usr/share/php/PHPUnit/Util/Fileloader.php:79
> PHP 9. include_once() /usr/share/php/PHPUnit/Util/Fileloader.php:95
> PHP 10. require_once()
> /«PKGBUILDDIR»/XML_Serializer-0.20.2/tests/AllTests.php:76
> PHP 11. require_once()
> /«PKGBUILDDIR»/XML_Serializer-0.20.2/tests/Unserializer_Arrays_TestCase.php:23
> PHP Fatal error: require_once(): Failed opening required 'XML/Parser.php'
> (include_path='.:/usr/share/php:/«PKGBUILDDIR»/XML_Serializer-0.20.2') in
> /«PKGBUILDDIR»/XML_Serializer-0.20.2/XML/Unserializer.php on line 58
> PHP Stack trace:
> PHP 1. {main}() /usr/bin/phpunit:0
> PHP 2. PHPUnit_TextUI_Command::main() /usr/bin/phpunit:46
> PHP 3. PHPUnit_TextUI_Command->run()
> /usr/share/php/PHPUnit/TextUI/Command.php:130
> PHP 4. PHPUnit_Runner_BaseTestRunner->getTest()
> /usr/share/php/PHPUnit/TextUI/Command.php:150
> PHP 5. PHPUnit_Runner_BaseTestRunner->loadSuiteClass()
> /usr/share/php/PHPUnit/Runner/BaseTestRunner.php:104
> PHP 6. PHPUnit_Runner_StandardTestSuiteLoader->load()
> /usr/share/php/PHPUnit/Runner/BaseTestRunner.php:168
> PHP 7. PHPUnit_Util_Fileloader::checkAndLoad()
> /usr/share/php/PHPUnit/Runner/StandardTestSuiteLoader.php:78
> PHP 8. PHPUnit_Util_Fileloader::load()
> /usr/share/php/PHPUnit/Util/Fileloader.php:79
> PHP 9. include_once() /usr/share/php/PHPUnit/Util/Fileloader.php:95
> PHP 10. require_once()
> /«PKGBUILDDIR»/XML_Serializer-0.20.2/tests/AllTests.php:76
> PHP 11. require_once()
> /«PKGBUILDDIR»/XML_Serializer-0.20.2/tests/Unserializer_Arrays_TestCase.php:23
> make[1]: *** [override_dh_link] Error 255
The full build log is available from:
http://people.debian.org/~lucas/logs/2012/05/24/php-xml-serializer_0.20.2-1_unstable.log
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.
--- End Message ---
--- Begin Message ---
Source: php-xml-serializer
Source-Version: 0.20.2-2
We believe that the bug you reported is fixed in the latest version of
php-xml-serializer, which is due to be installed in the Debian FTP archive:
php-xml-serializer_0.20.2-2.debian.tar.gz
to main/p/php-xml-serializer/php-xml-serializer_0.20.2-2.debian.tar.gz
php-xml-serializer_0.20.2-2.dsc
to main/p/php-xml-serializer/php-xml-serializer_0.20.2-2.dsc
php-xml-serializer_0.20.2-2_all.deb
to main/p/php-xml-serializer/php-xml-serializer_0.20.2-2_all.deb
A summary of the changes between this version and the previous on
Bug#674433: No longer builds on non-Linux
Source: accountsservice Version: 0.6.21-1 Severity: serious Hi, systemd is only available on Linux. This means the build dependency on libsystemd-login-dev and libsystemd-daemon-dev can't be fulfilled on non-Linux systems. You should either mark those as [linux-any] or consider disabling systemd support seeing that systemd is not (yet) the default init system on Debian. I assume that enabling systemd support (which seems to be used for session tracking) has a working runtime fallback to ConsoleKit if systemd is not found running? Michael -- System Information: Debian Release: wheezy/sid APT prefers unstable APT policy: (500, 'unstable'), (200, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 3.2.0-2-amd64 (SMP w/4 CPU cores) Locale: LANG=de_DE.utf8, LC_CTYPE=de_DE.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash -- 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#674372: marked as done (php-xml-rss: FTBFS: test failed)
Your message dated Thu, 24 May 2012 15:04:25 +
with message-id
and subject line Bug#674372: fixed in php-xml-rss 1.0.2-3
has caused the Debian Bug report #674372,
regarding php-xml-rss: FTBFS: test failed
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.)
--
674372: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=674372
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: php-xml-rss
Version: 1.0.2-2
Severity: serious
Tags: wheezy sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20120524 qa-ftbfs
Justification: FTBFS on amd64
Hi,
During a rebuild of all packages in sid, your package failed to build on
amd64.
Relevant part:
> make[1]: Entering directory `/«PKGBUILDDIR»'
> dh_link -O--buildsystem=phppear
> chmod +x ./debian/tests_run
> ./debian/tests_run XML_RSS-1.0.2
> PHP Warning: require_once(XML/Parser.php): failed to open stream: No such
> file or directory in /«PKGBUILDDIR»/XML_RSS-1.0.2/XML/RSS.php on line 17
> PHP Stack trace:
> PHP 1. {main}() /usr/bin/phpunit:0
> PHP 2. PHPUnit_TextUI_Command::main() /usr/bin/phpunit:46
> PHP 3. PHPUnit_TextUI_Command->run()
> /usr/share/php/PHPUnit/TextUI/Command.php:130
> PHP 4. PHPUnit_Runner_BaseTestRunner->getTest()
> /usr/share/php/PHPUnit/TextUI/Command.php:150
> PHP 5. PHPUnit_Runner_BaseTestRunner->loadSuiteClass()
> /usr/share/php/PHPUnit/Runner/BaseTestRunner.php:104
> PHP 6. PHPUnit_Runner_StandardTestSuiteLoader->load()
> /usr/share/php/PHPUnit/Runner/BaseTestRunner.php:168
> PHP 7. PHPUnit_Util_Fileloader::checkAndLoad()
> /usr/share/php/PHPUnit/Runner/StandardTestSuiteLoader.php:78
> PHP 8. PHPUnit_Util_Fileloader::load()
> /usr/share/php/PHPUnit/Util/Fileloader.php:79
> PHP 9. include_once() /usr/share/php/PHPUnit/Util/Fileloader.php:95
> PHP 10. require_once() /«PKGBUILDDIR»/XML_RSS-1.0.2/tests/AllTests.php:9
> PHP 11. require_once()
> /«PKGBUILDDIR»/XML_RSS-1.0.2/tests/XML_RSS_Infrastructure_Test.php:22
> PHP Fatal error: require_once(): Failed opening required 'XML/Parser.php'
> (include_path='.:/usr/share/php:/«PKGBUILDDIR»/XML_RSS-1.0.2') in
> /«PKGBUILDDIR»/XML_RSS-1.0.2/XML/RSS.php on line 17
> PHP Stack trace:
> PHP 1. {main}() /usr/bin/phpunit:0
> PHP 2. PHPUnit_TextUI_Command::main() /usr/bin/phpunit:46
> PHP 3. PHPUnit_TextUI_Command->run()
> /usr/share/php/PHPUnit/TextUI/Command.php:130
> PHP 4. PHPUnit_Runner_BaseTestRunner->getTest()
> /usr/share/php/PHPUnit/TextUI/Command.php:150
> PHP 5. PHPUnit_Runner_BaseTestRunner->loadSuiteClass()
> /usr/share/php/PHPUnit/Runner/BaseTestRunner.php:104
> PHP 6. PHPUnit_Runner_StandardTestSuiteLoader->load()
> /usr/share/php/PHPUnit/Runner/BaseTestRunner.php:168
> PHP 7. PHPUnit_Util_Fileloader::checkAndLoad()
> /usr/share/php/PHPUnit/Runner/StandardTestSuiteLoader.php:78
> PHP 8. PHPUnit_Util_Fileloader::load()
> /usr/share/php/PHPUnit/Util/Fileloader.php:79
> PHP 9. include_once() /usr/share/php/PHPUnit/Util/Fileloader.php:95
> PHP 10. require_once() /«PKGBUILDDIR»/XML_RSS-1.0.2/tests/AllTests.php:9
> PHP 11. require_once()
> /«PKGBUILDDIR»/XML_RSS-1.0.2/tests/XML_RSS_Infrastructure_Test.php:22
> make[1]: *** [override_dh_link] Error 255
The full build log is available from:
http://people.debian.org/~lucas/logs/2012/05/24/php-xml-rss_1.0.2-2_unstable.log
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.
--- End Message ---
--- Begin Message ---
Source: php-xml-rss
Source-Version: 1.0.2-3
We believe that the bug you reported is fixed in the latest version of
php-xml-rss, which is due to be installed in the Debian FTP archive:
php-xml-rss_1.0.2-3.debian.tar.gz
to main/p/php-xml-rss/php-xml-rss_1.0.2-3.debian.tar.gz
php-xml-rss_1.0.2-3.dsc
to main/p/php-xml-rss/php-xml-rss_1.0.2-3.dsc
php-xml-rss_1.0.2-3_all.deb
to main/p/php-xml-rss/php-xml-rss_1.0.2-3_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 674...@bugs.debian.org,
and the maintainer will reopen the bug repo
Bug#672986: marked as done (gnustep-gui-runtime: Multiple libobjc.so version linked due to mix of dependencies)
Your message dated Thu, 24 May 2012 15:02:13 +
with message-id
and subject line Bug#672986: fixed in gnustep-gui 0.22.0-1
has caused the Debian Bug report #672986,
regarding gnustep-gui-runtime: Multiple libobjc.so version linked due to mix of
dependencies
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.)
--
672986: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=672986
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: gnustep-gui-runtime
Version: 0.20.0-3
Severity: grave
Justification: renders package unusable
Dear Maintainer,
gnustep-base, gnustep-gui and gnustep-back depend on different version
of libobjc (libobjc.so.3 and libobjc.so.4 of gcc 4.6 and gcc 4.7
respectively).
Since several GNUstep applications do crash, I suppose all recently
compiled applications (self-compiled ones but also Gorm, which got
recently updated and for which a separate bug is pending).
checking with ldd, if libobjc.so.3 comes before .so.4 ("old app") the
app will work, if .so.4 comes before, the applicationwill crash.
I think it is not a good idea that gnustep-core packages
(base,gui,back) depend on different libobjc runtimes.
I have installed:
gnustep-back0.20-cairo 0.20.1-2+b1
libgnustep-base1.22 1.22.1-2+b1
libgnustep-gui0.20 0.20.0-3
it appears that only "gui" was updated to newer libobjc.
This makes gnustep unusable for any "new" package and for any
self-compiled apps for development.
A ldd output of a working application:
linux-gate.so.1 => (0xb76fe000)
libGNUMail.so.1 => /usr/lib/gnumail.app/libGNUMail.so.1 (0xb75b4000)
libgnustep-gui.so.0.20 => /usr/lib/libgnustep-gui.so.0.20 (0xb7153000)
libgnustep-base.so.1.22 => /usr/lib/libgnustep-base.so.1.22 (0xb6ce7000)
libobjc.so.3 => /usr/lib/i386-linux-gnu/libobjc.so.3 (0xb6cc7000)
libc.so.6 => /lib/i386-linux-gnu/i686/cmov/libc.so.6 (0xb6b6a000)
libPantomime.so.1.2 => /usr/lib/libPantomime.so.1.2 (0xb6aca000)
libAddresses.so.0 => /usr/lib/libAddresses.so.0 (0xb6a9b000)
libAddressView.so.0 => /usr/lib/libAddressView.so.0 (0xb6a6e000)
libm.so.6 => /lib/i386-linux-gnu/i686/cmov/libm.so.6 (0xb6a48000)
libgcc_s.so.1 => /lib/i386-linux-gnu/libgcc_s.so.1 (0xb6a2b000)
libpng12.so.0 => /lib/i386-linux-gnu/libpng12.so.0 (0xb6a0)
libgif.so.4 => /usr/lib/libgif.so.4 (0xb69f7000)
libtiff.so.4 => /usr/lib/i386-linux-gnu/libtiff.so.4 (0xb6991000)
libjpeg.so.8 => /usr/lib/i386-linux-gnu/libjpeg.so.8 (0xb6958000)
libobjc.so.4 => /usr/lib/i386-linux-gnu/libobjc.so.4 (0xb694)
libpthread.so.0 => /lib/i386-linux-gnu/i686/cmov/libpthread.so.0 (0xb692
output of a broken application:
linux-gate.so.1 => (0xb777b000)
libgnustep-gui.so.0.20 => /usr/lib/libgnustep-gui.so.0.20 (0xb7318000)
libgnustep-base.so.1.22 => /usr/lib/libgnustep-base.so.1.22 (0xb6eac000)
libpthread.so.0 =>
/lib/i386-linux-gnu/i686/cmov/libpthread.so.0 (0xb6e93000)
libobjc.so.4 => /usr/lib/i386-linux-gnu/libobjc.so.4 (0xb6e7b000)
libm.so.6 => /lib/i386-linux-gnu/i686/cmov/libm.so.6 (0xb6e55000)
libgcc_s.so.1 => /lib/i386-linux-gnu/libgcc_s.so.1 (0xb6e37000)
libc.so.6 => /lib/i386-linux-gnu/i686/cmov/libc.so.6 (0xb6cda000)
libpng12.so.0 => /lib/i386-linux-gnu/libpng12.so.0 (0xb6cb)
libgif.so.4 => /usr/lib/libgif.so.4 (0xb6ca7000)
libtiff.so.4 => /usr/lib/i386-linux-gnu/libtiff.so.4 (0xb6c41000)
libjpeg.so.8 => /usr/lib/i386-linux-gnu/libjpeg.so.8 (0xb6c07000)
libobjc.so.3 => /usr/lib/i386-linux-gnu/libobjc.so.3 (0xb6be7000)
libavahi-common.so.3 =>
/usr/lib/i386-linux-gnu/libavahi-common.so.3 (0xb6bd9000)
libavahi-client.so.3 =>
/usr/lib/i386-linux-gnu/libavahi-client.so.3 (0xb6bc6000)
libgnutls.so.26 => /usr/lib/i386-linux-gnu/libgnutls.so.26 (0xb6afd000)
-- System Information:
Debian Release: wheezy/sid
APT prefers unstable
APT policy: (500, 'unstable')
Architecture: i386 (i686)
Kernel: Linux 3.2.0-2-686-pae (SMP w/1 CPU core)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Versions of packages gnustep-gui-runtime depends on:
ii gnustep-base-runtime 1.22.1-2+b1
ii gnustep-common [gnustep-fslayout-fhs] 2.6.2-2
ii gnustep-gui-common 0.20.0-3
ii libao4 1.1.0-1.1+b1
ii libaspell150.60.7~20110707-1
ii libc6
Bug#674362: marked as done (inventor: FTBFS: build-dependency not installable: libglw1-mesa-dev)
Your message dated Thu, 24 May 2012 16:58:24 +0200 with message-id <20120524145824.gb31...@crater1.logilab.fr> and subject line Re: Bug#674362: inventor: FTBFS: build-dependency not installable: libglw1-mesa-dev has caused the Debian Bug report #674362, regarding inventor: FTBFS: build-dependency not installable: libglw1-mesa-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.) -- 674362: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=674362 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: inventor Version: 2.1.5-10-16 Severity: serious Tags: wheezy sid User: debian...@lists.debian.org Usertags: qa-ftbfs-20120524 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 inventor 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-inventor-dummy : Depends: libglw1-mesa-dev but it is > not going to be installed > E: Unable to correct problems, you have held broken packages. > apt-get failed. The full build log is available from: http://people.debian.org/~lucas/logs/2012/05/24/inventor_2.1.5-10-16_unstable.log 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. --- End Message --- --- Begin Message --- On Thu, May 24, 2012 at 11:38:54 +0200, Lucas Nussbaum wrote: > Source: inventor > Version: 2.1.5-10-16 > Severity: serious > Tags: wheezy sid > User: debian...@lists.debian.org > Usertags: qa-ftbfs-20120524 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 inventor 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-inventor-dummy : Depends: libglw1-mesa-dev but it is > > not going to be installed > > E: Unable to correct problems, you have held broken packages. > > apt-get failed. > We need to reintroduce that package, not an inventor bug. Cheers, Julien --- End Message ---
Processed: Re: Bug#674419: gnome-shell: segfaults in libaccountservice
Processing commands for cont...@bugs.debian.org: > reassign 674419 libaccountsservice0 Bug #674419 [gnome-shell] gnome-shell: segfaults in libaccountservice Bug reassigned from package 'gnome-shell' to 'libaccountsservice0'. No longer marked as found in versions gnome-shell/3.4.1-1. Ignoring request to alter fixed versions of bug #674419 to the same values previously set > forcemerge 673185 674419 Bug #673185 [libaccountsservice0] gnome-shell: segfault in libaccountsservice.so.0.0.0 Bug #673211 [libaccountsservice0] gnome-shell: segfault in libaccountsservice.so.0.0.0 Bug #674419 [libaccountsservice0] gnome-shell: segfaults in libaccountservice Set Bug forwarded-to-address to 'https://bugs.freedesktop.org/show_bug.cgi?id=50112'. Severity set to 'grave' from 'important' Added indication that 674419 affects gnome-shell Marked as found in versions accountsservice/0.6.18-3. Bug #673211 [libaccountsservice0] gnome-shell: segfault in libaccountsservice.so.0.0.0 Merged 673185 673211 674419 > thanks Stopping processing here. Please contact me if you need assistance. -- 673185: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=673185 673211: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=673211 674419: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=674419 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#640538: marked as done (simgrid: FTBFS on ia64: src/xbt/graphxml.c:2368:1: internal compiler error: in dwarf2out_cfi_begin_epilogue, at dwarf2out.c:3015)
Your message dated Thu, 24 May 2012 14:53:12 + with message-id and subject line Bug#640538: fixed in simgrid 3.7-1 has caused the Debian Bug report #640538, regarding simgrid: FTBFS on ia64: src/xbt/graphxml.c:2368:1: internal compiler error: in dwarf2out_cfi_begin_epilogue, at dwarf2out.c:3015 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.) -- 640538: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=640538 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: simgrid Version: 3.6.1-1 Severity: serious Hi, simgrid FTBFS on ia64: /usr/bin/gcc -Dgras_EXPORTS -O3 -finline-functions -funroll-loops -fno-strict-aliasing -L/usr/lib/ia64-linux-gnu -I/usr/include -I/usr/include/lua5.1 -g3 -fPIC -I/build/buildd-simgrid_3.6.1-3-ia64-RuqJcU/simgrid-3.6.1 -I/build/buildd-simgrid_3.6.1-3-ia64-RuqJcU/simgrid-3.6.1/include -I/build/buildd-simgrid_3.6.1-3-ia64-RuqJcU/simgrid-3.6.1/src -I/build/buildd-simgrid_3.6.1-3-ia64-RuqJcU/simgrid-3.6.1/src/include -I/build/buildd-simgrid_3.6.1-3-ia64-RuqJcU/simgrid-3.6.1/obj-ia64-linux-gnu -I/build/buildd-simgrid_3.6.1-3-ia64-RuqJcU/simgrid-3.6.1/obj-ia64-linux-gnu/include -I/build/buildd-simgrid_3.6.1-3-ia64-RuqJcU/simgrid-3.6.1/obj-ia64-linux-gnu/src -o CMakeFiles/gras.dir/src/xbt/graphxml_parse.c.o -c /build/buildd-simgrid_3.6.1-3-ia64-RuqJcU/simgrid-3.6.1/src/xbt/graphxml_parse.c In file included from /build/buildd-simgrid_3.6.1-3-ia64-RuqJcU/simgrid-3.6.1/src/xbt/graphxml_parse.c:19:0: src/xbt/graphxml.c: In function 'xbt_graph_parse_lex': src/xbt/graphxml.c:2368:1: internal compiler error: in dwarf2out_cfi_begin_epilogue, at dwarf2out.c:3015 Please submit a full bug report, with preprocessed source if appropriate. See for instructions. ia64 porters, could you take a look? Lucas --- End Message --- --- Begin Message --- Source: simgrid Source-Version: 3.7-1 We believe that the bug you reported is fixed in the latest version of simgrid, which is due to be installed in the Debian FTP archive: simgrid_3.7-1.debian.tar.gz to main/s/simgrid/simgrid_3.7-1.debian.tar.gz simgrid_3.7-1.dsc to main/s/simgrid/simgrid_3.7-1.dsc simgrid_3.7-1_amd64.deb to main/s/simgrid/simgrid_3.7-1_amd64.deb simgrid_3.7.orig.tar.gz to main/s/simgrid/simgrid_3.7.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 640...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Lucas Nussbaum (supplier of updated simgrid package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Thu, 24 May 2012 16:08:59 +0200 Source: simgrid Binary: simgrid Architecture: source amd64 Version: 3.7-1 Distribution: unstable Urgency: low Maintainer: Lucas Nussbaum Changed-By: Lucas Nussbaum Description: simgrid- Toolkit for scalable simulation of distributed applications Closes: 640538 656102 Changes: simgrid (3.7-1) unstable; urgency=low . * New upstream release. * Bump Standards-Version to 3.9.3. No changes needed. * debian/rules: Enable the SMPI library in the package. Closes: #656102. * Build with -O2 on ia64. Closes: #640538. * Use dpkg-buildflags to generate CFLAGS and LDFLAGS. Enable hardening. Checksums-Sha1: 8e500281531ad1490592e8f3d86e0d00aba036e4 1910 simgrid_3.7-1.dsc bf6bbc0ebe61203f3fffb171d425859237debd92 10762328 simgrid_3.7.orig.tar.gz 25edd98b674638e37b3d6b64197c42f7f7f2a0ea 7195 simgrid_3.7-1.debian.tar.gz 87537bb90d7f4cf19bf8dede56db457a7025c1e7 10029916 simgrid_3.7-1_amd64.deb Checksums-Sha256: fa485d9c25c8ecefbc6d191cd978c601df22d9c7ff70788339d6daa1b141e698 1910 simgrid_3.7-1.dsc 935a481c538f4f9ba95b865f592c07741e34a460e00da015b967b6b7078eb05d 10762328 simgrid_3.7.orig.tar.gz ebd7e897beee01cbc4710bc15a5bd7d05a39d408610a59003ebcc322ebc8d67e 7195 simgrid_3.7-1.debian.tar.gz 22abf19937c28ed96f9982b7eb9c6208ff797130c8afa57093a075ff1f0f33af 10029916 simgrid_3.7-1_amd64.deb Files: c77db0ad00ceb573d3cda99321a5c2c8 1910 science extra simgrid_3.7-1.dsc 0b481d1393e118847fde021f331fe130 10762328 science extra simgrid_3.7.orig.tar.gz 417a93a392dae78bcb9934cdcfba0739 7195 science extra simgrid_3.7-1.debian.tar.gz f76f708bffa53bd90590a08b9adf4436 10029916 science extra simgrid_3.7-1_amd64.deb
Bug#674395: libdbd-mysql-perl: FTBFS: ld: cannot find -lssl
On Thu, 24 May 2012 14:38:59 +0200, gregor herrmann wrote: > I haven't looked yet, but this seems new ... Can this be related to > changes in libmysqlclient-dev from 5.1 to 5.5? > http://packages.debian.org/changelogs/pool/main/m/mysql-5.5/current/changelog > mentions SSL stuff at some points ... > > (Random factoid: Lucas' rebuild was against > libmysqlclient-dev 5.5.23-2, yesterday 5.5.23+dfsg-1 was uploaded > with the changelog entry: >* Revert having libssl-dev as a build dependency and changed > WITH_SSL option to 'bundled' from 'yes' (Closes: #590905) > and (Closes: #673865) > ) Yup, FTBFS in an amd64 chroot with libmysqlclient-dev 5.5.23-2, builds successfully in an i386 chroot with libmysqlclient-dev 5.5.23+dfsg-1 (which didn't build for amd64, that's why I tried i386). I guess we can close this bug, at least as soon as the newer mysql is available everywhere. Cheers, gregor -- .''`. Homepage: http://info.comodo.priv.at/ - OpenPGP key 0xBB3A68018649AA06 : :' : Debian GNU/Linux user, admin, and developer - http://www.debian.org/ `. `' Member of VIBE!AT & SPI, fellow of the Free Software Foundation Europe `- NP: Mark Knopfler: Who's Your Baby Now signature.asc Description: Digital signature
Bug#674394: marked as done (php-xml-parser: FTBFS: test failed)
Your message dated Thu, 24 May 2012 14:51:27 + with message-id and subject line Bug#674394: fixed in php-xml-parser 1.3.4-6 has caused the Debian Bug report #674394, regarding php-xml-parser: FTBFS: test failed 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.) -- 674394: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=674394 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: php-xml-parser Version: 1.3.4-5 Severity: serious Tags: wheezy sid User: debian...@lists.debian.org Usertags: qa-ftbfs-20120524 qa-ftbfs Justification: FTBFS on amd64 Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part: > make[1]: Entering directory `/«PKGBUILDDIR»' > dh_link -O--buildsystem=phppear > chmod +x ./debian/tests_run > ./debian/tests_run > PHPUnit 3.6.10 by Sebastian Bergmann. > > ...SFS > > Time: 1 second, Memory: 3.50Mb > > There was 1 failure: > > 1) /«PKGBUILDDIR»/XML_Parser-1.3.4/tests/004b.phpt > --- Expected > +++ Actual > @@ @@ > -New XML_Parser: string(10) "xml_parser" > -Error message: XML_Parser: Mismatched tag at XML input line 2:12 > +Warning: require_once(XML/Parser.php): failed to open stream: No such file > or directory in /«PKGBUILDDIR»/XML_Parser-1.3.4/tests/004b.php on line 2 > + > +Fatal error: require_once(): Failed opening required 'XML/Parser.php' > (include_path='.:/usr/share/php:/«PKGBUILDDIR»/XML_Parser-1.3.4') in > /«PKGBUILDDIR»/XML_Parser-1.3.4/tests/004b.php on line 2 > > /usr/bin/phpunit:46 > > FAILURES! > Tests: 10, Assertions: 10, Failures: 1, Skipped: 6. > make[1]: *** [override_dh_link] Error 1 The full build log is available from: http://people.debian.org/~lucas/logs/2012/05/24/php-xml-parser_1.3.4-5_unstable.log 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. --- End Message --- --- Begin Message --- Source: php-xml-parser Source-Version: 1.3.4-6 We believe that the bug you reported is fixed in the latest version of php-xml-parser, which is due to be installed in the Debian FTP archive: php-xml-parser_1.3.4-6.debian.tar.gz to main/p/php-xml-parser/php-xml-parser_1.3.4-6.debian.tar.gz php-xml-parser_1.3.4-6.dsc to main/p/php-xml-parser/php-xml-parser_1.3.4-6.dsc php-xml-parser_1.3.4-6_all.deb to main/p/php-xml-parser/php-xml-parser_1.3.4-6_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 674...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Thomas Goirand (supplier of updated php-xml-parser package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: RIPEMD160 Format: 1.8 Date: Thu, 24 May 2012 14:43:28 + Source: php-xml-parser Binary: php-xml-parser Architecture: source all Version: 1.3.4-6 Distribution: unstable Urgency: low Maintainer: PKG-PHP-PEAR team Changed-By: Thomas Goirand Description: php-xml-parser - PHP PEAR module for parsing XML Closes: 674394 Changes: php-xml-parser (1.3.4-6) unstable; urgency=low . * Fixed unit tests script and fixes FTBFS (Closes: #674394). Checksums-Sha1: b48f75744c0b52d05a9118228cc4e601e1b4986e 1416 php-xml-parser_1.3.4-6.dsc 228019f6def54dc700f29c6f8f7a5da871168504 4980 php-xml-parser_1.3.4-6.debian.tar.gz 21e4cfae0b0fcd94f2dbb3d73aec486b526b4f81 27238 php-xml-parser_1.3.4-6_all.deb Checksums-Sha256: e5d19ea7e55100dce04dcff38501b8b60353a3e76591767b37009375c9beae72 1416 php-xml-parser_1.3.4-6.dsc 9d3e3736ea08e8863688e595724d573071438fc647d8a8e7bb365190d9e90f5e 4980 php-xml-parser_1.3.4-6.debian.tar.gz 94e86d4833c15c60eabb1ba3b55907e4d5e45b0706b43a1b4a09275cb1cb0389 27238 php-xml-parser_1.3.4-6_all.deb Files: 8243a6db46e173e52f3b58e5977e0821 1416 php optional php-xml-parser_1.3.4-6.dsc 51c368b4e472d324fdad11a741a1314f 4980 php optional php-xml-parser_1.3.4-6.debian.tar.gz dce82414cd142b6d434a0694336b9f
Bug#674304: marked as done (clusterssh: FTBFS: tests failed)
Your message dated Thu, 24 May 2012 14:47:40 + with message-id and subject line Bug#674304: fixed in clusterssh 4.01.01-3 has caused the Debian Bug report #674304, regarding clusterssh: FTBFS: tests failed 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.) -- 674304: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=674304 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: clusterssh Version: 4.01.01-2 Severity: serious Tags: wheezy sid User: debian...@lists.debian.org Usertags: qa-ftbfs-20120524 qa-ftbfs Justification: FTBFS on amd64 Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part: > make[1]: Entering directory `/«PKGBUILDDIR»' > PERL_DL_NONLAZY=1 /usr/bin/perl "-MExtUtils::Command::MM" "-e" > "test_harness(0, 'blib/lib', 'blib/arch')" t/*.t > t/00-load.t ... ok > t/01l10n.t ok > t/02base.t ok > t/10host.t ok > "ssh" binary not found - please amend $PATH or the cssh config file# Tests > were run but no plan was declared and done_testing() was not seen. > t/15config.t .. > Dubious, test returned 2 (wstat 512, 0x200) > All 1 subtests passed > t/20helper.t .. ok > t/30cluster.t . ok > Subroutine CORE::GLOBAL::exit redefined at /usr/lib/perl5/Tk.pm line 414. > "ssh" binary not found - please amend $PATH or the cssh config file# Tests > were run but no plan was declared and done_testing() was not seen. > t/80clusterssh.t .. > Dubious, test returned 2 (wstat 512, 0x200) > All 1 subtests passed > t/boilerplate.t ... ok > # Distribution files are missing in MANIFEST: > # pm_to_blib > # .pc/applied-patches > # .pc/.quilt_series > # .pc/.quilt_patches > # .pc/.version > # .pc/debian_364565.patch/lib/App/ClusterSSH.pm > # .pc/03_disable_config_test.patch/t/15config.t > # .pc/debian_578208.patch/lib/App/ClusterSSH.pm > # debian/clusterssh.debhelper.log > # debian/NEWS > # debian/README.Debian > # debian/dirs > # debian/preinst > # debian/clusterssh.desktop > # debian/menu > # debian/changelog > # debian/compat > # debian/copyright > # debian/clusterssh-32x32.xpm > # debian/control > # debian/rules > # debian/postinst > # debian/watch > # debian/README.source > # debian/postrm > # debian/patches/series > # debian/patches/debian_364565.patch > # debian/patches/03_disable_config_test.patch > # debian/patches/debian_578208.patch > # debian/patches/debian_644368.patch > # debian/source/format > t/manifest.t .. ok > t/pod-coverage.t .. ok > t/pod.t ... ok > > Test Summary Report > --- > t/15config.t(Wstat: 512 Tests: 1 Failed: 0) > Non-zero exit status: 2 > Parse errors: No plan found in TAP output > t/80clusterssh.t (Wstat: 512 Tests: 1 Failed: 0) > Non-zero exit status: 2 > Parse errors: No plan found in TAP output > t/boilerplate.t (Wstat: 0 Tests: 3 Failed: 0) > TODO passed: 1-3 > Files=12, Tests=437, 42 wallclock secs ( 0.13 usr 0.06 sys + 1.79 cusr > 0.28 csys = 2.26 CPU) > Result: FAIL > Failed 2/12 test programs. 0/437 subtests failed. > make[1]: *** [test_dynamic] Error 255 The full build log is available from: http://people.debian.org/~lucas/logs/2012/05/24/clusterssh_4.01.01-2_unstable.log 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. --- End Message --- --- Begin Message --- Source: clusterssh Source-Version: 4.01.01-3 We believe that the bug you reported is fixed in the latest version of clusterssh, which is due to be installed in the Debian FTP archive: clusterssh_4.01.01-3.debian.tar.gz to main/c/clusterssh/clusterssh_4.01.01-3.debian.tar.gz clusterssh_4.01.01-3.dsc to main/c/clusterssh/clusterssh_4.01.01-3.dsc clusterssh_4.01.01-3_all.deb to main/c/clusterssh/clusterssh_4.01.01-3_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 674...@bugs.debian.org, and the maintainer will reopen the bug report
Processed: tagging 674346
Processing commands for cont...@bugs.debian.org: > tags 674346 + pending Bug #674346 [src:soprano] soprano: FTBFS: /bin/sh: 1: docs/html/installdox: not found Added tag(s) pending. > thanks Stopping processing here. Please contact me if you need assistance. -- 674346: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=674346 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#673773: fwknop-server: fails to install: subprocess installed post-installation script returned error exit status 10
Le 21/05/2012 12:45, Andreas Beckmann a écrit : Hi, Hi, during a test with piuparts I noticed your package failed to install. As per definition of the release team this makes the package too buggy for a release, thus the severity. [...] Ok, I am taking care of psad and fwsnort and I will check that one afterwards. Regards, -- Franck -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#674368: marked as done (libarchive: FTBFS: tests failed)
Your message dated Thu, 24 May 2012 13:33:09 + with message-id and subject line Bug#674368: fixed in libarchive 3.0.4-2 has caused the Debian Bug report #674368, regarding libarchive: FTBFS: tests failed 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.) -- 674368: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=674368 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: libarchive Version: 3.0.4-1 Severity: serious Tags: wheezy sid User: debian...@lists.debian.org Usertags: qa-ftbfs-20120524 qa-ftbfs Justification: FTBFS on amd64 Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part: > make[4]: Entering directory `/«PKGBUILDDIR»' > > If tests fail or crash, details will be in: >/tmp/libarchive_test.2012-05-23T20.55.07-000 > > Reference files will be read from: /«PKGBUILDDIR»/libarchive/test > Exercising: libarchive 3.0.4 > 0: test_acl_freebsd > libarchive/test/test_acl_freebsd.c:191: SKIPPING: FreeBSD-specific ACL > restore test > 1: test_acl_nfs4 > 2: test_acl_pax > 3: test_acl_posix1e > 4: test_archive_api_feature > 5: test_archive_clear_error > 6: test_archive_md5 > 7: test_archive_rmd160 > 8: test_archive_sha1 > 9: test_archive_sha256 > 10: test_archive_sha384 > 11: test_archive_sha512 > 12: test_archive_getdate > 13: test_archive_match_owner > 14: test_archive_match_path > 15: test_archive_match_time > 16: test_archive_pathmatch > 17: test_archive_read_close_twice > 18: test_archive_read_close_twice_open_fd > 19: test_archive_read_close_twice_open_filename > 20: test_archive_read_next_header_empty > 21: test_archive_read_next_header_raw > 22: test_archive_read_open2 > 23: test_archive_read_set_filter_option > 24: test_archive_read_set_format_option > 25: test_archive_read_set_option > 26: test_archive_read_set_options > 27: test_archive_read_support > 28: test_archive_set_error > 29: test_archive_string > 30: test_archive_string_conversion > 31: test_archive_write_set_filter_option > 32: test_archive_write_set_format_option > 33: test_archive_write_set_option > 34: test_archive_write_set_options > 35: test_bad_fd > 36: test_compat_bzip2 > 37: test_compat_cpio > 38: test_compat_gtar > 39: test_compat_gzip > 40: test_compat_lzip > 41: test_compat_lzma > 42: test_compat_mac > 43: test_compat_pax_libarchive_2x > libarchive/test/test_compat_pax_libarchive_2x.c:45: SKIPPING: This test only > for the platform the WCS of which is not Unicode. > 44: test_compat_solaris_pax_sparse > 45: test_compat_solaris_tar_acl > 46: test_compat_tar_hardlink > 47: test_compat_xz > 48: test_compat_zip > 49: test_empty_write > 50: test_entry > 51: test_entry_strmode > 52: test_extattr_freebsd > libarchive/test/test_extattr_freebsd.c:39: SKIPPING: FreeBSD-specific extattr > restore test > 53: test_filter_count > 54: test_fuzz > 55: test_gnutar_filename_encoding > libarchive/test/test_gnutar_filename_encoding.c:81: SKIPPING: KOI8-R locale > not available on this system. > libarchive/test/test_gnutar_filename_encoding.c:123: SKIPPING: KOI8-R locale > not available on this system. > libarchive/test/test_gnutar_filename_encoding.c:166: SKIPPING: KOI8-R locale > not available on this system. > libarchive/test/test_gnutar_filename_encoding.c:211: SKIPPING: KOI8-R locale > not available on this system. > libarchive/test/test_gnutar_filename_encoding.c:252: SKIPPING: Russian_Russia > locale not available on this system. > libarchive/test/test_gnutar_filename_encoding.c:288: SKIPPING: eucJP locale > not available on this system. > libarchive/test/test_gnutar_filename_encoding.c:329: SKIPPING: eucJP locale > not available on this system. > libarchive/test/test_gnutar_filename_encoding.c:371: SKIPPING: CP932/SJIS > locale not available on this system. > 56: test_link_resolver > 57: test_open_failure > 58: test_open_fd > 59: test_open_file > 60: test_open_filename > 61: test_pax_filename_encoding > libarchive/test/test_pax_filename_encoding.c:347: SKIPPING: KOI8-R locale not > available on this system. > libarchive/test/test_pax_filename_encoding.c:395: SKIPPING: KOI8-R locale not > available on this system. > libarchive/test/test_pax_filename_encoding.c:442: SKIPPING: eucJP locale not &g
Bug#672690: marked as done (libarchive: FTBFS on hurd-i386)
Your message dated Thu, 24 May 2012 13:33:09 + with message-id and subject line Bug#674368: fixed in libarchive 3.0.4-2 has caused the Debian Bug report #674368, regarding libarchive: FTBFS on hurd-i386 to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 674368: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=674368 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: libarchive Version: 3.0.4-1 Severity: important User: debian-...@lists.debian.org Usertags: ftbfs-gcc-4.7 Hello, libarchive currently FTBFS on hurd-i386, see https://buildd.debian.org/status/fetch.php?pkg=libarchive&arch=hurd-i386&ver=3.0.4-1%2Bb1&stamp=1336821322 This build was done with gcc-4.7, which is probably the "culprit", by optimizing yet more. The issue is with the following piece of code: min_time = archive_entry_mtime(ae); assert(min_time <= 0); /* Simply asserting min_time - 1 > 0 breaks with some compiler optimizations. */ t = min_time - 1; assert(t > 0); This is supposed to check for overflowing when subtracting 1 from the minimum time_t value. Problem is: that is undefined in C, and the compiler is thus allowed to do anything, including always raising the assertion, since we have already checked that the integer is negative, so subtracting 1 to it is not supposed to make it positive (again, overflow is undefined). Printing t, for instance, fixes the test, since the compiler then actually computes t, but without it the assert always gets triggered. I tried to reproduce it with i386, without success, but anyway, the piece of code really has undefined behavior. Samuel -- System Information: Debian Release: wheezy/sid APT prefers testing APT policy: (990, 'testing'), (500, 'unstable'), (500, 'stable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 3.0.4 (SMP w/8 CPU cores) Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash -- Samuel Thibault Ça peut être une madeleine à sous munitions (avec des composants, par exemple) -+- #runtime -+- --- End Message --- --- Begin Message --- Source: libarchive Source-Version: 3.0.4-2 We believe that the bug you reported is fixed in the latest version of libarchive, which is due to be installed in the Debian FTP archive: bsdcpio_3.0.4-2_amd64.deb to main/liba/libarchive/bsdcpio_3.0.4-2_amd64.deb bsdtar_3.0.4-2_amd64.deb to main/liba/libarchive/bsdtar_3.0.4-2_amd64.deb libarchive-dev_3.0.4-2_amd64.deb to main/liba/libarchive/libarchive-dev_3.0.4-2_amd64.deb libarchive12_3.0.4-2_amd64.deb to main/liba/libarchive/libarchive12_3.0.4-2_amd64.deb libarchive_3.0.4-2.debian.tar.gz to main/liba/libarchive/libarchive_3.0.4-2.debian.tar.gz libarchive_3.0.4-2.dsc to main/liba/libarchive/libarchive_3.0.4-2.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 674...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Andreas Henriksson (supplier of updated libarchive package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.8 Date: Thu, 24 May 2012 14:49:41 +0200 Source: libarchive Binary: libarchive-dev libarchive12 bsdtar bsdcpio Architecture: source amd64 Version: 3.0.4-2 Distribution: unstable Urgency: low Maintainer: Debian Libarchive Maintainers Changed-By: Andreas Henriksson Description: bsdcpio- Implementation of the 'cpio' program from FreeBSD bsdtar - Implementation of the 'tar' program from FreeBSD libarchive-dev - Multi-format archive and compression library (development files) libarchive12 - Multi-format archive and compression library (shared library) Closes: 672690 674368 Changes: libarchive (3.0.4-2) unstable; urgency=low . * Add debian/patches/gcc-4.7-fixes-from-upstream.patch (Closes: #674368, #672690) Checksums-Sha1: 8a836a16a9e81a979a7e79f85ea0a10dc0fcfe26 1612 libarchive_3.0.4-2.dsc 61c0432033571e15291c43cf08c84d9978e9091e 10185 libarchive_3.0.4-2.debian.tar.gz 0e525220cb53bffd48d9c8e57b6ee9fd7543bcfa 471984 libarchive-dev_3.0.4-2_amd64.deb eb568bd57d7b18ead6d4088b3e9e5c1ec9e2b554 303296 libarchive12_3.0.4-2_amd64.deb 1c6364746c8b894ac2560f6c534ac78ec6800da1 54428 bsdtar_3.0.4-2_amd6
Bug#674368: marked as done (libarchive: FTBFS: tests failed)
Your message dated Thu, 24 May 2012 13:33:09 + with message-id and subject line Bug#672690: fixed in libarchive 3.0.4-2 has caused the Debian Bug report #672690, regarding libarchive: FTBFS: tests failed 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.) -- 672690: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=672690 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: libarchive Version: 3.0.4-1 Severity: serious Tags: wheezy sid User: debian...@lists.debian.org Usertags: qa-ftbfs-20120524 qa-ftbfs Justification: FTBFS on amd64 Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part: > make[4]: Entering directory `/«PKGBUILDDIR»' > > If tests fail or crash, details will be in: >/tmp/libarchive_test.2012-05-23T20.55.07-000 > > Reference files will be read from: /«PKGBUILDDIR»/libarchive/test > Exercising: libarchive 3.0.4 > 0: test_acl_freebsd > libarchive/test/test_acl_freebsd.c:191: SKIPPING: FreeBSD-specific ACL > restore test > 1: test_acl_nfs4 > 2: test_acl_pax > 3: test_acl_posix1e > 4: test_archive_api_feature > 5: test_archive_clear_error > 6: test_archive_md5 > 7: test_archive_rmd160 > 8: test_archive_sha1 > 9: test_archive_sha256 > 10: test_archive_sha384 > 11: test_archive_sha512 > 12: test_archive_getdate > 13: test_archive_match_owner > 14: test_archive_match_path > 15: test_archive_match_time > 16: test_archive_pathmatch > 17: test_archive_read_close_twice > 18: test_archive_read_close_twice_open_fd > 19: test_archive_read_close_twice_open_filename > 20: test_archive_read_next_header_empty > 21: test_archive_read_next_header_raw > 22: test_archive_read_open2 > 23: test_archive_read_set_filter_option > 24: test_archive_read_set_format_option > 25: test_archive_read_set_option > 26: test_archive_read_set_options > 27: test_archive_read_support > 28: test_archive_set_error > 29: test_archive_string > 30: test_archive_string_conversion > 31: test_archive_write_set_filter_option > 32: test_archive_write_set_format_option > 33: test_archive_write_set_option > 34: test_archive_write_set_options > 35: test_bad_fd > 36: test_compat_bzip2 > 37: test_compat_cpio > 38: test_compat_gtar > 39: test_compat_gzip > 40: test_compat_lzip > 41: test_compat_lzma > 42: test_compat_mac > 43: test_compat_pax_libarchive_2x > libarchive/test/test_compat_pax_libarchive_2x.c:45: SKIPPING: This test only > for the platform the WCS of which is not Unicode. > 44: test_compat_solaris_pax_sparse > 45: test_compat_solaris_tar_acl > 46: test_compat_tar_hardlink > 47: test_compat_xz > 48: test_compat_zip > 49: test_empty_write > 50: test_entry > 51: test_entry_strmode > 52: test_extattr_freebsd > libarchive/test/test_extattr_freebsd.c:39: SKIPPING: FreeBSD-specific extattr > restore test > 53: test_filter_count > 54: test_fuzz > 55: test_gnutar_filename_encoding > libarchive/test/test_gnutar_filename_encoding.c:81: SKIPPING: KOI8-R locale > not available on this system. > libarchive/test/test_gnutar_filename_encoding.c:123: SKIPPING: KOI8-R locale > not available on this system. > libarchive/test/test_gnutar_filename_encoding.c:166: SKIPPING: KOI8-R locale > not available on this system. > libarchive/test/test_gnutar_filename_encoding.c:211: SKIPPING: KOI8-R locale > not available on this system. > libarchive/test/test_gnutar_filename_encoding.c:252: SKIPPING: Russian_Russia > locale not available on this system. > libarchive/test/test_gnutar_filename_encoding.c:288: SKIPPING: eucJP locale > not available on this system. > libarchive/test/test_gnutar_filename_encoding.c:329: SKIPPING: eucJP locale > not available on this system. > libarchive/test/test_gnutar_filename_encoding.c:371: SKIPPING: CP932/SJIS > locale not available on this system. > 56: test_link_resolver > 57: test_open_failure > 58: test_open_fd > 59: test_open_file > 60: test_open_filename > 61: test_pax_filename_encoding > libarchive/test/test_pax_filename_encoding.c:347: SKIPPING: KOI8-R locale not > available on this system. > libarchive/test/test_pax_filename_encoding.c:395: SKIPPING: KOI8-R locale not > available on this system. > libarchive/test/test_pax_filename_encoding.c:442: SKIPPING: eucJP locale not &g
