Bug#834367: marked as done (systemctl daemon-reexec (as run on systemd upgrade) causes all keystrokes to go to text console in addition to X (including passwords))

[Debian Bug Tracking System]

Your message dated Thu, 18 Aug 2016 05:20:05 +
with message-id 
and subject line Bug#834367: fixed in systemd 231-4
has caused the Debian Bug report #834367,
regarding systemctl daemon-reexec (as run on systemd upgrade) causes all 
keystrokes to go to text console in addition to X (including passwords)
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.)


-- 
834367: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=834367
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: systemd
Version: 231-2
Severity: critical
Tags: security

[Severity and tag due to the likely possibility of exposing user
passwords this way.  If this occurs with the version in jessie as well,
it'll require a security update.]

After running "systemctl daemon-reexec" from within an X session, all
keystrokes in the X session (including passwords) appear on the
underlying text console as well.  They show up during the shutdown
process, or any other time X stops.

Since systemd's postinst runs "systemctl daemon-reexec" on upgrades,
this would occur in any session after upgrading the systemd package.

I can reliably reproduce this, either by upgrading or downgrading the
systemd package, or by running "systemctl daemon-reexec" (as root).

This might potentially explain the mention in bug 819500 of seeing
usernames and passwords on the console, as well.  This would only happen
in a session after upgrading systemd or otherwise running "systemctl
daemon-reexec", which would explain not seeing it every time.

-- Package-specific info:

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

Kernel: Linux 4.7.0-rc7-amd64 (SMP w/4 CPU cores)
Locale: LANG=C.UTF-8, LC_CTYPE=C.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  adduser 3.115
ii  libacl1 2.2.52-3
ii  libapparmor12.10.95-4
ii  libaudit1   1:2.6.5-1
ii  libblkid1   2.28-6
ii  libc6   2.23-4
ii  libcap2 1:2.25-1
ii  libcap2-bin 1:2.25-1
ii  libcryptsetup4  2:1.7.0-2
ii  libgcrypt20 1.7.2-2
ii  libgpg-error0   1.24-1
ii  libidn111.33-1
ii  libkmod222-1.1
ii  liblzma55.1.1alpha+20120614-2.1
ii  libmount1   2.28-6
ii  libpam0g1.1.8-3.3
ii  libseccomp2 2.3.1-2
ii  libselinux1 2.5-3
ii  libsystemd0 231-2
ii  mount   2.28-6
ii  util-linux  2.28-6

Versions of packages systemd recommends:
ii  dbus1.10.8-1
ii  libpam-systemd  231-2

Versions of packages systemd suggests:
ii  policykit-10.105-16
pn  systemd-container  
pn  systemd-ui 

Versions of packages systemd is related to:
ii  udev  231-2

-- no debconf information
--- End Message ---
--- Begin Message ---
Source: systemd
Source-Version: 231-4

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

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Thu, 18 Aug 2016 07:03:13 +0200
Source: systemd
Binary: systemd systemd-sysv systemd-container systemd-journal-remote 
systemd-coredump libpam-systemd libnss-myhostname libnss-mymachines 
libnss-resolve libsystemd0 libsystemd-dev udev libudev1 libudev-dev udev-udeb 
libudev1-udeb
Architecture: source
Version: 231-4
Distribution: unstable
Urgency: medium
Maintainer: Debian systemd Maintainers 

Changed-By: Martin Pitt 
Description:
 libnss-myhostname - nss module providing fallback resolution for the current 
hostname
 libnss-mymachines - nss module to resolve hostnames for local container 
instances
 libnss-resolve - nss module to resolve names via systemd-resolved
 libpam-systemd - system and service manager - PAM module
 libsystemd-dev - systemd utility library - 

Processed: fixed 831857 in 1:1.6.17-1.2+deb7u1

[Debian Bug Tracking System]

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

> fixed 831857 1:1.6.17-1.2+deb7u1
Bug #831857 [src:libupnp] libupnp: CVE-2016-6255: write files via POST
The source 'libupnp' and version '1:1.6.17-1.2+deb7u1' do not appear to match 
any binary packages
Marked as fixed in versions libupnp/1:1.6.17-1.2+deb7u1.
> thanks
Stopping processing here.

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

Bug#831964: marked as done (pentium-builder: FTBFS with dpkg-buildpackage -A: dpkg-genchanges: error: binary build with no binary artifacts found; cannot distribute)

[Debian Bug Tracking System]

Your message dated Thu, 18 Aug 2016 04:14:34 +
with message-id 
and subject line Bug#831964: fixed in pentium-builder 0.21
has caused the Debian Bug report #831964,
regarding pentium-builder: FTBFS with dpkg-buildpackage -A: dpkg-genchanges: 
error: binary build with no binary artifacts found; cannot distribute
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.)


-- 
831964: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=831964
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: pentium-builder
Version: 0.20
Severity: important
Tags: stretch sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20160720 qa-ftbfs qa-indep
Justification: FTBFS on amd64

Hi,

During a rebuild of all packages in sid, your package failed to build on
amd64.  This rebuild was done by building only the architecture-independent
packages.  At the same time, a normal build succeeded, which points the
problem specifically to build-indep/binary-indep targets.


The specific error below usually happens there is a binary-indep target in
debian/rules which is either empty or does not do anything useful.

If all the arch-independent packages are dummy transitional packages released
with jessie, the easy fix is to drop them now. If not, debian/rules should be
modified so that the binary-indep target generates the architecture independent
packages (and only those).

After checking that both "dpkg-buildpackage -A" and "dpkg-buildpackage -B" work
properly, this package will be suitable to be uploaded in source-only form if
you wish.

I file this bug as severity: important, but Santiago Vila, who led this
effort (kudos to him), got approval from the release team to consider those
bugs RC for stretch. The severity will be increased to 'serious' shortly.
See #830997 for details.

Relevant part (hopefully):
>  fakeroot debian/rules binary-indep
> dh_testdir
> dh_testroot
> dh_clean -k
> dh_clean: dh_clean -k is deprecated; use dh_prep instead
> dh_installdirs usr/bin
> install builder-cc builder-c++ debian/pentium-builder/usr/bin
> dh_link usr/bin/builder-cc usr/bin/gcc \
>   usr/bin/builder-c++ usr/bin/g++
>  dpkg-genchanges --build=all >../pentium-builder_0.20_all.changes
> dpkg-genchanges: error: binary build with no binary artifacts found; cannot 
> distribute

The full build log is available from:
   
http://people.debian.org/~lucas/logs/2016/07/20/pentium-builder_0.20_unstable_archallonly.log

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: pentium-builder
Source-Version: 0.21

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

Debian distribution maintenance software
pp.
Alex Pennace  (supplier of updated pentium-builder 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, 17 Aug 2016 21:54:37 -0400
Source: pentium-builder
Binary: pentium-builder
Architecture: source all
Version: 0.21
Distribution: unstable
Urgency: medium
Maintainer: Alex Pennace 
Changed-By: Alex Pennace 
Description:
 pentium-builder - force pentium optimized compilation
Closes: 831964
Changes:
 pentium-builder (0.21) unstable; urgency=medium
 .
   * Fix "FTBFS with dpkg-buildpackage -A: dpkg-genchanges: error: binary
 build with no binary artifacts found; cannot distribute", thanks
 Santiago Vila (Closes: #831964).
   * Fix email address in previous changelog entry.
Checksums-Sha1:
 a81cf583f346c0abb9015476049b08ae0dc55715 1049 pentium-builder_0.21.dsc
 e51f97ae169d37ed4892795c9b68dda4e0badb29 5815 pentium-builder_0.21.tar.gz
 7d785aaa013f19557743595d98f13a4ba6946505 7156 pentium-builder_0.21_all.deb

Bug#834631: marked as done (mcmcpack: FTBFS: ERROR: dependency 'mcmc' is not available for package 'MCMCpack')

[Debian Bug Tracking System]

Your message dated Thu, 18 Aug 2016 00:19:27 +
with message-id 
and subject line Bug#834631: fixed in mcmcpack 1.3-6-2
has caused the Debian Bug report #834631,
regarding mcmcpack: FTBFS: ERROR: dependency 'mcmc' is not available for 
package 'MCMCpack'
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.)


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

Dear Maintainer,

mcmcpack fails to build from source in unstable/amd64:

  [..]

  Preparing to unpack .../51-gfortran-6_6.1.1-12_amd64.deb ...
  Unpacking gfortran-6 (6.1.1-12) ...
  Selecting previously unselected package gfortran.
  Preparing to unpack .../52-gfortran_4%3a6.1.1-1_amd64.deb ...
  Unpacking gfortran (4:6.1.1-1) ...
  Selecting previously unselected package libblas-dev.
  Preparing to unpack .../53-libblas-dev_3.6.1-2_amd64.deb ...
  Unpacking libblas-dev (3.6.1-2) ...
  Selecting previously unselected package liblapack-dev.
  Preparing to unpack .../54-liblapack-dev_3.6.1-2_amd64.deb ...
  Unpacking liblapack-dev (3.6.1-2) ...
  Selecting previously unselected package libtinfo-dev:amd64.
  Preparing to unpack .../55-libtinfo-dev_6.0+20160625-1_amd64.deb ...
  Unpacking libtinfo-dev:amd64 (6.0+20160625-1) ...
  Selecting previously unselected package libncurses5-dev:amd64.
  Preparing to unpack .../56-libncurses5-dev_6.0+20160625-1_amd64.deb ...
  Unpacking libncurses5-dev:amd64 (6.0+20160625-1) ...
  Selecting previously unselected package libreadline6-dev:amd64.
  Preparing to unpack .../57-libreadline6-dev_6.3-8+b4_amd64.deb ...
  Unpacking libreadline6-dev:amd64 (6.3-8+b4) ...
  Selecting previously unselected package libreadline-dev:amd64.
  Preparing to unpack .../58-libreadline-dev_6.3-8+b4_amd64.deb ...
  Unpacking libreadline-dev:amd64 (6.3-8+b4) ...
  Selecting previously unselected package libjpeg62-turbo-dev:amd64.
  Preparing to unpack .../59-libjpeg62-turbo-dev_1%3a1.5.0-1_amd64.deb ...
  Unpacking libjpeg62-turbo-dev:amd64 (1:1.5.0-1) ...
  Selecting previously unselected package libjpeg-dev.
  Preparing to unpack .../60-libjpeg-dev_1%3a1.5.0-1_all.deb ...
  Unpacking libjpeg-dev (1:1.5.0-1) ...
  Selecting previously unselected package libpcre16-3:amd64.
  Preparing to unpack .../61-libpcre16-3_2%3a8.39-1_amd64.deb ...
  Unpacking libpcre16-3:amd64 (2:8.39-1) ...
  Selecting previously unselected package libpcre32-3:amd64.
  Preparing to unpack .../62-libpcre32-3_2%3a8.39-1_amd64.deb ...
  Unpacking libpcre32-3:amd64 (2:8.39-1) ...
  Selecting previously unselected package libpcrecpp0v5:amd64.
  Preparing to unpack .../63-libpcrecpp0v5_2%3a8.39-1_amd64.deb ...
  Unpacking libpcrecpp0v5:amd64 (2:8.39-1) ...
  Selecting previously unselected package libpcre3-dev:amd64.
  Preparing to unpack .../64-libpcre3-dev_2%3a8.39-1_amd64.deb ...
  Unpacking libpcre3-dev:amd64 (2:8.39-1) ...
  Selecting previously unselected package zlib1g-dev:amd64.
  Preparing to unpack .../65-zlib1g-dev_1%3a1.2.8.dfsg-2+b1_amd64.deb ...
  Unpacking zlib1g-dev:amd64 (1:1.2.8.dfsg-2+b1) ...
  Selecting previously unselected package libpng-dev:amd64.
  Preparing to unpack .../66-libpng-dev_1.6.24-2_amd64.deb ...
  Unpacking libpng-dev:amd64 (1.6.24-2) ...
  Selecting previously unselected package libbz2-dev:amd64.
  Preparing to unpack .../67-libbz2-dev_1.0.6-8_amd64.deb ...
  Unpacking libbz2-dev:amd64 (1.0.6-8) ...
  Selecting previously unselected package liblzma-dev:amd64.
  Preparing to unpack .../68-liblzma-dev_5.1.1alpha+20120614-2.1_amd64.deb ...
  Unpacking liblzma-dev:amd64 (5.1.1alpha+20120614-2.1) ...
  Selecting previously unselected package icu-devtools.
  Preparing to unpack .../69-icu-devtools_57.1-2_amd64.deb ...
  Unpacking icu-devtools (57.1-2) ...
  Selecting previously unselected package libasan2:amd64.
  Preparing to unpack .../70-libasan2_5.4.1-1_amd64.deb ...
  Unpacking libasan2:amd64 (5.4.1-1) ...
  Selecting previously unselected package libmpx0:amd64.
  Preparing to unpack .../71-libmpx0_5.4.1-1_amd64.deb ...
  Unpacking libmpx0:amd64 (5.4.1-1) ...
  Selecting previously unselected package libgcc-5-dev:amd64.
  Preparing to unpack .../72-libgcc-5-dev_5.4.1-1_amd64.deb ...
  Unpacking libgcc-5-dev:amd64 (5.4.1-1) ...
  Selecting previously unselected package libstdc++-5-dev:amd64.
  Preparing 

Bug#834686: ruby-httpclient: FTBFS too much often (failing tests)

[Santiago Vila]

Package: src:ruby-httpclient
Version: 2.7.1-1
Severity: serious

Dear maintainer:

I tried to build this package with "dpkg-buildpackage -A"
(which is what the "Arch: all" autobuilder would do to build it)
but it failed:


[...]
 debian/rules build-indep
dh build-indep --buildsystem=ruby --with ruby
   dh_testdir -i -O--buildsystem=ruby
   dh_update_autotools_config -i -O--buildsystem=ruby
   dh_auto_configure -i -O--buildsystem=ruby
dh_ruby --configure
   dh_auto_build -i -O--buildsystem=ruby
dh_ruby --build
   dh_ruby --build
   dh_auto_test -i -O--buildsystem=ruby
dh_ruby --test
 fakeroot debian/rules binary-indep
dh binary-indep --buildsystem=ruby --with ruby

[... snipped ...]

  test_debug_dev:   .: (1.147961)
  test_no_sslv3:F
===
Failure: test_no_sslv3(TestSSL)
/<>/test/test_ssl.rb:221:in `test_no_sslv3'
 218: 
 219:   def test_no_sslv3
 220: teardown_server
  => 221: assert_raise(ArgumentError) do
 222:   setup_server_with_ssl_version(:SSLv3)
 223:   @client.ssl_config.verify_mode = nil
 224:   @client.get("https://localhost:#{serverport}/hello;)

 expected but was


diff:
? ArgumentErrno::EADDRINUSE()
===
: (1.109614)
  test_options: .: (0.101632)
  test_proxy_ssl:   .: (1.284714)
  test_set_default_paths:   .: (1.151999)
  test_sync:.: (1.191771)
  test_use_higher_TLS:  O
===
TODO: it does not pass with Java 7 or old openssl  
[test_use_higher_TLS(TestSSL)]
/<>/test/test_ssl.rb:238:in `test_use_higher_TLS'
===
: (1.102445)
  test_verification:.: (0.197484)

Finished in 183.685536657 seconds.
--
221 tests, 747 assertions, 1 failures, 7 errors, 0 pendings, 1 omissions, 0 
notifications
96.3636% passed
--
1.20 tests/s, 4.07 assertions/s
rake aborted!
Command failed with status (1): [ruby -I"test"  
"/usr/lib/ruby/vendor_ruby/rake/rake_test_loader.rb" "test/test_auth.rb" 
"test/test_cookie.rb" "test/test_hexdump.rb" "test/test_http-access2.rb" 
"test/test_httpclient.rb" "test/test_include_client.rb" 
"test/test_jsonclient.rb" "test/test_ssl.rb" "test/test_webagent-cookie.rb" -v]

Tasks: TOP => default
(See full trace by running task with --trace)
ERROR: Test "ruby2.3" failed. Exiting.
dh_auto_install: dh_ruby --install /<>/debian/ruby-httpclient 
returned exit code 1
debian/rules:6: recipe for target 'binary-indep' failed
make: *** [binary-indep] Error 1
dpkg-buildpackage: error: fakeroot debian/rules binary-indep gave error exit 
status 2


Because this source package only generates "Arch: all" packages, this
is the same as a FTBFS bug in the usual sense and the fact that I was
using "dpkg-buildpackage -A" is quite irrelevant.

For this particular package, I've also checked that it fails to build
from source in the reproducible builds site:

https://tests.reproducible-builds.org/

Thanks.

Bug#834683: mini-buildd: FTBFS too much often (failing tests)

[Santiago Vila]

Package: src:mini-buildd
Version: 1.0.16
Severity: serious

Dear maintainer:

I tried to build this package with "dpkg-buildpackage -A"
(which is what the "Arch: all" autobuilder would do to build it)
but it failed:


[...]
 debian/rules build-indep
dh build-indep --with=python2,sphinxdoc,systemd
   dh_testdir -i
   dh_update_autotools_config -i
   dh_auto_configure -i
   debian/rules override_dh_auto_build
make[1]: Entering directory '/<>'
dh_auto_build
python setup.py build --force
I: Using setuptools: 20.10.1
I: Got version from changelog: 1.0.16
running build
running build_py

[... snipped ...]

mini_buildd.builder.Build.build
mini_buildd.builder.Build.clean
mini_buildd.builder.Build.distribution
mini_buildd.builder.Build.key
mini_buildd.builder.Build.package
mini_buildd.builder.Build.sbuildrc_path
mini_buildd.builder.Build.took
mini_buildd.builder.Build.upload
mini_buildd.builder.Build.upload_result_to
mini_buildd.builder.Build.version
mini_buildd.builder.LastBuild
mini_buildd.builder.LastBuild.__init__
mini_buildd.builder.LastBuild.__unicode__
mini_buildd.builder.build
mini_buildd.builder.build_close
mini_buildd.builder.run
0 tests in 25 items.
0 passed and 0 failed.
Test passed.
=> Doctest on mini_buildd/setup.py (mini_buildd.setup)
/<>/mini_buildd/misc.py:27: ImportWarning: Not importing directory 
'/<>/debian': missing __init__.py
  import debian.debian_support
/usr/lib/python2.7/dist-packages/registration/models.py:140: 
RemovedInDjango20Warning: on_delete will be a required arg for OneToOneField in 
Django 2.0. Set it to models.CASCADE on models and in existing migrations if 
you want to maintain the current default behavior. See 
https://docs.djangoproject.com/en/1.10/ref/models/fields/#django.db.models.ForeignKey.on_delete
  verbose_name=_(u'user'))
/usr/lib/python2.7/dist-packages/registration/migrations/0001_initial.py:31: 
RemovedInDjango20Warning: on_delete will be a required arg for OneToOneField in 
Django 2.0. Set it to models.CASCADE on models and in existing migrations if 
you want to maintain the current default behavior. See 
https://docs.djangoproject.com/en/1.10/ref/models/fields/#django.db.models.ForeignKey.on_delete
  verbose_name='user')),
2 items had no tests:
mini_buildd.setup
mini_buildd.setup.log_exception
0 tests in 2 items.
0 passed and 0 failed.
Test passed.
=> Doctest on mini_buildd/gnupg.py (mini_buildd.gnupg)
/<>/mini_buildd/misc.py:27: ImportWarning: Not importing directory 
'/<>/debian': missing __init__.py
  import debian.debian_support
/usr/lib/python2.7/dist-packages/registration/models.py:140: 
RemovedInDjango20Warning: on_delete will be a required arg for OneToOneField in 
Django 2.0. Set it to models.CASCADE on models and in existing migrations if 
you want to maintain the current default behavior. See 
https://docs.djangoproject.com/en/1.10/ref/models/fields/#django.db.models.ForeignKey.on_delete
  verbose_name=_(u'user'))
/usr/lib/python2.7/dist-packages/registration/migrations/0001_initial.py:31: 
RemovedInDjango20Warning: on_delete will be a required arg for OneToOneField in 
Django 2.0. Set it to models.CASCADE on models and in existing migrations if 
you want to maintain the current default behavior. See 
https://docs.djangoproject.com/en/1.10/ref/models/fields/#django.db.models.ForeignKey.on_delete
  verbose_name='user')),
D: TmpDir /tmp/tmpvXY9eX
I: Calling: gpg --homedir=/tmp/tmpvXY9eX --display-charset=UTF-8 --batch 
--gen-key
make[1]: *** wait: No child processes.  Stop.
make[1]: *** Waiting for unfinished jobs
make[1]: *** wait: No child processes.  Stop.
make: *** wait: No child processes.  Stop.
make: *** Waiting for unfinished jobs
make: *** wait: No child processes.  Stop.
Build killed with signal TERM after 60 minutes of inactivity


I actually tried to build this package three times, and there was
only one successful build from those three. I don't think that's
an acceptable statistic of successful builds for a releaseable package.

Because this source package only generates "Arch: all" packages, this
is the same as a FTBFS bug in the usual sense and the fact that I was
using "dpkg-buildpackage -A" is quite irrelevant.

For this particular package, I've also checked that it fails to build
from source in the reproducible builds site:

https://tests.reproducible-builds.org/

but in this case the error is different.

Thanks.

Bug#834682: mina2: FTBFS too much often (failing tests)

[Santiago Vila]

Package: src:mina2
Version: 2.0.13-1
Severity: serious

Dear maintainer:

I tried to build this package with "dpkg-buildpackage -A"
(which is what the "Arch: all" autobuilder would do to build it)
but it failed:


[...]
 debian/rules build-indep
dh build-indep --buildsystem=maven
   dh_testdir -i -O--buildsystem=maven
   dh_update_autotools_config -i -O--buildsystem=maven
   dh_auto_configure -i -O--buildsystem=maven
find: '/usr/share/maven-repo/org/codehaus/plexus/plexus-compiler/*/*.jar': No 
such file or directory
find: '/usr/share/maven-repo/org/codehaus/plexus/plexus-compilers/*/*.jar': No 
such file or directory
find: '/usr/share/maven-repo/org/codehaus/plexus/plexus-containers/*/*.jar': No 
such file or directory
mh_patchpoms -plibmina2-java --debian-build --keep-pom-version 
--maven-repo=/<>/debian/maven-repo
   debian/rules override_dh_auto_build
make[1]: Entering directory '/<>'
dh_auto_build -- -f src/pom.xml package javadoc:aggregate
/usr/lib/jvm/default-java/bin/java -noverify -cp 
/usr/share/maven/boot/plexus-classworlds-2.x.jar:/usr/lib/jvm/default-java/lib/tools.jar
 -Dmaven.home=/usr/share/maven 
-Dmaven.multiModuleProjectDirectory=/<> 
-Dclassworlds.conf=/etc/maven/m2-debian.conf 
-Dproperties.file.manual=/<>/debian/maven.properties 
org.codehaus.plexus.classworlds.launcher.Launcher 
-s/etc/maven/settings-debian.xml -Ddebian.dir=/<>/debian 
-Dmaven.repo.local=/<>/debian/maven-repo -f src/pom.xml package 
javadoc:aggregate -DskipTests -Dnotimestamp=true -Dlocale=en_US

[... snipped ...]

Running org.apache.mina.core.IoServiceListenerSupportTest
Tests run: 4, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 1.026 sec - in 
org.apache.mina.core.IoServiceListenerSupportTest

Results :

Tests in error: 
  NioFileRegionTest.testSendLargeFile ?? IO Broken pipe

Tests run: 201, Failures: 0, Errors: 1, Skipped: 5

[INFO] 
[INFO] Reactor Summary:
[INFO] 
[INFO] Apache MINA  SUCCESS [  0.007 s]
[INFO] Apache MINA Core ... FAILURE [01:26 min]
[INFO] Apache MINA APR Transport .. SKIPPED
[INFO] Apache MINA Compression Filter . SKIPPED
[INFO] Apache MINA JavaBeans Integration .. SKIPPED
[INFO] Apache MINA XBean Integration .. SKIPPED
[INFO] Apache MINA OGNL Integration ... SKIPPED
[INFO] Apache MINA JMX Integration  SKIPPED
[INFO] 
[INFO] BUILD FAILURE
[INFO] 
[INFO] Total time: 01:27 min
[INFO] Finished at: 2016-08-09T06:00:19+02:00
[INFO] Final Memory: 11M/60M
[INFO] 
[ERROR] Failed to execute goal 
org.apache.maven.plugins:maven-surefire-plugin:2.17:test (default-test) on 
project mina-core: There are test failures.
[ERROR] 
[ERROR] Please refer to /<>/src/mina-core/target/surefire-reports 
for the individual test results.
[ERROR] -> [Help 1]
[ERROR] 
[ERROR] To see the full stack trace of the errors, re-run Maven with the -e 
switch.
[ERROR] Re-run Maven using the -X switch to enable full debug logging.
[ERROR] 
[ERROR] For more information about the errors and possible solutions, please 
read the following articles:
[ERROR] [Help 1] 
http://cwiki.apache.org/confluence/display/MAVEN/MojoFailureException
[ERROR] 
[ERROR] After correcting the problems, you can resume the build with the command
[ERROR]   mvn  -rf :mina-core
dh_auto_test: /usr/lib/jvm/default-java/bin/java -noverify -cp 
/usr/share/maven/boot/plexus-classworlds-2.x.jar:/usr/lib/jvm/default-java/lib/tools.jar
 -Dmaven.home=/usr/share/maven 
-Dmaven.multiModuleProjectDirectory=/<> 
-Dclassworlds.conf=/etc/maven/m2-debian.conf 
-Dproperties.file.manual=/<>/debian/maven.properties 
org.codehaus.plexus.classworlds.launcher.Launcher 
-s/etc/maven/settings-debian.xml -Ddebian.dir=/<>/debian 
-Dmaven.repo.local=/<>/debian/maven-repo -f src/pom.xml test 
returned exit code 1
debian/rules:12: recipe for target 'override_dh_auto_test' failed
make[1]: *** [override_dh_auto_test] Error 1
make[1]: Leaving directory '/<>'
debian/rules:6: recipe for target 'build-indep' failed
make: *** [build-indep] Error 2
dpkg-buildpackage: error: debian/rules build-indep gave error exit status 2


Because this source package only generates "Arch: all" packages, this
is the same as a FTBFS bug in the usual sense and the fact that I was
using "dpkg-buildpackage -A" is quite irrelevant.

For this particular package, I've also checked that it fails to build
from source in the reproducible builds site:

Bug#834685: python-reno: FTBFS too much often (failing tests)

[Santiago Vila]

Package: src:python-reno
Version: 1.3.0-3
Severity: serious

Dear maintainer:

I tried to build this package with "dpkg-buildpackage -A"
(which is what the "Arch: all" autobuilder would do to build it)
but it failed:


[...]
 debian/rules build-indep
pyversions: missing X(S)-Python-Version in control file, fall back to 
debian/pyversions
pyversions: missing debian/pyversions file, fall back to supported versions
py3versions: no X-Python3-Version in control file, using supported versions
dh /usr/share/openstack-pkg-tools/pkgos.make --buildsystem=python_distutils 
--with python2,python3,sphinxdoc
dh: Unknown sequence /usr/share/openstack-pkg-tools/pkgos.make (choose from: 
binary binary-arch binary-indep build build-arch build-indep clean install 
install-arch install-indep)
dh build-indep --buildsystem=python_distutils --with python2,python3,sphinxdoc
   dh_testdir -i -O--buildsystem=python_distutils
   dh_update_autotools_config -i -O--buildsystem=python_distutils
   dh_auto_configure -i -O--buildsystem=python_distutils
   dh_auto_build -i -O--buildsystem=python_distutils
pyversions: missing X(S)-Python-Version in control file, fall back to 
debian/pyversions
pyversions: missing debian/pyversions file, fall back to supported versions

[... snipped ...]

  File "/usr/lib/python2.7/subprocess.py", line 567, in check_output
process = Popen(stdout=PIPE, *popenargs, **kwargs)
  File "/usr/lib/python2.7/subprocess.py", line 711, in __init__
errread, errwrite)
  File "/usr/lib/python2.7/subprocess.py", line 1343, in _execute_child
raise child_exception
OSError: [Errno 2] No such file or directory


==
FAIL: reno.tests.test_scanner.UniqueIdTest.test_modern
reno.tests.test_scanner.UniqueIdTest.test_modern
--
_StringException: Empty attachments:
  pythonlogging:''
  stderr
  stdout

