Bug#808052: should enemies-of-carlotta be removed?

[Mattia Rizzolo]

Source: enemies-of-carlotta
Version: 1.2.6-4
Severity: serious


Dear maintainer,

I think it can make sense to remove enemies-of-carlotta from the
archive:

* It has an unfixed RC bug, filed more half an year ago
* It depends on obsolete stuff (python-support)
* Last upload was more than 5 years ago
* It has an incredibily low popcon

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

Bug#808054: docker-libkv: FTBFS: keys.generated.go:11:2: cannot find package "github.com/ugorji/go/codec"

[Chris Lamb]

Source: docker-libkv
Version: 0.1.0-1
Severity: serious
Justification: fails to build from source
User: reproducible-bui...@lists.alioth.debian.org
Usertags: ftbfs
X-Debbugs-Cc: reproducible-bui...@lists.alioth.debian.org

Dear Maintainer,

docker-libkv fails to build from source in unstable/amd64:

  [..]

 dh_auto_build -O--buildsystem=golang
go install -v github.com/docker/libkv github.com/docker/libkv/store 
github.com/docker/libkv/store/boltdb github.com/docker/libkv/store/etcd 
github.com/docker/libkv/store/mock github.com/docker/libkv/store/zookeeper 
github.com/docker/libkv/testutils
  src/github.com/coreos/etcd/client/keys.generated.go:11:2: cannot find package 
"github.com/ugorji/go/codec" in any of:
/usr/lib/go/src/github.com/ugorji/go/codec (from $GOROOT)

/home/lamby/temp/cdt.20151215162920.4B7hN8Ws2j/docker-libkv-0.1.0/obj-x86_64-linux-gnu/src/github.com/ugorji/go/codec
 (from $GOPATH)
  dh_auto_build: go install -v github.com/docker/libkv 
github.com/docker/libkv/store github.com/docker/libkv/store/boltdb 
github.com/docker/libkv/store/etcd github.com/docker/libkv/store/mock 
github.com/docker/libkv/store/zookeeper github.com/docker/libkv/testutils 
returned exit code 1
  debian/rules:13: recipe for target 'build' failed
  make: *** [build] Error 1

  [..]

The full build log is attached.


Regards,

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


docker-libkv.0.1.0-1.unstable.amd64.log.txt.gz
Description: Binary data

Bug#808055: php-pinba: FTBFS: PHP Fatal error: Call to a member function getFilelist() on null in /usr/share/php/PEAR/Command/Install.php on line 747

[Chris Lamb]

Source: php-pinba
Version: 1.0.0-2
Severity: serious
Justification: fails to build from source
User: reproducible-bui...@lists.alioth.debian.org
Usertags: ftbfs
X-Debbugs-Cc: reproducible-bui...@lists.alioth.debian.org

Dear Maintainer,

php-pinba fails to build from source in unstable/amd64:

  [..]

 dh_auto_install -O--buildsystem=phppear
/usr/bin/pear -c debian/pearrc -d download_dir=/tmp -d 
include_path=/usr/share/php -d php_bin=/usr/bin/php -d bin_dir=/usr/bin -d 
php_dir=/usr/share/php -d data_dir=/usr/share/php/data -d 
doc_dir=/usr/share/doc/php5-pinba -d test_dir=/usr/share/php/tests install 
--offline --nodeps -P 
/home/lamby/temp/cdt.20151215162945.jSzid3ytVO/php-pinba-1.0.0/debian/php5-pinba
 --nobuild ./pinba-1.0.0/package.xml
  PHP Fatal error:  Call to a member function getFilelist() on null in 
/usr/share/php/PEAR/Command/Install.php on line 747
  dh_auto_install: /usr/bin/pear -c debian/pearrc -d download_dir=/tmp -d 
include_path=/usr/share/php -d php_bin=/usr/bin/php -d bin_dir=/usr/bin -d 
php_dir=/usr/share/php -d data_dir=/usr/share/php/data -d 
doc_dir=/usr/share/doc/php5-pinba -d test_dir=/usr/share/php/tests install 
--offline --nodeps -P 
/home/lamby/temp/cdt.20151215162945.jSzid3ytVO/php-pinba-1.0.0/debian/php5-pinba
 --nobuild ./pinba-1.0.0/package.xml returned exit code 255
  debian/rules:8: recipe for target 'binary' failed
  make: *** [binary] Error 10

  [..]

The full build log is attached.


Regards,

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


php-pinba.1.0.0-2.unstable.amd64.log.txt.gz
Description: Binary data

Bug#808056: python-statsd: FTBFS: AttributeError: assert_called_once

[Chris Lamb]

Source: python-statsd
Version: 3.2.1-1
Severity: serious
Justification: fails to build from source
User: reproducible-bui...@lists.alioth.debian.org
Usertags: ftbfs
X-Debbugs-Cc: reproducible-bui...@lists.alioth.debian.org

Dear Maintainer,

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

  [..]

 dh_auto_test -O--buildsystem=pybuild
  I: pybuild base:184: cd 
/home/lamby/temp/cdt.20151215162938.5GUj6SZkHy/python-statsd-3.2.1/.pybuild/pythonX.Y_2.7/build;
 python2.7 -m nose 
  ..EE
  ==
  ERROR: Socket errors in TCPStatsClient should be raised to user.
  --
  Traceback (most recent call last):
File "/usr/lib/python2.7/dist-packages/nose/case.py", line 197, in runTest
  self.test(*self.arg)
File "/usr/lib/python2.7/dist-packages/mock/mock.py", line 1305, in patched
  return func(*args, **keywargs)
File 
"/home/lamby/temp/cdt.20151215162938.5GUj6SZkHy/python-statsd-3.2.1/.pybuild/pythonX.Y_2.7/build/statsd/tests.py",
 line 945, in test_tcp_raises_exception_to_user
  cl._sock.sendall.assert_called_once()
File "/usr/lib/python2.7/dist-packages/mock/mock.py", line 721, in 
__getattr__
  raise AttributeError(name)
  AttributeError: assert_called_once
  
  ==
  ERROR: Timeout on TCPStatsClient should be set on socket.
  --
  Traceback (most recent call last):
File "/usr/lib/python2.7/dist-packages/nose/case.py", line 197, in runTest
  self.test(*self.arg)
File "/usr/lib/python2.7/dist-packages/mock/mock.py", line 1305, in patched
  return func(*args, **keywargs)
File 
"/home/lamby/temp/cdt.20151215162938.5GUj6SZkHy/python-statsd-3.2.1/.pybuild/pythonX.Y_2.7/build/statsd/tests.py",
 line 957, in test_tcp_timeout
  cl._sock.settimeout.assert_called_once()
File "/usr/lib/python2.7/dist-packages/mock/mock.py", line 721, in 
__getattr__
  raise AttributeError(name)
  AttributeError: assert_called_once
  
  --
  Ran 76 tests in 0.065s
  
  FAILED (errors=2)
  E: pybuild pybuild:274: test: plugin distutils failed with: exit code=1: cd 
/home/lamby/temp/cdt.20151215162938.5GUj6SZkHy/python-statsd-3.2.1/.pybuild/pythonX.Y_2.7/build;
 python2.7 -m nose 
  dh_auto_test: pybuild --test --test-nose -i python{version} -p 2.7 --dir . 
returned exit code 13
  debian/rules:8: recipe for target 'build' failed
  make: *** [build] Error 25

  [..]

The full build log is attached.


Regards,

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


python-statsd.3.2.1-1.unstable.amd64.log.txt.gz
Description: Binary data

Bug#808008: segmentation fault on any code compiled by tcc with libc6 2.21-4

[Vincent Lefevre]

Control: retitle -1 tcc: segmentation fault on any code due to new binutils 
relocations
Control: tags -1 upstream

On 2015-12-15 17:14:54 +0100, Aurelien Jarno wrote:
> Control: retitle -1: segmentation fault on any code due to new binutils 
> relocations

There shouldn't be a ":" after -1.

> I don't think it's related to the glibc. It's related to the fact that
> glibc 2.21-4 in unstable is built with a recent binutils, introducing
> some changes in the relocations. If you rebuild glibc 2.21-4 with
> binutils 2.25.1-7, the problem disappears.
[...]
> As you can see the R_X86_64_GOTPCREL has been replaced by a new
> relocation type R_X86_64_REX_GOTPCRELX. It looks like TCC doesn't
> support it.

Thanks for the information. Reported upstream in the tinycc-devel list
(I don't have the URL yet).

This is still not fixed in the git repository (mob branch).

-- 
Vincent Lefèvre  - Web: 
100% accessible validated (X)HTML - Blog: 
Work: CR INRIA - computer arithmetic / AriC project (LIP, ENS-Lyon)

Bug#808015: acpid: FTBFS: libnetlink.c:497:54: error: comparison between signed and unsigned integer expressions

[Chris Lamb]

>The common thread here is RTA_ALIGN().  My guess is that it's now 
> returning an unsigned.  Adding an (int) to each one should fix it.  E.g.:
> 
>  if ((int)RTA_ALIGN(rta->rta_len) + len > maxlen) {

Yep, works great. (Both in ./libnetlink.c and ./kacpimon/libnetlink.c)


Regards,

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

Bug#786150: marked as done (gextractwinicons: deprecation of python-support)

[Debian Bug Tracking System]

Your message dated Tue, 15 Dec 2015 16:22:37 +
with message-id 
and subject line Bug#786150: fixed in gextractwinicons 0.3.1-1.1
has caused the Debian Bug report #786150,
regarding gextractwinicons: 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.)


-- 
786150: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=786150
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: gextractwinicons
Version: 0.3.1-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: gextractwinicons
Source-Version: 0.3.1-1.1

We believe that the bug you reported is fixed in the latest version of
gextractwinicons, 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.
Mattia Rizzolo  (supplier of updated gextractwinicons 
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, 13 Dec 2015 15:34:41 +
Source: gextractwinicons
Binary: gextractwinicons
Architecture: source
Version: 0.3.1-1.1
Distribution: unstable
Urgency: medium
Maintainer: Fabio Castelli 
Changed-By: Mattia Rizzolo 
Description:
 gextractwinicons - extracts cursors and icons from MS Windows compatible 
resource fi
Closes: 786150
Changes:
 gextractwinicons (0.3.1-1.1) unstable; urgency=medium
 .
   * Non-maintainer upload.
   * Build using dh-python instead of python-support.  Closes: #786150
   * debian/watch: update after the move to github.
Checksums-Sha1:
 b285ed3fa3e238a19ef6c0ddb3d19a43c6194819 2081 gextractwinicons_0.3.1-1.1.dsc
 0ae6ecaf53a2922f141b09a52bf63ecdaa432867 1835 
gextractwinicons_0.3.1-1.1.diff.gz
Checksums-Sha256:
 479a182513be20de3294d5beabbd1623caff99d547f69f21f61a79c11c3c787d 2081 
gextractwinicons_0.3.1-1.1.dsc
 937cd4dfee4814d2a6bb2416dbb02bf68ba03a049255167794b972a269c9cf77 1835 
gextractwinicons_0.3.1-1.1.diff.gz
Files:
 ddc4d92c7d5c7002036e4c713031682b 2081 graphics optional 
gextractwinicons_0.3.1-1.1.dsc
 6ce3feb54da35e53d187bab26174a029 1835 graphics optional 
gextractwinicons_0.3.1-1.1.diff.gz

-BEGIN PGP SIGNATURE-
Version: GnuPG v1

iQIcBAEBCAAGBQJWbZDXAAoJEEsEP825REVAWxkQAJOVjlh3VjAF0nnh4wDryjrp
NtLJ6I6aONriw5QwIRaXKhRxudMsaYTmBXMu/ZhhMtw//IyzSk2FcPspnAQHR4kX
EsgfA5GqXnUin7N80f/Y6Ch+UjcNpVObimQLzU80rD5vApM0KcN+qYWuNZNLF/1n
gVk4jrJLuhMSUxNrsXPp5H8zU4Z5YyegFvI6gEqa5B/LaArm4APLIiGDpvpHv6vr
FUUPR0Ai6XijMSmNk3tqGr6sLW+SBil0ypSeW6bv2TNaSvzMdnNMfXzvDoOOkzKC
VZXZPwogXjS/JNePJknoF+3IgRiLtLieNpijT9O0R1jloLmF1kav+5AH8jXHWEQK
/fPb7YntFH0EFK3FQFnU0FTLNCe4O1yI15nngW5pkIPaCasj6aTiTlKR1A0BePXi
z4s5+740YE8J4y6T1r6R2agGx+aiIOZkaI3n87U9KerUIJuIHXaPeVgIErdTKoDU
frLge2T8WNNAGsKQOmeKOqTy9xfW/ZF+i68UX0A3EUQmjLCSdfkZqN6Q7xxXItm1
aEuCbXxtaBWB/zQBMeNaGa4df4ZUDkG+pUfhuNOcXaPONZpAilVQ+8LV/3xeD43Z
q71XiP9fn7WcE/p0wPfKfe8+DBMRa7XyoaKWeG1hV8mFWUTINpzy1hZhzm+fAs/e

Bug#786141: marked as done (gnome-hearts: deprecation of python-support)

[Debian Bug Tracking System]

Your message dated Tue, 15 Dec 2015 16:49:09 +
with message-id 
and subject line Bug#786141: fixed in gnome-hearts 0.3-2.2
has caused the Debian Bug report #786141,
regarding gnome-hearts: 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.)


-- 
786141: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=786141
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: gnome-hearts
Version: 0.3-2.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: gnome-hearts
Source-Version: 0.3-2.2

We believe that the bug you reported is fixed in the latest version of
gnome-hearts, 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.
Mattia Rizzolo  (supplier of updated gnome-hearts 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, 13 Dec 2015 16:20:50 +
Source: gnome-hearts
Binary: gnome-hearts
Architecture: source
Version: 0.3-2.2
Distribution: unstable
Urgency: medium
Maintainer: Sander Marechal 
Changed-By: Mattia Rizzolo 
Description:
 gnome-hearts - The classic hearts card game for the GNOME desktop
Closes: 786141
Changes:
 gnome-hearts (0.3-2.2) unstable; urgency=medium
 .
   * Non-maintainer upload.
   * Don't recommend gnome-games-extra-data. This package is obsolete and
 doesn't provide anything gnome-hearts could use anyway.
   * Build using dh-python instead of python-support.  Closes: #786141
Checksums-Sha1:
 4b678aa1f867a450c936bf2694c0898b51348ed2 2078 gnome-hearts_0.3-2.2.dsc
 e6bb1356ab9ff7c5176cab4da0062430f1a98bcd 4160 gnome-hearts_0.3-2.2.diff.gz
Checksums-Sha256:
 e7db0b446688d95c45ac82a2dc8c2c0a5ad9c93efbbbe30611a5a5de6b808dcc 2078 
gnome-hearts_0.3-2.2.dsc
 88ed7908cb964f52458af007ddb49aad01203f0b626eabeac2760a4208a7fa62 4160 
gnome-hearts_0.3-2.2.diff.gz
Files:
 dec0f9d77b8a394c99ff2a7bb76c3ca5 2078 games optional gnome-hearts_0.3-2.2.dsc
 311e99dd4b7e8ad1facbc3312425b06c 4160 games optional 
gnome-hearts_0.3-2.2.diff.gz

-BEGIN PGP SIGNATURE-
Version: GnuPG v1

iQIcBAEBCAAGBQJWbZ4RAAoJEEsEP825REVA+eAP/RuM3ON56ymRprm70I35YJrJ
VlxB86sI5mx2Vdz8AU2cix9BbGaUz8zH5Wj0yP9tnxlAp//JmxLVo0fBdRLTYkNj
/WUQwX9GY6yIR3R7gp7bcaHTrl8c+9aP+dqEqddIjpR48KvH0SBFssq9av4Jn01z
0dR/aHpwDYRbR1upurmN5eHz7C9MZskspGBKp+Q1D5OsBkBuN7FsaMjwnWQVPt5m
fi3nc7i+wvW81e7Rh+72yQ/MhL+rf4f7ahaQUNdqmLjfEmWMWgco4S7mKNVYR074
5gMaatHLApJPOnIXY0vqW9egSqOOfWrfWkID+HRcwRV1wE7sKJ7Y2OchuZoZJfLe
9Z5bZq2ZX9JgWJHWoTG+IrBlVylDtkvNNJZUKHQVp64Ug/mNqGced8c5fBqHJgJy
/d5AUYJw+OIKpis1fVJuSmDw9nou2d3tpB3NcWtEJt5YA31zAyndjTpkiq6xFG8W
4ePJY1MWMA3+vewuzO/QTzx4lr1GRkx8R2lmjcY0Q9OMWUDAzltPycd1eWcb+v+p
tCns/m4oAsKSmSxU9hZBumE+YC3VtpF9B1jLzPou2kRYKck1FuFqkrKsFKeRthpE
LgYwGCAFklxGi2EQjGtdTieBUBl7UndJ9Mmb+V9IGK4NZfG3JbjKBeo1AP27zeGC
5kN/v5VHdcSSaNJLwT1j
=LTtz

Bug#808060: should gnome-schedule be removed?

[Mattia Rizzolo]

Package: gnome-schedule
Version: 2.1.1-4
Severity: serious

Dear maintainer,
I think gnome-schedule would be a good candidate for removal from the
archive:

* It's unmaintained (last upload exactly 5 years ago)
* it's dead upstream
* it has RC bugs filed more than half and year ago
* it depends on obsolete libs (python-support)

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

Bug#808014: marked as done (maven2: FTBFS: 'org.apache.maven.plugins:maven-resources-plugin' not found in repository)

[Debian Bug Tracking System]

Your message dated Tue, 15 Dec 2015 17:53:58 +0100
with message-id <567045a6.7040...@apache.org>
and subject line Re: Bug#808014: maven2: FTBFS: 
'org.apache.maven.plugins:maven-resources-plugin' not found in repository
has caused the Debian Bug report #808014,
regarding maven2: FTBFS: 'org.apache.maven.plugins:maven-resources-plugin' not 
found in repository
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.)


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

maven2 fails to build from source in unstable/amd64:

  [..]

  maven-compile:
   [java] + Error stacktraces are turned on.
   [java] [INFO] 
   [java] NOTE: Maven is executing in offline mode. Any artifacts not 
already in your local
   [java] repository will be inaccessible.
   [java] 
   [java] [INFO] Scanning for projects...
   [java] [INFO] Reactor build order: 
   [java] [INFO]   Maven
   [java] [INFO]   Maven Distribution
   [java] [INFO] 

   [java] [INFO] Building Maven
   [java] [INFO]task-segment: [clean, install]
   [java] [INFO] 

   [java] [INFO] [clean:clean {execution: default-clean}]
   [java] [INFO] [install:install {execution: default-install}]
   [java] [INFO] Installing 
/home/lamby/temp/cdt.20151215105225.LtFu4m9JNM/maven2-2.2.1/pom.xml to 
/home/lamby/temp/cdt.20151215105225.LtFu4m9JNM/maven2-2.2.1/debian/tmp/maven-repo/org/apache/maven/maven/debian/maven-debian.pom
   [java] [INFO] 

   [java] [INFO] Building Maven Distribution
   [java] [INFO]task-segment: [clean, install]
   [java] [INFO] 

   [java] [INFO] [clean:clean {execution: default-clean}]
   [java] [INFO] 

   [java] [ERROR] BUILD ERROR
   [java] [INFO] 

   [java] [INFO] Error building POM (may not be this project's POM).
   [java] 
   [java] 
   [java] Project ID: org.apache.maven.plugins:maven-resources-plugin
   [java] 
   [java] Reason: POM 'org.apache.maven.plugins:maven-resources-plugin' not 
found in repository: System is offline.
   [java] 
   [java]   org.apache.maven.plugins:maven-resources-plugin:pom:2.3
   [java] 
   [java] 
   [java]  for project org.apache.maven.plugins:maven-resources-plugin
   [java] 
   [java] 
   [java] [INFO] 

   [java] [INFO] Trace
   [java] org.apache.maven.lifecycle.LifecycleExecutionException: Unable to 
build project for plugin 'org.apache.maven.plugins:maven-resources-plugin': POM 
'org.apache.maven.plugins:maven-resources-plugin' not found in repository: 
System is offline.
   [java] 
   [java]   org.apache.maven.plugins:maven-resources-plugin:pom:2.3
   [java] 
   [java] 
   [java]  for project org.apache.maven.plugins:maven-resources-plugin
   [java]   at 
org.apache.maven.lifecycle.DefaultLifecycleExecutor.verifyPlugin(DefaultLifecycleExecutor.java:1557)
   [java]   at 
org.apache.maven.lifecycle.DefaultLifecycleExecutor.getMojoDescriptor(DefaultLifecycleExecutor.java:1851)
   [java]   at 
org.apache.maven.lifecycle.DefaultLifecycleExecutor.bindLifecycleForPackaging(DefaultLifecycleExecutor.java:1311)
   [java]   at 
org.apache.maven.lifecycle.DefaultLifecycleExecutor.constructLifecycleMappings(DefaultLifecycleExecutor.java:1275)
   [java]   at 
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:534)
   [java]   at 
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:387)
   [java]   at 
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:348)
   [java]   at 

Bug#808008: segmentation fault on any code compiled by tcc with libc6 2.21-4

[Aurelien Jarno]

Control: retitle -1: segmentation fault on any code due to new binutils 
relocations

On 2015-12-15 12:34, Vincent Lefevre wrote:
> Control: retitle -1 segmentation fault on any code compiled by tcc with libc6 
> 2.21-4
> 
> Cc to the glibc maintainers because the cause of the bug is due to
> some change in glibc.

I don't think it's related to the glibc. It's related to the fact that
glibc 2.21-4 in unstable is built with a recent binutils, introducing
some changes in the relocations. If you rebuild glibc 2.21-4 with
binutils 2.25.1-7, the problem disappears.

> On 2015-12-15 09:35:04 +0100, Vincent Lefevre wrote:
> > Code compiled by tcc segfaults:
> > 
> > ypig% cat conftest.c 
> > int main (void)
> > { return 0; }
> > ypig% tcc conftest.c -o conftest
> > ypig% ./conftest 
> > zsh: segmentation fault (core dumped)  ./conftest
> 
> The cause is libc6 2.21. I get this problem with libc6 2.21-4,
> but on another machine, after reverting to libc6 2.19-22, this
> problem no longer occurs. So, I wonder whether this is a tcc
> bug or a glibc one.
> 
> In the "objdump -S" output of conftest, I notice the following
> difference:
> 
> libc6 2.19:
> 
> 00400430 <_init>:
>   400430:   48 83 ec 08 sub$0x8,%rsp
>   400434:   48 8b 05 4d 01 20 00mov0x20014d(%rip),%rax# 
> 600588 <_init+0x200158>
> [...]
> 
> libc6 2.21:
> 
> 004003f0 <_init>:
>   4003f0:   48 83 ec 08 sub$0x8,%rsp
>   4003f4:   48 8b 05 00 00 00 00mov0x0(%rip),%rax# 4003fb 
> <_init+0xb>
> 
> The 0x20014d(%rip) has changed to 0x0(%rip).

This is due to the following change in crti.o:

2.19:

| 000 <_init>:
|0:   48 83 ec 08 sub$0x8,%rsp
|4:   48 8b 05 00 00 00 00mov0x0(%rip),%rax# b <_init+0xb>
| 7: R_X86_64_GOTPCREL__gmon_start__-0x4
|b:   48 85 c0test   %rax,%rax
|e:   74 05   je 15 <_init+0x15>
|   10:   e8 00 00 00 00  callq  15 <_init+0x15>
| 11: R_X86_64_PLT32  __gmon_start__-0x4
| 

12.21:

|  <_init>:
|0:   48 83 ec 08 sub$0x8,%rsp
|4:   48 8b 05 00 00 00 00mov0x0(%rip),%rax# b <_init+0xb>
| 7: R_X86_64_REX_GOTPCRELX   __gmon_start__-0x4
|b:   48 85 c0test   %rax,%rax
|e:   74 05   je 15 <_init+0x15>
|   10:   e8 00 00 00 00  callq  15 <_init+0x15>
| 11: R_X86_64_PLT32  __gmon_start__-0x4

As you can see the R_X86_64_GOTPCREL has been replaced by a new
relocation type R_X86_64_REX_GOTPCRELX. It looks like TCC doesn't
support it.

Aurelien

-- 
Aurelien Jarno  GPG: 4096R/1DDD8C9B
aurel...@aurel32.net http://www.aurel32.net

Processed: Re: segmentation fault on any code compiled by tcc with libc6 2.21-4

[Debian Bug Tracking System]

Processing control commands:

> retitle -1 tcc: segmentation fault on any code due to new binutils relocations
Bug #808008 [tcc] segmentation fault on any code compiled by tcc with libc6 
2.21-4
Changed Bug title to 'tcc: segmentation fault on any code due to new binutils 
relocations' from 'segmentation fault on any code compiled by tcc with libc6 
2.21-4'
> tags -1 upstream
Bug #808008 [tcc] tcc: segmentation fault on any code due to new binutils 
relocations
Added tag(s) upstream.

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

Bug#808021: marked as done (python-tasklib: FTBFS: TaskWarriorException: Invalid JSON: [)

[Debian Bug Tracking System]

Your message dated Tue, 15 Dec 2015 16:23:31 +
with message-id 
and subject line Bug#808021: fixed in python-tasklib 0.11.0-1
has caused the Debian Bug report #808021,
regarding python-tasklib: FTBFS: TaskWarriorException: Invalid JSON: [
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.)


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

Dear Maintainer,

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

  [..]

  
  ==
  ERROR: test_removing_annotation_by_description (tasklib.tests.AnnotationTest)
  --
  Traceback (most recent call last):
File 
"/home/lamby/temp/cdt.20151215105529.I9Zdp3NADZ/python-tasklib-0.5.0/tasklib/tests.py",
 line 70, in test_removing_annotation_by_description
  task = self.tw.tasks.get()
File 
"/home/lamby/temp/cdt.20151215105529.I9Zdp3NADZ/python-tasklib-0.5.0/tasklib/task.py",
 line 275, in get
  num = len(clone)
File 
"/home/lamby/temp/cdt.20151215105529.I9Zdp3NADZ/python-tasklib-0.5.0/tasklib/task.py",
 line 207, in __len__
  self._result_cache = list(self)
File 
"/home/lamby/temp/cdt.20151215105529.I9Zdp3NADZ/python-tasklib-0.5.0/tasklib/task.py",
 line 212, in __iter__
  self._result_cache = self._execute()
File 
"/home/lamby/temp/cdt.20151215105529.I9Zdp3NADZ/python-tasklib-0.5.0/tasklib/task.py",
 line 244, in _execute
  return self.warrior.filter_tasks(self.filter_obj)
