Bug#614089: marked as done (nvidia-graphics-modules: needs updating to newer kernels)

[Debian Bug Tracking System]

Your message dated Thu, 28 Jun 2012 06:48:51 +
with message-id 
and subject line Bug#614089: fixed in nvidia-graphics-modules 302.17+1
has caused the Debian Bug report #614089,
regarding nvidia-graphics-modules: needs updating to newer kernels
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.)


-- 
614089: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=614089
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: nvidia-graphics-modules
Version: 195.36.31+2
Severity: serious

Hi,

linux-2.6 is now at 2.6.37 in sid, so I'm looking at removing
nvidia-graphics-modules from testing when the kernel gets ready to
migrate.  Filing this as a reminder.

Cheers,
Julien


--- End Message ---
--- Begin Message ---
Source: nvidia-graphics-modules
Source-Version: 302.17+1

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

nvidia-graphics-modules_302.17+1.dsc
  to non-free/n/nvidia-graphics-modules/nvidia-graphics-modules_302.17+1.dsc
nvidia-graphics-modules_302.17+1.tar.gz
  to non-free/n/nvidia-graphics-modules/nvidia-graphics-modules_302.17+1.tar.gz
nvidia-kernel-2.6-486_302.17+1_i386.deb
  to non-free/n/nvidia-graphics-modules/nvidia-kernel-2.6-486_302.17+1_i386.deb
nvidia-kernel-2.6-686-pae_302.17+1_i386.deb
  to 
non-free/n/nvidia-graphics-modules/nvidia-kernel-2.6-686-pae_302.17+1_i386.deb
nvidia-kernel-2.6-amd64_302.17+1_amd64.deb
  to 
non-free/n/nvidia-graphics-modules/nvidia-kernel-2.6-amd64_302.17+1_amd64.deb
nvidia-kernel-2.6-amd64_302.17+1_i386.deb
  to 
non-free/n/nvidia-graphics-modules/nvidia-kernel-2.6-amd64_302.17+1_i386.deb
nvidia-kernel-2.6-rt-686-pae_302.17+1_i386.deb
  to 
non-free/n/nvidia-graphics-modules/nvidia-kernel-2.6-rt-686-pae_302.17+1_i386.deb
nvidia-kernel-2.6-rt-amd64_302.17+1_amd64.deb
  to 
non-free/n/nvidia-graphics-modules/nvidia-kernel-2.6-rt-amd64_302.17+1_amd64.deb
nvidia-kernel-3.2.0-3-486_302.17+1+2+3.2.21-2_i386.deb
  to 
non-free/n/nvidia-graphics-modules/nvidia-kernel-3.2.0-3-486_302.17+1+2+3.2.21-2_i386.deb
nvidia-kernel-3.2.0-3-686-pae_302.17+1+2+3.2.21-2_i386.deb
  to 
non-free/n/nvidia-graphics-modules/nvidia-kernel-3.2.0-3-686-pae_302.17+1+2+3.2.21-2_i386.deb
nvidia-kernel-3.2.0-3-amd64_302.17+1+2+3.2.21-2_amd64.deb
  to 
non-free/n/nvidia-graphics-modules/nvidia-kernel-3.2.0-3-amd64_302.17+1+2+3.2.21-2_amd64.deb
nvidia-kernel-3.2.0-3-amd64_302.17+1+2+3.2.21-2_i386.deb
  to 
non-free/n/nvidia-graphics-modules/nvidia-kernel-3.2.0-3-amd64_302.17+1+2+3.2.21-2_i386.deb
nvidia-kernel-3.2.0-3-rt-686-pae_302.17+1+2+3.2.21-2_i386.deb
  to 
non-free/n/nvidia-graphics-modules/nvidia-kernel-3.2.0-3-rt-686-pae_302.17+1+2+3.2.21-2_i386.deb
nvidia-kernel-3.2.0-3-rt-amd64_302.17+1+2+3.2.21-2_amd64.deb
  to 
non-free/n/nvidia-graphics-modules/nvidia-kernel-3.2.0-3-rt-amd64_302.17+1+2+3.2.21-2_amd64.deb
nvidia-kernel-486_302.17+1_i386.deb
  to non-free/n/nvidia-graphics-modules/nvidia-kernel-486_302.17+1_i386.deb
nvidia-kernel-686-pae_302.17+1_i386.deb
  to non-free/n/nvidia-graphics-modules/nvidia-kernel-686-pae_302.17+1_i386.deb
nvidia-kernel-amd64_302.17+1_amd64.deb
  to non-free/n/nvidia-graphics-modules/nvidia-kernel-amd64_302.17+1_amd64.deb
nvidia-kernel-amd64_302.17+1_i386.deb
  to non-free/n/nvidia-graphics-modules/nvidia-kernel-amd64_302.17+1_i386.deb
nvidia-kernel-rt-686-pae_302.17+1_i386.deb
  to 
non-free/n/nvidia-graphics-modules/nvidia-kernel-rt-686-pae_302.17+1_i386.deb
nvidia-kernel-rt-amd64_302.17+1_amd64.deb
  to 
non-free/n/nvidia-graphics-modules/nvidia-kernel-rt-amd64_302.17+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 614...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Andreas Beckmann  (supplier of updated 
nvidia-graphics-modules package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Tue, 26 Jun 2012 11:01:35 +0200
Source: nvidia-graphics-modules
Binary: nvidia-kernel-amd64 nvidia-kernel-2.6-amd64 nvidia-kernel-3.2.0-3-amd64 
nvidia-kernel-486 nvidia-kernel-2.6-486 nvidia-kernel-3.2.0-3-486 
nvidia-kernel-686-pae nvidia-kernel-2.6-686-pae nvidia-kernel-3.2.0-3-686-pae 
nvidia-kernel-rt-686-pae nvidia-

Bug#675839: marked as done (boinc-app-seti: FTBFS[kfreebsd]: error: 'floor' was not declared in this scope)

[Debian Bug Tracking System]

Your message dated Thu, 28 Jun 2012 06:47:12 +
with message-id 
and subject line Bug#675839: fixed in boinc-app-seti 6.12~svn1306-1
has caused the Debian Bug report #675839,
regarding boinc-app-seti: FTBFS[kfreebsd]: error: 'floor' was not declared in 
this scope
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.)


-- 
675839: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=675839
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:boinc-app-seti
Version: 6.12~svn1305-2
Severity: serious
Tags: sid wheezy
User: debian-...@lists.debian.org
Usertags: kfreebsd
X-Debbugs-Cc: debian-...@lists.debian.org
Justification: fails to build from source (but built successfully in the past)

Hi!

Your package failed to build on the kfreebsd-* buildds:

vector/analyzeFuncs_sse.cpp: In function 'int sse1_ChirpData_ak(float (*)[2], 
float (*)[2], int, double, int, double)':
vector/analyzeFuncs_sse.cpp:782:62: error: 'floor' was not declared in this 
scope
vector/analyzeFuncs_sse.cpp: At global scope:
vector/analyzeFuncs_sse.cpp:1299:91: warning: deprecated conversion from string 
constant to 'char*' [-Wwrite-strings]
vector/analyzeFuncs_sse.cpp:2252:82: warning: deprecated conversion from string 
constant to 'char*' [-Wwrite-strings]
vector/analyzeFuncs_sse.cpp:2265:1: warning: 'typedef' was ignored in this 
declaration [enabled by default]
vector/analyzeFuncs_sse.cpp:2556:82: warning: deprecated conversion from string 
constant to 'char*' [-Wwrite-strings]
make[3]: *** [seti_boinc-analyzeFuncs_sse.o] Error 1

Full build log at
https://buildd.debian.org/status/fetch.php?pkg=boinc-app-seti&arch=kfreebsd-amd64&ver=6.12%7Esvn1305-2&stamp=1338167773

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: boinc-app-seti
Source-Version: 6.12~svn1306-1

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

boinc-app-seti-dbg_6.12~svn1306-1_amd64.deb
  to main/b/boinc-app-seti/boinc-app-seti-dbg_6.12~svn1306-1_amd64.deb
boinc-app-seti_6.12~svn1306-1.debian.tar.gz
  to main/b/boinc-app-seti/boinc-app-seti_6.12~svn1306-1.debian.tar.gz
boinc-app-seti_6.12~svn1306-1.dsc
  to main/b/boinc-app-seti/boinc-app-seti_6.12~svn1306-1.dsc
boinc-app-seti_6.12~svn1306-1_amd64.deb
  to main/b/boinc-app-seti/boinc-app-seti_6.12~svn1306-1_amd64.deb
