Processed: Re: Bug#838418: libreoffice-gtk3: Font corruption - both content and dialogs

[Debian Bug Tracking System]

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

> tag 838418 + moreinfo
Bug #838418 [libreoffice-gtk3] libreoffice-gtk3: Font corruption - both content 
and dialogs
Added tag(s) moreinfo.
> thanks
Stopping processing here.

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

Bug#838418: libreoffice-gtk3: Font corruption - both content and dialogs

[Rene Engelhard]

tag 838418 + moreinfo
thanks

On Wed, Sep 21, 2016 at 07:37:11AM +0200, Rene Engelhard wrote:
> > Upgrade of libreoffice. It was definitely working fine on August 16th,
> > then I haven't done any upgrades until this last week, so I suspect the
> > move from 5.2.0 to 5.2.1
> 
> I will never understand why on earth people think it's a good idea to
> upgrade unstable only that rarely? That makes it harder to find out which
> exact upgrade was the problem. You use unstable, if you want a stable system
> (as in non-changing) use stable or (lesser changing than unstable) testing.

Especially as end of August we got Gtk 3.0 3.21.x What happens if you downgrade
that one to 3.20.9? (see snapshot.debian.org?

Regards,
 
Rene

Bug#838418: libreoffice-gtk3: Font corruption - both content and dialogs

[Rene Engelhard]

found 838418 1:5.2.1-1
thanks
 
On Tue, Sep 20, 2016 at 11:25:58PM +0100, Simon John wrote:
> Package: libreoffice-gtk3
> Version: 1:5.2.1-3

Obviously wrrong. Because you say below that 1:5.2.1-1 has the same problem.
So please take some care on reporting bugs, especially if it's RC and your
bug will block other RC bugfixes to enter testing.

> Upgrade of libreoffice. It was definitely working fine on August 16th,
> then I haven't done any upgrades until this last week, so I suspect the
> move from 5.2.0 to 5.2.1

I will never understand why on earth people think it's a good idea to
upgrade unstable only that rarely? That makes it harder to find out which
exact upgrade was the problem. You use unstable, if you want a stable system
(as in non-changing) use stable or (lesser changing than unstable) testing.

> Its not a driver issue as I get the same problem on Nvidia (nouveau)
> desktop and Intel laptop.

Any special fonts or anything else which might be special?

Regards,

Rene

Processed: Re: Bug#838418: libreoffice-gtk3: Font corruption - both content and dialogs

[Debian Bug Tracking System]

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

> found 838418 1:5.2.1-1
Bug #838418 [libreoffice-gtk3] libreoffice-gtk3: Font corruption - both content 
and dialogs
Marked as found in versions libreoffice/1:5.2.1-1.
> thanks
Stopping processing here.

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

Processed: Re: Bug#838431: systemd.postinst fails because the systemd-timesync user already exists when upgrading

[Debian Bug Tracking System]

Processing control commands:

> tags -1 moreinfo unreproducible
Bug #838431 [systemd] systemd.postinst fails because the systemd-timesync user 
already exists when upgrading
Added tag(s) moreinfo and unreproducible.
> severity -1 important
Bug #838431 [systemd] systemd.postinst fails because the systemd-timesync user 
already exists when upgrading
Severity set to 'important' from 'grave'

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

Bug#838431: systemd.postinst fails because the systemd-timesync user already exists when upgrading

[Michael Biebl]

Control: tags -1 moreinfo unreproducible
Control: severity -1 important

Am 21.09.2016 um 05:31 schrieb Grond:
>   Setting up systemd (215-17+deb8u5) ...
>   addgroup: The group `systemd-journal' already exists as a system group. 
> Exiting.
>   dpkg: error processing package systemd (--configure):
>subprocess installed post-installation script returned error exit 
> status 1

...

> `getent` queries for the other systemd users referenced in the above have 
> similar results.
> Apparently, `adduser` returns a non-zero exit status when told to create a 
> user that already
> exists, even if the --quiet flag is given.

If that's the case, then this would be a bug in adduser and not systemd.
I can't reproduce that though

# getent passwd systemd-timesync
systemd-timesync:x:108:113:systemd Time
Synchronization,,,:/run/systemd:/bin/false

# adduser --quiet --system --group --no-create-home --home /run/systemd
--gecos "systemd Time Synchronization" systemd-timesync

# echo $?
0

> Since the whole script is run under `set -e`, when the `adduser` command 
> fails, the entire
> systemd.postist script aborts.

Can you add "set -e" to systemd.postinst and then run
dpkg --configure -a and attach the log. Somehow I suspect the addgroup /
adduser message is a red herring.

> Fixing the problem is as simple as appending ' || true' to the end of each of 
> the
> problematic `adduser` commands

Nope, that would we a hack, not a fix


-- 
Why is it that all of the instruments seeking intelligent life in the
universe are pointed away from Earth?



signature.asc
Description: OpenPGP digital signature

Bug#838431: systemd.postinst fails because the systemd-timesync user already exists when upgrading

[Grond]

Package: systemd
Version: 215-17+deb8u5
Severity: grave
Justification: renders package unusable

Dear Maintainer,

I recently was upgrading my system with `aptitude upgrade`.
Everything was working fine up until dpkg tried to configure the new
version of the systemd package (215-17+deb8u5).
Here is some representative output from aptitude/dpkg:

Setting up systemd (215-17+deb8u5) ...
addgroup: The group `systemd-journal' already exists as a system group. 
Exiting.
dpkg: error processing package systemd (--configure):
 subprocess installed post-installation script returned error exit 
status 1
Errors were encountered while processing:
 systemd
E: Sub-process /usr/bin/dpkg returned an error code (1)
Failed to perform requested operation on package.  Trying to recover:
Setting up systemd (215-17+deb8u5) ...
addgroup: The group `systemd-journal' already exists as a system group. 
Exiting.
dpkg: error processing package systemd (--configure):
 subprocess installed post-installation script returned error exit 
status 1
Errors were encountered while processing:
 systemd

In spite of the error messages, which would indicate debain/systemd.postinst 
line 100:

addgroup --system systemd-journal

As the culprit, testing reveals that the problem is line 102:

adduser --quiet --system --group --no-create-home --home /run/systemd \
--gecos "systemd Time Synchronization" systemd-timesync
adduser --quiet --system --group --no-create-home --home 
/run/systemd/netif \
--gecos "systemd Network Management" systemd-network
adduser --quiet --system --group --no-create-home --home 
/run/systemd/resolve \
--gecos "systemd Resolver" systemd-resolve
adduser --quiet --system --group --no-create-home --home /run/systemd \
--gecos "systemd Bus Proxy" systemd-bus-proxy

`getent user systemd-timesync`:

systemd-timesync:x:100:103:systemd Time 
Synchronization,,,:/run/systemd:/bin/false

`getent` queries for the other systemd users referenced in the above have 
similar results.
Apparently, `adduser` returns a non-zero exit status when told to create a user 
that already
exists, even if the --quiet flag is given.
Since the whole script is run under `set -e`, when the `adduser` command fails, 
the entire
systemd.postist script aborts.

Fixing the problem is as simple as appending ' || true' to the end of each of 
the
problematic `adduser` commands

-- Package-specific info:

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

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

Versions of packages systemd depends on:
ii  acl 2.2.52-2
ii  adduser 3.113+nmu3
ii  initscripts 2.88dsf-59
ii  libacl1 2.2.52-2
ii  libaudit1   1:2.4-1+b1
ii  libblkid1   2.25.2-6
ii  libc6   2.19-18+deb8u6
ii  libcap2 1:2.24-8
ii  libcap2-bin 1:2.24-8
ii  libcryptsetup4  2:1.6.6-5
ii  libgcrypt20 1.6.3-2+deb8u2
ii  libkmod218-3
ii  liblzma55.1.1alpha+20120614-2+b3
ii  libpam0g1.1.8-3.1+deb8u1+b1
ii  libselinux1 2.3-2
ii  libsystemd0 215-17+deb8u5
ii  mount   2.25.2-6
ii  sysv-rc 2.88dsf-59
ii  udev215-17+deb8u5
ii  util-linux  2.25.2-6

Versions of packages systemd recommends:
ii  dbus1.8.20-0+deb8u1
pn  libpam-systemd  

Versions of packages systemd suggests:
pn  systemd-ui  

-- no debconf information

Bug#838429: zsh-antigen: broken package - only contains an invalid symlink

[Ondra Lengal]

Package: zsh-antigen
Version: 1.1.2-1
Severity: grave
Justification: renders package unusable

Dear Maintainer,

I encountered the following bug in unstable that makes the package unusable.
The content of the zsh-antigen package is:

% dtrx -l zsh-antigen_1.1.2-1_all.deb
./
./usr/
./usr/share/
./usr/share/doc/
./usr/share/doc/zsh-antigen/
./usr/share/doc/zsh-antigen/README.Debian
./usr/share/doc/zsh-antigen/README.mkd.gz
./usr/share/doc/zsh-antigen/changelog.Debian.gz
./usr/share/doc/zsh-antigen/changelog.gz
./usr/share/doc/zsh-antigen/copyright
./usr/share/zsh-antigen/
./usr/share/zsh-antigen/antigen.zsh

and the file ./usr/share/zsh-antigen/antigen.zsh is just a symlink to
bin/antigen.zsh (which is not present), so when starting zsh, I just get

.zshrc:source:3: no such file or directory: /usr/share/zsh-antigen/antigen.zsh
.zshrc:6: command not found: antigen
.zshrc:9: command not found: antigen
.zshrc:12: command not found: antigen
.zshrc:13: command not found: antigen
.zshrc:14: command not found: antigen
.zshrc:15: command not found: antigen
.zshrc:16: command not found: antigen
.zshrc:17: command not found: antigen
.zshrc:18: command not found: antigen
.zshrc:21: command not found: antigen

  Best regards,
 Ondra



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

Kernel: Linux 4.5.0-2-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 zsh-antigen depends on:
ii  git  1:2.9.3-1
ii  zsh  5.2-5

zsh-antigen recommends no packages.

zsh-antigen suggests no packages.

-- no debconf information

Bug#729813: marked as done (jessie/testing pam_unix2 (2.6-1) module is compiled without blowfish support)

[Debian Bug Tracking System]

Your message dated Wed, 21 Sep 2016 02:39:29 +
with message-id 
and subject line Bug#628848: Removed package(s) from unstable
has caused the Debian Bug report #729813,
regarding jessie/testing pam_unix2 (2.6-1) module is compiled without blowfish 
support
to be marked as done.

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

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


-- 
729813: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=729813
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: libpam-unix2
Version: 2.6-1
Severity: grave
Justification: package is unusable as its main feature is not supported


Module libpam_unix2 is compiled without blowfish support. Password change 
finishes with error:

root@straightXedge:/usr/share/pam-configs# passwd
New Password:
Reenter New Password:
crypt_r: Don't know 0
Error: Password NOT changed.
passwd: Authentication token manipulation error
passwd: password unchanged

Lack of blowfish support is shown in debugs:

root@straightXedge:/lib/security# cat /var/log/auth.log | grep "19:12"
Nov 17 18:19:12 straightXedge sshd[3638]: Failed password for root from 
192.168.40.1 port 65354 ssh2
Nov 17 19:12:02 straightXedge passwd[6686]: pam_unix2(passwd:chauthtok): 
Unknown option: `blowfish'
Nov 17 19:12:02 straightXedge passwd[6686]: pam_unix2(passwd:chauthtok): 
pam_sm_chauthtok() called
Nov 17 19:12:02 straightXedge passwd[6686]: pam_unix2(passwd:chauthtok): 
username=[root]
Nov 17 19:12:02 straightXedge passwd[6686]: pam_unix2(passwd:chauthtok): No old 
password found.
Nov 17 19:12:02 straightXedge passwd[6686]: pam_unix2(passwd:chauthtok): 
Unknown option: `blowfish'
Nov 17 19:12:02 straightXedge passwd[6686]: pam_unix2(passwd:chauthtok): 
pam_sm_chauthtok() called
Nov 17 19:12:02 straightXedge passwd[6686]: pam_unix2(passwd:chauthtok): 
username=[root]
Nov 17 19:12:02 straightXedge passwd[6686]: pam_unix2(passwd:chauthtok): No old 
password found.
Nov 17 19:12:05 straightXedge passwd[6686]: pam_unix2(passwd:chauthtok): No 
blowfish support compiled in

I am using the most up-to-date versions of libpam-unix2 and libxcrypt packages.

root@straightXedge:/lib/security# dpkg -l | grep -e "unix2 \| libxcrypt \| 
libpam0g"
ii  libpam-unix21:2.6-1   i386 
Blowfish-capable PAM module
ii  libxcrypt1  1:2.4-3   i386 
Crypt library for DES, MD5, and blowfish
ii  libpam0g:i386   1.1.3-9   i386 
Pluggable Authentication Modules library

This bug was previously reported in as #487487.

http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=487487

I replaced the .so library with the previous wheezy 2.4.1 version and the 
problem is solved. 

root@straightXedge:/lib/security# passwd
New Password:
Reenter New Password:
Password changed.
passwd: password updated successfully


Please recompile it with blowfish support.

regards,
Lukasz
--- End Message ---
--- Begin Message ---
Version: 1:2.6-2+rm

Dear submitter,

as the package libpam-unix2 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/628848

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.
Chris Lamb (the ftpmaster behind the curtain)--- End Message ---

Bug#832840: license-reconcile: diff for NMU version 0.12+nmu1

[gustavo panizzo (gfa)]

On Tue, Sep 20, 2016 at 06:42:51AM +0800, gustavo panizzo (gfa) wrote:
> On Mon, Sep 19, 2016 at 07:15:50PM +0200, gregor herrmann wrote:
> > On Mon, 19 Sep 2016 00:32:17 +0800, gustavo panizzo (gfa) wrote:
> > 
> > > I've attached the debdiff, I'll push my changes to the git repo after
> > > the NMU has been uploaded, let me know if you don't agree with any of
> > > this.
> > 
> > Thanks for your help.
> > 
> > It might be easier to push the changes to the git repo before an
> > upload, with 0.12 instead of 0.12+nmu1, and we can do a regular tram
> > upload. -- Whatever you prefer.
> 
> I have no preference on the matter, and you are the maintainer.
> I've tried to push to the git repo but I have no perms. so I've attached
> the diff between HEAD and your last commit to this email

or you can clone from
git.debian.org:/srv/home/users/gfa-guest/public_git/license-reconcile



-- 
1AE0 322E B8F7 4717 BDEA BF1D 44BB 1BA7 9F6C 6333

keybase: https://keybase.io/gfa

Bug#817656: marked as done (root-tail: Removal of debhelper compat 4)

[Debian Bug Tracking System]

Your message dated Wed, 21 Sep 2016 01:20:00 +
with message-id 
and subject line Bug#817656: fixed in root-tail 1.2-4
has caused the Debian Bug report #817656,
regarding root-tail: Removal of debhelper compat 4
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.)


-- 
817656: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=817656
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: root-tail
Severity: important
Usertags: compat-4-removal

Hi,

The package root-tail uses debhelper with a compat level of 4,
which is deprecated and scheduled for removal.

 * Please bump the debhelper compat at your earliest convenience.
   on the 15th of June.
   - Compat 9 is recommended
   - Compat 5 is the bare minimum
   - If the package has been relying on dh_install being lenient about
 missing files, please see "MIGRATING TO COMPAT 5 OR LATER" in [1].

 * Compat level 4 will be removed on the first debhelper upload after
   the 15th of June.

Thanks,
~Niels

[1] https://lists.debian.org/debian-devel/2015/09/msg00257.html
--- End Message ---
--- Begin Message ---
Source: root-tail
Source-Version: 1.2-4

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

Debian distribution maintenance software
pp.
Axel Beckert  (supplier of updated root-tail package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Wed, 21 Sep 2016 03:01:00 +0200
Source: root-tail
Binary: root-tail
Architecture: source amd64
Version: 1.2-4
Distribution: unstable
Urgency: medium
Maintainer: Debian QA Group 
Changed-By: Axel Beckert 
Description:
 root-tail  - Displays select log files in the X root window
Closes: 641561 817656
Changes:
 root-tail (1.2-4) unstable; urgency=medium
 .
   * QA upload.
 + Set Maintainer to Debian QA Group. (See #838406)
 + Add Vcs-* headers for newly created collab-maint Git repo.
   * Apply wrap-and-sort.
   * Add Homepage header.
   * Bump debhelper compatibility level to 9. (Closes: #817656)
 + Update versioned build-dependency on debhelper accordingly.
   * Add dependency on ${misc:Depends}.
   * Rewrite debian/rules in minimal dh v7 style.
   * Enable all hardening build flags.
   * Convert to source format "3.0 (quilt)" using diff2patches.
 + Add DEP3 patch headers to all of them.
 + Drop patch against mkdist. (CVS-related, obsolete)
   * Update Makefile so that
 + all hardening flags are passed properly
 + $(DESTDIR) is honoured (no more need for override_dh_auto_install)
 + Upstream Changes file is no more installed (done by
   dh_installchangelogs automatically)
 + the package no more FTBFS with "ld --as-needed" (Closes: #641561, LP:
   #770864)
   * debian/clean: Make clean target work even when no patches are applied.
   * Extend long package description a bit.
   * Add a watch file.
   * Declare compliance with Debian Policy 3.9.8.
   * Convert debian/copyright to machine-readable DEP5 format.
   * Fix typos in 0.0.10-1 and 0.0.10-2 debian/changelog entries.
Checksums-Sha1:
 a4d3a67b866d3854fe7f2164d80c744da1a4e2ee 1854 root-tail_1.2-4.dsc
 f6232288970d569566b673d540e96f43e67150f7 5156 root-tail_1.2-4.debian.tar.xz
 1b054ceb2067af2ebb62eb9d9a589f408e1c956d 27640 root-tail-dbgsym_1.2-4_amd64.deb
 e897d010ccc162e578354d4e937640c490cf42c7 20940 root-tail_1.2-4_amd64.deb
Checksums-Sha256:
 5d82b71a8ded87b584df3a7ca07bfa6f7810b2f7da56c3e2eb07b456b847a1f8 1854 
root-tail_1.2-4.dsc
 6a7d73e08ef9a3d55e6bd418b96a90c0195bb85d9a6dc8b0204618854ab7e553 5156 
root-tail_1.2-4.debian.tar.xz
 203c1332869925234c6180e19427024e4abbe33b3ab29b88816142964dd8beed 27640 
root-tail-dbgsym_1.2-4_amd64.deb
 6bb3c6939b1b92321a5b8340b890b19c2d8da2635593c4fac2bc71ca07494bd3 20940 
root-tail_1.2-4_amd64.deb
Files:
 bacc9fa67f75a24109740122f2271061 1854 x11 optional root-tail_1.2-4.dsc
 5397e49b47e2ce5bef28c7efc5dae8f8 5156 x11 optional 
root-tail_1.2-4.debian.tar.xz
 dac6a1dc0ca35d574ca86fe540a929dc 27640 debug 

Bug#838336: marked as done (gnome-control-center: Keybinding panel fail to open)

[Debian Bug Tracking System]

Your message dated Wed, 21 Sep 2016 00:29:54 +
with message-id 
and subject line Bug#838336: fixed in gnome-control-center 1:3.22.0-1
has caused the Debian Bug report #838336,
regarding gnome-control-center: Keybinding panel fail to open
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.)


-- 
838336: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=838336
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: gnome-control-center
Version: 1:3.21.92-2
Severity: grave
Justification: renders package unusable

In gnome-control-center, the "keyboard" entry, for keybinding configuration 
fail to open (and gnome-control-center close). The trace i got in terminal is : 

(gnome-control-center:24830): Gtk-CRITICAL **: Error building template class 
'CcKeyboardPanel' for an instance of type 'CcKeyboardPanel': .:2:1622 Invalid 
property: GtkScrolledWindow.propagate_natural_width

(gnome-control-center:24830): Gtk-CRITICAL **: gtk_container_add: assertion 
'GTK_IS_CONTAINER (container)' failed
[…]
(gnome-control-center:24830): Gtk-CRITICAL **: gtk_list_box_set_sort_func: 
assertion 'GTK_IS_LIST_BOX (box)' failed

(gnome-control-center:24830): Gtk-CRITICAL **: gtk_list_box_set_header_func: 
assertion 'GTK_IS_LIST_BOX (box)' failed

(gnome-control-center:24830): Gtk-CRITICAL **: gtk_list_box_set_filter_func: 
assertion 'GTK_IS_LIST_BOX (box)' failed

(gnome-control-center:24830): Gtk-CRITICAL **: gtk_list_box_set_placeholder: 
assertion 'GTK_IS_LIST_BOX (box)' failed

(gnome-control-center:24830): Gtk-CRITICAL **: gtk_box_pack: assertion 
'GTK_IS_WIDGET (child)' failed

(gnome-control-center:24830): GLib-GObject-CRITICAL **: g_object_ref: assertion 
'G_IS_OBJECT (object)' failed

(gnome-control-center:24830): Gtk-CRITICAL **: gtk_size_group_add_widget: 
assertion 'GTK_IS_WIDGET (widget)' failed
**
ERROR:cc-panel.c:202:cc_panel_size_allocate: assertion failed: (child)



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

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

Versions of packages gnome-control-center depends on:
ii  accountsservice0.6.40-3
ii  apg2.2.3.dfsg.1-4
ii  colord 1.3.3-2
ii  desktop-file-utils 0.23-1
ii  gnome-control-center-data  1:3.21.92-2
ii  gnome-desktop3-data3.21.92-1
ii  gnome-settings-daemon  3.21.90-2
ii  gsettings-desktop-schemas  3.21.4-2
ii  libaccountsservice00.6.40-3
ii  libatk1.0-02.21.90-2
ii  libc6  2.23-5
ii  libcairo-gobject2  1.14.6-1+b1
ii  libcairo2  1.14.6-1+b1
ii  libcanberra-gtk3-0 0.30-3
ii  libcanberra0   0.30-3
ii  libcheese-gtk253.21.92-1
ii  libcheese8 3.21.92-1
ii  libclutter-1.0-0   1.26.0-2
ii  libclutter-gtk-1.0-0   1.8.0-2
ii  libcolord-gtk1 0.1.26-1
ii  libcolord2 1.3.3-2
ii  libcups2   2.1.4-4
ii  libfontconfig1 2.11.0-6.7
ii  libgdk-pixbuf2.0-0 2.34.0-1
ii  libglib2.0-0   2.49.6-1
ii  libgnome-bluetooth13   3.20.0-1
ii  libgnome-desktop-3-12  3.21.92-1
ii  libgoa-1.0-0b  3.21.91-1
ii  libgoa-backend-1.0-1   3.21.91-1
ii  libgrilo-0.3-0 0.3.2-1
ii  libgtk-3-0 3.21.5-3
ii  libgtop-2.0-10 2.34.1-2
ii  libgudev-1.0-0 230-3
ii  libibus-1.0-5  1.5.11-1
ii  libkrb5-3  1.14.3+dfsg-2
ii  libmm-glib01.6.0-1
ii  libnm0 1.2.4-2
ii  libnma01.2.4-1
ii  libpango-1.0-0 1.40.2-1
ii  libpangocairo-1.0-01.40.2-1
ii  libpolkit-gobject-1-0  0.105-16
ii  libpulse-mainloop-glib09.0-3
ii  libpulse0  9.0-3
ii  libpwquality1  1.3.0-1
ii  libsmbclient   2:4.4.5+dfsg-3
ii  libsoup2.4-1   2.55.90-1
ii  libupower-glib30.99.4-3
ii  libwacom2  0.19-1
ii  libx11-6   2:1.6.3-1
ii  libxi6 2:1.7.6-1
ii  libxml22.9.4+dfsg1-2

Versions of packages gnome-control-center recommends:
ii  cracklib-runtime  2.9.2-3
ii  cups-pk-helper0.2.6-1
ii  gkbd-capplet

Bug#817656: root-tail: Removal of debhelper compat 4

[Axel Beckert]

Hi Francesco,

Francesco Poli wrote:
> On Sun, 28 Aug 2016 16:08:03 +0200 Francesco Poli wrote:
> > I am a user of root-tail and I find it very nice and useful.
> > Thanks for maintaining it in Debian!
> > 
> > However, I am beginning to worry about the status of this package:
> > it has been removed from Debian testing, because of the RC bug I am
> > replying to (#817656), it has stayed out of Debian testing since then
> > and I cannot see any visible progress in addressing the issue.
> > 
> > Are you working on the packaging issues? Will they be solved soon?
> > If so, could you please send a status update to the bug address?

root-tail has just been orphaned by the MIA team on behalf of Stephen
Gran, see https://bugs.debian.org/838406.

I'm preparing a QA upload of root-tail fixing this bug and updating
the packaging to the current state of the art.

I also created a packaging git repository at
https://anonscm.debian.org/cgit/collab-maint/root-tail.git/ (will be
visibile in about an hour or so) for future root-tail maintenance.

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

Processed: tagging 817656

[Debian Bug Tracking System]

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

> # QA upload ahead
> tags 817656 + pending
Bug #817656 [src:root-tail] root-tail: Removal of debhelper compat 4
Added tag(s) pending.
> thanks
Stopping processing here.

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

Bug#837590: marked as done (alsa-tools FTBFS on armel: gcc-6 narrowing conversions)

[Debian Bug Tracking System]

Your message dated Tue, 20 Sep 2016 23:20:11 +
with message-id 
and subject line Bug#837590: fixed in alsa-tools 1.1.0-2
has caused the Debian Bug report #837590,
regarding alsa-tools FTBFS on armel: gcc-6 narrowing conversions
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.)


-- 
837590: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=837590
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: alsa-tools
Version: 1.1.0-1
Severity: serious

I noticed that alsa-tools fails to cross build from source for armel due
to gcc-6 narrowing conversion issues. Issues about narrowing conversions
are generally not cross compilation specific and reproducible natively.
Thus filing at RC severity. A full (cross) build log is attached. The
relevant excerpt is:

| arm-linux-gnueabi-g++ -DPACKAGE_NAME=\"hdspmixer\" 
-DPACKAGE_TARNAME=\"hdspmixer\" -DPACKAGE_VERSION=\"1.11\" 
-DPACKAGE_STRING=\"hdspmixer\ 1.11\" -DPACKAGE_BUGREPORT=\"\" 
-DPACKAGE_URL=\"\" -DPACKAGE=\"hdspmixer\" -DVERSION=\"1.11\" -DSTDC_HEADERS=1 
-DHAVE_LIBASOUND=1 -I.   -Wdate-time -D_FORTIFY_SOURCE=2  -g -O2 
-fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat 
-Werror=format-security   -I/usr/include/freetype2   -D_THREAD_SAFE 
-D_REENTRANT -fno-exceptions -MT channelmap.o -MD -MP -MF .deps/channelmap.Tpo 
-c -o channelmap.o channelmap.cxx
| channelmap.cxx:59:1: error: narrowing conversion of '-1' from 'int' to 'char' 
inside { } [-Wnarrowing]
|  };
|  ^

Helmut


alsa-tools_1.1.0-1_armel.log.xz
Description: application/xz
--- End Message ---
--- Begin Message ---
Source: alsa-tools
Source-Version: 1.1.0-2

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

Debian distribution maintenance software
pp.
Jordi Mallach  (supplier of updated alsa-tools package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Tue, 20 Sep 2016 11:45:12 +0200
Source: alsa-tools
Binary: alsa-tools alsa-tools-gui alsa-firmware-loaders ld10k1 liblo10k1-0 
liblo10k1-dev
Architecture: source amd64
Version: 1.1.0-2
Distribution: unstable
Urgency: medium
Maintainer: Debian ALSA Maintainers 
Changed-By: Jordi Mallach 
Description:
 alsa-firmware-loaders - ALSA software loaders for specific hardware
 alsa-tools - Console based ALSA utilities for specific hardware
 alsa-tools-gui - GUI based ALSA utilities for specific hardware
 ld10k1 - ALSA emu10k1/2 patch loader
 liblo10k1-0 - ALSA emu10k1/2 patch-loader library
 liblo10k1-dev - ALSA emu10k1/2 patch-loader library development files
Closes: 837590
Changes:
 alsa-tools (1.1.0-2) unstable; urgency=medium
 .
   [ Elimar Riesebieter ]
   * Cherry picked  gcc6-narrowing-error.patch from git to prevent a FTBFS on
 architecture armel. (closes: 837590)
 .
   [ Jordi Mallach ]
   * Add Catalan translation to desktop files.
   * Enable hardening build options.
Checksums-Sha1:
 e81c215bbab88dc44a1ea54c0c9205f2883d65c0 2418 alsa-tools_1.1.0-2.dsc
 859e2b36d662001ae3128b91c5ed4a210639a917 27936 alsa-tools_1.1.0-2.debian.tar.xz
 4ad9a4108d335eada698eaa43dba44c8faadfae2 54476 
alsa-firmware-loaders-dbgsym_1.1.0-2_amd64.deb
 d84d694028349ec6630f6069458514ee24c3c28a 32630 
alsa-firmware-loaders_1.1.0-2_amd64.deb
 0d24a273f3710662fd65cbd886735e649d2254b6 103756 
alsa-tools-dbgsym_1.1.0-2_amd64.deb
 73fc9ae8b94c08123d9126631b36212e854d905f 578280 
alsa-tools-gui-dbgsym_1.1.0-2_amd64.deb
 72b6b6a5b9d9913a89c3d7aa34c865a6b8ef5dca 191006 
alsa-tools-gui_1.1.0-2_amd64.deb
 7ea79f2c52c739bc145beaaa6029967455061cc0 65720 alsa-tools_1.1.0-2_amd64.deb
 6cd1d705be2657f4b9bd865fd69c5ab0fa800507 121350 ld10k1-dbgsym_1.1.0-2_amd64.deb
 c2daeb7fd13fb3815b1e52172dd900e9af3133eb 102722 ld10k1_1.1.0-2_amd64.deb
 e8dcf8f8602b99b7c2436d005219d8097d3c04ca 51166 
liblo10k1-0-dbgsym_1.1.0-2_amd64.deb
 a145a0714d7a37d13ee57370f3bc27b95956f1fc 34198 liblo10k1-0_1.1.0-2_amd64.deb
 8e84c7f76de5397b06c6554ada8ac1863cc98195 20902 

Bug#838418: libreoffice-gtk3: Font corruption - both content and dialogs

[Simon John]

Package: libreoffice-gtk3
Version: 1:5.2.1-3
Severity: grave
Justification: renders package unusable

Dear Maintainer,

   * What led up to the situation?

Upgrade of libreoffice. It was definitely working fine on August 16th,
then I haven't done any upgrades until this last week, so I suspect the
move from 5.2.0 to 5.2.1

   * What exactly did you do (or not do) that was effective (or
ineffective)?

Loaded a spreadsheet, then changed a filter or preference that caused
the display to refresh.

   * What was the outcome of this action?

Cell content was illegible - sometimes just garbarge, sometimes the
characters were replaced with other (random?) characters, sometimes some
characters were emboldened.

Also dialog boxes were corrupted - such as the save/discard/cancel
buttons, and even the text in the input line.

I tried various things - deleting the user profile, running as root,
rolling back to 5.2.1-1, reinstalling fonts, nothing worked other than
uninstalling libreoffice-gtk3.

Its not a driver issue as I get the same problem on Nvidia (nouveau)
desktop and Intel laptop.



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

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

Versions of packages libreoffice-gtk3 depends on:
ii  dpkg  1.18.10
ii  libatk1.0-0   2.22.0-1
ii  libc6 2.24-3
ii  libcairo-gobject2 1.14.6-1+b1
ii  libcairo2 1.14.6-1+b1
ii  libdbus-1-3   1.10.10-1
ii  libdbus-glib-1-2  0.108-1
ii  libgcc1   1:6.2.0-4
ii  libgdk-pixbuf2.0-02.36.0-1
ii  libgl1-mesa-glx [libgl1]  12.0.3-1
ii  libglew2.02.0.0-3
ii  libglib2.0-0  2.49.7-1
ii  libglu1-mesa [libglu1]9.0.0-2.1
ii  libgtk-3-03.21.6-1
ii  libice6   2:1.0.9-1+b1
ii  libpango-1.0-01.40.2-1
ii  libpangocairo-1.0-0   1.40.2-1
ii  libreoffice-core  1:5.2.1-3
ii  libsm62:1.2.2-1+b1
ii  libstdc++66.2.0-4
ii  libx11-6  2:1.6.3-1
ii  libxext6  2:1.3.3-1
ii  uno-libs3 5.2.1-3
ii  ure   5.2.1-3

Versions of packages libreoffice-gtk3 recommends:
ii  libreoffice-style-tango  1:5.2.1-3

Versions of packages libreoffice-gtk3 suggests:
ii  libreofficekit-data  1:5.2.1-3

-- no debconf information

Bug#837524: marked as done (psychtoolbox-3: FTBFS: cp: cannot stat 'moglcore.mex': No such file or directory)

[Debian Bug Tracking System]

Your message dated Tue, 20 Sep 2016 22:28:41 +
with message-id 
and subject line Bug#837524: fixed in psychtoolbox-3 3.0.13.20160910.dfsg1-1
has caused the Debian Bug report #837524,
regarding psychtoolbox-3: FTBFS: cp: cannot stat 'moglcore.mex': No such file 
or directory
to be marked as done.

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

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


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

psychtoolbox-3 fails to build from source in unstable/amd64:

  [..]

  gl_auto.c: In function 'glut_soliddodecahedron':
  gl_auto.c:5297:11: warning: the comparison will always evaluate as 'false' 
for the address of 'glutSolidDodecahedron' will never be NULL [-Waddress]
if (NULL == glutSolidDodecahedron) 
mogl_glunsupported("glutSolidDodecahedron");
 ^~
  gl_auto.c: In function 'glut_wireteapot':
  gl_auto.c:5304:11: warning: the comparison will always evaluate as 'false' 
for the address of 'glutWireTeapot' will never be NULL [-Waddress]
if (NULL == glutWireTeapot) mogl_glunsupported("glutWireTeapot");
 ^~
  gl_auto.c: In function 'glut_solidteapot':
  gl_auto.c:5311:11: warning: the comparison will always evaluate as 'false' 
for the address of 'glutSolidTeapot' will never be NULL [-Waddress]
if (NULL == glutSolidTeapot) mogl_glunsupported("glutSolidTeapot");
 ^~
  gl_auto.c: In function 'glut_wireoctahedron':
  gl_auto.c:5318:11: warning: the comparison will always evaluate as 'false' 
for the address of 'glutWireOctahedron' will never be NULL [-Waddress]
if (NULL == glutWireOctahedron) mogl_glunsupported("glutWireOctahedron");
 ^~
  gl_auto.c: In function 'glut_solidoctahedron':
  gl_auto.c:5325:11: warning: the comparison will always evaluate as 'false' 
for the address of 'glutSolidOctahedron' will never be NULL [-Waddress]
if (NULL == glutSolidOctahedron) mogl_glunsupported("glutSolidOctahedron");
 ^~
  gl_auto.c: In function 'glut_wiretetrahedron':
  gl_auto.c:5332:11: warning: the comparison will always evaluate as 'false' 
for the address of 'glutWireTetrahedron' will never be NULL [-Waddress]
if (NULL == glutWireTetrahedron) mogl_glunsupported("glutWireTetrahedron");
 ^~
  gl_auto.c: In function 'glut_solidtetrahedron':
  gl_auto.c:5339:11: warning: the comparison will always evaluate as 'false' 
for the address of 'glutSolidTetrahedron' will never be NULL [-Waddress]
if (NULL == glutSolidTetrahedron) 
mogl_glunsupported("glutSolidTetrahedron");
 ^~
  gl_auto.c: In function 'glut_wireicosahedron':
  gl_auto.c:5346:11: warning: the comparison will always evaluate as 'false' 
for the address of 'glutWireIcosahedron' will never be NULL [-Waddress]
if (NULL == glutWireIcosahedron) mogl_glunsupported("glutWireIcosahedron");
 ^~
  gl_auto.c: In function 'glut_solidicosahedron':
  gl_auto.c:5353:11: warning: the comparison will always evaluate as 'false' 
for the address of 'glutSolidIcosahedron' will never be NULL [-Waddress]
if (NULL == glutSolidIcosahedron) 
mogl_glunsupported("glutSolidIcosahedron");
 ^~
  gl_auto.c: In function 'gl_clearnamedframebufferfv':
  gl_auto.c:9159:3: warning: passing argument 4 of 
'__glewClearNamedFramebufferfv' discards 'const' qualifier from pointer target 
type [-Wdiscarded-qualifiers]
 (const GLfloat*)mxGetData(prhs[3]));
 ^
  gl_auto.c:9159:3: note: expected 'GLfloat * {aka float *}' but argument is of 
type 'const GLfloat * {aka const float *}'
  In file included from mogltypes.h:45:0,
   from gl_auto.c:9:
  gl_auto.c: In function 'gl_clearnamedframebufferfi':
  gl_auto.c:9166:2: error: too few arguments to function 
'__glewClearNamedFramebufferfi'
glClearNamedFramebufferfi((GLuint)mxGetScalar(prhs[0]),
^
  gl_auto.c: In function 'gl_multidrawarraysindirectcountarb':
  gl_auto.c:10360:3: warning: passing argument 2 of 
'__glewMultiDrawArraysIndirectCountARB' makes pointer from integer without a 
cast [-Wint-conversion]
 (GLintptr)mxGetScalar(prhs[1]),
 ^
  gl_auto.c:10360:3: note: expected 'const void *' but argument is of type 
'long int'
  gl_auto.c: In function 'gl_multidrawelementsindirectcountarb':
  gl_auto.c:10372:3: warning: 

Bug#793369: marked as done (jai-core: FTBFS - JPEGImageDecoder.java:29: error: package com.sun.image.codec.jpeg does not exist)

[Debian Bug Tracking System]

Your message dated Tue, 20 Sep 2016 22:14:42 +
with message-id 
and subject line Bug#838062: Removed package(s) from unstable
has caused the Debian Bug report #793369,
regarding jai-core: FTBFS - JPEGImageDecoder.java:29: error: package 
com.sun.image.codec.jpeg does not exist
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.)


-- 
793369: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=793369
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: jai-core
Version: 1.1.4-3
Severity: serious
Tags: jessie sid stretch
Justification: fails to build from source

from a rebuild in a clean jessie pbuilder environment (full log
attached):

[...]
compilation:
[mkdir] Created dir: 
/tmp/buildd/jai-core-1.1.4/build/linux-amd64/opt/classes
 [copy] Copying 5 files to /tmp/buildd/jai-core-1.1.4/build/linux-amd64/opt
[javac] /tmp/buildd/jai-core-1.1.4/build.xml:633: warning: 
'includeantruntime' was not set, defaulting to build.sysclasspath=last; set to 
false for repeatable builds
[javac] Compiling 829 source files to 
/tmp/buildd/jai-core-1.1.4/build/linux-amd64/opt/classes
[javac] warning: [options] bootstrap class path not set in conjunction with 
-source 1.3
[javac] 
/tmp/buildd/jai-core-1.1.4/src/share/classes/com/sun/media/jai/codecimpl/JPEGImageDecoder.java:29:
 error: package com.sun.image.codec.jpeg does not exist
[javac] import com.sun.image.codec.jpeg.ImageFormatException;
[javac]^
[javac] 
/tmp/buildd/jai-core-1.1.4/src/share/classes/com/sun/media/jai/codecimpl/JPEGImageEncoder.java:35:
 error: package com.sun.image.codec.jpeg does not exist
[javac] import com.sun.image.codec.jpeg.JPEGQTable;
[javac]^
[javac] 
/tmp/buildd/jai-core-1.1.4/src/share/classes/com/sun/media/jai/codecimpl/JPEGImageEncoder.java:36:
 error: package com.sun.image.codec.jpeg does not exist
[javac] import com.sun.image.codec.jpeg.JPEGDecodeParam;
[javac]^
[javac] 
/tmp/buildd/jai-core-1.1.4/src/share/classes/com/sun/media/jai/codecimpl/JPEGImageEncoder.java:68:
 error: package com.sun.image.codec.jpeg does not exist
[javac]   com.sun.image.codec.jpeg.JPEGEncodeParam j2dEP,
[javac]   ^
[javac] 
/tmp/buildd/jai-core-1.1.4/src/share/classes/com/sun/media/jai/codecimpl/TIFFImage.java:53:
 error: package com.sun.image.codec.jpeg does not exist
[javac] import com.sun.image.codec.jpeg.JPEGCodec;
[javac]^
[javac] 
/tmp/buildd/jai-core-1.1.4/src/share/classes/com/sun/media/jai/codecimpl/TIFFImage.java:54:
 error: package com.sun.image.codec.jpeg does not exist
[javac] import com.sun.image.codec.jpeg.JPEGDecodeParam;
[javac]^
[javac] 
/tmp/buildd/jai-core-1.1.4/src/share/classes/com/sun/media/jai/codecimpl/TIFFImage.java:55:
 error: package com.sun.image.codec.jpeg does not exist
[javac] import com.sun.image.codec.jpeg.JPEGImageDecoder;
[javac]^
[javac] 
/tmp/buildd/jai-core-1.1.4/src/share/classes/com/sun/media/jai/codecimpl/TIFFImage.java:114:
 error: cannot find symbol
[javac] JPEGDecodeParam decodeParam = null;
[javac] ^
[javac]   symbol:   class JPEGDecodeParam
[javac]   location: class TIFFImage
[javac] 
/tmp/buildd/jai-core-1.1.4/src/share/classes/com/sun/media/jai/codecimpl/TIFFImage.java:146:
 error: cannot find symbol
[javac]JPEGDecodeParam 
decodeParam,
[javac]^
[javac]   symbol:   class JPEGDecodeParam
[javac]   location: class TIFFImage
[...]


Andreas


jai-core_1.1.4-3.log.gz
Description: application/gzip
--- End Message ---
--- Begin Message ---
Version: 1.1.4-3+rm

Dear submitter,

as the package jai-core 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/838062

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.
Chris Lamb (the ftpmaster behind the 

Bug#837940: gnome-twitch-player-backend-mpv-opengl: immediate segmentation fault

[Tim Dengel]

Hi Jonas,

since apparently replies to bugs are not automatically sent to the
submitter, you probably didn't get my previous message. Sorry for that :(

Anyways, here it is:



On Thu, 15 Sep 2016 19:58:39 +0200 Jonas Smedegaard  wrote:
> Package: gnome-twitch-player-backend-mpv-opengl
> Version: 0.3.0-1
> Severity: grave
> Justification: renders package unusable
>
> Selecting mpv backend immediately causes segmentation fault.

Hi Jonas,

I can not reproduce this. Can you provide one (or more) of the following
things?

1. Log messages (i.e. run gnome-twitch in a terminal, maybe with a lower
logging level by giving it "--log-level=debug" or something as an argument)

2. A backtrace (install the dbgsym packages for gnome-twitch and
gnome-twitch-player-backend-mpv-opengl and run gnome-twitch in gdb, then
get a full backtrace with the "bt full" command.

3. A core dump (I would rather prefer the first two, if they are meaningful)

It would also be interesting to know what kind of graphics hardware you
have (Intel, NVIDIA, AMD...) and if you have tried other backends (and
whether they work). From your report it seems that the segfault happens
directly on selecting the backend, not on playback, is that correct?
Were you selecting it from the settings dialog[1] outside of a stream,
or when you were prompted to select one when trying to watch a stream?
Does the same happen when you try the other one of the two methods?

Sincerely,
Tim Dengel


[1] You can reach that dialog by clicking on the "gnome-twitch" item in
gnome's "task bar" and then selecting "settings"

Processed: Re: gpick: colors.txt is non-free

[Debian Bug Tracking System]

Processing control commands:

> found -1 gpick/0.2.4-1
Bug #838414 [gpick] gpick: colors.txt is non-free
Marked as found in versions gpick/0.2.4-1.

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

Bug#838414: gpick: colors.txt is non-free

[Francesco Poli]

Control: found -1 gpick/0.2.4-1


On Tue, 20 Sep 2016 23:46:04 +0200 Francesco Poli (wintermute) wrote:

> Package: gpick
> Version: 0.2.5-2

I see that the non-free restriction is not new: I am therefore marking
this bug as found in the oldstable version of the package...


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


pgpTephnmFRFk.pgp
Description: PGP signature

Bug#838415: Wrong package name, installs typelib file into wrong directory

[Michael Biebl]

Package: gir1.2-urfkill-glib0
Version: 0.5.0-4
Severity: serious

Hi,

please follow /usr/share/doc/gobject-introspection/policy.txt when
package typelib files.

In case of gir1.2-urfkill-glib0, debian/gir1.2-urfkill-glib0.install is
broken and installs the files as
/usr/lib/Urfkill-0.5.typelib

Since multiarch paths are allowed for typelib files, just use
usr/lib/*/girepository-1.0/Urfkill-*.typelib

Please also name the package accordingly, in your case, this would be
gir1.2-urfkill-0.5

Last but not least, you need to use the gir addon via

dh $@ --with gir




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

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

Bug#838414: gpick: colors.txt is non-free

[Francesco Poli (wintermute)]

Package: gpick
Version: 0.2.5-2
Severity: serious
Justification: Policy 2.2.1


Hello and thanks for maintaining this little tool in Debian!

I noticed that the license for file share/gpick/colors.txt fails
to meet the DFSG, as it includes at least one non-free restriction.
Clause 5 states:

|  5. These RGB colour formulations may not be used to the detriment of
|  Resene Paints Ltd.

This is a non-free restriction on use, which does not comply with
DFSG#6 (No Discrimination Against Fields of Endeavor).

This file is therefore unfit for the main Debian archive.

Possible solutions I can think of:

 A) get in touch with the colors.txt copyright holders (Resene Paints
Ltd.) and persuade them to drop the troublesome clause or, even
better, to re-license the file under well-known and widely used
DFSG-free terms (such as, for instance, the 3-clause BSD license
adopted by the rest of gpick)

 B) find a DFSG-free replacement for share/gpick/colors.txt and use it
in stead of the non-free one

 C) drop share/gpick/colors.txt from the package, if possible

 D) move the gpick package to the non-free archive (I hope this will
*not* happen!)

I hope solution A may be persued soon.
Solution B (or C) may be chosen as a temporary quick fix, while trying
to achieve solution A.

Thanks for your time!
Bye.

Processed (with 2 errors): I cannot reproduce it

[Debian Bug Tracking System]

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

> tags 830178 + unreproducible
Bug #830178 [src:mako] mako: FTBFS: ValueError: too many values to unpack
Added tag(s) unreproducible.
> severity 830178 important
Bug #830178 [src:mako] mako: FTBFS: ValueError: too many values to unpack
Severity set to 'important' from 'serious'
> It works fine for me (and I tested both mako and sqlalchemy with new
Unknown command or malformed arguments to command.
> zzzeeksphinx)
Unknown command or malformed arguments to command.
>
End of message, stopping processing here.

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

Processed: Re: Bug#811674: FTBFS with GCC 6: multiple errors

[Debian Bug Tracking System]

Processing control commands:

> tags -1 patch
Bug #811674 [ceph] FTBFS with GCC 6: multiple errors
Added tag(s) patch.

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

Bug#811674: FTBFS with GCC 6: multiple errors

[Vincent Lefevre]

Control: tags -1 patch

On 2016-09-19 17:12:17 +0200, Emilio Pozuelo Monfort wrote:
> On Tue, 19 Jan 2016 16:50:22 -0800 Martin Michlmayr  wrote:
> > 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.
> 
> Any news on this? This is blocking the boost1.58 removal, which in
> turn is blocking the ongoing openmpi transition. I'd appreciate if
> you could take a look at this.

The main difference between GCC 6 and the previous version for C++ is:

  The default mode for C++ is now -std=gnu++14 instead of -std=gnu++98.

(from https://gcc.gnu.org/gcc-6/changes.html), as incompatible changes
have been introduced in the new C++ standard.

This seems to be the cause of the failure here. One simple solution,
IMHO, is to switch back to -std=gnu++98. This is what the attached
patch does. I was not sure where to put -std=gnu++98, but with what
I did, it applies only to GCC, not to clang. So, I suppose that this
is what is expected. On my machine, ceph builds without any error
with this patch, but I have not tested the behavior when installed
(I don't see why there would be any new problem).

I don't think it would be worth to try to make this version C++14
compliant while there is a new version upstream (see the package in
experimental, for instance).

-- 
Vincent Lefèvre  - Web: 
100% accessible validated (X)HTML - Blog: 
Work: CR INRIA - computer arithmetic / AriC project (LIP, ENS-Lyon)
Index: ceph-0.80.11/src/Makefile-env.am
===
--- ceph-0.80.11.orig/src/Makefile-env.am
+++ ceph-0.80.11/src/Makefile-env.am
@@ -80,7 +80,7 @@ AM_CXXFLAGS = \
-Wnon-virtual-dtor \
-Wno-invalid-offsetof
 if !CLANG
-   AM_CXXFLAGS += -Wstrict-null-sentinel
+   AM_CXXFLAGS += -Wstrict-null-sentinel -std=gnu++98
 endif
 
 # note: this is position dependant, it affects the -l options that

Bug#825800: graphicsmagick: CVE-2016-5118

[Carsten Leonhardt]

László Böszörményi (GCS)  writes:

> On Tue, Sep 20, 2016 at 9:56 AM, Stephan Großberndt
>  wrote:

>> Do you think 1.3.25-2 might be the used for a stable update?
>  Upgrade to a newer version in stable is not easy and I can remember
> one, maybe two cases when it was allowed.
> In this case I'm not sure it should be the path.

It's done regularly with MySQL, so I'd say asking the release team
wouldn't hurt.

 - Carsten

Bug#838336: gnome-control-center: Keybinding panel fail to open

[Michael Biebl]

Am 20.09.2016 um 11:37 schrieb Raphael Hertzog:
> Hi,
> 
> On Tue, 20 Sep 2016, Michael Biebl wrote:
>>> (gnome-control-center:24830): Gtk-CRITICAL **: Error building template
>>> class 'CcKeyboardPanel' for an instance of type 'CcKeyboardPanel':
>>> .:2:1622 Invalid property: GtkScrolledWindow.propagate_natural_width
>> ...
>>> Versions of packages gnome-control-center depends on:
>>> ii  libgtk-3-0 3.21.5-3
>>
>> Does upgrading libgtk-3-0 to 3.21.6-1 fix the problem?
> 
> Yes. I already had a similar report on the Kali side:
> https://bugs.kali.org/view.php?id=3579
> 
> But gtk+3.0 3.21.6 is tangled with the libc6 transition
> right now and it doesn't migrate although it should since
> it has waited 5 days already.
> 
> It might make sense to do a quick tpu upload to get fixes in testing?

You have my ok to do so.


-- 
Why is it that all of the instruments seeking intelligent life in the
universe are pointed away from Earth?



signature.asc
Description: OpenPGP digital signature

Processed: affects

[Debian Bug Tracking System]

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

> affects 837618 src:gnustep-base
Bug #837618 [xml-core] docbook-slides: FTBFS: dh_installxmlcatalogs: Unexpected 
debhelper version format
Bug #837620 [xml-core] w3-dtd-mathml: FTBFS: dh_installxmlcatalogs: Unexpected 
debhelper version format
Bug #837745 [xml-core] sgml-data: FTBFS: dh_installxmlcatalogs: Unexpected 
debhelper version format
Added indication that 837618 affects src:gnustep-base
Added indication that 837620 affects src:gnustep-base
Added indication that 837745 affects src:gnustep-base
>
End of message, stopping processing here.

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

Bug#838336: gnome-control-center: Keybinding panel fail to open

[Mathieu R.]

2016-09-20 5:37 GMT-04:00 Raphael Hertzog :

>
> > Does upgrading libgtk-3-0 to 3.21.6-1 fix the problem?
>
>
Upgrading it from sid work

Processed: openbabel: FTBFS on mips,mips64el: internal compiler errors

[Debian Bug Tracking System]

Processing control commands:

> block 830200 with -1
Bug #830200 [release.debian.org] transition: perl
830200 was blocked by: 825524 834249 825609 825012 834796 825231 825014 836636 
837719 834798 825762 834800 834795 834799 834797
830200 was not blocking any bugs.
Added blocking bug(s) of 830200: 838394

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

Bug#838394: openbabel: FTBFS on mips,mips64el: internal compiler errors

[Niko Tyni]

Package: openbabel
Version: 2.3.2+dfsg-2.4
Severity: serious
Control: block 830200 with -1

This package failed to build on mips and mips64el.

- on mips:
"c++: internal compiler error: Segmentation fault (program cc1plus)"
https://buildd.debian.org/status/fetch.php?pkg=openbabel=mips=2.3.2%2Bdfsg-2.4=1474379322

- on mips64el:
"openbabel-perl.cpp:17073:86: internal compiler error: in df_reg_chain_unlink, 
at df-scan.c:790"
https://buildd.debian.org/status/fetch.php?pkg=openbabel=mips64el=2.3.2%2Bdfsg-2.4=1474385515

I'm running test builds on the porter boxes to see if these are
reproducible there and to gather data for gcc bug reports.

This blocks the Perl 5.24 transition so workarounds such as temporarily
building with an older compiler may be desirable.
-- 
Niko Tyni   nt...@debian.org

Processed: Re: [Debichem-devel] Bug#838299: Bug#838299: espresso: FTBFS on various arches: test suite hangs

[Debian Bug Tracking System]

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

> tags 838299 +pending
Bug #838299 [src:espresso] espresso: FTBFS on various arches: test suite hangs
Added tag(s) pending.
> thanks
Stopping processing here.

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

Bug#838299: [Debichem-devel] Bug#838299: Bug#838299: espresso: FTBFS on various arches: test suite hangs

[Michael Banck]

tags 838299 +pending
thanks

Hi,

On Tue, Sep 20, 2016 at 07:07:18PM +0200, Graham Inggs wrote:
> On 20 September 2016 at 16:03, Emilio Pozuelo Monfort  
> wrote:
> > I gave it back on armhf/mips* and it failed again. This time with 
> > libopenmpi2:
> >
> > https://buildd.debian.org/status/package.php?p=espresso

They changed the test suite setup, so now it does not print the tests as
they are being run anymore.

Which means the whole testsuite is run without output, timing out on the
slower autobuilders.

I've committed a patch to svn just now to run their python script in
verbose mode, which should at least address this; of course really slow
architectures might still timeout on one particularly long running test.

Will upload once the build looks good.


Michael

Bug#824011: marked as done (warzone2100: FTBFS in testing (maybe missing Build-Conflicts))

[Debian Bug Tracking System]

Your message dated Tue, 20 Sep 2016 19:19:50 +
with message-id 
and subject line Bug#824011: fixed in warzone2100 3.2.1-1
has caused the Debian Bug report #824011,
regarding warzone2100: FTBFS in testing (maybe missing Build-Conflicts)
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.)


-- 
824011: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=824011
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: warzone2100
Version: 3.1.1-3
Severity: serious

Dear maintainer:

This package fails to build from source in stretch:

-
 debian/rules build
dh build --parallel --with autoreconf
   dh_testdir
   dh_update_autotools_config
   debian/rules override_dh_autoreconf
make[1]: Entering directory '/<>'
dh_autoreconf ./autogen.sh
+ checking for automake >= 1.12 ... found 1.15, ok.
Sorry, automake 1.12+ is not supported yet, please use 1.11.
dh_autoreconf: ./autogen.sh returned exit code 1
debian/rules:10: recipe for target 'override_dh_autoreconf' failed
make[1]: *** [override_dh_autoreconf] Error 2
make[1]: Leaving directory '/<>'
debian/rules:7: recipe for target 'build' failed
make: *** [build] Error 2
dpkg-buildpackage: error: debian/rules build gave error exit status 2
-

The full build log is attached.

Note: My stretch chroot has debhelper installed by default to save
some time, so it has "automake" installed by default. If the package
does not build when "automake" is installed, then it should use a
Build-Conflicts.

Thanks.

warzone2100_3.1.1-3_amd64-20160511-1125.gz
Description: application/gzip
--- End Message ---
--- Begin Message ---
Source: warzone2100
Source-Version: 3.2.1-1

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

Debian distribution maintenance software
pp.
Markus Koschany  (supplier of updated warzone2100 package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Tue, 20 Sep 2016 20:34:59 +0200
Source: warzone2100
Binary: warzone2100 warzone2100-data warzone2100-music
Architecture: source
Version: 3.2.1-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Games Team 
Changed-By: Markus Koschany 
Description:
 warzone2100 - 3D real time strategy game
 warzone2100-data - data files for warzone2100
 warzone2100-music - official music for warzone2100
Closes: 814248 824011
Changes:
 warzone2100 (3.2.1-1) unstable; urgency=medium
 .
   * Team upload.
 .
   [ Russell Coker ]
   * New upstream version 3.2.1. (Closes: #814248)
   * Build-depend on qtbase5-dev qtscript5-dev libsdl2-dev instead of
 libqt4-dev.
   * Patch for too many parameters for upnpDiscover() to fix a FTBFS.
   * Change patches to apply to latest upstream.
   * Update revert-372eff6693e633e8d0d1d0b8a9ceb996a5c3f49f.patch and call
 automake1.11 directly. (Closes: #824011)
 .
   [ Markus Koschany ]
   * Add missing libssl-dev to Build-Depends.
   * Disable the tests by overriding dh_auto_test and work around a FTBFS.
   * Use compat level 10.
   * d/rules: Pass --with-appdatadir option to dh_auto_configure.
   * Add appdata.patch and install the missing appdata file.
   * Remove libsdl1.2-dev from B-D.
   * Use embedded version of glm to build the game because Debian's version
 causes graphical glitches (rotating units). It also does not provide a
 shared library which might cause further work in the future.
   * Update debian/copyright for new release.
   * Update debian/clean and ensure that the package can be built twice in a
 row.
   * Remove wkhtmltopdf from Build-Depends and add quickstartguide.patch for now
 because building the pdf documentation from source is causing a FTBFS at 
the
 moment.
   * d/rules: Replace --disable-debug with --enable-debug=no. The former option
 did nothing.
Checksums-Sha1:
 926255e63f0bf07e70fbc5e3f461542b981612b0 

Processed: Re: Caused by libgtk-3-0 3.21

[Debian Bug Tracking System]

Processing control commands:

> tags 836426 + upstream
Bug #836426 [libgtk-3-0] GTK+ 3.21 causes application redraw issues and 
warnings ("is drawn without a current allocation")
Bug #832077 [libgtk-3-0] GTK+ 3.21 causes application redraw issues and 
warnings ("is drawn without a current allocation")
Added tag(s) upstream.
Added tag(s) upstream.
> forwarded 836426 https://bugzilla.gnome.org/show_bug.cgi?id=771739
Bug #836426 [libgtk-3-0] GTK+ 3.21 causes application redraw issues and 
warnings ("is drawn without a current allocation")
Bug #832077 [libgtk-3-0] GTK+ 3.21 causes application redraw issues and 
warnings ("is drawn without a current allocation")
Set Bug forwarded-to-address to 
'https://bugzilla.gnome.org/show_bug.cgi?id=771739'.
Set Bug forwarded-to-address to 
'https://bugzilla.gnome.org/show_bug.cgi?id=771739'.

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

Bug#835910: marked as done (warzone2100: FTBFS when newer automake is installed)

[Debian Bug Tracking System]

Your message dated Tue, 20 Sep 2016 19:19:50 +
with message-id 
and subject line Bug#824011: fixed in warzone2100 3.2.1-1
has caused the Debian Bug report #824011,
regarding warzone2100: FTBFS when newer automake is installed
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.)


-- 
824011: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=824011
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: warzone2100
Version: 3.1.1-3
Severity: serious
Tags: upstream patch
Justification: fails to build from source (but built successfully in the past)

The warzone2100 build system insists on automake and aclocal version 1.11.  If
you have 1.15 installed it won't build.

The following patch makes it build when you have a version of automake newer
than 1.11 installed and the links automake and aclocal pointing to the newer
versions (as is the default when multiple versions are installed).

While it is possible to purge newer versions of automake from your system
before starting a build this shouldn't be required and doesn't work well if
your system is used for building packages that depend on newer versions of
automake.

I think this should be included in Unstable to make things easier for everyone
who wants to work on this package.  The same patch is needed for version 3.2.1.

Index: warzone2100-3.1.1/autogen.sh
===
--- warzone2100-3.1.1.orig/autogen.sh
+++ warzone2100-3.1.1/autogen.sh
@@ -148,13 +148,13 @@ not_version ()
 # Chdir to the srcdir, then run auto* tools.
 cd "$SRCDIR"
 
-version_check 0 "automake" "ftp://ftp.gnu.org/pub/gnu/automake/; 1 12 && {
+version_check 0 "automake-1.11" "ftp://ftp.gnu.org/pub/gnu/automake/; 1 12 && {
   echo "Sorry, automake 1.12+ is not supported yet, please use 1.11."
   exit 1
 }
 
 version_check 1 "autoconf" "ftp://ftp.gnu.org/pub/gnu/autoconf/; 2 56 || DIE=1
-version_check 1 "automake" "ftp://ftp.gnu.org/pub/gnu/automake/; 1 11 || DIE=1
+version_check 1 "automake-1.11" "ftp://ftp.gnu.org/pub/gnu/automake/; 1 11 || 
DIE=1
 if [ "$DIE" -eq 1 ]; then
   exit 1
 fi
@@ -164,10 +164,10 @@ fi
   exit 1
 }
 
-echo "+ running aclocal ..."
-aclocal -I m4 || {
+echo "+ running aclocal-1.11 ..."
+aclocal-1.11 -I m4 || {
   echo
-  echo "aclocal failed - check that all needed development files are present 
on system"
+  echo "aclocal-1.11 failed - check that all needed development files are 
present on system"
   exit 1
 }
 echo "+ running autoheader ... "
@@ -182,10 +182,10 @@ autoconf || {
   echo "autoconf failed"
   exit 1
 }
-echo "+ running automake ... "
-automake -a -c --foreign || {
+echo "+ running automake-1.11 ... "
+automake-1.11 -a -c --foreign || {
   echo
-  echo "automake failed"
+  echo "automake-1.11 failed"
   exit 1
 }
 

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

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

Versions of packages warzone2100 depends on:
ii  libc6 2.23-5
ii  libfontconfig12.11.0-6.7
ii  libfreetype6  2.6.3-3+b1
ii  libfribidi0   0.19.7-1
ii  libgcc1   1:6.2.0-1
ii  libgl1-mesa-glx [libgl1]  11.2.2-1
ii  libglc0   0.7.2-5+b3
ii  libglew1.13   1.13.0-2
ii  libglu1-mesa [libglu1]9.0.0-2.1
ii  libminiupnpc101.9.20140610-2.1
ii  libogg0   1.3.2-1
ii  libopenal11:1.17.2-1
ii  libphysfs12.0.3-3
ii  libpng16-16   1.6.24-2
ii  libqt4-network4:4.8.7+dfsg-8
ii  libqt4-script 4:4.8.7+dfsg-8
ii  libqtcore44:4.8.7+dfsg-8
ii  libsdl1.2debian   1.2.15+dfsg1-4
ii  libstdc++66.2.0-1
ii  libtheora01.1.1+dfsg.1-14
ii  libvorbis0a   1.3.5-3
ii  libvorbisfile31.3.5-3
ii  libx11-6  2:1.6.3-1
ii  libxrandr22:1.5.0-1
ii  warzone2100-data  3.1.1-3
ii  zlib1g1:1.2.8.dfsg-2+b1

Versions of packages warzone2100 recommends:
ii  warzone2100-music  3.1.1-3

warzone2100 suggests no packages.

-- no debconf information
--- End Message ---
--- Begin Message ---
Source: warzone2100
Source-Version: 3.2.1-1

We believe that the bug you reported is fixed in the latest version of
warzone2100, which is due to 

Bug#836426: Caused by libgtk-3-0 3.21

[Josh Triplett]

Control: tags 836426 + upstream
Control: forwarded 836426 https://bugzilla.gnome.org/show_bug.cgi?id=771739

On Tue, Sep 20, 2016 at 08:13:43PM +0200, Michael Biebl wrote:
> Am 20.09.2016 um 19:38 schrieb Josh Triplett:
> > On Thu, Sep 08, 2016 at 01:48:01PM +0200, Michael Biebl wrote:
> >> As for gnome-boxes, can you reproduce the problem with 3.21.3 from
> >> unstable? I just tested a local installation of debian 8.5 and that
> >> worked fine. I don't have  windows ISO to test whether that is
> >> reproducible with that setup.
> > 
> > I can confirm that this bug in libgtk-3-0 still affects gnome-boxes
> > 3.22.0-1 from latest sid.  (Tested with libgtk-3-0 3.21.6-1 .)
> > Downgrading libgtk-3-0 from 3.21.6-1 to 3.20.9-1 allows gnome-boxes to
> > render correctly again.
> > 
> > You might be able to reproduce this problem if you run the QXL graphics
> > driver (xserver-xorg-video-qxl) in the guest, and potentially the guest
> > agent as well.
> > 
> > I can reliably reproduce this with a Windows VM running the QXL driver
> > and guest agent.
> 
> Please file such issues upstream.

Done.

Bug#825800: graphicsmagick: CVE-2016-5118

[Bob Friesenhahn]

On Tue, 20 Sep 2016, László Böszörményi wrote:



Do you think 1.3.25-2 might be the used for a stable update?

Upgrade to a newer version in stable is not easy and I can remember
one, maybe two cases when it was allowed.
In this case I'm not sure it should be the path.


1.3.25 is the "fix" for security issues in previous versions.  1.3.20 
is the last release in the calm before GraphicsMagick entered Coverity 
testing (resulting in hundreds of changes) and the availability of 
ASAN and the subsequent flood of problem files from security 
researchers using fuzzers like American Fuzzy-Lop, which I fixed as 
quickly as I could.


There are hundreds of known files (many publically available) which 
might cause 1.3.20 to crash or consume immense resources.


Unfortunately there was a small ABI break in Magick++ (in 1.3.21) and 
I did bump its library major version number and reset age.


Bob
--
Bob Friesenhahn
bfrie...@simple.dallas.tx.us, http://www.simplesystems.org/users/bfriesen/
GraphicsMagick Maintainer,http://www.GraphicsMagick.org/

Bug#821688: marked as done (src:libpuzzle: PHP 7.0 Transition)

[Debian Bug Tracking System]

Your message dated Tue, 20 Sep 2016 18:19:06 +
with message-id 
and subject line Bug#821688: fixed in libpuzzle 0.11-1
has caused the Debian Bug report #821688,
regarding src:libpuzzle: PHP 7.0 Transition
to be marked as done.

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

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


-- 
821688: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=821688
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:libpuzzle
Severity: important
User: pkg-php-ma...@lists.alioth.debian.org
Usertags: php7.0-transition

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Dear maintainer(s),

this bug is a part of ongoing php7.0 transition.  It is filled as
important, but the severity will be bumped to serious within quite short
(~month) timeframe as the transition was announced almost 3 months ago.

The libpuzzle package currently build-depends on php5 php5-dev .

PHP 7.0 has landed in unstable with substantial changes to the packaging:

  1. Every package built from src:phpMAJOR.MINOR now include
 phpMAJOR.MINOR in the name, so f.e. php5-fpm is now php7.0-fpm.

  2. Accompanying src:php-defaults builds 1:1 mapping to a default
 MAJOR.MINOR version, e.g. php-fpm depends on php7.0-fpm.  When you
 specify a dependency, please use the generic name, unless you
 absolutely know that won't work for you.

  3. Every path in the system has been changed to a versioned, e.g.
 /etc/php5/cli is now /etc/php/7.0/cli

  4. dh_php5 is now dh_php

  5. php-pear is not built from independent source package.

  6. master-7.0 branches of several extensions (php-apcu, xdebug,
 php-apcu-bc) can be used as a template how to change the PHP
 extension packaging.  It's mostly cut since the d/rules tries
 to figure-out most of the variables from debian/ directory.

  7. pkg-php-tools package now supports PHP 7.0 packaging and if your
 package uses pkg-php-tools a simple binNMU is all it might need

  8. PHP 7.0 has changed extension API, so most-if-not-all extensions
 need work from upstream to be compatible with PHP 7.0.

  9. We expect to ship next Debian release (stretch) only with PHP
 7.0, that means that all packages needs to be made compatible with
 PHP 7.0.  Fortunately the PHP 7.0 is mostly compatible with properly
 maintained software.  However some extensions has been deprecated
 (f.e. mysql) and thus old unmaintained software will stop working
 and it will have to be either patched or removed from stable Debian.

So what you need to do:

Replace every occurence of php5 with just php, e.g. if you depend on
'php5' then you just need to depend on 'php'.  Also if you package a web
application and depend on specific SAPI, I would recommend depending just
on 'php' package and let the user decide whether he will install php-fpm,
libapache2-mod-php or php-cgi.

The script that was used to get the list of packages for MBF was not a
particular smart one (so it doesn't detect alternatives, etc.), so if
there's a false positive, please excuse me and just close the bug with
short explanation.

The other options that might be used with packages that don't and won't
support PHP 7.0 is to remove the software from Debian by changing the
title of this bugreport to:

RM: libpuzzle -- ROM; doesn't support PHP 7.0

reassigning it to ftp.debian.org pseudo-package and changing severity to
'normal'.

Also feel free to contact the maintainers at one of the lists:

pkg-php-p...@lists.alioth.debian.org -- for PEAR related packages
pkg-php-p...@lists.alioth.debian.org -- for PHP extensions
pkg-php-ma...@lists.alioth.debian.org -- main PHP packaging and catch-all

Cheers, Ondrej

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

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

-BEGIN PGP SIGNATURE-
Version: GnuPG v2

iQJ8BAEBCgBmBQJXFUtlXxSAAC4AKGlzc3Vlci1mcHJAbm90YXRpb25zLm9w
ZW5wZ3AuZmlmdGhob3JzZW1hbi5uZXQzMEI5MzNEODBGQ0UzRDk4MUEyRDM4RkIw
Qzk5QjcwRUY0RkNCQjA3AAoJEAyZtw70/LsHFw0P/Rrc1yNqoLAcY0JHJ7UEskFe
UvRDC4qlVRsnc2xWAREBBcRYTeUZdxa0U+9sa0wSN9DK/Eqv7WykkFRRddD4uQee
2kLPzpfq/WiOBOnTTY0KrvbrC72/s40Ywjgud2e6R4YdxeRcN9cbf53OJLwt8oA+
/B8QLYAIKuBPiPpp4sJyJmLSeUeUFXVv+LJNEA7PnBG1xFbvG8gDDvKTcy7HTdZm
OIe/9y8ToYNGOPAqUDM3O9Zh+XQnHGLeuzcDtz1ATje0BWATdhIPiI7kb/b2Y7tP

Bug#825800: graphicsmagick: CVE-2016-5118

[GCS]

On Tue, Sep 20, 2016 at 9:56 AM, Stephan Großberndt
 wrote:
> in the meantime its graphicsmagick 1.3.25-2 on Debian Stretch, but Jessie -
> which is the current stable release - still has 12 security issues going
> back to 2015:
 Yes, I consider this my fault. The other part is that there are way
to many fixes to integrate to 1.3.20 and I have other things to do as
well.

> Do you think 1.3.25-2 might be the used for a stable update?
 Upgrade to a newer version in stable is not easy and I can remember
one, maybe two cases when it was allowed.
In this case I'm not sure it should be the path.

Regards,
Laszlo/GCS

Bug#836426: Caused by libgtk-3-0 3.21

[Michael Biebl]

Am 20.09.2016 um 19:38 schrieb Josh Triplett:
> On Thu, Sep 08, 2016 at 01:48:01PM +0200, Michael Biebl wrote:
>> As for gnome-boxes, can you reproduce the problem with 3.21.3 from
>> unstable? I just tested a local installation of debian 8.5 and that
>> worked fine. I don't have  windows ISO to test whether that is
>> reproducible with that setup.
> 
> I can confirm that this bug in libgtk-3-0 still affects gnome-boxes
> 3.22.0-1 from latest sid.  (Tested with libgtk-3-0 3.21.6-1 .)
> Downgrading libgtk-3-0 from 3.21.6-1 to 3.20.9-1 allows gnome-boxes to
> render correctly again.
> 
> You might be able to reproduce this problem if you run the QXL graphics
> driver (xserver-xorg-video-qxl) in the guest, and potentially the guest
> agent as well.
> 
> I can reliably reproduce this with a Windows VM running the QXL driver
> and guest agent.

Please file such issues upstream.

Thanks


-- 
Why is it that all of the instruments seeking intelligent life in the
universe are pointed away from Earth?



signature.asc
Description: OpenPGP digital signature

Processed: Re: Bug#838342: gnome-builder 3.22 fails to install cleanly

[Debian Bug Tracking System]

Processing control commands:

> forwarded -1 https://bugzilla.gnome.org/771719
Bug #838342 [gnome-builder] gnome-builder 3.22 fails to install cleanly
Set Bug forwarded-to-address to 'https://bugzilla.gnome.org/771719'.

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

Bug#838342: gnome-builder 3.22 fails to install cleanly

[Jeremy Bicha]

Control: forwarded -1 https://bugzilla.gnome.org/771719

I reported this to GNOME but it might be a Debian packaging specific issue.

Thanks,
Jeremy

Bug#836426: Caused by libgtk-3-0 3.21

[Josh Triplett]

On Thu, Sep 08, 2016 at 01:48:01PM +0200, Michael Biebl wrote:
> As for gnome-boxes, can you reproduce the problem with 3.21.3 from
> unstable? I just tested a local installation of debian 8.5 and that
> worked fine. I don't have  windows ISO to test whether that is
> reproducible with that setup.

I can confirm that this bug in libgtk-3-0 still affects gnome-boxes
3.22.0-1 from latest sid.  (Tested with libgtk-3-0 3.21.6-1 .)
Downgrading libgtk-3-0 from 3.21.6-1 to 3.20.9-1 allows gnome-boxes to
render correctly again.

You might be able to reproduce this problem if you run the QXL graphics
driver (xserver-xorg-video-qxl) in the guest, and potentially the guest
agent as well.

I can reliably reproduce this with a Windows VM running the QXL driver
and guest agent.

- Josh Triplett

Bug#821883: ImportError: When using gi.repository you must not import static modules like "gobject"

[Martin Dosch]

Package: morituri
Version: 0.2.3-2
Followup-For: Bug #821883

Dear Maintainer,

I'm also affected. Morituri is no more longer usable as it always fail with the
same error message as in the opening report.

Morituri from jessie can't be installed due to missing gstreamer0.10-*
dependencies so I assume something broke with the gstreamer0.10 to gstreamer1.0
transition.

Best regards,
Martin



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

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

Versions of packages morituri depends on:
ii  cdparanoia 3.10.2+debian-11
ii  cdrdao 1:1.2.3-3
ii  gstreamer1.0-plugins-good  1.8.3-1+b1
ii  python 2.7.11-2
ii  python-cddb1.4-5.2
ii  python-gi  3.21.92-1
ii  python-gobject 3.21.92-1
ii  python-gst-1.0 1.8.3-1
ii  python-musicbrainzngs  0.6-1
ii  python-pkg-resources   27.1.2-1

Versions of packages morituri recommends:
ii  gstreamer1.0-libav  1.8.3-1
ii  gstreamer1.0-tools  1.8.3-1
ii  python-xdg  0.25-4

Versions of packages morituri suggests:
ii  gstreamer1.0-plugins-ugly  1.8.3-1
ii  python-gtk22.24.0-5
pn  python-pycdio  

-- debconf-show failed

Bug#838299: [Debichem-devel] Bug#838299: espresso: FTBFS on various arches: test suite hangs

[Graham Inggs]

Hi Emilio

On 20 September 2016 at 16:03, Emilio Pozuelo Monfort  wrote:
> I gave it back on armhf/mips* and it failed again. This time with libopenmpi2:
>
> https://buildd.debian.org/status/package.php?p=espresso

:(  Thanks for trying.

Regards
Graham

Bug#833530: marked as done (gnome-packagekit: Missing Build-Depends on sp)

[Debian Bug Tracking System]

Your message dated Tue, 20 Sep 2016 16:36:13 +
with message-id 
and subject line Bug#833530: fixed in gnome-packagekit 3.20.0-1
has caused the Debian Bug report #833530,
regarding gnome-packagekit: Missing Build-Depends on sp
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.)


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

Dear Maintainer,

gnome-packagekit fails to build from source in unstable/amd64 due to
missing Build-Depends on sp (for nsgmls):

  [..]

  /usr/share/docbook-utils/backends/man: 10: 
/usr/share/docbook-utils/backends/man: nsgmls: not 
found/usr/share/docbook-utils/backends/man: 10: 
/usr/share/docbook-utils/backends/man: 
  nsgmls: not found
  /usr/share/docbook-utils/backends/man: 10: 
/usr/share/docbook-utils/backends/man: nsgmls: not found
  /usr/share/docbook-utils/backends/man: 10: 
/usr/share/docbook-utils/backends/man: nsgmls: not found
   /bin/mkdir -p 
'/home/lamby/temp/cdt.20160805144704.JVeIEKvLyU.gnome-packagekit/gnome-packagekit-3.18.0/debian/tmp/usr/share/man/man1'
   /usr/bin/install -c -m 644 ./gpk-application.1 ./gpk-log.1 ./gpk-prefs.1 
./gpk-update-viewer.1 
'/home/lamby/temp/cdt.20160805144704.JVeIEKvLyU.gnome-packagekit/gnome-packagekit-3.18.0/debian/tmp/usr/share/man/man1'
  /usr/bin/install: cannot stat './gpk-application.1': No such file or directory
  /usr/bin/install: cannot stat './gpk-log.1': No such file or directory
  /usr/bin/install: cannot stat './gpk-prefs.1': No such file or directory
  /usr/bin/install: cannot stat './gpk-update-viewer.1': No such file or 
directory
  Makefile:389: recipe for target 'install-man1' failed
  make[4]: *** [install-man1] Error 1
  make[4]: Leaving directory 
'/home/lamby/temp/cdt.20160805144704.JVeIEKvLyU.gnome-packagekit/gnome-packagekit-3.18.0/man'
  Makefile:481: recipe for target 'install-am' failed
  make[3]: *** [install-am] Error 2
  make[3]: Leaving directory 
'/home/lamby/temp/cdt.20160805144704.JVeIEKvLyU.gnome-packagekit/gnome-packagekit-3.18.0/man'
  Makefile:481: recipe for target 'install-recursive' failed
  make[2]: *** [install-recursive] Error 1
  make[2]: Leaving directory 
'/home/lamby/temp/cdt.20160805144704.JVeIEKvLyU.gnome-packagekit/gnome-packagekit-3.18.0'
  dh_auto_install: make -j9 install 
DESTDIR=/home/lamby/temp/cdt.20160805144704.JVeIEKvLyU.gnome-packagekit/gnome-packagekit-3.18.0/debian/tmp
 AM_UPDATE_INFO_DIR=no returned exit code 2
  debian/rules:17: recipe for target 'override_dh_auto_install' failed
  make[1]: *** [override_dh_auto_install] Error 2
  make[1]: Leaving directory 
'/home/lamby/temp/cdt.20160805144704.JVeIEKvLyU.gnome-packagekit/gnome-packagekit-3.18.0'
  debian/rules:11: recipe for target 'binary' failed
  make: *** [binary] Error 2

  [..]

The full build log is attached.


Regards,

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


gnome-packagekit.3.18.0-1.unstable.amd64.log.txt.gz
Description: Binary data
--- End Message ---
--- Begin Message ---
Source: gnome-packagekit
Source-Version: 3.20.0-1

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

Debian distribution maintenance software
pp.
Matthias Klumpp  (supplier of updated gnome-packagekit package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Format: 1.8
Date: Tue, 20 Sep 2016 17:34:40 +0200
Source: gnome-packagekit
Binary: gnome-packagekit gnome-packagekit-data update-notifier
Architecture: source all amd64
Version: 3.20.0-1
Distribution: unstable
Urgency: medium
Maintainer: Matthias Klumpp 
Changed-By: Matthias Klumpp 
Description:
 gnome-packagekit - Graphical distribution neutral 

Bug#837242: marked as done (jwchat: FTBFS: Can't locate scripts/JWCI18N.pm in @INC)

[Debian Bug Tracking System]

Your message dated Tue, 20 Sep 2016 16:36:53 +
with message-id 
and subject line Bug#837242: fixed in jwchat 1.0+dfsg-1.4
has caused the Debian Bug report #837242,
regarding jwchat: FTBFS: Can't locate scripts/JWCI18N.pm in @INC
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.)


-- 
837242: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=837242
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: jwchat
Version: 1.0+dfsg-1.3
Severity: serious
Tags: stretch sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20160910 qa-ftbfs
Justification: FTBFS on amd64

Hi,

During a rebuild of all packages in sid, your package failed to build on
amd64.

Relevant part (hopefully):
>  debian/rules build
> dh build
>dh_testdir
>dh_update_autotools_config
>dh_auto_configure
>dh_auto_build
>   make -j1
> make[1]: Entering directory '/<>/jwchat-1.0+dfsg'
> 
> Copying Stylesheets ...
> Copying Images ...
> 
> Can't locate scripts/JWCI18N.pm in @INC (you may need to install the 
> scripts::JWCI18N module) (@INC contains: /etc/perl 
> /usr/local/lib/x86_64-linux-gnu/perl/5.22.2 /usr/local/share/perl/5.22.2 
> /usr/lib/x86_64-linux-gnu/perl5/5.22 /usr/share/perl5 
> /usr/lib/x86_64-linux-gnu/perl/5.22 /usr/share/perl/5.22 
> /usr/local/lib/site_perl /usr/lib/x86_64-linux-gnu/perl-base) at 
> ./scripts/templateparser.pl line 35.
> Makefile:8: recipe for target 'install' failed
> make[1]: *** [install] Error 2

The full build log is available from:
   http://aws-logs.debian.net/2016/09/10/jwchat_1.0+dfsg-1.3_unstable.log
(That DNS record was just updated. Use
http://ec2-52-58-237-241.eu-central-1.compute.amazonaws.com if it
doesn't work)

A list of current common problems and possible solutions is available at
http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute!

About the archive rebuild: The rebuild was done on EC2 VM instances from
Amazon Web Services, using a clean, minimal and up-to-date chroot. Every
failed build was retried once to eliminate random failures.
--- End Message ---
--- Begin Message ---
Source: jwchat
Source-Version: 1.0+dfsg-1.4

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

Debian distribution maintenance software
pp.
gregor herrmann  (supplier of updated jwchat package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Sun, 18 Sep 2016 17:11:06 +0200
Source: jwchat
Binary: jwchat
Architecture: source all
Version: 1.0+dfsg-1.4
Distribution: unstable
Urgency: medium
Maintainer: Debian XMPP Maintainers 
Changed-By: gregor herrmann 
Description:
 jwchat - full featured, web-based Jabber chat client
Closes: 837242
Changes:
 jwchat (1.0+dfsg-1.4) unstable; urgency=medium
 .
   * Non-maintainer upload.
   * Fix "FTBFS: Can't locate scripts/JWCI18N.pm in @INC":
 add a patch to prepend ./ to require() calls.
 (Closes: #837242)
   * Additionally add a second patch to handle the changed behaviour of
 Regexp::Common::delimited, otherwise the whole I18N mechanism fails.
Checksums-Sha1:
 ecb7af467a8d9fee5b3951a2672a59e495f11a16 2152 jwchat_1.0+dfsg-1.4.dsc
 75258273ed7184916355fd96fab424d877bc637d 15576 
jwchat_1.0+dfsg-1.4.debian.tar.xz
 b428d6129efa9bdd20cecdad9bc352a64b042b6c 254060 jwchat_1.0+dfsg-1.4_all.deb
Checksums-Sha256:
 ef0145374979885d46ebc2700e7f0b0c70698c041435ffe3d7722cd3b1bb08d6 2152 
jwchat_1.0+dfsg-1.4.dsc
 f2e1ae19714364670ff855498eec5b77e1989715f74a3974890743cb3757e021 15576 
jwchat_1.0+dfsg-1.4.debian.tar.xz
 813f18671e183d23e8597484d25457c76cbc4801a441f0b64786548454e6a450 254060 
jwchat_1.0+dfsg-1.4_all.deb
Files:
 b4b212e49a5b96c06daea6a1919f9aff 2152 web optional jwchat_1.0+dfsg-1.4.dsc
 fb28e3a232dc2c43ee61b0352d57adde 15576 web optional 
jwchat_1.0+dfsg-1.4.debian.tar.xz
 f7dc37000de06ac5457ad41c2283c79a 254060 web optional 
jwchat_1.0+dfsg-1.4_all.deb

-BEGIN PGP SIGNATURE-

Bug#832840: marked as done (license-reconcile: FTBFS: dh_auto_test: perl Build test --verbose 1 returned exit code 255)

[Debian Bug Tracking System]

Your message dated Tue, 20 Sep 2016 16:37:57 +
with message-id 
and subject line Bug#832840: fixed in license-reconcile 0.12
has caused the Debian Bug report #832840,
regarding license-reconcile: FTBFS: dh_auto_test: perl Build test --verbose 1 
returned exit code 255
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.)


-- 
832840: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=832840
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: license-reconcile
Version: 0.11
Severity: serious
Tags: stretch sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20160728 qa-ftbfs
Justification: FTBFS on amd64

Hi,

During a rebuild of all packages in sid, your package failed to build on
amd64.

Relevant part (hopefully):
>  debian/rules build
> dh build --with bash-completion
>dh_testdir
>dh_update_autotools_config
>dh_auto_configure
>   perl Build.PL --installdirs vendor --config "optimize=-g -O2 
> -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time 
> -D_FORTIFY_SOURCE=2" --config "ld=x86_64-linux-gnu-gcc -g -O2 
> -fstack-protector-strong -Wformat -Werror=format-security -Wl,-z,relro"
> WARNING: the following files are missing in your kit:
>   README
> Please inform the author.
> 
> Created MYMETA.yml and MYMETA.json
> Creating new 'Build' script for 'Debian-LicenseReconcile' version '0.11'
>dh_auto_build
>   perl Build
> Building Debian-LicenseReconcile
>dh_auto_test
>   perl Build test --verbose 1
> # Testing Debian::LicenseReconcile 0.11, Perl 5.022002, /usr/bin/perl
> bin/license-reconcile syntax OK
> t/00-load.t ... 
> 1..15
> ok 1 - use Debian::LicenseReconcile;
> ok 2 - use Debian::LicenseReconcile::Errors;
> ok 3 - use Debian::LicenseReconcile::App;
> ok 4 - use Debian::LicenseReconcile::LicenseCheck;
> ok 5 - use Debian::LicenseReconcile::FormatSpec;
> ok 6 - use Debian::LicenseReconcile::CopyrightTarget;
> ok 7 - use Debian::LicenseReconcile::CopyrightDatum;
> ok 8 - use Debian::LicenseReconcile::CopyrightDatum::Holder;
> ok 9 - use Debian::LicenseReconcile::Utils;
> ok 10 - use Debian::LicenseReconcile::Filter;
> ok 11 - use Debian::LicenseReconcile::Filter::Rules;
> ok 12 - use Debian::LicenseReconcile::Filter::Std;
> ok 13 - use Debian::LicenseReconcile::Filter::Shebang;
> ok 14 - use Debian::LicenseReconcile::Filter::ChangeLog;
> ok 15 - Compile test for bin/license-reconcile
> ok
> t/01-errors.t . 
> 1..20
> ok 1 - how many
> ok 2 - digest
> ok 3 - how many
> ok 4 - digest
> ok 5 - how many
> ok 6 - digest
> ok 7 - how many
> ok 8 - digest
> ok 9 - how many
> ok 10 - digest
> ok 11 - how many
> ok 12 - digest
> ok 13 - how many
> ok 14 - digest
> ok 15 - how many
> ok 16 - digest
> ok 17 - how many
> ok 18 - digest
> ok 19 - how many
> ok 20 - digest
> ok
> t/02-format.t . 
> 1..12
> ok 1 - how many
> ok 2 - initial state
> ok 3 - empty copyright
> ok 4 - how many
> ok 5 - initial state
> ok 6 - good format
> ok 7 - good format (HTTPS)
> ok 8 - how many
> ok 9 - initial state
> ok 10 - bad format
> ok 11 - how many
> ok 12 - initial state
> ok
> t/03-parse.t .. 
> 1..6
> ok 1 - how many
> ok 2 - initial state
> ok 3 - An object of class 'Debian::LicenseReconcile::CopyrightTarget' isa 
> 'Debian::LicenseReconcile::CopyrightTarget'
> ok 4 - failed parse
> ok 5 - how many
> ok 6 - bad copyright
> ok
> t/04-parse.t .. 
> 1..5
> ok 1 - how many
> ok 2 - initial state
> ok 3 - An object of class 'Debian::LicenseReconcile::CopyrightTarget' isa 
> 'Debian::LicenseReconcile::CopyrightTarget'
> ok 4 - An object of class 'Debian::LicenseReconcile::CopyrightTarget' isa 
> 'Debian::LicenseReconcile::CopyrightTarget'
> ok 5 - directory mapping
> ok
> t/05-duplicate.t .. 
> 1..7
> ok 1 - how many
> ok 2 - initial state
> ok 3 - An object of class 'Debian::LicenseReconcile::CopyrightTarget' isa 
> 'Debian::LicenseReconcile::CopyrightTarget'
> ok 4 - An object of class 'Debian::LicenseReconcile::CopyrightTarget' isa 
> 'Debian::LicenseReconcile::CopyrightTarget'
> ok 5 - how many
> ok 6 - initial state
> ok 7 - directory mapping
> ok
> t/06-filter.t . 
> 1..2
> ok 1 - An object of class 'Debian::LicenseReconcile::Filter' isa 
> 'Debian::LicenseReconcile::Filter'
> ok 2 - threw Regexp ((?^:not implemented in base class))
> ok
> 
> #   Failed test at t/08-licensecheck.t line 85.
> # Comparing $data as a Bag
> # Missing: 12 references
> # Extra: 12 references
> # Looks like you failed 1 test of 3.
> t/08-licensecheck.t 

Bug#837280: Dependency problem

[GCS]

Hi Michal,

On Tue, Sep 20, 2016 at 2:27 PM, Michal Čihař  wrote:
> this build failure is caused by mismatching versions of libpq-dev
> and postgresql used in the build.
 I know, should have contacted the PostgreSQL team already.

> This is still problem in current sid:
>
> postgresql is 9.5 while libpq-dev is 9.6
>
> Possible ways to address it:
>
> - make postgresql packaging consistent
 This should be done as it may break other packages as well. Maybe
those are not yet uncovered.

> - do not use pg_config to figure out binary path
 If you know any other way, please let me know.

> - Build-Depend on specific version (postgresql-9.6)
 This mean I'll have to do a libdbi-drivers upload for every
PostgreSQL version change - just changing -9.6 to -9.7 and so on. This
package is not specific to any PSQL release and should be totally
unrelated to its current version number.

> As the last choice is least intrusive, I will probably NMU it  unless
> there will be some objections. See attached diff.
 Can be, but the worst solution as you can see above. Let me ask what
the PostgreSQL maintainers say.

Regards,
Laszlo/GCS

Bug#832840: Pending fixes for bugs in the license-reconcile package

[pkg-perl-maintainers]

tag 832840 + pending
thanks

Some bugs in the license-reconcile package are closed in revision
7fec0a47583fe056156c894b9071d6f7e630d806 in branch 'master' by
gustavo panizzo

The full diff can be seen at
https://anonscm.debian.org/cgit/pkg-perl/packages/license-reconcile.git/commit/?id=7fec0a4

Commit message:

* Update test cases to match licensecheck output. Thanks Petter Reinholdtsen
  for the patches, Fix FTBFS (Closes: #832840).
* Fix typo in lib/Debian/LicenseReconcile/CopyrightDatum.pm.

Gbp-Dch: Ignore

Bug#832840: license-reconcile: diff for NMU version 0.12+nmu1

[gregor herrmann]

On Tue, 20 Sep 2016 06:42:51 +0800, gustavo panizzo (gfa) wrote:

> > > I've attached the debdiff, I'll push my changes to the git repo after
> > > the NMU has been uploaded, let me know if you don't agree with any of
> > > this.
> > Thanks for your help.
> > It might be easier to push the changes to the git repo before an
> > upload, with 0.12 instead of 0.12+nmu1, and we can do a regular tram
> > upload. -- Whatever you prefer.
> I have no preference on the matter, and you are the maintainer.
> I've tried to push to the git repo but I have no perms. so I've attached
> the diff between HEAD and your last commit to this email

Thanks.

The patch was against the last tag and not against HEAD, and it was
reversed, but I got it in after all :)
 
I've also added "Team upload" to d/changelog, otherwise lintian
complains about an NMU.

And uploaded. Thanks again.


Cheers,
gregor, closing the RFS bug

-- 
 .''`.  Homepage https://info.comodo.priv.at/ - OpenPGP key 0xBB3A68018649AA06
 : :' : Debian GNU/Linux user, admin, and developer -  https://www.debian.org/
 `. `'  Member of VIBE!AT & SPI, fellow of the Free Software Foundation Europe
   `-   NP: Nick Cave & The Bad Seeds: Spell


signature.asc
Description: Digital Signature

Processed: Pending fixes for bugs in the license-reconcile package

[Debian Bug Tracking System]

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

> tag 832840 + pending
Bug #832840 [src:license-reconcile] license-reconcile: FTBFS: dh_auto_test: 
perl Build test --verbose 1 returned exit code 255
Ignoring request to alter tags of bug #832840 to the same tags previously set
> thanks
Stopping processing here.

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

Processed: severity of 773747 is grave

[Debian Bug Tracking System]

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

> severity 773747 grave
Bug #773747 [pgpdump] pgpdump: CVE-2016-4021: endless loop parsing specially 
crafted input
Ignoring request to change severity of Bug 773747 to the same value.
> thanks
Stopping processing here.

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

Processed: severity of 773747 is grave

[Debian Bug Tracking System]

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

> severity 773747 grave
Bug #773747 [pgpdump] pgpdump: CVE-2016-4021: endless loop parsing specially 
crafted input
Severity set to 'grave' from 'normal'
> thanks
Stopping processing here.

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

Bug#838373: blender: FTBFS on mips/mipsel: linker bug

[Emilio Pozuelo Monfort]

Source: blender
Version: 2.77.a+dfsg0-8
Severity: serious
Control: block -1 with 834147

Hi,

It'd be good to get blender built on mips*, as that's blocking testing
migration, which is blocking some transitions. Could you switch to
ld.bfd until #834147 is fixed?

Thanks,
Emilio

Processed: blender: FTBFS on mips/mipsel: linker bug

[Debian Bug Tracking System]

Processing control commands:

> block -1 with 834147
Bug #838373 [src:blender] blender: FTBFS on mips/mipsel: linker bug
838373 was not blocked by any bugs.
838373 was not blocking any bugs.
Added blocking bug(s) of 838373: 834147

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

Bug#836588: [Cupt-devel] Bug#836588: Bug#836588: cupt: FTBFS on armel/armhf: test failures

[Emilio Pozuelo Monfort]

On 19/09/16 22:00, Eugene V. Lyubimkin wrote:
> On 18.09.2016 22:40, Eugene V. Lyubimkin wrote:
>> Thank you. Turned out it is reproducible in release build (at the least on 
>> armel porterbox), but not in debug build.
>>
>> I'll look into it.
> 
> Ok, something fishy is going on with lambda captures. I believe I found an 
> issue in either std::function or GCC
> optimizer. Looks like a captured value ("this" in this case) is uninitialized 
> or corrupted, but only if previous lambda
> captures a certain amount of variables, no matter was it called or not. Ugh. 
> I managed to reduce
> the code to the following small example:

Cool! Can you file a bug against g++-6 or libstdc++6 (or whatever you think is
appropriate)? Have you found what optimization flag causes this? If it builds
with -O1 or disabling some specific optimization, perhaps you can temporarily
use that to avoid autoremoval from testing.

Thanks,
Emilio

Bug#838299: [Debichem-devel] Bug#838299: espresso: FTBFS on various arches: test suite hangs

[Emilio Pozuelo Monfort]

On 20/09/16 07:59, Graham Inggs wrote:
> Hi Emilio
> 
> On 19 September 2016 at 16:37, Emilio Pozuelo Monfort  
> wrote:
>> Your package failed to build on various architectures:
> ...
>> Full logs at 
>> https://buildd.debian.org/status/package.php?p=espresso=unstable
> 
> If I read that page correctly, the architectures where it failed are
> the ones where it wasn't rebuilt rebuilt against libopenmpi2.

Because it had already failed in the past.

> Should I request givebacks on those architectures?

I gave it back on armhf/mips* and it failed again. This time with libopenmpi2:

https://buildd.debian.org/status/package.php?p=espresso

You can try to reproduce it on the porterboxes.

Cheers,
Emilio

Processed: Thank you, Jonas, I'm also removing debhelper from the bug title

[Debian Bug Tracking System]

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

> retitle 838359 cdbs: some packages FTBFS with 'no python implementation 
> resolved from binary package "stamp-autotools"'
Bug #838359 [cdbs] debhelper or cdbs make some packages to FTBFS
Bug #837006 [cdbs] gnome-python-desktop: FTBFS: 
/usr/share/cdbs/1/class/autotools.mk:44: *** no python implementation resolved 
from binary package "stamp-autotools".  Stop.
Bug #837018 [cdbs] gupnp-igd: FTBFS: /usr/share/cdbs/1/class/autotools.mk:44: 
*** no python implementation resolved from binary package "stamp-autotools".  
Stop.
Bug #837024 [cdbs] gamin: FTBFS: /usr/share/cdbs/1/class/autotools.mk:44: *** 
no python implementation resolved from binary package "stamp-autotools".  Stop.
Bug #837220 [cdbs] python-xklavier: FTBFS: 
/usr/share/cdbs/1/class/autotools.mk:44: *** no python implementation resolved 
from binary package "stamp-autotools".  Stop.
Bug #837239 [cdbs] sugar-base-0.88: FTBFS: 
/usr/share/cdbs/1/class/autotools.mk:44: *** no python implementation resolved 
from binary package "stamp-autotools".  Stop.
Bug #837243 [cdbs] sugar-toolkit: FTBFS: 
/usr/share/cdbs/1/class/autotools.mk:44: *** no python implementation resolved 
from binary package "stamp-autotools".  Stop.
Bug #837244 [cdbs] sugar-base: FTBFS: /usr/share/cdbs/1/class/autotools.mk:44: 
*** no python implementation resolved from binary package "stamp-autotools".  
Stop.
Bug #837248 [cdbs] sugar-datastore-0.88: FTBFS: 
/usr/share/cdbs/1/class/autotools.mk:44: *** no python implementation resolved 
from binary package "stamp-autotools".  Stop.
Bug #837260 [cdbs] sugar-presence-service: FTBFS: 
/usr/share/cdbs/1/class/autotools.mk:44: *** no python implementation resolved 
from binary package "stamp-autotools".  Stop.
Bug #837266 [cdbs] sugar-toolkit-gtk3: FTBFS: 
/usr/share/cdbs/1/class/autotools.mk:44: *** no python implementation resolved 
from binary package "stamp-autotools".  Stop.
Bug #837270 [cdbs] sugar-presence-service-0.88: FTBFS: 
/usr/share/cdbs/1/class/autotools.mk:44: *** no python implementation resolved 
from binary package "stamp-autotools".  Stop.
Bug #837274 [cdbs] sugar-datastore: FTBFS: 
/usr/share/cdbs/1/class/autotools.mk:44: *** no python implementation resolved 
from binary package "stamp-autotools".  Stop.
Bug #837278 [cdbs] sugar-toolkit-0.88: FTBFS: 
/usr/share/cdbs/1/class/autotools.mk:44: *** no python implementation resolved 
from binary package "stamp-autotools".  Stop.
Changed Bug title to 'cdbs: some packages FTBFS with 'no python implementation 
resolved from binary package "stamp-autotools"'' from 'debhelper or cdbs make 
some packages to FTBFS'.
Changed Bug title to 'cdbs: some packages FTBFS with 'no python implementation 
resolved from binary package "stamp-autotools"'' from 'gnome-python-desktop: 
FTBFS: /usr/share/cdbs/1/class/autotools.mk:44: *** no python implementation 
resolved from binary package "stamp-autotools".  Stop.'.
Changed Bug title to 'cdbs: some packages FTBFS with 'no python implementation 
resolved from binary package "stamp-autotools"'' from 'gupnp-igd: FTBFS: 
/usr/share/cdbs/1/class/autotools.mk:44: *** no python implementation resolved 
from binary package "stamp-autotools".  Stop.'.
Changed Bug title to 'cdbs: some packages FTBFS with 'no python implementation 
resolved from binary package "stamp-autotools"'' from 'gamin: FTBFS: 
/usr/share/cdbs/1/class/autotools.mk:44: *** no python implementation resolved 
from binary package "stamp-autotools".  Stop.'.
Changed Bug title to 'cdbs: some packages FTBFS with 'no python implementation 
resolved from binary package "stamp-autotools"'' from 'python-xklavier: FTBFS: 
/usr/share/cdbs/1/class/autotools.mk:44: *** no python implementation resolved 
from binary package "stamp-autotools".  Stop.'.
Changed Bug title to 'cdbs: some packages FTBFS with 'no python implementation 
resolved from binary package "stamp-autotools"'' from 'sugar-base-0.88: FTBFS: 
/usr/share/cdbs/1/class/autotools.mk:44: *** no python implementation resolved 
from binary package "stamp-autotools".  Stop.'.
Changed Bug title to 'cdbs: some packages FTBFS with 'no python implementation 
resolved from binary package "stamp-autotools"'' from 'sugar-toolkit: FTBFS: 
/usr/share/cdbs/1/class/autotools.mk:44: *** no python implementation resolved 
from binary package "stamp-autotools".  Stop.'.
Changed Bug title to 'cdbs: some packages FTBFS with 'no python implementation 
resolved from binary package "stamp-autotools"'' from 'sugar-base: FTBFS: 
/usr/share/cdbs/1/class/autotools.mk:44: *** no python implementation resolved 
from binary package "stamp-autotools".  Stop.'.
Changed Bug title to 'cdbs: some packages FTBFS with 'no python implementation 
resolved from binary package "stamp-autotools"'' from 'sugar-datastore-0.88: 
FTBFS: /usr/share/cdbs/1/class/autotools.mk:44: *** no python implementation 
resolved from binary package "stamp-autotools".  Stop.'.
Changed Bug title to 'cdbs: some packages FTBFS with 'no 

Bug#834249: marked as done (openbabel: FTBFS in testing)

[Debian Bug Tracking System]

Your message dated Tue, 20 Sep 2016 13:19:09 +
with message-id 
and subject line Bug#834249: fixed in openbabel 2.3.2+dfsg-2.4
has caused the Debian Bug report #834249,
regarding openbabel: FTBFS in testing
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.)


-- 
834249: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=834249
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: openbabel
Version: 2.3.2+dfsg-2.3
Severity: serious

Dear maintainer:

This package currently fails to build from source in stretch.

--
/<>/openbabel-2.3.2+dfsg/src/alias.cpp: In static member
function 'static bool OpenBabel::AliasData::LoadFile(O
penBabel::AliasData::SmartsTable&)':
/<>/openbabel-2.3.2+dfsg/src/alias.cpp:273:9: error:
reference to 'shared_ptr' is ambiguous
 shared_ptr psp(new OBSmartsPattern);
  ^~
--

(Failure seems quite different from the one in Bug #812259)

Full logs available here:

https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/openbabel.html

Thanks.
--- End Message ---
--- Begin Message ---
Source: openbabel
Source-Version: 2.3.2+dfsg-2.4

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

Debian distribution maintenance software
pp.
gregor herrmann  (supplier of updated openbabel package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Sun, 18 Sep 2016 14:49:09 +0200
Source: openbabel
Binary: openbabel openbabel-gui libopenbabel-dev libopenbabel4v5 
libopenbabel-doc python-openbabel libchemistry-openbabel-perl openbabel-dbg
Architecture: source amd64 all
Version: 2.3.2+dfsg-2.4
Distribution: unstable
Urgency: medium
Maintainer: Debichem Team 
Changed-By: gregor herrmann 
Description:
 libchemistry-openbabel-perl - Chemical toolbox library (perl bindings)
 libopenbabel-dev - Chemical toolbox library (development files)
 libopenbabel-doc - Chemical toolbox library (documentation)
 libopenbabel4v5 - Chemical toolbox library
 openbabel  - Chemical toolbox utilities (cli)
 openbabel-dbg - Chemical toolbox library (debugging symbols)
 openbabel-gui - Chemical toolbox utilities (graphical user interface)
 python-openbabel - Chemical toolbox library (python bindings)
Closes: 834249
Changes:
 openbabel (2.3.2+dfsg-2.4) unstable; urgency=medium
 .
   * Non-maintainer upload.
   * Fix "FTBFS in testing": build with -std=gnu++98.
 (Closes: #834249)
Checksums-Sha1:
 ce6c42017fb9af8526bb9c12e251705097a646bb 2732 openbabel_2.3.2+dfsg-2.4.dsc
 dea4cf8a4d6a6c79105544f34002eca98089c1e7 15232 
openbabel_2.3.2+dfsg-2.4.debian.tar.xz
 cd492abf977a24a350c6f75b9e3ef8eea1cafca9 813246 
libchemistry-openbabel-perl_2.3.2+dfsg-2.4_amd64.deb
 f44aa7e4021d3920bc400c7b50ecd7aa0f279034 314124 
libopenbabel-dev_2.3.2+dfsg-2.4_amd64.deb
 c22f4e1590e7c6ff7ffb7d4537e0ac8e4b79b0e9 5991938 
libopenbabel-doc_2.3.2+dfsg-2.4_all.deb
 b2e7442e536bb58f5f2dde1046d07d8ce2b60487 2844408 
libopenbabel4v5_2.3.2+dfsg-2.4_amd64.deb
 3987ed462e831f39cee9efbac34dfe6f4b19887e 28436982 
openbabel-dbg_2.3.2+dfsg-2.4_amd64.deb
 6025fe341be9e349684e5d455a5a2d9b18589c27 241540 
openbabel-gui_2.3.2+dfsg-2.4_amd64.deb
 3b175740580aba3baafae96642929398c2a85105 254906 
openbabel_2.3.2+dfsg-2.4_amd64.deb
 7934012b01b1c66cd8fa12cf30befcfc9fb95d3e 805988 
python-openbabel_2.3.2+dfsg-2.4_amd64.deb
Checksums-Sha256:
 8b9581bc67d1a538967a3165a1d0c3c23a480f58f709efa36d3ddc05a56f834b 2732 
openbabel_2.3.2+dfsg-2.4.dsc
 e336304bf81cee04e6fab582fdabf4c2b1943d0e59e20cbcb7a14666e6873161 15232 
openbabel_2.3.2+dfsg-2.4.debian.tar.xz
 2529e0e9cd1e6a2ac86d96d2eaab3dc4077a0c1e78f2725fad4818d90c3c 813246 
libchemistry-openbabel-perl_2.3.2+dfsg-2.4_amd64.deb
 fc01e135e052d467c59f4bbd808acefd237ace9b06763309d326cc3ea5f9c5c9 314124 
libopenbabel-dev_2.3.2+dfsg-2.4_amd64.deb
 

Bug#838114: marked as done (varnish-modules: FTBFS against varnish 5, GCC 6)

[Debian Bug Tracking System]

Your message dated Tue, 20 Sep 2016 12:49:23 +
with message-id 
and subject line Bug#838114: fixed in varnish-modules 0.9.1-4
has caused the Debian Bug report #838114,
regarding varnish-modules: FTBFS against varnish 5, 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.)


-- 
838114: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=838114
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: varnish-modules
Version: 0.9.1-3
Severity: serious
Justification: fails to build from source (but built successfully in the past)

varnish-modules against the recently uploaded varnish 5 and/or GCC 6

vmod_xkey.c:456:10: error: 'enum exp_event_e' declared inside parameter list 
will not be visible outside of this definition or declaration [-Werror]
 enum exp_event_e event, void *priv)
  ^~~
vmod_xkey.c:456:22: error: parameter 3 ('event') has incomplete type
 enum exp_event_e event, void *priv)
  ^
vmod_xkey.c: In function 'xkey_cb':
vmod_xkey.c:465:7: error: 'EXP_INSERT' undeclared (first use in this function)
  case EXP_INSERT:
   ^~
vmod_xkey.c:465:7: note: each undeclared identifier is reported only once for 
each function it appears in
vmod_xkey.c:466:7: error: 'EXP_INJECT' undeclared (first use in this function)
  case EXP_INJECT:
   ^~
vmod_xkey.c:469:7: error: 'EXP_REMOVE' undeclared (first use in this function)
  case EXP_REMOVE:
   ^~
vmod_xkey.c:456:22: error: unused parameter 'event' [-Werror=unused-parameter]
 enum exp_event_e event, void *priv)
  ^
vmod_xkey.c: In function 'purge':
vmod_xkey.c:511:18: error: 'struct objcore' has no member named 'exp'; did you 
mean 'keep'?
   oc->objcore->exp.ttl <= (ctx->now - oc->objcore->exp.t_origin))
  ^~
vmod_xkey.c:511:54: error: 'struct objcore' has no member named 'exp'; did you 
mean 'keep'?
   oc->objcore->exp.ttl <= (ctx->now - oc->objcore->exp.t_origin))
  ^~
vmod_xkey.c:524:19: error: 'struct objcore' has no member named 'exp'; did you 
mean 'keep'?
oc->objcore->exp.grace, oc->objcore->exp.keep);
   ^~
vmod_xkey.c:524:43: error: 'struct objcore' has no member named 'exp'; did you 
mean 'keep'?
oc->objcore->exp.grace, oc->objcore->exp.keep);
   ^~
vmod_xkey.c:526:38: error: 'struct objcore' has no member named 'exp'; did you 
mean 'keep'?
EXP_Rearm(oc->objcore, oc->objcore->exp.t_origin, 0,
  ^~
vmod_xkey.c: In function 'vmod_event':
vmod_xkey.c:559:8: error: implicit declaration of function 
'EXP_Register_Callback' [-Werror=implicit-function-declaration]
EXP_Register_Callback(xkey_cb, NULL);
^
vmod_xkey.c:572:4: error: implicit declaration of function 
'EXP_Deregister_Callback' [-Werror=implicit-function-declaration]
EXP_Deregister_Callback(_cb_handle);
^~~


Andreas


sid.build.gz
Description: application/gzip
--- End Message ---
--- Begin Message ---
Source: varnish-modules
Source-Version: 0.9.1-4

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

Debian distribution maintenance software
pp.
Stig Sandbeck Mathisen  (supplier of updated varnish-modules 
package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Tue, 20 Sep 2016 14:35:35 +0200
Source: varnish-modules
Binary: varnish-modules
Architecture: source
Version: 0.9.1-4
Distribution: unstable
Urgency: medium
Maintainer: Varnish Package Maintainers 

Changed-By: Stig Sandbeck Mathisen 
Description:
 varnish-modules - Varnish module collection
Closes: 838114
Changes:
 varnish-modules (0.9.1-4) unstable; urgency=medium
 .
   * Add patch to support Varnish 5.0.0.
 Thanks to Dridi Boukelmoune (Closes: #838114)
   * Add hardening 

Processed: tagging 837280

[Debian Bug Tracking System]

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

> tags 837280 + patch
Bug #837280 [src:libdbi-drivers] libdbi-drivers: FTBFS: ./debian/test_pgsql.sh: 
40: ./debian/test_pgsql.sh: /usr/lib/postgresql/9.6/bin/initdb: not found
Added tag(s) patch.
> thanks
Stopping processing here.

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

Bug#837280: Dependency problem

[Michal Čihař]

Hi

this build failure is caused by mismatching versions of libpq-dev
and postgresql used in the build. 

This is still problem in current sid:

postgresql is 9.5 while libpq-dev is 9.6

Possible ways to address it:

- make postgresql packaging consistent

- do not use pg_config to figure out binary path

- Build-Depend on specific version (postgresql-9.6)

As the last choice is least intrusive, I will probably NMU it  unless
there will be some objections. See attached diff.

-- 
Michal Čihař | https://cihar.com/ | https://weblate.org/
From 81850b0fc5c6f46206aba2563b1c79f2ee2856e0 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Michal=20=C4=8Ciha=C5=99?= 
Date: Tue, 20 Sep 2016 14:23:52 +0200
Subject: [PATCH 1/1] Adjust build dependency to avoid failure

* Adjust build dependency to avoid failure due to different
  version of libpg-dev and postgresql packages (Closes: #837280).
* Non-maintainer upload.
---
 debian/changelog | 8 
 debian/control   | 4 ++--
 2 files changed, 10 insertions(+), 2 deletions(-)

diff --git a/debian/changelog b/debian/changelog
index c09aece..bcc0121 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,3 +1,11 @@
+libdbi-drivers (0.9.0-4.1) UNRELEASED; urgency=medium
+
+  * Non-maintainer upload.
+  * Adjust build dependency to avoid failure due to different
+version of libpg-dev and postgresql packages (Closes: #837280).
+
+ -- Michal Čihař   Tue, 20 Sep 2016 14:22:30 +0200
+
 libdbi-drivers (0.9.0-4) unstable; urgency=medium
 
   * dbd_sqlite3: resolve a stack buffer overflow (closes: #824067).
diff --git a/debian/control b/debian/control
index 4d90275..4346bde 100644
--- a/debian/control
+++ b/debian/control
@@ -19,8 +19,8 @@ Build-Depends: automake,
mysql-client (>= 5.5),
mysql-server (>= 5.5),
openjade,
-   postgresql,
-   postgresql-client
+   postgresql-9.6,
+   postgresql-client-9.6
 Standards-Version: 3.9.8
 Vcs-Git: git://anonscm.debian.org/collab-maint/libdbi-drivers.git
 Vcs-Browser: http://anonscm.debian.org/gitweb/?p=collab-maint/libdbi-drivers.git
-- 
2.9.3



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

Bug#837284: marked as done (libimage-info-perl: FTBFS: Can't locate inc/Module/Install.pm in @INC)

[Debian Bug Tracking System]

Your message dated Tue, 20 Sep 2016 12:21:48 +
with message-id 
and subject line Bug#837284: fixed in libimage-info-perl 1.28-1.3
has caused the Debian Bug report #837284,
regarding libimage-info-perl: FTBFS: Can't locate inc/Module/Install.pm in @INC
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.)


-- 
837284: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=837284
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: libimage-info-perl
Version: 1.28-1.2
Severity: serious
Tags: stretch sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20160910 qa-ftbfs
Justification: FTBFS on amd64

Hi,

During a rebuild of all packages in sid, your package failed to build on
amd64.

Relevant part (hopefully):
>  debian/rules build
> dh_testdir
> /usr/bin/perl Makefile.PL INSTALLDIRS=vendor
> Can't locate inc/Module/Install.pm in @INC (you may need to install the 
> inc::Module::Install module) (@INC contains: /etc/perl 
> /usr/local/lib/x86_64-linux-gnu/perl/5.22.2 /usr/local/share/perl/5.22.2 
> /usr/lib/x86_64-linux-gnu/perl5/5.22 /usr/share/perl5 
> /usr/lib/x86_64-linux-gnu/perl/5.22 /usr/share/perl/5.22 
> /usr/local/lib/site_perl /usr/lib/x86_64-linux-gnu/perl-base) at Makefile.PL 
> line 8.
> BEGIN failed--compilation aborted at Makefile.PL line 8.
> debian/rules:29: recipe for target 'build-stamp' failed
> make: *** [build-stamp] Error 2

The full build log is available from:
   
http://aws-logs.debian.net/2016/09/10/libimage-info-perl_1.28-1.2_unstable.log
(That DNS record was just updated. Use
http://ec2-52-58-237-241.eu-central-1.compute.amazonaws.com if it
doesn't work)

A list of current common problems and possible solutions is available at
http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute!

About the archive rebuild: The rebuild was done on EC2 VM instances from
Amazon Web Services, using a clean, minimal and up-to-date chroot. Every
failed build was retried once to eliminate random failures.
--- End Message ---
--- Begin Message ---
Source: libimage-info-perl
Source-Version: 1.28-1.3

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

Debian distribution maintenance software
pp.
gregor herrmann  (supplier of updated libimage-info-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: Sun, 18 Sep 2016 13:23:13 +0200
Source: libimage-info-perl
Binary: libimage-info-perl
Architecture: source all
Version: 1.28-1.3
Distribution: unstable
Urgency: medium
Maintainer: Don Armstrong 
Changed-By: gregor herrmann 
Description:
 libimage-info-perl - allows extraction of meta information from image files
Closes: 837284
Changes:
 libimage-info-perl (1.28-1.3) unstable; urgency=medium
 .
   * Non-maintainer upload.
   * Fix "FTBFS: Can't locate inc/Module/Install.pm in @INC":
 call perl with "-I." in debian/rules.
 (Closes: #837284)
Checksums-Sha1:
 6c4e3394027b3277e8ff1f4af314f2de46c6536f 1994 libimage-info-perl_1.28-1.3.dsc
 9249b3647ef35ae18387e8d89f15658fb9e5e76c 4063 
libimage-info-perl_1.28-1.3.diff.gz
 11a47db99cf72b7cf919178a61c9ff86b0b7bfce 52436 
libimage-info-perl_1.28-1.3_all.deb
Checksums-Sha256:
 8620889e5a345fb2654d603630cdc334fed37d92c84459cf3c66ba154a732a89 1994 
libimage-info-perl_1.28-1.3.dsc
 87b155a53c48de6ccbc12728e26b2c21f253e0130cb592065954c29fd0e3e9ec 4063 
libimage-info-perl_1.28-1.3.diff.gz
 2fcd5406eac3ce3f3df7a32bca2e5cc96e396dcaaf18802ddd6ebdfc1aa9ed92 52436 
libimage-info-perl_1.28-1.3_all.deb
Files:
 b64d24cb6e755371f2e4511fe69f16e8 1994 perl optional 
libimage-info-perl_1.28-1.3.dsc
 ae542e90b1efd8fd79366449e3c8e482 4063 perl optional 
libimage-info-perl_1.28-1.3.diff.gz
 0c85761ccdbb54b3d9e9f25266be9328 52436 perl optional 
libimage-info-perl_1.28-1.3_all.deb

-BEGIN PGP SIGNATURE-

iQJ8BAEBCgBmBQJX3nlZXxSAAC4AKGlzc3Vlci1mcHJAbm90YXRpb25zLm9w
ZW5wZ3AuZmlmdGhob3JzZW1hbi5uZXREMUUxMzE2RTkzQTc2MEE4MTA0RDg1RkFC

Processed: unable to reproduce the issue on three AMD64 systems

[Debian Bug Tracking System]

Processing control commands:

> tags -1 unreproducible
Bug #827304 [mousepad] mousepad: Random crashing
Added tag(s) unreproducible.

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

Bug#827304: unable to reproduce the issue on three AMD64 systems

[Daniel Lange]

Control: tags -1 unreproducible

I've tried to reproduce the issue for 48h on three AMD64 systems I've
happened to have around here temporarily with fresh Debian testing
installs. Got to use the opportunity. One of the systems was used for
heavy editing, the two other for occasional editing with lots of idle
times. The theme was set to oblivion on mousepad invocation as
instructed by the bug submitter.
There were no crashes and no uninstructed switch of themes.
The memory consumption was also bound and only changed when editing and
saving.

So this look like an issue that may have been specific to the affected
system. As there have been no confirmations in three months either,
I suggest reducing the bug severity.

Processed: reassign 837243 to cdbs, reassign 837266 to cdbs, reassign 837278 to cdbs, reassign 837260 to cdbs ...

[Debian Bug Tracking System]

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

> reassign 837243 cdbs
Bug #837243 [src:sugar-toolkit] sugar-toolkit: FTBFS: 
/usr/share/cdbs/1/class/autotools.mk:44: *** no python implementation resolved 
from binary package "stamp-autotools".  Stop.
Bug reassigned from package 'src:sugar-toolkit' to 'cdbs'.
No longer marked as found in versions sugar-toolkit/0.98.1-7.
Ignoring request to alter fixed versions of bug #837243 to the same values 
previously set
> reassign 837266 cdbs
Bug #837266 [src:sugar-toolkit-gtk3] sugar-toolkit-gtk3: FTBFS: 
/usr/share/cdbs/1/class/autotools.mk:44: *** no python implementation resolved 
from binary package "stamp-autotools".  Stop.
Bug reassigned from package 'src:sugar-toolkit-gtk3' to 'cdbs'.
No longer marked as found in versions sugar-toolkit-gtk3/0.106.1-1.
Ignoring request to alter fixed versions of bug #837266 to the same values 
previously set
> reassign 837278 cdbs
Bug #837278 [src:sugar-toolkit-0.88] sugar-toolkit-0.88: FTBFS: 
/usr/share/cdbs/1/class/autotools.mk:44: *** no python implementation resolved 
from binary package "stamp-autotools".  Stop.
Bug reassigned from package 'src:sugar-toolkit-0.88' to 'cdbs'.
No longer marked as found in versions sugar-toolkit-0.88/0.88.1-4.
Ignoring request to alter fixed versions of bug #837278 to the same values 
previously set
> reassign 837260 cdbs
Bug #837260 [src:sugar-presence-service] sugar-presence-service: FTBFS: 
/usr/share/cdbs/1/class/autotools.mk:44: *** no python implementation resolved 
from binary package "stamp-autotools".  Stop.
Bug reassigned from package 'src:sugar-presence-service' to 'cdbs'.
No longer marked as found in versions sugar-presence-service/0.90.2-5.
Ignoring request to alter fixed versions of bug #837260 to the same values 
previously set
> reassign 837270 cdbs
Bug #837270 [src:sugar-presence-service-0.88] sugar-presence-service-0.88: 
FTBFS: /usr/share/cdbs/1/class/autotools.mk:44: *** no python implementation 
resolved from binary package "stamp-autotools".  Stop.
Bug reassigned from package 'src:sugar-presence-service-0.88' to 'cdbs'.
No longer marked as found in versions sugar-presence-service-0.88/0.88.0-3.1.
Ignoring request to alter fixed versions of bug #837270 to the same values 
previously set
> reassign 837274 cdbs
Bug #837274 [src:sugar-datastore] sugar-datastore: FTBFS: 
/usr/share/cdbs/1/class/autotools.mk:44: *** no python implementation resolved 
from binary package "stamp-autotools".  Stop.
Bug reassigned from package 'src:sugar-datastore' to 'cdbs'.
No longer marked as found in versions sugar-datastore/0.106.0-1.
Ignoring request to alter fixed versions of bug #837274 to the same values 
previously set
> reassign 837248 cdbs
Bug #837248 [src:sugar-datastore-0.88] sugar-datastore-0.88: FTBFS: 
/usr/share/cdbs/1/class/autotools.mk:44: *** no python implementation resolved 
from binary package "stamp-autotools".  Stop.
Bug reassigned from package 'src:sugar-datastore-0.88' to 'cdbs'.
No longer marked as found in versions sugar-datastore-0.88/0.88.0-4.
Ignoring request to alter fixed versions of bug #837248 to the same values 
previously set
> reassign 837244 cdbs
Bug #837244 [src:sugar-base] sugar-base: FTBFS: 
/usr/share/cdbs/1/class/autotools.mk:44: *** no python implementation resolved 
from binary package "stamp-autotools".  Stop.
Bug reassigned from package 'src:sugar-base' to 'cdbs'.
No longer marked as found in versions sugar-base/0.98.0-5.
Ignoring request to alter fixed versions of bug #837244 to the same values 
previously set
> reassign 837239 cdbs
Bug #837239 [src:sugar-base-0.88] sugar-base-0.88: FTBFS: 
/usr/share/cdbs/1/class/autotools.mk:44: *** no python implementation resolved 
from binary package "stamp-autotools".  Stop.
Bug reassigned from package 'src:sugar-base-0.88' to 'cdbs'.
No longer marked as found in versions sugar-base-0.88/0.88.0-4.
Ignoring request to alter fixed versions of bug #837239 to the same values 
previously set
> reassign 837220 cdbs
Bug #837220 [src:python-xklavier] python-xklavier: FTBFS: 
/usr/share/cdbs/1/class/autotools.mk:44: *** no python implementation resolved 
from binary package "stamp-autotools".  Stop.
Bug reassigned from package 'src:python-xklavier' to 'cdbs'.
No longer marked as found in versions python-xklavier/0.4-4.
Ignoring request to alter fixed versions of bug #837220 to the same values 
previously set
> reassign 837018 cdbs
Bug #837018 [src:gupnp-igd] gupnp-igd: FTBFS: 
/usr/share/cdbs/1/class/autotools.mk:44: *** no python implementation resolved 
from binary package "stamp-autotools".  Stop.
Bug reassigned from package 'src:gupnp-igd' to 'cdbs'.
No longer marked as found in versions gupnp-igd/0.2.4-1.
Ignoring request to alter fixed versions of bug #837018 to the same values 
previously set
> reassign 837024 cdbs
Bug #837024 [src:gamin] gamin: FTBFS: /usr/share/cdbs/1/class/autotools.mk:44: 
*** no python implementation resolved from binary package "stamp-autotools".  
Stop.
Bug reassigned from package 

Processed (with 1 error): forcibly merging 838359 837018 837266 837024 837006

[Debian Bug Tracking System]

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

> forcemerge 838359 837018 837266 837024 837006
Bug #838359 [cdbs] debhelper or cdbs make some packages to FTBFS
Unable to merge bugs because:
package of #837006 is 'src:gnome-python-desktop' not 'cdbs'
package of #837024 is 'src:gamin' not 'cdbs'
package of #837266 is 'src:sugar-toolkit-gtk3' not 'cdbs'
package of #837018 is 'src:gupnp-igd' not 'cdbs'
Failed to forcibly merge 838359: Did not alter merged bugs.

> thanks
Stopping processing here.

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

Processed: affects 838359

[Debian Bug Tracking System]

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

> affects 838359 gupnp-igd gamin gnome-python-desktop sugar-toolkit 
> sugar-toolkit-gtk3 sugar-toolkit-0.88 sugar-presence-service 
> sugar-presence-service-0.88 sugar-datastore sugar-datastore-0.88 sugar-base 
> sugar-base-0.88 python-xklavier
Bug #838359 [cdbs] debhelper or cdbs make some packages to FTBFS
Added indication that 838359 affects gupnp-igd, gamin, gnome-python-desktop, 
sugar-toolkit, sugar-toolkit-gtk3, sugar-toolkit-0.88, sugar-presence-service, 
sugar-presence-service-0.88, sugar-datastore, sugar-datastore-0.88, sugar-base, 
sugar-base-0.88, and python-xklavier
> thanks
Stopping processing here.

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

Bug#838359: [Build-common-hackers] Bug#838359: debhelper or cdbs make some packages to FTBFS

[Jonas Smedegaard]

Quoting Santiago Vila (2016-09-20 12:06:15)
> Some packages having cdbs and debhelper in their build-depends fail to
> build from source with an error like this:
> 
> ** no python implementation resolved from binary package "stamp-autotools"
[...]
> I think this is more likely to be a bug in debhelper or cdbs, hence 
> this report.

Thanks!

Haven't looked closer yet, but smells very much like a bug in cdbs.  So 
much so that I will blindly reassign.

 - Jonas

-- 
 * Jonas Smedegaard - idealist & Internet-arkitekt
 * Tlf.: +45 40843136  Website: http://dr.jones.dk/

 [x] quote me freely  [ ] ask before reusing  [ ] keep private


signature.asc
Description: signature

Processed (with 2 errors): reassign 838359 to cdbs ..., affects 838359

[Debian Bug Tracking System]

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

> reassign 838359 cdbs
Bug #838359 [cdbs, debhelper] debhelper or cdbs make some packages to FTBFS
Bug reassigned from package 'cdbs, debhelper' to 'cdbs'.
Ignoring request to alter found versions of bug #838359 to the same values 
previously set
Ignoring request to alter fixed versions of bug #838359 to the same values 
previously set
> forcemerge 838359 837243 837266 837278 837260 837270 837274 837248 837244 
> 837239 837220
Bug #838359 [cdbs] debhelper or cdbs make some packages to FTBFS
Unable to merge bugs because:
package of #837248 is 'src:sugar-datastore-0.88' not 'cdbs'
package of #837243 is 'src:sugar-toolkit' not 'cdbs'
package of #837278 is 'src:sugar-toolkit-0.88' not 'cdbs'
package of #837270 is 'src:sugar-presence-service-0.88' not 'cdbs'
package of #837260 is 'src:sugar-presence-service' not 'cdbs'
package of #837266 is 'src:sugar-toolkit-gtk3' not 'cdbs'
package of #837220 is 'src:python-xklavier' not 'cdbs'
package of #837239 is 'src:sugar-base-0.88' not 'cdbs'
package of #837244 is 'src:sugar-base' not 'cdbs'
package of #837274 is 'src:sugar-datastore' not 'cdbs'
Failed to forcibly merge 838359: Did not alter merged bugs.

> affects 838359 837018 837266 837024 837006 837243 837266 837278 837260 837270 
> 837274 837248 837244 837239 837220
Failed to mark 838359 as affecting package(s): failed to get lock on 
/org/bugs.debian.org/spool/lock/838359 -- Unable to lock 
/org/bugs.debian.org/spool/lock/838359 Resource temporarily unavailable.
Unable to lock /org/bugs.debian.org/spool/lock/838359 Resource temporarily 
unavailable at /usr/local/lib/site_perl/Debbugs/Common.pm line 629.
Unable to lock /org/bugs.debian.org/spool/lock/838359 Resource temporarily 
unavailable at /usr/local/lib/site_perl/Debbugs/Common.pm line 629.
Unable to lock /org/bugs.debian.org/spool/lock/838359 Resource temporarily 
unavailable at /usr/local/lib/site_perl/Debbugs/Common.pm line 629.
Unable to lock /org/bugs.debian.org/spool/lock/838359 Resource temporarily 
unavailable at /usr/local/lib/site_perl/Debbugs/Common.pm line 629.
Unable to lock /org/bugs.debian.org/spool/lock/838359 Resource temporarily 
unavailable at /usr/local/lib/site_perl/Debbugs/Common.pm line 629.
Unable to lock /org/bugs.debian.org/spool/lock/838359 Resource temporarily 
unavailable at /usr/local/lib/site_perl/Debbugs/Common.pm line 629.
Unable to lock /org/bugs.debian.org/spool/lock/838359 Resource temporarily 
unavailable at /usr/local/lib/site_perl/Debbugs/Common.pm line 629.
Unable to lock /org/bugs.debian.org/spool/lock/838359 Resource temporarily 
unavailable at /usr/local/lib/site_perl/Debbugs/Common.pm line 629.
Unable to lock /org/bugs.debian.org/spool/lock/838359 Resource temporarily 
unavailable at /usr/local/lib/site_perl/Debbugs/Common.pm line 629.
 at /usr/local/lib/site_perl/Debbugs/Common.pm line 587.

> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
837220: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=837220
837239: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=837239
837243: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=837243
837244: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=837244
837248: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=837248
837260: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=837260
837266: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=837266
837270: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=837270
837274: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=837274
837278: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=837278
838359: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=838359
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#836933: fdk-aac: FTBFS with GCC 6: error: narrowing conversion of '2975553344u' from 'unsigned int' to 'LONG {aka long int}' inside { }

[Daniel Knezevic]

Hi,

I had the same issue on mips* and this commit:
https://github.com/mstorsjo/fdk-aac/commit/15b128dd826ba86ee962d86b0b06966a25ed9158
was enough to fix the build.

Thanks,
Daniel

Bug#831077: marked as done (casacore: FTBFS with GCC 6: Math.cc:181:28: error: 'isinf' was not declared in this scope)

[Debian Bug Tracking System]

Your message dated Tue, 20 Sep 2016 11:27:12 +
with message-id 
and subject line Bug#831077: fixed in casacore 2.1.0-2
has caused the Debian Bug report #831077,
regarding casacore: FTBFS with GCC 6: Math.cc:181:28: error: 'isinf' was not 
declared in this scope
to be marked as done.

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

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


-- 
831077: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=831077
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: casacore
Version: 2.1.0-1
Severity: serious
Tags: stretch sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20160713 qa-ftbfs
Justification: FTBFS with GCC 6 on amd64

Hi,

During a rebuild of all packages in sid using the gcc-defaults package
available in experimental to make GCC default to version 6, your package failed
to build on amd64. For more information about GCC 6 and Stretch, see:
- https://wiki.debian.org/GCC6
- https://lists.debian.org/debian-devel-announce/2016/06/msg7.html

Relevant part (hopefully):
> make[3]: Entering directory '/«PKGBUILDDIR»/obj-x86_64-linux-gnu'
> [  0%] Building CXX object casa/CMakeFiles/casa_casa.dir/Arrays/ArrayBase.cc.o
> cd /«PKGBUILDDIR»/obj-x86_64-linux-gnu/casa && /usr/bin/c++   
> -DCFITSIO_VERSION_MAJOR=3 -DCFITSIO_VERSION_MINOR=380 -DHAVE_FFTW3 
> -DHAVE_FFTW3_THREADS -DHAVE_READLINE -DUSE_THREADS -DWCSLIB_VERSION_MAJOR=5 
> -DWCSLIB_VERSION_MINOR=15 -Dcasa_casa_EXPORTS -I/«PKGBUILDDIR» 
> -I/«PKGBUILDDIR»/obj-x86_64-linux-gnu  -fcx-fortran-rules -g -O2 
> -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time 
> -D_FORTIFY_SOURCE=2  -pthread -fPIC   -o 
> CMakeFiles/casa_casa.dir/Arrays/ArrayBase.cc.o -c 
> /«PKGBUILDDIR»/casa/Arrays/ArrayBase.cc
> [  0%] Building CXX object 
> casa/CMakeFiles/casa_casa.dir/Arrays/ArrayError.cc.o
> cd /«PKGBUILDDIR»/obj-x86_64-linux-gnu/casa && /usr/bin/c++   
> -DCFITSIO_VERSION_MAJOR=3 -DCFITSIO_VERSION_MINOR=380 -DHAVE_FFTW3 
> -DHAVE_FFTW3_THREADS -DHAVE_READLINE -DUSE_THREADS -DWCSLIB_VERSION_MAJOR=5 
> -DWCSLIB_VERSION_MINOR=15 -Dcasa_casa_EXPORTS -I/«PKGBUILDDIR» 
> -I/«PKGBUILDDIR»/obj-x86_64-linux-gnu  -fcx-fortran-rules -g -O2 
> -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time 
> -D_FORTIFY_SOURCE=2  -pthread -fPIC   -o 
> CMakeFiles/casa_casa.dir/Arrays/ArrayError.cc.o -c 
> /«PKGBUILDDIR»/casa/Arrays/ArrayError.cc
> [  0%] Building CXX object 
> casa/CMakeFiles/casa_casa.dir/Arrays/ArrayOpsDiffShapes.cc.o
> cd /«PKGBUILDDIR»/obj-x86_64-linux-gnu/casa && /usr/bin/c++   
> -DCFITSIO_VERSION_MAJOR=3 -DCFITSIO_VERSION_MINOR=380 -DHAVE_FFTW3 
> -DHAVE_FFTW3_THREADS -DHAVE_READLINE -DUSE_THREADS -DWCSLIB_VERSION_MAJOR=5 
> -DWCSLIB_VERSION_MINOR=15 -Dcasa_casa_EXPORTS -I/«PKGBUILDDIR» 
> -I/«PKGBUILDDIR»/obj-x86_64-linux-gnu  -fcx-fortran-rules -g -O2 
> -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time 
> -D_FORTIFY_SOURCE=2  -pthread -fPIC   -o 
> CMakeFiles/casa_casa.dir/Arrays/ArrayOpsDiffShapes.cc.o -c 
> /«PKGBUILDDIR»/casa/Arrays/ArrayOpsDiffShapes.cc
> [  0%] Building CXX object 
> casa/CMakeFiles/casa_casa.dir/Arrays/ArrayPosIter.cc.o
> cd /«PKGBUILDDIR»/obj-x86_64-linux-gnu/casa && /usr/bin/c++   
> -DCFITSIO_VERSION_MAJOR=3 -DCFITSIO_VERSION_MINOR=380 -DHAVE_FFTW3 
> -DHAVE_FFTW3_THREADS -DHAVE_READLINE -DUSE_THREADS -DWCSLIB_VERSION_MAJOR=5 
> -DWCSLIB_VERSION_MINOR=15 -Dcasa_casa_EXPORTS -I/«PKGBUILDDIR» 
> -I/«PKGBUILDDIR»/obj-x86_64-linux-gnu  -fcx-fortran-rules -g -O2 
> -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time 
> -D_FORTIFY_SOURCE=2  -pthread -fPIC   -o 
> CMakeFiles/casa_casa.dir/Arrays/ArrayPosIter.cc.o -c 
> /«PKGBUILDDIR»/casa/Arrays/ArrayPosIter.cc
> [  0%] Building CXX object 
> casa/CMakeFiles/casa_casa.dir/Arrays/ArrayUtil2.cc.o
> cd /«PKGBUILDDIR»/obj-x86_64-linux-gnu/casa && /usr/bin/c++   
> -DCFITSIO_VERSION_MAJOR=3 -DCFITSIO_VERSION_MINOR=380 -DHAVE_FFTW3 
> -DHAVE_FFTW3_THREADS -DHAVE_READLINE -DUSE_THREADS -DWCSLIB_VERSION_MAJOR=5 
> -DWCSLIB_VERSION_MINOR=15 -Dcasa_casa_EXPORTS -I/«PKGBUILDDIR» 
> -I/«PKGBUILDDIR»/obj-x86_64-linux-gnu  -fcx-fortran-rules -g -O2 
> -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time 
> -D_FORTIFY_SOURCE=2  -pthread -fPIC   -o 
> CMakeFiles/casa_casa.dir/Arrays/ArrayUtil2.cc.o -c 
> /«PKGBUILDDIR»/casa/Arrays/ArrayUtil2.cc
> [  0%] Building CXX object casa/CMakeFiles/casa_casa.dir/Arrays/Array2.cc.o
> cd /«PKGBUILDDIR»/obj-x86_64-linux-gnu/casa && /usr/bin/c++   
> -DCFITSIO_VERSION_MAJOR=3 -DCFITSIO_VERSION_MINOR=380 -DHAVE_FFTW3 
> -DHAVE_FFTW3_THREADS 

Processed: The actual bug is in liblognorm-dev

[Debian Bug Tracking System]

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

> reassign 835763 liblognorm-dev
Bug #835763 [libfastjson-dev] sagan: FTBFS: configure: error: Package 
requirements (lognorm >= 1.0.0) were not met
Bug reassigned from package 'libfastjson-dev' to 'liblognorm-dev'.
Ignoring request to alter found versions of bug #835763 to the same values 
previously set
Ignoring request to alter fixed versions of bug #835763 to the same values 
previously set
> forcemerge 834081 835763
Bug #834081 [liblognorm-dev] Missing dependency on libfastjson-dev
Bug #835763 [liblognorm-dev] sagan: FTBFS: configure: error: Package 
requirements (lognorm >= 1.0.0) were not met
Marked as found in versions liblognorm/2.0.1-1.
Added tag(s) patch.
Bug #834081 [liblognorm-dev] Missing dependency on libfastjson-dev
Added tag(s) stretch and sid.
Merged 834081 835763
> affects 834081 src:sagan
Bug #834081 [liblognorm-dev] Missing dependency on libfastjson-dev
Bug #835763 [liblognorm-dev] sagan: FTBFS: configure: error: Package 
requirements (lognorm >= 1.0.0) were not met
Added indication that 834081 affects src:sagan
Added indication that 835763 affects src:sagan
> thanks
Stopping processing here.

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

Processed: reassign 835763 to src:sagan

[Debian Bug Tracking System]

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

> reassign 835763 src:sagan
Bug #835763 [liblognorm-dev] sagan: FTBFS: configure: error: Package 
requirements (lognorm >= 1.0.0) were not met
Bug #834081 [liblognorm-dev] Missing dependency on libfastjson-dev
Bug reassigned from package 'liblognorm-dev' to 'src:sagan'.
Bug reassigned from package 'liblognorm-dev' to 'src:sagan'.
No longer marked as found in versions liblognorm/2.0.1-1.
No longer marked as found in versions liblognorm/2.0.1-1.
Ignoring request to alter fixed versions of bug #835763 to the same values 
previously set
Ignoring request to alter fixed versions of bug #834081 to the same values 
previously set
> thanks
Stopping processing here.

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

Processed (with 2 errors): The actual bug is in liblognorm-dev

[Debian Bug Tracking System]

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

> reassign 835763 libfastjson-dev
Bug #835763 [src:sagan] sagan: FTBFS: configure: error: Package requirements 
(lognorm >= 1.0.0) were not met
Bug reassigned from package 'src:sagan' to 'libfastjson-dev'.
No longer marked as found in versions sagan/1.0.1-0.3.
Ignoring request to alter fixed versions of bug #835763 to the same values 
previously set
> forcemerge 834081 835763
Bug #834081 [liblognorm-dev] Missing dependency on libfastjson-dev
Unable to merge bugs because:
package of #835763 is 'libfastjson-dev' not 'liblognorm-dev'
Failed to forcibly merge 834081: Did not alter merged bugs.

> affects 834081 src:sagan
Failed to mark 834081 as affecting package(s): failed to get lock on 
/org/bugs.debian.org/spool/lock/834081 -- Unable to lock 
/org/bugs.debian.org/spool/lock/834081 Resource temporarily unavailable.
Unable to lock /org/bugs.debian.org/spool/lock/834081 Resource temporarily 
unavailable at /usr/local/lib/site_perl/Debbugs/Common.pm line 629.
Unable to lock /org/bugs.debian.org/spool/lock/834081 Resource temporarily 
unavailable at /usr/local/lib/site_perl/Debbugs/Common.pm line 629.
Unable to lock /org/bugs.debian.org/spool/lock/834081 Resource temporarily 
unavailable at /usr/local/lib/site_perl/Debbugs/Common.pm line 629.
Unable to lock /org/bugs.debian.org/spool/lock/834081 Resource temporarily 
unavailable at /usr/local/lib/site_perl/Debbugs/Common.pm line 629.
Unable to lock /org/bugs.debian.org/spool/lock/834081 Resource temporarily 
unavailable at /usr/local/lib/site_perl/Debbugs/Common.pm line 629.
Unable to lock /org/bugs.debian.org/spool/lock/834081 Resource temporarily 
unavailable at /usr/local/lib/site_perl/Debbugs/Common.pm line 629.
Unable to lock /org/bugs.debian.org/spool/lock/834081 Resource temporarily 
unavailable at /usr/local/lib/site_perl/Debbugs/Common.pm line 629.
Unable to lock /org/bugs.debian.org/spool/lock/834081 Resource temporarily 
unavailable at /usr/local/lib/site_perl/Debbugs/Common.pm line 629.
Unable to lock /org/bugs.debian.org/spool/lock/834081 Resource temporarily 
unavailable at /usr/local/lib/site_perl/Debbugs/Common.pm line 629.
 at /usr/local/lib/site_perl/Debbugs/Common.pm line 587.

> thanks
Stopping processing here.

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

Processed: bug 838114 is forwarded to https://github.com/varnish/varnish-modules/issues/44

[Debian Bug Tracking System]

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

> forwarded 838114 https://github.com/varnish/varnish-modules/issues/44
Bug #838114 [src:varnish-modules] varnish-modules: FTBFS against varnish 5, GCC 
6
Set Bug forwarded-to-address to 
'https://github.com/varnish/varnish-modules/issues/44'.
> thanks
Stopping processing here.

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

Bug#835910: warzone2100: FTBFS when newer automake is installed

[Adrian Bunk]

On Wed, Sep 07, 2016 at 01:36:25AM +0200, Santiago Vila wrote:
> reassign 835910 src:warzone2100
> found 835910 3.1.1-3
> forcemerge 835910 824011
> thanks
> 
> On Mon, 29 Aug 2016, Russell Coker wrote:
> 
> > Package: warzone2100
> > Version: 3.1.1-3
> > Severity: serious
> > Tags: upstream patch
> > Justification: fails to build from source (but built successfully in the 
> > past)
> > 
> > The warzone2100 build system insists on automake and aclocal version 1.11.  
> > If
> > you have 1.15 installed it won't build.
> 
> I already reported this as Bug#824011 and suggested using a Build-Conflicts.

Your patch is sufficient, but the patch from Russell is better since it 
doesn't force removal of automake on the build system.

That's not an issue for the kind of builds autobuilders or you are 
doing, but it is annoying when you are forced to temporarily remove 
automake on a normal system.

> You probably didn't see the bug because the maintainer downgraded to "normal".
> 
> Maybe I'm not the only one to think that FTBFS bugs are RC, after all.

I am really surprised anyone disputed that this is RC.

Even more when considering that you already suggested a trivial fix
in the initial bug report.

> Thanks.

cu
Adrian

-- 

   "Is there not promise of rain?" Ling Tan asked suddenly out
of the darkness. There had been need of rain for many days.
   "Only a promise," Lao Er said.
   Pearl S. Buck - Dragon Seed

Bug#838359: debhelper or cdbs make some packages to FTBFS

[Santiago Vila]

More affected packages: gamin and gnome-python-desktop

https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=837024
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=837006

Processed: ltrace: diff for NMU version 0.7.3-5.2

[Debian Bug Tracking System]

Processing control commands:

> tags 837011 + patch
Bug #837011 [src:ltrace] ltrace: FTBFS: proc.c:245:3: error: 'readdir_r' is 
deprecated [-Werror=deprecated-declarations]
Added tag(s) patch.
> tags 837011 + pending
Bug #837011 [src:ltrace] ltrace: FTBFS: proc.c:245:3: error: 'readdir_r' is 
deprecated [-Werror=deprecated-declarations]
Added tag(s) pending.

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

Bug#837011: ltrace: diff for NMU version 0.7.3-5.2

[Paul Wise]

Control: tags 837011 + patch
Control: tags 837011 + pending

I've prepared an NMU for ltrace (versioned as 0.7.3-5.2) and
uploaded it to DELAYED/2. Please feel free to tell me if I
should delay it longer.

-- 
bye,
pabs

https://wiki.debian.org/PaulWise
diff -Nru ltrace-0.7.3/debian/changelog ltrace-0.7.3/debian/changelog
--- ltrace-0.7.3/debian/changelog	2015-11-02 18:07:02.0 +0800
+++ ltrace-0.7.3/debian/changelog	2016-09-20 18:45:00.0 +0800
@@ -1,3 +1,10 @@
+ltrace (0.7.3-5.2) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * Disable use of -Werror to prevent FTBFS (Closes: #837011)
+
+ -- Paul Wise   Tue, 20 Sep 2016 18:45:00 +0800
+
 ltrace (0.7.3-5.1) unstable; urgency=medium
 
   * Non-maintainer upload.
diff -Nru ltrace-0.7.3/debian/rules ltrace-0.7.3/debian/rules
--- ltrace-0.7.3/debian/rules	2014-01-03 19:46:17.0 +0800
+++ ltrace-0.7.3/debian/rules	2016-09-20 18:34:04.0 +0800
@@ -1,6 +1,6 @@
 #!/usr/bin/make -f
 
-cdbs_configure_flags := --with-libunwind=no
+cdbs_configure_flags := --with-libunwind=no --disable-werror
 
 include /usr/share/cdbs/1/rules/debhelper.mk
 include /usr/share/cdbs/1/class/autotools.mk


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

Processed: severity of 838302 is normal

[Debian Bug Tracking System]

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

> # with serious severity, migration to testing wont occure when NEW queue will 
> be passed
> severity 838302 normal
Bug #838302 [opencl-headers] opencl-headers depends on unavailable 
opencl-clhpp-headers
Severity set to 'normal' from 'serious'
> thanks
Stopping processing here.

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

Processed: ivtools FTBFS forwarded upstream

[Debian Bug Tracking System]

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

> forwarded 835747 https://github.com/vectaport/ivtools-1.2/issues/5
Bug #835747 [src:ivtools] ivtools: FTBFS: src/Attribute/attrlist.cc:514:35: 
error: call of overloaded 'abs(unsigned int)' is ambiguous
Set Bug forwarded-to-address to 
'https://github.com/vectaport/ivtools-1.2/issues/5'.
> thanks
Stopping processing here.

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

Bug#838359: debhelper or cdbs make some packages to FTBFS

[Santiago Vila]

Package: cdbs, debhelper
Severity: serious

Dear maintainer:

Some packages having cdbs and debhelper in their build-depends fail to
build from source with an error like this:

** no python implementation resolved from binary package "stamp-autotools"

Examples: gupnp-igd and sugar-toolkit-gtk3:

https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=837018
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=837266

I think this is more likely to be a bug in debhelper or cdbs, hence this report.

If that's really the case, please reassign those bugs and this one to
whatever package is to blame. Then use affects, so that we can still
see them in their respective web pages to avoid duplicate bugs.
Another affected package would be gdb.

If that was not really the case after all, I'm sorry and feel free to
close this bug. However, since those two packages (and gdb) fail in
exactly the same way I assume some hint about why this happens would
be appreciated by the maintainers.

Thanks.

Bug#838358: icinga2: FTBFS on armhf: test failures

[Emilio Pozuelo Monfort]

Source: icinga2
Version: 2.5.4-2
Severity: serious

Your package still fails to build on armhf:

97% tests passed, 2 tests failed out of 74

Total Test time (real) =   6.87 sec

The following tests FAILED:
 46 - base-base_timer/invoke (OTHER_FAULT)
 47 - base-base_timer/scope (OTHER_FAULT)
Errors while running CTest
Makefile:130: recipe for target 'test' failed
make[1]: *** [test] Error 8
make[1]: Leaving directory '/«PKGBUILDDIR»/obj-arm-linux-gnueabihf'
dh_auto_test: make -j1 test ARGS+=-j1 returned exit code 2
debian/rules:23: recipe for target 'build-arch' failed
make: *** [build-arch] Error 2

Full logs at 
https://buildd.debian.org/status/package.php?p=icinga2=unstable

Emilio

Bug#830436: marked as done (gnat-4.9: FTBFS: b_gnatb.adb:86: undefined reference to `__gnat_runtime_finalize')

[Debian Bug Tracking System]

Your message dated Tue, 20 Sep 2016 09:54:11 +
with message-id 
and subject line Bug#838315: Removed package(s) from unstable
has caused the Debian Bug report #830436,
regarding gnat-4.9: FTBFS: b_gnatb.adb:86: undefined reference to 
`__gnat_runtime_finalize'
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.)


-- 
830436: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=830436
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: gnat-4.9
Version: 4.9.3-3
Severity: serious
Tags: stretch sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20160707 qa-ftbfs
Justification: FTBFS on amd64

Hi,

During a rebuild of all packages in sid, your package failed to build on
amd64.

Relevant part (hopefully):
> x86_64-linux-gnu-g++ -g -DIN_GCC -fno-exceptions -fno-rtti 
> -fasynchronous-unwind-tables -W -Wall -Wno-narrowing -Wwrite-strings 
> -Wcast-qual -Wno-format -Wmissing-format-attribute -pedantic -Wno-long-long 
> -Wno-variadic-macros -Wno-overlength-strings -DHAVE_CONFIG_H 
> -static-libstdc++ -static-libgcc  -o gnatbind ada/b_gnatb.o ada/a-clrefi.o 
> ada/a-comlin.o ada/a-elchha.o ada/a-except.o ada/ada.o ada/adaint.o 
> ada/ali-util.o ada/ali.o ada/alloc.o ada/argv.o ada/aspects.o ada/atree.o 
> ada/bcheck.o ada/binde.o ada/binderr.o ada/bindgen.o ada/bindusg.o 
> ada/butil.o ada/casing.o ada/cio.o ada/csets.o ada/cstreams.o ada/debug.o 
> ada/einfo.o ada/elists.o ada/env.o ada/err_vars.o ada/errout.o ada/erroutc.o 
> ada/exit.o ada/final.o ada/fmap.o ada/fname-uf.o ada/fname.o ada/g-byorma.o 
> ada/g-hesora.o ada/g-htable.o ada/gnat.o ada/gnatbind.o ada/gnatvsn.o 
> ada/hostparm.o ada/init.o ada/initialize.o ada/interfac.o ada/krunch.o 
> ada/lib.o ada/link.o ada/namet.o ada/nlists.o ada/opt.o ada/osint-b.o 
> ada/osint.o ada/output.o ada/raise.o ada/restrict.o ada/rident.o 
> ada/s-addope.o ada/s-assert.o ada/s-carun8.o ada/s-casuti.o ada/s-conca2.o 
> ada/s-conca3.o ada/s-conca4.o ada/s-conca5.o ada/s-conca6.o ada/s-conca7.o 
> ada/s-conca8.o ada/s-conca9.o ada/s-crc32.o ada/s-crtl.o ada/s-excdeb.o 
> ada/s-except.o ada/s-exctab.o ada/s-htable.o ada/s-imenne.o ada/s-imgenu.o 
> ada/s-mastop.o ada/s-memory.o ada/s-os_lib.o ada/s-parame.o ada/s-restri.o 
> ada/s-secsta.o ada/s-soflin.o ada/s-sopco3.o ada/s-sopco4.o ada/s-sopco5.o 
> ada/s-stache.o ada/s-stalib.o ada/s-stoele.o ada/s-strhas.o ada/s-string.o 
> ada/s-strops.o ada/s-traent.o ada/s-unstyp.o ada/s-utf_32.o ada/s-wchcnv.o 
> ada/s-wchcon.o ada/s-wchjis.o ada/scans.o ada/scil_ll.o ada/scng.o 
> ada/sdefault.o ada/seh_init.o ada/sem_aux.o ada/sinfo.o ada/sinput-c.o 
> ada/sinput.o ada/snames.o ada/stand.o ada/stringt.o ada/style.o ada/styleg.o 
> ada/stylesw.o ada/switch-b.o ada/switch.o ada/system.o ada/table.o 
> ada/targext.o ada/targparm.o ada/tree_io.o ada/types.o ada/uintp.o 
> ada/uname.o ada/urealp.o ada/widechar.o ggc-none.o libcommon-target.a 
> libcommon.a ../libcpp/libcpp.a   ../libbacktrace/.libs/libbacktrace.a 
> ../libiberty/libiberty.a ../libdecnumber/libdecnumber.a   -g
> /«PKGBUILDDIR»/build/./gcc/xgcc -B/«PKGBUILDDIR»/build/./gcc/ -dumpspecs > 
> tmp-specs
> mv tmp-specs specs
> : > tmp-libgcc.mvars
> echo GCC_CFLAGS = '-g -O2 -DIN_GCC-W -Wall -Wno-narrowing -Wwrite-strings 
> -Wcast-qual -Wno-format -Wstrict-prototypes -Wmissing-prototypes 
> -Wold-style-definition  -isystem ./include ' >> tmp-libgcc.mvars
> echo INHIBIT_LIBC_CFLAGS = '' >> tmp-libgcc.mvars
> echo TARGET_SYSTEM_ROOT = '/' >> tmp-libgcc.mvars
> mv tmp-libgcc.mvars libgcc.mvars
> if /«PKGBUILDDIR»/build/./gcc/xgcc -B/«PKGBUILDDIR»/build/./gcc/ 
> -print-sysroot-headers-suffix > /dev/null 2>&1; then \
>   set -e; for ml in `/«PKGBUILDDIR»/build/./gcc/xgcc 
> -B/«PKGBUILDDIR»/build/./gcc/ -print-multi-lib`; do \
> multi_dir=`echo ${ml} | sed -e 's/;.*$//'`; \
> flags=`echo ${ml} | sed -e 's/^[^;]*;//' -e 's/@/ -/g'`; \
> sfx=`/«PKGBUILDDIR»/build/./gcc/xgcc -B/«PKGBUILDDIR»/build/./gcc/ 
> ${flags} -print-sysroot-headers-suffix`; \
> if [ "${multi_dir}" = "." ]; \
>   then multi_dir=""; \
> else \
>   multi_dir=/${multi_dir}; \
> fi; \
> echo "${sfx};${multi_dir}"; \
>   done; \
> else \
>   echo ";"; \
> fi > tmp-fixinc_list
> /bin/bash ../../src/gcc/../move-if-change tmp-fixinc_list fixinc_list
> echo timestamp > s-fixinc_list
> ada/b_gnatb.o: In function `adafinal':
> /«PKGBUILDDIR»/build/gcc/ada/b_gnatb.adb:86: undefined reference to 
> `__gnat_runtime_finalize'
> ada/b_gnatb.o: In function `adainit':
> /«PKGBUILDDIR»/build/gcc/ada/b_gnatb.adb:153: undefined 

Bug#837496: marked as done (mopidy-podcast-gpodder: needs to be updated for mopidy-podcast 2.x)

[Debian Bug Tracking System]

Your message dated Tue, 20 Sep 2016 09:53:54 +
with message-id 
and subject line Bug#838261: Removed package(s) from unstable
has caused the Debian Bug report #837496,
regarding mopidy-podcast-gpodder: needs to be updated for mopidy-podcast 2.x
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.)


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

