Bug#644466: shares a file with gnome-power-manager 3.0.2-1

[Jan Hauke Rahm]

Package: gnome-icon-theme-symbolic
Version: 3.2.0-1
Severity: serious

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Hi,

seems like an undeclared conflict or unintended file movement:

gnome-icon-theme-symbolic_3.2.0-1_all.deb is trying to overwrite
'/usr/share/icons/gnome/scalable/status/keyboard-brightness-symbolic.svg',
which is also in package gnome-power-manager 3.0.2-1

Hauke

- -- System Information:
Debian Release: wheezy/sid
  APT prefers unstable
  APT policy: (500, 'unstable'), (1, 'experimental')
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 gnome-icon-theme-symbolic depends on:
ii  gnome-icon-theme3.2.0-1
ii  hicolor-icon-theme  0.12-1 

gnome-icon-theme-symbolic recommends no packages.

gnome-icon-theme-symbolic suggests no packages.

- -- no debconf information

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

iQIcBAEBCgAGBQJOjUrpAAoJEOCD7BUSMcRlGIMQAInCXKNZ1hSP7fXUU9xHfBBy
GYVgrUs2RZTMQOLFxYzykZPwwNne0QwFpeu3phmSLiLRrPwGlDPSYpF+U7bH0Ihe
hm35naDuXQPQA7OkjO2CWzpob/fpkWQgZhGks5Y2OcD8eybp14xgjqCcDHVrHfAH
KeDkgIb65l8416B6FVD91q960rx6DmaD7dngGL5NZNQyHVwKyLkLDxL4BTZiLZHC
rVSYSRG6vdS63f7FwerVgXEk4LqYVtwsxaST6VqQJRKn5884LEq3DhG4SqBN0ohy
bzT4/3LUyKsGVTVfDijuIs6mubscZyEP5j2vGqz4xsmtOOVczXEZ2zy5gPNvbWp3
TVzYn5ya+XwfSM6eGihOvfyuQlYVmXzfb62iXWKehSbAfAOPh/qha20dqCPYDEKv
7HcbiF8bSNqFMenD4x10RAUhPspy3UOTg1SdVYpX0qXp5uhY2/pXnBUl6F1mN3Y9
QSKzjKTYC9w750/tDeZAWuVg4LTtw9tw79mdkgwUoM2N6lgHwA30j8YVRdBLWWyw
NRtmdT/VeUighjui2P0WrLeaXcFi5vCMC8vzRLl6sM7vtVojJiYSD+HaXyPe/C86
eneaPiAb23cBxBoXJjLAsm2SfbuqNA2lQ0Ua45ClPmLcQ7C/i0VEVzorIe86LyQg
rEjqVjuSS9zEWU+8rlK3
=ojrM
-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#643844: marked as done (lightdm: doesn't start at all)

[Debian Bug Tracking System]

Your message dated Thu, 06 Oct 2011 06:02:14 +
with message-id 
and subject line Bug#643844: fixed in lightdm 1.0.2-1
has caused the Debian Bug report #643844,
regarding lightdm: doesn't start at all
to be marked as done.

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

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


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

Dear Maintainer,

New problem! LightDM does not start at all.
I attach the log.

If you need more information do not hesitate to ask.

Hello and thanks



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

Kernel: Linux 3.0.0-1-686-pae (SMP w/2 CPU cores)
Locale: LANG=it_IT.utf8, LC_CTYPE=it_IT.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

Versions of packages lightdm depends on:
ii  adduser3.113
ii  consolekit 0.4.5-1  
ii  dbus   1.4.16-1 
ii  debconf [debconf-2.0]  1.5.41   
ii  libc6  2.13-21  
ii  libglib2.0-0   2.28.6-1 
ii  libpam0g   1.1.3-4  
ii  libxcb11.7-3
ii  libxdmcp6  1:1.1.0-3
ii  lightdm-gtk-greeter1.0.0-3  

Versions of packages lightdm recommends:
ii  xserver-xorg  1:7.6+9

Versions of packages lightdm suggests:
ii  accountsservice  0.6.14-1

-- debconf information:
  lightdm/daemon_name: /usr/sbin/lightdm
* shared/default-x-display-manager: gdm3
[+0.01s] DEBUG: Logging to /var/log/lightdm/lightdm.log
[+0.01s] DEBUG: Starting Light Display Manager 1.0.0, UID=0 PID=1514
[+0.01s] DEBUG: Loaded configuration from /etc/lightdm/lightdm.conf
[+0.01s] DEBUG: Using D-Bus name org.freedesktop.DisplayManager
[+0.01s] DEBUG: Registered seat module xlocal
[+0.01s] DEBUG: Registered seat module xremote
[+0.01s] DEBUG: Adding default seat
[+0.01s] DEBUG: Starting seat
[+0.01s] DEBUG: Starting new display for greeter
[+0.01s] DEBUG: Starting local X display
[+0.02s] DEBUG: Could not run plymouth --ping: Failed to execute child process 
"plymouth" (No such file or directory)
[+0.02s] DEBUG: Using VT 7
[+0.02s] DEBUG: Activating VT 7
[+0.03s] DEBUG: Logging to /var/log/lightdm/x-0.log
[+0.05s] DEBUG: Writing X server authority to /var/run/lightdm/root/:0
[+0.06s] DEBUG: Launching X Server
[+0.06s] DEBUG: Launching process 1623: /usr/bin/X :0 -auth 
/var/run/lightdm/root/:0 -nolisten tcp vt7 -novtswitch
[+0.06s] DEBUG: Waiting for ready signal from X server :0
[+0.06s] DEBUG: Acquired bus name
[+0.06s] DEBUG: Registering seat with bus path 
/org/freedesktop/DisplayManager/Seat0
[+1.66s] DEBUG: Got signal 10 from process 1623
[+1.66s] DEBUG: Got signal from X server :0
[+1.66s] DEBUG: Connecting to XServer :0
[+1.67s] DEBUG: Starting greeter session
[+2.48s] DEBUG: pam_start("lightdm-autologin", "lightdm") -> (0xb97bdc00, 0)
[+2.48s] DEBUG: Starting session lightdm-gtk-greeter as user lightdm logging to 
/var/log/lightdm/x-0-greeter.log
[+2.52s] DEBUG: Greeter user got prompt, aborting authentication
[+2.52s] DEBUG: pam_authenticate(0xb97bdc00, 0) -> 7 (Authentication failure)
[+2.52s] DEBUG: Greeter user failed authentication
[+85.08s] DEBUG: Got signal 15 from process 4865
[+85.08s] DEBUG: Caught Terminated signal, shutting down
[+85.08s] DEBUG: Stopping display manager
[+85.08s] DEBUG: Stopping seat
[+85.08s] DEBUG: Stopping display
[+85.08s] DEBUG: Sending signal 15 to process 1623
[+85.10s] DEBUG: Process 1623 exited with return value 0
[+85.10s] DEBUG: X server stopped
[+85.10s] DEBUG: Removing X server authority /var/run/lightdm/root/:0
[+85.10s] DEBUG: Releasing VT 7
[+85.10s] DEBUG: Display server stopped
[+85.10s] DEBUG: Display stopped
[+85.10s] DEBUG: Seat stopped
[+85.10s] DEBUG: Display manager stopped
[+85.10s] DEBUG: Stopping Light Display Manager
--- End Message ---
--- Begin Message ---
Source: lightdm
Source-Version: 1.0.2-1

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

liblightdm-gobject-1-0_1.0.2-1_amd64.deb
  to main/l/lightdm/liblightdm-gobject-1-0_1.0.2-1_amd64.deb
liblightdm-gobject-dev_1.0.2-1_amd64.deb
  to main/l/lightdm/liblightdm-gobject-dev_1.0.2-1_amd64.deb
liblightdm-qt-1-0_1.0.2-1_amd64.deb
  to main/l/lightdm/liblightdm-qt-1-0_1.0.2-1_amd64.deb
liblightdm-qt-dev_1.0.2-1_amd64.deb
  to main/l/lightdm/liblightdm-qt-dev_1.0.2-1_amd64.deb
lightdm-gtk-gr

Processed: your mail

[Debian Bug Tracking System]

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

> severity 639565 critical
Bug #639565 [liboauth-dev] liboauth-dev: please make loose libcurl dependency
Severity set to 'critical' from 'normal'

> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
639565: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=639565
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#644455: krdc doesn't work after upgrading libvncserver0

[Tarek Soliman]

Package: krdc
Version: 4:4.6.5-2
Severity: grave
Justification: renders package unusable

libvncserver0 was upgraded a few days ago from 0.9.7-3+b1 to 0.9.8-2.
This broke krdc's ability to connect to vnc servers.
Downgrading libvncserver0 to 0.9.7-3+b1 resolves this issue.

Not sure if this is a bug with krdc or libvncserver0 so reporting to krdc.

I think maybe all that is needed is a rebuild of some packages against the new 
libvncserver0?
Not sure what package to rebuild.

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

Kernel: Linux 3.0.0-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/bash

Versions of packages krdc depends on:
ii  kdebase-runtime4:4.6.5-1+b1
ii  libc6  2.13-21 
ii  libkcmutils4   4:4.6.5-2   
ii  libkdecore54:4.6.5-2   
ii  libkdeui5  4:4.6.5-2   
ii  libkdnssd4 4:4.6.5-2   
ii  libkio54:4.6.5-2   
ii  libknotifyconfig4  4:4.6.5-2   
ii  libqt4-xml 4:4.7.3-8   
ii  libqtcore4 4:4.7.3-8   
ii  libqtgui4  4:4.7.3-8   
ii  libstdc++6 4.6.1-13
ii  libvncserver0  0.9.8-2 

Versions of packages krdc recommends:
ii  rdesktop  1.7.0-1

Versions of packages krdc suggests:
ii  khelpcenter4  4:4.6.5-1+b1
ii  krfb  4:4.6.5-2   

-- 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#644450: quickfix: FTBFS: configure: error: C++ compiler cannot create executables

[Nobuhiro Iwamatsu]

Source: quickfix
Version: 1.13.3+dfsg-1
Severity: serious
Justification: fails to build from source
Tags: patch

Hi,

quickfix FTBFS In the architecture except the i386, amd64 and kfreebsd.
  https://buildd.debian.org/status/package.php?p=quickfix
  http://buildd.debian-ports.org/status/package.php?p=quickfix

-
libtoolize:   `/usr/share/aclocal/lt~obsolete.m4'
libtoolize: Consider adding `AC_CONFIG_MACRO_DIR([m4])' to configure.in and
libtoolize: rerunning libtoolize, to keep the correct libtool macros in-tree.
libtoolize: Consider adding `-I m4' to ACLOCAL_AMFLAGS in Makefile.am.
./configure --build arm-linux-gnueabi --prefix=/usr
--mandir=\${prefix}/share/man --infodir=\${prefix}/share/info
CC="/usr/bin/gcc" CXX="/usr/bin/g++" CFLAGS="-O3 -msse3" CXXFLAGS="-O3
-msse3" LDFLAGS="-Wl,-z,defs -L/usr/lib/python2.7/config -lpthread
-ldl -lutil -lm -lpython2.7 -Xlinker -export-dynamic -Wl,-O1
-Wl,-Bsymbolic-functions" --with-ruby --with-mysql=/usr
--enable-new-allocator --with-python=/usr/include/python2.6
--with-postgresql=/usr --with-boost=/usr/include/boost
checking for a BSD-compatible install... /usr/bin/install -c
checking whether build environment is sane... yes
checking for a thread-safe mkdir -p... /bin/mkdir -p
checking for gawk... gawk
checking whether make sets $(MAKE)... yes
checking for C++ compiler default output file name...
configure: error: in
`/build/buildd-quickfix_1.13.3+dfsg-1-armel-cQLPDX/quickfix-1.13.3+dfsg':
configure: error: C++ compiler cannot create executables
See `config.log' for more details.
make: *** [configure-stamp] Error 77
-

Because some architecuture does not support  "-msse3" option.
I made patch which reivse this problem. Please check this?

BTW, When you set -msse3 in build, this program does not work with
some CPU's. Do you notice this problem?
Please see http://www.debian.org/ports/amd64/index.en.html

Best regards,
 Nobuhiro

-- 
Nobuhiro Iwamatsu
   iwamatsu at {nigauri.org / debian.org}
   GPG ID: 40AD1FA6
diff -Nru quickfix-1.13.3+dfsg/debian/changelog quickfix-1.13.3+dfsg/debian/changelog
--- quickfix-1.13.3+dfsg/debian/changelog	2011-10-02 12:16:23.0 +0900
+++ quickfix-1.13.3+dfsg/debian/changelog	2011-10-06 10:33:44.0 +0900
@@ -1,3 +1,9 @@
+quickfix (1.13.3+dfsg-1.1) unstable; urgency=low
+
+  * Non-maintainer upload.
+
+ -- Nobuhiro Iwamatsu   Thu, 06 Oct 2011 10:33:42 +0900
+
 quickfix (1.13.3+dfsg-1) unstable; urgency=low
 
   * Initial release (Closes: #642268)
diff -Nru quickfix-1.13.3+dfsg/debian/rules quickfix-1.13.3+dfsg/debian/rules
--- quickfix-1.13.3+dfsg/debian/rules	2011-09-25 04:37:54.0 +0900
+++ quickfix-1.13.3+dfsg/debian/rules	2011-10-06 10:33:23.0 +0900
@@ -15,6 +15,7 @@
 # from having to guess our platform (since we know it already)
 DEB_HOST_GNU_TYPE   ?= $(shell dpkg-architecture -qDEB_HOST_GNU_TYPE)
 DEB_BUILD_GNU_TYPE  ?= $(shell dpkg-architecture -qDEB_BUILD_GNU_TYPE)
+DEB_HOST_ARCH ?= $(shell dpkg-architecture -qDEB_HOST_ARCH) 
 ifneq ($(DEB_HOST_GNU_TYPE),$(DEB_BUILD_GNU_TYPE))
 CROSS= --build $(DEB_BUILD_GNU_TYPE) --host $(DEB_HOST_GNU_TYPE)
 else
@@ -24,8 +25,14 @@
 
 CC=/usr/bin/gcc
 CXX=/usr/bin/g++
-CFLAGS = -O3 -msse3
-CXXFLAGS = -O3 -msse3
+CFLAGS = -O3
+CXXFLAGS = -O3
+
+ifeq (amd64,$(DEB_HOST_ARCH)) 
+CFLAGS += -O3 -msse3
+CXXFLAGS += -O3 -msse3
+endif
+
 #CFLAGS = -Wall -g
 
 #ifneq (,$(findstring noopt,$(DEB_BUILD_OPTIONS)))

Bug#627443: marked as done (CVE-2011-1929)

[Debian Bug Tracking System]

Your message dated Thu, 06 Oct 2011 01:55:46 +
with message-id 
and subject line Bug#627443: fixed in dovecot 1:1.2.15-7
has caused the Debian Bug report #627443,
regarding CVE-2011-1929
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.)


-- 
627443: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=627443
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: dovecot
Severity: grave
Tags: security

Hi Dovecot maintainers,
CVE-2011-1929 was assigned to the following issue fixed in
1.2.17 and 2.0.13:

| Fixed potential crashes and other problems when parsing
| header names that contained NUL characters.

http://dovecot.org/pipermail/dovecot/2011-May/059085.html
http://dovecot.org/pipermail/dovecot/2011-May/059086.html

Patch:
http://hg.dovecot.org/dovecot-1.1/rev/3698dfe0f21c

Could you contact upstream wrt the exact impact? What is
being crashed here, can someone only crash a delivery
thread or can the whole IMAP server be crashed through
malformed mail messages? In the latter case we should
release a DSA.

Cheers,
Moritz

-- System Information:
Debian Release: wheezy/sid
  APT prefers unstable
  APT policy: (500, 'unstable')
Architecture: amd64 (x86_64)

Kernel: Linux 2.6.38-2-amd64 (SMP w/2 CPU cores)
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash


--- End Message ---
--- Begin Message ---
Source: dovecot
Source-Version: 1:1.2.15-7

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

dovecot-common_1.2.15-7_amd64.deb
  to main/d/dovecot/dovecot-common_1.2.15-7_amd64.deb
dovecot-dbg_1.2.15-7_amd64.deb
  to main/d/dovecot/dovecot-dbg_1.2.15-7_amd64.deb
dovecot-dev_1.2.15-7_amd64.deb
  to main/d/dovecot/dovecot-dev_1.2.15-7_amd64.deb
dovecot-imapd_1.2.15-7_amd64.deb
  to main/d/dovecot/dovecot-imapd_1.2.15-7_amd64.deb
dovecot-pop3d_1.2.15-7_amd64.deb
  to main/d/dovecot/dovecot-pop3d_1.2.15-7_amd64.deb
dovecot_1.2.15-7.debian.tar.gz
  to main/d/dovecot/dovecot_1.2.15-7.debian.tar.gz
dovecot_1.2.15-7.dsc
  to main/d/dovecot/dovecot_1.2.15-7.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 627...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Marco Nenciarini  (supplier of updated dovecot package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Wed, 25 May 2011 10:08:30 +0200
Source: dovecot
Binary: dovecot-common dovecot-dev dovecot-imapd dovecot-pop3d dovecot-dbg
Architecture: source amd64
Version: 1:1.2.15-7
Distribution: stable-security
Urgency: high
Maintainer: Dovecot Maintainers 
Changed-By: Marco Nenciarini 
Description: 
 dovecot-common - secure mail server that supports mbox and maildir mailboxes
 dovecot-dbg - debug symbols for Dovecot
 dovecot-dev - header files for the dovecot mail server
 dovecot-imapd - secure IMAP server that supports mbox and maildir mailboxes
 dovecot-pop3d - secure POP3 server that supports mbox and maildir mailboxes
Closes: 622384 627443
Changes: 
 dovecot (1:1.2.15-7) stable-security; urgency=high
 .
   * [2ffd812] Lifted Build-Conflicts with ancient linux-kernel-headers
 (Closes: #622384)
 .
 dovecot (1:1.2.15-6) stable-security; urgency=high
 .
   * Rebuilt in a clean squeeze environment, no changes.
 .
 dovecot (1:1.2.15-5) stable-security; urgency=high
 .
   * [feae144] Fixed potential crashes and other problems when parsing
 header names that contained NUL characters. (CVE-2011-1929)
 (Closes: #627443)
Checksums-Sha1: 
 b68551c57ec82349ca160aa84f3367dfe7f23845 2208 dovecot_1.2.15-7.dsc
 24d6b7588aa207e4e54c4afa154b72ac4c3d365b 1498403 dovecot_1.2.15-7.debian.tar.gz
 3d6214237b840729c50d3e0f0c57a4e678d478c3 5512336 
dovecot-common_1.2.15-7_amd64.deb
 e0cfaa672ae5edbbbeb06d57fc1b1649c1e3452a 658688 dovecot-dev_1.2.15-7_amd64.deb
 5c79e0b79865217b2fc1c45541d62a4a639a4b34 1177652 
dovecot-imapd_1.2.15-7_amd64.deb
 40ee0ae260a3c89296867da96bfaa1cd29682c27 1073328 
dovecot-pop3d_1.2.15-7_amd64.deb
 83b695c61203a19b3c6d03f3443d678c1e48382e 15064550 
dovecot-dbg_1.2.15-7_amd64.deb
Checksums-Sha256: 
 c58128627d87383635dff60d644bfe06b980ac8257a6511f89d6324bc19f040a 2208 
dovecot_

Bug#625080: marked as done (fstrcmp: FTBFS: ./lib/diffseq.h:461:38: error: 'bxbest' may be used uninitialized in this function [-Werror=uninitialized])

[Debian Bug Tracking System]

Your message dated Thu, 06 Oct 2011 01:47:11 +
with message-id 
and subject line Bug#625331: fixed in fstrcmp 0.4.D001-1
has caused the Debian Bug report #625331,
regarding fstrcmp: FTBFS: ./lib/diffseq.h:461:38: error: 'bxbest' may be used 
uninitialized in this function [-Werror=uninitialized]
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.)


-- 
625331: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=625331
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: fstrcmp
Version: 0.3.D001-1
Severity: serious
Tags: wheezy sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20110502 qa-ftbfs
Justification: FTBFS on amd64

Hi,

During a rebuild of all packages in sid, your package failed to build on
amd64.

Relevant part:
> make[1]: Entering directory 
> `/build/user-fstrcmp_0.3.D001-1-amd64-HXzCBP/fstrcmp-0.3.D001'
> libtool --mode=compile gcc  -Wall -g -O2 -Wall -Wextra -Wshadow -Werror 
> -Wl,--as-needed -I. -c fstrcmp/main.c -o fstrcmp/main.lo
> libtool: compile:  gcc -Wall -g -O2 -Wall -Wextra -Wshadow -Werror 
> -Wl,--as-needed -I. -c fstrcmp/main.c  -fPIC -DPIC -o fstrcmp/.libs/main.o
> libtool: compile:  gcc -Wall -g -O2 -Wall -Wextra -Wshadow -Werror 
> -Wl,--as-needed -I. -c fstrcmp/main.c -o fstrcmp/main.o >/dev/null 2>&1
> libtool --mode=compile gcc  -Wall -g -O2 -Wall -Wextra -Wshadow -Werror 
> -Wl,--as-needed -I. -c lib/ac/string.c -o lib/ac/string.lo
> libtool: compile:  gcc -Wall -g -O2 -Wall -Wextra -Wshadow -Werror 
> -Wl,--as-needed -I. -c lib/ac/string.c  -fPIC -DPIC -o lib/ac/.libs/string.o
> libtool: compile:  gcc -Wall -g -O2 -Wall -Wextra -Wshadow -Werror 
> -Wl,--as-needed -I. -c lib/ac/string.c -o lib/ac/string.o >/dev/null 2>&1
> libtool --mode=compile gcc  -Wall -g -O2 -Wall -Wextra -Wshadow -Werror 
> -Wl,--as-needed -I. -c lib/downcase.c -o lib/downcase.lo
> libtool: compile:  gcc -Wall -g -O2 -Wall -Wextra -Wshadow -Werror 
> -Wl,--as-needed -I. -c lib/downcase.c  -fPIC -DPIC -o lib/.libs/downcase.o
> libtool: compile:  gcc -Wall -g -O2 -Wall -Wextra -Wshadow -Werror 
> -Wl,--as-needed -I. -c lib/downcase.c -o lib/downcase.o >/dev/null 2>&1
> libtool --mode=compile gcc  -Wall -g -O2 -Wall -Wextra -Wshadow -Werror 
> -Wl,--as-needed -I. -c lib/fmemcmp.c -o lib/fmemcmp.lo
> libtool: compile:  gcc -Wall -g -O2 -Wall -Wextra -Wshadow -Werror 
> -Wl,--as-needed -I. -c lib/fmemcmp.c  -fPIC -DPIC -o lib/.libs/fmemcmp.o
> In file included from lib/fmemcmp.c:76:0:
> ./lib/diffseq.h: In function 'diag':
> ./lib/diffseq.h:212:13: warning: variable 'big_snake' set but not used 
> [-Wunused-but-set-variable]
> ./lib/diffseq.h: In function 'compareseq':
> ./lib/diffseq.h:461:38: error: 'bxbest' may be used uninitialized in this 
> function [-Werror=uninitialized]
> ./lib/diffseq.h:406:20: note: 'bxbest' was declared here
> ./lib/diffseq.h:454:38: error: 'fxbest' may be used uninitialized in this 
> function [-Werror=uninitialized]
> ./lib/diffseq.h:404:20: note: 'fxbest' was declared here
> cc1: all warnings being treated as errors
> 
> make[1]: *** [lib/fmemcmp.lo] Error 1

The full build log is available from:
   
http://people.debian.org/~lucas/logs/2011/05/02/fstrcmp_0.3.D001-1_lsid64.buildlog

A list of current common problems and possible solutions is available at 
http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute!

About the archive rebuild: The rebuild was done on about 50 AMD64 nodes
of the Grid'5000 platform, using a clean chroot.  Internet was not
accessible from the build systems.

-- 
| Lucas Nussbaum
| lu...@lucas-nussbaum.net   http://www.lucas-nussbaum.net/ |
| jabber: lu...@nussbaum.fr GPG: 1024D/023B3F4F |


--- End Message ---
--- Begin Message ---
Source: fstrcmp
Source-Version: 0.4.D001-1

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

fstrcmp_0.4.D001-1.dsc
  to main/f/fstrcmp/fstrcmp_0.4.D001-1.dsc
fstrcmp_0.4.D001-1.tar.gz
  to main/f/fstrcmp/fstrcmp_0.4.D001-1.tar.gz
fstrcmp_0.4.D001-1_amd64.deb
  to main/f/fstrcmp/fstrcmp_0.4.D001-1_amd64.deb
libfstrcmp-dev_0.4.D001-1_amd64.deb
  to main/f/fstrcmp/libfstrcmp-dev_0.4.D001-1_amd64.deb
libfstrcmp0-dbg_0.4.D001-1_amd64.deb
  to main/f/fstrcmp/libfstrcmp0-dbg_0.4.D001-1_amd64.deb
libfstrcmp0_0.4.D001-1_amd64.deb
  to main/f/fstrcmp/libfstrcmp0_0.4.D001-1_amd64.deb



A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 625...@bugs.deb

Bug#625331: marked as done (fstrcmp: ftbfs with gcc-4.6 -Werror)

[Debian Bug Tracking System]

Your message dated Thu, 06 Oct 2011 01:47:11 +
with message-id 
and subject line Bug#625331: fixed in fstrcmp 0.4.D001-1
has caused the Debian Bug report #625331,
regarding fstrcmp: 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.)


-- 
625331: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=625331
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: fstrcmp
Version: 0.3.D001-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/fstrcmp_0.3.D001-1_lsid64.buildlog
The last lines of the build log are at the end of this report.



--- End Message ---
--- Begin Message ---
Source: fstrcmp
Source-Version: 0.4.D001-1

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

fstrcmp_0.4.D001-1.dsc
  to main/f/fstrcmp/fstrcmp_0.4.D001-1.dsc
fstrcmp_0.4.D001-1.tar.gz
  to main/f/fstrcmp/fstrcmp_0.4.D001-1.tar.gz
fstrcmp_0.4.D001-1_amd64.deb
  to main/f/fstrcmp/fstrcmp_0.4.D001-1_amd64.deb
libfstrcmp-dev_0.4.D001-1_amd64.deb
  to main/f/fstrcmp/libfstrcmp-dev_0.4.D001-1_amd64.deb
libfstrcmp0-dbg_0.4.D001-1_amd64.deb
  to main/f/fstrcmp/libfstrcmp0-dbg_0.4.D001-1_amd64.deb
libfstrcmp0_0.4.D001-1_amd64.deb
  to main/f/fstrcmp/libfstrcmp0_0.4.D001-1_amd64.deb



