Bug#814079: marked as done ([gdb-mingw-w64] Fails to connect to gdbserver)

[Debian Bug Tracking System]

Your message dated Mon, 08 Feb 2016 13:22:59 +0100
with message-id 
and subject line Re: Bug#814079: [gdb-mingw-w64] Fails to connect to gdbserver
has caused the Debian Bug report #814079,
regarding [gdb-mingw-w64] Fails to connect to gdbserver
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.)


-- 
814079: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=814079
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: gdb-mingw-w64
Version: 7.10-1+10.2
Severity: grave

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

On one terminal I start the program to debug under wine and gdbserver:

$ wine /usr/share/win32/gdbserver.exe localhost: path/to/something.exe

and it prints

Process path/to/something.exe created; pid = 41
Listening on port 
Remote debugging from host 127.0.0.1

and waits for the connection. Ok so far. On another terminal, I start gdb and 
try to connect:

$ i686-w64-mingw32-gdb path/to/something.exe
(gdb) target remote localhost:

and I get just:

Remote debugging using 127.0.0.1:
Ignoring packet error, continuing...
warning: unrecognized item "timeout" in "qSupported" response
Ignoring packet error, continuing...
Ignoring packet error, continuing...
Bogus trace status reply from target: timeout

The terminal with wine does not show anything new.

Very, very rarely it manages to connect, but most of the time it just shows 
this. It used to work.

I have both gdb-mingw-w64 and gdb-mingw-w64-target version 7.10-1+10.2 and 
wine 1.8-6.

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

Debian Release: stretch/sid
  990 testing http.debian.net 
  500 wilyppa.launchpad.net 
  500 unstablehttp.debian.net 
  500 trusty  ppa.launchpad.net 
  500 testing-proposed-updates http.debian.net 
  500 stable-updates  ftp.cz.debian.org 
  500 stable  security.debian.org 
  500 stable  ftp.cz.debian.org 
1 experimentalhttp.debian.net 

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

Package's Recommends field is empty.

Package's Suggests field is empty.



-- 
 - Jan Hudec 
--- End Message ---
--- Begin Message ---

Le 08/02/2016 12:17, Jan Hudec a écrit :

On Monday 08 of February 2016 11:22:38 Stephen Kitt wrote:

Do you get the third line immediately? It's only printed when a remote
debugger connects, so you shouldn't get it then unless something else 
is

connecting to port  (which would explain your other symptoms).


Hm, yes, I do.

And this is the culprit:
$ netstat -ptn | grep 
tcp0  0 127.0.0.1:47022 127.0.0.1:
ESTABLISHED 5510/adb
tcp0  0 127.0.0.1:  127.0.0.1:47022
ESTABLISHED 17476/gdbserver.exe

So I need to retrain my muscle memory to use different port (yes, it 
turned

out to work). Thank you for help.


You're welcome! It's nice to know there are users of the gdb-mingw-w64 
packages ;-).



I am somewhat surprised that it just stopped working sometime last week
though, because I've been using adb quite long.


It is surprising, yes; I don't know what could explain it, unless 
something started listening on port 5554, or perhaps you upgraded to adb 
6 (that's a stab in the dark, I don't know if its behaviour has 
changed).


Regards,

Stephen--- End Message ---

Bug#814072: tomcat-maven-plugin: FTBFS: Invalid plugin descriptor for org.codehaus.plexus:plexus-component-metadata

[Chris Lamb]

Source: tomcat-maven-plugin
Version: 1.1-2.4
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,

tomcat-maven-plugin fails to build from source in unstable/amd64:

  [..]

   dpkg-buildpackage -rfakeroot -D -us -uc -b
  dpkg-buildpackage: source package tomcat-maven-plugin
  dpkg-buildpackage: source version 1.1-2.4
  dpkg-buildpackage: source distribution unstable
  dpkg-buildpackage: source changed by Emmanuel Bourg 
   dpkg-source --before-build tomcat-maven-plugin-1.1
  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 -plibtomcat-maven-plugin-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 -plibtomcat-maven-plugin-java --debian-build 
--keep-pom-version 
--maven-repo=/home/lamby/temp/cdt.20160208085215.TnS3QnKMpI/tomcat-maven-plugin-1.1/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.20160208085215.TnS3QnKMpI/tomcat-maven-plugin-1.1
 -Dclassworlds.conf=/etc/maven/m2-debian.conf 
org.codehaus.plexus.classworlds.launcher.Launcher 
-s/etc/maven/settings-debian.xml 
-Ddebian.dir=/home/lamby/temp/cdt.20160208085215.TnS3QnKMpI/tomcat-maven-plugin-1.1/debian
 
-Dmaven.repo.local=/home/lamby/temp/cdt.20160208085215.TnS3QnKMpI/tomcat-maven-plugin-1.1/debian/maven-repo
 package -DskipTests -Dnotimestamp=true -Dlocale=en_US
  [INFO] Scanning for projects...
  [WARNING] 
  [WARNING] Some problems were encountered while building the effective model 
for org.codehaus.mojo:tomcat-maven-plugin:maven-plugin:1.1
  [WARNING] 'dependencies.dependency.systemPath' for 
org.apache.tomcat:jasper-jdt:jar should use a variable instead of a hard-coded 
path /usr/share/java/ecj.jar @ line 152, column 16
  [WARNING] 
  [WARNING] It is highly recommended to fix these problems because they 
threaten the stability of your build.
  [WARNING] 
  [WARNING] For this reason, future Maven versions might no longer support 
building such malformed projects.
  [WARNING] 
  [INFO]
 
  [INFO] 

  [INFO] Building Tomcat Maven Plugin 1.1
  [INFO] 

  [INFO] 

  [INFO] BUILD FAILURE
  [INFO] 

  [INFO] Total time: 0.115 s
  [INFO] Finished at: 2016-02-08T08:54:02+01:00
  [INFO] Final Memory: 8M/300M
  [INFO] 

  [ERROR] Invalid plugin descriptor for 
org.codehaus.plexus:plexus-component-metadata:1.6 
(/home/lamby/temp/cdt.20160208085215.TnS3QnKMpI/tomcat-maven-plugin-1.1/debian/maven-repo/org/codehaus/plexus/plexus-component-metadata/1.6/plexus-component-metadata-1.6.jar),
 Plugin's descriptor contains the wrong version: 1.5.5 -> [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/InvalidPluginDescriptorException
  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/lamby/temp/cdt.20160208085215.TnS3QnKMpI/tomcat-maven-plugin-1.1
 -Dclassworlds.conf=/etc/maven/m2-debian.conf 
org.codehaus.plexus.classworlds.launcher.Launcher 
-s/etc/maven/settings-debian.xml 

Bug#814071: pyorbital: FTBFS: AssertionError: 60.371433482573323 != 60.37143348255783

[Chris Lamb]

Source: pyorbital
Version: 0.3.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,

pyorbital fails to build from source in unstable/amd64:

  [..]

  
  ==
  FAIL: test_sunangles (pyorbital.tests.test_astronomy.TestAstronomy)
  Test the sun-angle calculations:
  --
  Traceback (most recent call last):
File 
"/home/lamby/temp/cdt.20160208085132.sRBTiAzuyQ/pyorbital-0.3.2/pyorbital/tests/test_astronomy.py",
 line 53, in test_sunangles
  self.assertEqual(sun_theta, 60.371433482557833)
  AssertionError: 60.371433482573323 != 60.37143348255783
  
  --
  Ran 16 tests in 0.049s
  
  FAILED (failures=1)
  debian/rules:21: recipe for target 'override_dh_auto_test' failed
  make[1]: *** [override_dh_auto_test] Error 1
  make[1]: Leaving directory 
'/home/lamby/temp/cdt.20160208085132.sRBTiAzuyQ/pyorbital-0.3.2'
  debian/rules:11: 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
   `-


pyorbital.0.3.2-1.unstable.amd64.log.txt.gz
Description: Binary data

Bug#814073: tzdata: FTBFS: Error: Unable to access jarfile /usr/lib/jvm/default-java//jre/lib/javazic.jar

[Chris Lamb]

Source: tzdata
Version: 2016a-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,

tzdata fails to build from source in unstable/amd64:

  [..]

  # Generate a java version
  /usr/lib/jvm/default-java//bin/java -jar 
/usr/lib/jvm/default-java//jre/lib/javazic.jar -V 2016a -d 
/home/lamby/temp/cdt.20160208085405.3qp2pN3cIl/tzdata-2016a/tzgen-java africa 
antarctica asia australasia europe northamerica southamerica etcetera factory 
backward systemv pacificnew gmt jdk11_backward
  Error: Unable to access jarfile /usr/lib/jvm/default-java//jre/lib/javazic.jar
  debian/rules:53: recipe for target 'build-indep-stamp' failed
  make: *** [build-indep-stamp] Error 1

  [..]

The full build log is attached.


Regards,

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


tzdata.2016a-1.unstable.amd64.log.txt.gz
Description: Binary data

Bug#814126: Fairly outdated version (unmaintained package?)

[David Prévot]

Source: php-solr
Version: 1.0.2-2
Severity: serious
Tags: stretch sid

[Filled as RC by a team member to see it autoremoved from testing if
 nobody disagrees. Please, do downgrade it with an explanation if you
 disagree.]

Hi,

php-solr 1.0.2 was uploaded to Debian in 2014 (released upstream in
2011). Since then, upstream released many versions (2.3.0 last
December). php5-solr has no reverse dependency, a fairly low popcon, so
if it has no real users nor actual maintainers, there is a priori little
point to ship it in the next stable release.

I intend to follow up with an RM request in a few months if nobody
objects (but feel free to beat me to it).

Regards

David


signature.asc
Description: PGP signature

Bug#814128: Useless in Debian

[David Prévot]

Package: php-net-ldap
Version: 1:1.1.5-3
Severity: serious
Tags: stretch sid

[Filled as RC by a team member to see it auto-removed from testing if
 nobody disagrees. Please, do downgrade it with an explanation if you
 disagree.]

Hi,

php-net-ldap is not used by any Debian package anymore, “is not
maintained anymore and has been superseded” [0] upstream.

0: http://pear.php.net/package/Net_LDAP

php-net-ldap2 is already in Debian (but not maintained upstream either).

There is a priori little point to ship it in the next stable release.

I intend to follow up with an RM request in a few months if nobody
objects (but feel free to beat me to it).

Regards

David


signature.asc
Description: PGP signature

Bug#814133: Useless in Debian

[David Prévot]

Package: php-net-smartirc
Version: 1.1.7-1
Severity: serious


[Filled as RC by a team member to see it autoremoved from testing if
 nobody disagrees. Please, do downgrade it with an explanation if you
 disagree.]

php-net-smartirc is not used by any Debian package currently, and even
if upstream is still active, it has a low (and shrinking) popcon, so
probably isn’t of any use anymore in Debian. There is a priori little
point in shipping it in the next stable release.

I intend to follow up with an RM request in a few months if nobody
objects (but feel free to beat me to it).

Regards

David


signature.asc
Description: PGP signature

Bug#811500: marked as done (cpl-plugin-visir: does not work)

[Debian Bug Tracking System]

Your message dated Mon, 08 Feb 2016 16:20:01 +
with message-id 
and subject line Bug#811500: fixed in cpl-plugin-visir 4.1.0+dfsg-2
has caused the Debian Bug report #811500,
regarding cpl-plugin-visir: does not work
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.)


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

Package: cpl-plugin-visir
Version: 4.1.0+dfsg-1
Severity: serious

the packaged recipe does not work at all for several reasons:

1. removed patched copy of swarp, visir does not work with 2.38, it 
needs 2.19 or the embedded convinience copy. To see run the 
visir_img_reduce recipe on any data and look at the garbage weight map 
it produces
2. does not work with packaged swarp even if that one would work because 
it is name SWarp not swarp as the pipeline expects.

3. the required swarp configuration visir_default.swarp is not installed.

Please spend at least at least the minimal effort to see if what you are 
packaging even works or don't bother at all. Note that in future the 
embedded swarp might receive more visir specific patches.


As upstream does not want this pipeline packaged in distributions I 
would recommend removing it completely.
--- End Message ---
--- Begin Message ---
Source: cpl-plugin-visir
Source-Version: 4.1.0+dfsg-2

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

Debian distribution maintenance software
pp.
Ole Streicher  (supplier of updated cpl-plugin-visir 
package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Format: 1.8
Date: Mon, 08 Feb 2016 16:11:50 +0100
Source: cpl-plugin-visir
Binary: cpl-plugin-visir cpl-plugin-visir-doc cpl-plugin-visir-calib
Architecture: source all amd64
Version: 4.1.0+dfsg-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Astronomy Team 

Changed-By: Ole Streicher 
Description:
 cpl-plugin-visir - ESO data reduction pipeline for the VISIR instrument
 cpl-plugin-visir-calib - ESO data reduction pipeline calibration data 
downloader for VISIR
 cpl-plugin-visir-doc - ESO data reduction pipeline documentation for the VISIR 
instrumen
Closes: 811500
Changes:
 cpl-plugin-visir (4.1.0+dfsg-2) unstable; urgency=medium
 .
   * Correct call SWarp executable name and install visir_default.swarp.
 Closes: #811500
   * Push standards version to 3.9.7. No changes needed.
Checksums-Sha1:
 750dcfe5aecf8f4f8042fec706ee5e128c647131 2343 cpl-plugin-visir_4.1.0+dfsg-2.dsc
 7786306ebe1bb649deffc79ee181c6641af275b9 10348 
cpl-plugin-visir_4.1.0+dfsg-2.debian.tar.xz
 8b66b1d2a1daaf6a4ad31a241ab31c7beb32852c 79920 
cpl-plugin-visir-calib_4.1.0+dfsg-2_all.deb
 b1dca8a56e239f65add88f8d0738fa021fbf4eeb 1154736 
cpl-plugin-visir-dbgsym_4.1.0+dfsg-2_amd64.deb
 b4f848f248be377b384baaa034af5db50c62f978 200076 
cpl-plugin-visir-doc_4.1.0+dfsg-2_all.deb
 016065aa43e78f6137f2fb6dd5f6c328b1be31d6 481232 
cpl-plugin-visir_4.1.0+dfsg-2_amd64.deb
Checksums-Sha256:
 78e3ba7b2427f17c08d286354b3d9b7a6981d2c723a694d2567dd92ebba627f6 2343 
cpl-plugin-visir_4.1.0+dfsg-2.dsc
 63937b37fdd4f8577b8c741704fda201e6a22adeca674b2531030e1a32b2a18a 10348 
cpl-plugin-visir_4.1.0+dfsg-2.debian.tar.xz
 830a4edb97d47bd02e85bda9bac6259d135f6d18ce11a8d6e5978c6e3b2d1bcd 79920 
cpl-plugin-visir-calib_4.1.0+dfsg-2_all.deb
 bfb99ad0fa93e9a21fdd2d708be5c5becc60766e9012473dfe0722ea499dd862 1154736 
cpl-plugin-visir-dbgsym_4.1.0+dfsg-2_amd64.deb
 907cbe448b5b677495ce650b665d371cb8a27db068f8f889fe7ade33770b3b27 200076 
cpl-plugin-visir-doc_4.1.0+dfsg-2_all.deb
 5bc7a1c0ffc14195c4f4397b220a89be605091465abfe196ba109265eb32bd90 481232 
cpl-plugin-visir_4.1.0+dfsg-2_amd64.deb
Files:
 6388dc2603b12c8a063e23f69daa35f3 2343 science optional 
cpl-plugin-visir_4.1.0+dfsg-2.dsc
 6596e8685e1488387611b7d421cb545e 10348 science optional 
cpl-plugin-visir_4.1.0+dfsg-2.debian.tar.xz
 ae6321a88e920a606065613293ab4282 79920 

Processed: retitle 814067 to xdelta3: CVE-2014-9765: buffer overflow in main_get_appheader

[Debian Bug Tracking System]

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

> retitle 814067 xdelta3: CVE-2014-9765: buffer overflow in main_get_appheader
Bug #814067 [xdelta3] Buffer overflow in xdelta3
Changed Bug title to 'xdelta3: CVE-2014-9765: buffer overflow in 
main_get_appheader' from 'Buffer overflow in xdelta3'
> thanks
Stopping processing here.

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

Bug#812298: marked as done (FTBFS: error: 'else' without a previous 'if')

[Debian Bug Tracking System]

Your message dated Mon, 08 Feb 2016 16:51:53 +
with message-id 
and subject line Bug#812297: fixed in console-bridge 0.3.2-1
has caused the Debian Bug report #812297,
regarding FTBFS: error: 'else' without a previous 'if'
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.)


-- 
812297: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=812297
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: ros-class-loader
Version: 0.3.2-1
Severity: serious

ros-class-loader fails to build in unstable:

> sbuild (Debian sbuild) 0.67.0 (26 Dec 2015) on dl580gen9-02.hlinux
...
> [ 20%] Building CXX object CMakeFiles/class_loader.dir/src/class_loader.cpp.o
> /usr/bin/c++   -Dclass_loader_EXPORTS -I/<>/include  -g -O2 
> -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time 
> -D_FORTIFY_SOURCE=2  -fPIC   -o 
> CMakeFiles/class_loader.dir/src/class_loader.cpp.o -c 
> /<>/src/class_loader.cpp
> /<>/src/class_loader.cpp: In member function 'int 
> class_loader::ClassLoader::unloadLibraryInternal(bool)':
> /<>/src/class_loader.cpp:95:3: error: 'else' without a previous 
> 'if'
>else
>^
> CMakeFiles/class_loader.dir/build.make:65: recipe for target 
> 'CMakeFiles/class_loader.dir/src/class_loader.cpp.o' failed
> make[3]: *** [CMakeFiles/class_loader.dir/src/class_loader.cpp.o] Error 1
> make[3]: Leaving directory '/<>/obj-x86_64-linux-gnu'
> CMakeFiles/Makefile2:102: recipe for target 'CMakeFiles/class_loader.dir/all' 
> failed

-- 
Martin Michlmayr
Linux for HPE Helion, Hewlett Packard Enterprise
--- End Message ---
--- Begin Message ---
Source: console-bridge
Source-Version: 0.3.2-1

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

Debian distribution maintenance software
pp.
Jose Luis Rivero  (supplier of updated 
console-bridge 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, 04 Feb 2016 01:17:30 +
Source: console-bridge
Binary: libconsole-bridge0.2v5 libconsole-bridge-dev libconsole-bridge0.2v5-dbg
Architecture: source
Version: 0.3.2-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Science Maintainers 

Changed-By: Jose Luis Rivero 
Description:
 libconsole-bridge-dev - console bridge - development files
 libconsole-bridge0.2v5 - console bridge - library
 libconsole-bridge0.2v5-dbg - console bridge - debugging symbols
Closes: 812297 813177
Changes:
 console-bridge (0.3.2-1) unstable; urgency=medium
 .
   * Imported Upstream version 0.3.2
 (Closes: #812297)
   * Declare Replaces+Break on libconsole-bridge0.2
 (Closes: #813177)
Checksums-Sha1:
 47f0f818a78e88aa243ec85a1ca5f4a00de49f43 1947 console-bridge_0.3.2-1.dsc
 82483a0bdc7ef0202630b6130f89c6e119150010 231243 
console-bridge_0.3.2.orig.tar.gz
 a6349febaebd85f6face63bb2d2343a3eaf1ae50 4016 
console-bridge_0.3.2-1.debian.tar.xz
Checksums-Sha256:
 4287ea47563a53e505d1c416b0be23292e367721b5d5541894155c4e76c7206f 1947 
console-bridge_0.3.2-1.dsc
 fd12e48c672cb9c5d516d90429c4a7ad605859583fc23d98258c3fa7a12d89f4 231243 
console-bridge_0.3.2.orig.tar.gz
 e399cdf7fcbead93301e1061aac0460ed49f85c58f6911b120776a7e3cf02ad0 4016 
console-bridge_0.3.2-1.debian.tar.xz
Files:
 9836abee5967e749ef5149eec0fd2045 1947 libs extra console-bridge_0.3.2-1.dsc
 6c525353efe6f386fa25d58eafa72869 231243 libs extra 
console-bridge_0.3.2.orig.tar.gz
 7d4dd7be12c4a9c79d4bfb5a0ea33dee 4016 libs extra 
console-bridge_0.3.2-1.debian.tar.xz

-BEGIN PGP SIGNATURE-
Version: GnuPG v1

iQEcBAEBCgAGBQJWuLzFAAoJEF6UbAkK/wQnz74IAL3gKf1pRNPblyGoT4csT1cW
CIBh/Ky5+o+cM83wqXV5Ic4VN8Kf8EJg3Bo00iPa1FznsHQiV0UxKhgH2DrrG/LS
1VrVLMQeeXIMDqlurGup1Si4bigbTy32mPDjyKVwdELNovg6J2DgDEQfpIy5DBw0
czvjOkvxeow+LhapdfeeddoFvjpNylhaDV5eo80nP76EyiglYZtfciQ40wGI5wga
zPWoJ0igMSzq5qs5IGLSJgDMJPrP6ND8uMH2sXfiddL6nnpLFBCZr81U4sXxzyPs
B8Sa+1hJPfdeKdAxAkrtgoVcagq7gi+k/9hYwA3Yo4Pv+7juvQE8phdwtuDUm2w=
=o3EQ
-END PGP 

Bug#812297: marked as done (FTBFS: error: 'else' without a previous 'if')

[Debian Bug Tracking System]

Your message dated Mon, 08 Feb 2016 16:51:53 +
with message-id 
and subject line Bug#812297: fixed in console-bridge 0.3.2-1
has caused the Debian Bug report #812297,
regarding FTBFS: error: 'else' without a previous 'if'
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.)


-- 
812297: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=812297
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: ros-ros-comm
Version: 1.11.16-2
Severity: serious

ros-ros-comm fails to build in unstable:

> sbuild (Debian sbuild) 0.67.0 (26 Dec 2015) on dl580gen9-02.hlinux
...
> make[3]: Leaving directory '/<>/obj-x86_64-linux-gnu'
> [ 45%] Built target roscpp_gencpp
> [ 45%] Built target roscpp_generate_messages
> /<>/tools/rosbag_storage/src/lz4_stream.cpp: In member function 
> 'virtual void rosbag::LZ4Stream::read(void*, size_t)':
> /<>/tools/rosbag_storage/src/lz4_stream.cpp:159:9: error: 'else' 
> without a previous 'if'
>  else {
>  ^
> make[3]: Leaving directory '/<>/obj-x86_64-linux-gnu'
> tools/rosbag_storage/CMakeFiles/rosbag_storage.dir/build.make:161: recipe for 
> target 
> 'tools/rosbag_storage/CMakeFiles/rosbag_storage.dir/src/lz4_stream.cpp.o' 
> failed
> make[3]: *** 
> [tools/rosbag_storage/CMakeFiles/rosbag_storage.dir/src/lz4_stream.cpp.o] 
> Error 1

-- 
Martin Michlmayr
Linux for HPE Helion, Hewlett Packard Enterprise
--- End Message ---
--- Begin Message ---
Source: console-bridge
Source-Version: 0.3.2-1

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

Debian distribution maintenance software
pp.
Jose Luis Rivero  (supplier of updated 
console-bridge 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, 04 Feb 2016 01:17:30 +
Source: console-bridge
Binary: libconsole-bridge0.2v5 libconsole-bridge-dev libconsole-bridge0.2v5-dbg
Architecture: source
Version: 0.3.2-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Science Maintainers 

Changed-By: Jose Luis Rivero 
Description:
 libconsole-bridge-dev - console bridge - development files
 libconsole-bridge0.2v5 - console bridge - library
 libconsole-bridge0.2v5-dbg - console bridge - debugging symbols
Closes: 812297 813177
Changes:
 console-bridge (0.3.2-1) unstable; urgency=medium
 .
   * Imported Upstream version 0.3.2
 (Closes: #812297)
   * Declare Replaces+Break on libconsole-bridge0.2
 (Closes: #813177)
Checksums-Sha1:
 47f0f818a78e88aa243ec85a1ca5f4a00de49f43 1947 console-bridge_0.3.2-1.dsc
 82483a0bdc7ef0202630b6130f89c6e119150010 231243 
console-bridge_0.3.2.orig.tar.gz
 a6349febaebd85f6face63bb2d2343a3eaf1ae50 4016 
console-bridge_0.3.2-1.debian.tar.xz
Checksums-Sha256:
 4287ea47563a53e505d1c416b0be23292e367721b5d5541894155c4e76c7206f 1947 
console-bridge_0.3.2-1.dsc
 fd12e48c672cb9c5d516d90429c4a7ad605859583fc23d98258c3fa7a12d89f4 231243 
console-bridge_0.3.2.orig.tar.gz
 e399cdf7fcbead93301e1061aac0460ed49f85c58f6911b120776a7e3cf02ad0 4016 
console-bridge_0.3.2-1.debian.tar.xz
Files:
 9836abee5967e749ef5149eec0fd2045 1947 libs extra console-bridge_0.3.2-1.dsc
 6c525353efe6f386fa25d58eafa72869 231243 libs extra 
console-bridge_0.3.2.orig.tar.gz
 7d4dd7be12c4a9c79d4bfb5a0ea33dee 4016 libs extra 
console-bridge_0.3.2-1.debian.tar.xz

-BEGIN PGP SIGNATURE-
Version: GnuPG v1

iQEcBAEBCgAGBQJWuLzFAAoJEF6UbAkK/wQnz74IAL3gKf1pRNPblyGoT4csT1cW
CIBh/Ky5+o+cM83wqXV5Ic4VN8Kf8EJg3Bo00iPa1FznsHQiV0UxKhgH2DrrG/LS
1VrVLMQeeXIMDqlurGup1Si4bigbTy32mPDjyKVwdELNovg6J2DgDEQfpIy5DBw0
czvjOkvxeow+LhapdfeeddoFvjpNylhaDV5eo80nP76EyiglYZtfciQ40wGI5wga
zPWoJ0igMSzq5qs5IGLSJgDMJPrP6ND8uMH2sXfiddL6nnpLFBCZr81U4sXxzyPs
B8Sa+1hJPfdeKdAxAkrtgoVcagq7gi+k/9hYwA3Yo4Pv+7juvQE8phdwtuDUm2w=
=o3EQ
-END PGP SIGNATURE End Message ---

Bug#814136: wimlib: FTBFS: doxygen: not found

[Aaron M. Ucko]

Source: wimlib
Version: 1.8.3-1
Severity: serious
Justification: fails to build from source

Builds of wimlib in minimal environments geared towards building its
architecture-dependent binary packages have been failing:

  cd doc && doxygen
  /bin/sh: 1: doxygen: not found
  debian/rules:10: recipe for target 'override_dh_auto_build' failed
  make[1]: *** [override_dh_auto_build] Error 127
  make[1]: Leaving directory '/«PKGBUILDDIR»'
  debian/rules:4: recipe for target 'build-arch' failed
  make: *** [build-arch] Error 2

Please either run doxygen only when actually building the
architecture-independent -doc package or move it from
Build-Depends-Indep to Build-Depends.

Thanks!

Bug#814079: [gdb-mingw-w64] Fails to connect to gdbserver

[Stephen Kitt]

Hi Jan,

Le 08/02/2016 10:07, Jan Hudec a écrit :

On one terminal I start the program to debug under wine and gdbserver:

$ wine /usr/share/win32/gdbserver.exe localhost: 
path/to/something.exe


and it prints

Process path/to/something.exe created; pid = 41
Listening on port 
Remote debugging from host 127.0.0.1


Do you get the third line immediately? It's only printed when a remote 
debugger connects, so you shouldn't get it then unless something else is 
connecting to port  (which would explain your other symptoms).


[...]

Regards,

Stephen

Bug#812689: marked as done (ruby-carrierwave fails its tests)

[Debian Bug Tracking System]

Your message dated Mon, 8 Feb 2016 22:28:45 +0530
with message-id <56b8c945.9070...@autistici.org>
and subject line Done in version 0.10.0+gh-2
has caused the Debian Bug report #812689,
regarding ruby-carrierwave fails its tests
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.)


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

Package: src:ruby-carrierwave
Version: 0.10.0+gh-1
Severity: serious
Tags: sid stretch

ruby-carrierwave fails its tests, also ruby-mysql2 is scheduled for removal, so 
please use ruby-mysql.


RUBYLIB=/scratch/packages/tmp/ruby-carrierwave-0.10.0+gh/debian/ruby-carrierwave/usr/lib/ruby/vendor_ruby:. 
GEM_PATH=/home/doko/.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-carrierwave/usr/share/rubygems-integration/all 
ruby2.2 -S rake -f debian/ruby-tests.rake

/usr/bin/ruby2.2 /usr/bin/rspec ./spec/processing/mini_magick_spec.rb
.FF

Failures:

  1) CarrierWave::MiniMagick test errors invalid image file should use I18n
 Failure/Error: change_locale_and_store_translations(:nl, :errors => {
 I18n::InvalidLocale:
   :nl is not a valid locale
 # ./spec/spec_helper.rb:104:in `change_locale_and_store_translations'
 # ./spec/processing/mini_magick_spec.rb:145:in `block (4 levels) in (required)>'


  2) CarrierWave::MiniMagick test errors invalid image file should not suppress 