Hi,

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

mopidy-podcast 2.x has added a Breaks: mopidy-podcast-gpodder (<< 2.0)


Cheers,

Andreas
--- End Message ---
--- Begin Message ---
Version: 1.0.0-1+rm

Dear submitter,

as the package mopidy-podcast-gpodder 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/838261

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.
Chris Lamb (the ftpmaster behind the curtain)--- End Message ---

Bug#813117: marked as done (jai-imageio-core: unsatisfiable B-D: libjai-core-java)

[Debian Bug Tracking System]

Your message dated Tue, 20 Sep 2016 09:53:40 +
with message-id 
and subject line Bug#838063: Removed package(s) from unstable
has caused the Debian Bug report #813117,
regarding jai-imageio-core: unsatisfiable B-D: libjai-core-java
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.)


-- 
813117: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=813117
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: jai-imageio-core
Version: 1.2-3
Severity: serious
Tags: sid
Justification: fails to build from source

Hi,

your package cannot be built in sid any longer:

Depends: libjai-core-java which is a virtual package and is not provided
by any available package.


Andreas
--- End Message ---
--- Begin Message ---
Version: 1.2-3+rm

Dear submitter,

as the package jai-imageio-core 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/838063

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.
Chris Lamb (the ftpmaster behind the curtain)--- End Message ---