Traceback (most recent call last):
  File "reno/tests/test_scanner.py", line 178, in setUp
self.useFixture(GPGKeyFixture())
  File "/usr/lib/python2.7/dist-packages/testtools/testcase.py", line 679, in 
useFixture
reraise(*exc_info)
  File "/usr/lib/python2.7/dist-packages/testtools/testcase.py", line 666, in 
useFixture
fixture.setUp()
  File "reno/tests/test_scanner.py", line 67, in setUp
cwd=tempdir.path)
  File "reno/utils.py", line 44, in check_output
raw = subprocess.check_output(*args, **kwds)
  File "/usr/lib/python2.7/subprocess.py", line 567, in check_output
process = Popen(stdout=PIPE, *popenargs, **kwargs)
  File "/usr/lib/python2.7/subprocess.py", line 711, in __init__
errread, errwrite)
  File "/usr/lib/python2.7/subprocess.py", line 1343, in _execute_child
raise child_exception
OSError: [Errno 2] No such file or directory


--
Ran 27 tests in 0.372s

FAILED (failures=22)
debian/rules:29: recipe for target 'override_dh_auto_test' failed
make[1]: *** [override_dh_auto_test] Error 1
make[1]: Leaving directory '/<>'
debian/rules:12: recipe for target 'build-indep' failed
make: *** [build-indep] Error 2
dpkg-buildpackage: error: debian/rules build-indep gave error exit status 2


Because this source package only generates "Arch: all" packages, this
is the same as a FTBFS bug in the usual sense and the fact that I was
using "dpkg-buildpackage -A" is quite irrelevant.

For this particular package, I've also checked that it fails to build
from source in the reproducible builds site:

https://tests.reproducible-builds.org/

Thanks.

Bug#834684: python-pbr: FTBFS too much often (failing tests)

[Santiago Vila]

Package: src:python-pbr
Version: 1.8.0-4.1
Severity: serious

Dear maintainer:

I tried to build this package with "dpkg-buildpackage -A"
(which is what the "Arch: all" autobuilder would do to build it)
but it failed:


[...]
 debian/rules build-indep
pyversions: missing X(S)-Python-Version in control file, fall back to 
debian/pyversions
pyversions: missing debian/pyversions file, fall back to supported versions
py3versions: no X-Python3-Version in control file, using supported versions
pyversions: missing X(S)-Python-Version in control file, fall back to 
debian/pyversions
pyversions: missing debian/pyversions file, fall back to supported versions
py3versions: no X-Python3-Version in control file, using supported versions
dh build-indep --buildsystem=python_distutils --with python2,python3,sphinxdoc
   dh_testdir -i -O--buildsystem=python_distutils
   dh_update_autotools_config -i -O--buildsystem=python_distutils
   dh_auto_configure -i -O--buildsystem=python_distutils
   dh_auto_build -i -O--buildsystem=python_distutils
pyversions: missing X(S)-Python-Version in control file, fall back to 
debian/pyversions

[... snipped ...]

stderr=subprocess.PIPE, cwd=cwd)
  File "/usr/lib/python2.7/subprocess.py", line 711, in __init__
errread, errwrite)
  File "/usr/lib/python2.7/subprocess.py", line 1343, in _execute_child
raise child_exception
OSError: [Errno 2] No such file or directory


==
FAIL: 
pbr.tests.test_packaging.TestVersions.test_valid_tag_honoured(postversioned)
pbr.tests.test_packaging.TestVersions.test_valid_tag_honoured(postversioned)
--
_StringException: Empty attachments:
  pythonlogging:''
  pythonlogging:'pbr'
  stderr

stdout: {{{Initialized empty Git repository in 
/tmp/tmpkKFWL8/tmpv7w8vy/testpackage/.git/}}}
traceback-1: {{{
Traceback (most recent call last):
  File "pbr/tests/test_packaging.py", line 275, in setUp
self.useFixture(GPGKeyFixture())
  File "/usr/lib/python2.7/dist-packages/testtools/testcase.py", line 679, in 
useFixture
reraise(*exc_info)
  File "/usr/lib/python2.7/dist-packages/testtools/testcase.py", line 666, in 
useFixture
fixture.setUp()
  File "pbr/tests/test_packaging.py", line 103, in setUp
gnupg_version = base._run_cmd(['gpg', '--version'], tempdir.path)
  File "pbr/tests/base.py", line 202, in _run_cmd
stderr=subprocess.PIPE, cwd=cwd)
  File "/usr/lib/python2.7/subprocess.py", line 711, in __init__
errread, errwrite)
  File "/usr/lib/python2.7/subprocess.py", line 1343, in _execute_child
raise child_exception
OSError: [Errno 2] No such file or directory
}}}


--
Ran 140 tests in 9.468s

FAILED (failures=32, skipped=10)
debian/rules:39: recipe for target 'override_dh_auto_test' failed
make[1]: *** [override_dh_auto_test] Error 1
make[1]: Leaving directory '/<>'
debian/rules:15: recipe for target 'build-indep' failed
make: *** [build-indep] Error 2
dpkg-buildpackage: error: debian/rules build-indep gave error exit status 2


Because this source package only generates "Arch: all" packages, this
is the same as a FTBFS bug in the usual sense and the fact that I was
using "dpkg-buildpackage -A" is quite irrelevant.

For this particular package, I've also checked that it fails to build
from source in the reproducible builds site:

https://tests.reproducible-builds.org/

Thanks.

Bug#834672: marked as done (mapnik-vector-tile: FTBFS in testing (boost related linking error))

[Debian Bug Tracking System]

Your message dated Thu, 18 Aug 2016 00:38:48 +0200
with message-id 
and subject line Re: Bug#834672: mapnik-vector-tile: FTBFS in testing (boost 
related linking error)
has caused the Debian Bug report #834672,
regarding mapnik-vector-tile: FTBFS in testing (boost related linking error)
to be marked as done.

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

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


-- 
834672: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=834672
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:mapnik-vector-tile
Version: 1.1.2+dfsg-1
Severity: serious

Dear maintainer:

I tried to build this package with "dpkg-buildpackage -A"
(which is what the "Arch: all" autobuilder would do to build it)
but it failed:


[...]
 debian/rules build-indep
dh build-indep --parallel
   dh_testdir -i -O--parallel
   dh_update_autotools_config -i -O--parallel
   dh_auto_configure -i -O--parallel
   debian/rules override_dh_auto_build
make[1]: Entering directory '/<>/mapnik-vector-tile-1.1.2+dfsg'
mkdir -p deps/gyp
ln -s /usr/bin/gyp deps/gyp/gyp
mkdir -p deps/clipper/cpp
ln -s /<>/mapnik-vector-tile-1.1.2+dfsg/debian/clipper.cpp 
deps/clipper/cpp/clipper.cpp
ln -s /<>/mapnik-vector-tile-1.1.2+dfsg/debian/clipper.hpp 
deps/clipper/cpp/clipper.hpp
dh_auto_build

[... snipped ...]

 from ../test/utils/geom_to_wkt.cpp:2:
/usr/include/boost/type_traits/detail/template_arity_spec.hpp:13:84: note: 
#pragma message: NOTE: Use of this header (template_arity_spec.hpp) is 
deprecated
 # pragma message("NOTE: Use of this header (template_arity_spec.hpp) is 
deprecated")

^
In file included from 
/usr/include/boost/iostreams/detail/is_dereferenceable.hpp:13:0,
 from /usr/include/boost/iostreams/detail/resolve.hpp:26,
 from /usr/include/boost/iostreams/detail/push.hpp:24,
 from 
/usr/include/boost/iostreams/detail/streambuf/indirect_streambuf.hpp:31,
 from /usr/include/boost/iostreams/stream_buffer.hpp:22,
 from /usr/include/boost/iostreams/stream.hpp:21,
 from 
/usr/include/boost/spirit/home/qi/stream/detail/iterator_source.hpp:14,
 from /usr/include/boost/spirit/home/qi/stream/stream.hpp:16,
 from /usr/include/boost/spirit/home/qi/stream.hpp:15,
 from /usr/include/boost/spirit/home/qi.hpp:30,
 from /usr/include/boost/spirit/include/qi.hpp:16,
 from /usr/include/mapnik/wkt/wkt_grammar.hpp:32,
 from /usr/include/mapnik/wkt/wkt_factory.hpp:29,
 from /usr/include/mapnik/util/geometry_to_wkt.hpp:27,
 from ../test/utils/geom_to_wkt.cpp:2:
/usr/include/boost/type_traits/detail/template_arity_spec.hpp:13:84: note: 
#pragma message: NOTE: Use of this header (template_arity_spec.hpp) is 
deprecated
 # pragma message("NOTE: Use of this header (template_arity_spec.hpp) is 
deprecated")

^
  CXX(target) Release/obj.target/tests/test/utils/encoding_util.o
  CXX(target) Release/obj.target/tests/test/utils/round_trip.o
  CXX(target) Release/obj.target/tests/test/utils/decoding_util.o
  LINK(target) Release/tests
/usr/bin/ld: warning: libboost_filesystem.so.1.58.0, needed by 
/usr/lib/libmapnik.so, may conflict with libboost_filesystem.so.1.61.0
/usr/bin/ld: warning: libboost_regex.so.1.58.0, needed by 
/usr/lib/libmapnik.so, may conflict with libboost_regex.so.1.61.0
/usr/bin/ld: warning: libicui18n.so.55, needed by /usr/lib/libmapnik.so, may 
conflict with libicui18n.so.57
/usr/bin/ld: warning: libboost_system.so.1.58.0, needed by 
/usr/lib/libmapnik.so, may conflict with libboost_system.so.1.61.0
/usr/bin/ld: warning: libicuuc.so.55, needed by /usr/lib/libmapnik.so, may 
conflict with libicuuc.so.57
/usr/bin/ld: /usr/lib/libmapnik.so: undefined reference to symbol 
'_ZN6icu_5513UnicodeStringC1ERKS0_'
//usr/lib/x86_64-linux-gnu/libicuuc.so.55: error adding symbols: DSO missing 
from command line
collect2: error: ld returned 1 exit status
gyp/tests.target.mk:253: recipe for target 'Release/tests' failed
make[3]: *** [Release/tests] Error 1
rm gyp_build_gyp_make_vector_tile_target_run_protoc.intermediate
make[3]: Leaving directory '/<>/mapnik-vector-tile-1.1.2+dfsg/build'
Makefile:23: recipe for target 'libvtile' failed
make[2]: *** [libvtile] 

Processed: Re: Bug#834672: mapnik-vector-tile: FTBFS in testing (boost related linking error)

[Debian Bug Tracking System]

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

> notfound 834672 mapnik-vector-tile/1.1.2+dfsg-1
Bug #834672 [src:mapnik-vector-tile] mapnik-vector-tile: FTBFS in testing 
(boost related linking error)
No longer marked as found in versions mapnik-vector-tile/1.1.2+dfsg-1.
> thanks
Stopping processing here.

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

Bug#834680: tomcat7: FTBFS in testing (failing tests)

[Santiago Vila]

Package: src:tomcat7
Version: 7.0.70-2
Severity: serious

Dear maintainer:

I tried to build this package with "dpkg-buildpackage -A"
(which is what the "Arch: all" autobuilder would do to build it)
but it failed:


[...]
 debian/rules build-indep
dh build-indep
   dh_testdir -i
   dh_update_autotools_config -i
   dh_auto_configure -i
   debian/rules override_dh_auto_build
make[1]: Entering directory '/<>'
ant -propertyfile debian/ant.properties -Dyear=2016 -Dtoday='Aug 2 2016' 
-Dtstamp=09:43:11 -Ddistribution.name=Debian extras-jmx-remote deploy
Buildfile: /<>/build.xml

extras-prepare:
[mkdir] Created dir: /<>/output/extras
[mkdir] Created dir: /<>/output/extras-src-jars

[... snipped ...]

[junit] INFO: Starting test case [testDuplicatePaths_02]
[junit] Aug 10, 2016 9:40:15 PM org.apache.coyote.AbstractProtocol destroy
[junit] INFO: Destroying ProtocolHandler ["http-nio-127.0.0.1-auto-6"]
[junit] Aug 10, 2016 9:40:15 PM org.apache.catalina.startup.LoggingBaseTest 
setUp
[junit] INFO: Starting test case [testDuplicatePaths_03]
[junit] Aug 10, 2016 9:40:15 PM org.apache.coyote.AbstractProtocol destroy
[junit] INFO: Destroying ProtocolHandler ["http-nio-127.0.0.1-auto-7"]
[junit] Aug 10, 2016 9:40:15 PM org.apache.catalina.startup.LoggingBaseTest 
setUp
[junit] INFO: Starting test case [testDuplicatePaths_04]
[junit] Aug 10, 2016 9:40:15 PM org.apache.coyote.AbstractProtocol destroy
[junit] INFO: Destroying ProtocolHandler ["http-nio-127.0.0.1-auto-8"]
[junit] Running util.TestCookieFilter
[junit] Tests run: 10, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 
0.038 sec

test-apr-exists:

test-apr:

cobertura-report:

test:
   [concat] Testsuites with skipped tests:
   [concat] TEST-org.apache.catalina.comet.TestCometProcessor.BIO.txt
   [concat] 
TEST-org.apache.catalina.loader.TestWebappClassLoaderThreadLocalMemoryLeak.BIO.txt
   [concat] 
TEST-org.apache.catalina.loader.TestWebappClassLoaderThreadLocalMemoryLeak.NIO.txt
   [concat] 
TEST-org.apache.catalina.session.TestStandardSessionIntegration.BIO.txt
   [concat] 
TEST-org.apache.catalina.session.TestStandardSessionIntegration.NIO.txt
   [concat] TEST-org.apache.tomcat.websocket.TestWsWebSocketContainer.BIO.txt
   [concat] 
TEST-org.apache.tomcat.websocket.TestWsWebSocketContainerWithProxy.BIO.txt
   [concat] 
TEST-org.apache.tomcat.websocket.TestWsWebSocketContainerWithProxy.NIO.txt
   [concat] 
TEST-org.apache.tomcat.websocket.server.TestWsRemoteEndpointImplServer.BIO.txt
   [concat] 
TEST-org.apache.tomcat.websocket.server.TestWsRemoteEndpointImplServer.NIO.txt
   [concat] Testsuites with failed tests:
   [concat] TEST-org.apache.tomcat.websocket.TestWebSocketFrameClient.BIO.txt
   [concat] TEST-org.apache.tomcat.websocket.TestWebSocketFrameClient.NIO.txt
   [concat] TEST-org.apache.tomcat.websocket.TestWebSocketFrameClientSSL.BIO.txt
   [concat] TEST-org.apache.tomcat.websocket.TestWebSocketFrameClientSSL.NIO.txt

BUILD FAILED
/<>/build.xml:1381: Some tests completed with an Error. See 
/<>/output/build/logs for details, search for "ERROR".

Total time: 43 minutes 27 seconds
debian/rules:31: recipe for target 'override_dh_auto_test' failed
make[1]: *** [override_dh_auto_test] Error 1
make[1]: Leaving directory '/<>'
debian/rules:18: recipe for target 'build-indep' failed
make: *** [build-indep] Error 2
dpkg-buildpackage: error: debian/rules build-indep gave error exit status 2


Because this source package only generates "Arch: all" packages, this
is the same as a FTBFS bug in the usual sense and the fact that I was
using "dpkg-buildpackage -A" is quite irrelevant.

For this particular package, I've also checked that it fails to build
from source in the reproducible builds site:

https://tests.reproducible-builds.org/

Thanks.

Bug#834679: surefire: FTBFS in testing (1 required artifact is missing)

[Santiago Vila]

Package: src:surefire
Version: 2.17-2
Severity: serious

Dear maintainer:

I tried to build this package with "dpkg-buildpackage -A"
(which is what the "Arch: all" autobuilder would do to build it)
but it failed:


[...]
 debian/rules build-indep
dh_listpackages: -s/--same-arch is deprecated; please use -a/--arch instead
test -x debian/rules
mkdir -p "."
cd . && /usr/lib/jvm/default-java/bin/java -classpath 
/usr/share/ant/lib/ant.jar:/usr/share/ant/lib/ant-launcher.jar:/usr/share/java/maven-core.jar:/usr/share/java/maven-model.jar:/usr/share/java/maven-plugin-api.jar:/usr/share/java/maven-project.jar:/usr/share/java/plexus-utils.jar:/usr/share/java/plexus-container-default-alpha.jar:/usr/lib/jvm/default-java/lib/tools.jar
 -Dant.home=/usr/share/ant org.apache.tools.ant.Main -Dpackage=surefire 
-Dversion=2.17 -buildfile debian/build.xml package 
Buildfile: /<>/debian/build.xml

package:
[mkdir] Created dir: 
/<>/surefire-grouper/target/generated-sources
   [javacc] Java Compiler Compiler Version 5.0 (Parser Generator)
   [javacc] (type "javacc" with no arguments for help)
   [javacc] Reading from file 
/<>/surefire-grouper/src/main/javacc/category-expression.jj . . .
   [javacc] File "TokenMgrError.java" does not exist.  Will create one.

[... snipped ...]

 [java] 1) org.apache.commons:commons-lang3:jar:3.x
 [java] 
 [java]   Try downloading the file manually from the project website.
 [java] 
 [java]   Then, install it using the command: 
 [java]   mvn install:install-file -DgroupId=org.apache.commons 
-DartifactId=commons-lang3 -Dversion=3.x -Dpackaging=jar -Dfile=/path/to/file
 [java] 
 [java]   Alternatively, if you host your own repository you can deploy the 
file there: 
 [java]   mvn deploy:deploy-file -DgroupId=org.apache.commons 
-DartifactId=commons-lang3 -Dversion=3.x -Dpackaging=jar -Dfile=/path/to/file 
-Durl=[url] -DrepositoryId=[id]
 [java] 
 [java]   Path to dependency: 
 [java] 1) 
org.apache.maven.plugins:maven-surefire-plugin:maven-plugin:2.17
 [java] 2) org.apache.maven.surefire:maven-surefire-common:jar:debian
 [java] 3) org.apache.commons:commons-lang3:jar:3.x
 [java] 
 [java] --
 [java] 1 required artifact is missing.
 [java] 
 [java] for artifact: 
 [java]   org.apache.maven.plugins:maven-surefire-plugin:maven-plugin:2.17
 [java] 
 [java] from the specified remote repositories:
 [java]   central (https://repo1.maven.org/maven2)
 [java] 
 [java] 
 [java] at 
org.apache.maven.artifact.resolver.DefaultArtifactResolver.resolveTransitively(DefaultArtifactResolver.java:361)
 [java] at 
org.apache.maven.artifact.resolver.DefaultArtifactResolver.resolveTransitively(DefaultArtifactResolver.java:304)
 [java] at 
org.apache.maven.plugin.DefaultPluginManager.resolveTransitiveDependencies(DefaultPluginManager.java:1499)
 [java] at 
org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:442)
 [java] at 
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:694)
 [java] ... 9 more
 [java] [INFO] 

 [java] [INFO] Total time: 1 second
 [java] [INFO] Finished at: Tue Aug 16 17:42:30 CEST 2016
 [java] [INFO] Final Memory: 5M/13M
 [java] [INFO] 


BUILD FAILED
/<>/debian/build.xml:111: The following error occurred while 
executing this line:
/<>/debian/build.xml:34: The following error occurred while 
executing this line:
/usr/share/maven-ant-helper/maven-build.xml:325: The following error occurred 
while executing this line:
/usr/share/maven-ant-helper/maven-build.xml:320: The following error occurred 
while executing this line:
/usr/share/maven-ant-helper/maven-build.xml:297: Java returned: 1

Total time: 48 seconds
/usr/share/cdbs/1/class/ant.mk:39: recipe for target 'debian/stamp-ant-build' 
failed
make: *** [debian/stamp-ant-build] Error 1
dpkg-buildpackage: error: debian/rules build-indep gave error exit status 2


Because this source package only generates "Arch: all" packages, this
is the same as a FTBFS bug in the usual sense and the fact that I was
using "dpkg-buildpackage -A" is quite irrelevant.

For this particular package, I've also checked that it fails to build
from source in the reproducible builds site:

https://tests.reproducible-builds.org/

Thanks.

Bug#834674: pyevolve: FTBFS in testing (Format: "jpeg" not recognized)

[Santiago Vila]

Package: src:pyevolve
Version: 0.6~rc1+svn398+dfsg-9
Severity: serious

Dear maintainer:

I tried to build this package with "dpkg-buildpackage -A"
(which is what the "Arch: all" autobuilder would do to build it)
but it failed:


[...]
 debian/rules build-indep
dh  build-indep --with python2,sphinxdoc --buildsystem=pybuild
   dh_testdir -i -O--buildsystem=pybuild
   dh_update_autotools_config -i -O--buildsystem=pybuild
   dh_auto_configure -i -O--buildsystem=pybuild
I: pybuild base:184: python2.7 setup.py config 
running config
   debian/rules override_dh_auto_build
make[1]: Entering directory '/<>/pyevolve-0.6~rc1+svn398+dfsg'
dh_auto_build
I: pybuild base:184: /usr/bin/python setup.py build 
running build
running build_py

[... snipped ...]

   
   .. versionadded:: 0.6
  The *GTreeGPMutatorSubtree* function
   
Slot [Crossover] (Count: 1)
Name: GTreeGPCrossoverSinglePoint - Weight: 0.50
Doc:  The crossover of the GTreeGP, Single Point for Genetic 
Programming

   ..note:: This crossover method creates offspring with restriction of the
*max_depth* parameter.
   
   Accepts the *max_attempt* parameter, *max_depth* (required).   
   

- GTree
Height: 2
Nodes:  5

GTreeNodeBase [Childs=2] - [gp_mul]
  GTreeNodeBase [Childs=2] - [gp_add]
GTreeNodeBase [Childs=0] - [a]
GTreeNodeBase [Childs=0] - [a]
  GTreeNodeBase [Childs=0] - [b]

- GTreeGP
Expression: gp_mul(gp_add(a, a), b)

Traceback (most recent call last):
  File "pyevolve_ex19_gp.py", line 85, in 
main_run()
  File "pyevolve_ex19_gp.py", line 82, in main_run
graph.write_jpeg('tree.png', prog='dot')
  File "/usr/lib/python2.7/dist-packages/pydot.py", line 1746, in 
lambda path, f=frmt, prog=self.prog: self.write(path, format=f, prog=prog)
  File "/usr/lib/python2.7/dist-packages/pydot.py", line 1851, in write
fobj.write(self.create(prog, format))
  File "/usr/lib/python2.7/dist-packages/pydot.py", line 1961, in create
status, stderr_output))
pydot.InvocationException: Program terminated with status: 1. stderr follows: 
Format: "jpeg" not recognized. Use one of: canon cmap cmapx cmapx_np dot eps 
fig gd gd2 gv imap imap_np ismap pdf pic plain plain-ext png pov ps ps2 svg 
svgz tk vml vmlz x11 xdot xdot1.2 xdot1.4 xlib

E: pybuild pybuild:274: test: plugin custom failed with: exit code=1: /bin/sh 
/<>/pyevolve-0.6~rc1+svn398+dfsg/debian/tests/run-most-examples
dh_auto_test: pybuild --test -i python{version} -p 2.7 returned exit code 13
debian/rules:37: recipe for target 'override_dh_auto_test' failed
make[1]: *** [override_dh_auto_test] Error 25
make[1]: Leaving directory '/<>/pyevolve-0.6~rc1+svn398+dfsg'
debian/rules:22: recipe for target 'build-indep' failed
make: *** [build-indep] Error 2
dpkg-buildpackage: error: debian/rules build-indep gave error exit status 2


Because this source package only generates "Arch: all" packages, this
is the same as a FTBFS bug in the usual sense and the fact that I was
using "dpkg-buildpackage -A" is quite irrelevant.

For this particular package, I've also checked that it fails to build
from source in the reproducible builds site:

https://tests.reproducible-builds.org/

Thanks.

Bug#834677: refcard: FTBFS in testing (xelatex compilation failed)

[Santiago Vila]

Package: src:refcard
Version: 9.0.1
Severity: serious

Dear maintainer:

I tried to build this package with "dpkg-buildpackage -A"
(which is what the "Arch: all" autobuilder would do to build it)
but it failed:


[...]
 debian/rules build-indep
dh_listpackages: -s/--same-arch is deprecated; please use -a/--arch instead
test -x debian/rules
mkdir -p "."
USE_DBLATEX=1 LC_ALL=en_US.utf8 /usr/bin/make -C . CFLAGS="-g -O2 
-fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat 
-Werror=format-security" CXXFLAGS="-g -O2 -fdebug-prefix-map=/<>=. 
-fstack-protector-strong -Wformat -Werror=format-security" 
CPPFLAGS="-Wdate-time -D_FORTIFY_SOURCE=2" LDFLAGS="-Wl,-z,relro" 
make[1]: Entering directory '/<>'
cp -f entries.dbk entries-en.dbk
po4a-translate --format docbook --keep 0 -m entries.dbk -p po4a/bg.po -l 
entries-bg.dbk
perl: warning: Setting locale failed.
perl: warning: Please check that your locale settings:
LANGUAGE = (unset),
LC_ALL = "en_US.utf8",
LANG = (unset)

[... snipped ...]

refcard-ja.dbk.tex:132: leading text: }&
refcard-ja.dbk.tex:132: Missing } inserted.
refcard-ja.dbk.tex:132: leading text: }&
refcard-ja.dbk.tex:132: Extra }, or forgotten $.
refcard-ja.dbk.tex:132: leading text: }&
refcard-ja.dbk.tex:132: Missing } inserted.
refcard-ja.dbk.tex:132: leading text: }&
refcard-ja.dbk.tex:132: Extra }, or forgotten $.
refcard-ja.dbk.tex:132: leading text: }&
refcard-ja.dbk.tex:132: Missing } inserted.
refcard-ja.dbk.tex:132: leading text: }&
refcard-ja.dbk.tex:132: Extra }, or forgotten $.
refcard-ja.dbk.tex:132: leading text: }&
refcard-ja.dbk.tex:132: Missing } inserted.
refcard-ja.dbk.tex:132: leading text: }&
refcard-ja.dbk.tex:132: Extra }, or forgotten $.
refcard-ja.dbk.tex:132: leading text: }&
refcard-ja.dbk.tex:132: Missing } inserted.
refcard-ja.dbk.tex:132: leading text: }&
refcard-ja.dbk.tex:132: Extra }, or forgotten $.
refcard-ja.dbk.tex:132: leading text: }&
refcard-ja.dbk.tex:132: Missing } inserted.
refcard-ja.dbk.tex:132: leading text: }&
refcard-ja.dbk.tex:132: Extra }, or forgotten $.
refcard-ja.dbk.tex:132: leading text: }&
refcard-ja.dbk.tex:132: Missing } inserted.
refcard-ja.dbk.tex:132: leading text: }&
refcard-ja.dbk.tex:132: Extra }, or forgotten $.
refcard-ja.dbk.tex:132: leading text: }&
refcard-ja.dbk.tex:132: Missing } inserted.
refcard-ja.dbk.tex:132: leading text: }&
refcard-ja.dbk.tex:132: Extra }, or forgotten $.
refcard-ja.dbk.tex:132: leading text: }&
refcard-ja.dbk.tex:132: Missing } inserted.
refcard-ja.dbk.tex:132: leading text: }&
refcard-ja.dbk.tex:132: Extra }, or forgotten $.
refcard-ja.dbk.tex:132: leading text: }&
refcard-ja.dbk.tex:132: Missing } inserted.
refcard-ja.dbk.tex:132: leading text: }&
Unexpected error occured
Error: xelatex compilation failed
Makefile:76: recipe for target 'refcard-ja-a4.s.pdf' failed
make[1]: *** [refcard-ja-a4.s.pdf] Error 1
rm refcard-pt.dbk refcard-bg-a4.fo refcard-pt-a4.s.pdf refcard-ml-a4.s.pdf 
refcard-ml.dbk refcard-pt-a4.t.pdf refcard-pt-a4.fo refcard-ja.dbk 
refcard-en-a4.t.pdf refcard-ml-a4.t.pdf refcard-en-a4.s.pdf refcard-bg-a4.s.pdf 
refcard-en.dbk refcard-bg.dbk refcard-ml-a4.fo refcard-en-a4.fo 
refcard-bg-a4.t.pdf refcard-ja-a4.fo
make[1]: Leaving directory '/<>'
/usr/share/cdbs/1/class/makefile.mk:77: recipe for target 
'debian/stamp-makefile-build' failed
make: *** [debian/stamp-makefile-build] Error 2
dpkg-buildpackage: error: debian/rules build-indep gave error exit status 2


