Bug#822701: [Debian-med-packaging] Bug#822701: Bug#822701: samtools: FTBFS: UNEXPECTED PASS: Task worked when we expected failure;

[Afif Elghraoui]

Hi, Charles,

I'm sorry for my late reply

على الثلاثاء 26 نيسـان 2016 ‫21:38، كتب Charles Plessy:
> Le Wed, Apr 27, 2016 at 10:12:31AM +0900, Charles Plessy a écrit :
>>
>> Perhaps we also need htslib 1.3.1 to "Break" samtools < 1.3.1... I cloned
>> this bug to address that issue.
> 
> Hi all,
> 
> I added: "Breaks: samtools (<< 1.3.1)".  I think that it would be better to
> update the package before backporting it to Jessie.  Are there other opinions,
> or other changes to make to the package ?
> 

This seems to happen with every htslib upgrade in the past few releases.
bcftools builds have also been breaking as a result and I was a little
confused. Aren't backwards-compatibility breaks supposed to be indicated
by soname bumps? Or is this because samtools, bcftools, and htslib are
all maintained by the same group, so they rely on the unstable internal
interfaces?

If that's the case, maybe every htslib release should be marked as
breaking lower versions of samtools and bcftools. And should samtools
and bcftools have run-time dependencies on libhts1 (=${binary:Version})?


So htslib:

Breaks: samtools (<< ${binary,Version}, bcftools (<< ${binary:Version})

samtools/bcftools:

Depends: libhts1 (>= ${binary:Version})

What do you think? For bcftools so far, I have only been constraining
the build-depends on htslib to be the corresponding upstream version at
a minimum.

regards
Afif


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

Bug#822322: marked as done (openmeeg: please switch to vtk6)

[Debian Bug Tracking System]

Your message dated Tue, 03 May 2016 04:20:12 +
with message-id <e1axroi-e3...@franck.debian.org>
and subject line Bug#822322: fixed in openmeeg 2.3.0~20160502-1
has caused the Debian Bug report #822322,
regarding openmeeg: please switch to vtk6
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.)


-- 
822322: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=822322
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: openmeeg
Version: 2.0.0.dfsg-5.2
Severity: serious
Control: block 822321 by -1

We're kicking vtk5 out of Debian, but your package still build-depend on
it.  Funnily, the binary doesn't depend on vtk, so I wonder if the
build-dep is just needed at all.

-- 
regards,
Mattia Rizzolo

GPG Key: 66AE 2B4A FCCF 3F52 DA18  4D18 4B04 3FCD B944 4540  .''`.
more about me:  https://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 ---
--- Begin Message ---
Source: openmeeg
Source-Version: 2.3.0~20160502-1

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

Debian distribution maintenance software
pp.
Yaroslav Halchenko <deb...@onerussian.com> (supplier of updated openmeeg 
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, 02 May 2016 21:57:39 -0400
Source: openmeeg
Binary: libopenmeeg1 libopenmeeg-dev openmeeg-tools python-openmeeg
Architecture: source amd64
Version: 2.3.0~20160502-1
Distribution: experimental
Urgency: medium
Maintainer: NeuroDebian Team <t...@neuro.debian.net>
Changed-By: Yaroslav Halchenko <deb...@onerussian.com>
Description:
 libopenmeeg-dev - openmeeg library -- development files
 libopenmeeg1 - library for solving EEG and MEG forward and inverse problems
 openmeeg-tools - openmeeg library -- command line tools
 python-openmeeg - openmeeg library -- Python bindings
Closes: 786335 822322
Changes:
 openmeeg (2.3.0~20160502-1) experimental; urgency=medium
 .
   * Trying fresh upstream snapshot
   * Skipping testing of python bindings atm
 (test failure: https://github.com/openmeeg/openmeeg/issues/101)
   * debian/control
 - bdepend on vtk6 (allowing vtk5 as alternative) (Closes: #822322)
 - policy boost to 3.9.8
 - we do not need python-support functionality (Closes: #786335)
 - allow for both swig | swig2.0
Checksums-Sha1:
 67cd2739688d3355eac5b41a0cc2a8221d41c438 2358 openmeeg_2.3.0~20160502-1.dsc
 88c5f1e8dcd161ebed01ca712f5a5c2c1dcca3be 5640780 
openmeeg_2.3.0~20160502.orig.tar.gz
 ab2f33b1661e5441c1fb9613440a7b1a833238e7 16020 
openmeeg_2.3.0~20160502-1.debian.tar.xz
 3c3ba8f9e1bacf93c5fab25beec7654d0528da4c 31898 
libopenmeeg-dev_2.3.0~20160502-1_amd64.deb
 9e695d8823bf42d824a79cce1f8e9bd1dd70995d 77768 
libopenmeeg1-dbgsym_2.3.0~20160502-1_amd64.deb
 2976a32edd1f2d24a42ccbdd1a7698c7c3a6305d 300652 
libopenmeeg1_2.3.0~20160502-1_amd64.deb
 bfbacaeb53c5ba50c1f4662fdf5dfd124ff44ebe 52908 
openmeeg-tools-dbgsym_2.3.0~20160502-1_amd64.deb
 a98d7d02daa150540857ac028909a0ec64cf8705 166060 
openmeeg-tools_2.3.0~20160502-1_amd64.deb
 724bd350f7da84ef2bd6cc1e817c95133924c89f 85056 
python-openmeeg-dbgsym_2.3.0~20160502-1_amd64.deb
 fb69c6a1bbd8a25ead8a15a3e49b61b4f1edc1e4 377924 
python-openmeeg_2.3.0~20160502-1_amd64.deb
Checksums-Sha256:
 22466ed6b371c7870dbf80ee6c02e0408844d0990087d6d08977ba4186d1eba0 2358 
openmeeg_2.3.0~20160502-1.dsc
 9d61f8a3fc6ec4fbfcfc2595e30f38b9e608098ed9eb161246926a3599786ca3 5640780 
openmeeg_2.3.0~20160502.orig.tar.gz
 e6622e74b64d8dd5dc9c8b512ad84de05893811982833b819fa29cb7f729af97 16020 
openmeeg_2.3.0~20160502-1.debian.tar.xz
 cb10828fba611d2bdf1d848dbd6dfaa49e8e49b0a7ef54b3bde788a5391badad 31898 
libopenmeeg-dev_2.3.0~20160502-1_amd64.deb
 d5fcc11299730a43cecee6d0dee91ab21708dca331507ca68c794d481381b6ce 77768 
libopenmeeg1-dbgsym_2.

Bug#786335: marked as done (openmeeg: deprecation of python-support)

[Debian Bug Tracking System]

Your message dated Tue, 03 May 2016 04:20:12 +
with message-id <e1axroi-dy...@franck.debian.org>
and subject line Bug#786335: fixed in openmeeg 2.3.0~20160502-1
has caused the Debian Bug report #786335,
regarding openmeeg: 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.)


-- 
786335: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=786335
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: openmeeg
Version: 2.0.0.dfsg-5.2
Severity: important
User: debian-pyt...@lists.debian.org
Usertags: pysupport-deprecation



Dear Maintainer,

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

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

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

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

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

Thanks! 
--- End Message ---
--- Begin Message ---
Source: openmeeg
Source-Version: 2.3.0~20160502-1

We believe that the bug you reported is fixed in the latest version of
openmeeg, 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.
Yaroslav Halchenko <deb...@onerussian.com> (supplier of updated openmeeg 
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, 02 May 2016 21:57:39 -0400
Source: openmeeg
Binary: libopenmeeg1 libopenmeeg-dev openmeeg-tools python-openmeeg
Architecture: source amd64
Version: 2.3.0~20160502-1
Distribution: experimental
Urgency: medium
Maintainer: NeuroDebian Team <t...@neuro.debian.net>
Changed-By: Yaroslav Halchenko <deb...@onerussian.com>
Description:
 libopenmeeg-dev - openmeeg library -- development files
 libopenmeeg1 - library for solving EEG and MEG forward and inverse problems
 openmeeg-tools - openmeeg library -- command line tools
 python-openmeeg - openmeeg library -- Python bindings
Closes: 786335 822322
Changes:
 openmeeg (2.3.0~20160502-1) experimental; urgency=medium
 .
   * Trying fresh upstream snapshot
   * Skipping testing of python bindings atm
 (test failure: https://github.com/openmeeg/openmeeg/issues/101)
   * debian/control
 - bdepend on vtk6 (allowing vtk5 as alternative) (Closes: #822322)
 - policy boost to 3.9.8
 - we do not need python-support functionality (Closes: #786335)
 - allow for both swig | swig2.0
Checksums-Sha1:
 67cd2739688d3355eac5b41a0cc2a8221d41c438 2358 openmeeg_2.3.0~20160502-1.dsc
 88c5f1e8dcd161ebed01ca712f5a5c2c1dcca3be 5640780 
openmeeg_2.3.0~20160502.orig.tar.gz
 ab2f33b1661e5441c1fb9613440a7b1a833238e7 16020 
openmeeg_2.3.0~20160502-1.debian.tar.xz
 3c3ba8f9e1bacf93c5fab25beec7654d0528da4c 31898 
libopenmeeg-dev_2.3.0~20160502-1_amd64.deb
 9e695d8823bf42d824a79cce1f8e9bd1dd70995d 77768 
libopenmeeg1-dbgsym_2.3.0~20160502-1_amd64.deb
 2976a32edd1f2d24a42ccbdd1a7698c7c3a6305d 300652 
libopenmeeg1_2.3.0~20160502-1_amd64.deb
 bfbacaeb53c5ba50c1f4662fdf5dfd124ff44ebe 52908 
openmeeg-tools-dbgsym_2.3.0~20160502-1_amd64.deb
 a98d7d02daa150540857ac028909a0ec64cf8705 166060 
openmeeg-tools_2.3.0~20160502-1_amd64.deb
 724bd350f7da84ef2bd6cc1e817c95133924c89f 85056 
python-openmeeg-dbgsym_2.3.0~20160502-1_amd64.deb
 fb69c6a1bbd8a25ead8a15a3e49b61b4f1edc1e4 377924 
python-openmee

Bug#823287: selinux-basics: System cannot boot with SELinux enabled after upgrade

[Jonathan Yu]

Package: selinux-basics
Version: 0.5.4
Severity: grave
Justification: renders package unusable

Dear Maintainer,

Thank you for your work bringing SELinux to Debian!

I regret that my knowledge of both SELinux and systemd is limited, so I do not
know what diagnostics to collect or how to collect it.  That said, I can
reproduce this problem at will, and I'm happy to collect whatever diagnostics
you need.

   * What led up to the situation?

I upgraded my system doing full-upgrade. My system is mainly 'testing' with
some packages coming from 'unstable' (I tried updating to the newer
selinux-utils in unstable, but to no avail).

Unfortunately there are not much diagnostics provided during boot, and I
could not find any trace of the failed boots in journalctl or in files
in /var/log, presumably because the problems occurred at such an early
stage of boot. I checked /var/log/syslog, but did not find much informative.

   * What exactly did you do (or not do) that was effective (or
 ineffective)?
   * What was the outcome of this action?

Removing the "selinux=1 security=selinux" flags from grub allowed me to boot.
I then used "selinux-activate disabled" to disable SELinux while we sort
these issues out.

I also tried running "selinux-activate disabled" and re-activating it again,
as it seems to do something with restorecond on first boot after activation.
Unfortunately this did not change anything :(

   * What outcome did you expect instead?

I expected that my system could continue booting. I've never had significant
issues with Debian upgrades (thanks to careful maintainers like you :) and
guess that there must be something strange about the way my system is
configured.

There was some interesting-looking output in /var/log/audit; here's a
section:

May  2 20:31:38 theory systemd[1]: Listening on CUPS Scheduler.
May  2 20:31:38 theory systemd[1]: Listening on D-Bus System Message Bus Socket.
May  2 20:31:38 theory systemd[1]: apt-daily.timer: Adding 7h 21min 31.345143s 
random time.
May  2 20:31:38 theory systemd[1]: Started Daily apt activities.
May  2 20:31:38 theory systemd[1]: Started Daily Cleanup of Temporary 
Directories.
May  2 20:31:38 theory systemd[1]: Reached target Timers.
May  2 20:31:38 theory systemd[1]: Started CUPS Scheduler.
May  2 20:31:38 theory systemd[1]: Reached target Paths.
May  2 20:31:38 theory systemd[1]: Listening on Virtual machine lock manager 
socket.
May  2 20:31:38 theory systemd[1]: Listening on mpd.socket.
May  2 20:31:38 theory systemd[1]: Listening on Virtual machine log manager 
socket.
May  2 20:31:38 theory systemd[1]: Reached target Sockets.
May  2 20:31:38 theory systemd[1]: Reached target Basic System.
May  2 20:31:38 theory systemd[1]: Started Run anacron jobs.
May  2 20:31:38 theory systemd[1]: Starting Accounts Service...
May  2 20:31:38 theory systemd[1]: Starting IIO Sensor Proxy service...
May  2 20:31:38 theory systemd[1]: Starting Restore /etc/resolv.conf if the 
system crashed before the ppp link was shut down...
May  2 20:31:38 theory systemd[1]: Starting Thermal Daemon Service...
May  2 20:31:38 theory systemd[1]: Starting Modem Manager...
May  2 20:31:38 theory systemd[1]: Started CUPS Scheduler.
May  2 20:31:38 theory systemd[1]: Started D-Bus System Message Bus.
May  2 20:31:38 theory ModemManager[1176]:   ModemManager (version 
1.4.14) starting in system bus...
May  2 20:31:38 theory dbus-daemon[1183]: Failed to start message bus: Failed 
to open "/etc/selinux/default/contexts/dbus_contexts": No such file or directory
May  2 20:31:38 theory systemd-udevd[823]: Process '/usr/sbin/alsactl -E 
HOME=/run/alsa restore 2' failed with exit code 99.
May  2 20:31:38 theory systemd[1]: Failed to subscribe to NameOwnerChanged 
signal for 'org.freedesktop.thermald': Connection timed out
May  2 20:31:38 theory systemd[1]: Failed to subscribe to NameOwnerChanged 
signal for 'org.freedesktop.ModemManager1': Connection timed out
May  2 20:31:38 theory systemd[1]: Failed to subscribe to NameOwnerChanged 
signal for 'net.hadess.SensorProxy': Connection timed out
May  2 20:31:38 theory systemd[1]: Failed to subscribe to NameOwnerChanged 
signal for 'org.freedesktop.NetworkManager': Connection timed out
May  2 20:31:38 theory systemd[1]: Failed to subscribe to NameOwnerChanged 
signal for 'org.freedesktop.login1': Connection timed out
May  2 20:31:38 theory systemd[1]: Failed to subscribe to NameOwnerChanged 
signal for 'org.freedesktop.Accounts': Connection timed out
May  2 20:31:38 theory systemd[1]: Failed to subscribe to activation signal: 
Connection timed out
May  2 20:31:38 theory systemd[1]: Failed to register name: Connection timed out
May  2 20:31:38 theory systemd[1]: Failed to set up API bus: Connection timed 
out
May  2 20:31:38 theory systemd[1]: Starting Network Manager...
May  2 20:31:38 theory systemd[1]: Starting LSB: Start the GNUstep distributed 
object mapper...
May  2 20:31:38 theory systemd[1]: Started Regular background program 
processing 

Bug#821782: openafs-modules-dkms installs correctly against Linux 4.4.0-1-amd64

[Benjamin Kaduk]

On Mon, 2 May 2016, Kai-Martin Knaak wrote:

> Package: openafs-modules-dkms
> Version: 1.6.17-2
> Followup-For: Bug #821782
>
> Dear Maintainer,
>
> the same set-up which failed for kernel 4.5.0-1-amd64 installed fine
> for kernel 4.4.0-1-amd .

This is expected, unfortunately -- upstream openafs does not support the
linux 4.5 kernel yet.  I am working on some patches (since it doesn't seem
like anyone else is), but they are not quite ready yet.

-Ben

Bug#809671: should openmeeg be removed from Debian?

[Yaroslav Halchenko]

On Sun, 01 May 2016, Gianfranco Costamagna wrote:
> is it ok for you to upload something before one month or two starting from 
> today?

> we are working hard in removing vtk5 from the archive and also libpng12, and 
> this bug is
> one of the last unsolved blockers for now.

> sorry for being pushy, but it missed jessie, it will probably miss stretch 
> too if we don't act
> in a timely manner.

reporting -- there is some progress... inquiring upstream about an
idea of uploading current master
https://github.com/openmeeg/openmeeg/issues/103 otherwise seems to be in
a reasonable shape... whenever/if local builds are done I will upload
snapshot to experimental tomorrow morning and see how it feels there ;)

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

Bug#822397: FTBFS: configure: error: "Some plugins are missing dependencies

[Martin Michlmayr]

* Martin Michlmayr  [2016-04-25 14:12]:
> I filed some other bugs about this issue.  I asked if someone can
> investigate, so you could just monitor the other bugs, and possibly
> reassign yours when they do. :)
> 
> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=822396#10

This has just been fixed in connman (1.32-0.1).  Maybe you can try to
build your package, and if it works, close this bug.

-- 
Martin Michlmayr
Linux for HPE Helion, Hewlett Packard Enterprise

Processed: tagging 820965

[Debian Bug Tracking System]

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

> # Wrong release tag was set by Jelmer Vernooij 
> tags 820965 + jessie
Bug #820965 [samba-common-bin] [regression]: net usersidlist: Could not malloc 
sid array Could not get the user/sid list
Ignoring request to alter tags of bug #820965 to the same tags previously set
> thanks
Stopping processing here.

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

Processed: tagging 820965

[Debian Bug Tracking System]

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

> # Wrong release tag was set by Jelmer Vernooij 
> tags 820965 - wheezy + jessie
Bug #820965 [samba-common-bin] [regression]: net usersidlist: Could not malloc 
sid array Could not get the user/sid list
Removed tag(s) wheezy.
Bug #820965 [samba-common-bin] [regression]: net usersidlist: Could not malloc 
sid array Could not get the user/sid list
Ignoring request to alter tags of bug #820965 to the same tags previously set
> thanks
Stopping processing here.

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

Processed: your mail

[Debian Bug Tracking System]

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

> tags 822976 moreinfo
Bug #822976 [gtk3-engines-unico] gtk3-engines-unico: Package broken by GTK 3.16
Added tag(s) moreinfo.
> thanks
Stopping processing here.

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

Bug#823068: marked as done (hurd-libfuse: libfuse-dev is already provided by src:fuse)

[Debian Bug Tracking System]

Your message dated Tue, 03 May 2016 00:19:54 +
with message-id 
and subject line Bug#823068: fixed in hurd-libfuse 0.0.20140820-3
has caused the Debian Bug report #823068,
regarding hurd-libfuse: libfuse-dev is already provided by src:fuse
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.)


-- 
823068: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=823068
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: hurd-libfuse
Version: 0.0.20140820-2
Severity: serious
Control: block 815466 with -1

Hi,

only one source package can build a binary package. Even if the second
source package would build it for a separate set of architectures.
Therefore the libfuse-dev package from src:hurd-libfuse got superseded
by the package built by src:fuse (which has a higher version number).

Please drop this package again and provide a virtual package instead.
(There is some support for versioned Provides, but I'm not sure whether
it is ready for use in packages, yet, as not all tools may understand it)


Andreas
--- End Message ---
--- Begin Message ---
Source: hurd-libfuse
Source-Version: 0.0.20140820-3

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

Debian distribution maintenance software
pp.
Samuel Thibault  (supplier of updated hurd-libfuse 
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, 02 May 2016 23:53:41 +
Source: hurd-libfuse
Binary: libfuse-hurd-dev libfuse-hurd1 libfuse-hurd-dbg
Architecture: source hurd-i386
Version: 0.0.20140820-3
Distribution: unstable
Urgency: medium
Maintainer: GNU Hurd Maintainers 
Changed-By: Samuel Thibault 
Description:
 libfuse-hurd-dbg - Hurd-based FUSE API library - debug symbols
 libfuse-hurd-dev - Hurd-based FUSE API library - development files
 libfuse-hurd1 - Hurd-based FUSE API library - shared library
Closes: 823068
Changes:
 hurd-libfuse (0.0.20140820-3) unstable; urgency=medium
 .
   * Explicitly build-depend on hurd-dev to fix bootstrapping.
   * Comment libfuse-dev package for now, it actually gets superseded by the
 fuse package. We will have to wait for versioned provides in the
 policy. (Closes: #823068).
Checksums-Sha1:
 52331948f36bf40821af1a42f6a5832dd268254a 2202 hurd-libfuse_0.0.20140820-3.dsc
 1f8e893912237bdabd40d5938e9ebcc68707ffc6 3112 
hurd-libfuse_0.0.20140820-3.debian.tar.xz
 ac3aad5bfab4f60b6479f627945687c7c56c2158 52304 
libfuse-hurd-dbg_0.0.20140820-3_hurd-i386.deb
 6e7f2bad236c7523c3604832f509aa325cfc29c3 32172 
libfuse-hurd-dev_0.0.20140820-3_hurd-i386.deb
 602465281fa832ff7045ba5305cab2e6a6c082d8 20848 
libfuse-hurd1_0.0.20140820-3_hurd-i386.deb
Checksums-Sha256:
 0c139428236c9f5b8f3f594a336cf5fd09dbcd32bba7c5d5d00677f4b8700745 2202 
hurd-libfuse_0.0.20140820-3.dsc
 df638fbaf3bb11eadac7e85c30271568503ae35e8b77fc6311c73ce506842b04 3112 
hurd-libfuse_0.0.20140820-3.debian.tar.xz
 bde0886acc180b7957bd53c5610653eae330d09886cd37e1630a82e203f555af 52304 
libfuse-hurd-dbg_0.0.20140820-3_hurd-i386.deb
 a673daa186878cbaae2bad47f5b15995dd25d4af72fa3ed7d7a55c0d0a73021a 32172 
libfuse-hurd-dev_0.0.20140820-3_hurd-i386.deb
 5b098e44a32e931da23709beecbbb79f92e0312d25fa23d55d95ad88b7e777cf 20848 
libfuse-hurd1_0.0.20140820-3_hurd-i386.deb
Files:
 040d8434aaa766fb418f9b8be2f27a26 2202 libs optional 
hurd-libfuse_0.0.20140820-3.dsc
 660a164df9cd51f2644bcbc26236bce2 3112 libs optional 
hurd-libfuse_0.0.20140820-3.debian.tar.xz
 e312c62dfec7379e5eb4875c68fd446f 52304 debug extra 
libfuse-hurd-dbg_0.0.20140820-3_hurd-i386.deb
 860738202a01d1cee4eb79cdec4547be 32172 libdevel optional 
libfuse-hurd-dev_0.0.20140820-3_hurd-i386.deb
 e33ef317cd6483625acae9fd89f89c0e 20848 libs optional 
libfuse-hurd1_0.0.20140820-3_hurd-i386.deb

-BEGIN PGP SIGNATURE-
Version: GnuPG v1

iQIcBAEBCgAGBQJXJ+kgAAoJEPs9hU7TiF8Y5LkQAIpE8e7sIEC40LJmdjoKPM3b
7/TNVNtF5b18DthOZlafUb+BDBLrzUPZqtE1c8zFyTztMmRZ2ZArp43IsW5xFev5

Bug#821463: Info received (Bug#821463:NOT fixed in chromium-browser 50.0.2661.75-2)

[Bryan Cebuliak]

Interestingly   the new  package  chromium (50.0.2661.94-1~deb8u1)
[security] does  not   have  the   Aw   snap!  in   gmailbug, unlike
the  Sid  50.0.2661.94 version.

On 1 May 2016 at 06:28, Bryan Cebuliak  wrote:

> Aw snap! The   bug   persists in the  latest 50.0.2661.94 update.
>
> On 30 April 2016 at 15:12, Debian Bug Tracking System <
> ow...@bugs.debian.org> wrote:
>
>> Thank you for the additional information you have supplied regarding
>> this Bug report.
>>
>> This is an automatically generated reply to let you know your message
>> has been received.
>>
>> Your message is being forwarded to the package maintainers and other
>> interested parties for their attention; they will reply in due course.
>>
>> Your message has been sent to the package maintainer(s):
>>  Debian Chromium Maintainers 
>>
>> If you wish to submit further information on this problem, please
>> send it to 821...@bugs.debian.org.
>>
>> Please do not send mail to ow...@bugs.debian.org unless you wish
>> to report a problem with the Bug-tracking system.
>>
>> --
>> 821463: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=821463
>> Debian Bug Tracking System
>> Contact ow...@bugs.debian.org with problems
>>
>
>

Bug#823281: gnustep-make: build-indep depends on binary-arch

[Santiago Vila]

Package: src:gnustep-make
Version: 2.6.6-3
Severity: serious

Dear maintainer:

While investigating Bug #806197 I found the following policy
violations in debian/rules:


* The build target should depend on build-arch and build-indep.

Currently, it is like this:

# NOTE: The Build-Indep-Depends are only available, when building the
# build-indep packages.
build: build-arch # build-indep

Quoting policy speaking about build-arch and build-indep:

  The build target should either depend on those targets or take the
  same actions as invoking those targets would perform.

If I only install build-depends and not build-indep-depends, it follows
that I can only use the build-arch target, but that's *my* problem.

The build target should still build everything, for the case that I
install all the build-dependencies and want to build everything.


* The "build-indep" target depends indirectly on "binary-arch" (!).
This is what I see:

build-indep: debian/build-indep-stamp
clean_files += debian/build-indep-stamp
debian/build-indep-stamp: binary-arch


Well, binary-arch is where architecture-dependent .deb packages are
created (i.e. Arch: any). Quoting policy:

  The build-arch and build-indep targets must not do anything that
  might require root privilege.

Because actually creating .deb packages requires to be root (or fakeroot),
it follows that build-indep must *not* depend on any of the binary
targets.


This is probably the reason why "dpkg-buildpackage -A" fails (Bug #806197),
but I can't verify this easily because I don't have a fixed debian/rules.

Thanks.

Processed: tagging 823068

[Debian Bug Tracking System]

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

> tags 823068 + pending
Bug #823068 [src:hurd-libfuse] hurd-libfuse: libfuse-dev is already provided by 
src:fuse
Added tag(s) pending.
> thanks
Stopping processing here.

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

Processed: Re: Bug#793911: groovy2 should not release with stretch

[Debian Bug Tracking System]

Processing control commands:

> reassign -1 groovy2
Bug #793911 [groovy] groovy should not release with stretch
Bug reassigned from package 'groovy' to 'groovy2'.
Ignoring request to alter found versions of bug #793911 to the same values 
previously set
Ignoring request to alter fixed versions of bug #793911 to the same values 
previously set
> retitle -1 groovy2 should not release with stretch
Bug #793911 [groovy2] groovy should not release with stretch
Changed Bug title to 'groovy2 should not release with stretch' from 'groovy 
should not release with stretch'.

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

Bug#793911: groovy2 should not release with stretch

[Emmanuel Bourg]

Control: reassign -1 groovy2
Control: retitle -1 groovy2 should not release with stretch

Reassigning to groovy2 since groovy has been updated to the latest 2.x
release and groovy2 will eventually be removed once the reverse
dependencies are transitioned back to the original package.

Bug#818528: marked as done (madplay: FTBFS: required file `./depcomp' not found)