errors when translation is unavailable

 Failure/Error: change_locale_and_store_translations(:foo, {}) do
 I18n::InvalidLocale:
   :foo is not a valid locale
 # ./spec/spec_helper.rb:104:in `change_locale_and_store_translations'
 # ./spec/processing/mini_magick_spec.rb:155:in `block (4 levels) in (required)>'
--- End Message ---
--- Begin Message ---
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

This bug was fixed in ruby-carrierwave version 0.10.0+gh-2 , but
somehow wasn't closed by the changelog.
- -- 
Regards
Balasankar C
http://balasankarc.in
-BEGIN PGP SIGNATURE-
Version: GnuPG v2

iQEcBAEBCgAGBQJWuMlEAAoJEJbtq5sua3FxKpcH/RWQPABSXzgZnWIxylIe6Bt7
RE77abhXCiW5iIgOlmkqVQbci1SDBt10UrH4rLDL4UnXo6lsR+NAJ2ZfDvxY0Rn+
TiXR0o28i4vO6WQOt5rw+QkNk+4mUCThOvmE0SeT8DGaehMJ04rsPDFQd+lUzkOn
pFdYozt5ravseJSwyqNw0lSsZVp2NTTjBe4SB0Z0fJgBaFwehUWmS859T1lvLim7
Uv0H/rjyl4Uwr9JgOhTHl4H1FtbNpd9eXndzXgHYH3+kUlcyVlmgu0Su2RMrItxh
DcbHkdZ49gnXdjZFLe2eIGZyYhHhCK9z+m99x4edMfz5xDKrQuA/MGBBRlM8YUE=
=Rui8
-END PGP SIGNATURE-


0x2E6B7171.asc
Description: application/pgp-keys
--- End Message ---

Bug#814131: Useless in Debian

[David Prévot]

Package: php-pager
Version: 2.4.8-3
Severity: serious
Tags: stretch sid

[Filled as RC by a team member to see it autoremoved from testing if
 nobody disagrees. Please, do downgrade it with an explanation if you
 disagree.]

Hi,

php-pager is only used by php-structures-datagrid-renderer-pager, but
it’s going away (#804904, #814108). There has been a new upstream
release five years after the version currently in Debian, but since it
has a low (and shrinking) popcon, it probably isn’t of any use anymore.
There is a priori little point to ship it in the next stable release.

I intend to follow up with an RM request in a few months if nobody
objects (but feel free to beat me to it).

Regards

David


signature.asc
Description: PGP signature

Bug#812579: marked as done (ros-class-loader: FTBFS: class_loader.cpp:95:3: error: 'else' without a previous 'if')

[Debian Bug Tracking System]

Your message dated Mon, 08 Feb 2016 16:51:53 +
with message-id 
and subject line Bug#812297: fixed in console-bridge 0.3.2-1
has caused the Debian Bug report #812297,
regarding ros-class-loader: FTBFS: class_loader.cpp:95:3: error: 'else' without 
a previous 'if'
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.)


-- 
812297: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=812297
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: ros-class-loader
Version: 0.3.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,

ros-class-loader fails to build from source in unstable/amd64:

  [..]

   dpkg-buildpackage -rfakeroot -D -us -uc -b
  dpkg-buildpackage: source package ros-class-loader
  dpkg-buildpackage: source version 0.3.2-1
  dpkg-buildpackage: source distribution unstable
  dpkg-buildpackage: source changed by Jochen Sprickerhof 

   dpkg-source --before-build ros-class-loader-0.3.2
  dpkg-buildpackage: host architecture amd64
   fakeroot debian/rules clean
  dh clean 
 dh_testdir
 dh_auto_clean
 dh_clean
   debian/rules build
  dh build 
 dh_testdir
 dh_update_autotools_config
 dh_auto_configure
cmake .. -DCMAKE_INSTALL_PREFIX=/usr -DCMAKE_VERBOSE_MAKEFILE=ON 
-DCMAKE_BUILD_TYPE=None -DCMAKE_INSTALL_SYSCONFDIR=/etc 
-DCMAKE_INSTALL_LOCALSTATEDIR=/var
  -- The C compiler identification is GNU 5.3.1
  -- The CXX compiler identification is GNU 5.3.1
  -- Check for working C compiler: /usr/bin/cc
  -- Check for working C compiler: /usr/bin/cc -- works
  -- Detecting C compiler ABI info
  -- Detecting C compiler ABI info - done
  -- Detecting C compile features
  -- Detecting C compile features - done
  -- Check for working CXX compiler: /usr/bin/c++
  -- Check for working CXX compiler: /usr/bin/c++ -- works
  -- Detecting CXX compiler ABI info
  -- Detecting CXX compiler ABI info - done
  -- Detecting CXX compile features
  -- Detecting CXX compile features - done
  -- Boost version: 1.58.0
  -- Found the following Boost libraries:
  --   thread
  --   system
  -- Using CATKIN_DEVEL_PREFIX: 
/home/lamby/temp/cdt.20160125084731.Q1uu3PJzhC/ros-class-loader-0.3.2/obj-x86_64-linux-gnu/devel
  -- Using CMAKE_PREFIX_PATH: 
  -- Found PythonInterp: /usr/bin/python (found version "2.7.11") 
  -- Using PYTHON_EXECUTABLE: /usr/bin/python
  -- Using Debian Python package layout
  -- Using empy: /usr/bin/empy
  -- Using CATKIN_ENABLE_TESTING: ON
  -- Call enable_testing()
  -- Using CATKIN_TEST_RESULTS_DIR: 
/home/lamby/temp/cdt.20160125084731.Q1uu3PJzhC/ros-class-loader-0.3.2/obj-x86_64-linux-gnu/test_results
  -- Looking for pthread.h
  -- Looking for pthread.h - found
  -- Looking for pthread_create
  -- Looking for pthread_create - not found
  -- Looking for pthread_create in pthreads
  -- Looking for pthread_create in pthreads - not found
  -- Looking for pthread_create in pthread
  -- Looking for pthread_create in pthread - found
  -- Found Threads: TRUE  
  -- Found gtest sources under '/usr/src/gtest': gtests will be built
  CMake Warning at /usr/share/catkin/cmake/test/nosetests.cmake:98 (message):
nosetests not found, Python tests can not be run (try installing package
'python-nose')
  Call Stack (most recent call first):
/usr/share/catkin/cmake/all.cmake:147 (include)
/usr/share/catkin/cmake/catkinConfig.cmake:20 (include)
CMakeLists.txt:5 (find_package)
  
  
  -- catkin 0.6.16
  -- Searching for Poco library...
  --   Found Poco!
  -- components found: Foundation.
  -- Boost version: 1.58.0
  -- Found the following Boost libraries:
  --   thread
  -- Checking to see if CXX compiler accepts flag 
-Wl,--version-script,"/home/lamby/temp/cdt.20160125084731.Q1uu3PJzhC/ros-class-loader-0.3.2/obj-x86_64-linux-gnu/test/class_loader_hide_library_symbols__class_loader_TestPlugins1.script"
  -- Checking to see if CXX compiler accepts flag 
-Wl,--version-script,"/home/lamby/temp/cdt.20160125084731.Q1uu3PJzhC/ros-class-loader-0.3.2/obj-x86_64-linux-gnu/test/class_loader_hide_library_symbols__class_loader_TestPlugins1.script"
 - yes
  -- Configuring done
  -- Generating done
  -- Build files have been written to: 
/home/lamby/temp/cdt.20160125084731.Q1uu3PJzhC/ros-class-loader-0.3.2/obj-x86_64-linux-gnu
 dh_auto_build
make -j1
  make[1]: Entering directory 

Bug#813177: marked as done (libconsole-bridge0.2v5: fails to upgrade from 'jessie' - trying to overwrite /usr/lib/x86_64-linux-gnu/libconsole_bridge.so.0.2)

[Debian Bug Tracking System]

Your message dated Mon, 08 Feb 2016 16:51:53 +
with message-id 
and subject line Bug#813177: fixed in console-bridge 0.3.2-1
has caused the Debian Bug report #813177,
regarding libconsole-bridge0.2v5: fails to upgrade from 'jessie' - trying to 
overwrite /usr/lib/x86_64-linux-gnu/libconsole_bridge.so.0.2
to be marked as done.

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

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


-- 
813177: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=813177
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: libconsole-bridge0.2v5
Version: 0.3.0-3
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts
Control: affects -1 + libconsole-bridge-dev