boinc-app-seti_6.12~svn1306.orig.tar.gz
  to main/b/boinc-app-seti/boinc-app-seti_6.12~svn1306.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 675...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Steffen Moeller  (supplier of updated boinc-app-seti 
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, 29 May 2012 23:52:47 +0200
Source: boinc-app-seti
Binary: boinc-app-seti boinc-app-seti-dbg
Architecture: source amd64
Version: 6.12~svn1306-1
Distribution: unstable
Urgency: low
Maintainer: Debian BOINC Maintainers 
Changed-By: Steffen Moeller 
Description: 
 boinc-app-seti - SETI@home application for the BOINC client
 boinc-app-seti-dbg - debug symbols for SETI@home
Closes: 675839
Changes: 
 boinc-app-seti (6.12~svn1306-1) unstable; urgency=low
 .
   * New upstream version.
   * Added inclusion for kfreebsd (Closes: #675839)
Checksums-Sha1: 
 e801020aba9a4a0518bd79a4277401c5f6cbcab0 1618 boinc-app-seti_6.12~svn1306-1.dsc
 ccbcc3ecebc153a70f417bfe042ec23d157478ed 2832216 
boinc-app-seti_6.12~svn1306.orig.tar.gz
 13eb1dc43e5b7598548b4ba9b22eace12d3c5a10 11953 
boinc-app-seti_6.12~svn1306-1.debian.tar.gz
 c5c5b960e67264d74fd54b66e211a5a8c4637833 379922 
boinc-app-seti_6.12~svn1306-1_amd64.deb
 7748eb603d9d063a17e45350478ed693d5c60e4f 2304744 
boinc-app-seti-dbg_6.12~svn1306-1_amd64.deb
Checksums-Sha256: 
 9195382e6f1f24279a66e192a320a136dedee018a5c55339678ee60f9717c41b 1618 
boinc-app-seti_6.12~svn1306-1.dsc
 63e03d481663c8775848d176a9ba10a97a33d6a87ef49b4eb560ff8e266905a3 2832216 
boinc-app-seti_6.12~svn1306.orig.tar.gz
 508cde096d8482c999275a8caa2444f9b36c5a4453

Bug#679280: [xml/sgml-pkgs] Bug#679280: CVE-2012-2807

[Aron Xu]

tags 679280 + moreinfo
thanks

Hi,

I'm still investigating the problem and more details about it are
welcomed, please don't NMU for either unstable or stable.



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

Processed: Re: [xml/sgml-pkgs] Bug#679280: CVE-2012-2807

[Debian Bug Tracking System]

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

> tags 679280 + moreinfo
Bug #679280 [libxml2] CVE-2012-2807
Added tag(s) moreinfo.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
679280: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=679280
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#679283: [xml/sgml-pkgs] Bug#679283: CVE-2012-2825

[Aron Xu]

Will make an upload to fix the bug soon, and maybe we need to prepare
a fix for stable?



-- 
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#679272: bcfg2-server: unescaped shell command issues in the Trigger plugin

[Florian Weimer]

* Arto Jantunen:

>> In Debian (and all other distros I know of) the bcfg2 server runs as
>> root, so in practice this is a remote root hole (limited to attackers
>> who can connect to the bcfg2 server (protected by a password and/or an
>> ssl key)).
>
> .dsc and .debian.tar.gz for a fixed package are attached. I'll upload
> the fix to unstable next.

There's a spurious diff in the changelog:

 bcfg2 (1.0.1-3+squeeze1) stable-security; urgency=high
 
   * Apply patch from Chris St. Pierre to fix several problems with
-unescaped shell commands (Closes: #640028).
+unescaped shell commands

But the actual patch seems fine.  Please build without -sa and upload
to security-master.  Thanks!



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

Bug#676633: marked as done (python-opencv: should depend on python-numpy)

[Debian Bug Tracking System]

Your message dated Thu, 28 Jun 2012 04:20:55 +
with message-id 
and subject line Bug#676633: fixed in opencv 2.3.1-11
has caused the Debian Bug report #676633,
regarding python-opencv: should depend on python-numpy
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.)


-- 
676633: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=676633
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: python-opencv
Version: 2.3.1-10
Severity: normal

Dear Maintainer,

It seems that the dependency on "python-numpy" is missing.
I installed "python-opencv", but a sample gave me the following error:

>
> ImportError: numpy.core.multiarray failed to import
> Traceback (most recent call last):
> File "cv20squares.py", line 8, in 
> import cv2.cv as cv
> ImportError: numpy.core.multiarray failed to import
>

I solved the problem installing explicitly "python-numpy".

Regards,


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

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

Versions of packages python-opencv depends on:
ii libc6 2.13-32
ii libgcc1 1:4.7.0-8
ii libopencv-calib3d2.3 2.3.1-10
ii libopencv-core2.3 2.3.1-10
ii libopencv-features2d2.3 2.3.1-10
ii libopencv-flann2.3 2.3.1-10
ii libopencv-highgui2.3 2.3.1-10
ii libopencv-imgproc2.3 2.3.1-10
ii libopencv-legacy2.3 2.3.1-10
ii libopencv-ml2.3 2.3.1-10
ii libopencv-objdetect2.3 2.3.1-10
ii libopencv-video2.3 2.3.1-10
ii libpython2.7 2.7.3~rc2-2.1
ii libstdc++6 4.7.0-8
ii python 2.7.2-10
ii python-support 1.0.14

python-opencv recommends no packages.

python-opencv suggests no packages.

-- no debconf information





---
E-Mail ist da wo du bist! Jetzt mit freenetMail ganz bequem auch unterwegs 
E-Mails verschicken.
Am besten gleich informieren unter 
http://mail.freenet.de/mobile-email/index.html
--- End Message ---
--- Begin Message ---
Source: opencv
Source-Version: 2.3.1-11

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

libcv-dev_2.3.1-11_amd64.deb
  to main/o/opencv/libcv-dev_2.3.1-11_amd64.deb
libcv2.3_2.3.1-11_amd64.deb
  to main/o/opencv/libcv2.3_2.3.1-11_amd64.deb
libcvaux-dev_2.3.1-11_amd64.deb
  to main/o/opencv/libcvaux-dev_2.3.1-11_amd64.deb
libcvaux2.3_2.3.1-11_amd64.deb
  to main/o/opencv/libcvaux2.3_2.3.1-11_amd64.deb
libhighgui-dev_2.3.1-11_amd64.deb
  to main/o/opencv/libhighgui-dev_2.3.1-11_amd64.deb
libhighgui2.3_2.3.1-11_amd64.deb
  to main/o/opencv/libhighgui2.3_2.3.1-11_amd64.deb
libopencv-calib3d-dev_2.3.1-11_amd64.deb
  to main/o/opencv/libopencv-calib3d-dev_2.3.1-11_amd64.deb
libopencv-calib3d2.3_2.3.1-11_amd64.deb
  to main/o/opencv/libopencv-calib3d2.3_2.3.1-11_amd64.deb
libopencv-contrib-dev_2.3.1-11_amd64.deb
  to main/o/opencv/libopencv-contrib-dev_2.3.1-11_amd64.deb
libopencv-contrib2.3_2.3.1-11_amd64.deb
  to main/o/opencv/libopencv-contrib2.3_2.3.1-11_amd64.deb
libopencv-core-dev_2.3.1-11_amd64.deb
  to main/o/opencv/libopencv-core-dev_2.3.1-11_amd64.deb
libopencv-core2.3_2.3.1-11_amd64.deb
  to main/o/opencv/libopencv-core2.3_2.3.1-11_amd64.deb
libopencv-dev_2.3.1-11_amd64.deb
  to main/o/opencv/libopencv-dev_2.3.1-11_amd64.deb
libopencv-features2d-dev_2.3.1-11_amd64.deb
  to main/o/opencv/libopencv-features2d-dev_2.3.1-11_amd64.deb
libopencv-features2d2.3_2.3.1-11_amd64.deb
  to main/o/opencv/libopencv-features2d2.3_2.3.1-11_amd64.deb
libopencv-flann-dev_2.3.1-11_amd64.deb
  to main/o/opencv/libopencv-flann-dev_2.3.1-11_amd64.deb
libopencv-flann2.3_2.3.1-11_amd64.deb
  to main/o/opencv/libopencv-flann2.3_2.3.1-11_amd64.deb
libopencv-gpu-dev_2.3.1-11_amd64.deb
  to main/o/opencv/libopencv-gpu-dev_2.3.1-11_amd64.deb
libopencv-gpu2.3_2.3.1-11_amd64.deb
  to main/o/opencv/libopencv-gpu2.3_2.3.1-11_amd64.deb
libopencv-highgui-dev_2.3.1-11_amd64.deb
  to main/o/opencv/libopencv-highgui-dev_2.3.1-11_amd64.deb
libopencv-highgui2.3_2.3.1-11_amd64.deb
  to main/o/opencv/libopencv-highgui2.3_2.3.1-11_amd64.deb
libopencv-imgproc-dev_2.3.1-11_amd64.deb
  to main/o/opencv/libopencv-imgproc-dev_2.3.1-11_amd64.deb
libopencv-imgproc2.3_2.3.1-11_amd64.deb
  to main/o/opencv/libopencv-imgproc2.3_2.3.1-11_amd64.deb
libopencv-legacy-dev_2.3.1-11_amd64.deb
  to main/o/opencv/libopencv-legacy-dev_2.3.1-11_amd64.deb
libopencv-legacy2.3_2.3.1-11_amd64.deb
  to main/o/opencv/libopencv-legacy2.3_2.3.1-11_amd64.deb
libopencv-ml-dev_2.3.1-11_amd64.deb
  to main/o/opencv/libopencv-ml-

Bug#619717: marked as done (atris: bashisms in Makefile)

[Debian Bug Tracking System]

Your message dated Thu, 28 Jun 2012 03:32:13 +
with message-id 
and subject line Bug#619717: fixed in atris 1.0.7.dfsg.1-8
has caused the Debian Bug report #619717,
regarding atris: bashisms in Makefile
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.)


-- 
619717: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=619717
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: atris
Version: 1.0.7.dfsg.1-7.1
Severity: important
Justification: ftbfs with dash as /bin/sh
Tags: upstream patch

Hi,

atris uses brace expansions (as in {foo,bar,baz}) in its Makefile
but that is not valid POSIX shell syntax (and dash and busybox ash
don't support them).  How about this patch?

-- 8< --
Subject: atris: avoid nonportable {foo,bar} expansion in Makefile

Signed-off-by: Jonathan Nieder 
---
 debian/changelog   |8 +++
 debian/patches/06-atris-1.0.7.brace_expansion.diff |   48 
 2 files changed, 56 insertions(+), 0 deletions(-)
 create mode 100644 debian/patches/06-atris-1.0.7.brace_expansion.diff

diff --git a/debian/changelog b/debian/changelog
index 225cd23..71e3e70 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,3 +1,11 @@
+atris (1.0.7.dfsg.1-7.1.1) local; urgency=low
+
+  * [debian/patches/06-atris-1.0.7.brace_expansion.diff]:
+Makefile.am: avoid brace expansions (since dash does not
+support them).
+
+ -- Jonathan Nieder   Sat, 26 Mar 2011 07:25:35 -0500
+
 atris (1.0.7.dfsg.1-7.1) unstable; urgency=low
 
   * Non-maintainer upload.
diff --git a/debian/patches/06-atris-1.0.7.brace_expansion.diff 
b/debian/patches/06-atris-1.0.7.brace_expansion.diff
new file mode 100644
index 000..d72a368
--- /dev/null
+++ b/debian/patches/06-atris-1.0.7.brace_expansion.diff
@@ -0,0 +1,48 @@
+From: Jonathan Nieder 
+Date: Sat, 26 Mar 2011 07:22:24 -0500
+Subject: avoid unportable brace expansion
+
+dash, FreeBSD ash, and busybox ash do not support 'echo {hello,world}'
+expansion.
+
+Signed-off-by: Jonathan Nieder 
+---
+ Makefile.am |   10 ++
+ 1 files changed, 6 insertions(+), 4 deletions(-)
+
+diff --git Makefile.am Makefile.am
+index cc07f93..561186a 100644
+--- Makefile.am
 Makefile.am
+@@ -59,14 +59,14 @@ install_gamedata:
+   cp -rv graphics \
+styles \
+$(target)/
+-  -rm -f $(target)/{graphics,styles}/Makefile*
++  -rm -f $(target)/graphics/Makefile* $(target)/styles/Makefile*
+ 
+   sh mkinstalldirs / $(statedir)/
+   cp -rv Atris.Players \
+  Atris.Scores \
+$(statedir)/
+-  chmod 666 $(statedir)/Atris.{Players,Scores}
+-  chown .games $(statedir)/Atris.{Players,Scores}
++  chmod 666 $(statedir)/Atris.Players $(statedir)/Atris.Scores
++  chown .games $(statedir)/Atris.Players $(statedir)/Atris.Scores
+ 
+ install_gamedocs:
+   sh mkinstalldirs $(target)/
+@@ -90,7 +90,9 @@ zip: distdir $(PACKAGE)
+   mv $(PACKAGE) $(PACKAGE)-$(VERSION)/$(PACKAGE).exe
+   mv $(PACKAGE)-$(VERSION) $(PACKAGE)
+   cp ~/*.dll $(PACKAGE)
+-  rm $(PACKAGE)/config* $(PACKAGE)/*.[ch] $(PACKAGE)/Make* 
$(PACKAGE)/*.m4 $(PACKAGE)/{install-sh,missing,mkinstalldirs,autogen.sh} 
++  rm $(PACKAGE)/config* $(PACKAGE)/*.[ch] $(PACKAGE)/Make* $(PACKAGE)/*.m4
++  rm $(PACKAGE)/install-sh $(PACKAGE)/missing $(PACKAGE)/mkinstalldirs
++  rm $(PACKAGE)/autogen.sh
+   rm $(PACKAGE)/*.in -r $(PACKAGE)/.protos
+   zip -r9 $(PACKAGE)-$(VERSION)-win32.zip $(PACKAGE)
+   rm -r $(PACKAGE)
+-- 
+1.7.4.1
+
-- 
1.7.4.1



--- End Message ---
--- Begin Message ---
Source: atris
Source-Version: 1.0.7.dfsg.1-8

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

atris_1.0.7.dfsg.1-8.debian.tar.gz
  to main/a/atris/atris_1.0.7.dfsg.1-8.debian.tar.gz
atris_1.0.7.dfsg.1-8.dsc
  to main/a/atris/atris_1.0.7.dfsg.1-8.dsc
atris_1.0.7.dfsg.1-8_amd64.deb
  to main/a/atris/atris_1.0.7.dfsg.1-8_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 619...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Pascal Giard  (supplier of updated atris 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)


--

Bug#679350: Acknowledgement (brewtarget: crashes on start up - qsharedpointer)

[Brian DeRocher]

I applied this patch

http://brewtarget.svn.sourceforge.net/viewvc/brewtarget?view=revision&revision=794

--
Brian DeRocher
http://derocher.org/~brian




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

Bug#679350: brewtarget: crashes on start up - qsharedpointer

[Brian DeRocher]

Package: brewtarget
Version: 1.2.4-1
Severity: grave
Tags: patch
Justification: renders package unusable

Crashes every time on start up.  I applied a patch from upstream to simplify
checkForNewVersion().  Recompiled and it works.



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

Kernel: Linux 3.2.0-2-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 brewtarget depends on:
ii  libc6   2.13-33
ii  libgcc1 1:4.7.1-1
ii  libphonon4  4:4.6.0.0-2
ii  libqt4-dbus 4:4.8.2-1
ii  libqt4-network  4:4.8.2-1
ii  libqt4-svg  4:4.8.2-1
ii  libqt4-xml  4:4.8.2-1
ii  libqt4-xmlpatterns  4:4.8.2-1
ii  libqtcore4  4:4.8.2-1
ii  libqtgui4   4:4.8.2-1
ii  libqtwebkit42.2.1-4+b1
ii  libstdc++6  4.7.1-1
ii  phonon  4:4.6.0.0-2

brewtarget recommends no packages.

brewtarget suggests no packages.

-- no debconf information
--- a/src/brewtarget.cpp
+++ b/src/brewtarget.cpp
@@ -56,6 +56,7 @@
 #include "CelsiusTempUnitSystem.h"
 #include "ImperialVolumeUnitSystem.h"
 #include "BtSplashScreen.h"
+#include "MainWindow.h"
 
 QApplication* Brewtarget::app;
 MainWindow* Brewtarget::mainWindow;
@@ -127,7 +128,7 @@
return true;
 }
 
-void Brewtarget::checkForNewVersion()
+void Brewtarget::checkForNewVersion(MainWindow* mw)
 {
 
// Don't do anything if the checkVersion flag was set false
@@ -135,53 +136,10 @@
   return;
 
QNetworkAccessManager manager;
-   QEventLoop loop;
QUrl url("http://brewtarget.sourceforge.net/version";);
-   QSharedPointer reply = QSharedPointer(manager.get( QNetworkRequest(url) ));
-   QObject::connect( reply.data(), SIGNAL(finished()), &loop, SLOT(quit()));
+   QNetworkReply* reply = manager.get( QNetworkRequest(url) );
+   QObject::connect( reply, SIGNAL(finished()), mw, SLOT(finishCheckingVersion()));
 
-   loop.exec(); // Waits until the reply comes back.
-
-   QString remoteVersion(reply->readAll());
-
-   // If there is an error, just return.
-   if( reply->error() != QNetworkReply::NoError )
-  return;
-
-   // If the remote version is newer...
-   if( !remoteVersion.startsWith(VERSIONSTRING) )
-   {
-  // ...and the user wants to download the new version...
-  if( QMessageBox::information(mainWindow,
-   QObject::tr("New Version"),
-   QObject::tr("Version %1 is now available. Download it?").arg(remoteVersion),
-   QMessageBox::Yes | QMessageBox::No,
-   QMessageBox::Yes) == QMessageBox::Yes )
-  {
- // ...take them to the website.
- QDesktopServices::openUrl(QUrl("http://brewtarget.sourceforge.net";));
-  }
-  else // ... and the user does NOT want to download the new version...
-  {
- // ... and they want us to stop bothering them...
- if( QMessageBox::question(mainWindow,
-  QObject::tr("New Version"),
-  QObject::tr("Stop bothering you about new versions?"),
-  QMessageBox::Yes | QMessageBox::No,
-  QMessageBox::Yes) == QMessageBox::Yes)
- {
-// ... tell brewtarget to stop bothering the user about the new version.
-checkVersion = false;
- }
-  }
-   }
-   else // The current version is newest so...
-   {
-  // ...tell brewtarget to bother users about future new versions.
-  // This means that when a user downloads the new version, this
-  // variable will always get reset to true.
-  checkVersion = true;
-   }
 }
 
 bool Brewtarget::copyDataFiles(QString newPath)
@@ -544,7 +502,7 @@

splashScreen.finish(mainWindow);
 
-   checkForNewVersion();
+   checkForNewVersion(mainWindow);
 
ret = app->exec();
savePersistentOptions();
--- a/src/brewtarget.h
+++ b/src/brewtarget.h
@@ -137,7 +137,7 @@
//! Load translation files.
static void loadTranslations();
//! Checks for a newer version and prompts user to download.
-   static void checkForNewVersion();
+   static void checkForNewVersion(MainWindow* mw);

//! If this option is false, do not bother the user about new versions.
static bool checkVersion;

Bug#678787: marked as done (github-backup: FTBFS: build-dependency not installable: libghc-github-dev)

[Debian Bug Tracking System]

Your message dated Thu, 28 Jun 2012 02:52:14 +
with message-id 
and subject line Bug#678787: fixed in github-backup 1.20120627
has caused the Debian Bug report #678787,
regarding github-backup: FTBFS: build-dependency not installable: 
libghc-github-dev
to be marked as done.

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

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


-- 
678787: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=678787
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: github-backup
Version: 1.20120314
Severity: serious
Tags: wheezy sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20120624 qa-ftbfs
Justification: FTBFS on amd64

Hi,

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

Relevant part:
> ┌──┐
> │ Install github-backup build dependencies (apt-based resolver)   
>  │
> └──┘
> 
> Installing build dependencies
> Reading package lists...
> Building dependency tree...
> Reading state information...
> Some packages could not be installed. This may mean that you have
> requested an impossible situation or if you are using the unstable
> distribution that some required packages have not yet been created
> or been moved out of Incoming.
> The following information may help to resolve the situation:
> 
> The following packages have unmet dependencies:
>  sbuild-build-depends-github-backup-dummy : Depends: libghc-github-dev but it 
> is not going to be installed
> E: Unable to correct problems, you have held broken packages.
> apt-get failed.

The full build log is available from:
   
http://people.debian.org/~lucas/logs/2012/06/24/github-backup_1.20120314_unstable.log

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

About the archive rebuild: The rebuild was done on EC2 VM instances from
Amazon Web Services, using a clean, minimal and up-to-date chroot. Every
failed build was retried once to eliminate random failures.


--- End Message ---
--- Begin Message ---
Source: github-backup
Source-Version: 1.20120627

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

github-backup_1.20120627.dsc
  to main/g/github-backup/github-backup_1.20120627.dsc
github-backup_1.20120627.tar.gz
  to main/g/github-backup/github-backup_1.20120627.tar.gz
github-backup_1.20120627_i386.deb
  to main/g/github-backup/github-backup_1.20120627_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 678...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Joey Hess  (supplier of updated github-backup 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, 27 Jun 2012 22:21:01 -0400
Source: github-backup
Binary: github-backup
Architecture: source i386
Version: 1.20120627
Distribution: unstable
Urgency: low
Maintainer: Joey Hess 
Changed-By: Joey Hess 
Description: 
 github-backup - backs up data from GitHub
Closes: 678787
Changes: 
 github-backup (1.20120627) unstable; urgency=low
 .
   * Rebuilt with new haskell-github, that works with the new version
 of http-conduit in Debian. Closes: #678787
   * Various updates to internal git and utility libraries shared with 
git-annex.
Checksums-Sha1: 
 b5ce05f7f939eb2d31b751fde8c12c6047767138 1629 github-backup_1.20120627.dsc
 a2fbe721bcd5abc137af337aba9a75de00babd47 100907 github-backup_1.20120627.tar.gz
 f416c5775597d6d38ec8b2c9ce3a9d884d07a719 3221782 
github-backup_1.20120627_i386.deb
Checksums-Sha256: 
 8748d532d3ae438ec905c9abad50731f3e1624678aede05bfb5faff6c123be7d 1629 
github-backup_1.20120627.dsc
 bcda3bad36df9a01c2b4f7b5a59da740c1b2746e051d52d7caad7e1635bf4cf5 100907 
github-backup_1.20120627.tar.gz
 6be48a9877a96bb420a8dbacf0cfa1909b1e8b4724b56328679d84c4819855b8 3221782 
github-backup_1.20120627_i386.deb
Files: 
 68de45a5678950ef02172b57f07f24bc 1629 utils optional 
github-backup_1.20120627.dsc
 6a2dd8253dc95534631565aa934015d3 100907 utils optional 
github-backup_1.20120627.tar.gz
 8bbf807

Bug#665498: [shotwell - Bug #5468] (Open) Segmentation fault shortly after starting Shotwell everytime

[Clinton Rogers]

Good evening,

As I stated before, I'm one of the upstream developers working on
Shotwell, and, unfortunately, I'm unable to reproduce this.  Here's my
setup:

   - output of 'cat /proc/version'
   Linux version 3.2.0-2-686-pae (Debian 3.2.20-1)
(debian-ker...@lists.debian.org)
   (gcc version 4.6.3 (Debian 4.6.3-7) ) #1 SMP Mon Jun 11
18:27:04 UTC 2012[/pre]
   - 2048MB physical memory, 8192MB swap space
   - Shotwell contains ~11000 images and five videos; most of the
images have EXIF data
embedded

If anyone watching this bug knows more about how to trigger it, or can
get us a backtrace, please let us know.



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

Bug#676717: proposed sgml-base 1.16+nmu4 fixing #676717 and #678902

[Ian Jackson]

Helmut Grohne writes ("proposed sgml-base 1.16+nmu4 fixing #676717 and 
#678902"):
> Here is my next attempt to fixing #676717 and #678902.
> 
> I incorporated the parser Jakub Wilk proposed and tested it on a variety
> of catalog files. See the discussion on #676717 for why update-catalog
> is starting to parse catalog files.
> 
> In addition I added a Pre-Dependency on dpkg >= 1.16.4 to close #678902.
> Which highlights that the fixed dpkg trigger bug #675613, #676061,
> #676062, #676107, #676118, #676122 still shows up. As per policy section
> 7.2 I raise this Pre-Depends on -devel. 
> 
> So the attached NMU is to fix all the known issues that have come up as
> a result of fixing #88010. Comments welcome.

I'm not convinced that a Pre-Depends is the best answer here.  I think
a better answer would be for the new dpkg to activate all file
triggers when it first starts, and for sgml-base to simply use
Depends.

Ian.



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

Bug#679319: a work-around

[Ilguiz Latypov]

I worked around the crash by choosing Open JDK 1.7 to run davmail
compiled by Open JDK 1.6.

> sudo update-alternatives --config java

I believe it is possible that davmail could compile with Open JDK 1.7
and that its build system prevents higher version numbers by mistake.

I believe changing the Java runtime might hide the defect.  I did not
investigate the root cause of the defect.  Perhaps, the libraries shown
by the traces only receive a corruption from JDK.

--
-
This transmission (including any attachments) may contain confidential 
information, privileged material (including material protected by the 
solicitor-client or other applicable privileges), or constitute non-public 
information. Any use of this information by anyone other than the intended 
recipient is prohibited. If you have received this transmission in error, 
please immediately reply to the sender and delete this information from your 
system. Use, dissemination, distribution, or reproduction of this transmission 
by unintended recipients is not authorized and may be unlawful.



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

Bug#679307: marked as done (remctl: FTBFS in parallel mode: PHP module link error)

[Debian Bug Tracking System]

Your message dated Thu, 28 Jun 2012 00:08:06 +
with message-id 
and subject line Bug#679307: fixed in remctl 3.2-2
has caused the Debian Bug report #679307,
regarding remctl: FTBFS in parallel mode: PHP module link error
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.)


-- 
679307: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=679307
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: remctl
Version: 3.2-1
Severity: serious
Justification: fails to build from source (but built successfully in the past)

Hi, Russ.

Parallel builds of remctl are failing because the PHP module tries to
link against -lremctl before it becomes available:

  libtool: link: cc -shared  -fPIC -DPIC  .libs/php_remctl.o   
-L/.../remctl-3.2/client/.libs -lremctl  -O2 -Wl,-z -Wl,relro -Wl,-z -Wl,now 
-Wl,--as-needed   -Wl,-soname -Wl,remctl.so -o .libs/remctl.so
  /usr/bin/ld: cannot find -lremctl
  collect2: error: ld returned 1 exit status
  make[4]: *** [remctl.la] Error 1
  make[4]: Leaving directory `/.../remctl-3.2/php'
  make[3]: *** [php/modules/remctl.so] Error 2

Could you please either declare a suitable internal dependency or stop
passing --parallel to dh?

Thanks!


--- End Message ---
--- Begin Message ---
Source: remctl
Source-Version: 3.2-2

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

libnet-remctl-perl_3.2-2_i386.deb
  to main/r/remctl/libnet-remctl-perl_3.2-2_i386.deb
libremctl-dev_3.2-2_i386.deb
  to main/r/remctl/libremctl-dev_3.2-2_i386.deb
libremctl-ruby1.8_3.2-2_i386.deb
  to main/r/remctl/libremctl-ruby1.8_3.2-2_i386.deb
libremctl-ruby1.9.1_3.2-2_i386.deb
  to main/r/remctl/libremctl-ruby1.9.1_3.2-2_i386.deb
libremctl-ruby_3.2-2_i386.deb
  to main/r/remctl/libremctl-ruby_3.2-2_i386.deb
libremctl1_3.2-2_i386.deb
  to main/r/remctl/libremctl1_3.2-2_i386.deb
php5-remctl_3.2-2_i386.deb
  to main/r/remctl/php5-remctl_3.2-2_i386.deb
python-remctl_3.2-2_i386.deb
  to main/r/remctl/python-remctl_3.2-2_i386.deb
remctl-client_3.2-2_i386.deb
  to main/r/remctl/remctl-client_3.2-2_i386.deb
remctl-server_3.2-2_i386.deb
  to main/r/remctl/remctl-server_3.2-2_i386.deb
remctl_3.2-2.debian.tar.xz
  to main/r/remctl/remctl_3.2-2.debian.tar.xz
remctl_3.2-2.dsc
  to main/r/remctl/remctl_3.2-2.dsc
ruby-remctl_3.2-2_i386.deb
  to main/r/remctl/ruby-remctl_3.2-2_i386.deb



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

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

Debian distribution maintenance software
pp.
Russ Allbery  (supplier of updated remctl 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, 27 Jun 2012 16:32:57 -0700
Source: remctl
Binary: libremctl1 libremctl-dev remctl-client remctl-server libnet-remctl-perl 
php5-remctl python-remctl ruby-remctl libremctl-ruby libremctl-ruby1.8 
libremctl-ruby1.9.1
Architecture: source i386
Version: 3.2-2
Distribution: unstable
Urgency: low
Maintainer: Russ Allbery 
Changed-By: Russ Allbery 
Description: 
 libnet-remctl-perl - Perl client for Kerberos-authenticated command execution
 libremctl-dev - Development files for Kerberos-authenticated command execution
 libremctl-ruby - Ruby extension for remctl (transitional package)
 libremctl-ruby1.8 - Ruby 1.8 extension for remctl (transitional package)
 libremctl-ruby1.9.1 - Ruby 1.9.1 extension for remctl (transitional package)
 libremctl1 - Library for Kerberos-authenticated command execution
 php5-remctl - PECL module for Kerberos-authenticated command execution
 python-remctl - Python extension for Kerberos-authenticated command execution
 remctl-client - Client for Kerberos-authenticated command execution
 remctl-server - Server for Kerberos-authenticated command execution
 ruby-remctl - Ruby extension for Kerberos-authenticated command execution
Closes: 679307
Changes: 
 remctl (3.2-2) unstable; urgency=low
 .
   * Cherry-pick upstream fix to add proper dependencies on libremctl.la to
 the build rules for other language bindings.  This should fix
 occasional FTBFS problems with parallel builds.  Thanks, Aaron
 M. Ucko.  (Closes: #679307)
Checksums-Sha1: 
 e5d73a5d7d558f8743da3105558dac8d1043a299 2148 remctl_3.2-2

Bug#674380: marked as done (ruby-ronn: FTBFS: test failed)

[Debian Bug Tracking System]

Your message dated Thu, 28 Jun 2012 00:08:24 +
with message-id 
and subject line Bug#674380: fixed in ruby-ronn 0.7.3-2
has caused the Debian Bug report #674380,
regarding ruby-ronn: FTBFS: test failed
to be marked as done.

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

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


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

Hi,

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

Relevant part:
>  fakeroot debian/rules binary
> dh binary --buildsystem=ruby --with ruby
>dh_testroot -O--buildsystem=ruby
>dh_prep -O--buildsystem=ruby
>dh_installdirs -O--buildsystem=ruby
>dh_auto_install -O--buildsystem=ruby
>   Entering dh_ruby --install
> install -d /«PKGBUILDDIR»/debian/ruby-ronn/usr/bin
> install -D -m755 bin/ronn /«PKGBUILDDIR»/debian/ruby-ronn/usr/bin/ronn
> install -d /«PKGBUILDDIR»/debian/ruby-ronn/usr/lib/ruby/vendor_ruby
> install -D -m644 lib/ronn/template/80c.css 
> /«PKGBUILDDIR»/debian/ruby-ronn/usr/lib/ruby/vendor_ruby/ronn/template/80c.css
> install -D -m644 lib/ronn/template/screen.css 
> /«PKGBUILDDIR»/debian/ruby-ronn/usr/lib/ruby/vendor_ruby/ronn/template/screen.css
> install -D -m644 lib/ronn/template/darktoc.css 
> /«PKGBUILDDIR»/debian/ruby-ronn/usr/lib/ruby/vendor_ruby/ronn/template/darktoc.css
> install -D -m644 lib/ronn/template/default.html 
> /«PKGBUILDDIR»/debian/ruby-ronn/usr/lib/ruby/vendor_ruby/ronn/template/default.html
> install -D -m644 lib/ronn/template/man.css 
> /«PKGBUILDDIR»/debian/ruby-ronn/usr/lib/ruby/vendor_ruby/ronn/template/man.css
> install -D -m644 lib/ronn/template/toc.css 
> /«PKGBUILDDIR»/debian/ruby-ronn/usr/lib/ruby/vendor_ruby/ronn/template/toc.css
> install -D -m644 lib/ronn/template/dark.css 
> /«PKGBUILDDIR»/debian/ruby-ronn/usr/lib/ruby/vendor_ruby/ronn/template/dark.css
> install -D -m644 lib/ronn/template/print.css 
> /«PKGBUILDDIR»/debian/ruby-ronn/usr/lib/ruby/vendor_ruby/ronn/template/print.css
> install -D -m644 lib/ronn/roff.rb 
> /«PKGBUILDDIR»/debian/ruby-ronn/usr/lib/ruby/vendor_ruby/ronn/roff.rb
> install -D -m644 lib/ronn/server.rb 
> /«PKGBUILDDIR»/debian/ruby-ronn/usr/lib/ruby/vendor_ruby/ronn/server.rb
> install -D -m644 lib/ronn/template.rb 
> /«PKGBUILDDIR»/debian/ruby-ronn/usr/lib/ruby/vendor_ruby/ronn/template.rb
> install -D -m644 lib/ronn/document.rb 
> /«PKGBUILDDIR»/debian/ruby-ronn/usr/lib/ruby/vendor_ruby/ronn/document.rb
> install -D -m644 lib/ronn/utils.rb 
> /«PKGBUILDDIR»/debian/ruby-ronn/usr/lib/ruby/vendor_ruby/ronn/utils.rb
> install -D -m644 lib/ronn/index.rb 
> /«PKGBUILDDIR»/debian/ruby-ronn/usr/lib/ruby/vendor_ruby/ronn/index.rb
> install -D -m644 lib/ronn.rb 
> /«PKGBUILDDIR»/debian/ruby-ronn/usr/lib/ruby/vendor_ruby/ronn.rb
> Rewriting shebang line of /«PKGBUILDDIR»/debian/ruby-ronn/usr/bin/ronn
> /usr/bin/ruby1.8 -I/usr/lib/ruby/vendor_ruby 
> /usr/lib/ruby/vendor_ruby/gem2deb/test_runner.rb
> Loaded suite debian/ruby-tests
> Started
> ...F...F
> Finished in 2.933736 seconds.
> 
>   1) Failure:
> test_markdown_syntax_HTML(RonnTest) [./test/test_ronn.rb:83]:
> --- ./test/markdown_syntax.html   2011-10-05 21:01:51.0 +
> +++ ./test/markdown_syntax.html.wrong 2012-05-23 20:59:14.243125256 +
> @@ -153,7 +153,7 @@
>  AT&T
>  
>  
> -Similarly, because Markdown supports  data-bare-link="true">inline HTML, if you use
> +Similarly, because Markdown supports  href="#html">inline HTML, if you use
>  angle brackets as delimiters for HTML tags, Markdown will treat them as
>  such. But if you write:
>  
> @@ -191,7 +191,7 @@
>  
>  Yes, this takes a tad more effort to create a 
, 
> but a simplistic
>  "every line break is a 
" rule wouldn't work for 
> Markdown.
> -Markdown's email-style  data-bare-link="true">blockquoting and multi-paragraph  data-bare-link="true">list items
> +Markdown's email-style  href="#blockquote">blockquoting and multi-paragraph  data-bare-link="true" href="#list">list items
>  work best -- and look better -- when you format them with hard breaks.
>  
>  Headers
> @@ -952,6 +952,6 @@
>  SEE ALSO
>  
>  ronn(5)
> -http://daringfireball.net/projects/markdown/"; 
> data-bare-link="true">http://daringfireball.net/projects/markdown/
> + href="http://daringfireball.net/projects/markdown/";>http://daringfireball.net/projects/markdown/
>  
>  
> .
> 
>   

Bug#662103: marked as done (phonon-backend-vlc: Pausing and resuming in Amarok changes volume to 100%)

[Debian Bug Tracking System]

Your message dated Thu, 28 Jun 2012 00:07:47 +
with message-id 
and subject line Bug#662103: fixed in phonon-backend-vlc 0.5.0+14.g382da0d-1
has caused the Debian Bug report #662103,
regarding phonon-backend-vlc: Pausing and resuming in Amarok changes volume to 
100%
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.)


-- 
662103: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=662103
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: phonon-backend-vlc
Version: 0.5.0-1
Severity: normal

When pausing and then resuming playback in Amarok (2.5.0-1) the volume of the
Amarok stream is always changed upon resume to 100%. Playback is via
PulseAudio.

I do not experience this problem with phonon-backend-gstreamer



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

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

Versions of packages phonon-backend-vlc depends on:
ii  libc6   2.13-27
ii  libphonon4  4:4.6.0.0-1
ii  libqtcore4  4:4.7.4-2
ii  libqtgui4   4:4.7.4-2
ii  libstdc++6  4.6.3-1
ii  libvlc5 2.0.0-6
ii  vlc-nox 2.0.0-6

Versions of packages phonon-backend-vlc recommends:
ii  vlc  2.0.0-6

phonon-backend-vlc suggests no packages.

-- no debconf information


--- End Message ---
--- Begin Message ---
Source: phonon-backend-vlc
Source-Version: 0.5.0+14.g382da0d-1

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

phonon-backend-vlc-dbg_0.5.0+14.g382da0d-1_amd64.deb
  to 
main/p/phonon-backend-vlc/phonon-backend-vlc-dbg_0.5.0+14.g382da0d-1_amd64.deb
phonon-backend-vlc_0.5.0+14.g382da0d-1.debian.tar.gz
  to 
main/p/phonon-backend-vlc/phonon-backend-vlc_0.5.0+14.g382da0d-1.debian.tar.gz
phonon-backend-vlc_0.5.0+14.g382da0d-1.dsc
  to main/p/phonon-backend-vlc/phonon-backend-vlc_0.5.0+14.g382da0d-1.dsc
phonon-backend-vlc_0.5.0+14.g382da0d-1_amd64.deb
  to main/p/phonon-backend-vlc/phonon-backend-vlc_0.5.0+14.g382da0d-1_amd64.deb
phonon-backend-vlc_0.5.0+14.g382da0d.orig.tar.xz
  to main/p/phonon-backend-vlc/phonon-backend-vlc_0.5.0+14.g382da0d.orig.tar.xz



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

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

Debian distribution maintenance software
pp.
Modestas Vainius  (supplier of updated phonon-backend-vlc 
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, 28 Jun 2012 02:30:31 +0300
Source: phonon-backend-vlc
Binary: phonon-backend-vlc phonon-backend-vlc-dbg
Architecture: source amd64
Version: 0.5.0+14.g382da0d-1
Distribution: experimental
Urgency: low
Maintainer: Debian Qt/KDE Maintainers 
Changed-By: Modestas Vainius 
Description: 
 phonon-backend-vlc - Phonon VLC backend
 phonon-backend-vlc-dbg - Phonon VLC backend debugging symbols
Closes: 662103
Changes: 
 phonon-backend-vlc (0.5.0+14.g382da0d-1) experimental; urgency=low
 .
   * New upstream snapshot from 0.5 branch (2012-06-18 03:38 am):
 - fixes a problem with volume going up to 100% upon resume. It only
   affected PulseAudio users. (Closes: #662103)
   * Bump Standards-Version to 3.9.3: no changes needed.
   * Add debian/watch file.
Checksums-Sha1: 
 775eb936cf40204a1fdcb01d810b25dce419677d 1778 
phonon-backend-vlc_0.5.0+14.g382da0d-1.dsc
 497000765b33841e90c380c137d6b1c9e7a046b9 51900 
phonon-backend-vlc_0.5.0+14.g382da0d.orig.tar.xz
 92df2e5e8d08bdad41f567398b3fa89aa42a1601 4249 
phonon-backend-vlc_0.5.0+14.g382da0d-1.debian.tar.gz
 b5ca51e3283b93354a2cb5289d08ec6d240f6778 93926 
phonon-backend-vlc_0.5.0+14.g382da0d-1_amd64.deb
 a2590e06129dde97e2520b21c5c86704d11c27c1 1223552 
phonon-backend-vlc-dbg_0.5.0+14.g382da0d-1_amd64.deb
Checksums-Sha256: 
 0c9f15741e6a1c449ba3e29314fa746d041b49952a8096ec635b1223565d5d8b 1778 
phonon-backend-vlc_0.5.0+14.g382da0d-1.dsc
 4c07c6bd7ac8a97e7925c6b3fdd55a6341e2df495fbd4e435420f8d1737ca9fd 51900 
phonon-backend-vlc_0.5.0+14.g382da0d.orig.tar.xz
 b682a44d7805a1eb569e752cb2b715be6b34f4baf4951790f9c0ed0fe2f

Bug#679319: a work-around

[Ilguiz Latypov]

On 27/06/12 07:57 PM, Ilguiz Latypov wrote:
> I worked around the crash by choosing Open JDK 1.7 to run davmail
> compiled by Open JDK 1.6.
>
>> sudo update-alternatives --config java

After reporting my work-around I followed advice of the davmail author
and disabled the use of system proxy settings in the davmail setup
dialog.  I then switched the default Java runtime to Open JDK 1.6 and
found that davmail could start without a crash.

--

-
This transmission (including any attachments) may contain confidential 
information, privileged material (including material protected by the 
solicitor-client or other applicable privileges), or constitute non-public 
information. Any use of this information by anyone other than the intended 
recipient is prohibited. If you have received this transmission in error, 
please immediately reply to the sender and delete this information from your 
system. Use, dissemination, distribution, or reproduction of this transmission 
by unintended recipients is not authorized and may be unlawful.



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

Bug#679307: remctl: FTBFS in parallel mode: PHP module link error

[Russ Allbery]

"Aaron M. Ucko"  writes:

> Parallel builds of remctl are failing because the PHP module tries to
> link against -lremctl before it becomes available:

>   libtool: link: cc -shared  -fPIC -DPIC  .libs/php_remctl.o   
> -L/.../remctl-3.2/client/.libs -lremctl  -O2 -Wl,-z -Wl,relro -Wl,-z -Wl,now 
> -Wl,--as-needed   -Wl,-soname -Wl,remctl.so -o .libs/remctl.so
>   /usr/bin/ld: cannot find -lremctl
>   collect2: error: ld returned 1 exit status
>   make[4]: *** [remctl.la] Error 1
>   make[4]: Leaving directory `/.../remctl-3.2/php'
>   make[3]: *** [php/modules/remctl.so] Error 2

> Could you please either declare a suitable internal dependency or stop
> passing --parallel to dh?

sudo strips out environment variables.  Such as DEB_BUILD_OPTIONS.  Which
would make my testing of parallel build rules via git-buildpackage kind of
useless, in the sense that I didn't test them at all.  Sigh.  You would
think I would know this.

Thanks, Aaron!  I'm testing an updated package now and it should be
uploaded in a few moments.

-- 
Russ Allbery (r...@debian.org)   



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

Bug#665498: shotwell: Segmentation fault shortly after starting Shotwell everytime

[Clinton Rogers]

Hi,

My name is Clint, and I'm one of the upstream developers for Shotwell.
 I wanted to let everyone watching this issue know that we're treating
it with the utmost care and urgency.

Unfortunately, we've never been able to reproduce it on other distros,
and as such, haven't yet been able to address it.  To that end, I'm
setting up a 'squeeze' testing machine as I write this, but if anyone
affected by this issue can obtain a backtrace, that would hellp us
greatly, too.

Based upon the way the initial report is worded, it sounds like
Shotwell ran correctly at one point for those affected, then suddenly
began crashing.  Is this correct?



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

Bug#677801: AttributeError: 'module' object has no attribute

[Carl Chenet]

> It's not a problem of python-pip.
> For new venvs it's a problem of python-virtualenv that contains an
> embedded source of pip 1.1 in /usr/share/python-virtualenv/pip-1.1.tar.gz
> For old venvs I'm afraid there can be no proper solution aside from
> installing the new pip version (unreleased yet) with easy_install.

I confirm, a bug should be opened on python-virtualenv package. This
issue has been solved by python-pip 1.1-3 for the Debian python-pip package.

For the Debian python-virtualenv package, a possible solution could be
to patch this tarball either with the patch provided by the upstream [1]
either with the patch used for the python-pip Debian package [2].

[1]: https://github.com/pypa/pip/issues/552
[2]:
http://anonscm.debian.org/viewvc/python-modules/packages/python-pip/trunk/debian/patches/test_urlparse_uses_fragment.patch?revision=22249&view=markup

Bye,
Carl Chenet



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

Bug#676473: marked as done (sysv-rc: give more information on left-behind init.d script while trying to migrate)

[Debian Bug Tracking System]

Your message dated Wed, 27 Jun 2012 22:50:24 +
with message-id 
and subject line Bug#678231: fixed in sysvinit 2.88dsf-28
has caused the Debian Bug report #678231,
regarding sysv-rc: give more information on left-behind init.d script while 
trying to migrate
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.)


-- 
678231: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=678231
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: sysv-rc
Version: 2.88dsf-26
Severity: wishlist
Tags: patch

Dear Maintainer,

my system has been running debian for about ten years now.  Once in a time,
I try to resolve a few issues preventing my system to be migrated to
dependency based boot.  Today, I looked at the suggestion
  dpkg --purge initscripts initscripts initscripts lm-sensors
which is not something I wanted to do.  Package initscripts has 24
non-obsolete and three obsolete init.d scripts.  Trying to figure out
which script to delete manually,  it would be really helpful if
sysv-rc.postinst reported the exact filename.  I used the attached
patch to get this behaviour.  Please apply if you consider it reasonable.

Regards
Stephan


diff --git a/debian/sysv-rc.postinst b/debian/sysv-rc.postinst
index 757c85e..48fdbba 100644
--- a/debian/sysv-rc.postinst
+++ b/debian/sysv-rc.postinst
@@ -85,7 +85,7 @@ is_unsafe_to_activate() {
 for initscript in $obsolete_initscripts; do
 if [ -e "$initscript" ]; then
 retval=0
-add_problematic "package $package left obsolete init.d 
script behind"
+add_problematic "package $package left obsolete init.d 
script $initscript behind"
 add_suggestion "$package"
 fi
 done

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

Kernel: Linux 3.3.0-trunk-amd64 (SMP w/8 CPU cores)
Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968)
Shell: /bin/sh linked to /bin/dash

Versions of packages sysv-rc depends on:
ii  debconf [debconf-2.0]  1.5.43
ii  insserv1.14.0-3
ii  sysvinit-utils 2.88dsf-26

Versions of packages sysv-rc recommends:
ii  lsb-base  4.1+Debian6

Versions of packages sysv-rc suggests:
ii  bum   
ii  sysv-rc-conf  0.99-7

-- debconf information:
* sysv-rc/unable-to-convert:
  sysv-rc/convert-legacy: true


--- End Message ---
--- Begin Message ---
Source: sysvinit
Source-Version: 2.88dsf-28

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

bootlogd_2.88dsf-28_amd64.deb
  to main/s/sysvinit/bootlogd_2.88dsf-28_amd64.deb
initscripts_2.88dsf-28_amd64.deb
  to main/s/sysvinit/initscripts_2.88dsf-28_amd64.deb
sysv-rc_2.88dsf-28_all.deb
  to main/s/sysvinit/sysv-rc_2.88dsf-28_all.deb
sysvinit-utils_2.88dsf-28_amd64.deb
  to main/s/sysvinit/sysvinit-utils_2.88dsf-28_amd64.deb
sysvinit_2.88dsf-28.debian.tar.gz
  to main/s/sysvinit/sysvinit_2.88dsf-28.debian.tar.gz
sysvinit_2.88dsf-28.dsc
  to main/s/sysvinit/sysvinit_2.88dsf-28.dsc
sysvinit_2.88dsf-28_amd64.deb
  to main/s/sysvinit/sysvinit_2.88dsf-28_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 678...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Roger Leigh  (supplier of updated sysvinit package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Wed, 27 Jun 2012 23:00:45 +0100
Source: sysvinit
Binary: sysvinit sysvinit-utils sysv-rc initscripts bootlogd
Architecture: source amd64 all
Version: 2.88dsf-28
Distribution: unstable
Urgency: low
Maintainer: Debian sysvinit maintainers 

Changed-By: Roger Leigh 
Description: 
 bootlogd   - daemon to log boot messages
 initscripts - scripts for initializing and shutting down the system
 sysv-rc- System-V-like runlevel change mechanism
 sysvinit   - System-V-like init utilities
 sysvinit-utils - System-V-like utilities
Closes: 625463 637390 668650 669162 671124 674178 676463 676473 676721 676725 
676773 676791 676814 676893 676910 677011 677333 677590 677753 

Bug#676520: marked as done ([sysv-rc] System unsuitable for dep-based boot cannot configure)

[Debian Bug Tracking System]

Your message dated Wed, 27 Jun 2012 22:50:24 +
with message-id 
and subject line Bug#678231: fixed in sysvinit 2.88dsf-28
has caused the Debian Bug report #678231,
regarding [sysv-rc] System unsuitable for dep-based boot cannot configure
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.)


-- 
678231: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=678231
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: sysv-rc
Version: 2.88dsf-26
Severity: grave

--- Please enter the report below this line. ---
I have an older init scripted system which will not configure for dep-based 
boot due to man missing lsb tags and overrides (what can I do about this?).

Additonally, as per bug #676463, there are numerous complaints about init 
scripts for removed applications and some that are not removed!

In the past, sysv-rc would configure for the old boot correctly and upgrades 
went merrily on their way. Now, it gives an error return.

Sysv-rc is left unconfigured and NO other apt operations are possible!

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

Debian Release: wheezy/sid
  500 unstableftp.us.debian.org 
  500 testing ftp.us.debian.org 
  100 experimental-snapshots qt-kde.debian.net 
1 experimentalftp.us.debian.org 

--- Package information. ---
Depends   (Version) | Installed
===-+-=
debconf   (>= 0.5)  | 1.5.43
 OR debconf-2.0 | 
sysvinit-utils (>= 2.86.ds1-62) | 2.88dsf-26
insserv  (>> 1.12.0-10) | 1.14.0-3


Recommends   (Version) | Installed
==-+-
lsb-base   (>= 3.2-14) | 4.1+Debian6


Suggests  (Version) | Installed
===-+-===
sysv-rc-conf| 
bum | 






--- End Message ---
--- Begin Message ---
Source: sysvinit
Source-Version: 2.88dsf-28

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

bootlogd_2.88dsf-28_amd64.deb
  to main/s/sysvinit/bootlogd_2.88dsf-28_amd64.deb
initscripts_2.88dsf-28_amd64.deb
  to main/s/sysvinit/initscripts_2.88dsf-28_amd64.deb
sysv-rc_2.88dsf-28_all.deb
  to main/s/sysvinit/sysv-rc_2.88dsf-28_all.deb
sysvinit-utils_2.88dsf-28_amd64.deb
  to main/s/sysvinit/sysvinit-utils_2.88dsf-28_amd64.deb
sysvinit_2.88dsf-28.debian.tar.gz
  to main/s/sysvinit/sysvinit_2.88dsf-28.debian.tar.gz
sysvinit_2.88dsf-28.dsc
  to main/s/sysvinit/sysvinit_2.88dsf-28.dsc
sysvinit_2.88dsf-28_amd64.deb
  to main/s/sysvinit/sysvinit_2.88dsf-28_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 678...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Roger Leigh  (supplier of updated sysvinit package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Wed, 27 Jun 2012 23:00:45 +0100
Source: sysvinit
Binary: sysvinit sysvinit-utils sysv-rc initscripts bootlogd
Architecture: source amd64 all
Version: 2.88dsf-28
Distribution: unstable
Urgency: low
Maintainer: Debian sysvinit maintainers 

Changed-By: Roger Leigh 
Description: 
 bootlogd   - daemon to log boot messages
 initscripts - scripts for initializing and shutting down the system
 sysv-rc- System-V-like runlevel change mechanism
 sysvinit   - System-V-like init utilities
 sysvinit-utils - System-V-like utilities
Closes: 625463 637390 668650 669162 671124 674178 676463 676473 676721 676725 
676773 676791 676814 676893 676910 677011 677333 677590 677753 677904 678231 
678627 678680 678878
Changes: 
 sysvinit (2.88dsf-28) unstable; urgency=low
 .
   [ Steve Langasek ]
   * debian/patches/upstart_support.patch: add missing
 startpar-upstart-inject manpage.
 .
   [ Roger Leigh ]
   * Updated debconf translations:
 - ca.  Thanks to Innocent De Marchi.  Closes: #677904.
 - cs.  Thanks to Miroslav Kure.  Closes: #678680.
 - da.  Thanks to Joe Hansen.  Closes: #676893.
 - de.  Thanks to Chris Leick.  Closes: #677753.
 - fr.  Thanks to Steve Petruzzello.  Closes: #677590.
 - gl.  Thanks to Jorge Barreiro.  Clos

Bug#676463: marked as done (sysv-rc: complains incorrectly(?) about obsolete init.d scripts for fuse and others)

[Debian Bug Tracking System]

Your message dated Wed, 27 Jun 2012 22:50:24 +
with message-id 
and subject line Bug#678231: fixed in sysvinit 2.88dsf-28
has caused the Debian Bug report #678231,
regarding sysv-rc: complains incorrectly(?) about obsolete init.d scripts for 
fuse and others
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.)


-- 
678231: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=678231
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: sysv-rc
Version: 2.88dsf-26
Severity: important

Dear Debian folks,


in contrast to earlier versions, with this version installation of
`sysv-rc` fails when migration to dependency based boot fails.
Additionally it complains about obsolete init.d scripts of packages
which were never a problem before and whose init.d scripts do not seem
to be obsolete.

sysv-rc (2.88dsf-26) wird eingerichtet ...
info: Checking if it is safe to convert to dependency based boot.

error: Unable to migrate to dependency based boot sequencing.
error: Problems detected: package fuse left obsolete init.d script 
behind, package initscripts left obsolete init.d script behind, package 
initscripts left obsolete init.d script behind, package initscripts left 
obsolete init.d script behind, package libchipcard-tools left obsolete init.d 
script behind, package smartmontools left obsolete init.d script behind,  , 
package gdm removed but not purged

If this is due to the presence of unpurged obsolete initscripts,
it is suggested that the following is run to remove them:
  dpkg --purge fuse initscripts initscripts initscripts 
libchipcard-tools smartmontools

See http://wiki.debian.org/LSBInitScripts/DependencyBasedBoot for
more information about dependency based boot sequencing. To
reattempt the migration process run 'dpkg --configure sysv-rc'.

dpkg: Fehler beim Bearbeiten von sysv-rc (--configure):
 Unterprozess installiertes post-installation-Skript gab den Fehlerwert 
1 zurück
Fehler traten auf beim Bearbeiten von:
 sysv-rc

This is an example for the package `fuse`.

$ dpkg -S /etc/init.d/fuse 
fuse: /etc/init.d/fuse

Also the other init.d scripts are packaged properly.


Thanks,

Paul

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

Kernel: Linux 3.2.0-2-686-pae (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/bash

Versions of packages sysv-rc depends on:
ii  debconf [debconf-2.0]  1.5.43
ii  insserv1.14.0-3
ii  sysvinit-utils 2.88dsf-26

Versions of packages sysv-rc recommends:
ii  lsb-base  4.1+Debian6

Versions of packages sysv-rc suggests:
pn  bum   
pn  sysv-rc-conf  

-- debconf information:
* sysv-rc/unable-to-convert:
  sysv-rc/convert-legacy: true


signature.asc
Description: This is a digitally signed message part
--- End Message ---
--- Begin Message ---
Source: sysvinit
Source-Version: 2.88dsf-28

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

bootlogd_2.88dsf-28_amd64.deb
  to main/s/sysvinit/bootlogd_2.88dsf-28_amd64.deb
initscripts_2.88dsf-28_amd64.deb
  to main/s/sysvinit/initscripts_2.88dsf-28_amd64.deb
sysv-rc_2.88dsf-28_all.deb
  to main/s/sysvinit/sysv-rc_2.88dsf-28_all.deb
sysvinit-utils_2.88dsf-28_amd64.deb
  to main/s/sysvinit/sysvinit-utils_2.88dsf-28_amd64.deb
sysvinit_2.88dsf-28.debian.tar.gz
  to main/s/sysvinit/sysvinit_2.88dsf-28.debian.tar.gz
sysvinit_2.88dsf-28.dsc
  to main/s/sysvinit/sysvinit_2.88dsf-28.dsc
sysvinit_2.88dsf-28_amd64.deb
  to main/s/sysvinit/sysvinit_2.88dsf-28_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 678...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Roger Leigh  (supplier of updated sysvinit package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Wed, 27 Jun 2012 23:00:45 +0100
Source: sysvinit
Binary: sysvinit sysvinit-utils sysv-rc initscript

Bug#678231: marked as done (sysv-rc: please log filename of "obsolete init.d script")

[Debian Bug Tracking System]

Your message dated Wed, 27 Jun 2012 22:50:24 +
with message-id 
and subject line Bug#678231: fixed in sysvinit 2.88dsf-28
has caused the Debian Bug report #678231,
regarding sysv-rc: please log filename of "obsolete init.d script"
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.)


-- 
678231: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=678231
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: sysv-rc
Version: 2.88dsf-26
Severity: normal

Having procrastinated on fixing sysv-rc's complaints about being unable to
switch to a dependency-based boot sequence for months, and finally looking
into it now that we're dependency-only and I can't install or upgrade
anything until I fix it, I finally dug in and started purging packages that
sysv-rc.postinst tells me were leaving obsolete init.d scripts lying around.

But, having spent several hours removing one thing after another and being
unable to appease the script, it finally gave me the following dubious advice:

  % sudo dpkg --configure sysv-rc
  Setting up sysv-rc (2.88dsf-26) ...
  info: Checking if it is safe to convert to dependency based boot.
  
  error: Unable to migrate to dependency based boot sequencing.
  error: Problems detected: package initscripts left obsolete init.d script 
behind, package initscripts left obsolete init.d script behind, package 
initscripts left obsolete init.d script behind
  
  If this is due to the presence of unpurged obsolete initscripts,
  it is suggested that the following is run to remove them:
dpkg --purge initscripts initscripts initscripts

Not wanting to completely break my system by removing 'initscripts', I wanted
to find out exactly which obsolete scripts were causing the problem. To that
end, I finally applied the following patch to sysv-rc.postinst, which I
submit might be nice to include upstream:

--- /var/lib/dpkg/info/sysv-rc.postinst 2012-06-06 15:26:49.0 -0700
+++ /usr/home/warner/sysv-rc.postinst   2012-06-19 21:57:44.0 -0700
@@ -85,7 +85,7 @@
 for initscript in $obsolete_initscripts; do
 if [ -e "$initscript" ]; then
 retval=0
-add_problematic "package $package left obsolete init.d 
script behind"
+add_problematic "package $package left obsolete init.d 
script $initscript behind"
 add_suggestion "$package"
 fi
 done

That pinpointed the trouble to three files: bootlogd, stop-bootlogd, and
stop-bootlogd-single. I still don't understand what problem they're causing,
but I've got more information to go on now.

cheers,
 -Brian


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

Kernel: Linux 2.6.37-1-686 (SMP w/1 CPU core)
Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968)
Shell: /bin/sh linked to /bin/dash

Versions of packages sysv-rc depends on:
ii  debconf [debconf-2.0]  1.5.43
ii  insserv1.14.0-3
ii  sysvinit-utils 2.88dsf-26

Versions of packages sysv-rc recommends:
ii  lsb-base  4.1+Debian6

Versions of packages sysv-rc suggests:
pn  bum   
pn  sysv-rc-conf  

-- debconf information:
* sysv-rc/unable-to-convert:
  sysv-rc/convert-legacy: true


--- End Message ---
--- Begin Message ---
Source: sysvinit
Source-Version: 2.88dsf-28

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

bootlogd_2.88dsf-28_amd64.deb
  to main/s/sysvinit/bootlogd_2.88dsf-28_amd64.deb
initscripts_2.88dsf-28_amd64.deb
  to main/s/sysvinit/initscripts_2.88dsf-28_amd64.deb
sysv-rc_2.88dsf-28_all.deb
  to main/s/sysvinit/sysv-rc_2.88dsf-28_all.deb
sysvinit-utils_2.88dsf-28_amd64.deb
  to main/s/sysvinit/sysvinit-utils_2.88dsf-28_amd64.deb
sysvinit_2.88dsf-28.debian.tar.gz
  to main/s/sysvinit/sysvinit_2.88dsf-28.debian.tar.gz
sysvinit_2.88dsf-28.dsc
  to main/s/sysvinit/sysvinit_2.88dsf-28.dsc
sysvinit_2.88dsf-28_amd64.deb
  to main/s/sysvinit/sysvinit_2.88dsf-28_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 678...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Roger Leigh  (supplier of updated sysvinit package)

(This message was generated automatically at their request; if you
believe that there is a problem with i

Bug#676520: marked as done ([sysv-rc] System unsuitable for dep-based boot cannot configure)

[Debian Bug Tracking System]

Your message dated Wed, 27 Jun 2012 22:50:24 +
with message-id 
and subject line Bug#676473: fixed in sysvinit 2.88dsf-28
has caused the Debian Bug report #676473,
regarding [sysv-rc] System unsuitable for dep-based boot cannot configure
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.)


-- 
676473: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=676473
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: sysv-rc
Version: 2.88dsf-26
Severity: grave

--- Please enter the report below this line. ---
I have an older init scripted system which will not configure for dep-based 
boot due to man missing lsb tags and overrides (what can I do about this?).

Additonally, as per bug #676463, there are numerous complaints about init 
scripts for removed applications and some that are not removed!

In the past, sysv-rc would configure for the old boot correctly and upgrades 
went merrily on their way. Now, it gives an error return.

Sysv-rc is left unconfigured and NO other apt operations are possible!

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

Debian Release: wheezy/sid
  500 unstableftp.us.debian.org 
  500 testing ftp.us.debian.org 
  100 experimental-snapshots qt-kde.debian.net 
1 experimentalftp.us.debian.org 

--- Package information. ---
Depends   (Version) | Installed
===-+-=
debconf   (>= 0.5)  | 1.5.43
 OR debconf-2.0 | 
sysvinit-utils (>= 2.86.ds1-62) | 2.88dsf-26
insserv  (>> 1.12.0-10) | 1.14.0-3


Recommends   (Version) | Installed
==-+-
lsb-base   (>= 3.2-14) | 4.1+Debian6


Suggests  (Version) | Installed
===-+-===
sysv-rc-conf| 
bum | 






--- End Message ---
--- Begin Message ---
Source: sysvinit
Source-Version: 2.88dsf-28

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

bootlogd_2.88dsf-28_amd64.deb
  to main/s/sysvinit/bootlogd_2.88dsf-28_amd64.deb
initscripts_2.88dsf-28_amd64.deb
  to main/s/sysvinit/initscripts_2.88dsf-28_amd64.deb
sysv-rc_2.88dsf-28_all.deb
  to main/s/sysvinit/sysv-rc_2.88dsf-28_all.deb
sysvinit-utils_2.88dsf-28_amd64.deb
  to main/s/sysvinit/sysvinit-utils_2.88dsf-28_amd64.deb
sysvinit_2.88dsf-28.debian.tar.gz
  to main/s/sysvinit/sysvinit_2.88dsf-28.debian.tar.gz
sysvinit_2.88dsf-28.dsc
  to main/s/sysvinit/sysvinit_2.88dsf-28.dsc
sysvinit_2.88dsf-28_amd64.deb
  to main/s/sysvinit/sysvinit_2.88dsf-28_amd64.deb



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

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

Debian distribution maintenance software
pp.
Roger Leigh  (supplier of updated sysvinit package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Wed, 27 Jun 2012 23:00:45 +0100
Source: sysvinit
Binary: sysvinit sysvinit-utils sysv-rc initscripts bootlogd
Architecture: source amd64 all
Version: 2.88dsf-28
Distribution: unstable
Urgency: low
Maintainer: Debian sysvinit maintainers 

Changed-By: Roger Leigh 
Description: 
 bootlogd   - daemon to log boot messages
 initscripts - scripts for initializing and shutting down the system
 sysv-rc- System-V-like runlevel change mechanism
 sysvinit   - System-V-like init utilities
 sysvinit-utils - System-V-like utilities
Closes: 625463 637390 668650 669162 671124 674178 676463 676473 676721 676725 
676773 676791 676814 676893 676910 677011 677333 677590 677753 677904 678231 
678627 678680 678878
Changes: 
 sysvinit (2.88dsf-28) unstable; urgency=low
 .
   [ Steve Langasek ]
   * debian/patches/upstart_support.patch: add missing
 startpar-upstart-inject manpage.
 .
   [ Roger Leigh ]
   * Updated debconf translations:
 - ca.  Thanks to Innocent De Marchi.  Closes: #677904.
 - cs.  Thanks to Miroslav Kure.  Closes: #678680.
 - da.  Thanks to Joe Hansen.  Closes: #676893.
 - de.  Thanks to Chris Leick.  Closes: #677753.
 - fr.  Thanks to Steve Petruzzello.  Closes: #677590.
 - gl.  Thanks to Jorge Barreiro.  Clos

Bug#678231: marked as done (sysv-rc: please log filename of "obsolete init.d script")

[Debian Bug Tracking System]

Your message dated Wed, 27 Jun 2012 22:50:24 +
with message-id 
and subject line Bug#676473: fixed in sysvinit 2.88dsf-28
has caused the Debian Bug report #676473,
regarding sysv-rc: please log filename of "obsolete init.d script"
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.)


-- 
676473: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=676473
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: sysv-rc
Version: 2.88dsf-26
Severity: normal

Having procrastinated on fixing sysv-rc's complaints about being unable to
switch to a dependency-based boot sequence for months, and finally looking
into it now that we're dependency-only and I can't install or upgrade
anything until I fix it, I finally dug in and started purging packages that
sysv-rc.postinst tells me were leaving obsolete init.d scripts lying around.

But, having spent several hours removing one thing after another and being
unable to appease the script, it finally gave me the following dubious advice:

  % sudo dpkg --configure sysv-rc
  Setting up sysv-rc (2.88dsf-26) ...
  info: Checking if it is safe to convert to dependency based boot.
  
  error: Unable to migrate to dependency based boot sequencing.
  error: Problems detected: package initscripts left obsolete init.d script 
behind, package initscripts left obsolete init.d script behind, package 
initscripts left obsolete init.d script behind
  
  If this is due to the presence of unpurged obsolete initscripts,
  it is suggested that the following is run to remove them:
dpkg --purge initscripts initscripts initscripts

Not wanting to completely break my system by removing 'initscripts', I wanted
to find out exactly which obsolete scripts were causing the problem. To that
end, I finally applied the following patch to sysv-rc.postinst, which I
submit might be nice to include upstream:

--- /var/lib/dpkg/info/sysv-rc.postinst 2012-06-06 15:26:49.0 -0700
+++ /usr/home/warner/sysv-rc.postinst   2012-06-19 21:57:44.0 -0700
@@ -85,7 +85,7 @@
 for initscript in $obsolete_initscripts; do
 if [ -e "$initscript" ]; then
 retval=0
-add_problematic "package $package left obsolete init.d 
script behind"
+add_problematic "package $package left obsolete init.d 
script $initscript behind"
 add_suggestion "$package"
 fi
 done

That pinpointed the trouble to three files: bootlogd, stop-bootlogd, and
stop-bootlogd-single. I still don't understand what problem they're causing,
but I've got more information to go on now.

cheers,
 -Brian


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

Kernel: Linux 2.6.37-1-686 (SMP w/1 CPU core)
Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968)
Shell: /bin/sh linked to /bin/dash

Versions of packages sysv-rc depends on:
ii  debconf [debconf-2.0]  1.5.43
ii  insserv1.14.0-3
ii  sysvinit-utils 2.88dsf-26

Versions of packages sysv-rc recommends:
ii  lsb-base  4.1+Debian6

Versions of packages sysv-rc suggests:
pn  bum   
pn  sysv-rc-conf  

-- debconf information:
* sysv-rc/unable-to-convert:
  sysv-rc/convert-legacy: true


--- End Message ---
--- Begin Message ---
Source: sysvinit
Source-Version: 2.88dsf-28

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

bootlogd_2.88dsf-28_amd64.deb
  to main/s/sysvinit/bootlogd_2.88dsf-28_amd64.deb
initscripts_2.88dsf-28_amd64.deb
  to main/s/sysvinit/initscripts_2.88dsf-28_amd64.deb
sysv-rc_2.88dsf-28_all.deb
  to main/s/sysvinit/sysv-rc_2.88dsf-28_all.deb
sysvinit-utils_2.88dsf-28_amd64.deb
  to main/s/sysvinit/sysvinit-utils_2.88dsf-28_amd64.deb
sysvinit_2.88dsf-28.debian.tar.gz
  to main/s/sysvinit/sysvinit_2.88dsf-28.debian.tar.gz
sysvinit_2.88dsf-28.dsc
  to main/s/sysvinit/sysvinit_2.88dsf-28.dsc
sysvinit_2.88dsf-28_amd64.deb
  to main/s/sysvinit/sysvinit_2.88dsf-28_amd64.deb



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

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

Debian distribution maintenance software
pp.
Roger Leigh  (supplier of updated sysvinit package)

(This message was generated automatically at their request; if you
believe that there is a problem with i

Bug#676463: marked as done (sysv-rc: complains incorrectly(?) about obsolete init.d scripts for fuse and others)

[Debian Bug Tracking System]

Your message dated Wed, 27 Jun 2012 22:50:24 +
with message-id 
and subject line Bug#676473: fixed in sysvinit 2.88dsf-28
has caused the Debian Bug report #676473,
regarding sysv-rc: complains incorrectly(?) about obsolete init.d scripts for 
fuse and others
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.)


-- 
676473: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=676473
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: sysv-rc
Version: 2.88dsf-26
Severity: important

Dear Debian folks,


in contrast to earlier versions, with this version installation of
`sysv-rc` fails when migration to dependency based boot fails.
Additionally it complains about obsolete init.d scripts of packages
which were never a problem before and whose init.d scripts do not seem
to be obsolete.

sysv-rc (2.88dsf-26) wird eingerichtet ...
info: Checking if it is safe to convert to dependency based boot.

error: Unable to migrate to dependency based boot sequencing.
error: Problems detected: package fuse left obsolete init.d script 
behind, package initscripts left obsolete init.d script behind, package 
initscripts left obsolete init.d script behind, package initscripts left 
obsolete init.d script behind, package libchipcard-tools left obsolete init.d 
script behind, package smartmontools left obsolete init.d script behind,  , 
package gdm removed but not purged

If this is due to the presence of unpurged obsolete initscripts,
it is suggested that the following is run to remove them:
  dpkg --purge fuse initscripts initscripts initscripts 
libchipcard-tools smartmontools

See http://wiki.debian.org/LSBInitScripts/DependencyBasedBoot for
more information about dependency based boot sequencing. To
reattempt the migration process run 'dpkg --configure sysv-rc'.

dpkg: Fehler beim Bearbeiten von sysv-rc (--configure):
 Unterprozess installiertes post-installation-Skript gab den Fehlerwert 
1 zurück
Fehler traten auf beim Bearbeiten von:
 sysv-rc

This is an example for the package `fuse`.

$ dpkg -S /etc/init.d/fuse 
fuse: /etc/init.d/fuse

Also the other init.d scripts are packaged properly.


Thanks,

Paul

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

Kernel: Linux 3.2.0-2-686-pae (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/bash

Versions of packages sysv-rc depends on:
ii  debconf [debconf-2.0]  1.5.43
ii  insserv1.14.0-3
ii  sysvinit-utils 2.88dsf-26

Versions of packages sysv-rc recommends:
ii  lsb-base  4.1+Debian6

Versions of packages sysv-rc suggests:
pn  bum   
pn  sysv-rc-conf  

-- debconf information:
* sysv-rc/unable-to-convert:
  sysv-rc/convert-legacy: true


signature.asc
Description: This is a digitally signed message part
--- End Message ---
--- Begin Message ---
Source: sysvinit
Source-Version: 2.88dsf-28

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

bootlogd_2.88dsf-28_amd64.deb
  to main/s/sysvinit/bootlogd_2.88dsf-28_amd64.deb
initscripts_2.88dsf-28_amd64.deb
  to main/s/sysvinit/initscripts_2.88dsf-28_amd64.deb
sysv-rc_2.88dsf-28_all.deb
  to main/s/sysvinit/sysv-rc_2.88dsf-28_all.deb
sysvinit-utils_2.88dsf-28_amd64.deb
  to main/s/sysvinit/sysvinit-utils_2.88dsf-28_amd64.deb
sysvinit_2.88dsf-28.debian.tar.gz
  to main/s/sysvinit/sysvinit_2.88dsf-28.debian.tar.gz
sysvinit_2.88dsf-28.dsc
  to main/s/sysvinit/sysvinit_2.88dsf-28.dsc
sysvinit_2.88dsf-28_amd64.deb
  to main/s/sysvinit/sysvinit_2.88dsf-28_amd64.deb



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

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

Debian distribution maintenance software
pp.
Roger Leigh  (supplier of updated sysvinit package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Wed, 27 Jun 2012 23:00:45 +0100
Source: sysvinit
Binary: sysvinit sysvinit-utils sysv-rc initscript

Bug#678231: marked as done (sysv-rc: please log filename of "obsolete init.d script")

[Debian Bug Tracking System]

Your message dated Wed, 27 Jun 2012 22:50:24 +
with message-id 
and subject line Bug#676463: fixed in sysvinit 2.88dsf-28
has caused the Debian Bug report #676463,
regarding sysv-rc: please log filename of "obsolete init.d script"
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.)


-- 
676463: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=676463
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: sysv-rc
Version: 2.88dsf-26
Severity: normal

Having procrastinated on fixing sysv-rc's complaints about being unable to
switch to a dependency-based boot sequence for months, and finally looking
into it now that we're dependency-only and I can't install or upgrade
anything until I fix it, I finally dug in and started purging packages that
sysv-rc.postinst tells me were leaving obsolete init.d scripts lying around.

But, having spent several hours removing one thing after another and being
unable to appease the script, it finally gave me the following dubious advice:

  % sudo dpkg --configure sysv-rc
  Setting up sysv-rc (2.88dsf-26) ...
  info: Checking if it is safe to convert to dependency based boot.
  
  error: Unable to migrate to dependency based boot sequencing.
  error: Problems detected: package initscripts left obsolete init.d script 
behind, package initscripts left obsolete init.d script behind, package 
initscripts left obsolete init.d script behind
  
  If this is due to the presence of unpurged obsolete initscripts,
  it is suggested that the following is run to remove them:
dpkg --purge initscripts initscripts initscripts

Not wanting to completely break my system by removing 'initscripts', I wanted
to find out exactly which obsolete scripts were causing the problem. To that
end, I finally applied the following patch to sysv-rc.postinst, which I
submit might be nice to include upstream:

--- /var/lib/dpkg/info/sysv-rc.postinst 2012-06-06 15:26:49.0 -0700
+++ /usr/home/warner/sysv-rc.postinst   2012-06-19 21:57:44.0 -0700
@@ -85,7 +85,7 @@
 for initscript in $obsolete_initscripts; do
 if [ -e "$initscript" ]; then
 retval=0
-add_problematic "package $package left obsolete init.d 
script behind"
+add_problematic "package $package left obsolete init.d 
script $initscript behind"
 add_suggestion "$package"
 fi
 done

That pinpointed the trouble to three files: bootlogd, stop-bootlogd, and
stop-bootlogd-single. I still don't understand what problem they're causing,
but I've got more information to go on now.

cheers,
 -Brian


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

Kernel: Linux 2.6.37-1-686 (SMP w/1 CPU core)
Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968)
Shell: /bin/sh linked to /bin/dash

Versions of packages sysv-rc depends on:
ii  debconf [debconf-2.0]  1.5.43
ii  insserv1.14.0-3
ii  sysvinit-utils 2.88dsf-26

Versions of packages sysv-rc recommends:
ii  lsb-base  4.1+Debian6

Versions of packages sysv-rc suggests:
pn  bum   
pn  sysv-rc-conf  

-- debconf information:
* sysv-rc/unable-to-convert:
  sysv-rc/convert-legacy: true


--- End Message ---
--- Begin Message ---
Source: sysvinit
Source-Version: 2.88dsf-28

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

bootlogd_2.88dsf-28_amd64.deb
  to main/s/sysvinit/bootlogd_2.88dsf-28_amd64.deb
initscripts_2.88dsf-28_amd64.deb
  to main/s/sysvinit/initscripts_2.88dsf-28_amd64.deb
sysv-rc_2.88dsf-28_all.deb
  to main/s/sysvinit/sysv-rc_2.88dsf-28_all.deb
sysvinit-utils_2.88dsf-28_amd64.deb
  to main/s/sysvinit/sysvinit-utils_2.88dsf-28_amd64.deb
sysvinit_2.88dsf-28.debian.tar.gz
  to main/s/sysvinit/sysvinit_2.88dsf-28.debian.tar.gz
sysvinit_2.88dsf-28.dsc
  to main/s/sysvinit/sysvinit_2.88dsf-28.dsc
sysvinit_2.88dsf-28_amd64.deb
  to main/s/sysvinit/sysvinit_2.88dsf-28_amd64.deb



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

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

Debian distribution maintenance software
pp.
Roger Leigh  (supplier of updated sysvinit package)

(This message was generated automatically at their request; if you
believe that there is a problem with i

Bug#676473: marked as done (sysv-rc: give more information on left-behind init.d script while trying to migrate)

[Debian Bug Tracking System]

Your message dated Wed, 27 Jun 2012 22:50:24 +
with message-id 
and subject line Bug#676473: fixed in sysvinit 2.88dsf-28
has caused the Debian Bug report #676473,
regarding sysv-rc: give more information on left-behind init.d script while 
trying to migrate
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.)


-- 
676473: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=676473
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: sysv-rc
Version: 2.88dsf-26
Severity: wishlist
Tags: patch

Dear Maintainer,

my system has been running debian for about ten years now.  Once in a time,
I try to resolve a few issues preventing my system to be migrated to
dependency based boot.  Today, I looked at the suggestion
  dpkg --purge initscripts initscripts initscripts lm-sensors
which is not something I wanted to do.  Package initscripts has 24
non-obsolete and three obsolete init.d scripts.  Trying to figure out
which script to delete manually,  it would be really helpful if
sysv-rc.postinst reported the exact filename.  I used the attached
patch to get this behaviour.  Please apply if you consider it reasonable.

Regards
Stephan


diff --git a/debian/sysv-rc.postinst b/debian/sysv-rc.postinst
index 757c85e..48fdbba 100644
--- a/debian/sysv-rc.postinst
+++ b/debian/sysv-rc.postinst
@@ -85,7 +85,7 @@ is_unsafe_to_activate() {
 for initscript in $obsolete_initscripts; do
 if [ -e "$initscript" ]; then
 retval=0
-add_problematic "package $package left obsolete init.d 
script behind"
+add_problematic "package $package left obsolete init.d 
script $initscript behind"
 add_suggestion "$package"
 fi
 done

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

Kernel: Linux 3.3.0-trunk-amd64 (SMP w/8 CPU cores)
Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968)
Shell: /bin/sh linked to /bin/dash

Versions of packages sysv-rc depends on:
ii  debconf [debconf-2.0]  1.5.43
ii  insserv1.14.0-3
ii  sysvinit-utils 2.88dsf-26

Versions of packages sysv-rc recommends:
ii  lsb-base  4.1+Debian6

Versions of packages sysv-rc suggests:
ii  bum   
ii  sysv-rc-conf  0.99-7

-- debconf information:
* sysv-rc/unable-to-convert:
  sysv-rc/convert-legacy: true


--- End Message ---
--- Begin Message ---
Source: sysvinit
Source-Version: 2.88dsf-28

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

bootlogd_2.88dsf-28_amd64.deb
  to main/s/sysvinit/bootlogd_2.88dsf-28_amd64.deb
initscripts_2.88dsf-28_amd64.deb
  to main/s/sysvinit/initscripts_2.88dsf-28_amd64.deb
sysv-rc_2.88dsf-28_all.deb
  to main/s/sysvinit/sysv-rc_2.88dsf-28_all.deb
sysvinit-utils_2.88dsf-28_amd64.deb
  to main/s/sysvinit/sysvinit-utils_2.88dsf-28_amd64.deb
sysvinit_2.88dsf-28.debian.tar.gz
  to main/s/sysvinit/sysvinit_2.88dsf-28.debian.tar.gz
sysvinit_2.88dsf-28.dsc
  to main/s/sysvinit/sysvinit_2.88dsf-28.dsc
sysvinit_2.88dsf-28_amd64.deb
  to main/s/sysvinit/sysvinit_2.88dsf-28_amd64.deb



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

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

Debian distribution maintenance software
pp.
Roger Leigh  (supplier of updated sysvinit package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Wed, 27 Jun 2012 23:00:45 +0100
Source: sysvinit
Binary: sysvinit sysvinit-utils sysv-rc initscripts bootlogd
Architecture: source amd64 all
Version: 2.88dsf-28
Distribution: unstable
Urgency: low
Maintainer: Debian sysvinit maintainers 

Changed-By: Roger Leigh 
Description: 
 bootlogd   - daemon to log boot messages
 initscripts - scripts for initializing and shutting down the system
 sysv-rc- System-V-like runlevel change mechanism
 sysvinit   - System-V-like init utilities
 sysvinit-utils - System-V-like utilities
Closes: 625463 637390 668650 669162 671124 674178 676463 676473 676721 676725 
676773 676791 676814 676893 676910 677011 677333 677590 677753 

Bug#676520: marked as done ([sysv-rc] System unsuitable for dep-based boot cannot configure)

[Debian Bug Tracking System]

Your message dated Wed, 27 Jun 2012 22:50:24 +
with message-id 
and subject line Bug#676463: fixed in sysvinit 2.88dsf-28
has caused the Debian Bug report #676463,
regarding [sysv-rc] System unsuitable for dep-based boot cannot configure
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.)


-- 
676463: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=676463
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: sysv-rc
Version: 2.88dsf-26
Severity: grave

--- Please enter the report below this line. ---
I have an older init scripted system which will not configure for dep-based 
boot due to man missing lsb tags and overrides (what can I do about this?).

Additonally, as per bug #676463, there are numerous complaints about init 
scripts for removed applications and some that are not removed!

In the past, sysv-rc would configure for the old boot correctly and upgrades 
went merrily on their way. Now, it gives an error return.

Sysv-rc is left unconfigured and NO other apt operations are possible!

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

Debian Release: wheezy/sid
  500 unstableftp.us.debian.org 
  500 testing ftp.us.debian.org 
  100 experimental-snapshots qt-kde.debian.net 
1 experimentalftp.us.debian.org 

--- Package information. ---
Depends   (Version) | Installed
===-+-=
debconf   (>= 0.5)  | 1.5.43
 OR debconf-2.0 | 
sysvinit-utils (>= 2.86.ds1-62) | 2.88dsf-26
insserv  (>> 1.12.0-10) | 1.14.0-3


Recommends   (Version) | Installed
==-+-
lsb-base   (>= 3.2-14) | 4.1+Debian6


Suggests  (Version) | Installed
===-+-===
sysv-rc-conf| 
bum | 






--- End Message ---
--- Begin Message ---
Source: sysvinit
Source-Version: 2.88dsf-28

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

bootlogd_2.88dsf-28_amd64.deb
  to main/s/sysvinit/bootlogd_2.88dsf-28_amd64.deb
initscripts_2.88dsf-28_amd64.deb
  to main/s/sysvinit/initscripts_2.88dsf-28_amd64.deb
sysv-rc_2.88dsf-28_all.deb
  to main/s/sysvinit/sysv-rc_2.88dsf-28_all.deb
sysvinit-utils_2.88dsf-28_amd64.deb
  to main/s/sysvinit/sysvinit-utils_2.88dsf-28_amd64.deb
sysvinit_2.88dsf-28.debian.tar.gz
  to main/s/sysvinit/sysvinit_2.88dsf-28.debian.tar.gz
sysvinit_2.88dsf-28.dsc
  to main/s/sysvinit/sysvinit_2.88dsf-28.dsc
sysvinit_2.88dsf-28_amd64.deb
  to main/s/sysvinit/sysvinit_2.88dsf-28_amd64.deb



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

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

Debian distribution maintenance software
pp.
Roger Leigh  (supplier of updated sysvinit package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Wed, 27 Jun 2012 23:00:45 +0100
Source: sysvinit
Binary: sysvinit sysvinit-utils sysv-rc initscripts bootlogd
Architecture: source amd64 all
Version: 2.88dsf-28
Distribution: unstable
Urgency: low
Maintainer: Debian sysvinit maintainers 

Changed-By: Roger Leigh 
Description: 
 bootlogd   - daemon to log boot messages
 initscripts - scripts for initializing and shutting down the system
 sysv-rc- System-V-like runlevel change mechanism
 sysvinit   - System-V-like init utilities
 sysvinit-utils - System-V-like utilities
Closes: 625463 637390 668650 669162 671124 674178 676463 676473 676721 676725 
676773 676791 676814 676893 676910 677011 677333 677590 677753 677904 678231 
678627 678680 678878
Changes: 
 sysvinit (2.88dsf-28) unstable; urgency=low
 .
   [ Steve Langasek ]
   * debian/patches/upstart_support.patch: add missing
 startpar-upstart-inject manpage.
 .
   [ Roger Leigh ]
   * Updated debconf translations:
 - ca.  Thanks to Innocent De Marchi.  Closes: #677904.
 - cs.  Thanks to Miroslav Kure.  Closes: #678680.
 - da.  Thanks to Joe Hansen.  Closes: #676893.
 - de.  Thanks to Chris Leick.  Closes: #677753.
 - fr.  Thanks to Steve Petruzzello.  Closes: #677590.
 - gl.  Thanks to Jorge Barreiro.  Clos

Bug#676463: marked as done (sysv-rc: complains incorrectly(?) about obsolete init.d scripts for fuse and others)

[Debian Bug Tracking System]

Your message dated Wed, 27 Jun 2012 22:50:24 +
with message-id 
and subject line Bug#676463: fixed in sysvinit 2.88dsf-28
has caused the Debian Bug report #676463,
regarding sysv-rc: complains incorrectly(?) about obsolete init.d scripts for 
fuse and others
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.)


-- 
676463: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=676463
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: sysv-rc
Version: 2.88dsf-26
Severity: important

Dear Debian folks,


in contrast to earlier versions, with this version installation of
`sysv-rc` fails when migration to dependency based boot fails.
Additionally it complains about obsolete init.d scripts of packages
which were never a problem before and whose init.d scripts do not seem
to be obsolete.

sysv-rc (2.88dsf-26) wird eingerichtet ...
info: Checking if it is safe to convert to dependency based boot.

error: Unable to migrate to dependency based boot sequencing.
error: Problems detected: package fuse left obsolete init.d script 
behind, package initscripts left obsolete init.d script behind, package 
initscripts left obsolete init.d script behind, package initscripts left 
obsolete init.d script behind, package libchipcard-tools left obsolete init.d 
script behind, package smartmontools left obsolete init.d script behind,  , 
package gdm removed but not purged

If this is due to the presence of unpurged obsolete initscripts,
it is suggested that the following is run to remove them:
  dpkg --purge fuse initscripts initscripts initscripts 
libchipcard-tools smartmontools

See http://wiki.debian.org/LSBInitScripts/DependencyBasedBoot for
more information about dependency based boot sequencing. To
reattempt the migration process run 'dpkg --configure sysv-rc'.

dpkg: Fehler beim Bearbeiten von sysv-rc (--configure):
 Unterprozess installiertes post-installation-Skript gab den Fehlerwert 
1 zurück
Fehler traten auf beim Bearbeiten von:
 sysv-rc

This is an example for the package `fuse`.

$ dpkg -S /etc/init.d/fuse 
fuse: /etc/init.d/fuse

Also the other init.d scripts are packaged properly.


Thanks,

Paul

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

Kernel: Linux 3.2.0-2-686-pae (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/bash

Versions of packages sysv-rc depends on:
ii  debconf [debconf-2.0]  1.5.43
ii  insserv1.14.0-3
ii  sysvinit-utils 2.88dsf-26

Versions of packages sysv-rc recommends:
ii  lsb-base  4.1+Debian6

Versions of packages sysv-rc suggests:
pn  bum   
pn  sysv-rc-conf  

-- debconf information:
* sysv-rc/unable-to-convert:
  sysv-rc/convert-legacy: true


signature.asc
Description: This is a digitally signed message part
--- End Message ---
--- Begin Message ---
Source: sysvinit
Source-Version: 2.88dsf-28

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

bootlogd_2.88dsf-28_amd64.deb
  to main/s/sysvinit/bootlogd_2.88dsf-28_amd64.deb
initscripts_2.88dsf-28_amd64.deb
  to main/s/sysvinit/initscripts_2.88dsf-28_amd64.deb
sysv-rc_2.88dsf-28_all.deb
  to main/s/sysvinit/sysv-rc_2.88dsf-28_all.deb
sysvinit-utils_2.88dsf-28_amd64.deb
  to main/s/sysvinit/sysvinit-utils_2.88dsf-28_amd64.deb
sysvinit_2.88dsf-28.debian.tar.gz
  to main/s/sysvinit/sysvinit_2.88dsf-28.debian.tar.gz
sysvinit_2.88dsf-28.dsc
  to main/s/sysvinit/sysvinit_2.88dsf-28.dsc
sysvinit_2.88dsf-28_amd64.deb
  to main/s/sysvinit/sysvinit_2.88dsf-28_amd64.deb



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

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

Debian distribution maintenance software
pp.
Roger Leigh  (supplier of updated sysvinit package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Wed, 27 Jun 2012 23:00:45 +0100
Source: sysvinit
Binary: sysvinit sysvinit-utils sysv-rc initscript

Bug#676473: marked as done (sysv-rc: give more information on left-behind init.d script while trying to migrate)

[Debian Bug Tracking System]

Your message dated Wed, 27 Jun 2012 22:50:24 +
with message-id 
and subject line Bug#676463: fixed in sysvinit 2.88dsf-28
has caused the Debian Bug report #676463,
regarding sysv-rc: give more information on left-behind init.d script while 
trying to migrate
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.)


-- 
676463: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=676463
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: sysv-rc
Version: 2.88dsf-26
Severity: wishlist
Tags: patch

Dear Maintainer,

my system has been running debian for about ten years now.  Once in a time,
I try to resolve a few issues preventing my system to be migrated to
dependency based boot.  Today, I looked at the suggestion
  dpkg --purge initscripts initscripts initscripts lm-sensors
which is not something I wanted to do.  Package initscripts has 24
non-obsolete and three obsolete init.d scripts.  Trying to figure out
which script to delete manually,  it would be really helpful if
sysv-rc.postinst reported the exact filename.  I used the attached
patch to get this behaviour.  Please apply if you consider it reasonable.

Regards
Stephan


diff --git a/debian/sysv-rc.postinst b/debian/sysv-rc.postinst
index 757c85e..48fdbba 100644
--- a/debian/sysv-rc.postinst
+++ b/debian/sysv-rc.postinst
@@ -85,7 +85,7 @@ is_unsafe_to_activate() {
 for initscript in $obsolete_initscripts; do
 if [ -e "$initscript" ]; then
 retval=0
-add_problematic "package $package left obsolete init.d 
script behind"
+add_problematic "package $package left obsolete init.d 
script $initscript behind"
 add_suggestion "$package"
 fi
 done

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

Kernel: Linux 3.3.0-trunk-amd64 (SMP w/8 CPU cores)
Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968)
Shell: /bin/sh linked to /bin/dash

Versions of packages sysv-rc depends on:
ii  debconf [debconf-2.0]  1.5.43
ii  insserv1.14.0-3
ii  sysvinit-utils 2.88dsf-26

Versions of packages sysv-rc recommends:
ii  lsb-base  4.1+Debian6

Versions of packages sysv-rc suggests:
ii  bum   
ii  sysv-rc-conf  0.99-7

-- debconf information:
* sysv-rc/unable-to-convert:
  sysv-rc/convert-legacy: true


--- End Message ---
--- Begin Message ---
Source: sysvinit
Source-Version: 2.88dsf-28

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

bootlogd_2.88dsf-28_amd64.deb
  to main/s/sysvinit/bootlogd_2.88dsf-28_amd64.deb
initscripts_2.88dsf-28_amd64.deb
  to main/s/sysvinit/initscripts_2.88dsf-28_amd64.deb
sysv-rc_2.88dsf-28_all.deb
  to main/s/sysvinit/sysv-rc_2.88dsf-28_all.deb
sysvinit-utils_2.88dsf-28_amd64.deb
  to main/s/sysvinit/sysvinit-utils_2.88dsf-28_amd64.deb
sysvinit_2.88dsf-28.debian.tar.gz
  to main/s/sysvinit/sysvinit_2.88dsf-28.debian.tar.gz
sysvinit_2.88dsf-28.dsc
  to main/s/sysvinit/sysvinit_2.88dsf-28.dsc
sysvinit_2.88dsf-28_amd64.deb
  to main/s/sysvinit/sysvinit_2.88dsf-28_amd64.deb



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

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

Debian distribution maintenance software
pp.
Roger Leigh  (supplier of updated sysvinit package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Wed, 27 Jun 2012 23:00:45 +0100
Source: sysvinit
Binary: sysvinit sysvinit-utils sysv-rc initscripts bootlogd
Architecture: source amd64 all
Version: 2.88dsf-28
Distribution: unstable
Urgency: low
Maintainer: Debian sysvinit maintainers 

Changed-By: Roger Leigh 
Description: 
 bootlogd   - daemon to log boot messages
 initscripts - scripts for initializing and shutting down the system
 sysv-rc- System-V-like runlevel change mechanism
 sysvinit   - System-V-like init utilities
 sysvinit-utils - System-V-like utilities
Closes: 625463 637390 668650 669162 671124 674178 676463 676473 676721 676725 
676773 676791 676814 676893 676910 677011 677333 677590 677753 

Bug#671124: marked as done (initscripts: Fails to update due to mountoverflowtmp)

[Debian Bug Tracking System]

Your message dated Wed, 27 Jun 2012 22:50:24 +
with message-id 
and subject line Bug#671124: fixed in sysvinit 2.88dsf-28
has caused the Debian Bug report #671124,
regarding initscripts: Fails to update due to mountoverflowtmp
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.)


-- 
671124: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=671124
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: initscripts
Version: 2.88dsf-22.1
Severity: serious
Justification: Fails to upgrade

Hi.

During dist-upgrade:

(Reading database ... 398609 files and directories currently installed.)
Preparing to replace initscripts 2.88dsf-22 (using 
.../initscripts_2.88dsf-22.1_amd64.deb) ...
Unpacking replacement initscripts ...
Processing triggers for man-db ...
Setting up initscripts (2.88dsf-22.1) ...
update-rc.d: error: unable to read /etc/init.d/mountoverflowtmp
dpkg: error processing initscripts (--configure):
 subprocess installed post-installation script returned error exit status 1
configured to not write apport reports
  Errors were encountered while processing:
 initscripts
E: Sub-process /usr/bin/dpkg returned an error code (1)
You have new mail in /var/mail/cbrulebois


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

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

Versions of packages initscripts depends on:
ii  coreutils   8.13-3.1
ii  debianutils 4.3
ii  libc6   2.13-31
ii  lsb-base3.2+Debian31
ii  mount   2.20.1-4
ii  sysv-rc 2.88dsf-22.1
ii  sysvinit-utils  2.88dsf-22.1
ii  ucf 3.0025+nmu3

Versions of packages initscripts recommends:
ii  e2fsprogs  1.42.1-2
ii  psmisc 22.16-1

initscripts suggests no packages.

-- Configuration Files:
/etc/init.d/mountkernfs.sh changed [not included]
/etc/init.d/mountoverflowtmp [Errno 2] No such file or directory: 
u'/etc/init.d/mountoverflowtmp'

-- no debconf information


--- End Message ---
--- Begin Message ---
Source: sysvinit
Source-Version: 2.88dsf-28

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

bootlogd_2.88dsf-28_amd64.deb
  to main/s/sysvinit/bootlogd_2.88dsf-28_amd64.deb
initscripts_2.88dsf-28_amd64.deb
  to main/s/sysvinit/initscripts_2.88dsf-28_amd64.deb
sysv-rc_2.88dsf-28_all.deb
  to main/s/sysvinit/sysv-rc_2.88dsf-28_all.deb
sysvinit-utils_2.88dsf-28_amd64.deb
  to main/s/sysvinit/sysvinit-utils_2.88dsf-28_amd64.deb
sysvinit_2.88dsf-28.debian.tar.gz
  to main/s/sysvinit/sysvinit_2.88dsf-28.debian.tar.gz
sysvinit_2.88dsf-28.dsc
  to main/s/sysvinit/sysvinit_2.88dsf-28.dsc
sysvinit_2.88dsf-28_amd64.deb
  to main/s/sysvinit/sysvinit_2.88dsf-28_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 671...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Roger Leigh  (supplier of updated sysvinit package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Wed, 27 Jun 2012 23:00:45 +0100
Source: sysvinit
Binary: sysvinit sysvinit-utils sysv-rc initscripts bootlogd
Architecture: source amd64 all
Version: 2.88dsf-28
Distribution: unstable
Urgency: low
Maintainer: Debian sysvinit maintainers 

Changed-By: Roger Leigh 
Description: 
 bootlogd   - daemon to log boot messages
 initscripts - scripts for initializing and shutting down the system
 sysv-rc- System-V-like runlevel change mechanism
 sysvinit   - System-V-like init utilities
 sysvinit-utils - System-V-like utilities
Closes: 625463 637390 668650 669162 671124 674178 676463 676473 676721 676725 
676773 676791 676814 676893 676910 677011 677333 677590 677753 677904 678231 
678627 678680 678878
Changes: 
 sysvinit (2.88dsf-28) unstable; urgency=low
 .
   [ Steve Langasek ]
   * debian/patches/upstart_support.patch: add missing
 startpar-upstart-inject manpage.
 .
   [ Roger Leigh ]
   * Updated debconf translations:
 - ca.  Thanks to Innocent De Marchi

Bug#677565: msva-perl: Insecure dependency in socket while running with -T switch at /usr/lib/perl/5.14/IO/Socket.pm line 80

[intrigeri]

Hi,

Iain Lane wrote (27 Jun 2012 22:30:40 GMT) :
> Where can I find these commits?

There: git://lair.fifthhorseman.net/~dkg/msva-perl
(Yeah, I know, that's not obvious.)



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

Processed (with 2 errors): forcibly merging 662844 679279, reassign 662844 to phonon-backend-vlc, forcibly merging 662103 662844 ...

[Debian Bug Tracking System]

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

> forcemerge 662844 679279
Bug #662844 [amarok] amarok: pause/resume cause maximum volume
Bug #662844 [amarok] amarok: pause/resume cause maximum volume
Marked as found in versions amarok/2.5.0-3.
Bug #679279 [amarok] amarok: Resets pulseaudio volume to 100% after pause
679279 was not blocked by any bugs.
679279 was not blocking any bugs.
Added blocking bug(s) of 679279: 662103
Marked as found in versions amarok/2.5.0-1.
Merged 662844 679279
> reassign 662844 phonon-backend-vlc
Bug #662844 [amarok] amarok: pause/resume cause maximum volume
Bug #679279 [amarok] amarok: Resets pulseaudio volume to 100% after pause
Bug reassigned from package 'amarok' to 'phonon-backend-vlc'.
Bug reassigned from package 'amarok' to 'phonon-backend-vlc'.
No longer marked as found in versions amarok/2.5.0-1 and amarok/2.5.0-3.
No longer marked as found in versions amarok/2.5.0-1 and amarok/2.5.0-3.
Ignoring request to alter fixed versions of bug #662844 to the same values 
previously set
Ignoring request to alter fixed versions of bug #679279 to the same values 
previously set
> forcemerge 662103 662844
Bug #662103 [phonon-backend-vlc] phonon-backend-vlc: Pausing and resuming in 
Amarok changes volume to 100%
Bug #662844 [phonon-backend-vlc] amarok: pause/resume cause maximum volume
Set Bug forwarded-to-address to 'https://bugs.kde.org/show_bug.cgi?id=296589'.
Set Bug forwarded-to-address to 'https://bugs.kde.org/show_bug.cgi?id=296589'.
Severity set to 'grave' from 'normal'
Severity set to 'grave' from 'normal'
Failed to forcibly merge 662103: It is nonsensical for a bug to block itself 
(or a merged partner): 662844
Debbugs::Control::set_blocks('bug', 662844, 'block', 662844, 'add', 1, 
'request_msgid', '<1340837161-3973-bts-mo...@debian.org>', 'request_replyto', 
...) called at /usr/local/lib/site_perl/Debbugs/Control.pm line 2117
Debbugs::Control::set_merged('transcript', 'GLOB(0x1eee1d8)', 
'requester', 'Modestas Vainius ', 'request_addr', 
'cont...@bugs.debian.org', 'request_msgid', 
'<1340837161-3973-bts-mo...@debian.org>', 'request_subject', ...) called at 
/usr/lib/debbugs/service line 887
eval {...} called at /usr/lib/debbugs/service line 886

> affects 662844 amarok
Failed to mark 662844 as affecting package(s): failed to get lock on 
/org/bugs.debian.org/spool/lock/662844 -- Unable to lock 
/org/bugs.debian.org/spool/lock/662844 Resource temporarily unavailable.
Unable to lock /org/bugs.debian.org/spool/lock/662844 Resource temporarily 
unavailable at /usr/local/lib/site_perl/Debbugs/Common.pm line 579.
Unable to lock /org/bugs.debian.org/spool/lock/662844 Resource temporarily 
unavailable at /usr/local/lib/site_perl/Debbugs/Common.pm line 579.
Unable to lock /org/bugs.debian.org/spool/lock/662844 Resource temporarily 
unavailable at /usr/local/lib/site_perl/Debbugs/Common.pm line 579.
Unable to lock /org/bugs.debian.org/spool/lock/662844 Resource temporarily 
unavailable at /usr/local/lib/site_perl/Debbugs/Common.pm line 579.
Unable to lock /org/bugs.debian.org/spool/lock/662844 Resource temporarily 
unavailable at /usr/local/lib/site_perl/Debbugs/Common.pm line 579.
Unable to lock /org/bugs.debian.org/spool/lock/662844 Resource temporarily 
unavailable at /usr/local/lib/site_perl/Debbugs/Common.pm line 579.
Unable to lock /org/bugs.debian.org/spool/lock/662844 Resource temporarily 
unavailable at /usr/local/lib/site_perl/Debbugs/Common.pm line 579.
Unable to lock /org/bugs.debian.org/spool/lock/662844 Resource temporarily 
unavailable at /usr/local/lib/site_perl/Debbugs/Common.pm line 579.
Unable to lock /org/bugs.debian.org/spool/lock/662844 Resource temporarily 
unavailable at /usr/local/lib/site_perl/Debbugs/Common.pm line 579. at 
/usr/local/lib/site_perl/Debbugs/Common.pm line 597
Debbugs::Common::filelock('/org/bugs.debian.org/spool/lock/662844') 
called at /usr/local/lib/site_perl/Debbugs/Status.pm line 209
Debbugs::Status::read_bug('bug', 662844, 'lock', 1) called at 
/usr/local/lib/site_perl/Debbugs/Status.pm line 464
Debbugs::Status::lock_read_all_merged_bugs('bug', 662844) called at 
/usr/local/lib/site_perl/Debbugs/Control.pm line 3604
Debbugs::Control::__begin_control('remove', 0, 'add', 1, 
'request_replyto', 'Modestas Vainius ', 'transcript', 
'GLOB(0x1eee1d8)', 'bug', ...) called at 
/usr/local/lib/site_perl/Debbugs/Control.pm line 2533
Debbugs::Control::affects('transcript', 'GLOB(0x1eee1d8)', 'requester', 
'Modestas Vainius ', 'request_addr', 
'cont...@bugs.debian.org', 'request_msgid', 
'<1340837161-3973-bts-mo...@debian.org>', 'request_subject', ...) called at 
/usr/lib/debbugs/service line 984
eval {...} called at /usr/lib/debbugs/service line 983

> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
662103: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=662103
662844: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=662844
679279: http://bugs

Bug#660260: Fwd: GDL seems to use non public symbols from plplot (Debian Wheezy freeze on Saturday)

[Sylwester Arabas]

Hi All,

On 27/06/12 18:59, Sylwester Arabas wrote:

Here's a fix suggested by Joel:

On 05/06/12 14:09, gal...@cox.net wrote:
 > I would suggest replacing:
 >
 > lib::mesh_nr(xVec1, yVec1, z1, (long int) xEl, 1,1);
 >
 > in plotting.cpp by
 >
 > plmesh(xVec1, yVec1, z1, (long int) xEl, 1,1);
 >
 > I think the plplot library now has the functionality that was
 > missing before.
 >
 > If we remove the call to mesh_nr then we no longer have to include
 > plot3d_nr.cpp which was causing the problem.

I'll try to test it and commit to the repository today or tomorrow.


That's now in the CVS. Please test if it fixes the issue.
Best,
Sylwester

--
http://www.igf.fuw.edu.pl/~slayoo/



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

Bug#678707: marked as done (mozc: FTBFS[kfreebsd]: error: aggregate 'mozc::{anonymous}::IsPeerValid(int, pid_t*)::ucred peer_cred' has incomplete type and cannot be defined)

[Debian Bug Tracking System]

Your message dated Wed, 27 Jun 2012 22:36:59 +
with message-id 
and subject line Bug#678707: fixed in mozc 1.5.1090.102-2
has caused the Debian Bug report #678707,
regarding mozc: FTBFS[kfreebsd]: error: aggregate 
'mozc::{anonymous}::IsPeerValid(int, pid_t*)::ucred peer_cred' has incomplete 
type and cannot be defined
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.)


-- 
678707: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=678707
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:mozc
Version: 1.5.1090.102-1
Severity: serious
Tags: sid wheezy
User: debian-...@lists.debian.org
Usertags: kfreebsd
X-Debbugs-Cc: debian-...@lists.debian.org
Justification: fails to build from source (but built successfully in the past)

Hi!

Your package failed to build on the kfreebsd-* buildds:

  g++ '-DGTEST_HAS_TR1_TUPLE=1' '-DGTEST_HAS_RTTI=0' '-DOS_LINUX' 
'-DMOZC_SERVER_DIRECTORY="/usr/lib/mozc"' '-DMOZC_BUILD' 
'-DMOZC_LANGUAGE_SUFFIX_FOR_LINUX="_japanese"' '-DMOZC_ENABLE_UNITTEST' 
'-DNDEBUG' '-DQT_NO_DEBUG' '-DNO_LOGGING' '-DIGNORE_HELP_FLAG' 
'-DIGNORE_INVALID_FLAG' -I. -Ithird_party/breakpad/src 
-Iout_linux/Release/obj/gen -Iout_linux/Release/obj/gen/proto_out 
-Ithird_party/gmock/include -Ithird_party/gtest/include  -Wall -Werror 
-Wno-char-subscripts -Wno-sign-compare -Wno-deprecated-declarations 
-Wwrite-strings -fPIC -fno-exceptions -fmessage-length=0 
-fno-omit-frame-pointer -fno-strict-aliasing -funsigned-char -include 
base/namespace.h -pipe -pthread -O2 -Wno-deprecated -MMD -MF 
out_linux/Release/.deps/out_linux/Release/obj.target/ipc/ipc/unix_ipc.o.d.raw 
-g -O2 -fstack-protector --param=ssp-buffer-size=4 -Wformat 
-Werror=format-security -c -o out_linux/Release/obj.target/ipc/ipc/unix_ipc.o 
ipc/unix_ipc.cc
ipc/unix_ipc.cc: In function 'bool mozc::{anonymous}::IsPeerValid(int, pid_t*)':
ipc/unix_ipc.cc:155:16: error: aggregate 'mozc::{anonymous}::IsPeerValid(int, 
pid_t*)::ucred peer_cred' has incomplete type and cannot be defined
ipc/unix_ipc.cc:157:38: error: 'SO_PEERCRED' was not declared in this scope
make[2]: *** [out_linux/Release/obj.target/ipc/ipc/unix_ipc.o] Error 1
make[2]: Leaving directory 
`/build/buildd-mozc_1.5.1090.102-1-kfreebsd-amd64-_FuKra/mozc-1.5.1090.102'
Traceback (most recent call last):
Running: make -j1 MAKE_JOBS=1 BUILDTYPE=Release builddir_name=out_linux 
ibus_mozc scim_mozc scim_mozc_setup mozc_emacs_helper uim-mozc fcitx-mozc 
mozc_server mozc_tool mozc_renderer
  File "build_mozc.py", line 1477, in 
main()
  File "build_mozc.py", line 1465, in main
BuildMain(cmd_opts, cmd_args, original_directory_name)
  File "build_mozc.py", line 1233, in BuildMain
BuildOnBSD(options, targets, original_directory_name)
  File "build_mozc.py", line 1080, in BuildOnBSD
RunOrDie([make_command] + build_args + target_names)
  File 
"/build/buildd-mozc_1.5.1090.102-1-kfreebsd-amd64-_FuKra/mozc-1.5.1090.102/build_tools/util.py",
 line 98, in RunOrDie
'==']))
build_tools.util.RunOrDieError: 
==
 ERROR: make -j1 MAKE_JOBS=1 BUILDTYPE=Release builddir_name=out_linux 
ibus_mozc scim_mozc scim_mozc_setup mozc_emacs_helper uim-mozc fcitx-mozc 
mozc_server mozc_tool mozc_renderer
==
make[1]: *** [override_dh_auto_build] Error 1
make[1]: Leaving directory 
`/build/buildd-mozc_1.5.1090.102-1-kfreebsd-amd64-_FuKra/mozc-1.5.1090.102'
make: *** [build-arch] Error 2
dpkg-buildpackage: error: debian/rules build-arch gave error exit status 2

Full build log at
https://buildd.debian.org/status/fetch.php?pkg=mozc&arch=kfreebsd-amd64&ver=1.5.1090.102-1&stamp=1340163911

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: mozc
Source-Version: 1.5.1090.102-2

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

emacs-mozc-bin_1.5.1090.102-2_amd64.deb
  to main/m/mozc/emacs-mozc-bin_1.5.1090.102-2_amd64.deb
emacs-mozc_1.5.1090.102-2_amd64.deb
  to main/m/mozc/emacs-mozc_1.5.1090.102-2_amd64.deb
fcitx-mozc_1.5.1090.102-2_amd64.deb
  to main/m/mozc/fcitx-mozc_1.5.1090.102-2_amd64.deb
ibus-mozc_1.5.1090.102-2_amd64.deb
  to main/m/mozc/ibus-mozc_1.5.1090.102-2_amd64.deb
mozc-data_1.5.1090.102-2_all.deb
  to main/m/mozc/mozc-data_1.5.1090.102-2_all.deb
mozc-server_1.5.1090.102-2_amd64.deb
  to main/m/mozc/mozc-server_1.5.1090.102-2_amd64.deb
mozc-utils-gui_1.5.1090.102-2_a

Bug#679182: FTBFS on mips*: braces around scalar initializer for type 'unsigned int'

[Vedran Furač]

On 06/26/2012 11:27 PM, Luca Falavigna wrote:

> Source: logkeys
> Version: 0.1.1a-3
> Severity: serious
> Justification: fails to build from source
> 
> 
> logkeys fails to build from source on mips*, but built in the past:

Hmmm, could you try with this source from svn:

http://mentors.debian.net/package/logkeys

http://mentors.debian.net/debian/pool/main/l/logkeys/logkeys_0.1.1a+svn20120529-1.dsc

Regards,
Vedran

<>

Bug#679311: marked as done (brasero: FTBFS[kfreebsd]: symbol delta)

[Debian Bug Tracking System]

Your message dated Wed, 27 Jun 2012 22:32:47 +
with message-id 
and subject line Bug#679311: fixed in brasero 3.4.1-2
has caused the Debian Bug report #679311,
regarding brasero: FTBFS[kfreebsd]: symbol delta
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.)


-- 
679311: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=679311
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:brasero
Version: 3.4.1-1
Severity: serious
Tags: sid wheezy
User: debian-...@lists.debian.org
Usertags: kfreebsd
X-Debbugs-Cc: debian-...@lists.debian.org
Justification: fails to build from source (but built successfully in the past)

Hi!

Your package failed to build on the kfreebsd-* buildds:

dh_compress -pbrasero-cdrkit  
dh_fixperms -pbrasero-cdrkit  
dh_makeshlibs -pbrasero-cdrkit  --no-act
dh_strip -plibbrasero-media3-1  
dh_compress -plibbrasero-media3-1  
dh_fixperms -plibbrasero-media3-1  
dh_makeshlibs -plibbrasero-media3-1  -V 'libbrasero-media3-1 (>= 3.0.0)' 
-Xplugins -- -c4
dpkg-gensymbols: warning: some symbols or patterns disappeared in the symbols 
file: see diff output below
dpkg-gensymbols: warning: debian/libbrasero-media3-1/DEBIAN/symbols doesn't 
match completely debian/libbrasero-media3-1.symbols
--- debian/libbrasero-media3-1.symbols 
(libbrasero-media3-1_3.4.1-1_kfreebsd-i386)
+++ dpkg-gensymbolsftlW5e   2012-06-25 20:16:08.0 +
@@ -177,11 +177,11 @@
  brasero_dest_selection_set_session@Base 3.0.0
  brasero_drive_properties_get_type@Base 3.0.0
  brasero_drive_properties_new@Base 3.0.0
- brasero_file_monitor_directory_contents@Base 3.0.0
- brasero_file_monitor_foreach_cancel@Base 3.0.0
- brasero_file_monitor_get_type@Base 3.0.0
- brasero_file_monitor_reset@Base 3.0.0
- brasero_file_monitor_single_file@Base 3.0.0
+#MISSING: 3.4.1-1# brasero_file_monitor_directory_contents@Base 3.0.0
+#MISSING: 3.4.1-1# brasero_file_monitor_foreach_cancel@Base 3.0.0
+#MISSING: 3.4.1-1# brasero_file_monitor_get_type@Base 3.0.0
+#MISSING: 3.4.1-1# brasero_file_monitor_reset@Base 3.0.0
+#MISSING: 3.4.1-1# brasero_file_monitor_single_file@Base 3.0.0
  brasero_file_node_add@Base 3.0.0
  brasero_file_node_check_imported_sibling@Base 3.0.0
  brasero_file_node_check_name_existence@Base 3.0.0
dh_makeshlibs: dpkg-gensymbols -plibbrasero-media3-1 
-Idebian/libbrasero-media3-1.symbols -Pdebian/libbrasero-media3-1 
-edebian/libbrasero-media3-1/usr/lib/libbrasero-burn3.so.1.2.3
 -edebian/libbrasero-media3-1/usr/lib/libbrasero-media3.so.1.2.3
 -edebian/libbrasero-media3-1/usr/lib/libbrasero-utils3.so.1.2.3
 -c4 returned exit code 1
make: *** [binary-fixup/libbrasero-media3-1] Error 1

Full build log at
https://buildd.debian.org/status/fetch.php?pkg=brasero&arch=kfreebsd-i386&ver=3.4.1-1&stamp=1340655382

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: brasero
Source-Version: 3.4.1-2

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

brasero-cdrkit_3.4.1-2_amd64.deb
  to main/b/brasero/brasero-cdrkit_3.4.1-2_amd64.deb
brasero-common_3.4.1-2_all.deb
  to main/b/brasero/brasero-common_3.4.1-2_all.deb
brasero_3.4.1-2.debian.tar.gz
  to main/b/brasero/brasero_3.4.1-2.debian.tar.gz
brasero_3.4.1-2.dsc
  to main/b/brasero/brasero_3.4.1-2.dsc
brasero_3.4.1-2_amd64.deb
  to main/b/brasero/brasero_3.4.1-2_amd64.deb
gir1.2-brasero-3.0_3.4.1-2_amd64.deb
  to main/b/brasero/gir1.2-brasero-3.0_3.4.1-2_amd64.deb
libbrasero-media3-1_3.4.1-2_amd64.deb
  to main/b/brasero/libbrasero-media3-1_3.4.1-2_amd64.deb
libbrasero-media3-dev_3.4.1-2_amd64.deb
  to main/b/brasero/libbrasero-media3-dev_3.4.1-2_amd64.deb



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

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

Debian distribution maintenance software
pp.
Michael Biebl  (supplier of updated brasero package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Thu, 28 Jun 2012 00:00:29 +0200
Source: brasero
Binary: brasero brasero-common brasero-cdrkit libbrasero-medi

Bug#677565: msva-perl: Insecure dependency in socket while running with -T switch at /usr/lib/perl/5.14/IO/Socket.pm line 80

[Iain Lane]

Hi,

On Wed, Jun 20, 2012 at 04:33:02AM +0200, intrigeri wrote:
> Hi,
> 
> intrigeri wrote (19 Jun 2012 19:44:19 GMT) :
> > However, given Net::Server pretends to be taint clean, it does looks
> > like there's a serious bug in there, that shall be reported and fixed.
> > I'll try to isolate a minimal testcase and will report it in Debian
> > and upstream.
> 
> I tried building msva-perl 0.8-2 + commit f24706da cherry-picked from
> upstream. Good news: for some reason, the resulting package does not
> expose the bug we are discussing :)
> 
> So I suggest the following plan:
> 
>   0. ASAP: someone (Iain? Daniel?) reproduces my successful testing
>  result.

Sorry for the delay. I tried to do this but failed because I cannot find
the commits you are referring to. I use the repository referenced in
Vcs-Git of msva-perl: git://git.monkeysphere.info/msva-perl.

,
| laney@raleigh> git show f24706da
| fatal: ambiguous argument 'f24706da': unknown revision or path not in
| the working tree.
`

Where can I find these commits? Alternatively, you could upload a source
package somewhere for me to build/test.

Cheers,

-- 
Iain Lane  [ i...@orangesquash.org.uk ]
Debian Developer   [ la...@debian.org ]
Ubuntu Developer   [ la...@ubuntu.com ]
PhD student   [ i...@cs.nott.ac.uk ]


signature.asc
Description: Digital signature

Bug#662103: Hearing loss is data loss...

[Shai Berger]

severity 662103 grave
thanks

I was listening to music on earphones today, when this bug hit me. Not nice. I 
am suggesting that this bug is "grave" because it may cause actual bodily 
harm.

Thanks,
Shai.



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

Bug#659061: brasero: segfaults when creating a subfolder

[Michael Biebl]

Hi,

I can't reproduce this problem with 3.4.1 (the current version in sid).

Could you please try again and check if the problem is fixed for you, too?

Michael
-- 
Why is it that all of the instruments seeking intelligent life in the
universe are pointed away from Earth?



signature.asc
Description: OpenPGP digital signature

Processed: Hearing loss is data loss...

[Debian Bug Tracking System]

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

> severity 662103 grave
Bug #662103 [phonon-backend-vlc] phonon-backend-vlc: Pausing and resuming in 
Amarok changes volume to 100%
Severity set to 'grave' from 'normal'
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
662103: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=662103
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#679332: Missing dependency on libnvidia-ml1

[Adam Majer]

Package: nvidia-smi
Version: 302.17-2
Severity: serious

There is a missing dependency on libnvidia-ml1


$ nvidia-smi -L
Failed to initialize NVML: Unknown Error


$ sudo aptitude install libnvidia-ml1
...
Setting up libnvidia-ml1:amd64 (302.17-2) ...
...


$ nvidia-smi -L
GPU 0: GeForce 6150 (UUID: N/A)
GPU 1: GeForce 9400 GT (UUID: N/A)



-- Package-specific info:
uname -a:
Linux mira 3.4-trunk-amd64 #1 SMP Wed Jun 6 10:34:53 CEST 2012 x86_64 GNU/Linux

/proc/version:
Linux version 3.4-trunk-amd64 (Debian 3.4.1-1~experimental.1) 
(debian-ker...@lists.debian.org) (gcc version 4.6.3 (Debian 4.6.3-1) ) #1 SMP 
Wed Jun 6 10:34:53 CEST 2012

/proc/driver/nvidia/version:
NVRM version: NVIDIA UNIX x86_64 Kernel Module  302.17  Tue Jun 12 16:03:22 PDT 
2012
GCC version:  gcc version 4.6.3 (Debian 4.6.3-7) 


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

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

Versions of packages nvidia-smi depends on:
ii  libc6  2.13-33

Versions of packages nvidia-smi recommends:
ii  nvidia-kernel-dkms [nvidia-kernel-302.17]  302.17-2

Versions of packages nvidia-smi suggests:
ii  nvidia-kernel-dkms [nvidia-kernel-dkms]  302.17-2
ii  nvidia-kernel-source 302.17-2

Versions of packages nvidia-glx depends on:
ii  dpkg   1.16.4.3
ii  libgl1-nvidia-glx  302.17-2
ii  nvidia-alternative 302.17-2
ii  nvidia-installer-cleanup   2011+3
ii  nvidia-kernel-dkms [nvidia-kernel-302.17]  302.17-2
ii  nvidia-support 2011+3
ii  nvidia-vdpau-driver302.17-2
ii  xserver-xorg-video-nvidia  302.17-2

Versions of packages nvidia-glx suggests:
ii  nvidia-kernel-dkms [nvidia-kernel-dkms]  302.17-2
ii  nvidia-kernel-source 302.17-2
ii  nvidia-settings  295.49-1

Versions of packages libgl1-nvidia-glx depends on:
ii  libc6 2.13-33
ii  libx11-6  2:1.5.0-1
ii  libxext6  2:1.3.1-2
ii  libxv12:1.0.7-1
ii  libxvmc1  2:1.0.7-1
ii  multiarch-support 2.13-33
ii  nvidia-alternative302.17-2
ii  nvidia-installer-cleanup  2011+3
ii  nvidia-support2011+3

Versions of packages libgl1-nvidia-glx recommends:
ii  nvidia-kernel-dkms [nvidia-kernel-302.17]  302.17-2

Versions of packages libgl1-nvidia-glx suggests:
ii  nvidia-kernel-dkms [nvidia-kernel-dkms]  302.17-2
ii  nvidia-kernel-source 302.17-2

Versions of packages xserver-xorg-video-nvidia depends on:
ii  libc6  2.13-33
ii  libgl1-nvidia-glx  302.17-2
ii  nvidia-alternative 302.17-2
ii  nvidia-installer-cleanup   2011+3
ii  nvidia-support 2011+3
ii  xserver-xorg-core [xorg-video-abi-12]  2:1.12.1.902-1

Versions of packages xserver-xorg-video-nvidia recommends:
ii  nvidia-kernel-dkms [nvidia-kernel-302.17]  302.17-2
ii  nvidia-vdpau-driver302.17-2

Versions of packages xserver-xorg-video-nvidia suggests:
ii  nvidia-kernel-dkms [nvidia-kernel-dkms]  302.17-2
ii  nvidia-kernel-source 302.17-2
ii  nvidia-settings  295.49-1

Versions of packages nvidia-alternative depends on:
ii  glx-alternative-nvidia  0.2.1
ii  libgl1-nvidia-alternatives  302.17-2
ii  libglx-nvidia-alternatives  302.17-2

Versions of packages nvidia-kernel-dkms depends on:
ii  dkms  2.2.0.3-1
ii  nvidia-installer-cleanup  2011+3
ii  nvidia-kernel-common  2011+3

Versions of packages nvidia-kernel-dkms recommends:
ii  nvidia-glx  302.17-2

Versions of packages nvidia-kernel-source depends on:
ii  debhelper  9.20120608
ii  make   3.81-8.2
ii  quilt  0.60-2

Versions of packages nvidia-kernel-source recommends:
ii  kernel-package12.036+nmu2
ii  module-assistant  0.11.4
ii  nvidia-kernel-common  2011+3

Versions of packages nvidia-kernel-source suggests:
ii  nvidia-glx  302.17-2

Versions of packages glx-alternative-nvidia depends on:
ii  glx-alternative-mesa  0.2.1
ii  glx-diversions0.2.1

Versions of packages glx-alternative-nvidia suggests:
ii  nvidia-glx  302.17-2

Versions of packages nvidia-smi is related to:
pn  libdrm-nouveau1  
ii  libdrm-nouveau1a 2.4.33-3
ii  libgl1-nvidia-glx [libgl1-nvidia-glx-any]302.17-2
ii  libgl1-nvidia-glx-ia32 [libgl1-nvidia-glx-ia32-any]  302.17-2
ii  linux-headers-3.4-trunk-amd64 [linux-headers]3.4.1-1~experimental.1
ii  nvidia-glx [nvidia-glx-any]  

Bug#676760: marked as done (lmms: FTBFS: build-dependency not installable: libwine-dev)

[Debian Bug Tracking System]

Your message dated Wed, 27 Jun 2012 22:06:23 +
with message-id 
and subject line Bug#676760: fixed in lmms 0.4.10-2.3
has caused the Debian Bug report #676760,
regarding lmms: FTBFS: build-dependency not installable: libwine-dev
to be marked as done.

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

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


-- 
676760: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=676760
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: lmms
Version: 0.4.10-2.2
Severity: serious
Tags: wheezy sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20120609 qa-ftbfs
Justification: FTBFS on amd64

Hi,

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

Relevant part:
> ┌──┐
> │ Install lmms build dependencies (apt-based resolver)
>  │
> └──┘
> 
> Installing build dependencies
> Reading package lists...
> Building dependency tree...
> Reading state information...
> Some packages could not be installed. This may mean that you have
> requested an impossible situation or if you are using the unstable
> distribution that some required packages have not yet been created
> or been moved out of Incoming.
> The following information may help to resolve the situation:
> 
> The following packages have unmet dependencies:
>  sbuild-build-depends-lmms-dummy : Depends: libwine-dev but it is not 
> installable
> E: Unable to correct problems, you have held broken packages.
> apt-get failed.

The full build log is available from:
   http://people.debian.org/~lucas/logs/2012/06/09/lmms_0.4.10-2.2_unstable.log

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

About the archive rebuild: The rebuild was done on EC2 VM instances from
Amazon Web Services, using a clean, minimal and up-to-date chroot. Every
failed build was retried once to eliminate random failures.


--- End Message ---
--- Begin Message ---
Source: lmms
Source-Version: 0.4.10-2.3

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

lmms-common_0.4.10-2.3_all.deb
  to main/l/lmms/lmms-common_0.4.10-2.3_all.deb
lmms_0.4.10-2.3.debian.tar.gz
  to main/l/lmms/lmms_0.4.10-2.3.debian.tar.gz
lmms_0.4.10-2.3.dsc
  to main/l/lmms/lmms_0.4.10-2.3.dsc
lmms_0.4.10-2.3_i386.deb
  to main/l/lmms/lmms_0.4.10-2.3_i386.deb



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

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

Debian distribution maintenance software
pp.
Hilko Bengen  (supplier of updated lmms 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, 27 Jun 2012 23:14:40 +0200
Source: lmms
Binary: lmms lmms-common
Architecture: source all i386
Version: 0.4.10-2.3
Distribution: sid
Urgency: low
Maintainer: Hilko Bengen 
Changed-By: Hilko Bengen 
Description: 
 lmms   - Linux Multimedia Studio
 lmms-common - Linux Multimedia Studio - common files
Closes: 676760
Changes: 
 lmms (0.4.10-2.3) unstable; urgency=low
 .
   * Non maintainer upload.
   * Remove wine-related dependencies on amd64, thereby disabling building
 VST plugin. (Closes: #676760)
Checksums-Sha1: 
 50a0c6a1eba534b95d2a986b73bf05b99f4a2f1f 1479 lmms_0.4.10-2.3.dsc
 0595f36b986c8730eb8af6f1a80c4c40d023cfbb 6393 lmms_0.4.10-2.3.debian.tar.gz
 f6da9f02101f2b2986a0ade2759076251da621c7 5694450 lmms-common_0.4.10-2.3_all.deb
 b098572881a12f3fc36081c1dcc53a81e4f7188c 4113154 lmms_0.4.10-2.3_i386.deb
Checksums-Sha256: 
 15f6e07332ddcbb68b3b47137c235ba9c86e0e8efadef50d5079a3191aefb2f5 1479 
lmms_0.4.10-2.3.dsc
 4c3c17425c70f6b9ed6f856a4a156393ddfa8a8215e500bf1b087d06afa90896 6393 
lmms_0.4.10-2.3.debian.tar.gz
 24de109c11ac83882c9abdef6f99a8e889db70b026260dea51fd4e598d7775d8 5694450 
lmms-common_0.4.10-2.3_all.deb
 bae4f9c29d0dd4cabbf530d4b6cb6bdb7edd7d74b39cf16df2c5d9d10bdf46ba 4113154 
lmms_0.4.10-2.3_i386.deb
Files: 
 9815824820ed9e8a20bca312ec0039d3 1479 sound optional lmms_0.4.10-2.3.dsc
 cc839066b3139770cbfef67e9bf7eb55 6393 sound optional 
lmms_0.4.10-2.3.d

Processed: Re: Bug#679320: elecctric-fence: FTBFS: testsuite timeout

[Debian Bug Tracking System]

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

> tags 679320 moreinfo unreproducible help
Bug #679320 [src:electric-fence] elecctric-fence: FTBFS: testsuite timeout
Added tag(s) unreproducible, help, and moreinfo.
> quit
Stopping processing here.

Please contact me if you need assistance.
-- 
679320: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=679320
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#679320: elecctric-fence: FTBFS: testsuite timeout

[Matthew Vernon]

tags 679320 moreinfo unreproducible help
quit


Hi!

Your package failed to build on the buildds:

rm -f eftest
cc -g -O2 -DUSE_SEMAPHORE -fPIC eftest.o libefence.a -o eftest -lpthread

Testing Electric Fence.
After the last test, it should print that the test has PASSED.
./eftest

   Electric Fence 2.2 Copyright (C) 1987-1999 Bruce Perens
./tstheap 3072

   Electric Fence 2.2 Copyright (C) 1987-1999 Bruce Perens
make[1]: *** [all] Killed
make: *** [build-stamp] Error 2


It's not clear to me why this was Killed. Is there a tight resource 
limit on the buildd or something? tstheap works the computer a little hard.


I normally build on i386, but I tested a build on a handy am64 machine, 
and it builds just fine.


Regards,

Matthew



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

Bug#671897: marked as done (xf86-video-omap: current binary segfaults, please update to fixed 0.3.0 release)

[Debian Bug Tracking System]

Your message dated Wed, 27 Jun 2012 21:42:38 +
with message-id 
and subject line Bug#671897: fixed in xf86-video-omap 0.3.0-1
has caused the Debian Bug report #671897,
regarding xf86-video-omap: current binary segfaults, please update to fixed 
0.3.0 release
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.)


-- 
671897: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=671897
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: xf86-video-omap
Version: 0.0.1~git20110717-1
Severity: grave
Justification: renders package unusable

The xf86-video-omap version, which is currently available through Debian
experimental, produces the following segfault:

Program received signal SIGSEGV, Segmentation fault.
xb6ef2d16 in pixman_fill1_line (v=1, width=, offs=0, 
dst=) at ../../pixman/pixman-fast-path.c:
2011../../pixman/pixman-fast-path.c: No such file or directory.
(gdb) bt
#0  0xb6ef2d16 in pixman_fill1_line (v=1, width=, offs=0, 
dst=) at ../../pixman/pixman-fast-path.c:2011
#1  pixman_fill1 (xor=4294967295, height=, width=16, y=0, x=0, 
stride=, bits=) at 
../../pixman/pixman-fast-path.c:2033
#2  fast_path_fill (imp=, bits=, 
stride=, bpp=, x=0, y=0, width=16, height=16, 
xor=4294967295)
at ../../pixman/pixman-fast-path.c:2134
#3  0xb6ef3bd8 in _pixman_implementation_fill (xor=4294967295, height=16, 
width=16, y=0, x=0, bpp=, stride=, 
bits=,
imp=) at ../../pixman/pixman-implementation.c:176
#4  delegate_fill (imp=, bits=, stride=, bpp=, x=0, y=0, width=16, height=16, xor=4294967295)
at ../../pixman/pixman-implementation.c:62
#5  0xb6ef3d0a in _pixman_implementation_fill (imp=, 
bits=, stride=, bpp=, x=0, y=0, 
width=16,
height=16, xor=4294967295) at ../../pixman/pixman-implementation.c:176
#6  0xb6ef3bd8 in _pixman_implementation_fill (xor=4294967295, height=16, 
width=16, y=0, x=0, bpp=, stride=, 
bits=,
imp=) at ../../pixman/pixman-implementation.c:176
#7  delegate_fill (imp=, bits=, stride=, bpp=, x=0, y=0, width=16, height=16, xor=4294967295)
at ../../pixman/pixman-implementation.c:62
#8  0xb6ef3d0a in _pixman_implementation_fill (imp=, 
bits=, stride=, bpp=, x=0, y=0, 
width=16,
height=16, xor=4294967295) at ../../pixman/pixman-implementation.c:176
#9  0xb6ebba96 in pixman_fill (bits=0x0, stride=0, bpp=1, x=, 
y=0, width=16, height=16, xor=4294967295) at ../../pixman/pixman.c:772
#10 0xb6b30354 in fbFill (pDrawable=, pGC=0x2a1830f8, 
x=, y=0, width=16, height=16) at ../../fb/fbfill.c:48
#11 0xb6b30808 in fbPolyFillRect (pDrawable=0x2a183578, pGC=0x2a1830f8, 
nrect=, prect=) at ../../fb/fbfillrect.c:77
#12 0xb6b4c0ee in ExaCheckPolyFillRect (pDrawable=0x2a183578, pGC=0x2a1830f8, 
nrect=1, prect=) at ../../exa/exa_unaccel.c:311
#13 0xb6b47e1e in exaPolyFillRect (pDrawable=0x2a183578, pGC=0x2a1830f8, 
nrect=1, prect=0xbefff66c) at ../../exa/exa_accel.c:852
#14 0x2a0b71d0 in damagePolyFillRect (pDrawable=0x2a183578, pGC=0x2a1830f8, 
nRects=1, pRects=0xbefff66c) at ../../../miext/damage/damage.c:1309
#15 0x2a03ec32 in CreateDefaultStipple (screenNum=) at 
../../dix/gc.c:938
#16 0x2a028206 in main (argc=3, argv=0xbefff854, envp=) at 
../../dix/main.c:220

This problem has been fixed in the latest release (0.3.0). xf86-video-omap 0.3.0
requires the OMAP API inside of libdrm, though.

-- Sebastian


--- End Message ---
--- Begin Message ---
Source: xf86-video-omap
Source-Version: 0.3.0-1

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

xf86-video-omap_0.3.0-1.debian.tar.gz
  to main/x/xf86-video-omap/xf86-video-omap_0.3.0-1.debian.tar.gz
xf86-video-omap_0.3.0-1.dsc
  to main/x/xf86-video-omap/xf86-video-omap_0.3.0-1.dsc
xf86-video-omap_0.3.0.orig.tar.gz
  to main/x/xf86-video-omap/xf86-video-omap_0.3.0.orig.tar.gz
xserver-xorg-video-omap-dbg_0.3.0-1_armhf.deb
  to main/x/xf86-video-omap/xserver-xorg-video-omap-dbg_0.3.0-1_armhf.deb
xserver-xorg-video-omap_0.3.0-1_armhf.deb
  to main/x/xf86-video-omap/xserver-xorg-video-omap_0.3.0-1_armhf.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 671...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Sebastian Reichel  (supplier of updated xf86-video-omap 
package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administ

Bug#665255: marked as done (ruby-net-http-persistent: FTBFS: tests failed)

[Debian Bug Tracking System]

Your message dated Wed, 27 Jun 2012 21:35:12 +
with message-id 
and subject line Bug#665255: fixed in ruby-net-http-persistent 2.7-1
has caused the Debian Bug report #665255,
regarding ruby-net-http-persistent: FTBFS: tests failed
to be marked as done.

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

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


-- 
665255: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=665255
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: ruby-net-http-persistent
Version: 2.5.2-1
Severity: serious
Tags: wheezy sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20120321 qa-ftbfs
Justification: FTBFS on amd64

Hi,

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

Relevant part:
>  fakeroot debian/rules binary
> dh binary --buildsystem=ruby --with ruby
>dh_testroot -O--buildsystem=ruby
>dh_prep -O--buildsystem=ruby
>dh_installdirs -O--buildsystem=ruby
>dh_auto_install -O--buildsystem=ruby
>   Entering dh_ruby --install
> install -d 
> /«PKGBUILDDIR»/debian/ruby-net-http-persistent/usr/lib/ruby/vendor_ruby
> install -D -m644 lib/net/http/persistent/ssl_reuse.rb 
> /«PKGBUILDDIR»/debian/ruby-net-http-persistent/usr/lib/ruby/vendor_ruby/net/http/persistent/ssl_reuse.rb
> install -D -m644 lib/net/http/faster.rb 
> /«PKGBUILDDIR»/debian/ruby-net-http-persistent/usr/lib/ruby/vendor_ruby/net/http/faster.rb
> install -D -m644 lib/net/http/persistent.rb 
> /«PKGBUILDDIR»/debian/ruby-net-http-persistent/usr/lib/ruby/vendor_ruby/net/http/persistent.rb
> /usr/bin/ruby1.8 -I/usr/lib/ruby/vendor_ruby 
> /usr/lib/ruby/vendor_ruby/gem2deb/test_runner.rb
> Run options: --seed 63029
> 
> # Running tests:
> 
> .SE
> 
> Finished tests in 0.390409s, 202.3519 tests/s, 678.7753 assertions/s.
> 
>   1) Error:
> test_ssl_connection_reuse(TestNetHttpPersistentSSLReuse):
> OpenSSL::SSL::SSLError: SSL_connect SYSCALL returned=5 errno=0 state=unknown 
> state
> 
> ./debian/ruby-net-http-persistent//usr/lib/ruby/vendor_ruby/net/http/persistent/ssl_reuse.rb:117:in
>  `connect'
> 
> ./debian/ruby-net-http-persistent//usr/lib/ruby/vendor_ruby/net/http/persistent/ssl_reuse.rb:117:in
>  `connect'
> /usr/lib/ruby/1.8/net/http.rb:553:in `do_start'
> /usr/lib/ruby/1.8/net/http.rb:548:in `start'
> ./test/test_net_http_persistent_ssl_reuse.rb:83:in 
> `test_ssl_connection_reuse'
> /usr/lib/ruby/vendor_ruby/minitest/unit.rb:1036:in `run_test'
> /usr/lib/ruby/vendor_ruby/minitest/unit.rb:1036:in `run'
> /usr/lib/ruby/vendor_ruby/minitest/unit.rb:825:in `_run_suite'
> /usr/lib/ruby/vendor_ruby/minitest/unit.rb:818:in `map'
> /usr/lib/ruby/vendor_ruby/minitest/unit.rb:818:in `_run_suite'
> /usr/lib/ruby/vendor_ruby/minitest/unit.rb:805:in `_run_suites'
> /usr/lib/ruby/vendor_ruby/minitest/unit.rb:805:in `map'
> /usr/lib/ruby/vendor_ruby/minitest/unit.rb:805:in `_run_suites'
> /usr/lib/ruby/vendor_ruby/minitest/unit.rb:778:in `_run_anything'
> /usr/lib/ruby/vendor_ruby/minitest/unit.rb:947:in `run_tests'
> /usr/lib/ruby/vendor_ruby/minitest/unit.rb:934:in `send'
> /usr/lib/ruby/vendor_ruby/minitest/unit.rb:934:in `_run'
> /usr/lib/ruby/vendor_ruby/minitest/unit.rb:933:in `each'
> /usr/lib/ruby/vendor_ruby/minitest/unit.rb:933:in `_run'
> /usr/lib/ruby/vendor_ruby/minitest/unit.rb:922:in `run'
> /usr/lib/ruby/vendor_ruby/minitest/unit.rb:690:in `autorun'
> -e:1
> 
> 79 tests, 265 assertions, 0 failures, 1 errors, 1 skips
> ERROR: Test "ruby1.8" failed. Exiting.
> dh_auto_install: dh_ruby --install 
> /«PKGBUILDDIR»/debian/ruby-net-http-persistent returned exit code 1
> make: *** [binary] Error 1

The full build log is available from:
   
http://people.debian.org/~lucas/logs/2012/03/21/ruby-net-http-persistent_2.5.2-1.log

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

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


--- End Message ---
--- Begin Message ---
Source: ruby-net-http-persistent
Source-Version: 2.7-1

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

ruby-net-http-persistent_2.7-1.debian.tar.gz
  to 
main/r/ruby-net-http-persistent/ruby-net-http-persistent_2.7-1.debian.tar.gz
ruby-net-http-persistent_2.7-1.dsc
  to main/

Bug#676045: nautilus-image-manipulator: diff for NMU version 1.1-1.1

[Emilien Klein]

2012/6/27 Salvatore Bonaccorso :
> I can cancel the NMU if you would like to upload yourself, this would be
> perfect!  It's still time do to so[1].

I just checked the patch and everything is fine. I'm OK with you doing the NMU.


> Btw, I had some warnings on build:
>
>> WARNING: syntax errors in nautilus_image_manipulator/ProfileSettings.py: 
>> encoding declaration in Unicode string (ProfileSettings.py, line 0)
>> WARNING: syntax errors in bin/nautilus-image-manipulator: encoding 
>> declaration in Unicode string (nautilus-image-manipulator, line 0)
>> WARNING: syntax errors in 
>> nautilus_image_manipulator/nautilus_image_manipulatorconfig.py: encoding 
>> declaration in Unicode string (nautilus_image_manipulatorconfig.py, line 0)
>> WARNING: syntax errors in docs/conf.py: encoding declaration in Unicode 
>> string (conf.py, line 0)
>> WARNING: syntax errors in nautilus_image_manipulator/helpers.py: encoding 
>> declaration in Unicode string (helpers.py, line 0)
>> /usr/lib/python2.6/dist-packages/DistUtilsExtra/auto.py:336: 
>> DeprecationWarning: the sha module is deprecated; use the hashlib module 
>> instead
>>   mod = __import__(module)
>> WARNING: syntax errors in nautilus_image_manipulator/upload/z1fichiercom.py: 
>> encoding declaration in Unicode string (z1fichiercom.py, line 0)
>> WARNING: syntax errors in nautilus_image_manipulator/ImageManipulations.py: 
>> encoding declaration in Unicode string (ImageManipulations.py, line 0)
>> WARNING: syntax errors in 
>> nautilus_image_manipulator/NautilusImageManipulatorDialog.py: encoding 
>> declaration in Unicode string (NautilusImageManipulatorDialog.py, line 0)

I'll investigate this.

   +Emilien



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

Bug#677462: marked as done (libmeep-mpich2-dev and libmeep-mpi-default-dev: error when trying to install together)

[Debian Bug Tracking System]

Your message dated Wed, 27 Jun 2012 21:26:41 +
with message-id 
and subject line Bug#677462: fixed in meep-mpi-default 1.1.1-9
has caused the Debian Bug report #677462,
regarding libmeep-mpich2-dev and libmeep-mpi-default-dev: error when trying to 
install together
to be marked as done.

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

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


-- 
677462: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=677462
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: libmeep-mpi-default-dev,libmeep-mpich2-dev
Version: libmeep-mpi-default-dev/1.1.1-8
Version: libmeep-mpich2-dev/1.1.1-8
Severity: serious
User: trei...@debian.org
Usertags: edos-file-overwrite

Date: 2012-06-14
Architecture: amd64
Distribution: sid

Hi,

automatic installation tests of packages that share a file and at the
same time do not conflict by their package dependency relationships has
detected the following problem:


WARNING: The following packages cannot be authenticated!
  libgomp1 libfftw3-3 libquadmath0 libgfortran3 libblas3 libblas3gf libcr0
  libgsl0ldbl liblapack3 liblapack3gf libharminv2 libmpich2-3 libhdf5-mpich2-7
  libmeep-mpi-default6 libmeep-mpi-default-dev libmeep-mpich2-6
  libmeep-mpich2-dev
Preconfiguring packages ...
Authentication warning overridden.
Can not write log, openpty() failed (/dev/pts not mounted?)
Selecting previously unselected package libgomp1:amd64.
(Reading database ... 10690 files and directories currently installed.)
Unpacking libgomp1:amd64 (from .../libgomp1_4.7.0-13_amd64.deb) ...
Selecting previously unselected package libfftw3-3:amd64.
Unpacking libfftw3-3:amd64 (from .../libfftw3-3_3.3.2-3_amd64.deb) ...
Selecting previously unselected package libquadmath0:amd64.
Unpacking libquadmath0:amd64 (from .../libquadmath0_4.7.0-13_amd64.deb) ...
Selecting previously unselected package libgfortran3:amd64.
Unpacking libgfortran3:amd64 (from .../libgfortran3_4.7.0-13_amd64.deb) ...
Selecting previously unselected package libblas3.
Unpacking libblas3 (from .../libblas3_1.2.20110419-3_amd64.deb) ...
Selecting previously unselected package libblas3gf.
Unpacking libblas3gf (from .../libblas3gf_1.2.20110419-3_amd64.deb) ...
Selecting previously unselected package libcr0.
Unpacking libcr0 (from .../libcr0_0.8.4-2_amd64.deb) ...
Selecting previously unselected package libgsl0ldbl.
Unpacking libgsl0ldbl (from .../libgsl0ldbl_1.15+dfsg-1_amd64.deb) ...
Selecting previously unselected package liblapack3.
Unpacking liblapack3 (from .../liblapack3_3.4.1-1_amd64.deb) ...
Selecting previously unselected package liblapack3gf.
Unpacking liblapack3gf (from .../liblapack3gf_3.4.1-1_amd64.deb) ...
Selecting previously unselected package libharminv2.
Unpacking libharminv2 (from .../libharminv2_1.3.1-8_amd64.deb) ...
Selecting previously unselected package libmpich2-3.
Unpacking libmpich2-3 (from .../libmpich2-3_1.4.1-4_amd64.deb) ...
Selecting previously unselected package libhdf5-mpich2-7.
Unpacking libhdf5-mpich2-7 (from .../libhdf5-mpich2-7_1.8.8-9_amd64.deb) ...
Selecting previously unselected package libmeep-mpi-default6.
Unpacking libmeep-mpi-default6 (from 
.../libmeep-mpi-default6_1.1.1-8_amd64.deb) ...
Selecting previously unselected package libmeep-mpi-default-dev.
Unpacking libmeep-mpi-default-dev (from 
.../libmeep-mpi-default-dev_1.1.1-8_amd64.deb) ...
Selecting previously unselected package libmeep-mpich2-6.
Unpacking libmeep-mpich2-6 (from .../libmeep-mpich2-6_1.1.1-8_amd64.deb) ...
Selecting previously unselected package libmeep-mpich2-dev.
Unpacking libmeep-mpich2-dev (from .../libmeep-mpich2-dev_1.1.1-8_amd64.deb) ...
dpkg: error processing 
/var/cache/apt/archives/libmeep-mpich2-dev_1.1.1-8_amd64.deb (--unpack):
 trying to overwrite '/usr/include/meep.hpp', which is also in package 
libmeep-mpi-default-dev 1.1.1-8
Errors were encountered while processing:
 /var/cache/apt/archives/libmeep-mpich2-dev_1.1.1-8_amd64.deb
E: Sub-process /usr/bin/dpkg returned an error code (1)


This is a serious bug as it makes installation fail, and violates
sections 7.6.1 and 10.1 of the policy. An optimal solution would
consist in only one of the packages installing that file, and renaming
or removing the file in the other package. Depending on the
circumstances you might also consider Replace relations or file
diversions. If the conflicting situation cannot be resolved then, as a
last resort, the two packages have to declare a mutual
Conflict. Please take into account that Replaces, Conflicts and
diversions should only be used when packages provide different
implementations for the same functionality.

Here is a list of files that a

Bug#677459: marked as done (libmeep-mpi-default-dev and libmeep-lam4-dev: error when trying to install together)

[Debian Bug Tracking System]

Your message dated Wed, 27 Jun 2012 21:26:41 +
with message-id 
and subject line Bug#677459: fixed in meep-mpi-default 1.1.1-9
has caused the Debian Bug report #677459,
regarding libmeep-mpi-default-dev and libmeep-lam4-dev: error when trying to 
install together
to be marked as done.

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

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


-- 
677459: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=677459
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: libmeep-lam4-dev,libmeep-mpi-default-dev
Version: libmeep-lam4-dev/1.1.1-8
Version: libmeep-mpi-default-dev/1.1.1-8
Severity: serious
User: trei...@debian.org
Usertags: edos-file-overwrite

Date: 2012-06-14
Architecture: amd64
Distribution: sid

Hi,

automatic installation tests of packages that share a file and at the
same time do not conflict by their package dependency relationships has
detected the following problem:


WARNING: The following packages cannot be authenticated!
  libgomp1 libfftw3-3 libquadmath0 libgfortran3 libblas3 libblas3gf libcr0
  libgsl0ldbl liblapack3 liblapack3gf libharminv2 libmpich2-3 libhdf5-mpich2-7
  libmeep-lam4-6 libmeep-lam4-dev libmeep-mpi-default6 libmeep-mpi-default-dev
Preconfiguring packages ...
Authentication warning overridden.
Can not write log, openpty() failed (/dev/pts not mounted?)
Selecting previously unselected package libgomp1:amd64.
(Reading database ... 10690 files and directories currently installed.)
Unpacking libgomp1:amd64 (from .../libgomp1_4.7.0-13_amd64.deb) ...
Selecting previously unselected package libfftw3-3:amd64.
Unpacking libfftw3-3:amd64 (from .../libfftw3-3_3.3.2-3_amd64.deb) ...
Selecting previously unselected package libquadmath0:amd64.
Unpacking libquadmath0:amd64 (from .../libquadmath0_4.7.0-13_amd64.deb) ...
Selecting previously unselected package libgfortran3:amd64.
Unpacking libgfortran3:amd64 (from .../libgfortran3_4.7.0-13_amd64.deb) ...
Selecting previously unselected package libblas3.
Unpacking libblas3 (from .../libblas3_1.2.20110419-3_amd64.deb) ...
Selecting previously unselected package libblas3gf.
Unpacking libblas3gf (from .../libblas3gf_1.2.20110419-3_amd64.deb) ...
Selecting previously unselected package libcr0.
Unpacking libcr0 (from .../libcr0_0.8.4-2_amd64.deb) ...
Selecting previously unselected package libgsl0ldbl.
Unpacking libgsl0ldbl (from .../libgsl0ldbl_1.15+dfsg-1_amd64.deb) ...
Selecting previously unselected package liblapack3.
Unpacking liblapack3 (from .../liblapack3_3.4.1-1_amd64.deb) ...
Selecting previously unselected package liblapack3gf.
Unpacking liblapack3gf (from .../liblapack3gf_3.4.1-1_amd64.deb) ...
Selecting previously unselected package libharminv2.
Unpacking libharminv2 (from .../libharminv2_1.3.1-8_amd64.deb) ...
Selecting previously unselected package libmpich2-3.
Unpacking libmpich2-3 (from .../libmpich2-3_1.4.1-4_amd64.deb) ...
Selecting previously unselected package libhdf5-mpich2-7.
Unpacking libhdf5-mpich2-7 (from .../libhdf5-mpich2-7_1.8.8-9_amd64.deb) ...
Selecting previously unselected package libmeep-lam4-6.
Unpacking libmeep-lam4-6 (from .../libmeep-lam4-6_1.1.1-8_amd64.deb) ...
Selecting previously unselected package libmeep-lam4-dev.
Unpacking libmeep-lam4-dev (from .../libmeep-lam4-dev_1.1.1-8_amd64.deb) ...
Selecting previously unselected package libmeep-mpi-default6.
Unpacking libmeep-mpi-default6 (from 
.../libmeep-mpi-default6_1.1.1-8_amd64.deb) ...
Selecting previously unselected package libmeep-mpi-default-dev.
Unpacking libmeep-mpi-default-dev (from 
.../libmeep-mpi-default-dev_1.1.1-8_amd64.deb) ...
dpkg: error processing 
/var/cache/apt/archives/libmeep-mpi-default-dev_1.1.1-8_amd64.deb (--unpack):
 trying to overwrite '/usr/include/meep.hpp', which is also in package 
libmeep-lam4-dev 1.1.1-8
Errors were encountered while processing:
 /var/cache/apt/archives/libmeep-mpi-default-dev_1.1.1-8_amd64.deb
E: Sub-process /usr/bin/dpkg returned an error code (1)


This is a serious bug as it makes installation fail, and violates
sections 7.6.1 and 10.1 of the policy. An optimal solution would
consist in only one of the packages installing that file, and renaming
or removing the file in the other package. Depending on the
circumstances you might also consider Replace relations or file
diversions. If the conflicting situation cannot be resolved then, as a
last resort, the two packages have to declare a mutual
Conflict. Please take into account that Replaces, Conflicts and
diversions should only be used when packages provide different
implementations for the same functionality.

Here is a list of files that are known to be shared

Bug#678152: marked as done (crashes at start)

[Debian Bug Tracking System]

Your message dated Wed, 27 Jun 2012 21:22:36 +
with message-id 
and subject line Bug#678152: fixed in freemedforms-project 0.7.5-1
has caused the Debian Bug report #678152,
regarding crashes at start
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.)


-- 
678152: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=678152
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: freediams
Version: 0.7.4-2
Severity: grave

Hello people,

today I started experimenting with the FreeMedForms suite. FreeMedForms starts
ok, but FreeDiams and FreeAccount do not (I won't file/clone the bug to
FreeAccount, since it seems to be the same exact issue).

Both, in fact, crash at start, with similar backtraces. I'm attaching them,
hoping that someone is able to fix them :)

Kindly,
David

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

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

Versions of packages freediams depends on:
ii  freemedforms-common-resources  0.7.4-2
ii  freemedforms-freedata  0.7.4-2
ii  freemedforms-libs  0.7.4-2
ii  libc6  2.13-33
ii  libgcc11:4.7.0-13
ii  libqt4-network 4:4.8.2-1
ii  libqt4-script  4:4.8.2-1
ii  libqt4-sql 4:4.8.2-1
ii  libqt4-svg 4:4.8.2-1
ii  libqt4-xml 4:4.8.2-1
ii  libqtcore4 4:4.8.2-1
ii  libqtgui4  4:4.8.2-1
ii  libstdc++6 4.7.0-13
ii  libx11-6   2:1.4.99.901-2
ii  libxext6   2:1.3.1-2

freediams recommends no packages.

Versions of packages freediams suggests:
pn  freediams-doc  
ii  ttf-mscorefonts-installer  3.4+nmu1

-- no debconf information



-- 
 . ''`.   Debian developer | http://wiki.debian.org/DavidPaleino
 : :'  : Linuxer #334216 --|-- http://www.hanskalabs.net/
 `. `'`  GPG: 1392B174 | http://deb.li/dapal
   `-   2BAB C625 4E66 E7B8 450A C3E1 E6AA 9017 1392 B174


freeaccount.log.bz2
Description: application/bzip


freediams.log.bz2
Description: application/bzip


signature.asc
Description: PGP signature
--- End Message ---
--- Begin Message ---
Source: freemedforms-project
Source-Version: 0.7.5-1

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

freeaccount_0.7.5-1_amd64.deb
  to main/f/freemedforms-project/freeaccount_0.7.5-1_amd64.deb
freediams-doc-en_0.7.5-1_all.deb
  to main/f/freemedforms-project/freediams-doc-en_0.7.5-1_all.deb
freediams-doc-fr_0.7.5-1_all.deb
  to main/f/freemedforms-project/freediams-doc-fr_0.7.5-1_all.deb
freediams_0.7.5-1_amd64.deb
  to main/f/freemedforms-project/freediams_0.7.5-1_amd64.deb
freemedforms-common-resources_0.7.5-1_all.deb
  to main/f/freemedforms-project/freemedforms-common-resources_0.7.5-1_all.deb
freemedforms-emr-doc-en_0.7.5-1_all.deb
  to main/f/freemedforms-project/freemedforms-emr-doc-en_0.7.5-1_all.deb
freemedforms-emr-doc-fr_0.7.5-1_all.deb
  to main/f/freemedforms-project/freemedforms-emr-doc-fr_0.7.5-1_all.deb
freemedforms-emr-resources_0.7.5-1_all.deb
  to main/f/freemedforms-project/freemedforms-emr-resources_0.7.5-1_all.deb
freemedforms-emr_0.7.5-1_amd64.deb
  to main/f/freemedforms-project/freemedforms-emr_0.7.5-1_amd64.deb
freemedforms-freedata_0.7.5-1_all.deb
  to main/f/freemedforms-project/freemedforms-freedata_0.7.5-1_all.deb
freemedforms-i18n_0.7.5-1_all.deb
  to main/f/freemedforms-project/freemedforms-i18n_0.7.5-1_all.deb
freemedforms-libs_0.7.5-1_amd64.deb
  to main/f/freemedforms-project/freemedforms-libs_0.7.5-1_amd64.deb
freemedforms-project_0.7.5-1.debian.tar.gz
  to main/f/freemedforms-project/freemedforms-project_0.7.5-1.debian.tar.gz
freemedforms-project_0.7.5-1.dsc
  to main/f/freemedforms-project/freemedforms-project_0.7.5-1.dsc
freemedforms-project_0.7.5-1_all.deb
  to main/f/freemedforms-project/freemedforms-project_0.7.5-1_all.deb
freemedforms-project_0.7.5.orig.tar.gz
  to main/f/freemedforms-project/freemedforms-project_0.7.5.orig.tar.gz
freemedforms-theme_0.7.5-1_all.deb
  to main/f/freemedforms-project/freemedforms-theme_0.7.5-1_all.deb



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

Thank you for reporting the bug, which will now be closed.  If 

Bug#679272: marked as done (bcfg2-server: unescaped shell command issues in the Trigger plugin)

[Debian Bug Tracking System]

Your message dated Wed, 27 Jun 2012 21:18:45 +
with message-id 
and subject line Bug#679272: fixed in bcfg2 1.2.2-2
has caused the Debian Bug report #679272,
regarding bcfg2-server: unescaped shell command issues in the Trigger plugin
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.)


-- 
679272: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=679272
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: bcfg2-server
Version: 1.0.1-3+squeeze1
Severity: critical
Tags: security, patch, pending

Quoting the upstream announcement (written by Chris St. Pierre):

"We have found a major security flaw in the Trigger plugin that would allow a
malicious user who has root access to a Bcfg2 client to run arbitrary commands
on the server as the user the bcfg2-server process is running as by passing a
malformed UUID.

This is very similar to a flaw discovered last year in a large number of other
plugins; this instance was not fixed at that time because Trigger uses a
different method to invoke external shell commands, and because Trigger
previously hid all errors from trigger scripts, so tests did not find the
issue.  As a side effect of this change, Trigger will begin reporting errors
from triggered scripts.

This only affects the Trigger plugin; if you are not using Trigger, you are
not affected by this flaw.  As a workaround, you can disable Trigger until you
are able to upgrade."

In Debian (and all other distros I know of) the bcfg2 server runs as
root, so in practice this is a remote root hole (limited to attackers
who can connect to the bcfg2 server (protected by a password and/or an
ssl key)).

-- 
Arto Jantunen

commit 8b0a5c5fc3ca99f6a2a8c393cedd02be66e6a846 (HEAD, squeeze-security)
Author: Arto Jantunen 
Date:   Wed Jun 27 12:00:08 2012 +0300

Backport upstream patch to fix unescaped shell command issues in the Trigger plugin

diff --git a/debian/patches/0005-Fix-unescaped-shell-commands-in-the-Trigger-plugin.patch b/debian/patches/0005-Fix-unescaped-shell-commands-in-the-Trigger-plugin.patch
new file mode 100644
index 000..fd58e79
--- /dev/null
+++ b/debian/patches/0005-Fix-unescaped-shell-commands-in-the-Trigger-plugin.patch
@@ -0,0 +1,69 @@
+From: Chris St. Pierre 
+Date: Tue, 12 Jun 2012 09:20:10 -0400
+Subject: [PATCH] Fix unescaped shell commands in the Trigger plugin
+
+---
+ src/lib/Server/Plugins/Trigger.py |   42 
+ 1 files changed, 28 insertions(+), 14 deletions(-)
+
+diff --git a/src/lib/Server/Plugins/Trigger.py b/src/lib/Server/Plugins/Trigger.py
+index b457431..5e6007e 100644
+--- a/src/lib/Server/Plugins/Trigger.py
 b/src/lib/Server/Plugins/Trigger.py
+@@ -1,17 +1,7 @@
+ import os
++import pipes
+ import Bcfg2.Server.Plugin
+-
+-
+-def async_run(prog, args):
+-pid = os.fork()
+-if pid:
+-os.waitpid(pid, 0)
+-else:
+-dpid = os.fork()
+-if not dpid:
+-os.system(" ".join([prog] + args))
+-os._exit(0)
+-
++from subprocess import Popen, PIPE
+ 
+ class Trigger(Bcfg2.Server.Plugin.Plugin,
+   Bcfg2.Server.Plugin.Statistics):
+@@ -27,9 +17,33 @@ class Trigger(Bcfg2.Server.Plugin.Plugin,
+ self.logger.error("Trigger: spool directory %s does not exist; unloading" % self.data)
+ raise Bcfg2.Server.Plugin.PluginInitError
+ 
++def async_run(self, args):
++pid = os.fork()
++if pid:
++os.waitpid(pid, 0)
++else:
++dpid = os.fork()
++if not dpid:
++self.debug_log("Running %s" % " ".join(pipes.quote(a)
++   for a in args))
++proc = Popen(args, stdin=PIPE, stdout=PIPE, stderr=PIPE)
++(out, err) = proc.communicate()
++rv = proc.wait()
++if rv != 0:
++self.logger.error("Trigger: Error running %s (%s): %s" %
++  (args[0], rv, err))
++elif err:
++self.debug_log("Trigger: Error: %s" % err)
++os._exit(0)
++
+ def process_statistics(self, metadata, _):
+ args = [metadata.hostname, '-p', metadata.profile, '-g',
+ ':'.join([g for g in metadata.groups])]
+ for notifier in os.listdir(self.data):
+-n = self.data + '/' + notifier
+-async_run(n, args)
++if ((notifier[-1] == '~') or
++(notifier[:2] == '.#') or
++(notifier[-4:] == '.swp') or
++(notifier in 

Processed: bug 674226 is forwarded to http://ball-trac.bioinf.uni-sb.de/ticket/455

[Debian Bug Tracking System]

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

> forwarded 674226 http://ball-trac.bioinf.uni-sb.de/ticket/455
Bug #674226 [src:ball] ball: FTBFS in sid: use of deleted function 
'BALL::String::String(const BALL::String&)'
Set Bug forwarded-to-address to 'http://ball-trac.bioinf.uni-sb.de/ticket/455'.
> thanks
Stopping processing here.

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

[Debian Bug Tracking System]

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

> tags 676633 pending
Bug #676633 [python-opencv] python-opencv: should depend on python-numpy
Added tag(s) pending.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
676633: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=676633
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: lmms: FTBFS: build-dependency not installable: libwine-dev

[Debian Bug Tracking System]

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

> tags 676760 +patch
Bug #676760 [src:lmms] lmms: FTBFS: build-dependency not installable: 
libwine-dev
Added tag(s) patch.
> thank you
Stopping processing here.

Please contact me if you need assistance.
-- 
676760: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=676760
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#676760: lmms: FTBFS: build-dependency not installable: libwine-dev

[Hilko Bengen]

tags 676760 +patch
thank you

The Wine packages have been modified to embrace multi-arch support. At
the moment, libwine and libwine-dev are only built for 32-bit
architectures. I am working on changing that, but it won't help much in
the case of lmms: When I tried to build lmms with a locally-built amd64
version of libwine-dev, it was not recognized. Apparently, the build
system only looks for 32-bit libwine.

The best advice for users who want to use the particular plugins on an
amd64 machine is probably going to be: "Set up i386 as a secondary
architecture and Install lmms:i386".

The attached patch disables the dependency and the build dependency for
amd64. (I don't see why it should not work on kfreebsd-i386, so I have
replaced i386 with any-i386.) I am going to NMU this shortly.

Cheers,
-Hilko

diff --git a/debian/control b/debian/control
index c4e315f..453fcf4 100644
--- a/debian/control
+++ b/debian/control
@@ -1,15 +1,15 @@
 Source: lmms
 Section: sound
 Priority: optional
 Maintainer: Patrick Winnertz 
-Build-Depends: debhelper (>= 5.0.0), libsdl-sound1.2-dev, libsamplerate0-dev, libsndfile1-dev, libvorbis-dev, libjack-dev, libstk0-dev, ladspa-sdk, libflac-dev, libwine-dev [i386 amd64], libasound2-dev [linux-any], festival-dev, imagemagick, cmake, qt4-qmake, libqt4-dev, libpulse-dev, libfluidsynth-dev, libfftw3-dev, libfreetype6-dev, libxft-dev, portaudio19-dev, libxinerama-dev, gcc-multilib [amd64], g++-multilib [amd64]
+Build-Depends: debhelper (>= 5.0.0), libsdl-sound1.2-dev, libsamplerate0-dev, libsndfile1-dev, libvorbis-dev, libjack-dev, libstk0-dev, ladspa-sdk, libflac-dev, libwine-dev [any-i386], libasound2-dev [linux-any], festival-dev, imagemagick, cmake, qt4-qmake, libqt4-dev, libpulse-dev, libfluidsynth-dev, libfftw3-dev, libfreetype6-dev, libxft-dev, portaudio19-dev, libxinerama-dev, gcc-multilib [amd64], g++-multilib [amd64]
 Standards-Version: 3.9.1
 Homepage: http://lmms.sf.net/
 
 Package: lmms
 Architecture: any
-Depends: lmms-common (= ${source:Version}) , ${shlibs:Depends}, ${misc:Depends}, stk, wine-bin [i386 amd64]
+Depends: lmms-common (= ${source:Version}) , ${shlibs:Depends}, ${misc:Depends}, stk, wine-bin [any-i386]
 Recommends: tap-plugins, caps
 Suggests: fil-plugins, mcp-plugins, omins, vcf, freepats
 Description: Linux Multimedia Studio
  LMMS aims to be a free alternative to popular (but commercial and closed-

Bug#679322: pdksh: add NEWS file for mksh transition

[Thorsten Glaser]

Package: pdksh
Severity: serious
Tags: pending

As discussed in IRC today, pdksh symlinked to lksh should not
transition to testing without a NEWS file detailing the transition
and that users shall switch to mksh as login shell since lksh
is not intended for interactive use.

Will tackle this ASAP together with fixes for some more remaining
issues, having reviewed the old pdksh bugs today.



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

Bug#679320: elecctric-fence: FTBFS: testsuite timeout

[Christoph Egger]

Package: src:electric-fence
Version: 2.2.1
Severity: serious
Tags: sid wheezy
Justification: fails to build from source (but built successfully in the past)

Hi!

Your package failed to build on the buildds:

rm -f eftest
cc -g -O2 -DUSE_SEMAPHORE -fPIC eftest.o libefence.a -o eftest -lpthread

Testing Electric Fence.
After the last test, it should print that the test has PASSED.
./eftest

  Electric Fence 2.2 Copyright (C) 1987-1999 Bruce Perens 
./tstheap 3072

  Electric Fence 2.2 Copyright (C) 1987-1999 Bruce Perens 
make[1]: *** [all] Killed
make: *** [build-stamp] Error 2

Full build log at
https://buildd.debian.org/status/fetch.php?pkg=electric-fence&arch=amd64&ver=2.2.1&stamp=1340781370

Regards

Christoph

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



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

Bug#679318: flumotion: twisted override bug - one more

[John Bazik]

Package: flumotion
Version: 0.10.0-2
Severity: grave
Tags: upstream patch
Justification: renders package unusable

This is the same problem I reported in #672404, but affecting a different
part of the code (there are two places that need to be fixed).  To recap,
flumotion overrides an internal method in twisted, which has changed.

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

Kernel: Linux 3.2.0-2-amd64 (SMP w/6 CPU cores)
Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968)
Shell: /bin/sh linked to /bin/dash
diff -ur a/flumotion/twisted/fdserver.py b/flumotion/twisted/fdserver.py
--- a/flumotion/twisted/fdserver.py	2011-10-07 06:10:58.0 -0400
+++ b/flumotion/twisted/fdserver.py	2012-06-15 10:55:46.344267000 -0400
@@ -173,7 +173,7 @@
 class _SocketMaybeCloser(tcp._SocketCloser):
 keepSocketAlive = False
 
-def _closeSocket(self):
+def _closeSocket(self, orderly):
 # We override this (from tcp._SocketCloser) so that we can close
 # sockets properly in the normal case, but once we've passed our
 # socket on via the FD-channel, we just close() it (not calling

Bug#679317: tarantool: FTBFS[kfreebsd]: undefined reference to `clock_gettime'

[Christoph Egger]

Package: src:tarantool
Version: 1.4.6+20120626-1
Severity: serious
Tags: sid wheezy
User: debian-...@lists.debian.org
Usertags: kfreebsd
X-Debbugs-Cc: debian-...@lists.debian.org
Justification: fails to build from source (but built successfully in the past)

Hi!

Your package failed to build on the kfreebsd-* buildds:

cd 
/build/buildd-tarantool_1.4.6+20120626-1-kfreebsd-amd64-EsdFxn/tarantool-1.4.6+20120626/build-area/mod/box
 && /usr/bin/cmake -E cmake_link_script CMakeFiles/tarantool_box.dir/link.txt 
--verbose=1
/usr/bin/c++   -g -O2 -fstack-protector --param=ssp-buffer-size=4 -Wformat 
-Werror=format-security -g -O2 -fstack-protector --param=ssp-buffer-size=4 
-Wformat -Werror=format-security 
-I/build/buildd-tarantool_1.4.6+20120626-1-kfreebsd-amd64-EsdFxn/tarantool-1.4.6+20120626/build-area/third_party/luajit/src
 -D_GNU_SOURCE -D_FILE_OFFSET_BITS=64 -DCORO_ASM -fno-omit-frame-pointer 
-fno-stack-protector -fexceptions -funwind-tables -fexceptions 
-fobjc-exceptions -fgnu89-inline   -Wl,-z,relro -pthread 
CMakeFiles/tarantool_box.dir/tuple.m.o CMakeFiles/tarantool_box.dir/index.m.o 
CMakeFiles/tarantool_box.dir/tree.m.o CMakeFiles/tarantool_box.dir/space.m.o 
CMakeFiles/tarantool_box.dir/port.m.o CMakeFiles/tarantool_box.dir/request.m.o 
CMakeFiles/tarantool_box.dir/txn.m.o CMakeFiles/tarantool_box.dir/box.m.o 
CMakeFiles/tarantool_box.dir/box.lua.c.o 
CMakeFiles/tarantool_box.dir/box_lua.m.o 
CMakeFiles/tarantool_box.dir/memcached.m.o 
CMakeFiles/tarantool_box.dir/__/__/cfg/tarantool_box_cfg.c.o  -o tarantool_box  
libltbox.a ../../cfg/libcfg.a ../../src/libcore.a ../../src/libev.a 
../../third_party/coro/libcoro.a ../../third_party/gopt/libgopt.a 
../../third_party/libmisc.a -lobjc ../../third_party/luajit/src/libluajit.a 
-lpthread -ldl -lbfd -liberty -lm 
../../src/libev.a(tarantool_ev.c.o): In function `ev_time':
/build/buildd-tarantool_1.4.6+20120626-1-kfreebsd-amd64-EsdFxn/tarantool-1.4.6+20120626/third_party/libev/ev.c:1295:
 undefined reference to `clock_gettime'
../../src/libev.a(tarantool_ev.c.o): In function `get_clock':
/build/buildd-tarantool_1.4.6+20120626-1-kfreebsd-amd64-EsdFxn/tarantool-1.4.6+20120626/third_party/libev/ev.c:1313:
 undefined reference to `clock_gettime'
/build/buildd-tarantool_1.4.6+20120626-1-kfreebsd-amd64-EsdFxn/tarantool-1.4.6+20120626/third_party/libev/ev.c:1313:
 undefined reference to `clock_gettime'
/build/buildd-tarantool_1.4.6+20120626-1-kfreebsd-amd64-EsdFxn/tarantool-1.4.6+20120626/third_party/libev/ev.c:1313:
 undefined reference to `clock_gettime'
/build/buildd-tarantool_1.4.6+20120626-1-kfreebsd-amd64-EsdFxn/tarantool-1.4.6+20120626/third_party/libev/ev.c:1313:
 undefined reference to `clock_gettime'
../../src/libev.a(tarantool_ev.c.o):/build/buildd-tarantool_1.4.6+20120626-1-kfreebsd-amd64-EsdFxn/tarantool-1.4.6+20120626/third_party/libev/ev.c:2240:
 more undefined references to `clock_gettime' follow
collect2: error: ld returned 1 exit status
make[3]: *** [mod/box/tarantool_box] Error 1

Full build log at
https://buildd.debian.org/status/fetch.php?pkg=tarantool&arch=kfreebsd-amd64&ver=1.4.6%2B20120626-1&stamp=1340804405

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#679316: starplot: FTBFS: No rule to make target `all'. Stop.

[Christoph Egger]

Package: src:starplot
Version: 0.95.5-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:

 fakeroot debian/rules clean
dh_testdir
dh_testroot
# Add here commands to clean up after the build process.
[ ! -f Makefile ] || /usr/bin/make distclean
rm -f build-stamp configure-stamp config.status config.log
dh_clean
 debian/rules build-arch
dh_testdir
# Add here commands to compile the package.
/usr/bin/make all CFLAGS="-Wall -pedantic -O2 -g" CXXFLAGS="-Wall -pedantic -O2 
-g" \
INSTALLPGM= \
docdir=/usr/share/doc/starplot mandir=/usr/share/man 
sysconfdir=/etc
make[1]: *** No rule to make target `all'.  Stop.
make[1]: Entering directory 
`/build/buildd-starplot_0.95.5-5-kfreebsd-amd64-Qf7IoR/starplot-0.95.5'
make[1]: Leaving directory 
`/build/buildd-starplot_0.95.5-5-kfreebsd-amd64-Qf7IoR/starplot-0.95.5'
make: *** [build-stamp] Error 2
dpkg-buildpackage: error: debian/rules build-arch gave error exit status 2

Full build log at
https://buildd.debian.org/status/fetch.php?pkg=starplot&arch=kfreebsd-amd64&ver=0.95.5-5&stamp=1340824563

Regards

Christoph

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



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

Bug#679315: openmeeg: FTBFS[kfreebsd-i386]: testsuite failure

[Christoph Egger]

Package: src:openmeeg
Version: 2.0.0.dfsg-5
Severity: serious
Tags: sid wheezy
User: debian-...@lists.debian.org
Usertags: kfreebsd
X-Debbugs-Cc: debian-...@lists.debian.org
Justification: fails to build from source (but built successfully in the past)

Hi!

Your package failed to build on the kfreebsd-i386 buildds:

35% tests passed, 121 tests failed out of 186

Total Test time (real) =  91.16 sec

The following tests FAILED:
 17 - SurfGainMEG-Head1 (ILLEGAL)
 18 - ESTMEG-Head1 (OTHER_FAULT)
 19 - MEG-HEAT-Head1 (OTHER_FAULT)
 20 - MEG-MN-Head1 (OTHER_FAULT)
 21 - MEG-TV-Head1 (OTHER_FAULT)
 29 - DipGainMEG-Head1 (ILLEGAL)
 30 - DipGainMEG-Head1-tangential (ILLEGAL)
 31 - DipGainMEG-Head1-noradial (ILLEGAL)
 32 - DipGainInternalPot-Head1 (ILLEGAL)
 34 - MEG-dipoles-Head1 (OTHER_FAULT)
 35 - MEG-dipoles-Head1-tangential (OTHER_FAULT)
 36 - MEG-dipoles-Head1-noradial (OTHER_FAULT)
 37 - InternalPot-dipoles-Head1 (OTHER_FAULT)
 50 - DipGainEEG-Head2 (ILLEGAL)
 51 - DipGainMEG-Head2 (ILLEGAL)
 52 - DipGainMEG-Head2-tangential (ILLEGAL)
 53 - DipGainMEG-Head2-noradial (ILLEGAL)
 54 - DipGainInternalPot-Head2 (ILLEGAL)
 55 - EEG-dipoles-Head2 (OTHER_FAULT)
 56 - MEG-dipoles-Head2 (OTHER_FAULT)
 57 - MEG-dipoles-Head2-tangential (OTHER_FAULT)
 58 - MEG-dipoles-Head2-noradial (OTHER_FAULT)
 59 - InternalPot-dipoles-Head2 (OTHER_FAULT)
 72 - cmp-SurfGainMEG-Head1 (OTHER_FAULT)
 73 - cmp-MEGEST-Head1 (OTHER_FAULT)
 74 - cmp-MEG-HEAT-Head1 (OTHER_FAULT)
 75 - cmp-MEG-MN-Head1 (OTHER_FAULT)
 76 - cmp-MEG-TV-Head1 (OTHER_FAULT)
 79 - cmp-EEGEST-dip-Head2-dip1-mag (OTHER_FAULT)
 80 - cmp-EEGEST-dip-Head2-dip1-rdm (OTHER_FAULT)
 83 - cmp-EEGEST-dip-Head2-dip2-mag (OTHER_FAULT)
 84 - cmp-EEGEST-dip-Head2-dip2-rdm (OTHER_FAULT)
 87 - cmp-EEGEST-dip-Head2-dip3-mag (OTHER_FAULT)
 88 - cmp-EEGEST-dip-Head2-dip3-rdm (OTHER_FAULT)
 91 - cmp-EEGEST-dip-Head2-dip4-mag (OTHER_FAULT)
 92 - cmp-EEGEST-dip-Head2-dip4-rdm (OTHER_FAULT)
 95 - cmp-EEGEST-dip-Head2-dip5-mag (OTHER_FAULT)
 96 - cmp-EEGEST-dip-Head2-dip5-rdm (OTHER_FAULT)
 98 - EITvalidation-dipoles-Head2 (ILLEGAL)
 99 - cmp-EEGinternal-dip-Head1-dip1 (OTHER_FAULT)
101 - cmp-EEGinternal-dip-Head2-dip1 (OTHER_FAULT)
102 - cmp-EIT-Head2-dip1 (OTHER_FAULT)
103 - cmp-EEGinternal-dip-Head1-dip2 (OTHER_FAULT)
105 - cmp-EEGinternal-dip-Head2-dip2 (OTHER_FAULT)
106 - cmp-EIT-Head2-dip2 (OTHER_FAULT)
107 - cmp-EEGinternal-dip-Head1-dip3 (OTHER_FAULT)
109 - cmp-EEGinternal-dip-Head2-dip3 (OTHER_FAULT)
110 - cmp-EIT-Head2-dip3 (OTHER_FAULT)
111 - cmp-EEGinternal-dip-Head1-dip4 (OTHER_FAULT)
113 - cmp-EEGinternal-dip-Head2-dip4 (OTHER_FAULT)
114 - cmp-EIT-Head2-dip4 (OTHER_FAULT)
115 - cmp-EEGinternal-dip-Head1-dip5 (OTHER_FAULT)
117 - cmp-EEGinternal-dip-Head2-dip5 (OTHER_FAULT)
118 - cmp-EIT-Head2-dip5 (OTHER_FAULT)
119 - cmp-MEGEST-dip-Head1-dip1-mag (OTHER_FAULT)
120 - cmp-MEGEST-dip-Head1-dip1-rdm (OTHER_FAULT)
121 - cmp-MEGEST-dip-Head1-dip2-mag (OTHER_FAULT)
122 - cmp-MEGEST-dip-Head1-dip2-rdm (OTHER_FAULT)
123 - cmp-MEGEST-dip-Head1-dip3-mag (OTHER_FAULT)
124 - cmp-MEGEST-dip-Head1-dip3-rdm (OTHER_FAULT)
125 - cmp-MEGEST-dip-Head1-dip4-mag (OTHER_FAULT)
126 - cmp-MEGEST-dip-Head1-dip4-rdm (OTHER_FAULT)
127 - cmp-MEGEST-dip-Head1-dip5-mag (OTHER_FAULT)
128 - cmp-MEGEST-dip-Head1-dip5-rdm (OTHER_FAULT)
129 - cmp-MEGEST-dip-Head1-dip6 (OTHER_FAULT)
130 - cmp-MEGEST-dip-Head2-dip1-mag (OTHER_FAULT)
131 - cmp-MEGEST-dip-Head2-dip1-rdm (OTHER_FAULT)
132 - cmp-MEGEST-dip-Head2-dip2-mag (OTHER_FAULT)
133 - cmp-MEGEST-dip-Head2-dip2-rdm (OTHER_FAULT)
134 - cmp-MEGEST-dip-Head2-dip3-mag (OTHER_FAULT)
135 - cmp-MEGEST-dip-Head2-dip3-rdm (OTHER_FAULT)
136 - cmp-MEGEST-dip-Head2-dip4-mag (OTHER_FAULT)
137 - cmp-MEGEST-dip-Head2-dip4-rdm (OTHER_FAULT)
138 - cmp-MEGEST-dip-Head2-dip5-mag (OTHER_FAULT)
139 - cmp-MEGEST-dip-Head2-dip5-rdm (OTHER_FAULT)
140 - cmp-MEGEST-dip-Head2-dip6 (OTHER_FAULT)
141 - cmp-MEGEST-dip-Head1-dip1-tangential-mag (OTHER_FAULT)
142 - cmp-MEGEST-dip-Head1-dip1-tangential-rdm (OTHER_FAULT)
143 - cmp-MEGEST-dip-Head1-dip2-tangential-mag (OTHER_FAULT)
144 - cmp-MEGEST-dip-Head1-dip2-tangential-rdm (OTHER_FAULT)
145 - cmp-MEGEST-dip-Head1-dip3-tangential-mag (OTHER_FAULT)
146 - cmp-MEGEST-dip-Head1-dip3-tangential-rdm (OTHER_FAULT)
147 - cmp-MEGEST-dip-Head1-dip4-tangential-mag (OTHER_FAULT)
148 - cmp-MEGEST-

Bug#679313: goobox: FTBFS: syntax error near unexpected token `maximum'

[Christoph Egger]

Package: src:goobox
Version: 3.0.1-1.1
Severity: serious
Tags: sid wheezy
Justification: fails to build from source (but built successfully in the past)

Hi!

Your package failed to build on the buildds:

checking for pkg-config... /usr/bin/pkg-config
checking pkg-config is at least version 0.9.0... yes
checking gnome-doc-utils >= 0.3.2... yes
./configure: line 15406: syntax error near unexpected token `maximum'
./configure: line 15406: `GNOME_COMPILE_WARNINGS(maximum)'
make: *** [config.status] Error 2
dpkg-buildpackage: error: debian/rules build-arch gave error exit status 2

Full build log at
https://buildd.debian.org/status/fetch.php?pkg=goobox&arch=i386&ver=3.0.1-1.1&stamp=1340748790

Regards

Christoph

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



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

Bug#679311: brasero: FTBFS[kfreebsd]: symbol delta

[Christoph Egger]

Package: src:brasero
Version: 3.4.1-1
Severity: serious
Tags: sid wheezy
User: debian-...@lists.debian.org
Usertags: kfreebsd
X-Debbugs-Cc: debian-...@lists.debian.org
Justification: fails to build from source (but built successfully in the past)

Hi!

Your package failed to build on the kfreebsd-* buildds:

dh_compress -pbrasero-cdrkit  
dh_fixperms -pbrasero-cdrkit  
dh_makeshlibs -pbrasero-cdrkit  --no-act
dh_strip -plibbrasero-media3-1  
dh_compress -plibbrasero-media3-1  
dh_fixperms -plibbrasero-media3-1  
dh_makeshlibs -plibbrasero-media3-1  -V 'libbrasero-media3-1 (>= 3.0.0)' 
-Xplugins -- -c4
dpkg-gensymbols: warning: some symbols or patterns disappeared in the symbols 
file: see diff output below
dpkg-gensymbols: warning: debian/libbrasero-media3-1/DEBIAN/symbols doesn't 
match completely debian/libbrasero-media3-1.symbols
--- debian/libbrasero-media3-1.symbols 
(libbrasero-media3-1_3.4.1-1_kfreebsd-i386)
+++ dpkg-gensymbolsftlW5e   2012-06-25 20:16:08.0 +
@@ -177,11 +177,11 @@
  brasero_dest_selection_set_session@Base 3.0.0
  brasero_drive_properties_get_type@Base 3.0.0
  brasero_drive_properties_new@Base 3.0.0
- brasero_file_monitor_directory_contents@Base 3.0.0
- brasero_file_monitor_foreach_cancel@Base 3.0.0
- brasero_file_monitor_get_type@Base 3.0.0
- brasero_file_monitor_reset@Base 3.0.0
- brasero_file_monitor_single_file@Base 3.0.0
+#MISSING: 3.4.1-1# brasero_file_monitor_directory_contents@Base 3.0.0
+#MISSING: 3.4.1-1# brasero_file_monitor_foreach_cancel@Base 3.0.0
+#MISSING: 3.4.1-1# brasero_file_monitor_get_type@Base 3.0.0
+#MISSING: 3.4.1-1# brasero_file_monitor_reset@Base 3.0.0
+#MISSING: 3.4.1-1# brasero_file_monitor_single_file@Base 3.0.0
  brasero_file_node_add@Base 3.0.0
  brasero_file_node_check_imported_sibling@Base 3.0.0
  brasero_file_node_check_name_existence@Base 3.0.0
dh_makeshlibs: dpkg-gensymbols -plibbrasero-media3-1 
-Idebian/libbrasero-media3-1.symbols -Pdebian/libbrasero-media3-1 
-edebian/libbrasero-media3-1/usr/lib/libbrasero-burn3.so.1.2.3
 -edebian/libbrasero-media3-1/usr/lib/libbrasero-media3.so.1.2.3
 -edebian/libbrasero-media3-1/usr/lib/libbrasero-utils3.so.1.2.3
 -c4 returned exit code 1
make: *** [binary-fixup/libbrasero-media3-1] Error 1

Full build log at
https://buildd.debian.org/status/fetch.php?pkg=brasero&arch=kfreebsd-i386&ver=3.4.1-1&stamp=1340655382

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#678902: proposed sgml-base 1.16+nmu4 fixing #676717 and #678902

[Helmut Grohne]

Here is my next attempt to fixing #676717 and #678902.

I incorporated the parser Jakub Wilk proposed and tested it on a variety
of catalog files. See the discussion on #676717 for why update-catalog
is starting to parse catalog files.

In addition I added a Pre-Dependency on dpkg >= 1.16.4 to close #678902.
Which highlights that the fixed dpkg trigger bug #675613, #676061,
#676062, #676107, #676118, #676122 still shows up. As per policy section
7.2 I raise this Pre-Depends on -devel. 

So the attached NMU is to fix all the known issues that have come up as
a result of fixing #88010. Comments welcome.

Please CC my in replies as I am not subscribed to -devel.

Helmut
diff -Nru sgml-base-1.26+nmu3/debian/changelog 
sgml-base-1.26+nmu4/debian/changelog
--- sgml-base-1.26+nmu3/debian/changelog2012-05-28 21:11:52.0 
+0200
+++ sgml-base-1.26+nmu4/debian/changelog2012-06-27 21:04:29.0 
+0200
@@ -1,3 +1,16 @@
+sgml-base (1.26+nmu4) unstable; urgency=low
+
+  * Non-maintainer upload.
+  * update-catalog --update-super ignores catalogs referencing non-existent
+files. (Closes: #676717) Thanks to Jakub Wilk for contributing the parser.
+  * Remove warning about rebuilding packages as it may confuse users.
+  * Quieten update-catalog during trigger and postinst, to avoid warnings for
+packages in "rc" state.
+  * Pre-Depend on dpkg >= 1.16.4 (Closes: #678902). Removed dependency on
+dpkg >= 1.14.18. sgml-base highlights a bug in dpkg's trigger processing. 
+
+ -- Helmut Grohne   Thu, 21 Jun 2012 16:09:07 +0200
+
 sgml-base (1.26+nmu3) unstable; urgency=low
 
   * Non-maintainer upload.
diff -Nru sgml-base-1.26+nmu3/debian/control sgml-base-1.26+nmu4/debian/control
--- sgml-base-1.26+nmu3/debian/control  2012-05-28 13:58:23.0 +0200
+++ sgml-base-1.26+nmu4/debian/control  2012-06-27 20:38:49.0 +0200
@@ -11,7 +11,8 @@
 Priority: optional
 Architecture: all
 Conflicts: sgml-data (<= 0.02), sgmltools-2 (<= 2.0.2-4)
-Depends: ${perl:Depends}, dpkg (>= 1.14.18)
+Depends: ${perl:Depends}
+Pre-Depends: dpkg (>= 1.16.4)
 Suggests: sgml-base-doc
 Description: SGML infrastructure and SGML catalog file support
  This package creates the SGML infrastructure directories and provides
diff -Nru sgml-base-1.26+nmu3/debian/sgml-base.postinst 
sgml-base-1.26+nmu4/debian/sgml-base.postinst
--- sgml-base-1.26+nmu3/debian/sgml-base.postinst   2012-05-28 
13:58:23.0 +0200
+++ sgml-base-1.26+nmu4/debian/sgml-base.postinst   2012-06-22 
17:22:31.0 +0200
@@ -61,12 +61,12 @@
 fi
 
 ## --
-update-catalog --update-super
+update-catalog --quiet --update-super
 ln -sf /var/lib/sgml-base/supercatalog /etc/sgml/catalog
 fi
 if [ "$1" = "triggered" ]
 then
-update-catalog --update-super
+update-catalog --quiet --update-super
 fi
 
 ## -- 
diff -Nru sgml-base-1.26+nmu3/tools/update-catalog 
sgml-base-1.26+nmu4/tools/update-catalog
--- sgml-base-1.26+nmu3/tools/update-catalog2012-05-28 21:11:52.0 
+0200
+++ sgml-base-1.26+nmu4/tools/update-catalog2012-06-27 21:04:45.0 
+0200
@@ -4,6 +4,7 @@
 ## --
 ## Copyright (c) 2001-2004 Ardo van Rangelrooij
 ## Copyright (c) 2012 Helmut Grohne
+## Copyright (c) 2012 Jakub Wilk
 ##
 ## This is free software; see the GNU General Public Licence version 2
 ## or later for copying conditions.  There is NO warranty.
@@ -138,8 +139,6 @@
 print "Invocation of dpkg-trigger failed with status $?.\n";
 print "Forcing update of the super catalog...\n";
 &update_super;
-} else {
-print "update-catalog: Please rebuild the package being set up with a 
version of debhelper fixing #477751.\n";
 }
 }
 elsif ( $add )
@@ -240,17 +239,71 @@
 }
 
 ## --
+# Reference: https://www.oasis-open.org/specs/a401.htm
+sub check_catalog($)
+{
+my($catalog)=shift;
+my $base = $catalog;
+$base =~ s,/[^/]+$,,;
+my $catalog_tokens = qr{
+( (?: \s+ | -- .*? --)+ # whitespace and comments
+| ' .*? ' | " .*? " # literal
+| \S+ # other tokens
+)
+}sx;
+unless(open(PKGCAT, "<", $catalog)) {
+print "Warning: Ignoring unreadable catalog file `$catalog'.\n"
+unless $quiet;
+return 0;
+};
+local $/;
+my $contents = ;
+close PKGCAT;
+my $prevtoken = 0;
+while ($contents =~ m/$catalog_tokens/g) {
+my $token = $1;
+if ($prevtoken) {
+next if $token =~ m/^\s|^--/;
+$token =~ s/^(['"])(.*)\1$/$2/;
+if($prevtoken eq 'base') {
+$base = $token;
+} elsif($prevtoken eq 'catalog') {
+my $path;
+if($token =~ m,^/,) 

Bug#679307: remctl: FTBFS in parallel mode: PHP module link error

[Aaron M. Ucko]

Source: remctl
Version: 3.2-1
Severity: serious
Justification: fails to build from source (but built successfully in the past)

Hi, Russ.

Parallel builds of remctl are failing because the PHP module tries to
link against -lremctl before it becomes available:

  libtool: link: cc -shared  -fPIC -DPIC  .libs/php_remctl.o   
-L/.../remctl-3.2/client/.libs -lremctl  -O2 -Wl,-z -Wl,relro -Wl,-z -Wl,now 
-Wl,--as-needed   -Wl,-soname -Wl,remctl.so -o .libs/remctl.so
  /usr/bin/ld: cannot find -lremctl
  collect2: error: ld returned 1 exit status
  make[4]: *** [remctl.la] Error 1
  make[4]: Leaving directory `/.../remctl-3.2/php'
  make[3]: *** [php/modules/remctl.so] Error 2

Could you please either declare a suitable internal dependency or stop
passing --parallel to dh?

Thanks!



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

Bug#679242: wvdial: Failed assertion on startup

[green]

Package: wvdial
Version: 1.61-4.1
Followup-For: Bug #679242

Same problem here, with a ThinkPad T61 and sl-modem-daemon.

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

Kernel: Linux 3.2.0-2-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 wvdial depends on:
ii  debconf [debconf-2.0]   1.5.43
ii  libc6   2.13-33
ii  libgcc1 1:4.7.0-8
ii  libstdc++6  4.7.0-8
ii  libuniconf4.6   4.6.1-4
ii  libwvstreams4.6-base4.6.1-4
ii  libwvstreams4.6-extras  4.6.1-4
ii  ppp 2.4.5-5.1+b1

wvdial recommends no packages.

wvdial suggests no packages.

-- Configuration Files:
/etc/ppp/peers/wvdial [Errno 13] Permission denied: u'/etc/ppp/peers/wvdial'
/etc/ppp/peers/wvdial-pipe [Errno 13] Permission denied: 
u'/etc/ppp/peers/wvdial-pipe'

-- debconf information:
* wvdial/wvdialconf: true
* wvdial/phone:
  wvdial/passphrases_mismatch:
* wvdial/login:

-- /etc/wvdial.conf applicable entries:
Init1 = ATZ
Init2 = ATQ0 V1 E1 S0=0 &C1 &D2 +FCLASS=0
Init3 = AT+MS=34
Modem Type = Analog Modem
Phone = nn
ISDN = 0
Username = 'username'
Password = 'password'
Modem = /dev/ttySL0
Baud = 460800
Carrier Check = no


signature.asc
Description: Digital signature

Processed: tagging 660260

[Debian Bug Tracking System]

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

> # just to make it clear it still FTBFS, but luckily upstream is working on it
> tags 660260 + confirmed
Bug #660260 [src:gnudatalanguage] gnudatalanguage: FTBFS since plplot uses 
-fvisibility=hidden
Bug #669497 [src:gnudatalanguage] gnudatalanguage: FTBFS: 
plotting_xyouts.cpp:260: undefined reference to `plP_mmpcy'
Added tag(s) confirmed.
Added tag(s) confirmed.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
660260: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=660260
669497: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=669497
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#675971: what should we be doing?

[Chris Knadle]

On Wednesday, June 27, 2012 08:59:25, Chris Knadle wrote:
...
> On Wheezy, after doing a checkout of v1.2.3-348-g317f5a0-1 I'm unable to
> get the package to build because there's no source tarball and debuild
> reports that it can't build source format 3.0 (quilt) if the source
> tarball is missing.  Do you have the source tarball for 1.2.3-348-g317f5a0
> at a web accessible location somewhere?

nevermind, 'apt-get source mumble' gets the necessary tarball.



I've re-read what you had written to at least try to understand what options 
there there might be.

If possible, I'd like some clarification on what the "zero-ice snafu" in the 
following statement means:

On Tuesday, June 19, 2012 04:58:38, Ron wrote:
...
> Given the general state of things, including the zeroc-ice snafu of
> breaking ABI to "fix the build with gcc 4.7", and the time we have
> remaining before the freeze, I'm having a very hard time seeing how this
> might possibly be a viable release candidate for Wheezy anyway at this
> stage.

  -- Chris

--
Chris Knadle
chris.kna...@coredump.us



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

Bug#674337: marked as done (ruby-bio: FTBFS: test failed)

[Debian Bug Tracking System]

Your message dated Wed, 27 Jun 2012 18:34:53 +
with message-id 
and subject line Bug#674337: fixed in ruby-bio 1.4.2-3
has caused the Debian Bug report #674337,
regarding ruby-bio: FTBFS: test failed
to be marked as done.

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

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


-- 
674337: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=674337
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: ruby-bio
Version: 1.4.2-2
Severity: serious
Tags: wheezy sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20120524 qa-ftbfs
Justification: FTBFS on amd64

Hi,

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

Relevant part:
> make[1]: Entering directory `/«PKGBUILDDIR»'
> dh_auto_install
>   Entering dh_ruby --install
> install -d /«PKGBUILDDIR»/debian/ruby-bio/usr/bin
> install -D -m755 bin/br_bioflat.rb 
> /«PKGBUILDDIR»/debian/ruby-bio/usr/bin/br_bioflat.rb
> install -D -m755 bin/bioruby /«PKGBUILDDIR»/debian/ruby-bio/usr/bin/bioruby
> install -D -m755 bin/br_biogetseq.rb 
> /«PKGBUILDDIR»/debian/ruby-bio/usr/bin/br_biogetseq.rb
> install -D -m755 bin/br_biofetch.rb 
> /«PKGBUILDDIR»/debian/ruby-bio/usr/bin/br_biofetch.rb
> install -D -m755 bin/br_pmfetch.rb 
> /«PKGBUILDDIR»/debian/ruby-bio/usr/bin/br_pmfetch.rb
> install -d /«PKGBUILDDIR»/debian/ruby-bio/usr/lib/ruby/vendor_ruby
> install -D -m644 lib/bio/shell/object.rb 
> /«PKGBUILDDIR»/debian/ruby-bio/usr/lib/ruby/vendor_ruby/bio/shell/object.rb
> install -D -m644 lib/bio/shell/irb.rb 
> /«PKGBUILDDIR»/debian/ruby-bio/usr/lib/ruby/vendor_ruby/bio/shell/irb.rb
> install -D -m644 lib/bio/shell/setup.rb 
> /«PKGBUILDDIR»/debian/ruby-bio/usr/lib/ruby/vendor_ruby/bio/shell/setup.rb
> install -D -m644 lib/bio/shell/web.rb 
> /«PKGBUILDDIR»/debian/ruby-bio/usr/lib/ruby/vendor_ruby/bio/shell/web.rb
> install -D -m644 lib/bio/shell/interface.rb 
> /«PKGBUILDDIR»/debian/ruby-bio/usr/lib/ruby/vendor_ruby/bio/shell/interface.rb
> install -D -m644 lib/bio/shell/core.rb 
> /«PKGBUILDDIR»/debian/ruby-bio/usr/lib/ruby/vendor_ruby/bio/shell/core.rb
> install -D -m644 
> lib/bio/shell/rails/vendor/plugins/bioruby/generators/bioruby/templates/_methods.rhtml
>  
> /«PKGBUILDDIR»/debian/ruby-bio/usr/lib/ruby/vendor_ruby/bio/shell/rails/vendor/plugins/bioruby/generators/bioruby/templates/_methods.rhtml
> install -D -m644 
> lib/bio/shell/rails/vendor/plugins/bioruby/generators/bioruby/templates/_modules.rhtml
>  
> /«PKGBUILDDIR»/debian/ruby-bio/usr/lib/ruby/vendor_ruby/bio/shell/rails/vendor/plugins/bioruby/generators/bioruby/templates/_modules.rhtml
> install -D -m644 
> lib/bio/shell/rails/vendor/plugins/bioruby/generators/bioruby/templates/bioruby_controller.rb
>  
> /«PKGBUILDDIR»/debian/ruby-bio/usr/lib/ruby/vendor_ruby/bio/shell/rails/vendor/plugins/bioruby/generators/bioruby/templates/bioruby_controller.rb
> install -D -m644 
> lib/bio/shell/rails/vendor/plugins/bioruby/generators/bioruby/templates/bioruby-link.gif
>  
> /«PKGBUILDDIR»/debian/ruby-bio/usr/lib/ruby/vendor_ruby/bio/shell/rails/vendor/plugins/bioruby/generators/bioruby/templates/bioruby-link.gif
> install -D -m644 
> lib/bio/shell/rails/vendor/plugins/bioruby/generators/bioruby/templates/bioruby.rhtml
>  
> /«PKGBUILDDIR»/debian/ruby-bio/usr/lib/ruby/vendor_ruby/bio/shell/rails/vendor/plugins/bioruby/generators/bioruby/templates/bioruby.rhtml
> install -D -m644 
> lib/bio/shell/rails/vendor/plugins/bioruby/generators/bioruby/templates/commands.rhtml
>  
> /«PKGBUILDDIR»/debian/ruby-bio/usr/lib/ruby/vendor_ruby/bio/shell/rails/vendor/plugins/bioruby/generators/bioruby/templates/commands.rhtml
> install -D -m644 
> lib/bio/shell/rails/vendor/plugins/bioruby/generators/bioruby/templates/history.rhtml
>  
> /«PKGBUILDDIR»/debian/ruby-bio/usr/lib/ruby/vendor_ruby/bio/shell/rails/vendor/plugins/bioruby/generators/bioruby/templates/history.rhtml
> install -D -m644 
> lib/bio/shell/rails/vendor/plugins/bioruby/generators/bioruby/templates/_classes.rhtml
>  
> /«PKGBUILDDIR»/debian/ruby-bio/usr/lib/ruby/vendor_ruby/bio/shell/rails/vendor/plugins/bioruby/generators/bioruby/templates/_classes.rhtml
> install -D -m644 
> lib/bio/shell/rails/vendor/plugins/bioruby/generators/bioruby/templates/spinner.gif
>  
> /«PKGBUILDDIR»/debian/ruby-bio/usr/lib/ruby/vendor_ruby/bio/shell/rails/vendor/plugins/bioruby/generators/bioruby/templates/spinner.gif
> install -D -m644 
> lib/bio/shell/rails/vendor/plugins/bioruby/generators/bioruby/templates/bioruby_helper.rb
>  
> /«PKGBUILDDIR»/debian/ruby-bio/usr/lib/ruby/vendor_ruby/bio/shell/rails/vendor/plugins/bioruby/generators/bioruby/templates/biorub

Processed: Re: Bug#679106: cron: multiple /etc/init.d/cron stop may kill unrelated processes

[Debian Bug Tracking System]

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

> tag 679106 moreinfo
Bug #679106 [cron] cron: multiple /etc/init.d/cron stop may kill unrelated 
processes
Added tag(s) moreinfo.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
679106: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=679106
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#679106: cron: multiple /etc/init.d/cron stop may kill unrelated processes

[Javier Fernandez-Sanguino]

tag 679106 moreinfo
thanks

> Apparently, cron doesn't clear the PID file once stopped, so
> subsequent invokations of:
> /etc/init.d/cron stop
> continue to try killing a process of that PID.

For its stop argument, cron uses /lib/lsb/init-functions's killproc. I
believe killproc should remove the pidfile if the processes is killed
properly.

I'm unable to reproduce the behaviour you are seeing. Maybe this is
associated with your environment. In order to diagnose it, I would
appreciate if you could run the following (as root) and send the
output to this bug report (you can use 'script' to capture all the
output to a file). Please ensure first that the cron daemon is
started:


sh -x /etc/init.d/cron stop
ls -la /var/run/cron*
/etc/init.d/cron status
sh -x /etc/init.d/cron stop
ls -la /var/run/cron*
/etc/init.d/cron status



Thanks,

Javier



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

Bug#679272: bcfg2-server: unescaped shell command issues in the Trigger plugin

[Arto Jantunen]

Arto Jantunen  writes:

> Package: bcfg2-server
> Version: 1.0.1-3+squeeze1
> Severity: critical
> Tags: security, patch, pending
>
> Quoting the upstream announcement (written by Chris St. Pierre):
>
> "We have found a major security flaw in the Trigger plugin that would allow a
> malicious user who has root access to a Bcfg2 client to run arbitrary commands
> on the server as the user the bcfg2-server process is running as by passing a
> malformed UUID.
>
> This is very similar to a flaw discovered last year in a large number of other
> plugins; this instance was not fixed at that time because Trigger uses a
> different method to invoke external shell commands, and because Trigger
> previously hid all errors from trigger scripts, so tests did not find the
> issue.  As a side effect of this change, Trigger will begin reporting errors
> from triggered scripts.
>
> This only affects the Trigger plugin; if you are not using Trigger, you are
> not affected by this flaw.  As a workaround, you can disable Trigger until you
> are able to upgrade."
>
> In Debian (and all other distros I know of) the bcfg2 server runs as
> root, so in practice this is a remote root hole (limited to attackers
> who can connect to the bcfg2 server (protected by a password and/or an
> ssl key)).

.dsc and .debian.tar.gz for a fixed package are attached. I'll upload
the fix to unstable next.

-- 
Arto Jantunen



pgpINkzijARrL.pgp
Description: PGP signature


bcfg2_1.0.1-3+squeeze2.dsc
Description: dsc


bcfg2_1.0.1-3+squeeze2.debian.tar.gz
Description: debian.tar.gz

Bug#679297: [canorus] canorus crashes when saving

[Markus Grunwald]

Package: canorus
Version: 0.7+dfsg+svn1256-2
Severity: grave

--- Please enter the report below this line. ---

Canorus crashes immediately when saving my data.

Steps to reproduce:
-Start canorus
-Press Ctrl-S
-Enter filename
-Press Enter
-Crash

No matter if the file is empty like in the example or not, canorus crashes.

Crash output:

*** buffer overflow detected ***: canorus terminated
=== Backtrace: =
/lib/x86_64-linux-gnu/libc.so.6(__fortify_fail+0x37)[0x7fca59d94f07]
/lib/x86_64-linux-gnu/libc.so.6(+0xebdc0)[0x7fca59d93dc0]
/lib/x86_64-linux-gnu/libc.so.6(+0xeb219)[0x7fca59d93219]
/lib/x86_64-linux-gnu/libc.so.6(_IO_default_xsputn+0x85)[0x7fca59d1c285]
/lib/x86_64-linux-gnu/libc.so.6(_IO_vfprintf+0x1a2a)[0x7fca59cebeaa]
/lib/x86_64-linux-gnu/libc.so.6(__vsprintf_chk+0x9d)[0x7fca59d932bd]
/lib/x86_64-linux-gnu/libc.so.6(__sprintf_chk+0x7f)[0x7fca59d931ff]
canorus(_ZN5CATar8numToOctEPcxi+0x108)[0x7fca5ca8d898]
canorus(_ZN5CATar9numToOctiERPcxi+0x1b)[0x7fca5ca8d8db]
canorus(_ZN5CATar11writeHeaderER9QIODevicei+0xe1)[0x7fca5ca8dba1]
canorus(_ZN5CATar5writeER9QIODevicex+0x2d9)[0x7fca5ca8e299]
canorus(_ZN9CAArchive5writeER9QIODevice+0x316)[0x7fca5ca90836]
canorus(_ZN11CACanExport18exportDocumentImplEP10CADocument+0x323)[0x7fca5cb64f33]
canorus(_ZN8CAExport3runEv+0x21)[0x7fca5cb53621]
/usr/lib/x86_64-linux-gnu/libQtCore.so.4(+0x8232b)[0x7fca5af7732b]
/lib/x86_64-linux-gnu/libpthread.so.0(+0x6b50)[0x7fca5aac8b50]
/lib/x86_64-linux-gnu/libc.so.6(clone+0x6d)[0x7fca59d806dd]
=== Memory map: 
7fca48618000-7fca48619000 ---p  00:00 0
7fca48619000-7fca48e19000 rw-p  00:00 0
7fca48e19000-7fca491fc000 rw-s  00:04 85000199
 /SYSV (deleted)
7fca492e7000-7fca493ee000 rw-s  00:04 85131272
 /SYSV (deleted)
7fca493ee000-7fca493f7000 r-xp  08:06 2348437
 /usr/lib/x86_64-linux-gnu/qt4/plugins/iconengines/libqsvgicon.so
7fca493f7000-7fca495f6000 ---p 9000 08:06 2348437
 /usr/lib/x86_64-linux-gnu/qt4/plugins/iconengines/libqsvgicon.so
7fca495f6000-7fca495f7000 r--p 8000 08:06 2348437
 /usr/lib/x86_64-linux-gnu/qt4/plugins/iconengines/libqsvgicon.so
7fca495f7000-7fca495f8000 rw-p 9000 08:06 2348437
 /usr/lib/x86_64-linux-gnu/qt4/plugins/iconengines/libqsvgicon.so
7fca495f8000-7fca495f9000 ---p  00:00 0
7fca495f9000-7fca49df9000 rw-p  00:00 0
7fca49df9000-7fca49dfb000 r-xp  08:06 2348462
 /usr/lib/x86_64-linux-gnu/gconv/MACINTOSH.so
7fca49dfb000-7fca49ffa000 ---p 2000 08:06 2348462
 /usr/lib/x86_64-linux-gnu/gconv/MACINTOSH.so
7fca49ffa000-7fca49ffb000 r--p 1000 08:06 2348462
 /usr/lib/x86_64-linux-gnu/gconv/MACINTOSH.so
7fca49ffb000-7fca49ffc000 rw-p 2000 08:06 2348462
 /usr/lib/x86_64-linux-gnu/gconv/MACINTOSH.so
7fca49ffc000-7fca49ffd000 ---p  00:00 0
7fca49ffd000-7fca4a7fd000 rw-p  00:00 0
7fca4a7fd000-7fca4a7fe000 ---p  00:00 0
7fca4a7fe000-7fca4affe000 rw-p  00:00 0
7fca4affe000-7fca4afff000 ---p  00:00 0
7fca4afff000-7fca4b7ff000 rw-p  00:00 0
7fca4b7ff000-7fca4b80 ---p  00:00 0
7fca4b80-7fca4c00 rw-p  00:00 0
7fca4c00-7fca4c465000 rw-p  00:00 0
7fca4c465000-7fca5000 ---p  00:00 0
7fca5003e000-7fca500b4000 rw-s  00:04 84901894
 /SYSV (deleted)
7fca500b4000-7fca500b5000 ---p  00:00 0
7fca500b5000-7fca508b5000 rw-p  00:00 0
7fca508b5000-7fca508b6000 ---p  00:00 0
7fca508b6000-7fca510b6000 rw-p  00:00 0
7fca510b6000-7fca510b7000 ---p  00:00 0
7fca510b7000-7fca518b7000 rw-p  00:00 0
7fca518b7000-7fca518b8000 ---p  00:00 0
7fca518b8000-7fca5212e000 rw-p  00:00 0
7fca52166000-7fca521a4000 rw-s  00:04 85065733
 /SYSV (deleted)
7fca521a4000-7fca521af000 r-xp  08:06 2346790
 /usr/lib/x86_64-linux-gnu/libjbig.so.0.0.0
7fca521af000-7fca523af000 ---p b000 08:06 2346790
 /usr/lib/x86_64-linux-gnu/libjbig.so.0.0.0
7fca523af000-7fca523b2000 rw-p b000 08:06 2346790
 /usr/lib/x86_64-linux-gnu/libjbig.so.0.0.0
7fca523b2000-7fca52415000 r-xp  08:06 2346107
 /usr/lib/x86_64-linux-gnu/libtiff.so.4.3.6
7fca52415000-7fca52614000 ---p 00063000 08:06 2346107
 /usr/lib/x86_64-linux-gnu/libtiff.so.4.3.6
7fca52614000-7fca52617000 r--p 00062000 08:06 2346107
 /usr/lib/x86_64-linux-gnu/libtiff.so.4.3.6
7fca52617000-7fca52618000 rw-p 00065000 08:06 2346107
 /usr/lib/x86_64-linux-gnu/libtiff.so.4.3.6
7fca52618000-7fca5261f000 r-xp  08:06 2349853
 /usr/lib/x86_64-linux-gnu/qt4/plugins/imageformats/libqtiff.so
7fca5261f000-7fca5281e000 ---p 7000 08:06 2349853
 /usr/lib/x86_64-linux-gnu/qt4/plugins/imageformats/libqtiff.so
7fca5281e000-7fca5281f000 r--p 6000 08:06 2349853
 /usr/lib/x86_64-linux-gnu/qt4/plugins/imageformats/libqtiff.so
7fca5281f000-7fca5282 rw-p 7000 08:06 2349853
 /usr/lib/x86_64-linux-gnu/qt4/plugins/imageformats/libqtiff.so
7fca5282-7fca52825000 r-xp  08:06 234

Bug#675295: FTBFS in version 0.13+ds1-2

[Boris Pek]

Hi Peter,

During researching the list of packages maintained by Debian QA Group [1] with
bugs I found the package matanza [2].

As we can see in changelog [3] you adopted this package, and its updated
version was uploaded into experimental.

Unfortunately, your changes causes new FTBFS. (I've tested version 0.13+ds1-1
and it was built successfully.)

Are you still interested in maintaining of this package? If yes could you
update the package in the nearest future? (Wheeze freeze will be at June 30.)

RC bug #675295 can be fixed by NMU, but less serious bugs #636984 and #662427
should be fixed in usual or QA upload. And it would be very nice to have them
fixed to approach the libpng15 transition.

Bug #662427 needs tiny change in debian/control and bug #636984 has patch.
So the package won't require much time for update.

I am not sure how organized the maintaining process in the Debian Games Team.
Maybe someone else can prepare an update. And this will be fine too.

(Please Cc me in replies, I am not subscribed to this mailing list)

Best regards,
Boris

[1] http://qa.debian.org/developer.php?login=packa...@qa.debian.org
[2] http://packages.qa.debian.org/m/matanza.html
[3] http://packages.debian.org/changelogs/pool/main/m/matanza/current/changelog



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

Bug#677801: AttributeError: 'module' object has no attribute 'uses_fragment'

[Andrey Rahmatullin]

On Wed, Jun 27, 2012 at 07:00:50PM +0200, Marek Hobler wrote:
> Package: python-pip
> Version: 1.1-3
> Followup-For: Bug #677801
> 
> Dear Maintainer,
> 
> On my system it works only outside virtualenv... Another words: I can
> reporoduce this on my systems in virtualenvs.
It's not a problem of python-pip.
For new venvs it's a problem of python-virtualenv that contains an
embedded source of pip 1.1 in /usr/share/python-virtualenv/pip-1.1.tar.gz
For old venvs I'm afraid there can be no proper solution aside from
installing the new pip version (unreleased yet) with easy_install.

-- 
WBR, wRAR


signature.asc
Description: Digital signature

Bug#660260: Fwd: GDL seems to use non public symbols from plplot (Debian Wheezy freeze on Saturday)

[Sylwester Arabas]

Hi Axel,
CC: Joel, Alain, Marc, Debian bug-tracker

On 27/06/12 18:07, Axel Beckert wrote:

... 
http://sourceforge.net/tracker/?func=detail&aid=3529264&group_id=97659&atid=618683

GDL unfortunately will not be part of the next Debian stable release
if this can't be fixed soon.


Here's a fix suggested by Joel:

On 05/06/12 14:09, gal...@cox.net wrote:
> I would suggest replacing:
>
> lib::mesh_nr(xVec1, yVec1, z1, (long int) xEl, 1,1);
>
> in plotting.cpp by
>
> plmesh(xVec1, yVec1, z1, (long int) xEl, 1,1);
>
> I think the plplot library now has the functionality that was
> missing before.
>
> If we remove the call to mesh_nr then we no longer have to include
> plot3d_nr.cpp which was causing the problem.

I'll try to test it and commit to the repository today or tomorrow.

Sorry for the delay and big thanks for the reminders!
Best,
Sylwester

--
http://www.igf.fuw.edu.pl/~slayoo/



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

Bug#669379: marked as done (abntex: unowned file /usr/local/share/texmf/ls-R after purge (policy 6.8, 9.1.2))

[Debian Bug Tracking System]

Your message dated Wed, 27 Jun 2012 17:02:43 +
with message-id 
and subject line Bug#669379: fixed in abntex 0.9~beta2-5.1
has caused the Debian Bug report #669379,
regarding abntex: unowned file /usr/local/share/texmf/ls-R after purge (policy 
6.8, 9.1.2)
to be marked as done.

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

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


-- 
669379: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=669379
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: abntex
Version: 0.9~beta2-5
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

during a test with piuparts I noticed your package left unowned files on
the system after purge, which is a violation of policy 6.8:
http://www.debian.org/doc/debian-policy/ch-maintainerscripts.html#s-removedetails

As putting files into /usr/local is also a violation of
http://www.debian.org/doc/debian-policy/ch-opersys.html#s9.1.2
I'm setting the severity to serious.

>From the attached log (scroll to the bottom...):

0m53.8s ERROR: FAIL: Package purging left files on system:
  /usr/local/share/texmf/not owned
  /usr/local/share/texmf/ls-Rnot owned


This problem is usually caused by running mktexlsr (or texhash) without
path arguments from a maintainer script.

The recommende solution is to switch to use dh_installtex and have this
generate most (or perhaps even all) of the maintainer scripts content.

Otherwise run mktexlsr with the tree as argument where the package
installs its files, which is usually
  mktexlsr /usr/share/texmf

There has been some further discussion about these bugs in this thread:
http://lists.debian.org/debian-tex-maint/2012/04/msg00306.html

Please have a look at the Debian-TeX-Policy (in the tex-common package)
for the current practice of handling TeX packages. For further TeX
packaging related questions contact debian-tex-ma...@lists.debian.org


cheers,

Andreas


abntex_0.9~beta2-5.log.gz
Description: GNU Zip compressed data
--- End Message ---
--- Begin Message ---
Source: abntex
Source-Version: 0.9~beta2-5.1

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

abntex_0.9~beta2-5.1.debian.tar.gz
  to main/a/abntex/abntex_0.9~beta2-5.1.debian.tar.gz
abntex_0.9~beta2-5.1.dsc
  to main/a/abntex/abntex_0.9~beta2-5.1.dsc
abntex_0.9~beta2-5.1_all.deb
  to main/a/abntex/abntex_0.9~beta2-5.1_all.deb



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

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

Debian distribution maintenance software
pp.
Andrew Starr-Bochicchio  (supplier of updated abntex 
package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Sun, 24 Jun 2012 18:08:20 -0400
Source: abntex
Binary: abntex
Architecture: source all
Version: 0.9~beta2-5.1
Distribution: unstable
Urgency: low
Maintainer: Otavio Salvador 
Changed-By: Andrew Starr-Bochicchio 
Description: 
 abntex - LaTeX class for writing documents in ABNT standard
Closes: 669379
Changes: 
 abntex (0.9~beta2-5.1) unstable; urgency=low
 .
   * Non-maintainer upload.
   * Drop debian/postinst, call dh_installtex in debian/rules,
 and build depend on tex-common This causes the package to
 no longer install files to /usr/local (Closes: #669379).
Checksums-Sha1: 
 7eb554757a73df96a890287a454ec9eb520bb726 1951 abntex_0.9~beta2-5.1.dsc
 f01f98ef8f8af8126473d02cb59cc370d05da62d 9237 
abntex_0.9~beta2-5.1.debian.tar.gz
 d78fe7ab0beb0f9c7f614a0b7c4be62291463414 328514 abntex_0.9~beta2-5.1_all.deb
Checksums-Sha256: 
 4346b5f7b18f151c922553796ed682f1b526a61b622d2913f65c8afa31f96c6c 1951 
abntex_0.9~beta2-5.1.dsc
 1970da8272c1300d460cf0f32cd8618bcac5b51dea3d9381c128722a2020d6e3 9237 
abntex_0.9~beta2-5.1.debian.tar.gz
 0ec6afff53cdd1b24d4162b39af6fa3bd0e93a1f4f6396c8a7a0acc39e0ec87d 328514 
abntex_0.9~beta2-5.1_all.deb
Files: 
 501b8a77aa48338f8667bdd8d51a387f 1951 tex optional abntex_0.9~beta2-5.1.dsc
 635260bf294e46c613ec29aabe3f0fdf 9237 tex optional 
abntex_0.9~beta2-5.1.debian.tar.gz
 7ba9ea03bfb808e9111e74e0c2340681 328514 tex optional 
abntex_0.9~beta2-5.1_all.deb

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

iQIcBAEBCAAGBQJP6JP0AAoJELs6aAGGSaoGUOMQAIXAFwjsfe36EmQ1q82fCz

Bug#588588: marked as done (aircrack-ng: debian/copyright is missing information for src/sha1-sse2.*)

[Debian Bug Tracking System]

Your message dated Wed, 27 Jun 2012 17:02:09 +
with message-id 
and subject line Bug#588588: fixed in aircrack-ng 1:1.1-2
has caused the Debian Bug report #588588,
regarding aircrack-ng: debian/copyright is missing information for 
src/sha1-sse2.*
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.)


-- 
588588: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=588588
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: aircrack-ng
Severity: serious
Justification: Policy 12.5

debian/copyright neither mentions the authors of or the license under which 
src/sha1-sse2.h and src/sha1-sse2.S are distributed.

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

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

Versions of packages aircrack-ng depends on:
pn  iw (no description available)
ii  libc6   2.11.2-2 Embedded GNU C Library: Shared lib
ii  libsqlite3-03.6.23.1-4   SQLite 3 shared library
ii  libssl0.9.8 0.9.8o-1 SSL shared libraries
pn  wireless-tools (no description available)
ii  zlib1g  1:1.2.3.4.dfsg-3 compression library - runtime

aircrack-ng recommends no packages.

aircrack-ng suggests no packages.


--- End Message ---
--- Begin Message ---
Source: aircrack-ng
Source-Version: 1:1.1-2

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

aircrack-ng_1.1-2.debian.tar.gz
  to main/a/aircrack-ng/aircrack-ng_1.1-2.debian.tar.gz
aircrack-ng_1.1-2.dsc
  to main/a/aircrack-ng/aircrack-ng_1.1-2.dsc
aircrack-ng_1.1-2_amd64.deb
  to main/a/aircrack-ng/aircrack-ng_1.1-2_amd64.deb
aircrack-ng_1.1.orig.tar.gz
  to main/a/aircrack-ng/aircrack-ng_1.1.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 588...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Carlos Alberto Lopez Perez  (supplier of updated aircrack-ng 
package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Mon, 18 Jun 2012 13:17:36 WST
Source: aircrack-ng
Binary: aircrack-ng
Architecture: source amd64
Version: 1:1.1-2
Distribution: unstable
Urgency: low
Maintainer: Carlos Alberto Lopez Perez 
Changed-By: Carlos Alberto Lopez Perez 
Description: 
 aircrack-ng - wireless WEP/WPA cracking utilities
Closes: 588588 600753 610688 642698 642934
Changes: 
 aircrack-ng (1:1.1-2) unstable; urgency=low
 .
   * New mantainer.
   * Re-upload to unstable (Closes: #642934)
   * Rework debian/*
 Switch debian/rules to dh.
 Switch debian/copyright to machine-readable.
 Add DEP-3 headers to debian/patches/*
   * Remove injection patches from package files. airdriver-ng downloads
 this patches from Internet, so is not needed at all to have
 this files on the package.
   * Include initial pre-downloaded file airodump-ng-oui.txt on package.
   * Add hardening flags.
   * Compile with sqlite support (Closes: #610688) (Closes: #600753)
   * Add 004-fix-license-issues.diff (cherry-pick from svn).
 Fixes copyright issues with src/sha1-sse2.* (Closes: #588588)
   * Add 005-fix-issues-cppcheck-r2008.patch (cherry-pick from svn).
 Fix issues on the code found by cppcheck.
   * Add 006-fix-ftbfs-and-man-path.patch (cherry-pick from svn).
 Fix FTBFS with gcc>=4.6 and fix manpage path.
   * Add 007-Add-support-for-GnuTLS.patch
 Add support for GnuTLS and link against GnuTLS.
 Fix issues with GPL and OpenSSL licenses.
   * Add 008-fix_path_airodump-ng-oui.patch.
 Fix paths to file airodump-ng-oui.txt on airodump-ng and script
 airodump-ng-oui-update.
   * Add 009-airodump-ng-oui-update-manpage.patch (cherry-pick from svn).
 Include manpage for script airodump-ng-oui-update.
   * Add 010-add-freebsd-support.patch
 Add support for GNU/kFreeBSD (Closes: #642698)
   * Update Standards-Version to 3.9.2
Checksums-Sha256: 
 c9d9633328b1dd4b9141d65632d5639b5df8cb4b5904

Bug#677801: AttributeError: 'module' object has no attribute 'uses_fragment'

[Marek Hobler]

Package: python-pip
Version: 1.1-3
Followup-For: Bug #677801

Dear Maintainer,

On my system it works only outside virtualenv... Another words: I can
reporoduce this on my systems in virtualenvs.




-- 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.4.0 (SMP w/8 CPU cores)
Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968)
Shell: /bin/sh linked to /bin/dash

Versions of packages python-pip depends on:
ii  python2.7.3~rc2-1
ii  python-pkg-resources  0.6.24-1
ii  python-setuptools 0.6.24-1
ii  python2.6 2.6.8-0.1

Versions of packages python-pip recommends:
ii  build-essential  11.5
pn  python-dev-all   

python-pip 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#665035: marked as done (openmcu: FTBFS: build-dependency not installable: libpt2.4.5-dev)

[Debian Bug Tracking System]

Your message dated Wed, 27 Jun 2012 16:51:39 +
with message-id 
and subject line Bug#679084: Removed package(s) from unstable
has caused the Debian Bug report #665035,
regarding openmcu: FTBFS: build-dependency not installable: libpt2.4.5-dev
to be marked as done.

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

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


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

Hi,

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

Relevant part:
> ┌──┐
> │ Install openmcu build dependencies (apt-based resolver) 
>  │
> └──┘
> 
> Installing build dependencies
> Reading package lists...
> Building dependency tree...
> Reading state information...
> Some packages could not be installed. This may mean that you have
> requested an impossible situation or if you are using the unstable
> distribution that some required packages have not yet been created
> or been moved out of Incoming.
> The following information may help to resolve the situation:
> 
> The following packages have unmet dependencies:
>  sbuild-build-depends-openmcu-dummy : Depends: libpt2.4.5-dev but it is not 
> going to be installed
> E: Broken packages

The full build log is available from:
   http://people.debian.org/~lucas/logs/2012/03/21/openmcu_2.2.5-1.log

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

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


--- End Message ---
--- Begin Message ---
Version: 2.2.5-1+rm

Dear submitter,

as the package openmcu has just been removed from the Debian archive
unstable we hereby close the associated bug reports.  We are sorry
that we couldn't deal with your issue properly.

For details on the removal, please see http://bugs.debian.org/679084

The version of this package that was in Debian prior to this removal
can still be found using http://snapshot.debian.org/.

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

Debian distribution maintenance software
pp.
Alexander Reichle-Schmehl (the ftpmaster behind the curtain)

--- End Message ---

Bug#669393: marked as done (tetex-brev: unowned file /usr/local/share/texmf/ls-R after purge (policy 6.8, 9.1.2))

[Debian Bug Tracking System]

Your message dated Wed, 27 Jun 2012 16:49:06 +
with message-id 
and subject line Bug#669393: fixed in tetex-brev 4.22.6+nmu1
has caused the Debian Bug report #669393,
regarding tetex-brev: unowned file /usr/local/share/texmf/ls-R after purge 
(policy 6.8, 9.1.2)
to be marked as done.

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

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


-- 
669393: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=669393
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: tetex-brev
Version: 4.22.6
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

during a test with piuparts I noticed your package left unowned files on
the system after purge, which is a violation of policy 6.8:
http://www.debian.org/doc/debian-policy/ch-maintainerscripts.html#s-removedetails

As putting files into /usr/local is also a violation of
http://www.debian.org/doc/debian-policy/ch-opersys.html#s9.1.2
I'm setting the severity to serious.

>From the attached log (scroll to the bottom...):

0m53.8s ERROR: FAIL: Package purging left files on system:
  /usr/local/share/texmf/not owned
  /usr/local/share/texmf/ls-Rnot owned


This problem is usually caused by running mktexlsr (or texhash) without
path arguments from a maintainer script.

The recommende solution is to switch to use dh_installtex and have this
generate most (or perhaps even all) of the maintainer scripts content.

Otherwise run mktexlsr with the tree as argument where the package
installs its files, which is usually
  mktexlsr /usr/share/texmf

There has been some further discussion about these bugs in this thread:
http://lists.debian.org/debian-tex-maint/2012/04/msg00306.html

Please have a look at the Debian-TeX-Policy (in the tex-common package)
for the current practice of handling TeX packages. For further TeX
packaging related questions contact debian-tex-ma...@lists.debian.org


cheers,

Andreas


tetex-brev_4.22.6.log.gz
Description: GNU Zip compressed data
--- End Message ---
--- Begin Message ---
Source: tetex-brev
Source-Version: 4.22.6+nmu1

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

tetex-brev_4.22.6+nmu1.dsc
  to main/t/tetex-brev/tetex-brev_4.22.6+nmu1.dsc
tetex-brev_4.22.6+nmu1.tar.gz
  to main/t/tetex-brev/tetex-brev_4.22.6+nmu1.tar.gz
tetex-brev_4.22.6+nmu1_all.deb
  to main/t/tetex-brev/tetex-brev_4.22.6+nmu1_all.deb



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

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

Debian distribution maintenance software
pp.
Andrew Starr-Bochicchio  (supplier of updated tetex-brev 
package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Sun, 24 Jun 2012 19:07:14 -0400
Source: tetex-brev
Binary: tetex-brev
Architecture: source all
Version: 4.22.6+nmu1
Distribution: unstable
Urgency: low
Maintainer: Petter Reinholdtsen 
Changed-By: Andrew Starr-Bochicchio 
Description: 
 tetex-brev - Norwegian A4 letter style for LaTeX
Closes: 669393
Changes: 
 tetex-brev (4.22.6+nmu1) unstable; urgency=low
 .
   * Non-maintainer upload.
   * Drop debian/postinst, call dh_installtex in debian/rules,
 and build depend on tex-common. This causes the package to
 no longer create files in /usr/local (Closes: #669393).
Checksums-Sha1: 
 603b476ca5dc08d942b0370ae69c0b01f9fefbe7 1499 tetex-brev_4.22.6+nmu1.dsc
 c7858e0268d92f32f8b4455e5ac2ff4920ac3711 25548 tetex-brev_4.22.6+nmu1.tar.gz
 358e50572c73977097f912dda3df7bb751d2f11d 16314 tetex-brev_4.22.6+nmu1_all.deb
Checksums-Sha256: 
 050b9b7be9468ebeb7160df6aa3fd9783eb5c449adba2c37a33dc2bc665c7855 1499 
tetex-brev_4.22.6+nmu1.dsc
 8077114647a8a578634309a3fa94e86a0b141f2abaae916c50c144cd6ec5b72e 25548 
tetex-brev_4.22.6+nmu1.tar.gz
 429609ec27c197257ec484f47c6e6215a966db8017e7fd47d74c5412ea999815 16314 
tetex-brev_4.22.6+nmu1_all.deb
Files: 
 97add4a6a86c85d86c863dc25ed502b0 1499 tex optional tetex-brev_4.22.6+nmu1.dsc
 4ceb3dc62f8d0353fa17fd335d062c63 25548 tex optional 
tetex-brev_4.22.6+nmu1.tar.gz
 5d2d7062d2d28606153755ee901aa9e8 16314 tex optional 
tetex-brev_4.22.6+nmu1_all.deb

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

iQIcBAEBCAAGBQJP6JC7AAoJELs6aAGGSaoGd1cQAKW7T

Bug#676091: marked as done (shoes: FTBFS: ./shoes/app.h:14:18: fatal error: ruby.h: No such file or directory)

[Debian Bug Tracking System]

Your message dated Wed, 27 Jun 2012 16:48:52 +
with message-id 
and subject line Bug#676091: fixed in shoes 0.r396-5.2
has caused the Debian Bug report #676091,
regarding shoes: FTBFS: ./shoes/app.h:14:18: fatal error: ruby.h: No such file 
or directory
to be marked as done.

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

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


-- 
676091: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=676091
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: shoes
Version: 0.r396-5.1
Severity: serious
Tags: wheezy sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20120604 qa-ftbfs
User: debian-r...@lists.debian.org
Usertags: default19
Justification: FTBFS on amd64

Hi,

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

Relevant part:
> make[1]: Entering directory `/«PKGBUILDDIR»'
> cleaning
> shoes build options:
> CC   = cc
> -e:1: Use RbConfig instead of obsolete and deprecated Config.
> RUBY = /usr
> OPTIONS  =
> ruby 1.9.3p194 (2012-04-20 revision 35410) [x86_64-linux]
> CC shoes/app.c
> -e:1: Use RbConfig instead of obsolete and deprecated Config.
> In file included from shoes/app.c:5:0:
> ./shoes/app.h:14:18: fatal error: ruby.h: No such file or directory
> compilation terminated.
> make[1]: *** [shoes/app.o] Error 1

The full build log is available from:
   http://people.debian.org/~lucas/logs/2012/06/04/shoes_0.r396-5.1_unstable.log

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

About the archive rebuild: The rebuild was done on EC2 VM instances from
Amazon Web Services, using a clean, minimal and up-to-date chroot. Every
failed build was retried once to eliminate random failures.


--- End Message ---
--- Begin Message ---
Source: shoes
Source-Version: 0.r396-5.2

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

shoes_0.r396-5.2.debian.tar.gz
  to main/s/shoes/shoes_0.r396-5.2.debian.tar.gz
shoes_0.r396-5.2.dsc
  to main/s/shoes/shoes_0.r396-5.2.dsc
shoes_0.r396-5.2_amd64.deb
  to main/s/shoes/shoes_0.r396-5.2_amd64.deb



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

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

Debian distribution maintenance software
pp.
Per Andersson  (supplier of updated shoes package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Sun, 24 Jun 2012 00:34:16 +0200
Source: shoes
Binary: shoes
Architecture: source amd64
Version: 0.r396-5.2
Distribution: unstable
Urgency: low
Maintainer: Bram Senders 
Changed-By: Per Andersson 
Description: 
 shoes  - tiny graphics and windowing toolkit using Ruby
Closes: 676091
Changes: 
 shoes (0.r396-5.2) unstable; urgency=low
 .
   * Non-maintainer upload.
   * Fix FTBFS (Closes: #676091)
 - Build for only Ruby 1.8.
 - Build depend on ruby1.8 instead of ruby.
 - Add patch for using ruby1.8 in Makefile.
Checksums-Sha1: 
 cb0872497de6a61915ab1397c6ddbf2a34cdfc99 1853 shoes_0.r396-5.2.dsc
 3fd5d808cc934ad23952af0ffcd5fd021909ee8f 7457 shoes_0.r396-5.2.debian.tar.gz
 a802d13ee8a63b190d257fc56cf6bf4f209a772d 192560 shoes_0.r396-5.2_amd64.deb
Checksums-Sha256: 
 9fa34655c5a4b8b65e1240e63b740ad65da5d2fd251874734484eb5fc3cc116b 1853 
shoes_0.r396-5.2.dsc
 2732af1b732c5643249911cff318d37c33e27609184c59e44844b6157b04831e 7457 
shoes_0.r396-5.2.debian.tar.gz
 c78feb27947280f29e53e0a17326393975234610518621d8e08048806c443d7a 192560 
shoes_0.r396-5.2_amd64.deb
Files: 
 11e63d95e87d800ab53d0ce313ba4c6b 1853 interpreters extra shoes_0.r396-5.2.dsc
 f6cc2a0d3a281916e0f2faddc50a 7457 interpreters extra 
shoes_0.r396-5.2.debian.tar.gz
 b18374f97af6c728301de9e1b37fa648 192560 interpreters extra 
shoes_0.r396-5.2_amd64.deb

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

iQIcBAEBCAAGBQJP50F8AAoJELCi8amz5hIsSl8P/3pjgvcLUCiwwk8Qffknn/i9
in7i4H3SID1psOhP6CEsbvtUHs4GubyNc4inCHmvbgzwDVORQCGf9kN4MDJhVIfA
e04Ymmd5/9V7gWag1LLlB+YWOvMsqcSgVv5XVMQeUfUcbw0dfzkjGsHTBkqWfoic
fBPwO3n/OHt77bO/wvE9kjV+nKTTBRzn9YTitC4zpEY+wiMOvVuRuzHTnbSinKgm
wDg+x7gYbf2YHbzmA2IQtaqoAmzt72LqyQBDQiuUHQRiIkCpe3wqO+6dWJDwOnp1
4YC0J23NlLXGSsDg87haXZADQCyt6SZUth2C

Processed: notfound 679171 in 1.76

[Debian Bug Tracking System]

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

> notfound 679171 1.76
Bug #679171 [console-setup-pc-ekmap] debian-installer: qwerty is kept after 
(another) keyboard is selected
No longer marked as found in versions console-setup/1.76.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
679171: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=679171
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#676016: marked as done (scim-tables: FTBFS: scim_table_imengine_setup.cpp:35:21: fatal error: gtk/gtk.h: No such file or directory)

[Debian Bug Tracking System]

Your message dated Wed, 27 Jun 2012 16:40:12 +
with message-id 
and subject line Bug#659309: Removed package(s) from unstable
has caused the Debian Bug report #676016,
regarding scim-tables: FTBFS: scim_table_imengine_setup.cpp:35:21: fatal error: 
gtk/gtk.h: No such file or directory
to be marked as done.

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

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


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

Hi,

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

Relevant part:
>  g++ -DHAVE_CONFIG_H -I. -I.. -I.. -I.. -I../src -I../intl 
> -DSCIM_ICONDIR=\"/usr/share/scim/icons\" 
> -DSCIM_TABLE_LOCALEDIR=\"/usr/share/locale\" 
> -DSCIM_TABLEDIR=\"/usr/share/scim/tables\" -DSCIM_DATADIR=\"/usr/share/scim\" 
> -I/usr/include/scim-1.0 -W -g -O -MT 
> table_imengine_setup_la-scim_table_imengine_setup.lo -MD -MP -MF 
> .deps/table_imengine_setup_la-scim_table_imengine_setup.Tpo -c 
> scim_table_imengine_setup.cpp  -fPIC -DPIC -o 
> .libs/table_imengine_setup_la-scim_table_imengine_setup.o
> scim_table_imengine_setup.cpp:35:21: fatal error: gtk/gtk.h: No such file or 
> directory
> compilation terminated.
> make[3]: *** [table_imengine_setup_la-scim_table_imengine_setup.lo] Error 1

The full build log is available from:
   
http://people.debian.org/~lucas/logs/2012/06/04/scim-tables_0.5.9-1_unstable.log

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

About the archive rebuild: The rebuild was done on EC2 VM instances from
Amazon Web Services, using a clean, minimal and up-to-date chroot. Every
failed build was retried once to eliminate random failures.


--- End Message ---
--- Begin Message ---
Version: 0.5.9-1+rm

Dear submitter,

as the package scim-tables has just been removed from the Debian archive
unstable we hereby close the associated bug reports.  We are sorry
that we couldn't deal with your issue properly.

For details on the removal, please see http://bugs.debian.org/659309

The version of this package that was in Debian prior to this removal
can still be found using http://snapshot.debian.org/.

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

Debian distribution maintenance software
pp.
Alexander Reichle-Schmehl (the ftpmaster behind the curtain)

--- End Message ---

Bug#668207: marked as done (libjavascript-perl: not installable in sid, needs migration to perl 5.14)

[Debian Bug Tracking System]

Your message dated Wed, 27 Jun 2012 16:40:43 +
with message-id 
and subject line Bug#679136: Removed package(s) from unstable
has caused the Debian Bug report #668207,
regarding libjavascript-perl: not installable in sid, needs migration to perl 
5.14
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.)


-- 
668207: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=668207
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: libjavascript-perl
Version: 1.16-3+b1
Severity: serious
User: trei...@debian.org
Usertags: edos-uninstallable

Hi, libjavascript-perl is not installable in sid, on amd64 and i386 since
August 10 2011, since it depends on perlapi-5.12.3. However, the version
of perl in sid is 5.14.

Cheers -Ralf.


--- End Message ---
--- Begin Message ---
Version: 1.16-3+rm

Dear submitter,

as the package libjavascript-perl has just been removed from the Debian archive
unstable we hereby close the associated bug reports.  We are sorry
that we couldn't deal with your issue properly.

For details on the removal, please see http://bugs.debian.org/679136

The version of this package that was in Debian prior to this removal
can still be found using http://snapshot.debian.org/.

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

Debian distribution maintenance software
pp.
Alexander Reichle-Schmehl (the ftpmaster behind the curtain)

--- End Message ---

Processed: Re: Bug#679171: debian-installer: qwerty is kept after (another) keyboard is selected

[Debian Bug Tracking System]

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

> tags 679171 + pending
Bug #679171 [console-setup-pc-ekmap] debian-installer: qwerty is kept after 
(another) keyboard is selected
Added tag(s) pending.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
679171: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=679171
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#679171: debian-installer: qwerty is kept after (another) keyboard is selected

[Samuel Thibault]

tags 679171 + pending
thanks

Samuel Thibault, le Wed 27 Jun 2012 12:14:46 -0300, a écrit :
> Samuel Thibault, le Wed 27 Jun 2012 11:28:14 -0300, a écrit :
> > Cyril Brulebois, le Tue 26 Jun 2012 22:19:35 +0200, a écrit :
> > > with text-mode netinst mini.iso, even after having chosen a typical
> > > French layout (after having picked the French language), qwerty is kept.
> > 
> > The ekmap files don't contain the keymaps. I'm having a look, it's
> > probably a bug in the ekmap file reduction.
> 
> Apparently it seems it is actually parallel build which brings the
> issue. Probably a missing dependency.

Indeed, I have pushed a fix.

Samuel



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

Bug#672504: marked as done (ruby-nora: FTBFS: undeclared build-dep on ruby1.8)

[Debian Bug Tracking System]

Your message dated Wed, 27 Jun 2012 16:34:38 +
with message-id 
and subject line Bug#672504: fixed in ruby-nora 1:0.0.20041021-5.1
has caused the Debian Bug report #672504,
regarding ruby-nora: FTBFS: undeclared build-dep on ruby1.8
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.)


-- 
672504: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=672504
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: ruby-nora
Version: 0.0.20041021-5
Severity: serious
Justification: fails to build from source

Builds of ruby-nora in minimal enviroments, such as on the
autobuilders, are failing:

  cd build && \
ruby1.8 install.rb config --site-ruby="`ruby1.8 -rrbconfig -e 
'print RbConfig::CONFIG[ARGV[0]]' vendorlibdir`" --site-ruby-common="`ruby1.8 
-rrbconfig -e 'print RbConfig::CONFIG[ARGV[0]]' vendorlibdir`" 
--so-dir="`ruby1.8 -rrbconfig -e 'print RbConfig::CONFIG[ARGV[0]]' 
vendorarchdir`"
  /bin/sh: 1: ruby1.8: not found
  /bin/sh: 1: ruby1.8: not found
  /bin/sh: 1: ruby1.8: not found
  /bin/sh: 2: ruby1.8: not found
  make[1]: *** [install-common] Error 127

Could you please declare a build dependency on ruby1.8 and check via
pbuilder or the like that no others are missing?

Thanks!


--- End Message ---
--- Begin Message ---
Source: ruby-nora
Source-Version: 1:0.0.20041021-5.1

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

libnora-ruby1.8_0.0.20041021-5.1_all.deb
  to main/r/ruby-nora/libnora-ruby1.8_0.0.20041021-5.1_all.deb
ruby-nora_0.0.20041021-5.1.debian.tar.gz
  to main/r/ruby-nora/ruby-nora_0.0.20041021-5.1.debian.tar.gz
ruby-nora_0.0.20041021-5.1.dsc
  to main/r/ruby-nora/ruby-nora_0.0.20041021-5.1.dsc
ruby-nora_0.0.20041021-5.1_amd64.deb
  to main/r/ruby-nora/ruby-nora_0.0.20041021-5.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 672...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Per Andersson  (supplier of updated ruby-nora package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Sun, 24 Jun 2012 00:23:14 +0200
Source: ruby-nora
Binary: ruby-nora libnora-ruby1.8
Architecture: source amd64 all
Version: 1:0.0.20041021-5.1
Distribution: unstable
Urgency: low
Maintainer: Tatsuki Sugiura 
Changed-By: Per Andersson 
Description: 
 libnora-ruby1.8 - Transitional package for ruby-nora
 ruby-nora  - Web Application Library for ruby
Closes: 672504
Changes: 
 ruby-nora (1:0.0.20041021-5.1) unstable; urgency=low
 .
   * Non-maintainer upload.
   * Fix FTBFS (Closes: #672504)
 - Build depend on ruby1.8.
 - Correct usage of XS-Ruby-Versions (1.8 -> ruby1.8)
 - Depend on ruby1.8 (instead of ruby | ruby-interpreter) since this
   version is required
Checksums-Sha1: 
 97313f016409f253fe26da785483f3f6f53caade 1888 ruby-nora_0.0.20041021-5.1.dsc
 4473a0872ece805dcfbebb48b13bf7c4414e66d0 3825 
ruby-nora_0.0.20041021-5.1.debian.tar.gz
 8ac498c1ec14f63fec9eb2832ccbe1699ae80bf0 48090 
ruby-nora_0.0.20041021-5.1_amd64.deb
 11fb9250559139d1a7c4fd2567af7f19b51305bf 3508 
libnora-ruby1.8_0.0.20041021-5.1_all.deb
Checksums-Sha256: 
 45841972eab910c0339556e37a031bc194d0ee945f78c86a4c251f8b2a4aa7dc 1888 
ruby-nora_0.0.20041021-5.1.dsc
 cb3506a398e9444d9c36b0f8b2167979ef2a5cdd8bc4fd228d72087dad1b71c3 3825 
ruby-nora_0.0.20041021-5.1.debian.tar.gz
 369248904f08d205c073d7d2b063d8ef73704122d62903a6cdf45af16bea5f90 48090 
ruby-nora_0.0.20041021-5.1_amd64.deb
 981a27accb2525378ce5bab01d9a1d2a08a7a66fa053b5e07f38c385c0d69c7b 3508 
libnora-ruby1.8_0.0.20041021-5.1_all.deb
Files: 
 1896ed6f791defccecd110e97aa9b1c6 1888 ruby extra ruby-nora_0.0.20041021-5.1.dsc
 65d66f09149e5eb1b1573b58e530c3fc 3825 ruby extra 
ruby-nora_0.0.20041021-5.1.debian.tar.gz
 9ae94cc1e92a53a0a461705c7062989c 48090 ruby extra 
ruby-nora_0.0.20041021-5.1_amd64.deb
 5106477677e57b66f1199c3bf01bc7cf 3508 oldlibs extra 
libnora-ruby1.8_0.0.20041021-5.1_all.deb

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

iQIcBAEBCAAGBQJP5z6aAAoJELCi8amz5hIs6L4P/3v6T2x+jOCYFx2BI7D9LDmc
VUBYqaVy0k0wYiKJPb0b53eBH4GPWf4rPedt5x26scpw3531wK6jDvmGsRO5VRJn
i9TE2se0QDHZrIdJMFJJXDVgP4KoKXtS+DGRm

Bug#660260: Fwd: GDL seems to use non public symbols from plplot (Debian Wheezy freeze on Saturday)

[Alain Coulais]

> Hi,
>
> sorry to bother you again, but the freeze for Debian 7.0 Wheezy is
> this Satuday (30th of June) and I still haven't heard or seen anything
> on this issue:
>

thanks

this is really urgent !

Alain

> On Tue, Apr 17, 2012 at 07:54:11PM -0400, gal...@cox.net wrote:
>>  Axel Beckert  wrote:
>> > On Sat, Feb 18, 2012 at 01:09:13AM +0100, Sylwester Arabas wrote:
>> > > There's a Debian bug report regarding GDL's usage of plplot's plP_*
>> calls:
>> > > http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=660260
>
> I also reported it to GDL's SF bug tracker at
> http://sourceforge.net/tracker/?func=detail&aid=3529264&group_id=97659&atid=618683
>
> GDL unfortunately will not be part of the next Debian stable release
> if this can't be fixed soon.
>
>> > > What were the reasons to put this plplot's (src/plot3d.c) file in
>> the GDL tree?
>> >
>> > Any news here? This _is_ definitely an issue on Ubuntu and may become
>> > one on Debian, too.
>
> While GDL made it into Ubuntu 12.04 LTS because some PLPLOT changes
> have been reversed there after the first build failures have been
> reported, this will likely affect Ubuntu 12.10, too.
>
>> I originally placed this file (in modified from) in the GDL
>> repository to support non-rectangular grids for the SURFACE and
>> CONTOUR functions.
>>
>> If PLPLOT can now support this feature natively then this code can
>> be replaced.
>
> I see[1] that you are preparing a 0.9.3 release but haven't noticed
> any chnagelog entry related to this issue.
>
> Any chance that the issue gets fixed for 0.9.3?
>
> When will the 0.9.3 release happen? If I know in advance, there may be
> a chance to get a freeze exception. (But I can't promise that.)
>
>   [1]
> http://gnudatalanguage.cvs.sourceforge.net/viewvc/gnudatalanguage/gdl/NEWS?revision=1.101&view=markup&sortby=date
>
> If you have a patch for the issue, please tell me (or send it to the
> above mentioned and Cc'ed Debian bug report) so that I can apply the
> patch to 0.9.2 and upload a fixed version as soon as possible without
> waiting for the 0.9.3 release. (I would actually prefer that variant
> currently as it's the most promising one for still getting into Debian
> Wheezy.)
>
>   Regards, Axel
> --
>  ,''`.  |  Axel Beckert , http://people.debian.org/~abe/
> : :' :  |  Debian Developer, ftp.ch.debian.org Admin
> `. `'   |  1024D: F067 EA27 26B9 C3FC 1486  202E C09E 1D89 9593 0EDE
>   `-|  4096R: 2517 B724 C5F6 CA99 5329  6E61 2FF9 CD59 6126 16B5
>





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

Bug#652591: noflushd: Crash with linux-image-2.6.32-5-686 (version 2.6.32-38)

[Mehdi Dogguy]

Any news here?

The packages's popcon is quite low and the project looks like dead
(last upstream release in 2010, nothing more recent than 2 years in
its CVS repository). If this is not fixed in time, we might drop the
package from Wheezy.

Regards,

-- 
Mehdi Dogguy



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

Bug#678783: flightgear: diff for NMU version 2.4.0-1.2

[Mehdi Dogguy]

tags 678783 + patch
tags 678783 + pending
thanks

Dear maintainer,

I've prepared an NMU for flightgear (versioned as 2.4.0-1.2) and
uploaded it to DELAYED/5. Please feel free to tell me if I
should delay it longer.

I took the liberty to choose 5 (instead of 10) because last upload was
an NMU and last maintainer's upload dates back to September 2011.

Regards.

-- 
Mehdi Dogguy
diff -u flightgear-2.4.0/config.sub flightgear-2.4.0/config.sub
--- flightgear-2.4.0/config.sub
+++ flightgear-2.4.0/config.sub
@@ -4,7 +4,7 @@
 #   2000, 2001, 2002, 2003, 2004, 2005, 2006, 2007, 2008, 2009, 2010,
 #   2011, 2012 Free Software Foundation, Inc.
 
-timestamp='2012-02-10'
+timestamp='2012-04-18'
 
 # This file is (in principle) common to ALL GNU software.
 # The presence of a machine in this file suggests that SOME GNU software
@@ -225,6 +225,12 @@
 	-isc*)
 		basic_machine=`echo $1 | sed -e 's/86-.*/86-pc/'`
 		;;
+	-lynx*178)
+		os=-lynxos178
+		;;
+	-lynx*5)
+		os=-lynxos5
+		;;
 	-lynx*)
 		os=-lynxos
 		;;
@@ -1537,6 +1543,9 @@
 	c4x-* | tic4x-*)
 		os=-coff
 		;;
+	hexagon-*)
+		os=-elf
+		;;
 	tic54x-*)
 		os=-coff
 		;;
diff -u flightgear-2.4.0/debian/changelog flightgear-2.4.0/debian/changelog
--- flightgear-2.4.0/debian/changelog
+++ flightgear-2.4.0/debian/changelog
@@ -1,3 +1,11 @@
+flightgear (2.4.0-1.2) unstable; urgency=high
+
+  * Non-maintainer upload.
+  * Fix FTBFS with svn 1.7 by adding missing include statement. (Closes: #678783).
+  * Set urgency=high to fix the RC bug.
+
+ -- Mehdi Dogguy   Wed, 27 Jun 2012 17:39:22 +0200
+
 flightgear (2.4.0-1.1) unstable; urgency=low
 
   * Non-maintainer upload.
diff -u flightgear-2.4.0/utils/TerraSync/terrasync.cxx flightgear-2.4.0/utils/TerraSync/terrasync.cxx
--- flightgear-2.4.0/utils/TerraSync/terrasync.cxx
+++ flightgear-2.4.0/utils/TerraSync/terrasync.cxx
@@ -64,6 +64,7 @@
 #include 
 #include 
 #include 
+#include 
 #  else
 #undef HAVE_SVN_CLIENT_H
 #  endif

Processed: flightgear: diff for NMU version 2.4.0-1.2

[Debian Bug Tracking System]

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

> tags 678783 + patch
Bug #678783 [src:flightgear] flightgear: FTBFS: terrasync.cxx:133:14: error: 
'svn_version_checklist_t' does not name a type
Added tag(s) patch.
> tags 678783 + pending
Bug #678783 [src:flightgear] flightgear: FTBFS: terrasync.cxx:133:14: error: 
'svn_version_checklist_t' does not name a type
Added tag(s) pending.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
678783: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=678783
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#679067: marked as done (urlparse: AttributeError: 'module' object has no attribute 'uses_fragment')

[Debian Bug Tracking System]

Your message dated Wed, 27 Jun 2012 16:06:54 +
with message-id 
and subject line Bug#679067: fixed in yum 3.2.25-2
has caused the Debian Bug report #679067,
regarding urlparse: AttributeError: 'module' object has no attribute 
'uses_fragment'
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.)


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

