Bug#815970: libtesseract4 and libtesseract3: error when trying to install together

[Ralf Treinen]

Package: libtesseract3,libtesseract4
Version: libtesseract3/3.4.1-3
Version: libtesseract4/3.4.1-2+b1
Severity: serious
User: trei...@debian.org
Usertags: edos-file-overwrite

Date: 2016-02-26
Architecture: amd64
Distribution: sid

Hi,

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


Selecting previously unselected package libjbig0:amd64.
(Reading database ... 10938 files and directories currently installed.)
Preparing to unpack .../libjbig0_2.1-3.1_amd64.deb ...
Unpacking libjbig0:amd64 (2.1-3.1) ...
Selecting previously unselected package gcc-5-base:amd64.
Preparing to unpack .../gcc-5-base_5.3.1-10_amd64.deb ...
Unpacking gcc-5-base:amd64 (5.3.1-10) ...
Setting up gcc-5-base:amd64 (5.3.1-10) ...
(Reading database ... 10950 files and directories currently installed.)
Preparing to unpack .../libstdc++6_5.3.1-10_amd64.deb ...
Unpacking libstdc++6:amd64 (5.3.1-10) over (4.8.2-19) ...
Processing triggers for libc-bin (2.21-9) ...
Setting up libstdc++6:amd64 (5.3.1-10) ...
Processing triggers for libc-bin (2.21-9) ...
Selecting previously unselected package libgif7:amd64.
(Reading database ... 10964 files and directories currently installed.)
Preparing to unpack .../libgif7_5.1.2-0.2_amd64.deb ...
Unpacking libgif7:amd64 (5.1.2-0.2) ...
Selecting previously unselected package libjpeg62-turbo:amd64.
Preparing to unpack .../libjpeg62-turbo_1%3a1.4.2-2_amd64.deb ...
Unpacking libjpeg62-turbo:amd64 (1:1.4.2-2) ...
Selecting previously unselected package libopenjp2-7:amd64.
Preparing to unpack .../libopenjp2-7_2.1.0-2.1_amd64.deb ...
Unpacking libopenjp2-7:amd64 (2.1.0-2.1) ...
Selecting previously unselected package libpng12-0:amd64.
Preparing to unpack .../libpng12-0_1.2.54-3_amd64.deb ...
Unpacking libpng12-0:amd64 (1.2.54-3) ...
Selecting previously unselected package libtiff5:amd64.
Preparing to unpack .../libtiff5_4.0.6-1_amd64.deb ...
Unpacking libtiff5:amd64 (4.0.6-1) ...
Selecting previously unselected package libwebp5:amd64.
Preparing to unpack .../libwebp5_0.4.4-1+b1_amd64.deb ...
Unpacking libwebp5:amd64 (0.4.4-1+b1) ...
Selecting previously unselected package liblept5.
Preparing to unpack .../liblept5_1.73-1+b1_amd64.deb ...
Unpacking liblept5 (1.73-1+b1) ...
Selecting previously unselected package libtesseract3.
Preparing to unpack .../libtesseract3_3.04.01-3_amd64.deb ...
Unpacking libtesseract3 (3.04.01-3) ...
Selecting previously unselected package libtesseract4.
Preparing to unpack .../libtesseract4_3.04.01-2+b1_amd64.deb ...
Unpacking libtesseract4 (3.04.01-2+b1) ...
dpkg: error processing archive 
/var/cache/apt/archives/libtesseract4_3.04.01-2+b1_amd64.deb (--unpack):
 trying to overwrite '/usr/share/tesseract-ocr/tessdata/pdf.ttf', which is also 
in package libtesseract3 3.04.01-3
dpkg-deb: error: subprocess paste was killed by signal (Broken pipe)
Processing triggers for libc-bin (2.21-9) ...
Errors were encountered while processing:
 /var/cache/apt/archives/libtesseract4_3.04.01-2+b1_amd64.deb
E: Sub-process /usr/bin/dpkg returned an error code (1)


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

Here is a list of files that are known to be shared by both packages
(according to the Contents file for sid/amd64, which may be
slightly out of sync):

  /usr/lib/libtesseract.so.3
  /usr/lib/libtesseract.so.3.0.4
  /usr/share/tesseract-ocr/tessdata/configs/ambigs.train
  /usr/share/tesseract-ocr/tessdata/configs/api_config
  /usr/share/tesseract-ocr/tessdata/configs/bigram
  /usr/share/tesseract-ocr/tessdata/configs/box.train
  /usr/share/tesseract-ocr/tessdata/configs/box.train.stderr
  /usr/share/tesseract-ocr/tessdata/configs/digits
  /usr/share/tesseract-ocr/tessdata/configs/hocr
  /usr/share/tesseract-ocr/tessdata/configs/inter
  /usr/share/tesseract-ocr/tessdata/configs/kannada
  /usr/share/tesseract-ocr/tessdata/configs/linebox
  /usr/share/tesseract-ocr/tessdata/configs/logfile
  /usr/share/tesseract-ocr/tessdata/configs/makebox
  /usr/share/tesseract-ocr/tessdata/configs/pdf
  /usr/share/tesseract-ocr/tessdata/configs/quiet
  /usr/share/tesseract-ocr/tessdata/configs/rebox
  /usr/share/tesseract-ocr/tessdata/configs/strokewidth
  /usr/share/tesseract-ocr/tessdata/configs/unlv
  /usr/share/tesseract-ocr/tessdata/pdf.ttf
  /usr/share/tesseract-ocr/tessdata/tessconfigs/batch
  

Bug#815960: python-openalpr: Missing python interpreter depends

[Scott Kitterman]

Package: python-openalpr
Version: 2.2.3-1
Severity: serious
Tags: patch
Justification: Policy 3.5

The python bindings require python to be installed to work, so they have to
depend on them.  Please see the attached patch for the standard pythonic way
to do this.

Scott K
diff -Nru openalpr-2.2.3/debian/changelog openalpr-2.2.3/debian/changelog
--- openalpr-2.2.3/debian/changelog	2016-01-24 17:27:18.0 -0500
+++ openalpr-2.2.3/debian/changelog	2016-02-25 23:25:49.0 -0500
@@ -1,3 +1,10 @@
+openalpr (2.2.3-1.1) UNRELEASED; urgency=medium
+
+  * Non-maintainer upload.
+  * Use dh-python to generate proper depends for python-openalpr
+
+ -- Scott Kitterman   Thu, 25 Feb 2016 23:25:02 -0500
+
 openalpr (2.2.3-1) unstable; urgency=low
 
   * Changed Debian config to build on all architectures (Closes: #812176)
diff -Nru openalpr-2.2.3/debian/control openalpr-2.2.3/debian/control
--- openalpr-2.2.3/debian/control	2016-01-24 15:34:14.0 -0500
+++ openalpr-2.2.3/debian/control	2016-02-25 23:28:28.0 -0500
@@ -4,7 +4,8 @@
 Maintainer: Matthew Hill 
 Build-Depends: debhelper (>= 9), git, cmake, quilt, 
  libtesseract-dev, libleptonica-dev, liblog4cplus-dev,
- libcurl3-dev, uuid-dev, libopencv-dev, default-jdk
+ libcurl3-dev, uuid-dev, libopencv-dev, default-jdk,
+ python, dh-python
 Standards-Version: 3.9.6
 Homepage: https://github.com/openalpr/openalpr
 Vcs-Browser: https://github.com/openalpr/openalpr
@@ -102,7 +103,7 @@
 Package: python-openalpr
 Section: python
 Architecture: any
-Depends: libopenalpr-dev (= ${binary:Version}), ${misc:Depends}
+Depends: libopenalpr-dev (= ${binary:Version}), ${python:Depends}, ${misc:Depends}
 Description: Python binding for OpenALPR library
  OpenALPR is an open source Automatic License Plate Recognition library written
  in C++. The library analyzes images and identifies license plates. The output
diff -Nru openalpr-2.2.3/debian/rules openalpr-2.2.3/debian/rules
--- openalpr-2.2.3/debian/rules	2016-01-24 15:34:14.0 -0500
+++ openalpr-2.2.3/debian/rules	2016-02-25 23:26:14.0 -0500
@@ -29,7 +29,7 @@
 
 # main packaging script based on dh7 syntax
 %:
-	dh $@ --sourcedirectory=src --with quilt
+	dh $@ --sourcedirectory=src --with quilt,python2
 
 override_dh_auto_configure:
 	dh_auto_configure -- \

Bug#815798: (no subject)

[James Montgomery]

tag 815798 + unreproducible
debootstrap stretch and installed gitlab successfully.

Processed (with 1 error): Re: Bug#815798: (no subject)

[Debian Bug Tracking System]

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

> tag 815798 + unreproducible
Bug #815798 [gitlab] (no subject)
Added tag(s) unreproducible.
> debootstrap stretch and installed gitlab successfully.
Unknown command or malformed arguments to command.
>
End of message, stopping processing here.

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

Processed: block 783490 with 815951

[Debian Bug Tracking System]

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

> block 783490 with 815951
Bug #783490 [isso] ReferenceError: exports is not defined (embed.dev.js line 
1306)
783490 was not blocked by any bugs.
783490 was not blocking any bugs.
Added blocking bug(s) of 783490: 815951
> thanks
Stopping processing here.

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

Bug#814826: marked as done (phpunit build-depends on php5-xdebug (not built anymore))

[Debian Bug Tracking System]

Your message dated Fri, 26 Feb 2016 03:19:29 +
with message-id 
and subject line Bug#814826: fixed in phpunit 5.2.9-2
has caused the Debian Bug report #814826,
regarding phpunit build-depends on php5-xdebug (not built anymore)
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.)


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

Package: src:phpunit
Version: 5.1.3-1
Severity: serious
Tags: sid stretch

phpunit build-depends on php5-xdebug (not built anymore), and the new php-xdebug 
doesn't provide php5-xdebug anymore.
--- End Message ---
--- Begin Message ---
Source: phpunit
Source-Version: 5.2.9-2

We believe that the bug you reported is fixed in the latest version of
phpunit, 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 814...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
David Prévot  (supplier of updated phpunit 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: Thu, 25 Feb 2016 22:48:57 -0400
Source: phpunit
Binary: phpunit
Architecture: source
Version: 5.2.9-2
Distribution: unstable
Urgency: medium
Maintainer: Debian PHP PEAR Maintainers 
Changed-By: David Prévot 
Description:
 phpunit- Unit testing suite for PHP5
Closes: 814826
Changes:
 phpunit (5.2.9-2) unstable; urgency=medium
 .
   * Team upload
   * Build-depend on php-debug instead of php5-xdebug (Closes: #814826)
Checksums-Sha1:
 12c1d3ecff5eaf0efc7cc8c56f07a04bcaddbbb4 2010 phpunit_5.2.9-2.dsc
 5dca5ecb36165f892b083e4f07b3386b81345753 11224 phpunit_5.2.9-2.debian.tar.xz
Checksums-Sha256:
 32ef63d07f9eab4982062b4e6707e0fbc64e6e26e3edf83df74714952a534cb9 2010 
phpunit_5.2.9-2.dsc
 5d54f5d0989b7f6cd1ab23b06d78e8389bdf9fe861616fac6528b94009b23c7d 11224 
phpunit_5.2.9-2.debian.tar.xz
Files:
 610bb12d2a7892ffae227b2891efcf7d 2010 php optional phpunit_5.2.9-2.dsc
 21cf15487b60c7d5ecf4aaf321801be5 11224 php optional 
phpunit_5.2.9-2.debian.tar.xz

-BEGIN PGP SIGNATURE-
Version: GnuPG v2

iQEcBAEBCAAGBQJWz7+lAAoJEAWMHPlE9r083I4IAJrWHhtDe5RSb+g0lkelBMFY
J/BevcxuCz5I3gt6UuYNag4ymeAbQjSwTaAfQS2QbfnPotvgB9Ym9wz0A2gmwq7M
SYpKa4T+50c7oiuwdRYIJBeIt7waipZ6xJbwsaGuq7lxprlKr8l+QjfdFBNQQBTI
po+6brHmZ108WICC/pP5uRSwg/CBucpkOtv+WVebX3uiI8XU6Akg+hH5/7A57OVN
mIC3hSJCyCkjbNU70iM323giaWuPQHBNvZ/2vIa+f8C7I0+twL/HO/rPCM9KnpsJ
lEpUwRgR58Z1KhHRpbRzgvVAe2BxcaptuO9LBbWBBxtyFHH3+/fHfHgvhFhOctw=
=KICy
-END PGP SIGNATURE End Message ---

Bug#737921: [TLS1.2] gnutls only likes SHA1 and SHA256 certificates

[Adam Bolte]

This issue also affects rsyslog. I hit this when I upgraded a bunch of
servers, including an rsyslog server from wheezy to jessie.

There are still a few wheezy servers that have yet to be upgraded, but
now they are unable to send their logs to the jessie rsyslog server
due to what appears to be this bug. Only the upgraded jessie servers
can send through their logs. Looks like I'll have to implement a
work-around.

Since this is obviously an issue with stable Debian releases, I too do
not believe this bug should be marked as closed.

Adam


signature.asc
Description: Digital signature

Bug#815945: sagan: FTBFS on *-i386: attempts to use 64-bit x86 assembly on 32-bit x86 arch

[Andreas Beckmann]

Source: sagan
Version: 1.0.1-0.1
Severity: serious
Justification: fails to build from source (but built successfully in the past)

Hi,

sagan FTBFS on i386 and kfreebsd-i386:

https://buildd.debian.org/status/fetch.php?pkg=sagan=kfreebsd-i386=1.0.1-0.1=1452795608
https://buildd.debian.org/status/fetch.php?pkg=sagan=i386=1.0.1-0.1=1452795303

[...]
gcc -DHAVE_CONFIG_H -I. -I..  -I.. -I/usr/include/json-c  -Wdate-time 
-D_FORTIFY_SOURCE=2  -g -O2 -fstack-protector-strong -Wformat 
-Werror=format-security -c -o sagan-strstr_sse2.o `test -f 
'parsers/sagan-strstr/strstr_sse2.S' || echo 
'./'`parsers/sagan-strstr/strstr_sse2.S
parsers/sagan-strstr/strstr_sse2.S: Assembler messages:
parsers/sagan-strstr/strstr_sse2.S:52: Error: bad register name `%rsi)'
[...]


Andreas

Bug#815768: Bumping severity

[Antonio Terceiro]

Hi,

ruby-defaults has just been uploaded to unstable, so this bug now
qualifies as a release critical bug.

-- 
Antonio Terceiro 


signature.asc
Description: PGP signature

Processed: severity of 815768 is serious, severity of 815773 is serious, severity of 815777 is serious

[Debian Bug Tracking System]

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

> severity 815768 serious
Bug #815768 [ruby-gsl] ruby-gsl: FTBFS against ruby2.3
Severity set to 'serious' from 'important'
> severity 815773 serious
Bug #815773 [ruby-zoom] ruby-zoom: FTBFS against ruby2.3
Severity set to 'serious' from 'important'
> severity 815777 serious
Bug #815777 [ruby-monkey-lib] ruby-monkey-lib: FTBFS against ruby2.3
Severity set to 'serious' from 'important'
> thanks
Stopping processing here.

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

Bug#815942: jzmq: FTBFS: missing header inclusion

[Laszlo Boszormenyi (GCS)]

Source: jzmq
Version: 3.1.0-8
Severity: serious
Tags: patch
Usertags: ftbfs
Justification: FTBFS and holds back zeromq3 transition

Hi Jan,

jzmq currently FTBFS and the zeromq3 transition is just part of it.
You need to update the build dependencies and change libzmq3-dev to
libzmq5-dev. The other is a missing include in src/main/c++/Event.cpp.
zmq.hpp needs to be included for the zmq_event_t struct definition.
The attached patch as an addition to the packaging fixes this issue.

Please add this patch for jzmq to keep the transition going.
Thanks,
Laszlo/GCSDescription: add missing header of zmq.hpp
 jzmq uses structs defined in zmq.hpp
Author: Laszlo Boszormenyi (GCS) 
Last-Update: 2016-02-25

---

--- jzmq-3.1.0.orig/src/main/c++/Event.cpp
+++ jzmq-3.1.0/src/main/c++/Event.cpp
@@ -2,6 +2,7 @@
 #include 
 #include 
 #include 
+#include 
 
 #include "jzmq.hpp"
 #include "util.hpp"

Bug#815651: marked as done (maven-invoker fails to build in unstable)

[Debian Bug Tracking System]

Your message dated Thu, 25 Feb 2016 22:43:24 +
with message-id 
and subject line Bug#815651: fixed in maven-invoker 2.2-2
has caused the Debian Bug report #815651,
regarding maven-invoker fails to build in unstable
to be marked as done.

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

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


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

Package: src:maven-invoker
Version: 2.2-1
Severity: serious
Tags: sid stretch

   dh_auto_build -O--buildsystem=maven
/usr/lib/jvm/default-java/bin/java -noverify -cp 
/usr/share/maven/boot/plexus-classworlds-2.x.jar:/usr/lib/jvm/default-java/lib/tools.jar 
-Dmaven.home=/usr/share/maven 
-Dmaven.multiModuleProjectDirectory=/home/packages/tmp/j/maven-invoker-2.2 
-Dclassworlds.conf=/etc/maven/m2-debian.conf 
org.codehaus.plexus.classworlds.launcher.Launcher 
-s/etc/maven/settings-debian.xml 
-Ddebian.dir=/home/packages/tmp/j/maven-invoker-2.2/debian 
-Dmaven.repo.local=/home/packages/tmp/j/maven-invoker-2.2/debian/maven-repo 
package -DskipTests -Dnotimestamp=true -Dlocale=en_US

[INFO] Scanning for projects...
[INFO]
[INFO] 
[INFO] Building Apache Maven Invoker 2.2
[INFO] 
[WARNING] The POM for org.codehaus.plexus:plexus-component-metadata:jar:1.6 is 
missing, no dependency information available

[INFO] 
[INFO] BUILD FAILURE
[INFO] 
[INFO] Total time: 0.152 s
[INFO] Finished at: 2016-02-23T10:38:38+00:00
[INFO] Final Memory: 7M/240M
[INFO] 
[ERROR] Plugin org.codehaus.plexus:plexus-component-metadata:1.6 or one of its 
dependencies could not be resolved: Cannot access central 
(https://repo.maven.apache.org/maven2) in offline mode and the artifact 
org.codehaus.plexus:plexus-component-metadata:jar:1.6 has not been downloaded 
from it before. -> [Help 1]

[ERROR]
[ERROR] To see the full stack trace of the errors, re-run Maven with the -e 
switch.
[ERROR] Re-run Maven using the -X switch to enable full debug logging.
[ERROR]
[ERROR] For more information about the errors and possible solutions, please 
read the following articles:
[ERROR] [Help 1] 
http://cwiki.apache.org/confluence/display/MAVEN/PluginResolutionException
dh_auto_build: /usr/lib/jvm/default-java/bin/java -noverify -cp 
/usr/share/maven/boot/plexus-classworlds-2.x.jar:/usr/lib/jvm/default-java/lib/tools.jar 
-Dmaven.home=/usr/share/maven 
-Dmaven.multiModuleProjectDirectory=/home/packages/tmp/j/maven-invoker-2.2 
-Dclassworlds.conf=/etc/maven/m2-debian.conf 
org.codehaus.plexus.classworlds.launcher.Launcher 
-s/etc/maven/settings-debian.xml 
-Ddebian.dir=/home/packages/tmp/j/maven-invoker-2.2/debian 
-Dmaven.repo.local=/home/packages/tmp/j/maven-invoker-2.2/debian/maven-repo 
package -DskipTests -Dnotimestamp=true -Dlocale=en_US returned exit code 1

debian/rules:6: recipe for target 'build' failed
make: *** [build] Error 2
--- End Message ---
--- Begin Message ---
Source: maven-invoker
Source-Version: 2.2-2

We believe that the bug you reported is fixed in the latest version of
maven-invoker, 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 815...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Emmanuel Bourg  (supplier of updated maven-invoker 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: Thu, 25 Feb 2016 23:00:38 +0100
Source: maven-invoker
Binary: libmaven-invoker-java
Architecture: source all
Version: 2.2-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Java Maintainers 

Changed-By: Emmanuel Bourg 
Description:
 libmaven-invoker-java - Maven Invoker
Closes: 815651
Changes:
 maven-invoker (2.2-2) unstable; urgency=medium
 .
   * Team upload.
   * Fixed the 

Bug#814877: marked as done (maven-dependency-analyzer: FTBFS: Plugin org.codehaus.plexus:plexus-component-metadata:1.6 or one of its dependencies could not be resolved)

[Debian Bug Tracking System]

Your message dated Thu, 25 Feb 2016 22:43:18 +
with message-id 
and subject line Bug#814877: fixed in maven-dependency-analyzer 1.6-2
has caused the Debian Bug report #814877,
regarding maven-dependency-analyzer: FTBFS: Plugin 
org.codehaus.plexus:plexus-component-metadata:1.6 or one of its dependencies 
could not be resolved
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.)


-- 
814877: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=814877
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: maven-dependency-analyzer
Version: 1.6-1
Severity: serious
Justification: fails to build from source
User: reproducible-bui...@lists.alioth.debian.org
Usertags: ftbfs
X-Debbugs-Cc: reproducible-bui...@lists.alioth.debian.org

Dear Maintainer,

maven-dependency-analyzer fails to build from source in unstable/amd64:

  [..]

   dpkg-buildpackage -rfakeroot -D -us -uc -b
  dpkg-buildpackage: source package maven-dependency-analyzer
  dpkg-buildpackage: source version 1.6-1
  dpkg-buildpackage: source distribution unstable
  dpkg-buildpackage: source changed by Emmanuel Bourg 
   dpkg-source --before-build maven-dependency-analyzer-1.6
  dpkg-buildpackage: host architecture amd64
   fakeroot debian/rules clean
  dh clean --buildsystem=maven
 dh_testdir -O--buildsystem=maven
 dh_auto_clean -O--buildsystem=maven
"for dir in \$(find . -name target -type d); do if [ -f \$(echo \$dir | 
sed -e s/target\$/pom.xml/) ]; then rm -Rf \$dir; fi done"
mh_unpatchpoms -plibmaven-dependency-analyzer-java
 dh_clean -O--buildsystem=maven
   debian/rules build
  dh build --buildsystem=maven
 dh_testdir -O--buildsystem=maven
 dh_update_autotools_config -O--buildsystem=maven
 dh_auto_configure -O--buildsystem=maven
  find: '/usr/share/maven-repo/org/codehaus/plexus/plexus-compiler/*/*.jar': No 
such file or directory
  find: '/usr/share/maven-repo/org/codehaus/plexus/plexus-compilers/*/*.jar': 
No such file or directory
  find: '/usr/share/maven-repo/org/codehaus/plexus/plexus-containers/*/*.jar': 
No such file or directory
mh_patchpoms -plibmaven-dependency-analyzer-java --debian-build 
--keep-pom-version 
--maven-repo=/home/lamby/temp/cdt.20160216090545.Ah1c25OwiU/maven-dependency-analyzer-1.6/debian/maven-repo
 dh_auto_build -O--buildsystem=maven
/usr/lib/jvm/default-java/bin/java -noverify -cp 
/usr/share/maven/boot/plexus-classworlds-2.x.jar:/usr/lib/jvm/default-java/lib/tools.jar
 -Dmaven.home=/usr/share/maven 
-Dmaven.multiModuleProjectDirectory=/home/lamby/temp/cdt.20160216090545.Ah1c25OwiU/maven-dependency-analyzer-1.6
 -Dclassworlds.conf=/etc/maven/m2-debian.conf 
-Dproperties.file.manual=/home/lamby/temp/cdt.20160216090545.Ah1c25OwiU/maven-dependency-analyzer-1.6/debian/maven.properties
 org.codehaus.plexus.classworlds.launcher.Launcher 
-s/etc/maven/settings-debian.xml 
-Ddebian.dir=/home/lamby/temp/cdt.20160216090545.Ah1c25OwiU/maven-dependency-analyzer-1.6/debian
 
-Dmaven.repo.local=/home/lamby/temp/cdt.20160216090545.Ah1c25OwiU/maven-dependency-analyzer-1.6/debian/maven-repo
 package -DskipTests -Dnotimestamp=true -Dlocale=en_US
  [INFO] Scanning for projects...
  [INFO]
 
  [INFO] 

  [INFO] Building Apache Maven Dependency Analyzer 1.6
  [INFO] 

  [WARNING] The POM for org.codehaus.plexus:plexus-component-metadata:jar:1.6 
is missing, no dependency information available
  [INFO] 

  [INFO] BUILD FAILURE
  [INFO] 

  [INFO] Total time: 0.103 s
  [INFO] Finished at: 2016-02-16T09:07:30+01:00
  [INFO] Final Memory: 8M/300M
  [INFO] 

  [ERROR] Plugin org.codehaus.plexus:plexus-component-metadata:1.6 or one of 
its dependencies could not be resolved: Cannot access central 
(https://repo.maven.apache.org/maven2) in offline mode and the artifact 
org.codehaus.plexus:plexus-component-metadata:jar:1.6 has not been downloaded 
from it before. -> [Help 1]
  [ERROR] 
  [ERROR] To see the full stack trace of the errors, re-run Maven with the -e 
switch.
  [ERROR] Re-run Maven using the -X switch to enable full debug logging.
  [ERROR] 
  [ERROR] For more information about 

Bug#815935: phoronix-test-suite: FTBFS with nonexistent $HOME

[Andreas Beckmann]

Source: phoronix-test-suite
Version: 3.8.0-1
Severity: serious
Tags: wheezy
Justification: fails to build from source

Hi,

phoronix-test-suite/wheezy FTBFS if $HOME does not exist (which is the
new behavior of pbuilder in sid/stretch).


I: Running cd /build/*/ && env PATH="/usr/sbin:/usr/bin:/sbin:/bin" 
HOME="/nonexistent" dpkg-buildpackage -us -uc -rfakeroot
dpkg-buildpackage: source package phoronix-test-suite
dpkg-buildpackage: source version 3.8.0-1
dpkg-buildpackage: source changed by Alessio Treglia 
 dpkg-source --before-build phoronix-test-suite-3.8.0
dpkg-buildpackage: host architecture amd64
 fakeroot debian/rules clean
dh clean
   dh_testdir
   dh_auto_clean
   dh_clean
 dpkg-source -b phoronix-test-suite-3.8.0
dpkg-source: info: using source format `3.0 (quilt)'
dpkg-source: info: building phoronix-test-suite using existing 
./phoronix-test-suite_3.8.0.orig.tar.gz
dpkg-source: info: building phoronix-test-suite in 
phoronix-test-suite_3.8.0-1.debian.tar.gz
dpkg-source: info: building phoronix-test-suite in 
phoronix-test-suite_3.8.0-1.dsc
 debian/rules build
dh build
   dh_testdir
   dh_auto_configure
   debian/rules override_dh_auto_build
make[1]: Entering directory `/build/phoronix-test-suite-3.8.0'
./phoronix-test-suite dump-documentation

[NOTICE] mkdir(): No such file or directory in pts_file_io.php:28

[NOTICE] DOMDocument::save(/nonexistent/.phoronix-test-suite/user-config.xml): 
failed to open stream: No such file or directory in nye_XmlWriter.php:100

[NOTICE] 
file_put_contents(/nonexistent/.phoronix-test-suite/graph-config.json): failed 
to open stream: No such file or directory in pts_config.php:74

NOTICE: No Network Connectivity


NOTICE: The following PHP extensions are OPTIONAL but recommended:

GD   The PHP GD library is recommended for improved graph rendering.
CURL PHP CURL is recommended for an enhanced download experience.


[NOTICE] file_put_contents(/nonexistent/.phoronix-test-suite/temp.pt2so): 
failed to open stream: No such file or directory in pts_storage_object.php:61

[...]

[NOTICE] 
copy(/nonexistent/.phoronix-test-suite/xsl/pts-user-config-viewer.xsl): failed 
to open stream: No such file or directory in pts_client.php:497

[NOTICE] copy(/nonexistent/.phoronix-test-suite/xsl/pts-logo.png): failed to 
open stream: No such file or directory in pts_client.php:498

WARNING: It appears that the Phoronix Test Suite is already running.
 For proper results, only run one instance at a time.


[NOTICE] disk_total_space(): No such file or directory in phodevi_disk.php:258
PHP Fatal error:  Call to a member function read_object() on a non-object in 
/build/phoronix-test-suite-3.8.0/pts-core/objects/client/pts_client.php on line 
1305
make[1]: Leaving directory `/build/phoronix-test-suite-3.8.0'
   dh_auto_test
 fakeroot debian/rules binary
dh binary
   dh_testroot
   dh_prep
   dh_installdirs
   debian/rules override_dh_install
make[1]: Entering directory `/build/phoronix-test-suite-3.8.0'
cp pts-core/static/bash_completion \

/build/phoronix-test-suite-3.8.0/debian/phoronix-test-suite/etc/bash_completion.d/phoronix-test-suite
cp pts-core/static/images/phoronix-test-suite.png \

/build/phoronix-test-suite-3.8.0/debian/phoronix-test-suite/usr/share/icons/hicolor/48x48/apps/phoronix-test-suite.png
cp pts-core/static/images/openbenchmarking.png \

/build/phoronix-test-suite-3.8.0/debian/phoronix-test-suite/usr/share/icons/hicolor/64x64/apps/openbenchmarking.png
cp pts-core/static/phoronix-test-suite.desktop \

/build/phoronix-test-suite-3.8.0/debian/phoronix-test-suite/usr/share/applications/
rm -f 
/build/phoronix-test-suite-3.8.0/debian/phoronix-test-suite/usr/share/phoronix-test-suite/pts/etc/scripts/package-build-*
cp -r pts-core/ 
/build/phoronix-test-suite-3.8.0/debian/phoronix-test-suite/usr/share/phoronix-test-suite/
rm -f 
ESTDIRNSTALL_PREFIX/share/phoronix-test-suite/pts-core/static/phoronix-test-suite.desktop
sed 's:PTS_DIR=`pwd`:PTS_DIR='/usr\/share\/phoronix-test-suite':g' 
phoronix-test-suite \
> 
/build/phoronix-test-suite-3.8.0/debian/phoronix-test-suite/usr/bin/phoronix-test-suite
make[1]: Leaving directory `/build/phoronix-test-suite-3.8.0'
   dh_installdocs
cp: cannot stat `documentation/phoronix-test-suite.pdf': No such file or 
directory
dh_installdocs: cp -a documentation/phoronix-test-suite.pdf 
debian/phoronix-test-suite/usr/share/doc/phoronix-test-suite returned exit code 
1
make: *** [binary] Error 2

Bug#814446: tomcat8: wants to overwrite admin configuration on upgrade

[Emmanuel Bourg]

Control: severity -1 important

I'm downgrading the severity to important for the following reasons:
- this issue has been there for years in the previous tomcat packages
- the actual policy violation seems to be debatable
- the RC bug prevents the latest version containing security fixes from
reaching testing and then jessie-backports

Processed: Re: Bug#814446: tomcat8: wants to overwrite admin configuration on upgrade

[Debian Bug Tracking System]

Processing control commands:

> severity -1 important
Bug #814446 [tomcat8] tomcat8: wants to overwrite admin configuration on upgrade
Severity set to 'important' from 'serious'

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

Bug#804695: marked as done (kodi: Please switch to fonts-noto from fonts-droid)

[Debian Bug Tracking System]

Your message dated Thu, 25 Feb 2016 21:54:20 +
with message-id 
and subject line Bug#804695: fixed in kodi 16.0+dfsg1-1
has caused the Debian Bug report #804695,
regarding kodi: Please switch to fonts-noto from fonts-droid
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.)


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

Source: kodi
Severity: normal
User: pkg-fonts-de...@lists.alioth.debian.org
Usertags: droid-migration

Dear Maintainer,

Since Android upstream stopped shipping Droid fonts and its been
declared that Noto fonts will be superseding the Droid¹² we in
"Debian Fonts Task Force" team decided to drop fonts-droid package.

One of your package kodi either Build-Depends on fonts-droid. I kindly
request you to do the switch to fonts-noto instead.

If you are using Fallback variants of Droid fonts, I would like note
that these fonts will still be shipped as part of new
fonts-droid-fallback package.

¹ https://github.com/googlei18n/noto-fonts/issues/555
² 
http://lists.alioth.debian.org/pipermail/pkg-fonts-devel/attachments/20151031/011f4334/attachment.mht

Best Regards, 
--- End Message ---
--- Begin Message ---
Source: kodi
Source-Version: 16.0+dfsg1-1

We believe that the bug you reported is fixed in the latest version of
kodi, 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 804...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Balint Reczey  (supplier of updated kodi 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, 22 Feb 2016 23:08:18 +0100
Source: kodi
Binary: kodi kodi-data kodi-bin kodi-eventclients-common kodi-eventclients-dev 
kodi-eventclients-wiiremote kodi-eventclients-j2me kodi-eventclients-ps3 
kodi-eventclients-kodi-send kodi-addons-dev
Architecture: source
Version: 16.0+dfsg1-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Multimedia Maintainers 

Changed-By: Balint Reczey 
Description:
 kodi   - Open Source Home Theatre (executable binaries)
 kodi-addons-dev - Open Source Home Theatre (Addons Dev package)
 kodi-bin   - Open Source Home Theatre (architecture-dependent files)
 kodi-data  - Open Source Home Theatre (arch-independent data package)
 kodi-eventclients-common - Open Source Home Theatre (Event Client Common 
package)
 kodi-eventclients-dev - Open Source Home Theatre (Event Client Dev package)
 kodi-eventclients-j2me - Open Source Home Theatre (Event Client J2ME package)
 kodi-eventclients-kodi-send - Open Source Home Theatre (Event Client Kodi-SEND 
package)
 kodi-eventclients-ps3 - Open Source Home Theatre (Event Client PS3 package)
 kodi-eventclients-wiiremote - Open Source Home Theatre (Event Client WII 
Remote support package
Closes: 777041 792299 803831 804695 810186
Changes:
 kodi (16.0+dfsg1-1) unstable; urgency=medium
 .
   * New upstream version 16.0
 See https://kodi.tv/kodi-16-0-jarvis-mark-xvi/
   * Refresh patches
   * Change build-dependency on libcec-platform-dev to libp8-platform-dev.
 The library has been renamed
   * Build-depend on libcec-dev (>= 3.1) which is built with p8-platform
   * Stop shipping menu file
   * Override false positive lintian warning about missing JavaScript source
 .
 kodi (16.0~rc3+dfsg2-1) experimental; urgency=medium
 .
   * New upstream release candidate 16.0 RC3
 (Closes: #792299) (CVE-2015-3885)
 See http://kodi.tv/kodi-16-0-jarvis-release-candidate-3/
   * Refresh patches
   * Don't use libcadec, wait for the codec to be included in FFmpeg instead
   * Drop libhdhomerun-dev build dependency
   * Add libcrossguid-dev and uuid-dev as build-dependencies
   * Drop workarounds for screensavers dropped by upstream
   * Use hinted Roboto fonts adapting to their new location in filesystem
   * Enable PIE
   * Make C-Pluff build with PIC only enabling PIE-enabled build to succeed
   * Update debian/copyright for 16.0 RC3 changes
 .
 kodi (15.2+dfsg1-3) unstable; urgency=medium
 .
   * 

Bug#815824: marked as done (gerris: build_function uses wrong compiler)

[Debian Bug Tracking System]

Your message dated Thu, 25 Feb 2016 21:23:52 +
with message-id 
and subject line Bug#815824: fixed in gerris 20131206+dfsg-7
has caused the Debian Bug report #815824,
regarding gerris: build_function uses wrong compiler
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.)


-- 
815824: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=815824
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: gerris
Version: 20131206+dfsg-5
Severity: grave
Tags: patch
Justification: renders package unusable

Dear Maintainer,

Gerris uses compilation in the background to evaluate user-defined functions in
parameter files. This is done through the /usr/share/gerris/build_function
script. Currently, the "serial" gerris package includes a build_function script
which uses 'mpicc' to compile, but mpicc is not a dependency of the package
(because the gerris executable itself is serial, not parallel). This causes all
user-defined functions to fail and thus very seriously limits the usability of
the package.

To reproduce the bug you can do

% wget
http://gerris.dalembert.upmc.fr/gerris/examples/examples/boussinesq/boussinesq.gfs
% gerris2D boussinesq.gfs

which will give

gerris: file `boussinesq.gfs' is not a valid simulation file
boussinesq.gfs:61:74: error compiling expression
/usr/share/gerris/build_function: 28: /usr/share/gerris/build_function: mpicc:
not found

The fix is simple, just replace 'mpicc' with 'gcc' on lines 7 and 8 of
/usr/share/gerris/build_function.

thanks for packaging Gerris!

Stephane



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

Kernel: Linux 3.16.0-4-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_US.utf8, LC_CTYPE=en_US.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages gerris depends on:
ii  libav-tools   6:11.4-1~deb8u1
ii  libc6 2.19-18+deb8u3
ii  libgcc1   1:4.9.2-10
ii  libgfortran3  4.9.2-10
ii  libgfs-1.3-2  20131206+dfsg-5
ii  libgfs-dev20131206+dfsg-5
ii  libglib2.0-0  2.42.1-1
ii  libgts-0.7-5  0.7.6+darcs121130-1.2
ii  libgts-dev0.7.6+darcs121130-1.2
ii  libquadmath0  4.9.2-10

Versions of packages gerris recommends:
ii  gfsview  20121130+dfsg-1

Versions of packages gerris suggests:
ii  python  2.7.9-1

-- no debconf information
--- End Message ---
--- Begin Message ---
Source: gerris
Source-Version: 20131206+dfsg-7

We believe that the bug you reported is fixed in the latest version of
gerris, 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 815...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Anton Gladky  (supplier of updated gerris 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: Thu, 25 Feb 2016 21:10:50 +0100
Source: gerris
Binary: gerris gerris-mpi libgfs-1.3-2 libgfs-dbg libgfs-dev libgfs-mpi-1.3-2 
libgfs-mpi-dev
Architecture: source
Version: 20131206+dfsg-7
Distribution: unstable
Urgency: medium
Maintainer: Debian Science Maintainers 

Changed-By: Anton Gladky 
Description:
 gerris - Fluid Flow Solver
 gerris-mpi - Fluid Flow Solver
 libgfs-1.3-2 - Fluid Flow Solver -- shared libraries
 libgfs-dbg - Fluid Flow Solver -- libraries with debugging symbols
 libgfs-dev - Fluid Flow Solver -- development libraries and headers
 libgfs-mpi-1.3-2 - Fluid Flow Solver -- shared libraries
 libgfs-mpi-dev - Fluid Flow Solver -- development libraries and headers
Closes: 815824
Changes:
 gerris (20131206+dfsg-7) unstable; urgency=medium
 .
   * [43c738d] Fix compiler in build_function. (Closes: #815824)
Checksums-Sha1:
 27548fbd1a09c2e44a123a6f3d6c647cbb3898c0 2555 gerris_20131206+dfsg-7.dsc
 41b36cfaa2f9e9f6d6a87940b2ae3a84fa2ec099 17092 
gerris_20131206+dfsg-7.debian.tar.xz
Checksums-Sha256:
 afc9f135abc498dae68ee75b8006438eb4499b0379a3117abdb5971f7d1c 2555 
gerris_20131206+dfsg-7.dsc
 1ff41bb8d0913294a7b8cce626343db1e5f591e12b9286e43d2fc1acbb57b3a7 17092 

Bug#813982: marked as done (python-mne: FTBFS: IndexError: an index can only have a single ellipsis ('...'))

[Debian Bug Tracking System]

Your message dated Thu, 25 Feb 2016 16:13:12 -0500
with message-id <20160225211312.ga7...@onerussian.com>
and subject line Re: Fwd: [Debian-med-packaging] python-mne is marked for 
autoremoval from testing
has caused the Debian Bug report #813982,
regarding python-mne: FTBFS: IndexError: an index can only have a single 
ellipsis ('...')
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.)


-- 
813982: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=813982
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: python-mne
Version: 0.10.1+dfsg-1
Severity: serious
Justification: fails to build from source
User: reproducible-bui...@lists.alioth.debian.org
Usertags: ftbfs
X-Debbugs-Cc: reproducible-bui...@lists.alioth.debian.org

Dear Maintainer,

python-mne fails to build from source in unstable/amd64:

  [..]

  ==
  ERROR: Test PSD estimation on epochs
  --
  Traceback (most recent call last):
File "/usr/lib/python2.7/dist-packages/nose/case.py", line 197, in runTest
  self.test(*self.arg)
File "/usr/lib/python2.7/dist-packages/numpy/testing/decorators.py", line 
147, in skipper_func
  return f(*args, **kwargs)
File 
"/home/lamby/temp/cdt.20160207103006.4o4ykTzhLo/python-mne-0.10.1+dfsg/mne/time_frequency/tests/test_psd.py",
 line 95, in test_psd_epochs
  n_fft=n_fft, picks=picks)
File "", line 2, in compute_epochs_psd
File 
"/home/lamby/temp/cdt.20160207103006.4o4ykTzhLo/python-mne-0.10.1+dfsg/mne/utils.py",
 line 551, in verbose
  return function(*args, **kwargs)
File 
"/home/lamby/temp/cdt.20160207103006.4o4ykTzhLo/python-mne-0.10.1+dfsg/mne/time_frequency/psd.py",
 line 171, in compute_epochs_psd
  data = epochs.get_data()[:, picks][..., time_mask]
  IndexError: an index can only have a single ellipsis ('...')
   >> begin captured stdout << -
  Opening raw data file 
/home/lamby/temp/cdt.20160207103006.4o4ykTzhLo/python-mne-0.10.1+dfsg/mne/io/tests/data/test_raw.fif...
  Read a total of 3 projection items:
  PCA-v1 (1 x 102)  idle
  PCA-v2 (1 x 102)  idle
  PCA-v3 (1 x 102)  idle
  Current compensation grade : 0
  Range : 25800 ... 40199 = 42.956 ...66.930 secs
  Ready.
  Adding average EEG reference projection.
  1 projection items deactivated
  2 matching events found
  Reading 2671 ... 3271  =  4.447 ... 5.446 secs...
  [done]
  Applying baseline correction ... (mode: mean)
  Reading 4350 ... 4950  =  7.243 ... 8.242 secs...
  [done]
  Applying baseline correction ... (mode: mean)
  0 bad epochs dropped
  2 matching events found
  Reading 2370 ... 3572  =  3.946 ... 5.947 secs...
  [done]
  Applying baseline correction ... (mode: mean)
  Reading 4049 ... 5251  =  6.741 ... 8.743 secs...
  [done]
  Applying baseline correction ... (mode: mean)
  0 bad epochs dropped
  
  - >> end captured stdout << --
  
  ==
  ERROR: Test plotting epochs psd (+topomap)
  --
  Traceback (most recent call last):
File "/usr/lib/python2.7/dist-packages/nose/case.py", line 197, in runTest
  self.test(*self.arg)
File "/usr/lib/python2.7/dist-packages/numpy/testing/decorators.py", line 
147, in skipper_func
  return f(*args, **kwargs)
File 
"/home/lamby/temp/cdt.20160207103006.4o4ykTzhLo/python-mne-0.10.1+dfsg/mne/viz/tests/test_epochs.py",
 line 164, in test_plot_psd_epochs
  epochs.plot_psd()
File 
"/home/lamby/temp/cdt.20160207103006.4o4ykTzhLo/python-mne-0.10.1+dfsg/mne/epochs.py",
 line 868, in plot_psd
  verbose=None, show=show)
File "", line 2, in plot_epochs_psd
File 
"/home/lamby/temp/cdt.20160207103006.4o4ykTzhLo/python-mne-0.10.1+dfsg/mne/utils.py",
 line 551, in verbose
  return function(*args, **kwargs)
File 
"/home/lamby/temp/cdt.20160207103006.4o4ykTzhLo/python-mne-0.10.1+dfsg/mne/viz/epochs.py",
 line 495, in plot_epochs_psd
  n_jobs=n_jobs)