[Debian Bug Tracking System]

Your message dated Mon, 02 May 2016 22:47:48 +
with message-id 
and subject line Bug#818528: fixed in madplay 0.15.2b-8.1
has caused the Debian Bug report #818528,
regarding madplay: FTBFS: required file `./depcomp' not found
to be marked as done.

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

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


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

This package fails to build in unstable:

> sbuild (Debian sbuild) 0.68.0 (15 Jan 2016) on dl580gen9-02.hlinux
...
> cd . && libtoolize -c -f
> libtoolize: putting auxiliary files in '.'.
> libtoolize: copying file './ltmain.sh'
> libtoolize: putting macros in 'm4'.
> libtoolize: copying file 'm4/libtool.m4'
> libtoolize: copying file 'm4/ltoptions.m4'
> libtoolize: copying file 'm4/ltsugar.m4'
> libtoolize: copying file 'm4/ltversion.m4'
> libtoolize: copying file 'm4/lt~obsolete.m4'
> libtoolize: Consider adding 'AC_CONFIG_MACRO_DIRS([m4])' to configure.ac,
> libtoolize: and rerunning libtoolize and aclocal.
> cd . && aclocal-1.11 -I m4
> main::scan_file() called too early to check prototype at 
> /usr/bin/aclocal-1.11 line 644.
> if [ -e ./configure.ac ] || [ -e ./configure.in ]; then cd . && `which 
> autoconfyes || which autoconf`; fi
> if [ -e ./configure.ac ] || [ -e ./configure.in ]; then cd . && `which  
> autoheader1.11 || which autoheader` ; fi
> if [ -e ./Makefile.am ]; then cd . &&  automake-1.11 --foreign ; fi
> Unescaped left brace in regex is deprecated, passed through in regex; marked 
> by <-- HERE in m/\${ <-- HERE ([^ \t=:+{}]+)}/ at /usr/bin/automake-1.11 line 
> 4159.
> configure.ac:29: required file `./missing' not found
> configure.ac:29:   `automake --add-missing' can install `missing'
> Makefile.am: required file `./depcomp' not found
> Makefile.am:   `automake --add-missing' can install `depcomp'
> /usr/share/cdbs/1/class/autotools-files.mk:62: recipe for target 
> 'debian/stamp-autotools-files' failed
> make: *** [debian/stamp-autotools-files] Error 1
> dpkg-buildpackage: error: debian/rules build gave error exit status 2
> 

-- 
Martin Michlmayr
Linux for HPE Helion, Hewlett Packard Enterprise
--- End Message ---
--- Begin Message ---
Source: madplay
Source-Version: 0.15.2b-8.1

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

Debian distribution maintenance software
pp.
Paul Gevers  (supplier of updated madplay package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Fri, 22 Apr 2016 21:58:24 +0200
Source: madplay
Binary: madplay
Architecture: source
Version: 0.15.2b-8.1
Distribution: unstable
Urgency: medium
Maintainer: Mad Maintainers 
Changed-By: Paul Gevers 
Description:
 madplay- MPEG audio player in fixed point
Closes: 818528
Changes:
 madplay (0.15.2b-8.1) unstable; urgency=medium
 .
   * Non-maintainer upload.
   * Fix FTBFS by --add-missing to automake call (Closes: #818528)
Checksums-Sha1:
 6952937a1dcdd3880fa9a4c06bcdfb33ec61a50e 1585 madplay_0.15.2b-8.1.dsc
 72207fe43e6e3764302e4b8c9c2af46d466bfdff 6691 madplay_0.15.2b-8.1.diff.gz
Checksums-Sha256:
 16300e35e2d5cadd834d782b7cfb23ef4c59781f0a1d9816dd7a280e01f11f2e 1585 
madplay_0.15.2b-8.1.dsc
 77fe89ad6f07a242f3cacee619c925457a471d136bdfee597d9f3fd7c8fe 6691 
madplay_0.15.2b-8.1.diff.gz
Files:
 d32ecf64c24dd19abc43db88add63545 1585 sound optional madplay_0.15.2b-8.1.dsc
 008577a24151808f7ccd8b690e4980d9 6691 sound optional 
madplay_0.15.2b-8.1.diff.gz

-BEGIN PGP SIGNATURE-
Version: GnuPG v1

iQEcBAEBCAAGBQJXGokSAAoJEJxcmesFvXUKiB4H/AzCmWUzNwz9T8sea6y7wuA7
w6PIKN/MskKdq57S3QKOfs7IBQjTwWlP9iWttwl+km2iqSDsMEinabog21SLAsvY
Z7awrtAvoevodQxIdhHjnLsSRmVpfjmX35Z7PXxXjTBXlI2jhukKLSdZuyuucPOM
+8zcp971Qp+VaVuLzwjJs4mIxt0poe3SQCMAsfP7A6Xpx+1VN52mJBKv6PABw3YS

Bug#793630: marked as done (groovy: FTBFS due to behaviour change introduced in commons-cli 1.3)

[Debian Bug Tracking System]

Your message dated Mon, 02 May 2016 22:42:10 +
with message-id 
and subject line Bug#793630: fixed in groovy 2.4.6-1
has caused the Debian Bug report #793630,
regarding groovy: FTBFS due to behaviour change introduced in commons-cli 1.3
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.)


-- 
793630: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=793630
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:groovy
Version: 1.8.6-4
Severity: serious
Justification: fails to build from source (but built successfully in the past)

[...]

  [groovyc] /usr/lib/jvm/java-7-openjdk-amd64/jre/bin/java
  [groovyc] -classpath
  [groovyc] 
/tmp/buildd/groovy-1.8.6/target/classes:/usr/share/ant/lib/ant.jar:/usr/share/ant/lib/ant-launcher.jar:/usr/share/java/ant.jar:/usr/share/java/mockobjects-core.jar:/usr/share/java/servlet-api-2.5.jar:/usr/share/java/jsp-api-2.1.jar:/usr/share/java/commons-cli.jar:/usr/share/java/antlr.jar:/usr/share/java/ant-antlr.jar:/usr/share/java/xstream.jar:/usr/share/java/bsf.jar:/usr/share/java/jline.jar:/usr/share/java/junit4.jar:/usr/share/java/asm3.jar:/usr/share/java/asm3-util.jar:/usr/share/java/asm3-tree.jar:/usr/share/java/asm3-analysis.jar:/usr/share/java/ivy.jar:/usr/share/java/qdox.jar:/usr/share/java/jarjar.jar:/usr/share/java/jansi.jar:/usr/lib/jvm/default-java/lib/tools.jar
  [groovyc] -Dfile.encoding=ANSI_X3.4-1968
  [groovyc] -Xmx384m
  [groovyc] org.codehaus.groovy.ant.FileSystemCompilerFacade
  [groovyc] --classpath
  [groovyc] 
/tmp/buildd/groovy-1.8.6/target/classes:/usr/share/ant/lib/ant.jar:/usr/share/ant/lib/ant-launcher.jar:/usr/share/java/ant.jar:/usr/share/java/mockobjects-core.jar:/usr/share/java/servlet-api-2.5.jar:/usr/share/java/jsp-api-2.1.jar:/usr/share/java/commons-cli.jar:/usr/share/java/antlr.jar:/usr/share/java/ant-antlr.jar:/usr/share/java/xstream.jar:/usr/share/java/bsf.jar:/usr/share/java/jline.jar:/usr/share/java/junit4.jar:/usr/share/java/asm3.jar:/usr/share/java/asm3-util.jar:/usr/share/java/asm3-tree.jar:/usr/share/java/asm3-analysis.jar:/usr/share/java/ivy.jar:/usr/share/java/qdox.jar:/usr/share/java/jarjar.jar:/usr/share/java/jansi.jar:/usr/lib/jvm/default-java/lib/tools.jar
  [groovyc] -j
  [groovyc] -Fg
  [groovyc] -Fdeprecation
  [groovyc] -Jsource=1.5
  [groovyc] -Jtarget=1.5
  [groovyc] -d
  [groovyc] /tmp/buildd/groovy-1.8.6/target/classes
  [groovyc] -e
  [groovyc] /tmp/buildd/groovy-1.8.6/src/main/groovy/beans/ListenerList.groovy
  [groovyc] 
/tmp/buildd/groovy-1.8.6/src/main/groovy/beans/ListenerListASTTransformation.groovy
  [groovyc] /tmp/buildd/groovy-1.8.6/src/main/groovy/grape/GrapeIvy.groovy
  [groovyc] /tmp/buildd/groovy-1.8.6/src/main/groovy/inspect/TextNode.groovy
  [groovyc] 
/tmp/buildd/groovy-1.8.6/src/main/groovy/inspect/TextTreeNodeMaker.groovy
  [groovyc] 
/tmp/buildd/groovy-1.8.6/src/main/groovy/inspect/swingui/AstBrowser.groovy
  [groovyc] 
/tmp/buildd/groovy-1.8.6/src/main/groovy/inspect/swingui/AstBrowserProperties.groovy
  [groovyc] 
/tmp/buildd/groovy-1.8.6/src/main/groovy/inspect/swingui/AstNodeToScriptAdapter.groovy
  [groovyc] 
/tmp/buildd/groovy-1.8.6/src/main/groovy/inspect/swingui/ObjectBrowser.groovy
  [groovyc] 
/tmp/buildd/groovy-1.8.6/src/main/groovy/inspect/swingui/ScriptToTreeNodeAdapter.groovy
  [groovyc] /tmp/buildd/groovy-1.8.6/src/main/groovy/json/JsonBuilder.groovy
  [groovyc] /tmp/buildd/groovy-1.8.6/src/main/groovy/json/JsonDelegate.groovy
  [groovyc] /tmp/buildd/groovy-1.8.6/src/main/groovy/json/JsonOutput.groovy
  [groovyc] 
/tmp/buildd/groovy-1.8.6/src/main/groovy/json/StreamingJsonBuilder.groovy
  [groovyc] 
/tmp/buildd/groovy-1.8.6/src/main/groovy/lang/GroovyLogTestCase.groovy
  [groovyc] 
/tmp/buildd/groovy-1.8.6/src/main/groovy/mock/interceptor/Demand.groovy
  [groovyc] 
/tmp/buildd/groovy-1.8.6/src/main/groovy/mock/interceptor/Ignore.groovy
  [groovyc] 
/tmp/buildd/groovy-1.8.6/src/main/groovy/mock/interceptor/LooseExpectation.groovy
  [groovyc] 
/tmp/buildd/groovy-1.8.6/src/main/groovy/mock/interceptor/MockFor.groovy
  [groovyc] 
/tmp/buildd/groovy-1.8.6/src/main/groovy/mock/interceptor/MockInterceptor.groovy
  [groovyc] 
/tmp/buildd/groovy-1.8.6/src/main/groovy/mock/interceptor/StrictExpectation.groovy
  [groovyc] 
/tmp/buildd/groovy-1.8.6/src/main/groovy/mock/interceptor/StubFor.groovy
  [groovyc] 
/tmp/buildd/groovy-1.8.6/src/main/groovy/swing/LookAndFeelHelper.groovy
  [groovyc] /tmp/buildd/groovy-1.8.6/src/main/groovy/swing/SwingBuilder.groovy
  [groovyc] 

Bug#793397: marked as done (Remote execution of untrusted code, DoS (CVE-2015-3253))

[Debian Bug Tracking System]

Your message dated Mon, 02 May 2016 22:42:09 +
with message-id 
and subject line Bug#793397: fixed in groovy 2.4.6-1
has caused the Debian Bug report #793397,
regarding Remote execution of untrusted code, DoS (CVE-2015-3253)
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.)


-- 
793397: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=793397
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: groovy
Version: 1.8.6-1
Severity: grave
Tags: security upstream

cpnrodzc7, working with HP's Zero Day Initiative, discovered that
Java applications using standard Java serialization mechanisms to
decode untrusted data, and that have Groovy on their classpath, can
be passed a serialized object that will cause the application to
execute arbitrary code.

This is issue has been marked as fixed in Groovy 2.4.4 and a standalone
security patch has been made available.

CVE-2015-3253 has been assigned to this issue. 
Please mention it in the changelog when fixing the issue.

References:
 * Bulletin
   http://seclists.org/bugtraq/2015/Jul/78
 * Security update
   http://groovy-lang.org/security.html
 * Fixing commit (on 2.4.x branch)
   
https://github.com/apache/incubator-groovy/commit/09e9778e8a33052d8c27105aee5310649637233d


-- System Information:
Debian Release: 8.1
  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=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: groovy
Source-Version: 2.4.6-1

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