Dear Maintainer,

Yum is suffering from a widely reported bug related to recent python upgrade(s).
Please consider fixing this by changing

> urlparse.uses_fragment.append("media")

to 

> try:
>urlparse.uses_fragment.append("media")
> except AttributeError, err:
>print err

in both 
/usr/lib/pymodules/python2.7/yum/yumRepo.py
and
/usr/lib/pymodules/python2.7/yum/packages.py

Thank you for your consideration.

Sincerely, Joh

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

Kernel: Linux 3.2.0-2-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_US.utf8, LC_CTYPE=en_US.utf8 (charmap=UTF-8) (ignored: LC_ALL 
set to en_US.utf8)
Shell: /bin/sh linked to /bin/dash

Versions of packages yum depends on:
ii  python   2.7.3~rc2-1
ii  python-libxml2   2.8.0+dfsg1-4
ii  python-rpm   4.10.0-2
ii  python-sqlite1.0.1-9
ii  python-sqlitecachec  1.1.2-1+b2
ii  python-support   1.0.14
ii  python-urlgrabber3.9.1-4
ii  rpm  4.10.0-2

yum recommends no packages.

yum suggests no packages.

-- no debconf information


--- End Message ---
--- Begin Message ---
Source: yum
Source-Version: 3.2.25-2

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

