Bug#645469: bind fails for AF_UNIX sockets with EINVAL

[Petr Salinger]

Btw, could we restrict this kludge to platforms that need it?  See
attached patch.


I like the idea, slightly different patch is in.

Petr



--
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: Message: /usr/lib/libgle-graphics-4.2.2.so: cannot open shared object file: No such file or directory

[Petr Salinger]

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


The problem seems be in src/gle/file_io.cpp:

#if defined(__UNIX__) && !defined(__MACOS__) && !defined(__FREEBSD__)
/* try to read location from the /proc/self/exe file */
char path[PATH_MAX];
struct stat stat_buf;
string path2 = "/proc/self/exe";


There is a "/proc/self/exe" support under GNU/kFreeBSD, but it is 
limited, namely inside combination of bind mounts and chroots.

I bet that configuration of buildd have been changed in mean time.
In fact the /proc/self/exe file systems is linuxism.

Please try this:

--- src/gle/file_io.cpp
+++ src/gle/file_io.cpp
@@ -1334,7 +1334,7 @@
return true;
}
 #endif
-#if defined(__UNIX__) && !defined(__MACOS__) && !defined(__FREEBSD__)
+#if defined(__linux__)
/* try to read location from the /proc/self/exe file */
char path[PATH_MAX];
struct stat stat_buf;


Petr



--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Processed: With good package name this time

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> package src:gmpc
Limiting to bugs with field 'package' containing at least one of 'src:gmpc'
Limit currently set to 'package':'src:gmpc'