Because this source package only generates "Arch: all" packages, this
is the same as a FTBFS bug in the usual sense and the fact that I was
using "dpkg-buildpackage -A" is quite irrelevant.

For this particular package, I've also checked that it fails to build
from source in the reproducible builds site:

https://tests.reproducible-builds.org/

Thanks.

Bug#834678: sorl-thumbnail: FTBFS in testing (failing tests)

[Santiago Vila]

Package: src:sorl-thumbnail
Version: 12.3-3
Severity: serious

Dear maintainer:

I tried to build this package with "dpkg-buildpackage -A"
(which is what the "Arch: all" autobuilder would do to build it)
but it failed:


[...]
 debian/rules build-indep
dh build-indep --with python2,python3,sphinxdoc --buildsystem=pybuild
   dh_testdir -i -O--buildsystem=pybuild
   dh_update_autotools_config -i -O--buildsystem=pybuild
   dh_auto_configure -i -O--buildsystem=pybuild
I: pybuild base:184: python2.7 setup.py config 
running config
I: pybuild base:184: python3.5 setup.py config 
running config
   debian/rules override_dh_auto_build
make[1]: Entering directory '/<>'
dh_auto_build
I: pybuild base:184: /usr/bin/python setup.py build 

[... snipped ...]


cls = , name = 'ContentType'
bases = (,)
attrs = {'__str__': , 'app_label': 
, 'get_all_objects_f...r_this_type at 
0x7f8e3b80e0c8>, 'get_object_for_this_type': , ...}

def __new__(cls, name, bases, attrs):
super_new = super(ModelBase, cls).__new__

# Also ensure initialization is only performed for subclasses of Model
# (excluding Model class itself).
parents = [b for b in bases if isinstance(b, ModelBase)]
if not parents:
return super_new(cls, name, bases, attrs)

# Create the class.
module = attrs.pop('__module__')
new_class = super_new(cls, name, bases, {'__module__': module})
attr_meta = attrs.pop('Meta', None)
abstract = getattr(attr_meta, 'abstract', False)
if not attr_meta:
meta = getattr(new_class, 'Meta', None)
else:
meta = attr_meta
base_meta = getattr(new_class, '_meta', None)

app_label = None

# Look for an application configuration to attach the model to.
app_config = apps.get_containing_app_config(module)

if getattr(meta, 'app_label', None) is None:
if app_config is None:
if not abstract:
raise RuntimeError(
"Model class %s.%s doesn't declare an explicit "
"app_label and isn't in an application in "
>   "INSTALLED_APPS." % (module, name)
)
E   RuntimeError: Model class 
django.contrib.contenttypes.models.ContentType doesn't declare an explicit 
app_label and isn't in an application in INSTALLED_APPS.

/usr/lib/python2.7/dist-packages/django/db/models/base.py:113: RuntimeError
=== 13 failed, 50 passed, 2 skipped in 2.07 seconds 
debian/rules:22: recipe for target 'override_dh_auto_test' failed
make[1]: *** [override_dh_auto_test] Error 1
make[1]: Leaving directory '/<>'
debian/rules:10: recipe for target 'build-indep' failed
make: *** [build-indep] Error 2
dpkg-buildpackage: error: debian/rules build-indep gave error exit status 2


Because this source package only generates "Arch: all" packages, this
is the same as a FTBFS bug in the usual sense and the fact that I was
using "dpkg-buildpackage -A" is quite irrelevant.

For this particular package, I've also checked that it fails to build
from source in the reproducible builds site:

https://tests.reproducible-builds.org/

Thanks.

Bug#834670: gnuchess-book: FTBFS in testing (build takes forever and has to be killed)

[Santiago Vila]

Package: src:gnuchess-book
Version: 1.02-1
Severity: serious

Dear maintainer:

I tried to build this package with "dpkg-buildpackage -A"
(which is what the "Arch: all" autobuilder would do to build it)
but it failed:


[...]
 debian/rules build-indep
dh build-indep
   dh_testdir -i
   dh_update_autotools_config -i
   dh_auto_configure -i
   debian/rules override_dh_auto_build
make[1]: Entering directory '/<>'
dh_testdir book_1.02.pgn
# Spam only if stdout is a tty
Building book.
make[1]: *** wait: No child processes.  Stop.
make[1]: *** Waiting for unfinished jobs
make[1]: *** wait: No child processes.  Stop.
make: *** wait: No child processes.  Stop.
make: *** Waiting for unfinished jobs
make: *** wait: No child processes.  Stop.
Build killed with signal TERM after 60 minutes of inactivity


Because this source package only generates "Arch: all" packages, this
is the same as a FTBFS bug in the usual sense and the fact that I was
using "dpkg-buildpackage -A" is quite irrelevant.

For this particular package, I've also checked that it fails to build
from source in the reproducible builds site:

https://tests.reproducible-builds.org/

You will notice that my autobuilder waited "only" for 60 minutes
before giving up. Well, the autobuilder from reproducible builds
waited for 18 hours.

The end result was the same: The build had to be killed.

Thanks.

Bug#834634: grib-api: Incorrect library path in CMake module (/usr/lib/lib/libgrib_api.so.0)

[Sebastiaan Couwenberg]

Control: tags -1 patch

Hi Alastair,

The attached patch fixes the library path, and the patched package 
allows the rebuilds for magics++ & metview with the proj 4.9.3 release 
candidate to succeed.


Kind Regards,

Bas

--
 GPG Key ID: 4096R/6750F10AE88D4AF1
Fingerprint: 8182 DE41 7056 408D 6146  50D1 6750 F10A E88D 4AF1
diff -Nru grib-api-1.16.0/debian/changelog grib-api-1.16.0/debian/changelog
--- grib-api-1.16.0/debian/changelog2016-08-12 12:57:44.0 +0200
+++ grib-api-1.16.0/debian/changelog2016-08-17 21:25:16.0 +0200
@@ -1,3 +1,10 @@
+grib-api (1.16.0-5.1) UNRELEASED; urgency=medium
+
+  * Non-maintainer upload.
+  * Fix library path in CMake module.
+
+ -- Bas Couwenberg   Wed, 17 Aug 2016 21:25:05 +0200
+
 grib-api (1.16.0-5) unstable; urgency=medium
 
   * Sanitise cmake/* scripts more to remove all dependencies.
diff -Nru grib-api-1.16.0/debian/rules grib-api-1.16.0/debian/rules
--- grib-api-1.16.0/debian/rules2016-08-12 12:57:44.0 +0200
+++ grib-api-1.16.0/debian/rules2016-08-17 22:32:59.0 +0200
@@ -90,6 +90,7 @@
cp debian/tmp/usr/share/grib_api/cmake/* 
debian/libgrib-api-dev/$(LIBDIR)/cmake/grib_api
cat debian/tmp/usr/share/grib_api//cmake/grib_api-targets-release.cmake 
| \
sed -e 's% *IMPORTED_LINK_INTERFACE_LIBRARIES_RELEASE.*%  
IMPORTED_LINK_INTERFACE_LIBRARIES_RELEASE ""%' \
+   -e 's%$${_IMPORT_PREFIX}%/usr%g' \
 > 
debian/libgrib-api-dev/$(LIBDIR)/cmake/grib_api/grib_api-targets-release.cmake
cat debian/tmp/usr/share/grib_api//cmake/grib_api-config.cmake | \
sed -e 's%^set( grib_api_BASE_DIR.*%set ( grib_api_BASE_DIR 
/build/grib-api )%' | \

Processed: grib-api: Incorrect library path in CMake module (/usr/lib/lib/libgrib_api.so.0)

[Debian Bug Tracking System]

Processing control commands:

> tags -1 patch
Bug #834634 [src:grib-api] grib-api: Incorrect library path in CMake module 
(/usr/lib/lib/libgrib_api.so.0)
Added tag(s) patch.

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

Bug#834676: python-oauth2client: FTBFS in testing ('module' object has no attribute 'SubfieldBase')

[Santiago Vila]

Package: src:python-oauth2client
Version: 2.0.1-3
Severity: serious

Dear maintainer:

I tried to build this package with "dpkg-buildpackage -A"
(which is what the "Arch: all" autobuilder would do to build it)
but it failed:


[...]
 debian/rules build-indep
pyversions: missing X(S)-Python-Version in control file, fall back to 
debian/pyversions
pyversions: missing debian/pyversions file, fall back to supported versions
py3versions: no X-Python3-Version in control file, using supported versions
pyversions: missing X(S)-Python-Version in control file, fall back to 
debian/pyversions
pyversions: missing debian/pyversions file, fall back to supported versions
py3versions: no X-Python3-Version in control file, using supported versions
dh build-indep --buildsystem=python_distutils --with python2,python3
   dh_testdir -i -O--buildsystem=python_distutils
   dh_update_autotools_config -i -O--buildsystem=python_distutils
   dh_auto_configure -i -O--buildsystem=python_distutils
   dh_auto_build -i -O--buildsystem=python_distutils
pyversions: missing X(S)-Python-Version in control file, fall back to 
debian/pyversions

[... snipped ...]

test_true (tests.test_jwt.TestHasOpenSSLFlag) ... ok
test__to_json_override 
(tests.test_service_account.ServiceAccountCredentialsTests) ... ok
test_access_token (tests.test_service_account.ServiceAccountCredentialsTests) 
... ok
test_create_delegated 
(tests.test_service_account.ServiceAccountCredentialsTests) ... ok
test_create_delegated_existing_sub 
(tests.test_service_account.ServiceAccountCredentialsTests) ... ok
test_create_scoped (tests.test_service_account.ServiceAccountCredentialsTests) 
... ok
test_create_scoped_required_with_scopes 
(tests.test_service_account.ServiceAccountCredentialsTests) ... ok
test_create_scoped_required_without_scopes 
(tests.test_service_account.ServiceAccountCredentialsTests) ... ok
test_from_json_keyfile_name_factory 
(tests.test_service_account.ServiceAccountCredentialsTests) ... ok
test_from_json_keyfile_name_factory_bad_type 
(tests.test_service_account.ServiceAccountCredentialsTests) ... ok
test_from_json_keyfile_name_factory_missing_field 
(tests.test_service_account.ServiceAccountCredentialsTests) ... ok
test_from_p12_keyfile_buffer 
(tests.test_service_account.ServiceAccountCredentialsTests) ... ok
test_from_p12_keyfile_defaults 
(tests.test_service_account.ServiceAccountCredentialsTests) ... ok
test_from_p12_keyfile_explicit 
(tests.test_service_account.ServiceAccountCredentialsTests) ... ok
test_from_p12_keyfile_with_pycrypto 
(tests.test_service_account.ServiceAccountCredentialsTests) ... ok
test_from_p12_keyfile_with_rsa 
(tests.test_service_account.ServiceAccountCredentialsTests) ... ok
test_service_account_email 
(tests.test_service_account.ServiceAccountCredentialsTests) ... ok
test_sign_blob (tests.test_service_account.ServiceAccountCredentialsTests) ... 
ok
test_ClientRedirectServer (tests.test_tools.TestClientRedirectServer) ... SKIP: 
Skipped in Debian: doing network access
test_iterables (tests.test_util.ScopeToStringTests) ... ok
test_conversion (tests.test_util.StringToScopeTests) ... ok

==
ERROR: Failure: AttributeError ('module' object has no attribute 'SubfieldBase')
--
Traceback (most recent call last):
  File "/usr/lib/python2.7/dist-packages/nose/loader.py", line 418, in 
loadTestsFromName
addr.filename, addr.module)
  File "/usr/lib/python2.7/dist-packages/nose/importer.py", line 47, in 
importFromPath
return self.importFromDir(dir_path, fqname)
  File "/usr/lib/python2.7/dist-packages/nose/importer.py", line 94, in 
importFromDir
mod = load_module(part_fqname, fh, filename, desc)
  File "tests/contrib/test_django_orm.py", line 53, in 
from oauth2client.contrib.django_orm import CredentialsField
  File "/<>/oauth2client/contrib/django_orm.py", line 34, in 

class CredentialsField(six.with_metaclass(models.SubfieldBase, 
models.Field)):
AttributeError: 'module' object has no attribute 'SubfieldBase'

--
Ran 350 tests in 1.076s

FAILED (SKIP=1, errors=1)
debian/rules:29: recipe for target 'override_dh_auto_test' failed
make[1]: *** [override_dh_auto_test] Error 1
make[1]: Leaving directory '/<>'
debian/rules:15: recipe for target 'build-indep' failed
make: *** [build-indep] Error 2
dpkg-buildpackage: error: debian/rules build-indep gave error exit status 2


Because this source package only generates "Arch: all" packages, this
is the same as a FTBFS bug in the usual sense and the fact that I was
using "dpkg-buildpackage -A" is quite irrelevant.

For this particular package, I've also checked that it fails to build
from source in the 

Bug#834673: nevow: FTBFS in testing (failing tests)

[Santiago Vila]

Package: src:nevow
Version: 0.14.0-1
Severity: serious

Dear maintainer:

I tried to build this package with "dpkg-buildpackage -A"
(which is what the "Arch: all" autobuilder would do to build it)
but it failed:


[...]
 debian/rules build-indep
dh build-indep --with python2,sphinxdoc --buildsystem=pybuild
   dh_testdir -i -O--buildsystem=pybuild
   dh_update_autotools_config -i -O--buildsystem=pybuild
   dh_auto_configure -i -O--buildsystem=pybuild
I: pybuild base:184: python2.7 setup.py config 
running config
   dh_auto_build -i -O--buildsystem=pybuild
I: pybuild base:184: /usr/bin/python setup.py build 
running build
got version from file /<>/nevow/_version.py {'version': '0.14.0', 
'full': '8204df0b63285ddbcc02e0cd56b21cd3757f7d83'}
running build_py
package init file 'twisted/plugins/__init__.py' not found (or not a regular 
file)

[... snipped ...]


nevow.test.test_howtolistings.RenderAndChat01.test_basicRendering
===
[ERROR]
Traceback (most recent call last):
  File "/<>/nevow/test/test_nit.py", line 68, in 
test_errorRendering
return renderLivePage(FragmentWrapper(te)).addCallback(
  File "/<>/nevow/testutil.py", line 378, in renderLivePage
D = renderPage(res, topLevelContext, reqFactory)
  File "/<>/nevow/testutil.py", line 392, in renderPage
render = appserver.NevowRequest(None, True).gotPageContext
  File "/<>/nevow/appserver.py", line 204, in __init__
server.Request.__init__(self, *args, **kw)
  File "/usr/lib/python2.7/dist-packages/twisted/web/server.py", line 107, in 
__init__
http.Request.__init__(self, *args, **kw)
  File "/usr/lib/python2.7/dist-packages/twisted/web/http.py", line 612, in 
__init__
self.transport = self.channel.transport
exceptions.AttributeError: 'NoneType' object has no attribute 'transport'

nevow.test.test_nit.NevowInteractiveTesterTest.test_errorRendering
===
[ERROR]
Traceback (most recent call last):
  File "/<>/nevow/test/test_testutil.py", line 114, in test_urls
return renderPage(_URLPage()).addCallback(_checkForUrl)
  File "/<>/nevow/testutil.py", line 392, in renderPage
render = appserver.NevowRequest(None, True).gotPageContext
  File "/<>/nevow/appserver.py", line 204, in __init__
server.Request.__init__(self, *args, **kw)
  File "/usr/lib/python2.7/dist-packages/twisted/web/server.py", line 107, in 
__init__
http.Request.__init__(self, *args, **kw)
  File "/usr/lib/python2.7/dist-packages/twisted/web/http.py", line 612, in 
__init__
self.transport = self.channel.transport
exceptions.AttributeError: 'NoneType' object has no attribute 'transport'

nevow.test.test_testutil.TestFakeRequest.test_urls
---
Ran 902 tests in 1.217s

FAILED (skips=21, expectedFailures=4, failures=71, errors=113, successes=776)
E: pybuild pybuild:274: test: plugin custom failed with: exit code=1: python2.7 
/usr/bin/trial nevow formless
dh_auto_test: pybuild --test -i python{version} -p 2.7 returned exit code 13
debian/rules:20: recipe for target 'override_dh_auto_test' failed
make[1]: *** [override_dh_auto_test] Error 25
make[1]: Leaving directory '/<>'
debian/rules:7: recipe for target 'build-indep' failed
make: *** [build-indep] Error 2
dpkg-buildpackage: error: debian/rules build-indep gave error exit status 2


Because this source package only generates "Arch: all" packages, this
is the same as a FTBFS bug in the usual sense and the fact that I was
using "dpkg-buildpackage -A" is quite irrelevant.

For this particular package, I've also checked that it fails to build
from source in the reproducible builds site:

https://tests.reproducible-builds.org/

Thanks.

Bug#834675: pygccxml: FTBFS in testing (Assertion failed)

[Santiago Vila]

Package: src:pygccxml
Version: 1.7.4-3
Severity: serious

Dear maintainer:

I tried to build this package with "dpkg-buildpackage -A"
(which is what the "Arch: all" autobuilder would do to build it)
but it failed:


[...]
 debian/rules build-indep
dh  build-indep --with python2,python3 --buildsystem=pybuild
   dh_testdir -i -O--buildsystem=pybuild
   dh_update_autotools_config -i -O--buildsystem=pybuild
   dh_auto_configure -i -O--buildsystem=pybuild
pybuild --configure -i python{version} -p 2.7
I: pybuild base:184: python2.7 setup.py config 
running config
pybuild --configure -i python{version} -p 3.5
I: pybuild base:184: python3.5 setup.py config 
running config
   debian/rules override_dh_auto_build
make[1]: Entering directory '/<>'

[... snipped ...]

INFO Parsing source file "core_ns_join_2.hpp" ... 
INFO Parsing source file "core_ns_join_3.hpp" ... 
INFO Parsing source file "core_membership.hpp" ... 
INFO Parsing source file "core_class_hierarchy.hpp" ... 
/<>/unittests/data/core_class_hierarchy.hpp:30:44: warning: direct 
base 'core::class_hierarchy::base_t' is inaccessible due to ambiguity:
class core::class_hierarchy::multi_derived_t -> class 
core::class_hierarchy::derived_private_t -> class core::class_hierarchy::base_t
class core::class_hierarchy::multi_derived_t -> class 
core::class_hierarchy::base_t [-Winaccessible-base]
class multi_derived_t : derived_private_t, protected base_t, private 
other_base_t{
   ^~~~
1 warning generated.
INFO Parsing source file "core_types.hpp" ... 
castxml: /usr/lib/llvm-3.7/include/clang/AST/Decl.h:169: llvm::StringRef 
clang::NamedDecl::getName() const: Assertion `Name.isIdentifier() && "Name is 
not a simple identifier"' failed.
Aborted
Castxml configured to simulate compiler None
Traceback (most recent call last):
  File "./unittests/test_all.py", line 161, in 
sys.exit(run_suite())
  File "./unittests/test_all.py", line 152, in run_suite
result = unittest.TextTestRunner(verbosity=2).run(create_suite())
  File "./unittests/test_all.py", line 147, in create_suite
main_suite.addTest(tester.create_suite())
  File "/<>/unittests/decl_printer_tester.py", line 68, in 
create_suite
suite.addTest(unittest.makeSuite(tester_t))
  File "/usr/lib/python2.7/unittest/loader.py", line 312, in makeSuite
return _makeLoader(prefix, sortUsing, 
suiteClass).loadTestsFromTestCase(testCaseClass)
  File "/usr/lib/python2.7/unittest/loader.py", line 56, in 
loadTestsFromTestCase
loaded_suite = self.suiteClass(map(testCaseClass, testCaseNames))
  File "/<>/unittests/decl_printer_tester.py", line 41, in __init__
compilation_mode=parser.COMPILATION_MODE.FILE_BY_FILE)
  File 
"/<>/.pybuild/pythonX.Y_2.7/build/pygccxml/parser/project_reader.py",
 line 249, in read_files
return self.__parse_file_by_file(files)
  File 
"/<>/.pybuild/pythonX.Y_2.7/build/pygccxml/parser/project_reader.py",
 line 278, in __parse_file_by_file
decls = reader.read_file(header)
  File 
"/<>/.pybuild/pythonX.Y_2.7/build/pygccxml/parser/source_reader.py",
 line 363, in read_file
return self.read_cpp_source_file(source_file)
  File 
"/<>/.pybuild/pythonX.Y_2.7/build/pygccxml/parser/source_reader.py",
 line 382, in read_cpp_source_file
xml_file = self.create_xml_file(ffname)
  File 
"/<>/.pybuild/pythonX.Y_2.7/build/pygccxml/parser/source_reader.py",
 line 333, in create_xml_file
gccxml_msg)
RuntimeError: Error occured while running CASTXML: 
E: pybuild pybuild:274: test: plugin custom failed with: exit code=1: python2.7 
./unittests/test_all.py
dh_auto_test: pybuild --test -i python{version} -p 2.7 returned exit code 13
debian/rules:18: recipe for target 'override_dh_auto_test' failed
make[1]: *** [override_dh_auto_test] Error 25
make[1]: Leaving directory '/<>'
debian/rules:8: recipe for target 'build-indep' failed
make: *** [build-indep] Error 2
dpkg-buildpackage: error: debian/rules build-indep gave error exit status 2


Because this source package only generates "Arch: all" packages, this
is the same as a FTBFS bug in the usual sense and the fact that I was
using "dpkg-buildpackage -A" is quite irrelevant.

For this particular package, I've also checked that it fails to build
from source in the reproducible builds site:

https://tests.reproducible-builds.org/

Thanks.

Bug#834672: mapnik-vector-tile: FTBFS in testing (boost related linking error)

[Santiago Vila]

Package: src:mapnik-vector-tile
Version: 1.1.2+dfsg-1
Severity: serious

Dear maintainer:

I tried to build this package with "dpkg-buildpackage -A"
(which is what the "Arch: all" autobuilder would do to build it)
but it failed:


[...]
 debian/rules build-indep
dh build-indep --parallel
   dh_testdir -i -O--parallel
   dh_update_autotools_config -i -O--parallel
   dh_auto_configure -i -O--parallel
   debian/rules override_dh_auto_build
make[1]: Entering directory '/<>/mapnik-vector-tile-1.1.2+dfsg'
mkdir -p deps/gyp
ln -s /usr/bin/gyp deps/gyp/gyp
mkdir -p deps/clipper/cpp
ln -s /<>/mapnik-vector-tile-1.1.2+dfsg/debian/clipper.cpp 
deps/clipper/cpp/clipper.cpp
ln -s /<>/mapnik-vector-tile-1.1.2+dfsg/debian/clipper.hpp 
deps/clipper/cpp/clipper.hpp
dh_auto_build

[... snipped ...]

 from ../test/utils/geom_to_wkt.cpp:2:
/usr/include/boost/type_traits/detail/template_arity_spec.hpp:13:84: note: 
#pragma message: NOTE: Use of this header (template_arity_spec.hpp) is 
deprecated
 # pragma message("NOTE: Use of this header (template_arity_spec.hpp) is 
deprecated")

^
In file included from 
/usr/include/boost/iostreams/detail/is_dereferenceable.hpp:13:0,
 from /usr/include/boost/iostreams/detail/resolve.hpp:26,
 from /usr/include/boost/iostreams/detail/push.hpp:24,
 from 
/usr/include/boost/iostreams/detail/streambuf/indirect_streambuf.hpp:31,
 from /usr/include/boost/iostreams/stream_buffer.hpp:22,
 from /usr/include/boost/iostreams/stream.hpp:21,
 from 
/usr/include/boost/spirit/home/qi/stream/detail/iterator_source.hpp:14,
 from /usr/include/boost/spirit/home/qi/stream/stream.hpp:16,
 from /usr/include/boost/spirit/home/qi/stream.hpp:15,
 from /usr/include/boost/spirit/home/qi.hpp:30,
 from /usr/include/boost/spirit/include/qi.hpp:16,
 from /usr/include/mapnik/wkt/wkt_grammar.hpp:32,
 from /usr/include/mapnik/wkt/wkt_factory.hpp:29,
 from /usr/include/mapnik/util/geometry_to_wkt.hpp:27,
 from ../test/utils/geom_to_wkt.cpp:2:
/usr/include/boost/type_traits/detail/template_arity_spec.hpp:13:84: note: 
#pragma message: NOTE: Use of this header (template_arity_spec.hpp) is 
deprecated
 # pragma message("NOTE: Use of this header (template_arity_spec.hpp) is 
deprecated")

^
  CXX(target) Release/obj.target/tests/test/utils/encoding_util.o
  CXX(target) Release/obj.target/tests/test/utils/round_trip.o
  CXX(target) Release/obj.target/tests/test/utils/decoding_util.o
  LINK(target) Release/tests
/usr/bin/ld: warning: libboost_filesystem.so.1.58.0, needed by 
/usr/lib/libmapnik.so, may conflict with libboost_filesystem.so.1.61.0
/usr/bin/ld: warning: libboost_regex.so.1.58.0, needed by 
/usr/lib/libmapnik.so, may conflict with libboost_regex.so.1.61.0
/usr/bin/ld: warning: libicui18n.so.55, needed by /usr/lib/libmapnik.so, may 
conflict with libicui18n.so.57
/usr/bin/ld: warning: libboost_system.so.1.58.0, needed by 
/usr/lib/libmapnik.so, may conflict with libboost_system.so.1.61.0
/usr/bin/ld: warning: libicuuc.so.55, needed by /usr/lib/libmapnik.so, may 
conflict with libicuuc.so.57
/usr/bin/ld: /usr/lib/libmapnik.so: undefined reference to symbol 
'_ZN6icu_5513UnicodeStringC1ERKS0_'
//usr/lib/x86_64-linux-gnu/libicuuc.so.55: error adding symbols: DSO missing 
from command line
collect2: error: ld returned 1 exit status
gyp/tests.target.mk:253: recipe for target 'Release/tests' failed
make[3]: *** [Release/tests] Error 1
rm gyp_build_gyp_make_vector_tile_target_run_protoc.intermediate
make[3]: Leaving directory '/<>/mapnik-vector-tile-1.1.2+dfsg/build'
Makefile:23: recipe for target 'libvtile' failed
make[2]: *** [libvtile] Error 2
make[2]: Leaving directory '/<>/mapnik-vector-tile-1.1.2+dfsg'
dh_auto_build: make -j1 returned exit code 2
debian/rules:21: recipe for target 'override_dh_auto_build' failed
make[1]: *** [override_dh_auto_build] Error 2
make[1]: Leaving directory '/<>/mapnik-vector-tile-1.1.2+dfsg'
debian/rules:8: recipe for target 'build-indep' failed
make: *** [build-indep] Error 2
dpkg-buildpackage: error: debian/rules build-indep gave error exit status 2


Because this source package only generates "Arch: all" packages, this
is the same as a FTBFS bug in the usual sense and the fact that I was
using "dpkg-buildpackage -A" is quite irrelevant.

For this particular package, I've also checked that it fails to build
from source in the reproducible builds site:

https://tests.reproducible-builds.org/

Thanks.

Bug#834671: libxalan2-java: FTBFS in testing (Error: could not match input)

[Santiago Vila]

Package: src:libxalan2-java
Version: 2.7.1-9
Severity: serious

Dear maintainer:

I tried to build this package with "dpkg-buildpackage -A"
(which is what the "Arch: all" autobuilder would do to build it)
but it failed:


[...]
 debian/rules build-indep
dh_listpackages: -s/--same-arch is deprecated; please use -a/--arch instead
test -x debian/rules
mkdir -p "."
rm -f lib/BCEL.jar lib/regexp.jar
ln -s /usr/share/java/bcel.jar lib/BCEL.jar
ln -s /usr/share/java/regexp.jar lib/regexp.jar
jh_linkjars
jh_build -J   
touch debian/jh_build_stamp
cd . && /usr/lib/jvm/default-java/bin/java -classpath 
/usr/share/ant/lib/ant.jar:/usr/share/ant/lib/ant-launcher.jar:/usr/share/java/xml-apis.jar:/usr/share/java/xercesImpl.jar:/usr/share/java/bsf.jar:/usr/share/java/bcel.jar:/usr/share/java/cup.jar:/usr/share/java/regexp.jar:/usr/share/java/stylebook.jar:/usr/share/java/JLex.jar:/usr/lib/jvm/default-java/lib/tools.jar
 -Dgnu.java.awt.peer.gtk.Graphics=Graphics2D -Dant.home=/usr/share/ant 
org.apache.tools.ant.Main -Dcompile.debug=true -Dcompile.optimize=true 
-propertyfile /<>/debian/ant.properties jar xsltc.unbundledjar 
javadocs docs
Buildfile: /<>/build.xml


[... snipped ...]

[javac] Note: Some input files use or override a deprecated API.
[javac] Note: Recompile with -Xlint:deprecation for details.
[javac] Note: Some input files use unchecked or unsafe operations.
[javac] Note: Recompile with -Xlint:unchecked for details.
[javac] 7 warnings

xalan-interpretive.compile:
 [echo] Compiling Xalan interpretive classes
[javac] /<>/build.xml:404: warning: 'includeantruntime' was 
not set, defaulting to build.sysclasspath=last; set to false for repeatable 
builds
[javac] Compiling 114 source files to /<>/build/classes
[javac] warning: [options] source value 1.5 is obsolete and will be removed 
in a future release
[javac] warning: [options] target value 1.5 is obsolete and will be removed 
in a future release
[javac] warning: [options] To suppress warnings about obsolete options, use 
-Xlint:-options.
[javac] Note: Some input files use or override a deprecated API.
[javac] Note: Recompile with -Xlint:deprecation for details.
[javac] Note: Some input files use unchecked or unsafe operations.
[javac] Note: Recompile with -Xlint:unchecked for details.
[javac] 3 warnings
 [copy] Copying 12 files to /<>/build/classes
 [copy] Copying 1 file to 
/<>/build/classes/org/apache/xalan/res

xsltc.prepare:
 [echo] Compiling XSLTC utilities
[javac] /<>/build.xml:452: warning: 'includeantruntime' was 
not set, defaulting to build.sysclasspath=last; set to false for repeatable 
builds
[javac] Compiling 2 source files to /<>/build/classes
[javac] warning: [options] source value 1.5 is obsolete and will be removed 
in a future release
[javac] warning: [options] target value 1.5 is obsolete and will be removed 
in a future release
[javac] warning: [options] To suppress warnings about obsolete options, use 
-Xlint:-options.
[javac] 3 warnings

xsltc.java_cup:
 [echo] java_cup preparsing
 [java] Exception in thread "main" java.lang.Error: Error: could not match 
input
 [java] at java_cup.Lexer.zzScanError(Lexer.java:728)
 [java] at java_cup.Lexer.next_token(Lexer.java:1058)
 [java] at java_cup.parser.scan(parser.java:417)
 [java] at java_cup.runtime.lr_parser.parse(lr_parser.java:578)
 [java] at java_cup.Main.parse_grammar_spec(Main.java:477)
 [java] at java_cup.Main.main(Main.java:186)
 [java] at 
org.apache.xalan.xsltc.util.JavaCupRedirect.main(JavaCupRedirect.java:90)

BUILD FAILED
/<>/build.xml:481: Java returned: 1

Total time: 8 seconds
/usr/share/cdbs/1/class/ant.mk:39: recipe for target 'debian/stamp-ant-build' 
failed
make: *** [debian/stamp-ant-build] Error 1
dpkg-buildpackage: error: debian/rules build-indep gave error exit status 2


Because this source package only generates "Arch: all" packages, this
is the same as a FTBFS bug in the usual sense and the fact that I was
using "dpkg-buildpackage -A" is quite irrelevant.

For this particular package, I've also checked that it fails to build
from source in the reproducible builds site:

https://tests.reproducible-builds.org/

Thanks.

Bug#834669: djangorestframework-gis: FTBFS in testing (failing tests)

[Santiago Vila]

Package: src:djangorestframework-gis
Version: 0.10.1-1
Severity: serious

Dear maintainer:

I tried to build this package with "dpkg-buildpackage -A"
(which is what the "Arch: all" autobuilder would do to build it)
but it failed:


[...]
 debian/rules build-indep
dh build-indep --with python2,python3 --buildsystem=pybuild
   dh_testdir -i -O--buildsystem=pybuild
   dh_update_autotools_config -i -O--buildsystem=pybuild
   dh_auto_configure -i -O--buildsystem=pybuild
I: pybuild base:184: python2.7 setup.py config 
running config
I: pybuild base:184: python3.5 setup.py config 
running config
   dh_auto_build -i -O--buildsystem=pybuild
I: pybuild base:184: /usr/bin/python setup.py build 
running build
running build_py

[... snipped ...]

  File "/usr/lib/python2.7/dist-packages/django/urls/resolvers.py", line 343, 
in _reverse_with_prefix
possibilities = self.reverse_dict.getlist(lookup_view)
  File "/usr/lib/python2.7/dist-packages/django/urls/resolvers.py", line 240, 
in reverse_dict
return self._reverse_dict[language_code]
KeyError: 'en-gb'

==
ERROR: test_inBBOXFilter_filtering 
(django_restframework_gis_tests.test_filters.TestRestFrameworkGisFilters)
--
Traceback (most recent call last):
  File "tests/django_restframework_gis_tests/test_filters.py", line 21, in setUp
self.location_contained_in_bbox_list_url = 
reverse('api_geojson_location_list_contained_in_bbox_filter')
  File "/usr/lib/python2.7/dist-packages/django/urls/base.py", line 91, in 
reverse
return force_text(iri_to_uri(resolver._reverse_with_prefix(view, prefix, 
*args, **kwargs)))
  File "/usr/lib/python2.7/dist-packages/django/urls/resolvers.py", line 343, 
in _reverse_with_prefix
possibilities = self.reverse_dict.getlist(lookup_view)
  File "/usr/lib/python2.7/dist-packages/django/urls/resolvers.py", line 240, 
in reverse_dict
return self._reverse_dict[language_code]
KeyError: 'en-gb'

==
ERROR: test_inBBOXFilter_filtering_none 
(django_restframework_gis_tests.test_filters.TestRestFrameworkGisFilters)
--
Traceback (most recent call last):
  File "tests/django_restframework_gis_tests/test_filters.py", line 21, in setUp
self.location_contained_in_bbox_list_url = 
reverse('api_geojson_location_list_contained_in_bbox_filter')
  File "/usr/lib/python2.7/dist-packages/django/urls/base.py", line 91, in 
reverse
return force_text(iri_to_uri(resolver._reverse_with_prefix(view, prefix, 
*args, **kwargs)))
  File "/usr/lib/python2.7/dist-packages/django/urls/resolvers.py", line 343, 
in _reverse_with_prefix
possibilities = self.reverse_dict.getlist(lookup_view)
  File "/usr/lib/python2.7/dist-packages/django/urls/resolvers.py", line 240, 
in reverse_dict
return self._reverse_dict[language_code]
KeyError: 'en-gb'

--
Ran 54 tests in 0.011s

FAILED (errors=51, skipped=3)
Creating test database for alias 'default'...
Destroying test database for alias 'default'...
E: pybuild pybuild:274: test: plugin custom failed with: exit code=1: python2.7 
./runtests.py
dh_auto_test: pybuild --test -i python{version} -p 2.7 --system=custom 
--test-args={interpreter} ./runtests.py returned exit code 13
debian/rules:12: recipe for target 'override_dh_auto_test' failed
make[1]: *** [override_dh_auto_test] Error 25
make[1]: Leaving directory '/<>'
debian/rules:9: recipe for target 'build-indep' failed
make: *** [build-indep] Error 2
dpkg-buildpackage: error: debian/rules build-indep gave error exit status 2


Because this source package only generates "Arch: all" packages, this
is the same as a FTBFS bug in the usual sense and the fact that I was
using "dpkg-buildpackage -A" is quite irrelevant.

For this particular package, I've also checked that it fails to build
from source in the reproducible builds site:

https://tests.reproducible-builds.org/

Thanks.

Bug#834667: django-modeltranslation: FTBFS in testing (type object 'TestModel' has no attribute '_deferred')

[Santiago Vila]

Package: src:django-modeltranslation
Version: 0.11-1
Severity: serious

Dear maintainer:

I tried to build this package with "dpkg-buildpackage -A"
(which is what the "Arch: all" autobuilder would do to build it)
but it failed:


[...]
 debian/rules build-indep
dh build-indep --with python2,python3,sphinxdoc --buildsystem=pybuild
   dh_testdir -i -O--buildsystem=pybuild
   dh_update_autotools_config -i -O--buildsystem=pybuild
   dh_auto_configure -i -O--buildsystem=pybuild
I: pybuild base:184: python2.7 setup.py config 
running config
I: pybuild base:184: python3.5 setup.py config 
running config
   debian/rules override_dh_auto_build
make[1]: Entering directory '/<>'
dh_auto_build
I: pybuild base:184: /usr/bin/python setup.py build 

[... snipped ...]

==
ERROR: setUpClass (modeltranslation.tests.tests.ModeltranslationTransactionTest)
--
Traceback (most recent call last):
  File "/<>/modeltranslation/tests/tests.py", line 114, in 
setUpClass
super(ModeltranslationTransactionTestBase, cls).setUpClass()
  File "/usr/lib/python3/dist-packages/django/test/testcases.py", line 172, in 
setUpClass
cls._cls_overridden_context.enable()
  File "/usr/lib/python3/dist-packages/django/test/utils.py", line 235, in 
enable
apps.set_installed_apps(self.options['INSTALLED_APPS'])
  File "/usr/lib/python3/dist-packages/django/apps/registry.py", line 340, in 
set_installed_apps
self.populate(installed)
  File "/usr/lib/python3/dist-packages/django/apps/registry.py", line 115, in 
populate
app_config.ready()
  File "/<>/modeltranslation/apps.py", line 11, in ready
handle_translation_registrations()
  File "/<>/modeltranslation/models.py", line 81, in 
handle_translation_registrations
autodiscover()
  File "/<>/modeltranslation/models.py", line 32, in autodiscover
import_module(module)
  File "/usr/lib/python3.5/importlib/__init__.py", line 126, in import_module
return _bootstrap._gcd_import(name[level:], package, level)
  File "", line 986, in _gcd_import
  File "", line 969, in _find_and_load
  File "", line 958, in _find_and_load_unlocked
  File "", line 673, in _load_unlocked
  File "", line 673, in exec_module
  File "", line 222, in _call_with_frames_removed
  File "/<>/modeltranslation/tests/translation.py", line 18, in 

translator.register(TestModel, TestTranslationOptions)
  File "/<>/modeltranslation/translator.py", line 427, in register
opts = self._get_options_for_model(model, opts_class, **options)
  File "/<>/modeltranslation/translator.py", line 547, in 
_get_options_for_model
if model._deferred:
AttributeError: type object 'TestModel' has no attribute '_deferred'

--
Ran 0 tests in 0.050s

FAILED (errors=22)
 OK
Destroying test database for alias 'default' 
('file:memorydb_default?mode=memory=shared')...
debian/rules:13: recipe for target 'override_dh_auto_test' failed
make[1]: *** [override_dh_auto_test] Error 1
make[1]: Leaving directory '/<>'
debian/rules:6: recipe for target 'build-indep' failed
make: *** [build-indep] Error 2
dpkg-buildpackage: error: debian/rules build-indep gave error exit status 2


Because this source package only generates "Arch: all" packages, this
is the same as a FTBFS bug in the usual sense and the fact that I was
using "dpkg-buildpackage -A" is quite irrelevant.

For this particular package, I've also checked that it fails to build
from source in the reproducible builds site:

https://tests.reproducible-builds.org/

Thanks.

Bug#834666: chkconfig: FTBFS in testing (failing tests)

[Santiago Vila]

Package: src:chkconfig
Version: 11.4.54.60.1debian1
Severity: serious

Dear maintainer:

I tried to build this package with "dpkg-buildpackage -A"
(which is what the "Arch: all" autobuilder would do to build it)
but it failed:


[...]
 debian/rules build-indep
dh build-indep --with quilt
   dh_testdir -i
   dh_update_autotools_config -i
   dh_quilt_patch -i
Applying patch deps-output.diff
patching file chkconfig
Hunk #1 succeeded at 714 (offset 9 lines).

Applying patch rcd-path.diff
patching file chkconfig

Applying patch hyphen-used-as-minus-sign.patch
patching file chkconfig.8

Now at patch hyphen-used-as-minus-sign.patch
   dh_auto_configure -i
   dh_auto_build -i
   debian/rules override_dh_auto_test
make[1]: Entering directory '/<>'
prove
t/add.t  ok
t/check.t: line 8: /sbin/runlevel: No such file or directory
t/check.t .. 
Failed 2/2 subtests 
t/del.t  ok
t/edit.t ... ok
t/list.t ... ok
t/set.t  ok
t/terse.t .. ok

Test Summary Report
---
t/check.t (Wstat: 0 Tests: 2 Failed: 2)
  Failed tests:  1-2
Files=7, Tests=18,  1 wallclock secs ( 0.02 usr  0.00 sys +  0.37 cusr  0.04 
csys =  0.43 CPU)
Result: FAIL
debian/rules:7: recipe for target 'override_dh_auto_test' failed
make[1]: *** [override_dh_auto_test] Error 1
make[1]: Leaving directory '/<>'
debian/rules:4: recipe for target 'build-indep' failed
make: *** [build-indep] Error 2
dpkg-buildpackage: error: debian/rules build-indep gave error exit status 2


Because this source package only generates "Arch: all" packages, this
is the same as a FTBFS bug in the usual sense and the fact that I was
using "dpkg-buildpackage -A" is quite irrelevant.

For this particular package, I've also checked that it fails to build
from source in the reproducible builds site:

https://tests.reproducible-builds.org/

Thanks.

Bug#834668: django-taggit: FTBFS in testing (failing tests)

[Santiago Vila]

Package: src:django-taggit
Version: 0.20.2-1
Severity: serious

Dear maintainer:

I tried to build this package with "dpkg-buildpackage -A"
(which is what the "Arch: all" autobuilder would do to build it)
but it failed:


[...]
 debian/rules build-indep
dh build-indep --fail-missing --with python2,python3 --buildsystem=pybuild
   dh_testdir -i -O--fail-missing -O--buildsystem=pybuild
   dh_update_autotools_config -i -O--fail-missing -O--buildsystem=pybuild
   dh_auto_configure -i -O--fail-missing -O--buildsystem=pybuild
I: pybuild base:184: python2.7 setup.py config 
running config
I: pybuild base:184: python3.5 setup.py config 
running config
   dh_auto_build -i -O--fail-missing -O--buildsystem=pybuild
I: pybuild base:184: /usr/bin/python setup.py build 
running build
running build_py

[... snipped ...]

Name:


>/tests/tests.py", line 156, in test_add_tag
self.assert_tags_equal(self.food_model.tags.all(), ['green'])
  File "/<>/tests/tests.py", line 45, in assert_tags_equal
self.assertEqual(got, tags)
AssertionError: Lists differ: [] != [u'green']

Second list contains 1 additional elements.
First extra element 0:
u'green'

- []
+ [u'green']

==
FAIL: test_prefetch_related (tests.tests.TaggableManagerDirectCustomPKTestCase)
--
Traceback (most recent call last):
  File "/<>/tests/tests.py", line 654, in test_prefetch_related
'apple': set(['1', '2'])
AssertionError: {u'orange': set([]), u'apple': set([])} != {u'orange': 
set([u'2', u'4']), u'apple': set([u'1', u'2'])}
- {u'apple': set([]), u'orange': set([])}
+ {u'apple': set([u'1', u'2']), u'orange': set([u'2', u'4'])}
? ++++


--
Ran 222 tests in 1.410s

FAILED (failures=7, skipped=1)
Creating test database for alias 'default'...
System check identified no issues (0 silenced).
Destroying test database for alias 'default'...
debian/rules:8: recipe for target 'override_dh_auto_test' failed
make[1]: *** [override_dh_auto_test] Error 1
make[1]: Leaving directory '/<>'
debian/rules:5: recipe for target 'build-indep' failed
make: *** [build-indep] Error 2
dpkg-buildpackage: error: debian/rules build-indep gave error exit status 2


Because this source package only generates "Arch: all" packages, this
is the same as a FTBFS bug in the usual sense and the fact that I was
using "dpkg-buildpackage -A" is quite irrelevant.

For this particular package, I've also checked that it fails to build
from source in the reproducible builds site:

https://tests.reproducible-builds.org/

Thanks.

Bug#828169:

[Chris Lamb]

Hi,

> should have ruby-attr-encrypted >= 3.0
>
> bug log shows
>
>  Selecting previously unselected package ruby-attr-encrypted.
>  Preparing to unpack .../ruby-attr-encrypted_1.3.4-1_all.deb ...
>  Unpacking ruby-attr-encrypted (1.3.4-1) ...

Right, except that I was reporting the bug against version 2.0.0-1,
which had ruby-attr-encrypted (>= 1.3.2) in its Build-Depends.


Regards,

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

Bug#834597: kgb-bot: FTBFS in testing

[gregor herrmann]

On Wed, 17 Aug 2016 20:34:04 +0200, gregor herrmann wrote:

> When builing from what we have in git, I get even more errors in the
> test suite:
> 
> #v+
> Test Summary Report
> ---
> t/50-client.t(Wstat: 256 Tests: 31 Failed: 1)
>   Failed test:  31
>   Non-zero exit status: 1
> t/52-client-git.t(Wstat: 65024 Tests: 68 Failed: 0)
>   Non-zero exit status: 254
>   Parse errors: No plan found in TAP output
> t/54-client-git-squash.t (Wstat: 256 Tests: 13 Failed: 1)
>   Failed test:  13
>   Non-zero exit status: 1
> t/55-client-git-merges-ff.t  (Wstat: 256 Tests: 14 Failed: 1)
>   Failed test:  14
>   Non-zero exit status: 1
> t/56-client-git-ff-merge-2.t (Wstat: 256 Tests: 15 Failed: 1)
>   Failed test:  15
>   Non-zero exit status: 1
> t/57-client-git-squash-tags.t (Wstat: 256 Tests: 9 Failed: 1)
>   Failed test:  9
>   Non-zero exit status: 1
> Files=16, Tests=263, 17 wallclock secs ( 0.10 usr  0.01 sys + 13.37 cusr  
> 1.71 csys = 15.19 CPU)
> Result: FAIL
> Failed 6/16 test programs. 5/263 subtests failed.
> #v-

Ok, this is caused by ade2ca5.

If I uncomment two new lines:
#v+
@@ -814,8 +814,8 @@ sub format_message {
 $p{commit_id} = $commit->id if ($commit->id);
 $p{log} = $commit->log if ($commit->log);
 }
-$p{author_name} ||= $p{author_login};
-$p{author_login} ||= $p{author_name};
+#$p{author_name} ||= $p{author_login};
+#$p{author_login} ||= $p{author_name};
 if (defined($self->module)) {
 $p{module} = $self->module;
 } elsif ($commit and defined($commit->module)) {
#v-

we're back to "only" t/52-client-git.t failing.
But that's maybe not what we want? :)
 

t/52-client-git.t works in testing but not in unstable. Maybe the
newer git version?


The test ends with

fatal: независими истории не може да се слеят
merge allnew: command returned error: 128
# stopping test bot, pid 22605
# Removing directory /build/kgb-bot-1.33/t/bot
# Tests were run but no plan was declared and done_testing() was not seen.
t/52-client-git.t ..
[..]
ok 68
Dubious, test returned 254 (wstat 65024, 0xfe00)

In the code we have

   367  TestBot->expect( '#test ^C03Test U. Ser^O (^C03ser^O) ^C05allnew^O '
   368  . $commit->id
   369  . ' ^C12test^O/^C06there^O created empty branch allnew * 
^C14http://scm.host.org/there/allnew/?commit='
   370  . $commit->id
   371  . '^O' );
   372
   373  # No more commits after the last
   374  $commit = $c->describe_commit;
   375  is( $commit, undef );
   376
   377  # now the same on the master branch
   378  $git->command( [ 'checkout', '-q', 'master' ], { STDERR => 0 } );
   379  $git->command( 'merge', 'allnew' );
   380  push_ok();
   381  $c2 = $commit = $c->describe_commit;
   382  ok( defined($commit), 'empty branch merge commit exists' );

Test 68 which passes is line 375, and the next test at 382 is not
reached. According to the error above, the problem happens in 379.

The "fatal" line in English:
fatal: refusing to merge unrelated histories


This looks interesting: /usr/share/doc/git/RelNotes/2.9.0.txt
  Merging two branches that have no common ancestor with "git merge" is
  by default forbidden now to prevent creating such an unusual merge by
  mistake.

 * "git merge" used to allow merging two branches that have no common
   base by default, which led to a brand new history of an existing
   project created and then get pulled by an unsuspecting maintainer,
   which allowed an unnecessary parallel history merged into the
   existing project.  The command has been taught not to allow this by
   default, with an escape hatch "--allow-unrelated-histories" option
   to be used in a rare event that merges histories of two projects
   that started their lives independently.


And from git-merge(1):
   --allow-unrelated-histories
   By default, git merge command refuses to merge histories that do not 
share a common ancestor. This option
   can be used to override this safety when merging histories of two 
projects that started their lives
   independently. As that is a very rare occasion, no configuration 
variable to enable this by default exists
   and will not be added.


A quick hotfix would be:

#v+
--- a/t/52-client-git.t
+++ b/t/52-client-git.t
@@ -376,7 +376,13 @@ is( $commit, undef );

 # now the same on the master branch
 $git->command( [ 'checkout', '-q', 'master' ], { STDERR => 0 } );
-$git->command( 'merge', 'allnew' );
+my $gitversion = Git::command_oneline('version');
+$gitversion =~ s/^git version\s*//;
+if ( $gitversion ge '2.9.0' ) {
+$git->command( 'merge', 'allnew', '--allow-unrelated-histories' );
+} else {
+$git->command( 'merge', 'allnew' );
+}
 push_ok();
 $c2 = $commit = $c->describe_commit;
 ok( defined($commit), 'empty branch merge commit exists' );