Debian distribution maintenance software
pp.
Emmanuel Bourg  (supplier of updated groovy 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, 02 May 2016 22:14:13 +0200
Source: groovy
Binary: groovy groovy-doc
Architecture: source all
Version: 2.4.6-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Java Maintainers 

Changed-By: Emmanuel Bourg 
Description:
 groovy - Agile dynamic language for the Java Virtual Machine
 groovy-doc - Agile dynamic language for the Java Virtual Machine (documentatio
Closes: 793397 793630 800859
Changes:
 groovy (2.4.6-1) unstable; urgency=medium
 .
   * Team upload.
   * New upstream release
 - Closes: #793397, #793630, #800859
 - Refreshed the patches
 - Updated the poms
   * Reverted to groovy as the package name
   * Depend on libasm-java (>= 5.0) instead of libasm4-java
   * Removed the build dependency on libcobertura-java
   * Standards-Version updated to 3.9.8 (no changes)
   * Use secure Vcs-* URLs
   * Updated debian/watch to track the latest releases
   * Removed the unused debian/orig-tar.sh script
Checksums-Sha1:
 5872c64000e045fc81082d33b1964f1fbad28e3e 2307 groovy_2.4.6-1.dsc
 7d7e25c4b024bd478e14454301bda03f14f150fa 2975660 groovy_2.4.6.orig.tar.xz
 92ad9e2c2c6f3da770130230d2bd980412569e98 23228 groovy_2.4.6-1.debian.tar.xz
 66b1f95ff9bb00573cd5210934cdc31265110628 3206478 groovy-doc_2.4.6-1_all.deb
 023e351e87582f49036eb199bcbb326c5695ea2d 11787994 groovy_2.4.6-1_all.deb
Checksums-Sha256:
 e8d83a0d8fd94cb5f7f226929b84a8a943426abc4298112fcdc0ce0f325ee360 2307 
groovy_2.4.6-1.dsc
 2d9ad2f0ededcc486ace193fb0768690423e389b89559772596a4ca16b6264e0 2975660 
groovy_2.4.6.orig.tar.xz
 760a0df409b43ad009d4508f646bb1dc7a69c637d0b07f969b8486e80b2737e8 23228 
groovy_2.4.6-1.debian.tar.xz
 64a1675d3e2f27a3bac9c8f7063e560f7b99da67ad6da2c4e02ced2cdbf25610 3206478 
groovy-doc_2.4.6-1_all.deb
 fa72ebe1937562fd80bd68f062a59f100cce349719f5f827eebc7eedd444ebd3 11787994 
groovy_2.4.6-1_all.deb
Files:
 2e546c8432c27e98a984a0cb2a1ab997 2307 java optional groovy_2.4.6-1.dsc
 3624580b04cfc8f5a7a14aa517e55dd9 2975660 java optional groovy_2.4.6.orig.tar.xz
 

Bug#822578: marked as done (poppler: CVE-2015-8868: heap buffer overflow)

[Debian Bug Tracking System]

Your message dated Mon, 02 May 2016 22:32:50 +
with message-id 
and subject line Bug#822578: fixed in poppler 0.26.5-2+deb8u1
has caused the Debian Bug report #822578,
regarding poppler: CVE-2015-8868: heap buffer overflow
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.)


-- 
822578: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=822578
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: poppler
Version: 0.38.0-2
Severity: important
Tags: security upstream patch fixed-upstream

Hi,

the following vulnerability was published for poppler.

CVE-2015-8868[0]:
heap overflow

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

For further information see:

[0] https://security-tracker.debian.org/tracker/CVE-2015-8868
[1] 
https://cgit.freedesktop.org/poppler/poppler/commit/?id=b3425dd3261679958cd56c0f71995c15d2124433
[2] https://bugs.freedesktop.org/show_bug.cgi?id=93476

Please adjust the affected versions in the BTS as needed. Only source
for poppler in unstable has been checked by now.

Regards,
Salvatore
--- End Message ---
--- Begin Message ---
Source: poppler
Source-Version: 0.26.5-2+deb8u1

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

Debian distribution maintenance software
pp.
Pino Toscano  (supplier of updated poppler 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, 25 Apr 2016 19:02:11 +0200
Source: poppler
Binary: libpoppler46 libpoppler-dev libpoppler-private-dev libpoppler-glib8 
libpoppler-glib-dev libpoppler-glib-doc gir1.2-poppler-0.18 libpoppler-qt4-4 
libpoppler-qt4-dev libpoppler-qt5-1 libpoppler-qt5-dev libpoppler-cpp0 
libpoppler-cpp-dev poppler-utils poppler-dbg
Architecture: source amd64 all
Version: 0.26.5-2+deb8u1
Distribution: jessie-security
Urgency: medium
Maintainer: Loic Minier 
Changed-By: Pino Toscano 
Description:
 gir1.2-poppler-0.18 - GObject introspection data for poppler-glib
 libpoppler-cpp-dev - PDF rendering library -- development files (CPP interface)
 libpoppler-cpp0 - PDF rendering library (CPP shared library)
 libpoppler-dev - PDF rendering library -- development files
 libpoppler-glib-dev - PDF rendering library -- development files (GLib 
interface)
 libpoppler-glib-doc - PDF rendering library -- documentation for the GLib 
interface
 libpoppler-glib8 - PDF rendering library (GLib-based shared library)
 libpoppler-private-dev - PDF rendering library -- private development files
 libpoppler-qt4-4 - PDF rendering library (Qt 4 based shared library)
 libpoppler-qt4-dev - PDF rendering library -- development files (Qt 4 
interface)
 libpoppler-qt5-1 - PDF rendering library (Qt 5 based shared library)
 libpoppler-qt5-dev - PDF rendering library -- development files (Qt 5 
interface)
 libpoppler46 - PDF rendering library
 poppler-dbg - PDF rendering library -- debugging symbols
 poppler-utils - PDF utilities (based on Poppler)
Closes: 822578
Changes:
 poppler (0.26.5-2+deb8u1) jessie-security; urgency=medium
 .
   * Backport upstream commit b3425dd3261679958cd56c0f71995c15d2124433 to fix
 a crash on invalid files, reported also as CVE-2015-8868; patch
 upstream_Do-not-crash-on-invalid-files.patch. (Closes: #822578)
Checksums-Sha1:
 1f09d682b1d5986379d7f7c3c032d8b754d9c71d 3288 poppler_0.26.5-2+deb8u1.dsc
 12937666faee80bae397a8338a3357e864d77d53 1595232 poppler_0.26.5.orig.tar.xz
 2aab1da9b0cdbf72571569cb60c62520240ba788 30420 
poppler_0.26.5-2+deb8u1.debian.tar.xz
 c01edb5bd7cb586c1e64525238374dd16160fd0c 1210822 
libpoppler46_0.26.5-2+deb8u1_amd64.deb
 8e84ead80a118efb71c928644c85564c804a72a0 764354 
libpoppler-dev_0.26.5-2+deb8u1_amd64.deb
 66d50a905f105105cff8b70c0499869d0a9e39bb 179206 
libpoppler-private-dev_0.26.5-2+deb8u1_amd64.deb
 b4e64f294dd999a92d185f02aa726fce0a6993b3 120698 
libpoppler-glib8_0.26.5-2+deb8u1_amd64.deb
 99d9813adfc3ea262509ce552ebdcaa551c3b840 162244 

Bug#821782: openafs-modules-dkms installs correctly against Linux 4.4.0-1-amd64

[Kai-Martin Knaak]

Package: openafs-modules-dkms
Version: 1.6.17-2
Followup-For: Bug #821782

Dear Maintainer,

the same set-up which failed for kernel 4.5.0-1-amd64 installed fine
for kernel 4.4.0-1-amd .

Regards, 

---<)kaimartin(>---

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

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

Versions of packages openafs-modules-dkms depends on:
ii  dkms   2.2.0.3-2
ii  libc6-dev  2.22-7
ii  perl   5.22.1-10

Versions of packages openafs-modules-dkms recommends:
ii  openafs-client  1.6.17-2

openafs-modules-dkms suggests no packages.

-- no debconf information



-- 
Kai-Martin Knaak   kn...@iqo.uni-hannover.de
Universität Hannover, Inst. f. Quantenoptiktel: +49-511-762-2895
Welfengarten 1, 30167 Hannover fax: +49-511-762-2211
GPG key: http://pgp.mit.edu:11371/pks/lookup?search=Knaak+kmk=get


pgpNgfkarHnZU.pgp
Description: OpenPGP digital signature

Bug#821782: openafs-modules-dkms: fails to build modules for kernel 4.5.0-1-amd64

[Kai-Martin Knaak]

Package: openafs-modules-dkms
Version: 1.6.17-2
Followup-For: Bug #821782

Dear Maintainer,

I too see this failure to build kernel 4.5.0-1

Here is the complete make log:

---/var/lib/dkms/openafs/1.6.17/build/make.log--8<---

DKMS make.log for openafs-1.6.17 for kernel 4.5.0-1-amd64 (x86_64)
Mon  2 May 22:32:18 CEST 2016
checking for a BSD-compatible install... /usr/bin/install -c
checking whether build environment is sane... yes
/var/lib/dkms/openafs/1.6.17/build/build-tools/missing: Unknown 
`--is-lightweight' option
Try `/var/lib/dkms/openafs/1.6.17/build/build-tools/missing --help' for more 
information
configure: WARNING: 'missing' script is too old or missing
checking for a thread-safe mkdir -p... /bin/mkdir -p
checking for gawk... gawk
checking whether make sets $(MAKE)... yes
checking whether make supports nested variables... yes
checking for gcc... gcc
checking whether the C compiler works... yes
checking for C compiler default output file name... a.out
checking for suffix of executables... 
checking whether we are cross compiling... no
checking for suffix of object files... o
checking whether we are using the GNU C compiler... yes
checking whether gcc accepts -g... yes
checking for gcc option to accept ISO C89... none needed
checking whether gcc understands -c and -o together... yes
checking for style of include used by make... GNU
checking dependency style of gcc... none
checking build system type... x86_64-pc-linux-gnu
checking host system type... x86_64-pc-linux-gnu
checking how to run the C preprocessor... gcc -E
checking for grep that handles long lines and -e... /bin/grep
checking for egrep... /bin/grep -E
checking for ANSI C header files... yes
checking for sys/types.h... yes
checking for sys/stat.h... yes
checking for stdlib.h... yes
checking for string.h... yes
checking for memory.h... yes
checking for strings.h... yes
checking for inttypes.h... yes
checking for stdint.h... yes
checking for unistd.h... yes
checking for flex... flex
checking lex output file root... lex.yy
checking lex library... -lfl
checking whether yytext is a pointer... yes
checking for pkg-config... /usr/bin/pkg-config
checking pkg-config is at least version 0.9.0... yes
checking for libxslt... no
checking for saxon... no
checking for xalan-j... no
checking for xsltproc... no
checking for docbook2pdf... no
checking for dblatex... no
checking for library containing strerror... none required
checking for pid_t... yes
checking for size_t... yes
checking whether ln -s works... yes
checking for ranlib... ranlib
checking for bison... bison -y
checking if lex is flex... yes
checking whether byte order is known at compile time... yes
checking whether byte ordering is bigendian... no
checking whether printf understands the %z length modifier... yes
checking your OS... linux
checking if gcc accepts -march=pentium... no
checking if gcc needs -fno-strength-reduce... yes
checking if gcc needs -fno-strict-aliasing... yes
checking if gcc supports -fno-common... yes
checking if gcc supports -pipe... yes
checking if linux kbuild requires EXTRA_CFLAGS... yes
checking for linux kernel module build works... yes
checking operation follow_link in inode_operations... no
checking operation put_link in inode_operations... no
checking for linux/config.h... no
checking for linux/completion.h... yes
checking for linux/exportfs.h... yes
checking for linux/freezer.h... yes
checking for linux/key-type.h... yes
checking for linux/semaphore.h... yes
checking for linux/seq_file.h... yes
checking for struct vfs_path... no
checking for kuid_t... yes
checking for backing_dev_info in struct address_space... no
checking for write_begin in struct address_space_operations... yes
checking for name in struct backing_dev_info... yes
checking for session_keyring in struct cred... yes
checking for ctl_name in struct ctl_table... no
checking for d_u.d_alias in struct dentry... yes
checking for d_automount in struct dentry_operations... yes
checking for i_alloc_sem in struct inode... no
checking for i_blkbits in struct inode... yes
checking for i_blksize in struct inode... no
checking for i_mutex in struct inode... yes
checking for i_security in struct inode... yes
checking for f_path in struct file... yes
checking for flock in struct file_operations... yes
checking for iterate in struct file_operations... yes
checking for read_iter in struct file_operations... yes
checking for sendfile in struct file_operations... no
checking for mount in struct file_system_type... yes
checking for truncate in struct inode_operations... no
checking for payload.value in struct key... no
checking for instantiate_prep in struct key_type... no
checking for match_preparse in struct key_type... yes
checking for preparse in struct key_type... yes
checking for msg_iter in struct msghdr... yes
checking for path in struct nameidata... no
checking for owner in struct proc_dir_entry... no
checking for s_bdi in struct super_block... yes
checking for s_d_op in 

Bug#823274: login error

[Adam D. Barratt]

Control: forcemerge 823236 -1

On Tue, 2016-05-03 at 02:00 +0530, Hema .p wrote:
> Package: sso.debian.org
> Severity: grave
> 
> Hi,
> 
> I can't login to sso.debian.org using my Alioth account "hemaprathaban-guest".
> 
> Error message:
> Authentication failed
> Invalid authenticating information

You already reported this a few hours ago, as bug #823236. Please don't
file duplicates, they don't help anyone.

Regards,

Adam

Processed: Re: Bug#823274: login error

[Debian Bug Tracking System]

Processing control commands:

> forcemerge 823236 -1
Bug #823236 [sso.debian.org] login error
Bug #823274 [sso.debian.org] login error
Merged 823236 823274

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

Bug#823227: libjpeg8: Please keep out of stretch

[Laurent Bigonville]

Le 02/05/16 à 22:18, Bill Allombert a écrit :

On Mon, May 02, 2016 at 10:03:58PM +0200, Laurent Bigonville wrote:

I am sure you mean well but the CTTE decision does not require the
removal of libjpeg62/libjpeg8 from stretch.

Well nothing in the archive depends on these packages and the
release/security team is usually not happy having multiple
implementations of almost the same library in the archive. libjpeg6b
and libjpeg8 were not in the jessie release for example.

Maybe, but this is not part of the CTTE decision.


libjpeg8 is needed for compatibility with wheezy.

I'm not sure what you mean by that.

Users upgrading from wheezy can have locally built binaries that depend
on libjpeg8.
I'm not sure that Debian is supposed to support skipping a release while 
upgrading, as said jessie, the current stable version, has not been 
released with libjpeg8.



In any case, packages removal is not done by filling serious bug to them.


Well, this is more and more used since the packages get automatically 
removed from testing if they have RC bugs.

Bug#823225: libjpeg6b: Keep libjpeg6b out of stretch

[Laurent Bigonville]

Le 02/05/16 à 22:21, Bill Allombert a écrit :

On Mon, May 02, 2016 at 03:30:25PM +0200, Laurent Bigonville wrote:

Source: libjpeg6b
Version: 1:6b2-2
Severity: serious

Hi,

I guess that libjpeg6b could stay out of testing or even removed from
the archive as nothing depends on it.

After the ctte decision[0], all the packages have transitioned to
libjpeg-turbo.

Hello Laurent,

libjpeg6b is needed for compatibility with the LSB.


FYI, Debian has never claimed to be LSB compliant, we are only 
supporting subset of LSB if I'm not wrong.


https://lists.debian.org/debian-devel/2015/07/msg00027.html

Bug#823274: login error

[Hema .p]

Package: sso.debian.org
Severity: grave

Hi,

I can't login to sso.debian.org using my Alioth account "hemaprathaban-guest".

Error message:
Authentication failed
Invalid authenticating information



Thanks
Hema

Bug#823225: marked as done (libjpeg6b: Keep libjpeg6b out of stretch)

[Debian Bug Tracking System]

Your message dated Mon, 2 May 2016 22:21:13 +0200
with message-id <20160502202113.GG3855@yellowpig>
and subject line Re: Bug#823225: libjpeg6b: Keep libjpeg6b out of stretch
has caused the Debian Bug report #823225,
regarding libjpeg6b: Keep libjpeg6b out of stretch
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.)


-- 
823225: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=823225
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: libjpeg6b
Version: 1:6b2-2
Severity: serious

Hi,

I guess that libjpeg6b could stay out of testing or even removed from
the archive as nothing depends on it.

After the ctte decision[0], all the packages have transitioned to
libjpeg-turbo.

Cheers,

Laurent Bigonville

[0] https://lists.debian.org/debian-devel-announce/2014/08/msg0.html

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

Kernel: Linux 4.5.0-2-amd64 (SMP w/8 CPU cores)
Locale: LANG=fr_BE.utf8, LC_CTYPE=fr_BE.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
--- End Message ---
--- Begin Message ---
On Mon, May 02, 2016 at 03:30:25PM +0200, Laurent Bigonville wrote:
> Source: libjpeg6b
> Version: 1:6b2-2
> Severity: serious
> 
> Hi,
> 
> I guess that libjpeg6b could stay out of testing or even removed from
> the archive as nothing depends on it.
> 
> After the ctte decision[0], all the packages have transitioned to
> libjpeg-turbo.

Hello Laurent,

libjpeg6b is needed for compatibility with the LSB.

Closing this bug.

Cheers,
-- 
Bill. 

Imagine a large red swirl here. --- End Message ---

Bug#823227: libjpeg8: Please keep out of stretch

[Bill Allombert]

On Mon, May 02, 2016 at 10:03:58PM +0200, Laurent Bigonville wrote:
> >I am sure you mean well but the CTTE decision does not require the
> >removal of libjpeg62/libjpeg8 from stretch.
> Well nothing in the archive depends on these packages and the
> release/security team is usually not happy having multiple
> implementations of almost the same library in the archive. libjpeg6b
> and libjpeg8 were not in the jessie release for example.

Maybe, but this is not part of the CTTE decision.

> >libjpeg8 is needed for compatibility with wheezy.
> I'm not sure what you mean by that.

Users upgrading from wheezy can have locally built binaries that depend
on libjpeg8. 

In any case, packages removal is not done by filling serious bug to them.

Cheers,
-- 
Bill. 

Imagine a large red swirl here. 

Processed: found 817778 in 1.0~pre3-1

[Debian Bug Tracking System]

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

> # also found in 1.0~pre3-1
> found 817778 1.0~pre3-1
Bug #817778 [info-beamer] silkscreen font is not DFSG compliant
Marked as found in versions info-beamer/1.0~pre3-1.
> thanks
Stopping processing here.

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

Bug#823227: libjpeg8: Please keep out of stretch

[Laurent Bigonville]

Le 02/05/16 à 20:38, Bill Allombert a écrit :

On Mon, May 02, 2016 at 03:41:43PM +0200, Laurent Bigonville wrote:

Source: libjpeg8
Version: 8d1-2
Severity: serious

Hi,

I guess that libjpeg8 could stay out of testing or even removed from the
archive. Only one package (ipe) depends on libjpeg8, and that package
builds fine with libjpeg-turbo.

After the ctte decision[0], all the packages have transitioned to
libjpeg-turbo.

Hello Laurent,

Hello Bill,


I am sure you mean well but the CTTE decision does not require the
removal of libjpeg62/libjpeg8 from stretch.
Well nothing in the archive depends on these packages and the 
release/security team is usually not happy having multiple 
implementations of almost the same library in the archive. libjpeg6b and 
libjpeg8 were not in the jessie release for example.


If they will not be part of next release (stretch), it might be 
interesting to remove them early to avoid other packages to depend on 
them again.

libjpeg8 is needed for compatibility with wheezy.

I'm not sure what you mean by that.

Bug#818432: [Debichem-devel] Bug#818432: espresso: FTBFS on armel and mips: hangs during the build

[Aurelien Jarno]

On 2016-05-02 19:25, Michael Banck wrote:
> Hi Aurelien,
> 
> On Mon, May 02, 2016 at 05:35:35PM +0200, Aurelien Jarno wrote:
> > control: retitle -1 espresso: FTBFS on armel: hangs during the build
> > 
> > On 2016-03-17 00:49, Emilio Pozuelo Monfort wrote:
> > > Source: espresso
> > > Version: 5.1+dfsg-4
> > > Severity: serious
> > > 
> > > Your package failed to build on armel and mips. Logs at
> > > 
> > > https://buildd.debian.org/status/package.php?p=espresso
> > 
> > The MIPS issue was due to the lack of FPU on the build daemon. It has
> > now been built successfully on mips-aql-06. Retitling the bug
> > accordingly.
> 
> Wow, that's great news we finally have an FPU enabled mips autobuilder.
> 
> Not just for Quantum Espresso, but for a whole bunch of other Debichem
> packages as well.
> 
> Will it be possible to say "please requeue on mips-aql-06" in the
> future, in case we suspect testsuite timeouts are due to lack of FPUs?

It means blacklisting the packages on the other build daemons, but
that's doable. We'll also get more autobuilders with FPU in the next
days, so that should get easier.

Aurelien

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

Processed: Re: Bug#822393: marked as done ( and conflict needs to be resolved)

[Debian Bug Tracking System]

Processing control commands:

> reopen -1
Bug #822393 {Done: Mateusz Łukasik } [src:linux,src:glibc] 
 and  conflict needs to be resolved
Bug #822378 {Done: Mateusz Łukasik } [src:linux,src:glibc] 
 and  conflict needs to be resolved
Bug #822396 {Done: Mateusz Łukasik } [src:linux,src:glibc] 
 and  conflict needs to be resolved
'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 connman/1.32-0.1.
No longer marked as fixed in versions connman/1.32-0.1.
No longer marked as fixed in versions connman/1.32-0.1.
> notfixed -1 connman/1.32-0.1
Bug #822393 [src:linux,src:glibc]  and  conflict needs to 
be resolved
Bug #822378 [src:linux,src:glibc]  and  conflict needs to 
be resolved
Bug #822396 [src:linux,src:glibc]  and  conflict needs to 
be resolved
The source connman and version 1.32-0.1 do not appear to match any binary 
packages
Ignoring request to alter fixed versions of bug #822393 to the same values 
previously set
Ignoring request to alter fixed versions of bug #822378 to the same values 
previously set
Ignoring request to alter fixed versions of bug #822396 to the same values 
previously set

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

Bug#822393: marked as done ( and conflict needs to be resolved)

[Ben Hutchings]

Control: reopen -1
Control: notfixed -1 connman/1.32-0.1

On Mon, 2016-05-02 at 18:54 +, Debian Bug Tracking System wrote:
> Your message dated Mon, 02 May 2016 18:50:07 +
> with message-id 
> and subject line Bug#822393: fixed in connman 1.32-0.1
> has caused the Debian Bug report #822393,
> regarding  and  conflict needs to be resolved
> to be marked as done.

This bug was not assigned to connman any more.  You made connman work
around it, but you didn't fix the bug.

Ben.

-- 
Ben Hutchings
Life is what happens to you while you're busy making other plans.
   - John Lennon


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

Bug#822396: marked as done ( and conflict needs to be resolved)

[Debian Bug Tracking System]

Your message dated Mon, 02 May 2016 18:50:07 +
with message-id 
and subject line Bug#822393: fixed in connman 1.32-0.1
has caused the Debian Bug report #822393,
regarding  and  conflict needs to be resolved
to be marked as done.

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

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


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

This package fails to build in unstable:

> sbuild (Debian sbuild) 0.68.0 (15 Jan 2016) on dl580gen9-02.hlinux
...
> libtool: compile:  gcc -DHAVE_CONFIG_H -I. -I../../../.. 
> -I../../../../src/libstrongswan -I../../../../src/libcharon -Wdate-time 
> -D_FORTIFY_SOURCE=2 -rdynamic -g -O2 -fstack-protector-strong -Wformat 
> -Werror=format-security -include /<>/config.h -c 
> connmark_listener.c  -fPIC -DPIC -o .libs/connmark_listener.o
> In file included from /usr/include/libiptc/ipt_kernel_headers.h:13:0,
>  from /usr/include/libiptc/libiptc.h:6,
>  from connmark_listener.c:24:
> /usr/include/linux/if.h:71:2: error: redeclaration of enumerator 'IFF_UP'
>   IFF_UP= 1<<0,  /* sysfs */
>   ^
> /usr/include/net/if.h:44:5: note: previous definition of 'IFF_UP' was here
>  IFF_UP = 0x1,  /* Interface is up.  */
>  ^
> /usr/include/linux/if.h:72:2: error: redeclaration of enumerator 
> 'IFF_BROADCAST'
>   IFF_BROADCAST   = 1<<1,  /* __volatile__ */
>   ^
> /usr/include/net/if.h:46:5: note: previous definition of 'IFF_BROADCAST' was 
> here
>  IFF_BROADCAST = 0x2, /* Broadcast address valid.  */
>  ^
> /usr/include/linux/if.h:73:2: error: redeclaration of enumerator 'IFF_DEBUG'
>   IFF_DEBUG   = 1<<2,  /* sysfs */
>   ^
> /usr/include/net/if.h:48:5: note: previous definition of 'IFF_DEBUG' was here
>  IFF_DEBUG = 0x4,  /* Turn on debugging.  */
>  ^
> /usr/include/linux/if.h:74:2: error: redeclaration of enumerator 
> 'IFF_LOOPBACK'
>   IFF_LOOPBACK   = 1<<3,  /* __volatile__ */
>   ^
> /usr/include/net/if.h:50:5: note: previous definition of 'IFF_LOOPBACK' was 
> here
>  IFF_LOOPBACK = 0x8,  /* Is a loopback net.  */
>  ^
> /usr/include/linux/if.h:75:2: error: redeclaration of enumerator 
> 'IFF_POINTOPOINT'
>   IFF_POINTOPOINT   = 1<<4,  /* __volatile__ */
>   ^
> /usr/include/net/if.h:52:5: note: previous definition of 'IFF_POINTOPOINT' 
> was here
>  IFF_POINTOPOINT = 0x10, /* Interface is point-to-point link.  */
>  ^
> /usr/include/linux/if.h:76:2: error: redeclaration of enumerator 
> 'IFF_NOTRAILERS'
>   IFF_NOTRAILERS   = 1<<5,  /* sysfs */
>   ^
> /usr/include/net/if.h:54:5: note: previous definition of 'IFF_NOTRAILERS' was 
> here
>  IFF_NOTRAILERS = 0x20, /* Avoid use of trailers.  */
>  ^
> /usr/include/linux/if.h:77:2: error: redeclaration of enumerator 'IFF_RUNNING'
>   IFF_RUNNING   = 1<<6,  /* __volatile__ */
>   ^
> /usr/include/net/if.h:56:5: note: previous definition of 'IFF_RUNNING' was 
> here
>  IFF_RUNNING = 0x40,  /* Resources allocated.  */
>  ^
> /usr/include/linux/if.h:78:2: error: redeclaration of enumerator 'IFF_NOARP'
>   IFF_NOARP   = 1<<7,  /* sysfs */
>   ^
> /usr/include/net/if.h:58:5: note: previous definition of 'IFF_NOARP' was here
>  IFF_NOARP = 0x80,  /* No address resolution protocol.  */
>  ^
> /usr/include/linux/if.h:79:2: error: redeclaration of enumerator 'IFF_PROMISC'
>   IFF_PROMISC   = 1<<8,  /* sysfs */
>   ^
> /usr/include/net/if.h:60:5: note: previous definition of 'IFF_PROMISC' was 
> here
>  IFF_PROMISC = 0x100, /* Receive all packets.  */
>  ^
> /usr/include/linux/if.h:80:2: error: redeclaration of enumerator 
> 'IFF_ALLMULTI'
>   IFF_ALLMULTI   = 1<<9,  /* sysfs */
>   ^
> /usr/include/net/if.h:64:5: note: previous definition of 'IFF_ALLMULTI' was 
> here
>  IFF_ALLMULTI = 0x200, /* Receive all multicast packets.  */
>  ^
> /usr/include/linux/if.h:81:2: error: redeclaration of enumerator 'IFF_MASTER'
>   IFF_MASTER   = 1<<10, /* __volatile__ */
>   ^
> /usr/include/net/if.h:67:5: note: previous definition of 'IFF_MASTER' was here
>  IFF_MASTER = 0x400,  /* Master of a load balancer.  */
>  ^
> /usr/include/linux/if.h:82:2: error: redeclaration of enumerator 'IFF_SLAVE'
>   IFF_SLAVE   = 1<<11, /* __volatile__ */
>   ^
> /usr/include/net/if.h:69:5: note: previous definition of 'IFF_SLAVE' was here
>  IFF_SLAVE = 0x800,  /* Slave of a load balancer.  */
>  ^
> /usr/include/linux/if.h:83:2: error: redeclaration of enumerator 
> 'IFF_MULTICAST'
>   

Bug#822393: marked as done ( and conflict needs to be resolved)

[Debian Bug Tracking System]

Your message dated Mon, 02 May 2016 18:50:07 +
with message-id 
and subject line Bug#822393: fixed in connman 1.32-0.1
has caused the Debian Bug report #822393,
regarding  and  conflict needs to be resolved
to be marked as done.

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

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


-- 
822393: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=822393
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: connman
Version: 1.21-1.2
Severity: serious

This package fails to build in unstable:

> sbuild (Debian sbuild) 0.68.0 (15 Jan 2016) on dl580gen9-02.hlinux
...
> gcc -DHAVE_CONFIG_H -I.  -I./include -I./gdbus -Wdate-time 
> -D_FORTIFY_SOURCE=2 -I/usr/include/dbus-1.0 
> -I/usr/lib/x86_64-linux-gnu/dbus-1.0/include -I/usr/include/glib-2.0 
> -I/usr/lib/x86_64-linux-gnu/glib-2.0/include -I/usr/include/p11-kit-1  
> -DCONNMAN_PLUGIN_BUILTIN -DSTATEDIR=\""/var/run/connman"\" 
> -DPLUGINDIR=\""/usr/lib/x86_64-linux-gnu/connman/plugins"\" 
> -DSCRIPTDIR=\""/usr/lib/x86_64-linux-gnu/connman/scripts"\" 
> -DSTORAGEDIR=\""/var/lib/connman\"" 
> -DVPN_STORAGEDIR=\""/var/lib/connman-vpn\"" -DCONFIGDIR=\""/etc/connman\"" 
> -I./src -g -O2 -fstack-protector-strong -Wformat -Werror=format-security -c 
> -o src/src_connmand-inotify.o `test -f 'src/inotify.c' || echo 
> './'`src/inotify.c
> In file included from /usr/include/xtables.h:16:0,
>  from src/iptables.c:33:
> /usr/include/linux/if.h:71:2: error: redeclaration of enumerator 'IFF_UP'
>   IFF_UP= 1<<0,  /* sysfs */
>   ^
> /usr/include/net/if.h:44:5: note: previous definition of 'IFF_UP' was here
>  IFF_UP = 0x1,  /* Interface is up.  */
>  ^
> /usr/include/linux/if.h:72:2: error: redeclaration of enumerator 
> 'IFF_BROADCAST'
>   IFF_BROADCAST   = 1<<1,  /* __volatile__ */
>   ^
> /usr/include/net/if.h:46:5: note: previous definition of 'IFF_BROADCAST' was 
> here
>  IFF_BROADCAST = 0x2, /* Broadcast address valid.  */
>  ^
> /usr/include/linux/if.h:73:2: error: redeclaration of enumerator 'IFF_DEBUG'
>   IFF_DEBUG   = 1<<2,  /* sysfs */
>   ^
> /usr/include/net/if.h:48:5: note: previous definition of 'IFF_DEBUG' was here
>  IFF_DEBUG = 0x4,  /* Turn on debugging.  */
>  ^
> /usr/include/linux/if.h:74:2: error: redeclaration of enumerator 
> 'IFF_LOOPBACK'
>   IFF_LOOPBACK   = 1<<3,  /* __volatile__ */
>   ^
> /usr/include/net/if.h:50:5: note: previous definition of 'IFF_LOOPBACK' was 
> here
>  IFF_LOOPBACK = 0x8,  /* Is a loopback net.  */
>  ^
> /usr/include/linux/if.h:75:2: error: redeclaration of enumerator 
> 'IFF_POINTOPOINT'
>   IFF_POINTOPOINT   = 1<<4,  /* __volatile__ */
>   ^
> /usr/include/net/if.h:52:5: note: previous definition of 'IFF_POINTOPOINT' 
> was here
>  IFF_POINTOPOINT = 0x10, /* Interface is point-to-point link.  */
>  ^
> /usr/include/linux/if.h:76:2: error: redeclaration of enumerator 
> 'IFF_NOTRAILERS'
>   IFF_NOTRAILERS   = 1<<5,  /* sysfs */
>   ^
> /usr/include/net/if.h:54:5: note: previous definition of 'IFF_NOTRAILERS' was 
> here
>  IFF_NOTRAILERS = 0x20, /* Avoid use of trailers.  */
>  ^
> /usr/include/linux/if.h:77:2: error: redeclaration of enumerator 'IFF_RUNNING'
>   IFF_RUNNING   = 1<<6,  /* __volatile__ */
>   ^
> /usr/include/net/if.h:56:5: note: previous definition of 'IFF_RUNNING' was 
> here
>  IFF_RUNNING = 0x40,  /* Resources allocated.  */
>  ^
> /usr/include/linux/if.h:78:2: error: redeclaration of enumerator 'IFF_NOARP'
>   IFF_NOARP   = 1<<7,  /* sysfs */
>   ^
> /usr/include/net/if.h:58:5: note: previous definition of 'IFF_NOARP' was here
>  IFF_NOARP = 0x80,  /* No address resolution protocol.  */
>  ^
> /usr/include/linux/if.h:79:2: error: redeclaration of enumerator 'IFF_PROMISC'
>   IFF_PROMISC   = 1<<8,  /* sysfs */
>   ^
> /usr/include/net/if.h:60:5: note: previous definition of 'IFF_PROMISC' was 
> here
>  IFF_PROMISC = 0x100, /* Receive all packets.  */
>  ^
> /usr/include/linux/if.h:80:2: error: redeclaration of enumerator 
> 'IFF_ALLMULTI'
>   IFF_ALLMULTI   = 1<<9,  /* sysfs */
>   ^
> /usr/include/net/if.h:64:5: note: previous definition of 'IFF_ALLMULTI' was 
> here
>  IFF_ALLMULTI = 0x200, /* Receive all multicast packets.  */
>  ^
> /usr/include/linux/if.h:81:2: error: redeclaration of enumerator 'IFF_MASTER'
>   IFF_MASTER   = 1<<10, /* __volatile__ */
>   ^
> /usr/include/net/if.h:67:5: note: previous definition of 'IFF_MASTER' was here
>  IFF_MASTER = 0x400,  /* Master of a load balancer.  */
>  ^
> /usr/include/linux/if.h:82:2: error: redeclaration of 

Bug#813647: marked as done (connman: daemon no longer starts after upgrade)

[Debian Bug Tracking System]

Your message dated Mon, 02 May 2016 18:50:07 +
with message-id 
and subject line Bug#813647: fixed in connman 1.32-0.1
has caused the Debian Bug report #813647,
regarding connman: daemon no longer starts after upgrade
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.)


-- 
813647: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=813647
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: connman
Version: 1.21-1.2+b2
Severity: grave
Justification: renders package unusable

Connman fails to start. See the attached 'connmand.out' for the segfault
which is printed on running `connmand -n --debug`.

Thanks for your help.
--
Morgan Hamill

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

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

Versions of packages connman depends on:
ii  dbus 1.10.6-1
ii  init-system-helpers  1.24
ii  libc62.21-7
ii  libdbus-1-3  1.10.6-1
ii  libglib2.0-0 2.46.2-3
ii  libgnutls30  3.4.8-2
ii  libreadline6 6.3-8+b4
ii  libxtables11 1.6.0-2
ii  lsb-base 9.20160110

Versions of packages connman recommends:
ii  bluez  5.36-1
pn  ofono  
ii  wpasupplicant  2.3-2.3

Versions of packages connman suggests:
pn  indicator-network  

-- no debconf information
connmand[5781]: Connection Manager version 1.21
connmand[5781]: src/dbus.c:__connman_dbus_init() 
connmand[5781]: src/main.c:parse_config() parsing main.conf
connmand[5781]: src/inotify.c:__connman_inotify_init() 
connmand[5781]: src/technology.c:__connman_technology_init() 
connmand[5781]: src/storage.c:storage_load() Loading /var/lib/connman/settings
connmand[5781]: src/storage.c:storage_load() Loading /var/lib/connman/settings
connmand[5781]: src/notifier.c:__connman_notifier_init() 
connmand[5781]: src/agent.c:__connman_agent_init() 
connmand[5781]: src/service.c:__connman_service_init() 
connmand[5781]: src/agent.c:connman_agent_driver_register() Registering driver 
0x6be180 name service
connmand[5781]: src/storage.c:storage_load() Loading 
/var/lib/connman/ethernet_d637d70df97b_cable/settings
connmand[5781]: src/storage.c:storage_load() Loading 
/var/lib/connman/wifi_5ce0c5bea51e_546f6d4e546f6d735f58656e2077696669_managed_none/settings
connmand[5781]: src/storage.c:storage_load() Loading 
/var/lib/connman/ethernet_fec4bf467024_cable/settings
connmand[5781]: src/storage.c:storage_load() Loading 
/var/lib/connman/wifi_5ce0c5bea51e_616e7369626c65_managed_psk/settings
connmand[5781]: src/storage.c:storage_load() Loading 
/var/lib/connman/ethernet_9af97dbef0dd_cable/settings
connmand[5781]: src/storage.c:storage_load() Loading 
/var/lib/connman/wifi_5ce0c5bea51e_494e46494e4954554d6b677a7a_managed_psk/settings
connmand[5781]: src/storage.c:storage_load() Loading 
/var/lib/connman/wifi_5ce0c5bea51e_4c41504c2d5075626c6963_managed_none/settings
connmand[5781]: src/storage.c:storage_load() Loading 
/var/lib/connman/wifi_5ce0c5bea51e_476f6f676c6520537461726275636b73_managed_none/settings
connmand[5781]: src/storage.c:storage_load() Loading 
/var/lib/connman/ethernet_fe5400fc3e5f_cable/settings
connmand[5781]: src/storage.c:storage_load() Loading 
/var/lib/connman/wifi_5ce0c5bea51e_44415649442031_managed_psk/settings
connmand[5781]: src/storage.c:storage_load() Loading 
/var/lib/connman/ethernet_aed21fe1c27c_cable/settings
connmand[5781]: src/storage.c:storage_load() Loading 
/var/lib/connman/wifi_5ce0c5bea51e_73756265746861_managed_psk/settings
connmand[5781]: src/storage.c:storage_load() Loading 
/var/lib/connman/wifi_5ce0c5bea51e_42444c7075626c6963_managed_none/settings
connmand[5781]: src/storage.c:storage_load() Loading 
/var/lib/connman/ethernet_feb7764a17b1_cable/settings
connmand[5781]: src/storage.c:storage_load() Loading 
/var/lib/connman/wifi_5ce0c5bea51e_537461706c6573486f7473706f74_managed_none/settings
connmand[5781]: src/storage.c:storage_load() Loading 
/var/lib/connman/ethernet_fe2ae7117c92_cable/settings
connmand[5781]: src/storage.c:storage_load() Loading 
/var/lib/connman/wifi_5ce0c5bea51e_776972656c657373_managed_psk/settings
connmand[5781]: src/storage.c:storage_load() Loading 
/var/lib/connman/wifi_5ce0c5bea51e_56696c6c6167652043616665204775657374204e6574776f726b_managed_psk/settings

Bug#822378: marked as done ( and conflict needs to be resolved)

[Debian Bug Tracking System]

Your message dated Mon, 02 May 2016 18:50:07 +
with message-id 
and subject line Bug#822393: fixed in connman 1.32-0.1
has caused the Debian Bug report #822393,
regarding  and  conflict needs to be resolved
to be marked as done.

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

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


-- 
822393: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=822393
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: xtables-addons
Version: 2.10-1
Severity: serious

This package fails to build in unstable:

> sbuild (Debian sbuild) 0.68.0 (15 Jan 2016) on dl580gen9-02.hlinux
...
> make[6]: Entering directory '/<>/extensions/pknock'
> gcc -DHAVE_CONFIG_H -I. -I../..  -D_LARGEFILE_SOURCE=1 -D_LARGE_FILES 
> -D_FILE_OFFSET_BITS=64  -D_REENTRANT -I../../include 
> -I/<>/extensions -Wdate-time -D_FORTIFY_SOURCE=2 -Wall 
> -Waggregate-return -Wmissing-declarations  -Wmissing-prototypes 
> -Wredundant-decls -Wshadow -Wstrict-prototypes -Winline -pipe  -g -O2 
> -fstack-protector-strong -Wformat -Werror=format-security -c -o pknlusr.o 
> pknlusr.c
> /bin/bash ../../libtool  --tag=CC   --mode=link gcc -Wall -Waggregate-return 
> -Wmissing-declarations   -Wmissing-prototypes -Wredundant-decls -Wshadow 
> -Wstrict-prototypes -Winline -pipe  -g -O2 -fstack-protector-strong 
> -Wformat -Werror=format-security  -Wl,-z,relro -o pknlusr pknlusr.o  
> libtool: link: gcc -Wall -Waggregate-return -Wmissing-declarations 
> -Wmissing-prototypes -Wredundant-decls -Wshadow -Wstrict-prototypes -Winline 
> -pipe -g -O2 -fstack-protector-strong -Wformat -Werror=format-security -Wl,-z 
> -Wl,relro -o pknlusr pknlusr.o 
> make -f ../../Makefile.iptrules all;
> make[7]: Entering directory '/<>/extensions/pknock'
>   CC libxt_pknock.oo
> In file included from /usr/include/xtables.h:16:0,
>  from libxt_pknock.c:15:
> /usr/include/linux/if.h:71:2: error: redeclaration of enumerator 'IFF_UP'
>   IFF_UP= 1<<0,  /* sysfs */
>   ^
> /usr/include/net/if.h:44:5: note: previous definition of 'IFF_UP' was here
>  IFF_UP = 0x1,  /* Interface is up.  */
>  ^
> /usr/include/linux/if.h:72:2: error: redeclaration of enumerator 
> 'IFF_BROADCAST'
>   IFF_BROADCAST   = 1<<1,  /* __volatile__ */
>   ^
> /usr/include/net/if.h:46:5: note: previous definition of 'IFF_BROADCAST' was 
> here
>  IFF_BROADCAST = 0x2, /* Broadcast address valid.  */
>  ^
> /usr/include/linux/if.h:73:2: error: redeclaration of enumerator 'IFF_DEBUG'
>   IFF_DEBUG   = 1<<2,  /* sysfs */
>   ^
> /usr/include/net/if.h:48:5: note: previous definition of 'IFF_DEBUG' was here
>  IFF_DEBUG = 0x4,  /* Turn on debugging.  */
>  ^
> /usr/include/linux/if.h:74:2: error: redeclaration of enumerator 
> 'IFF_LOOPBACK'
>   IFF_LOOPBACK   = 1<<3,  /* __volatile__ */
>   ^
> /usr/include/net/if.h:50:5: note: previous definition of 'IFF_LOOPBACK' was 
> here
>  IFF_LOOPBACK = 0x8,  /* Is a loopback net.  */
>  ^
> /usr/include/linux/if.h:75:2: error: redeclaration of enumerator 
> 'IFF_POINTOPOINT'
>   IFF_POINTOPOINT   = 1<<4,  /* __volatile__ */
>   ^
> /usr/include/net/if.h:52:5: note: previous definition of 'IFF_POINTOPOINT' 
> was here
>  IFF_POINTOPOINT = 0x10, /* Interface is point-to-point link.  */
>  ^
> /usr/include/linux/if.h:76:2: error: redeclaration of enumerator 
> 'IFF_NOTRAILERS'
>   IFF_NOTRAILERS   = 1<<5,  /* sysfs */
>   ^
> /usr/include/net/if.h:54:5: note: previous definition of 'IFF_NOTRAILERS' was 
> here
>  IFF_NOTRAILERS = 0x20, /* Avoid use of trailers.  */
>  ^
> /usr/include/linux/if.h:77:2: error: redeclaration of enumerator 'IFF_RUNNING'
>   IFF_RUNNING   = 1<<6,  /* __volatile__ */
>   ^
> /usr/include/net/if.h:56:5: note: previous definition of 'IFF_RUNNING' was 
> here
>  IFF_RUNNING = 0x40,  /* Resources allocated.  */
>  ^
> /usr/include/linux/if.h:78:2: error: redeclaration of enumerator 'IFF_NOARP'
>   IFF_NOARP   = 1<<7,  /* sysfs */
>   ^
> /usr/include/net/if.h:58:5: note: previous definition of 'IFF_NOARP' was here
>  IFF_NOARP = 0x80,  /* No address resolution protocol.  */
>  ^
> /usr/include/linux/if.h:79:2: error: redeclaration of enumerator 'IFF_PROMISC'
>   IFF_PROMISC   = 1<<8,  /* sysfs */
>   ^
> /usr/include/net/if.h:60:5: note: previous definition of 'IFF_PROMISC' was 
> here
>  IFF_PROMISC = 0x100, /* Receive all packets.  */
>  ^
> /usr/include/linux/if.h:80:2: error: redeclaration of enumerator 
> 'IFF_ALLMULTI'
>   IFF_ALLMULTI   = 1<<9,  /* sysfs */
>   ^
> /usr/include/net/if.h:64:5: note: previous definition of 

Bug#823227: marked as done (libjpeg8: Please keep out of stretch)

[Debian Bug Tracking System]

Your message dated Mon, 2 May 2016 20:38:23 +0200
with message-id <20160502183823.GE3855@yellowpig>
and subject line Re: Bug#823227: libjpeg8: Please keep out of stretch
has caused the Debian Bug report #823227,
regarding libjpeg8: Please keep out of stretch
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.)


