Bug#769865: mariadb-10.0: FTBFS on i386

[Ivo De Decker]

package: mariadb-10.0
version: 10.0.14-3
severity: serious

Hi,

The latest upload if mariadb-10.0 failed during the testsuite on i386:

https://buildd.debian.org/status/package.php?p=mariadb-10.0
https://buildd.debian.org/status/fetch.php?pkg=mariadb-10.0&arch=i386&ver=10.0.14-3&stamp=1416208329

A number of architectures are still building at this point, so the issue might
not be specific to i386 (but mips, mipsel and ppc64el built fine).

Cheers,

Ivo


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

Bug#609537:

[Otto Kekäläinen]

Hello!

In MariaDB the script has a section that waits for a long time so that
even the biggest and busiests databases will have enough time to shut
down:

  for i in `seq 1 600`; do
sleep 1
if mysqld_status check_dead nowarn; then server_down=1; break; fi
  done
  if test -z "$server_down"; then killall -9 mysqld; fi

See in context at
http://anonscm.debian.org/cgit/pkg-mysql/mariadb-10.0.git/tree/debian/mariadb-server-10.0.mysql.init#n146

This solution could easily be copied to mysql too, do you want me to
git push it?


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

Bug#769072: gnome-shell: GNOME Shell crashing with "Oh no, something went wrong"

[Simon McVittie]

Control: retitle 769072 libgl1-nvidia-glx and xserver-xorg-core but no 
xserver-xorg-video-nvidia breaks OpenGL

On Sun, 16 Nov 2014 at 01:26:53 +0100, Andreas Beckmann wrote:
> I don't think I can express this with package relationships:
> 
> libgl1-nvidia-glx needs to be installed
>   (1) together with xserver-xorg-video-nvidia (and xserver-xorg-core)
>   (regular installation on a host)
>   (2) OR without xserver-xorg-core (and xserver-xorg-video-nvidia)
>   (i.e. libraries from a foreign architecture only or in a chroot
>without own xserver)
> i.e. only the combination
>   install libgl1-nvidia-glx:native
>   install xserver-xorg-core:native
>   no-install xserver-xorg-video-nvidia
> should be forbidden.

Attempting to summarize that in < 100 characters as a new title, to
make sure this bug won't attract reports of any unrelated GNOME Shell
issues that happen to have the same symptoms.

Sorry, I can't see any way to express this requirement in dpkg dependencies
either.

S


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

Processed: Re: Bug#769072: gnome-shell: GNOME Shell crashing with "Oh no, something went wrong"

[Debian Bug Tracking System]

Processing control commands:

> retitle 769072 libgl1-nvidia-glx and xserver-xorg-core but no 
> xserver-xorg-video-nvidia breaks OpenGL
Bug #769072 [gnome-shell] gnome-shell: GNOME Shell crashing with "Oh no, 
something went wrong"
Changed Bug title to 'libgl1-nvidia-glx and xserver-xorg-core but no 
xserver-xorg-video-nvidia breaks OpenGL' from 'gnome-shell: GNOME Shell 
crashing with "Oh no, something went wrong"'

-- 
769072: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=769072
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#769328: plinth: no web page when started form boot, work when started from command line

[Sunil Mohan Adapa]

Hello,

I have a good picture of the problem and I have revamped Plinth's Apache
configuration to fix various problems.  The pull request is waiting for
review.

https://github.com/freedombox/Plinth/pull/25

The attached patch cleans up Plinth's Apache configuration in
freedombox-setup.

This bug will be fixed in Plinth's upstream and freedombox-setup package.

-- 
Sunil
From 0078a6a24c5e1961d5cd17f9a9956550818ddcb2 Mon Sep 17 00:00:00 2001
From: Sunil Mohan Adapa 
Date: Mon, 17 Nov 2014 14:30:48 +0530
Subject: [PATCH] Cleanup Plinth's Apache configuration

- Plinth related SSL redirection is no longer required in fbx.conf.

- Plinth no-longer hijacks default SSL site configuration.  Enable
  default SSL site configuration to compensate.

- Plinth's deault configuration works just fine, don't disable it.

- The change is need for the latest Plinth's Apache configuration
  changes at https://github.com/freedombox/Plinth/pull/25

- Newer version of FreedomBox setup should depend on Plinth > 0.4.1.
---
 debian/changelog   |  6 ++
 setup.d/90_apache2 | 12 +---
 2 files changed, 7 insertions(+), 11 deletions(-)

diff --git a/debian/changelog b/debian/changelog
index 4df0d71..40f4f69 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,5 +1,11 @@
 freedombox-setup (0.3) UNRELEASED; urgency=low
 
+  [ Sunil Mohan Adapa ]
+  * Cleanup Plinth's Apache configuration.  Default SSL site is no
+longer hijacked.  Plinth supplied configuration is good enough
+don't interfere.
+
+  [ Petter Reinholdtsen ]
   * Adjust debian/tests/test-chroot to build using unstable instead of
 testing.  We are focusing on unstable for now.
 
diff --git a/setup.d/90_apache2 b/setup.d/90_apache2
index 3ff6405..10b32f9 100755
--- a/setup.d/90_apache2
+++ b/setup.d/90_apache2
@@ -13,11 +13,6 @@ a2enmod ssl
 # disable default site
 a2dissite 000-default
 
-# disable plinth, if plinth-ssl is enabled
-if [ -e /etc/apache2/sites-enabled/plinth-ssl.conf ] ; then
-a2dissite plinth
-fi
-
 # setup freedombox site
 cat > /etc/apache2/sites-available/fbx.conf <<'EOF'
 
@@ -36,15 +31,10 @@ cat > /etc/apache2/sites-available/fbx.conf <<'EOF'
   
 Allow from all
   
-
-  ## Send plinth to HTTPS port handled by plinth.conf.
-  RewriteEngine on
-  ReWriteCond %{REQUEST_URI} ^/plinth
-  ReWriteCond %{SERVER_PORT} !^443$
-  RewriteRule ^/(.*) https://%{HTTP_HOST}/$1 [NC,R,L]
 
 EOF
 
 a2ensite fbx
+a2ensite default-ssl
 
 echo "Done configuring Apache."
-- 
2.1.1



signature.asc
Description: OpenPGP digital signature

Bug#768237: fixed in zeroinstall-injector 2.7-2

[Thomas Leonard]

On 16 November 2014 18:25, Adam D. Barratt  wrote:
> Control: reopen -1
>
> Hi,
>
> On Sun, 2014-11-16 at 15:21 +, Thomas Leonard wrote:
>> Changes:
>>  zeroinstall-injector (2.7-2) unstable; urgency=medium
>>  .
>>* Remove old conffile and directory when upgrading from the old
>>  zeroinstall-injector package. Closes: #768237
>
> Thanks for working on this bug.
>
> I was looking at the patch in order to unblock the package for migration
> to jessie, but unfortunately the fix is incomplete. As noted in
> dpkg-maintscript-helper(1), in order to use dir_to_symlink you need a
> "Pre-Depends: dpkg (>= 1.17.5)" as wheezy's dpkg-m-h does not understand
> the command.

Hopefully fixed now.


-- 
Dr Thomas Leonardhttp://0install.net/
GPG: 9242 9807 C985 3C07 44A6  8B9A AE07 8280 59A5 3CC1
GPG: DA98 25AE CAD0 8975 7CDA  BD8E 0713 3F96 CA74 D8BA


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

Processed: Re: Bug#758600: shibboleth-sp2-utils: postinst fails on initial installation

[Debian Bug Tracking System]

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

> tag 758600 + patch
Bug #758600 [shibboleth-sp2-utils] shibboleth-sp2-utils: postinst fails on 
initial installation
Added tag(s) patch.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
758600: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=758600
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#769865: [debian-mysql] Bug#769865: mariadb-10.0: FTBFS on i386

[Otto Kekäläinen]

Just for the record: I have done a test build and ran the test suites,
but it seems my pbuilder skips this test so it wasn't caught:

http://labs.seravo.fi/~otto/mariadb-repo/mariadb-10.0-sid-i386/mariadb-10.0_10.0.14-3_amd64.build-7b8f5e6-pbuilder.log

   plugins.unix_socket  [ skipped ]  $USER=root
which exists in mysql.user


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

Bug#769865: [debian-mysql] Bug#769865: mariadb-10.0: FTBFS on i386

[Otto Kekäläinen]

> The latest upload if mariadb-10.0 failed during the testsuite on i386:
>
> https://buildd.debian.org/status/package.php?p=mariadb-10.0
> https://buildd.debian.org/status/fetch.php?pkg=mariadb-10.0&arch=i386&ver=10.0.14-3&stamp=1416208329
>
> A number of architectures are still building at this point, so the issue might
> not be specific to i386 (but mips, mipsel and ppc64el built fine).

Thanks for reporting this. I've localized the root cause and pushed a fix:
http://anonscm.debian.org/cgit/pkg-mysql/mariadb-10.0.git/commit/debian/patches/username-in-tests-replace.patch?id=c413d37ab10b7c817d00f3a41bfac569736c6e4a

Now we need to upload mariadb-10.0.14-4, all builds are likely to fail
with current revision.


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

Bug#769865: [debian-mysql] Bug#769865: mariadb-10.0: FTBFS on i386

[Arnaud Fontaine]

Otto Kekäläinen  writes:

>> The latest upload if mariadb-10.0 failed during the testsuite on i386:
>>
>> https://buildd.debian.org/status/package.php?p=mariadb-10.0
>> https://buildd.debian.org/status/fetch.php?pkg=mariadb-10.0&arch=i386&ver=10.0.14-3&stamp=1416208329
>>
>> A number of architectures are still building at this point, so the issue 
>> might
>> not be specific to i386 (but mips, mipsel and ppc64el built fine).
>
> Thanks for reporting this. I've localized the root cause and pushed a fix:
> http://anonscm.debian.org/cgit/pkg-mysql/mariadb-10.0.git/commit/debian/patches/username-in-tests-replace.patch?id=c413d37ab10b7c817d00f3a41bfac569736c6e4a
>
> Now we need to upload mariadb-10.0.14-4, all builds are likely to fail
> with current revision.

Do you need me to upload it?

Cheers,
-- 
Arnaud Fontaine


signature.asc
Description: PGP signature

Bug#766241: gnome: dist-upgrade on 20-Oct lost gnome pixbufs and several tweak settings reset

[Jim Cobley]

Have checked dpkg.log for the date of the problem. The version of dpkg 
doesn't appear to be listed.

Problem has not recurred


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

Bug#767676: ola-rdm-tests: fails to install: subprocess installed post-installation script returned error exit status 10

[Jean Baptiste Favre]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Hello,
I just uploaded ola source package on mentors.debian.net

You can get it with

dget -x http://mentors.debian.net/debian/pool/main/o/ola/ola_0.9.1-1.1.dsc

Do you mind sponsoring it, or I will fill an RFS bug ?

Regards,
Jean Baptiste


On 17/11/2014 01:00, Wouter Verhelst wrote:
> On Sun, Nov 16, 2014 at 06:12:56PM +0100, Jean Baptiste Favre
> wrote:
>> Hello, I had a look on it during Debian BSP in Paris.
>> 
>> Problem is located into ola-rdm-test.postinst script: - It uses
>> debconf, for variable ola-rdm-tests/daemon, without providing any
>> template file - It uses db_get and never db_input, thus
>> ola-rdm-tests/daemon is never set - debconf is not mentioned as
>> dependency
>> 
>> Please find attached a patch which removes debconf usage from
>> postinst script.
> 
> Thanks.
> 
> Feel free to NMU; I do need to talk to debian-release about some
> other things, but this should be straightforward enough that it
> shouldn't interfere with that.
> 


-BEGIN PGP SIGNATURE-
Version: GnuPG v1

iQJ8BAEBCgBmBQJUac6kXxSAAC4AKGlzc3Vlci1mcHJAbm90YXRpb25zLm9w
ZW5wZ3AuZmlmdGhob3JzZW1hbi5uZXQ0RTg0NUJBMjMwQ0I0RDQ0ODkwNjk4NDdC
NERENTM2QUNGN0Q4NzM3AAoJELTdU2rPfYc3430QALDR4VMcSnJL1ASWCR4vkJnY
ndlF8G2jOqm1kRVuwbty4pUnZ6Rmq7RTlRe/GNBXuo0/2PU+CYOqHXJcBwMzGaKa
qAw/kn/+caWENOhWNMpBx6bmTa9k8kHX+3CSfXEo0bb4SF6Hut5eatAC3GfTzoIW
D4C0tQ8csW4brYcOF0jOtJEX30KX82KHhJXxdtlyarNpBb+XnesnSlClt61yqjNA
UOjczgkJHc/MGBvwd3gVbj05PbVSvIeIh+kh1wkqWldtjCklKvgy3+6MCUhrzHqX
LCmiiYqkmopPkYZ7sK3/9l4I5/9+/X5BDrrlKCbN3jyLE465U/DZVZrfj1Y7UCfy
xC1p+Lfc9JMFKSLbeky0JzQ6FCJqBFfTahGDkcai9w0r9nptNULWUFl+BEi0vN3K
9IXrddyysBgjwTc2rH+lnLZ/05jpNQNez4sshoAdQKYEQbLQNWbXEVSrFeJIRKQc
OMrcWZFOOJca1hXMJbBeAbqC+nz3Q0/whY9WW6wJSjx/I2Ce24oW1ELjz+9BCW4U
kHnPc1yPqexKSWNjRczgfp2BG/lYS6tYMlX899/qrK0aCTSsmp6F2preKWe+3FrY
SqtqMLbS7CFWY8Rfst44C0VCfRbfFyia250ILIMQqZFPD8oF+g6hvE9zvEtyKqIx
NNsk965tWhn77cHOnMBy
=aswP
-END PGP SIGNATURE-


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

Bug#768617: [Pkg-middleware-maintainers] Bug#768617: Bug#768617: qpid-proton: FTBFS in jessie: build-dependency not installable: libsslcommon2-dev

[Daniel Pocock]

On 11/11/14 15:11, Lucas Nussbaum wrote:
> On 11/11/14 at 08:07 -0500, Darryl L. Pierce wrote:
>> I've fixed the cause for this by updating the dependency from
>> libsslcommon2 to libssl in 0.7-7. How do I get this update in the build
>> stream for Jessie?
> Hi Darryl,
>
> Get the fix in unstable, keeping changes to a minimum.
> Then request an unblock. See
> https://lists.debian.org/debian-devel-announce/2014/11/msg3.html
>
> Thanks!
>
> Lucas


Lucas, thanks for reporting the issue, Darryl fixed it and I'm
sponsoring the upload right now

This upload is based on the last debdiff in the unblock request #769122
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=769122#71


diff -Nru qpid-proton-0.7/debian/changelog qpid-proton-0.7/debian/changelog
--- qpid-proton-0.7/debian/changelog2014-06-02 22:05:32.0 +0200
+++ qpid-proton-0.7/debian/changelog2014-11-17 11:25:04.0 +0100
@@ -1,3 +1,11 @@
+qpid-proton (0.7-2) unstable; urgency=low
+
+  * Change dependency from libsslcommon2-dev to libssl-dev. (Closes: #768617)
+  * Bumped Standards-Version to 3.9.6.
+  * Added support for dh_python2.
+
+ -- Darryl L. Pierce   Wed, 12 Nov 2014 15:58:45 -0500
+
 qpid-proton (0.7-1) unstable; urgency=low
 
   * Initial release. (Closes: #732302)
diff -Nru qpid-proton-0.7/debian/control qpid-proton-0.7/debian/control
--- qpid-proton-0.7/debian/control  2014-06-02 22:57:51.0 +0200
+++ qpid-proton-0.7/debian/control  2014-11-17 11:24:19.0 +0100
@@ -9,11 +9,12 @@
   pkg-config,
   doxygen,
   uuid-dev,
-  libsslcommon2-dev,
+  libssl-dev,
+  dh-python,
   python-epydoc,
   python (>=2.6.6-3~),
   python-dev (>=2.6.6-3~)
-Standards-Version: 3.9.3
+Standards-Version: 3.9.6
 Homepage: http://qpid.apache.org/proton
 Vcs-Browser: http://git.debian.org/?p=pkg-middleware/qpid-proton.git
 Vcs-Git: git://git.debian.org/git/pkg-middleware/qpid-proton.git
diff -Nru qpid-proton-0.7/debian/rules qpid-proton-0.7/debian/rules
--- qpid-proton-0.7/debian/rules2014-06-02 22:49:30.0 +0200
+++ qpid-proton-0.7/debian/rules2014-11-17 11:16:22.0 +0100
@@ -22,7 +22,7 @@
 export DH_ALWAYS_EXCLUDE=LICENSE
 
 %:
-   dh $@
+   dh $@ --with python2
 
 override_dh_auto_configure:
dh_auto_configure -- -DPROTON_DISABLE_RPATH=true -DNOBUILD_RUBY=on 
-DSYSINSTALL_BINDINGS=on

Bug#768617: marked as done (qpid-proton: FTBFS in jessie: build-dependency not installable: libsslcommon2-dev)

[Debian Bug Tracking System]

Your message dated Mon, 17 Nov 2014 10:49:08 +
with message-id 
and subject line Bug#768617: fixed in qpid-proton 0.7-2
has caused the Debian Bug report #768617,
regarding qpid-proton: FTBFS in jessie: build-dependency not installable: 
libsslcommon2-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.)


-- 
768617: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=768617
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: qpid-proton
Version: 0.7-1
Severity: serious
Tags: jessie sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20141108 qa-ftbfs
Justification: FTBFS in jessie on amd64

Hi,

During a rebuild of all packages in jessie (in a jessie chroot, not a
sid chroot), your package failed to build on amd64.

Relevant part (hopefully):
> ┌──┐
> │ Install qpid-proton 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-qpid-proton-dummy : Depends: libsslcommon2-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://aws-logs.debian.net/ftbfs-logs/2014/11/08/qpid-proton_0.7-1_jessie.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: qpid-proton
Source-Version: 0.7-2

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

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 768...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Darryl L. Pierce  (supplier of updated qpid-proton 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...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Wed, 12 Nov 2014 15:58:45 -0500
Source: qpid-proton
Binary: qpid-proton-dump libqpid-proton2 libqpid-proton2-dev 
libqpid-proton2-dev-examples libqpid-proton2-dev-doc python-qpid-proton 
python-qpid-proton-doc
Architecture: source amd64 all
Version: 0.7-2
Distribution: unstable
Urgency: low
Maintainer: Debian Middleware Maintainers 

Changed-By: Darryl L. Pierce 
Description:
 libqpid-proton2 - C libraries for Qpid Proton
 libqpid-proton2-dev - Development libraries for writing messaging apps with 
Qpid Proton
 libqpid-proton2-dev-doc - Developer documentation for Qpid Proton
 libqpid-proton2-dev-examples - Example applications for writign messaging apps 
with Qpid Proton
 python-qpid-proton - Python language bindings for Qpid Proton messaging 
framework
 python-qpid-proton-doc - Documentation for the Python language bindings for 
Qpid Proton
 qpid-proton-dump - Qpid Proton messaging tools
Closes: 768617
Changes:
 qpid-proton (0.7-2) unstable; urgency=low
 .
   * Change dependency from libsslcommon2-dev to libssl-dev. (Closes: #768617)
   * Bumped Standards-Version to 3.9.6.
   * Added support for dh_python2.
Checksums-Sha1:
 74a52c011ce1139d808e206412caf4f20a10f256 2577 qpid-proton_0.7-2.dsc
 95d5d0b8674a4db46e07b2fad499b27dc379a0f6 3860 qpid-proton_0.7-2.debian.tar.xz
 d09e8aac17dfa193fcf5c70c537065bb32f94aa3 5798 qpid-proton-dump_0.7-2_amd64.deb
 a7aa2e2d06bfc5b46c9ff641872c72c5e063c009 99124 libqpid-proton2_0.7-2_amd64.deb
 722d28bd44c94fa0c921582dfa8d60626ebe5f83 42436 
libqpid-proton2-dev_0.7-2_amd64.deb
 fac986e7cdb84b06

Bug#767194: marked as done (util-linux upgrade synchronously starts fstrim multiple times)

[Debian Bug Tracking System]

Your message dated Mon, 17 Nov 2014 10:49:36 +
with message-id 
and subject line Bug#767194: fixed in util-linux 2.25.2-3
has caused the Debian Bug report #767194,
regarding util-linux upgrade synchronously starts fstrim multiple times
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.)


-- 
767194: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=767194
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: util-linux
Severity: important
Version: 2.25.2-2

Upgrading util-linux to current version hangs a very long time (I
waited some 10 mintues). I noticed that fstrim was running, which is
apparently started by this autogenerated snippet in postinst:

# Automatically added by dh_systemd_start
if [ -d /run/systemd/system ]; then
systemctl --system daemon-reload >/dev/null || true
deb-systemd-invoke start fstrim.service fstrim.timer >/dev/null || true
fi

Even worse, as postinst doesn't check $1 this happens multiple times,
each time update-initramfs gets triggered.

IMHO this is undesired. fstrim ought to run in the background and not
block the whole upgrade. So this probably needs some --no-start
dh_installinit argument in debian/rules?

Thanks,

Martin

-- 
Martin Pitt| http://www.piware.de
Ubuntu Developer (www.ubuntu.com)  | Debian Developer  (www.debian.org)


signature.asc
Description: Digital signature
--- End Message ---
--- Begin Message ---
Source: util-linux
Source-Version: 2.25.2-3

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

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 767...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Andreas Henriksson  (supplier of updated util-linux 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...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Thu, 06 Nov 2014 13:54:04 +0100
Source: util-linux
Binary: util-linux util-linux-locales mount bsdutils fdisk-udeb cfdisk-udeb 
libblkid1 libblkid1-udeb libblkid-dev libmount1 libmount-dev libsmartcols1 
libsmartcols1-udeb libsmartcols-dev libuuid1 uuid-runtime libuuid1-udeb 
uuid-dev util-linux-udeb
Architecture: source amd64 all
Version: 2.25.2-3
Distribution: unstable
Urgency: medium
Maintainer: Debian util-linux Maintainers 
Changed-By: Andreas Henriksson 
Description:
 bsdutils   - basic utilities from 4.4BSD-Lite
 cfdisk-udeb - Manually partition a hard drive (cfdisk) (udeb)
 fdisk-udeb - Manually partition a hard drive (fdisk) (udeb)
 libblkid-dev - block device id library - headers and static libraries
 libblkid1  - block device id library
 libblkid1-udeb - stripped down block device id library, for debian-installer 
(udeb)
 libmount-dev - device mounting library - headers and static libraries
 libmount1  - device mounting library
 libsmartcols-dev - smart column output alignment library - headers and static 
librar
 libsmartcols1 - smart column output alignment library
 libsmartcols1-udeb - stripped down smart column output aligment library, for 
debian-in (udeb)
 libuuid1   - Universally Unique ID library
 libuuid1-udeb - stripped down universally unique id library, for 
debian-installer (udeb)
 mount  - Tools for mounting and manipulating filesystems
 util-linux - Miscellaneous system utilities
 util-linux-locales - Locales files for util-linux
 util-linux-udeb - stripped down miscellaneous system utilities, for 
debian-installe (udeb)
 uuid-dev   - universally unique id library - headers and static libraries
 uuid-runtime - runtime components for the Universally Unique ID library
Closes: 767194
Changes:
 util-linux (2.25.2-3) unstable; urgency=medium
 .
   * Ship fstrim timer/service units as examples only (Closes: #767194)
 - this works around #757891 and #767429 / #760168
Checksums-Sha1:
 a4a5f5bf072f43b7f1fc4793048e395b7907c0c1 3440 util-linux_2.25.2-3.dsc
 91d62c10a7def1c7399455eca46988c079dbb2f5 66756 
util-linux_2.25.2-3.debian.tar.xz
 832b828c001767bf66591a8c6a8c246282c9d16f 93172 bsdutils_2.25.2-3_amd64.deb
 c04a495f26e00be3ff9c481c846d59248a6eaa20 843632 util-linux_2.25.2-3_amd64.deb
 5762c949ae2b2f845159896744a438affa477596 832938 
util-linux-locales_2.25.2

Bug#769888: wine-development: Wrong Build-Depends in debian/control file

[Maxime Lombard]

Source: wine-development
Version: 1.7.29-3
Severity: serious
Tags: patch
Justification: fails to build from source (but built successfully in the past)

Dear Maintainer,

Actually, it's impossible to download the build-dependances of wine-development 
package (apt-get build-dep wine-development:i386).
I have this error after to launch the previous command :

"E: Impossible to satisfy dependences Build-Depends for wine-development : 
libtiff-dev"

If I check in "https://packages.debian.org/";, "libtiff-dev" package does not 
exist. There are only "libtiff4-dev" package (oldlibs)
and "libtiff5-dev" (libdevel).

Thanks to correct this error to build myself Wine (wine-git) in a chroot.

Cheers,
Max

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

Kernel: Linux 3.16.0-4-amd64 (SMP w/4 CPU cores)
Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
--- debian/control	2014-11-02 04:44:58.0 +0100
+++ debian/control	2014-11-17 11:40:56.594114565 +0100
@@ -35,7 +35,7 @@
  libxml2-dev,
  libgsm1-dev,
  libjpeg-dev,
- libtiff-dev,
+ libtiff5-dev,
  libpcap-dev,
  liblcms2-dev,
  libldap2-dev,

Processed: severity of 769887 is critical, tagging 769887

[Debian Bug Tracking System]

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

> severity 769887 critical
Bug #769887 [activemq] Apache ActiveMQ Packaged with JMX/RMI Enabled
Severity set to 'critical' from 'normal'
> tags 769887 + security
Bug #769887 [activemq] Apache ActiveMQ Packaged with JMX/RMI Enabled
Added tag(s) security.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
769887: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=769887
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#766241: gnome: dist-upgrade on 20-Oct lost gnome pixbufs and several tweak settings reset

[intrigeri]

Hi Jim,

Jim Cobley wrote (17 Nov 2014 10:24:08 GMT) :
> Have checked dpkg.log for the date of the problem. The version of dpkg 
> doesn't appear
> to be listed.

Maybe /var/log/dpkg.log.*, then. Or look at /var/log/apt/*.log* for
the last dpkg upgrade *before* the faulty dist-upgrade.

Cheers,
-- 
intrigeri


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

Processed: jeez

[Debian Bug Tracking System]

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

> tags 769759 + sid jessie
Bug #769759 [tracker-extract] tracker-extract dumps the complete file it cannot 
index to stdout/stderr
Added tag(s) sid and jessie.
>
End of message, stopping processing here.

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

[Youhei SASAKI]

Hi,

Thanks Antonio!

At Wed, 12 Nov 2014 12:31:00 -0200,
Antonio Terceiro  wrote:
> > This bug is unreproducible by my pbuilder/cowbuilder environments.
> > Thus I'll try setup sbuild for check this bug.
> > 
> > If someone who has jessies's sbuild environments, please try rebuild
> > this package and send report me.
> 
> I can't reproduce this with sbuild in either sid or jessie; both build
> just fine.

I'm also fine with sbuild in sid or jessie...

Hmm... What should I(we?) do?

---
Youhei SASAKI 
  
GPG fingerprint:
  4096/RSA: 66A4 EA70 4FE2 4055 8D6A C2E6 9394 F354 891D 7E07


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

Processed: closing 768671

[Debian Bug Tracking System]

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

> close 768671
Bug #768671 [src:jenkins] jenkins: FTBFS in jessie: build-dependency not 
installable: libjson-java
Marked Bug as done
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
768671: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=768671
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#766241: gnome: dist-upgrade on 20-Oct lost gnome pixbufs and several tweak settings reset

[Jim Cobley]

tks for ptr to alt log files!

Checked /var/log/apt/*.log* from 1st Aug to 20th October. The only ref 
to an update to dpkg was dated 31 Aug

dpkg:amd64 (1.17.10, 1.17.13)
same for dpkg-dev and libdpkg-perl

My current version on 17 Nov is 1.17.21


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

Bug#768237: fixed in zeroinstall-injector 2.7-2

[Adam D. Barratt]

On 2014-11-17 9:29, Thomas Leonard wrote:
On 16 November 2014 18:25, Adam D. Barratt  
wrote:

Control: reopen -1

Hi,

On Sun, 2014-11-16 at 15:21 +, Thomas Leonard wrote:

Changes:
 zeroinstall-injector (2.7-2) unstable; urgency=medium
 .
   * Remove old conffile and directory when upgrading from the old
 zeroinstall-injector package. Closes: #768237


Thanks for working on this bug.

I was looking at the patch in order to unblock the package for 
migration

to jessie, but unfortunately the fix is incomplete. As noted in
dpkg-maintscript-helper(1), in order to use dir_to_symlink you need a
"Pre-Depends: dpkg (>= 1.17.5)" as wheezy's dpkg-m-h does not 
understand

the command.


Hopefully fixed now.


Yep, thanks; unblocked.

Regards,

Adam


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

Bug#768671: closing 768671

[Emmanuel Bourg]

close 768671 
thanks

libjson-java is now in testing


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

Bug#769831: marked as done ([testng] Some sources are not included in your package)

[Debian Bug Tracking System]

Your message dated Mon, 17 Nov 2014 13:19:03 +
with message-id 
and subject line Bug#769831: fixed in testng 6.8.8-3
has caused the Debian Bug report #769831,
regarding [testng] Some sources are not included in your package
to be marked as done.

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

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


-- 
769831: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=769831
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: testng
Version: 6.8.8-2
user: lintian-ma...@debian.org
usertags: source-is-missing
severity: serious
X-Debbugs-CC: ftpmas...@debian.org

Hi,

Your package seems to include some files that lack sources
in prefered forms of modification:

src/main/resources/jquery-1.7.1.min.js

According to Debian Free Software Guidelines [1] (DFSG) #2:
 "The program must include source code, and must allow distribution
  in source code as well as compiled form.".

This could also constitute a license violation for some copyleft
licenses such as the GNU GPL.

In order to solve this problem, you could:
1. repack the origin tarball adding the missing source to it.
2  add the source files to "debian/missing-sources" directory

Both way satisfies the requirement that we ship the source. Second option
might be preferable due to the following reasons [2]:
 - Upstream can do it too and you could even supply a patch to them,
thus full filling our social contract [3], see particularly §2.
 - If source and non-source are in different locations, ftpmasters may
   miss the source and (needlessly) reject the package.
 - The source isn't duplicated in every .diff.gz/.debian.tar.* (though
   this only really matters for larger sources).

You could also ask debian...@lists.debian.org or #debian-qa for more
guidance.

Waiting for next upstream release is not sufficient.

[1] https://www.debian.org/social_contract.en.html#guidelines
[2] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=736873#8
[3] https://www.debian.org/social_contract
--- End Message ---
--- Begin Message ---
Source: testng
Source-Version: 6.8.8-3

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

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 769...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Eugene Zhukov  (supplier of updated testng 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...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Mon, 17 Nov 2014 11:43:10 +
Source: testng
Binary: testng
Architecture: source all
Version: 6.8.8-3
Distribution: unstable
Urgency: low
Maintainer: Debian Java Maintainers 

Changed-By: Eugene Zhukov 
Description:
 testng - testing framework for Java
Closes: 769831
Changes:
 testng (6.8.8-3) unstable; urgency=low
 .
   * Dropped orig-tar.sh in favor of jh_repack in d/watch
   * Added source for jquery-1.7.1.min.js (Closes: #769831)
   * Standards-Version updated to version 3.9.6
   * Updated debhelper to version 9 in d/control
Checksums-Sha1:
 1b7df5386a0eed62113963bd93874fdf525ac092 2045 testng_6.8.8-3.dsc
 27cc128a3d60fde9011ad8645dc464316b00a53d 66824 testng_6.8.8-3.debian.tar.xz
 e22ef3523532cf820a634eaf1a1b32814956c52d 752886 testng_6.8.8-3_all.deb
Checksums-Sha256:
 1ae2609fa84f89c74bd47231932685350c365954f308d9c424704642a0fe09b7 2045 
testng_6.8.8-3.dsc
 6cf66a79eb9f6aa9b6c1c76ff296a7ee65d8e551e549fdf4ac101f50bed66f70 66824 
testng_6.8.8-3.debian.tar.xz
 f9818e38f71854436ccde541be3c26a46b117e4f05db0687b88d4eeed35f18d7 752886 
testng_6.8.8-3_all.deb
Files:
 bcf27533eef4c1722a682cbc978faf97 2045 java optional testng_6.8.8-3.dsc
 56840454e854c1cc85894f2320aa4e7a 66824 java optional 
testng_6.8.8-3.debian.tar.xz
 76e0bdd6e4167e676e223d9ba065e9a9 752886 java optional testng_6.8.8-3_all.deb

-BEGIN PGP SIGNATURE-
Version: GnuPG v1

iQIcBAEBCgAGBQJUaeG8AAoJENfTQC4BBmMMUFUQAJG0XzPpx/QYPLxFxH8y0EZ8
P7CIpqaNFLpztFTH7Ehr8yhV4oqexDE0RvFclxJPrHItgZ/eYvEK7VJzGUSAJA3P
eM+DO2jIxgmxMdzMwwo4x56A6s7pM8re8wYnamhJLQqPXx5NSVxlsN+CVryylTyf
TaxmFsZcQSdK8T+bZquXYBNxs3NRHwRijlggu0N43GsCywM4TX3oAFmfjMND/JRk
LBpMEDq8w+8ax8gBSiHs/RpklgnvZaGsbMzr8NU0bqO5qIKQ5ONh45k+AV877ivT
ZSh+mdSAkSA0l0OopQqGMdxUuYaPSAA26TfesN+IyAXKbYkpUQlZxIbEI1nW0zM/
nze80zYfuNdry9ftLmKu1YY9Ox2Z

Bug#743396: nsd: diff for NMU version 4.1.0-1.1

[Ondřej Surý]

Hi Julien,

thanks for taking care of this. Feel free to push this to DELAYED/0 or
upload directly.

Cheers,
Ondrej

On Sun, Nov 16, 2014, at 16:46, Julien Cristau wrote:
> Control: tags 743396 + pending
> 
> Dear maintainer,
> 
> I've prepared an NMU for nsd (versioned as 4.1.0-1.1) and
> uploaded it to DELAYED/2. Please feel free to tell me if I
> should delay it longer.
> 
> Cheers,
> Julien
> Email had 2 attachments:
> + nsd-4.1.0-1.1-nmu.diff
>   3k (text/x-diff)
> + signature.asc
>   1k (application/pgp-signature)


-- 
Ondřej Surý 
Knot DNS (https://www.knot-dns.cz/) – a high-performance DNS server


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

Bug#769348: biomaj-watcher: switch to tomcat8

[Emmanuel Bourg]

Control: tags -1 + patch
Index: debian/README.Debian
===
--- debian/README.Debian(revision 18328)
+++ debian/README.Debian(working copy)
@@ -10,4 +10,4 @@
  http://gwt-google-apis.googlecode.com/svn/tags/visualization/1.1.1


- Biomaj watcher updates the access rights of most of Biomaj directories to add 
write access to the user tomcat6. Indeed, all configuration and bank updates 
will be done via the Tomcat application. Those modifications are needed only 
while biomaj-watcher is installed.
+ Biomaj watcher updates the access rights of most of Biomaj directories to add 
write access to the user tomcat8. Indeed, all configuration and bank updates 
will be done via the Tomcat application. Those modifications are needed only 
while biomaj-watcher is installed.
Index: debian/control
===
--- debian/control  (revision 18328)
+++ debian/control  (working copy)
@@ -21,7 +21,7 @@

 Package: biomaj-watcher
 Architecture: all
-Depends: ${misc:Depends}, default-jdk, tomcat6 (>=6.0.32-3), biomaj (>= 
1.2.1), debconf,
+Depends: ${misc:Depends}, default-jdk, tomcat8, biomaj (>= 1.2.1), debconf,
  liblog4j1.2-java, libjsch-java (>= 0.1.42),libjdom1-java (>= 1.1), 
libcommons-lang-java (>=2.4),
  libcommons-logging-java (>=1.1),libquartz-java(>=1.6),libxerces2-java, unzip, 
zip, libgnumail-java
 Description: biological data-bank updater - web interface
Index: debian/postinst
===
--- debian/postinst (revision 18328)
+++ debian/postinst (working copy)
@@ -48,9 +48,9 @@
   rm -f /usr/share/java/webapps/biomaj-watcher/WEB-INF/lib/gnumail.jar
   ln -s /usr/share/java/gnumail.jar 
/usr/share/java/webapps/biomaj-watcher/WEB-INF/lib/gnumail.jar

-  #cp /usr/share/biomaj/lib/biomaj.jar /var/lib/tomcat6/shared/
-  rm -f /var/lib/tomcat6/shared/biomaj.jar
-  cp /usr/share/biomaj/lib/biomaj.jar /var/lib/tomcat6/shared/biomaj.jar
+  #cp /usr/share/biomaj/lib/biomaj.jar /var/lib/tomcat8/shared/
+  rm -f /var/lib/tomcat8/shared/biomaj.jar
+  cp /usr/share/biomaj/lib/biomaj.jar /var/lib/tomcat8/shared/biomaj.jar
   # Install latest definition
   cp /usr/share/java/webapps/biomaj-watcher/jobs.xsd 
/etc/biomaj-watcher/jobs.xsd

@@ -62,24 +62,24 @@
   # Update logs
   set_perms /var/log/biomaj

-  #chown -R tomcat6 /etc/biomaj/db_properties
-  chown -R tomcat6 /usr/share/java/webapps/biomaj-watcher
+  #chown -R tomcat8 /etc/biomaj/db_properties
+  chown -R tomcat8 /usr/share/java/webapps/biomaj-watcher
   #chmod -R 775 /etc/biomaj/db_properties
-  #chown -R tomcat6 /var/log/biomaj
+  #chown -R tomcat8 /var/log/biomaj
   #chmod -R 775 /var/log/biomaj
-  #chown -R tomcat6 /var/lib/biomaj
+  #chown -R tomcat8 /var/lib/biomaj
   #chmod -R 775 /var/lib/biomaj
-  chown -R tomcat6 /etc/biomaj-watcher
+  chown -R tomcat8 /etc/biomaj-watcher
   # Update context
   java -cp $biomajwatcher_root/bin UpdateToBiomaj1_2 
/usr/share/java/webapps/biomaj-watcher admin
-  chown -R tomcat6 /etc/biomaj-watcher
-  #cp /etc/biomaj-watcher/BmajWatcher*.xml 
/var/lib/tomcat6/conf/Catalina/localhost/
-  rm -f /etc/tomcat6/Catalina/localhost/BmajWatcher.xml
-  rm -f /etc/tomcat6/Catalina/localhost/BmajWatcher#logs.xml
-  ln -s /etc/biomaj-watcher/BmajWatcher.xml 
/etc/tomcat6/Catalina/localhost/BmajWatcher.xml
-  ln -s /etc/biomaj-watcher/BmajWatcher#logs.xml 
/etc/tomcat6/Catalina/localhost/BmajWatcher#logs.xml
+  chown -R tomcat8 /etc/biomaj-watcher
+  #cp /etc/biomaj-watcher/BmajWatcher*.xml 
/var/lib/tomcat8/conf/Catalina/localhost/
+  rm -f /etc/tomcat8/Catalina/localhost/BmajWatcher.xml
+  rm -f /etc/tomcat8/Catalina/localhost/BmajWatcher#logs.xml
+  ln -s /etc/biomaj-watcher/BmajWatcher.xml 
/etc/tomcat8/Catalina/localhost/BmajWatcher.xml
+  ln -s /etc/biomaj-watcher/BmajWatcher#logs.xml 
/etc/tomcat8/Catalina/localhost/BmajWatcher#logs.xml

-  invoke-rc.d tomcat6 restart
+  invoke-rc.d tomcat8 restart


 ;;
Index: debian/postrm
===
--- debian/postrm   (revision 18328)
+++ debian/postrm   (working copy)
@@ -14,20 +14,20 @@
 ;;
 remove|failed-upgrade|abort-install|abort-upgrade|disappear)

-  if [ -e /var/lib/tomcat6/shared/biomaj.jar ]; then
-rm  /var/lib/tomcat6/shared/biomaj.jar
+  if [ -e /var/lib/tomcat8/shared/biomaj.jar ]; then
+rm  /var/lib/tomcat8/shared/biomaj.jar
   fi
-  rm -f /etc/tomcat6/Catalina/localhost/BmajWatcher.xml
-  rm -f /etc/tomcat6/Catalina/localhost/BmajWatcher#logs.xml
+  rm -f /etc/tomcat8/Catalina/localhost/BmajWatcher.xml
+  rm -f /etc/tomcat8/Catalina/localhost/BmajWatcher#logs.xml
   rm -f /usr/share/java/webapps/biom

Processed: Re: biomaj-watcher: switch to tomcat8

[Debian Bug Tracking System]

Processing control commands:

> tags -1 + patch
Bug #769348 [biomaj-watcher] biomaj-watcher: switch to tomcat8
Added tag(s) patch.

-- 
769348: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=769348
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems


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

Processed: severity of 768095 is grave

[Debian Bug Tracking System]

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

> severity 768095 grave
Bug #768095 [openvswitch-datapath-dkms] openvswitch-datapath-dkms fails to 
build on Debian 7.7 3.2.0-4-amd64 (3.2.63-2+deb7u1)
Severity set to 'grave' from 'important'
> thanks
Stopping processing here.

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

[Ondřej Surý]

Control: severity -1 important

Lowering the severity until the bug is confirmed.

Cheers,
-- 
Ondřej Surý 
Knot DNS (https://www.knot-dns.cz/) – a high-performance DNS server
-- 
Ondřej Surý 
Knot DNS (https://www.knot-dns.cz/) – a high-performance DNS server


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

Processed: Changing priority

[Debian Bug Tracking System]

Processing control commands:

> severity -1 important
Bug #768369 [libjpeg62-turbo] [libjpeg62-turbo] [DOS] Stack smashing
Severity set to 'important' from 'serious'

-- 
768369: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=768369
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#769809: marked as done (google-android-sdk-docs-installer: misses Depends: ca-certificates, unzip)

[Debian Bug Tracking System]

Your message dated Mon, 17 Nov 2014 15:34:08 +
with message-id 
and subject line Bug#769809: fixed in google-android-sdk-docs-installer 20.0.0.3
has caused the Debian Bug report #769809,
regarding google-android-sdk-docs-installer: misses Depends: ca-certificates, 
unzip
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.)


-- 
769809: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=769809
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: google-android-sdk-docs-installer
Version: 20.0.0.2
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

during a test with piuparts I noticed your package failed to install. As
per definition of the release team this makes the package too buggy for
a release, thus the severity.

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

  Selecting previously unselected package google-android-sdk-docs-installer.
  (Reading database ... 8837 files and directories currently installed.)
  Preparing to unpack .../google-android-sdk-docs-installer_20.0.0.2_all.deb ...
  Unpacking google-android-sdk-docs-installer (20.0.0.2) ...
  Setting up google-android-sdk-docs-installer (20.0.0.2) ...
  make: Entering directory '/var/cache/google-android-sdk-docs-installer'
  cd /var/cache/google-android-sdk-docs-installer && \
wget --continue 
https://dl-ssl.google.com/android/repository/docs-L_r01.zip
  converted 'https://dl-ssl.google.com/android/repository/docs-L_r01.zip' 
(ANSI_X3.4-1968) -> 
'https://dl-ssl.google.com/android/repository/docs-L_r01.zip' (UTF-8)
  --2014-11-15 17:38:33--  
https://dl-ssl.google.com/android/repository/docs-L_r01.zip
  Resolving dl-ssl.google.com (dl-ssl.google.com)... 2a00:1450:4013:c00::be, 
173.194.65.136, 173.194.65.93, ...
  Connecting to dl-ssl.google.com 
(dl-ssl.google.com)|2a00:1450:4013:c00::be|:443... connected.
  ERROR: The certificate of 'dl-ssl.google.com' is not trusted.
  ERROR: The certificate of 'dl-ssl.google.com' hasn't got a known issuer.
  Makefile:56: recipe for target 
'/var/cache/google-android-sdk-docs-installer/docs-L_r01.zip' failed
  make: *** [/var/cache/google-android-sdk-docs-installer/docs-L_r01.zip] Error 
5
  make: Leaving directory '/var/cache/google-android-sdk-docs-installer'
  dpkg: error processing package google-android-sdk-docs-installer 
(--configure):
   subprocess installed post-installation script returned error exit status 2
  Errors were encountered while processing:
   google-android-sdk-docs-installer

And if I add ca-certificates to the chroot, it will fail due to missing unzip.


Furthermore it leaves an unuowned directory after purge:

4m39.8s INFO: Warning: Package purging left files on system:
  /usr/share/doc/google-android-sdk-docs/not owned

If the package would ship this as an empty directory, dpkg would take
care of the creation and removal (if it's empty).


cheers,

Andreas


google-android-sdk-docs-installer_20.0.0.2.log.gz
Description: application/gzip
--- End Message ---
--- Begin Message ---
Source: google-android-sdk-docs-installer
Source-Version: 20.0.0.3

We believe that the bug you reported is fixed in the latest version of
google-android-sdk-docs-installer, which is due to be installed in the Debian 
FTP archive.

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 769...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Hans-Christoph Steiner  (supplier of updated 
google-android-sdk-docs-installer 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...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Mon, 17 Nov 2014 15:43:51 +0100
Source: google-android-sdk-docs-installer
Binary: google-android-sdk-docs-installer
Architecture: source all
Version: 20.0.0.3
Distribution: unstable
Urgency: low
Maintainer: Android tools Maintainer 

Changed-By: Hans-Christoph Steiner 
Description:
 google-android-sdk-docs-installer - Android SDK Documentation from Google
Closes: 769809
Changes:
 google-android-sdk-docs-installer (20.0.0.3) unstable; urgency=low
 .
   * add missing Depends (Closes: #769809)
   * let dpkg handle base dirs (Closes: #769809)
Checksums-Sha1:
 1a66c32478271d33d3383eae2ae244561db32ca8 1972 
google-android-sdk-docs-installer_20.0.0.3.dsc
 158bb39c

Bug#768723: Is this FTBfS cause by pry?

[Yukiharu YABUKI]

Hello, there

I checked build log. This build log tells us pry should put
"*[spc][spc]" but, pry replied "*[spc]".

Lucas, Can you check pry build in sbuild? if pry gives "*[spc]"
is pry's bug, but pry gives "*[spc][spc]" is not pry's bug.
If pry echos two spaces, test framework or low level
(Maybe in buffering?) has a bug.

That is why, It is difficult to reproduce this bug.

I rebuild pry and test "def x" by hand. I checked
pry echos two spaces.

Lucas, please try your binary. and try to test "def x" by hand.

Best
Yukiharu.

--
++++++++++++++
Yukiharu Yabuki (矢吹幸治)  I use Debian GNU/Linux
mail: yab...@netfort.gr.jp
++++++++++++++


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

Bug#768095: openvswitch-datapath-dkms fails to build on Debian 7.7 3.2.0-4-amd64 (3.2.63-2+deb7u1)

[Jonathan Dupart]

Hi,

I have been bittend by this bug.

I am raising this bug severity to grave, as it renders openvswitch
unusable after upgrading to the last stable kernel.

I tested the patch and it works flawlessly. It should be quite easy to
update the package in stable.

Regards,

-- 
Jonathan Dupart


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

Bug#765327: (Fwd) [rt.cpan.org #100385] Support for IPv6 link-local addresses with scope_id

[Ondřej Surý]

Thanks and uploaded.

I will fill unblock request tomorrow.

O.

On Sun, Nov 16, 2014, at 19:17, gregor herrmann wrote:
> Upstream comment on the bug + patch below.
> 
> I guess we should include the existing patch for the time being.
> 
> 
> Cheers,
> gregor
> 
> - Forwarded message from NLnet Labs via RT 
> -
> 
> From: NLnet Labs via RT 
> To: gre...@cpan.org
> Subject: [rt.cpan.org #100385] Support for IPv6 link-local addresses with
> scope_id
> Date: Sun, 16 Nov 2014 10:53:50 -0500
> Reply-To: bug-net-...@rt.cpan.org
> 
> https://rt.cpan.org/Ticket/Display.html?id=100385 >
> 
> On Sun 16 Nov 2014 10:40:36, GREGOA wrote:
> > We have the following bug reported to the Debian package of Net-DNS
> > (https://bugs.debian.org/765327):
> > 
> > It doesn't seem to be a bug in the packaging, so you may want to 
> > take a look. Thanks!
> 
> Thanks.  Yes link-local addresses with scope_id are not yet supported,
> but it shouldn't be too hard to make them work.
> 
> > Please note that the Debian bug report contains a proposed patch.
> 
> Your patch simply filters out the addresses with scope_id.  I think we
> could do better than that and actually start stupporting scoped
> link-local addresses.  The patch is good enough to keep things running
> for the time being though...
> 
> Thanks again
> 
> 
> - End forwarded message -
> 
> -- 
>  .''`.  Homepage: http://info.comodo.priv.at/ - OpenPGP key
>  0xBB3A68018649AA06
>  : :' : Debian GNU/Linux user, admin, and developer  - 
>  http://www.debian.org/
>  `. `'  Member of VIBE!AT & SPI, fellow of the Free Software Foundation
>  Europe
>`-   NP: Astrud Gilberto: Mamae Eu Quero
> Email had 1 attachment:
> + signature.asc
>   1k (application/pgp-signature)


-- 
Ondřej Surý 
Knot DNS (https://www.knot-dns.cz/) – a high-performance DNS server


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

Bug#754584: marked as done ([libnet-dns-perl] Makes $IPV6_LINK_LOCAL%$DEVICE queries to lo)

[Debian Bug Tracking System]

Your message dated Mon, 17 Nov 2014 16:34:26 +
with message-id 
and subject line Bug#765327: fixed in libnet-dns-perl 0.81-2
has caused the Debian Bug report #765327,
regarding [libnet-dns-perl] Makes $IPV6_LINK_LOCAL%$DEVICE queries to lo
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.)


-- 
765327: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=765327
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: libnet-dns-perl
Version: 0.78-1
Severity: normal
Affects: lintian

I was using lintian to check some packages and noticed that it is now slow as 
hell. A quick check showed that some perl stuff is sending bogus DNS requests 
over my lo device. This seems to be this perl script in _select_dns_method.

I am using network-manager in an IPv6 network and my /etc/resolv.conf contains 
entries like:


search real.example.org
nameserver 192.168.1.1
nameserver fe80::211:22ff:fe33:4455%wlan0
nameserver 2a01:1234:4568:abcd:ef01:2345:6781:abcd


And now I see a DNS query for fe80211:22ff:fe33:4455%wlan0 through my lo 
device when I am trying to start lintian on a package. This is a bogus query 
for a valid IPv6 link-lokal address nameserver entry and takes ages before it 
stops the query attempt and actually starts the rest of the lintian tests

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

Debian Release: jessie/sid
  500 unstablehttp.debian.net 

--- Package information. ---
Depends (Version) | Installed
=-+-==
perl(>= 5.18.2-5) | 5.18.2-6
perlapi-5.18.2| 
libc6(>= 2.4) | 
libdigest-hmac-perl (>= 1.01) | 
libio-socket-inet6-perl   | 
libmime-base64-perl   | 
libnet-ip-perl   (>= 1.2) | 


Package's Recommends field is empty.

Package's Suggests field is empty.
--- End Message ---
--- Begin Message ---
Source: libnet-dns-perl
Source-Version: 0.81-2

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

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 765...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Ondřej Surý  (supplier of updated libnet-dns-perl package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Mon, 17 Nov 2014 16:18:22 +0100
Source: libnet-dns-perl
Binary: libnet-dns-perl
Architecture: source amd64
Version: 0.81-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Perl Group 
Changed-By: Ondřej Surý 
Description:
 libnet-dns-perl - Perform DNS queries from a Perl script
Closes: 765327
Changes:
 libnet-dns-perl (0.81-2) unstable; urgency=medium
 .
   * Ignore link-local IPv6 resolvers (Closes: #765327)
Checksums-Sha1:
 f8f5b6c8b31a24272d443220bb453cdce45c56b0 2240 libnet-dns-perl_0.81-2.dsc
 5066e3a98866a64b2c378c37bed0c412d8669516 7464 
libnet-dns-perl_0.81-2.debian.tar.xz
 4242b5fd705d4b78c66c15cbd301b330e55054d4 331124 
libnet-dns-perl_0.81-2_amd64.deb
Checksums-Sha256:
 d22808d5aa074f138caa9bea8c4df4fce1ed74db6336f7fd203fe7469ef550e4 2240 
libnet-dns-perl_0.81-2.dsc
 a797c5d6c2446142c820c2d47140390c9e8feb289d16ba7284673422b907ed58 7464 
libnet-dns-perl_0.81-2.debian.tar.xz
 e4f48202bbd68822849495c0e6184de267e348e7f57f244114922f34d4732bfa 331124 
libnet-dns-perl_0.81-2_amd64.deb
Files:
 4720e2d94a5f1e7f2a37190c3786 2240 perl optional libnet-dns-perl_0.81-2.dsc
 97e71a35db8105039dc50fbb566df5f7 7464 perl optional 
libnet-dns-perl_0.81-2.debian.tar.xz
 98d9cb41acff34c2081aa32df6d8b5bc 331124 perl optional 
libnet-dns-perl_0.81-2_amd64.deb

-BEGIN PGP SIGNATURE-
Version: GnuPG v1

iQJ8BAEBCgBmBQJUahy1XxSAAC4AKGlzc3Vlci1mcHJAbm90YXRpb25zLm9w
ZW5wZ3AuZmlmdGhob3JzZW1hbi5uZXQzMEI5MzNEODBGQ0UzRDk4MUEyRDM4RkIw
Qzk5QjcwRUY0RkNCQjA3AAoJEAyZtw70/LsHrXcP/ilAeD1cwtT51uCJMLEjoYV+
gYjt4+9cVPKflsGbyccTEf3sbc0taEYK109JMkAkOocmCXOTSikpQwg9SfUHeIoh
npPHJrzxSzB3viy6I8VMAWFjh7BUVvf+2/NZ08OvVSWOivolXbMnl5hykpTe01GN
7FIe6WtLdnXSWY1Xz3q24i9S82WlirU97u7rye+0+XcA7NcgrEg7prJEUj0lEi/d
AaVsRM61JCJTJ56

Bug#765327: marked as done (lintian fails if the machine has a link-local IPv6 nameserver configured)

[Debian Bug Tracking System]

Your message dated Mon, 17 Nov 2014 16:34:26 +
with message-id 
and subject line Bug#765327: fixed in libnet-dns-perl 0.81-2
has caused the Debian Bug report #765327,
regarding lintian fails if the machine has a link-local IPv6 nameserver 
configured
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.)


-- 
765327: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=765327
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: libnet-dns-perl,lintian
Severity: normal

This is likely a bug in libnet-dns-perl but I wonder if there are network
accesses from lintian.

% lintian ./openclonk_5.5.1-1_amd64.changes
warning: Cannot load check "binaries"
unresolvable name: fe80::4ee6:76ff:fe51:ae30%eth0 at 
/usr/share/perl5/Email/Valid.pm line 41.
Compilation failed in require at /usr/share/perl5/Lintian/Check.pm line 27.
BEGIN failed--compilation aborted at /usr/share/perl5/Lintian/Check.pm line 27.
Compilation failed in require at /usr/share/lintian/checks/binaries.pm line 30.
BEGIN failed--compilation aborted at /usr/share/lintian/checks/binaries.pm line 
30.
Compilation failed in require at /usr/share/perl5/Lintian/CheckScript.pm line 
253.

This is due to:

% cat /etc/resolv.conf
[...]
nameserver 10.0.3.1
nameserver fe80::4ee6:76ff:fe51:ae30%eth0
[...]

The syntax is perfectly valid and understood by glibc, but apparently
libemail-valid-perl tries to resolve(!?) it and fails. No, it just
loads Net::DNS::Resolver:

$Resolver = Net::DNS::Resolver->new;

So it seems what explodes is Resolver/Base.pm's nameservers sub.

The message lintian displays is rather awkward: for a runtime error (runtime
configuration not parsable) one gets compilation failed. But I guess the load
is already guarded, hence the warning?

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

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

Versions of packages lintian depends on:
ii  binutils   2.24.51.20140918-1
ii  bzip2  1.0.6-7
ii  diffstat   1.58-1
ii  file   1:5.19-2
ii  gettext0.19.2-2
ii  hardening-includes 2.5+nmu1
ii  intltool-debian0.35.0+20060710.1
ii  libapt-pkg-perl0.1.29+b2
ii  libarchive-zip-perl1.38-1
ii  libclass-accessor-perl 0.34-1
ii  libclone-perl  0.37-1+b1
ii  libdpkg-perl   1.17.13
ii  libemail-valid-perl1.195-1
ii  libfile-basedir-perl   0.03-1
ii  libipc-run-perl0.92-1
ii  liblist-moreutils-perl 0.33-2+b1
ii  libparse-debianchangelog-perl  1.2.0-1.1
ii  libtext-levenshtein-perl   0.09-1
ii  libtimedate-perl   2.3000-2
ii  liburi-perl1.64-1
ii  man-db 2.6.7.1-1
ii  patchutils 0.3.3-1
ii  perl [libdigest-sha-perl]  5.20.1-1
ii  t1utils1.37-2.1

Versions of packages lintian recommends:
ii  libperlio-gzip-perl 0.18-3+b1
ii  perl5.20.1-1
ii  perl-modules [libautodie-perl]  5.20.1-1

Versions of packages lintian suggests:
pn  binutils-multiarch 
ii  dpkg-dev   1.17.13
ii  libhtml-parser-perl3.71-1+b2
ii  libtext-template-perl  1.46-1
ii  libyaml-perl   1.12-1
ii  xz-utils   5.1.1alpha+20120614-2

-- no debconf information
--- End Message ---
--- Begin Message ---
Source: libnet-dns-perl
Source-Version: 0.81-2

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

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 765...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Ondřej Surý  (supplier of updated libnet-dns-perl package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Mon, 17 Nov 2014 16:18:22 +0100
Source: libnet-dns-perl
Binary

Bug#756492: system-config-printer-kde: Authentication Dialog cannot receive focus

[Jim Scadden]

forwarded 756492 https://bugs.kde.org/show_bug.cgi?id=328014
tags 756492 + upstream
thanks

--

Jim Scadden


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

Processed: Re: Bug#756492: system-config-printer-kde: Authentication Dialog cannot receive focus

[Debian Bug Tracking System]

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

> forwarded 756492 https://bugs.kde.org/show_bug.cgi?id=328014
Bug #756492 [system-config-printer-kde] system-config-printer-kde: 
Authentication Dialog cannot receive focus
Set Bug forwarded-to-address to 'https://bugs.kde.org/show_bug.cgi?id=328014'.
> tags 756492 + upstream
Bug #756492 [system-config-printer-kde] system-config-printer-kde: 
Authentication Dialog cannot receive focus
Added tag(s) upstream.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
756492: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=756492
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#769685: awscli: FTBFS: ImportError: Failed to import test module: awscli.testutils

[Tom Marble]

Supposedly #769496 fixed this bug, but I continued to
have troubles with 'aws' (from package 'awscli').
I suspect the 'monkey patch' fix is very sensitive to import order (?)

I partial fix was to make this change in
/usr/lib/python3/dist-packages/botocore/awsrequest.py

#from requests.packages.urllib3.connection import HTTPConnection
#from requests.packages.urllib3.connectionpool import HTTPConnectionPool
#from requests.packages.urllib3.connectionpool import HTTPSConnectionPool
from urllib3.connection import HTTPConnection
from urllib3.connectionpool import HTTPConnectionPool
from urllib3.connectionpool import HTTPSConnectionPool

HOWEVER aws is still having some other troubles (which may
or may not be related to this bug).

Regards,

--Tom

$ aws --debug --region us-east-1c ec2 describe-instances
[...]
2014-11-17 11:45:03,723 - MainThread - botocore.endpoint - DEBUG - Exception 
received when sending HTTP request.
Traceback (most recent call last):
  File "/usr/lib/python3/dist-packages/urllib3/connectionpool.py", line 516, in 
urlopen
body=body, headers=headers)
  File "/usr/lib/python3/dist-packages/urllib3/connectionpool.py", line 304, in 
_make_request
self._validate_conn(conn)
  File "/usr/lib/python3/dist-packages/urllib3/connectionpool.py", line 724, in 
_validate_conn
conn.connect()
  File "/usr/lib/python3/dist-packages/urllib3/connection.py", line 203, in 
connect
conn = self._new_conn()
  File "/usr/lib/python3/dist-packages/urllib3/connection.py", line 133, in 
_new_conn
(self.host, self.port), self.timeout, **extra_kw)
  File "/usr/lib/python3/dist-packages/urllib3/util/connection.py", line 64, in 
create_connection
for res in socket.getaddrinfo(host, port, 0, socket.SOCK_STREAM):
  File "/usr/lib/python3.4/socket.py", line 534, in getaddrinfo
for res in _socket.getaddrinfo(host, port, family, type, proto, flags):
socket.gaierror: [Errno -2] Name or service not known


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

Bug#769551: Pre-Depends: init-system-helpers

[Guido Günther]

On Sun, Nov 16, 2014 at 07:07:43PM +0100, intrigeri wrote:
> Bastien ROUCARIES wrote (16 Nov 2014 12:27:30 GMT) :
> > On Sun, Nov 16, 2014 at 10:32 AM, Guido Günther  wrote:
> >> On Sat, Nov 15, 2014 at 06:06:17PM +0100, Bastien ROUCARIES wrote:
> >>> Thus I am asking to add a pre-depends to init-system-helpers
> >>
> >> Thanks for looking into this. I'm not sure this is enough, see
> >> #766362 where I propsed a solution without the Pre-Dependency.
> 
> > We had a short talk at Paris BSP and adding Pre-depends seems the more
> > natural ways.
> 
> Besides, the release team pre-approved the upload of a perl package
> that ships init-system-helpers' dependencies in perl-base, which
> alleviates most concerns one may have with declaring pre-depends
> on init-system-helpers :)

Awesome! That was the part I did not know. I'll upload a new version soonish.
Cheers,
 -- Guido


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

Bug#767842: ruby-actionpack-action-caching: fails to upgrade from 'wheezy' - trying to overwrite /usr/lib/ruby/vendor_ruby/action_controller/caching/actions.rb

[gregor herrmann]

On Sun, 02 Nov 2014 22:52:13 +0100, Andreas Beckmann wrote:

> >>From the attached log (scroll to the bottom...):
> 
>   Selecting previously unselected package ruby-actionmailer.
>   Preparing to unpack .../ruby-actionmailer_2%3a4.1.6-2_all.deb ...
>   Unpacking ruby-actionmailer (2:4.1.6-2) ...
>   Replacing files in old package ruby-actionmailer-2.3 (2.3.14-3) ...
>   Selecting previously unselected package ruby-actionpack-action-caching.
>   Preparing to unpack .../ruby-actionpack-action-caching_1.1.1-1_all.deb ...
>   Unpacking ruby-actionpack-action-caching (1.1.1-1) ...
>   dpkg: error processing archive 
> /var/cache/apt/archives/ruby-actionpack-action-caching_1.1.1-1_all.deb 
> (--unpack):
>trying to overwrite 
> '/usr/lib/ruby/vendor_ruby/action_controller/caching/actions.rb', which is 
> also in package ruby-actionpack-2.3 2.3.14-5
>   Selecting previously unselected package ruby-activemodel.
>   Preparing to unpack .../ruby-activemodel_2%3a4.1.6-2_all.deb ...
>   Unpacking ruby-activemodel (2:4.1.6-2) ...

Is this the same as #769555 (fixed some days ago) or something
different?

Cheers,
gregor


-- 
 .''`.  Homepage: http://info.comodo.priv.at/ - OpenPGP key 0xBB3A68018649AA06
 : :' : Debian GNU/Linux user, admin, and developer  -  http://www.debian.org/
 `. `'  Member of VIBE!AT & SPI, fellow of the Free Software Foundation Europe
   `-   NP: Elton John: Don't Let The Sun Go Down On Me


signature.asc
Description: Digital Signature

Bug#767842: ruby-actionpack-action-caching: fails to upgrade from 'wheezy' - trying to overwrite /usr/lib/ruby/vendor_ruby/action_controller/caching/actions.rb

[Andreas Beckmann]

On 2014-11-17 19:03, gregor herrmann wrote:
> On Sun, 02 Nov 2014 22:52:13 +0100, Andreas Beckmann wrote:
>>   Unpacking ruby-actionpack-action-caching (1.1.1-1) ...
>>   dpkg: error processing archive 
>> /var/cache/apt/archives/ruby-actionpack-action-caching_1.1.1-1_all.deb 
>> (--unpack):
>>trying to overwrite 
>> '/usr/lib/ruby/vendor_ruby/action_controller/caching/actions.rb', which is 
>> also in package ruby-actionpack-2.3 2.3.14-5

> Is this the same as #769555 (fixed some days ago) or something
> different?

It's probably the same issue which has *not* been fixed properly in the
recent upload.
Bumping the Depends is not sufficient to control unpack ordering - I can
still reproduce the file overwrite error with 1.1.1-2.
Versioned Breaks+Replaces need to be added for the file takeover.


Andreas


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

Processed (with 1 errors): Merge #733974 and #753560

[Debian Bug Tracking System]

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

> reassign 733974 src:libjsoncpp
Bug #733974 [minetest] Crash when browsing "Public Serverlist"
Bug #748896 [minetest] minetest: Crash when clicking "Online mod repository" in 
"Mods" tab
Bug reassigned from package 'minetest' to 'src:libjsoncpp'.
Bug reassigned from package 'minetest' to 'src:libjsoncpp'.
No longer marked as found in versions minetest/0.4.8+repack2-3, 
minetest/0.4.9+repack-4, and minetest/0.4.9+repack-5.
No longer marked as found in versions minetest/0.4.8+repack2-3, 
minetest/0.4.9+repack-4, and minetest/0.4.9+repack-5.
Ignoring request to alter fixed versions of bug #733974 to the same values 
previously set
Ignoring request to alter fixed versions of bug #748896 to the same values 
previously set
> forcemerge 733974 753560
Bug #733974 [src:libjsoncpp] Crash when browsing "Public Serverlist"
Bug #748896 [src:libjsoncpp] minetest: Crash when clicking "Online mod 
repository" in "Mods" tab
Bug #753560 [src:libjsoncpp] libjsoncpp: Numerical values cannot be converted 
to string
Changed Bug forwarded-to-address to 
'https://github.com/minetest/minetest/issues/1147' from 
'https://github.com/open-source-parsers/jsoncpp/issues/20'
733974 was blocked by: 753560
733974 was not blocking any bugs.
Removed blocking bug(s) of 733974: 753560
748896 was blocked by: 753560
748896 was not blocking any bugs.
Removed blocking bug(s) of 748896: 753560
748896 was not blocked by any bugs.
748896 was not blocking any bugs.
Removed blocking bug(s) of 748896: 753560
733974 was not blocked by any bugs.
733974 was not blocking any bugs.
Removed blocking bug(s) of 733974: 753560
Failed to forcibly merge 733974: It is nonsensical for a bug to block itself 
(or a merged partner): 753560

> severity 753560 serious
Bug #753560 [src:libjsoncpp] libjsoncpp: Numerical values cannot be converted 
to string
Severity set to 'serious' from 'normal'
> affects 753560 minetest
Bug #753560 [src:libjsoncpp] libjsoncpp: Numerical values cannot be converted 
to string
Added indication that 753560 affects minetest
> thanks
Stopping processing here.

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

[Debian Bug Tracking System]

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

> forcemerge 733974 753560
Bug #733974 [src:libjsoncpp] Crash when browsing "Public Serverlist"
Bug #748896 [src:libjsoncpp] minetest: Crash when clicking "Online mod 
repository" in "Mods" tab
Bug #753560 [src:libjsoncpp] libjsoncpp: Numerical values cannot be converted 
to string
Severity set to 'normal' from 'serious'
Removed indication that 753560 affects minetest
Bug #733974 [src:libjsoncpp] Crash when browsing "Public Serverlist"
Marked as found in versions libjsoncpp/0.6.0~rc2-3.
Marked as found in versions libjsoncpp/0.6.0~rc2-3.
Added tag(s) patch.
Added tag(s) patch.
Bug #748896 [src:libjsoncpp] minetest: Crash when clicking "Online mod 
repository" in "Mods" tab
Merged 733974 748896 753560
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
733974: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=733974
748896: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=748896
753560: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=753560
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#767842: ruby-actionpack-action-caching: fails to upgrade from 'wheezy' - trying to overwrite /usr/lib/ruby/vendor_ruby/action_controller/caching/actions.rb

[gregor herrmann]

Control: -1 + patch

On Mon, 17 Nov 2014 19:11:30 +0100, Andreas Beckmann wrote:

> On 2014-11-17 19:03, gregor herrmann wrote:
> > On Sun, 02 Nov 2014 22:52:13 +0100, Andreas Beckmann wrote:
> >>   Unpacking ruby-actionpack-action-caching (1.1.1-1) ...
> >>   dpkg: error processing archive 
> >> /var/cache/apt/archives/ruby-actionpack-action-caching_1.1.1-1_all.deb 
> >> (--unpack):
> >>trying to overwrite 
> >> '/usr/lib/ruby/vendor_ruby/action_controller/caching/actions.rb', which is 
> >> also in package ruby-actionpack-2.3 2.3.14-5
> 
> > Is this the same as #769555 (fixed some days ago) or something
> > different?
> 
> It's probably the same issue which has *not* been fixed properly in the
> recent upload.
> Bumping the Depends is not sufficient to control unpack ordering - I can
> still reproduce the file overwrite error with 1.1.1-2.
> Versioned Breaks+Replaces need to be added for the file takeover.

Thanks for checking; this confirms my gut feeling :)

So I guess there something needed as:

#v+
--- a/debian/control
+++ b/debian/control
@@ -15,6 +15,8 @@ Package: ruby-actionpack-action-caching
 Architecture: all
 XB-Ruby-Versions: ${ruby:Versions}
 Depends: ${shlibs:Depends}, ${misc:Depends}, ruby | ruby-interpreter, 
ruby-actionpack (>> 2:4)
+Breaks: ruby-actionpack-2.3, ruby-actionpack-3.2
+Replaces: ruby-actionpack-2.3, ruby-actionpack-3.2
 Description: action caching for Action Pack
  This package provides the functionality of caching the results of Rails
  controller actions, which was removed from the Rails core with the 4.0
#v-


Cheers,
gregor

-- 
 .''`.  Homepage: http://info.comodo.priv.at/ - OpenPGP key 0xBB3A68018649AA06
 : :' : Debian GNU/Linux user, admin, and developer  -  http://www.debian.org/
 `. `'  Member of VIBE!AT & SPI, fellow of the Free Software Foundation Europe
   `-   NP: Peter Ratzenbeck: Ka Liad


signature.asc
Description: Digital Signature

Processed: tagging 767842

[Debian Bug Tracking System]

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

> tags 767842 + patch
Bug #767842 [ruby-actionpack-action-caching] ruby-actionpack-action-caching: 
fails to upgrade from 'wheezy' - trying to overwrite 
/usr/lib/ruby/vendor_ruby/action_controller/caching/actions.rb
Added tag(s) patch.
> thanks
Stopping processing here.

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

[Debian Bug Tracking System]

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

> severity 753560 serious
Bug #753560 [src:libjsoncpp] libjsoncpp: Numerical values cannot be converted 
to string
Bug #733974 [src:libjsoncpp] Crash when browsing "Public Serverlist"
Bug #748896 [src:libjsoncpp] minetest: Crash when clicking "Online mod 
repository" in "Mods" tab
Severity set to 'serious' from 'normal'
Severity set to 'serious' from 'normal'
Severity set to 'serious' from 'normal'
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
733974: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=733974
748896: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=748896
753560: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=753560
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#769685: awscli: FTBFS: ImportError: Failed to import test module: awscli.testutils

[Daniele Tricoli]

Hello Tom,
many thanks for let me know of this!

On Monday 17 November 2014 11:59:38 Tom Marble wrote:
> Supposedly #769496 fixed this bug, but I continued to
> have troubles with 'aws' (from package 'awscli').
> I suspect the 'monkey patch' fix is very sensitive to import order (?)

It should not to be sensitive to import order, but I will investigate better 
also this.

> I partial fix was to make this change in
> /usr/lib/python3/dist-packages/botocore/awsrequest.py
> 
> #from requests.packages.urllib3.connection import HTTPConnection

This import is not working and I will investigate why.
It's of course related to the patch but it's a bit strange:

>>> import requests.packages.urllib3.connection
>>> dir(requests.packages.urllib3.connection)
['BaseSSLError', 'ConnectTimeoutError', 'ConnectionError', 'DummyConnection', 
'HTTPConnection', 'HTTPException', 'HTTPSConnection', 'RECENT_DATE', 
'SocketTimeout', 'SystemTimeWarning', 'UnverifiedHTTPSConnection', 
'VerifiedHTTPSConnection', '_HTTPConnection', '__builtins__', '__doc__', 
'__file__', '__name__', '__package__', 'assert_fingerprint', 'connection', 
'datetime', 'match_hostname', 'port_by_scheme', 'resolve_cert_reqs', 
'resolve_ssl_version', 'six', 'socket', 'ssl', 'ssl_wrap_socket', 'sys', 
'warnings']
>>> requests.packages.urllib3.connection.HTTPConnection


So the form "import <>" is working but not the "from ... import". 

I can't look at this right now, but I will work on it, I hope tomorrow. Feel 
free to open a serious bug against requests, since the purpose of the monkey 
patching is to transparently work.

Of course, any suggestions are appreciated! :)

> #from requests.packages.urllib3.connectionpool import HTTPConnectionPool
> #from requests.packages.urllib3.connectionpool import HTTPSConnectionPool

I tried these and they seem to work.

> from urllib3.connection import HTTPConnection
> from urllib3.connectionpool import HTTPConnectionPool
> from urllib3.connectionpool import HTTPSConnectionPool

I'm sorry for the more work you had to do, the monkey patch approach was 
supposed to avoid all of this.

> HOWEVER aws is still having some other troubles (which may
> or may not be related to this bug).
> 
> Regards,
> 
> --Tom
> 
> $ aws --debug --region us-east-1c ec2 describe-instances
> [...]
[CUT traceback]
> socket.gaierror: [Errno -2] Name or service not known

This seems to be related on DNS, can you try to simply resolve the host name?

Kind regards,

-- 
 Daniele Tricoli 'Eriol'
 http://mornie.org


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

Bug#768482: marked as done (libgit2-dev: Missing dependencies)

[Debian Bug Tracking System]

Your message dated Mon, 17 Nov 2014 18:48:48 +
with message-id 
and subject line Bug#768482: fixed in libgit2 0.21.2-2
has caused the Debian Bug report #768482,
regarding libgit2-dev: Missing dependencies
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.)


-- 
768482: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=768482
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: libgit2-dev
Version: 0.21.2-1
Severity: serious

Hi,

The libgit2-dev is missing some dependencies now that libgit2 is built
with ssh support.

The libgit2.pc file reads:

Requires.private:  openssl zlib libssh2
Libs.private:  -lhttp_parser -lrt

But the pkg is not declaring dependencies against these pkgs. Even
*.private should be available at built time.

This is causing FTBFS in libgit2-glib:

https://buildd.debian.org/status/fetch.php?pkg=libgit2-glib&arch=s390x&ver=0.0.22-1&stamp=1415317361

Cheers,

Laurent Bigonville

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

Kernel: Linux 3.16-3-amd64 (SMP w/8 CPU cores)
Locale: LANG=fr_BE.utf8, LC_CTYPE=fr_BE.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
--- End Message ---
--- Begin Message ---
Source: libgit2
Source-Version: 0.21.2-2

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

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 768...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Russell Sim  (supplier of updated libgit2 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...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Sun, 16 Nov 2014 10:33:23 +0100
Source: libgit2
Binary: libgit2-dev libgit2-21 libgit2-dbg
Architecture: source amd64
Version: 0.21.2-2
Distribution: unstable
Urgency: medium
Maintainer: Russell Sim 
Changed-By: Russell Sim 
Description:
 libgit2-21 - low-level Git library
 libgit2-dbg - libgit2 library and debugging symbols
 libgit2-dev - low-level Git library (development files)
Closes: 768482
Changes:
 libgit2 (0.21.2-2) unstable; urgency=medium
 .
   * debian/control: Added missing dependencies. (Closes: #768482)
Checksums-Sha1:
 3a74ef4cbf3f85e8a94547ea9ab4271bc7fea929 2070 libgit2_0.21.2-2.dsc
 1f1a205f0fe6233be9afdee5e3acfae16f8b055a 12076 libgit2_0.21.2-2.debian.tar.xz
 5a06bab56b4cc44697255829433d4ef1b9822427 535416 libgit2-dev_0.21.2-2_amd64.deb
 33b8c68314aee73a8bae290a7bba982f6feb1467 311562 libgit2-21_0.21.2-2_amd64.deb
 06a39acd3cd3726d676ee0dc9fcd24f411bc6b88 1203674 libgit2-dbg_0.21.2-2_amd64.deb
Checksums-Sha256:
 39c4dbf538777a6b3fa37ed768b0f45a8683f1a93a89c04a52eb04ab2af0a6b6 2070 
libgit2_0.21.2-2.dsc
 1c6e9d56ab501bcc660148c713cd5e90b5a19f0ddfeb160edc0a309ef03a8a81 12076 
libgit2_0.21.2-2.debian.tar.xz
 2cfbb7437b32f26d94f844f790636357ad46c9fa19d5b96eb93b1e9d9bd5d71b 535416 
libgit2-dev_0.21.2-2_amd64.deb
 6c977cb55fa9da536d6402a356ddab5ababfe969e5f7a83867a1e8f4c01f47c1 311562 
libgit2-21_0.21.2-2_amd64.deb
 6a050804f9dc340fb5387d2a5883626eff4edfa5fd1173fadece4592fda5fa59 1203674 
libgit2-dbg_0.21.2-2_amd64.deb
Files:
 1850509b6ad343f5218148f745e2a0b4 2070 libs extra libgit2_0.21.2-2.dsc
 46deb7c2f8bceb757cf782311a974b2e 12076 libs extra 
libgit2_0.21.2-2.debian.tar.xz
 2717b7b28250d3f9f726405e9b2942a8 535416 libdevel extra 
libgit2-dev_0.21.2-2_amd64.deb
 217bdfd451565d64d005bee07cd4582a 311562 libs extra 
libgit2-21_0.21.2-2_amd64.deb
 f5dc497ca31c8f59093aefb01eaafdfa 1203674 debug extra 
libgit2-dbg_0.21.2-2_amd64.deb

-BEGIN PGP SIGNATURE-
Version: GnuPG v1

iQIcBAEBCgAGBQJUakEoAAoJEE5xYO1KyO4dMp4P/2bPdi0UgiTROKgWJsbA/HQi
VVtquVufQuwTNVqRdENWQccw/AK/zCORMW/vK+ZGk3yszq9uViDwlT6a2daJqVep
qIg152i9dvZtijnDn52dngMHq+CuZofB03lHgjTz7c95G5CyM65E7fE8yNBFtNro
CFA9fGTNrAPx1hWGhNMNGXjATUw5IpW4fUGNu7cSUSPcfon20Un49aeOEbQ+xD9C
aOOabZ6z5oDyhltQtGxKocMdtQChkNkqlmy8rxz+dE1oSRbhDwdry9C+U5HkHMzc
n+qjdpXt7d5yIcvZ1SJ77tY0+oFKgoE+yVLRfvJb4oDdPyquyZFKFddBcbgkqU9x
K2YXF7g7t2UTrRcdOwhS5ZslUFXs6aUB2X7F1BBNbC8v/idrwtjZEMkmbvTDRp4r
j/x/d303o4wXbbs63DCBygL90dk6y7p9rjvoMFM3/rxstN8gm0gNTlRflmkB0Sg6
C8GOf8iKgQ5ZJYW1IESJTMKcuPmpI

Bug#767676: ola-rdm-tests: fails to install: subprocess installed post-installation script returned error exit status 10

[Helmut Grohne]

Hi Jean Baptiste,

On Sun, Nov 16, 2014 at 06:12:56PM +0100, Jean Baptiste Favre wrote:
> I had a look on it during Debian BSP in Paris.

Thanks for fixing RC bugs!

> Problem is located into ola-rdm-test.postinst script:
> - It uses debconf, for variable ola-rdm-tests/daemon, without providing
> any template file
> - It uses db_get and never db_input, thus ola-rdm-tests/daemon is never set
> - debconf is not mentioned as dependency
> 
> Please find attached a patch which removes debconf usage from postinst
> script.

I looked into this patch in more detail now and am willing to sponsor
your NMU (which has been approved by Wouter by now). Unfortunately, this
is not the only serious issue in ola-rdm-tests. In order to avoid
multiple round-trips through the release team I advise /not/ to upload
this fix as is (or at least only request an unblock after fixing the
remaining issues).

Your patch enables ola-rdm-tests to be installed. This is great and it
enables us to remove it again. Unfortunately, after removing and purging
/etc/defaults/ola-rdm-tests remains. The package fails to clean up after
itself.

Please try to improve on your patch to cover this case as well. Please
try to use the tool piuparts to verify that this issue and potentially
more problems are indeed fixed by your improved patch. When you submit a
new patch, please Cc me and attach a .debdiff like you did here. If
anything of the above is unclear, please ask.

Helmut


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

Bug#767842: ruby-actionpack-action-caching: fails to upgrade from 'wheezy' - trying to overwrite /usr/lib/ruby/vendor_ruby/action_controller/caching/actions.rb

[Antonio Terceiro]

On Mon, Nov 17, 2014 at 07:32:41PM +0100, gregor herrmann wrote:
> Control: -1 + patch
> 
> On Mon, 17 Nov 2014 19:11:30 +0100, Andreas Beckmann wrote:
> 
> > On 2014-11-17 19:03, gregor herrmann wrote:
> > > On Sun, 02 Nov 2014 22:52:13 +0100, Andreas Beckmann wrote:
> > >>   Unpacking ruby-actionpack-action-caching (1.1.1-1) ...
> > >>   dpkg: error processing archive 
> > >> /var/cache/apt/archives/ruby-actionpack-action-caching_1.1.1-1_all.deb 
> > >> (--unpack):
> > >>trying to overwrite 
> > >> '/usr/lib/ruby/vendor_ruby/action_controller/caching/actions.rb', which 
> > >> is also in package ruby-actionpack-2.3 2.3.14-5
> > 
> > > Is this the same as #769555 (fixed some days ago) or something
> > > different?
> > 
> > It's probably the same issue which has *not* been fixed properly in the
> > recent upload.
> > Bumping the Depends is not sufficient to control unpack ordering - I can
> > still reproduce the file overwrite error with 1.1.1-2.
> > Versioned Breaks+Replaces need to be added for the file takeover.
> 
> Thanks for checking; this confirms my gut feeling :)
> 
> So I guess there something needed as:
> 
> #v+
> --- a/debian/control
> +++ b/debian/control
> @@ -15,6 +15,8 @@ Package: ruby-actionpack-action-caching
>  Architecture: all
>  XB-Ruby-Versions: ${ruby:Versions}
>  Depends: ${shlibs:Depends}, ${misc:Depends}, ruby | ruby-interpreter, 
> ruby-actionpack (>> 2:4)
> +Breaks: ruby-actionpack-2.3, ruby-actionpack-3.2
> +Replaces: ruby-actionpack-2.3, ruby-actionpack-3.2
>  Description: action caching for Action Pack
>   This package provides the functionality of caching the results of Rails
>   controller actions, which was removed from the Rails core with the 4.0
> #v-

Right. I will upload this soon, thanks!

-- 
Antonio Terceiro 


signature.asc
Description: Digital signature

Bug#769941: libgstreamer-plugins-base1.0-0: Iceweasel crashes with "gst_app_src_set_size: assertion 'GST_IS_APP_SRC (appsrc)' failed"

[George B.]

Package: libgstreamer-plugins-base1.0-0
Version: 1.4.4-2
Severity: critical
Justification: breaks unrelated software

Hello,

Iceweasel has started crashing when I try and login into Google Mail.
Looking at the backtrace it appears to be caused by libgstreamer, so
filing a bug against this package (AFAIK this particular package is
where those functions came from).

Apologies if this was supposed to filed against a different package -
feel free to re-assign in that case.


** (iceweasel:5279): CRITICAL **: gst_app_src_set_size: assertion 
'GST_IS_APP_SRC (appsrc)' failed
[New Thread 0x7fffb7ea5700 (LWP 5356)]
[New Thread 0x7fffb726c700 (LWP 5357)]
[New Thread 0x7fffafcff700 (LWP 5358)]

Program received signal SIGSEGV, Segmentation fault.
[Switching to Thread 0x7fffb726c700 (LWP 5357)]
gst_ffmpegauddec_frame (ffmpegdec=0x0, data=0x7fffb8ddb090 "\377\373\220d", 
size=0, have_data=0x1a1, ret=0x1a1) at gstavauddec.c:644
644 gstavauddec.c: No such file or directory.
(gdb) bt
#0  gst_ffmpegauddec_frame (ffmpegdec=0x0, data=0x7fffb8ddb090
"\377\373\220d", size=0, have_data=0x1a1, ret=0x1a1) at gstavauddec.c:644
#1  0x7fffb684c3b0 in gst_ffmpegauddec_handle_frame 
(decoder=0x7fffb0ce32a0, inbuf=0x7fffc2661d20) at gstavauddec.c:751
#2  0x7fffb854d047 in gst_audio_decoder_push_buffers (dec=0x7fffb0ce32a0, 
force=-1033495264) at gstaudiodecoder.c:1416
#3  0x7fffb854d42b in gst_audio_decoder_chain_forward (dec=0x7fffb0ce32a0, 
buffer=0x7fffc2661c10) at gstaudiodecoder.c:1519
#4  0x7fffb854e4f8 in gst_audio_decoder_chain (pad=0x7fffb9cfe4c0 
<_gst_debug_min>, parent=0x7fffb0ce32a0, buffer=0x7fffc2661c10) at 
gstaudiodecoder.c:1798
#5  0x7fffb9a55d6f in gst_pad_chain_data_unchecked (data=, 
type=, pad=) at gstpad.c:3836
#6  gst_pad_push_data (pad=0x7fffbc5f5da0, type=3092570464, 
data=0x7fffc2661c10) at gstpad.c:4069
#7  0x7fffb959a524 in gst_base_parse_push_frame (parse=0x7fffc4a05230, 
frame=0x7fffc4cd8990) at gstbaseparse.c:2302
#8  0x7fffb959db7f in gst_base_parse_handle_and_push_frame 
(frame=, parse=) at gstbaseparse.c:2134
#9  gst_base_parse_finish_frame (parse=0x7fffc4a05230, frame=0x7fffc4cd8990, 
size=0) at gstbaseparse.c:2459
#10 0x7fffb727f0eb in ?? () from 
/usr/lib/x86_64-linux-gnu/gstreamer-1.0/libgstaudioparsers.so
#11 0x7fffb9596ac5 in gst_base_parse_handle_buffer (parse=0x7fffc4a05230, 
buffer=0x7fffc2661390, skip=0x7fffb726bdbc, flushed=0x7fffb726bdb8) at 
gstbaseparse.c:1961
#12 0x7fffb9597087 in gst_base_parse_scan_frame (parse=0x7fffc4a05230, 
klass=) at gstbaseparse.c:3121
#13 0x7fffb959bf22 in gst_base_parse_loop (pad=0x7fffb0b58000) at 
gstbaseparse.c:3194
#14 0x7fffb9a83ad6 in gst_task_func (task=0x7fffbc4605f0) at gsttask.c:317
#15 0x7fffef0212c8 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#16 0x7fffef020935 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#17 0x77bc70a4 in start_thread (arg=0x7fffb726c700) at 
pthread_create.c:309
#18 0x770ebccd in clone () at 
../sysdeps/unix/sysv/linux/x86_64/clone.S:111



Best regards,

George

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

Kernel: Linux 3.16.0-4-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 libgstreamer-plugins-base1.0-0 depends on:
ii  iso-codes  3.57-1
ii  libc6  2.19-13
ii  libglib2.0-0   2.42.1-1
ii  libgstreamer1.0-0  1.4.4-2
ii  liborc-0.4-0   1:0.4.22-1
ii  multiarch-support  2.19-13
ii  zlib1g 1:1.2.8.dfsg-2

Versions of packages libgstreamer-plugins-base1.0-0 recommends:
ii  gstreamer1.0-plugins-base  1.4.4-2

Versions of packages libgstreamer-plugins-base1.0-0 suggests:
pn  gstreamer-codec-install | gnome-codec-install  
ii  libvisual-0.4-plugins  0.4.0.dfsg.1-7

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

Processed: found 742873 in 0.31.1-15

[Debian Bug Tracking System]

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

> found 742873 0.31.1-15
Bug #742873 [autotrace] autotrace: CVE-2013-1953
Marked as found in versions autotrace/0.31.1-15.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
742873: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=742873
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#768798: libgdbm3:i386: changelog.Debian.gz different from libgdbm3:amd64

[gregor herrmann]

On Sun, 09 Nov 2014 11:26:23 +, Julien Cristau wrote:

> > The reason is the binNMU changelog entry from the buildd.
> > I thought this issue was fixed!???
> > 
> It's only fixed if you use dh_installchangelogs.

This seems to be a duplicate of #752465 / fixed in 1.8.3-13.1 which
closes #752465.


Cheers,
gregor

-- 
 .''`.  Homepage: http://info.comodo.priv.at/ - OpenPGP key 0xBB3A68018649AA06
 : :' : Debian GNU/Linux user, admin, and developer  -  http://www.debian.org/
 `. `'  Member of VIBE!AT & SPI, fellow of the Free Software Foundation Europe


signature.asc
Description: Digital Signature

Bug#769944: The server can't load /usr/lib/powerdns/libbindbackend.so, it's actually located at /usr/lib/x86_64-linux-gnu/pdns/libbindbackend.so

[Peter van Dijk]

On 17 Nov 2014, at 20:32 , Debian bug at v.nix.is  wrote:

> Package: pdns-server
> Version: 3.4.1-3
> Severity: grave
> 
> When I upgraded from 3.3.* I started getting this in error log:
> 
>Nov 17 19:28:30 u pdns[14671]: Loading 
> '/usr/lib/powerdns/libbindbackend.so'
>Nov 17 19:28:30 u pdns[14671]: Unable to load module 
> '/usr/lib/powerdns/libbindbackend.so': /usr/lib/powerdns/libbindbackend.so: 
> cannot open shared object file: No such file or directory
>Nov 17 19:28:30 u pdns[14671]: dnsbackend unable to load module in bind
>Nov 17 19:28:31 u pdns[14500]: Our pdns instance exited with code 1
>Nov 17 19:28:31 u pdns[14500]: Respawning

Your pdns.conf file (or a file included from it) may have a module-dir line. 
Try removing it, or if that fails, set it correctly so you do not need the 
symlink.

Kind regards,
-- 
Peter van Dijk
Netherlabs Computer Consulting BV - http://www.netherlabs.nl/


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

Bug#736042: please build-depend on libtiff-dev, not libtiff4-dev

[Bernd Zeimetz]

hi,

> The libtiff4-dev package is a transitional package that is going to
> disappear soon.  Please update your build dependency from libtiff4-dev
> to libtiff-dev.

I'll do so after jessie was released. radiance won't ship with jessie due to
major changes in the upstream buildsystem, so providing backports is the better
way then. Please ignore this bug :)

Cheers,

Bernd


-- 
 Bernd ZeimetzDebian GNU/Linux Developer
 http://bzed.dehttp://www.debian.org
 GPG Fingerprint: ECA1 E3F2 8E11 2432 D485  DD95 EB36 171A 6FF9 435F


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

Bug#765071: Change in severity

[Michele Cane]

Hi,

I decided to change the severity to grave since I am not able to use
the program.
When I reach the webpage from any device the icons are not displayed
and therefore I cannot add folders.

Here the errors from the chromium console:

Uncaught SyntaxError: Unexpected token { prototype.js:2636
Uncaught SyntaxError: Unexpected identifier nanotree.js:51
Uncaught SyntaxError: Unexpected token } tree.js:31
Uncaught TypeError: Cannot read property 'src' of null
chrome-extension://mmoheajlpfaigefceljflpohdehkjbli/findblog.js:12
Uncaught ReferenceError: Try is not defined 192.168.2.101/:65
Error in response to storage.get: TypeError: Cannot read property
'data-pin-hover' of undefined
at Object.eval [as callback] (eval at 
(chrome-extension://gpdjojdkbbmdfjfahjcgigfpmkopogic/hoverbuttons.js:4:11),
:579:28) 192.168.2.101/:1

I am available for providing any additional info.

Cheers


Michele Cane, PhD.


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

Bug#769944: The server can't load /usr/lib/powerdns/libbindbackend.so, it's actually located at /usr/lib/x86_64-linux-gnu/pdns/libbindbackend.so

[Debian bug at v.nix.is]

Package: pdns-server
Version: 3.4.1-3
Severity: grave

When I upgraded from 3.3.* I started getting this in error log:

Nov 17 19:28:30 u pdns[14671]: Loading '/usr/lib/powerdns/libbindbackend.so'
Nov 17 19:28:30 u pdns[14671]: Unable to load module 
'/usr/lib/powerdns/libbindbackend.so': /usr/lib/powerdns/libbindbackend.so: 
cannot open shared object file: No such file or directory
Nov 17 19:28:30 u pdns[14671]: dnsbackend unable to load module in bind
Nov 17 19:28:31 u pdns[14500]: Our pdns instance exited with code 1
Nov 17 19:28:31 u pdns[14500]: Respawning

There's no such *.so file. To hack around this I've done this:

$ sudo mkdir /usr/lib/powerdns/
$ sudo ln -s $(dpkg -L pdns-server|grep libbindbackend.so) 
/usr/lib/powerdns/libbindbackend.so
$ file /usr/lib/powerdns/libbindbackend.so
/usr/lib/powerdns/libbindbackend.so: symbolic link to 
`/usr/lib/x86_64-linux-gnu/pdns/libbindbackend.so'

Which makes pdns-server work again.

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

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

Versions of packages pdns-server depends on:
ii  adduser 3.113+nmu3
ii  debconf [debconf-2.0]   1.5.53
ii  init-system-helpers 1.21
ii  libboost-program-options1.55.0  1.55.0+dfsg-3
ii  libboost-serialization1.55.01.55.0+dfsg-3
ii  libbotan-1.10-0 1.10.8-2
ii  libc6   2.19-13
ii  libcrypto++95.6.1-6
ii  libgcc1 1:4.9.1-19
ii  libgmp102:6.0.0+dfsg-6
ii  liblua5.1-0 5.1.5-7.1
ii  libpolarssl71.3.8-1
ii  libsqlite3-03.8.7.1-1
ii  libstdc++6  4.9.1-19
ii  lsb-base4.1+Debian13+nmu1
ii  ucf 3.0030

pdns-server recommends no packages.

Versions of packages pdns-server suggests:
pn  pdns-backend   
ii  pdns-recursor  3.6.2-2

-- debconf information excluded


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

Processed: your mail

[Debian Bug Tracking System]

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

> severity 765071 grave
Bug #765071 [mediatomb] mediatomb: No icons in web ui
Severity set to 'grave' from 'important'
>
End of message, stopping processing here.

Please contact me if you need assistance.
-- 
765071: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=765071
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#768710: biojava3-live: FTBFS in jessie: dh_install: libbiojava3-java-doc missing files (doc/biojava/*), aborting

[gregor herrmann]

Control: tag -1 + confirmed patch

On Sun, 09 Nov 2014 08:07:04 +0100, Lucas Nussbaum wrote:

> Source: biojava3-live
> Version: 3.1.0+dfsg-1
> Severity: serious
> Tags: jessie sid
> User: debian...@lists.debian.org
> Usertags: qa-ftbfs-20141108 qa-ftbfs
> Justification: FTBFS in jessie on amd64

 
> > javadocs:

> >   [javadoc] 
> > /«BUILDDIR»/biojava3-live-3.1.0+dfsg/biojavadoc/src/main/java/org/biojava3/ontology/utils/Annotatable.java:77:
> >  error: unmappable character for encoding ASCII
> >   [javadoc]  * @author  Kalle N???slund (docs)
> >   [javadoc]^
> >   [javadoc] 
> > /«BUILDDIR»/biojava3-live-3.1.0+dfsg/biojavadoc/src/main/java/org/biojava3/ontology/utils/Annotatable.java:77:
> >  error: unmappable character for encoding ASCII
> >   [javadoc]  * @author  Kalle N???slund (docs)
> >   [javadoc] ^
> >   [javadoc] 
> > /«BUILDDIR»/biojava3-live-3.1.0+dfsg/biojavadoc/src/main/java/org/biojava3/ontology/utils/Annotatable.java:77:
> >  error: unmappable character for encoding ASCII
> >   [javadoc]  * @author  Kalle N???slund (docs)
> >   [javadoc]  ^

The package doesn't build in my sid chroot (because of some rdep
glitch [0]) but I've tested the attached patch in a jessie chroot.

(There are other ways to tell javadoc about the file encodings but
that was my first try and it works.)



Cheers,
gregor


[0]
Errors were encountered while processing:
 icedtea-netx:amd64
E: Sub-process /usr/bin/dpkg returned an error code (1)
Failed to perform requested operation on package.  Trying to recover:
Setting up icedtea-netx:amd64 (1.5.1-1) ...
update-alternatives: warning: forcing reinstallation of alternative 
/usr/lib/jvm/java-7-openjdk-amd64/jre/bin/itweb-settings because link group 
itweb-settings is broken
update-alternatives: warning: not replacing 
/usr/share/man/man1/itweb-settings.1.gz with a link
update-alternatives: warning: forcing reinstallation of alternative 
/usr/lib/jvm/java-7-openjdk-amd64/jre/bin/itweb-settings because link group 
itweb-settings is broken
update-alternatives: warning: not replacing 
/usr/share/man/man1/itweb-settings.1.gz with a link
update-alternatives: error: alternative path 
/usr/lib/jvm/java-8-openjdk-amd64/jre/bin/javaws doesn't exist
dpkg: error processing package icedtea-netx:amd64 (--configure):
 subprocess installed post-installation script returned error exit status 2
Errors were encountered while processing:
 icedtea-netx:amd64

-- 
 .''`.  Homepage: http://info.comodo.priv.at/ - OpenPGP key 0xBB3A68018649AA06
 : :' : Debian GNU/Linux user, admin, and developer  -  http://www.debian.org/
 `. `'  Member of VIBE!AT & SPI, fellow of the Free Software Foundation Europe
   `-   NP: The Beatles: Good Morning Good Morning
Index: debian/build.xml
===
--- debian/build.xml	(revision 18487)
+++ debian/build.xml	(working copy)
@@ -61,7 +61,7 @@
 	
 
 		
-		
+		
 			http://java.sun.com/j2se/1.6.0/docs/api/"/>
 		
 	
Index: debian/changelog
===
--- debian/changelog	(revision 18487)
+++ debian/changelog	(working copy)
@@ -1,3 +1,14 @@
+biojava3-live (3.1.0+dfsg-1.1) UNRELEASED; urgency=medium
+
+  * Non-maintainer upload.
+  * Fix "FTBFS in jessie: dh_install: libbiojava3-java-doc missing files
+(doc/biojava/*), aborting":
+debian/build.xml: tell javadoc that source files are encoded as UTF-8;
+otherwise it bails out, and dh_install finds nothing to install.
+(Closes: #768710)
+
+ -- gregor herrmann   Mon, 17 Nov 2014 20:36:16 +0100
+
 biojava3-live (3.1.0+dfsg-1) unstable; urgency=medium
 
   * New upstream release 


signature.asc
Description: Digital Signature

Processed: Re: Bug#768710: biojava3-live: FTBFS in jessie: dh_install: libbiojava3-java-doc missing files (doc/biojava/*), aborting

[Debian Bug Tracking System]

Processing control commands:

> tag -1 + confirmed patch
Bug #768710 [src:biojava3-live] biojava3-live: FTBFS in jessie: dh_install: 
libbiojava3-java-doc missing files (doc/biojava/*), aborting
Added tag(s) confirmed and patch.

-- 
768710: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=768710
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#769948: udev: dpkg can't configure udev while upgrading to jessie

[Thuban]

Package: udev
Version: 215-5+b1
Severity: grave
Justification: renders package unusable

Dear Maintainer,

While upgrading from wheezy to jessie, dpkg fails to configure udev. So,
the whole upgrade fails, with the following error : 

Paramétrage de udev (215-5+b1) ...
dpkg: erreur de traitement du paquet udev (--configure) :
le sous-processus script post-installation installé a retourné une
erreur de sortie d'état 1
E: Sub-process /usr/bin/dpkg returned an error code (1)

Sorry for french output...
I simply used `apt-get upgrade` with jessie in my sources.list.

How can I give you more information to help solving this issue?

Regards,

Thuban



-- Package-specific info:

-- System Information:
Debian Release: jessie/sid
  APT prefers stable-updates
  APT policy: (500, 'stable-updates'), (500, 'testing'), (500, 'stable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

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

Versions of packages udev depends on:
ii  adduser3.113+nmu3
ii  debconf [debconf-2.0]  1.5.53
ii  libacl12.2.52-2
ii  libblkid1  2.25.2-2
ii  libc6  2.19-13
ii  libkmod2   18-3
ii  libselinux12.3-2
ii  libudev1   215-5+b1
ii  lsb-base   4.1+Debian13+nmu1
ii  procps 2:3.3.9-8
ii  util-linux 2.25.2-2

udev recommends no packages.

udev suggests no packages.

-- debconf information:
  udev/title/upgrade:
  udev/reboot_needed:
  udev/sysfs_deprecated_incompatibility:
  udev/new_kernel_needed: false
P: /devices/LNXSYSTM:00
E: DEVPATH=/devices/LNXSYSTM:00
E: MODALIAS=acpi:LNXSYSTM:
E: SUBSYSTEM=acpi

P: /devices/LNXSYSTM:00/LNXCPU:00
E: DEVPATH=/devices/LNXSYSTM:00/LNXCPU:00
E: MODALIAS=acpi:LNXCPU:
E: SUBSYSTEM=acpi

P: /devices/LNXSYSTM:00/LNXCPU:01
E: DEVPATH=/devices/LNXSYSTM:00/LNXCPU:01
E: MODALIAS=acpi:LNXCPU:
E: SUBSYSTEM=acpi

P: /devices/LNXSYSTM:00/LNXCPU:02
E: DEVPATH=/devices/LNXSYSTM:00/LNXCPU:02
E: MODALIAS=acpi:LNXCPU:
E: SUBSYSTEM=acpi

P: /devices/LNXSYSTM:00/LNXCPU:03
E: DEVPATH=/devices/LNXSYSTM:00/LNXCPU:03
E: MODALIAS=acpi:LNXCPU:
E: SUBSYSTEM=acpi

P: /devices/LNXSYSTM:00/LNXCPU:04
E: DEVPATH=/devices/LNXSYSTM:00/LNXCPU:04
E: MODALIAS=acpi:LNXCPU:
E: SUBSYSTEM=acpi

P: /devices/LNXSYSTM:00/LNXCPU:05
E: DEVPATH=/devices/LNXSYSTM:00/LNXCPU:05
E: MODALIAS=acpi:LNXCPU:
E: SUBSYSTEM=acpi

P: /devices/LNXSYSTM:00/LNXCPU:06
E: DEVPATH=/devices/LNXSYSTM:00/LNXCPU:06
E: MODALIAS=acpi:LNXCPU:
E: SUBSYSTEM=acpi

P: /devices/LNXSYSTM:00/LNXCPU:07
E: DEVPATH=/devices/LNXSYSTM:00/LNXCPU:07
E: MODALIAS=acpi:LNXCPU:
E: SUBSYSTEM=acpi

P: /devices/LNXSYSTM:00/LNXPWRBN:00
E: DEVPATH=/devices/LNXSYSTM:00/LNXPWRBN:00
E: DRIVER=button
E: MODALIAS=acpi:LNXPWRBN:
E: SUBSYSTEM=acpi

P: /devices/LNXSYSTM:00/LNXPWRBN:00/input/input8
E: DEVPATH=/devices/LNXSYSTM:00/LNXPWRBN:00/input/input8
E: EV=3
E: ID_FOR_SEAT=input-acpi-LNXPWRBN_00
E: ID_INPUT=1
E: ID_INPUT_KEY=1
E: ID_PATH=acpi-LNXPWRBN:00
E: ID_PATH_TAG=acpi-LNXPWRBN_00
E: KEY=10 0
E: MODALIAS=input:b0019vp0001e-e0,1,k74,ramlsfw
E: NAME="Power Button"
E: PHYS="LNXPWRBN/button/input0"
E: PRODUCT=19/0/1/0
E: PROP=0
E: SUBSYSTEM=input
E: TAGS=:seat:
E: USEC_INITIALIZED=44347

P: /devices/LNXSYSTM:00/LNXPWRBN:00/input/input8/event4
N: input/event4
E: BACKSPACE=guess
E: DEVNAME=/dev/input/event4
E: DEVPATH=/devices/LNXSYSTM:00/LNXPWRBN:00/input/input8/event4
E: ID_INPUT=1
E: ID_INPUT_KEY=1
E: ID_PATH=acpi-LNXPWRBN:00
E: ID_PATH_TAG=acpi-LNXPWRBN_00
E: MAJOR=13
E: MINOR=68
E: SUBSYSTEM=input
E: TAGS=:power-switch:
E: USEC_INITIALIZED=43844
E: XKBLAYOUT=fr
E: XKBMODEL=pc105
E: XKBVARIANT=latin9

P: /devices/LNXSYSTM:00/LNXSYBUS:00
E: DEVPATH=/devices/LNXSYSTM:00/LNXSYBUS:00
E: MODALIAS=acpi:LNXSYBUS:
E: SUBSYSTEM=acpi

P: /devices/LNXSYSTM:00/LNXSYBUS:00/ACPI0003:00
E: DEVPATH=/devices/LNXSYSTM:00/LNXSYBUS:00/ACPI0003:00
E: DRIVER=ac
E: MODALIAS=acpi:ACPI0003:
E: SUBSYSTEM=acpi

P: /devices/LNXSYSTM:00/LNXSYBUS:00/ACPI0003:00/power_supply/ADP0
E: DEVPATH=/devices/LNXSYSTM:00/LNXSYBUS:00/ACPI0003:00/power_supply/ADP0
E: POWER_SUPPLY_NAME=ADP0
E: POWER_SUPPLY_ONLINE=1
E: SUBSYSTEM=power_supply

P: /devices/LNXSYSTM:00/LNXSYBUS:00/INT340E:00
E: DEVPATH=/devices/LNXSYSTM:00/LNXSYBUS:00/INT340E:00
E: ID_VENDOR_FROM_DATABASE=Interphase Corporation
E: MODALIAS=acpi:INT340E:PNP0C02:
E: SUBSYSTEM=acpi
E: USEC_INITIALIZED=18504

P: /devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A08:00
E: DEVPATH=/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A08:00
E: MODALIAS=acpi:PNP0A08:PNP0A03:
E: SUBSYSTEM=acpi

P: /devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A08:00/INTC0102:00
E: DEVPATH=/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A08:00/INTC0102:00
E: ID_VENDOR_FROM_DATABASE=Interphase Corporation
E: MODALIAS=acpi:INTC0102:PNP0C31:
E: SUBSYSTEM=acpi
E: USEC_INITIALIZED=18549

P: /devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A08:00/LNXVIDEO

Bug#769670: ola-rdm-tests: FTBFS in a sid chroot with pbuilder (no network)

[Pierre Duperray]

On 11/17/14 01:18, Wouter Verhelst wrote:
> On Sat, Nov 15, 2014 at 02:46:10PM +0100, Pitamila wrote:
>> Package: ola-rdm-tests
>> Version: 0.9.1-1
>> Severity: serious
>> Justification: fails to build from source (but built successfully in the 
>> past)
>>
>> Dear Maintainer,
>>
>> see pbuilder log below:
>>
>> InterfacePickerTest.cpp:67:Assertion
>> Test name: InterfacePickerTest::testGetInterfaces
>> assertion failed
>> - Expression: interfaces.size() > 0
>>
>> Failures !!!
>> Run: 21   Failure total: 1   Failures: 1   Errors: 0
>> FAIL: NetworkTester
> Can you give some detail on what the network looked like for this build?
>
Not really, I was connected to a public wifi hotspot (somewhere :)

Does a pbuilder chroot allow a network connection of any kind?


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

Bug#767842: marked as done (ruby-actionpack-action-caching: fails to upgrade from 'wheezy' - trying to overwrite /usr/lib/ruby/vendor_ruby/action_controller/caching/actions.rb)

[Debian Bug Tracking System]

Your message dated Mon, 17 Nov 2014 21:19:15 +
with message-id 
and subject line Bug#767842: fixed in ruby-actionpack-action-caching 1.1.1-3
has caused the Debian Bug report #767842,
regarding ruby-actionpack-action-caching: fails to upgrade from 'wheezy' - 
trying to overwrite 
/usr/lib/ruby/vendor_ruby/action_controller/caching/actions.rb
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.)


-- 
767842: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=767842
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: ruby-actionpack-action-caching
Version: 1.1.1-1
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

during a test with piuparts I noticed your package fails to upgrade from
'wheezy'.
It installed fine in 'wheezy', then the upgrade to 'jessie' fails
because it tries to overwrite other packages files without declaring a
Breaks+Replaces relation.

See policy 7.6 at
http://www.debian.org/doc/debian-policy/ch-relationships.html#s-replaces

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

  Selecting previously unselected package ruby-actionmailer.
  Preparing to unpack .../ruby-actionmailer_2%3a4.1.6-2_all.deb ...
  Unpacking ruby-actionmailer (2:4.1.6-2) ...
  Replacing files in old package ruby-actionmailer-2.3 (2.3.14-3) ...
  Selecting previously unselected package ruby-actionpack-action-caching.
  Preparing to unpack .../ruby-actionpack-action-caching_1.1.1-1_all.deb ...
  Unpacking ruby-actionpack-action-caching (1.1.1-1) ...
  dpkg: error processing archive 
/var/cache/apt/archives/ruby-actionpack-action-caching_1.1.1-1_all.deb 
(--unpack):
   trying to overwrite 
'/usr/lib/ruby/vendor_ruby/action_controller/caching/actions.rb', which is also 
in package ruby-actionpack-2.3 2.3.14-5
  Selecting previously unselected package ruby-activemodel.
  Preparing to unpack .../ruby-activemodel_2%3a4.1.6-2_all.deb ...
  Unpacking ruby-activemodel (2:4.1.6-2) ...


cheers,

Andreas


redmine_3.0~20140825-1.log.gz
Description: application/gzip
--- End Message ---
--- Begin Message ---
Source: ruby-actionpack-action-caching
Source-Version: 1.1.1-3

We believe that the bug you reported is fixed in the latest version of
ruby-actionpack-action-caching, which is due to be installed in the Debian FTP 
archive.

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 767...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Antonio Terceiro  (supplier of updated 
ruby-actionpack-action-caching 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...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Mon, 17 Nov 2014 17:45:23 -0200
Source: ruby-actionpack-action-caching
Binary: ruby-actionpack-action-caching
Architecture: source all
Version: 1.1.1-3
Distribution: unstable
Urgency: medium
Maintainer: Debian Ruby Extras Maintainers 

Changed-By: Antonio Terceiro 
Description:
 ruby-actionpack-action-caching - action caching for Action Pack
Closes: 767842
Changes:
 ruby-actionpack-action-caching (1.1.1-3) unstable; urgency=medium
 .
   * Breaks/Replaces against ruby-actionpack-2.3, ruby-actionpack-3.2 to
 properly fix upgrades from wheezy (Closes: #767842).
Checksums-Sha1:
 445f394d36db114e1ed3a021e98c83cce9b22972 2295 
ruby-actionpack-action-caching_1.1.1-3.dsc
 8ff2f905520705eacdefb4631abc3708b3210b6c 2484 
ruby-actionpack-action-caching_1.1.1-3.debian.tar.xz
 7488ace076753996bb9fcfefe43e6122049235bf 8592 
ruby-actionpack-action-caching_1.1.1-3_all.deb
Checksums-Sha256:
 e4e338387dc3fb08a4faf7f408ce9055ca6fb9bb71396dd7fb578c62928def6f 2295 
ruby-actionpack-action-caching_1.1.1-3.dsc
 02e9cdc81119173da75e8c279615695e07d0c99410a32c5c3b07ade24d5c02b9 2484 
ruby-actionpack-action-caching_1.1.1-3.debian.tar.xz
 77493e07bad997043c639203f2176ebc704d467d0a1353e75d096cddd175d898 8592 
ruby-actionpack-action-caching_1.1.1-3_all.deb
Files:
 930a7d1907827ab0be6b8f372905fd22 2295 ruby optional 
ruby-actionpack-action-caching_1.1.1-3.dsc
 d5d5a479eaa220fd437479192837095f 2484 ruby optional 
ruby-actionpack-action-caching_1.1.1-3.debian.tar.xz
 794e5426b3bc175b8d584b01eaae3c28 8592 ruby optional 
ruby-actionpack-action-caching_1.1.1-3_all.deb

-BEGIN PGP SIGNATURE-
Version: GnuPG v1

iQIcBAEBCAAGBQJUalFsAAoJE

Bug#768286: marked as done (python{, 3}-zope.interface-dbg: unhandled symlink to directory conversion: /usr/share/doc/PACKAGE)

[Debian Bug Tracking System]

Your message dated Mon, 17 Nov 2014 21:19:43 +
with message-id 
and subject line Bug#768286: fixed in zope.interface 4.1.1-3
has caused the Debian Bug report #768286,
regarding python{, 3}-zope.interface-dbg: unhandled symlink to directory 
conversion: /usr/share/doc/PACKAGE
to be marked as done.

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

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


-- 
768286: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=768286
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: python3-zope.interface-dbg,python-zope.interface-dbg
Version: 4.1.1-2
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

an upgrade test with piuparts revealed that your package installs files
over existing symlinks and possibly overwrites files owned by other
packages. This usually means an old version of the package shipped a
symlink but that was later replaced by a real (and non-empty)
directory. This kind of overwriting another package's files cannot be
detected by dpkg.

This was observed on the following upgrade paths:

  wheezy -> jessie

For /usr/share/doc/PACKAGE this may not be problematic as long as both
packages are installed, ship byte-for-byte identical files and are
upgraded in lockstep. But once one of the involved packages gets
removed, the other one will lose its documentation files, too,
including the copyright file, which is a violation of Policy 12.5:
http://www.debian.org/doc/debian-policy/ch-docs.html#s-copyrightfile

For other overwritten locations anything interesting may happen.

Note that dpkg intentionally does not replace directories with symlinks
and vice versa, you need the maintainer scripts to do this.
See in particular the end of point 4 in
http://www.debian.org/doc/debian-policy/ch-maintainerscripts.html#s-unpackphase

It is recommended to use the dpkg-maintscript-helper commands
'dir_to_symlink' and 'symlink_to_dir' (available since dpkg 1.17.2)
to perform the conversion, ideally using d/$PACKAGE.mainstscript.
See dpkg-maintscript-helper(1) and dh_installdeb(1) for details.


>From the attached log (usually somewhere in the middle...):

1m47.2s ERROR: FAIL: silently overwrites files via directory symlinks:
  /usr/share/doc/python3-zope.interface-dbg/changelog.Debian.gz 
(python3-zope.interface-dbg) != 
/usr/share/doc/python3-zope.interface/changelog.Debian.gz 
(python3-zope.interface)
  /usr/share/doc/python3-zope.interface-dbg/copyright 
(python3-zope.interface-dbg) != /usr/share/doc/python3-zope.interface/copyright 
(python3-zope.interface)

1m8.8s ERROR: FAIL: silently overwrites files via directory symlinks:
  /usr/share/doc/python-zope.interface-dbg/changelog.Debian.gz 
(python-zope.interface-dbg) != 
/usr/share/doc/python-zope.interface/changelog.Debian.gz (python-zope.interface)
  /usr/share/doc/python-zope.interface-dbg/copyright 
(python-zope.interface-dbg) != /usr/share/doc/python-zope.interface/copyright 
(python-zope.interface)


cheers,

Andreas


python3-zope.interface-dbg_4.1.1-2.log.gz
Description: application/gzip
--- End Message ---
--- Begin Message ---
Source: zope.interface
Source-Version: 4.1.1-3

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

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 768...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Barry Warsaw  (supplier of updated zope.interface 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...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Mon, 17 Nov 2014 13:48:08 -0500
Source: zope.interface
Binary: python-zope.interface python-zope.interface-dbg python3-zope.interface 
python3-zope.interface-dbg
Architecture: source amd64
Version: 4.1.1-3
Distribution: unstable
Urgency: medium
Maintainer: Debian/Ubuntu Zope Team 

Changed-By: Barry Warsaw 
Description:
 python-zope.interface - Interfaces for Python
 python-zope.interface-dbg - Interfaces for Python (debug extension)
 python3-zope.interface - Interfaces for Python3
 python3-zope.interface-dbg - Interfaces for Python3 (debug extension)
Closes: 768286
Changes:
 zope.interface (4.1.1-3) unstable; urgency=medium
 .
   * Added d/python{,3}-zope.interface-dbg.maintscript so that the s

Bug#769191: xorg: apt-get dist-upgrade somehow reconfigured my system to use the nvidia driver, even though I have no nvidia hardware

[Simon McVittie]

On Wed, 12 Nov 2014 at 02:08:34 +, Nathaniel J. Smith wrote:
> This evening I ran 'apt-get dist-upgrade' on my 'testing' system, rebooted, 
> and
> found the system unusable -- it just came up with gdm3's "Oh no! Something has
> gone wrong!" screen.
> 
> It turns out that the problem is that somehow, dist-upgrade reconfigured X to
> use the nvidia drivers for GLX -- e.g., from /var/log/messages:
> [...]
> Nov 12 01:47:35 branna gdm-Xorg-:0[4239]: (EE) Failed to initialize GLX
> extension (Compatible NVIDIA X driver not found)

This sounds somewhat similar to #769072 (which is currently assigned to
gnome-shell, and I only haven't reassigned it away because I'm not sure which
nvidia-related package has the bug). The exact symptom is different,
but the high-level situation ("trying to use a mixture of Mesa and nVidia
GL stuff after an upgrade") is similar. Perhaps they should be merged?

Finding the offending upgrade in /var/log/apt would be useful;
so would the details of the apt transaction(s) in which you removed
the nvidia stuff.

Michael, I assume you have out-of-band information that says #769481 is
in fact the same as #769191? (I ask because you merged them, but it isn't
obvious why from the bug log.)

S


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

Processed: Unreproducible

[Debian Bug Tracking System]

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

> tag 769625 + unreproducible
Bug #769625 [midori] /usr/bin/midori: error while loading shared libraries: 
libgcrypt.so.11: cannot open shared object file: No such file or directory 
Added tag(s) unreproducible.
> thanks
Stopping processing here.

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

[Neil Williams]

tag 769625 + unreproducible
thanks

I use midori on unstable on a daily basis. I've re-tested the build and
there is no mention of libgcrypt in the list of symbols
of /usr/bin/midori

Dynamic Section:
  NEEDED   libgobject-2.0.so.0
  NEEDED   libglib-2.0.so.0
  NEEDED   libm.so.6
  NEEDED   libunique-1.0.so.0
  NEEDED   libgtk-x11-2.0.so.0
  NEEDED   libgdk-x11-2.0.so.0
  NEEDED   libcairo.so.2
  NEEDED   libgdk_pixbuf-2.0.so.0
  NEEDED   libgio-2.0.so.0
  NEEDED   libpango-1.0.so.0
  NEEDED   libsoup-2.4.so.1
  NEEDED   libgmodule-2.0.so.0
  NEEDED   libsqlite3.so.0
  NEEDED   libnotify.so.4
  NEEDED   libwebkitgtk-1.0.so.0
  NEEDED   libjavascriptcoregtk-1.0.so.0
  NEEDED   libxml2.so.2
  NEEDED   libX11.so.6
  NEEDED   libXss.so.1
  NEEDED   libpthread.so.0
  NEEDED   libc.so.6

Could this be related to a plugin or extension installed on the system?

I've also just installed a completely fresh i386 VM based on Jessie/Sid
running XFCE4, libgcrypt11 was installed as part of it - midori runs
with or without libgcrypt11 installed. (libgnutls26 is removed alongside
libgcrypt11 in this situation).


-- 


Neil Williams
=
http://www.linux.codehelp.co.uk/



pgp90ZsJ5_zmV.pgp
Description: OpenPGP digital signature

Processed: Re: Bug#769722: creepy: Fail to look up on Flickr (Error: 95: SSL is required)

[Debian Bug Tracking System]

Processing control commands:

> severity -1 grave
Bug #769722 [python-flickrapi] creepy: Fail to look up on Flickr (Error: 95: 
SSL is required)
Severity set to 'grave' from 'important'

-- 
769722: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=769722
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#769072: Bug#769191: xorg: apt-get dist-upgrade somehow reconfigured my system to use the nvidia driver, even though I have no nvidia hardware

[Nathaniel Smith]

Here's my apt history files. history.log.1 has the big upgrade that
caused the problem; history.log has the mucking about I did to fix it.

Notice that the big upgrade got interrupted in the middle by libaudio2
failing to install (#768651), so there was some 'apt-get install -f'
and 'dpkg --configure -a' stuff in there before the dist-upgrade gets
restarted.

On Mon, Nov 17, 2014 at 9:26 PM, Simon McVittie  wrote:
> On Wed, 12 Nov 2014 at 02:08:34 +, Nathaniel J. Smith wrote:
>> This evening I ran 'apt-get dist-upgrade' on my 'testing' system, rebooted, 
>> and
>> found the system unusable -- it just came up with gdm3's "Oh no! Something 
>> has
>> gone wrong!" screen.
>>
>> It turns out that the problem is that somehow, dist-upgrade reconfigured X to
>> use the nvidia drivers for GLX -- e.g., from /var/log/messages:
>> [...]
>> Nov 12 01:47:35 branna gdm-Xorg-:0[4239]: (EE) Failed to initialize GLX
>> extension (Compatible NVIDIA X driver not found)
>
> This sounds somewhat similar to #769072 (which is currently assigned to
> gnome-shell, and I only haven't reassigned it away because I'm not sure which
> nvidia-related package has the bug). The exact symptom is different,
> but the high-level situation ("trying to use a mixture of Mesa and nVidia
> GL stuff after an upgrade") is similar. Perhaps they should be merged?
>
> Finding the offending upgrade in /var/log/apt would be useful;
> so would the details of the apt transaction(s) in which you removed
> the nvidia stuff.
>
> Michael, I assume you have out-of-band information that says #769481 is
> in fact the same as #769191? (I ask because you merged them, but it isn't
> obvious why from the bug log.)
>
> S



-- 
Nathaniel J. Smith
Postdoctoral researcher - Informatics - University of Edinburgh
http://vorpus.org


history.log.1
Description: Binary data

Start-Date: 2014-11-12  01:51:35
Commandline: apt-get remove xserver-xorg-video-nvidia
Remove: nvidia-driver:amd64 (340.46-3), xserver-xorg-video-nvidia:amd64 (340.46-3)
End-Date: 2014-11-12  01:51:41

Start-Date: 2014-11-12  01:52:49
Commandline: apt-get autoremove
Remove: libegl1-nvidia:amd64 (340.46-3), libgles2-nvidia:amd64 (340.46-3), libjansson4:amd64 (2.7-1), nvidia-settings:amd64 (340.46-2), libgl1-nvidia-glx:amd64 (340.46-3), libgles1-nvidia:amd64 (340.46-3), libnvidia-ml1:amd64 (340.46-3), libnvidia-eglcore:amd64 (340.46-3), libxnvctrl0:amd64 (340.46-2)
End-Date: 2014-11-12  01:52:57

Start-Date: 2014-11-13  18:40:54
Commandline: apt-get install vagrant
Install: ruby-i18n:amd64 (0.6.9-2, automatic), ruby-net-scp:amd64 (1.2.1-1, automatic), ruby-listen:amd64 (2.4.0-4, automatic), ruby-rb-inotify:amd64 (0.9.5-1, automatic), bsdtar:amd64 (3.1.2-9, automatic), ruby-dev:amd64 (2.1.0.4, automatic), ruby-timers:amd64 (1.1.0-2, automatic), ruby-childprocess:amd64 (0.5.5-1, automatic), vagrant:amd64 (1.6.5+dfsg1-2), ruby-net-ssh:amd64 (2.9.1-1, automatic), ruby-nokogiri:amd64 (1.6.3.1+ds-1, automatic), ruby2.1-dev:amd64 (2.1.4-1, automatic), ruby-erubis:amd64 (2.7.0-3, automatic), bundler:amd64 (1.7.4-1, automatic), ruby-celluloid:amd64 (0.15.2-2, automatic), ruby-log4r:amd64 (1.1.10-4, automatic), ruby-thor:amd64 (0.19.1-1, automatic), ruby-ffi:amd64 (1.9.6debian-2, automatic), ruby-net-http-persistent:amd64 (2.9-2, automatic)
End-Date: 2014-11-13  18:41:05

Start-Date: 2014-11-13  18:42:31
Commandline: apt-get install virtualbox virtualbox-guest-additions-iso
Install: virtualbox:amd64 (4.3.18-dfsg-1), virtualbox-dkms:amd64 (4.3.18-dfsg-1, automatic), virtualbox-guest-additions-iso:amd64 (4.3.18-1), virtualbox-qt:amd64 (4.3.18-dfsg-1, automatic), libvncserver0:amd64 (0.9.9+dfsg-6+b2, automatic), libgsoap5:amd64 (2.8.17-1, automatic)
End-Date: 2014-11-13  18:42:56

Start-Date: 2014-11-13  18:55:48
Commandline: apt-get install linux-headers-amd64
Install: linux-headers-3.16-3-common:amd64 (3.16.5-1, automatic), linux-kbuild-3.16:amd64 (3.16-2, automatic), linux-headers-3.16-3-amd64:amd64 (3.16.5-1, automatic), linux-compiler-gcc-4.8-x86:amd64 (3.16.5-1, automatic), linux-headers-amd64:amd64 (3.16+62)
End-Date: 2014-11-13  18:56:44

Start-Date: 2014-11-13  18:57:25
Commandline: apt-get install --reinstall virtualbox-dkms
Reinstall: virtualbox-dkms:amd64 (4.3.18-dfsg-1)
End-Date: 2014-11-13  18:58:12

Bug#767937: marked as done (plymouth: fails to upgrade from 'wheezy': plymouth.postinst: deb-systemd-helper: not found)

[Debian Bug Tracking System]

Your message dated Mon, 17 Nov 2014 22:03:56 +
with message-id 
and subject line Bug#767937: fixed in plymouth 0.9.0-9
has caused the Debian Bug report #767937,
regarding plymouth: fails to upgrade from 'wheezy': plymouth.postinst: 
deb-systemd-helper: not found
to be marked as done.

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

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


-- 
767937: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=767937
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: plymouth
Version: 0.9.0-7
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

during a test with piuparts I noticed your package fails to upgrade from
'wheezy'.
It installed fine in 'wheezy', then the upgrade to 'jessie' fails.

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

  Setting up plymouth (0.9.0-7) ...
  Installing new version of config file /etc/init.d/plymouth-log ...
  Installing new version of config file /etc/init.d/plymouth ...
  Installing new version of config file /etc/plymouth/plymouthd.conf ...
  /var/lib/dpkg/info/plymouth.postinst: 13: 
/var/lib/dpkg/info/plymouth.postinst: deb-systemd-helper: not found
  dpkg: error processing package plymouth (--configure):
   subprocess installed post-installation script returned error exit status 127
  Setting up debconf-i18n (1.5.53) ...
  Processing triggers for libc-bin (2.19-12) ...
  Processing triggers for initramfs-tools (0.116) ...
  Errors were encountered while processing:
   plymouth
 

cheers,

Andreas


plymouth_0.9.0-7.log.gz
Description: application/gzip
--- End Message ---
--- Begin Message ---
Source: plymouth
Source-Version: 0.9.0-9

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

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 767...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Sjoerd Simons  (supplier of updated plymouth 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...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Format: 1.8
Date: Mon, 17 Nov 2014 22:42:50 +0100
Source: plymouth
Binary: plymouth plymouth-x11 plymouth-dbg plymouth-dev plymouth-themes
Architecture: source amd64
Version: 0.9.0-9
Distribution: unstable
Urgency: medium
Maintainer: Laurent Bigonville 
Changed-By: Sjoerd Simons 
Description:
 plymouth   - boot animation, logger and I/O multiplexer
 plymouth-dbg - boot animation, logger and I/O multiplexer - debug symbols
 plymouth-dev - boot animation, logger and I/O multiplexer - development files
 plymouth-themes - boot animation, logger and I/O multiplexer - themes
 plymouth-x11 - boot animation, logger and I/O multiplexer - X11 renderer and 
log
Closes: 763276 767170 767937 768350
Changes:
 plymouth (0.9.0-9) unstable; urgency=medium
 .
   [ Laurent Bigonville ]
   * debian/control: Add a dependency against init-system-helpers as we are
 explicitly using deb-systemd-helper in the plymouth postinst script
 (Closes: #767937)
   * debian/local/plymouth.hook: Test if the plugin is present on disk before
 trying to copy it to the initramfs (Closes: #767170)
   * debian/control: Reword the package description. (Closes: #768350)
 Thanks to Justin B Rye 
   * debian/local/plymouth.hook: Properly copy .plymouth file into the
 initramfs for themes that are not shipping images, this should fix the
 tribar theme.
 .
   [ Sjoerd Simons ]
   * 
debian/patches/debian/patches/utils-Don-t-create-unix-sockets-non-blocking.patch:
 + Added. Don't open unix socket connections as non-blocking as the read
 function assume blocking sockets. Fixes plymouth failing to query the
 password from the user  (Closes: #763276)
Checksums-Sha1:
 59fc50d5b29ad207da189019ae3eb4088922e2be 2295 plymouth_0.9.0-9.dsc
 1bc09140061a6ed077540cd32025f4da6d094da7 24960 plymouth_0.9.0-9.debian.tar.xz
 781fc36d3ba4a1f56a25e0e628f3830afdd254a2 188664 plymouth_0.9.0-9_amd64.deb
 e1bcd91606ec91db98babed1a26cdd195da6efa4 21230 plymouth-x11_0.9.0-9_amd64.deb
 3cb40247c05a913d747c670765d49e652c110a86 572208 plymouth-dbg_0.9.0-9_amd64.deb
 c247d84d8acf00509eee22b977655ada0be4fd25 392754 plymouth-dev_0.9.0-9_amd64.deb
 6f0d76d8836283a31c78b888608de5a9aeaf82e8 663512 
plymouth-themes_0.9.0-9_amd6

Bug#767677: marked as done (android-permissions: fails to install: useradd: group '1004' does not exist)

[Debian Bug Tracking System]

Your message dated Mon, 17 Nov 2014 22:03:45 +
with message-id 
and subject line Bug#767677: fixed in android-permissions 0.2
has caused the Debian Bug report #767677,
regarding android-permissions: fails to install: useradd: group '1004' does not 
exist
to be marked as done.

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

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


-- 
767677: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=767677
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: android-permissions
Version: 0.1
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

during a test with piuparts I noticed your package failed to install. As
per definition of the release team this makes the package too buggy for
a release, thus the severity.

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

  Selecting previously unselected package android-permissions.
  (Reading database ... 7393 files and directories currently installed.)
  Preparing to unpack .../android-permissions_0.1_all.deb ...
  Unpacking android-permissions (0.1) ...
  Setting up android-permissions (0.1) ...
  useradd: group '1004' does not exist
  dpkg: error processing package android-permissions (--configure):
   subprocess installed post-installation script returned error exit status 6
  Errors were encountered while processing:
   android-permissions


cheers,

Andreas


android-permissions_0.1.log.gz
Description: application/gzip
--- End Message ---
--- Begin Message ---
Source: android-permissions
Source-Version: 0.2

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

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 767...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Hans-Christoph Steiner  (supplier of updated android-permissions 
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...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Mon, 17 Nov 2014 22:40:54 +0100
Source: android-permissions
Binary: android-permissions
Architecture: source all
Version: 0.2
Distribution: unstable
Urgency: low
Maintainer: Android Tools 
Changed-By: Hans-Christoph Steiner 
Description:
 android-permissions - create gids that represent Android permissions
Closes: 767677
Changes:
 android-permissions (0.2) unstable; urgency=low
 .
   * force all groups to use Android gid (Closes: #767677)
   * remove inode chroot check that is failing on Android
Checksums-Sha1:
 7a668b321eeb1406662dc5e0c827a98562150c9e 1758 android-permissions_0.2.dsc
 192f925e5270fcf452e5c74a0a52ba85eb7fc015 11720 android-permissions_0.2.tar.xz
 f6ce6db539093509439f758c79ec1d93e60cb96b 7118 android-permissions_0.2_all.deb
Checksums-Sha256:
 fcedc44cd2262afea27a6e2afb7645afb2c7f54e6260dd30643578953af63cb0 1758 
android-permissions_0.2.dsc
 1bf9a4afb5670d8a95515e95fa17a1e48140c04326f281260b1136b54cfd6236 11720 
android-permissions_0.2.tar.xz
 7e230732ebd8be2f55180565c5a50710fa3db33f69b6a43e64d90b3bde27f3ad 7118 
android-permissions_0.2_all.deb
Files:
 01575d1019f7b702a68daf4d091055ff 1758 utils extra android-permissions_0.2.dsc
 9c6e040986d30076c23dda46c23997af 11720 utils extra 
android-permissions_0.2.tar.xz
 8f17550719eb6d4dfadc96361cc05dbb 7118 utils extra 
android-permissions_0.2_all.deb

-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.11 (GNU/Linux)
Comment: GPG for Android - https://guardianproject.info/code/gnupg/

iQIcBAEBCAAGBQJUam0sAAoJEJ8P5Yc3S76B6EgP/RcWzC+kjseBEIpunYRZJbWW
KMuxZ3R3DalM2xK7i1ThY1OsEZzjcbt0xDYQGCFogvdCio6vooI3WlujOzsA4txo
UALvBBf52pUJ/AVD1D3zKSMIi1CO9Jyu6pD6eHzDvIMWY7wIeXJpuTXShkyb59nN
6xvQ5ushPZlA3IvDLRTtr1v89F7kaaFXE0aTAHCX1ZdPDKidbMr6/etS3Vj0vvQA
ITPKjXrb8XQ+TEhm+4lB2eHnSqwX9qUJMIGMmLaO8tWHixVXnoAFiw5WTWxdtmXM
hoY4dFw5jXw9NGpP+xpUqCJPdXkrNUN/4y0wy+THzLB/vqGqH9lFmhW5Pqg+Hl8N
gjPxH3RZr6xhFRoe9syCNDCKQ+Z/CqfFsu/HJOSDBTD3fwTjAVNt6HXT0xod0raC
2Y0LsoGjOEOUnKMDLdelxMO6skiecjFsmOnrsfNeMFJCunFiEYfEUlU1hsApPMA1
YjoAE3FejVmraWlaSOx8C2WOnT0huICPe8a8Y22DhPO7V0chbL1RO6H36RIY//LS
CNyF6ytf8zvexZwBlRDawYdBAMQdmPVJoJmpbKT+WqlwIIRPogugaroGxRKBeE7P
GUPGZUqQn6MzbkpTCAdBe9hNPfZliR2Zdpf2n8jeRHIBqVLG1EGNJg7QVhQiTRAC
MuiZ7lNkB4ZupMSDfQz1
=NZQI
-END PGP SIGNATURE End Message ---

Bug#767170: marked as done (plymouth: makes update-initramfs fail because label.so is missing)

[Debian Bug Tracking System]

Your message dated Mon, 17 Nov 2014 22:03:56 +
with message-id 
and subject line Bug#767170: fixed in plymouth 0.9.0-9
has caused the Debian Bug report #767170,
regarding plymouth: makes update-initramfs fail because label.so is missing
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.)


-- 
767170: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=767170
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: plymouth
Version: 0.9.0-8
Severity: serious

Version 0.9.0-8 of the package fixed bug #764644 but now another file
needed for graphical themes is missing: label.so.

If a graphical theme was previously chosen, this makes update-initramfs
fail on removal of plymouth-themes because label.so is needed in
/usr/share/initramfs-tools/hooks/plymouth. After that, if the user
doesn't revert back to a text-only theme, this bug makes
install/upgrade/remove of other kernel-related  packages fail too (hence
the "serious" severity).

Regards,

-- 
Raphaël HALIMI




signature.asc
Description: OpenPGP digital signature
--- End Message ---
--- Begin Message ---
Source: plymouth
Source-Version: 0.9.0-9

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

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 767...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Sjoerd Simons  (supplier of updated plymouth 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...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Format: 1.8
Date: Mon, 17 Nov 2014 22:42:50 +0100
Source: plymouth
Binary: plymouth plymouth-x11 plymouth-dbg plymouth-dev plymouth-themes
Architecture: source amd64
Version: 0.9.0-9
Distribution: unstable
Urgency: medium
Maintainer: Laurent Bigonville 
Changed-By: Sjoerd Simons 
Description:
 plymouth   - boot animation, logger and I/O multiplexer
 plymouth-dbg - boot animation, logger and I/O multiplexer - debug symbols
 plymouth-dev - boot animation, logger and I/O multiplexer - development files
 plymouth-themes - boot animation, logger and I/O multiplexer - themes
 plymouth-x11 - boot animation, logger and I/O multiplexer - X11 renderer and 
log
Closes: 763276 767170 767937 768350
Changes:
 plymouth (0.9.0-9) unstable; urgency=medium
 .
   [ Laurent Bigonville ]
   * debian/control: Add a dependency against init-system-helpers as we are
 explicitly using deb-systemd-helper in the plymouth postinst script
 (Closes: #767937)
   * debian/local/plymouth.hook: Test if the plugin is present on disk before
 trying to copy it to the initramfs (Closes: #767170)
   * debian/control: Reword the package description. (Closes: #768350)
 Thanks to Justin B Rye 
   * debian/local/plymouth.hook: Properly copy .plymouth file into the
 initramfs for themes that are not shipping images, this should fix the
 tribar theme.
 .
   [ Sjoerd Simons ]
   * 
debian/patches/debian/patches/utils-Don-t-create-unix-sockets-non-blocking.patch:
 + Added. Don't open unix socket connections as non-blocking as the read
 function assume blocking sockets. Fixes plymouth failing to query the
 password from the user  (Closes: #763276)
Checksums-Sha1:
 59fc50d5b29ad207da189019ae3eb4088922e2be 2295 plymouth_0.9.0-9.dsc
 1bc09140061a6ed077540cd32025f4da6d094da7 24960 plymouth_0.9.0-9.debian.tar.xz
 781fc36d3ba4a1f56a25e0e628f3830afdd254a2 188664 plymouth_0.9.0-9_amd64.deb
 e1bcd91606ec91db98babed1a26cdd195da6efa4 21230 plymouth-x11_0.9.0-9_amd64.deb
 3cb40247c05a913d747c670765d49e652c110a86 572208 plymouth-dbg_0.9.0-9_amd64.deb
 c247d84d8acf00509eee22b977655ada0be4fd25 392754 plymouth-dev_0.9.0-9_amd64.deb
 6f0d76d8836283a31c78b888608de5a9aeaf82e8 663512 
plymouth-themes_0.9.0-9_amd64.deb
Checksums-Sha256:
 2cd8084ceac3e547ea957b4aac10954fcc3cc46d4db2ea0ce1680ec76466815a 2295 
plymouth_0.9.0-9.dsc
 d80b6abc2f9b684872e76f2d2704595dc74ab7bcdb6728014557d50483ac330f 24960 
plymouth_0.9.0-9.debian.tar.xz
 34c05a04a352f2ecb99f9c6255caddd5602d41c96421eed3dcce425c05f2a399 188664 
plymouth_0.9.0-9_amd64.deb
 a827a4cccef3916b87baf5009c109fd8eb005b1f86237695258dbd1b22dabe74 21230 
plymouth-x11_0.9.0-9_amd64.deb
 693a74b6aab8ebf32a14807405dda03a7ad5c072e3e7a233d658784c6a

Bug#768474: marked as done (plymouth: Wheezy to Jessie: E: /usr/share/initramfs-tools/hooks/plymouth failed with return 1.)

[Debian Bug Tracking System]

Your message dated Mon, 17 Nov 2014 22:03:56 +
with message-id 
and subject line Bug#767170: fixed in plymouth 0.9.0-9
has caused the Debian Bug report #767170,
regarding plymouth: Wheezy to Jessie: E: 
/usr/share/initramfs-tools/hooks/plymouth failed with return 1.
to be marked as done.

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

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


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

This issue was found when upgrading a host from Wheezy to Jessie using the 
following recipe on 2014-11-07 just after the freeze started:

sudo apt-get update && sudo apt-get --purge dist-upgrade && sudo apt-get 
--purge autoremove $(deborphan --guess-all)

Setting up libck-connector0:i386 (0.4.6-5) ...
Processing triggers for initramfs-tools ...
update-initramfs: Generating /boot/initrd.img-3.2.0-4-686-pae
E: /usr/share/initramfs-tools/hooks/plymouth failed with return 1.
update-initramfs: failed for /boot/initrd.img-3.2.0-4-686-pae with 1.
dpkg: error processing initramfs-tools (--configure):
 subprocess installed post-installation script returned error exit status 1
Processing triggers for libc-bin ...
Errors were encountered while processing:
 initramfs-tools
E: Sub-process /usr/bin/dpkg returned an error code (1)


-- System Information:
Debian Release: jessie/sid
  APT prefers testing
  APT policy: (1001, 'testing'), (1001, 'oldstable'), (101, 'stable')
Architecture: i386 (i686)

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

Versions of packages plymouth depends on:
ih  initramfs-tools0.109.1
ii  libc6  2.19-12
ii  libdrm22.4.40-1~deb7u2
iu  libpng12-0 1.2.50-2
ii  libudev1   215-5+b1
ii  multiarch-support  2.13-38+deb7u6

plymouth recommends no packages.

Versions of packages plymouth suggests:
ii  desktop-base 7.0.3
pn  plymouth-themes  

-- Configuration Files:
/etc/plymouth/plymouthd.conf changed:
[Daemon]
Theme=joy


-- no debconf information
--- End Message ---
--- Begin Message ---
Source: plymouth
Source-Version: 0.9.0-9

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

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 767...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Sjoerd Simons  (supplier of updated plymouth 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...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Format: 1.8
Date: Mon, 17 Nov 2014 22:42:50 +0100
Source: plymouth
Binary: plymouth plymouth-x11 plymouth-dbg plymouth-dev plymouth-themes
Architecture: source amd64
Version: 0.9.0-9
Distribution: unstable
Urgency: medium
Maintainer: Laurent Bigonville 
Changed-By: Sjoerd Simons 
Description:
 plymouth   - boot animation, logger and I/O multiplexer
 plymouth-dbg - boot animation, logger and I/O multiplexer - debug symbols
 plymouth-dev - boot animation, logger and I/O multiplexer - development files
 plymouth-themes - boot animation, logger and I/O multiplexer - themes
 plymouth-x11 - boot animation, logger and I/O multiplexer - X11 renderer and 
log
Closes: 763276 767170 767937 768350
Changes:
 plymouth (0.9.0-9) unstable; urgency=medium
 .
   [ Laurent Bigonville ]
   * debian/control: Add a dependency against init-system-helpers as we are
 explicitly using deb-systemd-helper in the plymouth postinst script
 (Closes: #767937)
   * debian/local/plymouth.hook: Test if the plugin is present on disk before
 trying to copy it to the initramfs (Closes: #767170)
   * debian/control: Reword the package description. (Closes: #768350)
 Thanks to Justin B Rye 
   * debian/local/plymouth.hook: Properly copy .plymouth file into the
 initramfs for themes that are not shipping images, this should fix the
 tribar theme.
 .
   [ Sjoerd Simons ]
   * 
debian/patches/debian/patches/utils-Don-t-create-unix-sockets-non-blocking.patch:
 + Added. Don't open unix socket connections as non-blocking as the read
 function assume blocking sockets. Fixes plymouth failing to query t

Bug#762984: initramfs-tools: Alert! /dev/vg0/usr does not exist

[Javier Barroso]

Hello,
On Tue, 07 Oct 2014 12:07:48 +0200
=?UTF-8?B?IklPaGFubmVzIG0gem3DtmxuaWcgKERlYmlhbi9HTlUpIg==?=
  wrote:
> On 10/07/2014 11:59 AM, IOhannes m zmoelnig wrote:
> > i am hit by the same problem.
> > as a temporary fix, i added the 'vgchange -ay' to
> >   /usr/share/initramfs-tools/scripts/local-top/lvm2
> > as adding it to
> >   /etc/initramfs-tools/scripts/local-top/vgscan
> > somehow did not work (most likely due wrong order of execution, but i did 
> > not
> > investigate further)
>
> i turned out that i had forgotten to set +x permissions for
> /etc/initramfs-tools/scripts/local-top/vgscan

Is there any reference about why this change is not made ?

All my debian systems with separated /usr are not booting until they
are fixed with "vgchange -ay". I don't like such manually changes.

Having a Debian Installation which not boot is a hurt for Debian (I'm
sure many people discard Debian when it doesn't boot, all Debian Sid
Users wait their boot problems solved upgrading its systems the next
week, having a updated Debian Sid two months without booting , is a
not go).

Should Debian Users discard /usr and merge into / ? Is this bug left
open with such idea at mind?

Where is the danger of such fix ? Do you know which would be the
perfect solution?

Thank you very much and sorry for my english


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

Bug#768285: python-pyvorbis-dbg: unhandled symlink to directory conversion: /usr/share/doc/PACKAGE

[Sandro Tosi]

Hello,

> Please check your "override_dh_installdocs" target in debian/rules. May
> be removing the duplicates would be enough?

yes, that's the right fix; uploading it in a few minutes.

Regards,
-- 
Sandro Tosi (aka morph, morpheus, matrixhasu)
My website: http://matrixhasu.altervista.org/
Me at Debian: http://wiki.debian.org/SandroTosi


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

Processed: your mail

[Debian Bug Tracking System]

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

> tag 768285 + pending
Bug #768285 [python-pyvorbis-dbg] python-pyvorbis-dbg: unhandled symlink to 
directory conversion: /usr/share/doc/PACKAGE
Ignoring request to alter tags of bug #768285 to the same tags previously set
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
768285: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=768285
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#767676: ola-rdm-tests: fails to install: subprocess installed post-installation script returned error exit status 10

[Jean Baptiste Favre]

Hello Helmut,

On 17/11/2014 20:11, Helmut Grohne wrote:
> Hi Jean Baptiste,
>
> On Sun, Nov 16, 2014 at 06:12:56PM +0100, Jean Baptiste Favre wrote:
> > I had a look on it during Debian BSP in Paris.
>
> Thanks for fixing RC bugs!
>
> > Problem is located into ola-rdm-test.postinst script:
> > - It uses debconf, for variable ola-rdm-tests/daemon, without providing
> > any template file
> > - It uses db_get and never db_input, thus ola-rdm-tests/daemon is
> never set
> > - debconf is not mentioned as dependency
> >
> > Please find attached a patch which removes debconf usage from postinst
> > script.
>
> I looked into this patch in more detail now and am willing to sponsor
> your NMU (which has been approved by Wouter by now). Unfortunately, this
> is not the only serious issue in ola-rdm-tests. In order to avoid
> multiple round-trips through the release team I advise /not/ to upload
> this fix as is (or at least only request an unblock after fixing the
> remaining issues).
>
> Your patch enables ola-rdm-tests to be installed. This is great and it
> enables us to remove it again. Unfortunately, after removing and purging
> /etc/defaults/ola-rdm-tests remains. The package fails to clean up after
> itself.
>
> Please try to improve on your patch to cover this case as well. Please
> try to use the tool piuparts to verify that this issue and potentially
> more problems are indeed fixed by your improved patch. When you submit a
> new patch, please Cc me and attach a .debdiff like you did here. If
> anything of the above is unclear, please ask.

Thanks for your advice. I'm working on a new version of the patch.
In the meantime, what should I do with my already uploaded NMU (on
mentors.debian.net). Maybe I should delete it just to be sure nobody
will upload it ?

I also noticed that init scripts ask for "dpkg-reconfigure package" to
enable service start, which is disabled by default. I guess this was OK
when debconf handles /etc/default/package content, but obviously it
won't work anymore.
I can change the init script to display another message.

Finally, I'm considering shipping /etc/default/ola which is not shipped
currently, in the same way as /etc/default/ola-rdm-tests. It controls
whether olad service is enabled or not.

And, last question, speaking about /etc/default files, I wonder which
are the best practices:
- name /etc/default/xxx file according to the init script which will use
them
- name /etc/default/xxx file according to the package which provide them

In my case, /etc/default/ola is provided by ola package but controls
olad service. Same with /etc/default/ola-rdm-tests which is provided by
eponym package to control rdm_test_server service.

All these would indeed increase the overall package quality, but I
wonder if this is not a bit "out of scope" work considering Jessie freeze.

Regards,
Jean Baptiste



signature.asc
Description: OpenPGP digital signature

Bug#768285: marked as done (python-pyvorbis-dbg: unhandled symlink to directory conversion: /usr/share/doc/PACKAGE)

[Debian Bug Tracking System]

Your message dated Mon, 17 Nov 2014 22:48:55 +
with message-id 
and subject line Bug#768285: fixed in pyvorbis 1.5-4
has caused the Debian Bug report #768285,
regarding python-pyvorbis-dbg: unhandled symlink to directory conversion: 
/usr/share/doc/PACKAGE
to be marked as done.

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

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


-- 
768285: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=768285
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: python-pyvorbis-dbg
Version: 1.5-3
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

an upgrade test with piuparts revealed that your package installs files
over existing symlinks and possibly overwrites files owned by other
packages. This usually means an old version of the package shipped a
symlink but that was later replaced by a real (and non-empty)
directory. This kind of overwriting another package's files cannot be
detected by dpkg.

This was observed on the following upgrade paths:

  wheezy -> jessie

For /usr/share/doc/PACKAGE this may not be problematic as long as both
packages are installed, ship byte-for-byte identical files and are
upgraded in lockstep. But once one of the involved packages gets
removed, the other one will lose its documentation files, too,
including the copyright file, which is a violation of Policy 12.5:
http://www.debian.org/doc/debian-policy/ch-docs.html#s-copyrightfile

For other overwritten locations anything interesting may happen.

Note that dpkg intentionally does not replace directories with symlinks
and vice versa, you need the maintainer scripts to do this.
See in particular the end of point 4 in
http://www.debian.org/doc/debian-policy/ch-maintainerscripts.html#s-unpackphase

It is recommended to use the dpkg-maintscript-helper commands
'dir_to_symlink' and 'symlink_to_dir' (available since dpkg 1.17.2)
to perform the conversion, ideally using d/$PACKAGE.mainstscript.
See dpkg-maintscript-helper(1) and dh_installdeb(1) for details.


>From the attached log (usually somewhere in the middle...):

1m14.2s ERROR: FAIL: silently overwrites files via directory symlinks:
  /usr/share/doc/python-ogg-dbg/changelog.Debian.gz (python-ogg-dbg) != 
/usr/share/doc/python-ogg/changelog.Debian.gz (python-ogg)
  /usr/share/doc/python-ogg-dbg/changelog.gz (python-ogg-dbg) != 
/usr/share/doc/python-ogg/changelog.gz (python-ogg)
  /usr/share/doc/python-ogg-dbg/copyright (python-ogg-dbg) != 
/usr/share/doc/python-ogg/copyright (python-ogg)
  /usr/share/doc/python-pyvorbis-dbg/changelog.Debian.gz (python-pyvorbis-dbg) 
!= /usr/share/doc/python-pyvorbis/changelog.Debian.gz (python-pyvorbis)
  /usr/share/doc/python-pyvorbis-dbg/changelog.gz (python-pyvorbis-dbg) != 
/usr/share/doc/python-pyvorbis/changelog.gz (python-pyvorbis)
  /usr/share/doc/python-pyvorbis-dbg/copyright (python-pyvorbis-dbg) != 
/usr/share/doc/python-pyvorbis/copyright (python-pyvorbis)


cheers,

Andreas


python-pyvorbis-dbg_1.5-3.log.gz
Description: application/gzip
--- End Message ---
--- Begin Message ---
Source: pyvorbis
Source-Version: 1.5-4

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

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 768...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Sandro Tosi  (supplier of updated pyvorbis 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...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Format: 1.8
Date: Mon, 17 Nov 2014 22:36:50 +
Source: pyvorbis
Binary: python-pyvorbis python-pyvorbis-dbg
Architecture: source amd64
Version: 1.5-4
Distribution: unstable
Urgency: medium
Maintainer: Sandro Tosi 
Changed-By: Sandro Tosi 
Description:
 python-pyvorbis - Python interface to the Ogg Vorbis library
 python-pyvorbis-dbg - Python interface to the Ogg Vorbis library (debug 
extension)
Closes: 768285
Changes:
 pyvorbis (1.5-4) unstable; urgency=medium
 .
   * debian/rules
 - correctly link -dbg doc directory to the main package one; thanks to
   Andreas Beckmann for the report and to Jean-Michel Nirgal Vourgère for 
the
   first patch; Closes: #768285
Checksums-Sha1:
 b3196069c273e94f322e3912d8fdd903c93eec2b 1484 pyvorbis_1.5-4.dsc
 f3f6

Bug#769888: marked as done (wine-development: Wrong Build-Depends in debian/control file)

[Debian Bug Tracking System]

Your message dated Tue, 18 Nov 2014 00:04:10 +0100
with message-id <20141118000410.77043...@heffalump.sk2.org>
and subject line Re: [pkg-wine-party] Bug#769888: wine-development: Wrong 
Build-Depends in debian/control file
has caused the Debian Bug report #769888,
regarding wine-development: Wrong Build-Depends in debian/control file
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.)


-- 
769888: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=769888
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: wine-development
Version: 1.7.29-3
Severity: serious
Tags: patch
Justification: fails to build from source (but built successfully in the past)

Dear Maintainer,

Actually, it's impossible to download the build-dependances of wine-development 
package (apt-get build-dep wine-development:i386).
I have this error after to launch the previous command :

"E: Impossible to satisfy dependences Build-Depends for wine-development : 
libtiff-dev"

If I check in "https://packages.debian.org/";, "libtiff-dev" package does not 
exist. There are only "libtiff4-dev" package (oldlibs)
and "libtiff5-dev" (libdevel).

Thanks to correct this error to build myself Wine (wine-git) in a chroot.

Cheers,
Max

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

Kernel: Linux 3.16.0-4-amd64 (SMP w/4 CPU cores)
Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
--- debian/control	2014-11-02 04:44:58.0 +0100
+++ debian/control	2014-11-17 11:40:56.594114565 +0100
@@ -35,7 +35,7 @@
  libxml2-dev,
  libgsm1-dev,
  libjpeg-dev,
- libtiff-dev,
+ libtiff5-dev,
  libpcap-dev,
  liblcms2-dev,
  libldap2-dev,
--- End Message ---
--- Begin Message ---
Hi Maxime,

On Mon, 17 Nov 2014 11:52:32 +0100, Maxime Lombard 
wrote:
> Actually, it's impossible to download the build-dependances of
> wine-development package (apt-get build-dep wine-development:i386). I have
> this error after to launch the previous command :
> 
> "E: Impossible to satisfy dependences Build-Depends for wine-development :
> libtiff-dev"
> 
> If I check in "https://packages.debian.org/";, "libtiff-dev" package does
> not exist. There are only "libtiff4-dev" package (oldlibs) and
> "libtiff5-dev" (libdevel).
> 
> Thanks to correct this error to build myself Wine (wine-git) in a chroot.

You can't use multiarch specifiers like that, you need to build in an i386
chroot if you want to build wine32.

apt-get build-dep wine-development

works fine on amd64 and i386, even with libtiff-dev as a build-dependency.

Regards,

Stephen


pgp9PqxPzFwf3.pgp
Description: OpenPGP digital signature
--- End Message ---

Bug#769967: virtualbox-guest-utils: Starting VirtualBox Additions No suitable module for running kernel found ... failed!

[Tomas Fasth]

Package: virtualbox-guest-utils
Version: 4.3.18-dfsg-1
Severity: grave
Justification: renders package unusable

I have two Debian installations running as guests in a VirtualBox installation.
One is stable, the other one testing. Both have virtual-guest-utils and
virtual-guest-dkms packages installed. 

In stable the host time sync works, in testing it does not. Here is what can be
found in the system log after an attempt to start the virtual-guest-utils 
service:

// log extract begins
nov 10 01:36:47 debian-systemd sudo[1429]: tomfa : TTY=pts/0 ; PWD=/home/tomfa 
; USER=root ; COMMAND=/usr/sbin/service virtualbox-guest-utils start
nov 10 01:36:47 debian-systemd sudo[1429]: pam_unix(sudo:session): session 
opened for user root by tomfa(uid=0)
nov 10 01:36:47 debian-systemd virtualbox-guest-utils[1447]: Starting 
VirtualBox AdditionsNo suitable module for running kernel found ... failed!
nov 10 01:36:47 debian-systemd virtualbox-guest-utils[1447]: failed!
nov 10 01:36:47 debian-systemd sudo[1429]: pam_unix(sudo:session): session 
closed for user root
nov 10 01:36:47 debian-systemd systemd[1]: virtualbox-guest-utils.service: 
control process exited, code=exited status=1
nov 10 01:36:47 debian-systemd systemd[1]: Failed to start LSB: VirtualBox 
Linux Additions.
// log extract ends

It seems like the vboxguest kernel module is not loading correctly.

Please give advice on possible workaround or if you need further details.

Thank you for providing these packages. Looking forward to a solution.

Tomas Fasth

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

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

Versions of packages virtualbox-guest-utils depends on:
ii  adduser   3.113+nmu3
ii  dpkg  1.17.21
ii  libc6 2.19-12
ii  libpam0g  1.1.8-3.1
ii  pciutils  1:3.2.1-3

Versions of packages virtualbox-guest-utils recommends:
ii  virtualbox-guest-dkms  4.3.18-dfsg-1
ii  virtualbox-guest-x11   4.3.18-dfsg-1

virtualbox-guest-utils 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#769974: minimodem: FTBFS on armhf

[Hector Oron]

Source: minimodem
Version: 0.20-1
Severity: serious
Justification: FTBFS



Hello,

  Your package fails to build from source on Debian autobuilder network.

  Please check your package build logs at:
  

  Full log at: 
  
https://buildd.debian.org/status/fetch.php?pkg=minimodem&arch=armhf&ver=0.20-1&stamp=1415908645

Best regards


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

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


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

Bug#769975: pastimatch: FTBFS on several arches

[Hector Oron]

Source: pastimatch
Version: 1.5.16+dfsg-2
Severity: serious
Justification: FTBFS



Hello,

  Your package fails to build from source on Debian autobuilder network.

  Please check your package build logs at:
  
  
Best regards


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

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


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

Bug#769976: vnc4: FTBFS on powerpc

[Hector Oron]

Source: vnc4
Version: 4.1.1+X4.3.0-37.3
Severity: serious
Justification: FTBFS



Hello,

  Your package fails to build from source on Debian autobuilder network.

  Please check your package build logs at:
  
  
  Full log at:

https://buildd.debian.org/status/fetch.php?pkg=vnc4&arch=powerpc&ver=4.1.1%2BX4.3.0-37.3&stamp=1416239432

Best regards


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

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


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

Bug#769764: marked as done (ironic-common: fails to upgrade from 'sid': No support for ALTER of constraints in SQLite dialect)

[Debian Bug Tracking System]

Your message dated Tue, 18 Nov 2014 08:13:04 +0800
with message-id <546a8f10.1040...@debian.org>
and subject line Re: [PKG-Openstack-devel] Bug#769764: ironic-common: fails to 
upgrade from 'sid': No support for ALTER of constraints in SQLite dialect
has caused the Debian Bug report #769764,
regarding ironic-common: fails to upgrade from 'sid': No support for ALTER of 
constraints in SQLite dialect
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.)


-- 
769764: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=769764
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: ironic-common
Version: 2014.2-2
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

during a test with piuparts I noticed your package fails to upgrade from
'sid'.
It installed fine in 'sid', then the upgrade to 'experimental' fails.

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

  Setting up ironic-common (2014.2-2) ...
  Installing new version of config file 
/etc/ironic/rootwrap.d/ironic-utils.filters ...
  PKG-Openstack now calling: dbc_go ironic-common configure 2014.1-10
  dbconfig-common: writing config to /etc/dbconfig-common/ironic-common.conf
  INFO  [alembic.migration] Context impl SQLiteImpl.
  INFO  [alembic.migration] Will assume non-transactional DDL.
  INFO  [alembic.migration] Running upgrade 3cb628139ea4 -> 31baaf680d2b, Add 
Node instance info
  INFO  [alembic.migration] Running upgrade 31baaf680d2b -> 3bea56f25597, add 
unique constraint to instance_uuid
  CRITI [ironic] NotImplementedError: No support for ALTER of constraints in 
SQLite dialect
  Traceback (most recent call last):
File "/usr/bin/ironic-dbsync", line 10, in 
  sys.exit(main())
File "/usr/lib/python2.7/dist-packages/ironic/cmd/dbsync.py", line 100, in 
main
  CONF.command.func()
File "/usr/lib/python2.7/dist-packages/ironic/cmd/dbsync.py", line 36, in 
upgrade
  migration.upgrade(CONF.command.revision)
File "/usr/lib/python2.7/dist-packages/ironic/db/migration.py", line 36, in 
upgrade
  return get_backend().upgrade(version)
File "/usr/lib/python2.7/dist-packages/ironic/db/sqlalchemy/migration.py", 
line 56, in upgrade
  alembic.command.upgrade(config, revision or 'head')
File "/usr/lib/python2.7/dist-packages/alembic/command.py", line 125, in 
upgrade
  script.run_env()
File "/usr/lib/python2.7/dist-packages/alembic/script.py", line 203, in 
run_env
  util.load_python_file(self.dir, 'env.py')
File "/usr/lib/python2.7/dist-packages/alembic/util.py", line 212, in 
load_python_file
  module = load_module_py(module_id, path)
File "/usr/lib/python2.7/dist-packages/alembic/compat.py", line 58, in 
load_module_py
  mod = imp.load_source(module_id, path, fp)
File 
"/usr/lib/python2.7/dist-packages/ironic/db/sqlalchemy/alembic/env.py", line 
54, in 
  run_migrations_online()
File 
"/usr/lib/python2.7/dist-packages/ironic/db/sqlalchemy/alembic/env.py", line 
51, in run_migrations_online
  context.run_migrations()
File "", line 7, in run_migrations
File "/usr/lib/python2.7/dist-packages/alembic/environment.py", line 688, 
in run_migrations
  self.get_context().run_migrations(**kw)
File "/usr/lib/python2.7/dist-packages/alembic/migration.py", line 258, in 
run_migrations
  change(**kw)
File 
"/usr/lib/python2.7/dist-packages/ironic/db/sqlalchemy/alembic/versions/3bea56f25597_add_unique_constraint_to_instance_uuid.py",
 line 33, in upgrade
  ["instance_uuid"])
File "", line 7, in create_unique_constraint
File "/usr/lib/python2.7/dist-packages/alembic/operations.py", line 621, in 
create_unique_constraint
  schema=schema, **kw)
File "/usr/lib/python2.7/dist-packages/alembic/ddl/sqlite.py", line 21, in 
add_constraint
  "No support for ALTER of constraints in SQLite dialect")
  NotImplementedError: No support for ALTER of constraints in SQLite dialect
  dpkg: error processing package ironic-common (--configure):
   subprocess installed post-installation script returned error exit status 1
  Processing triggers for libc-bin (2.19-13) ...
  Errors were encountered while processing:
   ironic-common


cheers,

Andreas


ironic-common_2014.2-2.log.gz
Description: application/gzip
--- End Message ---
--- Begin Message ---
On 11/16/2014 06:35 PM, Andreas Beckmann wrote:
> Package: ironic-common
> Version: 2014.2-2
> Severity: serious
> User: debian...@lists.debian.org
> Usertags: piuparts
> 
> Hi,
> 
> during a test with piuparts I noticed your package fails to upgrade from
> 'sid'.
> It installed 

Processed: cl-portable-aserve: diff for NMU version 1.2.42+cvs.2010.02.08-dfsg-1.2

[Debian Bug Tracking System]

Processing control commands:

> tags 767811 + pending
Bug #767811 [cl-acl-compat] cl-acl-compat: fails to install: 
/usr/sbin/register-common-lisp-source: not found
Added tag(s) pending.
> tags 769509 + pending
Bug #769509 [cl-webactions] cl-webactions: installation fails
Added tag(s) pending.
> tags 769512 + pending
Bug #769512 [cl-aserve] cl-aserve: installation fails
Added tag(s) pending.
> tags 769513 + pending
Bug #769513 [cl-htmlgen] cl-htmlgen: installation fails
Added tag(s) pending.

-- 
767811: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=767811
769509: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=769509
769512: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=769512
769513: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=769513
769978: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=769978
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#769764: [PKG-Openstack-devel] Bug#769764: ironic-common: fails to upgrade from 'sid': No support for ALTER of constraints in SQLite dialect

[Andreas Beckmann]

On 2014-11-18 01:13, Thomas Goirand wrote:
> Therefore, I'm sorry, but I will not work on fixing this bug (largely,
> because I don't think it will help any users, because there is no user
> for Ironic 2014.1.x). For me, the only time when Ironic starts to be
> useful is with the Juno release (ie: 2014.2.x), so I will only put some
> upgrades efforts starting on this release.

I have no clue what these packages do (besides failing in piuparts) ;-)

> More over, this issue is, I believe, only happening when using SQLite,
> which anyway, nobody uses (I maintain it only so that piuparts of this
> kind can succeed...).

piuparts could enable other databases as well to test your packages, I
just enabled the "default one" i.e. that one that shows an error in the
log (like sqlite3 command not found). If you prefer to test against a
"real" database, give me some hints which one and how to enable it
(preseeding would work for instance).

> Therefore, closing this bug, without attempting to solve it.

No problem. I may add Found: in future versions that show the same
error, that may reopen this bug - feel free to close again if I miss this.
(the piuparts-analyze script need exact version matches in the bts to
mark a log as "known and bugged")


Andreas


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

Bug#768598: NMUdiff for patch to fix this bug

[Don Armstrong]

Control: tag -1 patch pending

Below please find the NMU diff which fixes #768599 (from fontconfig's
end). This will still need Breaks in dpkg. I have uploaded this to
delayed/2. Please override with a maintainer upload if necessary.

diff -Nru fontconfig-2.11.0/debian/changelog fontconfig-2.11.0/debian/changelog
--- fontconfig-2.11.0/debian/changelog  2014-08-20 06:36:05.0 -0700
+++ fontconfig-2.11.0/debian/changelog  2014-11-10 11:30:45.0 -0800
@@ -1,3 +1,13 @@
+fontconfig (2.11.0-6.2) unstable; urgency=medium
+
+  * Non-maintainer upload to delayed
+  * Switch to noawait triggers to allow self-triggering; will still need
+Breaks from dpkg to resolve this (closes: #768599)
+  * Add Pre-Depends on dpkg to allow for noawait just in case this gets
+backported to squeeze.
+
+ -- Don Armstrong   Mon, 10 Nov 2014 11:26:37 -0800
+
 fontconfig (2.11.0-6.1) unstable; urgency=low
 
   * Non-maintainer upload to delayed.
diff -Nru fontconfig-2.11.0/debian/control fontconfig-2.11.0/debian/control
--- fontconfig-2.11.0/debian/control2014-08-20 06:32:13.0 -0700
+++ fontconfig-2.11.0/debian/control2014-11-10 11:28:42.0 -0800
@@ -18,6 +18,7 @@
 Section: fonts
 Architecture: any
 Depends: ${shlibs:Depends}, ${misc:Depends}, fontconfig-config
+Pre-Depends: dpkg (>= 1.16.1)
 Replaces: fontconfig-config (<< 2.5.93-1)
 Multi-Arch: foreign
 Description: generic font configuration library - support binaries
diff -Nru fontconfig-2.11.0/debian/fontconfig.triggers 
fontconfig-2.11.0/debian/fontconfig.triggers
--- fontconfig-2.11.0/debian/fontconfig.triggers2013-06-25 
11:12:30.0 -0700
+++ fontconfig-2.11.0/debian/fontconfig.triggers2014-11-10 
11:28:03.0 -0800
@@ -1,3 +1,3 @@
-interest /usr/share/fonts
-interest /usr/share/ghostscript/fonts
-interest /usr/share/texmf/fonts
+interest-noawait /usr/share/fonts
+interest-noawait /usr/share/ghostscript/fonts
+interest-noawait /usr/share/texmf/fonts


-- 
Don Armstrong  http://www.donarmstrong.com

Junkies were all knitted together in a loose global macrame, the
intercontinental freemasonry of narcotics.
 -- Bruce Sterling, _Holy Fire_ p257


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

Processed: NMUdiff for patch to fix this bug

[Debian Bug Tracking System]

Processing control commands:

> tag -1 patch pending
Bug #768598 [fontconfig] fontconfig: cycle found while processing triggers
Added tag(s) pending and patch.

-- 
768598: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=768598
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#768272: marked as done (lilypond-doc: unhandled symlink to directory conversion: /usr/share/info/lilypond)

[Debian Bug Tracking System]

Your message dated Tue, 18 Nov 2014 01:49:00 +
with message-id 
and subject line Bug#768272: fixed in lilypond 2.18.2-4
has caused the Debian Bug report #768272,
regarding lilypond-doc: unhandled symlink to directory conversion: 
/usr/share/info/lilypond
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.)


-- 
768272: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=768272
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: lilypond-doc
Version: 2.18.2-3
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

an upgrade test with piuparts revealed that your package installs files
over existing symlinks and possibly overwrites files owned by other
packages. This usually means an old version of the package shipped a
symlink but that was later replaced by a real (and non-empty)
directory. This kind of overwriting another package's files cannot be
detected by dpkg.

This was observed on the following upgrade paths:

  wheezy -> jessie

For /usr/share/doc/PACKAGE this may not be problematic as long as both
packages are installed, ship byte-for-byte identical files and are
upgraded in lockstep. But once one of the involved packages gets
removed, the other one will lose its documentation files, too,
including the copyright file, which is a violation of Policy 12.5:
http://www.debian.org/doc/debian-policy/ch-docs.html#s-copyrightfile

For other overwritten locations anything interesting may happen.

Note that dpkg intentionally does not replace directories with symlinks
and vice versa, you need the maintainer scripts to do this.
See in particular the end of point 4 in
http://www.debian.org/doc/debian-policy/ch-maintainerscripts.html#s-unpackphase

It is recommended to use the dpkg-maintscript-helper commands
'dir_to_symlink' and 'symlink_to_dir' (available since dpkg 1.17.2)
to perform the conversion, ideally using d/$PACKAGE.mainstscript.
See dpkg-maintscript-helper(1) and dh_installdeb(1) for details.


>From the attached log (usually somewhere in the middle...):

1m23.9s INFO: dirname part contains a symlink:
  /usr/share/info/lilypond/00 (lilypond-doc) != 
/usr/share/doc/lilypond/html/Documentation/00 (?)
  /usr/share/info/lilypond/00/lily-1d0bbe5b.png (lilypond-doc) != 
/usr/share/doc/lilypond/html/Documentation/00/lily-1d0bbe5b.png (?)
  /usr/share/info/lilypond/00/lily-21876455.png (lilypond-doc) != 
/usr/share/doc/lilypond/html/Documentation/00/lily-21876455.png (?)
  /usr/share/info/lilypond/00/lily-3b688333.png (lilypond-doc) != 
/usr/share/doc/lilypond/html/Documentation/00/lily-3b688333.png (?)
  /usr/share/info/lilypond/00/lily-43d93de7.png (lilypond-doc) != 
/usr/share/doc/lilypond/html/Documentation/00/lily-43d93de7.png (?)

  /usr/share/info/lilypond/ff/lily-f31b0618.png (lilypond-doc) != 
/usr/share/doc/lilypond/html/Documentation/ff/lily-f31b0618.png (?)
  /usr/share/info/lilypond/ff/lily-f6ebaf30.png (lilypond-doc) != 
/usr/share/doc/lilypond/html/Documentation/ff/lily-f6ebaf30.png (?)
  /usr/share/info/lilypond/ff/lily-f8c03253.png (lilypond-doc) != 
/usr/share/doc/lilypond/html/Documentation/ff/lily-f8c03253.png (?)
  /usr/share/info/lilypond/ly-examples (lilypond-doc) != 
/usr/share/doc/lilypond/html/Documentation/ly-examples (?)
  /usr/share/info/lilypond/ly-examples/ancient-headword.png (lilypond-doc) != 
/usr/share/doc/lilypond/html/Documentation/ly-examples/ancient-headword.png (?)
  /usr/share/info/lilypond/ly-examples/aucun-snippet.png (lilypond-doc) != 
/usr/share/doc/lilypond/html/Documentation/ly-examples/aucun-snippet.png (?)
  /usr/share/info/lilypond/ly-examples/bach-bwv610.png (lilypond-doc) != 
/usr/share/doc/lilypond/html/Documentation/ly-examples/bach-bwv610.png (?)
  /usr/share/info/lilypond/ly-examples/bach-schenker.png (lilypond-doc) != 
/usr/share/doc/lilypond/html/Documentation/ly-examples/bach-schenker.png (?)
  /usr/share/info/lilypond/ly-examples/cary.png (lilypond-doc) != 
/usr/share/doc/lilypond/html/Documentation/ly-examples/cary.png (?)

  /usr/share/info/lilypond/pictures/text-input-parts-single-output.png 
(lilypond-doc) != 
/usr/share/doc/lilypond/html/Documentation/pictures/text-input-parts-single-output.png
 (?)
  /usr/share/info/lilypond/pictures/text-input-pop-annotate.png (lilypond-doc) 
!= 
/usr/share/doc/lilypond/html/Documentation/pictures/text-input-pop-annotate.png 
(?)
  /usr/share/info/lilypond/pictures/text-input-pop-output.png (lilypond-doc) != 
/usr/share/doc/lilypond/html/Documentation/pictures/text-input-pop-output.png 
(?)
  /usr/share/info/lilypond/pictures/text-input-score-annotate.png 
(lilypo

Bug#768509: debian-edu-config: After upgrading a Wheezy main-server to Debian 7.7 the Gosa gui fails to connect to LDAP

[David Prévot]

[ Adding php maintainers, security team and release team to the loop. ]

Hi,

Le 09/11/2014 17:45, Wolfgang Schweer a écrit :

[ About a severe issue that recently popped up. ]

> Seems to be that the update from php version 5.4.4 to 5.4.34 (new 
> upstream release) caused the problem.

I can confirm being hit by this issue, and downgrading from 5.4.34
recently introduced by DSA 3064-1 to 5.4.4 still in stable allowed to
workaround this problem (thanks by the way for the various
investigations and workarounds provided in this bug reports).

That makes me wonder, that even if we’ve been warned in the DSA that the
new version “includes additional bug fixes, new features and possibly
incompatible changes.”, simply “refer[ing] to the upstream
changelog for more information” sounds a bit like closing eyes in the
hope nothing will break.

Maybe this upgrade will allow us to spot and fix a severe issue in gosa
this time, but changing the way to handle (security) updates during the
lifetime of a stable release may not be the best way to keep it stable.

I do understand that safely backporting (security) patches may be hard
sometime, but that’s part of what (used to) make the quality and
robustness reputation of Debian, and it would be nice to only use such
upgrade to new (minor) version as a last resort only. Potentially
breaking user scripts on security updates is bad, but risking to break
package distributed in stable sounds even worse.

Regards

David

P.-S.: hopefully, the increase in DEP-8 adoption and structures like
ci.d.n and jenkins.d.n will allow us to spot similar issues in stable
sooner in a not too distant future.



signature.asc
Description: OpenPGP digital signature

Bug#769625: Unreproducible

[積丹尼 Dan Jacobson]

A fresh reinstall still reproduces it on my j3 machine.
No bug however on j2.

NW> Could this be related to a plugin or extension installed on the system?

Here is a list of the different packages between j2 (left) and j3.

mountpoint -q /cf/
set -xe; m=/cf/versions-$(hostname);\
if test $m -nt /var/lib/dpkg/status -a \
$m -nt /var/lib/aptitude/pkgstates; then exit; fi;\
apt-show-versions > /tmp/VERsions;\
test -s /tmp/VERsions;\
sort -o $m /tmp/VERsions || { echo try again as root first; false;}
: ${k?}
for i in /cf/versions-jidanni[23]; do cut -f 1 -d ' ' $i > /tmp/`basename $i`; 
done;\
comm -3 /tmp/versions-jidanni[23]
acpi-fakekey:i386/unstable
acpi-support-base:all/unstable
acpi-support:all/unstable
alien:all/unstable
alsa-base:all/unstable
apache2-bin:i386/unstable
apache2-data:all/unstable
apache2-utils:i386/unstable
apache2:i386/unstable
apt-listchanges:all/unstable
autoconf:all/unstable
bc:i386/unstable
chromium-inspector:all/unstable
cpufrequtils:i386/unstable
cups-bsd:i386/unstable
cups-client:i386/unstable
cups-common:all/unstable
dbconfig-common:all/unstable
debconf-i18n:all/unstable
debhelper:all/unstable
debugedit:i386/unstable
dmidecode:i386/unstable
eeepc-acpi-scripts:all/unstable
fancontrol:all/unstable
firmware-ipw2x00:all/unstable
fonts-arphic-bkai00mp:all/unstable
fonts-arphic-bsmi00lp:all/unstable
fonts-arphic-gbsn00lp:all/unstable
fonts-arphic-gkai00mp:all/unstable
fonts-arphic-ukai:all/unstable
gconf2:i386/unstable
gettext:i386/unstable
git-man:all/experimental
git:i386/experimental
glibc-doc-reference:all/unstable
gnome-mime-data:all/unstable
google-earth-stable:i386
gsfonts-x11:all/unstable
guile-1.8-libs:i386/unstable
id3v2:i386/unstable
init:i386/unstable
intltool-debian:all/unstable
iputils-ping:i386/unstable
isc-dhcp-client:i386/unstable
isc-dhcp-common:i386/unstable
iselect:i386/unstable
lftp:i386/unstable
liba52-0.7.4:i386/unstable
libaio1:i386/unstable
libapache2-mod-php5:i386/unstable
libaprutil1-dbd-mysql:i386/unstable
libaprutil1-ldap:i386/unstable
libapt-inst1.5:i386
libasn1-8-heimdal:i386/unstable
libasprintf-dev:i386/unstable
libass5:i386/experimental
libavahi-glib1:i386/unstable
libbonobo2-0:i386/unstable
libbonobo2-common:all/unstable
libbs2b0:i386/unstable
libcairo-perl:i386/unstable
libcanberra0:i386/unstable
libccid:i386/unstable
libcdio-cdda1:i386/unstable
libcdio-paranoia1:i386/unstable
libcdio13:i386/unstable
libclass-isa-perl:all/unstable
libcpufreq0:i386/unstable
libcrypt-ssleay-perl:i386/unstable
libdbd-mysql-perl:i386/unstable
libdbi-perl:i386/unstable
libdca0:i386/unstable
libdns-export100:i386/unstable
libdv4:i386/unstable
libdvdread4:i386/unstable
libemail-address-perl:all/unstable
libemail-date-format-perl:all/unstable
libemail-messageid-perl:all/unstable
libemail-mime-contenttype-perl:all/unstable
libemail-mime-encodings-perl:all/unstable
libemail-mime-perl:all/unstable
libemail-simple-perl:all/unstable
libenca0:i386/unstable
liberror-perl:all/unstable
libfaad2:i386/unstable
libgeo-distance-perl:all/unstable
libgettextpo-dev:i386/unstable
libgettextpo0:i386/unstable
libglade2-0:i386/unstable
libglib-perl:i386/unstable
libglib2.0-data:all/unstable
libgnome-2-0:i386/unstable
libgnome2-0:i386/unstable
libgnome2-bin:i386/unstable
libgnome2-common:all/unstable
libgnomevfs2-0:i386/unstable
libgnomevfs2-common:all/unstable
libgnutls-openssl27:i386/experimental
libgssapi3-heimdal:i386/unstable
libgtk2-perl:i386/unstable
libhcrypto4-heimdal:i386/unstable
libheimbase1-heimdal:i386/unstable
libheimntlm0-heimdal:i386/unstable
libhtml-linkextractor-perl:all/unstable
libhx509-5-heimdal:i386/unstable
libid3-3.8.3c2a:i386/unstable
libio-pty-perl:i386/unstable
libio-stringy-perl:all/unstable
libirs-export91:i386/unstable
libisc-export95:i386/unstable
libisccfg-export90:i386/unstable
libjack0:i386/unstable
libjcode-pm-perl:i386/unstable
libjs-codemirror:all/unstable
libjs-jquery-cookie:all/unstable
libjs-jquery-event-drag:all/unstable
libjs-jquery-metadata:all/unstable
libjs-jquery-mousewheel:all/unstable
libjs-jquery-tablesorter:all/unstable
libjs-jquery-ui:all/unstable
libjs-sphinxdoc:all/unstable
libjs-underscore:all/unstable
libkrb5-26-heimdal:i386/unstable
libldb1:i386/unstable
liblircclient0:i386/unstable
liblist-moreutils-perl:i386/unstable
liblua5.1-0:i386/unstable
libmad0:i386/unstable
libmcrypt4:i386/unstable
libmediawiki-api-perl:all/unstable
libmime-types-perl:all/unstable
libmodule-implementation-perl:all/unstable
libmodule-runtime-perl:all/unstable
libmpg123-0:i386/unstable
libmuparser-doc:all/unstable
libneon27-gnutls:i386/unstable
libnet-daemon-perl:all/unstable
libnl-3-200:i386/unstable
libnl-genl-3-200:i386/unstable
libntdb1:i386/unstable
libonig2:i386/unstable
liborbit-2-0:i386/unstable
libpango-perl:i386/unstable
libpaper-utils:i386/unstable
libparams-classify-perl:i386/unstable
libparams-validate-perl:i386

Bug#769981: reprepro complaining about 'all' architecture

[Michael P. Soulier]

Package: reprepro
Version: 4.12.5-1
Severity: serious
Justification: Policy 5.6.8

Dear Maintainer,

I tried to include a package in my existing custom apt repository, and now all
it does is complain about the 'all' architecture, which is apparently a valid
architecture.

https://www.debian.org/doc/debian-policy/ch-controlfields.html#s-f-Architecture

bear:/var/www/apt# reprepro list wheezy
Error: Distribution wheezy contains an architecture called 'all'.
There have been errors!

So now I cannot update my repository. This worked previously, and I do not
understand the nature of the complaint. It is not providing sufficient detail,
and my inquiries on the debian-user list go unanswered. I am not sure how to
proceed.

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

Kernel: Linux 3.2.0-4-486
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 reprepro depends on:
ii  libarchive12   3.0.4-3+nmu1
ii  libbz2-1.0 1.0.6-4
ii  libc6  2.13-38+deb7u4
ii  libdb5.1   5.1.29-5
ii  libgpg-error0  1.10-3.1
ii  libgpgme11 1.2.0-1.4+deb7u1
ii  zlib1g 1:1.2.7.dfsg-13

Versions of packages reprepro recommends:
ii  apt  0.9.7.9+deb7u5

Versions of packages reprepro suggests:
pn  gnupg-agent  
pn  inoticoming  
pn  lzip 
ii  lzma 9.22-2
ii  xz-utils [lzma]  5.1.1alpha+20120614-2

-- no debconf information


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

Bug#769625: Unreproducible

[積丹尼 Dan Jacobson]

Indeed installing libgcrypt11 makes the bug go away.


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

Bug#768670: marked as done (ruby-moneta: FTBFS in jessie: build-dependency not installable: ruby-activesupport-3.2 (>= 3.2.11~))

[Debian Bug Tracking System]

Your message dated Tue, 18 Nov 2014 03:48:55 +
with message-id 
and subject line Bug#768670: fixed in ruby-moneta 0.7.20-2.1
has caused the Debian Bug report #768670,
regarding ruby-moneta: FTBFS in jessie: build-dependency not installable: 
ruby-activesupport-3.2 (>= 3.2.11~)
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.)


-- 
768670: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=768670
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: ruby-moneta
Version: 0.7.20-2
Severity: serious
Tags: jessie sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20141108 qa-ftbfs
Justification: FTBFS in jessie on amd64

Hi,

During a rebuild of all packages in jessie (in a jessie chroot, not a
sid chroot), your package failed to build on amd64.

Relevant part (hopefully):
> ┌──┐
> │ Install ruby-moneta 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-ruby-moneta-dummy : Depends: ruby-activesupport-3.2 (>= 
> 3.2.11~) 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://aws-logs.debian.net/ftbfs-logs/2014/11/08/ruby-moneta_0.7.20-2_jessie.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: ruby-moneta
Source-Version: 0.7.20-2.1

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

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 768...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Scott Kitterman  (supplier of updated ruby-moneta 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...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Mon, 17 Nov 2014 21:41:08 -0500
Source: ruby-moneta
Binary: ruby-moneta
Architecture: source all
Version: 0.7.20-2.1
Distribution: unstable
Urgency: medium
Maintainer: Joshua Timberman 
Changed-By: Scott Kitterman 
Description:
 ruby-moneta - Ruby interface to multiple key/value stores
Closes: 768670
Changes:
 ruby-moneta (0.7.20-2.1) unstable; urgency=medium
 .
   * Non-maintainer upload.
   * Change build-depends-indep on ruby-activesupport to ruby-activesupport
 that is currently available for Jessie (Closes: #768670)
   * Move debhelper (>= 8) and gem2deb (>= 0.3.0~) to build-depends from
 build-depends-indep (Needed for clean)
Checksums-Sha1:
 29ea5ae30e26073e24c7f435ef1ea88c901760ba 2286 ruby-moneta_0.7.20-2.1.dsc
 d6a2732c98cc60a93a83a5c3317b692cb520eb90 11232 
ruby-moneta_0.7.20-2.1.debian.tar.xz
 e69a2a657d0574b2d9b9c0a706e35acb5fd0ce68 34074 ruby-moneta_0.7.20-2.1_all.deb
Checksums-Sha256:
 02dbb7018fcfa03cf64f4d9a1f39f09916e9394052a7d3c99e4495440b116d9a 2286 
ruby-moneta_0.7.20-2.1.dsc
 76eafa15765fdd50319a9977bdc0a23e4ffb40c7a3ec33132e53609e5c92c7f4 11232 
ruby-moneta_0.7.20-2.1.debian.tar.xz
 77e37468ad655cfd2c8e1c3628e466d5411e264e896808c0b8486720f1d7364e 34074 
ruby-moneta_0.7.20-2.1_all.deb
Files:
 005ff73061aa70a3debb6b9b0bb8f027 2286 ruby extra ruby-moneta_0.7.20-2.1.dsc
 3abe0366b57c11a4a5d0d2ba383eb64e 11232 ruby extra 
ruby-moneta_0.7.20-2.1.debian.tar.xz
 dac218c7867d7f184caf6dcad7d6c622 34074 ruby extra 
ruby-moneta_0.7.20-2.1_all.deb

-BEGIN

Processed: user debian...@lists.debian.org, usertagging 769171, usertagging 769509, usertagging 769512 ...

[Debian Bug Tracking System]

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

> user debian...@lists.debian.org
Setting user to debian...@lists.debian.org (was a...@debian.org).
> usertags 769171 piuparts
There were no usertags set.
Usertags are now: piuparts.
> usertags 769509 piuparts
Usertags were: instest instest-20141113.
Usertags are now: piuparts instest instest-20141113.
> usertags 769512 piuparts
Usertags were: instest instest-20141113.
Usertags are now: piuparts instest instest-20141113.
> usertags 769513 piuparts
Usertags were: instest instest-20141113.
Usertags are now: piuparts instest instest-20141113.
> found 767842 1.1.1-2
Bug #767842 {Done: Antonio Terceiro } 
[ruby-actionpack-action-caching] ruby-actionpack-action-caching: fails to 
upgrade from 'wheezy' - trying to overwrite 
/usr/lib/ruby/vendor_ruby/action_controller/caching/actions.rb
Marked as found in versions ruby-actionpack-action-caching/1.1.1-2.
> found 769555 1.1.1-1
Bug #769555 {Done: Antonio Terceiro } 
[ruby-actionpack-action-caching] redmine: package fails to upgrade properly 
from wheezy
Marked as found in versions ruby-actionpack-action-caching/1.1.1-1.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
767842: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=767842
769513: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=769513
769555: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=769555
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#769998: gnome-session-flashback: fails to install: update-alternatives: error: alternative path /usr/lib/gnome-panel/gnome-session-flashback doesn't exist

[Andreas Beckmann]

Package: gnome-session-flashback
Version: 3.14.0-2
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

during a test with piuparts I noticed your package failed to install. As
per definition of the release team this makes the package too buggy for
a release, thus the severity.

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

  Selecting previously unselected package gnome-session-flashback.
  (Reading database ... 32445 files and directories currently installed.)
  Preparing to unpack .../gnome-session-flashback_3.14.0-2_all.deb ...
  Unpacking gnome-session-flashback (3.14.0-2) ...
  Setting up gnome-session-flashback (3.14.0-2) ...
  update-alternatives: error: alternative path 
/usr/lib/gnome-panel/gnome-session-flashback doesn't exist
  dpkg: error processing package gnome-session-flashback (--configure):
   subprocess installed post-installation script returned error exit status 2
  Errors were encountered while processing:
   gnome-session-flashback


You need to ship all directories where alternatives (or slave alternatives)
will be installed.


cheers,

Andreas


gnome-session-flashback_3.14.0-2.log.gz
Description: application/gzip

Bug#769693: Please giveback libjogl2-java

[tony mancill]

On 11/15/2014 03:20 PM, gregor herrmann wrote:
> Control: retitle -1 libjogl2-java: FTBFS on arm64
> 
> On Sat, 15 Nov 2014 18:44:05 +0100, gregor herrmann wrote:
> 
>> libjogl2-java failed to build on arm64, ppc64el, and s390x because of
>> a bug in gluegen2 (#769003) which should be fixed in 2.2.4-2.
> 
> https://buildd.debian.org/status/logs.php?pkg=libjogl2-java&ver=2.2.4%2Bdfsg-1
> 
> ppc64el and s390x built.
> 
> arm64 fails but AFAICS differently than before. My assumptions are
> that
> - gluegen2/#769003 is ok
> - libjogl2-java has a different problem on arm64
> 
> This probably needs some deeper Java knowledge ...

Hmmm...  I installed the build-deps into an arm64 sid chroot on asachi
(arm64 porterbox) to take a look, but it seems to build okay now.

> (sid_arm64-dchroot)tmancill@asachi:~/libjogl2-java/libjogl2-java-2.2.4+dfsg$ 
> debuild -us -uc -B
[...snip...]
> dh_builddeb -plibjogl2-jni 
> dpkg-deb: building package `libjogl2-jni' in 
> `../libjogl2-jni_2.2.4+dfsg-1_arm64.deb'.
>  dpkg-genchanges -B >../libjogl2-java_2.2.4+dfsg-1_arm64.changes
> dpkg-genchanges: binary-only arch-specific upload (source code and arch-indep 
> packages not included)
>  dpkg-source --after-build libjogl2-java-2.2.4+dfsg
> dpkg-buildpackage: binary-only upload (no source included)

Am I missing something, or can we try to run this through the buildd again?

Thanks,
tony



signature.asc
Description: OpenPGP digital signature

Bug#768710: biojava3-live: FTBFS in jessie: dh_install: libbiojava3-java-doc missing files (doc/biojava/*), aborting

[Andreas Tille]

Hi Gregor,

I'm in (semi)-Vac since the weekend and will go on VAC tomorrow.  Feel
free to NMU (or "team" upload).  It seems Olivier who is usually very
responsive has some time constraints.

Thanks for your help

   Andreas.

On Mon, Nov 17, 2014 at 09:12:30PM +0100, gregor herrmann wrote:
> Control: tag -1 + confirmed patch
> 
> On Sun, 09 Nov 2014 08:07:04 +0100, Lucas Nussbaum wrote:
> 
> > Source: biojava3-live
> > Version: 3.1.0+dfsg-1
> > Severity: serious
> > Tags: jessie sid
> > User: debian...@lists.debian.org
> > Usertags: qa-ftbfs-20141108 qa-ftbfs
> > Justification: FTBFS in jessie on amd64
> 
>  
> > > javadocs:
> 
> > >   [javadoc] 
> > > /«BUILDDIR»/biojava3-live-3.1.0+dfsg/biojavadoc/src/main/java/org/biojava3/ontology/utils/Annotatable.java:77:
> > >  error: unmappable character for encoding ASCII
> > >   [javadoc]  * @author  Kalle N???slund (docs)
> > >   [javadoc]^
> > >   [javadoc] 
> > > /«BUILDDIR»/biojava3-live-3.1.0+dfsg/biojavadoc/src/main/java/org/biojava3/ontology/utils/Annotatable.java:77:
> > >  error: unmappable character for encoding ASCII
> > >   [javadoc]  * @author  Kalle N???slund (docs)
> > >   [javadoc] ^
> > >   [javadoc] 
> > > /«BUILDDIR»/biojava3-live-3.1.0+dfsg/biojavadoc/src/main/java/org/biojava3/ontology/utils/Annotatable.java:77:
> > >  error: unmappable character for encoding ASCII
> > >   [javadoc]  * @author  Kalle N???slund (docs)
> > >   [javadoc]  ^
> 
> The package doesn't build in my sid chroot (because of some rdep
> glitch [0]) but I've tested the attached patch in a jessie chroot.
> 
> (There are other ways to tell javadoc about the file encodings but
> that was my first try and it works.)
> 
> 
> 
> Cheers,
> gregor
> 
> 
> [0]
> Errors were encountered while processing:
>  icedtea-netx:amd64
> E: Sub-process /usr/bin/dpkg returned an error code (1)
> Failed to perform requested operation on package.  Trying to recover:
> Setting up icedtea-netx:amd64 (1.5.1-1) ...
> update-alternatives: warning: forcing reinstallation of alternative 
> /usr/lib/jvm/java-7-openjdk-amd64/jre/bin/itweb-settings because link group 
> itweb-settings is broken
> update-alternatives: warning: not replacing 
> /usr/share/man/man1/itweb-settings.1.gz with a link
> update-alternatives: warning: forcing reinstallation of alternative 
> /usr/lib/jvm/java-7-openjdk-amd64/jre/bin/itweb-settings because link group 
> itweb-settings is broken
> update-alternatives: warning: not replacing 
> /usr/share/man/man1/itweb-settings.1.gz with a link
> update-alternatives: error: alternative path 
> /usr/lib/jvm/java-8-openjdk-amd64/jre/bin/javaws doesn't exist
> dpkg: error processing package icedtea-netx:amd64 (--configure):
>  subprocess installed post-installation script returned error exit status 2
> Errors were encountered while processing:
>  icedtea-netx:amd64
> 
> -- 
>  .''`.  Homepage: http://info.comodo.priv.at/ - OpenPGP key 0xBB3A68018649AA06
>  : :' : Debian GNU/Linux user, admin, and developer  -  http://www.debian.org/
>  `. `'  Member of VIBE!AT & SPI, fellow of the Free Software Foundation Europe
>`-   NP: The Beatles: Good Morning Good Morning

> Index: debian/build.xml
> ===
> --- debian/build.xml  (revision 18487)
> +++ debian/build.xml  (working copy)
> @@ -61,7 +61,7 @@
>   
>  
>   
> -  packagenames="org.*">
> +  packagenames="org.*" encoding="UTF-8">
>   http://java.sun.com/j2se/1.6.0/docs/api/"/>
>   
>   
> Index: debian/changelog
> ===
> --- debian/changelog  (revision 18487)
> +++ debian/changelog  (working copy)
> @@ -1,3 +1,14 @@
> +biojava3-live (3.1.0+dfsg-1.1) UNRELEASED; urgency=medium
> +
> +  * Non-maintainer upload.
> +  * Fix "FTBFS in jessie: dh_install: libbiojava3-java-doc missing files
> +(doc/biojava/*), aborting":
> +debian/build.xml: tell javadoc that source files are encoded as UTF-8;
> +otherwise it bails out, and dh_install finds nothing to install.
> +(Closes: #768710)
> +
> + -- gregor herrmann   Mon, 17 Nov 2014 20:36:16 +0100
> +
>  biojava3-live (3.1.0+dfsg-1) unstable; urgency=medium
>  
>* New upstream release 




> ___
> Debian-med-packaging mailing list
> debian-med-packag...@lists.alioth.debian.org
> http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/debian-med-packaging


-- 
http://fam-tille.de


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