#v-


With this change the test passes in sid and stretch (ignoring the
fact that this version extraction and comparison attempt is 

Processed: tagging 834597

[Debian Bug Tracking System]

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

> tags 834597 + stretch sid
Bug #834597 [src:kgb-bot] kgb-bot: FTBFS in testing
Added tag(s) stretch and sid.
> thanks
Stopping processing here.

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

Processed: Re: Bug#834557: apt-listbugs: invalid byte sequence in US-ASCII (ArgumentError)

[Debian Bug Tracking System]

Processing control commands:

> severity -1 normal
Bug #834557 [apt-listbugs] apt-listbugs: invalid byte sequence in US-ASCII 
(ArgumentError)
Severity set to 'normal' from 'critical'
> tags -1 + moreinfo
Bug #834557 [apt-listbugs] apt-listbugs: invalid byte sequence in US-ASCII 
(ArgumentError)
Added tag(s) moreinfo.

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

Bug#834557: apt-listbugs: invalid byte sequence in US-ASCII (ArgumentError)

[Francesco Poli]

Control: severity -1 normal
Control: tags -1 + moreinfo


On Wed, 17 Aug 2016 05:47:26 +0200 Christoph Anton Mitterer wrote:

> Purging and reinstalling it seems to have fixed the issue... also I
> haven't had seen this on all my systems...

Hello Christoph,
thanks for your bug report!

It seems to me that you had some strange character
in /var/lib/apt-listbugs/ignore_bugs ...
Purging and reinstalling should have removed that file.

Do you still have a copy of that file (as it was before purging
apt-listbugs, I mean), by chance?
It would be useful to understand what went wrong...

> 
> I'll leave the issue open, perhaps you can find some issue in the code.

Maybe, or maybe not.
I suspect that the explanation is in the above-mentioned file, assuming
you still have a copy around...

Please let me know.
Thanks for your cooperation!


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


pgpdhOZF2X8_y.pgp
Description: PGP signature

Processed: severity of 834455 is serious

[Debian Bug Tracking System]

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

> severity 834455 serious
Bug #834455 [gnome-terminal] gnome-terminal: Window height decreases by 1 line 
with each typed character if multiple tabs are opened
Severity set to 'serious' from 'important'
> thanks
Stopping processing here.

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

Bug#832994: [debian-mysql] Bug#832994: libmariadbclient-dev-compat: fails to upgrade from 'testing' - trying to overwrite /usr/lib/x86_64-linux-gnu/libmysqlclient.so (from libmariadb-client-lgpl-dev-c

[Otto Kekäläinen]

Correct link format:
https://anonscm.debian.org/cgit/pkg-mysql/mariadb-10.0.git/commit/?id=4c9104d2b40df4b8619b0a81cd346719d242a334

Uploaded in 10.0.26-3. Closing issue.

Processed: your mail

[Debian Bug Tracking System]

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

> close 832994
Bug #832994 [libmariadbclient-dev-compat] libmariadbclient-dev-compat: fails to 
upgrade from 'testing' - trying to overwrite 
/usr/lib/x86_64-linux-gnu/libmysqlclient.so (from 
libmariadb-client-lgpl-dev-compat)
Marked Bug as done
>
End of message, stopping processing here.

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

Bug#834654: no upstream releases; severe bugs open

[Jelmer Vernooij]

Source: heimdal
Severity: serious

There have been no upstream releases of Heimdal in over 4 years and there is no 
current
release management or QA upstream. After 1.6RC2, prior to which releases were
fairly frequent (every month or so), no new releases have happened.

The last full feature release was 1.5 (September 2011). 

Debian has packaged snapshots of Heimdal for a while, mostly because Samba
(which bundles Heimdal) uses it, and it needs specific features to be
compatible with AD. However, Samba turned out too be too closely coupled
to a specific Heimdal version; using a different Heimdal snapshot than what
upstream Samba was using caused subtle bugs, in part because the extensive
QA that happened upstream didn't happen in Debian. Since then, the Samba
package has changed to use the bundled Heimdal. 
See also 
https://lists.alioth.debian.org/pipermail/pkg-samba-maint/2015-April/017277.html

Upstream Heimdal is still somewhat active; most contributors just seem
to run Git snapshots in their own environments. There is a long open bug
in master that makes Heimdal unusable on 32 bit platforms (#822749) and
at the moment of writing, ./configure doesn't run in master on Debian unstable.

At this point it seems very unlikely that upstream will release a 1.7 before
Debians next soft freeze. As maintainers, we don't want to package a 4 year old
Heimdal 1.5 or have Debian support a git snapshot for the next couple of years.

-- 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/2 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)

Bug#825727: python-babel: FTBFS: assert 'GMT+00:00' == 'GMT-01:59'

[Chris Lamb]

Santiago Vila wrote:

> > http://sources.debian.net/src/tzdata/2016f-1/debian/tzdata.postinst/#L30-L31
> 
> Ah, I checked in my laptop (jessie) and just assumed that it would be
> the same in stretch.

Ah, it indeed changed!


│   │   ├── debian/tzdata.postinst
│   │   │ @@ -23,15 +23,15 @@
│   │   │  ZONE=UTC
│   │   │  db_get tzdata/Areas && AREA="$RET"
│   │   │  db_get tzdata/Zones/$AREA && ZONE="$RET"
│   │   │  db_stop
│   │   │  
│   │   │  # Update the time zone
│   │   │  echo $AREA/$ZONE > /etc/timezone
│   │   │ - cp -f /usr/share/zoneinfo/$AREA/$ZONE /etc/localtime.dpkg-new 
&& \
│   │   │ + ln -nsf /usr/share/zoneinfo/$AREA/$ZONE /etc/localtime.dpkg-new 
&& \
│   │   │   mv -f /etc/localtime.dpkg-new /etc/localtime
│   │   │   which restorecon >/dev/null 2>&1 && restorecon /etc/localtime
│   │   │  
│   │   │  echo 
│   │   │  echo "Current default time zone: '$AREA/$ZONE'"
│   │   │  fi
│   │   │  

(This is unrelated to this bug I guess.)


Regards,

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

Bug#825727: python-babel: FTBFS: assert 'GMT+00:00' == 'GMT-01:59'

[Santiago Vila]

On Wed, Aug 17, 2016 at 08:29:38PM +0100, Chris Lamb wrote:
> > /etc/localtime -> /usr/share/zoneinfo/Europe/Madrid
> > 
> > I know this is not exactly what "dpkg-reconfigure tzdata" does
> 
> Really?
> 
> http://sources.debian.net/src/tzdata/2016f-1/debian/tzdata.postinst/#L30-L31

Ah, I checked in my laptop (jessie) and just assumed that it would be
the same in stretch.

So, being that the natural thing in stretch, I'm out of ideas.

Thanks.

Bug#825727: python-babel: FTBFS: assert 'GMT+00:00' == 'GMT-01:59'

[Chris Lamb]

> /etc/localtime -> /usr/share/zoneinfo/Europe/Madrid
> 
> I know this is not exactly what "dpkg-reconfigure tzdata" does

Really?

http://sources.debian.net/src/tzdata/2016f-1/debian/tzdata.postinst/#L30-L31


Regards,

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

Bug#811184: marked as done (Phatch not loading Debian Stretch)

[Debian Bug Tracking System]

Your message dated Wed, 17 Aug 2016 19:28:53 +
with message-id 
and subject line Bug#811184: fixed in phatch 0.2.7.1-4
has caused the Debian Bug report #811184,
regarding Phatch not loading Debian Stretch
to be marked as done.

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

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


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

Package: phatch
Version: 0.2.7.1-3.1
Severity: serious
Justification: renders package unusable

Dear Maintainer,
 
On Clean install of 'Stretch'


Problem:  'Phatch' fails to load displaying only the 'Phatch'
icon in centre of screen.





Repeatable: Yes, same problem on laptop running 'Stretch'




Tried from Command line,  same, output below.




/usr/lib/python2.7/dist-packages/wx-3.0-gtk2/wx/_core.py:8196:
GtkWarning: gtk_disable_setlocale() must be called before gtk_init()

return _core_.PyApp__BootstrapApp(*args, **kwargs)

Traceback (most recent call last):

File "/usr/lib/python2.7/dist-packages/wx-3.0-gtk2/wx/_core.py",
line 16765, in 

lambda event: event.callable(*event.args, **event.kw) )