-- 
823227: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=823227
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: libjpeg8
Version: 8d1-2
Severity: serious

Hi,

I guess that libjpeg8 could stay out of testing or even removed from the
archive. Only one package (ipe) depends on libjpeg8, and that package
builds fine with libjpeg-turbo.

After the ctte decision[0], all the packages have transitioned to
libjpeg-turbo.

Cheers,

Laurent Bigonville

[0] https://lists.debian.org/debian-devel-announce/2014/08/msg0.html

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

Kernel: Linux 4.5.0-2-amd64 (SMP w/8 CPU cores)
Locale: LANG=fr_BE.utf8, LC_CTYPE=fr_BE.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
--- End Message ---
--- Begin Message ---
On Mon, May 02, 2016 at 03:41:43PM +0200, Laurent Bigonville wrote:
> Source: libjpeg8
> Version: 8d1-2
> Severity: serious
> 
> Hi,
> 
> I guess that libjpeg8 could stay out of testing or even removed from the
> archive. Only one package (ipe) depends on libjpeg8, and that package
> builds fine with libjpeg-turbo.
> 
> After the ctte decision[0], all the packages have transitioned to
> libjpeg-turbo.

Hello Laurent,

I am sure you mean well but the CTTE decision does not require the
removal of libjpeg62/libjpeg8 from stretch.