> tag 640311 + wheezy sid
Bug #640311 [src:gmpc] gmpc: FTBFS: gmpc.vapi:1.7-1.25: error: The namespace 
name `Gmpc.PanedSizeGroup' could not be found
Ignoring request to alter tags of bug #640311 to the same tags previously set
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
640311: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=640311
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#640311: Fix the link of the log.

[Etienne Millon]

package gmpc
tag 640311 + wheezy sid
thanks

* Etienne Millon  [111018 06:22]:
> This bug also affects squeeze. The fix is simple, however : by
> disabling patch 0005 I managed to build it in a squeeze chroot.

Hum, I was mistaken. I tried to build the sid version in a squeeze
chroot. The squeeze one is fine, so tagging accordingly.

-- 
Etienne Millon



-- 
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#635853: marked as done ([slapd] /var/lib/dpkg/info/slapd.prerm breaks removal of broken slapd)

[Debian Bug Tracking System]

Your message dated Tue, 18 Oct 2011 05:32:25 +
with message-id 
and subject line Bug#628237: fixed in openldap 2.4.25-4
has caused the Debian Bug report #628237,
regarding [slapd] /var/lib/dpkg/info/slapd.prerm  breaks removal of broken slapd
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.)


-- 
628237: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=628237
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: slapd
Severity: normal

--- Please enter the report below this line. ---
Bug 62837 has creeped into Wheezy.  Attempting to remove slapd is impossible 
without commenting out  the code in /var/lib/dpkg/info/slapd.prerm


--- System information. ---
Architecture: i386
Kernel:   Linux 2.6.39-2-686-pae

Debian Release: wheezy/sid
  500 testing www.debian-multimedia.org 
  500 testing security.debian.org 
  500 testing ftp.us.debian.org 

--- Package information. ---
Package's Depends field is empty.

Package's Recommends field is empty.

Package's Suggests field is empty.





--- End Message ---
--- Begin Message ---
Source: openldap
Source-Version: 2.4.25-4

We believe that the bug you reported is fixed in the latest version of
openldap, which is due to be installed in the Debian FTP archive:

ldap-utils_2.4.25-4_amd64.deb
  to main/o/openldap/ldap-utils_2.4.25-4_amd64.deb
libldap-2.4-2-dbg_2.4.25-4_amd64.deb
  to main/o/openldap/libldap-2.4-2-dbg_2.4.25-4_amd64.deb
libldap-2.4-2_2.4.25-4_amd64.deb
  to main/o/openldap/libldap-2.4-2_2.4.25-4_amd64.deb
libldap2-dev_2.4.25-4_amd64.deb
  to main/o/openldap/libldap2-dev_2.4.25-4_amd64.deb
openldap_2.4.25-4.diff.gz
  to main/o/openldap/openldap_2.4.25-4.diff.gz
openldap_2.4.25-4.dsc
  to main/o/openldap/openldap_2.4.25-4.dsc
slapd-dbg_2.4.25-4_amd64.deb
  to main/o/openldap/slapd-dbg_2.4.25-4_amd64.deb
slapd-smbk5pwd_2.4.25-4_amd64.deb
  to main/o/openldap/slapd-smbk5pwd_2.4.25-4_amd64.deb
slapd_2.4.25-4_amd64.deb
  to main/o/openldap/slapd_2.4.25-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 628...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Steve Langasek  (supplier of updated openldap 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 01:08:34 +
Source: openldap
Binary: slapd slapd-smbk5pwd ldap-utils libldap-2.4-2 libldap-2.4-2-dbg 
libldap2-dev slapd-dbg
Architecture: source amd64
Version: 2.4.25-4
Distribution: unstable
Urgency: low
Maintainer: Debian OpenLDAP Maintainers 

Changed-By: Steve Langasek 
Description: 
 ldap-utils - OpenLDAP utilities
 libldap-2.4-2 - OpenLDAP libraries
 libldap-2.4-2-dbg - Debugging information for OpenLDAP libraries
 libldap2-dev - OpenLDAP development libraries
 slapd  - OpenLDAP server (slapd)
 slapd-dbg  - Debugging information for the OpenLDAP server (slapd)
 slapd-smbk5pwd - Keeps Samba and Kerberos passwords in sync within slapd.
Closes: 327585 621403 628237 644274 644427
Changes: 
 openldap (2.4.25-4) unstable; urgency=low
 .
   * Drop explicit depends on libdb4.8, since we're now linking against
 libdb5.1.  Thanks to Peter Marschall for catching.  Closes: #621403
 again.
   * Rebuild against cyrus-sasl2 2.1.25.  Closes: #628237.
   * Use dh_autoreconf instead of a locally-patched autogen.sh.
   * debian/patches/no-AM_INIT_AUTOMAKE: don't use AM_INIT_AUTOMAKE macro
 when we aren't using automake.
   * Convert debian/rules to dh(1).
   * use DEB_CFLAGS_MAINT_APPEND with appropriate versioned dependency on
 debhelper and dpkg-dev, so we can pick up dpkg-buildflags for our
 policy-mandated flags - as well as our security-enhancing ones!
 Closes: #644427.
   * Also set hardening=+pie,+bindnow buildflags options for maximum
 security, since this is a security-sensitive daemon dealing with
 untrusted input.  Ubuntu has been building with these flags for a
 while via hardening-wrappers, so the change is presumed safe.
   * Drop debian/check_config.  The upstream configure script now enforces
 --with-cyrus-sasl, so there's no need for a second check.
   * debian/po/es.po: tweak an ambiguous string in the Spanish debconf
 translation, noticed in response to a 

Bug#627984: marked as done (Restrict versions of libsasl2-2 slapd depends on)

[Debian Bug Tracking System]

Your message dated Tue, 18 Oct 2011 05:32:25 +
with message-id 
and subject line Bug#628237: fixed in openldap 2.4.25-4
has caused the Debian Bug report #628237,
regarding Restrict versions of libsasl2-2 slapd depends on
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.)


-- 
628237: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=628237
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: slapd
Version: 2.4.25-1+b1
Severity: important
Tags: sid

slapd does not work with the latest version of libsasl2-2 in sid
(2.1.24~rc1.dfsg1-1):

slapd[2816]: @(#) $OpenLDAP: slapd 2.4.25 (May  3 2011 23:46:04) $
^Ibuildd@biber:/build/buildd-openldap_2.4.25-1+b1-i386-QCBDvS/openldap-2.4.25/debian/b
uild/servers/slapd  
slapd[2816]: slap_sasl_init: auxprop add plugin failed
slapd[2816]: slapd stopped.

Please add version information to the dependency on libsasl2-2
(<=2.1.13 should be fine)

-- System Information:
Debian Release: wheezy/sid
  APT prefers unstable
  APT policy: (500, 'unstable'), (500, 'testing'), (500, 'stable'), (1, 
'experimental')
Architecture: i386 (i686)

Kernel: Linux 2.6.39-1-686-pae (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 slapd depends on:
ii  adduser   3.112+nmu2 add and remove users and groups
ii  coreutils 8.5-1  GNU core utilities
ii  debconf [debconf-2.0] 1.5.39 Debian configuration management sy
ii  libc6 2.13-4 Embedded GNU C Library: Shared lib
ii  libdb4.8  4.8.30-8   Berkeley v4.8 Database Libraries [
ii  libgcrypt11   1.4.6-5LGPL Crypto library - runtime libr
ii  libgnutls26   2.10.5-1+b1the GNU TLS library - runtime libr
ii  libldap-2.4-2 2.4.25-1+b1OpenLDAP libraries
ii  libltdl7  2.4-2  A system independent dlopen wrappe
ii  libperl5.12   5.12.3-7   shared Perl library
ii  libsasl2-22.1.23.dfsg1-7 Cyrus SASL - authentication abstra
ii  libslp1   1.2.1-7.8  OpenSLP libraries
ii  libwrap0  7.6.q-19   Wietse Venema's TCP wrappers libra
ii  lsb-base  3.2-27 Linux Standard Base 3.2 init scrip
ii  perl [libmime-base64-perl 5.12.3-7   Larry Wall's Practical Extraction 
ii  psmisc22.13-1utilities that use the proc file s
ii  unixodbc  2.2.14p2-2 ODBC tools libraries

Versions of packages slapd recommends:
pn  libsasl2-modules   (no description available)

Versions of packages slapd suggests:
ii  ldap-utils   2.4.25-1+b1 OpenLDAP utilities

-- Configuration Files:
/etc/default/slapd changed [not included]

-- debconf information excluded


--- End Message ---
--- Begin Message ---
Source: openldap
Source-Version: 2.4.25-4

We believe that the bug you reported is fixed in the latest version of
openldap, which is due to be installed in the Debian FTP archive:

ldap-utils_2.4.25-4_amd64.deb
  to main/o/openldap/ldap-utils_2.4.25-4_amd64.deb
libldap-2.4-2-dbg_2.4.25-4_amd64.deb
  to main/o/openldap/libldap-2.4-2-dbg_2.4.25-4_amd64.deb
libldap-2.4-2_2.4.25-4_amd64.deb
  to main/o/openldap/libldap-2.4-2_2.4.25-4_amd64.deb
libldap2-dev_2.4.25-4_amd64.deb
  to main/o/openldap/libldap2-dev_2.4.25-4_amd64.deb
openldap_2.4.25-4.diff.gz
  to main/o/openldap/openldap_2.4.25-4.diff.gz
openldap_2.4.25-4.dsc
  to main/o/openldap/openldap_2.4.25-4.dsc
slapd-dbg_2.4.25-4_amd64.deb
  to main/o/openldap/slapd-dbg_2.4.25-4_amd64.deb
slapd-smbk5pwd_2.4.25-4_amd64.deb
  to main/o/openldap/slapd-smbk5pwd_2.4.25-4_amd64.deb
slapd_2.4.25-4_amd64.deb
  to main/o/openldap/slapd_2.4.25-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 628...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Steve Langasek  (supplier of updated openldap 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 01:08:34 +
Source: openldap
Binary: slapd slapd-smbk5pwd ldap-utils libldap-2.4-2 libldap-2.4-2-dbg 
libldap2-

Bug#628237: marked as done (slapd: installation fails: slap_sasl_init: auxprop add plugin failed)

[Debian Bug Tracking System]

Your message dated Tue, 18 Oct 2011 05:32:25 +
with message-id 
and subject line Bug#628237: fixed in openldap 2.4.25-4
has caused the Debian Bug report #628237,
regarding slapd: installation fails: slap_sasl_init: auxprop add plugin failed
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
628237: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=628237
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: slapd
Version: 2.4.25-1+b1
Severity: grave
Justification: renders package unusable


Daily Q/A build, Debian/unstable chroot:

[...]
Setting up slapd (2.4.25-1+b1) ...
  Creating new user openldap... done.
  Creating initial configuration... Loading the initial configuration from the 
ldif file () failed with
the following error while running slapadd:
slap_sasl_init: auxprop add plugin failed
slapadd: slap_init failed!
dpkg: error processing slapd (--configure):
 subprocess installed post-installation script returned error exit status 1
[...]

regards,
-mika-


--- End Message ---
--- Begin Message ---
Source: openldap
Source-Version: 2.4.25-4

We believe that the bug you reported is fixed in the latest version of
openldap, which is due to be installed in the Debian FTP archive:

ldap-utils_2.4.25-4_amd64.deb
  to main/o/openldap/ldap-utils_2.4.25-4_amd64.deb
libldap-2.4-2-dbg_2.4.25-4_amd64.deb
  to main/o/openldap/libldap-2.4-2-dbg_2.4.25-4_amd64.deb
libldap-2.4-2_2.4.25-4_amd64.deb
  to main/o/openldap/libldap-2.4-2_2.4.25-4_amd64.deb
libldap2-dev_2.4.25-4_amd64.deb
  to main/o/openldap/libldap2-dev_2.4.25-4_amd64.deb
openldap_2.4.25-4.diff.gz
  to main/o/openldap/openldap_2.4.25-4.diff.gz
openldap_2.4.25-4.dsc
  to main/o/openldap/openldap_2.4.25-4.dsc
slapd-dbg_2.4.25-4_amd64.deb
  to main/o/openldap/slapd-dbg_2.4.25-4_amd64.deb
slapd-smbk5pwd_2.4.25-4_amd64.deb
  to main/o/openldap/slapd-smbk5pwd_2.4.25-4_amd64.deb
slapd_2.4.25-4_amd64.deb
  to main/o/openldap/slapd_2.4.25-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 628...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Steve Langasek  (supplier of updated openldap 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 01:08:34 +
Source: openldap
Binary: slapd slapd-smbk5pwd ldap-utils libldap-2.4-2 libldap-2.4-2-dbg 
libldap2-dev slapd-dbg
Architecture: source amd64
Version: 2.4.25-4
Distribution: unstable
Urgency: low
Maintainer: Debian OpenLDAP Maintainers 

Changed-By: Steve Langasek 
Description: 
 ldap-utils - OpenLDAP utilities
 libldap-2.4-2 - OpenLDAP libraries
 libldap-2.4-2-dbg - Debugging information for OpenLDAP libraries
 libldap2-dev - OpenLDAP development libraries
 slapd  - OpenLDAP server (slapd)
 slapd-dbg  - Debugging information for the OpenLDAP server (slapd)
 slapd-smbk5pwd - Keeps Samba and Kerberos passwords in sync within slapd.
Closes: 327585 621403 628237 644274 644427
Changes: 
 openldap (2.4.25-4) unstable; urgency=low
 .
   * Drop explicit depends on libdb4.8, since we're now linking against
 libdb5.1.  Thanks to Peter Marschall for catching.  Closes: #621403
 again.
   * Rebuild against cyrus-sasl2 2.1.25.  Closes: #628237.
   * Use dh_autoreconf instead of a locally-patched autogen.sh.
   * debian/patches/no-AM_INIT_AUTOMAKE: don't use AM_INIT_AUTOMAKE macro
 when we aren't using automake.
   * Convert debian/rules to dh(1).
   * use DEB_CFLAGS_MAINT_APPEND with appropriate versioned dependency on
 debhelper and dpkg-dev, so we can pick up dpkg-buildflags for our
 policy-mandated flags - as well as our security-enhancing ones!
 Closes: #644427.
   * Also set hardening=+pie,+bindnow buildflags options for maximum
 security, since this is a security-sensitive daemon dealing with
 untrusted input.  Ubuntu has been building with these flags for a
 while via hardening-wrappers, so the change is presumed safe.
   * Drop debian/check_config.  The upstream configure script now enforces
 --with-cyrus-sasl, so there's no need for a second check.
   * debian/po/es.po: tweak an ambiguous string in the Spanish debconf
 translation, noticed in response to a submitted Catalan translation
   *

Bug#645469: bind fails for AF_UNIX sockets with EINVAL

[Robert Millan]

2011/10/17 Robert Millan :
> 2011/10/17 Petr Salinger :
>> I just commited r3740 and r3739, at least one have to be active
>> with r3735 kernel.

Btw, could we restrict this kludge to platforms that need it?  See
attached patch.

-- 
Robert Millan
Index: sys/un.h
===
--- sys/un.h	(revision 3741)
+++ sys/un.h	(working copy)
@@ -31,7 +31,9 @@
   {
 __SOCKADDR_COMMON (sun_);
 char sun_path[104];		/* Path name, the kernel restrict it to 104, */
+#if defined(__i386__) || defined(__amd64__)
 char __sun_user_compat[4];  /* but former user header used 108 */
+#endif
   };
 
 
Index: sa_len.c
===
--- sa_len.c	(revision 3741)
+++ sa_len.c	(working copy)
@@ -22,6 +22,7 @@
 #include 
 #include 
 #include 
+#include 
 
 int
 __libc_sa_len (sa_family_t af)
@@ -37,7 +38,7 @@
 case AF_IPX:
   return sizeof (struct sockaddr_ipx);
 case AF_LOCAL:
-  return sizeof (struct sockaddr_un) - sizeof(((struct sockaddr_un *) 0)->__sun_user_compat);
+  return offsetof (struct sockaddr_un, sun_path) + sizeof (((struct sockaddr_un *) 0)->sun_path);
 }
   return 0;
 }

Bug#637309: marked as done (nautilus-open-terminal: Please transition to nautilus 3)

[Debian Bug Tracking System]

Your message dated Tue, 18 Oct 2011 05:17:17 +
with message-id 
and subject line Bug#637309: fixed in nautilus-open-terminal 0.19-2
has caused the Debian Bug report #637309,
regarding nautilus-open-terminal: Please transition to nautilus 3
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.)


-- 
637309: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=637309
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: nautilus-open-terminal
Severity: important
User: pkg-gnome-maintain...@lists.alioth.debian.org
Usertags: nautilus3-transition

Hi,

the Debian GNOME team is preparing the upload of nautilus 3 to
unstable.

The API of libnautilus-extension hasn't changed, but it builds
against GTK 3 now which changes its ABI, so the binary package name
was changed to libnautilus-extension1a.

Linking to both GTK 2 and GTK 3 in the same process is not supported
[1] and applications will abort. As a result, updating your package
for nautilus 3 means updating it to GTK 3.

nautilus 3 / libnautilus-extension 3 packages are available from
experimental. Please update and test your package against this
version and ideally upload it to experimental, too. This way, when we
start the transition, the package can be moved to unstable more
easily.

On behalf of the Debian GNOME team,

Michael Biebl

[1] http://developer.gnome.org/gtk3/3.0/ch25s02.html#id1493823


--- End Message ---
--- Begin Message ---
Source: nautilus-open-terminal
Source-Version: 0.19-2

We believe that the bug you reported is fixed in the latest version of
nautilus-open-terminal, which is due to be installed in the Debian FTP archive:

nautilus-open-terminal_0.19-2.debian.tar.gz
  to main/n/nautilus-open-terminal/nautilus-open-terminal_0.19-2.debian.tar.gz
nautilus-open-terminal_0.19-2.dsc
  to main/n/nautilus-open-terminal/nautilus-open-terminal_0.19-2.dsc
nautilus-open-terminal_0.19-2_amd64.deb
  to main/n/nautilus-open-terminal/nautilus-open-terminal_0.19-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 637...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Julien Valroff  (supplier of updated nautilus-open-terminal 
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 07:00:45 +0200
Source: nautilus-open-terminal
Binary: nautilus-open-terminal
Architecture: source amd64
Version: 0.19-2
Distribution: unstable
Urgency: low
Maintainer: Emilien Klein 
Changed-By: Julien Valroff 
Description: 
 nautilus-open-terminal - nautilus plugin for opening terminals in arbitrary 
paths
Closes: 637309
Changes: 
 nautilus-open-terminal (0.19-2) unstable; urgency=low
 .
   * Upload to unstable (Closes: #637309)
   * Update to new policy 3.9.2 (no changes needed)
   * Update VCS fields
   * Use dh-autoreconf --as-needed option rather than patching ltmain.sh
   * Set Emilien Klein as maintainer, set myself as uploader
   * Use DPKG_EXPORT_BUILDFLAGS to ensure LDFLAGS is exported
   * Fix DEP-5 copyright syntax
Checksums-Sha1: 
 1c18047a80471ccbe894745a8a19355ba814 2239 nautilus-open-terminal_0.19-2.dsc
 8eeaf184634abaaf0038774e055aed00e7f1ed48 5458 
nautilus-open-terminal_0.19-2.debian.tar.gz
 4ec863e4207039aa9465e28558b8a29001fd92df 64554 
nautilus-open-terminal_0.19-2_amd64.deb
Checksums-Sha256: 
 7ef07b62d484d20df4f2cc457367c42339460cf2ed59b9821facf5407d792cf3 2239 
nautilus-open-terminal_0.19-2.dsc
 3e6e9fdf98f695948ac4cbee4c343e42729cadde312983594f76d7c8cf327d8e 5458 
nautilus-open-terminal_0.19-2.debian.tar.gz
 4f26c3b6184277bed8bdae345c5347ccc5cffafa1048a7c0f3802d0e42ef1589 64554 
nautilus-open-terminal_0.19-2_amd64.deb
Files: 
 5a12b76c89cb7678f935a62339fe8bf2 2239 gnome optional 
nautilus-open-terminal_0.19-2.dsc
 b7ffa4563b34ed2c2fa1ad744ae4adde 5458 gnome optional 
nautilus-open-terminal_0.19-2.debian.tar.gz
 de18b60f86bad90c299afdab0b9c5301 64554 gnome optional 
nautilus-open-terminal_0.19-2_amd64.deb

-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.11 (GNU/Linux)

iQIcBAEBCAAGBQJOnQiJAAoJEFHhprzRxas7SjAQAMrw80v2a14vEJK86iFW73Pd
QTYbxwYSl6sGU+ANMnn2S8K7VM0IDlH0yH7kJpHi4nmdhdHUkdUE6TN+arUbP4hX
ccL2wZui2SACGbnnq8rCFGfE5i7wVqmO1FBLcQF4M1BfuiBwGDfSAfp6zC91j390
VhTPqGyO+cb2UEyMp3Ypd+dQiOk9g

Bug#375252: partlibrary removed from unstable

[Scott Howard]

partlibrary has been removed, bug has been filed against
release.debian.org to remove it from squeeze and lenny

There has been some discussion about bringing it back as a contrib
package that downloads it from the Internet, but that is a little
shady since still no one has a license to distribute it.



-- 
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#375252: marked as done (partslibrary: license)

[Debian Bug Tracking System]

Your message dated Tue, 18 Oct 2011 00:22:15 -0400
with message-id 

and subject line partlibrary removed from unstable
has caused the Debian Bug report #375252,
regarding partslibrary: license
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.)


-- 
375252: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=375252
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: partlibrary
Version: 2.0.1.2-1-2

What is the license of partlibrary?
http://www.ribbonsoft.com/qcad_downloads.html


--- End Message ---
--- Begin Message ---
partlibrary has been removed, bug has been filed against
release.debian.org to remove it from squeeze and lenny

There has been some discussion about bringing it back as a contrib
package that downloads it from the Internet, but that is a little
shady since still no one has a license to distribute it.

--- End Message ---

Bug#645712: yaskkserv: FTBFS: cc1plus: error: unrecognized command line option '-march=native'

[Nobuhiro Iwamatsu]

Hi,

2011/10/18 Satoru KURASHIKI :
> hi,
>
> On Tue, Oct 18, 2011 at 10:21 AM, Nobuhiro Iwamatsu
>  wrote:
>> Because these architecture does not support "-march=native".
>> I made patch which revise this problem. Could you check and apply this patch?
>
> yes, and I plan to contact upstream to fix this (because configure script 
> seems
> to be broken) suggesting a patch as follows:
>
> --- configure.orig      2011-10-18 00:56:16.033903126 +0900
> +++ configure   2011-10-18 01:26:46.366979251 +0900
> @@ -298,9 +298,10 @@
>  }
>
>  {
> +    $_ = `uname -m 2>&1`;
>    my $common = '';
>    if (GccIsSupport($global{'gcc_version'}, 4, 2, 0)) {
> -       $common .= '-march=native';
> +       $common .= '-march=native' if /86/i;
>    } else {
>       $common .= '-march=k8' if /x86_64/i;
>    }
>
> Your patch removes this if-clause entirely, which drops optimize
> options even in x86 architecture. It seems to make a (little bit)
> drastic cut, doesn't it?

Well, '-march=native' option varies in an option of the optimization
by building environment.
For example, the following optimization is made when we use this
option in C2Q and C2D.

C2D:
 -march=core2 -mcx16 -msahf -mno-movbe -mno-aes -mno-pclmul
-mno-popcnt -mno-abm -mno-lwp -mno-fma -mno-fma4 -mno-xop -mno-bmi
-mno-tbm -mno-avx -mno-sse4.2 -mno-sse4.1 --param l1-cache-size=32
--param l1-cache-line-size=64 --param l2-cache-size=4096
-mtune=core2
C2Q:
 -march=core2 -mcx16 -msahf -mno-movbe -mno-aes -mno-pclmul
-mno-popcnt -mno-abm -mno-lwp -mno-fma -mno-fma4 -mno-xop -mno-bmi
-mno-tbm -mno-avx -mno-sse4.2 -msse4.1 --param l1-cache-size=32
--param l1-cache-line-size=64 --param l2-cache-size=3072
-mtune=core2

When a binary optimized by the latest CPU is built, user may not work
with the old CPU.

Best regards,
  Nobuhiro

-- 
Nobuhiro Iwamatsu
   iwamatsu at {nigauri.org / debian.org}
   GPG ID: 40AD1FA6



--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#642276: marked as done (openrocket: Openrocket crashes on startup)

[Debian Bug Tracking System]

Your message dated Tue, 18 Oct 2011 03:47:13 +
with message-id 
and subject line Bug#642276: fixed in openrocket 1.1.8-2
has caused the Debian Bug report #642276,
regarding openrocket: Openrocket crashes on startup
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.)


-- 
642276: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=642276
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: openrocket
Version: 1.1.8-1
Severity: grave
Justification: renders package unusable


The startup banner appears and is replaced by an exception window.  This
vanishes when I click "View bug report".  The process then hangs until I
hit ^C.  The error output is included below. 


  13  0.866 ERROR (ExceptionHandler.java:48) Handling uncaught exception on 
thread=Thread[main,5,main]
   > java.lang.reflect.InvocationTargetException
   >at java.awt.EventQueue.invokeAndWait(EventQueue.java:1045)
   >at javax.swing.SwingUtilities.invokeAndWait(SwingUtilities.java:1347)
   >at net.sf.openrocket.startup.Startup.main(Startup.java:89)
   > Caused by: java.lang.ExceptionInInitializerError
   >at 
com.sun.imageio.plugins.png.PNGImageReader.getImageTypes(PNGImageReader.java:1496)
   >at 
com.sun.imageio.plugins.png.PNGImageReader.readImage(PNGImageReader.java:1282)
   >at 
com.sun.imageio.plugins.png.PNGImageReader.read(PNGImageReader.java:1579)
   >at javax.imageio.ImageIO.read(ImageIO.java:1438)
   >at javax.imageio.ImageIO.read(ImageIO.java:1342)
   >at net.sf.openrocket.util.GUIUtil.loadImage(GUIUtil.java:96)
   >at net.sf.openrocket.util.GUIUtil.(GUIUtil.java:81)
   >at net.sf.openrocket.startup.Startup.runMain(Startup.java:179)
   >at net.sf.openrocket.startup.Startup.access$000(Startup.java:52)
   >at net.sf.openrocket.startup.Startup$1.run(Startup.java:92)
   >at java.awt.event.InvocationEvent.dispatch(InvocationEvent.java:216)
   >at java.awt.EventQueue.dispatchEventImpl(EventQueue.java:647)
   >at java.awt.EventQueue.access$000(EventQueue.java:96)
   >at java.awt.EventQueue$1.run(EventQueue.java:608)
   >at java.awt.EventQueue$1.run(EventQueue.java:606)
   >at java.security.AccessController.doPrivileged(Native Method)
   >at 
java.security.AccessControlContext$1.doIntersectionPrivilege(AccessControlContext.java:105)
   >at java.awt.EventQueue.dispatchEvent(EventQueue.java:617)
   >at 
java.awt.EventDispatchThread.pumpOneEventForFilters(EventDispatchThread.java:275)
   >at 
java.awt.EventDispatchThread.pumpEventsForFilter(EventDispatchThread.java:200)
   >at 
java.awt.EventDispatchThread.pumpEventsForHierarchy(EventDispatchThread.java:190)
   >at java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:185)
   >at java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:177)
   >at java.awt.EventDispatchThread.run(EventDispatchThread.java:138)
   > Caused by: java.lang.IllegalArgumentException: Can't load standard 
profile: GRAY.pf
   >at java.awt.color.ICC_Profile$2.run(ICC_Profile.java:912)
   >at java.security.AccessController.doPrivileged(Native Method)
   >at java.awt.color.ICC_Profile.getStandardProfile(ICC_Profile.java:905)
   >at java.awt.color.ICC_Profile.getInstance(ICC_Profile.java:876)
   >at java.awt.color.ColorSpace.getInstance(ColorSpace.java:333)
   >at 
javax.imageio.ImageTypeSpecifier$Grayscale.(ImageTypeSpecifier.java:717)
   >at 
javax.imageio.ImageTypeSpecifier.createGrayscale(ImageTypeSpecifier.java:798)
   >at 
javax.imageio.ImageTypeSpecifier.(ImageTypeSpecifier.java:157)
   >... 24 more
java.lang.reflect.InvocationTargetException
at java.awt.EventQueue.invokeAndWait(EventQueue.java:1045)
at javax.swing.SwingUtilities.invokeAndWait(SwingUtilities.java:1347)
at net.sf.openrocket.startup.Startup.main(Startup.java:89)
Caused by: java.lang.ExceptionInInitializerError
at 
com.sun.imageio.plugins.png.PNGImageReader.getImageTypes(PNGImageReader.java:1496)
at 
com.sun.imageio.plugins.png.PNGImageReader.readImage(PNGImageReader.java:1282)
at 
com.sun.imageio.plugins.png.PNGImageReader.read(PNGImageReader.java:1579)
at javax.imageio.ImageIO.read(ImageIO.java:1438)
at javax.imageio.ImageIO.read(ImageIO.java:1342)
at net.sf.openrocket.util.GUIUtil.loadImage(GUIUtil.java:96)
at net.sf.openrocket.util.GUIUtil.(GUIUtil.java:81)
at net.sf.openrocket.startup.Startup.runMain(Startup.java:179)
at net.sf.openrocket.startup.Startup.access$000(Startup.

Bug#645712: yaskkserv: FTBFS: cc1plus: error: unrecognized command line option '-march=native'

[Satoru KURASHIKI]

hi,

On Tue, Oct 18, 2011 at 10:21 AM, Nobuhiro Iwamatsu
 wrote:
> Because these architecture does not support "-march=native".
> I made patch which revise this problem. Could you check and apply this patch?

yes, and I plan to contact upstream to fix this (because configure script seems
to be broken) suggesting a patch as follows:

--- configure.orig  2011-10-18 00:56:16.033903126 +0900
+++ configure   2011-10-18 01:26:46.366979251 +0900
@@ -298,9 +298,10 @@
 }

 {
+$_ = `uname -m 2>&1`;
my $common = '';
if (GccIsSupport($global{'gcc_version'}, 4, 2, 0)) {
-   $common .= '-march=native';
+   $common .= '-march=native' if /86/i;
} else {
   $common .= '-march=k8' if /x86_64/i;
}

Your patch removes this if-clause entirely, which drops optimize
options even in x86 architecture. It seems to make a (little bit)
drastic cut, doesn't it?

regards,
-- 
KURASHIKI Satoru



-- 
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Processed: dar-static removed

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> unblock 637991 by 632889
Bug #637991 {Done: Brian May } [dar] dar reports "SECURITY 
WARNING! SUSPICIOUS FILE" when using old archive files
Was blocked by: 632889
Removed blocking bug(s) of 637991: 632889
> unblock 637997 by 632889
Bug #637997 {Done: Brian May } [dar] dar: Error "Dates of 
file's data are not increasing when database's archive number grows"
Was blocked by: 632889
Removed blocking bug(s) of 637997: 632889
> unblock 638017 by 632889
Bug #638017 {Done: Brian May } [dar] missing strong encryption 
support
Was blocked by: 632889
Removed blocking bug(s) of 638017: 632889
> unblock 639206 by 632889
Bug #639206 {Done: Brian May } [dar] [dar] Missing lzo 
compression support
Was blocked by: 632889
Removed blocking bug(s) of 639206: 632889
> unblock 639417 by 632889
Bug #639417 {Done: Brian May } [dar] dar: not compiled with 
libgcrypt; --hash fails
Was blocked by: 632889
Removed blocking bug(s) of 639417: 632889
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
639417: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=639417
638017: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=638017
637991: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=637991
639206: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=639206
637997: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=637997
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems


-- 
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Processed: Re: Bug#645704: Acknowledgement (orbit2 needs update in debian unstable)

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> tags 645704 + pending
Bug #645704 [orbit2] orbit2 needs update in debian unstable
Added tag(s) pending.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
645704: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=645704
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems


-- 
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Processed: forcibly merging 645047 645086 645038

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> forcemerge 645047 645086 645038
Bug#645047: bison fails to upgrade, file conflict between libbison-dev and 
liby-dev
Bug#645038: libbison-dev: undeclared file conflict with liby-dev 1:2.5.dfsg-1
Bug#645086: libbison-dev: trying to overwrite '/usr/lib/i386-linux-gnu/liby.a', 
which is also in package liby-dev 1:2.5.dfsg-1
Forcibly Merged 645038 645047 645086.

> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
645038: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=645038
645047: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=645047
645086: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=645086
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#642276: Openrocket crashes on startup

[Bdale Garbee]

On Mon, 17 Oct 2011 20:33:22 -0500, John Hasler  wrote:
> I don't have time to work on it but it should be an easy fix.

Thanks for letting me know!  

I keep forgetting to update the runtime deps, guess I'm just spoiled by
how well that works with dh_shlibdeps for C apps, etc.

Bdale


pgpzatqP8hVIE.pgp
Description: PGP signature

Bug#642276: Openrocket crashes on startup

[John Hasler]

Downloaded the source package (apt-get source) and built it (dpkg -us
-uc -r) and installed it.  Works.  Reinstalled package from archive.  It
works now too (except for a minor bug in the file menu).  Pulling in the
build-depends upgraded some libraries: looks like one of the depends
needs to require a more recent version.  I don't have time to work on it
but it should be an easy fix.
-- 
John Hasler 
jhas...@newsguy.com
Elmwood, WI USA



-- 
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#645712: yaskkserv: FTBFS: cc1plus: error: unrecognized command line option '-march=native'

[Nobuhiro Iwamatsu]

Source: yaskkserv
Version:  0.5.0-2
Severity: serious
Justification: fails to build from source
Tags: patch

Hi,

yaskkserv FTBFS on some architecture.
  https://buildd.debian.org/status/package.php?p=yaskkserv

-
g++  -D YASKKSERV_ARCHITECTURE_BSD_CYGWIN_LINUX_GCC -D
YASKKSERV_ARCHITECTURE_BYTE_ORDER_VAX  -D
YASKKSERV_CONFIG_ENABLE_SYSLOG -D
YASKKSERV_CONFIG_ENABLE_ERROR_MESSAGE -D
YASKKSERV_CONFIG_ENABLE_GOOGLE_JAPANESE_INPUT -D
YASKKSERV_CONFIG_HEADER_HAVE_ICONV_H -D
YASKKSERV_CONFIG_HEADER_HAVE_SYS_VFS_H -D
YASKKSERV_CONFIG_HEADER_HAVE_MNTENT_H -D
YASKKSERV_CONFIG_MACRO_HAVE_SYMBOL_MSG_NOSIGNAL -I . -I
/build/buildd-yaskkserv_0.5.0-2-powerpc-qCSnXF/yaskkserv-0.5.0/var/bsd_cygwin_linux_gcc/release
-I /build/buildd-yaskkserv_0.5.0-2-powerpc-qCSnXF/yaskkserv-0.5.0/source/skk
-I 
/build/buildd-yaskkserv_0.5.0-2-powerpc-qCSnXF/yaskkserv-0.5.0/source/skk/architecture
-I 
/build/buildd-yaskkserv_0.5.0-2-powerpc-qCSnXF/yaskkserv-0.5.0/source/skk/architecture/bsd_cygwin_linux_gcc
  -fno-exceptions -fno-rtti -fmessage-length=0 -pipe -fPIC -D
YASKKSERV_VERSION=\"0.5.0\" -march=native -Os -Wabi -Wcomments
-Wctor-dtor-privacy -Wdeprecated -Wendif-labels -Wfloat-equal
-Wformat-extra-args -Wformat-nonliteral -Wformat-security -Wformat-y2k
-Wimport -Winvalid-pch -Wmissing-include-dirs -Wmultichar -Wpragmas
-Wredundant-decls -Wundef -Wunused-macros -Wvariadic-macros
-Winvalid-offsetof -Wnon-template-friend -Wpmf-conversions
-Wstrict-null-sentinel -Wall -Wextra -W -Weffc++ -Wold-style-cast
-Woverloaded-virtual -Wsign-promo -Wsynth -Wundef -Wshadow
-Wlarger-than-16384 -Wpointer-arith -Wcast-qual -Wcast-align
-Wconversion -Wsign-compare -Waggregate-return -Wmissing-noreturn
-Wredundant-decls -Wnon-virtual-dtor -Wreorder -Wswitch-default
-Wswitch-enum -c yaskkserv_simple.cpp -o
/build/buildd-yaskkserv_0.5.0-2-powerpc-qCSnXF/yaskkserv-0.5.0/var/bsd_cygwin_linux_gcc/release/yaskkserv_simple/yaskkserv_simple.o
cc1plus: error: unrecognized command line option '-march=native'
make[3]: *** 
[/build/buildd-yaskkserv_0.5.0-2-powerpc-qCSnXF/yaskkserv-0.5.0/var/bsd_cygwin_linux_gcc/release/yaskkserv_simple/yaskkserv_simple.o]
Error 1
make[2]: *** [all] Error 2
make[1]: *** [all] Error 2
make[1]: Leaving directory
`/build/buildd-yaskkserv_0.5.0-2-powerpc-qCSnXF/yaskkserv-0.5.0'
make: *** [build-stamp] Error 2
-