File "/usr/share/phatch/phatch/pyWx/gui.py", line 1218, in
show_frame

frame = Frame(self.filename, None, -1, ct.TITLE)

File "/usr/share/phatch/phatch/pyWx/gui.py", line 327, in __init__

frame.Frame.__init__(self, *args, **keyw)

File "/usr/share/phatch/phatch/pyWx/wxGlade/frame.py", line 141, in
__init__

self.tree = Tree(self, -1,
style=wx.TR_HAS_BUTTONS|wx.TR_NO_LINES|wx.TR_FULL_ROW_HIGHLIGHT|wx.TR_HIDE_ROOT|wx.TR_DEFAULT_STYLE|wx.SUNKEN_BORDER)

File "/usr/share/phatch/phatch/pyWx/wxGlade/frame.py", line 26, in
__init__

set_dirty = parent.set_dirty,

File "/usr/share/phatch/phatch/lib/pyWx/treeEdit.py", line 96, in
__init__

self.CreateImageList(icon_size)

File "/usr/share/phatch/phatch/lib/pyWx/treeEdit.py", line 111, in
CreateImageList

self._AddFormToImageList(form, icon_size, icon_disabled)

File "/usr/share/phatch/phatch/lib/pyWx/treeEdit.py", line 120, in
_AddFormToImageList

