Bug#644064: marked as done (ocfs2-tools: FTBFS with -Werror=format-security)
Your message dated Mon, 17 Oct 2011 06:47:30 + with message-id e1rfgyw-do...@franck.debian.org and subject line Bug#644064: fixed in ocfs2-tools 1.6.3-4 has caused the Debian Bug report #644064, regarding ocfs2-tools: FTBFS with -Werror=format-security 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.) -- 644064: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=644064 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: ocfs2-tools Version: 1.6.3-3 Severity: serious Justification: fails to build from source See https://buildd.debian.org/status/package.php?p=ocfs2-tools gcc -g -O2 -fstack-protector --param=ssp-buffer-size=4 -D_FORTIFY_SOURCE=2 -Wformat -Wformat-security -Werror=format-security -Wall -Wall -Wstrict-prototypes -Wmissing-prototypes -Wmissing-declarations -pipe -I../include -Iinclude -DVERSION=\1.6.3\ -MD -MP -MF ./.problem.d -o problem.o -c problem.c problem.c: In function 'prompt_input': problem.c:115:4: error: format not a string literal and no format arguments [-Werror=format-security] problem.c:117:4: error: format not a string literal and no format arguments [-Werror=format-security] cc1: some warnings being treated as errors make[2]: *** [problem.o] Error 1 Cheers, Julien ---End Message--- ---BeginMessage--- Source: ocfs2-tools Source-Version: 1.6.3-4 We believe that the bug you reported is fixed in the latest version of ocfs2-tools, which is due to be installed in the Debian FTP archive: ocfs2-tools-cman_1.6.3-4_amd64.deb to main/o/ocfs2-tools/ocfs2-tools-cman_1.6.3-4_amd64.deb ocfs2-tools-dev_1.6.3-4_amd64.deb to main/o/ocfs2-tools/ocfs2-tools-dev_1.6.3-4_amd64.deb ocfs2-tools-pacemaker_1.6.3-4_amd64.deb to main/o/ocfs2-tools/ocfs2-tools-pacemaker_1.6.3-4_amd64.deb ocfs2-tools_1.6.3-4.debian.tar.gz to main/o/ocfs2-tools/ocfs2-tools_1.6.3-4.debian.tar.gz ocfs2-tools_1.6.3-4.dsc to main/o/ocfs2-tools/ocfs2-tools_1.6.3-4.dsc ocfs2-tools_1.6.3-4_amd64.deb to main/o/ocfs2-tools/ocfs2-tools_1.6.3-4_amd64.deb ocfs2console_1.6.3-4_amd64.deb to main/o/ocfs2-tools/ocfs2console_1.6.3-4_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 644...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Jeremy Lainé jeremy.la...@m4x.org (supplier of updated ocfs2-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: Mon, 17 Oct 2011 08:29:00 +0200 Source: ocfs2-tools Binary: ocfs2-tools ocfs2-tools-cman ocfs2-tools-dev ocfs2-tools-pacemaker ocfs2console Architecture: source amd64 Version: 1.6.3-4 Distribution: unstable Urgency: low Maintainer: Jeremy Lainé jeremy.la...@m4x.org Changed-By: Jeremy Lainé jeremy.la...@m4x.org Description: ocfs2-tools - tools for managing OCFS2 cluster filesystems ocfs2-tools-cman - tools for managing OCFS2 cluster filesystems - cman support ocfs2-tools-dev - tools for managing OCFS2 cluster filesystems - development files ocfs2-tools-pacemaker - tools for managing OCFS2 cluster filesystems - pacemaker support ocfs2console - tools for managing OCFS2 cluster filesystems - graphical interfac Closes: 644064 Changes: ocfs2-tools (1.6.3-4) unstable; urgency=low . * Fix FTBS with -Werror=format-security (Closes: #644064). * Update Standards-Version to 3.9.2 (no changes). Checksums-Sha1: 2233602cee4465c8d183931e8415f6b5ec5db0f9 1834 ocfs2-tools_1.6.3-4.dsc 52c36e9c7a0abe30e6799b0047d3998faf464eaa 31322 ocfs2-tools_1.6.3-4.debian.tar.gz 89a01aafe31d14f44c32bdfc4db72e0ebbb59f0c 990698 ocfs2-tools_1.6.3-4_amd64.deb 4808e20b53332a1260eb931f4e73401196825932 54028 ocfs2-tools-cman_1.6.3-4_amd64.deb 32642a068c36e99fb6301fd9b7e33242d2bcc37b 183174 ocfs2-tools-dev_1.6.3-4_amd64.deb 68f4d18b684a33f24ed9be78aa9368fcfd372a78 53228 ocfs2-tools-pacemaker_1.6.3-4_amd64.deb ae20b201112276cc81f3dff0d5c233eebaa07993 150608 ocfs2console_1.6.3-4_amd64.deb Checksums-Sha256: d357057ed5ffea02aac36927d0d5941e801a6bda20d98f688f47842b35d191b4 1834 ocfs2-tools_1.6.3-4.dsc b1ad8efd9fda8726c161fa2d3c9030f31f1e93b1f52205163b40297313d681c2 31322 ocfs2-tools_1.6.3-4.debian.tar.gz 20d2f03f80125a3390461346ec8ae4588fbfd32af072a6180fab11522be6 990698
Bug#634413: [PATCH] build libgmock.a with tests
On Sat, Sep 10, 2011 at 04:12:42PM +0200, Philipp Kern wrote:
On Mon, Aug 29, 2011 at 09:01:12PM +0800, Daniel Hartwig wrote:
On 29 August 2011 01:36, Daniel Hartwig mand...@gmail.com wrote:
tags 634413 + patch
quit
Re: #634413 aptitude: FTBFS: ld: cannot find -lgmock
...
Nevermind, I have just seen that this was already fixed in git on 23/7
Should have checked ;)
can we have the fix in unstable, please? :)
I just uploaded the attached NMU to DELAYED/0-days. (And mailed a git
commit to dburrows for inclusion into the aptitude repository because
there's a bug in the recent gmock fix.)
Kind regards
Philipp Kern
diff -Nru aptitude-0.6.4/debian/changelog aptitude-0.6.4/debian/changelog
--- aptitude-0.6.4/debian/changelog 2011-05-16 18:05:00.0 +0200
+++ aptitude-0.6.4/debian/changelog 2011-10-16 22:30:18.0 +0200
@@ -1,3 +1,10 @@
+aptitude (0.6.4-1.1) unstable; urgency=low
+
+ * Non-maintainer upload.
+ * Fix FTBFS due to changes in google-mock. (Closes: #634413)
+
+ -- Philipp Kern pk...@debian.org Sun, 16 Oct 2011 22:29:57 +0200
+
aptitude (0.6.4-1) unstable; urgency=low
* New upstream release.
diff -Nru
aptitude-0.6.4/debian/patches/0001-Modify-autoconf-automake-scripts-to-handle-gmock-cha.patch
aptitude-0.6.4/debian/patches/0001-Modify-autoconf-automake-scripts-to-handle-gmock-cha.patch
---
aptitude-0.6.4/debian/patches/0001-Modify-autoconf-automake-scripts-to-handle-gmock-cha.patch
1970-01-01 01:00:00.0 +0100
+++
aptitude-0.6.4/debian/patches/0001-Modify-autoconf-automake-scripts-to-handle-gmock-cha.patch
2011-10-16 22:29:46.0 +0200
@@ -0,0 +1,113 @@
+From 942616a01dfdebe8e040ce459f07d7527220ed9b Mon Sep 17 00:00:00 2001
+From: Daniel Burrows dburr...@debian.org
+Date: Sat, 23 Jul 2011 15:51:23 -0700
+Subject: [PATCH 1/2] Modify autoconf/automake scripts to handle gmock
+ changes.
+
+---
+ configure.ac | 51 +--
+ tests/Makefile.am | 12 +++-
+ 2 files changed, 60 insertions(+), 3 deletions(-)
+
+diff --git a/configure.ac b/configure.ac
+index c0a6862..b0ef2a3 100644
+--- a/configure.ac
b/configure.ac
+@@ -23,8 +23,7 @@ ac_cv_c_const=yes
+ ac_cv_c_inline=yes
+
+ dnl Checks for libraries.
+-AC_CHECK_LIB(ncursesw, initscr, ,
+- [AC_MSG_ERROR([Can't find libncursesw -- please install
libncursesw5-dev])])
++AC_CHECK_LIB(ncursesw, initscr, , [AC_MSG_ERROR([Can't find libncursesw --
please install libncursesw5-dev])])
+ AC_CHECK_LIB(apt-pkg, main, , [AC_MSG_ERROR([Can't find the APT libraries --
please install libapt-pkg-dev])])
+
+ AC_MSG_CHECKING([whether apt includes the automatic dependency removal patch
(required)])
+@@ -482,6 +481,54 @@ AC_SUBST(BOOST_UNIT_TEST_LIBS)
+
+ # End Boost.Test check #
+
++# Check for Google Mock #
++
++dnl Google Mock's developers do not support prebuilt libraries (e.g.,
++dnl they pay no attention to ABI compatibility) and as a result have
++dnl asked Debian not to ship prebuilt libraries. So, if we are
++dnl running on a system where gmock isn't available in $LIBDIR, we
++dnl guess that maybe there's source available that we can compile
++dnl during our own build process.
++
++AC_MSG_CHECKING([how to link gmock])
++
++BUILD_LOCAL_GMOCK=0
++
++OLD_LIBS=$LIBS
++LIBS=$LIBS -lgmock
++
++AC_LINK_IFELSE([AC_LANG_SOURCE([
++#include gmock/gmock.h
++
++int main(int argc, char **argv)
++{
++ return 0;
++}])],
++[AC_MSG_RESULT([gmock is in in library path])]
++,
++dnl Ok, check whether we can link it if we include the gmock
++dnl source code. Note that it will require both pthreads and
++dnl gtest; no way around that.
++[LIBS=$OLD_LIBS -lpthread -lgtest
++ OLD_CPPFLAGS=$CPPFLAGS
++ CPPFLAGS=$CPPFLAGS -I/usr/src/gmock
++ AC_LINK_IFELSE([AC_LANG_SOURCE([
++#include src/gmock-all.cc
++
++int main(int argc, char **argv)
++{
++ return 0;
++}])],
++ [AC_MSG_RESULT([source is in /usr/src/gmock])
++BUILD_LOCAL_GMOCK=1],
++ [AC_MSG_ERROR([Can't figure out where Google Mock lives; either
install the google-mock package or place the library in the link path])])
++ CPPFLAGS=$OLD_CPPFLAGS
++ LIBS=$OLD_LIBS])
++
++AM_CONDITIONAL([BUILD_LOCAL_GMOCK], [test x$BUILD_LOCAL_GMOCK = x1])
++
++# End Google Mock check #
++
+ PKG_CHECK_MODULES(SQLITE3, sqlite3)
+
+ HAVE_GTK=1
+diff --git a/tests/Makefile.am b/tests/Makefile.am
+index 5234d43..2ec9ec0 100644
+--- a/tests/Makefile.am
b/tests/Makefile.am
+@@ -2,7 +2,6 @@ MAINTAINERCLEANFILES = Makefile.in
+
+ INCLUDES = -I$(top_builddir) -I$(top_srcdir) -I$(top_srcdir)/src -I$(srcdir)
+ BOOST_TEST_LDFLAGS = @BOOST_UNIT_TEST_LIBS@
+-GMOCK_LDFLAGS = -lgmock -lgtest
+ AM_CPPFLAGS = -DBOOST_TEST_DYN_LINK -DSRCDIR=\$(srcdir)\
+ LDADD = $(top_builddir)/src/loggers.o\
+
Bug#634413: marked as done (aptitude: FTBFS: ld: cannot find -lgmock)
Your message dated Mon, 17 Oct 2011 07:02:24 + with message-id e1rfhdm-00023d...@franck.debian.org and subject line Bug#634413: fixed in aptitude 0.6.4-1.1 has caused the Debian Bug report #634413, regarding aptitude: FTBFS: ld: cannot find -lgmock 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.) -- 634413: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=634413 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Source: aptitude Version: 0.6.4-1 Severity: serious Tags: wheezy sid User: debian...@lists.debian.org Usertags: qa-ftbfs-20110718 qa-ftbfs Justification: FTBFS on amd64 Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part: g++ -g -O2 -I/usr/include/sigc++-2.0 -I/usr/lib/sigc++-2.0/include -I/usr/lib/cwidget -I/usr/include/sigc++-2.0 -I/usr/lib/sigc++-2.0/include -I/usr/include/tagcoll-2.0.12 -D_REENTRANT -fno-strict-aliasing -Wall -L/usr/lib -o interactive_set_test interactive_set_test.o ../src/loggers.o ../src/generic/apt/matching/libgeneric-matching.a ../src/cmdline/libcmdline.a ../src/generic/apt/libgeneric-apt.a ../src/generic/controllers/libgeneric-controllers.a ../src/generic/apt/matching/libgeneric-matching.a ../src/generic/apt/libgeneric-apt.a ../src/generic/problemresolver/libgeneric-problemresolver.a ../src/cmdline/mocks/libcmdline-mocks.a ../src/cmdline/libcmdline.a ../src/generic/util/libgeneric-util.a ../src/generic/views/libgeneric-views.a ../src/generic/views/mocks/libgeneric-views-mocks.a -lcppunit -lboost_unit_test_framework -lgmock -lgtest -lapt-pkg -lncursesw -lsigc-2.0 -lcwidget -lncursesw -lsigc-2.0 -lept -lapt-pkg -lxapian -ltagcoll2 -lz -lwibble -lsqlite3 -lboost_iostreams-mt -lpthread /usr/bin/ld: cannot find -lgmock collect2: ld returned 1 exit status The full build log is available from: http://people.debian.org/~lucas/logs/2011/07/18/aptitude_0.6.4-1_lsid64.buildlog A list of current common problems and possible solutions is available at http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute! About the archive rebuild: The rebuild was done on about 50 AMD64 nodes of the Grid'5000 platform, using a clean chroot. Internet was not accessible from the build systems. -- | Lucas Nussbaum | lu...@lucas-nussbaum.net http://www.lucas-nussbaum.net/ | | jabber: lu...@nussbaum.fr GPG: 1024D/023B3F4F | ---End Message--- ---BeginMessage--- Source: aptitude Source-Version: 0.6.4-1.1 We believe that the bug you reported is fixed in the latest version of aptitude, which is due to be installed in the Debian FTP archive: aptitude-dbg_0.6.4-1.1_amd64.deb to main/a/aptitude/aptitude-dbg_0.6.4-1.1_amd64.deb aptitude-doc-cs_0.6.4-1.1_all.deb to main/a/aptitude/aptitude-doc-cs_0.6.4-1.1_all.deb aptitude-doc-en_0.6.4-1.1_all.deb to main/a/aptitude/aptitude-doc-en_0.6.4-1.1_all.deb aptitude-doc-es_0.6.4-1.1_all.deb to main/a/aptitude/aptitude-doc-es_0.6.4-1.1_all.deb aptitude-doc-fi_0.6.4-1.1_all.deb to main/a/aptitude/aptitude-doc-fi_0.6.4-1.1_all.deb aptitude-doc-fr_0.6.4-1.1_all.deb to main/a/aptitude/aptitude-doc-fr_0.6.4-1.1_all.deb aptitude-doc-ja_0.6.4-1.1_all.deb to main/a/aptitude/aptitude-doc-ja_0.6.4-1.1_all.deb aptitude-gtk_0.6.4-1.1_amd64.deb to main/a/aptitude/aptitude-gtk_0.6.4-1.1_amd64.deb aptitude_0.6.4-1.1.debian.tar.gz to main/a/aptitude/aptitude_0.6.4-1.1.debian.tar.gz aptitude_0.6.4-1.1.dsc to main/a/aptitude/aptitude_0.6.4-1.1.dsc aptitude_0.6.4-1.1_amd64.deb to main/a/aptitude/aptitude_0.6.4-1.1_amd64.deb A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 634...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Philipp Kern pk...@debian.org (supplier of updated aptitude 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, 16 Oct 2011 22:29:57 +0200 Source: aptitude Binary: aptitude aptitude-gtk aptitude-dbg aptitude-doc-cs aptitude-doc-en aptitude-doc-es aptitude-doc-fi aptitude-doc-fr aptitude-doc-ja Architecture: source amd64 all Version: 0.6.4-1.1 Distribution: unstable Urgency: low Maintainer: Daniel Burrows dburr...@debian.org Changed-By: Philipp Kern
Bug#645572: marked as done (haskell-bindings-libzip: FTBFS - missing build-dep on pkg-config)
Your message dated Mon, 17 Oct 2011 07:02:33 + with message-id e1rfhdv-00027a...@franck.debian.org and subject line Bug#645572: fixed in haskell-bindings-libzip 0.1.0.2-2 has caused the Debian Bug report #645572, regarding haskell-bindings-libzip: FTBFS - missing build-dep 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.) -- 645572: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=645572 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Source: haskell-bindings-libzip Version: 0.1.0.2-1 Severity: serious Justification: fails to build from source Builds of haskell-bindings-libzip in minimal environments, such as on the autobuilders, have been failing: hlibrary.setup: The program pkg-config version =0.9.0 is required but it could not be found. make: *** [dist-ghc] Error 1 Could you please add a build dependency on pkg-config and check with pbuilder or the like that no others are missing? Thanks! ---End Message--- ---BeginMessage--- Source: haskell-bindings-libzip Source-Version: 0.1.0.2-2 We believe that the bug you reported is fixed in the latest version of haskell-bindings-libzip, which is due to be installed in the Debian FTP archive: haskell-bindings-libzip_0.1.0.2-2.debian.tar.gz to main/h/haskell-bindings-libzip/haskell-bindings-libzip_0.1.0.2-2.debian.tar.gz haskell-bindings-libzip_0.1.0.2-2.dsc to main/h/haskell-bindings-libzip/haskell-bindings-libzip_0.1.0.2-2.dsc libghc-bindings-libzip-dev_0.1.0.2-2_amd64.deb to main/h/haskell-bindings-libzip/libghc-bindings-libzip-dev_0.1.0.2-2_amd64.deb libghc-bindings-libzip-doc_0.1.0.2-2_all.deb to main/h/haskell-bindings-libzip/libghc-bindings-libzip-doc_0.1.0.2-2_all.deb libghc-bindings-libzip-prof_0.1.0.2-2_amd64.deb to main/h/haskell-bindings-libzip/libghc-bindings-libzip-prof_0.1.0.2-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 645...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Joachim Breitner nome...@debian.org (supplier of updated haskell-bindings-libzip 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, 17 Oct 2011 08:37:20 +0200 Source: haskell-bindings-libzip Binary: libghc-bindings-libzip-dev libghc-bindings-libzip-prof libghc-bindings-libzip-doc Architecture: source all amd64 Version: 0.1.0.2-2 Distribution: unstable Urgency: low Maintainer: Debian Haskell Group pkg-haskell-maintain...@lists.alioth.debian.org Changed-By: Joachim Breitner nome...@debian.org Description: libghc-bindings-libzip-dev - low-level Haskell bindings to libzip libghc-bindings-libzip-doc - low-level Haskell bindings to libzip; documentation libghc-bindings-libzip-prof - low-level Haskell bindings to libzip; profiling libraries Closes: 645572 Changes: haskell-bindings-libzip (0.1.0.2-2) unstable; urgency=low . * Fix FTBFS: missing build-dep on pkg-config (that’d make a good case for a lintian check) (Closes: #645572) Checksums-Sha1: f38054af87674fb99bd9b1cc49135f0a5f821c91 1803 haskell-bindings-libzip_0.1.0.2-2.dsc d5e74222e267608a5ed4d3f1404453f46ebedb6f 2245 haskell-bindings-libzip_0.1.0.2-2.debian.tar.gz a9b2a5f26ba327ad36d77a5034556328291e3912 46706 libghc-bindings-libzip-doc_0.1.0.2-2_all.deb 4ef313d288d8117455bf6c669cf36a0fe9f9a06a 65624 libghc-bindings-libzip-dev_0.1.0.2-2_amd64.deb 14286e078e9704bb41808e51408d22359c9eb08e 62390 libghc-bindings-libzip-prof_0.1.0.2-2_amd64.deb Checksums-Sha256: 255f4673664dd0c11e3420d14fea41a07fbcb72821410403da064862c132b766 1803 haskell-bindings-libzip_0.1.0.2-2.dsc c88c077b1e69d2dcfdbb7f74e0293119a832336a061f44d7b9c97cc46168 2245 haskell-bindings-libzip_0.1.0.2-2.debian.tar.gz f04ea5a70d75de0bbbfecf0929705b6bbae9d2d0e1b8db65904b2c59a790c991 46706 libghc-bindings-libzip-doc_0.1.0.2-2_all.deb 38edf75143cb0f565aabef31d690005c8107e987a4f293c42b44a90e69db7eaf 65624 libghc-bindings-libzip-dev_0.1.0.2-2_amd64.deb 99f7438fa296aa21c0ecafb1ac7875ffd611c3f1cfb680906ef091b4bc50cab4 62390 libghc-bindings-libzip-prof_0.1.0.2-2_amd64.deb Files: d6f5f6df23d6a628aabf3d88b9f10717 1803 haskell extra haskell-bindings-libzip_0.1.0.2-2.dsc ad179cc20d7733f8af7b068d024a68f1 2245 haskell extra
Bug#645583: Import error
Package: python-mdp Version: 3.1-1 Severity: grave import mdp Traceback (most recent call last): File stdin, line 1, in module File /usr/lib/pymodules/python2.7/mdp/__init__.py, line 120, in module configuration.set_configuration() File /usr/lib/pymodules/python2.7/mdp/configuration.py, line 248, in set_configuration if not hasattr(sgClassifier.Classifier, 'classify'): AttributeError: 'module' object has no attribute 'Classifier' -- YunQiang Su -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#645573: [Pkg-haskell-maintainers] Bug#645573: haskell-hipmunk: FTBFS: errors building documentation
Hi, Am Sonntag, den 16.10.2011, 23:09 -0400 schrieb Aaron M. Ucko: Source: haskell-hipmunk Version: 5.2.0.4-1 Severity: serious Justification: fails to build from source Automatic builds of haskell-hipmunk's architecture-dependent packages (which run without build-depends-indep) have been failing: [ ! -x /usr/bin/haddock ] || debian/hlibrary.setup haddock --builddir=dist-ghc --hyperlink-source Running Haddock for Hipmunk-5.2.0.4... Preprocessing library Hipmunk-5.2.0.4... Running hscolour for Hipmunk-5.2.0.4... Warning: The documentation for the following packages are not installed. No links will be generated to these packages: StateVar-1.0.0.0, array-0.3.0.2, base-4.3.1.0, rts-1.0, containers-0.4.0.0, ghc-prim-0.2.0.0, integer-gmp-0.2.0.3, transformers-0.2.2.0 hlibrary.setup: dist-ghc/doc/html/Hipmunk/haddock-prolog23382.txt: invalid argument make: *** [build-haddock-stamp] Error 1 I'm not sure why they're trying to run haddock at all (though I will note that haskell-devscripts's dependency on ghc-haddock makes the command's conditional redundant) This might be due to confusion with cdbs, build-indep, build-arch et. al.. Maybe the situation has changed since two years ago, someone could check that. or why other packages with your standard setup fare better, but there you have it; could you please take a look? In this case, the package has unicode characters in the description, which haddock does not seem to like in some cases. The problem can be reproduced by setting LANG=C, and it seems it is Cabal writing the file that is the problem, not haddock reading it. Probably the encoding should be set explicitly in cabal. Anybody volunteering to discuss that with upstream? Greetings, Joachim -- Joachim nomeata Breitner Debian Developer nome...@debian.org | ICQ# 74513189 | GPG-Keyid: 4743206C JID: nome...@joachim-breitner.de | http://people.debian.org/~nomeata signature.asc Description: This is a digitally signed message part
Bug#619687: marked as done (ipsec-tools: FTBFS on kfreebsd-*: policy_token.l:56:19: fatal error: y.tab.h: No such file or directory)
Your message dated Mon, 17 Oct 2011 20:42:44 +1300 with message-id 1318837364.3656.0.camel@en-gedi and subject line Closed as package built kfreebsd unstable has caused the Debian Bug report #619687, regarding ipsec-tools: FTBFS on kfreebsd-*: policy_token.l:56:19: fatal error: y.tab.h: 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.) -- 619687: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=619687 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Source: ipsec-tools Version: 1:0.8.0-1 Severity: serious Justification: FTBFS User: debian-...@lists.debian.org Usertags: kfreebsd Hi, your package no longer builds on kfreebsd-*: | libtool: compile: x86_64-kfreebsd-gnu-gcc -DHAVE_CONFIG_H -I. -I../.. -I../../src/racoon/missing -Wall -g -fno-strict-aliasing -isystem /usr/include -D_FORTIFY_SOURCE=0 -O2 -Wall -Werror -Wno-unused -MT policy_token.lo -MD -MP -MF .deps/policy_token.Tpo -c policy_token.c -fPIC -DPIC -o .libs/policy_token.o | policy_token.l:56:19: fatal error: y.tab.h: No such file or directory | compilation terminated. Full build logs: https://buildd.debian.org/status/package.php?p=ipsec-toolssuite=experimental Please get in touch with debian-bsd@ if you need help. KiBi. ---End Message--- ---BeginMessage--- thanks ---End Message---
Bug#643570: marked as done (ipsec-tools: FTBFS(kfreebsd): symbol change)
Your message dated Mon, 17 Oct 2011 20:44:47 +1300 with message-id 1318837487.3656.2.camel@en-gedi and subject line Closes: #643570 as now in kfreebsd unstable. has caused the Debian Bug report #643570, regarding ipsec-tools: FTBFS(kfreebsd): symbol change 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.) -- 643570: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=643570 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: src:ipsec-tools Version: 1:0.8.0-6 Severity: serious Tags: sid wheezy User: debian-...@lists.debian.org Usertags: kfreebsd X-Debbugs-Cc: debian-...@lists.debian.org Hi! Your package failed to build on the kfreebsd-* buildds: --- debian/ipsec-tools.symbols (ipsec-tools_1:0.8.0-6_kfreebsd-amd64) +++ dpkg-gensymbolsSHAP1q 2011-09-26 19:18:51.0 + @@ -71,7 +71,7 @@ pfkey_send_get@Base 0.7.3 pfkey_send_getspi@Base 0.7.3 pfkey_send_getspi_nat@Base 0.8.0 - pfkey_send_migrate@Base 0.7.3 +#MISSING: 1:0.8.0-6# pfkey_send_migrate@Base 0.7.3 pfkey_send_promisc_toggle@Base 0.7.3 pfkey_send_register@Base 0.7.3 pfkey_send_spdadd2@Base 0.7.3 make[1]: *** [override_dh_perl] Error 1 make[1]: Leaving directory `/build/buildd-ipsec-tools_0.8.0-6-kfreebsd-amd64-RNpoBK/ipsec-tools-0.8.0' make: *** [binary-arch] Error 2 Full build log at https://buildd.debian.org/status/fetch.php?pkg=ipsec-toolsarch=kfreebsd-amd64ver=1%3A0.8.0-6stamp=1317064813 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--- thanks ---End Message---
Processed: fixed 643570 in ipsec-tools/1:0.8.0-9
Processing commands for cont...@bugs.debian.org:
fixed 643570 ipsec-tools/1:0.8.0-9
Bug #643570 {Done: Matthew Grant matthewgra...@gmail.com} [src:ipsec-tools]
ipsec-tools: FTBFS(kfreebsd): symbol change
Bug Marked as fixed in versions ipsec-tools/1:0.8.0-9.
thanks
Stopping processing here.
Please contact me if you need assistance.
--
643570: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=643570
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed: fixed 619687 in ipsec-tools/1:0.8.0-9
Processing commands for cont...@bugs.debian.org:
fixed 619687 ipsec-tools/1:0.8.0-9
Bug #619687 {Done: Matthew Grant matthewgra...@gmail.com} [src:ipsec-tools]
ipsec-tools: FTBFS on kfreebsd-*: policy_token.l:56:19: fatal error: y.tab.h:
No such file or directory
Bug Marked as fixed in versions ipsec-tools/1:0.8.0-9.
thanks
Stopping processing here.
Please contact me if you need assistance.
--
619687: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=619687
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#510027: marked as done (pavucontrol_0.9.7-1(sparc/experimental): FTBFS: undefined reference to `AO_store_full_emulation')
Your message dated Mon, 17 Oct 2011 10:42:50 +0200 with message-id 1318840970.3336.4.camel@alexander and subject line Re: pavucontrol_0.9.7-1(sparc/experimental): FTBFS: undefined reference to `AO_store_full_emulation' has caused the Debian Bug report #510027, regarding pavucontrol_0.9.7-1(sparc/experimental): FTBFS: undefined reference to `AO_store_full_emulation' 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.) -- 510027: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=510027 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: pavucontrol Version: 0.9.7-1 Severity: serious Hi, your package failed to build from source. | Automatic build of pavucontrol_0.9.7-1 on titan by sbuild/sparc 98-farm | Build started at 20081228-1846 | ** | Checking available source versions... | Fetching source files... | Reading package lists... | Building dependency tree... | Need to get 208kB of source archives. | Get:1 http://sinclair.farm.ftbfs.de experimental/main pavucontrol 0.9.7-1 (dsc) [1108B] | Get:2 http://sinclair.farm.ftbfs.de experimental/main pavucontrol 0.9.7-1 (tar) [206kB] | Fetched 208kB in 0s (1002kB/s) | Download complete and in download only mode | ** Using build dependencies supplied by package: | Build-Depends: debhelper (= 5), cdbs, autotools-dev, libpulse-dev (= 0.9.12), libgtkmm-2.4-dev, libglademm-2.4-dev, lynx, asciidoc, xmlto, quilt, libcanberra-gtk-dev, intltool | Checking for already installed source dependencies... [...] | g++ -D_REENTRANT -I/usr/include/gtkmm-2.4 -I/usr/lib/gtkmm-2.4/include -I/usr/include/glibmm-2.4 -I/usr/lib/glibmm-2.4/include -I/usr/include/gdkmm-2.4 -I/usr/lib/gdkmm-2.4/include -I/usr/include/pangomm-1.4 -I/usr/include/atkmm-1.6 -I/usr/include/gtk-2.0 -I/usr/include/sigc++-2.0 -I/usr/lib/sigc++-2.0/include -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -I/usr/lib/gtk-2.0/include -I/usr/include/cairomm-1.0 -I/usr/include/pango-1.0 -I/usr/include/cairo -I/usr/include/freetype2 -I/usr/include/directfb -I/usr/include/libpng12 -I/usr/include/pixman-1 -I/usr/include/atk-1.0 -I/usr/include/libglademm-2.4 -I/usr/lib/libglademm-2.4/include -I/usr/include/libglade-2.0 -I/usr/include/libxml2 -D_REENTRANT -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -DLOCALEDIR=\/usr/share/locale\ -DGLADE_FILE=\/usr/share/pavucontrol/pavucontrol.glade\ -g -O2 -g -Wall -O2 -pipe -Wall -W -o pavucontrol pavucontrol-pavucontrol.o -lglademm-2.4 -lgtkmm-2.4 -lglade-2.0 -lgdkmm-2.4 -latkmm-1.6 -lpangomm-1.4 -lcairomm-1.0 -lglibmm-2.4 -lxml2 -lsigc-2.0 -lcanberra-gtk -lcanberra -lgtk-x11-2.0 -lgdk-x11-2.0 -latk-1.0 -lgdk_pixbuf-2.0 -lm -lpangocairo-1.0 -lpango-1.0 -lcairo -lgobject-2.0 -lgmodule-2.0 -ldl -lglib-2.0 -lpulse-mainloop-glib -lpulse -lglib-2.0 | /usr/lib/gcc/sparc-linux-gnu/4.3.2/../../../../lib/libpulse-mainloop-glib.a(libpulse_mainloop_glib_la-once.o): In function `pa_once_end': | (.text+0x10): undefined reference to `AO_store_full_emulation' | /usr/lib/gcc/sparc-linux-gnu/4.3.2/../../../../lib/libpulse-mainloop-glib.a(libpulse_mainloop_glib_la-once.o): In function `pa_once_end': | (.text+0x48): undefined reference to `AO_compare_and_swap_emulation' | /usr/lib/gcc/sparc-linux-gnu/4.3.2/../../../../lib/libpulse-mainloop-glib.a(libpulse_mainloop_glib_la-once.o): In function `pa_once_end': | (.text+0x68): undefined reference to `AO_compare_and_swap_emulation' | /usr/lib/gcc/sparc-linux-gnu/4.3.2/../../../../lib/libpulse-mainloop-glib.a(libpulse_mainloop_glib_la-once.o): In function `pa_once_begin': | (.text+0x174): undefined reference to `AO_compare_and_swap_emulation' | /usr/lib/gcc/sparc-linux-gnu/4.3.2/../../../../lib/libpulse-mainloop-glib.a(libpulse_mainloop_glib_la-once.o): In function `pa_once_begin': | (.text+0x1c4): undefined reference to `AO_compare_and_swap_emulation' | /usr/lib/gcc/sparc-linux-gnu/4.3.2/../../../../lib/libpulse-mainloop-glib.a(libpulse_mainloop_glib_la-thread-posix.o): In function `pa_thread_self': | (.text+0x48c): undefined reference to `AO_store_full_emulation' | /usr/lib/gcc/sparc-linux-gnu/4.3.2/../../../../lib/libpulse-mainloop-glib.a(libpulse_mainloop_glib_la-thread-posix.o): In function `internal_thread_func': | (.text+0x634): undefined reference to `AO_compare_and_swap_emulation' | /usr/lib/gcc/sparc-linux-gnu/4.3.2/../../../../lib/libpulse-mainloop-glib.a(libpulse_mainloop_glib_la-thread-posix.o): In function `internal_thread_func': | (.text+0x65c): undefined reference to
Bug#618077: marked as done (Improper usage of #include for C headers leads to build problems in other packages)
Your message dated Mon, 17 Oct 2011 10:44:19 +0200 with message-id 1318841059.3336.6.camel@alexander and subject line Re: batmon.app: FTBFS: BatteryModel.m:308: undefined reference to `assert' has caused the Debian Bug report #618046, regarding Improper usage of #include for C headers leads to build problems in other packages 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.) -- 618046: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=618046 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Source: etoile Version: 0+20080616+dfsg-2 Severity: serious Tags: wheezy sid User: debian...@lists.debian.org Usertags: qa-ftbfs-20110313 qa-ftbfs Justification: FTBFS on amd64 Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part: gcc -rdynamic -Wl,-z,defs -Wl,--as-needed -shared-libgcc -fexceptions -fgnu-runtime -o DictionaryReader.app/./DictionaryReader \ ./obj/DictionaryReader.obj/AppController.m.o ./obj/DictionaryReader.obj/StreamLineWriter.m.o ./obj/DictionaryReader.obj/StreamLineReader.m.o ./obj/DictionaryReader.obj/DictConnection.m.o ./obj/DictionaryReader.obj/HistoryManager.m.o ./obj/DictionaryReader.obj/NSString+Convenience.m.o ./obj/DictionaryReader.obj/NSString+Clickable.m.o ./obj/DictionaryReader.obj/NSString+DictLineParsing.m.o ./obj/DictionaryReader.obj/NSScanner+Base64Encoding.m.o ./obj/DictionaryReader.obj/LocalDictionary.m.o ./obj/DictionaryReader.obj/main.m.o -L/usr/local/lib -L/usr/lib -lgnustep-gui-lgnustep-base -lpthread -lobjc -lm ./obj/DictionaryReader.obj/AppController.m.o: In function `-[AppController clickSearchNotification:]': /build/user-etoile_0+20080616+dfsg-2-amd64-KSoM7w/etoile-0+20080616+dfsg/Etoile/Services/User/DictionaryReader/AppController.m:343: undefined reference to `assert' /build/user-etoile_0+20080616+dfsg-2-amd64-KSoM7w/etoile-0+20080616+dfsg/Etoile/Services/User/DictionaryReader/AppController.m:348: undefined reference to `assert' ./obj/DictionaryReader.obj/StreamLineReader.m.o: In function `-[StreamLineReader getMoreCharacters]': /build/user-etoile_0+20080616+dfsg-2-amd64-KSoM7w/etoile-0+20080616+dfsg/Etoile/Services/User/DictionaryReader/StreamLineReader.m:117: undefined reference to `assert' ./obj/DictionaryReader.obj/StreamLineReader.m.o: In function `-[StreamLineReader extractNextLine]': /build/user-etoile_0+20080616+dfsg-2-amd64-KSoM7w/etoile-0+20080616+dfsg/Etoile/Services/User/DictionaryReader/StreamLineReader.m:145: undefined reference to `assert' /build/user-etoile_0+20080616+dfsg-2-amd64-KSoM7w/etoile-0+20080616+dfsg/Etoile/Services/User/DictionaryReader/StreamLineReader.m:146: undefined reference to `assert' collect2: ld returned 1 exit status The full build log is available from: http://people.debian.org/~lucas/logs/2011/03/13/etoile_0+20080616+dfsg-2_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--- On Wed, 2011-10-12 at 08:37 +0200, Alexander Kurtz wrote: Since both #618046 and #618077 have been fixed for some time now and the affected packages build fine[1][2], I'd like to close these bugs in a few days. Any objections? Closing now, feel free to reopen if necessary. Best regards Alexander Kurtz signature.asc Description: This is a digitally signed message part ---End Message---
Bug#618046: marked as done (Improper usage of #include for C headers leads to build problems in other packages)
Your message dated Mon, 17 Oct 2011 10:44:19 +0200 with message-id 1318841059.3336.6.camel@alexander and subject line Re: batmon.app: FTBFS: BatteryModel.m:308: undefined reference to `assert' has caused the Debian Bug report #618046, regarding Improper usage of #include for C headers leads to build problems in other packages 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.) -- 618046: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=618046 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Source: batmon.app Version: 0.5-1 Severity: serious Tags: wheezy sid User: debian...@lists.debian.org Usertags: qa-ftbfs-20110313 qa-ftbfs Justification: FTBFS on amd64 Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part: gcc -rdynamic -Wl,-z,defs -Wl,--as-needed -shared-libgcc -fexceptions -fgnu-runtime -o batmon.app/./batmon \ ./obj/batmon.obj/AppController.m.o ./obj/batmon.obj/BatteryModel.m.o ./obj/batmon.obj/main.m.o -L/usr/local/lib -L/usr/lib -lgnustep-gui-lgnustep-base -lpthread -lobjc -lm ./obj/batmon.obj/BatteryModel.m.o: In function `-[BatteryModel update]': /build/user-batmon.app_0.5-1-amd64-1Jxjg0/batmon.app-0.5/BatteryModel.m:308: undefined reference to `assert' /build/user-batmon.app_0.5-1-amd64-1Jxjg0/batmon.app-0.5/BatteryModel.m:416: undefined reference to `assert' /build/user-batmon.app_0.5-1-amd64-1Jxjg0/batmon.app-0.5/BatteryModel.m:437: undefined reference to `assert' /build/user-batmon.app_0.5-1-amd64-1Jxjg0/batmon.app-0.5/BatteryModel.m:519: undefined reference to `assert' collect2: ld returned 1 exit status The full build log is available from: http://people.debian.org/~lucas/logs/2011/03/13/batmon.app_0.5-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--- On Wed, 2011-10-12 at 08:37 +0200, Alexander Kurtz wrote: Since both #618046 and #618077 have been fixed for some time now and the affected packages build fine[1][2], I'd like to close these bugs in a few days. Any objections? Closing now, feel free to reopen if necessary. Best regards Alexander Kurtz signature.asc Description: This is a digitally signed message part ---End Message---
Bug#644031: librtorrent upload
Uploaded Rogério Brito wrote: Please note that, despite the revision being 3, I have included the full sources, since the package version 0.12.9 (which needed a SONAME update) has not yet entered the main archive. Please ping me when you need to upload anything. I am usually more responsive on weekdays. -- .''`. Sell Crazy Someplace Else. We're all stocked up here : :' : `. `' `- Proudly running Debian GNU/Linux -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed: tagging 638817, severity of 638817 is grave
Processing commands for cont...@bugs.debian.org: tags 638817 - wheezy Bug #638817 [gnome-settings-daemon] gnome-settings-daemon crashes on startup, errors on libnotify Removed tag(s) wheezy. severity 638817 grave Bug #638817 [gnome-settings-daemon] gnome-settings-daemon crashes on startup, errors on libnotify Severity set to 'grave' from 'critical' thanks Stopping processing here. Please contact me if you need assistance. -- 638817: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=638817 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: limit source to digikam, tagging 644702
Processing commands for cont...@bugs.debian.org: #digikam (2:2.2.0-2) UNRELEASED; urgency=low # # * Add Build-Depends: libqtwebkit-dev #- Fixes FTBFS: /usr/include/KDE/../kwebview.h:31:29: fatal error: #QtWebKit/QWebView: No such file or directory (Closes: #644702) # limit source digikam Limiting to bugs with field 'source' containing at least one of 'digikam' Limit currently set to 'source':'digikam' tags 644702 + pending Bug #644702 [digikam] FTBFS: /usr/include/KDE/../kwebview.h:31:29: fatal error: QtWebKit/QWebView: No such file or directory Added tag(s) pending. thanks Stopping processing here. Please contact me if you need assistance. -- 644702: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=644702 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#645601: node-backbone-dirty and libnode-backbone-dirty: error when trying to install together
Package: libnode-backbone-dirty,node-backbone-dirty Version: libnode-backbone-dirty/1.1.2-1 Version: node-backbone-dirty/1.1.2-2 Severity: serious User: trei...@debian.org Usertags: edos-file-overwrite Date: 2011-10-17 Architecture: amd64 Distribution: sid Hi, automatic installation tests of packages that share a file and at the same time do not conflict by their package dependency relationships has detected the following problem: WARNING: The following packages cannot be authenticated! libc-ares2 libicu44 libjs-underscore libjs-backbone libev4 libv8-3.4.14.21 nodejs libnode-dirty node-dirty libnode-backbone-dirty node-backbone-dirty Authentication warning overridden. Can not write log, openpty() failed (/dev/pts not mounted?) Selecting previously unselected package libc-ares2. (Reading database ... 10586 files and directories currently installed.) Unpacking libc-ares2 (from .../libc-ares2_1.7.5-1_amd64.deb) ... Selecting previously unselected package libicu44. Unpacking libicu44 (from .../libicu44_4.4.2-2_amd64.deb) ... Selecting previously unselected package libjs-underscore. Unpacking libjs-underscore (from .../libjs-underscore_1.1.6-1_all.deb) ... Selecting previously unselected package libjs-backbone. Unpacking libjs-backbone (from .../libjs-backbone_0.5.3-2_all.deb) ... Selecting previously unselected package libev4. Unpacking libev4 (from .../libev4_1%3a4.04-1_amd64.deb) ... Selecting previously unselected package libv8-3.4.14.21. Unpacking libv8-3.4.14.21 (from .../libv8-3.4.14.21_3.4.14.21-3_amd64.deb) ... Selecting previously unselected package nodejs. Unpacking nodejs (from .../nodejs_0.4.12-1_amd64.deb) ... Selecting previously unselected package libnode-dirty. Unpacking libnode-dirty (from .../libnode-dirty_0.9.4-1_all.deb) ... Selecting previously unselected package node-dirty. Unpacking node-dirty (from .../node-dirty_0.9.4-2_all.deb) ... dpkg: error processing /var/cache/apt/archives/node-dirty_0.9.4-2_all.deb (--unpack): trying to overwrite '/usr/lib/nodejs/dirty/dirty.js', which is also in package libnode-dirty 0.9.4-1 configured to not write apport reports Selecting previously unselected package libnode-backbone-dirty. Unpacking libnode-backbone-dirty (from .../libnode-backbone-dirty_1.1.2-1_all.deb) ... Selecting previously unselected package node-backbone-dirty. Unpacking node-backbone-dirty (from .../node-backbone-dirty_1.1.2-2_all.deb) ... dpkg: error processing /var/cache/apt/archives/node-backbone-dirty_1.1.2-2_all.deb (--unpack): trying to overwrite '/usr/share/nodejs/backbone-dirty.js', which is also in package libnode-backbone-dirty 1.1.2-1 configured to not write apport reports Processing triggers for man-db ... Errors were encountered while processing: /var/cache/apt/archives/node-dirty_0.9.4-2_all.deb /var/cache/apt/archives/node-backbone-dirty_1.1.2-2_all.deb E: Sub-process /usr/bin/dpkg returned an error code (1) This is a serious bug as it makes installation fail, and violates sections 7.6.1 and 10.1 of the policy. An optimal solution would consist in only one of the packages installing that file, and renaming or removing the file in the other package. Depending on the circumstances you might also consider Replace relations or file diversions. If the conflicting situation cannot be resolved then, as a last resort, the two packages have to declare a mutual Conflict. Please take into account that Replaces, Conflicts and diversions should only be used when packages provide different implementations for the same functionality. Here is a list of files that are known to be shared by both packages (according to the Contents file for sid/amd64, which may be slightly out of sync): /usr/share/nodejs/backbone-dirty.js This bug is assigned to both packages. If you, the maintainers of the two packages in question, have agreed on which of the packages will resolve the problem please reassign the bug to that package. You may also register in the BTS that the other package is affected by the bug. -Ralf. PS: for more information about the detection of file overwrite errors of this kind see http://edos.debian.net/file-overwrites/. -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#645602: node-chrono and libnode-chrono: error when trying to install together
Package: libnode-chrono,node-chrono Version: libnode-chrono/1.0.2-1 Version: node-chrono/1.0.2-2 Severity: serious User: trei...@debian.org Usertags: edos-file-overwrite Date: 2011-10-17 Architecture: amd64 Distribution: sid Hi, automatic installation tests of packages that share a file and at the same time do not conflict by their package dependency relationships has detected the following problem: WARNING: The following packages cannot be authenticated! libc-ares2 libicu44 libv8-3.4.14.21 libev4 libnode-chrono nodejs node-chrono Authentication warning overridden. Can not write log, openpty() failed (/dev/pts not mounted?) Selecting previously unselected package libc-ares2. (Reading database ... 10586 files and directories currently installed.) Unpacking libc-ares2 (from .../libc-ares2_1.7.5-1_amd64.deb) ... Selecting previously unselected package libicu44. Unpacking libicu44 (from .../libicu44_4.4.2-2_amd64.deb) ... Selecting previously unselected package libv8-3.4.14.21. Unpacking libv8-3.4.14.21 (from .../libv8-3.4.14.21_3.4.14.21-3_amd64.deb) ... Selecting previously unselected package libev4. Unpacking libev4 (from .../libev4_1%3a4.04-1_amd64.deb) ... Selecting previously unselected package libnode-chrono. Unpacking libnode-chrono (from .../libnode-chrono_1.0.2-1_all.deb) ... Selecting previously unselected package nodejs. Unpacking nodejs (from .../nodejs_0.4.12-1_amd64.deb) ... Selecting previously unselected package node-chrono. Unpacking node-chrono (from .../node-chrono_1.0.2-2_all.deb) ... dpkg: error processing /var/cache/apt/archives/node-chrono_1.0.2-2_all.deb (--unpack): trying to overwrite '/usr/lib/nodejs/chrono.js', which is also in package libnode-chrono 1.0.2-1 configured to not write apport reports Processing triggers for man-db ... Errors were encountered while processing: /var/cache/apt/archives/node-chrono_1.0.2-2_all.deb E: Sub-process /usr/bin/dpkg returned an error code (1) This is a serious bug as it makes installation fail, and violates sections 7.6.1 and 10.1 of the policy. An optimal solution would consist in only one of the packages installing that file, and renaming or removing the file in the other package. Depending on the circumstances you might also consider Replace relations or file diversions. If the conflicting situation cannot be resolved then, as a last resort, the two packages have to declare a mutual Conflict. Please take into account that Replaces, Conflicts and diversions should only be used when packages provide different implementations for the same functionality. Here is a list of files that are known to be shared by both packages (according to the Contents file for sid/amd64, which may be slightly out of sync): /usr/lib/nodejs/chrono.js This bug is assigned to both packages. If you, the maintainers of the two packages in question, have agreed on which of the packages will resolve the problem please reassign the bug to that package. You may also register in the BTS that the other package is affected by the bug. -Ralf. PS: for more information about the detection of file overwrite errors of this kind see http://edos.debian.net/file-overwrites/. -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#638817: gnome-settings-daemon: here is a backtrace
Package: gnome-settings-daemon Version: 3.0.3-2 Followup-For: Bug #638817 gdb =gnome-settings-daemon [...] (gdb) r Starting program: /usr/bin/gnome-settings-daemon [Thread debugging using libthread_db enabled] [New Thread 0x71dc2700 (LWP 8366)] [New Thread 0x715c1700 (LWP 8367)] [New Thread 0x7fffebfff700 (LWP 8368)] [New Thread 0x7fffeb7fe700 (LWP 8369)] ** (gnome-settings-daemon:8362): WARNING **: Ignoring unknown module 'org.gnome.settings-daemon.plugins.gconf' [Thread 0x71dc2700 (LWP 8366) exited] (gnome-settings-daemon:8362): GLib-CRITICAL **: g_variant_get_va: assertion `value != NULL' failed Program received signal SIGSEGV, Segmentation fault. 0x767499a2 in g_atomic_int_exchange_and_add () from /lib/libglib-2.0.so.0 (gdb) bt #0 0x767499a2 in g_atomic_int_exchange_and_add () from /lib/libglib-2.0.so.0 #1 0x767aceb2 in g_variant_unref () from /lib/libglib-2.0.so.0 #2 0x7fffdd4483f2 in ?? () from /usr/lib/gnome-settings-daemon-3.0/libupdates.so #3 0x76e588f0 in g_type_create_instance () from /usr/lib/libgobject-2.0.so.0 #4 0x76e36f9c in ?? () from /usr/lib/libgobject-2.0.so.0 #5 0x76e39f42 in g_object_newv () from /usr/lib/libgobject-2.0.so.0 #6 0x76e3ab0c in g_object_new () from /usr/lib/libgobject-2.0.so.0 #7 0x7fffdd448be2 in gsd_updates_refresh_new () from /usr/lib/gnome-settings-daemon-3.0/libupdates.so #8 0x7fffdd44cc5c in gsd_updates_manager_start () from /usr/lib/gnome-settings-daemon-3.0/libupdates.so #9 0x7fffdd44778c in ?? () from /usr/lib/gnome-settings-daemon-3.0/libupdates.so #10 0x0040595d in gnome_settings_plugin_info_activate () #11 0x004048e5 in _start () (gdb) -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#645604: node-connect and libnode-connect: error when trying to install together
Package: libnode-connect,node-connect Version: libnode-connect/1.7.1-1 Version: node-connect/1.7.1-2 Severity: serious User: trei...@debian.org Usertags: edos-file-overwrite Date: 2011-10-17 Architecture: amd64 Distribution: sid Hi, automatic installation tests of packages that share a file and at the same time do not conflict by their package dependency relationships has detected the following problem: WARNING: The following packages cannot be authenticated! libc-ares2 libicu44 libv8-3.4.14.21 libev4 libnode-qs libnode-mime libnode-connect nodejs node-qs node-mime node-connect Authentication warning overridden. Can not write log, openpty() failed (/dev/pts not mounted?) Selecting previously unselected package libc-ares2. (Reading database ... 10586 files and directories currently installed.) Unpacking libc-ares2 (from .../libc-ares2_1.7.5-1_amd64.deb) ... Selecting previously unselected package libicu44. Unpacking libicu44 (from .../libicu44_4.4.2-2_amd64.deb) ... Selecting previously unselected package libv8-3.4.14.21. Unpacking libv8-3.4.14.21 (from .../libv8-3.4.14.21_3.4.14.21-3_amd64.deb) ... Selecting previously unselected package libev4. Unpacking libev4 (from .../libev4_1%3a4.04-1_amd64.deb) ... Selecting previously unselected package libnode-qs. Unpacking libnode-qs (from .../libnode-qs_0.3.1-1_all.deb) ... Selecting previously unselected package libnode-mime. Unpacking libnode-mime (from .../libnode-mime_1.2.4-1_all.deb) ... Selecting previously unselected package libnode-connect. Unpacking libnode-connect (from .../libnode-connect_1.7.1-1_all.deb) ... Selecting previously unselected package nodejs. Unpacking nodejs (from .../nodejs_0.4.12-1_amd64.deb) ... Selecting previously unselected package node-qs. Unpacking node-qs (from .../node-qs_0.3.1-2_all.deb) ... dpkg: error processing /var/cache/apt/archives/node-qs_0.3.1-2_all.deb (--unpack): trying to overwrite '/usr/lib/nodejs/qs.js', which is also in package libnode-qs 0.3.1-1 configured to not write apport reports Selecting previously unselected package node-mime. Unpacking node-mime (from .../node-mime_1.2.4-2_all.deb) ... dpkg: error processing /var/cache/apt/archives/node-mime_1.2.4-2_all.deb (--unpack): trying to overwrite '/usr/lib/nodejs/mime.js', which is also in package libnode-mime 1.2.4-1 configured to not write apport reports Selecting previously unselected package node-connect. Unpacking node-connect (from .../node-connect_1.7.1-2_all.deb) ... dpkg: error processing /var/cache/apt/archives/node-connect_1.7.1-2_all.deb (--unpack): trying to overwrite '/usr/lib/nodejs/connect/http.js', which is also in package libnode-connect 1.7.1-1 configured to not write apport reports Processing triggers for man-db ... Errors were encountered while processing: /var/cache/apt/archives/node-qs_0.3.1-2_all.deb /var/cache/apt/archives/node-mime_1.2.4-2_all.deb /var/cache/apt/archives/node-connect_1.7.1-2_all.deb E: Sub-process /usr/bin/dpkg returned an error code (1) This is a serious bug as it makes installation fail, and violates sections 7.6.1 and 10.1 of the policy. An optimal solution would consist in only one of the packages installing that file, and renaming or removing the file in the other package. Depending on the circumstances you might also consider Replace relations or file diversions. If the conflicting situation cannot be resolved then, as a last resort, the two packages have to declare a mutual Conflict. Please take into account that Replaces, Conflicts and diversions should only be used when packages provide different implementations for the same functionality. Here is a list of files that are known to be shared by both packages (according to the Contents file for sid/amd64, which may be slightly out of sync): /usr/lib/nodejs/connect/cache.js /usr/lib/nodejs/connect/connect.js /usr/lib/nodejs/connect/http.js /usr/lib/nodejs/connect/https.js /usr/lib/nodejs/connect/index.js /usr/lib/nodejs/connect/middleware/basicAuth.js /usr/lib/nodejs/connect/middleware/bodyParser.js /usr/lib/nodejs/connect/middleware/compiler.js /usr/lib/nodejs/connect/middleware/cookieParser.js /usr/lib/nodejs/connect/middleware/csrf.js /usr/lib/nodejs/connect/middleware/directory.js /usr/lib/nodejs/connect/middleware/errorHandler.js /usr/lib/nodejs/connect/middleware/favicon.js /usr/lib/nodejs/connect/middleware/limit.js /usr/lib/nodejs/connect/middleware/logger.js /usr/lib/nodejs/connect/middleware/methodOverride.js /usr/lib/nodejs/connect/middleware/profiler.js /usr/lib/nodejs/connect/middleware/query.js /usr/lib/nodejs/connect/middleware/responseTime.js /usr/lib/nodejs/connect/middleware/router.js /usr/lib/nodejs/connect/middleware/session.js /usr/lib/nodejs/connect/middleware/session/cookie.js /usr/lib/nodejs/connect/middleware/session/memory.js /usr/lib/nodejs/connect/middleware/session/session.js /usr/lib/nodejs/connect/middleware/session/store.js
Bug#645605: node-dirty and libnode-dirty: error when trying to install together
Package: libnode-dirty,node-dirty Version: libnode-dirty/0.9.4-1 Version: node-dirty/0.9.4-2 Severity: serious User: trei...@debian.org Usertags: edos-file-overwrite Date: 2011-10-17 Architecture: amd64 Distribution: sid Hi, automatic installation tests of packages that share a file and at the same time do not conflict by their package dependency relationships has detected the following problem: WARNING: The following packages cannot be authenticated! libc-ares2 libicu44 libev4 libv8-3.4.14.21 nodejs libnode-dirty node-dirty Authentication warning overridden. Can not write log, openpty() failed (/dev/pts not mounted?) Selecting previously unselected package libc-ares2. (Reading database ... 10586 files and directories currently installed.) Unpacking libc-ares2 (from .../libc-ares2_1.7.5-1_amd64.deb) ... Selecting previously unselected package libicu44. Unpacking libicu44 (from .../libicu44_4.4.2-2_amd64.deb) ... Selecting previously unselected package libev4. Unpacking libev4 (from .../libev4_1%3a4.04-1_amd64.deb) ... Selecting previously unselected package libv8-3.4.14.21. Unpacking libv8-3.4.14.21 (from .../libv8-3.4.14.21_3.4.14.21-3_amd64.deb) ... Selecting previously unselected package nodejs. Unpacking nodejs (from .../nodejs_0.4.12-1_amd64.deb) ... Selecting previously unselected package libnode-dirty. Unpacking libnode-dirty (from .../libnode-dirty_0.9.4-1_all.deb) ... Selecting previously unselected package node-dirty. Unpacking node-dirty (from .../node-dirty_0.9.4-2_all.deb) ... dpkg: error processing /var/cache/apt/archives/node-dirty_0.9.4-2_all.deb (--unpack): trying to overwrite '/usr/lib/nodejs/dirty/dirty.js', which is also in package libnode-dirty 0.9.4-1 configured to not write apport reports Processing triggers for man-db ... Errors were encountered while processing: /var/cache/apt/archives/node-dirty_0.9.4-2_all.deb E: Sub-process /usr/bin/dpkg returned an error code (1) This is a serious bug as it makes installation fail, and violates sections 7.6.1 and 10.1 of the policy. An optimal solution would consist in only one of the packages installing that file, and renaming or removing the file in the other package. Depending on the circumstances you might also consider Replace relations or file diversions. If the conflicting situation cannot be resolved then, as a last resort, the two packages have to declare a mutual Conflict. Please take into account that Replaces, Conflicts and diversions should only be used when packages provide different implementations for the same functionality. Here is a list of files that are known to be shared by both packages (according to the Contents file for sid/amd64, which may be slightly out of sync): /usr/lib/nodejs/dirty/dirty.js /usr/lib/nodejs/dirty/index.js This bug is assigned to both packages. If you, the maintainers of the two packages in question, have agreed on which of the packages will resolve the problem please reassign the bug to that package. You may also register in the BTS that the other package is affected by the bug. -Ralf. PS: for more information about the detection of file overwrite errors of this kind see http://edos.debian.net/file-overwrites/. -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#645606: node-express and libnode-express: error when trying to install together
Package: libnode-express,node-express Version: libnode-express/2.4.7-1 Version: node-express/2.4.7-2 Severity: serious User: trei...@debian.org Usertags: edos-file-overwrite Date: 2011-10-17 Architecture: amd64 Distribution: sid Hi, automatic installation tests of packages that share a file and at the same time do not conflict by their package dependency relationships has detected the following problem: WARNING: The following packages cannot be authenticated! libc-ares2 libicu44 libv8-3.4.14.21 libev4 libnode-qs libnode-mime libnode-connect libnode-mkdirp libnode-express nodejs node-qs node-mime node-connect node-mkdirp node-express Authentication warning overridden. Can not write log, openpty() failed (/dev/pts not mounted?) Selecting previously unselected package libc-ares2. (Reading database ... 10586 files and directories currently installed.) Unpacking libc-ares2 (from .../libc-ares2_1.7.5-1_amd64.deb) ... Selecting previously unselected package libicu44. Unpacking libicu44 (from .../libicu44_4.4.2-2_amd64.deb) ... Selecting previously unselected package libv8-3.4.14.21. Unpacking libv8-3.4.14.21 (from .../libv8-3.4.14.21_3.4.14.21-3_amd64.deb) ... Selecting previously unselected package libev4. Unpacking libev4 (from .../libev4_1%3a4.04-1_amd64.deb) ... Selecting previously unselected package libnode-qs. Unpacking libnode-qs (from .../libnode-qs_0.3.1-1_all.deb) ... Selecting previously unselected package libnode-mime. Unpacking libnode-mime (from .../libnode-mime_1.2.4-1_all.deb) ... Selecting previously unselected package libnode-connect. Unpacking libnode-connect (from .../libnode-connect_1.7.1-1_all.deb) ... Selecting previously unselected package libnode-mkdirp. Unpacking libnode-mkdirp (from .../libnode-mkdirp_0.0.7-1_all.deb) ... Selecting previously unselected package libnode-express. Unpacking libnode-express (from .../libnode-express_2.4.7-1_all.deb) ... Selecting previously unselected package nodejs. Unpacking nodejs (from .../nodejs_0.4.12-1_amd64.deb) ... Selecting previously unselected package node-qs. Unpacking node-qs (from .../node-qs_0.3.1-2_all.deb) ... dpkg: error processing /var/cache/apt/archives/node-qs_0.3.1-2_all.deb (--unpack): trying to overwrite '/usr/lib/nodejs/qs.js', which is also in package libnode-qs 0.3.1-1 configured to not write apport reports Selecting previously unselected package node-mime. Unpacking node-mime (from .../node-mime_1.2.4-2_all.deb) ... dpkg: error processing /var/cache/apt/archives/node-mime_1.2.4-2_all.deb (--unpack): trying to overwrite '/usr/lib/nodejs/mime.js', which is also in package libnode-mime 1.2.4-1 configured to not write apport reports Selecting previously unselected package node-connect. Unpacking node-connect (from .../node-connect_1.7.1-2_all.deb) ... dpkg: error processing /var/cache/apt/archives/node-connect_1.7.1-2_all.deb (--unpack): trying to overwrite '/usr/lib/nodejs/connect/http.js', which is also in package libnode-connect 1.7.1-1 configured to not write apport reports Selecting previously unselected package node-mkdirp. Unpacking node-mkdirp (from .../node-mkdirp_0.0.7-2_all.deb) ... dpkg: error processing /var/cache/apt/archives/node-mkdirp_0.0.7-2_all.deb (--unpack): trying to overwrite '/usr/lib/nodejs/mkdirp.js', which is also in package libnode-mkdirp 0.0.7-1 configured to not write apport reports Selecting previously unselected package node-express. Unpacking node-express (from .../node-express_2.4.7-2_all.deb) ... dpkg: error processing /var/cache/apt/archives/node-express_2.4.7-2_all.deb (--unpack): trying to overwrite '/usr/lib/nodejs/express/request.js', which is also in package libnode-express 2.4.7-1 configured to not write apport reports Processing triggers for man-db ... Errors were encountered while processing: /var/cache/apt/archives/node-qs_0.3.1-2_all.deb /var/cache/apt/archives/node-mime_1.2.4-2_all.deb /var/cache/apt/archives/node-connect_1.7.1-2_all.deb /var/cache/apt/archives/node-mkdirp_0.0.7-2_all.deb /var/cache/apt/archives/node-express_2.4.7-2_all.deb E: Sub-process /usr/bin/dpkg returned an error code (1) This is a serious bug as it makes installation fail, and violates sections 7.6.1 and 10.1 of the policy. An optimal solution would consist in only one of the packages installing that file, and renaming or removing the file in the other package. Depending on the circumstances you might also consider Replace relations or file diversions. If the conflicting situation cannot be resolved then, as a last resort, the two packages have to declare a mutual Conflict. Please take into account that Replaces, Conflicts and diversions should only be used when packages provide different implementations for the same functionality. Here is a list of files that are known to be shared by both packages (according to the Contents file for sid/amd64, which may be slightly out of sync): /usr/bin/express /usr/lib/nodejs/express/express.js /usr/lib/nodejs/express/http.js
Bug#645607: node-mime and libnode-mime: error when trying to install together
Package: libnode-mime,node-mime Version: libnode-mime/1.2.4-1 Version: node-mime/1.2.4-2 Severity: serious User: trei...@debian.org Usertags: edos-file-overwrite Date: 2011-10-17 Architecture: amd64 Distribution: sid Hi, automatic installation tests of packages that share a file and at the same time do not conflict by their package dependency relationships has detected the following problem: WARNING: The following packages cannot be authenticated! libc-ares2 libicu44 libv8-3.4.14.21 libev4 libnode-mime nodejs node-mime Authentication warning overridden. Can not write log, openpty() failed (/dev/pts not mounted?) Selecting previously unselected package libc-ares2. (Reading database ... 10586 files and directories currently installed.) Unpacking libc-ares2 (from .../libc-ares2_1.7.5-1_amd64.deb) ... Selecting previously unselected package libicu44. Unpacking libicu44 (from .../libicu44_4.4.2-2_amd64.deb) ... Selecting previously unselected package libv8-3.4.14.21. Unpacking libv8-3.4.14.21 (from .../libv8-3.4.14.21_3.4.14.21-3_amd64.deb) ... Selecting previously unselected package libev4. Unpacking libev4 (from .../libev4_1%3a4.04-1_amd64.deb) ... Selecting previously unselected package libnode-mime. Unpacking libnode-mime (from .../libnode-mime_1.2.4-1_all.deb) ... Selecting previously unselected package nodejs. Unpacking nodejs (from .../nodejs_0.4.12-1_amd64.deb) ... Selecting previously unselected package node-mime. Unpacking node-mime (from .../node-mime_1.2.4-2_all.deb) ... dpkg: error processing /var/cache/apt/archives/node-mime_1.2.4-2_all.deb (--unpack): trying to overwrite '/usr/lib/nodejs/mime.js', which is also in package libnode-mime 1.2.4-1 configured to not write apport reports Processing triggers for man-db ... Errors were encountered while processing: /var/cache/apt/archives/node-mime_1.2.4-2_all.deb E: Sub-process /usr/bin/dpkg returned an error code (1) This is a serious bug as it makes installation fail, and violates sections 7.6.1 and 10.1 of the policy. An optimal solution would consist in only one of the packages installing that file, and renaming or removing the file in the other package. Depending on the circumstances you might also consider Replace relations or file diversions. If the conflicting situation cannot be resolved then, as a last resort, the two packages have to declare a mutual Conflict. Please take into account that Replaces, Conflicts and diversions should only be used when packages provide different implementations for the same functionality. Here is a list of files that are known to be shared by both packages (according to the Contents file for sid/amd64, which may be slightly out of sync): /usr/lib/nodejs/mime.js This bug is assigned to both packages. If you, the maintainers of the two packages in question, have agreed on which of the packages will resolve the problem please reassign the bug to that package. You may also register in the BTS that the other package is affected by the bug. -Ralf. PS: for more information about the detection of file overwrite errors of this kind see http://edos.debian.net/file-overwrites/. -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#645608: node-mirror and libnode-mirror: error when trying to install together
Package: libnode-mirror,node-mirror Version: libnode-mirror/0.3.3-1 Version: node-mirror/0.3.3-2 Severity: serious User: trei...@debian.org Usertags: edos-file-overwrite Date: 2011-10-17 Architecture: amd64 Distribution: sid Hi, automatic installation tests of packages that share a file and at the same time do not conflict by their package dependency relationships has detected the following problem: WARNING: The following packages cannot be authenticated! libc-ares2 libicu44 libv8-3.4.14.21 libev4 libnode-mirror nodejs node-mirror Authentication warning overridden. Can not write log, openpty() failed (/dev/pts not mounted?) Selecting previously unselected package libc-ares2. (Reading database ... 10586 files and directories currently installed.) Unpacking libc-ares2 (from .../libc-ares2_1.7.5-1_amd64.deb) ... Selecting previously unselected package libicu44. Unpacking libicu44 (from .../libicu44_4.4.2-2_amd64.deb) ... Selecting previously unselected package libv8-3.4.14.21. Unpacking libv8-3.4.14.21 (from .../libv8-3.4.14.21_3.4.14.21-3_amd64.deb) ... Selecting previously unselected package libev4. Unpacking libev4 (from .../libev4_1%3a4.04-1_amd64.deb) ... Selecting previously unselected package libnode-mirror. Unpacking libnode-mirror (from .../libnode-mirror_0.3.3-1_all.deb) ... Selecting previously unselected package nodejs. Unpacking nodejs (from .../nodejs_0.4.12-1_amd64.deb) ... Selecting previously unselected package node-mirror. Unpacking node-mirror (from .../node-mirror_0.3.3-2_all.deb) ... dpkg: error processing /var/cache/apt/archives/node-mirror_0.3.3-2_all.deb (--unpack): trying to overwrite '/usr/lib/nodejs/mirror.js', which is also in package libnode-mirror 0.3.3-1 configured to not write apport reports Processing triggers for man-db ... Errors were encountered while processing: /var/cache/apt/archives/node-mirror_0.3.3-2_all.deb E: Sub-process /usr/bin/dpkg returned an error code (1) This is a serious bug as it makes installation fail, and violates sections 7.6.1 and 10.1 of the policy. An optimal solution would consist in only one of the packages installing that file, and renaming or removing the file in the other package. Depending on the circumstances you might also consider Replace relations or file diversions. If the conflicting situation cannot be resolved then, as a last resort, the two packages have to declare a mutual Conflict. Please take into account that Replaces, Conflicts and diversions should only be used when packages provide different implementations for the same functionality. Here is a list of files that are known to be shared by both packages (according to the Contents file for sid/amd64, which may be slightly out of sync): /usr/lib/nodejs/mirror.js This bug is assigned to both packages. If you, the maintainers of the two packages in question, have agreed on which of the packages will resolve the problem please reassign the bug to that package. You may also register in the BTS that the other package is affected by the bug. -Ralf. PS: for more information about the detection of file overwrite errors of this kind see http://edos.debian.net/file-overwrites/. -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#645609: node-mkdirp and libnode-mkdirp: error when trying to install together
Package: libnode-mkdirp,node-mkdirp Version: libnode-mkdirp/0.0.7-1 Version: node-mkdirp/0.0.7-2 Severity: serious User: trei...@debian.org Usertags: edos-file-overwrite Date: 2011-10-17 Architecture: amd64 Distribution: sid Hi, automatic installation tests of packages that share a file and at the same time do not conflict by their package dependency relationships has detected the following problem: WARNING: The following packages cannot be authenticated! libc-ares2 libicu44 libv8-3.4.14.21 libev4 libnode-mkdirp nodejs node-mkdirp Authentication warning overridden. Can not write log, openpty() failed (/dev/pts not mounted?) Selecting previously unselected package libc-ares2. (Reading database ... 10586 files and directories currently installed.) Unpacking libc-ares2 (from .../libc-ares2_1.7.5-1_amd64.deb) ... Selecting previously unselected package libicu44. Unpacking libicu44 (from .../libicu44_4.4.2-2_amd64.deb) ... Selecting previously unselected package libv8-3.4.14.21. Unpacking libv8-3.4.14.21 (from .../libv8-3.4.14.21_3.4.14.21-3_amd64.deb) ... Selecting previously unselected package libev4. Unpacking libev4 (from .../libev4_1%3a4.04-1_amd64.deb) ... Selecting previously unselected package libnode-mkdirp. Unpacking libnode-mkdirp (from .../libnode-mkdirp_0.0.7-1_all.deb) ... Selecting previously unselected package nodejs. Unpacking nodejs (from .../nodejs_0.4.12-1_amd64.deb) ... Selecting previously unselected package node-mkdirp. Unpacking node-mkdirp (from .../node-mkdirp_0.0.7-2_all.deb) ... dpkg: error processing /var/cache/apt/archives/node-mkdirp_0.0.7-2_all.deb (--unpack): trying to overwrite '/usr/lib/nodejs/mkdirp.js', which is also in package libnode-mkdirp 0.0.7-1 configured to not write apport reports Processing triggers for man-db ... Errors were encountered while processing: /var/cache/apt/archives/node-mkdirp_0.0.7-2_all.deb E: Sub-process /usr/bin/dpkg returned an error code (1) This is a serious bug as it makes installation fail, and violates sections 7.6.1 and 10.1 of the policy. An optimal solution would consist in only one of the packages installing that file, and renaming or removing the file in the other package. Depending on the circumstances you might also consider Replace relations or file diversions. If the conflicting situation cannot be resolved then, as a last resort, the two packages have to declare a mutual Conflict. Please take into account that Replaces, Conflicts and diversions should only be used when packages provide different implementations for the same functionality. Here is a list of files that are known to be shared by both packages (according to the Contents file for sid/amd64, which may be slightly out of sync): /usr/lib/nodejs/mkdirp.js This bug is assigned to both packages. If you, the maintainers of the two packages in question, have agreed on which of the packages will resolve the problem please reassign the bug to that package. You may also register in the BTS that the other package is affected by the bug. -Ralf. PS: for more information about the detection of file overwrite errors of this kind see http://edos.debian.net/file-overwrites/. -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#645610: node-qs and libnode-qs: error when trying to install together
Package: libnode-qs,node-qs Version: libnode-qs/0.3.1-1 Version: node-qs/0.3.1-2 Severity: serious User: trei...@debian.org Usertags: edos-file-overwrite Date: 2011-10-17 Architecture: amd64 Distribution: sid Hi, automatic installation tests of packages that share a file and at the same time do not conflict by their package dependency relationships has detected the following problem: WARNING: The following packages cannot be authenticated! libc-ares2 libicu44 libv8-3.4.14.21 libev4 libnode-qs nodejs node-qs Authentication warning overridden. Can not write log, openpty() failed (/dev/pts not mounted?) Selecting previously unselected package libc-ares2. (Reading database ... 10586 files and directories currently installed.) Unpacking libc-ares2 (from .../libc-ares2_1.7.5-1_amd64.deb) ... Selecting previously unselected package libicu44. Unpacking libicu44 (from .../libicu44_4.4.2-2_amd64.deb) ... Selecting previously unselected package libv8-3.4.14.21. Unpacking libv8-3.4.14.21 (from .../libv8-3.4.14.21_3.4.14.21-3_amd64.deb) ... Selecting previously unselected package libev4. Unpacking libev4 (from .../libev4_1%3a4.04-1_amd64.deb) ... Selecting previously unselected package libnode-qs. Unpacking libnode-qs (from .../libnode-qs_0.3.1-1_all.deb) ... Selecting previously unselected package nodejs. Unpacking nodejs (from .../nodejs_0.4.12-1_amd64.deb) ... Selecting previously unselected package node-qs. Unpacking node-qs (from .../node-qs_0.3.1-2_all.deb) ... dpkg: error processing /var/cache/apt/archives/node-qs_0.3.1-2_all.deb (--unpack): trying to overwrite '/usr/lib/nodejs/qs.js', which is also in package libnode-qs 0.3.1-1 configured to not write apport reports Processing triggers for man-db ... Errors were encountered while processing: /var/cache/apt/archives/node-qs_0.3.1-2_all.deb E: Sub-process /usr/bin/dpkg returned an error code (1) This is a serious bug as it makes installation fail, and violates sections 7.6.1 and 10.1 of the policy. An optimal solution would consist in only one of the packages installing that file, and renaming or removing the file in the other package. Depending on the circumstances you might also consider Replace relations or file diversions. If the conflicting situation cannot be resolved then, as a last resort, the two packages have to declare a mutual Conflict. Please take into account that Replaces, Conflicts and diversions should only be used when packages provide different implementations for the same functionality. Here is a list of files that are known to be shared by both packages (according to the Contents file for sid/amd64, which may be slightly out of sync): /usr/lib/nodejs/qs.js This bug is assigned to both packages. If you, the maintainers of the two packages in question, have agreed on which of the packages will resolve the problem please reassign the bug to that package. You may also register in the BTS that the other package is affected by the bug. -Ralf. PS: for more information about the detection of file overwrite errors of this kind see http://edos.debian.net/file-overwrites/. -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#645611: node-sphericalmercator and libnode-sphericalmercator: error when trying to install together
Package: libnode-sphericalmercator,node-sphericalmercator Version: libnode-sphericalmercator/1.0.1-1 Version: node-sphericalmercator/1.0.1-2 Severity: serious User: trei...@debian.org Usertags: edos-file-overwrite Date: 2011-10-17 Architecture: amd64 Distribution: sid Hi, automatic installation tests of packages that share a file and at the same time do not conflict by their package dependency relationships has detected the following problem: WARNING: The following packages cannot be authenticated! libc-ares2 libicu44 libv8-3.4.14.21 libev4 libnode-sphericalmercator nodejs node-sphericalmercator Authentication warning overridden. Can not write log, openpty() failed (/dev/pts not mounted?) Selecting previously unselected package libc-ares2. (Reading database ... 10586 files and directories currently installed.) Unpacking libc-ares2 (from .../libc-ares2_1.7.5-1_amd64.deb) ... Selecting previously unselected package libicu44. Unpacking libicu44 (from .../libicu44_4.4.2-2_amd64.deb) ... Selecting previously unselected package libv8-3.4.14.21. Unpacking libv8-3.4.14.21 (from .../libv8-3.4.14.21_3.4.14.21-3_amd64.deb) ... Selecting previously unselected package libev4. Unpacking libev4 (from .../libev4_1%3a4.04-1_amd64.deb) ... Selecting previously unselected package libnode-sphericalmercator. Unpacking libnode-sphericalmercator (from .../libnode-sphericalmercator_1.0.1-1_all.deb) ... Selecting previously unselected package nodejs. Unpacking nodejs (from .../nodejs_0.4.12-1_amd64.deb) ... Selecting previously unselected package node-sphericalmercator. Unpacking node-sphericalmercator (from .../node-sphericalmercator_1.0.1-2_all.deb) ... dpkg: error processing /var/cache/apt/archives/node-sphericalmercator_1.0.1-2_all.deb (--unpack): trying to overwrite '/usr/lib/nodejs/sphericalmercator.js', which is also in package libnode-sphericalmercator 1.0.1-1 configured to not write apport reports Processing triggers for man-db ... Errors were encountered while processing: /var/cache/apt/archives/node-sphericalmercator_1.0.1-2_all.deb E: Sub-process /usr/bin/dpkg returned an error code (1) This is a serious bug as it makes installation fail, and violates sections 7.6.1 and 10.1 of the policy. An optimal solution would consist in only one of the packages installing that file, and renaming or removing the file in the other package. Depending on the circumstances you might also consider Replace relations or file diversions. If the conflicting situation cannot be resolved then, as a last resort, the two packages have to declare a mutual Conflict. Please take into account that Replaces, Conflicts and diversions should only be used when packages provide different implementations for the same functionality. Here is a list of files that are known to be shared by both packages (according to the Contents file for sid/amd64, which may be slightly out of sync): /usr/lib/nodejs/sphericalmercator.js This bug is assigned to both packages. If you, the maintainers of the two packages in question, have agreed on which of the packages will resolve the problem please reassign the bug to that package. You may also register in the BTS that the other package is affected by the bug. -Ralf. PS: for more information about the detection of file overwrite errors of this kind see http://edos.debian.net/file-overwrites/. -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#645612: libopenscap1 and libopenscap0: error when trying to install together
Package: libopenscap0,libopenscap1 Version: libopenscap0/0.7.3-1 Version: libopenscap1/0.8.0-1 Severity: serious User: trei...@debian.org Usertags: edos-file-overwrite Date: 2011-10-17 Architecture: amd64 Distribution: sid Hi, automatic installation tests of packages that share a file and at the same time do not conflict by their package dependency relationships has detected the following problem: WARNING: The following packages cannot be authenticated! libsasl2-2 libldap-2.4-2 libpcre3 libnl1 libcap2 libxml2 libxslt1.1 libopenscap0 libopenscap1 Authentication warning overridden. Can not write log, openpty() failed (/dev/pts not mounted?) Selecting previously unselected package libsasl2-2. (Reading database ... 10586 files and directories currently installed.) Unpacking libsasl2-2 (from .../libsasl2-2_2.1.25.dfsg1-2_amd64.deb) ... Selecting previously unselected package libldap-2.4-2. Unpacking libldap-2.4-2 (from .../libldap-2.4-2_2.4.25-3_amd64.deb) ... Selecting previously unselected package libpcre3. Unpacking libpcre3 (from .../libpcre3_8.12-4_amd64.deb) ... Selecting previously unselected package libnl1. Unpacking libnl1 (from .../libnl1_1.1-7_amd64.deb) ... Selecting previously unselected package libcap2. Unpacking libcap2 (from .../libcap2_1%3a2.22-1_amd64.deb) ... Selecting previously unselected package libxml2. Unpacking libxml2 (from .../libxml2_2.7.8.dfsg-5_amd64.deb) ... Selecting previously unselected package libxslt1.1. Unpacking libxslt1.1 (from .../libxslt1.1_1.1.26-8_amd64.deb) ... Selecting previously unselected package libopenscap0. Unpacking libopenscap0 (from .../libopenscap0_0.7.3-1_amd64.deb) ... Selecting previously unselected package libopenscap1. Unpacking libopenscap1 (from .../libopenscap1_0.8.0-1_amd64.deb) ... dpkg: error processing /var/cache/apt/archives/libopenscap1_0.8.0-1_amd64.deb (--unpack): trying to overwrite '/usr/bin/oscap', which is also in package libopenscap0 0.7.3-1 configured to not write apport reports dpkg-deb: error: subprocess paste was killed by signal (Broken pipe) Processing triggers for man-db ... Errors were encountered while processing: /var/cache/apt/archives/libopenscap1_0.8.0-1_amd64.deb E: Sub-process /usr/bin/dpkg returned an error code (1) This is a serious bug as it makes installation fail, and violates sections 7.6.1 and 10.1 of the policy. An optimal solution would consist in only one of the packages installing that file, and renaming or removing the file in the other package. Depending on the circumstances you might also consider Replace relations or file diversions. If the conflicting situation cannot be resolved then, as a last resort, the two packages have to declare a mutual Conflict. Please take into account that Replaces, Conflicts and diversions should only be used when packages provide different implementations for the same functionality. Here is a list of files that are known to be shared by both packages (according to the Contents file for sid/amd64, which may be slightly out of sync): /usr/bin/oscap /usr/lib/openscap/probe_dnscache /usr/lib/openscap/probe_dpkginfo /usr/lib/openscap/probe_family /usr/lib/openscap/probe_file /usr/lib/openscap/probe_filehash /usr/lib/openscap/probe_inetlisteningservers /usr/lib/openscap/probe_interface /usr/lib/openscap/probe_ldap57 /usr/lib/openscap/probe_partition /usr/lib/openscap/probe_password /usr/lib/openscap/probe_process /usr/lib/openscap/probe_runlevel /usr/lib/openscap/probe_shadow /usr/lib/openscap/probe_sysctl /usr/lib/openscap/probe_system_info /usr/lib/openscap/probe_textfilecontent /usr/lib/openscap/probe_textfilecontent54 /usr/lib/openscap/probe_uname /usr/lib/openscap/probe_xinetd /usr/lib/openscap/probe_xmlfilecontent /usr/share/man/man8/oscap.8.gz /usr/share/openscap/scap-fedora14-oval.xml /usr/share/openscap/scap-fedora14-xccdf.xml /usr/share/openscap/scap-rhel6-oval.xml /usr/share/openscap/scap-rhel6-xccdf.xml /usr/share/openscap/schemas/oval/5.8/aix-definitions-schema.xsd /usr/share/openscap/schemas/oval/5.8/aix-system-characteristics-schema.xsd /usr/share/openscap/schemas/oval/5.8/apache-definitions-schema.xsd /usr/share/openscap/schemas/oval/5.8/apache-system-characteristics-schema.xsd /usr/share/openscap/schemas/oval/5.8/catos-definitions-schema.xsd /usr/share/openscap/schemas/oval/5.8/catos-system-characteristics-schema.xsd /usr/share/openscap/schemas/oval/5.8/debian-definitions-schema.xsd /usr/share/openscap/schemas/oval/5.8/debian-system-characteristics-schema.xsd /usr/share/openscap/schemas/oval/5.8/esx-definitions-schema.xsd /usr/share/openscap/schemas/oval/5.8/esx-system-characteristics-schema.xsd /usr/share/openscap/schemas/oval/5.8/freebsd-definitions-schema.xsd /usr/share/openscap/schemas/oval/5.8/freebsd-system-characteristics-schema.xsd /usr/share/openscap/schemas/oval/5.8/hpux-definitions-schema.xsd
Bug#645612: also concerns -dbg pacakages
Hello, this bug also concerns the -dbg packages: Errors were encountered while processing: /var/cache/apt/archives/libopenscap1_0.8.0-1_amd64.deb /var/cache/apt/archives/libopenscap1-dbg_0.8.0-1_amd64.deb E: Sub-process /usr/bin/dpkg returned an error code (1) Here is a list of files that are known to be shared by both packages (according to the Contents file for sid/amd64, which may be slightly out of sync): /usr/lib/debug/usr/bin/oscap /usr/lib/debug/usr/lib/openscap/probe_dnscache /usr/lib/debug/usr/lib/openscap/probe_dpkginfo /usr/lib/debug/usr/lib/openscap/probe_family /usr/lib/debug/usr/lib/openscap/probe_file /usr/lib/debug/usr/lib/openscap/probe_filehash /usr/lib/debug/usr/lib/openscap/probe_inetlisteningservers /usr/lib/debug/usr/lib/openscap/probe_interface /usr/lib/debug/usr/lib/openscap/probe_ldap57 /usr/lib/debug/usr/lib/openscap/probe_partition /usr/lib/debug/usr/lib/openscap/probe_password /usr/lib/debug/usr/lib/openscap/probe_process /usr/lib/debug/usr/lib/openscap/probe_runlevel /usr/lib/debug/usr/lib/openscap/probe_shadow /usr/lib/debug/usr/lib/openscap/probe_sysctl /usr/lib/debug/usr/lib/openscap/probe_system_info /usr/lib/debug/usr/lib/openscap/probe_textfilecontent /usr/lib/debug/usr/lib/openscap/probe_textfilecontent54 /usr/lib/debug/usr/lib/openscap/probe_uname /usr/lib/debug/usr/lib/openscap/probe_xinetd /usr/lib/debug/usr/lib/openscap/probe_xmlfilecontent /usr/lib/debug/usr/lib/perl5/_openscap_pm.so /usr/lib/debug/usr/lib/python2.6/dist-packages/_openscap_py.so /usr/lib/debug/usr/lib/python2.7/dist-packages/_openscap_py.so -Ralf. -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#645601: marked as done (node-backbone-dirty and libnode-backbone-dirty: error when trying to install together)
Your message dated Mon, 17 Oct 2011 13:53:52 +0200 with message-id 20111017135352.687f2983@local and subject line Re: [Pkg-javascript-devel] Bug#645601: node-backbone-dirty and libnode-backbone-dirty: error when trying to install together has caused the Debian Bug report #645601, regarding node-backbone-dirty and libnode-backbone-dirty: error when trying to install together to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 645601: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=645601 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: libnode-backbone-dirty,node-backbone-dirty Version: libnode-backbone-dirty/1.1.2-1 Version: node-backbone-dirty/1.1.2-2 Severity: serious User: trei...@debian.org Usertags: edos-file-overwrite Date: 2011-10-17 Architecture: amd64 Distribution: sid Hi, automatic installation tests of packages that share a file and at the same time do not conflict by their package dependency relationships has detected the following problem: WARNING: The following packages cannot be authenticated! libc-ares2 libicu44 libjs-underscore libjs-backbone libev4 libv8-3.4.14.21 nodejs libnode-dirty node-dirty libnode-backbone-dirty node-backbone-dirty Authentication warning overridden. Can not write log, openpty() failed (/dev/pts not mounted?) Selecting previously unselected package libc-ares2. (Reading database ... 10586 files and directories currently installed.) Unpacking libc-ares2 (from .../libc-ares2_1.7.5-1_amd64.deb) ... Selecting previously unselected package libicu44. Unpacking libicu44 (from .../libicu44_4.4.2-2_amd64.deb) ... Selecting previously unselected package libjs-underscore. Unpacking libjs-underscore (from .../libjs-underscore_1.1.6-1_all.deb) ... Selecting previously unselected package libjs-backbone. Unpacking libjs-backbone (from .../libjs-backbone_0.5.3-2_all.deb) ... Selecting previously unselected package libev4. Unpacking libev4 (from .../libev4_1%3a4.04-1_amd64.deb) ... Selecting previously unselected package libv8-3.4.14.21. Unpacking libv8-3.4.14.21 (from .../libv8-3.4.14.21_3.4.14.21-3_amd64.deb) ... Selecting previously unselected package nodejs. Unpacking nodejs (from .../nodejs_0.4.12-1_amd64.deb) ... Selecting previously unselected package libnode-dirty. Unpacking libnode-dirty (from .../libnode-dirty_0.9.4-1_all.deb) ... Selecting previously unselected package node-dirty. Unpacking node-dirty (from .../node-dirty_0.9.4-2_all.deb) ... dpkg: error processing /var/cache/apt/archives/node-dirty_0.9.4-2_all.deb (--unpack): trying to overwrite '/usr/lib/nodejs/dirty/dirty.js', which is also in package libnode-dirty 0.9.4-1 configured to not write apport reports Selecting previously unselected package libnode-backbone-dirty. Unpacking libnode-backbone-dirty (from .../libnode-backbone-dirty_1.1.2-1_all.deb) ... Selecting previously unselected package node-backbone-dirty. Unpacking node-backbone-dirty (from .../node-backbone-dirty_1.1.2-2_all.deb) ... dpkg: error processing /var/cache/apt/archives/node-backbone-dirty_1.1.2-2_all.deb (--unpack): trying to overwrite '/usr/share/nodejs/backbone-dirty.js', which is also in package libnode-backbone-dirty 1.1.2-1 configured to not write apport reports Processing triggers for man-db ... Errors were encountered while processing: /var/cache/apt/archives/node-dirty_0.9.4-2_all.deb /var/cache/apt/archives/node-backbone-dirty_1.1.2-2_all.deb E: Sub-process /usr/bin/dpkg returned an error code (1) This is a serious bug as it makes installation fail, and violates sections 7.6.1 and 10.1 of the policy. An optimal solution would consist in only one of the packages installing that file, and renaming or removing the file in the other package. Depending on the circumstances you might also consider Replace relations or file diversions. If the conflicting situation cannot be resolved then, as a last resort, the two packages have to declare a mutual Conflict. Please take into account that Replaces, Conflicts and diversions should only be used when packages provide different implementations for the same functionality. Here is a list of files that are known to be shared by both packages (according to the Contents file for sid/amd64, which may be slightly out of sync): /usr/share/nodejs/backbone-dirty.js This bug is assigned to both packages. If you, the maintainers of the two packages in question, have agreed on which of the packages will resolve the problem please reassign the bug to that package. You may also register in the BTS that the other package is affected by the bug. -Ralf. PS: for
Bug#645602: marked as done (node-chrono and libnode-chrono: error when trying to install together)
Your message dated Mon, 17 Oct 2011 13:53:52 +0200 with message-id 20111017135352.687f2983@local and subject line Re: [Pkg-javascript-devel] Bug#645601: node-backbone-dirty and libnode-backbone-dirty: error when trying to install together has caused the Debian Bug report #645602, regarding node-chrono and libnode-chrono: error when trying to install together to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 645602: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=645602 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: libnode-chrono,node-chrono Version: libnode-chrono/1.0.2-1 Version: node-chrono/1.0.2-2 Severity: serious User: trei...@debian.org Usertags: edos-file-overwrite Date: 2011-10-17 Architecture: amd64 Distribution: sid Hi, automatic installation tests of packages that share a file and at the same time do not conflict by their package dependency relationships has detected the following problem: WARNING: The following packages cannot be authenticated! libc-ares2 libicu44 libv8-3.4.14.21 libev4 libnode-chrono nodejs node-chrono Authentication warning overridden. Can not write log, openpty() failed (/dev/pts not mounted?) Selecting previously unselected package libc-ares2. (Reading database ... 10586 files and directories currently installed.) Unpacking libc-ares2 (from .../libc-ares2_1.7.5-1_amd64.deb) ... Selecting previously unselected package libicu44. Unpacking libicu44 (from .../libicu44_4.4.2-2_amd64.deb) ... Selecting previously unselected package libv8-3.4.14.21. Unpacking libv8-3.4.14.21 (from .../libv8-3.4.14.21_3.4.14.21-3_amd64.deb) ... Selecting previously unselected package libev4. Unpacking libev4 (from .../libev4_1%3a4.04-1_amd64.deb) ... Selecting previously unselected package libnode-chrono. Unpacking libnode-chrono (from .../libnode-chrono_1.0.2-1_all.deb) ... Selecting previously unselected package nodejs. Unpacking nodejs (from .../nodejs_0.4.12-1_amd64.deb) ... Selecting previously unselected package node-chrono. Unpacking node-chrono (from .../node-chrono_1.0.2-2_all.deb) ... dpkg: error processing /var/cache/apt/archives/node-chrono_1.0.2-2_all.deb (--unpack): trying to overwrite '/usr/lib/nodejs/chrono.js', which is also in package libnode-chrono 1.0.2-1 configured to not write apport reports Processing triggers for man-db ... Errors were encountered while processing: /var/cache/apt/archives/node-chrono_1.0.2-2_all.deb E: Sub-process /usr/bin/dpkg returned an error code (1) This is a serious bug as it makes installation fail, and violates sections 7.6.1 and 10.1 of the policy. An optimal solution would consist in only one of the packages installing that file, and renaming or removing the file in the other package. Depending on the circumstances you might also consider Replace relations or file diversions. If the conflicting situation cannot be resolved then, as a last resort, the two packages have to declare a mutual Conflict. Please take into account that Replaces, Conflicts and diversions should only be used when packages provide different implementations for the same functionality. Here is a list of files that are known to be shared by both packages (according to the Contents file for sid/amd64, which may be slightly out of sync): /usr/lib/nodejs/chrono.js This bug is assigned to both packages. If you, the maintainers of the two packages in question, have agreed on which of the packages will resolve the problem please reassign the bug to that package. You may also register in the BTS that the other package is affected by the bug. -Ralf. PS: for more information about the detection of file overwrite errors of this kind see http://edos.debian.net/file-overwrites/. ---End Message--- ---BeginMessage--- Hello Ralf, On Mon, 17 Oct 2011 12:54:11 +0200, Ralf Treinen wrote: Package: libnode-backbone-dirty,node-backbone-dirty Version: libnode-backbone-dirty/1.1.2-1 Version: node-backbone-dirty/1.1.2-2 Severity: serious User: trei...@debian.org Usertags: edos-file-overwrite [..] (and much more similar bugs) libnode-* were renamed node-* while they were in NEW. They were built fromthe same source, and as you may notice, node-* have a revision of -2, while libnode-* had -1. There must've been some problem when they got ACCEPTed, but libnode-* packages aren't currently built from any source, so they should be removed by the auto-cruft-removal script. As you can see, their removals is already scheduled: http://ftp-master.debian.org/cruft-report-daily.txt I'm closing these bugs. David -- . ''`. Debian developer |
Bug#645604: marked as done (node-connect and libnode-connect: error when trying to install together)
Your message dated Mon, 17 Oct 2011 13:53:52 +0200 with message-id 20111017135352.687f2983@local and subject line Re: [Pkg-javascript-devel] Bug#645601: node-backbone-dirty and libnode-backbone-dirty: error when trying to install together has caused the Debian Bug report #645604, regarding node-connect and libnode-connect: error when trying to install together to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 645604: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=645604 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: libnode-connect,node-connect Version: libnode-connect/1.7.1-1 Version: node-connect/1.7.1-2 Severity: serious User: trei...@debian.org Usertags: edos-file-overwrite Date: 2011-10-17 Architecture: amd64 Distribution: sid Hi, automatic installation tests of packages that share a file and at the same time do not conflict by their package dependency relationships has detected the following problem: WARNING: The following packages cannot be authenticated! libc-ares2 libicu44 libv8-3.4.14.21 libev4 libnode-qs libnode-mime libnode-connect nodejs node-qs node-mime node-connect Authentication warning overridden. Can not write log, openpty() failed (/dev/pts not mounted?) Selecting previously unselected package libc-ares2. (Reading database ... 10586 files and directories currently installed.) Unpacking libc-ares2 (from .../libc-ares2_1.7.5-1_amd64.deb) ... Selecting previously unselected package libicu44. Unpacking libicu44 (from .../libicu44_4.4.2-2_amd64.deb) ... Selecting previously unselected package libv8-3.4.14.21. Unpacking libv8-3.4.14.21 (from .../libv8-3.4.14.21_3.4.14.21-3_amd64.deb) ... Selecting previously unselected package libev4. Unpacking libev4 (from .../libev4_1%3a4.04-1_amd64.deb) ... Selecting previously unselected package libnode-qs. Unpacking libnode-qs (from .../libnode-qs_0.3.1-1_all.deb) ... Selecting previously unselected package libnode-mime. Unpacking libnode-mime (from .../libnode-mime_1.2.4-1_all.deb) ... Selecting previously unselected package libnode-connect. Unpacking libnode-connect (from .../libnode-connect_1.7.1-1_all.deb) ... Selecting previously unselected package nodejs. Unpacking nodejs (from .../nodejs_0.4.12-1_amd64.deb) ... Selecting previously unselected package node-qs. Unpacking node-qs (from .../node-qs_0.3.1-2_all.deb) ... dpkg: error processing /var/cache/apt/archives/node-qs_0.3.1-2_all.deb (--unpack): trying to overwrite '/usr/lib/nodejs/qs.js', which is also in package libnode-qs 0.3.1-1 configured to not write apport reports Selecting previously unselected package node-mime. Unpacking node-mime (from .../node-mime_1.2.4-2_all.deb) ... dpkg: error processing /var/cache/apt/archives/node-mime_1.2.4-2_all.deb (--unpack): trying to overwrite '/usr/lib/nodejs/mime.js', which is also in package libnode-mime 1.2.4-1 configured to not write apport reports Selecting previously unselected package node-connect. Unpacking node-connect (from .../node-connect_1.7.1-2_all.deb) ... dpkg: error processing /var/cache/apt/archives/node-connect_1.7.1-2_all.deb (--unpack): trying to overwrite '/usr/lib/nodejs/connect/http.js', which is also in package libnode-connect 1.7.1-1 configured to not write apport reports Processing triggers for man-db ... Errors were encountered while processing: /var/cache/apt/archives/node-qs_0.3.1-2_all.deb /var/cache/apt/archives/node-mime_1.2.4-2_all.deb /var/cache/apt/archives/node-connect_1.7.1-2_all.deb E: Sub-process /usr/bin/dpkg returned an error code (1) This is a serious bug as it makes installation fail, and violates sections 7.6.1 and 10.1 of the policy. An optimal solution would consist in only one of the packages installing that file, and renaming or removing the file in the other package. Depending on the circumstances you might also consider Replace relations or file diversions. If the conflicting situation cannot be resolved then, as a last resort, the two packages have to declare a mutual Conflict. Please take into account that Replaces, Conflicts and diversions should only be used when packages provide different implementations for the same functionality. Here is a list of files that are known to be shared by both packages (according to the Contents file for sid/amd64, which may be slightly out of sync): /usr/lib/nodejs/connect/cache.js /usr/lib/nodejs/connect/connect.js /usr/lib/nodejs/connect/http.js /usr/lib/nodejs/connect/https.js /usr/lib/nodejs/connect/index.js /usr/lib/nodejs/connect/middleware/basicAuth.js
Bug#645605: marked as done (node-dirty and libnode-dirty: error when trying to install together)
Your message dated Mon, 17 Oct 2011 13:53:52 +0200 with message-id 20111017135352.687f2983@local and subject line Re: [Pkg-javascript-devel] Bug#645601: node-backbone-dirty and libnode-backbone-dirty: error when trying to install together has caused the Debian Bug report #645605, regarding node-dirty and libnode-dirty: error when trying to install together to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 645605: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=645605 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: libnode-dirty,node-dirty Version: libnode-dirty/0.9.4-1 Version: node-dirty/0.9.4-2 Severity: serious User: trei...@debian.org Usertags: edos-file-overwrite Date: 2011-10-17 Architecture: amd64 Distribution: sid Hi, automatic installation tests of packages that share a file and at the same time do not conflict by their package dependency relationships has detected the following problem: WARNING: The following packages cannot be authenticated! libc-ares2 libicu44 libev4 libv8-3.4.14.21 nodejs libnode-dirty node-dirty Authentication warning overridden. Can not write log, openpty() failed (/dev/pts not mounted?) Selecting previously unselected package libc-ares2. (Reading database ... 10586 files and directories currently installed.) Unpacking libc-ares2 (from .../libc-ares2_1.7.5-1_amd64.deb) ... Selecting previously unselected package libicu44. Unpacking libicu44 (from .../libicu44_4.4.2-2_amd64.deb) ... Selecting previously unselected package libev4. Unpacking libev4 (from .../libev4_1%3a4.04-1_amd64.deb) ... Selecting previously unselected package libv8-3.4.14.21. Unpacking libv8-3.4.14.21 (from .../libv8-3.4.14.21_3.4.14.21-3_amd64.deb) ... Selecting previously unselected package nodejs. Unpacking nodejs (from .../nodejs_0.4.12-1_amd64.deb) ... Selecting previously unselected package libnode-dirty. Unpacking libnode-dirty (from .../libnode-dirty_0.9.4-1_all.deb) ... Selecting previously unselected package node-dirty. Unpacking node-dirty (from .../node-dirty_0.9.4-2_all.deb) ... dpkg: error processing /var/cache/apt/archives/node-dirty_0.9.4-2_all.deb (--unpack): trying to overwrite '/usr/lib/nodejs/dirty/dirty.js', which is also in package libnode-dirty 0.9.4-1 configured to not write apport reports Processing triggers for man-db ... Errors were encountered while processing: /var/cache/apt/archives/node-dirty_0.9.4-2_all.deb E: Sub-process /usr/bin/dpkg returned an error code (1) This is a serious bug as it makes installation fail, and violates sections 7.6.1 and 10.1 of the policy. An optimal solution would consist in only one of the packages installing that file, and renaming or removing the file in the other package. Depending on the circumstances you might also consider Replace relations or file diversions. If the conflicting situation cannot be resolved then, as a last resort, the two packages have to declare a mutual Conflict. Please take into account that Replaces, Conflicts and diversions should only be used when packages provide different implementations for the same functionality. Here is a list of files that are known to be shared by both packages (according to the Contents file for sid/amd64, which may be slightly out of sync): /usr/lib/nodejs/dirty/dirty.js /usr/lib/nodejs/dirty/index.js This bug is assigned to both packages. If you, the maintainers of the two packages in question, have agreed on which of the packages will resolve the problem please reassign the bug to that package. You may also register in the BTS that the other package is affected by the bug. -Ralf. PS: for more information about the detection of file overwrite errors of this kind see http://edos.debian.net/file-overwrites/. ---End Message--- ---BeginMessage--- Hello Ralf, On Mon, 17 Oct 2011 12:54:11 +0200, Ralf Treinen wrote: Package: libnode-backbone-dirty,node-backbone-dirty Version: libnode-backbone-dirty/1.1.2-1 Version: node-backbone-dirty/1.1.2-2 Severity: serious User: trei...@debian.org Usertags: edos-file-overwrite [..] (and much more similar bugs) libnode-* were renamed node-* while they were in NEW. They were built fromthe same source, and as you may notice, node-* have a revision of -2, while libnode-* had -1. There must've been some problem when they got ACCEPTed, but libnode-* packages aren't currently built from any source, so they should be removed by the auto-cruft-removal script. As you can see, their removals is already scheduled: http://ftp-master.debian.org/cruft-report-daily.txt I'm closing these bugs. David -- .
Bug#645606: marked as done (node-express and libnode-express: error when trying to install together)
Your message dated Mon, 17 Oct 2011 13:53:52 +0200 with message-id 20111017135352.687f2983@local and subject line Re: [Pkg-javascript-devel] Bug#645601: node-backbone-dirty and libnode-backbone-dirty: error when trying to install together has caused the Debian Bug report #645606, regarding node-express and libnode-express: error when trying to install together to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 645606: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=645606 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: libnode-express,node-express Version: libnode-express/2.4.7-1 Version: node-express/2.4.7-2 Severity: serious User: trei...@debian.org Usertags: edos-file-overwrite Date: 2011-10-17 Architecture: amd64 Distribution: sid Hi, automatic installation tests of packages that share a file and at the same time do not conflict by their package dependency relationships has detected the following problem: WARNING: The following packages cannot be authenticated! libc-ares2 libicu44 libv8-3.4.14.21 libev4 libnode-qs libnode-mime libnode-connect libnode-mkdirp libnode-express nodejs node-qs node-mime node-connect node-mkdirp node-express Authentication warning overridden. Can not write log, openpty() failed (/dev/pts not mounted?) Selecting previously unselected package libc-ares2. (Reading database ... 10586 files and directories currently installed.) Unpacking libc-ares2 (from .../libc-ares2_1.7.5-1_amd64.deb) ... Selecting previously unselected package libicu44. Unpacking libicu44 (from .../libicu44_4.4.2-2_amd64.deb) ... Selecting previously unselected package libv8-3.4.14.21. Unpacking libv8-3.4.14.21 (from .../libv8-3.4.14.21_3.4.14.21-3_amd64.deb) ... Selecting previously unselected package libev4. Unpacking libev4 (from .../libev4_1%3a4.04-1_amd64.deb) ... Selecting previously unselected package libnode-qs. Unpacking libnode-qs (from .../libnode-qs_0.3.1-1_all.deb) ... Selecting previously unselected package libnode-mime. Unpacking libnode-mime (from .../libnode-mime_1.2.4-1_all.deb) ... Selecting previously unselected package libnode-connect. Unpacking libnode-connect (from .../libnode-connect_1.7.1-1_all.deb) ... Selecting previously unselected package libnode-mkdirp. Unpacking libnode-mkdirp (from .../libnode-mkdirp_0.0.7-1_all.deb) ... Selecting previously unselected package libnode-express. Unpacking libnode-express (from .../libnode-express_2.4.7-1_all.deb) ... Selecting previously unselected package nodejs. Unpacking nodejs (from .../nodejs_0.4.12-1_amd64.deb) ... Selecting previously unselected package node-qs. Unpacking node-qs (from .../node-qs_0.3.1-2_all.deb) ... dpkg: error processing /var/cache/apt/archives/node-qs_0.3.1-2_all.deb (--unpack): trying to overwrite '/usr/lib/nodejs/qs.js', which is also in package libnode-qs 0.3.1-1 configured to not write apport reports Selecting previously unselected package node-mime. Unpacking node-mime (from .../node-mime_1.2.4-2_all.deb) ... dpkg: error processing /var/cache/apt/archives/node-mime_1.2.4-2_all.deb (--unpack): trying to overwrite '/usr/lib/nodejs/mime.js', which is also in package libnode-mime 1.2.4-1 configured to not write apport reports Selecting previously unselected package node-connect. Unpacking node-connect (from .../node-connect_1.7.1-2_all.deb) ... dpkg: error processing /var/cache/apt/archives/node-connect_1.7.1-2_all.deb (--unpack): trying to overwrite '/usr/lib/nodejs/connect/http.js', which is also in package libnode-connect 1.7.1-1 configured to not write apport reports Selecting previously unselected package node-mkdirp. Unpacking node-mkdirp (from .../node-mkdirp_0.0.7-2_all.deb) ... dpkg: error processing /var/cache/apt/archives/node-mkdirp_0.0.7-2_all.deb (--unpack): trying to overwrite '/usr/lib/nodejs/mkdirp.js', which is also in package libnode-mkdirp 0.0.7-1 configured to not write apport reports Selecting previously unselected package node-express. Unpacking node-express (from .../node-express_2.4.7-2_all.deb) ... dpkg: error processing /var/cache/apt/archives/node-express_2.4.7-2_all.deb (--unpack): trying to overwrite '/usr/lib/nodejs/express/request.js', which is also in package libnode-express 2.4.7-1 configured to not write apport reports Processing triggers for man-db ... Errors were encountered while processing: /var/cache/apt/archives/node-qs_0.3.1-2_all.deb /var/cache/apt/archives/node-mime_1.2.4-2_all.deb /var/cache/apt/archives/node-connect_1.7.1-2_all.deb /var/cache/apt/archives/node-mkdirp_0.0.7-2_all.deb
Bug#645607: marked as done (node-mime and libnode-mime: error when trying to install together)
Your message dated Mon, 17 Oct 2011 13:53:52 +0200 with message-id 20111017135352.687f2983@local and subject line Re: [Pkg-javascript-devel] Bug#645601: node-backbone-dirty and libnode-backbone-dirty: error when trying to install together has caused the Debian Bug report #645607, regarding node-mime and libnode-mime: error when trying to install together to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 645607: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=645607 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: libnode-mime,node-mime Version: libnode-mime/1.2.4-1 Version: node-mime/1.2.4-2 Severity: serious User: trei...@debian.org Usertags: edos-file-overwrite Date: 2011-10-17 Architecture: amd64 Distribution: sid Hi, automatic installation tests of packages that share a file and at the same time do not conflict by their package dependency relationships has detected the following problem: WARNING: The following packages cannot be authenticated! libc-ares2 libicu44 libv8-3.4.14.21 libev4 libnode-mime nodejs node-mime Authentication warning overridden. Can not write log, openpty() failed (/dev/pts not mounted?) Selecting previously unselected package libc-ares2. (Reading database ... 10586 files and directories currently installed.) Unpacking libc-ares2 (from .../libc-ares2_1.7.5-1_amd64.deb) ... Selecting previously unselected package libicu44. Unpacking libicu44 (from .../libicu44_4.4.2-2_amd64.deb) ... Selecting previously unselected package libv8-3.4.14.21. Unpacking libv8-3.4.14.21 (from .../libv8-3.4.14.21_3.4.14.21-3_amd64.deb) ... Selecting previously unselected package libev4. Unpacking libev4 (from .../libev4_1%3a4.04-1_amd64.deb) ... Selecting previously unselected package libnode-mime. Unpacking libnode-mime (from .../libnode-mime_1.2.4-1_all.deb) ... Selecting previously unselected package nodejs. Unpacking nodejs (from .../nodejs_0.4.12-1_amd64.deb) ... Selecting previously unselected package node-mime. Unpacking node-mime (from .../node-mime_1.2.4-2_all.deb) ... dpkg: error processing /var/cache/apt/archives/node-mime_1.2.4-2_all.deb (--unpack): trying to overwrite '/usr/lib/nodejs/mime.js', which is also in package libnode-mime 1.2.4-1 configured to not write apport reports Processing triggers for man-db ... Errors were encountered while processing: /var/cache/apt/archives/node-mime_1.2.4-2_all.deb E: Sub-process /usr/bin/dpkg returned an error code (1) This is a serious bug as it makes installation fail, and violates sections 7.6.1 and 10.1 of the policy. An optimal solution would consist in only one of the packages installing that file, and renaming or removing the file in the other package. Depending on the circumstances you might also consider Replace relations or file diversions. If the conflicting situation cannot be resolved then, as a last resort, the two packages have to declare a mutual Conflict. Please take into account that Replaces, Conflicts and diversions should only be used when packages provide different implementations for the same functionality. Here is a list of files that are known to be shared by both packages (according to the Contents file for sid/amd64, which may be slightly out of sync): /usr/lib/nodejs/mime.js This bug is assigned to both packages. If you, the maintainers of the two packages in question, have agreed on which of the packages will resolve the problem please reassign the bug to that package. You may also register in the BTS that the other package is affected by the bug. -Ralf. PS: for more information about the detection of file overwrite errors of this kind see http://edos.debian.net/file-overwrites/. ---End Message--- ---BeginMessage--- Hello Ralf, On Mon, 17 Oct 2011 12:54:11 +0200, Ralf Treinen wrote: Package: libnode-backbone-dirty,node-backbone-dirty Version: libnode-backbone-dirty/1.1.2-1 Version: node-backbone-dirty/1.1.2-2 Severity: serious User: trei...@debian.org Usertags: edos-file-overwrite [..] (and much more similar bugs) libnode-* were renamed node-* while they were in NEW. They were built fromthe same source, and as you may notice, node-* have a revision of -2, while libnode-* had -1. There must've been some problem when they got ACCEPTed, but libnode-* packages aren't currently built from any source, so they should be removed by the auto-cruft-removal script. As you can see, their removals is already scheduled: http://ftp-master.debian.org/cruft-report-daily.txt I'm closing these bugs. David -- . ''`. Debian developer | http://wiki.debian.org/DavidPaleino :
Bug#645608: marked as done (node-mirror and libnode-mirror: error when trying to install together)
Your message dated Mon, 17 Oct 2011 13:53:52 +0200 with message-id 20111017135352.687f2983@local and subject line Re: [Pkg-javascript-devel] Bug#645601: node-backbone-dirty and libnode-backbone-dirty: error when trying to install together has caused the Debian Bug report #645608, regarding node-mirror and libnode-mirror: error when trying to install together to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 645608: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=645608 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: libnode-mirror,node-mirror Version: libnode-mirror/0.3.3-1 Version: node-mirror/0.3.3-2 Severity: serious User: trei...@debian.org Usertags: edos-file-overwrite Date: 2011-10-17 Architecture: amd64 Distribution: sid Hi, automatic installation tests of packages that share a file and at the same time do not conflict by their package dependency relationships has detected the following problem: WARNING: The following packages cannot be authenticated! libc-ares2 libicu44 libv8-3.4.14.21 libev4 libnode-mirror nodejs node-mirror Authentication warning overridden. Can not write log, openpty() failed (/dev/pts not mounted?) Selecting previously unselected package libc-ares2. (Reading database ... 10586 files and directories currently installed.) Unpacking libc-ares2 (from .../libc-ares2_1.7.5-1_amd64.deb) ... Selecting previously unselected package libicu44. Unpacking libicu44 (from .../libicu44_4.4.2-2_amd64.deb) ... Selecting previously unselected package libv8-3.4.14.21. Unpacking libv8-3.4.14.21 (from .../libv8-3.4.14.21_3.4.14.21-3_amd64.deb) ... Selecting previously unselected package libev4. Unpacking libev4 (from .../libev4_1%3a4.04-1_amd64.deb) ... Selecting previously unselected package libnode-mirror. Unpacking libnode-mirror (from .../libnode-mirror_0.3.3-1_all.deb) ... Selecting previously unselected package nodejs. Unpacking nodejs (from .../nodejs_0.4.12-1_amd64.deb) ... Selecting previously unselected package node-mirror. Unpacking node-mirror (from .../node-mirror_0.3.3-2_all.deb) ... dpkg: error processing /var/cache/apt/archives/node-mirror_0.3.3-2_all.deb (--unpack): trying to overwrite '/usr/lib/nodejs/mirror.js', which is also in package libnode-mirror 0.3.3-1 configured to not write apport reports Processing triggers for man-db ... Errors were encountered while processing: /var/cache/apt/archives/node-mirror_0.3.3-2_all.deb E: Sub-process /usr/bin/dpkg returned an error code (1) This is a serious bug as it makes installation fail, and violates sections 7.6.1 and 10.1 of the policy. An optimal solution would consist in only one of the packages installing that file, and renaming or removing the file in the other package. Depending on the circumstances you might also consider Replace relations or file diversions. If the conflicting situation cannot be resolved then, as a last resort, the two packages have to declare a mutual Conflict. Please take into account that Replaces, Conflicts and diversions should only be used when packages provide different implementations for the same functionality. Here is a list of files that are known to be shared by both packages (according to the Contents file for sid/amd64, which may be slightly out of sync): /usr/lib/nodejs/mirror.js This bug is assigned to both packages. If you, the maintainers of the two packages in question, have agreed on which of the packages will resolve the problem please reassign the bug to that package. You may also register in the BTS that the other package is affected by the bug. -Ralf. PS: for more information about the detection of file overwrite errors of this kind see http://edos.debian.net/file-overwrites/. ---End Message--- ---BeginMessage--- Hello Ralf, On Mon, 17 Oct 2011 12:54:11 +0200, Ralf Treinen wrote: Package: libnode-backbone-dirty,node-backbone-dirty Version: libnode-backbone-dirty/1.1.2-1 Version: node-backbone-dirty/1.1.2-2 Severity: serious User: trei...@debian.org Usertags: edos-file-overwrite [..] (and much more similar bugs) libnode-* were renamed node-* while they were in NEW. They were built fromthe same source, and as you may notice, node-* have a revision of -2, while libnode-* had -1. There must've been some problem when they got ACCEPTed, but libnode-* packages aren't currently built from any source, so they should be removed by the auto-cruft-removal script. As you can see, their removals is already scheduled: http://ftp-master.debian.org/cruft-report-daily.txt I'm closing these bugs. David -- . ''`. Debian developer |
Bug#645609: marked as done (node-mkdirp and libnode-mkdirp: error when trying to install together)
Your message dated Mon, 17 Oct 2011 13:53:52 +0200 with message-id 20111017135352.687f2983@local and subject line Re: [Pkg-javascript-devel] Bug#645601: node-backbone-dirty and libnode-backbone-dirty: error when trying to install together has caused the Debian Bug report #645609, regarding node-mkdirp and libnode-mkdirp: error when trying to install together to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 645609: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=645609 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: libnode-mkdirp,node-mkdirp Version: libnode-mkdirp/0.0.7-1 Version: node-mkdirp/0.0.7-2 Severity: serious User: trei...@debian.org Usertags: edos-file-overwrite Date: 2011-10-17 Architecture: amd64 Distribution: sid Hi, automatic installation tests of packages that share a file and at the same time do not conflict by their package dependency relationships has detected the following problem: WARNING: The following packages cannot be authenticated! libc-ares2 libicu44 libv8-3.4.14.21 libev4 libnode-mkdirp nodejs node-mkdirp Authentication warning overridden. Can not write log, openpty() failed (/dev/pts not mounted?) Selecting previously unselected package libc-ares2. (Reading database ... 10586 files and directories currently installed.) Unpacking libc-ares2 (from .../libc-ares2_1.7.5-1_amd64.deb) ... Selecting previously unselected package libicu44. Unpacking libicu44 (from .../libicu44_4.4.2-2_amd64.deb) ... Selecting previously unselected package libv8-3.4.14.21. Unpacking libv8-3.4.14.21 (from .../libv8-3.4.14.21_3.4.14.21-3_amd64.deb) ... Selecting previously unselected package libev4. Unpacking libev4 (from .../libev4_1%3a4.04-1_amd64.deb) ... Selecting previously unselected package libnode-mkdirp. Unpacking libnode-mkdirp (from .../libnode-mkdirp_0.0.7-1_all.deb) ... Selecting previously unselected package nodejs. Unpacking nodejs (from .../nodejs_0.4.12-1_amd64.deb) ... Selecting previously unselected package node-mkdirp. Unpacking node-mkdirp (from .../node-mkdirp_0.0.7-2_all.deb) ... dpkg: error processing /var/cache/apt/archives/node-mkdirp_0.0.7-2_all.deb (--unpack): trying to overwrite '/usr/lib/nodejs/mkdirp.js', which is also in package libnode-mkdirp 0.0.7-1 configured to not write apport reports Processing triggers for man-db ... Errors were encountered while processing: /var/cache/apt/archives/node-mkdirp_0.0.7-2_all.deb E: Sub-process /usr/bin/dpkg returned an error code (1) This is a serious bug as it makes installation fail, and violates sections 7.6.1 and 10.1 of the policy. An optimal solution would consist in only one of the packages installing that file, and renaming or removing the file in the other package. Depending on the circumstances you might also consider Replace relations or file diversions. If the conflicting situation cannot be resolved then, as a last resort, the two packages have to declare a mutual Conflict. Please take into account that Replaces, Conflicts and diversions should only be used when packages provide different implementations for the same functionality. Here is a list of files that are known to be shared by both packages (according to the Contents file for sid/amd64, which may be slightly out of sync): /usr/lib/nodejs/mkdirp.js This bug is assigned to both packages. If you, the maintainers of the two packages in question, have agreed on which of the packages will resolve the problem please reassign the bug to that package. You may also register in the BTS that the other package is affected by the bug. -Ralf. PS: for more information about the detection of file overwrite errors of this kind see http://edos.debian.net/file-overwrites/. ---End Message--- ---BeginMessage--- Hello Ralf, On Mon, 17 Oct 2011 12:54:11 +0200, Ralf Treinen wrote: Package: libnode-backbone-dirty,node-backbone-dirty Version: libnode-backbone-dirty/1.1.2-1 Version: node-backbone-dirty/1.1.2-2 Severity: serious User: trei...@debian.org Usertags: edos-file-overwrite [..] (and much more similar bugs) libnode-* were renamed node-* while they were in NEW. They were built fromthe same source, and as you may notice, node-* have a revision of -2, while libnode-* had -1. There must've been some problem when they got ACCEPTed, but libnode-* packages aren't currently built from any source, so they should be removed by the auto-cruft-removal script. As you can see, their removals is already scheduled: http://ftp-master.debian.org/cruft-report-daily.txt I'm closing these bugs. David -- . ''`. Debian developer |
Bug#645610: marked as done (node-qs and libnode-qs: error when trying to install together)
Your message dated Mon, 17 Oct 2011 13:53:52 +0200 with message-id 20111017135352.687f2983@local and subject line Re: [Pkg-javascript-devel] Bug#645601: node-backbone-dirty and libnode-backbone-dirty: error when trying to install together has caused the Debian Bug report #645610, regarding node-qs and libnode-qs: error when trying to install together to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 645610: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=645610 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: libnode-qs,node-qs Version: libnode-qs/0.3.1-1 Version: node-qs/0.3.1-2 Severity: serious User: trei...@debian.org Usertags: edos-file-overwrite Date: 2011-10-17 Architecture: amd64 Distribution: sid Hi, automatic installation tests of packages that share a file and at the same time do not conflict by their package dependency relationships has detected the following problem: WARNING: The following packages cannot be authenticated! libc-ares2 libicu44 libv8-3.4.14.21 libev4 libnode-qs nodejs node-qs Authentication warning overridden. Can not write log, openpty() failed (/dev/pts not mounted?) Selecting previously unselected package libc-ares2. (Reading database ... 10586 files and directories currently installed.) Unpacking libc-ares2 (from .../libc-ares2_1.7.5-1_amd64.deb) ... Selecting previously unselected package libicu44. Unpacking libicu44 (from .../libicu44_4.4.2-2_amd64.deb) ... Selecting previously unselected package libv8-3.4.14.21. Unpacking libv8-3.4.14.21 (from .../libv8-3.4.14.21_3.4.14.21-3_amd64.deb) ... Selecting previously unselected package libev4. Unpacking libev4 (from .../libev4_1%3a4.04-1_amd64.deb) ... Selecting previously unselected package libnode-qs. Unpacking libnode-qs (from .../libnode-qs_0.3.1-1_all.deb) ... Selecting previously unselected package nodejs. Unpacking nodejs (from .../nodejs_0.4.12-1_amd64.deb) ... Selecting previously unselected package node-qs. Unpacking node-qs (from .../node-qs_0.3.1-2_all.deb) ... dpkg: error processing /var/cache/apt/archives/node-qs_0.3.1-2_all.deb (--unpack): trying to overwrite '/usr/lib/nodejs/qs.js', which is also in package libnode-qs 0.3.1-1 configured to not write apport reports Processing triggers for man-db ... Errors were encountered while processing: /var/cache/apt/archives/node-qs_0.3.1-2_all.deb E: Sub-process /usr/bin/dpkg returned an error code (1) This is a serious bug as it makes installation fail, and violates sections 7.6.1 and 10.1 of the policy. An optimal solution would consist in only one of the packages installing that file, and renaming or removing the file in the other package. Depending on the circumstances you might also consider Replace relations or file diversions. If the conflicting situation cannot be resolved then, as a last resort, the two packages have to declare a mutual Conflict. Please take into account that Replaces, Conflicts and diversions should only be used when packages provide different implementations for the same functionality. Here is a list of files that are known to be shared by both packages (according to the Contents file for sid/amd64, which may be slightly out of sync): /usr/lib/nodejs/qs.js This bug is assigned to both packages. If you, the maintainers of the two packages in question, have agreed on which of the packages will resolve the problem please reassign the bug to that package. You may also register in the BTS that the other package is affected by the bug. -Ralf. PS: for more information about the detection of file overwrite errors of this kind see http://edos.debian.net/file-overwrites/. ---End Message--- ---BeginMessage--- Hello Ralf, On Mon, 17 Oct 2011 12:54:11 +0200, Ralf Treinen wrote: Package: libnode-backbone-dirty,node-backbone-dirty Version: libnode-backbone-dirty/1.1.2-1 Version: node-backbone-dirty/1.1.2-2 Severity: serious User: trei...@debian.org Usertags: edos-file-overwrite [..] (and much more similar bugs) libnode-* were renamed node-* while they were in NEW. They were built fromthe same source, and as you may notice, node-* have a revision of -2, while libnode-* had -1. There must've been some problem when they got ACCEPTed, but libnode-* packages aren't currently built from any source, so they should be removed by the auto-cruft-removal script. As you can see, their removals is already scheduled: http://ftp-master.debian.org/cruft-report-daily.txt I'm closing these bugs. David -- . ''`. Debian developer | http://wiki.debian.org/DavidPaleino : :' : Linuxer #334216 --|--
Bug#645611: marked as done (node-sphericalmercator and libnode-sphericalmercator: error when trying to install together)
Your message dated Mon, 17 Oct 2011 13:53:52 +0200 with message-id 20111017135352.687f2983@local and subject line Re: [Pkg-javascript-devel] Bug#645601: node-backbone-dirty and libnode-backbone-dirty: error when trying to install together has caused the Debian Bug report #645611, regarding node-sphericalmercator and libnode-sphericalmercator: error when trying to install together to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 645611: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=645611 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: libnode-sphericalmercator,node-sphericalmercator Version: libnode-sphericalmercator/1.0.1-1 Version: node-sphericalmercator/1.0.1-2 Severity: serious User: trei...@debian.org Usertags: edos-file-overwrite Date: 2011-10-17 Architecture: amd64 Distribution: sid Hi, automatic installation tests of packages that share a file and at the same time do not conflict by their package dependency relationships has detected the following problem: WARNING: The following packages cannot be authenticated! libc-ares2 libicu44 libv8-3.4.14.21 libev4 libnode-sphericalmercator nodejs node-sphericalmercator Authentication warning overridden. Can not write log, openpty() failed (/dev/pts not mounted?) Selecting previously unselected package libc-ares2. (Reading database ... 10586 files and directories currently installed.) Unpacking libc-ares2 (from .../libc-ares2_1.7.5-1_amd64.deb) ... Selecting previously unselected package libicu44. Unpacking libicu44 (from .../libicu44_4.4.2-2_amd64.deb) ... Selecting previously unselected package libv8-3.4.14.21. Unpacking libv8-3.4.14.21 (from .../libv8-3.4.14.21_3.4.14.21-3_amd64.deb) ... Selecting previously unselected package libev4. Unpacking libev4 (from .../libev4_1%3a4.04-1_amd64.deb) ... Selecting previously unselected package libnode-sphericalmercator. Unpacking libnode-sphericalmercator (from .../libnode-sphericalmercator_1.0.1-1_all.deb) ... Selecting previously unselected package nodejs. Unpacking nodejs (from .../nodejs_0.4.12-1_amd64.deb) ... Selecting previously unselected package node-sphericalmercator. Unpacking node-sphericalmercator (from .../node-sphericalmercator_1.0.1-2_all.deb) ... dpkg: error processing /var/cache/apt/archives/node-sphericalmercator_1.0.1-2_all.deb (--unpack): trying to overwrite '/usr/lib/nodejs/sphericalmercator.js', which is also in package libnode-sphericalmercator 1.0.1-1 configured to not write apport reports Processing triggers for man-db ... Errors were encountered while processing: /var/cache/apt/archives/node-sphericalmercator_1.0.1-2_all.deb E: Sub-process /usr/bin/dpkg returned an error code (1) This is a serious bug as it makes installation fail, and violates sections 7.6.1 and 10.1 of the policy. An optimal solution would consist in only one of the packages installing that file, and renaming or removing the file in the other package. Depending on the circumstances you might also consider Replace relations or file diversions. If the conflicting situation cannot be resolved then, as a last resort, the two packages have to declare a mutual Conflict. Please take into account that Replaces, Conflicts and diversions should only be used when packages provide different implementations for the same functionality. Here is a list of files that are known to be shared by both packages (according to the Contents file for sid/amd64, which may be slightly out of sync): /usr/lib/nodejs/sphericalmercator.js This bug is assigned to both packages. If you, the maintainers of the two packages in question, have agreed on which of the packages will resolve the problem please reassign the bug to that package. You may also register in the BTS that the other package is affected by the bug. -Ralf. PS: for more information about the detection of file overwrite errors of this kind see http://edos.debian.net/file-overwrites/. ---End Message--- ---BeginMessage--- Hello Ralf, On Mon, 17 Oct 2011 12:54:11 +0200, Ralf Treinen wrote: Package: libnode-backbone-dirty,node-backbone-dirty Version: libnode-backbone-dirty/1.1.2-1 Version: node-backbone-dirty/1.1.2-2 Severity: serious User: trei...@debian.org Usertags: edos-file-overwrite [..] (and much more similar bugs) libnode-* were renamed node-* while they were in NEW. They were built fromthe same source, and as you may notice, node-* have a revision of -2, while libnode-* had -1. There must've been some problem when they got ACCEPTed, but libnode-* packages aren't currently built from any source, so they should be
Bug#645612: libopenscap1 and libopenscap0: error when trying to install together
On Mon, Oct 17, 2011 at 01:20:53PM +0200, Ralf Treinen wrote: Package: libopenscap0,libopenscap1 Version: libopenscap0/0.7.3-1 Version: libopenscap1/0.8.0-1 Severity: serious User: trei...@debian.org Usertags: edos-file-overwrite Date: 2011-10-17 Architecture: amd64 Distribution: sid Hi, automatic installation tests of packages that share a file and at the same time do not conflict by their package dependency relationships has detected the following problem: Arg, I forgot to add the Conflict/Replace lines for the transition. I'll upload a fixed version ASAP. In the meantime you can safely remove libopenscap0 (both versions are not meant to be installed at the same time). BR, Pierre WARNING: The following packages cannot be authenticated! libsasl2-2 libldap-2.4-2 libpcre3 libnl1 libcap2 libxml2 libxslt1.1 libopenscap0 libopenscap1 Authentication warning overridden. Can not write log, openpty() failed (/dev/pts not mounted?) Selecting previously unselected package libsasl2-2. (Reading database ... 10586 files and directories currently installed.) Unpacking libsasl2-2 (from .../libsasl2-2_2.1.25.dfsg1-2_amd64.deb) ... Selecting previously unselected package libldap-2.4-2. Unpacking libldap-2.4-2 (from .../libldap-2.4-2_2.4.25-3_amd64.deb) ... Selecting previously unselected package libpcre3. Unpacking libpcre3 (from .../libpcre3_8.12-4_amd64.deb) ... Selecting previously unselected package libnl1. Unpacking libnl1 (from .../libnl1_1.1-7_amd64.deb) ... Selecting previously unselected package libcap2. Unpacking libcap2 (from .../libcap2_1%3a2.22-1_amd64.deb) ... Selecting previously unselected package libxml2. Unpacking libxml2 (from .../libxml2_2.7.8.dfsg-5_amd64.deb) ... Selecting previously unselected package libxslt1.1. Unpacking libxslt1.1 (from .../libxslt1.1_1.1.26-8_amd64.deb) ... Selecting previously unselected package libopenscap0. Unpacking libopenscap0 (from .../libopenscap0_0.7.3-1_amd64.deb) ... Selecting previously unselected package libopenscap1. Unpacking libopenscap1 (from .../libopenscap1_0.8.0-1_amd64.deb) ... dpkg: error processing /var/cache/apt/archives/libopenscap1_0.8.0-1_amd64.deb (--unpack): trying to overwrite '/usr/bin/oscap', which is also in package libopenscap0 0.7.3-1 configured to not write apport reports dpkg-deb: error: subprocess paste was killed by signal (Broken pipe) Processing triggers for man-db ... Errors were encountered while processing: /var/cache/apt/archives/libopenscap1_0.8.0-1_amd64.deb E: Sub-process /usr/bin/dpkg returned an error code (1) This is a serious bug as it makes installation fail, and violates sections 7.6.1 and 10.1 of the policy. An optimal solution would consist in only one of the packages installing that file, and renaming or removing the file in the other package. Depending on the circumstances you might also consider Replace relations or file diversions. If the conflicting situation cannot be resolved then, as a last resort, the two packages have to declare a mutual Conflict. Please take into account that Replaces, Conflicts and diversions should only be used when packages provide different implementations for the same functionality. Here is a list of files that are known to be shared by both packages (according to the Contents file for sid/amd64, which may be slightly out of sync): /usr/bin/oscap /usr/lib/openscap/probe_dnscache /usr/lib/openscap/probe_dpkginfo /usr/lib/openscap/probe_family /usr/lib/openscap/probe_file /usr/lib/openscap/probe_filehash /usr/lib/openscap/probe_inetlisteningservers /usr/lib/openscap/probe_interface /usr/lib/openscap/probe_ldap57 /usr/lib/openscap/probe_partition /usr/lib/openscap/probe_password /usr/lib/openscap/probe_process /usr/lib/openscap/probe_runlevel /usr/lib/openscap/probe_shadow /usr/lib/openscap/probe_sysctl /usr/lib/openscap/probe_system_info /usr/lib/openscap/probe_textfilecontent /usr/lib/openscap/probe_textfilecontent54 /usr/lib/openscap/probe_uname /usr/lib/openscap/probe_xinetd /usr/lib/openscap/probe_xmlfilecontent /usr/share/man/man8/oscap.8.gz /usr/share/openscap/scap-fedora14-oval.xml /usr/share/openscap/scap-fedora14-xccdf.xml /usr/share/openscap/scap-rhel6-oval.xml /usr/share/openscap/scap-rhel6-xccdf.xml /usr/share/openscap/schemas/oval/5.8/aix-definitions-schema.xsd /usr/share/openscap/schemas/oval/5.8/aix-system-characteristics-schema.xsd /usr/share/openscap/schemas/oval/5.8/apache-definitions-schema.xsd /usr/share/openscap/schemas/oval/5.8/apache-system-characteristics-schema.xsd /usr/share/openscap/schemas/oval/5.8/catos-definitions-schema.xsd /usr/share/openscap/schemas/oval/5.8/catos-system-characteristics-schema.xsd /usr/share/openscap/schemas/oval/5.8/debian-definitions-schema.xsd /usr/share/openscap/schemas/oval/5.8/debian-system-characteristics-schema.xsd
Bug#645612: libopenscap1 and libopenscap0: error when trying to install together
On Mon, Oct 17, 2011 at 14:13:03 +0200, Pierre Chifflier wrote: On Mon, Oct 17, 2011 at 01:20:53PM +0200, Ralf Treinen wrote: Package: libopenscap0,libopenscap1 Version: libopenscap0/0.7.3-1 Version: libopenscap1/0.8.0-1 Severity: serious User: trei...@debian.org Usertags: edos-file-overwrite Date: 2011-10-17 Architecture: amd64 Distribution: sid Hi, automatic installation tests of packages that share a file and at the same time do not conflict by their package dependency relationships has detected the following problem: Arg, I forgot to add the Conflict/Replace lines for the transition. I'll upload a fixed version ASAP. In the meantime you can safely remove libopenscap0 (both versions are not meant to be installed at the same time). Note that that'd still be buggy. Shared library packages must not contain non-versioned files, see policy 8.2. Please fix this properly instead. Cheers, Julien -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed: your mail
Processing commands for cont...@bugs.debian.org:
reopen 645327
Bug #645327 {Done: OndÅej Surý ond...@sury.org} [cyrus-imapd-2.2]
CVE-2011-3481: Denial of service
'reopen' may be inappropriate when a bug has been closed with a version;
you may need to use 'found' to remove fixed versions.
thank you
Stopping processing here.
Please contact me if you need assistance.
--
645327: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=645327
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#644782: directfb: diff for NMU version 1.2.10.0-4.3
tags 644782 + patch tags 644782 + pending thanks Dear maintainer, I've prepared an NMU for directfb (versioned as 1.2.10.0-4.3) and uploaded it to DELAYED/7. Please feel free to tell me if I should delay it longer. Please consider to apply this fix to experimental package too. I have opened a ticket upstream regarding this bug: http://directfb.org/mantis/view.php?id=16 Regards. -- Héctor Orón Our Sun unleashes tremendous flares expelling hot gas into the Solar System, which one day will disconnect us. -- Day DVB-T stop working nicely Video flare: http://antwrp.gsfc.nasa.gov/apod/ap100510.html diff -Nru directfb-1.2.10.0/debian/changelog directfb-1.2.10.0/debian/changelog --- directfb-1.2.10.0/debian/changelog 2011-08-10 00:10:13.0 +0100 +++ directfb-1.2.10.0/debian/changelog 2011-10-17 12:53:36.0 +0100 @@ -1,3 +1,12 @@ +directfb (1.2.10.0-4.3) unstable; urgency=low + + * Non-maintainer upload. + * Fix directfb ftbfs on armel. Implicit declaration error +- Thanks Peter Green for bug report and patch (Closes: #644782) + * Remove m4 macros when calling clean target + + -- Hector Oron zu...@debian.org Mon, 17 Oct 2011 12:53:01 +0100 + directfb (1.2.10.0-4.2) unstable; urgency=low * Non-maintainer upload. diff -Nru directfb-1.2.10.0/debian/patches/94_fix_mknod.patch directfb-1.2.10.0/debian/patches/94_fix_mknod.patch --- directfb-1.2.10.0/debian/patches/94_fix_mknod.patch 1970-01-01 01:00:00.0 +0100 +++ directfb-1.2.10.0/debian/patches/94_fix_mknod.patch 2011-10-17 13:03:43.0 +0100 @@ -0,0 +1,39 @@ +Description: directfb ftbfs on armel. Implicit declaration error + Fix for ARM builds failing on: + ../../../gfxdrivers/davinci/davinci_c64x.c: In function 'davinci_c64x_open': + ../../../gfxdrivers/davinci/davinci_c64x.c:1900:6: error: implicit declaration of function 'mknod' [-Werror=implicit-function-declaration] + cc1: some warnings being treated as errors + . + directfb (1.2.10.0-4.3) unstable; urgency=low + . + * Non-maintainer upload. + * Fix directfb ftbfs on armel. Implicit declaration error + - Thanks Peter Green for bug report and patch (Closes: #644782) + * Remove m4 macros when calling clean target +Author: Hector Oron zu...@debian.org +Bug-Debian: http://bugs.debian.org/644782 + +--- +The information above should follow the Patch Tagging Guidelines, please +checkout http://dep.debian.net/deps/dep3/ to learn about the format. Here +are templates for supplementary fields that you might want to add: + +Origin: vendor|upstream|other, url of original patch +Bug: url in upstream bugtracker +Bug-Debian: http://bugs.debian.org/644782 +Bug-Ubuntu: https://launchpad.net/bugs/bugnumber +Forwarded: http://directfb.org/mantis/view.php?id=16 +Reviewed-By: name and email of someone who approved the patch +Last-Update: -MM-DD + +--- directfb-1.2.10.0.orig/gfxdrivers/davinci/davinci_c64x.c directfb-1.2.10.0/gfxdrivers/davinci/davinci_c64x.c +@@ -37,6 +37,8 @@ + #include sys/ioctl.h + #include sys/mman.h + #include sys/types.h ++#include sys/stat.h ++ + #include unistd.h + + #include directfb_util.h diff -Nru directfb-1.2.10.0/debian/patches/series directfb-1.2.10.0/debian/patches/series --- directfb-1.2.10.0/debian/patches/series 2009-10-20 09:00:11.0 +0100 +++ directfb-1.2.10.0/debian/patches/series 2011-10-17 12:54:46.0 +0100 @@ -4,3 +4,4 @@ 70_linux_fusion.patch 90_linux_config.h.patch 93_fix_unicode_key_handling.patch +94_fix_mknod.patch diff -Nru directfb-1.2.10.0/debian/rules directfb-1.2.10.0/debian/rules --- directfb-1.2.10.0/debian/rules 2011-07-24 18:20:04.0 +0100 +++ directfb-1.2.10.0/debian/rules 2011-10-17 12:52:22.0 +0100 @@ -103,7 +103,12 @@ missing mkinstalldirs depcomp install-sh compile rm -rf $(DESTDIR_UDEB) - + + rm -f m4/libtool.m4 + rm -f m4/ltoptions.m4 + rm -f m4/ltsugar.m4 + rm -f m4/ltversion.m4 + rm -f m4/lt~obsolete.m4 dh_clean override_dh_auto_install: signature.asc Description: Digital signature
Processed: directfb: diff for NMU version 1.2.10.0-4.3
Processing commands for cont...@bugs.debian.org: tags 644782 + patch Bug #644782 [directfb] directfb ftbfs on armel. Implicit declaration error Added tag(s) patch. tags 644782 + pending Bug #644782 [directfb] directfb ftbfs on armel. Implicit declaration error Added tag(s) pending. thanks Stopping processing here. Please contact me if you need assistance. -- 644782: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=644782 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#645309: marked as done (debpartial-mirror: cannot handle duplicate entries in Packages)
Your message dated Mon, 17 Oct 2011 12:47:08 + with message-id e1rfmay-0001lc...@franck.debian.org and subject line Bug#645309: fixed in debpartial-mirror 0.3.0 has caused the Debian Bug report #645309, regarding debpartial-mirror: cannot handle duplicate entries in Packages 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.) -- 645309: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=645309 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: debpartial-mirror Version: 0.2.99 Severity: grave (Normally important, but bumped to RC because it's breaking for security updates on squeeze and that needs to not happen) If a Packages file contains two entries for the same package name, debpartial-mirror will die with this exception: Traceback (most recent call last): File /usr/bin/debpartial-mirror, line 177, in module main() File /usr/bin/debpartial-mirror, line 169, in main controller.executeCommand(cmnd) File /usr/lib/pymodules/python2.6/debpartial_mirror/Controller.py, line 34, in executeCommand self._commands.get(commandName)() File /usr/lib/pymodules/python2.6/debpartial_mirror/Controller.py, line 38, in doAll if self._load(): File /usr/lib/pymodules/python2.6/debpartial_mirror/Controller.py, line 72, in _load if not b.load(): File /usr/lib/pymodules/python2.6/debpartial_mirror/Backend.py, line 111, in load return self._dists.load() File /usr/lib/pymodules/python2.6/debpartial_mirror/Dists.py, line 186, in load processTagFile(index_filename, addPackage) File /usr/lib/pymodules/python2.6/debpartial_mirror/Dists.py, line 487, in processTagFile sectionHandler(section) File /usr/lib/pymodules/python2.6/debpartial_mirror/Dists.py, line 182, in addPackage pkglist.add(package) File /usr/lib/pymodules/python2.6/cdd/PackageList.py, line 167, in add raise PackageAlreadyExists, package['Package'] cdd.PackageList.PackageAlreadyExists Trivial patch follows which only mirrors the most recent version (which is probably what you wanted, and anyway much better than failing). diff -b -x debian -x DEBIAN -x build -ruN debpartial-mirror-0.2.99//debpartial_mirror/Dists.py /home/asuffield/src/debpartial-mirror-0.2.99//debpartial_mirror/Dists.py --- debpartial-mirror-0.2.99//debpartial_mirror/Dists.py2010-10-22 21:58:37.0 +0100 +++ /home/asuffield/src/debpartial-mirror-0.2.99//debpartial_mirror/Dists.py 2011-10-14 10:37:56.207266435 +0100 @@ -179,6 +179,14 @@ def addPackage(section): package = pkg(section) package.releaseInfo = releaseInfo +name = package['Package'] +if name in pkglist: +oldver = pkglist[name]['Version'] +newver = package['Version'] +if apt_pkg.version_compare(oldver, newver) 1: +pkglist.remove(name) +pkglist.add(package) +else: pkglist.add(package) index_filename = os.path.join(self._filesystem.base(), file) Right now, security.debian.org has duplicates on amd64 for these packages: Package: openjdk-6-doc Package: openjdk-6-jre-lib Package: openjdk-6-source Thijs Kinkhorst observed that this is because openjdk is hard to build on all architectures and they still don't have the latest update on powerpc and sparc, and suggested that this is just something that will happen from time to time. Also it's probably going to happen all the time for sid. I'm surprised this wasn't noticed and fixed before now. ---End Message--- ---BeginMessage--- Source: debpartial-mirror Source-Version: 0.3.0 We believe that the bug you reported is fixed in the latest version of debpartial-mirror, which is due to be installed in the Debian FTP archive: debpartial-mirror_0.3.0.dsc to main/d/debpartial-mirror/debpartial-mirror_0.3.0.dsc debpartial-mirror_0.3.0.tar.gz to main/d/debpartial-mirror/debpartial-mirror_0.3.0.tar.gz debpartial-mirror_0.3.0_all.deb to main/d/debpartial-mirror/debpartial-mirror_0.3.0_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 645...@bugs.debian.org, and the maintainer will reopen the bug report if
Bug#645546: clang: FTBFS(kfreebsd): error: Operating system is unknown, configure can't continue
Le dimanche 16 octobre 2011 à 23:26 +0200, Christoph Egger a écrit : cd build-clang \ ../llvm-2.9/configure CC=x86_64-kfreebsd-gnu-gcc CXX=x86_64-kfreebsd-gnu-g++ CPP=x86_64-kfreebsd-gnu-cpp --with-c-include-dirs=/usr/include/x86_64-kfreebsd-gnu:/usr/include --with-cxx-include-root=/usr/include/c++/4.6 --with-cxx-include-arch=x86_64-kfreebsd-gnu --host=x86_64-kfreebsd-gnu --build=x86_64-kfreebsd-gnu --with-cxx-include-32bit-dir=32 --prefix=/usr --disable-assertions --enable-shared --enable-optimized --with-optimize-option=' -g -O2' --enable-pic --enable-libffi CLANG_VENDOR=Debian checking build system type... x86_64-pc-kfreebsd-gnu checking host system type... x86_64-pc-kfreebsd-gnu checking target system type... x86_64-pc-kfreebsd-gnu checking type of operating system we're going to host on... Unknown checking type of operating system we're going to target... Unknown configure: error: Operating system is unknown, configure can't continue make: *** [/build/buildd-clang_2.9-16-kfreebsd-amd64-JQnCYR/clang-2.9/debian/stamps/configure-stamp-clang] Error 1 I wonder if it is not caused by an update of a dependency. Could it be possible to have access to the config.log file ? thanks S -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#645630: must not use bzip2 for libtextwrap1-udeb
Package: libtextwrap Version: 0.1-12 Severity: serious libtextwrap1-udeb is compressed with bzip2, which is illegal for all udebs. This one is in the initrd, so nothing explodes in real use, but that doesn't make it legal. -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#643350: marked as done (alsamixergui: FTBFS: Fl_AM.cxx:154:20: error: format not a string literal and no format arguments [-Werror=format-security])
Your message dated Mon, 17 Oct 2011 13:47:08 + with message-id e1rfnx2-0006z8...@franck.debian.org and subject line Bug#643350: fixed in alsamixergui 0.9.0rc2-1-9.1 has caused the Debian Bug report #643350, regarding alsamixergui: FTBFS: Fl_AM.cxx:154:20: error: format not a string literal and no format arguments [-Werror=format-security] 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.) -- 643350: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=643350 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Source: alsamixergui Version: 0.9.0rc2-1-9 Severity: serious Tags: wheezy sid User: debian...@lists.debian.org Usertags: qa-ftbfs-20110923 qa-ftbfs hardening-format-security hardening Justification: FTBFS on amd64 Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part: g++ -DHAVE_CONFIG_H -I. -I. -I. -g -O2 -fstack-protector --param=ssp-buffer-size=4 -D_FORTIFY_SOURCE=2 -Wformat -Wformat-security -Werror=format-security -Wall -c -o Fl_AM.o `test -f 'Fl_AM.cxx' || echo './'`Fl_AM.cxx In file included from Fl_AM.cxx:11:0: images/rec0.xpm:18:15: warning: deprecated conversion from string constant to 'char*' [-Wwrite-strings] images/rec0.xpm:18:15: warning: deprecated conversion from string constant to 'char*' [-Wwrite-strings] images/rec0.xpm:18:15: warning: deprecated conversion from string constant to 'char*' [-Wwrite-strings] images/rec0.xpm:18:15: warning: deprecated conversion from string constant to 'char*' [-Wwrite-strings] images/rec0.xpm:18:15: warning: deprecated conversion from string constant to 'char*' [-Wwrite-strings] images/rec0.xpm:18:15: warning: deprecated conversion from string constant to 'char*' [-Wwrite-strings] images/rec0.xpm:18:15: warning: deprecated conversion from string constant to 'char*' [-Wwrite-strings] images/rec0.xpm:18:15: warning: deprecated conversion from string constant to 'char*' [-Wwrite-strings] images/rec0.xpm:18:15: warning: deprecated conversion from string constant to 'char*' [-Wwrite-strings] images/rec0.xpm:18:15: warning: deprecated conversion from string constant to 'char*' [-Wwrite-strings] images/rec0.xpm:18:15: warning: deprecated conversion from string constant to 'char*' [-Wwrite-strings] images/rec0.xpm:18:15: warning: deprecated conversion from string constant to 'char*' [-Wwrite-strings] images/rec0.xpm:18:15: warning: deprecated conversion from string constant to 'char*' [-Wwrite-strings] images/rec0.xpm:18:15: warning: deprecated conversion from string constant to 'char*' [-Wwrite-strings] images/rec0.xpm:18:15: warning: deprecated conversion from string constant to 'char*' [-Wwrite-strings] images/rec0.xpm:18:15: warning: deprecated conversion from string constant to 'char*' [-Wwrite-strings] In file included from Fl_AM.cxx:12:0: images/rec1.xpm:18:15: warning: deprecated conversion from string constant to 'char*' [-Wwrite-strings] images/rec1.xpm:18:15: warning: deprecated conversion from string constant to 'char*' [-Wwrite-strings] images/rec1.xpm:18:15: warning: deprecated conversion from string constant to 'char*' [-Wwrite-strings] images/rec1.xpm:18:15: warning: deprecated conversion from string constant to 'char*' [-Wwrite-strings] images/rec1.xpm:18:15: warning: deprecated conversion from string constant to 'char*' [-Wwrite-strings] images/rec1.xpm:18:15: warning: deprecated conversion from string constant to 'char*' [-Wwrite-strings] images/rec1.xpm:18:15: warning: deprecated conversion from string constant to 'char*' [-Wwrite-strings] images/rec1.xpm:18:15: warning: deprecated conversion from string constant to 'char*' [-Wwrite-strings] images/rec1.xpm:18:15: warning: deprecated conversion from string constant to 'char*' [-Wwrite-strings] images/rec1.xpm:18:15: warning: deprecated conversion from string constant to 'char*' [-Wwrite-strings] images/rec1.xpm:18:15: warning: deprecated conversion from string constant to 'char*' [-Wwrite-strings] images/rec1.xpm:18:15: warning: deprecated conversion from string constant to 'char*' [-Wwrite-strings] images/rec1.xpm:18:15: warning: deprecated conversion from string constant to 'char*' [-Wwrite-strings] images/rec1.xpm:18:15: warning: deprecated conversion from string constant to 'char*' [-Wwrite-strings] images/rec1.xpm:18:15: warning: deprecated conversion from string constant to 'char*' [-Wwrite-strings] images/rec1.xpm:18:15: warning: deprecated conversion from string constant to 'char*' [-Wwrite-strings] In file included
Bug#645635: yaskkserv: FTBFS on armel, ia64, etc.
Package: yaskkserv Version: 0.5.0-2 Severity: serious The buildd log seems FTBFS is caused on several arch: https://buildd.debian.org/status/package.php?p=yaskkserv Thanks, -- Tatsuya Kinoshita pgpo5Ik25jnN6.pgp Description: PGP signature
Bug#645637: roundcube-plugins-extra: contains a convenience code copy of PEAR Net_Sieve
Package: roundcube-plugins-extra Version: 0.5.3-20110619 Severity: serious Justification: Policy 4.13 roundcube-plugins-extra ships and uses a convenience code copy of PEAR Net_Sieve module in the sieverules plugin. This module is available in Debian in the php-net-sieve package. The later will need to be updated before it can be used as a replacement (1.1.7 currently in Debian vs. 1.3.2 in sieverules plugin). -- Jérémy Bobbio.''`. lu...@debian.org: :Ⓐ : # apt-get install anarchism `. `'` `- signature.asc Description: Digital signature
Bug#643431: marked as done (libnet: FTBFS: libnet_init.c:88:17: error: format not a string literal and no format arguments [-Werror=format-security])
Your message dated Mon, 17 Oct 2011 15:03:56 + with message-id e1rfojm-0004zh...@franck.debian.org and subject line Bug#643431: fixed in libnet 1.1.4-2.1 has caused the Debian Bug report #643431, regarding libnet: FTBFS: libnet_init.c:88:17: error: format not a string literal and no format arguments [-Werror=format-security] 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.) -- 643431: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=643431 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Source: libnet Version: 1.1.4-2 Severity: serious Tags: wheezy sid User: debian...@lists.debian.org Usertags: qa-ftbfs-20110923 qa-ftbfs hardening-format-security hardening Justification: FTBFS on amd64 Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part: gcc -DHAVE_CONFIG_H -I. -I../include -g -O2 -fstack-protector --param=ssp-buffer-size=4 -D_FORTIFY_SOURCE=2 -Wformat -Wformat-security -Werror=format-security -Wall -c libnet_init.c -fPIC -DPIC -o .libs/libnet_init.o libnet_init.c: In function 'libnet_init': libnet_init.c:88:17: error: format not a string literal and no format arguments [-Werror=format-security] libnet_init.c:88:17: error: format not a string literal and no format arguments [-Werror=format-security] libnet_init.c:93:17: error: format not a string literal and no format arguments [-Werror=format-security] libnet_init.c:93:17: error: format not a string literal and no format arguments [-Werror=format-security] libnet_init.c:101:17: error: format not a string literal and no format arguments [-Werror=format-security] libnet_init.c:101:17: error: format not a string literal and no format arguments [-Werror=format-security] libnet_init.c:109:17: error: format not a string literal and no format arguments [-Werror=format-security] libnet_init.c:109:17: error: format not a string literal and no format arguments [-Werror=format-security] cc1: some warnings being treated as errors make[2]: *** [libnet_init.lo] Error 1 The full build log is available from: http://people.debian.org/~lucas/logs/2011/09/23/libnet_1.1.4-2_lsid64.buildlog This happened because since dpkg 1.16.0 [0], hardening flags are enabled under various conditions. [0] http://lists.debian.org/debian-devel-announce/2011/09/msg1.html 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: libnet Source-Version: 1.1.4-2.1 We believe that the bug you reported is fixed in the latest version of libnet, which is due to be installed in the Debian FTP archive: libnet1-dbg_1.1.4-2.1_i386.deb to main/libn/libnet/libnet1-dbg_1.1.4-2.1_i386.deb libnet1-dev_1.1.4-2.1_i386.deb to main/libn/libnet/libnet1-dev_1.1.4-2.1_i386.deb libnet1-doc_1.1.4-2.1_all.deb to main/libn/libnet/libnet1-doc_1.1.4-2.1_all.deb libnet1_1.1.4-2.1_i386.deb to main/libn/libnet/libnet1_1.1.4-2.1_i386.deb libnet_1.1.4-2.1.diff.gz to main/libn/libnet/libnet_1.1.4-2.1.diff.gz libnet_1.1.4-2.1.dsc to main/libn/libnet/libnet_1.1.4-2.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 643...@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 libnet package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Sat, 15 Oct 2011 16:30:40 +0200 Source: libnet Binary: libnet1 libnet1-dbg libnet1-dev libnet1-doc Architecture: source all i386 Version: 1.1.4-2.1 Distribution: unstable Urgency: low Maintainer: Stefanos Harhalakis v...@v13.gr Changed-By: gregor herrmann gre...@debian.org Description: libnet1- library for the construction and handling of network packets libnet1-dbg - debugging symbols for libnet libnet1-dev - development files for libnet libnet1-doc - developers documentation files for libnet Closes: 643431 Changes: libnet (1.1.4-2.1) unstable; urgency=low . *
Bug#643356: marked as done (babl: FTBFS: babl-model.c:49:7: error: format not a string literal and no format arguments [-Werror=format-security])
Your message dated Mon, 17 Oct 2011 15:03:00 + with message-id e1rfois-0004ns...@franck.debian.org and subject line Bug#643356: fixed in babl 0.0.22-1.1 has caused the Debian Bug report #643356, regarding babl: FTBFS: babl-model.c:49:7: error: format not a string literal and no format arguments [-Werror=format-security] 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.) -- 643356: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=643356 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Source: babl Version: 0.0.22-1 Severity: serious Tags: wheezy sid User: debian...@lists.debian.org Usertags: qa-ftbfs-20110923 qa-ftbfs hardening-format-security hardening Justification: FTBFS on amd64 Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part: gcc -DHAVE_CONFIG_H -I. -I. -I.. -I.. -I../babl/base -DLIBDIR=\/usr/lib\ -g -O2 -fstack-protector --param=ssp-buffer-size=4 -D_FORTIFY_SOURCE=2 -Wformat -Wformat-security -Werror=format-security -Wall -Wall -Wdeclaration-after-statement -Wmissing-prototypes -Wmissing-declarations -Winit-self -Wpointer-arith -Wold-style-definition -c babl-model.c -fPIC -DPIC -o .libs/babl-model.o babl-model.c: In function 'create_name': babl-model.c:49:7: error: format not a string literal and no format arguments [-Werror=format-security] cc1: some warnings being treated as errors make[4]: *** [babl-model.lo] Error 1 The full build log is available from: http://people.debian.org/~lucas/logs/2011/09/23/babl_0.0.22-1_lsid64.buildlog This happened because since dpkg 1.16.0 [0], hardening flags are enabled under various conditions. [0] http://lists.debian.org/debian-devel-announce/2011/09/msg1.html 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: babl Source-Version: 0.0.22-1.1 We believe that the bug you reported is fixed in the latest version of babl, which is due to be installed in the Debian FTP archive: babl_0.0.22-1.1.diff.gz to main/b/babl/babl_0.0.22-1.1.diff.gz babl_0.0.22-1.1.dsc to main/b/babl/babl_0.0.22-1.1.dsc libbabl-0.0-0-dev_0.0.22-1.1_i386.deb to main/b/babl/libbabl-0.0-0-dev_0.0.22-1.1_i386.deb libbabl-0.0-0_0.0.22-1.1_i386.deb to main/b/babl/libbabl-0.0-0_0.0.22-1.1_i386.deb libbabl-0.0-doc_0.0.22-1.1_all.deb to main/b/babl/libbabl-0.0-doc_0.0.22-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 643...@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 babl package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Sat, 15 Oct 2011 15:39:05 +0200 Source: babl Binary: libbabl-0.0-0 libbabl-0.0-0-dev libbabl-0.0-doc Architecture: source all i386 Version: 0.0.22-1.1 Distribution: unstable Urgency: low Maintainer: Ross Burton r...@debian.org Changed-By: gregor herrmann gre...@debian.org Description: libbabl-0.0-0 - Dynamic, any to any, pixel format conversion library libbabl-0.0-0-dev - Dynamic, any to any, pixel format conversion library (development libbabl-0.0-doc - Dynamic, any to any, pixel format conversion library (documentati Closes: 643356 Changes: babl (0.0.22-1.1) unstable; urgency=low . * Non-maintainer upload. * Fix FTBFS: babl-model.c:49:7: error: format not a string literal and no format arguments [-Werror=format-security]: add patch from Bart Martens (closes: #643356). Checksums-Sha1: 42b5f14880b6939ce49a9079cc3d63ec69a9c8dd 1762 babl_0.0.22-1.1.dsc 97eaf3703723caaa38d91c7f50216f2f007094cb 1980 babl_0.0.22-1.1.diff.gz 3e9861915e81f0124bc469c53f1056709516589f 123324 libbabl-0.0-doc_0.0.22-1.1_all.deb a926a727b15e4a5c156fcb62702b7b165b224d7b 101150 libbabl-0.0-0_0.0.22-1.1_i386.deb 0c4f24bd336a4f2031c35b3a131f30fd0eca29ae 37976 libbabl-0.0-0-dev_0.0.22-1.1_i386.deb Checksums-Sha256:
Processed: block
Processing commands for cont...@bugs.debian.org: block 645637 with 645529 Bug #645637 [roundcube-plugins-extra] roundcube-plugins-extra: contains a convenience code copy of PEAR Net_Sieve Was not blocked by any bugs. Added blocking bug(s) of 645637: 645529 thanks Stopping processing here. Please contact me if you need assistance. -- 645637: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=645637 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: libgail-gnome-module: needs porting to new libpanel-applet interface
Processing commands for cont...@bugs.debian.org: reassign 638112 ftp.debian.org Bug #638112 [libgail-gnome-module] libgail-gnome-module: needs porting to new libpanel-applet interface Bug reassigned from package 'libgail-gnome-module' to 'ftp.debian.org'. Bug No longer marked as found in versions libgail-gnome/1.20.3-1. retitle 638112 RM: libgail-module -- ROM; dead upstream, uninstallable Bug #638112 [ftp.debian.org] libgail-gnome-module: needs porting to new libpanel-applet interface Changed Bug title to 'RM: libgail-module -- ROM; dead upstream, uninstallable' from 'libgail-gnome-module: needs porting to new libpanel-applet interface' thanks Stopping processing here. Please contact me if you need assistance. -- 638112: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=638112 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#638112: libgail-gnome-module: needs porting to new libpanel-applet interface
reassign 638112 ftp.debian.org retitle 638112 RM: libgail-module -- ROM; dead upstream, uninstallable thanks Hi ftp-masters, please remove libgail-module from the archive. It's part of the ongoing libpanel-applet transition and and blocking the GNOME 3 transition. It is dead upstream and we don't plan to port it ourselves. For the only two remaining rdeps, orca and accerciser, we will request their removal from testing and they will be updated to work without libgail-gnome-module as part of GNOME 3.2. Cheers, Michael -- Why is it that all of the instruments seeking intelligent life in the universe are pointed away from Earth? signature.asc Description: OpenPGP digital signature
Bug#625330: marked as done (fileschanged: ftbfs with gcc-4.6 -Werror)
Your message dated Mon, 17 Oct 2011 16:02:16 + with message-id e1rfpdo-0002sa...@franck.debian.org and subject line Bug#625330: fixed in fileschanged 0.6.5-1.2 has caused the Debian Bug report #625330, regarding fileschanged: ftbfs with gcc-4.6 -Werror 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.) -- 625330: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=625330 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: fileschanged Version: 0.6.5-1.1 Severity: important Tags: wheezy sid User: debian-...@lists.debian.org Usertags: ftbfs-gcc-4.6 ftbfs-werror This package builds with -Werror, and GCC 4.6 triggers new warnings which will make the package fail to build. Currently a Debian patch just passes -Wno-error=unused-but-set-variable and -Wno-error=unused-but-set-parameter to avoid build failures, but this patch will be reverted with the GCC 4.6.1 release, and the severity of the report will be raised. The full build log can be found at: http://people.debian.org/~doko/tmp/werror/fileschanged_0.6.5-1.1_lsid64.buildlog The last lines of the build log are at the end of this report. ---End Message--- ---BeginMessage--- Source: fileschanged Source-Version: 0.6.5-1.2 We believe that the bug you reported is fixed in the latest version of fileschanged, which is due to be installed in the Debian FTP archive: fileschanged_0.6.5-1.2.diff.gz to main/f/fileschanged/fileschanged_0.6.5-1.2.diff.gz fileschanged_0.6.5-1.2.dsc to main/f/fileschanged/fileschanged_0.6.5-1.2.dsc fileschanged_0.6.5-1.2_i386.deb to main/f/fileschanged/fileschanged_0.6.5-1.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 625...@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 fileschanged package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Sat, 15 Oct 2011 17:27:14 +0200 Source: fileschanged Binary: fileschanged Architecture: source i386 Version: 0.6.5-1.2 Distribution: unstable Urgency: low Maintainer: Juan A. Diaz j...@linux.org.ar Changed-By: gregor herrmann gre...@debian.org Description: fileschanged - command-line utility that reports when files have been altered Closes: 625330 Changes: fileschanged (0.6.5-1.2) unstable; urgency=low . * Non-maintainer upload. * Fix ftbfs with gcc-4.6 -Werror: add patch 07_unused_variables.dpatch from Ubuntu / Colin Watson: - Avoid unused variable warnings so they don't cause build failures with -Werror (closes: #625330, LP: #831209). * Stop installing /usr/share/info/dir.gz (ftp-master autoreject reason). Checksums-Sha1: 81c84f5043f139ba808c0442b784c1b899af5959 1809 fileschanged_0.6.5-1.2.dsc 95a4046af3d115cbc45fe5576816d572b82137b6 5999 fileschanged_0.6.5-1.2.diff.gz c91087394f3c542aa484227a52b4b6df9c75c587 29836 fileschanged_0.6.5-1.2_i386.deb Checksums-Sha256: 7eb0395a7394828b86ae64b09f2b4aa4084cb92d6a7060f32c3f2ed35868af17 1809 fileschanged_0.6.5-1.2.dsc 6671b940b70966a417bdb8dcbce571babd1994b733449158e9f69ae001890352 5999 fileschanged_0.6.5-1.2.diff.gz 3fc2924ebb8226ffd2426b9fc8fc443c38bbb0be25f814f02a2ad63c7a0d5104 29836 fileschanged_0.6.5-1.2_i386.deb Files: a90f1f029b370249e58d1250835da98b 1809 utils optional fileschanged_0.6.5-1.2.dsc bf1d4f6125e8a374421a9127896bc711 5999 utils optional fileschanged_0.6.5-1.2.diff.gz a6f71fcddde5e49d4e0241592c72bd20 29836 utils optional fileschanged_0.6.5-1.2_i386.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.11 (GNU/Linux) iQIcBAEBCAAGBQJOmaelAAoJELs6aAGGSaoGQCkQAJS4k4tqWhAXvQF1SgLaV3l3 OoMxvy4jjixov9PrasqFUp/0aJMtyg7G14t/k0zII9xl527W+wvXmGMLrRl0kRAZ kFwRikl/p9ayxcoOozgw9DbV7Mz2P89VorpsToeAWid9MriYCePDsnJeClax+mZx +Wy/MwWT5vol/dbwvzpPkYM/mdKM9PxpkNeEYbHVGgg9QoeVfZClsN+cu2RJzOfn iYaq/tFfJ54wsKLyAqbYSI5nQ5x3b2wU08zlTaNK5VXuLBM+AKRAqFIyUCPKiJzp t7NO1zoWvnw0UW5rfxgbcb1zhnv/j7VodRFOLvJH6CaCH4RM1pWgqoRMRZ3Scktv gl+U5kPkQqxYroXPpeX0eHlyLYgfNQSQqcJlYtFtQJWeOq0jFOEPJDDL7mV/i2oV 8Hw3AQKloTnQfzgdnWZ6tWd/uqGhmz4jfAyt+4YLWl5VtSltLgiW9vFi7L8Vf0Xe laYBUWFdK3AkyRTIiKMxVLyP3q8jRb12Hs48HFQ9bNvwL3xWuT87RImJonuuzHCY 951O2zuXaxUAgQyqy9Jv/hiONxQfCFJqkcnEzKBZlfooKARD2MQLEFK0BDvjvk7l
Bug#645469: bind fails for AF_UNIX sockets with EINVAL
2011/10/16 Petr Salinger petr.salin...@seznam.cz:
Yes, I think this should be handled in glibc, and the sockaddr_un be
fixed to match what the kernel expects, the compat code would be there
to fix applications built against the bogus sockaddr_un type.
In fact, we already clip the passed size in our eglibc in
bind() and connect(), it might suffice in eglibc to
Silent truncation sounds a bit dangerous. Could this introduce a
security problem? E.g. a malliciously placed socket which matches the
truncated path.
On the other hand we cannot change size of userland
sockaddr_un without ABI change. To do it correctly it would mean
to raise soname of eglibc and perform transition involving all packages.
Is that really so bad? I guess the impact is minimal. How many
libraries would make sockaddr_un part of their ABI?
May be the limit can be raised in upstream in kernel only,
to allow 108 instead of 104 only bytes.
Maybe. You mean something like this?
struct sockaddr_un
{
...
#ifdef _KERNEL
sun_path[108];
#else
sun_path[104];
#endif
}
It's ugly though. I wouldn't count on this being accepted, specially
not backported. If it doesn't serve us to support people running
upstream kernels, is there a point in pushing this change?
--
Robert Millan
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#645658: bpython-urwid: unsusable due to urwid 1.0.0 in unstable
Package: bpython-urwid Version: 0.10.1-2 Severity: grave Tags: patch -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 The current version of bpython-urwid doesn't work with urwid 1.0.0, which is currenty in unstable. This issue has already been fixed upstream. The fix can be found at [1] and [2]. Regards [1] https://bitbucket.org/bobf/bpython/changeset/35cec9e170e7 [1] https://bitbucket.org/bobf/bpython/changeset/9492fcfa3a82 - -- System Information: Debian Release: wheezy/sid APT prefers unstable APT policy: (650, 'unstable'), (601, 'testing'), (600, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 3.0.0-2-amd64 (SMP w/4 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages bpython-urwid depends on: ii bpython 0.10.1-2 ii python2.7.2-9 ii python-urwid 1.0.0-1 bpython-urwid recommends no packages. bpython-urwid suggests no packages. - -- no debconf information -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.11 (GNU/Linux) iQIcBAEBCAAGBQJOnFdtAAoJEGny/FFupxmTU44P/ibcuijFWD1CjjnypXbMy4gf dZ588aU48hHThzxMFDv/ZeT4Utd4wHK1QANoPQwaFWycgV6b5oUtzOp3WaY9cE9J qhZRxJE4K91TqmgL3KB8LHj2ygmV8amVJS0zHcI5w7LOUJV5UpxBUAQqh7PSyYmf 6djElBAPk0YdUoY4JvTvR1GTImbvQu80Wjk+ws4wbX0+0p4ecVMZvUN0JRlzozgV VQ1JBR3MPIzhCuZwH2y5cMovwaKnIH/glXGJJW7u3ts9QHioxsvaPjQHEDPboo8V VWRGu68Fjy7fbtvPdJiQm+199xm7eZNkdhxupppI2uKkN8yaooaJ4n1X8JenR2He /hEhtl3p+svMNcFS0M5VM/0wu2SG/yNqnWHGmwFg12n65QQ03CWGQLBvDzbpVypq +E6r/DUZ7lsp6easLbbvqrW+ktKFg0D62l3ee2CnOhV46GU0lCn7n6LKih53mey5 vnDVHpPkL1N+CMYrFfpD3ShV3PYMad4SEEtpL+rfQUEY1t7pdwlINRozRQCA/cwJ TlpHVMDKCUH44+Fy7l0e+0sm1UzRP0yiR72EWZ2AoOlkSwyByUYjh8IxwRJaUGs+ IJ/9rl3/CRNaMHvAFOvKKTdCkZ5lPabeo3ok/6fIVBGsXd4w3xmRIWlx2lv9Au5M k4Lan8NkRIj8bt8Ox2f7 =yRVO -END PGP SIGNATURE- -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#644614: [Secure-testing-team] [rt.debian.org #3440] Re: Bug#644614: multiple security issues in radvd 1.6
On ven., 2011-10-14 at 23:26 +0200, Yves-Alexis Perez wrote:
On ven., 2011-10-14 at 09:10 +0200, Yves-Alexis Perez wrote:
Here's the debdiff for Lenny. Since I got no news from the maintainer, I
guess I'll prepare a 1.8.2 NMU with the 7a1471 patch backported for
unstable.
1.8.3 is out but that makes a diff a bit too huge for an NMU maybe.
Backporting only the relevant patch makes it a bit smaller, so here's
the debdiff I'm gonna upload to DELAYED/2.
Fix for CVE-2011-3601 was missing so here's the debdiff to the -1.2 NMU,
just uploaded to unstable.
Regards,
--
Yves-Alexis
diff -u radvd-1.8/debian/changelog radvd-1.8/debian/changelog
--- radvd-1.8/debian/changelog
+++ radvd-1.8/debian/changelog
@@ -1,3 +1,13 @@
+radvd (1:1.8-1.2) unstable; urgency=high
+
+ * Non-maintainer upload by the Security Team.
+ * debian/patches:
+- add 0008-In-process_ra-ND_OPT_DNSSL_INFORMATION-option-parsin,
+ backported from upstream, fix a buffer overflow leading to privilege
+ escalation (CVE-2011-3601).
+
+ -- Yves-Alexis Perez cor...@debian.org Mon, 17 Oct 2011 18:24:08 +0200
+
radvd (1:1.8-1.1) unstable; urgency=high
* Non-maintainer upload by the Security Team.
only in patch2:
unchanged:
--- radvd-1.8.orig/debian/patches/0008-In-process_ra-ND_OPT_DNSSL_INFORMATION-option-parsin.patch
+++ radvd-1.8/debian/patches/0008-In-process_ra-ND_OPT_DNSSL_INFORMATION-option-parsin.patch
@@ -0,0 +1,45 @@
+From 9dfaaaf740ce784541e76e68de4ae04dce2c0921 Mon Sep 17 00:00:00 2001
+From: Vasiliy Kulikov seg...@openwall.com
+Date: Tue, 4 Oct 2011 00:31:15 -0700
+Subject: [PATCH] In process_ra() ND_OPT_DNSSL_INFORMATION option parsing
+ label_len is not checked for negativeness; it leads to
+ suffix buffer overflow, which leads to privilege
+ escalation (at least with -fno-stack-protector, I didn't
+ discover whether it's possible with -fstack-protector).
+
+---
+ process.c | 11 +--
+ 1 files changed, 9 insertions(+), 2 deletions(-)
+
+diff --git a/process.c b/process.c
+index 302bb4f..3307daa 100644
+--- a/process.c
b/process.c
+@@ -280,7 +280,7 @@ process_ra(struct Interface *iface, unsigned char *msg, int len,
+ char prefix_str[INET6_ADDRSTRLEN];
+ char rdnss_str[INET6_ADDRSTRLEN];
+ char suffix[256];
+- int offset, label_len;
++ unsigned int offset, label_len;
+ uint32_t preferred, valid, count;
+
+ if (len 2)
+@@ -434,7 +434,14 @@ process_ra(struct Interface *iface, unsigned char *msg, int len,
+ continue;
+ }
+
+-if ((sizeof(suffix) - strlen(suffix)) (label_len + 2)) {
++/*
++ * 1) must not overflow int: label + 2, offset + label_len
++ * 2) last byte of dnssli_suffix must not overflow opt_str + len
++ */
++if ((sizeof(suffix) - strlen(suffix)) (label_len + 2) ||
++label_len label_len + 2 ||
++dnsslinfo-nd_opt_dnssli_suffixes[offset+label_len] - (char*)opt_str = len ||
++offset + label_len offset) {
+ flog(LOG_ERR, oversized suffix in DNSSL option on %s from %s,
+ iface-Name, addr_str);
+ break;
+--
+1.7.7
+
signature.asc
Description: This is a digitally signed message part
Processed: [bts-link] source package libreoffice
Processing commands for cont...@bugs.debian.org: # # bts-link upstream status pull for source package libreoffice # see http://lists.debian.org/debian-devel-announce/2006/05/msg1.html # user bts-link-upstr...@lists.alioth.debian.org Setting user to bts-link-upstr...@lists.alioth.debian.org (was bts-link-de...@lists.alioth.debian.org). # remote status report for #644957 (http://bugs.debian.org/644957) # Bug title: libreoffice-base: Base runs extremely slowly with newer JDKS # * https://bugs.freedesktop.org/show_bug.cgi?id=35023 # * remote status changed: (?) - RESOLVED # * remote resolution changed: (?) - NOTOURBUG # * closed upstream tags 644957 + fixed-upstream Bug #644957 [libreoffice-base] libreoffice-base: Base runs extremely slowly with newer JDKS Added tag(s) fixed-upstream. usertags 644957 + status-RESOLVED resolution-NOTOURBUG Bug#644957: libreoffice-base: Base runs extremely slowly with newer JDKS There were no usertags set. Usertags are now: status-RESOLVED resolution-NOTOURBUG. thanks Stopping processing here. Please contact me if you need assistance. -- 644957: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=644957 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#645469: bind fails for AF_UNIX sockets with EINVAL
Yes, I think this should be handled in glibc, and the sockaddr_un be fixed to match what the kernel expects, the compat code would be there to fix applications built against the bogus sockaddr_un type. In fact, we already clip the passed size in our eglibc in bind() and connect(), it might suffice in eglibc to Silent truncation sounds a bit dangerous. Could this introduce a security problem? E.g. a malliciously placed socket which matches the truncated path. We do truncating already, only at 108, not at 104. It could only match if the socket name will be really 104 bytes long. The current situation with truncating is not worse than previous one. On the other hand we cannot change size of userland sockaddr_un without ABI change. To do it correctly it would mean to raise soname of eglibc and perform transition involving all packages. Is that really so bad? I guess the impact is minimal. How many libraries would make sockaddr_un part of their ABI? Affected might be all libraries which use sockaddr_un internally. I just commited r3740 and r3739, at least one have to be active with r3735 kernel. I consider it cleanest way from current mess :-( Petr -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#631068: audacity: Commercial use of nyquist not allowed
Has no-one read the Readme.txt file? lib-src/libnyquist/nyquist/Readme.txt README file for Nyquist Version 3.03 24 Feb 2009 Roger B. Dannenberg LICENSE: see license.txt and in the same location is a file called license.txt Steve
Bug#645663: /var/run/sphinxsearch not present after reboot, sphinxsearch fails to start
Package: sphinxsearch
Version: 0.9.9+2.0.1beta-1
Severity: grave
Justification: renders package unusable
Dear Maintainer,
The postinit script creates the /var/run/sphinxsearch directory and assigns
permissions, but after a reboot, /var/run is wiped. The initd script does
not check to make sure /var/run/sphinxsearch exists. Thus the initd script
fails to start searchd (with its pid_file set to
/var/run/sphinxsearch/sphinx.pid).
Observed behaviour after a reboot:
--
$ service sphinxsearch start
Starting sphinxsearch: Sphinx 2.0.1-beta (r2792)
Copyright (c) 2001-2011, Andrew Aksyonoff
Copyright (c) 2008-2011, Sphinx Technologies Inc (http://sphinxsearch.com)
using config file '/etc/sphinxsearch/sphinx.conf'...
WARNING: compat_sphinxql_magics=1 is deprecated; please update your application
and config
FATAL: failed to create pid file '/var/run/sphinxsearch/searchd.pid': No such
file or directory
--
The package works as expected before the initial reboot, but fails after
all subsequent restarts.
The issue appears to have been introduced in 0.9.9-9. I have tested both
0.9.9-9 and
0.9.9+2.0.1beta1 packages, and verified the issue exists in both packages.
Below is a patch, which solves the issue by creating the /var/run/sphinxsearch
directory with the correct permissions in the init script. I have rebuilt the
package with this patch, and verified that it corrects the issue.
diff --git a/debian/init.d b/debian/init.d
index fc60e47..42013ed 100644
--- a/debian/init.d
+++ b/debian/init.d
@@ -47,6 +47,15 @@ fi
set -e
+# Make sure the pidfile directory exists with correct permissions
+piddir=`dirname $PIDFILE`
+if [ ! -d $piddir ]; then
+mkdir -p $piddir
+chown -R sphinxsearch $piddir
+chgrp -R sphinxsearch $piddir
+fi
+
+
running_pid()
{
# Check if a given process pid's cmdline matches a given name
-- System Information:
Debian Release: wheezy/sid
APT prefers testing
APT policy: (500, 'testing')
Architecture: amd64 (x86_64)
Kernel: Linux 3.0.0-1-amd64 (SMP w/1 CPU core)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Versions of packages sphinxsearch depends on:
ii adduser 3.113
ii libc6 2.13-21
ii libexpat1 2.0.1-7
ii libgcc1 1:4.6.1-4
ii libmysqlclient16 5.1.58-1
ii libpq59.1.1-1
ii libstdc++64.6.1-4
ii libstemmer0d 0+svn546-2
ii zlib1g1:1.2.3.4.dfsg-3
sphinxsearch recommends no packages.
sphinxsearch suggests no packages.
-- Configuration Files:
/etc/default/sphinxsearch changed [not included]
-- 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#645658: marked as done (bpython-urwid: unsusable due to urwid 1.0.0 in unstable)
Your message dated Mon, 17 Oct 2011 17:17:31 + with message-id e1rfqod-r9...@franck.debian.org and subject line Bug#645658: fixed in bpython 0.10.1-3 has caused the Debian Bug report #645658, regarding bpython-urwid: unsusable due to urwid 1.0.0 in unstable 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.) -- 645658: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=645658 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: bpython-urwid Version: 0.10.1-2 Severity: grave Tags: patch -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 The current version of bpython-urwid doesn't work with urwid 1.0.0, which is currenty in unstable. This issue has already been fixed upstream. The fix can be found at [1] and [2]. Regards [1] https://bitbucket.org/bobf/bpython/changeset/35cec9e170e7 [1] https://bitbucket.org/bobf/bpython/changeset/9492fcfa3a82 - -- System Information: Debian Release: wheezy/sid APT prefers unstable APT policy: (650, 'unstable'), (601, 'testing'), (600, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 3.0.0-2-amd64 (SMP w/4 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages bpython-urwid depends on: ii bpython 0.10.1-2 ii python2.7.2-9 ii python-urwid 1.0.0-1 bpython-urwid recommends no packages. bpython-urwid suggests no packages. - -- no debconf information -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.11 (GNU/Linux) iQIcBAEBCAAGBQJOnFdtAAoJEGny/FFupxmTU44P/ibcuijFWD1CjjnypXbMy4gf dZ588aU48hHThzxMFDv/ZeT4Utd4wHK1QANoPQwaFWycgV6b5oUtzOp3WaY9cE9J qhZRxJE4K91TqmgL3KB8LHj2ygmV8amVJS0zHcI5w7LOUJV5UpxBUAQqh7PSyYmf 6djElBAPk0YdUoY4JvTvR1GTImbvQu80Wjk+ws4wbX0+0p4ecVMZvUN0JRlzozgV VQ1JBR3MPIzhCuZwH2y5cMovwaKnIH/glXGJJW7u3ts9QHioxsvaPjQHEDPboo8V VWRGu68Fjy7fbtvPdJiQm+199xm7eZNkdhxupppI2uKkN8yaooaJ4n1X8JenR2He /hEhtl3p+svMNcFS0M5VM/0wu2SG/yNqnWHGmwFg12n65QQ03CWGQLBvDzbpVypq +E6r/DUZ7lsp6easLbbvqrW+ktKFg0D62l3ee2CnOhV46GU0lCn7n6LKih53mey5 vnDVHpPkL1N+CMYrFfpD3ShV3PYMad4SEEtpL+rfQUEY1t7pdwlINRozRQCA/cwJ TlpHVMDKCUH44+Fy7l0e+0sm1UzRP0yiR72EWZ2AoOlkSwyByUYjh8IxwRJaUGs+ IJ/9rl3/CRNaMHvAFOvKKTdCkZ5lPabeo3ok/6fIVBGsXd4w3xmRIWlx2lv9Au5M k4Lan8NkRIj8bt8Ox2f7 =yRVO -END PGP SIGNATURE- ---End Message--- ---BeginMessage--- Source: bpython Source-Version: 0.10.1-3 We believe that the bug you reported is fixed in the latest version of bpython, which is due to be installed in the Debian FTP archive: bpython-gtk_0.10.1-3_all.deb to main/b/bpython/bpython-gtk_0.10.1-3_all.deb bpython-urwid_0.10.1-3_all.deb to main/b/bpython/bpython-urwid_0.10.1-3_all.deb bpython3_0.10.1-3_all.deb to main/b/bpython/bpython3_0.10.1-3_all.deb bpython_0.10.1-3.debian.tar.gz to main/b/bpython/bpython_0.10.1-3.debian.tar.gz bpython_0.10.1-3.dsc to main/b/bpython/bpython_0.10.1-3.dsc bpython_0.10.1-3_all.deb to main/b/bpython/bpython_0.10.1-3_all.deb A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 645...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. David Paleino da...@debian.org (supplier of updated bpython 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, 17 Oct 2011 19:08:01 +0200 Source: bpython Binary: bpython bpython3 bpython-gtk bpython-urwid Architecture: source all Version: 0.10.1-3 Distribution: unstable Urgency: low Maintainer: David Paleino da...@debian.org Changed-By: David Paleino da...@debian.org Description: bpython- fancy interface to the Python interpreter - Curses frontend bpython-gtk - fancy interface to the Python interpreter - GTK+ frontend bpython-urwid - fancy interface to the Python interpreter - urwid frontend bpython3 - fancy interface to the Python interpreter - Curses frontend Closes: 645658 Changes: bpython (0.10.1-3) unstable; urgency=low . * Apply patch from upstream to handle newer urwid (Closes: #645658) * Add dh-buildinfo Checksums-Sha1: 40d691f6bc19b8d749f723e36b101a06f322999e 1401 bpython_0.10.1-3.dsc c4a2ba48b47be320d2c6714967916c36d9018e01 8837 bpython_0.10.1-3.debian.tar.gz 606366ac5f746b3cb07892d1eb489ef992f27d55 61380 bpython_0.10.1-3_all.deb
Bug#645546: clang: FTBFS(kfreebsd): error: Operating system is unknown, configure can't continue
Hi! Sylvestre Ledru sylves...@debian.org writes: Le dimanche 16 octobre 2011 à 23:26 +0200, Christoph Egger a écrit : cd build-clang \ ../llvm-2.9/configure CC=x86_64-kfreebsd-gnu-gcc CXX=x86_64-kfreebsd-gnu-g++ CPP=x86_64-kfreebsd-gnu-cpp --with-c-include-dirs=/usr/include/x86_64-kfreebsd-gnu:/usr/include --with-cxx-include-root=/usr/include/c++/4.6 --with-cxx-include-arch=x86_64-kfreebsd-gnu --host=x86_64-kfreebsd-gnu --build=x86_64-kfreebsd-gnu --with-cxx-include-32bit-dir=32 --prefix=/usr --disable-assertions --enable-shared --enable-optimized --with-optimize-option=' -g -O2' --enable-pic --enable-libffi CLANG_VENDOR=Debian checking build system type... x86_64-pc-kfreebsd-gnu checking host system type... x86_64-pc-kfreebsd-gnu checking target system type... x86_64-pc-kfreebsd-gnu checking type of operating system we're going to host on... Unknown checking type of operating system we're going to target... Unknown configure: error: Operating system is unknown, configure can't continue make: *** [/build/buildd-clang_2.9-16-kfreebsd-amd64-JQnCYR/clang-2.9/debian/stamps/configure-stamp-clang] Error 1 I wonder if it is not caused by an update of a dependency. Could it be possible to have access to the config.log file ? It is generally not possible to get at the files from the buildds. I've run a build on my local kfreebsd box (though with ocaml-nox installed) and put the log on http://people.debian.org/~christoph/clang.config.log 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
Bug#597129: marked as done (gpmudmon-applet: uninstallable, depends on libgtkdatabox-0.9.0-0)
Your message dated Mon, 17 Oct 2011 17:38:52 + with message-id e1rfr9i-0002xf...@franck.debian.org and subject line Bug#645575: Removed package(s) from unstable has caused the Debian Bug report #597129, regarding gpmudmon-applet: uninstallable, depends on libgtkdatabox-0.9.0-0 to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 597129: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=597129 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: gpmudmon-applet Version: 0.4.4-1 Severity: grave User: debian-powe...@lists.debian.org Usertags: powerpc Justification: renders package unusable gpmudmon-applet depends on libgtkdatabox-0.9.0-0, but there is no such package in sid/squeeze. -- Jakub Wilk signature.asc Description: Digital signature ---End Message--- ---BeginMessage--- Version: 0.4.4-1+rm Dear submitter, as the package gpmudmon-applet 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/645575 The version of this package that was in Debian prior to this removal can still be found using http://snapshot.debian.org/. This message was generated automatically; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@debian.org. Debian distribution maintenance software pp. Luca Falavigna (the ftpmaster behind the curtain) ---End Message---
Bug#611197: marked as done (gpmudmon-applet: FTBFS: error: ‘GNOME_FILE_DOMAIN_PIXMAP’ undeclared)
Your message dated Mon, 17 Oct 2011 17:38:52 + with message-id e1rfr9i-0002xf...@franck.debian.org and subject line Bug#645575: Removed package(s) from unstable has caused the Debian Bug report #611197, regarding gpmudmon-applet: FTBFS: error: ‘GNOME_FILE_DOMAIN_PIXMAP’ undeclared 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.) -- 611197: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=611197 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Source: gpmudmon-applet Version: 0.3.0-1 Severity: serious Justification: fails to build from source gpmudmon-applet FTBFS in a powerpc squeeze chroot. Tail of the build log: | make[3]: Entering directory `/home/jwilk/gpmudmon-applet-0.3.0/src' | if powerpc-linux-gnu-gcc -DHAVE_CONFIG_H -I. -I. -I.. -pthread -DORBIT2=1 -I/usr/include/gtk-2.0 -I/usr/lib/gtk-2.0/include -I/usr/include/atk-1.0 -I/usr/include/cairo -I/usr/include/pango-1.0 -I/usr/include/gio-unix-2.0/ -I/usr/include/pixman-1 -I/usr/include/freetype2 -I/usr/include/libpng12 -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -I/usr/include/panel-2.0 -I/usr/include/gconf/2 -I/usr/include/libbonoboui-2.0 -I/usr/include/orbit-2.0 -I/usr/include/dbus-1.0 -I/usr/lib/dbus-1.0/include -I/usr/include/libxml2 -I/usr/include/libbonobo-2.0 -I/usr/include/libgnomecanvas-2.0 -I/usr/include/libgnome-2.0 -I/usr/include/bonobo-activation-2.0 -I/usr/include/gail-1.0 -I/usr/include/libart-2.0 -I/usr/include/gnome-vfs-2.0 -I/usr/lib/gnome-vfs-2.0/include -DSHARE_DIR=\/usr/share\ -DPACKAGE_DIR=\/usr/share/gpmudmon-applet\ -DGNOMELOCALEDIR=\/usr/share/locale\ -DPIXMAPS_DIR=\\-Wall -g -O2 -MT gpmudmon.o -MD -MP -MF .deps/gpmudmon.Tpo \ | -c -o gpmudmon.o `test -f 'gpmudmon.c' || echo './'`gpmudmon.c; \ | then mv -f .deps/gpmudmon.Tpo .deps/gpmudmon.Po; \ | else rm -f .deps/gpmudmon.Tpo; exit 1; \ | fi | gpmudmon.c: In function ‘gpmudmon_load_pixbuf’: | gpmudmon.c:89: warning: implicit declaration of function ‘gnome_program_locate_file’ | gpmudmon.c:89: error: ‘GNOME_FILE_DOMAIN_PIXMAP’ undeclared (first use in this function) | gpmudmon.c:89: error: (Each undeclared identifier is reported only once | gpmudmon.c:89: error: for each function it appears in.) | gpmudmon.c: In function ‘about_cb’: | gpmudmon.c:123: warning: implicit declaration of function ‘gnome_about_new’ | gpmudmon.c: In function ‘help_cb’: | gpmudmon.c:151: warning: implicit declaration of function ‘gnome_help_display’ | gpmudmon.c:153: warning: implicit declaration of function ‘gnome_error_dialog’ | gpmudmon.c: In function ‘get_pmud_status’: | gpmudmon.c:491: warning: unused variable ‘str’ | gpmudmon.c:515: warning: unused variable ‘str’ | gpmudmon.c:505: warning: unused variable ‘error’ | gpmudmon.c:473: warning: unused variable ‘ptr1’ | gpmudmon.c:473: warning: unused variable ‘buf2’ | gpmudmon.c: In function ‘save_config’: | gpmudmon.c:619: warning: implicit declaration of function ‘panel_applet_gconf_set_int’ | gpmudmon.c:623: warning: implicit declaration of function ‘panel_applet_gconf_set_string’ | gpmudmon.c: In function ‘load_config’: | gpmudmon.c:650: warning: implicit declaration of function ‘panel_applet_gconf_get_int’ | gpmudmon.c:658: warning: implicit declaration of function ‘panel_applet_gconf_get_string’ | gpmudmon.c:648: warning: unused variable ‘error’ | make[3]: *** [gpmudmon.o] Error 1 -- Jakub Wilk ---End Message--- ---BeginMessage--- Version: 0.4.4-1+rm Dear submitter, as the package gpmudmon-applet 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/645575 The version of this package that was in Debian prior to this removal can still be found using http://snapshot.debian.org/. This message was generated automatically; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@debian.org. Debian distribution maintenance software pp. Luca Falavigna (the ftpmaster behind the curtain) ---End Message---
Bug#645574: marked as done (needs porting to new libpanel-applet interface)
Your message dated Mon, 17 Oct 2011 17:38:52 + with message-id e1rfr9i-0002xf...@franck.debian.org and subject line Bug#645575: Removed package(s) from unstable has caused the Debian Bug report #645574, regarding needs porting to new libpanel-applet interface 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.) -- 645574: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=645574 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Source: gpmudmon-applet Version: 0.4.4-1 Severity: serious User: pkg-gnome-maintain...@lists.alioth.debian.org Usertags: applets-transition Hi, this package currently depends on libpanel-applet2-0 - most likely because it provides an applet for the GNOME panel. The introduction of gnome-panel 3.0 to unstable is imminent. In this version, the libpanel-applet library has undergone large changes, and byzanz requires changes to support this version: * updating to the D-Bus activation mechanism * porting to GTK+ 3 You might want to check if upstream developers provide a new version, compatible with gnome-panel 3.x. Otherwise, porting is a feasible task if you have a pair of hours to spare. If you feel like it, the following guides should help you: * http://developer.gnome.org/gtk3/stable/gtk-migrating-2-to-3.html * http://live.gnome.org/GnomeGoals/AppletsDbusMigration For packages that provide other functionality than the GNOME applet, you can simply disable it in the build and remove the build-dependency if it hasn’t been ported. For pure applets packages, you should ask for removal from the archive if you do not intend to port it to the new interface. Such packages that have not been ported when gnome-panel is ready to migrate will be kicked out of testing. -- System Information: Debian Release: wheezy/sid APT prefers unstable APT policy: (500, 'unstable'), (200, 'experimental') Architecture: i386 (i686) Kernel: Linux 2.6.38-11-generic (SMP w/1 CPU core) 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--- Version: 0.4.4-1+rm Dear submitter, as the package gpmudmon-applet 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/645575 The version of this package that was in Debian prior to this removal can still be found using http://snapshot.debian.org/. This message was generated automatically; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@debian.org. Debian distribution maintenance software pp. Luca Falavigna (the ftpmaster behind the curtain) ---End Message---
Bug#638101: marked as done (RM: window-picker-applet -- RoQA, dead upstream, uninstallable, low popcon)
Your message dated Mon, 17 Oct 2011 17:41:58 + with message-id e1rfrci-00034w...@franck.debian.org and subject line Bug#638101: Removed package(s) from unstable has caused the Debian Bug report #638101, regarding RM: window-picker-applet -- RoQA, dead upstream, uninstallable, low popcon 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.) -- 638101: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=638101 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: window-picker-applet Version: 0.5.8-2 Severity: important User: pkg-gnome-maintain...@lists.alioth.debian.org Usertags: applets-transition Hi, this package currently depends on libpanel-applet2-0 - most likely because it provides an applet for the GNOME panel. The introduction of gnome-panel 3.0 to unstable is imminent. In this version, the libpanel-applet library has undergone large changes, and window-picker-applet requires changes to support this version: * updating to the D-Bus activation mechanism * porting to GTK+ 3 You might want to check if upstream developers provide a new version, compatible with gnome-panel 3.x. Otherwise, porting is a feasible task if you have a pair of hours to spare. If you feel like it, the following guides should help you: * http://developer.gnome.org/gtk3/stable/gtk-migrating-2-to-3.html * http://live.gnome.org/GnomeGoals/AppletsDbusMigration For packages that provide other functionality than the GNOME applet, you can simply disable it in the build and remove the build-dependency if it hasnât been ported. For pure applets packages, you should ask for removal from the archive if you do not intend to port it to the new interface. Such packages that have not been ported when gnome-panel is ready to migrate will be kicked out of testing. Cheers, -- .''`. Josselin Mouette : :' : `. `' `- ---End Message--- ---BeginMessage--- We believe that the bug you reported is now fixed; the following package(s) have been removed from unstable: window-picker-applet |0.5.8-2 | source, amd64, armel, hurd-i386, i386, ia64, kfreebsd-amd64, kfreebsd-i386, mips, mipsel, powerpc, s390, sparc --- Reason --- RoQA, dead upstream, uninstallable, low popcon -- Note that the package(s) have simply been removed from the tag database and may (or may not) still be in the pool; this is not a bug. The package(s) will be physically removed automatically when no suite references them (and in the case of source, when no binary references it). Please also remember that the changes have been done on the master archive (ftp-master.debian.org) and will not propagate to any mirrors (ftp.debian.org included) until the next cron.daily run at the earliest. Packages are usually not removed from testing by hand. Testing tracks unstable and will automatically remove packages which were removed from unstable when removing them from testing causes no dependency problems. The release team can force a removal from testing if it is really needed, please contact them if this should be the case. We try to close Bugs which have been reported against this package automatically. But please check all old bugs, if they where closed correctly or should have been re-assign to another package. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 638...@bugs.debian.org. The full log for this bug can be viewed at http://bugs.debian.org/638101 This message was generated automatically; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@debian.org. Debian distribution maintenance software pp. Luca Falavigna (the ftpmaster behind the curtain) ---End Message---
Bug#625581: Info received (Trying to fix API changes)
Hello Vincent, I'm currently preparing a fix for #632508 and have just seen that you have been working on this bug. Since 0.9.6 also suffers from #632508 I'd like to get a fixed 0.9.1 packaged and then I'd like to merge your changes if this is okay with you. My changes will be visible in DPMT's SVN repository [1] soon. Kind regards, [1] http://svn.debian.org/viewsvn/python-modules/packages/pythonmagick/trunk/ -- Sebastian Ramacher signature.asc Description: OpenPGP digital signature
Bug#638119: marked as done (giplet: needs porting to new libpanel-applet interface)
Your message dated Mon, 17 Oct 2011 17:47:51 + with message-id e1rfrhz-0003xe...@franck.debian.org and subject line Bug#645486: Removed package(s) from unstable has caused the Debian Bug report #638119, regarding giplet: needs porting to new libpanel-applet interface 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.) -- 638119: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=638119 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: giplet Version: 0.2.3-4 Severity: important User: pkg-gnome-maintain...@lists.alioth.debian.org Usertags: applets-transition Hi, this package currently depends on python-gnomeapplet - most likely because it provides an applet for the GNOME panel. The introduction of gnome-panel 3.0 to unstable is imminent. In this version, the panel-applet library has undergone large changes, and giplet requires changes to support this version: * updating to the D-Bus activation mechanism * porting to GTK+ 3 * porting from PyGTK to the GObject Introspection mechanism You might want to check if upstream developers provide a new version, compatible with gnome-panel 3.x. Otherwise, porting is a feasible task if you have a few hours to spare. If you feel like it, the following guides should help you: * http://live.gnome.org/PyGObject/IntrospectionPorting * http://developer.gnome.org/gtk3/stable/gtk-migrating-2-to-3.html * http://live.gnome.org/GnomeGoals/AppletsDbusMigration For packages that provide other functionality than the GNOME applet, you can simply disable it in the build and remove the dependency if it hasnât been ported. For pure applets packages, you should ask for removal from the archive if you do not intend to port it to the new interface. Such packages that have not been ported when gnome-panel is ready to migrate will be kicked out of testing. Cheers, -- .''`. Josselin Mouette : :' : `. `' `- ---End Message--- ---BeginMessage--- Version: 0.2.3-4+rm Dear submitter, as the package giplet 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/645486 The version of this package that was in Debian prior to this removal can still be found using http://snapshot.debian.org/. This message was generated automatically; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@debian.org. Debian distribution maintenance software pp. Luca Falavigna (the ftpmaster behind the curtain) ---End Message---
Bug#645469: bind fails for AF_UNIX sockets with EINVAL
2011/10/17 Petr Salinger petr.salin...@seznam.cz:
I just commited r3740 and r3739, at least one have to be active
with r3735 kernel.
I consider it cleanest way from current mess :-(
Yeah, I guess when the problem is so ugly the solution must be ugly too :-(
Have you tested r3740?
Btw, you forgot kfreebsd-{9,10}
--
Robert Millan
--
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 643604 is serious
Processing commands for cont...@bugs.debian.org: # severity 643604 serious Bug #643604 [qcontrol] fix ftbfs with ld --as-needed and lua in multiarch location Severity set to 'serious' from 'normal' thanks Stopping processing here. Please contact me if you need assistance. -- 643604: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=643604 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#625581: Info received (Trying to fix API changes)
Hello, On Mon, Oct 17, 2011 at 7:44 PM, Sebastian Ramacher s.ramac...@gmx.at wrote: I'm currently preparing a fix for #632508 and have just seen that you have been working on this bug. Since 0.9.6 also suffers from #632508 I'd like to get a fixed 0.9.1 packaged and then I'd like to merge your changes if this is okay with you. There aren't problems with that, save for the fact that you simply won't manage to build 0.9.1. I had started to port 0.9.1 to the newer ImageMagick API, and that turned out to be a nightmare. I'm unsure I have the changes left somewhere, but I had gotten to a 200-some lines diff, and I'm not even sure it did build in the end. You're much better off starting from 0.9.6. As far as I can remember, updating to 0.9.6 didn't actually require changes to the source (save updating the build-deps to the newer imagemagick development packages). That is what I would recommend you to do. There probably aren't changes you would have to incorporate from my packages, but if you wish to base your upon mine, please go ahead. BTW, I can't seem to find you in the Debian Database, so I assume that you may need sponsoring. If such is the case, I could sponsor a new version, if you wish. Cheers ! Vincent -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#625581: Info received (Trying to fix API changes)
Hello, On 10/17/2011 08:04 PM, Vincent Fourmond wrote: On Mon, Oct 17, 2011 at 7:44 PM, Sebastian Ramacher s.ramac...@gmx.at wrote: I'm currently preparing a fix for #632508 and have just seen that you have been working on this bug. Since 0.9.6 also suffers from #632508 I'd like to get a fixed 0.9.1 packaged and then I'd like to merge your changes if this is okay with you. There aren't problems with that, save for the fact that you simply won't manage to build 0.9.1. I had started to port 0.9.1 to the newer ImageMagick API, and that turned out to be a nightmare. I'm unsure I have the changes left somewhere, but I had gotten to a 200-some lines diff, and I'm not even sure it did build in the end. I've got it to build with the changes from [1]. You're much better off starting from 0.9.6. As far as I can remember, updating to 0.9.6 didn't actually require changes to the source (save updating the build-deps to the newer imagemagick development packages). That is what I would recommend you to do. There probably aren't changes you would have to incorporate from my packages, but if you wish to base your upon mine, please go ahead. That would be better probably. I've just commited what I got so far and will update to the new upstream release later today or tomorrow. BTW, I can't seem to find you in the Debian Database, so I assume that you may need sponsoring. If such is the case, I could sponsor a new version, if you wish. Thank you, I'd appreciate that. Kind regards [1] http://studio.imagemagick.org/pipermail/magick-bugs/2010-July/003388.html -- Sebastian Ramacher signature.asc Description: OpenPGP digital signature
Bug#645537: i386 specific
I cannot reproduce this bug on amd64 so I guess it's i386 specific. -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#645681: wicd-curses crashes on any keystroke
Package: wicd-curses Version: 1.7.0+ds1-6 Severity: grave Justification: renders package unusable wicd-curses crashes every time I press a key, with the same error message. The UI displays properly at first, and is consistent with the information provided by wicd-gtk, which works fine, and with iwconfig. I think wicd-curses somehow got the input devices mislabeled, because it treats a keypress like a mouse event. Here's the error message: % wicd-curses rename failed EXCEPTION! Please report this to the maintainer and file a bug report with the backtrace below: Traceback (most recent call last): File /usr/share/wicd/curses/wicd-curses.py, line 904, in call_update_ui self.update_ui(True) File /usr/share/wicd/curses/wicd-curses.py, line 89, in wrapper return func(*args, **kargs) File /usr/share/wicd/curses/wicd-curses.py, line 915, in update_ui self.handle_keys(input_data[1]) File /usr/share/wicd/curses/wicd-curses.py, line 884, in handle_keys if urwid.is_mouse_event(k): AttributeError: 'module' object has no attribute 'is_mouse_event' This problem only appeared after running 'apt-get update apt-get upgrade' today, so it appears to be new in the latest versions of the software or dependencies. -- System Information: Debian Release: wheezy/sid APT prefers unstable APT policy: (500, 'unstable'), (500, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 3.0.0-1-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 Versions of packages wicd-curses depends on: ii python 2.6.7-3 interactive high-level object-orie ii python-urwid 1.0.0-1 curses-based UI/widget library for ii wicd-daemon 1.7.0+ds1-6 wired and wireless network manager Versions of packages wicd-curses recommends: ii sudo 1.8.2-2Provide limited super user privile wicd-curses suggests no packages. Versions of packages wicd depends on: ii wicd-daemon 1.7.0+ds1-6 wired and wireless network manager Versions of packages wicd-gtk depends on: ii python 2.6.7-3 interactive high-level object-orie ii python-glade22.24.0-2GTK+ bindings: Glade support ii python-gtk2 2.24.0-2Python bindings for the GTK+ widge ii wicd-daemon 1.7.0+ds1-6 wired and wireless network manager Versions of packages wicd-gtk recommends: ii python-notify 0.1.1-2+b3 Python bindings for libnotify ii sudo 1.8.2-2Provide limited super user privile Versions of packages wicd-daemon depends on: ii adduser 3.113 add and remove users and groups ii dbus 1.4.16-1simple interprocess messaging syst ii debconf [debconf-2.0]1.5.41 Debian configuration management sy ii dhcp3-client 4.1.1-P1-17 ISC DHCP server (transitional pack ii iproute 20110629-1 networking and traffic control too ii iputils-ping 3:20101006-1+b1 Tools to test the reachability of ii isc-dhcp-client [dhcp3-c 4.1.1-P1-17 ISC DHCP client ii lsb-base 3.2-28 Linux Standard Base 3.2 init scrip ii net-tools1.60-24.1 The NET-3 networking toolkit ii psmisc 22.14-1 utilities that use the proc file s ii python 2.6.7-3 interactive high-level object-orie ii python-dbus 0.84.0-2simple interprocess messaging syst ii python-gobject 2.28.6-5Python bindings for the GObject li ii python-wicd 1.7.0+ds1-6 wired and wireless network manager ii wireless-tools 30~pre9-6 Tools for manipulating Linux Wirel ii wpasupplicant0.7.3-3 client support for WPA and WPA2 (I wicd-daemon recommends no packages. Versions of packages wicd-daemon suggests: ii pm-utils 1.4.1-8utilities and scripts for power ma Versions of packages python-wicd depends on: ii python2.6.7-3interactive high-level object-orie ii python-support1.0.14 automated rebuilding support for P -- debconf information: * wicd/users: jon -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#645612: libopenscap1 and libopenscap0: error when trying to install together
On Mon, Oct 17, 2011 at 02:39:52PM +0200, Julien Cristau wrote: On Mon, Oct 17, 2011 at 14:13:03 +0200, Pierre Chifflier wrote: On Mon, Oct 17, 2011 at 01:20:53PM +0200, Ralf Treinen wrote: Package: libopenscap0,libopenscap1 Version: libopenscap0/0.7.3-1 Version: libopenscap1/0.8.0-1 Severity: serious User: trei...@debian.org Usertags: edos-file-overwrite Date: 2011-10-17 Architecture: amd64 Distribution: sid Hi, automatic installation tests of packages that share a file and at the same time do not conflict by their package dependency relationships has detected the following problem: Arg, I forgot to add the Conflict/Replace lines for the transition. I'll upload a fixed version ASAP. In the meantime you can safely remove libopenscap0 (both versions are not meant to be installed at the same time). Note that that'd still be buggy. Shared library packages must not contain non-versioned files, see policy 8.2. Please fix this properly instead. Yep, according to policy 8.2 the probe files (required by the lib at runtime, and cannot be run by user directly) should go to /usr/lib/openscap1 instead of /usr/lib/openscap/ and the only binary to another package. I'll take care of that after this upload. Pierre -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed (with 1 errors): tagging as pending bugs that are closed by packages in NEW
Processing commands for cont...@bugs.debian.org: # Mon Oct 17 19:21:16 UTC 2011 # Tagging as pending bugs that are closed by packages in NEW # http://ftp-master.debian.org/new.html # # Source package in NEW: ccseapps tags 624233 + pending Failed to alter tags of Bug 624233: Not altering archived bugs; see unarchive. # Source package in NEW: libtorrent tags 644031 + pending Bug #644031 [rtorrent] rtorrent: Uninstallable in sid due to missing libtorrent14 package Added tag(s) pending. # Source package in NEW: libtorrent tags 490277 + pending Bug #490277 [rtorrent] rtorrent: IPv6 support would be nice Added tag(s) pending. # Source package in NEW: xf86-video-omap tags 640721 + pending Bug #640721 [wnpp] ITP: xf86-video-omap -- X.Org X server -- OMAP display driver Added tag(s) pending. End of message, stopping processing here. Please contact me if you need assistance. -- 640721: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=640721 490277: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=490277 624233: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=624233 644031: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=644031 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#642836: Bug#577704: Confirming bug in libsurefire-java
On Fri, Oct 14, 2011 at 4:23 PM, Damien Raude-Morvan draz...@drazzib.com wrote: Could you please check if this is fixed with maven2 2.2.1-10 ? I think that Build-Depends: libmaven-plugin-tools-java is missing only but I may be wrong... Cheers, Torsten -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#645527: marked as done (bind() fails for AF_UNIX sockets with EINVAL)
Your message dated Mon, 17 Oct 2011 19:48:39 + with message-id e1rftat-0008wq...@franck.debian.org and subject line Bug#645527: fixed in kfreebsd-8 8.2-10 has caused the Debian Bug report #645527, regarding bind() fails for AF_UNIX sockets with EINVAL 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.) -- 645527: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=645527 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: kfreebsd-9 Version: 9.0~svn225873 Severity: important Hi, Typical kfreebsd-amd64 experimental system. When I try to use cupt update after booting with kfreebsd 9, it always fails: E: unable to bind server socket to file '/tmp/cuptyL8GPC': Invalid argument E: error performing command 'update' By contrast, kfreebsd-image-8.2-1-amd64 8.2-8+gcc45 works fine. Trying to track this down, I tried the example from the bind(2) manpage (from manpages-dev 3.32-0.2), with MY_SOCK_PATH set to /tmp/somepath so it wouldn't require root permissions. Same story there --- the 8.2 kernel works fine, while kfreebsd 9 gives me bind: Invalid argument For reference, the installed libc0.1 is 2.13-21. Anyway, thought you might like to know. Regards, Jonathan ---End Message--- ---BeginMessage--- Source: kfreebsd-8 Source-Version: 8.2-10 We believe that the bug you reported is fixed in the latest version of kfreebsd-8, which is due to be installed in the Debian FTP archive: kfreebsd-8_8.2-10.debian.tar.gz to main/k/kfreebsd-8/kfreebsd-8_8.2-10.debian.tar.gz kfreebsd-8_8.2-10.dsc to main/k/kfreebsd-8/kfreebsd-8_8.2-10.dsc kfreebsd-headers-8-amd64_8.2-10_kfreebsd-amd64.deb to main/k/kfreebsd-8/kfreebsd-headers-8-amd64_8.2-10_kfreebsd-amd64.deb kfreebsd-headers-8.2-1-amd64_8.2-10_kfreebsd-amd64.deb to main/k/kfreebsd-8/kfreebsd-headers-8.2-1-amd64_8.2-10_kfreebsd-amd64.deb kfreebsd-headers-8.2-1_8.2-10_kfreebsd-amd64.deb to main/k/kfreebsd-8/kfreebsd-headers-8.2-1_8.2-10_kfreebsd-amd64.deb kfreebsd-image-8-amd64_8.2-10_kfreebsd-amd64.deb to main/k/kfreebsd-8/kfreebsd-image-8-amd64_8.2-10_kfreebsd-amd64.deb kfreebsd-image-8.2-1-amd64_8.2-10_kfreebsd-amd64.deb to main/k/kfreebsd-8/kfreebsd-image-8.2-1-amd64_8.2-10_kfreebsd-amd64.deb kfreebsd-source-8.2_8.2-10_all.deb to main/k/kfreebsd-8/kfreebsd-source-8.2_8.2-10_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 645...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Robert Millan r...@debian.org (supplier of updated kfreebsd-8 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, 17 Oct 2011 20:32:16 +0200 Source: kfreebsd-8 Binary: kfreebsd-source-8.2 kfreebsd-headers-8.2-1 kfreebsd-image-8.2-1-amd64 kfreebsd-image-8-amd64 kfreebsd-headers-8.2-1-amd64 kfreebsd-headers-8-amd64 kfreebsd-image-8.2-1-486 kfreebsd-image-8-486 kfreebsd-headers-8.2-1-486 kfreebsd-headers-8-486 kfreebsd-image-8.2-1-686 kfreebsd-image-8-686 kfreebsd-headers-8.2-1-686 kfreebsd-headers-8-686 kfreebsd-image-8.2-1-686-smp kfreebsd-image-8-686-smp kfreebsd-headers-8.2-1-686-smp kfreebsd-headers-8-686-smp kfreebsd-image-8.2-1-xen kfreebsd-image-8-xen kfreebsd-headers-8.2-1-xen kfreebsd-headers-8-xen kfreebsd-image-8.2-1-malta kfreebsd-image-8-malta kfreebsd-headers-8.2-1-malta kfreebsd-headers-8-malta Architecture: source all kfreebsd-amd64 Version: 8.2-10 Distribution: unstable Urgency: low Maintainer: GNU/kFreeBSD Maintainers debian-...@lists.debian.org Changed-By: Robert Millan r...@debian.org Description: kfreebsd-headers-8-486 - header files for kernel of FreeBSD 8 (meta-package) kfreebsd-headers-8-686 - header files for kernel of FreeBSD 8 (meta-package) kfreebsd-headers-8-686-smp - header files for kernel of FreeBSD 8 (meta-package) kfreebsd-headers-8-amd64 - header files for kernel of FreeBSD 8 (meta-package) kfreebsd-headers-8-malta - header files for kernel of FreeBSD 8 (meta-package) kfreebsd-headers-8-xen - header files for kernel of FreeBSD 8 (meta-package) kfreebsd-headers-8.2-1 - Common architecture-specific header files for kernel of FreeBSD 8 kfreebsd-headers-8.2-1-486 - header files for kernel of FreeBSD 8.2 kfreebsd-headers-8.2-1-686 - header files for
Bug#645612: marked as done (libopenscap1 and libopenscap0: error when trying to install together)
Your message dated Mon, 17 Oct 2011 19:48:59 + with message-id e1rftbd-wx...@franck.debian.org and subject line Bug#645612: fixed in openscap 0.8.0-2 has caused the Debian Bug report #645612, regarding libopenscap1 and libopenscap0: error when trying to install together to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 645612: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=645612 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: libopenscap0,libopenscap1 Version: libopenscap0/0.7.3-1 Version: libopenscap1/0.8.0-1 Severity: serious User: trei...@debian.org Usertags: edos-file-overwrite Date: 2011-10-17 Architecture: amd64 Distribution: sid Hi, automatic installation tests of packages that share a file and at the same time do not conflict by their package dependency relationships has detected the following problem: WARNING: The following packages cannot be authenticated! libsasl2-2 libldap-2.4-2 libpcre3 libnl1 libcap2 libxml2 libxslt1.1 libopenscap0 libopenscap1 Authentication warning overridden. Can not write log, openpty() failed (/dev/pts not mounted?) Selecting previously unselected package libsasl2-2. (Reading database ... 10586 files and directories currently installed.) Unpacking libsasl2-2 (from .../libsasl2-2_2.1.25.dfsg1-2_amd64.deb) ... Selecting previously unselected package libldap-2.4-2. Unpacking libldap-2.4-2 (from .../libldap-2.4-2_2.4.25-3_amd64.deb) ... Selecting previously unselected package libpcre3. Unpacking libpcre3 (from .../libpcre3_8.12-4_amd64.deb) ... Selecting previously unselected package libnl1. Unpacking libnl1 (from .../libnl1_1.1-7_amd64.deb) ... Selecting previously unselected package libcap2. Unpacking libcap2 (from .../libcap2_1%3a2.22-1_amd64.deb) ... Selecting previously unselected package libxml2. Unpacking libxml2 (from .../libxml2_2.7.8.dfsg-5_amd64.deb) ... Selecting previously unselected package libxslt1.1. Unpacking libxslt1.1 (from .../libxslt1.1_1.1.26-8_amd64.deb) ... Selecting previously unselected package libopenscap0. Unpacking libopenscap0 (from .../libopenscap0_0.7.3-1_amd64.deb) ... Selecting previously unselected package libopenscap1. Unpacking libopenscap1 (from .../libopenscap1_0.8.0-1_amd64.deb) ... dpkg: error processing /var/cache/apt/archives/libopenscap1_0.8.0-1_amd64.deb (--unpack): trying to overwrite '/usr/bin/oscap', which is also in package libopenscap0 0.7.3-1 configured to not write apport reports dpkg-deb: error: subprocess paste was killed by signal (Broken pipe) Processing triggers for man-db ... Errors were encountered while processing: /var/cache/apt/archives/libopenscap1_0.8.0-1_amd64.deb E: Sub-process /usr/bin/dpkg returned an error code (1) This is a serious bug as it makes installation fail, and violates sections 7.6.1 and 10.1 of the policy. An optimal solution would consist in only one of the packages installing that file, and renaming or removing the file in the other package. Depending on the circumstances you might also consider Replace relations or file diversions. If the conflicting situation cannot be resolved then, as a last resort, the two packages have to declare a mutual Conflict. Please take into account that Replaces, Conflicts and diversions should only be used when packages provide different implementations for the same functionality. Here is a list of files that are known to be shared by both packages (according to the Contents file for sid/amd64, which may be slightly out of sync): /usr/bin/oscap /usr/lib/openscap/probe_dnscache /usr/lib/openscap/probe_dpkginfo /usr/lib/openscap/probe_family /usr/lib/openscap/probe_file /usr/lib/openscap/probe_filehash /usr/lib/openscap/probe_inetlisteningservers /usr/lib/openscap/probe_interface /usr/lib/openscap/probe_ldap57 /usr/lib/openscap/probe_partition /usr/lib/openscap/probe_password /usr/lib/openscap/probe_process /usr/lib/openscap/probe_runlevel /usr/lib/openscap/probe_shadow /usr/lib/openscap/probe_sysctl /usr/lib/openscap/probe_system_info /usr/lib/openscap/probe_textfilecontent /usr/lib/openscap/probe_textfilecontent54 /usr/lib/openscap/probe_uname /usr/lib/openscap/probe_xinetd /usr/lib/openscap/probe_xmlfilecontent /usr/share/man/man8/oscap.8.gz /usr/share/openscap/scap-fedora14-oval.xml /usr/share/openscap/scap-fedora14-xccdf.xml /usr/share/openscap/scap-rhel6-oval.xml /usr/share/openscap/scap-rhel6-xccdf.xml /usr/share/openscap/schemas/oval/5.8/aix-definitions-schema.xsd /usr/share/openscap/schemas/oval/5.8/aix-system-characteristics-schema.xsd
Bug#645681: wicd-curses crashes on any keystroke
tags 645681 confirmed upstream retitle 645681 urwid 1.0.0 breaks wicd-curses thanks Hello Jonathan, On Mon, 17 Oct 2011 15:22:38 -0400, Jonathan Lane wrote: Package: wicd-curses Version: 1.7.0+ds1-6 Severity: grave Justification: renders package unusable wicd-curses crashes every time I press a key, with the same error message. [..] This problem only appeared after running 'apt-get update apt-get upgrade' today, so it appears to be new in the latest versions of the software or dependencies. You're right, in fact it's the new urwid that broke everything. I'll make a new upload ASAP. Kindly, David -- . ''`. Debian developer | http://wiki.debian.org/DavidPaleino : :' : Linuxer #334216 --|-- http://www.hanskalabs.net/ `. `'` GPG: 1392B174 | http://deb.li/dapal `- 2BAB C625 4E66 E7B8 450A C3E1 E6AA 9017 1392 B174 signature.asc Description: PGP signature
Processed: Re: Bug#645681: wicd-curses crashes on any keystroke
Processing commands for cont...@bugs.debian.org: tags 645681 confirmed upstream Bug #645681 [wicd-curses] wicd-curses crashes on any keystroke Added tag(s) upstream and confirmed. retitle 645681 urwid 1.0.0 breaks wicd-curses Bug #645681 [wicd-curses] wicd-curses crashes on any keystroke Changed Bug title to 'urwid 1.0.0 breaks wicd-curses' from 'wicd-curses crashes on any keystroke' thanks Stopping processing here. Please contact me if you need assistance. -- 645681: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=645681 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: retitle 638112 to RM: libgail-gnome -- ROM; dead upstream, uninstallable
Processing commands for cont...@bugs.debian.org: retitle 638112 RM: libgail-gnome -- ROM; dead upstream, uninstallable Bug #638112 [ftp.debian.org] RM: libgail-module -- ROM; dead upstream, uninstallable Changed Bug title to 'RM: libgail-gnome -- ROM; dead upstream, uninstallable' from 'RM: libgail-module -- ROM; dead upstream, uninstallable' thanks Stopping processing here. Please contact me if you need assistance. -- 638112: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=638112 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#644588: gle-graphics: FTBFS(kfreebsd): Message: /usr/lib/libgle-graphics-4.2.2.so: cannot open shared object file: No such file or directory
On Fri, Oct 07, 2011 at 11:33:33PM +0200, Christoph Egger wrote: Hi! Christian T. Steigies c...@debian.org writes: Hi, On Fri, Oct 07, 2011 at 12:08:59PM +0200, Christian T. Steigies wrote: On Fri, Oct 07, 2011 at 10:22:32AM +0200, Christoph Egger wrote: Package: src:gle-graphics Version: 4.2.2-5 Severity: serious Tags: sid wheezy Justification: fails to build from source (but built successfully in the past) Hi! Your package failed to build on the kfreebsd-* buildds: I do not understand why it fails now, since it has built before. As you can see, the previous binNMU has also failed, while the one before was successful: https://buildd.debian.org/status/logs.php?pkg=gle-graphicsarch=kfreebsd-amd64 The problem seems to be that during the build process the binary, that has just been built, is run a few times. It needs a library that has just been built and it should use the library from the build directory, since it is not installed on the system. In 4.2.2-4+b1 and -4, the library was found, in 4.2.2-4+b2 and -5, the library is not found. What has changed in kfreebsd in the meantime, and how do I circumvent it? I have successfully built 4.2.2-4 (which failed in the last binNMU) and 4.2.2-5 in an unstable chroot on asdfasdf.debian.net, the kfreebsd-amd64 porterbox. On io.debian.net, the kfreebsd-i386 porterbox, the build does not complete as there is no gs installed in the unstable chroot, but the executable works where it has failed on your machine: I've done some test-builds on my local box. It's permanently building Any news on this? Your bug report is blocking the package from moving to testing: http://qa.debian.org/excuses.php?package=gle-graphics fine unless I'm doing parallel build which fails in a different way: cp -p manip.hlp ../../build/manip.hlp g++ -DHAVE_CONFIG_H -DGLEVN=\4.2.2\ -pthread -I/usr/include/pixman-1 -I/usr/include/freetype2 -I/usr/include/libpng12 -I/usr/include/cairo -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -I/usr/include/libpng12 cell.o cmd.o eval.o filemenu.o fn.o general.o keyword.o manip.o mjl.o polish.o sub.o token.o var.o unix_extra.o unixinkey.o varargs.o unixscr.o ../gle/cutils.static.o ../gle/file_io.static.o -o ../../build/bin/manip -lncurses -ltinfo -lm make[2]: Leaving directory `/var/tmp/gle-graphics-4.2.2/src/manip' /usr/bin/make -C src/gui -f MakefileAC make[2]: Entering directory `/var/tmp/gle-graphics-4.2.2/src/gui' /usr/bin/qmake-qt4 /usr/bin/make make[3]: Entering directory `/var/tmp/gle-graphics-4.2.2/src/gui' make[3]: warning: jobserver unavailable: using -j1. Add `+' to parent make rule. make[3]: *** No targets specified and no makefile found. Stop. make[3]: Leaving directory `/var/tmp/gle-graphics-4.2.2/src/gui' make[2]: *** [domake] Error 2 make[2]: *** Waiting for unfinished jobs I am not sure what a parallel build is, but it seems to be something that is not done on buildds. I'll reshedule the build to see what happens. If it still fails hopefully someone from -bsd can help you further. So to summarize, both you and I can build the package on kfreebsd machines (debian porter boxes and your box), but the buildds fail to build since 4.2.2-4+b2, whereas 4.2.2-4+b1 and 4.2.2-4 have built successfully. Note that in a binNMU the source code has not been changed. From this I conclude that the bug is not in the source, but only on the buildds, especially since other kfreebsd machines build the package fine, without any source changes. Since nobody from -bsd seems to be able to help, I suggest to reassign the bug to bsd (what would be the pseudo package for that?) or reduce the severity from serious to something reasonable, normal or minor. Christian -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#634051: marked as done (wicd-daemon: Fails to install/upgrade if existing user is removed)
Your message dated Mon, 17 Oct 2011 21:07:03 + with message-id e1rfuol-0007k9...@franck.debian.org and subject line Bug#634051: fixed in wicd 1.7.0+ds1-7 has caused the Debian Bug report #634051, regarding wicd-daemon: Fails to install/upgrade if existing user is removed 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.) -- 634051: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=634051 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: wicd-daemon Version: 1.7.0+ds1-6 Severity: serious Justification: Policy 10.7.3 -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Dear maintainer, Installation/Upgrade of wicd-daemon fails at configure stage if a user that previously existed when wicd-daemon was installed is later removed from the system. To reproduce: sudo adduser testuser sudo apt-get install wicd-daemon (select to add 'testuser' to netenv group) sudo deluser testuser sudo dpkg-reconfigure wicd-daemon: adduser: The user `testuser' does not exist. When updating, this results for example in: Setting up wicd-daemon (1.7.0+ds1-2) ... Installing new version of config file /etc/dbus-1/system.d/wicd.conf ... Installing new version of config file /etc/init.d/wicd ... adduser: The user `bryony' does not exist. dpkg: error processing wicd-daemon (--configure): subprocess installed post-installation script returned error exit status 1 Workaround: Add the user again, then 'sudo apt-get -f install' - -- System Information: Debian Release: wheezy/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: amd64 (x86_64) Kernel: Linux 3.0.0-999-generic (SMP w/2 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages wicd-daemon depends on: ii adduser 3.113 add and remove users and groups ii dbus 1.4.12-4simple interprocess messaging syst ii debconf [debconf-2.0]1.5.40 Debian configuration management sy ii iproute 20110629-1 networking and traffic control too ii iputils-ping 3:20101006-1+b1 Tools to test the reachability of ii isc-dhcp-client [dhcp3-c 4.1.1-P1-17 ISC DHCP client ii lsb-base 3.2-27 Linux Standard Base 3.2 init scrip ii net-tools1.60-24 The NET-3 networking toolkit ii psmisc 22.14-1 utilities that use the proc file s ii python 2.6.7-1 interactive high-level object-orie ii python-dbus 0.84.0-1simple interprocess messaging syst ii python-gobject 2.28.6-4Python bindings for the GObject li ii python-wicd 1.7.0+ds1-6 wired and wireless network manager ii wireless-tools 30~pre9-5 Tools for manipulating Linux Wirel ii wpasupplicant0.7.3-3 client support for WPA and WPA2 (I Versions of packages wicd-daemon recommends: ii wicd-gtk [wicd-client] 1.7.0+ds1-6 wired and wireless network manager Versions of packages wicd-daemon suggests: pn pm-utils none (no description available) Versions of packages wicd-gtk depends on: ii python2.6.7-1interactive high-level object-orie ii python-glade2 2.24.0-2 GTK+ bindings: Glade support ii python-gtk2 2.24.0-2 Python bindings for the GTK+ widge Versions of packages wicd-gtk recommends: ii python-notify 0.1.1-2+b3 Python bindings for libnotify ii sudo 1.7.4p6-1 Provide limited super user privile Versions of packages python-wicd depends on: ii python2.6.7-1interactive high-level object-orie ii python-support1.0.14 automated rebuilding support for P - -- debconf information excluded -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.11 (GNU/Linux) iQIcBAEBAgAGBQJOIXvRAAoJEGHzRCZ03mYkKjYP/1jjdwDDBqFPY5+5pxGtHnMW 51DT+PK4XUe/KTDEKaBCAJh6Ld4YJMpXj33MFFCKcWjI7WYNzM2eC6i/yaGbrrg/ mjrtan2KM7mOJh7n8BElTvcxc72RZcGju/352JOnfg/PODxZgzoMJsTaoK70Guqi 3E9ickDz6xRT+QMXpCqjQSv+7pCIQpezw+4y9fG2atsyAAUFzdYKv3MS9rdUMwd3 wbj7fo4zq5HzdUsALcDBtl9R1hSV98CZg0IqZerN/jRcJGR7joAb0WSisKoTpzR3 mIpL9WbQ2EVWw4cGiwAh0fSvausKi0pFoqwEAJZ/S+F70Ftj9zcITuSDApDukO2F OvoelKycZH9XcMZXBIaQ3PgX/+jFdvhcVhVmpbyRi2nRwVzV/fAFQ818IwQKTCug tbQ7x+Yr9D+FVQampY4h27ZO9nibQDt9bpvPTwjfQL9+PcIbgIPJf/xDcPLO4cYt ZOiFc3WDdCWkKdlrvrVLRXASbsaS2O32+zQ1W1M52a75ubnOtnaoVt8A08NZkqC3
Bug#645681: marked as done (urwid 1.0.0 breaks wicd-curses)
Your message dated Mon, 17 Oct 2011 21:07:03 + with message-id e1rfuol-0007kd...@franck.debian.org and subject line Bug#645681: fixed in wicd 1.7.0+ds1-7 has caused the Debian Bug report #645681, regarding urwid 1.0.0 breaks wicd-curses 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.) -- 645681: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=645681 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: wicd-curses Version: 1.7.0+ds1-6 Severity: grave Justification: renders package unusable wicd-curses crashes every time I press a key, with the same error message. The UI displays properly at first, and is consistent with the information provided by wicd-gtk, which works fine, and with iwconfig. I think wicd-curses somehow got the input devices mislabeled, because it treats a keypress like a mouse event. Here's the error message: % wicd-curses rename failed EXCEPTION! Please report this to the maintainer and file a bug report with the backtrace below: Traceback (most recent call last): File /usr/share/wicd/curses/wicd-curses.py, line 904, in call_update_ui self.update_ui(True) File /usr/share/wicd/curses/wicd-curses.py, line 89, in wrapper return func(*args, **kargs) File /usr/share/wicd/curses/wicd-curses.py, line 915, in update_ui self.handle_keys(input_data[1]) File /usr/share/wicd/curses/wicd-curses.py, line 884, in handle_keys if urwid.is_mouse_event(k): AttributeError: 'module' object has no attribute 'is_mouse_event' This problem only appeared after running 'apt-get update apt-get upgrade' today, so it appears to be new in the latest versions of the software or dependencies. -- System Information: Debian Release: wheezy/sid APT prefers unstable APT policy: (500, 'unstable'), (500, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 3.0.0-1-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 Versions of packages wicd-curses depends on: ii python 2.6.7-3 interactive high-level object-orie ii python-urwid 1.0.0-1 curses-based UI/widget library for ii wicd-daemon 1.7.0+ds1-6 wired and wireless network manager Versions of packages wicd-curses recommends: ii sudo 1.8.2-2Provide limited super user privile wicd-curses suggests no packages. Versions of packages wicd depends on: ii wicd-daemon 1.7.0+ds1-6 wired and wireless network manager Versions of packages wicd-gtk depends on: ii python 2.6.7-3 interactive high-level object-orie ii python-glade22.24.0-2GTK+ bindings: Glade support ii python-gtk2 2.24.0-2Python bindings for the GTK+ widge ii wicd-daemon 1.7.0+ds1-6 wired and wireless network manager Versions of packages wicd-gtk recommends: ii python-notify 0.1.1-2+b3 Python bindings for libnotify ii sudo 1.8.2-2Provide limited super user privile Versions of packages wicd-daemon depends on: ii adduser 3.113 add and remove users and groups ii dbus 1.4.16-1simple interprocess messaging syst ii debconf [debconf-2.0]1.5.41 Debian configuration management sy ii dhcp3-client 4.1.1-P1-17 ISC DHCP server (transitional pack ii iproute 20110629-1 networking and traffic control too ii iputils-ping 3:20101006-1+b1 Tools to test the reachability of ii isc-dhcp-client [dhcp3-c 4.1.1-P1-17 ISC DHCP client ii lsb-base 3.2-28 Linux Standard Base 3.2 init scrip ii net-tools1.60-24.1 The NET-3 networking toolkit ii psmisc 22.14-1 utilities that use the proc file s ii python 2.6.7-3 interactive high-level object-orie ii python-dbus 0.84.0-2simple interprocess messaging syst ii python-gobject 2.28.6-5Python bindings for the GObject li ii python-wicd 1.7.0+ds1-6 wired and wireless network manager ii wireless-tools 30~pre9-6 Tools for manipulating Linux Wirel ii wpasupplicant0.7.3-3 client support for WPA and WPA2 (I
Bug#644031: marked as done (rtorrent: Uninstallable in sid due to missing libtorrent14 package)
Your message dated Mon, 17 Oct 2011 21:17:41 + with message-id e1rfuz3-es...@franck.debian.org and subject line Bug#644031: fixed in libtorrent 0.12.9-3 has caused the Debian Bug report #644031, regarding rtorrent: Uninstallable in sid due to missing libtorrent14 package 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.) -- 644031: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=644031 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: rtorrent Version: 0.8.9-1 Severity: serious Hi! This packages is uninstallable due to its dependency on libtorrent14, which is not in the archive, neither in NEW. When uploading new upstream versions depending on libtorrent packages with SONAME bumped, could you try to make sure the library packages have gotten out of NEW first? In this case it's not a big deal but in other cases it might tie up other transitions. thanks, guillem ---End Message--- ---BeginMessage--- Source: libtorrent Source-Version: 0.12.9-3 We believe that the bug you reported is fixed in the latest version of libtorrent, which is due to be installed in the Debian FTP archive: libtorrent-dev_0.12.9-3_amd64.deb to main/libt/libtorrent/libtorrent-dev_0.12.9-3_amd64.deb libtorrent14_0.12.9-3_amd64.deb to main/libt/libtorrent/libtorrent14_0.12.9-3_amd64.deb libtorrent_0.12.9-3.debian.tar.gz to main/libt/libtorrent/libtorrent_0.12.9-3.debian.tar.gz libtorrent_0.12.9-3.dsc to main/libt/libtorrent/libtorrent_0.12.9-3.dsc libtorrent_0.12.9.orig.tar.gz to main/libt/libtorrent/libtorrent_0.12.9.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 644...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Rogério Brito rbr...@ime.usp.br (supplier of updated libtorrent package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.8 Date: Thu, 13 Oct 2011 13:54:16 -0300 Source: libtorrent Binary: libtorrent-dev libtorrent14 Architecture: source amd64 Version: 0.12.9-3 Distribution: unstable Urgency: medium Maintainer: Jose Luis Rivas ghost...@debian.org Changed-By: Rogério Brito rbr...@ime.usp.br Description: libtorrent-dev - C++ BitTorrent library by Rakshasa (development files) libtorrent14 - C++ BitTorrent library by Rakshasa Closes: 490277 644031 Changes: libtorrent (0.12.9-3) unstable; urgency=medium . * Urgency medium due to RC bugfix. Closes: #644031. * debian/patches: Fix compilation with IPv6. Closes: #490277. Thanks to Steinar H. Gunderson. Checksums-Sha1: 53fd02156859dc44e2136e7ffe3b942e725b65c2 1466 libtorrent_0.12.9-3.dsc 176a836c6e685e4dad71ac08c0e09caaa5b7757c 667864 libtorrent_0.12.9.orig.tar.gz c4cd076e9f6cce6e45dd95ddca16c149d79741c4 24724 libtorrent_0.12.9-3.debian.tar.gz 70974a8c7f3195d30fc011ae32ae47e89a84e771 57846 libtorrent-dev_0.12.9-3_amd64.deb 8697484fa21c84782969a92b871aea6ffe87129d 405286 libtorrent14_0.12.9-3_amd64.deb Checksums-Sha256: a6a3cb1789bf7fe47bf287b9557740f851ddd4f8fc4e46a989274a5f5dda5409 1466 libtorrent_0.12.9-3.dsc 15dc9e8dd45d070f447e599bef08ef0ca421bac6e7f55e608dcd19360594af64 667864 libtorrent_0.12.9.orig.tar.gz 3e6cf620076d8930d3a55099280dc1d6f568a905ab1d2f32b0e0b4bd88962a5a 24724 libtorrent_0.12.9-3.debian.tar.gz 331106ad5e361f63d2174d68568c3cc7e92602e663b9691de8cf76ba9c8f09a0 57846 libtorrent-dev_0.12.9-3_amd64.deb a17b47f92daf8d478965a166547280167dbc379c49fe8c7b4e15c19dea0176ce 405286 libtorrent14_0.12.9-3_amd64.deb Files: 0cc7da7ef0f741749c9dd3ed97627e3a 1466 libs extra libtorrent_0.12.9-3.dsc b128bbd324f03eb42ef5060080f87548 667864 libs extra libtorrent_0.12.9.orig.tar.gz dba9fcc7e88ea9e7eb271c46745ff975 24724 libs extra libtorrent_0.12.9-3.debian.tar.gz 0b03a4c724912167bc43ed0cd440535b 57846 libdevel extra libtorrent-dev_0.12.9-3_amd64.deb 298fbfe42212d5f38b0a64cc8a6535b8 405286 libs extra libtorrent14_0.12.9-3_amd64.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.11 (GNU/Linux) iEYEARECAAYFAk6cJUwACgkQNFDtUT/MKpCwFQCgh9+5gyq9vHPe4TTwmkEInV6Q QcEAn1U0ExVSZhsvScXYPeA37X+FCAH9 =Ffyd -END PGP SIGNATURE- ---End Message---
Bug#644711: marked as done (iceweasel-vimperator: not compatible with iceweasel from testing/sid (7.0.1))
Your message dated Mon, 17 Oct 2011 21:19:23 + with message-id e1rfuah-00015x...@franck.debian.org and subject line Bug#644711: fixed in vimperator 3.2-3 has caused the Debian Bug report #644711, regarding iceweasel-vimperator: not compatible with iceweasel from testing/sid (7.0.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.) -- 644711: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=644711 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: iceweasel-vimperator Version: 3.2-2 Severity: grave Tags: upstream Hi, vimperator 3.2-2 is not marked as compatible with the version of Iceweasel currently is testing/unstable (7.0.1). Setting maxVersion to 7.0.1 in install.rdf makes it work. Bye, -- intrigeri intrig...@boum.org | GnuPG key @ https://gaffer.ptitcanardnoir.org/intrigeri/intrigeri.asc | OTR fingerprint @ https://gaffer.ptitcanardnoir.org/intrigeri/otr.asc | Who wants a world in which the guarantee that we shall not | die of starvation would entail the risk of dying of boredom ? ---End Message--- ---BeginMessage--- Source: vimperator Source-Version: 3.2-3 We believe that the bug you reported is fixed in the latest version of vimperator, which is due to be installed in the Debian FTP archive: iceweasel-vimperator_3.2-3_all.deb to main/v/vimperator/iceweasel-vimperator_3.2-3_all.deb vimperator_3.2-3.debian.tar.gz to main/v/vimperator/vimperator_3.2-3.debian.tar.gz vimperator_3.2-3.dsc to main/v/vimperator/vimperator_3.2-3.dsc A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 644...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Francois Marier franc...@debian.org (supplier of updated vimperator 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, 18 Oct 2011 09:44:39 +1300 Source: vimperator Binary: iceweasel-vimperator Architecture: source all Version: 3.2-3 Distribution: unstable Urgency: medium Maintainer: Francois Marier franc...@debian.org Changed-By: Francois Marier franc...@debian.org Description: iceweasel-vimperator - Iceweasel extension to make it have vim look and feel Closes: 644711 Changes: vimperator (3.2-3) unstable; urgency=medium . * Bump maxVersion to 7.0.1 (closes: #644711) Checksums-Sha1: 804b4315eda466b5e5ee4f4faa0f76e89cf4a22b 1898 vimperator_3.2-3.dsc 78f1cc97182e9d46fd36d78c219f6e985553ef40 2903 vimperator_3.2-3.debian.tar.gz 8dc915903959cd2f68edd06c7a43fb690a11d69c 555900 iceweasel-vimperator_3.2-3_all.deb Checksums-Sha256: 026fd0fed5f1c4ef06a1f8466d6dc082c3125693942357abe66d6d85af674f59 1898 vimperator_3.2-3.dsc b8c96f98dbb09cbf86fb0e664115531a879b45fb4e7dc996d133db75da3dd9e5 2903 vimperator_3.2-3.debian.tar.gz 4b9bb948723190ed39d3691c769b770a517000c5c216e85e4edb0099f7f39906 555900 iceweasel-vimperator_3.2-3_all.deb Files: a8d68785831fc7177d35cf945340a9e7 1898 web optional vimperator_3.2-3.dsc 867c1f20a4e75c9ca95cfff7880cbcba 2903 web optional vimperator_3.2-3.debian.tar.gz a63ee5d056a4ac02716baa95f8574822 555900 web optional iceweasel-vimperator_3.2-3_all.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.11 (GNU/Linux) iQIcBAEBCAAGBQJOnJZ3AAoJEBYoHy4AfJjRZlgP/jRMMFKaPkkZNvXTAuSL/ZsR eiyAsmFAsS16iwD08PV2CwFQYbnNWxX1kHgF98BRc9wuKLjuRjR45Wfl6gkdPt+D zcmzQehQYCcP1d/SHP1o94SVLt/W6FQ8epOoUBSK+7QWdnAXHin/1yX2h+qtL2Ol zYGr5Znz0nGA8Vu5mPzrm0M+W5MSSQwzhfgAsfDtWIQggXsgCmGgxP/3eF+hkdGG mOuU5PRYTiJUQA2PK529nCxS8p/Y8YYuzxrNU70GlYXYh7ejF7+F2UoPUwtJOBUS Z8gW/CflezNr2bKCZC3UNiqSlhzM4wWtd0fqZafA0E+nP5PCgT/RDSEVwPkzTmQW 6ccUnKLKFKBmnW4bylEMr5tvUqWwI0pCeripE+gD8D7+AI/sAp7LIrUJZV+7kuCa lKslqbnKAHrCeKfIq9pAJ4A/YX0AjrGHNjvlwWgXb32Q1uvzyRZj6Dr2jfsrxINC 3Hv6PLuc83pxBXzC0IweoczU8GpHvQzk1Q+cAl1bw3XrUAoBoy3ghtkYepENoG+c wJqSaGuTOGAftYGMQoEDyy00aWH8qKwhZVPeu+XfkMZQFykB+Y8dXZgvgvoT28Eq Xvg9sULKQTwATtQ9Ez64kMTw2JiHJimHEswXUg0Qy7TEFnCm0PlxX/j7HlIYtjAR XemepGbR+IWES0wM0sNM =TL50 -END PGP SIGNATURE- ---End Message---
Bug#628843: Ping
Hello, On Sun, Oct 16, 2011 at 05:20:31PM +0200, bubu...@debian.org wrote: Quoting Arne Wichmann (a...@anhrefn.saar.de): This critical bug is now pending for more than 3 months. Is there any update on the situation? Nicolas should actually release upstream 4.1.5 and then upload 4.1.5-1. Nicolas? Yes, this is the plan. There are still some untested changes, and I still have a few uncommitted changes on my tree. Regarding this bug * Arne, I do not know if your ping was related to the potential security impact, but it could help to have an assessment of the proposed solution (and also comment 46) * It did not seem that critical to me (e.g. in the pointed comp.security.oss.general thread, there were no agreement for a CVE) -- Nekral -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#645697: sqlalchemy: FTBFS: /bin/sh: 1: sphinx-build: not found
Package: src:sqlalchemy Version: 0.7.3-1 Severity: serious Tags: sid wheezy Justification: fails to build from source (but built successfully in the past) Hi! Your package failed to build on all buildds: dh_installdirs -i cd doc/build sphinx-build -N -q -E -b html . \ /build/buildd-sqlalchemy_0.7.3-1-armel-dc7Hs_/sqlalchemy-0.7.3/debian/python-sqlalchemy-doc/usr/share/doc/python-sqlalchemy-doc/html/ /bin/sh: 1: sphinx-build: not found make: *** [build-docs] Error 127 Full build log at https://buildd.debian.org/status/fetch.php?pkg=sqlalchemyarch=kfreebsd-amd64ver=0.7.3-1stamp=1318887428 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
Bug#645698: kbuild: FTBFS: undefined reference to `pthread_getspecific'
Package: src:kbuild Version: 1:0.1.9998svn2543-1 Severity: serious Tags: sid wheezy 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: kBuild: Installing kmk_time = /build/buildd-kbuild_0.1.9998svn2543-1-kfreebsd-i386-NaFp1W/kbuild-0.1.9998svn2543/out/gnukfreebsd.x86/release/stage/kBuild/bin/gnukfreebsd.x86/kmk_time /build/buildd-kbuild_0.1.9998svn2543-1-kfreebsd-i386-NaFp1W/kbuild-0.1.9998svn2543/out/gnukfreebsd.x86/release/obj/kash/shthread.o: In function `shthread_set_shell': /build/buildd-kbuild_0.1.9998svn2543-1-kfreebsd-i386-NaFp1W/kbuild-0.1.9998svn2543/src/kash/shthread.c:84: undefined reference to `pthread_key_create' /build/buildd-kbuild_0.1.9998svn2543-1-kfreebsd-i386-NaFp1W/kbuild-0.1.9998svn2543/src/kash/shthread.c:88: undefined reference to `pthread_setspecific' /build/buildd-kbuild_0.1.9998svn2543-1-kfreebsd-i386-NaFp1W/kbuild-0.1.9998svn2543/out/gnukfreebsd.x86/release/obj/kash/shthread.o: In function `shthread_get_shell': /build/buildd-kbuild_0.1.9998svn2543-1-kfreebsd-i386-NaFp1W/kbuild-0.1.9998svn2543/src/kash/shthread.c:106: undefined reference to `pthread_getspecific' collect2: ld returned 1 exit status This is probably the build system (configure?) detecting *freebsd* and not linking against pthread in that case. Full build log at https://buildd.debian.org/status/fetch.php?pkg=kbuildarch=kfreebsd-i386ver=1%3A0.1.9998svn2543-1stamp=1314212080 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#645697: marked as done (sqlalchemy: FTBFS: /bin/sh: 1: sphinx-build: not found)
Your message dated Mon, 17 Oct 2011 22:18:15 + with message-id e1rfvvf-00089m...@franck.debian.org and subject line Bug#645697: fixed in sqlalchemy 0.7.3-2 has caused the Debian Bug report #645697, regarding sqlalchemy: FTBFS: /bin/sh: 1: sphinx-build: not found to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 645697: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=645697 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: src:sqlalchemy Version: 0.7.3-1 Severity: serious Tags: sid wheezy Justification: fails to build from source (but built successfully in the past) Hi! Your package failed to build on all buildds: dh_installdirs -i cd doc/build sphinx-build -N -q -E -b html . \ /build/buildd-sqlalchemy_0.7.3-1-armel-dc7Hs_/sqlalchemy-0.7.3/debian/python-sqlalchemy-doc/usr/share/doc/python-sqlalchemy-doc/html/ /bin/sh: 1: sphinx-build: not found make: *** [build-docs] Error 127 Full build log at https://buildd.debian.org/status/fetch.php?pkg=sqlalchemyarch=kfreebsd-amd64ver=0.7.3-1stamp=1318887428 Regards Christoph -- 9FED 5C6C E206 B70A 5857 70CA 9655 22B9 D49A E731 Debian Developer | Lisp Hacker | CaCert Assurer ---End Message--- ---BeginMessage--- Source: sqlalchemy Source-Version: 0.7.3-2 We believe that the bug you reported is fixed in the latest version of sqlalchemy, which is due to be installed in the Debian FTP archive: python-sqlalchemy-doc_0.7.3-2_all.deb to main/s/sqlalchemy/python-sqlalchemy-doc_0.7.3-2_all.deb python-sqlalchemy-ext_0.7.3-2_amd64.deb to main/s/sqlalchemy/python-sqlalchemy-ext_0.7.3-2_amd64.deb python-sqlalchemy_0.7.3-2_all.deb to main/s/sqlalchemy/python-sqlalchemy_0.7.3-2_all.deb python3-sqlalchemy_0.7.3-2_all.deb to main/s/sqlalchemy/python3-sqlalchemy_0.7.3-2_all.deb sqlalchemy_0.7.3-2.debian.tar.gz to main/s/sqlalchemy/sqlalchemy_0.7.3-2.debian.tar.gz sqlalchemy_0.7.3-2.dsc to main/s/sqlalchemy/sqlalchemy_0.7.3-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 645...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Piotr Ożarowski pi...@debian.org (supplier of updated sqlalchemy 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, 18 Oct 2011 00:02:50 +0200 Source: sqlalchemy Binary: python-sqlalchemy python-sqlalchemy-ext python-sqlalchemy-doc python3-sqlalchemy Architecture: source all amd64 Version: 0.7.3-2 Distribution: unstable Urgency: low Maintainer: Piotr Ożarowski pi...@debian.org Changed-By: Piotr Ożarowski pi...@debian.org Description: python-sqlalchemy - SQL toolkit and Object Relational Mapper for Python python-sqlalchemy-doc - documentation for the SQLAlchemy Python library python-sqlalchemy-ext - SQL toolkit and Object Relational Mapper for Python - C extension python3-sqlalchemy - SQL toolkit and Object Relational Mapper for Python 3 Closes: 645697 Changes: sqlalchemy (0.7.3-2) unstable; urgency=low . * remove build-indep from build target's dependencies (closes: 645697) Checksums-Sha1: 638499457526a74a5ae0424a17c74fe922c92b9c 2375 sqlalchemy_0.7.3-2.dsc 01dc6c2f0a5f7b9f3348397972df8cb51910d706 9923 sqlalchemy_0.7.3-2.debian.tar.gz dc983c3c3d19fdb67c9a207bc8053ae4f004e651 522990 python-sqlalchemy_0.7.3-2_all.deb 035a9eff53dc8f7ccbd1439068cad0537087a6c7 731858 python-sqlalchemy-doc_0.7.3-2_all.deb dfbf22e90146e3e5e47c15e2f3ebb3feae8ec107 516058 python3-sqlalchemy_0.7.3-2_all.deb 5a8ca78bd00883a6887405d8be32c724bad218e5 21434 python-sqlalchemy-ext_0.7.3-2_amd64.deb Checksums-Sha256: 5380858bd1acb58cf21e1f44c9489f15ea96d158e6e6abf20648eb03864ec8af 2375 sqlalchemy_0.7.3-2.dsc 7103643c6776f077b72e0e438d4818c62fe7bbe152bdce44f676a0388f5bdcf3 9923 sqlalchemy_0.7.3-2.debian.tar.gz 46e8464f50fe2550e4868fcbcc98f88f438db4da9c903a3af4671c06d9637e55 522990 python-sqlalchemy_0.7.3-2_all.deb 6dcf35d7ae58241b5d3d3814abef3679a211b08a21b60d662f13b9ede35e4e70 731858 python-sqlalchemy-doc_0.7.3-2_all.deb c05ee108b900ce67c6edff50bc21b1c5f8fd52d33fd02e31c624b7c8169ec19c 516058 python3-sqlalchemy_0.7.3-2_all.deb c95f71f85e103ec38ab202582fd4f8d968f3592b96914776fbca17158c2c3e8d 21434 python-sqlalchemy-ext_0.7.3-2_amd64.deb Files:
Bug#643404: gyrus: diff for NMU version 0.3.10-1.1
tags 643404 + pending
thanks
Dear maintainer,
I've prepared an NMU for gyrus (versioned as 0.3.10-1.1) and
uploaded it to DELAYED/2. Please feel free to tell me if I
should delay it longer.
Regards.
--
.''`. Homepage: http://info.comodo.priv.at/ - OpenPGP key ID: 0x8649AA06
: :' : Debian GNU/Linux user, admin, developer - http://www.debian.org/
`. `' Member of VIBE!AT SPI, fellow of Free Software Foundation Europe
`-NP: PagePlant: Walking Into Clarksdale
diff -u gyrus-0.3.10/debian/changelog gyrus-0.3.10/debian/changelog
--- gyrus-0.3.10/debian/changelog
+++ gyrus-0.3.10/debian/changelog
@@ -1,3 +1,13 @@
+gyrus (0.3.10-1.1) unstable; urgency=low
+
+ * Non-maintainer upload.
+ * Fix FTBFS: gyrus-admin.c:1474:4: error: format not a string literal and
+no format arguments [-Werror=format-security]: add patch from Bart
+Martens (minus the change in Makefile.in) as debian/patches/643404.diff.
+Closes: #643404
+
+ -- gregor herrmann gre...@debian.org Sat, 15 Oct 2011 19:17:57 +0200
+
gyrus (0.3.10-1) unstable; urgency=low
* Imported Upstream version 0.3.10
only in patch2:
unchanged:
--- gyrus-0.3.10.orig/debian/patches/643404.diff
+++ gyrus-0.3.10/debian/patches/643404.diff
@@ -0,0 +1,73 @@
+diff -ruN -x '*.png' -x '*.jpg' -x '*.ogg' -x '*_image_archive' ../orig/gyrus-0.3.10/src/gyrus-admin.c ./src/gyrus-admin.c
+--- ../orig/gyrus-0.3.10/src/gyrus-admin.c 2010-12-29 01:31:16.0 +0100
./src/gyrus-admin.c 2011-10-04 04:31:06.0 +0200
+@@ -1471,11 +1471,11 @@
+ if (!duplicated) {
+ if (!gyrus_admin_acl_set_entry (admin, mailbox,
+ newname, rights, error)) {
+- g_warning (error);
++ g_warning (%s, error);
+ g_free (error);
+ } else if (!gyrus_admin_acl_delete_entry (admin, mailbox,
+ oldname, error)) {
+- g_warning (error);
++ g_warning (%s, error);
+ g_free (error);
+ } else {
+ gtk_list_store_set (GTK_LIST_STORE (model), iter,
+@@ -1486,16 +1486,16 @@
+ /* DELETE EXISTING ONE */
+ if (!gyrus_admin_acl_delete_entry (admin, mailbox,
+ newname, error)) {
+- g_warning (error);
++ g_warning (%s, error);
+ g_free (error);
+ } else if (!gyrus_admin_acl_set_entry (admin, mailbox,
+ newname, rights,
+ error)) {
+- g_warning (error);
++ g_warning (%s, error);
+ g_free (error);
+ } else if (!gyrus_admin_acl_delete_entry (admin, mailbox,
+ oldname, error)) {
+- g_warning (error);
++ g_warning (%s, error);
+ g_free (error);
+ } else {
+ /* All OK! */
+diff -ruN -x '*.png' -x '*.jpg' -x '*.ogg' -x '*_image_archive' ../orig/gyrus-0.3.10/src/gyrus-admin-mailbox.c ./src/gyrus-admin-mailbox.c
+--- ../orig/gyrus-0.3.10/src/gyrus-admin-mailbox.c 2010-12-29 00:57:44.0 +0100
./src/gyrus-admin-mailbox.c 2011-10-04 04:32:19.0 +0200
+@@ -163,7 +163,7 @@
+ /* sets the quota info in the screen */
+ if (quota_limit 0)
+ g_sprintf (str_quota_limit,
+- msg);
++ %s, msg);
+ else
+ gyrus_admin_mailbox_get_human_quota (quota_limit,
+ str_quota_limit);
+diff -ruN -x '*.png' -x '*.jpg' -x '*.ogg' -x '*_image_archive' ../orig/gyrus-0.3.10/src/gyrus-common.c ./src/gyrus-common.c
+--- ../orig/gyrus-0.3.10/src/gyrus-common.c 2010-12-29 00:52:13.0 +0100
./src/gyrus-common.c 2011-10-04 04:33:00.0 +0200
+@@ -36,7 +36,7 @@
+ GtkWidget *dialog;
+
+ dialog = gtk_message_dialog_new (parent, GTK_DIALOG_MODAL,
+- type, GTK_BUTTONS_OK, message);
++ type, GTK_BUTTONS_OK, %s, message);
+ gtk_dialog_run (GTK_DIALOG (dialog));
+ gtk_widget_destroy (dialog);
+ }
+diff -ruN -x '*.png' -x '*.jpg' -x '*.ogg' -x '*_image_archive' ../orig/gyrus-0.3.10/src/gyrus-session.c ./src/gyrus-session.c
+--- ../orig/gyrus-0.3.10/src/gyrus-session.c 2010-12-29 00:52:13.0 +0100
./src/gyrus-session.c 2011-10-04 04:31:16.0 +0200
+@@ -658,7 +658,7 @@
+ aux-sep_char = g_strdup (.);
+ else if (error) {
+ aux-sep_char = g_strdup (.);
+- g_warning (error-message);
++ g_warning (%s, error-message);
+ g_error_free (error);
+ }
+
signature.asc
Description: Digital signature
Processed: gyrus: diff for NMU version 0.3.10-1.1
Processing commands for cont...@bugs.debian.org: tags 643404 + pending Bug #643404 [src:gyrus] gyrus: FTBFS: gyrus-admin.c:1474:4: error: format not a string literal and no format arguments [-Werror=format-security] Added tag(s) pending. thanks Stopping processing here. Please contact me if you need assistance. -- 643404: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=643404 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#645704: orbit2 needs update in debian unstable
Package: orbit2 Version: 1:2.14.18-0.2 Severity: grave Tags: patch Am 17.10.2011 21:32, schrieb Andreas Henriksson: Hello! Alot of people (me included) are having problems with logging into gnome in unstable now that the 3.0 migration has started. (I was running 3.0 from experimental before and for some reason didn't have the problem there.weird.) When logging into gnome it says Oh no! A problem has occured. The system can not recover... because gnome-settings-daemon crashes. Anyway... I debugged my problem a bit and found that the same problem had previously been handled in ubuntu, please see: https://bugs.launchpad.net/ubuntu/+source/orbit2/+bug/788710 Apparently orbit2 is causing gnome-settings-daemon to crash, fixed by the patch mentioned in the above bug report and included in the ubuntu package (which also updates the package to a new upstream bugfix release which might not be a bad idea.) Would be awesome if you could have a look at updating the package in Debian! Let's turn this into a proper bug report. As this breaks unrelated packages, I'm filing with RC severity especially as this is a very often reported bug. Sebastian, in case you are busy we (the GNOME team) can prepare an NMU as we want to see this issue resolved as soon as possible. Please let us know what you prefer. If I don't hear back anything, I'd prepare an upload tomorrow and upload it to DELAYED/2. Cheers, Michael -- Why is it that all of the instruments seeking intelligent life in the universe are pointed away from Earth? signature.asc Description: OpenPGP digital signature
Bug#645475: autogen FTBFS: cannot find the library `/usr/lib/libgmp.la'
severity 645475 wishlist retitle 645475 libgmp-dev: please add Breaks against packages that used the .la file reopen 645475 tags 645475 + patch quit Jonathan Nieder wrote: I do think a Breaks would be a friendly thing to do (as usual when a package in sid causes a package in the stable to stop behaving as advertised). Incidentally, is there a reason for libgmp-dev to keep the .la file at all? Therefore reopening. -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed: Re: autogen FTBFS: cannot find the library `/usr/lib/libgmp.la'
Processing commands for cont...@bugs.debian.org:
severity 645475 wishlist
Bug #645475 {Done: Julien Cristau jcris...@debian.org} [libgmp-dev] autogen
FTBFS: cannot find the library `/usr/lib/libgmp.la'
Severity set to 'wishlist' from 'serious'
retitle 645475 libgmp-dev: please add Breaks against packages that used the
.la file
Bug #645475 {Done: Julien Cristau jcris...@debian.org} [libgmp-dev] autogen
FTBFS: cannot find the library `/usr/lib/libgmp.la'
Changed Bug title to 'libgmp-dev: please add Breaks against packages that used
the .la file' from 'autogen FTBFS: cannot find the library `/usr/lib/libgmp.la''
reopen 645475
Bug #645475 {Done: Julien Cristau jcris...@debian.org} [libgmp-dev]
libgmp-dev: please add Breaks against packages that used the .la file
tags 645475 + patch
Bug #645475 [libgmp-dev] libgmp-dev: please add Breaks against packages that
used the .la file
Added tag(s) patch.
quit
Stopping processing here.
Please contact me if you need assistance.
--
645475: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=645475
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#644592: mudlet: FTBFS (kfreebsd-i386): fatal error: Phonon: No such file or directory
On Fri, Oct 07, 2011 at 11:04:33AM +0200, Christoph Egger wrote: mudlet.h:42:22: fatal error: Phonon: No such file or directory It is because the code is checking for Q_OS_LINUX I have changed it to look if __GLIBC__ is defined. This is a common mistake of upstreams using qmake. - Craig -- Craig Small VK2XLZ http://enc.com.au/ csmall at : enc.com.au Debian GNU/Linux http://www.debian.org/ csmall at : debian.org old fingerprint: 1C1B D893 1418 2AF4 45EE 95CB C76C E5AC 12CA DFA5 NEW fingerprint: 5D2F B320 B825 D939 04D2 0519 3938 F96B DF50 FEA5 -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