Because these architecture does not support "-march=native".
I made patch which revise this problem. Could you check and apply this patch?

Best regards,
 Nobuhiro

-- 
Nobuhiro Iwamatsu
   iwamatsu at {nigauri.org / debian.org}
   GPG ID: 40AD1FA6


yaskkserv_0.5.0-2.1.diff.1rdTsK
Description: Binary data

Bug#645542: Acknowledgement (libpanel-applet transition: Please remove deskbar-plugins-pinot package)

[Michael Biebl]

tags 645542 + patch pending
thanks

Hi Jonas,

I've prepared an NMU for pinot dropping the deskbar-plugins-pinot package. As
we build a single package now, cdbs will install into debian/$(pkg) by
default, so I dropped the usage of --destdir=debian/tmp and pinot.install and
simply remove from pinot what's not needed.

As this bug blocks the ongoing GNOME 3 transition, I've uploaded it to
DELAYED/2. Please let me know if I should delay it further or if the patch is
otherwise not acceptable and I should cancel the NMU.

Cheers,
Michael

-- 
Why is it that all of the instruments seeking intelligent life in the
universe are pointed away from Earth?
diff -Nru pinot-0.96/debian/changelog pinot-0.96/debian/changelog
--- pinot-0.96/debian/changelog	2010-12-15 17:30:18.0 +0100
+++ pinot-0.96/debian/changelog	2011-10-18 02:41:18.0 +0200
@@ -1,3 +1,11 @@
+pinot (0.96-1.1) unstable; urgency=low
+
+  * Non-maintainer upload.
+  * Drop deskbar-plugins-pinot package as deskbar-applet has been removed.
+Closes: #645542
+
+ -- Michael Biebl   Tue, 18 Oct 2011 00:53:07 +0200
+
 pinot (0.96-1) unstable; urgency=low
 
   * New upstream release.