Bug#801248: marked as done (blends-image-hamradio: uninstallable in sid: unsatisfiable Depends: live-build (>= 5.0))

[Debian Bug Tracking System]

Your message dated Tue, 20 Sep 2016 09:53:58 +
with message-id 
and subject line Bug#838277: Removed package(s) from unstable
has caused the Debian Bug report #801248,
regarding blends-image-hamradio: uninstallable in sid: unsatisfiable Depends: 
live-build (>= 5.0)
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.)


-- 
801248: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=801248
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: blends-image-hamradio
Version: 0.1
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

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

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


The version of live-build available in sid is 5.0~a11-1


Cheers,

Andreas
--- End Message ---
--- Begin Message ---
Version: 0.1+rm

Dear submitter,

as the package blends-images 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/838277

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.
Chris Lamb (the ftpmaster behind the curtain)--- End Message ---

Processed: Re: [pkg-mono-group] Bug#838331: mono-reference-assemblies-3.5: does not contain the reference assemblies

[Debian Bug Tracking System]

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

> retitle 838331 missing dependency on mono-reference-assemblies-2.0
Bug #838331 [mono-reference-assemblies-3.5] mono-reference-assemblies-3.5: does 
not contain the reference assemblies
Changed Bug title to 'missing dependency on mono-reference-assemblies-2.0' from 
'mono-reference-assemblies-3.5: does not contain the reference assemblies'.
> severity 838331 normal
Bug #838331 [mono-reference-assemblies-3.5] missing dependency on 
mono-reference-assemblies-2.0
Severity set to 'normal' from 'grave'
> stop
Stopping processing here.

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