File 
"/home/lamby/temp/cdt.20151215105529.I9Zdp3NADZ/python-tasklib-0.5.0/tasklib/task.py",
 line 330, in filter_tasks
  raise TaskWarriorException('Invalid JSON: %s' % data)
  TaskWarriorException: Invalid JSON: [
  
  ==
  ERROR: test_removing_annotation_by_obj (tasklib.tests.AnnotationTest)
  --
  Traceback (most recent call last):
File 
"/home/lamby/temp/cdt.20151215105529.I9Zdp3NADZ/python-tasklib-0.5.0/tasklib/tests.py",
 line 76, in test_removing_annotation_by_obj
  task = self.tw.tasks.get()
File 
"/home/lamby/temp/cdt.20151215105529.I9Zdp3NADZ/python-tasklib-0.5.0/tasklib/task.py",
 line 275, in get
  num = len(clone)
File 
"/home/lamby/temp/cdt.20151215105529.I9Zdp3NADZ/python-tasklib-0.5.0/tasklib/task.py",
 line 207, in __len__
  self._result_cache = list(self)
File 
"/home/lamby/temp/cdt.20151215105529.I9Zdp3NADZ/python-tasklib-0.5.0/tasklib/task.py",
 line 212, in __iter__
  self._result_cache = self._execute()
File 
"/home/lamby/temp/cdt.20151215105529.I9Zdp3NADZ/python-tasklib-0.5.0/tasklib/task.py",
 line 244, in _execute
  return self.warrior.filter_tasks(self.filter_obj)
File 
"/home/lamby/temp/cdt.20151215105529.I9Zdp3NADZ/python-tasklib-0.5.0/tasklib/task.py",
 line 330, in filter_tasks
  raise TaskWarriorException('Invalid JSON: %s' % data)
  TaskWarriorException: Invalid JSON: [
  
  ==
  ERROR: test_all_empty (tasklib.tests.TaskFilterTest)
  --
  Traceback (most recent call last):
File 
"/home/lamby/temp/cdt.20151215105529.I9Zdp3NADZ/python-tasklib-0.5.0/tasklib/tests.py",
 line 23, in test_all_empty
  self.assertEqual(len(self.tw.tasks.all()), 0)
File 
"/home/lamby/temp/cdt.20151215105529.I9Zdp3NADZ/python-tasklib-0.5.0/tasklib/task.py",
 line 207, in __len__
  self._result_cache = list(self)
File 
"/home/lamby/temp/cdt.20151215105529.I9Zdp3NADZ/python-tasklib-0.5.0/tasklib/task.py",
 line 212, in __iter__
  self._result_cache = self._execute()
File 
"/home/lamby/temp/cdt.20151215105529.I9Zdp3NADZ/python-tasklib-0.5.0/tasklib/task.py",
 line 244, in _execute
  return self.warrior.filter_tasks(self.filter_obj)
File 
"/home/lamby/temp/cdt.20151215105529.I9Zdp3NADZ/python-tasklib-0.5.0/tasklib/task.py",
 line 330, in filter_tasks
  raise TaskWarriorException('Invalid JSON: %s' % data)
  TaskWarriorException: Invalid JSON: [
  
  ==
  

Bug#806167: marked as done (python-twisted fails to upgrade because of missing/incorrect replaces/breaks)

[Debian Bug Tracking System]

Your message dated Tue, 15 Dec 2015 17:00:31 +
with message-id 
and subject line Bug#806167: fixed in twisted 15.5.0-3
has caused the Debian Bug report #806167,
regarding python-twisted fails to upgrade because of missing/incorrect 
replaces/breaks
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.)


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

I just tried to upgrade my sid system where various python-twisted packages 
want to upgrade to 15.4.0-1, but it fails while trying to do so:

Current status: 71 (+68) upgradable, 103523 (+45) new.
root@bagend:/home/diederik# aptitude safe-upgrade
Resolving dependencies...
The following packages will be REMOVED:
  python-twisted-conch{u} python-twisted-lore{u} python-twisted-mail{u} 
python-twisted-names{u} python-twisted-news{u} python-twisted-runner{u} 
  python-twisted-words{u} 
The following packages will be upgraded:
  cpp-5 cpp-5-arm-linux-gnueabihf g++-5 gcc-5 gcc-5-arm-linux-gnueabihf 
gcc-5-arm-linux-gnueabihf-base gcc-5-base gcc-5-base:i386 gcc-5-cross-base 
  gcc-5-multilib lib32asan2 lib32atomic1 lib32cilkrts5 lib32gcc-5-dev lib32gcc1 
lib32gomp1 lib32itm1 lib32mpx0 lib32quadmath0 lib32stdc++6 lib32ubsan0 
  libasan2 libasan2-armhf-cross libatomic1 libatomic1-armhf-cross libcc1-0 
libcilkrts5 libdjvulibre-text libdjvulibre21 libgcc-5-dev 
  libgcc-5-dev-armhf-cross libgcc1 libgcc1:i386 libgcc1-armhf-cross 
libgfortran3 libgomp1 libgomp1-armhf-cross libitm1 liblsan0 libmpx0 
libquadmath0 
  libstdc++-5-dev libstdc++6 libstdc++6-armhf-cross libtsan0 libubsan0 
libubsan0-armhf-cross libx32asan2 libx32atomic1 libx32cilkrts5 libx32gcc-5-dev 
  libx32gcc1 libx32gomp1 libx32itm1 libx32quadmath0 libx32stdc++6 libx32ubsan0 
python-cffi-backend python-twisted python-twisted-bin 
  python-twisted-core python-twisted-web 
62 packages upgraded, 0 newly installed, 7 to remove and 3 not upgraded.
Need to get 95,3 MB of archives. After unpacking 715 kB will be freed.
Do you want to continue? [Y/n/?] 
Get: 1 http://ftp.nl.debian.org/debian/ sid/main python-twisted-bin amd64 
15.4.0-1 [19,1 kB]
Get: 2 http://ftp.nl.debian.org/debian/ sid/main python-twisted-core all 
15.4.0-1 [1917 kB]
Get: 3 http://ftp.nl.debian.org/debian/ sid/main python-twisted all 15.4.0-1 
[10,8 kB]
Get: 4 http://ftp.nl.debian.org/debian/ sid/main gcc-5-base i386 5.2.1-25 [167 
kB]
Get: 5 http://ftp.nl.debian.org/debian/ sid/main gcc-5-base amd64 5.2.1-25 [167 
kB]
Get: 6 http://ftp.nl.debian.org/debian/ sid/main libgcc1 amd64 1:5.2.1-25 [38,7 
kB]
Get: 7 http://ftp.nl.debian.org/debian/ sid/main libgcc1 i386 1:5.2.1-25 [46,2 
kB]
Get: 8 http://ftp.nl.debian.org/debian/ sid/main cpp-5 amd64 5.2.1-25 [26,0 MB]
Get: 9 http://ftp.nl.debian.org/debian/ sid/main libcc1-0 amd64 5.2.1-25 [30,4 
kB]
Get: 10 http://ftp.nl.debian.org/debian/ sid/main libgomp1 amd64 5.2.1-25 [54,2 
kB]
Get: 11 http://ftp.nl.debian.org/debian/ sid/main libitm1 amd64 5.2.1-25 [26,7 
kB]
Get: 12 http://ftp.nl.debian.org/debian/ sid/main libatomic1 amd64 5.2.1-25 
[8656 B]
Get: 13 http://ftp.nl.debian.org/debian/ sid/main libasan2 amd64 5.2.1-25 [266 
kB]
Get: 14 http://ftp.nl.debian.org/debian/ sid/main liblsan0 amd64 5.2.1-25 [108 
kB]
Get: 15 http://ftp.nl.debian.org/debian/ sid/main libtsan0 amd64 5.2.1-25 [244 
kB]
Get: 16 http://ftp.nl.debian.org/debian/ sid/main libubsan0 amd64 5.2.1-25 
[98,8 kB]
Get: 17 http://ftp.nl.debian.org/debian/ sid/main libcilkrts5 amd64 5.2.1-25 
[39,5 kB]
Get: 18 http://ftp.nl.debian.org/debian/ sid/main libmpx0 amd64 5.2.1-25 [9448 
B]
Get: 19 http://ftp.nl.debian.org/debian/ sid/main libquadmath0 amd64 5.2.1-25 
[131 kB]
Get: 20 http://ftp.nl.debian.org/debian/ sid/main libstdc++6 amd64 5.2.1-25 
[388 kB]
Get: 21 http://ftp.nl.debian.org/debian/ sid/main g++-5 amd64 5.2.1-25 [15,4 MB]
Get: 22 http://ftp.nl.debian.org/debian/ sid/main libstdc++-5-dev amd64 
5.2.1-25 [1409 kB]  

Get: 23 http://ftp.nl.debian.org/debian/ sid/main libgcc-5-dev amd64 5.2.1-25 
[2217 kB] 
Get: 24 http://ftp.nl.debian.org/debian/ sid/main gcc-5 amd64 5.2.1-25 [26,0 
MB]
Get: 25 http://ftp.nl.debian.org/debian/ sid/main lib32gcc1 amd64 1:5.2.1-25 
[46,0 kB]   

Bug#808058: should gnome-osd be removed?

[Mattia Rizzolo]

Package: gnome-osd
Version: 0.12.2-1.1
Severity: serious

Dear maintainer,
I believe it would be good to remove gnome-osd from the archive:

* it's unmaintained (last maintainer upload more than 7.5 years ago)
* it's obsolete since gnome3, IIUC
* it has RC bugs filed more than half an year ago

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

Bug#808061: should rats be removed from the archive?

[Mattia Rizzolo]

Package: rats
Version: 2.3-1
Severity: serious

Dear maintainer,
I think rats can be removed from the archive:

* It's unmaintained (last upload more than 6 years ago)
* I can't find the upstream site anymore
* low popcon
* currently not in stable
* it FTBFS => RC buggy since moore than 1,5 years


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

Bug#807074: fbreader: includes files with unclear DFSG-freeness and/or copyright status

[Eugene V. Lyubimkin]

On 14.12.2015 22:56, Francesco Poli wrote:
> Well, they themselves say that one of the files under consideration is
> 
> |   Derived, in part, from:
> |
> |* iso-pub.gml
> |
> |Copyright (C) 1986 International Organization for Standardization
> |Permission to copy in any form is granted for use with
> |conforming SGML systems and applications as defined in
> |ISO 8879, provided this notice is included in all copies.
> 
> and similarly for other files.
> 
> Hence, they basically say that some OASIS files (that they distribute
> under DFSG-free terms) are derived, in part, from some ISO files which
> do *not* grant any permission to modify.
> 
> Without any additional explanation, this sounds like a copyright
> violation.

Here our interpretations diverge then. Indeed it's always allowed to suspect, 
but I'd much prefer that a RC bug is filed
after those suspects are confirmed.

>> If they say 'yes', how one is
>> supposed to verify that they really do?
> 
> A simple "yes" answer would not suffice: they need to provide a
> convincing explanation...

Out of curiosity, what can that be?

> Dropping the OASIS files from package fbreader is the last resort
> solution, assuming that those files are not strictly needed for the
> package to provide significant functionality.

If a violation is present, this will be my first resort, otherwise fbreader 
will disappear from testing very quickly.
Between absense of fbreader and worse DocBook format support in fbreader, I 
choose second.

Ad plug: should anyone see a better action course, fbreader is open for 
adoption.

> Please note that, as I have previously said, one FTP Assistant
> confirmed that files under the ISO license are not fit for Debian main:
> https://lists.debian.org/debian-legal/2015/12/msg0.html

I don't read that as something I can directly apply for things under OASIS 
copyright. Of course I might be wrong, that's
why I invited Debian archive masters to the loop. No reason for us to argue any 
longer, let's just wait for what they
think. If those files are unfree, there were in the archive for 7+ years and 
can wait few days I presume.



signature.asc
Description: OpenPGP digital signature

Bug#808042: Should mumble-django be removed?

[Michael Ziegler]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

reassign 808042 ftp.debian.org
severity 808042 normal
retitle 808042 RM: mumble-django -- ROM; RC buggy; low popcon; depends
on obsolete libs

thanks

I also used the correct source email address this time :P


On 15.12.2015 20:09, Mattia Rizzolo wrote:
> On Tue, Dec 15, 2015 at 07:33:38PM +0100, Michael ZIegler wrote:
>> Hi Mattia,
>> 
>> I actually agree, I haven't looked into it for ages and I don't
>> think it is of much use anymore currently.
>> 
>> I'm just not quite sure what I need to do to get it cleanly
>> removed.
> 
> See this for some docs. 
> https://www.debian.org/doc/manuals/developers-reference/ch05.en.html#removing-pkgs
>
>  Here the tl;dr part:
> 
> Just reassign this bug to ftp.d.o and give it the right metadata
> :)
> 
> reassign 808042 ftp.debian.org severity 808042 normal retitle
> 808042 RM: mumble-django -- ROM; RC buggy; low popcon; depends on
> obsolete libs
> 
> 
> Thanks for being so nice! :)
> 


- -- 
Öffentlicher Schlüssel: 48F81543 - Michael Ziegler (Svedrin)
Wo kämen wir denn da hin, wenn jeder nur fragte "Wo kämen wir denn
da hin?", aber niemand ginge, um zu sehen, wohin wir kämen, wenn wir
gingen? (Kurt Marti)

Bug#786138: marked as done (moap: deprecation of python-support)

[Debian Bug Tracking System]

Your message dated Tue, 15 Dec 2015 18:36:05 +
with message-id 
and subject line Bug#786138: fixed in moap 0.2.7-1.1
has caused the Debian Bug report #786138,
regarding moap: 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.)


-- 
786138: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=786138
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: moap
Version: 0.2.7-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: moap
Source-Version: 0.2.7-1.1

We believe that the bug you reported is fixed in the latest version of
moap, 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.
Mattia Rizzolo  (supplier of updated moap 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, 13 Dec 2015 18:10:49 +
Source: moap
Binary: moap
Architecture: source
Version: 0.2.7-1.1
Distribution: unstable
Urgency: medium
Maintainer: Julien Lavergne 
Changed-By: Mattia Rizzolo 
Description:
 moap   - Swiss army knife for project maintainers and developers
Closes: 600239 786138
Changes:
 moap (0.2.7-1.1) unstable; urgency=medium
 .
   * Non-maintainer upload.
   * Suggest git instead of git-core.  Closes: #600239
   * Build using dh-python instead of python-support.  Closes: #786138
Checksums-Sha1:
 e7c23151759f00217dcf54cbc06a29ea34763a77 2039 moap_0.2.7-1.1.dsc
 bf254ab585e334c635b39c906fa7891e64c460c2 3033 moap_0.2.7-1.1.diff.gz
Checksums-Sha256:
 d36162af5aa3a8a28aa694aa14232cfa3ad7b3ea669445f0c0c926a6b944ae86 2039 
moap_0.2.7-1.1.dsc
 8adf95f649ce3b2d5b38f0c72ab9efe9753f4c326cae3b6ae16b81144bd43488 3033 
moap_0.2.7-1.1.diff.gz
Files:
 3f05cbd1cb8538073ed40b76906b105a 2039 devel optional moap_0.2.7-1.1.dsc
 22d3732a4f53c25baa40670b42d5f6ad 3033 devel optional moap_0.2.7-1.1.diff.gz

-BEGIN PGP SIGNATURE-
Version: GnuPG v1

iQIcBAEBCAAGBQJWbbUAAAoJEEsEP825REVAn1IP/iikiGkJwKqiVLirBGqekSBd
Za6ybZtJDgl4qx3n5zfIz1Y1MpcD4q3ekFrqM2ofoM7dXlXsbgHDHVeZdUexOWhk
/Isx1XptPn9Jmp+SEGzTzVCWZi+BbeDP/QLzyeUdke88nEzQD+kFc35ctcB9qYqc
7DXQ0zReqN1ScvH0UDvJul16S+59Gcd20L9clceSwM52uSocsgbtBE57QQVLviw/
jp6OrfnJXJCKBRskRjQlc2Ie49uh6AOvHDNMVz+uwPO5cneldeqPi0BqSM3fXvav
f04Jm+w5EW/duIAgD8y1Y3Coe24O7/xEX/H6ItflPKTSYv5MFP73dAqfaRjiaA6N
inPHZCHzr6aErovEVTg8V+RvSefbw+Q6/0xmwJhlRMJb1fA8tYL8Clm+P3v8tdhY
/kWIQTwZ9zT4MfxUNtAKaH0vIPwA/SzFBytVWAg5uavfWx7NDXBWfNsBKuH2kn6s
Alt3NzoUWDI3X1Knjwp3RShkx/tCAE0NTpruP9ozViQ3Qcu6AKrwT7wz/i5BP3RY
NktCEMCj9pkMiEwWPmeP5iVSqbuL7ihQBhza93JnffT4hAVTwqoDBtzh5aVl6W6j
Qvf1PKfY966QJl6X9KJsphKMxgNUPAxV25pPPbh+xvWIwrwhR45BUlIZaIPcpAF3
yapA/PXpz5peVbwTaMko
=JbbU
-END PGP SIGNATURE End Message ---

Bug#801276: marked as done (fritzing: uninstallable in sid due to too strict dependency on fritzing-parts)

[Debian Bug Tracking System]

Your message dated Tue, 15 Dec 2015 17:50:23 +
with message-id 
and subject line Bug#801276: fixed in fritzing 0.9.2b+dfsg-3
has caused the Debian Bug report #801276,
regarding fritzing: uninstallable in sid due to too strict dependency on 
fritzing-parts
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.)


-- 
801276: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=801276
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: fritzing
Version: 0.9.2b+dfsg-2
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

during a test with piuparts I noticed your package is no longer
installable in sid:

0m20.9s ERROR: Command failed (status=100): ['chroot', 
'/tmp/piupartss/tmpCtDr6q', 'apt-get', '-y', 'install', 
'fritzing=0.9.2b+dfsg-2']
  Reading package lists...
  Building dependency tree...
  Reading state information...
  Some packages could not be installed. This may mean that you have
  requested an impossible situation or if you are using the unstable
  distribution that some required packages have not yet been created
  or been moved out of Incoming.
  The following information may help to resolve the situation:
  
  The following packages have unmet dependencies:
   fritzing : Depends: fritzing-parts (= 0.9.2b+dfsg-2) but it is not going to 
be installed
  E: Unable to correct problems, you have held broken packages.


You have a 
Depends: fritzing-parts (= ${source:Version}),
which is wrong for a package from a different source package.
You probably want
Depends: fritzing-parts (>= ${source:UpstreamVersion})
instead. And maybe also
Depends: fritzing-parts (<< SOMEUPSTREAMVERSIONTHATMAYBEINCOMPATIBLE~)


Cheers,

Andreas
--- End Message ---
--- Begin Message ---
Source: fritzing
Source-Version: 0.9.2b+dfsg-3

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