yum_3.2.25-2.diff.gz
  to main/y/yum/yum_3.2.25-2.diff.gz
yum_3.2.25-2.dsc
  to main/y/yum/yum_3.2.25-2.dsc
yum_3.2.25-2_all.deb
  to main/y/yum/yum_3.2.25-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 679...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Thomas Goirand  (supplier of updated yum 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, 27 Jun 2012 15:19:14 +
Source: yum
Binary: yum
Architecture: source all
Version: 3.2.25-2
Distribution: unstable
Urgency: low
Maintainer: Thomas Goirand 
Changed-By: Thomas Goirand 
Description: 
 yum- Advanced front-end for rpm
Closes: 679067
Changes: 
 yum (3.2.25-2) unstable; urgency=low
 .
   * Fixes crash at start of yum with error: urlparse: AttributeError: 'module'
   object has no attribute 'uses_fragment' (Closes: #679067).
   * Using z...@debian.org as maintainer email.
Checksums-Sha1: 
 eb1b3aed262147014f5ec824bfab1183e0423546 1068 yum_3.2.25-2.dsc
 4231a31887d3a3f65902eeb28d64119e0177a744 10409 yum_3.2.25-2.diff.gz
 d089a5f6b14b7281ec04f8d91a1e1b83534a839a 631828 yum_3.2.25-2_all.deb
Checksums-Sha256: 
 ccae414d402ecc22cb5953a333dcd30da4d84406fe050b780633725b1f92dca5 1068 
yum_3.2.25-2.dsc
 450076b1893b6127bed2e6f2be1f008cb455d45656dd76200334cbd3ec50479c 10409 
yum_3.2.25-2.diff.gz
 25628795a497ec055d4c866169fad553c8b5c0f531a5f39d92904f2bf029d9ac 631828 
yum_3.2.25-2_all.deb
Files: 
 e3dbff2d1731f5b24847ca96fea6f82e 1068 admin extra yum_3.2.25-2.dsc
 3ea8fb43134324235d9ef31df144a1cf 10409 admin extra yum_3.2.25-2.diff.gz
 66027e5c7a4274c2b92768198f6f6c2a 631828 admin extra yum_3.2.25-2_all.deb

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

iEYEARECAAYFAk/rJSEACgkQl4M9yZjvmkmS0QCfbCuWSHzBAMjYg9LpBAi0yUxK
l8AAoMn2S4Ws2FEtSM9bt5rE+S6Zx6pa
=FlYl
-END PGP SIGNATURE-


--- End Message ---

Bug#677158: marked as done (openldap: FTBFS on armel: unaligned memory access in mdb, fixed upstream)

[Debian Bug Tracking System]

Your message dated Wed, 27 Jun 2012 16:05:33 +
with message-id 
and subject line Bug#677158: fixed in openldap 2.4.31-1
has caused the Debian Bug report #677158,
regarding openldap: FTBFS on armel: unaligned memory access in mdb, fixed 
upstream
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.)


-- 
677158: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=677158
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: openldap
Version: 2.4.28
Severity: serious
Tags: upstream
Justification: fails to build from source (but built successfully in the past)

openldap is failing to build on armel

https://buildd.debian.org/status/logs.php?pkg=openldap&ver=2.4.28-1.3&arch=armel

due to a unaligned memory access issue, which is in a mdb test
the stack is corrupted so i can't give a backtrace

latest version from upstream fixes this problem. (2.4.28 was released 6 months 
ago)

-- System Information: Debian Release: wheezy/sid
  APT prefers unstable
  APT policy: (101, 'unstable'), (1, 'experimental')
Architecture: armel (armv5tel)

Kernel: Linux 3.4.0-tomoyo-6-gfd64aac (PREEMPT)
Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968)
Shell: /bin/sh linked to /bin/dash