Processed: Re: gnome-twitch-player-backend-mpv-opengl: immediate segmentation fault

[Debian Bug Tracking System]

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

> tags 837940 + moreinfo unreproducible
Bug #837940 [gnome-twitch-player-backend-mpv-opengl] 
gnome-twitch-player-backend-mpv-opengl: immediate segmentation fault
Added tag(s) moreinfo and unreproducible.
> thanks
Stopping processing here.

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

Bug#835675: Bug#835702: The two seahorse-nautilus FTBFS bugs are the same bug

[Chris Lamb]

> The two seahorse-nautilus FTBFS bugs are the same bug.

Apologies, didn't see it otherwise would not have filed it again :)

 
Regards,

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

Processed: bug 838336 is forwarded to https://bugzilla.gnome.org/show_bug.cgi?id=771696

[Debian Bug Tracking System]

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

> forwarded 838336 https://bugzilla.gnome.org/show_bug.cgi?id=771696
Bug #838336 [gnome-control-center] gnome-control-center: Keybinding panel fail 
to open
Set Bug forwarded-to-address to 
'https://bugzilla.gnome.org/show_bug.cgi?id=771696'.
> thanks
Stopping processing here.

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

Bug#835416: imagevis3d: FTBFS: singleton.hpp:131: undefined reference to `boost::serialization::singleton_module::is_locked()'