Debian distribution maintenance software
pp.
Georges Khaznadar  (supplier of updated fritzing 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, 13 Dec 2015 19:43:09 +0100
Source: fritzing
Binary: fritzing fritzing-data
Architecture: source all amd64
Version: 0.9.2b+dfsg-3
Distribution: unstable
Urgency: medium
Maintainer: Enrique Hernández Bello 
Changed-By: Georges Khaznadar 
Description:
 fritzing   - Easy-to-use electronic design software
 fritzing-data - Easy-to-use electronic design software (data files)
Closes: 801276
Changes:
 fritzing (0.9.2b+dfsg-3) unstable; urgency=medium
 .
   * modified the versioned dependency on fritzing-parts. Closes: #801276
Checksums-Sha1:
 cda9f2eeafb71be7f4baec48366b5a8d7c4af377 2096 fritzing_0.9.2b+dfsg-3.dsc
 e47495c70cabeeaef91ee61e2ed676a8e7985726 20972 
fritzing_0.9.2b+dfsg-3.debian.tar.xz
 960c45b1643a23ff76e57121f9723742d726b4c8 3403064 
fritzing-data_0.9.2b+dfsg-3_all.deb
 0b80b0558367eb9a0ec9e1c829d49aeedb7bf906 3817122 
fritzing_0.9.2b+dfsg-3_amd64.deb
Checksums-Sha256:
 abec1d8cc19e08465d67cdfef8720672bf05e100c85c4af1bb157b41f2c1d607 2096 
fritzing_0.9.2b+dfsg-3.dsc
 ae2fe43731d698d8514a06690f2a824b13bfe5521c4b7b4351b5a6b98aba51c6 20972 
fritzing_0.9.2b+dfsg-3.debian.tar.xz
 adaa5438691a21804043e9d6b92673f314db70b09972e1c94ba229c29cbeb143 3403064 
fritzing-data_0.9.2b+dfsg-3_all.deb
 e58cb0b7d16944d0ca66af317eedf90ab961e50758770655948a9918ea60e772 3817122 
fritzing_0.9.2b+dfsg-3_amd64.deb
Files:
 3f048d73d04fa8478256b8b0b50e41c8 2096 electronics optional 
fritzing_0.9.2b+dfsg-3.dsc
 8d1143b3899795782d96e1fe2bef3a8d 20972 electronics optional 
fritzing_0.9.2b+dfsg-3.debian.tar.xz
 aa3bc53f60c3d737916c726634778db1 3403064 electronics optional 
fritzing-data_0.9.2b+dfsg-3_all.deb
 09827b8ea71d5b26f9bfb6a3bd47059f 3817122 electronics optional 
fritzing_0.9.2b+dfsg-3_amd64.deb

-BEGIN PGP SIGNATURE-
Version: GnuPG v1

iQIVAwUBVnBQqhwoFpBxNq45AQgDGg/8D8UrIjf1OwPeACJFuMcmqAgLqOYmILL2
G2BvLLJrHuHDS3yZWYVy54/Z+3mt24CSadXkbE5mVdAuRdOCPep4XP8mxjDCoM4k

Bug#802116: marked as done (ruby-coveralls: FTBFS: `require': cannot load such file -- multi_json (LoadError))

[Debian Bug Tracking System]

Your message dated Tue, 15 Dec 2015 17:34:53 +
with message-id 
and subject line Bug#802116: fixed in ruby-coveralls 0.7.0-2
has caused the Debian Bug report #802116,
regarding ruby-coveralls: FTBFS: `require': cannot load such file -- multi_json 
(LoadError)
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.)


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

Dear Maintainer,

The package fails to build:

Rewriting shebang line of 
/ruby-coveralls-0.7.0/debian/ruby-coveralls/usr/bin/coveralls

┌──┐
│ Install Rubygems integration metadata│
└──┘

generating gemspec at 
/ruby-coveralls-0.7.0/debian/ruby-coveralls/usr/share/rubygems-integration/all/specifications/coveralls-0.7.0.gemspec
/usr/bin/ruby2.1 /usr/bin/gem2deb-test-runner

┌──┐
│ Run tests for ruby2.1 from debian/ruby-tests.rb  │
└──┘

RUBYLIB=/ruby-coveralls-0.7.0/debian/ruby-coveralls/usr/lib/ruby/vendor_ruby:. 
ruby2.1 debian/ruby-tests.rb
/usr/lib/ruby/2.1.0/rubygems/core_ext/kernel_require.rb:55:in `require': cannot 
load such file -- multi_json (LoadError)
from /usr/lib/ruby/2.1.0/rubygems/core_ext/kernel_require.rb:55:in 
`require'
from 
/ruby-coveralls-0.7.0/debian/ruby-coveralls/usr/lib/ruby/vendor_ruby/coveralls/api.rb:4:in
 `'
from 
/ruby-coveralls-0.7.0/debian/ruby-coveralls/usr/lib/ruby/vendor_ruby/coveralls/api.rb:2:in
 `'
from 
/ruby-coveralls-0.7.0/debian/ruby-coveralls/usr/lib/ruby/vendor_ruby/coveralls/api.rb:1:in
 `'
from /usr/lib/ruby/2.1.0/rubygems/core_ext/kernel_require.rb:55:in 
`require'
from /usr/lib/ruby/2.1.0/rubygems/core_ext/kernel_require.rb:55:in 
`require'
from 
/ruby-coveralls-0.7.0/debian/ruby-coveralls/usr/lib/ruby/vendor_ruby/coveralls.rb:3:in
 `'
from /usr/lib/ruby/2.1.0/rubygems/core_ext/kernel_require.rb:55:in 
`require'
from /usr/lib/ruby/2.1.0/rubygems/core_ext/kernel_require.rb:55:in 
`require'
from /ruby-coveralls-0.7.0/spec/spec_helper.rb:35:in `'
from /usr/lib/ruby/2.1.0/rubygems/core_ext/kernel_require.rb:55:in 
`require'
from /usr/lib/ruby/2.1.0/rubygems/core_ext/kernel_require.rb:55:in 
`require'
from /ruby-coveralls-0.7.0/spec/coveralls/coveralls_spec.rb:1:in `'
from /usr/lib/ruby/2.1.0/rubygems/core_ext/kernel_require.rb:55:in 
`require'
from /usr/lib/ruby/2.1.0/rubygems/core_ext/kernel_require.rb:55:in 
`require'
from debian/ruby-tests.rb:2:in `block in '
from debian/ruby-tests.rb:2:in `each'
from debian/ruby-tests.rb:2:in `'
ERROR: Test "ruby2.1" failed. Exiting.
dh_auto_install: dh_ruby --install /ruby-coveralls-0.7.0/debian/ruby-coveralls 
returned exit code 1
debian/rules:15: recipe for target 'binary' failed

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

-- System Information:
Debian Release: stretch/sid
APT prefers unstable
APT policy: (500, 'unstable')
Architecture: amd64 (x86_64)
--- End Message ---
--- Begin Message ---
Source: ruby-coveralls
Source-Version: 0.7.0-2

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

Debian distribution maintenance software
pp.
Miguel Landaeta  (supplier of updated ruby-coveralls 
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: Tue, 15 Dec 2015 

Bug#786183: marked as done (mimms: deprecation of python-support)

[Debian Bug Tracking System]

Your message dated Tue, 15 Dec 2015 18:04:23 +
with message-id 
and subject line Bug#786183: fixed in mimms 3.2.2-1.1
has caused the Debian Bug report #786183,
regarding mimms: 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.)


-- 
786183: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=786183
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: mimms
Version: 3.2.2-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: mimms
Source-Version: 3.2.2-1.1

We believe that the bug you reported is fixed in the latest version of
mimms, 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.
Mattia Rizzolo  (supplier of updated mimms 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, 13 Dec 2015 17:54:05 +
Source: mimms
Binary: mimms
Architecture: source
Version: 3.2.2-1.1
Distribution: unstable
Urgency: medium
Maintainer: Mohammad Ebrahim Mohammadi Panah 
Changed-By: Mattia Rizzolo 
Description:
 mimms  - mms (e.g. mms://) stream downloader
Closes: 786183
Changes:
 mimms (3.2.2-1.1) unstable; urgency=medium
 .
   * Non-maintainer upload.
   * Build using dh-python instead of python-support.  Closes: #786183
   * Bump Standards-Version to 3.9.6, no changes needed.
Checksums-Sha1:
 91ce4ac2ae82ad6ce0f979cc9fb9a2a6100b690b 1939 mimms_3.2.2-1.1.dsc
 322c9c6fe4a21b3342ec81a127aa2bceb63551ed 3280 mimms_3.2.2-1.1.debian.tar.xz
Checksums-Sha256:
 5f9d30fb3c8007d48824a0f831316a6af15ebb855a4501d54c7b3e25f1dba0e8 1939 
mimms_3.2.2-1.1.dsc
 c5ce97cb535add17cbf243221a6d7833e1a7d1805d8a47c188e38ae9465ad96e 3280 
mimms_3.2.2-1.1.debian.tar.xz
Files:
 5a72d885cc69c3e53abceda5d7586c35 1939 net optional mimms_3.2.2-1.1.dsc
 870496a215147bd4d5e95a36e819955f 3280 net optional 
mimms_3.2.2-1.1.debian.tar.xz

-BEGIN PGP SIGNATURE-
Version: GnuPG v1

iQIcBAEBCAAGBQJWbbDCAAoJEEsEP825REVArfEP/12rK2CwZygi0BfWeTNLRYJI
r+Vs6Cpf3UPFVBPdMX79LBSn1gTBISV8mffkauSl3D5dszatAPuBgE8y+SpiotWq
vUf+2e9CJHch+7OvbBan9veRoqHxshkmmgYcUQfm2VkZPwQf+5fs2f7HPiaq6TeL
XsckX83KQhq8fsqaB4W5SmnaFQhCLM8MczFHu1UYNNmS2BHWauVmYQEXsYB72hb4
dP3T3s6M45xD4Eksqk8V/jWG0jeLaMg/5B16kSdKFwI33JMsSoougKQe+J+mZhMa
+Tgu0j9e7Eumy9LSIlIeRt6exZEUxq2/weVjOc67B3H7Tb/h4N4qqVKMjTDZuQ59
e6jobwL2k3LaIXoLfBdu3ZRX8ITEwnRm4m7v7d+9TjnrqTbXo/2Vdtdi7PtLIJG+
YLsWIsuI5xUSx407b+cl17xd1rA97h1ew5uFLMswI8bNLRFrjtoqPuZYLpBHxc8r
8vYyLGOnyRw3LVi1yptzia0zfq1czYdXT816P4xD+HG0ssFEa+IfrAcvJ4jfJGwu
1ut7Yc9OxboMyPVjTeDmeTyjI4j7kH1LLCl+Vek3HvzT5ROzk49+tlieCAxWnQKO
A6L+3kEzm0k90aZl3SmBFTwBtj1J7ty8LTnWgMHPVnVt3GyrEgkKlgUiTjwlRnuH
fKqiTSGVtXtOPHOz5Zw8
=PxjS
-END PGP SIGNATURE End Message ---

Processed (with 1 error): Re: Bug#808042: Should mumble-django be removed?

[Debian Bug Tracking System]

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

> reassign 808042 ftp.debian.org
Bug #808042 [src:mumble-django] Should mumble-django be removed?
Bug reassigned from package 'src:mumble-django' to 'ftp.debian.org'.
No longer marked as found in versions mumble-django/2.13-1.
Ignoring request to alter fixed versions of bug #808042 to the same values 
previously set
> severity 808042 normal
Bug #808042 [ftp.debian.org] Should mumble-django be removed?
Severity set to 'normal' from 'serious'
> retitle 808042 RM: mumble-django -- ROM; RC buggy; low popcon; depends
Bug #808042 [ftp.debian.org] Should mumble-django be removed?
Changed Bug title to 'RM: mumble-django -- ROM; RC buggy; low popcon; depends' 
from 'Should mumble-django be removed?'
> on obsolete libs
Unknown command or malformed arguments to command.
> thanks
Stopping processing here.

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

Bug#808043: linux-image-4.3.0-1-powerpc64: Fail to load md_mod with unknow symbol error

[Ben Hutchings]

Control: retitle -1 [powerpc] Modules fail to load following toolchain upgrade
Control: found -1 4.2.6-2
Control: tag -1 - moreinfo

On Tue, 2015-12-15 at 18:07 +0100, Christian Marillat wrote:
> On 15 déc. 2015 15:55, Ben Hutchings  wrote:
> 
> > Control: tag -1 moreinfo
> > 
> > On Tue, 2015-12-15 at 15:26 +0100, Christian Marillat wrote:
> > > Package: src:linux
> > > Version: 4.3.1-1
> > > Severity: serious
> > > 
> > > Dear Maintainer,
> > > 
> > > Since 4.2.6-2 the Powerpc G5 doesn't start with an error 'unknow symbol 
> > > in md_mod'
> > > 
> > > 4.2.6-1 work fine.
> > > 
> > > / is a RAID0 partition and kernels are in a normal partition in /boot
> > [...]
> > 
> > I don't see any differences between 4.2.6-1 and 4.2.6-2 that relate to
> > the md driver.
> 
> Me too, but the problem come from maybe the compiler or linker.

Right.

For 4.2.6-1: binutils 2.25.1-7           gcc-4.9 4.9.3-5
For 4.2.6-2: binutils 2.25.90.20151125-2 gcc-4.9 4.9.3-8

> > Assuming you get a rescue shell in the initramfs:
> > - The kernel log will show what the symbol is; please send that line
> >   (or lines)
> > - Send the output of 'modinfo -Fvermagic md_mod'
> 
> I don't have access to the rescue shell. CPUs go to 100% and
> the keyboard doesn't work. I attached two photos.
> 
> In the bottom screenshot you'll see that other module fail to load with
> an 'unknow symbol in module".

OK, so everything is failing because the 'mcount' symbol (used for
function tracing) is not found.  It is supposed to be exported from
vmlinux.  Comparing the two versions, there's no difference (aside from
addresses) in the symbols related to mcount, so I think there's a
deeper problem in the module loader.

Ben.

-- 
Ben Hutchings
Logic doesn't apply to the real world. - Marvin Minsky

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

Processed: Re: Bug#808043: linux-image-4.3.0-1-powerpc64: Fail to load md_mod with unknow symbol error

[Debian Bug Tracking System]

Processing control commands:

> retitle -1 [powerpc] Modules fail to load following toolchain upgrade
Bug #808043 [src:linux] linux-image-4.3.0-1-powerpc64: Fail to load md_mod with 
unknow symbol error
Changed Bug title to '[powerpc] Modules fail to load following toolchain 
upgrade' from 'linux-image-4.3.0-1-powerpc64: Fail to load md_mod with unknow 
symbol error'
> found -1 4.2.6-2
Bug #808043 [src:linux] [powerpc] Modules fail to load following toolchain 
upgrade
Marked as found in versions linux/4.2.6-2.
> tag -1 - moreinfo
Bug #808043 [src:linux] [powerpc] Modules fail to load following toolchain 
upgrade
Removed tag(s) moreinfo.

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

Bug#808060: should gnome-schedule be removed?

[Alejandro Ríos Peña]

Hi,

You are right, please remove it.  I am currently Missing in Action, I will
resign to the debian project as my last duty

Many Thanks,

Alejandro Rios


2015-12-15 11:36 GMT-05:00 Mattia Rizzolo :

> Package: gnome-schedule
> Version: 2.1.1-4
> Severity: serious
>
> Dear maintainer,
> I think gnome-schedule would be a good candidate for removal from the
> archive:
>
> * It's unmaintained (last upload exactly 5 years ago)
> * it's dead upstream
> * it has RC bugs filed more than half and year ago
> * it depends on obsolete libs (python-support)
>
> --
> 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  `-
>

Bug#808061: should rats be removed from the archive?

[Alejandro Ríos Peña]

Hi,

You are right, please remove it.  I am currently Missing in Action, I will
resign to the debian project as my last duty

Many Thanks,

Alejandro Rios

2015-12-15 11:39 GMT-05:00 Mattia Rizzolo :

> Package: rats
> Version: 2.3-1
> Severity: serious
>
> Dear maintainer,
> I think rats can be removed from the archive:
>
> * It's unmaintained (last upload more than 6 years ago)
> * I can't find the upstream site anymore
> * low popcon
> * currently not in stable
> * it FTBFS => RC buggy since moore than 1,5 years
>
>
> --
> 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  `-
>

Bug#808008: tcc: segmentation fault on any code compiled by tcc

[Vincent Lefevre]

Package: tcc
Version: 0.9.27~git20140923.9d7fb33-3
Severity: grave
Justification: renders package unusable

Code compiled by tcc segfaults:

ypig% cat conftest.c 
int main (void)
{ return 0; }
ypig% tcc conftest.c -o conftest
ypig% ./conftest 
zsh: segmentation fault (core dumped)  ./conftest

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

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

Versions of packages tcc depends on:
ii  libc6  2.21-4

Versions of packages tcc recommends:
ii  libc6-dev [libc-dev]  2.21-4

tcc suggests no packages.

-- no debconf information

Bug#807571: marked as done (ocserv: fails to install due to insserv rejecting the script header)

[Debian Bug Tracking System]

Your message dated Tue, 15 Dec 2015 10:06:23 +
with message-id 
and subject line Bug#807571: fixed in ocserv 0.10.10-1
has caused the Debian Bug report #807571,
regarding ocserv: fails to install due to insserv rejecting the script header
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.)


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

Hi,

during a test with piuparts I noticed your package failed to install due
to insserv rejecting the script header. Some notes are
available from at https://wiki.debian.org/LSBInitScripts

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

  Selecting previously unselected package ocserv.
  (Reading database ... 
(Reading database ... 7421 files and directories currently installed.)
  Preparing to unpack .../ocserv_0.10.7-1_amd64.deb ...
  Unpacking ocserv (0.10.7-1) ...
  Processing triggers for systemd (228-2) ...
  Setting up ocserv (0.10.7-1) ...
  insserv: Service dbus has to be enabled to start service ocserv
  insserv: exiting now!
  update-rc.d: error: insserv rejected the script header
  dpkg: error processing package ocserv (--configure):
   subprocess installed post-installation script returned error exit status 1
  Processing triggers for systemd (228-2) ...
  Errors were encountered while processing:
   ocserv


cheers,

Andreas


ocserv_0.10.7-1.log.gz
Description: application/gzip
--- End Message ---
--- Begin Message ---
Source: ocserv
Source-Version: 0.10.10-1

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

Debian distribution maintenance software
pp.
Aron Xu  (supplier of updated ocserv 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: Tue, 15 Dec 2015 16:36:00 +0800
Source: ocserv
Binary: ocserv
Architecture: source amd64
Version: 0.10.10-1
Distribution: unstable
Urgency: medium
Maintainer: Aron Xu 
Changed-By: Aron Xu 
Description:
 ocserv - OpenConnect VPN server compatible with Cisco AnyConnect VPN
Closes: 807571
Changes:
 ocserv (0.10.10-1) unstable; urgency=medium
 .
   * New upstream release
   * Add dbus to Depends (Closes: #807571)
Checksums-Sha1:
 4143953a4396bce8c1418f44667fb1cc1b36c7bb 1759 ocserv_0.10.10-1.dsc
 09ac866c34f11fbfdc83c96bc89b551b9191298b 729580 ocserv_0.10.10.orig.tar.xz
 99482c2a920e0e3c035cbb9bc8e4f40d392075d3 58904 ocserv_0.10.10-1.debian.tar.xz
 eff00603a9d5ed2df41855b1b9a3df4af171072f 232368 ocserv_0.10.10-1_amd64.deb
Checksums-Sha256:
 cdaf4c2b40ec15d0c925900dbfdf16e49d4bf07cb9f4a4780626d2161de0df56 1759 
ocserv_0.10.10-1.dsc
 17111607a6c833ea151424a85351a7936c9526a793799c49eea12d19fb4bc725 729580 
ocserv_0.10.10.orig.tar.xz
 497c3c836b3e904d7527658c26d7af575ab4e2a03eb7b9bf3e6ecd0f001e442b 58904 
ocserv_0.10.10-1.debian.tar.xz
 58c8ecb6d4a72f0b470fd28c736a12df931ace1f4a2706c96aad3e524ac2aff4 232368 
ocserv_0.10.10-1_amd64.deb
Files:
 bad4e932da13117093350a718251bec5 1759 net optional ocserv_0.10.10-1.dsc
 1f73ccb66d36cd51279323e95ae99e68 729580 net optional ocserv_0.10.10.orig.tar.xz
 c8a35e763b3848dbf1a7c376f1e02969 58904 net optional 
ocserv_0.10.10-1.debian.tar.xz
 20a6be356ba35c442ac79fef9f3c8be0 232368 net optional ocserv_0.10.10-1_amd64.deb

-BEGIN PGP SIGNATURE-
Version: GnuPG v1

iQEcBAEBCAAGBQJWb9UxAAoJEPbsVcVkKA0e+twH/RhxT7h/WPuWF1AEc2o0ZI7v
e5H/wxclYYlaB3WlfooTEiG30haL08jXY57Upls4qahQ+ijTYvgvmfebkTuQdEoi
byikt5esh2vI7OEKNXBFwCTD0+sOZrx/vwmkOp5Wtvgv+DpHEUWibPldqWHGjkPn
Pazcos8eStSceSeSAzIj6q3EqbZab2Z8dlEb/6fYklZ1EApfYb9dHUPtL3kMxYaA
v19OAz+Fshplul2b2fqiSnBblTB2fQdZGu+bF9J42f3lw4v1N0ofZDTVNOBEbnXx
8CuY4UeE0sxRYYNUZDd2AiKlInpmb1Fj8Ky0zSCLkhd5RluAf2tQ6EuCcpNnGS8=
=ueu+
-END PGP SIGNATURE End Message ---

Bug#808004: libdiet-client2.8: not installable on sid

[Ralf Treinen]

Package: libdiet-client2.8
Version: 2.8.0-1
Severity: serious
User: trei...@debian.org
Usertags: edos-uninstallable
Affects: libdiet-admin2.8, libdiet-sed2.8

Hi,

libdiet-client2.8 is not installable on sid on any architecture. This is
the case at least since 2015-08-02. The reason for this is that it depends
on libstdc++6, but libstdc++6 (5.3.1-3) declares a Breaks relation with
libdiet-client2.8 (<= 2.8.0-1+b3).

The same holds for:

libdiet-admin2.8 (<= 2.8.0-1+b3)
libdiet-sed2.8 (<= 2.8.0-1+b3)

-Ralf.

Bug#786165: gbirthday: deprecation of python-support

[Jérôme]

Hi.

To my knowledge, gbirthday is not worked on by anyone but myself.

The Debian package is maintained is Rolf Leggewie.

I'm clueless about Debian packaging, so I'm afraid I can't help with the
python-support issue. I've paid a look at the wiki page about the
migration to see if I could help, but that's too many new concepts to
grasp.

For the record, gbirthday has moved to GitHub:
https://github.com/Jerome-github/gbirthday/. I should update the watch
file (this seems feasible to me, but there is no need to do it as long
as there is no new release).

Regarding the future of gbirthday, unless somebody takes over, it won't
be ported to Python3/GTK3.

However, I started a Python3/Qt port:

https://github.com/Jerome-github/gbirthday/tree/pyQt4_python3_port

No release date planned ("when it's ready"...). Still a lot of things to
polish. I's not just about graphical toolkit switch, the code is also
pretty old and deserves improvements / simplifications.

The roadmap includes proper Python packaging to replace current makefile
(https://github.com/Jerome-github/gbirthday/issues/7). I hope this will
make Debian packaging easier if not trivial.

Note that if the Qt port is finally released, it may come with a new
name, as gbirthday sounds GTKish.

To conclude, the way I see it:

- Unless somebody comes in, gbirthday won't evolve as it is and will
probably be out of Stretch or the next Debian release due to
dependencies deprecation. I'm happy if I'm wrong.

- I hope to get a Qt version packageable for Stretch. Help welcome, of
course.

Have a nice day.

-- 
Jérôme

Bug#798484: marked as done (libdr-tarantool-perl: FTBFS: Failed 1/19 test programs. 1/853 subtests failed.)

[Debian Bug Tracking System]

Your message dated Tue, 15 Dec 2015 10:39:46 +
with message-id 
and subject line Bug#798484: fixed in libdr-tarantool-perl 0.44-1
has caused the Debian Bug report #798484,
regarding libdr-tarantool-perl: FTBFS: Failed 1/19 test programs. 1/853 
subtests failed.
to be marked as done.

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

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


-- 
798484: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=798484
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: libdr-tarantool-perl
Version: 0.43-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,

libdr-tarantool-perl fails to build from source in unstable/amd64.
tarantool doesn't seem to ship a taraontool_box binary, although it
looks like it should (?).

  [..]

  ok 30 # skip tarantool isn't started
  ok 31 # skip tarantool isn't started
  ok 32 # skip tarantool isn't started
  ok 33 # skip tarantool isn't started
  ok
  Can't exec "tarantool_box": No such file or directory at
  blib/lib/DR/Tarantool/StartTest.pm line 59.
  Use of uninitialized value $str in pattern match (m//) at
  blib/lib/DR/Tarantool/StartTest.pm line 60.
  t/090-parallel-requests.t ... skipped: Too low tarantool version
  Can't exec "tarantool_box": No such file or directory at
  blib/lib/DR/Tarantool/StartTest.pm line 59.
  Use of uninitialized value $str in pattern match (m//) at
  blib/lib/DR/Tarantool/StartTest.pm line 60.
  t/100-transform.t ... skipped: Too low tarantool version
  Can't exec "tarantool_box": No such file or directory at
  blib/lib/DR/Tarantool/StartTest.pm line 59.
  Use of uninitialized value $str in pattern match (m//) at
  blib/lib/DR/Tarantool/StartTest.pm line 60.
  t/110-netsplit-readahead.t .. skipped: Too low tarantool version
  t/120-sessionid.t ... skipped: Coro isn't installed
  t/130-reconnect.t ... skipped: Tarantool is not found
  t/900-podspell.t  
  1..11
  ok 1 - POD spelling for lib/DR/Tarantool.pm
  ok 2 - POD spelling for lib/DR/Tarantool/RealSyncClient.pm
  ok 3 - POD spelling for lib/DR/Tarantool/LLClient.pm
  ok 4 - POD spelling for lib/DR/Tarantool/AsyncClient.pm
  ok 5 - POD spelling for lib/DR/Tarantool/StartTest.pm
  ok 6 - POD spelling for lib/DR/Tarantool/SyncClient.pm
  ok 7 - POD spelling for lib/DR/Tarantool/Iterator.pm
  ok 8 - POD spelling for lib/DR/Tarantool/Tuple.pm
  ok 9 - POD spelling for lib/DR/Tarantool/LLSyncClient.pm
  ok 10 - POD spelling for lib/DR/Tarantool/CoroClient.pm
  ok 11 - POD spelling for lib/DR/Tarantool/Spaces.pm
  ok
  t/910-pod.t . skipped: Test::Pod 1.00 required for
  testing POD
  
  Test Summary Report
  ---
  t/065-realsync-client.t   (Wstat: 65280 Tests: 63 Failed: 1)
Failed test:  63
Non-zero exit status: 255
Parse errors: Bad plan.  You planned 62 tests but ran 63.
  Files=19, Tests=853,  4 wallclock secs ( 0.27 usr  0.06 sys +  2.89
  cusr  0.40 csys =  3.62 CPU)
  Result: FAIL
  Failed 1/19 test programs. 1/853 subtests failed.
  Makefile:1078: recipe for target 'test_dynamic' failed
  make[1]: *** [test_dynamic] Error 255
  make[1]: Leaving directory '/tmp/buildd/libdr-tarantool-perl-0.43'
  /usr/share/cdbs/1/class/makefile.mk:67: recipe for target
  'debian/stamp-makefile-check' failed
  make: *** [debian/stamp-makefile-check] Error 2
  dpkg-buildpackage: error: debian/rules build gave error exit status 2

  [..]

The full build log is attached or can be viewed here:


https://reproducible.debian.net/logs/unstable/amd64/libdr-tarantool-perl_0.43-1.build1.log.gz


Regards,

-- 
  ,''`.
 : :'  : Chris Lamb
 `. `'`  la...@debian.org / chris-lamb.co.uk
   `-
I: using fakeroot in build.
I: pbuilder: network access will be disabled during build
I: Current time: Sat Sep  5 11:09:49 GMT+12 2015
I: pbuilder-time-stamp: 1441494589
I: Building the build Environment
I: extracting base tarball [/var/cache/pbuilder/unstable-reproducible-base.tgz]
I: creating local configuration
I: copying local configuration
I: mounting /proc filesystem
I: mounting /run/shm filesystem
I: mounting /dev/pts filesystem
I: Mounting /dev/shm
I: Mounting /sys
I: policy-rc.d already exists
I: Installing the build-deps
 -> Attempting to satisfy build-dependencies
 -> Creating pbuilder-satisfydepends-dummy package
Package: pbuilder-satisfydepends-dummy
Version: 0.invalid.0
Architecture: amd64
Maintainer: Debian Pbuilder Team 

Bug#808021: python-tasklib: FTBFS: TaskWarriorException: Invalid JSON: [

[Chris Lamb]

Source: python-tasklib
Version: 0.5.0-2
Severity: serious
Justification: fails to build from source
User: reproducible-bui...@lists.alioth.debian.org
Usertags: ftbfs
X-Debbugs-Cc: reproducible-bui...@lists.alioth.debian.org

Dear Maintainer,

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

  [..]

  
  ==
  ERROR: test_removing_annotation_by_description (tasklib.tests.AnnotationTest)
  --
  Traceback (most recent call last):
File 
"/home/lamby/temp/cdt.20151215105529.I9Zdp3NADZ/python-tasklib-0.5.0/tasklib/tests.py",
 line 70, in test_removing_annotation_by_description
  task = self.tw.tasks.get()
File 
"/home/lamby/temp/cdt.20151215105529.I9Zdp3NADZ/python-tasklib-0.5.0/tasklib/task.py",
 line 275, in get
  num = len(clone)
File 
"/home/lamby/temp/cdt.20151215105529.I9Zdp3NADZ/python-tasklib-0.5.0/tasklib/task.py",
 line 207, in __len__
  self._result_cache = list(self)
File 
"/home/lamby/temp/cdt.20151215105529.I9Zdp3NADZ/python-tasklib-0.5.0/tasklib/task.py",
 line 212, in __iter__
  self._result_cache = self._execute()
File 
"/home/lamby/temp/cdt.20151215105529.I9Zdp3NADZ/python-tasklib-0.5.0/tasklib/task.py",
 line 244, in _execute
  return self.warrior.filter_tasks(self.filter_obj)
File 
"/home/lamby/temp/cdt.20151215105529.I9Zdp3NADZ/python-tasklib-0.5.0/tasklib/task.py",
 line 330, in filter_tasks
  raise TaskWarriorException('Invalid JSON: %s' % data)
  TaskWarriorException: Invalid JSON: [
  
  ==
  ERROR: test_removing_annotation_by_obj (tasklib.tests.AnnotationTest)
  --
  Traceback (most recent call last):
File 
"/home/lamby/temp/cdt.20151215105529.I9Zdp3NADZ/python-tasklib-0.5.0/tasklib/tests.py",
 line 76, in test_removing_annotation_by_obj
  task = self.tw.tasks.get()
File 
"/home/lamby/temp/cdt.20151215105529.I9Zdp3NADZ/python-tasklib-0.5.0/tasklib/task.py",
 line 275, in get
  num = len(clone)
File 
"/home/lamby/temp/cdt.20151215105529.I9Zdp3NADZ/python-tasklib-0.5.0/tasklib/task.py",
 line 207, in __len__
  self._result_cache = list(self)
File 
"/home/lamby/temp/cdt.20151215105529.I9Zdp3NADZ/python-tasklib-0.5.0/tasklib/task.py",
 line 212, in __iter__
  self._result_cache = self._execute()
File 
"/home/lamby/temp/cdt.20151215105529.I9Zdp3NADZ/python-tasklib-0.5.0/tasklib/task.py",
 line 244, in _execute
  return self.warrior.filter_tasks(self.filter_obj)
File 
"/home/lamby/temp/cdt.20151215105529.I9Zdp3NADZ/python-tasklib-0.5.0/tasklib/task.py",
 line 330, in filter_tasks
  raise TaskWarriorException('Invalid JSON: %s' % data)
  TaskWarriorException: Invalid JSON: [
  
  ==
  ERROR: test_all_empty (tasklib.tests.TaskFilterTest)
  --
  Traceback (most recent call last):
File 
"/home/lamby/temp/cdt.20151215105529.I9Zdp3NADZ/python-tasklib-0.5.0/tasklib/tests.py",
 line 23, in test_all_empty
  self.assertEqual(len(self.tw.tasks.all()), 0)
File 
"/home/lamby/temp/cdt.20151215105529.I9Zdp3NADZ/python-tasklib-0.5.0/tasklib/task.py",
 line 207, in __len__
  self._result_cache = list(self)
File 
"/home/lamby/temp/cdt.20151215105529.I9Zdp3NADZ/python-tasklib-0.5.0/tasklib/task.py",
 line 212, in __iter__
  self._result_cache = self._execute()
File 
"/home/lamby/temp/cdt.20151215105529.I9Zdp3NADZ/python-tasklib-0.5.0/tasklib/task.py",
 line 244, in _execute
  return self.warrior.filter_tasks(self.filter_obj)
File 
"/home/lamby/temp/cdt.20151215105529.I9Zdp3NADZ/python-tasklib-0.5.0/tasklib/task.py",
 line 330, in filter_tasks
  raise TaskWarriorException('Invalid JSON: %s' % data)
  TaskWarriorException: Invalid JSON: [
  
  ==
  ERROR: test_all_non_empty (tasklib.tests.TaskFilterTest)
  --
  Traceback (most recent call last):
File 
"/home/lamby/temp/cdt.20151215105529.I9Zdp3NADZ/python-tasklib-0.5.0/tasklib/tests.py",
 line 27, in test_all_non_empty
  self.assertEqual(len(self.tw.tasks.all()), 1)
File 
"/home/lamby/temp/cdt.20151215105529.I9Zdp3NADZ/python-tasklib-0.5.0/tasklib/task.py",
 line 207, in __len__
  self._result_cache = list(self)
File 
"/home/lamby/temp/cdt.20151215105529.I9Zdp3NADZ/python-tasklib-0.5.0/tasklib/task.py",
 line 212, in __iter__
  self._result_cache = self._execute()
File 
"/home/lamby/temp/cdt.20151215105529.I9Zdp3NADZ/python-tasklib-0.5.0/tasklib/task.py",
 line 244, in _execute
  return self.warrior.filter_tasks(self.filter_obj)
File 

Bug#808020: libcommons-cli-java: FTBFS: Error resolving version for plugin 'org.apache.maven.plugins:maven-scm-publish-plugin' from the repositories

[Chris Lamb]

Source: libcommons-cli-java
Version: 1.3.1-2
Severity: serious
Justification: fails to build from source
User: reproducible-bui...@lists.alioth.debian.org
Usertags: ftbfs
X-Debbugs-Cc: reproducible-bui...@lists.alioth.debian.org

Dear Maintainer,

libcommons-cli-java fails to build from source in unstable/amd64:

  [..]
  cd . && /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
  -Dclassworlds.conf=/etc/maven/m2-debian.conf -Dmaven.home=/usr/share/maven 
-Dmaven.multiModuleProjectDirectory=/home/lamby/temp/cdt.20151215105522.Ade30ILohQ/libcommons-cli-java-1.3.1
 org.codehaus.plexus.classworlds.launcher.Launcher 
-s/etc/maven/settings-debian.xml 
-Dmaven.repo.local=/home/lamby/temp/cdt.20151215105522.Ade30ILohQ/libcommons-cli-java-1.3.1/debian/maven-repo
  package -DskipTests
  [INFO] Scanning for projects...
  [INFO]
 
  [INFO] 

  [INFO] Building Apache Commons CLI 1.3.1
  [INFO] 

  [INFO] 

  [INFO] BUILD FAILURE
  [INFO] 

  [INFO] Total time: 0.152 s
  [INFO] Finished at: 2015-12-15T10:58:19+00:00
  [INFO] Final Memory: 6M/236M
  [INFO] 

  [ERROR] Error resolving version for plugin 
'org.apache.maven.plugins:maven-scm-publish-plugin' from the repositories 
[local 
(/home/lamby/temp/cdt.20151215105522.Ade30ILohQ/libcommons-cli-java-1.3.1/debian/maven-repo),
 central (https://repo.maven.apache.org/maven2)]: Plugin not found in any 
plugin repository -> [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/PluginVersionResolutionException
  /usr/share/cdbs/1/class/maven.mk:92: recipe for target 'mvn-build' failed
  make: *** [mvn-build] Error 1

  [..]

The full build log is attached.


Regards,

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


libcommons-cli-java.1.3.1-2.unstable.amd64.log.txt.gz
Description: Binary data

Bug#808016: bisonc++: FTBFS: [icmake/readlog, line 5] Error: conflicting operand types for fgets

[Chris Lamb]

Source: bisonc++
Version: 4.11.00-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,

bisonc++ fails to build from source in unstable/amd64:

  [..]

  # Add here commands to clean up after the build process.
  ./build clean
  [icmake/md, line 15] Warning: `sizeof' is deprecated. Use `listlen'
  
  [icmake/writelog, line 8] Warning: `sizeof' is deprecated. Use `listlen'
  
  [icmake/logdirs, line 10] Warning: `sizeof' is deprecated. Use `listlen'
  
  [icmake/logfiles, line 9] Warning: `sizeof' is deprecated. Use `listlen'
  
  [icmake/readlog, line 5] Error: conflicting operand types for fgets
  [icmake/readlog, line 5] Error: conflicting operand types for =
  [icmake/adddir, line 8] Warning: `sizeof' is deprecated. Use `listlen'
  
  [icmake/removedir, line 14] Warning: `sizeof' is deprecated. Use `listlen'
  
  [icmake/removedir, line 18] Warning: `sizeof' is deprecated. Use `listlen'
  
  [icmake/uninstall, line 18] Warning: `sizeof' is deprecated. Use `listlen'
  
  [icmake/uninstall, line 28] Warning: `sizeof' is deprecated. Use `listlen'
  
  
  2 error(s) detected
  debian/rules:52: recipe for target 'clean' failed
  make: *** [clean] Error 1

  [..]

The full build log is attached.


Regards,

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


bisonc++.4.11.00-1.unstable.amd64.log.txt.gz
Description: Binary data

Bug#808019: haskell-x509-util: FTBFS: src/Certificate.hs:92:52: Couldn't match expected type `RSA.PublicKey' with actual type `cryptonite-0.6:Crypto.PubKey.RSA.Types.PublicKey'

[Chris Lamb]

Source: haskell-x509-util
Version: 1.5.0-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,

haskell-x509-util fails to build from source in unstable/amd64:

  [..]

  In the first argument of `(*)', namely `RSA.public_size pubkey'
  
  src/Certificate.hs:92:52:
  Couldn't match expected type `RSA.PublicKey'
  with actual type 
`cryptonite-0.6:Crypto.PubKey.RSA.Types.PublicKey'
  NB: `RSA.PublicKey'
is defined in `Crypto.Types.PubKey.RSA'
in package `crypto-pubkey-types-0.4.3'
  `cryptonite-0.6:Crypto.PubKey.RSA.Types.PublicKey'
is defined in `Crypto.PubKey.RSA.Types' in package `cryptonite-0.6'
  In the first argument of `RSA.public_n', namely `pubkey'
  In the second argument of `printf', namely `(RSA.public_n pubkey)'
  
  src/Certificate.hs:93:52:
  Couldn't match expected type `RSA.PublicKey'
  with actual type 
`cryptonite-0.6:Crypto.PubKey.RSA.Types.PublicKey'
  NB: `RSA.PublicKey'
is defined in `Crypto.Types.PubKey.RSA'
in package `crypto-pubkey-types-0.4.3'
  `cryptonite-0.6:Crypto.PubKey.RSA.Types.PublicKey'
is defined in `Crypto.PubKey.RSA.Types' in package `cryptonite-0.6'
  In the first argument of `RSA.public_e', namely `pubkey'
  In the second argument of `printf', namely `(RSA.public_e pubkey)'
  
  src/Certificate.hs:95:44:
  Couldn't match expected type `DSA.PublicKey'
  with actual type `cryptonite-0.6:Crypto.PubKey.DSA.PublicKey'
  NB: `DSA.PublicKey'
is defined in `Crypto.Types.PubKey.DSA'
in package `crypto-pubkey-types-0.4.3'
  `cryptonite-0.6:Crypto.PubKey.DSA.PublicKey'
is defined in `Crypto.PubKey.DSA' in package `cryptonite-0.6'
  In the first argument of `DSA.public_params', namely `pubkey'
  In the expression: DSA.public_params pubkey
  
  src/Certificate.hs:97:52:
  Couldn't match expected type `DSA.PublicKey'
  with actual type `cryptonite-0.6:Crypto.PubKey.DSA.PublicKey'
  NB: `DSA.PublicKey'
is defined in `Crypto.Types.PubKey.DSA'
in package `crypto-pubkey-types-0.4.3'
  `cryptonite-0.6:Crypto.PubKey.DSA.PublicKey'
is defined in `Crypto.PubKey.DSA' in package `cryptonite-0.6'
  In the first argument of `DSA.public_y', namely `pubkey'
  In the second argument of `printf', namely `(DSA.public_y pubkey)'
  /usr/share/cdbs/1/class/hlibrary.mk:147: recipe for target 'build-ghc-stamp' 
failed
  make: *** [build-ghc-stamp] Error 1

  [..]

The full build log is attached.


Regards,

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


haskell-x509-util.1.5.0-4.unstable.amd64.log.txt.gz
Description: Binary data

Bug#808017: bustle: FTBFS: Bustle/Loader/OldSkool.hs:122:23: Ambiguous occurrence `<*>'

[Chris Lamb]

Source: bustle
Version: 0.4.8-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,

bustle fails to build from source in unstable/amd64:

  [..]

  Bustle/Loader/OldSkool.hs:122:23:
  Ambiguous occurrence `<*>'
  It could refer to either `Bustle.Loader.OldSkool.<*>',
   defined at Bustle/Loader/OldSkool.hs:41:1
or `Prelude.<*>',
   imported from `Prelude' at 
Bustle/Loader/OldSkool.hs:20:8-29
   (and originally defined in `GHC.Base')
  
  Bustle/Loader/OldSkool.hs:122:29:
  Ambiguous occurrence `<*'
  It could refer to either `Bustle.Loader.OldSkool.<*',
   defined at Bustle/Loader/OldSkool.hs:37:3
or `Prelude.<*',
   imported from `Prelude' at 
Bustle/Loader/OldSkool.hs:20:8-29
   (and originally defined in `GHC.Base')
  
  Bustle/Loader/OldSkool.hs:122:34:
  Ambiguous occurrence `<*>'
  It could refer to either `Bustle.Loader.OldSkool.<*>',
   defined at Bustle/Loader/OldSkool.hs:41:1
or `Prelude.<*>',
   imported from `Prelude' at 
Bustle/Loader/OldSkool.hs:20:8-29
   (and originally defined in `GHC.Base')
  
  Bustle/Loader/OldSkool.hs:144:37:
  Ambiguous occurrence `<*'
  It could refer to either `Bustle.Loader.OldSkool.<*',
   defined at Bustle/Loader/OldSkool.hs:37:3
or `Prelude.<*',
   imported from `Prelude' at 
Bustle/Loader/OldSkool.hs:20:8-29
   (and originally defined in `GHC.Base')
  
  Bustle/Loader/OldSkool.hs:145:21:
  Ambiguous occurrence `<*>'
  It could refer to either `Bustle.Loader.OldSkool.<*>',
   defined at Bustle/Loader/OldSkool.hs:41:1
or `Prelude.<*>',
   imported from `Prelude' at 
Bustle/Loader/OldSkool.hs:20:8-29
   (and originally defined in `GHC.Base')
  
  Bustle/Loader/OldSkool.hs:145:38:
  Ambiguous occurrence `<*'
  It could refer to either `Bustle.Loader.OldSkool.<*',
   defined at Bustle/Loader/OldSkool.hs:37:3
or `Prelude.<*',
   imported from `Prelude' at 
Bustle/Loader/OldSkool.hs:20:8-29
   (and originally defined in `GHC.Base')
  
  Bustle/Loader/OldSkool.hs:145:43:
  Ambiguous occurrence `<*>'
  It could refer to either `Bustle.Loader.OldSkool.<*>',
   defined at Bustle/Loader/OldSkool.hs:41:1
or `Prelude.<*>',
   imported from `Prelude' at 
Bustle/Loader/OldSkool.hs:20:8-29
   (and originally defined in `GHC.Base')
  
  Bustle/Loader/OldSkool.hs:145:60:
  Ambiguous occurrence `<*'
  It could refer to either `Bustle.Loader.OldSkool.<*',
   defined at Bustle/Loader/OldSkool.hs:37:3
or `Prelude.<*',
   imported from `Prelude' at 
Bustle/Loader/OldSkool.hs:20:8-29
   (and originally defined in `GHC.Base')
  
  Bustle/Loader/OldSkool.hs:145:65:
  Ambiguous occurrence `<*>'
  It could refer to either `Bustle.Loader.OldSkool.<*>',
   defined at Bustle/Loader/OldSkool.hs:41:1
or `Prelude.<*>',
   imported from `Prelude' at 
Bustle/Loader/OldSkool.hs:20:8-29
   (and originally defined in `GHC.Base')
  
  Bustle/Loader/OldSkool.hs:155:19:
  Ambiguous occurrence `<*'
  It could refer to either `Bustle.Loader.OldSkool.<*',
   defined at Bustle/Loader/OldSkool.hs:37:3
or `Prelude.<*',
   imported from `Prelude' at 
Bustle/Loader/OldSkool.hs:20:8-29
   (and originally defined in `GHC.Base')
  
  Bustle/Loader/OldSkool.hs:156:26:
  Ambiguous occurrence `<*'
  It could refer to either `Bustle.Loader.OldSkool.<*',
   defined at Bustle/Loader/OldSkool.hs:37:3
or `Prelude.<*',
   imported from `Prelude' at 
Bustle/Loader/OldSkool.hs:20:8-29
   (and originally defined in `GHC.Base')
  
  Bustle/Loader/OldSkool.hs:157:17:
  Ambiguous occurrence `<*'
  It could refer to either `Bustle.Loader.OldSkool.<*',
   

Bug#808015: acpid: FTBFS: libnetlink.c:497:54: error: comparison between signed and unsigned integer expressions

[Chris Lamb]

Source: acpid
Version: 1:2.0.25-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,

acpid fails to build from source in unstable/amd64:

  [..]

  gcc -DHAVE_CONFIG_H -I. -I..  -include ../config.h -D_FORTIFY_SOURCE=2 -Wall 
-Wmissing-declarations -Wmissing-prototypes -Wredundant-decls -Wshadow 
-Wstrict-prototypes -Wformat=2 -W -Wall -Werror -Wundef -Wshadow -D_GNU_SOURCE 
-g -O2 -fstack-protector-strong -Wformat -Werror=format-security 
-fno-strict-aliasing -c -o libnetlink.o libnetlink.c
  libnetlink.c: In function 'addattr_l':
  libnetlink.c:497:54: error: comparison between signed and unsigned integer 
expressions [-Werror=sign-compare]
if ((int)NLMSG_ALIGN(n->nlmsg_len) + RTA_ALIGN(len) > maxlen) {
^
  libnetlink.c: In function 'rta_addattr32':
  libnetlink.c:527:36: error: comparison between signed and unsigned integer 
expressions [-Werror=sign-compare]
if (RTA_ALIGN(rta->rta_len) + len > maxlen) {
  ^
  libnetlink.c: In function 'rta_addattr_l':
  libnetlink.c:545:47: error: comparison between signed and unsigned integer 
expressions [-Werror=sign-compare]
if (RTA_ALIGN(rta->rta_len) + RTA_ALIGN(len) > maxlen) {
 ^
  cc1: all warnings being treated as errors
  Makefile:389: recipe for target 'libnetlink.o' failed
  make[3]: *** [libnetlink.o] Error 1
  make[3]: Leaving directory 
'/home/lamby/temp/cdt.20151215105238.YtstkitUES/acpid-2.0.25/kacpimon'
  Makefile:635: recipe for target 'all-recursive' failed
  make[2]: *** [all-recursive] Error 1
  make[2]: Leaving directory 
'/home/lamby/temp/cdt.20151215105238.YtstkitUES/acpid-2.0.25'
  Makefile:384: recipe for target 'all' failed
  make[1]: *** [all] Error 2
  make[1]: Leaving directory 
'/home/lamby/temp/cdt.20151215105238.YtstkitUES/acpid-2.0.25'
  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
   `-


acpid.1:2.0.25-1.unstable.amd64.log.txt.gz
Description: Binary data

Bug#808014: maven2: FTBFS: 'org.apache.maven.plugins:maven-resources-plugin' not found in repository

[Chris Lamb]

Source: maven2
Version: 2.2.1-28
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,

maven2 fails to build from source in unstable/amd64:

  [..]

  maven-compile:
   [java] + Error stacktraces are turned on.
   [java] [INFO] 
   [java] NOTE: Maven is executing in offline mode. Any artifacts not 
already in your local
   [java] repository will be inaccessible.
   [java] 
   [java] [INFO] Scanning for projects...
   [java] [INFO] Reactor build order: 
   [java] [INFO]   Maven
   [java] [INFO]   Maven Distribution
   [java] [INFO] 

   [java] [INFO] Building Maven
   [java] [INFO]task-segment: [clean, install]
   [java] [INFO] 

   [java] [INFO] [clean:clean {execution: default-clean}]
   [java] [INFO] [install:install {execution: default-install}]
   [java] [INFO] Installing 
/home/lamby/temp/cdt.20151215105225.LtFu4m9JNM/maven2-2.2.1/pom.xml to 
/home/lamby/temp/cdt.20151215105225.LtFu4m9JNM/maven2-2.2.1/debian/tmp/maven-repo/org/apache/maven/maven/debian/maven-debian.pom
   [java] [INFO] 

   [java] [INFO] Building Maven Distribution
   [java] [INFO]task-segment: [clean, install]
   [java] [INFO] 

   [java] [INFO] [clean:clean {execution: default-clean}]
   [java] [INFO] 

   [java] [ERROR] BUILD ERROR
   [java] [INFO] 

   [java] [INFO] Error building POM (may not be this project's POM).
   [java] 
   [java] 
   [java] Project ID: org.apache.maven.plugins:maven-resources-plugin
   [java] 
   [java] Reason: POM 'org.apache.maven.plugins:maven-resources-plugin' not 
found in repository: System is offline.
   [java] 
   [java]   org.apache.maven.plugins:maven-resources-plugin:pom:2.3
   [java] 
   [java] 
   [java]  for project org.apache.maven.plugins:maven-resources-plugin
   [java] 
   [java] 
   [java] [INFO] 

   [java] [INFO] Trace
   [java] org.apache.maven.lifecycle.LifecycleExecutionException: Unable to 
build project for plugin 'org.apache.maven.plugins:maven-resources-plugin': POM 
'org.apache.maven.plugins:maven-resources-plugin' not found in repository: 
System is offline.
   [java] 
   [java]   org.apache.maven.plugins:maven-resources-plugin:pom:2.3
   [java] 
   [java] 
   [java]  for project org.apache.maven.plugins:maven-resources-plugin
   [java]   at 
org.apache.maven.lifecycle.DefaultLifecycleExecutor.verifyPlugin(DefaultLifecycleExecutor.java:1557)
   [java]   at 
org.apache.maven.lifecycle.DefaultLifecycleExecutor.getMojoDescriptor(DefaultLifecycleExecutor.java:1851)
   [java]   at 
org.apache.maven.lifecycle.DefaultLifecycleExecutor.bindLifecycleForPackaging(DefaultLifecycleExecutor.java:1311)
   [java]   at 
org.apache.maven.lifecycle.DefaultLifecycleExecutor.constructLifecycleMappings(DefaultLifecycleExecutor.java:1275)
   [java]   at 
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:534)
   [java]   at 
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:387)
   [java]   at 
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:348)
   [java]   at 
org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:180)
   [java]   at 
org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:328)
   [java]   at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:138)
   [java]   at org.apache.maven.cli.MavenCli.main(MavenCli.java:362)
   [java]   at 
org.apache.maven.cli.compat.CompatibleMain.main(CompatibleMain.java:60)
   [java]   at 
org.apache.maven.cli.compat.CompatibleMain.main(CompatibleMain.java:37)
   [java] Caused by: org.apache.maven.plugin.InvalidPluginException: Unable 
to build project for plugin 'org.apache.maven.plugins:maven-resources-plugin': 
POM 'org.apache.maven.plugins:maven-resources-plugin' not found in repository: 
System is offline.
   [java] 
   [java]   org.apache.maven.plugins:maven-resources-plugin:pom:2.3
   [java] 
   [java] 
   [java]  for project org.apache.maven.plugins:maven-resources-plugin
   [java]   at 

Processed: segmentation fault on any code compiled by tcc with libc6 2.21-4

[Debian Bug Tracking System]

Processing control commands:

> retitle -1 segmentation fault on any code compiled by tcc with libc6 2.21-4
Bug #808008 [tcc] tcc: segmentation fault on any code compiled by tcc
Changed Bug title to 'segmentation fault on any code compiled by tcc with libc6 
2.21-4' from 'tcc: segmentation fault on any code compiled by tcc'

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

Bug#808008: segmentation fault on any code compiled by tcc with libc6 2.21-4

[Vincent Lefevre]

Control: retitle -1 segmentation fault on any code compiled by tcc with libc6 
2.21-4

Cc to the glibc maintainers because the cause of the bug is due to
some change in glibc.

On 2015-12-15 09:35:04 +0100, Vincent Lefevre wrote:
> Code compiled by tcc segfaults:
> 
> ypig% cat conftest.c 
> int main (void)
> { return 0; }
> ypig% tcc conftest.c -o conftest
> ypig% ./conftest 
> zsh: segmentation fault (core dumped)  ./conftest

The cause is libc6 2.21. I get this problem with libc6 2.21-4,
but on another machine, after reverting to libc6 2.19-22, this
problem no longer occurs. So, I wonder whether this is a tcc
bug or a glibc one.

In the "objdump -S" output of conftest, I notice the following
difference:

libc6 2.19:

00400430 <_init>:
  400430:   48 83 ec 08 sub$0x8,%rsp
  400434:   48 8b 05 4d 01 20 00mov0x20014d(%rip),%rax# 
600588 <_init+0x200158>
[...]

libc6 2.21:

004003f0 <_init>:
  4003f0:   48 83 ec 08 sub$0x8,%rsp
  4003f4:   48 8b 05 00 00 00 00mov0x0(%rip),%rax# 4003fb 
<_init+0xb>

The 0x20014d(%rip) has changed to 0x0(%rip).

-- 
Vincent Lefèvre  - Web: 
100% accessible validated (X)HTML - Blog: 
Work: CR INRIA - computer arithmetic / AriC project (LIP, ENS-Lyon)

Bug#808020: marked as done (libcommons-cli-java: FTBFS: Error resolving version for plugin 'org.apache.maven.plugins:maven-scm-publish-plugin' from the repositories)

[Debian Bug Tracking System]

Your message dated Tue, 15 Dec 2015 12:22:47 +
with message-id 
and subject line Bug#808020: fixed in libcommons-cli-java 1.3.1-3
has caused the Debian Bug report #808020,
regarding libcommons-cli-java: FTBFS: Error resolving version for plugin 
'org.apache.maven.plugins:maven-scm-publish-plugin' from the repositories
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.)


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

Dear Maintainer,

libcommons-cli-java fails to build from source in unstable/amd64:

  [..]
  cd . && /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
  -Dclassworlds.conf=/etc/maven/m2-debian.conf -Dmaven.home=/usr/share/maven 
-Dmaven.multiModuleProjectDirectory=/home/lamby/temp/cdt.20151215105522.Ade30ILohQ/libcommons-cli-java-1.3.1
 org.codehaus.plexus.classworlds.launcher.Launcher 
-s/etc/maven/settings-debian.xml 
-Dmaven.repo.local=/home/lamby/temp/cdt.20151215105522.Ade30ILohQ/libcommons-cli-java-1.3.1/debian/maven-repo
  package -DskipTests
  [INFO] Scanning for projects...
  [INFO]
 
  [INFO] 

  [INFO] Building Apache Commons CLI 1.3.1
  [INFO] 

  [INFO] 

  [INFO] BUILD FAILURE
  [INFO] 

  [INFO] Total time: 0.152 s
  [INFO] Finished at: 2015-12-15T10:58:19+00:00
  [INFO] Final Memory: 6M/236M
  [INFO] 

  [ERROR] Error resolving version for plugin 
'org.apache.maven.plugins:maven-scm-publish-plugin' from the repositories 
[local 
(/home/lamby/temp/cdt.20151215105522.Ade30ILohQ/libcommons-cli-java-1.3.1/debian/maven-repo),
 central (https://repo.maven.apache.org/maven2)]: Plugin not found in any 
plugin repository -> [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/PluginVersionResolutionException
  /usr/share/cdbs/1/class/maven.mk:92: recipe for target 'mvn-build' failed
  make: *** [mvn-build] Error 1

  [..]

The full build log is attached.


Regards,

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


libcommons-cli-java.1.3.1-2.unstable.amd64.log.txt.gz
Description: Binary data
--- End Message ---
--- Begin Message ---
Source: libcommons-cli-java
Source-Version: 1.3.1-3

We believe that the bug you reported is fixed in the latest version of
libcommons-cli-java, 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.
Emmanuel Bourg  (supplier of updated libcommons-cli-java 
package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Tue, 15 Dec 2015 12:50:47 +0100
Source: libcommons-cli-java
Binary: libcommons-cli-java
Architecture: source all
Version: 1.3.1-3
Distribution: unstable
Urgency: medium
Maintainer: Debian Java Maintainers 

Changed-By: Emmanuel Bourg 
Description:
 libcommons-cli-java - Command line arguments and options parsing library
Closes: 800148 808020
Changes:
 libcommons-cli-java (1.3.1-3) unstable; urgency=medium
 .
  

Bug#786145: marked as done (openshot: deprecation of python-support)

[Debian Bug Tracking System]

Your message dated Tue, 15 Dec 2015 11:24:58 +
with message-id 
and subject line Bug#786145: fixed in openshot 1.4.3-1.2
has caused the Debian Bug report #786145,
regarding openshot: 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.)


-- 
786145: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=786145
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: openshot
Version: 1.4.3-1.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: openshot
Source-Version: 1.4.3-1.2

We believe that the bug you reported is fixed in the latest version of
openshot, 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.
Mattia Rizzolo  (supplier of updated openshot 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, 14 Dec 2015 00:04:24 +
Source: openshot
Binary: openshot openshot-doc
Architecture: source
Version: 1.4.3-1.2
Distribution: unstable
Urgency: medium
Maintainer: Jonathan Thomas 
Changed-By: Mattia Rizzolo 
Description:
 openshot   - Create and edit videos and movies
 openshot-doc - Help manual for OpenShot Video Editor
Closes: 685999 786145
Changes:
 openshot (1.4.3-1.2) unstable; urgency=medium
 .
   * Non-maintainer upload.
   * debian/control: let openshot-doc recommend yelp.  Closes: #685999
   * Build with dh-python instead of python-support.  Closes: #786145
   * Improve debian/watch to have it to match something.  Thanks bartm!
   * debian/copyright:
 + reflow, separeting License: fields from the the files stanzas.
 + remove now unused openshot/windows/SimpleGladeApp.py stanza.
Checksums-Sha1:
 fec216e7b5046e48b88aa8a978c4b7547b9b1656 1910 openshot_1.4.3-1.2.dsc
 85a7b1384665e641dcf179cc519e21a12244c190 4204 openshot_1.4.3-1.2.debian.tar.xz
Checksums-Sha256:
 298b8e8e55fb4fa1d004279b0231b60b7de2b73bebe52790cf24307953bca274 1910 
openshot_1.4.3-1.2.dsc
 4dae78fcd86e45c86c6733f3a1a68b31528c10cabc3c2742b7e27e6320aa1a8d 4204 
openshot_1.4.3-1.2.debian.tar.xz
Files:
 072172a8e539d7e642624bf749e2fc45 1910 video optional openshot_1.4.3-1.2.dsc
 8fa6f392976fe951924434566af3cfbd 4204 video optional 
openshot_1.4.3-1.2.debian.tar.xz

-BEGIN PGP SIGNATURE-
Version: GnuPG v1

iQIcBAEBCAAGBQJWb/IoAAoJEEsEP825REVAG90QAJEE1YP1S9b0Foeb1f2bR7Bv
ET7UBoh+yLnBtFh71fB+Fxy0RPbRnw/V53neKqccbHcRsSX39tSLCT50s4tucaYV
tvkWFpUQ76GWGAgwTz/pQf/7Rz80whkITIwFTFunEklUlqumkfo1G9B1rNQ6lBme
GaMoBqioLzT7zcWliNApNJ1RwD3MO0jw647v9Tna5H9KQr0c/lpFUa+kxmLKKNGh
HQckM4Zs7WJbd8JfC3h3YKX4V1QCnSjgapajQkoyaw5IbFVsBBs6rmojfRdFXKJj
HnNjHlFsyWqh/3zpdE1YkDXwcnlJvZPWc94LsLCNKQ36Ciqk6xG0q8dwbMKpR2EY
lr3llOepwOIFmkU4qbqKJWmvTdi/ymUiZUb7gtB8Gg6ELAH7pJISA1MXL3nuX9ux
778sl7pWVkSnaXN1UfHyzy3/KGBuXkY/BNUlkBAVAhxdAv0NjzT/D2Vkpt92v3VO

Processed: this is clearly non pending

[Debian Bug Tracking System]

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

> tag 785991 - pending
Bug #785991 [src:dipy] dipy: deprecation of python-support
Removed tag(s) pending.
> --
Stopping processing here.

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

Bug#786227: marked as done (python-django-rosetta: deprecation of python-support)

[Debian Bug Tracking System]

Your message dated Tue, 15 Dec 2015 12:23:53 +
with message-id 
and subject line Bug#786227: fixed in python-django-rosetta 0.7.2-1.1
has caused the Debian Bug report #786227,
regarding python-django-rosetta: 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.)


-- 
786227: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=786227
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: python-django-rosetta
Version: 0.7.2-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-django-rosetta
Source-Version: 0.7.2-1.1

We believe that the bug you reported is fixed in the latest version of
python-django-rosetta, 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.
Mattia Rizzolo  (supplier of updated python-django-rosetta 
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: Tue, 15 Dec 2015 11:37:46 +
Source: python-django-rosetta
Binary: python-django-rosetta
Architecture: source
Version: 0.7.2-1.1
Distribution: unstable
Urgency: medium
Maintainer: Debian Python Modules Team 

Changed-By: Mattia Rizzolo 
Description:
 python-django-rosetta - Eases the translation process of your Django projects
Closes: 786227
Changes:
 python-django-rosetta (0.7.2-1.1) unstable; urgency=medium
 .
   * Non-maintainer upload.
   * Build using dh-python instead of python-support.  Closes: #786227
   * Switch buildsystem to pybuild.
   * Rewrite debian/watch to use the pypi.debian.net redirector.
Checksums-Sha1:
 ed7659fb2de42b91991f276579c87770098af010 2157 
python-django-rosetta_0.7.2-1.1.dsc
 e03eac128fc94c482414e64662f32d57a5408535 3172 
python-django-rosetta_0.7.2-1.1.debian.tar.xz
Checksums-Sha256:
 74290a49f6ed0648283fc4f5aeed862bb9101b55f55a22b1103a0b2ee61ffe6e 2157 
python-django-rosetta_0.7.2-1.1.dsc
 e72780e1e537af41b18f5ec7abae46ce8c629e8ded1bfc03d8133b42c1181bed 3172 
python-django-rosetta_0.7.2-1.1.debian.tar.xz
Files:
 d0e839ec6f05ab599004f12a7764f6a5 2157 python optional 
python-django-rosetta_0.7.2-1.1.dsc
 b49d28a99a2ed9b44689dc0c056e 3172 python optional 
python-django-rosetta_0.7.2-1.1.debian.tar.xz

-BEGIN PGP SIGNATURE-
Version: GnuPG v1

iQIcBAEBCAAGBQJWb/xWAAoJEEsEP825REVAvZoQALhPBrKpl9+uMS08u07HSBDK
jXLXIv2NVu0t/N9EWSS8xnplwSl/5eu/TLq9z6ep+I3FqPKCqA/6CLY+mqfQjojl
BVEAupUYXBAMbpDTTaAEgRd8YlQhWPc0euF1G9ux4I9uQFpQc9SFM7NBlpqICvXz
GgPH79ngoz0iTmtSg4p8g9PExTcyClLF400oL+hnMBQVhAoU+WVhY293MLgsWhiE
y4DkE3PEDPXlut1bgkB8/a4cddCGpGC6LgA2MrPYppnku3EZYWlDgZUmXBQQFZfx
MePQhzC7mtV5wuqGVUcH2L8RXlx/kxOkSbYCpgWA6qg+9evHkAuSDoANHjCWqbFk
py4l9U3lpipggZf7GHYGCgN6XMIA5qUGZ5NLTMehWG9MUWG1sZV8oDHMY+/3o8Rh
0ll0MkFaUE/Ihp/CsaVAP7a8wJapB9WzK0yW7mzrFcGSvS+yyg4zSWyNbrMd9/CL

Bug#808011: missing license in debian/copyright

[Thorsten Alteholz]

Package: arrayfire
Version: 3.2.1+dfsg1-2
Severity: serious
User: alteh...@debian.org
Usertags: ftp
X-Debbugs-CC: ftpmas...@ftp-master.debian.org
thanks

Dear Maintainer,

please add the missing licenses of:
 arrayfire-3.2.1+dfsg1/test/gtest/scripts/upload.py
to your debian/copyright.

Thanks!
  Thorsten

Bug#808017: bustle: FTBFS: Bustle/Loader/OldSkool.hs:122:23: Ambiguous occurrence `<*>'

[Joachim Breitner]

Hi,

likely easily fixed by upgrading to a more recent version of bustle.

Greetings,
Joachim
-- 
Joachim "nomeata" Breitner
Debian Developer
  nome...@debian.org | ICQ# 74513189 | GPG-Keyid: F0FBF51F
  JID: nome...@joachim-breitner.de | http://people.debian.org/~nomeata



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

Bug#791868: closed by Milan Kupcevic <mi...@physics.harvard.edu> (Bug#741642: fixed in mkvmlinuz 37+deb8u1)

[Holger Levsen]

Hi Milan,

thanks for fixing this bug in stable! It's great to see this bug seeing fixed, 
even despite I finally gave the hardware away a very few weeks ago… :)


cheers,
Holger


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

Bug#808008: segmentation fault on any code compiled by tcc with libc6 2.21-4

[Vincent Lefevre]

BTW, that's also FTBFS: due to this bug, the tests fail:

 hello-exe 
../tcc -B.. -I.. -I.. -I../include ../examples/ex1.c -o hello || (../tcc -vv; 
exit 1) && ./hello
Segmentation fault (core dumped)
Makefile:82: recipe for target 'hello-exe' failed
make[2]: *** [hello-exe] Error 139

-- 
Vincent Lefèvre  - Web: 
100% accessible validated (X)HTML - Blog: 
Work: CR INRIA - computer arithmetic / AriC project (LIP, ENS-Lyon)

Bug#808022: gs-collections: FTBFS: Error resolving version for plugin 'org.apache.felix:maven-bundle-plugin' from the repositories

[Chris Lamb]

Source: gs-collections
Version: 5.1.0-1
Severity: serious
Justification: fails to build from source
User: reproducible-bui...@lists.alioth.debian.org
Usertags: ftbfs
X-Debbugs-Cc: reproducible-bui...@lists.alioth.debian.org

Dear Maintainer,

gs-collections fails to build from source in unstable/amd64:

  [..]

  [INFO] Compiling 8 source files to 
/home/lamby/temp/cdt.20151215105604.OhDc8OlapK/gs-collections-5.1.0/gs-collections-forkjoin/target/classes
  [INFO] 
/home/lamby/temp/cdt.20151215105604.OhDc8OlapK/gs-collections-5.1.0/gs-collections-forkjoin/src/main/java/com/gs/collections/impl/forkjoin/FJIterate.java:
 
/home/lamby/temp/cdt.20151215105604.OhDc8OlapK/gs-collections-5.1.0/gs-collections-forkjoin/src/main/java/com/gs/collections/impl/forkjoin/FJIterate.java
 uses unchecked or unsafe operations.
  [INFO] 
/home/lamby/temp/cdt.20151215105604.OhDc8OlapK/gs-collections-5.1.0/gs-collections-forkjoin/src/main/java/com/gs/collections/impl/forkjoin/FJIterate.java:
 Recompile with -Xlint:unchecked for details.
  [INFO] 
  [INFO] --- maven-resources-plugin:2.6:testResources (default-testResources) @ 
gs-collections-forkjoin ---
  [INFO] Using 'UTF-8' encoding to copy filtered resources.
  [INFO] skip non existing resourceDirectory 
/home/lamby/temp/cdt.20151215105604.OhDc8OlapK/gs-collections-5.1.0/gs-collections-forkjoin/src/test/resources
  [INFO] 
  [INFO] --- maven-compiler-plugin:3.2:testCompile (default-testCompile) @ 
gs-collections-forkjoin ---
  [INFO] Nothing to compile - all classes are up to date
  [INFO] 
  [INFO] --- maven-surefire-plugin:2.17:test (default-test) @ 
gs-collections-forkjoin ---
  [INFO] Tests are skipped.
  [INFO] 
  [INFO] <<< maven-bundle-plugin:2.5.4:bundle (default-bundle) < package @ 
gs-collections-forkjoin <<<
  [INFO] 
  [INFO] --- maven-bundle-plugin:2.5.4:bundle (default-bundle) @ 
gs-collections-forkjoin ---
  [INFO]
 
  [INFO] 

  [INFO] Building Goldman Sachs Collections Parent Project 5.1.0
  [INFO] 

  [INFO] 

  [INFO] Reactor Summary:
  [INFO] 
  [INFO] Goldman Sachs Collections Code Generator ... SUCCESS [  2.974 
s]
  [INFO] Goldman Sachs Collections Code Generator Maven Plugin SUCCESS [  1.238 
s]
  [INFO] Goldman Sachs Collections API .. SUCCESS [ 10.861 
s]
  [INFO] Goldman Sachs Collections Main Library . SUCCESS [ 58.261 
s]
  [INFO] Goldman Sachs Collections Test Utilities ... SUCCESS [  0.771 
s]
  [INFO] Goldman Sachs Collections Fork Join Utilities .. SUCCESS [  0.399 
s]
  [INFO] Goldman Sachs Collections Parent Project ... FAILURE [  0.001 
s]
  [INFO] 

  [INFO] BUILD FAILURE
  [INFO] 

  [INFO] Total time: 01:16 min
  [INFO] Finished at: 2015-12-15T11:01:13+00:00
  [INFO] Final Memory: 53M/1804M
  [INFO] 

  [ERROR] Error resolving version for plugin 
'org.apache.felix:maven-bundle-plugin' from the repositories [local 
(/home/lamby/temp/cdt.20151215105604.OhDc8OlapK/gs-collections-5.1.0/debian/maven-repo),
 central (https://repo.maven.apache.org/maven2)]: Plugin not found in any 
plugin repository -> [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/PluginVersionResolutionException
  /usr/share/cdbs/1/class/maven.mk:92: recipe for target 'mvn-build' failed
  make: *** [mvn-build] Error 1

  [..]

The full build log is attached.


Regards,

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


gs-collections.5.1.0-1.unstable.amd64.log.txt.gz
Description: Binary data

Bug#808016: bisonc++: FTBFS: [icmake/readlog, line 5] Error: conflicting operand types for fgets

[Frank B. Brokken]

Dear Chris Lamb, you wrote:
> Source: bisonc++
> Version: 4.11.00-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,
> 
> bisonc++ fails to build from source in unstable/amd64:

Ha! I beat you here by 1/2 day :-) 

Yesterday I prepared a new release, among other adapting the scripts to icmake
8.00.04 and updated the Debian files accordingly. We're now at bisonc++
4.13.00, and the new package should be available RSN.

@Tony: could you add a Closed #808016 entry to Debian's changelog, please?



scripts and 
> 
>   [..]
> 
>   # Add here commands to clean up after the build process.
>   ./build clean
>   [icmake/md, line 15] Warning: `sizeof' is deprecated. Use `listlen'
>   ...
>   2 error(s) detected
>   debian/rules:52: recipe for target 'clean' failed
>   make: *** [clean] Error 1
> 
>   [..]

Cheers,

-- 
Frank B. Brokken
Center for Information Technology, University of Groningen
(+31) 50 363 9281 
Public PGP key: http://pgp.surfnet.nl
Key Fingerprint: DF32 13DE B156 7732 E65E  3B4D 7DB2 A8BE EAE4 D8AA

Bug#808081: bind9: CVE-2015-8000: Responses with a malformed class attribute can trigger an assertion failure in db.c

[Salvatore Bonaccorso]

Source: bind9
Version: 1:9.7.3.dfsg-1
Severity: grave
Tags: security upstream fixed-upstream

Hi,

the following vulnerability was published for bind9.

CVE-2015-8000[0]:
Responses with a malformed class attribute can trigger an assertion failure in 
db.c

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

For further information see:

[0] https://security-tracker.debian.org/tracker/CVE-2015-8000
[1] https://kb.isc.org/article/AA-01317

Regards,
Salvatore

Bug#808060: should gnome-schedule be removed?

[Mattia Rizzolo]

Control: reassign -1 ftp.debian.org
Control: severity -1 normal
Control: retitle -1 RM: gnome-schedule -- ROM; unmaintained, dead upstream, RC 
buggy, depends on obsolete libs

On Tue, Dec 15, 2015 at 02:55:24PM -0500, Alejandro Ríos Peña wrote:
> Hi,
> 
> You are right, please remove it.  I am currently Missing in Action, I will
> resign to the debian project as my last duty

Thanks for being nice! ♥

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

Processed: Re: Bug#808060: should gnome-schedule be removed?

[Debian Bug Tracking System]

Processing control commands:

> reassign -1 ftp.debian.org
Bug #808060 [gnome-schedule] should gnome-schedule be removed?
Bug reassigned from package 'gnome-schedule' to 'ftp.debian.org'.
No longer marked as found in versions gnome-schedule/2.1.1-4.
Ignoring request to alter fixed versions of bug #808060 to the same values 
previously set
> severity -1 normal
Bug #808060 [ftp.debian.org] should gnome-schedule be removed?
Severity set to 'normal' from 'serious'
> retitle -1 RM: gnome-schedule -- ROM; unmaintained, dead upstream, RC buggy, 
> depends on obsolete libs
Bug #808060 [ftp.debian.org] should gnome-schedule be removed?
Changed Bug title to 'RM: gnome-schedule -- ROM; unmaintained, dead upstream, 
RC buggy, depends on obsolete libs' from 'should gnome-schedule be removed?'

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

Processed: Re: spellcast-doc: Please migrate a supported debhelper compat level

[Debian Bug Tracking System]

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

> tags 800307 patch
Bug #800307 [src:spellcast-doc] spellcast-doc: Please migrate a supported 
debhelper compat level
Added tag(s) patch.
> tags 800307 pending
Bug #800307 [src:spellcast-doc] spellcast-doc: Please migrate a supported 
debhelper compat level
Added tag(s) pending.
> thanks
Stopping processing here.

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

Bug#800307: spellcast-doc: Please migrate a supported debhelper compat level

[Eriberto Mota]

tags 800307 patch
tags 800307 pending
thanks


Hi,

I uploaded a NMU to 10-day/delay queue. Feel free to cancel this
upload if needed.

The debian/changelog is:

 spellcast-doc (1.5+nmu1) unstable; urgency=medium
 .
   * Non-maintainer upload.
   * Update DH level to 9 to avoid a FTBFS. (Closes: #800307)
   * debian/compat: created.
   * debian/control:
   - Added the Depends field with ${misc:Depends} variable
 to provide the right install dependencies.
   - Bumped Standards-Version to 3.9.6.
   - Changed from Build-Depends-Indep to Build-Depends.

I attached a debdiff.

Regards,

Eriberto


spellcast-doc.debdiff
Description: Binary data

Bug#786179: marked as done (python-uniconvertor: deprecation of python-support)

[Debian Bug Tracking System]

Your message dated Tue, 15 Dec 2015 22:10:46 +
with message-id 
and subject line Bug#786179: fixed in python-uniconvertor 1.1.5-1
has caused the Debian Bug report #786179,
regarding python-uniconvertor: 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.)


-- 
786179: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=786179
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: python-uniconvertor
Version: 1.1.4-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-uniconvertor
Source-Version: 1.1.5-1

We believe that the bug you reported is fixed in the latest version of
python-uniconvertor, 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.
Mattia Rizzolo  (supplier of updated python-uniconvertor 
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: Tue, 15 Dec 2015 19:59:18 +
Source: python-uniconvertor
Binary: python-uniconvertor python-uniconvertor-dbg
Architecture: source
Version: 1.1.5-1
Distribution: unstable
Urgency: medium
Maintainer: Debian QA Group 
Changed-By: Mattia Rizzolo 
Description:
 python-uniconvertor - Universal vector graphics translator
 python-uniconvertor-dbg - Universal vector graphics translator (debug 
extension)
Closes: 592840 699301 786179
Changes:
 python-uniconvertor (1.1.5-1) unstable; urgency=medium
 .
   * QA upload.
   * Orphan the package.  See #644559
   * Update debian watch with the one from sepwatch.  Thanks bartm!
   * Use source format 3.0 (quilt).
 + Drop now useless README.source.
   * New upstream release.  Closes: #592840, LP: #637800
 + Remove non-free files.  Closes: #699301
   * Run wrap-and-sort
   * Bump Standards-Version to 3.9.6, no changes needed.
   * Use the dh sequencer in debian/rules.
   * Bump debhelper compat version to 9.
   * Build using dh-python instead of python-support.  Closes: #786179
Checksums-Sha1:
 23844e9114cb139b10979f0f83ba9d78b00488fb 1976 python-uniconvertor_1.1.5-1.dsc
 51ec7c4487048c3357ed95cdb4ab3524018a2c9e 246998 
python-uniconvertor_1.1.5.orig.tar.gz
 d304669718542d7c0552a5a81549a80179213617 4880 
python-uniconvertor_1.1.5-1.debian.tar.xz
Checksums-Sha256:
 cfe8383ce8ddf59b1b4f2a76369fbf8b7fda728453253bf5e0e8aa4467820982 1976 
python-uniconvertor_1.1.5-1.dsc
 c3a9ecb70779911470e01c6b1950b07fc2fe1880777a1e70e44251323f4d5882 246998 
python-uniconvertor_1.1.5.orig.tar.gz
 13c714bdeef264038009aaf6d2dfc4e87c46fb0a695895a1747f9660a4133c9d 4880 
python-uniconvertor_1.1.5-1.debian.tar.xz
Files:
 047f0274f09a6864fb9fa1f9b331aab8 1976 python optional 
python-uniconvertor_1.1.5-1.dsc
 d1272315a58304ece2ff588834e23f72 246998 python optional 
python-uniconvertor_1.1.5.orig.tar.gz
 73b4ed488b26d128b8e48f933e7b2a3b 4880 python 

Bug#807318: marked as done (libmpich-dev: should add Depends: to match hard-wired gcc dependency in mpicxx.h)

[Debian Bug Tracking System]

Your message dated Tue, 15 Dec 2015 22:09:38 +
with message-id 
and subject line Bug#807318: fixed in mpich 3.2-1~exp1
has caused the Debian Bug report #807318,
regarding libmpich-dev: should add Depends: to match hard-wired gcc dependency 
in mpicxx.h
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.)


-- 
807318: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=807318
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: libmpich-dev
Version: 3.1-6
Severity: grave
Justification: renders package unusable

/usr/include/mpich/mpicxx.h has a hardwired dependency on the gcc used
to build mpich (gcc 5.2):

#ifdef __GNUC__ 
# if __GNUC__ >= 5 
#  if __GNUC_MINOR__ > 2 && 2 == 2 
#  error 'Please use the same version of GCC and g++ for compiling MPICH and 
user MPI programs'
#  endif
# endif 
#endif

But the current gcc (on s390x) is 5.3.  So an error is thrown when
building client programs (cf. Bug#803477), making mpich mostly
unusable on this architecture. 


libmpich-dev has a dependency on gcc.  But because the version in
mpicxx.h has been hardwired like this, I think that means libmpich-dev
should have a versioned Depends: gcc (<=4:5.2), Conflicts: gcc (>4:5.2)

In any case, mpich needs to be rebuilt, on s390x at least, to
update the gcc dependency in mpicxx.h.


-- System Information:
Debian Release: stretch/sid
  APT prefers unstable
  APT policy: (500, 'unstable'), (1, 'experimental')
Architecture: s390x
--- End Message ---
--- Begin Message ---
Source: mpich
Source-Version: 3.2-1~exp1

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

Debian distribution maintenance software
pp.
Anton Gladky  (supplier of updated mpich 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: Tue, 15 Dec 2015 22:15:03 +0100
Source: mpich
Binary: libmpich-dev libmpich12 mpich mpich-doc
Architecture: source
Version: 3.2-1~exp1
Distribution: experimental
Urgency: medium
Maintainer: Debian Science Maintainers 

Changed-By: Anton Gladky 
Description:
 libmpich-dev - Development files for MPICH
 libmpich12 - Shared libraries for MPICH
 mpich  - Implementation of the MPI Message Passing Interface standard
 mpich-doc  - Documentation for MPICH
Closes: 807318 807666
Changes:
 mpich (3.2-1~exp1) experimental; urgency=medium
 .
   [ Torquil Macdonald Sørensen ]
   * New upstream release. (Closes: #807318, #807666)
   * Set MPILIBNAME to keep old soname
   * Drop transitional packages for MPICH2
   * Drop libmpl*/libopa* since they are now only symlinks to files in libmpich*
   * Remove ARMCI section from debian/copyright since ARMCI is no longer in 
MPICH
   * Bump standards version to 3.9.6.0
   * Remove versioned mpich2-doc from mpich-doc Conflicts
   * Replace versioned libmpich2-dev Conflicts by Breaks and Replaces in package
 libmpich-dev
   * Remove versioned mpich2 from mpich Conflicts
   * Man page updates
   * Add libmpl1/libopa1 to Breaks/Replaces for libmpich12, since it replaces
 those
   * Include upstream manual page mpif77.1 and provide symlink for 
mpif90.mpich.1
   * Include hydra* manual pages
   * Add parkill manual page
 .
   [ Anton Gladky ]
   * Apply cme fix dpkg-control
   * Cosmetic changes
Checksums-Sha1:
 c4debc542681be40ed11ddb50ff8b456667ccada 2532 mpich_3.2-1~exp1.dsc
 5fae7df02f750b6966837b554f9985a9c574236f 11862150 mpich_3.2.orig.tar.gz
 ce65b4118e0b45ba59b9b7d16c574e10a68d51ea 43584 mpich_3.2-1~exp1.debian.tar.xz
Checksums-Sha256:
 175dc1fe1547a8d843e32f6b13457036f2198d43aca632e4acbf523e35f79d86 2532 
mpich_3.2-1~exp1.dsc
 0778679a6b693d7b7caff37ff9d2856dc2bfc51318bf8373859bfa74253da3dc 11862150 
mpich_3.2.orig.tar.gz
 ad3009d16a6a183eee5a4f6dcf3376d43f4509d6d4615070523ec5b59eaac296 43584 
mpich_3.2-1~exp1.debian.tar.xz
Files:
 bcb62387b45dce421b2436ab7bfde629 2532 devel extra mpich_3.2-1~exp1.dsc
 f414cfa77099cd1fa1a5ae4e22db508a 11862150 devel extra mpich_3.2.orig.tar.gz

Bug#699301: marked as done (python-uniconvertor: sRGB_Color_Space_Profile.icm is non-free)

[Debian Bug Tracking System]

Your message dated Tue, 15 Dec 2015 22:10:46 +
with message-id 
and subject line Bug#699301: fixed in python-uniconvertor 1.1.5-1
has caused the Debian Bug report #699301,
regarding python-uniconvertor: sRGB_Color_Space_Profile.icm is non-free
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.)


-- 
699301: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=699301
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: python-uniconvertor
Version: 1.1.4-1
Severity: serious
Justification: DFSG3: must allow derived works

Dear Maintainer,

The file src/share/icc/sRGB_Color_Space_Profile.icm is not licensed under the
same terms as the rest of this package -- it is a file from HP and is not
distributed under a free licence.

$ md5sum python-uniconvertor-1.1.4/src/share/icc/sRGB_Color_Space_Profile.icm 
"fop-1.1.dfsg/src/java/org/apache/fop/pdf/sRGB Color Space Profile.icm"
1d3fda2edb4a89ab60a23c5f7c7d81dd  
python-uniconvertor-1.1.4/src/share/icc/sRGB_Color_Space_Profile.icm
1d3fda2edb4a89ab60a23c5f7c7d81dd  fop-1.1.dfsg/src/java/org/apache/fop/pdf/sRGB 
Color Space Profile.icm

The fop package has a LICENSE file with it that helps understand where this
file came from:

--- 8< --
Obtained from: http://www.srgb.com/usingsrgb.html

The file "sRGB Color Space Profile.icm" is:
Copyright (c) 1998 Hewlett-Packard Company

To anyone who acknowledges that the file "sRGB Color Space Profile.icm" 
is provided "AS IS" WITH NO EXPRESS OR IMPLIED WARRANTY:
permission to use, copy and distribute this file for any purpose is hereby 
granted without fee, provided that the file is not changed including the HP 
copyright notice tag, and that the name of Hewlett-Packard Company not be 
used in advertising or publicity pertaining to distribution of the software 
without specific, written prior permission.  Hewlett-Packard Company makes 
no representations about the suitability of this software for any purpose.
--- 8< --

http://web.archive.org/web/20061117153845/http://www.srgb.com/usingsrgb.html

This licence does not permit distribution of derived works which makes it
unsuitable for Debian.

See also bug #657281.

cheers
Stuart
--- End Message ---
--- Begin Message ---
Source: python-uniconvertor
Source-Version: 1.1.5-1

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

Debian distribution maintenance software
pp.
Mattia Rizzolo  (supplier of updated python-uniconvertor 
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: Tue, 15 Dec 2015 19:59:18 +
Source: python-uniconvertor
Binary: python-uniconvertor python-uniconvertor-dbg
Architecture: source
Version: 1.1.5-1
Distribution: unstable
Urgency: medium
Maintainer: Debian QA Group 
Changed-By: Mattia Rizzolo 
Description:
 python-uniconvertor - Universal vector graphics translator
 python-uniconvertor-dbg - Universal vector graphics translator (debug 
extension)
Closes: 592840 699301 786179
Changes:
 python-uniconvertor (1.1.5-1) unstable; urgency=medium
 .
   * QA upload.
   * Orphan the package.  See #644559
   * Update debian watch with the one from sepwatch.  Thanks bartm!
   * Use source format 3.0 (quilt).
 + Drop now useless README.source.
   * New upstream release.  Closes: #592840, LP: #637800
 + Remove non-free files.  Closes: #699301
   * Run wrap-and-sort
   * Bump Standards-Version to 3.9.6, no changes needed.
   * Use the dh sequencer in debian/rules.
   * Bump debhelper compat version to 9.
   * Build using dh-python instead of python-support.  Closes: #786179
Checksums-Sha1:
 23844e9114cb139b10979f0f83ba9d78b00488fb 1976 python-uniconvertor_1.1.5-1.dsc
 51ec7c4487048c3357ed95cdb4ab3524018a2c9e 246998 
python-uniconvertor_1.1.5.orig.tar.gz
 d304669718542d7c0552a5a81549a80179213617 4880 
python-uniconvertor_1.1.5-1.debian.tar.xz
Checksums-Sha256:
 cfe8383ce8ddf59b1b4f2a76369fbf8b7fda728453253bf5e0e8aa4467820982 1976 

Bug#807666: marked as done (mpich: overly restrictive GCC check)

[Debian Bug Tracking System]

Your message dated Tue, 15 Dec 2015 22:09:38 +
with message-id 
and subject line Bug#807666: fixed in mpich 3.2-1~exp1
has caused the Debian Bug report #807666,
regarding mpich: overly restrictive GCC check
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.)


-- 
807666: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=807666
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: binnmu

Hello,

Compiling c++ programs against mpich currently fails in sid:

In file included from /usr/include/mpich/mpi.h:2175:0,
 from test.c:1:
/usr/include/mpich/mpicxx.h:22:4: error: #error 'Please use the same version of 
GCC and g++ for compiling MPICH and user MPI programs'
 #  error 'Please use the same version of GCC and g++ for compiling MPICH and 
user MPI programs'

Apparently mpich got built with 5.2, and sid currently has 5.3, thus the
failure.  Rebuilding mpich with current gcc 5.3 should be fixing it.

Samuel

nmu mpich_3.1-6 . ANY . unstable . -m "Rebuild against g++ 5.3"

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

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

-- 
Samuel
 Créer une hiérarchie supplementaire pour remedier à un problème (?) de
 dispersion est d'une logique digne des Shadocks.
 * BT in: Guide du Cabaliste Usenet - La Cabale vote oui (les Shadocks aussi) *
--- End Message ---
--- Begin Message ---
Source: mpich
Source-Version: 3.2-1~exp1

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

Debian distribution maintenance software
pp.
Anton Gladky  (supplier of updated mpich 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: Tue, 15 Dec 2015 22:15:03 +0100
Source: mpich
Binary: libmpich-dev libmpich12 mpich mpich-doc
Architecture: source
Version: 3.2-1~exp1
Distribution: experimental
Urgency: medium
Maintainer: Debian Science Maintainers 

Changed-By: Anton Gladky 
Description:
 libmpich-dev - Development files for MPICH
 libmpich12 - Shared libraries for MPICH
 mpich  - Implementation of the MPI Message Passing Interface standard
 mpich-doc  - Documentation for MPICH
Closes: 807318 807666
Changes:
 mpich (3.2-1~exp1) experimental; urgency=medium
 .
   [ Torquil Macdonald Sørensen ]
   * New upstream release. (Closes: #807318, #807666)
   * Set MPILIBNAME to keep old soname
   * Drop transitional packages for MPICH2
   * Drop libmpl*/libopa* since they are now only symlinks to files in libmpich*
   * Remove ARMCI section from debian/copyright since ARMCI is no longer in 
MPICH
   * Bump standards version to 3.9.6.0
   * Remove versioned mpich2-doc from mpich-doc Conflicts
   * Replace versioned libmpich2-dev Conflicts by Breaks and Replaces in package
 libmpich-dev
   * Remove versioned mpich2 from mpich Conflicts
   * Man page updates
   * Add libmpl1/libopa1 to Breaks/Replaces for libmpich12, since it replaces
 those
   * Include upstream manual page mpif77.1 and provide symlink for 
mpif90.mpich.1
   * Include hydra* manual pages
   * Add parkill manual page
 .
   [ Anton Gladky ]
   * Apply cme fix dpkg-control
   * Cosmetic changes
Checksums-Sha1:
 c4debc542681be40ed11ddb50ff8b456667ccada 2532 mpich_3.2-1~exp1.dsc
 5fae7df02f750b6966837b554f9985a9c574236f 11862150 mpich_3.2.orig.tar.gz
 ce65b4118e0b45ba59b9b7d16c574e10a68d51ea 43584 mpich_3.2-1~exp1.debian.tar.xz
Checksums-Sha256:
 175dc1fe1547a8d843e32f6b13457036f2198d43aca632e4acbf523e35f79d86 2532 

Bug#803291: prepare for giflib5

[Christian Welzel]

Am 28.10.2015 um 15:53 schrieb Matthias Klose:


Planning an update of giflib to the current version 5.1.1. Giflib
slightly changes it's API, requiring soureful changes.


I'll look into this, and fix some other issues with the package on
the way. Currently looking for some source for the swf.

--
 MfG, Christian Welzel

  GPG-Key: pub 4096R/5117E119 2011-09-19
  Fingerprint: 3688 337C 0D3E 3725 94EC  E401 8D52 CDE9 5117 E119

Processed: fixed 803927 in glibc/2.21-1

[Debian Bug Tracking System]

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

> fixed 803927 glibc/2.21-1
Bug #803927 {Done: Raphaël Hertzog } [src:glibc] glibc: 
multiple overflows in strxfrm()
Marked as fixed in versions glibc/2.21-1.
> thanks
Stopping processing here.

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

Bug#807571: ocserv: fails to install due to insserv rejecting the script header

[fishy]

OK, found out that it's because in /lib/systemd/system/ocserv.socket, we
have:

--->8---
[Unit]
Description=OpenConnect SSL VPN server Socket

[Socket]
ListenStream=443
ListenDatagram=443
BindIPv6Only=default
Accept=false
ReusePort=true

[Install]
WantedBy=sockets.target
---8<---

I'm not sure what's the correct way to do it, but:

1. Why does that file overrides port defined in /etc/ocserv/ocserv.conf?
2. Can we try to ask the user to choose a port during installation?
3. If 2 is not possible, maybe don't try to auto-start the service during
configuration (or fail silently)?

On Mon, Dec 14, 2015 at 7:37 PM fishy  wrote:

> A few more informations:
>
> I have port 443 occupied by nginx, so aptitude install or service ocserv
> start (after successful installation) will fail, but I have port 1443
> instead of 443 in my /etc/ocserv/ocserv.conf file.
>
> If I stop nginx before install/start ocserv, it will work, and will listen
> on 443 instead of 1443. ps shows the command was actually:
>
> $ ps ax | grep ocserv
>  7601 ?Ss 0:00 /usr/sbin/ocserv --foreground --pid-file
> /var/run/ocserv.pid --config /etc/ocserv/ocserv.conf
>  7602 ?S  0:00 /usr/sbin/ocserv --foreground --pid-file
> /var/run/ocserv.pid --config /etc/ocserv/ocserv.conf
>  7642 pts/0S+ 0:00 grep ocserv
>
> If I just run that command line manually, it will actually listen to 1443
> instead of 443 (which is expected).
>
> On Mon, Dec 14, 2015 at 7:18 PM Yuxuan Wang  wrote:
>
>> Package: ocserv
>> Version: 0.10.7-1
>> Followup-For: Bug #807571
>>
>> Dear Maintainer,
>>
>> /etc/init.d/ocserv from package ocserv always try to use port 443,
>> despite that
>> I have an /etc/ocserv/ocserv.conf file says otherwise
>>
>> Start it manually will work:
>>
>> /usr/sbin/ocserv --pid-file /var/run/ocserv.pid --config
>> /etc/ocserv/ocserv.conf
>>
>> But the init.d script doesn't. I failed to dig out why that init.d script
>> always
>> tries to use port 443.
>>
>> *** Reporter, please consider answering these questions, where
>> appropriate ***
>>
>>* What led up to the situation?
>>* What exactly did you do (or not do) that was effective (or
>>  ineffective)?
>>* What was the outcome of this action?
>>* What outcome did you expect instead?
>>
>> *** End of the template - remove these template lines ***
>>
>>
>> -- System Information:
>> Debian Release: stretch/sid
>>   APT prefers unstable
>>   APT policy: (500, 'unstable'), (1, 'experimental')
>> Architecture: amd64 (x86_64)
>> Foreign Architectures: i386
>>
>> Kernel: Linux 4.3.0-1-amd64 (SMP w/2 CPU cores)
>> Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
>> Shell: /bin/sh linked to /bin/dash
>> Init: systemd (via /run/systemd/system)
>>
>> Versions of packages ocserv depends on:
>> ii  libc6  2.21-4
>> ii  libgnutls-deb0-28  3.3.18-1
>> ii  libhttp-parser2.1  2.1-2
>> ii  liblz4-1   0.0~r131-1
>> ii  libnl-3-2003.2.26-1
>> ii  libnl-route-3-200  3.2.26-1
>> ii  libopts25  1:5.18.6-4
>> ii  libpam0g   1.1.8-3.1
>> ii  libpcl11.6-1
>> ii  libprotobuf-c1 1.1.1-1
>> ii  libreadline6   6.3-8+b4
>> ii  libseccomp22.2.3-2
>> ii  libsystemd0228-2
>> ii  libtalloc2 2.1.5-1
>> ii  libwrap0   7.6.q-25
>>
>> Versions of packages ocserv recommends:
>> ii  ca-certificates  20150426
>> ii  ssl-cert 1.0.37
>>
>> ocserv suggests no packages.
>>
>> -- no debconf information
>>
> --
> fishy
>
-- 
fishy

Bug#786165: gbirthday: deprecation of python-support

[Jérôme]

Le Tue, 15 Dec 2015 13:30:36 +,
Mattia Rizzolo  a écrit :

> On Tue, Dec 15, 2015 at 10:04:09AM +0100, Jérôme wrote:
> > Hi.
> 
> Hi Jérôme!
> Please note that nor me nor anybody else but the maintainer receive
> emails from bug reports unless they have subscribed through the PTS or
> to that specific bug.  So if you want to get the attention of somebody
> in cases like this would be better if you keep the in Cc or such.

Actually, I didn't mean to ping anybody. I was rather writing this for
the record, for anyone looking for this and ending up on the bugtracker.
 
> Yeah, this bug is mostly about deprecating a debian tool (pysupport)
> in favour of another (dh-python, or better, dh_python2 in this case).

This is pretty much all I had understood.
 
> I uploaded dozens of packages in the last 4 days removing it, but I'm
> stuck at gbirthday because it insists at installing images in sitelib,
> which used to be /usr/share/pyshared/gbirthday/ with pysupport, but
> now we're migrating off that directory and going to
> /usr/lib/python2.7/dist-packages, where images are not really welcome.

OK, this is concrete.
 
> So, given that this is actually an application and not a python module
> or such.
> 
> To do so, I'd like to upload what I attached as debdiff.
> In particoular I'm adding a patch to let it load from
> /usr/share/gbirthday.  

Alright. I have no educated opinion about this choice.

Do you want to put all gbirthday in /usr/share/gbirthday ? Or only
the images, while the code would be in /usr/lib/python2.7/dist-packages?

> Happens that the program doesn't load here, no
> UI appears; since this is the same behaviour I have with the package
> already in the archive that's not a regression, 

You mean package gbirthday from stable/testing does not work for you? I
guess this should be investigated. You should probably file a bug.
Maybe also try GitHub version (no need to install, executing from
the repo is fine).

Missing dependency?

Any console output?

> but given that
> uploading such untested changes would be too bad, I'd like to ask you
> what do you think of the patch attached as 'patch'.

Well, the patch looks fine. It worked on my machine.

I don't really see the need for the try clause. I mean if gbirthday is
installed in /usr/share/gbirthday, it is bound to fail, isn't it? And
the code in the except clause will be executed everytime.

If you upload an experimental version, I'll give it a try.

> > For the record, gbirthday has moved to GitHub:
> > https://github.com/Jerome-github/gbirthday/. I should update the
> > watch file (this seems feasible to me, but there is no need to do
> > it as long as there is no new release).
> 
> I would update it, but I don't know which kind of filenames you'll
> use, since there is no release already made there.

Ah. I didn't notice I had not uploaded the tags...

There you go:

https://github.com/Jerome-github/gbirthday/releases

(Note that a new version is available that gets rid of a broken
dependency.)

> [...]
> > - Unless somebody comes in, gbirthday won't evolve as it is and will
> > probably be out of Stretch or the next Debian release due to
> > dependencies deprecation. I'm happy if I'm wrong.
> 
> Not with *this* deprecation ;)

Alright. Good to know.
 
> > - I hope to get a Qt version packageable for Stretch. Help welcome,
> > of course.
> 
> Stretch will still release with python2, even if we definitely would
> like to remove it for buster.

Yep, I read that.

Don't give me too much time or I'll slack until last moment...

Thanks.

-- 
Jérôme

Bug#803927: Patch for eglibc 2.13 in wheezy

[Aurelien Jarno]

On 2015-11-24 17:34, Raphael Hertzog wrote:
> [ Cc the security team if they want to use it to prepare a DSA ]
> 
> Hello,
> 
> since the wheezy eglibc is relatively close to squeeze's version, I have
> updated my former backport for wheezy as well.
> 
> Please find the patch attached. It does build but the resulting
> package has not been tested and I did not do any comparison of the
> build logs to identify regression via the test suite.
> 

Thanks for the patch. I have applied it and updated bug#802371 so that
we can get an updated package in the next point release.

I'll work on the jessie upload in the next days.

Aurelien

-- 
Aurelien Jarno  GPG: 4096R/1DDD8C9B
aurel...@aurel32.net http://www.aurel32.net

Bug#803281: marked as done (prepare for giflib5)

[Debian Bug Tracking System]

Your message dated Tue, 15 Dec 2015 23:50:35 +
with message-id 
and subject line Bug#803281: fixed in gladtex 1.4.2-2
has caused the Debian Bug report #803281,
regarding prepare for giflib5
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.)


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

Package: src:gladtex
Version:1.4.2-1
Tags: sid stretch patch
Blocks: 803158
User: gif...@packages.debian.org
Usertags: giflib5

Planning an update of giflib to the current version 5.1.1. Giflib slightly 
changes it's API, requiring soureful changes. There are some options for getting 
giflib5.1 support:


- Look for a newer upstream version, if upstream supports
both giflib4 and giflib5.1. Upload the new package,
and close the bug report.

- Patch the code to both use the NEW API. This can be done using
#if GIFLIB_MAJOR >= 5

#else

#endif
Please upload the package, and close the report.

- Unconditionally patch the code, not supporting giflib4 anymore.
Please upload a package to experimental once giflib5 hits
experimental.

For the latter two options, please see a patch at
http://launchpadlibrarian.net/222923611/gladtex_1.4.2-1build2_1.4.2-1ubuntu1.diff.gz

To test your changes before giflib5 is found in experimental, please use

deb https://people.debian.org/~doko/tmp/giflib5 ./

Thanks, Matthias
--- End Message ---
--- Begin Message ---
Source: gladtex
Source-Version: 1.4.2-2

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

Debian distribution maintenance software
pp.
Sebastian Humenda  (supplier of updated gladtex 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, 14 Dec 2015 11:27:20 +0100
Source: gladtex
Binary: gladtex
Architecture: source amd64
Version: 1.4.2-2
Distribution: unstable
Urgency: medium
Maintainer: Sebastian Humenda 
Changed-By: Sebastian Humenda 
Description:
 gladtex- Embed LaTeX equations in HTML files
Closes: 803281
Changes:
 gladtex (1.4.2-2) unstable; urgency=medium
 .
   * Bump Standards-Version to 3.9.6 (no changes).
   * remove GIF support (removed in new upstream version anyway)
 (Closes: #803281)
Checksums-Sha1:
 bc97f4967c0e5e5e667d8dd444c7427d35dddfec 1834 gladtex_1.4.2-2.dsc
 80d29936507bacfdf11bc469583acaf980462298 2092 gladtex_1.4.2-2.debian.tar.xz
 f29d82bc2b56a21cd775e99ec94f78537b565939 22482 gladtex_1.4.2-2_amd64.deb
Checksums-Sha256:
 090e2beb8fda52d2b092c8a0900a5a529ba9710165bd1da973ac91b67d2d045b 1834 
gladtex_1.4.2-2.dsc
 f23c71c69c5e9bd52d512cf6c019cd20a18d10a2eba952ae2d357a9f18370945 2092 
gladtex_1.4.2-2.debian.tar.xz
 d5f95bb37a47abdcb3f9b9abb9a8a684a886ebfaf7c8e5596b2d4a4f9eccd110 22482 
gladtex_1.4.2-2_amd64.deb
Files:
 a000315706014b53775a108a4d315b29 1834 text optional gladtex_1.4.2-2.dsc
 0a12ff224e37b1be8309b5d02b197ea6 2092 text optional 
gladtex_1.4.2-2.debian.tar.xz
 ee5ef6cf89fc8b9024864e95be645db9 22482 text optional gladtex_1.4.2-2_amd64.deb

-BEGIN PGP SIGNATURE-
Version: GnuPG v1

iQIcBAEBCgAGBQJWcKJyAAoJEAdNJfYUJ+jAgP0P/iTv0qRuucGYfDxRg2t+aeVE
VLVLkNoB+YM0HQCrgYmxkwYR/pnZG/agwKrRq8l3QTVzcfBLeC7n2+4jHKqDG3iv
MDYjGBR7kaafi3KUJxQzqSJW3UvycNDh0TcvcnGw8n/joyw1vJfiGrVrbHh7x5Eq
WSe8e57iD4rTyAJv3Ruy8DGeyhOQHJs1UMHOUQ2Ve7nxDRwrA2kmX+7/kCxzZjuO
/4DQ9uT/gRIrLzT+Fltqld97BtVoHtjcUX0iQpnFmt1wE3Erl/bIUkt9opqnRen8
pzpeJ7My1we5bfQW60zjbbuBgrEH9vH1aUhk/wfIcCvj96M/LZ0NQ4zPg7410jog
UzNrIKviqpwJbydmx3ZYMcqYypacmdqePHFAO/fbDQ8c1RcIo4ushCtQMktqOkJM
iQn57moZXZlrLynJIsB5QRlaSH41pOwJKP89no42xJSmvCURa5kOjNk1uB0saeD4
l2foasylsBZXMIdz7RIueYIXnBYpoU8oV0NJ8PGb0Mk6EnmDRiinkyIFfYl3GGa2
U+JpNFrduYpE1DNZ5j9Imv+0TCsWx5oaWrGxTHImZ7ZyHtz7OwOsJ/88MnYVfVyN
6XgZ97IW5+PSSJGRj4/vshDGJDEPMt4EbK8GAzjz+Oc7cVSm371XcP7QpuUXQELX
owGQXlKtIUoX6jdkIyZs
=IFMC
-END PGP SIGNATURE End Message ---

Processed: your mail

[Debian Bug Tracking System]

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

> # gnome-schedule, RM in 808060
> tag 786065 pending
Bug #786065 [src:gnome-schedule] gnome-schedule: deprecation of python-support
Added tag(s) pending.
> # mumble-django, RM in 808042
> tag 786086 pending
Bug #786086 [src:mumble-django] mumble-django: deprecation of python-support
Added tag(s) pending.
> --
Stopping processing here.

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

Bug#786165: gbirthday: deprecation of python-support

[Mattia Rizzolo]

On Wed, Dec 16, 2015 at 12:35:31AM +0100, Jérôme wrote:
> Mattia Rizzolo  a écrit :
> > On Tue, Dec 15, 2015 at 10:04:09AM +0100, Jérôme wrote:
> > So, given that this is actually an application and not a python module
> > or such.
> > 
> > To do so, I'd like to upload what I attached as debdiff.
> > In particoular I'm adding a patch to let it load from
> > /usr/share/gbirthday.  
> 
> Alright. I have no educated opinion about this choice.
> 
> Do you want to put all gbirthday in /usr/share/gbirthday ? Or only
> the images, while the code would be in /usr/lib/python2.7/dist-packages?

It's not really important from my POV.
the gbirthday python module can really be thought as a private module,
and interely installed in /usr/share/. See the Debian Python
Policy for more in this regard:

https://www.debian.org/doc/packaging-manuals/python-policy/ch-programs.html#s-current_version_progs

I figured it would be easier for me to just do that, rather than trying
to separate assents (since ISTR it's not only images) from the code.

> > Happens that the program doesn't load here, no
> > UI appears; since this is the same behaviour I have with the package
> > already in the archive that's not a regression, 
> 
> You mean package gbirthday from stable/testing does not work for you? I
> guess this should be investigated. You should probably file a bug.
> Maybe also try GitHub version (no need to install, executing from
> the repo is fine).
> 
> Missing dependency?
> 
> Any console output?

dunno:
mattia@chase ~/devel/NMU/gbirthday % gbirthday
^CTraceback (most recent call last):
  File "/usr/bin/gbirthday", line 12, in 
main()
  File "/usr/share/gbirthday/gbirthday/__init__.py", line 249, in main
gtk.main()
KeyboardInterrupt


> > but given that
> > uploading such untested changes would be too bad, I'd like to ask you
> > what do you think of the patch attached as 'patch'.
> 
> Well, the patch looks fine. It worked on my machine.
> 
> I don't really see the need for the try clause. I mean if gbirthday is
> installed in /usr/share/gbirthday, it is bound to fail, isn't it? And
> the code in the except clause will be executed everytime.

The try/except structure is to make it easier to get accepted and
incorporated by you upstream.
I wanted to avoid doing such checks if the gbirthday module is already
present.  TBH, I did that following what I read on openshot main script
earlier today, which was in more or less the same issue.

> If you upload an experimental version, I'll give it a try.

Ok, I these days I feel very lightway wrt uploading, so I just pushed
that to experimental.

> > > For the record, gbirthday has moved to GitHub:
> > > https://github.com/Jerome-github/gbirthday/. I should update the
> > > watch file (this seems feasible to me, but there is no need to do
> > > it as long as there is no new release).
> > 
> > I would update it, but I don't know which kind of filenames you'll
> > use, since there is no release already made there.
> 
> Ah. I didn't notice I had not uploaded the tags...
> 
> There you go:
> 
> https://github.com/Jerome-github/gbirthday/releases

Actually I screw the upload up: I uploaded, then recalled about this,
hurried up to cancel the upload, but I got a mail telling me it didn't
cancel anything, so meh.

Anyway, I'll include it in the unstable upload.

> (Note that a new version is available that gets rid of a broken
> dependency.)

I want to try uploading a new upstream version in a NMU, if possible :)

> Don't give me too much time or I'll slack until last moment...

heh

> Thanks.

Thank you for being involved downstream! :)

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

Processed: tagging 808054

[Debian Bug Tracking System]

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

> tags 808054 + pending
Bug #808054 [src:docker-libkv] docker-libkv: FTBFS: keys.generated.go:11:2: 
cannot find package "github.com/ugorji/go/codec"
Added tag(s) pending.
> thanks
Stopping processing here.

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

Bug#803725: marked as done (subversion: dump-load of a repository modifies verbose log output: M line lost)

[Debian Bug Tracking System]

Your message dated Wed, 16 Dec 2015 04:29:03 +
with message-id 
and subject line Bug#803725: fixed in subversion 1.9.3-1
has caused the Debian Bug report #803725,
regarding subversion: dump-load of a repository modifies verbose log output: M 
line lost
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.)


-- 
803725: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=803725
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: subversion
Version: 1.9.2-2
Severity: critical
Justification: causes serious data loss

I've posted the following to the Subversion-dev mailing-list:

  http://svn.haxx.se/dev/archive-2015-11/0001.shtml

With the MPFR repository:

I currently have:

zira:~> TZ=UTC svn log -r 1984 -v file:///home/vinc17/private/svn-mpfr

r1984 | vlefevre | 2002-07-23 16:22:08 + (Tue, 23 Jul 2002) | 2 lines
Changed paths:
   M /trunk/mul.c

Fixed permissions.



But after a dump-load:

zira:~> TZ=UTC svn log -r 1984 -v file:///home/vinc17/private/test-svn-mpfr

r1984 | vlefevre | 2002-07-23 16:22:08 + (Tue, 23 Jul 2002) | 2 lines

Fixed permissions.



The "M /trunk/mul.c" line has been lost!

FYI, this came from the CVS conversion, where the permissions of mul.c
were changed, but with no effect in the SVN repository.

I don't know whether this is due to a buggy change in the format of
the dump, or a bug in the load. The dump of this revision changed in
the following way for this revision:

 Node-path: trunk/mul.c
 Node-kind: file
 Node-action: change
-Text-delta: true
-Text-delta-base-md5: a79ede6a595f7bad6a4549c23ef9cd2b
-Text-delta-base-sha1: a9ce78ba643c727019f926d957f37414cfc1a050
-Text-content-length: 15
-Text-content-md5: a79ede6a595f7bad6a4549c23ef9cd2b
-Text-content-sha1: a9ce78ba643c727019f926d957f37414cfc1a050
-Content-length: 15

-[Contents]

This might be related to:

  http://subversion.tigris.org/issues/show_bug.cgi?id=4598

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

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

Versions of packages subversion depends on:
ii  libapr11.5.2-3
ii  libaprutil11.5.4-1
ii  libc6  2.19-22
ii  libldap-2.4-2  2.4.42+dfsg-2
ii  libsasl2-2 2.1.26.dfsg1-14
ii  libsvn11.9.2-2

subversion recommends no packages.

Versions of packages subversion suggests:
pn  db5.3-util
ii  patch 2.7.5-1
ii  subversion-tools  1.9.2-2

-- no debconf information
--- End Message ---
--- Begin Message ---
Source: subversion
Source-Version: 1.9.3-1

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

Debian distribution maintenance software
pp.
James McCoy  (supplier of updated subversion 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: Tue, 15 Dec 2015 20:26:57 -0500
Source: subversion
Binary: subversion subversion-dbg libsvn1 libsvn-dev libsvn-doc 
libapache2-mod-svn libapache2-svn python-subversion subversion-tools 
libsvn-java libsvn-perl ruby-svn libsvn-ruby1.8
Architecture: source
Version: 1.9.3-1
Distribution: unstable
Urgency: high
Maintainer: Peter Samuelson 
Changed-By: James McCoy 
Closes: 796781 797216 802156 802611 803725
Description: 
 libapache2-mod-svn - Apache Subversion server modules for Apache httpd
 libapache2-svn - Apache Subversion server modules for Apache httpd (dummy 
package)
 libsvn1- Shared libraries used by Apache 

Bug#800268: marked as done (xflip: Please migrate a supported debhelper compat level)

[Debian Bug Tracking System]

Your message dated Wed, 16 Dec 2015 04:29:20 +
with message-id 
and subject line Bug#800268: fixed in xflip 1.01-26
has caused the Debian Bug report #800268,
regarding xflip: Please migrate a supported debhelper compat level
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.)


-- 
800268: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=800268
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: xflip
Severity: important
Usertags: deprecated-debhelper-compat-leq-3

Hi,

The package xflip is using a debhelper compat level of 3 or less
according to lintian.  These compat levels have been deprecated for
the past ~10 years and debhelper will remove support for them in the near
future (as declared in [1]).

 * Please migrate the package to a supported debhelper compat level.
   - Compat 9 is recommended
   - Compat 5 is the bare minimum (compat 4 will be removed soon as
 well)

 * If your package uses any of the following tools, please remove them
   from the rules files.  Neither of them does anything except warn
   about their deprecation.
   - dh_desktop
   - dh_scrollkeeper (deadline: January 1st 2016)
   - dh_suidregister
   - dh_undocumented

 * Please note that your package might have been flagged for using
   e.g. "DH_COMPAT=2 dh_foo ...".
   - This will still cause issues when the compat level is removed.

 * If the package has been relying on dh_install being lenient about
   missing files, please see "MIGRATING TO COMPAT 5 OR LATER" in [1].

 * Deadline: 
   - compat 1+2: November 1st 2015
   - compat 3: January 1st 2016

If you are using other deprecated debhelper features (such as omitting
the debian/compat file), please consider fixing those while you are at
it.

Thanks,
~Niels

[1] https://lists.debian.org/debian-devel/2015/09/msg00257.html
--- End Message ---
--- Begin Message ---
Source: xflip
Source-Version: 1.01-26

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

Debian distribution maintenance software
pp.
Joao Eriberto Mota Filho  (supplier of updated xflip 
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, 14 Dec 2015 19:41:53 -0200
Source: xflip
Binary: xflip
Architecture: source
Version: 1.01-26
Distribution: unstable
Urgency: medium
Maintainer: Debian QA Group 
Changed-By: Joao Eriberto Mota Filho 
Description:
 xflip  - programs to mirror-image or melt your display
Closes: 800268
Changes:
 xflip (1.01-26) unstable; urgency=medium
 .
   * QA upload.
   * Set maintainer as Debian QA Group  (see #800325).
   * Migrations:
   - debian/copyright to 1.0 format.
   - debian/rules to (new) reduced format.
   - DebSrc to 3.0 format.
   - DH level to 9. (Closes: #800268)
   * debian/compat: added. (Closes: #800268)
   * debian/control:
  - Added the ${misc:Depends} variable to provide the right install
dependencies.
  - Bumped Standards-Version to 3.9.6.
   * debian/links: added to link the meltdown manpage to xflip manpage.
   * debian/manpages: added to install the manpage.
   * debian/patches/10_avoid_direct_changes.patch: created to avoid direct
   changes in upstream source code. Removed the file 'trace\=open', a trash
   created by strace command in a past time. The manpage was extracted.
   * debian/watch: added a fake site to explain about the current status of the
   original upstream homepage.
   * debian/xflip.6: extracted from patch 10_avoid_direct_changes.patch.
Checksums-Sha1:
 c29c63bfbdf56b12e2abdbc8e52c2d8f0cf1151d 1641 xflip_1.01-26.dsc
 6c8ecf46043d756e49464023f661da05a4c615bd 5796 xflip_1.01-26.debian.tar.xz
Checksums-Sha256:
 e639f8451d2a8434171102732d672205d0544b65c6512f85941832bb8fc811d7 1641 
xflip_1.01-26.dsc
 687d451000b266b4a41bd021ed305cc92cefa27879b9ddc291d2b19f407ff051 5796 
xflip_1.01-26.debian.tar.xz
Files:
 ea8deff0dc5012f29972fe20ec32ad4f 1641 games optional xflip_1.01-26.dsc
 

Bug#786165: gbirthday and python-support

[Rolf Leggewie]

Hello guys,

thank you for working on this bug. I'm happy some work has been done in
experimental already.

What I do not understand is why this bug is marked as RC.  As far I am
aware removal of python-support is not an RC-goal.  I think this ticket
should be downgraded.

Mattia, do you have your changes in git somewhere?  It would be nice if
you pushed them to a separate branch in alioth.  I'd like to cherry-pick
the stuff I like.

I haven't been able to upload for several months and I believe the issue
with my key is as of now still unresolved.  I'll have to look into it again.

Regards

Rolf

Bug#808022: marked as done (gs-collections: FTBFS: Error resolving version for plugin 'org.apache.felix:maven-bundle-plugin' from the repositories)

[Debian Bug Tracking System]

Your message dated Tue, 15 Dec 2015 15:50:50 +
with message-id 
and subject line Bug#808022: fixed in gs-collections 5.1.0-2
has caused the Debian Bug report #808022,
regarding gs-collections: FTBFS: Error resolving version for plugin 
'org.apache.felix:maven-bundle-plugin' from the repositories
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.)


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

Dear Maintainer,

gs-collections fails to build from source in unstable/amd64:

  [..]

  [INFO] Compiling 8 source files to 
/home/lamby/temp/cdt.20151215105604.OhDc8OlapK/gs-collections-5.1.0/gs-collections-forkjoin/target/classes
  [INFO] 
/home/lamby/temp/cdt.20151215105604.OhDc8OlapK/gs-collections-5.1.0/gs-collections-forkjoin/src/main/java/com/gs/collections/impl/forkjoin/FJIterate.java:
 
/home/lamby/temp/cdt.20151215105604.OhDc8OlapK/gs-collections-5.1.0/gs-collections-forkjoin/src/main/java/com/gs/collections/impl/forkjoin/FJIterate.java
 uses unchecked or unsafe operations.
  [INFO] 
/home/lamby/temp/cdt.20151215105604.OhDc8OlapK/gs-collections-5.1.0/gs-collections-forkjoin/src/main/java/com/gs/collections/impl/forkjoin/FJIterate.java:
 Recompile with -Xlint:unchecked for details.
  [INFO] 
  [INFO] --- maven-resources-plugin:2.6:testResources (default-testResources) @ 
gs-collections-forkjoin ---
  [INFO] Using 'UTF-8' encoding to copy filtered resources.
  [INFO] skip non existing resourceDirectory 
/home/lamby/temp/cdt.20151215105604.OhDc8OlapK/gs-collections-5.1.0/gs-collections-forkjoin/src/test/resources
  [INFO] 
  [INFO] --- maven-compiler-plugin:3.2:testCompile (default-testCompile) @ 
gs-collections-forkjoin ---
  [INFO] Nothing to compile - all classes are up to date
  [INFO] 
  [INFO] --- maven-surefire-plugin:2.17:test (default-test) @ 
gs-collections-forkjoin ---
  [INFO] Tests are skipped.
  [INFO] 
  [INFO] <<< maven-bundle-plugin:2.5.4:bundle (default-bundle) < package @ 
gs-collections-forkjoin <<<
  [INFO] 
  [INFO] --- maven-bundle-plugin:2.5.4:bundle (default-bundle) @ 
gs-collections-forkjoin ---
  [INFO]
 
  [INFO] 

  [INFO] Building Goldman Sachs Collections Parent Project 5.1.0
  [INFO] 

  [INFO] 

  [INFO] Reactor Summary:
  [INFO] 
  [INFO] Goldman Sachs Collections Code Generator ... SUCCESS [  2.974 
s]
  [INFO] Goldman Sachs Collections Code Generator Maven Plugin SUCCESS [  1.238 
s]
  [INFO] Goldman Sachs Collections API .. SUCCESS [ 10.861 
s]
  [INFO] Goldman Sachs Collections Main Library . SUCCESS [ 58.261 
s]
  [INFO] Goldman Sachs Collections Test Utilities ... SUCCESS [  0.771 
s]
  [INFO] Goldman Sachs Collections Fork Join Utilities .. SUCCESS [  0.399 
s]
  [INFO] Goldman Sachs Collections Parent Project ... FAILURE [  0.001 
s]
  [INFO] 

  [INFO] BUILD FAILURE
  [INFO] 

  [INFO] Total time: 01:16 min
  [INFO] Finished at: 2015-12-15T11:01:13+00:00
  [INFO] Final Memory: 53M/1804M
  [INFO] 

  [ERROR] Error resolving version for plugin 
'org.apache.felix:maven-bundle-plugin' from the repositories [local 
(/home/lamby/temp/cdt.20151215105604.OhDc8OlapK/gs-collections-5.1.0/debian/maven-repo),
 central (https://repo.maven.apache.org/maven2)]: Plugin not found in any 
plugin repository -> [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/PluginVersionResolutionException
  /usr/share/cdbs/1/class/maven.mk:92: recipe for target 'mvn-build' failed
  make: *** 

Bug#785987: marked as done (controlaula: deprecation of python-support)

[Debian Bug Tracking System]

Your message dated Tue, 15 Dec 2015 15:50:26 +
with message-id 
and subject line Bug#785987: fixed in controlaula 1.8.0-3.1
has caused the Debian Bug report #785987,
regarding controlaula: 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.)


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

We believe that the bug you reported is fixed in the latest version of
controlaula, 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.
Mattia Rizzolo  (supplier of updated controlaula 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, 13 Dec 2015 00:50:30 +
Source: controlaula
Binary: controlaula ltsp-controlaula
Architecture: source
Version: 1.8.0-3.1
Distribution: unstable
Urgency: medium
Maintainer: José L. Redrejo Rodríguez 
Changed-By: Mattia Rizzolo 
Description:
 controlaula - classroom management tool
 ltsp-controlaula - classroom management tool - LTSP client version
Closes: 785987
Changes:
 controlaula (1.8.0-3.1) unstable; urgency=medium
 .
   * Non-maintainer upload.
   * Remove obsolated DM-Upload-Allowed field from debian/control.
   * Build using dh-python instead of python-support.  Closes: #785987
Checksums-Sha1:
 d7c302720589a2f7b55c206221f0c2a3affe7d8c 1857 controlaula_1.8.0-3.1.dsc
 4a92f36b2b41595b33db8e7fb0d70d570783bb48 11648 
controlaula_1.8.0-3.1.debian.tar.xz
Checksums-Sha256:
 44e574fc5cb15ebafd6850ed7ca8bb0b1549de2340d0a967740506aa57ba0ece 1857 
controlaula_1.8.0-3.1.dsc
 95f3d0c9419b594b34ca8341c4911292582da51771351de2815a10c82585c374 11648 
controlaula_1.8.0-3.1.debian.tar.xz
Files:
 5ea21579fa589b77df7ec76adfcee48d 1857 admin optional controlaula_1.8.0-3.1.dsc
 f6dbf9e3102471bd8fbf9ea50adca376 11648 admin optional 
controlaula_1.8.0-3.1.debian.tar.xz

-BEGIN PGP SIGNATURE-
Version: GnuPG v1

iQIcBAEBCAAGBQJWbMRrAAoJEEsEP825REVALDEQAJRlgv1uXrt0JdWifGq1x8Sm
FfBEFDa5yrwqhQVLGZ/F2cIXQkRVSgrAq9aa5r2yo0nBFtoes51HMn+tkGSuFBbU
hnu/W1WXb+WJEMxsUwBIliv6/pfENLiXnkR+K2peGE6Rx8fIWWsuo1LlodJiuqVR
MRGTYIAxqjuZ3BI/MYGayj0x/MRr5J5wB68eFL0g4nTQEfZ28dJ8+zihJdc+CM9N
ZtNYJ2DpEMbCKVEKVIC+WfRuFQqaR75R/Fa5dxNCmxOXr+rdV6Tbu+B0V9ruZ7C4
vFNXqFvgYAkScHbrGNuubR6dZzkT1TIrD896brqcPNZf2b+/rUi7RReNuZWSiZT9
2uWwBbrmJU/Isvh7LGjFPAElZm1cjH6EYSNya0eMbRBNw110rbh1Pcg2tTk2Vsuv
weeSeBPvpxRAcYN+gIM8PZ+QH36CtEA4mx/4l3cIlXoAmzUkgMQsEQ8uXKWFyyoj
VibtSZfQr13PKRmac4vo8NmL0rTJaKiK51HMysZnkIJ8D9JrJyzWhZgQUMCV6ade
QtIffeMq2i0dHfhXtNJNA+IDLqBpT5tOJZK4N2YcghMG4uivWN2IIoQ9Joo0XZUR
xH+ShIisMe+SOhnJ6Rj7QWhQhhZKISdRGu1OYiBIb02r/EtSrhpWv7x03BtiGGt2

Bug#786042: marked as done (jack: deprecation of python-support)

[Debian Bug Tracking System]

Your message dated Tue, 15 Dec 2015 15:51:30 +
with message-id 
and subject line Bug#786042: fixed in jack 3.1.1+cvs20050801-29.1
has caused the Debian Bug report #786042,
regarding jack: 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.)


-- 
786042: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=786042
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: jack
Version: 3.1.1+cvs20050801-29
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: jack
Source-Version: 3.1.1+cvs20050801-29.1

We believe that the bug you reported is fixed in the latest version of
jack, 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.
Mattia Rizzolo  (supplier of updated jack 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, 13 Dec 2015 17:21:11 +
Source: jack
Binary: jack
Architecture: source
Version: 3.1.1+cvs20050801-29.1
Distribution: unstable
Urgency: medium
Maintainer: Michael Banck 
Changed-By: Mattia Rizzolo 
Description:
 jack   - Rip and encode CDs with one command
Closes: 786042
Changes:
 jack (3.1.1+cvs20050801-29.1) unstable; urgency=medium
 .
   * Non-maintainer upload.
   * Build with dh-python instead of python-support.  Closes: #786042
   * Update watch file.
Checksums-Sha1:
 a7e3a2a109aa7f4a3fde70569be5adfb9795f5a8 1769 jack_3.1.1+cvs20050801-29.1.dsc
 a1c432b1eb13a9fa9204f6f2f543f398c47fcd2b 65622 
jack_3.1.1+cvs20050801-29.1.diff.gz
Checksums-Sha256:
 9ba2fef0a849459ee043fe0370baccd22d87449a6eb5f13dae54322eb187b57c 1769 
jack_3.1.1+cvs20050801-29.1.dsc
 9ed9a25f03fd830919080716eff9e378136067e04c4fbcf5f88860bf606b15b1 65622 
jack_3.1.1+cvs20050801-29.1.diff.gz
Files:
 daa8ab6da1ed6ce2b66f0cf65b86212b 1769 sound optional 
jack_3.1.1+cvs20050801-29.1.dsc
 b48c1232faf0328acb011c79610b8959 65622 sound optional 
jack_3.1.1+cvs20050801-29.1.diff.gz

-BEGIN PGP SIGNATURE-
Version: GnuPG v1

iQIcBAEBCAAGBQJWbanyAAoJEEsEP825REVA/uIQAKRf8OKmNpv/1jEJVdiU/TdF
SmOuXSMc8US6/JHN8ucHzbyq540uvYWaGjw8AwnzrMX+MZ6pqBeWHHGKoD2iFHW6
h7yWOq96yeB2NBN7TPY0PCJLxJ4nWIqL074It1fruTAMq1dQoDLxMgVWGMY3IbA3
uc2hjXevKqltHaK+d1YVmATR9w9n5va7kg7LuQ86+ZD8qWekcOBr/20F39fNMwtp
xBGqPB/BD4JazXYW3HoOQVidKnxL+Fzxow+n6VtfdThRGMBzA1IfrPrnqG9YzP4L
3ugBV7QTarxC67w+sSlH+ZerI7XOTn1YKtKUE47+jTMocSiVkKTzMAy8x3AjShM6
ycEZ2hx9hauch745AQAu49eKLJv3/C14GI2boNBVg6RrmhZc3S9EnjOMwShmwsUh
c//L5aLLhqdczErIXwLSQlOriuSHJQ68aF/iF8IpWB3+sHJKOR97oTKLicsfIM2f
8m1mnhW/OmaRE97+/pagQkTIONqe5AwBEU98e2EeRSt7zFjrg1kQE+gVqSJhBINM
lWmrBT+7rEDP387ItbotBMpTmXeuzGanGJzeO/V2V78xDiF/JRUxGvUwOHgENION
ksg2TFmOHQQ9F9UGD5LEIXUwV/Y82BkbqLkEKbfu96r04NKeLGVAsZa0LT6TObam
4hjfXqTfHsEh8m0Kdqx5
=Lllk
-END PGP SIGNATURE End Message ---

Bug#786083: marked as done (pythontracer: deprecation of python-support)

[Debian Bug Tracking System]

Your message dated Tue, 15 Dec 2015 15:56:29 +
with message-id 
and subject line Bug#786083: fixed in pythontracer 8.10.16-1.2
has caused the Debian Bug report #786083,
regarding pythontracer: 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.)


-- 
786083: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=786083
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: pythontracer
Version: 8.10.16-1.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: pythontracer
Source-Version: 8.10.16-1.2

We believe that the bug you reported is fixed in the latest version of
pythontracer, 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.
Mattia Rizzolo  (supplier of updated pythontracer 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, 12 Dec 2015 13:40:02 +
Source: pythontracer
Binary: pythontracer
Architecture: source
Version: 8.10.16-1.2
Distribution: unstable
Urgency: medium
Maintainer: TANIGUCHI Takaki 
Changed-By: Mattia Rizzolo 
Description:
 pythontracer - Python programs' execution tracer and profiler
Closes: 786083
Changes:
 pythontracer (8.10.16-1.2) unstable; urgency=medium
 .
   * Non-maintainer upload.
   * Migrate from python-support to dh-python.  Closes: #786083
Checksums-Sha1:
 8715440a339a5f3863dc6b6cd3fd7fb74e5b072d 1805 pythontracer_8.10.16-1.2.dsc
 b71631979014dc236e3655d65dac4290853e791e 2188 
pythontracer_8.10.16-1.2.debian.tar.xz
Checksums-Sha256:
 ad6b17bf83a204379774f574c0f2b68967f9eb37e98393fc999226b216a16abc 1805 
pythontracer_8.10.16-1.2.dsc
 88a94b2151f5188057e9b7e370478faa1ed3c5708f802b8af4a6323464883fb1 2188 
pythontracer_8.10.16-1.2.debian.tar.xz
Files:
 556c78c7b0806450b6a3f9718bfa1875 1805 python extra pythontracer_8.10.16-1.2.dsc
 eafff40f335af932407d94e8df7b522e 2188 python extra 
pythontracer_8.10.16-1.2.debian.tar.xz

-BEGIN PGP SIGNATURE-
Version: GnuPG v1

iQIcBAEBCAAGBQJWbCPTAAoJEEsEP825REVAYtAP/AgdHuCvy/AsK0IR8mbVlX+w
jePkquvyLRf1HoEQGdK5ffBTWo57nTtiN2qcDSEOeaXrpm0u0IKAc2+4F8Q3FGg9
/q2EAcQkjjsIhfyLLoOQxpzfuElF+6o1vl3mhNXqI3oiHhwnM+fqwMMe609UKiRw
3s1q4bSasFy9Unj+yemWhd169E961SYDJSlkgRQX/NDL+1HQBbJMjoboUuXXpwy7
jFXaIGL7/2y0buvkdL9tXg03L7TM+6ajxLXboPCcgUzgrriSpIu21NObL7T36HUW
1c2ANWrUFoDMEjdKERWQU1o9yYSh7hRipLTPWY5jfPA+qe56d4kqdCKArnRGF7cZ
mDr6yMVhymDe/vjVeZ91hcsyguRGa0Gp2nJMM/LrS97Jbe8gNTxrBY0tSaPzTyoT
Z0VlJcIZtgQh9dOIIpJReAJ8xGP6peZLF36ANYijKG7gJwb7Z7dTeIgDWOIhBIFp
TWko5S8EIaP5rw2fa5JtnZ9ToQYWwGqptjgvoO6b93x2S50TQJvalSPTNwCpEee+
hF3RxBvPj26J4F77WlzbHmUew//lLNeoAs8f1GxwLSeThFTG8LPvSHNWVt4ioZnM
/mjfUNcJqr3rt1JA0gXMotPHfTAILa/2I74sHUEoY940Y7zm+75JRD+YkoZ+A8tm
aVFSYUD2ydUfeeHJ7Xh4
=ELZ/
-END PGP SIGNATURE End Message ---

Bug#785993: marked as done (python-carrot: deprecation of python-support)

[Debian Bug Tracking System]

Your message dated Tue, 15 Dec 2015 15:55:51 +
with message-id 
and subject line Bug#785993: fixed in python-carrot 0.10.7-1.1
has caused the Debian Bug report #785993,
regarding python-carrot: 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.)


-- 
785993: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=785993
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: python-carrot
Version: 0.10.7-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-carrot
Source-Version: 0.10.7-1.1

We believe that the bug you reported is fixed in the latest version of
python-carrot, 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.
Mattia Rizzolo  (supplier of updated python-carrot 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, 14 Dec 2015 16:57:37 +
Source: python-carrot
Binary: python-carrot
Architecture: source
Version: 0.10.7-1.1
Distribution: unstable
Urgency: medium
Maintainer: David Watson 
Changed-By: Mattia Rizzolo 
Description:
 python-carrot - AMQP messaging queue framework
Closes: 785617 785993
Changes:
 python-carrot (0.10.7-1.1) unstable; urgency=medium
 .
   * Non-maintainer upload.
   * Use source format 3.0 (quilt).
   * Build using dh-python instead of python-support.  Closes: #785993
   * Assure a reproducible build.
 Thanks to Juan Picca  for the patch.  Closes: #785617
   * Bump debhelper compat version to 9.
   * Bump Standards-Version to 3.9.6, no changes needed.
   * Rewrite debian/watch to use the pypi.debian.net redirector.
Checksums-Sha1:
 578c0166b580932147eb5e15bed5dfa006af3adb 1853 python-carrot_0.10.7-1.1.dsc
 f06ff885e0a487a1f685d9563602dbb4c62a0486 3268 
python-carrot_0.10.7-1.1.debian.tar.xz
Checksums-Sha256:
 7307f4810ab5b9a4adb9b26a92a3ba9bc791926b2bf281cbd6cf4f96bd73f889 1853 
python-carrot_0.10.7-1.1.dsc
 56fd998ef2ef258514472d915d90e2962ccb125bebcb0db1a2dcb4f4cdefa5bf 3268 
python-carrot_0.10.7-1.1.debian.tar.xz
Files:
 c36ca5a8ec597ef4d328a237ce85deb3 1853 python optional 
python-carrot_0.10.7-1.1.dsc
 8f17fd35ea58fdc1aeb181bf97c6dcff 3268 python optional 
python-carrot_0.10.7-1.1.debian.tar.xz

-BEGIN PGP SIGNATURE-
Version: GnuPG v1

iQIcBAEBCAAGBQJWbvXXAAoJEEsEP825REVAAGgP/3H9nKTgBz4IpmfeOVT8kUbV
Y29WNAY/FFggcZr3SDGPPlZ1LbtvRVdO80/O3no3inJ6SFWako3zXF6Lk0sKnoaY
EzufKsiO/zlVQU1cFDcrr7wsaBj9lnaoY5pzpxvOc0dW5h62chSCpE7KKH8daB5l
SgE3Mtb6piEJRBeQjl0PiC4Yuppk8G8GKb67iZAenPXzkhLMkxOzX062hi0dDCng
dFZIBremtdE/+3RybOXlhIbzru5b4xqN3BGHv6KkHY9Duoh3jTnvGJsQjkVSiH/N
UmK4iYmri+YwUQgrl+2+KauEnadmRPVGrelAI6XDsy0msbHcK8VFbUEmG4LpcNjh
XWrkcfl1Ngb/ZaM4P9TPYWRAheOcdqmeIzUvEFGkHMO96xc7qg/ck9duJOdiQpt+
L17hpwOfe8ZOloHmkJ3/tWAOnupTTPdFVsHYeV397Qe63oJPSm6EJXBMdv/3MDYW

Bug#786149: marked as done (pivy: deprecation of python-support)

[Debian Bug Tracking System]

Your message dated Tue, 15 Dec 2015 15:55:08 +
with message-id 
and subject line Bug#786149: fixed in pivy 0.5.0~v609hg-3.1
has caused the Debian Bug report #786149,
regarding pivy: 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.)


-- 
786149: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=786149
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: pivy
Version: 0.5.0~v609hg-3
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: pivy
Source-Version: 0.5.0~v609hg-3.1

We believe that the bug you reported is fixed in the latest version of
pivy, 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.
Mattia Rizzolo  (supplier of updated pivy 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, 14 Dec 2015 01:10:04 +
Source: pivy
Binary: python-pivy
Architecture: source
Version: 0.5.0~v609hg-3.1
Distribution: unstable
Urgency: medium
Maintainer: Debian Science Maintainers 

Changed-By: Mattia Rizzolo 
Description:
 python-pivy - Coin binding for Python
Closes: 786149
Changes:
 pivy (0.5.0~v609hg-3.1) unstable; urgency=medium
 .
   * Non-maintainer upload.
   * Remove long useless debian/pycompat file.
   * Build-Depend on dh-python instead of python-support.  Closes:
 #786149
   * use X-Python-Version control field instead of the debian/pyversions
 file.
   * debian/control: bump Standards-Version to 3.9.6, no changes needed.
Checksums-Sha1:
 96584857e76861988a521715f8d4e493d1a5edf0 2089 pivy_0.5.0~v609hg-3.1.dsc
 b1b209ccdbe1f8d632121b04bb0695e78a273276 3246 
pivy_0.5.0~v609hg-3.1.debian.tar.bz2
Checksums-Sha256:
 cdb0aeda909ff994a7768e1c92ac911a76917a4cb87261c75bc9e67c1ee925ea 2089 
pivy_0.5.0~v609hg-3.1.dsc
 3f526f228852da8f0eb068640b30225cf704c8e4c4de5f96646d8fc8dad72358 3246 
pivy_0.5.0~v609hg-3.1.debian.tar.bz2
Files:
 ac702aa1e32012db55bd7ed7dd6f4359 2089 python extra pivy_0.5.0~v609hg-3.1.dsc
 396c45ba765c46508b9990be7da4e4f6 3246 python extra 
pivy_0.5.0~v609hg-3.1.debian.tar.bz2

-BEGIN PGP SIGNATURE-
Version: GnuPG v1

iQIcBAEBCAAGBQJWbhmQAAoJEEsEP825REVAzcYQAKX0tMLtb9W4G62MK1FYaiZj
5qP87bQFlMW87zALuakm2PPdE3+Njjureo30KN30/NtbSGhRkJBxnnnSuQ4FrBOB
q54BHkByfD16py48FjPAU2+EsIkTT46DbtvhPGBKSbVFmayxbifGuqOlHQLsji3j
fOMXndXl8Obg9dCgnAB/PXtobmjjG/5GFENY+axYd5Y2G5FbEOdZw7ODPzYYNQMc
ae5EXXM0swQzA5DdJz9jx0f5A82dB5uc6ZZsZ9QCC+FHQIwVDMyxDA3C5f3rggUC
e8j/VmhwJJG73Et7f2f31dhAC4x8B9P9EGfnTBYde17v765EL/KIFuSjNBNvrxAl
glZmvIdYhd4KINhSqfemeS3Ee5gnyE8mSeK3ha+tAoRx3MgRf1Wpr+7EzT5hTxk+
a6yQ1GlobIMF++LTc8Ce00TzzLQhsgE0ow6jnT/xge5bijxZFufHWRSJRkoC6lYT
e6ttIvEDumASRr4XZy74GyiV86nv1JgKic/cEHW4S8aOh7oCqw6B7Mk2H+HWut0q
MsFJGYjK8HWGSS6pk48F+NkksPNURHRPfy48gPzBwi4vtGrClRrTdAMYuXUv7bsL

Bug#786077: marked as done (opensesame: deprecation of python-support)

[Debian Bug Tracking System]

Your message dated Tue, 15 Dec 2015 15:54:33 +
with message-id 
and subject line Bug#786077: fixed in opensesame 0.27.4-2.1
has caused the Debian Bug report #786077,
regarding opensesame: 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.)


-- 
786077: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=786077
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: opensesame
Version: 0.27.4-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: opensesame
Source-Version: 0.27.4-2.1

We believe that the bug you reported is fixed in the latest version of
opensesame, 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.
Mattia Rizzolo  (supplier of updated opensesame 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, 13 Dec 2015 23:50:13 +
Source: opensesame
Binary: opensesame
Architecture: source
Version: 0.27.4-2.1
Distribution: unstable
Urgency: medium
Maintainer: Sebastiaan Mathot 
Changed-By: Mattia Rizzolo 
Description:
 opensesame - graphical experiment builder for the social sciences
Closes: 786077
Changes:
 opensesame (0.27.4-2.1) unstable; urgency=medium
 .
   * Non-maintainer upload.
   * Build using dh-python instead of python-support.  Closes: #786077
   * move the debian/upstream file to debian/upstream/metadata
Checksums-Sha1:
 ee21ab61ecbc81f5aedbf372ddd6bb2a427b921f 1932 opensesame_0.27.4-2.1.dsc
 b9ce54731696fbf9809d483309fcd7c80ff5021d 5211 opensesame_0.27.4-2.1.diff.gz
Checksums-Sha256:
 497eb50f67b561c26a0350bd45ce0362deb7252f0241aaf6d7562af8ce729335 1932 
opensesame_0.27.4-2.1.dsc
 ce7101b288fb48b8a37ede755579a8bc778218ddcc1a70a1472cd8acccf55748 5211 
opensesame_0.27.4-2.1.diff.gz
Files:
 d4ed726638017aecc9c4ed39faaef29b 1932 science extra opensesame_0.27.4-2.1.dsc
 fc5564973c7297e7865c8bf8756cfa4d 5211 science extra 
opensesame_0.27.4-2.1.diff.gz

-BEGIN PGP SIGNATURE-
Version: GnuPG v1

iQIcBAEBCAAGBQJWbgXUAAoJEEsEP825REVAYK0QAKY0TJKaQ2Ug2FDndAMmDI0h
D8jxbD+wIc8hX4HKDFS6EEKv8gc8Pege6Euy6hmGX52kysRj+3pjkqeijmPVd+ue
eygX6iDKeWt+uO76DFqVEDfPxC01Y0dkUReZJ0QXWuXjX36LFv6rNATo5Bk6DrHt
bwTuu217t1sj1maiLx9SLOuPegMS/qT+3dBzHZwGvnsTSU/FQ32AJxU7x2bItp9W
w+kVjggVGukEeiUX0fhF3tcsOWdkjGHIAtSl+zTYGD26GOmkc5LLjZDTxjJwbeDx
0Pl51DBjd6/+tz2nc0akC3MkGywd5kUff6fbucg6y/BzEC4yChckFU1OfqhUzUYJ
b8kPNGiKSm3aRddB5mfasd5xie8crtK/Qv5wjhYC2misExJG86Tshm0Wd6molYQO
lKadFka7rxVJ41YlbFeE7Abngu2/IsizSInjrJQEkNB8Hxnnmsp/gKPqexpvTkbI
DAXQpMs+y01dB0Be5K0Ts7dQHKs4qXXXg8djysJy9wfvscC3wOHGMj+akkpYZqkA
vujBrqlFJ7EY3fsMZc2VyPfHYYN48Ud62xvARb2R0qMKTESvmp5EfGEboLUVjmwW
ImFT04gnQKbVLmbJiCvS3VIZ47bXPv/tnEMbbFQuxG4aqSNKcRMxW8H+N9sruTk1
7I9RP6jw2oIoMaCOG2nP
=QwP/
-END PGP SIGNATURE End Message ---

Bug#786071: marked as done (py-asterisk: deprecation of python-support)

[Debian Bug Tracking System]

Your message dated Tue, 15 Dec 2015 15:55:19 +
with message-id 
and subject line Bug#786071: fixed in py-asterisk 0.5.3-1.1
has caused the Debian Bug report #786071,
regarding py-asterisk: 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.)


-- 
786071: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=786071
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: py-asterisk
Version: 0.5.3-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: py-asterisk
Source-Version: 0.5.3-1.1

We believe that the bug you reported is fixed in the latest version of
py-asterisk, 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.
Mattia Rizzolo  (supplier of updated py-asterisk 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, 14 Dec 2015 01:50:33 +
Source: py-asterisk
Binary: python-asterisk
Architecture: source
Version: 0.5.3-1.1
Distribution: unstable
Urgency: medium
Maintainer: Debian VoIP Maintainers 

Changed-By: Mattia Rizzolo 
Description:
 python-asterisk - Asterisk Manager API interface module for Python
Closes: 786071
Changes:
 py-asterisk (0.5.3-1.1) unstable; urgency=medium
 .
   * Non-maintainer upload.
   * Build-Depend on dh-python instead of python-support.  Closes: #786071
   * Bump Standard-Version to 3.9.6, no changes needed.
   * Rewrite debian/watch to use pypi.debian.org redirector.
Checksums-Sha1:
 6976d02b24c15df1dd5e86e480cb432264990d1e 2016 py-asterisk_0.5.3-1.1.dsc
 259f7462755074ef1f8844d80305734010082f3b 3400 
py-asterisk_0.5.3-1.1.debian.tar.xz
Checksums-Sha256:
 e603f7d2c06a4b40dfdfa3daeb4309c4a9e37f887bf4b102ae98c4a59a5f4d0d 2016 
py-asterisk_0.5.3-1.1.dsc
 81533c5705583629fd0ae078fb555079788693a39717d7b5a0ccb20c9d74a72c 3400 
py-asterisk_0.5.3-1.1.debian.tar.xz
Files:
 0c8c88639818ef812a89ea22acc4df65 2016 comm extra py-asterisk_0.5.3-1.1.dsc
 5ccaa2345d1fb7df2bde5a4905bcf676 3400 comm extra 
py-asterisk_0.5.3-1.1.debian.tar.xz

-BEGIN PGP SIGNATURE-
Version: GnuPG v1

iQIcBAEBCAAGBQJWbiEVAAoJEEsEP825REVAoXQP/R2Lu9Ygx/VuE5cAAMgoIg8j
esSsja+OHJp++buaExmInWwMX3ip5S+P8QU2s1jSOS92fAah6bvHROtBEc7nkAu5
Tp64m+7cawEnggwKQ/4gLEK8ZhTzvPlbBAza5Qp0IHu38LPZiR7pccc/ID6eFELb
JMQz53aYxqrZAHoGeqYzIGXDaZvzfctZEn9HWRU7wIaUdzfy5LWG9ZL0KMSU4Tkr
zegls2AwwVNUwg8pNi02oymU51/yN3VXiL1yMuCSxQWNsHMia8Pu7HQFJO6Q2JKw
e+DGtxDgZW/a7322AS83pktzwUOMYVoXCLpS1Ln9sbHaHMxdGIXZcaDCYkt1RYyu
yJ4fAboH+0rp1KyvsBWpJ2a8ZDxt08aSseEg5WQGApyoLtwvimIER4lvYKJzxg3r
JGZfDBQogDYQtDN5mkHxnDpwUD6pbaWkrRg77HWWrPlD/kOAqQhi6RhVQEAPIChY
Va7hgzV1knosWHzXFlK7FYPeNGsEGQzwcWJiO/FvgqLc/zD4u5lvAIEhMwSz7gRu
optj2MWUIt6Ozzie/RIa18IVxBiExDGM3PXSaJQ5lOx7tBiX9aHR9lcdEZvnBZzA

Bug#786165: marked as done (gbirthday: deprecation of python-support)

[Debian Bug Tracking System]

Your message dated Wed, 16 Dec 2015 01:34:05 +
with message-id 
and subject line Bug#786165: fixed in gbirthday 0.6.7-1.1
has caused the Debian Bug report #786165,
regarding gbirthday: 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.)


-- 
786165: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=786165
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: gbirthday
Version: 0.6.7-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: gbirthday
Source-Version: 0.6.7-1.1

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

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Wed, 16 Dec 2015 00:13:45 +
Source: gbirthday
Binary: gbirthday
Architecture: source
Version: 0.6.7-1.1
Distribution: experimental
Urgency: medium
Maintainer: Rolf Leggewie 
Changed-By: Mattia Rizzolo 
Description:
 gbirthday  - birthday reminder applet
Closes: 707843 786165
Changes:
 gbirthday (0.6.7-1.1) experimental; urgency=medium
 .
   * Non-maintainer upload.
   * Bump Standards-Version to 3.9.6: no changes needed.
   * Run wrap-and-sort.
   * Canonicalize Vcs-* fields.
   * Bump debhelper compat level to 9.
   * Stop recommending python-evolution.  Closes: #707843
   * Add a patch to allow gbirthday load from /usr/share/gbirthday if needed.
   * Build using dh-python instead of python-support.  Closes: #786165.
 Also, move all the files to the private location /usr/share/gbirthday, 
since
 this is an application.
   * Rewrite debian/watch to use github as source.
Checksums-Sha1:
 7042c01e36b9d469e1d53cc5247fd79db8bec97c 1904 gbirthday_0.6.7-1.1.dsc
 a1ee9cdc57c3de847d35ad87e61814ec0ed1face 3880 gbirthday_0.6.7-1.1.debian.tar.xz
Checksums-Sha256:
 8d552f6dcf3167eb50faf76b7f6c03087c03f94f43c52c81eb5ad4928f519ae1 1904 
gbirthday_0.6.7-1.1.dsc
 3cd5b9c89d579c4e96314d73803c7dec990ae1346ff84240f4f6e0601a9f84e1 3880 
gbirthday_0.6.7-1.1.debian.tar.xz
Files:
 851e2302b35e733b167666235399401a 1904 gnome extra gbirthday_0.6.7-1.1.dsc
 1ab61c6a98f752916a1d33c521a405b0 3880 gnome extra 
gbirthday_0.6.7-1.1.debian.tar.xz

-BEGIN PGP SIGNATURE-
Version: GnuPG v1

iQIcBAEBCAAGBQJWcK2sAAoJEEsEP825REVAQqcQAMMBrb/z0sW4OJsRzdkWOW8v
oqwGQIwfXQo+vn04S4UeZQtvJx5/Mj6aqFIdjlrp5p8ZUGBgLCVsZ1MGt2zkmJM/
HfgBmmNaA3467PsdD+VrWg1SoO55Ove5I2/9pntLV3fgpG4mdPX1N04ed0za9c5N
BXWmEnJVe3AmH7YiGCEvpBKDyuB3/+OWRjS8Xb26OodusTX2T1I/1Ii/5EYHtiAN
NnJfja6mRoGedwR5FUNpJdDJXGOxRkfiAnLB/EZfQg9m7FrvjIyXNVMFFnm5sAs9
d5ffzMf11fyzl2vjA/CBKvp2Xo8/2RMnw/SEQpUV75EpQwPt/Iea2L26PAFKXcPM
x82juuNMo2Gmf+F069gqme/SemOJzf0PBBroIfPYdX/xzh+UJLHTOb1d0VoCj2fT

Processed: subversion Debian ci: r1500 - src/1.9.x/debian

[Debian Bug Tracking System]

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

> tags 803725 pending
Bug #803725 [subversion] subversion: dump-load of a repository modifies verbose 
log output: M line lost
Added tag(s) pending.
> thanks
Stopping processing here.

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

Processed: tagging 808016

[Debian Bug Tracking System]

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

> tags 808016 + pending
Bug #808016 [src:bisonc++] bisonc++: FTBFS: [icmake/readlog, line 5] Error: 
conflicting operand types for fgets
Added tag(s) pending.
> thanks
Stopping processing here.

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

Bug#806487: syslinux: FTBFS: ldlinux.raw: write error

[Alex Andreotti]

I've the same error with buildroot's syslinux, the problem is in
the file prepcore.c, in particular:

if (fwrite(infile + start, 1, offset - start, f) != offset - start ||
fwrite(out, 1, outfile_len, f) != outfile_len || fclose(f))
error("write error");

given the code seems obvious an offset > start is expected, but a
printf show otherwise:

infile=0x1cf0240 start=31744 out=0x7f3db1d6e010 offset=0
outfile_len=57639

offset is initialized with pfx_compressed:

offset = get_32(>pfx_compressed);

something changed in some file format or some header?
or something about the arch being 64bit?
(objcopy doesn't fail)

-rw-r--r-- 1 alex alex 250589 Dec 15 13:05 ldlinux.lsr
-rw-r--r-- 1 alex alex 250589 Dec 15 13:05 ldlinux.lst
-rw-r--r-- 1 alex alex   4136 Dec 15 13:05 ldlinux.sec
-rwxr-xr-x 1 alex alex 687828 Dec 15 13:05 ldlinux.elf
-rw-r--r-- 1 alex alex 127464 Dec 15 13:05 ldlinux.raw
-rw-r--r-- 1 alex alex  0 Dec 15 13:05 ldlinux.bin

Bug#808038: linux-image-4.4.0-rc4-amd64: Fails to boot on kernel 4.4rc4

[Alexandre]

Package: linux-image-4.4.0-rc4-amd64
Version: 4.4~rc4-1~exp1
Severity: critical
Justification: breaks the whole system

Dear Maintainer,

Actually, i'm usging linux-image-4.3.0-trunk-amd64 on Dell XPS 13 9350. In
order to fix WiFi problem i would install linux-image-4.4.0rc4 but it makes it
impossible to boot my laptop.

I have this message before Luks ask passphrase :

Loading, please wait...
modprobe: module microcode not found in modules.dep
lvmetad is not active yet, using direct activation during sysinit
volume group "vg" not found
Cannot process volume group vg
/run/lvm/lvmetad.socket: connect failed: No such file or directory
WARNING: Failed to connect to lvmetad. Falling back to internal scanning.
Reading all physical volumes. This may take a while...
/run/lvm/lvmetad.socket: connect failed: No such file or directory
WARNING: Failed to connect to lvmetad. Falling back to internal scanning.
Reading all physical volumes. This may take a while...
/run/lvm/lvmetad.socket: connect failed: No such file or directory
WARNING: Failed to connect to lvmetad. Falling back to internal scanning.
Reading all physical volumes. This may take a while...
/run/lvm/lvmetad.socket: connect failed: No such file or directory
WARNING: Failed to connect to lvmetad. Falling back to internal scanning.
Reading all physical volumes. This may take a while...
/run/lvm/lvmetad.socket: connect failed: No such file or directory
WARNING: Failed to connect to lvmetad. Falling back to internal scanning.
Reading all physical volumes. This may take a while...
/run/lvm/lvmetad.socket: connect failed: No such file or directory
WARNING: Failed to connect to lvmetad. Falling back to internal scanning.




-- System Information:
Debian Release: stretch/sid
  APT prefers stable
  APT policy: (1001, 'stable'), (1, 'experimental')
Architecture: amd64 (x86_64)

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

Bug#808035: [src:linux] Local Modules Fail to Load

[David Baron]

Package: src:linux
Version: linux-image-4.3.0-1
Severity: grave

--- Please enter the report below this line. ---
Today's upgrades, nvidia-legacy drivers, dkms, and linux-image, headers 
4.3.0-1

On reboot to 4.3.0-1 kernel, get two messages "Local modules fail to load"
Everything else seems to play OK, no other messages on boot.
Kde GUI fails to start.

This may be a post-install problem, relating the nvidia-legacy-304xx  dkms, 
why I mention them.
Kernel objects were built, in their similar places to 4.2.0-1.
But, indeed, xorg log reports failure to load module>

Notes:

Despite the tiny / partition given by the installer, one does, indeed need 
space to have more than one kernel around. For just this type of eventuality!!

Got that good old "Failed to mount /usr" on 4.2.0-1 bootup. /proc/mounts shows 
/usr is, in fact, mounted rw.



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

Debian Release: stretch/sid
  500 unstableftp.us.debian.org 
  500 testing ftp.us.debian.org 
  500 sid linux.dropbox.com 
  500 lucid   ppa.launchpad.net 
1 experimentalftp.us.debian.org 

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

Package's Recommends field is empty.

Package's Suggests field is empty.

Bug#786227: python-django-rosetta: deprecation of python-support

[Michael Fladischer]

On Sat, 2015-12-12 at 18:52 +, Mattia Rizzolo wrote:
> Dear Michael,
> what's the current status of this package?
> It would be nice to have it uploaded.

I started working on it but I got stuck when I took a shot at running
the tests as they revealed some dependencies (e.g. microsofttranslator)
for which I have no interest in packaging them.

There is also the issue of a privacy breach because the code uses
JavaScript from www.google.com/jsapi.

The documentation source is also bogus as it contains minified JS-files 
for which I'd have too check if they can be symlinked by sphinxdoc.

And of course there are .pyc files in the source tarball from pypi
which lintian dislikes.

To be honest, I'm no longer interested in getting this package up to
DPMT standards as is a mess, even after I put a considerable amount of
time into polishing it up. Because of it's bad state I also got rid of
it in all of my projects ... 

Maybe someone other would like to give it a shot. I'll push my changes
but this leaves the package still at FTBFS.

Cheers,
-- 
Michael Fladischer
Fladi.at


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


smime.p7s
Description: S/MIME cryptographic signature

Bug#786165: gbirthday: deprecation of python-support

[Mattia Rizzolo]

On Tue, Dec 15, 2015 at 10:04:09AM +0100, Jérôme wrote:
> Hi.

Hi Jérôme!
Please note that nor me nor anybody else but the maintainer receive
emails from bug reports unless they have subscribed through the PTS or
to that specific bug.  So if you want to get the attention of somebody
in cases like this would be better if you keep the in Cc or such.

> To my knowledge, gbirthday is not worked on by anyone but myself.
> 
> The Debian package is maintained is Rolf Leggewie.

whatever, is always *great* when the upstream developer of a project
interacts in the Debian bug tracker!

> I'm clueless about Debian packaging, so I'm afraid I can't help with the
> python-support issue. I've paid a look at the wiki page about the
> migration to see if I could help, but that's too many new concepts to
> grasp.

Yeah, this bug is mostly about deprecating a debian tool (pysupport) in
favour of another (dh-python, or better, dh_python2 in this case).

I uploaded dozens of packages in the last 4 days removing it, but I'm
stuck at gbirthday because it insists at installing images in sitelib,
which used to be /usr/share/pyshared/gbirthday/ with pysupport, but now
we're migrating off that directory and going to
/usr/lib/python2.7/dist-packages, where images are not really welcome.

So, given that this is actually an application and not a python module
or such.

To do so, I'd like to upload what I attached as debdiff.
In particoular I'm adding a patch to let it load from
/usr/share/gbirthday.  Happens that the program doesn't load here, no UI
appears; since this is the same behaviour I have with the package
already in the archive that's not a regression, but given that uploading
such untested changes would be too bad, I'd like to ask you what do you
think of the patch attached as 'patch'.

> For the record, gbirthday has moved to GitHub:
> https://github.com/Jerome-github/gbirthday/. I should update the watch
> file (this seems feasible to me, but there is no need to do it as long
> as there is no new release).

I would update it, but I don't know which kind of filenames you'll use,
since there is no release already made there.

[...]
> - Unless somebody comes in, gbirthday won't evolve as it is and will
> probably be out of Stretch or the next Debian release due to
> dependencies deprecation. I'm happy if I'm wrong.

Not with *this* deprecation ;)

> - I hope to get a Qt version packageable for Stretch. Help welcome, of
> course.

Stretch will still release with python2, even if we definitely would
like to remove it for buster.



-- 
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  `-
diffstat for gbirthday-0.6.7 gbirthday-0.6.7

 changelog   |   15 +++
 compat  |2 +-
 control |   24 
 copyright   |6 +++---
 patches/load-from-private-dir.patch |   22 ++
 patches/series  |1 +
 rules   |4 ++--
 7 files changed, 60 insertions(+), 14 deletions(-)

diff -Nru gbirthday-0.6.7/debian/changelog gbirthday-0.6.7/debian/changelog
--- gbirthday-0.6.7/debian/changelog2014-06-19 09:21:13.0 +
+++ gbirthday-0.6.7/debian/changelog2015-12-15 13:22:30.0 +
@@ -1,3 +1,18 @@
+gbirthday (0.6.7-1.1) UNRELEASED; urgency=medium
+
+  * Non-maintainer upload.
+  * Bump Standards-Version to 3.9.6: no changes needed.
+  * Run wrap-and-sort.
+  * Canonicalize Vcs-* fields.
+  * Bump debhelper compat level to 9.
+  * Stop recommending python-evolution.  Closes: #707843
+  * Add a patch to allow gbirthday load from /usr/share/gbirthday if needed.
+  * Build using dh-python instead of python-support.  Closes: #786165.
+Also, move all the files to the private location /usr/share/gbirthday, 
since
+this is an application.
+
+ -- Mattia Rizzolo   Tue, 15 Dec 2015 12:58:11 +
+
 gbirthday (0.6.7-1) unstable; urgency=low
 
   * new upstream release 0.6.7
diff -Nru gbirthday-0.6.7/debian/compat gbirthday-0.6.7/debian/compat
--- gbirthday-0.6.7/debian/compat   2014-06-19 09:10:22.0 +
+++ gbirthday-0.6.7/debian/compat   2015-12-15 12:56:59.0 +
@@ -1 +1 @@
-7
+9
diff -Nru gbirthday-0.6.7/debian/control gbirthday-0.6.7/debian/control
--- gbirthday-0.6.7/debian/control  2014-06-19 09:10:22.0 +
+++ gbirthday-0.6.7/debian/control  2015-12-15 13:16:25.0 +
@@ -2,19 +2,27 @@
 Section: gnome
 Priority: extra
 Maintainer: Rolf Leggewie 
-Build-Depends: debhelper (>= 7.0.50~), python-nose, python-support, 
python-coverage, python-gtk2, 

Processed: severity of 808046 is grave

[Debian Bug Tracking System]

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

> severity 808046 grave
Bug #808046 [chromium] chromium: chrashes if chromium-l10n is not installed
Severity set to 'grave' from 'normal'
> thanks
Stopping processing here.

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

Processed: fixed 808081 in 1:9.8.4.dfsg.P1-6+nmu2+deb7u8, fixed 808081 in 1:9.9.5.dfsg-9+deb8u4

[Debian Bug Tracking System]

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

> fixed 808081 1:9.8.4.dfsg.P1-6+nmu2+deb7u8
Bug #808081 [src:bind9] bind9: CVE-2015-8000: Responses with a malformed class 
attribute can trigger an assertion failure in db.c
The source 'bind9' and version '1:9.8.4.dfsg.P1-6+nmu2+deb7u8' do not appear to 
match any binary packages
Marked as fixed in versions bind9/1:9.8.4.dfsg.P1-6+nmu2+deb7u8.
> fixed 808081 1:9.9.5.dfsg-9+deb8u4
Bug #808081 [src:bind9] bind9: CVE-2015-8000: Responses with a malformed class 
attribute can trigger an assertion failure in db.c
The source 'bind9' and version '1:9.9.5.dfsg-9+deb8u4' do not appear to match 
any binary packages
Marked as fixed in versions bind9/1:9.9.5.dfsg-9+deb8u4.
> thanks
Stopping processing here.

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

Processed: Re: Bug#808061: should rats be removed from the archive?

[Debian Bug Tracking System]

Processing control commands:

> reassign -1 ftp.debian.org
Bug #808061 [rats] should rats be removed from the archive?
Bug reassigned from package 'rats' to 'ftp.debian.org'.
No longer marked as found in versions rats/2.3-1.
Ignoring request to alter fixed versions of bug #808061 to the same values 
previously set
> severity -1 normal
Bug #808061 [ftp.debian.org] should rats be removed from the archive?
Severity set to 'normal' from 'serious'
> retitle -1 RM: rats -- ROM; unmaintained; dead upstream: low popcon; RC-buggy
Bug #808061 [ftp.debian.org] should rats be removed from the archive?
Changed Bug title to 'RM: rats -- ROM; unmaintained; dead upstream: low popcon; 
RC-buggy' from 'should rats be removed from the archive?'

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

Bug#808061: should rats be removed from the archive?

[Mattia Rizzolo]

Control: reassign -1 ftp.debian.org
Control: severity -1 normal
Control: retitle -1 RM: rats -- ROM; unmaintained; dead upstream: low popcon; 
RC-buggy

On Tue, Dec 15, 2015 at 02:55:41PM -0500, Alejandro Ríos Peña wrote:
> Hi,
> 
> You are right, please remove it.  I am currently Missing in Action, I will
> resign to the debian project as my last duty

Thanks for being so nice! ♥

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

Bug#807980: This bug can be closed

[Wayne Rowcliffe]

I was able to get things working correctly by moving libevdocument3-4 up in
the `/var/lib/dpkg/status` file so that it was next to `evince`. I have no
idea why that changed anything, but afterward it found the package fine.

-- Wayne

Bug#808046:

[Felipe Ortiz]

Hi,

Install chromium-l10n doesn't work for me

-- 
Felipe Ortiz C.

Bug#805746: aghermann: Fails to build with GSL 2

[Yaroslav Halchenko]

On Sat, 12 Dec 2015, andrei zavada wrote:

> Hey Yaroslav & Bas,

> Sorry for getting a bit late with an apparently simple fix. Here's
> version 1.0.7, which builds with gsl-2.0:
> http://johnhommer.com/academic/code/aghermann/source/deb/aghermann_1.0.7-1.dsc.

building now

cheers
-- 
Yaroslav O. Halchenko
Center for Open Neuroscience http://centerforopenneuroscience.org
Dartmouth College, 419 Moore Hall, Hinman Box 6207, Hanover, NH 03755
Phone: +1 (603) 646-9834   Fax: +1 (603) 646-1419
WWW:   http://www.linkedin.com/in/yarik

Processed: your mail

[Debian Bug Tracking System]

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

> forcemerge 808046 808077
Bug #808046 [chromium] chromium: chrashes if chromium-l10n is not installed
Bug #808077 [chromium] Crash when starting chromium, unless chromium-l10n is 
installed
Severity set to 'grave' from 'normal'
Merged 808046 808077
> thanks
Stopping processing here.

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

Bug#808045: missing license in debian/copyright

[Thorsten Alteholz]

Package: scala
Version: 2.11.6-3
Severity: serious
User: alteh...@debian.org
Usertags: ftp
X-Debbugs-CC: ftpmas...@ftp-master.debian.org
thanks

Dear Maintainer,

please add the missing Apache license of files in:
 scala-2.11.6/test/disabled/presentation/akka/src/akka/*
to debian/copyright.

Thanks!
  Thorsten

Bug#786227: python-django-rosetta: deprecation of python-support

[Mattia Rizzolo]

On Tue, Dec 15, 2015 at 01:45:05PM +0100, Michael Fladischer wrote:
> I started working on it but I got stuck when I took a shot at running
> the tests as they revealed some dependencies (e.g. microsofttranslator)
> for which I have no interest in packaging them.

Ok, so I've uploaded an actual NMU, targeting this specific issue, then
let's see...

> To be honest, I'm no longer interested in getting this package up to
> DPMT standards as is a mess, even after I put a considerable amount of
> time into polishing it up. Because of it's bad state I also got rid of
> it in all of my projects ... 

Well, that's not really just DPMT standards, I'd say it's usual Debian
standards :D (or at least, what we try for...)

> Maybe someone other would like to give it a shot. I'll push my changes
> but this leaves the package still at FTBFS.

Given that is in a so bad condition, and have a really really low
popcon, maybe consider to remove it from the archive?

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

Bug#808042: Should mumble-django be removed?

[Mattia Rizzolo]

Package: src:mumble-django
Version: 2.13-1
Severity: serious

Dear maintainer,

mumble-django is currently in a bad state:
 * reported to be uninstallable (and piuparts confirms) #765419
 * reported to break apache #793832
 * uses an obsolete lib (=> python-support) #786086

furthermore the popcon is low.

I therefore suggest to remove this package from the archive.

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

Bug#808043: linux-image-4.3.0-1-powerpc64: Fail to load md_mod with unknow symbol error

[Christian Marillat]

Package: src:linux
Version: 4.3.1-1
Severity: serious

Dear Maintainer,

Since 4.2.6-2 the Powerpc G5 doesn't start with an error 'unknow symbol in 
md_mod'

4.2.6-1 work fine.

/ is a RAID0 partition and kernels are in a normal partition in /boot

Christian

-- Package-specific info:
** Kernel log: boot messages should be attached

** Model information
revision: 1.1 (pvr 0044 0101)
revision: 1.1 (pvr 0044 0101)
revision: 1.1 (pvr 0044 0101)
revision: 1.1 (pvr 0044 0101)
platform: PowerMac
model   : PowerMac11,2
machine : PowerMac11,2
motherboard : PowerMac11,2 MacRISC4 Power Macintosh 

** PCI devices:
:00:0b.0 PCI bridge [0604]: Apple Inc. CPC945 PCIe Bridge [106b:005b] 
(prog-if 00 [Normal decode])
Control: I/O+ Mem+ BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR+ FastB2B- DisINTx-
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- TAbort- Reset- FastB2B-
PriDiscTmr- SecDiscTmr- DiscTmrStat- DiscTmrSERREn-
Capabilities: 

:0a:00.0 VGA compatible controller [0300]: NVIDIA Corporation NV43 [GeForce 
6600] [10de:0141] (rev a2) (prog-if 00 [VGA controller])
Subsystem: NVIDIA Corporation Device [10de:0010]
Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx-
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- 

0001:00:00.0 Host bridge [0600]: Apple Inc. U4 HT Bridge [106b:0074]
Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx-
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- 

0001:00:01.0 PCI bridge [0604]: Broadcom BCM5780 [HT2000] PCI-X bridge 
[1166:0130] (rev a3) (prog-if 00 [Normal decode])
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR+ FastB2B- DisINTx-
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- TAbort- Reset- FastB2B-
PriDiscTmr- SecDiscTmr+ DiscTmrStat- DiscTmrSERREn-
Capabilities: 

0001:00:02.0 PCI bridge [0604]: Broadcom BCM5780 [HT2000] PCI-X bridge 
[1166:0130] (rev a3) (prog-if 00 [Normal decode])
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR+ FastB2B- DisINTx-
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- TAbort- Reset- FastB2B-
PriDiscTmr- SecDiscTmr+ DiscTmrStat- DiscTmrSERREn-
Capabilities: 

0001:00:03.0 PCI bridge [0604]: Broadcom BCM5780 [HT2000] PCI-Express Bridge 
[1166:0132] (rev a3) (prog-if 00 [Normal decode])
Control: I/O+ Mem+ BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR+ FastB2B- DisINTx-
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- TAbort- 
Reset- FastB2B-
PriDiscTmr- SecDiscTmr- DiscTmrStat- DiscTmrSERREn-
Capabilities: 

0001:00:04.0 PCI bridge [0604]: Broadcom BCM5780 [HT2000] PCI-Express Bridge 
[1166:0132] (rev a3) (prog-if 00 [Normal decode])
Control: I/O+ Mem+ BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR+ FastB2B- DisINTx-
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- TAbort- 
Reset- FastB2B-
PriDiscTmr- SecDiscTmr- DiscTmrStat- DiscTmrSERREn-
Capabilities: 

0001:00:05.0 PCI bridge [0604]: Broadcom BCM5780 [HT2000] PCI-Express Bridge 
[1166:0132] (rev a3) (prog-if 00 [Normal decode])
Control: I/O+ Mem+ BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR+ FastB2B- DisINTx-
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- TAbort- 
Reset- FastB2B-
PriDiscTmr- SecDiscTmr- DiscTmrStat- DiscTmrSERREn-
Capabilities: 

0001:00:06.0 PCI bridge [0604]: Broadcom BCM5780 [HT2000] PCI-Express Bridge 
[1166:0132] (rev a3) (prog-if 00 [Normal decode])
Control: I/O+ Mem+ BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR+ FastB2B- DisINTx-
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- TAbort- 
Reset- FastB2B-
PriDiscTmr- SecDiscTmr- DiscTmrStat- DiscTmrSERREn-
Capabilities: 

0001:00:07.0 PCI bridge [0604]: Apple Inc. Shasta PCI Bridge [106b:0053] 
(prog-if 00 [Normal decode])
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR+ FastB2B- DisINTx-
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- TAbort- 
Reset- FastB2B-
PriDiscTmr- SecDiscTmr- DiscTmrStat- DiscTmrSERREn-
Capabilities: 

0001:00:08.0 PCI bridge [0604]: Apple Inc. Shasta PCI Bridge [106b:0054] 
(prog-if 00 [Normal decode])
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx-
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast