Bug#835074: How to solve "'float log2(float)' conflicts with a previous declaration"

[Andreas Tille]

Hi,

I tried to fix the issue with the duplicated definition of log2 in
clustalo in Git[1] but failed.  It probably failed since even if I
remove the line that should be excluded by #ifndef HAVE_LOG2 the problem
persists and so I assume there is another log2 definition done
somewhere.

Any ideas?

Kind regards

  Andreas.

[1] 
https://anonscm.debian.org/cgit/debian-med/clustalo.git/tree/debian/patches/log2.patch

-- 
http://fam-tille.de

Bug#835719: monkeysphere: FTBFS: /<>/tests/../src/share/m/subkey_to_ssh_agent: line 123: agent-transfer: command not found

[Daniel Kahn Gillmor]

On Sun 2016-08-28 06:26:24 -0400, Lucas Nussbaum wrote:
>> ##
>> ### ssh connection test for success...
>> # starting ssh server...
>> # starting ssh client...
>> /<>/tests/../src/share/m/subkey_to_ssh_agent: line 123: 
>> agent-transfer: command not found
>> # ssh connection test FAILED. returned: 127, expected: 0
>> FAILED!
>> ### removing temp dir...
>> Makefile:114: recipe for target 'test-basic' failed
>> make[1]: *** [test-basic] Error 1
>> make[1]: Leaving directory '/<>'
>> dh_auto_test: make -j1 test returned exit code 2

looks like the test suite should be setting PATH as well, right?  looks
like this only affects systems where gpg itself is 2.1.x, which is why
the build is now failing when it wasn't when 0.38 was uploaded.

working on a fix...

  --dkg

Processed: tagging 835778

[Debian Bug Tracking System]

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

> tags 835778 + confirmed help
Bug #835778 [src:criu] criu: FTBFS: make[2]: *** No rule to make target 
'images/google/protobuf/descriptor.pb-c.c', needed by 
'images/google/protobuf/descriptor.pb-c.d'.  Stop.
Added tag(s) help and confirmed.
> thanks
Stopping processing here.

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

Bug#835894: terminal.app: crashes on startup: Did not find correct version of backend

[Yavor Doganov]

reassign 835894 libgnustep-gui0.25 0.25.0-2
affects 835894 terminal.app
thanks

Eric Heintzmann wrote:
> Well, it seems that teminal.app doesn't depends on gnustep-back package.
> 
> Instead it depends on libgnustep-gui0.25 which doesn't depends on
> gnustep-back.

That's because of the .symbols file; the .shlibs is not used at all
which makes gnustep-gui's dh_makeshlibs override kind of useless.

Unfortunately it looks like all apps that were rebuilt during the
GNUstep transition are affected.

Yet another good reason to avoid .symbols files for Objective-C
libraries.

Processed: Re: Bug#835894: terminal.app: crashes on startup: Did not find correct version of backend

[Debian Bug Tracking System]

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

> reassign 835894 libgnustep-gui0.25 0.25.0-2
Bug #835894 [terminal.app] missing dependency on gnustep-back
Bug reassigned from package 'terminal.app' to 'libgnustep-gui0.25'.
No longer marked as found in versions terminal.app/0.9.8-1+nmu1.
Ignoring request to alter fixed versions of bug #835894 to the same values 
previously set
Bug #835894 [libgnustep-gui0.25] missing dependency on gnustep-back
Marked as found in versions gnustep-gui/0.25.0-2.
> affects 835894 terminal.app
Bug #835894 [libgnustep-gui0.25] missing dependency on gnustep-back
Added indication that 835894 affects terminal.app
> thanks
Stopping processing here.

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

Processed: your mail

[Debian Bug Tracking System]

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

> tag 835937 + pending
Bug #835937 [src:beets] beets: FTBFS randomly (test_nonexistent_file fails)
Added tag(s) pending.
> thanks
Stopping processing here.

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

Bug#835681: marked as done (python-axolotl: FTBFS: dh_auto_test: pybuild --test -i python{version} -p 2.7 returned exit code 13)

[Debian Bug Tracking System]

Your message dated Tue, 30 Aug 2016 04:20:34 +
with message-id 
and subject line Bug#835681: fixed in python-axolotl 0.1.35-1
has caused the Debian Bug report #835681,
regarding python-axolotl: FTBFS: dh_auto_test: pybuild --test -i 
python{version} -p 2.7 returned exit code 13
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.)


-- 
835681: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=835681
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: python-axolotl
Version: 0.1.7-1
Severity: serious
Tags: stretch sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20160828 qa-ftbfs
Justification: FTBFS on amd64

Hi,

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

Relevant part (hopefully):
>  debian/rules build
> dh build --with python2 --buildsystem=pybuild
>dh_testdir -O--buildsystem=pybuild
>dh_update_autotools_config -O--buildsystem=pybuild
>dh_auto_configure -O--buildsystem=pybuild
> I: pybuild base:184: python2.7 setup.py config 
> running config
>dh_auto_build -O--buildsystem=pybuild
> I: pybuild base:184: /usr/bin/python setup.py build 
> running build
> running build_py
> creating /<>/.pybuild/pythonX.Y_2.7/build/axolotl
> copying axolotl/nosessionexception.py -> 
> /<>/.pybuild/pythonX.Y_2.7/build/axolotl
> copying axolotl/invalidmessageexception.py -> 
> /<>/.pybuild/pythonX.Y_2.7/build/axolotl
> copying axolotl/identitykeypair.py -> 
> /<>/.pybuild/pythonX.Y_2.7/build/axolotl
> copying axolotl/statekeyexchangeexception.py -> 
> /<>/.pybuild/pythonX.Y_2.7/build/axolotl
> copying axolotl/untrustedidentityexception.py -> 
> /<>/.pybuild/pythonX.Y_2.7/build/axolotl
> copying axolotl/legacymessageexception.py -> 
> /<>/.pybuild/pythonX.Y_2.7/build/axolotl
> copying axolotl/duplicatemessagexception.py -> 
> /<>/.pybuild/pythonX.Y_2.7/build/axolotl
> copying axolotl/invalidkeyexception.py -> 
> /<>/.pybuild/pythonX.Y_2.7/build/axolotl
> copying axolotl/identitykey.py -> 
> /<>/.pybuild/pythonX.Y_2.7/build/axolotl
> copying axolotl/__init__.py -> 
> /<>/.pybuild/pythonX.Y_2.7/build/axolotl
> copying axolotl/invalidversionexception.py -> 
> /<>/.pybuild/pythonX.Y_2.7/build/axolotl
> copying axolotl/sessioncipher.py -> 
> /<>/.pybuild/pythonX.Y_2.7/build/axolotl
> copying axolotl/invalidkeyidexception.py -> 
> /<>/.pybuild/pythonX.Y_2.7/build/axolotl
> copying axolotl/sessionbuilder.py -> 
> /<>/.pybuild/pythonX.Y_2.7/build/axolotl
> creating /<>/.pybuild/pythonX.Y_2.7/build/axolotl/kdf
> copying axolotl/kdf/messagekeys.py -> 
> /<>/.pybuild/pythonX.Y_2.7/build/axolotl/kdf
> copying axolotl/kdf/derivedrootsecrets.py -> 
> /<>/.pybuild/pythonX.Y_2.7/build/axolotl/kdf
> copying axolotl/kdf/hkdfv2.py -> 
> /<>/.pybuild/pythonX.Y_2.7/build/axolotl/kdf
> copying axolotl/kdf/derivedmessagesecrets.py -> 
> /<>/.pybuild/pythonX.Y_2.7/build/axolotl/kdf
> copying axolotl/kdf/__init__.py -> 
> /<>/.pybuild/pythonX.Y_2.7/build/axolotl/kdf
> copying axolotl/kdf/hkdfv3.py -> 
> /<>/.pybuild/pythonX.Y_2.7/build/axolotl/kdf
> copying axolotl/kdf/hkdf.py -> 
> /<>/.pybuild/pythonX.Y_2.7/build/axolotl/kdf
> creating /<>/.pybuild/pythonX.Y_2.7/build/axolotl/util
> copying axolotl/util/byteutil.py -> 
> /<>/.pybuild/pythonX.Y_2.7/build/axolotl/util
> copying axolotl/util/hexutil.py -> 
> /<>/.pybuild/pythonX.Y_2.7/build/axolotl/util
> copying axolotl/util/__init__.py -> 
> /<>/.pybuild/pythonX.Y_2.7/build/axolotl/util
> copying axolotl/util/medium.py -> 
> /<>/.pybuild/pythonX.Y_2.7/build/axolotl/util
> copying axolotl/util/keyhelper.py -> 
> /<>/.pybuild/pythonX.Y_2.7/build/axolotl/util
> creating /<>/.pybuild/pythonX.Y_2.7/build/axolotl/tests
> copying axolotl/tests/inmemoryprekeystore.py -> 
> /<>/.pybuild/pythonX.Y_2.7/build/axolotl/tests
> copying axolotl/tests/inmemorysessionstore.py -> 
> /<>/.pybuild/pythonX.Y_2.7/build/axolotl/tests
> copying axolotl/tests/test_sigs.py -> 
> /<>/.pybuild/pythonX.Y_2.7/build/axolotl/tests
> copying axolotl/tests/inmemoryaxolotlstore.py -> 
> /<>/.pybuild/pythonX.Y_2.7/build/axolotl/tests
> copying axolotl/tests/test_sessioncipher.py -> 
> /<>/.pybuild/pythonX.Y_2.7/build/axolotl/tests
> copying axolotl/tests/inmemorysignedprekeystore.py -> 
> /<>/.pybuild/pythonX.Y_2.7/build/axolotl/tests
> copying axolotl/tests/__init__.py -> 
> /<>/.pybuild/pythonX.Y_2.7/build/axolotl/tests
> copying axolotl/tests/test_sessionbuilder.py -> 
> /<>/.pybuild/pythonX.Y_2.7/build/axolotl/tests
> copying axolotl/tests/test_stuff.py -> 
> /<>/.pybuild/pythonX.Y_2.7/build/axolotl/tests
> copying axolotl/tests/inmemoryidentitykeystore.p

Bug#836011: akregator: Akregator keep crashing at exit, sometimes do not save recent feeds

[Ismael]

Package: akregator
Version: 4:16.04.3-1
Severity: grave
Justification: causes non-serious data loss

Dear Maintainer,


   * What led up to the situation?

Since a recent upgrade (less than a month ago). After reading a feed when
closing Akregator it will crash without saving feeds state. The next time it
will load like it didn't fetch any feed.


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

If I remaing in the welcome page I can synchronize without problems, and
Akregator will close correctly.

But If I read a post from a feed or load the list of post in a folder. It will
crash when closing Akregator.


   * What was the outcome of this action?

Run under gdb generates the following stack trace


#0  0x7fffd4079f48 in Akregator::SubscriptionListModel::index(int, int,
QModelIndex const&) const ()
   from /usr/lib/x86_64-linux-gnu/qt5/plugins/akregatorpart.so
#1  0x75dac951 in QTreeView::isRowHidden(int, QModelIndex const&) const
() from /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5
#2  0x75dac9d7 in QTreeView::isIndexHidden(QModelIndex const&) const ()
from /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5
#3  0x75da831c in QTreeView::visualRegionForSelection(QItemSelection
const&) const () from /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5
#4  0x75d6b168 in QAbstractItemView::selectionChanged(QItemSelection
const&, QItemSelection const&) ()
   from /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5
#5  0x75db78da in QTreeView::selectionChanged(QItemSelection const&,
QItemSelection const&) ()
   from /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5
#6  0x75d70750 in
QAbstractItemView::setSelectionModel(QItemSelectionModel*) () from
/usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5
#7  0x75db5977 in QTreeView::setSelectionModel(QItemSelectionModel*) ()
from /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5
#8  0x75d6af45 in QAbstractItemView::setModel(QAbstractItemModel*) ()
from /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5
#9  0x75db5724 in QTreeView::setModel(QAbstractItemModel*) ()
   from /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5
#10 0x7fffd407843d in ?? ()
   from /usr/lib/x86_64-linux-gnu/qt5/plugins/akregatorpart.so
#11 0x7fffd40918bc in ?? ()
   from /usr/lib/x86_64-linux-gnu/qt5/plugins/akregatorpart.so
#12 0x7fffd40bc665 in
Akregator::MainWidget::setFeedList(QSharedPointer const&)
()
   from /usr/lib/x86_64-linux-gnu/qt5/plugins/akregatorpart.so
#13 0x7fffd40bc7ed in Akregator::MainWidget::slotOnShutdown() ()
   from /usr/lib/x86_64-linux-gnu/qt5/plugins/akregatorpart.so
#14 0x7fffd40b2136 in ?? ()
   from /usr/lib/x86_64-linux-gnu/qt5/plugins/akregatorpart.so
#15 0x7fffd40b2908 in ?? ()
   from /usr/lib/x86_64-linux-gnu/qt5/plugins/akregatorpart.so
#16 0x7fffd40b2969 in ?? ()
   from /usr/lib/x86_64-linux-gnu/qt5/plugins/akregatorpart.so
#17 0x74fa6c7c in QMetaObject::activate(QObject*, int, int, void**) ()
from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#18 0x74f7fa13 in QCoreApplication::exec() ()
   from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#19 0x00408828 in ?? ()
#20 0x743dc700 in __libc_start_main (main=0x4081b0, argc=1,
argv=0x7fffe478, init=, fini=,
rtld_fini=, stack_end=0x7fffe468)
at ../csu/libc-start.c:291
#21 0x00408ac9 in _start ()


   * What outcome did you expect instead?

I'd expect that it didn't crash when closing.




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

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

Versions of packages akregator depends on:
ii  kinit5.23.0-1
ii  kio  5.23.0-1
ii  libc62.23-5
ii  libgcc1  1:6.1.1-11
ii  libkf5codecs55.23.0-1
ii  libkf5completion55.23.0-1
ii  libkf5configcore55.23.0-1
ii  libkf5configgui5 5.23.0-1
ii  libkf5configwidgets5 5.23.0-1
ii  libkf5coreaddons55.23.0-1
ii  libkf5grantleetheme-plugins  16.04.3-1
ii  libkf5grantleetheme5 16.04.3-1
ii  libkf5i18n5  5.23.0-1
ii  libkf5iconthemes55.23.0-1
ii  libkf5jobwidgets55.23.0-1
ii  libkf5kcmutils5  5.23.0-1
ii  libkf5kiocore5   5.23.0-1
ii  libkf5kiogui55.23.0-1
ii  libkf5kiowidgets55.23.0-1
ii  libkf5kontactinterface5  16.04.2-1
ii  libkf5libkdepim-plugins  4:16.04.2-3
ii  libkf5libkdepim5 4:16.04.2-3
ii  libkf5messageviewer5 4:16.04.3-2
ii  libkf5notifications5 5.23.0-1
ii  libkf5notifyconfig5  5.23.0-1
ii  libkf5parts5 5.23.0-1
ii  libkf5pim

Processed (with 5 errors): your mail

[Debian Bug Tracking System]

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

> reassign 835271 python-axolotl
Bug #835271 [python-protobuf] python-protobuf returns " TypeError: Descriptors 
should not be created directly, but only retrieved from their parent" message
Bug reassigned from package 'python-protobuf' to 'python-axolotl'.
No longer marked as found in versions protobuf/3.0.0-1.
Ignoring request to alter fixed versions of bug #835271 to the same values 
previously set
> merge 835271 835681
Bug #835271 [python-axolotl] python-protobuf returns " TypeError: Descriptors 
should not be created directly, but only retrieved from their parent" message
Unable to merge bugs because:
severity of #835681 is 'serious' not 'important'
package of #835681 is 'src:python-axolotl' not 'python-axolotl'
Failed to merge 835271: Did not alter merged bugs.

> ---
Unknown command or malformed arguments to command.
> Josue Ortega
Unknown command or malformed arguments to command.
> «Happy Hacking»
Unknown command or malformed arguments to command.
> http://josueortega.org
Unknown command or malformed arguments to command.
>
End of message, stopping processing here.

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

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

[Debian Bug Tracking System]

Your message dated Tue, 30 Aug 2016 00:49:13 +
with message-id 
and subject line Bug#831931: fixed in html2wml 0.4.11-1.2
has caused the Debian Bug report #831931,
regarding html2wml: 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.)


-- 
831931: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=831931
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: html2wml
Version: 0.4.11-1.1
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):
> make[1]: Entering directory '/<>'
> Skipping checkconfig.pl for Debian package.
> install -m 555 html2wml.cgi 
> /<>/debian/html2wml/usr/lib/cgi-bin//html2wml
> make[1]: Leaving directory '/<>'
>  dpkg-genchanges --build=all >../html2wml_0.4.11-1.1_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/html2wml_0.4.11-1.1_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: html2wml
Source-Version: 0.4.11-1.2

