Processed: tagging 835278

[Debian Bug Tracking System]

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

> tags 835278 + fixed-in-experimental
Bug #835278 {Done: Dmitry Bogatov } [runit] [runit] fails to 
upgrade cleanly
Bug #835903 {Done: Dmitry Bogatov } [runit] runit: upgrade 
failed
Added tag(s) fixed-in-experimental.
Added tag(s) fixed-in-experimental.
> thanks
Stopping processing here.

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

Bug#836571: jessie-pu: package rabbitvcs/0.16-1

[Christopher Hoskin]

Package: release.debian.org
Severity: critical
Tags: patch
User: release.debian@packages.debian.org
Usertags: pu

The attached patch fixes bug #817231 in the rabbitvcs package. This is 
classified as a critical bug on the grounds that it can cause serious data loss 
(e.g. loss of entire home folder). There are several reports of this actually 
happening to users of the software on Debian and other systems:

https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=817231
https://github.com/rabbitvcs/rabbitvcs/issues/127
http://askubuntu.com/questions/473433/rabbitsvn-deleted-all-my-folders
https://github.com/rabbitvcs/rabbitvcs/issues/70

Bug #817231 has now been closed in unstable. Given the nature of the bug, I 
thought perhaps it should also be fixed in jessie-updates? The attached patch 
acheives this. (I understand that the distribution needs to be set to jessie in 
debian/changelog, rather than {jessie|stable}-updates[0].)

I am not a Debian Developer so would require a sponsor.

[0] https://lists.debian.org/debian-devel/2015/06/msg00307.html

Thanks.