A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 625...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Peter Miller  (supplier of updated fstrcmp 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, 06 Oct 2011 10:38:38 +1100
Source: fstrcmp
Binary: fstrcmp libfstrcmp0 libfstrcmp0-dbg libfstrcmp-dev
Architecture: source amd64
Version: 0.4.D001-1
Distribution: unstable
Urgency: low
Maintainer: Peter Miller 
Changed-By: Peter Miller 
Description: 
 fstrcmp- fuzzy comparison of strings
 libfstrcmp-dev - library of fuzzy string comparison functions - development 
files
 libfstrcmp0 - library of fuzzy string comparison functions
 libfstrcmp0-dbg - library of fuzzy string comparison functions - debugging 
symbols
Closes: 625080 625331
Changes: 
 fstrcmp (0.4.D001-1) unstable; urgency=low
 .
   * This change set prepares the fstrcmp project for the next public release.
   * 0.3.D003: Closes: #625080
   * 0.3.D003: Closes: #625331
   * This is a summary, see earlier changelog entries for details of individual
 bug fixes.
Checksums-Sha1: 
 bbcb2db19fa2f118380926110a0665856b708ed2 842 fstrcmp_0.4.D001-1.dsc
 a836965d9bb0ca29b44643eed5c82423aa9c48fb 394614 fstrcmp_0.4.D001-1.tar.gz
 cbeb21276cf1cc24a4ec6e65d4d02483b4af4d59 22678 fstrcmp_0.4.D001-1_amd64.deb
 f3a297f74d88b8dae19f6c5b49b96a8b302bb922 9876 libfstrcmp0_0.4.D001-1_amd64.deb
 c57f53bcc8bb224390c4a5cd724808ff892ef622 25132 
libfstrcmp0-dbg_0.4.D001-1_amd64.deb
 23739f78854e1aded641288ebf3a384a56919511 12290 
libfstrcmp-dev_0.4.D001-1_amd64.deb
Checksums-Sha256: 
 93fb9f2bed7fc74c3dda00bb70c0cb1a606a9f78a9041f333c9a2aef96296001 842 
fstrcmp_0.4.D001-1.dsc
 019f321427de17c033e8d223ee1eca904b202491b7c5edbe4e18be20ae67f8a2 394614 
fstrcmp_0.4.D001-1.tar.gz
 143427e1b814da63700d2a1c32d687772c7381f36e837165d999b5fb7109ba21 22678 
fstrcmp_0.4.D001-1_amd64.deb
 6b4b9efa4562d36756c6c42eacabb6ccb2acdb3076aa0ff4548ac48116a1c5a7 9876 
libfstrcmp0_0.4.D001-1_amd64.deb
 00f2bc4b87101d8733a41f3b5cac012a401e86a8cff28ebe629813f10011ca2f 25132 
libfstrcmp0-dbg_0.4.D001-1_amd64.deb
 a4717039ead380e8447aeb5cbf2a31553d2fd0f95ec8596f795715ddc7768261 12290 
libfstrcmp-dev_0.4.D001-1_amd64.deb
Files: 
 4cb8120da772a94852567aec763460ea 842 devel optional fstrcmp_0.4.D001-1.dsc
 41380b08c921c645e860ed545dba914e 394614 devel optional 
fstrcmp_0.4.D001-1.tar.gz
 4b9867c3aa385f93aeb1c9058c1

Bug#625331: marked as done (fstrcmp: ftbfs with gcc-4.6 -Werror)

[Debian Bug Tracking System]

Your message dated Thu, 06 Oct 2011 01:47:10 +
with message-id 
and subject line Bug#625080: fixed in fstrcmp 0.4.D001-1
has caused the Debian Bug report #625080,
regarding fstrcmp: 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.)


-- 
625080: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=625080
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: fstrcmp
Version: 0.3.D001-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/fstrcmp_0.3.D001-1_lsid64.buildlog
The last lines of the build log are at the end of this report.



--- End Message ---
--- Begin Message ---
Source: fstrcmp
Source-Version: 0.4.D001-1

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

fstrcmp_0.4.D001-1.dsc
  to main/f/fstrcmp/fstrcmp_0.4.D001-1.dsc
fstrcmp_0.4.D001-1.tar.gz
  to main/f/fstrcmp/fstrcmp_0.4.D001-1.tar.gz
fstrcmp_0.4.D001-1_amd64.deb
  to main/f/fstrcmp/fstrcmp_0.4.D001-1_amd64.deb
libfstrcmp-dev_0.4.D001-1_amd64.deb
  to main/f/fstrcmp/libfstrcmp-dev_0.4.D001-1_amd64.deb
libfstrcmp0-dbg_0.4.D001-1_amd64.deb
  to main/f/fstrcmp/libfstrcmp0-dbg_0.4.D001-1_amd64.deb
libfstrcmp0_0.4.D001-1_amd64.deb
  to main/f/fstrcmp/libfstrcmp0_0.4.D001-1_amd64.deb



A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 625...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Peter Miller  (supplier of updated fstrcmp 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, 06 Oct 2011 10:38:38 +1100
Source: fstrcmp
Binary: fstrcmp libfstrcmp0 libfstrcmp0-dbg libfstrcmp-dev
Architecture: source amd64
Version: 0.4.D001-1
Distribution: unstable
Urgency: low
Maintainer: Peter Miller 
Changed-By: Peter Miller 
Description: 
 fstrcmp- fuzzy comparison of strings
 libfstrcmp-dev - library of fuzzy string comparison functions - development 
files
 libfstrcmp0 - library of fuzzy string comparison functions
 libfstrcmp0-dbg - library of fuzzy string comparison functions - debugging 
symbols
Closes: 625080 625331
Changes: 
 fstrcmp (0.4.D001-1) unstable; urgency=low
 .
   * This change set prepares the fstrcmp project for the next public release.
   * 0.3.D003: Closes: #625080
   * 0.3.D003: Closes: #625331
   * This is a summary, see earlier changelog entries for details of individual
 bug fixes.
Checksums-Sha1: 
 bbcb2db19fa2f118380926110a0665856b708ed2 842 fstrcmp_0.4.D001-1.dsc
 a836965d9bb0ca29b44643eed5c82423aa9c48fb 394614 fstrcmp_0.4.D001-1.tar.gz
 cbeb21276cf1cc24a4ec6e65d4d02483b4af4d59 22678 fstrcmp_0.4.D001-1_amd64.deb
 f3a297f74d88b8dae19f6c5b49b96a8b302bb922 9876 libfstrcmp0_0.4.D001-1_amd64.deb
 c57f53bcc8bb224390c4a5cd724808ff892ef622 25132 
libfstrcmp0-dbg_0.4.D001-1_amd64.deb
 23739f78854e1aded641288ebf3a384a56919511 12290 
libfstrcmp-dev_0.4.D001-1_amd64.deb
Checksums-Sha256: 
 93fb9f2bed7fc74c3dda00bb70c0cb1a606a9f78a9041f333c9a2aef96296001 842 
fstrcmp_0.4.D001-1.dsc
 019f321427de17c033e8d223ee1eca904b202491b7c5edbe4e18be20ae67f8a2 394614 
fstrcmp_0.4.D001-1.tar.gz
 143427e1b814da63700d2a1c32d687772c7381f36e837165d999b5fb7109ba21 22678 
fstrcmp_0.4.D001-1_amd64.deb
 6b4b9efa4562d36756c6c42eacabb6ccb2acdb3076aa0ff4548ac48116a1c5a7 9876 
libfstrcmp0_0.4.D001-1_amd64.deb
 00f2bc4b87101d8733a41f3b5cac012a401e86a8cff28ebe629813f10011ca2f 25132 
libfstrcmp0-dbg_0.4.D001-1_amd64.deb
 a4717039ead380e8447aeb5cbf2a31553d2fd0f95ec8596f795715ddc7768261 12290 
libfstrcmp-dev_0.4.D001-1_amd64.deb
Files: 
 4cb8120da772a94852567aec763460ea 842 devel optional fstrcmp_0.4.D001-1.dsc
 41380b08c921c645e860ed545dba914e 394614 devel optional 
fstrcmp_0.4.D001-1.tar.gz
 4b9867c3aa385f93aeb1c9058c1

Bug#625080: marked as done (fstrcmp: FTBFS: ./lib/diffseq.h:461:38: error: 'bxbest' may be used uninitialized in this function [-Werror=uninitialized])

[Debian Bug Tracking System]

Your message dated Thu, 06 Oct 2011 01:47:10 +
with message-id 
and subject line Bug#625080: fixed in fstrcmp 0.4.D001-1
has caused the Debian Bug report #625080,
regarding fstrcmp: FTBFS: ./lib/diffseq.h:461:38: error: 'bxbest' may be used 
uninitialized in this function [-Werror=uninitialized]
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.)


-- 
625080: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=625080
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: fstrcmp
Version: 0.3.D001-1
Severity: serious
Tags: wheezy sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20110502 qa-ftbfs
Justification: FTBFS on amd64

Hi,

During a rebuild of all packages in sid, your package failed to build on
amd64.

Relevant part:
> make[1]: Entering directory 
> `/build/user-fstrcmp_0.3.D001-1-amd64-HXzCBP/fstrcmp-0.3.D001'
> libtool --mode=compile gcc  -Wall -g -O2 -Wall -Wextra -Wshadow -Werror 
> -Wl,--as-needed -I. -c fstrcmp/main.c -o fstrcmp/main.lo
> libtool: compile:  gcc -Wall -g -O2 -Wall -Wextra -Wshadow -Werror 
> -Wl,--as-needed -I. -c fstrcmp/main.c  -fPIC -DPIC -o fstrcmp/.libs/main.o
> libtool: compile:  gcc -Wall -g -O2 -Wall -Wextra -Wshadow -Werror 
> -Wl,--as-needed -I. -c fstrcmp/main.c -o fstrcmp/main.o >/dev/null 2>&1
> libtool --mode=compile gcc  -Wall -g -O2 -Wall -Wextra -Wshadow -Werror 
> -Wl,--as-needed -I. -c lib/ac/string.c -o lib/ac/string.lo
> libtool: compile:  gcc -Wall -g -O2 -Wall -Wextra -Wshadow -Werror 
> -Wl,--as-needed -I. -c lib/ac/string.c  -fPIC -DPIC -o lib/ac/.libs/string.o
> libtool: compile:  gcc -Wall -g -O2 -Wall -Wextra -Wshadow -Werror 
> -Wl,--as-needed -I. -c lib/ac/string.c -o lib/ac/string.o >/dev/null 2>&1
> libtool --mode=compile gcc  -Wall -g -O2 -Wall -Wextra -Wshadow -Werror 
> -Wl,--as-needed -I. -c lib/downcase.c -o lib/downcase.lo
> libtool: compile:  gcc -Wall -g -O2 -Wall -Wextra -Wshadow -Werror 
> -Wl,--as-needed -I. -c lib/downcase.c  -fPIC -DPIC -o lib/.libs/downcase.o
> libtool: compile:  gcc -Wall -g -O2 -Wall -Wextra -Wshadow -Werror 
> -Wl,--as-needed -I. -c lib/downcase.c -o lib/downcase.o >/dev/null 2>&1
> libtool --mode=compile gcc  -Wall -g -O2 -Wall -Wextra -Wshadow -Werror 
> -Wl,--as-needed -I. -c lib/fmemcmp.c -o lib/fmemcmp.lo
> libtool: compile:  gcc -Wall -g -O2 -Wall -Wextra -Wshadow -Werror 
> -Wl,--as-needed -I. -c lib/fmemcmp.c  -fPIC -DPIC -o lib/.libs/fmemcmp.o
> In file included from lib/fmemcmp.c:76:0:
> ./lib/diffseq.h: In function 'diag':
> ./lib/diffseq.h:212:13: warning: variable 'big_snake' set but not used 
> [-Wunused-but-set-variable]
> ./lib/diffseq.h: In function 'compareseq':
> ./lib/diffseq.h:461:38: error: 'bxbest' may be used uninitialized in this 
> function [-Werror=uninitialized]
> ./lib/diffseq.h:406:20: note: 'bxbest' was declared here
> ./lib/diffseq.h:454:38: error: 'fxbest' may be used uninitialized in this 
> function [-Werror=uninitialized]
> ./lib/diffseq.h:404:20: note: 'fxbest' was declared here
> cc1: all warnings being treated as errors
> 
> make[1]: *** [lib/fmemcmp.lo] Error 1

The full build log is available from:
   
http://people.debian.org/~lucas/logs/2011/05/02/fstrcmp_0.3.D001-1_lsid64.buildlog

A list of current common problems and possible solutions is available at 
http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute!

About the archive rebuild: The rebuild was done on about 50 AMD64 nodes
of the Grid'5000 platform, using a clean chroot.  Internet was not
accessible from the build systems.

-- 
| Lucas Nussbaum
| lu...@lucas-nussbaum.net   http://www.lucas-nussbaum.net/ |
| jabber: lu...@nussbaum.fr GPG: 1024D/023B3F4F |


--- End Message ---
--- Begin Message ---
Source: fstrcmp
Source-Version: 0.4.D001-1

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

fstrcmp_0.4.D001-1.dsc
  to main/f/fstrcmp/fstrcmp_0.4.D001-1.dsc
fstrcmp_0.4.D001-1.tar.gz
  to main/f/fstrcmp/fstrcmp_0.4.D001-1.tar.gz
fstrcmp_0.4.D001-1_amd64.deb
  to main/f/fstrcmp/fstrcmp_0.4.D001-1_amd64.deb
libfstrcmp-dev_0.4.D001-1_amd64.deb
  to main/f/fstrcmp/libfstrcmp-dev_0.4.D001-1_amd64.deb
libfstrcmp0-dbg_0.4.D001-1_amd64.deb
  to main/f/fstrcmp/libfstrcmp0-dbg_0.4.D001-1_amd64.deb
libfstrcmp0_0.4.D001-1_amd64.deb
  to main/f/fstrcmp/libfstrcmp0_0.4.D001-1_amd64.deb



A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 625...@bugs.deb

Processed: NMU: guile-1.8 1.8.8+1-6.1

[Debian Bug Tracking System]

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

> tags 625355 + pending
Bug #625355 [guile-1.8] guile-1.8: ftbfs with gcc-4.6 -Werror
Bug #638215 [guile-1.8] guile: Fix FTBFS on hurd-i386
Added tag(s) pending.
Added tag(s) pending.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
625355: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=625355
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#625355: NMU: guile-1.8 1.8.8+1-6.1

[Nobuhiro Iwamatsu]

tags 625355 + pending
thanks

Dear maintainer,

I've prepared an NMU for guile-1.8 (1.8.8+1-6.1) and uploaded
it to DELAYED/5.
Please see changelog for more details.

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


guile-1.8-1.8.8+1.debdiff
Description: Binary data

Processed: Re: FTBFS: ERROR: socket.test: AF_INET6/SOCK_STREAM: bind - arguments: ((system-error "bind" "~A" ("Cannot assign requested address") (99)))

[Debian Bug Tracking System]

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

> severity 643283 important
Bug #643283 [src:guile-1.8] FTBFS: ERROR: socket.test: AF_INET6/SOCK_STREAM: 
bind - arguments: ((system-error "bind" "~A" ("Cannot assign requested 
address") (99)))
Severity set to 'important' from 'serious'

> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
643283: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=643283
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#643283: FTBFS: ERROR: socket.test: AF_INET6/SOCK_STREAM: bind - arguments: ((system-error "bind" "~A" ("Cannot assign requested address") (99)))

[Nobuhiro Iwamatsu]

severity 643283 important
thanks

Hi,

> Source: guile-1.8
> Version: 1.8.8+1-6
> Severity: serious
> Justification: fails to build from source
>
> Hi,
>
> guile-1.8 FTBFS on latest unstable.
> I confirmed on amd64 with cowbuilder.
>
> -
> Running receive.test
> Running regexp.test
> Running signals.test
> Running socket.test
> ERROR: socket.test: AF_INET6/SOCK_STREAM: bind - arguments:
> ((system-error "bind" "~A" ("Cannot assign requested address") (99)))
> ERROR: socket.test: AF_INET6/SOCK_STREAM: bind/sockaddr - arguments:
> ((system-error "bind" "~A" ("Cannot assign requested address") (99)))

This problem depends on the build environment.
When IPv6 is not effective in build environment, this problem occurs.

I changed severity to important.

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#644431: marked as done (theunarchiver: FTBFS(kfreebsd): undefined reference to `reallocf')

[Debian Bug Tracking System]

Your message dated Thu, 06 Oct 2011 01:33:26 +
with message-id 
and subject line Bug#644431: fixed in theunarchiver 2.7.1-3
has caused the Debian Bug report #644431,
regarding theunarchiver: FTBFS(kfreebsd): undefined reference to `reallocf'
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.)


-- 
644431: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=644431
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:theunarchiver
Version: 2.7.1-2
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:

make[3]: Leaving directory 
`/build/buildd-theunarchiver_2.7.1-2-kfreebsd-amd64-xipvuN/theunarchiver-2.7.1/UniversalDetector'
gcc -Wl,--whole-archive -fexceptions -fgnu-runtime -o unar unar.o 
CSCommandLineParser.o CommandLineCommon.o NSStringPrinting.o libXADMaster.a 
../UniversalDetector/libUniversalDetector.a -Wl,--no-whole-archive 
-lgnustep-base -lcrypto -lbz2 -lz -licuuc -lobjc -lstdc++ -lm
libXADMaster.a(XADPrefixCode.o): In function `NewNode':
/build/buildd-theunarchiver_2.7.1-2-kfreebsd-amd64-xipvuN/theunarchiver-2.7.1/XADMaster/XADPrefixCode.m:42:
 undefined reference to `reallocf'
/build/buildd-theunarchiver_2.7.1-2-kfreebsd-amd64-xipvuN/theunarchiver-2.7.1/XADMaster/XADPrefixCode.m:42:
 undefined reference to `reallocf'
/build/buildd-theunarchiver_2.7.1-2-kfreebsd-amd64-xipvuN/theunarchiver-2.7.1/XADMaster/XADPrefixCode.m:42:
 undefined reference to `reallocf'
/build/buildd-theunarchiver_2.7.1-2-kfreebsd-amd64-xipvuN/theunarchiver-2.7.1/XADMaster/XADPrefixCode.m:42:
 undefined reference to `reallocf'
/build/buildd-theunarchiver_2.7.1-2-kfreebsd-amd64-xipvuN/theunarchiver-2.7.1/XADMaster/XADPrefixCode.m:42:
 undefined reference to `reallocf'
libXADMaster.a(XADSkipHandle.o):/build/buildd-theunarchiver_2.7.1-2-kfreebsd-amd64-xipvuN/theunarchiver-2.7.1/XADMaster/XADSkipHandle.m:137:
 more undefined references to `reallocf' follow
collect2: ld returned 1 exit status
make[2]: *** [unar] Error 1
make[2]: Leaving directory 
`/build/buildd-theunarchiver_2.7.1-2-kfreebsd-amd64-xipvuN/theunarchiver-2.7.1/XADMaster'
make[1]: *** [override_dh_auto_build] Error 2
make[1]: Leaving directory 
`/build/buildd-theunarchiver_2.7.1-2-kfreebsd-amd64-xipvuN/theunarchiver-2.7.1'
make: *** [build] Error 2

Full build log at
https://buildd.debian.org/status/fetch.php?pkg=theunarchiver&arch=kfreebsd-amd64&ver=2.7.1-2&stamp=1317795384

Regards

Christoph

If you have further questions please mail debian-...@lists.debian.org

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


--- End Message ---
--- Begin Message ---
Source: theunarchiver
Source-Version: 2.7.1-3

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

theunarchiver_2.7.1-3.debian.tar.bz2
  to main/t/theunarchiver/theunarchiver_2.7.1-3.debian.tar.bz2
theunarchiver_2.7.1-3.dsc
  to main/t/theunarchiver/theunarchiver_2.7.1-3.dsc
theunarchiver_2.7.1-3_amd64.deb
  to main/t/theunarchiver/theunarchiver_2.7.1-3_amd64.deb



A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 644...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Matt Kraai  (supplier of updated theunarchiver package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Format: 1.8
Date: Wed, 05 Oct 2011 18:10:29 -0700
Source: theunarchiver
Binary: theunarchiver
Architecture: source amd64
Version: 2.7.1-3
Distribution: unstable
Urgency: low
Maintainer: Matt Kraai 
Changed-By: Matt Kraai 
Description: 
 theunarchiver - Unarchiver for a variety of file formats
Closes: 644431
Changes: 
 theunarchiver (2.7.1-3) unstable; urgency=low
 .
   * Define reallocf on GNU/kFreeBSD, closes: #644431.
Checksums-Sha1: 
 7c4f83216eed76b612dc7d64e5926eab3f4b2d2c 1451 theunarchiver_2.7.1-3.dsc
 54f9128a6130aaae5864aa61b9c7d8f4d668eda9 15706 
theunarchiver_2.7.1-3.debian.tar.bz2
 d555e73cd4215be4f1e8cb6c317b537ef1bb06cd 1765442 
theunarchiver_2.7.1-3_amd64.deb
Checksums-Sha256: 
 1dd23204cbe4561bb0926f3058bc7d

Bug#644392: dspam truncates mail

[Laurence Withers]

Hi Julien,

On Wed, Oct 05, 2011 at 06:36:26PM +0200, Julien Valroff wrote:
> You use the backport, am I right?

I believe so; Squeeze backports are enabled. There was a dspam update
maybe a couple of weeks ago or so.

> Would you please describe your setup? Do you use DSPAM in daemon mode?

Sure. I don't use the daemon mode, just the command line agent. Here is an
excerpt from my exim configuration:

begin routers
# ...
spamscan:
  no_verify
  condition = "${if and {{!eq {$received_protocol}{spam-scanned}} {!eq 
{$received_protocol}{local}} } {1}{0}}"
  driver = accept
  transport = spamcheck
  require_files = /var/lib/dspam:+/usr/bin

begin transports
# ...
spamcheck:
  driver = pipe
  command = "/usr/bin/dspam --deliver=innocent --user $local_part -- %u" 
  user = dspam
  group = dspam
  return_path_add = false
  log_output = true
  return_fail_output = true

> Do you have 'Broken lineStripping' enabled in your dspam.conf?

No, it is not enabled. I guess the most important bits of the config (though
you're welcome to the entire thing if you want) are:

Preference "spamAction=quarantine"
Preference "signatureLocation=headers"  # 'message' or 'headers'
Preference "showFactors=off"

Bye for now,
-- 
Laurence Withers,http://www.lwithers.me.uk/
tel:+447753988197  tel:+44408643   sip:0408643@0408...@call.me.uk



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

Bug#643514: marked as done (jbossas4: FTBFS: JAVA_HOME not defined correctly.)

[Debian Bug Tracking System]

Your message dated Wed, 05 Oct 2011 22:47:44 +
with message-id 
and subject line Bug#643514: fixed in jbossas4 4.2.3.GA-6
has caused the Debian Bug report #643514,
regarding jbossas4: FTBFS: JAVA_HOME not defined correctly.
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.)


-- 
643514: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=643514
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: jbossas4
Version: 4.2.3.GA-5
Severity: serious
Tags: wheezy sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20110923 qa-ftbfs java-home
Justification: FTBFS on amd64

Hi,

During a rebuild of all packages in sid, your package failed to build on
amd64.

Relevant part:
>  fakeroot debian/rules clean
> test -x debian/rules
> dh_testroot
> You must specify a valid JAVA_HOME or JAVACMD!
> make: *** [testsanity] Error 1

The full build log is available from:
   
http://people.debian.org/~lucas/logs/2011/09/23/jbossas4_4.2.3.GA-5_lsid64.buildlog

This is probably due to the multiarch'ification of openjdk. Please coordinate
with debian-j...@lists.debian.org.

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: jbossas4
Source-Version: 4.2.3.GA-6

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

jbossas4_4.2.3.GA-6.debian.tar.gz
  to main/j/jbossas4/jbossas4_4.2.3.GA-6.debian.tar.gz
jbossas4_4.2.3.GA-6.dsc
  to main/j/jbossas4/jbossas4_4.2.3.GA-6.dsc
jbossas4_4.2.3.GA-6_all.deb
  to main/j/jbossas4/jbossas4_4.2.3.GA-6_all.deb
libjboss-aspects-java_4.2.3.GA-6_all.deb
  to main/j/jbossas4/libjboss-aspects-java_4.2.3.GA-6_all.deb
libjboss-cluster-java_4.2.3.GA-6_all.deb
  to main/j/jbossas4/libjboss-cluster-java_4.2.3.GA-6_all.deb
libjboss-connector-java_4.2.3.GA-6_all.deb
  to main/j/jbossas4/libjboss-connector-java_4.2.3.GA-6_all.deb
libjboss-deployment-java_4.2.3.GA-6_all.deb
  to main/j/jbossas4/libjboss-deployment-java_4.2.3.GA-6_all.deb
libjboss-ejb3-java_4.2.3.GA-6_all.deb
  to main/j/jbossas4/libjboss-ejb3-java_4.2.3.GA-6_all.deb
libjboss-ejb3x-java_4.2.3.GA-6_all.deb
  to main/j/jbossas4/libjboss-ejb3x-java_4.2.3.GA-6_all.deb
libjboss-j2ee-java_4.2.3.GA-6_all.deb
  to main/j/jbossas4/libjboss-j2ee-java_4.2.3.GA-6_all.deb
libjboss-jms-java_4.2.3.GA-6_all.deb
  to main/j/jbossas4/libjboss-jms-java_4.2.3.GA-6_all.deb
libjboss-jmx-java_4.2.3.GA-6_all.deb
  to main/j/jbossas4/libjboss-jmx-java_4.2.3.GA-6_all.deb
libjboss-management-java_4.2.3.GA-6_all.deb
  to main/j/jbossas4/libjboss-management-java_4.2.3.GA-6_all.deb
libjboss-messaging-java_4.2.3.GA-6_all.deb
  to main/j/jbossas4/libjboss-messaging-java_4.2.3.GA-6_all.deb
libjboss-naming-java_4.2.3.GA-6_all.deb
  to main/j/jbossas4/libjboss-naming-java_4.2.3.GA-6_all.deb
libjboss-security-java_4.2.3.GA-6_all.deb
  to main/j/jbossas4/libjboss-security-java_4.2.3.GA-6_all.deb
libjboss-server-java_4.2.3.GA-6_all.deb
  to main/j/jbossas4/libjboss-server-java_4.2.3.GA-6_all.deb
libjboss-system-java_4.2.3.GA-6_all.deb
  to main/j/jbossas4/libjboss-system-java_4.2.3.GA-6_all.deb
libjboss-test-java_4.2.3.GA-6_all.deb
  to main/j/jbossas4/libjboss-test-java_4.2.3.GA-6_all.deb
libjboss-transaction-java_4.2.3.GA-6_all.deb
  to main/j/jbossas4/libjboss-transaction-java_4.2.3.GA-6_all.deb
libjboss-webservices-java_4.2.3.GA-6_all.deb
  to main/j/jbossas4/libjboss-webservices-java_4.2.3.GA-6_all.deb



A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 643...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Miguel Landaeta  (supplier of updated jbossas4 package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Format: 1.8
Date: Tue, 27 Sep 2011 21:20:46 -0430
Source: jbossas4
Binary: jbossas4 libjboss-test-java libjboss-jmx-java libjboss-system-java 
libjboss-j2ee-java libjboss-ejb3-java libjboss-ejb3x-java libjboss-naming-java 
libjboss-deployment-java libjboss

Bug#643532: marked as done (libjibx1.2-java: FTBFS: JAVA_HOME not defined correctly.)

[Debian Bug Tracking System]

Your message dated Wed, 05 Oct 2011 22:33:34 +
with message-id 
and subject line Bug#643532: fixed in libjibx1.2-java 1.2.3-2
has caused the Debian Bug report #643532,
regarding libjibx1.2-java: FTBFS: JAVA_HOME not defined correctly.
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.)


-- 
643532: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=643532
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: libjibx1.2-java
Version: 1.2.3-1
Severity: serious
Tags: wheezy sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20110923 qa-ftbfs java-home
Justification: FTBFS on amd64

Hi,

During a rebuild of all packages in sid, your package failed to build on
amd64.

Relevant part:
>  fakeroot debian/rules clean
> test -x debian/rules
> dh_testroot
> rmdir build
> rmdir: failed to remove `build': Directory not empty
> make: [cleanbuilddir] Error 1 (ignored)
> You must specify a valid JAVA_HOME or JAVACMD!
> make: *** [testsanity] Error 1

The full build log is available from:
   
http://people.debian.org/~lucas/logs/2011/09/23/libjibx1.2-java_1.2.3-1_lsid64.buildlog

This is probably due to the multiarch'ification of openjdk. Please coordinate
with debian-j...@lists.debian.org.

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: libjibx1.2-java
Source-Version: 1.2.3-2

We believe that the bug you reported is fixed in the latest version of
libjibx1.2-java, which is due to be installed in the Debian FTP archive:

libjibx-java_1.2.3-2_all.deb
  to main/libj/libjibx1.2-java/libjibx-java_1.2.3-2_all.deb
libjibx1.2-java-doc_1.2.3-2_all.deb
  to main/libj/libjibx1.2-java/libjibx1.2-java-doc_1.2.3-2_all.deb
libjibx1.2-java_1.2.3-2.debian.tar.gz
  to main/libj/libjibx1.2-java/libjibx1.2-java_1.2.3-2.debian.tar.gz
libjibx1.2-java_1.2.3-2.dsc
  to main/libj/libjibx1.2-java/libjibx1.2-java_1.2.3-2.dsc
libjibx1.2-java_1.2.3-2_all.deb
  to main/libj/libjibx1.2-java/libjibx1.2-java_1.2.3-2_all.deb