libjpeg8 is needed for compatibility with wheezy.

Closing this bug.
Cheers,
-- 
Bill. 

Imagine a large red swirl here. --- End Message ---

Processed: severity of 823156 is important

[Debian Bug Tracking System]

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

> severity 823156 important
Bug #823156 [linux-headers-4.5.0-0.bpo.1-all-amd64] 
linux-headers-4.5.0-0.bpo.1-all-amd64: breaks kwin (abort with fatal error) on 
Thinkpad T560
Severity set to 'important' from 'critical'
> thanks
Stopping processing here.

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

Bug#823156: linux-image-4.5.0-0.bpo.1-amd64: Backport Kernel breaks kwin (FATAL ERROR, while trying to open display)

[Ben Hutchings]

Control: reopen -1
Control: tag -1 moreinfo

On Mon, 2016-05-02 at 16:38 +0200, Maria wrote:
> thanks to your kind hints how to gather the information I was able to
> fill this out with more information.

Thank you for responding.

> Actually I have to correct my information in the original post: It was
> not Linux Mint which managed to use WLAN (it actually didn't).
> It was the new Kubuntu 16-04 which managed to use WLAN. I didn't use it
> as other things where too much of a mess. I tried so much Distros these
> two days I must have mixed it up - sorry.
> So here is the additional information.
> 
> For more Information about my Kernelmessages please have a look at the
> attached Textfiles.
> 
> Thanks alot for your kind work - Maria
> 
> 
> -- Package-specific info:
> ** Version:
> Linux version 4.5.0-0.bpo.1-amd64 (debian-ker...@lists.debian.org) (gcc
> version 4.9.2 (Debian 4.9.2-10) ) #1 SMP Debian 4.5.1-1~bpo8+1 (2016-04-20)
> 
> ** Command line:
> BOOT_IMAGE=/vmlinuz-4.5.0-0.bpo.1-amd64 root=/dev/mapper/sda3--vg-root
> ro quiet
> 
> ** Tainted: E (8192)
>  * Unsigned module has been loaded (currently expected).
> 
> ** Kernel log:
> [   25.990301] Bluetooth: hci0: Secure boot is enabled
> [   25.990302] Bluetooth: hci0: OTP lock is enabled
> [   25.990303] Bluetooth: hci0: API lock is enabled
> [   25.990305] Bluetooth: hci0: Debug lock is disabled
> [   25.990306] Bluetooth: hci0: Minimum firmware build 1 week 10 2014
> [   25.990321] bluetooth hci0: firmware: failed to load
> intel/ibt-11-5.sfi (-2)
> [   25.990325] bluetooth hci0: Direct firmware load for
> intel/ibt-11-5.sfi failed with error -2
> [   25.990327] Bluetooth: hci0: Failed to load Intel firmware file (-2)
> [   25.991879] uvcvideo: Found UVC 1.00 device Integrated Camera (5986:0706)
> [   25.998348] Intel(R) Wireless WiFi driver for Linux
> [   25.998351] Copyright(c) 2003- 2015 Intel Corporation
> [   25.998689] iwlwifi :04:00.0: enabling device ( -> 0002)
[...]
> [   26.000969] iwlwifi :04:00.0: no suitable firmware found!

So WLAN does not work because the firmware is not available.

And these error messages:

> [   25.965566] i915 :00:02.0: firmware: failed to load 
> i915/skl_dmc_ver1.bin (-2)
> [   25.965571] i915 :00:02.0: Direct firmware load for 
> i915/skl_dmc_ver1.bin failed with error -2

suggest that kwin does not start because the firmware for the GPU is
not available.

I suspect that the sound chip may also require firmware loaded from
disk.

I think that with firmware-intel-sound, firmware-iwlwifi and firmware-
misc-nonfree installed (all of which are in the non-free section of the
archive), this computer will be fully functional.  Let us know whether
that helps.

Ben.

-- 
Ben Hutchings
Life is what happens to you while you're busy making other plans.
   - John Lennon

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

Processed: Re: Bug#823156: linux-image-4.5.0-0.bpo.1-amd64: Backport Kernel breaks kwin (FATAL ERROR, while trying to open display)

[Debian Bug Tracking System]

Processing control commands:

> reopen -1
Bug #823156 {Done: Ben Hutchings } 
[linux-headers-4.5.0-0.bpo.1-all-amd64] linux-headers-4.5.0-0.bpo.1-all-amd64: 
breaks kwin (abort with fatal error) on Thinkpad T560
Bug reopened
Ignoring request to alter fixed versions of bug #823156 to the same values 
previously set
> tag -1 moreinfo
Bug #823156 [linux-headers-4.5.0-0.bpo.1-all-amd64] 
linux-headers-4.5.0-0.bpo.1-all-amd64: breaks kwin (abort with fatal error) on 
Thinkpad T560
Added tag(s) moreinfo.

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

Bug#771755: marked as done (gnustep-dl2-postgresql-adaptor: unhandled symlink to directory conversion: /usr/lib/GNUstep/Frameworks/PostgreSQLEOAdaptor.framework/Resources)

[Debian Bug Tracking System]

Your message dated Mon, 02 May 2016 17:27:03 +
with message-id 
and subject line Bug#771755: fixed in gnustep-dl2 0.12.0-14
has caused the Debian Bug report #771755,
regarding gnustep-dl2-postgresql-adaptor: unhandled symlink to directory 
conversion: /usr/lib/GNUstep/Frameworks/PostgreSQLEOAdaptor.framework/Resources
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.)


-- 
771755: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=771755
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: gnustep-dl2-postgresql-adaptor
Version: 0.12.0-13
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts
Control: affects -1 + gnustep-dl2

Hi,

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

This was observed on the following upgrade paths:

  wheezy -> sid

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

For other overwritten locations anything interesting may happen.

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

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


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

3m8.5s INFO: dirname part contains a symlink:
  
/usr/lib/GNUstep/Frameworks/PostgreSQLEOAdaptor.framework/Resources/LoginPanel.bundle
 (gnustep-dl2-postgresql-adaptor) != 
/usr/lib/GNUstep/Frameworks/PostgreSQLEOAdaptor.framework/Versions/0/Resources/LoginPanel.bundle
 (?)
  
/usr/lib/GNUstep/Frameworks/PostgreSQLEOAdaptor.framework/Resources/LoginPanel.bundle/LoginPanel
 (gnustep-dl2-postgresql-adaptor) != 
/usr/lib/GNUstep/Frameworks/PostgreSQLEOAdaptor.framework/Versions/0/Resources/LoginPanel.bundle/LoginPanel
 (?)
  
/usr/lib/GNUstep/Frameworks/PostgreSQLEOAdaptor.framework/Resources/LoginPanel.bundle/Resources
 (gnustep-dl2-postgresql-adaptor) != 
/usr/lib/GNUstep/Frameworks/PostgreSQLEOAdaptor.framework/Versions/0/Resources/LoginPanel.bundle/Resources
 (?)
  
/usr/lib/GNUstep/Frameworks/PostgreSQLEOAdaptor.framework/Resources/LoginPanel.bundle/Resources/Info-gnustep.plist
 (gnustep-dl2-postgresql-adaptor) != 
/usr/lib/GNUstep/Frameworks/PostgreSQLEOAdaptor.framework/Versions/0/Resources/LoginPanel.bundle/Resources/Info-gnustep.plist
 (?)
  
/usr/lib/GNUstep/Frameworks/PostgreSQLEOAdaptor.framework/Resources/LoginPanel.bundle/Resources/postgreslogo.tif
 (gnustep-dl2-postgresql-adaptor) != 
/usr/lib/GNUstep/Frameworks/PostgreSQLEOAdaptor.framework/Versions/0/Resources/LoginPanel.bundle/Resources/postgreslogo.tif
 (?)
  
/usr/lib/GNUstep/Frameworks/PostgreSQLEOAdaptor.framework/Resources/LoginPanel.bundle/stamp.make
 (gnustep-dl2-postgresql-adaptor) != 
/usr/lib/GNUstep/Frameworks/PostgreSQLEOAdaptor.framework/Versions/0/Resources/LoginPanel.bundle/stamp.make
 (?)


cheers,

Andreas


gnustep-dl2_0.12.0-13.log.gz
Description: application/gzip
--- End Message ---
--- Begin Message ---
Source: gnustep-dl2
Source-Version: 0.12.0-14

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

Debian distribution maintenance software
pp.
Eric Heintzmann  (supplier of updated gnustep-dl2 
package)

(This message was generated automatically at their request; if you
believe that there 

Bug#754838: marked as done (grr.app: Cannot add new feeds)

[Debian Bug Tracking System]

Your message dated Mon, 02 May 2016 17:27:10 +
with message-id 
and subject line Bug#754838: fixed in grr.app 1.0-1
has caused the Debian Bug report #754838,
regarding grr.app: Cannot add new feeds
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.)


-- 
754838: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=754838
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: grr.app
Version: 0.9.0-1+b1
Severity: grave
Justification: renders package unusable

On amd64, adding a feed results in:

2014-07-14 20:30:48.495 Grr[16032] Unnamed feed finished loading
https://tracker.debian.org/pkg/grr.app/rss
2014-07-14 20:30:48.497 Grr[16032] Date=Mon, 14 Jul 2014 18:09:18
+, calc'd from Mon, 14 Jul 2014 18:09:18 +, which matched to
%a, %d %b %Y %H:%M:%S %Z (1th try)
2014-07-14 20:30:48.498 Grr[16032] Problem posting notification:
 NAME:NSRangeException REASON:Index
18446744073709551615 is out of range 0 (in 'objectAtIndex:')
INFO:{Array = (); Count = 0; Index = 4294967295; }
--- End Message ---
--- Begin Message ---
Source: grr.app
Source-Version: 1.0-1

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