File "", line 2, in compute_epochs_psd
File 
"/home/lamby/temp/cdt.20160207103006.4o4ykTzhLo/python-mne-0.10.1+dfsg/mne/utils.py",
 line 551, in verbose
  return function(*args, **kwargs)
File 
"/home/lamby/temp/cdt.20160207103006.4o4ykTzhLo/python-mne-0.10.1+dfsg/mne/time_frequency/psd.py",
 line 171, in compute_epochs_psd
  

Bug#815765: #815765: remctl: FTBFS against ruby2.3

[Russ Allbery]

Christian Hofstaedtler  writes:

> During a follow-up rebuild of remctl in an unmodified sid chroot
> using sbuild, your package FTBFS in the very same way - phpize not
> finding libtool.

> Therefore I'm raising the bug's severity as it's likely the package
> will FTBFS for anyone building it.

Thanks for the report!  I won't get a chance to get to this until this
weekend, but I'll definitely take a look and try to get it fixed then.

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

Bug#815917: phpmyadmin crashes silently

[Guy Durrieu]

Le 25/02/2016 20:21, Guy Durrieu a écrit :


OK, I should have a look to that:

error.log:[Thu Feb 25 17:39:42.283655 2016] [:error] [pid 16091] 
[client ::1:55330] PHP Fatal error:  require_once(): Failed opening 
required './libraries/php-gettext/gettext.inc' (include_path='.') in 
/usr/share/phpmyadmin/libraries/sql-parser/autoload.php on line 70, 
referer: http://localhost/phpmyadmin/import.php




In my config the required file is located here: 
/usr/share/php/php-gettext/gettext.inc


-- Regards.

-- GD.

Processed: your mail

[Debian Bug Tracking System]

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

> tags 815633 pending
Bug #815633 [ilmbase] ilmbase: symbols file update for kfreebsd
Added tag(s) pending.
> tags 788102 pending
Bug #788102 [src:ilmbase] ilmbase: FPU functions unimplemented on kfreebsd/hurd
Added tag(s) pending.
> tags 815712 pending
Bug #815712 [src:ilmbase] ilmbase: FTBFS on many 32-bit arches: 
testBoxAlgo.cpp:892
Added tag(s) pending.
>
End of message, stopping processing here.

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

Bug#815869: marked as done (osmium-tool: FTBFS: protobuf_tags.hpp:36:35: fatal error: protozero/pbf_types.hpp: No such file or directory)

[Debian Bug Tracking System]

Your message dated Thu, 25 Feb 2016 20:53:31 +0100
with message-id <56cf5bbb.8020...@xs4all.nl>
and subject line Re: Bug#815869: Header renamed in protozero 1.3.0
has caused the Debian Bug report #815869,
regarding osmium-tool: FTBFS: protobuf_tags.hpp:36:35: fatal error: 
protozero/pbf_types.hpp: No such file or directory
to be marked as done.

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

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


-- 
815869: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=815869
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: osmium-tool
Version: 1.3.0-1
Severity: serious
Justification: fails to build from source
User: reproducible-bui...@lists.alioth.debian.org
Usertags: ftbfs
X-Debbugs-Cc: reproducible-bui...@lists.alioth.debian.org

Dear Maintainer,

osmium-tool fails to build from source in unstable/amd64:

  [..]

  [ 46%] Building CXX object src/CMakeFiles/osmium.dir/command_check_refs.cpp.o
  cd 
/home/lamby/temp/cdt.20160225074829.SvnyKmT6F8/osmium-tool-1.3.0/obj-x86_64-linux-gnu/src
 && /usr/bin/c++   -DOSMIUM_VERSION=\"1.3.0\" -D_FILE_OFFSET_BITS=64 
-D_LARGEFILE_SOURCE 
-I/home/lamby/temp/cdt.20160225074829.SvnyKmT6F8/osmium-tool-1.3.0/include 
-I/home/lamby/temp/cdt.20160225074829.SvnyKmT6F8/osmium-tool-1.3.0/obj-x86_64-linux-gnu/src
  -g -O2 -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time 
-D_FORTIFY_SOURCE=2-std=c++11 -o 
CMakeFiles/osmium.dir/command_check_refs.cpp.o -c 
/home/lamby/temp/cdt.20160225074829.SvnyKmT6F8/osmium-tool-1.3.0/src/command_check_refs.cpp
  In file included from /usr/include/osmium/io/detail/pbf_decoder.hpp:51:0,
   from /usr/include/osmium/io/detail/pbf_input_format.hpp:51,
   from /usr/include/osmium/io/pbf_input.hpp:46,
   from /usr/include/osmium/io/any_input.hpp:48,
   from 
/home/lamby/temp/cdt.20160225074829.SvnyKmT6F8/osmium-tool-1.3.0/src/command_cat.cpp:28:
  /usr/include/osmium/io/detail/protobuf_tags.hpp:36:35: fatal error: 
protozero/pbf_types.hpp: No such file or directory
  compilation terminated.
  src/CMakeFiles/osmium.dir/build.make:65: recipe for target 
'src/CMakeFiles/osmium.dir/command_cat.cpp.o' failed
  make[3]: *** [src/CMakeFiles/osmium.dir/command_cat.cpp.o] Error 1
  make[3]: *** Waiting for unfinished jobs
  In file included from /usr/include/osmium/io/detail/pbf_decoder.hpp:51:0,
   from /usr/include/osmium/io/detail/pbf_input_format.hpp:51,
   from /usr/include/osmium/io/pbf_input.hpp:46,
   from /usr/include/osmium/io/any_input.hpp:48,
   from 
/home/lamby/temp/cdt.20160225074829.SvnyKmT6F8/osmium-tool-1.3.0/src/command_changeset_filter.cpp:27:
  /usr/include/osmium/io/detail/protobuf_tags.hpp:36:35: fatal error: 
protozero/pbf_types.hpp: No such file or directory
  compilation terminated.
  [ 48%] Building CXX object 
test/CMakeFiles/unit_tests.dir/__/src/command_apply_changes.cpp.o
  cd 
/home/lamby/temp/cdt.20160225074829.SvnyKmT6F8/osmium-tool-1.3.0/obj-x86_64-linux-gnu/test
 && /usr/bin/c++   -DOSMIUM_VERSION=\"1.3.0\" -D_FILE_OFFSET_BITS=64 
-D_LARGEFILE_SOURCE 
-I/home/lamby/temp/cdt.20160225074829.SvnyKmT6F8/osmium-tool-1.3.0/test/include 
-I/home/lamby/temp/cdt.20160225074829.SvnyKmT6F8/osmium-tool-1.3.0/test/../src 
-I/home/lamby/temp/cdt.20160225074829.SvnyKmT6F8/osmium-tool-1.3.0/test/../include
  -g -O2 -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time 
-D_FORTIFY_SOURCE=2-std=c++11 -o 
CMakeFiles/unit_tests.dir/__/src/command_apply_changes.cpp.o -c 
/home/lamby/temp/cdt.20160225074829.SvnyKmT6F8/osmium-tool-1.3.0/src/command_apply_changes.cpp
  src/CMakeFiles/osmium.dir/build.make:161: recipe for target 
'src/CMakeFiles/osmium.dir/command_changeset_filter.cpp.o' failed
  make[3]: *** [src/CMakeFiles/osmium.dir/command_changeset_filter.cpp.o] Error 
1
  [ 51%] Building CXX object 
test/CMakeFiles/unit_tests.dir/__/src/command_help.cpp.o
  cd 
/home/lamby/temp/cdt.20160225074829.SvnyKmT6F8/osmium-tool-1.3.0/obj-x86_64-linux-gnu/test
 && /usr/bin/c++   -DOSMIUM_VERSION=\"1.3.0\" -D_FILE_OFFSET_BITS=64 
-D_LARGEFILE_SOURCE 
-I/home/lamby/temp/cdt.20160225074829.SvnyKmT6F8/osmium-tool-1.3.0/test/include 
-I/home/lamby/temp/cdt.20160225074829.SvnyKmT6F8/osmium-tool-1.3.0/test/../src 
-I/home/lamby/temp/cdt.20160225074829.SvnyKmT6F8/osmium-tool-1.3.0/test/../include
  -g -O2 -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time 
-D_FORTIFY_SOURCE=2-std=c++11 -o 
CMakeFiles/unit_tests.dir/__/src/command_help.cpp.o -c 

Bug#815868: marked as done (osmcoastline: FTBFS: protobuf_tags.hpp:36:35: fatal error: protozero/pbf_types.hpp: No such file or directory)

[Debian Bug Tracking System]

Your message dated Thu, 25 Feb 2016 20:53:31 +0100
with message-id <56cf5bbb.8020...@xs4all.nl>
and subject line Re: Bug#815869: Header renamed in protozero 1.3.0
has caused the Debian Bug report #815868,
regarding osmcoastline: FTBFS: protobuf_tags.hpp:36:35: fatal error: 
protozero/pbf_types.hpp: No such file or directory
to be marked as done.

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

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


-- 
815868: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=815868
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: osmcoastline
Version: 2.1.2-1
Severity: serious
Justification: fails to build from source
User: reproducible-bui...@lists.alioth.debian.org
Usertags: ftbfs
X-Debbugs-Cc: reproducible-bui...@lists.alioth.debian.org

Dear Maintainer,

osmcoastline fails to build from source in unstable/amd64:

  [..]

  [ 70%] Building CXX object 
src/CMakeFiles/osmcoastline.dir/output_database.cpp.o
  cd 
/home/lamby/temp/cdt.20160225074733.Dt35P9JqeR/osmcoastline-2.1.2/obj-x86_64-linux-gnu/src
 && /usr/bin/c++   -DOSMCOASTLINE_VERSION=\"2.1.2\" -D_FILE_OFFSET_BITS=64 
-D_LARGEFILE_SOURCE 
-I/home/lamby/temp/cdt.20160225074733.Dt35P9JqeR/osmcoastline-2.1.2/include 
-isystem /usr/include/gdal  -g -O2 -fstack-protector-strong -Wformat 
-Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2-std=c++11 -Wall 
-Wextra -pedantic -Wredundant-decls -Wdisabled-optimization -Wctor-dtor-privacy 
-Wnon-virtual-dtor -Woverloaded-virtual -Wsign-promo -Wold-style-cast -o 
CMakeFiles/osmcoastline.dir/output_database.cpp.o -c 
/home/lamby/temp/cdt.20160225074733.Dt35P9JqeR/osmcoastline-2.1.2/src/output_database.cpp
  In file included from /usr/include/osmium/io/detail/pbf_decoder.hpp:51:0,
   from /usr/include/osmium/io/detail/pbf_input_format.hpp:51,
   from /usr/include/osmium/io/pbf_input.hpp:46,
   from /usr/include/osmium/io/any_input.hpp:48,
   from 
/home/lamby/temp/cdt.20160225074733.Dt35P9JqeR/osmcoastline-2.1.2/src/osmcoastline_filter.cpp:27:
  /usr/include/osmium/io/detail/protobuf_tags.hpp:36:35: fatal error: 
protozero/pbf_types.hpp: No such file or directory
  compilation terminated.
  src/CMakeFiles/osmcoastline_filter.dir/build.make:65: recipe for target 
'src/CMakeFiles/osmcoastline_filter.dir/osmcoastline_filter.cpp.o' failed
  make[3]: *** 
[src/CMakeFiles/osmcoastline_filter.dir/osmcoastline_filter.cpp.o] Error 1
  make[3]: Leaving directory 
'/home/lamby/temp/cdt.20160225074733.Dt35P9JqeR/osmcoastline-2.1.2/obj-x86_64-linux-gnu'
  CMakeFiles/Makefile2:168: recipe for target 
'src/CMakeFiles/osmcoastline_filter.dir/all' failed
  make[2]: *** [src/CMakeFiles/osmcoastline_filter.dir/all] Error 2
  make[2]: *** Waiting for unfinished jobs
  In file included from /usr/include/osmium/io/detail/pbf_decoder.hpp:51:0,
   from /usr/include/osmium/io/detail/pbf_input_format.hpp:51,
   from /usr/include/osmium/io/pbf_input.hpp:46,
   from /usr/include/osmium/io/any_input.hpp:48,
   from 
/home/lamby/temp/cdt.20160225074733.Dt35P9JqeR/osmcoastline-2.1.2/src/osmcoastline_ways.cpp:31:
  /usr/include/osmium/io/detail/protobuf_tags.hpp:36:35: fatal error: 
protozero/pbf_types.hpp: No such file or directory
  compilation terminated.
  src/CMakeFiles/osmcoastline_ways.dir/build.make:65: recipe for target 
'src/CMakeFiles/osmcoastline_ways.dir/osmcoastline_ways.cpp.o' failed
  make[3]: *** [src/CMakeFiles/osmcoastline_ways.dir/osmcoastline_ways.cpp.o] 
Error 1
  make[3]: Leaving directory 
'/home/lamby/temp/cdt.20160225074733.Dt35P9JqeR/osmcoastline-2.1.2/obj-x86_64-linux-gnu'
  CMakeFiles/Makefile2:242: recipe for target 
'src/CMakeFiles/osmcoastline_ways.dir/all' failed
  make[2]: *** [src/CMakeFiles/osmcoastline_ways.dir/all] Error 2
  [ 75%] Building CXX object src/CMakeFiles/osmcoastline.dir/srs.cpp.o
  cd 
/home/lamby/temp/cdt.20160225074733.Dt35P9JqeR/osmcoastline-2.1.2/obj-x86_64-linux-gnu/src
 && /usr/bin/c++   -DOSMCOASTLINE_VERSION=\"2.1.2\" -D_FILE_OFFSET_BITS=64 
-D_LARGEFILE_SOURCE 
-I/home/lamby/temp/cdt.20160225074733.Dt35P9JqeR/osmcoastline-2.1.2/include 
-isystem /usr/include/gdal  -g -O2 -fstack-protector-strong -Wformat 
-Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2-std=c++11 -Wall 
-Wextra -pedantic -Wredundant-decls -Wdisabled-optimization -Wctor-dtor-privacy 
-Wnon-virtual-dtor -Woverloaded-virtual -Wsign-promo -Wold-style-cast -o 
CMakeFiles/osmcoastline.dir/srs.cpp.o -c 
/home/lamby/temp/cdt.20160225074733.Dt35P9JqeR/osmcoastline-2.1.2/src/srs.cpp
  [ 80%] 

Processed: Re: Bug#815869: Header renamed in protozero 1.3.0

[Debian Bug Tracking System]

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

> notfound 815868 osmcoastline/2.1.2-1
Bug #815868 [src:osmcoastline] osmcoastline: FTBFS: protobuf_tags.hpp:36:35: 
fatal error: protozero/pbf_types.hpp: No such file or directory
No longer marked as found in versions osmcoastline/2.1.2-1.
> notfound 815869 osmium-tool/1.3.0-1
Bug #815869 [src:osmium-tool] osmium-tool: FTBFS: protobuf_tags.hpp:36:35: 
fatal error: protozero/pbf_types.hpp: No such file or directory
No longer marked as found in versions osmium-tool/1.3.0-1.
> thanks
Stopping processing here.

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