Hi,

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

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

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

  Selecting previously unselected package libconsole-bridge0.2v5:amd64.
  (Reading database ... 
(Reading database ... 20581 files and directories currently installed.)
  Preparing to unpack .../libconsole-bridge0.2v5_0.3.0-3_amd64.deb ...
  Unpacking libconsole-bridge0.2v5:amd64 (0.3.0-3) ...
  dpkg: error processing archive 
/var/cache/apt/archives/libconsole-bridge0.2v5_0.3.0-3_amd64.deb (--unpack):
   trying to overwrite '/usr/lib/x86_64-linux-gnu/libconsole_bridge.so.0.2', 
which is also in package libconsole-bridge0.2:amd64 0.2.5-2+b1


cheers,

Andreas


libconsole-bridge-dev_0.3.0-3.log.gz
Description: application/gzip
--- End Message ---
--- Begin Message ---
Source: console-bridge
Source-Version: 0.3.2-1

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

Debian distribution maintenance software
pp.
Jose Luis Rivero  (supplier of updated 
console-bridge 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, 04 Feb 2016 01:17:30 +
Source: console-bridge
Binary: libconsole-bridge0.2v5 libconsole-bridge-dev libconsole-bridge0.2v5-dbg
Architecture: source
Version: 0.3.2-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Science Maintainers 

Changed-By: Jose Luis Rivero 
Description:
 libconsole-bridge-dev - console bridge - development files
 libconsole-bridge0.2v5 - console bridge - library
 libconsole-bridge0.2v5-dbg - console bridge - debugging symbols
Closes: 812297 813177
Changes:
 console-bridge (0.3.2-1) unstable; urgency=medium
 .
   * Imported Upstream version 0.3.2
 (Closes: #812297)
   * Declare Replaces+Break on libconsole-bridge0.2
 (Closes: #813177)
Checksums-Sha1:
 47f0f818a78e88aa243ec85a1ca5f4a00de49f43 1947 console-bridge_0.3.2-1.dsc
 82483a0bdc7ef0202630b6130f89c6e119150010 231243 
console-bridge_0.3.2.orig.tar.gz
 a6349febaebd85f6face63bb2d2343a3eaf1ae50 4016 
console-bridge_0.3.2-1.debian.tar.xz
Checksums-Sha256:
 4287ea47563a53e505d1c416b0be23292e367721b5d5541894155c4e76c7206f 1947 
console-bridge_0.3.2-1.dsc
 fd12e48c672cb9c5d516d90429c4a7ad605859583fc23d98258c3fa7a12d89f4 231243 
console-bridge_0.3.2.orig.tar.gz
 e399cdf7fcbead93301e1061aac0460ed49f85c58f6911b120776a7e3cf02ad0 4016 
console-bridge_0.3.2-1.debian.tar.xz
Files:
 9836abee5967e749ef5149eec0fd2045 1947 libs extra console-bridge_0.3.2-1.dsc
 6c525353efe6f386fa25d58eafa72869 231243 libs extra 
console-bridge_0.3.2.orig.tar.gz
 7d4dd7be12c4a9c79d4bfb5a0ea33dee 4016 libs extra 
console-bridge_0.3.2-1.debian.tar.xz

-BEGIN PGP SIGNATURE-
Version: GnuPG v1

iQEcBAEBCgAGBQJWuLzFAAoJEF6UbAkK/wQnz74IAL3gKf1pRNPblyGoT4csT1cW
CIBh/Ky5+o+cM83wqXV5Ic4VN8Kf8EJg3Bo00iPa1FznsHQiV0UxKhgH2DrrG/LS
1VrVLMQeeXIMDqlurGup1Si4bigbTy32mPDjyKVwdELNovg6J2DgDEQfpIy5DBw0
czvjOkvxeow+LhapdfeeddoFvjpNylhaDV5eo80nP76EyiglYZtfciQ40wGI5wga

Bug#786173: marked as done (python-peak.rules: deprecation of python-support)

[Debian Bug Tracking System]

Your message dated Mon, 08 Feb 2016 16:56:51 +
with message-id 
and subject line Bug#786173: fixed in python-peak.rules 0.5a1+r2713-1
has caused the Debian Bug report #786173,
regarding python-peak.rules: deprecation of python-support
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.)


-- 
786173: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=786173
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: python-peak.rules
Version: 0.5a1+r2707-1
Severity: important
User: debian-pyt...@lists.debian.org
Usertags: pysupport-deprecation



Dear Maintainer,

your package either build-depends or depends on the python-support
package, or uses dh_pysupport in debian/rules file.

python-support has been deprecated for some time, and any package
still using it should be migrated to dh_python2 and dh_python3.
Instructions on how to migrate packages to dh_python2/dh_python3 can
be found on the Debian wiki [0]. An overview of the anatomy of a
package using the pybuild and dh_python{2,3} helpers can be found in
the Python Module Style Guide [1].

Please test your package thoroughly to make sure the transition to
dh_python2/dh_python3 is done correctly and does not cause a negative
impact on your package. In particular, please test upgrades from the
current jessie and stretch/sid versions of the package.

If your package does not yet use Python 3, please consider adding
Python 3 support to your package at the same time as updating the
build system; the py3k porters can offer assistance with that [2].

[0] https://wiki.debian.org/Python/TransitionToDHPython2 [1]
https://wiki.debian.org/Python/LibraryStyleGuide [2]
https://wiki.debian.org/Python/Python3Port

Thanks! 
--- End Message ---
--- Begin Message ---
Source: python-peak.rules
Source-Version: 0.5a1+r2713-1

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

Debian distribution maintenance software
pp.
Daniele Tricoli  (supplier of updated python-peak.rules 
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: Fri, 05 Feb 2016 01:17:55 +0100
Source: python-peak.rules
Binary: python-peak.rules
Architecture: source
Version: 0.5a1+r2713-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Python Modules Team 

Changed-By: Daniele Tricoli 
Description:
 python-peak.rules - generic functions support for Python
Closes: 671424 786173
Changes:
 python-peak.rules (0.5a1+r2713-1) unstable; urgency=medium
 .
   [ Jakub Wilk ]
   * Use canonical URIs for Vcs-* fields.
 .
   [ Daniele Tricoli ]
   * New upstream release.
   * Replace deprecated dh_pysupport with dh_python2. (Closes: #786173)
   * debian/{clean,rules}
 - Clean using debian/clean instead of override_dh_auto_clean.
 - Clean also prioritized_methods egg-info to build the package twice in a
   row. Thanks to Jakub Wilk for the bug report. (Closes: #671424)
   * debian/compat
 - Bump debhelper compatibility level to 9.
   * debian/control
 - Bump Standards-Version to 3.9.7 (no changes needed).
 - Update Vcs fields for git migration.
 - Bump debhelper B-D to (>= 9).
 - Add X-Python-Version.
 - Use secure URI for Vcs-Git.
   * debian/copyright
 - Update Format URI.
 - Fix wildcard-matches-nothing-in-dep5-copyright.
 - Use secure URI in Source field.
 - Update copyright years.
   * debian/rules
 - Use mktemp to create GOS_TMP_DIR.
 - Create GOS_TMP_DIR only inside get-orig-source target.
   * debian/README.source
 - Update.
Checksums-Sha1:
 0e084d3577b75901100719d473a4d68a98a79760 2867 
python-peak.rules_0.5a1+r2713-1.dsc
 909f3201e0bfae8ce5761058f4c4cb9fa9bb6f41 4755 
python-peak.rules_0.5a1+r2713.orig-prioritized-methods-0-2-2dev-20110830.tar.gz
 46c77faf704c0f4b7bb5aba97a9027158d6ebf80 113186 
python-peak.rules_0.5a1+r2713.orig-rules.tar.gz
 41797f618da41fed9bb855a356daf35bc2aeddc2 130 
python-peak.rules_0.5a1+r2713.orig.tar.gz
 

Bug#814079: [gdb-mingw-w64] Fails to connect to gdbserver

[Jan Hudec]

On Monday 08 of February 2016 11:22:38 Stephen Kitt wrote:
> Hi Jan,
> 
> Le 08/02/2016 10:07, Jan Hudec a écrit :
> > On one terminal I start the program to debug under wine and gdbserver:
> > $ wine /usr/share/win32/gdbserver.exe localhost:
> > 
> > path/to/something.exe
> > 
> > and it prints
> > 
> > Process path/to/something.exe created; pid = 41
> > Listening on port 
> > Remote debugging from host 127.0.0.1
> 
> Do you get the third line immediately? It's only printed when a remote
> debugger connects, so you shouldn't get it then unless something else is
> connecting to port  (which would explain your other symptoms).

Hm, yes, I do.

And this is the culprit:
$ netstat -ptn | grep 
tcp0  0 127.0.0.1:47022 127.0.0.1:  
ESTABLISHED 5510/adb
tcp0  0 127.0.0.1:  127.0.0.1:47022 
ESTABLISHED 17476/gdbserver.exe 

So I need to retrain my muscle memory to use different port (yes, it turned 
out to work). Thank you for help.

I am somewhat surprised that it just stopped working sometime last week 
though, because I've been using adb quite long.

-- 
 - Jan Hudec 

Bug#790275: qstat: FTBFS with glibc 2.21 and gcc-5

[Guillaume Delacour]

On Sat, 31 Oct 2015 15:15:33 +0100 Guillaume Delacour 
wrote:
> 
> Upstream seems to have modified qstat.c to include strndup() only if
> needed in recent version of qstat :
> 
> https://github.com/multiplay/qstat/commit/9977e09cebc340208ab097f8db619ebc80756859

I've uploaded a fix on mentors:
http://mentors.debian.net/debian/pool/main/q/qstat/qstat_2.15-2.dsc.

I'm waiting for Jordi for uploading it in the archive.

-- 
Guillaume Delacour



signature.asc
Description: OpenPGP digital signature

Bug#814079: [gdb-mingw-w64] Fails to connect to gdbserver

[Jan Hudec]

Package: gdb-mingw-w64
Version: 7.10-1+10.2
Severity: grave

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

On one terminal I start the program to debug under wine and gdbserver:

$ wine /usr/share/win32/gdbserver.exe localhost: path/to/something.exe

and it prints

Process path/to/something.exe created; pid = 41
Listening on port 
Remote debugging from host 127.0.0.1

and waits for the connection. Ok so far. On another terminal, I start gdb and 
try to connect:

$ i686-w64-mingw32-gdb path/to/something.exe
(gdb) target remote localhost:

and I get just:

Remote debugging using 127.0.0.1:
Ignoring packet error, continuing...
warning: unrecognized item "timeout" in "qSupported" response
Ignoring packet error, continuing...
Ignoring packet error, continuing...
Bogus trace status reply from target: timeout

The terminal with wine does not show anything new.

Very, very rarely it manages to connect, but most of the time it just shows 
this. It used to work.

I have both gdb-mingw-w64 and gdb-mingw-w64-target version 7.10-1+10.2 and 
wine 1.8-6.

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

Debian Release: stretch/sid
  990 testing http.debian.net 
  500 wilyppa.launchpad.net 
  500 unstablehttp.debian.net 
  500 trusty  ppa.launchpad.net 
  500 testing-proposed-updates http.debian.net 
  500 stable-updates  ftp.cz.debian.org 
  500 stable  security.debian.org 
  500 stable  ftp.cz.debian.org 
1 experimentalhttp.debian.net 

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

Package's Recommends field is empty.

Package's Suggests field is empty.



-- 
 - Jan Hudec 

Bug#813271: marked as done (diaspora-installer: fails to install: post-installation script returned error exit status 127)

[Debian Bug Tracking System]

Your message dated Mon, 08 Feb 2016 10:19:32 +
with message-id 
and subject line Bug#813271: fixed in diaspora-installer 0.5.6.3+debian1
has caused the Debian Bug report #813271,
regarding diaspora-installer: fails to install: post-installation script 
returned error exit status 127
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.)


-- 
813271: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=813271
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: diaspora-installer
Version: 0.5.3.0+debian1
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

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

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

  Selecting previously unselected package diaspora-installer.
  Preparing to unpack .../diaspora-installer_0.5.3.0+debian1_all.deb ...
  You already have a PostgreSQL database named 'diaspora_production'...
  Unpacking diaspora-installer (0.5.3.0+debian1) ...
  Setting up diaspora-installer (0.5.3.0+debian1) ...
  Download diaspora tarball version 0.5.3.0 from github.com...
  --2016-01-24 17:05:34--  
https://github.com/diaspora/diaspora/archive/v0.5.3.0.tar.gz
  Resolving github.com (github.com)... 192.30.252.128
  Connecting to github.com (github.com)|192.30.252.128|:443... connected.
  HTTP request sent, awaiting response... 302 Found
  Location: https://codeload.github.com/diaspora/diaspora/tar.gz/v0.5.3.0 
[following]
  --2016-01-24 17:05:34--  
https://codeload.github.com/diaspora/diaspora/tar.gz/v0.5.3.0
  Resolving codeload.github.com (codeload.github.com)... 192.30.252.163
  Connecting to codeload.github.com 
(codeload.github.com)|192.30.252.163|:443... connected.
  HTTP request sent, awaiting response... 200 OK
  Length: unspecified [application/x-gzip]
  Saving to: '/var/cache/diaspora-installer/diaspora-0.5.3.0.tar.gz'
  
  
  /var/cach [<=> ]   0  --.-KB/s   
 /var/cache [ <=>]  83.87K   300KB/s   
/var/cache/ [  <=>   ] 546.67K  1.11MB/s   
   /var/cache/d [   <=>  ]   1.92M  2.82MB/s   
/var/cache/diaspora [<=> ]   2.65M  3.55MB/sin 0.7s
  
  2016-01-24 17:05:36 (3.55 MB/s) - 
'/var/cache/diaspora-installer/diaspora-0.5.3.0.tar.gz' saved [2776158]
  
  Extracting files...
  Copying files to /usr/share/diaspora...
  diaspora archive to copy: diaspora-0.5.3.0
  Copying source tarball to /usr/share/diaspora/public...
  Setting up environment varibales...
  Using /etc/diaspora.conf...
  export RAILS_ENV=production
  export DB=postgres
  RAILS_ENV=production DB=postgres ENVIRONMENT_URL=https://localhost
  Fetching: bundler-1.11.2.gem
Fetching: bundler-1.11.2.gem (  6%)
Fetching: bundler-1.11.2.gem ( 13%)
Fetching: bundler-1.11.2.gem ( 19%)
Fetching: bundler-1.11.2.gem ( 25%)
Fetching: bundler-1.11.2.gem ( 31%)
Fetching: bundler-1.11.2.gem ( 38%)
Fetching: bundler-1.11.2.gem ( 44%)
Fetching: bundler-1.11.2.gem ( 50%)
Fetching: bundler-1.11.2.gem ( 56%)
Fetching: bundler-1.11.2.gem ( 62%)
Fetching: bundler-1.11.2.gem ( 69%)
Fetching: bundler-1.11.2.gem ( 75%)
Fetching: bundler-1.11.2.gem ( 81%)
Fetching: bundler-1.11.2.gem ( 87%)
Fetching: bundler-1.11.2.gem ( 94%)
Fetching: bundler-1.11.2.gem (100%)
Fetching: bundler-1.11.2.gem (100%)
  Successfully installed bundler-1.11.2
  Parsing documentation for bundler-1.11.2
  Installing ri documentation for bundler-1.11.2
  Done installing documentation for bundler after 10 seconds
  1 gem installed
  Installing gems with rubygems ...
  Fetching gem metadata from https://rails-assets.org/...
  Fetching version metadata from https://rails-assets.org/..
  Fetching gem metadata from https://rails-assets.org/...
  Fetching gem metadata from https://rubygems.org/
  Fetching version metadata from https://rails-assets.org/..
  Fetching version metadata from https://rubygems.org/...
  Fetching dependency metadata from https://rails-assets.org/..
  Fetching dependency metadata from https://rubygems.org/..
  Resolving dependencies.
  Using rake 10.4.2
  Installing CFPropertyList 2.3.1
  Installing i18n 0.7.0
  Installing json 1.8.3 with native extensions
  Installing minitest 5.8.0
  Installing thread_safe 0.3.5
  Installing builder 3.2.2
  Installing erubis 

Bug#808446: marked as done (google-android-build-tools-installer: configuration script fail)

[Debian Bug Tracking System]

Your message dated Mon, 08 Feb 2016 10:49:31 +
with message-id 
and subject line Bug#808446: fixed in google-android-build-tools-installer 
23.0.2.1
has caused the Debian Bug report #808446,
regarding google-android-build-tools-installer: configuration script fail
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.)


-- 
808446: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=808446
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: google-android-build-tools-installer
Version: 23.0.2.0
Severity: grave
Tags: patch

Hello, 

google-android-build-tools-installer fail to install on my computer:


   install: impossible d'évaluer « 
/var/cache/google-android-build-tools-installer/android-4.4W/split-select »: 
Aucun fichier ou dossier de ce type

Meaning that it can find split-select.

It seem that it fail because it is not installing android-4.4W but
android-6.

The attached path fix this problem.

There is another bug in the Makefile: the library (libLLVM.so
libbcinfo.so libbcc.so libclang.so) are looked for in the wrong
subdirectory of android-*/, and the test looking at their possible
installation in the current system look in /usr/bin and not /usr/lib.

My patch fix those two error too.


Thanks for the package.

Cordially, Rémi.

--- google-android/Makefile 2015-12-20 10:34:56.106509766 +0100
+++ /usr/share/google-android-build-tools-installer/Makefile2015-12-20 10:30:59.106470309 +0100
@@ -6,7 +6,7 @@
 PKG_SOURCE_URL:=https://dl.google.com/android/repository/${PKG_SOURCE}
 
 DL_DIR=/var/cache/google-android-build-tools-installer
-UNPACK_DIR=$(DL_DIR)/android-4.4W
+UNPACK_DIR=$(DL_DIR)/android-6.0
 DOC_DIR=/usr/share/doc/google-android-build-tools
 
 all: $(DL_DIR)/$(UNPACK_DIR)/aapt
@@ -30,8 +30,8 @@
$(UNPACK_DIR)/zipalign \
/usr/bin/
install -d -m0755 /usr/lib/
-   for f in libLLVM.so libbcinfo.so libbcc.so libclang.so; do \
-   test -e /usr/bin/$$f || install -m0644 $(UNPACK_DIR)/$$f /usr/lib/; done
+   for f in lib/libLLVM.so lib/libbcinfo.so lib/libbcc.so lib/libclang.so; do \
+   test -e /usr/lib/$$f || install -m0644 $(UNPACK_DIR)/$$f /usr/lib/; done
install -d -m0755 $(DOC_DIR)
gzip -9 --stdout $(UNPACK_DIR)/NOTICE.txt > $(DOC_DIR)/copyright.gz
install -m0644 $(UNPACK_DIR)/source.properties $(DOC_DIR)/





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

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

Versions of packages google-android-build-tools-installer depends on:
ii  build-essential  12.1
ii  ca-certificates  20150426
ii  dpkg-dev 1.18.3
ii  libstdc++6   5.3.1-3
ii  make 4.0-8.2
ii  unzip6.0-20
ii  wget 1.17.1-1
ii  zlib1g   1:1.2.8.dfsg-2+b1

google-android-build-tools-installer recommends no packages.

google-android-build-tools-installer suggests no packages.

-- no debconf information

-- 
Rémi Vanicat
--- End Message ---
--- Begin Message ---
Source: google-android-build-tools-installer
Source-Version: 23.0.2.1

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

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

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

Debian distribution maintenance software
pp.
Hans-Christoph Steiner  (supplier of updated 
google-android-build-tools-installer package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Mon, 08 Feb 2016 10:56:14 +0100
Source: google-android-build-tools-installer
Binary: google-android-build-tools-installer
Architecture: source
Version: 23.0.2.1
Distribution: unstable
Urgency: medium
Maintainer: Android tools Maintainer 

Changed-By: Hans-Christoph 

Processed: your mail

[Debian Bug Tracking System]

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

> owner 813974 ken...@lexical.tw
Bug #813974 [libbitcoinconsensus-dev,dogecoin] dogecoin and 
libbitcoinconsensus-dev: error when trying to install together
Owner recorded as ken...@lexical.tw.
>
End of message, stopping processing here.

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

Bug#811708: [PKG-OpenRC-Debian] Bug#811708: need help?

[Svante Signell]

On Mon, 2016-02-08 at 08:26 +0100, Adam Borowski wrote:
> > init-system-helpers: file conflict with openrc: /usr/sbin/update-rc.d
> 
> Uhm, guys... are you alive?  This bug keeps openrc uninstallable, and will
> cause its autoremoval soon.
> 
> If you're too busy and need help, I could help with fixing or NMUing, but
> you need to decide whether to:
> * cooperate with init-system-helpers and put the logic there (like sysv-rc)
> * divert update-rc.d (like file-rc)
> 
> Note that I'm not the best person to help, though, as I use openrc only on a
> single desktop and thus don't know anything about its advanced features nor
> internals.

Hi Adam,
Cc: Roger

I sent the following mail to the openrc maintainers: Benda Xu, Thomas Goirand
and Roger Leigh on Friday February 5th (no reply so far). The mail to Roger
bounced, he is no longer a Debian maintainer.

> Hello,
> 
> Due to the serious bug 811708 openrc (0.18.3-1) will be removed from Debian
> testing on February 18. In my opinion it would be a pity if it disappears.
> 
> Is it possible to do as file-rc (0.8.17) did in bug 812337: add a diversion?
> 
> From changelog: divert update-rc.d + invoke-rc.d files to cooperate with init-
> system-helpers =1.25. It seems like only divert() in preinst and
> undivert() in
> postrm scripts has to be created and called.
> 
> Thanks!

Bug#814069: python-six-whl and python-pip-whl: error when trying to install together

[Colin Watson]

On Mon, Feb 08, 2016 at 08:11:22AM +0100, Ralf Treinen wrote:
> Selecting previously unselected package python-pip-whl.
> (Reading database ... 10940 files and directories currently installed.)
> Preparing to unpack .../python-pip-whl_8.0.2-3_all.deb ...
> Unpacking python-pip-whl (8.0.2-3) ...
> Selecting previously unselected package python-six-whl.
> Preparing to unpack .../python-six-whl_1.10.0-2_all.deb ...
> Unpacking python-six-whl (1.10.0-2) ...
> dpkg: error processing archive 
> /var/cache/apt/archives/python-six-whl_1.10.0-2_all.deb (--unpack):
>  trying to overwrite 
> '/usr/share/python-wheels/six-1.10.0-py2.py3-none-any.whl', which is also in 
> package python-pip-whl 8.0.2-3
> Errors were encountered while processing:
>  /var/cache/apt/archives/python-six-whl_1.10.0-2_all.deb
> E: Sub-process /usr/bin/dpkg returned an error code (1)

Looks like https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=813399, but
more of the same.  Barry, shouldn't you be doing something like
"python-six-whl (<< 1.10.0+)", rather than these sketchy <= dependencies
on specific packaging revisions that are going to break when we do
something innocuous in six?

The whole way this devendoring is handled seems very very sketchy
anyway.  I take it that you're trying to ensure that pip has
exactly-versioned wheels available even when (e.g.) six moves on to a
newer upstream version?  In that case, I suggest finding a way to ship
the necessary wheels in a directory private to pip instead of in
/usr/share/python-wheels/.  We really shouldn't be deliberately shipping
the same file in two different packages for more than just temporary
transitional purposes.

> Here is a list of files that are known to be shared by both packages
> (according to the Contents file for sid/amd64, which may be
> slightly out of sync):
> 
>   /usr/share/python-wheels/six-1.10.0-py2.py3-none-any.whl
> 
> This bug has been filed against both packages. If you, the maintainers of
> the two packages in question, have agreed on which of the packages will
> resolve the problem please reassign the bug to that package. You may then
> also register in the BTS that the other package is affected by the bug.

I would be inclined to argue that this path clearly belongs to the
python-six-whl package.  Barry, do you agree with me reassigning this
bug to python-pip-whl?

-- 
Colin Watson   [cjwat...@debian.org]

Bug#813578: marked as done (obexpushd: Please update package name of libopenobex in B-D)

[Debian Bug Tracking System]

Your message dated Mon, 08 Feb 2016 11:20:17 +
with message-id 
and subject line Bug#813578: fixed in obexpushd 0.11.2-1.1
has caused the Debian Bug report #813578,
regarding obexpushd: Please update package name of libopenobex in B-D
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.)


-- 
813578: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=813578
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: obexpushd
Version: 0.11.2-1
Severity: important
Tags: patch

Dear Maintainer,

soname of libopenobex has been updated. 
libopenobex of obexpushd has been set libopenobex1, this will FTBFS on unsbtale 
of environment.
Please update package name from libopenobex1-dev to libopenobex2-dev.

Best regards,
  Nobuhiro

-- System Information:
Debian Release: stretch/sid
  APT prefers unstable
  APT policy: (500, 'unstable'), (1, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: armhf, armel, sh4, powerpc

Kernel: Linux 4.2.0-1-amd64 (SMP w/4 CPU cores)
Locale: LANG=ja_JP.utf8, LC_CTYPE=ja_JP.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
diff -Nru obexpushd-0.11.2/debian/changelog obexpushd-0.11.2/debian/changelog
--- obexpushd-0.11.2/debian/changelog	2011-08-08 09:56:43.0 +0900
+++ obexpushd-0.11.2/debian/changelog	2016-02-03 18:15:53.0 +0900
@@ -1,3 +1,10 @@
+obexpushd (0.11.2-1.1) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * Change B-D from libopenobex1-dev to libopenobex2-dev.
+
+ -- Nobuhiro Iwamatsu   Wed, 03 Feb 2016 18:15:15 +0900
+
 obexpushd (0.11.2-1) unstable; urgency=low
 
   * New upstream release.
diff -Nru obexpushd-0.11.2/debian/control obexpushd-0.11.2/debian/control
--- obexpushd-0.11.2/debian/control	2011-08-08 09:56:43.0 +0900
+++ obexpushd-0.11.2/debian/control	2016-02-03 18:16:06.0 +0900
@@ -2,7 +2,7 @@
 Section: comm
 Priority: optional
 Maintainer: Gabriele Giacone <1o5g4...@gmail.com>
-Build-Depends: debhelper (>= 7), libopenobex1-dev, libbluetooth-dev,
+Build-Depends: debhelper (>= 7), libopenobex2-dev, libbluetooth-dev,
  pkg-config, xmlto, cmake, cdbs
 Standards-Version: 3.9.2
 Homepage: http://www.gitorious.org/obexpushd/
--- End Message ---
--- Begin Message ---
Source: obexpushd
Source-Version: 0.11.2-1.1

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

Debian distribution maintenance software
pp.
Mattia Rizzolo  (supplier of updated obexpushd 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: Sun, 07 Feb 2016 13:53:47 +
Source: obexpushd
Binary: obexpushd
Architecture: source
Version: 0.11.2-1.1
Distribution: unstable
Urgency: medium
Maintainer: Gabriele Giacone <1o5g4...@gmail.com>
Changed-By: Mattia Rizzolo 
Description:
 obexpushd  - program for receiving files via Bluetooth or IRDA
Closes: 813578
Changes:
 obexpushd (0.11.2-1.1) unstable; urgency=medium
 .
   * Non-maintainer upload.
   * Change build-dep on libopenobex1-dev by libopenobex2-dev.  Closes: #813578
Checksums-Sha1:
 d08214e8152b2386779a6061c23b495d8527d453 1786 obexpushd_0.11.2-1.1.dsc
 88df1357032bfcf013b7debe136050a32fc77c72 2976 
obexpushd_0.11.2-1.1.debian.tar.xz
Checksums-Sha256:
 db7f78b7cb765351f11adc6af77c6ef789db2e09b6549a378e48e1cb2acbd4d9 1786 
obexpushd_0.11.2-1.1.dsc
 74443a7051ee588c68acf7a83c43997819f3aee34b027f88de8e4c394af78859 2976 
obexpushd_0.11.2-1.1.debian.tar.xz
Files:
 dcda2a9a24ff8bf7b96ed6657ded4b34 1786 comm optional obexpushd_0.11.2-1.1.dsc
 160202dfd65e5d05b12996283047586e 2976 comm optional 
obexpushd_0.11.2-1.1.debian.tar.xz

-BEGIN PGP SIGNATURE-
Version: GnuPG v1

iQIcBAEBCAAGBQJWt0x3AAoJEEsEP825REVAou8P/jWArUjkC2JMU5R23MCWiFuQ
LBIVjeqml7k712hyZVh1dEi4DnajAQPNI0Yi2Nq6fvVcGN5CKw1qznZCci16fpwS
akz7y56VDQKKi073dreL7j/a6ylpp0N823LACPwFlwPMrM9Eibqgy+yatPRTiqHy
g9qHeTUut4CYZG7VnlzwLEHAzfqBT90BIinigk3OsXUr7aiePNVY04kfimGCjwav

Bug#811300: marked as done (FTBFS: error: 'OBEX_TRANS_CUST' undeclared)

[Debian Bug Tracking System]

Your message dated Mon, 08 Feb 2016 11:20:04 +
with message-id 
and subject line Bug#811300: fixed in libsyncml 0.5.4-2.3
has caused the Debian Bug report #811300,
regarding FTBFS: error: 'OBEX_TRANS_CUST' undeclared
to be marked as done.

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

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


-- 
811300: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=811300
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: libsyncml
Version: 0.5.4-2.2
Severity: serious

libsyncml fails to build:

> sbuild (Debian sbuild) 0.67.0 (26 Dec 2015) on dl580gen9-02.hlinux
...
> [ 34%] Building C object 
> libsyncml/CMakeFiles/syncml.dir/transports/obex_client.o
> cd /<>/build/libsyncml && /usr/bin/cc  -Dsyncml_EXPORTS 
> -I/<> -I/<>/build -I/usr/include/glib-2.0 
> -I/usr/lib/x86_64-linux-gnu/glib-2.0/include -I/usr/include/libxml2 
> -I/usr/include/libsoup-2.4  -Wall -g -O2 -fPIC   -o 
> CMakeFiles/syncml.dir/transports/obex_client.o   -c 
> /<>/libsyncml/transports/obex_client.c
> /<>/libsyncml/transports/obex_client.c: In function 
> 'smlTransportObexClientSetConnectionType':
> /<>/libsyncml/transports/obex_client.c:719:32: error: 
> 'OBEX_TRANS_CUST' undeclared (first use in this function)
> env->obexhandle = OBEX_Init(OBEX_TRANS_CUST, smlTransportObexClientEvent, 
> 0); 
> ^
> /<>/libsyncml/transports/obex_client.c:719:32: note: each 
> undeclared identifier is reported only once for each function it appears in
> /<>/libsyncml/transports/obex_client.c:743:6: warning: 
> initialization from incompatible pointer type [-Wincompatible-pointer-types]
>   obex_cable_handleinput,
>   ^
> /<>/libsyncml/transports/obex_client.c:743:6: note: (near 
> initialization for 'cabletrans.write')
> /<>/libsyncml/transports/obex_client.c:744:6: warning: 
> initialization from incompatible pointer type [-Wincompatible-pointer-types]
>   env};
>   ^
> /<>/libsyncml/transports/obex_client.c:744:6: note: (near 
> initialization for 'cabletrans.handleinput')
> /<>/libsyncml/transports/obex_client.c: In function 
> 'smlTransportObexClientConnect':
> /<>/libsyncml/transports/obex_client.c:885:19: warning: implicit 
> declaration of function 'OBEX_FindInterfaces' 
> [-Wimplicit-function-declaration]
>obex_intf_cnt = OBEX_FindInterfaces(env->obexhandle, _intf);
>^
> libsyncml/CMakeFiles/syncml.dir/build.make:785: recipe for target 
> 'libsyncml/CMakeFiles/syncml.dir/transports/obex_client.o' failed
> make[3]: *** [libsyncml/CMakeFiles/syncml.dir/transports/obex_client.o] Error 
> 1

-- 
Martin Michlmayr
Linux for HPE Helion, Hewlett Packard Enterprise
--- End Message ---
--- Begin Message ---
Source: libsyncml
Source-Version: 0.5.4-2.3

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

Debian distribution maintenance software
pp.
Mattia Rizzolo  (supplier of updated libsyncml 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: Sat, 06 Feb 2016 13:05:59 +
Source: libsyncml
Binary: libsyncml2 libsyncml-utils libsyncml-dev libsyncml-doc libsyncml2-dbg
Architecture: all source
Version: 0.5.4-2.3
Distribution: unstable
Urgency: medium
Maintainer: Michael Banck 
Changed-By: Mattia Rizzolo 
Closes: 794225 811300
Description: 
 libsyncml2-dbg - Debug symbols for libsyncml2
 libsyncml2 - SyncML protocol library
 libsyncml-dev - SyncML protocol development library
 libsyncml-doc - SyncML protocol library documentation
 libsyncml-utils - SyncML protocol library utilities
Changes:
 libsyncml (0.5.4-2.3) unstable; urgency=medium
 .
   * Non-maintainer upload.
 .
   [ Nobuhiro Iwamatsu ]
   * Fix FTBFS with libopenobex2-dev.  Closes: #811300
 Add patches/fix_build_with_libopenobex2.patch.
   * Change B-D from libopenobex1-dev to libopenobex2-dev.
 .
   [ Maria Valentina Marin ]
   * Export environment variable SOURCE_DATE_EPOCH to produce reproducible
 timestamps in manpage output.  Closes: #794225

Processed: your mail

[Debian Bug Tracking System]

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

> owner 813973 ken...@lexical.tw
Bug #813973 [libbitcoinconsensus0,dogecoin] dogecoin and libbitcoinconsensus0: 
error when trying to install together
Owner recorded as ken...@lexical.tw.
>
End of message, stopping processing here.

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

Bug#812129: marked as done (libxmlrpcpp-dev: /usr/include/base64.h already shipped by heimdal-dev)

[Debian Bug Tracking System]

Your message dated Tue, 09 Feb 2016 07:34:45 +
with message-id 
and subject line Bug#812129: fixed in ros-ros-comm 1.11.16-3
has caused the Debian Bug report #812129,
regarding libxmlrpcpp-dev: /usr/include/base64.h already shipped by heimdal-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.)


-- 
812129: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=812129
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: libxmlrpcpp-dev,heimdal-dev
Severity: serious
User: trei...@debian.org
Usertags: edos-file-overwrite
Control: found -1 1.11.16-2
Control: found -1 1.6~rc2+dfsg-10

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 libxmlrpcpp-dev.
  Preparing to unpack .../libxmlrpcpp-dev_1.11.16-2_amd64.deb ...
  Unpacking libxmlrpcpp-dev (1.11.16-2) ...
  dpkg: error processing archive 
/var/cache/apt/archives/libxmlrpcpp-dev_1.11.16-2_amd64.deb (--unpack):
   trying to overwrite '/usr/include/base64.h', which is also in package 
heimdal-dev 1.6~rc2+dfsg-10
  Processing triggers for libc-bin (2.21-6) ...
  Errors were encountered while processing:
   /var/cache/apt/archives/libxmlrpcpp-dev_1.11.16-2_amd64.deb


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/include/base64.h

This bug is assigned to both packages. If you, the maintainers of
the two packages in question, have agreed on which of the packages will
resolve the problem please reassign the bug to that package. You may
also register in the BTS that the other package is affected by the bug.

/usr/include/base64.h sounds like a very generic name and I wouldn't
expect to find such a file in either of these two packages.
There are a lot of packages shipping base64.h in their specific include
directories:
https://packages.debian.org/search?searchon=contents=base64.h=path=unstable=any

Cheers,

Andreas

PS: for more information about the detection of file overwrite errors
of this kind see https://qa.debian.org/dose/file-overwrites.html
--- End Message ---
--- Begin Message ---
Source: ros-ros-comm
Source-Version: 1.11.16-3

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

Debian distribution maintenance software
pp.
Jochen Sprickerhof  (supplier of updated 
ros-ros-comm 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: Sat, 16 Jan 2016 14:27:26 +0100
Source: ros-ros-comm
Binary: libroscpp-dev libroscpp0d libroscpp-msgs-dev python-roscpp-msgs 
cl-roscpp-msgs python-rospy librosbag-dev librosbag0d python-rosbag 
librosbag-storage-dev librosbag-storage0d librosconsole-dev librosconsole0d 
python-rosgraph python-roslaunch python-rosmaster python-rosmsg python-rosnode 
rosout python-rosparam python-rosservice python-rostest librostest-dev 
python-rostopic libtopic-tools-dev libtopic-tools0d topic-tools 
python-topic-tools cl-topic-tools libmessage-filters-dev libmessage-filters0d 
python-message-filters python-roswtf libroslz4-dev libroslz4-0d python-roslz4 
libxmlrpcpp-dev libxmlrpcpp0d
Architecture: source all amd64
Version: 1.11.16-3
Distribution: unstable
Urgency: medium
Maintainer: Debian 

Bug#814200: kdepimlibs: Incorrect Build-Deps

[Zhang Jingqiang]

Package: kdepimlibs
Version: 4:15.12.1-1
Severity: serious
Justification: fails to build from source (but built successfully in the past)

Dear Maintainer,

It should build-depend on kgendesignerplugin, which install the needed cmake 
files.

And the optional prison-dev is not needed, as the really needed one is 
kf5prison which
has not been released yet.

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

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

Bug#814202: android-platform-dalvik: FTBFS: unable to load addon maven_repo_helper

[Aaron M. Ucko]

Source: android-platform-dalvik
Version: 6.0.1+r16-1
Severity: serious
Justification: fails to build from source

Builds of android-platform-dalvik in minimal environments geared for
building only its architecture-dependent binary packages (notably, on
the autobuilders) have been failing:

  dh clean --with maven_repo_helper --buildsystem=gradle
  dh: unable to load addon maven_repo_helper: Can't locate 
Debian/Debhelper/Sequence/maven_repo_helper.pm in @INC (you may need to install 
the Debian::Debhelper::Sequence::maven_repo_helper module) (@INC contains: 
/etc/perl /usr/local/lib/i386-linux-gnu/perl/5.22.1 
/usr/local/share/perl/5.22.1 /usr/lib/i386-linux-gnu/perl5/5.22 
/usr/share/perl5 /usr/lib/i386-linux-gnu/perl/5.22 /usr/share/perl/5.22 
/usr/local/lib/site_perl /usr/lib/i386-linux-gnu/perl-base .) at (eval 13) line 
2.
  BEGIN failed--compilation aborted at (eval 13) line 2.

Please either move maven-repo-helper from Build-Depends-Indep to
Build-Depends or conditionalize your usage of --with maven_repo_helper
appropriately; likewise for gradle-debian-helper and
--buildsystem=gradle.  Also, please confirm with pbuilder or the like
that you haven't missed anything else; in particular, you might find
pbuilder's --binary-arch option useful.

Thanks!

Bug#814179: marked as done (omegat: (Build-)Depends on OpenJDK 7)

[Debian Bug Tracking System]

Your message dated Tue, 09 Feb 2016 05:48:58 +
with message-id 
and subject line Bug#814179: fixed in omegat 2.3.0.1+dfsg-4
has caused the Debian Bug report #814179,
regarding omegat: (Build-)Depends on OpenJDK 7
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.)


-- 
814179: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=814179
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:omegat
Version: 2.3.0.1+dfsg-3
Severity: serious
User: debian-j...@lists.debian.org
Usertags: openjdk-8-transition

The package build-depends or depends one an openjdk-7-* package,
which is scheduled for removal for stretch.  Please do not depend
on a specific openjdk version, but on one of the default-java,
default-java-headless or default-jdk packages instead.

default-java defaulting to openjdk-8 on most architectures is now
available in unstable.
--- End Message ---
--- Begin Message ---
Source: omegat
Source-Version: 2.3.0.1+dfsg-4

We believe that the bug you reported is fixed in the latest version of
omegat, 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.
tony mancill  (supplier of updated omegat package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Mon, 08 Feb 2016 21:19:14 -0800
Source: omegat
Binary: omegat
Architecture: source all
Version: 2.3.0.1+dfsg-4
Distribution: unstable
Urgency: medium
Maintainer: Debian Java Maintainers 

Changed-By: tony mancill 
Description:
 omegat - Computer Assisted Translation (CAT) tool
Closes: 814179
Changes:
 omegat (2.3.0.1+dfsg-4) unstable; urgency=medium
 .
   [ Emmanuel Bourg ]
   * Team upload.
   * debian/control:
 - Use canonical URLs for the Vcs-* fields
 - Runtime dependency on java-runtime instead of openjdk-jre or sun-java-jre
   (Closes: #814179)
   * Swicth to debhelper level 9
 .
   [ tony mancill ]
   * Bump Standards-Version updated to 3.9.6
   * Remove menu file; this package ships a desktop file.
Checksums-Sha1:
 cf0f18c4ebb0398b5a98190bd81bc0c013b3b527 2077 omegat_2.3.0.1+dfsg-4.dsc
 668c7052537adf0b69e9585ea9599fe254e209e4 13832 
omegat_2.3.0.1+dfsg-4.debian.tar.xz
 3e6b1246897e200c0368f5c3544adfb51d27f61b 10888070 omegat_2.3.0.1+dfsg-4_all.deb
Checksums-Sha256:
 9496ee1f04b32eced0f7f36d09d6e68d67a4bc3aec4d70043f7c78feaa5e8978 2077 
omegat_2.3.0.1+dfsg-4.dsc
 c1adc6e69dac30369e023b6930800475c6f54051e0d2513a599416e12bf8af16 13832 
omegat_2.3.0.1+dfsg-4.debian.tar.xz
 1a205ac598fdc7c831db8fb56f0a7c25122127d6020e6ad93c371e39b7c394fe 10888070 
omegat_2.3.0.1+dfsg-4_all.deb
Files:
 a11fdd247088d8d522cb4cf26d1f660d 2077 editors optional 
omegat_2.3.0.1+dfsg-4.dsc
 353e147f584ffc1b89b74a5afee48814 13832 editors optional 
omegat_2.3.0.1+dfsg-4.debian.tar.xz
 4abc441cedfb24651ae6b1988384665c 10888070 editors optional 
omegat_2.3.0.1+dfsg-4_all.deb

-BEGIN PGP SIGNATURE-
Version: GnuPG v1

iQIcBAEBCgAGBQJWuXnzAAoJECHSBYmXSz6WwPMQAJH1YEOS9B/JztYV0jZYdqm2
8fh7F5LZVTQXweQg0K+3Ky3/qArJYNlQVMbwETkUMSXgWB+WqcPmKrvbC8fdrM2O
17JcgI4vG1VSraHHPlviLwg+osh1MJ5J4Eh18VY5nZyLxWdTImPKq6i/ZgkOP/QX
2kk7IlfQkKPq4i+Ul9MEmKmGo2p3+BW98aPTX85XjCdFUBcHQpKavG9Xc5dv3B7j
KEZNCkZ6K6uF5vd5aHZ73Z+SfhS3hL6PCMAdJ/o0ODVF/aCsALQN16YpXbPiRvMZ
l+amk/SiQf24u54jB2Ly9srkrTGZ7eqeIaXKNxP05BPMl6h7L31hJG/2A03+vWH3
UzTFCwauQsIdS8Bq6jmqVqr9P84j49iXBvnd3GbgR8dVy/d4WYYhONXgv8S8FVmd
pxKehlGcx4Qq3o+g+XLsbjo7nfZLYD6dSx5i966flB76P/sM3nj0FVym0z9odVbx
0lLfcUqg7JEiYNKUyA1qkzEtIzptwWfinoaB1k8z3ff0Qcdc9zXucaD4l/pmrnxL
qQgy1gwirOH0sklGwpPXe7Gv/JzMCZ8eXi6+10dwxlKqpNobCf1eEe7FAjeP5PFx
iTM5MI5okCjqbUwJEFE/Rcty54LHCSuE2g/2SvMdqXzzSY2hdh6hLVMoO5J81ycU
fxzMNClz5jQcijfCUeFX
=12jX
-END PGP SIGNATURE End Message ---

Bug#814198: csmith: FTBFS: platform.cpp:78:10: error: impossible constraint in 'asm'

[Nobuhiro Iwamatsu]

Package: csmith
Version: 2.2.0-1
Severity: serious
Justification: fails to build from source

Hi,

csmith FTBFS on some architecture.

arm64:  
https://buildd.debian.org/status/fetch.php?pkg=csmith=arm64=2.2.0-1=1454715566

MIPS: 
https://buildd.debian.org/status/fetch.php?pkg=csmith=mips=2.2.0-1=1454824019

Please fix this problem.

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

Bug#813339: breaking an essential service is bad enough, failure to document just compounds the error.

[Craig Sanders]

making changes to how things work is reasonable and perfectly normal.

completely failing to document those changes, resulting in broken
servers (and, given that this is a dhcp server, broken networks) is not.

there isn't even a single mention of this change ANYWHERE in the
updated package, not in the /etc/default file, and not under
/usr/share/doc/isc-dhcp-server.


/usr/share/doc/isc-dhcp-server# find . -type f -exec zgrep -i INTERFACESv[46] 
{} +
/usr/share/doc/isc-dhcp-server#


i had to discover this change myself by running the init.d script with
'bash -x' (good thing i hadn't jumped on the systemd bandwagon - shell
scripts are beneficial, not a hassle)...only then did i have enough info
to figure out what the problem was and enough info to search the bug
tracker.

so, please, if you're going to make major changes to how something works
then at least make some minimal effort to document the changes.

thanks,

craig

-- 
craig sanders 

Bug#785991: marked as done (dipy: deprecation of python-support)

[Debian Bug Tracking System]

Your message dated Tue, 09 Feb 2016 05:19:17 +
with message-id 
and subject line Bug#785991: fixed in dipy 0.10.1-1
has caused the Debian Bug report #785991,
regarding dipy: deprecation of python-support
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.)


-- 
785991: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=785991
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: dipy
Version: 0.7.1-2
Severity: important
User: debian-pyt...@lists.debian.org
Usertags: pysupport-deprecation



Dear Maintainer,

your package either build-depends or depends on the python-support
package, or uses dh_pysupport in debian/rules file.

python-support has been deprecated for some time, and any package
still using it should be migrated to dh_python2 and dh_python3.
Instructions on how to migrate packages to dh_python2/dh_python3 can
be found on the Debian wiki [0]. An overview of the anatomy of a
package using the pybuild and dh_python{2,3} helpers can be found in
the Python Module Style Guide [1].

Please test your package thoroughly to make sure the transition to
dh_python2/dh_python3 is done correctly and does not cause a negative
impact on your package. In particular, please test upgrades from the
current jessie and stretch/sid versions of the package.

If your package does not yet use Python 3, please consider adding
Python 3 support to your package at the same time as updating the
build system; the py3k porters can offer assistance with that [2].

[0] https://wiki.debian.org/Python/TransitionToDHPython2 [1]
https://wiki.debian.org/Python/LibraryStyleGuide [2]
https://wiki.debian.org/Python/Python3Port

Thanks! 
--- End Message ---
--- Begin Message ---
Source: dipy
Source-Version: 0.10.1-1

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

Debian distribution maintenance software
pp.
Yaroslav Halchenko  (supplier of updated dipy 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, 08 Feb 2016 20:04:07 -0500
Source: dipy
Binary: python-dipy python-dipy-lib python-dipy-doc
Architecture: source all amd64
Version: 0.10.1-1
Distribution: unstable
Urgency: medium
Maintainer: NeuroDebian Team 
Changed-By: Yaroslav Halchenko 
Description:
 python-dipy - toolbox for analysis of MR diffusion imaging data
 python-dipy-doc - toolbox for analysis of MR diffusion imaging data -- 
documentatio
 python-dipy-lib - toolbox for analysis of MR diffusion imaging data -- 
extensions
Closes: 785991 789747
Changes:
 dipy (0.10.1-1) unstable; urgency=medium
 .
   [ Michael Hanke ]
   * Upload to unstable (Closes: #785991).
   * Update maintainer email.
   * Modify build to enable reproducible build (Closes: #789747). Patch is
 courtesy of Juan Picca .
 .
   [ Yaroslav Halchenko ]
   * Fresh upstream release
   * debian/patches/up_numpy_compat-PR858.patch - for compatibility with numpy
 1:1.11.0~b2
Checksums-Sha1:
 0c67e7b1f24905dc4b7c59e5777a91365e4e29cd 2461 dipy_0.10.1-1.dsc
 c7dbca727f3d2e47b0ecba682ac79db0da57b4ab 67425139 
dipy_0.10.1.orig-doc-examples.tar.gz
 731a37af0a6862c04b427e20255f91a9ae43cf21 4834090 dipy_0.10.1.orig.tar.gz
 3e10094482fb776eacbe8335f4d6f26095494917 590968 dipy_0.10.1-1.debian.tar.xz
 6ec926f369b354b6bc3456bd47c2c3c55811d4b2 11463842 
python-dipy-doc_0.10.1-1_all.deb
 bdca1e96cac7404f83d2dfd663ac9d6226880647 6208922 
python-dipy-lib-dbgsym_0.10.1-1_amd64.deb
 5f279f7e2549c223c836decc6474b39c07c90f30 1160558 
python-dipy-lib_0.10.1-1_amd64.deb
 5e5191c2a5f9f8ad688bdf062ffd1a108e07a3f0 2441686 python-dipy_0.10.1-1_all.deb
Checksums-Sha256:
 becd952c57ccbfeb270f0c035171b4d793f8764eb5deee04ea2fe5fbe9b53f94 2461 
dipy_0.10.1-1.dsc
 7ede9540bb1cdb0897be06761d73cd2967cab525acdabf4128b85977190641bc 67425139 
dipy_0.10.1.orig-doc-examples.tar.gz
 f77d507799e4ebe2ea127c3901312c51f37502ec382e50abdffa4a6be00c3d98 4834090 
dipy_0.10.1.orig.tar.gz
 

Bug#814183: openmpi 1.10.2 is broken on powerpc

[Graham Inggs]

I don't believe the warning below is related to the problem.

> A deprecated MCA variable value was specified in the environment or
> on the command line.  Deprecated MCA variables should be avoided;
> they may disappear in future releases.

It can be avoided by changing the following line in petsc's debian/rules

export OMPI_MCA_orte_rsh_agent=/bin/false

to

export OMPI_MCA_plm_rsh_agent=/bin/false

Unfortunately this does not prevent the building ending with (as does aces3):

Build killed with signal TERM after 150 minutes of inactivity

On powerpc, running one of petsc's tests on one processor gets a
result (instantly):

$ mpiexec -n 1 ./ex19 -da_refine 3 -snes_monitor_short -pc_type mg
-ksp_type fgmres -pc_mg_type full
lid velocity = 0.0016, prandtl # = 1, grashof # = 1
  0 SNES Function norm 0.0406612
  1 SNES Function norm 3.33636e-06
  2 SNES Function norm 1.653e-11
Number of SNES iterations = 2

Running it on two processors never completes:

$ mpiexec -n 2 ./ex19 -da_refine 3 -snes_monitor_short -pc_type mg
-ksp_type fgmres -pc_mg_type full
lid velocity = 0.0016, prandtl # = 1, grashof # = 1
  0 SNES Function norm 0.0406612

Bug#756253: Upgrade from 2.02~beta2-10 to 2.02~beta2-11 left grub unbootable

[Michal Zimen]

Hi,

I'm facing the same problem caused most probably by the latest grub update.
Any issue how  to fix or hack to have bootable laptop?

Here are some of my logs:

# efibootmgr -c -l "\\EFI\\debian\\grubx64.efi" -L "Debian"
efibootmgr: Could not set variable Boot: No space left on device
efibootmgr: Could not prepare boot variable: No space left on device
#


/dev/sda2  256M   27M  230M  11% /boot/efi


# dpkg -l efibootmgr grub-efi grub2-common
Desired=Unknown/Install/Remove/Purge/Hold
| 
Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend

|/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad)
||/ Name   Version Architecture   
Description

+++-==-==-==-=
ii  efibootmgr 0.12-4 amd64  
Interact with the EFI Boot Manager
ii  grub-efi   2.02~beta2-35 amd64   
GRand Unified Bootloader, version 2 (dummy package)
ii  grub2-common   2.02~beta2-35 amd64   GRand 
Unified Bootloader (common files for version 2)



#efibootmgr
BootCurrent: 0001
Timeout: 0 seconds
BootOrder: 2001,0002,0005,0004,2002,2003
Boot0001* EFI USB Device (USB FLASH DRIVE)
Boot0002* Windows Boot Manager
Boot0004* Network Boot: Realtek PXE B01 D00
Boot0005* ATA HDD : ST500LM000-1EJ162
Boot2001* EFI USB Device
Boot2002* EFI DVD/CDROM
Boot2003* EFI Network
   ---> my debian entry has completely lost from the list of boot 
devices. I can boot only via USB.


Thanks for any help,

Michal


On Mon, 24 Aug 2015 22:51:09 +0200 Felix Zielcke  wrote:
> Am Montag, den 24.08.2015, 10:28 +0200 schrieb Giorgio Valocchi:
> > The problem was that the nvram entry wasn't properly created under
> > sid.
> >
> > I managed to login in a stable distribution I have on the same system
> > to
> > create it.
>
> In that case it would be a bug either in efibootmgr or the Linux
> Kernel.
> grub-install just calls efibootmgr to create the entry
>
>

--
~Epitheton s.r.o./AMDG

Processed: [libkscreenlocker5] Conflict with plasma-workspace

[Debian Bug Tracking System]

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

> severity 814152 serious
Bug #814152 [libkscreenlocker5] [libkscreenlocker5] Conflict with 
plasma-workspace
Severity set to 'serious' from 'normal'
> thanks
Stopping processing here.

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

Processed: found in gnome-shell-extensions_3.18.3-1 too

[Debian Bug Tracking System]

Processing control commands:

> found -1 3.18.3-1
Bug #808906 [gnome-shell-extensions] gnome-shell-extensions: overwriting 
/usr/share/gnome-shell/theme/calendar-today.svg
Marked as found in versions gnome-shell-extensions/3.18.3-1.

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

Bug#813725: [Debian-astro-maintainers] Bug#813725: Bug#813725: Patch for build against openmpi1.10

[Axel Beckert]

Hi,

Alastair McKinstry wrote:
> On 07/02/2016 19:58, Axel Beckert wrote:
> > Alastair McKinstry wrote:
> >> -   libboost-dev (>= 1.53.1), libboost-mpi-dev, dh-autoreconf,
> >> +   libboost1.58-dev, libboost1.58-mpi-devm dh-autoreconf,
> >
> > This looks rather scary to me.
> >
> > Since libboost-dev (currently) directly depends on libboost1.58-dev,
> > there is no need to replace the dependency on libboost-dev with
> > libboost1.58-dev.
>
> Ok, the libboost1.58-dev is not needed if boost-dev makes it into
> testing;

There is no such package "boost-dev". Did you mean libboost-dev? A
libboost-dev which depends on libboost1.58-dev_is_ in Testing:
https://packages.qa.debian.org/b/boost-defaults.html

> I just included it to get the pkg to build, boost1.55 FTBFS at the moment.

I was surprised to see that boost1.55 is still in unstable.

> A decision from the Boost team on which Boost is going to stretch is
> desirable.

I'm very sure it won't be 1.55 -- no idea if a version newer than 1.58
is targeted.

Regards, Axel
-- 
 ,''`.  |  Axel Beckert , http://people.debian.org/~abe/
: :' :  |  Debian Developer, ftp.ch.debian.org Admin
`. `'   |  4096R: 2517 B724 C5F6 CA99 5329  6E61 2FF9 CD59 6126 16B5
  `-|  1024D: F067 EA27 26B9 C3FC 1486  202E C09E 1D89 9593 0EDE

Bug#808906: found in gnome-shell-extensions_3.18.3-1 too

[Holger Levsen]

control: found -1 3.18.3-1

Hi,

I just noticed 
https://jenkins.debian.net/job/chroot-installation_jessie_install_gnome_upgrade_to_stretch/78//console
which once again failed with 

dpkg: error processing archive 
/var/cache/apt/archives/gnome-shell-extensions_3.18.3-1_all.deb (--unpack):
 trying to overwrite '/usr/share/gnome-shell/theme/calendar-today.svg', which 
is also in package gnome-shell-common 3.14.4-1~deb8u1

Strangely enough,
https://jenkins.debian.net/job/chroot-installation_jessie_install_gnome_upgrade_to_stretch/
shows this didnt happen between January 18th and February 4th, so probably
this bug doenst happen on all jessie to stretch upgrades…


cheers,
Holger


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

Bug#813725: [Debian-astro-maintainers] Bug#813725: Patch for build against openmpi1.10

[Alastair McKinstry]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Hi,

Ok, the libboost1.58-dev is not needed if boost-dev makes it into testing;
I just included it to get the pkg to build, boost1.55 FTBFS at the moment.

A decision from the Boost team on which Boost is going to stretch is
desirable.

regards
Alastair


On 07/02/2016 19:58, Axel Beckert wrote:
> Hi,
>
> Alastair McKinstry wrote:
>> -   libboost-dev (>= 1.53.1), libboost-mpi-dev, dh-autoreconf,
>> +   libboost1.58-dev, libboost1.58-mpi-devm dh-autoreconf,
>
> This looks rather scary to me.
>
> Since libboost-dev (currently) directly depends on libboost1.58-dev,
> there is no need to replace the dependency on libboost-dev with
> libboost1.58-dev.
>
> In contrary: It would make very future boost transition rather awkward
> and would make additional source-ful uploads necessary. So I strongly
> recommend to _not_ apply that part of the patch as it makes things
> worse.
>
> Regards, Axel

- -- 
Alastair McKinstry, , ,
https://diaspora.sceal.ie/u/amckinstry
Misentropy: doubting that the Universe is becoming more disordered.
-BEGIN PGP SIGNATURE-
Version: GnuPG v2

iQIcBAEBCAAGBQJWuJL4AAoJEMvmu05dmtOlSrcP/1t4sDsBxboZOqQWYFXk+sX3
7t/c2lemKc5n3gNLBGXRct6izgWk3f9Zc6sGjLSw5J0ShofvTFMs7sbbp8H8dEZy
CVLPrc7n8Z2nhejE8KFxzJHbOXfXi/dgAQUyrDPQfxIELN8SgYczmaQNtMwPPkmE
isFvlYLQni9oU773fAAOZYiwcIHR6sotNvJP7khPCbjwrJNoNcqDGB//XhLmzQu9
zMqUlsM6rWvw1/4cw1CYbGmZL9Z2Dltr6Dqc4yfQ7J+RKI3YTparIy6/X22GTtjF
oxJl1tZA+hOW9cX/xcyIFUIazksaQJM7/FbBdZx3OzIqlq64sSAeBHMMrpguneUW
f107d5xhd6Yxl3JzD0TH9Ua9yTzg+HMTOnh/O3kruO7sTKZfwo6ZVvseSeFbkwP+
k4COpD30nkei156UkSQADp3CASHJ1DGoy7j7jWQc35HpB7FH91Y8JXzHLOMz4UUG
sH7zY6n9/G7j4RTS90N8bMZRTsXJTPcXHWOoBvaPyO4oc8Ps5t0qzadRZqJRJgay
/hEi21jXBVlkr0xVCUZOLRfUmvFakbhkIcptKlbxutR19xf/0v2mNY5t+hrOdTFa
KVrTW0jsyb3/ce3W5Rx1+N99SmTaBVhK7IUYKPgckVg0omRSpD8iIDeRpAb32Dqn
McIK9vfzw6oAeDV2U213
=sVD5
-END PGP SIGNATURE-

Bug#814069: python-six-whl and python-pip-whl: error when trying to install together

[Barry Warsaw]

On Feb 08, 2016, at 10:51 AM, Colin Watson wrote:

>Looks like https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=813399, but
>more of the same.  Barry, shouldn't you be doing something like
>"python-six-whl (<< 1.10.0+)", rather than these sketchy <= dependencies
>on specific packaging revisions that are going to break when we do
>something innocuous in six?
>
>The whole way this devendoring is handled seems very very sketchy
>anyway.  I take it that you're trying to ensure that pip has
>exactly-versioned wheels available even when (e.g.) six moves on to a
>newer upstream version?  In that case, I suggest finding a way to ship
>the necessary wheels in a directory private to pip instead of in
>/usr/share/python-wheels/.  We really shouldn't be deliberately shipping
>the same file in two different packages for more than just temporary
>transitional purposes.
>
>> Here is a list of files that are known to be shared by both packages
>> (according to the Contents file for sid/amd64, which may be
>> slightly out of sync):
>> 
>>   /usr/share/python-wheels/six-1.10.0-py2.py3-none-any.whl
>> 
>> This bug has been filed against both packages. If you, the maintainers of
>> the two packages in question, have agreed on which of the packages will
>> resolve the problem please reassign the bug to that package. You may then
>> also register in the BTS that the other package is affected by the bug.  
>
>I would be inclined to argue that this path clearly belongs to the
>python-six-whl package.  Barry, do you agree with me reassigning this
>bug to python-pip-whl?

-whl packages really only exist for pip and virtualenv.  As per Debian Python
policy, they shouldn't be used for anything else in the archive.  It used to
be that the only way we could provide those .whl files was to build them when
we built the dependent packages, thus we had to add python-six-whl and others.

But now we have dirtbike, which is a tool to turn .deb provided packages back
into wheels, so pip and virtualenv build whatever they need using dirtbike in
their own d/rules files, and have Built-Using headers to at least document
this; or at least *did* - it looks like some things got lost or mis-merged
from an earlier branch :(

So where we ultimately want to end up is that python-six-whl and the others go
away.  Instead, we'll have only python-pip-whl and another -whl package in
virtualenv to provide a few additional requirements.  I haven't uploaded or
file bugs for the appropriate changes in the dependent packages yet.  I
thought I had everything working locally and ready to go, but I've run into a
few snafus which I'm still working out.

Anyway, that's the plan.  As you mention, this really is a transitional period
and I thought it would go more smoothly.  /usr/share/python-wheels will not
have two paths owned by two different packages once this is done.  Debian
Python Policy has been updated in bzr but not yet pushed out (there are other
unrelated changes pending).

You're right Colin, that this bug really belongs in pip and I think it should
be duped to #813399; which I closed over the weekend, but maybe not
correctly.  You might be right about the << dependencies, in which case, let's
keep this bug (#814069) as a separate bug, but move it to python-pip.

Hopefully that makes sense.  Apologies for all the brokenness I've introduced.
I had some work priorities that unfortunately interrupted this transition, but
I'll be working only on this transition now until it's all fixed.


pgpf0J7Mx91l1.pgp
Description: OpenPGP digital signature

Bug#790275: marked as done (qstat: FTBFS with glibc 2.21 and gcc-5)

[Debian Bug Tracking System]

Your message dated Mon, 08 Feb 2016 13:21:47 +
with message-id 
and subject line Bug#790275: fixed in qstat 2.15-2
has caused the Debian Bug report #790275,
regarding qstat: FTBFS with glibc 2.21 and gcc-5
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.)


-- 
790275: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=790275
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: qstat
Version: 2.15-1
Severity: normal

>From my pbuilder build log, using a setup preferring glibc and gcc-defaults
from experimental:

...
gcc -DHAVE_CONFIG_H -I.   -Dsysconfdir=\"/etc\" -D_FORTIFY_SOURCE=2 -DDEBUG 
-DENABLE_DUMP  -g -O2 -fstack-protector-strong -Wformat -Werror=format-security 
-Wall -c -o md5.o md5.c
gcc -DHAVE_CONFIG_H -I.   -Dsysconfdir=\"/etc\" -D_FORTIFY_SOURCE=2 -DDEBUG 
-DENABLE_DUMP  -g -O2 -fstack-protector-strong -Wformat -Werror=format-security 
-Wall -c -o qserver.o qserver.c
gcc -DHAVE_CONFIG_H -I.   -Dsysconfdir=\"/etc\" -D_FORTIFY_SOURCE=2 -DDEBUG 
-DENABLE_DUMP  -g -O2 -fstack-protector-strong -Wformat -Werror=format-security 
-Wall -c -o qstat.o qstat.c
In file included from /usr/include/string.h:634:0,
 from qstat.c:31:
qstat.c:2633:7: error: expected identifier or '(' before '__extension__'
 char *strndup(const char *string, size_t len);
   ^
qstat.c: In function 'do_work':
qstat.c:3104:18: warning: variable 'fd' set but not used 
[-Wunused-but-set-variable]
  int pktlen, rc, fd;
  ^
qstat.c: In function 'deal_with_ghostrecon_packet':
qstat.c:9789:26: warning: variable 'end' set but not used 
[-Wunused-but-set-variable]
  char str[256], *start, *end, StartFlag, *lpszIgnoreServerPlayer;
  ^
qstat.c:9789:18: warning: variable 'start' set but not used 
[-Wunused-but-set-variable]
  char str[256], *start, *end, StartFlag, *lpszIgnoreServerPlayer;
  ^
In file included from /usr/include/string.h:634:0,
 from qstat.c:31:
qstat.c: At top level:
qstat.c:12121:7: error: expected identifier or '(' before '__extension__'
 char *strndup(const char *string, size_t len)
   ^
Makefile:543: recipe for target 'qstat.o' failed
make[3]: *** [qstat.o] Error 1
make[3]: Leaving directory '/tmp/buildd/qstat-2.15'
Makefile:580: recipe for target 'all-recursive' failed
make[2]: *** [all-recursive] Error 1
make[2]: Leaving directory '/tmp/buildd/qstat-2.15'
Makefile:397: recipe for target 'all' failed
make[1]: *** [all] Error 2
make[1]: Leaving directory '/tmp/buildd/qstat-2.15'
dh_auto_build: make -j1 returned exit code 2
debian/rules:4: recipe for target 'build' failed
make: *** [build] Error 2
dpkg-buildpackage: error: debian/rules build gave error exit status 2
E: Failed autobuilding of package
-- 
Daniel Schepler
--- End Message ---
--- Begin Message ---
Source: qstat
Source-Version: 2.15-2

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

Debian distribution maintenance software
pp.
Guillaume Delacour  (supplier of updated qstat 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, 08 Feb 2016 11:21:01 +0100
Source: qstat
Binary: qstat
Architecture: source amd64
Version: 2.15-2
Distribution: unstable
Urgency: medium
Maintainer: Jordi Mallach 
Changed-By: Guillaume Delacour 
Description:
 qstat  - Command-line tool for querying quake (and other) servers
Closes: 790275
Changes:
 qstat (2.15-2) unstable; urgency=medium
 .
   * Fix FTBFS with gcc-5 by importing upstream patch (Closes: #790275)
   * Use autoreconf in addition of autotools, to regenerate build system and not
 stick on older autoreconf versions
   * Update upstream author and homepage
   * Update https url for Vcs-Browser
Checksums-Sha1:
 8b93017f3d92c1cee12392a70e574aaaf6e10a26 1891 qstat_2.15-2.dsc
 15e964ce37db84730bede765637b86d9ff21d74f 11548 qstat_2.15-2.debian.tar.xz
 9f4a478193a8a3e22e7539e24d91f706d95b1b44 283104 qstat-dbgsym_2.15-2_amd64.deb
 

Processed (with 1 error): insightoolkit4 -> castxml bug

[Debian Bug Tracking System]

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

> reassign 813875 castxml
Bug #813875 [src:insighttoolkit4] insighttoolkit4: FTBFS on i386 (member 
reference base type 'void' is not a structure or union)
Bug reassigned from package 'src:insighttoolkit4' to 'castxml'.
No longer marked as found in versions insighttoolkit4/4.9.0-1.
Ignoring request to alter fixed versions of bug #813875 to the same values 
previously set
> affects 813875 insighttoolkit4
Bug #813875 [castxml] insighttoolkit4: FTBFS on i386 (member reference base 
type 'void' is not a structure or union)
Added indication that 813875 affects insighttoolkit4
> retitle 813875 castxml on i386 doesn't support anonymous unions in type
Bug #813875 [castxml] insighttoolkit4: FTBFS on i386 (member reference base 
type 'void' is not a structure or union)
Changed Bug title to 'castxml on i386 doesn't support anonymous unions in type' 
from 'insighttoolkit4: FTBFS on i386 (member reference base type 'void' is not 
a structure or union)'
> specifier.
Unknown command or malformed arguments to command.
> thanks
Stopping processing here.

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

Bug#814181: automake-1.15 fails it's tests with the current perl

[Matthias Klose]

Package: automake-1.15
Version: 1:1.15-3
Severity: serious
Tags: sid stretch patch

automake-1.15 currently fails some of its tests because of the perl warning. 
Patch at

http://launchpadlibrarian.net/236967005/automake-1.15_1%3A1.15-3ubuntu1_1%3A1.15-3ubuntu2.diff.gz

Processed: notfound 813970 in 1.10.6-1, found 813970 in 1.8.20-0+deb8u1

[Debian Bug Tracking System]

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

> notfound 813970 1.10.6-1
Bug #813970 [dbus] dbus: purge fails: invoke-rc.d: initscript dbus, action 
"stop" failed.
No longer marked as found in versions dbus/1.10.6-1.
> found 813970 1.8.20-0+deb8u1
Bug #813970 [dbus] dbus: purge fails: invoke-rc.d: initscript dbus, action 
"stop" failed.
Marked as found in versions dbus/1.8.20-0+deb8u1.
> thanks
Stopping processing here.

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

Bug#814183: openmpi 1.10.2 is broken on powerpc

[Matthias Klose]

Package: src:openmpi
Version: 1.10.2-5
Severity: serious
Tags: sid stretch

openmpi 1.10.2 is broken on powerpc.

Graham Inggs confirmed that at least aces3 and petsc fail in the same way in 
Debian unstable, as soon the mpi test program is launched.


[...]
Possible error running C/C++ src/snes/examples/tutorials/ex19 with 1 MPI process
See http://www.mcs.anl.gov/petsc/documentation/faq.html
--
A deprecated MCA variable value was specified in the environment or
on the command line.  Deprecated MCA variables should be avoided;
they may disappear in future releases.

  Deprecated variable: orte_rsh_agent
  New variable:plm_rsh_agent
--
lid velocity = 0.0016, prandtl # = 1, grashof # = 1
Number of SNES iterations = 2

Session terminated, terminating shell... ...terminated.
make: *** [build-arch] Terminated

build logs:
https://launchpad.net/ubuntu/+source/aces3/3.0.8-5build2/+build/8974836
https://launchpad.net/ubuntu/+source/petsc/3.6.2.dfsg1-3build2/+build/8975053

Bug#804558: Failing Unittests on Tweepy [RC]

[Ross Gammon]

Hi,

Adding python(3)-unittest2, vcr & nose to the build dependencies get you
past all the Import Errors. But unfortunately, all (except a few) tests
then fail with "CONNECTION REFUSED".

As most of the tests seem to need an internet connection, it may be best
to disable the tests in Debian.

Regards,

Ross



signature.asc
Description: OpenPGP digital signature

Bug#813722: [Debichem-devel] Bug#813722: Bug#813722: aces3: FTBFS on powerpc

[Michael Banck]

Hi,

On Mon, Feb 08, 2016 at 11:26:17PM +0200, Graham Inggs wrote:
> On 4 February 2016 at 19:52, Mattia Rizzolo  wrote:
> > your package FTBFS on powercpc on the buildds.
> 
> The same happens with petsc, as soon as the mpi test programs are
> launched they use 100% cpu and stop responding.
> See bug #814183.

Hrm, ok.  But clearly aces3 is more broken on newer MPIs and GCC5.  

I'm in contact with upstream now, and hopefully they try to reproduced
with gfortran-5.3 and openmpi-1.10.


Michael

Bug#812995: yorick-ynfft: FTBFS with libnfft version 3.3

[Thibaut Paumard]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Thanks,

I forwarded this bug report to upstream.

Kind regards, Thibaut.

Le 08/02/2016 20:19, Gianfranco Costamagna a écrit :
> Hi Thibaut and Debian Science maintainers,
> 
> I did a little patch to fix the build failure, but now there is a 
> testsuite failure:
> 
> here the patch
> 
> --- yorick-ynfft-1.0.2.orig/yor_nfft.c +++
> yorick-ynfft-1.0.2/yor_nfft.c @@ -312,7 +312,7 @@ struct _op { 
> #define GET_INP_DIMS(op)((op)->plan.N) #define
> GET_OVR_DIMS(op)((op)->plan.n) #define GET_OVR_FACT(op)
> ((op)->plan.sigma) -#define GET_NFFT_FLAGS(op)
> ((op)->plan.nfft_flags) +#define GET_NFFT_FLAGS(op)
> ((op)->plan.flags) #define GET_FFTW_FLAGS(op)
> ((op)->plan.fftw_flags) #define GET_CUTOFF(op)
> ((op)->plan.m) #define GET_NEVALS(op)  ((op)->nevals) @@
> -1013,7 +1013,7 @@ static void make_nfft_plan(nfft_plan *pl }
> 
> /* Precompute interpolation weights. */ -  if ((plan->nfft_flags &
> PRE_ONE_PSI) != 0) { +  if ((plan->flags & PRE_ONE_PSI) != 0) { 
> nfft_precompute_one_psi(plan); } return;
> 
> basically nfft_flags has been renamed in flags.
> 
> the testsuite failure is: make[1]: Entering directory
> '/build/yorick-ynfft-1.0.2' /usr/bin/make tests make[2]: Entering
> directory '/build/yorick-ynfft-1.0.2' /usr/lib/yorick/bin/yorick
> -batch nfft-tests.i 1-D transform (A0 vs. A1): SUCCESS - absolute
> error: max. = 1.9e-14, RMS = 3.9e-15 1-D transform (A1 vs. A2):
> SUCCESS - absolute error: max. = 1.2e-15, RMS = 2.8e-16
> 
> ERROR (nfft_full_matrix) length must be a strictly positive even
> number LINE: 272  FILE: /build/yorick-ynfft-1.0.2/nfft.i yorick:
> quitting on error in batch mode Makefile:97: recipe for target
> 'tests' failed make[2]: *** [tests] Error 1 make[2]: Leaving
> directory '/build/yorick-ynfft-1.0.2' debian/rules:27: recipe for
> target 'override_dh_auto_test' failed
> 
> 
> and I'm not sure what does it mean.
> 
> do you have any clue?
> 
> cheers,
> 
> Gianfranco
> 
> On Thu, 28 Jan 2016 12:37:48 + Ghislain Antony Vaillant 
>  wrote:
>> Package: yorick-ynfft Version: 1.0.2-2 Severity: important
> 
>> Dear Maintainer,
> 
>> This source package fails to build with the latest release of 
>> libnfft available in experimental. The relevant portion of the 
>> build log is available below.
> 
>> Version 3.3 introduced some API breaking changes in the
>> signature of the public structures.
> 
>> ``` cc -I. -DVERSION=\"1.0.2\" -Wdate-time -D_FORTIFY_SOURCE=2
>> -g -O2 -fstack-protector-strong -Wformat -Werror=format-security 
>> -Wdate-time -D_FORTIFY_SOURCE=2  -fPIC -DPLUG_IN -I. 
>> -I/usr/lib/yorick/include -o yor_nfft.o -c yor_nfft.c
>> yor_nfft.c: In function 'op_eval': yor_nfft.c:380:12: warning:
>> assignment from incompatible pointer type
>> [-Wincompatible-pointer-types] inp_dims = GET_INP_DIMS(op); ^
>> yor_nfft.c: In function 'op_extract': yor_nfft.c:313:33: warning:
>> initialization from incompatible pointer type
>> [-Wincompatible-pointer-types] #define GET_OVR_DIMS(op)
>> ((op)->plan.n) ^ yor_nfft.c:448:22: note: in expansion of macro
>> 'GET_OVR_DIMS' const int *src = GET_OVR_DIMS(op); ^
>> yor_nfft.c:312:33: warning: initialization from incompatible
>> pointer type [-Wincompatible-pointer-types] #define 
>> GET_INP_DIMS(op)((op)->plan.N) ^ yor_nfft.c:459:22:
>> note: in expansion of macro 'GET_INP_DIMS' const int *src = 
>> GET_INP_DIMS(op); ^ yor_nfft.c:315:44: error: 'nfft_plan {aka 
>> struct }' has no member named 'nfft_flags' #define 
>> GET_NFFT_FLAGS(op)  ((op)->plan.nfft_flags) ^ 
>> yor_nfft.c:500:27: note: in expansion of macro 'GET_NFFT_FLAGS'
>> int value = get_flags(GET_NFFT_FLAGS(op), GET_FFTW_FLAGS(op)); ^
>>  yor_nfft.c:315:44: error: 'nfft_plan {aka struct }'
>> has no member named 'nfft_flags' #define GET_NFFT_FLAGS(op) 
>> ((op)->plan.nfft_flags) ^ yor_nfft.c:503:17: note: in expansion
>> of macro 'GET_NFFT_FLAGS' int value = GET_NFFT_FLAGS(op); ^ 
>> yor_nfft.c: In function 'make_nfft_plan': yor_nfft.c:1016:12: 
>> error: 'nfft_plan {aka struct }' has no member named 
>> 'nfft_flags' if ((plan->nfft_flags & PRE_ONE_PSI) != 0) { ```
> 
>> -- System Information: Debian Release: stretch/sid APT prefers 
>> testing APT policy: (500, 'testing'), (2, '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_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8) Shell: 
>> /bin/sh linked to /bin/dash Init: systemd (via 
>> /run/systemd/system)
> 

-BEGIN PGP SIGNATURE-
Version: GnuPG v2

iQIcBAEBCAAGBQJWuQkBAAoJEJOUU0jg3ChAoQoP/2RzU5YE8GDl/p3kpUCgFvXe
E1LP031iOT/KAB1MXJgbkjGCP0OTiWf0KhFIgeNsoOVwR5JNcvU0en4vTSCx8uSW
/m3ExJ6kC2zKQ2UGKtSqPe8v3ShlgRnibWVLnQ30LS/X608lJBm/YZbq6UpiKXGI
hEFViwvuKa2bH0nkoS3ySIt4V0QAgGrFJ11Cs7GA9RQX5ya6dh9tmP9RAQ9WR15v
r1SSBvuF6n4Z844KcSwHkVH3mj5gJimxpLUOULKvQvtBFSteWbGrFb+jp7RJZ2on

Bug#814173: postgis-java: (Build-)Depends on OpenJDK 7

[Sebastiaan Couwenberg]

Control: tags -1 pending

On 08-02-16 21:27, Matthias Klose wrote:
> The package build-depends or depends one an openjdk-7-* package,
> which is scheduled for removal for stretch.  Please do not depend
> on a specific openjdk version, but on one of the default-java,
> default-java-headless or default-jdk packages instead.
> 
> default-java defaulting to openjdk-8 on most architectures is now
> available in unstable.

Same story as osmpbf, GJC is not supported so openjdk is an explicit
dependency.

Update package will be available in unstable soon.

Kind Regards,

Bas

-- 
 GPG Key ID: 4096R/6750F10AE88D4AF1
Fingerprint: 8182 DE41 7056 408D 6146  50D1 6750 F10A E88D 4AF1

Processed: Re: Bug#814173: postgis-java: (Build-)Depends on OpenJDK 7

[Debian Bug Tracking System]

Processing control commands:

> tags -1 pending
Bug #814173 [src:postgis-java] postgis-java: (Build-)Depends on OpenJDK 7
Added tag(s) pending.

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

Bug#814174: radare2-bindings: (Build-)Depends on OpenJDK 7

[Matthias Klose]

Package: src:radare2-bindings
Version: 0.9.6-4
Severity: serious
User: debian-j...@lists.debian.org
Usertags: openjdk-8-transition

The package build-depends or depends one an openjdk-7-* package,
which is scheduled for removal for stretch.  Please do not depend
on a specific openjdk version, but on one of the default-java,
default-java-headless or default-jdk packages instead.

default-java defaulting to openjdk-8 on most architectures is now
available in unstable.

Bug#814173: postgis-java: (Build-)Depends on OpenJDK 7

[Matthias Klose]

Package: src:postgis-java
Version: 1:2.2.0-2
Severity: serious
User: debian-j...@lists.debian.org
Usertags: openjdk-8-transition

The package build-depends or depends one an openjdk-7-* package,
which is scheduled for removal for stretch.  Please do not depend
on a specific openjdk version, but on one of the default-java,
default-java-headless or default-jdk packages instead.

default-java defaulting to openjdk-8 on most architectures is now
available in unstable.

Bug#814179: omegat: (Build-)Depends on OpenJDK 7

[Matthias Klose]

Package: src:omegat
Version: 2.3.0.1+dfsg-3
Severity: serious
User: debian-j...@lists.debian.org
Usertags: openjdk-8-transition

The package build-depends or depends one an openjdk-7-* package,
which is scheduled for removal for stretch.  Please do not depend
on a specific openjdk version, but on one of the default-java,
default-java-headless or default-jdk packages instead.

default-java defaulting to openjdk-8 on most architectures is now
available in unstable.

Bug#814175: uwsgi: (Build-)Depends on OpenJDK 7

[Matthias Klose]

Package: src:uwsgi
Version: 2.0.11.2-6
Severity: serious
User: debian-j...@lists.debian.org
Usertags: openjdk-8-transition

The package build-depends or depends one an openjdk-7-* package,
which is scheduled for removal for stretch.  Please do not depend
on a specific openjdk version, but on one of the default-java,
default-java-headless or default-jdk packages instead.

default-java defaulting to openjdk-8 on most architectures is now
available in unstable.

Bug#814161: drmips: (Build-)Depends on OpenJDK 7

[Matthias Klose]

Package: src:drmips
Version: 2.0.1-1
Severity: serious
User: debian-j...@lists.debian.org
Usertags: openjdk-8-transition

The package build-depends or depends one an openjdk-7-* package,
which is scheduled for removal for stretch.  Please do not depend
on a specific openjdk version, but on one of the default-java,
default-java-headless or default-jdk packages instead.

default-java defaulting to openjdk-8 on most architectures is now
available in unstable.

Bug#814180: piespy: (Build-)Depends on OpenJDK 7

[Matthias Klose]

Package: src:piespy
Version: 0.4.0-3
Severity: serious
User: debian-j...@lists.debian.org
Usertags: openjdk-8-transition

The package build-depends or depends one an openjdk-7-* package,
which is scheduled for removal for stretch.  Please do not depend
on a specific openjdk version, but on one of the default-java,
default-java-headless or default-jdk packages instead.

default-java defaulting to openjdk-8 on most architectures is now
available in unstable.

Bug#813819: Needs a rebuild due to libopenobex soname bump

[Tino Mettler]

On Sun, Feb 07, 2016 at 14:24:44 +, Mattia Rizzolo wrote:

> Dear maintainer, attached there is the simple patch that is enough to
> accomplish this.
> 
> I can easily NMU it if you want, or sponsor an upload of it, as you
> prefer.

Hi Mattia,

thanks for the offer to sponsor the upload. I'll incorporate the change
in a new package and also upgrade to the current upstream version.

> I haven't used the git repository since there seems to not be the
> applied patches in d/patches, and the top d/changelog is not finalized
> (still use UNRELEASED, even if there is a tag)

I use gitpkg which handles the patches from corresponding git commits
inside a patches branch. That's why there is no debian/patches in the
master branch. The UNRELEASED in debian/changelog is intended. I'm not
a DD and AFAIK the release is finally set by the uploader.

Regards,
Tino

Bug#814169: osmpbf: (Build-)Depends on OpenJDK 7

[Sebastiaan Couwenberg]

Control: tags -1 pending

On 08-02-16 21:27, Matthias Klose wrote:
> The package build-depends or depends one an openjdk-7-* package,
> which is scheduled for removal for stretch.  Please do not depend
> on a specific openjdk version, but on one of the default-java,
> default-java-headless or default-jdk packages instead.

GJC is not supported, hence the explicit dependency on OpenJDK in
addition to default-jdk.

> default-java defaulting to openjdk-8 on most architectures is now
> available in unstable.

Thanks, the new osmpbf will be available in unstable soon.

Kind Regards,

Bas

-- 
 GPG Key ID: 4096R/6750F10AE88D4AF1
Fingerprint: 8182 DE41 7056 408D 6146  50D1 6750 F10A E88D 4AF1

Processed: closing 754960

[Debian Bug Tracking System]

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

> close 754960 0.7.2-2
Bug #754960 [libapache2-mod-gnutls] libapache2-mod-gnutls: cannot disable SSLv3
Marked as fixed in versions mod-gnutls/0.7.2-2.
Bug #754960 [libapache2-mod-gnutls] libapache2-mod-gnutls: cannot disable SSLv3
Marked Bug as done
> thanks
Stopping processing here.

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

Processed: Re: Bug#814169: osmpbf: (Build-)Depends on OpenJDK 7

[Debian Bug Tracking System]

Processing control commands:

> tags -1 pending
Bug #814169 [src:osmpbf] osmpbf: (Build-)Depends on OpenJDK 7
Added tag(s) pending.

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

Bug#754960: closing 754960

[Daniel Kahn Gillmor]

close 754960 0.7.2-2
thanks

As of 0.7.2-2, GnuTLSPriorities works as expected.  furthermore, SSLv3
is disabled by default in the underlying gnutls library.

So the following directive is sufficient to disable SSLv3 and TLS 1.0:

 GnuTLSPriorities  NORMAL:-VERS-TLS1.0

Bug#814177: jalview: (Build-)Depends on OpenJDK 7

[Matthias Klose]

Package: src:jalview
Version: 2.7.dfsg-4
Severity: serious
User: debian-j...@lists.debian.org
Usertags: openjdk-8-transition

The package build-depends or depends one an openjdk-7-* package,
which is scheduled for removal for stretch.  Please do not depend
on a specific openjdk version, but on one of the default-java,
default-java-headless or default-jdk packages instead.

default-java defaulting to openjdk-8 on most architectures is now
available in unstable.

Bug#814176: azureus: (Build-)Depends on OpenJDK 7

[Matthias Klose]

Package: src:azureus
Version: 4.3.0.6-5
Severity: serious
User: debian-j...@lists.debian.org
Usertags: openjdk-8-transition

The package build-depends or depends one an openjdk-7-* package,
which is scheduled for removal for stretch.  Please do not depend
on a specific openjdk version, but on one of the default-java,
default-java-headless or default-jdk packages instead.

default-java defaulting to openjdk-8 on most architectures is now
available in unstable.

Bug#814178: jaxe: (Build-)Depends on OpenJDK 7

[Matthias Klose]

Package: src:jaxe
Version: 3.5-6
Severity: serious
User: debian-j...@lists.debian.org
Usertags: openjdk-8-transition

The package build-depends or depends one an openjdk-7-* package,
which is scheduled for removal for stretch.  Please do not depend
on a specific openjdk version, but on one of the default-java,
default-java-headless or default-jdk packages instead.

default-java defaulting to openjdk-8 on most architectures is now
available in unstable.

Bug#814182: automake-1.14 not uploadable in unstable

[Matthias Klose]

Package: automake-1.14
Version: 1:1.14.1-4
Severity: serious
Tags: sid

automake-1.14 is currently not uploadable in unstable, because it builds the 
automake binary also built from automake-1.15.  It probably should be removed.

Bug#814168: openjdk-7-jre-dcevm: (Build-)Depends on OpenJDK 7

[Matthias Klose]

Package: src:openjdk-7-jre-dcevm
Version: 7u79-2
Severity: serious
User: debian-j...@lists.debian.org
Usertags: openjdk-8-transition

The package build-depends or depends one an openjdk-7-* package,
which is scheduled for removal for stretch.  Please do not depend
on a specific openjdk version, but on one of the default-java,
default-java-headless or default-jdk packages instead.

default-java defaulting to openjdk-8 on most architectures is now
available in unstable.

Bug#813361: marked as done (doxygen: FTBFS on amd64 due to wrong version of flex)

[Debian Bug Tracking System]

Your message dated Mon, 8 Feb 2016 22:16:07 +0100
with message-id <56b90597.6010...@debian.org>
and subject line fixed
has caused the Debian Bug report #813361,
regarding doxygen: FTBFS on amd64 due to wrong version of flex
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.)


-- 
813361: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=813361
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: doxygen
Version: 1.8.9.1-6
Severity: serious
Justification: fails to build from source

Hi!

doxygen currently fails to build from source with the following error message:

/usr/bin/flex -i -PvhdlcodeYY -t vhdlcode.l | python3 increasebuffer.py > 
../generated_src/doxygen/vhdlcode.cpp
g++ -c -pipe -fno-exceptions -D_LARGEFILE_SOURCE -Wall -W -Wdate-time 
-D_FORTIFY_SOURCE=2 -g -O2 -fstack-protector-strong
-Wformat -Werror=format-security -I../generated_src/doxygen -I../src 
-I../qtools -I../libmd5 -I../vhdlparser
-I/usr/lib/llvm-3.6/include -I/usr/include -o ../objects/doxygen/vhdlcode.o 
../generated_src/doxygen/vhdlcode.cpp
vhdlcode.l:1618:2: error: #error "You seem to be using a version of flex newer 
than 2.5.4 but older than 2.5.33.
These versions do NOT work with doxygen! Please use version <=2.5.4 or >=2.5.33 
or expect things to be parsed wrongly!"
 #endif
  ^

This was tested on amd64.

When addressing this bug, please also consider fixing #808766 [1].

Cheers,
Adrian

> [1] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=808766

-- 
 .''`.  John Paul Adrian Glaubitz
: :' :  Debian Developer - glaub...@debian.org
`. `'   Freie Universitaet Berlin - glaub...@physik.fu-berlin.de
  `-GPG: 62FF 8A75 84E0 2956 9546  0006 7426 3B37 F5B5 F913
--- End Message ---
--- Begin Message ---

Version: 1.8.11-1--- End Message ---

Bug#814172: marked as done (postgis: (Build-)Depends on OpenJDK 7)

[Debian Bug Tracking System]

Your message dated Mon, 8 Feb 2016 22:22:00 +0100
with message-id <56b906f8.5090...@xs4all.nl>
and subject line Re: Bug#814172: postgis: (Build-)Depends on OpenJDK 7
has caused the Debian Bug report #814172,
regarding postgis: (Build-)Depends on OpenJDK 7
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.)


-- 
814172: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=814172
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:postgis
Version: 2.1.8+dfsg-4
Severity: serious
User: debian-j...@lists.debian.org
Usertags: openjdk-8-transition

The package build-depends or depends one an openjdk-7-* package,
which is scheduled for removal for stretch.  Please do not depend
on a specific openjdk version, but on one of the default-java,
default-java-headless or default-jdk packages instead.

default-java defaulting to openjdk-8 on most architectures is now
available in unstable.
--- End Message ---
--- Begin Message ---
fixed 814172 postgis/2.2.0~rc1+dfsg-1~exp1
thanks

On 08-02-16 21:27, Matthias Klose wrote:
> The package build-depends or depends one an openjdk-7-* package,
> which is scheduled for removal for stretch.  Please do not depend
> on a specific openjdk version, but on one of the default-java,
> default-java-headless or default-jdk packages instead.

The java support has been split off into a separate upstream project
packaged in postgis-java since the 2.2.0 release. Both are available in
testing/unstable for a little while already.

Kind Regards,

Bas

-- 
 GPG Key ID: 4096R/6750F10AE88D4AF1
Fingerprint: 8182 DE41 7056 408D 6146  50D1 6750 F10A E88D 4AF1--- End Message ---

Processed: Re: Bug#814172: postgis: (Build-)Depends on OpenJDK 7

[Debian Bug Tracking System]

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

> fixed 814172 postgis/2.2.0~rc1+dfsg-1~exp1
Bug #814172 [src:postgis] postgis: (Build-)Depends on OpenJDK 7
Marked as fixed in versions postgis/2.2.0~rc1+dfsg-1~exp1.
> thanks
Stopping processing here.

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

Bug#813722: [Debichem-devel] Bug#813722: aces3: FTBFS on powerpc

[Graham Inggs]

On 4 February 2016 at 19:52, Mattia Rizzolo  wrote:
> your package FTBFS on powercpc on the buildds.

The same happens with petsc, as soon as the mpi test programs are
launched they use 100% cpu and stop responding.
See bug #814183.

Bug#814163: elki: (Build-)Depends on OpenJDK 7

[Matthias Klose]

Package: src:elki
Version: 0.7.0-6
Severity: serious
User: debian-j...@lists.debian.org
Usertags: openjdk-8-transition

The package build-depends or depends one an openjdk-7-* package,
which is scheduled for removal for stretch.  Please do not depend
on a specific openjdk version, but on one of the default-java,
default-java-headless or default-jdk packages instead.

default-java defaulting to openjdk-8 on most architectures is now
available in unstable.

Bug#814171: plm: (Build-)Depends on OpenJDK 7

[Matthias Klose]

Package: src:plm
Version: 2.6+repack-1
Severity: serious
User: debian-j...@lists.debian.org
Usertags: openjdk-8-transition

The package build-depends or depends one an openjdk-7-* package,
which is scheduled for removal for stretch.  Please do not depend
on a specific openjdk version, but on one of the default-java,
default-java-headless or default-jdk packages instead.

default-java defaulting to openjdk-8 on most architectures is now
available in unstable.

Bug#814167: lwjgl: (Build-)Depends on OpenJDK 7

[Matthias Klose]

Package: src:lwjgl
Version: 2.7.1+dfsg-5
Severity: serious
User: debian-j...@lists.debian.org
Usertags: openjdk-8-transition

The package build-depends or depends one an openjdk-7-* package,
which is scheduled for removal for stretch.  Please do not depend
on a specific openjdk version, but on one of the default-java,
default-java-headless or default-jdk packages instead.

default-java defaulting to openjdk-8 on most architectures is now
available in unstable.

Bug#814169: osmpbf: (Build-)Depends on OpenJDK 7

[Matthias Klose]

Package: src:osmpbf
Version: 1.3.3-5
Severity: serious
User: debian-j...@lists.debian.org
Usertags: openjdk-8-transition

The package build-depends or depends one an openjdk-7-* package,
which is scheduled for removal for stretch.  Please do not depend
on a specific openjdk version, but on one of the default-java,
default-java-headless or default-jdk packages instead.

default-java defaulting to openjdk-8 on most architectures is now
available in unstable.

Bug#814170: pegasus-wms: (Build-)Depends on OpenJDK 7

[Matthias Klose]

Package: src:pegasus-wms
Version: 4.4.0+dfsg-4
Severity: serious
User: debian-j...@lists.debian.org
Usertags: openjdk-8-transition

The package build-depends or depends one an openjdk-7-* package,
which is scheduled for removal for stretch.  Please do not depend
on a specific openjdk version, but on one of the default-java,
default-java-headless or default-jdk packages instead.

default-java defaulting to openjdk-8 on most architectures is now
available in unstable.

Bug#814172: postgis: (Build-)Depends on OpenJDK 7

[Matthias Klose]

Package: src:postgis
Version: 2.1.8+dfsg-4
Severity: serious
User: debian-j...@lists.debian.org
Usertags: openjdk-8-transition

The package build-depends or depends one an openjdk-7-* package,
which is scheduled for removal for stretch.  Please do not depend
on a specific openjdk version, but on one of the default-java,
default-java-headless or default-jdk packages instead.

default-java defaulting to openjdk-8 on most architectures is now
available in unstable.

Bug#814158: automake-1.15: (Build-)Depends on OpenJDK 7

[Matthias Klose]

Package: src:automake-1.15
Version: 1:1.15-3
Severity: serious
User: debian-j...@lists.debian.org
Usertags: openjdk-8-transition

The package build-depends or depends one an openjdk-7-* package,
which is scheduled for removal for stretch.  Please do not depend
on a specific openjdk version, but on one of the default-java,
default-java-headless or default-jdk packages instead.

default-java defaulting to openjdk-8 on most architectures is now
available in unstable.

Bug#814157: automake-1.14: (Build-)Depends on OpenJDK 7

[Matthias Klose]

Package: src:automake-1.14
Version: 1:1.14.1-4
Severity: serious
User: debian-j...@lists.debian.org
Usertags: openjdk-8-transition

The package build-depends or depends one an openjdk-7-* package,
which is scheduled for removal for stretch.  Please do not depend
on a specific openjdk version, but on one of the default-java,
default-java-headless or default-jdk packages instead.

default-java defaulting to openjdk-8 on most architectures is now
available in unstable.

Bug#814159: avian: (Build-)Depends on OpenJDK 7

[Matthias Klose]

Package: src:avian
Version: 1.1.0-4
Severity: serious
User: debian-j...@lists.debian.org
Usertags: openjdk-8-transition

The package build-depends or depends one an openjdk-7-* package,
which is scheduled for removal for stretch.  Please do not depend
on a specific openjdk version, but on one of the default-java,
default-java-headless or default-jdk packages instead.

default-java defaulting to openjdk-8 on most architectures is now
available in unstable.

Bug#814160: doc-linux-fr: (Build-)Depends on OpenJDK 7

[Matthias Klose]

Package: src:doc-linux-fr
Version: 2013.01-2
Severity: serious
User: debian-j...@lists.debian.org
Usertags: openjdk-8-transition

The package build-depends or depends one an openjdk-7-* package,
which is scheduled for removal for stretch.  Please do not depend
on a specific openjdk version, but on one of the default-java,
default-java-headless or default-jdk packages instead.

default-java defaulting to openjdk-8 on most architectures is now
available in unstable.

Processed: raise severity of ftbfs issues with openjdk-8 (now the default)

[Debian Bug Tracking System]

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

> severity 748045 serious
Bug #748045 [src:openvrml] openvrml: FTBFS with Java 8: cannot stat 
'./javadoc/resources/*': No such file or directory
Severity set to 'serious' from 'important'
> severity 760928 serious
Bug #760928 [src:openvrml] openvrml: ftbfs with OpenJDK 8
Severity set to 'serious' from 'important'
> severity 757536 serious
Bug #757536 [src:eclipse] eclipse: FTBFS with Java 8: Duplicate methods named 
spliterator with the parameters () and ()
Severity set to 'serious' from 'important'
> severity 775775 serious
Bug #775775 [ca-certificates-java] ca-certificates-java: please add support for 
openjdk-8
Severity set to 'serious' from 'normal'
> thanks
Stopping processing here.

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

Bug#770369: I may have a solution for the bug 770369

[Arnaud Ceyrolle]

Hello, I think I might have found why Eterm is behaving like this and have
also a solution.

>From the source tarball listed in the page:
https://packages.debian.org/jessie/eterm

at the link in the right :
eterm_0.9.6.orig.tar.gz


My modification is to just change the line 1564 in src/command.c
from
unsigned short i;
to
unsigned long i;

and recompile, it works for me.

The problem was that, a few lines further 1564, eterm tries to close all
the possible file descriptors from 0 up to 65536.
But when using a short integer, there is an overflow, and when i is at the
value 65535
the i++ instruction puts it at 0, so the loop is beginning again for over
65536 iterations and over and over and forever.

That's why you could see its process consuming 100% of the CPU.

Besides that, I'm surprised that the compiler does not warn about comparing
a long int to a short int in a for loop !!

Let me know if it works for you.

regards

-- 
*Arnaud Ceyrolle*

Bug#814150: blacs-mpi: sync with mpi-default-dev 1.0.2+nmu2

[Aaron M. Ucko]

Source: blacs-mpi
Version: 1.1-33.2
Severity: serious
Justification: fails to build from source (but built successfully in the past)

Please resynchronize blacs-mpi's architecture lists with
mpi-default-dev's.  Per https://packages.debian.org/sid/mpi-default-dev,
sparc64 uses OpenMPI these days, and sh4 and x32 (both currently left
out) use MPICH.  As it stands, blacs-mpi FTBFS on sparc64, and scalapack
and elpa both FTBFS on x32 because blacs-mpi is out of date there.
(FTR, the elpa failure is #814129.)

Thanks!

Bug#813462: marked as done (flexml: FTBFS: flexml-act.c:2888:21: error: C++ style comments are not allowed in ISO C90)

[Debian Bug Tracking System]

Your message dated Mon, 08 Feb 2016 19:34:15 +
with message-id 
and subject line Bug#813462: fixed in flexml 1.9.6-4
has caused the Debian Bug report #813462,
regarding flexml: FTBFS: flexml-act.c:2888:21: error: C++ style comments are 
not allowed in ISO C90
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.)


-- 
813462: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=813462
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: flexml
Version: 1.9.6-3
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,

flexml fails to build from source in unstable/amd64:

  [..]

41 templates created, 207 uses
51/256 equivalence classes created
7/256 meta-equivalence classes created
8 (13 saved) hash collisions, 566 DFAs equal
6 sets of reallocations needed
4051 total table entries needed
  gcc -Wall -ansi -pedantic -Wno-implicit-function-declaration -O2 -g 
-Wdate-time -D_FORTIFY_SOURCE=2  -c -o flexml-act.o flexml-act.c
  flexml-act.c: In function 'yyensure_buffer_stack':
  flexml-act.c:2888:21: error: C++ style comments are not allowed in ISO C90
 num_to_alloc = 1; // After all that talk, this was set to 1 anyways...
   ^
  flexml-act.c:2888:21: error: (this will be reported only once per input file)
  : recipe for target 'flexml-act.o' failed
  make[1]: *** [flexml-act.o] Error 1
  make[1]: Leaving directory 
'/home/lamby/temp/cdt.20160202094936.RNSXeBTn8Z/flexml-1.9.6'
  dh_auto_build: make -j1 returned exit code 2
  debian/rules:7: 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
   `-


flexml.1.9.6-3.unstable.amd64.log.txt.gz
Description: Binary data
--- End Message ---
--- Begin Message ---
Source: flexml
Source-Version: 1.9.6-4

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

Debian distribution maintenance software
pp.
Martin Quinson  (supplier of updated flexml 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, 08 Feb 2016 17:16:45 +0100
Source: flexml
Binary: flexml
Architecture: source amd64
Version: 1.9.6-4
Distribution: unstable
Urgency: medium
Maintainer: Martin Quinson 
Changed-By: Martin Quinson 
Description:
 flexml - Fast validating XML processors and applications generator
Closes: 813462
Changes:
 flexml (1.9.6-4) unstable; urgency=medium
 .
   * Rework how the output is sorted, so that it still compiles SimGrid.
   * d/p/FTBFS-pedantic: remove -ansi -pedantic flag as Flex parsers
 don't compile with these flags on modern compilers (Closes: #813462).
Checksums-Sha1:
 b47ec6d3c205c4d89caafc8e42c61f94373377f6 1853 flexml_1.9.6-4.dsc
 7e483b234dc06528d169d6bb65725eda4c3f6d26 8712 flexml_1.9.6-4.debian.tar.xz
 a76adb90e9594b38cfbaf2fde7b692d899fd1e68 16538 flexml-dbgsym_1.9.6-4_amd64.deb
 434bdb9ad4cb6bf9ede83dafc5aeb0c6a72a7190 90424 flexml_1.9.6-4_amd64.deb
Checksums-Sha256:
 470914f5f3f07999861af760b1f919e8c9ec2309138733a54c1604b1431f1766 1853 
flexml_1.9.6-4.dsc
 ae08e00c5fe7e269ac9637aab9f92bf479c89404b54c1b4eec5f8f0aac466bd5 8712 
flexml_1.9.6-4.debian.tar.xz
 8f0a426c566751109c0ab56bb1b050ec40b203de824f9ff4d36989c97233ee93 16538 
flexml-dbgsym_1.9.6-4_amd64.deb
 03462f7632c5116accc8e8d749e6e11349650e7b176aa2697cdb3b4ab25fa6f4 90424 
flexml_1.9.6-4_amd64.deb
Files:
 548cab249d78be38cbcd825f974d38d9 1853 devel optional flexml_1.9.6-4.dsc
 360c6629a918ccc3f46526a3f114cf1a 8712 devel optional 
flexml_1.9.6-4.debian.tar.xz
 45c0948646da54372e3570eecc985f3d 16538 debug extra 
flexml-dbgsym_1.9.6-4_amd64.deb
 f59efbb3537f5eaaa3436c3df7207eb2 90424 devel optional flexml_1.9.6-4_amd64.deb

-BEGIN PGP SIGNATURE-
Version: GnuPG v1

Bug#814146: jpathwatch: FTBFS: jni.h:45:20: fatal error: jni_md.h: No such file or directory

[Chris Lamb]

Source: jpathwatch
Version: 0.95-3
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,

jpathwatch fails to build from source in unstable/amd64:

  [..]

  debian/rules override_dh_auto_build
  make[1]: Entering directory 
'/home/lamby/temp/cdt.20160208200841.5hv5hxrBAb/jpathwatch-0.95'
  # build JNI library
  /usr/bin/make -C jpathwatch-native/src -f ../../debian/Makefile.jni
  make[2]: Entering directory 
'/home/lamby/temp/cdt.20160208200841.5hv5hxrBAb/jpathwatch-0.95/jpathwatch-native/src'
  g++ -g -O2 -fstack-protector-strong -Wformat -Werror=format-security 
-Wdate-time -D_FORTIFY_SOURCE=2 -fPIC -I/usr/lib/jvm/default-java/include  -c 
-o LinuxPathWatchService.o LinuxPathWatchService.cpp
  In file included from name_pachler_nio_file_impl_LinuxPathWatchService.h:2:0,
   from LinuxPathWatchService.cpp:28:
  /usr/lib/jvm/default-java/include/jni.h:45:20: fatal error: jni_md.h: No such 
file or directory
  compilation terminated.
  : recipe for target 'LinuxPathWatchService.o' failed
  make[2]: *** [LinuxPathWatchService.o] Error 1
  make[2]: Leaving directory 
'/home/lamby/temp/cdt.20160208200841.5hv5hxrBAb/jpathwatch-0.95/jpathwatch-native/src'
  debian/rules:7: recipe for target 'override_dh_auto_build' failed
  make[1]: *** [override_dh_auto_build] Error 2
  make[1]: Leaving directory 
'/home/lamby/temp/cdt.20160208200841.5hv5hxrBAb/jpathwatch-0.95'
  debian/rules:4: 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
   `-


jpathwatch.0.95-3.unstable.amd64.log.txt.gz
Description: Binary data

Bug#812995: yorick-ynfft: FTBFS with libnfft version 3.3

[Gianfranco Costamagna]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Hi Thibaut and Debian Science maintainers,

I did a little patch to fix the build failure, but now there is a
testsuite failure:

here the patch

- --- yorick-ynfft-1.0.2.orig/yor_nfft.c
+++ yorick-ynfft-1.0.2/yor_nfft.c
@@ -312,7 +312,7 @@ struct _op {
 #define GET_INP_DIMS(op)((op)->plan.N)
 #define GET_OVR_DIMS(op)((op)->plan.n)
 #define GET_OVR_FACT(op)((op)->plan.sigma)
- -#define GET_NFFT_FLAGS(op)  ((op)->plan.nfft_flags)
+#define GET_NFFT_FLAGS(op)  ((op)->plan.flags)
 #define GET_FFTW_FLAGS(op)  ((op)->plan.fftw_flags)
 #define GET_CUTOFF(op)  ((op)->plan.m)
 #define GET_NEVALS(op)  ((op)->nevals)
@@ -1013,7 +1013,7 @@ static void make_nfft_plan(nfft_plan *pl
   }

   /* Precompute interpolation weights. */
- -  if ((plan->nfft_flags & PRE_ONE_PSI) != 0) {
+  if ((plan->flags & PRE_ONE_PSI) != 0) {
 nfft_precompute_one_psi(plan);
   }
   return;

basically nfft_flags has been renamed in flags.

the testsuite failure is:
make[1]: Entering directory '/build/yorick-ynfft-1.0.2'
/usr/bin/make tests
make[2]: Entering directory '/build/yorick-ynfft-1.0.2'
/usr/lib/yorick/bin/yorick -batch nfft-tests.i
1-D transform (A0 vs. A1): SUCCESS
  - absolute error: max. = 1.9e-14, RMS = 3.9e-15
1-D transform (A1 vs. A2): SUCCESS
  - absolute error: max. = 1.2e-15, RMS = 2.8e-16

ERROR (nfft_full_matrix) length must be a strictly positive even number
  LINE: 272  FILE: /build/yorick-ynfft-1.0.2/nfft.i
yorick: quitting on error in batch mode
Makefile:97: recipe for target 'tests' failed
make[2]: *** [tests] Error 1
make[2]: Leaving directory '/build/yorick-ynfft-1.0.2'
debian/rules:27: recipe for target 'override_dh_auto_test' failed


and I'm not sure what does it mean.

do you have any clue?

cheers,

Gianfranco

On Thu, 28 Jan 2016 12:37:48 + Ghislain Antony Vaillant
 wrote:
> Package: yorick-ynfft Version: 1.0.2-2 Severity: important
> 
> Dear Maintainer,
> 
> This source package fails to build with the latest release of
> libnfft available in experimental. The relevant portion of the
> build log is available below.
> 
> Version 3.3 introduced some API breaking changes in the signature
> of the public structures.
> 
> ``` cc -I. -DVERSION=\"1.0.2\" -Wdate-time -D_FORTIFY_SOURCE=2  -g
> -O2 -fstack-protector-strong -Wformat -Werror=format-security
> -Wdate-time -D_FORTIFY_SOURCE=2  -fPIC -DPLUG_IN -I.
> -I/usr/lib/yorick/include -o yor_nfft.o -c yor_nfft.c yor_nfft.c:
> In function 'op_eval': yor_nfft.c:380:12: warning: assignment from
> incompatible pointer type [-Wincompatible-pointer-types] inp_dims =
> GET_INP_DIMS(op); ^ yor_nfft.c: In function 'op_extract': 
> yor_nfft.c:313:33: warning: initialization from incompatible
> pointer type [-Wincompatible-pointer-types] #define
> GET_OVR_DIMS(op)((op)->plan.n) ^ yor_nfft.c:448:22: note:
> in expansion of macro 'GET_OVR_DIMS' const int *src =
> GET_OVR_DIMS(op); ^ yor_nfft.c:312:33: warning: initialization from
> incompatible pointer type [-Wincompatible-pointer-types] #define
> GET_INP_DIMS(op)((op)->plan.N) ^ yor_nfft.c:459:22: note:
> in expansion of macro 'GET_INP_DIMS' const int *src =
> GET_INP_DIMS(op); ^ yor_nfft.c:315:44: error: 'nfft_plan {aka
> struct }' has no member named 'nfft_flags' #define
> GET_NFFT_FLAGS(op)  ((op)->plan.nfft_flags) ^ 
> yor_nfft.c:500:27: note: in expansion of macro 'GET_NFFT_FLAGS' int
> value = get_flags(GET_NFFT_FLAGS(op), GET_FFTW_FLAGS(op)); ^ 
> yor_nfft.c:315:44: error: 'nfft_plan {aka struct }' has
> no member named 'nfft_flags' #define GET_NFFT_FLAGS(op)
> ((op)->plan.nfft_flags) ^ yor_nfft.c:503:17: note: in expansion of
> macro 'GET_NFFT_FLAGS' int value = GET_NFFT_FLAGS(op); ^ 
> yor_nfft.c: In function 'make_nfft_plan': yor_nfft.c:1016:12:
> error: 'nfft_plan {aka struct }' has no member named
> 'nfft_flags' if ((plan->nfft_flags & PRE_ONE_PSI) != 0) { ```
> 
> -- System Information: Debian Release: stretch/sid APT prefers
> testing APT policy: (500, 'testing'), (2, '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_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8) Shell:
> /bin/sh linked to /bin/dash Init: systemd (via
> /run/systemd/system)
-BEGIN PGP SIGNATURE-
Version: GnuPG v1

iQIcBAEBCAAGBQJWuOo3AAoJEPNPCXROn13ZWQ4P/Ax0NS7aK0l20yCbxb0ljHj6
o7mWX7YvyIiUStZod5mByDHXJPimxEw89GkjcB/5XliYjZnv/OgNJiaTJkWZ/ERo
12POS3hbgpM30b3QiavsosrD8O8dCGY4rQyU4VST05flGpo16ENiieeHavUe2eL5
CnslkG1x8jGVN6aEnEUjEzdL775TvQe9FigvugGqEcp1s6A1bdF5ZaZsJhbH99bO
lUzX5UCS13GpdASQO5kvVGANFsVqR51xgrcL6jnatAA+Q3wcvHbJwM++SoaKO+Pd
qt5opAfwPzG+LoLPJrjbjxHRWdr10/yTCZVEfjnMY1D0s41hujWZuWCX+mIMU0qT
52V0IYtk42g31dYqULpiXZyppZdMdm2snfdcpL+A2qeKNeWQIaw35IxAGyXzBzFk
rYWYm6+mdzljtlFXO04WDnEhLuIFei+j8DfH1kKOdmCbDDyj3X90pw3BB9V//8W2

Processed: your mail

[Debian Bug Tracking System]

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

> tags 813332 moreinfo
Bug #813332 [trang] trang fails with NullPointerException
Added tag(s) moreinfo.
>
End of message, stopping processing here.

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

Bug#813332: trang fails with NullPointerException

[Eugene Zhukov]

tags -1 moreinfo

Could you please provide more information e.g. input files you tried
with, the command you run?

Bug#814153: wimlib: packing the source fails

[Adam Borowski]

Source: wimlib
Version: 1.8.3-1
Severity: serious

Hi!
I'm afraid that trying to pack up the source for wimlib (dpkg-buildpackage -S)
fails:

dpkg-buildpackage: source package wimlib
dpkg-buildpackage: source version 1.8.3-1.1
dpkg-buildpackage: source distribution unstable
dpkg-buildpackage: source changed by Adam Borowski 
 dpkg-source --before-build wimlib-1.8.3
 fakeroot debian/rules clean
dh clean --with=autoreconf --parallel
   dh_testdir -O--parallel
   dh_auto_clean -O--parallel
   dh_autoreconf_clean -O--parallel
   dh_clean -O--parallel
 dpkg-source -b wimlib-1.8.3
dpkg-source: info: using source format '3.0 (quilt)'
dpkg-source: info: building wimlib using existing ./wimlib_1.8.3.orig.tar.gz
dpkg-source: error: cannot represent change to 
tests/tmpdir_test-imagex-mount/dir/subdir/rel_symlink:
dpkg-source: error:   new version is symlink to hello
dpkg-source: error:   old version is nonexistent
dpkg-source: warning: ignoring deletion of file configure, use 
--include-removal to override
dpkg-source: warning: ignoring deletion of file Makefile.in, use 
--include-removal to override
dpkg-source: warning: ignoring deletion of file build-aux/install-sh, use 
--include-removal to override
dpkg-source: warning: ignoring deletion of file build-aux/ltmain.sh, use 
--include-removal to override
dpkg-source: warning: ignoring deletion of file m4/libtool.m4, use 
--include-removal to override
dpkg-source: warning: ignoring deletion of file programs/mkwinpeimg, use 
--include-removal to override
dpkg-source: error: cannot represent change to doc/html/arrowdown.png: binary 
file contents changed
dpkg-source: error: add doc/html/arrowdown.png in 
debian/source/include-binaries if you want to store the modified binary in the 
debian tarball
dpkg-source: error: cannot represent change to doc/html/arrowright.png: binary 
file contents changed
dpkg-source: error: add doc/html/arrowright.png in 
debian/source/include-binaries if you want to store the modified binary in the 
debian tarball
dpkg-source: error: cannot represent change to doc/html/bc_s.png: binary file 
contents changed
dpkg-source: error: add doc/html/bc_s.png in debian/source/include-binaries if 
you want to store the modified binary in the debian tarball
dpkg-source: error: cannot represent change to doc/html/bdwn.png: binary file 
contents changed
dpkg-source: error: add doc/html/bdwn.png in debian/source/include-binaries if 
you want to store the modified binary in the debian tarball
dpkg-source: error: cannot represent change to doc/html/closed.png: binary file 
contents changed
dpkg-source: error: add doc/html/closed.png in debian/source/include-binaries 
if you want to store the modified binary in the debian tarball
dpkg-source: error: cannot represent change to doc/html/doc.png: binary file 
contents changed
dpkg-source: error: add doc/html/doc.png in debian/source/include-binaries if 
you want to store the modified binary in the debian tarball
dpkg-source: error: cannot represent change to doc/html/doxygen.png: binary 
file contents changed
dpkg-source: error: add doc/html/doxygen.png in debian/source/include-binaries 
if you want to store the modified binary in the debian tarball
dpkg-source: error: cannot represent change to doc/html/folderclosed.png: 
binary file contents changed
dpkg-source: error: add doc/html/folderclosed.png in 
debian/source/include-binaries if you want to store the modified binary in the 
debian tarball
dpkg-source: error: cannot represent change to doc/html/folderopen.png: binary 
file contents changed
dpkg-source: error: add doc/html/folderopen.png in 
debian/source/include-binaries if you want to store the modified binary in the 
debian tarball
dpkg-source: warning: file wimlib-1.8.3/doc/html/graph_legend.md5 has no final 
newline (either original or modified version)
dpkg-source: warning: file wimlib-1.8.3/doc/html/jquery.js has no final newline 
(either original or modified version)
dpkg-source: error: cannot represent change to doc/html/nav_f.png: binary file 
contents changed
dpkg-source: error: add doc/html/nav_f.png in debian/source/include-binaries if 
you want to store the modified binary in the debian tarball
dpkg-source: error: cannot represent change to doc/html/nav_g.png: binary file 
contents changed
dpkg-source: error: add doc/html/nav_g.png in debian/source/include-binaries if 
you want to store the modified binary in the debian tarball
dpkg-source: error: cannot represent change to doc/html/nav_h.png: binary file 
contents changed
dpkg-source: error: add doc/html/nav_h.png in debian/source/include-binaries if 
you want to store the modified binary in the debian tarball
dpkg-source: error: cannot represent change to doc/html/open.png: binary file 
contents changed
dpkg-source: error: add doc/html/open.png in debian/source/include-binaries if 
you want to store the modified binary in the debian tarball
dpkg-source: error: cannot represent change to doc/html/search/close.png: 

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

[Gianfranco Costamagna]

Hi Paul and Abou,

First thanks for having a look at the problem :)
>The "file" it tries to open is stderr ;)


>I agree with that statement. Unless we find out that it never worked on
>arm*, we just have to fix whatever needs fixing.

sure, in general if you want to support arm* you would like to fix this issue.

I was saying instead:
"I'm not sure many people runs hedgewars on arm* architectures", so if you think
this is a corner case for some arm architecture, and consider not worth a fix, 
feel
free to close (I have no knowledge about the topic, so I'll accept your 
decision).

(but for sure, if there is a bug, fixing is always the best option)


cheers,

Gianfranco

Bug#814162: hyperestraier: (Build-)Depends on OpenJDK 7

[Matthias Klose]

Package: src:hyperestraier
Version: 1.4.13-13
Severity: serious
User: debian-j...@lists.debian.org
Usertags: openjdk-8-transition

The package build-depends or depends one an openjdk-7-* package,
which is scheduled for removal for stretch.  Please do not depend
on a specific openjdk version, but on one of the default-java,
default-java-headless or default-jdk packages instead.

default-java defaulting to openjdk-8 on most architectures is now
available in unstable.

Bug#814164: ikvm: (Build-)Depends on OpenJDK 7

[Matthias Klose]

Package: src:ikvm
Version: 7.2.4630.5+ds-2
Severity: serious
User: debian-j...@lists.debian.org
Usertags: openjdk-8-transition

The package build-depends or depends one an openjdk-7-* package,
which is scheduled for removal for stretch.  Please do not depend
on a specific openjdk version, but on one of the default-java,
default-java-headless or default-jdk packages instead.

default-java defaulting to openjdk-8 on most architectures is now
available in unstable.

Bug#814166: libsbml: (Build-)Depends on OpenJDK 7

[Matthias Klose]

Package: src:libsbml
Version: 5.12.0+dfsg-2
Severity: serious
User: debian-j...@lists.debian.org
Usertags: openjdk-8-transition

The package build-depends or depends one an openjdk-7-* package,
which is scheduled for removal for stretch.  Please do not depend
on a specific openjdk version, but on one of the default-java,
default-java-headless or default-jdk packages instead.

default-java defaulting to openjdk-8 on most architectures is now
available in unstable.

Bug#814165: jcc: (Build-)Depends on OpenJDK 7

[Matthias Klose]

Package: src:jcc
Version: 2.20-1
Severity: serious
User: debian-j...@lists.debian.org
Usertags: openjdk-8-transition

The package build-depends or depends one an openjdk-7-* package,
which is scheduled for removal for stretch.  Please do not depend
on a specific openjdk version, but on one of the default-java,
default-java-headless or default-jdk packages instead.

default-java defaulting to openjdk-8 on most architectures is now
available in unstable.

Processed: tagging 804536

[Debian Bug Tracking System]

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

> tags 804536 + pending
Bug #804536 [gcc-5] gcc-5: [mips,mipsel] regression in optimization causes 
FTBFS for gsoap
Added tag(s) pending.
> thanks
Stopping processing here.

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

Bug#813819: Needs a rebuild due to libopenobex soname bump

[Mattia Rizzolo]

On Mon, Feb 08, 2016 at 10:05:21PM +0100, Tino Mettler wrote:
> thanks for the offer to sponsor the upload. I'll incorporate the change
> in a new package and also upgrade to the current upstream version.

ok.
feel free to hurry as you are pleased since this is the last package
blocking that transition ;)

For completeness sake: this kind of thing should not happen.  See the
transition bug to see what went wrong with it.

> > I haven't used the git repository since there seems to not be the
> > applied patches in d/patches, and the top d/changelog is not finalized
> > (still use UNRELEASED, even if there is a tag)
> 
> I use gitpkg which handles the patches from corresponding git commits
> inside a patches branch. That's why there is no debian/patches in the
> master branch.

ok, I've never used gitpkg, and even if I use git-buildpackage for some
tasks I'm still in love with plain raw quilt for handing the patches.

And I also now see that README.source I really should have noticed
before...

> The UNRELEASED in debian/changelog is intended. I'm not
> a DD and AFAIK the release is finally set by the uploader.

well, guess that any sponsor is different.  I'd usually agree that doing
the change before a sponsor say "ok, let's upload now" may be a waste,
but I also personally believe that the tag should really reflect that
uploaded package, and in this case doesn't.  And anyway there are no
written rules about how one is supposed to handle the git repository of
a package (some teams have some rules, but otherwise there are really
none).  Given this whole business if you are going to ask sponsorship to
me please send me a signed .dsc somewhere (mentors.d.n, for example) :)

-- 
regards,
Mattia Rizzolo

GPG Key: 66AE 2B4A FCCF 3F52 DA18  4D18 4B04 3FCD B944 4540  .''`.
more about me:  http://mapreri.org  : :'  :
Launchpad user: https://launchpad.net/~mapreri  `. `'`
Debian QA page: https://qa.debian.org/developer.php?login=mattia  `-


signature.asc
Description: PGP signature