Debian distribution maintenance software
pp.
Eric Heintzmann  (supplier of updated grr.app 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: Fri, 22 Apr 2016 10:33:50 +
Source: grr.app
Binary: grr.app
Architecture: source
Version: 1.0-1
Distribution: unstable
Urgency: low
Maintainer: Debian GNUstep maintainers 

Changed-By: Eric Heintzmann 
Description:
 grr.app- RSS reader for GNUstep
Closes: 754838
Changes:
 grr.app (1.0-1) unstable; urgency=low
 .
   * Team upload:
 + Add myself as new Co-Maintainer.
   * New upstream version:
 + Can now add new feeds (Closes: #754838).
   * Update debhelper, gnustep and rsskit Build-Depends (remove dpkg-dev).
   * Remove no more needed {gnustep:Depends} var in debian/control file.
   * Update Vcs-Browser and Vcs-Git fields in debian/control file
 to make lintian quiet.
   * Bump Standards-Version to 3.9.8:
 + Rewrite debian/rules file:
   - don't hardcode build flags, use dpkg-buildflags instead,
   - fix permissions of .tiff and .desktop files,
   - don't build .dbgsym package.
   * Accordind to debian policy 9.1.1, move architecture independent files
 to /usr/share/GNUstep subdirs:
 + provide a new debian install file,
 + use dh_symlink and dpkg-maintainer-script (and thus add dependency
   to dpkg (>=1.17.14) to create symlinks from old to new locations,
 + provide a new private script (debian/generate.sh) to autogenerate
  debian/install, debian/links and debian/maintscript files,
 + remove old debian/preinst script.
   * Update debian/watch file to version 4.
   * Add Upstream-Contact in debian/copyright file.
   * Provide a new debian/docs files (install README and TODO)
   * Add a Keyword entry in debian/Grr.desktop.
   * Provide a debian/source/options file with a dpkg-source argument
 to ignore Grr.xpm file generated by imagemagick.
Checksums-Sha1:
 8d8a0ed360ce246ceef127dcdc6c8243ca47b4e4 1687 grr.app_1.0-1.dsc
 780b9fd3f30e69468c1c10872faa2c9d4c002101 919124 grr.app_1.0.orig.tar.xz
 ce5d200a94740912ce6dd851e6370b1ca87e9a5a 8288 grr.app_1.0-1.debian.tar.xz
Checksums-Sha256:
 e70569dc14a7ddbe9ccf7ae4fc96f6f21581c67edd7c359d8fb7cddcae23ab91 1687 
grr.app_1.0-1.dsc
 fa055cd6c3fba4ca609b2a7ba6482880289a9eb4b1c5f732bffd2c25e0db8e88 919124 
grr.app_1.0.orig.tar.xz
 154a6ffb3619056b2fd8dbb963424b20f14e09911c0e09437935ae6ce2d00987 8288 
grr.app_1.0-1.debian.tar.xz
Files:
 a00bee0d1f7c941b6f567e3ba6b112f1 1687 gnustep optional grr.app_1.0-1.dsc
 18069c1aef83e740d5851430bf6460ca 919124 gnustep optional 
grr.app_1.0.orig.tar.xz
 407d40f61730a8da49acb474df5cf8c5 8288 gnustep optional 
grr.app_1.0-1.debian.tar.xz

-BEGIN PGP SIGNATURE-
Version: GnuPG v1

Bug#820707: marked as done (camera.app: FTBFS: DigitalCamera.m:15:21: fatal error: gphoto2.h: No such file or directory)

[Debian Bug Tracking System]

Your message dated Mon, 02 May 2016 17:23:53 +
with message-id 
and subject line Bug#820707: fixed in camera.app 0.8.0-10
has caused the Debian Bug report #820707,
regarding camera.app: FTBFS: DigitalCamera.m:15:21: fatal error: gphoto2.h: 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.)


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

Dear Maintainer,

camera.app fails to build from source in unstable/amd64:

  [..]

   debian/rules build
  dh_testdir
  gs_make
  make[1]: Entering directory 
'/home/lamby/temp/cdt.20160411154253.WuLF7ilhTH.camera.app/camera.app-0.8.0'
  This is gnustep-make 2.6.6. Type 'make print-gnustep-make-help' for help.
  Making all for app Camera...
   Creating Camera.app/
   Compiling file main.m ...
  /bin/sh: 1: gphoto2-config: not found
   Compiling file AppDelegate.m ...
  /bin/sh: 1: gphoto2-config: not found
   Compiling file CameraController.m ...
  /bin/sh: 1: gphoto2-config: not found
   Compiling file DigitalCamera.m ...
  /bin/sh: 1: gphoto2-config: not found
  DigitalCamera.m:15:21: fatal error: gphoto2.h: No such file or directory
  compilation terminated.
  /usr/share/GNUstep/Makefiles/rules.make:468: recipe for target 
'obj/Camera.obj/DigitalCamera.m.o' failed
  make[4]: *** [obj/Camera.obj/DigitalCamera.m.o] Error 1
  /usr/share/GNUstep/Makefiles/Instance/application.make:145: recipe for target 
'internal-app-run-compile-submake' failed
  make[3]: *** [internal-app-run-compile-submake] Error 2
  /usr/share/GNUstep/Makefiles/Master/rules.make:298: recipe for target 
'Camera.all.app.variables' failed
  make[2]: *** [Camera.all.app.variables] Error 2
  /usr/share/GNUstep/Makefiles/Master/application.make:38: recipe for target 
'internal-all' failed
  make[1]: *** [internal-all] Error 2
  make[1]: Leaving directory 
'/home/lamby/temp/cdt.20160411154253.WuLF7ilhTH.camera.app/camera.app-0.8.0'
  debian/rules:11: recipe for target 'build-stamp' failed
  make: *** [build-stamp] Error 2

  [..]

The full build log is attached.


Regards,

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


camera.app.0.8.0-9.1.unstable.amd64.log.txt.gz
Description: Binary data
--- End Message ---
--- Begin Message ---
Source: camera.app
Source-Version: 0.8.0-10

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

Debian distribution maintenance software
pp.
Eric Heintzmann  (supplier of updated camera.app 
package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Format: 1.8
Date: Tue, 19 Apr 2016 22:10:57 +0200
Source: camera.app
Binary: camera.app
Architecture: source
Version: 0.8.0-10
Distribution: unstable
Urgency: medium
Maintainer: Debian GNUstep maintainers 

Changed-By: Eric Heintzmann 
Description:
 camera.app - GNUstep application for digital still cameras
Closes: 618456 820707
Changes:
 camera.app (0.8.0-10) unstable; urgency=medium
 .
   * Team upload, in harmony with Gürkan,:
 - move Debian GNUstep maintainer to Maintainer field,
 - move Gürkan to Uploaders field,
 - Add myself as new Co-Maintainer.
   * Bump debhelper compat to 9.
   * Upgrade to source format 3.0 (quilt).
   * Bump Standards-Version to 3.9.8.
   * Add Vcs-Browser and Vcs-Git fields.
   * Update gnustep Build-Depends.
   * Update libgphoto2-dev Build-Depends.
   * Add ${misc:Depends} to Depends field.
   * Update Description field.
   * Reformat debian/copyright file.
   * Provide a new debian/watch file.
   * Rewrite debian/rules:
 overrides 2 GNUmakefile.preamble variables (Closes: #820707).
   * Update 

Bug#818432: [Debichem-devel] Bug#818432: espresso: FTBFS on armel and mips: hangs during the build

[Michael Banck]

Hi Aurelien,

On Mon, May 02, 2016 at 05:35:35PM +0200, Aurelien Jarno wrote:
> control: retitle -1 espresso: FTBFS on armel: hangs during the build
> 
> On 2016-03-17 00:49, Emilio Pozuelo Monfort wrote:
> > Source: espresso
> > Version: 5.1+dfsg-4
> > Severity: serious
> > 
> > Your package failed to build on armel and mips. Logs at
> > 
> > https://buildd.debian.org/status/package.php?p=espresso
> 
> The MIPS issue was due to the lack of FPU on the build daemon. It has
> now been built successfully on mips-aql-06. Retitling the bug
> accordingly.

Wow, that's great news we finally have an FPU enabled mips autobuilder.

Not just for Quantum Espresso, but for a whole bunch of other Debichem
packages as well.

Will it be possible to say "please requeue on mips-aql-06" in the
future, in case we suspect testsuite timeouts are due to lack of FPUs?


Michael

Bug#800295: gkrellm-volume: Please migrate a supported debhelper compat level

[Logan Rosen]

Package: gkrellm-volume
Version: 2.1.13-1
Followup-For: Bug #800295
User: ubuntu-de...@lists.ubuntu.com
Usertags: origin-ubuntu yakkety ubuntu-patch

Dear Maintainer,

In Ubuntu, the attached patch was applied to achieve the following:

  * debian/rules:
- Remove legacy DH_COMPAT export.
- Add recommended build-arch and build-indep targets.
- Don't allow $(MAKE) clean to ignore errors.
- Use dh_prep instead of dh_clean -k.
  * debian/compat: Specify compatibility level of 9.
  * debian/control:
- Build-depend on debhelper (>= 9).
- Depend on ${misc:Depends}.

Thanks for considering the patch.

Logan Rosen

-- 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.4.0-21-generic (SMP w/2 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) (ignored: LC_ALL 
set to en_US.utf8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
diff -u gkrellm-volume-2.1.13/debian/control gkrellm-volume-2.1.13/debian/control
--- gkrellm-volume-2.1.13/debian/control
+++ gkrellm-volume-2.1.13/debian/control
@@ -3,12 +3,12 @@
 Priority: optional
 Maintainer: Sjoerd Simons 
-Build-Depends: debhelper (>> 3.0.0), gkrellm (>= 2.0.0), libgtk2.0-dev, libasound2-dev
+Build-Depends: debhelper (>= 9), gkrellm (>= 2.0.0), libgtk2.0-dev, libasound2-dev
 Standards-Version: 3.5.7
 
 Package: gkrellm-volume
 Architecture: any
 Conflicts: gkrellm-volume2
 Replaces: gkrellm-volume2
-Depends: ${shlibs:Depends}, gkrellm (>= 2.0.0)
+Depends: ${misc:Depends}, ${shlibs:Depends}, gkrellm (>= 2.0.0)
 Description: A mixer plugin for GKrellM
  This GKrellM plugin allows you to control the mixer of your soundcard.
diff -u gkrellm-volume-2.1.13/debian/rules gkrellm-volume-2.1.13/debian/rules
--- gkrellm-volume-2.1.13/debian/rules
+++ gkrellm-volume-2.1.13/debian/rules
@@ -5,11 +5,6 @@
 # Uncomment this to turn on verbose mode.
 #export DH_VERBOSE=1
 
-# This is the debhelper compatibility version to use.
-export DH_COMPAT=3
-
-
-
 ifneq (,$(findstring debug,$(DEB_BUILD_OPTIONS)))
 	CFLAGS += -g
 endif
@@ -25,7 +20,9 @@
 	touch configure-stamp
 
 
-build: build-stamp
+build: build-arch build-indep
+build-arch: build-stamp
+build-indep: build-stamp
 
 build-stamp: configure-stamp 
 	dh_testdir
@@ -42,14 +39,14 @@
 	rm -f build-stamp configure-stamp
 
 	# Add here commands to clean up after the build process.
-	-$(MAKE) clean
+	$(MAKE) clean
 
 	dh_clean
 
 install: build
 	dh_testdir
 	dh_testroot
-	dh_clean -k
+	dh_prep
 	dh_installdirs
 
 	# Add here commands to install the package into debian/gkrellm-volume2.
only in patch2:
unchanged:
--- gkrellm-volume-2.1.13.orig/debian/compat
+++ gkrellm-volume-2.1.13/debian/compat
@@ -0,0 +1 @@
+9

Bug#800214: gmt-doc-ps: Please migrate a supported debhelper compat level

[Logan Rosen]

Package: gmt-doc-ps
Version: 3.4.4-1
Followup-For: Bug #800214
User: ubuntu-de...@lists.ubuntu.com
Usertags: origin-ubuntu yakkety ubuntu-patch

Dear Maintainer,

In Ubuntu, the attached patch was applied to achieve the following:

  * debian/rules:
- Remove legacy DH_COMPAT export.
- Replace dh_clean -k with dh_prep.
- Add recommended build-arch and build-indep targets.
  * debian/compat: Indicate compatibilty level of 9.
  * debian/control:
- Build-depend on debhelper (>= 9).
- Move debhelper build dependency to Build-Depends, as clean requires it.
- Depend on ${misc:Depends}.

Thanks for considering the patch.

Logan Rosen

-- 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.4.0-21-generic (SMP w/2 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) (ignored: LC_ALL 
set to en_US.utf8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
diff -u gmt-doc-ps-3.4.4/debian/control gmt-doc-ps-3.4.4/debian/control
--- gmt-doc-ps-3.4.4/debian/control
+++ gmt-doc-ps-3.4.4/debian/control
@@ -3,14 +3,16 @@
 Priority: extra
 Maintainer: Torsten Landschoff 
-Build-Depends-Indep: debhelper (>= 2)
+Build-Depends: debhelper (>= 9)
 Standards-Version: 3.0.1
 
 Package: gmt-doc-ps
 Architecture: all
+Depends: ${misc:Depends}
 Description: PostScript docs for the Generic Mapping Tools
  This package has the users guide of GMT in PostScript format.
 
 Package: gmt-tutorial-ps
 Architecture: all
+Depends: ${misc:Depends}
 Description: Tutorial for the Generic Mapping Tools (PostScript)
  This package contains the tutorial for GMT in PostScript format.
diff -u gmt-doc-ps-3.4.4/debian/rules gmt-doc-ps-3.4.4/debian/rules
--- gmt-doc-ps-3.4.4/debian/rules
+++ gmt-doc-ps-3.4.4/debian/rules
@@ -6,10 +6,9 @@
 #export DH_VERBOSE=1
 MANDIR:=$(shell pwd)/debian/tmp/usr/share/man/man1
 
-# This is the debhelper compatability version to use.
-export DH_COMPAT=2
-
-build:
+build: build-arch build-indep
+build-arch:
+build-indep:
 
 clean:
 	dh_testdir
@@ -22,7 +21,7 @@
 install-stamp:
 	dh_testdir
 	dh_testroot
-	dh_clean -k
+	dh_prep
 	dh_installdirs
 	touch install-stamp
 
only in patch2:
unchanged:
--- gmt-doc-ps-3.4.4.orig/debian/compat
+++ gmt-doc-ps-3.4.4/debian/compat
@@ -0,0 +1 @@
+9

Bug#800232: libcorelinux: Please migrate a supported debhelper compat level

[Logan Rosen]

Package: libcorelinux
Version: 0.4.32-7.4
Followup-For: Bug #800232
User: ubuntu-de...@lists.ubuntu.com
Usertags: origin-ubuntu yakkety ubuntu-patch

Dear Maintainer,

In Ubuntu, the attached patch was applied to achieve the following:

  * debian/rules:
- Remove legacy DH_COMPAT export.
- Use dh_prep instead of dh_clean -k.
  * debian/compat: Specify compatibility level of 9.
  * debian/control:
- Build-depend on debhelper (>= 9).
- Depend on ${misc:Depends}.

Thanks for considering the patch.

Logan Rosen

-- 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.4.0-21-generic (SMP w/2 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) (ignored: LC_ALL 
set to en_US.utf8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
diff -Nru libcorelinux-0.4.32/debian/compat libcorelinux-0.4.32/debian/compat
--- libcorelinux-0.4.32/debian/compat	1969-12-31 19:00:00.0 -0500
+++ libcorelinux-0.4.32/debian/compat	2016-03-15 00:36:09.0 -0400
@@ -0,0 +1 @@
+9
diff -Nru libcorelinux-0.4.32/debian/control libcorelinux-0.4.32/debian/control
--- libcorelinux-0.4.32/debian/control	2014-10-05 09:39:24.0 -0400
+++ libcorelinux-0.4.32/debian/control	2016-05-02 12:32:21.0 -0400
@@ -1,5 +1,5 @@
 Source: libcorelinux
-Build-Depends: debhelper, libtool, doxygen, dh-autoreconf
+Build-Depends: debhelper (>= 9), libtool, doxygen, dh-autoreconf
 Section: libs
 Priority: optional
 Maintainer: Christophe Prud'homme 
@@ -10,7 +10,7 @@
 Architecture: any
 Conflicts: libcorelinux
 Replaces: libcorelinux
-Depends: ${shlibs:Depends}
+Depends: ${misc:Depends}, ${shlibs:Depends}
 Description: Foundation Classes, Design Patterns, IPC and Threads 
  OOA and OOD for Linux dynamic libraries.
  .
@@ -34,7 +34,7 @@
 Package: libcorelinux-dev
 Section: libdevel
 Architecture: any
-Depends: libcorelinuxc2a, libc6-dev
+Depends: ${misc:Depends}, libcorelinuxc2a, libc6-dev
 Suggests: libcorelinux-doc, libcorelinux-examples
 Description: Foundation Classes, Design Patterns, IPC and Threads 
  OOA and OOD for Linux development kit. 
@@ -59,6 +59,7 @@
 Package: libcorelinux-doc
 Section: doc
 Architecture: all
+Depends: ${misc:Depends}
 Description: Foundation Classes, Design Patterns, IPC and Threads 
  OOA and OOD for Linux: reference manual.
  . 
@@ -86,7 +87,7 @@
 Package: libcorelinux-examples
 Section: libdevel
 Architecture: all
-Depends: libcorelinux-dev
+Depends: ${misc:Depends}, libcorelinux-dev
 Description: Foundation Classes, Design Patterns, IPC and Threads 
  OOA and OOD for Linux: examples. 
  .
diff -Nru libcorelinux-0.4.32/debian/rules libcorelinux-0.4.32/debian/rules
--- libcorelinux-0.4.32/debian/rules	2014-10-05 09:39:24.0 -0400
+++ libcorelinux-0.4.32/debian/rules	2016-03-15 00:47:53.0 -0400
@@ -10,9 +10,6 @@
 top_builddir=`pwd`
 top_srcdir=..
 
-# This is the debhelper compatibility version to use.
-export DH_COMPAT=3
-
 build: build-stamp
 build-stamp:
 	dh_testdir
@@ -44,7 +41,7 @@
 install: build
 	dh_testdir
 	dh_testroot
-	dh_clean -k
+	dh_prep
 	dh_installdirs
 
 	cd classic/src/classlibs && $(MAKE) install DESTDIR=$$PWD/../../../debian/tmp

Bug#823162: marked as done (pseudo: wrong update-alternatives call in postinst)

[Debian Bug Tracking System]

Your message dated Mon, 02 May 2016 16:34:20 +
with message-id 
and subject line Bug#823162: fixed in pseudo 1.7.5-5
has caused the Debian Bug report #823162,
regarding pseudo: wrong update-alternatives call in postinst
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.)


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

Dear Maintainer,

thank for your work on pseudo.

This bug is presumably related to #805937, but I'm reporting it alone as
it prevents a smooth installation of the package.

During upgrade:

  Setting up pseudo (1.7.5-4) ...
  update-alternatives: error: alternative path /usr/bin/fakeroot-pseudo
  doesn't exist
  dpkg: error processing package pseudo (--configure):
   subprocess installed post-installation script returned error exit
  status 2

This is because of the update-alternatives invocation in postinst:

  configure)
  # continue below
  update-alternatives --install /usr/bin/fakeroot fakeroot \
  /usr/bin/fakeroot-pseudo 5 \
  --slave /usr/share/man/man1/fakeroot.1.gz \
  fakeroot.1.gz /usr/share/man/man1/fakeroot-pseudo.1.gz
  ;;

The pseudo package does not contain the fakeroot-pseudo wrapper (as a
fix for #805937 ?):

  $ fgrep bin /var/lib/dpkg/info/pseudo.list 
  /usr/bin
  /usr/bin/pseudolog
  /usr/bin/pseudodb
  /usr/bin/pseudo 

Thanks,
Gian Piero.

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

Kernel: Linux 4.5.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: sysvinit (via /sbin/init)

Versions of packages pseudo depends on:
ii  libc6 2.22-7
ii  libpseudo 1.7.5-4
ii  libsqlite3-0  3.12.2-1

pseudo recommends no packages.

pseudo suggests no packages.

-- no debconf information
--- End Message ---
--- Begin Message ---
Source: pseudo
Source-Version: 1.7.5-5

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

Debian distribution maintenance software
pp.
Andrew Shadura  (supplier of updated pseudo 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, 02 May 2016 17:59:30 +0200
Source: pseudo
Binary: pseudo libpseudo
Architecture: source
Version: 1.7.5-5
Distribution: unstable
Urgency: medium
Maintainer: Andrew Shadura 
Changed-By: Andrew Shadura 
Description:
 libpseudo  - advanced tool for simulating superuser privileges
 pseudo - advanced tool for simulating superuser privileges
Closes: 823162
Changes:
 pseudo (1.7.5-5) unstable; urgency=medium
 .
   * Actually install fakeroot-pseudo wrapper (Closes: #823162).
Checksums-Sha1:
 205bd0221b7756827cdd5a48ce5f9a74a0995d2a 1497 pseudo_1.7.5-5.dsc
 fdbd19a3c8b1f70b02b69bfbef81d2276e77061f 7492 pseudo_1.7.5-5.debian.tar.xz
Checksums-Sha256:
 d32511020d13661a59a9862f6ee0082c1471f12fd81ccbc4133628b7816064fc 1497 
pseudo_1.7.5-5.dsc
 992ddb18ce5ce7aac86ec7c60ec95ca43e15737f958f3fe87bd66e2f657c0de4 7492 
pseudo_1.7.5-5.debian.tar.xz
Files:
 6c5fa1d5d01e52a066e42a9d58528c03 1497 utils optional pseudo_1.7.5-5.dsc
 f96e7d21576de43102cc856abe14c555 7492 utils optional 
pseudo_1.7.5-5.debian.tar.xz

-BEGIN PGP SIGNATURE-
Version: GnuPG v1

iQEcBAEBAgAGBQJXJ3mEAAoJEJ1bI/kYT6UUvMcH/jt9q9XN8Sxm1WrzqVlIXGBW
dDo5vnMg7UrQOULcMUbkVUh5ITTCQSJT5cOq4dGB2Py3XGTowPnaMlWiWNtTw4/P
GEFfstGoB8BdeOGh10ShNDANaHhoz3K6qGAyJWHCGxbuk94CZA51ldlsQxGAEbHf
0IojdyajRY19gZeuGmtyq4qbklr5kMxiTuaIVuKAcc2XP/FehTF5LfFL/bf5zYQY
ZeK7wc5GqFLaPNHGTRYhDgzlnAZrKoELf+DiMuKJfCqanGQLV13Qmzf7xc46jMIf
7z6F5g1NjaAXGMZcl01LHSjT6vWX7l8SjmbuCNdxC32kEjpZnYAkGvW2fvt8650=
=ZiPO
-END PGP SIGNATURE End Message ---

Bug#805926: marked as done (GNOME GMail broken on Jessie)

[Debian Bug Tracking System]

Your message dated Mon, 2 May 2016 12:03:22 -0400
with message-id 

and subject line gnome-gmail has been removed from stable and oldstable
has caused the Debian Bug report #805926,
regarding GNOME GMail broken on Jessie
to be marked as done.

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

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


-- 
805926: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=805926
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: gnome-gmail
Version: 1.8.3-1
Severity: grave


The gnome-gmail package is broken in Jessie for a couple of
reasons.First, IMAP authentication, which used for file attachments,
now requires OAuth2 authentication. OAuth2 support was first added in
1.9-1. Second, access to configuration settings is broken for a fresh
Jessie install. Version 1.8.3 still used GNOME 2's gconf for
configuration data.

Later versions of gnome-gmail, through at least 1.9.3, resolve these
problems and retain compatibility with Jessie.

-- 
"Le mieux est l'ennemi du bien" - Voltaire
--- End Message ---
--- Begin Message ---
-- 
"Le mieux est l'ennemi du bien" - Voltaire--- End Message ---

Bug#823235: marked as done (login error)

[Debian Bug Tracking System]

Your message dated Mon, 02 May 2016 17:03:51 +0100
with message-id <1462205031.2051.8.ca...@adam-barratt.org.uk>
and subject line Re: Bug#823235: login error
has caused the Debian Bug report #823235,
regarding login error
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.)


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

Hi,

I can't login to sso.debian.org using my Alioth account "onovy-guest".

Error message:
Authentication failed
Invalid authenticating information
--- End Message ---
--- Begin Message ---
On Mon, 2016-05-02 at 21:11 +0530, Hema .p wrote:
> Package: sso.debian.org
> Severity: grave
> Justification: renders package unusable
> 
> Hi,
> 
> I can't login to sso.debian.org using my Alioth account "onovy-guest".

Presumably because that's not you. Closing in favour of #823236, where
you appear to have used the correct username.

Regards,

Adam--- End Message ---

Processed: Bug#818432: espresso: FTBFS on armel and mips: hangs during the build

[Debian Bug Tracking System]

Processing control commands:

> retitle -1 espresso: FTBFS on armel: hangs during the build
Bug #818432 [src:espresso] espresso: FTBFS on armel and mips: hangs during the 
build
Changed Bug title to 'espresso: FTBFS on armel: hangs during the build' from 
'espresso: FTBFS on armel and mips: hangs during the build'.

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

Bug#823236: login error

[Hema .p]

Package: sso.debian.org
Severity: grave
Justification: renders package unusable

Hi,

I can't login to sso.debian.org using my Alioth account "hemaprathaban-guest".

Error message:
Authentication failed
Invalid authenticating information

Bug#823235: login error

[Hema .p]

Package: sso.debian.org
Severity: grave
Justification: renders package unusable

Hi,

I can't login to sso.debian.org using my Alioth account "onovy-guest".

Error message:
Authentication failed
Invalid authenticating information

Bug#818432: espresso: FTBFS on armel and mips: hangs during the build

[Aurelien Jarno]

control: retitle -1 espresso: FTBFS on armel: hangs during the build

On 2016-03-17 00:49, Emilio Pozuelo Monfort wrote:
> Source: espresso
> Version: 5.1+dfsg-4
> Severity: serious
> 
> Your package failed to build on armel and mips. Logs at
> 
> https://buildd.debian.org/status/package.php?p=espresso

The MIPS issue was due to the lack of FPU on the build daemon. It has
now been built successfully on mips-aql-06. Retitling the bug
accordingly.

Aurelien

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

Bug#805852: ipe: diff for NMU version 7.1.10-1.2

[Laurent Bigonville]

Control: tags 805852 + pending

Dear maintainer,

I've prepared an NMU for ipe (versioned as 7.1.10-1.2) and
uploaded it to DELAYED/5. Please feel free to tell me if I
should delay it longer.

Regards.
diff -Nru ipe-7.1.10/debian/changelog ipe-7.1.10/debian/changelog
--- ipe-7.1.10/debian/changelog 2016-01-22 11:09:49.0 +0100
+++ ipe-7.1.10/debian/changelog 2016-05-02 17:17:35.0 +0200
@@ -1,3 +1,13 @@
+ipe (7.1.10-1.2) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * Switch back to libjpeg-turbo instead of libjpeg8, this change is not
+documented in the debian/changelog file and goes against the CTTE decision
+stating that libjpeg-turbo should be the default implementation of libjpeg
+in Debian, see #717076 (Closes: #805852)
+
+ -- Laurent Bigonville   Mon, 02 May 2016 17:16:51 +0200
+
 ipe (7.1.10-1.1) unstable; urgency=medium
 
   * Non-maintainer upload.
diff -Nru ipe-7.1.10/debian/control ipe-7.1.10/debian/control
--- ipe-7.1.10/debian/control   2016-01-22 11:09:31.0 +0100
+++ ipe-7.1.10/debian/control   2016-05-02 15:31:39.0 +0200
@@ -13,7 +13,7 @@
   qtbase5-dev-tools,
   libfreetype6-dev (>= 2.3.9),
   libcairo2-dev,
-  libjpeg8-dev,
+  libjpeg-dev,
   libpng-dev,
   liblua5.2-dev,
   gsfonts

Processed: ipe: diff for NMU version 7.1.10-1.2

[Debian Bug Tracking System]

Processing control commands:

> tags 805852 + pending
Bug #805852 [src:ipe] depends on libjpeg8
Bug #814873 [src:ipe] src:ipe: build-depends on libjpeg8-dev
Added tag(s) pending.
Added tag(s) pending.

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

Bug#820866: r-cran-tgp: FTBFS: cmath:171:3: error: template with C linkage

[Pablo Oliveira]

Dear both,

On Wed, 20 Apr 2016 03:44:41 +0200 Andreas Beckmann  wrote:
> Hi Chris,
> [...]
> 
> I cannot reproduce this in my sid pbuilder setup. Could you check again?
> (I think gcc got updated since you filed this bug.)

I am able to reproduce the problem using cowbuilder unstable/amd64.

I will try to see if the new upstream version (2.4-14) fixes the problem
and update the package.

Pablo
make[1]: Entering directory '/build/r-cran-tgp-2.4-9/src'
gcc -std=gnu99 -I/usr/share/R/include -DNDEBUG -DRPRINT -DNDEBUG  -fpic  -g -O2 -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -g  -c all_draws.c -o all_draws.o
g++ -I/usr/share/R/include -DNDEBUG -DRPRINT -DNDEBUG  -fpic  -g -O2 -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -g  -c base.cc -o base.o
In file included from /usr/share/R/include/R.h:40:0,
 from rhelp.h:20,
 from base.h:30,
 from base.cc:25:
/usr/include/c++/5/cstdlib: In function 'long long int std::abs(long long int)':
/usr/include/c++/5/cstdlib:174:20: error: conflicting declaration of C function 'long long int std::abs(long long int)'
   abs(long long __x) { return __builtin_llabs (__x); }
^
/usr/include/c++/5/cstdlib:166:3: note: previous declaration 'long int std::abs(long int)'
   abs(long __i) { return __builtin_labs(__i); }
   ^
/usr/include/c++/5/cstdlib: In function '__int128 std::abs(__int128)':
/usr/include/c++/5/cstdlib:179:33: error: conflicting declaration of C function '__int128 std::abs(__int128)'
   abs(__GLIBCXX_TYPE_INT_N_0 __x) { return __x >= 0 ? __x : -__x; }
 ^
/usr/include/c++/5/cstdlib:174:3: note: previous declaration 'long long int std::abs(long long int)'
   abs(long long __x) { return __builtin_llabs (__x); }
   ^
/usr/include/c++/5/cstdlib:179:33: error: conflicting declaration of C function '__int128 std::abs(__int128)'
   abs(__GLIBCXX_TYPE_INT_N_0 __x) { return __x >= 0 ? __x : -__x; }
 ^
/usr/include/c++/5/cstdlib:166:3: note: previous declaration 'long int std::abs(long int)'
   abs(long __i) { return __builtin_labs(__i); }
   ^
In file included from /usr/include/c++/5/cmath:42:0,
 from /usr/share/R/include/R.h:43,
 from rhelp.h:20,
 from base.h:30,
 from base.cc:25:
/usr/include/c++/5/bits/cpp_type_traits.h: At global scope:
/usr/include/c++/5/bits/cpp_type_traits.h:72:3: error: template with C linkage
   template
   ^
/usr/include/c++/5/bits/cpp_type_traits.h:85:3: error: template with C linkage
   template
   ^
/usr/include/c++/5/bits/cpp_type_traits.h:89:3: error: template specialization with C linkage
   template<>
   ^
/usr/include/c++/5/bits/cpp_type_traits.h:95:3: error: template with C linkage
   template
   ^
/usr/include/c++/5/bits/cpp_type_traits.h:103:3: error: template with C linkage
   template
   ^
/usr/include/c++/5/bits/cpp_type_traits.h:110:3: error: template with C linkage
   template
   ^
/usr/include/c++/5/bits/cpp_type_traits.h:118:3: error: template with C linkage
   template
   ^
/usr/include/c++/5/bits/cpp_type_traits.h:125:3: error: template specialization with C linkage
   template<>
   ^
/usr/include/c++/5/bits/cpp_type_traits.h:135:3: error: template with C linkage
   template
   ^
/usr/include/c++/5/bits/cpp_type_traits.h:146:3: error: template specialization with C linkage
   template<>
   ^
/usr/include/c++/5/bits/cpp_type_traits.h:153:3: error: template specialization with C linkage
   template<>
   ^
/usr/include/c++/5/bits/cpp_type_traits.h:160:3: error: template specialization with C linkage
   template<>
   ^
/usr/include/c++/5/bits/cpp_type_traits.h:167:3: error: template specialization with C linkage
   template<>
   ^
/usr/include/c++/5/bits/cpp_type_traits.h:175:3: error: template specialization with C linkage
   template<>
   ^
/usr/include/c++/5/bits/cpp_type_traits.h:199:3: error: template specialization with C linkage
   template<>
   ^
/usr/include/c++/5/bits/cpp_type_traits.h:206:3: error: template specialization with C linkage
   template<>
   ^
/usr/include/c++/5/bits/cpp_type_traits.h:213:3: error: template specialization with C linkage
   template<>
   ^
/usr/include/c++/5/bits/cpp_type_traits.h:220:3: error: template specialization with C linkage
   template<>
   ^
/usr/include/c++/5/bits/cpp_type_traits.h:227:3: error: template specialization with C linkage
   template<>
   ^
/usr/include/c++/5/bits/cpp_type_traits.h:234:3: error: template specialization with C linkage
   template<>
   ^
/usr/include/c++/5/bits/cpp_type_traits.h:241:3: error: template specialization with C linkage
   template<>
   ^
/usr/include/c++/5/bits/cpp_type_traits.h:248:3: error: template specialization with C linkage
   template<>
   ^
/usr/include/c++/5/bits/cpp_type_traits.h:270:1: error: template 

Processed: your mail

[Debian Bug Tracking System]

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

> retitle 749531 fslview: please switch to vtk6
Bug #749531 [fslview] Switch to vtk6
Changed Bug title to 'fslview: please switch to vtk6' from 'Switch to vtk6'.
> --
Stopping processing here.

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

Bug#749531: Still not compiling with vtk6

[Mattia Rizzolo]

On Fri, Aug 21, 2015 at 02:59:31PM +0200, Michael Hanke wrote:
> Just for the record. I still fail to compile this package with vtk6.
> VTK6.1 shows the previous Qt5 linker resolution issue. VTK6.1 fails due
> to some MOC incompatibility, ala:


So, now this is the LAST package that is blocking vtk5 removal.

There are great possibilities that I'm going to ask FTP master to break
the package by forcing its vtk5, if this doesn't get fixed soon.

-- 
regards,
Mattia Rizzolo

GPG Key: 66AE 2B4A FCCF 3F52 DA18  4D18 4B04 3FCD B944 4540  .''`.
more about me:  https://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: notfound 820965 in 2:4.4.2+dfsg-2

[Debian Bug Tracking System]

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

> notfound 820965 2:4.4.2+dfsg-2
Bug #820965 [samba-common-bin] [regression]: net usersidlist: Could not malloc 
sid array Could not get the user/sid list
Ignoring request to alter found versions of bug #820965 to the same values 
previously set
> thanks
Stopping processing here.

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

Processed: notfound 822937 in 2:4.4.2+dfsg-2

[Debian Bug Tracking System]

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

> notfound 822937 2:4.4.2+dfsg-2
Bug #822937 [samba] samba: throws error on atempt to connect
Ignoring request to alter found versions of bug #822937 to the same values 
previously set
> thanks
Stopping processing here.

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

Processed: tagging 822937

[Debian Bug Tracking System]

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

> tags 822937 + upstream
Bug #822937 [samba] samba: throws error on atempt to connect
Added tag(s) upstream.
> thanks
Stopping processing here.

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

Processed: tagging 822937

[Debian Bug Tracking System]

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

> tags 822937 + jessie
Bug #822937 [samba] samba: throws error on atempt to connect
Added tag(s) jessie.
> thanks
Stopping processing here.

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

Processed: tagging 820965

[Debian Bug Tracking System]

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

> tags 820965 + wheezy
Bug #820965 [samba-common-bin] [regression]: net usersidlist: Could not malloc 
sid array Could not get the user/sid list
Added tag(s) wheezy.
> thanks
Stopping processing here.

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

Processed: notfound 821811 in 2:4.4.2+dfsg-2

[Debian Bug Tracking System]

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

> notfound 821811 2:4.4.2+dfsg-2
Bug #821811 [samba] samba: badlock patch breaks trust relationship
Ignoring request to alter found versions of bug #821811 to the same values 
previously set
> thanks
Stopping processing here.

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

Processed: tagging 821811

[Debian Bug Tracking System]

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

> tags 821811 + confirmed
Bug #821811 [samba] samba: badlock patch breaks trust relationship
Added tag(s) confirmed.
> thanks
Stopping processing here.

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

Processed: notfound 821002 in 2:4.4.2+dfsg-2

[Debian Bug Tracking System]

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

> notfound 821002 2:4.4.2+dfsg-2
Bug #821002 [samba-libs] samba: Error upgrading from deb8u1 to deb8u2. Missing 
Replaces for libsmbd-base.so.0
Ignoring request to alter found versions of bug #821002 to the same values 
previously set
> thanks
Stopping processing here.

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

Processed: tagging 821811

[Debian Bug Tracking System]

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

> tags 821811 + upstream
Bug #821811 [samba] samba: badlock patch breaks trust relationship
Added tag(s) upstream.
> thanks
Stopping processing here.

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

Processed: notfound 822937 in +2:4.4.2+dfsg-2

[Debian Bug Tracking System]

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

> notfound 822937 +2:4.4.2+dfsg-2
Bug #822937 [samba] samba: throws error on atempt to connect
There is no source info for the package 'samba' at version '+2:4.4.2+dfsg-2' 
with architecture ''
Unable to make a source version for version '+2:4.4.2+dfsg-2'
Ignoring request to alter found versions of bug #822937 to the same values 
previously set
> thanks
Stopping processing here.

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

Processed: tagging 822937

[Debian Bug Tracking System]

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

> tags 822937 + confirmed
Bug #822937 [samba] samba: throws error on atempt to connect
Added tag(s) confirmed.
> thanks
Stopping processing here.

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

Processed: tagging 821811

[Debian Bug Tracking System]

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

> tags 821811 + jessie
Bug #821811 [samba] samba: badlock patch breaks trust relationship
Added tag(s) jessie.
> thanks
Stopping processing here.

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

Processed: severity of 823214 is normal

[Debian Bug Tracking System]

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

> severity 823214 normal
Bug #823214 [xserver-xorg-input-libinput] xserver-xorg-input-libinput: 
InputClass Options ignored after upgrade
Severity set to 'normal' from 'grave'
> thanks
Stopping processing here.

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

Processed: severity of 805852 is serious

[Debian Bug Tracking System]

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

> severity 805852 serious
Bug #805852 [src:ipe] depends on libjpeg8
Bug #814873 [src:ipe] src:ipe: build-depends on libjpeg8-dev
Severity set to 'serious' from 'important'
Severity set to 'serious' from 'important'
> thanks
Stopping processing here.

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

Processed: block 823227 with 805852

[Debian Bug Tracking System]

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

> block 823227 with 805852
Bug #823227 [src:libjpeg8] libjpeg8: Please keep out of stretch
823227 was not blocked by any bugs.
823227 was not blocking any bugs.
Added blocking bug(s) of 823227: 805852 and 814873
> thanks
Stopping processing here.

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

Bug#823227: libjpeg8: Please keep out of stretch

[Laurent Bigonville]

Source: libjpeg8
Version: 8d1-2
Severity: serious

Hi,

I guess that libjpeg8 could stay out of testing or even removed from the
archive. Only one package (ipe) depends on libjpeg8, and that package
builds fine with libjpeg-turbo.

After the ctte decision[0], all the packages have transitioned to
libjpeg-turbo.

Cheers,

Laurent Bigonville

[0] https://lists.debian.org/debian-devel-announce/2014/08/msg0.html

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

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

Bug#823225: libjpeg6b: Keep libjpeg6b out of stretch

[Laurent Bigonville]

Source: libjpeg6b
Version: 1:6b2-2
Severity: serious

Hi,

I guess that libjpeg6b could stay out of testing or even removed from
the archive as nothing depends on it.

After the ctte decision[0], all the packages have transitioned to
libjpeg-turbo.

Cheers,

Laurent Bigonville

[0] https://lists.debian.org/debian-devel-announce/2014/08/msg0.html

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

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

Processed (with 1 error): forcibly merging 797291 812662

[Debian Bug Tracking System]

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

> forcemerge 797291 812662
Bug #797291 [src:debian-parl] debian-parl: FTBFS: Class 'Blend.parl.desktop.EU' 
(in ancestry of node './desktop-eu') not found under 
yaml_fs:///usr/share/boxer/jessie/classes
Unable to merge bugs because:
package of #812662 is 'debian-parl' not 'src:debian-parl'
Failed to forcibly merge 797291: Did not alter merged bugs.

> thanks
Stopping processing here.

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

Bug#823212: marked as done (apktool script fails with "can't find apktool-2.0.2+dfsg.jar")

[Debian Bug Tracking System]

Your message dated Mon, 02 May 2016 11:49:08 +
with message-id 
and subject line Bug#823212: fixed in apktool 2.1.0+dfsg-2
has caused the Debian Bug report #823212,
regarding apktool script fails with "can't find apktool-2.0.2+dfsg.jar"
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.)


-- 
823212: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=823212
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: apktool
Version: 2.1.0+dfsg-1
Severity: serious
User: de...@kali.org
Usertags: origin-kali

The script apktool in /usr/bin/ refers to the old version of the .jar 
(2.0.2+dfsg
instead of 2.1.0+dfsg)

Running the apktool script thus fails with this error:
apktool: can't find apktool-2.0.2+dfsg.jar

This bug has been reported to Kali here:
https://bugs.kali.org/view.php?id=3261

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

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

Versions of packages apktool depends on:
ii  aapt 1:6.0.1+r16-1+b1
ii  default-jre-headless [java7-runtime-headless]2:1.8-57
ii  libantlr3-runtime-java   3.5.2-4
ii  libcommons-cli-java  1.3.1-3
ii  libcommons-io-java   2.4-2
ii  libcommons-lang3-java3.4-1
ii  libguava-java19.0-1
ii  libjsr305-java   0.1~+svn49-9
ii  libsmali-java2.1.2-1
ii  libstringtemplate-java   3.2.1-2
ii  libxmlunit-java  1.6-1
ii  libxpp3-java 1.1.4c-2
ii  libyaml-snake-java   1.17-1
ii  openjdk-8-jre-headless [java7-runtime-headless]  8u91-b14-2

apktool recommends no packages.

apktool suggests no packages.

-- no debconf information
--- End Message ---
--- Begin Message ---
Source: apktool
Source-Version: 2.1.0+dfsg-2

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

Debian distribution maintenance software
pp.
Markus Koschany  (supplier of updated apktool 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, 02 May 2016 12:56:44 +0200
Source: apktool
Binary: apktool
Architecture: source all
Version: 2.1.0+dfsg-2
Distribution: unstable
Urgency: medium
Maintainer: Android Tools Maintainers 

Changed-By: Markus Koschany 
Description:
 apktool- tool for reverse engineering Android apk files
Closes: 823212
Changes:
 apktool (2.1.0+dfsg-2) unstable; urgency=medium
 .
   * Remove superfluous check for apktool.jar because it is guaranteed to be
 installed into /usr/share/apktool anyway.
 Thanks to Sophie Brun for the report. (Closes: #823212)
Checksums-Sha1:
 63aab64f13f0c7aa3cf006fa11490614307c0f55 2396 apktool_2.1.0+dfsg-2.dsc
 4e457ee54ad45f67c911dcab3110a3c7dba93414 6432 
apktool_2.1.0+dfsg-2.debian.tar.xz
 660f29d9fea9d30e0ebc6b2f432f29489ddc1f90 193674 apktool_2.1.0+dfsg-2_all.deb
Checksums-Sha256:
 e63b676bb221eabed72ba93f8491c2995f9e49831914b583dc3312bc260ffe98 2396 
apktool_2.1.0+dfsg-2.dsc
 67cc7a5d458422f2328d44d3faa29112a0473c95300d54418a5b5789be3da843 6432 
apktool_2.1.0+dfsg-2.debian.tar.xz
 b7f11d75c5a430f2a3b2fdca302881c229cf97ad1fc7aa79f407b0589ea0dec9 193674 
apktool_2.1.0+dfsg-2_all.deb
Files:
 be6855f825a71c670d2cebcba9a8ce8b 2396 devel optional apktool_2.1.0+dfsg-2.dsc
 4b654102d92739c4a16e8351a9b56b40 6432 devel optional 
apktool_2.1.0+dfsg-2.debian.tar.xz
 d4f889761176f41c4d723195e75ef468 193674 devel optional 
apktool_2.1.0+dfsg-2_all.deb

-BEGIN PGP 

Bug#823006: marked as done (license issue in hyperic-sigar)

[Debian Bug Tracking System]

Your message dated Mon, 2 May 2016 13:46:05 +0200
with message-id 
and subject line Re: Bug#823006: license issue in hyperic-sigar
has caused the Debian Bug report #823006,
regarding license issue in hyperic-sigar
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.)


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

Package: hyperic-sigar
Version: 1.6.4+dfsg-2.1
Severity: serious

This package contains  the file

bindings/java/src/org/hyperic/sigar/util/PrintfFormat.java with the
license attached.

The addition to the license:

   You acknowledge that Software is not designed, licensed or intended
   for use in the design, construction, operation or maintenance of any
   nuclear facility ("High Risk Activities").

seems to make it free-open source  (restricts the licensing to one
domain --nuclear facilities).


// Permission to use, copy, modify, and distribute this Software and its
// documentation for NON-COMMERCIAL or COMMERCIAL purposes and without fee
is
// hereby granted.
//
// This Software is provided "AS IS".  All express warranties, including any
// implied warranty of merchantability, satisfactory quality, fitness for a
// particular purpose, or non-infringement, are disclaimed, except to the
extent
// that such disclaimers are held to be legally invalid.
//
// You acknowledge that Software is not designed, licensed or intended for
use in
// the design, construction, operation or maintenance of any nuclear
facility
// ("High Risk Activities").  Sun disclaims any express or implied warranty
of
// fitness for such uses.
//




--
Daniel M. German  "That the only purpose for
   which power can be rightfully exercised
   over any member of a civilized
   community, against his will,
   is to prevent harm to others.
   His own good, either physical
   John Stuart Mill -> or moral, is not a sufficient warrant."
http://turingmachine.org/
http://silvernegative.com/
dmg (at) uvic (dot) ca
replace (at) with @ and (dot) with .

 
--- End Message ---
--- Begin Message ---
Control: tags -1 wontfix

Le 29/04/2016 à 23:26, D M German a écrit :

> This package contains  the file
> 
> bindings/java/src/org/hyperic/sigar/util/PrintfFormat.java with the
> license attached.
> 
> The addition to the license:
> 
>You acknowledge that Software is not designed, licensed or intended
>for use in the design, construction, operation or maintenance of any
>nuclear facility ("High Risk Activities").
> 
> seems to make it free-open source  (restricts the licensing to one
> domain --nuclear facilities).

Hi Daniel,

This sentence doesn't refer to a copyright license, it just states that
the code hasn't been vetted by an official organization for use in
nuclear facilities. With this statement the author waives any
responsibility, but he doesn't restrict the field of use.

This has already been discussed on debian-legal in the past, see:

https://lists.debian.org/debian-legal/2012/09/msg00034.html

Emmanuel Bourg--- End Message ---

Processed (with 1 error): merging 797291 812662

[Debian Bug Tracking System]

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

> merge 797291 812662
Bug #797291 [src:debian-parl] debian-parl: FTBFS: Class 'Blend.parl.desktop.EU' 
(in ancestry of node './desktop-eu') not found under 
yaml_fs:///usr/share/boxer/jessie/classes
Unable to merge bugs because:
package of #812662 is 'debian-parl' not 'src:debian-parl'
Failed to merge 797291: Did not alter merged bugs.

> thanks
Stopping processing here.

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

Bug#819858: marked as done (pdf-presenter-console: FTBFS: src/classes/action/movie.vala:540.24-540.39: error: use `new' operator to create new objects)

[Debian Bug Tracking System]

Your message dated Mon, 02 May 2016 10:53:21 +
with message-id 
and subject line Bug#819858: fixed in pdf-presenter-console 4.0.2-2
has caused the Debian Bug report #819858,
regarding pdf-presenter-console: FTBFS: 
src/classes/action/movie.vala:540.24-540.39: error: use `new' operator to 
create new objects
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.)


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

Dear Maintainer,

pdf-presenter-console fails to build from source in unstable/amd64:

  [..]

/home/lamby/temp/cdt.20160403081017.85gU9hQcX8/pdf-presenter-console-4.0.2/src/pdfpc.vala
  gee-0.8.vapi:267.4-267.13: warning: [Deprecated] is deprecated. Use [Version 
(deprecated = true, deprecated_since = "", replacement = "")]
  gee-0.8.vapi:662.4-662.13: warning: [Deprecated] is deprecated. Use [Version 
(deprecated = true, deprecated_since = "", replacement = "")]
  gee-0.8.vapi:664.4-664.13: warning: [Deprecated] is deprecated. Use [Version 
(deprecated = true, deprecated_since = "", replacement = "")]
  gee-0.8.vapi:672.4-672.13: warning: [Deprecated] is deprecated. Use [Version 
(deprecated = true, deprecated_since = "", replacement = "")]
  gee-0.8.vapi:674.4-674.13: warning: [Deprecated] is deprecated. Use [Version 
(deprecated = true, deprecated_since = "", replacement = "")]
  
/home/lamby/temp/cdt.20160403081017.85gU9hQcX8/pdf-presenter-console-4.0.2/src/classes/action/movie.vala:540.24-540.39:
 error: use `new' operator to create new objects
  var info = Gst.Video.Info();
 
  
/home/lamby/temp/cdt.20160403081017.85gU9hQcX8/pdf-presenter-console-4.0.2/src/classes/action/movie.vala:540.17-540.39:
 error: var declaration not allowed with non-typed initializer
  var info = Gst.Video.Info();
  ^^^
  
/home/lamby/temp/cdt.20160403081017.85gU9hQcX8/pdf-presenter-console-4.0.2/src/classes/action/movie.vala:541.13-541.26:
 error: The name `from_caps' does not exist in the context of `GLib.info'
  info.from_caps(caps);
  ^^
  
/home/lamby/temp/cdt.20160403081017.85gU9hQcX8/pdf-presenter-console-4.0.2/src/classes/action/movie.vala:542.25-542.34:
 error: The name `width' does not exist in the context of `GLib.info'
  int width = info.width, height = info.height;
  ^^
  
/home/lamby/temp/cdt.20160403081017.85gU9hQcX8/pdf-presenter-console-4.0.2/src/classes/action/movie.vala:542.46-542.56:
 error: The name `height' does not exist in the context of `GLib.info'
  int width = info.width, height = info.height;
   ^^^
  
/home/lamby/temp/cdt.20160403081017.85gU9hQcX8/pdf-presenter-console-4.0.2/src/classes/window/fullscreen.vala:66.31-66.74:
 warning: Gdk.Display.get_device_manager has been deprecated since 3.20.
  
/home/lamby/temp/cdt.20160403081017.85gU9hQcX8/pdf-presenter-console-4.0.2/src/classes/window/fullscreen.vala:66.31-66.95:
 warning: Gdk.DeviceManager.get_client_pointer has been deprecated since 3.20
  Compilation failed: 5 error(s), 7 warning(s)
  src/CMakeFiles/pdfpc.dir/build.make:96: recipe for target 
'src/interfaces/controllable.c' failed
  make[3]: *** [src/interfaces/controllable.c] Error 1
  make[3]: Leaving directory 
'/home/lamby/temp/cdt.20160403081017.85gU9hQcX8/pdf-presenter-console-4.0.2/obj-x86_64-linux-gnu'
  CMakeFiles/Makefile2:89: recipe for target 'src/CMakeFiles/pdfpc.dir/all' 
failed
  make[2]: *** [src/CMakeFiles/pdfpc.dir/all] Error 2
  make[2]: Leaving directory 
'/home/lamby/temp/cdt.20160403081017.85gU9hQcX8/pdf-presenter-console-4.0.2/obj-x86_64-linux-gnu'
  Makefile:130: recipe for target 'all' failed
  make[1]: *** [all] Error 2
  make[1]: Leaving directory 
'/home/lamby/temp/cdt.20160403081017.85gU9hQcX8/pdf-presenter-console-4.0.2/obj-x86_64-linux-gnu'
  dh_auto_build: make -j9 returned exit code 2
  debian/rules:4: recipe for target 'build' failed
  make: *** [build] Error 2

  [..]

The full build log is attached.


Regards,

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

Bug#823214: xserver-xorg-input-libinput: InputClass Options ignored after upgrade

[Sam Halliday]

Package: xserver-xorg-input-libinput
Version: 0.18.0-1
Severity: grave
Justification: renders package unusable

Dear Maintainer,

I did a routine upgrade of my apt packages, this is what I believe was the 
relevant part of the /var/log/apt/term.log

Selecting previously unselected package xserver-xorg-input-libinput.
Preparing to unpack .../xserver-xorg-input-libinput_0.18.0-1_amd64.deb ...
Unpacking xserver-xorg-input-libinput (0.18.0-1) ...
Preparing to unpack .../xserver-xorg-input-all_1%3a7.7+15_amd64.deb ...
Unpacking xserver-xorg-input-all (1:7.7+15) over (1:7.7+14) ...
Processing triggers for libc-bin (2.22-7) ...
Processing triggers for man-db (2.7.5-1) ...
Processing triggers for initramfs-tools (0.125) ...
update-initramfs: Generating /boot/initrd.img-4.5.0-1-amd64
Setting up btrfs-progs (4.4.1-1.1) ...
Setting up xserver-xorg-input-libinput (0.18.0-1) ...
Setting up xserver-xorg-input-all (1:7.7+15) ...

After the upgrade, my input device options were ignored and I was unable to use 
my device.

This is the relevant part of my /etc/x11/xorg.conf

Section "InputClass"
   Identifier  "Kensington"
   MatchProduct"Kensington Kensington Slimblade Trackball"
   Option  "InvertX" "on"
   Option  "InvertY" "on"
   Option  "ButtonMapping" "9 3 8 4 5 6 7 1 2"
EndSection

reportbug has a attached various logs, I cannot see anything relevant in there 
to suggest what could have broken this.


My workaround is to use an old mouse that I have, I'll set my trackpad aside. 
Please let me know if there is any further information that you require.

I'm going to try and track down version 1:7.7+14 of the above packages, if you 
have a link to them it would be greatly appreciated. I'll report back if 
downgrading helps.

If this was Java, Scala or lisp related, I could dig into the details and send 
you a fix, but unfortunately my understanding of the X11 / input layer (and C 
in general) is extremely poor.

Best regards,
Sam


-- Package-specific info:
X server symlink status:

lrwxrwxrwx 1 root root 13 Mar 22  2014 /etc/X11/X -> /usr/bin/Xorg
-rwxr-xr-x 1 root root 274 Apr  5 08:05 /usr/bin/Xorg

Diversions concerning libGL are in place

diversion of /usr/lib/arm-linux-gnueabihf/libGL.so.1.2.0 to 
/usr/lib/mesa-diverted/arm-linux-gnueabihf/libGL.so.1.2.0 by glx-diversions
diversion of /usr/lib/libGL.so.1 to /usr/lib/mesa-diverted/libGL.so.1 by 
glx-diversions
diversion of /usr/lib/arm-linux-gnueabihf/libGLESv2.so.2.0.0 to 
/usr/lib/mesa-diverted/arm-linux-gnueabihf/libGLESv2.so.2.0.0 by glx-diversions
diversion of /usr/lib/libGLESv2.so.2 to /usr/lib/mesa-diverted/libGLESv2.so.2 
by glx-diversions
diversion of /usr/lib/arm-linux-gnueabihf/libGL.so to 
/usr/lib/mesa-diverted/arm-linux-gnueabihf/libGL.so by glx-diversions
diversion of /usr/lib/x86_64-linux-gnu/libGLESv1_CM.so.1.1.0 to 
/usr/lib/mesa-diverted/x86_64-linux-gnu/libGLESv1_CM.so.1.1.0 by glx-diversions
diversion of /usr/lib/arm-linux-gnueabihf/libGLESv1_CM.so to 
/usr/lib/mesa-diverted/arm-linux-gnueabihf/libGLESv1_CM.so by glx-diversions
diversion of /usr/lib/i386-linux-gnu/libGLESv2.so.2 to 
/usr/lib/mesa-diverted/i386-linux-gnu/libGLESv2.so.2 by glx-diversions
diversion of /usr/lib/x86_64-linux-gnu/libGLESv2.so.2 to 
/usr/lib/mesa-diverted/x86_64-linux-gnu/libGLESv2.so.2 by glx-diversions
diversion of /usr/lib/arm-linux-gnueabihf/libGL.so.1.2 to 
/usr/lib/mesa-diverted/arm-linux-gnueabihf/libGL.so.1.2 by glx-diversions
diversion of /usr/lib/libGLESv1_CM.so.1.1.0 to 
/usr/lib/mesa-diverted/libGLESv1_CM.so.1.1.0 by glx-diversions
diversion of /usr/lib/i386-linux-gnu/libGLESv1_CM.so.1 to 
/usr/lib/mesa-diverted/i386-linux-gnu/libGLESv1_CM.so.1 by glx-diversions
diversion of /usr/lib/x86_64-linux-gnu/libGLESv1_CM.so to 
/usr/lib/mesa-diverted/x86_64-linux-gnu/libGLESv1_CM.so by glx-diversions
diversion of /usr/lib/arm-linux-gnueabihf/libGLESv1_CM.so.1.1.0 to 
/usr/lib/mesa-diverted/arm-linux-gnueabihf/libGLESv1_CM.so.1.1.0 by 
glx-diversions
diversion of /usr/lib/libGL.so.1.2.0 to /usr/lib/mesa-diverted/libGL.so.1.2.0 
by glx-diversions
diversion of /usr/lib/libGLESv2.so to /usr/lib/mesa-diverted/libGLESv2.so by 
glx-diversions
diversion of /usr/lib/libGL.so.1.2 to /usr/lib/mesa-diverted/libGL.so.1.2 by 
glx-diversions
diversion of /usr/lib/i386-linux-gnu/libGLESv1_CM.so.1.1.0 to 
/usr/lib/mesa-diverted/i386-linux-gnu/libGLESv1_CM.so.1.1.0 by glx-diversions
diversion of /usr/lib/x86_64-linux-gnu/libGL.so.1.2.0 to 
/usr/lib/mesa-diverted/x86_64-linux-gnu/libGL.so.1.2.0 by glx-diversions
diversion of /usr/lib/arm-linux-gnueabihf/libGLESv2.so to 
/usr/lib/mesa-diverted/arm-linux-gnueabihf/libGLESv2.so by glx-diversions
diversion of /usr/lib/libGL.so to /usr/lib/mesa-diverted/libGL.so by 
glx-diversions
diversion of /usr/lib/arm-linux-gnueabihf/libGLESv2.so.2 to 

Bug#823212: apktool script fails with "can't find apktool-2.0.2+dfsg.jar"

[Sophie Brun]

Package: apktool
Version: 2.1.0+dfsg-1
Severity: serious
User: de...@kali.org
Usertags: origin-kali

The script apktool in /usr/bin/ refers to the old version of the .jar 
(2.0.2+dfsg
instead of 2.1.0+dfsg)

Running the apktool script thus fails with this error:
apktool: can't find apktool-2.0.2+dfsg.jar

This bug has been reported to Kali here:
https://bugs.kali.org/view.php?id=3261

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

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

Versions of packages apktool depends on:
ii  aapt 1:6.0.1+r16-1+b1
ii  default-jre-headless [java7-runtime-headless]2:1.8-57
ii  libantlr3-runtime-java   3.5.2-4
ii  libcommons-cli-java  1.3.1-3
ii  libcommons-io-java   2.4-2
ii  libcommons-lang3-java3.4-1
ii  libguava-java19.0-1
ii  libjsr305-java   0.1~+svn49-9
ii  libsmali-java2.1.2-1
ii  libstringtemplate-java   3.2.1-2
ii  libxmlunit-java  1.6-1
ii  libxpp3-java 1.1.4c-2
ii  libyaml-snake-java   1.17-1
ii  openjdk-8-jre-headless [java7-runtime-headless]  8u91-b14-2

apktool recommends no packages.

apktool suggests no packages.

-- no debconf information

Bug#823211: python-pygccxml-doc: fails to upgrade from 'jessie' - trying to overwrite /usr/share/doc-base/pygccxml-apidocs

[Andreas Beckmann]

Package: python-pygccxml-doc
Version: 1.7.4-2
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

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

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

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

  Selecting previously unselected package python-pygccxml-doc.
  Preparing to unpack .../python-pygccxml-doc_1.7.4-2_all.deb ...
  Unpacking python-pygccxml-doc (1.7.4-2) ...
  dpkg: error processing archive 
/var/cache/apt/archives/python-pygccxml-doc_1.7.4-2_all.deb (--unpack):
   trying to overwrite '/usr/share/doc-base/pygccxml-apidocs', which is also in 
package python-pygccxml 1.0.0-4
  dpkg-deb: error: subprocess paste was killed by signal (Broken pipe)
  Errors were encountered while processing:
   /var/cache/apt/archives/python-pygccxml-doc_1.7.4-2_all.deb


cheers,

Andreas


python-pygccxml=1.0.0-4_python-pygccxml-doc=1.7.4-2.log.gz
Description: application/gzip

Processed: user debian...@lists.debian.org, usertagging 823162, found 816135 in 3.4.4-3, affects 822671

[Debian Bug Tracking System]

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

> user debian...@lists.debian.org
Setting user to debian...@lists.debian.org (was a...@debian.org).
> usertags 823162 piuparts
There were no usertags set.
Usertags are now: piuparts.
> found 816135 3.4.4-3
Bug #816135 [idle-python3.4] idle-python3.4: uninstallable since python3-tk 
stopped providing python3.4-tk
Marked as found in versions python3.4/3.4.4-3.
> affects 822671 + plymouth
Bug #822671 [initramfs-tools] initramfs-tools: preserves unmodified 
/etc/initramfs-tools/initramfs.conf on upgrades from jessie
Added indication that 822671 affects plymouth
> thanks
Stopping processing here.

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

Processed: merging 822369 822470

[Debian Bug Tracking System]

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

> merge 822369 822470
Bug #822369 [xfsprogs] xfsprogs: FTBFS: error: redefinition of 'struct fsxattr'
Bug #822470 [xfsprogs] qemu: FTBFS: error: redefinition of 'struct fsxattr'
Bug #822470 [xfsprogs] qemu: FTBFS: error: redefinition of 'struct fsxattr'
Merged 822369 822470
> thanks
Stopping processing here.

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

Bug#818072: warzone2100: FTBFS in stretch (new flex)

[Graham Inggs]

On 1 May 2016 at 19:10, Markus Koschany  wrote:
> that was really bad timing. I had uploaded a new revision with a fix one
> hour before you sent your e-mail. Nevertheless thanks for the patch!

Oh well, no harm done.  Thanks for taking care of warzone2100.

Processed: Close bug #800767

[Debian Bug Tracking System]

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

> package biomaj
Limiting to bugs with field 'package' containing at least one of 'biomaj'
Limit currently set to 'package':'biomaj'

> fixed 800767 1.2.3-7
Bug #800767 [biomaj] biomaj: depends on obsolete libcommons-net2-java library
Marked as fixed in versions biomaj/1.2.3-7.
> thanks
Stopping processing here.

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