Processed: Re: clutter-1.0: non-free file (CC-BY-NC-SA-2.5)

[Debian Bug Tracking System]

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

> tags 821095 + pending
Bug #821095 [src:clutter-1.0] clutter-1.0: non-free file (CC-BY-NC-SA-2.5)
Added tag(s) pending.
>
End of message, stopping processing here.

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

Processed: Re: Bug#819546: vsftpd no longer starts with systemd because of listen_ipv6=NO from Bug: #803999

[Debian Bug Tracking System]

Processing control commands:

> severity -1 grave
Bug #819546 [vsftpd] vsftpd no longer starts with systemd because of 
listen_ipv6=NO from Bug: #803999
Severity set to 'grave' from 'normal'

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

Processed: severity of 818812 is serious

[Debian Bug Tracking System]

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

> severity 818812 serious
Bug #818812 [madness] madness: FTBFS with libc 2.23: 'isnan' was not declared 
in this scope
Severity set to 'serious' from 'important'
> thanks
Stopping processing here.

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

Bug#829657: python-bioblend-doc: Typo in dependency

[Jeremy Bicha]

Package: python-bioblend-doc
Version: 0.7.0-1
Severity: serious

python-bioblend-doc should depend on
-libjs-query
+libjs-jquery

Currently, python-bioblend-doc is uninstallable.

Also, please point both your Vcs-Git and Vcs-Browser to:
https://anonscm.debian.org/git/python-modules/packages/python-bioblend.git

(The lintian tag vcs-field-uses-insecure-uri recommends using https://
instead of git:// )

Thanks,
Jeremy Bicha

Bug#829656: mkdocs: Missing dependencies

[Jeremy Bicha]

Package: mkdocs
Version: 0.15.3-3
Severity: serious
Justification: not binNMU safe

When python-mkdocs is built in a clean chroot (like on Ubuntu or in
Debian's reproducible builds), it is missing some dependencies
(mkdocs-bootstrap and mkdocs-bootswatch) that were somehow present in
the package that was uploaded to Debian.

https://launchpad.net/ubuntu/+source/python-mkdocs/0.15.3-3/+build/9729927

https://tests.reproducible-builds.org/debian/rbuild/unstable/amd64/python-mkdocs_0.15.3-3.rbuild.log

https://packages.debian.org/unstable/mkdocs

The logs have these warnings:
I: dh_python3 pydist:184: Cannot find package that provides
mkdocs_bootstrap. Please add package that provides it to Build-Depends
or add "mkdocs_bootstrap python3-mkdocs-bootstrap" line to
debian/py3dist-overrides or add proper  dependency to Depends by hand
and ignore this info.
I: dh_python3 pydist:184: Cannot find package that provides
mkdocs_bootswatch. Please add package that provides it to
Build-Depends or add "mkdocs_bootswatch python3-mkdocs-bootswatch"
line to debian/py3dist-overrides or add proper  dependency to Depends
by hand and ignore this info.

Please add the appropriate lines to debian/py3dist-overrides.

And please consider switching to source-only uploads:

https://wiki.debian.org/SourceOnlyUpload

Thanks,
Jeremy Bicha

Bug#811831: projectm: FTBFS with GCC 6: no match for

[Matt Beary]

an upstream patch is available which addresses GCC-6 compatibility:

https://sourceforge.net/p/projectm/code/ci/92226e25192a69839b9ae3b66ea7173732c639b3/

Bug#820026: icedove crashes suddenly

[jathan]

Am 21.06.2016 um 07:49 schrieb Laurent:
> I have a problem those days with Icedove : when running (writting an 
> email, searching in a list or any simple operation), it crashes. This >
never happened before.
>

I do have the same issue. It have been happening since the beginning
when I start to use Debian Jessie, but crashes were less common. Now
with the latest icedove version 1:45.1.0-1~deb8u1, the crashes occurs
during all the time that I am using Icedove. For me it happens randomly
when clicking on any mail, about 5-10 times everyday. After
starting icedove again, there's no problem when opening the mail clicked
on before.

The installed addons are enigmail and iceowl from jessie repo. In all
the computers that I use Debian and Icedove happend the same. This the
terminal message when Icedove crash:

@debian:~$ icedove
[calBackendLoader] Using libical backend at
/usr/lib/icedove/extensions/{e2fda1a4-762b-4020-b5ad-a41df1933103}/components/libical-manifest
enigmail.js: Registered components
mimeVerify.jsm: module initialized
Violación de segmento
@debian:~$

Best regards,
Jathan

-- 
Por favor evita enviarme adjuntos en formato de word o powerpoint, si
quieres saber porque lee esto:
http://www.gnu.org/philosophy/no-word-attachments.es.html
¡Cámbiate a GNU/Linux! http://getgnulinux.org/es



signature.asc
Description: OpenPGP digital signature

Bug#820026: icedove crashes suddenly

[jathan]

Am 21.06.2016 um 07:49 schrieb Laurent:
> I have a problem those days with Icedove : when running (writting an >
email, searching in a list or any simple operation), it crashes. This >
never happened before.
>

I do have the same issue. It have been happening since the beginning
when I start to use Debian Jessie, but crashes were less common. Now
with the latest icedove version 1:45.1.0-1~deb8u1, the crashes occurs
during all the time that I am using Icedove. For me it happens randomly
when clicking on any mail, about 5-10 times everyday. After
starting icedove again, there's no problem when opening the mail clicked
on before.

The installed addons are enigmail and iceowl from jessie repo. In all
the computers that I use Debian and Icedove happend the same. This the
terminal message when Icedove crash:

@debian:~$ icedove
[calBackendLoader] Using libical backend at
/usr/lib/icedove/extensions/{e2fda1a4-762b-4020-b5ad-a41df1933103}/components/libical-manifest
enigmail.js: Registered components
mimeVerify.jsm: module initialized
Violación de segmento
@debian:~$

Best regards,
Jathan

-- 
Por favor evita enviarme adjuntos en formato de word o powerpoint, si
quieres saber porque lee esto:
http://www.gnu.org/philosophy/no-word-attachments.es.html
¡Cámbiate a GNU/Linux! http://getgnulinux.org/es

Bug#829642: pulseaudio 9 breaks SPDIF/iec958 and Intel HDMI audio on ASUS B85-Pro motherboard

[Felipe Sateler]

Control: tags -1 moreinfo

On 4 July 2016 at 19:21, Adam Warner  wrote:
>
> Package: pulseaudio
> Version: 9.0-1
> Severity: serious
> Justification: keep out of testing. Workaround is to downgrade to the
> version in testing
>
>
> Installation is x86-64 stock sid/unstable as of an hour ago
> (with libwebrtc-audio-processing-0 held after downgrade to
> pulseaudio 8.0-2+b2)
>
> Before pulseaudio upgrade:
>
> $ pacmd list-sinks | grep name:
> name: 
> name: 



> After reboot:
>  pacmd list-sinks | grep name:
> name: 


Could you please attach a verbose log of both versions of pulseaudio?
https://wiki.ubuntu.com/PulseAudio/Log

-- 

Saludos,
Felipe Sateler

Processed: Re: Bug#829642: pulseaudio 9 breaks SPDIF/iec958 and Intel HDMI audio on ASUS B85-Pro motherboard

[Debian Bug Tracking System]

Processing control commands:

> tags -1 moreinfo
Bug #829642 [pulseaudio] pulseaudio 9 breaks SPDIF/iec958 and Intel HDMI audio 
on ASUS B85-Pro motherboard
Added tag(s) moreinfo.

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

Bug#825926: marked as done (python-pgmagick: FTBFS: ./src/_Image.cpp:529:56: error: no matching function for call to ‘boost::python::class_::def(const char [12],

[Debian Bug Tracking System]

Your message dated Tue, 05 Jul 2016 00:04:26 +
with message-id 
and subject line Bug#825926: fixed in python-pgmagick 0.6.2-1
has caused the Debian Bug report #825926,
regarding python-pgmagick: FTBFS: ./src/_Image.cpp:529:56: error: no matching 
function for call to ‘boost::python::class_::def(const char 
[12], )’
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.)


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

Dear Maintainer,

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

  [..]

  Setting up liblzma-dev:amd64 (5.1.1alpha+20120614-2.1) ...
  Setting up libtiffxx5:amd64 (4.0.6-1) ...
  Setting up libtiff5-dev:amd64 (4.0.6-1) ...
  Setting up libexif12:amd64 (0.6.21-2) ...
  Setting up libjs-jquery (1.12.3-1) ...
  Setting up libexif-dev (0.6.21-2) ...
  Setting up libbz2-dev:amd64 (1.0.6-8) ...
  Setting up libltdl7:amd64 (2.4.6-0.1) ...
  Setting up libltdl-dev:amd64 (2.4.6-0.1) ...
  Setting up libgraphicsmagick1-dev (1.3.24-1) ...
  Setting up libgraphicsmagick++1-dev (1.3.24-1) ...
  Setting up libboost1.58-dev:amd64 (1.58.0+dfsg-5+b1) ...
  Setting up libboost-python1.58.0 (1.58.0+dfsg-5+b1) ...
  Setting up libboost-python1.58-dev (1.58.0+dfsg-5+b1) ...
  Setting up libboost-python-dev (1.58.0.1) ...
  Setting up python-pgmagick-build-deps (0.6-1) ...
  Processing triggers for libc-bin (2.22-9) ...
  Processing triggers for systemd (230-1) ...
  
  
**
  ** Environment
  **
  
**
  
  
PATH=/home/lamby/git/projects/dotfiles/dotfiles/..//bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin
  HOSTNAME=31a16acb692a
  TERM=xterm
  EVAL=db python-pgmagick; ret="${?}"; if [ "${ret}" = 29 ]; then ft . 300; 
echo python-pgmagick >> /tmp/tmp.Fy5wFBu5Ks; fi; echo python-pgmagick >> 
/home/lamby/unfiled/get-ftbfs-logs/.unreproducible; exit ${ret}
  PAGER=more
  DISPLAY=:0
  DOCKER_IMAGE=lamby-debian-sid
  DEB_BUILD_OPTIONS=parallel=9
  PIP_DOWNLOAD_CACHE=/home/lamby/.cache/pip
  HOME=/home/lamby
  LOGNAME=lamby
  SHLVL=1
  
PWD=/home/lamby/temp/cdt.20160531140342.uhIR1MuCRv.python-pgmagick/python-pgmagick-0.6
  OLDPWD=/home/lamby/temp/cdt.20160531140342.uhIR1MuCRv.python-pgmagick
  GPG_TTY=/dev/console
  QUILT_PATCHES=debian/patches
  QUILT_NO_DIFF_INDEX=1
  QUILT_REFRESH_ARGS=-p ab --no-timestamps --no-index
  DEBEMAIL=la...@debian.org
  DEBFULLNAME=Chris Lamb
  EDITOR=vim
  LESS=-cgiFx4M
  BLASTER=A220 I5 D1 H5 P330 T6
  _=/usr/bin/env
  
  
**
  ** Building python-pgmagick 0.6-1 on amd64
  **
  
**
  
   dpkg-buildpackage -rfakeroot -D -us -uc -b
  dpkg-buildpackage: info: source package python-pgmagick
  dpkg-buildpackage: info: source version 0.6-1
  dpkg-buildpackage: info: source distribution unstable
  dpkg-buildpackage: info: source changed by TANIGUCHI Takaki 

   dpkg-source --before-build python-pgmagick-0.6
  dpkg-buildpackage: info: host architecture amd64
   fakeroot debian/rules clean
  dh clean --buildsystem=pybuild --with python2,python3
 dh_testdir -O--buildsystem=pybuild
 dh_auto_clean -O--buildsystem=pybuild
  I: pybuild base:184: python2.7 setup.py clean 
  include header path: /usr/include/GraphicsMagick/
  boost lib: boost_python
  library path: /usr/lib/libGraphicsMagick++
  GraphicsMagick version: 1.3.24
  running clean
  removing 
'/home/lamby/temp/cdt.20160531140342.uhIR1MuCRv.python-pgmagick/python-pgmagick-0.6/.pybuild/pythonX.Y_2.7/build'
 (and everything under it)
  'build/bdist.linux-x86_64' does not exist -- can't clean it
  'build/scripts-2.7' does not exist -- can't clean it
  I: pybuild base:184: python3.5 setup.py clean 
  include header path: /usr/include/GraphicsMagick/
  boost lib: boost_python-py35
  library path: /usr/lib/libGraphicsMagick++
  GraphicsMagick version: 1.3.24
  running clean
  removing 

Bug#824944: Update on #824944

[Jason Pleau]

Hey,

On 07/04/2016 06:43 PM, Julian Wollrath wrote:
> Hi,
> 
> thanks for your interest. I modified it myself to incorporate (and
> hopefully support) the flags of discount 2.1.8, therefore the version
> change, since upstream seems inactive. I am in contact with Enrico
> Tassi, who sponsored previous uploads to get it uploaded.
> 

Awesome, thanks for the swift reply and explanation !

> Cheers,
> Julian
> 

Cheers

-- 
Jason Pleau

Bug#829642: pulseaudio 9 breaks SPDIF/iec958 and Intel HDMI audio on ASUS B85-Pro motherboard

[Adam Warner]

Package: pulseaudio
Version: 9.0-1
Severity: serious
Justification: keep out of testing. Workaround is to downgrade to the
version in testing


Installation is x86-64 stock sid/unstable as of an hour ago
(with libwebrtc-audio-processing-0 held after downgrade to
pulseaudio 8.0-2+b2)

Before pulseaudio upgrade:

$ pacmd list-sinks | grep name:
name: 
name: 


consisting of:
device.product.name = "8 Series/C220 Series Chipset High Definition
Audio Controller"
device.description = "Built-in Audio Digital Stereo (IEC958)"
alsa.mixer_name = "Realtek ALC1150"
alsa.components = "HDA:10ec0900,10438610,0011"
module-udev-detect.discovered = "1"

and:
device.product.name = "Xeon E3-1200 v3/4th Gen Core Processor HD Audio
Controller"
device.description = "Built-in Audio Digital Stereo (HDMI)"
alsa.mixer_name = "Intel Haswell HDMI"
alsa.components = "HDA:80862807,80860101,0010"
module-udev-detect.discovered = "1"



Upgrade to pulseaudio 9.0-1:

~# apt-get install libpulse-mainloop-glib0 libpulse0 libpulsedsp
pulseaudio pulseaudio-utils
Reading package lists... Done
Building dependency tree   
Reading state information... Done
The following package was automatically installed and is no longer
required:
  libwebrtc-audio-processing-0
Use 'apt autoremove' to remove it.
Suggested packages:
  pavumeter paman paprefs
Recommended packages:
  pulseaudio-module-x11 rtkit pulseaudio-module-udev
The following packages will be upgraded:
  libpulse-mainloop-glib0 libpulse0 libpulsedsp pulseaudio pulseaudio-
utils
5 upgraded, 0 newly installed, 0 to remove and 1 not upgraded.
Need to get 0 B/1,467 kB of archives.
After this operation, 36.9 kB of additional disk space will be used.
Retrieving bug reports... Done
Parsing Found/Fixed information... Done
Reading changelogs... Done
(Reading database ... 359743 files and directories currently
installed.)
Preparing to unpack .../libpulsedsp_9.0-1_amd64.deb ...
Unpacking libpulsedsp:amd64 (9.0-1) over (8.0-2+b2) ...
Preparing to unpack .../pulseaudio-utils_9.0-1_amd64.deb ...
Unpacking pulseaudio-utils (9.0-1) over (8.0-2+b2) ...
Preparing to unpack .../pulseaudio_9.0-1_amd64.deb ...
Unpacking pulseaudio (9.0-1) over (8.0-2+b2) ...
Preparing to unpack .../libpulse-mainloop-glib0_9.0-1_amd64.deb ...
Unpacking libpulse-mainloop-glib0:amd64 (9.0-1) over (8.0-2+b2) ...
Preparing to unpack .../libpulse0_9.0-1_amd64.deb ...
Unpacking libpulse0:amd64 (9.0-1) over (8.0-2+b2) ...
Processing triggers for man-db (2.7.5-1) ...
Processing triggers for dbus (1.10.8-1) ...
Processing triggers for libc-bin (2.23-1) ...
Setting up libpulse0:amd64 (9.0-1) ...
Setting up libpulsedsp:amd64 (9.0-1) ...
Setting up pulseaudio-utils (9.0-1) ...
Setting up pulseaudio (9.0-1) ...
Installing new version of config file /etc/pulse/daemon.conf ...
Installing new version of config file /etc/pulse/default.pa ...
Setting up libpulse-mainloop-glib0:amd64 (9.0-1) ...
Processing triggers for libc-bin (2.23-1) ...


After reboot:
 pacmd list-sinks | grep name:
name: 

consisting of:
device.product.name = "8 Series/C220 Series Chipset High Definition
Audio Controller"
device.description = "Built-in Audio Analog Stereo"
alsa.mixer_name = "Realtek ALC1150"
alsa.components = "HDA:10ec0900,10438610,0011"


Downgrade to pulseaudio 8.0-2+b2:
~# apt-get install libpulse-mainloop-glib0/testing libpulse0/testing
libpulsedsp/testing pulseaudio/testing pulseaudio-utils/testing
Reading package lists... Done
Building dependency tree   
Reading state information... Done
Selected version '8.0-2+b2' (Debian:testing [amd64]) for 'libpulse-
mainloop-glib0'
Selected version '8.0-2+b2' (Debian:testing [amd64]) for 'libpulse0'
Selected version '8.0-2+b2' (Debian:testing [amd64]) for 'libpulsedsp'
Selected version '8.0-2+b2' (Debian:testing [amd64]) for 'pulseaudio'
Selected version '8.0-2+b2' (Debian:testing [amd64]) for 'pulseaudio-
utils'
The following package was automatically installed and is no longer
required:
  libwebrtc-audio-processing1
Use 'apt autoremove' to remove it.
Suggested packages:
  pavumeter paman paprefs
Recommended packages:
  pulseaudio-module-x11 rtkit
The following packages will be DOWNGRADED:
  libpulse-mainloop-glib0 libpulse0 libpulsedsp pulseaudio pulseaudio-
utils
0 upgraded, 0 newly installed, 5 downgraded, 0 to remove and 1 not
upgraded.
Need to get 0 B/1,455 kB of archives.
After this operation, 36.9 kB disk space will be freed.
Do you want to continue? [Y/n] 
dpkg: warning: downgrading libpulsedsp:amd64 from 9.0-1 to 8.0-2+b2
(Reading database ... 359736 files and directories currently
installed.)
Preparing to unpack .../libpulsedsp_8.0-2+b2_amd64.deb ...
Unpacking libpulsedsp:amd64 (8.0-2+b2) over (9.0-1) ...
dpkg: warning: downgrading pulseaudio-utils from 9.0-1 to 8.0-2+b2
Preparing to unpack .../pulseaudio-utils_8.0-2+b2_amd64.deb ...
Unpacking pulseaudio-utils (8.0-2+b2) over (9.0-1) ...
dpkg: warning: downgrading pulseaudio from 9.0-1 to 8.0-2+b2
Preparing to 

Bug#829640: netfilter-persistent loads firewall rules too late

[Patrick Schleizer]

Package: netfilter-persistent
Severity: grave
X-Debbugs-CC: whonix-de...@whonix.org
Tags: security

Dear maintainer,

there is a security issue with the netfilter-persistent systemd service. [1]

netfilter-persistent orders itself before the wrong target. Should be
'Before=network-pre.target'.

The systemd manual is quite clear on network.target and
network-pre.target. [2]

Credits for finding this bug go to rustybird. [3] [4] (I am only
seconding and reporting it.)

(Using severity grave as this could pose a security risk, i.e. the
firewall getting up too late.)

Cheers,
Patrick

[1]
https://anonscm.debian.org/cgit/collab-maint/iptables-persistent.git/tree/systemd/netfilter-persistent.service
[2] https://www.freedesktop.org/software/systemd/man/systemd.special.html
[3] https://github.com/rustybird
[4] https://github.com/rustybird/corridor/issues/8#issuecomment-230266161

Bug#820149: marked as done (docker.io: FTBFS in stretch)

[Debian Bug Tracking System]

Your message dated Mon, 04 Jul 2016 23:00:23 +
with message-id 
and subject line Bug#820149: fixed in docker.io 1.11.2~ds1-1
has caused the Debian Bug report #820149,
regarding docker.io: FTBFS in 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.)


-- 
820149: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=820149
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:docker.io
Version: 1.8.3~ds1-2
Severity: serious

Dear maintainers: As you righly pointed out in Bug#818122, docker.io
still FTBFS in stretch (but for other reasons), so I'm filing a new bug.

-
# WARNING! I don't seem to be running in the Docker container.
# The result of this command might be an incorrect build, and will not be
#   officially supported.
#
# Try this instead: make all
#

---> Making bundle: dynbinary (in bundles/1.8.3/dynbinary)
# github.com/docker/docker/daemon/execdriver/native/template
.gopath/src/github.com/docker/docker/daemon/execdriver/native/template/default_template.go:40:
 unknown configs.Cgroup fie
ld 'AllowAllDevices' in struct literal
.gopath/src/github.com/docker/docker/daemon/execdriver/native/template/default_template.go:41:
 unknown configs.Cgroup fie
ld 'MemorySwappiness' in struct literal
debian/rules:59: recipe for target 'override_dh_auto_build' failed
-

I usually check "dpkg-buildpackage -A" only, but you can get full
build logs here:

https://reproducible.debian.net/rb-pkg/unstable/amd64/docker.io.html

Thanks.
--- End Message ---
--- Begin Message ---
Source: docker.io
Source-Version: 1.11.2~ds1-1

