Bug#675911: swig2.0: Wrong configuration for Java
On Mon, Jun 11, 2012 at 10:00 PM, Torsten Landschoff t.landsch...@gmx.net wrote: On 06/04/2012 08:26 AM, Mathieu Malaterre wrote: swig2.0 should be configured with default Java (default-jdk package). It currently uses gcj-jdk You are right. However, I fail to see how this renders the package unusable as the SWIG generated code should be portable among different Java version. I think severity grave is a bit exaggerated here. I thought this was a clear requirement, re-reading it: http://www.debian.org/doc/packaging-manuals/java-policy/c208.html Java packages should be built with default-jdk if possible. So there is a should and if possible, how do you understand the statement ? -- 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 598638 is serious
Processing commands for cont...@bugs.debian.org: severity 598638 serious Bug #598638 [libatlas3gf-base] lapack: update-alternatives breaks application linking Bug #576972 [libatlas3gf-base] libatlas3gf-base: octave does not work with this version Bug #624318 [libatlas3gf-base] Subject: liblapack.so.3gf: undefined symbol: ATL_dGetNB Bug #638236 [libatlas3gf-base] /usr/lib/liblapack.so.3gf: undefined symbol: ATL_chem Bug #676726 [libatlas3gf-base] libopenblas-base, libatlas3-base: Coinstalling libatlas3-base and libopenblas-base breaks LAPACK Severity set to 'serious' from 'important' Severity set to 'serious' from 'important' Severity set to 'serious' from 'important' Severity set to 'serious' from 'important' Severity set to 'serious' from 'important' thanks Stopping processing here. Please contact me if you need assistance. -- 576972: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=576972 598638: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=598638 624318: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=624318 638236: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=638236 676726: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=676726 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#675908: marked as done (swig2.0: Wrong python configuration: python2.5)
Your message dated Tue, 12 Jun 2012 06:48:19 +
with message-id e1sektn-a3...@franck.debian.org
and subject line Bug#675908: fixed in swig2.0 2.0.7-3
has caused the Debian Bug report #675908,
regarding swig2.0: Wrong python configuration: python2.5
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
675908: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=675908
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
---BeginMessage---
Package: swig2.0
Version: 2.0.7-2
Severity: grave
Justification: renders package unusable
swig2.0 is configured with python2.5 which is non-existant on sid:
PHP4INC=`php-config --includes` \
CFLAGS=-g -O2 `perl -e 'use Config; print $Config{ccflags};'` \
cd builddir ../configure --prefix=/usr --mandir=/usr/share/man
--with-tclconfig=/usr/lib --with-python=/usr/bin/python2.5
--with-ruby=/usr/bin/ruby1.8 --with-pike=/usr/bin/pike7.6
--with-pikeincl=/usr/include/pike/7.6.24 --with-swiglibdir=/usr/share/swig2.0
--without-mzscheme --program-suffix=2.0 --with-java=/usr/bin/java
--with-javac=/usr/bin/javac --with-chicken=/usr/bin/chicken
--with-chickencfg=/usr/bin/chicken-config
checking build system type... i686-pc-linux-gnu
checking for Python exec-prefix...
.../configure: line 7365: /usr/bin/python2.5: No such file or directory
-- System Information:
Debian Release: 6.0.4
APT prefers stable-updates
APT policy: (500, 'stable-updates'), (500, 'stable'), (200, 'testing'), (100,
'unstable')
Architecture: amd64 (x86_64)
Kernel: Linux 2.6.39-bpo.2-amd64 (SMP w/8 CPU cores)
Locale: LANG=en_US.utf8, LC_CTYPE=en_US.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Versions of packages swig2.0 depends on:
ii libc6 2.11.3-3 Embedded GNU C Library: Shared lib
ii libgcc1 1:4.4.5-8GCC support library
ii libpcre38.02-1.1 Perl 5 Compatible Regular Expressi
ii libstdc++6 4.4.5-8 The GNU Standard C++ Library v3
ii zlib1g 1:1.2.3.4.dfsg-3 compression library - runtime
swig2.0 recommends no packages.
Versions of packages swig2.0 suggests:
pn swig2.0-doc none (no description available)
pn swig2.0-examples none (no description available)
-- no debconf information
---End Message---
---BeginMessage---
Source: swig2.0
Source-Version: 2.0.7-3
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.7-3_all.deb
to main/s/swig2.0/swig-doc_2.0.7-3_all.deb
swig-examples_2.0.7-3_all.deb
to main/s/swig2.0/swig-examples_2.0.7-3_all.deb
swig2.0-doc_2.0.7-3_all.deb
to main/s/swig2.0/swig2.0-doc_2.0.7-3_all.deb
swig2.0-examples_2.0.7-3_all.deb
to main/s/swig2.0/swig2.0-examples_2.0.7-3_all.deb
swig2.0_2.0.7-3.debian.tar.gz
to main/s/swig2.0/swig2.0_2.0.7-3.debian.tar.gz
swig2.0_2.0.7-3.dsc
to main/s/swig2.0/swig2.0_2.0.7-3.dsc
swig2.0_2.0.7-3_amd64.deb
to main/s/swig2.0/swig2.0_2.0.7-3_amd64.deb
swig_2.0.7-3_amd64.deb
to main/s/swig2.0/swig_2.0.7-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 675...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Torsten Landschoff tors...@debian.org (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: Mon, 11 Jun 2012 22:55:25 +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.7-3
Distribution: sid
Urgency: low
Maintainer: Torsten Landschoff tors...@debian.org
Changed-By: Torsten Landschoff tors...@debian.org
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: 675908 675911
Changes:
swig2.0 (2.0.7-3) unstable; urgency=low
.
* Use /usr/bin/python instead of /usr/bin/python2.5 in debian/rules
(closes: #675908).
* Use default-jdk
Bug#675911: marked as done (swig2.0: Wrong configuration for Java)
Your message dated Tue, 12 Jun 2012 06:48:19 + with message-id e1sektn-a6...@franck.debian.org and subject line Bug#675911: fixed in swig2.0 2.0.7-3 has caused the Debian Bug report #675911, regarding swig2.0: Wrong configuration for Java 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.) -- 675911: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=675911 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: swig2.0 Version: 2.0.7-2 Severity: grave Justification: renders package unusable swig2.0 should be configured with default Java (default-jdk package). It currently uses gcj-jdk -- System Information: Debian Release: 6.0.4 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable'), (200, 'testing'), (100, 'unstable') Architecture: amd64 (x86_64) Kernel: Linux 2.6.39-bpo.2-amd64 (SMP w/8 CPU cores) Locale: LANG=en_US.utf8, LC_CTYPE=en_US.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages swig2.0 depends on: ii libc6 2.11.3-3 Embedded GNU C Library: Shared lib ii libgcc1 1:4.4.5-8GCC support library ii libpcre38.02-1.1 Perl 5 Compatible Regular Expressi ii libstdc++6 4.4.5-8 The GNU Standard C++ Library v3 ii zlib1g 1:1.2.3.4.dfsg-3 compression library - runtime swig2.0 recommends no packages. Versions of packages swig2.0 suggests: pn swig2.0-doc none (no description available) pn swig2.0-examples none (no description available) -- no debconf information ---End Message--- ---BeginMessage--- Source: swig2.0 Source-Version: 2.0.7-3 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.7-3_all.deb to main/s/swig2.0/swig-doc_2.0.7-3_all.deb swig-examples_2.0.7-3_all.deb to main/s/swig2.0/swig-examples_2.0.7-3_all.deb swig2.0-doc_2.0.7-3_all.deb to main/s/swig2.0/swig2.0-doc_2.0.7-3_all.deb swig2.0-examples_2.0.7-3_all.deb to main/s/swig2.0/swig2.0-examples_2.0.7-3_all.deb swig2.0_2.0.7-3.debian.tar.gz to main/s/swig2.0/swig2.0_2.0.7-3.debian.tar.gz swig2.0_2.0.7-3.dsc to main/s/swig2.0/swig2.0_2.0.7-3.dsc swig2.0_2.0.7-3_amd64.deb to main/s/swig2.0/swig2.0_2.0.7-3_amd64.deb swig_2.0.7-3_amd64.deb to main/s/swig2.0/swig_2.0.7-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 675...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Torsten Landschoff tors...@debian.org (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: Mon, 11 Jun 2012 22:55:25 +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.7-3 Distribution: sid Urgency: low Maintainer: Torsten Landschoff tors...@debian.org Changed-By: Torsten Landschoff tors...@debian.org 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: 675908 675911 Changes: swig2.0 (2.0.7-3) unstable; urgency=low . * Use /usr/bin/python instead of /usr/bin/python2.5 in debian/rules (closes: #675908). * Use default-jdk instead of gcj-jdk (closes: #675911). Checksums-Sha1: 81ef6018c3545c4668bcb6396a74006534fe261f 1652 swig2.0_2.0.7-3.dsc fb20cc4ce50222399a846871d9551f23dae751a4 18908 swig2.0_2.0.7-3.debian.tar.gz 77b49312b95b468fb379e3456ca56f8f22d588d5 271650 swig-examples_2.0.7-3_all.deb 64a2954c31c7123a6963609caa8e2db2b244ebef 1274314 swig2.0-examples_2.0.7-3_all.deb 3e106df7f8cd697177cc3559061254f4aa1f8b3b 271632 swig-doc_2.0.7-3_all.deb 7ac4daf0d4bc3de5ea182d59fa7e39fc029c1e36 2800870 swig2.0-doc_2.0.7-3_all.deb 271438703f07332b59b3b27c8ca121722ff4 276996 swig_2.0.7-3_amd64.deb c0bacbd879a3107120f2f2f5bd3f00776a9dafb7 1435562 swig2.0_2.0.7-3_amd64.deb Checksums-Sha256:
Bug#676686: [xml/sgml-pkgs] Bug#676686: libxslt1.1: libxslt1.1 binNMU broke multi-arch installability
On Mon, 2012-06-11 at 11:39:24 +0100, Ian Jackson wrote: Guillem Jover writes (Re: [xml/sgml-pkgs] Bug#676686: libxslt1.1: libxslt1.1 binNMU broke multi-arch installability): As I mentioned in the long ref-counting thread, I strongly disagree this is a correct solution, it just seems like a hack to me. Instead I think we should consider changelog (and copyright as long as it's in machine parseable format) as dpkg metadata (something dpkg misses compared to rpm or other package managers for example) and as such they should go into the .deb control member, which would end up in the dpkg database w/o any kind of file conflict, and very minor packaging effort as for most that would be handled by helpers. I think this is the wrong design. The changelog is primarily used by humans, not software, and burying it in the dpkg database is not helpful. I think the solution with the binNMU changelogs is straightforward and should be implemented. Well, the dpkg suite makes extensive use of the changelog to retrieve all kinds of information, dpkg (the program) does not currently access it though, but that data is still package metadata. The same could be said about some fields in the control file and it still makes sense to have them there, because again it's package metadata. There's also other precedent of package metadata not handled directly by dpkg (currently or in the past) which gets installed in the info database, like templates, config, md5sums and clilibs, for some I'm aware of. I disagree placing it in the dpkg database is not helpful, for a user or other programs wanting to access that structured package metadata it's obviously easier and better to do something like «dpkg --show-changelog foo» or «dpkg-query --control-path foo changelog», than having to go hunt where in the filesystem the changelog might be located, regardless of distribution path polcies. The same for the copyright information, and I've actually been asked in the past why dpkg does not have a command to show package copyright information. I've listed the other reasons (which you trimmed) in the parent mail. And if by “the binNMU changelogs”, you mean the split changelog solution, I still disagree that's the correct avenue. It means the information of why the package was rebuilt either ends up in yet another different place on the filesystem, or lost if the helper does not get updated to cope with that or if the package does not use any helper, which is still a non-insignificant amount of the archive. It might also break with packages poking at the debian/changelog file directly as Jonathan mentioned, or external software accessing the source tree, because debian/changelog is an interface, and while it might seem like a straightforward solution it looks like it will cause more problems than the ones it solves, and it still seems like a workaround. * changelog extractors (like apt-listchanges) would not need (eventually) to extract the whole .deb data member to get the changelog, it would just need to extract the control member, and get a fixed filename. They would stop needing to hardcode possible paths to the files too. This still leaves the NEWS.Debian file but then maybe that should also be considered metadata... This path leads, eventually, to all structured data currently stored in the filesystem being subsumed by dpkg. This is not healthy for dpkg and not healthy for the rest of the project. Eh, only structured data that is packaging metadata. TBH, I don't see other clear candidates besides changelog and copyright (maybe even NEWS.Debian, but this one might be a stretch), and those two are clearly package metadata. So, I'm still unconvinced by the arguments you brought up. regards, guillem -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#677130: marked as done (pyppd doesn't build with python3)
Your message dated Tue, 12 Jun 2012 07:03:06 +
with message-id e1sel86-00027k...@franck.debian.org
and subject line Bug#677130: fixed in pyppd 0.4.9-8
has caused the Debian Bug report #677130,
regarding pyppd doesn't build with python3
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.)
--
677130: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=677130
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
---BeginMessage---
Package: pyppd
Version: 0.4.9-7
Severity: serious
Tags: patch
Justification: fails to build from source (but built successfully in the
past)
User: ubuntu-de...@lists.ubuntu.com
Usertags: origin-ubuntu quantal ubuntu-patch
Dear Maintainer,
This patch allows pyppd to build with python3. In addition I've tested
it with
python2.7.
This modifies the setup.py long_description variable to convert loaded data
into bytes first,
then to utf-8.
*** /tmp/tmpUEI3Df/bug_body
In Ubuntu, the attached patch was applied to achieve the following:
* debian/patches/03_python3_setup.patch: setup.py long_description fixed
to work with both python2 and 3.
Thanks for considering the patch.
-- System Information:
Debian Release: wheezy/sid
APT prefers precise-updates
APT policy: (500, 'precise-updates'), (500, 'precise-security'), (500,
'precise'), (100, 'precise-backports')
Architecture: amd64 (x86_64)
Kernel: Linux 3.2.0-24-generic (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
diff -Nru pyppd-0.4.9/debian/changelog pyppd-0.4.9/debian/changelog
diff -Nru pyppd-0.4.9/debian/patches/03_python3_setup.patch pyppd-0.4.9/debian/patches/03_python3_setup.patch
--- pyppd-0.4.9/debian/patches/03_python3_setup.patch 1969-12-31 18:00:00.0 -0600
+++ pyppd-0.4.9/debian/patches/03_python3_setup.patch 2012-06-11 11:59:36.0 -0500
@@ -0,0 +1,17 @@
+## Description: Fixes setup.py long_description to work with python3.
+## Author: Chris J Arges chris.j.ar...@canonical.com
+Index: pyppd-0.4.9/setup.py
+===
+--- pyppd-0.4.9.orig/setup.py 2012-06-11 10:53:18.130693582 -0500
pyppd-0.4.9/setup.py 2012-06-11 10:55:45.822691880 -0500
+@@ -28,8 +28,8 @@
+ url='http://gitorious.org/vitorbaptista/pyppd/',
+ license='GPLv3',
+ description='A CUPS PostScript Printer Driver\'s compressor and generator',
+-long_description=open('README.txt').read() + \n +
+- open('ISSUES.txt').read(),
++long_description=(open('README.txt', 'rb').read() + b\n +
++ open('ISSUES.txt', 'rb').read()).decode(utf-8),
+ cmdclass={'sdist': sdist},
+ classifiers=[
+ 'Development Status :: 4 - Beta',
diff -Nru pyppd-0.4.9/debian/patches/series pyppd-0.4.9/debian/patches/series
--- pyppd-0.4.9/debian/patches/series 2012-06-05 02:52:15.0 -0500
+++ pyppd-0.4.9/debian/patches/series 2012-06-11 11:08:18.0 -0500
@@ -1,3 +1,4 @@
00git_improve_runtime_error_handling.patch
01_python3_compat.patch
02_use_python3.patch
+03_python3_setup.patch
---End Message---
---BeginMessage---
Source: pyppd
Source-Version: 0.4.9-8
We believe that the bug you reported is fixed in the latest version of
pyppd, which is due to be installed in the Debian FTP archive:
pyppd_0.4.9-8.debian.tar.gz
to main/p/pyppd/pyppd_0.4.9-8.debian.tar.gz
pyppd_0.4.9-8.dsc
to main/p/pyppd/pyppd_0.4.9-8.dsc
pyppd_0.4.9-8_all.deb
to main/p/pyppd/pyppd_0.4.9-8_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 677...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Martin Pitt mp...@debian.org (supplier of updated pyppd 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, 12 Jun 2012 08:39:24 +0200
Source: pyppd
Binary: pyppd
Architecture: source all
Version: 0.4.9-8
Distribution: experimental
Urgency: low
Maintainer: Debian Printing Group debian-print...@lists.debian.org
Changed-By: Martin Pitt mp...@debian.org
Description:
pyppd - CUPS PostScript Printer Driver's compressor and generator
Closes: 677130
Changes:
pyppd (0.4.9-8) experimental; urgency=low
.
* 00git_improve_runtime_error_handling.patch: Also
Bug#666672: should be fixed in 1.8.0
fixed 72 1.8.0-2 thanks This should be fixed with the recently uploaded 1.8.x branch. /Simon -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed: should be fixed in 1.8.0
Processing commands for cont...@bugs.debian.org: fixed 72 1.8.0-2 Bug #72 [src:gsasl] gsasl: FTBFS: tests hang Marked as fixed in versions gsasl/1.8.0-2. thanks Stopping processing here. Please contact me if you need assistance. -- 72: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=72 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#661887: mxml: Bad control character error when attempting to load banks
Message from upstream maintainer (SourceForge): Comment By: Mark McCurry (fundamental) Date: 2012-06-11 08:18 Message: As suspected, this bug report is out of date. While the version of zyn that debian testing ships with has this bug, this bug does not exist in the git head and thus it does not need to be patched. As I stated before there should be a release fairly soon, and I have tested this version on a fresh debian weezy install (32 bit if relevent). If you are able to replicate this bug with the current version of zyn, then feel free to reopen.
Processed (with 2 errors): r4921 - in packages/fonts-ipaexfont: tags tags/00103-13/debian trunk/debian
Processing commands for cont...@bugs.debian.org:
tags 676307 pending
Bug #676307 {Done: Hideki Yamane henr...@debian.org}
[fonts-ipaexfont-gothic,fonts-ipaexfont-mincho] fonts-ipaexfont-{gothic,
mincho}: fails to install: update-alternatives: error: error creating symbolic
link /usr/share/fonts/truetype/*.ttf.dpkg-tmp
Added tag(s) pending.
tags 642103 pending
Failed to alter tags of Bug 642103: Not altering archived bugs; see unarchive.
tags 565916 pending
Failed to alter tags of Bug 565916: Not altering archived bugs; see unarchive.
thanks
Stopping processing here.
Please contact me if you need assistance.
--
565916: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=565916
676307: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=676307
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#670733: Some remarks
severity 670733 important severity 672673 important severity 672666 important severity 672667 important severity 672668 important severity 672669 important severity 672670 important severity 672671 important thanks On 11/06/12 18:06, Romain Beauxis wrote: this issue is not even a RC issue because the module clearly does not fail to build in the buildds, it just fails to build with_pbuilder_. As such, I'm lowering the severity of these bugs to important. Regards, -- Mehdi Dogguy مهدي الدڤي http://dogguy.org/ -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#671711: Assumptions when processing triggers (was [pkg-mono-group] Bug#671711: monodoc-browser: fails to upgrade) from 'testing'
Hi there, [ dropping -devel ] On Fri, Jun 08, 2012 at 07:09:56AM +0200, Guillem Jover wrote: Hi! […] Hmmm, so I had prepared a patch which basically checks if the package has its dependencies fulfilled before calling the postinst script with triggered, and otherwise defers the trigger processing for later (but only as long as it is not running from inside the deferred trigproc run). This fixes this specific case just fine (t-triggers-depends test case in dpkg/pkg-tests.git), but this in turn creates problems with packages with pending triggers depending on packages awaiting them, as it forces breaking trigger cycles, which is not really a nice upgrade path. An immediate example of this is man-db and dpkg itself. While this specific case could be fixed by removing the old versioned dpkg dependency from man-db, I'm assuming other such cases might exist on the archive, and I'm not prepared to add any such fix to dpkg w/o further analysis. Is it possible to detect that there is a cycle happening and revert to the 'old' behaviour of just not considering satisfaction of depends? In any case, this and most other similar cases would just disappear by switching those triggers to the noawait variants, but that's not supported by dpkg in stable so that would need to wait until after wheezy. OTOH I'm quite tired right now, and it's probable I'm missing something obvious... but in view of the above possibly producing mass breakage I've pulled out that patch from the dpkg 1.16.4 release which I wanted to push yesterday already. OK. For mono-tools then, do we get that libgtk2.0-cil will be at least unpacked when the trigger is processed? i.e. could we have the postinst perform the GAC registration itself? Hmm, but that at least requires mono-gac (on which libgtk2.0-cil transitively depends) to be unpacked and for its postinst to be run too. Can we also assume that it will be unpacked by dpkg's standard ordering? Cheers, -- Iain Lane [ i...@orangesquash.org.uk ] Debian Developer [ la...@debian.org ] Ubuntu Developer [ la...@ubuntu.com ] PhD student [ i...@cs.nott.ac.uk ] signature.asc Description: Digital signature
Processed: Re: Bug#670733: Some remarks
Processing commands for cont...@bugs.debian.org: severity 670733 important Bug #670733 [src:ocaml-cry] ocaml-cry: FTBFS: Incorrectly thinks it's building as root Severity set to 'important' from 'serious' severity 672673 important Bug #672673 [src:ocaml-soundtouch] ocaml-soundtouch: FTBFS: Incorrectly thinks it's building as root Severity set to 'important' from 'serious' severity 672666 important Bug #672666 [src:ocaml-duppy] ocaml-duppy: FTBFS: Incorrectly thinks it's building as root Severity set to 'important' from 'serious' severity 672667 important Bug #672667 [src:ocaml-gstreamer] ocaml-gstreamer: FTBFS: Incorrectly thinks it's building as root Severity set to 'important' from 'serious' severity 672668 important Bug #672668 [src:ocaml-ladspa] ocaml-ladspa: FTBFS: Incorrectly thinks it's building as root Severity set to 'important' from 'serious' severity 672669 important Bug #672669 [src:ocaml-lame] ocaml-lame: FTBFS: Incorrectly thinks it's building as root Severity set to 'important' from 'serious' severity 672670 important Bug #672670 [src:ocaml-mad] ocaml-mad: FTBFS: Incorrectly thinks it's building as root Severity set to 'important' from 'serious' severity 672671 important Bug #672671 [src:ocaml-mm] ocaml-mm: FTBFS: Incorrectly thinks it's building as root Severity set to 'important' from 'serious' thanks Stopping processing here. Please contact me if you need assistance. -- 670733: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=670733 672666: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=672666 672667: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=672667 672668: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=672668 672669: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=672669 672670: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=672670 672671: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=672671 672673: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=672673 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#672672: Bug#670733: Some remarks
severity 672672 important thanks On 12/06/12 10:19, Mehdi Dogguy wrote: On 11/06/12 18:06, Romain Beauxis wrote: this issue is not even a RC issue because the module clearly does not fail to build in the buildds, it just fails to build with_pbuilder_. As such, I'm lowering the severity of these bugs to important. #672672 too. Regards, -- Mehdi Dogguy مهدي الدڤي http://dogguy.org/ -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed: Re: Bug#670733: Some remarks
Processing commands for cont...@bugs.debian.org: severity 672672 important Bug #672672 [src:ocaml-ogg] ocaml-ogg: FTBFS: Incorrectly thinks it's building as root Severity set to 'important' from 'serious' thanks Stopping processing here. Please contact me if you need assistance. -- 672672: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=672672 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 (with 9 errors): r4922 - in packages/fonts-ipafont: tags tags/00303-9/debian trunk/debian
Processing commands for cont...@bugs.debian.org:
tags 676308 pending
Bug #676308 {Done: Hideki Yamane henr...@debian.org}
[fonts-ipafont-gothic,fonts-ipafont-mincho] fonts-ipafont-{gothic, mincho}:
fails to install: update-alternatives: error: error creating symbolic link
/usr/share/fonts/truetype/*.ttf.dpkg-tmp
Added tag(s) pending.
tags 636138 pending
Failed to alter tags of Bug 636138: Not altering archived bugs; see unarchive.
tags 604622 pending
Failed to alter tags of Bug 604622: Not altering archived bugs; see unarchive.
tags 591664 pending
Failed to alter tags of Bug 591664: Not altering archived bugs; see unarchive.
tags 585956 pending
Failed to alter tags of Bug 585956: Not altering archived bugs; see unarchive.
tags 585956 pending
Failed to alter tags of Bug 585956: Not altering archived bugs; see unarchive.
tags 573713 pending
Failed to alter tags of Bug 573713: Not altering archived bugs; see unarchive.
tags 572731 pending
Failed to alter tags of Bug 572731: Not altering archived bugs; see unarchive.
tags 570067 pending
Failed to alter tags of Bug 570067: Not altering archived bugs; see unarchive.
tags 531190 pending
Failed to alter tags of Bug 531190: Not altering archived bugs; see unarchive.
thanks
Stopping processing here.
Please contact me if you need assistance.
--
531190: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=531190
676308: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=676308
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#677191: emacsen-common: errors while upgrading to wheezy(some time ago) = wheezy(today)
Package: emacsen-common Version: 2.0.3 Severity: serious Hi, an upgrade to current wheezy got stuck with emacsen-common: # dpkg --configure --pending Setting up emacsen-common (2.0.3) ... Install emacsen-common for emacs23 emacsen-common: Handling install of emacsen flavor emacs23 Warning: Lisp directory `/usr/local/share/emacs/23.4/site-lisp' does not exist. Wrote /etc/emacs23/site-start.d/00debian-vars.elc Wrote /usr/share/emacs23/site-lisp/debian-startup.elc Install emacsen-common for xemacs21 emacsen-common: Handling install of emacsen flavor xemacs21 WARNING: Couldn't find obvious defaults for: data-directory mule-lisp-directory lisp-directory Perhaps some directories don't exist, or the XEmacs executable, /usr/bin/xemacs21 is in a strange place?Loading /usr/share/emacs/site-lisp/debian-startup... Loading 00debian... Error while loading 00debian: Symbol's function definition is void: loop Loading 00debian-vars... Loading 50a2ps... Loading 50autoconf... Error while loading 50autoconf: No /usr/local/ prefixed paths in load-path Loading 50cmake... Loading 50cmake-data... Loading 50dictionaries-common... Error while loading 50dictionaries-common: No /usr/local/ prefixed paths in load-path Loading 50emacs-goodies-el... Package emacs-goodies-el not fully installed. Skipping setup. Loading 50lilypond-data... Loading 50psvn... Symbol's function definition is void: batch-byte-compile xemacs exiting . ERROR: install script from emacsen-common package failed dpkg: error processing emacsen-common (--configure): subprocess installed post-installation script returned error exit status 1 Setting up dictionaries-common (1.12.7) ... Install dictionaries-common for emacs23 install/dictionaries-common: Already byte-compiled for emacs23. Skipping ... Install dictionaries-common for xemacs21 install/dictionaries-common: Byte-compiling for emacsen flavour xemacs21 WARNING: Couldn't find obvious defaults for: data-directory mule-lisp-directory lisp-directory Perhaps some directories don't exist, or the XEmacs executable, /usr/bin/xemacs21 is in a strange place?Symbol's function definition is void: batch-byte-compile xemacs exiting . ERROR: install script from dictionaries-common package failed dpkg: error processing dictionaries-common (--configure): subprocess installed post-installation script returned error exit status 1 As that's an experimental system (running testing/sid mix since testing=lenny) and noone needs emacs there, I'm leaving it broken for now and can provide additional information if needed. Andreas # COLUMNS=110 dpkg -l | grep emacs iU emacs 23.4+1-3 The GNU Emacs editor (metapackage) ii emacs-goodies-el 35.2 Miscellaneous add-ons for Emacs iU emacs23 23.4+1-3 The GNU Emacs editor (with GTK+ user interface) iU emacs23-bin-common23.4+1-3 The GNU Emacs editor's shared, architecture dependent file iU emacs23-common23.4+1-3 The GNU Emacs editor's shared, architecture independent in iF emacsen-common2.0.3 Common facilities for all emacsen ii xemacs21 21.4.22-3.2 highly customizable text editor ii xemacs21-basesupport 2009.02.17.dfsg.1-1 Editor and kitchen sink -- compiled elisp support files ii xemacs21-bin 21.4.22-3.2+b1highly customizable text editor -- support binaries iU xemacs21-mule 21.4.22-3.2+b1highly customizable text editor -- Mule binary ii xemacs21-mulesupport 2009.02.17.dfsg.1-1 Editor and kitchen sink -- Mule elisp support files ii xemacs21-support 21.4.22-3.2 highly customizable text editor -- architecture independen -- System Information: Debian Release: wheezy/sid APT prefers testing APT policy: (700, 'testing'), (600, 'unstable'), (130, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 3.2.0-2-amd64 (SMP w/4 CPU cores) Locale: LANG=C, 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#677194: CVE-2012-2672
Package: mojarra Severity: grave Tags: security Please see https://bugzilla.redhat.com/show_bug.cgi?id=CVE-2012-2672 I'm not sure if Debian is affected, please verify. 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#677195: CVE-2012-2673
Package: libgc Severity: grave Tags: security Please see http://kqueue.org/blog/2012/03/05/memory-allocator-security-revisited/ The fixes for libgc are listed in Red Hat bugzilla: https://bugzilla.redhat.com/show_bug.cgi?id=CVE-2012-2673 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#677197: CVE-2012-2677
Package: boost1.49 Severity: grave Tags: security Please see http://kqueue.org/blog/2012/03/05/memory-allocator-security-revisited/ The upstream fix and a test case is available here: https://svn.boost.org/trac/boost/changeset/78326 This likely affects 1.42 from stable as well? 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: mark 677018 serious
Processing commands for cont...@bugs.debian.org: # unfit for release with CVE-2012-2122 present: either should be fixed # in wheezy or package must not be released with wheezy severity 677018 serious Bug #677018 [mysql-5.1] mysql-5.1: CVE-2012-2122: MySQL authentication bypass Severity set to 'serious' from 'important' thanks Stopping processing here. Please contact me if you need assistance. -- 677018: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=677018 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#627235: libpoex-role-sessioninstantiation-perl: Can't locate object method _set_id via package My::Session at /usr/share/perl5/POE/Kernel.pm line 1399.
On Sun, 10 Jun 2012 11:00:34 +0200 Dominique Dumont d...@debian.org wrote: To fix this module one has to know POE internal, Moose, MooseX::Declare, overloading and whatnot. Unless upstream author steps up, (hello Nicholas), I doubt that this module will be fixed in time for Debian 7.0 Hola! Yeah, I am not going to fix this. 1) Don't have the time 2) These modules (POEx) were a thought experiment in a combination of technologies that are shiny 3) Reflex provides a much cleaner way of doing POE + Moose 4) Just this morning I scheduled deletes of all the POEx modules via PAUSE. 5) You guys are crazy for wanting to package up things like this for Debian :) -- Nicholas Perez XMPP/Email: n...@nickandperla.net https://metacpan.org/author/NPEREZ http://github.com/nperez -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#674504: About debian bugs #674504
Hi swift-im maintainers, You have recently uploaded a new package swift-im and introduced a small issue, but unfortunately marked as serious and RC by debian policy bots. So, to quickly solve this issue, we need to rename the binary swift to swift-im And to save your time, please find attached a proposed patch to solve this issue. Don't hesitate, if you need more informations. Best Regards, -- Mehdi Abaakouk sil...@sileht.net commit 32ddb09798e46f115dd7e988dbd7751428824164 Author: Mehdi Abaakouk sil...@sileht.net Date: Tue Jun 12 10:45:42 2012 +0200 binary rename diff --git a/debian/changelog b/debian/changelog index 992a63f..d721600 100644 --- a/debian/changelog +++ b/debian/changelog @@ -1,3 +1,9 @@ +swift-im (2.0~beta1+dev26-2) unstable; urgency=low + + * Rename binary swift to swift-im. Closes: #674504 + + -- Mehdi Abaakouk sil...@sileht.net Tue, 12 Jun 2012 10:15:09 +0200 + swift-im (2.0~beta1+dev26-1) unstable; urgency=low * Initial release. Closes: #631002 diff --git a/debian/patches/rename_binary b/debian/patches/rename_binary new file mode 100644 index 000..08eb452 --- /dev/null +++ b/debian/patches/rename_binary @@ -0,0 +1,13 @@ +Index: swift-im-2.0~beta1+dev26.mod/Swift/resources/swift.desktop +=== +--- swift-im-2.0~beta1+dev26.mod.orig/Swift/resources/swift.desktop 2012-05-22 21:14:29.0 +0200 swift-im-2.0~beta1+dev26.mod/Swift/resources/swift.desktop 2012-06-12 10:32:39.0 +0200 +@@ -8,7 +8,7 @@ + GenericName=Jabber/XMPP Messenger + Comment=Communicate over the Jabber/XMPP network + Icon=swift +-Exec=swift ++Exec=swift-im + Terminal=false + Categories=Network;InstantMessaging;Qt; + diff --git a/debian/patches/series b/debian/patches/series new file mode 100644 index 000..ca55695 --- /dev/null +++ b/debian/patches/series @@ -0,0 +1 @@ +rename_binary diff --git a/debian/rules b/debian/rules index d05e34a..cf4ab70 100755 --- a/debian/rules +++ b/debian/rules @@ -23,6 +23,7 @@ install: build dh_prep dh_installdirs scons $(SCONS_FLAGS) $(SCONS_EXTRA_FLAGS) SWIFT_INSTALLDIR=$(CURDIR)/debian/tmp/usr SWIFTEN_INSTALLDIR=$(CURDIR)/debian/tmp/usr $(CURDIR)/debian/tmp + mv -f $(CURDIR)/debian/tmp/usr/bin/swift $(CURDIR)/debian/tmp/usr/bin/swift-im binary-indep: install binary-arch: install diff --git a/debian/swift-im.1 b/debian/swift-im.1 new file mode 100644 index 000..6626b40 --- /dev/null +++ b/debian/swift-im.1 @@ -0,0 +1,33 @@ +.\ DO NOT MODIFY THIS FILE! It was generated by help2man 1.38.4. +.TH SWIFT 1 June 2011 Swift Swift Manual +.SH NAME +Swift \- swift +.SH SYNOPSIS +.B swift +[\fIOPTIONS\fR]... +.SH DESCRIPTION +Swift is an instant messaging client for the XMPP network. +.SH OPTIONS +.TP +\fB\-\-debug\fR +Turn on debug logging +.TP +\fB\-\-help\fR +Show this help message +.TP +\fB\-\-version\fR +Show version information +.TP +\fB\-\-netbook\-mode\fR +Use netbook mode display (unsupported) +.TP +\fB\-\-no\-tabs\fR +Don't manage chat windows in tabs (unsupported) +.TP +\fB\-\-latency\-debug\fR +Use latency debugging (unsupported) +.HP +\fB\-\-multi\-account\fR arg (=1) Number of accounts to open windows for (unsupported) +.TP +\fB\-\-start\-minimized\fR +Don't show the login/roster window at startup diff --git a/debian/swift-im.install b/debian/swift-im.install index 3144192..9e09ac7 100644 --- a/debian/swift-im.install +++ b/debian/swift-im.install @@ -1,2 +1,2 @@ -usr/bin/swift +usr/bin/swift-im usr/share diff --git a/debian/swift-im.manpages b/debian/swift-im.manpages index f3fb91e..287f11f 100644 --- a/debian/swift-im.manpages +++ b/debian/swift-im.manpages @@ -1 +1 @@ -debian/swift.1 +debian/swift-im.1 diff --git a/debian/swift-im.menu b/debian/swift-im.menu new file mode 100644 index 000..68b621d --- /dev/null +++ b/debian/swift-im.menu @@ -0,0 +1,3 @@ +?package(swift-im):needs=X11 section=Applications/Network/Communication\ + title=Swift IM command=/usr/bin/swift-im\ + icon=/usr/share/pixmaps/swift.xpm diff --git a/debian/swift.1 b/debian/swift.1 deleted file mode 100644 index 6626b40..000 --- a/debian/swift.1 +++ /dev/null @@ -1,33 +0,0 @@ -.\ DO NOT MODIFY THIS FILE! It was generated by help2man 1.38.4. -.TH SWIFT 1 June 2011 Swift Swift Manual -.SH NAME -Swift \- swift -.SH SYNOPSIS -.B swift -[\fIOPTIONS\fR]... -.SH DESCRIPTION -Swift is an instant messaging client for the XMPP network. -.SH OPTIONS -.TP -\fB\-\-debug\fR -Turn on debug logging -.TP -\fB\-\-help\fR -Show this help message -.TP -\fB\-\-version\fR -Show version information -.TP -\fB\-\-netbook\-mode\fR -Use netbook mode display (unsupported) -.TP -\fB\-\-no\-tabs\fR -Don't manage chat windows in tabs (unsupported) -.TP -\fB\-\-latency\-debug\fR -Use latency debugging (unsupported) -.HP -\fB\-\-multi\-account\fR arg (=1) Number of accounts to open windows for (unsupported) -.TP -\fB\-\-start\-minimized\fR -Don't show the login/roster window at startup diff --git
Bug#677199: w3c-dtd-xhtml: please rebuild to fix your copy of #477751
Source: w3c-dtd-xhtml Severity: serious Dear maintainer(s) of w3c-dtd-xhtml, TL;DR: Please upload a new version of this package closing this bug. Problem ~~~ Your package uses the dh_installcatalogs helper from debhelper. This helper added code to the postinst that unconditionally overwrites files in /etc which is a policy violation. The corresponding bug #477751 is now solved in debhelper. Nevertheless the code overwriting files in /etc is still present in a binary package built from this source package, so your package needs a rebuild. Unfortunately the binary package in question is Architecture: all, so a binNMU is not enough. How to solve This bug tracks the progress of the rebuild and should be closed by any upload of this package. Before building, please ensure that your debhelper version is at least 9.20120528 which should be the case if you are running sid. Is my package really/still affected? Any binary package using the dh_installcatalogs helper will add a versioned dependency on sgml-base. If the depended upon version is at least 1.26+nmu2, your package is not affected. In that case, just close this bug. If you have any further questions concerning this issue, please don't hesitate to contact me. Thanks for your help Helmut -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/debian-bugs-rc
Bug#677202: biber packages version 0.9.9+git2012426-3 is beta and requires beta version of biblatex
Package: biber
Version: 0.9.9+git2012426-3
Severity: grave
Justification: renders package unusable
Dear all,
Overview
With the current Sid situation (even close to release) we have a
conflict between the versions of biber and biblatex. Both come from
the same upstream author but are handled by different Debian Teams and
maintainers (Perl and Tex teams respectively).
Fortunately, the situation is easy to fix by either downgrading biber
package version (to the latest official 0.9.9 version) or upgrading
biblatex to the 2.0 beta version. I have tested both scenarios and
both of them work fine.
How to reproduce the bug
In the current Sid scenario take a latex-biber document and perform:
pdflatex file.tex
biber file
pdflatex file.tex
and you will obtain the following error at the 2nd latex invocation:
! Undefined control sequence.
l.22 \sortlist
{entry}{}
(besides you also obtained warnings like this
Use of uninitialized value $llabel in concatenation (.) or string at
/usr/share/perl5/Biber.pm
in the biber invocation).
Further evidence that this is a version conflict
* Using biber --version reports 1.0 (beta), and going to the
upstream site it says that biber 1.0 version requires biblatex
beta version as well.
http://sourceforge.net/projects/biblatex-biber/files/
* The \sortlist undefined control sequence is reported to be a
symptom of this version incompatibility.
http://sourceforge.net/tracker/?func=detailaid=3520829group_id=228270atid=1073792
Possible solutions
--
I propose two scenarios (to be discuseed with upstream author between
the Perl and Tex Debian teams):
A) Beta versions in Sid:
- Package the biblatex 2.0 beta in Sid replacing the 1.7.1 version.
B) Official versions in Sid, beta versions in experimental.
Move this biber version 0.9.9+git2012426-3 to experimental and
downgrade the biber Sid version to 0.9.9 from either sourceforge
or upstream git repository using the v0.9.9 tag.
Optionally package biblatex 2.0beta in experimental.
Regards,
Miguel Telleria
-- System Information:
Debian Release: wheezy/sid
APT prefers unstable
APT policy: (500, 'unstable'), (1, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 3.2.0-2-amd64 (SMP w/4 CPU cores)
Locale: LANG=es_ES.UTF-8, LC_CTYPE=es_ES.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Versions of packages biber depends on:
ii libdata-compare-perl1.22-0.1
ii libdata-dump-perl 1.21-1
ii libdate-simple-perl 3.03.03-1+b3
ii libfile-slurp-unicode-perl 0.7.1-1
ii libipc-run3-perl0.045-1
ii liblist-allutils-perl 0.03-1
ii liblist-moreutils-perl 0.33-1+b1
ii liblog-log4perl-perl1.29-1
ii liblwp-protocol-https-perl 6.03-1
ii libreadonly-perl1.03-3
ii libregexp-common-perl 2011121001-1
ii libtext-bibtex-perl 0.63-1
ii libunicode-collate-perl 0.89-1
ii libwww-perl 6.04-1
ii libxml-libxml-simple-perl 0.91-1
ii libxml-libxslt-perl 1.77-1
ii libxml-writer-string-perl 0.1-1
ii perl5.14.2-11
ii perl-modules [libunicode-collate-perl] 5.14.2-11
Versions of packages biber recommends:
ii biblatex 1.7-1
ii libreadonly-xs-perl 1.04-2+b3
biber 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#676636: [c0e9499] Fix for Bug#676636 committed to git
tags 676636 + pending thanks Hello, The following change has been committed for this bug by Giuseppe Iuculano iucul...@debian.org on Tue, 12 Jun 2012 11:06:24 +0200. The fix will be in the next upload. = Improved sqlite patch. Thanks: Andrew Chant Closes: #676636 = You can check the diff of the fix at: http://anonscm.debian.org/gitweb/?p=pkg-chromium/pkg-chromium.git;a=commitdiff;h=c0e9499 -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed: [c0e9499] Fix for Bug#676636 committed to git
Processing commands for cont...@bugs.debian.org: tags 676636 + pending Bug #676636 [chromium] segfault repeatedly when using the omnibox (in sqlite code?) Added tag(s) pending. thanks Stopping processing here. Please contact me if you need assistance. -- 676636: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=676636 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#675481: docbook-website: please rebuild to fix your copy of #477751
tags 675481 + patch thanks Jakub Wilk kindly pointed out that there is more to do for docbook-website as it explicitly call update-catalog to remove an old left-over catalog. Maybe this call can be removed by some maintainer upload? In the mean time I prepared a .debdiff that upgrades the transitional code. Helmut diff -u docbook-website-2.5.0.0/debian/changelog docbook-website-2.5.0.0/debian/changelog --- docbook-website-2.5.0.0/debian/changelog +++ docbook-website-2.5.0.0/debian/changelog @@ -1,3 +1,10 @@ +docbook-website (2.5.0.0-7.3) unstable; urgency=low + + * Non-maintainer upload. (Closes: #675481) + * Update transitional code in postinst to play well with new sgml-base. + + -- Helmut Grohne hel...@subdivi.de Tue, 12 Jun 2012 11:24:49 +0200 + docbook-website (2.5.0.0-7.2) unstable; urgency=low * NMU. diff -u docbook-website-2.5.0.0/debian/docbook-website.postinst docbook-website-2.5.0.0/debian/docbook-website.postinst --- docbook-website-2.5.0.0/debian/docbook-website.postinst +++ docbook-website-2.5.0.0/debian/docbook-website.postinst @@ -8,9 +8,11 @@ # remove old cruft, just in case if [ $1 = configure ]; then # remove the old catalog -install-sgmlcatalog --quiet --remove docbook-xml-website -update-catalog --quiet --remove --super docbook-xml-website.cat -rm -f /etc/sgml/docbook-xml-website.cat +if [ -f /etc/sgml/docbook-xml-website.cat ]; then + install-sgmlcatalog --quiet --remove docbook-xml-website + rm -f /etc/sgml/docbook-xml-website.cat + dpkg-trigger /etc/sgml +fi # Skip all this if compatibility symlink exists
Processed: Re: docbook-website: please rebuild to fix your copy of #477751
Processing commands for cont...@bugs.debian.org: tags 675481 + patch Bug #675481 [src:docbook-website] docbook-website: please rebuild to fix your copy of #477751 Added tag(s) patch. thanks Stopping processing here. Please contact me if you need assistance. -- 675481: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=675481 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#677018: [debian-mysql] Bug#677018: Bug#677018: more information
Thijs, No we are planning to remove 5.1 before wheezy is released. I just fear the timescale is not soon enough. On 12/06/12 10:02, Thijs Kinkhorst wrote: Hi Nicholas, I seem to recall that this bug is fixed in 5.5.24 which actually is in testing. The migration is not yet complete and probably still has a week or two to go at the least. But does that change your calculations at all. Yes, 5.5 seems fixed in both sid and wheezy. As for 5.1, although our specific builds are not currently vulnerable this can not be guaranteed if they are rebuilt in different circumstances. Will 5.1 be in wheezy or will it be removed soon? If it's going to stay around please upload 5.1.63 a.s.a.p. Cheers, Thijs ___ pkg-mysql-maint mailing list pkg-mysql-ma...@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-mysql-maint -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#676060: scim-thai build failure
Hello Lucas and Theppitak, thank you for this report and the work you've already done to fix it. I'm currently preparing a new scim upload, I was on the road a few days. Regards Rolf -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#677199: w3c-dtd-xhtml: please rebuild to fix your copy of #477751
Helmut, I think I should be able to persuade myself to do an upload of this little package. On 01/06/12 14:52, Helmut Grohne wrote: Source: w3c-dtd-xhtml Severity: serious Dear maintainer(s) of w3c-dtd-xhtml, TL;DR: Please upload a new version of this package closing this bug. Problem ~~~ Your package uses the dh_installcatalogs helper from debhelper. This helper added code to the postinst that unconditionally overwrites files in /etc which is a policy violation. The corresponding bug #477751 is now solved in debhelper. Nevertheless the code overwriting files in /etc is still present in a binary package built from this source package, so your package needs a rebuild. Unfortunately the binary package in question is Architecture: all, so a binNMU is not enough. How to solve This bug tracks the progress of the rebuild and should be closed by any upload of this package. Before building, please ensure that your debhelper version is at least 9.20120528 which should be the case if you are running sid. Is my package really/still affected? Any binary package using the dh_installcatalogs helper will add a versioned dependency on sgml-base. If the depended upon version is at least 1.26+nmu2, your package is not affected. In that case, just close this bug. If you have any further questions concerning this issue, please don't hesitate to contact me. Thanks for your help Helmut -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed: Re: sgmltools-lite: do not call update-catalog
Processing commands for cont...@bugs.debian.org: tags 674914 + patch Bug #674914 [sgmltools-lite] sgmltools-lite: do not call update-catalog Added tag(s) patch. severity 674914 serious Bug #674914 [sgmltools-lite] sgmltools-lite: do not call update-catalog Severity set to 'serious' from 'important' thanks Stopping processing here. Please contact me if you need assistance. -- 674914: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=674914 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#669495: marked as done (nilfs-tools: FTBFS: ld: final link failed: Bad value)
Your message dated Tue, 12 Jun 2012 09:40:51 + with message-id e1senal-0008p6...@franck.debian.org and subject line Bug#669495: fixed in nilfs-tools 2.1.2-2 has caused the Debian Bug report #669495, regarding nilfs-tools: FTBFS: ld: final link failed: Bad value 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.) -- 669495: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=669495 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Source: nilfs-tools Version: 2.1.1-1 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: /usr/bin/ld: .libs/libnilfs_la-nilfs.o: relocation R_X86_64_PC32 against symbol `nilfs_get_cpinfo' can not be used when making a shared object; recompile with -fPIC /usr/bin/ld: final link failed: Bad value collect2: ld returned 1 exit status The full build log is available from: http://people.debian.org/~lucas/logs/2012/04/19/nilfs-tools_2.1.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--- ---BeginMessage--- Source: nilfs-tools Source-Version: 2.1.2-2 We believe that the bug you reported is fixed in the latest version of nilfs-tools, which is due to be installed in the Debian FTP archive: nilfs-tools-dbg_2.1.2-2_i386.deb to main/n/nilfs-tools/nilfs-tools-dbg_2.1.2-2_i386.deb nilfs-tools_2.1.2-2.debian.tar.gz to main/n/nilfs-tools/nilfs-tools_2.1.2-2.debian.tar.gz nilfs-tools_2.1.2-2.dsc to main/n/nilfs-tools/nilfs-tools_2.1.2-2.dsc nilfs-tools_2.1.2-2_i386.deb to main/n/nilfs-tools/nilfs-tools_2.1.2-2_i386.deb A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 669...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Daniel Baumann daniel.baum...@progress-technologies.net (supplier of updated nilfs-tools package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.8 Date: Tue, 12 Jun 2012 11:20:24 +0200 Source: nilfs-tools Binary: nilfs-tools nilfs-tools-dbg Architecture: source i386 Version: 2.1.2-2 Distribution: unstable Urgency: low Maintainer: Daniel Baumann daniel.baum...@progress-technologies.net Changed-By: Daniel Baumann daniel.baum...@progress-technologies.net Description: nilfs-tools - Continuous Snapshotting Log-structured Filesystem nilfs-tools-dbg - Continuous Snapshotting Log-structured Filesystem (debug) Closes: 669495 Changes: nilfs-tools (2.1.2-2) unstable; urgency=low . * Disabling hardening flags, doesn't build reliably everywhere yet (Closes: #669495). Checksums-Sha1: 969c61b96f8138ebee249b7bd96d6ac3a8d37695 1198 nilfs-tools_2.1.2-2.dsc f10aec76ef025f9a927ed5b0ad8facafa8ae6f82 4658 nilfs-tools_2.1.2-2.debian.tar.gz cf2cc82d6fb22136a5aa0716ce2d980d3bb49a6a 158604 nilfs-tools_2.1.2-2_i386.deb ff7726f86c9cb088acb7fe2c6ffed23a681b0e47 242374 nilfs-tools-dbg_2.1.2-2_i386.deb Checksums-Sha256: ac85b41c2742615039997cdfd4c4ce35964ee6581d1d8e5b388cc03c5bf6e4fa 1198 nilfs-tools_2.1.2-2.dsc 01ba118a0728fd842407523d581e1e85a57830ba19e467b75ec57f85809126c1 4658 nilfs-tools_2.1.2-2.debian.tar.gz 9606ed041a6662118d8d7e8e2773133cef5bb1bc3e945be799ba0c9167d5f78e 158604 nilfs-tools_2.1.2-2_i386.deb c9711df45afaa710beec16792792c69a5069b65b788e266f885ddec153a22c20 242374 nilfs-tools-dbg_2.1.2-2_i386.deb Files: 9398312585abc6aba19b9feb39d4dc61 1198 admin optional nilfs-tools_2.1.2-2.dsc 55a373cc4ac8abce1056f03d27c8d96c 4658 admin optional nilfs-tools_2.1.2-2.debian.tar.gz b5b52484f59606b393cc41f9e66b7982 158604 admin optional nilfs-tools_2.1.2-2_i386.deb 2d508feffe8f798b95455c9b31efe3ba 242374 debug extra nilfs-tools-dbg_2.1.2-2_i386.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.10 (GNU/Linux) iEYEARECAAYFAk/XCqoACgkQ+C5cwEsrK57E/ACg2KbTW8NTyE5OxMuJjMCnz1Xg yJcAoJQKZBxVKYC0gLQx8irGj2DkYDcN =eC+q -END PGP SIGNATURE-
Bug#675488: sgml-data: do not call update-catalog
tags 674913 + patch
tags 675488 + patch
thanks
On Mon, May 28, 2012 at 05:06:18PM +0200, Helmut Grohne wrote:
Your package calls update-catalog on /etc/sgml/$PACKAGE.cat. The latter
file will transition to a conffile, so changing that file induces
questions to the user. Please remove the old and no longer needed call
to update-catalog.
I attached a patch for both issues.
Helmut
diff -Nru sgml-data-2.0.6/debian/changelog sgml-data-2.0.6+nmu1/debian/changelog
--- sgml-data-2.0.6/debian/changelog2011-05-29 18:04:05.0 +0200
+++ sgml-data-2.0.6+nmu1/debian/changelog 2012-06-12 11:47:46.0
+0200
@@ -1,3 +1,11 @@
+sgml-data (2.0.6+nmu1) unstable; urgency=low
+
+ * Non-maintainer upload. (Closes: #675488)
+ * Remove calls to update-catalog from postinst. They are noops with the new
+sgml-base. (Closes: #674913)
+
+ -- Helmut Grohne hel...@subdivi.de Tue, 12 Jun 2012 11:46:23 +0200
+
sgml-data (2.0.6) unstable; urgency=low
* QA upload.
diff -Nru sgml-data-2.0.6/debian/postinst sgml-data-2.0.6+nmu1/debian/postinst
--- sgml-data-2.0.6/debian/postinst 2004-02-15 18:34:00.0 +0100
+++ sgml-data-2.0.6+nmu1/debian/postinst2012-06-12 11:44:47.0
+0200
@@ -1,16 +1,8 @@
#!/bin/sh
# sgml-data postinst
-# jobs: remove old catalog entry in transitional.cat
set -e
-PACKAGE=sgml-data
-
-if [ $1 = configure ]; then
-# remove legacy SGML catalog
-update-catalog --quiet --remove /etc/sgml/${PACKAGE}.cat
/usr/share/sgml/html/dtd/xml/1.0/xhtml.soc
-fi
-
# automatically generated debhelper commands
#DEBHELPER#
Processed: Re: sgml-data: do not call update-catalog
Processing commands for cont...@bugs.debian.org: tags 674913 + patch Bug #674913 [sgml-data] sgml-data: do not call update-catalog Added tag(s) patch. tags 675488 + patch Bug #675488 [src:sgml-data] sgml-data: please rebuild to fix your copy of #477751 Added tag(s) patch. thanks Stopping processing here. Please contact me if you need assistance. -- 674913: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=674913 675488: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=675488 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#676638: nova-objectstore: Upgrade to version 2012.1-5 Failed
The output: # apt-get install nova-objectstore Reading package lists... Done Building dependency tree Reading state information... Done The following NEW packages will be installed: nova-objectstore 0 upgraded, 1 newly installed, 0 to remove and 279 not upgraded. Need to get 0 B/12.9 kB of archives. After this operation, 65.5 kB of additional disk space will be used. Selecting previously unselected package nova-objectstore. (Reading database ... 63680 files and directories currently installed.) Unpacking nova-objectstore (from .../nova-objectstore_2012.1-5_all.deb) ... Processing triggers for man-db ... Setting up nova-objectstore (2012.1-5) ... Value of NOVA_ENABLE in must be either 'true' or 'false'; ... failed! not starting nova-objectstore daemon. ... failed! invoke-rc.d: initscript nova-objectstore, action start failed. dpkg: error processing nova-objectstore (--configure): subprocess installed post-installation script returned error exit status 1 configured to not write apport reports Errors were encountered while processing: nova-objectstore E: Sub-process /usr/bin/dpkg returned an error code (1) There are errors in /etc/init.d/nova-objectstore The diff to get it working --- nova-objectstore.orig 2012-06-12 11:57:52.0 +0200 +++ nova-objectstore2012-06-12 11:59:12.0 +0200 @@ -21,7 +21,7 @@ SCRIPTNAME=/etc/init.d/$NAME NOVA_USER=nova LOCK_DIR=/var/lock/nova/ -EFAULTS_FILE=/etc/default/nova +DEFAULTS_FILE=/etc/default/nova-common # Exit if the package is not installed [ -x $DAEMON ] || exit 0 -- François Charlier Software Engineer // eNovance labs http://labs.enovance.com // ✉ francois.charl...@enovance.com ☎ +33 1 49 70 99 81 -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#676977: marked as done (ruby-redcarpet: FTBFS: test suite can't find nokogiri)
Your message dated Tue, 12 Jun 2012 10:03:38 + with message-id e1senwo-0005dd...@franck.debian.org and subject line Bug#676977: fixed in ruby-redcarpet 2.1.1-2 has caused the Debian Bug report #676977, regarding ruby-redcarpet: FTBFS: test suite can't find nokogiri 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.) -- 676977: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=676977 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Source: ruby-redcarpet Version: 2.1.1-1 Severity: serious Justification: fails to build from source Builds of ruby-redcarpet in minimal environments, such as the autobuilders, have been failing due to an undeclared build dependency on ruby-nokogiri: ./test/redcarpet_test.rb:12:in `require': no such file to load -- nokogiri (LoadError) from ./test/redcarpet_test.rb:12 from -e:1:in `require' from -e:1 from -e:1:in `each' from -e:1 ERROR: Test ruby1.8 failed. Exiting. dh_auto_install: dh_ruby --install /.../ruby-redcarpet-2.1.1/debian/ruby-redcarpet returned exit code 1 make: *** [binary-arch] Error 1 Please add ruby-nokogiri to ruby-redcarpet's Build-Depends (and Depends if appropriate), and check with pbuilder or the like that nothing else is missing. Thanks! ---End Message--- ---BeginMessage--- Source: ruby-redcarpet Source-Version: 2.1.1-2 We believe that the bug you reported is fixed in the latest version of ruby-redcarpet, which is due to be installed in the Debian FTP archive: ruby-redcarpet_2.1.1-2.debian.tar.gz to main/r/ruby-redcarpet/ruby-redcarpet_2.1.1-2.debian.tar.gz ruby-redcarpet_2.1.1-2.dsc to main/r/ruby-redcarpet/ruby-redcarpet_2.1.1-2.dsc ruby-redcarpet_2.1.1-2_amd64.deb to main/r/ruby-redcarpet/ruby-redcarpet_2.1.1-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 676...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Youhei SASAKI uwab...@gfd-dennou.org (supplier of updated ruby-redcarpet 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: Tue, 12 Jun 2012 16:26:16 +0900 Source: ruby-redcarpet Binary: ruby-redcarpet Architecture: source amd64 Version: 2.1.1-2 Distribution: unstable Urgency: low Maintainer: Debian Ruby Extras Maintainers pkg-ruby-extras-maintain...@lists.alioth.debian.org Changed-By: Youhei SASAKI uwab...@gfd-dennou.org Description: ruby-redcarpet - Fast, safe and extensible Markdown to (X)HTML parser for Ruby Closes: 676977 677147 Changes: ruby-redcarpet (2.1.1-2) unstable; urgency=low . * Fix FTBFS: (Closes: #677147, #676977) - Add Build-Depends: ruby-nokogiri Thanks to Peter Green, Aaron M. Ucko Checksums-Sha1: 837ec76c566a75cedd9000634e27e79173c2be92 2134 ruby-redcarpet_2.1.1-2.dsc 116ef93a2ef41f3cf8e954b94ece7ef6ee575e8b 43165 ruby-redcarpet_2.1.1.orig.tar.gz 92b950b846aea24d0dd86aeb1797d9f37af6b083 2348 ruby-redcarpet_2.1.1-2.debian.tar.gz 36e52798deeabc38b2bbf6c54c0b04ca8cdce50b 76130 ruby-redcarpet_2.1.1-2_amd64.deb Checksums-Sha256: ce00776176630df2d5c6163efb44d9a446bd551eb49055f544d38e621a77788f 2134 ruby-redcarpet_2.1.1-2.dsc 8fb2e26714e05991b3d80fc1ca51153ae3b2fa5e09375720cde0396635211212 43165 ruby-redcarpet_2.1.1.orig.tar.gz adb71e4f0453827dd52f27e3328fb75e00df780597c2f08177fd0382deaabe71 2348 ruby-redcarpet_2.1.1-2.debian.tar.gz 3990843c4bd1646a7b7f60775839410b463b40ac40a1adcb7042fa7480cc6da5 76130 ruby-redcarpet_2.1.1-2_amd64.deb Files: ce1a46c9694850bb88c4fbcb534fe5e0 2134 ruby optional ruby-redcarpet_2.1.1-2.dsc 42048a3861c529a8998bfe64e7b5f693 43165 ruby optional ruby-redcarpet_2.1.1.orig.tar.gz ab415409d6f3c4d63fcdb4dadd9cb6cb 2348 ruby optional ruby-redcarpet_2.1.1-2.debian.tar.gz b94644cbfba75f1ef558d5e67d267200 76130 ruby optional ruby-redcarpet_2.1.1-2_amd64.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.12 (GNU/Linux) iQIcBAEBCgAGBQJP1w0kAAoJEJOU81SJHX4HCRAP/3FaJ3vfDjeF7PFaoyRVZl+k RIhIroLCykx5cxXt1aiTHoy2GEScFozDYIZtdsotSckTc4IXeLO0/v56Cy024V+F KJRuULRpGqHa4xnIwDgTfpZsQJUQWcOpqul/PHXXmHESAQGj4THV3+UbmZ4eJiQT P48w14CesVQPy0STKhpVk/icyg7lRs0VXWye/yTsNRYJWBwct/41Ai+1zJOWGfPm QgXKARPGNLcwxmGCwa11OkVnFY18MJBWGZXVRAbnjEEVeaoEgPyhk1O+b8TNOfrQ
Bug#677147: marked as done (ruby-redcarpet FTBFS ./test/redcarpet_test.rb:12:in `require': no such file to load -- nokogiri (LoadError))
Your message dated Tue, 12 Jun 2012 10:03:38 + with message-id e1senwo-0005dk...@franck.debian.org and subject line Bug#677147: fixed in ruby-redcarpet 2.1.1-2 has caused the Debian Bug report #677147, regarding ruby-redcarpet FTBFS ./test/redcarpet_test.rb:12:in `require': no such file to load -- nokogiri (LoadError) 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.) -- 677147: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=677147 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- package: ruby-redcarpet severity: serious version: 2.1.1-1 tags: patch ruby-redcarpet failed to build on all autobuilders that had tried to build it at the time of writing and also failed in my amd64 pbuilder. Rewriting shebang line of /build/buildd-ruby-redcarpet_2.1.1-1-armel-YKFnOe/ruby-redcarpet-2.1.1/debian/ruby-redcarpet/usr/bin/redcarpet /usr/bin/ruby1.8 -I/usr/lib/ruby/vendor_ruby /usr/lib/ruby/vendor_ruby/gem2deb/test_runner.rb ./test/redcarpet_test.rb:12:in `require': no such file to load -- nokogiri (LoadError) from ./test/redcarpet_test.rb:12 from -e:1:in `require' from -e:1 from -e:1:in `each' from -e:1 ERROR: Test ruby1.8 failed. Exiting. dh_auto_install: dh_ruby --install /build/buildd-ruby-redcarpet_2.1.1-1-armel-YKFnOe/ruby-redcarpet-2.1.1/debian/ruby-redcarpet returned exit code 1 The package builds successfully if ruby-nokogiri is installed, please add it to the build-depends or otherwise fix this bug. ---End Message--- ---BeginMessage--- Source: ruby-redcarpet Source-Version: 2.1.1-2 We believe that the bug you reported is fixed in the latest version of ruby-redcarpet, which is due to be installed in the Debian FTP archive: ruby-redcarpet_2.1.1-2.debian.tar.gz to main/r/ruby-redcarpet/ruby-redcarpet_2.1.1-2.debian.tar.gz ruby-redcarpet_2.1.1-2.dsc to main/r/ruby-redcarpet/ruby-redcarpet_2.1.1-2.dsc ruby-redcarpet_2.1.1-2_amd64.deb to main/r/ruby-redcarpet/ruby-redcarpet_2.1.1-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 677...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Youhei SASAKI uwab...@gfd-dennou.org (supplier of updated ruby-redcarpet 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: Tue, 12 Jun 2012 16:26:16 +0900 Source: ruby-redcarpet Binary: ruby-redcarpet Architecture: source amd64 Version: 2.1.1-2 Distribution: unstable Urgency: low Maintainer: Debian Ruby Extras Maintainers pkg-ruby-extras-maintain...@lists.alioth.debian.org Changed-By: Youhei SASAKI uwab...@gfd-dennou.org Description: ruby-redcarpet - Fast, safe and extensible Markdown to (X)HTML parser for Ruby Closes: 676977 677147 Changes: ruby-redcarpet (2.1.1-2) unstable; urgency=low . * Fix FTBFS: (Closes: #677147, #676977) - Add Build-Depends: ruby-nokogiri Thanks to Peter Green, Aaron M. Ucko Checksums-Sha1: 837ec76c566a75cedd9000634e27e79173c2be92 2134 ruby-redcarpet_2.1.1-2.dsc 116ef93a2ef41f3cf8e954b94ece7ef6ee575e8b 43165 ruby-redcarpet_2.1.1.orig.tar.gz 92b950b846aea24d0dd86aeb1797d9f37af6b083 2348 ruby-redcarpet_2.1.1-2.debian.tar.gz 36e52798deeabc38b2bbf6c54c0b04ca8cdce50b 76130 ruby-redcarpet_2.1.1-2_amd64.deb Checksums-Sha256: ce00776176630df2d5c6163efb44d9a446bd551eb49055f544d38e621a77788f 2134 ruby-redcarpet_2.1.1-2.dsc 8fb2e26714e05991b3d80fc1ca51153ae3b2fa5e09375720cde0396635211212 43165 ruby-redcarpet_2.1.1.orig.tar.gz adb71e4f0453827dd52f27e3328fb75e00df780597c2f08177fd0382deaabe71 2348 ruby-redcarpet_2.1.1-2.debian.tar.gz 3990843c4bd1646a7b7f60775839410b463b40ac40a1adcb7042fa7480cc6da5 76130 ruby-redcarpet_2.1.1-2_amd64.deb Files: ce1a46c9694850bb88c4fbcb534fe5e0 2134 ruby optional ruby-redcarpet_2.1.1-2.dsc 42048a3861c529a8998bfe64e7b5f693 43165 ruby optional ruby-redcarpet_2.1.1.orig.tar.gz ab415409d6f3c4d63fcdb4dadd9cb6cb 2348 ruby optional ruby-redcarpet_2.1.1-2.debian.tar.gz b94644cbfba75f1ef558d5e67d267200 76130 ruby optional ruby-redcarpet_2.1.1-2_amd64.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.12 (GNU/Linux) iQIcBAEBCgAGBQJP1w0kAAoJEJOU81SJHX4HCRAP/3FaJ3vfDjeF7PFaoyRVZl+k
Processed: Re: xml2rfc: do not call update-catalog
Processing commands for cont...@bugs.debian.org: severity 674911 serious Bug #674911 [xml2rfc] xml2rfc: do not call update-catalog Severity set to 'serious' from 'important' thanks Stopping processing here. Please contact me if you need assistance. -- 674911: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=674911 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#666620: marked as done (muse-el: FTBFS: install: cannot stat `examples/QuickStart.pdf': No such file or directory)
Your message dated Tue, 12 Jun 2012 12:11:51 +0200 with message-id 871ulkltzs@zelenka.enovance.com and subject line Closing has caused the Debian Bug report #20, regarding muse-el: FTBFS: install: cannot stat `examples/QuickStart.pdf': 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.) -- 20: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=20 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Source: muse-el Version: 3.20-2 Severity: serious Tags: wheezy sid User: debian...@lists.debian.org Usertags: qa-ftbfs-20120331 qa-ftbfs Justification: FTBFS on amd64 Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part: fakeroot debian/rules binary dh_testdir dh_testroot dh_clean dh_installdirs # Add here commands to install the package into debian/muse. # /usr/bin/make install DESTDIR=/«PKGBUILDDIR»/debian/muse install -m 0644 lisp/*.el debian/muse-el/usr/share/emacs/site-lisp/muse-el install -m 0644 experimental/*.el debian/muse-el/usr/share/emacs/site-lisp/muse-el/experimental install -m 0644 contrib/*.el debian/muse-el/usr/share/emacs/site-lisp/muse-el/contrib install -m 0644 contrib/blosxom/* debian/muse-el/usr/share/doc/muse-el/contrib/blosxom install -m 0644 contrib/pyblosxom/* debian/muse-el/usr/share/doc/muse-el/contrib/pyblosxom # Examples and miscellanea install -m 0644 etc/muse.rnc debian/muse-el/usr/share/doc/muse-el/examples install -m 0644 examples/QuickStart.muse debian/muse-el/usr/share/doc/muse-el/examples install -m 0644 examples/publish-project debian/muse-el/usr/share/doc/muse-el/examples # Other documentation install -m 0644 AUTHORS debian/muse-el/usr/share/doc/muse-el/AUTHORS install -m 0644 NEWS debian/muse-el/usr/share/doc/muse-el/NEWS install -m 0644 README debian/muse-el/usr/share/doc/muse-el/README install -m 0644 etc/emacs-wiki-migration.txt debian/muse-el/usr/share/doc/muse-el/emacs-wiki-migration.txt install -m 0644 examples/QuickStart.html debian/muse-el/usr/share/doc/muse-el/QuickStart.html install -m 0644 examples/QuickStart.pdf debian/muse-el/usr/share/doc/muse-el/QuickStart.pdf install: cannot stat `examples/QuickStart.pdf': No such file or directory make: *** [install] Error 1 The full build log is available from: http://people.debian.org/~lucas/logs/2012/03/31/muse-el_3.20-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--- ---BeginMessage--- I cannot reproduce it neither, so closing. -- Julien pgphCmqMOm4Pt.pgp Description: PGP signature ---End Message---
Bug#674914: sgmltools-lite: do not call update-catalog
Sorry I forgot to attach the patch again. Helmut diff -u sgmltools-lite-3.0.3.0.cvs.20010909/debian/postinst sgmltools-lite-3.0.3.0.cvs.20010909/debian/postinst --- sgmltools-lite-3.0.3.0.cvs.20010909/debian/postinst +++ sgmltools-lite-3.0.3.0.cvs.20010909/debian/postinst @@ -13,13 +13,6 @@ case $1 in configure) - # for old sgmltools-2 bug - if [ -x /usr/sbin/update-catalog ] - then - /usr/sbin/update-catalog --quiet --remove --super \ - /usr/lib/sgml/stylesheet/dsssl/sgmltools/sgmltools.cat - fi - # sgmltools-lite does not need to install custom catalog ;; diff -u sgmltools-lite-3.0.3.0.cvs.20010909/debian/changelog sgmltools-lite-3.0.3.0.cvs.20010909/debian/changelog --- sgmltools-lite-3.0.3.0.cvs.20010909/debian/changelog +++ sgmltools-lite-3.0.3.0.cvs.20010909/debian/changelog @@ -1,3 +1,11 @@ +sgmltools-lite (3.0.3.0.cvs.20010909-15.2) unstable; urgency=low + + * Non-maintainer upload. + * Remove transitional call to update-catalog from postinst. The call is a +noop since the new sgml-base version. (Closes: #674914) + + -- Helmut Grohne hel...@subdivi.de Tue, 12 Jun 2012 11:39:39 +0200 + sgmltools-lite (3.0.3.0.cvs.20010909-15.1) unstable; urgency=low * Non-maintainer upload.
Processed: Re: Bug#677206: xserver-xorg-video-intel: Segfault with missing driver name in xorg.conf
Processing commands for cont...@bugs.debian.org: severity 677206 serious Bug #677206 [xserver-xorg-video-intel] xserver-xorg-video-intel: Segfault with missing driver name in xorg.conf Severity set to 'serious' from 'normal' thanks Stopping processing here. Please contact me if you need assistance. -- 677206: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=677206 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#656618: marked as done (open-vm-tools: FTBFS w/ Linux 3.2)
Your message dated Tue, 12 Jun 2012 10:50:42 + with message-id e1seogm-7m...@franck.debian.org and subject line Bug#656618: fixed in open-vm-tools 2:8.8.0+2012.03.13-651368-1 has caused the Debian Bug report #656618, regarding open-vm-tools: FTBFS w/ Linux 3.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.) -- 656618: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=656618 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: open-vm-tools Version: 2:8.8.0+2011.12.20-562307-1 Severity: grave Tags: upstream Justification: renders package unusable Dear Maintainer, Today I installed the Linux 3.2 kernel, rebooted into it and tried to compile the open-vm-tools for that kernel. The build failed, the relevant error message is: CC [M] /usr/src/modules/open-vm/modules/linux/vmhgfs/fsutil.o /usr/src/modules/open-vm/modules/linux/vmhgfs/fsutil.c: In function ‘HgfsChangeFileAttributes’: /usr/src/modules/open-vm/modules/linux/vmhgfs/fsutil.c:610:4: error: assignment of read-only member ‘i_nlink’ full build log is attached. The versions of the open-vm-* packages are a little bit out of sync: sid:/usr/src/modules/open-vm# dpkg -l open-vm-tools open-vm-source Desired=Unknown/Install/Remove/Purge/Hold |Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend |/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad) ||/ Name Version Description +++-=-=-== ii open-vm-source2:8.8.0+2011.09.23-491607-1 Source for VMware guest systems driver ii open-vm-tools 2:8.8.0+2011.12.20-562307-1 tools and components for VMware guest systems (CLI tools) When looking at http://packages.debian.org/open-vm-source only version 1:8.4.2-261024-1 is listed. Maybe updating open-vm-source to the latest version would solve the problem, but it doesn't seem to be packaged. Regards, Hilmar -- System Information: Debian Release: wheezy/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: i386 (i686) Kernel: Linux 3.2.0-1-686-pae (SMP w/1 CPU core) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) (ignored: LC_ALL set to en_GB.UTF-8) Shell: /bin/sh linked to /bin/bash Versions of packages open-vm-tools depends on: ii libc6 2.13-24 ii libdumbnet1 1.12-3.1 ii libfuse2 2.8.6-4 ii libgcc1 1:4.6.2-11 ii libglib2.0-0 2.30.2-5 ii libicu48 4.8.1.1-2 ii libstdc++64.6.2-11 ii procps1:3.3.2-2 Versions of packages open-vm-tools recommends: ii ethtool 1:3.1-1 ii open-vm-dkms none ii zerofree 1.0.1-2 Versions of packages open-vm-tools suggests: pn open-vm-toolbox none -- Configuration Files: /etc/vmware-tools/tools.conf changed: -- no debconf information open-vm-source.buildlog.3.2.0-1-686-pae.1327060210.bz2 Description: BZip2 compressed data ---End Message--- ---BeginMessage--- Source: open-vm-tools Source-Version: 2:8.8.0+2012.03.13-651368-1 We believe that the bug you reported is fixed in the latest version of open-vm-tools, which is due to be installed in the Debian FTP archive: open-vm-dkms_8.8.0+2012.03.13-651368-1_all.deb to main/o/open-vm-tools/open-vm-dkms_8.8.0+2012.03.13-651368-1_all.deb open-vm-toolbox_8.8.0+2012.03.13-651368-1_i386.deb to main/o/open-vm-tools/open-vm-toolbox_8.8.0+2012.03.13-651368-1_i386.deb open-vm-tools-dbg_8.8.0+2012.03.13-651368-1_i386.deb to main/o/open-vm-tools/open-vm-tools-dbg_8.8.0+2012.03.13-651368-1_i386.deb open-vm-tools-dev_8.8.0+2012.03.13-651368-1_all.deb to main/o/open-vm-tools/open-vm-tools-dev_8.8.0+2012.03.13-651368-1_all.deb open-vm-tools_8.8.0+2012.03.13-651368-1.debian.tar.gz to main/o/open-vm-tools/open-vm-tools_8.8.0+2012.03.13-651368-1.debian.tar.gz open-vm-tools_8.8.0+2012.03.13-651368-1.dsc to main/o/open-vm-tools/open-vm-tools_8.8.0+2012.03.13-651368-1.dsc open-vm-tools_8.8.0+2012.03.13-651368-1_i386.deb to main/o/open-vm-tools/open-vm-tools_8.8.0+2012.03.13-651368-1_i386.deb open-vm-tools_8.8.0+2012.03.13-651368.orig.tar.gz to main/o/open-vm-tools/open-vm-tools_8.8.0+2012.03.13-651368.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 656...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance
Bug#659595: marked as done (open-vm-tools build-depends on obsolete libproc-dev)
Your message dated Tue, 12 Jun 2012 10:50:42 + with message-id e1seogm-7q...@franck.debian.org and subject line Bug#659595: fixed in open-vm-tools 2:8.8.0+2012.03.13-651368-1 has caused the Debian Bug report #659595, regarding open-vm-tools build-depends on obsolete libproc-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.) -- 659595: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=659595 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Source: open-vm-tools Version: 2:8.8.0+2011.12.20-562307-1 Severity: serious libproc-dev is no longer built on top of procps source package, and is planned to be decrufted from the archive. Please replace libproc-dev build-dependency with libprocps0-dev. -- System Information: Debian Release: wheezy/sid APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 3.2.0-1-amd64 (SMP w/8 CPU cores) Locale: LANG=it_IT.UTF-8, LC_CTYPE=it_IT.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash ---End Message--- ---BeginMessage--- Source: open-vm-tools Source-Version: 2:8.8.0+2012.03.13-651368-1 We believe that the bug you reported is fixed in the latest version of open-vm-tools, which is due to be installed in the Debian FTP archive: open-vm-dkms_8.8.0+2012.03.13-651368-1_all.deb to main/o/open-vm-tools/open-vm-dkms_8.8.0+2012.03.13-651368-1_all.deb open-vm-toolbox_8.8.0+2012.03.13-651368-1_i386.deb to main/o/open-vm-tools/open-vm-toolbox_8.8.0+2012.03.13-651368-1_i386.deb open-vm-tools-dbg_8.8.0+2012.03.13-651368-1_i386.deb to main/o/open-vm-tools/open-vm-tools-dbg_8.8.0+2012.03.13-651368-1_i386.deb open-vm-tools-dev_8.8.0+2012.03.13-651368-1_all.deb to main/o/open-vm-tools/open-vm-tools-dev_8.8.0+2012.03.13-651368-1_all.deb open-vm-tools_8.8.0+2012.03.13-651368-1.debian.tar.gz to main/o/open-vm-tools/open-vm-tools_8.8.0+2012.03.13-651368-1.debian.tar.gz open-vm-tools_8.8.0+2012.03.13-651368-1.dsc to main/o/open-vm-tools/open-vm-tools_8.8.0+2012.03.13-651368-1.dsc open-vm-tools_8.8.0+2012.03.13-651368-1_i386.deb to main/o/open-vm-tools/open-vm-tools_8.8.0+2012.03.13-651368-1_i386.deb open-vm-tools_8.8.0+2012.03.13-651368.orig.tar.gz to main/o/open-vm-tools/open-vm-tools_8.8.0+2012.03.13-651368.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 659...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Daniel Baumann daniel.baum...@progress-linux.org (supplier of updated open-vm-tools package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.8 Date: Tue, 20 Mar 2012 07:52:18 +0100 Source: open-vm-tools Binary: open-vm-tools open-vm-toolbox open-vm-tools-dev open-vm-tools-dbg open-vm-dkms Architecture: source i386 all Version: 2:8.8.0+2012.03.13-651368-1 Distribution: unstable Urgency: low Maintainer: Daniel Baumann daniel.baum...@progress-technologies.net Changed-By: Daniel Baumann daniel.baum...@progress-linux.org Description: open-vm-dkms - Source for VMware guest systems driver (DKMS) open-vm-toolbox - tools and components for VMware guest systems (GUI tools) open-vm-tools - tools and components for VMware guest systems (CLI tools) open-vm-tools-dbg - tools and components for VMware guest systems (debug) open-vm-tools-dev - tools and components for VMware guest systems (development) Closes: 651779 654249 656618 659595 Changes: open-vm-tools (2:8.8.0+2012.03.13-651368-1) unstable; urgency=low . [ Michael Dorrington ] * Changed Build-Depends to libprocps0-dev to fix libproc-dev removal (Closes: #659595). . [ Daniel Baumann ] * Merging upstream version 8.8.0+2012.03.13-651368: - compatible with linux 3.2 and 3.3 (Closes: #656618). * Updating to debhelper version 9. * Updating to standards version 3.9.3. * Updating copyright file machine-readable format version 1.0. * Building with debhelper dkms support (Closes: #651779, #654249). * Updating procps patch for newest procps library name. * Building without multiarch paths for now. Checksums-Sha1: 335e76705113d4b276981239cde70560ce1d97da 1753 open-vm-tools_8.8.0+2012.03.13-651368-1.dsc 190f843d63585c128f2a9f3d3a912ac6cd6df462 3551741
Bug#635548: marked as done (CVE-2011-2716 udhcpc insufficient checking of DHCP options)
Your message dated Tue, 12 Jun 2012 11:02:26 + with message-id e1seori-00036l...@franck.debian.org and subject line Bug#635548: fixed in busybox 1:1.20.0-3 has caused the Debian Bug report #635548, regarding CVE-2011-2716 udhcpc insufficient checking of DHCP options 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.) -- 635548: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=635548 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: udhcpc Severity: grave Tags: security Dear Busybox maintainers, it was discovered that busybox's udhcpc is also affected by https://www.isc.org/software/dhcp/advisories/cve-2011-0997 This has been assigned CVE-2011-2716. Cheers, Moritz -- System Information: Debian Release: wheezy/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: amd64 (x86_64) Kernel: Linux 3.0.0-1-amd64 (SMP w/2 CPU cores) Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash ---End Message--- ---BeginMessage--- Source: busybox Source-Version: 1:1.20.0-3 We believe that the bug you reported is fixed in the latest version of busybox, which is due to be installed in the Debian FTP archive: busybox-static_1.20.0-3_i386.deb to main/b/busybox/busybox-static_1.20.0-3_i386.deb busybox-syslogd_1.20.0-3_all.deb to main/b/busybox/busybox-syslogd_1.20.0-3_all.deb busybox-udeb_1.20.0-3_i386.udeb to main/b/busybox/busybox-udeb_1.20.0-3_i386.udeb busybox_1.20.0-3.debian.tar.gz to main/b/busybox/busybox_1.20.0-3.debian.tar.gz busybox_1.20.0-3.dsc to main/b/busybox/busybox_1.20.0-3.dsc busybox_1.20.0-3_i386.deb to main/b/busybox/busybox_1.20.0-3_i386.deb udhcpc_1.20.0-3_i386.deb to main/b/busybox/udhcpc_1.20.0-3_i386.deb udhcpd_1.20.0-3_i386.deb to main/b/busybox/udhcpd_1.20.0-3_i386.deb A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 635...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Michael Tokarev m...@tls.msk.ru (supplier of updated busybox 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: Sat, 02 Jun 2012 14:54:04 +0400 Source: busybox Binary: busybox busybox-static busybox-udeb busybox-syslogd udhcpc udhcpd Architecture: source all i386 Version: 1:1.20.0-3 Distribution: unstable Urgency: low Maintainer: Debian Install System Team debian-b...@lists.debian.org Changed-By: Michael Tokarev m...@tls.msk.ru Description: busybox- Tiny utilities for small and embedded systems busybox-static - Standalone rescue shell with tons of builtin utilities busybox-syslogd - Provides syslogd and klogd using busybox busybox-udeb - Tiny utilities for the debian-installer (udeb) udhcpc - Provides the busybox DHCP client implementation udhcpd - Provides the busybox DHCP server implementation Closes: 635370 635548 Changes: busybox (1:1.20.0-3) unstable; urgency=low . * 1.20 had a few fixes which I forgot to mention: - integer overflow in expression on big endian (Closes: #635370) (I dislike the fix since it makes use of 64bit integers instead of using unsigned 32bit, but this is how upstream fixed it) - CVE-2011-2716 udhcpc insufficient checking of DHCP options (Closes: #635548) busybox dhcpd now replaces values of HOST_NAME, DOMAIN_NAME, NIS_DOMAIN, TFTP_SERVER_NAME with the literal string bad if these contains any bad characters. * applied stable patches from upstream (ash, man, ifupdown, tar) Checksums-Sha1: 60baa9063717370174713a4409fdf4990933 1610 busybox_1.20.0-3.dsc 20bd5adcbfb32bac41a7eb963cba80b1fcad3ae1 51184 busybox_1.20.0-3.debian.tar.gz 31eb0e1882901dad5b50e6ad218c28aebfc93bda 19356 busybox-syslogd_1.20.0-3_all.deb 488f5a0b1d0637eb6abfbc34de7a84bd6e0cefec 876936 busybox-static_1.20.0-3_i386.deb d06d577af0abc7c8bfbd01fd1c413c3fb45857da 439684 busybox_1.20.0-3_i386.deb 81829b2a3d7e6fb47d46e5db9d06fd6feef2708e 17018 udhcpc_1.20.0-3_i386.deb 10569b7d28e824c66d96a874a24e31198addda69 20324 udhcpd_1.20.0-3_i386.deb 7a8555d042c945faa7e193e185f23932eaabf1fe 202436 busybox-udeb_1.20.0-3_i386.udeb Checksums-Sha256: fd70216c557d46c231d9d93c0dcb80d7ccf3275867031386a38d5298327101ee 1610
Bug#627235: libpoex-role-sessioninstantiation-perl: Can't locate object method _set_id via package My::Session at /usr/share/perl5/POE/Kernel.pm line 1399.
On Tuesday 12 June 2012 11:01:51 Nick Perez wrote: 1) Don't have the time 2) These modules (POEx) were a thought experiment in a combination of technologies that are shiny 3) Reflex provides a much cleaner way of doing POE + Moose 4) Just this morning I scheduled deletes of all the POEx modules via PAUSE. 5) You guys are crazy for wanting to package up things like this for Debian :) Right... Well, thanks for the quick response :-). We'll have this package removed from Debian. Just for the record, we don't package development version of a Perl distribution. Looks like nobody did notice that lib-poex* were all development versions... Intrigeri, only the unreleased version of libpoe-component-pubsub-perl depends on lib-poex*. jirc and other depends on libpoe-component-pubsub-perl = 0.05. This version does not depend on lib-poex*, so we can safely ask for their removal. The only thing left will be to cleanup libpoe-component-pubsub-perl git repo (used for Debian packages). Nicholas has removed version 0.091317 from CPAN, so our git repo contains a non-existent version... I don't know how to clean this up. I'll ask for removal of lib-poex* All the best -- https://github.com/dod38fr/config-model/ -o- http://search.cpan.org/~ddumont/ http://ddumont.wordpress.com/-o- irc: dod at irc.debian.org -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#676741: marked as done (flactag: FTBFS: a2x: ERROR: xmllint --nonet --noout --valid /«PKGBUILDDIR»/flactag.1.xml returned non-zero exit status 127)
Your message dated Tue, 12 Jun 2012 11:32:52 + with message-id e1sepla-0006ox...@franck.debian.org and subject line Bug#676741: fixed in flactag 2.0.3-2 has caused the Debian Bug report #676741, regarding flactag: FTBFS: a2x: ERROR: xmllint --nonet --noout --valid /«PKGBUILDDIR»/flactag.1.xml returned non-zero exit status 127 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.) -- 676741: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=676741 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Source: flactag Version: 2.0.3-1 Severity: serious Tags: wheezy sid User: debian...@lists.debian.org Usertags: qa-ftbfs-20120609 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»' g++ -DHAVE_CONFIG_H -I. -DSYSCONFDIR='/etc' -DPKGLIBDIR='/usr/lib/flactag' -I/usr/include/FLAC++ -I/usr/include/FLAC -I/usr/include/neon-D_FORTIFY_SOURCE=2 -g -O2 -fPIE -fstack-protector --param=ssp-buffer-size=4 -Wformat -Werror=format-security -c -o flactag.o flactag.cc g++ -DHAVE_CONFIG_H -I. -DSYSCONFDIR='/etc' -DPKGLIBDIR='/usr/lib/flactag' -I/usr/include/FLAC++ -I/usr/include/FLAC -I/usr/include/neon-D_FORTIFY_SOURCE=2 -g -O2 -fPIE -fstack-protector --param=ssp-buffer-size=4 -Wformat -Werror=format-security -c -o Album.o Album.cc g++ -DHAVE_CONFIG_H -I. -DSYSCONFDIR='/etc' -DPKGLIBDIR='/usr/lib/flactag' -I/usr/include/FLAC++ -I/usr/include/FLAC -I/usr/include/neon-D_FORTIFY_SOURCE=2 -g -O2 -fPIE -fstack-protector --param=ssp-buffer-size=4 -Wformat -Werror=format-security -c -o Track.o Track.cc g++ -DHAVE_CONFIG_H -I. -DSYSCONFDIR='/etc' -DPKGLIBDIR='/usr/lib/flactag' -I/usr/include/FLAC++ -I/usr/include/FLAC -I/usr/include/neon-D_FORTIFY_SOURCE=2 -g -O2 -fPIE -fstack-protector --param=ssp-buffer-size=4 -Wformat -Werror=format-security -c -o AlbumWindow.o AlbumWindow.cc g++ -DHAVE_CONFIG_H -I. -DSYSCONFDIR='/etc' -DPKGLIBDIR='/usr/lib/flactag' -I/usr/include/FLAC++ -I/usr/include/FLAC -I/usr/include/neon-D_FORTIFY_SOURCE=2 -g -O2 -fPIE -fstack-protector --param=ssp-buffer-size=4 -Wformat -Werror=format-security -c -o TrackWindow.o TrackWindow.cc g++ -DHAVE_CONFIG_H -I. -DSYSCONFDIR='/etc' -DPKGLIBDIR='/usr/lib/flactag' -I/usr/include/FLAC++ -I/usr/include/FLAC -I/usr/include/neon-D_FORTIFY_SOURCE=2 -g -O2 -fPIE -fstack-protector --param=ssp-buffer-size=4 -Wformat -Werror=format-security -c -o FlacInfo.o FlacInfo.cc g++ -DHAVE_CONFIG_H -I. -DSYSCONFDIR='/etc' -DPKGLIBDIR='/usr/lib/flactag' -I/usr/include/FLAC++ -I/usr/include/FLAC -I/usr/include/neon-D_FORTIFY_SOURCE=2 -g -O2 -fPIE -fstack-protector --param=ssp-buffer-size=4 -Wformat -Werror=format-security -c -o TagName.o TagName.cc g++ -DHAVE_CONFIG_H -I. -DSYSCONFDIR='/etc' -DPKGLIBDIR='/usr/lib/flactag' -I/usr/include/FLAC++ -I/usr/include/FLAC -I/usr/include/neon-D_FORTIFY_SOURCE=2 -g -O2 -fPIE -fstack-protector --param=ssp-buffer-size=4 -Wformat -Werror=format-security -c -o TagsWindow.o TagsWindow.cc g++ -DHAVE_CONFIG_H -I. -DSYSCONFDIR='/etc' -DPKGLIBDIR='/usr/lib/flactag' -I/usr/include/FLAC++ -I/usr/include/FLAC -I/usr/include/neon-D_FORTIFY_SOURCE=2 -g -O2 -fPIE -fstack-protector --param=ssp-buffer-size=4 -Wformat -Werror=format-security -c -o CuesheetTrack.o CuesheetTrack.cc g++ -DHAVE_CONFIG_H -I. -DSYSCONFDIR='/etc' -DPKGLIBDIR='/usr/lib/flactag' -I/usr/include/FLAC++ -I/usr/include/FLAC -I/usr/include/neon-D_FORTIFY_SOURCE=2 -g -O2 -fPIE -fstack-protector --param=ssp-buffer-size=4 -Wformat -Werror=format-security -c -o Cuesheet.o Cuesheet.cc g++ -DHAVE_CONFIG_H -I. -DSYSCONFDIR='/etc' -DPKGLIBDIR='/usr/lib/flactag' -I/usr/include/FLAC++ -I/usr/include/FLAC -I/usr/include/neon-D_FORTIFY_SOURCE=2 -g -O2 -fPIE -fstack-protector --param=ssp-buffer-size=4 -Wformat -Werror=format-security -c -o DiscIDWrapper.o DiscIDWrapper.cc g++ -DHAVE_CONFIG_H -I. -DSYSCONFDIR='/etc' -DPKGLIBDIR='/usr/lib/flactag' -I/usr/include/FLAC++ -I/usr/include/FLAC -I/usr/include/neon-D_FORTIFY_SOURCE=2 -g -O2 -fPIE -fstack-protector --param=ssp-buffer-size=4 -Wformat -Werror=format-security -c -o base64.o base64.cc g++ -DHAVE_CONFIG_H -I. -DSYSCONFDIR='/etc' -DPKGLIBDIR='/usr/lib/flactag' -I/usr/include/FLAC++ -I/usr/include/FLAC -I/usr/include/neon-D_FORTIFY_SOURCE=2 -g -O2 -fPIE -fstack-protector --param=ssp-buffer-size=4 -Wformat -Werror=format-security -c -o
Bug#676354: marked as done (Needs dependency on python-lxml)
Your message dated Tue, 12 Jun 2012 11:34:39 + with message-id e1sepmt-0006ve...@franck.debian.org and subject line Bug#676354: fixed in sozi 12.05-1 has caused the Debian Bug report #676354, regarding Needs dependency on python-lxml 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.) -- 676354: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=676354 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: sozi Version: 11.07-1 Severity: serious -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi, when I start sozi in inkscape, I get: Diese Erweiterung benötigt python-lxml. Diese erhalten Sie unter http://cheeseshop.python.org/pypi/lxml/; oder durch ein Packet ihres Packetmanagers (z.B.: sudo apt-get install python-lxml) It seems sozi is missing a dependency on python-lxml. Greetings, Joachim - -- System Information: Debian Release: wheezy/sid APT prefers unstable APT policy: (500, 'unstable'), (101, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 3.2.0-2-amd64 (SMP w/2 CPU cores) Locale: LANG=de_DE.utf8, LC_CTYPE=de_DE.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages sozi depends on: ii inkscape 0.48.3.1-1+b1 ii python 2.7.2-10 ii python-gtk2 2.24.0-3 sozi recommends no packages. sozi suggests no packages. - -- no debconf information -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.12 (GNU/Linux) iEYEARECAAYFAk/PPIsACgkQ9ijrk0dDIGyE2wCdGguOcEnsPt5EOzBMXgIpKuAT r0oAoKsWmJ+hihycJxqhTOfsKre/EBjH =gKMz -END PGP SIGNATURE- ---End Message--- ---BeginMessage--- Source: sozi Source-Version: 12.05-1 We believe that the bug you reported is fixed in the latest version of sozi, which is due to be installed in the Debian FTP archive: sozi_12.05-1.debian.tar.gz to main/s/sozi/sozi_12.05-1.debian.tar.gz sozi_12.05-1.dsc to main/s/sozi/sozi_12.05-1.dsc sozi_12.05-1_all.deb to main/s/sozi/sozi_12.05-1_all.deb sozi_12.05.orig.tar.gz to main/s/sozi/sozi_12.05.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 676...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Kan-Ru Chen kos...@debian.org (supplier of updated sozi 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, 12 Jun 2012 18:04:46 +0800 Source: sozi Binary: sozi Architecture: source all Version: 12.05-1 Distribution: unstable Urgency: low Maintainer: Kan-Ru Chen kos...@debian.org Changed-By: Kan-Ru Chen kos...@debian.org Description: sozi - inkscape extension for creating animated presentations Closes: 676002 676354 Changes: sozi (12.05-1) unstable; urgency=low . * New upstream release (Closes: #676002) * README.source - Explain why the orig tarball is repackaged. * debian/copyright - Update Format url. * debian/control - Update Standards-Version to 3.9.3. - Add Depends python-lxml (Closes: #676354). Checksums-Sha1: 01e88762f7ffcdc2409ce289d1b9fab8e33e6d0f 1818 sozi_12.05-1.dsc 25618b286cc704f3fdf678604445600c4fb885a4 217155 sozi_12.05.orig.tar.gz aeadaac06d3127da7bcdbf9bc60d4537eb47de3f 3875 sozi_12.05-1.debian.tar.gz 8094d05276704b0222d76431b684ea7d9d43dea7 28736 sozi_12.05-1_all.deb Checksums-Sha256: 6fb303830b6d711c90933e40bd88b24b62019c5501dae174c46669f620e2e4fc 1818 sozi_12.05-1.dsc b4657f9ecbd1c56de895a5ce3c29fd3f3dd0fc77b0a3ac0311059b234f43a34e 217155 sozi_12.05.orig.tar.gz 642b42851646abbf1ec4d728cbe2a8cc146b7f900c981a958891b4a4aafad1a1 3875 sozi_12.05-1.debian.tar.gz bf87a37ab1dc7b6f537c4eb8c00d2f64eea7473abcbf38e98e3ea06c6c9a6bad 28736 sozi_12.05-1_all.deb Files: ae5a069dc4146cb65a60eb8e9f6ecf56 1818 graphics optional sozi_12.05-1.dsc 8bb8aef19f9020b21ea5d8b344714e5d 217155 graphics optional sozi_12.05.orig.tar.gz cccfb2dbed23e5623cbdb46a5f68174a 3875 graphics optional sozi_12.05-1.debian.tar.gz 9b679c3c099c715681c3fe0beedde6cb 28736 graphics optional sozi_12.05-1_all.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.12 (GNU/Linux) iQIcBAEBCAAGBQJP1yTzAAoJEAo5NUq25X3hmaIQAKLo7Idzqhd5jfRHt1FOLrw+ QNhmz7JaY1u8NXmZwEQGjm6IDYLIJi28g8HsRpxdxtyUEqSo8EIPGTG7wGSu69lY tHQ5SV94AZJ8Z4iHAm9BoQuyEt4KlooMCP5kOT4Mwwkia9jX9hNi+a6KYcGiT9dC
Bug#604129: marked as done (tardy: tardy is under GPL3 not GPL2)
Your message dated Tue, 12 Jun 2012 12:18:05 + with message-id e1seq2v-ac...@franck.debian.org and subject line Bug#604129: fixed in tardy 1.25-1 has caused the Debian Bug report #604129, regarding tardy: tardy is under GPL3 not GPL2 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.) -- 604129: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=604129 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: tardy Version: 1.20-0.1 Severity: normal Starting from release 1.15 tardy is released under GPL 3 or later, the debian/copyright file still mention GPL2 or later. HTH -- Walter Franzini http://aegis.stepbuild.org/ pgpMG6KdITdiz.pgp Description: PGP signature ---End Message--- ---BeginMessage--- Source: tardy Source-Version: 1.25-1 We believe that the bug you reported is fixed in the latest version of tardy, which is due to be installed in the Debian FTP archive: tardy_1.25-1.debian.tar.gz to main/t/tardy/tardy_1.25-1.debian.tar.gz tardy_1.25-1.dsc to main/t/tardy/tardy_1.25-1.dsc tardy_1.25-1_amd64.deb to main/t/tardy/tardy_1.25-1_amd64.deb tardy_1.25.orig.tar.gz to main/t/tardy/tardy_1.25.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 604...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Jari Aalto jari.aa...@cante.net (supplier of updated tardy 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: Fri, 08 Jun 2012 21:08:49 +0300 Source: tardy Binary: tardy Architecture: source amd64 Version: 1.25-1 Distribution: unstable Urgency: low Maintainer: Jari Aalto jari.aa...@cante.net Changed-By: Jari Aalto jari.aa...@cante.net Description: tardy - post-processor for tar command Closes: 604129 675765 Changes: tardy (1.25-1) unstable; urgency=low . * New maintainer (Closes: #675765). - New upstream release. * debian/clean - New file. * debian/compat - Update to 9 * debian/control - (Build-Depends): Update to debhelper 9. Add libexplain-dev, libboost-dev, cpio - (Description): Update first line for Lintian. - (Standards-Version): Update to 3.9.3. - (Vcs-*): Add. * debian/copyright - Update to format 1.0. - Correct license to GPL-3 (Closes: #604129). * debian/install - Rename. Was package.install. * debian/manpages - Update path. * debian/patches - (10): New. Correct manpage issues. * debian/rules - Update to dh(1). - Use hardened build flags. http://wiki.debian.org/ReleaseGoals/SecurityHardeningBuildFlags Checksums-Sha1: 5e2175be462d12f65758a8ed5ea39f1cb0879ef8 1228 tardy_1.25-1.dsc f657b9298eef19ddbbef5f350601c2846f699f19 1834343 tardy_1.25.orig.tar.gz c4c0ddbd5ac69464500f8d8c5a5f51ef869cd5af 4596 tardy_1.25-1.debian.tar.gz 4eaa6dc494ffd6917f70964b4ad7828fae01f9e9 156908 tardy_1.25-1_amd64.deb Checksums-Sha256: 2fb285969b3227fcb528b8ff6fc7c3daf5d4bbae668ae0fa8761c568fb6f617a 1228 tardy_1.25-1.dsc 8ae113b1d10d7e645f1f6a4ebf2bc31b37cae7871b057a275aa787288ce60bb0 1834343 tardy_1.25.orig.tar.gz c619f9910cbd241927472d16defdd550e200b96fbf681f64ce51f5aa0ba6aea9 4596 tardy_1.25-1.debian.tar.gz 3111f560d3832dc49a05893f1b68b9537af0619752c17866a579f3fa87597c1c 156908 tardy_1.25-1_amd64.deb Files: 820a53eb8c3aea9ccf5d3c5dba482b68 1228 utils optional tardy_1.25-1.dsc 27e1b625488d824d6e95412ba88c0651 1834343 utils optional tardy_1.25.orig.tar.gz 7c262b6c76c3ee4ae99ee07d61f9a492 4596 utils optional tardy_1.25-1.debian.tar.gz cd8363ab62034be2496cbd0c8efad3c4 156908 utils optional tardy_1.25-1_amd64.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.11 (GNU/Linux) iEYEARECAAYFAk/XLsUACgkQLARVQsm1Xax8cgCfUkTRiutDh3ov0x9tN2ZjGeNb JLcAn3SDrR1VaO8WQ7m5iRv4ZQSEaO4d =mcPU -END PGP SIGNATURE- ---End Message---
Processed: r2147 - mysql-5.1/branches/stable-security/debian
Processing commands for cont...@bugs.debian.org:
tags 670636 pending
Bug #670636 {Done: Clint Byrum cl...@ubuntu.com} [mysql-5.1] Multiple
security issues in April security release
Added tag(s) pending.
tags 677018 pending
Bug #677018 [mysql-5.1] mysql-5.1: CVE-2012-2122: MySQL authentication bypass
Added tag(s) pending.
thanks
Stopping processing here.
Please contact me if you need assistance.
--
670636: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=670636
677018: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=677018
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#677221: xen: Xen PV privilege escalation (CVE-2012-0217)
Source: xen Version: 4.1.2-2 Severity: critical Tags: security Justification: allows PV domains to escape into the dom0 context Hi, I realize you're most likely pretty well aware of that problem already, but Debian's Xen versions are vulnerable to a PV privilege escalation [1]. The issue is tracked as CVE-2012-0217 and public as of today. Therefore I am filing this bug for coordination and traceability. Please update the packages and consider a security update for Squeeze. [1] http://lists.xen.org/archives/html/xen-devel/2012-06/msg00670.html -- System Information: Debian Release: wheezy/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: amd64 (x86_64) Kernel: Linux 3.3.0-trunk-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 -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#627235: libpoex-role-sessioninstantiation-perl: Can't locate object method _set_id via package My::Session at /usr/share/perl5/POE/Kernel.pm line 1399.
Hi Dominique On Tue, Jun 12, 2012 at 01:11:27PM +0200, Dominique Dumont wrote: The only thing left will be to cleanup libpoe-component-pubsub-perl git repo (used for Debian packages). Nicholas has removed version 0.091317 from CPAN, so our git repo contains a non-existent version... I don't know how to clean this up. If you want to do it yourself: http://pkg-perl.alioth.debian.org/git.html#removing_packages Or if you want to remove it completely instead of motiv it to attic, remove the repo on vasks and update the mrconfig in the meta.git repo. Regards, Salvatore signature.asc Description: Digital signature
Bug#677227: screen: Workaround for #644788 fails to detect a running screen on kfreebsd / process renaming does not work on kfreebsd
Package: screen Version: 4.1.0~20120320gitdb59704-2 Severity: serious User: debian-...@lists.debian.org Usertags: kfreebsd The implemented workaround for http://bugs.debian.org/644788 uses pidof SCREEN to detect running screen servers as screen server processes rename themselves in the process listing to SCREEN. But on kfreebsd this process renaming don't seem to work. This doesn't seem to be a screen issue but a general kfreebsd issue as the following works as expected on Linux, but not on kfreebsd: $ perl -e '$0 = foobar!; ' Happened with kernel 8.2-1-686-smp which seems no more to be available. Will test later if it still happens with current kernels and if so, file a seperated bug report against some kfreebsd-image-* packages. Planned workaround for the workaround is to also check for pidof screen. At least that showed a running screen server on kfreebsd. Manual temporary workaround for the workaround is to downgrade to screen from testing or -- if e.g. apt/aptitude/dpkg is still running and a second apt/aptitude/dpkg is therefore not possible without killing apt/aptitude/dpkg -- to extract the screen binary from the package in testing and then use that one: # dget screen=4.0.3-14 # dpkg-deb -x screen_4.0.3-14_kfreebsd-*.deb screen-4.0.3 # screen-4.0.3/usr/bin/screen -rd Sorry for the inconvenience. Regards, Axel -- ,''`. | Axel Beckert a...@debian.org, http://people.debian.org/~abe/ : :' : | Debian Developer, ftp.ch.debian.org Admin `. `' | 1024D: F067 EA27 26B9 C3FC 1486 202E C09E 1D89 9593 0EDE `-| 4096R: 2517 B724 C5F6 CA99 5329 6E61 2FF9 CD59 6126 16B5 -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#627235: libpoex-role-sessioninstantiation-perl: Can't locate object method _set_id via package My::Session at /usr/share/perl5/POE/Kernel.pm line 1399.
On Tuesday 12 June 2012 14:55:35 Salvatore Bonaccorso wrote: Hi Dominique On Tue, Jun 12, 2012 at 01:11:27PM +0200, Dominique Dumont wrote: The only thing left will be to cleanup libpoe-component-pubsub-perl git repo (used for Debian packages). Nicholas has removed version 0.091317 from CPAN, so our git repo contains a non-existent version... I don't know how to clean this up. If you want to do it yourself: http://pkg-perl.alioth.debian.org/git.html#removing_packages Or if you want to remove it completely instead of motiv it to attic, remove the repo on vasks and update the mrconfig in the meta.git repo. Well, we cannot remove the whole git repo of the package. Only the last commited version (0.091137) is wrong and needs to be cleaned up (or put aside in a branch). Debian still has version 0.05 (which we want to keep), so any further packaging activity must start from tag debian/0.05-1, not from HEAD All the best -- https://github.com/dod38fr/config-model/ -o- http://search.cpan.org/~ddumont/ http://ddumont.wordpress.com/-o- irc: dod at irc.debian.org -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#627235: libpoex-role-sessioninstantiation-perl: Can't locate object method _set_id via package My::Session at /usr/share/perl5/POE/Kernel.pm line 1399.
Hi, Salvatore Bonaccorso wrote (12 Jun 2012 12:55:35 GMT) : On Tue, Jun 12, 2012 at 01:11:27PM +0200, Dominique Dumont wrote: The only thing left will be to cleanup libpoe-component-pubsub-perl git repo (used for Debian packages). Nicholas has removed version 0.091317 from CPAN, so our git repo contains a non-existent version... I don't know how to clean this up. If you want to do it yourself: http://pkg-perl.alioth.debian.org/git.html#removing_packages I don't think we want to remove the package entirely, but rather bring its Git repository into a state that is based on the 0.05 upstream release. I'm taking care of it. -- 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 637451 is normal
Processing commands for cont...@bugs.debian.org: severity 637451 normal Bug #637451 [zabbix-frontend-php] zabbix-frontend-php: web access fails with Access denied for user 'zabbix'@'localhost' Severity set to 'normal' from 'grave' thanks Stopping processing here. Please contact me if you need assistance. -- 637451: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=637451 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#673814: marked as done (ruby-pdf-writer: fails to upgrade from 'testing' - trying to overwrite /usr/bin/techbook)
Your message dated Tue, 12 Jun 2012 13:31:50 + with message-id e1serci-0006af...@franck.debian.org and subject line Bug#677170: Removed package(s) from unstable has caused the Debian Bug report #673814, regarding ruby-pdf-writer: fails to upgrade from 'testing' - trying to overwrite /usr/bin/techbook 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.) -- 673814: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=673814 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: ruby-pdf-writer Version: 1.1.8+dfsg-2 Severity: serious User: debian...@lists.debian.org Usertags: piuparts Hi, during a test with piuparts I noticed your package fails to upgrade from 'testing'. It installed fine in 'testing', then the upgrade to 'sid' fails because it tries to overwrite other packages files without declaring a replaces relation. See policy 7.6 at http://www.debian.org/doc/debian-policy/ch-relationships.html#s-replaces From the attached log (scroll to the bottom...): Selecting previously unselected package ruby-pdf-writer. Unpacking ruby-pdf-writer (from .../ruby-pdf-writer_1.1.8+dfsg-2_all.deb) ... dpkg: error processing /var/cache/apt/archives/ruby-pdf-writer_1.1.8+dfsg-2_all.deb (--unpack): trying to overwrite '/usr/bin/techbook', which is also in package libpdf-writer-ruby1.8 1.1.8+dfsg-1 dpkg-deb: error: subprocess paste was killed by signal (Broken pipe) Preparing to replace libpdf-writer-ruby 1.1.8+dfsg-1 (using .../libpdf-writer-ruby_1.1.8+dfsg-2_all.deb) ... Unpacking replacement libpdf-writer-ruby ... Preparing to replace libpdf-writer-ruby1.8 1.1.8+dfsg-1 (using .../libpdf-writer-ruby1.8_1.1.8+dfsg-2_all.deb) ... Unpacking replacement libpdf-writer-ruby1.8 ... Errors were encountered while processing: /var/cache/apt/archives/ruby-pdf-writer_1.1.8+dfsg-2_all.deb cheers, Andreas libpdf-writer-ruby_1.1.8+dfsg-2.log.gz Description: GNU Zip compressed data ---End Message--- ---BeginMessage--- Version: 1.1.8+dfsg-2+rm Dear submitter, as the package ruby-pdf-writer has just been removed from the Debian archive unstable we hereby close the associated bug reports. We are sorry that we couldn't deal with your issue properly. For details on the removal, please see http://bugs.debian.org/677170 The version of this package that was in Debian prior to this removal can still be found using http://snapshot.debian.org/. This message was generated automatically; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@debian.org. Debian distribution maintenance software pp. Alexander Reichle-Schmehl (the ftpmaster behind the curtain) ---End Message---
Bug#674371: marked as done (ruby-pdf-writer: FTBFS: test failed)
Your message dated Tue, 12 Jun 2012 13:31:50 + with message-id e1serci-0006af...@franck.debian.org and subject line Bug#677170: Removed package(s) from unstable has caused the Debian Bug report #674371, regarding ruby-pdf-writer: 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.) -- 674371: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=674371 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Source: ruby-pdf-writer Version: 1.1.8+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: fakeroot debian/rules binary dh binary --buildsystem=ruby --with ruby dh_testroot -O--buildsystem=ruby dh_prep -O--buildsystem=ruby dh_installdirs -O--buildsystem=ruby dh_auto_install -O--buildsystem=ruby Invalid gemspec in [pdf-writer.gemspec]: uninitialized constant Gem::Specification::FileList Entering dh_ruby --install install -d /«BUILDDIR»/ruby-pdf-writer-1.1.8+dfsg/debian/ruby-pdf-writer/usr/bin install -D -m755 bin/techbook /«BUILDDIR»/ruby-pdf-writer-1.1.8+dfsg/debian/ruby-pdf-writer/usr/bin/techbook install -d /«BUILDDIR»/ruby-pdf-writer-1.1.8+dfsg/debian/ruby-pdf-writer/usr/lib/ruby/vendor_ruby install -D -m644 lib/pdf/simpletable.rb /«BUILDDIR»/ruby-pdf-writer-1.1.8+dfsg/debian/ruby-pdf-writer/usr/lib/ruby/vendor_ruby/pdf/simpletable.rb install -D -m644 lib/pdf/writer.rb /«BUILDDIR»/ruby-pdf-writer-1.1.8+dfsg/debian/ruby-pdf-writer/usr/lib/ruby/vendor_ruby/pdf/writer.rb install -D -m644 lib/pdf/math.rb /«BUILDDIR»/ruby-pdf-writer-1.1.8+dfsg/debian/ruby-pdf-writer/usr/lib/ruby/vendor_ruby/pdf/math.rb install -D -m644 lib/pdf/quickref.rb /«BUILDDIR»/ruby-pdf-writer-1.1.8+dfsg/debian/ruby-pdf-writer/usr/lib/ruby/vendor_ruby/pdf/quickref.rb install -D -m644 lib/pdf/techbook.rb /«BUILDDIR»/ruby-pdf-writer-1.1.8+dfsg/debian/ruby-pdf-writer/usr/lib/ruby/vendor_ruby/pdf/techbook.rb install -D -m644 lib/pdf/writer/graphics.rb /«BUILDDIR»/ruby-pdf-writer-1.1.8+dfsg/debian/ruby-pdf-writer/usr/lib/ruby/vendor_ruby/pdf/writer/graphics.rb install -D -m644 lib/pdf/writer/object.rb /«BUILDDIR»/ruby-pdf-writer-1.1.8+dfsg/debian/ruby-pdf-writer/usr/lib/ruby/vendor_ruby/pdf/writer/object.rb install -D -m644 lib/pdf/writer/lang/en.rb /«BUILDDIR»/ruby-pdf-writer-1.1.8+dfsg/debian/ruby-pdf-writer/usr/lib/ruby/vendor_ruby/pdf/writer/lang/en.rb install -D -m644 lib/pdf/writer/oreader.rb /«BUILDDIR»/ruby-pdf-writer-1.1.8+dfsg/debian/ruby-pdf-writer/usr/lib/ruby/vendor_ruby/pdf/writer/oreader.rb install -D -m644 lib/pdf/writer/ohash.rb /«BUILDDIR»/ruby-pdf-writer-1.1.8+dfsg/debian/ruby-pdf-writer/usr/lib/ruby/vendor_ruby/pdf/writer/ohash.rb install -D -m644 lib/pdf/writer/state.rb /«BUILDDIR»/ruby-pdf-writer-1.1.8+dfsg/debian/ruby-pdf-writer/usr/lib/ruby/vendor_ruby/pdf/writer/state.rb install -D -m644 lib/pdf/writer/graphics/imageinfo.rb /«BUILDDIR»/ruby-pdf-writer-1.1.8+dfsg/debian/ruby-pdf-writer/usr/lib/ruby/vendor_ruby/pdf/writer/graphics/imageinfo.rb install -D -m644 lib/pdf/writer/fontmetrics.rb /«BUILDDIR»/ruby-pdf-writer-1.1.8+dfsg/debian/ruby-pdf-writer/usr/lib/ruby/vendor_ruby/pdf/writer/fontmetrics.rb install -D -m644 lib/pdf/writer/strokestyle.rb /«BUILDDIR»/ruby-pdf-writer-1.1.8+dfsg/debian/ruby-pdf-writer/usr/lib/ruby/vendor_ruby/pdf/writer/strokestyle.rb install -D -m644 lib/pdf/writer/object/procset.rb /«BUILDDIR»/ruby-pdf-writer-1.1.8+dfsg/debian/ruby-pdf-writer/usr/lib/ruby/vendor_ruby/pdf/writer/object/procset.rb install -D -m644 lib/pdf/writer/object/destination.rb /«BUILDDIR»/ruby-pdf-writer-1.1.8+dfsg/debian/ruby-pdf-writer/usr/lib/ruby/vendor_ruby/pdf/writer/object/destination.rb install -D -m644 lib/pdf/writer/object/info.rb /«BUILDDIR»/ruby-pdf-writer-1.1.8+dfsg/debian/ruby-pdf-writer/usr/lib/ruby/vendor_ruby/pdf/writer/object/info.rb install -D -m644 lib/pdf/writer/object/viewerpreferences.rb /«BUILDDIR»/ruby-pdf-writer-1.1.8+dfsg/debian/ruby-pdf-writer/usr/lib/ruby/vendor_ruby/pdf/writer/object/viewerpreferences.rb install -D -m644 lib/pdf/writer/object/fontdescriptor.rb /«BUILDDIR»/ruby-pdf-writer-1.1.8+dfsg/debian/ruby-pdf-writer/usr/lib/ruby/vendor_ruby/pdf/writer/object/fontdescriptor.rb install -D -m644 lib/pdf/writer/object/annotation.rb /«BUILDDIR»/ruby-pdf-writer-1.1.8+dfsg/debian/ruby-pdf-writer/usr/lib/ruby/vendor_ruby/pdf/writer/object/annotation.rb install -D -m644
Bug#676089: marked as done (libpdf-writer-ruby: FTBFS: /usr/lib/ruby/1.9.1/rubygems/custom_require.rb:36:in `require': /«BUILDDIR»/libpdf-writer-ruby-1.1.8+dfsg/lib/pdf/writer.rb:712: invalid multib
Your message dated Tue, 12 Jun 2012 13:30:54 +
with message-id e1serbo-0006uq...@franck.debian.org
and subject line Bug#677169: Removed package(s) from unstable
has caused the Debian Bug report #676089,
regarding libpdf-writer-ruby: FTBFS:
/usr/lib/ruby/1.9.1/rubygems/custom_require.rb:36:in `require':
/«BUILDDIR»/libpdf-writer-ruby-1.1.8+dfsg/lib/pdf/writer.rb:712: invalid
multibyte char (US-ASCII) (SyntaxError)
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.)
--
676089: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=676089
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
---BeginMessage---
Source: libpdf-writer-ruby
Version: 1.1.8+dfsg-1
Severity: serious
Tags: wheezy sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20120604 qa-ftbfs
User: debian-r...@lists.debian.org
Usertags: default19
Justification: FTBFS on amd64
Hi,
During a rebuild of all packages in sid, your package failed to build on
amd64.
Relevant part:
fakeroot debian/rules binary
test -x debian/rules
dh_testroot
dh_clean -k
dh_clean: dh_clean -k is deprecated; use dh_prep instead
dh_installdirs -A
mkdir -p .
/usr/share/cdbs/1/rules/buildcore.mk:109: WARNING: DEB_COMPRESS_EXCLUDE is a
deprecated variable
dh_installman --package=libpdf-writer-ruby1.8 debian/techbook.1
Adding cdbs dependencies to debian/libpdf-writer-ruby.substvars
dh_installdirs -plibpdf-writer-ruby
Adding cdbs dependencies to debian/libpdf-writer-ruby-doc.substvars
dh_installdirs -plibpdf-writer-ruby-doc
# Build the documentation PDF
/usr/bin/ruby -I ./debian/libpdf-writer-ruby1.8/ ./bin/techbook -n manual.pwd
/usr/lib/ruby/1.9.1/rubygems/custom_require.rb:36:in `require':
/«BUILDDIR»/libpdf-writer-ruby-1.1.8+dfsg/lib/pdf/writer.rb:712: invalid
multibyte char (US-ASCII) (SyntaxError)
/«BUILDDIR»/libpdf-writer-ruby-1.1.8+dfsg/lib/pdf/writer.rb:712: invalid
multibyte char (US-ASCII)
/«BUILDDIR»/libpdf-writer-ruby-1.1.8+dfsg/lib/pdf/writer.rb:712: syntax
error, unexpected $end, expecting keyword_end
content = %PDF-#{@version}\n%âãÏÓ\n
^
from /usr/lib/ruby/1.9.1/rubygems/custom_require.rb:36:in `require'
from
/«BUILDDIR»/libpdf-writer-ruby-1.1.8+dfsg/lib/pdf/simpletable.rb:11:in `top
(required)'
from /usr/lib/ruby/1.9.1/rubygems/custom_require.rb:36:in `require'
from /usr/lib/ruby/1.9.1/rubygems/custom_require.rb:36:in `require'
from
/«BUILDDIR»/libpdf-writer-ruby-1.1.8+dfsg/lib/pdf/techbook.rb:12:in `top
(required)'
from /usr/lib/ruby/1.9.1/rubygems/custom_require.rb:36:in `require'
from /usr/lib/ruby/1.9.1/rubygems/custom_require.rb:36:in `require'
from ./bin/techbook:18:in `rescue in main'
from ./bin/techbook:12:in `main'
make: *** [install/libpdf-writer-ruby-doc] Error 1
The full build log is available from:
http://people.debian.org/~lucas/logs/2012/06/04/libpdf-writer-ruby_1.1.8+dfsg-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 EC2 VM instances from
Amazon Web Services, using a clean, minimal and up-to-date chroot. Every
failed build was retried once to eliminate random failures.
---End Message---
---BeginMessage---
Version: 1.1.8+dfsg-1+rm
Dear submitter,
as the package libpdf-writer-ruby has just been removed from the Debian archive
unstable we hereby close the associated bug reports. We are sorry
that we couldn't deal with your issue properly.
For details on the removal, please see http://bugs.debian.org/677169
The version of this package that was in Debian prior to this removal
can still be found using http://snapshot.debian.org/.
This message was generated automatically; if you believe that there is
a problem with it please contact the archive administrators by mailing
ftpmas...@debian.org.
Debian distribution maintenance software
pp.
Alexander Reichle-Schmehl (the ftpmaster behind the curtain)
---End Message---
Bug#676929: marked as done (gtkpod: FTBFS on most architectures: exported symbols not as expected)
Your message dated Tue, 12 Jun 2012 13:32:35 + with message-id e1serd1-0006eo...@franck.debian.org and subject line Bug#676929: fixed in gtkpod 2.1.2~beta2-2 has caused the Debian Bug report #676929, regarding gtkpod: FTBFS on most architectures: exported symbols not as expected 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.) -- 676929: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=676929 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Source: gtkpod Version: 2.1.2~beta2-1 Severity: serious Justification: fails to build from source (but built successfully in the past) Builds of gtkpod have been failing on most architectures because some mangled names vary, mostly due to natural differences in underlying types; you can find the details at https://buildd.debian.org/status/package.php?p=gtkpodver=2.1.2~beta2-1 (I'll report the kfreebsd-amd64 failure separately in a moment.) Could you please accommodate these differences? Thanks! ---End Message--- ---BeginMessage--- Source: gtkpod Source-Version: 2.1.2~beta2-2 We believe that the bug you reported is fixed in the latest version of gtkpod, which is due to be installed in the Debian FTP archive: gtkpod-data_2.1.2~beta2-2_all.deb to main/g/gtkpod/gtkpod-data_2.1.2~beta2-2_all.deb gtkpod-dbg_2.1.2~beta2-2_amd64.deb to main/g/gtkpod/gtkpod-dbg_2.1.2~beta2-2_amd64.deb gtkpod_2.1.2~beta2-2.debian.tar.gz to main/g/gtkpod/gtkpod_2.1.2~beta2-2.debian.tar.gz gtkpod_2.1.2~beta2-2.dsc to main/g/gtkpod/gtkpod_2.1.2~beta2-2.dsc gtkpod_2.1.2~beta2-2_amd64.deb to main/g/gtkpod/gtkpod_2.1.2~beta2-2_amd64.deb libatomicparsley-dev_2.1.2~beta2-2_amd64.deb to main/g/gtkpod/libatomicparsley-dev_2.1.2~beta2-2_amd64.deb libatomicparsley0_2.1.2~beta2-2_amd64.deb to main/g/gtkpod/libatomicparsley0_2.1.2~beta2-2_amd64.deb libgtkpod-dev_2.1.2~beta2-2_amd64.deb to main/g/gtkpod/libgtkpod-dev_2.1.2~beta2-2_amd64.deb libgtkpod1_2.1.2~beta2-2_amd64.deb to main/g/gtkpod/libgtkpod1_2.1.2~beta2-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 676...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Matteo F. Vescovi mfv.deb...@gmail.com (supplier of updated gtkpod 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, 12 Jun 2012 09:18:54 +0200 Source: gtkpod Binary: gtkpod gtkpod-data gtkpod-dbg libgtkpod1 libgtkpod-dev libatomicparsley0 libatomicparsley-dev Architecture: source amd64 all Version: 2.1.2~beta2-2 Distribution: unstable Urgency: low Maintainer: gtkpod Maintainers pkg-gtkpod-de...@lists.alioth.debian.org Changed-By: Matteo F. Vescovi mfv.deb...@gmail.com Description: gtkpod - manage songs and playlists on an Apple iPod gtkpod-data - architecture-independent files for gtkpod gtkpod-dbg - debugging symbols for gtkpod libatomicparsley-dev - main library for atomic parsley in gtkpod, development kit libatomicparsley0 - main library for atomic parsley in gtkpod, shared library libgtkpod-dev - main library for the gtkpod package, development kit libgtkpod1 - main library for the gtkpod package, shared library Closes: 676929 676931 Changes: gtkpod (2.1.2~beta2-2) UNRELEASED; urgency=low . * debian/libatomicparsley0.symbols: symbols updated (Closes: #676929) * debian/control: pkg-kde-tools added to b-deps * debian/patches/: #0002 added to fix FTBFS on kBSD64 (Closes: #676931) * debian/watch: uscan opts updated Checksums-Sha1: 6ec04529db1a011c478095a9eac0fe99287825b4 2638 gtkpod_2.1.2~beta2-2.dsc 2b42c4e1eaf4dd0745559c8345df08373f950def 19521 gtkpod_2.1.2~beta2-2.debian.tar.gz dbd59cb8f7cb4c33b26d2b2d15f2c35743591b4c 498868 gtkpod_2.1.2~beta2-2_amd64.deb 333ca677b171971d87fb6334720910e6bbfefbca 1477742 gtkpod-data_2.1.2~beta2-2_all.deb 0b6cc1d2003af9a23675e1e29f9aad82081c55d4 1661828 gtkpod-dbg_2.1.2~beta2-2_amd64.deb 709ca881c0ae38cd0846477d0e012b98dbc9dc36 291430 libgtkpod1_2.1.2~beta2-2_amd64.deb abb027dbc579dfa04281f74e2a3b91665b019962 338056 libgtkpod-dev_2.1.2~beta2-2_amd64.deb 8d61846b6701cd6308bfa6d0bec25f766843e1b8 216494 libatomicparsley0_2.1.2~beta2-2_amd64.deb 99a2e974a90a711e14b9c60d7e1330479642af25 148066 libatomicparsley-dev_2.1.2~beta2-2_amd64.deb
Bug#676931: marked as done (gtkpod: FTBFS on kfreebsd-amd64: conflicting uint64_t definitions)
Your message dated Tue, 12 Jun 2012 13:32:35 + with message-id e1serd1-0006er...@franck.debian.org and subject line Bug#676931: fixed in gtkpod 2.1.2~beta2-2 has caused the Debian Bug report #676931, regarding gtkpod: FTBFS on kfreebsd-amd64: conflicting uint64_t definitions 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.) -- 676931: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=676931 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Source: gtkpod Version: 2.1.2~beta2-1 Severity: serious Justification: fails to build from source (but built successfully in the past) gtkpod picks up two (formally) different definitions of uint64_t on kfreebsd-amd64: In file included from /usr/include/sys/kern/types.h:71:0, from /usr/include/sys/kern/param.h:67, from /usr/include/osreldate.h:1, from /usr/include/x86_64-kfreebsd-gnu/sys/param.h:39, from AtomicParsley.h:25, from AP_commons.cpp:35: /usr/include/sys/_stdint.h:69:21: error: conflicting declaration 'typedef __uint64_t uint64_t' In file included from AP_commons.cpp:33:0: AP_commons.h:45:28: error: 'uint64_t' has a previous declaration as 'typedef long long unsigned int uint64_t' Could you please fix AP_commons.h to #include stdint.h rather than trying to define (u)intN_t itself? Thanks! ---End Message--- ---BeginMessage--- Source: gtkpod Source-Version: 2.1.2~beta2-2 We believe that the bug you reported is fixed in the latest version of gtkpod, which is due to be installed in the Debian FTP archive: gtkpod-data_2.1.2~beta2-2_all.deb to main/g/gtkpod/gtkpod-data_2.1.2~beta2-2_all.deb gtkpod-dbg_2.1.2~beta2-2_amd64.deb to main/g/gtkpod/gtkpod-dbg_2.1.2~beta2-2_amd64.deb gtkpod_2.1.2~beta2-2.debian.tar.gz to main/g/gtkpod/gtkpod_2.1.2~beta2-2.debian.tar.gz gtkpod_2.1.2~beta2-2.dsc to main/g/gtkpod/gtkpod_2.1.2~beta2-2.dsc gtkpod_2.1.2~beta2-2_amd64.deb to main/g/gtkpod/gtkpod_2.1.2~beta2-2_amd64.deb libatomicparsley-dev_2.1.2~beta2-2_amd64.deb to main/g/gtkpod/libatomicparsley-dev_2.1.2~beta2-2_amd64.deb libatomicparsley0_2.1.2~beta2-2_amd64.deb to main/g/gtkpod/libatomicparsley0_2.1.2~beta2-2_amd64.deb libgtkpod-dev_2.1.2~beta2-2_amd64.deb to main/g/gtkpod/libgtkpod-dev_2.1.2~beta2-2_amd64.deb libgtkpod1_2.1.2~beta2-2_amd64.deb to main/g/gtkpod/libgtkpod1_2.1.2~beta2-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 676...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Matteo F. Vescovi mfv.deb...@gmail.com (supplier of updated gtkpod 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, 12 Jun 2012 09:18:54 +0200 Source: gtkpod Binary: gtkpod gtkpod-data gtkpod-dbg libgtkpod1 libgtkpod-dev libatomicparsley0 libatomicparsley-dev Architecture: source amd64 all Version: 2.1.2~beta2-2 Distribution: unstable Urgency: low Maintainer: gtkpod Maintainers pkg-gtkpod-de...@lists.alioth.debian.org Changed-By: Matteo F. Vescovi mfv.deb...@gmail.com Description: gtkpod - manage songs and playlists on an Apple iPod gtkpod-data - architecture-independent files for gtkpod gtkpod-dbg - debugging symbols for gtkpod libatomicparsley-dev - main library for atomic parsley in gtkpod, development kit libatomicparsley0 - main library for atomic parsley in gtkpod, shared library libgtkpod-dev - main library for the gtkpod package, development kit libgtkpod1 - main library for the gtkpod package, shared library Closes: 676929 676931 Changes: gtkpod (2.1.2~beta2-2) UNRELEASED; urgency=low . * debian/libatomicparsley0.symbols: symbols updated (Closes: #676929) * debian/control: pkg-kde-tools added to b-deps * debian/patches/: #0002 added to fix FTBFS on kBSD64 (Closes: #676931) * debian/watch: uscan opts updated Checksums-Sha1: 6ec04529db1a011c478095a9eac0fe99287825b4 2638 gtkpod_2.1.2~beta2-2.dsc 2b42c4e1eaf4dd0745559c8345df08373f950def 19521 gtkpod_2.1.2~beta2-2.debian.tar.gz dbd59cb8f7cb4c33b26d2b2d15f2c35743591b4c 498868 gtkpod_2.1.2~beta2-2_amd64.deb 333ca677b171971d87fb6334720910e6bbfefbca 1477742 gtkpod-data_2.1.2~beta2-2_all.deb 0b6cc1d2003af9a23675e1e29f9aad82081c55d4 1661828
Bug#676116: mlpost: FTBFS: Command exited with code 1.
Le 05/06/2012 00:29, Lucas Nussbaum a écrit : Source: mlpost Version: 0.8.1-2 [...] + mkdir -p img/ cd img/ ../customdoc/img_doc.byte /dev/null cd .. Command exited with code 1. make[2]: *** [doc] Error 10 Some observations: - mlpost compiles in a sid snapshot of 20120524T111800Z - context/2012.05.24.20120525-1 introduced the failure; mlpost compiles when context is held at 2011.05.18.20110627-2 in an otherwise up-to-date sid chroot - this looks related to #676127 Looking at differences between context versions 2011.05.18.20110627-2 and 2012.05.24.20120525-1, the file /usr/share/texmf/metapost/context/base/mp-tool.mp has disappeared in favour of mp-tool.mpii and mp-tool.mpiv. -- Stéphane -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#676127: ocamlviz: FTBFS: I can't open file `mp-tool'.
reassign 676127 mlpost 0.8.1-2 thanks On 05/06/12 00:30, Lucas Nussbaum wrote: During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part: make[2]: Entering directory `/«PKGBUILDDIR»' cd doc mlpost -latex manual.tex -pdf fig.ml pdflatex manual.tex This is MetaPost, version 1.504 (kpathsea version 6.1.0) (mpost.mp (/usr/share/texlive/texmf-dist/metapost/base/plain.mp Preloading the plain mem file, version 1.004)) (./mlpost9c9b7e.mp ! I can't open file `mp-tool'. l.1 input mp-tool ; % some initializations and auxiliary macros Please type another input file name ! Emergency stop. l.1 input mp-tool ; % some initializations and auxiliary macros Transcript written on mlpost9c9b7e.log. make[2]: *** [doc/manual.pdf] Error 1 Looks like mlpost is broken. I'm re-assigning the bug. A change in src:context broke mlpost but this doesn't affect Squeeze. Regards, -- Mehdi Dogguy مهدي الدڤي http://dogguy.org/ -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#677227: screen: Workaround for #644788 fails to detect a running screen on kfreebsd / process renaming does not work on kfreebsd
On 12/06/12 14:23, Axel Beckert wrote: But on kfreebsd this process renaming don't seem to work. This doesn't seem to be a screen issue but a general kfreebsd issue as the following works as expected on Linux, but not on kfreebsd: $ perl -e '$0 = foobar!; ' Hi Axel, I recall that setproctitle was implemented as a no-op in libbsd. So that is probably a known bug / unimplemented yet. Regards, -- Steven Chamberlain ste...@pyro.eu.org -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#677227: screen: Workaround for #644788 fails to detect a running screen on kfreebsd / process renaming does not work on kfreebsd
Hi, some more details: Axel Beckert wrote: [...] on kfreebsd this process renaming don't seem to work. This doesn't seem to be a screen issue but a general kfreebsd issue as the following works as expected on Linux, but not on kfreebsd: $ perl -e '$0 = foobar!; ' JFTR: hurd-i386 seems not to be affected, works as expected there, too. Happened with kernel 8.2-1-686-smp which seems no more to be available. Will test later if it still happens with current kernels and if so, file a seperated bug report against some kfreebsd-image-* packages. According to lifeng on IRC the same happens with our 9.0 kernel, too. Regards, Axel -- ,''`. | Axel Beckert a...@debian.org, http://people.debian.org/~abe/ : :' : | Debian Developer, ftp.ch.debian.org Admin `. `' | 1024D: F067 EA27 26B9 C3FC 1486 202E C09E 1D89 9593 0EDE `-| 4096R: 2517 B724 C5F6 CA99 5329 6E61 2FF9 CD59 6126 16B5 -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#627235: libpoex-role-sessioninstantiation-perl: Can't locate object method _set_id via package My::Session at /usr/share/perl5/POE/Kernel.pm line 1399.
Hi Dominique On Tue, Jun 12, 2012 at 03:15:00PM +0200, Dominique Dumont wrote: On Tuesday 12 June 2012 14:55:35 Salvatore Bonaccorso wrote: Hi Dominique On Tue, Jun 12, 2012 at 01:11:27PM +0200, Dominique Dumont wrote: The only thing left will be to cleanup libpoe-component-pubsub-perl git repo (used for Debian packages). Nicholas has removed version 0.091317 from CPAN, so our git repo contains a non-existent version... I don't know how to clean this up. If you want to do it yourself: http://pkg-perl.alioth.debian.org/git.html#removing_packages Or if you want to remove it completely instead of motiv it to attic, remove the repo on vasks and update the mrconfig in the meta.git repo. Well, we cannot remove the whole git repo of the package. Only the last commited version (0.091137) is wrong and needs to be cleaned up (or put aside in a branch). Debian still has version 0.05 (which we want to keep), so any further packaging activity must start from tag debian/0.05-1, not from HEAD Ah. I'm sorry I missunderstood then your question. Regards, Salvatore signature.asc Description: Digital signature
Bug#677227: screen: Workaround for #644788 fails to detect a running screen on kfreebsd / process renaming does not work on kfreebsd
Hi Steven, Steven Chamberlain wrote: On 12/06/12 14:23, Axel Beckert wrote: But on kfreebsd this process renaming don't seem to work. This doesn't seem to be a screen issue but a general kfreebsd issue as the following works as expected on Linux, but not on kfreebsd: $ perl -e '$0 = foobar!; ' I recall that setproctitle was implemented as a no-op in libbsd. So that is probably a known bug / unimplemented yet. Thanks for the confirmation! Regards, Axel -- ,''`. | Axel Beckert a...@debian.org, http://people.debian.org/~abe/ : :' : | Debian Developer, ftp.ch.debian.org Admin `. `' | 1024D: F067 EA27 26B9 C3FC 1486 202E C09E 1D89 9593 0EDE `-| 4096R: 2517 B724 C5F6 CA99 5329 6E61 2FF9 CD59 6126 16B5 -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#677127: Versions
Using the rescue mode of the Debian installer I verified that the version of cryptsetup, cryptsetup-bin and libcryptsetup4 is 2:1.4.3-1. I then downgraded to cryptsetup, libcryptsetup and libcryptsetup-dev 2:1.4.1-3, and can now boot my system again. Philipp -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#676569: gcc-4.7: -nostdlib broken, multiarch library path always added
severity 676569 normal
thanks
-nostdlib doesn't say anything about discarding the -L flags. Did this change
with 4.7?
On 07.06.2012 22:14, Thorsten Glaser wrote:
Package: gcc-4.7
Version: 4.7.0-12
Severity: serious
Justification: breaks unrelated software
The following scenario is broken: I would expect the link to fail.
This is a carefully nailed-down testcase to figure out that the
fault is with gcc not binutils.
tg@zigo:~ $ echo 'int login_tty(int); void _exit(int); void _start() {
_exit(login_tty(0)); }' test.c
tg@zigo:~ $ rm -f test.out; gcc -nostdlib -lutil -o test.out test.c; ls -l
test.out
-rwxr-xr-x 1 tg tg 3712 Jun 7 20:09 test.out
Reason behind this is that GNU autoconf generated configure scripts
(and other things like that) use such tests to check whether to add
libraries providing certain functionality to the build. Now if klibc
or dietlibc are used, you don't want to have libraries linked against
eglibc added to the build, as that will eventually fail. Figured this
out while trying to see whether jupp can be built with those libcs.
tg@zigo:~ $ gcc -nostdlib -lutil -o test.out test.c -v 21 | tail -1
/usr/lib/gcc/x86_64-linux-gnu/4.7/collect2 --sysroot=/ --build-id
--no-add-needed --eh-frame-hdr -m elf_x86_64 --hash-style=both
-dynamic-linker /lib64/ld-linux-x86-64.so.2 -o test.out
-L/usr/lib/gcc/x86_64-linux-gnu/4.7
-L/usr/lib/gcc/x86_64-linux-gnu/4.7/../../../x86_64-linux-gnu
-L/usr/lib/gcc/x86_64-linux-gnu/4.7/../../../../lib -L/lib/x86_64-linux-gnu
-L/lib/../lib -L/usr/lib/x86_64-linux-gnu -L/usr/lib/../lib
-L/usr/lib/gcc/x86_64-linux-gnu/4.7/../../.. -lutil /tmp/ccjpTrCm.o
tg@zigo:~ $ $(gcc -nostdlib -lutil -o test.out test.c -v -save-temps 21 |
tail -1) -t
/usr/bin/ld.bfd.real: mode elf_x86_64
-lutil
(/usr/lib/gcc/x86_64-linux-gnu/4.7/../../../x86_64-linux-gnu/libutil.so)
test.o
Here ^ we see nicely how gcc is the culprit adding -L directives,
and that ld uses them at library resolution time.
tg@zigo:~ $ gcc -v
Using built-in specs.
COLLECT_GCC=/usr/bin/gcc-4.7.real
COLLECT_LTO_WRAPPER=/usr/lib/gcc/x86_64-linux-gnu/4.7/lto-wrapper
Target: x86_64-linux-gnu
Configured with: ../src/configure -v --with-pkgversion='Debian 4.7.0-12'
--with-bugurl=file:///usr/share/doc/gcc-4.7/README.Bugs
--enable-languages=c,c++,go,fortran,objc,obj-c++ --prefix=/usr
--program-suffix=-4.7 --enable-shared --enable-linker-build-id
--with-system-zlib --libexecdir=/usr/lib --without-included-gettext
--enable-threads=posix --with-gxx-include-dir=/usr/include/c++/4.7
--libdir=/usr/lib --enable-nls --with-sysroot=/ --enable-clocale=gnu
--enable-libstdcxx-debug --enable-libstdcxx-time=yes
--enable-gnu-unique-object --enable-plugin --enable-objc-gc
--with-arch-32=i586 --with-tune=generic --enable-checking=release
--build=x86_64-linux-gnu --host=x86_64-linux-gnu --target=x86_64-linux-gnu
Thread model: posix
gcc version 4.7.0 (Debian 4.7.0-12)
--
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#676569: gcc-4.7: -nostdlib broken, multiarch library path always added
Processing commands for cont...@bugs.debian.org: severity 676569 normal Bug #676569 [gcc-4.7] gcc-4.7: -nostdlib broken, multiarch library path always added Severity set to 'normal' from 'serious' thanks Stopping processing here. Please contact me if you need assistance. -- 676569: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=676569 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#677127: [pkg-cryptsetup-devel] Bug#677127: Versions
Am 12.06.2012 17:06, schrieb jonas: Hey Philipp, Am 12.06.2012 16:00, schrieb Philipp Klaus Krause: Using the rescue mode of the Debian installer I verified that the version of cryptsetup, cryptsetup-bin and libcryptsetup4 is 2:1.4.3-1. I then downgraded to cryptsetup, libcryptsetup and libcryptsetup-dev 2:1.4.1-3, and can now boot my system again. Thanks for the bugreport. Unfortunately so far I didn't succeed to reproduce the bug. For me, latest packages (2:1.4.3-1) work as expected. Which architecture do hardware, kernel and userland have? Debian unstable, amd64 running on a Core 2 Duo T9300. The kernel is 3.4.0-rc7, from the tarball from kernel.org, compiled using make-kpkg from the kernel-package package. There seems to be another person encountering a similar issue (but they didn't have libcryptsetup4 installed): http://siduction.de/index.php?name=PNphpBB2file=viewtopicp=21186 Philipp -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#677242: virtualbox-guest-x11: Keyboard stops working after some time.
Package: virtualbox-guest-x11 Version: 4.1.16-dfsg-2 Severity: grave Justification: renders package unusable Hello, after Upgrading to virtualbox-guest-* 4.1.16-dfsg-1 my keyboard stops working in X after some minutes using it. The mouse is not affected, CutPaste still works. When i stop the X-Server the keyboard on console is running without problem. My System is a Debian unstable running on a Windows7-host. I couldn't find any information in Virtualbox' log, or inside the Xorg-Log that could be related to the problem. After Downgrading to 4.1.16-dfsg-1 all seems to be ok again for some hours now. Cord -- System Information: Debian Release: wheezy/sid APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'unstable'), (500, 'testing'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 3.2.0-2-amd64 (SMP w/3 CPU cores) 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 virtualbox-guest-x11 depends on: ii libc6 2.13-33 ii libx11-6 2:1.4.99.901-2 ii libxcomposite1 1:0.4.3-2 ii libxdamage11:1.1.3-2 ii libxext6 2:1.3.1-2 ii libxfixes3 1:5.0-4 ii libxmu62:1.1.1-1 ii libxrandr2 2:1.3.2-2 ii libxt6 1:1.1.3-1 ii virtualbox-guest-utils 4.1.16-dfsg-2 ii xserver-xorg-core [xorg-video-abi-12] 2:1.12.1.902-1 virtualbox-guest-x11 recommends no packages. virtualbox-guest-x11 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#629767: marked as done (ember: FTBFS: build-dependency not installable: libceguiogre-dev)
Your message dated Tue, 12 Jun 2012 15:32:45 + with message-id e1set5j-0004rh...@franck.debian.org and subject line Bug#629767: fixed in ember 0.6.2+dfsg-1 has caused the Debian Bug report #629767, regarding ember: FTBFS: build-dependency not installable: libceguiogre-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.) -- 629767: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=629767 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Source: ember Version: 0.5.7-1.1 Severity: serious Tags: wheezy sid User: debian...@lists.debian.org Usertags: qa-ftbfs-20110607 qa-ftbfs Justification: FTBFS on amd64 Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part: ┌──┐ │ Install ember 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-ember-dummy : Depends: libceguiogre-dev but it is not installable E: Broken packages The full build log is available from: http://people.debian.org/~lucas/logs/2011/06/07/ember_0.5.7-1.1_lsid64.buildlog A list of current common problems and possible solutions is available at http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute! About the archive rebuild: The rebuild was done on about 50 AMD64 nodes of the Grid'5000 platform, using a clean chroot. Internet was not accessible from the build systems. -- | Lucas Nussbaum | lu...@lucas-nussbaum.net http://www.lucas-nussbaum.net/ | | jabber: lu...@nussbaum.fr GPG: 1024D/023B3F4F | ---End Message--- ---BeginMessage--- Source: ember Source-Version: 0.6.2+dfsg-1 We believe that the bug you reported is fixed in the latest version of ember, which is due to be installed in the Debian FTP archive: ember_0.6.2+dfsg-1.debian.tar.gz to main/e/ember/ember_0.6.2+dfsg-1.debian.tar.gz ember_0.6.2+dfsg-1.dsc to main/e/ember/ember_0.6.2+dfsg-1.dsc ember_0.6.2+dfsg-1_amd64.deb to main/e/ember/ember_0.6.2+dfsg-1_amd64.deb ember_0.6.2+dfsg.orig.tar.xz to main/e/ember/ember_0.6.2+dfsg.orig.tar.xz A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 629...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Stephen M. Webb stephen.w...@bregmasoft.ca (supplier of updated ember 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: Mon, 04 Jun 2012 11:46:25 -0400 Source: ember Binary: ember Architecture: amd64 source Version: 0.6.2+dfsg-1 Distribution: unstable Urgency: low Maintainer: Debian Games Team pkg-games-de...@lists.alioth.debian.org Changed-By: Stephen M. Webb stephen.w...@bregmasoft.ca Closes: 629767 633854 653970 Description: ember - 3D client framework for the WorldForge project Changes: ember (0.6.2+dfsg-1) unstable; urgency=low . * new upstream release (closes: #633854) - removed dependency on libceguiogre-dev (closes: #629767) * removed old unused build dependencies * converted to 3.0 (quilt) source format, removed obsolete patches * converted to use dh sequencer (compat level 9) * new maintainer: Debian games team (closes: #653970) - added myself as uploader * adjusted paths in installed launcher script to use defaults * used xz compression in packaging * debian/control: updated Standards-Version to 3.9.3 * debian/copyright: changed to computer-readable format (DEP-5) * 0008-replace-fastdeletegate-with-sigc++.patch: replaced FastDelegate - removed non-free code from orig tarball, added +dfsg to version - pulled sigc++ replacement patch from upstream instead * 0009-spelling-bach.patch: fix spelling
Bug#633854: marked as done ([ember] Update or remove)
Your message dated Tue, 12 Jun 2012 15:32:45 + with message-id e1set5j-0004rn...@franck.debian.org and subject line Bug#633854: fixed in ember 0.6.2+dfsg-1 has caused the Debian Bug report #633854, regarding [ember] Update or remove 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.) -- 633854: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=633854 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: ember Version: 0.5.7-1.1 Severity: grave --- Please enter the report below this line. --- 0.5.7 was released almost 2 years ago, with newer versions available for more than a year, even before Squeeze's freeze: 0.5.8 , 0.6.0 and 0.6.1. It depends on OGRE 1.6.4, removed a few months ago from unstable repositories, and it won't be coming back. Apart from that, Ember is a kind of big demo, technology preview of sorts, not a fun and playable game per se. So having a 2 years old technology preview in the archives is pretty useless. Therefore I submit this request for upgrade to 0.6.1 or removal, and with grave severity level because of the complete uselessness of the package in its current incarnation. Cheers. -- Manuel A. Fernandez Montecelo manuel.montez...@gmail.com ---End Message--- ---BeginMessage--- Source: ember Source-Version: 0.6.2+dfsg-1 We believe that the bug you reported is fixed in the latest version of ember, which is due to be installed in the Debian FTP archive: ember_0.6.2+dfsg-1.debian.tar.gz to main/e/ember/ember_0.6.2+dfsg-1.debian.tar.gz ember_0.6.2+dfsg-1.dsc to main/e/ember/ember_0.6.2+dfsg-1.dsc ember_0.6.2+dfsg-1_amd64.deb to main/e/ember/ember_0.6.2+dfsg-1_amd64.deb ember_0.6.2+dfsg.orig.tar.xz to main/e/ember/ember_0.6.2+dfsg.orig.tar.xz A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 633...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Stephen M. Webb stephen.w...@bregmasoft.ca (supplier of updated ember 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: Mon, 04 Jun 2012 11:46:25 -0400 Source: ember Binary: ember Architecture: amd64 source Version: 0.6.2+dfsg-1 Distribution: unstable Urgency: low Maintainer: Debian Games Team pkg-games-de...@lists.alioth.debian.org Changed-By: Stephen M. Webb stephen.w...@bregmasoft.ca Closes: 629767 633854 653970 Description: ember - 3D client framework for the WorldForge project Changes: ember (0.6.2+dfsg-1) unstable; urgency=low . * new upstream release (closes: #633854) - removed dependency on libceguiogre-dev (closes: #629767) * removed old unused build dependencies * converted to 3.0 (quilt) source format, removed obsolete patches * converted to use dh sequencer (compat level 9) * new maintainer: Debian games team (closes: #653970) - added myself as uploader * adjusted paths in installed launcher script to use defaults * used xz compression in packaging * debian/control: updated Standards-Version to 3.9.3 * debian/copyright: changed to computer-readable format (DEP-5) * 0008-replace-fastdeletegate-with-sigc++.patch: replaced FastDelegate - removed non-free code from orig tarball, added +dfsg to version - pulled sigc++ replacement patch from upstream instead * 0009-spelling-bach.patch: fix spelling mistake * 0010-fix-ember-script-args.patch: fix argument handling in script * 0011-qualify-template-function.patch: fixes FTBFS using GCC 4.7 * 0012-fix-osdir-headers: adds required headers for POSIX. * 0013-remove-invalid-linker-flags.patch: remove an invalid linker flag Checksums-Sha1: 87e2707a2e793daa5fc823118a0491b16a5d6cef 2283 ember_0.6.2+dfsg-1.dsc df85ad73fc223997a0b6b539dd0cf15017cfc327 1744568 ember_0.6.2+dfsg.orig.tar.xz 1ff0ff0cfb461e06e1aaebe663b20c1b2a745ef4 11304 ember_0.6.2+dfsg-1.debian.tar.gz f25d70edd5cea32d626179613293b44887fb58cf 1779634 ember_0.6.2+dfsg-1_amd64.deb Checksums-Sha256: efaff3209c7d2e6d4aab88583ca249e951abc9f71a8d8b7d5c9a718e417c6585 2283 ember_0.6.2+dfsg-1.dsc 2d95b985df7366fad727ee11c9815fe7c7416cc94b50c1f84c4a32d43f6954c8 1744568 ember_0.6.2+dfsg.orig.tar.xz af31d57b247d82633f69e0152b6610a3e71ccfa820782097d8900cfc9caa104c 11304
Bug#669587: marked as done (latex-xcolor: unowned file /usr/local/share/texmf/ls-R after purge (policy 6.8, 9.1.2))
Your message dated Tue, 12 Jun 2012 15:37:50 + with message-id e1setae-0004ko...@franck.debian.org and subject line Bug#669587: fixed in latex-xcolor 2.11-1.1 has caused the Debian Bug report #669587, regarding latex-xcolor: 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.) -- 669587: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=669587 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: latex-xcolor Version: 2.11-1 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 latex-xcolor_2.11-1.log.gz Description: GNU Zip compressed data ---End Message--- ---BeginMessage--- Source: latex-xcolor Source-Version: 2.11-1.1 We believe that the bug you reported is fixed in the latest version of latex-xcolor, which is due to be installed in the Debian FTP archive: latex-xcolor_2.11-1.1.diff.gz to main/l/latex-xcolor/latex-xcolor_2.11-1.1.diff.gz latex-xcolor_2.11-1.1.dsc to main/l/latex-xcolor/latex-xcolor_2.11-1.1.dsc latex-xcolor_2.11-1.1_all.deb to main/l/latex-xcolor/latex-xcolor_2.11-1.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 669...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Thomas Preud'homme robo...@celest.fr (supplier of updated latex-xcolor package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Wed, 23 May 2012 17:07:57 +0200 Source: latex-xcolor Binary: latex-xcolor Architecture: all source Version: 2.11-1.1 Distribution: unstable Urgency: medium Maintainer: OHURA Makoto oh...@debian.org Changed-By: Thomas Preud'homme robo...@celest.fr Closes: 669587 Description: latex-xcolor - Easy driver-independent TeX class for color Changes: latex-xcolor (2.11-1.1) unstable; urgency=medium . * Non-maintainer upload. * debian/rules: - Use dh_installtex to generate calls to mktexlsr in postinst and postrm in order to avoid creating /usr/local/share/texmf/ls-R (Closes: #669587). * Remove useless preinst and prerm scripts. Checksums-Sha1: 51151b1a3ab3d0dd5d18c5f6f3208c3713ae3a21 1723 latex-xcolor_2.11-1.1.dsc 5cfc3c2a74324a2e53cea6cc9a09f5a9c8cef371 7748 latex-xcolor_2.11-1.1.diff.gz 57715db070a03e07ee7ea7e53bb71d3b35928dc0 609614 latex-xcolor_2.11-1.1_all.deb Checksums-Sha256: d2c82c9b641716c082e8a4b14eb40b129e5df3118f543791769223b8a2a7b564 1723 latex-xcolor_2.11-1.1.dsc 404343eebaff73df8cc2e6f97a9d3847d25f55aeefdc5155b1923632e3bb79d4 7748 latex-xcolor_2.11-1.1.diff.gz e68522031842385f22fe4aef202cd3bcfe37ef916fcf817d94fa455da7d26292 609614 latex-xcolor_2.11-1.1_all.deb Files: e05e5dfd08e6702d36483d7aacdc65cd 1723 tex optional latex-xcolor_2.11-1.1.dsc f460e28f76c5bd74e0a0f4bf8deb1574 7748 tex optional latex-xcolor_2.11-1.1.diff.gz e41a617019e902f181b76e7096fd632c 609614 tex optional
Bug#674212: marked as done (libalkimia: ftbs missing dependency on pkg-config)
Your message dated Tue, 12 Jun 2012 15:38:02 + with message-id e1setaq-0004ly...@franck.debian.org and subject line Bug#674212: fixed in libalkimia 4.3.2-1.1 has caused the Debian Bug report #674212, regarding libalkimia: ftbs missing dependency on pkg-config 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.) -- 674212: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=674212 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: libalkimia Version: 4.3.2-1 Severity: serious libalkimia fails to build from source it needs pkg-config but does not depend on it. CMake Error at /usr/share/cmake-2.8/Modules/FindPackageHandleStandardArgs.cmake:97 (MESSAGE): Could NOT find PkgConfig (missing: PKG_CONFIG_EXECUTABLE) Call Stack (most recent call first): /usr/share/cmake-2.8/Modules/FindPackageHandleStandardArgs.cmake:288 (_FPHSA_FAILURE_MESSAGE) /usr/share/cmake-2.8/Modules/FindPkgConfig.cmake:102 (find_package_handle_standard_args) libalkimia/CMakeLists.txt:35 (find_package) See also attached log. libalkimia_4.3.2-1.log.gz Description: GNU Zip compressed data signature.asc Description: OpenPGP digital signature ---End Message--- ---BeginMessage--- Source: libalkimia Source-Version: 4.3.2-1.1 We believe that the bug you reported is fixed in the latest version of libalkimia, which is due to be installed in the Debian FTP archive: libalkimia-dev_4.3.2-1.1_amd64.deb to main/liba/libalkimia/libalkimia-dev_4.3.2-1.1_amd64.deb libalkimia4_4.3.2-1.1_amd64.deb to main/liba/libalkimia/libalkimia4_4.3.2-1.1_amd64.deb libalkimia_4.3.2-1.1.debian.tar.gz to main/liba/libalkimia/libalkimia_4.3.2-1.1.debian.tar.gz libalkimia_4.3.2-1.1.dsc to main/liba/libalkimia/libalkimia_4.3.2-1.1.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. gregor herrmann gre...@debian.org (supplier of updated libalkimia 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: Sun, 10 Jun 2012 15:38:21 +0200 Source: libalkimia Binary: libalkimia4 libalkimia-dev Architecture: source amd64 Version: 4.3.2-1.1 Distribution: unstable Urgency: low Maintainer: Debian KDE Extras Team pkg-kde-ext...@lists.alioth.debian.org Changed-By: gregor herrmann gre...@debian.org Description: libalkimia-dev - Financial library - Development files libalkimia4 - Financial library common classes for KDE SC Closes: 674212 Changes: libalkimia (4.3.2-1.1) unstable; urgency=low . * Non-maintainer upload. * Fix ftbs missing dependency on pkg-config: add it. (Closes: #674212) Checksums-Sha1: c531043a0df36cab6f1ac694cb44646088ba12b8 1995 libalkimia_4.3.2-1.1.dsc b2676079a4d65dcb8c403df1265f2014154e3d7b 2263 libalkimia_4.3.2-1.1.debian.tar.gz 400780be2edc578673a5f82efde99aaec5d304c7 23344 libalkimia4_4.3.2-1.1_amd64.deb 0c93f39cc48fac179fda2a4d921812d8a886b368 6338 libalkimia-dev_4.3.2-1.1_amd64.deb Checksums-Sha256: 52d227293f0e62e861f7d24e72836b29f5651e1a50bd2c42dcf5069369d998df 1995 libalkimia_4.3.2-1.1.dsc 24798309c7b6a7b7d05727fa53111df110de8a260d0794758a928413499d01dc 2263 libalkimia_4.3.2-1.1.debian.tar.gz 3a804ba2c7a2d6dca6c20dc34946ef8746728dc99bc2f31d5b87089e50a75b3c 23344 libalkimia4_4.3.2-1.1_amd64.deb d7e1a4bf19a147072292784125c4b271c63c3c1d3c6027ed0eb4206a975f51e9 6338 libalkimia-dev_4.3.2-1.1_amd64.deb Files: 23f41d482acb82d844cb72a401972b72 1995 kde optional libalkimia_4.3.2-1.1.dsc 801a1718adf9d67cae3e0c250ed1864c 2263 kde optional libalkimia_4.3.2-1.1.debian.tar.gz 0941c94213e48d0687f6110ac31f34fe 23344 kde optional libalkimia4_4.3.2-1.1_amd64.deb 2254a2f2dfd91cb60e93c9a6c2196af6 6338 libdevel extra libalkimia-dev_4.3.2-1.1_amd64.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.12 (GNU/Linux) iQIcBAEBCAAGBQJP1KOPAAoJELs6aAGGSaoG/vIQAKBpndJNUYkJSeRlceaxN736 0imA+UJeGiebql1h6tpRhorbClm8F1aDMaos5ghIxQhXE6l5LwZu+Xq2DgsqSHiC 400BwRpp6C8eB9IsjjWdsx6zIDrnDKYhah6SHzsKjl5KwVO7WxoG55SbH/T/xG8S MHfdMVc40sLmK8dTcM0v/x+ZKANWNB7ul0cr4OB3w8vsPYn87Swy8czBp0Gzf6vQ DoDX/WLS2iUlPGA3X6oVo3WHQ68NgwqJBEPyZn3vDhSSRy2X2RyRHzqGT7D3jOVi dqeEqfVHrZtraS4aUuI5L2iQBegYYY0mA7tXp8huNODoWSAgmu6qkAxV368ItaXo
Bug#677127: [pkg-cryptsetup-devel] Bug#677127: Versions
Hey Philipp, Am 12.06.2012 16:00, schrieb Philipp Klaus Krause: Using the rescue mode of the Debian installer I verified that the version of cryptsetup, cryptsetup-bin and libcryptsetup4 is 2:1.4.3-1. I then downgraded to cryptsetup, libcryptsetup and libcryptsetup-dev 2:1.4.1-3, and can now boot my system again. Thanks for the bugreport. Unfortunately so far I didn't succeed to reproduce the bug. For me, latest packages (2:1.4.3-1) work as expected. Which architecture do hardware, kernel and userland have? Regards, jonas -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#670053: marked as done (rdkit: FTBFS on mips / s390 (terminated due to inactivity))
Your message dated Tue, 12 Jun 2012 15:39:51 + with message-id e1setcb-0004rm...@franck.debian.org and subject line Bug#670053: fixed in rdkit 201203-2 has caused the Debian Bug report #670053, regarding rdkit: FTBFS on mips / s390 (terminated due to inactivity) 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.) -- 670053: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=670053 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Source: rdkit Version: 201112-1 Severity: serious Tags: wheezy sid Hi, rdkit FTBFS on mips / s390 due to the build being auto-killed after a period of inactivity. From the mips build log: 27/76 Test #27: smaTest1 . Passed 38.28 sec Start 28: fileParsersTest1 make[1]: *** [override_dh_auto_test] Terminated make[2]: *** [test] Terminated make: *** [build-arch] Terminated E: Caught signal 'Terminated': terminating immediately Build killed with signal TERM after 300 minutes of inactivity Full logs available via https://buildd.debian.org/status/package.php?p=rdkit Regards, Adam ---End Message--- ---BeginMessage--- Source: rdkit Source-Version: 201203-2 We believe that the bug you reported is fixed in the latest version of rdkit, which is due to be installed in the Debian FTP archive: librdkit-dev_201203-2_amd64.deb to main/r/rdkit/librdkit-dev_201203-2_amd64.deb librdkit1_201203-2_amd64.deb to main/r/rdkit/librdkit1_201203-2_amd64.deb python-rdkit_201203-2_amd64.deb to main/r/rdkit/python-rdkit_201203-2_amd64.deb rdkit-data_201203-2_all.deb to main/r/rdkit/rdkit-data_201203-2_all.deb rdkit-doc_201203-2_all.deb to main/r/rdkit/rdkit-doc_201203-2_all.deb rdkit_201203-2.debian.tar.gz to main/r/rdkit/rdkit_201203-2.debian.tar.gz rdkit_201203-2.dsc to main/r/rdkit/rdkit_201203-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 670...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Michael Banck mba...@debian.org (supplier of updated rdkit 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, 12 Jun 2012 13:45:10 +0200 Source: rdkit Binary: python-rdkit rdkit-doc rdkit-data librdkit1 librdkit-dev Architecture: source amd64 all Version: 201203-2 Distribution: unstable Urgency: low Maintainer: Michael Banck mba...@debian.org Changed-By: Michael Banck mba...@debian.org Description: librdkit-dev - Collection of cheminformatics and machine-learning software (deve librdkit1 - Collection of cheminformatics and machine-learning software (shar python-rdkit - Collection of cheminformatics and machine-learning software rdkit-data - Collection of cheminformatics and machine-learning software (data rdkit-doc - Collection of cheminformatics and machine-learning software (docu Closes: 670053 670054 Changes: rdkit (201203-2) unstable; urgency=low . * debian/rules (override_dh_auto_test): Deactivated for now (Closes: #670053, #670054). Checksums-Sha1: cbda4bb5550326f5fd7370f660f94fb2b9b11074 1582 rdkit_201203-2.dsc c3f400d169206e70452f928943bb568a969fbfd6 5346 rdkit_201203-2.debian.tar.gz 9c05ef71e8b03fe7c4a4a57241a51744b26d5db4 2711414 python-rdkit_201203-2_amd64.deb 1e34f432e13ebdff6a6888ee1e436993f4edf215 3010080 rdkit-doc_201203-2_all.deb 3ad4bbdf65278b734303e717f099c3e5158923d6 452702 rdkit-data_201203-2_all.deb 1ef697e2be9b828159ea94bfcad07412826377c1 1972334 librdkit1_201203-2_amd64.deb f9679951ef354fe57b5c0b25757e5254e4d58cba 156286 librdkit-dev_201203-2_amd64.deb Checksums-Sha256: 010df32c91f5eccf2c5c79bb6d2a9c9fdee0bdf9ac236067ec0096eccdb36441 1582 rdkit_201203-2.dsc c91539908bd1768862837219484aa8072aea052946a83dba36cacb4c72b62e9d 5346 rdkit_201203-2.debian.tar.gz e69e2c7feb61d7b939e77a587ff6a1c03b5f817e8837351fe0c2a636dd84ed86 2711414 python-rdkit_201203-2_amd64.deb 0b7b4453874947e0ec3ccd4de9425e42c71834bb8950e7552f36a7a301815e6c 3010080 rdkit-doc_201203-2_all.deb 738380b263499d63a4390e4ee48f2f1d50429c71cc131e3af6f01be3682864c8 452702 rdkit-data_201203-2_all.deb 493e630781d79d1118fab313e947af7711df6c1b2f9e5d6747bf4e262f1789c9 1972334 librdkit1_201203-2_amd64.deb 07ae6608b6272f5cf16ac1a5ceef3d641a030d0c6103a24099f4ce2c41728e04 156286
Bug#670054: marked as done (rdkit: FTFBS on powerpc / s390x / sparc (test suite failures))
Your message dated Tue, 12 Jun 2012 15:39:51 + with message-id e1setcb-0004rs...@franck.debian.org and subject line Bug#670054: fixed in rdkit 201203-2 has caused the Debian Bug report #670054, regarding rdkit: FTFBS on powerpc / s390x / sparc (test suite failures) 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.) -- 670054: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=670054 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Source: rdkit Version: 201112-1 Severity: serious Tags: wheezy sid Hi, rdkit FTBFS on powerpc, s390x and sparc due to test suite failures. From the powerpc build log: 88% tests passed, 9 tests failed out of 76 Total Test time (real) = 113.88 sec The following tests FAILED: 2 - testDataStructs (OTHER_FAULT) 4 - pyDiscreteValueVect (Failed) 5 - pySparseIntVect (Failed) 7 - testGrid (OTHER_FAULT) 22 - graphmoltestPickler (OTHER_FAULT) 42 - pyMolDescriptors (Failed) 66 - pyCMIM (Failed) 67 - pyRanker (Failed) 69 - pyFeatures (Failed) Errors while running CTest make[2]: *** [test] Error 8 make[2]: Leaving directory `/build/buildd-rdkit_201112-1-powerpc-PES4nC/rdkit-201112/obj-powerpc-linux-gnu' dh_auto_test: make -j1 test ARGS+=-j1 returned exit code 2 make[1]: *** [override_dh_auto_test] Error 29 make[1]: Leaving directory `/build/buildd-rdkit_201112-1-powerpc-PES4nC/rdkit-201112' make: *** [build] Error 2 dpkg-buildpackage: error: debian/rules build gave error exit status 2 Full logs available via https://buildd.debian.org/status/package.php?p=rdkit Regards, Adam ---End Message--- ---BeginMessage--- Source: rdkit Source-Version: 201203-2 We believe that the bug you reported is fixed in the latest version of rdkit, which is due to be installed in the Debian FTP archive: librdkit-dev_201203-2_amd64.deb to main/r/rdkit/librdkit-dev_201203-2_amd64.deb librdkit1_201203-2_amd64.deb to main/r/rdkit/librdkit1_201203-2_amd64.deb python-rdkit_201203-2_amd64.deb to main/r/rdkit/python-rdkit_201203-2_amd64.deb rdkit-data_201203-2_all.deb to main/r/rdkit/rdkit-data_201203-2_all.deb rdkit-doc_201203-2_all.deb to main/r/rdkit/rdkit-doc_201203-2_all.deb rdkit_201203-2.debian.tar.gz to main/r/rdkit/rdkit_201203-2.debian.tar.gz rdkit_201203-2.dsc to main/r/rdkit/rdkit_201203-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 670...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Michael Banck mba...@debian.org (supplier of updated rdkit 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, 12 Jun 2012 13:45:10 +0200 Source: rdkit Binary: python-rdkit rdkit-doc rdkit-data librdkit1 librdkit-dev Architecture: source amd64 all Version: 201203-2 Distribution: unstable Urgency: low Maintainer: Michael Banck mba...@debian.org Changed-By: Michael Banck mba...@debian.org Description: librdkit-dev - Collection of cheminformatics and machine-learning software (deve librdkit1 - Collection of cheminformatics and machine-learning software (shar python-rdkit - Collection of cheminformatics and machine-learning software rdkit-data - Collection of cheminformatics and machine-learning software (data rdkit-doc - Collection of cheminformatics and machine-learning software (docu Closes: 670053 670054 Changes: rdkit (201203-2) unstable; urgency=low . * debian/rules (override_dh_auto_test): Deactivated for now (Closes: #670053, #670054). Checksums-Sha1: cbda4bb5550326f5fd7370f660f94fb2b9b11074 1582 rdkit_201203-2.dsc c3f400d169206e70452f928943bb568a969fbfd6 5346 rdkit_201203-2.debian.tar.gz 9c05ef71e8b03fe7c4a4a57241a51744b26d5db4 2711414 python-rdkit_201203-2_amd64.deb 1e34f432e13ebdff6a6888ee1e436993f4edf215 3010080 rdkit-doc_201203-2_all.deb 3ad4bbdf65278b734303e717f099c3e5158923d6 452702 rdkit-data_201203-2_all.deb 1ef697e2be9b828159ea94bfcad07412826377c1 1972334 librdkit1_201203-2_amd64.deb f9679951ef354fe57b5c0b25757e5254e4d58cba 156286 librdkit-dev_201203-2_amd64.deb Checksums-Sha256: 010df32c91f5eccf2c5c79bb6d2a9c9fdee0bdf9ac236067ec0096eccdb36441 1582 rdkit_201203-2.dsc
Bug#677244: xen-utils-common: xen-toolstack fails if either `xm` or `xl` is not found in xen-dir
Package: xen-utils-common Version: 4.1.2-7 Severity: grave Tags: patch Justification: renders package unusable Dear Maintainer, The script /usr/lib/xen-common/bin/xen-toolstack improperly aborts if *either* `xm` or `xl` cannot be found in the xen-dir (/usr/lib/xen-4.0/bin). This means that a default installation (e.g. following Debian wiki on the subject, namely installing xen-linux-system and xen-tools without any configuration) will NOT be usable as-is because it cannot find an usable toolstack. This is due to a bug in the error handling of the xen-toolstack script when it comes to checking the availability of `xm` and `xl`. Since the script is run with `sh -e` and the return value of `command -v` isn't used, the script aborts. Attached is a tiny patch fixing the issue by using the `command -v` return value. Best regards, Colomban -- System Information: Debian Release: wheezy/sid APT prefers unstable APT policy: (500, 'unstable'), (500, 'testing'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 3.2.0-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/dash Versions of packages xen-utils-common depends on: ii gawk1:4.0.1+dfsg-2 ii lsb-base4.1+Debian7 ii python 2.7.3~rc2-1 ii ucf 3.0025+nmu3 ii udev175-3.1 ii xenstore-utils 4.1.2-7 xen-utils-common recommends no packages. xen-utils-common suggests no packages. -- no debconf information --- /usr/lib/xen-common/bin/xen-toolstack 2012-05-22 10:52:37.0 +0200 +++ xen-toolstack 2012-06-12 17:40:37.174403052 +0200 @@ -11,7 +11,7 @@ else PATH=$dir/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin fi -command -v $1 +command -v $1 || true } if [ -e $configfile ]; then
Bug#677127: relocation error
On 06/11/2012 09:31 PM, p...@spth.de wrote: /sbin/crpytsetup: relocation error: /sbin/cryptsetup: symbol crypt_activate_by_key_file_offste, version CRYPTSETUP_1.0 not defined in file libcryptsetup.so.4 with link time reference just if it helps: crypt_activate_by_key_file_offset was added in 1.4.2 libcryptsetup, library is backward compatible but not forward compatible of course. Isn't possible that you have in initramfs old libcryptsetup.4 but new cryptsetup binary? (it should have proper version set, so it should be visible even for *.so symlink) Milan -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#670221: plptools: fails to install due to insserv rejecting the script header
On Tue, 24 Apr 2012 10:27:07 +0200, Andreas Beckmann wrote:
From the attached log (scroll to the bottom...):
Selecting previously unselected package plptools.
(Reading database ... 6917 files and directories currently installed.)
Unpacking plptools (from .../plptools_1.0.9-2.3_amd64.deb) ...
Setting up plptools (1.0.9-2.3) ...
insserv: Service fuse has to be enabled to start service plptools
insserv: exiting now!
update-rc.d: error: insserv rejected the script header
dpkg: error processing plptools (--configure):
subprocess installed post-installation script returned error exit status 1
Errors were encountered while processing:
plptools
This looks like an explicit dependency on fuse (or whichever package
provides the 'fuse' service) is missing. This was working previously
because some dependency chain fulfilled this, but other packages have
changed and therefore this no longer works.
Hm, seems to be there:
[source package]
Package: plptools
Architecture: linux-any kfreebsd-any
Depends: ${shlibs:Depends},${misc:Depends}, fuse [linux-any] | fuse4bsd
[kfreebsd-any]
[apt-cache show on amd64]
Package: plptools
Version: 1.0.9-2.3
Architecture: amd64
Depends: libc6 (= 2.2.5), libgcc1 (= 1:4.1.1), libncurses5 (= 5.5-5~),
libreadline6 (= 6.0), libstdc++6 (= 4.4.0), libtinfo5, debconf (= 0.5) |
debconf-2.0, fuse
I can reproduce the error in a cowbuilder chroot (piuparts doesn't
like me today):
# cowbuilder --login
[..]
# apt-get install plptools
Reading package lists... Done
Building dependency tree
Reading state information... Done
The following extra packages will be installed:
adduser fuse libfuse2 libudev0 udev
Suggested packages:
liblocale-gettext-perl
Recommended packages:
usbutils pciutils
The following NEW packages will be installed:
adduser fuse libfuse2 libudev0 plptools udev
0 upgraded, 6 newly installed, 0 to remove and 0 not upgraded.
Need to get 289 kB/1222 kB of archives.
After this operation, 3362 kB of additional disk space will be used.
Do you want to continue [Y/n]?
Get:1 http://ftp.at.debian.org/debian/ sid/main fuse amd64 2.9.0-1 [72.3 kB]
Get:2 http://ftp.at.debian.org/debian/ sid/main plptools amd64 1.0.9-2.3 [216
kB]
Fetched 289 kB in 0s (527 kB/s)
debconf: delaying package configuration, since apt-utils is not installed
Selecting previously unselected package libudev0:amd64.
(Reading database ... 10976 files and directories currently installed.)
Unpacking libudev0:amd64 (from .../libudev0_175-3.1_amd64.deb) ...
Selecting previously unselected package udev.
Unpacking udev (from .../udev_175-3.1_amd64.deb) ...
Selecting previously unselected package libfuse2:amd64.
Unpacking libfuse2:amd64 (from .../libfuse2_2.9.0-1_amd64.deb) ...
Selecting previously unselected package adduser.
Unpacking adduser (from .../adduser_3.113+nmu3_all.deb) ...
Selecting previously unselected package fuse.
Unpacking fuse (from .../fuse_2.9.0-1_amd64.deb) ...
Selecting previously unselected package plptools.
Unpacking plptools (from .../plptools_1.0.9-2.3_amd64.deb) ...
Setting up libudev0:amd64 (175-3.1) ...
Setting up udev (175-3.1) ...
A chroot environment has been detected, udev not started.
Setting up libfuse2:amd64 (2.9.0-1) ...
Setting up adduser (3.113+nmu3) ...
Setting up fuse (2.9.0-1) ...
Creating fuse group...
Adding group `fuse' (GID 102) ...
Done.
MAKEDEV not installed, skipping device node creation.
Setting up plptools (1.0.9-2.3) ...
insserv: Service fuse has to be enabled to start service plptools
insserv: exiting now!
update-rc.d: error: insserv rejected the script header
dpkg: error processing plptools (--configure):
subprocess installed post-installation script returned error exit status 1
Errors were encountered while processing:
plptools
E: Sub-process /usr/bin/dpkg returned an error code (1)
But I don't think that this is plptools's fault if fuse is not provided.
Or is it?
Hm.
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: Lucia Lago Lusson Bueno: Sublime Illusion
signature.asc
Description: Digital signature
Bug#677018: [debian-mysql] Bug#677018: more information
On Tue, Jun 12, 2012 at 08:57:28AM +0100, Nicholas Bamber wrote: Henri, I seem to recall that this bug is fixed in 5.5.24 which actually is in testing. The migration is not yet complete and probably still has a week or two to go at the least. But does that change your calculations at all. What do you mean by calculations? Please close the bug if it is handled. At least running the oneliner in Debian squeeze MySQL-server using the client-package squeeze is not affected. - Henri Salo -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#670221: plptools: fails to install due to insserv rejecting the script header
On 2012-06-12 18:07, gregor herrmann wrote: But I don't think that this is plptools's fault if fuse is not provided. /etc/init.d/fuse is gone: fuse (2.8.7-2) unstable; urgency=low . * Removing initscript in favour of udev rule, thanks to Josh Triplett j...@joshtriplett.org (Closes: #667988, #601546). So plptools initascript needs to stop depending on it Andreas -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#677254: busybox: FTBFS[kfreebsd]: error: storage size of 'info' isn't known
Package: src:busybox Version: 1:1.20.0-3 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: LD procps/built-in.o CC procps/kill.o CC procps/pidof.o CC procps/ps.o procps/ps.c: In function 'ps_main': procps/ps.c:638:17: error: storage size of 'info' isn't known procps/ps.c:698:3: warning: implicit declaration of function 'sysinfo' [-Wimplicit-function-declaration] procps/ps.c:638:17: warning: unused variable 'info' [-Wunused-variable] make[2]: *** [procps/ps.o] Error 1 make[1]: *** [procps] Error 2 make[1]: Leaving directory `/build/buildd-busybox_1.20.0-3-kfreebsd-amd64-kk5cZ7/busybox-1.20.0/debian/build/udeb' make: *** [debian/build/udeb/.built] Error 2 Full build log at https://buildd.debian.org/status/logs.php?pkg=busyboxver=1%3A1.20.0-3arch=kfreebsd-amd64 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 -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#677259: netams: FTBFS[kfreebsd]: undefined reference to `crypt'
Package: src:netams Version: 3.4.5-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: g++ billing.o s_billing.o main.o common.o versions.o connections.o security.o services.o s_server.o users.o net_units.o s_processor.o messages_fifo.o s_datasource.o policy.o s_storage.o st_hash.o st_sql.o p_prefix.o s_alerter.o s_scheduler.o ds_netflow.o s_html.o s_monitor.o s_quotactl.o s_quota.o st_sql_mysql.o st_sql_oracle.o st_sql_postgres.o iptree.o s_login.o flow.o flowengine.o ds_ipq.o ds_libpcap.o ds_ipfw.o memory.o events.o html.o bw.o ds_ulog.o ds_netgraph.o attrlist.o time.o st_radius.o s_acl_server.o mutex.o lang.o cli.o layer7.o ds_raw.o list.o versions_build.o -L../lib -lnetams -pthread -lpcap -lmysqlclient -L/usr/lib -lglib-2.0 -L/usr/lib -lnetgraph -L../lib -lcli -o netams security.o: In function `CryptWord(char*)': /build/buildd-netams_3.4.5-2.1+b1-kfreebsd-i386-7bwblx/netams-3.4.5/src/security.c:55: undefined reference to `crypt' net_units.o: In function `NetUnitsList::listPasswordsHtml(_IO_FILE*)': /build/buildd-netams_3.4.5-2.1+b1-kfreebsd-i386-7bwblx/netams-3.4.5/src/net_units.c:415: undefined reference to `crypt' ../lib/libcli.a(libcli.o): In function `pass_matches': /build/buildd-netams_3.4.5-2.1+b1-kfreebsd-i386-7bwblx/netams-3.4.5/lib/libcli/libcli.c:924: undefined reference to `crypt' collect2: error: ld returned 1 exit status make[2]: *** [netams] Error 1 Full build log at https://buildd.debian.org/status/logs.php?pkg=netamsver=3.4.5-2.1%2Bb1arch=kfreebsd-i386 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 -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#677260: xserver-xorg-video-openchrome: FTBFS[kfreebsd]: error: unknown type name 'uint8_t'
Package: src:xserver-xorg-video-openchrome Version: 1:0.2.906-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: In file included from /usr/include/libdrm/via_drm.h:27:0, from ../../src/via_xvmc.h:29, from ../../libxvmc/viaXvMCPriv.h:34, from ../../libxvmc/viaLowLevel.c:34: /usr/include/libdrm/drm.h:50:1: error: unknown type name 'uint8_t' /usr/include/libdrm/drm.h:52:1: error: unknown type name 'uint16_t' /usr/include/libdrm/drm.h:54:1: error: unknown type name 'uint32_t' /usr/include/libdrm/drm.h:56:1: error: unknown type name 'uint64_t' make[3]: *** [libchromeXvMC_la-viaLowLevel.lo] Error 1 Full build log at https://buildd.debian.org/status/fetch.php?pkg=xserver-xorg-video-openchromearch=kfreebsd-i386ver=1%3A0.2.906-1stamp=1339164249 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 -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#677261: vsftpd: FTBFS[kfreebsd-amd64 mips{,el}]: relocation R_X86_64_32 against `.rodata.str1.1' can not be used when making a shared object; recompile with -fPIC
Package: src:vsftpd Version: 3.0.0-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: gcc -o vsftpd main.o utility.o prelogin.o ftpcmdio.o postlogin.o privsock.o tunables.o ftpdataio.o secbuf.o ls.o postprivparent.o logging.o str.o netstr.o sysstr.o strlist.o banner.o filestr.o parseconf.o secutil.o ascii.o oneprocess.o twoprocess.o privops.o standalone.o hash.o tcpwrap.o ipaddrparse.o access.o features.o readwrite.o opts.o ssl.o sslslave.o ptracesandbox.o ftppolicy.o sysutil.o sysdeputil.o seccompsandbox.o -fPIE -pie -Wl,-z,relro -Wl,-z,now -lwrap -lpam -lssl -lcrypto /usr/bin/ld: main.o: relocation R_X86_64_32 against `.rodata.str1.1' can not be used when making a shared object; recompile with -fPIC main.o: could not read symbols: Bad value collect2: error: ld returned 1 exit status make[2]: *** [vsftpd] Error 1 Similar for mips* Full build log at https://buildd.debian.org/status/logs.php?pkg=vsftpdver=3.0.0-1arch=kfreebsd-amd64 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 -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#677018: [debian-mysql] Bug#677018: more information
I believe Clint is updating squeeze just to be safe. We will be updating wheezy just to be safe. Most likely both updates would have happened anyway. On 12/06/12 17:10, Henri Salo wrote: On Tue, Jun 12, 2012 at 08:57:28AM +0100, Nicholas Bamber wrote: Henri, I seem to recall that this bug is fixed in 5.5.24 which actually is in testing. The migration is not yet complete and probably still has a week or two to go at the least. But does that change your calculations at all. What do you mean by calculations? Please close the bug if it is handled. At least running the oneliner in Debian squeeze MySQL-server using the client-package squeeze is not affected. - Henri Salo -- 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#676127: ocamlviz: FTBFS: I can't open file `mp-tool'.
Processing commands for cont...@bugs.debian.org: reassign 676127 mlpost 0.8.1-2 Bug #676127 [src:ocamlviz] ocamlviz: FTBFS: I can't open file `mp-tool'. Bug reassigned from package 'src:ocamlviz' to 'mlpost'. No longer marked as found in versions ocamlviz/1.01-2. Ignoring request to alter fixed versions of bug #676127 to the same values previously set Bug #676127 [mlpost] ocamlviz: FTBFS: I can't open file `mp-tool'. Marked as found in versions mlpost/0.8.1-2. thanks Stopping processing here. Please contact me if you need assistance. -- 676127: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=676127 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 still FTBFS (on some arches)
found 665054 1.10-1 bye Still happening on mips* and kfreebsd* Regards Christoph -- 9FED 5C6C E206 B70A 5857 70CA 9655 22B9 D49A E731 Debian Developer | Lisp Hacker | CaCert Assurer -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed (with 4 errors): dwarves-dfsg still FTBFS (on some arches)
Processing commands for cont...@bugs.debian.org:
found 665054 1.10-1
Bug #665054 {Done: Thomas Girard thomas.g.gir...@free.fr} [src:dwarves-dfsg]
dwarves-dfsg: FTBFS: make[3]: *** No rule to make target `/usr/lib/libdw.so',
needed by `codiff'. Stop.
Marked as found in versions dwarves-dfsg/1.10-1; no longer marked as fixed in
versions dwarves-dfsg/1.10-1 and reopened.
bye
Unknown command or malformed arguments to command.
Still happening on mips* and kfreebsd*
Unknown command or malformed arguments to command.
Regards
Unknown command or malformed arguments to command.
Christoph
Unknown command or malformed arguments to command.
--
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#669559: marked as done (xserver-xorg-video-mach64: FTBFS: cp: cannot stat `debian/tmp/usr/share/man': No such file or directory)
Your message dated Tue, 12 Jun 2012 18:31:08 +0200 with message-id 20120612163108.ga15...@jadzia.comodo.priv.at and subject line Re: Bug#669559: xserver-xorg-video-mach64: FTBFS: cp: cannot stat `debian/tmp/usr/share/man': No such file or directory has caused the Debian Bug report #669559, regarding xserver-xorg-video-mach64: FTBFS: cp: cannot stat `debian/tmp/usr/share/man': 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.) -- 669559: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=669559 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Source: xserver-xorg-video-mach64 Version: 6.9.1-1 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: make[1]: Entering directory `/«PKGBUILDDIR»' find debian/tmp -name '*.la' -delete dh_install --fail-missing cp: cannot stat `debian/tmp/usr/share/man': No such file or directory dh_install: cp -a debian/tmp/usr/share/man debian/xserver-xorg-video-mach64//usr/share/ returned exit code 1 make[1]: *** [override_dh_install] Error 2 The full build log is available from: http://people.debian.org/~lucas/logs/2012/04/19/xserver-xorg-video-mach64_6.9.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--- ---BeginMessage--- Version: 6.9.1-2 On Thu, 19 Apr 2012 22:21:05 +0200, Lucas Nussbaum wrote: Source: xserver-xorg-video-mach64 Version: 6.9.1-1 Severity: serious Tags: wheezy sid User: debian...@lists.debian.org Usertags: qa-ftbfs-20120419 qa-ftbfs Justification: FTBFS on amd64 Relevant part: make[1]: Entering directory `/«PKGBUILDDIR»' find debian/tmp -name '*.la' -delete dh_install --fail-missing cp: cannot stat `debian/tmp/usr/share/man': No such file or directory dh_install: cp -a debian/tmp/usr/share/man debian/xserver-xorg-video-mach64//usr/share/ returned exit code 1 make[1]: *** [override_dh_install] Error 2 Fixed in the next upload: xserver-xorg-video-mach64 (6.9.1-2) unstable; urgency=low * Drop usr/share/man from dh_install, there's no manpage to ship for this driver. -- Cyril Brulebois k...@debian.org Tue, 01 May 2012 14:41:22 +0200 Also confirmed with a local build, and not found in http://anonscm.debian.org/viewvc/collab-qa/archive-rebuilds/2012-06-04-unstable-amd64/failed.2012-06-04.txt?revision=2364view=markup Cheers, gregor, closing the bug -- .''`. 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: John Zorn: Sansanah (Ribot) signature.asc Description: Digital signature ---End Message---
Bug#677163: marked as done (linkchecker-web: fails to install: ERROR: Module version does not exist!)
Your message dated Tue, 12 Jun 2012 16:33:13 + with message-id e1seu1p-0001lb...@franck.debian.org and subject line Bug#677163: fixed in linkchecker 7.9-2 has caused the Debian Bug report #677163, regarding linkchecker-web: fails to install: ERROR: Module version 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.) -- 677163: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=677163 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: linkchecker-web Version: 7.9-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...): Selecting previously unselected package linkchecker-web. (Reading database ... 11031 files and directories currently installed.) Unpacking linkchecker-web (from .../linkchecker-web_7.9-1_all.deb) ... Setting up linkchecker-web (7.9-1) ... ERROR: Module version does not exist! dpkg: error processing linkchecker-web (--configure): subprocess installed post-installation script returned error exit status 1 Errors were encountered while processing: linkchecker-web cheers, Andreas linkchecker-web_7.9-1.log.gz Description: GNU Zip compressed data ---End Message--- ---BeginMessage--- Source: linkchecker Source-Version: 7.9-2 We believe that the bug you reported is fixed in the latest version of linkchecker, which is due to be installed in the Debian FTP archive: linkchecker-gui_7.9-2_all.deb to main/l/linkchecker/linkchecker-gui_7.9-2_all.deb linkchecker-web_7.9-2_all.deb to main/l/linkchecker/linkchecker-web_7.9-2_all.deb linkchecker_7.9-2.debian.tar.gz to main/l/linkchecker/linkchecker_7.9-2.debian.tar.gz linkchecker_7.9-2.dsc to main/l/linkchecker/linkchecker_7.9-2.dsc linkchecker_7.9-2_amd64.deb to main/l/linkchecker/linkchecker_7.9-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 677...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Bastian Kleineidam cal...@debian.org (supplier of updated linkchecker 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, 12 Jun 2012 07:33:19 +0200 Source: linkchecker Binary: linkchecker linkchecker-web linkchecker-gui Architecture: source amd64 all Version: 7.9-2 Distribution: unstable Urgency: low Maintainer: Bastian Kleineidam cal...@debian.org Changed-By: Bastian Kleineidam cal...@debian.org Description: linkchecker - check websites and HTML documents for broken links linkchecker-gui - check websites and HTML documents for broken links (GUI client) linkchecker-web - check websites and HTML documents for broken links (web client) Closes: 677163 Changes: linkchecker (7.9-2) unstable; urgency=low . * Fix postinstallation script of linkchecker-web. (Closes: #677163) Checksums-Sha1: 0ecc3b100591f6fb10a0218f156a89b6068e36c5 1396 linkchecker_7.9-2.dsc 6dbe29da087516d06c1968c8eeb67b5eb06cc84b 21240 linkchecker_7.9-2.debian.tar.gz 8960e0d562374d8644c1808c8f8972ad680346dd 394998 linkchecker_7.9-2_amd64.deb b42943882b55a27529ac25c28661904135dcd3df 54556 linkchecker-web_7.9-2_all.deb 97c1bd19ccfa548081460d50bb575b10648857c3 110734 linkchecker-gui_7.9-2_all.deb Checksums-Sha256: 8e0900582387ce100d3f1d3af997edc4bd7675044aa3d9b32f0f4794e7f4fa67 1396 linkchecker_7.9-2.dsc fcf84c633ae11721167b7cfd40d4a4cdf621ae167c91e021bc3a15666a1c5647 21240 linkchecker_7.9-2.debian.tar.gz 9a28d52b0ca345c0568563203e6988a99fbca6f45327d518b7a84eb2a3f8c0b2 394998 linkchecker_7.9-2_amd64.deb 7960357d5a15d9a752ccfe5dd9872df1902b22e19b7dfdfd0383ada2d94e243b 54556 linkchecker-web_7.9-2_all.deb f41a51598f4596c3f4b1336a59b7c3483c52f48860c1b89732e9655f4104bb29 110734 linkchecker-gui_7.9-2_all.deb Files: 0ff3d48df912d0f888486a37f6433bd2 1396 web optional linkchecker_7.9-2.dsc fb22abc3a95dc5c1d4a035cc14b4cf01 21240 web optional linkchecker_7.9-2.debian.tar.gz a53de2de37fb8840c26cc3bf3ec9ef1e 394998 web optional linkchecker_7.9-2_amd64.deb 78c8e6e9e7371ba7fa9cf988a6685e34 54556 web optional
Bug#677227: screen: Workaround for #644788 fails to detect a running screen on kfreebsd / process renaming does not work on kfreebsd
On Tue, 2012-06-12 at 14:34:16 +0100, Steven Chamberlain wrote: On 12/06/12 14:23, Axel Beckert wrote: But on kfreebsd this process renaming don't seem to work. This doesn't seem to be a screen issue but a general kfreebsd issue as the following works as expected on Linux, but not on kfreebsd: $ perl -e '$0 = foobar!; ' I recall that setproctitle was implemented as a no-op in libbsd. So that is probably a known bug / unimplemented yet. I don't think neither perl nor screen are using libbsd-dev, though? regards, guillem -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#676116: marked as done (mlpost: FTBFS: Command exited with code 1.)
Your message dated Tue, 12 Jun 2012 16:49:26 + with message-id e1seuhw-0002h9...@franck.debian.org and subject line Bug#676116: fixed in mlpost 0.8.1-3 has caused the Debian Bug report #676116, regarding mlpost: FTBFS: Command exited with code 1. to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 676116: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=676116 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Source: mlpost Version: 0.8.1-2 Severity: serious Tags: wheezy sid User: debian...@lists.debian.org Usertags: qa-ftbfs-20120604 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»' rm -f doc /usr/bin/ocamlbuild -no-links -tag dtypes -tags cairo_yes,concrete_yes -classic-display -log build.log doc/index.html cp mlpost_yeslablgtk.odocl mlpost.odocl /usr/bin/ocamldep -modules customdoc/img.ml customdoc/img.ml.depends /usr/bin/ocamlc -c -I +ocamldoc -I +ocamldoc -dtypes -I customdoc -I gui -I concrete -I backend -I dvi -o customdoc/img.cmo customdoc/img.ml cp contrib/dot/mlpost_dot.mli mlpost_dot.mli /usr/bin/ocamldep -modules mlpost_dot.mli mlpost_dot.mli.depends cp contrib/lablgtk/mlpost_lablgtk.mli mlpost_lablgtk.mli /usr/bin/ocamldep -modules mlpost_lablgtk.mli mlpost_lablgtk.mli.depends /usr/bin/ocamldoc -dump mlpost.odoc -hide Mlpost -g customdoc/img.cmo -I /usr/lib/ocaml/lablgtk2 -I /usr/lib/ocaml/cairo -I /usr/lib/ocaml/cairo -pp './myocamlmacroparser.byte -D CAIRO -D CONCRETE' -I gui -I concrete -I backend -I dvi mlpost.mli /usr/bin/ocamldoc -dump mlpost_dot.odoc -hide Mlpost -g customdoc/img.cmo -I /usr/lib/ocaml/lablgtk2 -I gui -I concrete -I backend -I dvi mlpost_dot.mli /usr/bin/ocamldoc -dump mlpost_lablgtk.odoc -hide Mlpost -g customdoc/img.cmo -I /usr/lib/ocaml/lablgtk2 -I gui -I concrete -I backend -I dvi mlpost_lablgtk.mli + /usr/bin/ocamldoc -dump mlpost_lablgtk.odoc -hide Mlpost -g customdoc/img.cmo -I /usr/lib/ocaml/lablgtk2 -I gui -I concrete -I backend -I dvi mlpost_lablgtk.mli Warning: Class or class type GObj.widget not found rm -rf mlpost.docdir mkdir -p mlpost.docdir /usr/bin/ocamldoc -load mlpost.odoc -load mlpost_dot.odoc -load mlpost_lablgtk.odoc -hide Mlpost -g customdoc/img.cmo -I /usr/lib/ocaml/lablgtk2 -html -d mlpost.docdir + /usr/bin/ocamldoc -load mlpost.odoc -load mlpost_dot.odoc -load mlpost_lablgtk.odoc -hide Mlpost -g customdoc/img.cmo -I /usr/lib/ocaml/lablgtk2 -html -d mlpost.docdir Warning: Class or class type GObj.widget not found /usr/bin/ocamldep -modules customdoc/img_doc.ml customdoc/img_doc.ml.depends /usr/bin/ocamlc -c -dtypes -I /usr/lib/ocaml/cairo -I /usr/lib/ocaml/bitstring -I customdoc -I gui -I concrete -I backend -I dvi -o customdoc/img_doc.cmo customdoc/img_doc.ml /usr/bin/ocamlc unix.cma bigarray.cma -I /usr/lib/ocaml/cairo cairo.cma -I /usr/lib/ocaml/bitstring bitstring.cma dvi/dvi_util.cmo name.cmo scan_prelude.cmo mlpost.cmo customdoc/img_doc.cmo -o customdoc/img_doc.byte mkdir -p img/ cd img/ ../customdoc/img_doc.byte /dev/null cd .. + mkdir -p img/ cd img/ ../customdoc/img_doc.byte /dev/null cd .. Command exited with code 1. make[2]: *** [doc] Error 10 The full build log is available from: http://people.debian.org/~lucas/logs/2012/06/04/mlpost_0.8.1-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 EC2 VM instances from Amazon Web Services, using a clean, minimal and up-to-date chroot. Every failed build was retried once to eliminate random failures. ---End Message--- ---BeginMessage--- Source: mlpost Source-Version: 0.8.1-3 We believe that the bug you reported is fixed in the latest version of mlpost, which is due to be installed in the Debian FTP archive: libmlpost-ocaml-dev_0.8.1-3_amd64.deb to main/m/mlpost/libmlpost-ocaml-dev_0.8.1-3_amd64.deb libmlpost-ocaml-doc_0.8.1-3_all.deb to main/m/mlpost/libmlpost-ocaml-doc_0.8.1-3_all.deb mlpost_0.8.1-3.debian.tar.gz to main/m/mlpost/mlpost_0.8.1-3.debian.tar.gz mlpost_0.8.1-3.dsc to main/m/mlpost/mlpost_0.8.1-3.dsc mlpost_0.8.1-3_amd64.deb to main/m/mlpost/mlpost_0.8.1-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
Bug#676127: marked as done (ocamlviz: FTBFS: I can't open file `mp-tool'.)
Your message dated Tue, 12 Jun 2012 16:49:26 +
with message-id e1seuhw-0002hc...@franck.debian.org
and subject line Bug#676127: fixed in mlpost 0.8.1-3
has caused the Debian Bug report #676127,
regarding ocamlviz: FTBFS: I can't open file `mp-tool'.
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.)
--
676127: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=676127
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
---BeginMessage---
Source: ocamlviz
Version: 1.01-2
Severity: serious
Tags: wheezy sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20120604 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»'
cd doc mlpost -latex manual.tex -pdf fig.ml pdflatex manual.tex
This is MetaPost, version 1.504 (kpathsea version 6.1.0)
(mpost.mp (/usr/share/texlive/texmf-dist/metapost/base/plain.mp
Preloading the plain mem file, version 1.004)) (./mlpost9c9b7e.mp
! I can't open file `mp-tool'.
l.1 input mp-tool
; % some initializations and auxiliary macros
Please type another input file name
! Emergency stop.
l.1 input mp-tool
; % some initializations and auxiliary macros
Transcript written on mlpost9c9b7e.log.
make[2]: *** [doc/manual.pdf] Error 1
The full build log is available from:
http://people.debian.org/~lucas/logs/2012/06/04/ocamlviz_1.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 EC2 VM instances from
Amazon Web Services, using a clean, minimal and up-to-date chroot. Every
failed build was retried once to eliminate random failures.
---End Message---
---BeginMessage---
Source: mlpost
Source-Version: 0.8.1-3
We believe that the bug you reported is fixed in the latest version of
mlpost, which is due to be installed in the Debian FTP archive:
libmlpost-ocaml-dev_0.8.1-3_amd64.deb
to main/m/mlpost/libmlpost-ocaml-dev_0.8.1-3_amd64.deb
libmlpost-ocaml-doc_0.8.1-3_all.deb
to main/m/mlpost/libmlpost-ocaml-doc_0.8.1-3_all.deb
mlpost_0.8.1-3.debian.tar.gz
to main/m/mlpost/mlpost_0.8.1-3.debian.tar.gz
mlpost_0.8.1-3.dsc
to main/m/mlpost/mlpost_0.8.1-3.dsc
mlpost_0.8.1-3_amd64.deb
to main/m/mlpost/mlpost_0.8.1-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 676...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Mehdi Dogguy me...@debian.org (supplier of updated mlpost 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, 12 Jun 2012 18:12:17 +0200
Source: mlpost
Binary: mlpost libmlpost-ocaml-dev libmlpost-ocaml-doc
Architecture: source amd64 all
Version: 0.8.1-3
Distribution: unstable
Urgency: low
Maintainer: Debian OCaml Maintainers debian-ocaml-ma...@lists.debian.org
Changed-By: Mehdi Dogguy me...@debian.org
Description:
libmlpost-ocaml-dev - Objective Caml interface to Metapost (library)
libmlpost-ocaml-doc - Objective Caml interface to Metapost (doc)
mlpost - Objective Caml interface to Metapost (command-line tool)
Closes: 676116 676127
Changes:
mlpost (0.8.1-3) unstable; urgency=low
.
* Team upload.
* Since context (= 2012.05.23.20120524-1), mp-tool.mp and mp-spec.mp
are no longer provided. Instead, context provide .mpii and .mpiv files.
- add 0005-Fully-qualify-name-of-input-ed-files.patch
- {build-,}depend on context (= 2012.05.23.20120524-1~)
(Closes: #676116, #676127).
* Use Breaks instead of Conflicts with mlpost ( 0.8.1).
* Bump Standards-Version to 3.9.3 (no changes)
Checksums-Sha1:
eb70ace43ad63857693b6f8be03e4c13b49e68ad 1967 mlpost_0.8.1-3.dsc
f57b779e26fb2974a17145c60acb1cec503dcbb7 6275 mlpost_0.8.1-3.debian.tar.gz
28753bc2f8a0d07217a3a06d65961a084b610581 238258 mlpost_0.8.1-3_amd64.deb
1e9e450348d0a96ddfdc37099cf57a22b3645c52 971408
libmlpost-ocaml-dev_0.8.1-3_amd64.deb
a5ad82560ed433931b6b5d41ad62e8112924c125 113396
libmlpost-ocaml-doc_0.8.1-3_all.deb
Checksums-Sha256:
9da41ae4dc34f9e3eb7e951d507dfda9daddf960b2ae1e8c5d0443c7240bc18e 1967
Bug#677261: marked as done (vsftpd: FTBFS[kfreebsd-amd64 mips{,el}]: relocation R_X86_64_32 against `.rodata.str1.1' can not be used when making a shared object; recompile with -fPIC)
Your message dated Tue, 12 Jun 2012 16:51:38 +
with message-id e1seuje-0002ql...@franck.debian.org
and subject line Bug#677261: fixed in vsftpd 3.0.0-2
has caused the Debian Bug report #677261,
regarding vsftpd: FTBFS[kfreebsd-amd64 mips{,el}]: relocation R_X86_64_32
against `.rodata.str1.1' can not be used when making a shared object; recompile
with -fPIC
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.)
--
677261: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=677261
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
---BeginMessage---
Package: src:vsftpd
Version: 3.0.0-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:
gcc -o vsftpd main.o utility.o prelogin.o ftpcmdio.o postlogin.o privsock.o
tunables.o ftpdataio.o secbuf.o ls.o postprivparent.o logging.o str.o netstr.o
sysstr.o strlist.o banner.o filestr.o parseconf.o secutil.o ascii.o
oneprocess.o twoprocess.o privops.o standalone.o hash.o tcpwrap.o ipaddrparse.o
access.o features.o readwrite.o opts.o ssl.o sslslave.o ptracesandbox.o
ftppolicy.o sysutil.o sysdeputil.o seccompsandbox.o -fPIE -pie -Wl,-z,relro
-Wl,-z,now -lwrap -lpam -lssl -lcrypto
/usr/bin/ld: main.o: relocation R_X86_64_32 against `.rodata.str1.1' can not be
used when making a shared object; recompile with -fPIC
main.o: could not read symbols: Bad value
collect2: error: ld returned 1 exit status
make[2]: *** [vsftpd] Error 1
Similar for mips*
Full build log at
https://buildd.debian.org/status/logs.php?pkg=vsftpdver=3.0.0-1arch=kfreebsd-amd64
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---
---BeginMessage---
Source: vsftpd
Source-Version: 3.0.0-2
We believe that the bug you reported is fixed in the latest version of
vsftpd, which is due to be installed in the Debian FTP archive:
vsftpd_3.0.0-2.debian.tar.gz
to main/v/vsftpd/vsftpd_3.0.0-2.debian.tar.gz
vsftpd_3.0.0-2.dsc
to main/v/vsftpd/vsftpd_3.0.0-2.dsc
vsftpd_3.0.0-2_i386.deb
to main/v/vsftpd/vsftpd_3.0.0-2_i386.deb
A summary of the changes between this version and the previous one is
attached.
Thank you for reporting the bug, which will now be closed. If you
have further comments please address them to 677...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Daniel Baumann daniel.baum...@progress-technologies.net (supplier of updated
vsftpd 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, 12 Jun 2012 18:33:09 +0200
Source: vsftpd
Binary: vsftpd
Architecture: source i386
Version: 3.0.0-2
Distribution: unstable
Urgency: low
Maintainer: Daniel Baumann daniel.baum...@progress-technologies.net
Changed-By: Daniel Baumann daniel.baum...@progress-technologies.net
Description:
vsftpd - lightweight, efficient FTP server written for security
Closes: 677261
Changes:
vsftpd (3.0.0-2) unstable; urgency=low
.
* Temporarily build without hardening flags, doesn't build reliably
everywhere yet (Closes: #677261).
Checksums-Sha1:
198081d3b8f130c463ad5c18d0886c695edc3ba1 1125 vsftpd_3.0.0-2.dsc
25220bb4541768c215a867d0af8d4be2af852910 27237 vsftpd_3.0.0-2.debian.tar.gz
37c2c5cbd05d1d6c36b1d2142328173e1e7eb301 162406 vsftpd_3.0.0-2_i386.deb
Checksums-Sha256:
841942bfe7d6e7b6d29347f2be9a031bd90b0acfc856421ec3e44cd94276e72a 1125
vsftpd_3.0.0-2.dsc
ed9487ef130598473da1012192257e269e56608b0547e48d0b04569b572a53aa 27237
vsftpd_3.0.0-2.debian.tar.gz
4cc60ff0bd8b8e21d9a04b265a35d616104c0e7039d1d050aaee3fc2e6afc57b 162406
vsftpd_3.0.0-2_i386.deb
Files:
24d14da9a45505dc63c50648e6a5664c 1125 net extra vsftpd_3.0.0-2.dsc
8a6570f0c715e5b533994ab96a577140 27237 net extra vsftpd_3.0.0-2.debian.tar.gz
49d3b90fa5d8b6ed8ab7f1001ea71ee7 162406 net extra vsftpd_3.0.0-2_i386.deb
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.10 (GNU/Linux)
iEYEARECAAYFAk/Xb9EACgkQ+C5cwEsrK55eEQCgucSLwlM/CzTgmR/iGVeqMMD0
PNwAnjaOzwR7q8iAJfz9YKXwNW1HoJrR
=fMo/
-END PGP SIGNATURE-
---End Message---
Bug#677206: xserver-xorg-video-intel: Segfault with missing driver name in xorg.conf
Hi! I'd like to confirm that I was getting the same segfault: [93.128] Backtrace: [93.129] 0: /usr/bin/Xorg (xorg_backtrace+0x36) [0x7f1587d37796] [93.129] 1: /usr/bin/Xorg (0x7f1587bb9000+0x1822b9) [0x7f1587d3b2b9] [93.129] 2: /lib/x86_64-linux-gnu/libpthread.so.0 (0x7f1586ee1000+0xf030) [0x7f1586ef0030] [93.129] 3: /usr/bin/Xorg (xf86nameCompare+0x63) [0x7f1587c72963] [93.129] 4: /usr/lib/xorg/modules/drivers/intel_drv.so (0x7f1583b12000+0xfba9) [0x7f1583b21ba9] [93.129] 5: /usr/bin/Xorg (0x7f1587bb9000+0xa67f7) [0x7f1587c5f7f7] [93.129] 6: /usr/bin/Xorg (xf86CallDriverProbe+0x8c) [0x7f1587c3dd4c] [93.129] 7: /usr/bin/Xorg (xf86BusConfig+0x80) [0x7f1587c3e5e0] [93.129] 8: /usr/bin/Xorg (InitOutput+0x7a0) [0x7f1587c4a6a0] [93.129] 9: /usr/bin/Xorg (0x7f1587bb9000+0x41d36) [0x7f1587bfad36] [93.129] 10: /lib/x86_64-linux-gnu/libc.so.6 (__libc_start_main+0xfd) [0x7f1585c0aead] [93.129] 11: /usr/bin/Xorg (0x7f1587bb9000+0x421ad) [0x7f1587bfb1ad] [93.129] [93.129] Segmentation fault at address (nil) [93.129] Fatal server error: [93.129] Caught signal 11 (Segmentation fault). Server aborting [93.129] [93.129] Please consult the The X.Org Foundation support at http://wiki.x.org for help. [93.129] Please also check the log file at /var/log/Xorg.0.log for additional information. and my Device section in /etc/X11/xorg.conf is also empty: Section Device Identifier Configured Video Device EndSection I've found this bug report only after I've worked around the bug by downgrading from xserver-xorg-video-intel_2.19.0-2_amd64.deb to xserver-xorg-video-intel_2.19.0-1_amd64.deb An additional detail is that in my case, this bug was manifesting in a nasty way of rapidly launching lots and lots of instances of Xorg processes, which were trying to allocate new TTYs, and the conputer was hanging. My hardware is: video integrated into Intel Core i5-2310, and motherboard is ASUS P8Z77-V PRO. Best wishes, Vladimir