Bug#815917: phpmyadmin crashes silently

[Guy Durrieu]

Le 25/02/2016 19:09, Michal Čihař a écrit :

Hi

Dne 25.2.2016 v 18:29 Guy Durrieu napsal(a):

Package: phpmyadmin
Version: 4:4.5.5-1
Severity: grave
Justification: renders package unusable

Dear Maintainer,

I again got a problem with phpmyadmin...

After today last upgrade(from 4:4.5.4.1-2 to 4:4.5.5-1), phpmyadmin
silently crashes after login. I get a blank screen with iceweasel, and a
server error 500 with chromium, wjth the following details (sorry, in
french):
---
Le site Web a rencontré une erreur lors de l'extraction de*
http://localhost/phpmyadmin/index.php?target=import.php=0ef11afdf0092fafdb39d194dbf8baf0*.

Cela peut être dû à une opération de maintenance ou à une configuration
incorrecte.
---

However, no error messages were displayed, neither during upgrade nor in
log files:

Is there something in the Apache error logs?



OK, I should have a look to that:

error.log:[Thu Feb 25 17:39:42.283655 2016] [:error] [pid 16091] [client 
::1:55330] PHP Fatal error:  require_once(): Failed opening required 
'./libraries/php-gettext/gettext.inc' (include_path='.') in 
/usr/share/phpmyadmin/libraries/sql-parser/autoload.php on line 70, 
referer: http://localhost/phpmyadmin/import.php


Regards.

-- GD.

Bug#808528: marked as done (pidgin-twitter: FTBFS: error: #warning "_BSD_SOURCE and _SVID_SOURCE are deprecated, use _DEFAULT_SOURCE" [-Werror=cpp])

[Debian Bug Tracking System]

Your message dated Thu, 25 Feb 2016 19:21:56 +
with message-id 
and subject line Bug#808528: fixed in pidgin-twitter 0.9.2.1-6
has caused the Debian Bug report #808528,
regarding pidgin-twitter: FTBFS: error: #warning "_BSD_SOURCE and _SVID_SOURCE 
are deprecated, use _DEFAULT_SOURCE" [-Werror=cpp]
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.)


-- 
808528: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=808528
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: pidgin-twitter
Version: 0.9.2.1-5
Severity: serious
Justification: fails to build from source
Tags: sid 
User: reproducible-bui...@lists.alioth.debian.org
Usertags: ftbfs
X-Debbugs-CC: reproducible-bui...@lists.alioth.debian.org

Dear Maintainer,

The package fails to build:

make[1]: Entering directory '/pidgin-twitter-0.9.2.1'
CFLAGS="-g -O2 -fstack-protector-strong -Wformat -Werror=format-security" 
CPPFLAGS="-D_FORTIFY_SOURCE=2" CXXFLAGS="-g -O2 -fstack-protector-strong 
-Wformat -Werror=format-security" FCFLAGS="-g -O2 -fstack-protector-strong" 
FFLAGS="-g -O2 -fstack-protector-strong" GCJFLAGS="-g -O2 
-fstack-protector-strong" LDFLAGS="-Wl,-z,relro" OBJCFLAGS="-g -O2 
-fstack-protector-strong -Wformat -Werror=format-security" OBJCXXFLAGS="-g -O2 
-fstack-protector-strong -Wformat -Werror=format-security"  /usr/bin/make
make[2]: Entering directory '/pidgin-twitter-0.9.2.1'
cc -MM main.c util.c prefs.c icon.c twitter_api.c > .deps
main.c:1440:24: error: missing binary operator before token "("
 #if !GLIB_CHECK_VERSION(2, 35, 0)
^
cc -o main.o main.c -c -g -O2 -fstack-protector-strong -Wformat 
-Werror=format-security -fPIC -shared -Wall -Werror -g -pthread 
-I/usr/include/gtk-2.0 -I/usr/lib/x86_64-linux-gnu/gtk-2.0/include 
-I/usr/include/gio-unix-2.0/ -I/usr/include/cairo -I/usr/include/pango-1.0 
-I/usr/include/atk-1.0 -I/usr/include/cairo -I/usr/include/pixman-1 
-I/usr/include/libpng12 -I/usr/include/gdk-pixbuf-2.0 -I/usr/include/libpng12 
-I/usr/include/pango-1.0 -I/usr/include/harfbuzz -I/usr/include/pango-1.0 
-I/usr/include/freetype2 -I/usr/include/glib-2.0 
-I/usr/lib/x86_64-linux-gnu/glib-2.0/include -I/usr/include/pidgin 
-I/usr/include/libpurple -I/usr/include/glib-2.0 
-I/usr/lib/x86_64-linux-gnu/glib-2.0/include -I/usr/include/libxml2 
-DDATADIR=\"/usr/share\" -D_FORTIFY_SOURCE=2
In file included from /usr/include/stdio.h:27:0,
 from pidgin-twitter.h:6,
 from main.c:21:
/usr/include/features.h:148:3: error: #warning "_BSD_SOURCE and _SVID_SOURCE 
are deprecated, use _DEFAULT_SOURCE" [-Werror=cpp]
 # warning "_BSD_SOURCE and _SVID_SOURCE are deprecated, use _DEFAULT_SOURCE"
   ^
cc1: all warnings being treated as errors
Makefile:26: recipe for target 'main.o' failed
make[2]: *** [main.o] Error 1

Full build log:
https://reproducible.debian.net/rb-pkg/unstable/amd64/pidgin-twitter.html

-- System Information:
Debian Release: stretch/sid
APT prefers unstable
APT policy: (500, 'unstable')
Architecture: amd64 (x86_64)
--- End Message ---
--- Begin Message ---
Source: pidgin-twitter
Source-Version: 0.9.2.1-6

We believe that the bug you reported is fixed in the latest version of
pidgin-twitter, 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 808...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Andreas Beckmann  (supplier of updated pidgin-twitter 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: Thu, 25 Feb 2016 18:12:54 +0100
Source: pidgin-twitter
Binary: pidgin-twitter
Architecture: source
Version: 0.9.2.1-6
Distribution: unstable
Urgency: medium
Maintainer: Debian QA Group 
Changed-By: Andreas Beckmann 
Description:
 pidgin-twitter - Pidgin plugin for Twitter
Closes: 808528
Changes:
 pidgin-twitter (0.9.2.1-6) unstable; urgency=medium
 .
   [ Andreas Beckmann ]
   * QA upload.
   * Update Vcs-* URLs.
   * Bump Standards-Version to 3.9.7.
 .
   [ Raúl Salinas-Monteagudo ]
   * Fixed FTBFS: _BSD_SOURCE is deprecated (Closes: #808528).
Checksums-Sha1:
 

Processed: affects 812743

[Debian Bug Tracking System]

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

> affects 812743 libsdformat3-dev
Bug #812743 [libsdformat4-dev] libsdformat4-dev and libsdformat3-dev: error 
when trying to install together
Added indication that 812743 affects libsdformat3-dev
> thanks
Stopping processing here.

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

Processed: affects 809764

[Debian Bug Tracking System]

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

> affects 809764 libqb-dev
Bug #809764 [libqb6-dev] libqb6-dev and libqb-dev: error when trying to install 
together
Added indication that 809764 affects libqb-dev
> thanks
Stopping processing here.

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

Bug#814494: marked as done (ijs: FTBFS: configure.ac:88: required file `./missing' not found)

[Debian Bug Tracking System]

Your message dated Thu, 25 Feb 2016 18:51:27 +
with message-id 
and subject line Bug#814494: fixed in ijs 0.35-12
has caused the Debian Bug report #814494,
regarding ijs: FTBFS: configure.ac:88: required file `./missing' 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.)


-- 
814494: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=814494
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: ijs
Version: 0.35-11
Severity: serious
Justification: fails to build from source
User: reproducible-bui...@lists.alioth.debian.org
Usertags: ftbfs
X-Debbugs-Cc: reproducible-bui...@lists.alioth.debian.org

Dear Maintainer,

ijs fails to build from source in unstable/amd64:

  [..]

   dpkg-buildpackage -rfakeroot -D -us -uc -b
  dpkg-buildpackage: source package ijs
  dpkg-buildpackage: source version 0.35-11
  dpkg-buildpackage: source distribution unstable
  dpkg-buildpackage: source changed by Didier Raboud 
   dpkg-source --before-build ijs-0.35
  dpkg-buildpackage: host architecture amd64
   fakeroot debian/rules clean
  test -x debian/rules
  rm -f debian/stamp-makefile-build debian/stamp-makefile-install
  /usr/bin/make  -C .  -k distclean
  make[1]: Entering directory 
'/home/lamby/temp/cdt.20160212093707.idGPdCiGpW/ijs-0.35'
  make[1]: *** No rule to make target 'distclean'.
  make[1]: Leaving directory 
'/home/lamby/temp/cdt.20160212093707.idGPdCiGpW/ijs-0.35'
  /usr/share/cdbs/1/class/makefile.mk:55: recipe for target 'makefile-clean' 
failed
  make: [makefile-clean] Error 2 (ignored)
  rm -f debian/stamp-autotools
  rmdir --ignore-fail-on-non-empty .
  rmdir: failed to remove '.': Invalid argument
  /usr/share/cdbs/1/class/autotools.mk:52: recipe for target 'makefile-clean' 
failed
  make: [makefile-clean] Error 1 (ignored)
  for i in ./config.guess ./config.sub  ; do \
if test -e $i.cdbs-orig ; then \
mv $i.cdbs-orig $i ; \
fi ; \
  done
  rm -f debian/stamp-autotools-files
  dh_clean 
  rm -f debian/copyright_newhints
  rm -f debian/cdbs-install-list debian/cdbs-package-list 
debian/stamp-copyright-check
  rm -rf "debian/upstream-cruft"
  rm -f debian/stamp-upstream-cruft
  for file in ltmain.sh configure aclocal.m4 Makefile.in ijs_spec.pdf; do \
[ ! -e $file.upstream ] || mv -f $file.upstream $file; \
  done
  rm -f debian/stamp-upstreamtmpstuff
  rm -f debian/cdbs-reduced-package-list debian/cdbs-reduced-install-list 
debian/cdbs-install-diff
   debian/rules build
  test -x debian/rules
  mkdir -p "."
  
  Scanning upstream source for new/changed copyright notices...
  
  licensecheck -c '.*' -r --copyright -i 
'^(ijs_spec\.pdf|debian/(changelog|copyright(|_hints|_newhints)))' -l '9' * 
| /usr/lib/cdbs/licensecheck2dep5 > debian/copyright_newhints
  11 combinations of copyright and licensing found.
  WARNING: The following (and possibly more) new or changed notices discovered:
  
  Format: http://www.debian.org/doc/packaging-manuals/…
   debian/README.source
   debian/gbp.conf
   debian/libijs-doc.docs
   debian/patches/pkgconfig-libdir.diff
   debian/patches/series
   debian/patches/use_db2pdf.patch
2001-2004, artofcode LLC
  License: Expat
  Files: aclocal.m4
   config.guess
   ltmain.sh
  Copyright: 1992-1999, 2000-2003, Free Software Foundation, …
1996-2001, 2003 Free Software Foundation, Inc.
1996-2002, Free Software Foundation, Inc.
   missing
  Copyright: 1996-1997, 1999-2000, 2002-2003, Free Software …
2003, Free Software Foundation, Inc
  Files: install-sh
  Copyright: 1994, X Consortium
and license
  License: Expat
  Files: debian/rules
  Copyright: 2008, Bradley Smith 
2011, Jonas Smedegaard 
  Copyright: 1994-2002, Free Software Foundation, Inc.
  
  To fix the situation please do the following:
1) Fully compare debian/copyright_hints with debian/copyright_newhints
2) Update debian/copyright as needed
3) Replace debian/copyright_hints with debian/copyright_newhints
  touch debian/stamp-copyright-check
  touch debian/stamp-upstream-cruft
  for file in ltmain.sh configure aclocal.m4 Makefile.in ijs_spec.pdf; do \
[ ! -e $file ] || [ -e $file.upstream ] || cp -a $file $file.upstream; \
  done
  touch debian/stamp-upstreamtmpstuff
  if test -e /usr/share/misc/config.guess ; then \
for i in ./config.guess ; do \
if ! test -e $i.cdbs-orig ; then \
mv $i $i.cdbs-orig ; \
cp --remove-destination 

Bug#815660: marked as done (lombok-patcher b-d's on liblombok-java (>= 1:1.16.6) which doesn't exist)

[Debian Bug Tracking System]

Your message dated Thu, 25 Feb 2016 18:51:55 +
with message-id 
and subject line Bug#815660: fixed in lombok-patcher 0.20-3
has caused the Debian Bug report #815660,
regarding lombok-patcher b-d's on liblombok-java (>= 1:1.16.6) which doesn't 
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.)


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

Package: src:lombok-patcher
Version: 0.20-2
Severity: serious
Tags: sid stretch

lombok-patcher b-d's on liblombok-java (>= 1:1.16.6) which doesn't exist (not in 
the NEW queue either).
--- End Message ---
--- Begin Message ---
Source: lombok-patcher
Source-Version: 0.20-3

We believe that the bug you reported is fixed in the latest version of
lombok-patcher, 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 815...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Markus Koschany  (supplier of updated lombok-patcher 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, 25 Feb 2016 19:08:58 +0100
Source: lombok-patcher
Binary: liblombok-patcher-java
Architecture: source all
Version: 0.20-3
Distribution: unstable
Urgency: medium
Maintainer: Debian Java Maintainers 

Changed-By: Markus Koschany 
Description:
 liblombok-patcher-java - live-rewrite classes as a JVM runs
Closes: 815660
Changes:
 lombok-patcher (0.20-3) unstable; urgency=medium
 .
   * Remove versioned build-dependency on liblombok-java. (Closes: #815660)
   * Remove ivy from Build-Depends.
   * Update build.patch and define compilerarg processorpath explicitly. This
 ensures that the correct annotation processor is instantiated and prevents
 build failures.
Checksums-Sha1:
 c6183f55ca3fb1fdb97595ef5714ce54a096dfc1 2210 lombok-patcher_0.20-3.dsc
 09dca02f2cb1b59403517fb74648674b130660db 3468 
lombok-patcher_0.20-3.debian.tar.xz
 2f9155fb48eccebc41f486474f7345bd8f289c49 65554 
liblombok-patcher-java_0.20-3_all.deb
Checksums-Sha256:
 72a701cfaf2ff9ec952b8ab27591a5ca621924871ddee3b151dc18efe415c331 2210 
lombok-patcher_0.20-3.dsc
 5c0ea177e377f040e71e0494d3d41935b1571329bfc303847edef4d5b8526867 3468 
lombok-patcher_0.20-3.debian.tar.xz
 343560bc5323c87a88b837e9827a74b197dbdac1bf5b9d56ed8a2985319aa228 65554 
liblombok-patcher-java_0.20-3_all.deb
Files:
 89502f526988a5f5eae7f0739844d568 2210 java optional lombok-patcher_0.20-3.dsc
 eff060c8cc0019eaed8e6b24830e433c 3468 java optional 
lombok-patcher_0.20-3.debian.tar.xz
 365dfaaeab668a6b2eea00f8593d62cf 65554 java optional 
liblombok-patcher-java_0.20-3_all.deb

-BEGIN PGP SIGNATURE-
Version: GnuPG v1

iQJ8BAEBCgBmBQJWz0RZXxSAAC4AKGlzc3Vlci1mcHJAbm90YXRpb25zLm9w
ZW5wZ3AuZmlmdGhob3JzZW1hbi5uZXRBQ0YzRDA4OEVGMzJFREVGNkExQTgzNUZE
OUFEMTRCOTUxM0I1MUU0AAoJENmtFLlRO1Hk1OwP/jJ1XH3sJC5oUVZgM6mLow6w
4lk68EzK3KDZp3pDB0sPwDNpNXo8txWsT3OJgYyCVTBCdYClpwPa+7b+MV9aCTzF
6nvPjwEAeNye9nvgM+Rgqo/fHQhw98q2vu28ESGtzYH82uneCTIcGzuCwi9CBr6d
7UtCNOgkzBm4yroFTFNGAQiO56uyGgS8kH5ejM9QvxUAsxZNWtfXXqAvksGmBEpX
20QMmE/fmm6BG36UyRj0IFORw/Sbb0yO9Gc3T5lQw4GXpVR6E7EMx5fyxOwqLa21
33KVOqxqMmphL/0O8XW9LSwL73rWwjKMCVSDMJqFShj3JqJbOabttm3C46NNDVny
k2BeQTZXTL8YqMQyQboTT7hcyPKvHhgCYCnuPLvT8JrwsHoUGz/JFBYvcAIE3iVP
N0VOupE6QAyBIaoB4m3b7PtN3xLEABYGg7DLjNkEDPmIjNKV8GYic86zxK8BdSVl
R0H1NPsteNGC/HBdL4mgoouarRDcOpopJqi1Y2FwudWd5AjbrPOiaogNW9lZORWm
dZJfUk2rRb0/QLx24lN9b1+jus0sjQenk1k0uV8IpLcVcods8jqub0WkFR2TPNWG
pDESiXpqYoc3iR7+iUbXboIkiVEubvqL2NYmb/hfTLekZI7FCNTIkXCbiaWVOssE
3piXt1xyDRcsWH/w4gO6
=XA2o
-END PGP SIGNATURE End Message ---

Bug#808433: marked as done (nethogs doesn't start, saying "creating socket failed")

[Debian Bug Tracking System]

Your message dated Thu, 25 Feb 2016 18:27:56 +
with message-id 
and subject line Bug#808433: fixed in nethogs 0.8.1-0.3
has caused the Debian Bug report #808433,
regarding nethogs doesn't start, saying "creating socket failed"
to be marked as done.

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

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


-- 
808433: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=808433
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: nethogs
Version: 0.8.0-1+b2

On Linux kernel 4.3.3-2, nethogs fails immediately:

$ nethogs wlan0
creating socket failed while establishing local IP - are you root?
$ cat /proc/version
Linux version 4.3.0-1-686-pae (debian-ker...@lists.debian.org) (gcc version
5.3.1 20151207 (Debian 5.3.1-3) ) #1 SMP Debian 4.3.3-2 (2015-12-17)
$ id
uid=0(root) gid=0(root) groups=0(root)
$ ip link show wlan0
3: wlan0:  mtu 1500 qdisc mq state UP mode
DORMANT group default qlen 1000
link/ether 00:13:02:99:59:18 brd ff:ff:ff:ff:ff:ff

It worked as I expected on kernel 4.2.6-3 (and many earlier versions).
--- End Message ---
--- Begin Message ---
Source: nethogs
Source-Version: 0.8.1-0.3

We believe that the bug you reported is fixed in the latest version of
nethogs, 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 808...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Arnout Engelen  (supplier of updated nethogs 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: Wed, 17 Feb 2016 12:34:56 +0100
Source: nethogs
Binary: nethogs
Architecture: source amd64
Version: 0.8.1-0.3
Distribution: unstable
Urgency: medium
Maintainer: Bart Martens 
Changed-By: Arnout Engelen 
Description:
 nethogs- Net top tool grouping bandwidth per process
Closes: 808433
Changes:
 nethogs (0.8.1-0.3) unstable; urgency=medium
 .
   * Non-maintainer upload.
   * New upstream release. Closes: #808433
   * Show '?' as PID when the PID could not be determined, instead of '0'.
   * Allow large values for 'pid'
   * Use a normal DGRAM (UDP) socket to determine local IPv4 IP
Checksums-Sha1:
 0aba0377721f05c41c4112a574360e9f0e4e0c05 1485 nethogs_0.8.1-0.3.dsc
 f768eca5567657de36de8b1b73eedeb5f093cc8c 35986 nethogs_0.8.1.orig.tar.gz
 18450cbcdca1acbda9f9464a875df9aa7395db4e 2904 nethogs_0.8.1-0.3.debian.tar.xz
 c5624d85fe2af5e8b554e9635e1c718d51d30d1e 179858 
nethogs-dbgsym_0.8.1-0.3_amd64.deb
 52850c6f5a9c308e74ef997f3c6c7209330e47b9 26554 nethogs_0.8.1-0.3_amd64.deb
Checksums-Sha256:
 16ba9759a3baa100df56b42880212e6054688b58d3ea11d47a4d14b22b59cfce 1485 
nethogs_0.8.1-0.3.dsc
 4c30ef43814549974a5b01fb1a94eb72ff08628c5a421085b1ce3bfe0524df42 35986 
nethogs_0.8.1.orig.tar.gz
 5d807afb8a02ff2d99e49f408066bf774e4906e4b4b16e9a60f2564cd409bc1a 2904 
nethogs_0.8.1-0.3.debian.tar.xz
 f069bf54084a34871c71abcd69c14d9da88c78b4b21f99ddb77d7d68266033a9 179858 
nethogs-dbgsym_0.8.1-0.3_amd64.deb
 6f1e4cc78b33a42238efe042189cb3b921fbb1baf2146864e14909218c5b28eb 26554 
nethogs_0.8.1-0.3_amd64.deb
Files:
 403e6706e34062abfc2a721553a947f5 1485 net optional nethogs_0.8.1-0.3.dsc
 cc0aed87c4cc67fc2ffc5f60aa67bf3d 35986 net optional nethogs_0.8.1.orig.tar.gz
 06e6753c829b8b6592b7188e93fcec9b 2904 net optional 
nethogs_0.8.1-0.3.debian.tar.xz
 8c95d7d6510e6c0158b291285875e623 179858 debug extra 
nethogs-dbgsym_0.8.1-0.3_amd64.deb
 c1f8d09c1b99c0e634508b5a8ec47f56 26554 net optional nethogs_0.8.1-0.3_amd64.deb

-BEGIN PGP SIGNATURE-

iQF8BAEBCgBmBQJWz0T+XxSAAC4AKGlzc3Vlci1mcHJAbm90YXRpb25zLm9w
ZW5wZ3AuZmlmdGhob3JzZW1hbi5uZXQ1QzA2NTY4NTc1NTE2RDBBMzNGRkE3QTND
MDg5OTBGQjFGNjM3ODkzAAoJEMCJkPsfY3iTAhQH/16URlkLX+xqO5QUi5WDqSwR
lEdYG30jrMvxJ7krwjnhp+iEflZBGx/Zfv6iyX2E4ZVIaylXrVOKbOamsPCPxJAB
kIx5A51dedS5bz6MF5wFMK7m8w1mwpiNq4VwHMfWvnKImpz6Ac+nuiQWu9gTGkVc
qOIOBxllD1/ITKHGN4gcDajeM8pXbcXrP4uKB1F9qa8trMamXgCBwR3gPGGyeEwX
JD2+YNyMYxCTCQRShxHxoYdjNAbXBNxWR4yhal8JbucuTkn1lxb+MeR2mQPbUXBl
52VaDwmh4P3wRnGH9A5iGbC/a/XJKwey8AFr9pm1Ji8qbSvWC9l+IjwbZmkPsKI=
=XcNd
-END PGP SIGNATURE End Message ---

Bug#811273: marked as done (nethogs: creating socket failed while establishing local IP)

[Debian Bug Tracking System]

Your message dated Thu, 25 Feb 2016 18:27:56 +
with message-id 
and subject line Bug#808433: fixed in nethogs 0.8.1-0.3
has caused the Debian Bug report #808433,
regarding nethogs: creating socket failed while establishing local IP
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.)


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

Hello,

I get this error when I run nethogs:
creating socket failed while establishing local IP - are you root?

I tried running it with sudo and with the root user itself, but I always get
this message.

Regards,



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

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

Versions of packages nethogs depends on:
ii  libc62.19-18+deb8u1
ii  libgcc1  1:4.9.2-10
ii  libncurses5  5.9+20140913-1+b1
ii  libpcap0.8   1.6.2-2
ii  libstdc++6   4.9.2-10

nethogs recommends no packages.

nethogs suggests no packages.

-- no debconf information
--- End Message ---
--- Begin Message ---
Source: nethogs
Source-Version: 0.8.1-0.3

We believe that the bug you reported is fixed in the latest version of
nethogs, 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 808...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Arnout Engelen  (supplier of updated nethogs 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: Wed, 17 Feb 2016 12:34:56 +0100
Source: nethogs
Binary: nethogs
Architecture: source amd64
Version: 0.8.1-0.3
Distribution: unstable
Urgency: medium
Maintainer: Bart Martens 
Changed-By: Arnout Engelen 
Description:
 nethogs- Net top tool grouping bandwidth per process
Closes: 808433
Changes:
 nethogs (0.8.1-0.3) unstable; urgency=medium
 .
   * Non-maintainer upload.
   * New upstream release. Closes: #808433
   * Show '?' as PID when the PID could not be determined, instead of '0'.
   * Allow large values for 'pid'
   * Use a normal DGRAM (UDP) socket to determine local IPv4 IP
Checksums-Sha1:
 0aba0377721f05c41c4112a574360e9f0e4e0c05 1485 nethogs_0.8.1-0.3.dsc
 f768eca5567657de36de8b1b73eedeb5f093cc8c 35986 nethogs_0.8.1.orig.tar.gz
 18450cbcdca1acbda9f9464a875df9aa7395db4e 2904 nethogs_0.8.1-0.3.debian.tar.xz
 c5624d85fe2af5e8b554e9635e1c718d51d30d1e 179858 
nethogs-dbgsym_0.8.1-0.3_amd64.deb
 52850c6f5a9c308e74ef997f3c6c7209330e47b9 26554 nethogs_0.8.1-0.3_amd64.deb
Checksums-Sha256:
 16ba9759a3baa100df56b42880212e6054688b58d3ea11d47a4d14b22b59cfce 1485 
nethogs_0.8.1-0.3.dsc
 4c30ef43814549974a5b01fb1a94eb72ff08628c5a421085b1ce3bfe0524df42 35986 
nethogs_0.8.1.orig.tar.gz
 5d807afb8a02ff2d99e49f408066bf774e4906e4b4b16e9a60f2564cd409bc1a 2904 
nethogs_0.8.1-0.3.debian.tar.xz
 f069bf54084a34871c71abcd69c14d9da88c78b4b21f99ddb77d7d68266033a9 179858 
nethogs-dbgsym_0.8.1-0.3_amd64.deb
 6f1e4cc78b33a42238efe042189cb3b921fbb1baf2146864e14909218c5b28eb 26554 
nethogs_0.8.1-0.3_amd64.deb
Files:
 403e6706e34062abfc2a721553a947f5 1485 net optional nethogs_0.8.1-0.3.dsc
 cc0aed87c4cc67fc2ffc5f60aa67bf3d 35986 net optional nethogs_0.8.1.orig.tar.gz
 06e6753c829b8b6592b7188e93fcec9b 2904 net optional 
nethogs_0.8.1-0.3.debian.tar.xz
 8c95d7d6510e6c0158b291285875e623 179858 debug extra 
nethogs-dbgsym_0.8.1-0.3_amd64.deb
 c1f8d09c1b99c0e634508b5a8ec47f56 26554 net optional nethogs_0.8.1-0.3_amd64.deb

-BEGIN PGP SIGNATURE-

iQF8BAEBCgBmBQJWz0T+XxSAAC4AKGlzc3Vlci1mcHJAbm90YXRpb25zLm9w
ZW5wZ3AuZmlmdGhob3JzZW1hbi5uZXQ1QzA2NTY4NTc1NTE2RDBBMzNGRkE3QTND
MDg5OTBGQjFGNjM3ODkzAAoJEMCJkPsfY3iTAhQH/16URlkLX+xqO5QUi5WDqSwR
lEdYG30jrMvxJ7krwjnhp+iEflZBGx/Zfv6iyX2E4ZVIaylXrVOKbOamsPCPxJAB

Processed: nethogs: diff for NMU version 0.8.1-0.3

[Debian Bug Tracking System]

Processing control commands:

> tags 808433 + patch
Bug #808433 [nethogs] nethogs doesn't start, saying "creating socket failed"
Bug #811273 [nethogs] nethogs: creating socket failed while establishing local 
IP
Added tag(s) patch.
Added tag(s) patch.

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

Bug#808433: nethogs: diff for NMU version 0.8.1-0.3

[Tristan Seligmann]

Control: tags 808433 + patch

Dear maintainer,

I've prepared an NMU for nethogs (versioned as 0.8.1-0.3). The diff
is attached to this message.

(This is just Arnout Engelen's package from mentors, with a tiny tweak to the
changelog)

Regards.
diff -Nru nethogs-0.8.0/Changelog nethogs-0.8.1/Changelog
--- nethogs-0.8.0/Changelog 2010-08-31 23:16:32.0 +0200
+++ nethogs-0.8.1/Changelog 2015-12-20 21:14:42.0 +0200
@@ -1,5 +1,15 @@
 Changelog
 
+12/05/13 (muzso)
+- added new command line switches:
+  -s  Sorts output by the sent column.
+  -c  Limits the number of updates (useful for tracemode and scripting the
+  output).
+  -v  Sets view mode (0 = KB/s, 1 = total KB, 2 = total B, 3 = total MB)
+- changed needrefresh default value from true to false
+  (upon startup there's no useful info on network usage, so displaying
+   any results has no use for the user)
+
 31/08/10 (Arnout)
 - support for screens wider than 80 characters, thanks to Shock
   at https://bugs.launchpad.net/ubuntu/+source/nethogs/+bug/627626
@@ -18,7 +28,7 @@
 27/08/05 (Arnout)
 - giving all unknown connections their own
   `unknown' process
-- UDP support
+- Initial work on UDP support
 - investigated memleak, turns out to be a problem in libc:
   http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=273051 
   https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=103142
diff -Nru nethogs-0.8.0/connection.cpp nethogs-0.8.1/connection.cpp
--- nethogs-0.8.0/connection.cpp2008-12-31 17:52:26.0 +0200
+++ nethogs-0.8.1/connection.cpp2015-12-20 21:14:42.0 +0200
@@ -1,19 +1,31 @@
+/* 
+ * connection.cpp
+ *
+ * Copyright (c) 2004-2006,2008 Arnout Engelen
+ *
+ * This program is free software; you can redistribute it and/or
+ * modify it under the terms of the GNU General Public License
+ * as published by the Free Software Foundation; either version 2
+ * of the License, or (at your option) any later version.
+ *
+ * This program is distributed in the hope that it will be useful,
+ * but WITHOUT ANY WARRANTY; without even the implied warranty of
+ * MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.  See the
+ * GNU General Public License for more details.
+ *
+ * You should have received a copy of the GNU General Public License
+ * along with this program; if not, write to the Free Software
+ * Foundation, Inc., 51 Franklin Street, Fifth Floor, Boston, MA  02110-1301, 
USA.
+ *
+ */
+
+
 #include 
-#include 
+#include 
 #include 
 #include "nethogs.h"
 #include "connection.h"
-
-class ConnList
-{
-public:
-   ConnList (Connection * m_val = NULL, ConnList * m_next = NULL)
-   {
-   val = m_val; next = m_next;
-   }
-   Connection * val;
-   ConnList * next;
-};
+#include "process.h"
 
 ConnList * connections = NULL;
 
@@ -105,22 +117,22 @@
ConnList * prev_conn = NULL;
while (curr_conn != NULL)
{
-   if (curr_conn->val == this)
+   if (curr_conn->getVal() == this)
{
ConnList * todelete = curr_conn;
-   curr_conn = curr_conn->next;
+   curr_conn = curr_conn->getNext();
if (prev_conn == NULL)
{
connections = curr_conn;
} else {
-   prev_conn->next = curr_conn;
+   prev_conn->setNext(curr_conn);
}
delete (todelete);
}
else
{
prev_conn = curr_conn;
-   curr_conn = curr_conn->next;
+   curr_conn = curr_conn->getNext();
}
}
 }
@@ -153,43 +165,55 @@
}
 }
 