We believe that the bug you reported is fixed in the latest version of
docker.io, 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.
Tianon Gravi  (supplier of updated docker.io 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, 04 Jul 2016 09:59:44 -0700
Source: docker.io
Binary: docker.io vim-syntax-docker golang-github-docker-docker-dev 
golang-docker-dev docker-doc
Architecture: source all amd64
Version: 1.11.2~ds1-1
Distribution: unstable
Urgency: medium
Maintainer: Paul Tagliamonte 
Changed-By: Tianon Gravi 
Description:
 docker-doc - Linux container runtime -- documentation
 docker.io  - Linux container runtime
 golang-docker-dev - Transitional package for golang-github-docker-docker-dev
 golang-github-docker-docker-dev - Externally reusable Go packages included 
with Docker
 vim-syntax-docker - Docker container engine - Vim highlighting syntax files
Closes: 785093 799386 805725 806887 812838 816844 820149 822628 824833
Changes:
 docker.io (1.11.2~ds1-1) unstable; urgency=medium
 .
   * Update to 1.11.2 upstream release
 (Closes: #806887, #820149, #822628, #812838)
   * Add NEWS file describing the AUFS issue and the unfortunate possible
 "solutions" (Closes: #799386, #805725)
   * Add "/etc/docker" to the directories explicitly installed by the package
 to help combat issues like #806261
   * Update "Homepage" to "dockerproject.org" (versus ".com" which now 
redirects)
   * Update "Vcs-Browser" to use https
   * Shrink the Ubuntu delta by pulling in many of the changes
   * Replace "btrfs-tools" relations with "btrfs-progs" (Closes: #824833)
   * Adjust "repack.sh" to allow keeping minor bits of vendor/
   * Fix bad URL in README (Closes: #816844); thanks Clint!
   * Move documentation to dedicated "docker-doc" package
   * Refresh patches, add minor patch to get unit tests running
   * Use gccgo on non-golang architectures (Closes: #785093)
   * Use "dh-golang" to calculate "Built-Using" more accurately
   * Add simple "basic-smoke" DEP8 test
Checksums-Sha1:
 d25f1e48d956770c853eb4059357108449e0b418 6185 docker.io_1.11.2~ds1-1.dsc
 47727d5af2c7ef60731166b5d6b8e5fb24d13f80 7544603 
docker.io_1.11.2~ds1.orig.tar.gz
 81415eee12877d7ac5378a23c3a8455fc81e75ef 31496 

Bug#824944: Update on #824944

[Julian Wollrath]

Hi,

thanks for your interest. I modified it myself to incorporate (and
hopefully support) the flags of discount 2.1.8, therefore the version
change, since upstream seems inactive. I am in contact with Enrico
Tassi, who sponsored previous uploads to get it uploaded.

Cheers,
Julian

Bug#828979: marked as done (pyosmium: FTBFS in testing (FAIL: test_location_tuple))

[Debian Bug Tracking System]

Your message dated Mon, 04 Jul 2016 22:28:00 +
with message-id 
and subject line Bug#828979: fixed in pyosmium 2.7.1-3
has caused the Debian Bug report #828979,
regarding pyosmium: FTBFS in testing (FAIL: test_location_tuple)
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.)


-- 
828979: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=828979
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:pyosmium
Version: 2.7.1-2
User: reproducible-bui...@lists.alioth.debian.org
Usertags: ftbfs
Severity: serious

Dear maintainer:

This package currently fails to build in stretch:


[...]
FAIL: test_location_tuple (test_writer.TestWriteNode)
--
Traceback (most recent call last):
  File "/build/pyosmium-2.7.1/test/test_writer.py", line 112, in 
test_location_tuple
w.add_node(O(location=(1, 2)))
  File "/usr/lib/python2.7/contextlib.py", line 24, in __exit__
self.gen.next()
  File "/build/pyosmium-2.7.1/test/test_writer.py", line 35, in WriteExpect
assert_equals(line, expected)
AssertionError: 'n0 v0 dV c0 t i0 u T x1 y2' != 'n0 v0 dV c0 t i0 u T 
x1.000 y2.000'


A full build log is available here:

https://tests.reproducible-builds.org/debian/rbuild/testing/amd64/pyosmium_2.7.1-2.rbuild.log

Thanks.
--- End Message ---
--- Begin Message ---
Source: pyosmium
Source-Version: 2.7.1-3

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

Debian distribution maintenance software
pp.
Bas Couwenberg  (supplier of updated pyosmium 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, 04 Jul 2016 23:42:48 +0200
Source: pyosmium
Binary: python-pyosmium python3-pyosmium pyosmium-doc
Architecture: source all amd64
Version: 2.7.1-3
Distribution: unstable
Urgency: medium
Maintainer: Debian GIS Project 
Changed-By: Bas Couwenberg 
Description:
 pyosmium-doc - Osmium library bindings for Python - Documentation
 python-pyosmium - Osmium library bindings for Python
 python3-pyosmium - Osmium library bindings for Python 3
Closes: 828979
Changes:
 pyosmium (2.7.1-3) unstable; urgency=medium
 .
   * Add patch to fix test_location_tuple failure.
 (closes: #828979)
Checksums-Sha1:
 9d23277411c525cc5b93a5de928d65aeaa3a3ef2 2303 pyosmium_2.7.1-3.dsc
 be708d03777c3bd8cf72744464df6eb629fd5d84 4932 pyosmium_2.7.1-3.debian.tar.xz
 0538d7e7b3a4a6c12fb165b76b6a1f7bd5aaa3b5 42062 pyosmium-doc_2.7.1-3_all.deb
 756fe86e7d61701f32905d01f645fb84c96dfa78 5910424 
python-pyosmium-dbgsym_2.7.1-3_amd64.deb
 2a3fa237f0795cc69d7d926337fcfb8e35cf 452558 
python-pyosmium_2.7.1-3_amd64.deb
 7b1ee396163f76542fa71baf1be1b6247950c87a 5913838 
python3-pyosmium-dbgsym_2.7.1-3_amd64.deb
 94e01e6ed614a5f0d047218453a2d251ac623e96 452216 
python3-pyosmium_2.7.1-3_amd64.deb
Checksums-Sha256:
 8f25e034a613966413a712a75675630baaae79a20dc1ec66c3a27ad6cce62687 2303 
pyosmium_2.7.1-3.dsc
 76fe7f2c0f63ff9149ed139562bdc353e9f14c771def87763a8f042dfc2d024c 4932 
pyosmium_2.7.1-3.debian.tar.xz
 c8422a2cae82be4463d4081dbbcdef8f43581fe86a562f031d6b1abf77d6b052 42062 
pyosmium-doc_2.7.1-3_all.deb
 ee1528ddad25c1f2ca39b9665c3203273c011d918e518dc48bb4da7ec9ed79ac 5910424 
python-pyosmium-dbgsym_2.7.1-3_amd64.deb
 7486dbde1773a35201362b5f5268fe3b352b4f172d2272eb0e77b75a2d2d0899 452558 
python-pyosmium_2.7.1-3_amd64.deb
 ddf6447ff7bd925d7458a27011c41243f9aac9bd9ad0c60690766fcca4d224c2 5913838 
python3-pyosmium-dbgsym_2.7.1-3_amd64.deb
 334ed28b75b534f4ed81da6f8c9ccb3d52e4aae97157b099691522dbba901307 452216 
python3-pyosmium_2.7.1-3_amd64.deb
Files:
 6f163905b70fc308ec66e2f078e07197 2303 science optional pyosmium_2.7.1-3.dsc
 c23e7a06cdee57b43a13041127e2eb18 4932 science optional 
pyosmium_2.7.1-3.debian.tar.xz
 

Bug#826966: marked as done (libpythonqt-dev: Missing header PythonQtUtils.h)

[Debian Bug Tracking System]

Your message dated Mon, 04 Jul 2016 22:28:17 +
with message-id 
and subject line Bug#826966: fixed in pythonqt 3.0-2
has caused the Debian Bug report #826966,
regarding libpythonqt-dev: Missing header PythonQtUtils.h
to be marked as done.

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

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


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

Dear Maintainer,

/usr/include/PythonQt/PythonQt.h demands PythonQtUtils.h but this header,
although present in the source package, is missing.

Without this file it is impossible to compile anything against libPythonQt.

A possible solution is to add src/PythonQtUtils.h in CMakeLists.txt:145 and
rebuild the package.

Best,
a.



-- System Information:
Debian Release: 8.4
  APT prefers stable
  APT policy: (1000, 'stable'), (900, 'stable'), (750, 'testing')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 4.4.0-0.bpo.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 libpythonqt-dev depends on:
ii  libpythonqt3.0  3.0-1

libpythonqt-dev recommends no packages.

libpythonqt-dev suggests no packages.

-- no debconf information
--- End Message ---
--- Begin Message ---
Source: pythonqt
Source-Version: 3.0-2

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

Debian distribution maintenance software
pp.
Andreas Tille  (supplier of updated pythonqt 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, 04 Jul 2016 17:02:27 +0200
Source: pythonqt
Binary: libpythonqt3.0 libpythonqt-dev
Architecture: source
Version: 3.0-2
Distribution: unstable
Urgency: medium
Maintainer: Debian QA Group 
Changed-By: Andreas Tille 
Description:
 libpythonqt-dev - Dynamic Python binding for the Qt framework - development
 libpythonqt3.0 - Dynamic Python binding for the Qt framework - runtime
Closes: 826966
Changes:
 pythonqt (3.0-2) unstable; urgency=medium
 .
   * Orphan the package
   * Add PythonQtUtils.h which is somehow missing in CMakeLists.txt
 (Thanks for the hint to alex)
 Closes: #826966
   * cme fix dpkg-control
   * hardening=+bindnow
   * automatically use xz compression
Checksums-Sha1:
 041ea4725375a1f0b31a527bd5c2ad0ed6e31d8e 2005 pythonqt_3.0-2.dsc
 53282f8231d08e9213a50a571065c7ae70ee6743 4092 pythonqt_3.0-2.debian.tar.xz
Checksums-Sha256:
 d81c8ed9d4a09d6f57d6ed772af497d575973196657b9cdd52bf4bb069f5da09 2005 
pythonqt_3.0-2.dsc
 7b07f222128391c2b807d61de3908905f00d924298125c2809933a45fa2c507c 4092 
pythonqt_3.0-2.debian.tar.xz
Files:
 02fef1d1b5fce929cf356d405564fcd5 2005 libs optional pythonqt_3.0-2.dsc
 0fb4c6a3de86c601a3929f53e4f4690f 4092 libs optional 
pythonqt_3.0-2.debian.tar.xz

-BEGIN PGP SIGNATURE-
Version: GnuPG v1

iQIcBAEBCAAGBQJXesBiAAoJEFeKBJTRxkbR6wgP/jvfMFyr9CZQfx9n2rnJH2g8
DQwgA5NHzg/72aYt3g8g0kDR0uzh+z/R02BRjLnECm70aiY+d/1qu1RoVlDrYSj8
3g8QBL7Cy+Gpb+oN+padTfmS6eTSsRmif84sX29Zwrdhsi1oBf5xANv7YzSVA730
SybhUvBX6EHTms0wephOUZwGwZJYhMDCbqbCl5jlm/DMB6iOS6jWBn3qaqm3VDZ6
dgbXXYQpoxLKzZKNKn7WLbHXjN/DNSPX8yJtNgHHtQYpMKD2k09hymBtd5w4vd0O
XdS0cN6NZIX3GaO5tEo3ZaYI41tmrdtUkdOig/ARkotC/TydNO1Jiip2orP+a7vH
U8GeJ8BMMGh84xmZtrfhAEdP+G4l/AA4QH7d4jcOIswTQeJHMjxuK3HhoH2wPocM
LAhkJFfUUqknzOx6F4TGljWYN6oWbQMEtpzPVfLVfvs76krjRANeEhB2+PNW3c+g
i0DArasfokOEpXtKxWjtA8TCDKrkSXt8HxqWv+2ZNfNNJLxSBe3BsXyHKNbsmxFk
bNS5iqwLrMjXxOG5BAMnmianQK9RVogDGEfVPe4tielgy/8tRv7JcW/5a/RE+/aG
tOXLA6bCchJfXPjzcmQrVHf+QQuUYGHOPFXYdzLKtskCzeJ/iQCoMbIRaYnG+ISM
9MlwrlcOjNRW53fsiBI0
=233d
-END PGP SIGNATURE End Message ---

Bug#824944: Update on #824944

[Jason Pleau]

Hi,

I saw you seem to have fixed the bug in git last week [1]

Is the new version going to be uploaded to unstable soonish ? I also
noticed the version string in debian/changelog didn't really match
anything that upstream released. (I can't find 2.1.8 anywhere)

I'd be glad to help if you need. (I have a package that has a build-dep
that depends on lua-discount, so I got notified)

1:
https://anonscm.debian.org/cgit/pkg-lua/lua-discount.git/commit/?id=25d62151f8ed866ee938eb6e8191771b22e834ca

Thanks !

-- 
Jason Pleau

Processed: Re: Bug#828979: pyosmium: FTBFS in testing (FAIL: test_location_tuple)

[Debian Bug Tracking System]

Processing control commands:

> tags -1 pending
Bug #828979 [src:pyosmium] pyosmium: FTBFS in testing (FAIL: 
test_location_tuple)
Added tag(s) pending.

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

Bug#828979: pyosmium: FTBFS in testing (FAIL: test_location_tuple)

[Sebastiaan Couwenberg]

Control: tags -1 pending

Hi Santiago,

On 06/29/2016 05:47 PM, Sebastiaan Couwenberg wrote:
> Thanks for reporting this issue, I've forwarded it upstream.
> 
> I suspect the test failure is caused by changes in Python 2.7.12~rc1,
> because all the tests succeeded with Python 2.7.11.

I've added a patch to fix the test failure by changing the expected
output, that allows the tests to succeed on unstable and jessie (for the
backport). The patch has also been forwarded upstream.

Kind Regards,

Bas

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

Bug#829635: lintian: FTBFS: dpkg-source: error: syntax error in .../debian/tests/control

[Jakub Wilk]

Source: lintian
Version: 2.5.45
Severity: serious
Justification: fails to build from source

lintian FTBFS when built against dpkg-dev_1.18.9, because the following 
tests fail:


* tests::testsuite-control-not-file
| dpkg-buildpackage: info: source package testsuite-control-not-file
| dpkg-buildpackage: info: source version 1.0
| dpkg-buildpackage: info: source distribution unstable
| dpkg-buildpackage: info: source changed by Debian Lintian Maintainers 

|  dpkg-source -iNEVER_MATCH_ANYTHING -INEVER_MATCH_ANYTHING --auto-commit 
--before-build testsuite-control-not-file-1.0
| dpkg-buildpackage: info: host architecture i386
| dpkg-source: error: test control debian/tests/control is not a regular file
| dpkg-buildpackage: error: dpkg-source -iNEVER_MATCH_ANYTHING 
-INEVER_MATCH_ANYTHING --auto-commit --before-build 
testsuite-control-not-file-1.0 gave error exit status 255

* tests::testsuite-control-syntax
| dpkg-buildpackage: info: source package testsuite-control-syntax
| dpkg-buildpackage: info: source version 1.0
| dpkg-buildpackage: info: source distribution unstable
| dpkg-buildpackage: info: source changed by Debian Lintian Maintainers 

|  dpkg-source -iNEVER_MATCH_ANYTHING -INEVER_MATCH_ANYTHING --auto-commit 
--before-build testsuite-control-syntax-1.0
| dpkg-buildpackage: info: host architecture i386
| dpkg-source: error: syntax error in 
testsuite-control-syntax-1.0/debian/tests/control at line 1: line with unknown 
format (not field-colon-value)
| dpkg-buildpackage: error: dpkg-source -iNEVER_MATCH_ANYTHING 
-INEVER_MATCH_ANYTHING --auto-commit --before-build 
testsuite-control-syntax-1.0 gave error exit status 25

* tests::testsuite-general:
| dpkg-buildpackage: info: source package testsuite-general
| dpkg-buildpackage: info: source version 1.0
| dpkg-buildpackage: info: source distribution unstable
| dpkg-buildpackage: info: source changed by Debian Lintian Maintainers 

|  dpkg-source -iNEVER_MATCH_ANYTHING -INEVER_MATCH_ANYTHING --auto-commit 
--before-build testsuite-general-1.0
| dpkg-buildpackage: info: host architecture i386
| dpkg-source: error: syntax error in 
testsuite-general-1.0/debian/tests/control at line 26: block lacks either Tests 
or Test-Command fields
| dpkg-buildpackage: error: dpkg-source -iNEVER_MATCH_ANYTHING 
-INEVER_MATCH_ANYTHING --auto-commit --before-build testsuite-general-1.0 gave 
error exit status 25

--
Jakub Wilk

Bug#824896: fix available

[Nicholas D Steeves]

Because I do not yet have Debian upload privileges I have requested
sponsorship for an NMU that solves this bug.  The associated
sponsorship request, and the rationale for uploading 4.5.3 rather than
4.6.1 can be found in Bug #829205.

Cheers,
Nicholas

Processed: Re: [Pkg-xfce-devel] Bug#829348: lightdm: LightDM + MATE: switching users fails, unable to connect to D-Bus

[Debian Bug Tracking System]

Processing control commands:

> forcemerge -1 829557
Bug #829348 [lightdm] lightdm: LightDM + MATE: switching users fails, unable to 
connect to D-Bus
Bug #829557 [lightdm] lightdm 1.18.2-1 breaks D-BUS / gconf
Severity set to 'normal' from 'grave'
Added tag(s) moreinfo.
Merged 829348 829557

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

Bug#824895: [PATCH] warn against likely data loss

[Nicholas D Steeves]

Justification: Problems like these [1] still exist.

[1] https://www.spinics.net/lists/linux-btrfs/msg56596.html

Bug#829620: pcp: FTBFS: cp: cannot stat '.gitignore' (under qa/)

[Aaron M. Ucko]

Source: pcp
Version: 3.10.1
Severity: serious
Justification: fails to build from source (but built successfully in the past)

Builds of pcp have been failing:

  ../install-sh -o root -g root -m 644 common.check common.config common.filter 
common.product common.rc common.setup common.secure common.gfs2 common.rpm 
common.qt common.avahi common.docker common.discovery common.compress 
common.webapi common.python  group qa_hosts.master README sanity.coverage 
.gitignore valgrind-suppress valgrind-suppress-3.10.0 valgrind-suppress-3.5.0 
valgrind-suppress-3.6.0.SVN-Debian valgrind-suppress-3.6.1 
valgrind-suppress-3.7.0 valgrind-suppress-3.8.1 /var/lib/pcp/testsuite
  cp: cannot stat '.gitignore': No such file or directory
  GNUmakefile:81: recipe for target 'install_pcp' failed
  make[2]: *** [install_pcp] Error 1
  make[2]: Leaving directory '/«PKGBUILDDIR»/qa'
  GNUmakefile:62: recipe for target 'install_pcp' failed
  make[1]: *** [install_pcp] Error 2
  make[1]: Leaving directory '/«PKGBUILDDIR»'
  debian/rules:169: recipe for target 'binary-arch' failed
  make: *** [binary-arch] Error 2

Please either ensure arrange for this .gitignore file to be available
or fix the build system not to require it.  (Also, please double check
that there aren't similar issues in other subtrees.)

Thanks!

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

Kernel: Linux 4.6.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)

Bug#829442: marked as done (libconfig-model-itself-perl: FTBFS: Failed 1/12 test programs. 0/108 subtests failed.)

[Debian Bug Tracking System]

Your message dated Mon, 04 Jul 2016 18:48:57 +
with message-id 
and subject line Bug#829442: fixed in libconfig-model-itself-perl 2.005-1
has caused the Debian Bug report #829442,
regarding libconfig-model-itself-perl: FTBFS: Failed 1/12 test programs. 0/108 
subtests failed.
to be marked as done.

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

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


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

libconfig-model-itself-perl fails to build from source in unstable/amd64:

  [..]

  MasterModel::HashIdOfValues->hash_follower: parameter follow is deprecated in 
favor of follow_keys_from
  MasterModel::HashIdOfValues->hash_with_allow: parameter allow is deprecated 
in favor of allow_keys
  MasterModel::HashIdOfValues->hash_with_allow_from: parameter allow_from is 
deprecated in favor of allow_keys_from
  t/itself-editor.t .. 
  You can play with the widget if you run the test with 's' argument
  1..15
  ok 1 - compiled
  ok 2 - loaded Master model
  MasterModel->warp_el: using follow parameter in warped node is deprecated. 
follow must be specified in a warp parameter.
  MasterModel->warp_el: using rules parameter in warped node is deprecated. 
rules must be specified in a warp parameter.
  MasterModel::SlaveY->warp2: using follow parameter in warped node is 
deprecated. follow must be specified in a warp parameter.
  MasterModel::SlaveY->warp2: using rules parameter in warped node is 
deprecated. rules must be specified in a warp parameter.
  ok 3 - created master_model instance
  ok 4 - loaded some data in master_model instance
  ok 5 - Read Itself::Model and created instance
  MasterModel->warp_el: using follow parameter in warped node is deprecated. 
follow must be specified in a warp parameter.
  MasterModel->warp_el: using rules parameter in warped node is deprecated. 
rules must be specified in a warp parameter.
  MasterModel::SlaveY->warp2: using follow parameter in warped node is 
deprecated. follow must be specified in a warp parameter.
  MasterModel::SlaveY->warp2: using rules parameter in warped node is 
deprecated. rules must be specified in a warp parameter.
  Itself::Element->warp: using follow parameter in warped node is deprecated. 
follow must be specified in a warp parameter.
  Itself::Element->warp: using rules parameter in warped node is deprecated. 
rules must be specified in a warp parameter.
  Itself::Element->rules: using follow parameter in warped node is deprecated. 
follow must be specified in a warp parameter.
  Itself::Element->rules: using rules parameter in warped node is deprecated. 
rules must be specified in a warp parameter.
  Itself::Element->cargo: using follow parameter in warped node is deprecated. 
follow must be specified in a warp parameter.
  Itself::Element->cargo: using rules parameter in warped node is deprecated. 
rules must be specified in a warp parameter.
  Itself::NonWarpableElement->computed_refer_to: using follow parameter in 
warped node is deprecated. follow must be specified in a warp parameter.
  Itself::NonWarpableElement->computed_refer_to: using rules parameter in 
warped node is deprecated. rules must be specified in a warp parameter.
  Itself::NonWarpableElement->compute: using follow parameter in warped node is 
deprecated. follow must be specified in a warp parameter.
  Itself::NonWarpableElement->compute: using rules parameter in warped node is 
deprecated. rules must be specified in a warp parameter.
  Itself::NonWarpableElement->migrate_from: using follow parameter in warped 
node is deprecated. follow must be specified in a warp parameter.
  Itself::NonWarpableElement->migrate_from: using rules parameter in warped 
node is deprecated. rules must be specified in a warp parameter.
  Itself::CargoElement->warp: using follow parameter in warped node is 
deprecated. follow must be specified in a warp parameter.
  Itself::CargoElement->warp: using rules parameter in warped node is 
deprecated. rules must be specified in a warp parameter.
  Itself::CargoElement->rules: using follow parameter in warped node is 
deprecated. follow must be specified in a warp parameter.
  Itself::CargoElement->rules: using rules parameter in warped node is 
deprecated. rules must be specified in a warp parameter.

Bug#812286: marked as done (FTBFS with GCC 6: rcpp and quantlib need recompile with GCC 6)

[Debian Bug Tracking System]

Your message dated Mon, 04 Jul 2016 18:34:27 +
with message-id 
and subject line Bug#812286: fixed in rquantlib 0.4.2-2
has caused the Debian Bug report #812286,
regarding FTBFS with GCC 6: rcpp and quantlib need recompile with GCC 6
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.)


-- 
812286: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=812286
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: rquantlib
Version: 0.4.2-1
Severity: normal
User: debian-...@lists.debian.org
Usertags: ftbfs-gcc-6 gcc-6-unknown

This package fails to build with GCC 6.  GCC 6 has not been released
yet, but it's expected that GCC 6 will become the default compiler for
stretch.

Unfortunately, it's not clear from the log why the build failed.
It's possible there's a bug in this package or in GCC.  It's also
possible I reported a non-issue, although I tried to avoid that.
I apologize in advance if this is the case.

If you have some time to look into this issue, that'd be great.  If
not, I can re-test the package with GCC 6 in a few weeks time.

You can find a snapshot of GCC 6 in experimental.  To build with
GCC 6, you can set CC=gcc-6 CXX=g++-6 explicitly.

You may be able to find out more about this issue at
https://gcc.gnu.org/gcc-6/changes.html

> sbuild (Debian sbuild) 0.67.0 (26 Dec 2015) on dl580gen9-02.hlinux
...
> installing to 
> /<>/debian/r-cran-rquantlib/usr/lib/R/site-library/RQuantLib/libs
> ** R
> ** demo
> ** inst
> ** preparing package for lazy loading
> ** help
> *** installing help indices
> ** building package indices
> ** testing if installed package can be loaded
> 
>  *** caught segfault ***
> address 0x7f7f1504a6c0, cause 'invalid permissions'
> 
> Traceback:
>  1: dyn.load(file, DLLpath = DLLpath, ...)
>  2: library.dynam(lib, package, package.lib)
>  3: loadNamespace(package, c(which.lib.loc, lib.loc))
>  4: doTryCatch(return(expr), name, parentenv, handler)
>  5: tryCatchOne(expr, names, parentenv, handlers[[1L]])
>  6: tryCatchList(expr, classes, parentenv, handlers)
>  7: tryCatch(expr, error = function(e) {call <- conditionCall(e)if 
> (!is.null(call)) {if (identical(call[[1L]], quote(doTryCatch)))   
>   call <- sys.call(-4L)dcall <- deparse(call)[1L]prefix 
> <- paste("Error in", dcall, ": ")LONG <- 75Lmsg <- 
> conditionMessage(e)sm <- strsplit(msg, "\n")[[1L]]w <- 14L + 
> nchar(dcall, type = "w") + nchar(sm[1L], type = "w")if (is.na(w)) 
> w <- 14L + nchar(dcall, type = "b") + nchar(sm[1L], 
> type = "b")if (w > LONG) prefix <- paste0(prefix, "\n  ") 
>}else prefix <- "Error : "msg <- paste0(prefix, 
> conditionMessage(e), "\n").Internal(seterrmessage(msg[1L]))if 
> (!silent && identical(getOption("show.error.messages"), TRUE)) {  
>   cat(msg, file = stderr()).Internal(printDeferredWarnings())}
> invisible(structure(msg, class = "try-error", condition = e))})
>  8: try({ns <- loadNamespace(package, c(which.lib.loc, lib.loc))env 
> <- attachNamespace(ns, pos = pos, deps)})
>  9: library(pkg_name, lib.loc = lib, character.only = TRUE, logical.return = 
> TRUE)
> 10: withCallingHandlers(expr, packageStartupMessage = function(c) 
> invokeRestart("muffleMessage"))
> 11: suppressPackageStartupMessages(library(pkg_name, lib.loc = lib, 
> character.only = TRUE, logical.return = TRUE))
> 12: doTryCatch(return(expr), name, parentenv, handler)
> 13: tryCatchOne(expr, names, parentenv, handlers[[1L]])
> 14: tryCatchList(expr, classes, parentenv, handlers)
> 15: tryCatch(expr, error = function(e) {call <- conditionCall(e)if 
> (!is.null(call)) {if (identical(call[[1L]], quote(doTryCatch)))   
>   call <- sys.call(-4L)dcall <- deparse(call)[1L]prefix 
> <- paste("Error in", dcall, ": ")LONG <- 75Lmsg <- 
> conditionMessage(e)sm <- strsplit(msg, "\n")[[1L]]w <- 14L + 
> nchar(dcall, type = "w") + nchar(sm[1L], type = "w")if (is.na(w)) 
> w <- 14L + nchar(dcall, type = "b") + nchar(sm[1L], 
> type = "b")if (w > LONG) prefix <- paste0(prefix, "\n  ") 
>}else prefix <- "Error : "msg <- paste0(prefix, 
> conditionMessage(e), "\n").Internal(seterrmessage(msg[1L]))if 
> (!silent && identical(getOption("show.error.messages"), TRUE)) {  
>   cat(msg, file = stderr()).Internal(printDeferredWarnings())  

Bug#829442: libconfig-model-itself-perl: FTBFS: Failed 1/12 test programs. 0/108 subtests failed.

[Dominique Dumont]

On Sun, 03 Jul 2016 20:33:18 +0200 intrigeri  wrote:
> 
> Confirmed here (in pbuilder). Interestingly, testing is not affected.

I did some changes in Config::Model parameters to simplify 
Config::Model::Itself.

Unfortunately I did not find a way to avoid breaking Config::Model::Itself 
tests. Hence the failures that happens on in unstable.

I've uploaded upstream an updated version of Config::Model::Itself that fixes 
all issues.

I will upload a new package shortly.

All the best
-- 
 https://github.com/dod38fr/   -o- http://search.cpan.org/~ddumont/
http://ddumont.wordpress.com/  -o-   irc: dod at irc.debian.org

Bug#812286: Bug 812286 with R, Rcpp, QuantLib, RQuantLib and g++-6

[Dirk Eddelbuettel]

On 4 July 2016 at 19:33, Martin Michlmayr wrote:
| * Dirk Eddelbuettel  [2016-07-04 11:30]:
| > So how do I get the autoremove on rquantlib turned off?  Martin?
| 
| I don't know, but these bugs are not RC yet anyway.

I was partially asleep at the wheel. It needs a rebuild against the updated
QuantLib.  Doing that now.

So this issue is so far entirely local.  I dropped an element of the chain.
All my packages, so my bad :-/

The rebuild *should* fix this so I'll close it.

Dirk

-- 
http://dirk.eddelbuettel.com | @eddelbuettel | e...@debian.org

Bug#812286: Bug 812286 with R, Rcpp, QuantLib, RQuantLib and g++-6

[Martin Michlmayr]

* Dirk Eddelbuettel  [2016-07-04 11:30]:
> So how do I get the autoremove on rquantlib turned off?  Martin?

I don't know, but these bugs are not RC yet anyway.

-- 
Martin Michlmayr
HPE Linux, Hewlett Packard Enterprise

Bug#828163: marked as done (sbd: FTBFS: sbd-common.c:690:13: error: format not a string literal and no format arguments)

[Debian Bug Tracking System]

Your message dated Mon, 04 Jul 2016 17:50:47 +
with message-id 
and subject line Bug#828163: fixed in sbd 1.2.0-109-gc511b06-2
has caused the Debian Bug report #828163,
regarding sbd: FTBFS: sbd-common.c:690:13: error: format not a string literal 
and no format arguments
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.)


-- 
828163: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=828163
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: sbd
Version: 1.2.0-109-gc511b06-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,

sbd fails to build from source in unstable/amd64:

  [..]

  Selecting previously unselected package libcrmservice3:amd64.
  Preparing to unpack .../libcrmservice3_1.1.15-1_amd64.deb ...
  Unpacking libcrmservice3:amd64 (1.1.15-1) ...
  Selecting previously unselected package liblrmd1:amd64.
  Preparing to unpack .../liblrmd1_1.1.15-1_amd64.deb ...
  Unpacking liblrmd1:amd64 (1.1.15-1) ...
  Selecting previously unselected package liblrmd-dev:amd64.
  Preparing to unpack .../liblrmd-dev_1.1.15-1_amd64.deb ...
  Unpacking liblrmd-dev:amd64 (1.1.15-1) ...
  Selecting previously unselected package libcrmservice-dev:amd64.
  Preparing to unpack .../libcrmservice-dev_1.1.15-1_amd64.deb ...
  Unpacking libcrmservice-dev:amd64 (1.1.15-1) ...
  Selecting previously unselected package libqb-dev.
  Preparing to unpack .../libqb-dev_1.0-1_amd64.deb ...
  Unpacking libqb-dev (1.0-1) ...
  Selecting previously unselected package libcorosync-common-dev:amd64.
  Preparing to unpack .../libcorosync-common-dev_2.3.6-2_amd64.deb ...
  Unpacking libcorosync-common-dev:amd64 (2.3.6-2) ...
  Selecting previously unselected package libcpg-dev:amd64.
  Preparing to unpack .../libcpg-dev_2.3.6-2_amd64.deb ...
  Unpacking libcpg-dev:amd64 (2.3.6-2) ...
  Selecting previously unselected package icu-devtools.
  Preparing to unpack .../icu-devtools_55.1-7_amd64.deb ...
  Unpacking icu-devtools (55.1-7) ...
  Selecting previously unselected package libicu-dev:amd64.
  Preparing to unpack .../libicu-dev_55.1-7_amd64.deb ...
  Unpacking libicu-dev:amd64 (55.1-7) ...
  Selecting previously unselected package libxml2-dev:amd64.
  Preparing to unpack .../libxml2-dev_2.9.3+dfsg1-1.2_amd64.deb ...
  Unpacking libxml2-dev:amd64 (2.9.3+dfsg1-1.2) ...
  Selecting previously unselected package libplumbgpl2.
  Preparing to unpack .../libplumbgpl2_1.0.12-5_amd64.deb ...
  Unpacking libplumbgpl2 (1.0.12-5) ...
  Selecting previously unselected package libplumbgpl2-dev.
  Preparing to unpack .../libplumbgpl2-dev_1.0.12-5_amd64.deb ...
  Unpacking libplumbgpl2-dev (1.0.12-5) ...
  Selecting previously unselected package libplumb2.
  Preparing to unpack .../libplumb2_1.0.12-5_amd64.deb ...
  Unpacking libplumb2 (1.0.12-5) ...
  Selecting previously unselected package libplumb2-dev.
  Preparing to unpack .../libplumb2-dev_1.0.12-5_amd64.deb ...
  Unpacking libplumb2-dev (1.0.12-5) ...
  Selecting previously unselected package libaio1:amd64.
  Preparing to unpack .../libaio1_0.3.110-3_amd64.deb ...
  Unpacking libaio1:amd64 (0.3.110-3) ...
  Selecting previously unselected package libaio-dev.
  Preparing to unpack .../libaio-dev_0.3.110-3_amd64.deb ...
  Unpacking libaio-dev (0.3.110-3) ...
  Selecting previously unselected package uuid-dev:amd64.
  Preparing to unpack .../uuid-dev_2.28-5_amd64.deb ...
  Unpacking uuid-dev:amd64 (2.28-5) ...
  Processing triggers for man-db (2.7.5-1) ...
  Processing triggers for libc-bin (2.22-12) ...
  Processing triggers for libglib2.0-0:amd64 (2.48.1-1) ...
  No schema files found: doing nothing.
  Setting up dh-systemd (1.35) ...
  Setting up libelf1:amd64 (0.165-3) ...
  Setting up libglib2.0-data (2.48.1-1) ...
  Setting up libglib2.0-bin (2.48.1-1) ...
  Setting up libpcre16-3:amd64 (2:8.38-3.1) ...
  Setting up libpcre32-3:amd64 (2:8.38-3.1) ...
  Setting up libpcrecpp0v5:amd64 (2:8.38-3.1) ...
  Setting up libpcre3-dev:amd64 (2:8.38-3.1) ...
  Setting up pkg-config (0.29-4) ...
  Setting up zlib1g-dev:amd64 (1:1.2.8.dfsg-2+b1) ...
  Setting up libglib2.0-dev (2.48.1-1) ...
  Setting up libqb0:amd64 (1.0-1) ...
  Setting up libxslt1.1:amd64 (1.1.28-4) ...
  Setting up libcrmcommon3:amd64 (1.1.15-1) ...
  Setting up libpe-rules2:amd64 (1.1.15-1) ...
  Setting up libcib4:amd64 (1.1.15-1) ...
  Setting up libcib-dev:amd64 (1.1.15-1) ...
  Setting up libtransitioner2:amd64 (1.1.15-1) ...
  

Bug#829138: marked as done (liblist-moreutils-perl: tries to load code from cwd)

[Debian Bug Tracking System]

Your message dated Mon, 04 Jul 2016 17:49:54 +
with message-id 
and subject line Bug#829138: fixed in liblist-moreutils-perl 0.415-1
has caused the Debian Bug report #829138,
regarding liblist-moreutils-perl: tries to load code from cwd
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.)


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

Package: liblist-moreutils-perl
Version: 0.413-1+b1
Tags: security
Control: affects -1 + check-all-the-things

List::MoreUtils tries to load code from a subdirectory of the current 
working directory. This could lead to execution of arbitrary code if 
cwd is untrusted.


Proof of concept:

$ mkdir -p '(eval 1)/auto/List/MoreUtils/'
$ gcc -Wall -fPIC -shared moo.c -o '(eval 1)/auto/List/MoreUtils/MoreUtils.so'
$ perl -e 'no lib "."; use List::MoreUtils'
(__)
(oo)
  /--\/
 / |||
*  /\---/\
   ~~   ~~
..."Have you mooed today?"...
Segmentation fault


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

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

Versions of packages liblist-moreutils-perl depends on:
ii  libc6   2.22-13
ii  libexporter-tiny-perl   0.042-1
ii  perl5.22.2-1
ii  perl-base [perlapi-5.22.1]  5.22.2-1

--
Jakub Wilk
#include 
#include 
void __attribute__((constructor)) moo() {
	system("apt-get moo");
	kill(0, SIGSEGV);
}
--- End Message ---
--- Begin Message ---
Source: liblist-moreutils-perl
Source-Version: 0.415-1

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

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

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

Debian distribution maintenance software
pp.
Salvatore Bonaccorso  (supplier of updated 
liblist-moreutils-perl package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Mon, 04 Jul 2016 19:20:03 +0200
Source: liblist-moreutils-perl
Binary: liblist-moreutils-perl
Architecture: source
Version: 0.415-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Perl Group 
Changed-By: Salvatore Bonaccorso 
Closes: 829138
Description: 
 liblist-moreutils-perl - Perl module with additional list functions not found 
in List::Uti
Changes:
 liblist-moreutils-perl (0.415-1) unstable; urgency=medium
 .
   * Team upload.
 .
   [ Salvatore Bonaccorso ]
   * debian/control: Use HTTPS transport protocol for Vcs-Git URI
 .
   [ gregor herrmann ]
   * debian/copyright: change Copyright-Format 1.0 URL to HTTPS.
   * debian/upstream/metadata: change GitHub/CPAN URL(s) to HTTPS.
 .
   [ Salvatore Bonaccorso ]
   * Import upstream version 0.415
   * Update copyright years for upstream files
   * Update copyright years for included Config::AutoConf
   * Simplify Build-Depends on just only perl.
 The alternative version used as well to enforce the right version for
 Test::More is already satisfied in wheezy. Make only a Build-Depends to
 perl (unversioned).
   * Declare compliance with Debian policy 3.9.8
   * Drop unneeded patch makefile-author.patch (resolved in different way
 upstream)
   * debian/rules: Build enabling all hardening flags
   * Add patch to fix spelling errors in Contributing POD
   * Fix caller information passed down the stack.
 List/MoreUtils/XS.pm calls XSLoader::load from inside a string eval
 leading to the path used by XSLoader to determine the library to be
 (eval 1)/List/MoreUtils/XS.pm.
 Thanks to Jakub Wilk  (Closes: #829138)
Checksums-Sha1: 
 6524bff313b3d83eda33d23243e6997bff59beef 2307 
liblist-moreutils-perl_0.415-1.dsc
 6a067e7b40cdb1ae3a0acc6e55a93302c6a28477 132151 

Bug#828089: marked as done (consul fails to build on arm64 due to missing poll)

[Debian Bug Tracking System]

Your message dated Mon, 04 Jul 2016 17:49:42 +
with message-id 
and subject line Bug#828089: fixed in golang-golang-x-sys 
0.0~git20160704.0.a408501-1
has caused the Debian Bug report #828089,
regarding consul fails to build on arm64 due to missing poll
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.)


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

Package: golang-1.6
Severity: serious

consul failed to build on arm64 with

src/golang.org/x/sys/unix/zsyscall_linux_arm64.go:57: undefined: SYS_POLL


Googling this error finds https://github.com/golang/go/issues/16052 
which links to a commit fixing the issue. 
https://github.com/golang/sys/commit/5a8c7f28c1853e998847117cf1f3fe96ce88a59f 
can we get this fix in the Debian golang-1.6 package so that consul can 
be built successfully and migrate to testing. There is already at least 
one package in testing that build-depends on the new consul.
--- End Message ---
--- Begin Message ---
Source: golang-golang-x-sys
Source-Version: 0.0~git20160704.0.a408501-1

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

Debian distribution maintenance software
pp.
Martín Ferrari  (supplier of updated golang-golang-x-sys 
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, 04 Jul 2016 17:28:03 +
Source: golang-golang-x-sys
Binary: golang-golang-x-sys-dev
Architecture: source all
Version: 0.0~git20160704.0.a408501-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Go Packaging Team 

Changed-By: Martín Ferrari 
Description:
 golang-golang-x-sys-dev - Low-level interaction with the operating system
Closes: 828089
Changes:
 golang-golang-x-sys (0.0~git20160704.0.a408501-1) unstable; urgency=medium
 .
   * New upstream release. Closes: #828089.
   * debian/control:
 - Depend on recent dh-golang.
 - Remove unneeded Built-Using field.
   * debian/rules: use new dh-golang features to simplify rules.
Checksums-Sha1:
 7e97e15b9839f7a33c7f51fac475ce6629b43a69 2327 
golang-golang-x-sys_0.0~git20160704.0.a408501-1.dsc
 eefbd25105e71f42328f85dafc22b3eb66451cde 597802 
golang-golang-x-sys_0.0~git20160704.0.a408501.orig.tar.gz
 3ab6c7b81d4b91ba497d2d0b3c0172d98bbe91cb 2540 
golang-golang-x-sys_0.0~git20160704.0.a408501-1.debian.tar.xz
 9fcf1a193f16d2f1bcfa77dc4461cf8ea3a38265 183276 
golang-golang-x-sys-dev_0.0~git20160704.0.a408501-1_all.deb
Checksums-Sha256:
 9e1f2ee4d2f854274c62a976e8d727fd1c09e67bec257522d39e812530f056b8 2327 
golang-golang-x-sys_0.0~git20160704.0.a408501-1.dsc
 59f4bcddbdf7b6c6df84857f3eb03832fcb3b9a06d7628cfc641a515cf4b7e50 597802 
golang-golang-x-sys_0.0~git20160704.0.a408501.orig.tar.gz
 9b1f85387e0d34ca64ffc77d946a14e900e2b684e8e5f1463408473992caac9d 2540 
golang-golang-x-sys_0.0~git20160704.0.a408501-1.debian.tar.xz
 4ce1f16f5d9446aa137171b8d5a7bf494b6eac17ceb3391619efbe5453c24ab7 183276 
golang-golang-x-sys-dev_0.0~git20160704.0.a408501-1_all.deb
Files:
 959d813ed55a01db7cd505a822cdebe7 2327 devel extra 
golang-golang-x-sys_0.0~git20160704.0.a408501-1.dsc
 4f4399158e7fbd02115869fd0eefdd99 597802 devel extra 
golang-golang-x-sys_0.0~git20160704.0.a408501.orig.tar.gz
 d2292448ef92f9b010e39665ce9f1759 2540 devel extra 
golang-golang-x-sys_0.0~git20160704.0.a408501-1.debian.tar.xz
 f72fa767cf78f3d7d004ae11c80395d0 183276 devel extra 
golang-golang-x-sys-dev_0.0~git20160704.0.a408501-1_all.deb

-BEGIN PGP SIGNATURE-
Version: GnuPG v1

iQIcBAEBCAAGBQJXep0JAAoJEF3Y4L+Ro9PaR1YQAMwJ4AMmq+sMDznLkptYSQkC
SpGHWflQprBd0uF9hpDhypFvqNvxOtzxhTvw3501kteDLCoAB9E6ZsUCVnPtbImK
SJ9F2uLczPq/cZInvss+7VHW+17C4Dq9Fqa/H7dRsJujY6scYxJyc4QuPY7rokEC
WwUsoxCr4OfIGSuLBgB85gTIwPQcO2+mcbXrcSucLhAGZ4SNwG8t0L7WsBym26mT
yHBM430oqBDROVC6z3OxguRWeeYJrwJRsZ4Su9m113IByMrl59XldUPftc9tiqwe
RfXbTvcFLwAtnfm+dr5aOAiVH10n+IIwyjrpFptVJxF0V0EjDWYcstgINrRamkA3

Processed: [bts-link] source package zoneminder

[Debian Bug Tracking System]

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

> #
> # bts-link upstream status pull for source package zoneminder
> # see http://lists.debian.org/debian-devel-announce/2006/05/msg1.html
> #
> user bts-link-upstr...@lists.alioth.debian.org
Setting user to bts-link-upstr...@lists.alioth.debian.org (was 
bts-link-de...@lists.alioth.debian.org).
> # remote status report for #812026 (http://bugs.debian.org/812026)
> # Bug title: zoneminder: FTBFS with GCC 6: flexible array member...
> #  * https://github.com/ZoneMinder/ZoneMinder/issues/1265
> #  * remote status changed: open -> closed
> #  * closed upstream
> tags 812026 + fixed-upstream
Bug #812026 [zoneminder] zoneminder: FTBFS with GCC 6: flexible array member...
Added tag(s) fixed-upstream.
> usertags 812026 - status-open
Usertags were: status-open.
Usertags are now: .
> usertags 812026 + status-closed
There were no usertags set.
Usertags are now: status-closed.
> thanks
Stopping processing here.

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

Bug#828819: intel-microcode: i7-6500U doesn't boot in 4/5 cases with 3.20160607.1

[Henrique de Moraes Holschuh]

On Mon, 04 Jul 2016, Mike Palmer wrote:
> Jul  3 22:12:30 carbon kernel: [1.670464] microcode: CPU0
> sig=0x406e3, pf=0x80, revision=0x8a

Well, basically it is not doing anything because your BIOS has the new
microcode already...

I wanted to confirm the "pf", and it is the same pf as the other
processors that were reported to dislike the microcode update.

That said, there is microcode 0x94 already for this processor, so Intel
should issue another update sooner or later (and so will your vendor).

-- 
  "One disk to rule them all, One disk to find them. One disk to bring
  them all and in the darkness grind them. In the Land of Redmond
  where the shadows lie." -- The Silicon Valley Tarot
  Henrique Holschuh

Bug#828089: Pending fixes for bugs in the golang-golang-x-sys package

[pkg-go-maintainers]

tag 828089 + pending
tag 828089 + pending
thanks

Some bugs in the golang-golang-x-sys package are closed in revision
98299fbe9499529b1672358d68333d0868c5641f in branch 'master' by
Martín Ferrari

The full diff can be seen at
https://anonscm.debian.org/cgit/pkg-go/packages/golang-golang-x-sys.git/commit/?id=98299fb

Commit message:

New upstream release. Closes: #828089.

* New upstream release. Closes: #828089.
* debian/control: depend on recent dh-golang.
* debian/rules: use new dh-golang features to simplify rules.

Processed: Pending fixes for bugs in the golang-golang-x-sys package

[Debian Bug Tracking System]

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

> tag 828089 + pending
Bug #828089 [golang-golang-x-sys-dev] consul fails to build on arm64 due to 
missing poll
Added tag(s) pending.
> tag 828089 + pending
Bug #828089 [golang-golang-x-sys-dev] consul fails to build on arm64 due to 
missing poll
Ignoring request to alter tags of bug #828089 to the same tags previously set
> thanks
Stopping processing here.

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

Bug#829138: Pending fixes for bugs in the liblist-moreutils-perl package

[pkg-perl-maintainers]

tag 829138 + pending
thanks

Some bugs in the liblist-moreutils-perl package are closed in
revision b7bf84415bc2f20db926163b32571b071ef3a831 in branch 'master'
by Salvatore Bonaccorso

The full diff can be seen at
https://anonscm.debian.org/cgit/pkg-perl/packages/liblist-moreutils-perl.git/commit/?id=b7bf844

Commit message:

Fix caller information passed down the stack

List/MoreUtils/XS.pm calls XSLoader::load from inside a string eval
leading to the path used by XSLoader to determine the library to be
(eval 1)/List/MoreUtils/XS.pm.

Thanks: Jakub Wilk 

Closes: #829138

Processed: Pending fixes for bugs in the liblist-moreutils-perl package

[Debian Bug Tracking System]

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

> tag 829138 + pending
Bug #829138 [liblist-moreutils-perl] liblist-moreutils-perl: tries to load code 
from cwd
Added tag(s) pending.
> thanks
Stopping processing here.

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

Bug#822472: various haskell -dev packages are missing Built-Using attributes

[Sven Bartscher]

Am Mon, 4 Jul 2016 18:17:37 +0200
schrieb Matthias Klose :

> On 04.07.2016 15:01, Sven Bartscher wrote:
> > On Sun, 24 Apr 2016 22:13:47 +0200 Matthias Klose 
> > wrote:
> >> [snip]
> >>
> >> [I was doing a transition (icu 55 to 57), and investigating some
> >> build failures with link failures, some missing icu55 symbols. I
> >> didn't find the appropriate haskell package immediately, because it
> >> neither has a dependency on the icu runtime library or a
> >> Built-Using attribute ]
> >>
> >> Seen with haskell-text-icu, but it looks like there are no
> >> Built-Using attributes for any C library used for many packages.
> >> Therefore filing this isssue on a package which is maintained by
> >> the debian haskell maintainers. Feel free to clone, reassign, ...  
> > 
> > I'm afraid I don't understand what the problem is.
> > I don't see why our packages would need Build-Using fields on any C
> > libraries, because AFAIK all our packages that use C libraries are
> > dynamically linked against them and have the appropriate Depends on
> > them.  
> 
> I don't think so. For your library -dev packages you don't have any
> such dependencies.

Could you name an example? You mentioned libghc-text-icu-dev earlier,
but it has dependencies on libc6, libicu55 and libicu-dev. I don't see
anything missing here.

> > Are you at DebConf? If so, maybe we could meet and you explain the
> > problem to me.  
> 
> yes.

You don't seem to be online on IRC, so finding you isn't trivial.

Regards
Sven


pgpeWOPLozEQ8.pgp
Description: Digitale Signatur von OpenPGP

Processed: Re: Bug#829608: Acknowledgement (orthanc: ftbfs with new dcmtk)

[Debian Bug Tracking System]

Processing control commands:

> tags -1 patch
Bug #829608 [src:orthanc] orthanc: ftbfs with new dcmtk
Added tag(s) patch.
> tags -1 pending
Bug #829608 [src:orthanc] orthanc: ftbfs with new dcmtk
Added tag(s) pending.
> found -1 1.1.0+dfsg-1
Bug #829608 [src:orthanc] orthanc: ftbfs with new dcmtk
Marked as found in versions orthanc/1.1.0+dfsg-1.

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

Bug#829608: Acknowledgement (orthanc: ftbfs with new dcmtk)

[Gianfranco Costamagna]

control: tags -1 patch
control: tags -1 pending
control: found -1 1.1.0+dfsg-1

patch attached
Gianfranco


debdiff
Description: Binary data

Processed: Re: Bug#829607: Acknowledgement (odin: test failures against new dcmtk)

[Debian Bug Tracking System]

Processing control commands:

> severity -1 serious
Bug #829607 [src:odin] odin: test failures against new dcmtk
Severity set to 'serious' from 'normal'
> tags -1 patch
Bug #829607 [src:odin] odin: test failures against new dcmtk
Added tag(s) patch.
> tags -1 pending
Bug #829607 [src:odin] odin: test failures against new dcmtk
Added tag(s) pending.

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

Bug#829608: orthanc: ftbfs with new dcmtk

[Gianfranco Costamagna]

Source: orthanc
Severity: serious

Version: 1.1.0+dfsg-1
Tags: patch pending
Hi, I'm uploading a fix in deferred/15, for this build failure.
I'll attach the debdiff as soon as I have the bug report.
Gianfranco

Bug#828034: gnss-sdr 0.0.8 uploaded to mentors (fixes bugs #828034 and #828040)

[Carles Fernandez]

Package: gnss-sdr
Version: 0.0.8


Dear all,

I have just uploaded to mentors the latest upstream release, 0.0.8, which 
includes fixes for bugs #828034 and #828040 (thanks to Dejan Latinovic).

The URL of the package is:
https://mentors.debian.net/package/gnss-sdr 


The respective dsc file can be found at:
https://mentors.debian.net/debian/pool/main/g/gnss-sdr/gnss-sdr_0.0.8-1.dsc 


It is Iain Learmonth who usually signs the package, so I ask once again for his 
great help.

Best regards,
Carles





--

Dr. Carles Fernández Prades
Senior Researcher
Communication Systems Division

Centre Tecnològic de Telecomunicacions de Catalunya (CTTC)
Address: Parc Mediterrani de la Tecnologia
  Av. Carl Friedrich Gauss, 7
  08860 Castelldefels, Barcelona, Spain.
Phone: +34 936452909Fax: +34 936452901
http://www.cttc.es/people/cfernandez/ 








signature.asc
Description: Message signed with OpenPGP using GPGMail

Bug#829557: firefox: error box at start-up / D-BUS related issue

[Simon McVittie]

On Mon, 04 Jul 2016 at 12:43:41 +0200, Vincent Lefevre wrote:
> $ ls -a /tmp/*dbus*
> zsh: no match

This is normal. The session dbus-daemon on Linux uses abstract Unix
sockets (AF_UNIX sockets with sockaddr_un.sun_path[0] == '\0'), which
are not present in the filesystem at all: their names (the rest of
sockaddr_un.sun_path) are opaque and meaningless.

Confusingly, the value dbus-daemon chooses for the rest of sun_path
looks like a pathname, because it is chosen by code that transparently
uses either an abstract Unix socket or a filesystem-backed Unix socket,
whichever the kernel supports.

> The dbus related processes:
> 
> UIDPID  PPID  C STIME TTY  TIME CMD
> message+   879 1  0 Jul01 ?00:00:02 /usr/bin/dbus-daemon --system 
> --address=systemd: --nofork --nopidfile --systemd-activation

This is the system bus and is not relevant here: your problem is with
the session bus.

> lightdm   3597 1  0 Jul01 ?00:00:00 dbus-launch 
> --autolaunch=dcbbbc34fb4249e4864ba967a9d3b514 --binary-syntax --close-stderr
> lightdm   3598 1  0 Jul01 ?00:00:00 /usr/bin/dbus-daemon --fork 
> --print-pid 5 --print-address 7 --session

This is the lightdm user's session bus, started as a side-effect
of something in the lightdm greeter using D-Bus. It is not running
under your uid and hopefully should not be relevant here.

> vlefevre  9702 1  0 11:20 ?00:00:00 /usr/bin/dbus-launch 
> --exit-with-session --sh-syntax
> vlefevre 30347 1  0 Jul03 pts/000:00:00 dbus-launch --autolaunch 
> dcbbbc34fb4249e4864ba967a9d3b514 --binary-syntax --close-stderr
> vlefevre 30348 1  0 Jul03 ?00:00:00 /usr/bin/dbus-daemon --fork 
> --print-pid 5 --print-address 7 --session

These indicate that something in your session, whose controlling terminal
is /dev/pts/0 (?!), used D-Bus and started a dbus-daemon as a side-effect
("autolaunching", pid 30347/30348); and in addition, dbus-launch was run
during your X11 session startup (pid 9702; most likely by
/etc/X11/Xsession.d/75dbus_dbus-launch). From the fact that pid 9702
does not have a dbus-daemon child, I think we can infer that it has
latched onto some other dbus-daemon - hopefully 30348 - advertised in
a hidden X11 window by some other dbus-launch - hopefully 30347.

What is /dev/pts/0? Is it a terminal or something?

It might be enlightening to see the result of

env | grep '^DBUS'

inside the session that is failing (for example from an xterm); if
you're lucky, there might be a process ID (I can't remember whether that
gets exported or not). It might also be useful to attach a gdb to each
dbus-launch process (with dbus-1-dbg installed), go to the frame that
is in main() and do "p bus_pid", "p bus_address", "p address", "p wid"
before detaching.

For a session startup less closely resembling a Rube Goldberg machine,
consider installing dbus-user-session. This makes a semantic change
to the meaning of "D-Bus session", which is why it is not the default:
it is meant to be "opt-in". See its Description for details.

At some point I'm probably going to do a mass-bug-filing for misuses of
dbus-launch, with a mini-policy on what desktop components should do about
D-Bus, and a side goal of having all desktop environments that currently
depend on dbus-x11 switch to "dbus-x11 | dbus-user-session" (or even
"dbus-user-session | dbus-x11") so that removing dbus-x11 altogether
becomes feasible. This is blocking on me writing up that mini-policy,
without which a mass-bug-filing would be unconstructive.

Regards,
S

Bug#828819: intel-microcode: i7-6500U doesn't boot in 4/5 cases with 3.20160607.1

[Mike Palmer]

>From the kernel log this is all I see now that it is working.

Jul  3 22:12:30 carbon kernel: [1.670464] microcode: CPU0
sig=0x406e3, pf=0x80, revision=0x8a
Jul  3 22:12:30 carbon kernel: [1.670477] microcode: CPU1
sig=0x406e3, pf=0x80, revision=0x8a
Jul  3 22:12:30 carbon kernel: [1.670513] microcode: CPU2
sig=0x406e3, pf=0x80, revision=0x8a
Jul  3 22:12:30 carbon kernel: [1.670540] microcode: CPU3
sig=0x406e3, pf=0x80, revision=0x8a
Jul  3 22:12:30 carbon kernel: [1.670830] microcode: Microcode
Update Driver: v2.01 , Peter Oruba

This is what it said when intel-microcode 3.20160607.1 dropped and it
stopped booting.

Jun 26 22:44:41 carbon kernel: [1.722592] microcode: CPU0
sig=0x406e3, pf=0x80, revision=0x74
Jun 26 22:44:41 carbon kernel: [1.722657] microcode: CPU1
sig=0x406e3, pf=0x80, revision=0x74
Jun 26 22:44:41 carbon kernel: [1.722767] microcode: CPU2
sig=0x406e3, pf=0x80, revision=0x74
Jun 26 22:44:41 carbon kernel: [1.722849] microcode: CPU3
sig=0x406e3, pf=0x80, revision=0x74

I had an older 4.6-trunk kernel on the system as well from experimental
that did not get the initramfs hook called on it when intel-microcode
updated. So that one continued to boot while I couldn't use the kernel
that did until I updated the bios. I also tried "update-initramfs -u -k
4.6.0-1-amd64" many times to fix it with no luck. Only after updating
the BIOS did it boot with the previously generated initramfs.

(this is post BIOS update btw)

# cat /proc/cpuinfo 
processor   : 0
vendor_id   : GenuineIntel
cpu family  : 6
model   : 78
model name  : Intel(R) Core(TM) m3-6Y30 CPU @ 0.90GHz
stepping: 3
microcode   : 0x8a
cpu MHz : 427.617
cache size  : 4096 KB
physical id : 0
siblings: 4
core id : 0
cpu cores   : 2
apicid  : 0
initial apicid  : 0
fpu : yes
fpu_exception   : yes
cpuid level : 22
wp  : yes
flags   : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr
pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe
syscall nx pdpe1gb rdtscp lm constant_tsc art arch_perfmon pebs bts
rep_good nopl xtopology nonstop_tsc aperfmperf eagerfpu pni pclmulqdq
dtes64 monitor ds_cpl vmx est tm2 ssse3 sdbg fma cx16 xtpr pdcm pcid
sse4_1 sse4_2 x2apic movbe popcnt tsc_deadline_timer aes xsave avx f16c
rdrand lahf_lm abm 3dnowprefetch epb intel_pt tpr_shadow vnmi
flexpriority ept vpid fsgsbase tsc_adjust bmi1 avx2 smep bmi2 erms
invpcid mpx rdseed adx smap clflushopt xsaveopt xsavec xgetbv1 dtherm
ida arat pln pts hwp hwp_notify hwp_act_window hwp_epp
bugs:
bogomips: 3023.81
clflush size: 64
cache_alignment : 64
address sizes   : 39 bits physical, 48 bits virtual
power management:

processor   : 1
vendor_id   : GenuineIntel
cpu family  : 6
model   : 78
model name  : Intel(R) Core(TM) m3-6Y30 CPU @ 0.90GHz
stepping: 3
microcode   : 0x8a
cpu MHz : 473.320
cache size  : 4096 KB
physical id : 0
siblings: 4
core id : 1
cpu cores   : 2
apicid  : 2
initial apicid  : 2
fpu : yes
fpu_exception   : yes
cpuid level : 22
wp  : yes
flags   : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr
pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe
syscall nx pdpe1gb rdtscp lm constant_tsc art arch_perfmon pebs bts
rep_good nopl xtopology nonstop_tsc aperfmperf eagerfpu pni pclmulqdq
dtes64 monitor ds_cpl vmx est tm2 ssse3 sdbg fma cx16 xtpr pdcm pcid
sse4_1 sse4_2 x2apic movbe popcnt tsc_deadline_timer aes xsave avx f16c
rdrand lahf_lm abm 3dnowprefetch epb intel_pt tpr_shadow vnmi
flexpriority ept vpid fsgsbase tsc_adjust bmi1 avx2 smep bmi2 erms
invpcid mpx rdseed adx smap clflushopt xsaveopt xsavec xgetbv1 dtherm
ida arat pln pts hwp hwp_notify hwp_act_window hwp_epp
bugs:
bogomips: 3025.29
clflush size: 64
cache_alignment : 64
address sizes   : 39 bits physical, 48 bits virtual
power management:

processor   : 2
vendor_id   : GenuineIntel
cpu family  : 6
model   : 78
model name  : Intel(R) Core(TM) m3-6Y30 CPU @ 0.90GHz
stepping: 3
microcode   : 0x8a
cpu MHz : 418.417
cache size  : 4096 KB
physical id : 0
siblings: 4
core id : 0
cpu cores   : 2
apicid  : 1
initial apicid  : 1
fpu : yes
fpu_exception   : yes
cpuid level : 22
wp  : yes
flags   : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr
pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe
syscall nx pdpe1gb rdtscp lm constant_tsc art arch_perfmon pebs bts
rep_good nopl xtopology nonstop_tsc aperfmperf eagerfpu pni pclmulqdq
dtes64 monitor ds_cpl vmx est tm2 ssse3 sdbg fma cx16 xtpr pdcm pcid
sse4_1 sse4_2 x2apic movbe popcnt tsc_deadline_timer aes xsave avx f16c
rdrand lahf_lm abm 

Bug#812286: Bug 812286 with R, Rcpp, QuantLib, RQuantLib and g++-6

[Dirk Eddelbuettel]

On 4 July 2016 at 18:26, Matthias Klose wrote:
| On 04.07.2016 16:36, Dirk Eddelbuettel wrote:
| > 
| > On 3 July 2016 at 18:01, Dirk Eddelbuettel wrote:
| > | On Sun, Jul 03, 2016 at 07:43:49PM +0200, Martin Michlmayr wrote:
| > | > [I've copied Matthias so he can comment on this]
| > | > 
| > | > * Dirk Eddelbuettel  [2016-07-03 17:39]:
| > | > > For this issue (and its already long thread in the BTS):
| > | > > 
| > | > >  - You are correct. We need g++-6 for QuantLib, for Rcpp and then 
RQuantLib
| > | > > 
| > | > >  - Shall I do new uploads of QuantLib (and then Rcpp) with g++-6 now?
| > | > > 
| > | > >  - To then be followed by a rebuild of RQuantLib?
| > | > 
| > | > doko, can you suggest when to do this?  If you read the bug log,
| > | > you'll see that there are some dependency issues.
| > | 
| > | Generally speaking, when R itself builds, it stores its CC,CXX,... 
settings in its
| > | configuration which then becomes the default.
| > | 
| > | So in that case I could rebiuld R itself with g++-6. I don't have much
| > | experience "launching" a full binary migration in Debian but methinks
| > | we need this here.  And once R has been rebuild, we can just do
| > | automatic (?) binary NMUs to get g++-6.
| > | 
| > | (And for this particular bug I need to rebuild QuantLib as well.)
| > | 
| > | Does that sound right?
| > 
| > doko?
| > 
| > Shall I start more narrowly with just Rcpp, QuantLib and then RQuantLib?
| > This *will* force all package depending on Rcpp to rebuild:
| > 
| > $ apt-cache rdepends r-cran-rcpp
| > r-cran-rcpp
| > Reverse Depends:
| >   r-cran-rcppeigen
| >   r-cran-rquantlib
| >   r-cran-xml2
| >   r-cran-surveillance
| >   r-cran-shiny
| >   r-cran-rprotobuf
| >   r-cran-rncl
| >   r-cran-rinside
| >   r-cran-reshape2
| >   r-cran-readxl
| >   r-cran-amelia
| >   r-cran-rcpparmadillo
| >   r-cran-plyr
| >   r-cran-minqa
| >   r-cran-htmltools
| >   r-cran-dplyr
| >   r-cran-bayesfactor
| > $
| > 
| > I maintain some but not all of these.  They *will* break when you mix
| > compilers.
| > 
| > Now, if we don't want that now, can we "defuse" (ie delay) the autoremove on
| > rquantlib?
| 
| hmm, but then you have to explicitly use gcc-6. Is this really something you
| want to do? Why not wait until gcc points to 6, and then stage your 
transition?

Yes -- could not agree more.  That is also what we did last round with gcc-5.

So how do I get the autoremove on rquantlib turned off?  Martin?

Dirk


-- 
http://dirk.eddelbuettel.com | @eddelbuettel | e...@debian.org

Bug#812286: Bug 812286 with R, Rcpp, QuantLib, RQuantLib and g++-6

[Matthias Klose]

On 04.07.2016 16:36, Dirk Eddelbuettel wrote:
> 
> On 3 July 2016 at 18:01, Dirk Eddelbuettel wrote:
> | On Sun, Jul 03, 2016 at 07:43:49PM +0200, Martin Michlmayr wrote:
> | > [I've copied Matthias so he can comment on this]
> | > 
> | > * Dirk Eddelbuettel  [2016-07-03 17:39]:
> | > > For this issue (and its already long thread in the BTS):
> | > > 
> | > >  - You are correct. We need g++-6 for QuantLib, for Rcpp and then 
> RQuantLib
> | > > 
> | > >  - Shall I do new uploads of QuantLib (and then Rcpp) with g++-6 now?
> | > > 
> | > >  - To then be followed by a rebuild of RQuantLib?
> | > 
> | > doko, can you suggest when to do this?  If you read the bug log,
> | > you'll see that there are some dependency issues.
> | 
> | Generally speaking, when R itself builds, it stores its CC,CXX,... settings 
> in its
> | configuration which then becomes the default.
> | 
> | So in that case I could rebiuld R itself with g++-6. I don't have much
> | experience "launching" a full binary migration in Debian but methinks
> | we need this here.  And once R has been rebuild, we can just do
> | automatic (?) binary NMUs to get g++-6.
> | 
> | (And for this particular bug I need to rebuild QuantLib as well.)
> | 
> | Does that sound right?
> 
> doko?
> 
> Shall I start more narrowly with just Rcpp, QuantLib and then RQuantLib?
> This *will* force all package depending on Rcpp to rebuild:
> 
> $ apt-cache rdepends r-cran-rcpp
> r-cran-rcpp
> Reverse Depends:
>   r-cran-rcppeigen
>   r-cran-rquantlib
>   r-cran-xml2
>   r-cran-surveillance
>   r-cran-shiny
>   r-cran-rprotobuf
>   r-cran-rncl
>   r-cran-rinside
>   r-cran-reshape2
>   r-cran-readxl
>   r-cran-amelia
>   r-cran-rcpparmadillo
>   r-cran-plyr
>   r-cran-minqa
>   r-cran-htmltools
>   r-cran-dplyr
>   r-cran-bayesfactor
> $
> 
> I maintain some but not all of these.  They *will* break when you mix
> compilers.
> 
> Now, if we don't want that now, can we "defuse" (ie delay) the autoremove on
> rquantlib?

hmm, but then you have to explicitly use gcc-6. Is this really something you
want to do? Why not wait until gcc points to 6, and then stage your transition?

Bug#822472: various haskell -dev packages are missing Built-Using attributes

[Matthias Klose]

On 04.07.2016 15:01, Sven Bartscher wrote:
> On Sun, 24 Apr 2016 22:13:47 +0200 Matthias Klose 
> wrote:
>> Package: haskell-devscripts
>> Version: 0.10.2.3
>> Severity: serious
>> Tags: sid stretch
>>
>> [I was doing a transition (icu 55 to 57), and investigating some
>> build failures with link failures, some missing icu55 symbols. I
>> didn't find the appropriate haskell package immediately, because it
>> neither has a dependency on the icu runtime library or a Built-Using
>> attribute ]
>>
>> Seen with haskell-text-icu, but it looks like there are no
>> Built-Using attributes for any C library used for many packages.
>> Therefore filing this isssue on a package which is maintained by the
>> debian haskell maintainers. Feel free to clone, reassign, ...
> 
> I'm afraid I don't understand what the problem is.
> I don't see why our packages would need Build-Using fields on any C
> libraries, because AFAIK all our packages that use C libraries are
> dynamically linked against them and have the appropriate Depends on
> them.

I don't think so. For your library -dev packages you don't have any such
dependencies.

> Are you at DebConf? If so, maybe we could meet and you explain the
> problem to me.

yes.

Bug#811992: librostlab-blast: FTBFS with GCC 6: misc errors

[Gert Wollny]

Hi, 

there seems to be a bug in g++-6 [1] that results in this compile
failure. 

I think the only way to quell this bug at the moment is to force c++03,
i.e. 

  export DEB_CXXFLAGS_MAINT_APPEND  = -std=c++03

in d/rules. 

Because this workaround exists I'm not adding #829604 as blocker now.
Also I'd like to know th opinion of the gcc maintainers on whether this
is really a bug, or a new c++ feature I'm not aware of. 

If #829604 is for real, I will open a whishlist bug instead that asks
for removing -std=c++03 and and the according blocker. 

best, 
Gert 


[1]  https://bugs.debian.org/829604

Bug#811576: patch

[Mike Gerow]

On Fri, 01 Jul 2016 08:27:48 +0200 Robert Bihlmeyer  wrote:
> Package: tpm-tools
> Followup-For: Bug #811576
> 
> The indentation is wrong. Attaching a patch, if reportbug allows me to do it.
Looking at the problem again the whole issue seems to be with some
confusing mixing of tabs and spaces in just this one area. The attached
patch just replaces these with tabs and puts it in a quilt patch.

I'll go ahead and post the patch on the trousers development list too.

-- 
Mike Gerow
ge...@mgerow.com
diff -Nru tpm-tools-1.3.8/debian/changelog tpm-tools-1.3.8/debian/changelog
--- tpm-tools-1.3.8/debian/changelog	2015-06-28 12:15:23.0 +0200
+++ tpm-tools-1.3.8/debian/changelog	2016-07-04 17:05:26.0 +0200
@@ -1,3 +1,11 @@
+tpm-tools (1.3.8-2.1) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * Fix confusing indentation in tpm_present.c that fails build with GCC 6
+(Closes: #811576).
+
+ -- Mike Gerow   Mon, 04 Jul 2016 16:49:41 +0200
+
 tpm-tools (1.3.8-2) unstable; urgency=medium
 
   * Add patch 03 to fix FTBFS with gcc-5 (Closes: #778147)
diff -Nru tpm-tools-1.3.8/debian/patches/05-fix-FTBFS-gcc-6.patch tpm-tools-1.3.8/debian/patches/05-fix-FTBFS-gcc-6.patch
--- tpm-tools-1.3.8/debian/patches/05-fix-FTBFS-gcc-6.patch	1970-01-01 02:00:00.0 +0200
+++ tpm-tools-1.3.8/debian/patches/05-fix-FTBFS-gcc-6.patch	2016-07-04 16:56:36.0 +0200
@@ -0,0 +1,21 @@
+--- a/src/tpm_mgmt/tpm_present.c
 b/src/tpm_mgmt/tpm_present.c
+@@ -349,13 +349,13 @@
+ 		}
+ 	} while (flags[++i].name);
+ 
+-  out_success:
++out_success:
+ 	logSuccess(argv[0]);
+ 	iRc = 0;
+-  out_close:
++out_close:
+ 	contextClose(hContext);
+-  out:
+-if (szTpmPasswd && !isWellKnown)
+-	shredPasswd( szTpmPasswd );
++out:
++	if (szTpmPasswd && !isWellKnown)
++		shredPasswd( szTpmPasswd );
+ 	return iRc;
+ }
diff -Nru tpm-tools-1.3.8/debian/patches/series tpm-tools-1.3.8/debian/patches/series
--- tpm-tools-1.3.8/debian/patches/series	2015-06-28 12:11:26.0 +0200
+++ tpm-tools-1.3.8/debian/patches/series	2016-07-04 16:57:31.0 +0200
@@ -2,3 +2,4 @@
 02-cflags-errors-unused.patch
 03-fix-bool-error-parseStringWithValues.patch
 04-fix-FTBFS-clang.patch
+05-fix-FTBFS-gcc-6.patch


signature.asc
Description: PGP signature

Bug#812286: Bug 812286 with R, Rcpp, QuantLib, RQuantLib and g++-6

[Dirk Eddelbuettel]

On 3 July 2016 at 18:01, Dirk Eddelbuettel wrote:
| On Sun, Jul 03, 2016 at 07:43:49PM +0200, Martin Michlmayr wrote:
| > [I've copied Matthias so he can comment on this]
| > 
| > * Dirk Eddelbuettel  [2016-07-03 17:39]:
| > > For this issue (and its already long thread in the BTS):
| > > 
| > >  - You are correct. We need g++-6 for QuantLib, for Rcpp and then 
RQuantLib
| > > 
| > >  - Shall I do new uploads of QuantLib (and then Rcpp) with g++-6 now?
| > > 
| > >  - To then be followed by a rebuild of RQuantLib?
| > 
| > doko, can you suggest when to do this?  If you read the bug log,
| > you'll see that there are some dependency issues.
| 
| Generally speaking, when R itself builds, it stores its CC,CXX,... settings 
in its
| configuration which then becomes the default.
| 
| So in that case I could rebiuld R itself with g++-6. I don't have much
| experience "launching" a full binary migration in Debian but methinks
| we need this here.  And once R has been rebuild, we can just do
| automatic (?) binary NMUs to get g++-6.
| 
| (And for this particular bug I need to rebuild QuantLib as well.)
| 
| Does that sound right?

doko?

Shall I start more narrowly with just Rcpp, QuantLib and then RQuantLib?
This *will* force all package depending on Rcpp to rebuild:

$ apt-cache rdepends r-cran-rcpp
r-cran-rcpp
Reverse Depends:
  r-cran-rcppeigen
  r-cran-rquantlib
  r-cran-xml2
  r-cran-surveillance
  r-cran-shiny
  r-cran-rprotobuf
  r-cran-rncl
  r-cran-rinside
  r-cran-reshape2
  r-cran-readxl
  r-cran-amelia
  r-cran-rcpparmadillo
  r-cran-plyr
  r-cran-minqa
  r-cran-htmltools
  r-cran-dplyr
  r-cran-bayesfactor
$

I maintain some but not all of these.  They *will* break when you mix
compilers.

Now, if we don't want that now, can we "defuse" (ie delay) the autoremove on
rquantlib?

| > > In case I don't get my server back up in time, is there another
| > > (convenient) machine somewhere I can use?  Worst case I can try to set
| > > up a new pbuilder environment on another machine.
| > 
| > http://db.debian.org/machines.cgi lists some machines where you can
| > log in.  There are chroots and you can install packages.
| 
| Very helpful, thank you. That should help. The accessible ones are the
| ones marked 'public' ?

I did get my server back. It is an older machine, upgraded many times which
each Ubuntu release, and now running Ubuntu 16.04 which seemingly forgets to
call 'lvm vgchange -ay' during boot forcing me to do it by hand from
initramfs.  Not sure how to make the boot process do it for me.  Asked here:
http://askubuntu.com/questions/794526/

Dirk
 
| Dirk
| 
| > -- 
| > Martin Michlmayr
| > HPE Linux, Hewlett Packard Enterprise
| 
| -- 
| Three out of two people have difficulties with fractions.

-- 
http://dirk.eddelbuettel.com | @eddelbuettel | e...@debian.org

Bug#825466: marked as done (FTBFS on i386: needs -msse2 flag)

[Debian Bug Tracking System]

Your message dated Mon, 4 Jul 2016 11:35:54 -0300
with message-id 

and subject line Re: FTBFS on i386: needs -msse2 flag
has caused the Debian Bug report #825466,
regarding FTBFS on i386: needs -msse2 flag
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.)


-- 
825466: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=825466
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: webrtc-audio-processing
Severity: serious
Tags: patch
Justification: fails to build from source (but built successfully in the past)

Using the attached patch built successfully libwebrtc-audio-processing1 and
pulseaudio 8.99.



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

Kernel: Linux 4.6.0-trunk-amd64 (SMP w/8 CPU cores)
Locale: LANG=es_AR.UTF-8, LC_CTYPE=es_AR.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
--- webrtc-audio-processing-0.2/configure.ac	2016-05-26 23:10:55.903649671 -0300
+++ webrtc-audio-processing-0.2/configure.ac.new	2016-05-26 23:10:39.883490181 -0300
@@ -59,6 +59,7 @@
 [i?86|x86_64],
 [
  HAVE_X86=1
+	 ARCH_CFLAGS="-msse2"
 ],
 [armv7*|armv8*],
 [
--- End Message ---
--- Begin Message ---
Version: 0.3-1

On Thu, 26 May 2016 23:16:23 -0300 Gerardo Esteban Malazdrewicz
 wrote:
> Source: webrtc-audio-processing
> Severity: serious
> Tags: patch
> Justification: fails to build from source (but built successfully in the past)
>
> Using the attached patch built successfully libwebrtc-audio-processing1 and
> pulseaudio 8.99.

This was fixed in the latest upload, but with a different patch (we
can't assume sse is available).


Saludos--- End Message ---

Bug#811724: New SuperTuxKart upstream version 0.9.2 fixes this critical Debian bug, please upload new release

[UAB "Bona Mens" paslaugos]

New SuperTuxKart upstream version 0.9.2 fixes this critical Debian bug,
please upload new STK release.

Should I report separate bug in Debian BTS about new upstream stable
Supertuxkart release?

-- 

IT paslaugos įmonėms, prekyba kompiuteriais su Linux OS:
UAB „Bona Mens“  - http://bonamens.lt  http://tinklas.eu/prekyba
Tel.: +370-614-53085
Laisva programinė įranga verslui ir namams:http://baltix.lthttp://openoffice.lt

Processed: tagging 811576

[Debian Bug Tracking System]

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

> tags 811576 + patch
Bug #811576 [tpm-tools] FTBFS with GCC 6: statement indented as if it were 
guarded by
Added tag(s) patch.
> thanks
Stopping processing here.

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

Bug#812264: marked as done (samba: FTBFS with GCC 6: ctype.h:216: first defined here)

[Debian Bug Tracking System]

Your message dated Mon, 04 Jul 2016 13:51:05 +
with message-id 
and subject line Bug#812264: fixed in samba 2:4.4.4+dfsg-3
has caused the Debian Bug report #812264,
regarding samba: FTBFS with GCC 6: ctype.h:216: first defined here
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.)


-- 
812264: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=812264
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: samba
Version: 2:4.3.3+dfsg-1
Severity: normal
User: debian-...@lists.debian.org
Usertags: ftbfs-gcc-6 gcc-6-unknown

This package fails to build with GCC 6.  GCC 6 has not been released
yet, but it's expected that GCC 6 will become the default compiler for
stretch.

Unfortunately, it's not clear from the log why the build failed.
It's possible there's a bug in this package or in GCC.  It's also
possible I reported a non-issue, although I tried to avoid that.
I apologize in advance if this is the case.

If you have some time to look into this issue, that'd be great.  If
not, I can re-test the package with GCC 6 in a few weeks time.

You can find a snapshot of GCC 6 in experimental.  To build with
GCC 6, you can set CC=gcc-6 CXX=g++-6 explicitly.

You may be able to find out more about this issue at
https://gcc.gnu.org/gcc-6/changes.html

> sbuild (Debian sbuild) 0.67.0 (26 Dec 2015) on dl580gen9-02.hlinux
...
> [ 253/4013] Linking default/source4/heimdal_build/compile_et
> 07:16:25 runner /usr/bin/gcc default/source4/heimdal/lib/roken/base64_3.o 
> default/source4/heimdal/lib/roken/ct_3.o 
> default/source4/heimdal/lib/roken/hex_3.o 
> default/source4/heimdal/lib/roken/bswap_3.o 
> default/source4/heimdal/lib/roken/dumpdata_3.o 
> default/source4/heimdal/lib/roken/emalloc_3.o 
> default/source4/heimdal/lib/roken/ecalloc_3.o 
> default/source4/heimdal/lib/roken/getarg_3.o 
> default/source4/heimdal/lib/roken/get_window_size_3.o 
> default/source4/heimdal/lib/roken/getdtablesize_3.o 
> default/source4/heimdal/lib/roken/h_errno_3.o 
> default/source4/heimdal/lib/roken/issuid_3.o 
> default/source4/heimdal/lib/roken/net_read_3.o 
> default/source4/heimdal/lib/roken/net_write_3.o 
> default/source4/heimdal/lib/roken/parse_time_3.o 
> default/source4/heimdal/lib/roken/parse_units_3.o 
> default/source4/heimdal/lib/roken/vis_3.o 
> default/source4/heimdal/lib/roken/strlwr_3.o 
> default/source4/heimdal/lib/roken/strsep_copy_3.o 
> default/source4/heimdal/lib/roken/strsep_3.o default/source4/heimdal/lib/roke
> n/strupr_3.o default/source4/heimdal/lib/roken/strpool_3.o 
> default/source4/heimdal/lib/roken/estrdup_3.o 
> default/source4/heimdal/lib/roken/erealloc_3.o 
> default/source4/heimdal/lib/roken/simple_exec_3.o 
> default/source4/heimdal/lib/roken/strcollect_3.o 
> default/source4/heimdal/lib/roken/rtbl_3.o 
> default/source4/heimdal/lib/roken/rand_3.o 
> default/source4/heimdal/lib/roken/cloexec_3.o 
> default/source4/heimdal/lib/roken/xfree_3.o 
> default/source4/heimdal_build/replace_3.o 
> default/source4/heimdal/lib/roken/closefrom_3.o 
> default/source4/heimdal/lib/vers/print_version_128.o 
> default/source4/heimdal_build/version_128.o 
> default/source4/heimdal/lib/com_err/parse_132.o 
> default/source4/heimdal/lib/com_err/lex_132.o 
> default/source4/heimdal/lib/com_err/compile_et_132.o 
> default/lib/replace/replace_1.o -o 
> /<>/samba-4.3.3+dfsg/bin/default/source4/heimdal_build/compile_et 
> -Wl,-z,relro -Wl,--as-needed -lpthread -Wl,-no-undefined -Wl,--export-dynamic 
> -fstack-protector -L/usr/local/lib -Wl,-Bdynamic -lbsd
> default/source4/heimdal/lib/roken/vis_3.o: In function `tolower':
> /usr/include/ctype.h:216: multiple definition of `tolower'
> default/source4/heimdal/lib/roken/hex_3.o:/usr/include/ctype.h:216: first 
> defined here
> default/source4/heimdal/lib/roken/vis_3.o: In function `toupper':
> /usr/include/ctype.h:222: multiple definition of `toupper'
> default/source4/heimdal/lib/roken/hex_3.o:/usr/include/ctype.h:222: first 
> defined here
> collect2: error: ld returned 1 exit status
> default/source4/heimdal/lib/roken/vis_3.o: In function `tolower':
> /usr/include/ctype.h:216: multiple definition of `tolower'
> default/source4/heimdal/lib/roken/hex_3.o:/usr/include/ctype.h:216: first 
> defined here
> default/source4/heimdal/lib/roken/vis_3.o: In function `toupper':
> /usr/include/ctype.h:222: multiple definition of `toupper'
> default/source4/heimdal/lib/roken/hex_3.o:/usr/include/ctype.h:222: first 
> defined here
> default/source4/heimdal/lib/asn1/asn1parse_130.o: In function `tolower':
> /usr/include/ctype.h:216: 

Bug#741610: marked as done (Lock screen does not allow to enter password)

[Debian Bug Tracking System]

Your message dated Sun, 3 Jul 2016 22:07:39 +0200
with message-id <795ac48f-5616-3783-c39e-dbba5017d...@debian.org>
and subject line gdm has been superseded by gdm3
has caused the Debian Bug report #741610,
regarding Lock screen does not allow to enter password
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.)


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

Package: gdm
Version: 3.8.4-6
Severity: grave
Debian: Testing amd64
Regression: No
gnome-shell: 3.8.4-5+b1
gnome-session: 3.8.4-3

Sometimes, the lock screen does not allow to enter the password while a 
session is currently running. It completely disallows the current 
session to be recovered.
Trying to restart gdm does not help. And the only way I could find was 
to reboot my computer.

This could lead to data corruption (ie I had to make my backup again).

I found no relevant information in the various logs.

The bug seems to appear seldom and hazardously.
--- End Message ---
--- Begin Message ---
Version: 2.20.11-4+rm

gdm was last released with Debian 6.0 (squeeze) in
February 2011 and removed from Debian sid/unstable in 2011 (see
http://bugs.debian.org/613491 for details on the removal). Since
support for squeeze and squeeze-LTS has now ended, I'm closing all the
remaining bugs reported against this package.


Andreas--- End Message ---

Bug#812264: marked as pending

[Jelmer Vernooij]

tag 812264 pending
thanks

Hello,

Bug #812264 reported by you has been fixed in the Git repository. You can
see the changelog below, and you can check the diff of the fix at:

http://git.debian.org/?p=pkg-samba/samba.git;a=commitdiff;h=e23b11c

---
commit e23b11c3bccb7e463ffb51c86f3321cca63d57a9
Author: Jelmer Vernooij 
Date:   Mon Jul 4 12:23:25 2016 +

Add patch gcc_6.patch, fixing compatibility with gcc 6. Closes: #812264

diff --git a/debian/changelog b/debian/changelog
index 02eaf36..06b215c 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,3 +1,10 @@
+samba (2:4.4.4+dfsg-3) UNRELEASED; urgency=medium
+
+  * Add patch gcc_6.patch, fixing compatibility with gcc 6.
+Closes: #812264
+
+ -- Jelmer Vernooij   Mon, 04 Jul 2016 12:20:56 +
+
 samba (2:4.4.4+dfsg-2) unstable; urgency=medium
 
   * Mask samba-ad-dc.service unless needed (Closes: #828137)

Processed: Bug#812264 marked as pending

[Debian Bug Tracking System]

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

> tag 812264 pending
Bug #812264 [samba] samba: FTBFS with GCC 6: ctype.h:216: first defined here
Added tag(s) pending.
> thanks
Stopping processing here.

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

Bug#811830: marked as done (proftmb: FTBFS with GCC 6: no match for)

[Debian Bug Tracking System]

Your message dated Mon, 04 Jul 2016 13:35:14 +
with message-id 
and subject line Bug#811830: fixed in proftmb 1.1.12-5
has caused the Debian Bug report #811830,
regarding proftmb: FTBFS with GCC 6: no match for
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.)


-- 
811830: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=811830
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: proftmb
Version: 1.1.12-3
Severity: important
User: debian-...@lists.debian.org
Usertags: ftbfs-gcc-6 gcc-6-no-match

This package fails to build with GCC 6.  GCC 6 has not been released
yet, but it's expected that GCC 6 will become the default compiler for
stretch.

Note that only the first error is reported; there might be more.  You
can find a snapshot of GCC 6 in experimental.  To build with GCC 6,
you can set CC=gcc-6 CXX=g++-6 explicitly.

You may be able to find out more about this issue at
https://gcc.gnu.org/gcc-6/changes.html

> sbuild (Debian sbuild) 0.67.0 (26 Dec 2015) on dl580gen9-02.hlinux
...
> g++ -DHAVE_CONFIG_H -I. -I..   -Wdate-time -D_FORTIFY_SOURCE=2  -g -O2 
> -fstack-protector-strong -Wformat -Werror=format-security -c -o proftmb.o 
> proftmb.cpp
> sed -e 
> 's|__pkgdatadir__|/usr/share/proftmb|g;s|__datadir__|/usr/share|g;s|__PACKAGE__|proftmb|g;'
>  < proftmb_example.txt.raw > proftmb_example.txt
> In file included from HMMOutput.cpp:1:0:
> HMMOutput.h:21:46: warning: ISO C++ forbids converting a string constant to 
> 'char*' [-Wwrite-strings]
>  void DisplayArch(ostream&,Par&,uint,char* ="");
>   ^
> 
> HMMOutput.h:24:44: warning: ISO C++ forbids converting a string constant to 
> 'char*' [-Wwrite-strings]
>  void PrintEmit(ostream&,Par&,uint,char* ="");
> ^
> 
> In file included from proftmb.cpp:18:0:
> HMMOutput.h:21:46: warning: ISO C++ forbids converting a string constant to 
> 'char*' [-Wwrite-strings]
>  void DisplayArch(ostream&,Par&,uint,char* ="");
>   ^
> 
> HMMOutput.h:24:44: warning: ISO C++ forbids converting a string constant to 
> 'char*' [-Wwrite-strings]
>  void PrintEmit(ostream&,Par&,uint,char* ="");
> ^
> 
> proftmb.cpp: In function 'int Run(int, char**)':
> proftmb.cpp:166:47: error: no match for 'operator<<' (operand types are 
> 'std::basic_ostream' and 'std::ostringstream {aka 
> std::__cxx11::basic_ostringstream}')
>   if (!TS) { cerr<<"Couldn't open Output file "< strerror(errno) <  ~~^~

-> error

> 
> proftmb.cpp:166:47: note: candidate: operator<<(int, int) 
> proftmb.cpp:166:47: note:   no known conversion for argument 2 from 
> 'std::ostringstream {aka std::__cxx11::basic_ostringstream}' to 'int'
> In file included from /usr/include/c++/6/iostream:39:0,
>  from proftmb.cpp:6:
> /usr/include/c++/6/ostream:108:7: note: candidate: std::basic_ostream<_CharT, 
> _Traits>::__ostream_type& std::basic_ostream<_CharT, 
> _Traits>::operator<<(std::basic_ostream<_CharT, _Traits>::__ostream_type& 
> (*)(std::basic_ostream<_CharT, _Traits>::__ostream_type&)) [with _CharT = 
> char; _Traits = std::char_traits; std::basic_ostream<_CharT, 
> _Traits>::__ostream_type = std::basic_ostream]
>operator<<(__ostream_type& (*__pf)(__ostream_type&))
>^~~~
> 
> /usr/include/c++/6/ostream:108:7: note:   no known conversion for argument 1 
> from 'std::ostringstream {aka std::__cxx11::basic_ostringstream}' to 
> 'std::basic_ostream::__ostream_type& 
> (*)(std::basic_ostream::__ostream_type&) {aka std::basic_ostream& 
> (*)(std::basic_ostream&)}'
> /usr/include/c++/6/ostream:117:7: note: candidate: std::basic_ostream<_CharT, 
> _Traits>::__ostream_type& std::basic_ostream<_CharT, 
> _Traits>::operator<<(std::basic_ostream<_CharT, _Traits>::__ios_type& 
> (*)(std::basic_ostream<_CharT, _Traits>::__ios_type&)) [with _CharT = char; 
> _Traits = std::char_traits; std::basic_ostream<_CharT, 
> _Traits>::__ostream_type = std::basic_ostream; 
> std::basic_ostream<_CharT, _Traits>::__ios_type = std::basic_ios]
>operator<<(__ios_type& (*__pf)(__ios_type&))
>^~~~
> 
> /usr/include/c++/6/ostream:117:7: note:   no known conversion for argument 1 
> from 'std::ostringstream {aka std::__cxx11::basic_ostringstream}' to 
> 'std::basic_ostream::__ios_type& 
> (*)(std::basic_ostream::__ios_type&) {aka std::basic_ios& 
> (*)(std::basic_ios&)}'

Processed: severity of 829523 is normal

[Debian Bug Tracking System]

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

> severity 829523 normal
Bug #829523 [ftp.debian.org] RM: vpim -- RoQA; unmaintained, broken, dead 
upstream
Severity set to 'normal' from 'serious'
> thanks
Stopping processing here.

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

Bug#829427: marked as done (gimp: FTBFS in testing (undefined reference to `GEGL_IS_PARAM_SPEC_MULTILINE'))

[Debian Bug Tracking System]

Your message dated Mon, 04 Jul 2016 13:04:35 +
with message-id 
and subject line Bug#829427: fixed in gimp 2.8.16-2.1
has caused the Debian Bug report #829427,
regarding gimp: FTBFS in testing (undefined reference to 
`GEGL_IS_PARAM_SPEC_MULTILINE')
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.)


-- 
829427: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=829427
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:gimp
Version: 2.8.16-2
User: reproducible-bui...@lists.alioth.debian.org
Usertags: ftbfs
Severity: serious

Dear maintainer:

This package currently fails to build in stretch:


[...]
ranlib libapp.a
libtool: link: gcc -g -O2 -fdebug-prefix-map=/build/gimp-2.8.16=. 
-fstack-protector-strong -Wformat -Werror=format-security -Wall 
-Wdeclaration-after-statement -Wmissing-prototypes -Werror=missing-prototypes 
-Wstrict-prototypes -Wmissing-declarations -Winit-self -Wpointer-arith 
-Wold-style-definition -Wmissing-format-attribute -Wformat-security -fno-common 
-fdiagnostics-show-option -u gimp_vectors_undo_get_type -u 
gimp_vectors_mod_undo_get_type -u gimp_vectors_prop_undo_get_type -u 
gimp_curve_map_pixels -u xcf_init -u internal_procs_init -u 
gimp_plug_in_manager_restore -u gimp_pdb_compat_param_spec -u 
plug_in_icc_profile_apply_rgb -u gimp_image_map_config_get_type -Wl,-z 
-Wl,relro -o .libs/gimp-console-2.8 gimp_console_2_8-app.o 
gimp_console_2_8-batch.o gimp_console_2_8-errors.o gimp_console_2_8-language.o 
gimp_console_2_8-sanity.o gimp_console_2_8-signals.o gimp_console_2_8-tests.o 
gimp_console_2_8-unique.o gimp_console_2_8-units.o gimp_console_2_8-version.o 
gimp_console_2_8-gimp-de
 bug.o gimp_console_2_8-gimp-log.o gimp_console_2_8-main.o -Wl,--export-dynamic 
-pthread -pthread  xcf/libappxcf.a pdb/libappinternal-procs.a pdb/libapppdb.a 
plug-in/libappplug-in.a vectors/libappvectors.a core/libappcore.a 
file/libappfile.a text/libapptext.a paint/libapppaint.a 
composite/libappcomposite.a gegl/libappgegl.a config/libappconfig.a 
paint-funcs/libapppaint-funcs.a base/libappbase.a 
../libgimpconfig/.libs/libgimpconfig-2.0.so 
../libgimpmath/.libs/libgimpmath-2.0.so 
../libgimpthumb/.libs/libgimpthumb-2.0.so 
../libgimpcolor/.libs/libgimpcolor-2.0.so 
../libgimpmodule/.libs/libgimpmodule-2.0.so 
../libgimpbase/.libs/libgimpbase-2.0.so -lgdk_pixbuf-2.0 
-L/usr/lib/x86_64-linux-gnu -lpangocairo-1.0 -lpangoft2-1.0 -lpango-1.0 
-lfontconfig /usr/lib/x86_64-linux-gnu/libfreetype.so -lcairo -lgegl-0.3 
-lgegl-npd-0.3 -lgmodule-2.0 -ljson-glib-1.0 -lgio-2.0 -lbabl-0.1 -lgobject-2.0 
-lgthread-2.0 -lglib-2.0 -lm -pthread
libtool: link: gcc -g -O2 -fdebug-prefix-map=/build/gimp-2.8.16=. 
-fstack-protector-strong -Wformat -Werror=format-security -Wall 
-Wdeclaration-after-statement -Wmissing-prototypes -Werror=missing-prototypes 
-Wstrict-prototypes -Wmissing-declarations -Winit-self -Wpointer-arith 
-Wold-style-definition -Wmissing-format-attribute -Wformat-security -fno-common 
-fdiagnostics-show-option -u gimp_vectors_undo_get_type -u 
gimp_vectors_mod_undo_get_type -u gimp_vectors_prop_undo_get_type -u 
gimp_curve_map_pixels -u xcf_init -u internal_procs_init -u 
gimp_plug_in_manager_restore -u gimp_pdb_compat_param_spec -u 
plug_in_icc_profile_apply_rgb -u gimp_image_map_config_get_type -Wl,-z 
-Wl,relro -o .libs/gimp-2.8 app.o batch.o errors.o language.o sanity.o 
signals.o tests.o unique.o units.o version.o gimp-debug.o gimp-log.o main.o 
-pthread -Wl,--export-dynamic -pthread -pthread  gui/libappgui.a 
menus/libappmenus.a actions/libappactions.a dialogs/libappdialogs.a 
tools/libapptools.a display/libappdisp
 lay.a widgets/libappwidgets.a ../libgimpwidgets/.libs/libgimpwidgets-2.0.so 
-lgtk-x11-2.0 -lgdk-x11-2.0 -latk-1.0 -ldbus-glib-1 -ldbus-1 xcf/libappxcf.a 
pdb/libappinternal-procs.a pdb/libapppdb.a plug-in/libappplug-in.a 
vectors/libappvectors.a core/libappcore.a file/libappfile.a text/libapptext.a 
paint/libapppaint.a composite/libappcomposite.a gegl/libappgegl.a 
config/libappconfig.a paint-funcs/libapppaint-funcs.a base/libappbase.a 
../libgimpconfig/.libs/libgimpconfig-2.0.so 
../libgimpmath/.libs/libgimpmath-2.0.so 
../libgimpthumb/.libs/libgimpthumb-2.0.so 
../libgimpcolor/.libs/libgimpcolor-2.0.so 
../libgimpmodule/.libs/libgimpmodule-2.0.so 
../libgimpbase/.libs/libgimpbase-2.0.so -lgdk_pixbuf-2.0 
-L/usr/lib/x86_64-linux-gnu -lpangocairo-1.0 -lpangoft2-1.0 -lpango-1.0 
-lfontconfig /usr/lib/x86_64-linux-gnu/libfreetype.so -lcairo 

Bug#829431: marked as done (FTBFS: undefined reference to `GEGL_IS_PARAM_SPEC_MULTILINE')

[Debian Bug Tracking System]

Your message dated Mon, 04 Jul 2016 13:04:35 +
with message-id 
and subject line Bug#829427: fixed in gimp 2.8.16-2.1
has caused the Debian Bug report #829427,
regarding FTBFS: undefined reference to `GEGL_IS_PARAM_SPEC_MULTILINE'
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.)


-- 
829427: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=829427
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: gimp
Version: 2.8.16-2
Severity: serious
Justification: FTBFS

Hi

src:gimp in my pubilder environment FTBFS while I was trying to patch
gimp for the open CVE.

Attached is my buildlog.

Regards,
Salvatore


gimp_2.8.16-2_amd64.build.gz
Description: application/gzip
--- End Message ---
--- Begin Message ---
Source: gimp
Source-Version: 2.8.16-2.1

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

Debian distribution maintenance software
pp.
Matteo F. Vescovi  (supplier of updated gimp 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, 04 Jul 2016 14:26:58 +0200
Source: gimp
Binary: libgimp2.0 gimp gimp-data libgimp2.0-dev libgimp2.0-doc gimp-dbg
Architecture: source
Version: 2.8.16-2.1
Distribution: unstable
Urgency: medium
Maintainer: Ari Pollak 
Changed-By: Matteo F. Vescovi 
Description:
 gimp   - The GNU Image Manipulation Program
 gimp-data  - Data files for GIMP
 gimp-dbg   - Debugging symbols for GIMP
 libgimp2.0 - Libraries for the GNU Image Manipulation Program
 libgimp2.0-dev - Headers and other files for compiling plugins for GIMP
 libgimp2.0-doc - Developers' Documentation for the GIMP library
Closes: 829427
Changes:
 gimp (2.8.16-2.1) unstable; urgency=medium
 .
   * Non-maintainer upload.
   * debian/patches/: patchset updated
 - fix_GEGL_FTBFS.patch added (Closes: #829427)
   Thanks to Michael Natterer (upstream dev) for the hint.
Checksums-Sha1:
 092871822f6e213094429fc2b80ffd61f3b60325 3258 gimp_2.8.16-2.1.dsc
 7c77e3cc80884e4211ea2872f340a70ae3d752a2 41180 gimp_2.8.16-2.1.debian.tar.xz
Checksums-Sha256:
 7d2ab192c336a4585754830eb81da5593d0d916e944c93e1f10129fb17a91570 3258 
gimp_2.8.16-2.1.dsc
 47dda1bd8b3a02ff25004f940cf5e8ef46b8e42e3dd417715613bc2465a8316a 41180 
gimp_2.8.16-2.1.debian.tar.xz
Files:
 fcabe312187da7211d6ec97bb8d5b31e 3258 graphics optional gimp_2.8.16-2.1.dsc
 80a5508448da7c1cdf7613898ed6f283 41180 graphics optional 
gimp_2.8.16-2.1.debian.tar.xz

-BEGIN PGP SIGNATURE-
Comment: Debian powered!

iQJ8BAEBCgBmBQJXelZGXxSAAC4AKGlzc3Vlci1mcHJAbm90YXRpb25zLm9w
ZW5wZ3AuZmlmdGhob3JzZW1hbi5uZXRGM0REMDlGOERBODdEMURGNTA0NkM5OUIw
NjEyRjQ5NDRFQ0RDRDVBAAoJEAYS9JROzc1aeo4QAKz9KPewtwEyCqI7IS9xig0I
lMHQeokFMhwNlyf5PMX1NfqYj/4fI7KioQYOzQyOhWLgwtcSE6+R/8V8PSU2g7KA
8HbTQsmTQVIT5joqiqgLMmjl6BowZNmpQz3xkrIhn8QHgXHcEnovS2sj3876ATwb
pd6q4TrLhKsfL7ubv8dXLrvtyBLBLvT1BN+Nw12R0fQe9XYISqyziFAQ1DbRA8xD
3Fve4ii+hanGOUmEozdyDE9zVsyXgBwcmmyOcBlsJGBBef8umHOz2Vjuxu1019g8
OxUA9eyKqOUy6zfKGTZWPIC4iqCXCstj/MvqLRScanZsN4qmIleP22K7YL+Bzmfv
SgtlkW/n5qnxIiqZhLZCe5R4u6U3KJNq0zE76k/BuT+NF1MyMALmlIGC5GaNqrCp
tb0MfFP/EsClFeg/ZAK+djeJnKRzZGXwvj+ik0DxM9T+Moca36kI5f3C2hn5+KFD
xjTOwuqDRvOFPwweLdsjEL8JwzPeLvARzXjoeGD5/AV5wYdkBmQoUejp54RBh6ld
DECgonFZG+IB1PwRI7V3/pOPBqr2NO7GpoequW0WD67J8JJB6M2NFEdnkIcxVY5u
d2L0t4FPFibk+ifW34LgtB75ZwFJEMA7+07ppyQ9bTGDyrYD+5R8rcDmnQsgxS6f
X2lG+TfrXZZi4VSpao9W
=EU6O
-END PGP SIGNATURE End Message ---

Bug#822472: various haskell -dev packages are missing Built-Using attributes

[Sven Bartscher]

On Sun, 24 Apr 2016 22:13:47 +0200 Matthias Klose 
wrote:
> Package: haskell-devscripts
> Version: 0.10.2.3
> Severity: serious
> Tags: sid stretch
> 
> [I was doing a transition (icu 55 to 57), and investigating some
> build failures with link failures, some missing icu55 symbols. I
> didn't find the appropriate haskell package immediately, because it
> neither has a dependency on the icu runtime library or a Built-Using
> attribute ]
> 
> Seen with haskell-text-icu, but it looks like there are no
> Built-Using attributes for any C library used for many packages.
> Therefore filing this isssue on a package which is maintained by the
> debian haskell maintainers. Feel free to clone, reassign, ...

I'm afraid I don't understand what the problem is.
I don't see why our packages would need Build-Using fields on any C
libraries, because AFAIK all our packages that use C libraries are
dynamically linked against them and have the appropriate Depends on
them.

Are you at DebConf? If so, maybe we could meet and you explain the
problem to me.

Regards
Sven


pgpRjZ_xS9ouH.pgp
Description: Digitale Signatur von OpenPGP

Processed: severity of 828776 is serious

[Debian Bug Tracking System]

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

> # Causes package installations, e.g. of apprecommender, to fail and leaves 
> debtags package in state "half-configured".
> severity 828776 serious
Bug #828776 [debtags] UnicodeDecodeError: 'utf-8' codec can't decode byte 0xe3 
in position 349: invalid continuation byte
Severity set to 'serious' from 'important'
> thanks
Stopping processing here.

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

Processed: reassign 829560 to liblinux-prctl-perl, forcibly merging 806542 829560

[Debian Bug Tracking System]

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

> reassign 829560 liblinux-prctl-perl
Bug #829560 [src:liblinux-prctl-perl] liblinux-prctl-perl: FTBFS: Failed 2/18 
test programs. 50/510 subtests failed.
Bug reassigned from package 'src:liblinux-prctl-perl' to 'liblinux-prctl-perl'.
No longer marked as found in versions liblinux-prctl-perl/1.6.0-3.
Ignoring request to alter fixed versions of bug #829560 to the same values 
previously set
> forcemerge 806542 829560
Bug #806542 [liblinux-prctl-perl] liblinux-prctl-perl: autopkgtest failures: 
seccomp, capbset
Bug #829560 [liblinux-prctl-perl] liblinux-prctl-perl: FTBFS: Failed 2/18 test 
programs. 50/510 subtests failed.
Set Bug forwarded-to-address to 
'https://rt.cpan.org/Ticket/Display.html?id=109934'.
Severity set to 'normal' from 'serious'
Marked as found in versions liblinux-prctl-perl/1.6.0-2.
Added tag(s) confirmed.
Merged 806542 829560
> thanks
Stopping processing here.

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

Processed: Re: connection to the D-BUS daemon no longer works

[Debian Bug Tracking System]

Processing control commands:

> reassign -1 lightdm 1.18.2-1
Bug #829557 [libdbus-1-3] libdbus-1-3: connection to the D-BUS daemon no longer 
works (no /tmp/dbus-* files)
Bug reassigned from package 'libdbus-1-3' to 'lightdm'.
No longer marked as found in versions dbus/1.10.8-1.
Ignoring request to alter fixed versions of bug #829557 to the same values 
previously set
Bug #829557 [lightdm] libdbus-1-3: connection to the D-BUS daemon no longer 
works (no /tmp/dbus-* files)
Marked as found in versions lightdm/1.18.2-1.
> retitle -1 lightdm 1.18.2-1 breaks D-BUS / gconf
Bug #829557 [lightdm] libdbus-1-3: connection to the D-BUS daemon no longer 
works (no /tmp/dbus-* files)
Changed Bug title to 'lightdm 1.18.2-1 breaks D-BUS / gconf' from 'libdbus-1-3: 
connection to the D-BUS daemon no longer works (no /tmp/dbus-* files)'.

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

Bug#829557: connection to the D-BUS daemon no longer works

[Vincent Lefevre]

Control: reassign -1 lightdm 1.18.2-1
Control: retitle -1 lightdm 1.18.2-1 breaks D-BUS / gconf

On 2016-07-04 14:07:15 +0200, Vincent Lefevre wrote:
> Not sure where the bug is exactly. The dbus related packages have
> not been upgraded for several weeks, and the problem is new. In the
> recent upgrades, there was systemd (to 230-5).

Downgrading to systemd 230-3 (which was OK) doesn't solve the problem.
But downgrading lightdm / liblightdm-gobject-1-0 to 1.18.1-1 solves
it. So, the bug is there. I didn't notice it before, because it seems
that I had done a single X login after upgrading and rebooting the
machine (the problem occurs only at the second login).

To reproduce:

1. (Re)boot the machine.
2. Log in.
3. Run emacs24 from a terminal. Everything is fine.
4. Log out.
5. Log in again.
6. Run emacs24 from a terminal. This gives gconf warnings.

Note: in case this matters, my window manager is fvwm.

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

Bug#824089: marked as done (golang-github-jonboulle-clockwork-dev and golang-clockwork-dev: error when trying to install together)

[Debian Bug Tracking System]

Your message dated Mon, 04 Jul 2016 12:43:00 +
with message-id 
and subject line Bug#824089: Removed package(s) from unstable
has caused the Debian Bug report #824089,
regarding golang-github-jonboulle-clockwork-dev and golang-clockwork-dev: error 
when trying to install together
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.)


-- 
824089: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=824089
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: golang-clockwork-dev,golang-github-jonboulle-clockwork-dev
Version: golang-clockwork-dev/0.0~git20141217-1
Version: golang-github-jonboulle-clockwork-dev/0.0~git20141217-3
Severity: serious
User: trei...@debian.org
Usertags: edos-file-overwrite

Date: 2016-05-12
Architecture: amd64
Distribution: sid

Hi,

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


Selecting previously unselected package golang-src.
(Reading database ... 10961 files and directories currently installed.)
Preparing to unpack .../golang-src_2%3a1.6.1-2_amd64.deb ...
Unpacking golang-src (2:1.6.1-2) ...
Selecting previously unselected package golang-go.
Preparing to unpack .../golang-go_2%3a1.6.1-2_amd64.deb ...
Unpacking golang-go (2:1.6.1-2) ...
Selecting previously unselected package golang-clockwork-dev.
Preparing to unpack .../golang-clockwork-dev_0.0~git20141217-1_all.deb ...
Unpacking golang-clockwork-dev (0.0~git20141217-1) ...
Selecting previously unselected package golang-github-jonboulle-clockwork-dev.
Preparing to unpack 
.../golang-github-jonboulle-clockwork-dev_0.0~git20141217-3_all.deb ...
Unpacking golang-github-jonboulle-clockwork-dev (0.0~git20141217-3) ...
dpkg: error processing archive 
/var/cache/apt/archives/golang-github-jonboulle-clockwork-dev_0.0~git20141217-3_all.deb
 (--unpack):
 trying to overwrite 
'/usr/share/gocode/src/github.com/jonboulle/clockwork/example_test.go', which 
is also in package golang-clockwork-dev 0.0~git20141217-1
Processing triggers for man-db (2.7.5-1) ...
Errors were encountered while processing:
 
/var/cache/apt/archives/golang-github-jonboulle-clockwork-dev_0.0~git20141217-3_all.deb
E: Sub-process /usr/bin/dpkg returned an error code (1)


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

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

  /usr/share/gocode/src/github.com/jonboulle/clockwork/clockwork.go
  /usr/share/gocode/src/github.com/jonboulle/clockwork/clockwork_test.go
  /usr/share/gocode/src/github.com/jonboulle/clockwork/example_test.go

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

-Ralf.

PS: for more information about the detection of file overwrite errors
of this kind see http://qa.debian.org/dose/file-overwrites.html.
--- End Message ---
--- Begin Message ---
We believe that the bug you reported is now fixed; the following
package(s) have been removed from unstable:

golang-clockwork | 0.0~git20141217-1 | source
golang-clockwork-dev | 0.0~git20141217-1 | all

--- Reason ---
ROM; replaced by golang-github-jonboulle-clockwork
--

Note that the package(s) have simply been removed from the tag
database and may (or may not) still be in the pool; this is not a bug.
The package(s) will be physically removed automatically when no suite
references them (and in the case of source, when no binary references
it).  Please also remember that the changes have been done on the
master archive and will not propagate to any mirrors until the next
dinstall run at the earliest.

Bug#824089: marked as done (golang-github-jonboulle-clockwork-dev and golang-clockwork-dev: error when trying to install together)

[Debian Bug Tracking System]

Your message dated Mon, 04 Jul 2016 12:43:05 +
with message-id 
and subject line Bug#824089: Removed package(s) from unstable
has caused the Debian Bug report #824089,
regarding golang-github-jonboulle-clockwork-dev and golang-clockwork-dev: error 
when trying to install together
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.)


-- 
824089: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=824089
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: golang-clockwork-dev,golang-github-jonboulle-clockwork-dev
Version: golang-clockwork-dev/0.0~git20141217-1
Version: golang-github-jonboulle-clockwork-dev/0.0~git20141217-3
Severity: serious
User: trei...@debian.org
Usertags: edos-file-overwrite

Date: 2016-05-12
Architecture: amd64
Distribution: sid

Hi,

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


Selecting previously unselected package golang-src.
(Reading database ... 10961 files and directories currently installed.)
Preparing to unpack .../golang-src_2%3a1.6.1-2_amd64.deb ...
Unpacking golang-src (2:1.6.1-2) ...
Selecting previously unselected package golang-go.
Preparing to unpack .../golang-go_2%3a1.6.1-2_amd64.deb ...
Unpacking golang-go (2:1.6.1-2) ...
Selecting previously unselected package golang-clockwork-dev.
Preparing to unpack .../golang-clockwork-dev_0.0~git20141217-1_all.deb ...
Unpacking golang-clockwork-dev (0.0~git20141217-1) ...
Selecting previously unselected package golang-github-jonboulle-clockwork-dev.
Preparing to unpack 
.../golang-github-jonboulle-clockwork-dev_0.0~git20141217-3_all.deb ...
Unpacking golang-github-jonboulle-clockwork-dev (0.0~git20141217-3) ...
dpkg: error processing archive 
/var/cache/apt/archives/golang-github-jonboulle-clockwork-dev_0.0~git20141217-3_all.deb
 (--unpack):
 trying to overwrite 
'/usr/share/gocode/src/github.com/jonboulle/clockwork/example_test.go', which 
is also in package golang-clockwork-dev 0.0~git20141217-1
Processing triggers for man-db (2.7.5-1) ...
Errors were encountered while processing:
 
/var/cache/apt/archives/golang-github-jonboulle-clockwork-dev_0.0~git20141217-3_all.deb
E: Sub-process /usr/bin/dpkg returned an error code (1)


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

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

  /usr/share/gocode/src/github.com/jonboulle/clockwork/clockwork.go
  /usr/share/gocode/src/github.com/jonboulle/clockwork/clockwork_test.go
  /usr/share/gocode/src/github.com/jonboulle/clockwork/example_test.go

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

-Ralf.

PS: for more information about the detection of file overwrite errors
of this kind see http://qa.debian.org/dose/file-overwrites.html.
--- End Message ---
--- Begin Message ---
Version: 0.0~git20141217-1+rm

Dear submitter,

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

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

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

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

Debian distribution maintenance software
pp.
Paul Richards Tagliamonte (the ftpmaster behind the curtain)--- End Message ---

Bug#824089: RM: golang-clockwork-dev -- ROM; replaced by golang-github-jonboulle-clockwork

[Paul Tagliamonte]

Package: ftp.debian.org
Severity: important
thanks

golang-clockwork-dev was replaced by something with a fancier source and
binary name.

I'll remove this in a minute.

 Paul


signature.asc
Description: PGP signature

Bug#811709: marked as done (adun.app: FTBFS with GCC 6: unknown type name)

[Debian Bug Tracking System]

Your message dated Mon, 04 Jul 2016 12:33:50 +
with message-id 
and subject line Bug#811709: fixed in adun.app 0.81-9
has caused the Debian Bug report #811709,
regarding adun.app: FTBFS with GCC 6: unknown type name
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.)


-- 
811709: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=811709
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: adun.app
Version: 0.81-8
Severity: important
User: debian-...@lists.debian.org
Usertags: ftbfs-gcc-6 gcc-6-unknown-type-name

This package fails to build with GCC 6.  GCC 6 has not been released
yet, but it's expected that GCC 6 will become the default compiler for
stretch.

Note that only the first error is reported; there might be more.  You
can find a snapshot of GCC 6 in experimental.  To build with GCC 6,
you can set CC=gcc-6 CXX=g++-6 explicitly.

You may be able to find out more about this issue at
https://gcc.gnu.org/gcc-6/changes.html

> sbuild (Debian sbuild) 0.67.0 (26 Dec 2015) on dl580gen9-02.hlinux
...
>   -MMD -MP -Wdate-time -D_FORTIFY_SOURCE=2 -DMT_VERSION=\"3.0.1\" 
> -DGNUSTEP -DGNUSTEP_BASE_LIBRARY=1 -DGNU_GUI_LIBRARY=1 -DGNU_RUNTIME=1 
> -DGNUSTEP_BASE_LIBRARY=1 -fno-strict-aliasing -fexceptions -fobjc-exceptions 
> -D_NATIVE_OBJC_EXCEPTIONS -pthread -fPIC -Wall -DGSWARN -DGSDIAGNOSE 
> -Wno-import -g -O2 -g -O2 -fstack-protector-strong -Wformat 
> -Werror=format-security -fgnu-runtime -DUNSAFEENV -D none 
> -fconstant-string-class=NSConstantString -march=athlon64 -I./derived_src -I. 
> -I/usr/local/include/GNUstep -I/usr/include/GNUstep \
>-o obj/MolTalk.obj/MTResidue.m.o
> MTResidue.m: In function '-[MTResidue mutateTo:]':
> MTResidue.m:653:2: error: unknown type name 'MTResidue'
>   MTResidue *res2 = [p_res copy];
>   ^
> 
> MTResidue.m:653:2: note: use 'struct' keyword to refer to the type
> MTResidue.m:653:20: warning: initialization from incompatible pointer type 
> [-Wincompatible-pointer-types]
>   MTResidue *res2 = [p_res copy];
> ^
> 
> MTResidue.m:654:11: error: request for member 'atomarr' in something not a 
> structure or union
>   l = [res2->atomarr count];
>^~
> 
> MTResidue.m:655:2: warning: invalid receiver type 'int *'
>   [res2 translateBy: tr1];  // to origin
>   ^
> 
> MTResidue.m:657:2: warning: invalid receiver type 'int *'
>   [res2 rotateBy: rot2];  // on  Z-axis
>   ^
> 
> MTResidue.m:658:2: warning: invalid receiver type 'int *'
>   [res2 rotateBy: rotZ];  // adjust rotation around Z axis
>   ^
> 
> MTResidue.m:659:2: warning: invalid receiver type 'int *'
>   [res2 rotateBy: rot1];  // from Z-axis to orientation 1
>   ^
> 
> MTResidue.m:660:2: warning: invalid receiver type 'int *'
>   [res2 translateBy: tr2];  // to location 1
>   ^
> 
> MTResidue.m:663:14: error: request for member 'atomarr' in something not a 
> structure or union
>atm = [res2->atomarr objectAtIndex: i];
--- End Message ---
--- Begin Message ---
Source: adun.app
Source-Version: 0.81-9

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

Debian distribution maintenance software
pp.
Gert Wollny  (supplier of updated adun.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: SHA256

Format: 1.8
Date: Mon, 04 Jul 2016 10:00:50 +
Source: adun.app
Binary: adun.app adun-core adun.app-dbg
Architecture: source amd64
Version: 0.81-9
Distribution: unstable
Urgency: medium
Maintainer: Debian Med Packaging Team 

Changed-By: Gert Wollny 
Description:
 adun-core  - Molecular Simulator
 adun.app   - Molecular Simulator for GNUstep (GUI)
 adun.app-dbg - Molecular Simulator for GNUstep (debugging symbols)
Closes: 811709
Changes:
 adun.app (0.81-9) unstable; urgency=medium
 .
   [ Gert Wollny ]
   * Team upload.
   * d/p/gcc-6: Add patch to fix compilation with gcc-6, Closes: #811709
   * cme fix dpkg-control
   * d/control: Change browse URL to https
 .
   [ Andreas 

Bug#829582: does not depend on taskwarrior

[Thadeu Lima de Souza Cascardo]

Package: tasksh
Version: 1.0.0-1
Severity: serious

tasksh does not work without taskwarrior being installed. It should
Depend on taskwarrior.

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

Kernel: Linux 4.6.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 tasksh depends on:
ii  libc6   2.22-13
ii  libgcc1 1:6.1.1-8
ii  libstdc++6  6.1.1-8

tasksh recommends no packages.

tasksh suggests no packages.

-- no debconf information

Processed: Re: Bug#829138: liblist-moreutils-perl: tries to load code from cwd

[Debian Bug Tracking System]

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

> clone 829138 -1
Bug #829138 [liblist-moreutils-perl] liblist-moreutils-perl: tries to load code 
from cwd
Bug 829138 cloned as bug 829578
> retitle -1 perl: XSLoader tries to load code from '(eval 1)/' when called 
> inside a string eval
Bug #829578 [liblist-moreutils-perl] liblist-moreutils-perl: tries to load code 
from cwd
Changed Bug title to 'perl: XSLoader tries to load code from '(eval 1)/' when 
called inside a string eval' from 'liblist-moreutils-perl: tries to load code 
from cwd'.
> reassign -1 perl 5.22.2-1
Bug #829578 [liblist-moreutils-perl] perl: XSLoader tries to load code from 
'(eval 1)/' when called inside a string eval
Bug reassigned from package 'liblist-moreutils-perl' to 'perl'.
No longer marked as found in versions liblist-moreutils-perl/0.413-1.
Ignoring request to alter fixed versions of bug #829578 to the same values 
previously set
Bug #829578 [perl] perl: XSLoader tries to load code from '(eval 1)/' when 
called inside a string eval
Marked as found in versions perl/5.22.2-1.
> tag -1 patch fixed-upstream
Bug #829578 [perl] perl: XSLoader tries to load code from '(eval 1)/' when 
called inside a string eval
Added tag(s) fixed-upstream and patch.
> severity -1 important
Bug #829578 [perl] perl: XSLoader tries to load code from '(eval 1)/' when 
called inside a string eval
Severity set to 'important' from 'serious'
> tag 829138 patch
Bug #829138 [liblist-moreutils-perl] liblist-moreutils-perl: tries to load code 
from cwd
Added tag(s) patch.
> thanks
Stopping processing here.

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

Bug#829138: liblist-moreutils-perl: tries to load code from cwd

[Niko Tyni]

clone 829138 -1
retitle -1 perl: XSLoader tries to load code from '(eval 1)/' when called 
inside a string eval
reassign -1 perl 5.22.2-1
tag -1 patch fixed-upstream
severity -1 important
tag 829138 patch
thanks

On Thu, Jun 30, 2016 at 11:28:51PM +0200, Jakub Wilk wrote:
> Package: liblist-moreutils-perl
> Version: 0.413-1+b1
> Tags: security
> Control: affects -1 + check-all-the-things
> 
> List::MoreUtils tries to load code from a subdirectory of the current
> working directory. This could lead to execution of arbitrary code if cwd is
> untrusted.

Thanks for the report.

As discussed in the upstream ticket, the root cause is XSLoader, which
uses caller() information to locate the .so file to load. This can be
incorrect if XSLoader::load() is called in a string eval.

  https://rt.cpan.org/Ticket/Display.html?id=115808

I'm cloning a separate bug against perl about this; XSLoader
is already fixed upstream with

 http://perl5.git.perl.org/perl.git/commitdiff/08e3451d7

There's a simple workaround for List::MoreUtils in the upstream ticket
included below. I think we should apply this in any case as it improves
the diagnostics.

I'm setting the severity of the XSLoader bug to 'important';
the circumstances are rare enough that I don't think it should be
release-critical at this point as long as List-MoreUtils gets patched.

I'll still try to fix it in perl soon, and we can revisit this if other
packages turn out to be affected.

diff -rup List-MoreUtils-0.415-sba79Z-orig/lib/List/MoreUtils/XS.pm 
List-MoreUtils-0.415-sba79Z/lib/List/MoreUtils/XS.pm
--- List-MoreUtils-0.415-sba79Z-orig/lib/List/MoreUtils/XS.pm   2016-05-01 
09:47:00.0 -0700
+++ List-MoreUtils-0.415-sba79Z/lib/List/MoreUtils/XS.pm2016-07-03 
11:02:41.0 -0700
@@ -13,6 +13,7 @@ BEGIN
 # Load the XS at compile-time so that redefinition warnings will be
 # thrown correctly if the XS versions of part or indexes loaded
 my $ldr = <

Processed: connection to the D-BUS daemon no longer works

[Debian Bug Tracking System]

Processing control commands:

> severity -1 grave
Bug #829557 [libdbus-1-3] libdbus-1-3: connection to the D-BUS daemon no longer 
works (no /tmp/dbus-* files)
Severity set to 'grave' from 'important'

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

Processed (with 1 error): Re: Bug#829560: liblinux-prctl-perl: FTBFS: Failed 2/18 test programs. 50/510 subtests failed.

[Debian Bug Tracking System]

Processing control commands:

> forcemerge 806542 829560
Bug #806542 [liblinux-prctl-perl] liblinux-prctl-perl: autopkgtest failures: 
seccomp, capbset
Unable to merge bugs because:
package of #829560 is 'src:liblinux-prctl-perl' not 'liblinux-prctl-perl'
Failed to forcibly merge 806542: Did not alter merged bugs.


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

Bug#829560: liblinux-prctl-perl: FTBFS: Failed 2/18 test programs. 50/510 subtests failed.

[Salvatore Bonaccorso]

Control: forcemerge 806542 829560
Hi

Okay looks it's the same as #806542. So I think it's not actually RC
but should be catched in some way as well for the reproducible builds
setup.

Regards,
Salvatore

Bug#829560: liblinux-prctl-perl: FTBFS: Failed 2/18 test programs. 50/510 subtests failed.

[Salvatore Bonaccorso]

Hi Chris,

On Mon, Jul 04, 2016 at 11:56:58AM +0200, Chris Lamb wrote:
> Source: liblinux-prctl-perl
> Version: 1.6.0-3
> Severity: serious
> Justification: fails to build from source
> User: reproducible-bui...@lists.alioth.debian.org
> Usertags: ftbfs
> X-Debbugs-Cc: reproducible-bui...@lists.alioth.debian.org
> 
> Dear Maintainer,
> 
> liblinux-prctl-perl fails to build from source in unstable/amd64:
[...]

I currently cannot replicate this in my usual pbuilder build
environment (up to date).

I will try to so with an sbuild setup though next.

Regards,
Salvatore

Bug#811825: Patch

[u]

Hi!

> On 07/02/2016 10:37 AM, u wrote:
>> Here's a debdiff which fixes this bug.
>> I've tested building in a chroot using gcc-6.
>>
>> One might want to consider setting up a Git repository for this package :)
> 
> Thanks!

Actually, it did not build correctly, I was a bit too optimistic here.
The error seemed to be that:

/usr/include/c++/6/bits/stl_iterator.h:304:5: note:   template argument
deduction/substitution failed:
ppl_pips.cc:561:51: note:   'std::ostream {aka
std::basic_ostream}' is not derived from 'const
std::reverse_iterator<_Iterator>'
   if (output_stream_p && *output_stream_p != std::cout)
   ^~~~
In file included from /usr/include/c++/6/bits/stl_algobase.h:64:0,
 from /usr/include/c++/6/bits/char_traits.h:39,
 from /usr/include/c++/6/ios:40,
 from /usr/include/c++/6/ostream:38,
 from /usr/include/c++/6/iostream:39,
 from ../../src/ppl.hh:746,
 from ppl_pips.cc:34:
/usr/include/c++/6/bits/stl_pair.h:376:5: note: candidate:
template constexpr bool std::operator!=(const
std::pair<_T1, _T2>&, const std::pair<_T1, _T2>&)
 operator!=(const pair<_T1, _T2>& __x, const pair<_T1, _T2>& __y)

So in a second try I also applied upstream commit
832e1e5b0c48d89588b4d2c20150473a308e3298 but i still get an error which
I've not yet completely identified.

> Indeed the best of all would be to upgrade to PPL 1.2.

Agreed. No idea if the maintainer plans on doing so :)

Cheers!

Processed: cloning 829500, reassign -1 to src:aide, severity of -1 is serious

[Debian Bug Tracking System]

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

> clone 829500 -1
Bug #829500 [libaudit-dev] undefined reference to `capng_have_capability'
Bug 829500 cloned as bug 829575
> reassign -1 src:aide 0.16~b1-1
Bug #829575 [libaudit-dev] undefined reference to `capng_have_capability'
Bug reassigned from package 'libaudit-dev' to 'src:aide'.
No longer marked as found in versions audit/1:2.6.1-1.
Ignoring request to alter fixed versions of bug #829575 to the same values 
previously set
Bug #829575 [src:aide] undefined reference to `capng_have_capability'
Marked as found in versions aide/0.16~b1-1.
> severity -1 serious
Bug #829575 [src:aide] undefined reference to `capng_have_capability'
Severity set to 'serious' from 'important'
> thanks
Stopping processing here.

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

Processed: fixed 811939 in 0.112-1

[Debian Bug Tracking System]

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

> fixed 811939 0.112-1
Bug #811939 [pesign] pesign: FTBFS with GCC 6: defined but not used
Marked as fixed in versions pesign/0.112-1.
> thanks
Stopping processing here.

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

Bug#828819: intel-microcode: i7-6500U doesn't boot in 4/5 cases with 3.20160607.1

[Henrique de Moraes Holschuh]

Mike,

After the BIOS update, do you have any "microcode" entries in the kernel
log?  Could you send them to the bug report?

-- 
  "One disk to rule them all, One disk to find them. One disk to bring
  them all and in the darkness grind them. In the Land of Redmond
  where the shadows lie." -- The Silicon Valley Tarot
  Henrique Holschuh

Bug#828172: marked as done (python-asdf: FTBFS: asdf/tags/transform/tests/test_transform.py:57: AssertionError)

[Debian Bug Tracking System]

Your message dated Mon, 04 Jul 2016 10:39:35 +
with message-id 
and subject line Bug#828172: fixed in python-asdf 1.1.0-3
has caused the Debian Bug report #828172,
regarding python-asdf: FTBFS: asdf/tags/transform/tests/test_transform.py:57: 
AssertionError
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.)


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

Dear Maintainer,

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

  [..]

  asdf/tags/wcs/tests/test_wcs.py::test_frames SKIPPED
  asdf/tests/test_asdftypes.py::test_custom_tag PASSED
  asdf/tests/test_asdftypes.py::test_version_mismatch PASSED
  asdf/tests/test_asdftypes.py::test_versioned_writing PASSED
  asdf/tests/test_asdftypes.py::test_longest_match PASSED
  asdf/tests/test_compression.py::test_invalid_compression PASSED
  asdf/tests/test_compression.py::test_zlib PASSED
  asdf/tests/test_compression.py::test_bzp2 PASSED
  asdf/tests/test_fits_embed.py::test_embed_asdf_in_fits_file PASSED
  
asdf/tests/test_fits_embed.py::test_embed_asdf_in_fits_file_anonymous_extensions
 PASSED
  asdf/tests/test_fits_embed.py::test_create_in_tree_first PASSED
  asdf/tests/test_generic_io.py::test_mode_fail PASSED
  asdf/tests/test_generic_io.py::test_open PASSED
  asdf/tests/test_generic_io.py::test_path[tree0] PASSED
  asdf/tests/test_generic_io.py::test_path[tree1] PASSED
  asdf/tests/test_generic_io.py::test_open2[tree0] PASSED
  asdf/tests/test_generic_io.py::test_open2[tree1] PASSED
  asdf/tests/test_generic_io.py::test_open_fail PASSED
  asdf/tests/test_generic_io.py::test_open_fail2 PASSED
  asdf/tests/test_generic_io.py::test_open_fail4 PASSED
  asdf/tests/test_generic_io.py::test_io_open[tree0] PASSED
  asdf/tests/test_generic_io.py::test_io_open[tree1] PASSED
  asdf/tests/test_generic_io.py::test_bytes_io[tree0] PASSED
  asdf/tests/test_generic_io.py::test_bytes_io[tree1] PASSED
  asdf/tests/test_generic_io.py::test_streams[tree0] PASSED
  asdf/tests/test_generic_io.py::test_streams[tree1] PASSED
  asdf/tests/test_generic_io.py::test_streams2 PASSED
  asdf/tests/test_generic_io.py::test_urlopen[tree0] SKIPPED
  asdf/tests/test_generic_io.py::test_urlopen[tree1] SKIPPED
  asdf/tests/test_generic_io.py::test_http_connection[tree0] SKIPPED
  asdf/tests/test_generic_io.py::test_http_connection[tree1] SKIPPED
  asdf/tests/test_generic_io.py::test_http_connection_range[tree0] SKIPPED
  asdf/tests/test_generic_io.py::test_http_connection_range[tree1] SKIPPED
  asdf/tests/test_generic_io.py::test_exploded_filesystem[tree0] PASSED
  asdf/tests/test_generic_io.py::test_exploded_filesystem[tree1] PASSED
  asdf/tests/test_generic_io.py::test_exploded_filesystem_fail[tree0] PASSED
  asdf/tests/test_generic_io.py::test_exploded_filesystem_fail[tree1] PASSED
  asdf/tests/test_generic_io.py::test_exploded_http[tree0] SKIPPED
  asdf/tests/test_generic_io.py::test_exploded_http[tree1] SKIPPED
  asdf/tests/test_generic_io.py::test_exploded_stream_write PASSED
  asdf/tests/test_generic_io.py::test_exploded_stream_read PASSED
  asdf/tests/test_generic_io.py::test_unicode_open PASSED
  asdf/tests/test_generic_io.py::test_invalid_obj PASSED
  asdf/tests/test_generic_io.py::test_nonseekable_file PASSED
  asdf/tests/test_generic_io.py::test_relative_uri PASSED
  asdf/tests/test_generic_io.py::test_arbitrary_file_object PASSED
  asdf/tests/test_generic_io.py::test_check_bytes PASSED
  asdf/tests/test_generic_io.py::test_truncated_reader PASSED
  asdf/tests/test_low_level.py::test_no_yaml_end_marker PASSED
  asdf/tests/test_low_level.py::test_no_final_newline PASSED
  asdf/tests/test_low_level.py::test_no_asdf_header PASSED
  asdf/tests/test_low_level.py::test_no_asdf_blocks PASSED
  asdf/tests/test_low_level.py::test_invalid_source PASSED
  asdf/tests/test_low_level.py::test_empty_file PASSED
  asdf/tests/test_low_level.py::test_not_asdf_file PASSED
  asdf/tests/test_low_level.py::test_junk_file PASSED
  asdf/tests/test_low_level.py::test_block_mismatch PASSED
  asdf/tests/test_low_level.py::test_block_header_too_small PASSED
  asdf/tests/test_low_level.py::test_file_already_closed PASSED
  asdf/tests/test_low_level.py::test_external_block PASSED
  asdf/tests/test_low_level.py::test_external_block_non_url PASSED
  

Bug#660206: marked as done (mysql-server: client cannot authenticate)

[Debian Bug Tracking System]

Your message dated Sun, 3 Jul 2016 11:46:27 +0200
with message-id 
and subject line closing bugs reported against ancient mysql-5.1
has caused the Debian Bug report #660206,
regarding mysql-server: client cannot authenticate
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.)


-- 
660206: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=660206
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: mysql-server
Version: 5.1.58-1
Severity: important

rails 1.2.6 app cannot authenticate and received following error:

#08S01Bad handshake

It seems this may be the following bug in  the upstream:
http://bugs.mysql.com/bug.php?id=61222



-- System Information:
Debian Release: wheezy/sid
  APT prefers testing
  APT policy: (900, 'testing'), (800, 'unstable')
Architecture: amd64 (x86_64)

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

Versions of packages mysql-server depends on:
ii  mysql-server-5.1  5.1.58-1

mysql-server recommends no packages.

mysql-server suggests no packages.

-- no debconf information


--- End Message ---
--- Begin Message ---
This bug has been reported against an ancient version of mysql (5.1),
that was last released with Debian 6.0 (squeeze). But even squeeze-lts
has now reached end-of-life and is no longer supported.
The bug is assumed to be fixed (or no longer relevant) in newer mysql
(or mariadb) releases and therefore I'm closing this report now. If the
problem is still reproducible in the currently supported versions
(mysql-5.6/mysql-5.7), feel free to provide more information, reopen
and reassign this bug report.

Andreas--- End Message ---

Bug#829542: marked as done (dpkg-dev: dpkg-buildpackage misses import of Dpkg::Control::Info)

[Debian Bug Tracking System]

Your message dated Mon, 04 Jul 2016 10:20:14 +
with message-id 
and subject line Bug#829542: fixed in dpkg 1.18.9
has caused the Debian Bug report #829542,
regarding dpkg-dev: dpkg-buildpackage misses import of Dpkg::Control::Info
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.)


-- 
829542: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=829542
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: dpkg-dev
Version: 1.18.8
Severity: normal

dpkg-buldpackage -B reports:

Can't locate object method "new" via package "Dpkg::Control::Info" (perhaps you 
forgot to load "Dpkg::Control::Info"?) at /usr/bin/dpkg-buildpackage line 728.

And indeed, adding 

use Dpkg::Control::Info;

to the header fixes this problem.  Please provide an official fixed version.
-- 
Thanks,
Feri.
--- End Message ---
--- Begin Message ---
Source: dpkg
Source-Version: 1.18.9

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

Debian distribution maintenance software
pp.
Guillem Jover  (supplier of updated dpkg 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, 04 Jul 2016 09:23:13 +0200
Source: dpkg
Binary: libdpkg-dev dpkg dpkg-dev libdpkg-perl dselect
Architecture: source
Version: 1.18.9
Distribution: unstable
Urgency: medium
Maintainer: Dpkg Developers 
Changed-By: Guillem Jover 
Description:
 dpkg   - Debian package management system
 dpkg-dev   - Debian package development tools
 dselect- Debian package management front-end
 libdpkg-dev - Debian package management static library
 libdpkg-perl - Dpkg perl modules
Closes: 829542 829546
Changes:
 dpkg (1.18.9) unstable; urgency=medium
 .
   * Require Dpkg::Control::Info in dpkg-buildpackage.
 Initially reported by Helmut Grohne .
 Regression introduced in dpkg 1.18.8. Closes: #829542
   * Documentation:
 - Fix user configuration filename in dpkg-buildpackage(1).
   Thanks to Sven Joachim . Closes: #829546
Checksums-Sha1:
 8c1af5c8a2b217f42631485bda72929175b07671 2026 dpkg_1.18.9.dsc
 3624ad729afa96674d85e48414c76ffd052a46d1 4632900 dpkg_1.18.9.tar.xz
Checksums-Sha256:
 6087a82d1ae6f24d48d5ea84da66384e84a9089699606e48748a46bcb1af5c7d 2026 
dpkg_1.18.9.dsc
 86ac4af917e9e75eb9b6c947a0a11439d1de32f72237413f7ddab17f77082093 4632900 
dpkg_1.18.9.tar.xz
Files:
 1b18fe3c784459583a93dd9bd64045b2 2026 admin required dpkg_1.18.9.dsc
 8a28f8cd4b85d10a8a23e6428dd41c41 4632900 admin required dpkg_1.18.9.tar.xz

-BEGIN PGP SIGNATURE-
Version: GnuPG v2

iQIcBAEBCgAGBQJXehgHAAoJELlyvz6krlejQDwP/jVYAesAvxIXxiassqer1lVT
R398WZ3fMmbQSUXQUtiSoTcW2kHqYSBK/4XReuWoBvlNK924WQj/O8PPSW6PT3va
S+vIkIUL5oqY9w0Wk0+iqQItGPXouEF18/bz2AmaYRb9kRManSQHHoWawdQ8jSEu
88858uUVKxiY+I6QFUPPH8AtT1EfqLzwls2tqZNeKrLcoMH5c22/uTdRoMAie4w+
SRG1U1LBn6BJc4vLKwFeDIjEgbk6Bu4+0fRdVjHnkxF8odjpTzg0AUJDzx0Vt5WU
FNgWXpbvPykFSjlKk5CfLpsyaSvwLKN2hhjQRfeplYXo4JgKmiKOScJNc0rUYnNv
kjnqIgn4nyj/U78+nnj6NYOmePe88Sum/PnCZe8EDHuk9eqQ6h0ry62A1ppzqFAJ
m6xmSU9tI04D3Ni87pxX0dXiExraD80qZ8ksgfXJqlIP+TArWqOkKU7qABe4fepI
OKwze/+8FYQM1c/hZCbBSa8z9ICyX8D8QO/aTwGtR1F+0G6OGzKFsajSHsUji2Ut
+wKe2cAf9ILM5QnilrBp3W/c6gy4wwlIJZiY98DZ9h9zwAUjxFVNtZR5TaubsjFz
Ed6njoGAPljK3EqsGNq2Yi0h5bTG9R7XYlLPjyv7E5yzZdo6QOG38jA/5Z0S80lE
0IogaAt3w1gagFThGYVS
=P6m+
-END PGP SIGNATURE End Message ---

Bug#811619: marked as done (FTBFS with GCC 6: cannot convert x to y)

[Debian Bug Tracking System]

Your message dated Mon, 04 Jul 2016 10:20:27 +
with message-id 
and subject line Bug#811619: fixed in gbgoffice 1.4-9
has caused the Debian Bug report #811619,
regarding FTBFS with GCC 6: cannot convert x to y
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.)


-- 
811619: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=811619
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: gbgoffice
Version: 1.4-8
Severity: important
User: debian-...@lists.debian.org
Usertags: ftbfs-gcc-6 gcc-6-cannot-convert

This package fails to build with GCC 6.  GCC 6 has not been released
yet, but it's expected that GCC 6 will become the default compiler for
stretch.

Note that only the first error is reported; there might be more.  You
can find a snapshot of GCC 6 in experimental.  To build with GCC 6,
you can set CC=gcc-6 CXX=g++-6 explicitly.

> sbuild (Debian sbuild) 0.67.0 (26 Dec 2015) on dl580gen9-02.hlinux
...
> g++ -DHAVE_CONFIG_H -I.  -DDATA_DIR_CONFIG=\"/usr/share/bgoffice/\"   
> -std=c++11 -pthread -I/usr/include/gtkmm-2.4 
> -I/usr/lib/x86_64-linux-gnu/gtkmm-2.4/include -I/usr/include/atkmm-1.6 
> -I/usr/include/gtk-unix-print-2.0 -I/usr/include/gtk-2.0 
> -I/usr/include/gdkmm-2.4 -I/usr/lib/x86_64-linux-gnu/gdkmm-2.4/include 
> -I/usr/include/giomm-2.4 -I/usr/lib/x86_64-linux-gnu/giomm-2.4/include 
> -I/usr/include/pangomm-1.4 -I/usr/lib/x86_64-linux-gnu/pangomm-1.4/include 
> -I/usr/include/glibmm-2.4 -I/usr/lib/x86_64-linux-gnu/glibmm-2.4/include 
> -I/usr/include/cairomm-1.0 -I/usr/lib/x86_64-linux-gnu/cairomm-1.0/include 
> -I/usr/include/sigc++-2.0 -I/usr/lib/x86_64-linux-gnu/sigc++-2.0/include 
> -I/usr/include/gtk-2.0 -I/usr/lib/x86_64-linux-gnu/gtk-2.0/include 
> -I/usr/include/gio-unix-2.0/ -I/usr/include/cairo -I/usr/include/pango-1.0 
> -I/usr/include/atk-1.0 -I/usr/include/cairo -I/usr/include/pixman-1 
> -I/usr/include/libpng12 -I/usr/include/gdk-pixbuf-2.0 -I/usr/include/libpng12 
> -I/usr/include/pango-
> 1.0 -I/usr/include/harfbuzz -I/usr/include/pango-1.0 -I/usr/include/glib-2.0 
> -I/usr/lib/x86_64-linux-gnu/glib-2.0/include -I/usr/include/freetype2  -Wall 
> -g -O2 -MT translator_manager.o -MD -MP -MF .deps/translator_manager.Tpo -c 
> -o translator_manager.o translator_manager.cpp
> translator_manager.cpp: In member function 'Translator* 
> TranslatorManager::getTestDictionaryObject(int, int)':
> translator_manager.cpp:179:10: error: cannot convert 'bool' to 'Translator*' 
> in return
>return false;
>   ^
> 
> translator_manager.cpp:183:10: error: cannot convert 'bool' to 'Translator*' 
> in return
>return false;
>   ^
> 
> Makefile:424: recipe for target 'translator_manager.o' failed
> make[3]: *** [translator_manager.o] Error 1

-- 
Martin Michlmayr
Linux for HPE Helion, Hewlett Packard Enterprise
--- End Message ---
--- Begin Message ---
Source: gbgoffice
Source-Version: 1.4-9

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

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

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

Debian distribution maintenance software
pp.
Damyan Ivanov  (supplier of updated gbgoffice 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, 04 Jul 2016 10:02:23 +
Source: gbgoffice
Binary: gbgoffice
Architecture: source
Version: 1.4-9
Distribution: unstable
Urgency: medium
Maintainer: Damyan Ivanov 
Changed-By: Damyan Ivanov 
Closes: 480003 811619
Description: 
 gbgoffice  - bgoffice dictionary frontend (GTK2)
Changes:
 gbgoffice (1.4-9) unstable; urgency=medium
 .
   * Add Vcs-* flags, reporitory uploaded to collab-maint
   * rules: turn on all hardening options
   * fix return value of TranslatorManager::getTestDictionaryObject when the
 file is not good
 - fixes compilation with gcc-6; Closes: #811619
   * patch exam function to not crash when no siutable dictionaries are present
 (Closes: 480003)
   * drop README.source pointing to quilt docs
   * bump copyright years of debian/*
   * drop the menu file from the package
   

Processed: your mail

[Debian Bug Tracking System]

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

> severity 802522 normal
Bug #802522 {Done: Debian FTP Masters } 
[mediawiki-extensions-ldapauth] mediawiki-extensions-ldapauth: Ldap auth is 
broken when used with php5 > 5.6.11
Severity set to 'normal' from 'grave'
> reassign 802522 ftp.debian.org
Bug #802522 {Done: Debian FTP Masters } 
[mediawiki-extensions-ldapauth] mediawiki-extensions-ldapauth: Ldap auth is 
broken when used with php5 > 5.6.11
Bug reassigned from package 'mediawiki-extensions-ldapauth' to 'ftp.debian.org'.
No longer marked as found in versions mediawiki-extensions/3.7.
No longer marked as fixed in versions 3.7+rm.
>
End of message, stopping processing here.

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

Bug#825845: mrpt: FTBFS on big-endian systems, with test suite errors

[Gianfranco Costamagna]

Hi,


>lease, find the workaround (not solution!) commit in [1]. Please, if

>possible, apply it directly over the current v1.4.0 Debian package to
>unblock building in big endian platforms. It would be great if you
>could sponsor the update in Debian, not only in Ubuntu.
>
>If I find spare time to work in a real solution, I'll contact you just
>in case you could help me testing the patches in porter machines...


I can sponsor whatever you give me, a dsc, a tarball of debian packaging 
directory,
whatever (a git snapshot)


Right now, I applied the two commits as patches, and the fix for breaks+replaces
fields, and I uploaded it in Ubuntu (to check if everything is correct)

I called it ~build2 [1], so on the Debian upload it will be overridden 
automatically
by the auto import robot


here [2]

[1] https://launchpad.net/ubuntu/+source/mrpt/1:1.4.0-1build2

[2] 
http://launchpadlibrarian.net/270793330/mrpt_1%3A1.4.0-1build1_1%3A1.4.0-1build2.diff.gz

I'm looking the build logs, if you can give me a dsc file I'll sponsor it in a 
matter of minutes.

If you don't change the version, just send me a tarball of the debian 
directory, it should be enough for me!

thanks for "fixing" :)

Gianfranco

Bug#829560: liblinux-prctl-perl: FTBFS: Failed 2/18 test programs. 50/510 subtests failed.

[Chris Lamb]

Source: liblinux-prctl-perl
Version: 1.6.0-3
Severity: serious
Justification: fails to build from source
User: reproducible-bui...@lists.alioth.debian.org
Usertags: ftbfs
X-Debbugs-Cc: reproducible-bui...@lists.alioth.debian.org

Dear Maintainer,

liblinux-prctl-perl fails to build from source in unstable/amd64:

  [..]

  #   at t/capbset.t line 16.
  #  got: '0'
  # expected: '1'
  
  #   Failed test 'Checking whether mac_override is in the bounding set'
  #   at t/capbset.t line 16.
  #  got: '0'
  # expected: '1'
  
  #   Failed test 'Checking whether net_admin is in the bounding set'
  #   at t/capbset.t line 16.
  #  got: '0'
  # expected: '1'
  
  #   Failed test 'Checking whether net_broadcast is in the bounding set'
  #   at t/capbset.t line 16.
  #  got: '0'
  # expected: '1'
  
  #   Failed test 'Checking whether syslog is in the bounding set'
  #   at t/capbset.t line 16.
  #  got: '0'
  # expected: '1'
  
  #   Failed test 'Checking whether sys_admin is in the bounding set'
  #   at t/capbset.t line 16.
  #  got: '0'
  # expected: '1'
  
  #   Failed test 'Checking whether sys_boot is in the bounding set'
  #   at t/capbset.t line 16.
  #  got: '0'
  # expected: '1'
  
  #   Failed test 'Checking whether sys_module is in the bounding set'
  #   at t/capbset.t line 16.
  #  got: '0'
  # expected: '1'
  
  #   Failed test 'Checking whether sys_nice is in the bounding set'
  #   at t/capbset.t line 16.
  #  got: '0'
  # expected: '1'
  
  #   Failed test 'Checking whether sys_pacct is in the bounding set'
  #   at t/capbset.t line 16.
  #  got: '0'
  # expected: '1'
  
  #   Failed test 'Checking whether sys_ptrace is in the bounding set'
  #   at t/capbset.t line 16.
  #  got: '0'
  # expected: '1'
  
  #   Failed test 'Checking whether sys_rawio is in the bounding set'
  #   at t/capbset.t line 16.
  #  got: '0'
  # expected: '1'
  
  #   Failed test 'Checking whether sys_resource is in the bounding set'
  #   at t/capbset.t line 16.
  #  got: '0'
  # expected: '1'
  
  #   Failed test 'Checking whether sys_time is in the bounding set'
  #   at t/capbset.t line 16.
  #  got: '0'
  # expected: '1'
  
  #   Failed test 'Checking whether sys_tty_config is in the bounding set'
  #   at t/capbset.t line 16.
  #  got: '0'
  # expected: '1'
  
  #   Failed test 'Checking whether wake_alarm is in the bounding set'
  #   at t/capbset.t line 16.
  #  got: '0'
  # expected: '1'
  # Looks like you failed 22 tests of 73.
  t/capbset.t ... 
  1..73
  ok 1 - Have a tied capbset object
  not ok 2 - Checking whether audit_control is in the bounding set
  ok 3 - Checking whether audit_write is in the bounding set
  ok 4 - Checking whether chown is in the bounding set
  ok 5 - Checking whether dac_override is in the bounding set
  not ok 6 - Checking whether dac_read_search is in the bounding set
  ok 7 - Checking whether fowner is in the bounding set
  ok 8 - Checking whether fsetid is in the bounding set
  not ok 9 - Checking whether ipc_lock is in the bounding set
  not ok 10 - Checking whether ipc_owner is in the bounding set
  ok 11 - Checking whether kill is in the bounding set
  not ok 12 - Checking whether lease is in the bounding set
  not ok 13 - Checking whether linux_immutable is in the bounding set
  not ok 14 - Checking whether mac_admin is in the bounding set
  not ok 15 - Checking whether mac_override is in the bounding set
  ok 16 - Checking whether mknod is in the bounding set
  not ok 17 - Checking whether net_admin is in the bounding set
  ok 18 - Checking whether net_bind_service is in the bounding set
  not ok 19 - Checking whether net_broadcast is in the bounding set
  ok 20 - Checking whether net_raw is in the bounding set
  ok 21 - Checking whether setfcap is in the bounding set
  ok 22 - Checking whether setgid is in the bounding set
  ok 23 - Checking whether setpcap is in the bounding set
  ok 24 - Checking whether setuid is in the bounding set
  not ok 25 - Checking whether syslog is in the bounding set
  not ok 26 - Checking whether sys_admin is in the bounding set
  not ok 27 - Checking whether sys_boot is in the bounding set
  ok 28 - Checking whether sys_chroot is in the bounding set
  not ok 29 - Checking whether sys_module is in the bounding set
  not ok 30 - Checking whether sys_nice is in the bounding set
  not ok 31 - Checking whether sys_pacct is in the bounding set
  not ok 32 - Checking whether sys_ptrace is in the bounding set
  not ok 33 - Checking whether sys_rawio is in the bounding set
  not ok 34 - Checking whether sys_resource is in the bounding set
  not ok 35 - Checking whether sys_time is in the bounding set
  not ok 36 - Checking whether sys_tty_config is in the bounding set
  not ok 37 - Checking whether wake_alarm is in the bounding set
  ok 38 # skip Drop tests only 

Bug#829478: shadowsocks-libev: modifies conffiles (policy 10.7.3): /etc/shadowsocks-libev/config.json

[Andreas Beckmann]

On 2016-07-04 09:31, Roger Shimizu wrote:
> The fix may be one of the following:
> - move the config from /etc/ to somewhere else, such as /var/cache
> - use debconf to get the password from user when install, as Andreas
> said in previous email

Ship a config file template in /usr/share/$PACKAGE/...
The file (whereever you place it) created by the maintainer scripts is
*not* shipped by the package but only managed by the maintainer scripts.

Maybe look into using ucf to manage it.


Andreas

Processed: bug 829549 is forwarded to https://github.com/celogeek/MooX-Options/issues/55

[Debian Bug Tracking System]

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

> forwarded 829549 https://github.com/celogeek/MooX-Options/issues/55
Bug #829549 [src:libmoox-options-perl] libmoox-options-perl: FTBFS: Failed 2/31 
test programs. 2/156 subtests failed.
Set Bug forwarded-to-address to 
'https://github.com/celogeek/MooX-Options/issues/55'.
> thanks
Stopping processing here.

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

Bug#821795: lttng-modules-dkms: module FTBFS in jessie against Linux 3.16: error: conflicting types for 'trace_mm_page_alloc_extfrag'

[Michael Jeanson]

Hi Jon,

Here is an updated debdiff, it works on a fully updated jessie. Should
we track these updates in a branch of the collab-maint repo?

Michael
diff -Nru lttng-modules-2.5.1/debian/changelog 
lttng-modules-2.5.1/debian/changelog
--- lttng-modules-2.5.1/debian/changelog2014-10-24 11:11:35.0 
-0400
+++ lttng-modules-2.5.1/debian/changelog2016-07-04 04:49:26.0 
-0400
@@ -1,3 +1,9 @@
+lttng-modules (2.5.1-2~test2) unstable; urgency=medium
+
+  * Add patches
+
+ -- Michael Jeanson   Mon, 04 Jul 2016 17:24:58 -0400
+
 lttng-modules (2.5.1-1) unstable; urgency=medium
 
   * [106d0a8] New upstream version 2.5.1
diff -Nru lttng-modules-2.5.1/debian/lttng-modules-dkms.dkms.in 
lttng-modules-2.5.1/debian/lttng-modules-dkms.dkms.in
--- lttng-modules-2.5.1/debian/lttng-modules-dkms.dkms.in   2014-10-24 
11:11:35.0 -0400
+++ lttng-modules-2.5.1/debian/lttng-modules-dkms.dkms.in   2016-07-04 
04:47:00.0 -0400
@@ -10,7 +10,7 @@
 KCONFIG=true
 fi
 
-MAKE[$i]="make -C $kernel_source_dir 
M=$dkms_tree/$PACKAGE_NAME/$PACKAGE_VERSION/build modules"
+MAKE[$i]="make -C $kernel_source_dir 
M=$dkms_tree/$PACKAGE_NAME/$PACKAGE_VERSION/build modules V=1"
 
 BUILT_MODULE_NAME[$i]="lttng-lib-ring-buffer"
 BUILT_MODULE_LOCATION[$i]="lib/"
@@ -158,13 +158,6 @@
 DEST_MODULE_LOCATION[$i]="/extra/probes"
 i=$((i+1))
 
-if [ "$KCONFIG" = "true" ] && [ -n "$CONFIG_REGMAP" ]; then
-BUILT_MODULE_NAME[$i]="lttng-probe-regmap"
-BUILT_MODULE_LOCATION[$i]="probes/"
-DEST_MODULE_LOCATION[$i]="/extra/probes"
-i=$((i+1))
-fi
-
 if [ "$KCONFIG" = "true" ] && [ -n "$CONFIG_REGULATOR" ]; then
 BUILT_MODULE_NAME[$i]="lttng-probe-regulator"
 BUILT_MODULE_LOCATION[$i]="probes/"
diff -Nru lttng-modules-2.5.1/debian/patches/0001-Fix-discover-Debian-API.patch 
lttng-modules-2.5.1/debian/patches/0001-Fix-discover-Debian-API.patch
--- lttng-modules-2.5.1/debian/patches/0001-Fix-discover-Debian-API.patch   
1969-12-31 19:00:00.0 -0500
+++ lttng-modules-2.5.1/debian/patches/0001-Fix-discover-Debian-API.patch   
2016-07-04 04:41:24.0 -0400
@@ -0,0 +1,257 @@
+From 0aadd8424c7c21259f80da4c97a2b9fef92bd2e9 Mon Sep 17 00:00:00 2001
+From: Mathieu Desnoyers 
+Date: Mon, 27 Apr 2015 10:57:34 -0400
+Subject: [PATCH 1/2] Fix: discover Debian API
+
+Signed-off-by: Mathieu Desnoyers 
+---
+ Makefile   | 12 ++--
+ Makefile.ABI.workarounds   | 11 
+ abi-debian-version.sh  | 30 ++
+ instrumentation/events/lttng-module/kmem.h | 91 +-
+ lib/Makefile   |  4 ++
+ lttng-kernel-version.h | 14 +
+ probes/Makefile|  4 ++
+ 7 files changed, 161 insertions(+), 5 deletions(-)
+ create mode 100644 Makefile.ABI.workarounds
+ create mode 100755 abi-debian-version.sh
+
+--- a/Makefile
 b/Makefile
+@@ -5,6 +5,8 @@
+ ifneq ($(KERNELRELEASE),)
+ ifneq ($(CONFIG_TRACEPOINTS),)
+ 
++KERNELDIR=${LTTNG_KERNELDIR}
++
+ lttng_check_linux_version = $(shell pwd)/include/linux/version.h
+ lttng_check_generated_linux_version = $(shell 
pwd)/include/generated/uapi/linux/version.h
+ 
+@@ -19,6 +21,8 @@
+ endif
+ endif
+ 
++include $(KBUILD_EXTMOD)/Makefile.ABI.workarounds
++
+ obj-m += lttng-ring-buffer-client-discard.o
+ obj-m += lttng-ring-buffer-client-overwrite.o
+ obj-m += lttng-ring-buffer-metadata-client.o
+@@ -67,14 +71,14 @@
+   CFLAGS = $(EXTCFLAGS)
+ 
+ default:
+-  $(MAKE) -C $(KERNELDIR) M=$(PWD) modules
++  LTTNG_KERNELDIR=$(KERNELDIR) $(MAKE) -C $(KERNELDIR) M=$(PWD) modules
+ 
+ modules_install:
+-  $(MAKE) -C $(KERNELDIR) M=$(PWD) modules_install
++  LTTNG_KERNELDIR=$(KERNELDIR) $(MAKE) -C $(KERNELDIR) M=$(PWD) 
modules_install
+ 
+ clean:
+-  $(MAKE) -C $(KERNELDIR) M=$(PWD) clean
++  LTTNG_KERNELDIR=$(KERNELDIR) $(MAKE) -C $(KERNELDIR) M=$(PWD) clean
+ 
+ %.i: %.c
+-  $(MAKE) -C $(KERNELDIR) M=$(PWD) $@
++  LTTNG_KERNELDIR=$(KERNELDIR) $(MAKE) -C $(KERNELDIR) M=$(PWD) $@
+ endif # KERNELRELEASE
+--- /dev/null
 b/Makefile.ABI.workarounds
+@@ -0,0 +1,11 @@
++# Work-around for distro-specific public modules ABI breakages.
++# Some distributions break the public module instrumentation ABI
++# compared to upstream stable kernels without providing other mean than
++# the kernel EXTRAVERSION to figure it out. Translate this information
++# into a define visible from the C preprocessor.
++
++DEB_API_VERSION=$(shell $(KBUILD_EXTMOD)/abi-debian-version.sh $(CURDIR))
++
++ifneq ($(DEB_API_VERSION), 0)
++ccflags-y += -DDEBIAN_API_VERSION=$(DEB_API_VERSION)
++endif
+--- /dev/null
 b/abi-debian-version.sh
+@@ -0,0 +1,39 @@
++#!/bin/sh
++
++# First argument is the path to the kernel headers.
++KPATH=$1
++
++if [ ! -f ${KPATH}/include/generated/package.h ]; then
++  echo 

Bug#825845: mrpt: FTBFS on big-endian systems, with test suite errors

[JOSE LUIS BLANCO CLARACO]

Hi,

Please, find the workaround (not solution!) commit in [1]. Please, if
possible, apply it directly over the current v1.4.0 Debian package to
unblock building in big endian platforms. It would be great if you
could sponsor the update in Debian, not only in Ubuntu.

If I find spare time to work in a real solution, I'll contact you just
in case you could help me testing the patches in porter machines...

Thanks for the support!

[1] https://github.com/MRPT/mrpt/commit/b247f14ffdaf8f31ec8cafefcc2a12ac1d210618

Bug#813749: mozjs24: Unsatisfiable Build-Depends and Build-Conflicts

[dai]

On Mon, Jul 04, 2016 at 11:06:32AM +0900, d...@debian.org wrote:
> built mozjs24 24.2.0-3 removed python3*-minimal from Build-Depends on Jessie,

s/Build-Depends/Build-Conflicts/

> So I think Build-Depends: python3*-minimal is not needed to build at present.

s/Build-Depends/Build-Conflicts/

sorry.
-- 
Regards,
dai

GPG Fingerprint = 0B29 D88E 42E6 B765 B8D8 EA50 7839 619D D439 668E


signature.asc
Description: PGP signature

Processed: Bug#829542 in package dpkg marked as pending

[Debian Bug Tracking System]

Processing control commands:

> tag 829542 pending
Bug #829542 [dpkg-dev] dpkg-dev: dpkg-buildpackage misses import of 
Dpkg::Control::Info
Added tag(s) pending.

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

Bug#829550: ngetty: FTBFS: sig_action.h:16:7: error: '_NSIG_WORDS' undeclared (first use in this function)

[Chris Lamb]

Source: ngetty
Version: 1.1-3
Severity: serious
Justification: fails to build from source
User: reproducible-bui...@lists.alioth.debian.org
Usertags: ftbfs
X-Debbugs-Cc: reproducible-bui...@lists.alioth.debian.org

Dear Maintainer,

ngetty fails to build from source in unstable/amd64:

  [..]

  
  
**
  ** Starting build 
  **
  
**
  
   Package:  ngetty
   Version:  1.1-3
   Build architecture:   amd64
   Date: Mon, 04 Jul 2016 08:32:16 +0200
   Hostname: eae6b7eb52d2
   Uname:Linux eae6b7eb52d2 4.6.0-1-amd64 #1 SMP Debian 4.6.2-2 
(2016-06-25) x86_64 GNU/Linux
   /etc/timezone:Africa/Johannesburg
  
  
**
  ** Installing build dependencies  
  **
  
**
  
  dh_testdir
  dh_testroot
  dh_prep
  dh_testdir
  dh_testroot
  dh_install
  dh_installdocs
  dh_installchangelogs
  dh_compress
  dh_fixperms
  dh_installdeb
  dh_gencontrol
  dh_md5sums
  dh_builddeb
  dpkg-deb: building package 'ngetty-build-deps' in 
'../ngetty-build-deps_1.1-3_all.deb'.
  
  The package has been created.
  Attention, the package has been created in the current directory,
  not in ".." as indicated by the message above!
  Selecting previously unselected package ngetty-build-deps.
  (Reading database ... 23081 files and directories currently installed.)
  Preparing to unpack ngetty-build-deps_1.1-3_all.deb ...
  Unpacking ngetty-build-deps (1.1-3) ...
  Reading package lists...
  Building dependency tree...
  Reading state information...
  Correcting dependencies... Done
  The following additional packages will be installed:
dietlibc-dev
  Suggested packages:
dietlibc-doc
  The following NEW packages will be installed:
dietlibc-dev
  0 upgraded, 1 newly installed, 0 to remove and 0 not upgraded.
  1 not fully installed or removed.
  Need to get 401 kB of archives.
  After this operation, 2859 kB of additional disk space will be used.
  Get:1 http://httpredir.debian.org/debian sid/main amd64 dietlibc-dev amd64 
0.34~cvs20160606-1 [401 kB]
  Fetched 401 kB in 0s (549 kB/s)
  Selecting previously unselected package dietlibc-dev:amd64.
  (Reading database ... 
(Reading database ... 5%
(Reading database ... 10%
(Reading database ... 15%
(Reading database ... 20%
(Reading database ... 25%
(Reading database ... 30%
(Reading database ... 35%
(Reading database ... 40%
(Reading database ... 45%
(Reading database ... 50%
(Reading database ... 55%
(Reading database ... 60%
(Reading database ... 65%
(Reading database ... 70%
(Reading database ... 75%
(Reading database ... 80%
(Reading database ... 85%
(Reading database ... 90%
(Reading database ... 95%
(Reading database ... 100%
(Reading database ... 23085 files and directories currently installed.)
  Preparing to unpack .../dietlibc-dev_0.34~cvs20160606-1_amd64.deb ...
  Unpacking dietlibc-dev:amd64 (0.34~cvs20160606-1) ...
  Processing triggers for man-db (2.7.5-1) ...
  Setting up dietlibc-dev:amd64 (0.34~cvs20160606-1) ...
  update-alternatives: using /usr/lib/x86_64-linux-gnu/diet/lib-x86_64 to 
provide /usr/lib/diet/lib-x86_64 (dietlibc-libdir-x86_64) in auto mode
  update-alternatives: using /usr/lib/x86_64-linux-gnu/diet/bin/diet to provide 
/usr/bin/diet (diet) in auto mode
  Setting up ngetty-build-deps (1.1-3) ...
  
  
**
  ** Environment
  **
  
**
  
  
PATH=/home/lamby/git/projects/dotfiles/dotfiles/..//bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin
  HOSTNAME=eae6b7eb52d2
  TERM=xterm
  PAGER=more
  DISPLAY=:0
  DOCKER_IMAGE=lamby-debian-sid
  DEB_BUILD_OPTIONS=parallel=9
  PIP_DOWNLOAD_CACHE=/home/lamby/.cache/pip
  HOME=/home/lamby
  LOGNAME=lamby
  SHLVL=1
  PWD=/home/lamby/temp/cdt.20160704083214.WCvLSE9Tyn.ngetty/ngetty-1.1
  OLDPWD=/home/lamby/temp/cdt.20160704083214.WCvLSE9Tyn.ngetty
  GPG_TTY=/dev/console
  QUILT_PATCHES=debian/patches
  QUILT_NO_DIFF_INDEX=1
  QUILT_REFRESH_ARGS=-p ab --no-timestamps --no-index
  DEBEMAIL=la...@debian.org
  DEBFULLNAME=Chris Lamb
  EDITOR=vim
  LESS=-cgiFx4M
  BLASTER=A220 I5 D1 H5 P330 T6
  _=/usr/bin/env
  
  
**
  ** Building ngetty 1.1-3 on amd64 
  **
  

Bug#565010: marked as done (kanjisaver: ftbfs with gcc-4.5)

[Debian Bug Tracking System]

Your message dated Sun, 3 Jul 2016 22:12:56 +0200
with message-id <6445b9e1-e283-e473-87a6-5e185fbe3...@debian.org>
and subject line kanjisaver was removed from Debian in 2011
has caused the Debian Bug report #565010,
regarding kanjisaver: ftbfs with gcc-4.5
to be marked as done.

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

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


-- 
565010: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=565010
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: kanjisaver
Version: 0.9.10-1
Severity: normal
Tags: sid
User: debian-...@lists.debian.org
Usertags: ftbfs-gcc-4.5

The package fails to build in a test rebuild on at least amd64 with
gcc-4.5/g++-4.5, but succeeds to build with gcc-4.4/g++-4.4.
For the compiler version used, see:
http://lists.debian.org/debian-devel/2010/01/msg00230.html

The full build log can be found at:
http://people.debian.org/~lucas/logs/2010/01/08b/kanjisaver_0.9.10-1_lsid64b.buildlog
The last lines of the build log are cwat the end of this report.

The reason of the build failure is likely in the package (compiler or
linker message found in the build log), if this turns out as a gcc bug,
please reassign to the gcc-4.5 package. If the build ends with a
message "confused by earlier errors, bailing out", please
ignore it for now; these compiler errors are filed separately.


[...]
kanjisaver.cpp:566:40: note: for a function-style cast, remove the redundant 
'::QPoint'
kanjisaver.cpp:567:53: error: cannot call constructor 'QPoint::QPoint' directly
kanjisaver.cpp:567:53: note: for a function-style cast, remove the redundant 
'::QPoint'
kanjisaver.cpp:567:53: error: no matching function for call to 
'QPoint::QPoint(int, int&, int, int&)'
/usr/share/qt3/include/qpoint.h:114:8: note: candidates are: 
QPoint::QPoint(int, int)
/usr/share/qt3/include/qpoint.h:111:8: note: QPoint::QPoint()
/usr/share/qt3/include/qpoint.h:50:1: note: 
QPoint::QPoint(const QPoint&)
kanjisaver.cpp:568:8: error: cannot call constructor 'QRect::QRect' directly
kanjisaver.cpp:568:8: note: for a function-style cast, remove the redundant 
'::QRect'
kanjisaver.cpp:577:57: warning: conversion to 'int' from 'size_t' may alter its 
value
kanjisaver.cpp:604:42: error: cannot call constructor 'QPoint::QPoint' directly
kanjisaver.cpp:604:42: note: for a function-style cast, remove the redundant 
'::QPoint'
kanjisaver.cpp:605:61: error: cannot call constructor 'QPoint::QPoint' directly
kanjisaver.cpp:605:61: note: for a function-style cast, remove the redundant 
'::QPoint'
kanjisaver.cpp:605:61: error: no matching function for call to 
'QPoint::QPoint(int, double, int, double)'
/usr/share/qt3/include/qpoint.h:114:8: note: candidates are: 
QPoint::QPoint(int, int)
/usr/share/qt3/include/qpoint.h:111:8: note: QPoint::QPoint()
/usr/share/qt3/include/qpoint.h:50:1: note: 
QPoint::QPoint(const QPoint&)
kanjisaver.cpp:606:8: error: cannot call constructor 'QRect::QRect' directly
kanjisaver.cpp:606:8: note: for a function-style cast, remove the redundant 
'::QRect'
kanjisaver.cpp:610: confused by earlier errors, bailing out
Preprocessed source stored into /tmp/ccQSHAWS.out file, please attach this to 
your bugreport.
make[3]: *** [kanjisaver.o] Error 1
make[3]: Leaving directory 
`/build/user-kanjisaver_0.9.10-1-amd64-EL_ott/kanjisaver-0.9.10/src'
make[2]: *** [all-recursive] Error 1
make[2]: Leaving directory 
`/build/user-kanjisaver_0.9.10-1-amd64-EL_ott/kanjisaver-0.9.10'
make[1]: *** [all] Error 2
make[1]: Leaving directory 
`/build/user-kanjisaver_0.9.10-1-amd64-EL_ott/kanjisaver-0.9.10'
make: *** [build-stamp] Error 2
dpkg-buildpackage: error: debian/rules build gave error exit status 2


--- End Message ---
--- Begin Message ---
Version: 0.9.10-1+rm

kanjisaver was last released with Debian 6.0 (squeeze) in
February 2011 and removed from Debian sid/unstable in 2011 (see
http://bugs.debian.org/510529 for details on the removal). Since
support for squeeze and squeeze-LTS has now ended, I'm closing all the
remaining bugs reported against this package.


Andreas--- End Message ---