We believe that the bug you reported is fixed in the latest version of
html2wml, 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.
Axel Beckert  (supplier of updated html2wml 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: Sat, 27 Aug 2016 19:50:03 +0200
Source: html2wml
Binary: html2wml
Architecture: source all
Version: 0.4.11-1.2
Distribution: unstable
Urgency: medium
Maintainer: Werner Heuser 
Changed-By: Axel Beckert 
Description:
 html2wml   - converts HTML pages to WML (WAP) or i-mode pages
Closes: 831931 835623
Changes:
 html2wml (0.4.11-1.2) unstable; urgency=medium
 .
   * Non-maintainer upload
   * Swap binary-* targets to fix FTBFS with "dpkg-buildpackage -A". Patch
 by Santiago Vila. (Closes: #831931)
   * Add missing dependency on libcgi-pm-perl. (Closes: #835623)
Checksums-Sha1:
 f1b814e1de1ca1f1e656d934c44fe9cf4f039d05 1615 html2wml_0.4.11-1.2.dsc
 a7b8f11d77a9b45d27e07d8fcd49432dff90ba89 3325 html2wml_0.4.11-1.2.diff.gz
 bf86700502039d6930797210c871be0aac3668ea 88668 html2wml_0.4.11-1.2_all.deb
Checksums-Sha256:
 0175b331877de7993802c55e353ed57c02e92a86073576459c70ddfaec4b8ea1 1615 
html2wml_0.4.11-1.2.dsc
 7f39cd4dd336d0e9417f157167a614ec64dd40f1ba90d137e323c5e401516bd6 3325 
html2wml_0.4.11-1.2.diff.gz
 89a7c87fb01fe54067c251ad46e0f5081c5c674965e3

Bug#835623: marked as done (html2wml: Missing run-time dependency on libcgi-pm-perl)

[Debian Bug Tracking System]

Your message dated Tue, 30 Aug 2016 00:49:13 +
with message-id 
and subject line Bug#835623: fixed in html2wml 0.4.11-1.2
has caused the Debian Bug report #835623,
regarding html2wml: Missing run-time dependency on libcgi-pm-perl
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.)


-- 
835623: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=835623
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: html2wml
Version: 0.4.11-1.1
Severity: serious

Dear Werner,

in Sid and Stretch, the perl package no more contains CGI.pm (as it has
been removed upstream from Perl's core), hence html2wml now needs an
additional run-time dependency on libcgi-pm-perl.

Unfortunately I didn't notice this issue before uploading my NMU to
DELAYED/2. I've cancelled my previous upload and will upload a new one
including a fix for this issue to e.g. DELAYED/10 instead.

-- System Information:
Debian Release: stretch/sid
  APT prefers unstable
  APT policy: (990, 'unstable'), (600, 'testing'), (500, 'unstable-debug'), 
(500, 'buildd-unstable'), (110, 'experimental'), (1, 'experimental-debug'), (1, 
'buildd-experimental')
Architecture: amd64 (x86_64)

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

Versions of packages html2wml depends on:
ii  libhtml-parser-perl3.72-2
ii  libtext-template-perl  1.46-1
ii  liburi-perl1.71-1
ii  libwww-perl6.15-1
ii  perl   5.22.2-3

Versions of packages html2wml recommends:
pn  httpd | httpd-cgi   
ii  libxml-parser-perl  2.44-2
ii  tidy1:5.2.0-2

Versions of packages html2wml suggests:
ii  iceweasel  45.3.0esr-1
ii  wap-wml-tools  0.0.4-7
ii  wapua  0.06.2-1

-- no debconf information
--- End Message ---
--- Begin Message ---
Source: html2wml
Source-Version: 0.4.11-1.2

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

Debian distribution maintenance software
pp.
Axel Beckert  (supplier of updated html2wml 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: Sat, 27 Aug 2016 19:50:03 +0200
Source: html2wml
Binary: html2wml
Architecture: source all
Version: 0.4.11-1.2
Distribution: unstable
Urgency: medium
Maintainer: Werner Heuser 
Changed-By: Axel Beckert 
Description:
 html2wml   - converts HTML pages to WML (WAP) or i-mode pages
Closes: 831931 835623
Changes:
 html2wml (0.4.11-1.2) unstable; urgency=medium
 .
   * Non-maintainer upload
   * Swap binary-* targets to fix FTBFS with "dpkg-buildpackage -A". Patch
 by Santiago Vila. (Closes: #831931)
   * Add missing dependency on libcgi-pm-perl. (Closes: #835623)
Checksums-Sha1:
 f1b814e1de1ca1f1e656d934c44fe9cf4f039d05 1615 html2wml_0.4.11-1.2.dsc
 a7b8f11d77a9b45d27e07d8fcd49432dff90ba89 3325 html2wml_0.4.11-1.2.diff.gz
 bf86700502039d6930797210c871be0aac3668ea 88668 html2wml_0.4.11-1.2_all.deb
Checksums-Sha256:
 0175b331877de7993802c55e353ed57c02e92a86073576459c70ddfaec4b8ea1 1615 
html2wml_0.4.11-1.2.dsc
 7f39cd4dd336d0e9417f157167a614ec64dd40f1ba90d137e323c5e401516bd6 3325 
html2wml_0.4.11-1.2.diff.gz
 89a7c87fb01fe54067c251ad46e0f5081c5c674965e3e6d9fce9af4bdc723a6a 88668 
html2wml_0.4.11-1.2_all.deb
Files:
 a6422d5c4b3c33edfaff82a9e4b23799 1615 web optional html2wml_0.4.11-1.2.dsc
 b4ccb82cf32572347514f006603a65b6 3325 web optional html2wml_0.4.11-1.2.diff.gz
 bb161f547eeb7a9d52861b9a3c0874c3 88668 web optional html2wml_0.4.11-1.2_all.deb

-BEGIN PGP SIGNATURE-

iQIcBAEBCAAGBQJXwdMWAAoJEGvmY8daNcl1OkcP/j+GbQvyAQkkZqA4sNg2rNEd
+gtSlkGBgQFWXpMcatFGInEO4AFM7HBLXIMjKM5WfahTdTKbTzDApSlybdRX+TQB
S9kwVtkR6/e0jdqChILdSSLUwRAhowsypjRZBW2RYpCIelEUZ2NMGtsLYLueQI27
va1Ald80CEHa/wMQ3tj/LtoNOXxgyXWqK1XqX2dWg5FzmsRBwN0EIZJxQiv6ZSiJ
LRqo/lrh3HgtX2GLRH2Y6N+/hdBhkTMPNjNWfiDFm01oDQqdPDZhBTtaZzoeqdBv
oji4ZHFOnBabJLj1Sfuu/rE1qz9LotMcFTh8if+sIXkSgLHZHZSEwH4S8Z26Poma
O0PMc8sTzndQzbm6LNz+IuA5wTOvyF9LxkyA9iDsOPkEV6oWC79sJtRJ+D2ae29k
+gQW/K33lRsvNRrCcrD4MTFtunsvcN7yU/bq

Bug#708956: [Bug-jwhois] Bug#708956: Bug#708956: [jwhois] GFDL non free license

[Mathieu Lirzin]

Hello,

Mathieu Lirzin  writes:

> Yuan-Chen Cheng  writes:
>
>> Shall we just remove those two file from the install list and live
>> with that ?
>>
>> I am interested to provide patch to do that if that’s the possible and
>> legal way to do.
[...]
> IIUC correctly the issue is that the license notice in Jwhois 4.0 manual is
>
> Permission is granted to copy, distribute and/or modify this document
> under the terms of the GNU Free Documentation License, Version 1.1 or
> any later version published by the Free Software Foundation; with no
> Invariant Sections, with the Front-Cover Texts being ``A GNU Manual,''
> and with the Back-Cover Texts as in (a) below.  A copy of the
> license is included in the section entitled ``GNU Free Documentation
> License.''
>
> (a) The FSF's Back-Cover Text is: ``You have freedom to copy and modify
> this GNU Manual, like GNU software.  Copies published by the Free
> Software Foundation raise funds for GNU development.''
>
> which requires the FSF back-cover text.  Without this requirement the
> manual could be distributed as in Debian main.  Like what is done with
> GNU Automake manual which license is:
>
> Permission is granted to copy, distribute and/or modify this document
> under the terms of the GNU Free Documentation License,
> Version 1.3 or any later version published by the Free Software
> Foundation; with no Invariant Sections, with no Front-Cover texts,
> and with no Back-Cover Texts.  A copy of the license is included in the
> section entitled ``GNU Free Documentation License.''
>
> So to recap the situation, as a recent Jwhois contributor I have already
> modified (in the development repository) the license of Jwhois to match
> the one from Automake.  I will check with the FSF if they are OK with
> that.

The FSF is not willing to adapt its licenses to comply with Debian
Policy until a compromise between Debian and the FSF is negotiated on
the general GFDL issue.

This means that I have reverted my change in JWhois development
repository which mistakenly has removed the Front-Cover and Back-Cover
texts. As a consequence the current issue will remain valid in the next
JWhois release.

So in the short term, the best way to solve this issue would be to move
the manual from JWhois into a separate package 'jwhois-doc' in Debian
"non-free" repository, like what is done for GNU Bison.

Thanks.

-- 
Mathieu Lirzin

Processed: severity of 835049 is important

[Debian Bug Tracking System]

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

> severity 835049 important
Bug #835049 [src:deluge] deluge is not libtorrent 1.1.0 capable
Severity set to 'important' from 'grave'
> thanks
Stopping processing here.

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

Bug#835937: beets: FTBFS randomly (test_nonexistent_file fails)

[Stefano Rivera]

Hi Santiago (2016.08.29_06:44:11_-0700)
> The failure happens randomly: It always happen in a certain
> autobuilder I have, and it does never happen on the others.

Yeah I saw this when I uploaded to the archive, and have been meaning to
dig deeper.

Thanks for doing the legwork :)

SR

-- 
Stefano Rivera
  http://tumbleweed.org.za/
  +1 415 683 3272

Bug#835713: marked as done (safecat: FTBFS: sed: -e expression #1, char 43: unknown option to `s')

[Debian Bug Tracking System]

Your message dated Mon, 29 Aug 2016 22:33:41 +
with message-id 
and subject line Bug#835713: fixed in safecat 1.13-3
has caused the Debian Bug report #835713,
regarding safecat: FTBFS: sed: -e expression #1, char 43: unknown option to `s'
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.)


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

Hi,

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

Relevant part (hopefully):
>  debian/rules build
> dh build
>dh_testdir
>dh_update_autotools_config
>debian/rules override_dh_auto_configure
> make[1]: Entering directory '/<>'
> sed -i -e "s/cc \(.*\)/cc -g -O2 -fdebug-prefix-map=/<>=. 
> -fstack-protector-strong -Wformat -Werror=format-security 
> -D_LARGEFILE64_SOURCE \1/" conf-cc
> sed: -e expression #1, char 43: unknown option to `s'
> debian/rules:9: recipe for target 'override_dh_auto_configure' failed
> make[1]: *** [override_dh_auto_configure] Error 1

The full build log is available from:
   http://people.debian.org/~lucas/logs/2016/08/28/safecat_1.13-2_unstable.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: safecat
Source-Version: 1.13-3

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

Debian distribution maintenance software
pp.
Teemu Hukkanen  (supplier of updated safecat package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Mon, 29 Aug 2016 23:12:39 +0200
Source: safecat
Binary: safecat
Architecture: source amd64
Version: 1.13-3
Distribution: unstable
Urgency: medium
Maintainer: Teemu Hukkanen 
Changed-By: Teemu Hukkanen 
Description:
 safecat- Safely copy stdin to a file
Closes: 829720 835713
Changes:
 safecat (1.13-3) unstable; urgency=medium
 .
   * Make build reproducible (Closes: #829720)
   * Bump Standards-Version to 3.9.8
   * Update packaging copyright years
   * Add short name to license block in copyright file
   * Use a non-conflicting regexp separator (Closes: #835713)
   * Unapply patches from source
   * Restore conf-(cc|ld) on clean target
Checksums-Sha1:
 56be5223d3be8d38bdc11972c569bb0fc34f422f 1704 safecat_1.13-3.dsc
 25f4e88f6c8dd8b3a1b9856fcaf6b9076927be7c 5652 safecat_1.13-3.debian.tar.xz
 a4299ee29854d1dce431c64c46be6ee7d116 19390 safecat-dbgsym_1.13-3_amd64.deb
 aab1c04416847e7ef381c19f0044df037b6f07ce 19156 safecat_1.13-3_amd64.deb
Checksums-Sha256:
 428f2c7ec6003280a376179269ad4a82f606cd0cbf8362b2a660155ce498ff25 1704 
safecat_1.13-3.dsc
 68e4a9a6b1cef832490bb695dbd27f751ee77bdfce6ccf4f66cac5b74860e9c2 5652 
safecat_1.13-3.debian.tar.xz
 5de9156184637f2371ad0310d4cdbc91e02773b41172f1a113b31ba7fb3cfcad 19390 
safecat-dbgsym_1.13-3_amd64.deb
 b29da581914b471feee239c0fef6c575877b196428b4ced5b60b3b012f2475c4 19156 
safecat_1.13-3_amd64.deb
Files:
 edab554e484896cb88c11e1d8fa638c5 1704 utils optional safecat_1.13-3.dsc
 3557268a0c55666173b39cc6896029b4 5652 utils optional 
safecat_1.13-3.debian.tar.xz
 0064c39bf2057fdb4d02c68580da302f 19390 debug extra 
safecat-dbgsym_1.13-3_amd64.deb
 d6b8535cc0a5429581dfbd984a570e0b 19156 utils optional safecat_1.13-3_amd64.deb

-BEGIN PGP SIGNATURE-
Version: GnuPG v1

iQIcBAEBCgAGBQJXxKr9AAoJEFNtV0icIAHQY7kQAIZQ4adXle2tu6mgb1Iy8MH0
iGCZeK70L1NpYe0yQgzM3Y6MFtzXhJZUpaptpebUX1mxxQ9NOg4EnRvGFzYAwhIJ
v+0y67fCK6mFOA6BAPRp39hlL9PRGTaoOk32xDmR8cgYbvkd5wKeKV9lLzpAmDa4
68KeZgUybA7Zd5oVljJ6o4X9pfLWpgVFhf4KsVcdx5/h0sg678e1GQJZ47KTa2Wz
Lvol90qrmmJGUwTR3Bz9OEoqsVdlvS0o7yST0Z

Bug#830428: marked as done (sweethome3d-furniture-editor: FTBFS: [javac] /«PKGBUILDDIR»/src/com/eteks/furniturelibraryeditor/swing/FurniturePanel.java:900: error: cannot access Localizable)

[Debian Bug Tracking System]

Your message dated Mon, 29 Aug 2016 22:34:03 +
with message-id 
and subject line Bug#830428: fixed in sweethome3d-furniture-editor 1.15-2
has caused the Debian Bug report #830428,
regarding sweethome3d-furniture-editor: FTBFS: [javac] 
/«PKGBUILDDIR»/src/com/eteks/furniturelibraryeditor/swing/FurniturePanel.java:900:
 error: cannot access Localizable
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.)


-- 
830428: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=830428
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: sweethome3d-furniture-editor
Version: 1.15-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[1]: Entering directory '/«PKGBUILDDIR»'
> mkdir -p build/classes-sh3d
> unzip -q /usr/share/sweethome3d/sweethome3d.jar -d build/classes-sh3d
> dh_auto_build
>   ant -Duser.name debian
> Buildfile: /«PKGBUILDDIR»/build.xml
> 
> furnitureLibraryEditor:
> [mkdir] Created dir: /«PKGBUILDDIR»/build/classes
> [javac] /«PKGBUILDDIR»/build.xml:36: warning: 'includeantruntime' was not 
> set, defaulting to build.sysclasspath=last; set to false for repeatable builds
> [javac] Compiling 23 source files to /«PKGBUILDDIR»/build/classes
> [javac] 
> [javac]   WARNING
> [javac] 
> [javac] The -source switch defaults to 1.8 in JDK 1.8.
> [javac] If you specify -target 1.5 you now must also specify -source 1.5.
> [javac] Ant will implicitly add -source 1.5 for you.  Please change your 
> build file.
> [javac] warning: [options] bootstrap class path not set in conjunction 
> with -source 1.5
> [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] 
> /«PKGBUILDDIR»/src/com/eteks/furniturelibraryeditor/swing/FurniturePanel.java:900:
>  error: cannot access Localizable
> [javac]   pathParser.setPathHandler(new 
> AWTPathProducer());
> [javac] ^
> [javac]   class file for org.apache.batik.i18n.Localizable not found
> [javac] Note: Some input files use unchecked or unsafe operations.
> [javac] Note: Recompile with -Xlint:unchecked for details.
> [javac] 1 error
> [javac] 4 warnings
> 
> BUILD FAILED
> /«PKGBUILDDIR»/build.xml:36: Compile failed; see the compiler error output 
> for details.
> 
> Total time: 2 seconds
> dh_auto_build: ant -Duser.name debian returned exit code 1
> make[1]: *** [override_dh_auto_build] Error 2

The full build log is available from:
   
http://people.debian.org/~lucas/logs/2016/07/07/sweethome3d-furniture-editor_1.15-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: sweethome3d-furniture-editor
Source-Version: 1.15-2

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

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Mon, 29 Aug 2016 21:58:08 +0200
Source: sweethome3d-furniture-editor
Binary: sweethome3d-furniture-editor
Architecture: source
Version: 1.15-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Java Maintainers 

Changed-By: Markus Koschany 
Description:
 sweethome3d-furnit

Bug#835494: marked as done (spamassassin: FTBFS with '.' removed from perl's @INC)

[Debian Bug Tracking System]

Your message dated Mon, 29 Aug 2016 22:33:58 +
with message-id 
and subject line Bug#835494: fixed in spamassassin 3.4.1-5
has caused the Debian Bug report #835494,
regarding spamassassin: FTBFS with '.' removed from perl's @INC
to be marked as done.

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

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


-- 
835494: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=835494
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: spamassassin
Version: 3.4.1-4
Severity: important
User: debian-p...@lists.debian.org
Usertags: perl-cwd-inc-removal
Tags: patch

This package FTBFS when '.' is removed from @INC, as seen at [1].
This change is being made for security reasons; for more background,
see #588017 and [2]. Please see the attached patch which fixes this.

This bug will become RC when the perl package change removing '.' from
@INC by default is uploaded to unstable, expected in a week or two.

Thanks,
Dominic.

[1] 

[2] 
diff -urN spamassassin-3.4.1.orig/spamc/configure.pl spamassassin-3.4.1/spamc/configure.pl
--- spamassassin-3.4.1.orig/spamc/configure.pl	2015-04-28 20:56:59.0 +0100
+++ spamassassin-3.4.1/spamc/configure.pl	2016-08-26 11:31:59.521602138 +0100
@@ -66,7 +66,7 @@
   # Do the same thing as for the preprocessor below.
   package version_h;
   my $Z = $0;
-  local $0= "version.h.pl";
+  local $0= "./version.h.pl";
   local @ARGV = ();
   # Got to check for defined because the script returns shell error level!
   unless (defined do $0) {
--- End Message ---
--- Begin Message ---
Source: spamassassin
Source-Version: 3.4.1-5

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

Debian distribution maintenance software
pp.
Noah Meyerhans  (supplier of updated spamassassin package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Mon, 29 Aug 2016 14:14:31 -0700
Source: spamassassin
Binary: spamassassin spamc sa-compile
Architecture: source all amd64
Version: 3.4.1-5
Distribution: unstable
Urgency: medium
Maintainer: Noah Meyerhans 
Changed-By: Noah Meyerhans 
Description:
 sa-compile - Tools for compiling SpamAssassin rules into C
 spamassassin - Perl-based spam filter using text analysis
 spamc  - Client for SpamAssassin spam filtering daemon
Closes: 831872 835494
Changes:
 spamassassin (3.4.1-5) unstable; urgency=medium
 .
   * Fix "FTBFS with '.' removed from perl's @INC" with patch from
 Dominic Hargreaves  (Closes: #835494)
   * Fix "fails to install: error: gpg required but not found!" by
 making gpg usage optional. (Closes: #831872)
Checksums-Sha1:
 a5608037f3f0e11350471aa7cba2d9acc41189d4 2387 spamassassin_3.4.1-5.dsc
 1393899597fb91b05ac4eb9505b2bc06978d0fca 40624 
spamassassin_3.4.1-5.debian.tar.xz
 1d5fcaa36639e3f566b36b69d1dc42ce4a4e6263 53502 sa-compile_3.4.1-5_all.deb
 13aac7a0f3d4eefc42faf7fa7210848b1a5c3a05 1101422 spamassassin_3.4.1-5_all.deb
 79a355000db37dd21b8a8518df82d139f9663825 64636 spamc-dbgsym_3.4.1-5_amd64.deb
 18fa880206a6299bd53c250fac650c0678efabad 88412 spamc_3.4.1-5_amd64.deb
Checksums-Sha256:
 bd142abe347b004040f524b645686ca9cf1d90478f677ddbdb5a7e49b1612eff 2387 
spamassassin_3.4.1-5.dsc
 47b7aff65c424ced849ac8a563d0653ea3a7087422037f650d7dbafad826ad79 40624 
spamassassin_3.4.1-5.debian.tar.xz
 5501f998902edf5b633b0d6100d6db3ec5a4c4383b6c857d349b8f0286cd0091 53502 
sa-compile_3.4.1-5_all.deb
 3b5da0cc20c9298a2a9f0dbda36e3646cc87c53aaeb70652c66d576bf384a6c3 1101422 
spamassassin_3.4.1-5_all.deb
 56e92cd7d798aee00953d808dba42f99785225b8856b6d7c1d403aa5f9f8dcaa 64636 
spamc-dbgsym_3.4.1-5_amd64.deb
 8b3c4cbe0ff68034a344b57a1ce861be4664a22101f973118cf14bbfea15bc3f 88412 
spamc_3.4.1-5_amd64.deb
Files:
 3a8413522d1cb49da895797502403505 2387 mail optional spamassassin_3.4.1-5.dsc
 307fadd5835b5d8db60868f43755397a 40624 mail optional 
spamassassin_3.4.1-5.debian.tar.xz
 ac5581f9d3b78e184e0cd67600

Bug#835575: marked as done (ros-pcl-msgs: FTBFS in testing (configure fails))

[Debian Bug Tracking System]

Your message dated Mon, 29 Aug 2016 22:33:30 +
with message-id 
and subject line Bug#835575: fixed in ros-pcl-msgs 0.2.0-5
has caused the Debian Bug report #835575,
regarding ros-pcl-msgs: FTBFS in testing (configure fails)
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.)


-- 
835575: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=835575
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:ros-pcl-msgs
Version: 0.2.0-4
Severity: serious

Dear maintainer:

I tried to build this package in stretch 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 --buildsystem=cmake --with python2
   dh_testdir -i -O--parallel -O--buildsystem=cmake
   dh_update_autotools_config -i -O--parallel -O--buildsystem=cmake
   dh_auto_configure -i -O--parallel -O--buildsystem=cmake
cmake .. -DCMAKE_INSTALL_PREFIX=/usr -DCMAKE_VERBOSE_MAKEFILE=ON 
-DCMAKE_BUILD_TYPE=None -DCMAKE_INSTALL_SYSCONFDIR=/etc 
-DCMAKE_INSTALL_LOCALSTATEDIR=/var
-- The C compiler identification is GNU 6.1.1
-- The CXX compiler identification is GNU 6.1.1
-- Check for working C compiler: /usr/bin/cc
-- Check for working C compiler: /usr/bin/cc -- works
-- Detecting C compiler ABI info
-- Detecting C compiler ABI info - done
-- Detecting C compile features

[... snipped ...]

CMAKE_SKIP_INSTALL_RPATH-ADVANCED:INTERNAL=1
//ADVANCED property for variable: CMAKE_SKIP_RPATH
CMAKE_SKIP_RPATH-ADVANCED:INTERNAL=1
//ADVANCED property for variable: CMAKE_STATIC_LINKER_FLAGS
CMAKE_STATIC_LINKER_FLAGS-ADVANCED:INTERNAL=1
//ADVANCED property for variable: CMAKE_STATIC_LINKER_FLAGS_DEBUG
CMAKE_STATIC_LINKER_FLAGS_DEBUG-ADVANCED:INTERNAL=1
//ADVANCED property for variable: CMAKE_STATIC_LINKER_FLAGS_MINSIZEREL
CMAKE_STATIC_LINKER_FLAGS_MINSIZEREL-ADVANCED:INTERNAL=1
//ADVANCED property for variable: CMAKE_STATIC_LINKER_FLAGS_RELEASE
CMAKE_STATIC_LINKER_FLAGS_RELEASE-ADVANCED:INTERNAL=1
//ADVANCED property for variable: CMAKE_STATIC_LINKER_FLAGS_RELWITHDEBINFO
CMAKE_STATIC_LINKER_FLAGS_RELWITHDEBINFO-ADVANCED:INTERNAL=1
//ADVANCED property for variable: CMAKE_STRIP
CMAKE_STRIP-ADVANCED:INTERNAL=1
//uname command
CMAKE_UNAME:INTERNAL=/bin/uname
//ADVANCED property for variable: CMAKE_VERBOSE_MAKEFILE
CMAKE_VERBOSE_MAKEFILE-ADVANCED:INTERNAL=1
//Details about finding PythonInterp
FIND_PACKAGE_MESSAGE_DETAILS_PythonInterp:INTERNAL=[/usr/bin/python][v2.7.12()]
//Details about finding Threads
FIND_PACKAGE_MESSAGE_DETAILS_Threads:INTERNAL=[TRUE][v()]
GTEST_FROM_SOURCE_FOUND:INTERNAL=TRUE
GTEST_FROM_SOURCE_INCLUDE_DIRS:INTERNAL=/usr/include
GTEST_FROM_SOURCE_LIBRARIES:INTERNAL=gtest
GTEST_FROM_SOURCE_LIBRARY_DIRS:INTERNAL=/<>/obj-x86_64-linux-gnu/gtest
GTEST_FROM_SOURCE_MAIN_LIBRARIES:INTERNAL=gtest_main
//ADVANCED property for variable: GTEST_INCLUDE_DIR
GTEST_INCLUDE_DIR-ADVANCED:INTERNAL=1
//ADVANCED property for variable: GTEST_LIBRARY
GTEST_LIBRARY-ADVANCED:INTERNAL=1
//ADVANCED property for variable: GTEST_LIBRARY_DEBUG
GTEST_LIBRARY_DEBUG-ADVANCED:INTERNAL=1
//ADVANCED property for variable: GTEST_MAIN_LIBRARY
GTEST_MAIN_LIBRARY-ADVANCED:INTERNAL=1
//ADVANCED property for variable: GTEST_MAIN_LIBRARY_DEBUG
GTEST_MAIN_LIBRARY_DEBUG-ADVANCED:INTERNAL=1
//ADVANCED property for variable: PYTHON_EXECUTABLE
PYTHON_EXECUTABLE-ADVANCED:INTERNAL=1
//This needs to be in PYTHONPATH when 'setup.py install' is called.
//  And it needs to match.  But setuptools won't tell us where
// it will install things.
PYTHON_INSTALL_DIR:INTERNAL=lib/python2.7/dist-packages
//CMAKE_INSTALL_PREFIX during last run
_GNUInstallDirs_LAST_CMAKE_INSTALL_PREFIX:INTERNAL=/usr

dh_auto_configure: cmake .. -DCMAKE_INSTALL_PREFIX=/usr 
-DCMAKE_VERBOSE_MAKEFILE=ON -DCMAKE_BUILD_TYPE=None 
-DCMAKE_INSTALL_SYSCONFDIR=/etc -DCMAKE_INSTALL_LOCALSTATEDIR=/var returned 
exit code 1
debian/rules:6: recipe for target 'build-indep' failed
make: *** [build-indep] Error 255
dpkg-buildpackage: error: debian/rules build-indep gave error exit status 2


Sorry, I have no idea why it fails, but the failure is reproducible easily.

Once you fix this, I would recommend that you try uploading this in
source-only form, then we will get pretty official build logs in
buildd.debian.org.

Thanks.
--- End Message ---
--- Begin Message ---
Source: ros-pcl-msgs
Source-Version: 0.2.0-5

We believe that the bug you reported is fixed i

Bug#835576: marked as done (ros-ros-comm-msgs: FTBFS in testing (configure fails))

[Debian Bug Tracking System]

Your message dated Mon, 29 Aug 2016 22:33:35 +
with message-id 
and subject line Bug#835576: fixed in ros-ros-comm-msgs 1.11.2-4
has caused the Debian Bug report #835576,
regarding ros-ros-comm-msgs: FTBFS in testing (configure fails)
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.)


-- 
835576: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=835576
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:ros-ros-comm-msgs
Version: 1.11.2-3
Severity: serious

Dear maintainer:

I tried to build this package in stretch 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 --buildsystem=cmake --with python2
   dh_testdir -i -O--parallel -O--buildsystem=cmake
   dh_update_autotools_config -i -O--parallel -O--buildsystem=cmake
   dh_auto_configure -i -O--parallel -O--buildsystem=cmake
cmake .. -DCMAKE_INSTALL_PREFIX=/usr -DCMAKE_VERBOSE_MAKEFILE=ON 
-DCMAKE_BUILD_TYPE=None -DCMAKE_INSTALL_SYSCONFDIR=/etc 
-DCMAKE_INSTALL_LOCALSTATEDIR=/var
-- The C compiler identification is GNU 6.1.1
-- The CXX compiler identification is GNU 6.1.1
-- Check for working C compiler: /usr/bin/cc
-- Check for working C compiler: /usr/bin/cc -- works
-- Detecting C compiler ABI info
-- Detecting C compiler ABI info - done
-- Detecting C compile features

[... snipped ...]

CMAKE_SKIP_INSTALL_RPATH-ADVANCED:INTERNAL=1
//ADVANCED property for variable: CMAKE_SKIP_RPATH
CMAKE_SKIP_RPATH-ADVANCED:INTERNAL=1
//ADVANCED property for variable: CMAKE_STATIC_LINKER_FLAGS
CMAKE_STATIC_LINKER_FLAGS-ADVANCED:INTERNAL=1
//ADVANCED property for variable: CMAKE_STATIC_LINKER_FLAGS_DEBUG
CMAKE_STATIC_LINKER_FLAGS_DEBUG-ADVANCED:INTERNAL=1
//ADVANCED property for variable: CMAKE_STATIC_LINKER_FLAGS_MINSIZEREL
CMAKE_STATIC_LINKER_FLAGS_MINSIZEREL-ADVANCED:INTERNAL=1
//ADVANCED property for variable: CMAKE_STATIC_LINKER_FLAGS_RELEASE
CMAKE_STATIC_LINKER_FLAGS_RELEASE-ADVANCED:INTERNAL=1
//ADVANCED property for variable: CMAKE_STATIC_LINKER_FLAGS_RELWITHDEBINFO
CMAKE_STATIC_LINKER_FLAGS_RELWITHDEBINFO-ADVANCED:INTERNAL=1
//ADVANCED property for variable: CMAKE_STRIP
CMAKE_STRIP-ADVANCED:INTERNAL=1
//uname command
CMAKE_UNAME:INTERNAL=/bin/uname
//ADVANCED property for variable: CMAKE_VERBOSE_MAKEFILE
CMAKE_VERBOSE_MAKEFILE-ADVANCED:INTERNAL=1
//Details about finding PythonInterp
FIND_PACKAGE_MESSAGE_DETAILS_PythonInterp:INTERNAL=[/usr/bin/python][v2.7.12()]
//Details about finding Threads
FIND_PACKAGE_MESSAGE_DETAILS_Threads:INTERNAL=[TRUE][v()]
GTEST_FROM_SOURCE_FOUND:INTERNAL=TRUE
GTEST_FROM_SOURCE_INCLUDE_DIRS:INTERNAL=/usr/include
GTEST_FROM_SOURCE_LIBRARIES:INTERNAL=gtest
GTEST_FROM_SOURCE_LIBRARY_DIRS:INTERNAL=/<>/obj-x86_64-linux-gnu/gtest
GTEST_FROM_SOURCE_MAIN_LIBRARIES:INTERNAL=gtest_main
//ADVANCED property for variable: GTEST_INCLUDE_DIR
GTEST_INCLUDE_DIR-ADVANCED:INTERNAL=1
//ADVANCED property for variable: GTEST_LIBRARY
GTEST_LIBRARY-ADVANCED:INTERNAL=1
//ADVANCED property for variable: GTEST_LIBRARY_DEBUG
GTEST_LIBRARY_DEBUG-ADVANCED:INTERNAL=1
//ADVANCED property for variable: GTEST_MAIN_LIBRARY
GTEST_MAIN_LIBRARY-ADVANCED:INTERNAL=1
//ADVANCED property for variable: GTEST_MAIN_LIBRARY_DEBUG
GTEST_MAIN_LIBRARY_DEBUG-ADVANCED:INTERNAL=1
//ADVANCED property for variable: PYTHON_EXECUTABLE
PYTHON_EXECUTABLE-ADVANCED:INTERNAL=1
//This needs to be in PYTHONPATH when 'setup.py install' is called.
//  And it needs to match.  But setuptools won't tell us where
// it will install things.
PYTHON_INSTALL_DIR:INTERNAL=lib/python2.7/dist-packages
//CMAKE_INSTALL_PREFIX during last run
_GNUInstallDirs_LAST_CMAKE_INSTALL_PREFIX:INTERNAL=/usr

dh_auto_configure: cmake .. -DCMAKE_INSTALL_PREFIX=/usr 
-DCMAKE_VERBOSE_MAKEFILE=ON -DCMAKE_BUILD_TYPE=None 
-DCMAKE_INSTALL_SYSCONFDIR=/etc -DCMAKE_INSTALL_LOCALSTATEDIR=/var returned 
exit code 1
debian/rules:6: recipe for target 'build-indep' failed
make: *** [build-indep] Error 255
dpkg-buildpackage: error: debian/rules build-indep gave error exit status 2


Sorry, I have no idea why it fails, but the failure is reproducible easily.

Once you fix this, I would recommend that you try uploading this in
source-only form, then we will get pretty official build logs in
buildd.debian.org.

Thanks.
--- End Message ---
--- Begin Message ---
Source: ros-ros-comm-msgs
Source-Version: 1.11.2-4

We believe that the bug 

Bug#831872: marked as done (spamassassin: fails to install: error: gpg required but not found!)

[Debian Bug Tracking System]

Your message dated Mon, 29 Aug 2016 22:33:58 +
with message-id 
and subject line Bug#831872: fixed in spamassassin 3.4.1-5
has caused the Debian Bug report #831872,
regarding spamassassin: fails to install: error: gpg required but 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.)


-- 
831872: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=831872
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: spamassassin
Version: 3.4.1-4
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts
Control: affects -1 + spampd

Hi,

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

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

  Setting up spamassassin (3.4.1-4) ...
  Adding system user `debian-spamd' (UID 150) ...
  Adding new group `debian-spamd' (GID 150) ...
  Adding new user `debian-spamd' (UID 150) with group `debian-spamd' ...
  Creating home directory `/var/lib/spamassassin' ...
  error: gpg required but not found!  It is not recommended, but you can use 
"sa-update" with the --no-gpg to skip the verification. 
  dpkg: error processing package spamassassin (--configure):
   subprocess installed post-installation script returned error exit status 2


cheers,

Andreas


spampd_2.30-23.log.gz
Description: application/gzip
--- End Message ---
--- Begin Message ---
Source: spamassassin
Source-Version: 3.4.1-5

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

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Mon, 29 Aug 2016 14:14:31 -0700
Source: spamassassin
Binary: spamassassin spamc sa-compile
Architecture: source all amd64
Version: 3.4.1-5
Distribution: unstable
Urgency: medium
Maintainer: Noah Meyerhans 
Changed-By: Noah Meyerhans 
Description:
 sa-compile - Tools for compiling SpamAssassin rules into C
 spamassassin - Perl-based spam filter using text analysis
 spamc  - Client for SpamAssassin spam filtering daemon
Closes: 831872 835494
Changes:
 spamassassin (3.4.1-5) unstable; urgency=medium
 .
   * Fix "FTBFS with '.' removed from perl's @INC" with patch from
 Dominic Hargreaves  (Closes: #835494)
   * Fix "fails to install: error: gpg required but not found!" by
 making gpg usage optional. (Closes: #831872)
Checksums-Sha1:
 a5608037f3f0e11350471aa7cba2d9acc41189d4 2387 spamassassin_3.4.1-5.dsc
 1393899597fb91b05ac4eb9505b2bc06978d0fca 40624 
spamassassin_3.4.1-5.debian.tar.xz
 1d5fcaa36639e3f566b36b69d1dc42ce4a4e6263 53502 sa-compile_3.4.1-5_all.deb
 13aac7a0f3d4eefc42faf7fa7210848b1a5c3a05 1101422 spamassassin_3.4.1-5_all.deb
 79a355000db37dd21b8a8518df82d139f9663825 64636 spamc-dbgsym_3.4.1-5_amd64.deb
 18fa880206a6299bd53c250fac650c0678efabad 88412 spamc_3.4.1-5_amd64.deb
Checksums-Sha256:
 bd142abe347b004040f524b645686ca9cf1d90478f677ddbdb5a7e49b1612eff 2387 
spamassassin_3.4.1-5.dsc
 47b7aff65c424ced849ac8a563d0653ea3a7087422037f650d7dbafad826ad79 40624 
spamassassin_3.4.1-5.debian.tar.xz
 5501f998902edf5b633b0d6100d6db3ec5a4c4383b6c857d349b8f0286cd0091 53502 
sa-compile_3.4.1-5_all.deb
 3b5da0cc20c9298a2a9f0dbda36e3646cc87c53aaeb70652c66d576bf384a6c3 1101422 
spamassassin_3.4.1-5_all.deb
 56e92cd7d798aee00953d808dba42f99785225b8856b6d7c1d403aa5f9f8dcaa 64636 
spamc-dbgsym_3.4.1-5_amd64.deb
 8b3c4cbe0ff68034a344b57a1ce861be4664a22101f973118cf14bbfea15bc3f 88412 
spamc_3.4.1-5_amd64.deb
Files:
 3a8413522d1cb49da895797502403505 2387 mail optional spamassassin_3.4.1-5.dsc
 307fadd5835b5d8db60868f43755397a 40624 mail optional 
spamassassin_3.4.1-5.debian.tar.xz
 ac5581f9d3b78e184e0cd67600ffe201 53502 mail optional sa-compile_3.4.1-5_all.deb
 254cbd2e5d07e8db4bb7eda85ab1ebf0 1101422 mail optional 
spamassassin_3.4.1-5_all.deb
 860f3ab04634f1d65dbda81232f6aacf 64636 debug extra 
spamc-dbgsym_3.4.1-5_amd64.deb
 57c6c6e7771487160992d6ce03148a09 884

Bug#831084: marked as done (odb: FTBFS with GCC 6: configure: error: GCC plugin headers not found; consider installing GCC plugin development package)

[Debian Bug Tracking System]

Your message dated Mon, 29 Aug 2016 22:31:44 +
with message-id 
and subject line Bug#831084: fixed in odb 2.4.0-5
has caused the Debian Bug report #831084,
regarding odb: FTBFS with GCC 6: configure: error: GCC plugin headers not 
found; consider installing GCC plugin development 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.)


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

Hi,

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

Relevant part (hopefully):
> configure: creating ./config.lt
> config.lt: creating libtool
> checking whether g++ supports plugins... yes
> checking whether to install ODB plugin into default GCC plugin directory... 
> yes
> checking for GCC plugin headers... no
> configure: error: GCC plugin headers not found; consider installing GCC 
> plugin development package
>   "tail -v -n +0 config.log"

The full build log is available from:
   http://people.debian.org/~lucas/logs/2016/07/13/odb_2.4.0-4_unstable_gcc6.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: odb
Source-Version: 2.4.0-5

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

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Mon, 29 Aug 2016 19:18:10 +
Source: odb
Binary: odb
Architecture: source amd64
Version: 2.4.0-5
Distribution: unstable
Urgency: low
Maintainer: Laszlo Boszormenyi (GCS) 
Changed-By: Laszlo Boszormenyi (GCS) 
Description:
 odb- C++ Object-Relational Mapping (ORM)
Closes: 793264 831084 835959
Changes:
 odb (2.4.0-5) unstable; urgency=low
 .
   * Backport upstream development for GCC 6.x versions
 (closes: #793264, #835959).
   * Use gcc-6-plugin-dev build dependency (closes: #831084).
   * Update Standards-Version to 3.9.8 .
Checksums-Sha1:
 e9acfdf44d2838701742b600c65b6728e7a724f6 1715 odb_2.4.0-5.dsc
 d392fec59cd0ec82779b41108c340f4472a7fb76 7860 odb_2.4.0-5.debian.tar.xz
 6e07e43055cf5137e6f5a88cf27d166857af6e3c 31525706 odb-dbgsym_2.4.0-5_amd64.deb
 87b2eadbd3078194606eaa8a0c48bac1c86d3534 2584376 odb_2.4.0-5_amd64.deb
Checksums-Sha256:
 f9955788ee51d0587bab40df325970e1db65cb9b87ec162acb4e99477febe50a 1715 
odb_2.4.0-5.dsc
 129bbaab1810eda3276e030454a8b43741e7dd6e6d0ecadfbdbe296cc981292f 7860 
odb_2.4.0-5.debian.tar.xz
 1c75974cc6bfb29f4404e17d863c84c97f60bad270d95bfdc24c3ad252ea498e 31525706 
odb-dbgsym_2.4.0-5_amd64.deb
 5f2252439363ae5b53ac9b6db192fd9440bd3ad0df552d30a2aa0bf328e41083 2584376 
odb_2.4.0-5_amd64.deb
Files:
 92e59d2a946d125ab70e3d6ea1bcf692 1715 devel optional odb_2.4.0-5.dsc
 aa4d68dbe4075a474d73a845d0a6721a 7860 devel optional odb_2.4.0-5.debian.tar.xz
 a6415a10ed879bfca499aadc0e01c0c3 31525706 debug extra 
odb-dbgsym_2.4.0-5_amd64.deb
 06fcf04a58941470231740ac327e3375 2584376 devel optional odb_2.4.0-5_amd64.deb

-BEGIN PGP SIGNATURE-
Version: GnuPG v1

iQIcBAEBCAAGBQJXxKtLAAoJENzjEOeGTMi/azcQAIclqkF5ZehIP4TAsXUH4OqS
uESpfov30eZbSr48UNt2hw6WNSeqISpUKPVixO+2nKT9wGzkKdPhMIYd2KXLqrc7
818NC/Xslo/rOK2IoTmnSMBrpIvGvlXQcUIhaEty0B9lPws+J8XYVXnAiXHSO8WB
s9I4yWQMK7U0tbqb0+aEVhlFk9Ez+hkoCxUdw7PI5tQU1vZl7y7Z

Bug#828657: marked as done (FTBFS under Django 1.10)

[Debian Bug Tracking System]

Your message dated Mon, 29 Aug 2016 22:22:28 +
with message-id 
and subject line Bug#828657: fixed in django-sitetree 1.6.0-1
has caused the Debian Bug report #828657,
regarding FTBFS under Django 1.10
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.)


-- 
828657: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=828657
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: django-sitetree
Version: 1.5.1-2
Severity: important
User: python-dja...@packages.debian.org
Usertags: django110 django110-ftbfs

Hi,

Whilst rebuilding all reverse build-dependencies of python-django
with the latest beta, I noticed that django-sitetree FTBFS with 1.10.

Please update your package to work with Django 1.10 (in experimental)
as I will uploading it to unstable once it is released (and at the same
time raising the severity of this bug to RC).

Upstream's release notes may be helpful in diagnosing the issue:

  https://docs.djangoproject.com/en/dev/releases/1.10/

The full build log is attached.


Regards,

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


django-sitetree_1.5.1-2.log.txt.gz
Description: Binary data
--- End Message ---
--- Begin Message ---
Source: django-sitetree
Source-Version: 1.6.0-1

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

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

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

Debian distribution maintenance software
pp.
Michael Fladischer  (supplier of updated django-sitetree 
package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Mon, 29 Aug 2016 22:38:33 +0200
Source: django-sitetree
Binary: python-django-sitetree python3-django-sitetree 
python-django-sitetree-doc
Architecture: source all
Version: 1.6.0-1
Distribution: unstable
Urgency: low
Maintainer: Debian Python Modules Team 

Changed-By: Michael Fladischer 
Description:
 python-django-sitetree - site tree, menu and breadcrumbs navigation for Django
 python-django-sitetree-doc - site tree, menu and breadcrumbs navigation for 
Django (Documentat
 python3-django-sitetree - site tree, menu and breadcrumbs navigation for 
Django (Python3 ve
Closes: 828657
Changes:
 django-sitetree (1.6.0-1) unstable; urgency=low
 .
   [ Ondřej Nový ]
   * Fixed VCS URL (https)
 .
   [ Michael Fladischer ]
   * New upstream release (Closes: #828657).
   * Bump Standards-Version to 3.9.8.
   * Use https:// for copyright-format 1.0 URL.
   * Use python3-sphinx to build documentation.
Checksums-Sha1:
 dca2a49b734581136bcaa9a29cc49a9430c43ada 2022 django-sitetree_1.6.0-1.dsc
 5bed91474a3a7f5a0aa5182d95a47f11bc8dd2cc 74958 
django-sitetree_1.6.0.orig.tar.gz
 37e67329a32c053cb781a872b2f039c530653ba8 3536 
django-sitetree_1.6.0-1.debian.tar.xz
 73cdf1fa6eae484c043854f3d7363c75ff30b8f6 45400 
python-django-sitetree-doc_1.6.0-1_all.deb
 63543d3e4e743f9a1a9609a7c542c982e5803ead 52350 
python-django-sitetree_1.6.0-1_all.deb
 0aed59f08ed9400365d2be967e9d2b50431c6010 52314 
python3-django-sitetree_1.6.0-1_all.deb
Checksums-Sha256:
 3abf7a484268c8a5c9d80c4042b61b3f5e4872b40baea8f77598dd9dc3195877 2022 
django-sitetree_1.6.0-1.dsc
 028f84d1ec46eccc9536434080ef1dfa4112531effd6111d6a39c671c54ff75c 74958 
django-sitetree_1.6.0.orig.tar.gz
 a66781213eb297bebcfaef1fa9ea6c89285ee4e2ade308641b4b56fb79d55d56 3536 
django-sitetree_1.6.0-1.debian.tar.xz
 7c42ec24b9503960202436ba9d189760e5a9415caef2aaf1a3f26a6204d79ee5 45400 
python-django-sitetree-doc_1.6.0-1_all.deb
 5acb3460ed1324394384290c669c2f2aee6fbdf4b682aa7432b30ad7ac341a7e 52350 
python-django-sitetree_1.6.0-1_all.deb
 9d7a7845430da9d72646c3c06d599c750a82d82919c7cb4cba6b92097f6ca454 52314 
python3-django-sitetree_1.6.0-1_all.deb
Files:
 3bb5eadec6f63665efc9fd858a0b50b8 2022 python optional 
django-sitetree_1.6.0-1.dsc
 789537b5305d5df1884650e33192b237 74958 python optional 
django-sitetree_1.6.0.orig.tar.gz
 ab89a2923a8f4b6a4fa4ef7e4ed4e035 3536 python optional 
django-sitetree_1.6.0-1.debian.tar.xz
 874a4e42d749970d572055e14b965d0b 45400 doc optional 
python-django-sitetree-doc_1.6.0-1_all.deb
 74266517287575513842a66f1e

Processed: block 835729 with 835354

[Debian Bug Tracking System]

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

> block 835729 with 835354
Bug #835729 [src:jasperreports] jasperreports: FTBFS: build-dependency not 
installable: libitext-java (>= 2.1.7-11~)
835729 was not blocked by any bugs.
835729 was not blocking any bugs.
Added blocking bug(s) of 835729: 835354
> thanks
Stopping processing here.

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

Bug#820528: marked as done (libicu-4.2-java: Needs to Replace / Conflict with libicu4j-java)

[Debian Bug Tracking System]

Your message dated Tue, 30 Aug 2016 00:02:03 +0200
with message-id 
and subject line Re: libicu-4.2-java: Needs to Replace / Conflict with 
libicu4j-java
has caused the Debian Bug report #820528,
regarding libicu-4.2-java: Needs to Replace / Conflict with libicu4j-java
to be marked as done.

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

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


-- 
820528: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=820528
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: libicu-4.2-java
Version: 4.2.1.1-4
Severity: grave

libicu4j-4.2-java cannot be installed on a system where libicu4j-java is
installed:

Preparing to unpack .../libicu4j-4.2-java_4.2.1.1-4_all.deb ...
Unpacking libicu4j-4.2-java (4.2.1.1-4) ...
dpkg: error processing archive 
/var/cache/apt/archives/libicu4j-4.2-java_4.2.1.1-4_all.deb (--unpack):
 trying to overwrite 
'/usr/share/maven-repo/com/ibm/icu/icu4j/4.2.1.1/icu4j-4.2.1.1.pom', which is 
also in package libicu4j-java 4.2.1.1-3

Please add the necessary "Conflicts", "Replaces".

Cheers,
-Hilko
--- End Message ---
--- Begin Message ---
Version: 4.2.1.1-5

On Sat, 09 Apr 2016 16:23:23 +0200 Hilko Bengen  wrote:
> Package: libicu-4.2-java
> Version: 4.2.1.1-4
> Severity: grave
> 
> libicu4j-4.2-java cannot be installed on a system where libicu4j-java is
> installed:
> 
> Preparing to unpack .../libicu4j-4.2-java_4.2.1.1-4_all.deb ...
> Unpacking libicu4j-4.2-java (4.2.1.1-4) ...
> dpkg: error processing archive 
> /var/cache/apt/archives/libicu4j-4.2-java_4.2.1.1-4_all.deb (--unpack):
>  trying to overwrite 
> '/usr/share/maven-repo/com/ibm/icu/icu4j/4.2.1.1/icu4j-4.2.1.1.pom', which is 
> also in package libicu4j-java 4.2.1.1-3
> 
> Please add the necessary "Conflicts", "Replaces".
> 
> Cheers,
> -Hilko

This issue was apparently fixed in version 4.2.1.1-5 but someone forgot
to close this bug report.

Closing now.

Regards,

Markus







signature.asc
Description: OpenPGP digital signature
--- End Message ---

Processed: Bug#828657 marked as pending

[Debian Bug Tracking System]

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

> tag 828657 pending
Bug #828657 [src:django-sitetree] FTBFS under Django 1.10
Added tag(s) pending.
> thanks
Stopping processing here.

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

Bug#828657: marked as pending

[Michael Fladischer]

tag 828657 pending
thanks

Hello,

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


http://git.debian.org/?p=python-modules/packages/django-sitetree.git;a=commitdiff;h=3fbe6b2

---
commit 3fbe6b29eaef40539e284d7ac302e5d0207be519
Author: Michael Fladischer 
Date:   Mon Aug 29 22:39:13 2016 +0200

change target to unstable
New upstream release (Closes: #828657).

diff --git a/debian/changelog b/debian/changelog
index cacedf1..acf3854 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,15 +1,15 @@
-django-sitetree (1.6.0-1) UNRELEASED; urgency=low
+django-sitetree (1.6.0-1) unstable; urgency=low
 
   [ Ondřej Nový ]
   * Fixed VCS URL (https)
 
   [ Michael Fladischer ]
-  * New upstream release.
+  * New upstream release (Closes: #828657).
   * Bump Standards-Version to 3.9.8.
   * Use https:// for copyright-format 1.0 URL.
   * Use python3-sphinx to build documentation.
 
- -- Michael Fladischer   Mon, 29 Aug 2016 22:19:13 +0200
+ -- Michael Fladischer   Mon, 29 Aug 2016 22:38:33 +0200
 
 django-sitetree (1.5.1-2) unstable; urgency=low
 

Processed: 'perl Makefile.PL' sv_setpvn panic issues

[Debian Bug Tracking System]

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

> clone 834961 -2 -3 -4
Bug #834961 [src:libvitacilina-perl] libvitacilina-perl: FTBFS too much often 
(configure fails)
Bug 834961 cloned as bugs 835988-835990
> retitle -2 perl: EU::MM outputs UTF8 strings on an ASCII filehandle in 
> non-UTF8 locales
Bug #835988 [src:libvitacilina-perl] libvitacilina-perl: FTBFS too much often 
(configure fails)
Changed Bug title to 'perl: EU::MM outputs UTF8 strings on an ASCII filehandle 
in non-UTF8 locales' from 'libvitacilina-perl: FTBFS too much often (configure 
fails)'.
> reassign -2 perl 5.22.2-3
Bug #835988 [src:libvitacilina-perl] perl: EU::MM outputs UTF8 strings on an 
ASCII filehandle in non-UTF8 locales
Bug reassigned from package 'src:libvitacilina-perl' to 'perl'.
No longer marked as found in versions libvitacilina-perl/0.2-1.
Ignoring request to alter fixed versions of bug #835988 to the same values 
previously set
Bug #835988 [perl] perl: EU::MM outputs UTF8 strings on an ASCII filehandle in 
non-UTF8 locales
Marked as found in versions perl/5.22.2-3.
> severity -2 normal
Bug #835988 [perl] perl: EU::MM outputs UTF8 strings on an ASCII filehandle in 
non-UTF8 locales
Severity set to 'normal' from 'serious'
> submitter -2 !
Bug #835988 [perl] perl: EU::MM outputs UTF8 strings on an ASCII filehandle in 
non-UTF8 locales
Changed Bug submitter to 'Niko Tyni ' from 'Santiago Vila 
'.
> forwarded -2 https://rt.cpan.org/Public/Bug/Display.html?id=106461
Bug #835988 [perl] perl: EU::MM outputs UTF8 strings on an ASCII filehandle in 
non-UTF8 locales
Set Bug forwarded-to-address to 
'https://rt.cpan.org/Public/Bug/Display.html?id=106461'.
> retitle -3 libencode-perl: panic: sv_setpvn called with negative strlen
Bug #835989 [src:libvitacilina-perl] libvitacilina-perl: FTBFS too much often 
(configure fails)
Changed Bug title to 'libencode-perl: panic: sv_setpvn called with negative 
strlen' from 'libvitacilina-perl: FTBFS too much often (configure fails)'.
> reassign -3 libencode-perl 2.84-2
Bug #835989 [src:libvitacilina-perl] libencode-perl: panic: sv_setpvn called 
with negative strlen
Bug reassigned from package 'src:libvitacilina-perl' to 'libencode-perl'.
No longer marked as found in versions libvitacilina-perl/0.2-1.
Ignoring request to alter fixed versions of bug #835989 to the same values 
previously set
Bug #835989 [libencode-perl] libencode-perl: panic: sv_setpvn called with 
negative strlen
Marked as found in versions libencode-perl/2.84-2.
> forwarded -3 https://rt.cpan.org/Public/Bug/Display.html?id=65541
Bug #835989 [libencode-perl] libencode-perl: panic: sv_setpvn called with 
negative strlen
Set Bug forwarded-to-address to 
'https://rt.cpan.org/Public/Bug/Display.html?id=65541'.
> submitter -3 !
Bug #835989 [libencode-perl] libencode-perl: panic: sv_setpvn called with 
negative strlen
Changed Bug submitter to 'Niko Tyni ' from 'Santiago Vila 
'.
> severity -3 important
Bug #835989 [libencode-perl] libencode-perl: panic: sv_setpvn called with 
negative strlen
Severity set to 'important' from 'serious'
> retitle -4 perl: (Encode) panic: sv_setpvn called with negative strlen
Bug #835990 [src:libvitacilina-perl] libvitacilina-perl: FTBFS too much often 
(configure fails)
Changed Bug title to 'perl: (Encode) panic: sv_setpvn called with negative 
strlen' from 'libvitacilina-perl: FTBFS too much often (configure fails)'.
> reassign -4 perl 5.22.2-3
Bug #835990 [src:libvitacilina-perl] perl: (Encode) panic: sv_setpvn called 
with negative strlen
Bug reassigned from package 'src:libvitacilina-perl' to 'perl'.
No longer marked as found in versions libvitacilina-perl/0.2-1.
Ignoring request to alter fixed versions of bug #835990 to the same values 
previously set
Bug #835990 [perl] perl: (Encode) panic: sv_setpvn called with negative strlen
Marked as found in versions perl/5.22.2-3.
> forwarded -4 https://rt.cpan.org/Public/Bug/Display.html?id=65541
Bug #835990 [perl] perl: (Encode) panic: sv_setpvn called with negative strlen
Set Bug forwarded-to-address to 
'https://rt.cpan.org/Public/Bug/Display.html?id=65541'.
> block -4 with -3
Bug #835990 [perl] perl: (Encode) panic: sv_setpvn called with negative strlen
835990 was not blocked by any bugs.
835990 was not blocking any bugs.
Added blocking bug(s) of 835990: 835989
> severity -4 important
Bug #835990 [perl] perl: (Encode) panic: sv_setpvn called with negative strlen
Severity set to 'important' from 'serious'
> submitter -4 !
Bug #835990 [perl] perl: (Encode) panic: sv_setpvn called with negative strlen
Changed Bug submitter to 'Niko Tyni ' from 'Santiago Vila 
'.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
834961: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=834961
835988: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=835988
835989: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=835989
835990: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=835990
Debian Bug Tracking System
Contact ow...@bugs.debian.org w

Bug#834961: 'perl Makefile.PL' sv_setpvn panic issues

[Niko Tyni]

clone 834961 -2 -3 -4
retitle -2 perl: EU::MM outputs UTF8 strings on an ASCII filehandle in non-UTF8 
locales
reassign -2 perl 5.22.2-3
severity -2 normal
submitter -2 !
forwarded -2 https://rt.cpan.org/Public/Bug/Display.html?id=106461
retitle -3 libencode-perl: panic: sv_setpvn called with negative strlen
reassign -3 libencode-perl 2.84-2
forwarded -3 https://rt.cpan.org/Public/Bug/Display.html?id=65541
submitter -3 !
severity -3 important
retitle -4 perl: (Encode) panic: sv_setpvn called with negative strlen
reassign -4 perl 5.22.2-3
forwarded -4 https://rt.cpan.org/Public/Bug/Display.html?id=65541
block -4 with -3
severity -4 important
submitter -4 !
thanks

My current understanding of this bug is:

- ExtUtils::MakeMaker has a problem in non-UTF8 locales where it can
  write UTF8 metadata from for instance META.yml into Makefile through an
  ASCII-only file handle, causing the ""\x{00c2}" does not map to ascii"
  warnings. This is [rt.cpan.org #106461]; cloning a separate bug for it.

- Encode has an easily reproducible problem when coercing multibyte
  characters into a single byte file handle (or something to that
  effect). The IO layer buffering can get flushed in the middle of a
  multibyte character, corrupting the output. A test case is
perl -e 'binmode(STDOUT, ":encoding(ascii)"); print(("A"x shift) . "ä\n")' 
1023
  which outputs \x{fffd} when it shouldn't.

- More or less related to the above, Encode can also end up using
  uninitialized memory in similar circumstances, sometimes ending up
  with 'panic: sv_setpvn called with negative strlen'. This happens
  occasionally on current sid when building libvitacilina-perl. I'm
  appending valgrind output and a gdb stack trace. This together with
  the previous issue is [rt.cpan.org #65541], so I'm keeping them in
  one report for now (but cloning a separate one against perl which will
  only be updated after the separate package.)

The release critical part of this is probably easiest solved by either
building everything with UTF-8 metadata in a UTF-8 locale, or fixing the
ExtUtils::MakeMaker issue. I'm not sure how many packages are affected.

The upstream tickets need to be updated; I'll do that tomorrow or
so unless somebody wants to beat me to it.

Valgrind output with Encode-2.86 without optimization follows, fully
reproducible on current sid (perl 5.22.2-3), where it is sensitive to
these exact command line arguments.

% LC_ALL=C valgrind perl -I. Makefile.PL INSTALLDIRS=vendor create_packlist=0
==18958== Memcheck, a memory error detector
==18958== Copyright (C) 2002-2015, and GNU GPL'd, by Julian Seward et al.
==18958== Using Valgrind-3.12.0.SVN and LibVEX; rerun with -h for copyright info
==18958== Command: perl -I. Makefile.PL INSTALLDIRS=vendor create_packlist=0
==18958== 
'CREATE_PACKLIST' is not a known MakeMaker parameter name.
Generating a Unix-style Makefile
Writing Makefile for Vitacilina
"\x{00c2}" does not map to ascii at /usr/share/perl/5.22/ExtUtils/MakeMaker.pm 
line 1187.
"\x{00a1}" does not map to ascii at /usr/share/perl/5.22/ExtUtils/MakeMaker.pm 
line 1187.
"\x{00c3}" does not map to ascii at /usr/share/perl/5.22/ExtUtils/MakeMaker.pm 
line 1187.
"\x{00a9}" does not map to ascii at /usr/share/perl/5.22/ExtUtils/MakeMaker.pm 
line 1187.
"\x{00c2}" does not map to ascii at /usr/share/perl/5.22/ExtUtils/MakeMaker.pm 
line 1187.
"\x{00a1}" does not map to ascii at /usr/share/perl/5.22/ExtUtils/MakeMaker.pm 
line 1187.
==18958== Conditional jump or move depends on uninitialised value(s)
==18958==at 0x52E2D2: Perl_utf8n_to_uvchr (utf8.c:588)
==18958==by 0x755237B: encode_method (Encode.xs:193)
==18958==by 0x7554C42: XS_Encode__XS_encode (Encode.xs:763)
==18958==by 0x4BDAF9: Perl_pp_entersub (pp_hot.c:3272)
==18958==by 0x4B69A5: Perl_runops_standard (run.c:41)
==18958==by 0x43C212: Perl_call_sv (perl.c:2764)
==18958==by 0x8F96E36: PerlIOEncode_flush (encoding.xs:425)
==18958==by 0x53B74E: Perl_PerlIO_flush (perlio.c:1630)
==18958==by 0x53C31B: PerlIOBuf_write (perlio.c:4165)
==18958==by 0x518364: Perl_do_print (doio.c:1386)
==18958==by 0x4B8815: Perl_pp_print (pp_hot.c:856)
==18958==by 0x4B69A5: Perl_runops_standard (run.c:41)
==18958== 
"\x{fffd}" does not map to ascii at /usr/share/perl/5.22/ExtUtils/MakeMaker.pm 
line 1187.
"\x{fffd}" does not map to ascii at /usr/share/perl/5.22/ExtUtils/MakeMaker.pm 
line 1187.
"\x{00a9}" does not map to ascii at /usr/share/perl/5.22/ExtUtils/MakeMaker.pm 
line 1187.
Writing MYMETA.yml and MYMETA.json
==18958== 
==18958== HEAP SUMMARY:
==18958== in use at exit: 14,378,715 bytes in 54,070 blocks
==18958==   total heap usage: 179,891 allocs, 125,821 frees, 32,136,429 bytes 
allocated
==18958== 
==18958== LEAK SUMMARY:
==18958==definitely lost: 69,536 bytes in 29 blocks
==18958==indirectly lost: 14,244,115 bytes in 53,915 blocks
==18958==  possibly lost: 51,952 bytes in 89 blocks
==18958==still reachable: 13,112 bytes in

Bug#835987: dbconfig-common: breaks redmine

[Antonio Terceiro]

Package: dbconfig-common
Version: 2.0.5
Severity: grave
Justification: renders package unusable

After the upload of 2.0.5, the CI tests of redmine started failing:

https://ci.debian.net/packages/r/redmine/unstable/amd64/

I am attaching a copy of the failing log for completeness.


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

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

Versions of packages dbconfig-common depends on:
ii  debconf [debconf-2.0]  1.5.59
ii  ucf3.0036

dbconfig-common recommends no packages.

Versions of packages dbconfig-common suggests:
pn  dbconfig-mysql | dbconfig-pgsql | dbconfig-sqlite | dbconfig-sqlite  

-- debconf information excluded


redmine.autopkgtest.log.gz
Description: application/gzip


signature.asc
Description: PGP signature

Bug#835185: mysql-workbench: Segfault when opening connection

[Felipe Sateler]

On Sun, 28 Aug 2016 16:47:18 +0800 Paul Wise  wrote:
> Followup-For: Bug #835185
> Package: mysql-workbench
> Version: 6.3.4+dfsg-3+b5
> Control: severity -1 serious
> Control: usertags -1 + bittenby crash
>
> On Tue, 23 Aug 2016 07:41:42 -0400 Richard Ayotte wrote:
>
> > The application segfaults when a connection is clicked to be opened.
>
> I have the same issue, which prevents me from using mysql-workbench.
>
> This is a serious issue since it makes mysql-workbench not work.

It appears something changed ABI without bumping SONAME. Recompiling
mysql-workbench makes it work again.


Saludos

Bug#835649: [flashplugin-nonfree] OldStable (Wheezy) version of package is critically out of date

[Stephen Lyons]

According to
https://helpx.adobe.com/security/products/flash-player/apsb16-25.html
the listed CVEs are:

CVE-2016-4172, CVE-2016-4173, CVE-2016-4174, CVE-2016-4175,
CVE-2016-4176, CVE-2016-4177, CVE-2016-4178, CVE-2016-4179,
CVE-2016-4180, CVE-2016-4181, CVE-2016-4182, CVE-2016-4183,
CVE-2016-4184, CVE-2016-4185, CVE-2016-4186, CVE-2016-4187,
CVE-2016-4188, CVE-2016-4189, CVE-2016-4190, CVE-2016-4217,
CVE-2016-4218, CVE-2016-4219, CVE-2016-4220, CVE-2016-4221,
CVE-2016-4222, CVE-2016-4223, CVE-2016-4224, CVE-2016-4225,
CVE-2016-4226, CVE-2016-4227, CVE-2016-4228, CVE-2016-4229,
CVE-2016-4230, CVE-2016-4231, CVE-2016-4232, CVE-2016-4233,
CVE-2016-4234, CVE-2016-4235, CVE-2016-4236, CVE-2016-4237,
CVE-2016-4238, CVE-2016-4239, CVE-2016-4240, CVE-2016-4241,
CVE-2016-4242, CVE-2016-4243, CVE-2016-4244, CVE-2016-4245,
CVE-2016-4246, CVE-2016-4247, CVE-2016-4248, CVE-2016-4249

I am sorry but I have not tried to pin down which of them actually
related to the Linux OS, but at least one of them seems to be "bad"
enough for steps to have been taken to address the issue for "Stable"
and "Testing", it is just that this has not made it back into "OldStable".

As for "affected flashplayer versions" 11.2.202.626 is a victim
according to the same web-page and 11.2.202.632 is "the cure",
regrettably, flashplugin-nonfree 3.2 from the "OldStable" distribution
will leave "626" in place as it does not have the "fixes" that the later
versions 3.6.1 or 3.7 have.

I believe that the needed changes are the ones that:
* replaces the "get-upstream-version.pl" if it is older than 2016-08-04
09:35" in /usr/sbin/update-flashplugin-nonfree
* revises the user-agent string in the file referred to, i.e.
/var/cache/flashplugin-nonfree/get-upstream-version.pl (so it does not
have a "KH" in it?) AND does NOT use "fp10"(?) (as a download source).

I would be lying if I said I fully understood the revisions that have
been made to the package but as I understand these are so that the
package does not try and download something with a 20.xxx version
numbers which "is NOT the file that we are looking for"!

As I said, FireFox is now actively blocking that older flash version so
there is a loss of functionality as it attempts to protect users from
the vulnerabilities...

I hope that helps!

Regards

Stephen

On 28/08/16 07:05, Bart Martens wrote:
> Control tags 835649 moreinfo
> 
> On Sat, Aug 27, 2016 at 11:41:02PM +0100, Stephen Lyons wrote:
>> I believe the version of this package for Debian 7 installations
>> ("OldStable") is *critically* out of date and still has the CVEs that
>> have been addressed by later versions 1:3.6.1 in "Stable" or 1:3.7
>> "Testing" and "Unstable".
> 
> Which CVEs exactly?
> 
>> For the record, backporting by hand-editing in the differences between
>> 3.2 and 3.7 into the 3.2 version does seem to do the job
> 
> Which differences exactly matter?
> 
> Regards,
> 
> Bart Martens
> 



signature.asc
Description: OpenPGP digital signature

Processed: reassign 834368 to gnupg-agent, forcibly merging 830658 834368 ..., tagging 830658

[Debian Bug Tracking System]

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

> reassign 834368 gnupg-agent
Bug #834368 [gnupg] gnupg: update to gnupg2 broke gpg-agent autostart
Bug reassigned from package 'gnupg' to 'gnupg-agent'.
No longer marked as found in versions gnupg2/2.1.14-5.
Ignoring request to alter fixed versions of bug #834368 to the same values 
previously set
> forcemerge 830658 834368
Bug #830658 [gnupg-agent] gpg-agent: cannot talk to libsecret when used as 
ssh-agent and not started from the same session
Bug #834368 [gnupg-agent] gnupg: update to gnupg2 broke gpg-agent autostart
Severity set to 'normal' from 'serious'
Marked as found in versions gnupg2/2.1.13-5.
Added tag(s) upstream and help.
Merged 830658 834368
> retitle 830658 gpg-agent cannot talk to libsecret or X11 when not started 
> from the same session
Bug #830658 [gnupg-agent] gpg-agent: cannot talk to libsecret when used as 
ssh-agent and not started from the same session
Bug #834368 [gnupg-agent] gnupg: update to gnupg2 broke gpg-agent autostart
Changed Bug title to 'gpg-agent cannot talk to libsecret or X11 when not 
started from the same session' from 'gpg-agent: cannot talk to libsecret when 
used as ssh-agent and not started from the same session'.
Changed Bug title to 'gpg-agent cannot talk to libsecret or X11 when not 
started from the same session' from 'gnupg: update to gnupg2 broke gpg-agent 
autostart'.
> tags 830658 + moreinfo
Bug #830658 [gnupg-agent] gpg-agent cannot talk to libsecret or X11 when not 
started from the same session
Bug #834368 [gnupg-agent] gpg-agent cannot talk to libsecret or X11 when not 
started from the same session
Added tag(s) moreinfo.
Added tag(s) moreinfo.
> thanks
Stopping processing here.

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

Bug#803520: marked as done (libpreludedb: FTBFS: cp: cannot stat './debian/tmp//usr/lib/x86_64-linux-gnu/perl5/5.20': No such file or directory)

[Debian Bug Tracking System]

Your message dated Mon, 29 Aug 2016 20:47:17 +0100
with message-id 
<1472500037.3896840.709561569.42178...@webmail.messagingengine.com>
and subject line Re: libpreludedb: FTBFS: cp: cannot stat 
'./debian/tmp//usr/lib/x86_64-linux-gnu/perl5/5.20': No such file or directory
has caused the Debian Bug report #803520,
regarding libpreludedb: FTBFS: cp: cannot stat 
'./debian/tmp//usr/lib/x86_64-linux-gnu/perl5/5.20': No such file or directory
to be marked as done.

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

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


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

Dear Maintainer,

libpreludedb fails to build from source in unstable/amd64:

  [..]

  sed -e 's,${archlib},/usr/lib/x86_64-linux-gnu/perl5/5.20,g'
  debian/libpreludedb-perl.install.in > debian/libpreludedb-perl.install
  cd bindings/python && python2.7 setup.py install --root
  /build/libpreludedb-1.0.0/debian/python-preludedb
  running install
  running build
  running build_py
  running build_ext
  running install_lib
  creating /build/libpreludedb-1.0.0/debian/python-preludedb/usr
  creating /build/libpreludedb-1.0.0/debian/python-preludedb/usr/lib
  creating
  /build/libpreludedb-1.0.0/debian/python-preludedb/usr/lib/python2.7
  creating
  
/build/libpreludedb-1.0.0/debian/python-preludedb/usr/lib/python2.7/site-packages
  copying build/lib.linux-x86_64-2.7/_preludedb.so ->
  
/build/libpreludedb-1.0.0/debian/python-preludedb/usr/lib/python2.7/site-packages
  copying build/lib.linux-x86_64-2.7/preludedb.py ->
  
/build/libpreludedb-1.0.0/debian/python-preludedb/usr/lib/python2.7/site-packages
  byte-compiling
  
/build/libpreludedb-1.0.0/debian/python-preludedb/usr/lib/python2.7/site-packages/preludedb.py
  to preludedb.pyc
  running install_egg_info
  Writing
  
/build/libpreludedb-1.0.0/debian/python-preludedb/usr/lib/python2.7/site-packages/preludedb-0.0.0-py2.7.egg-info
  dh_testdir
  dh_testroot
  dh_install
  cp: cannot stat './debian/tmp//usr/lib/x86_64-linux-gnu/perl5/5.20':
  No such file or directory
  dh_install: cp --reflink=auto -a
  ./debian/tmp//usr/lib/x86_64-linux-gnu/perl5/5.20
  debian/libpreludedb-perl///usr/lib/x86_64-linux-gnu/perl5/ returned
  exit code 1
  debian/rules:71: recipe for target 'binary-arch' failed
  make: *** [binary-arch] Error 2
  dpkg-buildpackage: error: fakeroot debian/rules binary gave error exit
  status 2

  [..]

The full build log is attached or (an alternate build) can be viewed
here:


https://reproducible.debian.net/logs/unstable/amd64/libpreludedb_1.0.0-2.3.build1.log.gz


Regards,

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


libpreludedb.1.0.0-2.3.unstable.amd64.log.txt.gz
Description: application/gzip
--- End Message ---
--- Begin Message ---
Hi,

> libpreludedb: FTBFS: cp: cannot stat 
> './debian/tmp//usr/lib/x86_64-linux-gnu/perl5/5.20': No such file or directory

I can no longer reproduce this, so closing (in BCC).


Regards,

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

Bug#834963: ruby-protected-attributes: FTBFS too much often (failing tests)

[Antonio Terceiro]

Control: tags -1 + patch pending
Control: forwarded -1 https://github.com/rails/protected_attributes/pull/89

err, fixing the metadata update


signature.asc
Description: PGP signature

Processed: Re: Bug#834963: ruby-protected-attributes: FTBFS too much often (failing tests)

[Debian Bug Tracking System]

Processing control commands:

> tags -1 + patch pending
Bug #834963 [src:ruby-protected-attributes] ruby-protected-attributes: FTBFS 
too much often (failing tests)
Added tag(s) patch and pending.
> forwarded -1 https://github.com/rails/protected_attributes/pull/89
Bug #834963 [src:ruby-protected-attributes] ruby-protected-attributes: FTBFS 
too much often (failing tests)
Set Bug forwarded-to-address to 
'https://github.com/rails/protected_attributes/pull/89'.

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

Bug#803520: libpreludedb: FTBFS: cp: cannot stat './debian/tmp//usr/lib/x86_64-linux-gnu/perl5/5.20': No such file or directory

[Chris Lamb]

Hi,

> libpreludedb: FTBFS: cp: cannot stat 
> './debian/tmp//usr/lib/x86_64-linux-gnu/perl5/5.20': No such file or directory

I can no longer reproduce this, so closing (in BCC).


Regards,

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

Bug#824226: marked as done (openjdk-8-jre: ATK bridge causes segfault when loading JR)

[Debian Bug Tracking System]

Your message dated Mon, 29 Aug 2016 19:19:28 +
with message-id 
and subject line Bug#824226: fixed in java-atk-wrapper 0.33.3-9
has caused the Debian Bug report #824226,
regarding openjdk-8-jre: ATK bridge causes segfault when loading JR
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.)


-- 
824226: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=824226
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: openjdk-8-jre
Version: 8u91-b14-2
Severity: normal

Dear Maintainer,

When attempting to launch Jabref after updating openjdk from ( i believe, based 
upon apt history) 7u91-2.6.3-1 to 8u91-b14-2, i found that the following 
segfault occured:


** (java:13536): WARNING **: Couldn't register with accessibility bus: Did not 
receive a reply. Possible causes include: the remote application did not send a 
reply, the message bus security policy blocked the reply, the reply timeout 
expired, or the network connection was broken.
#
# A fatal error has been detected by the Java Runtime Environment:
#
#  SIGSEGV (0xb) at pc=0x7fe243798a42, pid=13536, tid=140609524610816
#
# JRE version: OpenJDK Runtime Environment (8.0_91-b14) (build 
1.8.0_91-8u91-b14-2-b14)
# Java VM: OpenJDK 64-Bit Server VM (25.91-b14 mixed mode linux-amd64 
compressed oops)
# Problematic frame:
# C  [libatk-bridge-2.0.so.0+0x10a42]
#
# Failed to write core dump. Core dumps have been disabled. To enable core 
dumping, try "ulimit -c unlimited" before starting Java again
#
# An error report file with more information is saved as:
# /home/username/hs_err_pid13536.log
#
# If you would like to submit a bug report, please visit:
#   http://bugreport.java.com/bugreport/crash.jsp
# The crash happened outside the Java Virtual Machine in native code.
# See problematic frame for where to report the bug.
#
Aborted

This appears to have been reported elsewhere in bug 798131 for freemind. , when 
following the suggestion to disable the ATK bridge line int 
/etc/java-8-openjdk/accessibility.properties , the program was able to run 
successfully.  I am running XFCE, as per one commenter in 798131m, however  
ulike in that bug report, I have assitive technologies in XFCE enabled.


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

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

Versions of packages openjdk-8-jre depends on:
ii  libasound21.1.0-1
ii  libatk-wrapper-java-jni   0.33.3-6+b1
ii  libc6 2.22-7
ii  libgif7   5.1.4-0.1
ii  libgl1-mesa-glx [libgl1]  11.1.3-1
ii  libgtk2.0-0   2.24.30-1.1
ii  libjpeg62-turbo   1:1.4.2-2
ii  libpng16-16   1.6.21-4
ii  libpulse0 8.0-2+b2
ii  libx11-6  2:1.6.3-1
ii  libxext6  2:1.3.3-1
ii  libxinerama1  2:1.1.3-1+b1
ii  libxrandr22:1.5.0-1
ii  openjdk-8-jre-headless8u91-b14-2
ii  zlib1g1:1.2.8.dfsg-2+b1

Versions of packages openjdk-8-jre recommends:
ii  fonts-dejavu-extra  2.35-1
ii  libgconf-2-43.2.6-3
ii  libgnome-2-02.32.1-5
ii  libgnomevfs2-0  1:2.24.4-6.1+b1

Versions of packages openjdk-8-jre suggests:
pn  icedtea-8-plugin  

-- no debconf information
--- End Message ---
--- Begin Message ---
Source: java-atk-wrapper
Source-Version: 0.33.3-9

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

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

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

Debian distribution maintenance software
pp.
Samuel Thibault  (supplier of updated java-atk-wrapper 
package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Mon, 29 Aug 2016 21:01:22 +0200
Source: java-atk-wrapper
Binary: libatk-wrapper-java libatk-wrapper-java-jni
Architecture: source amd64 all
Version: 0.33.3-9
Distribution: unstable
Urgency: medium

Processed: Bug#834894 marked as pending

[Debian Bug Tracking System]

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

> tag 834894 pending
Bug #834894 {Done: Salvatore Bonaccorso } [src:gnupg1] 
gnupg1: CVE-2016-6313: RNG prediction vulnerability
Added tag(s) pending.
> thanks
Stopping processing here.

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

Bug#834894: marked as pending

[Daniel Kahn Gillmor]

tag 834894 pending
thanks

Hello,

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

http://git.debian.org/?p=pkg-gnupg/gnupg1.git;a=commitdiff;h=d62c4bf

---
commit d62c4bffe159e648f2e6fd6fd60febc377eee8de
Author: Daniel Kahn Gillmor 
Date:   Mon Aug 29 15:08:29 2016 -0400

tweak changelog for correct bug report number and to include CVE

diff --git a/debian/changelog b/debian/changelog
index a0c099f..e2b9df1 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,6 +1,7 @@
 gnupg1 (1.4.21-1) unstable; urgency=medium
 
-  * new upstream release (Closes: #834893)
+  * new upstream release
+- fixes CVE-2016-6313 (Closes: #834894)
   * drop already upstreamed patches, refresh remainder
   * build reproducibly (Closes: #806494)
   * gnupg1 is Priority: extra (Closes: #834757)

Processed: tagging 824226

[Debian Bug Tracking System]

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

> tags 824226 + pending
Bug #824226 [java-atk-wrapper] openjdk-8-jre: ATK bridge causes segfault when 
loading JR
Added tag(s) pending.
> thanks
Stopping processing here.

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

Processed: reassign 824226 to java-atk-wrapper

[Debian Bug Tracking System]

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

> reassign 824226 java-atk-wrapper
Bug #824226 [openjdk-8-jre] openjdk-8-jre: ATK bridge causes segfault when 
loading JR
Bug reassigned from package 'openjdk-8-jre' to 'java-atk-wrapper'.
No longer marked as found in versions openjdk-8/8u102-b14.1-2 and 
openjdk-8/8u91-b14-2.
Ignoring request to alter fixed versions of bug #824226 to the same values 
previously set
> thanks
Stopping processing here.

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

Bug#835983: python-pypdf2: Incorrect Breaks/Replaces which forbids co-installation with python-pypdf

[Raphaël Hertzog]

Package: python-pypdf2
Version: 1.26.0-1
Severity: serious
Justification: co-installation
User: de...@kali.org
Usertags: origin-kali

python-pypdf and python-pypdf2 use a differente module name and can thus
be co-installed... except that this is no longer possible because you
added unversioned Breaks/Replaces on python-pypdf2.

The #764090 report that triggered those Breaks/Replaces refers to to an
old version of a binary package that was built by src:pypdf2 but that is
no longer built for quite a long time (cf #762186 that you also fixed two
years ago).

Since python-pypdf added an epoch to work around the hijack you might want
to do this:
Breaks: python-pypdf (<< 1:1.13-2)
Replaces: python-pypdf (<< 1:1.13-2)

In Kali we actually need python-pypdf and python-pypdf2 to be
co-installable.

Thank you in advance.

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

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

Bug#834368: gpg-agent's ssh-agent functionality

[Daniel Kahn Gillmor]

Control: forcemerge 830658 834368
Control: retitle 830658 gpg-agent cannot talk to libsecret or X11 when not 
started from the same session
Control: tags 830658 + moreinfo

834368 and 830658 describe basically the same problem: when gpg-agent is
started from a different session, from systemd's user services, or from
anywhere else, the ssh-agent mimcry fails because it doesn't know how to
prompt the user.

During the user's X session (possibly at the start of the session), the
user can explicitly invoke (as Werner points out in
https://bugs.debian.org/834368#20):

gpg-connect-agent updatestartuptty /bye

Which is documented as:

0 dkg@alice:~$ gpg-connect-agent 'help updatestartuptty' /bye
# UPDATESTARTUPTTY
# 
# Set startup TTY and X11 DISPLAY variables to the values of this
# session.  This command is useful to pull future pinentries to
# another screen.  It is only required because there is no way in the
# ssh-agent protocol to convey this information.
OK
0 dkg@alice:~$ 

This will update not only TTY and X11 but also GTK and DBUS env vars to
match whatever's present in the session.  You can see the full list with
"getinfo std_env_names", the current "startup env" with "getinfo
std_startup_env", and the env of the current session (if you're in the
middle of one) with "getinfo std_session_env"

However, i note that when i use these commands with the
systemd-controlled user service while i'm the only logged in user (and
i'm logged in only once), i get the following answers for
std_startup_env:

D DISPLAY=:0
D XAUTHORITY=/home/dkg/.Xauthority
D DBUS_SESSION_BUS_ADDRESS=unix:path=/run/user/1000/bus

This looks sufficient for pinentry to be able to prompt successfully.
DISPLAY points to the right location, and the DBUS_SESSION_BUS_ADDRESS
appears to be sufficient for libsecret to get the info it needs.

I tested pinentry by hand (for -qt, -gtk-2, and -gnome3) with:

  echo getpin | env -i DISPLAY=:0 DBUS_SESSION_BUS_ADDRESS=/run/user/1000/bus 
pinentry

a longer script on stdin than "getpin" should make it possible to do the
same test for libsecret.  something like (see "info pinentry" for more
details):

env -i DISPLAY=:0 DBUS_SESSION_BUS_ADDRESS=/run/user/1000/bus pinentry <

signature.asc
Description: PGP signature

Processed (with 3 errors): gpg-agent's ssh-agent functionality

[Debian Bug Tracking System]

Processing control commands:

> forcemerge 830658 834368
Bug #830658 [gnupg-agent] gpg-agent: cannot talk to libsecret when used as 
ssh-agent and not started from the same session
Unable to merge bugs because:
package of #834368 is 'gnupg' not 'gnupg-agent'
Failed to forcibly merge 830658: Did not alter merged bugs.

> retitle 830658 gpg-agent cannot talk to libsecret or X11 when not started 
> from the same session
Failed to set the title of 830658: failed to get lock on 
/org/bugs.debian.org/spool/lock/830658 -- Unable to lock 
/org/bugs.debian.org/spool/lock/830658 Resource temporarily unavailable.
Unable to lock /org/bugs.debian.org/spool/lock/830658 Resource temporarily 
unavailable at /usr/local/lib/site_perl/Debbugs/Common.pm line 629.
Unable to lock /org/bugs.debian.org/spool/lock/830658 Resource temporarily 
unavailable at /usr/local/lib/site_perl/Debbugs/Common.pm line 629.
Unable to lock /org/bugs.debian.org/spool/lock/830658 Resource temporarily 
unavailable at /usr/local/lib/site_perl/Debbugs/Common.pm line 629.
Unable to lock /org/bugs.debian.org/spool/lock/830658 Resource temporarily 
unavailable at /usr/local/lib/site_perl/Debbugs/Common.pm line 629.
Unable to lock /org/bugs.debian.org/spool/lock/830658 Resource temporarily 
unavailable at /usr/local/lib/site_perl/Debbugs/Common.pm line 629.
Unable to lock /org/bugs.debian.org/spool/lock/830658 Resource temporarily 
unavailable at /usr/local/lib/site_perl/Debbugs/Common.pm line 629.
Unable to lock /org/bugs.debian.org/spool/lock/830658 Resource temporarily 
unavailable at /usr/local/lib/site_perl/Debbugs/Common.pm line 629.
Unable to lock /org/bugs.debian.org/spool/lock/830658 Resource temporarily 
unavailable at /usr/local/lib/site_perl/Debbugs/Common.pm line 629.
Unable to lock /org/bugs.debian.org/spool/lock/830658 Resource temporarily 
unavailable at /usr/local/lib/site_perl/Debbugs/Common.pm line 629.
 at /usr/local/lib/site_perl/Debbugs/Common.pm line 587.

> tags 830658 + moreinfo
Failed to alter tags of Bug 830658: failed to get lock on 
/org/bugs.debian.org/spool/lock/830658 -- Unable to lock 
/org/bugs.debian.org/spool/lock/830658 Resource temporarily unavailable.
Unable to lock /org/bugs.debian.org/spool/lock/830658 Resource temporarily 
unavailable at /usr/local/lib/site_perl/Debbugs/Common.pm line 629.
Unable to lock /org/bugs.debian.org/spool/lock/830658 Resource temporarily 
unavailable at /usr/local/lib/site_perl/Debbugs/Common.pm line 629.
Unable to lock /org/bugs.debian.org/spool/lock/830658 Resource temporarily 
unavailable at /usr/local/lib/site_perl/Debbugs/Common.pm line 629.
Unable to lock /org/bugs.debian.org/spool/lock/830658 Resource temporarily 
unavailable at /usr/local/lib/site_perl/Debbugs/Common.pm line 629.
Unable to lock /org/bugs.debian.org/spool/lock/830658 Resource temporarily 
unavailable at /usr/local/lib/site_perl/Debbugs/Common.pm line 629.
Unable to lock /org/bugs.debian.org/spool/lock/830658 Resource temporarily 
unavailable at /usr/local/lib/site_perl/Debbugs/Common.pm line 629.
Unable to lock /org/bugs.debian.org/spool/lock/830658 Resource temporarily 
unavailable at /usr/local/lib/site_perl/Debbugs/Common.pm line 629.
Unable to lock /org/bugs.debian.org/spool/lock/830658 Resource temporarily 
unavailable at /usr/local/lib/site_perl/Debbugs/Common.pm line 629.
Unable to lock /org/bugs.debian.org/spool/lock/830658 Resource temporarily 
unavailable at /usr/local/lib/site_perl/Debbugs/Common.pm line 629.
 at /usr/local/lib/site_perl/Debbugs/Common.pm line 587.


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

Processed (with 3 errors): gpg-agent's ssh-agent functionality

[Debian Bug Tracking System]

Processing control commands:

> forcemerge 830658 834368
Bug #830658 [gnupg-agent] gpg-agent: cannot talk to libsecret when used as 
ssh-agent and not started from the same session
Unable to merge bugs because:
package of #834368 is 'gnupg' not 'gnupg-agent'
Failed to forcibly merge 830658: Did not alter merged bugs.

> retitle 830658 gpg-agent cannot talk to libsecret or X11 when not started 
> from the same session
Failed to set the title of 830658: failed to get lock on 
/org/bugs.debian.org/spool/lock/830658 -- Unable to lock 
/org/bugs.debian.org/spool/lock/830658 Resource temporarily unavailable.
Unable to lock /org/bugs.debian.org/spool/lock/830658 Resource temporarily 
unavailable at /usr/local/lib/site_perl/Debbugs/Common.pm line 629.
Unable to lock /org/bugs.debian.org/spool/lock/830658 Resource temporarily 
unavailable at /usr/local/lib/site_perl/Debbugs/Common.pm line 629.
Unable to lock /org/bugs.debian.org/spool/lock/830658 Resource temporarily 
unavailable at /usr/local/lib/site_perl/Debbugs/Common.pm line 629.
Unable to lock /org/bugs.debian.org/spool/lock/830658 Resource temporarily 
unavailable at /usr/local/lib/site_perl/Debbugs/Common.pm line 629.
Unable to lock /org/bugs.debian.org/spool/lock/830658 Resource temporarily 
unavailable at /usr/local/lib/site_perl/Debbugs/Common.pm line 629.
Unable to lock /org/bugs.debian.org/spool/lock/830658 Resource temporarily 
unavailable at /usr/local/lib/site_perl/Debbugs/Common.pm line 629.
Unable to lock /org/bugs.debian.org/spool/lock/830658 Resource temporarily 
unavailable at /usr/local/lib/site_perl/Debbugs/Common.pm line 629.
Unable to lock /org/bugs.debian.org/spool/lock/830658 Resource temporarily 
unavailable at /usr/local/lib/site_perl/Debbugs/Common.pm line 629.
Unable to lock /org/bugs.debian.org/spool/lock/830658 Resource temporarily 
unavailable at /usr/local/lib/site_perl/Debbugs/Common.pm line 629.
 at /usr/local/lib/site_perl/Debbugs/Common.pm line 587.

> tags 830658 + moreinfo
Failed to alter tags of Bug 830658: failed to get lock on 
/org/bugs.debian.org/spool/lock/830658 -- Unable to lock 
/org/bugs.debian.org/spool/lock/830658 Resource temporarily unavailable.
Unable to lock /org/bugs.debian.org/spool/lock/830658 Resource temporarily 
unavailable at /usr/local/lib/site_perl/Debbugs/Common.pm line 629.
Unable to lock /org/bugs.debian.org/spool/lock/830658 Resource temporarily 
unavailable at /usr/local/lib/site_perl/Debbugs/Common.pm line 629.
Unable to lock /org/bugs.debian.org/spool/lock/830658 Resource temporarily 
unavailable at /usr/local/lib/site_perl/Debbugs/Common.pm line 629.
Unable to lock /org/bugs.debian.org/spool/lock/830658 Resource temporarily 
unavailable at /usr/local/lib/site_perl/Debbugs/Common.pm line 629.
Unable to lock /org/bugs.debian.org/spool/lock/830658 Resource temporarily 
unavailable at /usr/local/lib/site_perl/Debbugs/Common.pm line 629.
Unable to lock /org/bugs.debian.org/spool/lock/830658 Resource temporarily 
unavailable at /usr/local/lib/site_perl/Debbugs/Common.pm line 629.
Unable to lock /org/bugs.debian.org/spool/lock/830658 Resource temporarily 
unavailable at /usr/local/lib/site_perl/Debbugs/Common.pm line 629.
Unable to lock /org/bugs.debian.org/spool/lock/830658 Resource temporarily 
unavailable at /usr/local/lib/site_perl/Debbugs/Common.pm line 629.
Unable to lock /org/bugs.debian.org/spool/lock/830658 Resource temporarily 
unavailable at /usr/local/lib/site_perl/Debbugs/Common.pm line 629.
 at /usr/local/lib/site_perl/Debbugs/Common.pm line 587.


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

Bug#835981: dbconfig-common: autopkg test fails with 2.0.5

[Paul Gevers]

Package: dbconfig-common
Version: 2.0.5
Severity: serious

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

The 2.0.5 upload of dbconfig-common caused the autopkg tests to fail¹, albeit
they passed on my system. To prevent migration of the current package before I
understand why and determine it to be ok or not, I file this bug.

Paul
¹ 
https://ci.debian.net/data/packages/unstable/amd64/d/dbconfig-common/20160828_214723.autopkgtest.log.gz


-BEGIN PGP SIGNATURE-
Version: GnuPG v1

iQEcBAEBCAAGBQJXxIHnAAoJEJxcmesFvXUKM68IAMDi08Spm70Oyalvw7iTRKrY
1biz1/fw0FvCNv7NKcCpdOFK3oh7xL2FcUHQR1l7skM+dqG6jXtudL+Abv6Npr4t
IkmKfvE6YYCiBQiG3a3fNXT7E0DaI6WH1AX81AT2Uti9j0gbLuQzaoqQit6kszKT
fhUsm4ZDwpTwWpTel9it5d0i79zK6dpVcNbvpoqDdso+9dkws7yYUFt8wlejIrJD
joc8quvPqQEn/0kVGaw1/RKtR3M+vSZX+SABF+WQi1/dNDc4BgZOeW+/O5rEbuPK
j0qpdriBLxhlOb7X9X5WoCn6AZ3bHC0pQ+d95CHdb0kqpQM1JIrohMaZ9+P4V1E=
=BLYR
-END PGP SIGNATURE-

Processed: tag

[Debian Bug Tracking System]

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

> tags 831872 + pending
Bug #831872 [spamassassin] spamassassin: fails to install: error: gpg required 
but not found!
Added tag(s) pending.
> thanks
Stopping processing here.

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

Bug#834963: ruby-protected-attributes: FTBFS too much often (failing tests)

[Antonio Terceiro]

Close: tags -1 + patch pending
Close: forwarded -1 https://github.com/rails/protected_attributes/pull/89

On Sun, Aug 21, 2016 at 01:41:27AM +0200, Santiago Vila wrote:
> Package: src:ruby-protected-attributes
> Version: 1.1.3-1
> Severity: serious
> 
> Dear maintainer:
> 
> I tried to build this package in stretch with "dpkg-buildpackage -A"
> (which is what the "Arch: all" autobuilder would do to build it)
> but it failed:
> 
> 
> [...]
[snip]
> 
> 
> 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
> doing "dpkg-buildpackage -A" does not mean anything special.

Thanks for the bug report. I have found the issue, and submitted a patch
upstream. I will upload a fixed package in a few days.


signature.asc
Description: PGP signature

Processed: tag

[Debian Bug Tracking System]

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

> tags 835494 + pending
Bug #835494 [src:spamassassin] spamassassin: FTBFS with '.' removed from perl's 
@INC
Added tag(s) pending.
> thanks
Stopping processing here.

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

Processed: [bts-link] source package lshell

[Debian Bug Tracking System]

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

> #
> # bts-link upstream status pull for source package lshell
> # see http://lists.debian.org/debian-devel-announce/2006/05/msg1.html
> #
> user bts-link-upstr...@lists.alioth.debian.org
Setting user to bts-link-upstr...@lists.alioth.debian.org (was 
bts-link-de...@lists.alioth.debian.org).
> # remote status report for #834946 (http://bugs.debian.org/834946)
> # Bug title: lshell: CVE-2016-6903: Shell outbreak with multiline commands
> #  * https://github.com/ghantoos/lshell/issues/149
> #  * remote status changed: open -> closed
> #  * closed upstream
> tags 834946 + fixed-upstream
Bug #834946 [lshell] lshell: CVE-2016-6903: Shell outbreak with multiline 
commands
Added tag(s) fixed-upstream.
> usertags 834946 - status-open
Usertags were: status-open.
Usertags are now: .
> usertags 834946 + status-closed
There were no usertags set.
Usertags are now: status-closed.
> # remote status report for #834949 (http://bugs.debian.org/834949)
> # Bug title: lshell: CVE-2016-6902: Shell outbreak due to bad syntax parse
> #  * https://github.com/ghantoos/lshell/issues/147
> #  * remote status changed: open -> closed
> #  * closed upstream
> tags 834949 + fixed-upstream
Bug #834949 [lshell] lshell: CVE-2016-6902: Shell outbreak due to bad syntax 
parse
Added tag(s) fixed-upstream.
> usertags 834949 - status-open
Usertags were: status-open.
Usertags are now: .
> usertags 834949 + status-closed
There were no usertags set.
Usertags are now: status-closed.
> thanks
Stopping processing here.

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

Processed: [bts-link] source package systemd

[Debian Bug Tracking System]

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

> #
> # bts-link upstream status pull for source package systemd
> # see http://lists.debian.org/debian-devel-announce/2006/05/msg1.html
> #
> user bts-link-upstr...@lists.alioth.debian.org
Setting user to bts-link-upstr...@lists.alioth.debian.org (was 
bts-link-de...@lists.alioth.debian.org).
> # remote status report for #794721 (http://bugs.debian.org/794721)
> # Bug title: udev_queue_get_udev_is_active API is broken starting in 221-1
> #  * https://github.com/systemd/systemd/issues/2477
> #  * remote status changed: open -> closed
> #  * closed upstream
> tags 794721 + fixed-upstream
Bug #794721 [udev] udev_queue_get_udev_is_active API is broken starting in 221-1
Added tag(s) fixed-upstream.
> usertags 794721 - status-open
Usertags were: status-open.
Usertags are now: .
> usertags 794721 + status-closed
There were no usertags set.
Usertags are now: status-closed.
> # remote status report for #832713 (http://bugs.debian.org/832713)
> # Bug title: systemd: after "systemd (231-1) unstable" update 
> systemd-jurnald.service fails to start
> #  * https://github.com/systemd/systemd/issues/3882
> #  * remote status changed: open -> closed
> #  * closed upstream
> tags 832713 + fixed-upstream
Bug #832713 [systemd] systemd: after "systemd (231-1) unstable" update 
systemd-jurnald.service fails to start
Bug #832893 [systemd] Failed at step SECCOMP spawning systemd-networkd
Added tag(s) fixed-upstream.
Added tag(s) fixed-upstream.
> usertags 832713 - status-open
Usertags were: status-open.
Usertags are now: .
> usertags 832713 + status-closed
There were no usertags set.
Usertags are now: status-closed.
> # remote status report for #832893 (http://bugs.debian.org/832893)
> # Bug title: Failed at step SECCOMP spawning systemd-networkd
> #  * https://github.com/systemd/systemd/issues/3882
> #  * remote status changed: open -> closed
> #  * closed upstream
> tags 832893 + fixed-upstream
Bug #832893 [systemd] Failed at step SECCOMP spawning systemd-networkd
Bug #832713 [systemd] systemd: after "systemd (231-1) unstable" update 
systemd-jurnald.service fails to start
Ignoring request to alter tags of bug #832893 to the same tags previously set
Ignoring request to alter tags of bug #832713 to the same tags previously set
> usertags 832893 - status-open
Usertags were: status-open.
Usertags are now: .
> usertags 832893 + status-closed
There were no usertags set.
Usertags are now: status-closed.
> thanks
Stopping processing here.

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

Bug#835980: triggerhappy: FTBFS: evtable_SW.inc:17:8: error: array index in initializer exceeds array bounds

[Chris Lamb]

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

Dear Maintainer,

triggerhappy fails to build from source in unstable/amd64:

  [..]

  
  
**
  ** Starting build 
  **
  
**
  
   Package:  triggerhappy
   Version:  0.4.0-2
   Build architecture:   amd64
   Date: Mon, 29 Aug 2016 18:12:30 +0100
   Hostname: 664a26da6444
   Uname:Linux 664a26da6444 4.6.0-1-amd64 #1 SMP Debian 4.6.4-1 
(2016-07-18) x86_64 GNU/Linux
   /etc/timezone:Europe/London
  
  
**
  ** 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 'triggerhappy-build-deps' in 
'../triggerhappy-build-deps_0.4.0-2_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 triggerhappy-build-deps.
  (Reading database ... 23302 files and directories currently installed.)
  Preparing to unpack triggerhappy-build-deps_0.4.0-2_all.deb ...
  Unpacking triggerhappy-build-deps (0.4.0-2) ...
  Reading package lists...
  Building dependency tree...
  Reading state information...
  Correcting dependencies... Done
  The following additional packages will be installed:
libsystemd-dev pkg-config
  The following NEW packages will be installed:
libsystemd-dev pkg-config
  0 upgraded, 2 newly installed, 0 to remove and 0 not upgraded.
  1 not fully installed or removed.
  Need to get 287 kB of archives.
  After this operation, 827 kB of additional disk space will be used.
  Get:1 http://httpredir.debian.org/debian sid/main amd64 pkg-config amd64 
0.29-4 [62.5 kB]
  Get:2 http://httpredir.debian.org/debian sid/main amd64 libsystemd-dev amd64 
231-5 [224 kB]
  Fetched 287 kB in 0s (22.8 MB/s)
  Selecting previously unselected package pkg-config.
  (Reading database ... 
(Reading database ... 5%
(Reading database ... 10%
(Reading database ... 15%
(Reading database ... 20%
(Reading database ... 25%
(Reading database ... 30%
(Reading database ... 35%
(Reading database ... 40%
(Reading database ... 45%
(Reading database ... 50%
(Reading database ... 55%
(Reading database ... 60%
(Reading database ... 65%
(Reading database ... 70%
(Reading database ... 75%
(Reading database ... 80%
(Reading database ... 85%
(Reading database ... 90%
(Reading database ... 95%
(Reading database ... 100%
(Reading database ... 23306 files and directories currently installed.)
  Preparing to unpack .../0-pkg-config_0.29-4_amd64.deb ...
  Unpacking pkg-config (0.29-4) ...
  Selecting previously unselected package libsystemd-dev:amd64.
  Preparing to unpack .../1-libsystemd-dev_231-5_amd64.deb ...
  Unpacking libsystemd-dev:amd64 (231-5) ...
  Setting up pkg-config (0.29-4) ...
  Processing triggers for man-db (2.7.5-1) ...
  Setting up libsystemd-dev:amd64 (231-5) ...
  Setting up triggerhappy-build-deps (0.4.0-2) ...
  
  
**
  ** Environment
  **
  
**
  
  
PATH=/home/lamby/git/projects/dotfiles/dotfiles/..//bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin
  HOSTNAME=664a26da6444
  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.20160829181228.8nOvYn1exW.db.triggerhappy/triggerhappy-0.4.0
  OLDPWD=/home/lamby/temp/cdt.20160829181228.8nOvYn1exW.db.triggerhappy
  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
  GPG_KEY=1E953E27D4311E58
  BLASTER=A220 I5 D1 H5 P330 T6
  _=/usr/bin/env
  
  
**
  ** Building triggerhappy 0.4.0-2 on amd64 

Processed: found 834893 in 1.4.18-7

[Debian Bug Tracking System]

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

> found 834893 1.4.18-7
Bug #834893 [src:gnupg] gnupg: CVE-2016-6313: RNG prediction vulnerability
Marked as found in versions gnupg/1.4.18-7.
> thanks
Stopping processing here.

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

Processed: fixed 834894 in 1.4.21-1

[Debian Bug Tracking System]

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

> fixed 834894 1.4.21-1
Bug #834894 [src:gnupg1] gnupg1: CVE-2016-6313: RNG prediction vulnerability
The source 'gnupg1' and version '1.4.21-1' do not appear to match any binary 
packages
Marked as fixed in versions gnupg1/1.4.21-1.
> thanks
Stopping processing here.

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

Processed: reopening 834893

[Debian Bug Tracking System]

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

> reopen 834893
Bug #834893 {Done: Daniel Kahn Gillmor } [src:gnupg] 
gnupg: CVE-2016-6313: RNG prediction vulnerability
'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 gnupg/1.4.18-7+deb8u2 and gnupg1/1.4.21-1.
> thanks
Stopping processing here.

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

Processed: closing 834894

[Debian Bug Tracking System]

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

> close 834894 1.4.21-1
Bug #834894 [src:gnupg1] gnupg1: CVE-2016-6313: RNG prediction vulnerability
The source 'gnupg1' and version '1.4.21-1' do not appear to match any binary 
packages
Ignoring request to alter fixed versions of bug #834894 to the same values 
previously set
Bug #834894 [src:gnupg1] gnupg1: CVE-2016-6313: RNG prediction vulnerability
Marked Bug as done
> thanks
Stopping processing here.

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

Bug#834894: closing 834894

[Salvatore Bonaccorso]

close 834894 1.4.21-1
thanks

Processed: fixed 834893 in 1.4.18-7+deb8u2

[Debian Bug Tracking System]

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

> fixed 834893 1.4.18-7+deb8u2
Bug #834893 [src:gnupg] gnupg: CVE-2016-6313: RNG prediction vulnerability
Marked as fixed in versions gnupg/1.4.18-7+deb8u2.
> thanks
Stopping processing here.

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

Processed: notfixed 834893 in gnupg1/1.4.21-1

[Debian Bug Tracking System]

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

> notfixed 834893 gnupg1/1.4.21-1
Bug #834893 [src:gnupg] gnupg: CVE-2016-6313: RNG prediction vulnerability
The source gnupg1 and version 1.4.21-1 do not appear to match any binary 
packages
Ignoring request to alter fixed versions of bug #834893 to the same values 
previously set
> thanks
Stopping processing here.

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

Bug#835872: marked as done (redeclipse-common: Fails to upgrade due to undeclare file conflict: trying to overwrite '/usr/share/doc/redeclipse/guidelines.txt', which is also in package redeclipse 1.5.

[Debian Bug Tracking System]

Your message dated Mon, 29 Aug 2016 16:29:59 +
with message-id 
and subject line Bug#835872: fixed in redeclipse 1.5.5-2
has caused the Debian Bug report #835872,
regarding redeclipse-common: Fails to upgrade due to undeclare file conflict: 
trying to overwrite '/usr/share/doc/redeclipse/guidelines.txt', which is also 
in package redeclipse 1.5.1-2
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.)


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

Dear Maintainer,

upgrading redeclipse-common from 1.5.1-2 to 1.5.5-1 fails for me as
follows:

Unpacking redeclipse-common (1.5.5-1) over (1.5.1-2) ...
dpkg: error processing archive 
/tmp/apt-dpkg-install-R5cuNe/15-redeclipse-common_1.5.5-1_all.deb (--unpack):
 trying to overwrite '/usr/share/doc/redeclipse/guidelines.txt', which is also 
in package redeclipse 1.5.1-2

There seem to be Breaks/Replaces header missing for moving that file
(and maybe further ones) from redeclipse to redeclipse-common.

-- System Information:
Debian Release: stretch/sid
  APT prefers unstable
  APT policy: (990, 'unstable'), (600, 'testing'), (500, 'unstable-debug'), 
(500, 'buildd-unstable'), (110, 'experimental'), (1, 'experimental-debug'), (1, 
'buildd-experimental')
Architecture: amd64 (x86_64)

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

-- no debconf information
--- End Message ---
--- Begin Message ---
Source: redeclipse
Source-Version: 1.5.5-2

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

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

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Mon, 29 Aug 2016 15:21:11 +0200
Source: redeclipse
Binary: redeclipse redeclipse-server redeclipse-common
Architecture: source
Version: 1.5.5-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Games Team 
Changed-By: Markus Koschany 
Description:
 redeclipse - free, casual arena shooter
 redeclipse-common - common config files for the Red Eclipse FPS game
 redeclipse-server - server for the Red Eclipse FPS game
Closes: 835872
Changes:
 redeclipse (1.5.5-2) unstable; urgency=medium
 .
   * Team upload.
   * redeclipse-common: Add Breaks and Replaces to fix dpkg failure on upgrade.
 Thanks to Axel Beckert for the report. (Closes: #835872)
Checksums-Sha1:
 d00e8a67fb6fd090a73c7f621e21315dfb97548a 2348 redeclipse_1.5.5-2.dsc
 78fc005c3b169e8a4a9827d5fb7d6f8d6e9139b0 16044 redeclipse_1.5.5-2.debian.tar.xz
Checksums-Sha256:
 8365eab6e68f724956a9897763cf2417e89f6e936a9ea41c8034f8864426422c 2348 
redeclipse_1.5.5-2.dsc
 7c7677bce6c06cccf377a79018333e9dc97e30123e6858580ab92faf89fbfc2b 16044 
redeclipse_1.5.5-2.debian.tar.xz
Files:
 f7d53a953e66ed21243ed0f3fd489788 2348 games optional redeclipse_1.5.5-2.dsc
 b40f1136bf2e812f24fc4920b9766a8f 16044 games optional 
redeclipse_1.5.5-2.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQKMBAEBCgB2BQJXxD7OXxSAAC4AKGlzc3Vlci1mcHJAbm90YXRpb25zLm9w
ZW5wZ3AuZmlmdGhob3JzZW1hbi5uZXRBQ0YzRDA4OEVGMzJFREVGNkExQTgzNUZE
OUFEMTRCOTUxM0I1MUU0DxxhcG9AZGViaWFuLm9yZwAKCRDZrRS5UTtR5OPZD/91
cZyWHkw7qM870Re+5Hin0cpB2KAHrGHrlJpNgKTGtiC9Zk0YrVj+Qc5LsCkWoB8A
k1Nowb+DEsUDB+6OlurHY5tYFmI0IswIQdyFOUkUSTyDX4jkaTOdP4rvL1pPzrqv
lykt2FLESHgFMwBKvb0TSExHIMDKhKKdy7GvxqjMFaPakAkuhfzOpZ/nYwYmpCS5
ZLzf97L9cZL/yHB3fKf6YfQVz3W+/aBpwgoV/RH4WNaFGm+TCOX8t6DSwOLrObvz
9TknKxfP3okLAwjnPO35XdtVAAdaz66+QiskvGIi1Tn5zfjydzpGnRd1RMQVkCTE
obzpk1cX2armGQ57mbhukPuMKB1JM1d8LaQ4tcHwbsQY64ynleiAg8X6fKg+jDxW
QDN3949e3NwOA+x6y2lgDzihRYQ/zwBUU2tcJuJmYYIeoDffhz7Y2u2lZVaKUy96
UobPdUFOa0RG4iVMgBemruT6rw0AjqbUH31ZU9wAnjvY8u9rPOLcQNdtA6F+xucr
HrVLtdqBxlE8rNPJTgoHfV4cQdt23oOhc149BlR9Qsx0XCt9lK8IG3OITRn0yycY
6inHgfq4HSRsol0XwlsY3wBifro+fi35Y95J7+XBVx70MEdl5VD616pcKNnLkxxk
Sv++KFNgEKt4aiqJoQUZr+Tx4ClzwgDFhD+

Bug#817676: marked as done (spellcast: Removal of debhelper compat 4)

[Debian Bug Tracking System]

Your message dated Mon, 29 Aug 2016 16:30:13 +
with message-id 
and subject line Bug#817676: fixed in spellcast 1.0-22
has caused the Debian Bug report #817676,
regarding spellcast: Removal of debhelper compat 4
to be marked as done.

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

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


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

Hi,

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

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

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

Thanks,
~Niels

[1] https://lists.debian.org/debian-devel/2015/09/msg00257.html
--- End Message ---
--- Begin Message ---
Source: spellcast
Source-Version: 1.0-22

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

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

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

Debian distribution maintenance software
pp.
Javier Fernández-Sanguino Peña  (supplier of updated spellcast 
package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Mon, 29 Aug 2016 16:37:56 +0200
Source: spellcast
Binary: spellcast
Architecture: source i386
Version: 1.0-22
Distribution: unstable
Urgency: medium
Maintainer: Javier Fernández-Sanguino Peña 
Changed-By: Javier Fernández-Sanguino Peña 
Description:
 spellcast  - Classic hand-waving multi-player game of spellcasting
Closes: 817676
Changes:
 spellcast (1.0-22) unstable; urgency=medium
 .
   * After 10 years without changes, this new version introduces some general
 changes to use newer debhelper compatibility versions. Maybe it will
 be sufficient to keep this old game in the archive for years to come.
 (Closes: #817676)
   * debian/control:
 - Update Standards Version
 - Upgrade to debhelper version 9
 - Update maintainer's name, use proper UTF-8 encoding
   * debian/NEWS: proper formatting
   * debian/README.debian:
- Changes to reflect the current situation (only 1024x768 version
  shipped)
- Provide an alternative way to run the program without opening
  an X11 TCP socket using socat.
- Point to the content to reflect that this version is not being
  updated any more but other alternatives exist.
   * spellcast.6: Add a link to the original's author webpage of this game
   * debian/spellcast.docs: List all the documents to install
   * debian/spellcast.manpages: List the manpages to install
   * debian/spellcast.man.html: Remove as this is not really required this day
 and age.
   * debian/rules:
   - Adapt to use debhelper with only a few overrides
   - Do not ship a version for 800x600 displays anymore, just keep the
 default (1024x768)
   * debian/postinst: Fix lintian warnings
   * spellcast.6: Remove undefined macro
Checksums-Sha1:
 2c597d3e472a736b3da88bd85fcfc3e71ea67832 1702 spellcast_1.0-22.dsc
 8c267cf3050ae00f7233d94ac72494f6db8a59d1 66828 spellcast_1.0-22.diff.gz
 b935017b108209c6989560dec4ef12f1309bc626 79012 spellcast_1.0-22_i386.deb
Checksums-Sha256:
 91281f5b9f32000fb3666dccb65cd2b9cd6b80c6544331928746e0ed14f30e72 1702 
spellcast_1.0-22.dsc
 2813c3137bd9d70f2c359991aa242e5b5603c0fcc290ccf6a7c6bcd02df2168b 66828 
spellcast_1.0-22.diff.gz
 2e164b2fb354e5ea27e11aa55d3569d4ddf00d26af4e92125c3d1aff3187698c 79012 
spellcast_1.0-22_i386.deb
Files:
 31524b394e67cef427520397b6e77561 1702 non-free/games optional 
spellcast_1.0-22.dsc
 3af6cde7e2357424d4aa2f960d96bd12 66828 non-free/games optional 
spellcast_1.0-22.diff.gz
 536c995d7f753e3f21fcc6699b6010aa 79012 non-free/games optional 
spellcast_1.0-22_i386.deb

-BEGIN PGP SIGNATURE-
Version: GnuPG v1

iQIVAwUBV8ROQ4sfb0irJX+YAQinwg//SniiPJSOIKYfzZqh1Mhqg

Bug#834757: marked as done (Breaks between gnupg1 and gnupg currently break bootstrapping of stretch)

[Debian Bug Tracking System]

Your message dated Mon, 29 Aug 2016 16:21:10 +
with message-id 
and subject line Bug#834757: fixed in gnupg1 1.4.21-1
has caused the Debian Bug report #834757,
regarding Breaks between gnupg1 and gnupg currently break bootstrapping of 
stretch
to be marked as done.

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

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


-- 
834757: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=834757
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: gnupg1
Version: 1.4.20-7
Severity: serious

Hi!

Testing currently has this: [0] [1]

gnupg  => 1.4.20-6
gnupg1 => 1.4.20-7

Those versions are incompatible. [2]

However, gnupg1 still has Priority: important [3] which means
debootstrap will install it per default. Since the gnupg package is
also installed because of some dependencies, this currently breaks
bootstrapping stretch.

I have attached a full log of a failed debootstrap, but you should be
able to easily reproduce this by trying to debootstrap stretch.

Best regards

Alexander Kurtz

[0] https://tracker.debian.org/pkg/gnupg
[1] https://tracker.debian.org/pkg/gnupg1
[2] 
https://anonscm.debian.org/cgit/pkg-gnupg/gnupg1.git/tree/debian/control?h=debian/1.4.20-7#n38
[3] 
https://anonscm.debian.org/cgit/pkg-gnupg/gnupg1.git/tree/debian/control?h=debian/1.4.20-7#n3root@shepard:~# debootstrap stretch /tmp/chroot
I: Retrieving Release 
I: Retrieving Release.gpg 
I: Checking Release signature
I: Valid Release signature (key id 126C0D24BD8A2942CC7DF8AC7638D0442B90D010)
I: Retrieving Packages 
I: Validating Packages 
I: Resolving dependencies of required packages...
I: Resolving dependencies of base packages...
I: Found additional required dependencies: libaudit-common libaudit1 libbz2-1.0 libcap-ng0 libdb5.3 libdebconfclient0 libgcrypt20 libgpg-error0 libncursesw5 libsemanage-common libsemanage1 libsystemd0 libudev1 libustr-1.0-1 
I: Found additional base dependencies: dmsetup libapparmor1 libbsd0 libcap2 libcap2-bin libcryptsetup4 libdevmapper1.02.1 libdns-export162 libffi6 libgmp10 libgnutls30 libhogweed4 libicu57 libidn11 libip4tc0 libip6tc0 libiptc0 libisc-export160 libjson-c3 liblocale-gettext-perl liblz4-1 libmnl0 libnetfilter-conntrack3 libnettle6 libnfnetlink0 libp11-kit0 libpsl5 libseccomp2 libtasn1-6 libtext-charwidth-perl libtext-iconv-perl libtext-wrapi18n-perl 
I: Checking component main on http://httpredir.debian.org/debian...
I: Retrieving libacl1 2.2.52-3
I: Validating libacl1 2.2.52-3
I: Retrieving adduser 3.115
I: Validating adduser 3.115
I: Retrieving libapparmor1 2.10.95-4
I: Validating libapparmor1 2.10.95-4
I: Retrieving apt 1.3~rc1
I: Validating apt 1.3~rc1
I: Retrieving apt-utils 1.3~rc1
I: Validating apt-utils 1.3~rc1
I: Retrieving libapt-inst2.0 1.3~rc1
I: Validating libapt-inst2.0 1.3~rc1
I: Retrieving libapt-pkg5.0 1.3~rc1
I: Validating libapt-pkg5.0 1.3~rc1
I: Retrieving libattr1 1:2.4.47-2
I: Validating libattr1 1:2.4.47-2
I: Retrieving libaudit-common 1:2.6.5-1
I: Validating libaudit-common 1:2.6.5-1
I: Retrieving libaudit1 1:2.6.5-1
I: Validating libaudit1 1:2.6.5-1
I: Retrieving base-files 9.6
I: Validating base-files 9.6
I: Retrieving base-passwd 3.5.39
I: Validating base-passwd 3.5.39
I: Retrieving bash 4.3-15
I: Validating bash 4.3-15
I: Retrieving libdns-export162 1:9.10.3.dfsg.P4-10.1
I: Validating libdns-export162 1:9.10.3.dfsg.P4-10.1
I: Retrieving libisc-export160 1:9.10.3.dfsg.P4-10.1
I: Validating libisc-export160 1:9.10.3.dfsg.P4-10.1
I: Retrieving blends-tasks 0.6.93
I: Validating blends-tasks 0.6.93
I: Retrieving libboost-iostreams1.60.0 1.60.0+dfsg-6+b1
I: Validating libboost-iostreams1.60.0 1.60.0+dfsg-6+b1
I: Retrieving bsdmainutils 9.0.10
I: Validating bsdmainutils 9.0.10
I: Retrieving libbz2-1.0 1.0.6-8
I: Validating libbz2-1.0 1.0.6-8
I: Retrieving libdebconfclient0 0.215
I: Validating libdebconfclient0 0.215
I: Retrieving coreutils 8.25-2
I: Validating coreutils 8.25-2
I: Retrieving cpio 2.11+dfsg-5
I: Validating cpio 2.11+dfsg-5
I: Retrieving cron 3.0pl1-128
I: Validating cron 3.0pl1-128
I: Retrieving libcryptsetup4 2:1.7.0-2
I: Validating libcryptsetup4 2:1.7.0-2
I: Retrieving dash 0.5.8-2.3
I: Validating dash 0.5.8-2.3
I: Retrieving libdb5.3 5.3.28-12
I: Validating libdb5.3 5.3.28-12
I: Retrieving debconf 1.5.59
I: Validating debconf 1.5.59
I: Retrieving debconf-i18n 1.5.59
I: Validating debconf-i18n 1.5.59
I: Retrieving debian-archive-keyring 2014.3
I: Validating debian-archive-keyring 2014.3
I: Retrieving debianutils 4.8
I: Validating debianutils 4.8
I: Retrieving diffutils 1:3.3-3
I: Validating diffutils 1:3.3-3
I: Retrieving dmidecode 3.0-3
I: Validat

Bug#834893: marked as done (gnupg: CVE-2016-6313: RNG prediction vulnerability)

[Debian Bug Tracking System]

Your message dated Mon, 29 Aug 2016 16:21:10 +
with message-id 
and subject line Bug#834893: fixed in gnupg1 1.4.21-1
has caused the Debian Bug report #834893,
regarding gnupg: CVE-2016-6313: RNG prediction vulnerability
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.)


-- 
834893: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=834893
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: gnupg
Version: 1.4.12-1
Severity: grave
Tags: security upstream patch fixed-upstream
Control: fixed -1 1.4.18-7+deb8u2

Hi,

the following vulnerability was published for gnupg.

CVE-2016-6313[0]:
libgcrypt: PRNG output is predictable

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

For further information see:

[0] https://security-tracker.debian.org/tracker/CVE-2016-6313

Regards,
Salvatore
--- End Message ---
--- Begin Message ---
Source: gnupg1
Source-Version: 1.4.21-1

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

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Mon, 29 Aug 2016 10:03:15 -0400
Source: gnupg1
Binary: gnupg1 gnupg1-curl gpgv1 gpgv1.4-udeb gnupg1-l10n
Architecture: source
Version: 1.4.21-1
Distribution: unstable
Urgency: medium
Maintainer: Debian GnuPG-Maintainers 
Changed-By: Daniel Kahn Gillmor 
Description:
 gnupg1 - GNU privacy guard - a free PGP replacement ("classic" version)
 gnupg1-curl - GNU privacy guard - a free PGP replacement (cURL helpers for "cla
 gnupg1-l10n - GNU privacy guard "classic" - localization files
 gpgv1  - GNU privacy guard - signature verification tool ("classic" versio
 gpgv1.4-udeb - minimal signature verification tool (udeb)
Closes: 806494 834757 834893
Changes:
 gnupg1 (1.4.21-1) unstable; urgency=medium
 .
   * new upstream release (Closes: #834893)
   * drop already upstreamed patches, refresh remainder
   * build reproducibly (Closes: #806494)
   * gnupg1 is Priority: extra (Closes: #834757)
Checksums-Sha1:
 dd110e2a95020d1f765cdd4d4e7a5f96d5ad5534 2474 gnupg1_1.4.21-1.dsc
 e3bdb585026f752ae91360f45c28e76e4a15d338 3689305 gnupg1_1.4.21.orig.tar.bz2
 0669b04a617b7d91c1e69d7565748efa6393eba4 32836 gnupg1_1.4.21-1.debian.tar.xz
Checksums-Sha256:
 9c0b7672cf68070b715a9694d656bc759b790b4754252046a33b4d06c083e51c 2474 
gnupg1_1.4.21-1.dsc
 6b47a3100c857dcab3c60e6152e56a997f2c7862c1b8b2b25adf3884a1ae2276 3689305 
gnupg1_1.4.21.orig.tar.bz2
 20648f68e91b54e7cabbec6cf219be70b6a84c2d8ead4522077a227f1f3717a0 32836 
gnupg1_1.4.21-1.debian.tar.xz
Files:
 8e76e0b7deded18e37b615db34d1e14a 2474 utils extra gnupg1_1.4.21-1.dsc
 9bdeabf3c0f87ff21cb3f9216efdd01d 3689305 utils extra gnupg1_1.4.21.orig.tar.bz2
 3ff8c347d12a2d55685beffb8dfe9739 32836 utils extra 
gnupg1_1.4.21-1.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQKTBAEBCgB9BQJXxErOXxSAAC4AKGlzc3Vlci1mcHJAbm90YXRpb25zLm9w
ZW5wZ3AuZmlmdGhob3JzZW1hbi5uZXRFREIyRTc0RjU2RkNGMkI2NzI5N0I3MzUy
NEVDRkY1QUZGNjgzNzBBFhxka2dAZmlmdGhob3JzZW1hbi5uZXQACgkQJOz/Wv9o
NwqJbw/+LJRypGZjQQdOEb5LXkUolyNmKL90nRf30p4ANFnaXgLsMnyIt2PreU5y
SL/bTfzzlPu0CzRll1/qmyvRVOh4To6UepbmdE9T9fzqduzmXUrl1ijs3pD6lv19
NmXNuYDgyWdyOpbTmYdPPKhUqalEwusFSl7W2+jFCCKcINrM+v7cwVnGqQEt3U7m
onICZVXZLrxbdrT6dgp4JRzvMT/cKdPgsMSJM1oxZ0tHJyflqQKb+WLyFLxPvJgL
NzOha/aCpyAN0L9NlnBgjYMRk5VXWAXS/iCBlBmXAG9rDhYZnQjEaV/OyUOaae2E
AhdC1MdgPJFVqWQDe0sraUAmeKUlsl1Adu/AQCUYLhqZCr/VdNuaTB/LW4dlTg/P
J46cEPuW+1xyceKRWATrV93hkX0eZc1OrhtRNjfFbexNfY4r54jut9g5CLTC7Lbd
57Kmyg9WqUXKUjs2XeU931tHCGrWm1uJxNWNT8GOMqKl+M5hRXfvepBA2wI4Ugy6
uv/6+/bzu9nDzlmfOTjyeqj0YQENRk8jnffCZdfSWzcEirD6QLCzlsVUkMkse9/U
Pg8Rsa0J0m7AyDEPvHAqfNE03jVY7anHU7dr1iyK5phOjaibnC7in3jkQ2TBTlo7
eGixaK0/SY3DDRoOljXwapwMSDhR5DIeUgn55cz5AD/TFbwVI0s=
=kj7I
-END PGP SIGNATURE End Message ---

Bug#833930: Problem went away

[Oleg Pudeyev]

Gitk now renders properly for me.

I believe I uninstalled libx11-6 and all dependent packages then
reinstalled everything in one go. I did some apt-get upgrades before
and/or after that too.

There was no change in gitk behavior within the existing X session,
however after restarting the computer gitk started rendering itself
correctly.

Processed: tagging 834893

[Debian Bug Tracking System]

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

> tags 834893 - pending
Bug #834893 [src:gnupg] gnupg: CVE-2016-6313: RNG prediction vulnerability
Removed tag(s) pending.
> thanks
Stopping processing here.

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

Bug#832713: systemd: after "systemd (231-1) unstable" update systemd-jurnald.service fails to start

[Felipe Sateler]

On 29 August 2016 at 12:10, Pete Batard  wrote:
> Please find my boot log. Note that I've tried commenting out
> 'MemoryDenyWriteExecute=yes' in the various .service config files, but it
> didn't help.
>
> If you need anything else, please let me know.

This log is not verbose. Could you boot with kernel argument
systemd.log_level=debug ?

Also, on the arm machine could you attach the contents of /proc/self/status ?

-- 
Saludos,
Felipe Sateler

Bug#832713: systemd: after "systemd (231-1) unstable" update systemd-jurnald.service fails to start

[Pete Batard]

Please find my boot log. Note that I've tried commenting out 
'MemoryDenyWriteExecute=yes' in the various .service config files, but 
it didn't help.


If you need anything else, please let me know.

Regards,

/Pete
[0.00] Booting Linux on physical CPU 0xf00
[0.00] Initializing cgroup subsys cpuset
[0.00] Initializing cgroup subsys cpu
[0.00] Initializing cgroup subsys cpuacct
[0.00] Linux version 4.4.19-v7+ (dc4@dc4-XPS13-9333) (gcc version 4.9.3 
(crosstool-NG crosstool-ng-1.22.0-88-g8460611) ) #906 SMP Tue Aug 23 15:53:06 
BST 2016
[0.00] CPU: ARMv7 Processor [410fc075] revision 5 (ARMv7), cr=10c5387d
[0.00] CPU: PIPT / VIPT nonaliasing data cache, VIPT aliasing 
instruction cache
[0.00] Machine model: Raspberry Pi 2 Model B Rev 1.1
[0.00] cma: Reserved 8 MiB at 0x3a80
[0.00] Memory policy: Data cache writealloc
[0.00] On node 0 totalpages: 241664
[0.00] free_area_init_node: node 0, pgdat 808c2f40, node_mem_map 
b9fa6000
[0.00]   Normal zone: 2124 pages used for memmap
[0.00]   Normal zone: 0 pages reserved
[0.00]   Normal zone: 241664 pages, LIFO batch:31
[0.00] [bcm2709_smp_init_cpus] enter (9520->f3003010)
[0.00] [bcm2709_smp_init_cpus] ncores=4
[0.00] PERCPU: Embedded 13 pages/cpu @b9f62000 s22592 r8192 d22464 
u53248
[0.00] pcpu-alloc: s22592 r8192 d22464 u53248 alloc=13*4096
[0.00] pcpu-alloc: [0] 0 [0] 1 [0] 2 [0] 3 
[0.00] Built 1 zonelists in Zone order, mobility grouping on.  Total 
pages: 239540
[0.00] Kernel command line: dma.dmachans=0x7f35 bcm2708_fb.fbwidth=1680 
bcm2708_fb.fbheight=1050 bcm2709.boardrev=0x2a01041 bcm2709.serial=0x66b48257 
smsc95xx.macaddr=B8:27:EB:B4:82:57 bcm2708_fb.fbswap=1 
bcm2709.uart_clock=4800 bcm2709.disk_led_gpio=47 
bcm2709.disk_led_active_low=0 vc_mem.mem_base=0x3dc0 
vc_mem.mem_size=0x3f00  dwc_otg.lpm_enable=0 console=ttyAMA0,115200 
console=tty1 root=/dev/mmcblk0p2 rootwait net.ifnames=1
[0.00] PID hash table entries: 4096 (order: 2, 16384 bytes)
[0.00] Dentry cache hash table entries: 131072 (order: 7, 524288 bytes)
[0.00] Inode-cache hash table entries: 65536 (order: 6, 262144 bytes)
[0.00] Memory: 939076K/966656K available (6348K kernel code, 432K 
rwdata, 1716K rodata, 476K init, 764K bss, 19388K reserved, 8192K cma-reserved)
[0.00] Virtual kernel memory layout:
   vector  : 0x - 0x1000   (   4 kB)
   fixmap  : 0xffc0 - 0xfff0   (3072 kB)
   vmalloc : 0xbb80 - 0xff80   (1088 MB)
   lowmem  : 0x8000 - 0xbb00   ( 944 MB)
   modules : 0x7f00 - 0x8000   (  16 MB)
 .text : 0x80008000 - 0x807e8510   (8066 kB)
 .init : 0x807e9000 - 0x8086   ( 476 kB)
 .data : 0x8086 - 0x808cc250   ( 433 kB)
  .bss : 0x808cf000 - 0x8098e1ec   ( 765 kB)
[0.00] SLUB: HWalign=64, Order=0-3, MinObjects=0, CPUs=4, Nodes=1
[0.00] Hierarchical RCU implementation.
[0.00]  Build-time adjustment of leaf fanout to 32.
[0.00] NR_IRQS:16 nr_irqs:16 16
[0.00] Architected cp15 timer(s) running at 19.20MHz (phys).
[0.00] clocksource: arch_sys_counter: mask: 0xff 
max_cycles: 0x46d987e47, max_idle_ns: 440795202767 ns
[0.07] sched_clock: 56 bits at 19MHz, resolution 52ns, wraps every 
4398046511078ns
[0.21] Switching to timer-based delay loop, resolution 52ns
[0.000249] Console: colour dummy device 80x30
[0.001031] console [tty1] enabled
[0.001069] Calibrating delay loop (skipped), value calculated using timer 
frequency.. 38.40 BogoMIPS (lpj=192000)
[0.001121] pid_max: default: 32768 minimum: 301
[0.001408] Mount-cache hash table entries: 2048 (order: 1, 8192 bytes)
[0.001443] Mountpoint-cache hash table entries: 2048 (order: 1, 8192 bytes)
[0.002303] Disabling cpuset control group subsystem
[0.002365] Initializing cgroup subsys io
[0.002408] Initializing cgroup subsys memory
[0.002466] Initializing cgroup subsys devices
[0.002504] Initializing cgroup subsys freezer
[0.002536] Initializing cgroup subsys net_cls
[0.002603] CPU: Testing write buffer coherency: ok
[0.002685] ftrace: allocating 21217 entries in 63 pages
[0.037656] CPU0: update cpu_capacity 1024
[0.037712] CPU0: thread -1, cpu 0, socket 15, mpidr 8f00
[0.037739] [bcm2709_smp_prepare_cpus] enter
[0.037858] Setting up static identity map for 0x8240 - 0x8274
[0.039516] [bcm2709_boot_secondary] cpu:1 started (0) 16
[0.039854] [bcm2709_secondary_init] enter cpu:1
[0.039898] CPU1: update cpu_capacity 1024
[0.039904] CPU1: thread -1, cpu 1, socket 15, mpidr 8f01
[0.040305] [bcm2709_boot_secondary] cpu:2 started (0) 17
[0.04057

Processed: Bug#834893 marked as pending

[Debian Bug Tracking System]

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

> tag 834893 pending
Bug #834893 [src:gnupg] gnupg: CVE-2016-6313: RNG prediction vulnerability
Added tag(s) pending.
> thanks
Stopping processing here.

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

Bug#834893: marked as pending

[Daniel Kahn Gillmor]

tag 834893 pending
thanks

Hello,

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

http://git.debian.org/?p=pkg-gnupg/gnupg1.git;a=commitdiff;h=2147d7b

---
commit 2147d7bd53244662453cffc9c25604e2e265a2ca
Author: Daniel Kahn Gillmor 
Date:   Mon Aug 29 10:04:21 2016 -0400

prepare release

diff --git a/debian/changelog b/debian/changelog
index 586c73e..a0c099f 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,3 +1,12 @@
+gnupg1 (1.4.21-1) unstable; urgency=medium
+
+  * new upstream release (Closes: #834893)
+  * drop already upstreamed patches, refresh remainder
+  * build reproducibly (Closes: #806494)
+  * gnupg1 is Priority: extra (Closes: #834757)
+
+ -- Daniel Kahn Gillmor   Mon, 29 Aug 2016 10:03:15 
-0400
+
 gnupg1 (1.4.20-7) unstable; urgency=medium
 
   * Release to unstable.

Processed: Bug#834757 marked as pending

[Debian Bug Tracking System]

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

> tag 834757 pending
Bug #834757 [gnupg1] Breaks between gnupg1 and gnupg currently break 
bootstrapping of stretch
Added tag(s) pending.
> thanks
Stopping processing here.

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

Bug#834757: marked as pending

[Daniel Kahn Gillmor]

tag 834757 pending
thanks

Hello,

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

http://git.debian.org/?p=pkg-gnupg/gnupg1.git;a=commitdiff;h=2147d7b

---
commit 2147d7bd53244662453cffc9c25604e2e265a2ca
Author: Daniel Kahn Gillmor 
Date:   Mon Aug 29 10:04:21 2016 -0400

prepare release

diff --git a/debian/changelog b/debian/changelog
index 586c73e..a0c099f 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,3 +1,12 @@
+gnupg1 (1.4.21-1) unstable; urgency=medium
+
+  * new upstream release (Closes: #834893)
+  * drop already upstreamed patches, refresh remainder
+  * build reproducibly (Closes: #806494)
+  * gnupg1 is Priority: extra (Closes: #834757)
+
+ -- Daniel Kahn Gillmor   Mon, 29 Aug 2016 10:03:15 
-0400
+
 gnupg1 (1.4.20-7) unstable; urgency=medium
 
   * Release to unstable.

Processed: re: s/XML_NO_ERROR/XML_SUCCESS/

[Debian Bug Tracking System]

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

> tags 835427 +patch
Bug #835427 [src:gazebo] gazebo: FTBFS in unstable (error: 'XML_NO_ERROR' is 
not a member of 'tinyxml2')
Added tag(s) patch.
> thanks
Stopping processing here.

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

Bug#835427: s/XML_NO_ERROR/XML_SUCCESS/

[Peter Michael Green]

tags 835427 +patch
thanks

Older versions of tinyxml defined both XML_NO_ERROR and XML_SUCCESS to 0. Never
versions define only XML_SUCCESS.


Attatched is a patch that replaces XML_NO_ERROR with XML_SUCCESS


diff -Nru gazebo-7.3.0+dfsg/debian/changelog gazebo-7.3.0+dfsg/debian/changelog
--- gazebo-7.3.0+dfsg/debian/changelog  2016-07-21 15:33:10.0 +
+++ gazebo-7.3.0+dfsg/debian/changelog  2016-08-27 16:02:33.0 +
@@ -1,3 +1,9 @@
+gazebo (7.3.0+dfsg-2+rpi1) stretch-staging; urgency=medium
+
+  * Change XML_NO_ERROR to XML_SUCCESS (Closes: 835427)
+
+ -- Peter Michael Green   Sat, 27 Aug 2016 16:02:33 
+
+
 gazebo (7.3.0+dfsg-2) unstable; urgency=medium
 
* Patch to fix linking with gcc6 (Closes: #831176)
diff -Nru gazebo-7.3.0+dfsg/debian/patches/0010-xml-no-error.patch 
gazebo-7.3.0+dfsg/debian/patches/0010-xml-no-error.patch
--- gazebo-7.3.0+dfsg/debian/patches/0010-xml-no-error.patch1970-01-01 
00:00:00.0 +
+++ gazebo-7.3.0+dfsg/debian/patches/0010-xml-no-error.patch2016-08-27 
16:02:33.0 +
@@ -0,0 +1,24 @@
+Description:  Change XML_NO_ERROR to XML_SUCCESS (Closes: 835427)
+Author: Peter Michael Green 
+Bug-Debian: https://bugs.debian.org/835427
+
+--- gazebo-7.3.0+dfsg.orig/gazebo/util/LogPlay.cc
 gazebo-7.3.0+dfsg/gazebo/util/LogPlay.cc
+@@ -72,7 +72,7 @@ void LogPlay::Open(const std::string &_l
+ 
+   // Flag use to indicate if a parser failure has occurred
+   bool xmlParserFail = this->dataPtr->xmlDoc.LoadFile(_logFile.c_str()) !=
+-tinyxml2::XML_NO_ERROR;
++tinyxml2::XML_SUCCESS;
+ 
+   // Parse the log file
+   if (xmlParserFail)
+@@ -105,7 +105,7 @@ void LogPlay::Open(const std::string &_l
+ 
+   // Retry loading the log file.
+   xmlParserFail = this->dataPtr->xmlDoc.LoadFile(_logFile.c_str()) !=
+-tinyxml2::XML_NO_ERROR;
++tinyxml2::XML_SUCCESS;
+ }
+   }
+ }
diff -Nru gazebo-7.3.0+dfsg/debian/patches/series 
gazebo-7.3.0+dfsg/debian/patches/series
--- gazebo-7.3.0+dfsg/debian/patches/series 2016-07-21 15:35:01.0 
+
+++ gazebo-7.3.0+dfsg/debian/patches/series 2016-08-27 16:02:33.0 
+
@@ -2,3 +2,4 @@
 0005-fix-problems-on-manpage.patch
 0008-arial-font-removed-in-dfsg.patch
 0009-fix-gcc6-linking.patch
+0010-xml-no-error.patch

Processed: notfound 834911 in 2.082

[Debian Bug Tracking System]

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

> notfound 834911 2.082
Bug #834911 {Done: gregor herrmann } 
[src:libconfig-model-dpkg-perl] libconfig-model-dpkg-perl: FTBFS too much often 
(Failed 2/12 test programs)
No longer marked as found in versions libconfig-model-dpkg-perl/2.082.
> thanks
Stopping processing here.

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

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

[Alberto Garcia]

On Fri, Aug 12, 2016 at 02:06:53PM +, Gianfranco Costamagna wrote:

> 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.
  [...]
> /usr/bin/ld.gold: error: Can't find matching LO16 reloc
> /usr/bin/ld.gold: error: Can't find matching LO16 reloc

webkit2gtk is also affected by this. Switching to ld.bfd seems to
solve the problem.

Berto

Bug#835966: RM: polyorb -- RoQA; unmaintained, RC-buggy

[Mattia Rizzolo]

source: polyorb
version: 2.11~20140418-3
severity: serious

Dear maintainer,

polyorb is the last package using gnat-4.9 for building, which means
it's the last package holding gnat-4.9 clean removal.

I don't see any activity going on this package, and it already has 2
unaswered RC bugs (#790664 from half 2015).

I wonder if these are signs that calls the removal of the packge.

If I don't receive any reply from you in 2 weeks I'll reassign this bug
to ftpmaster to proceed with the removal.

-- 
regards,
Mattia Rizzolo

GPG Key: 66AE 2B4A FCCF 3F52 DA18  4D18 4B04 3FCD B944 4540  .''`.
more about me:  https://mapreri.org : :'  :
Launchpad user: https://launchpad.net/~mapreri  `. `'`
Debian QA page: https://qa.debian.org/developer.php?login=mattia  `-


signature.asc
Description: PGP signature

Processed: Re: Bug#835255: gdc-6: std.datetime: undefined reference to dlopen/dlsym/dlclose

[Debian Bug Tracking System]

Processing control commands:

> severity -1 serious
Bug #835255 [gdc-6] gdc-6: std.datetime: undefined reference to 
dlopen/dlsym/dlclose
Severity set to 'serious' from 'normal'

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

Bug#835930: flann: breaks reverse-dependencies

[Leopold Palomo-Avellaneda]

El Dilluns, 29 d'agost de 2016, a les 12:34:15, Gianfranco Costamagna va 
escriure:
> Source: flann
> Severity: serious
> Version: 1.9.1+dfsg-2
> 
> Justification: breaks reverse dependencies.
> 
> Hi, the latest flann broke kido build, now it fails with a missing LZ4 link.

there's no missing link IMHO. The problem is that the new flann version has 
incorporated lz4 code, so you must link against libflann_cpp, that has the lz4 
missing functions.

But I should investigate more ...


-- 
--
Linux User 152692 GPG: 05F4A7A949A2D9AA
Catalonia
-
A: Because it messes up the order in which people normally read text.
Q: Why is top-posting such a bad thing?
A: Top-posting.
Q: What is the most annoying thing in e-mail?

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

Bug#835373: blitz++: FTBFS due to testsuite failures on several architectures

[Jerome BENOIT]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Hello blitz++ enthusiasts,

to begin with, this issue are not new issues but old ones:
what is new is that tests has been improve, in particular their
results is now taking into account during the package building.

Otherwise, I am working on it.

Thanks,
Jerome

- -- 
Jerome BENOIT | calculus+at-rezozer^dot*net
https://qa.debian.org/developer.php?login=calcu...@rezozer.net
AE28 AE15 710D FF1D 87E5  A762 3F92 19A6 7F36 C68B
-BEGIN PGP SIGNATURE-

iQQcBAEBCgAGBQJXxD3JAAoJED+SGaZ/NsaLQMIf/1F6N92ovW6yNyn9RWffV23K
7YlKTEsyBfNI4PB8NKXnzOdsVJwxKwFgg95D+SXw4ZKg/Kw0JVr7RSd/UZSdLNyi
mPgsdV9TkbhZW1GpdQrPlZ89iaKkmoSgxf7p37v2LlUG5+2eOA5c5pZIL8jfJaay
lxHcFxIpaPExj0PprKlVVb14YkZceGRZzJv40S7nspUec/8t5tvsYh2hzxDOXb1K
eSXzH4wUxQZNAwPMCXzrM00K4XBcny8X+CrAAcDAwWO+sr/2jPgrZp4V7bkWyc7N
XZ7IvtWXMUibP27SPxQXyTHH8H+l43cI9YvQlG7KSD6UjSBnEqRFJV4apen3psDD
IbTVxbwtdSKEwakzI4BMo2nuW8zfpoJBFujapU1VitOPTvFzxEJgOTW8rLdqSiah
rzLTPJR9ErqsuVnlC9c3sJ1qYuszfZ1M55SiKUSmYOoiDHKOiaEwleI041CwJ+oK
fAHAC96nxqBtuHEQ1lRGMlmtgHUGGKhnjVJoh0LT8QjocP2EpfRTG2LYKKX8y685
iWcjqNTXcpv57nIr/RuYqBplIjmxWKAsLO3U4jZyeVuGhUakNGMnrfO+7pZSvecj
sxaOpqqNmn/sl8KSRdp0YHqdhgwojh2uZKSouyjFGchWFLFa1Mur45B45jTSEroj
AMQv0q7fYWll9FpXfJTf2P2uXqhf5bV9jUWx+FQGivFWmpUtQ1AaIen12qm1PMVI
6JDFQ9UwoWADL/PTA3vntM+ePZfWtM5X2KrMByOU0Xq8hWWc1Ny0Bu4LCWkddNC5
uxuTSGC39Yk9Ystb672PNQ9/dyB/42CHI/wgcxW1uU6ZvXBQxPnCC0kJ4wruyr0G
TirMIMxIZkpzJOmcJ9NtnLbF9beQtLuSoBAyMI7xvoZMTli9Dq+q+czUrSSO2nO3
tQxakeC5C6AwQfXa8TMTe2OU5mWc/RPOsDNsmkOuwYGMmoq6xRoEWLN7D4noBrcV
+sf7kjjQAXLkVtNqS8l+NaWcLTRgThsNVfDtrkoFnmA37IjdJVwyTMf839lnEuOS
u4xoQNv/S99Rts5SXd+5m/+KLHgokBxBYzB7fM/oKdxZjkOceg4bGRZZU5fywKhT
LJ0Q2mh4+5/4ngMGrb0UuMrNcyeFmRSfPol9jpdKbxz8mFbPT7RO0+qOyD3xlG2O
nKSUl4gAdPCx/mreLFKGVTsN7t4zZ6yo61W2K0AS2sIcfuO/EjeHVvD/3qWvHUBx
ardOh5lkKcP3OLDr4aJf9KKoBcX4l5+IImk/14qUUCJwU5nGFHeRX5qs2QguiGBH
w65wSM6DVubWS+Skry9uZozy7uasjB5hPOimAhZLXSqlt7cBKBsQL6qJtTABjMc=
=oqBd
-END PGP SIGNATURE-

Processed: PEBKAC error, not anything else

[Debian Bug Tracking System]

Processing control commands:

> severity -1 minor
Bug #835917 [kdeconnect] kdeconnect: The following packages will be REMOVED?
Severity set to 'minor' from 'grave'

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

Bug#835917: PEBKAC error, not anything else

[Diederik de Haas]

Control: severity -1 minor

>  The following packages will be REMOVED:
>kdeconnect plasma-workspace

kdeconnect depends on plasma-workspace, thus removing the latter will also 
remove the former.
So this isn't a bug. Besides, do you really want to remove plasma-workspace? 
That would ruin your KDE desktop.

topic on #debian-kde says it all:
"Plasma 5.7.4 is not currently installable in sid, please use plasma from 
testing"

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

Processed: Increase severity of perl-cwd-inc-removal bugs prior to upload

[Debian Bug Tracking System]

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

> severity 834412 serious
Bug #834412 [src:barnowl] barnowl: FTBFS with '.' removed from perl's @INC
Severity set to 'serious' from 'important'
> severity 834550 serious
Bug #834550 [src:interchange] interchange: FTBFS with '.' removed from perl's 
@INC
Severity set to 'serious' from 'important'
> severity 834731 serious
Bug #834731 [src:kdesrc-build] kdesrc-build: FTBFS with '.' removed from perl's 
@INC
Severity set to 'serious' from 'important'
> severity 834738 serious
Bug #834738 [src:libcatmandu-mab2-perl] libcatmandu-mab2-perl: FTBFS with '.' 
removed from perl's @INC
Severity set to 'serious' from 'important'
> severity 835181 serious
Bug #835181 [src:libintl-perl] libintl-perl: FTBFS with '.' removed from perl's 
@INC
Severity set to 'serious' from 'important'
> severity 835192 serious
Bug #835192 [src:makepp] makepp: FTBFS with '.' removed from perl's @INC
Severity set to 'serious' from 'important'
> severity 835206 serious
Bug #835206 [src:munin] munin: FTBFS with '.' removed from perl's @INC
Severity set to 'serious' from 'important'
> severity 835432 serious
Bug #835432 [src:polymake] polymake: FTBFS with '.' removed from perl's @INC
Severity set to 'serious' from 'important'
> severity 835491 serious
Bug #835491 [src:slack] slack: FTBFS with '.' removed from perl's @INC
Severity set to 'serious' from 'important'
> severity 835494 serious
Bug #835494 [src:spamassassin] spamassassin: FTBFS with '.' removed from perl's 
@INC
Severity set to 'serious' from 'important'
> severity 835497 serious
Bug #835497 [src:xemacs21-packages] xemacs21-packages: FTBFS with '.' removed 
from perl's @INC
Severity set to 'serious' from 'important'
> severity 834420 serious
Bug #834420 [src:latex2html] latex2html: Relies on '.' being in perl's @INC
Severity set to 'serious' from 'important'
> severity 834423 serious
Bug #834423 [src:latex2html] latex2html: FTBFS with '.' removed from perl's @INC
Severity set to 'serious' from 'important'
> severity 835353 serious
Bug #835353 [src:pari] pari: FTBFS with '.' removed from perl's @INC
Severity set to 'serious' from 'important'
> severity 834520 important
Bug #834520 [src:duck] duck: perl -c test could use wrong version of DUCK.pm
Severity set to 'important' from 'normal'
>
End of message, stopping processing here.

Please contact me if you need assistance.
-- 
834412: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=834412
834420: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=834420
834423: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=834423
834520: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=834520
834550: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=834550
834731: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=834731
834738: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=834738
835181: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=835181
835192: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=835192
835206: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=835206
835353: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=835353
835432: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=835432
835491: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=835491
835494: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=835494
835497: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=835497
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Processed: Re: Bug#832713: systemd: after "systemd (231-1) unstable" update systemd-jurnald.service fails to start

[Debian Bug Tracking System]

Processing control commands:

> tags -1 moreinfo
Bug #832713 {Done: Martin Pitt } [systemd] systemd: after 
"systemd (231-1) unstable" update systemd-jurnald.service fails to start
Bug #832893 {Done: Martin Pitt } [systemd] Failed at step 
SECCOMP spawning systemd-networkd
Added tag(s) moreinfo.
Added tag(s) moreinfo.
> found -1 231-5
Bug #832713 {Done: Martin Pitt } [systemd] systemd: after 
"systemd (231-1) unstable" update systemd-jurnald.service fails to start
Bug #832893 {Done: Martin Pitt } [systemd] Failed at step 
SECCOMP spawning systemd-networkd
Marked as found in versions systemd/231-5 and reopened.
Marked as found in versions systemd/231-5 and reopened.

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

Bug#832713: systemd: after "systemd (231-1) unstable" update systemd-jurnald.service fails to start

[Felipe Sateler]

Control: tags -1 moreinfo
Control: found -1 231-5

On 28 August 2016 at 17:46, Pete Batard  wrote:
> On 2016.08.28 15:37, Felipe Sateler wrote:
>>
>> Could you try 231-5 from unstable?
>
>
> Oops, I mean 231-5 broke it. I'm seeing the issue back in 231-5 and not
> 231-4 as I mentioned earlier.
>
> 231-4 seemed to be okay, and it's only when I upgraded to 231-5 that the
> problem reappeared.

Hmm. Strange. I cannot reproduce on a vm with seccomp disabled. Could
you please attach a verbose log?

-- 

Saludos,
Felipe Sateler

Bug#835930: flann: breaks reverse-dependencies

[Gianfranco Costamagna]

Source: flann
Severity: serious
Version: 1.9.1+dfsg-2

Justification: breaks reverse dependencies.

Hi, the latest flann broke kido build, now it fails with a missing LZ4 link.

Scanning dependencies of target testNearestNeighbor
make[4]: Leaving directory '/<>/kido-0.1.0+dfsg/build'
/usr/bin/make -f unittests/CMakeFiles/testNearestNeighbor.dir/build.make 
unittests/CMakeFiles/testNearestNeighbor.dir/build
make[4]: Entering directory '/<>/kido-0.1.0+dfsg/build'
[ 71%] Building CXX object 
unittests/CMakeFiles/testNearestNeighbor.dir/testNearestNeighbor.cpp.o
cd /<>/kido-0.1.0+dfsg/build/unittests && /usr/bin/c++   
-DBOOST_TEST_DYN_LINK -DHAVE_BULLET_COLLISION -I/<>/kido-0.1.0+dfsg 
-isystem /usr/include/eigen3 -isystem /usr/include/bullet 
-I/<>/kido-0.1.0+dfsg/build 
-I/<>/kido-0.1.0+dfsg/unittests/gtest/include 
-I/<>/kido-0.1.0+dfsg/unittests/gtest  -Wall -fPIC -std=c++11 -g -O2 
-fdebug-prefix-map=/<>/kido-0.1.0+dfsg=. -fPIE 
-fstack-protector-strong -Wformat -Werror=format-security -Wdate-time 
-D_FORTIFY_SOURCE=2   -I/usr/include/bullet -o 
CMakeFiles/testNearestNeighbor.dir/testNearestNeighbor.cpp.o -c 
/<>/kido-0.1.0+dfsg/unittests/testNearestNeighbor.cpp
[ 71%] Linking CXX executable ../bin/tests/testNearestNeighbor
cd /<>/kido-0.1.0+dfsg/build/unittests && /usr/bin/cmake -E 
cmake_link_script CMakeFiles/testNearestNeighbor.dir/link.txt --verbose=1
/usr/bin/c++   -Wall -fPIC -std=c++11 -g -O2 
-fdebug-prefix-map=/<>/kido-0.1.0+dfsg=. -fPIE 
-fstack-protector-strong -Wformat -Werror=format-security -Wdate-time 
-D_FORTIFY_SOURCE=2   -fPIE -pie -Wl,-z,relro -Wl,-z,now -Wl,--as-needed 
CMakeFiles/testNearestNeighbor.dir/testNearestNeighbor.cpp.o  -o 
../bin/tests/testNearestNeighbor  -L/<>/kido-0.1.0+dfsg/build/lib 
-rdynamic ../lib/libkido-utils.so.0.1.0 ../lib/libgtest.a 
../lib/libkido.so.0.1.0 -lccd -lfcl -lassimp -lboost_regex -lboost_system -lGLU 
-lGL -lBulletSoftBody -lBulletDynamics -lBulletCollision -lLinearMath 
-lurdfdom_sensor -lurdfdom_model_state -lurdfdom_model -lurdfdom_world 
-lconsole_bridge -ltinyxml -ltinyxml2 -lpthread 
-Wl,-rpath,/<>/kido-0.1.0+dfsg/build/lib 
CMakeFiles/testNearestNeighbor.dir/testNearestNeighbor.cpp.o: In function 
`flann::serialization::SaveArchive::initBlock()':
/usr/include/flann/util/serialization.h:406: undefined reference to 
`LZ4_resetStreamHC'
CMakeFiles/testNearestNeighbor.dir/testNearestNeighbor.cpp.o: In function 
`flann::serialization::SaveArchive::flushBlock()':
/usr/include/flann/util/serialization.h:425: undefined reference to 
`LZ4_compress_HC_continue'
/usr/include/flann/util/serialization.h:443: undefined reference to 
`LZ4_compress_HC_continue'
CMakeFiles/testNearestNeighbor.dir/testNearestNeighbor.cpp.o: In function 
`flann::serialization::LoadArchive::decompressAndLoadV10(_IO_FILE*)':
/usr/include/flann/util/serialization.h:610: undefined reference to 
`LZ4_decompress_safe'
CMakeFiles/testNearestNeighbor.dir/testNearestNeighbor.cpp.o: In function 
`flann::serialization::LoadArchive::loadBlock(char*, unsigned int, _IO_FILE*)':
/usr/include/flann/util/serialization.h:690: undefined reference to 
`LZ4_decompress_safe_continue'
CMakeFiles/testNearestNeighbor.dir/testNearestNeighbor.cpp.o: In function 
`flann::serialization::LoadArchive::initBlock(_IO_FILE*)':
/usr/include/flann/util/serialization.h:667: undefined reference to 
`LZ4_setStreamDecode'
collect2: error: ld returned 1 exit status
unittests/CMakeFiles/testNearestNeighbor.dir/build.make:114: recipe for target 
'bin/tests/testNearestNeighbor' failed
make[4]: *** [bin/tests/testNearestNeighbor] Error 1
make[4]: Leaving directory '/<>/kido-0.1.0+dfsg/build'
CMakeFiles/Makefile2:1981: recipe for target 
'unittests/CMakeFiles/testNearestNeighbor.dir/all' failed
make[3]: *** [unittests/CMakeFiles/testNearestNeighbor.dir/all] Error 2
make[3]: Leaving directory '/<>/kido-0.1.0+dfsg/build'
Makefile:141: recipe for target 'all' failed
make[2]: *** [all] Error 2
make[2]: Leaving directory '/<>/kido-0.1.0+dfsg/build'
debian/rules:33: recipe for target 'override_dh_auto_build' failed
make[1]: *** [override_dh_auto_build] Error 2
make[1]: Leaving directory '/<>/kido-0.1.0+dfsg'
debian/rules:22: recipe for target 'build' failed
make: *** [build] Error 2
dpkg-buildpackage: error: debian/rules build gave error exit status 2

Gianfranco

Processed: Re: Bug#833817: kido: FTBFS on non-x86 architectures due to hard-wired compiler flags

[Debian Bug Tracking System]

Processing control commands:

> tags -1 patch
Bug #835734 [src:kido] kido: FTBFS: FCLCollisionNode.cpp:354:5: error: 'boost' 
has not been declared
Added tag(s) patch.

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

Processed: Re: Bug#833817: kido: FTBFS on non-x86 architectures due to hard-wired compiler flags

[Debian Bug Tracking System]

Processing control commands:

> tags -1 patch
Bug #833817 [src:kido] kido: FTBFS on non-x86 architectures due to hard-wired 
compiler flags
Added tag(s) patch.

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

Bug#833817: kido: FTBFS on non-x86 architectures due to hard-wired compiler flags

[Gianfranco Costamagna]

control: tags -1 patch

attached a patch, unfortunately I can't upload because it seems the latest 
flann.
(I'm opening a bug)

G.
diff -Nru kido-0.1.0+dfsg/debian/changelog kido-0.1.0+dfsg/debian/changelog
--- kido-0.1.0+dfsg/debian/changelog2016-07-21 16:33:19.0 +0200
+++ kido-0.1.0+dfsg/debian/changelog2016-08-29 13:25:42.0 +0200
@@ -1,3 +1,16 @@
+kido (0.1.0+dfsg-1.1) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * debian/patches/fix-msse2-flag: 
+- remove msse3 hard-coded flag (Closes: #833817)
+  * debian/patches/update-new-fcl.patch:
+- fix boost issue with new fcl.
+  * debian/patches/2841967fc6628c9aea58c93227b28abdf5dfbcc2.patch:
+- cherry-pick part of upstream fix for new fcl and tinyxml2.
+  (Closes: #835734)
+
+ -- Gianfranco Costamagna   Mon, 29 Aug 2016 
12:22:34 +0200
+
 kido (0.1.0+dfsg-1) unstable; urgency=medium
 
   * Initial release. (Closes: #812126)
diff -Nru 
kido-0.1.0+dfsg/debian/patches/2841967fc6628c9aea58c93227b28abdf5dfbcc2.patch 
kido-0.1.0+dfsg/debian/patches/2841967fc6628c9aea58c93227b28abdf5dfbcc2.patch
--- 
kido-0.1.0+dfsg/debian/patches/2841967fc6628c9aea58c93227b28abdf5dfbcc2.patch   
1970-01-01 01:00:00.0 +0100
+++ 
kido-0.1.0+dfsg/debian/patches/2841967fc6628c9aea58c93227b28abdf5dfbcc2.patch   
2016-08-29 12:50:17.0 +0200
@@ -0,0 +1,66 @@
+From 2841967fc6628c9aea58c93227b28abdf5dfbcc2 Mon Sep 17 00:00:00 2001
+From: Jeongseok Lee 
+Date: Thu, 21 Jul 2016 17:34:40 -0400
+Subject: [PATCH] Update API to support fcl 0.5 and tinyxml 4.0 -- for DART 6.1
+ (#750)
+
+* Update API to support fcl 0.5.0
+
+* Update changelog
+
+* Use type aliasing rather than boilerplate preprocessors
+
+* Switch to use XML_SUCCESS rather than XML_NO_ERROR
+---
+ kido/utils/XmlHelpers.cpp   | 10 +-
+ 7 files changed, 24 insertions(+), 17 deletions(-)
+
+Index: kido-0.1.0+dfsg/kido/utils/XmlHelpers.cpp
+===
+--- kido-0.1.0+dfsg.orig/kido/utils/XmlHelpers.cpp
 kido-0.1.0+dfsg/kido/utils/XmlHelpers.cpp
+@@ -731,7 +731,7 @@
+   const int result = element->QueryBoolAttribute(attributeName.c_str(),
+  &val);
+ 
+-  if (result != tinyxml2::XML_NO_ERROR)
++  if (result != tinyxml2::XML_SUCCESS)
+   {
+ dtwarn << "[getAttribute] Error in parsing bool type attribute ["
+<< attributeName << "] of an element [" << element->Name()
+@@ -749,7 +749,7 @@
+   int val = 0;
+   const int result = element->QueryIntAttribute(attributeName.c_str(), &val);
+ 
+-  if (result != tinyxml2::XML_NO_ERROR)
++  if (result != tinyxml2::XML_SUCCESS)
+   {
+ dtwarn << "[getAttribute] Error in parsing int type attribute ["
+<< attributeName << "] of an element [" << element->Name()
+@@ -768,7 +768,7 @@
+   const int result = element->QueryUnsignedAttribute(attributeName.c_str(),
+  &val);
+ 
+-  if (result != tinyxml2::XML_NO_ERROR)
++  if (result != tinyxml2::XML_SUCCESS)
+   {
+ dtwarn << "[getAttribute] Error in parsing unsiged int type attribute ["
+<< attributeName << "] of an element [" << element->Name()
+@@ -787,7 +787,7 @@
+   const int result = element->QueryFloatAttribute(attributeName.c_str(),
+   &val);
+ 
+-  if (result != tinyxml2::XML_NO_ERROR)
++  if (result != tinyxml2::XML_SUCCESS)
+   {
+ dtwarn << "[getAttribute] Error in parsing float type attribute ["
+<< attributeName << "] of an element [" << element->Name()
+@@ -806,7 +806,7 @@
+   const int result = element->QueryDoubleAttribute(attributeName.c_str(),
+&val);
+ 
+-  if (result != tinyxml2::XML_NO_ERROR)
++  if (result != tinyxml2::XML_SUCCESS)
+   {
+ dtwarn << "[getAttribute] Error in parsing double type attribute ["
+<< attributeName << "] of an element [" << element->Name()
diff -Nru kido-0.1.0+dfsg/debian/patches/fix-msse2-flag.patch 
kido-0.1.0+dfsg/debian/patches/fix-msse2-flag.patch
--- kido-0.1.0+dfsg/debian/patches/fix-msse2-flag.patch 1970-01-01 
01:00:00.0 +0100
+++ kido-0.1.0+dfsg/debian/patches/fix-msse2-flag.patch 2016-08-29 
13:25:17.0 +0200
@@ -0,0 +1,37 @@
+Description: Remove msse2 flag
+Author: Gianfranco Costamagna 
+Bug-Debian: https://bugs.debian.org/833817
+
+---
+The information above should follow the Patch Tagging Guidelines, please
+checkout http://dep.debian.net/deps/dep3/ to learn about the format. Here
+are templates for supplementary fields that you might want to add:
+
+Origin: , 
+Bug: 
+Bug-Debian: https://bugs.debian.org/
+Bug-Ubuntu: https://launchpad.net/bugs/
+Forwarded: 
+Reviewed-By: 
+Last-Update: 
+
+--- kido-0.1.0+dfsg.orig/CMakeLists.txt
 kido-0.1.0+dfsg/CMakeLists.txt
+@@ -492,7 +492,7 @@ if(MSVC)
+ set(CMAKE_CXX_FLAGS_RELEASE "${CMAKE_CXX_FLAGS

Bug#834034: marked as done (bacula-director-{sqlite3, mysql, pgsql}: fails to install: Processing configuration...sed: can't read /usr/share/bacula-common/defconfig/scripts/delete_catalog_backup: No s

[Debian Bug Tracking System]

Your message dated Mon, 29 Aug 2016 11:48:34 +
with message-id 
and subject line Bug#834034: fixed in bacula 7.4.3+dfsg-4
has caused the Debian Bug report #834034,
regarding bacula-director-{sqlite3, mysql, pgsql}: fails to install: Processing 
configuration...sed: can't read 
/usr/share/bacula-common/defconfig/scripts/delete_catalog_backup: No such file 
or directory
to be marked as done.

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

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


-- 
834034: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=834034
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: bacula-director-sqlite3,bacula-director-pgsql,bacula-director-mysql
Version: 7.4.3+dfsg-3
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

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

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

  Selecting previously unselected package bacula-director-sqlite3.
  (Reading database ... 
(Reading database ... 6774 files and directories currently installed.)
  Preparing to unpack .../bacula-director-sqlite3_7.4.3+dfsg-3_amd64.deb ...
  Unpacking bacula-director-sqlite3 (7.4.3+dfsg-3) ...
  Setting up bacula-director-sqlite3 (7.4.3+dfsg-3) ...
  dbconfig-common: writing config to 
/etc/dbconfig-common/bacula-director-sqlite3.conf
  
  Creating config file /etc/dbconfig-common/bacula-director-sqlite3.conf with 
new version
  creating database bacula.db: success.
  verifying database bacula.db exists: success.
  populating database via sql...  done.
  
  Creating config file /etc/default/bacula-dir with new version
  Processing configuration...sed: can't read 
/usr/share/bacula-common/defconfig/scripts/delete_catalog_backup: No such file 
or directory
  dpkg: error processing package bacula-director-sqlite3 (--configure):
   subprocess installed post-installation script returned error exit status 2
  Errors were encountered while processing:
   bacula-director-sqlite3



cheers,

Andreas


bacula-director-sqlite3_7.4.3+dfsg-3.log.gz
Description: application/gzip
--- End Message ---
--- Begin Message ---
Source: bacula
Source-Version: 7.4.3+dfsg-4

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

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Mon, 29 Aug 2016 13:34:08 +0200
Source: bacula
Binary: bacula bacula-common bacula-common-sqlite3 bacula-common-pgsql 
bacula-common-mysql bacula-director bacula-director-sqlite3 
bacula-director-mysql bacula-director-pgsql bacula-client bacula-fd 
bacula-server bacula-sd bacula-bscan bacula-console bacula-console-qt
Architecture: source
Version: 7.4.3+dfsg-4
Distribution: experimental
Urgency: medium
Maintainer: Debian Bacula Team 
Changed-By: Carsten Leonhardt 
Description:
 bacula - network backup service - metapackage
 bacula-bscan - network backup service - bscan tool
 bacula-client - network backup service - client metapackage
 bacula-common - network backup service - common support files
 bacula-common-mysql - network backup service - MySQL common files
 bacula-common-pgsql - network backup service - PostgreSQL common files
 bacula-common-sqlite3 - network backup service - SQLite v3 common files
 bacula-console - network backup service - text console
 bacula-console-qt - network backup service - Bacula Administration Tool
 bacula-director - network backup service - Director daemon
 bacula-director-mysql - network backup service - MySQL storage for Director
 bacula-director-pgsql - network backup service - PostgreSQL storage for 
Director
 bacula-director-sqlite3 - network backup service - SQLite 3 storage for 
Director
 bacula-fd  - network backup service - file daemon
 bacula-sd  - network backup service - storage daemon
 bacula-server - network backup service - server metapackage
Closes: 834034
Changes:
 bacula (7.4.3+dfsg-4) experimental; urg

Processed: forcibly merging 835822 835922

[Debian Bug Tracking System]

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

> forcemerge 835822 835922
Bug #835822 [network-manager] network-manager: wifi network setup fails 
completely
Bug #835822 [network-manager] network-manager: wifi network setup fails 
completely
Marked as found in versions network-manager/1.4.0-3.
Added tag(s) upstream.
Bug #835922 [network-manager] network-manager: NetworkManager 1.4.0-1 breaks 
wifi
Severity set to 'important' from 'grave'
Marked as found in versions network-manager/1.4.0-2.
Merged 835822 835922
> thanks
Stopping processing here.

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

Processed: Re: [Debian GNUstep maintainers] Bug#835894: terminal.app: crashes on startup: Did not find correct version of backend

[Debian Bug Tracking System]

Processing control commands:

> retitle -1 missing dependency on gnustep-back
Bug #835894 [terminal.app] terminal.app: crashes on startup: Did not find 
correct version of backend
Changed Bug title to 'missing dependency on gnustep-back' from 'terminal.app: 
crashes on startup: Did not find correct version of backend'.

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

Bug#835894: [Debian GNUstep maintainers] Bug#835894: terminal.app: crashes on startup: Did not find correct version of backend

[Adam Borowski]

Control: retitle -1 missing dependency on gnustep-back

> >I'm afraid terminal.app crashes at startup in unstable

> Well, it seems that teminal.app doesn't depends on gnustep-back package.
> 
> Instead it depends on libgnustep-gui0.25 which doesn't depends on
> gnustep-back.

Indeed, installing gnustep-back0.25 makes it work.

There are no rdepends on gnustep-back0.25 (nor any of its backends) in
Debian at all, so there might be more packages in the gnustep world that
would likewise fail to work.


Thanks for the prompt investigation!

-- 
An imaginary friend squared is a real enemy.

Processed: fixed 835341 in 1.7.0-1

[Debian Bug Tracking System]

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

> fixed 835341 1.7.0-1
Bug #835341 {Done: Antonio Radici } [mutt] mutt 1.6.2-3 has 
wrong dependencies
Bug #835477 {Done: Antonio Radici } [mutt] depends on 
libnotmuch3, not available in unstable
Marked as fixed in versions mutt/1.7.0-1.
Marked as fixed in versions mutt/1.7.0-1.
> thanks
Stopping processing here.

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

Bug#835360: rkt: FTBFS on several architectures

[Luca BRUNO]

1.13.0+dfsg-1 has been built without issues on i386:
https://buildd.debian.org/status/fetch.php?pkg=rkt&arch=i386&ver=1.13.0%2Bdfsg-1&stamp=1472188080

ppc64 and s390x are in progress upstream and should hopefully
be back in the next releases.

Ciao, Luca

-- 
«Доверяй, но проверяй»


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

Bug#772576: taskcoach bug 772576

[Nicolas Boulenguez]

Hello.

Please consider checking whether you can reproduce the problem
- with the .deb package distributed by upstream
- in a clean Debian install, if you can start a live system or a chroot.
I can see no better way to start investigating this issue.

However...
Popcon reports 144 users of the .deb distributed by Debian. There are
probably more of them either not running popcon or installing the
almost identical .deb from Ubuntu.  No one else has reported the same
issue for 18 months. Some really run it daily, since unrelated issues
have been reported meanwhile. So I intend to reduce the severity to
important and allow the package to migrate to testing.

 important: a bug which has a major effect on the usability of a
   package, without rendering it completely unusable to everyone.

Bug#835341: marked as done (mutt 1.6.2-3 has wrong dependencies)

[Debian Bug Tracking System]

Your message dated Mon, 29 Aug 2016 10:47:43 +
with message-id <20160829104743.3rgcf3fqmn5xr...@cherubino.dyne.org>
and subject line Re: [Pkg-mutt-maintainers] Bug#835341: mutt 1.6.2-3 has wrong 
dependencies
has caused the Debian Bug report #835341,
regarding mutt 1.6.2-3 has wrong dependencies
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.)


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

Dear Maintainer,

the latest version of mutt has somehow got wrong dependencies (from an
older version I guess) and so is not installable in unstable or testing.

# apt-get install mutt
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:
 mutt : Depends: libgnutls-deb0-28 (>= 3.3.0) but it is not installable
Depends: libnotmuch3 (>= 0.13~rc1) but it is not installable
E: Unable to correct problems, you have held broken packages.

Version 1.6.2-2 depends on

libgnutls30 (>=3.5.0)
libnotmuch4 (>=0.21~rc1)

These should be correct.

Regards
Viktor
--- End Message ---
--- Begin Message ---
fixed 1.7.0-1
thanks

The new version of the mutt package (1.7.0-1) superseeds 1.6.2-3, therefore I'm
closing this bug marking it as fixed in the new version.

I'll keep the binNMU request open, in the meantime we would like mutt to
transition to testing though.--- End Message ---

Bug#835477: marked as done (depends on libnotmuch3, not available in unstable)

[Debian Bug Tracking System]

Your message dated Mon, 29 Aug 2016 10:47:43 +
with message-id <20160829104743.3rgcf3fqmn5xr...@cherubino.dyne.org>
and subject line Re: [Pkg-mutt-maintainers] Bug#835341: mutt 1.6.2-3 has wrong 
dependencies
has caused the Debian Bug report #835341,
regarding depends on libnotmuch3, not available in unstable
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.)


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

Hi,

My system wants to update mutt to 1.6.2-3, but that depends on
libnotmuch3, whereas in unstable, that should now be libnotmuch4
instead.

As such, it tries to install libnotmuch3 from jessie, which wants to
pull in libxapian22 (conflicting with libxapian22v5), resulting in
things not going so well.

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

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

Versions of packages mutt is related to:
ii  mutt  1.6.2-2
--- End Message ---
--- Begin Message ---
fixed 1.7.0-1
thanks

The new version of the mutt package (1.7.0-1) superseeds 1.6.2-3, therefore I'm
closing this bug marking it as fixed in the new version.

I'll keep the binNMU request open, in the meantime we would like mutt to
transition to testing though.--- End Message ---

Bug#830672: [pkg-go] Bug#830672: golang-github-azure-go-autorest: accesses the internet during build

[Chris Lamb]

Martín Ferrari wrote:

> unshare -n bash

I'm using a Docker container.

> > Just tcpdump in a container. I can still reproduce this. Are you running
> > the tests? :)
> 
> Yeah!

I bit of manual bisecting later, this is the test:

 
http://sources.debian.net/src/golang-github-azure-go-autorest/7.0.4-2/autorest/azure/token_test.go/#L375

Hope that helps.


Regards,

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

Bug#834743: marked as done (sixer: FTBFS (clean target does not work))

[Debian Bug Tracking System]

Your message dated Mon, 29 Aug 2016 10:26:17 +
with message-id 
and subject line Bug#834743: fixed in sixer 1.6-2
has caused the Debian Bug report #834743,
regarding sixer: FTBFS (clean target does not work)
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.)


-- 
834743: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=834743
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:sixer
Version: 1.6-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:


[...]
dpkg-buildpackage: info: source package sixer
dpkg-buildpackage: info: source version 1.6-1
dpkg-buildpackage: info: source distribution unstable
dpkg-buildpackage: info: source changed by Thomas Goirand 
 dpkg-source --before-build sixer-1.6
dpkg-source: info: using options from sixer-1.6/debian/source/options: 
--extend-diff-ignore=^[^/]*[.]egg-info/
 fakeroot debian/rules clean
make: pyversions: Command not found
py3versions: no X-Python3-Version in control file, using supported versions
dh clean --buildsystem=python_distutils --with python3
   dh_testdir -O--buildsystem=python_distutils
   dh_auto_clean -O--buildsystem=python_distutils
dh_auto_clean: failed to run pyversions
debian/rules:7: recipe for target 'clean' failed
make: *** [clean] Error 2
dpkg-buildpackage: error: fakeroot debian/rules clean gave error exit status 2


Once you make this to build again, please consider uploading it in
source-only form, so that we have pretty official build logs available
here:

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

Thanks.
--- End Message ---
--- Begin Message ---
Source: sixer
Source-Version: 1.6-2

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

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Mon, 29 Aug 2016 08:47:13 +
Source: sixer
Binary: sixer
Architecture: source all
Version: 1.6-2
Distribution: unstable
Urgency: medium
Maintainer: PKG OpenStack 
Changed-By: Thomas Goirand 
Description:
 sixer  - add Python 3 support to Python 2 applications using six - Python
Closes: 834743
Changes:
 sixer (1.6-2) unstable; urgency=medium
 .
   * Added python-all as build-depends (Closes: #834743).
Checksums-Sha1:
 a6bcb9e53382b26ef7b1b8474d7d0192bc44f41a 1964 sixer_1.6-2.dsc
 401bce959a6f0b0e245d9de7e66c90d31ac76065 2324 sixer_1.6-2.debian.tar.xz
 6d2c34931695497775b2910e147c3dd8f9325bf3 16764 sixer_1.6-2_all.deb
Checksums-Sha256:
 73548a5a163c941ae7583b405370237d646a200bdd19715782fb0d787f3a7bda 1964 
sixer_1.6-2.dsc
 e3d44c1ba5bdc47101f4f63f7fb3ce2fa7b4f575adf793af3cc557bb2c41cb08 2324 
sixer_1.6-2.debian.tar.xz
 fd935c3f128a6959c574a336438ce8c2088a6872becfa2be299559b98c641493 16764 
sixer_1.6-2_all.deb
Files:
 4bd48f191dd4d353ba5f0ceec57d94f8 1964 python optional sixer_1.6-2.dsc
 9c8fdf997b583ee592521bcb209e988c 2324 python optional sixer_1.6-2.debian.tar.xz
 3a4f73f758df64f1f7509b6f39badab5 16764 python optional sixer_1.6-2_all.deb

-BEGIN PGP SIGNATURE-

iQItBAEBCAAXBQJXw/cLEBx6aWdvQGRlYmlhbi5vcmcACgkQ1BatFaxrQ/4GmQ//
d9c4/W7WTlDomPmXImFmKQDavMYt1fhoLLy0lmuDtnUEazAe4hBWzT4Gchd3ijp+
/ktytGbaXkRgn4qPkDpbnDn/tBaHR+eHMwBP53ZOFmY5r/wpsBVMdwZjkUmChG72
E9tTKb+YNdroJkTBy183a6aK7ixyJGT4CTuIG2WO0idZHZU6uffBl31O4IQ9titB
38gylnCJQkSkFA1+cH26+cm50Xm+7TjdcPIX07amXB8wFKxlk3MEbtV4ydpgDKAo
hjPCWxX7qbFxgmxWMBEIAe62suXNb0qOSRuJlg1MHg27pEkiSnJcvsOWG/+ukMe5
spOtzKBEZBTzTk5IHD+7QFbyRBru01Bsigo57aK3ow1N/f+6PcWE3DJcILg8Yo8I
lzP5MQC3fGtS7cWJQ6wtS4mP+NWH4zm7O6g0MkInmAPJi2wyxFyKEjieU2+Hf8k0
TwM2xAEwd8/kYrNAab9qMYbhZhS91Brj5CiXNFjIXbG07/LLNvuz1ojQ3z0gdGGz
PVgXfuip7Q50ZIS55Kl9hjKEfh3vwMHQfsgZVf3CqjgFpv9Xsu4xlONxkTZ2p1vF
RlBWurahGOv+QSgrpVAkVjs4U3pGev57rsHcwdw0Au81gCSiUIm9f2fOmZNPSq/O
+pQpDb

Bug#835224: marked as done (pymol: FTBFS in every autobuilder (No such file or directory))

[Debian Bug Tracking System]

Your message dated Mon, 29 Aug 2016 10:25:42 +
with message-id 
and subject line Bug#835224: fixed in pymol 1.8.2.1+dfsg-1.1
has caused the Debian Bug report #835224,
regarding pymol: FTBFS in every autobuilder (No such file or directory)
to be marked as done.

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

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


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

Dear maintainer:

I tried to build this package in stretch 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 --parallel
   dh_testdir -i -O--parallel
   dh_update_autotools_config -i -O--parallel
   debian/rules override_dh_auto_configure
make[1]: Entering directory '/<>/pymol-1.8.2.1+dfsg'
dh_auto_configure -Spython_distutils
make[1]: Leaving directory '/<>/pymol-1.8.2.1+dfsg'
   debian/rules override_dh_auto_build
make[1]: Entering directory '/<>/pymol-1.8.2.1+dfsg'
dh_auto_build -Spython_distutils
python setup.py build --force

[... snipped ...]

copying build/lib.linux-x86_64-2.7/chempy/champ/amber99.py -> 
/<>/pymol-1.8.2.1+dfsg/debian/tmp/usr/lib/python2.7/dist-packages/chempy/champ
creating 
/<>/pymol-1.8.2.1+dfsg/debian/tmp/usr/lib/python2.7/dist-packages/chempy/bmin
copying build/lib.linux-x86_64-2.7/chempy/bmin/util.py -> 
/<>/pymol-1.8.2.1+dfsg/debian/tmp/usr/lib/python2.7/dist-packages/chempy/bmin
copying build/lib.linux-x86_64-2.7/chempy/bmin/state.py -> 
/<>/pymol-1.8.2.1+dfsg/debian/tmp/usr/lib/python2.7/dist-packages/chempy/bmin
copying build/lib.linux-x86_64-2.7/chempy/bmin/realtime.py -> 
/<>/pymol-1.8.2.1+dfsg/debian/tmp/usr/lib/python2.7/dist-packages/chempy/bmin
copying build/lib.linux-x86_64-2.7/chempy/bmin/commands.py -> 
/<>/pymol-1.8.2.1+dfsg/debian/tmp/usr/lib/python2.7/dist-packages/chempy/bmin
copying build/lib.linux-x86_64-2.7/chempy/bmin/__init__.py -> 
/<>/pymol-1.8.2.1+dfsg/debian/tmp/usr/lib/python2.7/dist-packages/chempy/bmin
copying build/lib.linux-x86_64-2.7/chempy/water_residues.py -> 
/<>/pymol-1.8.2.1+dfsg/debian/tmp/usr/lib/python2.7/dist-packages/chempy
creating 
/<>/pymol-1.8.2.1+dfsg/debian/tmp/usr/lib/python2.7/dist-packages/pmg_wx
copying build/lib.linux-x86_64-2.7/pmg_wx/__init__.py -> 
/<>/pymol-1.8.2.1+dfsg/debian/tmp/usr/lib/python2.7/dist-packages/pmg_wx
running install_egg_info
Writing 
/<>/pymol-1.8.2.1+dfsg/debian/tmp/usr/lib/python2.7/dist-packages/pymol-1.8.2.1.egg-info
creating /<>/pymol-1.8.2.1+dfsg/debian/tmp/usr/bin
   debian/rules override_dh_install
make[1]: Entering directory '/<>/pymol-1.8.2.1+dfsg'
pdflatex -output-directory debian -jobname pymol-ref-card debian/pymolRef.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
(./debian/pymolRef.tex
LaTeX2e <2016/03/31> patch level 3
Babel <3.9r> and hyphenation patterns for 3 language(s) loaded.
(/usr/share/texlive/texmf-dist/tex/latex/base/article.cls
Document Class: article 2014/09/29 v1.4h Standard LaTeX document class
(/usr/share/texlive/texmf-dist/tex/latex/base/size10.clo))
(/usr/share/texlive/texmf-dist/tex/latex/tools/multicol.sty)
No file pymol-ref-card.aux.

Underfull \hbox (badness 1) in paragraph at lines 78--79

[1{/var/lib/texmf/fonts/map/pdftex/updmap/pdftex.map}]
(/usr/share/texlive/texmf-dist/tex/latex/base/omscmr.fd) [2]
(debian/pymol-ref-card.aux) )
(see the transcript file for additional information)
Output written on debian/pymol-ref-card.pdf (2 pages, 108274 bytes).
Transcript written on debian/pymol-ref-card.log.
sed -e s/@PYTHON_VERSION@/2.7/g < debian/pymol.launch.in > debian/pymol.launch
dh_numpy
dh_install data/shaders usr/lib/python2.7/dist-packages/pymol/data/
install -m 755 debian/pymol.launch debian/pymol/usr/bin/pymol
install: cannot create regular file 'debian/pymol/usr/bin/pymol': No such file 
or directory
debian/rules:37: recipe for target 'override_dh_install' failed
make[1]: *** [override_dh_install] Error 1
make[1]: Leaving directory '/<>/pymol-1.8.2.1+dfsg'
debian/rules:14: recipe for target 'binary-indep' failed
make: *** [binary-indep] Error 2
dpkg-buildpackage: error: fakeroot debian/rules binary-indep gave error exit 
status 2


To reproduce, please try to build the package with "dpkg-bu