[peter green]

1. It's failing in the doc/genlua stuff, which is an internal tool meant
to generate documentation that is currently unfinished.  Arguably it
should be removed from source releases anyway.  So a simple fix is for
debian to just remove this directory from SUBDIRS in TuvokSubdirs.pro.
I don't see a file called TuvokSubdirs.pro , I guess you mean 
Tuvok/Tuvok.pro ?


Anyway I removed doc/genlua from SUBDIRS in Tuvok/Tuvok.pro and tried a 
build in raspbian stretch.


Unfortunately it failed with

g++ -fopenmp -Wl,-z,relro -o ../Build/ImageVis3D 
../Build/objects/BrowseData.o ../Build/objects/ImageVis3D.o 
../Build/objects/ImageVis3D_Capturing.o 
../Build/objects/ImageVis3D_Progress.o 
../Build/objects/ImageVis3D_1DTransferFunction.o 
../Build/objects/ImageVis3D_2DTransferFunction.o 
../Build/objects/ImageVis3D_FileHandling.o 
../Build/objects/ImageVis3D_WindowHandling.o 
../Build/objects/ImageVis3D_DebugWindow.o 
../Build/objects/ImageVis3D_Settings.o 
../Build/objects/ImageVis3D_Locking.o 
../Build/objects/ImageVis3D_Stereo.o ../Build/objects/ImageVis3D_Help.o 
../Build/objects/ImageVis3D_I3M.o ../Build/objects/PleaseWait.o 
../Build/objects/Welcome.o ../Build/objects/MDIRenderWin.o 
../Build/objects/MetadataDlg.o ../Build/objects/AboutDlg.o 
../Build/objects/URLDlg.o ../Build/objects/FTPDialog.o 
../Build/objects/BugRepDlg.o ../Build/objects/LODDlg.o 
../Build/objects/QTransferFunction.o 
../Build/objects/Q1DTransferFunction.o 
../Build/objects/Q2DTransferFunction.o 
../Build/objects/QDataRadioButton.o ../Build/objects/QLightPreview.o 
../Build/objects/RenderWindowGL.o ../Build/objects/RenderWindow.o 
../Build/objects/BasicSettingsDlg.o ../Build/objects/SettingsDlg.o 
../Build/objects/RAWDialog.o ../Build/objects/MIPRotDialog.o 
../Build/objects/MergeDlg.o ../Build/objects/CrashDetDlg.o 
../Build/objects/ScaleAndBiasDlg.o ../Build/objects/QTOut.o 
../Build/objects/QTLabelOut.o ../Build/objects/DialogConverter.o 
../Build/objects/main.o ../Build/objects/DebugScriptWindow.o 
../Build/objects/moc_SettingsDlg.o 
../Build/objects/moc_BasicSettingsDlg.o 
../Build/objects/moc_BrowseData.o ../Build/objects/moc_ImageVis3D.o 
../Build/objects/moc_PleaseWait.o ../Build/objects/moc_FTPDialog.o 
../Build/objects/moc_QTransferFunction.o 
../Build/objects/moc_Q1DTransferFunction.o 
../Build/objects/moc_Q2DTransferFunction.o 
../Build/objects/moc_QLightPreview.o 
../Build/objects/moc_RenderWindowGL.o ../Build/objects/moc_RAWDialog.o 
../Build/objects/moc_MIPRotDialog.o ../Build/objects/moc_Welcome.o 
../Build/objects/moc_MetadataDlg.o ../Build/objects/moc_AboutDlg.o 
../Build/objects/moc_URLDlg.o ../Build/objects/moc_BugRepDlg.o 
../Build/objects/moc_LODDlg.o ../Build/objects/moc_MergeDlg.o 
../Build/objects/moc_CrashDetDlg.o 
../Build/objects/moc_ScaleAndBiasDlg.o 
../Build/objects/moc_DebugScriptWindow.o 
../Build/objects/qrc_ImageVis3D.o-L../Tuvok/Build 
-L../Tuvok/IO/expressions -L/usr/lib/arm-linux-gnueabihf 
-L/usr/X11R6/lib -lTuvok -ltuvokexpr -lz -llua5.2 -lGLEW -ltiff -lbz2 
-fopenmp -llz4 -lGLU -lQtOpenGL -lQtGui -lQtNetwork -lQtCore -lGL -lpthread
../Tuvok/Build/libTuvok.a(SysTools.o): In function 
`SysTools::GetTempDirectory(std::__cxx11::basic_string&)':
./Tuvok/Basics/SysTools.cpp:1060: warning: the use of `tmpnam' is 
dangerous, better use `mkstemp'
../Build/objects/ImageVis3D_WindowHandling.o: In function 
`boost::serialization::singleton::get_mutable_instance()':
/usr/include/boost/serialization/singleton.hpp:131: undefined reference 
to `boost::serialization::singleton_module::is_locked()'
/usr/include/boost/serialization/singleton.hpp:131: undefined reference 
to `boost::serialization::singleton_module::is_locked()'
/usr/include/boost/serialization/singleton.hpp:131: undefined reference 
to `boost::serialization::singleton_module::is_locked()'
/usr/include/boost/serialization/singleton.hpp:131: undefined reference 
to `boost::serialization::singleton_module::is_locked()'
/usr/include/boost/serialization/singleton.hpp:131: undefined reference 
to `boost::serialization::singleton_module::is_locked()'
../Build/objects/ImageVis3D_WindowHandling.o:/usr/include/boost/serialization/singleton.hpp:131: 
more undefined references to 
`boost::serialization::singleton_module::is_locked()' follow

