Bug#805917: marked as done (nvidia-graphics-drivers: CVE-2015-7869 Unsanitized User Mode Input)

[Debian Bug Tracking System]

Your message dated Mon, 14 Dec 2015 23:32:06 +
with message-id 
and subject line Bug#805917: fixed in nvidia-graphics-drivers 340.96-1
has caused the Debian Bug report #805917,
regarding nvidia-graphics-drivers: CVE-2015-7869 Unsanitized User Mode Input
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.)


-- 
805917: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=805917
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: nvidia-graphics-drivers
Version: 304.22-1
Severity: serious
Tags: security

http://nvidia.custhelp.com/app/answers/detail/a_id/3808
http://people.canonical.com/~ubuntu-security/cve/2015/CVE-2015-7869.html

[...] This report also details an advisory regarding integer overflow issues
in the underlying kernel mode driver.

[...] The integer overflow issues affect both Windows and Linux-based GPU
drivers. These issues affect all GPU products and are not specific to
any GPU class device.


Andreas
--- End Message ---
--- Begin Message ---
Source: nvidia-graphics-drivers
Source-Version: 340.96-1

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

Debian distribution maintenance software
pp.
Andreas Beckmann  (supplier of updated nvidia-graphics-drivers 
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 10:17:49 +0100
Source: nvidia-graphics-drivers
Binary: nvidia-driver nvidia-driver-bin nvidia-glx xserver-xorg-video-nvidia 
libgl1-nvidia-glx libgl1-nvidia-glx-i386 libegl1-nvidia libgles1-nvidia 
libgles2-nvidia libnvidia-eglcore nvidia-alternative nvidia-kernel-dkms 
nvidia-kernel-source nvidia-vdpau-driver nvidia-smi nvidia-cuda-mps libcuda1 
libcuda1-i386 libnvidia-compiler libnvcuvid1 libnvidia-encode1 libnvidia-ifr1 
libnvidia-fbc1 libnvidia-ml1 nvidia-opencl-common nvidia-opencl-icd 
nvidia-libopencl1 nvidia-detect
Architecture: source
Version: 340.96-1
Distribution: jessie
Urgency: medium
Maintainer: Debian NVIDIA Maintainers 
Changed-By: Andreas Beckmann 
Description:
 libcuda1   - NVIDIA CUDA Driver Library
 libcuda1-i386 - NVIDIA CUDA 32-bit runtime library${nvidia:LegacyDesc}
 libegl1-nvidia - NVIDIA binary EGL libraries${nvidia:LegacyDesc}
 libgl1-nvidia-glx - NVIDIA binary OpenGL libraries${nvidia:LegacyDesc}
 libgl1-nvidia-glx-i386 - NVIDIA binary OpenGL 32-bit 
libraries${nvidia:LegacyDesc}
 libgles1-nvidia - NVIDIA binary OpenGL|ES 1.x libraries${nvidia:LegacyDesc}
 libgles2-nvidia - NVIDIA binary OpenGL|ES 2.x libraries${nvidia:LegacyDesc}
 libnvcuvid1 - NVIDIA CUDA Video Decoder runtime library
 libnvidia-compiler - NVIDIA runtime compiler library
 libnvidia-eglcore - NVIDIA binary EGL core libraries${nvidia:LegacyDesc}
 libnvidia-encode1 - NVENC Video Encoding runtime library
 libnvidia-fbc1 - NVIDIA OpenGL-based Framebuffer Capture runtime library
 libnvidia-ifr1 - NVIDIA OpenGL-based Inband Frame Readback runtime library
 libnvidia-ml1 - NVIDIA Management Library (NVML) runtime library
 nvidia-alternative - allows the selection of NVIDIA as GLX provider
 nvidia-cuda-mps - NVIDIA CUDA Multi Process Service (MPS)
 nvidia-detect - NVIDIA GPU detection utility
 nvidia-driver - NVIDIA metapackage${nvidia:LegacyDesc}
 nvidia-driver-bin - NVIDIA driver support binaries${nvidia:LegacyDesc}
 nvidia-glx - transition to ${nvidia}-driver
 nvidia-kernel-dkms - NVIDIA binary kernel module DKMS 
source${nvidia:LegacyDesc}
 nvidia-kernel-source - NVIDIA binary kernel module source${nvidia:LegacyDesc}
 nvidia-libopencl1 - NVIDIA OpenCL ICD Loader library
 nvidia-opencl-common - NVIDIA OpenCL driver
 nvidia-opencl-icd - NVIDIA OpenCL installable client driver (ICD)
 nvidia-smi - NVIDIA System Management Interface
 nvidia-vdpau-driver - Video Decode and Presentation API for Unix - NVIDIA 
driver
 xserver-xorg-video-nvidia - NVIDIA binary Xorg driver${nvidia:LegacyDesc}
Closes: 805917
Changes:
 nvidia-graphics-drivers (340.96-1) jessie; urgency=medium
 

Bug#798162: marked as done (node-leveldown: FTBFS when rebuilt against libleveldb1v5 (GCC-5 transition))

[Debian Bug Tracking System]

Your message dated Tue, 15 Dec 2015 00:35:19 +
with message-id 
and subject line Bug#798162: fixed in node-leveldown 1.4.1+dfsg-1
has caused the Debian Bug report #798162,
regarding node-leveldown: FTBFS when rebuilt against libleveldb1v5 (GCC-5 
transition)
to be marked as done.

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

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


-- 
798162: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=798162
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: node-leveldown
Version: 1.0.0+dfsg-1
Severity: serious
Tags: sid stretch
User: debian-...@lists.debian.org
Usertags: libstdc++-cxx11

Hi,

The node-leveldown package FTBFS when we attempted to rebuild it
against libleveldb1v5 for the GCC-5 transition:

"""
gyp info spawn args [ 'BUILDTYPE=Release', '-C', 'build' ]
make[2]: Entering directory '/«BUILDDIR»/node-leveldown-1.0.0+dfsg/build'
  CXX(target) Release/obj.target/leveldown/src/batch.o
[... more issues here ...]
In file included from ../src/database.h:18:0,
 from ../src/batch.cc:5:
../src/leveldown.h:78:28: error: 'NanGetCurrentContext' was not declared in 
this scope
   NanGetCurrentContext()->Global(), callback, argc, argv);
^
../src/batch.cc:146:5: note: in expansion of macro 'LD_RUN_CALLBACK'
 LD_RUN_CALLBACK(v8::Local::Cast(args[0]), 0, NULL);
 ^
../src/leveldown.h:78:61: error: 'NanMakeCallback' was not declared in this 
scope
   NanGetCurrentContext()->Global(), callback, argc, argv);
 ^
../src/batch.cc:146:5: note: in expansion of macro 'LD_RUN_CALLBACK'
 LD_RUN_CALLBACK(v8::Local::Cast(args[0]), 0, NULL);
 ^
../src/batch.cc:149:22: error: 'NanReturnUndefined' was not declared in this 
scope
   NanReturnUndefined();
  ^
make[2]: *** [Release/obj.target/leveldown/src/batch.o] Error 1
leveldown.target.mk:88: recipe for target 
'Release/obj.target/leveldown/src/batch.o' failed
"""

Thanks,
~Niels
--- End Message ---
--- Begin Message ---
Source: node-leveldown
Source-Version: 1.4.1+dfsg-1

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

Debian distribution maintenance software
pp.
Felipe Sateler  (supplier of updated node-leveldown 
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 21:21:33 -0300
Source: node-leveldown
Binary: node-leveldown
Architecture: source
Version: 1.4.1+dfsg-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Javascript Maintainers 

Changed-By: Felipe Sateler 
Description:
 node-leveldown - LevelDB bindings - Node.js module
Closes: 798162
Changes:
 node-leveldown (1.4.1+dfsg-1) unstable; urgency=medium
 .
   * Team upload
   * New upstream release
 - Fix build against newer nan. Closes: #798162
   * Bump dependency versions
Checksums-Sha1:
 d586f9a6f33f0072fe363d9567571959fcc9b32c 2127 node-leveldown_1.4.1+dfsg-1.dsc
 96e38cb1bbdebfc0ac67d02289ae9651b55fa58f 39387 
node-leveldown_1.4.1+dfsg.orig.tar.gz
 0ef57cba03c08415d1d8faa1113af79ec562ae62 3852 
node-leveldown_1.4.1+dfsg-1.debian.tar.xz
Checksums-Sha256:
 9b519b9c6b8f7e680a52d968958d8c030308cdabb4dc746323a32ba5c7b6b3f5 2127 
node-leveldown_1.4.1+dfsg-1.dsc
 48e12d1e768518d821666d52bebd4377dc065e84cdc2d8984a836c9bc1fa60cc 39387 
node-leveldown_1.4.1+dfsg.orig.tar.gz
 155305e83dd310f639325b9b07e2f25de0acebf1ded51fd2eceed4ff73852f60 3852 
node-leveldown_1.4.1+dfsg-1.debian.tar.xz
Files:
 9786e327b04f39a092b81f5ac825e053 2127 web extra node-leveldown_1.4.1+dfsg-1.dsc
 dcbb6952b49c0fd66e213d4daa399ddf 39387 web extra 
node-leveldown_1.4.1+dfsg.orig.tar.gz
 a4e5894615d34a81dd3949fe32234b34 3852 web extra 
node-leveldown_1.4.1+dfsg-1.debian.tar.xz

-BEGIN PGP SIGNATURE-
Version: GnuPG v1

iQIcBAEBCAAGBQJWb11nAAoJEKO6uuJAjdbPCA8P/02v+E4Cx/Gw/iIQJTkNChar
aihRxoLCZJzXWA8k9sbiOI4ml9P3Q7EF02zAtCZ9NmbT9cE8oLYu1nXcFFc0mgZV

Bug#796294: tgif: diff for NMU version 1:4.2.5-1.3

[Carlo Segre]

This is fine.  I am not sure when I will get to updating the package.

Carlo

On Mon, 14 Dec 2015, Mattia Rizzolo wrote:


Control: tags 796294 + patch
Control: tags 796294 + pending

Dear maintainer,

I've prepared an NMU for tgif (versioned as 1:4.2.5-1.3) and
uploaded it to DELAYED/2. Please feel free to tell me if I
should delay it longer.

Regards.




--
Carlo U. Segre -- Duchossois Leadership Professor of Physics
Director, Center for Synchrotron Radiation Research and Instrumentation
Illinois Institute of Technology
Voice: 312.567.3498Fax: 312.567.3494
se...@iit.edu   http://phys.iit.edu/~segre   se...@debian.org

Bug#796294: tgif: diff for NMU version 1:4.2.5-1.3

[Mattia Rizzolo]

On Mon, Dec 14, 2015 at 06:13:26PM -0600, Carlo Segre wrote:
> This is fine.  I am not sure when I will get to updating the package.

Oh, this is cool, thanks :)

Then I rescheduled the NMU to a 0-day.

Thank for being so well-disposed!

-- 
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#807979: [Debian-med-packaging] Bug#807979: bamtools cannot open bam files on big endian systems

[Afif Elghraoui]

Control: severity -1 important
Control: forwarded -1 https://github.com/pezmaster31/bamtools/issues/113


Hi, Dominique,

على الإثنين 14 كانون الأول 2015 ‫18:09، كتب Dominique Belhachemi:
> Package: bamtools
> Version: 2.4.0+dfsg-2
> Severity: grave
> 
> 
> This bug affects big endian systems (mips, powerpc, ...) . It is not
> possible to handle bam files.
>

I'm reducing the severity because it does not appear to affect *all*
users (only users on a subset of architectures) based on your description.

Many thanks for your bug report

regards
Afif

-- 
Afif Elghraoui | عفيف الغراوي
http://afif.ghraoui.name

Processed: Re: [Debian-med-packaging] Bug#807979: bamtools cannot open bam files on big endian systems

[Debian Bug Tracking System]

Processing control commands:

> severity -1 important
Bug #807979 [bamtools] bamtools cannot open bam files on big endian systems
Severity set to 'important' from 'grave'
> forwarded -1 https://github.com/pezmaster31/bamtools/issues/113
Bug #807979 [bamtools] bamtools cannot open bam files on big endian systems
Set Bug forwarded-to-address to 
'https://github.com/pezmaster31/bamtools/issues/113'.

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

Bug#807980: libevdocument3-4: Fails to install without specifying an error

[Wayne Rowcliffe]

Package: libevdocument3-4
Version: 3.18.2-1
Severity: grave
Justification: renders package unusable

Dear Maintainer,

I had an upgrade that failed to complete. It said evince was partially
installed. So I ran `apt-get install -f` and the problem persisted.

I ran `apt-get remove libevdocument3-4 evince libevview3-3` and was then
able to complete the upgrade and afterwards install several other
packages.

I then tried to reinstall evince.

apt-get install evince
Reading package lists... Done
Building dependency tree
Reading state information... Done
The following additional packages will be installed:
  libevdocument3-4 libevview3-3

The following NEW packages will be installed:
  evince libevdocument3-4 libevview3-3
0 upgraded, 3 newly installed, 0 to remove and 0 not
upgraded.
Need to get 0 B/2,304 kB of archives.
After this operation, 3,591 kB of additional disk space will
be used.
Do you want to continue? [Y/n] y
(Reading database ... 311103 files and directories currently
installed.)
Preparing to unpack .../libevdocument3-4_3.18.2-1_amd64.deb

Unpacking libevdocument3-4 (3.18.2-1) over (3.18.2-1) ...
Selecting previously unselected package libevview3-3.
Preparing to unpack .../libevview3-3_3.18.2-1_amd64.deb ...
Unpacking libevview3-3 (3.18.2-1) ...
Selecting previously unselected package evince.
Preparing to unpack .../evince_3.18.2-1_amd64.deb ...
Unpacking evince (3.18.2-1) ...
Processing triggers for libc-bin (2.19-22) ...
Setting up libevdocument3-4 (3.18.2-1) ...
Setting up libevview3-3 (3.18.2-1) ...
Setting up evince (3.18.2-1) ...
Processing triggers for libc-bin (2.19-22) ...

That seemed to be successful.

However:

apt-get install
Reading package lists... Done
Building dependency tree
Reading state information... Done
You might want to run 'apt-get -f install' to correct these.
The following packages have unmet dependencies:
 evince : Depends: libevdocument3-4 (= 3.18.2-1) but it is not installed
 libevview3-3 : Depends: libevdocument3-4 (>= 3.18.0) but it is not
 installed
E: Unmet dependencies. Try using -f.

and

apt-cache policy libevdocument3-4
libevdocument3-4:
  Installed: (none)
  Candidate: 3.18.2-1
  Version table:
 3.18.2-1 700
   700 http://ftp.us.debian.org/debian testing/main amd64 Packages
   650 http://ftp.us.debian.org/debian unstable/main amd64 Packages

I am not sure what the issue is but I filed it under evince since that
is the package causing me issues.

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

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

Versions of packages libevdocument3-4 depends on:
ii  libarchive13 3.1.2-11+b1
ii  libatk1.0-0  2.18.0-1
ii  libc62.19-22
ii  libcairo-gobject21.14.4-1
ii  libcairo21.14.4-1
ii  libdjvulibre21   3.5.27.1-5
ii  libgcc1  1:5.2.1-23
ii  libgdk-pixbuf2.0-0   2.32.2-1
ii  libglib2.0-0 2.46.2-1
ii  libgtk-3-0   3.18.5-1
ii  libgxps2 0.2.3.2-1
ii  libkpathsea6 2015.20150524.37493-7
ii  libpango-1.0-0   1.38.1-1
ii  libpangocairo-1.0-0  1.38.1-1
ii  libpoppler-glib8 0.26.5-4
ii  libspectre1  0.2.7-3
ii  libstdc++6   5.2.1-23
ii  libtiff5 4.0.5-1
ii  libxml2  2.9.2+zdfsg1-4
ii  zlib1g   1:1.2.8.dfsg-2+b1

libevdocument3-4 recommends no packages.

libevdocument3-4 suggests no packages.

-- no debconf information

Processed: Re: [Debian-med-packaging] Bug#807979: bamtools cannot open bam files on big endian systems

[Debian Bug Tracking System]

Processing control commands:

> severity -1 grave
Bug #807979 [bamtools] bamtools cannot open bam files on big endian systems
Severity set to 'grave' from 'important'

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

Bug#802087: marked as done (node-groove: FTBFS: gn_file.h:8:40: error: expected class-name before ‘{’ token)

[Debian Bug Tracking System]

Your message dated Tue, 15 Dec 2015 00:25:07 +
with message-id 
and subject line Bug#802087: fixed in node-groove 2.5.0-1
has caused the Debian Bug report #802087,
regarding node-groove: FTBFS: gn_file.h:8:40: error: expected class-name before 
‘{’ token
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.)


-- 
802087: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=802087
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: node-groove
Version: 2.2.6-2
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:

gyp info spawn make
gyp info spawn args [ 'BUILDTYPE=Release', '-C', 'build' ]
make[2]: Entering directory '/node-groove-2.2.6/build'
  CXX(target) Release/obj.target/groove/src/groove.o
In file included from ../src/groove.cc:3:0:
../src/gn_file.h:8:40: error: expected class-name before ‘{’ token
 class GNFile : public node::ObjectWrap {
^
../src/gn_file.h:13:53: error: ‘Arguments’ in namespace ‘v8’ does not name a 
type
 static v8::Handle Open(const v8::Arguments& args);
 ^
../src/gn_file.h:21:52: error: ‘Arguments’ in namespace ‘v8’ does not name a 
type
 static v8::Handle New(const v8::Arguments& args);
^
../src/gn_file.h:24:27: error: ‘AccessorInfo’ in namespace ‘v8’ does not name a 
type
 const v8::AccessorInfo );
   ^
../src/gn_file.h:26:27: error: ‘AccessorInfo’ in namespace ‘v8’ does not name a 
type
 const v8::AccessorInfo );
   ^

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

-- System Information:
Debian Release: stretch/sid
APT prefers unstable
APT policy: (500, 'unstable')
Architecture: amd64 (x86_64)
--- End Message ---
--- Begin Message ---
Source: node-groove
Source-Version: 2.5.0-1

We believe that the bug you reported is fixed in the latest version of
node-groove, 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.
Felipe Sateler  (supplier of updated node-groove 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 21:05:55 -0300
Source: node-groove
Binary: node-groove
Architecture: source amd64
Version: 2.5.0-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Javascript Maintainers 

Changed-By: Felipe Sateler 
Description:
 node-groove - bindings to libgroove - generic music player library - Node.js mo
Closes: 802087
Changes:
 node-groove (2.5.0-1) unstable; urgency=medium
 .
   * New upstream release
 - Fix build with nan 2. Closes: #802087
 - Drop patch applied upstream
 - Replace node with nodejs in bindings.gyp
   * Bump standards version
   * Fix typo in copyright file
Checksums-Sha1:
 af4dcd6b80781a92e3938a9d7de04ac739866983 2237 node-groove_2.5.0-1.dsc
 d11207aab9faa74b94ae2a6132c11e7f7af831b5 104530 node-groove_2.5.0.orig.tar.gz
 b431fa7daf8109e444113481a77e46d0e53c7bba 3148 node-groove_2.5.0-1.debian.tar.xz
 3e2567ad7928295b9357414ef2140234931bde30 44598 node-groove_2.5.0-1_amd64.deb
Checksums-Sha256:
 65b31b2ff6d856969139c6ec9899c36d90065aff4c8a46976b803fcc8bdf2947 2237 
node-groove_2.5.0-1.dsc
 b6b49caec2d492013eb8e0c7eb8a02969e6652d4d0884c8f5db093176111 104530 
node-groove_2.5.0.orig.tar.gz
 d4eff1b11719ae47e471068c45ff843305d12f4e631b647e9b145545c799 3148 
node-groove_2.5.0-1.debian.tar.xz
 11f868d15222781dae9de57353159b8c87b40c9fcaf94669b36cfd9d444d7c95 44598 
node-groove_2.5.0-1_amd64.deb
Files:
 f5662c0b261ae3ea33a6718f6e776c54 2237 web extra node-groove_2.5.0-1.dsc
 5df7ff35c6766f9957d139ad0725fdb7 104530 web extra node-groove_2.5.0.orig.tar.gz
 

Bug#802139: marked as done (screenlets: FTBFS: chmod: missing operand after '644')

[Debian Bug Tracking System]

Your message dated Tue, 15 Dec 2015 00:35:37 +
with message-id 
and subject line Bug#802139: fixed in screenlets 0.1.2-8.1
has caused the Debian Bug report #802139,
regarding screenlets: FTBFS: chmod: missing operand after '644'
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.)


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

dh_shlibdeps -pscreenlets
find debian/screenlets/usr/share/screenlets-manager/ -name "*.png" -perm 755 | 
xargs chmod 644
chmod: missing operand after ‘644’
Try 'chmod --help' for more information.
debian/rules:29: recipe for target 'binary-predeb/screenlets' failed
make: *** [binary-predeb/screenlets] Error 123
dpkg-buildpackage: error: debian/rules binary gave error exit status 2

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

-- System Information:
Debian Release: stretch/sid
APT prefers unstable
APT policy: (500, 'unstable')
Architecture: amd64 (x86_64)
--- End Message ---
--- Begin Message ---
Source: screenlets
Source-Version: 0.1.2-8.1

We believe that the bug you reported is fixed in the latest version of
screenlets, 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.
Mattia Rizzolo  (supplier of updated screenlets 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 00:17:44 +
Source: screenlets
Binary: screenlets screenlets-doc
Architecture: source
Version: 0.1.2-8.1
Distribution: unstable
Urgency: medium
Maintainer: Julien Lavergne 
Changed-By: Mattia Rizzolo 
Description:
 screenlets - Widget-like mini-applications for GNOME
 screenlets-doc - Widget-like mini-applications for GNOME - Documentation 
package
Closes: 786009 802139
Changes:
 screenlets (0.1.2-8.1) unstable; urgency=medium
 .
   * Non-maintainer upload.
   * Fix FTBFS.  Closes: #802139
   * Build using dh-python instead of python-support.  Closes: #786009
Checksums-Sha1:
 864da8ec2bff250ae6b62ee5edd3d4f413dfa70c 2073 screenlets_0.1.2-8.1.dsc
 4995dd874e09dae46cf71a6617d1bd885724c124 27272 screenlets_0.1.2-8.1.diff.gz
Checksums-Sha256:
 22a26499c2e64b5d949bd0c90557bd8dcd98ff135db5b15c1573a2d862d98d98 2073 
screenlets_0.1.2-8.1.dsc
 2502470c262316a42c32d1cf694d4f03a23276ea2154ed5cec9afe2bf7bcea89 27272 
screenlets_0.1.2-8.1.diff.gz
Files:
 1a69bd578eb8ac43adc3cd6d98d5cd2b 2073 gnome optional screenlets_0.1.2-8.1.dsc
 32b69e39d9607c942867a1cb0ce98a91 27272 gnome optional 
screenlets_0.1.2-8.1.diff.gz

-BEGIN PGP SIGNATURE-
Version: GnuPG v1

iQIcBAEBCAAGBQJWb1y9AAoJEEsEP825REVAD8YP/1R3Rc3SRvi5ZW+QKQ6Q2XvP
QIuP+oxn5EDVkVUnhQHnniSUZKBARot8GAUBH+hA1Dm7YXsdiOtGVAu5UjmvEA33
kY7lmSAgBY84lPgEFsc8A9Dju7nYXMdP4KSnMyqo2Gm0FLDWOkpdHt9/HIuWNojK
eaPF8XL4g/4cvjlRNfy/f+61r4f65IwTV4kWE2qbVklYnH/fkEcw7XCb0iyc8Ezx
xZtNCnQfjYy77ZYp3FHhdoMHckdIgaicwN32SRcEkiBI84G/WTrSzk+TzA59rlKR
VcZDyMxkEkdpPg9hFNo5w3xNQfV7ESG63avvBVtj4XN/zoKkDjxu0iKKbpvgXUa5
4pe1AX1Ge9+X/kaCbHc7z9BBFfQntfxYXPqqVbAi0GKf8AbolV2H7c07wY2ZtKyj
ZPPsXxipJCuxa4JrFlf1ISOm8/LfR+sgVUs62vQEseTvE9dUgisGs3kSS8KBnZs9
Y/eI8RZ0oojusyHRLvK4yQlej+BWG4BuQxmf5ZIdW2dghYq508CW8QReBDrnMCOe
bBXlXOROI85qkucr5zUAgp7cG7oQdcu3b6BYjRt75SZPnrw5oUeyFCh3p9OYwAXf
OUzWNf1sZuLTwKtZQCXacjppyUNp5Jt3XyyWky1QPcUTUohrSMzN+bqkNiZn5go6
vDHEqF5xmb5NL6GZU6Xa
=Ug0r
-END PGP SIGNATURE End Message ---

Bug#807979: bamtools cannot open bam files on big endian systems

[Dominique Belhachemi]

Package: bamtools
Version: 2.4.0+dfsg-2
Severity: grave


This bug affects big endian systems (mips, powerpc, ...) . It is not
possible to handle bam files.

Here is a quick test case:

$ bamtools count -in test.bam
bamtools count ERROR: could not open input BAM file(s)... Aborting.


I filed a bug report upstream with a detailed explanation.
https://github.com/pezmaster31/bamtools/issues/113


Best
-Dominique

Bug#805917: marked as done (nvidia-graphics-drivers: CVE-2015-7869 Unsanitized User Mode Input)

[Debian Bug Tracking System]

Your message dated Mon, 14 Dec 2015 23:33:22 +
with message-id 
and subject line Bug#805917: fixed in nvidia-graphics-drivers 304.131-1
has caused the Debian Bug report #805917,
regarding nvidia-graphics-drivers: CVE-2015-7869 Unsanitized User Mode Input
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.)


-- 
805917: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=805917
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: nvidia-graphics-drivers
Version: 304.22-1
Severity: serious
Tags: security

http://nvidia.custhelp.com/app/answers/detail/a_id/3808
http://people.canonical.com/~ubuntu-security/cve/2015/CVE-2015-7869.html

[...] This report also details an advisory regarding integer overflow issues
in the underlying kernel mode driver.

[...] The integer overflow issues affect both Windows and Linux-based GPU
drivers. These issues affect all GPU products and are not specific to
any GPU class device.


Andreas
--- End Message ---
--- Begin Message ---
Source: nvidia-graphics-drivers
Source-Version: 304.131-1

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

Debian distribution maintenance software
pp.
Andreas Beckmann  (supplier of updated nvidia-graphics-drivers 
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 09:53:49 +0100
Source: nvidia-graphics-drivers
Binary: nvidia-glx xserver-xorg-video-nvidia nvidia-glx-ia32 libgl1-nvidia-glx 
libxvmcnvidia1 libgl1-nvidia-glx-ia32 nvidia-alternative nvidia-kernel-dkms 
nvidia-kernel-source nvidia-vdpau-driver nvidia-vdpau-driver-ia32 nvidia-smi 
libcuda1 libcuda1-ia32 libnvidia-compiler libnvidia-compiler-ia32 libnvcuvid1 
libnvidia-ml1 nvidia-opencl-common nvidia-opencl-icd nvidia-opencl-icd-ia32 
nvidia-libopencl1 nvidia-libopencl1-ia32 libgl1-nvidia-alternatives 
libgl1-nvidia-alternatives-ia32 libglx-nvidia-alternatives nvidia-detect
Architecture: source amd64
Version: 304.131-1
Distribution: wheezy
Urgency: medium
Maintainer: Debian NVIDIA Maintainers 
Changed-By: Andreas Beckmann 
Description: 
 libcuda1   - NVIDIA CUDA runtime library
 libcuda1-ia32 - please switch to multiarch libcuda1:i386
 libgl1-nvidia-alternatives - transition libGL.so* diversions to 
glx-alternative-nvidia
 libgl1-nvidia-alternatives-ia32 - simplifies replacing MESA libGL with GPU 
vendor libraries (32-bit
 libgl1-nvidia-glx - NVIDIA binary OpenGL libraries${nvidia:LegacyDesc}
 libgl1-nvidia-glx-ia32 - please switch to multiarch 
libgl1-nvidia${nvidia:Legacy}-glx:i386
 libglx-nvidia-alternatives - transition libgl.so diversions to 
glx-alternative-nvidia
 libnvcuvid1 - NVIDIA CUDA nvcuvid runtime library
 libnvidia-compiler - NVIDIA runtime compiler library
 libnvidia-compiler-ia32 - please switch to multiarch libnvidia-compiler:i386
 libnvidia-ml1 - NVIDIA management library (NVML) runtime library
 libxvmcnvidia1 - NVIDIA binary XvMC library${nvidia:LegacyDesc}
 nvidia-alternative - allows the selection of NVIDIA as GLX provider
 nvidia-detect - NVIDIA GPU detection utility
 nvidia-glx - NVIDIA metapackage${nvidia:LegacyDesc}
 nvidia-glx-ia32 - NVIDIA 32-bit libraries${nvidia:LegacyDesc} (transitional 
package
 nvidia-kernel-dkms - NVIDIA binary kernel module DKMS 
source${nvidia:LegacyDesc}
 nvidia-kernel-source - NVIDIA binary kernel module source${nvidia:LegacyDesc}
 nvidia-libopencl1 - NVIDIA OpenCL library
 nvidia-libopencl1-ia32 - please switch to multiarch nvidia-libopencl1:i386
 nvidia-opencl-common - NVIDIA OpenCL driver
 nvidia-opencl-icd - NVIDIA OpenCL ICD
 nvidia-opencl-icd-ia32 - please switch to multiarch nvidia-opencl-icd:i386
 nvidia-smi - NVIDIA System Management Interface
 nvidia-vdpau-driver - NVIDIA vdpau driver
 nvidia-vdpau-driver-ia32 - please switch to multiarch nvidia-vdpau-driver:i386
 xserver-xorg-video-nvidia - NVIDIA binary Xorg driver${nvidia:LegacyDesc}
Closes: 805917
Changes: 
 nvidia-graphics-drivers 

Processed: raise severity of pysupport → dh_python2 bugs to RC

[Debian Bug Tracking System]

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

> # I'm getting to the end of this.
> # Most of you, bugs, are already fixed and your fix is in the
> # DEFERRED queue.
> # For the one that are not, good chances are an RM bug is already
> # filed, so you're only waiting for a FTP assistant to come
> # along and accidentally kill your host (the package you're bugging).
> # If you aren't in neither of those 2 situation above probably
> # your host ought to be kicked, maybe tell your master (=the
> # maintainer of the package you're bugging) to get your host killed.
> # If your master refuses then he should just kill you instead of
> # your host; there might be reason I haven't done that myself,
> # tell him he should probably get in touch with me.
> # If you, reader of this text, are a Debian Release Menager and
> # you're wondering why I'm generating some 40 new RC bugs from
> # nothing be reassured that I want them to be fixed by the end of
> # the week, one way or another.
> severity 785987 serious
Bug #785987 [src:controlaula] controlaula: deprecation of python-support
Severity set to 'serious' from 'important'
> severity 785990 serious
Bug #785990 [src:distcc] distcc: deprecation of python-support
Severity set to 'serious' from 'important'
> severity 785991 serious
Bug #785991 [src:dipy] dipy: deprecation of python-support
Severity set to 'serious' from 'important'
> severity 785993 serious
Bug #785993 [src:python-carrot] python-carrot: deprecation of python-support
Severity set to 'serious' from 'important'
> severity 786026 serious
Bug #786026 [src:liquidsoap] liquidsoap: deprecation of python-support
Severity set to 'serious' from 'important'
> severity 786042 serious
Bug #786042 [src:jack] jack: deprecation of python-support
Severity set to 'serious' from 'important'
> severity 786048 serious
Bug #786048 [src:conduit] conduit: deprecation of python-support
Severity set to 'serious' from 'important'
> severity 786054 serious
Bug #786054 [src:gnomecatalog] gnomecatalog: deprecation of python-support
Severity set to 'serious' from 'important'
> severity 786065 serious
Bug #786065 [src:gnome-schedule] gnome-schedule: deprecation of python-support
Severity set to 'serious' from 'important'
> severity 786071 serious
Bug #786071 [src:py-asterisk] py-asterisk: deprecation of python-support
Severity set to 'serious' from 'important'
> severity 786077 serious
Bug #786077 [src:opensesame] opensesame: deprecation of python-support
Severity set to 'serious' from 'important'
> severity 786083 serious
Bug #786083 [src:pythontracer] pythontracer: deprecation of python-support
Severity set to 'serious' from 'important'
> severity 786086 serious
Bug #786086 [src:mumble-django] mumble-django: deprecation of python-support
Severity set to 'serious' from 'important'
> severity 786100 serious
Bug #786100 [src:gnome-osd] gnome-osd: deprecation of python-support
Severity set to 'serious' from 'important'
> severity 786118 serious
Bug #786118 [src:gwrite] gwrite: deprecation of python-support
Severity set to 'serious' from 'important'
> severity 786120 serious
Bug #786120 [src:miro] miro: deprecation of python-support
Severity set to 'serious' from 'important'
> severity 786138 serious
Bug #786138 [src:moap] moap: deprecation of python-support
Severity set to 'serious' from 'important'
> severity 786141 serious
Bug #786141 [src:gnome-hearts] gnome-hearts: deprecation of python-support
Severity set to 'serious' from 'important'
> severity 786144 serious
Bug #786144 [src:urlgrabber] urlgrabber: deprecation of python-support
Bug #637262 [src:urlgrabber] urlgrabber: Please update to dh_python2 for 
deprecation of dh_pysupport
Severity set to 'serious' from 'normal'
Severity set to 'serious' from 'normal'
> severity 786145 serious
Bug #786145 [src:openshot] openshot: deprecation of python-support
Severity set to 'serious' from 'important'
> severity 786149 serious
Bug #786149 [src:pivy] pivy: deprecation of python-support
Severity set to 'serious' from 'important'
> severity 786150 serious
Bug #786150 [src:gextractwinicons] gextractwinicons: deprecation of 
python-support
Severity set to 'serious' from 'important'
> severity 786158 serious
Bug #786158 [src:pystatgrab] pystatgrab: deprecation of python-support
Severity set to 'serious' from 'important'
> severity 786165 serious
Bug #786165 [src:gbirthday] gbirthday: deprecation of python-support
Severity set to 'serious' from 'important'
> severity 786166 serious
Bug #786166 [src:python-fixtures] python-fixtures: deprecation of python-support
Severity set to 'serious' from 'important'
> severity 786173 serious
Bug #786173 [src:python-peak.rules] python-peak.rules: deprecation of 
python-support
Severity set to 'serious' from 'important'
> severity 786179 serious
Bug #786179 [src:python-uniconvertor] python-uniconvertor: deprecation of 
python-support
Severity set to 'serious' from 'important'
> severity 786183 serious
Bug #786183 [src:mimms] mimms: deprecation of python-support

Processed: these 2 pysupport→dh-python are not serious, lucky you

[Debian Bug Tracking System]

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

> # You two only causes the packegs to install random files in
> # directories owned by python-support.
> # That's buggy, but not as buggy as your brothers, lucky you.
> severity 798477 important
Bug #798477 [gnuspool] gnuspool: do not install files in python-support 
directories
Severity set to 'important' from 'serious'
> severity 798478 important
Bug #798478 [ratpoison] ratpoison: do not install files in python-support 
directories
Severity set to 'important' from 'serious'
> quit
Stopping processing here.

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

Bug#807728: 0.76 didn't fix it for me

[Hans-Christoph Steiner]

Doh, just saw this is a bug in pbuilder, not cowbuilder.  I updated to
pbuilder 0.221.3 and it fixed the issue for me.

Bug#766631: marked as done (FTBFS ppc64el: Remove deprecated SVID_SOURCE)

[Debian Bug Tracking System]

Your message dated Mon, 14 Dec 2015 09:43:33 +
with message-id 
and subject line Bug#766631: fixed in turnserver 0.7.3-4
has caused the Debian Bug report #766631,
regarding FTBFS ppc64el: Remove deprecated SVID_SOURCE
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.)


-- 
766631: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=766631
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: turnserver
Version: 0.7.3-2
Severity: critical
Tags: patch

At the moment, turnserver doesn't build on ppc64el platform with the following
error:

In file included from tls_peer.c:72:0:
/usr/include/netinet/tcp.h:89:11: error: duplicate member 'th_off'
  u_int8_t th_off:4;  /* data offset */
   ^
/usr/include/netinet/tcp.h:90:11: error: duplicate member 'th_x2'
  u_int8_t th_x2:4;  /* (unused) */

https://buildd.debian.org/status/fetch.php?pkg=turnserver=ppc64el=0.7.3-2=1410498176

That is because both path of the following are being executed:

 # if __BYTE_ORDER == __BIG_ENDIAN
 u_int8_t th_off:4;  /* data offset */
 u_int8_t th_x2:4;   /* (unused) */
 # endif
 # if __BYTE_ORDER == __LITTLE_ENDIAN
 u_int8_t th_x2:4;   /* (unused) */
 u_int8_t th_off:4;  /* data offset */
 # endif

This is because SVID_SOURCE is being used, and it is deprecated. The proper way
is to use _DEFAULT_SOURCE, which fixes the problem above.

Thanks
Breno
--- turnserver-0.7.3.orig/src/Makefile.am
+++ turnserver-0.7.3/src/Makefile.am
@@ -1,4 +1,4 @@
-AM_CFLAGS = -std=c99 -Wall -Wextra -Werror -Wstrict-prototypes -Wredundant-decls -Wshadow -pedantic -fno-strict-aliasing -D_POSIX_C_SOURCE=200112L -D_XOPEN_SOURCE=600 -O2 -D_SVID_SOURCE
+AM_CFLAGS = -std=c99 -Wall -Wextra -Werror -Wstrict-prototypes -Wredundant-decls -Wshadow -pedantic -fno-strict-aliasing -D_POSIX_C_SOURCE=200112L -D_XOPEN_SOURCE=600 -O2 -D_DEFAULT_SOURCE
 
 if ENABLE_DEBUG_BUILD
 AM_CFLAGS += -g 
--- turnserver-0.7.3.orig/src/Makefile.in
+++ turnserver-0.7.3/src/Makefile.in
@@ -288,7 +288,7 @@ top_srcdir = @top_srcdir@
 AM_CFLAGS = -std=c99 -Wall -Wextra -Werror -Wstrict-prototypes \
 	-Wredundant-decls -Wshadow -pedantic -fno-strict-aliasing \
 	-D_POSIX_C_SOURCE=200112L -D_XOPEN_SOURCE=600 -O2 \
-	-D_SVID_SOURCE $(am__append_1) $(am__append_2)
+	-D_DEFAULT_SOURCE $(am__append_1) $(am__append_2)
 INCLUDE = -I.
 noinst_HEADERS = turnserver.h \
  turn.h \
--- End Message ---
--- Begin Message ---
Source: turnserver
Source-Version: 0.7.3-4

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

Debian distribution maintenance software
pp.
Andreas Beckmann  (supplier of updated turnserver 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 09:04:59 +0100
Source: turnserver
Binary: turnserver
Architecture: source
Version: 0.7.3-4
Distribution: unstable
Urgency: medium
Maintainer: Debian QA Group 
Changed-By: Andreas Beckmann 
Description:
 turnserver - server for ICE/STUN/TURN, NAT traversal for SIP and Jabber
Closes: 766631
Changes:
 turnserver (0.7.3-4) unstable; urgency=medium
 .
   * QA upload.
   * Switch from deprecated _SVID_SOURCE to _DEFAULT_SOURCE, fixing FTBFS on
 ppc* (any maybe more) architectures, thanks to Breno Leitao.
 (Closes: #766631)
   * Use canonical Vcs-* URLs.
Checksums-Sha1:
 f6cb757866fe451961b09535d0f3f09d2b65134f 1937 turnserver_0.7.3-4.dsc
 0f3fe8b922c440f964afbccca2990abedc7ca275 5580 turnserver_0.7.3-4.debian.tar.xz
Checksums-Sha256:
 b59daa9dc7c7f9d75f12c464d56bf1f8f52459d58928dd02e05d38c507982e1b 1937 
turnserver_0.7.3-4.dsc
 5a92881527bed099cd27d0863bc8d2e4f8f2f155f97af357c1484cee1149861b 5580 
turnserver_0.7.3-4.debian.tar.xz
Files:
 82d497e5bcc3dbf8c8685250b91eb969 1937 net extra turnserver_0.7.3-4.dsc
 de67b75ee0c1ba568c56d143986634af 5580 net extra 
turnserver_0.7.3-4.debian.tar.xz

-BEGIN PGP SIGNATURE-
Version: GnuPG v1

Bug#807728: 0.76 didn't fix it for me

[Hans-Christoph Steiner]

I'm also affected by this issue using cowbuilder 0.75.  Updating to 0.76
did not fix it.  This did:

sudo cowbuilder --login --save-after-login
# mkdir -p /home/hans/.cache

Here's the error:
Setting up pbuilder-satisfydepends-dummy (0.invalid.0) ...
E: Could not create directory: /home/hans/.cache:
boost::filesystem::create_directory: No such file or directory:
"/home/hans/.cache"
E: pbuilder-satisfydepends failed.



To reproduce it, I did:
sudo cowbuilder --login --save-after-login
# rm -rf /home/hans

Bug#807589: libechonest: FTBFS on all architectures due to mismatched symbols file(s)

[John Paul Adrian Glaubitz]

On 12/14/2015 08:19 AM, Stefan Ahlers wrote:
> What should we do now? A new build only to fix the sh4 symbols or shell
> we fix it for the next release?

sh4 is one of my pet architectures. I will have a look and report back
later. I still need to set up the four more additional buildds to
speed up the build process similar to m68k. Hopefully I can do that
today, I still had to spend lots of time into getting ghc fixed
on sparc64 :).

Adrian

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

Bug#805919: marked as done (nvidia-graphics-drivers-legacy-340xx: CVE-2015-7869: Unsanitized User Mode Input)

[Debian Bug Tracking System]

Your message dated Mon, 14 Dec 2015 11:35:08 +
with message-id 
and subject line Bug#805919: fixed in nvidia-graphics-drivers-legacy-340xx 
340.96-1
has caused the Debian Bug report #805919,
regarding nvidia-graphics-drivers-legacy-340xx: CVE-2015-7869: Unsanitized User 
Mode Input
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.)


-- 
805919: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=805919
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: nvidia-graphics-drivers
Version: 304.22-1
Severity: serious
Tags: security

http://nvidia.custhelp.com/app/answers/detail/a_id/3808
http://people.canonical.com/~ubuntu-security/cve/2015/CVE-2015-7869.html

[...] This report also details an advisory regarding integer overflow issues
in the underlying kernel mode driver.

[...] The integer overflow issues affect both Windows and Linux-based GPU
drivers. These issues affect all GPU products and are not specific to
any GPU class device.


Andreas
--- End Message ---
--- Begin Message ---
Source: nvidia-graphics-drivers-legacy-340xx
Source-Version: 340.96-1

We believe that the bug you reported is fixed in the latest version of
nvidia-graphics-drivers-legacy-340xx, 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 805...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Andreas Beckmann  (supplier of updated 
nvidia-graphics-drivers-legacy-340xx 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 12:25:37 +0100
Source: nvidia-graphics-drivers-legacy-340xx
Binary: nvidia-legacy-340xx-driver nvidia-legacy-340xx-driver-bin 
xserver-xorg-video-nvidia-legacy-340xx libgl1-nvidia-legacy-340xx-glx 
libgl1-nvidia-legacy-340xx-glx-i386 libegl1-nvidia-legacy-340xx 
libgles1-nvidia-legacy-340xx libgles2-nvidia-legacy-340xx 
libnvidia-legacy-340xx-eglcore nvidia-legacy-340xx-alternative 
nvidia-legacy-340xx-kernel-support nvidia-legacy-340xx-kernel-dkms 
nvidia-legacy-340xx-kernel-source nvidia-legacy-340xx-vdpau-driver 
nvidia-legacy-340xx-smi libnvidia-legacy-340xx-cuda1 
libnvidia-legacy-340xx-cuda1-i386 libnvidia-legacy-340xx-compiler 
libnvidia-legacy-340xx-nvcuvid1 libnvidia-legacy-340xx-encode1 
libnvidia-legacy-340xx-ifr1 libnvidia-legacy-340xx-fbc1 
libnvidia-legacy-340xx-ml1 nvidia-legacy-340xx-opencl-icd
Architecture: source
Version: 340.96-1
Distribution: unstable
Urgency: medium
Maintainer: Debian NVIDIA Maintainers 
Changed-By: Andreas Beckmann 
Description:
 libegl1-nvidia-legacy-340xx - NVIDIA binary EGL libraries${nvidia:LegacyDesc}
 libgl1-nvidia-legacy-340xx-glx - NVIDIA binary OpenGL 
libraries${nvidia:LegacyDesc}
 libgl1-nvidia-legacy-340xx-glx-i386 - NVIDIA binary OpenGL 32-bit 
libraries${nvidia:LegacyDesc}
 libgles1-nvidia-legacy-340xx - NVIDIA binary OpenGL|ES 1.x 
libraries${nvidia:LegacyDesc}
 libgles2-nvidia-legacy-340xx - NVIDIA binary OpenGL|ES 2.x 
libraries${nvidia:LegacyDesc}
 libnvidia-legacy-340xx-compiler - NVIDIA runtime compiler library
 libnvidia-legacy-340xx-cuda1 - NVIDIA CUDA Driver Library
 libnvidia-legacy-340xx-cuda1-i386 - NVIDIA CUDA 32-bit runtime 
library${nvidia:LegacyDesc}
 libnvidia-legacy-340xx-eglcore - NVIDIA binary EGL core 
libraries${nvidia:LegacyDesc}
 libnvidia-legacy-340xx-encode1 - NVENC Video Encoding runtime library
 libnvidia-legacy-340xx-fbc1 - NVIDIA OpenGL-based Framebuffer Capture runtime 
library
 libnvidia-legacy-340xx-ifr1 - NVIDIA OpenGL-based Inband Frame Readback 
runtime library
 libnvidia-legacy-340xx-ml1 - NVIDIA Management Library (NVML) runtime library
 libnvidia-legacy-340xx-nvcuvid1 - NVIDIA CUDA Video Decoder runtime library
 nvidia-legacy-340xx-alternative - allows the selection of NVIDIA as GLX 
provider
 nvidia-legacy-340xx-driver - NVIDIA metapackage${nvidia:LegacyDesc}
 nvidia-legacy-340xx-driver-bin - NVIDIA driver support 
binaries${nvidia:LegacyDesc}
 nvidia-legacy-340xx-kernel-dkms - NVIDIA binary kernel module DKMS 
source${nvidia:LegacyDesc}
 nvidia-legacy-340xx-kernel-source - NVIDIA binary kernel 

Bug#806246: marked as done (cmucl: FTBFS (missing build-depends))

[Debian Bug Tracking System]

Your message dated Mon, 14 Dec 2015 10:19:39 +
with message-id 
and subject line Bug#806246: fixed in cmucl 21a-3
has caused the Debian Bug report #806246,
regarding cmucl: FTBFS (missing build-depends)
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.)


-- 
806246: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=806246
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:cmucl
Version: 21a-2
Severity: serious

Dear maintainer:

I tried to build this package in a clean chroot and this is what
happened:


[...]
 fakeroot debian/rules clean
debian/rules:18: /usr/share/hardening-includes/hardening.make: No such file or 
directory
make: *** No rule to make target 
'/usr/share/hardening-includes/hardening.make'.  Stop.
dpkg-buildpackage: error: fakeroot debian/rules clean gave error exit status 2


Seems like a missing Build-Depends on hardening-includes, the package
containing /usr/share/hardening-includes/hardening.make, so it
should be quite easy to fix.

I would recommend that you try to build this package in a clean
environment to ensure that this does not happen. There are several
ways to do that. I use schroot myself, but pbuilder is also quite
popular.

BTW: I wonder why this package does not exist for amd64. Is it a
bootstrapping problem as the extended description suggests?

Thanks.
--- End Message ---
--- Begin Message ---
Source: cmucl
Source-Version: 21a-3

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

Debian distribution maintenance software
pp.
Peter Van Eynde  (supplier of updated cmucl package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Wed, 14 Oct 2015 14:30:35 +0200
Source: cmucl
Binary: cmucl cmucl-docs cmucl-clm cmucl-source
Architecture: source i386 all
Version: 21a-3
Distribution: unstable
Urgency: medium
Maintainer: Debian Common Lisp Team 

Changed-By: Peter Van Eynde 
Description:
 cmucl  - CMU Common Lisp compiler and development system
 cmucl-clm  - Motif interface for CMUCL
 cmucl-docs - CMUCL documentation
 cmucl-source - CMUCL lisp sources
Closes: 806246
Changes:
 cmucl (21a-3) unstable; urgency=medium
 .
   * Fix "FTBFS (missing build-depends)" by adding a Build-Depends on
 hardening-includes and cleaning up the build environment.
 (Closes: #806246)
Checksums-Sha1:
 a5c7426cdd37edf2e0fee2abe0312af57dbef61e 2311 cmucl_21a-3.dsc
 b0a28276eaede981ec0580f6b448f3e8c7171af2 1030752 cmucl_21a-3.debian.tar.xz
 e3ebe68a5cb05839dfe308372872072ab3b0b7ed 359958 cmucl-clm_21a-3_i386.deb
 a9d4a3514d8dbf02332db954a75345fa5acb5ed5 2448684 cmucl-docs_21a-3_all.deb
 35ecbf7f555d939a0dd21519d26804d80fda99d1 3615584 cmucl-source_21a-3_all.deb
 971d9ee521016572789056e83c20816459c456da 8457584 cmucl_21a-3_i386.deb
Checksums-Sha256:
 a941c2ad336397d0db78a90c9a7dd26be6e6c780d07ac91494f1152cbf84 2311 
cmucl_21a-3.dsc
 9a4bde6411b890b4181496b9101690e7a4f456f16df94760cc3bcbe4fd6f95eb 1030752 
cmucl_21a-3.debian.tar.xz
 5bf69cbd3f11b0e4a6546c15a3b02797dea5765cd988aba5e544facc034a 359958 
cmucl-clm_21a-3_i386.deb
 1701f46a2aba9898aa3fd32cc58a866d2ce4a7be6c979d11955db9ab79147d70 2448684 
cmucl-docs_21a-3_all.deb
 994e075f6347389d47466fb5d24bf7f899a5e9d9dfe119b45262dc1332458fb0 3615584 
cmucl-source_21a-3_all.deb
 8be2b5b62aad8e568d37768b74413237fc6eedfa0f6f0a10b3655d5073d1eade 8457584 
cmucl_21a-3_i386.deb
Files:
 f716e1334120468ec4e2cb4690b94969 2311 lisp optional cmucl_21a-3.dsc
 5ea19ebdc69f94bb4c8a9e9747f48a2e 1030752 lisp optional 
cmucl_21a-3.debian.tar.xz
 0dedbafb4e8473f39414cc7295e120a5 359958 lisp optional cmucl-clm_21a-3_i386.deb
 2e7d718f848b05313c101b9d31128877 2448684 doc optional cmucl-docs_21a-3_all.deb
 ccb8025939018463f86473105630cb3f 3615584 lisp optional 
cmucl-source_21a-3_all.deb
 

Bug#804111: marked as done (lava-server: fails to install: The name 'physical-group' is invalid related_name for field Device.physical_group)

[Debian Bug Tracking System]

Your message dated Mon, 14 Dec 2015 10:35:27 +
with message-id 
and subject line Bug#804111: fixed in lava-server 2015.12-1
has caused the Debian Bug report #804111,
regarding lava-server: fails to install: The name 'physical-group' is invalid 
related_name for field Device.physical_group
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.)


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

Hi,

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

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

  Selecting previously unselected package lava-server.
  (Reading database ... 
(Reading database ... 26380 files and directories currently installed.)
  Preparing to unpack .../lava-server_2015.11-1_all.deb ...
  Unpacking lava-server (2015.11-1) ...
  Processing triggers for systemd (227-2) ...
  Setting up lava-server (2015.11-1) ...
  
WARNING:py.warnings:/usr/lib/python2.7/dist-packages/dashboard_app/models.py:36:
 RemovedInDjango19Warning: django.contrib.contenttypes.generic is deprecated 
and will be removed in Django 1.9. Its contents have been moved to the fields, 
forms, and admin submodules of django.contrib.contenttypes.
from django.contrib.contenttypes import generic
  
  
Error: System check identified some issues:
  

AndreaRORS:
  va_scheduler_app.Device.physical_group: (fields.E306) The name 
'physical-group' is invalid related_name for field Device.physical_group
HINT: Related name must be a valid Python identifier or end with a 
'+'va_scheduler_app.Device.physical_owner: (fields.E306) The name 
'physical-owner' is invalid related_name for field Device.physical_owner
HINT: Related name must be a valid Python identifier or end with a 
'+'RNINGS:
  
ogle_analytics.Analytic.site: (fields.W342) Setting unique=True on a ForeignKey 
has the same effect as using a OneToOneField.
HINT: ForeignKey(unique=True) is usually better served by a 
OneToOneField.va_scheduler_app.Device.current_job: (fields.W342) Setting 
unique=True on a ForeignKey has the same effect as using a OneToOneField.
HINT: ForeignKey(unique=True) is usually better served by a 
OneToOneField.va_scheduler_app.Device.last_health_report_job: (fields.W342) 
Setting unique=True on a ForeignKey has the same effect as using a 
OneToOneField.
HINr: ForeignKey(unique=True) is usually better served by a 
OneToOneField.va_scheduler_app.DeviceType.cores: (fields.W340) null has no 
effect on ManyToManyField.va_scheduler_app.TestJob.viewing_groups: 
(fields.W340) null has no effect on ManyToManyField.
r processing package lava-server (--configure):
   subprocess installed post-installation script returned error exit status 1
  Processing triggers for systemd (227-2) ...
  Errors were encountered while processing:
   lava-server


lava-server_2015.11-1.log.gz
Description: application/gzip
--- End Message ---
--- Begin Message ---
Source: lava-server
Source-Version: 2015.12-1

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

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

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

Debian distribution maintenance software
pp.
Neil Williams  (supplier of updated lava-server 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 09:40:37 +
Source: lava-server
Binary: lava-server lava lava-dev lava-server-doc
Architecture: source all
Version: 2015.12-1
Distribution: unstable
Urgency: medium
Maintainer: Debian LAVA team 
Changed-By: Neil Williams 
Description:
 lava   - Linaro Automated Validation Architecture metapackage
 lava-dev   - Linaro Automated Validation Architecture developer support
 lava-server - Linaro Automated 

Processed: tagging 765419

[Debian Bug Tracking System]

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

> tags 765419 + sid
Bug #765419 [mumble-django] mumble-django: wont install , broken is useless
Added tag(s) sid.
> thanks
Stopping processing here.

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

Bug#785991: Delayed upload

[Mattia Rizzolo]

Hi,

On Wed, Aug 26, 2015 at 09:10:28PM +0200, Michael Hanke wrote:
> The package update is done, but a failing tests prevent an immediate
> upload. See attached build log. Investigation is under way...

any news on this?
we'd like to go on... :)

-- 
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#807741: marked as done ([package:salt-master] salt-master.service start times out)

[Debian Bug Tracking System]

Your message dated Mon, 14 Dec 2015 15:59:48 +
with message-id 
and subject line Bug#807741: fixed in salt 2015.8.3+ds-2
has caused the Debian Bug report #807741,
regarding [package:salt-master] salt-master.service start times out
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.)


-- 
807741: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=807741
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: package:salt-master
Version: 2015.8.3+ds-1
Severity: serious

--- Please enter the report below this line. ---
After upgrade from version 2015.8.1+ds-2 to 2015.8.3+ds-1 the salt-
master.service times out upon start. This already happens during apt-get. If I 
try to start it afterwards, I get:

# systemctl start salt-master
Job for salt-master.service failed because a timeout was exceeded. See 
"systemctl status salt-master.service" and "journalctl -xe" for details.

However, the process runs for some time, I can see logging output using 
journactl -f in a 2nd shell, but once systemctl returns the salt-master 
process is also gone.

If I start it from the shell directly, it runs just fine.

Since the package is not usable in this state, I've set the severity to 
"serious"...
--- System information. ---
Architecture: amd64
Kernel:   Linux 4.2.0-1-amd64

Debian Release: stretch/sid
  990 testing www.deb-multimedia.org 
  990 testing security.debian.org 
  990 testing ftp.de.debian.org 
  500 utopic  ppa.launchpad.net 
  500 unstabledownload.jitsi.org 
  500 stable  update.devolo.com 
  500 nightly pkg.tox.chat 

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

Package's Recommends field is empty.

Package's Suggests field is empty.
-- 
Dirk Heinrichs 
GPG Public Key CB614542 | Jabber: dirk.heinri...@altum.de
Tox: he...@toxme.se
Sichere Internetkommunikation: http://www.retroshare.org
Privacy Handbuch: https://www.privacy-handbuch.de


signature.asc
Description: This is a digitally signed message part.
--- End Message ---
--- Begin Message ---
Source: salt
Source-Version: 2015.8.3+ds-2

We believe that the bug you reported is fixed in the latest version of
salt, 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.
Benjamin Drung  (supplier of updated salt 
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 12:17:44 +0100
Source: salt
Binary: salt-common salt-master salt-minion salt-syndic salt-ssh salt-doc 
salt-cloud salt-api salt-proxy
Architecture: source all
Version: 2015.8.3+ds-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Salt Team 
Changed-By: Benjamin Drung 
Description:
 salt-api   - Generic, modular network access system
 salt-cloud - public cloud VM management system
 salt-common - shared libraries that salt requires for all packages
 salt-doc   - additional documentation for salt, the distributed remote executi
 salt-master - remote manager to administer servers via salt
 salt-minion - client package for salt, the distributed remote execution system
 salt-proxy - Proxy client package for salt stack
 salt-ssh   - remote manager to administer servers via Salt SSH
 salt-syndic - master-of-masters for salt, the distributed remote execution syst
Closes: 807741
Changes:
 salt (2015.8.3+ds-2) unstable; urgency=medium
 .
   * salt-master: Depend on python-systemd for the startup notification
 unless sysvinit is used as default init system (Closes: #807741,
 LP: #1525184)
Checksums-Sha1:
 b74e011658c304e16454d86f283b9c0a97e92b5a 2580 salt_2015.8.3+ds-2.dsc
 e3d8ba0d426a8fca8bb4716ea496a4fb58a66b42 26232 salt_2015.8.3+ds-2.debian.tar.xz
 12773b524bfac1fcbf474f42bad18e02cd472dde 21830 salt-api_2015.8.3+ds-2_all.deb
 73ed7fa29c5a2cc0a487d20b7f6f4eb606aac4fd 23288 salt-cloud_2015.8.3+ds-2_all.deb
 0b852c0166b0c03f99917e66dc3e2b580437a9ce 3044008 

Bug#807915: mono-addins: FTBFS with new mono, upgrade to 1.2 release?

[Dimitri John Ledkov]

Would something like attached work?
Description: set target framework to 4.5.
Author: Dimitri John Ledkov 

--- mono-addins-1.2.orig/Mono.Addins.CecilReflector/Mono.Addins.CecilReflector.csproj
+++ mono-addins-1.2/Mono.Addins.CecilReflector/Mono.Addins.CecilReflector.csproj
@@ -11,7 +11,7 @@
 Mono.Addins.CecilReflector
 True
 ..\mono-addins.snk
-v4.0
+v4.5
   
   
 True
--- mono-addins-1.2.orig/Mono.Addins.Gui/Mono.Addins.Gui.csproj
+++ mono-addins-1.2/Mono.Addins.Gui/Mono.Addins.Gui.csproj
@@ -11,7 +11,7 @@
 Mono.Addins.Gui
 True
 ..\mono-addins.snk
-v4.0
+v4.5
   
   
 True
--- mono-addins-1.2.orig/Mono.Addins.MSBuild/Mono.Addins.MSBuild.csproj
+++ mono-addins-1.2/Mono.Addins.MSBuild/Mono.Addins.MSBuild.csproj
@@ -11,6 +11,7 @@
 Mono.Addins.MSBuild
 True
 ..\mono-addins.snk
+v4.5
   
   
 True
--- mono-addins-1.2.orig/Mono.Addins.Setup/Mono.Addins.Setup.csproj
+++ mono-addins-1.2/Mono.Addins.Setup/Mono.Addins.Setup.csproj
@@ -11,7 +11,7 @@
 Mono.Addins.Setup
 True
 ..\mono-addins.snk
-v4.0
+v4.5
   
   
 True
--- mono-addins-1.2.orig/Mono.Addins/Mono.Addins.csproj
+++ mono-addins-1.2/Mono.Addins/Mono.Addins.csproj
@@ -11,7 +11,7 @@
 Mono.Addins
 True
 ..\mono-addins.snk
-v4.0
+v4.5
   
   
 True
--- mono-addins-1.2.orig/mautil/mautil.csproj
+++ mono-addins-1.2/mautil/mautil.csproj
@@ -9,6 +9,7 @@
 mautil
 2.0
 mautil
+v4.5
   
   
 True

Bug#807915: marked as done (mono-addins: FTBFS with new mono, upgrade to 1.2 release?)

[Debian Bug Tracking System]

Your message dated Mon, 14 Dec 2015 15:57:59 +
with message-id <e1a8vvf-0005o2...@franck.debian.org>
and subject line Bug#807915: fixed in mono-addins 1.0+git20130406.adcd75b-4
has caused the Debian Bug report #807915,
regarding mono-addins: FTBFS with new mono, upgrade to 1.2 release?
to be marked as done.

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

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


-- 
807915: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=807915
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
X-Debbugs-CC: Dimitri John Ledkov <x...@debian.org>
Source: mono-addins
Severity: serious

mono-addins ftbfs in unstable.

maybe it should be upgraded to 1.2 release from github? I haven't tried
it yet - https://github.com/mono/mono-addins/releases

(note there have been 10 commits to master since 1.2 release)

Build log attached.

Last error is:

Building Mono.Addins.csproj
CSC: error CS0518: The predefined type `System.Object' is not defined
or imported
CSC: error CS0518: The predefined type `System.ValueType' is not
defined or imported
CSC: error CS0518: The predefined type `System.Attribute' is not
defined or imported
CSC: error CS0518: The predefined type `System.Int32' is not defined or imported
CSC: error CS0518: The predefined type `System.UInt32' is not defined
or imported
CSC: error CS0518: The predefined type `System.Int64' is not defined or imported
CSC: error CS0518: The predefined type `System.UInt64' is not defined
or imported
CSC: error CS0518: The predefined type `System.Single' is not defined
or imported
CSC: error CS0518: The predefined type `System.Double' is not defined
or imported
CSC: error CS0518: The predefined type `System.Char' is not defined or imported
CSC: error CS0518: The predefined type `System.Int16' is not defined or imported
CSC: error CS0518: The predefined type `System.Decimal' is not defined
or imported
CSC: error CS0518: The predefined type `System.Boolean' is not defined
or imported
CSC: error CS0518: The predefined type `System.SByte' is not defined or imported
CSC: error CS0518: The predefined type `System.Byte' is not defined or imported
CSC: error CS0518: The predefined type `System.UInt16' is not defined
or imported
CSC: error CS0518: The predefined type `System.String' is not defined
or imported
CSC: error CS0518: The predefined type `System.Enum' is not defined or imported
CSC: error CS0518: The predefined type `System.Delegate' is not
defined or imported
CSC: error CS0518: The predefined type `System.MulticastDelegate' is
not defined or imported
CSC: error CS0518: The predefined type `System.Void' is not defined or imported
CSC: error CS0518: The predefined type `System.Array' is not defined or imported
CSC: error CS0518: The predefined type `System.Type' is not defined or imported
CSC: error CS0518: The predefined type
`System.Collections.IEnumerator' is not defined or imported
CSC: error CS0518: The predefined type
`System.Collections.IEnumerable' is not defined or imported
CSC: error CS0518: The predefined type `System.IDisposable' is not
defined or imported
CSC: error CS0518: The predefined type `System.IntPtr' is not defined
or imported
CSC: error CS0518: The predefined type `System.UIntPtr' is not defined
or imported
CSC: error CS0518: The predefined type `System.RuntimeFieldHandle' is
not defined or imported
CSC: error CS0518: The predefined type `System.RuntimeTypeHandle' is
not defined or imported
CSC: error CS0518: The predefined type `System.Exception' is not
defined or imported
make[2]: *** [csproj_build] Error 1
Makefile:567: recipe for target 'csproj_build' failed
make[2]: Leaving directory
'/«BUILDDIR»/mono-addins-1.0+git20130406.adcd75b/Mono.Addins'
make[1]: *** [all-recursive] Error 1
Makefile:348: recipe for target 'all-recursive' failed
make[1]: Leaving directory '/«BUILDDIR»/mono-addins-1.0+git20130406.adcd75b'
dh_auto_build: make -j1 returned exit code 2
make: *** [build] Error 2
debian/rules:40: recipe for target 'build' failed
dpkg-buildpackage: error: debian/rules build gave error exit status 2


-- 
Regards,

Dimitri.


mono-addins_1.0+git20130406.adcd75b-3_amd64-20151214-1318.build.xz
Description: application/xz
--- End Message ---
--- Begin Message ---
Source: mono-addins
Source-Version: 1.0+git20130406.adcd75b-4

We believe that the bug you reported is fixed in the latest version of
mono-addins, 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...@bug

Bug#807502: gcc-avr: Missing support for atxmega

[Lisandro Damián Nicanor Pérez Meyer]

On Sunday 13 December 2015 09:43:47 you wrote:
> Hi,
> I've now uploaded a new version of avr-libc with the new names on those
> files. I'll also update binutils to declear that it wont work with older
> avr-libc.

I confirm it works, thanks!


-- 
Bebe a bordo (pero con moderación)

Lisandro Damián Nicanor Pérez Meyer
http://perezmeyer.com.ar/
http://perezmeyer.blogspot.com/


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

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

[fishy]

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

Bug#796294: marked as done (Possibly drop uniconvertor dependency)

[Debian Bug Tracking System]

Your message dated Tue, 15 Dec 2015 04:48:58 +
with message-id 
and subject line Bug#796294: fixed in tgif 1:4.2.5-1.3
has caused the Debian Bug report #796294,
regarding Possibly drop uniconvertor dependency
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.)


-- 
796294: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=796294
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: tgif
Version: 1:4.2.5-1.2
Severity: important
Control: block 787925 by -1


Dear Maintainer,

tgif gained support for SVG output by adding python-uniconvertor
dependency (#608243).

Unfortunately, python-uniconvertor is not maintaned anymore (#644559),
has a severe bug report (#699301) which needs to be fixed with the
next upload (otherwise dak will reject the package due to a lintian
autoreject tag), and it will become a blocker for the python-support
removal (#786179).

I'm wondering whether it would be possible to drop python-uniconvertor
from tgif dependencies, so it will allow us to get rid of
python-uniconvertor and tgif will migrate to testing again. Another
option would be to step in and maintain python-uniconvertor.

-- 
Cheers,
Luca
--- End Message ---
--- Begin Message ---
Source: tgif
Source-Version: 1:4.2.5-1.3

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

Debian distribution maintenance software
pp.
Mattia Rizzolo  (supplier of updated tgif 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 23:01:37 +
Source: tgif
Binary: tgif
Architecture: source
Version: 1:4.2.5-1.3
Distribution: unstable
Urgency: medium
Maintainer: Carlo Segre 
Changed-By: Mattia Rizzolo 
Description:
 tgif   - 2D vector graphic drawing tool using Xlib
Closes: 796294
Changes:
 tgif (1:4.2.5-1.3) unstable; urgency=medium
 .
   * Non-maintainer upload.
   * Remove dependency on python-uniconvertor, since we want to remove it from
 the archive.  Closes: #796294; Reopens: #608243
Checksums-Sha1:
 9b777da4aaffee42299294f76bf48426d5bc7644 1739 tgif_4.2.5-1.3.dsc
 982fbe22c01d62cb4e0d822a2dac0398c4cc3d91 37692 tgif_4.2.5-1.3.debian.tar.xz
Checksums-Sha256:
 51f51b9425ed84ae3816a1bb6dec37bf76265d07cf2599e2b6635d00e10f961d 1739 
tgif_4.2.5-1.3.dsc
 8bbab3e8aee37bd28fe1b7af63cc8fd14e93b18387cae3343ad6ee9c551dc6dc 37692 
tgif_4.2.5-1.3.debian.tar.xz
Files:
 2c1d2262d8e8fc7666396c660709f74f 1739 graphics optional tgif_4.2.5-1.3.dsc
 c45e7efad6df4c11312efde16842ef03 37692 graphics optional 
tgif_4.2.5-1.3.debian.tar.xz

-BEGIN PGP SIGNATURE-
Version: GnuPG v1

iQIcBAEBCAAGBQJWb0tEAAoJEEsEP825REVAhusP/1L54XSmL5aZ4GGLlO4TTGdS
5nu0NsgiPGn528etbY9ManXxy6vSaxBHm88vAHmyZmouW1JPP6GcDll4Kh5dMt9m
J+cbPV6gyM1rGrrHr187bRhYodLP6EgY5kl85Z3nqOSS7ztYerGuUoS+UVQMJnqb
j7C2jIS2IGMdIkuoAcwZwLQFgA+2ad9boJafGRtBdnzwum9Ou9xLAUnSPDINUUvJ
iNey3tmETEciaBRYqyhJB9J9R5TaMmT91JkNP+6i4Ueixy28Z3qr6MgZ0c4aync8
YKFGgIfdSJ3vGM/1ylIxlF65caz7puJK7HRv+M0bJlGC2+u+ws0B8O3BFrTxK75r
VjSzDsWWd1OU+ZsWySXXTmxyRlc/2IqeZyZMn0j/1KZ0WZ6kV6KTA9HRD8DK0ayw
89Iaf3VynXCgpvt7I0OtOzGH3HMWj5b+R8Z6hFMFmeWmQBMDlOVYgd80Thpdj8Z9
kc5b6UasvGUPXFTJs2dMHD5jbwLtvjgMEtE2dSyRa/kb7OvezdZVETARr/6nL7lu
wKHeQ+Yqr/q2ijwrdtZ4VWgse+Kadg9En+1mxwTN3Bxg/4+XeMT5CJEnBlaHx2qm
znrJgMTc/CGMQJyRk1vJk9JNIkFHhS+tXPNuQ57yWJl6olobtJHkAVyPY+NekYK6
gn4kyFnUz4WwtTsdGmZH
=QCDI
-END PGP SIGNATURE End Message ---

Bug#785990: distcc: deprecation of python-support

[Mattia Rizzolo]

Unstable got fixed by Luca, but also experimental needs this.
Unluckily, distcc in experimental fails its tests since the switch to
gcc-5.

I tried to have a look at it, but i didn't manage to go anywhere.
Would be useful if somebody tries to see whether they go somewhere
useful...

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

[Debian Bug Tracking System]

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

> tags 807915 + sid
Bug #807915 {Done: Iain Lane } [src:mono-addins] mono-addins: 
FTBFS with new mono, upgrade to 1.2 release?
Added tag(s) sid.
> thanks
Stopping processing here.

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

Bug#807985: marked as done (blasr: /usr/bin/blasr - No such file or directory)

[Debian Bug Tracking System]

Your message dated Tue, 15 Dec 2015 05:25:23 +
with message-id 
and subject line Bug#807985: fixed in blasr 0~20151014+git8e668be-1
has caused the Debian Bug report #807985,
regarding blasr: /usr/bin/blasr - No such file or directory
to be marked as done.

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

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


-- 
807985: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=807985
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: blasr
Version: 0~20150724+git3ca7fe8-1+b3
Severity: grave
Control: tag -1 + pending

The package appears to have been improperly linked against its
libraries, rendering the package completely unusable:

$ which blasr
/usr/bin/blasr
$ blasr --help
bash: /usr/bin/blasr: No such file or directory

$ which sawriter
/usr/bin/sawriter
$ sawriter
bash: /usr/bin/sawriter: No such file or directory


I am preparing an upload to resolve this problem, but I think this
should be documented in the BTS.

-- 
Afif Elghraoui | عفيف الغراوي
http://afif.ghraoui.name
--- End Message ---
--- Begin Message ---
Source: blasr
Source-Version: 0~20151014+git8e668be-1

We believe that the bug you reported is fixed in the latest version of
blasr, 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.
Afif Elghraoui  (supplier of updated blasr 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 19:51:57 -0800
Source: blasr
Binary: blasr
Architecture: source amd64
Version: 0~20151014+git8e668be-1
Distribution: unstable
Urgency: high
Maintainer: Debian Med Packaging Team 

Changed-By: Afif Elghraoui 
Description:
 blasr  - mapping single-molecule sequencing reads
Closes: 807985
Changes:
 blasr (0~20151014+git8e668be-1) unstable; urgency=high
 .
   * Don't install LICENSES.txt file
   * Imported Upstream version 0~20151014+git8e668be
   * Use externally packaged pbseqlib and dynamically link to it
 (Closes: #807985)
   * Adjust for renamed upstream documentation
   * Minor clean-ups
   * Update comment about why tests can't be run
   * Allow building in parallel
Checksums-Sha1:
 d8981a64c32ea6e29c8e913be0caab07ee48ada3 2074 blasr_0~20151014+git8e668be-1.dsc
 dc74a7dc4fb0b9513a519a722794855b97a8b9f8 136528 
blasr_0~20151014+git8e668be.orig.tar.gz
 20865708c27cf289319a13a64e2d11c20a25c926 12060 
blasr_0~20151014+git8e668be-1.debian.tar.xz
 334ef26fd34d880feb312fb0807be0609dca7fb4 449024 
blasr_0~20151014+git8e668be-1_amd64.deb
Checksums-Sha256:
 c75bc3299d0de8ef1de33ba28fdc9f6050ec03bbb225bef4ed1e21a3d68d5226 2074 
blasr_0~20151014+git8e668be-1.dsc
 a5282ada4dbd304e9393057c66dd952186557111c262850b420c0d34dde1e9b3 136528 
blasr_0~20151014+git8e668be.orig.tar.gz
 81a58c5eaf70ef903757783d04982e27216ba642979ea870ba495b94749eb0ae 12060 
blasr_0~20151014+git8e668be-1.debian.tar.xz
 40c3e8d5032f22b449392ee49d56d01ed8401737f4ea0d0963d2065e8c0b21f1 449024 
blasr_0~20151014+git8e668be-1_amd64.deb
Files:
 59d65925c782b092b168b69c3297a5cb 2074 science optional 
blasr_0~20151014+git8e668be-1.dsc
 88dad2545e7f878eb681ac37c1e36280 136528 science optional 
blasr_0~20151014+git8e668be.orig.tar.gz
 c6cbc4a27784e4aea69dcdac31a5541b 12060 science optional 
blasr_0~20151014+git8e668be-1.debian.tar.xz
 c8225958cef9ea79a7e3675eeb41d473 449024 science optional 
blasr_0~20151014+git8e668be-1_amd64.deb

-BEGIN PGP SIGNATURE-
Version: GnuPG v1

iQIcBAEBCAAGBQJWb5QDAAoJEM6uatOv6Cb71NQP/ROiQ8aFOgE/th4nX5CVPCFj
YEv4zHs+Hs1qupXuH4Qjk721KYOMlBaSfJJcstvK/e9Q9/8cjHy2Zz/GsGlRh+s2
8Wo+L0mAMeb17efKslt9Xkct17YLmCm091ZaR8Tn+ZlDiocA/EvTktuo/tXMA9Pj
CkE9d21aemE/7UlTBiHwPiQYICcK53E+Hsvpu0NkgQgDdUhEqXH6SffIuX/V1Hzh
ZP5AYTDLGeVsLSitySeIazDycnYENlk6HHYglTu4P5GklWup5uOxKVJY3957ow7K
+vlsabYY7EPPSBxTDQP4dXLbygcCccuuiqONMjrUEAl7upOHzrD7k92y3JQc6vpw
nD5aZ/pWjMa+2WKx0ipiUamwmwoemzl8mQV/9BJHvTHt+1cR9+9of3I6+LKqqi96
6kyKBw+q4CMVGm9jA9VVl7PlfmDoK3TdthfucdNivn0gqXExwNHyVDLYcJaGiMr4
5b8nE2f4hrkO1h58ex6qyy0rtftdL+7ql0FLwor338ZkbYijLvwAhHu7zsIsnyD2

Bug#786166: marked as done (python-fixtures: deprecation of python-support)

[Debian Bug Tracking System]

Your message dated Tue, 15 Dec 2015 03:27:28 +
with message-id <20151215032728.ga18...@chase.mapreri.org>
and subject line Re: Bug#786166: python-fixtures: deprecation of python-support
has caused the Debian Bug report #786166,
regarding python-fixtures: 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.)


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

On Thu, May 21, 2015 at 05:25:03AM +1200, Robert Collins wrote:
> Hi, please feel free to NMU this, its not on my current short-list of
> things to get done.

Turns out zigo did this in July and nobody noticed ;)

^^

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

Processed: tagging 786317, tagging 786287, tagging 786282, tagging 786227, tagging 786213, tagging 786194 ...

[Debian Bug Tracking System]

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

> tags 786317 + sid stretch
Bug #786317 [src:python-peak.util] python-peak.util: deprecation of 
python-support
Added tag(s) sid and stretch.
> tags 786287 + sid
Bug #786287 [src:turtleart] turtleart: deprecation of python-support
Added tag(s) sid.
> tags 786282 + sid stretch
Bug #786282 [src:enemies-of-carlotta] enemies-of-carlotta: deprecation of 
python-support
Added tag(s) sid and stretch.
> tags 786227 + sid stretch
Bug #786227 [src:python-django-rosetta] python-django-rosetta: deprecation of 
python-support
Added tag(s) stretch and sid.
> tags 786213 + sid stretch
Bug #786213 [src:ezmlm-browse] ezmlm-browse: deprecation of python-support
Added tag(s) sid and stretch.
> tags 786194 + sid
Bug #786194 [src:zorp] zorp: deprecation of python-support
Added tag(s) sid.
> tags 786183 + sid stretch
Bug #786183 [src:mimms] mimms: deprecation of python-support
Added tag(s) stretch and sid.
> tags 786173 + sid stretch
Bug #786173 [src:python-peak.rules] python-peak.rules: deprecation of 
python-support
Added tag(s) stretch and sid.
> tags 786166 + sid stretch
Bug #786166 {Done: Mattia Rizzolo } [src:python-fixtures] 
python-fixtures: deprecation of python-support
Added tag(s) sid and stretch.
> tags 786145 + sid stretch
Bug #786145 [src:openshot] openshot: deprecation of python-support
Added tag(s) stretch and sid.
> tags 786165 + sid stretch
Bug #786165 [src:gbirthday] gbirthday: deprecation of python-support
Added tag(s) stretch and sid.
> tags 786150 + sid stretch
Bug #786150 [src:gextractwinicons] gextractwinicons: deprecation of 
python-support
Added tag(s) sid and stretch.
> tags 786149 + sid stretch
Bug #786149 [src:pivy] pivy: deprecation of python-support
Added tag(s) stretch and sid.
> tags 786141 + sid stretch
Bug #786141 [src:gnome-hearts] gnome-hearts: deprecation of python-support
Added tag(s) sid and stretch.
> tags 786138 + sid stretch
Bug #786138 [src:moap] moap: deprecation of python-support
Added tag(s) sid and stretch.
> tags 786100 + sid stretch
Bug #786100 [src:gnome-osd] gnome-osd: deprecation of python-support
Added tag(s) stretch and sid.
> tags 786086 + sid
Bug #786086 [src:mumble-django] mumble-django: deprecation of python-support
Added tag(s) sid.
> tags 786083 + sid stretch
Bug #786083 [src:pythontracer] pythontracer: deprecation of python-support
Added tag(s) stretch and sid.
> tags 786077 + sid stretch
Bug #786077 [src:opensesame] opensesame: deprecation of python-support
Added tag(s) sid and stretch.
> tags 786071 + sid stretch
Bug #786071 [src:py-asterisk] py-asterisk: deprecation of python-support
Added tag(s) stretch and sid.
> tags 786065 + sid stretch
Bug #786065 [src:gnome-schedule] gnome-schedule: deprecation of python-support
Added tag(s) stretch and sid.
> tags 786054 + sid stretch
Bug #786054 [src:gnomecatalog] gnomecatalog: deprecation of python-support
Added tag(s) stretch and sid.
> tags 786048 + sid
Bug #786048 [src:conduit] conduit: deprecation of python-support
Added tag(s) sid.
> tags 786042 + sid stretch
Bug #786042 [src:jack] jack: deprecation of python-support
Added tag(s) stretch and sid.
> tags 786026 + sid
Bug #786026 [src:liquidsoap] liquidsoap: deprecation of python-support
Added tag(s) sid.
> tags 785993 + sid stretch
Bug #785993 [src:python-carrot] python-carrot: deprecation of python-support
Added tag(s) stretch and sid.
> tags 785991 + sid
Bug #785991 [src:dipy] dipy: deprecation of python-support
Added tag(s) sid.
> tags 637262 + sid stretch
Bug #637262 [src:urlgrabber] urlgrabber: Please update to dh_python2 for 
deprecation of dh_pysupport
Bug #786144 [src:urlgrabber] urlgrabber: deprecation of python-support
Added tag(s) stretch and sid.
Added tag(s) stretch and sid.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
637262: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=637262
785991: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=785991
785993: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=785993
786026: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=786026
786042: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=786042
786048: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=786048
786054: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=786054
786065: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=786065
786071: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=786071
786077: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=786077
786083: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=786083
786086: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=786086
786100: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=786100
786138: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=786138
786141: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=786141
786144: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=786144
786145: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=786145
786149: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=786149

Bug#807989: gnukhata-core-engine: fails to install: psql: ALTER: command not found

[Andreas Beckmann]

Package: gnukhata-core-engine
Version: 2.6.0-2
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

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

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

  Selecting previously unselected package gnukhata-core-engine.
  (Reading database ... 
(Reading database ... 12312 files and directories currently installed.)
  Preparing to unpack .../gnukhata-core-engine_2.6.0-2_all.deb ...
  Unpacking gnukhata-core-engine (2.6.0-2) ...
  Processing triggers for systemd (228-2) ...
  Setting up gnukhata-core-engine (2.6.0-2) ...
  dbconfig-common: writing config to 
/etc/dbconfig-common/gnukhata-core-engine.conf
  
  Creating config file /etc/dbconfig-common/gnukhata-core-engine.conf with new 
version
  creating postgres user gnukhata:  success.
  verifying creation of user: success.
  creating database gnukhata: success.
  verifying database gnukhata exists: success.
  dbconfig-common: flushing administrative password
  Creating/updating gnukhata user account...
  Allow gnukhata user to create databases...
  psql: ALTER: command not found
  dpkg: error processing package gnukhata-core-engine (--configure):
   subprocess installed post-installation script returned error exit status 1
  Processing triggers for systemd (228-2) ...
  Errors were encountered while processing:
   gnukhata-core-engine


cheers,

Andreas


gnukhata-core-engine_2.6.0-2.log.gz
Description: application/gzip

Processed: blocks

[Debian Bug Tracking System]

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

> # these FTBFS blocks the transition away from pysupport
> # pystatgrab
> block 786158 by 735573
Bug #786158 [src:pystatgrab] pystatgrab: deprecation of python-support
786158 was not blocked by any bugs.
786158 was blocking: 746741
Added blocking bug(s) of 786158: 735573
> # liquidsoap
> block 786026 by 802055
Bug #786026 [src:liquidsoap] liquidsoap: deprecation of python-support
786026 was not blocked by any bugs.
786026 was blocking: 746741
Added blocking bug(s) of 786026: 802055
> # zorp
> block 786194 by 805112
Bug #786194 [src:zorp] zorp: deprecation of python-support
786194 was not blocked by any bugs.
786194 was blocking: 746741
Added blocking bug(s) of 786194: 805112
> # pyimport-relative
> block 786259 by 713086
Bug #786259 [src:pyimport-relative] pyimport-relative: deprecation of 
python-support
786259 was not blocked by any bugs.
786259 was blocking: 746741
Added blocking bug(s) of 786259: 713086
> # openmeeg
> block 786335 by 730904
Bug #786335 [src:openmeeg] openmeeg: deprecation of python-support
786335 was not blocked by any bugs.
786335 was blocking: 746741
Added blocking bug(s) of 786335: 730904
> --
Stopping processing here.

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

Bug#807994: python-django-south: Incompatable with Django >= 1.7

[Brian May]

Source: python-django-south
Version: 1.0.0-1
Severity: grave
Justification: renders package unusable

Package is broken with Django 1.7+ in Debian and not fit for release. It
will not get fixed, as the functionality has been replaced by the Django
1.7 migration mechanism.

I was going to file a bug report to remove the package, however then I
noticed there are packages that still depend on this package.

(sid-amd64)root@prune:/home/brian# apt-cache rdepends
python-django-south
python-django-south
Reverse Depends:
  bcfg2-web
  python-django-voting
  python-django-threadedcomments
  lava-server
  python-django-sitetree
  python-django-picklefield


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

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

Bug#786287: marked as done (turtleart: deprecation of python-support)

[Debian Bug Tracking System]

Your message dated Tue, 15 Dec 2015 04:49:36 +
with message-id 
and subject line Bug#786287: fixed in turtleart 98-1.1
has caused the Debian Bug report #786287,
regarding turtleart: 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.)


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

We believe that the bug you reported is fixed in the latest version of
turtleart, 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 turtleart 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 01:51:38 +
Source: turtleart
Binary: turtleart sugar-turtleart-activity
Architecture: source
Version: 98-1.1
Distribution: unstable
Urgency: medium
Maintainer: Matthew Gallagher 
Changed-By: Mattia Rizzolo 
Description:
 sugar-turtleart-activity - a LOGO-like tool for teaching programming - Sugar 
activity
 turtleart  - a LOGO-like tool for teaching programming
Closes: 786287
Changes:
 turtleart (98-1.1) unstable; urgency=medium
 .
   * Non-maintainer upload.
   * Build using dh-python instead of python-support.  Closes: #786287
Checksums-Sha1:
 cfe359a20947ded4f3177c0e9a72da23385be7ec 2003 turtleart_98-1.1.dsc
 cbbb7794ed1ae871aac0f434f95d3bc2386aad54 11440 turtleart_98-1.1.debian.tar.xz
Checksums-Sha256:
 8ef4b7b19d3a81954e6e744c04ea419e6dd32c5a0ccb34aa93339196fb8f216b 2003 
turtleart_98-1.1.dsc
 df15331abdfebe3e10238e7b22305e7f64733099537a1015c5af2608a5c4edf4 11440 
turtleart_98-1.1.debian.tar.xz
Files:
 f3b3174a1581f788e5f91faec7b03fa7 2003 misc optional turtleart_98-1.1.dsc
 72638c50a6db34f4e3eb8e463c90fb0b 11440 misc optional 
turtleart_98-1.1.debian.tar.xz

-BEGIN PGP SIGNATURE-
Version: GnuPG v1

iQIcBAEBCAAGBQJWb3VcAAoJEEsEP825REVASpsQAKzQC62igjCCSg4fks8BWZEh
bNdjLzb6XG8ECw99J7f5cxtFt+Lyrpd97T1gRyRa3fs03cVMGafn1nZkCYvJNp1r
1pdGEUj5FnBRv4c2XMkCCe5PQga3HsKscOSFNs94k8MvXdOly3vUHJc+kKTwYJXr
pYSWWhw2xT7ddhPXML9F+yymf9hgiwXskrU+79lIV9+I7j157xvUKEouuFQ4uPx+
eiYIyAXH9XKoJZUAio04/IOdgoMMF3DrgIzsVm187T/OfgU1FFCb3ZgHq0i6GB7x
/i+lS4EfhNyxas9mMpm8PGp1ufWaArxKpPiFSyaJHESvr6fBJ9nmLfb+/rO8rf3y
HQkOLnEdYbdZwIvJahfznYu8P3QtPEWvc9KOor14mFw8nkKO2yV6aLu1Lc/Vtc1v
fTUhZmTduoK6ZG4feTYRJRoraVwkmkuwRBoyDu4s/MCubKPJjL+uTKuhFHD4wh81
FSvH6c08emXnFRfNE2MxNioOC97ouVLZ3+bhfMZdTsLXGB1YhdaoJCpbc83UGPzq
/wVeyPhWe5lmqbR1Lf3/hOhMHJhOELBEl0X7+hQ1yy2e6bbGjnWxwhNS21Lxn6xw
abhyfbxciHg3gx9W0d/mAsCeM7S7RaOhFhV5UdHU2FbVG7s3I9nIKRw9eWM5C18y
lT0EsPqX/x+jGMijaBvB
=NSyk
-END PGP SIGNATURE End Message ---

Bug#637262: marked as done (urlgrabber: Please update to dh_python2 for deprecation of dh_pysupport)

[Debian Bug Tracking System]

Your message dated Tue, 15 Dec 2015 04:49:40 +
with message-id 
and subject line Bug#637262: fixed in urlgrabber 3.9.1-4.2
has caused the Debian Bug report #637262,
regarding urlgrabber: Please update to dh_python2 for deprecation of 
dh_pysupport
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.)


-- 
637262: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=637262
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: urlgrabber
Version: 3.9.1-4
Severity: normal
Tags: patch
User: ubuntu-de...@lists.ubuntu.com
Usertags: origin-ubuntu oneiric ubuntu-patch

As per http://wiki.debian.org/Python/TransitionToDHPython2, dh_pysupport
is now deprecated. Attached is a patch making the transition to dh_python2.

Thanks for considering the patch.


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

Kernel: Linux 3.0.0-8-generic (SMP w/4 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
diff -Nru urlgrabber-3.9.1/debian/control urlgrabber-3.9.1/debian/control
--- urlgrabber-3.9.1/debian/control	2010-07-08 13:38:19.0 -0400
+++ urlgrabber-3.9.1/debian/control	2011-08-09 19:21:02.0 -0400
@@ -3,7 +3,7 @@
 Priority: optional
 Maintainer: Kevin Coyner 
 Uploaders: Debian Python Modules Team 
-Build-Depends: debhelper (>= 7.4~), python-all, python-support (>= 0.6), python-pycurl, quilt (>= 0.46-7~)
+Build-Depends: debhelper (>= 7.4~), python-all (>= 2.6.6-3~), python-pycurl, quilt (>= 0.46-7~)
 Standards-Version: 3.8.4
 Homepage: http://urlgrabber.baseurl.org/
 Vcs-Svn: svn://svn.debian.org/python-modules/packages/urlgrabber/trunk/
diff -Nru urlgrabber-3.9.1/debian/rules urlgrabber-3.9.1/debian/rules
--- urlgrabber-3.9.1/debian/rules	2010-07-08 13:39:10.0 -0400
+++ urlgrabber-3.9.1/debian/rules	2011-08-09 18:58:53.0 -0400
@@ -9,7 +9,7 @@
 # Uncomment this to turn on verbose mode.
 #export DH_VERBOSE=1
 %:
-	dh --with quilt $@
+	dh $@ --with quilt,python2
 
 
 PYVERS = $(shell pyversions -r)
@@ -49,7 +49,7 @@
 	dh_prep
 	dh_installdirs
 	# Add here commands to install the package into debian/urlgrabber.
-	python setup.py install --prefix=/usr --root=$(CURDIR)/debian/python-urlgrabber
+	python setup.py install --prefix=/usr --root=$(CURDIR)/debian/python-urlgrabber --install-layout=deb
 	# remove unneeded documents installed by setup.py
 	-rm -rf $(CURDIR)/debian/python-urlgrabber/usr/share/doc/urlgrabber-3*
 
@@ -64,7 +64,7 @@
 	dh_strip
 	dh_compress
 	dh_fixperms
-	dh_pysupport
+	dh_python2
 	dh_installdeb
 	dh_shlibdeps
 	dh_gencontrol
--- End Message ---
--- Begin Message ---
Source: urlgrabber
Source-Version: 3.9.1-4.2

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

Debian distribution maintenance software
pp.
Mattia Rizzolo  (supplier of updated urlgrabber 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 02:14:39 +
Source: urlgrabber
Binary: python-urlgrabber
Architecture: source
Version: 3.9.1-4.2
Distribution: unstable
Urgency: medium
Maintainer: Kevin Coyner 
Changed-By: Mattia Rizzolo 
Description:
 python-urlgrabber - A high-level cross-protocol url-grabber
Closes: 637262
Changes:
 urlgrabber (3.9.1-4.2) unstable; urgency=medium
 .
   * Non-maintainer upload.
   * Build using dh-python instead of python-support.  Closes: #637262
   * Update Vcs-* fields after DPMT migration to git.
Checksums-Sha1:
 3c3c9a27898310a4d16c63c2dd21e9cfcc3f6ffb 2032 urlgrabber_3.9.1-4.2.dsc
 a94ddfa10a03dde110f2cb0771d798493a695eb4 10688 
urlgrabber_3.9.1-4.2.debian.tar.xz
Checksums-Sha256:
 676d20ee4ef5f808ec56f7d62c47346f9881f46ed13f17a4bedb503de2bfe420 2032 
urlgrabber_3.9.1-4.2.dsc
 

Bug#786144: marked as done (urlgrabber: deprecation of python-support)

[Debian Bug Tracking System]

Your message dated Tue, 15 Dec 2015 04:49:40 +
with message-id 
and subject line Bug#637262: fixed in urlgrabber 3.9.1-4.2
has caused the Debian Bug report #637262,
regarding urlgrabber: 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.)


-- 
637262: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=637262
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: urlgrabber
Version: 3.9.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: urlgrabber
Source-Version: 3.9.1-4.2

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

Debian distribution maintenance software
pp.
Mattia Rizzolo  (supplier of updated urlgrabber 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 02:14:39 +
Source: urlgrabber
Binary: python-urlgrabber
Architecture: source
Version: 3.9.1-4.2
Distribution: unstable
Urgency: medium
Maintainer: Kevin Coyner 
Changed-By: Mattia Rizzolo 
Description:
 python-urlgrabber - A high-level cross-protocol url-grabber
Closes: 637262
Changes:
 urlgrabber (3.9.1-4.2) unstable; urgency=medium
 .
   * Non-maintainer upload.
   * Build using dh-python instead of python-support.  Closes: #637262
   * Update Vcs-* fields after DPMT migration to git.
Checksums-Sha1:
 3c3c9a27898310a4d16c63c2dd21e9cfcc3f6ffb 2032 urlgrabber_3.9.1-4.2.dsc
 a94ddfa10a03dde110f2cb0771d798493a695eb4 10688 
urlgrabber_3.9.1-4.2.debian.tar.xz
Checksums-Sha256:
 676d20ee4ef5f808ec56f7d62c47346f9881f46ed13f17a4bedb503de2bfe420 2032 
urlgrabber_3.9.1-4.2.dsc
 8a17a5140d96f56d31b4d4adedc38cbe7966e887c73ce30f8da5941a831a9bc4 10688 
urlgrabber_3.9.1-4.2.debian.tar.xz
Files:
 575040c53a385c51ff3bee04ef00fbab 2032 python optional urlgrabber_3.9.1-4.2.dsc
 d8cfe758029cf72362b3edfd8ac5f5ab 10688 python optional 
urlgrabber_3.9.1-4.2.debian.tar.xz

-BEGIN PGP SIGNATURE-
Version: GnuPG v1

iQIcBAEBCAAGBQJWb3fiAAoJEEsEP825REVAZdQP/16V4iNuo6CvERdqXUoAuTxm
vnh0NZuqGIg7JOLqAxZGgP3u26F+AdOLeMu6c62wRBh49JCP7ev4aPUhMEqpbpeC
Z+NhM6c4TlpIx2MfLs74yZBNCB+7DNjN2iqI1NIvJzucFcmFKOHWteOW3z7xM6lh
Q18mzTXSTddRpbc7xhv9iIf3Swc3MxLhykqmYc32v6PTdIND9z8fFPBm4piFI3le
7IP2w7kJyY74lD3qE+3A2ffM4xXqe3w3IhLyuEdxxTVRODnA0YwpLCMaViaBQyUb
sutJi2bAErc/OtomFzr7DhQxXohe8er7zg0bB1GSiXpSaS0ZYvAzJ3dseRZbMGGm
AJRXTOfa7dChR2AfAX/1AsAMYCF7CrhQMmwIjmDBr8T2Qviq91xq+QjFnlMVSmUM
HmerVY0A+0VWlzOck5fXARqCFGmrC7RGhpHlNc0c9rqigckUAZyQyPaGbQpuS9Bx
tUG3zWtnp2tggTmgcG0X0oGTQKsThc66s5FU8ziaQ20jK2H9FRZczV0iHBdVgQ4E
vFCgHjTV7T4Ig8pLeiTcNRWQAJLUe8gb4qTWk8+OLPaBskzCKDr0Im0oVhHflT5h
e+kv/+MKRpqLNkYApHwPs1MtIMuj37SYMr4MWt9J9jyomY6RjArcxsw3NQtEBClx
BLZlUHJWT75MF5VwpbtB
=AErT
-END PGP SIGNATURE End Message ---

Processed: this patch ain't really useful

[Debian Bug Tracking System]

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

> tag 785990 - patch
Bug #785990 [src:distcc] distcc: deprecation of python-support
Removed tag(s) patch.
> --
Stopping processing here.

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

Bug#796466: marked as done (pepper: FTBFS: error: ‘svn_sort__hash’ was not declared in this scope)

[Debian Bug Tracking System]

Your message dated Tue, 15 Dec 2015 05:31:35 +
with message-id 
and subject line Bug#796466: fixed in pepper 0.3.3-1
has caused the Debian Bug report #796466,
regarding pepper: FTBFS: error: ‘svn_sort__hash’ was not declared in this scope
to be marked as done.

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

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


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

Dear Maintainer,

The package fails to build:

backends/subversion.cpp: In member function ‘virtual std::vector 
SubversionBackend::tags()’:
backends/subversion.cpp:829:94: error: ‘svn_sort__hash’ was not declared in 
this scope
  apr_array_header_t *array = svn_sort__hash(dirents, 
_sort_compare_items_lexically,  pool);

  ^
In file included from /usr/include/subversion-1/svn_client.h:37:0,
 from backends/subversion.cpp:22:
/usr/include/apr-1.0/apr_tables.h:141:59: error: invalid use of incomplete type 
‘struct svn_sort__item_t’
 #define APR_ARRAY_IDX(ary,i,type) (((type *)(ary)->elts)[i])
   ^
backends/subversion.cpp:831:29: note: in expansion of macro ‘APR_ARRAY_IDX’
   svn_sort__item_t *item = _ARRAY_IDX(array, i, svn_sort__item_t);
 ^
In file included from backends/subversion.cpp:28:0:
/usr/include/subversion-1/svn_sorts.h:55:16: note: forward declaration of 
‘struct svn_sort__item_t’
 typedef struct svn_sort__item_t svn_sort__item_t;
^
backends/subversion.cpp:832:68: error: invalid use of incomplete type 
‘svn_sort__item_t {aka struct svn_sort__item_t}’
   svn_dirent_t *dirent = (svn_dirent_t *)apr_hash_get(dirents, item->key, 
item->klen);
^
In file included from backends/subversion.cpp:28:0:
/usr/include/subversion-1/svn_sorts.h:55:16: note: forward declaration of 
‘svn_sort__item_t {aka struct svn_sort__item_t}’
 typedef struct svn_sort__item_t svn_sort__item_t;
^

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

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

Kernel: Linux 3.19.0-23-generic (SMP w/8 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)
--- End Message ---
--- Begin Message ---
Source: pepper
Source-Version: 0.3.3-1

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

Debian distribution maintenance software
pp.
Antoine Beaupré  (supplier of updated pepper 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 21:39:58 -0500
Source: pepper
Binary: pepper
Architecture: source amd64
Version: 0.3.3-1
Distribution: unstable
Urgency: medium
Maintainer: Antoine Beaupré 
Changed-By: Antoine Beaupré 
Description:
 pepper - Source code repository statistics and report tool
Closes: 796466
Changes:
 pepper (0.3.3-1) unstable; urgency=medium
 .
   * New upstream release (Closes: #796466)
   * Update standards version to 3.9.6, no change
   * Update watch and homepage URLs to follow upstream move to github
   * Drop ld --as-needed patch, integrated upstream
Checksums-Sha1:
 2f671184a202966463c986e8bb6c06e1ffe39860 1969 pepper_0.3.3-1.dsc
 a62447794801dbb4027943da5d1d7127a68bc677 189564 pepper_0.3.3.orig.tar.gz
 89c9f5e4b9adc0e3fe3d4767a233fd46baa58f7d 3368 pepper_0.3.3-1.debian.tar.xz
 1e43a73dc185cbdf9c18589c7dc702920c9fecb8 7494 pepper_0.3.3-1_amd64.deb
Checksums-Sha256:
 

Bug#786120: marked as done (miro: deprecation of python-support)

[Debian Bug Tracking System]

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


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

We believe that the bug you reported is fixed in the latest version of
miro, 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 miro 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 03:43:36 +
Source: miro
Binary: miro miro-data
Architecture: source
Version: 6.0-1.2
Distribution: unstable
Urgency: medium
Maintainer: Uwe Hermann 
Changed-By: Mattia Rizzolo 
Description:
 miro   - GTK+ based RSS video aggregator
 miro-data  - GTK+ based RSS video aggregator data files
Closes: 786120
Changes:
 miro (6.0-1.2) unstable; urgency=medium
 .
   * Non-maintainer upload.
   * Build using dh-python instead of python-support.  Closes: #786120
   * Remove unused lintian override on build-depends-on-obsolete-package.
   * Run wrap-and-sort.
Checksums-Sha1:
 26fc0f68ff9b94fa6d52c430097a5e2370074272 1872 miro_6.0-1.2.dsc
 28cf8d022d18e409b7cb66089e088dccc6898ae7 16276 miro_6.0-1.2.debian.tar.xz
Checksums-Sha256:
 850034dcbfd31a77a2d710d71023a48fa75df6a774338f67ae6d11a8627ce054 1872 
miro_6.0-1.2.dsc
 2efeaae4138663bd67d04178d99ebafa326de7dd16e15c3a0c7cf22b2374afa3 16276 
miro_6.0-1.2.debian.tar.xz
Files:
 8a4d5999ae0f60181947a31b943c3212 1872 net extra miro_6.0-1.2.dsc
 d0999513c0d912423d226ca23cf8a40f 16276 net extra miro_6.0-1.2.debian.tar.xz

-BEGIN PGP SIGNATURE-
Version: GnuPG v1

iQIcBAEBCAAGBQJWb4yEAAoJEEsEP825REVA6dwQAL4zVoS4gry+9mHPp25vFL8V
KslfE1k0EpodW5iGhJLUOnhB5dN4Mty03B2Y166w6Y/Ety9Q6Do1qWFObROe2e8u
jj9c3rOaS8PQQtbnlbzIvb0Abd5PD5W57BxYgjfRJlB11BT4pPFboxQ89SvO+5nR
zG7879jdp2Dlz7jIvs9kj5iqktLHgegd3SRq57fmy5atdB8gHxkopYJFBMUgTcK6
RfEaxDOn0+0rA9nidiU3D02YNh7uxrPGnf2vlKXSVFNnDGa8x1AQQNRJ6dVc7w6l
w38H8M4vDhL02fZsI9DbO/O3p8QPpxVRwQ1lJtjGwWdodw2LyuBa1j6OfZiJHjye
/pyHdCj9gfHG94BcztutTjnT6FFvLIhCbisda7qY7HDrgG+NebFMjVWslYqPBOPI
x7h2vFtsirhyLxsOiLI1EynydUiJFjkyKSJUKmL7JTQhYgSlu3s8SiR7K2b7Ku1W
jPswyjuuLkYR56r59+q9eKSOPzBtcgQttP4zvAUezCe+2uwPPpD9jSkC0F1f5L+o
oRacjNqTYu1WPOcGGBdt5haTC7cWfWTdI35GltDkKZYWhEoniIEefwp145+7fydn
ZzfmabW/wZglmFi8aIs6cg9X5Qj1tO+JfBfA8RyCbZM/IHPsAuG6E1h/4PGJfh8H
1+SofhG6RgqR/bTV2crO
=HR86
-END PGP SIGNATURE End Message ---

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

[Yuxuan Wang]

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

Processed: blasr: /usr/bin/blasr - No such file or directory

[Debian Bug Tracking System]

Processing control commands:

> tag -1 + pending
Bug #807985 [blasr] blasr: /usr/bin/blasr - No such file or directory
Added tag(s) pending.

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

Bug#807985: blasr: /usr/bin/blasr - No such file or directory

[Afif Elghraoui]

Package: blasr
Version: 0~20150724+git3ca7fe8-1+b3
Severity: grave
Control: tag -1 + pending

The package appears to have been improperly linked against its
libraries, rendering the package completely unusable:

$ which blasr
/usr/bin/blasr
$ blasr --help
bash: /usr/bin/blasr: No such file or directory

$ which sawriter
/usr/bin/sawriter
$ sawriter
bash: /usr/bin/sawriter: No such file or directory


I am preparing an upload to resolve this problem, but I think this
should be documented in the BTS.

-- 
Afif Elghraoui | عفيف الغراوي
http://afif.ghraoui.name

Bug#807988: python-hypothesis: fails to install: SyntaxError: invalid syntax in /usr/lib/python2.7/dist-packages/hypothesis/internal/compat3.py

[Andreas Beckmann]

Package: python-hypothesis
Version: 1.16.0-1
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

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

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

  Selecting previously unselected package python-hypothesis.
  (Reading database ... 
(Reading database ... 8169 files and directories currently installed.)
  Preparing to unpack .../python-hypothesis_1.16.0-1_all.deb ...
  Unpacking python-hypothesis (1.16.0-1) ...
  Setting up python-hypothesis (1.16.0-1) ...
File "/usr/lib/python2.7/dist-packages/hypothesis/internal/compat3.py", 
line 23
  raise exc from None
   ^
  SyntaxError: invalid syntax
  
  dpkg: error processing package python-hypothesis (--configure):
   subprocess installed post-installation script returned error exit status 101
  Errors were encountered while processing:
   python-hypothesis


cheers,

andreas


python-hypothesis_1.16.0-1.log.gz
Description: application/gzip

Bug#807546: not quite fixed in alfred 2015.2-1

[Petter Reinholdtsen]

Control: severity -1 important
Control: reopen -1
Control: found -1 2015.2-1

[Steffen Moeller]
>* Likely-fixed: Builds on non-linux systems (Closes: #807546)

The build still fail on hurd and kfreebsd.  Reopening.  This time
with the severity I believe is appropriate for a build failure
on an architecture where it never built before in Debian.

-- 
Happy hacking
Petter Reinholdtsen

Processed: Bug#807546: not quite fixed in alfred 2015.2-1

[Debian Bug Tracking System]

Processing control commands:

> severity -1 important
Bug #807546 {Done: Steffen Moeller } [alfred] [alfred] 
Fails to build on non-linux systems
Severity set to 'important' from 'grave'
> reopen -1
Bug #807546 {Done: Steffen Moeller } [alfred] [alfred] 
Fails to build on non-linux systems
'reopen' may be inappropriate when a bug has been closed with a version;
all fixed versions will be cleared, and you may need to re-add them.
Bug reopened
No longer marked as fixed in versions alfred/2015.2-1.
> found -1 2015.2-1
Bug #807546 [alfred] [alfred] Fails to build on non-linux systems
Marked as found in versions alfred/2015.2-1.

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

Bug#803300: prepare for giflib5

[Alberto Luaces]

"Manuel A. Fernandez Montecelo"  writes:

> Hi all,
>
> 2015-12-13 15:33 GMT+00:00 Sebastiaan Couwenberg :
>> On Wed, 28 Oct 2015 16:02:40 +0100 Matthias Klose wrote:
>>> For the latter two options, please see a patch at
>>> http://launchpadlibrarian.net/222944251/openscenegraph_3.2.1-7ubuntu2_3.2.1-7ubuntu3.diff.gz
>>
>> Upstream has fixed the giflib5 support a bit differently [0][1].
>>
>> The attached debdiff uses the upstream changes for giflib 5.x instead of
>> those applied in Ubuntu.
>>
>> Please include these changes in openscenegraph (3.2.1-9) to prevent
>> testing autoremoval of openscenegraph and all its reverse dependencies
>> because of this RC bug.
>>
>> [0]
>> https://github.com/openscenegraph/osg/commit/afb442fccd182cfe8608f43394af016f6723f97a
>> [1]
>> https://github.com/openscenegraph/osg/commit/18213bfb67d464715af618fd8c73549f749625b9
>
> Thanks both.
>
> I can work on this towards the end of next week (17-20th or so), not
> before.  I don't know if Alberto will be able to upload before then.
>
> There are a few other pending things to fix, so I think that it would
> be better that either Alberto or I get around to work on this and fix
> the issues in a single upload, so the less powerfull arches are not
> taxed too much.  The removal from testing will happen in a month, so
> there should be plenty of time.

I intend to finish a new release in short, so count on having it before
the scheduled removal.

Regards,

Alberto

Bug#807915: mono-addins: FTBFS with new mono, upgrade to 1.2 release?

[Dimitri John Ledkov]

X-Debbugs-CC: Dimitri John Ledkov <x...@debian.org>
Source: mono-addins
Severity: serious

mono-addins ftbfs in unstable.

maybe it should be upgraded to 1.2 release from github? I haven't tried
it yet - https://github.com/mono/mono-addins/releases

(note there have been 10 commits to master since 1.2 release)

Build log attached.

Last error is:

Building Mono.Addins.csproj
CSC: error CS0518: The predefined type `System.Object' is not defined
or imported
CSC: error CS0518: The predefined type `System.ValueType' is not
defined or imported
CSC: error CS0518: The predefined type `System.Attribute' is not
defined or imported
CSC: error CS0518: The predefined type `System.Int32' is not defined or imported
CSC: error CS0518: The predefined type `System.UInt32' is not defined
or imported
CSC: error CS0518: The predefined type `System.Int64' is not defined or imported
CSC: error CS0518: The predefined type `System.UInt64' is not defined
or imported
CSC: error CS0518: The predefined type `System.Single' is not defined
or imported
CSC: error CS0518: The predefined type `System.Double' is not defined
or imported
CSC: error CS0518: The predefined type `System.Char' is not defined or imported
CSC: error CS0518: The predefined type `System.Int16' is not defined or imported
CSC: error CS0518: The predefined type `System.Decimal' is not defined
or imported
CSC: error CS0518: The predefined type `System.Boolean' is not defined
or imported
CSC: error CS0518: The predefined type `System.SByte' is not defined or imported
CSC: error CS0518: The predefined type `System.Byte' is not defined or imported
CSC: error CS0518: The predefined type `System.UInt16' is not defined
or imported
CSC: error CS0518: The predefined type `System.String' is not defined
or imported
CSC: error CS0518: The predefined type `System.Enum' is not defined or imported
CSC: error CS0518: The predefined type `System.Delegate' is not
defined or imported
CSC: error CS0518: The predefined type `System.MulticastDelegate' is
not defined or imported
CSC: error CS0518: The predefined type `System.Void' is not defined or imported
CSC: error CS0518: The predefined type `System.Array' is not defined or imported
CSC: error CS0518: The predefined type `System.Type' is not defined or imported
CSC: error CS0518: The predefined type
`System.Collections.IEnumerator' is not defined or imported
CSC: error CS0518: The predefined type
`System.Collections.IEnumerable' is not defined or imported
CSC: error CS0518: The predefined type `System.IDisposable' is not
defined or imported
CSC: error CS0518: The predefined type `System.IntPtr' is not defined
or imported
CSC: error CS0518: The predefined type `System.UIntPtr' is not defined
or imported
CSC: error CS0518: The predefined type `System.RuntimeFieldHandle' is
not defined or imported
CSC: error CS0518: The predefined type `System.RuntimeTypeHandle' is
not defined or imported
CSC: error CS0518: The predefined type `System.Exception' is not
defined or imported
make[2]: *** [csproj_build] Error 1
Makefile:567: recipe for target 'csproj_build' failed
make[2]: Leaving directory
'/«BUILDDIR»/mono-addins-1.0+git20130406.adcd75b/Mono.Addins'
make[1]: *** [all-recursive] Error 1
Makefile:348: recipe for target 'all-recursive' failed
make[1]: Leaving directory '/«BUILDDIR»/mono-addins-1.0+git20130406.adcd75b'
dh_auto_build: make -j1 returned exit code 2
make: *** [build] Error 2
debian/rules:40: recipe for target 'build' failed
dpkg-buildpackage: error: debian/rules build gave error exit status 2


-- 
Regards,

Dimitri.


mono-addins_1.0+git20130406.adcd75b-3_amd64-20151214-1318.build.xz
Description: application/xz

Bug#805918: marked as done (nvidia-graphics-drivers-legacy-304xx: CVE-2015-7869: Unsanitized User Mode Input)

[Debian Bug Tracking System]

Your message dated Mon, 14 Dec 2015 13:34:25 +
with message-id 
and subject line Bug#805918: fixed in nvidia-graphics-drivers-legacy-304xx 
304.131-2
has caused the Debian Bug report #805918,
regarding nvidia-graphics-drivers-legacy-304xx: CVE-2015-7869: Unsanitized User 
Mode Input
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.)


-- 
805918: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=805918
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: nvidia-graphics-drivers
Version: 304.22-1
Severity: serious
Tags: security

http://nvidia.custhelp.com/app/answers/detail/a_id/3808
http://people.canonical.com/~ubuntu-security/cve/2015/CVE-2015-7869.html

[...] This report also details an advisory regarding integer overflow issues
in the underlying kernel mode driver.

[...] The integer overflow issues affect both Windows and Linux-based GPU
drivers. These issues affect all GPU products and are not specific to
any GPU class device.


Andreas
--- End Message ---
--- Begin Message ---
Source: nvidia-graphics-drivers-legacy-304xx
Source-Version: 304.131-2

We believe that the bug you reported is fixed in the latest version of
nvidia-graphics-drivers-legacy-304xx, 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 805...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Andreas Beckmann  (supplier of updated 
nvidia-graphics-drivers-legacy-304xx 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 14:11:22 +0100
Source: nvidia-graphics-drivers-legacy-304xx
Binary: nvidia-legacy-304xx-driver xserver-xorg-video-nvidia-legacy-304xx 
libgl1-nvidia-legacy-304xx-glx libgl1-nvidia-legacy-304xx-glx-i386 
nvidia-legacy-304xx-alternative nvidia-legacy-304xx-kernel-support 
nvidia-legacy-304xx-kernel-dkms nvidia-legacy-304xx-kernel-source
Architecture: source
Version: 304.131-2
Distribution: unstable
Urgency: medium
Maintainer: Debian NVIDIA Maintainers 
Changed-By: Andreas Beckmann 
Description:
 libgl1-nvidia-legacy-304xx-glx - NVIDIA binary OpenGL 
libraries${nvidia:LegacyDesc}
 libgl1-nvidia-legacy-304xx-glx-i386 - NVIDIA binary OpenGL 32-bit 
libraries${nvidia:LegacyDesc}
 nvidia-legacy-304xx-alternative - allows the selection of NVIDIA as GLX 
provider
 nvidia-legacy-304xx-driver - NVIDIA metapackage${nvidia:LegacyDesc}
 nvidia-legacy-304xx-kernel-dkms - NVIDIA binary kernel module DKMS 
source${nvidia:LegacyDesc}
 nvidia-legacy-304xx-kernel-source - NVIDIA binary kernel module 
source${nvidia:LegacyDesc}
 nvidia-legacy-304xx-kernel-support - NVIDIA binary kernel module support 
files${nvidia:LegacyDesc}
 xserver-xorg-video-nvidia-legacy-304xx - NVIDIA binary Xorg 
driver${nvidia:LegacyDesc}
Closes: 805918
Changes:
 nvidia-graphics-drivers-legacy-304xx (304.131-2) unstable; urgency=medium
 .
   * Merge changes from 304.131-1 (UNRELEASED).
   * Synchronize packaging with nvidia-graphics-drivers-legacy-340xx 340.96-1:
   * Synchronize packaging with nvidia-graphics-drivers 340.96-3:
 - Use a more generic approach for unloading the modules.
   * Synchronize packaging with nvidia-graphics-drivers 340.96-2:
 - seq-printf.patch: Remove, fixed upstream.
   * Upload to unstable.
 .
 nvidia-graphics-drivers-legacy-304xx (304.131-1) UNRELEASED; urgency=medium
 .
   * New upstream legacy 304xx branch release 304.131 (2015-11-16).
 * Fixed CVE-2015-7869: Unsanitized User Mode Input.  (Closes: #805918)
 - Fixed a bug that could cause texture corruption in some OpenGL
   applications when video memory is exhausted by a combination of
   simultaneously running graphical and compute workloads.
 - Added support for X.Org xserver ABI 20 (xorg-server 1.18).
 * Improved compatibility with recent Linux kernels.
   * Synchronize packaging with nvidia-graphics-drivers 340.96-1:
 - d/control: Make dependencies on nvidia-legacy-304xx-alternative strictly
   versioned to prevent partial upgrades.
   * Synchronize packaging with nvidia-graphics-drivers 304.131-1:
 - 

Bug#680856: marked as done (offlineimap: FTBFS with python3-sphinx: invalid syntax (imaplib2.py, line 376))

[Debian Bug Tracking System]

Your message dated Mon, 14 Dec 2015 13:21:01 +
with message-id 
and subject line Bug#680856: fixed in offlineimap 6.6.0~rc3+dfsg1-1
has caused the Debian Bug report #680856,
regarding offlineimap: FTBFS with python3-sphinx: invalid syntax (imaplib2.py, 
line 376)
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.)


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

Source: offlineimap
Version: 6.5.4-2
Severity: serious
Justification: fails to build from source

If python3-sphinx is installed, but python-sphinx is not, offlineimap 
FTBFS:

| sphinx-build -b html -d html/doctrees doc-src html
| Running Sphinx v1.1.3
| Making output directory...
|
| Configuration error:
| There is a syntax error in your configuration file: invalid syntax 
(imaplib2.py, line 376)
| Did you change the syntax from 2.x to 3.x?
| make[3]: *** [doc] Error 1
| make[2]: *** [doc] Error 2
| make[3]: Leaving directory `/build/offlineimap-E5qchg/offlineimap-6.5.4/docs'
| make[2]: Leaving directory `/build/offlineimap-E5qchg/offlineimap-6.5.4'
| make[1]: *** [override_dh_auto_build] Error 2
| make[1]: Leaving directory `/build/offlineimap-E5qchg/offlineimap-6.5.4'
| make: *** [build] Error 2
| dpkg-buildpackage: error: debian/rules build gave error exit status 2

--
Jakub Wilk


--- End Message ---
--- Begin Message ---
Source: offlineimap
Source-Version: 6.6.0~rc3+dfsg1-1

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

Debian distribution maintenance software
pp.
Ilias Tsitsimpis  (supplier of updated offlineimap 
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, 24 Nov 2015 13:59:19 +0200
Source: offlineimap
Binary: offlineimap
Architecture: source
Version: 6.6.0~rc3+dfsg1-1
Distribution: unstable
Urgency: medium
Maintainer: Ilias Tsitsimpis 
Changed-By: Ilias Tsitsimpis 
Description:
 offlineimap - IMAP/Maildir synchronization and reader support
Closes: 343924 629264 648863 655721 679975 680856 715516 728445 745822 747033 
760960 785594
Changes:
 offlineimap (6.6.0~rc3+dfsg1-1) unstable; urgency=medium
 .
   [ Ilias Tsitsimpis ]
   * New upstream release
 (Closes: #747033, #629264, #745822, #760960, #785594, #648863, #343924)
   * Update build dependencies
 - Add dh-python and python-setuptools, required to build Python modules
 - Remove python-sphinx, since we are not shipping documentation anymore
 - Add asciidoc, xsltproc, docbook-xml and libxml2-utils,
   required to build the manpages (Closes: #680856)
   * Add X-Python-Version field in d/control
   * Bump Standards Version to 3.9.6.
 No changes to the source package.
   * Convert d/copyright to DEP-5 and update its entries (Closes: #655721)
   * Update d/watch file according to wiki.d.o/watch
   * Create a DFSG version of the package
 - Remove non free IETF documents
 - Remove embedded copy of imaplib2
   * Remove improve_man_page patch.
 Manpages have been rewritten.
   * Don't use embedded copy of imaplib2 (Closes: #728445)
   * Add python-imaplib2 to package dependencies
   * Install offlineimapui.7 manpage
   * d/patches: Fix typos in offlineimap(1) manpage
   * Update d/rules to build newer version
 - Use pybuild instead of python_distutils.
 - Don't export OfflineIMAP's Python modules
   Python applications should ship only private modules, according
   to the Debian Python Policy.
 - Disable tests since they require a valid IMAP account.
   * Don't install documentation.
 OfflineIMAP's manual and FAQ have been moved by upstream to another
 package (OfflineIMAP/offlineimap.github.io). Only developer's
 documentation is included, which is not needed to be installed alongside
 this package.
   * Remove python-sqlite from the recommended packages.
 OfflineIMAP uses sqlite3 to access the sqlite database which
 is 

Bug#747033: marked as done (offlineimap uses OpenSSL, causing Debian to violate the GPL when distributing it)

[Debian Bug Tracking System]

Your message dated Mon, 14 Dec 2015 13:21:01 +
with message-id 
and subject line Bug#747033: fixed in offlineimap 6.6.0~rc3+dfsg1-1
has caused the Debian Bug report #747033,
regarding offlineimap uses OpenSSL, causing Debian to violate the GPL when 
distributing it
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.)


-- 
747033: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=747033
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: offlineimap
Version: 6.5.5-0.1
Severity: serious
Justification: 2.3

Dear Maintainer,

offlineimap/imaplib2.py currently uses Python's ssl library, which
pulls in OpenSSL as described here:
https://docs.python.org/2/license.html#openssl

Additionally offlineimap/folder/Maildir.py uses the md5 function from
the ssl library if available, and offlineimap/imaplibutil.py uses the
sha1 function. Both of these also use OpenSSL code. 

The GPL and the OpenSSL license are incompatible. See the following
debian-legal thread for more information.
https://lists.debian.org/debian-legal/2002/10/msg00113.html

Regards,
Simon Fondrie-Teitler

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

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

Versions of packages offlineimap depends on:
ii  libjs-sphinxdoc  1.2.2+dfsg-1
ii  python   2.7.5-5

Versions of packages offlineimap recommends:
ii  python-sqlite  1.0.1-11

Versions of packages offlineimap suggests:
pn  doc-base 
pn  python-kerberos  

-- debconf-show failed
--- End Message ---
--- Begin Message ---
Source: offlineimap
Source-Version: 6.6.0~rc3+dfsg1-1

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

Debian distribution maintenance software
pp.
Ilias Tsitsimpis  (supplier of updated offlineimap 
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, 24 Nov 2015 13:59:19 +0200
Source: offlineimap
Binary: offlineimap
Architecture: source
Version: 6.6.0~rc3+dfsg1-1
Distribution: unstable
Urgency: medium
Maintainer: Ilias Tsitsimpis 
Changed-By: Ilias Tsitsimpis 
Description:
 offlineimap - IMAP/Maildir synchronization and reader support
Closes: 343924 629264 648863 655721 679975 680856 715516 728445 745822 747033 
760960 785594
Changes:
 offlineimap (6.6.0~rc3+dfsg1-1) unstable; urgency=medium
 .
   [ Ilias Tsitsimpis ]
   * New upstream release
 (Closes: #747033, #629264, #745822, #760960, #785594, #648863, #343924)
   * Update build dependencies
 - Add dh-python and python-setuptools, required to build Python modules
 - Remove python-sphinx, since we are not shipping documentation anymore
 - Add asciidoc, xsltproc, docbook-xml and libxml2-utils,
   required to build the manpages (Closes: #680856)
   * Add X-Python-Version field in d/control
   * Bump Standards Version to 3.9.6.
 No changes to the source package.
   * Convert d/copyright to DEP-5 and update its entries (Closes: #655721)
   * Update d/watch file according to wiki.d.o/watch
   * Create a DFSG version of the package
 - Remove non free IETF documents
 - Remove embedded copy of imaplib2
   * Remove improve_man_page patch.
 Manpages have been rewritten.
   * Don't use embedded copy of imaplib2 (Closes: #728445)
   * Add python-imaplib2 to package dependencies
   * Install offlineimapui.7 manpage
   * d/patches: Fix typos in offlineimap(1) manpage
   * Update d/rules to build newer version
 - Use pybuild instead of python_distutils.
 - Don't export OfflineIMAP's Python modules
   Python applications should ship only private modules, according
   to the Debian Python Policy.
 - Disable tests since they require a valid IMAP account.
   * Don't install documentation.
 OfflineIMAP's manual and FAQ 

Bug#805584: libsbml maintenance needs to be enhanced

[Andreas Tille]

Hi Ivo,

I admit I'm not very happy with the way we are cooperating on libsbml
maintenance.  When trying to squash bugs in our advent bug squashing
effort I intended to check the bugs of libsbml (1 RC tagged patch, 1
important tagged patch and 1 important where bug submitter requested
confirmation).  So in principle all these bugs are quite simple - but no
reply has hit the BTS.  While I assume that you are subscribed to the
maintainer list or at least to the package in the Package Tracking
System (which was now moved to tracker).  Please confirm that you are
at least aware of the three open bugs.

The next thing I'm not happy about is that you are feeding SVN from
time to time with commits all stating

libsbml () UNRELEASED; urgency=medium

and there is no signal for me if this is worth sponsering or not.
Moreover we do not leave paragraphs targeting at UNRELEASED at all - if
there is a new version please take over the changes to have only one
single paragraph targeting at UNRELEASED "distribution" and this should
be the top most paragraph.  (I intended to tell you previously but may
be I forgot to mention this.)

Finally at least your latest commit was not ready to build.  I needed
to refresh the quilt patches from some fuzz - please make sure that
all quilt patches apply cleanly.

To fix things up I applied the patches submitted in BTS and adapted
these to the latest upstream version.  Sorry for the mass-commit - may
be we should switch to Git for libsbml which would be sensible to my
personal policy anyway to use Git in case changes to the upstream
tarball are necessary.

Unfortunately my commit does not build but I'm running out of ideas now
how to tell cmake where to find JAVA_INCLUDE_PATH.  I'm struck by

...
-- Found Doxygen: /usr/bin/doxygen (found version "1.8.9.1")
CMake Warning at docs/CMakeLists.txt:40 (message):
  Creating Documentation with CMake is experimental.  Please consider
  configuring with gnumake, to generate documentation.


CMake Error at docs/CMakeLists.txt:212 (message):
  Cannot generate java documentation, please specify the Java_JAVADOC_JAR.


-- Configuring incomplete, errors occurred!
...


and I wonder whether you might have an idea how to fix this.

Please be so kind to tell me if you also have no idea or no time to fix
this to let me try other means / ask somewhere else for help.  I'd be
also happy if you could make suggestions in general how we could enhance
the sponsee - sponsor relation to guarantee a proper maintenance
according to the standards we have set in the Debian Med team.

Kind regards

  Andreas.


-- 
http://fam-tille.de

Bug#800496: evolution-ews: Unable to store Host URI / OAB URI

[أبو المنتصر لدين اللّه]

Hi All,

On Sun, 15 Nov 2015 06:15:48 +0100 Michael Biebl  wrote:
> On Wed, 30 Sep 2015 09:13:36 +0200 Yusuf Iskenderoglu
>  wrote:
> > Package: evolution-ews
> > Version: 3.16.3-1
> > Severity: grave
> > Justification: renders package unusable
> > 
> > Dear Maintainer,
> > 
> > Currently, evolution cannot access EWS anymore and prevents me from using
> > company mail.
> > 
> 
> Hi, could you please try the latest version 3.18.0 from unstable and
> report back with your findings.
I was updating today my system and was surprised to see evolution-ews gowing out
of the repository if testing. I was using this plugin without any issue for last
few years.

Trying to look for the reason it was removed, I found this bug and consider that
it is unfair to prevent all testing users from this package because an old
version is buggy. So I would propose that we tag this bug not in 3.18.0-1 and
all above or lower this bug severity.
-- 
Cheers,
Abou Al Montacir


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

Bug#807074: marked as done (fbreader: includes files with unclear DFSG-freeness and/or copyright status)

[Debian Bug Tracking System]

Your message dated Mon, 14 Dec 2015 21:07:40 +0100
with message-id <566f218c.3050...@debian.org>
and subject line Re: Bug#807074: fbreader: includes files with unclear 
DFSG-freeness and/or copyright status
has caused the Debian Bug report #807074,
regarding fbreader: includes files with unclear DFSG-freeness and/or copyright 
status
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.)


-- 
807074: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=807074
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: fbreader
Version: 0.10.7dfsg-4
Severity: serious
Justification: Policy 2.2.1

Hello Eugene and thanks for maintaining FBReader in Debian!

I noticed something awkward in the debian/copyright file:

[...]
|  Html entity files (fbreader/data/formats/docbook/*.ent) with
|  these licenses:
|  
|  
|  
|  
[...]

The problem is: among these two licenses, the first one is non-free,
as it does not grant permission to modify (thus failing DFSG#3) and
only grants a limited permission to copy and use, restricting the
field of endeavor to conforming SGML systems and applications as
defined in ISO 8879 (thus failing DFSG#6).
The second license is instead fine for Debian main.

By only reading the debian/copyright file, it was not clear to me
whether both licenses apply (which would mean that these files
are non-free in fbreader) or, instead, whether the recipient may
choose which of the two licenses will apply (which would mean that
we can choose the second license and everything is fine for fbreader).

This freeness issue has been discussed on the debian-legal mailing list:
https://lists.debian.org/debian-legal/2015/11/msg00048.html
https://lists.debian.org/debian-legal/2015/11/msg00049.html

During that debian-legal thread, I was pointed out that the licensing
of those files in fbreader is a bit different from what is documented
in the fbreader debian/copyright file:
https://lists.debian.org/debian-legal/2015/11/msg00050.html
And indeed, the files under consideration include that permission grant,
saying that the DFSG-free license applies, but that the files are
derived, in part, from files (copyrighted by ISO) which grant no
permission to modify.
As I said in
https://lists.debian.org/debian-legal/2015/11/msg00051.html
I cannot fully understand how those files could be derived from
the ISO files in the first place, if the ISO files are not legally
modifiable.
Maybe OASIS obtained a special permission from ISO, but this does
not seem to be documented.
Otherwise, this looks like a copyright violation, which, if confirmed,
would result in undistributable files.

An FTP Assitant confirmed that files under the ISO license under
consideration are not fit for Debian main:
https://lists.debian.org/debian-legal/2015/12/msg0.html


Please investigate and clarify and/or fix this issue.

Possible solutions I can think of:

 A) clarify the licensing status of those files and find out
that they are distributable under DFSG-free terms; explain
and document why this is the case
 
 B) get in touch with the copyright holder (ISO) and persuade
them to re-license the ISO files in a DFSG-free manner
 
 C) find DFSG-free replacements for the non-free files

 D) drop the non-free files from the package, assuming they are
not strictly needed for the package to provide significant
functionality


Thanks for your time!
--- End Message ---
--- Begin Message ---
Hi Francesco and all,

Thanks for your interest.

> I cannot fully understand how those files could be derived from
> the ISO files in the first place, if the ISO files are not legally
> modifiable.
> Maybe OASIS obtained a special permission from ISO, but this does
> not seem to be documented.

I am afraid I don't get it.

OASIS say [1] they are the copyright holder and their license is DFSG-free. You 
suspect OASIS breaches copyright of ISO,
and the source for this suspect is license headers written by OASIS themselves?

You propose we contact OASIS and ask whether they have right to distribute 
those files? If they say 'yes', how one is
supposed to verify that they really do? In what circumstances they could say 
'no'?

Or you propose we contact ISO and ask whether OASIS breaches their copyright?

[1] http://www.oasis-open.org/docbook/xmlcharent/0.1/entities-2001-11-19.html


The files in question (fbreader/fbreader/data/formats/docbook/*) didn't change, 
at least, after 2009. Since that time,
fbreader has been gone through NEW queue at least in 2010 [2] and in 2015 [3].

[2] https://tracker.debian.org/news/496859
[3] 

Processed: tagging 790958

[Debian Bug Tracking System]

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

> tags 790958 + unreproducible
Bug #790958 [cegui-mk2] cegui-mk2: FTBFS on rebuild against GLEW 1.12.0
Added tag(s) unreproducible.
> thanks
Stopping processing here.

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

Bug#795879: curlftpfs misbuilds on 64-bit architectures (missing getpass prototype)

[Vincent Bernat]

 ❦  9 décembre 2015 07:24 +0100, Andreas Beckmann  :

> do you plan to fix this bug in jessie, too? The next point release will
> probably be in January. A simple backport of the sid package should be
> sufficient, proposed patch attached.

Isn't backports reserved for some special cases? This doesn't matter
much here since there is virtually no difference, but wouldn't it better
to call this new version 0.9.2-8+deb8u1?

I am quite busy now. I'll try to push the patch to the release team but
if you want to do it yourself, please do.
-- 
Don't comment bad code - rewrite it.
- The Elements of Programming Style (Kernighan & Plauger)


signature.asc
Description: PGP signature

Processed: tagging 802147

[Debian Bug Tracking System]

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

> tags 802147 + stretch
Bug #802147 [src:python-invocations] python-invocations: FTBFS: ImportError: No 
module named 'invoke'
Added tag(s) stretch.
> thanks
Stopping processing here.

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

Processed: tagging 806472

[Debian Bug Tracking System]

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

> tags 806472 + stretch
Bug #806472 [src:libxi] libxi: FTBFS: dh_install: libxi-dev missing files 
(usr/share/doc/libXi/*.txt), aborting
Added tag(s) stretch.
> thanks
Stopping processing here.

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

Processed: tagging 796466

[Debian Bug Tracking System]

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

> tags 796466 + stretch
Bug #796466 [src:pepper] pepper: FTBFS: error: ‘svn_sort__hash’ was not 
declared in this scope
Added tag(s) stretch.
> thanks
Stopping processing here.

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

Processed: tagging 806471

[Debian Bug Tracking System]

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

> tags 806471 + stretch
Bug #806471 [src:libxfont] libxfont: FTBFS: dh_install: libxfont-dev missing 
files (../../build-main/doc/*.txt), aborting
Added tag(s) stretch.
> thanks
Stopping processing here.

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

Processed: tagging 794141

[Debian Bug Tracking System]

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

> tags 794141 + stretch
Bug #794141 [src:r10k] FTBFS: undefined method `its' for 
RSpec::ExampleGroups::R10KModuleForge::SettingAttributes:Class
Added tag(s) stretch.
> thanks
Stopping processing here.

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

Processed: tagging 804582

[Debian Bug Tracking System]

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

> tags 804582 + stretch
Bug #804582 [src:paramiko] paramiko: FTBFS: ImportError: No module named 
pyasn1.type.univ
Added tag(s) stretch.
> thanks
Stopping processing here.

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

Processed: tagging 793515

[Debian Bug Tracking System]

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

> tags 793515 + stretch
Bug #793515 [src:flower] FTBFS: sphinx: LoginHandler: 'module' object has no 
attribute 'GoogleMixin'
Added tag(s) stretch.
> thanks
Stopping processing here.

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

Processed: tagging 802865

[Debian Bug Tracking System]

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

> tags 802865 + stretch
Bug #802865 [src:nss-passwords] nss-passwords: FTBFS: ocaml/caml/config.h: 
error: conflicting types for 'int64'
Added tag(s) stretch.
> thanks
Stopping processing here.

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

Processed: tagging 794154

[Debian Bug Tracking System]

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

> tags 794154 + stretch
Bug #794154 [src:spork] FTBFS: undefined method `stub!' for Dir:Class
Added tag(s) stretch.
> thanks
Stopping processing here.

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

Processed: tagging 805674

[Debian Bug Tracking System]

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

> tags 805674 + stretch
Bug #805674 [src:ohcount] ohcount: FTBFS: cp: cannot stat 'ruby/gestalt': No 
such file or directory
Added tag(s) stretch.
> thanks
Stopping processing here.

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

Processed: tagging 794267

[Debian Bug Tracking System]

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

> tags 794267 + stretch
Bug #794267 [src:ruby-merb-assets] FTBFS: "in `block in const_missing': 
uninitialized constant RSpec::Runner (NameError)"
Added tag(s) stretch.
> thanks
Stopping processing here.

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

Processed: tagging 805242

[Debian Bug Tracking System]

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

> tags 805242 + stretch
Bug #805242 [src:webassets] webassets: FTBFS: ImportError: No module named 
pytest
Added tag(s) stretch.
> thanks
Stopping processing here.

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

Processed: tagging 806485

[Debian Bug Tracking System]

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

> tags 806485 + stretch
Bug #806485 [src:setools] setools: FTBFS: policy_define.c: error: 
'class_perm_node_t {aka ..}' has no member named 'class'
Added tag(s) stretch.
> thanks
Stopping processing here.

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

Processed: tagging 798059

[Debian Bug Tracking System]

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

> tags 798059 + stretch
Bug #798059 [src:turbojson] turbojson: FTBFS: ImportError: from peak.rules 
import abstract, around, when
Added tag(s) stretch.
> thanks
Stopping processing here.

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

Bug#793872: marked as done (gcc-4.6-doc: FTBFS in sid)

[Debian Bug Tracking System]

Your message dated Mon, 14 Dec 2015 18:28:28 +
with message-id 
and subject line Bug#807891: Removed package(s) from unstable
has caused the Debian Bug report #793872,
regarding gcc-4.6-doc: FTBFS in sid
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.)


-- 
793872: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=793872
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: gcc-4.6-doc
Version: 4.6.4-3
Severity: serious
Justification: fails to build from source

gcc-4.6-doc FTBFS in sid, probably due to a newer texinfo and friends.
See the attached buildlog for details.
It's probably not worth fixing this, since the package will get removed
along gcc-4.6 at some point and the package released with wheezy is
fine.

Andreas


gcc-4.6-doc_4.6.4-3.log.gz
Description: application/gzip
--- End Message ---
--- Begin Message ---
Version: 4.6.4-3+rm

Dear submitter,

as the package gcc-4.6-doc has just been removed from the Debian archive
unstable we hereby close the associated bug reports.  We are sorry
that we couldn't deal with your issue properly.

For details on the removal, please see https://bugs.debian.org/807891

The version of this package that was in Debian prior to this removal
can still be found using http://snapshot.debian.org/.

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

Debian distribution maintenance software
pp.
Thorsten Alteholz (the ftpmaster behind the curtain)--- End Message ---

Processed: Re: red5: Transition to Groovy 2

[Debian Bug Tracking System]

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

> severity 805627 serious
Bug #805627 [src:red5] red5: Transition to Groovy 2
Severity set to 'serious' from 'normal'
> thanks
Stopping processing here.

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

Processed: tagging 802861

[Debian Bug Tracking System]

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

> tags 802861 + stretch
Bug #802861 [src:kalzium] kalzium: FTBFS: gasCalculator.h: error: expected 
unqualified-id before numeric constant
Added tag(s) stretch.
> thanks
Stopping processing here.

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

Processed: tagging 804584

[Debian Bug Tracking System]

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

> tags 804584 + stretch
Bug #804584 [src:python-enable] python-enable: FTBFS: Error: Unknown SWIG 
preprocessor directive: map
Added tag(s) stretch.
> thanks
Stopping processing here.

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

Processed: tagging 802861

[Debian Bug Tracking System]

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

> tags 802861 + stretch
Bug #802861 [src:kalzium] kalzium: FTBFS: gasCalculator.h: error: expected 
unqualified-id before numeric constant
Ignoring request to alter tags of bug #802861 to the same tags previously set
> thanks
Stopping processing here.

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

Processed: tagging 806498

[Debian Bug Tracking System]

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

> tags 806498 + stretch
Bug #806498 [src:x11proto-core] x11proto-core: FTBFS: dh_install: 
x11proto-core-dev missing files (usr/share/doc/x11proto-core-dev/*.txt), 
aborting
Added tag(s) stretch.
> thanks
Stopping processing here.

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

Processed: tagging 802065

[Debian Bug Tracking System]

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

> tags 802065 + stretch
Bug #802065 [src:ditaa] ditaa: FTBFS: Cannot find symbol: 
org.apache.batik.dom.svg.SAXSVGDocumentFactory
Added tag(s) stretch.
> thanks
Stopping processing here.

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

Processed: tagging 805205

[Debian Bug Tracking System]

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

> tags 805205 + stretch
Bug #805205 [src:kindleclip] kindleclip: FTBFS: in `load_rbconfig': 
uninitialized constant Config (NameError)
Added tag(s) stretch.
> thanks
Stopping processing here.

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

Bug#804728: marked as done (FTBFS: libode-sp-dev has been dropped)

[Debian Bug Tracking System]

Your message dated Mon, 14 Dec 2015 18:48:39 +
with message-id 
and subject line Bug#805243: Removed package(s) from unstable
has caused the Debian Bug report #804728,
regarding FTBFS: libode-sp-dev has been dropped
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.)


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

soya needs ode to be built. ode has a new version in unstable that  
has dropped the sp (single precession) version. Also, ode has been upgraded
to 0.13.1 version. So, soya  will fail till its Build-depends field change 
from libode-sp-dev to libode-dev and had been upgraded to ode 0.13.x.



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

Kernel: Linux 3.16.0-4-amd64 (SMP w/4 CPU cores)
Locale: LANG=ca_ES.UTF-8, LC_CTYPE=ca_ES.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
--- End Message ---
--- Begin Message ---
Version: 0.15~rc1-10+rm

Dear submitter,

as the package soya has just been removed from the Debian archive
unstable we hereby close the associated bug reports.  We are sorry
that we couldn't deal with your issue properly.

For details on the removal, please see https://bugs.debian.org/805243

The version of this package that was in Debian prior to this removal
can still be found using http://snapshot.debian.org/.

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

Debian distribution maintenance software
pp.
Thorsten Alteholz (the ftpmaster behind the curtain)--- End Message ---

Bug#803292: wmaker is marked for autoremoval from testing

[Andreas Metzler]

On 2015-12-14 Debian testing autoremoval watch  
wrote:
> wmaker 0.95.6-1.1 is marked for autoremoval from testing on 2016-01-12

> It is affected by these RC bugs:
> 803292: wmaker: prepare for giflib5

Hello,

Rodolfo, do you want me to try to fix this with a NMU?

BTW I have seen that there is some packaging for 0.95.7 in upstream
GIT, is there a special treason why this has not appeared in Debian
yet?

cu Andreas
-- 
`What a good friend you are to him, Dr. Maturin. His other friends are
so grateful to you.'
`I sew his ears on from time to time, sure'

Processed: Re: xflip: Please migrate a supported debhelper compat level

[Debian Bug Tracking System]

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

> tags 800268 -pending
Bug #800268 [src:xflip] xflip: Please migrate a supported debhelper compat level
Removed tag(s) pending.
> thanks
Stopping processing here.

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

Bug#800268: xflip: Please migrate a supported debhelper compat level

[Eriberto Mota]

tags 800268 -pending
thanks


Ooopss!!!

The package is orphan... Sorry.

I will cancel the NMU and prepare a QA upload.

Regards,

Eriberto

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

[Francesco Poli]

On Mon, 14 Dec 2015 21:07:40 +0100 Eugene V. Lyubimkin wrote:

> Hi Francesco and all,

Hello Eugene, hello FTP Masters,

> 
> Thanks for your interest.

You're welcome.
Thanks to you for replying!

> 
> > I cannot fully understand how those files could be derived from
> > the ISO files in the first place, if the ISO files are not legally
> > modifiable.
> > Maybe OASIS obtained a special permission from ISO, but this does
> > not seem to be documented.
> 
> I am afraid I don't get it.
> 
> OASIS say [...] they are the copyright holder and their license is
> DFSG-free. You suspect OASIS breaches copyright of ISO,
> and the source for this suspect is license headers written by OASIS
> themselves?

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.

Maybe it's not, but there has to be some explanation of how it can
avoid being a copyright violation... Perhaps the ISO files have been
assessed to not be copyrighted? but this is not documented! Perhaps ISO
granted some permission to re-license the ISO files? but this is not
documented, either! And so forth...

Or maybe it is indeed a copyright violation done by OASIS by
oversight... Maybe OASIS will promptly act to fix this issue (for
instance, by persuading ISO to re-license the ISO files...).

> 
> You propose we contact OASIS and ask whether they have right to
> distribute those files?

One possible solution is seeking clarification from OASIS: maybe they
have a perfectly valid and convincing explanation and it just needs to
be documented properly!

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

> In what circumstances they could say 'no'?

For example, in case they violated the ISO copyright by mistake.

> 
> Or you propose we contact ISO and ask whether OASIS breaches their
> copyright?

Another possible strategy is getting in touch with ISO and persuade
them to re-license the ISO files in a DFSG-free and permissive manner.
The new license should be a simple permissive non-copyleft one,
compatible with pretty everything.

As I have already said, one more possible solution is finding DFSG-free
replacements for the ISO files and asking OASIS to base their files on
those DFSG-free replacements, in stead of the ISO files.

> 
> 
> The files in question (fbreader/fbreader/data/formats/docbook/*)
> didn't change, at least, after 2009. Since that time,
> fbreader has been gone through NEW queue at least in 2010
[...]
> and in 2015
[...]

With all due respect for the FTP Masters, mistakes *can* happen.
It would not be the first time that a package with non-free (or even
undistributable) content gets accepted in Debian main, by oversight.

> 
> 
> Given above, I am going to assume, for now, that those files are fine.
> Dear archive masters (To'ed), please re-open this
> bug if they are not, and in that case files will be not included.

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.

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

Hence, I do *not* agree that this bug report should have been closed
simply assuming that everything is fine. Please reopen the bug report
and investigate the issue.


Thanks for your time.
Bye.

-- 
 http://www.inventati.org/frx/
 There's not a second to spare! To the laboratory!
. Francesco Poli .
 GnuPG key fpr == CA01 1147 9CD2 EFDF FB82  3925 3E1C 27E1 1F69 BFFE


pgp_j8EIBGUMS.pgp
Description: PGP signature

Processed: Re: xflip: Please migrate a supported debhelper compat level

[Debian Bug Tracking System]

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

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

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

Bug#800268: xflip: Please migrate a supported debhelper compat level

[Eriberto Mota]

tags 800268 patch
tags 800268 pending
thanks


Hi,

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

The debian/changelog is:

xflip (1.01-25.1) unstable; urgency=medium
 .
   * Non-maintainer upload.
   * Migrated DH level to 9 to avoid a FTBFS. (Closes: #800268)
   * debian/compat: added.
   * debian/control:
  - Added the ${misc:Depends} variable to provide the
right install dependencies.
  - Bumped Standards-Version to 3.9.6.
   * debian/rules: updated to not use tmp dir.

I attached a debdiff.

Regards,

Eriberto


xflip.debdiff
Description: Binary data

Bug#807492: marked as done (libmath-bigint-gmp-perl: FTBFS on 32 bit platforms)

[Debian Bug Tracking System]

Your message dated Mon, 14 Dec 2015 22:10:10 +
with message-id 
and subject line Bug#807492: fixed in libmath-bigint-gmp-perl 1.47-1
has caused the Debian Bug report #807492,
regarding libmath-bigint-gmp-perl: FTBFS on 32 bit platforms
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.)


-- 
807492: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=807492
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: libmath-bigint-gmp-perl
Version: 1.46-1
Severity: serious
Justification: FTBFS on platforms where it built before
Forwarded: https://rt.cpan.org/Public/Bug/Display.html?id=103517

The new release, 1.46, introduced a regression on 32 bit platforms
where perl is compiled with 64 bit support. You can see that it has
failed to build on armel, armhf, i386, mips, mipsel, hppa, kfreebsd-i386
as a result:

https://buildd.debian.org/status/package.php?p=libmath-bigint-gmp-perl=unstable

There is discussion about this problem at the CPAN bug above.
Since this collides with the impending perl 5.22 transition, I
checked and it appears that the impact of removing this would not be
huge; so although I will add it as a blocker of the transition, if it
isn't fixed in the next few days it'll probably get removed.

Cheers,
Dominic.
--- End Message ---
--- Begin Message ---
Source: libmath-bigint-gmp-perl
Source-Version: 1.47-1

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

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

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

Debian distribution maintenance software
pp.
gregor herrmann  (supplier of updated 
libmath-bigint-gmp-perl package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Mon, 14 Dec 2015 21:49:13 +0100
Source: libmath-bigint-gmp-perl
Binary: libmath-bigint-gmp-perl
Architecture: source
Version: 1.47-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Perl Group 
Changed-By: gregor herrmann 
Closes: 807492
Description: 
 libmath-bigint-gmp-perl - module for arbitrary precision arithmetic using GMP
Changes:
 libmath-bigint-gmp-perl (1.47-1) unstable; urgency=medium
 .
   * New upstream release.
 Fixes "FTBFS on 32 bit platforms".
 (Closes: #807492)
Checksums-Sha1: 
 343b1fb25dddfab4cd37c32e891c8b0185e59846 2467 
libmath-bigint-gmp-perl_1.47-1.dsc
 cc2193cc0de1c33a3844fdb98bf439f5240642b6 58266 
libmath-bigint-gmp-perl_1.47.orig.tar.gz
 ac0ce9226e77f94cb3486cc313cfd1cfb8af4291 3784 
libmath-bigint-gmp-perl_1.47-1.debian.tar.xz
Checksums-Sha256: 
 fefff57663d5cf91e9b59ff9af199a784f33d126d3ad172325515c64fc824afd 2467 
libmath-bigint-gmp-perl_1.47-1.dsc
 9ed3101d39fc118e025604e48894b88bf674f44c745a591c580987b2f24127e8 58266 
libmath-bigint-gmp-perl_1.47.orig.tar.gz
 57a6cd08c72da8ae6979bd8484656b962b399b878a55fc7912ef5157aa82bb25 3784 
libmath-bigint-gmp-perl_1.47-1.debian.tar.xz
Files: 
 bb549c8f46b6526e4be46824a9804ebf 2467 perl optional 
libmath-bigint-gmp-perl_1.47-1.dsc
 38129e6563b52f479e8e5b4fb66a10eb 58266 perl optional 
libmath-bigint-gmp-perl_1.47.orig.tar.gz
 82a3416340d824ebce1a414fabc64d19 3784 perl optional 
libmath-bigint-gmp-perl_1.47-1.debian.tar.xz

-BEGIN PGP SIGNATURE-
Version: GnuPG v1

iQJ8BAEBCgBmBQJWbyvcXxSAAC4AKGlzc3Vlci1mcHJAbm90YXRpb25zLm9w
ZW5wZ3AuZmlmdGhob3JzZW1hbi5uZXREMUUxMzE2RTkzQTc2MEE4MTA0RDg1RkFC
QjNBNjgwMTg2NDlBQTA2AAoJELs6aAGGSaoGq98QAMBsTqahYFWNtOOWSeoI7xZP
/3Y/JiL5qHrFfnu7c5hquWWpsTbNzSWDvMDdedtuat8xZ9qPOPoq6X1JgPCGjyHG
Phv3zAyqtLlu8UucCGoScdzhx1fmxx1j/Iu5fOtLDldfJfFicFDNILKk8mQZq/te
ExPdkZ4jCeS0kVe055QF/fjWDko3pmifL12PIKeuDJSLySlE24odxAlSUoXeNH1S
YfzMOilaTXpiXQ4sf2fKJ2MM4MIVvRocbOkCd4k8JrJNxlkwVHD1vMTngQbn9Ev3
QZG/6tL/JLrzqyBHSo+7VYYWsaV2/SoNC9iR/9yQmAjWMhF/30QNdRqLV8wl76c+
2HOH8mrljGsqTYwQ/I9sv0tLmM4Im3WiuH5x3aXVzdbqM2eHN29lP+JQrFjGU8c8
UHTjFx3soiG6kRZeDVptYqkJowN65vGIFEHRnrHGeTGJLAOAyob23cSHEzV4pmxt
fdsgSFLNydMIRdAfwyrivg03XcvN/oLQqTC3TZvgVeOmf2vsDZjgIwxchuvLZYQ/
tDNZPalVc+gHSD0iRdKH0EtNLbv/lnoOR+RNowPkKcWMNpNgzlMI5O/4hPlLCJli

Bug#807966: drift: FTBFS with ghc 7.10

[Logan Rosen]

Package: drift
Version: 2.2.3-2.3
Severity: serious
Justification: fails to build from source (but built successfully in the past)

drift currently fails to build from source with GHC 7.10 due to an unresolved
System.Time reference. A build dependency on libghc-old-time-dev is probably
necessary here, but adding that just exposes more issues.

Here's a pastebin of the log, done in an amd64 unstable pbuilder:
http://paste.ubuntu.com/14013137/

-- System Information:
Debian Release: stretch/sid
  APT prefers xenial-updates
  APT policy: (500, 'xenial-updates'), (500, 'xenial-security'), (500, 
'xenial'), (100, 'xenial-backports')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

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

Processed: tagging 798484

[Debian Bug Tracking System]

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

> tags 798484 + stretch
Bug #798484 [src:libdr-tarantool-perl] libdr-tarantool-perl: FTBFS: Failed 1/19 
test programs. 1/853 subtests failed.
Added tag(s) stretch.
> thanks
Stopping processing here.

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

Processed: tagging 805665

[Debian Bug Tracking System]

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

> tags 805665 + stretch
Bug #805665 [src:guacamole-client] guacamole-client: FTBFS: Missing: 
org.glyptodon.guacamole:guacamole-common-js:zip:0.7.4
Added tag(s) stretch.
> thanks
Stopping processing here.

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

Bug#784070: Stable is still affected

[Yann Soubeyrand]

Le lundi 14 décembre 2015 à 11:36 +0500, patra...@gmail.com a écrit :
> Are there any plans to produce a stable update containing this fix?

Yes, the package is done, waiting for the approval of the release team
(https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=805894).

Bug#790958: cegui-mk2: FTBFS on rebuild against GLEW 1.12.0

[Tobias Frost]

Source: cegui-mk2
Severity: -1 normal
Followup-For: Bug #790958
Control: -1 tags unreproducible 

Hi,

On the weekend I've rebuilt locally here against the latest libglew, 1.13.0-2.

Well, it built fine, so I assume some glitch...

Therefore marking it appropiatly and downgrading severity. 
Please revert that if you can reproduce this...

tobi

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

Kernel: Linux 4.0.5-revert-done (SMP w/4 CPU cores)
Locale: LANG=de_DE.utf8, LC_CTYPE=de_DE.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: sysvinit (via /sbin/init)

Bug#802671: marked as done (CVE-2015-7940: bouncycastle: ECC private keys can be recovered via invalid curve attack)

[Debian Bug Tracking System]

Your message dated Mon, 14 Dec 2015 22:47:07 +
with message-id 
and subject line Bug#802671: fixed in bouncycastle 1.49+dfsg-3+deb8u1
has caused the Debian Bug report #802671,
regarding CVE-2015-7940: bouncycastle: ECC private keys can be recovered via 
invalid curve attack
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.)


-- 
802671: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=802671
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: bouncycastle
Version: 1.44+dfsg-2
Severity: serious
Tags: security
Control: fixed -1 1.51-1

Hello,

bouncycastle 1.49 in stable/testing/unstable (and 1.44 in wheezy/squeeze)
is vulnerable to an invalid curve attack as described here:
https://web-in-security.blogspot.ca/2015/09/practical-invalid-curve-attacks.html

This is fixed in version 1.51 (in experimental).

The upstream patches that fix this issue should be those ones:
https://github.com/bcgit/bc-java/commit/5cb2f05
https://github.com/bcgit/bc-java/commit/e25e94a

A CVE has been requested here:
http://www.openwall.com/lists/oss-security/2015/10/22/7

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

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)
--- End Message ---
--- Begin Message ---
Source: bouncycastle
Source-Version: 1.49+dfsg-3+deb8u1

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

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Sun, 13 Dec 2015 22:16:20 +0100
Source: bouncycastle
Binary: libbcprov-java libbcprov-java-doc libbcmail-java libbcmail-java-doc 
libbcpkix-java libbcpkix-java-doc libbcpg-java libbcpg-java-doc
Architecture: source all
Version: 1.49+dfsg-3+deb8u1
Distribution: jessie-security
Urgency: high
Maintainer: Debian Java Maintainers 

Changed-By: Markus Koschany 
Description:
 libbcmail-java - Bouncy Castle generators/processors for S/MIME and CMS
 libbcmail-java-doc - Bouncy Castle generators/processors for S/MIME and CMS 
(Documenta
 libbcpg-java - Bouncy Castle generators/processors for OpenPGP
 libbcpg-java-doc - Bouncy Castle generators/processors for OpenPGP 
(Documentation)
 libbcpkix-java - Bouncy Castle Java API for PKIX, CMS, EAC, TSP, PKCS, OCSP, 
CMP,
 libbcpkix-java-doc - Bouncy Castle Java API for PKIX, CMS, EAC, TSP, PKCS... 
(Document
 libbcprov-java - Bouncy Castle Java Cryptographic Service Provider
 libbcprov-java-doc - Bouncy Castle Java Cryptographic Service Provider 
(Documentation)
Closes: 802671
Changes:
 bouncycastle (1.49+dfsg-3+deb8u1) jessie-security; urgency=high
 .
   * Team upload.
   * CVE-2015-7940: fix invalid curve attack as described in
 
http://web-in-security.blogspot.ca/2015/09/practical-invalid-curve-attacks.html
 (Closes: #802671)
Checksums-Sha1:
 c6c378985e7292b1438d5c0c83d1e8da81f66266 2724 
bouncycastle_1.49+dfsg-3+deb8u1.dsc
 e8ae9351b809a04b6da4692ca7e4d84940c66c6f 5877794 
bouncycastle_1.49+dfsg.orig.tar.gz
 221c1cf4ef0b401d85136a4d1da735004bd936bb 20700 
bouncycastle_1.49+dfsg-3+deb8u1.debian.tar.xz
 d6b6a1f26c32bd2996b4e549e34721b8e2fb5eaf 2001778 
libbcprov-java_1.49+dfsg-3+deb8u1_all.deb
 919e974743010123206d654307c40a2b3e2283ea 80192 
libbcprov-java-doc_1.49+dfsg-3+deb8u1_all.deb
 5c9bc2c22bcd73b622ed55c944dafb62438c8f30 115662 
libbcmail-java_1.49+dfsg-3+deb8u1_all.deb
 5e67f6b347aa984b37c34245330f354f31acf3f2 97124 
libbcmail-java-doc_1.49+dfsg-3+deb8u1_all.deb
 c6fd82ec4ff0a6757c8d62bcc041534dbb14de03 532544 

Bug#741642: marked as done (/etc/kernel/postinst.d/mkvmlinuz exited with return code 20)

[Debian Bug Tracking System]

Your message dated Mon, 14 Dec 2015 22:48:42 +
with message-id 
and subject line Bug#741642: fixed in mkvmlinuz 37+deb8u1
has caused the Debian Bug report #741642,
regarding /etc/kernel/postinst.d/mkvmlinuz exited with return code 20
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.)


-- 
741642: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=741642
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:linux
Version: 3.13.5-1
Severity: normal

Dear Maintainer,

I get the following when I try to do an upgrade:

root# aptitude install linux-image-powerpc-smp
The following partially installed packages will be configured:
  linux-image-3.13-1-powerpc-smp  linux-image-powerpc-smp
No packages will be installed, upgraded, or removed.
0 packages upgraded, 0 newly installed, 0 to remove and 96 not
upgraded.
Need to get 0 B of archives. After unpacking 0 B will be used.
Setting up linux-image-3.13-1-powerpc-smp (3.13.5-1) ...
vmlinux(/boot/vmlinux-3.13-1-powerpc-smp
) points to /boot/vmlinux-3.13-1-powerpc-smp
 (/boot/vmlinux-3.13-1-powerpc-smp) -- doing nothing at
 /var/lib/dpkg/info/linux-image-3.13-1-powerpc-smp.postinst line 263.
initrd.img(/boot/initrd.img-3.13-1-powerpc-smp
) points to /boot/initrd.img-3.13-1-powerpc-smp
 (/boot/initrd.img-3.13-1-powerpc-smp) -- doing nothing at
 /var/lib/dpkg/info/linux-image-3.13-1-powerpc-smp.postinst line 263.
/etc/kernel/postinst.d/initramfs-tools:
update-initramfs: Generating /boot/initrd.img-3.13-1-powerpc-smp
run-parts: /etc/kernel/postinst.d/mkvmlinuz exited with return code 20
Failed to process /etc/kernel/postinst.d at
/var/lib/dpkg/info/linux-image-3.13-1-powerpc-smp.postinst line 591.
dpkg: error processing package linux-image-3.13-1-powerpc-smp
(--configure):
 subprocess installed post-installation script returned error exit
 status 1
dpkg: dependency problems prevent configuration of
linux-image-powerpc-smp:
 linux-image-powerpc-smp depends on linux-image-3.13-1-powerpc-smp;
 however:
  Package linux-image-3.13-1-powerpc-smp is not configured yet.

dpkg: error processing package linux-image-powerpc-smp (--configure):
 dependency problems - leaving unconfigured
Errors were encountered while processing:
 linux-image-3.13-1-powerpc-smp
 linux-image-powerpc-smp
E: Sub-process /usr/bin/dpkg returned an error code (1)
Failed to perform requested operation on package.  Trying to recover:
Setting up linux-image-3.13-1-powerpc-smp (3.13.5-1) ...
vmlinux(/boot/vmlinux-3.13-1-powerpc-smp
) points to /boot/vmlinux-3.13-1-powerpc-smp
 (/boot/vmlinux-3.13-1-powerpc-smp) -- doing nothing at
 /var/lib/dpkg/info/linux-image-3.13-1-powerpc-smp.postinst line 263.
initrd.img(/boot/initrd.img-3.13-1-powerpc-smp
) points to /boot/initrd.img-3.13-1-powerpc-smp
 (/boot/initrd.img-3.13-1-powerpc-smp) -- doing nothing at
 /var/lib/dpkg/info/linux-image-3.13-1-powerpc-smp.postinst line 263.
/etc/kernel/postinst.d/initramfs-tools:
update-initramfs: Generating /boot/initrd.img-3.13-1-powerpc-smp
run-parts: /etc/kernel/postinst.d/mkvmlinuz exited with return code 20
Failed to process /etc/kernel/postinst.d at
 /var/lib/dpkg/info/linux-image-3.13-1-powerpc-smp.postinst line 591.
dpkg: error processing package linux-image-3.13-1-powerpc-smp
 (--configure):
 subprocess installed post-installation script returned error exit
 status 1
dpkg: dependency problems prevent configuration of
 linux-image-powerpc-smp:
 linux-image-powerpc-smp depends on linux-image-3.13-1-powerpc-smp;
 however:
  Package linux-image-3.13-1-powerpc-smp is not configured yet.

dpkg: error processing package linux-image-powerpc-smp (--configure):
 dependency problems - leaving unconfigured
Errors were encountered while processing:
 linux-image-3.13-1-powerpc-smp
 linux-image-powerpc-smp



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

** Model information
revision: 2.9 (pvr 000c 0209)
revision: 2.9 (pvr 000c 0209)
platform: PowerMac
model   : PowerMac3,3
machine : PowerMac3,3
motherboard : PowerMac3,3 MacRISC2 MacRISC Power Macintosh

** Network interface configuration:

auto lo
iface lo inet loopback

allow-hotplug eth0
iface eth0 inet static
address 192.168.70.1
broadcast   192.168.70.0
netmask 255.255.255.0
gateway 192.168.70.20



** PCI devices:
:00:0b.0 Host bridge [0600]: Apple Inc. UniNorth AGP [106b:0020]
Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV+ VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx-
Status: Cap+ 66MHz+ UDF- 

Bug#791868: marked as done (/etc/kernel/postinst.d/mkvmlinuz exited with return code 20)

[Debian Bug Tracking System]

Your message dated Mon, 14 Dec 2015 22:48:42 +
with message-id 
and subject line Bug#741642: fixed in mkvmlinuz 37+deb8u1
has caused the Debian Bug report #741642,
regarding /etc/kernel/postinst.d/mkvmlinuz exited with return code 20
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.)


-- 
741642: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=741642
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
package: upgrade-reports, linux-image-3.16.0-4-powerpc
tags: powerpc

Hi,

I've upgraded my old PowerMac from wheezy to jessie, which failed like shown
below. On boot now, yaboots boots the correct kernel but then after loading
the initramfs the fontsize switches to "gigantic" (8 lines, 25 chars per line
or so) and it goes into a systemd rescue environment, I believe.

I havent investigated further (it's my last powerpc, about to be
decommissioned), so I'm filing this bug report so that this doesnt get lost:


Setting up linux-image-3.16.0-4-powerpc (3.16.7-ckt9-3~deb8u1) ...
vmlinux(/boot/vmlinux-3.16.0-4-powerpc
) points to /boot/vmlinux-3.16.0-4-powerpc
 (/boot/vmlinux-3.16.0-4-powerpc) -- doing nothing at 
/var/lib/dpkg/info/linux-image-3.16.0-4-powerpc.postinst line 263.
initrd.img(/boot/initrd.img-3.16.0-4-powerpc
) points to /boot/initrd.img-3.16.0-4-powerpc
 (/boot/initrd.img-3.16.0-4-powerpc) -- doing nothing at 
/var/lib/dpkg/info/linux-image-3.16.0-4-powerpc.postinst line 263.
/etc/kernel/postinst.d/initramfs-tools:
update-initramfs: Generating /boot/initrd.img-3.16.0-4-powerpc
run-parts: /etc/kernel/postinst.d/mkvmlinuz exited with return code 20
Failed to process /etc/kernel/postinst.d at 
/var/lib/dpkg/info/linux-image-3.16.0-4-powerpc.postinst line 634.
dpkg: error processing package linux-image-3.16.0-4-powerpc (--configure):
 subprocess installed post-installation script returned error exit status 1
dpkg: dependency problems prevent configuration of linux-image-powerpc:
 linux-image-powerpc depends on linux-image-3.16.0-4-powerpc; however:
  Package linux-image-3.16.0-4-powerpc is not configured yet.

dpkg: error processing package linux-image-powerpc (--configure):
 dependency problems - leaving unconfigured
Errors were encountered while processing:
 linux-image-3.16.0-4-powerpc
 linux-image-powerpc


myframe:~# cat /proc/cpuinfo 
processor   : 0
cpu : 7400, altivec supported
temperature : 38-40 C (uncalibrated)
clock   : 466.65MHz
revision: 2.9 (pvr 000c 0209)
bogomips: 66.58
timebase: 33290001
platform: PowerMac
model   : PowerMac3,4
machine : PowerMac3,4
motherboard : PowerMac3,4 MacRISC2 MacRISC Power Macintosh
detected as : 69 (PowerMac G4 Silver)
pmac flags  : 0010
L2 cache: 1024K unified
pmac-generation : NewWorld
Memory  : 768 MB
myframe:~# ls /boot/
System.map-3.16.0-4-powerpc  config-3.16.0-4-powerpc  
initrd.img-3.16.0-4-powerpc  vmlinux-3.16.0-4-powerpc
System.map-3.2.0-4-powerpc   config-3.2.0-4-powerpc   
initrd.img-3.2.0-4-powerpc   vmlinux-3.2.0-4-powerpc


cheers,
Holger


signature.asc
Description: This is a digitally signed message part.
--- End Message ---
--- Begin Message ---
Source: mkvmlinuz
Source-Version: 37+deb8u1

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

Debian distribution maintenance software
pp.
Milan Kupcevic  (supplier of updated mkvmlinuz 
package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Thu, 23 Jul 2015 23:00:46 -0400
Source: mkvmlinuz
Binary: mkvmlinuz
Architecture: source powerpc
Version: 37+deb8u1
Distribution: stable
Urgency: medium
Maintainer: Debian Kernel Team 
Changed-By: Milan Kupcevic 
Description:
 mkvmlinuz  - create a kernel to boot a PowerPC machine from Open Firmware
Closes: 741642
Changes:
 mkvmlinuz (37+deb8u1) stable; urgency=medium
 .
   * Push run-parts output to stderr. (Closes: #741642)

Bug#807973: chromium-browser: 1 GB of sourceless binaries in the source package

[Andreas Cadhalpun]

Source: chromium-browser
Version: 47.0.2526.80-1
Severity: serious
Justification: policy §2.1

Dear Maintainer,

in this version, the source package includes about 1 GB of binaries
in the native_client/toolchain subdirectory.
Apparently no sources for them are included, only references in:
native_client/toolchain_build/toolchain_build.py

The DFSG #2 requires source code to be present. Since these binaries
are hopefully not used during build, please strip them from the tarball.

Best regards,
Andreas

Processed: tgif: diff for NMU version 1:4.2.5-1.3

[Debian Bug Tracking System]

Processing control commands:

> tags 796294 + patch
Bug #796294 [tgif] Possibly drop uniconvertor dependency
Added tag(s) patch.
> tags 796294 + pending
Bug #796294 [tgif] Possibly drop uniconvertor dependency
Added tag(s) pending.

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

Bug#796294: tgif: diff for NMU version 1:4.2.5-1.3

[Mattia Rizzolo]

Control: tags 796294 + patch
Control: tags 796294 + pending

Dear maintainer,

I've prepared an NMU for tgif (versioned as 1:4.2.5-1.3) and
uploaded it to DELAYED/2. Please feel free to tell me if I
should delay it longer.

Regards.

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

 changelog |8 
 control   |4 ++--
 2 files changed, 10 insertions(+), 2 deletions(-)

diff -Nru tgif-4.2.5/debian/changelog tgif-4.2.5/debian/changelog
--- tgif-4.2.5/debian/changelog	2012-06-16 11:23:37.0 +
+++ tgif-4.2.5/debian/changelog	2015-12-14 23:01:40.0 +
@@ -1,3 +1,11 @@
+tgif (1:4.2.5-1.3) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * Remove dependency on python-uniconvertor, since we want to remove it from
+the archive.  Closes: #796294; Reopens: #608243
+
+ -- Mattia Rizzolo   Mon, 14 Dec 2015 23:01:37 +
+
 tgif (1:4.2.5-1.2) unstable; urgency=low
 
   * Non-maintainer upload.
diff -Nru tgif-4.2.5/debian/control tgif-4.2.5/debian/control
--- tgif-4.2.5/debian/control	2011-06-11 22:58:40.0 +
+++ tgif-4.2.5/debian/control	2015-12-14 23:00:25.0 +
@@ -8,8 +8,8 @@
 Homepage: http://bourbon.usc.edu/tgif/
 
 Package: tgif
-Depends: ${misc:Depends}, gettext-base, ${shlibs:Depends}, netpbm, 
- ghostscript, python-uniconvertor, texlive-latex-base
+Depends: ${misc:Depends}, gettext-base, ${shlibs:Depends}, netpbm,
+ ghostscript, texlive-latex-base
 Recommends: xfonts-75dpi
 Architecture: any
 Description: 2D vector graphic drawing tool using Xlib


signature.asc
Description: PGP signature