diff -Nru pinot-0.96/debian/control pinot-0.96/debian/control
--- pinot-0.96/debian/control	2010-12-15 17:30:26.0 +0100
+++ pinot-0.96/debian/control	2011-10-18 02:39:45.0 +0200
@@ -33,7 +33,7 @@
 Package: pinot
 Architecture: any
 Depends: ${shlibs:Depends}, ${misc:Depends}, dbus-x11
-Suggests: deskbar-plugins-pinot, antiword, catdoc, catdvi, djvulibre-bin, 
+Suggests: antiword, catdoc, catdvi, djvulibre-bin, 
  poppler-utils | xpdf-utils, rpm, unrtf, unzip
 Description: meta-search engine for local files and web queries
  Pinot provides a D-Bus service that crawls, indexes your documents and
@@ -44,20 +44,3 @@
  .
  Pinot also provides a Xesam interface, which can be used through Xesam Query
  Language and Xesam User Language.
-
-Package: deskbar-plugins-pinot
-Architecture: all
-Depends: ${python:Depends}, ${misc:Depends}, deskbar-applet (>= 2.20), 
- pinot, python-gnome2, python-gobject, python-dbus
-Description: deskbar plugin to search files with pinot
- Pinot provides a D-Bus service that crawls, indexes your documents and
- monitors them for changes. This service can then be used via a command-line
- interface, or through a GTK-based GUI that enables to query the index built
- by the service and your favourite Web engines, and display and analyze the
- results.
- .
- Pinot also provides a Xesam interface, which can be used through Xesam Query
- Language and Xesam User Language.
- .
- This package provides a plugin for the GNOME Deskbar applet to search for
- files using Pinot.
diff -Nru pinot-0.96/debian/control.in pinot-0.96/debian/control.in
--- pinot-0.96/debian/control.in	2010-12-15 17:29:27.0 +0100
+++ pinot-0.96/debian/control.in	2011-10-18 02:39:45.0 +0200
@@ -11,7 +11,7 @@
 Package: pinot
 Architecture: any
 Depends: ${shlibs:Depends}, ${misc:Depends}, dbus-x11
-Suggests: deskbar-plugins-pinot, antiword, catdoc, catdvi, djvulibre-bin, 
+Suggests: antiword, catdoc, catdvi, djvulibre-bin, 
  poppler-utils | xpdf-utils, rpm, unrtf, unzip
 Description: meta-search engine for local files and web queries
  Pinot provides a D-Bus service that crawls, indexes your documents and
@@ -22,20 +22,3 @@
  .
  Pinot also provides a Xesam interface, which can be used through Xesam Query
  Language and Xesam User Language.
-
-Package: deskbar-plugins-pinot
-Architecture: all
-Depends: ${python:Depends}, ${misc:Depends}, deskbar-applet (>= 2.20), 
- pinot, python-gnome2, python-gobject, python-dbus
-Description: deskbar plugin to search files with pinot
- Pinot provides a D-Bus service that crawls, indexes your documents and
- monitors them for changes. This service can then be used via a command-line
- interface, or through a GTK-based GUI that enables to query the index built
- by the service and your favourite Web engines, and display and analyze the
- results.
- .
- Pinot also provides a Xesam interface, which can be used through Xesam Query
- Language and Xesam User Language.
- .
- This package provides a plugin for the GNOME Deskbar applet to search for
- files using Pinot.
diff -Nru pinot-0.96/debian/deskbar-plugins-pinot.dirs pinot-0.96/debian/deskbar-plugins-pinot.dirs
--- pinot-0.96/debian/deskbar-plugins-pinot.dirs	2009-05-10 14:24:38.0 +0200
+++ pinot-0.96/debian/deskbar-plugins-pinot.dirs	1970-01-01 01:00:00.0 +0100
@@ -1 +0,0 @@
-/usr/lib/deskbar-applet/modules-2.20-compatible/
diff -Nru pinot-0.96/debian/deskbar-plugins-pinot.install pinot-0.96/debian/deskbar-plugins-pinot.install
--- pinot-0.96/debian/deskbar-plugins-pinot.install	2009-05-10 14:24:38.0 +0200
+++ pinot-0.96/debian/deskbar-plugins-pinot.install	1970-01-01 01:00:00.0 +0100
@@ -1 +0,0 @@
-usr/lib/deskbar-applet/modules-2.20-compatible/pinot-module.py
diff -Nru pinot-0.96/debian/pinot.install pinot-0.96/debian/pinot.install
--- p

Processed: Re: Bug#645542: Acknowledgement (libpanel-applet transition: Please remove deskbar-plugins-pinot package)

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> tags 645542 + patch pending
Bug #645542 [deskbar-plugins-pinot] libpanel-applet transition: Please remove 
deskbar-plugins-pinot package
Added tag(s) pending and patch.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
645542: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=645542
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#638135: marked as done (python-gnomeapplet: binary should be removed)

[Debian Bug Tracking System]

Your message dated Tue, 18 Oct 2011 00:17:31 +
with message-id 
and subject line Bug#638135: fixed in gnome-python-desktop 2.32.0-4
has caused the Debian Bug report #638135,
regarding python-gnomeapplet: binary should be 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.)


-- 
638135: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=638135
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: python-gnomeapplet
Version: 2.32.0-1
Severity: important
User: pkg-gnome-maintain...@lists.alioth.debian.org
Usertags: applets-transition

This is a reminder bug for dropping python-gnomeapplet, since it is
replaced by gir1.2-panelapplet-4.0, when the fate of all Python applets
has been decided:
http://deb.li/panel3 

-- 
 .''`.  Josselin Mouette
: :' :
`. `'
  `-




signature.asc
Description: This is a digitally signed message part
--- End Message ---
--- Begin Message ---
Source: gnome-python-desktop
Source-Version: 2.32.0-4

We believe that the bug you reported is fixed in the latest version of
gnome-python-desktop, which is due to be installed in the Debian FTP archive:

gnome-python-desktop_2.32.0-4.debian.tar.gz
  to main/g/gnome-python-desktop/gnome-python-desktop_2.32.0-4.debian.tar.gz
gnome-python-desktop_2.32.0-4.dsc
  to main/g/gnome-python-desktop/gnome-python-desktop_2.32.0-4.dsc
python-evolution_2.32.0-4_i386.deb
  to main/g/gnome-python-desktop/python-evolution_2.32.0-4_i386.deb
python-gnome2-desktop-dev_2.32.0-4_all.deb
  to main/g/gnome-python-desktop/python-gnome2-desktop-dev_2.32.0-4_all.deb
python-gnomedesktop_2.32.0-4_i386.deb
  to main/g/gnome-python-desktop/python-gnomedesktop_2.32.0-4_i386.deb
python-gnomekeyring_2.32.0-4_i386.deb
  to main/g/gnome-python-desktop/python-gnomekeyring_2.32.0-4_i386.deb
python-gtop_2.32.0-4_i386.deb
  to main/g/gnome-python-desktop/python-gtop_2.32.0-4_i386.deb
python-metacity_2.32.0-4_i386.deb
  to main/g/gnome-python-desktop/python-metacity_2.32.0-4_i386.deb
python-rsvg_2.32.0-4_i386.deb
  to main/g/gnome-python-desktop/python-rsvg_2.32.0-4_i386.deb
python-totem-plparser_2.32.0-4_i386.deb
  to main/g/gnome-python-desktop/python-totem-plparser_2.32.0-4_i386.deb
python-wnck_2.32.0-4_i386.deb
  to main/g/gnome-python-desktop/python-wnck_2.32.0-4_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 638...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Michael Biebl  (supplier of updated gnome-python-desktop 
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 01:34:12 +0200
Source: gnome-python-desktop
Binary: python-gnome2-desktop-dev python-evolution python-gnomedesktop 
python-gnomekeyring python-gtop python-metacity python-rsvg 
python-totem-plparser python-wnck
Architecture: source all i386
Version: 2.32.0-4
Distribution: unstable
Urgency: low
Maintainer: Loic Minier 
Changed-By: Michael Biebl 
Description: 
 python-evolution - Python bindings for the evolution libraries
 python-gnome2-desktop-dev - Python bindings for the GNOME desktop environment
 python-gnomedesktop - Python bindings for the GNOME desktop library
 python-gnomekeyring - Python bindings for the GNOME keyring library
 python-gtop - Python bindings for the Gtop library
 python-metacity - Python bindings for metacity
 python-rsvg - Python bindings for the RSVG library
 python-totem-plparser - Python bindings for the Totem playlist parser library
 python-wnck - Python bindings for the WNCK library
Closes: 638135
Changes: 
 gnome-python-desktop (2.32.0-4) unstable; urgency=low
 .
   * Drop python-gnomeapplet. It has been replaced by gir1.2-panelapplet-4.0
 and PyGObject. Closes: #638135
   * Add Build-Depends on gnome-common, required for autoreconf.
Checksums-Sha1: 
 c36b80aa6c58c1f974efd901451211df31fa4aa3 3198 gnome-python-desktop_2.32.0-4.dsc
 946c0d8b2443ea8392f2d9268f1c1d3f959ed0dd 9233 
gnome-python-desktop_2.32.0-4.debian.tar.gz
 48cf22fa10bc06c0ceb76b716b61435030397b63 52966 
python-gnome2-desktop-dev_2.32.0-4_all.deb
 c99959846592c3d1c93ba7feba2c2d7af52d1eb6 100260 
python-evolution_2.32.0-4_i386.deb
 584062173c5fbacbee57c510da3f753ff073b620 47394 
python-gnomedesktop_2.32.0-4_i386.deb
 a3ab852ad4538ce0bf9

Processed: re: FTBFS: error: 'gdk_display' undeclared (first use in this function)

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> # Switch tag squeeze (shouldn't be affected) and switch tag wheezy
> # (should be affected)
> tags 638991 - squeeze, wheezy
Bug #638991 {Done: Andreas Rönnquist } [devilspie] FTBFS: 
error: 'gdk_display' undeclared (first use in this function)
Removed tag(s) squeeze.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
638991: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=638991
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

[Craig Small]

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

Processed: Re: autogen FTBFS: cannot find the library `/usr/lib/libgmp.la'

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> severity 645475 wishlist
Bug #645475 {Done: Julien Cristau } [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 } [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 } [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#645475: autogen FTBFS: cannot find the library `/usr/lib/libgmp.la'

[Jonathan Nieder]

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

Bug#645704: orbit2 needs update in debian unstable

[Michael Biebl]

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

Processed: gyrus: diff for NMU version 0.3.10-1.1

[Debian Bug Tracking System]

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#643404: gyrus: diff for NMU version 0.3.10-1.1

[gregor herrmann]

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: Page&Plant: 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   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

Bug#645697: marked as done (sqlalchemy: FTBFS: /bin/sh: 1: sphinx-build: not found)

[Debian Bug Tracking System]

Your message dated Mon, 17 Oct 2011 22:18:15 +
with message-id 
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
--- Begin Message ---
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=sqlalchemy&arch=kfreebsd-amd64&ver=0.7.3-1&stamp=1318887428

Regards

Christoph

-- 
9FED 5C6C E206 B70A 5857  70CA 9655 22B9 D49A E731
Debian Developer | Lisp Hacker | CaCert Assurer


--- End Message ---
--- Begin Message ---
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  (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 
Changed-By: Piotr Ożarowski 
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: 
 cf4eedd26b3942abe4145fa58b1e3141 2375 python optional sqlalchemy_0.7.3-2.dsc
 2eeca777

Bug#645698: kbuild: FTBFS: undefined reference to `pthread_getspecific'

[Christoph Egger]

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=kbuild&arch=kfreebsd-i386&ver=1%3A0.1.9998svn2543-1&stamp=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: sqlalchemy: FTBFS: /bin/sh: 1: sphinx-build: not found

[Christoph Egger]

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=sqlalchemy&arch=kfreebsd-amd64&ver=0.7.3-1&stamp=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#628843: Ping

[Nicolas François]

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#644711: marked as done (iceweasel-vimperator: not compatible with iceweasel from testing/sid (7.0.1))

[Debian Bug Tracking System]

Your message dated Mon, 17 Oct 2011 21:19:23 +
with message-id 
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
--- Begin Message ---
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 
  | 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 ---
--- Begin Message ---
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  (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 
Changed-By: Francois Marier 
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#644031: marked as done (rtorrent: Uninstallable in sid due to missing libtorrent14 package)

[Debian Bug Tracking System]

Your message dated Mon, 17 Oct 2011 21:17:41 +
with message-id 
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
--- Begin Message ---
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 ---
--- Begin Message ---
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  (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 
Changed-By: Rogério Brito 
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#645681: marked as done (urwid 1.0.0 breaks wicd-curses)

[Debian Bug Tracking System]

Your message dated Mon, 17 Oct 2011 21:07:03 +
with message-id 
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
--- Begin Message ---
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 p

Bug#634051: marked as done (wicd-daemon: Fails to install/upgrade if existing user is removed)

[Debian Bug Tracking System]

Your message dated Mon, 17 Oct 2011 21:07:03 +
with message-id 
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
--- Begin Message ---
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   (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
nOhV5iwvQRICUTg04MJfCFYcV8aCvzEEva0bdlA1TQzkyUgPbdyxX3yJRVjzAy5X
+iYtyQyLw

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

[Christian T. Steigies]

On Fri, Oct 07, 2011 at 11:33:33PM +0200, Christoph Egger wrote:
> Hi!
> 
> "Christian T. Steigies"  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-graphics&arch=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

Processed: retitle 638112 to RM: libgail-gnome -- ROM; dead upstream, uninstallable

[Debian Bug Tracking System]

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

Processed: Re: Bug#645681: wicd-curses crashes on any keystroke

[Debian Bug Tracking System]

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

Bug#645681: wicd-curses crashes on any keystroke

[David Paleino]

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

Bug#645612: marked as done (libopenscap1 and libopenscap0: error when trying to install together)

[Debian Bug Tracking System]

Your message dated Mon, 17 Oct 2011 19:48:59 +
with message-id 
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
--- Begin Message ---
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/apac

Bug#645527: marked as done (bind() fails for AF_UNIX sockets with EINVAL)

[Debian Bug Tracking System]

Your message dated Mon, 17 Oct 2011 19:48:39 +
with message-id 
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
--- Begin Message ---
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 ---
--- Begin Message ---
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  (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 
Changed-By: Robert Millan 
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 kernel of FreeBSD 8.2
 kfreebsd-headers-8.2-1-686-smp - header files for kernel of Fr

Bug#642836: Bug#577704: Confirming bug in libsurefire-java

[Torsten Werner]

On Fri, Oct 14, 2011 at 4:23 PM, Damien Raude-Morvan
 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

Processed (with 1 errors): tagging as pending bugs that are closed by packages in NEW

[Debian Bug Tracking System]

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#645612: libopenscap1 and libopenscap0: error when trying to install together

[Pierre Chifflier]

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

Bug#645681: wicd-curses crashes on any keystroke

[Jonathan Lane]

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#645537: i386 specific

[Jerome Robert]

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#625581: Info received (Trying to fix API changes)

[Sebastian Ramacher]

Hello,

On 10/17/2011 08:04 PM, Vincent Fourmond wrote:
> On Mon, Oct 17, 2011 at 7:44 PM, Sebastian Ramacher  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#625581: Info received (Trying to fix API changes)

[Vincent Fourmond]

  Hello,

On Mon, Oct 17, 2011 at 7:44 PM, Sebastian Ramacher  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

Processed: severity of 643604 is serious

[Debian Bug Tracking System]

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#645469: bind fails for AF_UNIX sockets with EINVAL

[Robert Millan]

2011/10/17 Petr Salinger :
> 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

Bug#638119: marked as done (giplet: needs porting to new libpanel-applet interface)

[Debian Bug Tracking System]

Your message dated Mon, 17 Oct 2011 17:47:51 +
with message-id 
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
--- Begin Message ---
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 ---
--- Begin Message ---
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#625581: Info received (Trying to fix API changes)

[Sebastian Ramacher]

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#638101: marked as done (RM: window-picker-applet -- RoQA, dead upstream, uninstallable, low popcon)

[Debian Bug Tracking System]

Your message dated Mon, 17 Oct 2011 17:41:58 +
with message-id 
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
--- Begin Message ---
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 ---
--- Begin Message ---
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#645574: marked as done (needs porting to new libpanel-applet interface)

[Debian Bug Tracking System]

Your message dated Mon, 17 Oct 2011 17:38:52 +
with message-id 
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
--- Begin Message ---
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 ---
--- Begin Message ---
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)

[Debian Bug Tracking System]

Your message dated Mon, 17 Oct 2011 17:38:52 +
with message-id 
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
--- Begin Message ---

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 ---
--- Begin Message ---
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#597129: marked as done (gpmudmon-applet: uninstallable, depends on libgtkdatabox-0.9.0-0)

[Debian Bug Tracking System]

Your message dated Mon, 17 Oct 2011 17:38:52 +
with message-id 
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
--- Begin Message ---

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 ---
--- Begin Message ---
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#645546: clang: FTBFS(kfreebsd): error: Operating system is unknown, configure can't continue

[Christoph Egger]

Hi!

Sylvestre Ledru  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#645658: marked as done (bpython-urwid: unsusable due to urwid 1.0.0 in unstable)

[Debian Bug Tracking System]

Your message dated Mon, 17 Oct 2011 17:17:31 +
with message-id 
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
--- Begin Message ---
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 ---
--- Begin Message ---
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  (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 
Changed-By: David Paleino 
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
 e609df37a9cd983e2521799d2dd5a8edaed7e653 73602 bpython3_0.10.1-3_all.deb
 3a4519ea5d579dcc3312af08724f2a113

Bug#645663: /var/run/sphinxsearch not present after reboot, sphinxsearch fails to start

[John Paulett]

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#631068: audacity: Commercial use of nyquist not allowed

[STF]

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#645469: bind fails for AF_UNIX sockets with EINVAL

[Petr Salinger]

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

Processed: [bts-link] source package libreoffice

[Debian Bug Tracking System]

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#644614: [Secure-testing-team] [rt.debian.org #3440] Re: Bug#644614: multiple security issues in radvd 1.6

[Yves-Alexis Perez]

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   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 
+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

Bug#645658: bpython-urwid: unsusable due to urwid 1.0.0 in unstable

[Sebastian Ramacher]

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#645469: bind fails for AF_UNIX sockets with EINVAL

[Robert Millan]

2011/10/16 Petr Salinger :
>> 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#625330: marked as done (fileschanged: ftbfs with gcc-4.6 -Werror)

[Debian Bug Tracking System]

Your message dated Mon, 17 Oct 2011 16:02:16 +
with message-id 
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
--- Begin Message ---
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 ---
--- Begin Message ---
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  (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 
Changed-By: gregor herrmann 
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
H64fwyvrbr2Q+2uuYGkxygE1DxQJ152TyGVtz7PCLrbz2k4Emid+LjNEmng95pAb
ggBBlxNe63SBlEBO7vmD
=SPj/

Processed: libgail-gnome-module: needs porting to new libpanel-applet interface

[Debian Bug Tracking System]

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

[Michael Biebl]

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

Processed: block

[Debian Bug Tracking System]

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

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])

[Debian Bug Tracking System]

Your message dated Mon, 17 Oct 2011 15:03:00 +
with message-id 
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
--- Begin Message ---
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 ---
--- Begin Message ---
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  (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 
Changed-By: gregor herrmann 
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: 
 8bdabae3754ddc34018bc6d0d099c30d49ffbeb3c8d37fc8e1abe3bd09f3fd55 1762 
babl_0.0.22-1.1.dsc
 913f060f12cf8c3c

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])

[Debian Bug Tracking System]

Your message dated Mon, 17 Oct 2011 15:03:56 +
with message-id 
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
--- Begin Message ---
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 ---
--- Begin Message ---
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  (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 
Changed-By: gregor herrmann 
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
 .
   * Non-maintainer upload.
   * Fix "FTBFS: libnet_init.c:88:17:

Bug#645637: roundcube-plugins-extra: contains a convenience code copy of PEAR Net_Sieve

[Jérémy Bobbio]

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#645635: yaskkserv: FTBFS on armel, ia64, etc.

[Tatsuya Kinoshita]

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#643350: marked as done (alsamixergui: FTBFS: Fl_AM.cxx:154:20: error: format not a string literal and no format arguments [-Werror=format-security])

[Debian Bug Tracking System]

Your message dated Mon, 17 Oct 2011 13:47:08 +
with message-id 
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
--- Begin Message ---
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*' 

Bug#645630: must not use bzip2 for libtextwrap1-udeb

[Philipp Kern]

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#645546: clang: FTBFS(kfreebsd): error: Operating system is unknown, configure can't continue

[Sylvestre Ledru]

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#645309: marked as done (debpartial-mirror: cannot handle duplicate entries in Packages)

[Debian Bug Tracking System]

Your message dated Mon, 17 Oct 2011 12:47:08 +
with message-id 
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
--- Begin Message ---
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 
   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 ---
--- Begin Message ---
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 appropriate.

Deb

Processed: directfb: diff for NMU version 1.2.10.0-4.3

[Debian Bug Tracking System]

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#644782: directfb: diff for NMU version 1.2.10.0-4.3

[Hector Oron]

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:
 

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   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 
+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: , 
+Bug: 
+Bug-Debian: http://bugs.debian.org/644782
+Bug-Ubuntu: https://launchpad.net/bugs/
+Forwarded: http://directfb.org/mantis/view.php?id=16
+Reviewed-By: 
+Last-Update: 
+
+--- 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 
+ #include 
+ #include 
++#include 
++
+ #include 
+ 
+ #include 
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: your mail

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> reopen 645327
Bug #645327 {Done: Ondřej Surý } [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#645612: libopenscap1 and libopenscap0: error when trying to install together

[Julien Cristau]

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

Bug#645612: libopenscap1 and libopenscap0: error when trying to install together

[Pierre Chifflier]

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

Bug#645611: marked as done (node-sphericalmercator and libnode-sphericalmercator: error when trying to install together)

[Debian Bug Tracking System]

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
--- Begin Message ---
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 ---
--- Begin Message ---
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 the

Bug#645610: marked as done (node-qs and libnode-qs: error when trying to install together)

[Debian Bug Tracking System]

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
--- Begin Message ---
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 ---
--- Begin Message ---
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#645609: marked as done (node-mkdirp and libnode-mkdirp: error when trying to install together)

[Debian Bug Tracking System]

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
--- Begin Message ---
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 ---
--- Begin Message ---
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

-- 
 . ''`.   Debi

Bug#645608: marked as done (node-mirror and libnode-mirror: error when trying to install together)

[Debian Bug Tracking System]

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
--- Begin Message ---
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 ---
--- Begin Message ---
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

-- 
 . ''`.   Debi

Bug#645607: marked as done (node-mime and libnode-mime: error when trying to install together)

[Debian Bug Tracking System]

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
--- Begin Message ---
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 ---
--- Begin Message ---
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/

Bug#645606: marked as done (node-express and libnode-express: error when trying to install together)

[Debian Bug Tracking System]

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
--- Begin Message ---
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-

Bug#645605: marked as done (node-dirty and libnode-dirty: error when trying to install together)

[Debian Bug Tracking System]

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
--- Begin Message ---
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 ---
--- Begin Message ---
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.

Bug#645604: marked as done (node-connect and libnode-connect: error when trying to install together)

[Debian Bug Tracking System]

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
--- Begin Message ---
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/bo

Bug#645602: marked as done (node-chrono and libnode-chrono: error when trying to install together)

[Debian Bug Tracking System]

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
--- Begin Message ---
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 ---
--- Begin Message ---
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

-- 
 . ''`.   Debi

Bug#645601: marked as done (node-backbone-dirty and libnode-backbone-dirty: error when trying to install together)

[Debian Bug Tracking System]

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
--- Begin Message ---
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#645612: also concerns -dbg pacakages

[Ralf Treinen]

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#645612: libopenscap1 and libopenscap0: error when trying to install together

[Ralf Treinen]

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
  /usr/share/openscap/schemas/oval/5.8/hpux-system-characteristics-sch

Bug#645611: node-sphericalmercator and libnode-sphericalmercator: error when trying to install together

[Ralf Treinen]

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#645610: node-qs and libnode-qs: error when trying to install together

[Ralf Treinen]

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#645609: node-mkdirp and libnode-mkdirp: error when trying to install together

[Ralf Treinen]

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