collect2: error: ld returned 1 exit status
Makefile:233: recipe for target '../Build/ImageVis3D' failed
make[2]: *** [../Build/ImageVis3D] Error 1
make[2]: Leaving directory '/imagevis3d-3.1.0/ImageVis3D'
Makefile:80: recipe for target 'sub-ImageVis3D-make_default-ordered' failed
make[1]: *** [sub-ImageVis3D-make_default-ordered] Error 2
make[1]: Leaving directory '/imagevis3d-3.1.0'
dh_auto_build: make -j4 returned exit code 2
debian/rules:5: recipe for target 'build' failed
make: *** [build] Error 25
dpkg-buildpackage: error: debian/rules build gave error exit status 2

Bug#838357: altos FTBFS on mips and mipsel

[Adrian Bunk]

Source: altos
Version: 1.6.8-1
Severity: serious

https://buildd.debian.org/status/package.php?p=altos=sid

...
  CC  ao_easymega.o
  CC  easymega-v1.0-1.6.8.elf
../../pdclib-root/lib/libpdclib-cortex-m3.a: file not recognized: File format 
not recognized
collect2: error: ld returned 1 exit status
Makefile:126: recipe for target 'easymega-v1.0-1.6.8.elf' failed

Bug#838336: gnome-control-center: Keybinding panel fail to open