--- End Message ---
--- Begin Message ---
Source: openldap
Source-Version: 2.4.31-1

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

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

Debian distribution maintenance software
pp.
Steve Langasek  (supplier of updated openldap package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Wed, 27 Jun 2012 03:27:34 +
Source: openldap
Binary: slapd slapd-smbk5pwd ldap-utils libldap-2.4-2 libldap-2.4-2-dbg 
libldap2-dev slapd-dbg
Architecture: source amd64
Version: 2.4.31-1
Distribution: unstable
Urgency: low
Maintainer: Debian OpenLDAP Maintainers 

Changed-By: Steve Langasek 
Description: 
 ldap-utils - OpenLDAP utilities
 libldap-2.4-2 - OpenLDAP libraries
 libldap-2.4-2-dbg - Debugging information for OpenLDAP libraries
 libldap2-dev - OpenLDAP development libraries
 slapd  - OpenLDAP server (slapd)
 slapd-dbg  - Debugging information for the OpenLDAP server (slapd)
 slapd-smbk5pwd - Keeps Samba and Kerberos passwords in sync within slapd.
Closes: 654824 662940 663644 663724 664930 666230 677158
Changes: 
 openldap (2.4.31-1) unstable; urgency=low
 .
   * New upstream release.
 - Fixes a denial of service attack, CVE-2012-1164, when using the rwm
   overlay.  Closes: #663644.
 - Fixes a bug with ldap_result always returning -1 when called from
   sssd.  Closes: #666230.
 - Fix a build failure on armel due to unaligned memory access.
   Closes: #677158.
   * Incorporate NMU (thanks, Julien Cristau, Mattias Ellert):
 - Disable the mdb backend on non-Linux, it looks like it doesn't work
   with linuxthreads (closes: #654824).
 - Backport fix for shell backend configuration.  Closes: #662940.
 .
   [ Peter Marschall ]
   * debian/slapd.scripts-common: avoid grep warnings
   * debian/patches/heimdal-fix: fix arguments of
 hdb_generate_key_set_password().  Closes: #664930
 .
   [ Steve Langasek ]
   * debian/patches/contrib-modules-use-dpkg-buildflags: pass CFLAGS to
 contrib builds.  Thanks to Simon Ruderich .
 Closes: #663724.
Checksums

Bug#664930: marked as done (openldap: FTBFS: smbk5pwd.c:471:4: error: too few arguments to function 'hdb_generate_key_set_password')

[Debian Bug Tracking System]

Your message dated Wed, 27 Jun 2012 16:05:33 +
with message-id 
and subject line Bug#664930: fixed in openldap 2.4.31-1
has caused the Debian Bug report #664930,
regarding openldap: FTBFS: smbk5pwd.c:471:4: error: too few arguments to 
function 'hdb_generate_key_set_password'
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.)


-- 
664930: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=664930
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: openldap
Version: 2.4.28-1.1
Severity: serious
Tags: wheezy sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20120321 qa-ftbfs
Justification: FTBFS on amd64

Hi,

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

Relevant part:
> ../../../debian/build/libtool --mode=compile gcc -g -O2 -DDO_KRB5 -DDO_SAMBA 
> -DDO_SHADOW -I../../../debian/build/include 
> -I../../../debian/build/servers/slapd -I../../../include 
> -I../../../servers/slapd -I/usr/include  -c smbk5pwd.c
> libtool: compile:  gcc -g -O2 -DDO_KRB5 -DDO_SAMBA -DDO_SHADOW 
> -I../../../debian/build/include -I../../../debian/build/servers/slapd 
> -I../../../include -I../../../servers/slapd -I/usr/include -c smbk5pwd.c  
> -fPIC -DPIC -o .libs/smbk5pwd.o
> smbk5pwd.c: In function 'smbk5pwd_exop_passwd':
> smbk5pwd.c:471:4: warning: passing argument 4 of 
> 'hdb_generate_key_set_password' from incompatible pointer type [enabled by 
> default]
> /usr/include/hdb-protos.h:271:1: note: expected 'struct krb5_key_salt_tuple 
> *' but argument is of type 'struct Key **'
> smbk5pwd.c:471:4: warning: passing argument 5 of 
> 'hdb_generate_key_set_password' makes integer from pointer without a cast 
> [enabled by default]
> /usr/include/hdb-protos.h:271:1: note: expected 'int' but argument is of type 
> 'size_t *'
> smbk5pwd.c:471:4: error: too few arguments to function 
> 'hdb_generate_key_set_password'
> /usr/include/hdb-protos.h:271:1: note: declared here
> smbk5pwd.c: In function 'smbk5pwd_modules_init':
> smbk5pwd.c:1024:4: warning: 'krb5_get_error_string' is deprecated (declared 
> at /usr/include/krb5-protos.h:2157) [-Wdeprecated-declarations]
> smbk5pwd.c:1026:5: warning: 'krb5_get_err_text' is deprecated (declared at 
> /usr/include/krb5-protos.h:2146) [-Wdeprecated-declarations]
> smbk5pwd.c:1031:5: warning: 'krb5_free_error_string' is deprecated (declared 
> at /usr/include/krb5-protos.h:1926) [-Wdeprecated-declarations]
> make[2]: *** [smbk5pwd.lo] Error 1

The full build log is available from:
   http://people.debian.org/~lucas/logs/2012/03/21/openldap_2.4.28-1.1.log

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

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


--- End Message ---
--- Begin Message ---
Source: openldap
Source-Version: 2.4.31-1

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

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

Debian distribution maintenance software
pp.
Steve Langasek  (supplier of updated openldap package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Wed, 27 Jun 2012 03:27:34 +

Bug#666230: marked as done (libldap-2.4-2: ldap_result returns -1 when called from sssd)

[Debian Bug Tracking System]

Your message dated Wed, 27 Jun 2012 16:05:33 +
with message-id 
and subject line Bug#666230: fixed in openldap 2.4.31-1
has caused the Debian Bug report #666230,
regarding libldap-2.4-2: ldap_result returns -1 when called from sssd
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.)


-- 
666230: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=666230
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: libldap-2.4-2
Version: 2.4.28-1.2
Severity: serious
Tags: upstream patch
Justification: breaks unrelated software on the system (which is rc-critical as 
per http://release.debian.org/wheezy/rc_policy.txt)

After an upgrade from 2.4.25, sssd ldap lookups stop working due to ldap_result 
returning -1 even on success.

Please see https://bugs.launchpad.net/ubuntu/+source/openldap/+bug/929888 for 
details on the bug and
http://www.openldap.org/its/index.cgi?findid=7167 for a patch.

Cheers,
Juha

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

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

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


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

Kernel: Linux 3.2.0-1-amd64 (SMP w/2 CPU cores)
Locale: LANG=C, LC_CTYPE=C (charmap=UTF-8) (ignored: LC_ALL set to en_GB.UTF-8)
Shell: /bin/sh linked to /bin/bash

Versions of packages libldap-2.4-2 depends on:
ii  libc6  2.13-27
ii  libgcrypt111.5.0-3
ii  libgnutls262.12.18-1
ii  libsasl2-2 2.1.25.dfsg1-4
ii  multiarch-support  2.13-27

libldap-2.4-2 recommends no packages.

libldap-2.4-2 suggests no packages.

-- Configuration Files:
/etc/ldap/ldap.conf changed [not included]

-- no debconf information

-- debsums errors found:
debsums: package libldap-2.4-2 is not installed


--- End Message ---
--- Begin Message ---
Source: openldap
Source-Version: 2.4.31-1

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

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

Debian distribution maintenance software
pp.
Steve Langasek  (supplier of updated openldap package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Wed, 27 Jun 2012 03:27:34 +
Source: openldap
Binary: slapd slapd-smbk5pwd ldap-utils libldap-2.4-2 libldap-2.4-2-dbg 
libldap2-dev slapd-dbg
Architecture: source amd64
Version: 2.4.31-1
Distribution: unstable
Urgency: low
Maintainer: Debian OpenLDAP Maintainers 

Changed-By: Steve Langasek 
Description: 
 ldap-utils - OpenLDAP utilities
 libldap-2.4-2 - OpenLDAP libraries
 libldap-2.4-2-dbg - Debugging information for OpenLDAP libraries
 libldap2-dev - OpenLDAP development libraries
 slapd  - OpenLDAP server (slapd)
 slapd-dbg  - Debugging information for the OpenLDAP server (slapd)
 slapd-smbk5pwd - Keeps Samba and Kerberos passwords in sync within slapd.
Closes: 654824 662940 663644 663724 664930 666230 677158
Changes: 
 openldap (2.4.31-1) unstable; urgency=low
 .
   * New upstream release.
 - Fixes a denial of service attack, CVE-2012-1164,