A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 643...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Miguel Landaeta  (supplier of updated libjibx1.2-java package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Format: 1.8
Date: Tue, 27 Sep 2011 20:38:31 -0430
Source: libjibx1.2-java
Binary: libjibx1.2-java libjibx-java libjibx1.2-java-doc
Architecture: source all
Version: 1.2.3-2
Distribution: unstable
Urgency: low
Maintainer: Debian Java Maintainers 

Changed-By: Miguel Landaeta 
Description: 
 libjibx-java - Framework for binding XML data to Java objects
 libjibx1.2-java - Framework for binding XML data to Java objects
 libjibx1.2-java-doc - Documentation for libjibx-java
Closes: 643532
Changes: 
 libjibx1.2-java (1.2.3-2) unstable; urgency=low
 .
   * Team upload.
   * Switch to default-jdk. (Closes: #643532).
   * Bump Standards-Version to 3.9.2. No changes were required.
   * Drop unneeded B-D on quilt.
   * Use anonymous URL for Vcs-Svn field.
Checksums-Sha1: 
 94293cb585e57a501a35690d9aafd137686bb386 1624 libjibx1.2-java_1.2.3-2.dsc
 68781a48003a0683336713173a340a6500a88020 5856 
libjibx1.2-java_1.2.3-2.debian.tar.gz
 fe5c228eedac65550f3b96735b3969216b08fb5a 663938 libjibx1.2-java_1.2.3-2_all.deb
 866d7e0f2de6512b437c7fc3c46445fa286cef3e 6610 libjibx-java_1.2.3-2_all.deb
 8e4aa746d13d67d7f481db6da8086b0b3907ac86 5913982 
libjibx1.2-java-doc_1.2.3-2_all.deb
Checksums-Sha256: 
 3bddea7d258ef703958a99a8f90d9ef820bff1c1814878a0ddd5ce2ae7c31d68 1624 
libjibx1.2-java_1.2.3-2.dsc
 efc04c3fce1d982ea57fe29be1793550eb58c5ea058e1f9a81ba36e25ad8897d 5856 
libjibx1.2-java_1.2.3-2.debian.tar.gz
 0219419b2470a1c10944fdac3aad99deafc05db8e2eeff36f8bc36c616626204 663938 
libjibx1.2-java_1.2.3-2_all.deb
 5e74e41a8cf9a17a48f0e4227f583e389bb4eb13554ffa685fb55373a4baae8f 6610 
libjibx-java_1.2.3-2_all.deb
 32116b400e65f27a8f7c9bdd774b72ce350f07703d7a994ff01dd0c0c641a8db 5913982 
libjibx1.2-java-doc_1.2

Processed: reassign 644443 to quodlibet-plugins, severity of 644443 is grave

[Debian Bug Tracking System]

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

> reassign 63 quodlibet-plugins
Bug #63 [quodlibet] Fails to start; "ImportError: cannot import name 
EditingPlugins"
Bug reassigned from package 'quodlibet' to 'quodlibet-plugins'.
Bug No longer marked as found in versions quodlibet/2.3-1.
> # Turns out it goes away if I remove quodlibet-plugins
> severity 63 grave
Bug #63 [quodlibet-plugins] Fails to start; "ImportError: cannot import 
name EditingPlugins"
Severity set to 'grave' from 'important'

> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
63: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=63
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#554556: marked as done (FTBFS with binutils-gold)

[Christian T. Steigies]

On Wed, Oct 05, 2011 at 09:15:39PM +0200, Jakub Wilk wrote:
> * Christian T. Steigies , 2011-10-05, 20:24:
> >>>Tried to build your package and it fails to build with GNU
> >>>binutils-gold.
> >>The version in unstable builds fine against binutils-gold.
> >Sorry, I can not reproduce your finding on amd64.
> 
> Interesting. Indeed, it fails to build on amd64. However, before
> closing the bug I tried it on i386, where it builds successfully.
> The relevant line from i386 buid log[0] is:
> 
> g++ -Wl,-O1 -o ../../build/bin/qgle objects/about.o objects/amove.o 
> objects/arc.o objects/circle.o objects/colourbutton.o objects/colourpicker.o 
> objects/component.o objects/consolewindow.o objects/drawingobject.o 
> objects/ellipse.o objects/fileinfo.o objects/gledrawing.o objects/grid.o 
> objects/line.o objects/main.o objects/mainwindow.o objects/newfile.o 
> objects/polararray.o objects/propertyeditor.o objects/propertymodel.o 
> objects/qgle_statics.o objects/qgs.o objects/qgslibloader.o 
> objects/serverthread.o objects/settings.o objects/settings_dialogue.o 
> objects/snapline.o objects/text.o objects/variantdelegate.o 
> objects/objectblocks.o objects/dialogues.o objects/moc_about.o 
> objects/moc_amove.o objects/moc_arc.o objects/moc_circle.o 
> objects/moc_colourbutton.o objects/moc_colourpicker.o objects/moc_component.o 
> objects/moc_consolewindow.o objects/moc_drawingobject.o objects/moc_ellipse.o 
> objects/moc_gledrawing.o objects/moc_grid.o objects/moc_line.o 
> objects/moc_mainwindow.o objects/moc_newfile.o objects/moc_polararr
> ay.o objects/moc_propertyeditor.o objects/moc_propertymodel.o
> objects/moc_qgs.o objects/moc_serverthread.o objects/moc_settings.o
> objects/moc_settings_dialogue.o objects/moc_snapline.o
> objects/moc_text.o objects/moc_variantdelegate.o
> objects/moc_objectblocks.o objects/moc_dialogues.o
> objects/qrc_qgle.o-L/usr/lib -ldl -lgle-graphics-4.2.2
> -L../../build/lib/ -lQtGui -lQtNetwork -lQtCore -lpthread
> 
> As you see, -ldl is there.

Yes, maybe that explains why I can not find the place where I need to add
-ldl to make it build on amd64.

> >Are you sure you have binutils-gold installed?
> 
> Yes. But anyway, sorry for the noise!
> 
> 
> [0] 
> https://buildd.debian.org/status/fetch.php?pkg=gle-graphics&arch=i386&ver=4.2.2-4%2Bb2&stamp=1316278910

On the amd64 buildd (without binutils-gold), it builds, without -ldl:
https://buildd.debian.org/status/fetch.php?pkg=gle-graphics&arch=amd64&ver=4.2.2-4%2Bb2&stamp=1316277792
 
With binutils-gold, there is no -ldl, and the build fails. I did not see any
significant difference between your i386 and and my amd64 buildlog, during
the build, the check for dlopen succeeds:

 checking for qmake-qt4... /usr/bin/qmake-qt4
 checking for library containing dlopen... -ldl


However, tt does build on amd64 with this patch:

-- gle-graphics-4.2.2.orig/src/gui/qgle.pro.in
+++ gle-graphics-4.2.2/src/gui/qgle.pro.in
@@ -163,7 +163,7 @@
 
 # link against the GLE library (unix -> Linux and Mac OS/X)
 unix {
-   LIBS += -lgle-graphics-@GLE_VERSION@ -L../../build/lib/
+   LIBS += -ldl -lgle-graphics-@GLE_VERSION@ -L../../build/lib/
 }
 win32 {
LIBS += -lgle-graphics-@GLE_VERSION@ -L../../build/bin/


Or with this patch:

--- gle-graphics-4.2.2.orig/src/gui/qgle.pro.in
+++ gle-graphics-4.2.2/src/gui/qgle.pro.in
@@ -157,7 +157,7 @@
  images/reload.png \
  images/reload_red.png
 
-linux-g++ {
+linux-g++-64 {
LIBS += -ldl
 }
 

I am not a qt expert, but I wonder why the rule needs to be called
linux-g++-64 even though the compiler is called as g++.  I assume the latter
patch works only for amd64 and will fail on all other arches, does it need
an arch specific extension for every other CPU?

So perhaps the first solution is better, is there a reason why -ldl is not
included in the unix rule?

Christian



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

Bug#643557: gtk+2.0: FTBFS: Failed to start xvfb.

[Michael Biebl]

Version 2.24.6-2 that I just uploaded to unstable builds fine [1]

So I'm closing this bug.

[1] https://buildd.debian.org/status/package.php?p=gtk%2B2.0&suite=sid
-- 
Why is it that all of the instruments seeking intelligent life in the
universe are pointed away from Earth?



signature.asc
Description: OpenPGP digital signature

Bug#643557: marked as done (gtk+2.0: FTBFS: Failed to start xvfb.)

[Debian Bug Tracking System]

Your message dated Wed, 05 Oct 2011 23:51:03 +0200
with message-id <4e8cd147.5020...@debian.org>
and subject line gtk+2.0: FTBFS: Failed to start xvfb.
has caused the Debian Bug report #643557,
regarding gtk+2.0: FTBFS: Failed to start xvfb.
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.)


-- 
643557: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=643557
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: gtk+2.0
Version: 2.24.6-1
Severity: serious
Tags: wheezy sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20110923 qa-ftbfs
Justification: FTBFS on amd64

Hi,

During a rebuild of all packages in sid, your package failed to build on
amd64.

Relevant part:
> make[4]: Entering directory 
> `/build/gtk+2.0-xBtYvS/gtk+2.0-2.24.6/debian/build/shared/gtk/tests'
> /usr/bin/make  check-local
> make[5]: Entering directory 
> `/build/gtk+2.0-xBtYvS/gtk+2.0-2.24.6/debian/build/shared/gtk/tests'
> Gtk+Tests:ERROR: Failed to start Xvfb environment for X11 target tests.
> make[5]: *** [test-cwd] Error 1

The full build log is available from:
   
http://people.debian.org/~lucas/logs/2011/09/23/gtk+2.0_2.24.6-1_lsid64.buildlog

A list of current common problems and possible solutions is available at 
http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute!

About the archive rebuild: The rebuild was done on about 50 AMD64 nodes
of the Grid'5000 platform, using a clean chroot.  Internet was not
accessible from the build systems.


--- End Message ---
--- Begin Message ---
Version 2.24.6-2 that I just uploaded to unstable builds fine [1]

So I'm closing this bug.

[1] https://buildd.debian.org/status/package.php?p=gtk%2B2.0&suite=sid
-- 
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
--- End Message ---

Bug#642922: regression: "sh -c" change causes FTBFS

[Stéphane Glondu]

Le 26/09/2011 22:44, Jonathan Nieder a écrit :
>> I beg to differ. ocamlbuild uses libc's system(), it would be insane to
>> change that. It seems that darcs is also affected. There might be also
>> more packages affected...
> 
> Got it --- I'll prepare an upload reverting the "sh -c" patch.
> 
> More understanding of what is actually happening would be welcome, of
> course.

It seems that darcs failure was unrelated. I digged a bit more, and
found some suspicious code in ocamlbuild:

  http://caml.inria.fr/mantis/view.php?id=5371

I still don't understand why this corner case is triggered with this
patched dash, and I'd rather wait for more feedback before unreverting
the patch in dash.


Cheers,

-- 
Stéphane




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

Bug#636536: marked as done (multiarch enabled libgail breaks libgnome2)

[Debian Bug Tracking System]

Your message dated Wed, 05 Oct 2011 21:17:55 +
with message-id 
and subject line Bug#636536: fixed in gtk+2.0 2.24.6-2
has caused the Debian Bug report #636536,
regarding multiarch enabled libgail breaks libgnome2
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.)


-- 
636536: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=636536
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: libgnome2-0
Version: 2.32.1-1
Severity: important

Start any application linked with libgnome2-0, e.g. dia-gnome or gvim
from vim-gnome, while you have the new multiarch libgtk2.0-00 installed:

  (dia-gnome:4047): Gnome-WARNING **: Accessibility: failed to find module
  'libgail' which is needed to make this application accessible
  **
  ERROR:accessible.c:556:spi_accessible_construct: assertion failed: (o)
  Aborted

Reason is that libgnome2 can't find the GTK module libgail.so
which is now in /usr/lib/x86_64-linux-gnu/gtk-2.0/modules/libgail.so.
Note that when looking for accessibility modules libgnome does _not_
use the glib module loading functions (which are patched to look
both into the multiarch and "classic" directories). Instead it does
its own search which doesn't know about multiarch.

Cheers, Roderich


-- System Information:
Debian Release: wheezy/sid
  APT prefers oneiric
  APT policy: (500, 'oneiric'), (500, 'unstable'), (1, 'experimental')
Architecture: amd64 (x86_64)

Kernel: Linux 3.0.0 (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 libgnome2-0 depends on:
ii  gvfs1.8.2-1  userspace virtual filesystem - ser
ii  libbonobo2-02.24.3-1 Bonobo CORBA interfaces library
ii  libc6   2.13-13  Embedded GNU C Library: Shared lib
ii  libcanberra00.28-1   a simple abstract interface for pl
ii  libgconf2-4 2.32.4-1 GNOME configuration database syste
ii  libglib2.0-02.29.14-0ubuntu1 GLib library of C routines
ii  libgnome2-common2.32.1-1 The GNOME library - common files
ii  libgnomevfs2-0  1:2.24.4-1   GNOME Virtual File System (runtime
ii  liborbit2   1:2.14.18-0.2libraries for ORBit2 - a CORBA ORB
ii  libpopt01.16-1   lib for parsing cmdline parameters

ii  libgtk2.0-0 2.24.5-4 GTK+ graphical user interface lib
ii  libgail-common  2.24.5-4 GNOME Accessibility Implementation


libgnome2-0 recommends no packages.

libgnome2-0 suggests no packages.

-- no debconf information


--- End Message ---
--- Begin Message ---
Source: gtk+2.0
Source-Version: 2.24.6-2

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

gir1.2-gtk-2.0_2.24.6-2_i386.deb
  to main/g/gtk+2.0/gir1.2-gtk-2.0_2.24.6-2_i386.deb
gtk+2.0_2.24.6-2.debian.tar.gz
  to main/g/gtk+2.0/gtk+2.0_2.24.6-2.debian.tar.gz
gtk+2.0_2.24.6-2.dsc
  to main/g/gtk+2.0/gtk+2.0_2.24.6-2.dsc
gtk2-engines-pixbuf_2.24.6-2_i386.deb
  to main/g/gtk+2.0/gtk2-engines-pixbuf_2.24.6-2_i386.deb
gtk2.0-examples_2.24.6-2_i386.deb
  to main/g/gtk+2.0/gtk2.0-examples_2.24.6-2_i386.deb
libgail-common_2.24.6-2_i386.deb
  to main/g/gtk+2.0/libgail-common_2.24.6-2_i386.deb
libgail-dbg_2.24.6-2_i386.deb
  to main/g/gtk+2.0/libgail-dbg_2.24.6-2_i386.deb
libgail-dev_2.24.6-2_i386.deb
  to main/g/gtk+2.0/libgail-dev_2.24.6-2_i386.deb
libgail-doc_2.24.6-2_all.deb
  to main/g/gtk+2.0/libgail-doc_2.24.6-2_all.deb
libgail18_2.24.6-2_i386.deb
  to main/g/gtk+2.0/libgail18_2.24.6-2_i386.deb
libgtk2.0-0-dbg_2.24.6-2_i386.deb
  to main/g/gtk+2.0/libgtk2.0-0-dbg_2.24.6-2_i386.deb
libgtk2.0-0-udeb_2.24.6-2_i386.udeb
  to main/g/gtk+2.0/libgtk2.0-0-udeb_2.24.6-2_i386.udeb
libgtk2.0-0_2.24.6-2_i386.deb
  to main/g/gtk+2.0/libgtk2.0-0_2.24.6-2_i386.deb
libgtk2.0-bin_2.24.6-2_i386.deb
  to main/g/gtk+2.0/libgtk2.0-bin_2.24.6-2_i386.deb
libgtk2.0-common_2.24.6-2_all.deb
  to main/g/gtk+2.0/libgtk2.0-common_2.24.6-2_all.deb
libgtk2.0-dev_2.24.6-2_i386.deb
  to main/g/gtk+2.0/libgtk2.0-dev_2.24.6-2_i386.deb
libgtk2.0-doc_2.24.6-2_all.deb
  to main/g/gtk+2.0/libgtk2.0-doc_2.24.6-2_all.deb



A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 636...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance s

Bug#644290: marked as done (phppgadmin multiple XSS (CVE-2011-3598))

[Debian Bug Tracking System]

Your message dated Wed, 05 Oct 2011 20:54:22 +
with message-id 
and subject line Bug#644290: fixed in phppgadmin 5.0.3-1
has caused the Debian Bug report #644290,
regarding phppgadmin multiple XSS (CVE-2011-3598)
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.)


-- 
644290: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=644290
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: phppgadmin
Severity: critical
Tags: security

Hi,

Multiple XSS vulnerabilities have been reported in phpPgAdmin:
https://secunia.com/advisories/46248/

Please ensure that unstable is fixed on short notice and give the upload
an elevated urgency tag.

Can you also assess whether (old)stable are affected, and if so, provide
packages? If not (affected or able), do let us know aswell.

In any case, please mention CVE-2011-3598 in your changelogs.


thanks,
Thijs


--- End Message ---
--- Begin Message ---
Source: phppgadmin
Source-Version: 5.0.3-1

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

phppgadmin_5.0.3-1.debian.tar.gz
  to main/p/phppgadmin/phppgadmin_5.0.3-1.debian.tar.gz
phppgadmin_5.0.3-1.dsc
  to main/p/phppgadmin/phppgadmin_5.0.3-1.dsc
phppgadmin_5.0.3-1_all.deb
  to main/p/phppgadmin/phppgadmin_5.0.3-1_all.deb
phppgadmin_5.0.3.orig.tar.gz
  to main/p/phppgadmin/phppgadmin_5.0.3.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.
Christoph Berg  (supplier of updated phppgadmin package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Wed, 05 Oct 2011 21:47:32 +0200
Source: phppgadmin
Binary: phppgadmin
Architecture: source all
Version: 5.0.3-1
Distribution: unstable
Urgency: low
Maintainer: Isaac Clerencia 
Changed-By: Christoph Berg 
Description: 
 phppgadmin - web-based administration tool for PostgreSQL
Closes: 644290
Changes: 
 phppgadmin (5.0.3-1) unstable; urgency=low
 .
   * New upstream release, fixes XSS vulnerabilities.
 Closes: #644290, CVE-2011-3598.
Checksums-Sha1: 
 fe2527743edf131853e253a197813f734c0ed41f 1949 phppgadmin_5.0.3-1.dsc
 dcf3f3a580fce7e2ed8d57a6559a23b8b7c20417 1056396 phppgadmin_5.0.3.orig.tar.gz
 54a7a745842386650ae5a57735191e5320814a8f 10889 phppgadmin_5.0.3-1.debian.tar.gz
 4dc6a1c3bd15e97fbf53df5fff855c3c656c6479 1018752 phppgadmin_5.0.3-1_all.deb
Checksums-Sha256: 
 880e7e8b6a4a394aec9977109ea1490d6e170284fb86565ff9d76137072a5cce 1949 
phppgadmin_5.0.3-1.dsc
 5cb6fc8b6bcf109d6919f99d875e4407f7b78fdcc3a1d92d9e76c99ed281a166 1056396 
phppgadmin_5.0.3.orig.tar.gz
 8f1a725f0df4140a4e23389b0c7700be4b29ad0c26bd64663bc7a3ceea12c7ad 10889 
phppgadmin_5.0.3-1.debian.tar.gz
 114ea51c0d518b6857638c5bce1c7366367b2179abfac807b8670f54decb9226 1018752 
phppgadmin_5.0.3-1_all.deb
Files: 
 28513af558a8d4860c4682ce2cc2a3ac 1949 web extra phppgadmin_5.0.3-1.dsc
 885e18d4fc02805e479034c1e6c23c41 1056396 web extra phppgadmin_5.0.3.orig.tar.gz
 475ecf4b10b9a4a790511caaf143b444 10889 web extra 
phppgadmin_5.0.3-1.debian.tar.gz
 64df941fb7d39706528a6c1bbca781d5 1018752 web extra phppgadmin_5.0.3-1_all.deb

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

iQIcBAEBCAAGBQJOjLfcAAoJEExaa6sS0qeuiHcP/RKtvTpEmjaRIH2vwBNZKBel
cMZ1iNKfpdrDzUuw/WotPxdEWNppQuOr4oxsZ6qFYx+YXjW6gzCQOT2mGo7pasp1
YQa4W/nPUbt0QFoxMR3Yhe+l7qeq84MI0v9Zfo+QSRV5Mc4UvCdtNmjG6+fzgk9F
o1ey7/3NhE6CrdQDsyXdi22VN+4E4xOmeVYtwjaI+ND9uDKfX7t4BIKJ+WlypGY5
OeFpWSTs7DvPkvf0O+yBk9bpQLoYa62zh6Ulu467nH7C8IFf4HfhuFD/hponKYAj
bGaS2KA51UkiNeMJYbhOS+aYAw9+gLHy1xUQpu/q4xWAWVVtvd+KY39rB3MLSbJy
LzIibN4P7M2Sv+qVXRS4wqBKe/sZnWG8aBdi6+7FBkkxfV2A4ZRoTxN8SFCVHE4j
aC7vFJDxoLybNoz9MF6X8XBk7++I/VQdMFnFarrmg9pJxeF630OzEq96xDMbzRdb
TmTbopL2IWVc0hI5tMGW15Iw98BSWo0TL7t78pLdO4WZyKtwftIZOJVaP/cbNe6d
rNyXULNYre8tfIQ2EBr5lpBQKxdJCww9Zy9iFcVaalWm+67e0E8UhdN8JZMNfB5s
3tCzbJt08VT5xKxQSqHvRDRtNp4HVrSR7pqVuGBeNJUwc+yAFPESEeLosRPjLBac
6AMGqij/8LX2QmZuZKWu
=kM1P
-END PGP SIGNATURE-


--- End Message ---

Bug#556506: marked as done (FTBFS with binutils-gold)

[Debian Bug Tracking System]

Your message dated Wed, 05 Oct 2011 20:54:55 +
with message-id 
and subject line Bug#556506: fixed in ttt 1.7-3.3
has caused the Debian Bug report #556506,
regarding FTBFS with binutils-gold
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.)


-- 
556506: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=556506
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: ttt
Version: 1.7-3.2
Severity: minor
User: peter.fritzs...@gmx.de
Usertags: no-add-needed

Tried to build your package and it fails to build with GNU binutils-gold. The
important difference is that --no-add-needed is the default behavior of of GNU
binutils-gold. Please provide all needed libraries to the linker when building
your executables.

Objects inside an .a archive aren't linked yet. This means that you must resolve
their symbols when linking them to a program.

More informations can be found at
 
http://wiki.debian.org/qa.debian.org/FTBFS#A2009-11-02Packagesfailingbecausebinutils-gold.2BAC8-indirectlinking

gcc -o ttt ttt.o tk_ttt.o common.o display.o account.o net_names.o window.o 
node.o net_read.o  -L/usr/lib -ltk8.4 -ltcl8.4 -L/usr/lib -lBLT.2.4.8.4 -L 
-lX11 -lpcap -ldl -lm -lnsl  -ldl
/usr/bin/ld: /usr/lib/libBLT.2.4.8.4.a(bltGraph.o): in function 
DrawPlotRegion:(.text+0x4f6): error: undefined reference to 'XFillRectangle'
/usr/bin/ld: /usr/lib/libBLT.2.4.8.4.a(bltGraph.o): in function 
Blt_DrawGraph:(.text+0x652): error: undefined reference to 'XCopyArea'
/usr/bin/ld: /usr/lib/libBLT.2.4.8.4.a(bltGraph.o): in function 
Blt_DrawGraph:(.text+0x952): error: undefined reference to 'XFillRectangles'
/usr/bin/ld: /usr/lib/libBLT.2.4.8.4.a(bltGraph.o): in function 
DisplayGraph:(.text+0xaf5): error: undefined reference to 'XCopyArea'
/usr/bin/ld: /usr/lib/libBLT.2.4.8.4.a(bltGraph.o): in function 
DisplayGraph:(.text+0xbb8): error: undefined reference to 'XCopyArea'
/usr/bin/ld: /usr/lib/libBLT.2.4.8.4.a(bltBeep.o): in function 
BeepCmd:(.text+0x6a): error: undefined reference to 'XBell'
/usr/bin/ld: /usr/lib/libBLT.2.4.8.4.a(bltBitmap.o): in function 
BitmapToData:(.text+0x2a9): error: undefined reference to 'XGetImage'
/usr/bin/ld: /usr/lib/libBLT.2.4.8.4.a(bltBusy.o): in function 
ShowBusyWindow:(.text+0x48f): error: undefined reference to 'XRaiseWindow'
/usr/bin/ld: /usr/lib/libBLT.2.4.8.4.a(bltCanvEps.o): in function 
DisplayEps:(.text+0x6c6): error: undefined reference to 'XSetTSOrigin'
/usr/bin/ld: /usr/lib/libBLT.2.4.8.4.a(bltCanvEps.o): in function 
DisplayEps:(.text+0x6f3): error: undefined reference to 'XFillRectangle'
/usr/bin/ld: /usr/lib/libBLT.2.4.8.4.a(bltCanvEps.o): in function 
DisplayEps:(.text+0x706): error: undefined reference to 'XSetTSOrigin'
/usr/bin/ld: /usr/lib/libBLT.2.4.8.4.a(bltCanvEps.o): in function 
DisplayEps:(.text+0x8f7): error: undefined reference to 'XCopyArea'
/usr/bin/ld: /usr/lib/libBLT.2.4.8.4.a(bltContainer.o): in function 
GetChildren:(.text+0xa6): error: undefined reference to 'XQueryTree'
/usr/bin/ld: /usr/lib/libBLT.2.4.8.4.a(bltContainer.o): in function 
GetChildren:(.text+0x11b): error: undefined reference to 'XFree'
/usr/bin/ld: /usr/lib/libBLT.2.4.8.4.a(bltContainer.o): in function 
MapTree:(.text+0x13b): error: undefined reference to 'XMapWindow'
/usr/bin/ld: /usr/lib/libBLT.2.4.8.4.a(bltContainer.o): in function 
StringToXID:(.text+0x348): error: undefined reference to 'XMoveResizeWindow'
/usr/bin/ld: /usr/lib/libBLT.2.4.8.4.a(bltContainer.o): in function 
StringToXID:(.text+0x568): error: undefined reference to 'XSelectInput'
/usr/bin/ld: /usr/lib/libBLT.2.4.8.4.a(bltContainer.o): in function 
CmdSearch:(.text+0x5ae): error: undefined reference to 'XGetCommand'
/usr/bin/ld: /usr/lib/libBLT.2.4.8.4.a(bltContainer.o): in function 
CmdSearch:(.text+0x625): error: undefined reference to 'XFreeStringList'
/usr/bin/ld: /usr/lib/libBLT.2.4.8.4.a(bltContainer.o): in function 
NameSearch:(.text+0x699): error: undefined reference to 'XFetchName'
/usr/bin/ld: /usr/lib/libBLT.2.4.8.4.a(bltContainer.o): in function 
NameSearch:(.text+0x719): error: undefined reference to 'XFree'
/usr/bin/ld: /usr/lib/libBLT.2.4.8.4.a(bltContainer.o): in function 
ConfigureContainer:(.text+0x99d): error: undefined reference to 
'XTranslateCoordinates'
/usr/bin/ld: /usr/lib/libBLT.2.4.8.4.a(bltContainer.o): in function 
ConfigureContainer:(.text+0x9f0): error: undefined reference to 'XGetGeometry'
/usr/bin/ld: /usr/lib/libBLT.2.4.8.4.a(bltContainer.o): in function 
ConfigureContainer:(.text+0xa0a): error: undefined reference to 'XSync'
/usr/bin/ld: /usr/lib/libBLT.2.4.8.4.a(bltContainer.o): in functi

Bug#644225: marked as done (fonts-khmeros: Transient installation failure)

[Debian Bug Tracking System]

Your message dated Wed, 05 Oct 2011 20:50:53 +
with message-id 
and subject line Bug#644225: fixed in fonts-khmeros 5.0-5
has caused the Debian Bug report #644225,
regarding fonts-khmeros: Transient installation failure
to be marked as done.

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

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


-- 
644225: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=644225
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: fonts-khmeros
Version: 5.0-4
Severity: minor

The first time I tried to install this package just now gave me the following:

Unpacking fonts-khmeros (from .../fonts-khmeros_5.0-4_all.deb) ...
dpkg: error processing /var/cache/apt/archives/fonts-khmeros_5.0-4_all.deb 
(--unpack):
 trying to overwrite '/etc/fonts/conf.d/65-khmer.conf', which is also in 
package ttf-khmeros 5.0-3
configured to not write apport reports

A second attempt was successful.

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

Kernel: Linux 3.0.4-ibid-1 (SMP w/2 CPU cores; PREEMPT)
Locale: LANG=fi_FI.UTF-8, LC_CTYPE=fi_FI.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash

-- no debconf information


--- End Message ---
--- Begin Message ---
Source: fonts-khmeros
Source-Version: 5.0-5

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

fonts-khmeros-udeb_5.0-5_all.udeb
  to main/f/fonts-khmeros/fonts-khmeros-udeb_5.0-5_all.udeb
fonts-khmeros_5.0-5.debian.tar.gz
  to main/f/fonts-khmeros/fonts-khmeros_5.0-5.debian.tar.gz
fonts-khmeros_5.0-5.dsc
  to main/f/fonts-khmeros/fonts-khmeros_5.0-5.dsc
fonts-khmeros_5.0-5_all.deb
  to main/f/fonts-khmeros/fonts-khmeros_5.0-5_all.deb
ttf-khmeros_5.0-5_all.deb
  to main/f/fonts-khmeros/ttf-khmeros_5.0-5_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 644...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Christian Perrier  (supplier of updated fonts-khmeros 
package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Format: 1.8
Date: Wed, 05 Oct 2011 21:45:56 +0200
Source: fonts-khmeros
Binary: fonts-khmeros fonts-khmeros-udeb ttf-khmeros
Architecture: source all
Version: 5.0-5
Distribution: unstable
Urgency: low
Maintainer: Debian Fonts Task Force 
Changed-By: Christian Perrier 
Description: 
 fonts-khmeros - KhmerOS Unicode fonts for the Khmer language of Cambodia
 fonts-khmeros-udeb - Debian-Installer font for the Khmer language of Cambodia 
(udeb)
 ttf-khmeros - transitional dummy package
Closes: 644225
Changes: 
 fonts-khmeros (5.0-5) unstable; urgency=low
 .
   * Add proper Replaces, Conflicts, Provides fields for transition
 with ttf-khmeros. Closes: #644225
Checksums-Sha1: 
 4f4cfe86860319460d6f67a4db281f6741f111c9 1951 fonts-khmeros_5.0-5.dsc
 04fcb7ae8e9eca6778ec519519db62c338839e71 593490 fonts-khmeros_5.0.orig.tar.bz2
 89ae7826c7dca47da2529d7a93d3217c34c72f08 3371 fonts-khmeros_5.0-5.debian.tar.gz
 123bdc22b28ecbeb6cd298b0e573fc7f167ae5f3 943644 fonts-khmeros_5.0-5_all.deb
 45036f9437b290c5a2e16eed52a094dc6ae6bc0e 107794 
fonts-khmeros-udeb_5.0-5_all.udeb
 000d7b01f77cf65e95e578451be8c8e05276c982 3130 ttf-khmeros_5.0-5_all.deb
Checksums-Sha256: 
 5e559d844b0fb63f4203b677b6f7c90478d62096cce4f54b8ed78d73615a94b4 1951 
fonts-khmeros_5.0-5.dsc
 9be5e6b10ac79f0b9dbfccff149b6d3771425e0b0390b3d1ac221be2f88491fc 593490 
fonts-khmeros_5.0.orig.tar.bz2
 5fa6e02ec33485d1b028526a16b3fc26753b3fe361a86d7148930c6abe63935f 3371 
fonts-khmeros_5.0-5.debian.tar.gz
 f99695d9820e33775a0fd35a49d05b8d0106d8b5234880c432e9cabfc4e14572 943644 
fonts-khmeros_5.0-5_all.deb
 0f193c740b6b304547ef5d42adc41cbc9fb2ff41ee5cadd68d260caee165ddac 107794 
fonts-khmeros-udeb_5.0-5_all.udeb
 6110b070c3884f8c1dbc8db29cb033febf75cca79914714b4b56315435262cbc 3130 
ttf-khmeros_5.0-5_all.deb
Files: 
 be8942a91eaaa30427fbf46c9cc79e27 1951 fonts optional fonts-khmeros_5.0-5.dsc
 c9757d27994388cbc5098dfbdabca0f7 593490 fonts optional 
fonts-khmeros_5.0.orig.tar.bz2
 8c07844b078b59bb516fb439224bd075 3371 fonts optional 
fonts-khmeros_5.0-5.debian.tar.gz
 1e73fb28e7cff6ad0fa01829

Bug#644431: theunarchiver: FTBFS(kfreebsd): undefined reference to `reallocf'

[Matt Kraai]

Hi,

On Wed, Oct 05, 2011 at 09:36:16PM +0200, Christoph Egger wrote:
> Your package failed to build on the kfreebsd-* buildds:
> 
> make[3]: Leaving directory 
> `/build/buildd-theunarchiver_2.7.1-2-kfreebsd-amd64-xipvuN/theunarchiver-2.7.1/UniversalDetector'
> gcc -Wl,--whole-archive -fexceptions -fgnu-runtime -o unar unar.o 
> CSCommandLineParser.o CommandLineCommon.o NSStringPrinting.o libXADMaster.a 
> ../UniversalDetector/libUniversalDetector.a -Wl,--no-whole-archive 
> -lgnustep-base -lcrypto -lbz2 -lz -licuuc -lobjc -lstdc++ -lm
> libXADMaster.a(XADPrefixCode.o): In function `NewNode':
> /build/buildd-theunarchiver_2.7.1-2-kfreebsd-amd64-xipvuN/theunarchiver-2.7.1/XADMaster/XADPrefixCode.m:42:
>  undefined reference to `reallocf'
> /build/buildd-theunarchiver_2.7.1-2-kfreebsd-amd64-xipvuN/theunarchiver-2.7.1/XADMaster/XADPrefixCode.m:42:
>  undefined reference to `reallocf'
> /build/buildd-theunarchiver_2.7.1-2-kfreebsd-amd64-xipvuN/theunarchiver-2.7.1/XADMaster/XADPrefixCode.m:42:
>  undefined reference to `reallocf'
> /build/buildd-theunarchiver_2.7.1-2-kfreebsd-amd64-xipvuN/theunarchiver-2.7.1/XADMaster/XADPrefixCode.m:42:
>  undefined reference to `reallocf'
> /build/buildd-theunarchiver_2.7.1-2-kfreebsd-amd64-xipvuN/theunarchiver-2.7.1/XADMaster/XADPrefixCode.m:42:
>  undefined reference to `reallocf'
> libXADMaster.a(XADSkipHandle.o):/build/buildd-theunarchiver_2.7.1-2-kfreebsd-amd64-xipvuN/theunarchiver-2.7.1/XADMaster/XADSkipHandle.m:137:
>  more undefined references to `reallocf' follow
> collect2: ld returned 1 exit status
> make[2]: *** [unar] Error 1
> make[2]: Leaving directory 
> `/build/buildd-theunarchiver_2.7.1-2-kfreebsd-amd64-xipvuN/theunarchiver-2.7.1/XADMaster'
> make[1]: *** [override_dh_auto_build] Error 2
> make[1]: Leaving directory 
> `/build/buildd-theunarchiver_2.7.1-2-kfreebsd-amd64-xipvuN/theunarchiver-2.7.1'
> make: *** [build] Error 2

This has already been fixed upstream by removing the use of reallocf.

I think the best solution for theunarchiver package is to change the
new test in define-reallocf-on-GNU-Hurd to

 #if !defined BSD || defined __GNU__

I'll probably do so this evening.

-- 
Matt Kraai
https://ftbfs.org/kraai



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

Processed: r3932 - packages/fonts-khmeros/trunk/debian

[Debian Bug Tracking System]

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

> tags 644225 pending
Bug #644225 [fonts-khmeros] fonts-khmeros: Transient installation failure
Added tag(s) pending.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
644225: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=644225
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#644432: [python-pytrilinos] Depends on python2.6 but 2.7 is now in unstable

[Dietrich Brunn]

Package: python-pytrilinos
Version: 10.4.0.dfsg-1 
Severity: grave

--- Please enter the report below this line. ---
Hi,
python-pytrilinos depends on python <2.7, but Version 2.7 is now in unstable.
 Hence, this package is not installable and also python-dolfin (fenics) is not 
installable either.

Cheers, dietrich

--- System information. ---
Architecture: amd64
Kernel:   Linux 3.0.0-1-amd64

Debian Release: wheezy/sid
  500 unstableftp.debian-multimedia.org 
  500 unstableftp.de.debian.org 
  500 testing ftp.de.debian.org 
1 experimentalftp.de.debian.org 

--- Package information. ---
Depends  (Version) | Installed
==-+-==
python-numpy   | 1:1.5.1-3
libtrilinos  (= 10.4.0.dfsg-1) | 10.4.0.dfsg-1
libblas3gf | 1.2.20110419-2
 OR libblas.so.3gf | 
 OR libatlas3gf-base   | 3.8.4-3
libc6   (>= 2.2.5) | 2.13-21
libgcc1   (>= 1:4.1.1) | 1:4.6.1-13
liblapack3gf   | 3.3.1-1
 OR liblapack.so.3gf   | 
 OR libatlas3gf-base   | 3.8.4-3
libopenmpi1.3  | 1.4.3-2.1
libstdc++6  (>= 4.1.1) | 4.6.1-13
python(<< 2.7) | 2.7.2-7
python(>= 2.6) | 2.7.2-7
python-central (>= 0.6.11) | 0.6.17
python2.6  | 2.6.7-4


Package's Recommends field is empty.

Package's Suggests field is empty.








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

Bug#644431: theunarchiver: FTBFS(kfreebsd): undefined reference to `reallocf'

[Christoph Egger]

Package: src:theunarchiver
Version: 2.7.1-2
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:

make[3]: Leaving directory 
`/build/buildd-theunarchiver_2.7.1-2-kfreebsd-amd64-xipvuN/theunarchiver-2.7.1/UniversalDetector'
gcc -Wl,--whole-archive -fexceptions -fgnu-runtime -o unar unar.o 
CSCommandLineParser.o CommandLineCommon.o NSStringPrinting.o libXADMaster.a 
../UniversalDetector/libUniversalDetector.a -Wl,--no-whole-archive 
-lgnustep-base -lcrypto -lbz2 -lz -licuuc -lobjc -lstdc++ -lm
libXADMaster.a(XADPrefixCode.o): In function `NewNode':
/build/buildd-theunarchiver_2.7.1-2-kfreebsd-amd64-xipvuN/theunarchiver-2.7.1/XADMaster/XADPrefixCode.m:42:
 undefined reference to `reallocf'
/build/buildd-theunarchiver_2.7.1-2-kfreebsd-amd64-xipvuN/theunarchiver-2.7.1/XADMaster/XADPrefixCode.m:42:
 undefined reference to `reallocf'
/build/buildd-theunarchiver_2.7.1-2-kfreebsd-amd64-xipvuN/theunarchiver-2.7.1/XADMaster/XADPrefixCode.m:42:
 undefined reference to `reallocf'
/build/buildd-theunarchiver_2.7.1-2-kfreebsd-amd64-xipvuN/theunarchiver-2.7.1/XADMaster/XADPrefixCode.m:42:
 undefined reference to `reallocf'
/build/buildd-theunarchiver_2.7.1-2-kfreebsd-amd64-xipvuN/theunarchiver-2.7.1/XADMaster/XADPrefixCode.m:42:
 undefined reference to `reallocf'
libXADMaster.a(XADSkipHandle.o):/build/buildd-theunarchiver_2.7.1-2-kfreebsd-amd64-xipvuN/theunarchiver-2.7.1/XADMaster/XADSkipHandle.m:137:
 more undefined references to `reallocf' follow
collect2: ld returned 1 exit status
make[2]: *** [unar] Error 1
make[2]: Leaving directory 
`/build/buildd-theunarchiver_2.7.1-2-kfreebsd-amd64-xipvuN/theunarchiver-2.7.1/XADMaster'
make[1]: *** [override_dh_auto_build] Error 2
make[1]: Leaving directory 
`/build/buildd-theunarchiver_2.7.1-2-kfreebsd-amd64-xipvuN/theunarchiver-2.7.1'
make: *** [build] Error 2

Full build log at
https://buildd.debian.org/status/fetch.php?pkg=theunarchiver&arch=kfreebsd-amd64&ver=2.7.1-2&stamp=1317795384

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#643412: marked as done (jack-keyboard: FTBFS: jack-keyboard.c:261:2: error: format not a string literal and no format arguments [-Werror=format-security])

[Debian Bug Tracking System]

Your message dated Wed, 05 Oct 2011 19:33:05 +
with message-id 
and subject line Bug#643412: fixed in jack-keyboard 2.6-2
has caused the Debian Bug report #643412,
regarding jack-keyboard: FTBFS: jack-keyboard.c:261:2: 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.)


-- 
643412: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=643412
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: jack-keyboard
Version: 2.6-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:
> /usr/bin/cc  -DHAVE_JACK=1 -DHAVE_X11=1 -g -O2 -fstack-protector 
> --param=ssp-buffer-size=4 -D_FORTIFY_SOURCE=2 -Wformat -Wformat-security 
> -Werror=format-security -Wall -I/usr/include/gtk-2.0 -I/usr/include/freetype2 
> -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include 
> -I/usr/include/gdk-pixbuf-2.0 -I/usr/lib/x86_64-linux-gnu/gtk-2.0/include 
> -I/usr/include/cairo -I/usr/include/pango-1.0 -I/usr/include/atk-1.0-o 
> CMakeFiles/jack-keyboard.dir/src/jack-keyboard.c.o   -c 
> /build/jack-keyboard-hYgQDt/jack-keyboard-2.6/src/jack-keyboard.c
> /build/jack-keyboard-hYgQDt/jack-keyboard-2.6/src/jack-keyboard.c: In 
> function 'warning_async':
> /build/jack-keyboard-hYgQDt/jack-keyboard-2.6/src/jack-keyboard.c:261:2: 
> error: format not a string literal and no format arguments 
> [-Werror=format-security]
> /build/jack-keyboard-hYgQDt/jack-keyboard-2.6/src/jack-keyboard.c: In 
> function 'init_gtk_1':
> /build/jack-keyboard-hYgQDt/jack-keyboard-2.6/src/jack-keyboard.c:1545:3: 
> warning: reading through null pointer (argument 3) [-Wformat]
> /build/jack-keyboard-hYgQDt/jack-keyboard-2.6/src/jack-keyboard.c: In 
> function 'log_handler':
> /build/jack-keyboard-hYgQDt/jack-keyboard-2.6/src/jack-keyboard.c:1683:4: 
> error: format not a string literal and no format arguments 
> [-Werror=format-security]
> cc1: some warnings being treated as errors
> 
> make[3]: *** [CMakeFiles/jack-keyboard.dir/src/jack-keyboard.c.o] Error 1

The full build log is available from:
   
http://people.debian.org/~lucas/logs/2011/09/23/jack-keyboard_2.6-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: jack-keyboard
Source-Version: 2.6-2

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

jack-keyboard_2.6-2.debian.tar.gz
  to main/j/jack-keyboard/jack-keyboard_2.6-2.debian.tar.gz
jack-keyboard_2.6-2.dsc
  to main/j/jack-keyboard/jack-keyboard_2.6-2.dsc
jack-keyboard_2.6-2_amd64.deb
  to main/j/jack-keyboard/jack-keyboard_2.6-2_amd64.deb



A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 643...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Alessio Treglia  (supplier of updated jack-keyboard package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Format: 1.8
Date: Wed, 05 Oct 2011 21:15:57 +0200
Source: jack-keyboard
Binary: jack-keyboard
Architecture: source amd64
Version: 2.6-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Multimedia Maintainers 

Changed-By: Alessio Treglia 
Description: 
 jack-keyboard - Virtual MIDI keyboard for JACK MIDI
Closes: 643412
Changes: 
 jack-keyboard (2.6-2) unstable; urgency=medium
 .
   * Fix "format not a string literal and no format arguments"
 errors. (Closes: #643412)
Checksums-Sha1: 
 4c34c871fb8e76cc42ea754a40656a7ad5582904 1476 jack-keyboard_2.6-2.dsc
 b371e6fce5f6aaff67d04ff08a

Bug#644389: suspect non-working mdadm.conf created during install

[pille]

So it looks like during install time, in d-i, the system were named "hetzer" 
(most likely
due to DHCP), and all md arrays were created using that name.  And later on, it 
fails to
boot with actual hostname.


i' don't know if it's the initramfs shipped with d-i, but today i did an 
offline install. no net, no DHCP, no hetzner datacenter.
i completely understand what happens as i'm able to boot the system by 
manually assembling the array and fixing the problem, but how the wrong 
hostname slips into the initramfs should be investigated by debians devs.


> Note that mdadm.conf in initrd contains name "hetzer", while

actual arrays are named "file".


that's what i'm talking about.


Is your real hostname "file" ?


yes.


  pille



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

Bug#635548: CVE-2011-2716

[Nico Golde]

Hi,
* Michael Tokarev  [2011-10-05 20:44]:
> I'm Cc'ing the relevant bug# so others may see this information.
> Hopefully you wont object -- the bug is public for a long time.

No, not at all.

> On 05.10.2011 16:04, Nico Golde wrote:
> > * Nico Golde  [2011-10-05 11:21]:
> >> * Michael Tokarev  [2011-10-05 10:34]:
> >>> On 05.10.2011 02:42, Nico Golde wrote:
>  Hi,
>  can you tell me if CVE-2011-2716 is a problem with a default 
>  busybox or only in case there are additional shell scripts 
>  that make use of the untrusted host name?
> >>>
> >>> Busybox itself does not really work in this case: an additional
> >>> shell script is _required_ for DHCP functionality, since busybox
> >>> executes a shell script to do the real work, and, in particular,
> >>> to set up host name etc.  The default script supplied with the
> >>> package is not affected.
> > 
> > (/debian/tree/busybox-udeb/usr/share/udhcpc/default.script) and was 
> > wondering 
> > if the domain name is safe to use. I see it is the only unquoted variable 
> > in 
> > this script. Can you comment on this? I have to admit that I don't know the 
> 
> Actually it was me who looked into the wrong script - I looked into the
> version installed on my system, which is modified by me long ago.  That
> version does not use any of the "bad" variables at all.

Partly the same here, I also looked into the wrong one.
I looked into the one of the udeb.

> You're right, the actual script in the dhcpc package refers to $domain
> variable - the only variable referenced in this script which may be
> insecure.
> 
> But you're not correct that the variable is used unquoted.  Here's the
> actual code:
> 
> # Update resolver configuration file
> R=""
> [ -n "$domain" ] && R="domain $domain
> "
> for i in $dns; do
> echo "$0: Adding DNS $i"
> R="${R}nameserver $i
> "
> done
> 
> if [ -x /sbin/resolvconf ]; then
> echo -n "$R" | resolvconf -a "${interface}.udhcpc"
> else
> echo -n "$R" > "$RESOLV_CONF"
> fi
> ;;
> 
> So, in all cases the variable is enclosed in double quotes.

Yes this look secure. What about the udeb script?
/debian/tree/busybox-udeb/usr/share/udhcpc/default.script:
do_resolv_conf() {
local cfg=/etc/resolv.conf

if [ -n "$domain" ] || [ -n "$dns" ]; then
echo -n > $cfg
if [ -n "$domain" ]; then
echo search $domain >> $cfg
fi

for i in $dns ; do
echo nameserver $i >> $cfg
done
fi
}

Not quoted in thsi case.

> There's just one possible problem with this: it is possible to
> inject bad - eg, syntactically incorrect - content into /etc/resolv.conf.
> I'm not really sure if glibc's resolver will cope with any and all
> garbage found in /etc/resolv.conf, but its parser is very simple and
> just ignores everything that it does not understand.

I think it's no big problem. Even if this could be a DoS scenario it would be a
rather obscure one.

> It is definitely not possible to execute (shell) code "embedded" in
> ${domain} variable - at least not from the udhcpc script quoted above.
> Also, the only place where content of a single "insecure" variable is
> used is /etc/resolv.conf (which is already controlled by an rogue dhcp
> server anyway, to a large extent) - eg, the default script does not set
> system hostname to the string supplied by dhcp server.

Ok makes sense, thanks for the explanation.

> > inner workings of the dhcpc in combination with the surrounded scripts very 
> > well so please bear with me :)
> 
> There's nothing to know about really: dhcpcd converts every known option
> found in dhcp reply packet into an environment variable, without any
> content checking/filtering whatsoever.  There are 2 most common types
> of options: it is either a (list of) IP address(es), which are passed as
> 4-byte binaries and hence cannot contain bad strings at all (they're
> converted into 1.2.3.4 - octet - form by udhcpc) - these are $broadcast,
> $subnet, $router, $dns.  And the other common type is string - a sequence
> of any characters.  One of these is $domain, there are others like
> $hostname.
> 
> And all this stuff gets passed to the script, which may deal with them
> in any way.

In this case even an unquoted $domain is probably no problem.
E.g.:
$ domain='`id`'
$ echo $domain
`id`

> Note that in theory it is possible to have some other script - e.g. a
> script executed by resolvconf from /etc/resolv.d/* directories - which
> uses the same variables without clearing their contents.  But this is
> a different story, and that'd be a definitive bug in these scripts,
> with or without a rogue dhcp server.

I totally agree on this.
Thanks again for the update!

Cheers
Nico
-- 
Nico Golde - http://www.ngolde.de - n...@jabber.ccc.de - GPG: 0xA0A0
For security reasons,

Processed: your mail

[Debian Bug Tracking System]

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

> severity 613121 serious
Bug #613121 [vlc] /usr/share/doc/vlc is empty
Severity set to 'serious' from 'normal'

> merge 613121 640285
Bug#613121: /usr/share/doc/vlc is empty
Bug#640285: vlc has no copyright information (doc directory is empty)
Merged 613121 640285.

> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
640285: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=640285
613121: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=613121
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#644423: libterm-readline-gnu-perl: FTBFS: Could not find neither libtermcap.a, libncurses.a, or libcurses.

[Sven Joachim]

On 2011-10-05 20:50 +0200, Sven Joachim wrote:

> ,
> |  debian/rules build
> | dh build
> |dh_testdir
> |dh_auto_configure
> | Could not find neither libtermcap.a, libncurses.a, or libcurses.
> | dh_auto_configure: perl Makefile.PL INSTALLDIRS=vendor create_packlist=0 
> returned exit code 1
> | make: *** [build] Error 2
> `
>
> The reason is that libreadline-dev has stopped depending on
> libncurses5-dev in 6.2-6, and libterm-readline-gnu-perl does not
> build-depend on libncurses5-dev itself.
>
> Possible solutions:
>
> 1) Build-depend on libncurses5-dev;
>
> 2) Patch Makefile.PL to try -ltinfo in preference over -ltermcap,
>-lcurses or -lncurses;
>
> 3) Wait for libtinfo-dev to take over the libtermcap.{a,so} symlinks
>from libncurses5-dev.

For the record, I have just proposed 3) in #644426, but don't hold your
breath.

Cheers,
   Sven



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

Bug#644146: marked as done (Double free in C++ destructor)

[Debian Bug Tracking System]

Your message dated Wed, 05 Oct 2011 19:18:42 +
with message-id 
and subject line Bug#643024: fixed in libffado 2.0.99+svn1995-2
has caused the Debian Bug report #643024,
regarding Double free in C++ destructor
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.)


-- 
643024: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=643024
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: libffado2
Version: 2.0.99+svn1995-1

A program that is linked with libffado aborts on exit.  This command
reproduces the problem:

echo 'int main() {}' |gcc -x c -lffado - && ./a.out

Command output follows (amd64):

Cannot create thread 1 Operation not permitted
Cleaning up leftover debug module: DeviceManager
*** glibc detected *** ./a.out: free(): invalid pointer: 0x7fc333e1f9c0 ***
=== Backtrace: =
/lib/x86_64-linux-gnu/libc.so.6(+0x72606)[0x7fc333924606]
/lib/x86_64-linux-gnu/libc.so.6(cfree+0x6c)[0x7fc33392933c]
/usr/lib/libffado.so.2(_ZN18DebugModuleManagerD2Ev+0x81)[0x7fc333cf33e1]
/usr/lib/libffado.so.2(+0xbb236)[0x7fc333cf1236]
/lib64/ld-linux-x86-64.so.2(+0xe21c)[0x7fc333e2f21c]
/lib/x86_64-linux-gnu/libc.so.6(+0x36d82)[0x7fc3338e8d82]
/lib/x86_64-linux-gnu/libc.so.6(+0x36dd5)[0x7fc3338e8dd5]
/lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0x104)[0x7fc3338d0eb4]
./a.out[0x4004f9]
=== Memory map: 
0040-00401000 r-xp  00:13 34146  
/tmp/a.out
00401000-00402000 rw-p  00:13 34146  
/tmp/a.out
01364000-01385000 rw-p  00:00 0  [heap]
7fc32c00-7fc32c021000 rw-p  00:00 0 
7fc32c021000-7fc33000 ---p  00:00 0 
7fc330335000-7fc330336000 ---p  00:00 0 
7fc330336000-7fc330d37000 rw-p  00:00 0 
7fc330d37000-7fc330d73000 r-xp  08:02 4849738
/lib/x86_64-linux-gnu/libpcre.so.3.12.1
7fc330d73000-7fc330f72000 ---p 0003c000 08:02 4849738
/lib/x86_64-linux-gnu/libpcre.so.3.12.1
7fc330f72000-7fc330f73000 rw-p 0003b000 08:02 4849738
/lib/x86_64-linux-gnu/libpcre.so.3.12.1
7fc330f73000-7fc330f76000 r-xp  08:02 797451 
/usr/lib/libgmodule-2.0.so.0.2800.6
7fc330f76000-7fc331175000 ---p 3000 08:02 797451 
/usr/lib/libgmodule-2.0.so.0.2800.6
7fc331175000-7fc331176000 rw-p 2000 08:02 797451 
/usr/lib/libgmodule-2.0.so.0.2800.6
7fc331176000-7fc33118d000 r-xp  08:02 799367 
/usr/lib/libz.so.1.2.3.4
7fc33118d000-7fc33138c000 ---p 00017000 08:02 799367 
/usr/lib/libz.so.1.2.3.4
7fc33138c000-7fc33138d000 rw-p 00016000 08:02 799367 
/usr/lib/libz.so.1.2.3.4
7fc33138d000-7fc33138f000 r-xp  08:02 4850295
/lib/x86_64-linux-gnu/libdl-2.13.so
7fc33138f000-7fc33158f000 ---p 2000 08:02 4850295
/lib/x86_64-linux-gnu/libdl-2.13.so
7fc33158f000-7fc33159 r--p 2000 08:02 4850295
/lib/x86_64-linux-gnu/libdl-2.13.so
7fc33159-7fc331591000 rw-p 3000 08:02 4850295
/lib/x86_64-linux-gnu/libdl-2.13.so
7fc331591000-7fc3315a6000 r-xp  08:02 4849679
/lib/x86_64-linux-gnu/libgcc_s.so.1
7fc3315a6000-7fc3317a6000 ---p 00015000 08:02 4849679
/lib/x86_64-linux-gnu/libgcc_s.so.1
7fc3317a6000-7fc3317a7000 rw-p 00015000 08:02 4849679
/lib/x86_64-linux-gnu/libgcc_s.so.1
7fc3317a7000-7fc331828000 r-xp  08:02 4850218
/lib/x86_64-linux-gnu/libm-2.13.so
7fc331828000-7fc331a27000 ---p 00081000 08:02 4850218
/lib/x86_64-linux-gnu/libm-2.13.so
7fc331a27000-7fc331a28000 r--p 0008 08:02 4850218
/lib/x86_64-linux-gnu/libm-2.13.so
7fc331a28000-7fc331a29000 rw-p 00081000 08:02 4850218
/lib/x86_64-linux-gnu/libm-2.13.so
7fc331a29000-7fc331b15000 r-xp  08:02 1189696
/usr/lib/x86_64-linux-gnu/libstdc++.so.6.0.16
7fc331b15000-7fc331d14000 ---p 000ec000 08:02 1189696
/usr/lib/x86_64-linux-gnu/libstdc++.so.6.0.16
7fc331d14000-7fc331d1c000 r--p 000eb000 08:02 1189696
/usr/lib/x86_64-linux-gnu/libstdc++.so.6.0.16
7fc331d1c000-7fc331d1e000 rw-p 000f3000 08:02 1189696
/usr/lib/x86_64-linux-gnu/libstdc++.so.6.0.16
7fc331d1e000-7fc331d33000 rw-p  00:00 0 
7fc331d33000-7fc331e23000 r-xp  08:02 4849897
/lib/libglib

Bug#643024: marked as done (libffado2: jackd can't start with libffado version 2.0.99+svn1995-1)

[Debian Bug Tracking System]

Your message dated Wed, 05 Oct 2011 19:18:42 +
with message-id 
and subject line Bug#643024: fixed in libffado 2.0.99+svn1995-2
has caused the Debian Bug report #643024,
regarding libffado2: jackd can't start with libffado version 2.0.99+svn1995-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.)


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

Dear Maintainer,

When I have tried to start jackd the following lines was printed :

ckdmp 1.9.7
Copyright 2001-2005 Paul Davis and others.
Copyright 2004-2011 Grame.
jackdmp comes with ABSOLUTELY NO WARRANTY
This is free software, and you are welcome to redistribute it
under certain conditions; see the file COPYING for details
Cleaning up leftover debug module: DeviceManager
*** glibc detected *** jackd: free(): invalid pointer: 0xb73db63c ***
=== Backtrace: =
/lib/i386-linux-gnu/i686/cmov/libc.so.6(+0x6aac1)[0xb7449ac1]
/lib/i386-linux-gnu/i686/cmov/libc.so.6(+0x6c328)[0xb744b328]
/lib/i386-linux-gnu/i686/cmov/libc.so.6(cfree+0x6d)[0xb744e3dd]
/usr/lib/i386-linux-gnu/libstdc++.so.6(_ZdlPv+0x1f)[0xb771bb5f]
=== Memory map: 
08048000-0804d000 r-xp  fe:02 5473527/usr/bin/jackd
0804d000-0804e000 rw-p 5000 fe:02 5473527/usr/bin/jackd
0853c000-0855d000 rw-p  00:00 0  [heap]
b630-b6321000 rw-p  00:00 0
b6321000-b640 ---p  00:00 0
b644e000-b644f000 ---p  00:00 0
b644f000-b6e5 rw-p  00:00 0
b6e5-b6e8c000 r-xp  fe:00 459082 /lib/i386-linux-
gnu/libpcre.so.3.12.1
b6e8c000-b6e8d000 rw-p 0003b000 fe:00 459082 /lib/i386-linux-
gnu/libpcre.so.3.12.1
b6e8d000-b6e9 r-xp  fe:02 9475036
/usr/lib/libgmodule-2.0.so.0.2800.6
b6e9-b6e91000 rw-p 2000 fe:02 9475036
/usr/lib/libgmodule-2.0.so.0.2800.6
b6e91000-b6ea4000 r-xp  fe:02 3736123/usr/lib/libz.so.1.2.3.4
b6ea4000-b6ea5000 rw-p 00013000 fe:02 3736123/usr/lib/libz.so.1.2.3.4
b6ea5000-b6f7d000 r-xp  fe:00 459183 /lib/libglib-2.0.so.0.2800.6
b6f7d000-b6f7e000 rw-p 000d8000 fe:00 459183 /lib/libglib-2.0.so.0.2800.6
b6fa7000-b6fab000 r-xp  fe:02 9475131
/usr/lib/libgthread-2.0.so.0.2800.6
b6fab000-b6fac000 rw-p 3000 fe:02 9475131
/usr/lib/libgthread-2.0.so.0.2800.6
b6fac000-b6ff3000 r-xp  fe:02 5769146
/usr/lib/libgobject-2.0.so.0.2800.6
b6ff3000-b6ff5000 rw-p 00046000 fe:02 5769146
/usr/lib/libgobject-2.0.so.0.2800.6
b6ff5000-b7058000 r-xp  fe:02 9437331
/usr/lib/libglibmm-2.4.so.1.3.0
b7058000-b705a000 rw-p 00062000 fe:02 9437331
/usr/lib/libglibmm-2.4.so.1.3.0
b705a000-b71a3000 r-xp  fe:02 9438207/usr/lib/libxml2.so.2.7.8
b71a3000-b71a8000 rw-p 00149000 fe:02 9438207/usr/lib/libxml2.so.2.7.8
b71a8000-b71a9000 rw-p  00:00 0
b71a9000-b71cb000 r-xp  fe:02 9438765/usr/lib/libxml++-2.6.so.2.0.7
b71cb000-b71cc000 rw-p 00022000 fe:02 9438765/usr/lib/libxml++-2.6.so.2.0.7
b71cc000-b71e r-xp  fe:02 9474676/usr/lib/libconfig++.so.8.0.0
b71e-b71e1000 rw-p 00014000 fe:02 9474676/usr/lib/libconfig++.so.8.0.0
b71e1000-b73ce000 r-xp  fe:02 9437350/usr/lib/libffado.so.2.999.0
b73ce000-b73dc000 rw-p 001ed000 fe:02 9437350/usr/lib/libffado.so.2.999.0
b73dc000-b73df000 rw-p  00:00 0
b73df000-b7532000 r-xp  fe:00 458908 /lib/i386-linux-
gnu/i686/cmov/libc-2.13.so
b7532000-b7533000 ---p 00153000 fe:00 458908 /lib/i386-linux-
gnu/i686/cmov/libc-2.13.so
b7533000-b7535000 r--p 00153000 fe:00 458908 /lib/i386-linux-
gnu/i686/cmov/libc-2.13.so
b7535000-b7536000 rw-p 00155000 fe:00 458908 /lib/i386-linux-
gnu/i686/cmov/libc-2.13.so
b7536000-b7539000 rw-p  00:00 0
b7539000-b7555000 r-xp  fe:00 458929 /lib/i386-linux-
gnu/libgcc_s.so.1
b7555000-b7556000 rw-p 0001b000 fe:00 458929 /lib/i386-linux-
gnu/libgcc_s.so.1
b7556000-b7557000 rw-p  00:00 0
b7557000-b757b000 r-xp  fe:00 458844 /lib/i386-linux-
gnu/i686/cmov/libm-2.13.so
b757b000-b757c000 r--p 00023000 fe:00 458844 /lib/i386-linux-
gnu/i686/cmov/libm-2.13.so
b757c000-b757d000 rw-p 00024000 fe:00 458844 /lib/i386-linux-
gnu/i686/cmov/libm-2.13.so
b757d000-b75c5000 r-xp  fe:00 458794 /lib/i386-linux-
gnu/libdbus-1.so.3.5.8
b75c5000-b75c6000 r--p 00048000 fe:00 458794 /lib/i386-linux-
gnu/libdbus-1.so.3.5.8
b75c6000-b75c7000 rw-p 00049000 fe:00 45879

Processed: tagging 643412

[Debian Bug Tracking System]

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

> tags 643412 + pending
Bug #643412 [src:jack-keyboard] jack-keyboard: FTBFS: jack-keyboard.c:261:2: 
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.
-- 
643412: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=643412
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#554556: marked as done (FTBFS with binutils-gold)

[Jakub Wilk]

* Christian T. Steigies , 2011-10-05, 20:24:
Tried to build your package and it fails to build with GNU 
binutils-gold.

The version in unstable builds fine against binutils-gold.

Sorry, I can not reproduce your finding on amd64.


Interesting. Indeed, it fails to build on amd64. However, before closing 
the bug I tried it on i386, where it builds successfully. The relevant 
line from i386 buid log[0] is:


g++ -Wl,-O1 -o ../../build/bin/qgle objects/about.o objects/amove.o objects/arc.o objects/circle.o objects/colourbutton.o objects/colourpicker.o objects/component.o objects/consolewindow.o objects/drawingobject.o objects/ellipse.o objects/fileinfo.o objects/gledrawing.o objects/grid.o objects/line.o objects/main.o objects/mainwindow.o objects/newfile.o objects/polararray.o objects/propertyeditor.o objects/propertymodel.o objects/qgle_statics.o objects/qgs.o objects/qgslibloader.o objects/serverthread.o objects/settings.o objects/settings_dialogue.o objects/snapline.o objects/text.o objects/variantdelegate.o objects/objectblocks.o objects/dialogues.o objects/moc_about.o objects/moc_amove.o objects/moc_arc.o objects/moc_circle.o objects/moc_colourbutton.o objects/moc_colourpicker.o objects/moc_component.o objects/moc_consolewindow.o objects/moc_drawingobject.o objects/moc_ellipse.o objects/moc_gledrawing.o objects/moc_grid.o objects/moc_line.o objects/moc_mainwindow.o objects/moc_newfile.o objects/moc_polararray.o objects/moc_propertyeditor.o objects/moc_propertymodel.o objects/moc_qgs.o objects/moc_serverthread.o objects/moc_settings.o objects/moc_settings_dialogue.o objects/moc_snapline.o objects/moc_text.o objects/moc_variantdelegate.o objects/moc_objectblocks.o objects/moc_dialogues.o objects/qrc_qgle.o-L/usr/lib -ldl -lgle-graphics-4.2.2 -L../../build/lib/ -lQtGui -lQtNetwork -lQtCore -lpthread 


As you see, -ldl is there.


Are you sure you have binutils-gold installed?


Yes. But anyway, sorry for the noise!


[0] 
https://buildd.debian.org/status/fetch.php?pkg=gle-graphics&arch=i386&ver=4.2.2-4%2Bb2&stamp=1316278910

--
Jakub Wilk



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

Bug#644389: suspect non-working mdadm.conf created during install

[Michael Tokarev]

On 05.10.2011 22:53, pille wrote:
>> In this case there is very little I can do. I have done multiple
>> squeeze installs with RAID, and upgrades, and I have not seen this
>> problem. Unless you can reproduce this bug, I cannot do anything but
>> keep this report open.
> 
> i've just reproduced such a failing install inside a KVM.
> see (combined) screenshot attached from first boot.
> 
> i've snapshotted the VM at different stages and can provide you with one that 
> just boots for the first time (snapshot3, see screenshot).
> tell me if you're interrested in investigating it.
> 
> 
> here's a log of what i did:
> 
> booted 
> http://cdimage.debian.org/debian-cd/current-live/amd64/iso-hybrid/debian-live-6.0.2-amd64-rescue.iso
>  (sha1=0e5d9409719e657de4cbd9f355545cdc4c869038)
> expert text install
> selected some udebs (parted, reiserfs, squash, virtio)
> hostname = file.lan
> partition
>   manual
> for all 4 disks:
>   GPT
>   p1: 6MB   BIOS BOOT
>   p2: 250MB RAID1 BOOT
>   p3: 768MB SWAP
>   p4: 3.3GB RAID6 VG/PV
> configure sw raid:
>   md0: RAID1 /dev/sd[a-d]2: /boot (ext2)
>   md1: RAID6 /dev/sd[a-d]4: LVM PV (VG=vg-sys)
> configure LVM:
>   LV system: /dev/md1 (4GB) / (reiserfs)
> snapshot1
> install system (normal)
> install grub
> finish
> snapshot2
> reboot
> snapshot3

So it looks like during install time, in d-i, the system were named "hetzer" 
(most likely
due to DHCP), and all md arrays were created using that name.  And later on, it 
fails to
boot with actual hostname.  Note that mdadm.conf in initrd contains name 
"hetzer", while
actual arrays are named "file".

Is your real hostname "file" ?

/mjt



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

Bug#644389: suspect non-working mdadm.conf created during install

[pille]

In this case there is very little I can do. I have done multiple
squeeze installs with RAID, and upgrades, and I have not seen this
problem. Unless you can reproduce this bug, I cannot do anything but
keep this report open.


i've just reproduced such a failing install inside a KVM.
see (combined) screenshot attached from first boot.

i've snapshotted the VM at different stages and can provide you with one 
that just boots for the first time (snapshot3, see screenshot).

tell me if you're interrested in investigating it.


here's a log of what i did:

booted 
http://cdimage.debian.org/debian-cd/current-live/amd64/iso-hybrid/debian-live-6.0.2-amd64-rescue.iso 
(sha1=0e5d9409719e657de4cbd9f355545cdc4c869038)

expert text install
selected some udebs (parted, reiserfs, squash, virtio)
hostname = file.lan
partition
  manual
for all 4 disks:
  GPT
  p1: 6MB   BIOS BOOT
  p2: 250MB RAID1 BOOT
  p3: 768MB SWAP
  p4: 3.3GB RAID6 VG/PV
configure sw raid:
  md0: RAID1 /dev/sd[a-d]2: /boot (ext2)
  md1: RAID6 /dev/sd[a-d]4: LVM PV (VG=vg-sys)
configure LVM:
  LV system: /dev/md1 (4GB) / (reiserfs)
snapshot1
install system (normal)
install grub
finish
snapshot2
reboot
snapshot3


cheers
  pille
<>

Bug#644423: libterm-readline-gnu-perl: FTBFS: Could not find neither libtermcap.a, libncurses.a, or libcurses.

[Sven Joachim]

Package: libterm-readline-gnu-perl
Version: 1.20-1
Severity: serious
Tags: wheezy sid

>From my pbuilder log:

,
|  debian/rules build
| dh build
|dh_testdir
|dh_auto_configure
| Could not find neither libtermcap.a, libncurses.a, or libcurses.
| dh_auto_configure: perl Makefile.PL INSTALLDIRS=vendor create_packlist=0 
returned exit code 1
| make: *** [build] Error 2
`

The reason is that libreadline-dev has stopped depending on
libncurses5-dev in 6.2-6, and libterm-readline-gnu-perl does not
build-depend on libncurses5-dev itself.

Possible solutions:

1) Build-depend on libncurses5-dev;

2) Patch Makefile.PL to try -ltinfo in preference over -ltermcap,
   -lcurses or -lncurses;

3) Wait for libtinfo-dev to take over the libtermcap.{a,so} symlinks
   from libncurses5-dev.

While 1) is the easiest short-term solution, 2) and 3) have the
advantage that libterm-readline-gnu-perl will only depend on libtinfo5
and not unnecessarily link against libncurses5.


-- System Information:
Debian Release: wheezy/sid
  APT prefers unstable
  APT policy: (500, 'unstable'), (101, 'experimental')
Architecture: i386 (x86_64)

Kernel: Linux 3.1.0-rc9-nouveau (SMP w/2 CPU cores)
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

Versions of packages libterm-readline-gnu-perl depends on:
ii  libc6   2.13-21 
ii  libncurses5 5.9-2   
ii  libreadline66.2-6   
ii  perl5.12.4-5
ii  perl-base [perlapi-5.12.3]  5.12.4-5

libterm-readline-gnu-perl recommends no packages.

libterm-readline-gnu-perl suggests no packages.

-- no debconf information



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

Bug#643377: marked as done (flac: FTBFS: main.c:118:3: error: format not a string literal and no format arguments [-Werror=format-security])

[Debian Bug Tracking System]

Your message dated Wed, 05 Oct 2011 18:47:21 +
with message-id 
and subject line Bug#643377: fixed in flac 1.2.1-6
has caused the Debian Bug report #643377,
regarding flac: FTBFS: main.c:118:3: 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.)


-- 
643377: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=643377
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: flac
Version: 1.2.1-5
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../../..   -DFLaC__INLINE=__inline__ -DNDEBUG 
> -I../../.. -I./include -I../../../include   -O3 -funroll-loops 
> -finline-functions -Wall -W -Winline -g -O2 -fstack-protector 
> --param=ssp-buffer-size=4 -D_FORTIFY_SOURCE=2 -Wformat -Wformat-security 
> -Werror=format-security -c main.c
> main.c: In function 'main':
> main.c:118:3: error: format not a string literal and no format arguments 
> [-Werror=format-security]
> main.c:123:3: error: format not a string literal and no format arguments 
> [-Werror=format-security]
> main.c:132:4: error: format not a string literal and no format arguments 
> [-Werror=format-security]
> cc1: some warnings being treated as errors
> 
> make[5]: *** [main.o] Error 1

The full build log is available from:
   http://people.debian.org/~lucas/logs/2011/09/23/flac_1.2.1-5_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: flac
Source-Version: 1.2.1-6

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

flac_1.2.1-6.diff.gz
  to main/f/flac/flac_1.2.1-6.diff.gz
flac_1.2.1-6.dsc
  to main/f/flac/flac_1.2.1-6.dsc
flac_1.2.1-6_amd64.deb
  to main/f/flac/flac_1.2.1-6_amd64.deb
libflac++-dev_1.2.1-6_amd64.deb
  to main/f/flac/libflac++-dev_1.2.1-6_amd64.deb
libflac++6_1.2.1-6_amd64.deb
  to main/f/flac/libflac++6_1.2.1-6_amd64.deb
libflac-dev_1.2.1-6_amd64.deb
  to main/f/flac/libflac-dev_1.2.1-6_amd64.deb
libflac-doc_1.2.1-6_all.deb
  to main/f/flac/libflac-doc_1.2.1-6_all.deb
libflac8_1.2.1-6_amd64.deb
  to main/f/flac/libflac8_1.2.1-6_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 643...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Fabian Greffrath  (supplier of updated flac 
package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Format: 1.8
Date: Wed, 05 Oct 2011 14:26:47 +0200
Source: flac
Binary: flac libflac8 libflac-doc libflac-dev libflac++6 libflac++-dev
Architecture: source amd64 all
Version: 1.2.1-6
Distribution: unstable
Urgency: medium
Maintainer: Debian Multimedia Maintainers 

Changed-By: Fabian Greffrath 
Description: 
 flac   - Free Lossless Audio Codec - command line tools
 libflac++-dev - Free Lossless Audio Codec - C++ development library
 libflac++6 - Free Lossless Audio Codec - C++ runtime library
 libflac-dev - Free Lossless Audio Codec - C development library
 libflac-doc - Free Lossless Audio Codec - library documentation
 libflac8   - Free Lossless Audio Codec - runtime C library
Closes: 643377
Changes: 
 flac (1.2.1-6) unstable; urgency=medium
 .
   * Fix "format not a string literal and no format arguments
 [-Werror=format-security]" errors (Closes: #643377).
Checksums-Sha1: 
 66df762b1554197ee6219d901f322883a4e7e6ed 1613 flac_1.2.1-6.dsc
 88a7932da05243fe486aa82092a97e9d0cd75950 15955 flac_1.2.1-6.diff.gz
 2c6b856f58ab8baf81e278bab3493453e7386ddc 177294 flac_1

Bug#635548: CVE-2011-2716

[Michael Tokarev]

I'm Cc'ing the relevant bug# so others may see this information.
Hopefully you wont object -- the bug is public for a long time.

On 05.10.2011 16:04, Nico Golde wrote:
> Hi,
> * Nico Golde  [2011-10-05 11:21]:
>> * Michael Tokarev  [2011-10-05 10:34]:
>>> On 05.10.2011 02:42, Nico Golde wrote:
 Hi,
 can you tell me if CVE-2011-2716 is a problem with a default 
 busybox or only in case there are additional shell scripts 
 that make use of the untrusted host name?
>>>
>>> Busybox itself does not really work in this case: an additional
>>> shell script is _required_ for DHCP functionality, since busybox
>>> executes a shell script to do the real work, and, in particular,
>>> to set up host name etc.  The default script supplied with the
>>> package is not affected.
> 
> (/debian/tree/busybox-udeb/usr/share/udhcpc/default.script) and was wondering 
> if the domain name is safe to use. I see it is the only unquoted variable in 
> this script. Can you comment on this? I have to admit that I don't know the 

Actually it was me who looked into the wrong script - I looked into the
version installed on my system, which is modified by me long ago.  That
version does not use any of the "bad" variables at all.

You're right, the actual script in the dhcpc package refers to $domain
variable - the only variable referenced in this script which may be
insecure.

But you're not correct that the variable is used unquoted.  Here's the
actual code:

# Update resolver configuration file
R=""
[ -n "$domain" ] && R="domain $domain
"
for i in $dns; do
echo "$0: Adding DNS $i"
R="${R}nameserver $i
"
done

if [ -x /sbin/resolvconf ]; then
echo -n "$R" | resolvconf -a "${interface}.udhcpc"
else
echo -n "$R" > "$RESOLV_CONF"
fi
;;

So, in all cases the variable is enclosed in double quotes.

There's just one possible problem with this: it is possible to
inject bad - eg, syntactically incorrect - content into /etc/resolv.conf.
I'm not really sure if glibc's resolver will cope with any and all
garbage found in /etc/resolv.conf, but its parser is very simple and
just ignores everything that it does not understand.

It is definitely not possible to execute (shell) code "embedded" in
${domain} variable - at least not from the udhcpc script quoted above.
Also, the only place where content of a single "insecure" variable is
used is /etc/resolv.conf (which is already controlled by an rogue dhcp
server anyway, to a large extent) - eg, the default script does not set
system hostname to the string supplied by dhcp server.


> inner workings of the dhcpc in combination with the surrounded scripts very 
> well so please bear with me :)

There's nothing to know about really: dhcpcd converts every known option
found in dhcp reply packet into an environment variable, without any
content checking/filtering whatsoever.  There are 2 most common types
of options: it is either a (list of) IP address(es), which are passed as
4-byte binaries and hence cannot contain bad strings at all (they're
converted into 1.2.3.4 - octet - form by udhcpc) - these are $broadcast,
$subnet, $router, $dns.  And the other common type is string - a sequence
of any characters.  One of these is $domain, there are others like
$hostname.

And all this stuff gets passed to the script, which may deal with them
in any way.

Note that in theory it is possible to have some other script - e.g. a
script executed by resolvconf from /etc/resolv.d/* directories - which
uses the same variables without clearing their contents.  But this is
a different story, and that'd be a definitive bug in these scripts,
with or without a rogue dhcp server.

So, the only problem is when the default script is replaced/modified
locally and in insecure way.

Note that current udhcpc script is in /usr/share, so it is not possible
to replace it locally in debian (well, without diverting it) - it's a
bug in dhcpcd, a file intended to be modified should be a conffile and
placed into /etc.  But this is, again, a different story ;)

Thanks,

/mjt



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

Bug#644417: CPU-faults early on boot

[Petr Salinger]

On my main workstation, kfreebsd 8.2-1.1 and later versions CPU-faults
early on boot.  This affects the i686 version only (not amd64 one).

8.2-1 is not affected.


Probably related to:

 * Build by GCC 4.6.  (Closes: #594288)

Would you mind to rebuild latest kfreebsd-8 with gcc-4.3 from stable ?
And by current "gcc-4.6 -fno-gcse" ?

Petr



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

Bug#607479: libfcgi-perl/CVE-2011-2766 authentication bypass

[Dominic Hargreaves]

On Sat, Oct 01, 2011 at 12:44:33PM +0200, Moritz Mühlenhoff wrote:
> On Sat, Oct 01, 2011 at 08:12:18AM +0300, Damyan Ivanov wrote:

> > Porting the patch (for some reason it doesn't apply cleanly) is 
> > trivial. Attached is a patch that does exactly that (to be git 
> > apply'ed to the debian/0.71-1 tag, which is the squeeze version).
> 
> Did update this receive testing?

I've just tested RT 3.8 + squeeze + mod_fcgid, and I can't spot any
breakage.
 
> distribution needs to point to stable-security, not unstable. And
> while you're at it, please modify 0.71-1+squeeze.1 to 0.71-1+squeeze1
> for consistency.

-- 
Dominic Hargreaves | http://www.larted.org.uk/~dom/
PGP key 5178E2A5 from the.earth.li (keyserver,web,email)



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

Bug#607479: libfcgi-perl/CVE-2011-2766 authentication bypass

[Dominic Hargreaves]

On Sat, Oct 01, 2011 at 08:12:18AM +0300, Damyan Ivanov wrote:
> -=| Dominic Hargreaves, 30.09.2011 18:26:41 +0100 |=-
> > I'm reopening the bug, because I believe this fix applies to 
> > squeeze, and should be fixed there.
> 
> Agreed.
> 
> > Has anyone yet contacted the security team about this/is anyone 
> > working on packages for squeeze?
> 
> I don't think so.
> 
> Porting the patch (for some reason it doesn't apply cleanly) is 
> trivial. Attached is a patch that does exactly that (to be git 
> apply'ed to the debian/0.71-1 tag, which is the squeeze version).

As now publicly announced, this affects Request Tracker on squeeze:

.

-- 
Dominic Hargreaves | http://www.larted.org.uk/~dom/
PGP key 5178E2A5 from the.earth.li (keyserver,web,email)



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

Bug#640021: copypasted descriptions of eg, comics without copyright

[Ritesh Raj Sarraf]

Kovid,

Please have a look at this bug report.
And would you fix this in your release first?

-- 
Ritesh Raj Sarraf | http://people.debian.org/~rrs
Debian - The Universal Operating System




signature.asc
Description: OpenPGP digital signature

Bug#644189: marked as done (libcrypt-dsa-perl: signing leaks secret key on systems)

[Debian Bug Tracking System]

Your message dated Wed, 05 Oct 2011 17:47:40 +
with message-id 
and subject line Bug#644189: fixed in libcrypt-dsa-perl 1.17-3
has caused the Debian Bug report #644189,
regarding libcrypt-dsa-perl: signing leaks secret key on systems
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.)


-- 
644189: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=644189
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: libcrypt-dsa-perl
Version: 1.17-1
Severity: wishlist

Hi,

IMHO the package has an unneccesary dependency on Data::Random.

Crypt::DSA's Makefile.PL states:
requires  'Data::Random' => '0.05' if win32;

Obviously my system isn't windows ;-)

I checked the code, and AFAICS Data::Random is only necessary if the system
does not have a /dev/random.
Is this the case for any of the kernels that Debian works on?
If yes, would it b possible to add the dependency on Data::Random only for
these kernels?

Thanks in advance for giving it a thought &
also thanks for maintaining Crypt::DSA in Debian
Peter


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

Kernel: Linux 3.0.0-1-amd64 (SMP w/4 CPU cores)
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

Versions of packages libcrypt-dsa-perl depends on:
ii  libconvert-asn1-perl  0.22-2  
ii  libconvert-pem-perl   0.08-1  
ii  libdata-buffer-perl   0.04-1.1
ii  libfile-which-perl1.08-1  
ii  perl  5.12.4-4
ii  perl-modules [libfile-spec-perl]  5.12.4-4

Versions of packages libcrypt-dsa-perl recommends:
ii  libdata-random-perl  0.05-4
ii  libmath-bigint-gmp-perl  1.37-1

libcrypt-dsa-perl suggests no packages.

-- no debconf information


--- End Message ---
--- Begin Message ---
Source: libcrypt-dsa-perl
Source-Version: 1.17-3

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

libcrypt-dsa-perl_1.17-3.debian.tar.gz
  to main/libc/libcrypt-dsa-perl/libcrypt-dsa-perl_1.17-3.debian.tar.gz
libcrypt-dsa-perl_1.17-3.dsc
  to main/libc/libcrypt-dsa-perl/libcrypt-dsa-perl_1.17-3.dsc
libcrypt-dsa-perl_1.17-3_all.deb
  to main/libc/libcrypt-dsa-perl/libcrypt-dsa-perl_1.17-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 644...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Harlan Lieberman-Berg  (supplier of updated 
libcrypt-dsa-perl package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Mon, 03 Oct 2011 14:39:15 -0400
Source: libcrypt-dsa-perl
Binary: libcrypt-dsa-perl
Architecture: source all
Version: 1.17-3
Distribution: unstable
Urgency: low
Maintainer: Debian Perl Group 
Changed-By: Harlan Lieberman-Berg 
Description: 
 libcrypt-dsa-perl - Perl module for DSA Signatures and Key Generation
Closes: 644189
Changes: 
 libcrypt-dsa-perl (1.17-3) unstable; urgency=low
 .
   * Team upload.
   * Add patch to remove fallback to Data::Random (Closes: #644189).
Checksums-Sha1: 
 3e2234ed9d78bb56030df46e070ec9f3c6359e62 2203 libcrypt-dsa-perl_1.17-3.dsc
 c6f233d280e5fe5a310e25edcd3f8ef436f79159 2441 
libcrypt-dsa-perl_1.17-3.debian.tar.gz
 7c0103589c31f0e643473fbdd7d3edef4973da3a 34648 libcrypt-dsa-perl_1.17-3_all.deb
Checksums-Sha256: 
 1b957388ee17ab260ba4ed770aa5a2bed074af6dcb8cba7aeca92cfb12d7242a 2203 
libcrypt-dsa-perl_1.17-3.dsc
 a2291829b1d0883964b1f456e2b2e4b2655f28b661e55976f389bf1be3b0a34e 2441 
libcrypt-dsa-perl_1.17-3.debian.tar.gz
 8a963f0912f314d5ba01956410cd4f48466a1ca1cfcbcd980c0e664ed1802585 34648 
libcrypt-dsa-perl_1.17-3_all.deb
Files: 
 aac3d0b7095f362aee414af73c622789 2203 perl optional 
libcrypt-dsa-perl_1.17-3.dsc
 037830c436dc94b5f012b1204e151b29 2441 perl optional 
libcrypt-dsa-perl_1.17-3.debian.tar.gz
 2b32bfe72a1d214e9c29e5cd3c2ab4fc 34648 perl optional 
libcrypt-dsa-perl_1.17-3_all.deb

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

iQIcBAEBCAAGBQJOjJczAAoJELs6aAGGSaoGL7QP/2MX/N/AECFGMGhn8BkcQPSQ
5l/lgRmObv9Ytn

Bug#644418: Proposed-RM: libcoat-perl -- RoM; unmaintained, alternatives exist

[Ansgar Burchardt]

Package: libcoat-perl
Version: 0.334-2
Severity: serious
Tags: wheezy sid

Hi,

libcoat-perl is no longer maintained upstream, it is suggested to use
Moose, Mouse, Moo and Mo instead.

If nobody objects, I'll reasign to the ftp.d.o after a while (and also
file a removal request for libcoat-persistent-perl).

Regards,
Ansgar



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

Bug#644417: CPU-faults early on boot (regression)

[Robert Millan]

Package: kfreebsd-image-8.2-1-686
Version: 8.2-1.1
Severity: grave

On my main workstation, kfreebsd 8.2-1.1 and later versions CPU-faults
early on boot.  This affects the i686 version only (not amd64 one).

8.2-1 is not affected.

-- System Information:
Debian Release: 6.0.2
  APT prefers stable-updates
  APT policy: (500, 'stable-updates'), (500, 'stable')
Architecture: kfreebsd-i386 (i686)



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

Bug#643866: electric-fence: FTBFS on GNU/kFreeBSD

[peter green]

Matthew Vernon wrote:

Hi,


I have just tested and the version in testing also FTBFS on kfreebsd

OOI, what's the failure mode?

Program terminated with a Segfault during the self test.



Thanks,

Matthew






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

Bug#644389: suspect non-working mdadm.conf created during install

[martin f krafft]

also sprach pille  [2011.10.05.1819 
+0200]:
> >Please provide the exact original and new UUIDs, don't expect me to
> >search the Net for them (I am offline right now).
> 
> unfortunately i cannot provide you with those. if i could i would
> have done so, already.
> the install was a week ago and i don't have any backups of a broken
> config. don't expect me to memorize UUIDs.
> 
> >Also, did you change the hostname?
> 
> no.

In this case there is very little I can do. I have done multiple
squeeze installs with RAID, and upgrades, and I have not seen this
problem. Unless you can reproduce this bug, I cannot do anything but
keep this report open.

-- 
 .''`.   martin f. krafft   Related projects:
: :'  :  proud Debian developer   http://debiansystem.info
`. `'`   http://people.debian.org/~madduckhttp://vcs-pkg.org
  `-  Debian - when you have better things to do than fixing systems
 
"the mind of the thoroughly well-informed man is a dreadful thing.
 it is like a bric-à-brac shop, all monsters and dust,
 with everything priced above its proper value."
-- oscar wilde


digital_signature_gpg.asc
Description: Digital signature (see http://martin-krafft.net/gpg/sig-policy/999bbcc4/current)

Bug#643353: patch

[Bart Martens]

tags 643353 patch
stop


--- ./asmix.c.orig	2011-10-05 18:32:32.0 +0200
+++ ./asmix.c	2011-10-05 18:33:22.0 +0200
@@ -577,14 +577,14 @@
   ret = XpmCreatePixmapFromData(dpy, Root, bg_xpm, &asMix.pixmap, 
 &asMix.mask, &asMix.attributes);
   if(ret != XpmSuccess)
-{fprintf(stderr, ERR_colorcells);exit(1);}
+{fprintf(stderr, "%s", ERR_colorcells);exit(1);}
 
 
   Mark.attributes.valuemask |= (XpmReturnPixels | XpmReturnExtensions);
   ret = XpmCreatePixmapFromData(dpy, Root, mark_xpm, &Mark.pixmap, 
 &Mark.mask, &Mark.attributes);
   if(ret != XpmSuccess)
-{fprintf(stderr, ERR_colorcells);exit(1);}
+{fprintf(stderr, "%s", ERR_colorcells);exit(1);}
 
 }
 //

Processed: patch

[Debian Bug Tracking System]

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

> tags 643353 patch
Bug #643353 [src:asmix] asmix: FTBFS: asmix.c:580:5: error: format not a string 
literal and no format arguments [-Werror=format-security]
Added tag(s) patch.
> stop
Stopping processing here.

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

[Julien Valroff]

Hi Laurence,

Le mercredi 05 oct. 2011 à 14:49:24 (+0200 CEST), Laurence Withers a écrit :
> Package: dspam
> Version: 3.10.1+dfs
> Severity: critical
> Justification: causes serious data loss
> 
> 
> I have discovered that dspam is truncating inbound email after it has been
> scanned. Please consider the size field (S=) in the following exim log
> entries:
> 
> 2011-10-05 01:58:48 1RBGky-0007w4-3k <= linux-omap-ow...@vger.kernel.org 
> H=mail2.jellyfishnet.co.uk [93.91.20.10] P=esmtps X=TLS1.0:RSA_ARCFOUR_MD5:16 
> S=6021 id=2a3dcf3da181ad40bde86a3150b27b6b03b4fb3...@dbde02.ent.ti.com
> 2011-10-05 01:58:48 1RBGky-0007wE-9z <= linux-omap-ow...@vger.kernel.org 
> U=dspam P=spam-scanned S=3591 
> id=2a3dcf3da181ad40bde86a3150b27b6b03b4fb3...@dbde02.ent.ti.com
> 2011-10-05 01:58:48 1RBGky-0007w4-3k => guralp  
> R=spamscan T=spamcheck
> 2011-10-05 01:58:48 1RBGky-0007w4-3k Completed
> 
> As you can see, there is a significant drop in size between the mail being
> received from a remote SMTP server (6021 bytes) and after it has been scanned
> by DSPAM (3591 bytes).

You use the backport, am I right?

Would you please describe your setup? Do you use DSPAM in daemon mode?

Do you have 'Broken lineStripping' enabled in your dspam.conf?

Cheers,
Julien

-- 
  .''`.   Julien Valroff ~  ~ 
 : :'  :  Debian Developer & Free software contributor
 `. `'`   http://www.kirya.net/
   `- 4096R/ E1D8 5796 8214 4687 E416  948C 859F EF67 258E 26B1



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

Bug#644389: suspect non-working mdadm.conf created during install

[pille]

i assembled my RAID devices by hand


How?


something like:
  mdadm --assemble /dev/md1 /dev/sd[abcd]4



but all names were prefixed with hostname 'hetzner'.


What names? You mean the name= attribute in the mdadm --examine
output?


excactly.


Please provide the exact original and new UUIDs, don't expect me to
search the Net for them (I am offline right now).


unfortunately i cannot provide you with those. if i could i would have 
done so, already.
the install was a week ago and i don't have any backups of a broken 
config. don't expect me to memorize UUIDs.



Also, did you change the hostname?


no.



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

Bug#643350: alsamixergui: FTBFS [-Werror=format-security]

[Bart Martens]

tags 643350 patch
stop


diff -ruN -x '*.png' -x '*.jpg' -x '*.ogg' -x '*_image_archive' ../orig/alsamixergui-0.9.0rc2-1/src/Fl_AM.cxx ./src/Fl_AM.cxx
--- ../orig/alsamixergui-0.9.0rc2-1/src/Fl_AM.cxx	2011-10-05 18:18:04.0 +0200
+++ ./src/Fl_AM.cxx	2011-10-05 18:21:16.0 +0200
@@ -151,7 +151,7 @@
 void gui_abort(const char* errorstr)
 {
 	if (strcmp(errorstr,""))
-		fl_alert(errorstr);
+		fl_alert("%s", errorstr);
 }
 
 void gui_mixer_change_view(void)

Processed: alsamixergui: FTBFS [-Werror=format-security]

[Debian Bug Tracking System]

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

> tags 643350 patch
Bug #643350 [src:alsamixergui] alsamixergui: FTBFS: Fl_AM.cxx:154:20: error: 
format not a string literal and no format arguments [-Werror=format-security]
Added tag(s) patch.
> stop
Stopping processing here.

Please contact me if you need assistance.
-- 
643350: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=643350
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#625080: marked as done (fstrcmp: FTBFS: ./lib/diffseq.h:461:38: error: 'bxbest' may be used uninitialized in this function [-Werror=uninitialized])

[Debian Bug Tracking System]

Your message dated Wed, 05 Oct 2011 16:17:12 +
with message-id 
and subject line Bug#625080: fixed in fstrcmp 0.3.D001-1.1
has caused the Debian Bug report #625080,
regarding fstrcmp: FTBFS: ./lib/diffseq.h:461:38: error: 'bxbest' may be used 
uninitialized in this function [-Werror=uninitialized]
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.)


-- 
625080: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=625080
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: fstrcmp
Version: 0.3.D001-1
Severity: serious
Tags: wheezy sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20110502 qa-ftbfs
Justification: FTBFS on amd64

Hi,

During a rebuild of all packages in sid, your package failed to build on
amd64.

Relevant part:
> make[1]: Entering directory 
> `/build/user-fstrcmp_0.3.D001-1-amd64-HXzCBP/fstrcmp-0.3.D001'
> libtool --mode=compile gcc  -Wall -g -O2 -Wall -Wextra -Wshadow -Werror 
> -Wl,--as-needed -I. -c fstrcmp/main.c -o fstrcmp/main.lo
> libtool: compile:  gcc -Wall -g -O2 -Wall -Wextra -Wshadow -Werror 
> -Wl,--as-needed -I. -c fstrcmp/main.c  -fPIC -DPIC -o fstrcmp/.libs/main.o
> libtool: compile:  gcc -Wall -g -O2 -Wall -Wextra -Wshadow -Werror 
> -Wl,--as-needed -I. -c fstrcmp/main.c -o fstrcmp/main.o >/dev/null 2>&1
> libtool --mode=compile gcc  -Wall -g -O2 -Wall -Wextra -Wshadow -Werror 
> -Wl,--as-needed -I. -c lib/ac/string.c -o lib/ac/string.lo
> libtool: compile:  gcc -Wall -g -O2 -Wall -Wextra -Wshadow -Werror 
> -Wl,--as-needed -I. -c lib/ac/string.c  -fPIC -DPIC -o lib/ac/.libs/string.o
> libtool: compile:  gcc -Wall -g -O2 -Wall -Wextra -Wshadow -Werror 
> -Wl,--as-needed -I. -c lib/ac/string.c -o lib/ac/string.o >/dev/null 2>&1
> libtool --mode=compile gcc  -Wall -g -O2 -Wall -Wextra -Wshadow -Werror 
> -Wl,--as-needed -I. -c lib/downcase.c -o lib/downcase.lo
> libtool: compile:  gcc -Wall -g -O2 -Wall -Wextra -Wshadow -Werror 
> -Wl,--as-needed -I. -c lib/downcase.c  -fPIC -DPIC -o lib/.libs/downcase.o
> libtool: compile:  gcc -Wall -g -O2 -Wall -Wextra -Wshadow -Werror 
> -Wl,--as-needed -I. -c lib/downcase.c -o lib/downcase.o >/dev/null 2>&1
> libtool --mode=compile gcc  -Wall -g -O2 -Wall -Wextra -Wshadow -Werror 
> -Wl,--as-needed -I. -c lib/fmemcmp.c -o lib/fmemcmp.lo
> libtool: compile:  gcc -Wall -g -O2 -Wall -Wextra -Wshadow -Werror 
> -Wl,--as-needed -I. -c lib/fmemcmp.c  -fPIC -DPIC -o lib/.libs/fmemcmp.o
> In file included from lib/fmemcmp.c:76:0:
> ./lib/diffseq.h: In function 'diag':
> ./lib/diffseq.h:212:13: warning: variable 'big_snake' set but not used 
> [-Wunused-but-set-variable]
> ./lib/diffseq.h: In function 'compareseq':
> ./lib/diffseq.h:461:38: error: 'bxbest' may be used uninitialized in this 
> function [-Werror=uninitialized]
> ./lib/diffseq.h:406:20: note: 'bxbest' was declared here
> ./lib/diffseq.h:454:38: error: 'fxbest' may be used uninitialized in this 
> function [-Werror=uninitialized]
> ./lib/diffseq.h:404:20: note: 'fxbest' was declared here
> cc1: all warnings being treated as errors
> 
> make[1]: *** [lib/fmemcmp.lo] Error 1

The full build log is available from:
   
http://people.debian.org/~lucas/logs/2011/05/02/fstrcmp_0.3.D001-1_lsid64.buildlog

A list of current common problems and possible solutions is available at 
http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute!

About the archive rebuild: The rebuild was done on about 50 AMD64 nodes
of the Grid'5000 platform, using a clean chroot.  Internet was not
accessible from the build systems.

-- 
| Lucas Nussbaum
| lu...@lucas-nussbaum.net   http://www.lucas-nussbaum.net/ |
| jabber: lu...@nussbaum.fr GPG: 1024D/023B3F4F |


--- End Message ---
--- Begin Message ---
Source: fstrcmp
Source-Version: 0.3.D001-1.1

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

fstrcmp_0.3.D001-1.1.diff.gz
  to main/f/fstrcmp/fstrcmp_0.3.D001-1.1.diff.gz
fstrcmp_0.3.D001-1.1.dsc
  to main/f/fstrcmp/fstrcmp_0.3.D001-1.1.dsc
fstrcmp_0.3.D001-1.1_i386.deb
  to main/f/fstrcmp/fstrcmp_0.3.D001-1.1_i386.deb
libfstrcmp-dev_0.3.D001-1.1_i386.deb
  to main/f/fstrcmp/libfstrcmp-dev_0.3.D001-1.1_i386.deb
libfstrcmp0-dbg_0.3.D001-1.1_i386.deb
  to main/f/fstrcmp/libfstrcmp0-dbg_0.3.D001-1.1_i386.deb
libfstrcmp0_0.3.D001-1.1_i386.deb
  to main/f/fstrcmp/libfstrcmp0_0.3.D001-1.1_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 t

Bug#625331: marked as done (fstrcmp: ftbfs with gcc-4.6 -Werror)

[Debian Bug Tracking System]

Your message dated Wed, 05 Oct 2011 16:17:12 +
with message-id 
and subject line Bug#625080: fixed in fstrcmp 0.3.D001-1.1
has caused the Debian Bug report #625080,
regarding fstrcmp: 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.)


-- 
625080: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=625080
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: fstrcmp
Version: 0.3.D001-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/fstrcmp_0.3.D001-1_lsid64.buildlog
The last lines of the build log are at the end of this report.



--- End Message ---
--- Begin Message ---
Source: fstrcmp
Source-Version: 0.3.D001-1.1

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

fstrcmp_0.3.D001-1.1.diff.gz
  to main/f/fstrcmp/fstrcmp_0.3.D001-1.1.diff.gz
fstrcmp_0.3.D001-1.1.dsc
  to main/f/fstrcmp/fstrcmp_0.3.D001-1.1.dsc
fstrcmp_0.3.D001-1.1_i386.deb
  to main/f/fstrcmp/fstrcmp_0.3.D001-1.1_i386.deb
libfstrcmp-dev_0.3.D001-1.1_i386.deb
  to main/f/fstrcmp/libfstrcmp-dev_0.3.D001-1.1_i386.deb
libfstrcmp0-dbg_0.3.D001-1.1_i386.deb
  to main/f/fstrcmp/libfstrcmp0-dbg_0.3.D001-1.1_i386.deb
libfstrcmp0_0.3.D001-1.1_i386.deb
  to main/f/fstrcmp/libfstrcmp0_0.3.D001-1.1_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 fstrcmp 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: Mon, 03 Oct 2011 17:43:52 +0200
Source: fstrcmp
Binary: fstrcmp libfstrcmp0 libfstrcmp0-dbg libfstrcmp-dev
Architecture: source i386
Version: 0.3.D001-1.1
Distribution: unstable
Urgency: low
Maintainer: Peter Miller 
Changed-By: gregor herrmann 
Description: 
 fstrcmp- fuzzy comparison of strings
 libfstrcmp-dev - library of fuzzy string comparison functions - development 
files
 libfstrcmp0 - library of fuzzy string comparison functions
 libfstrcmp0-dbg - library of fuzzy string comparison functions - debugging 
symbols
Closes: 625080
Changes: 
 fstrcmp (0.3.D001-1.1) unstable; urgency=low
 .
   * Non-maintainer upload.
   * Fix "FTBFS: ./lib/diffseq.h:461:38: error: 'bxbest' may be used
 uninitialized in this function [-Werror=uninitialized]":
 apply patch from Ubuntu / Colin Watson:
 - Guard all references to big_snake in lib/diffseq.h with #ifdef
   USE_HEURISTIC.
 - Build with -Dlint (closes: #625080, LP: #749279).
Checksums-Sha1: 
 f2f8f05e2c1c544dfee466c6302f1e0dd8fe23d2 1890 fstrcmp_0.3.D001-1.1.dsc
 4103e319713fcc08e323963d482942d3d1bbcfe5 3484 fstrcmp_0.3.D001-1.1.diff.gz
 17c646e76dd8d6826f663bd8b6d6ddd48afece0c 9586 fstrcmp_0.3.D001-1.1_i386.deb
 7c4a91b637705df86876d002324645e5b9181d2a 9692 libfstrcmp0_0.3.D001-1.1_i386.deb
 862a2cf263f476a402e25aa8b7a2e9da438629a1 21102 
libfstrcmp0-dbg_0.3.D001-1.1_i386.deb
 b2f62f2c98238685dae2431acb62febd4ba98ef6 24806 
libfstrcmp-dev_0.3.D001-1.1_i386.deb
Checksums-Sha256: 
 3426bb85973a3e167e211bfa81e0146b1492075484affcdcf0fb30c51b2a42e9 1890 
fstrcmp_0.3.D001-1.1.dsc
 6fb0cf8126417322f0568eae9ca099b49dbff63202317c11ea2abd86090172da 3484 
fstrcmp_0.3.D001-1.1.diff.gz
 438aa3b43970681ced8375b2b00b3a8af978e392c1c79c3955c18a50d6cd29bf 9586 
fstrcmp_0.3.D001-1.1_i386.deb
 0b20172ca53a2273ad57ceaef881556e1508828fefbc598eaacd7e2967e48f84 9692 
libfstrcmp0_0.3.D001-1.1_i386.deb
 cae8de51052e64a74620cc3bf70d980fc24cb5dfe810ea00e3373e7c5404348b 21102 
libfstrcmp0-dbg_0.3.D001-1.1_i386.deb
 b2e7bef3f10349cf6df643f32068f3669415676e0748fa4f9d82551b9529d0b8 24806 
libfstrcmp-dev_0.3.D001-1.1_i386.deb
Files: 
 c7f4389137182e64c2f7a08b776ff8

Bug#644336: marked as done (leveldb: ./port/atomic_pointer.h:161:3: error: expected primary-expression before 'volatile')

[Debian Bug Tracking System]

Your message dated Wed, 05 Oct 2011 16:02:11 +
with message-id 
and subject line Bug#644336: fixed in leveldb 0+20110926.git26db4d9-2
has caused the Debian Bug report #644336,
regarding leveldb: ./port/atomic_pointer.h:161:3: error: expected 
primary-expression before 'volatile'
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.)


-- 
644336: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=644336
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: leveldb
Version: 0+20110926.git26db4d9-1
Severity: serious
Justification: fails to build from source
Tags: patch

Hi,

leveldb ftbfs on s390.
  
https://buildd.debian.org/status/fetch.php?pkg=leveldb&arch=s390&ver=0%2B20110926.git26db4d9-1&stamp=1317749307
-
In file included from ./port/port_posix.h:28:0,
 from ./port/port.h:14,
 from ./db/filename.h:14,
 from db/builder.cc:7:
./port/atomic_pointer.h: In function 'void leveldb::port::ReadMemoryBarrier()':
./port/atomic_pointer.h:161:3: error: expected primary-expression
before 'volatile'
./port/atomic_pointer.h:161:3: error: expected ';' before 'volatile'
./port/atomic_pointer.h: In function 'void leveldb::port::WriteMemoryBarrier()':
./port/atomic_pointer.h:164:3: error: expected primary-expression
before 'volatile'
./port/atomic_pointer.h:164:3: error: expected ';' before 'volatile'
make[1]: *** [db/builder.o] Error 1
make[1]: *** Waiting for unfinished jobs
-

Because there is not asm keyword in front of volatile.
(Sorry, this patch was provided by me.)

I created new patch. Please check and apply.

Best regards,
 Nobuhiro

-- 
Nobuhiro Iwamatsu
   iwamatsu at {nigauri.org / debian.org}
   GPG ID: 40AD1FA6
From bc03fac68e487d0aa367b93794177178a1f9f1ab Mon Sep 17 00:00:00 2001
From: Nobuhiro Iwamatsu 
Date: Wed, 28 Sep 2011 12:29:28 +0900
Subject: [PATCH 5/9] Add support S390

Signed-off-by: Nobuhiro Iwamatsu 
---
 port/atomic_pointer.h |   14 ++
 1 files changed, 14 insertions(+), 0 deletions(-)

diff --git a/port/atomic_pointer.h b/port/atomic_pointer.h
index 6d0b15f..03a1815 100644
--- a/port/atomic_pointer.h
+++ b/port/atomic_pointer.h
@@ -42,6 +42,8 @@
 #define ARCH_CPU_IA64_FAMILY 1
 #elif defined(__alpha__)
 #define ARCH_CPU_ALPHA_FAMILY 1
+#elif defined(__s390x__) || defined(__s390__)
+#define ARCH_CPU_S390_FAMILY 1
 #endif
 
 namespace leveldb {
@@ -144,6 +146,17 @@ inline void WriteMemoryBarrier() {
 }
 #define LEVELDB_HAVE_MEMORY_BARRIER
 
+// S390
+#elif defined(ARCH_CPU_S390_FAMILY)
+
+inline void ReadMemoryBarrier() {
+  asm volatile("bcr 15,0" : : : "memory");
+}
+inline void WriteMemoryBarrier() {
+  asm volatile("bcr 15,0" : : : "memory");
+}
+#define LEVELDB_HAVE_MEMORY_BARRIER
+
 #endif
 
 // AtomicPointer built using platform-specific MemoryBarrier()
@@ -201,6 +214,7 @@ class AtomicPointer {
 #undef ARCH_CPU_PPC_FAMILY
 #undef ARCH_CPU_IA64_FAMILY
 #undef ARCH_CPU_ALPHA_FAMILY
+#undef ARCH_CPU_S390_FAMILY
 
 } // namespace leveldb::port
 } // namespace leveldb
-- 
1.7.6.3

--- End Message ---
--- Begin Message ---
Source: leveldb
Source-Version: 0+20110926.git26db4d9-2

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

leveldb-doc_0+20110926.git26db4d9-2_all.deb
  to main/l/leveldb/leveldb-doc_0+20110926.git26db4d9-2_all.deb
leveldb_0+20110926.git26db4d9-2.debian.tar.gz
  to main/l/leveldb/leveldb_0+20110926.git26db4d9-2.debian.tar.gz
leveldb_0+20110926.git26db4d9-2.dsc
  to main/l/leveldb/leveldb_0+20110926.git26db4d9-2.dsc
libleveldb-dev_0+20110926.git26db4d9-2_amd64.deb
  to main/l/leveldb/libleveldb-dev_0+20110926.git26db4d9-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 644...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Alessio Treglia  (supplier of updated leveldb package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Format: 1.8
Date: Wed, 05 Oct 2011 17:45:43 +0200
Source: leveldb
Binary: libleveldb-dev leveldb-doc
Architecture: source amd64 all
Version: 0+20110926.git26db4d9-2
Distribution: unstable
Urgency: low
Maintainer: Alessio Treglia 
Changed-By: Alessio Treglia 
Description: 
 le

Processed: tagging 644336

[Debian Bug Tracking System]

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

> tags 644336 + pending
Bug #644336 [src:leveldb] leveldb: ./port/atomic_pointer.h:161:3: error: 
expected primary-expression before 'volatile'
Added tag(s) pending.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
644336: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=644336
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#644346: marked as done (identicurse: conflict on upgrade)

[Debian Bug Tracking System]

Your message dated Wed, 05 Oct 2011 15:47:52 +
with message-id 
and subject line Bug#644346: fixed in identicurse 0.8.2+dfsg0-1
has caused the Debian Bug report #644346,
regarding identicurse: conflict on upgrade
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.)


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

Dear Maintainer,
*** Please consider answering these questions, where appropiate ***

   * What led up to the situation?
   * What exactly did you do (or not do) that was effective (or
 ineffective)?
   * What was the outcome of this action?
   * What outcome did you expect instead?

On upgrade, I observed:

Preparing to replace identicurse 0.7.3-1 (using 
.../identicurse_0.8.2-1_all.deb) ...
Unpacking replacement identicurse ...
dpkg: error processing /var/cache/apt/archives/identicurse_0.8.2-1_all.deb 
(--unpack):
 trying to overwrite '/usr/share/pyshared/oauth/__init__.py', which is also in 
package python-oauth 1.0.1-3
configured to not write apport reports
  Processing triggers for menu ...
Errors were encountered while processing:
 /var/cache/apt/archives/identicurse_0.8.2-1_all.deb
E: Sub-process /usr/bin/dpkg returned an error code (1)
A package failed to install.  Trying to recover:
Press return to continue.



*** End of the template - remove these lines ***


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

Kernel: Linux 3.1.0-rc8 (SMP w/4 CPU cores)
Locale: LANG=en_AU.UTF-8, LC_CTYPE=en_AU.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash

Versions of packages identicurse depends on:
ii  python 2.7.2-7
ii  python2.6  2.6.7-4
ii  python2.7  2.7.2-5

identicurse recommends no packages.

identicurse suggests no packages.

-- debconf-show failed


--- End Message ---
--- Begin Message ---
Source: identicurse
Source-Version: 0.8.2+dfsg0-1

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

identicurse_0.8.2+dfsg0-1.debian.tar.gz
  to main/i/identicurse/identicurse_0.8.2+dfsg0-1.debian.tar.gz
identicurse_0.8.2+dfsg0-1.dsc
  to main/i/identicurse/identicurse_0.8.2+dfsg0-1.dsc
identicurse_0.8.2+dfsg0-1_all.deb
  to main/i/identicurse/identicurse_0.8.2+dfsg0-1_all.deb
identicurse_0.8.2+dfsg0.orig.tar.bz2
  to main/i/identicurse/identicurse_0.8.2+dfsg0.orig.tar.bz2



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.
Alessio Treglia  (supplier of updated identicurse package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Format: 1.8
Date: Wed, 05 Oct 2011 17:38:39 +0200
Source: identicurse
Binary: identicurse
Architecture: source all
Version: 0.8.2+dfsg0-1
Distribution: unstable
Urgency: low
Maintainer: Alessio Treglia 
Changed-By: Alessio Treglia 
Description: 
 identicurse - simple Identi.ca client with a curses-based UI
Closes: 644346
Changes: 
 identicurse (0.8.2+dfsg0-1) unstable; urgency=low
 .
   * Repack the new release to get rid of oauth's code already provided by
 python-oauth (Closes: #644346).
   * Depends on python-oauth.
Checksums-Sha1: 
 7406d39adbf4d8b9eefac31e9cc38b16829119e0 1300 identicurse_0.8.2+dfsg0-1.dsc
 7f05ccbe51091c5df01b1391f025d6a327ec140d 56169 
identicurse_0.8.2+dfsg0.orig.tar.bz2
 fe018fdd1b3a664019b7e9a04b4ea7e7476bcb11 4343 
identicurse_0.8.2+dfsg0-1.debian.tar.gz
 840853da9f75c7a86a8ce4134605e4bd995abfcb 58544 
identicurse_0.8.2+dfsg0-1_all.deb
Checksums-Sha256: 
 1e21c927f9eca34e371cfe6c13344003ba5453ade75fdf0c7ac184e1cfb3aad8 1300 
identicurse_0.8.2+dfsg0-1.dsc
 7628ba9206e90a7ff21b6ba171d941e566085f0a8bd55c91edfab9e13c398ebb 56169 
identicurse_0.8.2+dfsg0.orig.tar.bz2
 e227a55470fe39f9b1ecb6a5c2a02d585b3e91774f0324d8b51be2e180f1 4343 
identicurse_0.8.2+dfsg0-1.debian.tar.gz
 ae6589caace92a7ea8ec0936fc29f399c63710943c790c3af5f058b1a8af721d 58544 
identicurse_0.8.2

Processed: limit source to hp-ppd, tagging 588317

[Debian Bug Tracking System]

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

> #hp-ppd (0.9-0.2) unstable; urgency=low
> #
> #  * Fix syntax error in various ppd files (add missing parens) Patch thanks 
> to
> #Sanjoy Mahajan  (Closes: #588317)
> #
> limit source hp-ppd
Limiting to bugs with field 'source' containing at least one of 'hp-ppd'
Limit currently set to 'source':'hp-ppd'

> tags 588317 + pending
Bug #588317 [hp-ppd] cups: FTBFS with hp-ppd 0.9-0.1 (1 test failed: "Missing 
Product in /usr/share/ppd/hp-ppd/HP/...")
Added tag(s) pending.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
588317: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=588317
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: cdrdao: diff for NMU version 1:1.2.3-0.2

[Debian Bug Tracking System]

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

> tags 625005 + pending
Bug #625005 [src:cdrdao] cdrdao: FTBFS: ScsiIf-linux.cc:287:37: error: no 
matching function for call to 'stat::stat(const char [22], stat*)'
Added tag(s) pending.
> thanks
Stopping processing here.

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

[Debian Bug Tracking System]

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

> found 588317 0.9-0.1
Bug #588317 [hp-ppd] cups: FTBFS with hp-ppd 0.9-0.1 (1 test failed: "Missing 
Product in /usr/share/ppd/hp-ppd/HP/...")
Bug Marked as found in versions hp-ppd/0.9-0.1.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
588317: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=588317
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#625005: cdrdao: diff for NMU version 1:1.2.3-0.2

[gregor herrmann]

tags 625005 + pending
thanks

Dear maintainer,

I've prepared an NMU for cdrdao (versioned as 1:1.2.3-0.2) 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: Paul Mc Cartney: Good Rockin' Tonight
diff -Nru cdrdao-1.2.3/debian/changelog cdrdao-1.2.3/debian/changelog
--- cdrdao-1.2.3/debian/changelog	2010-07-04 15:52:34.0 +0200
+++ cdrdao-1.2.3/debian/changelog	2011-10-05 17:00:26.0 +0200
@@ -1,3 +1,13 @@
+cdrdao (1:1.2.3-0.2) unstable; urgency=low
+
+  * Non-maintainer upload.
+  * Fix "FTBFS: ScsiIf-linux.cc:287:37: error: no matching function for
+call to 'stat::stat(const char [22], stat*)'": add patch 14-stat.h.patch
+(include sys/stat.h) by brian m. carlson.
+Closes: #625005
+
+ -- gregor herrmann   Wed, 05 Oct 2011 16:59:54 +0200
+
 cdrdao (1:1.2.3-0.1) unstable; urgency=low
 
   * Non-maintainer upload.
diff -Nru cdrdao-1.2.3/debian/patches/14-stat.h.patch cdrdao-1.2.3/debian/patches/14-stat.h.patch
--- cdrdao-1.2.3/debian/patches/14-stat.h.patch	1970-01-01 01:00:00.0 +0100
+++ cdrdao-1.2.3/debian/patches/14-stat.h.patch	2011-10-05 17:23:04.0 +0200
@@ -0,0 +1,19 @@
+Description: This patch fixes the FTBFS by including sys/stat.h.
+Origin: vendor
+Bug-Debian: http://bugs.debian.org/625005
+Forwarded: no
+Author: "brian m. carlson" 
+Reviewed-by: gregor herrmann 
+Last-Update: 2011-10-05
+
+diff -ur cdrdao.old/dao/ScsiIf-linux.cc cdrdao-1.2.3/dao/ScsiIf-linux.cc
+--- cdrdao.old/dao/ScsiIf-linux.cc	2011-05-18 22:00:28.0 +
 cdrdao-1.2.3/dao/ScsiIf-linux.cc	2011-05-18 22:05:38.0 +
+@@ -27,6 +27,7 @@
+ #include 
+ #include 
+ #include 
++#include 
+ #include 
+ #include 
+ #include 
diff -Nru cdrdao-1.2.3/debian/patches/series cdrdao-1.2.3/debian/patches/series
--- cdrdao-1.2.3/debian/patches/series	2010-07-04 15:54:01.0 +0200
+++ cdrdao-1.2.3/debian/patches/series	2011-10-05 16:59:30.0 +0200
@@ -5,3 +5,4 @@
 #11-rules-mips.patch
 #12-rules-s390.patch
 #13-rename-functions.patch
+14-stat.h.patch


signature.asc
Description: Digital signature

Processed: Re: Bug#588317: patch to fix FTBFS

[Debian Bug Tracking System]

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

> severity 588317 serious
Bug #588317 [hp-ppd] cups: FTBFS with hp-ppd 0.9-0.1 (1 test failed: "Missing 
Product in /usr/share/ppd/hp-ppd/HP/...")
Severity set to 'serious' from 'normal'

> thanks
Stopping processing here.

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

[Debian Bug Tracking System]

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

> found 644189 1.17-2
Bug #644189 {Done: gregor herrmann } [libcrypt-dsa-perl] 
libcrypt-dsa-perl: signing leaks secret key on systems
Bug Marked as found in versions libcrypt-dsa-perl/1.17-2; no longer marked as 
fixed in versions libcrypt-dsa-perl/1.17-2 and reopened.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
644189: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=644189
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#644395: libreoffice-core: oosplash.bin possibly compiled against wrong version of libpng12

[Gian Uberto Lauri]

> "RE" == Rene Engelhard  writes:

RE> libpng.so.12 in /usr/local/lib.  

Godammit! A  manual case of  PEBCAK! Thank  you for pointing  out this
eye-level error.

Thank you.

--
ing. Gian Uberto Lauri
Ricercatore / Reasearcher
Laboratorio Ricerca e Sviluppo / Research & Development Lab.
Area Calcolo Distribuito / Distributed Computation Area

gianuberto.la...@eng.it

Engineering Ingegneria Informatica spa
Corso Stati Uniti 23/C, 35127 Padova (PD) 

Tel. +39-049.8283.571 | main(){printf(&unix["\021%six\012\0"], 
Fax  +39-049.8283.569 |(unix)["have"]+"fun"-0x60);}   
Skype: gian.uberto.lauri  |  David Korn, AT&T Bell Labs 

http://www.eng.it |  ioccc best One Liner, 1987 




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

Bug#644395: libreoffice-core: oosplash.bin possibly compiled against wrong version of libpng12

[Rene Engelhard]

On Wed, Oct 05, 2011 at 04:33:21PM +0200, Gian Uberto Lauri wrote:
> > "RE" == Rene Engelhard  writes:
> 
> RE> No. Read my mail. The fix is to remove your broken copy of
  ^^
> RE> libpng.so.12 in /usr/local/lib.
  ^^
> 
> O.K.

Not OK.

> Updating  the  library was  the  first  thing  I  tried to  do,  "it's
> outdated" I thought.
> 
> I then  run an apt-get update,  and apt-get ugrade and  the problem is
> still there. 
> 
> I then run  apt-get install --reinstall libpng12-0 and  the problem is
> still there.

I haven't said you should upgrade or reinstall libpng12-0. I said that
libpng12-0 was *CORRECT*. libpng12-0 doesn't install its lib into
/usr/local/lib but /usr/lib.

The /usr/local/lib is simply a copy you or some install script put there.
Remove it:

rm -f /usr/local/lib/libpng.so.12

(and maybe even for some more libs, I honestly don't care)

> The problemi is still there.

Because you didn't remove tbe broken library.

> Does it means that  the bug is in the packaging  of libpng12-0 for the
> amd64 architecture ?

No, it's a problem with you having a broken libpng.so.2 in /usr/local/lib,
as I say for the third - and last - time now. libpng12-0 is
- as said - correct.

Grüße/Regards,

René



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

Bug#644254: [PATCH 2/2] Use QT4_IM_MODULE instead of QT_IM_MODULE.

[Aron Xu]

Second patch, for QT4_IM_MODULE



-- 
Regards,
Aron Xu
From 2a2c403f1867dcbff266eac7ed7be2b513f32d5b Mon Sep 17 00:00:00 2001
From: Aron Xu 
Date: Wed, 5 Oct 2011 22:37:04 +0800
Subject: [PATCH 2/2] Use QT4_IM_MODULE instead of QT_IM_MODULE.

---
 data/20_ibus.im |3 ++-
 1 files changed, 2 insertions(+), 1 deletions(-)

diff --git a/data/20_ibus.im b/data/20_ibus.im
index 6183f41..24da5e9 100644
--- a/data/20_ibus.im
+++ b/data/20_ibus.im
@@ -16,10 +16,11 @@ for IM_CONFIG_MARKER in /usr/lib/gtk-2.0/*/immodules/im-ibus.so /usr/lib/*/gtk-2
 done
 
 QT_IM_MODULE=xim
+QT4_IM_MODULE=xim
 # use immodule when available for QT
 for IM_CONFIG_MARKER in /usr/lib/qt4/plugins/inputmethods/libqtim-ibus.so /usr/lib/*/qt4/plugins/inputmethods/libqtim-ibus.so ; do
 if [ -e $IM_CONFIG_MARKER ]; then
-QT_IM_MODULE=ibus
+QT4_IM_MODULE=ibus
 fi
 done
 
-- 
1.7.1

Bug#644395: libreoffice-core: oosplash.bin possibly compiled against wrong version of libpng12

[Gian Uberto Lauri]

> "RE" == Rene Engelhard  writes:

>> the last update of the system introduced a critical malfunctionn in
>> libreoffice:
RE>  

RE> You mean the one almost a month ago?

I savet the last files 2 days ago...

RE> [2011-09-13] libreoffice 1:3.4.3-1 MIGRATED to testing (Britney)

I  don't remember  this in  the  list of  previous bugs  shown by  the
reportbug tool.

And if it's not in testing, why it reached my machine through apt? 

And what should be a workaround ? Remove the package and go for what's
supplied by LibreOffice.org ? What's a package system for, then?

--
ing. Gian Uberto Lauri
Ricercatore / Reasearcher
Laboratorio Ricerca e Sviluppo / Research & Development Lab.
Area Calcolo Distribuito / Distributed Computation Area

gianuberto.la...@eng.it

Engineering Ingegneria Informatica spa
Corso Stati Uniti 23/C, 35127 Padova (PD) 

Tel. +39-049.8283.571 | main(){printf(&unix["\021%six\012\0"], 
Fax  +39-049.8283.569 |(unix)["have"]+"fun"-0x60);}   
Skype: gian.uberto.lauri  |  David Korn, AT&T Bell Labs 

http://www.eng.it |  ioccc best One Liner, 1987 





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

Bug#621866: Bug fixed in unstable/testung/experimental

[Arne Wichmann]

As far as I can see, this bug is fixed in testing (and anything newer):

/usr/share/doc/rsync/changelog.gz:

[...]
- Fixed a data-corruption issue when preserving hard-links without
  preserving file ownership, and doing deletions either before or during
  the transfer (CVE-2011-1097).  This fixes some assert errors in the
  hard-linking code, and some potential failed checksums (via -c) that
  should have matched.
[...]

cu

AW
-- 
[...] If you don't want to be restricted, don't agree to it. If you are
coerced, comply as much as you must to protect yourself, just don't support
it. Noone can free you but yourself. (crag, on Debian Planet)
Arne Wichmann (a...@linux.de)


signature.asc
Description: Digital signature

Bug#644254: [PATCH 1/2] Multi-Arch support for ibus IM Modules.

[Aron Xu]

First patch, for Multi-Arch support.


-- 
Regards,
Aron Xu
From 9c3c6f287cc3459e807e4f1587e287f2f95f9253 Mon Sep 17 00:00:00 2001
From: Aron Xu 
Date: Wed, 5 Oct 2011 22:36:06 +0800
Subject: [PATCH 1/2] Multi-Arch support for ibus IM Modules.

---
 data/20_ibus.im |4 ++--
 1 files changed, 2 insertions(+), 2 deletions(-)

diff --git a/data/20_ibus.im b/data/20_ibus.im
index b38952d..6183f41 100644
--- a/data/20_ibus.im
+++ b/data/20_ibus.im
@@ -9,7 +9,7 @@ XMODIFIERS=@im=ibus
 
 GTK_IM_MODULE=xim
 # use immodule when available for GTK
-for IM_CONFIG_MARKER in /usr/lib/gtk-2.0/*/immodules/im-ibus.so ; do
+for IM_CONFIG_MARKER in /usr/lib/gtk-2.0/*/immodules/im-ibus.so /usr/lib/*/gtk-2.0/*/immodules/im-ibus.so ; do
 if [ -e $IM_CONFIG_MARKER ]; then
 GTK_IM_MODULE=ibus
 fi
@@ -17,7 +17,7 @@ done
 
 QT_IM_MODULE=xim
 # use immodule when available for QT
-for IM_CONFIG_MARKER in /usr/lib/qt4/plugins/inputmethods/libqtim-ibus.so ; do
+for IM_CONFIG_MARKER in /usr/lib/qt4/plugins/inputmethods/libqtim-ibus.so /usr/lib/*/qt4/plugins/inputmethods/libqtim-ibus.so ; do
 if [ -e $IM_CONFIG_MARKER ]; then
 QT_IM_MODULE=ibus
 fi
-- 
1.7.1

Bug#644395: libreoffice-core: oosplash.bin possibly compiled against wrong version of libpng12

[Gian Uberto Lauri]

> "RE" == Rene Engelhard  writes:

RE> No. Read my mail. The fix is to remove your broken copy of
RE> libpng.so.12 in /usr/local/lib.

O.K.

Updating  the  library was  the  first  thing  I  tried to  do,  "it's
outdated" I thought.

I then  run an apt-get update,  and apt-get ugrade and  the problem is
still there. 

I then run  apt-get install --reinstall libpng12-0 and  the problem is
still there.

I  even tried  to redo  the same  after issuing  an apt-ger  clean and
apt-get autoclean  to empty the  package cache and force  the download
from mirror.switch.ch with another run of apt-get install --reinstall.

The problemi is still there.

Does it means that  the bug is in the packaging  of libpng12-0 for the
amd64 architecture ?

--
ing. Gian Uberto Lauri
Ricercatore / Reasearcher
Laboratorio Ricerca e Sviluppo / Research & Development Lab.
Area Calcolo Distribuito / Distributed Computation Area

gianuberto.la...@eng.it

Engineering Ingegneria Informatica spa
Corso Stati Uniti 23/C, 35127 Padova (PD) 

Tel. +39-049.8283.571 | main(){printf(&unix["\021%six\012\0"], 
Fax  +39-049.8283.569 |(unix)["have"]+"fun"-0x60);}   
Skype: gian.uberto.lauri  |  David Korn, AT&T Bell Labs 

http://www.eng.it |  ioccc best One Liner, 1987 




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

Bug#644395: libreoffice-core: oosplash.bin possibly compiled against wrong version of libpng12

[Rene Engelhard]

Hi,

why are you ignoring the important point of the mail?

On Wed, Oct 05, 2011 at 04:14:39PM +0200, Gian Uberto Lauri wrote:
> And if it's not in testing, why it reached my machine through apt? 

It is in testing. Since around 1 month. I was aiming at you reporting it now,
1 month after it entered testing and then saying "last update"...

> And what should be a workaround ? Remove the package and go for what's
> supplied by LibreOffice.org ?

No. Read my mail. The fix is to remove your broken copy of libpng.so.12
in /usr/local/lib. The libreoffice-core package is correct and has
a correct dependency of the packaged libpng12-0.

Who said to remove libreoffice? None.

> What's a package system for, then?

Amonsgst others for exactly preventing stuff like happened here with having
incompatible random versions of libraries lying around somewhere randomly
where the linker finds it.

Grüße/Regards,

René



--
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#644389: suspect non-working mdadm.conf created during install

[Debian Bug Tracking System]

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

> tags 644389 moreinfo unreproducible
Bug #644389 [mdadm] suspect non-working mdadm.conf created during install
Added tag(s) unreproducible and moreinfo.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
644389: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=644389
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#644389: suspect non-working mdadm.conf created during install

[martin f krafft]

tags 644389 moreinfo unreproducible
thanks

also sprach pille  [2011.10.05.1458 
+0200]:
> i assembled my RAID devices by hand

How?

> but all names were prefixed with hostname 'hetzner'.

What names? You mean the name= attribute in the mdadm --examine
output?

> disks used were new & empty and had no affiliation to hetzner
> online AG you can search the net for '"name=hetzner:" mdadm.conf'
> to yield probably the original UUIDs.

Please provide the exact original and new UUIDs, don't expect me to
search the Net for them (I am offline right now).

Also, did you change the hostname?

-- 
 .''`.   martin f. krafft   Related projects:
: :'  :  proud Debian developer   http://debiansystem.info
`. `'`   http://people.debian.org/~madduckhttp://vcs-pkg.org
  `-  Debian - when you have better things to do than fixing systems


digital_signature_gpg.asc
Description: Digital signature (see http://martin-krafft.net/gpg/sig-policy/999bbcc4/current)

Processed: notfound 644395 in 1:3.4.3-1

[Debian Bug Tracking System]

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

> notfound 644395 1:3.4.3-1
Bug #644395 {Done: Rene Engelhard } [libreoffice-core] 
libreoffice-core: oosplash.bin possibly compiled against wrong version of 
libpng12
Bug No longer marked as found in versions libreoffice/1:3.4.3-1.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
644395: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=644395
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#644395: libreoffice-core: oosplash.bin possibly compiled against wrong version of libpng12

[Debian Bug Tracking System]

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

> severity 644395 grave
Bug #644395 [libreoffice-core] libreoffice-core: oosplash.bin possibly compiled 
against wrong version of libpng12
Severity set to 'grave' from 'critical'

> close 644395
Bug#644395: libreoffice-core: oosplash.bin possibly compiled against wrong 
version of libpng12
'close' is deprecated; see http://www.debian.org/Bugs/Developer#closing.
Bug closed, send any further explanations to Gian Uberto Lauri 

> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
644395: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=644395
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#644395: libreoffice-core: oosplash.bin possibly compiled against wrong version of libpng12

[Rene Engelhard]

severity 644395 grave
close 644395
thanks

On Wed, Oct 05, 2011 at 03:00:09PM +0200, Gian Uberto Lauri wrote:
> Severity: critical

How the f* does this break unlrelated applicatoions or the whole system?
Right, it doesn't. if this was a bug (see below) this would only be grave.

> the last update of the system introduced a critical malfunctionn in 
> libreoffice:
 

You mean the one almost a month ago?

[2011-09-13] libreoffice 1:3.4.3-1 MIGRATED to testing (Britney)

(And yes, this added libpng linkage to ooplash.bin)

> saint@quigley:~
> 14:33:11 [24] $soffice
> /usr/lib/libreoffice/program/oosplash.bin: /usr/local/lib/libpng12.so.0: no 
> version information available (required by 
> /usr/lib/libreoffice/program/oosplash.bin)
 ^
> /usr/lib/libreoffice/program/oosplash.bin: symbol lookup error: 
> /usr/local/lib/libpng12.so.0: undefined symbol: inflateInit_
  


(Remark: don't use soffice, better to use libreoffice. Doesn't have to do
with this problem, though)

Notice the /usr/local.

That's your problem. You have a hand-compiled(?) libpng which doesn't match what
libreoffice is built against (which is Debians official libpng12 with versioned
symbols).

In you subject you write "oosplash.bin possibly compiled against wrong version 
of
libpng12". 

No, oosplash is compiled against the *correct* libpng12, sou have a wrong 
version in 
/usr/local.

Remove it and/or fix it.

Closing.

Grüße/Regards,

René
-- 
 .''`.  René Engelhard -- Debian GNU/Linux Developer
 : :' : http://www.debian.org | http://people.debian.org/~rene/
 `. `'  r...@debian.org | GnuPG-Key ID: D03E3E70
   `-   Fingerprint: E12D EA46 7506 70CF A960 801D 0AA0 4571 D03E 3E70



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

Bug#644395: libreoffice-core: oosplash.bin possibly compiled against wrong version of libpng12

[Gian Uberto Lauri]

Package: libreoffice-core
Version: 1:3.4.3-1
Severity: critical

Dear Maintainer,

the last update of the system introduced a critical malfunctionn in libreoffice:

saint@quigley:~
14:33:11 [24] $soffice
/usr/lib/libreoffice/program/oosplash.bin: /usr/local/lib/libpng12.so.0: no 
version information available (required by 
/usr/lib/libreoffice/program/oosplash.bin)
/usr/lib/libreoffice/program/oosplash.bin: symbol lookup error: 
/usr/local/lib/libpng12.so.0: undefined symbol: inflateInit_

and the progam fails to start, preventing me from doing any work that require 
accessing my ODT files.

*** Please consider answering these questions, where appropiate ***

   * What led up to the situation?

The last apt-get upgrade.

   * What exactly did you do (or not do) that was effective (or
 ineffective)?

Nothing effective

   * What was the outcome of this action?

libreoffice not starting

   * What outcome did you expect instead?

libreoffice starting

*** End of the template - remove these lines ***


-- Package-specific info:
All deployed shared extensions:


All deployed user extensions:



-- System Information:
Debian Release: wheezy/sid
  APT prefers testing
  APT policy: (500, 'testing')
Architecture: amd64 (x86_64)

Kernel: Linux 2.6.32-5-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/bash

Versions of packages libreoffice-core depends on:
ii  fontconfig   2.8.0-3
ii  libatk1.0-0  2.0.1-2
ii  libc62.13-7 
ii  libcairo21.10.2-6.1 
ii  libcurl3-gnutls  7.21.7-1   
ii  libdb5.1 5.1.25-11  
ii  libexpat12.0.1-7
ii  libfontconfig1   2.8.0-3
ii  libfreetype6 2.4.6-2
ii  libgcc1  1:4.6.0-10 
ii  libgdk-pixbuf2.0-0   2.24.0-1   
ii  libglib2.0-0 2.28.6-1   
ii  libgraphite2-2.0.0   1.0.3.real-1   
ii  libgstreamer-plugins-base0.10-0  0.10.35-1  
ii  libgstreamer0.10-0   0.10.35-1  
ii  libgtk2.0-0  2.24.4-3   
ii  libhunspell-1.2-01.2.14-4   
ii  libhyphen0   2.7.1-4
ii  libice6  2:1.0.7-2  
ii  libicu44 4.4.2-2
ii  libjpeg8 8c-2   
ii  libmythes-1.2-0  2:1.2.1-1  
ii  libneon27-gnutls 0.29.6-1   
ii  libnspr4-0d  4.8.9-1
ii  libnss3-1d   3.12.11-3  
ii  libpango1.0-01.28.4-3   
ii  libpng12-0   1.2.46-3   
ii  librdf0  1.0.13-3   
ii  libreoffice-common   1:3.4.3-1  
ii  libsm6   2:1.2.0-2  
ii  libssl1.0.0  1.0.0e-2   
ii  libstdc++6   4.6.0-10   
ii  libtextcat0  2.2-9  
ii  libx11-6 2:1.4.3-2  
ii  libxaw7  2:1.0.9-2  
ii  libxext6 2:1.2.0-2  
ii  libxinerama1 2:1.1.1-3  
ii  libxml2  2.7.8.dfsg-4   
ii  libxrandr2   2:1.3.2-2  
ii  libxrender1  1:0.9.6-2  
ii  libxslt1.1   1.1.26-8   
ii  libxt6   1:1.1.1-2  
ii  ttf-opensymbol   2:2.4.3+LibO3.4.3-1
ii  ure  3.4.3-1
ii  zlib1g   1:1.2.3.4.dfsg-3   

libreoffice-core recommends no packages.

libreoffice-core suggests no packages.

Versions of packages libreoffice-common depends on:
ii  libreoffice-style-crystal [libreoffice-style]  1:3.4.3-1
ii  libreoffice-style-tango [libreoffice-style]1:3.4.3-1
ii  ure3.4.3-1  

Versions of packages libreoffice-common recommends:
ii  libtextcat-data  2.2-9
ii  xfonts-mathml4

Versions of packages libreoffice-common suggests:
ii  libreoffice-style-crystal 1:3.4.3-1
ii  libreoffice-style-hicontrast 
ii  libreoffice-style-oxygen 
ii  libreoffice-style-tango   1:3.4.3-1

Versions of packages libreoffice-java-common depends on:
ii  libjaxp1.3-java 1.3.05-1 
ii  libreoffice-common  1:3.4.3-1
ii  libxalan2-java  2.7.1-5  
ii  libxerces2-java 2.9.1-4.1

Versions of packages ttf-opensymbol recommends:
ii  fontconfig  2.8.0-3

Versions of packages libreoffice-core is related to:
pn  fglrx-driver  

Bug#644392: dspam truncates mail

[Laurence Withers]

Package: dspam
Version: 3.10.1+dfs
Severity: critical
Justification: causes serious data loss


I have discovered that dspam is truncating inbound email after it has been
scanned. Please consider the size field (S=) in the following exim log
entries:

2011-10-05 01:58:48 1RBGky-0007w4-3k <= linux-omap-ow...@vger.kernel.org 
H=mail2.jellyfishnet.co.uk [93.91.20.10] P=esmtps X=TLS1.0:RSA_ARCFOUR_MD5:16 
S=6021 id=2a3dcf3da181ad40bde86a3150b27b6b03b4fb3...@dbde02.ent.ti.com
2011-10-05 01:58:48 1RBGky-0007wE-9z <= linux-omap-ow...@vger.kernel.org 
U=dspam P=spam-scanned S=3591 
id=2a3dcf3da181ad40bde86a3150b27b6b03b4fb3...@dbde02.ent.ti.com
2011-10-05 01:58:48 1RBGky-0007w4-3k => guralp  
R=spamscan T=spamcheck
2011-10-05 01:58:48 1RBGky-0007w4-3k Completed

As you can see, there is a significant drop in size between the mail being
received from a remote SMTP server (6021 bytes) and after it has been scanned
by DSPAM (3591 bytes).

The mail as it should be is visible here:

http://article.gmane.org/gmane.linux.ports.arm.omap/65281

The mail as I received it ends after the word "earlier" and immediately
before the period. I can of course provide a copy as written in my .maildir
on request.

-- System Information:
Debian Release: 6.0.2
  APT prefers stable
  APT policy: (1001, 'stable'), (500, 'stable-updates')
Architecture: amd64 (x86_64)

Kernel: Linux 2.6.32-5-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash



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

Bug#644254: im-config: problems in IM Module settings

[Osamu Aoki]

Hi,


On Wed, Oct 05, 2011 at 07:37:01AM +0800, Aron Xu wrote:
> On Wed, Oct 5, 2011 at 04:25, Osamu Aoki  wrote:
> > [...]
> > By the way, where is doc on how to use version specific QT4_IM_MODULE,
> > GTK2_IM_MODULE or GKT3_IM_MODULE?
> >
> 
> QT4_IM_MODULE was added in QT 4.5.0, see:
> http://qt.nokia.com/products/changes/changes-4.5.0/
> In Squeeze, the version of libqt4* is 4.6.3, so there is no problem as
> far as I can see.
> 
> It works like QT4_IM_MODULE=ibus
> 
> There is no variables like GTK2_IM_MODULE or GKT3_IM_MODULE to the
> best of my knowledge, and after some small tests I am confident that
> these two variables don't exist. We may contact the GTK package
> maintainer and/or file an upstream bug report, to add a GTK3_IM_MODULE
> variable.

It sounds like good idea.  
 
> >> Further more, we should deal with Multi-Arch of those libraries, which 
> >> means:
> >> > for IM_CONFIG_MARKER in /usr/lib/gtk-2.0/*/immodules/im-ibus.so 
> >> > /usr/lib/*/gtk-2.0/*/immodules/im-ibus.so ; do
> >> and
> >> > for IM_CONFIG_MARKER in 
> >> > /usr/lib/qt4/plugins/inputmethods/libqtim-ibus.so 
> >> > /usr/lib/*/qt4/plugins/inputmethods/libqtim-ibus.so ; do
> >>
> >> This is needed because transition to Mult-Arch is in progress, we need
> >> to take care of all the situations.
> >
> > Multi-Arch is black magic for me now. patch welcomed.
> >
> > Osamu
> >
> 
> I'll do this for you in a few days.

Let's fix ibus case first then follow other IMs.

> -- 
> Regards,
> Aron Xu



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

Bug#644389: suspect non-working mdadm.conf created during install

[pille]

Package: mdadm
Version: 3.1.4-1+8efb9d1
Severity: critical
Tags: d-i
Justification: breaks the whole system

during install of squeeze i partitioned my disks and setup different MD-RAID 
devices using the partition tool.
the corresponding /dev/mdX devices were created properly and i went on creating 
LVM ontop of it and successfully installed the system.

first boot into my new system failed because the root FS could not be found, 
leaving me in a initramfs-shell.
i assembled my RAID devices by hand and compared /etc/mdadm/mdadm.conf (inside 
initramfs) with 'mdadm --examine --scan', which listed completely different 
UUIDs. the count of my MD-devices was ok, but all names were prefixed with 
hostname 'hetzner'.

after booting, fixing (the systems) /etc/mdadm/mdadm.conf and update-initramfs
all went fine.

i don't remember the exact content, but install generated a mdadm.conf like:
  ARRAY /dev/md/0 metadata=1.2 UUID=12345678:12345678:12345678:12345678 
name=hetzner:0
  ARRAY /dev/md/1 metadata=1.2 UUID=24680135:24680135:24680135:24680135 
name=hetzner:1
  ARRAY /dev/md/2 metadata=1.2 UUID=abcdef12:abcdef12:abcdef12:abcdef12 
name=hetzner:2

(UUIDs are made up)

disks used were new & empty and had no affiliation to hetzner online AG
you can search the net for '"name=hetzner:" mdadm.conf' to yield probably the 
original UUIDs.

  pille

--- initrd.img-2.6.32-5-amd64:
47498 blocks
3718babf31303bc28114430ec0182e14  ./etc/mdadm/mdadm.conf
d24ed7389311fb002ff017c8acb3a032  
./lib/modules/2.6.32-5-amd64/kernel/drivers/md/dm-mirror.ko
4818680648975a4d4181181df95de446  
./lib/modules/2.6.32-5-amd64/kernel/drivers/md/dm-log.ko
bb013669544366b71ebd8b335a7d8b0a  
./lib/modules/2.6.32-5-amd64/kernel/drivers/md/dm-mod.ko
ee2079d7e0bf4da6b64af9e579f6c0ae  
./lib/modules/2.6.32-5-amd64/kernel/drivers/md/raid456.ko
b210dd35ca38b2e33637351a979561c9  
./lib/modules/2.6.32-5-amd64/kernel/drivers/md/multipath.ko
0c8325eb1abcf4ad33e45a20d44c5bf8  
./lib/modules/2.6.32-5-amd64/kernel/drivers/md/dm-crypt.ko
f25a213d65a481b66cfdbf8f6453aacf  
./lib/modules/2.6.32-5-amd64/kernel/drivers/md/dm-region-hash.ko
cc5177855661025115a2ef74d0d394d6  
./lib/modules/2.6.32-5-amd64/kernel/drivers/md/raid0.ko

-- System Information:
Debian Release: 6.0.2
  APT prefers stable
  APT policy: (990, 'stable'), (500, 'stable-updates'), (500, 'testing')
Architecture: amd64 (x86_64)

Kernel: Linux 2.6.32-5-amd64 (SMP w/2 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

Versions of packages mdadm depends on:
ii  debconf 1.5.36.1 Debian configuration management sy
ii  libc6   2.11.2-10Embedded GNU C Library: Shared lib
ii  lsb-base3.2-23.2squeeze1 Linux Standard Base 3.2 init scrip
ii  udev164-3/dev/ and hotplug management daemo

Versions of packages mdadm recommends:
ii  exim4-daemon-light [mail 4.72-6+squeeze2 lightweight Exim MTA (v4) daemon
ii  module-init-tools3.12-1  tools for managing Linux kernel mo

mdadm suggests no packages.

-- debconf information:
  mdadm/autostart: true
  mdadm/mail_to: root
  mdadm/initrdstart_msg_errmd:
  mdadm/initrdstart: all
  mdadm/initrdstart_msg_errconf:
  mdadm/initrdstart_notinconf: false
  mdadm/initrdstart_msg_errexist:
  mdadm/initrdstart_msg_intro:
  mdadm/autocheck: true
  mdadm/initrdstart_msg_errblock:
  mdadm/start_daemon: true



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

Bug#644277: marked as done (mobyle: FTBFS when only building architecture-dependent packages)

[Debian Bug Tracking System]

Your message dated Wed, 05 Oct 2011 12:17:19 +
with message-id 
and subject line Bug#644277: fixed in mobyle 1.0.2~dfsg-2
has caused the Debian Bug report #644277,
regarding mobyle: FTBFS when only building architecture-dependent 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.)


-- 
644277: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=644277
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: mobyle
Version: 1.0.2~dfsg-1
Severity: serious
Justification: fails to build from source

Hi, Olivier.

I've found that builds of mobyle covering only the architecture-dependent
mobyle-utils package (as on the autobuilders) are failing:

  mv debian/mobyle/usr/share/mobyle/htdocs/data debian/mobyle/var/lib/mobyle/
  mv: cannot move `debian/mobyle/usr/share/mobyle/htdocs/data' to 
`debian/mobyle/var/lib/mobyle/': No such file or directory
  make[1]: *** [override_dh_auto_install] Error 1
  make[1]: Leaving directory `.../mobyle-1.0.2~dfsg'
  make: *** [binary-arch] Error 2

There are various ways to account for this possibility, but I'd suggest
tightening mobyle's build dependency on debhelper to (>= 8.9.7) and
proceeding to factor out separate override_dh_auto_install-arch and
override_dh_auto_install-indep targets (along with a -common target on
which they could both depend that would run setup.py):

clean:
dh clean --with python2
rm -f debian/common-install-stamp

debian/common-install-stamp:
python setup.py install ...
find ... | xargs sed ...
find ... | xargs sed ...
touch $@

override_dh_auto_install-arch: debian/common-install-stamp
mv debian/mobyle/usr/share/mobyle/core/Tools/setsid \
debian/mobyle-utils/usr/bin/mobyle-setsid

override_dh_auto_install-indep: debian/common-install-stamp
# The old override_dh_auto_install target's remaining commands.

At any rate, please test with svn-buildpackage -B or the like to confirm
that builds only covering mobyle-utils succeed.

Thanks!


--- End Message ---
--- Begin Message ---
Source: mobyle
Source-Version: 1.0.2~dfsg-2

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

mobyle-utils_1.0.2~dfsg-2_amd64.deb
  to main/m/mobyle/mobyle-utils_1.0.2~dfsg-2_amd64.deb
mobyle_1.0.2~dfsg-2.debian.tar.gz
  to main/m/mobyle/mobyle_1.0.2~dfsg-2.debian.tar.gz
mobyle_1.0.2~dfsg-2.dsc
  to main/m/mobyle/mobyle_1.0.2~dfsg-2.dsc
mobyle_1.0.2~dfsg-2_all.deb
  to main/m/mobyle/mobyle_1.0.2~dfsg-2_all.deb



A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 644...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Olivier Sallou  (supplier of updated mobyle package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Wed, 05 Oct 2011 13:35:00 +0900
Source: mobyle
Binary: mobyle mobyle-utils
Architecture: source all amd64
Version: 1.0.2~dfsg-2
Distribution: unstable
Urgency: low
Maintainer: Debian Med Packaging Team 

Changed-By: Olivier Sallou 
Description: 
 mobyle - Web portal that provides web forms for command-line software
 mobyle-utils - binary tools used by Mobyle
Closes: 644277
Changes: 
 mobyle (1.0.2~dfsg-2) unstable; urgency=low
 .
   * debian/rules :  Thanks to A. Ucko
   - fix issue when building arch depandant only package (Closes: #644277)
Checksums-Sha1: 
 b3e4192479b8bc296daafa697e9e46d964d8f1fd 2206 mobyle_1.0.2~dfsg-2.dsc
 567dce2415ca4f7b5a96f71b50c6cfdfe8ea3cc0 13804 
mobyle_1.0.2~dfsg-2.debian.tar.gz
 d794058a74614c3ef8dfd12e1f4ee97eda148e7d 4473060 mobyle_1.0.2~dfsg-2_all.deb
 4b97111be447c8c94a2dc13b5fd8a9bd3524429c 12130 
mobyle-utils_1.0.2~dfsg-2_amd64.deb
Checksums-Sha256: 
 9228a7711ecf3bb43a00067efbd435dab9bab36d7448a1901a846a831754407f 2206 
mobyle_1.0.2~dfsg-2.dsc
 b58867aa5a8e781bf0d40dda72bc6f08d59eff48711d6d5ad69df3b062973ad0 13804 
mobyle_1.0.2~dfsg-2.debian.tar.gz
 a580efd5df0b0bf955282f9aa46ebd192bc229c039a80b62264ef0bb8b995074 4473060 
mobyle_1.0.2~dfsg-2_all.deb
 dc523a8da27edbd4f9cbd9a47837da8aec5b7f33a7a22f045a6a768d76a210b9 12130 
mobyle-utils_1.0.2~dfsg-2_amd64.deb
Files: 
 dc276ba061ae3ea6593559e053d3a0d7 2206 science optional mobyle_1.0.2

Bug#618956: can't install cgroup-bin

[Lucas]

Hello,

Can't install cgroup-bin ( 0.36.2-3+squeeze1 ) on squeeze :

apt-get install cgroup-bin
Lecture des listes de paquets... Fait
Construction de l'arbre des dépendances
Lecture des informations d'état... Fait
Les NOUVEAUX paquets suivants seront installés :
  cgroup-bin
0 mis à jour, 1 nouvellement installés, 0 à enlever et 0 non mis à jour.
Il est nécessaire de prendre 0 o/54,8 ko dans les archives.
Après cette opération, 279 ko d'espace disque supplémentaires seront
utilisés.
Sélection du paquet cgroup-bin précédemment désélectionné.
(Lecture de la base de données... 42174 fichiers et répertoires déjà
installés.)
Dépaquetage de cgroup-bin (à partir de
.../cgroup-bin_0.36.2-3+squeeze1_i386.deb) ...
Traitement des actions différées (« triggers ») pour « man-db »...
Paramétrage de cgroup-bin (0.36.2-3+squeeze1) ...
Starting cgconfig service: Loading configuration file /etc/cgconfig.conf
failed
Cgroup mounting failed
Failed to parse /etc/cgconfig.conf ... failed!
invoke-rc.d: initscript cgconfig, action "start" failed.
dpkg : erreur de traitement de cgroup-bin (--configure) :
 le sous-processus script post-installation installé a retourné une erreur
de sortie d'état 1
configured to not write apport reports
  Des erreurs ont été rencontrées
pendant l'exécution :
 cgroup-bin
E: Sub-process /usr/bin/dpkg returned an error code (1)


If we try to start :

/etc/init.d/cgconfig start
Starting cgconfig service: Loading configuration file /etc/cgconfig.conf
failed
Cgroup mounting failed
Failed to parse /etc/cgconfig.conf ... failed!


A problem with the config file ? so let's try :

cgconfigparser -l /etc/cgconfig.conf
Loading configuration file /etc/cgconfig.conf failed
Cgroup mounting failed

A strace ?
http://pastebin.com/CvR00EuS

I have no mount point in the fstab and nothing from cgroups in /proc/ but
folder /mnt/cgroups exist.


-- System Information:
Debian Release: 6.0.2
  APT prefers stable
  APT policy: (700, 'stable'), (650, 'testing')
Architecture: i386 (i686)

Kernel: Linux 2.6.35.8.-V1.1 (SMP w/4 CPU cores)
Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

Versions of packages cgroup-bin depends on:
ii  libc6  2.11.2-10 Embedded GNU C Library: Shared
lib
ii  libcgroup1 0.36.2-3+squeeze1 A library to control and
monitor c

cgroup-bin recommends no packages.

cgroup-bin suggests no packages.

-- Configuration Files:
/etc/cgconfig.conf changed:
mount {
cpuacct = /mnt/cgroups/cpuacct;
devices = /mnt/cgroups/devices;
}


-- no debconf information

If more information is needed, mail me.
Hope this will be fixed soon.

Bug#625835: kplayer crashes at startup

[groenedraeck]

A follow-up on my post at Sat, 14 May 2011 22:21:31 +0200 (Messsage
#10 at 625...@bugs.debian.org), it was found that after a full system
reboot and starting the application by clicking a movie file, the
problem was found to be resolved. Hereafter, starting the program from
the Kickoff Application Launcher (start menu) worked as well as
starting it by clicking a movie file. In my case, the problem could no
long be reproduced.



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

Bug#643304: marked as done (python-awn-extras: can't install: unable to open '/usr/share/pyshared/awn/extras/__init__.py.dpkg-new')

[Debian Bug Tracking System]

Your message dated Wed, 5 Oct 2011 13:18:16 +0200
with message-id <20111005111816.ga1...@jwilk.net>
and subject line Re: Bug#643304: stat output
has caused the Debian Bug report #643304,
regarding python-awn-extras: can't install: unable to open 
'/usr/share/pyshared/awn/extras/__init__.py.dpkg-new'
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.)


-- 
643304: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=643304
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: python-awn-extras
Version: 0.4.0-3.1
Severity: grave
Justification: renders package unusable

Dear Maintainer,

I attempted to upgrade to AWN 4.0.4 in sid. All my other packages are
up to date. python-awn-extras fails to install with the following
message:

Retrieving bug reports... Done
Parsing Found/Fixed information... Done
(Reading database ... 336028 files and directories currently installed.)
Unpacking python-awn-extras (from .../python-awn-extras_0.4.0-4_amd64.deb) ...
dpkg: error processing 
/var/cache/apt/archives/python-awn-extras_0.4.0-4_amd64.deb (--unpack):
 unable to open '/usr/share/pyshared/awn/extras/__init__.py.dpkg-new': No such 
file or directory
configured to not write apport reports

The package, and thus awn-python-applets-{core, extras}, cannot be installed.


-- System Information:
Debian Release: wheezy/sid
  APT prefers unstable
  APT policy: (500, 'unstable'), (1, 'experimental')
Architecture: amd64 (x86_64)

Kernel: Linux 3.0.4 (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 python-awn-extras depends on:
ii  python  2.6.7-3
ii  python-support  1.0.14 

python-awn-extras recommends no packages.

python-awn-extras suggests no packages.

-- no debconf information


--- End Message ---
--- Begin Message ---

* nick black , 2011-10-04, 10:42:
Did you create the symlink manually, perhaps following the "advice" 
from ?


this was precisely the issue. thanks!


Thanks for information. As Gergely Nagy said in 
, your problem should go away if you 
remove and then reinstall the package.


I'm closing the bug now, as it was caused by user error.

--
Jakub Wilk

--- End Message ---

Processed: tagging 644138

[Debian Bug Tracking System]

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

> tags 644138 + confirmed
Bug #644138 [heimdal-clients,kcc] kcc and heimdal-clients: error when trying to 
install together
Ignoring request to alter tags of bug #644138 to the same tags previously set
> thanks
Stopping processing here.

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


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

Processed: tagging 644138

[Debian Bug Tracking System]

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

> tags 644138 + confirmed
Bug #644138 [heimdal-clients,kcc] kcc and heimdal-clients: error when trying to 
install together
Added tag(s) confirmed.
> thanks
Stopping processing here.

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

[Debian Bug Tracking System]

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

> severity 644296 grave
Bug #644296 [python-restkit] python-restkit can't be installed because it 
depends on python-http-parser which no package provides
Severity set to 'grave' from 'normal'

> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
644296: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=644296
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#632673: Message from the original reporter :)

[Manuel Bilderbeek]

Hi all,

For some reason, I don't get updates on bugs I reported.

Anyway, to clarify some things:
- I have kdm installed (it comes with KDE and I wanted some KDE apps), 
but it's not the default display manager, so it's never actually started
- I am using gdm for years and years and as I wrote in the initial 
report, moved to gdm3 a few weeks before I reported it. So, I really 
have it installed, no doubt about it.


If you need any more info, please contact me directly on this mail address.

--
Kind regards,

Manuel



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

Bug#642310: overwrite error: /usr/share/man/man2/io_getevents.2.gz

[Goswin von Brederlow]

Guillem Jover  writes:

> On Wed, 2011-09-28 at 10:30:53 +0200, Goswin von Brederlow wrote:
>> Guillem Jover  writes:
>> > On Wed, 2011-09-21 at 14:28:46 +0200, Goswin von Brederlow wrote:
>> >> Trying to upgarde libaio-dev fails with:
>> >> 
>> >> Unpacking replacement libaio-dev ...
>> >> dpkg: error processing 
>> >> /var/cache/apt/archives/libaio-dev_0.3.109-2_amd64.deb (--unpack):
>> >>  trying to overwrite '/usr/share/man/man2/io_getevents.2.gz', which is 
>> >> also in package manpages-dev 3.28-1
>> >
>> > This is a bug in manpages, which included those when libaio-dev has
>> > always provided them, fixed in manpages-dev 3.32-0.2, you should
>> > upgrade that one. (Bug #636704)
>
>> Upgrades have to work in any order or packages have to say otherwise
>> (breaks, conflicts, replaces, ...) so that isn't really a solution.
>
> We are talking about a buggy package (manpages-dev) that does not exist
> anymore on the archive, is not in any stable release, and for which
> there's a fix released in testing already.
>
> So for starters serious here is way way out of proportion.
>
> Even if libaio-dev was to drop the pages right now, there would still
> be a period where upgrades can break, there's no way around this fact.
> unstable and testing break from time to time, if you cannot cope with
> that do not use them...

No, there wouldn't.

Upgrading manpages-dev first would introduce the Replaces so that works
and upgrading libaio-dev first would remove the conflicting files. So
either order would work, unlike now.

>> Also manpages-dev says:
>> 
>>* debian/control: add Replace against libaio-dev, because of
>>  aio_init.3.gz and lio_listio.3.gz (Closes: #636704)
>> 
>> That is only approriate when the files are moved from libaio-dev to
>> manpages-dev and clearly libaio-dev has not droped those files.
>
> They have not moved yet, that does not make manpages-dev wrong,
> neither libaio-dev. If manpages-dev did not have missed the Replaces
> on the first place the overwritting issue would not have ever existed.
>
>> So one or both of the two packages are wrong.
>
> I strongly disagree, and as such I'm re-closing this now.
>
> regards,
> guillem

MfG
Goswin



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

Bug#643848: marked as done (wsjt: FTBFS: /bin/sh: 1: /usr/bin/f2py: not found)

[Debian Bug Tracking System]

Your message dated Wed, 5 Oct 2011 12:12:06 +0200
with message-id <20111005101206.ga1...@jwilk.net>
and subject line Re: Bug#643848: wsjt: FTBFS: /bin/sh: 1: /usr/bin/f2py: not 
found
has caused the Debian Bug report #643848,
regarding wsjt: FTBFS: /bin/sh: 1: /usr/bin/f2py: 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.)


-- 
643848: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=643848
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:wsjt
Version: 5.9.7.r383-1.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 buildds:

/usr/bin/f2py -c --quiet --opt="-O -Wall -O0 -g  -Wall -O0 -g -DBIGSYM=1 -fPIC 
-DPACKAGE_NAME=\"wsjt\" -DPACKAGE_TARNAME=\"wsjt\" -DPACKAGE_VERSION=\"5.9.6\" 
-DPACKAGE_STRING=\"wsjt\ 5.9.6\" -DPACKAGE_BUGREPORT=\"\" -DPACKAGE_URL=\"\" 
-DSTDC_HEADERS=1 -DHAVE_SYS_TYPES_H=1 -DHAVE_SYS_STAT_H=1 -DHAVE_STDLIB_H=1 
-DHAVE_STRING_H=1 -DHAVE_MEMORY_H=1 -DHAVE_STRINGS_H=1 -DHAVE_INTTYPES_H=1 
-DHAVE_STDINT_H=1 -DHAVE_UNISTD_H=1 -DHAVE_INTTYPES_H=1 -DHAVE_STDINT_H=1 
-DHAVE_SYS_RESOURCE_H=1 -DHAVE_SYS_PARAM_H=1 -DHAVE_ERRNO_H=1 
-DHAVE_SYS_SYSLOG_H=1 -DHAVE_STDDEF_H=1 -DHAVE_LIBGEN_H=1 -DHAVE_SYS_WAIT_H=1 
-DHAVE_WAIT_H=1 -DHAVE_STDIO_H=1 -DHAVE_TERMIOS_H=1 -DHAVE_SYS_RESOURCE_H=1 
-DHAVE_LINUX_PPDEV_H=1 -DHAVE_SYS_STAT_H=1 -DHAVE_FCNTL_H=1 
-DHAVE_SYS_IOCTL_H=1 -DTIME_WITH_SYS_TIME=1 -DSTRING_WITH_STRINGS=1 
-DSIZEOF_INT64_T=8 -DSIZEOF_LONG_LONG=8 -DNDEBUG=1 -DPREFIX=\"/usr\" 
-DFC_LIB_PATH=\"/usr/lib/gcc/x86_64-linux-gnu/4.6\" -DFC=\"/usr/bin/gfortran\" 
-DUSE_PORTAUDIO=1 -DHAS_ASOUNDLIB_H=1 -DHAS_SOUNDCARD_H=1 -DHAS_JACK_H=1 
-DHAS_PORTAUDIO_H=1 -DHAS_SAMPLERATE_H=1 \
-fno-second-underscore" init_rs.o encode_rs.o decode_rs.o wsjt1.o 
astro.o azdist.o coord.o dcoord.o deg2grid.o dot.o ftsky.o geocentric.o 
GeoDist.o grid2deg.o moon2.o MoonDop.o sun.o toxyz.o pfxdump.o avesp2.o bzap.o 
spec441.o spec2d.o mtdecode.o stdecode.o indexx.o s2shape.o flat2.o gen65.o 
chkmsg.o gen6m.o gentone.o syncf0.o syncf1.o synct.o decode6m.o avemsg6m.o 
set.o flatten.o db.o pctile.o sort.o ssort.o ps.o smooth.o ping.o longx.o 
peakup.o sync.o detect.o avemsg65.o decode65.o demod64a.o encode65.o extract.o 
chkhist.o flat1.o four2.o rfile2.o gencw.o getpfx1.o getpfx2.o getsnr.o 
graycode.o grid2k.o interleave63.o k2grid.o limit.o lpf1.o morse.o nchar.o 
packcall.o packgrid.o packmsg.o packtext.o setup65.o short65.o slope.o 
spec2d65.o sync65.o unpackcall.o unpackgrid.o unpackmsg.o unpacktext.o xcor.o 
xfft.o xfft2.o wsjt65.o ftpeak65.o fil651.o fil652.o fil653.o symsync65.o 
deep65.o -m Audio \
--f77exec=/usr/bin/gfortran --f90exec=/usr/bin/gfortran -I/usr/include 
-I/usr/local/include -I/usr/include/alsa -I/usr/local/include/alsa  
-DPACKAGE_NAME=\"wsjt\" -DPACKAGE_TARNAME=\"wsjt\" -DPACKAGE_VERSION=\"5.9.6\" 
-DPACKAGE_STRING=\"wsjt\ 5.9.6\" -DPACKAGE_BUGREPORT=\"\" -DPACKAGE_URL=\"\" 
-DSTDC_HEADERS=1 -DHAVE_SYS_TYPES_H=1 -DHAVE_SYS_STAT_H=1 -DHAVE_STDLIB_H=1 
-DHAVE_STRING_H=1 -DHAVE_MEMORY_H=1 -DHAVE_STRINGS_H=1 -DHAVE_INTTYPES_H=1 
-DHAVE_STDINT_H=1 -DHAVE_UNISTD_H=1 -DHAVE_INTTYPES_H=1 -DHAVE_STDINT_H=1 
-DHAVE_SYS_RESOURCE_H=1 -DHAVE_SYS_PARAM_H=1 -DHAVE_ERRNO_H=1 
-DHAVE_SYS_SYSLOG_H=1 -DHAVE_STDDEF_H=1 -DHAVE_LIBGEN_H=1 -DHAVE_SYS_WAIT_H=1 
-DHAVE_WAIT_H=1 -DHAVE_STDIO_H=1 -DHAVE_TERMIOS_H=1 -DHAVE_SYS_RESOURCE_H=1 
-DHAVE_LINUX_PPDEV_H=1 -DHAVE_SYS_STAT_H=1 -DHAVE_FCNTL_H=1 
-DHAVE_SYS_IOCTL_H=1 -DTIME_WITH_SYS_TIME=1 -DSTRING_WITH_STRINGS=1 
-DSIZEOF_INT64_T=8 -DSIZEOF_LONG_LONG=8 -DNDEBUG=1 -DPREFIX=\"/usr\" 
-DFC_LIB_PATH=\"/usr/lib/gcc/x86_64-linux-gnu/4.6\" -DFC=\"/usr/bin/gfortran\" 
-DUSE_PORTAUDIO=1 -DHAS_ASOUNDLIB_H=1 -DHAS_SOUNDCARD_H=1 -DHAS_JACK_H=1 
-DHAS_PORTAUDIO_H=1 -DHAS_SAMPLERATE_H=1 -I. -L/usr/lib -L/usr/local/lib  
-L/usr/lib/gcc/x86_64-linux-gnu/4.6 -lpthread  -lrt -lsamplerate -lportaudio \
only: ftn_init ftn_quit audio_init spec getfile azdist0 astro0 \
: abc441.F90 astro0.F90 audio_init.F90 azdist0.f90 blanker.f90 
decode1.F90 decode2.f90 decode3.F90 ftn_init.F90 ftn_quit.f90 get_fname.F90 
getfile.F90 horizspec.f90 hscroll.f90 i1tor4.f90 pix2d.f90 pix2d65.f90 
rfile.f90 savedata.F90 spec.f90 wsjtgen.F90 runqqq.F90 fivehz.F90 \
ptt_unix.c igray.c wrapkarn.c cutil.c a2d.f90 jtaudio.c resample.c 
start_portaudio.c
/bin/sh: 1: /usr/bin/f2py: not found
make[1]: *** [Audio.so] Error 127
make[1]: Leaving directory 
`/build/buildd-wsjt_5.9.7.r383-1.5+b1-amd64-dLF6VD/wsjt-5.9.7.r383'
make: *** [build-s

Processed: found 644346 in 0.8.2-1, notfound 644346 in 0.7.3-1

[Debian Bug Tracking System]

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

> found 644346 0.8.2-1
Bug #644346 [identicurse] identicurse: conflict on upgrade
Bug Marked as found in versions identicurse/0.8.2-1.
> notfound 644346 0.7.3-1
Bug #644346 [identicurse] identicurse: conflict on upgrade
Bug No longer marked as found in versions identicurse/0.7.3-1.
> thanks
Stopping processing here.

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

[Debian Bug Tracking System]

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

> severity 637921 important
Bug #637921 [libgtk2.0-0] numerous gtk ui apps, reportbug, geany crash with 
assertion failures
Severity set to 'important' from 'serious'

> thanks
Stopping processing here.

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