[Raphael Hertzog]

Hi,

On Tue, 20 Sep 2016, Michael Biebl wrote:
> > (gnome-control-center:24830): Gtk-CRITICAL **: Error building template
> > class 'CcKeyboardPanel' for an instance of type 'CcKeyboardPanel':
> > .:2:1622 Invalid property: GtkScrolledWindow.propagate_natural_width
> ...
> > Versions of packages gnome-control-center depends on:
> > ii  libgtk-3-0 3.21.5-3
> 
> Does upgrading libgtk-3-0 to 3.21.6-1 fix the problem?

Yes. I already had a similar report on the Kali side:
https://bugs.kali.org/view.php?id=3579

But gtk+3.0 3.21.6 is tangled with the libc6 transition
right now and it doesn't migrate although it should since
it has waited 5 days already.

It might make sense to do a quick tpu upload to get fixes in testing?

At least that's what I did in Kali.

Cheers,
-- 
Raphaël Hertzog ◈ Debian Developer

Support Debian LTS: http://www.freexian.com/services/debian-lts.html
Learn to master Debian: http://debian-handbook.info/get/

Processed: The macs FTBFS bug is a duplicate

[Debian Bug Tracking System]

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

> reassign 835674 cython
Bug #835674 [src:macs] macs: FTBFS: MACS2/IO/PeakIO.c:1:2: error: #error Do not 
use this file, it is the result of a failed Cython compilation.
Bug reassigned from package 'src:macs' to 'cython'.
No longer marked as found in versions macs/2.1.1.20160309-1.
Ignoring request to alter fixed versions of bug #835674 to the same values 
previously set
> forcemerge 833288 835674
Bug #833288 [cython] would FTBFS now with cython 0.24.1 
MACS2/IO/PeakIO.pyx:632:49: Cannot assign type 'float' to 'int'
Bug #835674 [cython] macs: FTBFS: MACS2/IO/PeakIO.c:1:2: error: #error Do not 
use this file, it is the result of a failed Cython compilation.
Set Bug forwarded-to-address to 'https://github.com/cython/cython/issues/551'.
Added indication that 835674 affects src:macs
There is no source info for the package 'cython' at version '2.1.1.20160309-1' 
with architecture ''
Unable to make a source version for version '2.1.1.20160309-1'
There is no source info for the package 'cython' at version 'macs' with 
architecture ''
Unable to make a source version for version 'macs'
Marked as found in versions cython/0.24.1-1, macs, and 2.1.1.20160309-1.
Added tag(s) upstream.
Bug #833288 [cython] would FTBFS now with cython 0.24.1 
MACS2/IO/PeakIO.pyx:632:49: Cannot assign type 'float' to 'int'
Added tag(s) sid and stretch.
Merged 833288 835674
> thanks
Stopping processing here.

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