-/* 
- * finds connection to which this packet belongs.
- * a packet belongs to a connection if it matches
- * to its reference packet 
- */
-Connection * findConnection (Packet * packet)
-{
+Connection * findConnectionWithMatchingSource(Packet * packet) {
+   assert(packet->Outgoing());
+
ConnList * current = connections;
while (current != NULL)
{
-   /* the reference packet is always *outgoing* */
-   if (packet->match(current->val->refpacket))
+   /* the reference packet is always outgoing */
+   if (packet->matchSource(current->getVal()->refpacket))
{
-   return current->val;
+   return current->getVal();
}
 
-   current = current->next;
+   current = current->getNext();
}
+   return NULL;
+}
 
-   // Try again, now with the packet inverted:
-   current = connections;
-   Packet * invertedPacket = packet->newInverted();
-
+Connection * findConnectionWithMatchingRefpacketOrSource(Packet * packet) {
+   ConnList * current = connections;

Bug#815917: phpmyadmin crashes silently

[Michal Čihař]

Hi

Dne 25.2.2016 v 18:29 Guy Durrieu napsal(a):
> Package: phpmyadmin
> Version: 4:4.5.5-1
> Severity: grave
> Justification: renders package unusable
> 
> Dear Maintainer,
> 
> I again got a problem with phpmyadmin...
> 
> After today last upgrade(from 4:4.5.4.1-2 to 4:4.5.5-1), phpmyadmin
> silently crashes after login. I get a blank screen with iceweasel, and a
> server error 500 with chromium, wjth the following details (sorry, in
> french):

> 
> ---
> Le site Web a rencontré une erreur lors de l'extraction de*
> http://localhost/phpmyadmin/index.php?target=import.php=0ef11afdf0092fafdb39d194dbf8baf0*.
> 
> Cela peut être dû à une opération de maintenance ou à une configuration
> incorrecte.
> ---
> 
> However, no error messages were displayed, neither during upgrade nor in
> log files:

Is there something in the Apache error logs?

-- 
Michal Čihař | http://cihar.com | http://blog.cihar.com



signature.asc
Description: OpenPGP digital signature

Processed: tagging 815880, reassign 799259 to foomatic-filters, fixed 799259 in 4.0.17-8, affects 799259 ...

[Debian Bug Tracking System]

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

> tags 815880 + sid stretch
Bug #815880 [dnssec-trigger] Fails to update /etc/resolv.conf with 
network-manager 1.1.90
Added tag(s) stretch and sid.
> reassign 799259 foomatic-filters
Bug #799259 {Done: Jörg Frings-Fürst } 
[cups,foomatic-filters] foomatic-filters (for beh) and cups not coinstallable
Bug reassigned from package 'cups,foomatic-filters' to 'foomatic-filters'.
Ignoring request to alter found versions of bug #799259 to the same values 
previously set
No longer marked as fixed in versions foomatic-filters/4.0.17-8.
> fixed 799259 4.0.17-8
Bug #799259 {Done: Jörg Frings-Fürst } 
[foomatic-filters] foomatic-filters (for beh) and cups not coinstallable
Marked as fixed in versions foomatic-filters/4.0.17-8.
> affects 799259 + cups
Bug #799259 {Done: Jörg Frings-Fürst } 
[foomatic-filters] foomatic-filters (for beh) and cups not coinstallable
Added indication that 799259 affects cups
> tags 787924 + sid
Bug #787924 {Done: Thorsten Alteholz } [node-crc] node-crc: 
test failure Error: Use CoffeeScript.register()
Added tag(s) sid.
> thanks
Stopping processing here.

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

Processed: [bts-link] source package webkit2gtk

[Debian Bug Tracking System]

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

> #
> # bts-link upstream status pull for source package webkit2gtk
> # see http://lists.debian.org/debian-devel-announce/2006/05/msg1.html
> #
> user bts-link-upstr...@lists.alioth.debian.org
Setting user to bts-link-upstr...@lists.alioth.debian.org (was 
bts-link-de...@lists.alioth.debian.org).
> # remote status report for #802380 (http://bugs.debian.org/802380)
> # Bug title: epiphany-browser: System crashes when visiting reuters.com URL 
> (GPU crash?)
> #  * https://bugs.webkit.org/show_bug.cgi?id=126122
> #  * remote status changed: REOPENED -> RESOLVED
> #  * remote resolution changed: (?) -> FIXED
> #  * closed upstream
> tags 802380 + fixed-upstream
Bug #802380 [libwebkit2gtk-4.0-37] epiphany-browser: System crashes when 
visiting reuters.com URL (GPU crash?)
Added tag(s) fixed-upstream.
> usertags 802380 - status-REOPENED
Usertags were: status-REOPENED.
Usertags are now: .
> usertags 802380 + status-RESOLVED resolution-FIXED
There were no usertags set.
Usertags are now: resolution-FIXED status-RESOLVED.
> thanks
Stopping processing here.

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

Bug#815917: phpmyadmin crashes silently

[Guy Durrieu]

Package: phpmyadmin
Version: 4:4.5.5-1
Severity: grave
Justification: renders package unusable

Dear Maintainer,

I again got a problem with phpmyadmin...

After today last upgrade(from 4:4.5.4.1-2 to 4:4.5.5-1), phpmyadmin 
silently crashes after login. I get a blank screen with iceweasel, and a 
server error 500 with chromium, wjth the following details (sorry, in 
french):


---
Le site Web a rencontré une erreur lors de l'extraction de*
http://localhost/phpmyadmin/index.php?target=import.php=0ef11afdf0092fafdb39d194dbf8baf0*. 

Cela peut être dû à une opération de maintenance ou à une configuration 
incorrecte.

---

However, no error messages were displayed, neither during upgrade nor in 
log files:


---
apt/term.log:Dépaquetage de phpmyadmin (4:4.5.5-1) sur (4:4.5.4.1-2) ...
apt/term.log:Paramétrage de phpmyadmin (4:4.5.5-1) ...
apt/term.log:dbconfig-common: writing config to 
/etc/dbconfig-common/phpmyadmin.conf
apt/term.log:Replacing config file /etc/dbconfig-common/phpmyadmin.conf 
with new version
apt/term.log:Replacing config file /etc/phpmyadmin/config-db.php with 
new version

apt/term.log:apache2_invoke phpmyadmin: already enabled
---

Regards.

-- GD.

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

Kernel: Linux 4.4.0-1-amd64 (SMP w/2 CPU cores)
Locale: LANG=fr_FR.utf8, LC_CTYPE=fr_FR.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages phpmyadmin depends on:
ii  dbconfig-common2.0.3
ii  dbconfig-mysql 2.0.3
ii  debconf [debconf-2.0]  1.5.58
ii  libapache2-mod-php55.6.18+dfsg-1
ii  libjs-sphinxdoc1.3.5-1
ii  perl   5.22.1-7
ii  php-gettext1.0.11-2
ii  php-phpseclib  2.0.1-1
ii  php5   5.6.18+dfsg-1
ii  php5-common5.6.18+dfsg-1
ii  php5-json  1.3.7-1
ii  php5-mysql 5.6.18+dfsg-1
ii  ucf3.0035

Versions of packages phpmyadmin recommends:
ii  apache2 [httpd]  2.4.18-1
ii  mysql-client 5.6.28-1
ii  mysql-client-5.6 [virtual-mysql-client]  5.6.28-1
ii  php-tcpdf6.0.093+dfsg-1
ii  php5-gd  5.6.18+dfsg-1

Versions of packages phpmyadmin suggests:
ii  chromium [www-browser]   48.0.2564.116-1
ii  iceweasel [www-browser] 46.0~a2+20160217064514-1
ii  mysql-server 5.6.28-1
ii  mysql-server-5.6 [virtual-mysql-server]  5.6.28-1
ii  w3m [www-browser]0.5.3-26

-- debconf information:
  phpmyadmin/install-error: ignore
  phpmyadmin/mysql/method: Unix socket
  phpmyadmin/upgrade-error: abort
  phpmyadmin/remove-error: abort
  phpmyadmin/dbconfig-reinstall: false
  phpmyadmin/upgrade-backup: true
  phpmyadmin/remote/host: localhost
  phpmyadmin/db/dbname: phpmyadmin
* phpmyadmin/mysql/admin-user: debian-sys-maint
  phpmyadmin/database-type: mysql
* phpmyadmin/dbconfig-upgrade: true
* phpmyadmin/reconfigure-webserver: apache2
  phpmyadmin/internal/reconfiguring: false
  phpmyadmin/passwords-do-not-match:
  phpmyadmin/setup-username: admin
  phpmyadmin/remote/port:
  phpmyadmin/internal/skip-preseed: false
* phpmyadmin/dbconfig-install: true
  phpmyadmin/dbconfig-remove: true
  phpmyadmin/purge: false
  phpmyadmin/db/app-user: root
  phpmyadmin/remote/newhost:
  phpmyadmin/missing-db-package-error: abort

Bug#810903: marked as done (python-ase: FTBFS: VisibleDeprecationWarning: boolean index did not match indexed array along dimension 0; dimension is 20 but corresponding boolean dimension is 16)

[Debian Bug Tracking System]

Your message dated Thu, 25 Feb 2016 17:25:57 +
with message-id 
and subject line Bug#810903: fixed in python-ase 3.9.1.4567-3
has caused the Debian Bug report #810903,
regarding python-ase: FTBFS: VisibleDeprecationWarning: boolean index did not 
match indexed array along dimension 0; dimension is 20 but corresponding 
boolean dimension is 16
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.)


-- 
810903: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=810903
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: python-ase
Version: 3.9.1.4567-2
Severity: serious
Justification: fails to build from source
User: reproducible-bui...@lists.alioth.debian.org
Usertags: ftbfs
X-Debbugs-Cc: reproducible-bui...@lists.alioth.debian.org

Dear Maintainer,

python-ase fails to build from source in unstable/amd64:

  [..]

  COCu111.py (ScriptTestCase) ... Test suite failed
  ok
  
  ==
  ERROR: ga/basic_example_main_run.py (ScriptTestCase)
  --
  Traceback (most recent call last):
File 
"/home/lamby/temp/cdt.20160113161620.G27Cs2P8mg/python-ase-3.9.1.4567/ase/test/__init__.py",
 line 51, in testfile
  {'display': self.display})
File 
"/home/lamby/temp/cdt.20160113161620.G27Cs2P8mg/python-ase-3.9.1.4567/ase/test/ga/basic_example_main_run.py",
 line 49, in 
  dyn.run(fmax=0.05, steps=100)
File 
"/home/lamby/temp/cdt.20160113161620.G27Cs2P8mg/python-ase-3.9.1.4567/ase/optimize/optimize.py",
 line 148, in run
  f = self.atoms.get_forces()
File 
"/home/lamby/temp/cdt.20160113161620.G27Cs2P8mg/python-ase-3.9.1.4567/ase/atoms.py",
 line 691, in get_forces
  constraint.adjust_forces(self, forces)
File 
"/home/lamby/temp/cdt.20160113161620.G27Cs2P8mg/python-ase-3.9.1.4567/ase/constraints.py",
 line 125, in adjust_forces
  forces[self.index] = 0.0
  VisibleDeprecationWarning: boolean index did not match indexed array along 
dimension 0; dimension is 20 but corresponding boolean dimension is 16
  
  ==
  ERROR: ga/mutations.py (ScriptTestCase)
  --
  Traceback (most recent call last):
File 
"/home/lamby/temp/cdt.20160113161620.G27Cs2P8mg/python-ase-3.9.1.4567/ase/test/__init__.py",
 line 51, in testfile
  {'display': self.display})
File 
"/home/lamby/temp/cdt.20160113161620.G27Cs2P8mg/python-ase-3.9.1.4567/ase/test/ga/mutations.py",
 line 60, in 
  c3, desc = mmut.get_new_individual([c1])
File 
"/home/lamby/temp/cdt.20160113161620.G27Cs2P8mg/python-ase-3.9.1.4567/ase/ga/standardmutations.py",
 line 92, in get_new_individual
  indi = self.mutate(f)
File 
"/home/lamby/temp/cdt.20160113161620.G27Cs2P8mg/python-ase-3.9.1.4567/ase/ga/standardmutations.py",
 line 120, in mutate
  a.set_positions(p_tot)
File 
"/home/lamby/temp/cdt.20160113161620.G27Cs2P8mg/python-ase-3.9.1.4567/ase/atoms.py",
 line 608, in set_positions
  constraint.adjust_positions(self, newpositions)
File 
"/home/lamby/temp/cdt.20160113161620.G27Cs2P8mg/python-ase-3.9.1.4567/ase/constraints.py",
 line 122, in adjust_positions
  new[self.index] = atoms.positions[self.index]
  VisibleDeprecationWarning: boolean index did not match indexed array along 
dimension 0; dimension is 36 but corresponding boolean dimension is 32
  
  --
  Ran 142 tests in 34.993s
  
  FAILED (errors=2)
  E: pybuild pybuild:274: test: plugin custom failed with: exit code=2: 
python2.7 
/home/lamby/temp/cdt.20160113161620.G27Cs2P8mg/python-ase-3.9.1.4567/setup.py 
test
  dh_auto_test: pybuild --test -i python{version} -p 2.7 --dir . returned exit 
code 13
  debian/rules:11: recipe for target 'override_dh_auto_test' failed
  make[1]: *** [override_dh_auto_test] Error 25
  make[1]: Leaving directory 
'/home/lamby/temp/cdt.20160113161620.G27Cs2P8mg/python-ase-3.9.1.4567'
  debian/rules:8: recipe for target 'build' failed
  make: *** [build] Error 2

  [..]

The full build log is attached.


Regards,

-- 
  ,''`.
 : :'  : Chris Lamb
 `. `'`  la...@debian.org / chris-lamb.co.uk
   `-


python-ase.3.9.1.4567-2.unstable.amd64.log.txt.gz
Description: Binary data
--- End Message ---
--- Begin Message ---
Source: python-ase
Source-Version: 3.9.1.4567-3

We believe that the bug you reported is fixed in the 

Bug#787924: node-crc: test failure Error: Use CoffeeScript.register()

[Andreas Beckmann]

Followup-For: Bug #787924

Hi,

this package FTBFS in a similar way in jessie:

 debian/rules build
dh build
   dh_testdir
   dh_auto_configure
   debian/rules override_dh_auto_build
make[1]: Entering directory '/build/node-crc-3.0.0'
if [ ! -d lib.org ]; then mv lib lib.orig; fi
coffee --bare --output ./lib --compile ./src/*.coffee
make[1]: Leaving directory '/build/node-crc-3.0.0'
   debian/rules override_dh_auto_test
make[1]: Entering directory '/build/node-crc-3.0.0'
mocha -C test/*.spec.coffee

module.js:340
throw err;
  ^
Error: Cannot find module 'coffee-script/register'
at Function.Module._resolveFilename (module.js:338:15)
at Function.Module._load (module.js:280:25)
at Module.require (module.js:364:17)
at require (module.js:380:17)
at /usr/lib/nodejs/mocha/bin/_mocha:269:3
at Array.forEach (native)
at Object. (/usr/lib/nodejs/mocha/bin/_mocha:263:19)
at Module._compile (module.js:456:26)
at Object.Module._extensions..js (module.js:474:10)
at Module.load (module.js:356:32)
at Function.Module._load (module.js:312:12)
at Function.Module.runMain (module.js:497:10)
at startup (node.js:119:16)
at node.js:906:3
debian/rules:19: recipe for target 'override_dh_auto_test' failed
make[1]: *** [override_dh_auto_test] Error 8
make[1]: Leaving directory '/build/node-crc-3.0.0'
debian/rules:8: recipe for target 'build' failed
make: *** [build] Error 2


Andreas

Bug#796516: marked as done (ruby-mysql2: FTBFS: Mysql2::Error returns error messages and sql state in Encoding.default_internal if set)

[Debian Bug Tracking System]

Your message dated Thu, 25 Feb 2016 16:30:37 +
with message-id 
and subject line Bug#796516: fixed in ruby-mysql2 0.4.3-1
has caused the Debian Bug report #796516,
regarding ruby-mysql2: FTBFS: Mysql2::Error returns error messages and sql 
state in Encoding.default_internal if set
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.)


-- 
796516: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=796516
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: ruby-mysql2
Version: 0.3.18-1
Severity: serious
Justification: fails to build from source
User: reproducible-bui...@lists.alioth.debian.org
Usertags: ftbfs
X-Debbugs-Cc: reproducible-bui...@lists.alioth.debian.org

Dear Maintainer,

ruby-mysql2 fails to build from source in unstable/amd64:

  [..]
  
  
┌──┐
  │ Run tests for ruby2.2 from debian/ruby-tests.rake   
  │
  
└──┘
  
  
RUBYLIB=/tmp/buildd/ruby-mysql2-0.3.18/debian/ruby-mysql2/usr/lib/x86_64-linux-gnu/ruby/vendor_ruby/2.2.0:/tmp/buildd/ruby-mysql2-0.3.18/debian/ruby-mysql2/usr/lib/ruby/vendor_ruby:.
  rake2.2 -f debian/ruby-tests.rake
  /usr/bin/ruby2.2 /usr/bin/rspec --pattern
  ./spec/mysql2/\*\*/\*_spec.rb
  
*..F.
  
  Pending: (Failures listed here are expected and do not affect your
  suite's status)
  
1) Mysql2::Client should be able to connect via SSL options
   # DON'T WORRY, THIS TEST PASSES - but SSL is not enabled in your
   MySQL daemon.
   Failure/Error: expect(results[0]['Value']).not_to be_empty
 expected `"".empty?` to return false, got true
   # ./spec/mysql2/client_spec.rb:145:in `block (2 levels) in '
  
  Failures:
  
1) Mysql2::Error returns error messages and sql state in
Encoding.default_internal if set
   Failure/Error: client.query("\xE9\x80\xA0\xE5\xAD\x97")
   SystemStackError:
 stack level too deep
   # ./lib/mysql2/error.rb:59:in `encode'
   # ./lib/mysql2/error.rb:59:in `clean_message'
   # ./lib/mysql2/error.rb:19:in `initialize'
   # ./spec/mysql2/error_spec.rb:33:in `new'
   # ./spec/mysql2/error_spec.rb:33:in `query'
   # ./spec/mysql2/error_spec.rb:33:in `block (2 levels) in '
   # ./spec/mysql2/error_spec.rb:75:in `block (3 levels) in '
   # ./spec/spec_helper.rb:14:in `with_internal_encoding'
   # ./spec/mysql2/error_spec.rb:74:in `block (2 levels) in '
  
  Finished in 14.71 seconds (files took 0.58277 seconds to load)
  181 examples, 1 failure, 1 pending
  
  Failed examples:
  
  rspec ./spec/mysql2/error_spec.rb:73 # Mysql2::Error returns error
  messages and sql state in Encoding.default_internal if set
  
  /usr/bin/ruby2.2 /usr/bin/rspec --pattern
  ./spec/mysql2/\*\*/\*_spec.rb failed
  ERROR: Test "ruby2.2" failed. Exiting.
  dh_auto_install: dh_ruby --install
  /tmp/buildd/ruby-mysql2-0.3.18/debian/ruby-mysql2 returned exit code 1
  2015-08-21 05:04:41 18930 [Note] /usr/sbin/mysqld: Normal shutdown
  
  2015-08-21 05:04:41 18930 [Note] Giving 0 client threads a chance to
  die gracefully
  2015-08-21 05:04:41 18930 [Note] Event Scheduler: Purging the queue. 0
  events
  2015-08-21 05:04:41 18930 [Note] Shutting down slave threads
  2015-08-21 05:04:41 18930 [Note] Forcefully disconnecting 0 remaining
  clients
  2015-08-21 05:04:41 18930 [Note] Binlog end
  2015-08-21 05:04:41 18930 [Note] Shutting down plugin 'partition'
  2015-08-21 05:04:41 18930 [Note] Shutting down plugin 'ARCHIVE'
  2015-08-21 05:04:41 18930 [Note] Shutting down plugin
  'INNODB_SYS_DATAFILES'
  2015-08-21 05:04:41 18930 [Note] Shutting down plugin
  'INNODB_SYS_TABLESPACES'
  2015-08-21 05:04:41 18930 [Note] Shutting down plugin
  'INNODB_SYS_FOREIGN_COLS'
  2015-08-21 05:04:41 18930 [Note] Shutting down plugin
  'INNODB_SYS_FOREIGN'
  2015-08-21 05:04:41 18930 [Note] Shutting down plugin
  'INNODB_SYS_FIELDS'
  2015-08-21 05:04:41 18930 [Note] Shutting down plugin
  'INNODB_SYS_COLUMNS'
  2015-08-21 05:04:41 18930 [Note] Shutting down plugin
  'INNODB_SYS_INDEXES'
  2015-08-21 05:04:41 18930 [Note] Shutting down plugin
  'INNODB_SYS_TABLESTATS'
  2015-08-21 05:04:41 18930 [Note] Shutting down plugin
  'INNODB_SYS_TABLES'
  2015-08-21 05:04:41 18930 [Note] Shutting down plugin
  

Bug#794477: marked as done (ruby-mysql2: Unversioned dependency on libmysqlclient18 leads to unusable package in testing)

[Debian Bug Tracking System]

Your message dated Thu, 25 Feb 2016 16:30:37 +
with message-id 
and subject line Bug#794477: fixed in ruby-mysql2 0.4.3-1
has caused the Debian Bug report #794477,
regarding ruby-mysql2: Unversioned dependency on libmysqlclient18 leads to 
unusable package in testing
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.)


-- 
794477: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=794477
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: ruby-mysql2
Version: 0.3.18-1
Severity: important

The contents of the ruby-mysql2 package effectively have a versioned
dependency on libmysqlclient18, but the package itself does not specify a
version dependency.

This leads to the current version of ruby-mysql2 in testing being unusable
until the new version of mysql migrates to testing.  Witness:

Setting up redmine (3.0~20140825-8) ...
Populating database for redmine instance "default".
This may take a while.
rake aborted!
Incorrect MySQL client library version! This gem was compiled for 5.6.25 but
the client library is 5.5.43.

If the ruby library is going to complain about the mysql library version,
seems the package dependencies should reflect that.

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

Kernel: Linux 3.16.0-4-amd64 (SMP w/12 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages ruby-mysql2 depends on:
ii  libc6  2.19-19
ii  libgmp10   2:6.0.0+dfsg-7
ii  libmysqlclient18   5.5.43-0+deb8u1
ii  libruby2.1 2.1.5-3
ii  ruby   1:2.1.5.1
ii  ruby-eventmachine  1.0.7-3
ii  zlib1g 1:1.2.8.dfsg-2+b1

ruby-mysql2 recommends no packages.

ruby-mysql2 suggests no packages.

-- no debconf information
--- End Message ---
--- Begin Message ---
Source: ruby-mysql2
Source-Version: 0.4.3-1

We believe that the bug you reported is fixed in the latest version of
ruby-mysql2, 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 794...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Antonio Terceiro  (supplier of updated ruby-mysql2 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: Thu, 25 Feb 2016 12:01:39 -0300
Source: ruby-mysql2
Binary: ruby-mysql2
Architecture: source
Version: 0.4.3-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Ruby Extras Maintainers 

Changed-By: Antonio Terceiro 
Description:
 ruby-mysql2 - simple, fast MySQL library for Ruby
Closes: 794477 796516 815770
Changes:
 ruby-mysql2 (0.4.3-1) unstable; urgency=medium
 .
   * Team upload
 .
   [ Christian Hofstaedtler ]
   * Imported Upstream version 0.4.2
   * Drop upstream applied patches
   * Refresh local patches
   * Bump Standard-Version to 3.9.6
 .
   [ Antonio Terceiro ]
   * Imported Upstream version 0.4.3
   * rename debian/start_mysqld_and_auto_install.sh to
 debian/start_mysqld_and_run.sh and make it generic; adapt all in
 debian/rules accordingly.
   * Move logic for calling debian/start_mysqld_and_run.sh for running the
 tests inside debian/ruby-tests.rake
   * Add skip-problematic-tests.patch to skip 2 tests (Closes: #815770, #796516)
   * Add trust-library-ABI.patch: skip check for exact versions of the MySQL
 client library (Closes: #794477)
   * Update packaging with a new dh-make-ruby run
 - bump debhelper compatibility level from 7 to 9
 - switch Vcs-* to https URLs
 - cleanup debian/rules
Checksums-Sha1:
 810171de8cdd2ac2bc0ba4db8a71206e0ba57e85 2119 ruby-mysql2_0.4.3-1.dsc
 b136b02fdafaac56396f13fdd188360e454a5188 70899 ruby-mysql2_0.4.3.orig.tar.gz
 1bf5f9426bde205593fe4fe123033364fd09c166 6208 ruby-mysql2_0.4.3-1.debian.tar.xz
Checksums-Sha256:
 39159522c8c14782b7a8c161bd534a97318c9409c549e9b6e8e077970747bb8d 2119 
ruby-mysql2_0.4.3-1.dsc
 

Processed: tagging 808692

[Debian Bug Tracking System]

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

> tags 808692 + pending
Bug #808692 [src:watchdog] watchdog: FTBFS: dpkg-genbuildinfo: error: cannot 
fstat file ../watchdog-dbgsym_5.14-3_amd64.deb: No such file or directory
Added tag(s) pending.
> thanks
Stopping processing here.

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

Processed: severity of 815886 is serious, merging 815886 814526

[Debian Bug Tracking System]

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

> severity 815886 serious
Bug #815886 [plasma-desktop-data] plasma-desktop-data: conflight with 
kde-l10n-engb
Bug #814526 [plasma-desktop-data] plasma-desktop-data: fails to upgrade from 
'sid' - trying to overwrite 
/usr/share/locale/*/LC_MESSAGES/kcm_device_automounter.mo
Ignoring request to change severity of Bug 815886 to the same value.
Ignoring request to change severity of Bug 814526 to the same value.
> merge 815886 814526
Bug #815886 [plasma-desktop-data] plasma-desktop-data: conflight with 
kde-l10n-engb
Bug #814526 [plasma-desktop-data] plasma-desktop-data: fails to upgrade from 
'sid' - trying to overwrite 
/usr/share/locale/*/LC_MESSAGES/kcm_device_automounter.mo
Bug #814526 [plasma-desktop-data] plasma-desktop-data: fails to upgrade from 
'sid' - trying to overwrite 
/usr/share/locale/*/LC_MESSAGES/kcm_device_automounter.mo
Merged 814526 815886
> thanks
Stopping processing here.

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

Bug#815908: ruby-github-linguist: FTBFS: install: cannot stat '[..]/ruby-github-linguist-4.7.2/bin/linguist': No such file or directory

[Chris Lamb]

Source: ruby-github-linguist
Version: 4.7.2-1
Severity: serious
Justification: fails to build from source
User: reproducible-bui...@lists.alioth.debian.org
Usertags: ftbfs
X-Debbugs-Cc: reproducible-bui...@lists.alioth.debian.org

Dear Maintainer,

ruby-github-linguist fails to build from source in unstable/amd64:

  [..]


 dh_auto_install -O--buildsystem=ruby
dh_ruby --install 
/home/lamby/temp/cdt.20160225150719.LlpPnpiK8v/ruby-github-linguist-4.7.2/debian/ruby-github-linguist
 dh_ruby --install
  
  
┌──────────────────────────────────────────────────────────────────────────────â”
  │ Install files 
   │
  
└──────────────────────────────────────────────────────────────────────────────┘
  
  install -d 
/home/lamby/temp/cdt.20160225150719.LlpPnpiK8v/ruby-github-linguist-4.7.2/debian/ruby-github-linguist/usr/bin
  install -D -m755 
/home/lamby/temp/cdt.20160225150719.LlpPnpiK8v/ruby-github-linguist-4.7.2/bin/linguist
 
/home/lamby/temp/cdt.20160225150719.LlpPnpiK8v/ruby-github-linguist-4.7.2/debian/ruby-github-linguist/usr/bin/linguist
  install: cannot stat 
'/home/lamby/temp/cdt.20160225150719.LlpPnpiK8v/ruby-github-linguist-4.7.2/bin/linguist':
 No such file or directory
  /usr/lib/ruby/vendor_ruby/gem2deb.rb:56:in `run': install -D -m755 
/home/lamby/temp/cdt.20160225150719.LlpPnpiK8v/ruby-github-linguist-4.7.2/bin/linguist
 
/home/lamby/temp/cdt.20160225150719.LlpPnpiK8v/ruby-github-linguist-4.7.2/debian/ruby-github-linguist/usr/bin/linguist
 (Gem2Deb::CommandFailed)
from /usr/lib/ruby/vendor_ruby/gem2deb/installer.rb:172:in `block in 
install_files'
from /usr/lib/ruby/vendor_ruby/gem2deb/installer.rb:169:in `each'
from /usr/lib/ruby/vendor_ruby/gem2deb/installer.rb:169:in 
`install_files'
from /usr/lib/ruby/vendor_ruby/gem2deb/installer.rb:30:in 
`install_files_and_build_extensions'
from /usr/lib/ruby/vendor_ruby/gem2deb/dh_ruby.rb:84:in `block in 
install'
from /usr/lib/ruby/vendor_ruby/gem2deb/dh_ruby.rb:82:in `each'
from /usr/lib/ruby/vendor_ruby/gem2deb/dh_ruby.rb:82:in `install'
from /usr/bin/dh_ruby:94:in `'
  dh_auto_install: dh_ruby --install 
/home/lamby/temp/cdt.20160225150719.LlpPnpiK8v/ruby-github-linguist-4.7.2/debian/ruby-github-linguist
 returned exit code 1
  debian/rules:16: recipe for target 'binary' failed
  make: *** [binary] Error 1

  [..]

The full build log is attached.


Regards,

-- 
  ,''`.
 : :'  : Chris Lamb
 `. `'`  la...@debian.org / chris-lamb.co.uk
   `-


ruby-github-linguist.4.7.2-1.unstable.amd64.log.txt.gz
Description: Binary data

Processed: Re: Bug#762133: fixed in ruby-kakasi-ffi 1.0.2-1

[Debian Bug Tracking System]

Processing control commands:

> reopen -1
Bug #815769 {Done: Christian Hofstaedtler } 
[src:ruby-kakasi-ffi] ruby-kakasi-ffi: FTBFS against ruby2.3
Bug #762133 {Done: Christian Hofstaedtler } 
[src:ruby-kakasi-ffi] ruby-kakasi-ffi: FTBFS: can't load libkakasi.so 
(DL::DLError)
'reopen' may be inappropriate when a bug has been closed with a version;
all fixed versions will be cleared, and you may need to re-add them.
Bug reopened
No longer marked as fixed in versions ruby-kakasi-ffi/1.0.2-1.
No longer marked as fixed in versions ruby-kakasi-ffi/1.0.2-1.

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

Bug#815769: Bug#762133: fixed in ruby-kakasi-ffi 1.0.2-1

[Antonio Terceiro]

make[1]: Nothing to be done for 'install'.
make[1]: Leaving directory '/<>/ext/kakasi-config'
Building has failed. See above output for more information on the failure.
rmdir 
/<>/debian/ruby-kakasi-ffi/usr/lib/x86_64-linux-gnu/ruby/vendor_ruby/2.2.0

┌──┐
│ Build native extensions for ruby2.3  │
└──┘

/usr/bin/ruby2.3 /usr/lib/ruby/vendor_ruby/gem2deb/extension_builder.rb 
/<> debian/ruby-kakasi-ffi
"make clean"
make[1]: Entering directory '/<>/ext/kakasi-config'
make[1]: *** No rule to make target 'clean'.  Stop.
make[1]: Leaving directory '/<>/ext/kakasi-config'
/usr/lib/ruby/vendor_ruby/gem2deb.rb:56:in `run': "make clean" 
(Gem2Deb::CommandFailed)
from /usr/lib/ruby/vendor_ruby/gem2deb/extension_builder.rb:38:in 
`block in clean'
from /usr/lib/ruby/vendor_ruby/gem2deb/extension_builder.rb:36:in 
`chdir'
from /usr/lib/ruby/vendor_ruby/gem2deb/extension_builder.rb:36:in 
`clean'
from /usr/lib/ruby/vendor_ruby/gem2deb/extension_builder.rb:102:in 
`block in build_all_extensions'
from /usr/lib/ruby/vendor_ruby/gem2deb/extension_builder.rb:100:in 
`each'
from /usr/lib/ruby/vendor_ruby/gem2deb/extension_builder.rb:100:in 
`build_all_extensions'
from /usr/lib/ruby/vendor_ruby/gem2deb/extension_builder.rb:116:in 
`'
/usr/lib/ruby/vendor_ruby/gem2deb.rb:56:in `run': /usr/bin/ruby2.3 
/usr/lib/ruby/vendor_ruby/gem2deb/extension_builder.rb /<> 
debian/ruby-kakasi-ffi (Gem2Deb::CommandFailed)
from /usr/lib/ruby/vendor_ruby/gem2deb.rb:67:in `run_ruby'
from /usr/lib/ruby/vendor_ruby/gem2deb/installer.rb:37:in `block in 
install_files_and_build_extensions'
from /usr/lib/ruby/vendor_ruby/gem2deb/installer.rb:34:in `each'
from /usr/lib/ruby/vendor_ruby/gem2deb/installer.rb:34:in 
`install_files_and_build_extensions'
from /usr/lib/ruby/vendor_ruby/gem2deb/dh_ruby.rb:84:in `block in 
install'
from /usr/lib/ruby/vendor_ruby/gem2deb/dh_ruby.rb:82:in `each'
from /usr/lib/ruby/vendor_ruby/gem2deb/dh_ruby.rb:82:in `install'
from /usr/bin/dh_ruby:94:in `'
dh_auto_install: dh_ruby --install /<>/debian/ruby-kakasi-ffi 
returned exit code 1
debian/rules:6: recipe for target 'binary' failed
make: *** [binary] Error 1
dpkg-buildpackage: error: fakeroot debian/rules binary gave error exit status 2

Build finished at 20160225-1226

Finished


E: Build failure (dpkg-buildpackage died)

+--+
| Cleanup  |
+--+

Purging /<>
Not cleaning session: cloned chroot in use

+--+
| Summary  |
+--+

Build Architecture: amd64
Build-Space: 264
Build-Time: 3
Distribution: unstable
Fail-Stage: build
Host Architecture: amd64
Install-Time: 26
Job: /tmp/ruby-kakasi-ffi_1.0.2-1.dsc
Machine Architecture: amd64
Package: ruby-kakasi-ffi
Package-Time: 34
Source-Version: 1.0.2-1
Space: 264
Status: attempted
Version: 1.0.2-1

Finished at 20160225-1226
Build needed 00:00:34, 264k disc space


signature.asc
Description: PGP signature

Processed: fixed 815907 in 3.1.1-3+deb7u2, fixed 815907 in 3.1.1-5.1+deb8u1

[Debian Bug Tracking System]

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

> fixed 815907 3.1.1-3+deb7u2
Bug #815907 [src:xerces-c] xerces-c: CVE-2016-0729
The source 'xerces-c' and version '3.1.1-3+deb7u2' do not appear to match any 
binary packages
Marked as fixed in versions xerces-c/3.1.1-3+deb7u2.
> fixed 815907 3.1.1-5.1+deb8u1
Bug #815907 [src:xerces-c] xerces-c: CVE-2016-0729
The source 'xerces-c' and version '3.1.1-5.1+deb8u1' do not appear to match any 
binary packages
Marked as fixed in versions xerces-c/3.1.1-5.1+deb8u1.
> thanks
Stopping processing here.

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

Bug#815004: libengine-pkcs11-openssl: Engine is installed at wrong location (sparc64 as well)

[Anatoly Pugachev]

Package: libengine-pkcs11-openssl
Version: 0.2.1-1
Followup-For: Bug #815004

Dear Maintainer,


sparc64 as well

mator@deb4g:~$ openssl speed rsa2048 -engine pkcs11
invalid engine "pkcs11"
1892278191086752:error:25066067:DSO support routines:DLFCN_LOAD:could not 
load the shared 
library:dso_dlfcn.c:187:filename(/usr/lib/sparc64-linux-gnu/openssl-1.0.2/engines/libpkcs11.so):
 /usr/lib/sparc64-linux-gnu/openssl-1.0.2/engines/libpkcs11.so: cannot open 
shared object file: No such file or directory
1892278191086752:error:25070067:DSO support routines:DSO_load:could not 
load the shared library:dso_lib.c:232:
1892278191086752:error:260B6084:engine routines:DYNAMIC_LOAD:dso not 
found:eng_dyn.c:465:
1892278191086752:error:2606A074:engine routines:ENGINE_by_id:no such 
engine:eng_list.c:390:id=pkcs11
1892278191086752:error:25066067:DSO support routines:DLFCN_LOAD:could not 
load the shared library:dso_dlfcn.c:187:filename(libpkcs11.so): libpkcs11.so: 
cannot open shared object file: No such file or directory
1892278191086752:error:25070067:DSO support routines:DSO_load:could not 
load the shared library:dso_lib.c:232:
1892278191086752:error:260B6084:engine routines:DYNAMIC_LOAD:dso not 
found:eng_dyn.c:465:
Doing 2048 bit private rsa's for 10s: 12688 2048 bit private RSA's in 10.00s


mator@deb4g:~$ dpkg -L libengine-pkcs11-openssl | grep libpkcs11.so
/usr/lib/ssl/engines/libpkcs11.so

-- System Information:
Debian Release: stretch/sid
  APT prefers unreleased
  APT policy: (500, 'unreleased'), (500, 'unstable')
Architecture: sparc64

Kernel: Linux 4.4.0-trunk-sparc64-smp (SMP w/1 CPU core)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages libengine-pkcs11-openssl depends on:
ii  libc62.21-9
ii  libp11-2 0.3.1-1
ii  libssl1.0.2  1.0.2f-2

libengine-pkcs11-openssl recommends no packages.

libengine-pkcs11-openssl suggests no packages.

-- no debconf information

Bug#814639: noweb: unowned file /usr/local/share/texmf/ls-R after purge (policy 6.8, 9.1.2)

[Hubert Chathi]

On Sat, 13 Feb 2016 17:15:40 +0100, Andreas Beckmann  said:

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

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

Thank you for the bug report.  I've prepared version 2.11b-10 which
fixes this bug (along with another (minor) bug).  Unfortunately, I don't
have a valid key in the keyring (due to my 1024D being too weak, and not
being able to get my new key signed).  If you are willing to sponsor my
upload, the packages are available at
https://debian.uhoreg.ca/experimental/noweb/.  Otherwise, I will try to
find another sponsor.

-- 
Hubert Chathi  -- Jabber: hub...@uhoreg.ca
PGP/GnuPG key: 4096R/113A1368 https://www.uhoreg.ca/
Fingerprint: F24C F749 6C73 DDB8 DCB8  72DE B2DE 88D3 113A 1368

Bug#815731: arandr: Doesn't work with the current version of xrandr

[Julien Cristau]

On Thu, Feb 25, 2016 at 08:59:13 +0100, chrysn wrote:

> version 0.1.9 that fixes this is released, i'm just waiting for sponsor
> review for 0.1.9-1 to hit the archive. a "Breaks: arandr (<< 0.1.9)"
> would avoid creating broken systems in testing. (afaik it wouldn't
> impede testing migration, but only make arandr uninstallable for a few
> days at most in testing).
> 
It will very much impede testing migration.  The whole point of the
testing migration script is to keep packages in testing installable.

I'll add the Breaks.

> as for further coordination, i have lost touch with xrandr devs a bit;
> is there any more official announcement to xrandr releases apart from
> tags on the git repo these days?
> 
https://lists.x.org/pipermail/xorg-announce/2016-February/002677.html

Cheers,
Julien

Bug#815907: xerces-c: CVE-2016-0729

[Salvatore Bonaccorso]

Source: xerces-c
Version: 3.1.1-1
Severity: grave
Tags: security upstream patch fixed-upstream

Hi,

the following vulnerability was published for xerces-c.

CVE-2016-0729[0]:
Apache Xerces-C XML Parser Crashes on Malformed Input

If you fix the vulnerability please also make sure to include the
CVE (Common Vulnerabilities & Exposures) id in your changelog entry.

For further information see:

[0] https://security-tracker.debian.org/tracker/CVE-2016-0729
[1] http://svn.apache.org/viewvc?view=revision=1727978

Regards,
Salvatore

Bug#815154: gnome-control-center removes XKBMODEL and XKBOPTIONS from /etc/default/keyboard

[Felipe Sateler]

On 23 February 2016 at 13:41, Anton Zinoviev  wrote:
> On Tue, Feb 23, 2016 at 11:51:35AM -0300, Felipe Sateler wrote:
>> On 19 February 2016 at 14:52, Anton Zinoviev  wrote:
>> >
>> > XKBMODEL has no default value (at least in console-setup).  It should 
>> > always be
>> > present and never as empty value.
>
> Thanks to this discussion, now I think it will be a good idea for 
> console-setup
> to compute some default XKBMODEL.
>
>> This is not what keyboard(5) says:
>>
>>
>> XKBMODEL
>>  Specifies the XKB keyboard model name.  Default: pc105 for  most
>>  platforms.
>
> Thank you.  I acknowledge that this is a bug in the documentation.  I will 
> have
> to rewrite this man-page so that it becomes clearer which parts in it are
> software independent and which are related specificly to console-setup.

Great that we find agreement :)

>
>> On 20 February 2016 at 11:02, Anton Zinoviev  wrote:
>> > In case it is difficult to preserve the existing value, you can use 
>> > 'pc105' as a
>> > default value.  Alternatively, the following table with default values can 
>> > be
>> > used:
>> >
>> > Architecture  Subarchitecture Model
>> > ---
>> > m68k  atari   ataritt
>> > m68k  mac macintosh_old
>> > m68k  Other   pc105
>> > powerpc   amiga   amiga
>> > powerpc   Other   pc105
>> > Other pc105
>>
>> Maybe console-setup should encode this table itself, so that the
>> documentation becomes correct.
>
> In fact, console-setup can compute default XKBMODEL if one is missing.  If the
> file /etc/default/keyboard becomes corrupt, then this will be corrected when 
> the
> package is upgraded (or the user uses dpkg-reconfigure).
>
> The reason no such logic exists in /bin/setupcon (the script used to actually
> configure the console) is that the script setupcon can be used on any Linux or
> FreeBSD variety (not just Debian) and I don't know how to implement a table 
> like
> this in a distribution independent way.  Therefore, all such logic is encoded 
> in
> the package scripts (mostly debconf config and postinst).

I agree that a non-trivial if (Debian) { /* guess xkbmodel */ } feels
hackish. But the architecture can be obtained via uname which should
be quite portable, and the subarchitecture you have already posted a
script to detect in the necessary cases. Alternatively, the maintainer
scripts could preseed the value into /var/lib/console-setup or some
other private directory, and have setupcon try to read that when
XKBMODEL is not set. Then other OSes can preseed the file in the
manner most appropriate for them.

>  Even if I include such
> a logic in setupcon, it will be somewhat primitive, so a warning to the user 
> will
> have to be issued when XKBMODEL is missing.

This may be a good idea.

-- 

Saludos,
Felipe Sateler

Bug#815906: postfix: upgrade to 3.0.4-3 breaks

[Thorsten Glaser]

Package: postfix
Version: 3.0.4-3
Severity: serious
Justification: does not install

──
Preparing to unpack .../postfix_3.0.4-3_amd64.deb ...
Stopping Postfix Mail Transport Agent: postfixpostfix: Postfix is running with 
backwards-compatible default settings
postfix: See http://www.postfix.org/COMPATIBILITY_README.html for details
postfix: To disable backwards compatibility use "postconf 
compatibility_level=2" and "postfix reload"
.
Stopping Postfix Mail Transport Agent: postfix.
Unpacking postfix (3.0.4-3) over (3.0.4-1) ...
[…]
Setting up postfix (3.0.4-3) ...
Installing new version of config file /etc/init.d/postfix ...

Postfix configuration was not changed.  If you need to make changes, edit
/etc/postfix/main.cf (and others) as needed.  To view Postfix configuration
values, see postconf(1).

After modifying main.cf, be sure to run '/etc/init.d/postfix reload'.

Running newaliases
Stopping Postfix Mail Transport Agent: postfix.
Starting Postfix Mail Transport Agent: postfixcp: cannot overwrite directory 
'/var/spool/postfix/etc/ssl/godaddy.ca' with non-directory
invoke-rc.d: initscript postfix, action "restart" failed.
dpkg: error processing package postfix (--configure):
 subprocess installed post-installation script returned error exit status 1
──

What I’d like to know is why it duplicates /etc/ssl there, and badly?

In case this helps:

tglase@tglase-nb:~ $ ll -a /etc/ssl 

total 80
drwxr-xr-x   4 root root  4096 Feb 24 10:51 ./
drwxr-xr-x 181 root root 12288 Feb 25 15:25 ../
-rw-r--r--   1 root ssl-cert   169 May 27  2011 W_lan_tarent_de.apa
-rw-r--r--   1 root ssl-cert  2664 Jun 11  2015 W_lan_tarent_de.cer
drwxr-xr-x   3 root root 28672 Feb 12 16:59 certs/
-rw-r--r--   1 root ssl-cert  1749 Apr  8  2014 godaddy.ca
-rw-r--r--   1 root root 10835 Jun  6  2012 openssl.cnf
drwx--s---   2 root ssl-cert  4096 Feb 24 10:52 private/
-r--r--r--   1 root root  2212 Apr 17  2010 startcom.ca


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

Kernel: Linux 4.4.0-1-amd64 (SMP w/2 CPU cores)
Locale: LANG=C, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/lksh
Init: sysvinit (via /sbin/init)

Versions of packages postfix depends on:
ii  adduser3.113+nmu3
ii  cpio   2.11+dfsg-5
ii  debconf [debconf-2.0]  1.5.58
ii  dpkg   1.18.4
ii  libc6  2.21-9
ii  libdb5.3   5.3.28-11
ii  libicu55   55.1-7
ii  libsasl2-2 2.1.26.dfsg1-14+b1
ii  libsqlite3-0   3.11.0-2
ii  libssl1.0.21.0.2f-2
ii  lsb-base   9.20160110
ii  netbase5.3
ii  ssl-cert   1.0.37

Versions of packages postfix recommends:
ii  python3  3.5.1-2

Versions of packages postfix suggests:
ii  bsd-mailx [mail-reader]  8.1.2-0.20160123cvs-2
pn  dovecot-common   
ii  kmail [mail-reader]  4:4.14.10-2
ii  libsasl2-modules 2.1.26.dfsg1-14+b1
pn  postfix-cdb  
pn  postfix-doc  
pn  postfix-ldap 
pn  postfix-mysql
pn  postfix-pcre 
pn  postfix-pgsql
pn  procmail 
pn  resolvconf   
pn  sasl2-bin
pn  ufw  

-- debconf information:
* postfix/mynetworks: 127.0.0.0/8 [:::127.0.0.0]/104 [::1]/128
* postfix/mailname: tglase-nb.lan.tarent.de
* postfix/dynamicmaps_conversion_warning: true
* postfix/recipient_delim: +
* postfix/procmail: false
* postfix/chattr: false
* postfix/protocols: all
* postfix/destinations: tglase-nb.lan.tarent.de
  postfix/kernel_version_warning:
  postfix/bad_recipient_delimiter:
  postfix/retry_upgrade_warning:
* postfix/root_address: tg
* postfix/mailbox_limit: 0
  postfix/sqlite_warning:
  postfix/mydomain_warning:
  postfix/not_configured:
  postfix/relay_restrictions_warning:
  postfix/rfc1035_violation: false
* postfix/main_mailer_type: Internet Site
  postfix/tlsmgr_upgrade_warning:
  postfix/relayhost:

Bug#815814: urdfdom: FTBFS on several architectures

[Jochen Sprickerhof]

Package: src:urdfdom
Followup-For: Bug #815814

Hi,

I've looked into this and the bug is actually in urdfdom-headers-dev. It's
/usr/share/urdfdom_headers/cmake/urdfdom_headers-config-version.cmake installs
arch:all but has a arch dependent check at the bottom:

> # check that the installed version has the same 32/64bit-ness as the one 
> which is currently searching:
> if(NOT CMAKE_SIZEOF_VOID_P STREQUAL "8")
>   math(EXPR installedBits "8 * 8")
>   set(PACKAGE_VERSION "${PACKAGE_VERSION} (${installedBits}bit)")
>   set(PACKAGE_VERSION_UNSUITABLE TRUE)
> endif()

which is instantiated from
/usr/share/cmake-3.4/Modules/BasicConfigVersion-AnyNewerVersion.cmake.in (in
cmake-data) through write_basic_package_version_file().

So we can either make all packages using this arch dependent, or fix the cmake
template. Any opinions?

Cheers Jochen


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

Kernel: Linux 4.3.0-1-amd64 (SMP w/12 CPU cores)
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: sysvinit (via /sbin/init)

Bug#808738: closed by Pirate Praveen <prav...@debian.org> (Bug#808738: fixed in ruby-sinatra 1.4.7-1)

[Chris Lamb]

> > >- Specify available locales during testing (Closes: #808738)
> > 
> > Is this due to /missing/ locales or the "wrong" locale?
> > 
> > If the latter, then whatever the failing test, that functionality is
> > going to fail for users at runtime who aren't using that particular
> > locale!
> 
> the issue is caused by some setup that needs to be done by applications
> when using the i18n library, that was not mandatory before ruby-i18n
> 0.7.

Great :)  Thanks for looking into this.


Regards,

-- 
  ,''`.
 : :'  : Chris Lamb
 `. `'`  la...@debian.org / chris-lamb.co.uk
   `-

Bug#815397: marked as done (r-cran-tm: FTBFS: ERROR: dependencies 'NLP', 'slam' are not available for package 'tm')

[Debian Bug Tracking System]

Your message dated Thu, 25 Feb 2016 13:58:46 +
with message-id 
and subject line Bug#815373: fixed in r-cran-tm 0.6-2-2
has caused the Debian Bug report #815373,
regarding r-cran-tm: FTBFS: ERROR: dependencies 'NLP', 'slam' are not available 
for package 'tm'
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.)


-- 
815373: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=815373
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: r-cran-tm
Version: 0.6-2-1
Severity: serious
Justification: fails to build from source
User: reproducible-bui...@lists.alioth.debian.org
Usertags: ftbfs
X-Debbugs-Cc: reproducible-bui...@lists.alioth.debian.org

Dear Maintainer,

r-cran-tm fails to build from source in unstable/amd64:

  [..]

  echo "R:Depends=r-base-core (>= 3.2.3-6), r-api-3" >> 
debian/r-cran-tm.substvars
  if test -f /usr/bin/xvfb-run; then\
 xvfb-run -a\
R CMD INSTALL -l 
/home/lamby/temp/cdt.20160221091835.7kRrMoa2Ut/r-cran-tm-0.6-2/debian/r-cran-tm/usr/lib/R/site-library
 --clean \
 .  \
"--built-timestamp=\"Thu, 18 Feb 2016 21:43:55 
+0100\"" \
;   \
else\
 R CMD INSTALL -l 
/home/lamby/temp/cdt.20160221091835.7kRrMoa2Ut/r-cran-tm-0.6-2/debian/r-cran-tm/usr/lib/R/site-library
\
--clean  .  \
"--built-timestamp=\"Thu, 18 Feb 2016 21:43:55 
+0100\"" \
;   \
fi
  ERROR: dependencies 'NLP', 'slam' are not available for package 'tm'
  * removing 
'/home/lamby/temp/cdt.20160221091835.7kRrMoa2Ut/r-cran-tm-0.6-2/debian/r-cran-tm/usr/lib/R/site-library/tm'
  /usr/share/R/debian/r-cran.mk:98: recipe for target 'R_any_arch' failed
  make: *** [R_any_arch] Error 1

  [..]

The full build log is attached.


Regards,

-- 
  ,''`.
 : :'  : Chris Lamb
 `. `'`  la...@debian.org / chris-lamb.co.uk
   `-


r-cran-tm.0.6-2-1.unstable.amd64.log.txt.gz
Description: Binary data
--- End Message ---
--- Begin Message ---
Source: r-cran-tm
Source-Version: 0.6-2-2

We believe that the bug you reported is fixed in the latest version of
r-cran-tm, 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 815...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Daniel Pocock  (supplier of updated r-cran-tm 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: Thu, 25 Feb 2016 10:24:39 +0100
Source: r-cran-tm
Binary: r-cran-tm
Architecture: source amd64
Version: 0.6-2-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Science Team 

Changed-By: Daniel Pocock 
Description:
 r-cran-tm  - Text Mining functionality for R
Closes: 815373
Changes:
 r-cran-tm (0.6-2-2) unstable; urgency=medium
 .
   * Add more build dependencies. (Closes: #815373)
Checksums-Sha1:
 7edeb196162d6cb88490faaf16c81a448927a8d8 1998 r-cran-tm_0.6-2-2.dsc
 862e5e96bfc5c2af865d89153c0f7c870dec644f 12200 r-cran-tm_0.6-2-2.debian.tar.xz
 f78aa33c405523e23b4e8e5aed4027e3c236b65f 3514 
r-cran-tm-dbgsym_0.6-2-2_amd64.deb
 98f3298eb2cda775834b24094ffcf0abc0126838 647248 r-cran-tm_0.6-2-2_amd64.deb
Checksums-Sha256:
 27356c89a3280e5fbe29993dbcac9565aa8a1624e48c9f18b0dc6c4f0f976ee5 1998 
r-cran-tm_0.6-2-2.dsc
 a41c300ba0f0632fb95b5f3895c16695ef3db2de64c965328b68bc55448dc62b 12200 
r-cran-tm_0.6-2-2.debian.tar.xz
 d9ca0d9afa205e48e8d60e38c10f4cee7446cd22be1b92426584d8a455a014a9 3514 
r-cran-tm-dbgsym_0.6-2-2_amd64.deb
 789505822a24752e81ffa761f13389350f8d1cff22dcf92ae4ea832430cad8d8 647248 
r-cran-tm_0.6-2-2_amd64.deb
Files:
 4f1a81ece60436367ea6801bdff8c8f6 1998 gnu-r optional r-cran-tm_0.6-2-2.dsc
 c9d035000cc48466b9fa33426fa27bbf 12200 gnu-r optional 

Bug#815373: marked as done (r-cran-tm: FTBFS: dependencies 'NLP', 'slam' are not available)

[Debian Bug Tracking System]

Your message dated Thu, 25 Feb 2016 13:58:46 +
with message-id 
and subject line Bug#815373: fixed in r-cran-tm 0.6-2-2
has caused the Debian Bug report #815373,
regarding r-cran-tm: FTBFS: dependencies 'NLP', 'slam' are not available
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.)


-- 
815373: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=815373
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: r-cran-tm
Version: 0.6.2-1
Severity: serious
Justification: fails to build from source

Hi, Daniel.

Builds of r-cran-tm in minimal environments (notably, on the
autobuilders) have been failing:

  ERROR: dependencies 'NLP', 'slam' are not available for package 'tm'
  * removing '/«PKGBUILDDIR»/debian/r-cran-tm/usr/lib/R/site-library/tm'
  /usr/share/R/debian/r-cran.mk:98: recipe for target 'R_any_arch' failed
  make: *** [R_any_arch] Error 1

Please declare build dependencies on r-cran-nlp and r-cran-slam, and
confirm with pbuilder or the like that you haven't missed any others.

Thanks!
--- End Message ---
--- Begin Message ---
Source: r-cran-tm
Source-Version: 0.6-2-2

We believe that the bug you reported is fixed in the latest version of
r-cran-tm, 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 815...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Daniel Pocock  (supplier of updated r-cran-tm 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: Thu, 25 Feb 2016 10:24:39 +0100
Source: r-cran-tm
Binary: r-cran-tm
Architecture: source amd64
Version: 0.6-2-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Science Team 

Changed-By: Daniel Pocock 
Description:
 r-cran-tm  - Text Mining functionality for R
Closes: 815373
Changes:
 r-cran-tm (0.6-2-2) unstable; urgency=medium
 .
   * Add more build dependencies. (Closes: #815373)
Checksums-Sha1:
 7edeb196162d6cb88490faaf16c81a448927a8d8 1998 r-cran-tm_0.6-2-2.dsc
 862e5e96bfc5c2af865d89153c0f7c870dec644f 12200 r-cran-tm_0.6-2-2.debian.tar.xz
 f78aa33c405523e23b4e8e5aed4027e3c236b65f 3514 
r-cran-tm-dbgsym_0.6-2-2_amd64.deb
 98f3298eb2cda775834b24094ffcf0abc0126838 647248 r-cran-tm_0.6-2-2_amd64.deb
Checksums-Sha256:
 27356c89a3280e5fbe29993dbcac9565aa8a1624e48c9f18b0dc6c4f0f976ee5 1998 
r-cran-tm_0.6-2-2.dsc
 a41c300ba0f0632fb95b5f3895c16695ef3db2de64c965328b68bc55448dc62b 12200 
r-cran-tm_0.6-2-2.debian.tar.xz
 d9ca0d9afa205e48e8d60e38c10f4cee7446cd22be1b92426584d8a455a014a9 3514 
r-cran-tm-dbgsym_0.6-2-2_amd64.deb
 789505822a24752e81ffa761f13389350f8d1cff22dcf92ae4ea832430cad8d8 647248 
r-cran-tm_0.6-2-2_amd64.deb
Files:
 4f1a81ece60436367ea6801bdff8c8f6 1998 gnu-r optional r-cran-tm_0.6-2-2.dsc
 c9d035000cc48466b9fa33426fa27bbf 12200 gnu-r optional 
r-cran-tm_0.6-2-2.debian.tar.xz
 13032468f513b178251cde4fdb65cb16 3514 debug extra 
r-cran-tm-dbgsym_0.6-2-2_amd64.deb
 7054b7488331bab275fe88f8a49d569d 647248 gnu-r optional 
r-cran-tm_0.6-2-2_amd64.deb

-BEGIN PGP SIGNATURE-
Version: GnuPG v1

iQIcBAEBCAAGBQJWztmLAAoJEGxlgOd711bEuJUQANNpaWcp5QvqaVlnlVfyhpEg
pRxDPc72E1aWNBJ6J9KAyNnvmvkviH981SyXVPfExRRqtlKe53ASPuy64G/P1TNJ
W8F3jn/evSecbfqP/Eeyi1UzjUBANoIVqz/YqEeRa+FEVk0xyXPnsuQYOVsdROtm
crITgKmKCS3IfD4mB/TKqd0NPgKDnIjyI4BM/m410ZrwAd+CwaZVhhrpDnSOjYZx
BvGHG+eotdsOcyLphguD6oHVDDbWsbQe9PpS/3xCi+0nyKeMFMBuf4TdiPSoK2WG
ZjdgWRV83PbXkwsKtPfDqrCx5vGbzZVKderx8n+kK+21NadBOg9qYxGVWWVLlQAo
XnU4W8WsjD/n1sO+wcBwTFA5m0cugW0eMHyunZXan00DYOvQNjcwyxRo+tE77o+7
7r+LwcQLE7JKxPu1orT7dDJgi0QLWumej+NZo44r6P3jka4wSBSdc/oAs8gu4gJC
6wMXUczH506nPlyo6i0t+zYmupcbRQ67cFExvOjjE3S79/y68jcGiRWEK8x+oslD
G/n8/1OL3aqm8iUwALWyRTGwg4dsXZP+p36VF43CMhFc3z/TJ3TI+IBzDQvrnJVs
E1efzI72DvRMdBhCFtwilhtHBalScKyfUmvftF82hxbdDv+eEfPIlAyHzi/FofxZ
mZfhUcjDwkGy2jdkjLEq
=lhdX
-END PGP SIGNATURE End Message ---

Bug#808738: closed by Pirate Praveen <prav...@debian.org> (Bug#808738: fixed in ruby-sinatra 1.4.7-1)

[Antonio Terceiro]

On Thu, Feb 25, 2016 at 08:57:03AM +0100, Chris Lamb wrote:
> >   * Add patch i18n-fix.patch
> >- Specify available locales during testing (Closes: #808738)
> 
> Is this due to /missing/ locales or the "wrong" locale?
> 
> If the latter, then whatever the failing test, that functionality is
> going to fail for users at runtime who aren't using that particular
> locale!

the issue is caused by some setup that needs to be done by applications
when using the i18n library, that was not mandatory before ruby-i18n
0.7. Those tests are testing integration betweem sinatra and i18n, in
the case when the application makes use of i18n (which they do not, by
default - not that ruby-sinatra does not depend on ruby-i18n).

Independent of that, applications using i18n (with sinatra or not) need
to be fixed anyway.


signature.asc
Description: PGP signature

Processed: notfixed 814972 in 1.6.10~dfsg0-2

[Debian Bug Tracking System]

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

> # unconfuse bts
> notfixed 814972 1.6.10~dfsg0-2
Bug #814972 {Done: "Matteo F. Vescovi" } [src:openimageio] 
openimageio: FTBFS:  CMakeFiles/Makefile2:1517: recipe for target 
'src/libOpenImageIO/CMakeFiles/OpenImageIO.dir/all' failed
No longer marked as fixed in versions 1.6.10~dfsg0-2.
> thanks
Stopping processing here.

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

Bug#815888: nvidia-detect: GF119M [GeForce 610M] nvidia-detect=ok for nvidia-driver . . . not ok

[Fulano Diego Perez]

Package: nvidia-detect
Severity: grave
Justification: renders package unusable


_disclaimer_

1.
i do not know if the problem lies with nvidia-detect, nvidia-driver and its
dependencies, or neither

2.
this bug report was submitted after removal and revert back to nouveau

3.
applies to intel ivy bridge chipset with built-in intel graphics +
nvidia below



nvidia-detect recommends nvidia-driver

i then install nvidia-driver, its dependencies and nvidia-xconfig

NB i attempted this ~6 months ago and yesterday, i do not know the affect of
the recent nvidia updates to xserver and whether nvidia-xconfig is still
necessary

gdm3 cannot proceed after reboot

please advise any further log provision where necessary:



/var/log/Xorg.0.log



[   152.193]
X.Org X Server 1.18.1
Release Date: 2016-02-08
[   152.193] X Protocol Version 11, Revision 0
[   152.193] Build Operating System: Linux 3.16.0-4-amd64 x86_64 Debian
[   152.193] Current Operating System: Linux sys 4.3.0-1-amd64 #1 SMP Debian
4.3.5-1 (2016-02-06) x86_64
[   152.193] Kernel command line: BOOT_IMAGE=/vmlinuz-4.3.0-1-amd64
root=/dev/mapper/vg-root ro apparmor=1 security=apparmor quiet
[   152.193] Build Date: 09 February 2016  11:06:03AM
[   152.193] xorg-server 2:1.18.1-1 (http://www.debian.org/support)
[   152.193] Current version of pixman: 0.33.6
[   152.193]Before reporting problems, check http://wiki.x.org
to make sure that you have the latest version.
[   152.193] Markers: (--) probed, (**) from config file, (==) default
setting,
(++) from command line, (!!) notice, (II) informational,
(WW) warning, (EE) error, (NI) not implemented, (??) unknown.
[   152.194] (==) Log file: "/var/log/Xorg.0.log", Time: Wed Feb 24 20:56:36
2016
[   152.194] (==) Using config file: "/etc/X11/xorg.conf"
[   152.194] (==) Using system config directory "/usr/share/X11/xorg.conf.d"
[   152.194] (==) ServerLayout "Layout0"
[   152.194] (**) |-->Screen "Screen0" (0)
[   152.194] (**) |   |-->Monitor "Monitor0"
[   152.195] (**) |   |-->Device "Device0"
[   152.195] (**) |-->Input Device "Keyboard0"
[   152.195] (**) |-->Input Device "Mouse0"
[   152.195] (==) Automatically adding devices
[   152.195] (==) Automatically enabling devices
[   152.195] (==) Automatically adding GPU devices
[   152.195] (==) Max clients allowed: 256, resource mask: 0x1f
[   152.195] (WW) The directory "/usr/share/fonts/X11/cyrillic" does not
exist.
[   152.195]Entry deleted from font path.
[   152.195] (==) FontPath set to:
/usr/share/fonts/X11/misc,
/usr/share/fonts/X11/100dpi/:unscaled,
/usr/share/fonts/X11/75dpi/:unscaled,
/usr/share/fonts/X11/Type1,
/usr/share/fonts/X11/100dpi,
/usr/share/fonts/X11/75dpi,
built-ins
[   152.195] (==) ModulePath set to "/usr/lib/xorg/modules"
[   152.195] (WW) Hotplugging is on, devices using drivers 'kbd', 'mouse' or
'vmmouse' will be disabled.
[   152.195] (WW) Disabling Keyboard0
[   152.195] (WW) Disabling Mouse0
[   152.195] (II) Loader magic: 0x5588086c2dc0
[   152.195] (II) Module ABI versions:
[   152.195]X.Org ANSI C Emulation: 0.4
[   152.195]X.Org Video Driver: 20.0
[   152.195]X.Org XInput driver : 22.1
[   152.195]X.Org Server Extension : 9.0
[   152.196] (++) using VT number 1

[   152.200] (II) systemd-logind: took control of session
/org/freedesktop/login1/session/_3255
[   152.201] (II) xfree86: Adding drm device (/dev/dri/card0)
[   152.201] (II) systemd-logind: got fd for /dev/dri/card0 226:0 fd 8
paused 0
[   152.201] (II) xfree86: Adding drm device (/dev/dri/card1)
[   152.202] (II) systemd-logind: got fd for /dev/dri/card1 226:1 fd 9
paused 0
[   152.204] (--) PCI:*(0:0:2:0) 8086:0166:1043:1457 rev 9, Mem @
0xf740/4194304, 0xd000/268435456, I/O @ 0xf000/64
[   152.204] (--) PCI: (0:1:0:0) 10de:1058:1043:1457 rev 161, Mem @
0xf600/16777216, 0xe000/134217728, 0xe800/33554432, I/O @
0xe000/128, BIOS @ 0x/524288
[   152.204] (II) LoadModule: "glx"
[   152.204] (II) Loading /usr/lib/xorg/modules/linux/libglx.so
[   152.215] (II) Module glx: vendor="NVIDIA Corporation"
[   152.215]compiled for 4.0.2, module version = 1.0.0
[   152.215]Module class: X.Org Server Extension
[   152.215] (II) NVIDIA GLX Module  352.79  Wed Jan 13 15:54:44 PST 2016
[   152.215] (II) LoadModule: "nvidia"
[   152.215] (II) Loading /usr/lib/xorg/modules/drivers/nvidia_drv.so
[   152.215] (II) Module nvidia: vendor="NVIDIA Corporation"
[   152.215]compiled for 4.0.2, module version = 1.0.0
[   152.215]Module class: X.Org Video Driver
[   152.216] (II) NVIDIA dlloader X Driver  352.79  Wed Jan 13 15:31:15 PST
2016
[   152.216] (II) NVIDIA Unified Driver for all Supported NVIDIA GPUs
[   152.216] (EE) No devices detected.
[   152.216] (EE)
Fatal server error:
[   152.216] (EE) no screens found(EE)
[   152.216] (EE)
Please consult the The X.Org Foundation support
 at http://wiki.x.org
 for help.
[  

Processed: Re: Bug#815886: plasma-desktop-data: conflight with kde-l10n-engb

[Debian Bug Tracking System]

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

> severity 815886 serious
Bug #815886 [plasma-desktop-data] plasma-desktop-data: conflight with 
kde-l10n-engb
Severity set to 'serious' from 'normal'
> merge 815886 814526
Bug #815886 [plasma-desktop-data] plasma-desktop-data: conflight with 
kde-l10n-engb
Bug #815886 [plasma-desktop-data] plasma-desktop-data: conflight with 
kde-l10n-engb
Added tag(s) pending.
Bug #814526 [plasma-desktop-data] plasma-desktop-data: fails to upgrade from 
'sid' - trying to overwrite 
/usr/share/locale/*/LC_MESSAGES/kcm_device_automounter.mo
Merged 814526 815886
> thanks
Stopping processing here.

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

Bug#815372: marked as done (r-cran-lubridate: FTBFS: dependency stringr is not available)

[Debian Bug Tracking System]

Your message dated Thu, 25 Feb 2016 12:07:58 +
with message-id 
and subject line Bug#815372: fixed in r-cran-lubridate 1.5.0-2
has caused the Debian Bug report #815372,
regarding r-cran-lubridate: FTBFS: dependency stringr is not available
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.)


-- 
815372: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=815372
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: r-cran-lubridate
Version: 1.5.0-1
Severity: serious
Justification: fails to build from source

Hi, Daniel.

Builds of r-cran-lubridate in minimal environments (notably, on the
autobuilders) have been failing:

  ERROR: dependency 'stringr' is not available for package 'lubridate'
  * removing 
'/«PKGBUILDDIR»/debian/r-cran-lubridate/usr/lib/R/site-library/lubridate'
  /usr/share/R/debian/r-cran.mk:98: recipe for target 'R_any_arch' failed
  make: *** [R_any_arch] Error 1

Please declare a build dependency on r-cran-stringr and confirm with
pbuilder or the like that you haven't missed any others.

Thanks!
--- End Message ---
--- Begin Message ---
Source: r-cran-lubridate
Source-Version: 1.5.0-2

We believe that the bug you reported is fixed in the latest version of
r-cran-lubridate, 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 815...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Daniel Pocock  (supplier of updated r-cran-lubridate 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: Thu, 25 Feb 2016 10:24:39 +0100
Source: r-cran-lubridate
Binary: r-cran-lubridate
Architecture: source amd64
Version: 1.5.0-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Science Team 

Changed-By: Daniel Pocock 
Description:
 r-cran-lubridate - simplifies dealing with dates in R
Closes: 815372
Changes:
 r-cran-lubridate (1.5.0-2) unstable; urgency=medium
 .
   * Add more build dependencies. (Closes: #815372)
Checksums-Sha1:
 3e077cd8abe011e9cf1bb22a750322e09e72f0fa 2045 r-cran-lubridate_1.5.0-2.dsc
 93b2c744b8dd6c90614476783fe9ce3d819d5843 1508 
r-cran-lubridate_1.5.0-2.debian.tar.xz
 18c9056b6ed0b9802e8885a9a0c8bac9bc2bd61d 8234 
r-cran-lubridate-dbgsym_1.5.0-2_amd64.deb
 14c5d0018b2d529380ba77a07a489b4b773555f2 621086 
r-cran-lubridate_1.5.0-2_amd64.deb
Checksums-Sha256:
 3fcbb23aefeb1875f122604941f184230ba0d296cf5fdfbc81b5caffa9bb0ad8 2045 
r-cran-lubridate_1.5.0-2.dsc
 d96bc7b7bd5b3398e08c359cb5e12b3e4aa25f0ddcdcd8a75600bfc46e17c1ab 1508 
r-cran-lubridate_1.5.0-2.debian.tar.xz
 b39732b6089eaf3b5029395918658b539a23531da7be88e9b7e28ad5fb45cf76 8234 
r-cran-lubridate-dbgsym_1.5.0-2_amd64.deb
 71bdef30989abc8745314adccd69655fc74cbc4f5e63ac8d0eba2c31954ddce5 621086 
r-cran-lubridate_1.5.0-2_amd64.deb
Files:
 5f70813387809d966e2c64e9ae696a6b 2045 gnu-r optional 
r-cran-lubridate_1.5.0-2.dsc
 504196b6c56235df204738e2f6c75364 1508 gnu-r optional 
r-cran-lubridate_1.5.0-2.debian.tar.xz
 bd36de17bf65e48c388c9d6f329a539a 8234 debug extra 
r-cran-lubridate-dbgsym_1.5.0-2_amd64.deb
 2270eae4922ddf32ffa0ebe862ba9125 621086 gnu-r optional 
r-cran-lubridate_1.5.0-2_amd64.deb

-BEGIN PGP SIGNATURE-
Version: GnuPG v1

iQIcBAEBCAAGBQJWztiSAAoJEGxlgOd711bEh3cP/3Z2tLsnUqy5seEklTnwfw3c
YKtbPoWwU/NBWcM2xYsGrHXDbwq8CtqetJYuZauxfitM3StcONPde9Tz0Enky8Zu
5qDZX0g5erZpUg2eCDEd5DjagQ892hgrSMcKE0Ka+ZGzpp3iyrZQre/iUtPbMbN7
4qeVlcrSkb9CUpTYsdP1yuAU6YXKK8k4M0GOjWXBlAPsX4yaJrCX1mmTj3o+yQRM
BZ+62TU6OuXxyHgQKJPkh2OUsH6Ff/yrFcEEG87ByRJKgI2f2t3+odvhT4FWVK7o
VcmWBk6M8pbNigkizR4KSb5EMAFwB0HKX0eJO3MKpuqk+AmyGCqj69xJBdXwL0Ad
l5kLM5hRJRmyasSpJd2HypEWpd6Tqd1UdXP+v4mjgJwhoY3OorBNX6mh0ZpEO+/a
OCh9yqfOfOI/twIRWtBD1XFdU2EdovnAbSc43WszC7bWTkvmET51in1y1W21OZ2k
MT0AoXJ5pnzzCatB4yDOe6mEt1x1FxB6JU6axmzvtd2a4KnZGhFQXm19GVZ5auEC
L28eFh2Q4IkiWs4VREvCome/cs+yyjHNmmpGirJ93W4Lb43MiOlmfOWWgtIfqzSw
t0dnr5lwUZXNiTtpVhsmh2ORlETDEuJbeCnswlRa/IBG5npZmYRBXmUKwQyLSBVD
4rkkagP5og4Vpuzpx8u1
=yNb8
-END PGP SIGNATURE End Message ---

Bug#815383: marked as done (r-cran-glmnet: FTBFS: dependencies 'Matrix', 'foreach' are not available)

[Debian Bug Tracking System]

Your message dated Thu, 25 Feb 2016 12:07:50 +
with message-id 
and subject line Bug#815383: fixed in r-cran-glmnet 2.0-2-2
has caused the Debian Bug report #815383,
regarding r-cran-glmnet: FTBFS: dependencies 'Matrix', 'foreach' are not 
available
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.)


-- 
815383: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=815383
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: r-cran-glmnet
Version: 2.0-2-1
Severity: serious
Justification: fails to build from source

Hi, Daniel.

Builds of r-cran-glmnet in minimal environments (notably, on the
autobuilders) have been failing:

  ERROR: dependencies 'Matrix', 'foreach' are not available for package 'glmnet'
  * removing '/«PKGBUILDDIR»/debian/r-cran-glmnet/usr/lib/R/site-library/glmnet'
  /usr/share/R/debian/r-cran.mk:98: recipe for target 'R_any_arch' failed
  make: *** [R_any_arch] Error 1

Please declare build dependencies on r-cran-matrix and r-cran-foreach,
and confirm with pbuilder or the like that you haven't missed any others.

Thanks!
--- End Message ---
--- Begin Message ---
Source: r-cran-glmnet
Source-Version: 2.0-2-2

We believe that the bug you reported is fixed in the latest version of
r-cran-glmnet, 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 815...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Daniel Pocock  (supplier of updated r-cran-glmnet 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: Thu, 25 Feb 2016 10:18:38 +0100
Source: r-cran-glmnet
Binary: r-cran-glmnet
Architecture: source amd64
Version: 2.0-2-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Science Team 

Changed-By: Daniel Pocock 
Description:
 r-cran-glmnet - Lasso and Elastic-Net Regularized Generalized Linear Models
Closes: 815383
Changes:
 r-cran-glmnet (2.0-2-2) unstable; urgency=medium
 .
   * Add more build dependencies. (Closes: #815383)
Checksums-Sha1:
 889005d6b557c778de67df67c6a28995f92118f5 2040 r-cran-glmnet_2.0-2-2.dsc
 7fdef538d557d03600c00fcea865c707e59b7d73 2108 
r-cran-glmnet_2.0-2-2.debian.tar.xz
 074989fa068198fffd28d8f3787a8077ee9adbb4 164732 
r-cran-glmnet-dbgsym_2.0-2-2_amd64.deb
 2e31e2ef6eb56ed59ff4d217f6f3f6953d5a9855 1587036 
r-cran-glmnet_2.0-2-2_amd64.deb
Checksums-Sha256:
 d9e152d6297a82678346626fadf2705ec1ddf3fb6585157100955ba4410f86c2 2040 
r-cran-glmnet_2.0-2-2.dsc
 6f6b788f73673104662d034ba5441313dad42ad04a8b6f73436694a85a40569b 2108 
r-cran-glmnet_2.0-2-2.debian.tar.xz
 2d6c9a8a1a2d62f7b546799a73bdf3c65cd5a8e9111b9fc31a1bcfaf37a2995c 164732 
r-cran-glmnet-dbgsym_2.0-2-2_amd64.deb
 cd0271c4fa0b8aefb15ad58233afb8784c6c797326fb5519bc3a14dfaf0ce0ec 1587036 
r-cran-glmnet_2.0-2-2_amd64.deb
Files:
 8cd07f8dc044f971c95f74eed362f26b 2040 gnu-r optional r-cran-glmnet_2.0-2-2.dsc
 4258109461b455e98a14b05e8fe6e836 2108 gnu-r optional 
r-cran-glmnet_2.0-2-2.debian.tar.xz
 25fbc09c429fdba78772f1360ccabb19 164732 debug extra 
r-cran-glmnet-dbgsym_2.0-2-2_amd64.deb
 bf9d28adc358e255d7ca211bfe97c70f 1587036 gnu-r optional 
r-cran-glmnet_2.0-2-2_amd64.deb

-BEGIN PGP SIGNATURE-
Version: GnuPG v1

iQIcBAEBCAAGBQJWzskBAAoJEGxlgOd711bEezAP/ijwWJBPuC6LRA4+6z75IOL7
n7NjnOtp8AvgLLw9qBlewVq6dDGCjLUOP21Z276Wx7uupeQ1k/EmHYPAfGuKPpEd
eLazYpuhv7vh0tp3nboBiGFETVbWchc3NgE3RShHTwc+yPk0AUcfyR3C38zmvN/q
sunZO8h4XU+O4u59Z3rmb2BHoKwXqXqrlZSuUT90OI/QQuaZH/q8BUhVx17p1exR
PFWU5SrPlnveVuH2AY2QHQcoctq402BtIzSY0nKmgazZOwH6Hkarvkz4Zp/bLS38
51yNroCEn+qS65St+8ZAXsui/umjwgXxAkFOlUC4X/B/+aV+ksrgN7ZXJwqrYj64
N6w4Qnqj4aOl5RSgmZeG9MOi+wPXv1ATLWoPWyhZUwT06cFkHjhjMcO/Yu8rJsKk
GQIz/m6Sl9O/SFNGEppgUF5fxIPjjdmaZ+vJU/IF5LQB3/vr60Xm4uSxxvskEPEq
oMyOhY9ZFaDSJHiMhVAG3IaHSub/o26l//AANhMQH93Md7NC38tCUDkDpdxL/DW+
+F86y8cW9f7UPdv5cb1lPIX37FJADrv1vHY9JR9Eslk9ueJbAf2PSlcWV7ui2DAc
iMpp6+lK74nD89ZEd2vgwmlfAIoJJwQ4TRzYPAM/cbfNUvcO4lOHwPipdps4cynH
WzOEwk3tKi/Ry7vrSJDr
=Qz2I
-END PGP SIGNATURE End Message ---

Bug#815783: marked as done (r-cran-arm: FTBFS - dependencies are not available for package 'arm')

[Debian Bug Tracking System]

Your message dated Thu, 25 Feb 2016 12:07:42 +
with message-id 
and subject line Bug#815741: fixed in r-cran-arm 1.8-6-2
has caused the Debian Bug report #815741,
regarding r-cran-arm: FTBFS - dependencies are not available for package 'arm'
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.)


-- 
815741: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=815741
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: r-cran-arm
Version: 1.8-6-1
Severity: serious
Usertags: goto-cc

During a rebuild of all Debian packages in a clean sid chroot (using cowbuilder
and pbuilder) the build failed with the following error.

[...]
dh_installdirs  usr/lib/R/site-library
echo "R:Depends=r-base-core (>= 3.2.3-6), r-api-3" >> 
debian/r-cran-arm.substvars
if test -f /usr/bin/xvfb-run; then  \
 xvfb-run -a\
R CMD INSTALL -l 
/srv/jenkins-slave/workspace/sid-goto-cc-r-cran-arm/r-cran-arm-1.8-6/debian/r-cran-arm/usr/lib/R/site-library
 --clean \
 .  \
"--built-timestamp=\"Thu, 18 Feb 2016 21:43:55 
+0100\"" \
;   \
else\
 R CMD INSTALL -l 
/srv/jenkins-slave/workspace/sid-goto-cc-r-cran-arm/r-cran-arm-1.8-6/debian/r-cran-arm/usr/lib/R/site-library
 \
--clean  .  \
"--built-timestamp=\"Thu, 18 Feb 2016 21:43:55 
+0100\"" \
;   \
fi
ERROR: dependencies 'MASS', 'Matrix', 'lme4', 'abind', 'coda', 'nlme' are not 
available for package 'arm'
* removing 
'/srv/jenkins-slave/workspace/sid-goto-cc-r-cran-arm/r-cran-arm-1.8-6/debian/r-cran-arm/usr/lib/R/site-library/arm'
/usr/share/R/debian/r-cran.mk:98: recipe for target 'R_any_arch' failed
make: *** [R_any_arch] Error 1


The full build log is attached; please do let me know if the problem is
unreproducible, in which case I shall try to investigate further.

Best,
Michael


r-cran-arm-build-log.txt.gz
Description: application/gunzip


signature.asc
Description: PGP signature
--- End Message ---
--- Begin Message ---
Source: r-cran-arm
Source-Version: 1.8-6-2

We believe that the bug you reported is fixed in the latest version of
r-cran-arm, 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 815...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Daniel Pocock  (supplier of updated r-cran-arm 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: Thu, 25 Feb 2016 10:24:39 +0100
Source: r-cran-arm
Binary: r-cran-arm
Architecture: source all
Version: 1.8-6-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Science Team 

Changed-By: Daniel Pocock 
Description:
 r-cran-arm - Data Analysis Using Regression and Multilevel/Hierarchical Models
Closes: 815741
Changes:
 r-cran-arm (1.8-6-2) unstable; urgency=medium
 .
   * Add more build dependencies. (Closes: #815741)
Checksums-Sha1:
 d50d06c6361dfafa0e1e551204b7aef3546cff97 2049 r-cran-arm_1.8-6-2.dsc
 b099a8f08c31a352b25c4607dc778abcc7b2dd24 1700 r-cran-arm_1.8-6-2.debian.tar.xz
 0e35e15205be9e828c51bf1471a4a03988d3d186 223760 r-cran-arm_1.8-6-2_all.deb
Checksums-Sha256:
 15ae933480b69bab422dc5568155ffc29692a2eb9dc6948dd6e4eabbdb6217c1 2049 
r-cran-arm_1.8-6-2.dsc
 fa24667a4920282c784f7dcb83fb9c60f5e78a165999a00eac3f91d8d072ed00 1700 
r-cran-arm_1.8-6-2.debian.tar.xz
 997744388de3ed12bca3e7a197f17d14059941a80eb7934f58dab42539e3001f 223760 
r-cran-arm_1.8-6-2_all.deb
Files:
 c506fa557f17853e8e56264eeb6749c0 2049 gnu-r optional r-cran-arm_1.8-6-2.dsc
 71b60d597b5d352675a8f039cf162ab4 1700 gnu-r optional 
r-cran-arm_1.8-6-2.debian.tar.xz
 5f4ff13af2915f1eba67c3be466501d2 223760 gnu-r optional 
r-cran-arm_1.8-6-2_all.deb

-BEGIN PGP SIGNATURE-

Bug#815741: marked as done (r-cran-arm: FTBFS: ERROR: dependencies 'MASS', 'Matrix', 'lme4', 'abind', 'coda', 'nlme' are not available for package 'arm')

[Debian Bug Tracking System]

Your message dated Thu, 25 Feb 2016 12:07:42 +
with message-id 
and subject line Bug#815741: fixed in r-cran-arm 1.8-6-2
has caused the Debian Bug report #815741,
regarding r-cran-arm: FTBFS: ERROR: dependencies 'MASS', 'Matrix', 'lme4', 
'abind', 'coda', 'nlme' are not available for package 'arm'
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.)


-- 
815741: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=815741
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: r-cran-arm
Version: 1.8-6-1
Severity: serious
Justification: fails to build from source
User: reproducible-bui...@lists.alioth.debian.org
Usertags: ftbfs
X-Debbugs-Cc: reproducible-bui...@lists.alioth.debian.org

Dear Maintainer,

r-cran-arm fails to build from source in unstable/amd64:

  [..]

   dpkg-buildpackage -rfakeroot -D -us -uc -b
  dpkg-buildpackage: source package r-cran-arm
  dpkg-buildpackage: source version 1.8-6-1
  dpkg-buildpackage: source distribution unstable
  dpkg-buildpackage: source changed by Daniel Pocock 
   dpkg-source --before-build r-cran-arm-1.8-6
  dpkg-buildpackage: host architecture amd64
   fakeroot debian/rules clean
  test -x debian/rules
  dh_clean 
  if test -d src; then  \
find src -regex ".*\.o" |   \
  xargs --no-run-if-empty -r rm;  \
fi
  rm -f config.log config.status
   debian/rules build
  test -x debian/rules
  mkdir -p "."
   fakeroot debian/rules binary
  test -x debian/rules
  dh_testroot
  dh_prep 
  dh_installdirs -A 
  mkdir -p "."
  dh_installdirsusr/lib/R/site-library
  echo "R:Depends=r-base-core (>= 3.2.3-6), r-api-3" >> 
debian/r-cran-arm.substvars
  if test -f /usr/bin/xvfb-run; then\
 xvfb-run -a\
R CMD INSTALL -l 
/home/lamby/temp/cdt.20160224081417.Fxz5143g8S/r-cran-arm-1.8-6/debian/r-cran-arm/usr/lib/R/site-library
 --clean \
 .  \
"--built-timestamp=\"Thu, 18 Feb 2016 21:43:55 
+0100\"" \
;   \
else\
 R CMD INSTALL -l 
/home/lamby/temp/cdt.20160224081417.Fxz5143g8S/r-cran-arm-1.8-6/debian/r-cran-arm/usr/lib/R/site-library
  \
--clean  .  \
"--built-timestamp=\"Thu, 18 Feb 2016 21:43:55 
+0100\"" \
;   \
fi
  ERROR: dependencies 'MASS', 'Matrix', 'lme4', 'abind', 'coda', 'nlme' are not 
available for package 'arm'
  * removing 
'/home/lamby/temp/cdt.20160224081417.Fxz5143g8S/r-cran-arm-1.8-6/debian/r-cran-arm/usr/lib/R/site-library/arm'
  /usr/share/R/debian/r-cran.mk:98: recipe for target 'R_any_arch' failed
  make: *** [R_any_arch] Error 1

  [..]

The full build log is attached.


Regards,

-- 
  ,''`.
 : :'  : Chris Lamb
 `. `'`  la...@debian.org / chris-lamb.co.uk
   `-


r-cran-arm.1.8-6-1.unstable.amd64.log.txt.gz
Description: Binary data
--- End Message ---
--- Begin Message ---
Source: r-cran-arm
Source-Version: 1.8-6-2

We believe that the bug you reported is fixed in the latest version of
r-cran-arm, 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 815...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Daniel Pocock  (supplier of updated r-cran-arm 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: Thu, 25 Feb 2016 10:24:39 +0100
Source: r-cran-arm
Binary: r-cran-arm
Architecture: source all
Version: 1.8-6-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Science Team 

Changed-By: Daniel Pocock 
Description:
 r-cran-arm - Data Analysis Using Regression and Multilevel/Hierarchical Models
Closes: 815741
Changes:
 r-cran-arm 

Bug#814645: not in stable yet

[Andreas Beckmann]

On 2016-02-25 08:36, Pirate Praveen wrote:
> ruby-mousetrap-rails is not part of any stable release. So should I
> really handle this upgrade case?

Yes. Especially since the fix should be trivial.


Andreas

Processed (with 1 error): Re: Bug#815886: plasma-desktop-data: conflight with kde-l10n-engb

[Debian Bug Tracking System]

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

> merge 815886 814526
Bug #815886 [plasma-desktop-data] plasma-desktop-data: conflight with 
kde-l10n-engb
Unable to merge bugs because:
severity of #814526 is 'serious' not 'normal'
Failed to merge 815886: Did not alter merged bugs.

> thanks
Stopping processing here.

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

Bug#815047: Still not fixed

[Scott Kitterman]

On Thursday, February 25, 2016 10:01:27 AM you wrote:
> reopen 815047
> thanks
> 
> Still not fixed. It seems the latest fix didn't make it into the package for
> some reason. Manually setting
> 
> shlib_directory=/usr/lib/postfix
> daemon_directory=/usr/lib/postfix/sbin
> 
> in main.cf fixes the problem for me, but obviously the upgrade shouldn't
> need such manual config change.

Thanks.

It works on new installs now, but clearly we'll need something in the postinst 
to repair broken installs.

Scott K

Bug#815864: python3-venv: unable to create a virtual environment

[Florent Rougon]

Some more info:

Inserting a 'print(cmd)' at line 259 showed that the direct cause of
the error message is the command:

  ['/home/flo/python-venv/testdir/bin/python3.5',
   '-Im', 'ensurepip', '--upgrade', '--default-pip']

exiting with a non-zero exit status. Running this command by hand after
the venv creation failed yields:

~/python-venv % /home/flo/python-venv/testdir/bin/python3.5 -Im ensurepip 
--upgrade --default-pip; echo $?
Traceback (most recent call last):
  File "/usr/lib/python3.5/runpy.py", line 184, in _run_module_as_main
"__main__", mod_spec)
  File "/usr/lib/python3.5/runpy.py", line 85, in _run_code
exec(code, run_globals)
  File "/usr/lib/python3.5/ensurepip/__main__.py", line 4, in 
ensurepip._main()
  File "/usr/lib/python3.5/ensurepip/__init__.py", line 218, in _main
version="pip {}".format(version()),
  File "/usr/lib/python3.5/ensurepip/__init__.py", line 74, in version
assert len(wheel_names) == 1, wheel_names
AssertionError: []
1
~/python-venv %

The assertion error comes from this in
/usr/lib/python3.5/ensurepip/__init__.py:

wheel_names = glob.glob('/usr/share/python-wheels/pip-*.whl')
assert len(wheel_names) == 1, wheel_names

and indeed:

~/python-venv % ls /usr/share/python-wheels/pip-*.whl
zsh: no matches found: /usr/share/python-wheels/pip-*.whl
~/python-venv % apt-file search /usr/share/python-wheels/pip-
virtualenv: /usr/share/python-wheels/pip-8.0.2-py2.py3-none-any.whl
~/python-venv %

I then installed the 'virtualenv' package, which does provide the
mentioned file, and tried to recreate the venv from scratch after adding
a 'print(os.getcwd())' right after the previously-added 'print(cmd)' in
/usr/lib/python3.5/venv/__init__.py (lines 259-260, before the 'try'
statement in EnvBuilder._setup_pip()):

~/python-venv % rm -rf testdir
~/python-venv % /usr/bin/python3.5 -m venv testdir
['/home/flo/python-venv/testdir/bin/python3.5', '-Im', 'ensurepip', 
'--upgrade', '--default-pip']
/home/flo/python-venv
The virtual environment was not created successfully because ensurepip is not
available.  On Debian/Ubuntu systems, you need to install the python3-venv
package using the following command.

apt-get install python3-venv

You may need to use sudo with that command.  After installing the python3-venv
package, recreate your virtual environment.

~/python-venv % /usr/bin/python3.5 -c "import subprocess; 
subprocess.check_output(['/home/flo/python-venv/testdir/bin/python3.5', '-Im', 
'ensurepip', '--upgrade', '--default-pip'])"
Traceback (most recent call last):
  File 
"/tmp/tmpicb907db/pip-8.0.2-py2.py3-none-any.whl/pip/_vendor/__init__.py", line 
33, in vendored
ImportError: No module named 'pip._vendor.cachecontrol'

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File "/usr/lib/python3.5/runpy.py", line 184, in _run_module_as_main
"__main__", mod_spec)
  File "/usr/lib/python3.5/runpy.py", line 85, in _run_code
exec(code, run_globals)
  File "/usr/lib/python3.5/ensurepip/__main__.py", line 4, in 
ensurepip._main()
  File "/usr/lib/python3.5/ensurepip/__init__.py", line 269, in _main
default_pip=args.default_pip,
  File "/usr/lib/python3.5/ensurepip/__init__.py", line 175, in bootstrap
_run_pip(args + _PROJECTS, additional_paths)
  File "/usr/lib/python3.5/ensurepip/__init__.py", line 65, in _run_pip
import pip
  File "/tmp/tmpicb907db/pip-8.0.2-py2.py3-none-any.whl/pip/__init__.py", line 
12, in 
  File "/tmp/tmpicb907db/pip-8.0.2-py2.py3-none-any.whl/pip/exceptions.py", 
line 6, in 
  File 
"/tmp/tmpicb907db/pip-8.0.2-py2.py3-none-any.whl/pip/_vendor/__init__.py", line 
52, in 
  File 
"/tmp/tmpicb907db/pip-8.0.2-py2.py3-none-any.whl/pip/_vendor/__init__.py", line 
35, in vendored
ImportError: No module named 'cachecontrol'
Traceback (most recent call last):
  File "", line 1, in 
  File "/usr/lib/python3.5/subprocess.py", line 626, in check_output
**kwargs).stdout
  File "/usr/lib/python3.5/subprocess.py", line 708, in run
output=stdout, stderr=stderr)
subprocess.CalledProcessError: Command 
'['/home/flo/python-venv/testdir/bin/python3.5', '-Im', 'ensurepip', 
'--upgrade', '--default-pip']' returned non-zero exit status 1
~/python-venv %

-- 
Florent

Bug#813819: MIA Ping

[Joachim Breitner]

Hi,

Am Donnerstag, den 25.02.2016, 11:51 +0100 schrieb Tino Mettler:
> yes, I am. The simple change is not as simple as it seems. It got a
> (not very verbose) build error in pbuilder and got no time for
> investigating, yet. I'll ask for help if I can't figure it out this
> evening.

here, I could simply rebuild syncevolution against unstable and it
worked...

Greetings,
Joachim

-- 
Joachim “nomeata” Breitner
Debian Developer
  nome...@debian.org • https://people.debian.org/~nomeata
  XMPP: nome...@joachim-breitner.de • GPG-Key: 0xF0FBF51F
  https://www.joachim-breitner.de/


signature.asc
Description: This is a digitally signed message part

Bug#813452: [Pkg-pascal-devel] Bug#813452: [Core] Bug#813452: Bug#813452: fpc-3.0 regression in armhf and armel architectures

[Abou Al Montacir]

Hi Sven,
On Mon, 2016-02-22 at 17:44 +0100, Abou Al Montacir wrote:
> Hi Sven
> 
> On Mon, 2016-02-22 at 07:58 +0100, Sven Barth wrote:
> > >  Looks like PIC code was broken in 3.0. Is there anyone aware of that? How
> > can we fix that?
> > >
> > Would you please try the current development version of FPC (3.1.1) to check
> > whether the issue persists there?
> Yes, sure I'll do and let you know.
I've tested the FPC trunk and it works well. Here is the log of both wersions:
(sid_armel-dchroot)abou@abel:~/hedgewars-0.9.22-dfsg/obj-arm-linux-gnueabi/hedgewars$
 fpc -fPIC test2 && ./test2
Free Pascal Compiler version 3.0.0+dfsg-2 [2016/01/28] for arm
Copyright (c) 1993-2015 by Florian Klaempfl and others
Target OS: Linux for ARMEL
Compiling test2.pas
Assembling test
Linking test2
/usr/bin/ld.bfd: warning: link.res contains output sections; did you forget -T?
4 lines compiled, 0.3 sec
Runtime error 103 at $000101D8
  $000101D8
  $00010124
(sid_armel-dchroot)abou@abel:~/hedgewars-0.9.22-dfsg/obj-arm-linux-gnueabi/hedgewars$
 /home/abou/fpc-3.1.1/fpc-3.1.1/build/fpc-3.1.1/fpcsrc/compiler/ppcarm 
-Fu/home/abou/fpc-3.1.1/fpc-3.1.1/build/fpc-3.1.1/fpcsrc/ 
-Fu/home/abou/fpc-3.1.1/fpc-3.1.1/build/fpc-3.1.1/fpcsrc/rtl/units/arm-linux 
-fPIC test2 && ./test2
Free Pascal Compiler version 3.1.1-0 [2016/02/24] for arm
Copyright (c) 1993-2015 by Florian Klaempfl and others
Target OS: Linux for ARMEL
Compiling test2.pas
Linking test2
4 lines compiled, 0.2 sec
Hello
(sid_armel-dchroot)abou@abel:~/hedgewars-0.9.22-dfsg/obj-arm-linux-gnueabi/hedgewars$
 
This shows that the issue was fixed in trunk. Can you please help finding the 
revision that may fixed that so we can extract a patch and fix 3.0.0?
As long as this bug is open, fpc transition to testing is blocked and this is 
quite unpleasing for many of our users.
-- 
Cheers,
Abou Al Montacir

signature.asc
Description: This is a digitally signed message part

Bug#815365: marked as done (roaraudio: build-depends on libslp-dev)

[Debian Bug Tracking System]

Your message dated Thu, 25 Feb 2016 11:06:47 +
with message-id 
and subject line Bug#815365: fixed in roaraudio 1.0~beta11-6
has caused the Debian Bug report #815365,
regarding roaraudio: build-depends on libslp-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.)


-- 
815365: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=815365
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: openslp-dfsg
Severity: serious

The last maintainer upload of openslp happened in 2007
and it's orphaned for 5.5 years now. The 1.2 branch is
completely abandoned upstream.

At the minimum the package should be upgraded to 2.0,
but the comment at
https://bugzilla.redhat.com/show_bug.cgi?id=CVE-2015-5177
suggests it's completely abandoned upstream.

Cheers,
Moritz
--- End Message ---
--- Begin Message ---
Source: roaraudio
Source-Version: 1.0~beta11-6

We believe that the bug you reported is fixed in the latest version of
roaraudio, 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 815...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Patrick Matthäi  (supplier of updated roaraudio 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: Thu, 25 Feb 2016 11:00:20 +0100
Source: roaraudio
Binary: libroar2 libroar-dev roaraudio-dbg roaraudio roarclients 
libroar-compat2 libroar-compat-tools libroar-plugins-universal
Architecture: source amd64
Version: 1.0~beta11-6
Distribution: unstable
Urgency: high
Maintainer: Patrick Matthäi 
Changed-By: Patrick Matthäi 
Description:
 libroar-compat-tools - drop-in replacements for other sound libraries (tools 
package)
 libroar-compat2 - drop-in replacements for other sound libraries
 libroar-dev - header files and documentation for the RoarAudio libraries
 libroar-plugins-universal - Collection of host-independent plugins for libroar
 libroar2   - foundation libraries for the RoarAudio sound server and clients
 roaraudio  - sound server for audio mixing
 roaraudio-dbg - RoarAudio sound server for audio mixing (debugging symbols)
 roarclients - Collection of basic clients for the RoarAudio Sound System
Closes: 815365
Changes:
 roaraudio (1.0~beta11-6) unstable; urgency=high
 .
   * Bump Standards-Version to 3.9.7 (no changes required).
   * Enable full hardening.
   * Drop libslp-dev build dependency.
 Closes: #815365
   * Add patch 04-more-spelling-errors to fix a bunch of spelling errors.
Checksums-Sha1:
 30bd1fb379456d2024b13c9c495f7acdc841e6a8 2416 roaraudio_1.0~beta11-6.dsc
 6a6fa7c131923b718ecbba3e540edb26ba1e3982 31896 
roaraudio_1.0~beta11-6.debian.tar.xz
 bacaf4ea631cffbe90549c1f7f710d0f0777b84b 20910 
libroar-compat-tools_1.0~beta11-6_amd64.deb
 e1a38d366355ad094a4d6fbbd241ebd6eb6818a3 55518 
libroar-compat2_1.0~beta11-6_amd64.deb
 12c7f25319b9e849c9945b9efca8f371165c26c9 234224 
libroar-dev_1.0~beta11-6_amd64.deb
 42bbed388aca39d461fcf761e5a14d015defc13a 38108 
libroar-plugins-universal_1.0~beta11-6_amd64.deb
 28e0b7827cdf0a3d0aa6b6d4df839abbe1b61783 179848 libroar2_1.0~beta11-6_amd64.deb
 a8263ab8024d993c310c85ac6ce9c4f4e8751965 1374324 
roaraudio-dbg_1.0~beta11-6_amd64.deb
 c4229a9f184e8ac68b866398a0b00be73f393874 150018 
roaraudio_1.0~beta11-6_amd64.deb
 a24d1154121d466ca54e9c400ac58a7a850597e8 100328 
roarclients_1.0~beta11-6_amd64.deb
Checksums-Sha256:
 d6591215f2a617ffe1bbad6eba21568de0357870085e42289ec1a3a98d073584 2416 
roaraudio_1.0~beta11-6.dsc
 6d8e8ee488c1ec0b6d21c73de62829de4957e2928561f5ee4a63a4f9dc04e61c 31896 
roaraudio_1.0~beta11-6.debian.tar.xz
 371886b2b5de8b294dd36cb616239fa1f211aa43c56b07d4d7896ee5b65d1403 20910 
libroar-compat-tools_1.0~beta11-6_amd64.deb
 84fface02c13b170327b29130288004cd91b0f94a414c2827690b2066d138a8a 55518 
libroar-compat2_1.0~beta11-6_amd64.deb
 5acd1651158abb612a71abf86025595a6db48bda824dd33d4e956f05572e9799 234224 
libroar-dev_1.0~beta11-6_amd64.deb
 37b45fa56b17a6308dab8bba76689b19f36d42b88a64a95d4fe19323af019939 38108 
libroar-plugins-universal_1.0~beta11-6_amd64.deb
 

Bug#813819: MIA Ping

[Tino Mettler]

On Thu, Feb 25, 2016 at 10:51:38 +0100, Joachim Breitner wrote:
> Dear Tino,
> 
> this is just a ping whether you are still an active Debian maintainer.
> The RC bug #813819 should be a matter of a simple change and upload...

Hi,

yes, I am. The simple change is not as simple as it seems. It got a
(not very verbose) build error in pbuilder and got no time for
investigating, yet. I'll ask for help if I can't figure it out this
evening.

Regards,
Tino

Bug#815879: RM: ftpbackup -- ROM; Following the discussions on debian-devel, I realize the program is not ready to integrate Debian

[Carl Chenet]

Hi Thomas,

Thanks for the reports. I realized ftpbackup is not ready to enter into
Debian so I requested ftpmasters to remove it.

Regards,
-- 
Carl Chenet

Fondateur de linuxjobs.fr et du journalduhacker.net
Blog : https://carlchenet.com
Twitter: https://twitter.com/carl_chenet
D*: https://framasphere.org/people/50358020451f013251102a053625

Processed: notfixed 782330 in 0.3.3-2, fixed 782330 in 1:0.3.3-2

[Debian Bug Tracking System]

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

> notfixed 782330 0.3.3-2
Bug #782330 {Done: Timo Aaltonen } 
[src:xserver-xorg-video-openchrome] FTBFS with libc6-dev >= 2.21: 
/usr/include/xorg/os.h:579:1: error: expected identifier or '(' before 
'__extension__' strndup(const char *str, size_t n);
Bug #807705 {Done: Timo Aaltonen } 
[src:xserver-xorg-video-openchrome] xserver-xorg-video-openchrome: FTBFS: 
/usr/include/xorg/os.h:558:1: error: expected identifier or '(' before 
'__extension__'
The source 'xserver-xorg-video-openchrome' and version '0.3.3-2' do not appear 
to match any binary packages
No longer marked as fixed in versions xserver-xorg-video-openchrome/0.3.3-2.
No longer marked as fixed in versions xserver-xorg-video-openchrome/0.3.3-2.
> fixed 782330 1:0.3.3-2
Bug #782330 {Done: Timo Aaltonen } 
[src:xserver-xorg-video-openchrome] FTBFS with libc6-dev >= 2.21: 
/usr/include/xorg/os.h:579:1: error: expected identifier or '(' before 
'__extension__' strndup(const char *str, size_t n);
Bug #807705 {Done: Timo Aaltonen } 
[src:xserver-xorg-video-openchrome] xserver-xorg-video-openchrome: FTBFS: 
/usr/include/xorg/os.h:558:1: error: expected identifier or '(' before 
'__extension__'
Marked as fixed in versions xserver-xorg-video-openchrome/1:0.3.3-2.
Marked as fixed in versions xserver-xorg-video-openchrome/1:0.3.3-2.
> thanks
Stopping processing here.

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

Bug#813746: marked as done (ruby-hipchat: FTBFS: Real HTTP connections are disabled. Unregistered request: GET)

[Debian Bug Tracking System]

Your message dated Thu, 25 Feb 2016 10:09:02 +
with message-id 
and subject line Bug#813746: fixed in ruby-hipchat 1.5.2-2
has caused the Debian Bug report #813746,
regarding ruby-hipchat: FTBFS: Real HTTP connections are disabled. Unregistered 
request: GET
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.)


-- 
813746: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=813746
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: ruby-hipchat
Version: 1.5.2-1
Severity: serious
Justification: fails to build from source
User: reproducible-bui...@lists.alioth.debian.org
Usertags: ftbfs
X-Debbugs-Cc: reproducible-bui...@lists.alioth.debian.org

Dear Maintainer,

ruby-hipchat fails to build from source in unstable/amd64:

  [..]
  
  
RUBYLIB=/home/lamby/temp/cdt.20160204233035.u8eNtVVitE/ruby-hipchat-1.5.2/debian/ruby-hipchat/usr/lib/ruby/vendor_ruby:.
 
GEM_PATH=/home/lamby/.gem/ruby/2.2.0:/var/lib/gems/2.2.0:/usr/lib/x86_64-linux-gnu/rubygems-integration/2.2.0:/usr/share/rubygems-integration/2.2.0:/usr/share/rubygems-integration/2.2:/usr/share/rubygems-integration/all:debian/ruby-hipchat/usr/share/rubygems-integration/all
 ruby2.2 -S rake -f debian/ruby-tests.rake
  /usr/bin/ruby2.2 /usr/bin/rspec --pattern ./spec/\*\*/\*_spec.rb
  warning: coveralls gem not found; skipping coverage
  .FF...
  
  Failures:
  
1) HipChat (API V2) #statistics is successful without custom options
   Failure/Error: expect(room.statistics()).to be_truthy
   WebMock::NetConnectNotAllowedError:
 Real HTTP connections are disabled. Unregistered request: GET 
https://api.hipchat.com/v2/room/Hipchat/statistics?auth_token=blah==_id=Hipchat=
 with headers {'Accept'=>'application/json', 'Content-Type'=>'application/json'}
 
 You can stub this request with the following snippet:
 
 stub_request(:get, 
"https://api.hipchat.com/v2/room/Hipchat/statistics?auth_token=blah==_id=Hipchat=;).
   with(:headers => {'Accept'=>'application/json', 
'Content-Type'=>'application/json'}).
   to_return(:status => 200, :body => "", :headers => {})
 
 registered request stubs:
 
 stub_request(:get, 
"https://api.hipchat.com/v2/room/Hipchat/statistics?auth_token=blah_id=Hipchat;)
 
 
   # ./lib/hipchat/room.rb:269:in `statistics'
   # ./spec/hipchat_api_v2_spec.rb:61:in `block (3 levels) in '
  
2) HipChat (API V2) #statistics is successful from fetched room
   Failure/Error: expect(subject.rooms.first.statistics).to be_truthy
   WebMock::NetConnectNotAllowedError:
 Real HTTP connections are disabled. Unregistered request: GET 
https://api.hipchat.com/v2/room/Hipchat/statistics?auth_token=blah==_id=Hipchat=
 with headers {'Accept'=>'application/json', 'Content-Type'=>'application/json'}
 
 You can stub this request with the following snippet:
 
 stub_request(:get, 
"https://api.hipchat.com/v2/room/Hipchat/statistics?auth_token=blah==_id=Hipchat=;).
   with(:headers => {'Accept'=>'application/json', 
'Content-Type'=>'application/json'}).
   to_return(:status => 200, :body => "", :headers => {})
 
 registered request stubs:
 
 stub_request(:get, 
"https://api.hipchat.com/v2/room/Hipchat/statistics?auth_token=blah_id=Hipchat;)
 stub_request(:get, "https://api.hipchat.com/v2/room?auth_token=blah;).
   with(:body => "",
:headers => {'Accept'=>'application/json', 
'Content-Type'=>'application/json'})
 
 
   # ./lib/hipchat/room.rb:269:in `statistics'
   # ./spec/hipchat_api_v2_spec.rb:69:in `block (3 levels) in '
  
  Finished in 0.17968 seconds (files took 0.60475 seconds to load)
  74 examples, 2 failures
  
  Failed examples:
  
  rspec ./spec/hipchat_api_v2_spec.rb:58 # HipChat (API V2) #statistics is 
successful without custom options
  rspec ./spec/hipchat_api_v2_spec.rb:64 # HipChat (API V2) #statistics is 
successful from fetched room
  
  /usr/bin/ruby2.2 /usr/bin/rspec --pattern ./spec/\*\*/\*_spec.rb failed
  ERROR: Test "ruby2.2" failed. Exiting.
  dh_auto_install: dh_ruby --install 
/home/lamby/temp/cdt.20160204233035.u8eNtVVitE/ruby-hipchat-1.5.2/debian/ruby-hipchat
 returned exit code 1
  debian/rules:15: recipe for target 'binary' 

Bug#815842: marked as done (php-rrd source incorrectly references imagick-*)

[Debian Bug Tracking System]

Your message dated Thu, 25 Feb 2016 10:07:04 +
with message-id 
and subject line Bug#815842: fixed in php-rrd 2.0.0+1.1.3-3
has caused the Debian Bug report #815842,
regarding php-rrd source incorrectly references imagick-*
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.)


-- 
815842: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=815842
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: php-rrd
Version: 2.0.0+1.1.3-2
Severity: serious
Justification: fails to build from source (but built successfully in the past)

Dear Maintainer,

debian/tests/control lists:

Test-Command: cd imagick-* && phpunit --verbose tests
Depends: php-cli, php-imagick, phpunit

which I believe has been copied unaltered from php-imagick. This
obviously fails with php-rrd.

-Nish
--- End Message ---
--- Begin Message ---
Source: php-rrd
Source-Version: 2.0.0+1.1.3-3

We believe that the bug you reported is fixed in the latest version of
php-rrd, 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 815...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Ondřej Surý  (supplier of updated php-rrd 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, 25 Feb 2016 09:46:07 +0100
Source: php-rrd
Binary: php-rrd
Architecture: source amd64
Version: 2.0.0+1.1.3-3
Distribution: unstable
Urgency: medium
Maintainer: Debian PHP PECL Maintainers 
Changed-By: Ondřej Surý 
Description:
 php-rrd- PHP bindings to rrd tool system
Closes: 815842
Changes:
 php-rrd (2.0.0+1.1.3-3) unstable; urgency=medium
 .
   * Remove autopkgtest copied from imagemagick (Closes: #815842)
Checksums-Sha1:
 ff456e35b7b9f7792de947303453f1af99f4c822 2118 php-rrd_2.0.0+1.1.3-3.dsc
 77cf85ae532a4a90d7425bd53c96df2351cc3a55 3120 
php-rrd_2.0.0+1.1.3-3.debian.tar.xz
 21a7af71f04df4bf919b4ec32ae912ceec0f01af 45100 
php-rrd-dbgsym_2.0.0+1.1.3-3_amd64.deb
 8fff42c0fcaa32bbc48dfefe92c4f34b77105426 14290 php-rrd_2.0.0+1.1.3-3_amd64.deb
Checksums-Sha256:
 5ef174bf848f17a270ab8312511621f5bd8dcb9513dc5aa1c8d0b2667fcfafc3 2118 
php-rrd_2.0.0+1.1.3-3.dsc
 35a7e9c42c64fba47f4443f2f7c44ede4c20361e5e17bdd25626e15f76e7bf0e 3120 
php-rrd_2.0.0+1.1.3-3.debian.tar.xz
 eb3745bbc625dd0cc73e6ecf130225dedff52e86e164d2312776f152081869ab 45100 
php-rrd-dbgsym_2.0.0+1.1.3-3_amd64.deb
 3f17baa16b91b1192b8202ee66e1ea109a5049201b3aba7d3679931a607b3d2a 14290 
php-rrd_2.0.0+1.1.3-3_amd64.deb
Files:
 278bab87b3054074986ba726fddea304 2118 php optional php-rrd_2.0.0+1.1.3-3.dsc
 2ee34592fb1d26e1e877f9303457ff49 3120 php optional 
php-rrd_2.0.0+1.1.3-3.debian.tar.xz
 4d1944493d67215fb1b468ef97084745 45100 debug extra 
php-rrd-dbgsym_2.0.0+1.1.3-3_amd64.deb
 c385def1ea9ff176ac09d87381dfd736 14290 php optional 
php-rrd_2.0.0+1.1.3-3_amd64.deb

-BEGIN PGP SIGNATURE-
Version: GnuPG v2

iQJ8BAEBCgBmBQJWzsAXXxSAAC4AKGlzc3Vlci1mcHJAbm90YXRpb25zLm9w
ZW5wZ3AuZmlmdGhob3JzZW1hbi5uZXQzMEI5MzNEODBGQ0UzRDk4MUEyRDM4RkIw
Qzk5QjcwRUY0RkNCQjA3AAoJEAyZtw70/LsHk5MP/2392sj2dluud4tDmjZCN5Wl
sUWlwBLOLgE9Yqp2ey19y5xE4R6qiGvQthZ+MYDxROaNrXQ5/HlTSwZ9HU9fpGGk
IuyETGjVyvIYKn4PNNTrVz6CzffvU803xRg4k/2bl260h+vQnX8+0bSQk6a4sjmH
FoxfAgwZmDdwSUcax8rCJ2gL/vmTdpr0BZ3RmCJFcUO7Svra7elDlZZ0UjaUB8vz
G5h9z656H3Uxy9u8tZyXZEsBkGtQAfW8AFYiZQHlaArnz3THRVae7mt2fnjDemNv
xGXn7Z5dskhxVCPbKQKuuQTJuFK5s1Wal0xOFtZhxkFR44PQwGvgOSWjIjqSpItD
6w29Y+JtWJgt3f+n394jzo4v9yaTTTiimb5X+Kve44NX41TOcS5kSZyZXvowhnR0
iHVBhxDs3rOuJdIhJgvmyx16+inM3fVA0UjDzZugMTUtwcMu8YQ2ckzyMuB4FUEG
rbBNVmyW5m7ZO4hSEJEkPxA3tmX79zOr570oxtX7EX35gA3Hldu9MhRS3I2ph87V
aSNxfzrNCyw9B/P4PpORmiq2EGwI2Kz2roAhqfABToNvp6pDldwwqG6kV7YeGrrT
U1jINgi9Wdke4FerReGGKxGQjXmGkXIKMHQqLknCHJhP0XYonr5UuFkrmoVcTog9
I/p3Kohe8NSbMzrs7DaU
=Zsx8
-END PGP SIGNATURE End Message ---

Processed: duplicates

[Debian Bug Tracking System]

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

> reassign 815783 src:r-cran-arm
Bug #815783 [r-cran-arm] r-cran-arm: FTBFS - dependencies are not available for 
package 'arm'
Bug reassigned from package 'r-cran-arm' to 'src:r-cran-arm'.
No longer marked as found in versions r-cran-arm/1.8-6-1.
Ignoring request to alter fixed versions of bug #815783 to the same values 
previously set
> merge 815783 815741
Bug #815783 [src:r-cran-arm] r-cran-arm: FTBFS - dependencies are not available 
for package 'arm'
Bug #815783 [src:r-cran-arm] r-cran-arm: FTBFS - dependencies are not available 
for package 'arm'
Marked as found in versions r-cran-arm/1.8-6-1.
Bug #815741 [src:r-cran-arm] r-cran-arm: FTBFS: ERROR: dependencies 'MASS', 
'Matrix', 'lme4', 'abind', 'coda', 'nlme' are not available for package 'arm'
Merged 815741 815783
>
End of message, stopping processing here.

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

Processed: bug 812710 is forwarded to https://github.com/nose-devs/nose2/issues/276

[Debian Bug Tracking System]

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

> forwarded 812710 https://github.com/nose-devs/nose2/issues/276
Bug #812710 [nose2] nose2: FTBFS - multiple test failures
Changed Bug forwarded-to-address to 
'https://github.com/nose-devs/nose2/issues/276' from 
'https://github.com/nose-devs/nose2/issues/273'
> thanks
Stopping processing here.

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

Processed: retitle 815872 to ftpbackup sends unencrypted backups over FTP

[Debian Bug Tracking System]

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

> # fix typo
> retitle 815872 ftpbackup sends unencrypted backups over FTP
Bug #815872 [ftpbackup] ftpbackup sends enencrypted backups over FTP
Changed Bug title to 'ftpbackup sends unencrypted backups over FTP' from 
'ftpbackup sends enencrypted backups over FTP'
> thanks
Stopping processing here.

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

Bug#811442: marked as done (conkeror: does not want to run)

[Debian Bug Tracking System]

Your message dated Thu, 25 Feb 2016 09:48:04 +
with message-id 
and subject line Bug#795597: fixed in conkeror 1.0~~pre-1+git141025-1+deb8u1
has caused the Debian Bug report #795597,
regarding conkeror: does not want to run
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.)


-- 
795597: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=795597
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: conkeror
Version: 1.0~~pre-1+git141025-1
Severity: grave
Justification: renders package unusable

Dear Maintainer,

It won't run.

--> conkeror

(process:2696): GLib-CRITICAL **: g_slice_set_config: assertion 'sys_page_size 
== 0' failed
JavaScript strict warning: resource://gre/modules/GMPUtils.jsm, line 92: 
ReferenceError: reference to undefined property this.KEY_LOG_BASE
JavaScript strict warning: chrome://conkeror/content/keywords.js, line 20: 
SyntaxError: in strict mode code, functions may be declared only at top level 
or immediately within another function
JavaScript strict warning: chrome://conkeror/content/keywords.js, line 30: 
SyntaxError: in strict mode code, functions may be declared only at top level 
or immediately within another function
JavaScript strict warning: chrome://conkeror/content/keywords.js, line 62: 
SyntaxError: in strict mode code, functions may be declared only at top level 
or immediately within another function
JavaScript strict warning: chrome://conkeror/content/keywords.js, line 68: 
SyntaxError: in strict mode code, functions may be declared only at top level 
or immediately within another function
JavaScript strict warning: chrome://conkeror/content/keywords.js, line 72: 
SyntaxError: in strict mode code, functions may be declared only at top level 
or immediately within another function
JavaScript warning: chrome://conkeror/content/coroutine.js, line 354: mutating 
the [[Prototype]] of an object will cause your code to run very slowly; instead 
create the object with the correct initial [[Prototype]] value using 
Object.create
JavaScript warning: chrome://conkeror/content/debug.js, line 87: JavaScript 
1.7's let blocks are deprecated
JavaScript strict warning: chrome://conkeror/content/env.js, line 16: 
SyntaxError: in strict mode code, functions may be declared only at top level 
or immediately within another function
JavaScript warning: chrome://conkeror/content/env.js, line 15: JavaScript 1.7's 
let blocks are deprecated
JavaScript strict warning: chrome://conkeror/content/env.js, line 42: 
SyntaxError: in strict mode code, functions may be declared only at top level 
or immediately within another function
JavaScript warning: chrome://conkeror/content/env.js, line 41: JavaScript 1.7's 
let blocks are deprecated
JavaScript strict warning: chrome://conkeror/content/env.js, line 79: 
SyntaxError: in strict mode code, functions may be declared only at top level 
or immediately within another function
JavaScript warning: chrome://conkeror/content/env.js, line 78: JavaScript 1.7's 
let blocks are deprecated
JavaScript strict warning: chrome://conkeror/content/utils.js, line 207: 
SyntaxError: octal literals and octal escape sequences are deprecated
JavaScript strict warning: chrome://conkeror/content/utils.js, line 207: 
SyntaxError: octal literals and octal escape sequences are deprecated
JavaScript strict warning: chrome://conkeror/content/utils.js, line 207: 
SyntaxError: octal literals and octal escape sequences are deprecated
JavaScript strict warning: 
file:///usr/share/conkeror/components/application.js, line 167: ReferenceError: 
reference to undefined property (intermediate value)[e]
Error initializing.
Error: Error opening input stream (invalid filename?): 
chrome://conkeror/content/io
JavaScript error: file:///usr/share/conkeror/components/command-line.js, line 
23: TypeError: conkeror.handle_command_line is not a function
Console error: [JavaScript Warning: "SyntaxError: in strict mode code, 
functions may be declared only at top level or immediately within another 
function" {file: "chrome://conkeror/content/env.js" line: 16 column: 13 source: 
"function get_os () {
"}]
  Category: chrome javascript
Console error: [JavaScript Warning: "JavaScript 1.7's let blocks are 
deprecated" {file: "chrome://conkeror/content/env.js" line: 15}]
  Category: chrome javascript
Console error: [JavaScript Warning: "SyntaxError: in strict mode code, 
functions may be declared only at top level or immediately within another 
function" {file: "chrome://conkeror/content/env.js" line: 42 column: 13 source: 
"function getenv 

Bug#792685: marked as done (Unable to upgrade from wheezy to jessie)

[Debian Bug Tracking System]

Your message dated Thu, 25 Feb 2016 09:48:11 +
with message-id 
and subject line Bug#792685: fixed in s3ql 2.11.1+dfsg-3
has caused the Debian Bug report #792685,
regarding Unable to upgrade from  wheezy to  jessie
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.)


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

package: s3ql
severity: grave
version: 2.11.1+dfsg-1
Justification: Renders filesystem unusable and data accessible

Hi.
I'm upgrading a system from wheezy to jessie.
Wheezy ships s3ql 1.11, jessie ships version 2.11.

I have a filesystem that I can easily mount and fsck in wheezy, but when
I try to run the jessie s3qladm upgrade command I get:
Getting file system parameters..

File system revision too old to upgrade!

You need to use an older S3QL version to upgrade to a more recent
revision before you can use this version to upgrade to the newest
revision.

Uncaught top-level exception:
Traceback (most recent call last):
  File "/usr/bin/s3qladm", line 9, in 
  load_entry_point('s3ql==2.11.1', 'console_scripts', 's3qladm')()
File "/usr/lib/s3ql/s3ql/adm.py", line 96, in main
options.cachedir))
  File "/usr/lib/s3ql/s3ql/adm.py", line 316, in upgrade
  print(get_old_rev_msg(param['revision'] + 1, 's3qladm'))
File "/usr/lib/s3ql/s3ql/adm.py", line 224, in 
get_old_rev_msg
''' % { 'version': REV_VER_MAP[rev],
KeyError: 17


It's critical that there be a documented procedure that works for
upgrading from the version in wheezy to the version in jessie using
tools in jessie.


There was another upgrade at version 2.5, which is not in either wheezy
or jessie.  However, it needs to be possible to upgrade from one Debian
release to the next using the software in Debian.


I believe this problem is important enough to fix in a Jessie point
release and would be happy to help with any process issues that come up
in making that happen.


pgpTsHSVI0OT7.pgp
Description: PGP signature
--- End Message ---
--- Begin Message ---
Source: s3ql
Source-Version: 2.11.1+dfsg-3

We believe that the bug you reported is fixed in the latest version of
s3ql, 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 792...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Nikolaus Rath  (supplier of updated s3ql 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, 19 Jul 2015 19:30:10 -0700
Source: s3ql
Binary: s3ql s3ql-dbg
Architecture: source amd64
Version: 2.11.1+dfsg-3
Distribution: jessie
Urgency: medium
Maintainer: Nikolaus Rath 
Changed-By: Nikolaus Rath 
Description:
 s3ql   - Full-featured file system for online data storage
 s3ql-dbg   - Full-featured file system for online data storage (debugging symb
Closes: 792685
Changes:
 s3ql (2.11.1+dfsg-3) jessie; urgency=medium
 .
   * Add support to upgrade from file systems created with the
 S3QL version in Debian Wheezy. Closes: #792685.
Checksums-Sha1:
 070041160e8fb5464f6d1b81cf515cefe28e 2582 s3ql_2.11.1+dfsg-3.dsc
 fe9defe74e3ab5ce523dbeddd744b541a964a828 12300 s3ql_2.11.1+dfsg-3.debian.tar.xz
 45dda448374526350c78e83017314eb676efce20 557726 s3ql_2.11.1+dfsg-3_amd64.deb
 8875269061a5c846f1cb8ca433fedaf807759752 289564 
s3ql-dbg_2.11.1+dfsg-3_amd64.deb
Checksums-Sha256:
 0b5caaf114d5f0747ee75bd402987142a95536cef6c15c9ceeb118791987eb57 2582 
s3ql_2.11.1+dfsg-3.dsc
 9971227fc65117f74649bdbd39ce186e0a1fb6190cf0a89b671a67c4c9e988d2 12300 
s3ql_2.11.1+dfsg-3.debian.tar.xz
 5a952b2d479369259928dad176eba72857e985b4424908d192aa858255b9f770 557726 
s3ql_2.11.1+dfsg-3_amd64.deb
 6f7c2e0de7ad690a317a9b35e3fc097723cf864b4277e904e416c4618eeff0e0 289564 
s3ql-dbg_2.11.1+dfsg-3_amd64.deb
Files:
 7b5ceaa8765b434f73d2fb556c9f4253 2582 misc optional s3ql_2.11.1+dfsg-3.dsc
 bb685c6ef887473b1e5352a66e342b51 12300 misc optional 
s3ql_2.11.1+dfsg-3.debian.tar.xz
 

Bug#795597: marked as done (Conkeror crashes on start up with SyntaxError, ReferenceError and TypeError)

[Debian Bug Tracking System]

Your message dated Thu, 25 Feb 2016 09:48:04 +
with message-id 
and subject line Bug#795597: fixed in conkeror 1.0~~pre-1+git141025-1+deb8u1
has caused the Debian Bug report #795597,
regarding Conkeror crashes on start up with SyntaxError, ReferenceError and 
TypeError
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.)


-- 
795597: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=795597
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: conkeror
Version: 1.0~~pre-1+git141025-1

When starting conkeror it crashes with following message:

(process:29288): GLib-CRITICAL **: g_slice_set_config: assertion 'sys_page_size 
== 0' failed
JavaScript strict warning: resource://gre/modules/GMPUtils.jsm, line 92: 
ReferenceError: reference to undefined property this.KEY_LOG_BASE
JavaScript strict warning: chrome://conkeror/content/keywords.js, line 20: 
SyntaxError: in strict mode code, functions may be declared only at top level 
or immediately within another function
JavaScript strict warning: chrome://conkeror/content/keywords.js, line 30: 
SyntaxError: in strict mode code, functions may be declared only at top level 
or immediately within another function
JavaScript strict warning: chrome://conkeror/content/keywords.js, line 62: 
SyntaxError: in strict mode code, functions may be declared only at top level 
or immediately within another function
JavaScript strict warning: chrome://conkeror/content/keywords.js, line 68: 
SyntaxError: in strict mode code, functions may be declared only at top level 
or immediately within another function
JavaScript strict warning: chrome://conkeror/content/keywords.js, line 72: 
SyntaxError: in strict mode code, functions may be declared only at top level 
or immediately within another function
JavaScript warning: chrome://conkeror/content/coroutine.js, line 354: mutating 
the [[Prototype]] of an object will cause your code to run very slowly; instead 
create the object with the correct initial [[Prototype]] value using 
Object.create
JavaScript warning: chrome://conkeror/content/debug.js, line 87: JavaScript 
1.7's let blocks are deprecated
JavaScript strict warning: chrome://conkeror/content/env.js, line 16: 
SyntaxError: in strict mode code, functions may be declared only at top level 
or immediately within another function
JavaScript warning: chrome://conkeror/content/env.js, line 15: JavaScript 1.7's 
let blocks are deprecated
JavaScript strict warning: chrome://conkeror/content/env.js, line 42: 
SyntaxError: in strict mode code, functions may be declared only at top level 
or immediately within another function
JavaScript warning: chrome://conkeror/content/env.js, line 41: JavaScript 1.7's 
let blocks are deprecated
JavaScript strict warning: chrome://conkeror/content/env.js, line 79: 
SyntaxError: in strict mode code, functions may be declared only at top level 
or immediately within another function
JavaScript warning: chrome://conkeror/content/env.js, line 78: JavaScript 1.7's 
let blocks are deprecated
JavaScript strict warning: chrome://conkeror/content/utils.js, line 207: 
SyntaxError: octal literals and octal escape sequences are deprecated
JavaScript strict warning: chrome://conkeror/content/utils.js, line 207: 
SyntaxError: octal literals and octal escape sequences are deprecated
JavaScript strict warning: chrome://conkeror/content/utils.js, line 207: 
SyntaxError: octal literals and octal escape sequences are deprecated
JavaScript strict warning: 
file:///usr/share/conkeror/components/application.js, line 167: ReferenceError: 
reference to undefined property (intermediate value)[e]
Error initializing.
Error: Error opening input stream (invalid filename?): 
chrome://conkeror/content/io
JavaScript error: file:///usr/share/conkeror/components/command-line.js, line 
23: TypeError: conkeror.handle_command_line is not a function
Console error: [JavaScript Warning: "SyntaxError: in strict mode code, 
functions may be declared only at top level or immediately within another 
function" {file: "chrome://conkeror/content/env.js" line: 16 column: 13 source: 
"function get_os () {
"}]
  Category: chrome javascript
Console error: [JavaScript Warning: "JavaScript 1.7's let blocks are 
deprecated" {file: "chrome://conkeror/content/env.js" line: 15}]
  Category: chrome javascript
Console error: [JavaScript Warning: "SyntaxError: in strict mode code, 
functions may be declared only at top level or immediately within another 
function" {file: "chrome://conkeror/content/env.js" line: 42 column: 13 source: 
"function 

Bug#815853: marked as done (Cannot modprobe due to wrong kernel version string)

[Debian Bug Tracking System]

Your message dated Thu, 25 Feb 2016 18:40:18 +0900
with message-id 

and subject line Re: Bug#815853: Cannot modprobe due to wrong kernel version 
string
has caused the Debian Bug report #815853,
regarding Cannot modprobe due to wrong kernel version string
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.)


-- 
815853: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=815853
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: linux-image-3.16.0-4-armmp-lpae
Version: 3.16.7-ckt20-1+deb8u2
Severity: grave

The package installs modules in /lib/modules/3.16.0-4-armmp-lpae
but uname -r returns
3.16.0-4-armmp

This means that modules cannot be loaded, e.g.

$ sudo modprobe nls_cp437
modprobe: ERROR: ../libkmod/libkmod.c:557 kmod_search_moddep() could not
open moddep file '/lib/modules/3.16.0-4-armmp/modules.dep.bin'

For lpae kernels append -lpae to the kernel version string.

Best regards

Heinrich Schuchardt
--- End Message ---
--- Begin Message ---
On Thu, Feb 25, 2016 at 3:57 PM, Heinrich Schuchardt  wrote:
> The error was caused by the system not using the kernel installed in
> /boot but reading it from /dev/mmcblk0p1.
>
> Please, close the message.

Thanks for your report and clarification!--- End Message ---

Bug#815880: Fails to update /etc/resolv.conf with network-manager 1.1.90

[Gaudenz Steinlin]

Package: dnssec-trigger
Version: 0.13~svn685-4+b1
Severity: grave
Tags: patch

The /usr/lib/dnssec-trigger/dnssec-trigger-script fails to update
/etc/resolv.conf with the version of network-manager now in
testing and unstable. The problem is that calls to
client.get_manager_running() return False even if NetworkManager is
running. This is caused by imporper initialization of the client object.

According to https://bugzilla.redhat.com/show_bug.cgi?id=1229337 the
client object should be created with NMClient.Client().new() instead of
just using NMClient.Client(). The attached patch fixes this and resolves
the issue.

The patch also adds the recommended GI version specification before
importing NMClient. This currently only avoids a warning and if you
don't like that part you can also apply the patch without it.

Gaudenz

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

Kernel: Linux 4.3.0-1-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=de_CH.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages dnssec-trigger depends on:
ii  gir1.2-networkmanager-1.0  1.1.90-6
ii  init-system-helpers1.28
ii  libc6  2.21-9
ii  libgdk-pixbuf2.0-0 2.32.3-1.2
ii  libglib2.0-0   2.46.2-3
ii  libgtk2.0-02.24.29-1
ii  libldns1   1.6.17-8
ii  libssl1.0.21.0.2f-2
ii  python 2.7.11-1
ii  python-gi  3.18.2-2
ii  python-lockfile1:0.10.2-2
ii  unbound1.5.7-1

dnssec-trigger recommends no packages.

dnssec-trigger suggests no packages.

-- no debconf information

-- debsums errors found:
debsums: changed file /usr/lib/dnssec-trigger/dnssec-trigger-script (from 
dnssec-trigger package)
--- /usr/lib/dnssec-trigger/dnssec-trigger-script.orig	2016-02-25 10:17:23.296285495 +0100
+++ /usr/lib/dnssec-trigger/dnssec-trigger-script	2016-02-25 10:34:25.856239132 +0100
@@ -5,6 +5,8 @@
 @author: Pavel Šimerda 
 """
 
+import gi
+gi.require_version('NMClient', '1.0')
 from gi.repository import NMClient
 import os, sys, shutil, glob, subprocess
 import logging, logging.handlers
@@ -333,7 +335,7 @@
 except AttributeError:
 self.usage()
 self.config = Config()
-self.client = NMClient.Client()
+self.client = NMClient.Client().new()
 
 self.resolvconf = "/etc/resolv.conf"
 self.resolvconf_backup = "/run/dnssec-trigger/resolv.conf.bak"

Bug#815879: disables opportunistic TLS

[Thomas Goirand]

Package: ftpbackup
Version: 0.3-1
Severity: critical
Tags: security

> # remove old archive on the FTP
> lftp -e "set ftp:ssl-allow no; 

Not only this program lets the backups be sent over unencrypted channel, but
it even disables opportunistic TLS.

Processed (with 1 error): duplicates

[Debian Bug Tracking System]

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

> merge 815397 815373
Bug #815397 [src:r-cran-tm] r-cran-tm: FTBFS: ERROR: dependencies 'NLP', 'slam' 
are not available for package 'tm'
Bug #815373 [src:r-cran-tm] r-cran-tm: FTBFS: dependencies 'NLP', 'slam' are 
not available
Merged 815373 815397
> merge 815783 815741
Bug #815783 [r-cran-arm] r-cran-arm: FTBFS - dependencies are not available for 
package 'arm'
Unable to merge bugs because:
package of #815741 is 'src:r-cran-arm' not 'r-cran-arm'
Failed to merge 815783: Did not alter merged bugs.

>
End of message, stopping processing here.

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

Bug#815878: Creates backup folders world readable

[Thomas Goirand]

Package: ftpbackup
Version: 0.3-1
Severity: critical
Tags: security

As per Jakub's message in debian-devel:

> # create BACKUPHOME if not exists
> mkdir -p $BACKUPHOME

No umask set anywhere in this script, so in default setup the directory (and
later, the backup files) will be created readable to anyone.

Bug#815877: ghostscript: FTBFS on several architectures

[Emilio Pozuelo Monfort]

Package: ghostscript
Version: 9.18~dfsg-4
Severity: serious

Your package failed to build on several architectures, see:

https://buildd.debian.org/status/package.php?p=ghostscript=sid

Emilio

Processed: Still not fixed

[Debian Bug Tracking System]

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

> reopen 815047
Bug #815047 {Done: LaMont Jones } [postfix] postfix: Postfix 
fails to start after upgrade
Bug #815070 {Done: LaMont Jones } [postfix] postfix: does 
not start
Bug #815538 {Done: LaMont Jones } [postfix] postfix: Does 
not start after upgrading to 3.0.3-1 - instance conflicts
Bug #815622 {Done: LaMont Jones } [postfix] Postfix fails to 
start after apt-get upgrade
'reopen' may be inappropriate when a bug has been closed with a version;
all fixed versions will be cleared, and you may need to re-add them.
Bug reopened
No longer marked as fixed in versions postfix/3.0.4-3.
No longer marked as fixed in versions postfix/3.0.4-3.
No longer marked as fixed in versions postfix/3.0.4-3.
No longer marked as fixed in versions postfix/3.0.4-3.
> thanks
Stopping processing here.

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

Bug#815047: Still not fixed

[Michael Meskes]

reopen 815047
thanks

Still not fixed. It seems the latest fix didn't make it into the package for
some reason. Manually setting

shlib_directory=/usr/lib/postfix
daemon_directory=/usr/lib/postfix/sbin

in main.cf fixes the problem for me, but obviously the upgrade shouldn't need
such manual config change.

Michael
-- 
Michael Meskes
Michael at Fam-Meskes dot De, Michael at Meskes dot (De|Com|Net|Org)
Meskes at (Debian|Postgresql) dot Org
Jabber: michael at xmpp dot meskes dot org
VfL Borussia! Força Barça! Go SF 49ers! Use Debian GNU/Linux, PostgreSQL

Bug#815872: ftpbackup sends enencrypted backups over FTP

[Thomas Goirand]

Package: ftpbackup
Version: 0.3-1
Severity: critical

ftpbackup is sending a non-encrypted copy of most sensitive files of a system,
including all what's in /etc and /home, and all of the MySQL database over
an FTP link, and to potentially non-trusted 3rd party FTP areas. Its author
even claims that it is the right fit for sending it over the FTP space of
French ISPs. It certainly is not the case.

Please don't allow this software to migrate to Testing until this issue is
addressed correctly. Also, some kind of upper case huge warning should at
least have been added to the long description, but it hasn't been done, which
may lead to miss-use by unexperienced users.

Processed: Header renamed in protozero 1.3.0

[Debian Bug Tracking System]

Processing control commands:

> tags -1 upstream confirmed
Bug #815869 [src:osmium-tool] osmium-tool: FTBFS: protobuf_tags.hpp:36:35: 
fatal error: protozero/pbf_types.hpp: No such file or directory
Added tag(s) confirmed and upstream.

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

Processed: Header renamed in protozero 1.3.0

[Debian Bug Tracking System]

Processing control commands:

> tags -1 upstream confirmed
Bug #815868 [src:osmcoastline] osmcoastline: FTBFS: protobuf_tags.hpp:36:35: 
fatal error: protozero/pbf_types.hpp: No such file or directory
Added tag(s) upstream and confirmed.

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

Bug#815868: Header renamed in protozero 1.3.0

[Bas Couwenberg]

Control: tags -1 upstream confirmed

Hi Chris,

Thanks for reporting these issues.

They are caused by the renaming of the header to types.hpp in protozero 
1.3.0.


This has been fixed in libosmium 2.6.1 released a few days ago.

Updating the libosmium package to 2.6.1 should resolve these issues.

Kind Regards,

Bas

Bug#797293: marked as done (votca-tools: rename needed for libstdc++ ABI transition)

[Debian Bug Tracking System]

Your message dated Thu, 25 Feb 2016 08:00:24 +
with message-id 
and subject line Bug#797293: fixed in votca-tools 1.3.0-1
has caused the Debian Bug report #797293,
regarding votca-tools: rename needed for libstdc++ ABI transition
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.)


-- 
797293: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=797293
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: votca-csg
Version: 1.2.4-1
Severity: serious
Justification: FTBFS

This package FTBFS in a clean sid chroot:

CMakeFiles/csg_dump.dir/csg_dump.cc.o:(.data.rel.ro._ZTV10CsgDumpApp[_ZTV10CsgDu
mpApp]+0x28): undefined reference to `votca::tools::Application::VersionString[a
bi:cxx11]()'
../libcsg/libvotca_csg.so.2: undefined reference to `votca::tools::ParseXML::Par
seIgnore(std::__cxx11::basic_string const&, std::map, std::__cxx11::basic_string, std::less >, 
std::allocator const, 
std::__cxx11::basic_string 
> > >&)'
../libcsg/libvotca_csg.so.2: undefined reference to 
`votca::tools::Property::get(std::__cxx11::basic_string const&)'
../libcsg/libvotca_csg.so.2: undefined reference to 
`votca::tools::ParseXML::Open(std::__cxx11::basic_string const&)'
../libcsg/libvotca_csg.so.2: undefined reference to 
`votca::tools::ToolsVersionStr[abi:cxx11]()'
../libcsg/libvotca_csg.so.2: undefined reference to 
`votca::tools::load_property_from_xml(votca::tools::Property&, 
std::__cxx11::basic_string)'
../libcsg/libvotca_csg.so.2: undefined reference to 
`votca::tools::Application::CheckRequired(std::__cxx11::basic_string const&, 
std::__cxx11::basic_string 
const&)'
../libcsg/libvotca_csg.so.2: undefined reference to 
`votca::tools::Table::Load(std::__cxx11::basic_string)'
../libcsg/libvotca_csg.so.2: undefined reference to 
`votca::tools::Property::Select(std::__cxx11::basic_string const&)'
../libcsg/libvotca_csg.so.2: undefined reference to 
`votca::tools::RangeParser::Parse(std::__cxx11::basic_string)'
collect2: error: ld returned 1 exit status
make[3]: *** [src/tools/csg_dump] Error 1
src/tools/CMakeFiles/csg_dump.dir/build.make:92: recipe for target 
'src/tools/csg_dump' failed
make[3]: Leaving directory '/«PKGBUILDDIR»/obj-x86_64-linux-gnu'
make[2]: *** [src/tools/CMakeFiles/csg_dump.dir/all] Error 2
CMakeFiles/Makefile2:654: recipe for target 
'src/tools/CMakeFiles/csg_dump.dir/all' failed
make[2]: Leaving directory '/«PKGBUILDDIR»/obj-x86_64-linux-gnu'
make[1]: *** [all] Error 2


Cheers,
Dominic.
--- End Message ---
--- Begin Message ---
Source: votca-tools
Source-Version: 1.3.0-1

We believe that the bug you reported is fixed in the latest version of
votca-tools, 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 797...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Michael Banck  (supplier of updated votca-tools package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Format: 1.8
Date: Wed, 24 Feb 2016 22:42:00 +0100
Source: votca-tools
Binary: libvotca-tools-dev libvotca-tools3
Architecture: source amd64
Version: 1.3.0-1
Distribution: unstable
Urgency: medium
Maintainer: Debichem Team 
Changed-By: Michael Banck 
Description:
 libvotca-tools-dev - VOTCA's tools library, development kit
 libvotca-tools3 - VOTCA's tools library
Closes: 797293
Changes:
 votca-tools (1.3.0-1) unstable; urgency=medium
 .
   * New upstream release.
 .
   [ Daniel Leidert ]
   * 

Bug#815731: arandr: Doesn't work with the current version of xrandr

[chrysn]

On Wed, Feb 24, 2016 at 07:43:14PM +0100, Julien Cristau wrote:
> ewww.  I don't think xrandr's output is really suitable for machine
> consumption.  Can't you use the libXrandr API directly?

arandr is more of an editor for shell scripts that invoke xrandr --
executing a saved arandr file works even without arandr.

going from parser to api is an option i'm considering for future
versions when it comes to gathering information about the current state,
but the xrandr invocation will stay, so a certain dependency on xrandr
behavior will stay in place as well.

> As for your question, the right thing at this point is probably to add
> Breaks against current versions of arandr to x11-xserver-utils.  What
> version of arandr is likely to have that issue fixed?

version 0.1.9 that fixes this is released, i'm just waiting for sponsor
review for 0.1.9-1 to hit the archive. a "Breaks: arandr (<< 0.1.9)"
would avoid creating broken systems in testing. (afaik it wouldn't
impede testing migration, but only make arandr uninstallable for a few
days at most in testing).

as for further coordination, i have lost touch with xrandr devs a bit;
is there any more official announcement to xrandr releases apart from
tags on the git repo these days?

thanks
chrysn

-- 
To use raw power is to make yourself infinitely vulnerable to greater powers.
  -- Bene Gesserit axiom


signature.asc
Description: PGP signature

Bug#808738: closed by Pirate Praveen <prav...@debian.org> (Bug#808738: fixed in ruby-sinatra 1.4.7-1)

[Chris Lamb]

>   * Add patch i18n-fix.patch
>- Specify available locales during testing (Closes: #808738)

Is this due to /missing/ locales or the "wrong" locale?

If the latter, then whatever the failing test, that functionality is going to 
fail for users at runtime who aren't using that particular locale!


Regards,

-- 
  ,''`.
 : :'  : Chris Lamb
 `. `'`  la...@debian.org / chris-lamb.co.uk
   `-