wx_image = pil_wxImage(wxImage_pil(wx_image).resize(icon_size,\

File "/usr/share/phatch/phatch/lib/pyWx/wxPil.py", line 46, in
wxImage_pil

image.fromstring(wx_image.GetData())

File "/usr/lib/python2.7/dist-packages/PIL/Image.py", line 737, in 
fromstring "Please call frombytes() instead.") Exception: fromstring() 
has been removed. Please call frombytes() instead.







Posted on Debian > 'General Questions' Forum advised by
Stevepusser "try editing line 737 in that file, replacing fromstring
with frombytes"




This failed replacing text red above with:




File "/usr/lib/python2.7/dist-packages/PIL/Image.py", line 626, in
__getattr__

raise AttributeError(name)

AttributeError: fromstring




Advised to post Bug report.  Apologies if this report is not in the
correct format but this is my first.




Regards

John




-
www.scotlandsartists.com - A directory of Scotland's Visual Artists
Prints for sale from a selection of artists on website
Original Art
Giclée printing up to A1
Print mounting
Art Cards in various sizes
Artwork Photography
Websites
Find us on Facebook 


Follow us on Twitter 
--- End Message ---
--- Begin Message ---
Source: phatch
Source-Version: 0.2.7.1-4

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

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

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

Debian distribution maintenance software
pp.
Piotr Ożarowski  (supplier of updated phatch package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Wed, 17 Aug 2016 20:44:12 +0200
Source: phatch
Binary: phatch phatch-cli phatch-doc
Architecture: source all
Version: 0.2.7.1-4
Distribution: unstable
Urgency: medium
Maintainer: Python Applications Packaging Team 

Bug#821734: libvotca-csg3: fails to upgrade from 'jessie' - trying to overwrite /usr/share/man/man7/votca-csg.7.gz

[Nicholas Breen]

Unless someone else is already on it, I'll take care of this within the week,
and that'll handle the necessary rebuild for the libgromacs1 -> libgromacs2
SONAME bump at the same time.



-- 
Nicholas Breen
nbr...@debian.org

Processed: affects 834616

[Debian Bug Tracking System]

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

> affects 834616 src:thuban
Bug #834616 [tex4ht] tex4ht is uninstallable in sid: depends on experimental 
texlive-htmlxml
Added indication that 834616 affects src:thuban
> thanks
Stopping processing here.

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

Bug#830419: marked as done (debomatic: FTBFS: ! LaTeX Error: File `iftex.sty' not found.)

[Debian Bug Tracking System]

Your message dated Wed, 17 Aug 2016 18:53:01 +
with message-id 
and subject line Bug#830419: fixed in debomatic 0.21-2
has caused the Debian Bug report #830419,
regarding debomatic: FTBFS: ! LaTeX Error: File `iftex.sty' not found.
to be marked as done.

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

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


-- 
830419: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=830419
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: debomatic
Version: 0.21-1
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):
> make[3]: Entering directory '/«PKGBUILDDIR»/docs/_build/latex'
> pdflatex  'Deb-o-Matic.tex'
> This is pdfTeX, Version 3.14159265-2.6-1.40.17 (TeX Live 2016/Debian) 
> (preloaded format=pdflatex)
>  restricted \write18 enabled.
> entering extended mode
> (./Deb-o-Matic.tex
> LaTeX2e <2016/03/31> patch level 1
> Babel <3.9r> and hyphenation patterns for 3 language(s) loaded.
> (./sphinxmanual.cls
> Document Class: sphinxmanual 2009/06/02 Document class (Sphinx manual)
> (/usr/share/texlive/texmf-dist/tex/latex/base/report.cls
> Document Class: report 2014/09/29 v1.4h Standard LaTeX document class
> (/usr/share/texlive/texmf-dist/tex/latex/base/size10.clo)))
> 
> ! LaTeX Error: File `iftex.sty' not found.
> 
> Type X to quit or  to proceed,
> or enter new name. (Default extension: sty)
> 
> Enter file name: 
> ! Emergency stop.
>  
>  
> l.5 ^^M
>
> !  ==> Fatal error occurred, no output PDF file produced!
> Transcript written on Deb-o-Matic.log.
> make[3]: *** [Deb-o-Matic.pdf] Error 1

The full build log is available from:
   
http://people.debian.org/~lucas/logs/2016/07/07/debomatic_0.21-1_unstable_reb.normal.log

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: debomatic
Source-Version: 0.21-2

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

Debian distribution maintenance software
pp.
Luca Falavigna  (supplier of updated debomatic 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, 17 Aug 2016 19:46:27 +0200
Source: debomatic
Binary: debomatic
Architecture: source
Version: 0.21-2
Distribution: unstable
Urgency: medium
Maintainer: Luca Falavigna 
Changed-By: Luca Falavigna 
Description:
 debomatic  - automatic build machine for Debian source packages
Closes: 830419
Changes:
 debomatic (0.21-2) unstable; urgency=medium
 .
   * debian/control:
 - Add texlive-generic-extra to Build-Depends, fix FTBFS.
   Thanks to Andrea Claudi for the suggestion! (Closes: #830419).
 - Bump Standards-Version to 3.9.8.
 - Use secure VCS URI's.
Checksums-Sha1:
 6d817e1c25725e2630f98b3504f084a2597d1e6c 2101 debomatic_0.21-2.dsc
 f628d6274f47616024693a0e630667e5bd908d29 5640 debomatic_0.21-2.debian.tar.xz
Checksums-Sha256:
 786d29627b77437624f412eeed101370eca084dd0355f9facb9e46c4878ec1a1 2101 
debomatic_0.21-2.dsc
 f2d7e952cf72ae9d5a43a3e1daa8a9eb7788da9872cd06cd8acf3bac2d522151 5640 
debomatic_0.21-2.debian.tar.xz
Files:
 e73bd565039a64c3b77b6c8c51bc3941 2101 devel extra debomatic_0.21-2.dsc
 d8c2fae94888d6d5061d996a07e73c5c 5640 devel extra 
debomatic_0.21-2.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQIcBAEBCAAGBQJXtKS9AAoJEEkIatPr4vMfsdAP/RVvctmN9NinwU7YW8b9R9bI
CjybJ67eRaQ05EiCyU568pcG77zPP06gLvYMdFLY+o0z9fhD2+KUdAKQ+nj5uIce
UPWUU+aldlDiIUWaFHxgPu3FfLQQPsGoZQmj2K5qoq6qAOcX2M3zVCJsk9FrMXoQ
pil+qvjMHsVAOcmoWSp5NJledrWox4dbP/YQdXjB/SfTgElOPu6Qdj1+sFbTP4XU

Bug#834640: ncl: FTBFS (sed: -e expression #5, char 39: unknown option to `s')

[Bas Couwenberg]

Source: ncl
Version: 6.3.0-9
Severity: serious
Tags: patch
Justification: makes the package in question unusable or mostly so

Dear Maintainer,

In preparation of the upcoming transition to PROJ.4 4.9.3 ncl has been
rebuilt, but unfortunately it FTBFS due to changes in FFLAGS:

 sed -e 's/@CC@/cc/' \
 -e 's/@FC@/gfortran/' \
 -e 's/@LD@/cc/' \
 -e 's:@CFLAGS@:-g -O2 -fdebug-prefix-map=/build/ncl-6.3.0=. 
-fstack-protector-strong -Wformat -Werror=format-security 
-I/usr/include/hdf5/serial:' \
 -e 's/@FFLAGS@/-g -O2 -fdebug-prefix-map=/build/ncl-6.3.0=. 
-fstack-protector-strong/' \
 -e 's/@CPPFLAGS@/-Wdate-time -D_FORTIFY_SOURCE=2/' \
 -e 's/@LDFLAGS@//' \
 -e 's%@DESTDIR@%/build/ncl-6.3.0/debian/tmp/%' \
 < debian/Site.local.shared.in > config/Site.local.shared
 sed: -e expression #5, char 39: unknown option to `s'
 debian/rules:47: recipe for target 'override_dh_auto_configure' failed

The attached patch fixes the issue by using the colon in the sed
expression like CFLAGS.

Kind Regards,

Bas
--- a/debian/rules
+++ b/debian/rules
@@ -52,7 +52,7 @@
-e 's/@FC@/${FC}/' \
-e 's/@LD@/${CC}/' \
-e 's:@CFLAGS@:${CFLAGS}:' \
-   -e 's/@FFLAGS@/${FFLAGS}/' \
+   -e 's:@FFLAGS@:${FFLAGS}:' \
-e 's/@CPPFLAGS@/${CPPFLAGS}/' \
-e 's/@LDFLAGS@/${LDFLAGS}/' \
-e 's%@DESTDIR@%${DESTDIR}%' \
@@ -61,7 +61,7 @@
-e 's/@FC@/${FC}/' \
-e 's/@LD@/${CC}/' \
-e 's:@CFLAGS@:${CFLAGS}:' \
-   -e 's/@FFLAGS@/${FFLAGS}/' \
+   -e 's:@FFLAGS@:${FFLAGS}:' \
-e 's/@CPPFLAGS@/${CPPFLAGS}/' \
-e 's/@LDFLAGS@/${LDFLAGS}/' \
-e 's%@DESTDIR@%${DESTDIR}%' \

Processed: Re: Bug#834597: kgb-bot: FTBFS in testing

[Debian Bug Tracking System]

Processing control commands:

> tag -1 + confirmed pending
Bug #834597 [src:kgb-bot] kgb-bot: FTBFS in testing
Added tag(s) pending and confirmed.

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

Processed: tagging 834600

[Debian Bug Tracking System]

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

> tags 834600 - moreinfo + pending
Bug #834600 [src:python-gnupg] python-gnupg: FTBFS: Missing build-depends on 
gnupg
Removed tag(s) moreinfo.
Bug #834600 [src:python-gnupg] python-gnupg: FTBFS: Missing build-depends on 
gnupg
Added tag(s) pending.
> thanks
Stopping processing here.

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

Bug#834597: kgb-bot: FTBFS in testing

[gregor herrmann]

Control: tag -1 + confirmed pending

On Wed, 17 Aug 2016 13:38:25 +, Santiago Vila wrote:

> I tried to build this package with "dpkg-buildpackage -A"
> (which is what the "Arch: all" autobuilder would do to build it)
> but it failed:
> 
> 
> [...]
>  debian/rules build-indep
> dh build-indep
>dh_testdir -i
>dh_update_autotools_config -i
>dh_auto_configure -i
>   perl Build.PL --installdirs vendor
> Base class package "Module::Build" is empty.
> (Perhaps you need to 'use' the module which defines that package first,
> or make that module available in @INC (@INC contains: privinc /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 privinc/My/Builder.pm line 6.
> BEGIN failed--compilation aborted at privinc/My/Builder.pm line 6.
> Compilation failed in require at Build.PL line 5.
> BEGIN failed--compilation aborted at Build.PL line 5.
> dh_auto_configure: perl Build.PL --installdirs vendor returned exit code 255
> debian/rules:4: recipe for target 'build-indep' failed
> make: *** [build-indep] Error 2
> dpkg-buildpackage: error: debian/rules build-indep gave error exit status 2
> 

This is already fixed in git [0].

If I "backport" only this change to the 1.33-2 it gets past
dh_auto_configure, but then one test fails:

#v+
# prove --blib --verbose t/52-client-git.t
t/52-client-git.t .. # trying port 5392
# test bot listening on 127.0.0.1:5392, pid: 2228  at t/TestBot.pm line 116.

Initialized empty Git repository in /tmp/kgb-WSQmwxU/there.git/
Initialized empty Git repository in /tmp/kgb-WSQmwxU/here/.git/
ok 1 - local repository allocated
ok 2 - An object of class 'Git' isa 'Git'
ok 3 - An object of class 'App::KGB::Client::Git' isa 'App::KGB::Client::Git'
ok 4 - post-receive hook logs
ok 5 - commit 1 present
ok 6
ok 7
ok 8
ok 9
ok 10
ok 11
ok 12 - commit 2 present
ok 13
ok 14
ok 15
ok 16
ok 17
ok 18
ok 19
ok 20 - commit 3 present
ok 21 - commit 3 branch is "master"
ok 22
ok 23
ok 24
ok 25
ok 26
ok 27 - commit 4 present
ok 28
ok 29
ok 30
ok 31
ok 32
ok 33
ok 34
ok 35 - commit 5 present
ok 36 - commit 5 id
ok 37 - commit 5 branch
ok 38 - commit 5 log
ok 39 - commit 5 author
ok 40 - commit 5 changes
ok 41 - commit 6 present
ok 42
ok 43
ok 44
ok 45
ok 46
ok 47
ok 48 - annotated tag here
ok 49
ok 50
ok 51
ok 52
ok 53 - annotated tag log
ok 54 - hollow branch described
ok 55 - hollow commit is cf87bf3
ok 56 - hollow commit branch is 'hollow'
ok 57 - no changes in hollow commit
ok 58 - hollow commit log is 'branch created'
ok 59 - hollow branch has no commits
ok 60 - UTF-8 commit exists
ok 61
ok 62
ok 63
ok 64
ok 65 - empty branch creation commit exists
ok 66 - empty branch name
ok 67 - empty branch log
ok 68
fatal: refusing to merge unrelated histories
merge allnew: command returned error: 128
# stopping test bot, pid 2228
# Removing directory /build/kgb-bot-1.33/t/bot
# Tests were run but no plan was declared and done_testing() was not seen.
Dubious, test returned 254 (wstat 65024, 0xfe00)
All 68 subtests passed 

Test Summary Report
---
t/52-client-git.t (Wstat: 65024 Tests: 68 Failed: 0)
  Non-zero exit status: 254
  Parse errors: No plan found in TAP output
Files=1, Tests=68,  4 wallclock secs ( 0.03 usr  0.01 sys +  2.95 cusr  0.36 
csys =  3.35 CPU)
Result: FAIL
#v-

When builing from what we have in git, I get even more errors in the
test suite:

#v+
Test Summary Report
---
t/50-client.t(Wstat: 256 Tests: 31 Failed: 1)
  Failed test:  31
  Non-zero exit status: 1
t/52-client-git.t(Wstat: 65024 Tests: 68 Failed: 0)
  Non-zero exit status: 254
  Parse errors: No plan found in TAP output
t/54-client-git-squash.t (Wstat: 256 Tests: 13 Failed: 1)
  Failed test:  13
  Non-zero exit status: 1
t/55-client-git-merges-ff.t  (Wstat: 256 Tests: 14 Failed: 1)
  Failed test:  14
  Non-zero exit status: 1
t/56-client-git-ff-merge-2.t (Wstat: 256 Tests: 15 Failed: 1)
  Failed test:  15
  Non-zero exit status: 1
t/57-client-git-squash-tags.t (Wstat: 256 Tests: 9 Failed: 1)
  Failed test:  9
  Non-zero exit status: 1
Files=16, Tests=263, 17 wallclock secs ( 0.10 usr  0.01 sys + 13.37 cusr  1.71 
csys = 15.19 CPU)
Result: FAIL
Failed 6/16 test programs. 5/263 subtests failed.
#v-


Not nice.


Hm, might be related to:

#v+
-( my $full_name = $user->gecos ) =~ s/,.*//;
+my $full_name = $login;
+( $full_name = $user->gecos ) =~ s/,.*// if defined $user;
#v-

since most errors look like:

#v+
#   Failed test at t/57-client-git-squash-tags.t line 197.
# --- Got
# +++ Expected
# @@ -1,3 +1,3 @@
#  '#test ^C03Test U. Ser^O (^C03ser^O) ^C05master^O 

Bug#834600: python-gnupg: FTBFS: Missing build-depends on gnupg

[Elena ``of Valhalla'']

Ah! stretch! that's why you weren't seeing the same FTBFS I was working
on (which is caused by the new gnupg, and thus right now only in sid).

I've investigated a bit on the issue, and found that gnupg is indeed
installed when installing build-essential, but only as a Recommends, and
thus it won't be installed on the autobuilders.

This made me learn that I should really recreate my (p|cow)builder
images now and then: I still had gnupg installed by default in the base
image for historical reasons and it hadn't been autoremoved because of
that Recommends.

Anyway, the pending upload that I've prepared for the other FTBFS had to
add an explicit dependency on gnupg1, which should fix also this issue;
I won't remove it when I'll be able to go back on depending on gnupg.

Thanks again for your report.
-- 
Elena ``of Valhalla''

Bug#825727: python-babel: FTBFS: assert 'GMT+00:00' == 'GMT-01:59'

[Santiago Vila]

On Wed, Aug 17, 2016 at 06:42:19PM +0100, Chris Lamb wrote:
> Santiago Vila wrote:
> 
> > > I'm afaid I still cannot reproduce it. Downgrading until somebody else 
> > > can.
> > 
> > Well, I can. Not exactly the same error, but for now I will assume
> > there is a common reason for them.
> 
> Looking at this again "my" error appears to be caused by the fact that my
> /etc/timezone and /etc/localtime are read-only at the filesystem level as
> I inherit them from outside my container:
> 
> --volume=/etc/adjtime:/etc/adjtime:ro
> --volume=/etc/timezone:/etc/timezone:ro
> --volume=/etc/localtime:/etc/localtime:ro
> 
> When I turn that off, I can build fine. I find this strange, as I don't
> actually build as root within this container so it couldn't write to it
> even if it wanted.
> 
> Any ideas?

My files are not read-only, but the /etc/localtime in my chroots,
instead of being a copy of the binary file in /usr/share/zoneinfo, is
just a symlink:

/etc/localtime -> /usr/share/zoneinfo/Europe/Madrid

I know this is not exactly what "dpkg-reconfigure tzdata" does,
but I think it should be supported.

Thanks.

Processed: Re: Bug#818862: Similar issues with kernel 4.6 and 4.7

[Debian Bug Tracking System]

Processing control commands:

> severity 818862 important
Bug #818862 [nvidia-kernel-dkms] [nvidia-kernel-dkms] fails to build for 
custom-compiled 4.4.6 kernel
Severity set to 'important' from 'grave'

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

Bug#818862: Similar issues with kernel 4.6 and 4.7

[Eduard Bloch]

Control: severity 818862 important

Hallo,
* Luca Boccassi [Tue, Aug 16 2016, 09:48:40PM]:
> On Tue, 2016-08-16 at 20:02 +0200, Eduard Bloch wrote:
> > Package: nvidia-kernel-source
> > Version: 367.35-1
> > Followup-For: Bug #818862
> > Control: severity 818862 grave
> > 
> > Hello,
> > 
> > I have no idea how you manage to build the current modules even for Sid.
> > For me, it fails, always with the same symptoms. It fails with Sid
> > version of nvidia-kernel-source, it fails with the Experimental version
> > of the package, it fails with the SVN version which I built using the
> > instructions from the Wiki. It fails with my kernel 4.7 (locally
> > compiled) and also when I try to build against the official Sid kernel
> > headers.
> > 
> > So, how is it supposed to work? Is the source not ready for gcc 6? Is it
> > doing some broken checks that depend on running kernel rather than the
> > target kernel?
> > 
> > I briefly tried to investigate in the source but it's a huge mess, IMHO.
> 
> Have you read the supplied readme
> file, /usr/share/doc/nvidia-kernel-source/README.Debian.gz ?
> As the readme suggests, it's recommended to use module-assistant.

I am the original author of module-assistant, thanks.

> EG:
> 
> module-assistant build --text-mode --force --kvers-list 4.7.0-rc7-amd64 
> nvidia-kernel

a) minor detail, the readme does not mention --force, although it should not be 
required.

b) For 4.7.0-rc7-amd64 it seems to compile, indeed; that is the FIRST "success"
I have seen in the last couple of days. However, 4.7.0-rc7-amd64 is from
Experimental.

c) I tried a similar command with 4.6.0-1-amd64 (Sid kernel) and it did NOT 
work. Now
after the previous build succeeded, I tried again, failure. Tried for
4.7.0+ (the active kernel) again, failure. Tried again for
4.6.0-1-amd64, seems to compile now. Not sure what's going on here, I
have not upgraded unrelated packages. Log file attached, maybe this helps.

d) it is still not building for my custom kernels build from vanilla
source. But this is basically the same configuration I used last year
and the driver was compiling fine back then. Are there any new special
requirements? Config attached.

Regards,
Eduard.


nvidia-kernel-source.buildlog.4.6.0-1-amd64.1471370049.gz
Description: application/gzip


config-4.7.0+.gz
Description: application/gzip

Bug#784845: libdevel-gdb-perl: autopkgtest failure in t/expect.t

[gregor herrmann]

On Tue, 16 Aug 2016 23:33:09 +0100, Santiago Vila wrote:

> > Sorry, I don't understand the connection to building with -A. Is
> > there a report about the package failing with it? Does it fail for
> > you if you build with -A?
> I only build with -A, but there are a lot of packages for which a
> failed build with -A and a failed build without -A are essentially the
> same thing.

Ok, thanks for the explanation.
 
> > So you got a failing build? [...]
> Yes, so far I got a failed build and three successful builds.
> I attach the failed build.

Thanks!
 
> > (And on the reproducible builds it works roughly half of the time:
> > https://tests.reproducible-builds.org/debian/history/libdevel-gdb-perl.html
> > )
> That's more or less my point: For a package which is "Arch: all" like
> this one, a success rate of only 50% is bad enough not to be RC.

Agreed -- in general; my point is that this 50% failure rate only
occurs on the reproducible build setup and not on ci.debian.net or my
machine (or anybody else's who tried to hunt this this annoying bug).


Cheers,
gregor

-- 
 .''`.  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: Dawn Landes: Tired Of This Life


signature.asc
Description: Digital Signature

Bug#825727: python-babel: FTBFS: assert 'GMT+00:00' == 'GMT-01:59'

[Chris Lamb]

Santiago Vila wrote:

> > I'm afaid I still cannot reproduce it. Downgrading until somebody else can.
> 
> Well, I can. Not exactly the same error, but for now I will assume
> there is a common reason for them.

Looking at this again "my" error appears to be caused by the fact that my
/etc/timezone and /etc/localtime are read-only at the filesystem level as
I inherit them from outside my container:

--volume=/etc/adjtime:/etc/adjtime:ro
--volume=/etc/timezone:/etc/timezone:ro
--volume=/etc/localtime:/etc/localtime:ro

When I turn that off, I can build fine. I find this strange, as I don't
actually build as root within this container so it couldn't write to it
even if it wanted.

Any ideas?


Regards,

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

Processed: mako: FTBFS

[Debian Bug Tracking System]

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

> unmerge 830178
Bug #830178 {Done: Piotr Ożarowski } [zzzeeksphinx] mako: 
FTBFS: ValueError: too many values to unpack
Bug #829020 {Done: Piotr Ożarowski } [zzzeeksphinx] 
sqlalchemy: FTBFS in testing (too many values to unpack)
Disconnected #830178 from all other report(s).
> reassign 830178 src:mako
Bug #830178 {Done: Piotr Ożarowski } [zzzeeksphinx] mako: 
FTBFS: ValueError: too many values to unpack
Bug reassigned from package 'zzzeeksphinx' to 'src:mako'.
No longer marked as found in versions 1.0.18-1.
No longer marked as fixed in versions zzzeeksphinx/1.0.18-2.
> found 830178 1.0.4+ds1-1
Bug #830178 {Done: Piotr Ożarowski } [src:mako] mako: FTBFS: 
ValueError: too many values to unpack
Marked as found in versions mako/1.0.4+ds1-1 and reopened.
> thanks
Stopping processing here.

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

Bug#830178: mako: FTBFS

[Santiago Vila]

unmerge 830178
reassign 830178 src:mako
found 830178 1.0.4+ds1-1
thanks

On Sun, 31 Jul 2016, Piotr Ożarowski wrote:

> reassign 829020 zzzeeksphinx 1.0.18-1
> reassign 830178 zzzeeksphinx 1.0.18-1
> merge 829020 830178

Hello Piotr.

The version of zzzeeksphinx which was supposed to fix this (1.0.18-2)
already propagated to testing, but mako still FTBFS:

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

So I infer (but I may be wrong) that this was not the fault of
zzzeeksphinx after all.

Thanks.

Processed: grib-api: Incorrect library path in CMake module (/usr/lib/lib/libgrib_api.so.0)

[Debian Bug Tracking System]

Processing control commands:

> affects -1 magics++ metview
Bug #834634 [src:grib-api] grib-api: Incorrect library path in CMake module 
(/usr/lib/lib/libgrib_api.so.0)
Added indication that 834634 affects magics++ and metview

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

Bug#784619: [creepy] Qt4's WebKit removal

[Dmitry Shachnev]

Hi Petter,

On Sun, Aug 07, 2016 at 12:47:57PM +0200, Petter Reinholdtsen wrote:
> Control: tags -1 + help
>
> We belive we will need help with porting creepy to Qt5.
>
> I got a tip on #debian-gis that
> https://github.com/qgis/QGIS/blob/master/scripts/2to3 > might
> help.  It is a script to migrate python code from Qt4 to Qt5.

No, that is a script to port from Python 2 to Python 3. This is also a
good thing to do, but has nothing to do with Qt.

The biggest difference between PyQt4 and PyQt5 is that the latter only
supports the new-style connect syntax. Fortunately creepy seems to be
already using it, so your work is much less than it could be.

The three main steps then are:

1) There are Python files in creepy/ui/ directory which are generated
   from .ui files using pyuic4. You need to regenerate them using pyuic5
   (available in pyqt5-dev-tools package).

2) There is creepy/components/creepy_resources_compiled.py file which is
   generated from creepy/include/creepy_resources.qrc file using pyrcc4.
   You need to regenerate it using pyrcc5 (the same package).

3) In the remaining files, replace PyQt4 imports with PyQt5. Note that
   the widgets are no longer in QtGui module, but in a separate QtWidgets
   module.

   So you need to do some imports replacing i.e.:

   from PyQt4.QtGui import QWizard →
   from PyQt5.QtWidgets import QWizard

   from PyQt4.QtWebKit import QWebView →
   from PyQt5.QtWebKitWidgets import QWebView

   Alternatively you can just import all modules from PyQt5.Qt, though maybe
   that would slow down the import a bit:

   from PyQt5.Qt import QWizard, QWebView

If something does not work after doing all these steps, please write to me
and I will try to help you.

-- 
Dmitry Shachnev


signature.asc
Description: PGP signature

Bug#834634: grib-api: Incorrect library path in CMake module (/usr/lib/lib/libgrib_api.so.0)

[Bas Couwenberg]

Source: grib-api
Version: 1.16.0-5
Severity: critical
Justification: breaks unrelated software
Control: affects -1 magics++ metview

Dear Maintainer,

With the recent update of grib-api both magics++ & metview still FTBFS:

 CMake Error at 
/usr/lib/x86_64-linux-gnu/cmake/grib_api/grib_api-targets.cmake:184 (message):
   The imported target "grib_api" references the file

  "/usr/lib/lib/libgrib_api.so.0"

   but this file does not exist.  Possible reasons include:

   * The file was deleted, renamed, or moved to another location.

   * An install or uninstall procedure did not complete successfully.

   * The installation package was faulty and contained

  "/usr/lib/x86_64-linux-gnu/cmake/grib_api/grib_api-targets.cmake"

   but not all the files it references.

 Call Stack (most recent call first):
   /usr/lib/x86_64-linux-gnu/cmake/grib_api/grib_api-config.cmake:78 (include)
   cmake/ecbuild_find_package.cmake:213 (find_package)
   cmake/ecbuild_use_package.cmake:269 (ecbuild_find_package)
   CMakeLists.txt:52 (ecbuild_use_package)

Please correct the library path in the CMake module, both magics++ &
metview are affected by the upcoming libgeotiff & proj transitions and
will need to be rebuilt for those.

Kind Regards,

Bas

Processed: Re: Bug#825727: python-babel: FTBFS: assert 'GMT+00:00' == 'GMT-01:59'

[Debian Bug Tracking System]

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

> severity 825727 serious
Bug #825727 [src:python-babel] python-babel: FTBFS: assert 'GMT+00:00' == 
'GMT-01:59'
Severity set to 'serious' from 'important'
> thanks
Stopping processing here.

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

Bug#834631: mcmcpack: FTBFS: ERROR: dependency 'mcmc' is not available for package 'MCMCpack'

[Chris Lamb]

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

Dear Maintainer,

mcmcpack fails to build from source in unstable/amd64:

  [..]

  Preparing to unpack .../51-gfortran-6_6.1.1-12_amd64.deb ...
  Unpacking gfortran-6 (6.1.1-12) ...
  Selecting previously unselected package gfortran.
  Preparing to unpack .../52-gfortran_4%3a6.1.1-1_amd64.deb ...
  Unpacking gfortran (4:6.1.1-1) ...
  Selecting previously unselected package libblas-dev.
  Preparing to unpack .../53-libblas-dev_3.6.1-2_amd64.deb ...
  Unpacking libblas-dev (3.6.1-2) ...
  Selecting previously unselected package liblapack-dev.
  Preparing to unpack .../54-liblapack-dev_3.6.1-2_amd64.deb ...
  Unpacking liblapack-dev (3.6.1-2) ...
  Selecting previously unselected package libtinfo-dev:amd64.
  Preparing to unpack .../55-libtinfo-dev_6.0+20160625-1_amd64.deb ...
  Unpacking libtinfo-dev:amd64 (6.0+20160625-1) ...
  Selecting previously unselected package libncurses5-dev:amd64.
  Preparing to unpack .../56-libncurses5-dev_6.0+20160625-1_amd64.deb ...
  Unpacking libncurses5-dev:amd64 (6.0+20160625-1) ...
  Selecting previously unselected package libreadline6-dev:amd64.
  Preparing to unpack .../57-libreadline6-dev_6.3-8+b4_amd64.deb ...
  Unpacking libreadline6-dev:amd64 (6.3-8+b4) ...
  Selecting previously unselected package libreadline-dev:amd64.
  Preparing to unpack .../58-libreadline-dev_6.3-8+b4_amd64.deb ...
  Unpacking libreadline-dev:amd64 (6.3-8+b4) ...
  Selecting previously unselected package libjpeg62-turbo-dev:amd64.
  Preparing to unpack .../59-libjpeg62-turbo-dev_1%3a1.5.0-1_amd64.deb ...
  Unpacking libjpeg62-turbo-dev:amd64 (1:1.5.0-1) ...
  Selecting previously unselected package libjpeg-dev.
  Preparing to unpack .../60-libjpeg-dev_1%3a1.5.0-1_all.deb ...
  Unpacking libjpeg-dev (1:1.5.0-1) ...
  Selecting previously unselected package libpcre16-3:amd64.
  Preparing to unpack .../61-libpcre16-3_2%3a8.39-1_amd64.deb ...
  Unpacking libpcre16-3:amd64 (2:8.39-1) ...
  Selecting previously unselected package libpcre32-3:amd64.
  Preparing to unpack .../62-libpcre32-3_2%3a8.39-1_amd64.deb ...
  Unpacking libpcre32-3:amd64 (2:8.39-1) ...
  Selecting previously unselected package libpcrecpp0v5:amd64.
  Preparing to unpack .../63-libpcrecpp0v5_2%3a8.39-1_amd64.deb ...
  Unpacking libpcrecpp0v5:amd64 (2:8.39-1) ...
  Selecting previously unselected package libpcre3-dev:amd64.
  Preparing to unpack .../64-libpcre3-dev_2%3a8.39-1_amd64.deb ...
  Unpacking libpcre3-dev:amd64 (2:8.39-1) ...
  Selecting previously unselected package zlib1g-dev:amd64.
  Preparing to unpack .../65-zlib1g-dev_1%3a1.2.8.dfsg-2+b1_amd64.deb ...
  Unpacking zlib1g-dev:amd64 (1:1.2.8.dfsg-2+b1) ...
  Selecting previously unselected package libpng-dev:amd64.
  Preparing to unpack .../66-libpng-dev_1.6.24-2_amd64.deb ...
  Unpacking libpng-dev:amd64 (1.6.24-2) ...
  Selecting previously unselected package libbz2-dev:amd64.
  Preparing to unpack .../67-libbz2-dev_1.0.6-8_amd64.deb ...
  Unpacking libbz2-dev:amd64 (1.0.6-8) ...
  Selecting previously unselected package liblzma-dev:amd64.
  Preparing to unpack .../68-liblzma-dev_5.1.1alpha+20120614-2.1_amd64.deb ...
  Unpacking liblzma-dev:amd64 (5.1.1alpha+20120614-2.1) ...
  Selecting previously unselected package icu-devtools.
  Preparing to unpack .../69-icu-devtools_57.1-2_amd64.deb ...
  Unpacking icu-devtools (57.1-2) ...
  Selecting previously unselected package libasan2:amd64.
  Preparing to unpack .../70-libasan2_5.4.1-1_amd64.deb ...
  Unpacking libasan2:amd64 (5.4.1-1) ...
  Selecting previously unselected package libmpx0:amd64.
  Preparing to unpack .../71-libmpx0_5.4.1-1_amd64.deb ...
  Unpacking libmpx0:amd64 (5.4.1-1) ...
  Selecting previously unselected package libgcc-5-dev:amd64.
  Preparing to unpack .../72-libgcc-5-dev_5.4.1-1_amd64.deb ...
  Unpacking libgcc-5-dev:amd64 (5.4.1-1) ...
  Selecting previously unselected package libstdc++-5-dev:amd64.
  Preparing to unpack .../73-libstdc++-5-dev_5.4.1-1_amd64.deb ...
  Unpacking libstdc++-5-dev:amd64 (5.4.1-1) ...
  Selecting previously unselected package libicu-dev.
  Preparing to unpack .../74-libicu-dev_57.1-2_amd64.deb ...
  Unpacking libicu-dev (57.1-2) ...
  Selecting previously unselected package cdbs.
  Preparing to unpack .../75-cdbs_0.4.142_all.deb ...
  Unpacking cdbs (0.4.142) ...
  Selecting previously unselected package r-base-dev.
  Preparing to unpack .../76-r-base-dev_3.3.1-1_all.deb ...
  Unpacking r-base-dev (3.3.1-1) ...
  Selecting previously unselected package r-cran-lattice.
  Preparing to unpack .../77-r-cran-lattice_0.20-33-1_amd64.deb ...
  Unpacking r-cran-lattice (0.20-33-1) ...
  Selecting previously unselected package r-cran-coda.
  Preparing to unpack .../78-r-cran-coda_0.18-1-1_all.deb ...
  Unpacking r-cran-coda (0.18-1-1) ...
  Selecting previously 

Bug#834067: marked as done (python-toposort: ships /usr/lib/python2.7/dist-packages/test/__init__.py)

[Debian Bug Tracking System]

Your message dated Wed, 17 Aug 2016 18:58:57 +0200
with message-id 

Bug#811481: marked as done (ovirt-guest-agent service still doesn't start)

[Debian Bug Tracking System]

Your message dated Wed, 17 Aug 2016 16:55:53 +
with message-id 
and subject line Bug#811481: fixed in ovirt-guest-agent 1.0.12.2.dfsg-1
has caused the Debian Bug report #811481,
regarding ovirt-guest-agent service still doesn't start
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.)


-- 
811481: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=811481
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: ovirt-guest-agent
Version: 1.0.11.2.dfsg-1
Severity: important

When systemd is used, ovirt-guest-agent still doesn't start.  The
problem is that /var/log/ovirt-guest-agent owner is set to root:root, so
the daemon can't write to the directory and fails.  (The directory
ownership is fixed in init.d script but that is not executed with
systemd.)
--- End Message ---
--- Begin Message ---
Source: ovirt-guest-agent
Source-Version: 1.0.12.2.dfsg-1

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

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

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

Debian distribution maintenance software
pp.
Laszlo Boszormenyi (GCS)  (supplier of updated 
ovirt-guest-agent 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, 16 Aug 2016 18:32:11 +
Source: ovirt-guest-agent
Binary: ovirt-guest-agent
Architecture: source all
Version: 1.0.12.2.dfsg-1
Distribution: unstable
Urgency: low
Maintainer: Laszlo Boszormenyi (GCS) 
Changed-By: Laszlo Boszormenyi (GCS) 
Description:
 ovirt-guest-agent - daemon that resides within guest virtual machines
Closes: 811481
Changes:
 ovirt-guest-agent (1.0.12.2.dfsg-1) unstable; urgency=low
 .
   * New upstream release.
   * Change owner of log directory to ovirtagent in postinst (closes: #811481).
   * Update Standards-Version to 3.9.8 .
Checksums-Sha1:
 a9848b68bd4a2a8121602df58c7b08c6ac264dc8 1982 
ovirt-guest-agent_1.0.12.2.dfsg-1.dsc
 e1f26315a7274b26bb45b826086dd63e774890f3 93672 
ovirt-guest-agent_1.0.12.2.dfsg.orig.tar.xz
 51c831e3d3a5e93497fb3431aa873b94af0ba732 6012 
ovirt-guest-agent_1.0.12.2.dfsg-1.debian.tar.xz
 4977f251f34c31494b4b5b5ba671f08e0a809ddb 51828 
ovirt-guest-agent_1.0.12.2.dfsg-1_all.deb
Checksums-Sha256:
 0ff11295a542bd15e472f9ed5455eb425873d211ced2aae738ef5918db81e285 1982 
ovirt-guest-agent_1.0.12.2.dfsg-1.dsc
 ddf99f72458f4232a399d119c44063e76bea2d7ff1072b45733fad4cfc88a514 93672 
ovirt-guest-agent_1.0.12.2.dfsg.orig.tar.xz
 99f6ccfa67ba4aec39ee3f2cd13b6a93e4437c32c7db41761ccb61cb15f66ca7 6012 
ovirt-guest-agent_1.0.12.2.dfsg-1.debian.tar.xz
 bcff180dcc86e81fbd54542aabcdb12b7a69349118afa2fd0b0b08f1b183f121 51828 
ovirt-guest-agent_1.0.12.2.dfsg-1_all.deb
Files:
 c7d12c656268ec630a60beef87a0cfca 1982 utils extra 
ovirt-guest-agent_1.0.12.2.dfsg-1.dsc
 ff006394792ce677673e4e49887d5134 93672 utils extra 
ovirt-guest-agent_1.0.12.2.dfsg.orig.tar.xz
 dc557104fadf9abb9628ececb686f78b 6012 utils extra 
ovirt-guest-agent_1.0.12.2.dfsg-1.debian.tar.xz
 7db2c6047f1e147f231dd0d3852fb632 51828 utils extra 
ovirt-guest-agent_1.0.12.2.dfsg-1_all.deb

-BEGIN PGP SIGNATURE-
Version: GnuPG v1

iQIcBAEBCAAGBQJXtIC9AAoJENzjEOeGTMi/EjIP/018wPLD+b24z8hGRvGzzG1D
aylKhiBve1k8b6JplyfqwACVHN5mlxOI1solB7SvGIZ+dZh+8nMGWogLyrWHsqYu
XljXjlB3f29I1d4bs3IbxDXiEppRxfai9UXtUDVlSeMJ7u63P5/yJjA1ssKO2DnG
ajLnC8DzJhR1DQ+KZWRExJ4JUgDoEGXYl3wmpuyyXTz8+O6uvyqWE65TGRRxoBZ/
orqL9EuxRzSHVtACRIwUBeYFypFYscrMIlLNv+ZjaBZJWEX7Vy0OyxPXlUA9iJfG
BtEZ6ckF2uMI5m7tjTgSYyNar9i3AGkUbbh0Ut9vmhJ86Zn08PUDddRrtzsao8mt
tR3t3r1XN5lYq0L+j6jaZ/O1g7O3ybxyyDMtwrgcz6eFEc6oCxbeCnmd8268frSR
ssH8XsKClEbNFjA9Xp3J9SWyAUyxfR0Akr6Hlmp7lQdArKyd9B5iemascVHc7a20
hw94aOpK1ooGNsbzwLKS0R2Njxztj+vu61XhwNLtR1K4F75pVW2hcI/LT2eYl9Re
8Q9fE+BWA8qAv4028D790izD0XU7laOLsHmmkPW1by4qZyte99lGPedzsVPF/XU1
HwpaW5+pi7qtCQh/VTTY1Q+vBYcfjPEwr0BwfXqKJpzZN4ZtTSR+W8Xqg0HcqJCF
nil8Y2z0r98mJ/Kr7rQF
=aLrs
-END PGP SIGNATURE End Message ---

Processed: lucene2: FTBFS too much often

[Debian Bug Tracking System]

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

> retitle 749365 lucene2: FTBFS too much often
Bug #749365 [lucene2] lucene2: FTBFS - sporadic test failure
Changed Bug title to 'lucene2: FTBFS too much often' from 'lucene2: FTBFS - 
sporadic test failure'.
> severity 749365 serious
Bug #749365 [lucene2] lucene2: FTBFS too much often
Severity set to 'serious' from 'important'
> thanks
Stopping processing here.

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

Processed: reopen 737921

[Debian Bug Tracking System]

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

> reopen 737921
Bug #737921 {Done: "FedEx SmartPost" } [gnutls26] 
[TLS1.2] gnutls only likes SHA1 and SHA256 certificates
Bug #740160 {Done: "FedEx SmartPost" } [gnutls26] 
gnutls unusable with cacert SHA2-512 sigs
'reopen' may be inappropriate when a bug has been closed with a version;
all fixed versions will be cleared, and you may need to re-add them.
Bug reopened
No longer marked as fixed in versions 2.12.23-17+rm.
No longer marked as fixed in versions 2.12.23-17+rm.
>
End of message, stopping processing here.

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

Bug#834624: vm-bonus-el: vm-bogofilter.el doesn't byte-compile

[Joe Pfeiffer]

Package: vm-bonus-el
Version: 35.2+nmu1
Severity: serious

Attempting to install, byte-compilation fails.  The compilation log in
/tmp/ contains

emacs24 -q -no-site-file --no-site-file -batch -l path.el -f batch-byte-compile 
vm-bogofilter.el
Eager macro-expansion failure: (void-variable vm-supported-sort-keys)
Eager macro-expansion failure: (void-variable vm-supported-sort-keys)
Eager macro-expansion failure: (void-variable vm-supported-sort-keys)
Eager macro-expansion failure: (void-variable vm-supported-sort-keys)
Eager macro-expansion failure: (void-variable vm-supported-sort-keys)
Eager macro-expansion failure: (void-variable vm-supported-sort-keys)
Eager macro-expansion failure: (void-variable vm-supported-sort-keys)
Eager macro-expansion failure: (void-variable vm-supported-sort-keys)
Eager macro-expansion failure: (void-variable vm-supported-sort-keys)
Eager macro-expansion failure: (void-variable vm-supported-sort-keys)
Eager macro-expansion failure: (void-variable vm-supported-sort-keys)
Eager macro-expansion failure: (void-variable vm-supported-sort-keys)
Eager macro-expansion failure: (void-variable vm-supported-sort-keys)
Eager macro-expansion failure: (void-variable vm-supported-sort-keys)
Eager macro-expansion failure: (void-variable vm-supported-sort-keys)
Eager macro-expansion failure: (void-variable vm-supported-sort-keys)
Eager macro-expansion failure: (void-variable vm-supported-sort-keys)
Eager macro-expansion failure: (void-variable vm-supported-sort-keys)
Eager macro-expansion failure: (void-variable vm-supported-sort-keys)
Eager macro-expansion failure: (void-variable vm-supported-sort-keys)
Eager macro-expansion failure: (void-variable vm-supported-sort-keys)
Eager macro-expansion failure: (void-variable vm-supported-sort-keys)
Eager macro-expansion failure: (void-variable vm-supported-sort-keys)
Eager macro-expansion failure: (void-variable vm-supported-sort-keys)
Eager macro-expansion failure: (void-variable vm-supported-sort-keys)
Eager macro-expansion failure: (void-variable vm-supported-sort-keys)
Eager macro-expansion failure: (void-variable vm-supported-sort-keys)
Eager macro-expansion failure: (void-variable vm-supported-sort-keys)
Eager macro-expansion failure: (void-variable vm-supported-sort-keys)
Eager macro-expansion failure: (void-variable vm-supported-sort-keys)
Eager macro-expansion failure: (void-variable vm-supported-sort-keys)
Eager macro-expansion failure: (void-variable vm-supported-sort-keys)
Eager macro-expansion failure: (void-variable vm-supported-sort-keys)
Eager macro-expansion failure: (void-variable vm-supported-sort-keys)
Eager macro-expansion failure: (void-variable vm-supported-sort-keys)
Eager macro-expansion failure: (void-variable vm-supported-sort-keys)
Eager macro-expansion failure: (void-variable vm-supported-sort-keys)
Eager macro-expansion failure: (void-variable vm-supported-sort-keys)
Eager macro-expansion failure: (void-variable vm-supported-sort-keys)
Eager macro-expansion failure: (void-variable vm-supported-sort-keys)
Eager macro-expansion failure: (void-variable vm-supported-sort-keys)
Eager macro-expansion failure: (void-variable vm-supported-sort-keys)
Eager macro-expansion failure: (void-variable vm-supported-sort-keys)
Eager macro-expansion failure: (void-variable vm-supported-sort-keys)
Eager macro-expansion failure: (void-variable vm-supported-sort-keys)
Eager macro-expansion failure: (void-variable vm-supported-sort-keys)
Eager macro-expansion failure: (void-variable vm-supported-sort-keys)
Eager macro-expansion failure: (void-variable vm-supported-sort-keys)
Eager macro-expansion failure: (void-variable vm-supported-sort-keys)
Eager macro-expansion failure: (void-variable vm-supported-sort-keys)
Eager macro-expansion failure: (void-variable vm-supported-sort-keys)
Eager macro-expansion failure: (void-variable vm-supported-sort-keys)
Eager macro-expansion failure: (void-variable vm-supported-sort-keys)
Eager macro-expansion failure: (void-variable vm-supported-sort-keys)
Eager macro-expansion failure: (void-variable vm-supported-sort-keys)
Eager macro-expansion failure: (void-variable vm-supported-sort-keys)
Eager macro-expansion failure: (void-variable vm-supported-sort-keys)
Eager macro-expansion failure: (void-variable vm-supported-sort-keys)
Eager macro-expansion failure: (void-variable vm-supported-sort-keys)
Eager macro-expansion failure: (void-variable vm-supported-sort-keys)
Eager macro-expansion failure: (void-variable vm-supported-sort-keys)
Eager macro-expansion failure: (void-variable vm-supported-sort-keys)
Eager macro-expansion failure: (void-variable vm-supported-sort-keys)
Eager macro-expansion failure: (void-variable vm-supported-sort-keys)
Eager macro-expansion failure: (void-variable vm-supported-sort-keys)
Eager macro-expansion failure: (void-variable vm-supported-sort-keys)
Eager macro-expansion failure: (void-variable vm-supported-sort-keys)
Eager macro-expansion failure: (void-variable 

Bug#828037: fontconfig: diff for NMU version 2.11.0-6.6

[Raphael Hertzog]

Control: tags 828037 + pending

Dear maintainer,

Upstream responded in my bug report
(https://bugs.freedesktop.org/show_bug.cgi?id=96896) and suggested to use
a fontconfig rule to reject those files and that's what the attached patch
does. I tested it and it does indeed skip over .dpkg-tmp files that I
manually created.

I'm thus uploading it as a delayed NMU (versioned as 2.11.0-6.6) and
uploaded it to DELAYED/05.

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/
diff -Nru fontconfig-2.11.0/debian/changelog fontconfig-2.11.0/debian/changelog
--- fontconfig-2.11.0/debian/changelog	2016-08-06 10:24:50.0 +0200
+++ fontconfig-2.11.0/debian/changelog	2016-08-17 16:47:14.0 +0200
@@ -1,3 +1,11 @@
+fontconfig (2.11.0-6.6) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * Modifiy /etc/fontconfig/fonts.conf to ignore *.dpkg-tmp files.
+(Closes: #828037)
+
+ -- Raphaël Hertzog   Wed, 17 Aug 2016 16:46:23 +0200
+
 fontconfig (2.11.0-6.5) unstable; urgency=high
 
   * Non-maintainer upload.
diff -Nru fontconfig-2.11.0/debian/patches/series fontconfig-2.11.0/debian/patches/series
--- fontconfig-2.11.0/debian/patches/series	2016-08-06 10:24:50.0 +0200
+++ fontconfig-2.11.0/debian/patches/series	2016-08-17 16:33:16.0 +0200
@@ -5,3 +5,4 @@
 05_doc_files.patch
 06_cross.patch
 07_CVE-2016-5384-Properly-validate-offsets-in-cache-files.patch
+skip-dpkg-tmp-files.patch
diff -Nru fontconfig-2.11.0/debian/patches/skip-dpkg-tmp-files.patch fontconfig-2.11.0/debian/patches/skip-dpkg-tmp-files.patch
--- fontconfig-2.11.0/debian/patches/skip-dpkg-tmp-files.patch	1970-01-01 01:00:00.0 +0100
+++ fontconfig-2.11.0/debian/patches/skip-dpkg-tmp-files.patch	2016-08-17 16:37:31.0 +0200
@@ -0,0 +1,25 @@
+Description: Configure fontconfig to ignore *.dpkg-tmp files
+Bug: https://bugs.freedesktop.org/show_bug.cgi?id=96896
+Bug-Debian: https://bugs.debian.org/828037
+Author: Raphaël Hertzog 
+Last-Update: 2016-08-17
+---
+This patch header follows DEP-3: http://dep.debian.net/deps/dep3/
+--- a/fonts.conf.in
 b/fonts.conf.in
+@@ -66,6 +66,15 @@
+ 	
+ 
+ 
++	
++		
++			*.dpkg-tmp
++		
++	
++
++
+ 	@CONFIGDIR@

Processed: fontconfig: diff for NMU version 2.11.0-6.6

[Debian Bug Tracking System]

Processing control commands:

> tags 828037 + pending
Bug #828037 [fontconfig] fontconfig: font-config should not register .dpkg-tmp 
files in its cache, users ends up seeing squares instead of expected characters
Added tag(s) pending.

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

Bug#834617: keystone: FTBFS in testing (ImportError: No module named pep8)

[Santiago Vila]

Package: src:keystone
Version: 2:9.0.2-2
Severity: serious

Dear maintainer:

I tried to build this package with "dpkg-buildpackage -A"
(which is what the "Arch: all" autobuilder would do to build it)
but it failed:


[...]
 debian/rules build-indep
pyversions: missing X(S)-Python-Version in control file, fall back to 
debian/pyversions
pyversions: missing debian/pyversions file, fall back to supported versions
py3versions: no X-Python3-Version in control file, using supported versions
dh build-indep --buildsystem=python_distutils --with python2,sphinxdoc,systemd
   dh_testdir -i -O--buildsystem=python_distutils
   dh_update_autotools_config -i -O--buildsystem=python_distutils
   dh_auto_configure -i -O--buildsystem=python_distutils
   debian/rules override_dh_auto_build
make[1]: Entering directory '/<>'
pyversions: missing X(S)-Python-Version in control file, fall back to 
debian/pyversions
pyversions: missing debian/pyversions file, fall back to supported versions
py3versions: no X-Python3-Version in control file, using supported versions

[... snipped ...]

done
+ cut -d. -f1
+ echo 2.7
+ PYMAJOR=2
+ echo ===> Testing with python2.7 (python2)
===> Testing with python2.7 (python2)
+ rm -rf .testrepository
+ testr-python2 init
+ mktemp -t
+ TEMP_REZ=/tmp/tmp.aALQ0zRxXX
+ subunit2pyunit
+ tee /tmp/tmp.aALQ0zRxXX
+ PYTHONPATH=/<> PYTHON=python2.7 testr-python2 run --subunit 
keystone\.tests\.unit.*
running=
${PYTHON:-python} -m subunit.run discover -t ./ 
${OS_TEST_PATH:-./keystone/tests/unit} --list 
--- impNon-zero exit code (2) from test listing.
ort errors ---
Failed to import test module: keystone.tests.unit.test_hacking_checks
Traceback (most recent call last):
  File "/usr/lib/python2.7/dist-packages/unittest2/loader.py", line 456, in 
_find_test_path
module = self._get_module_from_name(name)
  File "/usr/lib/python2.7/dist-packages/unittest2/loader.py", line 395, in 
_get_module_from_name
__import__(name)
  File "keystone/tests/unit/test_hacking_checks.py", line 16, in 
import pep8
ImportError: No module named pep8

--
Ran 0 tests in 1.521s

OK
+ subunit-stats
+ subunit-filter -s --no-passthrough
+ cat /tmp/tmp.aALQ0zRxXX
Total tests:   0
Passed tests:  0
Failed tests:  0
Skipped tests: 0
Seen tags: 
+ rm -f /tmp/tmp.aALQ0zRxXX
+ testr-python2 slowest
debian/rules:22: recipe for target 'override_dh_auto_test' failed
make[1]: *** [override_dh_auto_test] Error 3
make[1]: Leaving directory '/<>'
debian/rules:18: recipe for target 'build-indep' failed
make: *** [build-indep] Error 2
dpkg-buildpackage: error: debian/rules build-indep gave error exit status 2


If you manage to make it build again, please consider uploading in
source-only form, so that we get pretty official build logs here:

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

Thanks.

Processed: cura-engine: FTBFS: mathcalls.h:109:1: error: '__DECL_SIMD__log' does not name a type

[Debian Bug Tracking System]

Processing control commands:

> tags -1 patch
Bug #818140 [src:cura-engine] cura-engine: FTBFS: mathcalls.h:109:1: error: 
'__DECL_SIMD__log' does not name a type
Added tag(s) patch.

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

Bug#818140: cura-engine: FTBFS: mathcalls.h:109:1: error: '__DECL_SIMD__log' does not name a type

[Graham Inggs]

Control: tags -1 patch


Hi Maintainer

Please find attached patch which avoids a FTBFS with recent toolchain.

As noted in #744112, this version of cura-engine is rather old.

Regards
Graham

--- a/utils/logoutput.cpp
+++ b/utils/logoutput.cpp
@@ -15,7 +15,7 @@
 fflush(stdout);
 }
 
-void _log(const char* fmt, ...)
+void log(const char* fmt, ...)
 {
 if (verbose_level < 1)
 return;
--- a/utils/logoutput.h
+++ b/utils/logoutput.h
@@ -5,8 +5,7 @@
 extern int verbose_level;
 
 void logError(const char* fmt, ...);
-void _log(const char* fmt, ...);
-#define log _log
+void log(const char* fmt, ...);
 void logProgress(const char* type, int value, int maxValue);
 
 #endif//LOGOUTPUT_H

Bug#834616: tex4ht is uninstallable in sid: depends on experimental texlive-htmlxml

[Helmut Grohne]

Package: tex4ht
Version: 20160814-1
Severity: serious
User: helm...@debian.org
Usertags: rebootstrap

Since the version mentioned above both tex4ht and texlive-htmlxml are
uninstallable in sid. sid's texlive-htmlxml depends on tex4ht, which in
turn depends on experimental's texlive-htmlxml.

Maybe the texlive-htmlxml upload should have gone to sid?

Helmut

Bug#834600: python-gnupg: FTBFS: Missing build-depends on gnupg

[Santiago Vila]

On Wed, Aug 17, 2016 at 04:55:13PM +0200, Elena ``of Valhalla'' wrote:

> Could you please tell me how are you generating the chroot, and how it
> ends up not having any version of gnupg installed?

I can't tell for sure.

I often use tools like deborphan and debfoster to make sure that the
chroot is really minimal. Recently I read in sbuild changelog that
gnupg was no longer required inside the chroot so I tried to see if
gnupg could be removed from the chroot, and yes, it could be removed.

So the only fast recipe I can give would be like this:

* Use debootstrap to create a chroot in any way you like.
* Install build-essential and debhelper.
* Then remove any package which is not in the attached list.

That's the chroot I'm currently using for stretch.

Thanks.
adduser
apt
autoconf
automake
autopoint
autotools-dev
base-files
base-passwd
bash
binutils
bsdmainutils
bsdutils
build-essential
bzip2
coreutils
cpp
cpp-6
dash
debconf
debhelper
debian-archive-keyring
debianutils
dh-autoreconf
dh-strip-nondeterminism
diffutils
dmsetup
dpkg
dpkg-dev
e2fslibs
e2fsprogs
eatmydata
fakeroot
file
findutils
g++
g++-6
gcc
gcc-5-base
gcc-6
gcc-6-base
gettext
gettext-base
gpgv
grep
groff-base
gzip
hostname
init-system-helpers
initscripts
insserv
intltool-debian
less
libacl1
libapt-pkg5.0
libarchive-zip-perl
libasan3
libatomic1
libattr1
libaudit-common
libaudit1
libblkid1
libbsd0
libbz2-1.0
libc-bin
libc-dev-bin
libc-l10n
libc6
libc6-dev
libcap-ng0
libcc1-0
libcilkrts5
libcomerr2
libcroco3
libdb5.3
libdebconfclient0
libdevmapper1.02.1
libdpkg-perl
libeatmydata1
libfakeroot
libfdisk1
libffi6
libfile-stripnondeterminism-perl
libgcc-6-dev
libgcc1
libgcrypt20
libgdbm3
libglib2.0-0
libgmp10
libgomp1
libgpg-error0
libicu57
libisl15
libitm1
liblsan0
liblz4-1
liblzma5
libmagic-mgc
libmagic1
libmount1
libmpc3
libmpfr4
libmpx2
libncurses5
libncursesw5
libpam-modules
libpam-modules-bin
libpam-runtime
libpam0g
libpcre3
libperl5.22
libpipeline1
libquadmath0
libselinux1
libsemanage-common
libsemanage1
libsepol1
libsigsegv2
libsmartcols1
libss2
libstdc++-6-dev
libstdc++6
libsystemd0
libtimedate-perl
libtinfo5
libtool
libtsan0
libubsan0
libudev1
libunistring0
libustr-1.0-1
libuuid1
libxml2
linux-libc-dev
locales
login
lsb-base
m4
make
man-db
mawk
mount
multiarch-support
nano
ncurses-base
ncurses-bin
passwd
patch
perl
perl-base
perl-modules-5.22
po-debconf
sed
sensible-utils
startpar
sysv-rc
sysvinit-utils
tar
tzdata
util-linux
xz-utils
zlib1g

Bug#834600: python-gnupg: FTBFS: Missing build-depends on gnupg

[Elena ``of Valhalla'']

Thanks for your report.

This doesn't come completely unexpected: I knew that python-gnupg wasn't
going to build as-is with gnupg pointing to gnupg2.1 (#834514), and in
the last few days I've been working on a fix, which is currently
building locally, but wouldn't build on a buildbot for lack of entropy.

I'm a bit more surprised by the specific failure: while gnupg is not
essential, installing build-essential in a chroot where it wasn't
available did install it, so AFAIK it should be available (altough in
version 2.1)

Manually forcing the removal of gnupg afterwards did indeed result in
the error you mentioned, among a number of others, but I'm not sure how
such a situation would end up happening.

(The version I'm currently working on does add an explicit dependency on
gnupg1, but I was planning to remove it by the time #834514 is fixed
upstream)

Could you please tell me how are you generating the chroot, and how it
ends up not having any version of gnupg installed?

-- 
Elena ``of Valhalla''

Processed: tagging 834600

[Debian Bug Tracking System]

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

> tags 834600 + moreinfo
Bug #834600 [src:python-gnupg] python-gnupg: FTBFS: Missing build-depends on 
gnupg
Added tag(s) moreinfo.
> thanks
Stopping processing here.

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

Bug#828037: fontconfig: font-config should not register .dpkg-tmp files in its cache, users ends up seeing squares instead of expected characters

[Keith Packard]

Raphael Hertzog  writes:

> (Keith, I would really like if you could step in, fontconfig
> is at its fifth NMU in a row and the sources are not even in
> a git packaging repo... I find it highly demotivating to contribute
> without any reaction from the package maintainer when I know that
> he's not MIA but just ignoring emails)

Sorry that I haven't been dealing with fontconfig packaging for a while;
I've been watching upstream try to deal with a couple of architectural
issues and trying to figure out how to fix them.

I've also got some new packaging bits that I want to finish which move
fontconfig to dh; the current bits are pretty hard to comprehend.

-- 
-keith


signature.asc
Description: PGP signature

Bug#834147: binutils: breaks mips and mipsel link of blender

[James Cowgill]

Hi,

On Sun, 14 Aug 2016 13:04:18 + Mattia Rizzolo  wrote:
> Control: reopen -1
> control: found -1 2.27-5
> 
> On Sun, Aug 14, 2016 at 01:02:28PM +0200, Matthias Klose wrote:
> > On 12.08.2016 16:06, Gianfranco Costamagna wrote:
> > > source: binutils
> > > version: 2.27-1
> > > severity: serious
> > > justification: breaks link and build of depending packages.
> > > 
> > > Hi, as said the latest blender upload is not working anymore, and since 
> > > the failure seems to be in ld.gold, I presume
> > > the changes between 2.26.1 and 2.27 broke the link.
> > 
> > Please check for open and recently closed bug reports before filing 
> > duplicates.
> 
> This is a different bug than #834096.
> Indeed it's still present in a build done with 2.27-5:
> https://buildd.debian.org/status/fetch.php?pkg=blender=mips=2.77.a%2Bdfsg0-8=1471014507

I think this is actually a gcc 6 regression (from gcc 5).

The LO16 errors also appear in the successful 2.77.a+dfsg0-7 log in a
different format, but do not cause ld to exit with a failing exit code
(this might be a separate bug in binutils). The errors only started
appearing in the blender build logs after gcc6 was made the default.

Disabling gold on mips by removing the "-fuse-ld=gold" option fixes the
build and can be used as a workaround, but it still produces some LO16
errors and I'm not sure if it actually produces a working blender
executable.

James



signature.asc
Description: OpenPGP digital signature

Bug#834600: python-gnupg: FTBFS: Missing build-depends on gnupg

[Santiago Vila]

Package: src:python-gnupg
Version: 0.3.8-2
Severity: serious
Tags: patch

Dear maintainer:

I tried to build this package with "dpkg-buildpackage -A"
(which is what the "Arch: all" autobuilder would do to build it)"
but it failed:

-
ERROR: test_deletion (__main__.GPGTestCase)
Test that key deletion works
--
Traceback (most recent call last):
  File "test_gnupg.py", line 102, in setUp
  self.gpg = gpg = gnupg.GPG(gnupghome=hd, gpgbinary=GPGBINARY)
File "/<>/gnupg.py", line 741, in __init__
result.stderr))
ValueError: Error invoking gpg: 126:
/<>/debian/bin/gpg: 6: exec: : Permission denied
-

I guess the package relies on gnupg being present during the build,
but gnupg is not essential.

Trivial (but untested) patch attached. Please try to reproduce the
error first on a chroot not having gnupg installed because I may be
wrong about the reason why this fails.

Thanks.--- a/debian/control
+++ b/debian/control
@@ -3,7 +3,7 @@ Maintainer: Elena Grandi 
 Uploaders: Debian Python Modules Team 

 Section: python
 Priority: optional
-Build-Depends: python-all (>= 2.6.6-3~), python3-all (>= 3.1.2-7~), debhelper 
(>= 9), dh-python
+Build-Depends: python-all (>= 2.6.6-3~), python3-all (>= 3.1.2-7~), debhelper 
(>= 9), dh-python, gnupg
 Standards-Version: 3.9.6
 Homepage: https://bitbucket.org/vinay.sajip/python-gnupg
 Vcs-Git: git://anonscm.debian.org/python-modules/packages/python-gnupg.git

Bug#811700: FTBFS with GCC 6: macro passed X arguments, takes Y

[Graham Inggs]

Control: tags -1 patch


Hi Maintainer

Please find patches from upstream attached, fixing the build issues with 
GCC6 and Boost 1.60.


Regards
Graham

Description: Fixed return value for deserialize() implementations
 This fixes a FTBFS with GCC 6.
Origin: upstream, https://github.com/alexrj/Slic3r/commit/6e5938c8330b5bdb6b85c3ca8dc188605ee56b98
Bug-Debian: https://bugs.debian.org/811700
Author: Alessandro Ranellucci 
Last-Update: 2016-03-13
--- a/xs/src/libslic3r/Config.cpp
+++ b/xs/src/libslic3r/Config.cpp
@@ -23,7 +23,10 @@
 
 // not the most efficient way, but easier than casting pointers to subclasses
 bool res = my_opt->deserialize( other.option(*it)->serialize() );
-if (!res) CONFESS("Unexpected failure when deserializing serialized value");
+if (!res) {
+std::string error = "Unexpected failure when deserializing serialized value for " + *it;
+CONFESS(error.c_str());
+}
 }
 }
 
--- a/xs/src/libslic3r/Config.hpp
+++ b/xs/src/libslic3r/Config.hpp
@@ -65,7 +65,8 @@
 
 bool deserialize(std::string str) {
 std::istringstream iss(str);
-return iss >> this->value;
+iss >> this->value;
+return !iss.fail();
 };
 };
 
@@ -124,7 +125,8 @@
 
 bool deserialize(std::string str) {
 std::istringstream iss(str);
-return iss >> this->value;
+iss >> this->value;
+return !iss.fail();
 };
 };
 
@@ -249,7 +251,8 @@
 bool deserialize(std::string str) {
 // don't try to parse the trailing % since it's optional
 std::istringstream iss(str);
-return iss >> this->value;
+iss >> this->value;
+return !iss.fail();
 };
 };
 
@@ -279,7 +282,8 @@
 bool deserialize(std::string str) {
 this->percent = str.find_first_of("%") != std::string::npos;
 std::istringstream iss(str);
-return iss >> this->value;
+iss >> this->value;
+return !iss.fail();
 };
 };
 
Description: Support incompatible change in Boost 1.60
Origin: upstream, https://github.com/alexrj/Slic3r/commit/f4a9fa6569722ef530fac995dc66ec8b6a3179ce
Author: Alessandro Ranellucci 
Last-Update: 2016-03-14
--- a/xs/src/libslic3r/Point.hpp
+++ b/xs/src/libslic3r/Point.hpp
@@ -124,11 +124,15 @@
 }
 
 // start Boost
+#include 
 #include 
 namespace boost { namespace polygon {
 template <>
 struct geometry_concept { typedef coordinate_concept type; };
 
+/* Boost.Polygon already defines a specialization for coordinate_traits as of 1.60:
+   https://github.com/boostorg/polygon/commit/0ac7230dd1f8f34cb12b86c8bb121ae86d3d9b97 */
+#if BOOST_VERSION < 106000
 template <>
 struct coordinate_traits {
 typedef coord_t coordinate_type;
@@ -138,6 +142,7 @@
 typedef long long coordinate_difference;
 typedef long double coordinate_distance;
 };
+#endif
 
 template <>
 struct geometry_concept { typedef point_concept type; };

Processed: FTBFS with GCC 6: macro passed X arguments, takes Y

[Debian Bug Tracking System]

Processing control commands:

> tags -1 patch
Bug #811700 [slic3r] FTBFS with GCC 6: macro passed X arguments, takes Y
Added tag(s) patch.

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

Bug#834597: [kgb-maintainers] Bug#834597: kgb-bot: FTBFS in testing

[gregor herrmann]

Control: user debian-p...@lists.debian.org
Control usertags + perl-cwd-inc-removal

On Wed, 17 Aug 2016 13:38:25 +, Santiago Vila wrote:

> I tried to build this package with "dpkg-buildpackage -A"
> (which is what the "Arch: all" autobuilder would do to build it)
> but it failed:

Thanks for your bug report.
 
> 
> [...]
>  debian/rules build-indep
> dh build-indep
>dh_testdir -i
>dh_update_autotools_config -i
>dh_auto_configure -i
>   perl Build.PL --installdirs vendor
> Base class package "Module::Build" is empty.
> (Perhaps you need to 'use' the module which defines that package first,
> or make that module available in @INC (@INC contains: privinc /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 privinc/My/Builder.pm line 6.
> BEGIN failed--compilation aborted at privinc/My/Builder.pm line 6.
> Compilation failed in require at Build.PL line 5.
> BEGIN failed--compilation aborted at Build.PL line 5.
> dh_auto_configure: perl Build.PL --installdirs vendor returned exit code 255
> debian/rules:4: recipe for target 'build-indep' failed
> make: *** [build-indep] Error 2
> dpkg-buildpackage: error: debian/rules build-indep gave error exit status 2
> 

Ah, another instance of the fallout of "no . in @INC" and the
following problems with base.pm.
 
Let's add it to the list (i.e. set usertags).


Cheers,
gregor

-- 
 .''`.  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
   `-   BOFH excuse #311:  transient bus protocol violation 

Bug#749714: marked as done (liblog4ada: failed to rename -dev package)

[Debian Bug Tracking System]

Your message dated Wed, 17 Aug 2016 15:45:39 +0200
with message-id <20160817134538.xvccnquydjfuxcxx@pegase>
and subject line close bugs in 1.3-1 fixed by unreleased 1.2-5.1
has caused the Debian Bug report #749714,
regarding liblog4ada: failed to rename -dev package
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.)


-- 
749714: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=749714
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:liblog4ada
Version: 1.2-4
Severity: serious
Justification: policy violation

The name of the -dev package must change whenever any of the .ali files
in the package changes.  Compiling against libgnat-4.9 instead of
libgnat-4.6 causes such a change.

Similarly the name and soname of the shared library must change.

-- 
Ludovic Brenta.
--- End Message ---
--- Begin Message ---
Version: 1.3-1

liblog4ada/1.2-5.1 has rever been uploaded. I should have removed the
stanza from the changelog and closed the bugs with 1.3-1.

  * Non-maintainer upload.
  * Build with gnat-6. Closes: #831237, #756445, #749714.
  * Bump ALI and SO version
  * Add symbols file for ppc64. Closes: #801445.
 -- Matthias Klose   Thu, 11 Aug 2016 14:54:15 +0200--- End Message ---

Bug#756445: marked as done (liblog4ada2-dev" not installable in sid)

[Debian Bug Tracking System]

Your message dated Wed, 17 Aug 2016 15:45:39 +0200
with message-id <20160817134538.xvccnquydjfuxcxx@pegase>
and subject line close bugs in 1.3-1 fixed by unreleased 1.2-5.1
has caused the Debian Bug report #756445,
regarding liblog4ada2-dev" not installable in sid
to be marked as done.

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

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


-- 
756445: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=756445
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: liblog4ada2-dev
Version: 1.2-4
Severity: serious
User: trei...@debian.org
Usertags: edos-uninstallable,

liblog4ada2-dev is not installable in sid, on any architecture, since it
depends both on gnat and gnat-4.6. Package gnat depends on gnat-4.9. which
is in conflict with gnat-4.6.

-Ralf.
--- End Message ---
--- Begin Message ---
Version: 1.3-1

liblog4ada/1.2-5.1 has rever been uploaded. I should have removed the
stanza from the changelog and closed the bugs with 1.3-1.

  * Non-maintainer upload.
  * Build with gnat-6. Closes: #831237, #756445, #749714.
  * Bump ALI and SO version
  * Add symbols file for ppc64. Closes: #801445.
 -- Matthias Klose   Thu, 11 Aug 2016 14:54:15 +0200--- End Message ---

Bug#831237: marked as done (liblog4ada: FTBFS: unsatisfiable build-dependencies: libxmlezout3-dev, gnat-4.9)

[Debian Bug Tracking System]

Your message dated Wed, 17 Aug 2016 15:45:39 +0200
with message-id <20160817134538.xvccnquydjfuxcxx@pegase>
and subject line close bugs in 1.3-1 fixed by unreleased 1.2-5.1
has caused the Debian Bug report #831237,
regarding liblog4ada: FTBFS: unsatisfiable build-dependencies: 
libxmlezout3-dev, gnat-4.9
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.)


-- 
831237: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=831237
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: liblog4ada
Version: 1.2-5
Severity: serious
Tags: stretch sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20160714 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):
> ┌──┐
> │ Install liblog4ada build dependencies (apt-based resolver)  
>  │
> └──┘
> 
> Installing build dependencies
> 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:
>  sbuild-build-depends-liblog4ada-dummy : Depends: libxmlezout3-dev but it is 
> not going to be installed
>  Depends: gnat-4.9 but it is not 
> going to be installed
> E: Unable to correct problems, you have held broken packages.
> apt-get failed.

The full build log is available from:
   
http://people.debian.org/~lucas/logs/2016/07/14/liblog4ada_1.2-5_unstable_gcc5.log

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 ---
Version: 1.3-1

liblog4ada/1.2-5.1 has rever been uploaded. I should have removed the
stanza from the changelog and closed the bugs with 1.3-1.

  * Non-maintainer upload.
  * Build with gnat-6. Closes: #831237, #756445, #749714.
  * Bump ALI and SO version
  * Add symbols file for ppc64. Closes: #801445.
 -- Matthias Klose   Thu, 11 Aug 2016 14:54:15 +0200--- End Message ---

Bug#834597: kgb-bot: FTBFS in testing

[Santiago Vila]

Package: src:kgb-bot
Version: 1.33-2
Severity: serious

Dear maintainer:

I tried to build this package with "dpkg-buildpackage -A"
(which is what the "Arch: all" autobuilder would do to build it)
but it failed:


[...]
 debian/rules build-indep
dh build-indep
   dh_testdir -i
   dh_update_autotools_config -i
   dh_auto_configure -i
perl Build.PL --installdirs vendor
Base class package "Module::Build" is empty.
(Perhaps you need to 'use' the module which defines that package first,
or make that module available in @INC (@INC contains: privinc /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 privinc/My/Builder.pm line 6.
BEGIN failed--compilation aborted at privinc/My/Builder.pm line 6.
Compilation failed in require at Build.PL line 5.
BEGIN failed--compilation aborted at Build.PL line 5.
dh_auto_configure: perl Build.PL --installdirs vendor returned exit code 255
debian/rules:4: recipe for target 'build-indep' failed
make: *** [build-indep] Error 2
dpkg-buildpackage: error: debian/rules build-indep gave error exit status 2


I guess nobody tried to build this package in a long time, maybe
because it's "Arch: all", or maybe because it's blacklisted in the
reproducible builds setup:

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

because of Bug #782079.

If you manage to make it build again, I would strongly recommend that
you upload it in source-only form, so that we get pretty official
build logs here:

https://buildd.debian.org/status/package.php?p=kgb-bot

Thanks.

Bug#834075: marked as done (libvariantslib-ocaml{, -dev}: fails to upgrade from 'sid' - trying to overwrite /usr/lib/ocaml/variantslib/{META, variantslib.a})

[Debian Bug Tracking System]

Your message dated Wed, 17 Aug 2016 12:37:28 +
with message-id 
and subject line Bug#834075: fixed in variantslib 113.33.03-2
has caused the Debian Bug report #834075,
regarding libvariantslib-ocaml{, -dev}: fails to upgrade from 'sid' - trying to 
overwrite /usr/lib/ocaml/variantslib/{META, variantslib.a}
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.)


-- 
834075: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=834075
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: libvariantslib-ocaml,libvariantslib-ocaml-dev
Version: 113.33.03-1
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

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

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

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

  Selecting previously unselected package libvariantslib-ocaml.
  Preparing to unpack .../libvariantslib-ocaml_113.33.03-1_amd64.deb ...
  Unpacking libvariantslib-ocaml (113.33.03-1) ...
  dpkg: error processing archive 
/var/cache/apt/archives/libvariantslib-ocaml_113.33.03-1_amd64.deb (--unpack):
   trying to overwrite '/usr/lib/ocaml/variantslib/META', which is also in 
package libvariants-camlp4-dev 109.15.03-2
  Selecting previously unselected package libvariantslib-ocaml-dev.
  Preparing to unpack .../libvariantslib-ocaml-dev_113.33.03-1_amd64.deb ...
  Unpacking libvariantslib-ocaml-dev (113.33.03-1) ...
  dpkg: error processing archive 
/var/cache/apt/archives/libvariantslib-ocaml-dev_113.33.03-1_amd64.deb 
(--unpack):
   trying to overwrite '/usr/lib/ocaml/variantslib/variantslib.a', which is 
also in package libvariants-camlp4-dev 109.15.03-2
  Errors were encountered while processing:
   /var/cache/apt/archives/libvariantslib-ocaml_113.33.03-1_amd64.deb
   /var/cache/apt/archives/libvariantslib-ocaml-dev_113.33.03-1_amd64.deb


cheers,

Andreas


libvariants-camlp4-dev=109.15.03-2_libvariantslib-ocaml-dev=113.33.03-1.log.gz
Description: application/gzip
--- End Message ---
--- Begin Message ---
Source: variantslib
Source-Version: 113.33.03-2

We believe that the bug you reported is fixed in the latest version of
variantslib, 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.
Stéphane Glondu  (supplier of updated variantslib package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Wed, 17 Aug 2016 14:12:30 +0200
Source: variantslib
Binary: libvariantslib-ocaml-dev libvariantslib-ocaml
Architecture: source amd64
Version: 113.33.03-2
Distribution: unstable
Urgency: medium
Maintainer: Debian OCaml Maintainers 
Changed-By: Stéphane Glondu 
Description:
 libvariantslib-ocaml - OCaml syntax extension for supporting variants as first 
class val
 libvariantslib-ocaml-dev - OCaml syntax extension for supporting variants as 
first class val
Closes: 834075
Changes:
 variantslib (113.33.03-2) unstable; urgency=medium
 .
   * Team upload
   * Upload to unstable
   * Add Breaks/Replaces libvariants-camlp4-dev (Closes: #834075)
   * Move ocaml-findlib to recommends
   * Fix FTBFS on bytecode architectures
Checksums-Sha1:
 759ebc94868b9073de86eb9addeedb9589433a95 2200 variantslib_113.33.03-2.dsc
 678ebd1525df6389fbe8344912be21f77757a7e9 2268 
variantslib_113.33.03-2.debian.tar.xz
 ef034fbe68b916a21734fb2183c77b515f6d885a 2312 
libvariantslib-ocaml-dbgsym_113.33.03-2_amd64.deb
 29534282e486b2d8136b6385ff951ce2fc0a6e19 5862 
libvariantslib-ocaml-dev_113.33.03-2_amd64.deb
 4a12d3babc475ea95e55c87926a9770b3a65c5e4 4488 
libvariantslib-ocaml_113.33.03-2_amd64.deb
Checksums-Sha256:
 dd86ebbdfa3160843290b2ef92c33fb8ff3b24dac0dc289e36c451d1ec5dad23 2200 
variantslib_113.33.03-2.dsc
 

Bug#834071: marked as done (libfieldslib-ocaml{, -dev}: fails to upgrade from 'sid' - trying to overwrite /usr/lib/ocaml/fieldslib/{META, field.annot})

[Debian Bug Tracking System]

Your message dated Wed, 17 Aug 2016 12:19:47 +
with message-id 
and subject line Bug#834071: fixed in fieldslib 113.33.03-2
has caused the Debian Bug report #834071,
regarding libfieldslib-ocaml{, -dev}: fails to upgrade from 'sid' - trying to 
overwrite /usr/lib/ocaml/fieldslib/{META, field.annot}
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.)


-- 
834071: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=834071
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: libfieldslib-ocaml,libfieldslib-ocaml-dev
Version: 113.33.03-1
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

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

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

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

  Selecting previously unselected package libfieldslib-ocaml.
  Preparing to unpack .../libfieldslib-ocaml_113.33.03-1_amd64.deb ...
  Unpacking libfieldslib-ocaml (113.33.03-1) ...
  dpkg: error processing archive 
/var/cache/apt/archives/libfieldslib-ocaml_113.33.03-1_amd64.deb (--unpack):
   trying to overwrite '/usr/lib/ocaml/fieldslib/META', which is also in 
package libfields-camlp4-dev 113.00.00-1
  Selecting previously unselected package libfieldslib-ocaml-dev.
  Preparing to unpack .../libfieldslib-ocaml-dev_113.33.03-1_amd64.deb ...
  Unpacking libfieldslib-ocaml-dev (113.33.03-1) ...
  dpkg: error processing archive 
/var/cache/apt/archives/libfieldslib-ocaml-dev_113.33.03-1_amd64.deb (--unpack):
   trying to overwrite '/usr/lib/ocaml/fieldslib/field.annot', which is also in 
package libfields-camlp4-dev 113.00.00-1
  Errors were encountered while processing:
   /var/cache/apt/archives/libfieldslib-ocaml_113.33.03-1_amd64.deb
   /var/cache/apt/archives/libfieldslib-ocaml-dev_113.33.03-1_amd64.deb


cheers,

Andreas


libfields-camlp4-dev=113.00.00-1_libfieldslib-ocaml-dev=113.33.03-1.log.gz
Description: application/gzip
--- End Message ---
--- Begin Message ---
Source: fieldslib
Source-Version: 113.33.03-2

We believe that the bug you reported is fixed in the latest version of
fieldslib, 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.
Stéphane Glondu  (supplier of updated fieldslib package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Wed, 17 Aug 2016 14:07:26 +0200
Source: fieldslib
Binary: libfieldslib-ocaml-dev libfieldslib-ocaml
Architecture: source amd64
Version: 113.33.03-2
Distribution: unstable
Urgency: medium
Maintainer: Debian OCaml Maintainers 
Changed-By: Stéphane Glondu 
Description:
 libfieldslib-ocaml - OCaml syntax extension that enables folding over record 
fields (r
 libfieldslib-ocaml-dev - OCaml syntax extension that enables folding over 
record fields (d
Closes: 834071
Changes:
 fieldslib (113.33.03-2) unstable; urgency=medium
 .
   * Upload to unstable
   * Add Breaks/Replaces libfields-camlp4-dev (Closes: #834071)
   * Move ocaml-findlib to Recommends
   * Fix FTBFS on bytecode architectures
Checksums-Sha1:
 d322301b5b450fc24eeba2ce747afd505c6d646b 2246 fieldslib_113.33.03-2.dsc
 154230556a980237e57d8d394a3204cc70958d86 2900 
fieldslib_113.33.03-2.debian.tar.xz
 aef11bac8d993454c857cf75f677949786b20f7d 2706 
libfieldslib-ocaml-dbgsym_113.33.03-2_amd64.deb
 f3331a352d43e8a02611bdb94d67a551b43f2643 14526 
libfieldslib-ocaml-dev_113.33.03-2_amd64.deb
 09651164a3177e044c171e2b65774f0650988f78 8476 
libfieldslib-ocaml_113.33.03-2_amd64.deb
Checksums-Sha256:
 29fa857919c86e9d00952fed130a6ede39db47206e677c04f669ac7e7b9964f9 2246 
fieldslib_113.33.03-2.dsc
 ba958d74a44483854503ac3d97d4ad2a9eac7418efdc552154300a1a9d0eb88f 2900 
fieldslib_113.33.03-2.debian.tar.xz
 

Bug#834069: marked as done (libbin-prot-ocaml{, -dev}: fails to upgrade from 'sid' - trying to overwrite /usr/lib/ocaml/bin_prot/{META, bin_prot.a})

[Debian Bug Tracking System]

Your message dated Wed, 17 Aug 2016 14:06:02 +0200
with message-id 
and subject line Re: Bug#834069: libbin-prot-ocaml{, -dev}: fails to upgrade 
from 'sid' - trying to overwrite /usr/lib/ocaml/bin_prot/{META, bin_prot.a}
has caused the Debian Bug report #834069,
regarding libbin-prot-ocaml{, -dev}: fails to upgrade from 'sid' - trying to 
overwrite /usr/lib/ocaml/bin_prot/{META, bin_prot.a}
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.)


-- 
834069: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=834069
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: libbin-prot-ocaml,libbin-prot-ocaml-dev
Version: 113.33.03-1
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

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

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

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

  Selecting previously unselected package libbin-prot-ocaml.
  Preparing to unpack .../libbin-prot-ocaml_113.33.03-1_amd64.deb ...
  Unpacking libbin-prot-ocaml (113.33.03-1) ...
  dpkg: error processing archive 
/var/cache/apt/archives/libbin-prot-ocaml_113.33.03-1_amd64.deb (--unpack):
   trying to overwrite '/usr/lib/ocaml/bin_prot/META', which is also in package 
libbin-prot-camlp4-dev 113.00.00-1
  dpkg-deb: error: subprocess paste was killed by signal (Broken pipe)
  Selecting previously unselected package libbin-prot-ocaml-dev.
  Preparing to unpack .../libbin-prot-ocaml-dev_113.33.03-1_amd64.deb ...
  Unpacking libbin-prot-ocaml-dev (113.33.03-1) ...
  dpkg: error processing archive 
/var/cache/apt/archives/libbin-prot-ocaml-dev_113.33.03-1_amd64.deb (--unpack):
   trying to overwrite '/usr/lib/ocaml/bin_prot/bin_prot.a', which is also in 
package libbin-prot-camlp4-dev 113.00.00-1
  dpkg-deb: error: subprocess paste was killed by signal (Broken pipe)
  Errors were encountered while processing:
   /var/cache/apt/archives/libbin-prot-ocaml_113.33.03-1_amd64.deb
   /var/cache/apt/archives/libbin-prot-ocaml-dev_113.33.03-1_amd64.deb


cheers,

Andreas


libbin-prot-camlp4-dev=113.00.00-1_libbin-prot-ocaml-dev=113.33.03-1.log.gz
Description: application/gzip
--- End Message ---
--- Begin Message ---
Version: 113.33.03-2

Le 11/08/2016 à 20:34, Andreas Beckmann a écrit :
> during a test with piuparts I noticed your package fails to upgrade from
> 'sid' to 'experimental'.
> It installed fine in 'sid', then the upgrade to 'experimental' fails
> because it tries to overwrite other packages files without declaring a
> Breaks+Replaces relation.

Fixed in last upload.

Cheers,

-- 
Stéphane--- End Message ---

Processed: Re: Bug#834163: libmagick++: undefined behavior on concurrent access because mutex locking is poorly done

[Debian Bug Tracking System]

Processing control commands:

> tags -1 security
Bug #834163 [libmagick++-6.q16-5v5] libmagick++: undefined behavior on 
concurrent access because mutex locking is poorly done
Added tag(s) security.
> severity -1 grave
Bug #834163 [libmagick++-6.q16-5v5] libmagick++: undefined behavior on 
concurrent access because mutex locking is poorly done
Severity set to 'grave' from 'important'

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

Bug#811639: marked as done (FTBFS with GCC 6: multiple errors)

[Debian Bug Tracking System]

Your message dated Wed, 17 Aug 2016 11:35:43 +
with message-id 
and subject line Bug#811639: fixed in choreonoid 1.5.0+dfsg-0.1
has caused the Debian Bug report #811639,
regarding FTBFS with GCC 6: multiple errors
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.)


-- 
811639: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=811639
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: choreonoid
Version: 1.1.0+dfsg-6.2
Severity: important
User: debian-...@lists.debian.org
Usertags: ftbfs-gcc-6 gcc-6-cannot-convert gcc-6-reference-ambiguous

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

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

Search for "error:"

> sbuild (Debian sbuild) 0.67.0 (26 Dec 2015) on dl580gen9-02.hlinux
...
> In file included from /usr/include/eigen3/Eigen/Core:298:0,
>  from 
> /<>/choreonoid-1.1.0+dfsg/src/Util/EigenTypes.h:8,
>  from 
> /<>/choreonoid-1.1.0+dfsg/src/Util/MultiAffine3Seq.h:10,
>  from 
> /<>/choreonoid-1.1.0+dfsg/include/cnoid/MultiAffine3Seq:1,
>  from 
> /<>/choreonoid-1.1.0+dfsg/src/Body/BodyMotion.h:10,
>  from 
> /<>/choreonoid-1.1.0+dfsg/src/Body/BodyMotion.cpp:6:
> /usr/include/eigen3/Eigen/src/Core/util/XprHelper.h:148:88: warning: ignoring 
> attributes on template argument 'Eigen::internal::packet_traits::type 
> {aka __vector(4) float}'
>typedef typename find_best_packet_helper packet_traits::type>::type type;
>   
>   ^~~~
> 
> /usr/include/eigen3/Eigen/src/Core/DenseCoeffsBase.h: In instantiation of 
> 'class 
> Eigen::DenseCoeffsBase  const Eigen::Product, 
> Eigen::CwiseBinaryOp Eigen::Matrix, const 
> Eigen::CwiseUnaryOp Eigen::Matrix > >, 0>, const Eigen::Matrix >, 0>':
> /usr/include/eigen3/Eigen/src/Core/util/XprHelper.h:457:8:   required from 
> 'struct 
> Eigen::internal::special_scalar_op_base  const Eigen::Product, 
> Eigen::CwiseBinaryOp Eigen::Matrix, const 
> Eigen::CwiseUnaryOp Eigen::Matrix > >, 0>, const Eigen::Matrix >, 
> double, double, 
> Eigen::DenseCoeffsBase  const Eigen::Product, 
> Eigen::CwiseBinaryOp Eigen::Matrix, const 
> Eigen::CwiseUnaryOp Eigen::Matrix > >, 0>, const Eigen::Matrix >, 0>, 
> false>'
> /usr/include/eigen3/Eigen/src/Core/DenseBase.h:41:34:   required from 'class 
> Eigen::DenseBase const Eigen::Product, 
> Eigen::CwiseBinaryOp Eigen::Matrix, const 
> Eigen::CwiseUnaryOp Eigen::Matrix > >, 0>, const Eigen::Matrix > >'
> /usr/include/eigen3/Eigen/src/Core/MatrixBase.h:48:34:   required from 'class 
> Eigen::MatrixBase  const Eigen::Product, 
> Eigen::CwiseBinaryOp Eigen::Matrix, const 
> Eigen::CwiseUnaryOp Eigen::Matrix > >, 0>, const Eigen::Matrix > >'
> /usr/include/eigen3/Eigen/src/Core/CwiseBinaryOp.h:148:7:   required from 
> 'class Eigen::CwiseBinaryOpImpl Eigen::Product, 
> Eigen::CwiseBinaryOp Eigen::Matrix, const 
> Eigen::CwiseUnaryOp Eigen::Matrix > >, 0>, const Eigen::Matrix, 
> Eigen::Dense>'
> 

Bug#828905: marked as done (youtube-dl: FTBFS: /bin/sh: 1: zip: not found)

[Debian Bug Tracking System]

Your message dated Wed, 17 Aug 2016 10:56:34 +
with message-id 
and subject line Bug#828905: fixed in youtube-dl 2016.06.25-2
has caused the Debian Bug report #828905,
regarding youtube-dl: FTBFS: /bin/sh: 1: zip: not found
to be marked as done.

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

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


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

Dear Maintainer,

youtube-dl fails to build from source in unstable/amd64:

  [..]

  
  
**
  ** Starting build 
  **
  
**
  
   Package:  youtube-dl
   Version:  2016.06.25-1
   Build architecture:   amd64
   Date: Tue, 28 Jun 2016 22:29:30 +0200
   Hostname: 0990dc296c77
   Uname:Linux 0990dc296c77 4.5.0-2-amd64 #1 SMP Debian 4.5.4-1 
(2016-05-16) x86_64 GNU/Linux
   /etc/timezone:Africa/Johannesburg
  
  
**
  ** Installing build dependencies  
  **
  
**
  
  dh_testdir
  dh_testroot
  dh_prep
  dh_testdir
  dh_testroot
  dh_install
  dh_installdocs
  dh_installchangelogs
  dh_compress
  dh_fixperms
  dh_installdeb
  dh_gencontrol
  dh_md5sums
  dh_builddeb
  dpkg-deb: building package 'youtube-dl-build-deps' in 
'../youtube-dl-build-deps_2016.06.25-1_all.deb'.
  
  The package has been created.
  Attention, the package has been created in the current directory,
  not in ".." as indicated by the message above!
  Selecting previously unselected package youtube-dl-build-deps.
  (Reading database ... 23073 files and directories currently installed.)
  Preparing to unpack youtube-dl-build-deps_2016.06.25-1_all.deb ...
  Unpacking youtube-dl-build-deps (2016.06.25-1) ...
  Reading package lists...
  Building dependency tree...
  Reading state information...
  0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
  1 not fully installed or removed.
  After this operation, 0 B of additional disk space will be used.
  Setting up youtube-dl-build-deps (2016.06.25-1) ...
  
  
**
  ** Environment
  **
  
**
  
  
PATH=/home/lamby/git/projects/dotfiles/dotfiles/..//bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin
  HOSTNAME=0990dc296c77
  TERM=xterm
  PAGER=more
  DISPLAY=:0
  DOCKER_IMAGE=lamby-debian-sid
  DEB_BUILD_OPTIONS=parallel=9
  PIP_DOWNLOAD_CACHE=/home/lamby/.cache/pip
  HOME=/home/lamby
  LOGNAME=lamby
  SHLVL=1
  
PWD=/home/lamby/temp/cdt.20160628222929.OWeCoxWrxz.youtube-dl/youtube-dl-2016.06.25
  OLDPWD=/home/lamby/temp/cdt.20160628222929.OWeCoxWrxz.youtube-dl
  GPG_TTY=/dev/console
  QUILT_PATCHES=debian/patches
  QUILT_NO_DIFF_INDEX=1
  QUILT_REFRESH_ARGS=-p ab --no-timestamps --no-index
  DEBEMAIL=la...@debian.org
  DEBFULLNAME=Chris Lamb
  EDITOR=vim
  LESS=-cgiFx4M
  BLASTER=A220 I5 D1 H5 P330 T6
  _=/usr/bin/env
  
  
**
  ** Building youtube-dl 2016.06.25-1 on amd64  
  **
  
**
  
   dpkg-buildpackage -rfakeroot -D -us -uc -b
  dpkg-buildpackage: info: source package youtube-dl
  dpkg-buildpackage: info: source version 2016.06.25-1
  dpkg-buildpackage: info: source distribution unstable
  dpkg-buildpackage: info: source changed by Rogrio Brito 
   dpkg-source --before-build youtube-dl-2016.06.25
  dpkg-buildpackage: info: host architecture amd64
   fakeroot debian/rules clean
  dh clean --with python2 --buildsystem=python_distutils
 dh_testdir -O--buildsystem=python_distutils
 dh_auto_clean -O--buildsystem=python_distutils

Bug#834587: custodia: FTBFS too much often

[Santiago Vila]

Package: custodia
Version: 0.1.0-5
Severity: serious

Dear maintainer:

This package FTBFS half of the time, which is not an acceptable
statistics for a releaseable package. Sure, there is a successful
build log here:

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

but that only means that we were lucky that time, 159 days ago,
it does not mean that the "package builds ok from source".

You will find failed build logs here:

https://tests.reproducible-builds.org/debian/rb-pkg/testing/amd64/custodia.html

but I also attach the failed build logs that I got while checking for
"dpkg-buildpackage -A".

Thanks.

custodia_0.1.0-5_amd64-20160810-1916.gz
Description: application/gzip


custodia_0.1.0-5_amd64-20160817-0119.gz
Description: application/gzip

Bug#834586: libghc-http-dev: Currently not installable

[Hilmar Preuße]

Package: libghc-http-dev
Version: 1:4000.3.3-1
Severity: grave
Justification: renders package unusable

Dear Maintainer,

   * What led up to the situation?

sid:~# apt-get install libghc-http-dev
Reading package lists... Done
Building dependency tree
Reading state information... Done
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:
 libghc-http-dev : Depends: libghc-network-dev-2.6.2.1-bb6bd but it is not 
installable
E: Unable to correct problems, you have held broken packages.

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

Recently a new version of libghc-network-dev has been uploaded and the dep of
libghc-http-dev is quite tight set.

haskell-network (2.6.3.1-1) unstable; urgency=medium

  [ Dmitry Bogatov ]
  * Use secure (https) uri in Vcs-Git field in 'debian/control'
  * Bump standards version to 3.9.8 (no changes needed)

  [ Sean Whitton ]
  * New upstream release

 -- Sean Whitton   Fri, 12 Aug 2016 21:45:16 -0700

Hilmar

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

Kernel: Linux 4.6.0-1-686-pae (SMP w/1 CPU core)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) (ignored: LC_ALL 
set to en_GB.UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: sysvinit (via /sbin/init)

Bug#826446: marked as done (libxslt: New upstream release with multiple security fixes)

[Debian Bug Tracking System]

Your message dated Wed, 17 Aug 2016 10:18:10 +
with message-id 
and subject line Bug#826446: fixed in libxslt 1.1.29-1
has caused the Debian Bug report #826446,
regarding libxslt: New upstream release with multiple security fixes
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.)


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

Hi,

Upstream released a new version with multiple security fixes.

See e.g.

https://git.gnome.org/browse/libxslt/commit/?id=5d0c6565bab5b9b7efceb33b626916d22b4101a7
https://git.gnome.org/browse/libxslt/commit/?id=d8862309f08054218b28e2c8f5fb3cb2f650cac7
https://git.gnome.org/browse/libxslt/commit/?id=91d0540ac9beaa86719a05b749219a69baa0dd8d

And others.

Please update to 1.1.29.

Emilio
--- End Message ---
--- Begin Message ---
Source: libxslt
Source-Version: 1.1.29-1

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

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

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

Debian distribution maintenance software
pp.
YunQiang Su  (supplier of updated libxslt 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, 17 Aug 2016 15:30:11 +0800
Source: libxslt
Binary: libxslt1.1 libxslt1-dev libxslt1-dbg xsltproc python-libxslt1 
python-libxslt1-dbg
Architecture: source amd64
Version: 1.1.29-1
Distribution: unstable
Urgency: medium
Maintainer: Debian XML/SGML Group 
Changed-By: YunQiang Su 
Description:
 libxslt1-dbg - XSLT 1.0 processing library - debugging symbols
 libxslt1-dev - XSLT 1.0 processing library - development kit
 libxslt1.1 - XSLT 1.0 processing library - runtime library
 python-libxslt1 - Python bindings for libxslt1
 python-libxslt1-dbg - Python bindings for libxslt1 (debug extension)
 xsltproc   - XSLT 1.0 command line processor
Closes: 721602 801989 826446
Changes:
 libxslt (1.1.29-1) unstable; urgency=medium
 .
   * Imported Upstream version 1.1.29 (Closes: #826446)
   * Remove patches which have been merged upstream
   * Remove plugin option in xslt-config as it has arch-dep string
   * Link libxslt with libm (Closes: #801989, #721602)
   * Add --parallel in debian/rules.
Checksums-Sha1:
 839592bba3642b2c3b675c4375738109304d4fb8 2008 libxslt_1.1.29-1.dsc
 edcaeabb3555ae44853bdc406ee9521fb65c620d 3428524 libxslt_1.1.29.orig.tar.gz
 4e46475ee559bd90d40361d71b757611a9eade63 27388 libxslt_1.1.29-1.debian.tar.xz
 9007ec72e10a6490f3ae0641b50221a79b4c278f 547160 libxslt1-dbg_1.1.29-1_amd64.deb
 34e9b9190e15cd16eb596eb7e686e00cd8aafb64 513312 libxslt1-dev_1.1.29-1_amd64.deb
 ca557abc801a84f1e51f1688d43e39e0a6f9ec3a 233042 libxslt1.1_1.1.29-1_amd64.deb
 3f0d34d54d53c9152490a92fe720358627b0ced2 241534 
python-libxslt1-dbg_1.1.29-1_amd64.deb
 ed67323429b3a0276641cc903188d3e67983763e 138998 
python-libxslt1_1.1.29-1_amd64.deb
 c5fd33d7c98b606d61dca0a9f8f152f0a92ca9e4 120022 xsltproc_1.1.29-1_amd64.deb
Checksums-Sha256:
 5e338b41be35a2994c546673dee6682303f0849df9a78d4664e6924e4e3eaafd 2008 
libxslt_1.1.29-1.dsc
 b5976e3857837e7617b29f2249ebb5eeac34e249208d31f1fbf7a6ba7a4090ce 3428524 
libxslt_1.1.29.orig.tar.gz
 484c2fe11d32e1d60608c0eb4766140e5c0208385259cdbf9ea08604657f03a9 27388 
libxslt_1.1.29-1.debian.tar.xz
 609ada9916cd19fdb6d3258416d7bad9016c56c24781b3b6538aab3ffc486aeb 547160 
libxslt1-dbg_1.1.29-1_amd64.deb
 7972e4f6fad51d68a11f98d1940f1ce90a42ee211a9374f01118fae26bdab9ce 513312 
libxslt1-dev_1.1.29-1_amd64.deb
 11322fba2bd30ea12cfb1010f013f10a76c74ec10f6ee2da735844b172907602 233042 
libxslt1.1_1.1.29-1_amd64.deb
 f4afd0c60899d71b14920048bce2f736e99b64266c8b3c8b20f3c1b7fa933175 241534 
python-libxslt1-dbg_1.1.29-1_amd64.deb
 809dfb1797674d0190b79fcb0ec771fa1468e370ccd40e28bf634de9428f7561 138998 
python-libxslt1_1.1.29-1_amd64.deb
 801408986b3d485db803690a001513a66522c94e1e143a506e3b77dfebcc0f48 120022 
xsltproc_1.1.29-1_amd64.deb
Files:
 2212b5beaa7b67748cd9f83528c84df4 2008 text optional 

Bug#801989: marked as done (libxslt must be linked with libm)

[Debian Bug Tracking System]

Your message dated Wed, 17 Aug 2016 10:18:10 +
with message-id 
and subject line Bug#801989: fixed in libxslt 1.1.29-1
has caused the Debian Bug report #801989,
regarding libxslt must be linked with libm
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.)


-- 
801989: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=801989
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: libxslt1-dev
Version: 1.1.28-2+b2

Various programs fail to link unless they just happen to specify
"-lm":

 /usr/lib/gcc/x86_64-linux-gnu/5/../../../x86_64-linux-gnu/libxslt.so: error: 
undefined reference to 'pow'
 /usr/lib/gcc/x86_64-linux-gnu/5/../../../x86_64-linux-gnu/libxslt.so: error: 
undefined reference to 'floor'
 /usr/lib/gcc/x86_64-linux-gnu/5/../../../x86_64-linux-gnu/libxslt.so: error: 
undefined reference to 'fmod'
--- End Message ---
--- Begin Message ---
Source: libxslt
Source-Version: 1.1.29-1

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

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

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

Debian distribution maintenance software
pp.
YunQiang Su  (supplier of updated libxslt 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, 17 Aug 2016 15:30:11 +0800
Source: libxslt
Binary: libxslt1.1 libxslt1-dev libxslt1-dbg xsltproc python-libxslt1 
python-libxslt1-dbg
Architecture: source amd64
Version: 1.1.29-1
Distribution: unstable
Urgency: medium
Maintainer: Debian XML/SGML Group 
Changed-By: YunQiang Su 
Description:
 libxslt1-dbg - XSLT 1.0 processing library - debugging symbols
 libxslt1-dev - XSLT 1.0 processing library - development kit
 libxslt1.1 - XSLT 1.0 processing library - runtime library
 python-libxslt1 - Python bindings for libxslt1
 python-libxslt1-dbg - Python bindings for libxslt1 (debug extension)
 xsltproc   - XSLT 1.0 command line processor
Closes: 721602 801989 826446
Changes:
 libxslt (1.1.29-1) unstable; urgency=medium
 .
   * Imported Upstream version 1.1.29 (Closes: #826446)
   * Remove patches which have been merged upstream
   * Remove plugin option in xslt-config as it has arch-dep string
   * Link libxslt with libm (Closes: #801989, #721602)
   * Add --parallel in debian/rules.
Checksums-Sha1:
 839592bba3642b2c3b675c4375738109304d4fb8 2008 libxslt_1.1.29-1.dsc
 edcaeabb3555ae44853bdc406ee9521fb65c620d 3428524 libxslt_1.1.29.orig.tar.gz
 4e46475ee559bd90d40361d71b757611a9eade63 27388 libxslt_1.1.29-1.debian.tar.xz
 9007ec72e10a6490f3ae0641b50221a79b4c278f 547160 libxslt1-dbg_1.1.29-1_amd64.deb
 34e9b9190e15cd16eb596eb7e686e00cd8aafb64 513312 libxslt1-dev_1.1.29-1_amd64.deb
 ca557abc801a84f1e51f1688d43e39e0a6f9ec3a 233042 libxslt1.1_1.1.29-1_amd64.deb
 3f0d34d54d53c9152490a92fe720358627b0ced2 241534 
python-libxslt1-dbg_1.1.29-1_amd64.deb
 ed67323429b3a0276641cc903188d3e67983763e 138998 
python-libxslt1_1.1.29-1_amd64.deb
 c5fd33d7c98b606d61dca0a9f8f152f0a92ca9e4 120022 xsltproc_1.1.29-1_amd64.deb
Checksums-Sha256:
 5e338b41be35a2994c546673dee6682303f0849df9a78d4664e6924e4e3eaafd 2008 
libxslt_1.1.29-1.dsc
 b5976e3857837e7617b29f2249ebb5eeac34e249208d31f1fbf7a6ba7a4090ce 3428524 
libxslt_1.1.29.orig.tar.gz
 484c2fe11d32e1d60608c0eb4766140e5c0208385259cdbf9ea08604657f03a9 27388 
libxslt_1.1.29-1.debian.tar.xz
 609ada9916cd19fdb6d3258416d7bad9016c56c24781b3b6538aab3ffc486aeb 547160 
libxslt1-dbg_1.1.29-1_amd64.deb
 7972e4f6fad51d68a11f98d1940f1ce90a42ee211a9374f01118fae26bdab9ce 513312 
libxslt1-dev_1.1.29-1_amd64.deb
 11322fba2bd30ea12cfb1010f013f10a76c74ec10f6ee2da735844b172907602 233042 
libxslt1.1_1.1.29-1_amd64.deb
 f4afd0c60899d71b14920048bce2f736e99b64266c8b3c8b20f3c1b7fa933175 241534 
python-libxslt1-dbg_1.1.29-1_amd64.deb
 809dfb1797674d0190b79fcb0ec771fa1468e370ccd40e28bf634de9428f7561 138998 
python-libxslt1_1.1.29-1_amd64.deb
 801408986b3d485db803690a001513a66522c94e1e143a506e3b77dfebcc0f48 120022 
xsltproc_1.1.29-1_amd64.deb
Files:
 2212b5beaa7b67748cd9f83528c84df4 2008 text optional libxslt_1.1.29-1.dsc
 

Bug#834251: openmw: FTBFS with GCC 6

[Santiago Vila]

On Tue, 16 Aug 2016, bret curtis wrote:

> We're aware of the problem and version 0.39 has been waiting in the
> upload queue for ages now awaiting someone to upload it. [1] With the
> 0.39 release, it no longer uses unordered maps. We're also about to
> make another release (0.40) shortly... we're just short in people
> willing to upload our packages. :)
> 
> Any takers?

If you prepare a release for unstable (not experimental), maybe I could
upload it. This bug is RC. I think it deserves to be fixed in unstable.

Thanks.

Bug#821471: marked as done (adminer: PHP 7.0 Transition)

[Debian Bug Tracking System]

Your message dated Wed, 17 Aug 2016 10:05:29 +
with message-id 
and subject line Bug#821471: fixed in adminer 4.2.5-2
has caused the Debian Bug report #821471,
regarding adminer: 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.)


-- 
821471: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=821471
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: adminer
Version: 4.2.1-1
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 adminer package currently depends on libapache2-mod-php5 php5 php5-cgi
php5-mysql php5-pgsql php5-sqlite .

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

iQJ8BAEBCgBmBQJXFUpVXxSAAC4AKGlzc3Vlci1mcHJAbm90YXRpb25zLm9w
ZW5wZ3AuZmlmdGhob3JzZW1hbi5uZXQzMEI5MzNEODBGQ0UzRDk4MUEyRDM4RkIw
Qzk5QjcwRUY0RkNCQjA3AAoJEAyZtw70/LsHqLgP/2pkV6n8QtgDt2rnX3txIRuB
9+soQ4s3uolQ2teHOXZe08wiqTt7u9PXPBJLnuPL3EL102aVMF+HDtYxy6Voejnj
0m8EMuHePSejuGqQ2F/wMZQZ54CUf46E2zwZj8SCBc5siwk0Cy0vz+90jGNbDgIg
HkZpdz4Xg/ATZEsgO9aQWMgT8oTJBVJvB6wZeyZi3qTL02i0QWYGmqSAF3xu90Uz

Bug#828037: fontconfig: font-config should not register .dpkg-tmp files in its cache, users ends up seeing squares instead of expected characters

[Raphael Hertzog]

(Keith, I would really like if you could step in, fontconfig
is at its fifth NMU in a row and the sources are not even in
a git packaging repo... I find it highly demotivating to contribute
without any reaction from the package maintainer when I know that
he's not MIA but just ignoring emails)

On Tue, 12 Jul 2016, Raphael Hertzog wrote:
> Please find attached some untested patch. I'm going to test this
> in Kali.

I have been running this patch in Kali and it has had not bad side
effects. I haven't gotten any recent report of similar failure in the last
month so I guess that it does its work as well.

Please integrate my patch. I will likely upload an NMU if I don't hear
anything back in a timely manner (or maybe I'll do a DELAYED upload
immediately).

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: ovirt-guest-agent

[Debian Bug Tracking System]

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

> fixed 782005 ovirt-guest-agent/1.0.11.2.dfsg-1
Bug #782005 [ovirt-guest-agent] ovirt-guest-agent service does not start
Marked as fixed in versions ovirt-guest-agent/1.0.11.2.dfsg-1.
>
End of message, stopping processing here.

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

Processed: ovirt-guest-agent in jessie

[Debian Bug Tracking System]

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

> unarchive 782005
Bug #782005 {Done: Laszlo Boszormenyi (GCS) } 
[ovirt-guest-agent] ovirt-guest-agent service does not start
Unarchived Bug 782005
> reopen 782005
Bug #782005 {Done: Laszlo Boszormenyi (GCS) } 
[ovirt-guest-agent] ovirt-guest-agent service does not start
'reopen' may be inappropriate when a bug has been closed with a version;
all fixed versions will be cleared, and you may need to re-add them.
Bug reopened
No longer marked as fixed in versions ovirt-guest-agent/1.0.11.2.dfsg-1.
> severity 782005 serious
Bug #782005 [ovirt-guest-agent] ovirt-guest-agent service does not start
Severity set to 'serious' from 'normal'
> tags 782005 jessie
Bug #782005 [ovirt-guest-agent] ovirt-guest-agent service does not start
Added tag(s) jessie.
>
End of message, stopping processing here.

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