Christopher Hoskin
diff -Nru rabbitvcs-0.16/debian/changelog rabbitvcs-0.16/debian/changelog
--- rabbitvcs-0.16/debian/changelog	2014-10-05 10:21:39.0 +0100
+++ rabbitvcs-0.16/debian/changelog	2016-09-04 07:09:07.0 +0100
@@ -1,3 +1,10 @@
+rabbitvcs (0.16-1.1) jessie; urgency=medium
+
+  * Non-maintainer upload.
+  * Fix "All files in home folder removed" Applied upstream fix as patch (Closes: #817231)
+
+ -- Christopher Hoskin   Sun, 04 Sep 2016 07:08:46 +0100
+
 rabbitvcs (0.16-1) unstable; urgency=medium
 
   * Team upload.
diff -Nru rabbitvcs-0.16/debian/patches/fix-817231.patch rabbitvcs-0.16/debian/patches/fix-817231.patch
--- rabbitvcs-0.16/debian/patches/fix-817231.patch	1970-01-01 01:00:00.0 +0100
+++ rabbitvcs-0.16/debian/patches/fix-817231.patch	2016-09-04 07:05:41.0 +0100
@@ -0,0 +1,38 @@
+Subject: Repository Browser export empties target folder
+ A critical bug, where when the user attempts to export files from within the
+ RabbitVCS Repository Browser to a local target folder, the contents of the
+ target folder are deleted without warning, and the export fails.
+Origin: upstream, https://github.com/rabbitvcs/rabbitvcs/pull/89/commits/b3dc98601d57d2e58e491a66b562a399ce1a
+Bug-Debian: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=817231
+Bug: https://github.com/rabbitvcs/rabbitvcs/issues/70
+Bug: https://github.com/rabbitvcs/rabbitvcs/issues/127
+Bug: https://github.com/rabbitvcs/rabbitvcs/issues/161
+From: abaheti 
+Acked-by: Christopher Hoskin 
+Last-Update: 2016-08-28
+Applied-Upstream: commit:b3dc986, https://github.com/rabbitvcs/rabbitvcs/pull/89/commits/b3dc98601d57d2e58e491a66b562a399ce1a
+
+---
+ rabbitvcs/vcs/svn/__init__.py | 6 +-
+ 1 file changed, 1 insertion(+), 5 deletions(-)
+
+diff --git a/rabbitvcs/vcs/svn/__init__.py b/rabbitvcs/vcs/svn/__init__.py
+index 96d821d..dee5e7f 100644
+--- a/rabbitvcs/vcs/svn/__init__.py
 b/rabbitvcs/vcs/svn/__init__.py
+@@ -1237,11 +1237,7 @@ class SVN:
+ @param  recurse: Whether or not to run a recursive checkout.
+ 
+ """
+-if os.path.exists(dest_path):
+-if os.path.isdir(dest_path):
+-shutil.rmtree(dest_path)
+-else:
+-os.remove(dest_path)
++revision=Revision("head")
+ 
+ 
+ 
+-- 
+2.9.3
+
diff -Nru rabbitvcs-0.16/debian/patches/series rabbitvcs-0.16/debian/patches/series
--- rabbitvcs-0.16/debian/patches/series	2014-10-05 10:12:07.0 +0100
+++ rabbitvcs-0.16/debian/patches/series	2016-09-04 07:05:41.0 +0100
@@ -1 +1,2 @@
 99_setup.py.patch
+fix-817231.patch

Bug#830568: python-asyncssh: accesses the internet during build

[Vincent Bernat]

 ❦  3 septembre 2016 23:37 CEST, Chris Lamb  :

>> If your bug was wishlist, I would just ignore it. It is severity serious
>> and I have to handle it. Maybe it is legitimate. Maybe not.
>
> Oh! I thought we were discussing whether it was a bug at all — hence the
> time you spent addressing whether privacy leaking is valuable — not the
> severity of the bug itself.
>
> As I probably dislike "bug severity wars" even more than Debian Policy
> wording debates, free to change it to whatever you feel is appropriate… :)
>
> Howevever, it does feel regrettable you readily admit you might completely
> ignore a bug.

This is why I think the issue should be discussed more broadly. I am
pretty sure many people will agree with you, but I am also pretty sure
some will agree with me. I can start the thread on debian-devel@ if you
don't mind.
-- 
Make it clear before you make it faster.
- The Elements of Programming Style (Kernighan & Plauger)


signature.asc
Description: PGP signature

Bug#830568: python-asyncssh: accesses the internet during build

[Vincent Bernat]

 ❦  4 septembre 2016 01:03 CEST, Santiago Vila  :

>> [...] information leak [...]
>
> This is not just a privacy issue but also a reproducibility issue.
>
> It is bad that a package leaks information to the external world,
> but it is even worse, I would say, that information from the outside
> world is being used in any way by the package during the build.
>
> If we allow packages to communicate with the external world during the
> build, then a sentence like "this is the source for this binary package"
> becomes completely meaningless, as the source package stops being all
> you need to build the package.

In this case, there is no reproducibility issue. The worst that can
happen is the unit tests to fail if you have a host called "fail" on
your network. Something that is plausible but should stay quite rare.

I am totally OK with the general rule that a package must build without
having access to the network. This is the case with python-asyncssh. It
builds fine without access to the network.
-- 
Make your program read from top to bottom.
- The Elements of Programming Style (Kernighan & Plauger)


signature.asc
Description: PGP signature

Bug#811432: Krita no longer part of Calligra

[juichenieder-debbie]

Just found out about Krita, and thinking about giving it a try...


Does the fact that the latest stable version of Krita upstream (3.x) has now 
split from Calligra have any bearing
on this bug?

I.e. instead of trying to fix these issues, we should just start from a clean 
slate with Calligra?

Best,

Jack


P.S.  It looks like libilmbase6 -> libilmbase12 and libopenexr6 -> libopenexr22

Bug#833625: Request for fixing

[Garrett Kajmowicz]

Can we get some traction on this issue. I'm having the exact same problem.
However, I don't want to delete my SQLITE databases because they contain
any additional annotations and tags that I've added. I would expect a
software version upgrade to handle this transparently.

- Garrett

Bug#830568: python-asyncssh: accesses the internet during build

[Santiago Vila]

On Sat, 3 Sep 2016, Vincent Bernat wrote:

> [...] information leak [...]

This is not just a privacy issue but also a reproducibility issue.

It is bad that a package leaks information to the external world,
but it is even worse, I would say, that information from the outside
world is being used in any way by the package during the build.

If we allow packages to communicate with the external world during the
build, then a sentence like "this is the source for this binary package"
becomes completely meaningless, as the source package stops being all
you need to build the package.

I would try explaining that to upstream.

Thanks.

Bug#835667: marked as done (d-shlibs: FTBFS in testing (broken by new shellcheck))

[Debian Bug Tracking System]

Your message dated Sun, 04 Sep 2016 01:00:49 +0200
with message-id <147294364988.953.6502748623064315...@auryn.jones.dk>
and subject line Re: Bug#835667: d-shlibs: FTBFS in testing (broken by new 
shellcheck)
has caused the Debian Bug report #835667,
regarding d-shlibs: FTBFS in testing (broken by new shellcheck)
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.)


-- 
835667: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=835667
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:d-shlibs
Version: 0.75
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
test -x debian/rules
mkdir -p "."
CDBS WARNING:  copyright-check disabled - licensecheck (from devscripts 
package) is missing.
make: licensecheck: Command not found

Scanning upstream source for new/changed copyright notices...

set -e; LC_ALL=C.UTF-8 licensecheck --check '.*' --recursive --copyright 
--ignore '^(debian/(changelog|copyright(|_hints|_newhints)))$' --lines 9 * 
| /usr/lib/cdbs/licensecheck2dep5 > debian/copyright_newhints
/bin/sh: 1: licensecheck: not found
0 combinations of copyright and licensing found.
No new copyright notices found - assuming no news is good news...
touch debian/stamp-copyright-check
touch debian/stamp-upstream-cruft
/usr/bin/make -C . CFLAGS="-g -O2 -fdebug-prefix-map=/<>=. 
-fstack-protector-strong -Wformat -Werror=format-security" CXXFLAGS="-g -O2 
-fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat 
-Werror=format-security" CPPFLAGS="-Wdate-time -D_FORTIFY_SOURCE=2" 
LDFLAGS="-Wl,-z,relro" 
make[1]: Entering directory '/<>'
make[1]: Nothing to be done for 'all'.
make[1]: Leaving directory '/<>'
touch debian/stamp-makefile-build
/usr/bin/make -C . CFLAGS="-g -O2 -fdebug-prefix-map=/<>=. 
-fstack-protector-strong -Wformat -Werror=format-security" CXXFLAGS="-g -O2 
-fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat 
-Werror=format-security" CPPFLAGS="-Wdate-time -D_FORTIFY_SOURCE=2" 
LDFLAGS="-Wl,-z,relro" check
make[1]: Entering directory '/<>'
bash -n d-shlibmove
bash -n d-devlibdeps
shellcheck d-shlibmove

In d-shlibmove line 238:
while read A B; do
  ^-- SC2162: read without -r will mangle backslashes.


In d-shlibmove line 245:
while read A B; do
  ^-- SC2162: read without -r will mangle backslashes.

Makefile:8: recipe for target 'check' failed
make[1]: *** [check] Error 1
make[1]: Leaving directory '/<>'
/usr/share/cdbs/1/class/makefile.mk:113: recipe for target 
'debian/stamp-makefile-check' failed
make: *** [debian/stamp-makefile-check] Error 2
dpkg-buildpackage: error: debian/rules build-indep gave error exit status 2


This used to build ok in testing so the new shellcheck which
has just migrated to testing may be related to this.

Thanks.
--- End Message ---
--- Begin Message ---
Version: 0.76

Quoting Santiago Vila (2016-08-28 10:56:23)
> 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:
[...]
> shellcheck d-shlibmove
> 
> In d-shlibmove line 238:
> while read A B; do
>   ^-- SC2162: read without -r will mangle backslashes.
> 
> 
> In d-shlibmove line 245:
> while read A B; do
>   ^-- SC2162: read without -r will mangle backslashes.
> 
> Makefile:8: recipe for target 'check' failed

Thanks for reporting.

This was fixed with the release of d-shlibs 0.76.

 - Jonas

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

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


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

Processed: Re: Bug#835612: ikiwiki: FTBFS in testing (broken by new git)

[Debian Bug Tracking System]

Processing control commands:

> tags 835612 + fixed-upstream pending
Bug #835612 [src:ikiwiki] ikiwiki: FTBFS in testing (broken by new git)
Added tag(s) fixed-upstream and pending.

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

Bug#835612: ikiwiki: FTBFS in testing (broken by new git)

[Simon McVittie]

Control: tags 835612 + fixed-upstream pending

On Sat, 27 Aug 2016 at 15:34:30 +, Santiago Vila wrote:
> This used to build ok, so this failure seems related to git 2.9.3,
> which is in testing since a few days.

This is reproducible in an upstream build on current unstable, and should
now be fixed. I'll release the fix to Debian soon.

Thanks,
S

Bug#719382: marked as done (node-stringprep: FTBFS: /bin/sh: 1: node-waf: not found)

[Debian Bug Tracking System]

Your message dated Sun, 04 Sep 2016 00:53:45 +0200
with message-id <147294322588.953.869991314541340...@auryn.jones.dk>
and subject line Re: [Pkg-javascript-devel] Bug#719382: node-stringprep: FTBFS: 
/bin/sh: 1: node-waf: not found
has caused the Debian Bug report #719382,
regarding node-stringprep: FTBFS: /bin/sh: 1: node-waf: 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.)


-- 
719382: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=719382
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: node-stringprep
Version: 0.1.5-1
Severity: serious
Tags: jessie sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20130811 qa-ftbfs
Justification: FTBFS on amd64

Hi,

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

Maybe this is related to that as of node.js v0.8 node-waf was removed
and replaced with node-gyp (packaged independently).

Relevant part (hopefully):
>  debian/rules build
> test -x debian/rules
> mkdir -p "."
> 
> WARNING: copyright-check disabled - licensecheck (from devscripts package) is 
> missing.
> 
> touch debian/stamp-copyright-check
> touch debian/stamp-upstream-cruft
> NODE_PATH=/«PKGBUILDDIR»/debian/node-node-stringprep//usr/lib/nodejs node-waf 
> configure
> /bin/sh: 1: node-waf: not found
> make: *** [configure/node-node-stringprep] Error 127

The full build log is available from:
   
http://aws-logs.debian.net/ftbfs-logs/2013/08/11/node-stringprep_0.1.5-1_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 ---
Version: 0.6.2-1

Quoting David Suárez (2013-08-11 13:54:01)
> During a rebuild of all packages in sid, your package failed to build 
> on amd64.

Thanks for reporting.

This was fixed with the release of node-stringprep 0.6.2-1.

 - Jonas

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

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


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

Bug#836554: gnupg - file verification leaves agent running

[Bastian Blank]

Package: gnupg
Version: 2.1.15-2
Severity: grave

A simple verification of a inlined signed file leaves the agent running.
This makes it impossible to clean up the system properly.  This is for
example used by cdebootstrap.

As it is inline signed, it is not possible to use gpgv, which can't
decode messages.

Bastian

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

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

Versions of packages gnupg2 depends on:
ii  dpkg   1.18.9
ii  gnupg-agent2.1.11-7
ii  install-info   6.1.0.dfsg.1-8
ii  libassuan0 2.4.3-1
ii  libbz2-1.0 1.0.6-8
ii  libc6  2.23-2
ii  libgcrypt201.7.2-2
ii  libgpg-error0  1.24-1
ii  libksba8   1.3.4-3
ii  libreadline6   6.3-8+b4
ii  libsqlite3-0   3.13.0-1
ii  zlib1g 1:1.2.8.dfsg-2+b1

Versions of packages gnupg2 recommends:
pn  dirmngr  

Versions of packages gnupg2 suggests:
pn  gnupg-doc   
pn  parcimonie  
pn  xloadimage  

-- no debconf information

Bug#835278: marked as done ([runit] fails to upgrade cleanly)

[Debian Bug Tracking System]

Your message dated Sat, 03 Sep 2016 22:31:17 +
with message-id 
and subject line Bug#835278: fixed in runit 2.1.2-7
has caused the Debian Bug report #835278,
regarding [runit] fails to upgrade cleanly
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.)


-- 
835278: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=835278
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: runit
Version: 2.1.2-6

Preparing to unpack .../runit_2.1.2-6_amd64.deb ...
unsupported: /etc/service exists, but does not point to 
/etc/runit/runsvdir/current
dpkg: error processing archive /var/cache/apt/archives/runit_2.1.2-6_amd64.deb 
(--unpack):
 subprocess new pre-installation script returned error exit status 1

Something in the whole upgrade path here just isn't working right,
this is coming from 2.1.2-5 which had some stuff in /etc/runit/runsvdir/

 root@ruth:~# ls -l /etc/runit/runsvdir/
 total 4
 lrwxrwxrwx 1 root root7 Aug 24 00:13 current -> default
 drwxr-xr-x 2 root root 4096 Aug 24 00:13 default

but it was unused (default is empty).

-- 
Jamie Heilman http://audible.transient.net/~jamie/
--- End Message ---
--- Begin Message ---
Source: runit
Source-Version: 2.1.2-7

We believe that the bug you reported is fixed in the latest version of
runit, 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.
Dmitry Bogatov  (supplier of updated runit 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, 03 Sep 2016 20:51:31 +0300
Source: runit
Binary: runit runit-systemd runit-sysv getty-run runit-init
Architecture: source
Version: 2.1.2-7
Distribution: experimental
Urgency: medium
Maintainer: Dmitry Bogatov 
Changed-By: Dmitry Bogatov 
Description:
 getty-run  - runscripts to supervise getty processes
 runit  - system-wide service supervision
 runit-init - system-wide service supervision (as init system)
 runit-systemd - system-wide service supervision (systemd integration)
 runit-sysv - system-wide service supervision (sysv integration)
Closes: 835278
Changes:
 runit (2.1.2-7) experimental; urgency=medium
 .
   * Create /etc/runit/runsvdir/default directory and /etc/service directories
 as part of binary package, not in maintainer scripts. Empty directories are
 not pretty, but usually user installs some runscripts with 'runit' binary
 package, and will not notice issue.
   * Make upgrade from previous revisions (3,5,6th) piuparts-clean
 (Closes: #835278)
Checksums-Sha1:
 2f615ccf1900dcc107488ddd9fcd422b31f307fa 2114 runit_2.1.2-7.dsc
 398f7bf995acd58797c1d4a7bcd75cc1fc83aa66 110916 runit_2.1.2.orig.tar.gz
 0223758d681ef70a2172664195c15532f77c81a3 18728 runit_2.1.2-7.debian.tar.xz
Checksums-Sha256:
 fb85332c76f723f797f550fe799a1e25ab4ebdd4d39e102bfce2c1bf7c9d44ba 2114 
runit_2.1.2-7.dsc
 6fd0160cb0cf1207de4e66754b6d39750cff14bb0aa66ab49490992c0c47ba18 110916 
runit_2.1.2.orig.tar.gz
 d454e5e442a4884c34ade68745d80547b2cdf0bfac45e54a45a7f8ebaaf579cd 18728 
runit_2.1.2-7.debian.tar.xz
Files:
 71d0515ebdecd303daecf2880f0c25df 2114 admin optional runit_2.1.2-7.dsc
 6c985fbfe3a34608eb3c53dc719172c4 110916 admin optional runit_2.1.2.orig.tar.gz
 fa05932798cb2072c073d1e032e2cccb 18728 admin optional 
runit_2.1.2-7.debian.tar.xz

-BEGIN PGP SIGNATURE-
Version: GnuPG v2

iQIcBAEBCAAGBQJXy0iHAAoJEPNPCXROn13ZhbsQAK5TwHGZyry14BiSUbA6Q511
eX6mZBWccw93t+Hzmw0N3SXHEOy4US/AAYhjOYsp118SM95OVVeZCMm7BAFM/jb+
5h5kua5+nWDsADI6jPrSzr0zJfQTD0sndxxW6QQQDDvoEzygBc2+qvYMnsAY/poB
z7shrfSIL6SzvW5yZLc2ci8DuFHpJeTf7m1GrpmDl0aj1yqdOyUxa7HrunDtytB+
eEMeyA64xQ93YFw6FYmkjuQiNGOyMxeYKd5aNFMTXeexFMRkrHQzRAKm+GxTxwYz
rBqmUME6zzhRHQbC9nnJ0LtURbuZTjVby+0QYQTmpOoRFQL7NaXNjZ/+vwDSQjLt
alO85psuXb2QBsQzyNeMKGdESTR/Y9UAr/lGrsLVjEdTS4ZZD/YfDI0Yru6gGZmd
2FHGTxXtp4HUDrX6YRhR3WGwGvodJOVYguVsA+rOhHYQ7VHR1WgrBCKyUHkwSv6Y
J4AteikiZxCElt/JX/pAGlyOt2CTN2NMDeTB3EdRSvxo+BiOpyYntX7ickme80dH
v44/lk7idTOSxnRnhdN2nGrS0greuO6+9QMThamI5FHNWUYCOygwzu8rR1u/1MYg
qEyccv24ktjjtkfa8VuVJXiOHp2o5mhUjZ9M/ojTNir5jC1dSYoHnYMcdd7Aq/p9
5cJyXRJfdYMWCcttV0hI
=hQbR
-END PGP SIGNATURE

Bug#817038: marked as done (transifex-client: Use python-six instead of the embedded version of python-urllib3)

[Debian Bug Tracking System]

Your message dated Sat, 03 Sep 2016 22:32:10 +
with message-id 
and subject line Bug#817038: fixed in transifex-client 0.11.1+git15~g655c5e9-1.1
has caused the Debian Bug report #817038,
regarding transifex-client: Use python-six instead of the embedded version of 
python-urllib3
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.)


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

Package: transifex-client
Version: 0.11.1+git15~g655c5e9
Severity: important
Tags: patch

Transifex imports six from urlilib3 embedded version.
Since python-urllib3 (1.13.1-1) debian dropped the
embedded six module which, although it makes sense, broke
transifex-client.

Please consider applying the attached patch that switches
imports to python-six.


>From 6937c1065204cd6801f6cefe9fa7b5d9a37fe4e3 Mon Sep 17 00:00:00 2001
From: Christos Trochalakis 
Date: Mon, 7 Mar 2016 12:16:39 +0200
Subject: [PATCH] Use six library instead of the one embedded in urllib3

---
 requirements.txt   | 1 +
 txclib/commands.py | 2 +-
 txclib/config.py   | 2 +-
 txclib/project.py  | 2 +-
 txclib/utils.py| 4 ++--
 5 files changed, 6 insertions(+), 5 deletions(-)

diff --git a/requirements.txt b/requirements.txt
index a42590b..71aa090 100644
--- a/requirements.txt
+++ b/requirements.txt
@@ -1 +1,2 @@
 urllib3
+six
diff --git a/txclib/commands.py b/txclib/commands.py
index 122ecca..b221c02 100644
--- a/txclib/commands.py
+++ b/txclib/commands.py
@@ -25,7 +25,7 @@ try:
 except ImportError:
 import ConfigParser as configparser
 
-from urllib3.packages.six.moves import input
+from six.moves import input
 
 from txclib import utils, project
 from txclib.utils import parse_json, compile_json, files_in_project
diff --git a/txclib/config.py b/txclib/config.py
index f37f0a6..4bad9da 100644
--- a/txclib/config.py
+++ b/txclib/config.py
@@ -3,7 +3,7 @@ try:
 except ImportError:
 import ConfigParser as configparser
 
-from urllib3.packages import six
+import six
 
 
 class OrderedRawConfigParser(configparser.RawConfigParser):
diff --git a/txclib/project.py b/txclib/project.py
index 0961abf..55c24ae 100644
--- a/txclib/project.py
+++ b/txclib/project.py
@@ -18,7 +18,7 @@ except ImportError:
 from txclib import web
 from txclib import utils
 from urllib3.exceptions import SSLError
-from urllib3.packages import six
+import six
 from txclib.urls import API_URLS
 from txclib.config import OrderedRawConfigParser, Flipdict
 from txclib.log import logger
diff --git a/txclib/utils.py b/txclib/utils.py
index 3f4ed81..75263fb 100644
--- a/txclib/utils.py
+++ b/txclib/utils.py
@@ -13,8 +13,8 @@ except ImportError:
 
 from email.parser import Parser
 from urllib3.exceptions import SSLError
-from urllib3.packages import six
-from urllib3.packages.six.moves import input
+import six
+from six.moves import input
 from txclib.urls import API_URLS
 from txclib.exceptions import UnknownCommandError
 from txclib.paths import posix_path, native_path, posix_sep
-- 
2.7.0

--- End Message ---
--- Begin Message ---
Source: transifex-client
Source-Version: 0.11.1+git15~g655c5e9-1.1

We believe that the bug you reported is fixed in the latest version of
transifex-client, 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.
Felix Geyer  (supplier of updated transifex-client 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: Sat, 03 Sep 2016 22:17:45 +0200
Source: transifex-client
Binary: transifex-client
Architecture: source
Version: 0.11.1+git15~g655c5e9-1.1
Distribution: unstable
Urgency: medium
Maintainer: Janos Guljas 
Changed-By: Felix Geyer 
Description:
 transifex-client - Command line interface for Transifex
Closes: 817038
Changes:
 transifex-client (0.11.1+git15~g655c5e9-1.1) unstable; urgency=medium
 .
   * Non-maintainer upload.
   * Use the six library instead of the one embedded in urllib3.
 - Backport upstream commits.
 - Closes: #817038
Checksums-Sha1:
 92b42024126d1e6f9a795b04a4b3e02c8e760ec1 2217 
transifex-client_0.11.1+git15~g655c5e

Bug#835903: marked as done (runit: upgrade failed)

[Debian Bug Tracking System]

Your message dated Sat, 03 Sep 2016 22:31:17 +
with message-id 
and subject line Bug#835278: fixed in runit 2.1.2-7
has caused the Debian Bug report #835278,
regarding runit: upgrade failed
to be marked as done.

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

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


-- 
835278: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=835278
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: runit
Version: 2.1.2-5
Severity: grave


Hi, 

upgrade to 2.1.2-6 give errors:

[quote]
Möchten Sie fortfahren? [J/n] 
Laden der Fehlerberichte … Erledigt
»Found/Fixed«-Informationen werden ausgewertet … Erledigt
Lese Changelogs... Fertig
(Lese Datenbank ... 424257 Dateien und Verzeichnisse sind derzeit installiert.)
Vorbereitung zum Entpacken von .../runit_2.1.2-6_amd64.deb ...
unsupported: /etc/service exists, but does not point to 
/etc/runit/runsvdir/current
dpkg: Fehler beim Bearbeiten des Archivs 
/var/cache/apt/archives/runit_2.1.2-6_amd64.deb (--unpack):
 Unterprozess neues pre-installation-Skript gab den Fehlerwert 1 zurück
Fehler traten auf beim Bearbeiten von:
 /var/cache/apt/archives/runit_2.1.2-6_amd64.deb
E: Sub-process /usr/bin/dpkg returned an error code (1)
[/quote]


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

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

Versions of packages runit depends on:
ii  libc6  2.23-5

runit recommends no packages.

Versions of packages runit suggests:
pn  socklog-run  

-- no debconf information
--- End Message ---
--- Begin Message ---
Source: runit
Source-Version: 2.1.2-7

We believe that the bug you reported is fixed in the latest version of
runit, 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.
Dmitry Bogatov  (supplier of updated runit 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, 03 Sep 2016 20:51:31 +0300
Source: runit
Binary: runit runit-systemd runit-sysv getty-run runit-init
Architecture: source
Version: 2.1.2-7
Distribution: experimental
Urgency: medium
Maintainer: Dmitry Bogatov 
Changed-By: Dmitry Bogatov 
Description:
 getty-run  - runscripts to supervise getty processes
 runit  - system-wide service supervision
 runit-init - system-wide service supervision (as init system)
 runit-systemd - system-wide service supervision (systemd integration)
 runit-sysv - system-wide service supervision (sysv integration)
Closes: 835278
Changes:
 runit (2.1.2-7) experimental; urgency=medium
 .
   * Create /etc/runit/runsvdir/default directory and /etc/service directories
 as part of binary package, not in maintainer scripts. Empty directories are
 not pretty, but usually user installs some runscripts with 'runit' binary
 package, and will not notice issue.
   * Make upgrade from previous revisions (3,5,6th) piuparts-clean
 (Closes: #835278)
Checksums-Sha1:
 2f615ccf1900dcc107488ddd9fcd422b31f307fa 2114 runit_2.1.2-7.dsc
 398f7bf995acd58797c1d4a7bcd75cc1fc83aa66 110916 runit_2.1.2.orig.tar.gz
 0223758d681ef70a2172664195c15532f77c81a3 18728 runit_2.1.2-7.debian.tar.xz
Checksums-Sha256:
 fb85332c76f723f797f550fe799a1e25ab4ebdd4d39e102bfce2c1bf7c9d44ba 2114 
runit_2.1.2-7.dsc
 6fd0160cb0cf1207de4e66754b6d39750cff14bb0aa66ab49490992c0c47ba18 110916 
runit_2.1.2.orig.tar.gz
 d454e5e442a4884c34ade68745d80547b2cdf0bfac45e54a45a7f8ebaaf579cd 18728 
runit_2.1.2-7.debian.tar.xz
Files:
 71d0515ebdecd303daecf2880f0c25df 2114 admin optional runit_2.1.2-7.dsc
 6c985fbfe3a34608eb3c53dc719172c4 110916 admin optional runit_2.1.2.orig.tar.gz
 fa05932798cb2072c073d1e032e2cccb 18728 admin optional 
runit_2.1.2-7.debian.tar.xz

-BEGIN PGP SIGNATURE-
Version: GnuPG v2

iQIcBAEBCAAGBQJXy0iHAAoJEPNPCXROn13ZhbsQAK5TwHGZyry14BiSUbA6Q511
eX6mZBWccw93t+Hzmw0N3SXHEOy4US/AAYhjOYsp118SM95OVVeZCMm7BAFM/jb+
5h5kua5+nWDsADI6jPrSzr0zJfQTD0sndxxW6QQQDDvoEzygBc2+qvYMnsAY/poB
z7shrfSIL6SzvW5yZLc2ci8DuFHpJeTf7m1GrpmD

Bug#835413: marked as done (pygobject: wrong enum to hash conversion on 64-bit big endian)

[Debian Bug Tracking System]

Your message dated Sat, 03 Sep 2016 22:29:51 +
with message-id 
and subject line Bug#835413: fixed in pygobject 3.21.91-2
has caused the Debian Bug report #835413,
regarding pygobject: wrong enum to hash conversion on 64-bit big endian
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.)


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

libsecret has test suite failure ons mipsel and s390x [1]

mipsel:
FAIL: test-session 4 /session/ensure-async-aes
FAIL: test-collection 18 /collection/delete-sync

s390x:
FAIL: test-collection 18 /collection/delete-sync
the build gets stuck and is killed after 150min



[1] https://buildd.debian.org/status/package.php?p=libsecret
-- System Information:
Debian Release: stretch/sid
  APT prefers unstable-debug
  APT policy: (500, 'unstable-debug'), (500, 'unstable'), (500, 'testing'), 
(200, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 4.5.0-1-amd64 (SMP w/4 CPU cores)
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
--- End Message ---
--- Begin Message ---
Source: pygobject
Source-Version: 3.21.91-2

We believe that the bug you reported is fixed in the latest version of
pygobject, 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.
Michael Biebl  (supplier of updated pygobject 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: Sun, 04 Sep 2016 00:02:14 +0200
Source: pygobject
Binary: python-gi python3-gi python-gi-cairo python-gi-dbg python3-gi-dbg 
python-gi-dev python3-gi-cairo python-gobject python-gobject-dbg 
python-gobject-dev
Architecture: source
Version: 3.21.91-2
Distribution: unstable
Urgency: medium
Maintainer: Debian GNOME Maintainers 

Changed-By: Michael Biebl 
Description:
 python-gi  - Python 2.x bindings for gobject-introspection libraries
 python-gi-cairo - Python Cairo bindings for the GObject library
 python-gi-dbg - Python bindings for the GObject library (debug extension)
 python-gi-dev - development headers for GObject Python bindings
 python-gobject - Python 2.x bindings for GObject - transitional package
 python-gobject-dbg - Python 2.x debugging modules for GObject - transitional 
package
 python-gobject-dev - Python 2.x development headers for GObject - transitional 
package
 python3-gi - Python 3 bindings for gobject-introspection libraries
 python3-gi-cairo - Python 3 Cairo bindings for the GObject library
 python3-gi-dbg - Python 3 bindings for gobject-introspection libraries (debug 
exte
Closes: 835413 836049
Changes:
 pygobject (3.21.91-2) unstable; urgency=medium
 .
   [ Aurelien Jarno ]
   * Fix wrong enum to hash conversion on 64-bit big endian. (Closes: #835413)
 .
   [ Michael Biebl ]
   * Use dbus-run-session instead of dbus-launch to run the tests.
 (Closes: #836049)
   * Handle nullable filename parameters. This fixes a test suite error in
 test_spawn_async_with_pipes triggered by an annotation change in glib.
   * Drop override for dh_python2, no longer needed.
Checksums-Sha1:
 0d4b42385e53bda94df348915c74be1dc522542b 3295 pygobject_3.21.91-2.dsc
 b7e156c3bba14cdcef81d2c77e2c98bd0e289bc9 23412 
pygobject_3.21.91-2.debian.tar.xz
Checksums-Sha256:
 f4c5bbc54ef2616336139d3cc237d15b088adf0c6982f66c041ef764e970c47c 3295 
pygobject_3.21.91-2.dsc
 76b472b19ea4cf3201c7595a49cb61c3c3038d41eec1ec9c8423aedfc14c1bb2 23412 
pygobject_3.21.91-2.debian.tar.xz
Files:
 ac21c2ba1fd7ef9d0eb0b9847b7279eb 3295 python optional pygobject_3.21.91-2.dsc
 cf32bbfb33cf5b6c330c6e543c1dfd06 23412 python optional 
pygobject_3.21.91-2.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQIuBAEBCAAYBQJXy0iNERxiaWVibEBkZWJpYW4ub3JnAAoJEGrh3w1gjyLcJeIP
/1z+DC87O36gUpEOltv3AmbvMa5e8LLvZKCRKe6jsegffs+DWXLBFPjCkhA0Vaaw
FJEn2C6Cnwf78Y0sPV2t/UpcCecpdE/MCaBI+7oLq2M3tZCpGu3FS0AUvrc1qoqn
qMT7ECEYP/iP/pstQIq0cM+RFMS0pjHIww29oIErZK7Snx2unG16Gyghp4Dg4IGn
yljYLsJLSRAA6uQSg

Bug#826300: [Pkg-pascal-devel] Bug#826300: Share knowledge on fpc and powerpc issue

[peter green]

On 03/09/16 14:15, Graham Inggs wrote:

A wild stab in the dark: don't we need to binNMU lazarus before we can
build packages with it?
   
I'd say yes, in that build log it looks like it's lazbuild which is 
crashing. So yes a binnmu of lazarus seems the next step.

Then, don't we need to binNMU everything that build with the old fpc
for powerpc?
   
Afaict we need to binnmu binaries that were built with the old fpc AND 
built against one or more C libraries. Pure pascal programs should be ok.

Bug#828715: marked as done (graphite-api: FTBFS: ImportError: No module named 'sphinx_rtd_theme')

[Debian Bug Tracking System]

Your message dated Sat, 03 Sep 2016 22:27:59 +
with message-id 
and subject line Bug#828715: fixed in graphite-api 1.1.3-2
has caused the Debian Bug report #828715,
regarding graphite-api: FTBFS: ImportError: No module named 'sphinx_rtd_theme'
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.)


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

Dear Maintainer,

graphite-api fails to build from source in unstable/amd64:

  [..]

  'build/scripts-3.5' does not exist -- can't clean it
 dh_clean -O--buildsystem=pybuild
   debian/rules build
  dh build --with python3,sphinxdoc --buildsystem pybuild
 dh_testdir -O--buildsystem=pybuild
 dh_update_autotools_config -O--buildsystem=pybuild
 dh_auto_configure -O--buildsystem=pybuild
  I: pybuild base:184: python3.5 setup.py config 
  running config
 dh_auto_build -O--buildsystem=pybuild
  I: pybuild base:184: /usr/bin/python3 setup.py build 
  running build
  running build_py
  creating 
/home/lamby/temp/cdt.20160627075457.Algpr1UWZ1.graphite-api/graphite-api-1.1.3/.pybuild/pythonX.Y_3.5/build/graphite_api
  copying graphite_api/utils.py -> 
/home/lamby/temp/cdt.20160627075457.Algpr1UWZ1.graphite-api/graphite-api-1.1.3/.pybuild/pythonX.Y_3.5/build/graphite_api
  copying graphite_api/functions.py -> 
/home/lamby/temp/cdt.20160627075457.Algpr1UWZ1.graphite-api/graphite-api-1.1.3/.pybuild/pythonX.Y_3.5/build/graphite_api
  copying graphite_api/__init__.py -> 
/home/lamby/temp/cdt.20160627075457.Algpr1UWZ1.graphite-api/graphite-api-1.1.3/.pybuild/pythonX.Y_3.5/build/graphite_api
  copying graphite_api/carbonlink.py -> 
/home/lamby/temp/cdt.20160627075457.Algpr1UWZ1.graphite-api/graphite-api-1.1.3/.pybuild/pythonX.Y_3.5/build/graphite_api
  copying graphite_api/storage.py -> 
/home/lamby/temp/cdt.20160627075457.Algpr1UWZ1.graphite-api/graphite-api-1.1.3/.pybuild/pythonX.Y_3.5/build/graphite_api
  copying graphite_api/node.py -> 
/home/lamby/temp/cdt.20160627075457.Algpr1UWZ1.graphite-api/graphite-api-1.1.3/.pybuild/pythonX.Y_3.5/build/graphite_api
  copying graphite_api/readers.py -> 
/home/lamby/temp/cdt.20160627075457.Algpr1UWZ1.graphite-api/graphite-api-1.1.3/.pybuild/pythonX.Y_3.5/build/graphite_api
  copying graphite_api/search.py -> 
/home/lamby/temp/cdt.20160627075457.Algpr1UWZ1.graphite-api/graphite-api-1.1.3/.pybuild/pythonX.Y_3.5/build/graphite_api
  copying graphite_api/config.py -> 
/home/lamby/temp/cdt.20160627075457.Algpr1UWZ1.graphite-api/graphite-api-1.1.3/.pybuild/pythonX.Y_3.5/build/graphite_api
  copying graphite_api/app.py -> 
/home/lamby/temp/cdt.20160627075457.Algpr1UWZ1.graphite-api/graphite-api-1.1.3/.pybuild/pythonX.Y_3.5/build/graphite_api
  copying graphite_api/encoders.py -> 
/home/lamby/temp/cdt.20160627075457.Algpr1UWZ1.graphite-api/graphite-api-1.1.3/.pybuild/pythonX.Y_3.5/build/graphite_api
  copying graphite_api/intervals.py -> 
/home/lamby/temp/cdt.20160627075457.Algpr1UWZ1.graphite-api/graphite-api-1.1.3/.pybuild/pythonX.Y_3.5/build/graphite_api
  copying graphite_api/middleware.py -> 
/home/lamby/temp/cdt.20160627075457.Algpr1UWZ1.graphite-api/graphite-api-1.1.3/.pybuild/pythonX.Y_3.5/build/graphite_api
  creating 
/home/lamby/temp/cdt.20160627075457.Algpr1UWZ1.graphite-api/graphite-api-1.1.3/.pybuild/pythonX.Y_3.5/build/graphite_api/render
  copying graphite_api/render/__init__.py -> 
/home/lamby/temp/cdt.20160627075457.Algpr1UWZ1.graphite-api/graphite-api-1.1.3/.pybuild/pythonX.Y_3.5/build/graphite_api/render
  copying graphite_api/render/datalib.py -> 
/home/lamby/temp/cdt.20160627075457.Algpr1UWZ1.graphite-api/graphite-api-1.1.3/.pybuild/pythonX.Y_3.5/build/graphite_api/render
  copying graphite_api/render/attime.py -> 
/home/lamby/temp/cdt.20160627075457.Algpr1UWZ1.graphite-api/graphite-api-1.1.3/.pybuild/pythonX.Y_3.5/build/graphite_api/render
  copying graphite_api/render/glyph.py -> 
/home/lamby/temp/cdt.20160627075457.Algpr1UWZ1.graphite-api/graphite-api-1.1.3/.pybuild/pythonX.Y_3.5/build/graphite_api/render
  copying graphite_api/render/grammar.py -> 
/home/lamby/temp/cdt.20160627075457.Algpr1UWZ1.graphite-api/graphite-api-1.1.3/.pybuild/pythonX.Y_3.5/build/graphite_api/render
  creating 
/home/lamby/temp/cdt.20160627075457.Algpr1UWZ1.graphite-api/graphite-api-1.1.3/.pybuild/pythonX.Y_3.5/build/graphite_api

Bug#835411: marked as done (eigen3: causes FTBFS in other packages)

[Debian Bug Tracking System]

Your message dated Sat, 03 Sep 2016 22:25:02 +
with message-id 
and subject line Bug#835411: fixed in eigen3 3.3~beta2-2
has caused the Debian Bug report #835411,
regarding eigen3: causes FTBFS in other packages
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.)


-- 
835411: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=835411
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: ceres-solver
Version: 1.11.0~dfsg0-5
Severity: serious
Tags: upstream
Justification: Policy 2.1

As found out through reproducible builds, ceres-solver FTBFS since
eigen3 3.3~beta2 was uploaded:
https://tests.reproducible-builds.org/debian/rbuild/unstable/amd64/ceres-solver_1.11.0~dfsg0-5.rbuild.log

Building with eigen3 3.3~beta1 works without problems.
--- End Message ---
--- Begin Message ---
Source: eigen3
Source-Version: 3.3~beta2-2

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

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Format: 1.8
Date: Sat, 03 Sep 2016 22:14:51 +0200
Source: eigen3
Binary: libeigen3-dev libeigen3-doc
Architecture: source
Version: 3.3~beta2-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Science Maintainers 

Changed-By: Anton Gladky 
Description:
 libeigen3-dev - lightweight C++ template library for linear algebra
 libeigen3-doc - eigen3 API documentation
Closes: 813233 835411
Changes:
 eigen3 (3.3~beta2-2) unstable; urgency=medium
 .
   [ Michael R. Crusoe ]
   * [221266e] Fix grammar error. (Closes: #813233)
 .
   [ Anton Gladky ]
   * [f702569] Add missing patch.
   * [6e583ef] Apply cme fix dpkg.
 .
   [ Gael Guennebaud ]
   * [c5cb3df] Fix compilation in check_for_aliasing. (Closes: #835411)
Checksums-Sha1:
 f9ff674ed63ce418e6d65f033b0b8014bc6742be 2193 eigen3_3.3~beta2-2.dsc
 fe2e1208d64486bdfa3be93d4a5eb5130989667e 35012 eigen3_3.3~beta2-2.debian.tar.xz
Checksums-Sha256:
 a1a0ac6129ea2709df556760c47ae1e5aaa11b25cfb683920fc3803e1384ea95 2193 
eigen3_3.3~beta2-2.dsc
 cf1edfe02130dae3937791c7745380aeee929388a84c6b92ccd681a9c041c663 35012 
eigen3_3.3~beta2-2.debian.tar.xz
Files:
 f01cec77e9c240b3db421ff50f35f9b1 2193 libdevel extra eigen3_3.3~beta2-2.dsc
 3cf09a07e46e86a3557b2bdfde4855b5 35012 libdevel extra 
eigen3_3.3~beta2-2.debian.tar.xz

-BEGIN PGP SIGNATURE-
Version: GnuPG v1

iQIcBAEBAgAGBQJXyy+TAAoJENPhc4PPp/8Grj0QAIXT+M9JR9PJsXRTlGw3JEp0
7T+/tZgpWoIVqWZhOr164lhrY8WtwkZ99K0oD32f5h8A+FkdLkEsbmhGuXvCQFpy
OoVKLPt34qrrBjMi2qephEC/oEXD7yrewY7XuzCwlGkl/wZwLmPuZDHT57TCWg5H
DJoyE74bwbLrYY75ExiyHvvyQTgzrI+Y6jEIqDOTFtrWX/7AxZ5PktxGa38hKdK0
hXYKeHRkuYOdG67/bZ3t4oqpF+nhbL/cXx03cveNxF8XU6XdoX5HkIyeeX16kwSp
f05PlKxTOvlm9Mk76QdQB7zfMz37UjGKrNqtu+SueKWVz5gymaH3W6mhRBcApCDN
0cMsShm6XgGTosSdcpIz9gZE/TdKpu297LR3imnrjwOhGAXfTKwMXsMmj2HpT0wG
cnw7YAuoRsvfiGYCTShcGdIyqQyubgkejoA51WqWX+fQSnRNlef3+ZBfepbgTAvZ
TpcLRGr9vC6NEJny/9I+2pvScM5+fru9oIMgEcxM1hmOefoVG1gDQwSEN3F+bUAt
AZsPGsJuOHXITZ6Jz8JCh5IVYG72JHeuuR8YSvAJGQzlY8Q0dF3FaaC8vL6OVmrT
gTJEXQatTUbO5u9mpJgzGC4FDq+E7BEe8WpzsRu0PE2wxsApR4NMrZWdaBlDxzUJ
bpLUn8eG+miOzutT+tFF
=1+OT
-END PGP SIGNATURE End Message ---

Bug#830568: python-asyncssh: accesses the internet during build

[Chris Lamb]

> If your bug was wishlist, I would just ignore it. It is severity serious
> and I have to handle it. Maybe it is legitimate. Maybe not.

Oh! I thought we were discussing whether it was a bug at all — hence the
time you spent addressing whether privacy leaking is valuable — not the
severity of the bug itself.

As I probably dislike "bug severity wars" even more than Debian Policy
wording debates, free to change it to whatever you feel is appropriate… :)

Howevever, it does feel regrettable you readily admit you might completely
ignore a bug.


Regards,

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

Bug#830568: python-asyncssh: accesses the internet during build

[Vincent Bernat]

 ❦  3 septembre 2016 21:22 CEST, Chris Lamb  :

>> The policy says "may not". I am not a native speaker, but for me, this
>> is not like "must not". Since you are a native speaker, I think you know
>> better: is it optional or not?
>
> May I suggest an alternative approach…? We have two cases here:
>
>  a) Debian Policy states it is a bug in python-asyncssh.
>
>  b) Debian Policy does not state it is a bug python-asyncssh.
>
> In both cases it would be perfectly legitimate to continue discussing
> whether it *should* be a bug in python-asyncssh.
>
> In other words, tedious haggling over the wording and intention of a
> document neither of us wrote is unproductive to the goal of improving
> Debian. So, let's just skip all of that.

Well, what you think is productive/improvement, I think this is a waste
of time. Let's say I disable the test.  Next release, I will have to
rebase the patch. Next release, upstream will have added a test, I don't
notice it, you'll file another bug, another upload to fix that. Upstream
may notice that I am crippling its test suite. I'll have to
explain. They may or may not understand. I don't want to do all that.

The time I can spend on Debian is limited. If your bug was wishlist, I
would just ignore it. It is severity serious and I have to handle
it. Maybe it is legitimate. Maybe not. That's why I would have feeled
more comfortable if this was discussed on debian-devel@.
-- 
There is a great discovery still to be made in Literature: that of
paying literary men by the quantity they do NOT write.


signature.asc
Description: PGP signature

Bug#830377: Reduce bug`s severity?

[Anton Gladky]

Hi all,

it looks like this test failure is the random case. I was not
able to reproduce it building it 2 times on barriere.debian.org.

I propose to reduce the bug severity to "normal".

Thanks

Anton

Bug#836538: nipy: FTBFS in testing (failing tests)

[Yaroslav Halchenko]

On September 3, 2016 4:01:16 PM EDT, Santiago Vila  wrote:
>Package: src:nipy
>Version: 0.4.0+git26-gf8d3149-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 --buildsystem=python_distutils --with=python2 build-indep
>   dh_testdir -i -O--buildsystem=python_distutils
>   dh_update_autotools_config -i -O--buildsystem=python_distutils
>   dh_auto_configure -i -O--buildsystem=python_distutils
>   debian/rules override_dh_auto_build
>make[1]: Entering directory '/<>/nipy-0.4.0+git26-gf8d3149'
>dh_auto_build
>pyversions: missing X(S)-Python-Version in control file, fall back to
>debian/pyversions
>   python-dbg setup.py build --force
>lapack_opt_info:
>openblas_lapack_info:
>libraries openblas not found in ['/usr/local/lib', '/usr/lib',
>'/usr/lib/x86_64-linux-gnu']
>
>[... snipped ...]
>
>../<>/nipy-0.4.0+git26-gf8d3149/debian/tmp/usr/lib/python2.7/dist-packages/nipy/labs/viz_tools/slicers.py:376:
>UserWarning: empty mask
>  get_mask_bounds(not_mask, affine)
>.S../<>/nipy-0.4.0+git26-gf8d3149/debian/tmp/usr/lib/python2.7/dist-packages/nipy/labs/mask.py:235:
>VisibleDeprecationWarning: using a non-integer number instead of an
>integer will result in an error in the future
>  delta = sorted_input[limiteinf + 1:limitesup + 1] \
>/<>/nipy-0.4.0+git26-gf8d3149/debian/tmp/usr/lib/python2.7/dist-packages/nipy/labs/mask.py:236:
>VisibleDeprecationWarning: using a non-integer number instead of an
>integer will result in an error in the future
>  - sorted_input[limiteinf:limitesup]
>/<>/nipy-0.4.0+git26-gf8d3149/debian/tmp/usr/lib/python2.7/dist-packages/nipy/labs/mask.py:238:
>VisibleDeprecationWarning: using a non-integer number instead of an
>integer will result in an error in the future
>  threshold = 0.5 * (sorted_input[ia + limiteinf]
>/<>/nipy-0.4.0+git26-gf8d3149/debian/tmp/usr/lib/python2.7/dist-packages/nipy/labs/mask.py:239:
>VisibleDeprecationWarning: using a non-integer number instead of an
>integer will result in an error in the future
>  + sorted_input[ia + limiteinf + 1])
>/usr/lib/python2.7/dist-packages/numpy/lib/function_base.py:2569:
>RuntimeWarning: invalid value encountered in true_divide
>  c /= stddev[:, None]
>/usr/lib/python2.7/dist-packages/numpy/lib/function_base.py:2570:
>RuntimeWarning: invalid value encountered in true_divide
>  c /= stddev[None, :]
>/<>/nipy-0.4.0+git26-gf8d3149/debian/tmp/usr/lib/python2.7/dist-packages/nipy/modalities/fmri/tests/test_dmtx.py:407:
>FutureWarning: elementwise comparison failed; returning scalar instead,
>but in the future will perform elementwise comparison
>  idx = paradigm.onset[paradigm.con_id == 0].astype(np.int)
>/<>/nipy-0.4.0+git26-gf8d3149/debian/tmp/usr/lib/python2.7/dist-packages/nipy/modalities/fmri/tests/test_dmtx.py:407:
>VisibleDeprecationWarning: using a boolean instead of an integer will
>result in an error in the future
>  idx = paradigm.onset[paradigm.con_id == 0].astype(np.int)
>../<>/nipy-0.4.0+git26-gf8d3149/debian/tmp/usr/lib/python2.7/dist-packages/nipy/modalities/fmri/tests/test_dmtx.py:429:
>FutureWarning: elementwise comparison failed; returning scalar instead,
>but in the future will perform elementwise comparison
>  idx = bp.onset[bp.con_id == 1].astype(np.int)
>/<>/nipy-0.4.0+git26-gf8d3149/debian/tmp/usr/lib/python2.7/dist-packages/nipy/modalities/fmri/tests/test_dmtx.py:429:
>VisibleDeprecationWarning: using a boolean instead of an integer will
>result in an error in the future
>  idx = bp.onset[bp.con_id == 1].astype(np.int)
>/<>/nipy-0.4.0+git26-gf8d3149/debian/tmp/usr/lib/python2.7/dist-packages/nipy/modalities/fmri/glm.py:581:
>UserWarning: Contrast for session 1 is null
>  warn('Contrast for session %d is null' % i)
>S.../<>/nipy-0.4.0+git26-gf8d3149/debian/tmp/usr/lib/python2.7/dist-packages/nipy/modalities/fmri/tests/test_utils.py:212:
>VisibleDeprecationWarning: using a non-integer number instead of an
>integer will result in an error in the future
>  z1s = np.zeros((np.round(1./dt)))
>..
>==
>ERROR: nipy.io.tests.test_image_io.test_badfile
>--
>Traceback (most recent call last):
>File "/usr/lib/python2.7/dist-packages/nose/case.py", line 197, in
>runTest
>self.test(*self.arg)
>File
>"/<>/nipy-0.4.0+git26-gf8d3149/debian/tmp/usr/lib/python2.7/dist-packages/nipy/io/tests/test_image_io.py",
>line 44, in test_badfile
>assert_raises(ImageFileError, load_image, filename)
>File "/usr/lib/python2.7/dist-packages/numpy/testing/utils.py",

Bug#836538: nipy: FTBFS in testing (failing tests)

[Santiago Vila]

Package: src:nipy
Version: 0.4.0+git26-gf8d3149-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 --buildsystem=python_distutils --with=python2 build-indep
   dh_testdir -i -O--buildsystem=python_distutils
   dh_update_autotools_config -i -O--buildsystem=python_distutils
   dh_auto_configure -i -O--buildsystem=python_distutils
   debian/rules override_dh_auto_build
make[1]: Entering directory '/<>/nipy-0.4.0+git26-gf8d3149'
dh_auto_build
pyversions: missing X(S)-Python-Version in control file, fall back to 
debian/pyversions
python-dbg setup.py build --force
lapack_opt_info:
openblas_lapack_info:
  libraries openblas not found in ['/usr/local/lib', '/usr/lib', 
'/usr/lib/x86_64-linux-gnu']

[... snipped ...]

../<>/nipy-0.4.0+git26-gf8d3149/debian/tmp/usr/lib/python2.7/dist-packages/nipy/labs/viz_tools/slicers.py:376:
 UserWarning: empty mask
  get_mask_bounds(not_mask, affine)
.S../<>/nipy-0.4.0+git26-gf8d3149/debian/tmp/usr/lib/python2.7/dist-packages/nipy/labs/mask.py:235:
 VisibleDeprecationWarning: using a non-integer number instead of an integer 
will result in an error in the future
  delta = sorted_input[limiteinf + 1:limitesup + 1] \
/<>/nipy-0.4.0+git26-gf8d3149/debian/tmp/usr/lib/python2.7/dist-packages/nipy/labs/mask.py:236:
 VisibleDeprecationWarning: using a non-integer number instead of an integer 
will result in an error in the future
  - sorted_input[limiteinf:limitesup]
/<>/nipy-0.4.0+git26-gf8d3149/debian/tmp/usr/lib/python2.7/dist-packages/nipy/labs/mask.py:238:
 VisibleDeprecationWarning: using a non-integer number instead of an integer 
will result in an error in the future
  threshold = 0.5 * (sorted_input[ia + limiteinf]
/<>/nipy-0.4.0+git26-gf8d3149/debian/tmp/usr/lib/python2.7/dist-packages/nipy/labs/mask.py:239:
 VisibleDeprecationWarning: using a non-integer number instead of an integer 
will result in an error in the future
  + sorted_input[ia + limiteinf + 1])
/usr/lib/python2.7/dist-packages/numpy/lib/function_base.py:2569:
 RuntimeWarning: invalid value encountered in true_divide
  c /= stddev[:, None]
/usr/lib/python2.7/dist-packages/numpy/lib/function_base.py:2570: 
RuntimeWarning: invalid value encountered in true_divide
  c /= stddev[None, :]
/<>/nipy-0.4.0+git26-gf8d3149/debian/tmp/usr/lib/python2.7/dist-packages/nipy/modalities/fmri/tests/test_dmtx.py:407:
 FutureWarning: elementwise comparison failed; returning scalar instead, but in 
the future will perform elementwise comparison
  idx = paradigm.onset[paradigm.con_id == 0].astype(np.int)
/<>/nipy-0.4.0+git26-gf8d3149/debian/tmp/usr/lib/python2.7/dist-packages/nipy/modalities/fmri/tests/test_dmtx.py:407:
 VisibleDeprecationWarning: using a boolean instead of an integer will result 
in an error in the future
  idx = paradigm.onset[paradigm.con_id == 0].astype(np.int)
../<>/nipy-0.4.0+git26-gf8d3149/debian/tmp/usr/lib/python2.7/dist-packages/nipy/modalities/fmri/tests/test_dmtx.py:429:
 FutureWarning: elementwise comparison failed; returning scalar instead, but in 
the future will perform elementwise comparison
  idx = bp.onset[bp.con_id == 1].astype(np.int)
/<>/nipy-0.4.0+git26-gf8d3149/debian/tmp/usr/lib/python2.7/dist-packages/nipy/modalities/fmri/tests/test_dmtx.py:429:
 VisibleDeprecationWarning: using a boolean instead of an integer will result 
in an error in the future
  idx = bp.onset[bp.con_id == 1].astype(np.int)
/<>/nipy-0.4.0+git26-gf8d3149/debian/tmp/usr/lib/python2.7/dist-packages/nipy/modalities/fmri/glm.py:581:
 UserWarning: Contrast for session 1 is null
  warn('Contrast for session %d is null' % i)
S.../<>/nipy-0.4.0+git26-gf8d3149/debian/tmp/usr/lib/python2.7/dist-packages/nipy/modalities/fmri/tests/test_utils.py:212:
 VisibleDeprecationWarning: using a non-integer number instead of an integer 
will result in an error in the future
  z1s = np.zeros((np.round(1./dt)))
..
==
ERROR: nipy.io.tests.test_image_io.test_badfile
--
Traceback (most recent call last):
  File "/usr/lib/python2.7/dist-packages/nose/case.py", line 197, in runTest
self.test(*self.arg)
  File 
"/<>/nipy-0.4.0+git26-gf8d3149/debian/tmp/usr/lib/python2.7/dist-packages/nipy/io/tests/test_image_io.py",
 line 44, in test_badfile
assert_raises(ImageFileError, load_image, filename)
  File "/usr/lib/python2.7/dist-packages/numpy/testing/utils.py", line 1145, in 
assert_raises
return nose.tools.assert_raises(*args,**kwargs)
  File "/usr/lib/python2.7/unitte

Bug#836537: snd: FTBFS: snd-main.c:2162:24: error: macro "g_abort" passed 1 arguments, but takes just 0

[Chris Lamb]

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

Dear Maintainer,

snd fails to build from source in unstable/amd64:

  [..]

  make: [makefile-clean] Error 1 (ignored)
  rmdir --ignore-fail-on-non-empty debian/stamp-autotools
  rmdir: failed to remove 'debian/stamp-autotools': No such file or directory
  /usr/share/cdbs/1/class/autotools.mk:58: recipe for target 'makefile-clean' 
failed
  make: [makefile-clean] Error 1 (ignored)
  set -e;
  if test -e debian/autoreconf.before; then \
dh_autoreconf_clean ; \
  fi
  dh_clean 
  rm -f debian/stamp-autotools-files
  rm -f debian/copyright_newhints
  rm -f debian/cdbs-install-list debian/cdbs-package-list 
debian/stamp-copyright-check
  rm -rf "debian/upstream-cruft"
  rm -f debian/stamp-upstream-cruft
  rm -f snd.nox.1 snd.gtk-jack.1 snd.gtk-pulse.1
   debian/rules build
  CDBS WARNING:  copyright-check disabled - licensecheck is missing.
  test -x debian/rules
  mkdir -p "build"
  CDBS WARNING:DEB_COPYRIGHT_CHECK_IGNORE_REGEX is deprecated since 0.4.133
  mkdir -p debian/stamp-makefile-build debian/stamp-makefile-install
  mkdir -p debian/stamp-autotools
  
  Scanning upstream source for new/changed copyright notices...
  
  set -e; LC_ALL=C.UTF-8 licensecheck --check '.*' --recursive --copyright 
--deb-fmt --ignore 
'^(pix/.*\.png|debian/(changelog|copyright(|_hints|_newhints)))' --lines 0 * | 
/usr/lib/cdbs/licensecheck2dep5 > debian/copyright_newhints
  /bin/sh: 1: licensecheck: not found
  0 combinations of copyright and licensing found.
  No new copyright notices found - assuming no news is good news...
  touch debian/stamp-copyright-check
  touch debian/stamp-upstream-cruft
  set -e;   mv ./config.guess ./config.guess.cdbs-orig; cp --remove-destination 
/usr/share/misc/config.guess ./config.guess;
  set -e;   mv ./config.sub ./config.sub.cdbs-orig; cp --remove-destination 
/usr/share/misc/config.sub ./config.sub;
  dh_autoreconf 
  touch debian/stamp-autotools-files
  chmod a+x 
/home/lamby/temp/cdt.20160903204930.AgBYCHkK99.db.snd/snd-16.7/./configure
  mkdir -p build/gtk-jack
  cd build/gtk-jack && CFLAGS="-g -O2 
-fdebug-prefix-map=/home/lamby/temp/cdt.20160903204930.AgBYCHkK99.db.snd/snd-16.7=.
 -fstack-protector-strong -Wformat -Werror=format-security" CXXFLAGS="-g -O2 
-fdebug-prefix-map=/home/lamby/temp/cdt.20160903204930.AgBYCHkK99.db.snd/snd-16.7=.
 -fstack-protector-strong -Wformat -Werror=format-security" 
CPPFLAGS="-Wdate-time -D_FORTIFY_SOURCE=2 -DREPRODUCIBLE_BUILD=1" 
LDFLAGS="-Wl,-z,relro" 
/home/lamby/temp/cdt.20160903204930.AgBYCHkK99.db.snd/snd-16.7/./configure 
--build=x86_64-linux-gnu --prefix=/usr --includedir="\${prefix}/include" 
--mandir="\${prefix}/share/man" --infodir="\${prefix}/share/info" 
--sysconfdir=/etc --localstatedir=/var --libexecdir="\${prefix}/lib/snd" 
--disable-maintainer-mode --disable-dependency-tracking --disable-silent-rules 
--with-ladspa --with-gmp --prefix=/usr --with-gtk --with-alsa --with-jack
  configure: WARNING: unrecognized options: --disable-maintainer-mode, 
--disable-dependency-tracking, --disable-silent-rules
  checking build system type... x86_64-pc-linux-gnu
  checking host system type... x86_64-pc-linux-gnu
  checking for gcc... gcc
  checking whether the C compiler works... yes
  checking for C compiler default output file name... a.out
  checking for suffix of executables... 
  checking whether we are cross compiling... no
  checking for suffix of object files... o
  checking whether we are using the GNU C compiler... yes
  checking whether gcc accepts -g... yes
  checking for gcc option to accept ISO C89... none needed
  checking for a BSD-compatible install... /usr/bin/install -c
  checking how to run the C preprocessor... gcc -E
  checking for grep that handles long lines and -e... /bin/grep
  checking for egrep... /bin/grep -E
  checking for ANSI C header files... yes
  checking for sys/types.h... yes
  checking for sys/stat.h... yes
  checking for stdlib.h... yes
  checking for string.h... yes
  checking for memory.h... yes
  checking for strings.h... yes
  checking for inttypes.h... yes
  checking for stdint.h... yes
  checking for unistd.h... yes
  checking whether byte ordering is bigendian... no
  checking size of void *... 8
  checking for pkg-config... /usr/bin/pkg-config
  checking for fftw3... yes
  checking for gsl... yes
  checking for oggdec... no
  checking for oggenc... no
  checking for mpg123... no
  checking for mpg321... no
  checking for speexdec... no
  checking for speexenc... no
  checking for flac... no
  checking for timidity... no
  checking for wavpack... no
  checking for wvunpack... no
  checking for audio system... ALSA+JACK
  configure: creating ./config.status
  config.status: creating makefile
  config.status: creating mus-config.h
  configure: WARNING: unrecognized options: --d

Bug#836536: ruby-concurrent: FTBFS too much often (failed examples)

[Santiago Vila]

Package: src:ruby-concurrent
Version: 1.0.0-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 --buildsystem=ruby --with ruby
   dh_testdir -i -O--buildsystem=ruby
   dh_update_autotools_config -i -O--buildsystem=ruby
   dh_auto_configure -i -O--buildsystem=ruby
dh_ruby --configure
   dh_auto_build -i -O--buildsystem=ruby
dh_ruby --build
   dh_ruby --build
   dh_auto_test -i -O--buildsystem=ruby
dh_ruby --test
 fakeroot debian/rules binary-indep
dh binary-indep --buildsystem=ruby --with ruby

[... snipped ...]


 RuntimeError:
 # ./spec/concurrent/agent_spec.rb:954:in `block (4 levels) in 
'

  5) Concurrent::Agent waiting with #await_for! raises an error if restarted 
with :clear_actions true
 # the timing is nearly impossible
 Failure/Error:
 pending('the timing is nearly impossible'); fail
 subject = Agent.new(0, error_mode: :fail)
   
 subject.send_via(executor){ sleep(0.1) }
 subject.send_via(executor){ raise StandardError }
 subject.send_via(executor){ nil }
   
 t = Thread.new{ subject.restart(42, clear_actions: true) }
   
 expect {

 RuntimeError:
 # ./spec/concurrent/agent_spec.rb:1007:in `block (4 levels) in 
'

  6) Concurrent::Synchronization Concurrent::Synchronization::LockableObject 
signaling for now pending, tested pretty well by Event
 # Not yet implemented
 # ./spec/concurrent/synchronization_spec.rb:172

  7) Concurrent::LazyRegister 
 # Not yet implemented
 # ./spec/concurrent/lazy_register_spec.rb:4

Failures:

  1) Concurrent::Agent waiting the await job does not trigger the error mode
 Failure/Error: expect(subject.value).to eq 11

   expected: 11
got: 10

   (compared using ==)
 # ./spec/concurrent/agent_spec.rb:808:in `block (4 levels) in 
'

Finished in 1 minute 21.56 seconds (files took 0.626 seconds to load)
1255 examples, 1 failure, 7 pending

Failed examples:

rspec ./spec/concurrent/agent_spec.rb:803 # Concurrent::Agent waiting the await 
job does not trigger the error mode

Randomized with seed 28093

/usr/bin/ruby2.3 /usr/bin/rspec --pattern ./spec/concurrent/\*_spec.rb --format 
documentation failed
ERROR: Test "ruby2.3" failed. Exiting.
dh_auto_install: dh_ruby --install /<>/debian/ruby-concurrent 
returned exit code 1
debian/rules:6: recipe for target 'binary-indep' failed
make: *** [binary-indep] Error 1
dpkg-buildpackage: error: fakeroot debian/rules binary-indep gave error exit 
status 2


The failure does not seem related to using "dpkg-buildpackage -A".

It does not always fail, but it fails often enough to allow me to
attach 5 different failed build logs to this report.

The builds were made on KVM virtual machines using sbuild and an
up-to-date stretch chroot (plus diffutils 3.5 from unstable, but this
is not the reason it fails), with memory ranging from 768 MB (plus 1 GB
of swap) to 3 GB (plus 4 GB of swap).

BTW: I think the "Randomized with seed xxx" above is a bad idea.
Maintainers often ask bug reporters for "a way to reproduce the error".
But if the build is based on random variables, this becomes an
impossible task. Please consider modifying the build system so that
those random things are always the same.

Thanks.

ruby-concurrent_1.0.0-1_amd64-20160903T022630Z.gz
Description: application/gzip


ruby-concurrent_1.0.0-1_amd64-20160903T180334Z.gz
Description: application/gzip


ruby-concurrent_1.0.0-1_amd64-20160903T180617Z.gz
Description: application/gzip


ruby-concurrent_1.0.0-1_amd64-20160903T180806Z.gz
Description: application/gzip


ruby-concurrent_1.0.0-1_amd64-20160903T181046Z.gz
Description: application/gzip

Bug#830568: python-asyncssh: accesses the internet during build

[Chris Lamb]

Hi Vincent,
 
> The policy says "may not". I am not a native speaker, but for me, this
> is not like "must not". Since you are a native speaker, I think you know
> better: is it optional or not?

May I suggest an alternative approach…? We have two cases here:

 a) Debian Policy states it is a bug in python-asyncssh.

 b) Debian Policy does not state it is a bug python-asyncssh.

In both cases it would be perfectly legitimate to continue discussing
whether it *should* be a bug in python-asyncssh.

In other words, tedious haggling over the wording and intention of a
document neither of us wrote is unproductive to the goal of improving
Debian. So, let's just skip all of that.

> People which are really concerned about information leak during
> build should do the same.

I disagree, when we can easily enforce it for all of our users.
 
> Of course, another solution would be to use 127.0.0.1:discard which
> would be almost equivalent since the goal of the test seems to be
> broader than just DNS failures.

I recommend you disable the test for the "regular" Debian package build
and run as many privacy-leaking/slow/etc. tests using autopkgtest.


Regards,

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

Processed: Re: dimbl: FTBFS: include/dimbl/DimProcs.h:37:29: error: expected ')' before '&' token

[Debian Bug Tracking System]

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

> tags 833905 +fixed-upstream
Bug #833905 [src:dimbl] dimbl: FTBFS: include/dimbl/DimProcs.h:37:29: error: 
expected ')' before '&' token
Added tag(s) fixed-upstream.
> thanks
Stopping processing here.

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

Bug#833905: dimbl: FTBFS: include/dimbl/DimProcs.h:37:29: error: expected ')' before '&' token

[Adrian Bunk]

tags 833905 +fixed-upstream
thanks


On Wed, Aug 10, 2016 at 08:45:57AM +0100, Chris Lamb wrote:
>...
>   make[3]: Entering directory 
> '/home/lamby/temp/cdt.20160810084053.cX2EXg73ka.dimbl/dimbl-0.12/src'
>   g++ -DHAVE_CONFIG_H -I. -I..  -I../include -Wdate-time -D_FORTIFY_SOURCE=2  
> -g -O2 
> -fdebug-prefix-map=/home/lamby/temp/cdt.20160810084053.cX2EXg73ka.dimbl/dimbl-0.12=.
>  -fstack-protector-strong -Wformat -Werror=format-security -fopenmp 
> -I/usr/include/libxml2 -fopenmp -c -o Dimbl.o Dimbl.cxx
>   In file included from Dimbl.cxx:33:0:
>   ../include/dimbl/DimProcs.h:37:29: error: expected ')' before '&' token
>  settings( Timbl::TimblOpts& );
>^
>   ../include/dimbl/DimProcs.h:87:30: error: expected ')' before '&' token
> experiment( Timbl::TimblOpts& opts ): config( opts ){
> ^
>   Dimbl.cxx:136:34: error: expected '}' before end of line
>#pragma omp parallel private( i )
> ^
>   Dimbl.cxx:136:34: error: expected ';' before end of line
>   Dimbl.cxx:136:34: error: expected declaration before end of line
>   Makefile:307: recipe for target 'Dimbl.o' failed
>...

I have confirmed in a (non-packetized) build that this bug is fixed in 
upstream 0.15.

A maintainer upload of the latest upstream version should therefore be 
sufficient to fix this bug.

cu
Adrian

-- 

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

Bug#833780: undertaker: FTBFS with boost1.61

[Adrian Bunk]

On Mon, Aug 08, 2016 at 03:41:19PM +, Mattia Rizzolo wrote:
> source: undertaker
> version: 1.6.1-2
> severity: serious
> 
> Dear maintainer,
> 
> your package failed to build during the rebuilds for the boost1.61
> transition, using gcc-6 as a compiler.
> you can see the failed build logs at:
> https://buildd.debian.org/status/logs.php?pkg=undertaker&ver=1.6.1-2%2Bb1

The problematic line is
yyFlexLexer::yyFlexLexer( FLEX_STD istream* arg_yyin, FLEX_STD ostream* 
arg_yyout ):

Regenerating BoolExpLexer.cpp_shipped with flex 2.6.1 fixes the issue, 
likely due to the following change in flex:
Replaced FLEX_STD macro with std::.  The std:: construct exists as of 
C++98, so we can simply assume it
is supported.

Reinhard, can you confirm and upload a fixed package?

> regards,
> Mattia Rizzolo

cu
Adrian

-- 

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

Processed: severity of 834688 is normal, tagging 834688

[Debian Bug Tracking System]

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

> severity 834688 normal
Bug #834688 [java-package] java-package: Fails to create package for JDK 8u102
Severity set to 'normal' from 'grave'
> tags 834688 + moreinfo
Bug #834688 [java-package] java-package: Fails to create package for JDK 8u102
Added tag(s) moreinfo.
> thanks
Stopping processing here.

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

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

[Debian Bug Tracking System]

Your message dated Sat, 03 Sep 2016 18:21:54 +
with message-id 
and subject line Bug#831914: fixed in gui-apt-key 0.4-2.2
has caused the Debian Bug report #831914,
regarding gui-apt-key: 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.)


-- 
831914: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=831914
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: gui-apt-key
Version: 0.4-2.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):
>  fakeroot debian/rules binary-indep
> make: Nothing to be done for 'binary-indep'.
>  dpkg-genchanges --build=all >../gui-apt-key_0.4-2.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/gui-apt-key_0.4-2.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: gui-apt-key
Source-Version: 0.4-2.2

We believe that the bug you reported is fixed in the latest version of
gui-apt-key, 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 gui-apt-key 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 16:48:34 +0200
Source: gui-apt-key
Binary: gui-apt-key
Architecture: source all
Version: 0.4-2.2
Distribution: unstable
Urgency: medium
Maintainer: Martin Schulze 
Changed-By: Axel Beckert 
Description:
 gui-apt-key - Graphical Key Manager for APT
Closes: 831914 834465
Changes:
 gui-apt-key (0.4-2.2) unstable; urgency=medium
 .
   * Non-maintainer upload
   * Swap binary-* targets to fix FTBFS with "dpkg-buildpackage -A".
 (closes: #831914)
   * Fix empty owner with GnuPG 2.1 by also parsing "uid:" lines in
 output and assigning them to the right key. (closes: #834465)
Checksums-Sha1:
 6e77105e2540c3721b37f20ade3c0c5569cf401e 1617 gui-apt-key_0.4-2.2.dsc
 c923ccfad9fcd48dd27a660e69e5c8d2b01975e6 13106 gui-apt-key_0.4-2.2.diff.gz
 e1d3dd5ae887c856bbf677e15bc9488231d518fd 27622 gui-apt-key_0.4-2.2_all.deb
Checksums-Sha256:
 2ae228e519f43b5465ada55ffee6c6028b310e7f791819787cff606af8b3c6c7 1617 
gui-apt-key_0.4-2.2.dsc
 a046473a76ee4fd8f6e9f9de9aca8ed2a163fb41320b7a02848f7098b9bd875e 13106 
gui-apt-key_0.4-2.2.diff.gz
 3e1dc12cb25b31af08fc9249d78efbf069361b19fff1e7e4f09bc9b6c761 27622 
gui-apt-key_0.4-2.2_all.deb
Files:
 ed1e

Bug#831813: marked as done (nullmailer leaks sensitive data through debconf)

[Debian Bug Tracking System]

Your message dated Sat, 03 Sep 2016 18:17:11 +
with message-id 
and subject line Bug#831813: fixed in nullmailer 1:1.13-1+deb8u1
has caused the Debian Bug report #831813,
regarding nullmailer leaks sensitive data through debconf
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.)


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

The nullmailer package keeps sensitive information like users and passwords to
the mail accounts on the remote SMTP servers in the '/etc/nullmailer/remotes'
file, which is secured by 600 permissions and owned by mail:mail. However,
after running command:

  dpkg-reconfigure -f noninteractive nullmailer

contents of this file are stored in the debconf database as cleartext in the
'nullmailer/relayhost' database key and can be read by any user using the
command:

  debconf-get-selections | grep nullmailer

The 'dpkg-reconfigure' command cannot be executed directly by unprivileged
users. However, the debconf database reads the contents of the
'/etc/nullmailer/remotes' file and includes its contents in the database on
package installation.

This behaviour occurs again on package reinstallation - the debconf database
is automatically updated with the contents of the '/etc/nullmailer/remotes'
file. Therefore the sensitive information might show up in the
'debconf-get-selections' output after an automatic package upgrade or package
reinstallation.

Regards,
Maciej


pgpJKjlCZvMgN.pgp
Description: PGP signature
--- End Message ---
--- Begin Message ---
Source: nullmailer
Source-Version: 1:1.13-1+deb8u1

We believe that the bug you reported is fixed in the latest version of
nullmailer, 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.
Christian Hofstaedtler  (supplier of updated nullmailer 
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, 06 Aug 2016 17:36:35 +
Source: nullmailer
Binary: nullmailer
Architecture: source
Version: 1:1.13-1+deb8u1
Distribution: jessie
Urgency: medium
Maintainer: Nick Leverton 
Changed-By: Christian Hofstaedtler 
Description:
 nullmailer - simple relay-only mail transport agent
Closes: 831813
Changes:
 nullmailer (1:1.13-1+deb8u1) jessie; urgency=medium
 .
   * Non-maintainer upload.
   * Do not keep relayhost data in debconf database longer than
 strictly needed. (Closes: #831813)
 Backport of 1:1.13-1.2 from unstable.
Checksums-Sha1:
 57fdbd9bcebace7fc996a3b708e3fa1aa961b9d5 1818 nullmailer_1.13-1+deb8u1.dsc
 39e235edf71d9b5d08967c76dc884d8b04979e2a 30280 
nullmailer_1.13-1+deb8u1.debian.tar.xz
Checksums-Sha256:
 74bd217d6c9692234637994b9962a7a53ed10497edb89059ac47e8b9dd6db535 1818 
nullmailer_1.13-1+deb8u1.dsc
 4d66a9d5165fee044efe8dccb11851cb545d5ddfe98a579196845d61e9a7f6d4 30280 
nullmailer_1.13-1+deb8u1.debian.tar.xz
Files:
 8e70dfea43d021a277cd6813f9a38045 1818 mail extra nullmailer_1.13-1+deb8u1.dsc
 8ef8d48fc4dd60376e2eb76732a8353b 30280 mail extra 
nullmailer_1.13-1+deb8u1.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQItBAEBCAAXBQJXyDKGEBx6ZWhhQGRlYmlhbi5vcmcACgkQXBPW25MFLgN8rw//
VcIMCnmFEhcclqfvBN9LDWywCYKrjCzXIDA58d0GAv7pPE5dPXQshzRMUVBKHOZ/
17ERND4glZM4JJ+NO3ZOK04m+73LTp+yKPHZsOmNbPM/z9CTwZeHd4/ejd0HArp6
6ysfQKCvy8r64FwFLt/Jhm/HcXI+EDYnJl9J9E6QlOXprw7xfjCBcmrU1+c4+fDy
hhe7zYlnywN7MZmQ8yjYVFwW9DJo8p86mLoZznPRokbCSqzDE7RTvKU9AfV9avK2
QdOA4SLG8wOe/Tztdr0b1sQCL/BnxDl07KyYI6IKr2kIlWVUXxcGOaGeX9lA70a9
8A7HlHKMfoGt8dn7bFom347CgYUqgyDZ/Q8LcP6tLavMb7mgRGNC5nkqhD+Q/Fry
1P/vGqWFn9fR6i0+gHwUrI87cIu0c18wVTSG4bQDjqRA0eva6GKL01IP+Cn9ykS9
0KjkMEGqfvg0420OeUGNBJtzOLpvX1HSz9gCmz48ZjLvP4oUyc92sADNWmo2WuAK
wJjmvL9o39fEV/R8/Lr77ITT7wEmaxJo1JslOQiyTEVS2Ion26gHIv5i2zir2lOO
39YX6yrm5cd84L5w0y3AsQMMzKYWqpSuoY8TCbrVgQ0OwFenh/b3k5wFjUBSSwiE
cyWkmQlggY9DbET3JIaHWBeH1MHmwGP8Y/1FssY4Dx8=
=GzEL
-END PGP SIGNATURE End Message ---

Bug#827411: marked as done (piuparts: FTBFS on jessie: 'wheezy' != 'squeeze')

[Debian Bug Tracking System]

Your message dated Sat, 03 Sep 2016 18:17:12 +
with message-id 
and subject line Bug#827411: fixed in piuparts 0.62+deb8u1
has caused the Debian Bug report #827411,
regarding piuparts: FTBFS on jessie: 'wheezy' != 'squeeze'
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.)


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

This package fails to build on a clean jessie sbuild chroot:

==
FAIL: testConfStdDistroNames (test_config.ConfStdDistroTests)
--
Traceback (most recent call last):
  File "/<>/tests/test_config.py", line 20, in 
testConfStdDistroNames
self.assertEqual(self.oldstable, 'squeeze')
AssertionError: 'wheezy' != 'squeeze'

--
Ran 39 tests in 0.536s

FAILED (failures=1)

The complete log is at

http://perl.debian.net/rebuild-logs/jessie/piuparts_0.62/piuparts_0.62_amd64-20160615-1509.build

Cheers,
Dominic.
--- End Message ---
--- Begin Message ---
Source: piuparts
Source-Version: 0.62+deb8u1

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

Debian distribution maintenance software
pp.
Holger Levsen  (supplier of updated piuparts 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: Fri, 02 Sep 2016 20:23:20 +0200
Source: piuparts
Binary: piuparts piuparts-master piuparts-slave piuparts-common
Architecture: source all
Version: 0.62+deb8u1
Distribution: stable
Urgency: medium
Maintainer: piuparts developers team 
Changed-By: Holger Levsen 
Description:
 piuparts   - .deb package installation, upgrading, and removal testing tool
 piuparts-common - common piuparts components
 piuparts-master - piuparts master components
 piuparts-slave - piuparts slave components
Closes: 827411
Changes:
 piuparts (0.62+deb8u1) stable; urgency=medium
 .
   [ Stefano Rivera ]
   * Don't test the current Debian release status, tracking that is
 distro-info-data's problem. (Closes: #827411)
Checksums-Sha1:
 a5204bd0fda932ed40b160ecb189ac6e216cf29f 1973 piuparts_0.62+deb8u1.dsc
 60f919db033de33d61bea556259e68241cf67758 221933 piuparts_0.62+deb8u1.tar.gz
 4f9f35a5051d6af1cdb30ae0c1a0165fde52af92 94616 piuparts_0.62+deb8u1_all.deb
 3f7bc52b4430458fed455cca9515b834303a6e7d 117056 
piuparts-master_0.62+deb8u1_all.deb
 429b588afc6eaa053faba0857e6927ad9214e6e8 50078 
piuparts-slave_0.62+deb8u1_all.deb
 d1910b19fcaf147981063ba0aa3760212525c1c3 53032 
piuparts-common_0.62+deb8u1_all.deb
Checksums-Sha256:
 04962b5532cf825cc4357ec1d075cf3178cde58fc9080968f50d3580306fcca2 1973 
piuparts_0.62+deb8u1.dsc
 6b39d12698c2f8259779b939a313018f3fe422831adeeb74972c04ce528d4e3c 221933 
piuparts_0.62+deb8u1.tar.gz
 cc894abec5bca19dd3d3fe026dc6ce28f02f40b45d6d74332ad7a4d9f9ca5737 94616 
piuparts_0.62+deb8u1_all.deb
 1fc42fe9269110e1bbe8563631daa176f7054217fbf2a18fb2c979308d7ae61e 117056 
piuparts-master_0.62+deb8u1_all.deb
 47246d9030249257663422a27cde5d4b73ba7ad4d9ae8606585bcafee833798d 50078 
piuparts-slave_0.62+deb8u1_all.deb
 5778568651321de70f09fea5bb46e5b19a082d1bced6931b2e61c2bfba8bca70 53032 
piuparts-common_0.62+deb8u1_all.deb
Files:
 69a3cb948e3ecd2608f412e605c53695 1973 devel extra piuparts_0.62+deb8u1.dsc
 a4b8a7eb751e746bd9f31294f004daa2 221933 devel extra piuparts_0.62+deb8u1.tar.gz
 29a83a952ea35c8e3b80a2c23f873392 94616 devel extra piuparts_0.62+deb8u1_all.deb
 c0c55b6d2558713659de457202900f42 117056 devel extra 
piuparts-master_0.62+deb8u1_all.deb
 3dd0a85a72e763c9acf5451f2b08fcc3 50078 devel extra 
piuparts-slave_0.62+deb8u1_all.deb
 8e263c4c11f1b21806f2c079e5e1fff8 53032 devel extra 
piuparts-common_0.62+deb8u1_all.deb

-BEGIN PGP SIGNATURE-
Version: GnuPG v1

iQIVAwUBV8q+bgkauFYGmqocAQo+HA//YtwHsurkYGUdvannsgHcVWW6gbyPG/MM
CA2rCSebl8MAc8pZbn9BeG7fRljMsJ0czF2noZAhBm3yUC+k6K9sZFLF9

Bug#835536: closed by Dominic Hargreaves (Bug#835536: fixed in request-tracker4 4.2.13-1)

[Niko Tyni]

Control: found -1 4.2.13-1

>  request-tracker4 (4.2.13-1) unstable; urgency=medium
>* Fix FTBFS with gpg 2.1 by no longer explicitly configuring the
>  path to gpg (Closes: #835536)

This doesn't seem to have worked: 4.2.13-1 failed on the 'all' buildd
with lots of

 # Tests were run but no plan was declared and done_testing() was not seen.
 t/mail/gnupg-bad.t . skipped: gpg 
executable is required.

Maybe it's just missing a build dependency on gnupg?
-- 
Niko Tyni   nt...@debian.org

Processed: Re: Bug#835536 closed by Dominic Hargreaves (Bug#835536: fixed in request-tracker4 4.2.13-1)

[Debian Bug Tracking System]

Processing control commands:

> found -1 4.2.13-1
Bug #835536 {Done: Dominic Hargreaves } [src:request-tracker4] 
request-tracker4: FTBFS with gnupg 2.1
The source 'request-tracker4' and version '4.2.13-1' do not appear to match any 
binary packages
Marked as found in versions request-tracker4/4.2.13-1; no longer marked as 
fixed in versions request-tracker4/4.2.13-1 and reopened.

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

Processed: fixed 836377 in 0.10.2

[Debian Bug Tracking System]

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

> fixed 836377 0.10.2
Bug #836377 {Done: Ben Finney } [dput] build system 
terminal locale not inherited by build programs
Marked as fixed in versions dput/0.10.2.
> thanks
Stopping processing here.

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

Bug#833727: emacs24: FTBFS with glibc 2.24

[Aurelien Jarno]

On 2016-09-03 11:07, Rob Browning wrote:
> Aurelien Jarno  writes:
> 
> > glibc 2.24 is now in unstable, so I am upgrading the severity of this
> > bug to serious. If you don't have time to fix this bug, I can do a
> > non-maintainer upload with the patch which is in the bug log.
> 
> I've been working on a release, and I think I should have time to finish
> it by Tuesday, but if not, you're welcome to go ahead.

Ok, great if you are working on a release. I am not on a hurry
personally, the package in the archive still works perfectly, the
problem is just when trying to rebuild it. Given I am the "one" who
broke that, I felt that I have to offer help.

Aurelien

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


signature.asc
Description: PGP signature

Bug#831399: marked as done (FTBFS on armel and i386: Test values out of range for platform time_t on various architectures)

[Debian Bug Tracking System]

Your message dated Sat, 03 Sep 2016 16:32:11 +
with message-id 
and subject line Bug#831399: fixed in python-pyotp 2.1.1-2
has caused the Debian Bug report #831399,
regarding FTBFS on armel and i386: Test values out of range for platform time_t 
on various architectures
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.)


-- 
831399: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=831399
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: python-pyotp
Version: 2.1.1-1
Severity: important
Forwarded: https://github.com/pyotp/pyotp/issues/30

Hi,

The testsuite always fails on 32-bits/ARM architectures because of out
of range test values. This makes the package FTBFS on i386, amrhf, armel
and maybe others.

A way to solve this would be to remove the three invalid test values from 
test.py.

Regards,
 Hugo (hle)

-- 
 Hugo Lefeuvre (hle)|www.owl.eu.com
4096/ ACB7 B67F 197F 9B32 1533 431C AC90 AC3E C524 065E


signature.asc
Description: PGP signature
--- End Message ---
--- Begin Message ---
Source: python-pyotp
Source-Version: 2.1.1-2

We believe that the bug you reported is fixed in the latest version of
python-pyotp, 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.
Hugo Lefeuvre  (supplier of updated python-pyotp 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: Fri, 15 Jul 2016 16:45:17 +0200
Source: python-pyotp
Binary: python-pyotp python3-pyotp
Architecture: source all
Version: 2.1.1-2
Distribution: unstable
Urgency: high
Maintainer: Hugo Lefeuvre 
Changed-By: Hugo Lefeuvre 
Description:
 python-pyotp - Python One Time Password Library (Python 2)
 python3-pyotp - Python One Time Password Library (Python 3)
Closes: 831399
Changes:
 python-pyotp (2.1.1-2) unstable; urgency=high
 .
   * Fix FTBFS on 32-bit platforms (Closes: #831399).
   * debian/control:
 - Add Python version informations in the short descriptions.
Checksums-Sha1:
 0fdb037e7f30c7bd73da026d6f14ac88c0b7e01a 2048 python-pyotp_2.1.1-2.dsc
 52cd4bb5aa698eab162aaf3fa1566a667e612fb7 2956 
python-pyotp_2.1.1-2.debian.tar.xz
 d0bacf514d06befa866dcaa51c89cdc78af7783a 9848 python-pyotp_2.1.1-2_all.deb
 7486af2aa5fe9d93bf38baeb11ab5aaa1e873105 9920 python3-pyotp_2.1.1-2_all.deb
Checksums-Sha256:
 307b0a1c2fc4ce13e954ec7951dbe4f6f48f51a84a4207a98dfbf9e16636e20f 2048 
python-pyotp_2.1.1-2.dsc
 ab1ad77139a758052c64c159c7699582408dbb3a5ce49ae5c5fbbdc991bc5bc4 2956 
python-pyotp_2.1.1-2.debian.tar.xz
 ec437ba9f753ea3fe686bb15e369f93e59f332a94f3a54119177696947f54662 9848 
python-pyotp_2.1.1-2_all.deb
 dad469009b0435ba6728bbf7a8ae8f7ac004bf1b8e2a4bebc2627f9e57b0bd03 9920 
python3-pyotp_2.1.1-2_all.deb
Files:
 2938459ff539097056b66f7ad9a46495 2048 python optional python-pyotp_2.1.1-2.dsc
 0dfc5aa484f5cb1f3ab6475eeb8d3f61 2956 python optional 
python-pyotp_2.1.1-2.debian.tar.xz
 4601cda6932967b6525869726e102e3b 9848 python optional 
python-pyotp_2.1.1-2_all.deb
 7c4fc3d24331c3eb8a0a5d77b187fd84 9920 python optional 
python3-pyotp_2.1.1-2_all.deb

-BEGIN PGP SIGNATURE-
Version: GnuPG v1

iQIcBAEBCgAGBQJXytg8AAoJEKyQrD7FJAZeV/cQAKKOYK2jq3/SmIN0uiL88hqb
B0Q/CRvKxstC2kc2Krh9+Q2iA9463Gw/SUT+5r3j6NXdnS2X72WVD7Jkf0kKvt0n
1v2cYxmdP6MZ8hB086vLTiAMHHWsWH04TImlugIg5lg6FVQ6ZZl0kr5zctmkV0w2
AenkVaTB/QiXoxyJMDApaRthORo6U+voz8o1HU+lY1TNIXZ+2YIez0WY6N9Obo0a
W9h9CFA+YTmoHDnWlloMwKgkFIMwEtnJ2sHk8c9rwPFNAyUwPtTXjghJ3GofFMxj
s3Uso5B+9DuIFPucW0PMlcwgkydKSycoetHNPVgNtTlGFsXfKWOdtHaS7Sc/5T4c
bIbOaa9+a4szO8Wz1BkUKuhhTDym4Szcb99M1eqX0hLcPL1KWGFCkRrTpJ+Z3c+E
llkJIIC4QWCz+LMmPmvqc63rVdoWudelUccMvrtEwzAwGIezauUltSMvvV8fMl93
vN/ZuJ1yk+jbe8zTNO2KQ52EFe259JSbomU6CDS00PyKzFiCl40L8SLqtMKbVs/u
xIzcdQmugX2TQoTgq1+bPOk9vnSr7BDVLS8uxaQMwTf5fP38Vt6mtp5Lg9f7rq3m
9m1m4FE6KVxa66NDyw39PS/7INMSuHiKWJKqw5J4L3kIMFL+Tr3dc7ppHGuxm+v8
Os64Q105wG4KQWwQFWaA
=aM9x
-END PGP SIGNATURE End Message ---

Bug#835894: marked as done (missing dependency on gnustep-back)

[Debian Bug Tracking System]

Your message dated Sat, 03 Sep 2016 16:26:57 +
with message-id 
and subject line Bug#835894: fixed in gnustep-gui 0.25.0-4
has caused the Debian Bug report #835894,
regarding missing dependency on gnustep-back
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.)


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

Hi!
I'm afraid terminal.app crashes at startup in unstable; this doesn't seem to
be related to my particular setup as the same happens on three different
machines (amd64, i386, armhf) with varied environments.

2016-08-29 05:12:57.421 Terminal[21768:21768] Did not find correct version
⤷of backend (libgnustep-back-025.bundle), falling back to std
⤷(libgnustep-back.bundle).
2016-08-29 05:12:57.425 Terminal[21768:21768] NSApplication.m:304  Assertion
⤷failed in initialize_gnustep_backend.  Unable to find backend back
Terminal: Uncaught exception NSInternalInconsistencyException, reason:
⤷NSApplication.m:304  Assertion failed in initialize_gnustep_backend.  Unable
⤷to find backend back



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

Kernel: Linux 4.7.2-xfsreflink+ (SMP w/6 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 terminal.app depends on:
ii  libc62.23-5
ii  libgnustep-base1.24  1.24.9-3
ii  libgnustep-gui0.25   0.25.0-3
ii  libobjc4 6.2.0-1

terminal.app recommends no packages.

terminal.app suggests no packages.

-- no debconf information
--- End Message ---
--- Begin Message ---
Source: gnustep-gui
Source-Version: 0.25.0-4

We believe that the bug you reported is fixed in the latest version of
gnustep-gui, 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.
Eric Heintzmann  (supplier of updated gnustep-gui 
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: Fri, 02 Sep 2016 19:42:42 +0200
Source: gnustep-gui
Binary: gnustep-gui-common gnustep-gui-runtime libgnustep-gui0.25 
libgnustep-gui-dev libgnustep-gui0.25-dbg gnustep-gui-doc
Architecture: source
Version: 0.25.0-4
Distribution: unstable
Urgency: medium
Maintainer: Debian GNUstep maintainers 

Changed-By: Eric Heintzmann 
Description:
 gnustep-gui-common - GNUstep GUI Library - common files
 gnustep-gui-doc - Documentation for the GNUstep GUI Library
 gnustep-gui-runtime - GNUstep GUI Library - runtime files
 libgnustep-gui-dev - GNUstep GUI header files and static libraries
 libgnustep-gui0.25 - GNUstep GUI Library
 libgnustep-gui0.25-dbg - GNUstep GUI Library - debugging symbols
Closes: 835894
Changes:
 gnustep-gui (0.25.0-4) unstable; urgency=medium
 .
   * Delete debian/libgnustep-gui0.25.symbols file (Closes: #835894).
   * Override lintian warning about symbols control file.
Checksums-Sha1:
 7330ce8bfe4c393b960f12eaa365ae7565c2a479 2648 gnustep-gui_0.25.0-4.dsc
 98bfaa3aa9c5c14ecb7d338da1548bbe2743291e 102048 
gnustep-gui_0.25.0-4.debian.tar.xz
Checksums-Sha256:
 82ba0b3d3fee4c541619b7a234be4263b676bb67d242da2e59cb03c702b6b104 2648 
gnustep-gui_0.25.0-4.dsc
 b6520a4f826362eb595b682397619a89fb261173e20df54a37071fd7bc2a9c57 102048 
gnustep-gui_0.25.0-4.debian.tar.xz
Files:
 db3d3f85c47f79d96daa1bb33a485d50 2648 gnustep optional gnustep-gui_0.25.0-4.dsc
 12db8b1e207bca61ff2bd17b47292884 102048 gnustep optional 
gnustep-gui_0.25.0-4.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQIcBAEBCgAGBQJXytjcAAoJEEsEP825REVA8QEP/RZGLrSV8GCNYi6Cc0+oovCl
vWE3chpGcWPGF3Ukz0br3qFiDi15VkvAmOty8pwM1rVBR0p8an1AO1O3vZui06SI
l7OXae88YkJh1wcIJgYqC53K4oCuHO66ZxzZFAihTkYx2UIJC24lYASPYyXaO0vS
5n9wFtCK5grclh4zL5WCUQdN/mrkZP5BeGBrmlj8ALAEFsM/ketEpY3PDSyKNvQ2
DuFyNf/8tyiPKP6kPEHrX5JaiF+nsoyBTz6LMz+kCmeTt6b06tWj7rO80FTp4pW

Bug#833727: emacs24: FTBFS with glibc 2.24

[Rob Browning]

Aurelien Jarno  writes:

> glibc 2.24 is now in unstable, so I am upgrading the severity of this
> bug to serious. If you don't have time to fix this bug, I can do a
> non-maintainer upload with the patch which is in the bug log.

I've been working on a release, and I think I should have time to finish
it by Tuesday, but if not, you're welcome to go ahead.

Thanks for the help
-- 
Rob Browning
rlb @defaultvalue.org and @debian.org
GPG as of 2011-07-10 E6A9 DA3C C9FD 1FF8 C676 D2C4 C0F0 39E9 ED1B 597A
GPG as of 2002-11-03 14DD 432F AE39 534D B592 F9A0 25C8 D377 8C7E 73A4

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

[Christoph Anton Mitterer]

Hey.

Not really sure whether these changes here makes things so much better:

1) It's still al just Wants, no Requires... i.e. if netfilter rules
loading fails for whichever reason, the boot process will continue just
normally, with networking and any daemons, that possibly require
netfilter for their security, being brought up.


2) Some daemons might actually improperly start even before
network.target or network-pre.target... while this is certainly bad, it
likely happens in the realworld... so a dependency (or at least a
Wants) on something much earlier would be useful... e.g.
sysinit.target, which I use for that.


3) I don't quite understand the benefit of:
Conflicts=shutdown.target
Before=shutdown.target
Doesn't this actually open a possible window int which daemons may
still run but netfilter-persistent is going to be stopped and thus
rules might be removed?


Chris.

smime.p7s
Description: S/MIME cryptographic signature

Bug#830088: Could not find 'em-socksify' (>= 0.3)

[Sebastien Badia]

tags 830088 + pending
tags 830099 + pending
owner 830099 !
owner 830088 !
thanks

Hi,

Back in the game! \o/
Thanks for this bugreport, I take a look on this one.

Cheers,


signature.asc
Description: PGP signature

Processed: Re: Could not find 'em-socksify' (>= 0.3)

[Debian Bug Tracking System]

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

> tags 830088 + pending
Bug #830088 [ruby-em-socksify] Could not find 'em-socksify' (>= 0.3)
Added tag(s) pending.
> tags 830099 + pending
Bug #830099 [ruby-em-http-request] Could not find 'em-socksify' (>= 0.3)
Added tag(s) pending.
> owner 830099 !
Bug #830099 [ruby-em-http-request] Could not find 'em-socksify' (>= 0.3)
Owner recorded as Sebastien Badia .
> owner 830088 !
Bug #830088 [ruby-em-socksify] Could not find 'em-socksify' (>= 0.3)
Owner recorded as Sebastien Badia .
> thanks
Stopping processing here.

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

Bug#828927: marked as done (strigi: FTBFS with gcc-6 and glibc 2.23)

[Debian Bug Tracking System]

Your message dated Sat, 03 Sep 2016 15:36:16 +
with message-id 
and subject line Bug#835236: Removed package(s) from unstable
has caused the Debian Bug report #828927,
regarding strigi: FTBFS with gcc-6 and glibc 2.23
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.)


-- 
828927: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=828927
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: strigi
Version: 0.7.8-2.1
Severity: important

>From my pbuilder build log, using a chroot preferring gcc-defaults and
glibc from experimental:

...
/build/strigi-0.7.8/libstreamanalyzer/plugins/indexers/clucenengindexer/cluceneindexreader.cpp:
In static member function 'static void
CLuceneIndexReader::Private::addField(lucene::document::Field*,
Strigi::IndexedDocument&)':
/build/strigi-0.7.8/libstreamanalyzer/plugins/indexers/clucenengindexer/cluceneindexreader.cpp:325:37:
error: no matching function for call to
'make_pair(std::__cxx11::string, std::__cxx11::string&)'
 wchartoutf8(name), value));
 ^
In file included from /usr/include/c++/6/bits/stl_algobase.h:64:0,
 from /usr/include/c++/6/bits/stl_tree.h:63,
 from /usr/include/c++/6/map:60,
 from
/build/strigi-0.7.8/libstreamanalyzer/include/strigi/indexeddocument.h:23,
 from
/build/strigi-0.7.8/libstreamanalyzer/include/strigi/indexreader.h:24,
 from
/build/strigi-0.7.8/libstreamanalyzer/plugins/indexers/clucenengindexer/cluceneindexreader.h:24,
 from
/build/strigi-0.7.8/libstreamanalyzer/plugins/indexers/clucenengindexer/cluceneindexreader.cpp:21:
/usr/include/c++/6/bits/stl_pair.h:425:5: note: candidate:
template constexpr std::pair::__type, typename
std::__decay_and_strip<_T2>::__type> std::make_pair(_T1&&, _T2&&)
 make_pair(_T1&& __x, _T2&& __y)
 ^
/usr/include/c++/6/bits/stl_pair.h:425:5: note:   template argument
deduction/substitution failed:
/build/strigi-0.7.8/libstreamanalyzer/plugins/indexers/clucenengindexer/cluceneindexreader.cpp:325:37:
note:   cannot convert 'value' (type 'std::__cxx11::string {aka
std::__cxx11::basic_string}') to type
'std::__cxx11::basic_string&&'
 wchartoutf8(name), value));
 ^
...
make[3]: Leaving directory '/build/strigi-0.7.8/obj-x86_64-linux-gnu'
[ 85%] Built target perfieldxml
make[2]: Leaving directory '/build/strigi-0.7.8/obj-x86_64-linux-gnu'
Makefile:141: recipe for target 'all' failed
make[1]: *** [all] Error 2
make[1]: Leaving directory '/build/strigi-0.7.8/obj-x86_64-linux-gnu'
dh_auto_build: make -j8 returned exit code 2
debian/rules:15: recipe for target 'build' failed
make: *** [build] Error 2
dpkg-buildpackage: error: debian/rules build gave error exit status 2
-- 
Daniel Schepler
--- End Message ---
--- Begin Message ---
Version: 0.7.8-2.2+rm

Dear submitter,

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

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

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

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

Debian distribution maintenance software
pp.
Chris Lamb (the ftpmaster behind the curtain)--- End Message ---

Bug#724520: marked as done (gnupg-doc ftbfs in unstable)

[Debian Bug Tracking System]

Your message dated Sat, 03 Sep 2016 15:35:40 +
with message-id 
and subject line Bug#836085: Removed package(s) from unstable
has caused the Debian Bug report #724520,
regarding gnupg-doc ftbfs 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.)


-- 
724520: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=724520
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: gnupg-doc
Version: 2003.04.06+dak1-1
Severity: serious
Tags: jessie sid

## mini-howto
for format in html txt ps; do \
  for lang in $(find mini_howto -name \*.sgml); do \
make -C $(dirname $lang) $(echo $(basename $lang) | sed -e
"s/\.sgml/.$format/") >> build.log 2>&1; \
  done; \
done
make: *** [build] Error 2

build.log ends with:

make[1]: Entering directory
`/scratch/packages/tmp/gnupg-doc-2003.04.06+dak1/mini_howto/de'
sgml2latex --language=de --charset=latin --output=ps GPGMiniHowto.sgml
Processing file GPGMiniHowto.sgml
nsgmls:0:26:10:E: end tag for element "ABSTRACT" which is not open
nsgmls:0:28:4:E: document type does not allow element "TOC" here
fmt_latex2e::postASP: LaTeX first run problem. Aborting ...
make[1]: *** [GPGMiniHowto.ps] Error 1
make[1]: Leaving directory
`/scratch/packages/tmp/gnupg-doc-2003.04.06+dak1/mini_howto/de'
--- End Message ---
--- Begin Message ---
Version: 2003.04.06+dak1-1+rm

Dear submitter,

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

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

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

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

Debian distribution maintenance software
pp.
Chris Lamb (the ftpmaster behind the curtain)--- End Message ---

Bug#818124: marked as done (easymp3gain: FTBFS: Could not check LCL version)

[Debian Bug Tracking System]

Your message dated Sat, 03 Sep 2016 15:35:18 +
with message-id 
and subject line Bug#836161: Removed package(s) from unstable
has caused the Debian Bug report #818124,
regarding easymp3gain: FTBFS: Could not check LCL version
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.)


-- 
818124: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=818124
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:easymp3gain
Version: 0.5.0+svn135-6
Severity: serious

Dear maintainer:

This package currently fails to build from source in stretch:


-- Check for Lazbuild: /usr/bin/lazbuild
CMake Error at data/cmake/FindLazbuild.cmake:36 (message):
  Could not check LCL version (Lazbuild found?)
  Call Stack (most recent call first):
src/CMakeLists.txt:3 (find_package)


-- Configuring incomplete, errors occurred!
See also 
"/<>/easymp3gain-0.5.0+svn135/build/CMakeFiles/CMakeOutput.log".
debian/rules:21: recipe for target 'override_dh_auto_configure' failed
make[1]: *** [override_dh_auto_configure] Error 1
make[1]: Leaving directory '/<>/easymp3gain-0.5.0+svn135'
debian/rules:18: recipe for target 'build-arch' failed
make: *** [build-arch] Error 2
dpkg-buildpackage: error: debian/rules build-arch gave error exit status 2


The full build log is attached.

Thanks.

easymp3gain_0.5.0+svn135-6_amd64-20160313-2250.gz
Description: application/gzip
--- End Message ---
--- Begin Message ---
Version: 0.5.0+svn135-6+rm

Dear submitter,

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

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

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

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

Debian distribution maintenance software
pp.
Chris Lamb (the ftpmaster behind the curtain)--- End Message ---

Bug#832300: marked as done (pyoperators: Non-deterministically FTBFS to unreliable timing in tests)

[Debian Bug Tracking System]

Your message dated Sat, 03 Sep 2016 15:35:03 +
with message-id 
and subject line Bug#836178: Removed package(s) from unstable
has caused the Debian Bug report #832300,
regarding pyoperators: Non-deterministically FTBFS to unreliable timing in tests
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.)


-- 
832300: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=832300
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: pyoperators
Version: 0.13.13-1
Severity: serious
X-Debbugs-Cc: reproducible-bui...@lists.alioth.debian.org

Hi,
pyoperator's testsuite appears to use method timing/benchmarking
in such a way that it will non-deterministically FTBFS:

==
FAIL: test.test_utils.test_timer1
--
Traceback (most recent call last):
  File "/usr/lib/python2.7/dist-packages/nose/case.py", line 197, in runTest
self.test(*self.arg)
  File 
"/build/pyoperators-0.13.13/.pybuild/pythonX.Y_2.7/build/test/test_utils.py", 
line 560, in test_timer1
assert abs(delta1 - 0.01) < 0.001
AssertionError


Regards,

-- 
  ,''`.
 : :'  : Chris Lamb
 `. `'`  la...@debian.org / chris-lamb.co.uk
   `-
--- End Message ---
--- Begin Message ---
Version: 0.13.13-1+rm

Dear submitter,

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

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

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

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

Debian distribution maintenance software
pp.
Chris Lamb (the ftpmaster behind the curtain)--- End Message ---

Bug#830568: python-asyncssh: accesses the internet during build

[Vincent Bernat]

 ❦  3 septembre 2016 15:46 CEST, Chris Lamb  :

>> Was this MBF discussed somewhere?
>
> I don't consider it to be a MBF — I haven't been systematically working
> my way through the archive and I've really only filed a handful of bugs;
> mostly quasi-duplicates due to Sphinx stuff (which is arguably more a
> QA thing than to do with violation of any policy).

Well, that's a lot of bugs, so it should have been discussed. But
whatever, I was just asking to not repeat something already discussed.

The policy says "may not". I am not a native speaker, but for me, this
is not like "must not". Since you are a native speaker, I think you know
better: is it optional or not?

While I understand why the policy says no network access, in the case of
python-asyncssh, the network access is to access a non-existing host
From a DNS point of view. It's something that would be far more complex
to setup a DNS in the chroot and LD_PRELOAD something to ensure it is
used in place of the regular resolver part. Not running the test would
just reduce the test coverage. If upstream wrote this test, I suppose it
is useful. If we run tests as part of our build, I suppose this is also
useful. And there is no positive side. Nowadays, we have little risk to
have a package that access the network in a meaningful way during the
build: both pbuilder and sbuild are running in a separate network
namespace and I believe many official builders also have restricted
access. People which are really concerned about information leak during
build should do the same.

Of course, another solution would be to use 127.0.0.1:discard which
would be almost equivalent since the goal of the test seems to be
broader than just DNS failures.

What do you think?
-- 
Use uniform input formats.
- The Elements of Programming Style (Kernighan & Plauger)


signature.asc
Description: PGP signature

Bug#836510: quilt: FTBFS in testing (failing tests)

[Santiago Vila]

Package: src:quilt
Version: 0.63-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
   dh_testdir -i
   dh_update_autotools_config -i
   debian/rules override_dh_auto_configure
make[1]: Entering directory '/<>'
dh_auto_configure -- --with-docdir=/usr/share/doc/quilt 
--with-sendmail=/usr/sbin/sendmail --with-awk=/usr/bin/awk
./configure --build=x86_64-linux-gnu --prefix=/usr 
--includedir=\${prefix}/include --mandir=\${prefix}/share/man 
--infodir=\${prefix}/share/info --sysconfdir=/etc --localstatedir=/var 
--disable-silent-rules --libdir=\${prefix}/lib/x86_64-linux-gnu 
--libexecdir=\${prefix}/lib/x86_64-linux-gnu --disable-maintainer-mode 
--disable-dependency-tracking --with-docdir=/usr/share/doc/quilt 
--with-sendmail=/usr/sbin/sendmail --with-awk=/usr/bin/awk
configure: WARNING: unrecognized options: --disable-silent-rules, 
--disable-maintainer-mode, --disable-dependency-tracking, --with-docdir
checking for a BSD-compatible install... /usr/bin/install -c
checking whether #! works in shell scripts... yes
checking for bash... /bin/bash
checking whether /bin/bash quoting works... yes

[... snipped ...]

Unescaped left brace in regex is deprecated, passed through in regex; marked by 
<-- HERE in m/%{ <-- HERE \?}/ at ./run line 290.
[create-delete.test]
19 commands (19 passed, 0 failed)
Unescaped left brace in regex is deprecated, passed through in regex; marked by 
<-- HERE in m/%{ <-- HERE (\w+)}/ at ./run line 114.
Unescaped left brace in regex is deprecated, passed through in regex; marked by 
<-- HERE in m/%{ <-- HERE \?}/ at ./run line 290.
[annotate.test]
31 commands (31 passed, 0 failed)
Unescaped left brace in regex is deprecated, passed through in regex; marked by 
<-- HERE in m/%{ <-- HERE (\w+)}/ at ./run line 114.
Unescaped left brace in regex is deprecated, passed through in regex; marked by 
<-- HERE in m/%{ <-- HERE \?}/ at ./run line 290.
[no-file-to-patch.test]
5 commands (5 passed, 0 failed)
Unescaped left brace in regex is deprecated, passed through in regex; marked by 
<-- HERE in m/%{ <-- HERE (\w+)}/ at ./run line 114.
Unescaped left brace in regex is deprecated, passed through in regex; marked by 
<-- HERE in m/%{ <-- HERE \?}/ at ./run line 290.
[nolink.test]
28 commands (28 passed, 0 failed)
Unescaped left brace in regex is deprecated, passed through in regex; marked by 
<-- HERE in m/%{ <-- HERE (\w+)}/ at ./run line 114.
Unescaped left brace in regex is deprecated, passed through in regex; marked by 
<-- HERE in m/%{ <-- HERE \?}/ at ./run line 290.
[three.test]
58 commands (58 passed, 0 failed)
Unescaped left brace in regex is deprecated, passed through in regex; marked by 
<-- HERE in m/%{ <-- HERE (\w+)}/ at ./run line 114.
Unescaped left brace in regex is deprecated, passed through in regex; marked by 
<-- HERE in m/%{ <-- HERE \?}/ at ./run line 290.
[edit.test]
15 commands (15 passed, 0 failed)
Unescaped left brace in regex is deprecated, passed through in regex; marked by 
<-- HERE in m/%{ <-- HERE (\w+)}/ at ./run line 114.
Unescaped left brace in regex is deprecated, passed through in regex; marked by 
<-- HERE in m/%{ <-- HERE \?}/ at ./run line 290.
[faildiff.test]
[1] $ mkdir patches -- ok
[3] $ quilt new test.diff -- ok
[6] $ cat > test.txt -- ok
[8] $ quilt add test.txt -- ok
[13] $ chmod -r test.txt -- ok
[15] $ quilt refresh -- ok
[18] $ echo 1 -- ok
[21] $ chmod +r test.txt -- ok
[25] $ printf "\\002\\000\\001" > test.bin -- ok
[26] $ quilt add test.bin -- ok
[29] $ printf "\\003\\000\\001" > test.bin -- ok
[30] $ quilt diff -pab --no-index -- ok
[32] $ echo 0 -- failed
0 != 1
[35] $ quilt refresh -- failed
Refreshed patch patches/test.diff != Diff failed on file 'test.bin', 
aborting
[37] $ echo 0 -- failed
0 != 1
15 commands (12 passed, 3 failed)
Makefile:407: recipe for target 'test/.faildiff.ok' failed
make[2]: *** [test/.faildiff.ok] Error 3
make[2]: Leaving directory '/<>'
dh_auto_test: make -j1 check VERBOSE=1 returned exit code 2
debian/rules:48: recipe for target 'override_dh_auto_test' failed
make[1]: *** [override_dh_auto_test] Error 2
make[1]: Leaving directory '/<>'
debian/rules:7: recipe for target 'build-indep' failed
make: *** [build-indep] Error 2
dpkg-buildpackage: error: debian/rules build-indep gave error exit status 2


The failure does not seem related to using "dpkg-buildpackage -A".

Thanks.

Bug#836508: barbican: FTBFS in testing (failing tests)

[Santiago Vila]

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

[... snipped ...]

barbican.tests.tasks.test_resources.WhenUsingOrderTaskHelper.test_should_handle_success_result_large_statuses_clipped
barbican.tests.tasks.test_resources.WhenUsingOrderTaskHelper.test_should_handle_success_result_large_statuses_clipped
 ... ok
barbican.tests.tasks.test_resources.WhenUsingOrderTaskHelper.test_should_handle_success_result_no_follow_on_needed
barbican.tests.tasks.test_resources.WhenUsingOrderTaskHelper.test_should_handle_success_result_no_follow_on_needed
 ... ok
barbican.tests.tasks.test_resources.WhenUsingOrderTaskHelper.test_should_retrieve_entity
barbican.tests.tasks.test_resources.WhenUsingOrderTaskHelper.test_should_retrieve_entity
 ... ok

==
FAIL: 
barbican.tests.plugin.test_snakeoil_ca.CertManagerTestCase.test_gen_cert_no_file_storage
barbican.tests.plugin.test_snakeoil_ca.CertManagerTestCase.test_gen_cert_no_file_storage
--
_StringException: Empty attachments:
  pythonlogging:''
  stderr
  stdout

Traceback (most recent call last):
  File "barbican/tests/plugin/test_snakeoil_ca.py", line 166, in 
test_gen_cert_no_file_storage
self.verify_sig(cert_enc)
  File "barbican/tests/plugin/test_snakeoil_ca.py", line 157, in verify_sig
crypto.verify(self.ca.cert, sig[1:], der[0], 'sha256')
  File "/usr/lib/python2.7/dist-packages/OpenSSL/crypto.py", line 2605, in 
verify
md_ctx = _ffi.new("EVP_MD_CTX*")
TypeError: cannot instantiate ctype 'EVP_MD_CTX' of unknown size


==
FAIL: 
barbican.tests.plugin.test_snakeoil_ca.CertManagerTestCase.test_gen_cert_with_file_storage
barbican.tests.plugin.test_snakeoil_ca.CertManagerTestCase.test_gen_cert_with_file_storage
--
_StringException: Empty attachments:
  pythonlogging:''
  stderr
  stdout

Traceback (most recent call last):
  File "barbican/tests/plugin/test_snakeoil_ca.py", line 182, in 
test_gen_cert_with_file_storage
self.verify_sig(cert_enc)
  File "barbican/tests/plugin/test_snakeoil_ca.py", line 157, in verify_sig
crypto.verify(self.ca.cert, sig[1:], der[0], 'sha256')
  File "/usr/lib/python2.7/dist-packages/OpenSSL/crypto.py", line 2605, in 
verify
md_ctx = _ffi.new("EVP_MD_CTX*")
TypeError: cannot instantiate ctype 'EVP_MD_CTX' of unknown size


--
Ran 1216 tests in 80.278s

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


The failure does not seem related to using "dpkg-buildpackage -A".

Thanks.

Bug#836509: glance: FTBFS in testing (failing tests)

[Santiago Vila]

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

[... snipped ...]

glance.tests.unit.v2.test_tasks_resource.TestTasksDeserializer.test_index_non_integer_limit
glance.tests.unit.v2.test_tasks_resource.TestTasksDeserializer.test_index_non_integer_limit
 ... ok
glance.tests.unit.v2.test_tasks_resource.TestTasksDeserializer.test_index_sort_dir_asc
glance.tests.unit.v2.test_tasks_resource.TestTasksDeserializer.test_index_sort_dir_asc
 ... ok
glance.tests.unit.v2.test_tasks_resource.TestTasksDeserializer.test_index_sort_dir_bad_value
glance.tests.unit.v2.test_tasks_resource.TestTasksDeserializer.test_index_sort_dir_bad_value
 ... ok
glance.tests.unit.v2.test_tasks_resource.TestTasksDeserializer.test_index_sort_key_id
glance.tests.unit.v2.test_tasks_resource.TestTasksDeserializer.test_index_sort_key_id
 ... ok
glance.tests.unit.v2.test_tasks_resource.TestTasksDeserializer.test_index_strip_params_from_filters
glance.tests.unit.v2.test_tasks_resource.TestTasksDeserializer.test_index_strip_params_from_filters
 ... ok
glance.tests.unit.v2.test_tasks_resource.TestTasksDeserializer.test_index_with_filter_and_limit
glance.tests.unit.v2.test_tasks_resource.TestTasksDeserializer.test_index_with_filter_and_limit
 ... ok
glance.tests.unit.v2.test_tasks_resource.TestTasksDeserializer.test_index_with_many_filter
glance.tests.unit.v2.test_tasks_resource.TestTasksDeserializer.test_index_with_many_filter
 ... ok
glance.tests.unit.v2.test_tasks_resource.TestTasksDeserializer.test_index_zero_limit
glance.tests.unit.v2.test_tasks_resource.TestTasksDeserializer.test_index_zero_limit
 ... ok
glance.tests.unit.v2.test_tasks_resource.TestTasksSerializer.test_create
glance.tests.unit.v2.test_tasks_resource.TestTasksSerializer.test_create ... ok
glance.tests.unit.v2.test_tasks_resource.TestTasksSerializer.test_create_ensure_expires_at_is_not_returned
glance.tests.unit.v2.test_tasks_resource.TestTasksSerializer.test_create_ensure_expires_at_is_not_returned
 ... ok
glance.tests.unit.v2.test_tasks_resource.TestTasksSerializer.test_get
glance.tests.unit.v2.test_tasks_resource.TestTasksSerializer.test_get ... ok
glance.tests.unit.v2.test_tasks_resource.TestTasksSerializer.test_get_ensure_expires_at_not_returned
glance.tests.unit.v2.test_tasks_resource.TestTasksSerializer.test_get_ensure_expires_at_not_returned
 ... ok
glance.tests.unit.v2.test_tasks_resource.TestTasksSerializer.test_index
glance.tests.unit.v2.test_tasks_resource.TestTasksSerializer.test_index ... ok
glance.tests.unit.v2.test_tasks_resource.TestTasksSerializer.test_index_carries_query_parameters
glance.tests.unit.v2.test_tasks_resource.TestTasksSerializer.test_index_carries_query_parameters
 ... ok
glance.tests.unit.v2.test_tasks_resource.TestTasksSerializer.test_index_next_marker
glance.tests.unit.v2.test_tasks_resource.TestTasksSerializer.test_index_next_marker
 ... ok

==
FAIL: glance.tests.unit.common.test_utils.TestUtils.test_validate_key_cert_key
glance.tests.unit.common.test_utils.TestUtils.test_validate_key_cert_key
--
_StringException: Traceback (most recent call last):
  File "glance/tests/unit/common/test_utils.py", line 276, in 
test_validate_key_cert_key
utils.validate_key_cert(keyfile, certfile)
  File "glance/common/utils.py", line 431, in validate_key_cert
out = crypto.sign(key, data, digest)
  File "/usr/lib/python2.7/dist-packages/OpenSSL/crypto.py", line 2563, in sign
md_ctx = _ffi.new("EVP_MD_CTX*")
TypeError: cannot instantiate ctype 'EVP_MD_CTX' of unknown size


--
Ran 2162 tests in 529.312s

FAILED (failures=1, skipped=11)
debian/rules:17: recipe for target 'override_dh_auto_test' failed
make[1]: *** [override_dh_auto_test] Error 1
make[1]: Leaving directory '/<>

Bug#836505: elog: CVE-2016-6342: posting entry as arbitrary username by improper authentication

[Salvatore Bonaccorso]

Source: elog
Version: 2.9.2+2014.05.11git44800a7-2
Severity: grave
Tags: security upstream patch

Hi,

the following vulnerability was published for elog.

CVE-2016-6342[0]:
posting entry as arbitrary username by improper authentication

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

Using severity grave, since for at least stretch this should be fixed
to be in a fixed version. I OTOH do not know elog well enough to see
if the affected setup is actual a frequent one.

Could you as well schedule a fix for the stable version via a
point-release, cf.
https://www.debian.org/doc/manuals/developers-reference/ch05.en.html#upload-stable

Regards,
Salvatore

Bug#826300: [Pkg-pascal-devel] Bug#826300: Share knowledge on fpc and powerpc issue

[Paul Gevers]

Hi Graham,

On 03-09-16 15:15, Graham Inggs wrote:
> Of course you mean s/doublecmd/ddrescueview/ there.

Indeed, duh...

> A wild stab in the dark: don't we need to binNMU lazarus before we can
> build packages with it?

Hmm, forgot about that. You are probably right.

> Then, don't we need to binNMU everything that build with the old fpc
> for powerpc?

Probably, at least to be sure. I'll be filing the bug reports this
evening (UTC+2) hopefully.

Paul



signature.asc
Description: OpenPGP digital signature

Bug#830568: python-asyncssh: accesses the internet during build

[Chris Lamb]

Hi Vincent,

> Was this MBF discussed somewhere?

I don't consider it to be a MBF — I haven't been systematically working
my way through the archive and I've really only filed a handful of bugs;
mostly quasi-duplicates due to Sphinx stuff (which is arguably more a
QA thing than to do with violation of any policy).

Hope that helps.


Regards,

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

Bug#672390: Please consider chaging dependency of libsigc++1.2 to 2.0

[Bhavani Shankar R]

Hi Manuel,

I am the maintainer of freqtweak in Debian,

Sorry for the late response as I was busy all these days

I am taking a look at all bugs now and will come up with an upload soon.

On Thu, May 10, 2012 at 11:24 PM, Manuel A. Fernandez Montecelo
 wrote:
> Source: freqtweak
> Version: 0.7.2-4
> Severity: normal
>
> Hello,
>
> I would like to ask you to consider changing the build-depends from
> libsigc++-1.2-dev to libsigc++-2.0-dev.
>
> The version in 1.2 is very old, unsupported (last release on 2005,
> more than 7 years ago) and it should probably be removed from Debian
> when possible.
>
> There are only 3 packages in the whole archive depending on it (versus
> 150+ for 2.0), and this is one of them.
>
> Regards.
>
>



-- 
Bhavani Shankar
Ubuntu Developer   |  www.ubuntu.com
https://launchpad.net/~bhavi

Bug#826300: [Pkg-pascal-devel] Bug#826300: Share knowledge on fpc and powerpc issue

[Graham Inggs]

On 3 September 2016 at 13:47, Paul Gevers  wrote:
> Unfortunately it doesn't seem to solve all issues. At least doublecmd
> now only FTBFS on powerpc (yes, fpc installed fine):
>
> An unhandled exception occurred at $0FE281F0:
> EAccessViolation:
>   $0FE281F0
>   $0FE36604
>   $0FDED188
>   $0FDED25C
>
> See
> https://buildd.debian.org/status/fetch.php?pkg=ddrescueview&arch=powerpc&ver=0.4~alpha3-1&stamp=1472901797

Of course you mean s/doublecmd/ddrescueview/ there.

A wild stab in the dark: don't we need to binNMU lazarus before we can
build packages with it?

Then, don't we need to binNMU everything that build with the old fpc
for powerpc?

Bug#797998: unknown-horizons: Crash shortly after start of single player game

[Markus Koschany]

forwarded 797998 
https://github.com/unknown-horizons/unknown-horizons/issues/2295
thanks

Apparently unknown horizon is incompatible with Swig >= 3 and both the fife 
engine and the game
itself have to be updated to the current Git master version.

I requested a new release at

https://github.com/unknown-horizons/unknown-horizons/issues/2471




signature.asc
Description: OpenPGP digital signature

Processed: Re: unknown-horizons: Crash shortly after start of single player game

[Debian Bug Tracking System]

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

> forwarded 797998 
> https://github.com/unknown-horizons/unknown-horizons/issues/2295
Bug #797998 [unknown-horizons] unknown-horizons: Crash shortly after start of 
single player game
Set Bug forwarded-to-address to 
'https://github.com/unknown-horizons/unknown-horizons/issues/2295'.
> thanks
Stopping processing here.

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

Bug#836456: marked as done (AttributeError: 'file' object has no attribute 'readable')

[Debian Bug Tracking System]

Your message dated Sat, 03 Sep 2016 12:22:39 +
with message-id 
and subject line Bug#836456: fixed in dput 0.10.3
has caused the Debian Bug report #836456,
regarding AttributeError: 'file' object has no attribute 'readable'
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.)


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

Hello,

every time I try to upload something I get the following:

>  % dput local-desktop_0.83_amd64.changes
> Trying to upload package to ghedini.me
> Checking signature on .changes
> Traceback (most recent call last):
>   File "/usr/bin/dput", line 11, in 
> load_entry_point('dput==0.10.2', 'console_scripts', 'execute-dput')()
>   File "/usr/share/dput/dput/dput.py", line 1053, in main
> config, check_only, check_version, unsigned_upload, debug)
>   File "/usr/share/dput/dput/dput.py", line 415, in verify_files
> config, check_only, unsigned_upload, binary_upload, debug)
>   File "/usr/share/dput/dput/dput.py", line 313, in verify_signature
> check_signature(changes_file)
>   File "/usr/share/dput/dput/dput.py", line 248, in check_signature
> gnupg_stdout = dputhelper.make_text_stream(gnupg_subprocess.stdout)
>   File "/usr/share/dput/dput/helper/dputhelper.py", line 188, in 
> make_text_stream
> result = io.TextIOWrapper(stream, encoding=encoding)
> AttributeError: 'file' object has no attribute 'readable'
> gpg: Signature made Sat 03 Sep 2016 12:33:10 BST
> gpg:using RSA key 6F0CCBE021624728
> gpg:issuer "gh...@debian.org"
> gpg: Good signature from "Alessandro Ghedini " 
> [unknown]
> gpg: aka "Alessandro Ghedini " [unknown]
> gpg: aka "Alessandro Ghedini " [unknown]

then dput dies and the pckage does not get uploaded.

Cheers

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

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

Versions of packages dput depends on:
ii  gnupg 2.1.15-2
ii  python-debian 0.1.29
ii  python-pkg-resources  26.1.1-1
pn  python:any

dput recommends no packages.

Versions of packages dput suggests:
pn  lintian 
pn  mini-dinstall   
ii  openssh-client  1:7.3p1-1
pn  rsync   

-- no debconf information


signature.asc
Description: PGP signature
--- End Message ---
--- Begin Message ---
Source: dput
Source-Version: 0.10.3

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

Debian distribution maintenance software
pp.
Ben Finney  (supplier of updated dput 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, 03 Sep 2016 22:02:50 +1000
Source: dput
Binary: dput
Architecture: source
Version: 0.10.3
Distribution: unstable
Urgency: medium
Maintainer: Ben Finney 
Changed-By: Ben Finney 
Description:
 dput   - Debian package upload tool
Closes: 836456
Changes:
 dput (0.10.3) unstable; urgency=medium
 .
   * The “Shafiul Islam” release.
   * Special-case streams that are the Python 2 brute ‘file’ type.
 Closes: bug#836456. Thanks to Alessandro Ghedini for the report.
Checksums-Sha1:
 869443c5706cb06cb5810a2791744e44a8770ae5 1733 dput_0.10.3.dsc
 5568bbcb0c2f78c1b55721820a5eec6f3a6a997e 98300 dput_0.10.3.tar.xz
Checksums-Sha256:
 82136f3f162aa84b8977c4cba31a0eca539f24f3bc44ad42dc4f7a892749 1733 
dput_0.10.3.dsc
 d66e9fc4d6072cc64a9228a1bb6d87eed3b2892789915c93e966be9ab3cb3436 98300 
dput_0.10.3.tar.xz
Files:
 cb6a7556c960122d9ce4a8f39646ccda 1733 devel optional dput_0.10.3.dsc
 c9a14102dbbabac6158a50f16f40e62f 98300 devel optional dput_0.10.3.tar.xz

-BEGIN PGP SI

Bug#836377: separate issue for a separate report

[Ben Finney]

On 03-Sep-2016, gregor herrmann wrote:

> I consider the following as RC as well:

That's quite different behaviour, so should be in a separate bug
report.

Fortunately bug#836456 already addresses that separate issue, so I'll
respond to it there.

-- 
 \   “I was sleeping the other night, alone, thanks to the |
  `\   exterminator.” —Emo Philips |
_o__)  |
Ben Finney 


signature.asc
Description: PGP signature

Bug#836377: marked as done (build system terminal locale not inherited by build programs)

[Debian Bug Tracking System]

Your message dated Sat, 3 Sep 2016 21:57:25 +1000
with message-id <20160903115724.p2jlyhvwbjrjw...@benfinney.id.au>
and subject line Re: Bug#836377: build system terminal locale not inherited by 
build programs
has caused the Debian Bug report #836377,
regarding build system terminal locale not inherited by build programs
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.)


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

The package ‘dput’ explicitly sets the ‘LC_ALL’ environment variable
to “C.UTF-8”, and exports that value to sub-processes
https://sources.debian.net/src/dput/0.10.1/debian/rules/>.

Yet the latest reproducible-build attempt reports failure
https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/dput.html>.

Specifically, the build system does not detect a UTF-8 locale:

=
Traceback (most recent call last):
  […]
UnicodeEncodeError: 'ascii' codec can't encode character u'\u2009' in position 
186: ordinal not in range(128)
E: pybuild pybuild:276: test: plugin distutils failed with: exit code=1: 
python2.7 setup.py test 
dh_auto_test: pybuild --test -i python{version} -p 2.7 returned exit code 13
debian/rules:24: recipe for target 'build' failed
make: *** [build] Error 25
dpkg-buildpackage: error: debian/rules build gave error exit status 2
=

This happens only on the reproducible build server; when running on a
system that actually has a UTF-8 terminal locale, the build succeeds.

-- 
 \ “Nothing worth saying is inoffensive to everyone. Nothing worth |
  `\saying will fail to make you enemies. And nothing worth saying |
_o__)will not produce a confrontation.” —Johann Hari, 2011 |
Ben Finney 


signature.asc
Description: PGP signature
--- End Message ---
--- Begin Message ---
Control: fixed -1 dput/0.10.2

On 02-Sep-2016, Holger Levsen wrote:
> then I suppose this is an RC bug in dput :-D

Well, not as described. But you're right, the terminal encoding issue
was a problem in ‘dput’.

The bug was in variables to specify terminal encoding. I have uploaded
version “0.10.2”, which specifically addressed that, fixing this bug.

-- 
 \“The fact of your own existence is the most astonishing fact |
  `\you'll ever have to confront. Don't dare ever see your life as |
_o__)boring, monotonous, or joyless.” —Richard Dawkins, 2010-03-10 |
Ben Finney 


signature.asc
Description: PGP signature
--- End Message ---

Bug#826300: Share knowledge on fpc and powerpc issue

[Paul Gevers]

Hi

Unfortunately it doesn't seem to solve all issues. At least doublecmd
now only FTBFS on powerpc (yes, fpc installed fine):

An unhandled exception occurred at $0FE281F0:
EAccessViolation:
  $0FE281F0
  $0FE36604
  $0FDED188
  $0FDED25C

See
https://buildd.debian.org/status/fetch.php?pkg=ddrescueview&arch=powerpc&ver=0.4~alpha3-1&stamp=1472901797

Paul



signature.asc
Description: OpenPGP digital signature

Bug#836456: AttributeError: 'file' object has no attribute 'readable'

[Alessandro Ghedini]

Package: dput
Version: 0.10.2
Severity: grave
Justification: renders package unusable

Hello,

every time I try to upload something I get the following:

>  % dput local-desktop_0.83_amd64.changes
> Trying to upload package to ghedini.me
> Checking signature on .changes
> Traceback (most recent call last):
>   File "/usr/bin/dput", line 11, in 
> load_entry_point('dput==0.10.2', 'console_scripts', 'execute-dput')()
>   File "/usr/share/dput/dput/dput.py", line 1053, in main
> config, check_only, check_version, unsigned_upload, debug)
>   File "/usr/share/dput/dput/dput.py", line 415, in verify_files
> config, check_only, unsigned_upload, binary_upload, debug)
>   File "/usr/share/dput/dput/dput.py", line 313, in verify_signature
> check_signature(changes_file)
>   File "/usr/share/dput/dput/dput.py", line 248, in check_signature
> gnupg_stdout = dputhelper.make_text_stream(gnupg_subprocess.stdout)
>   File "/usr/share/dput/dput/helper/dputhelper.py", line 188, in 
> make_text_stream
> result = io.TextIOWrapper(stream, encoding=encoding)
> AttributeError: 'file' object has no attribute 'readable'
> gpg: Signature made Sat 03 Sep 2016 12:33:10 BST
> gpg:using RSA key 6F0CCBE021624728
> gpg:issuer "gh...@debian.org"
> gpg: Good signature from "Alessandro Ghedini " 
> [unknown]
> gpg: aka "Alessandro Ghedini " [unknown]
> gpg: aka "Alessandro Ghedini " [unknown]

then dput dies and the pckage does not get uploaded.

Cheers

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

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

Versions of packages dput depends on:
ii  gnupg 2.1.15-2
ii  python-debian 0.1.29
ii  python-pkg-resources  26.1.1-1
pn  python:any

dput recommends no packages.

Versions of packages dput suggests:
pn  lintian 
pn  mini-dinstall   
ii  openssh-client  1:7.3p1-1
pn  rsync   

-- no debconf information


signature.asc
Description: PGP signature

Bug#830568: python-asyncssh: accesses the internet during build

[Vincent Bernat]

 ❦  9 juillet 2016 15:26 CEST, Chris Lamb  :

> Source: python-asyncssh
> Version: 1.5.6-1
> Severity: serious
> Justification: Policy 4.9
> User: la...@debian.org
> Usertags: network-access
>
> Dear Maintainer,
>
> Whilst python-asyncssh builds successfully on unstable/amd64, according to
> Debian Policy 4.9 packages may not attempt network access during
> a build.
>
>   00:00:00.00 IP f8fc55487205.58764 > dnscache.uct.ac.za.domain: 33265+ 
> A? fail.uct.ac.za. (32)
>   00:00:00.46 IP f8fc55487205.58764 > dnscache.uct.ac.za.domain: 12531+ 
> ? fail.uct.ac.za. (32)
>   00:00:00.001320 IP dnscache.uct.ac.za.domain > f8fc55487205.58764: 33265 
> NXDomain* 0/1/0 (86)
>   00:00:00.001523 IP dnscache.uct.ac.za.domain > f8fc55487205.58764: 12531 
> NXDomain* 0/1/0 (86)
>   00:00:00.001604 IP f8fc55487205.47627 > dnscache.uct.ac.za.domain: 56301+ 
> A? fail.chris-lamb.co.uk. (39)
>   00:00:00.001620 IP f8fc55487205.47627 > dnscache.uct.ac.za.domain: 35318+ 
> ? fail.chris-lamb.co.uk. (39)
>
>   [..]
>
> The full build log (including tcpdump output) is attached.

Hey!

Was this MBF discussed somewhere?

I am dubious about this bug and think it should have been discussed on
debian-devel@ (but I may have missed the thread).
-- 
Don't comment bad code - rewrite it.
- The Elements of Programming Style (Kernighan & Plauger)


signature.asc
Description: PGP signature

Processed: perl hasn't been updated yet...

[Debian Bug Tracking System]

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

> severity 835497 important
Bug #835497 [src:xemacs21-packages] xemacs21-packages: FTBFS with '.' removed 
from perl's @INC
Severity set to 'important' from 'serious'
>
End of message, stopping processing here.

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

Bug#836452: givaro: FTBFS when built with dpkg-buildpackage -A (chmod: cannot access '[...]/isgenerator.C': No such file or directory)

[Santiago Vila]

Package: src:givaro
Version: 4.0.2-2
Severity: serious
Tags: patch

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 autoreconf 
   dh_testdir -i
   dh_update_autotools_config -i
   dh_autoreconf -i
libtoolize: putting auxiliary files in AC_CONFIG_AUX_DIR, 'build-aux'.
libtoolize: copying file 'build-aux/ltmain.sh'
libtoolize: putting macros in AC_CONFIG_MACRO_DIRS, 'macros'.
libtoolize: copying file 'macros/libtool.m4'
libtoolize: copying file 'macros/ltoptions.m4'
libtoolize: copying file 'macros/ltsugar.m4'
libtoolize: copying file 'macros/ltversion.m4'
libtoolize: copying file 'macros/lt~obsolete.m4'

[... snipped ...]

make[4]: Nothing to be done for 'install-exec-am'.
make[4]: Nothing to be done for 'install-data-am'.
make[4]: Leaving directory '/<>/examples/RecInt'
make[3]: Leaving directory '/<>/examples/RecInt'
make[3]: Entering directory '/<>/examples'
make[4]: Entering directory '/<>/examples'
make[4]: Nothing to be done for 'install-exec-am'.
make[4]: Nothing to be done for 'install-data-am'.
make[4]: Leaving directory '/<>/examples'
make[3]: Leaving directory '/<>/examples'
make[2]: Leaving directory '/<>/examples'
Making install in benchmarks
make[2]: Entering directory '/<>/benchmarks'
make[3]: Entering directory '/<>/benchmarks'
make[4]: Entering directory '/<>/benchmarks'
make[4]: Nothing to be done for 'install-exec-am'.
make[4]: Nothing to be done for 'install-data-am'.
make[4]: Leaving directory '/<>/benchmarks'
make[3]: Leaving directory '/<>/benchmarks'
make[2]: Leaving directory '/<>/benchmarks'
make[2]: Entering directory '/<>'
make[3]: Entering directory '/<>'
 /bin/mkdir -p '/<>/debian/tmp/usr/bin'
 /usr/bin/install -c givaro-config givaro-makefile 
'/<>/debian/tmp/usr/bin'
 /bin/mkdir -p '/<>/debian/tmp/usr/include'
 /usr/bin/install -c -m 644 givaro-config.h 
'/<>/debian/tmp/usr/include'
 /bin/mkdir -p '/<>/debian/tmp/usr/lib/x86_64-linux-gnu/pkgconfig'
 /usr/bin/install -c -m 644 givaro.pc 
'/<>/debian/tmp/usr/lib/x86_64-linux-gnu/pkgconfig'
make[3]: Leaving directory '/<>'
make[2]: Leaving directory '/<>'
make[1]: Leaving directory '/<>'
   dh_install -i
   dh_installdocs -i
   dh_installchangelogs -i
   debian/rules override_dh_installexamples
make[1]: Entering directory '/<>'
dh_installexamples -XMakefile -XMakefile.am -XMakefile.in
make[1]: Leaving directory '/<>'
   dh_lintian -i
   dh_perl -i
   dh_link -i
   dh_strip_nondeterminism -i
   dh_compress -i
   debian/rules override_dh_fixperms
make[1]: Entering directory '/<>'
dh_fixperms
chmod -x 
debian/libgivaro-dev/usr/share/doc/libgivaro-dev/examples/Polynomial/isgenerator.C
chmod: cannot access 
'debian/libgivaro-dev/usr/share/doc/libgivaro-dev/examples/Polynomial/isgenerator.C':
 No such file or directory
debian/rules:35: recipe for target 'override_dh_fixperms' failed
make[1]: *** [override_dh_fixperms] Error 1
make[1]: Leaving directory '/<>'
debian/rules:41: recipe for target 'binary-indep' failed
make: *** [binary-indep] Error 2
dpkg-buildpackage: error: fakeroot debian/rules binary-indep gave error exit 
status 2


This happens because debian/libgivaro-dev/[...] does not exist,
as we are creating arch-independent packages only and libgivaro-dev
is "Arch: any".

The patch below (trivial but untested) might fix this.

Thanks.

--- a/debian/rules
+++ b/debian/rules
@@ -31,7 +31,7 @@ override_dh_auto_build-indep:
 override_dh_auto_test:
dh_auto_test --max-parallel=1
 
-override_dh_fixperms:
+override_dh_fixperms-arch:
dh_fixperms
chmod -x 
debian/libgivaro-dev/usr/share/doc/libgivaro-dev/examples/Polynomial/isgenerator.C
 

Bug#836338: grads: FTBFS with libdap 3.18.0

[Alastair McKinstry]

This requires a rebuild of gadap, which I've just uploaded. A fixed grads 
should follow tonight.


On 1 September 2016 21:48:06 GMT+01:00, Bas Couwenberg  
wrote:
>Source: grads
>Version: 2:2.1.a3-3
>Severity: serious
>Tags: upstream
>Justification: make the package in question unusable or mostly so
>Control: block 836192 by -1
>
>Dear Maintainer,
>
>As mentioned in the libdap transition bugreport (#836192), grads fails
>to build with libdap 3.18.0. The buildlogs report:
>
>g++  -g -O2 -fdebug-prefix-map=/«PKGBUILDDIR»=.
>-fstack-protector-strong -Wformat -Werror=format-security -rdynamic 
>-Wl,-z,relro -L/usr/lib/x86_64-linux-gnu/hdf5/serial -Lyes/lib
>-Wl,--as-needed -o grads grads.o gxsubs.o gxmeta.o gxchpl.o gxcntr.o
>gxstrm.o gxwmap.o gxshad.o gxshad2.o gaexpr.o gafunc.o gautil.o gagx.o
>gscrpt.o gamach.o bufrstn.o gabufr.o gabufrtbl.o gxdxwd.o galloc.o 
>dodstn.o gaddes.o gaio.o gacfg.o gauser.o gasdf.o gatxt.o gxX.o gxC.o
>gxprint.o -L/usr/lib-lX11 -lXext -lreadline  -ltermcap -lgd -lpng16
>-lz -ljpeg -lgrib2c -lmfhdfalt -ldfalt -ludunits2 -lsz -ljpeg -lz
>-lhdf5 -ljpeg -lz -lsz -lnetcdf -ludunits2  -ltiff -lgeotiff -lshp
>-lgadap -ldapclient -ldap -lcurl -lxml2 -lz -lpthread -lm -ldl -lrt
>-lcairo -lXrender -lfontconfig -lfreetype -lpixman-1 -lpng16 -lxml2 -lz
>-lm  -lcairo -lfreetype
>/usr/lib/gcc/x86_64-linux-gnu/6/../../../x86_64-linux-gnu/libgadap.a(gaConnect.o):
>In function `gaConnect::gaConnect(std::__cxx11::basic_stringstd::char_traits, std::allocator >,
>std::__cxx11::basic_string,
>std::allocator >, std::__cxx11::basic_stringstd::char_traits, std::allocator >)':
> (.text+0x1633): undefined reference to `libdap::DAS::DAS()'
> collect2: error: ld returned 1 exit status
>
>Kind Regards,
>
>Bas

-- 
Sent from my Android device with K-9 Mail. Please excuse my brevity.

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

[Debian Bug Tracking System]

Your message dated Sat, 03 Sep 2016 10:55:45 +
with message-id 
and subject line Bug#835491: fixed in slack 1:0.15.2-9
has caused the Debian Bug report #835491,
regarding slack: 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.)


-- 
835491: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=835491
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: slack
Version: 0.15.2-8
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
by explicitly re-adding '.' to @INC where needed in test scripts.

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.

By the way, when preparing this patch I found that the git repository
at git://anonscm.debian.org/collab-maint/polymake.git was behind the
Debian archive.

Thanks,
Dominic.

[1] 

[2] 
diff -urN slack-0.15.2.orig/test/01_module.t slack-0.15.2/test/01_module.t
--- slack-0.15.2.orig/test/01_module.t	2008-04-21 02:06:10.0 +0100
+++ slack-0.15.2/test/01_module.t	2016-08-26 11:17:14.629445024 +0100
@@ -5,7 +5,7 @@
 
 BEGIN {
 chdir 'test' if -d 'test';
-unshift @INC, '../src';
+unshift @INC, '../src', '.';
 use_ok("Slack");
 }
 
diff -urN slack-0.15.2.orig/test/02_getroles.t slack-0.15.2/test/02_getroles.t
--- slack-0.15.2.orig/test/02_getroles.t	2008-04-21 02:06:10.0 +0100
+++ slack-0.15.2/test/02_getroles.t	2016-08-26 11:17:22.709336964 +0100
@@ -1,5 +1,7 @@
 #!/usr/bin/perl -w
 
+BEGIN { unshift @INC, '.' }
+
 use strict;
 use Test::More tests => 6;
 use test_util;
diff -urN slack-0.15.2.orig/test/03_sync.t slack-0.15.2/test/03_sync.t
--- slack-0.15.2.orig/test/03_sync.t	2008-04-21 02:06:10.0 +0100
+++ slack-0.15.2/test/03_sync.t	2016-08-26 11:17:30.901227349 +0100
@@ -1,5 +1,7 @@
 #!/usr/bin/perl -w
 
+BEGIN { unshift @INC, '.' }
+
 use strict;
 use warnings FATAL => qw(all);
 use Test::More;
diff -urN slack-0.15.2.orig/test/04_stage.t slack-0.15.2/test/04_stage.t
--- slack-0.15.2.orig/test/04_stage.t	2008-04-21 02:06:11.0 +0100
+++ slack-0.15.2/test/04_stage.t	2016-08-26 11:17:34.629177462 +0100
@@ -1,5 +1,7 @@
 #!/usr/bin/perl -w
 
+BEGIN { unshift @INC, '.' }
+
 use strict;
 use warnings FATAL => qw(all);
 use Test::More tests => 15;
diff -urN slack-0.15.2.orig/test/05_runscript.t slack-0.15.2/test/05_runscript.t
--- slack-0.15.2.orig/test/05_runscript.t	2008-04-21 02:06:10.0 +0100
+++ slack-0.15.2/test/05_runscript.t	2016-08-26 11:17:37.877134008 +0100
@@ -1,5 +1,7 @@
 #!/usr/bin/perl -w
 
+BEGIN { unshift @INC, '.' }
+
 use strict;
 use Test::More tests => 18;
 use test_util;
diff -urN slack-0.15.2.orig/test/06_installfiles.t slack-0.15.2/test/06_installfiles.t
--- slack-0.15.2.orig/test/06_installfiles.t	2008-04-21 02:06:10.0 +0100
+++ slack-0.15.2/test/06_installfiles.t	2016-08-26 11:17:41.093091097 +0100
@@ -1,5 +1,7 @@
 #!/usr/bin/perl -w
 
+BEGIN { unshift @INC, '.' }
+
 use strict;
 use warnings FATAL => qw(all);
 use Test::More tests => 13;
diff -urN slack-0.15.2.orig/test/07_frontend.t slack-0.15.2/test/07_frontend.t
--- slack-0.15.2.orig/test/07_frontend.t	2008-04-21 02:06:11.0 +0100
+++ slack-0.15.2/test/07_frontend.t	2016-08-26 11:17:44.581044326 +0100
@@ -1,5 +1,7 @@
 #!/usr/bin/perl -w
 
+BEGIN { unshift @INC, '.' }
+
 use strict;
 use warnings FATAL => qw(all);
 use Test::More tests => 13;
diff -urN slack-0.15.2.orig/test/08_diff.t slack-0.15.2/test/08_diff.t
--- slack-0.15.2.orig/test/08_diff.t	2008-04-21 02:06:10.0 +0100
+++ slack-0.15.2/test/08_diff.t	2016-08-26 11:17:48.100997199 +0100
@@ -1,5 +1,7 @@
 #!/usr/bin/perl -w
 
+BEGIN { unshift @INC, '.' }
+
 use strict;
 use POSIX qw(strftime);
 #use Test::More qw(no_plan); # tests => 12;
diff -urN slack-0.15.2.orig/test/gen_config_file slack-0.15.2/test/gen_config_file
--- slack-0.15.2.orig/test/gen_config_file	2008-04-21 02:06:11.0 +0100
+++ slack-0.15.2/test/gen_config_file	2016-08-26 11:17:55.812894220 +0100
@@ -1,5 +1,7 @@
 #!/usr/bin/perl -w
 
+BEGIN { unshift @INC, '.' }
+
 use test_util qw(gen_config_file);
 
 die unless $#ARGV==1;
--- End Me

Processed: bug 835241 is forwarded to https://github.com/pytest-dev/pytest-mock/issues/61

[Debian Bug Tracking System]

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

> forwarded 835241 https://github.com/pytest-dev/pytest-mock/issues/61
Bug #835241 [src:pytest-mock] pytest-mock: FTBFS against pytest 3.0.0
Set Bug forwarded-to-address to 
'https://github.com/pytest-dev/pytest-mock/issues/61'.
> thanks
Stopping processing here.

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

Bug#826300: marked as done (fpc: fp-compiler not installable on powerpc since glibc 2.23)

[Debian Bug Tracking System]

Your message dated Sat, 03 Sep 2016 10:41:08 +
with message-id 
and subject line Bug#826300: fixed in fpc 3.0.0+dfsg-8
has caused the Debian Bug report #826300,
regarding fpc: fp-compiler not installable on powerpc since glibc 2.23
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.)


-- 
826300: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=826300
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: fpc
Version: 3.0.0+dfsg-6
Severity: important
User: debian-gl...@lists.debian.org
Usertags: 2.23

Package fp-compiler fails to install on powerpc with libc6 2.23
(2.23-0experimental2 from
experimental).  Previously reported in Ubuntu [1], confirmed on
partch.debian.org.

$ schroot -b -c experimental -n $mysid

$ dd-schroot-cmd -c $mysid apt-get update

$ dd-schroot-cmd -c $mysid apt-get install libc6=2.23-0experimental2
libc-bin=2.23-0experimental2 libc6-dev=2.23-0experimental2
libc-dev-bin=2.23-0experimental2

$ dd-schroot-cmd -c $mysid apt-get install fpc

> Setting up fp-compiler-3.0.0 (3.0.0+dfsg-6) ...
> An unhandled exception occurred at $0FE28330:
> EAccessViolation:
>  $0FE28330
>  $0FE366E4
>  $0FDED248
>  $0FDED31C
>
> dpkg: error processing package fp-compiler-3.0.0 (--configure):
>  subprocess installed post-installation script returned error exit status 217

This will cause all packages build-depending on fpc; e.g. hedgewars,
lazarus, libqt4pas, and fpc itself, to FTBFS.


[1] https://bugs.launchpad.net/ubuntu/+source/fpc/+bug/1562480
--- End Message ---
--- Begin Message ---
Source: fpc
Source-Version: 3.0.0+dfsg-8

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

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

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

Debian distribution maintenance software
pp.
Peter Michael Green  (supplier of updated fpc 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, 3 Sep 2016 03:05:00 +
Source: fpc
Binary: fpc-3.0.0 fpc-source-3.0.0 fp-compiler-3.0.0 fp-ide-3.0.0 
fp-utils-3.0.0 fp-docs-3.0.0 fp-units-rtl-3.0.0 fp-units-base-3.0.0 
fp-units-fcl-3.0.0 fp-units-fv-3.0.0 fp-units-gtk2-3.0.0 fp-units-db-3.0.0 
fp-units-gfx-3.0.0 fp-units-net-3.0.0 fp-units-math-3.0.0 fp-units-misc-3.0.0 
fp-units-multimedia-3.0.0 fp-units-i386-3.0.0 fpc fpc-source fp-compiler fp-ide 
fp-utils fp-docs fp-units-rtl fp-units-base fp-units-fcl fp-units-fv 
fp-units-gtk2 fp-units-db fp-units-gfx fp-units-net fp-units-math fp-units-misc 
fp-units-multimedia fp-units-i386
Architecture: source powerpc all
Version: 3.0.0+dfsg-8
Distribution: unstable
Urgency: medium
Maintainer: Pascal Packaging Team 
Changed-By: Peter Michael Green 
Description:
 fp-compiler - Free Pascal - compiler dependency package
 fp-compiler-3.0.0 - Free Pascal - compiler
 fp-docs- Free Pascal - documentation dependency package
 fp-docs-3.0.0 - Free Pascal - documentation
 fp-ide - Free Pascal - IDE dependency package
 fp-ide-3.0.0 - Free Pascal - IDE
 fp-units-base - Free Pascal - base units dependency package
 fp-units-base-3.0.0 - Free Pascal - base units
 fp-units-db - Free Pascal - database-library units dependency package
 fp-units-db-3.0.0 - Free Pascal - database-library units
 fp-units-fcl - Free Pascal - Free Component Library dependency package
 fp-units-fcl-3.0.0 - Free Pascal - Free Component Library
 fp-units-fv - Free Pascal - Free Vision units dependency package
 fp-units-fv-3.0.0 - Free Pascal - Free Vision units
 fp-units-gfx - Free Pascal - graphics-library units dependency package
 fp-units-gfx-3.0.0 - Free Pascal - graphics-library units
 fp-units-gtk2 - Free Pascal - GTK+ 2.x units dependency package
 fp-units-gtk2-3.0.0 - Free Pascal - GTK+ 2.x units
 fp-units-i386 - Free Pascal - Kylix compatibility units dependency package
 fp-units-i386-3.0.0 - Free Pascal - Kylix compatibility units
 fp-units-math - Free Pascal - math units dependency package
 fp-units-math-3.0.0 - Free Pascal - math units
 fp-units-misc - Free Pascal - miscellaneous units dependency package
 fp-units-misc-3.0.0 - Free Pascal - miscellaneous units
 fp-units-multimedia - Free Pascal - multimedia units dependency

Bug#836449: tome: needs a rebuild for boost 1.61

[Emilio Pozuelo Monfort]

Package: tome
Version: 2.4~0.git.2015.12.29-1
Severity: serious

Hi,

tome needs to be rebuilt against boost 1.61. It can't be binNMUed as it's
in non-free, so please do a maintainer upload.

Thanks,
Emilio

Bug#836450: vowpal-wabbit: FTBFS everywhere

[Emilio Pozuelo Monfort]

Source: vowpal-wabbit
Version: 8.1.1-1
Severity: serious

Your package failed to build everywhere:

https://buildd.debian.org/status/package.php?p=vowpal-wabbit&suite=unstable

Emilio

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

Kernel: Linux 4.6.0-1-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: systemd (via /run/systemd/system)

Bug#836448: fcl: out of date binaries on armel/armhf

[Emilio Pozuelo Monfort]

Source: fcl
Version: 0.5.0-2
Severity: serious

Your package no longer builds on armel/armhf because it build-depends
on liboctomap-dev, which is unavailable there. You should either get
it built there somehow (e.g. by disabling that b-d there if possible)
or by getting your package removed from those architectures by filing
a bug against ftp.debian.org.

Emilio

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

Kernel: Linux 4.6.0-1-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: systemd (via /run/systemd/system)

Bug#796020: Bug#796497: reconsidering the removal of ruby-hpricot

[Axel Beckert]

Hi Antonio,

Antonio Terceiro wrote:
> On Tue, Aug 18, 2015 at 06:26:06PM +0200, Christian Hofstaedtler wrote:
> > We're not going to have ruby-hpricot in stretch.
> 
> ruby-hpricot has now only 2 reverse dependencies: ruby-ronn and
> ruby-fast-fs. However, the number of packages build-depending on
> ruby-ronn only grows, and is currently at 54¹

Noticed that, too, mostly because I'm partially guilty for that,
because I use ronn to generate unburden-home-dir's man page from
Markdown since 0.4, to be able to also provide the man page in the
online documentation as HTML.

> ruby-hpricot is indeed dead upstream, but so is a lot of software in
> Debian. Also, being dead upstream does not mean not being useful, or
> necessarily being broken.

Fully agree. Especially ronn does a real good job.

> So I think we should give up on removing ruby-hpricot until at least one
> of the following happen:
> 
> - ruby-ronn gets rewritten to not use ruby-hpricot (unlikely since ronn
>   is dead upstream itself)

Indeed:

* Last release June 2010: https://github.com/rtomayko/ronn/releases
* Last commit in August 2013: https://github.com/rtomayko/ronn/commits/master
* Last comment by author on issues or pull requests in August 2013:
  https://github.com/rtomayko/ronn/pull/77#issuecomment-22620549

> - something else can replace ruby-ronn and we manage to make reverse
>   (build) dependencies switch to it.

Before starting to use ronn in an official release of
unburden-home-dir, I tried different tools and was very unsatisfied:

* go-md2man
* pandoc

There is also https://github.com/sunaku/md2man which is not yet
packaged. Haven't tried that one yet since it requires a newer version
of rubygems (2.5.2) than in Debian Unstable (2.5.1):
https://github.com/sunaku/binman/issues/4

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

Bug#836327: gsequencer: FTBFS on mips and powerpc: ags_functional_audio_test segmentation fault

[Joël Krähemann]

Hi

Yesterday, I was providing an new tarball 0.7.63 making the tests
pass. ags_functional_audio_test.c needs your soundcard
but shouldn't crash if it's not available. Further there was an issue
with $(HOME)/.gsequencer/ags.conf having jack=enabled.
Since jack support is a work in progress it is not supported, yet. But
the new tarball should fix the NULL pointer access.

Bests,
Joël


On Thu, Sep 1, 2016 at 7:12 PM, Aaron M. Ucko  wrote:
> Source: gsequencer
> Version: 0.7.62-1
> Severity: serious
> Justification: fails to build from source (but built successfully in the past)
>
> The latest builds of gsequencer for mips and powerpc both failed
> because ags_functional_audio_test segfaulted:
>
> https://buildd.debian.org/status/fetch.php?pkg=gsequencer&arch=mips&ver=0.7.62-1&stamp=1472716604
> https://buildd.debian.org/status/fetch.php?pkg=gsequencer&arch=powerpc&ver=0.7.62-1&stamp=1472714618
>
> Could you please take a look?
>
> Thanks!
>

Bug#836326: gsequencer: FTBFS on i386: ags_channel_test segmentation fault

[Joël Krähemann]

Hi

Yesterday, I was providing a new tarball 0.7.63 fixing the unit tests.
They should all pass for now.

Bests,
Joël

On Thu, Sep 1, 2016 at 7:10 PM, Aaron M. Ucko  wrote:
> Source: gsequencer
> Version: 0.7.62-1
> Severity: serious
> Justification: fails to build from source (but built successfully in the past)
>
> The latest i386 build of gsequencer failed because ags_channel_test
> crashed.  Could you please take a look?
>
> Thanks!
>
>   PASS: ags_thread_test
>   PASS: ags_audio_test
>   ./test-driver: line 107:  9968 Segmentation fault  "$@" > $log_file 2>&1
>   FAIL: ags_channel_test
>   PASS: ags_recycling_test
>   PASS: ags_audio_signal_test
>   PASS: ags_recall_test
>   PASS: ags_pattern_test
>   PASS: ags_notation_test
>   PASS: ags_automation_test
>   PASS: ags_functional_audio_test
>   =
>  gsequencer 0.7.62: ./test-suite.log
>   =
>
>   # TOTAL: 10
>   # PASS:  9
>   # SKIP:  0
>   # XFAIL: 0
>   # FAIL:  1
>   # XPASS: 0
>   # ERROR: 0
>
>   .. contents:: :depth: 2
>
>   FAIL: ags_channel_test
>   ==
>
>
>
>CUnit - A unit testing framework for C - Version 2.1-3
>http://cunit.sourceforge.net/
>
>
>   Suite: AgsChannelTest
> Test: test of AgsChannel add recall ...passed
> Test: test of AgsChannel add recall container ...FAILED
>   1. ags/test/audio/ags_channel_test.c:131  - 
> g_list_find(channel->container, recall_container) != NULL
> Test: test of AgsChannel add recall id ...FAILED
>   1. ags/test/audio/ags_channel_test.c:148  - 
> g_list_find(channel->recall_id, recall_id) != NULL
> Test: test of AgsChannel add duplicate recall ...FAIL ags_channel_test 
> (exit status: 139)
>

Bug#826300: Share knowledge on fpc and powerpc issue

[peter green]

On 03/09/16 03:36, peter green wrote:

On 02/09/16 23:05, Abou Al Montacir wrote:

Upstream suggests the following patch which may be temporary:
diff --git a/rtl/linux/powerpc/cprt0.as b/rtl/linux/powerpc/cprt0.as
index e237d8d..a5672e3 100644
--- a/rtl/linux/powerpc/cprt0.as
+++ b/rtl/linux/powerpc/cprt0.as
@@ -88,12 +88,8 @@ main_stub:
  .globl  _haltproc
  .type   _haltproc, @function
  _haltproc:
-lis 11, ___fpc_ret@ha
-lwz 1, ___fpc_ret@l(11)
-addi1, 1, 16
-lwz 0, 0(1)
-mtlr0
-blr
+bl _exit
+b  _haltproc

  #li  0, 1   /* exit call */
  #lis 3,operatingsystem_result@h  
Apparent good news. With this patch and the hacks I previously 
mentioned for building in a jessie chroot I was able to get a 
successful build in a jessie chroot on the porterbox. I was then able 
to run the resulting fpcmkcfg-3.0.0 in the sid chroot on the porterbox.


I then installed the packages built in the jessie chroot on the 
porterbox into a sid chroot in qemu and attempted to build the packge 
with the patch above but without the jessie hacks.


That build is currently ongoing. If it succeeds I intend to upload it 
to Debian (as a "source all powerpc" upload).

This build succeeded, so I have uploaded it.

Can someone tell me what git workflow is being used so I can also push 
this to the git repo on alioth?

Processed: shogun: FTBFS with eigen3 3.3~beta2-1

[Debian Bug Tracking System]

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

> block 836444 by 835411
Bug #836444 [src:shogun] shogun: FTBFS with eigen3 3.3~beta2-1
836444 was not blocked by any bugs.
836444 was not blocking any bugs.
Added blocking bug(s) of 836444: 835411
> thanks
Stopping processing here.

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

Bug#836444: shogun: FTBFS with eigen3 3.3~beta2-1

[Graham Inggs]

Source: shogun
Version: 3.2.0-7.3
Severity: serious


Along with ceres-solver and opensurgsim, shogun FTBFS with eigen3
3.3~beta2-1, however they all build fine with 3.3~beta1-2.

Shogun also builds fine with eigen3 3.3~beta2-1 including the patch
mentioned by Philipp [1].

In both of the above cases I included the patch from #809290 [2].


[1] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=835411#36
[2] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=809290#12

Bug#832931: mariadb-10.0: FTBFS on powerpc

[Salvatore Bonaccorso]

Hi Otto,

On Sat, Sep 03, 2016 at 09:51:02AM +0300, Otto Kekäläinen wrote:
> The MariaDB 10.0.26 PowerPC build failure regression was identified
> and fixed in commit
> https://anonscm.debian.org/cgit/pkg-mysql/mariadb-10.0.git/commit/?id=de356c12d3ff73a20e65d1cd7756f3370208ccb2
> 
> This has been fixed also upstream and the new 10.0.27 should build OK
> on PowerPC. Now we just need to wait for somebody to publish a CVE
> regarding 10.0.27 so if qualitfies for security upload and this this
> issue can be closed...

Thanks for investigating the issue with upstream.

I think there are three options:

1/ We can afford to wait for the next DSA to fix the issue and leave
   powerpc users with the previous CVEs unfixed so far. With the next
   DSA then the fix is included and #832931 can be closed.
2/ We can release a regression update DSA, to fix the issue, since it
   was introduced with the last DSA, but this means users of other
   architectures will need to update twice, now again, and then later
   for a future DSA.
3/ Similar to 2/ but release an update to fix #832931 via the next
   Jessie point release, which will be soon (cf. [1]).

 [1] https://lists.debian.org/debian-release/2016/09/msg00025.html

Regards,
Salvatore


signature.asc
Description: PGP signature

Bug#835411: opensurgsim: FTBFS with eigen3 3.3~beta2-1

[Graham Inggs]

With eigen3 including upstream's patch mentioned by Philipp [1],
opensurgsim now builds and passes all 12 tests on ppc64el, but fails 1
test on amd64 and 3 tests on arm64.  I don't know if more work is
needed in the eigen3 patch or in opensurgsim.


[1] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=835411#36

Bug#835075: [PATCH] use fake-pinentry (Closes: #835075)

[gregor herrmann]

On Fri, 02 Sep 2016 10:49:23 -0400, Daniel Kahn Gillmor wrote:

Thanks for the patch!


I can confirm that it works but I still have some issues:

1) After the build finishes there are 6 instances of gpg-agent
  running. In my cowbuilder setup this doesn't cause any issues and
  they time out after some time (1 minute I guess).

2) autopkgtests initially failed with:

t/30.inline-decrypt.t  
1..5
ok 1 - An object of class 'MIME::Entity' isa 'MIME::Entity'
gpg: keybox 
'/tmp/autopkgtest.n6im1C/autopkgtest_tmp/smoke7NpYaR/mgtrYHsk/pubring.kbx' 
created
gpg: /tmp/autopkgtest.n6im1C/autopkgtest_tmp/smoke7NpYaR/mgtrYHsk/trustdb.gpg: 
trustdb created
gpg: key 49539D60EFEA4EAD marked as ultimately trusted
gpg: key 49539D60EFEA4EAD: public key "Mail::GnuPG Test Key " 
imported
gpg: key 49539D60EFEA4EAD/49539D60EFEA4EAD: error sending to agent: No pinentry
gpg: error building skey array: No pinentry
[..]

3) This is in schroot-on-lvm. And here unmounting fails because of the
   running gpg-agents leaving my schroot/lvm setup in a sad state.

4) I can fix 2) with debian/tests/pkg-perl/smoke-setup containing
   chmod a+x $TDIR/t/fake-pinentry.pl
   like in d/rules. Then the tests pass, but 3) still remains.
   (Cleaning up manually again now ...)


Alltogether I think we need to think a bit more about this gpg-agent
thing, currently this seems a bit too fragile to me.

Another question is if we could have a fake-pinentry in some central
place (gnupg binary package?) to be used from all packages instead of
adding it everywhere?


Thanks again for your work on this bug!


Cheers,
gregor

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


signature.asc
Description: Digital Signature

Bug#835730: marked as done (mercurial: FTBFS: Tests failures)

[Debian Bug Tracking System]

Your message dated Sat, 03 Sep 2016 07:48:44 +
with message-id 
and subject line Bug#835730: fixed in mercurial 3.9.1-1
has caused the Debian Bug report #835730,
regarding mercurial: FTBFS: Tests failures
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.)


-- 
835730: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=835730
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: mercurial
Version: 3.9-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):
> Skipped test-convert-tagsbranch-topology.t: missing feature: git command line 
> client
> Skipped test-mac-packages.t: missing feature: OS X packaging tools
> Skipped test-chg.t: missing feature: running with chg
> Skipped test-verify-repo-operations.py: missing feature: allow slow tests
> Skipped test-convert-bzr-merges.t: missing feature: Canonical's Bazaar client
> Skipped test-no-symlinks.t: system supports symbolic links
> Skipped test-docker-packaging.t: missing feature: docker support
> Skipped test-convert-bzr-ghosts.t: missing feature: Canonical's Bazaar client
> Skipped test-convert-bzr-114.t: missing feature: Canonical's Bazaar client >= 
> 1.14
> Skipped test-convert-bzr-treeroot.t: missing feature: Canonical's Bazaar 
> client
> Skipped test-debian-packages.t: missing feature: debian packaging tools
> Failed test-gpg.t: output changed
> # Ran 474 tests, 49 skipped, 0 warned, 1 failed.
> python hash seed: 3324319778
> # Cleaning up HGTMP /tmp/hgtests.fBryXH 
> Makefile:110: recipe for target 'tests' failed

The full build log is available from:
   http://people.debian.org/~lucas/logs/2016/08/28/mercurial_3.9-1_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: mercurial
Source-Version: 3.9.1-1

We believe that the bug you reported is fixed in the latest version of
mercurial, 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.
Javi Merino  (supplier of updated mercurial 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, 03 Sep 2016 09:04:00 +0300
Source: mercurial
Binary: mercurial-common mercurial
Architecture: source all amd64
Version: 3.9.1-1
Distribution: unstable
Urgency: medium
Maintainer: Python Applications Packaging Team 

Changed-By: Javi Merino 
Description:
 mercurial  - easy-to-use, scalable distributed version control system
 mercurial-common - easy-to-use, scalable distributed version control system 
(common
Closes: 835730
Changes:
 mercurial (3.9.1-1) unstable; urgency=medium
 .
   * New upstream release signed with a new gpg key
   * Fix "FTBFS: Tests failures" by fixing test-gpg.t's output to take into
 account gpg 2.1's messages when importing classic gpg keyring files.
 (Closes: #835730)
Checksums-Sha1:
 885365d06947720406291b534b45331792a3f47b 2378 mercurial_3.9.1-1.dsc
 6927932e144ad3dbf7677d1d0e12e1cd980a92f9 4797967 mercurial_3.9.1.orig.tar.gz
 e452db5b7161e2671112f941386322d662918c39 95404 mercurial_3.9.1-1.debian.tar.xz
 d29a05e8002af57c5588f8625bd3bc511f0375b5 1931874 
mercurial-common_3.9.1-1_all.deb
 4d1ae06cd01c198981c6f2103028d5c48f2d6a25 167130 
mercurial-dbgsym_3.9.1-1_amd64.deb
 399748a99438d5e21636c734deadfd464614833e 74808 mercurial_3.9.1-1_amd64.deb
Checksums-Sha256:
 bd9e31db3a3b9a7803b2227d43ace6e7130a58bbfc9a5d749bd85e7b13addde6 2378 
mercurial_3.9.1-1.dsc
 625e4fc7e85ec2278c2828bdc547fce74091b3bbe4d9eeeba2d61af51195df74 4797967 
mercurial_3.9.1.orig.tar.gz
 baf6e83cc8918b0842d52fad6ac85d2f261b19aa4521a539cd275949d02b98b9 95404 
mercurial_3.9.1-1.debian.tar.xz
 62e92d9e0bd81f09e0e

Bug#835250: marked as done (FTBFS against pytest 3.0.0)

[Debian Bug Tracking System]

Your message dated Sat, 03 Sep 2016 07:19:00 +
with message-id 
and subject line Bug#835250: fixed in sqlobject 3.1.0+dfsg-1
has caused the Debian Bug report #835250,
regarding FTBFS against pytest 3.0.0
to be marked as done.

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

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


-- 
835250: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=835250
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: sqlobject
Version: 3.0.0+dfsg-2
Severity: important
Tags: sid stretch
Usertags: pytest3.0.0

During a test build with pytest 3.0.0 from experimental sqlobject failed to
build:
| === FAILURES 
===
|  test_deep_inheritance 
_
|
| def test_deep_inheritance():
| setupClass([DIManager, DIEmployee, DIPerson])
| 
| manager = DIManager(firstName='Project', lastName='Manager',
| >   position='Project Manager')
|
| ../../../sqlobject/inheritance/tests/test_deep_inheritance.py:78: 
| _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 
_ 
| ../../../sqlobject/main.py:1301: in __init__
| self._create(id, **kw)
| ../../../sqlobject/inheritance/__init__.py:406: in _create
| connection=self._connection)
| ../../../sqlobject/main.py:1301: in __init__
| self._create(id, **kw)
| ../../../sqlobject/inheritance/__init__.py:413: in _create
| super(InheritableSQLObject, self)._create(id, **kw)
| ../../../sqlobject/main.py:1352: in _create
| self._SO_finishCreate(id)
| ../../../sqlobject/main.py:1378: in _SO_finishCreate
| id, names, values)
| ../../../sqlobject/dbconnection.py:494: in queryInsertID
| names, values)
| ../../../sqlobject/dbconnection.py:348: in _runWithConnection
| val = meth(conn, *args)
| ../../../sqlobject/sqlite/sqliteconnection.py:257: in _queryInsertID
| self._executeRetry(conn, c, q)
| _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 
_ 
|
| self = 
| conn = 
| cursor = 
| query = "INSERT INTO di_employee (id, position, child_name) VALUES (3, 
'Project Manager', 'DIManager')"
|
| def _executeRetry(self, conn, cursor, query):
| if self.debug:
| self.printDebug(conn, query, 'QueryR')
| try:
| return cursor.execute(query)
| except self.module.OperationalError as e:
| raise dberrors.OperationalError(ErrorMessage(e))
| except self.module.IntegrityError as e:
| msg = ErrorMessage(e)
| if msg.startswith('column') and msg.endswith('not unique') \
| or msg.startswith('UNIQUE constraint failed:'):
| >   raise dberrors.DuplicateEntryError(msg)
| E   DuplicateEntryError: UNIQUE constraint failed: 
di_employee.position

Please see
https://people.debian.org/~sramacher/logs/pytest3.0.0/sqlobject_amd64.log for a
full log.

Cheers
-- 
Sebastian Ramacher


signature.asc
Description: PGP signature
--- End Message ---
--- Begin Message ---
Source: sqlobject
Source-Version: 3.1.0+dfsg-1

We believe that the bug you reported is fixed in the latest version of
sqlobject, 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.
Neil Muller  (supplier of updated sqlobject 
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: Sat, 03 Sep 2016 09:01:56 +0200
Source: sqlobject
Binary: python-sqlobject python3-sqlobject python-sqlobject-doc sqlobject-admin
Architecture: source
Version: 3.1.0+dfsg-1
Distribution: unstable
Urgency: low
Maintainer: Debian Python Modules Team 

Changed-By: Neil Muller 
Description:
 python-sqlobject - Python 2 object relational manager providing an object 
interface
 python-sqlobject-doc - Documentation for SQLObject, a Python object relational 
manager f
 python3-sqlobject - Python 3 object relational manager providing an object 
interface
 sqlobject-admin - Helper applications for SQLObject, a Python ORM for databases
Closes: 835250
Changes:
 sqlobject (3.1.0+dfsg-1) unstable; urgency=low
 

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

[Sandro Knauß]

Control: usertags -1 fixed-upstream

Hey,

Fix is upstream:

kdepim [Applications/16.08 f68b21d] Akregator keep crashing at exit
akregator [master 36c7fe5] Akregator keep crashing at exit

(upstream had switched repos, so stable and master needs to be applied two 
times)

Regards,

sandro

--
Am Freitag, 2. September 2016, 14:13:31 CEST schrieb Maximiliano Curia:
> Control: tag -1 + pending
> 
> ¡Hola Sandro!
> 
> El 2016-09-02 a las 08:51 +0200, Sandro Knauß escribió:
> > Control: tags -1 +patch
> > 
> > thanks, for the backtrace. This helps to track this down.
> > 
> > I can reproduce this, but currently I can't test the patch for it. But
> > this
> > only happens if akregator is started as single application. My normal way
> > to use akregator is via kontact and this way it does not crash.
> > 
> > I looks that we have to test the partenNode if this is a valid
> > pointer.Akregator::SubscriptionListModel::index
> > 
> > Akregator::SubscriptionListModel::index
> > 
> > add this add line 248:
> >if (!parentNode) {
> >
> >return QModelIndex();
> >
> >}
> 
> Oh, I had came up with the same patch. :)
> I could finally test this, and the patch fixes the segfault. Could you push
> this upstream (for 16.08.1, I guess)?
> 
> Happy hacking



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