Processed: The two seahorse-nautilus FTBFS bugs are the same bug

[Debian Bug Tracking System]

Processing control commands:

> merge 835675 835702
Bug #835675 [src:seahorse-nautilus] seahorse-nautilus: FTBFS: conftest.c:11:28: 
fatal error: ac_nonexistent.h: No such file or directory
Bug #835702 [src:seahorse-nautilus] seahorse-nautilus: FTBFS: conftest.c:64:20: 
error: expected expression before ')' token
Merged 835675 835702
> tags 835675 +fixed-upstream
Bug #835675 [src:seahorse-nautilus] seahorse-nautilus: FTBFS: conftest.c:11:28: 
fatal error: ac_nonexistent.h: No such file or directory
Bug #835702 [src:seahorse-nautilus] seahorse-nautilus: FTBFS: conftest.c:64:20: 
error: expected expression before ')' token
Added tag(s) fixed-upstream.
Added tag(s) fixed-upstream.
> tags 835675 +patch
Bug #835675 [src:seahorse-nautilus] seahorse-nautilus: FTBFS: conftest.c:11:28: 
fatal error: ac_nonexistent.h: No such file or directory
Bug #835702 [src:seahorse-nautilus] seahorse-nautilus: FTBFS: conftest.c:64:20: 
error: expected expression before ')' token
Added tag(s) patch.
Added tag(s) patch.

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