Bug#804567: marked as done (libaccounts-glib: FTBFS on s390x)

[Debian Bug Tracking System]

Your message dated Sun, 20 Dec 2015 23:48:17 +
with message-id 
and subject line Bug#804567: fixed in libaccounts-glib 1.18+20150112-2
has caused the Debian Bug report #804567,
regarding libaccounts-glib: FTBFS on s390x
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.)


-- 
804567: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=804567
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: libaccounts-glib
Version: 1.18+20150112-1
Severity: serious

Your package failed to build on s390x. Normally this wouldn't be RC as
this package has never built on that architecture. However,
ktp-common-internals needs this (through libaccounts-qt) to build there.

Log at
https://buildd.debian.org/status/fetch.php?pkg=libaccounts-glib=s390x=1.18%2B20150112-1=1447063649

Cheers,
Emilio
--- End Message ---
--- Begin Message ---
Source: libaccounts-glib
Source-Version: 1.18+20150112-2

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

Debian distribution maintenance software
pp.
Diane Trout  (supplier of updated libaccounts-glib package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Sun, 20 Dec 2015 14:43:13 -0800
Source: libaccounts-glib
Binary: libaccounts-glib-dev libaccounts-glib-dbg libaccounts-glib0 
gir1.2-accounts-1.0 libaccounts-glib-doc libaccounts-glib-tools
Architecture: source
Version: 1.18+20150112-2
Distribution: unstable
Urgency: medium
Maintainer: Debian/Kubuntu Qt/KDE Maintainers 
Changed-By: Diane Trout 
Description:
 gir1.2-accounts-1.0 - typelib file for libaccounts-glib0
 libaccounts-glib-dbg - Accounts database access - debug files
 libaccounts-glib-dev - Accounts database access - development files
 libaccounts-glib-doc - Accounts database access - documentation
 libaccounts-glib-tools - Accounts database access - tools
 libaccounts-glib0 - Accounts database access - shared library
Closes: 804567
Changes:
 libaccounts-glib (1.18+20150112-2) unstable; urgency=medium
 .
   * Add disable-deprecation-errors.patch to work around glib API change
   * Add fix-endianness-issues.patch to build on s390x (Closes: #804567)
Checksums-Sha1:
 b68fa2c0563d81d55b88e3194fffb9f71449d017 2827 
libaccounts-glib_1.18+20150112-2.dsc
 2abb8317e2e590856294e48ba6cb3308f0381787 8948 
libaccounts-glib_1.18+20150112-2.debian.tar.xz
Checksums-Sha256:
 8cb8c635b42880f26a0ef7f20faca68f9f672550645feeea62d70ae330294cca 2827 
libaccounts-glib_1.18+20150112-2.dsc
 b5c13c094f2e1f2107cecdb43fae5cd67ec7ea8c73e943b0c0fcceb1f4f44341 8948 
libaccounts-glib_1.18+20150112-2.debian.tar.xz
Files:
 0dd3034952270eb9dd487b61888798a1 2827 libs optional 
libaccounts-glib_1.18+20150112-2.dsc
 ffca7b5e1027fc01d59055fb092af0c7 8948 libs optional 
libaccounts-glib_1.18+20150112-2.debian.tar.xz

-BEGIN PGP SIGNATURE-
Version: GnuPG v1

iQIcBAEBCgAGBQJWdzGXAAoJEJkNODZzNNdwU/IP/3cKnTRFeg4SmlKEO+oDrxE/
lRgC5rKsNCQAe87cZtHfhTU3zlcCUituXUVGr/5eXIZUcJiJJltNa1lo5Lw6oVM7
eVNG7dXF43LR1DGcDCSBkaOs+/eg9xx94VZcfZebVrnuwNH0/vsJWhVZzUbuBMFz
TTS8KZ2I02+8INUPx+ey5zrGYkltrAc2wbXhzz+YtqyniVJpcMdwMdmjo7zK5wB4
2Wxiw7qdMyYw/PjwW0NJ+BApt4MG6eQKGsZjR8mlUUIL16//ys0YfThWuWDLgkpy
ilVJx96/9kHjXlQVs1WpxAbPQ31J8reAd1q1CWpQGiPdXVNuWPAz0d0Tg5YAliMN
ChbS0bNJXcor197vtHOsHcp66B4B1TslfPpVreltj2ZBhBrWJBO29uVM1EPbk5Iv
CbfwGDMDWJSCYLme4EN8BfvfIaeBYR61tX6MVelSPDlO4tYTDqIGBAywDVxy4a31
qJkFkIw7yAm/kBvjXdNApL7TgJoGIve4QRHnx7azjEA7QQNvNbqg9TxrrpG4k5hp
JwQQY9xs6HapCnD0nlDuGj7EivQeblsFc1sv54fK/v4kev5WUQQ1pv7xShbSH0jY
0eY8gQk1jnwPnHun51UTH92mxv7ImvX+9cSaaDMGauElrjHhxHlToVrPguwKGPAK
DRosV/A/o5lnmijVt7ET
=3O38
-END PGP SIGNATURE End Message ---

Bug#808189: marked as done (html2wml: Depends on virtual package "perl5" which will is gone with perl/5.22)

[Debian Bug Tracking System]

Your message dated Mon, 21 Dec 2015 00:27:15 +
with message-id 
and subject line Bug#808189: fixed in html2wml 0.4.11-1.1
has caused the Debian Bug report #808189,
regarding html2wml: Depends on virtual package "perl5" which will is gone with 
perl/5.22
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.)


-- 
808189: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=808189
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: html2wml
Version: 0.4.11-1
Severity: serious
Control: tags -1 + patch

Dear Werner,

the Perl 5.22 transition just started (see
https://lists.debian.org/debian-devel-announce/2015/12/msg5.html)
and we seem to have missed that html2wml depends on the deprecated
virtual package "perl5" like some other packages did.

The virtual package "perl5" is provided by the 5.20 perl package as
present in Debian Unstable until just now, but is no more be provided by
the 5.22 perl package which was just uploaded.

The following patch fixes this issue:

diff -u html2wml-0.4.11/debian/control html2wml-0.4.11/debian/control
--- html2wml-0.4.11/debian/control
+++ html2wml-0.4.11/debian/control
@@ -7,7 +7,7 @@
 
 Package: html2wml
 Architecture: all
-Depends: perl5, libhtml-parser-perl, liburi-perl, libwww-perl, 
libtext-template-perl
+Depends: perl, libhtml-parser-perl, liburi-perl, libwww-perl, 
libtext-template-perl
 Recommends: libxml-parser-perl, tidy, httpd | httpd-cgi
 Suggests: wap-wml-tools, iceweasel, wapua
 Description: converts HTML pages to WML (WAP) or i-mode pages

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

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

Versions of packages html2wml depends on:
ii  libhtml-parser-perl3.71-2
ii  libtext-template-perl  1.46-1
ii  liburi-perl1.69-1
ii  libwww-perl6.15-1
ii  perl [perl5]   5.20.2-6

Versions of packages html2wml recommends:
pn  httpd | httpd-cgi   
ii  libxml-parser-perl  2.44-1
ii  tidy20091223cvs-1.5

Versions of packages html2wml suggests:
ii  iceweasel  38.5.0esr-1
ii  wap-wml-tools  0.0.4-7
ii  wapua  0.06.1-3

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

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

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

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

Debian distribution maintenance software
pp.
Axel Beckert  (supplier of updated html2wml package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Sat, 19 Dec 2015 00:36:01 +0100
Source: html2wml
Binary: html2wml
Architecture: source all
Version: 0.4.11-1.1
Distribution: unstable
Urgency: high
Maintainer: Werner Heuser 
Changed-By: Axel Beckert 
Description:
 html2wml   - converts HTML pages to WML (WAP) or i-mode pages
Closes: 808189
Changes:
 html2wml (0.4.11-1.1) unstable; urgency=high
 .
   * Non-maintainer upload
   * Replace dependency on "perl5" with just "perl". (Closes: #808189)
Checksums-Sha1:
 7ab209bdc2db6a4baa0be23d4c755b6304eb2dfe 1633 html2wml_0.4.11-1.1.dsc
 26a120a26dc1f476f90c513c000a7a1b4253b376 3200 html2wml_0.4.11-1.1.diff.gz
 c20ef4fb6303faeaf560334dcba476011bcfba92 88550 html2wml_0.4.11-1.1_all.deb
Checksums-Sha256:
 fc0158a4e6d4062fdb909ceb01c2ded784e9e096487581760bc19054213ed514 1633 
html2wml_0.4.11-1.1.dsc
 9989944c0277bd81c63124a3ca25431fa0a59829433266924bba975b4b5dd418 3200 
html2wml_0.4.11-1.1.diff.gz
 270ffd64f382dfa45932f3c7cdb3720f39533780415625eb15ba0a2952b492c6 88550 
html2wml_0.4.11-1.1_all.deb
Files:
 785da4adf71e0186fc902ca0502fee5f 1633 web optional html2wml_0.4.11-1.1.dsc
 f15a784304121497c4926b8177d35468 3200 web optional html2wml_0.4.11-1.1.diff.gz
 

Bug#808488: marked as done (brutalchess: FTBFS: fatal error: freetype2/freetype.h: No such file or directory)

[Debian Bug Tracking System]

Your message dated Mon, 21 Dec 2015 00:53:20 +
with message-id 
and subject line Bug#808488: fixed in brutalchess 0.5.2+dfsg-7
has caused the Debian Bug report #808488,
regarding brutalchess: FTBFS: fatal error: freetype2/freetype.h: No such file 
or directory
to be marked as done.

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

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


-- 
808488: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=808488
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: brutalchess
Version: 0.5.2+dfsg-6
Severity: serious
Justification: fails to build from source
Tags: sid stretch
User: reproducible-bui...@lists.alioth.debian.org
Usertags: ftbfs
X-Debbugs-CC: reproducible-bui...@lists.alioth.debian.org

Dear Maintainer,

The package fails to build:

g++ -DHAVE_CONFIG_H -I. -DPREFIX_DIR=\"/usr/share/games/brutalchess/\" 
-DMODELS_DIR=\"/usr/share/games/brutalchess//models/\" 
-DART_DIR=\"/usr/share/games/brutalchess//art/\" -DFONTS_DIR=\"\"  
-D_FORTIFY_SOURCE=2  -g -O2 -fPIE -fstack-protector-strong -Wformat 
-Werror=format-security  -I/usr/include/SDL -D_GNU_SOURCE=1 -D_REENTRANT 
-I/usr/include/freetype2 -c -o brutalchess.o brutalchess.cpp
In file included from brutalchess.cpp:26:0:
fontloader.h:16:32: fatal error: freetype2/freetype.h: No such file or directory
compilation terminated.
Makefile:546: recipe for target 'brutalchess.o' failed
make[3]: *** [brutalchess.o] Error 1
make[3]: Leaving directory '/brutalchess-0.5.2+dfsg/src'
Makefile:355: recipe for target 'all' failed

Full build log:
https://reproducible.debian.net/rb-pkg/unstable/amd64/brutalchess.html

-- System Information:
Debian Release: stretch/sid
APT prefers unstable
APT policy: (500, 'unstable')
Architecture: amd64 (x86_64)
--- End Message ---
--- Begin Message ---
Source: brutalchess
Source-Version: 0.5.2+dfsg-7

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

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

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Mon, 21 Dec 2015 00:43:32 +0100
Source: brutalchess
Binary: brutalchess
Architecture: source
Version: 0.5.2+dfsg-7
Distribution: unstable
Urgency: medium
Maintainer: Debian Games Team 
Changed-By: Markus Koschany 
Description:
 brutalchess - 3D chess game with reflection of the chessmen
Closes: 808488
Changes:
 brutalchess (0.5.2+dfsg-7) unstable; urgency=medium
 .
   * Team upload.
   * Drop FreeType.patch. Apparently src:freetype has reverted the changes from
 earlier versions and the path to freetype.h had to be adjusted again.
 Thanks to Chris West for the report. (Closes: #808488)
Checksums-Sha1:
 a5e0a92dde1d2b13c5fb6093f455ff82e588ebcd 2255 brutalchess_0.5.2+dfsg-7.dsc
 487a2c9dc3fe462042eb9e87208ddd411eef20e1 6924 
brutalchess_0.5.2+dfsg-7.debian.tar.xz
Checksums-Sha256:
 8bb734aeb61cd3aeed65053254865037decbaec177bdbb411aaa28fe76b0d638 2255 
brutalchess_0.5.2+dfsg-7.dsc
 e1da252c249492744cbe51bbe4a4e7d38426dc1202b4830ac9294408f4e21ae1 6924 
brutalchess_0.5.2+dfsg-7.debian.tar.xz
Files:
 7cedb08248a851500069d4c785a6f9f2 2255 games optional 
brutalchess_0.5.2+dfsg-7.dsc
 1c5d549711f1f6a496e0f59e70477c21 6924 games optional 
brutalchess_0.5.2+dfsg-7.debian.tar.xz

-BEGIN PGP SIGNATURE-
Version: GnuPG v1

iQJ8BAEBCgBmBQJWdz7XXxSAAC4AKGlzc3Vlci1mcHJAbm90YXRpb25zLm9w
ZW5wZ3AuZmlmdGhob3JzZW1hbi5uZXRBQ0YzRDA4OEVGMzJFREVGNkExQTgzNUZE
OUFEMTRCOTUxM0I1MUU0AAoJENmtFLlRO1Hk4nEP/3VnC5cp++cQsE+Jyt8lfAPh
q6oe2UG/Q80N6lJYr9/T+gsnQYuOgXW8cvfKvxlNCT0xRhrfAHnr4cgdO3jmIGHF
i0ELj8VS5I08qN8jEKO8/RRc5tEVIIpmPPPlQePVIlrBibNW2UHn+dNavhYqA7ZK
wGx3LhlqYNhelgQ8+WOVM37tA6BJYmaWAt/gzoJ6xu7x9+mbX2o51KH6sBsLmd84
ppP6saV+/tb+5X26tLVtollSFQgZTc8wUTE3++1glPkgDKWhl1RH0t4nxFEHDbnc
SfiFrfVro6luYidV1VJybD7fDL3zuD+5+MzywSPymqytSt122OvGq4Xm2LhyKgyp
RMuyVhfDooWXx7e3oJOAVocR+hYS+Lsu573mCfezibZ5+m3iLO18NnZTAmI1zVsZ
pPunbKoazdBflmaolG+KMa1nv7EskKzypYY5EkKgR3gIkN0jFj6MYOmWLxR2EsvE

Processed: severity of 808563 is grave

[Debian Bug Tracking System]

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

> severity 808563 grave
Bug #808563 [src:linux] Boot with 4.3: SATA errors. Returning to 4.2: no errors
Severity set to 'grave' from 'important'
> thanks
Stopping processing here.

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

Bug#799778: digikam: Not able to import pictures from CANON EOS350D after upgrading from 3.5

[Steve M. Robbins]

On Tue, 22 Sep 2015 15:34:20 +0200 Etienne BRETTEVILLE 
 wrote:

> After upgrading from LinuxMintDebianEdition LMDE 1 (based on debian 7) to 
LMDE2
> based on debian Jessie, digikam has been updated to 4.4.0 instead of 3.5.x.
> 
> Since then I'm no longer able to import my pictures from my CanonEOS350D 
using
> the importation tool from digikam.
> 
> You can see the error message in the screenshot here:
> https://framapic.org/AiUtTFceoQN0/lexIQ4R7
> 
> What about introducing the latest revsion of digikam, 4.13.0?!

I just uploaded 4.14 today.  If you are in a position to try that out, I'd be 
very glad to know if it fixes this issue.

If not, then as a work-around: I wonder if you can set the camera to act as a 
USB device and import from the filesystem?

Finally, while I realize this makes digikam unusable for you, the  bug 
severity "grave" is intended for a package completely unusable by most users.  
I don't believe it applies in this case.

Best,
-Steve



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

Processed: severity of 799778 is normal

[Debian Bug Tracking System]

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

> severity 799778 normal
Bug #799778 [digikam] digikam: Not able to import pictures from CANON EOS350D 
after upgrading from 3.5
Severity set to 'normal' from 'grave'
> thanks
Stopping processing here.

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

Bug#802121: marked as pending

[Josue Ortega]

tag 802121 pending
thanks

Hello,

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


http://git.debian.org/?p=python-modules/packages/pysvn.git;a=commitdiff;h=edc97fc

---
commit edc97fc6aec0e9fc94fd89ff9e12383acc2e94d8
Author: Josue Ortega 
Date:   Sun Dec 20 17:10:29 2015 -0600

Removed python3 package version

diff --git a/debian/changelog b/debian/changelog
index 5c0bd01..e96a3d2 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,17 +1,13 @@
 pysvn (1.8.0-1) UNRELEASED; urgency=medium
 
-  * New upstream release:
+  * New upstream release (Closes: #802121):
  - debian/patches/* updated to be compatible with the new upstream release.
   * debian/control:
  - Dependencies version updated.
  - set Standards-Version: 3.9.6 no changes required.
- - Bumped X-Python3-Version to 3.5.
   * debian/copyright:
  - Updated BSD license tag name to BSD-4-clause.
- - Paragraphs reordered.
-  * Added Python 3 version of the package.
-  * debian/rules: Removed override_dh_installdocs in order to avoid
-documentation conflicts between the Python 3 and Python 2 package.
+ - Paragraphs have been reordered.
 
  -- Josue Ortega   Sun, 01 Nov 2015 18:52:15 -0600
 

Processed: Bug#802121 marked as pending

[Debian Bug Tracking System]

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

> tag 802121 pending
Bug #802121 [src:pysvn] pysvn: FTBFS: error: ‘svn_sort__hash’ was not declared 
in this scope
Added tag(s) pending.
> thanks
Stopping processing here.

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

Bug#808320: Proposed fix with breaks / replaces

[Gianfranco Costamagna]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Hi,

> +Replaces: libarrayfire-cpu-dev (<< 3.2.1+dfsg1-6) +Breaks:
> libarrayfire-cpu-dev (<< 3.2.1+dfsg1-6)

please check this wiky, that should have the most common use-cases
https://wiki.debian.org/PackageTransition

cheers,

G.
-BEGIN PGP SIGNATURE-
Version: GnuPG v1

iQIcBAEBCAAGBQJWd3sxAAoJEPNPCXROn13ZH3gP/0STTxRv6pNCQQpxdOKsgJgk
ClQUDbE8hdzKDIAFLCXgWnv1Hxq8GO0Z5xkAQoCAefzZd4hv2Q6ZaBb3v2K8OE/c
SVhkvRjr8JpZqbmCHeyk7wAmyrDHjhuofJge9M4NOOCuOLeac5lh8Fwo/O6i8bnN
MvqdYxWsyj218FKmOTZ55a/fR3HQ2yqiLXYBa+yNm0hdT0PF4eiOcgYDzR0oewtD
nIJAkkBOlRiw8tyLoJbn1UAd8nIughA651Xc/A+TSPpDtufUJdEbTdSORJyAiCYC
xXMxtZypZ1gHEdTthul+L3rcIjtgyUm6a1+slG2c76s39/nUuJgxDfpBtHkQNb//
lkxKSAEkIpyimNEw5PcItj1vrsNtFG1nwlTE3uqoSyzP1RNXRbsv6I7b0MQW/7eB
ORjL2vbFArgWlIdV8bMBL3fJaSFSpDX9kqZw4f99vTiomUPfGj9ZLZjyvg5vzAHb
Ds62w8dZAgS+BuTE7Og0LD//aJHn3s9D+l/QltAkNP5bl2OqO9Ku3F8y2ftcNLGG
9W+2HjdiXqnf8f8p1TIsI0ewhXFwJ/4QKlxQNEgMmip8iW7OxCZ9BuHa9MX0EujD
ucyR1BcXdgZsjDR8arG7J6MHPDwD+b70zv/qRwBsoB7pnq7qy2qyou0zs5jTUGqp
RUylV5wcr/oTA/o4dHAb
=xGg2
-END PGP SIGNATURE-

Bug#808573: network-manager: undefined symbol: g_udev_enumerator_new

[Mike Dupont]

Subject: network-manager: undefined symbol: g_udev_enumerator_new
Package: network-manager
Version: 1.0.8-2
Justification: renders package unusable
Severity: grave

Job for NetworkManager.service failed because the control process
exited with error code. See "systemctl status NetworkManager.service"
and "journalctl -xe" for details.


● NetworkManager.service - Network Manager
   Loaded: loaded (/lib/systemd/system/NetworkManager.service;
enabled; vendor preset: enabled)
   Active: failed (Result: start-limit) since Sun 2015-12-20 23:03:04
CST; 4min 30s ago
  Process: 17718 ExecStart=/usr/sbin/NetworkManager --no-daemon
(code=exited, status=127)
 Main PID: 17718 (code=exited, status=127)

/usr/sbin/NetworkManager --no-daemon
/usr/sbin/NetworkManager: symbol lookup error:
/usr/sbin/NetworkManager: undefined symbol: g_udev_enumerator_new



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

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

Versions of packages network-manager depends on:
ii  adduser3.113+nmu3
ii  dbus   1.10.2-1
ii  init-system-helpers1.24
ii  isc-dhcp-client4.3.3-5
ii  libbluetooth3  5.36-1
ii  libc6  2.19-22
ii  libdbus-1-31.10.2-1
ii  libdbus-glib-1-2   0.102-1
ii  libglib2.0-0   2.46.1-2
ii  libgnutls-deb0-28  3.3.18-1
ii  libgudev-1.0-0 1:162-2.2
ii  libmm-glib01.0.0-4
ii  libndp01.4-2
ii  libnewt0.520.52.18-1+b1
ii  libnl-3-2003.2.26-1
ii  libnl-genl-3-200   3.2.26-1
ii  libnl-route-3-200  3.2.26-1
ii  libnm0 1.0.6-1
ii  libpam-systemd 227-2
ii  libpolkit-agent-1-00.105-13
ii  libpolkit-gobject-1-0  0.105-13
ii  libreadline6   6.3-8+b3
ii  libsoup2.4-1   2.52.1-1
ii  libsystemd0227-2
ii  libteamdctl0   1.18-1
ii  libuuid1   2.27.1-1
ii  lsb-base   9.20150917
ii  policykit-10.105-13
ii  udev   227-2
ii  wpasupplicant  2.3-2

Versions of packages network-manager recommends:
ii  crda3.13-1
ii  dnsmasq-base2.75-1
ii  iptables1.4.21-2+b1
ii  iputils-arping  3:20121221-5+b2
ii  modemmanager1.0.0-4
ii  ppp 2.4.7-1+1

Versions of packages network-manager suggests:
ii  avahi-autoipd  0.6.32~rc+dfsg-1
pn  libteam-utils  

-- no debconf information


-- 
James Michael DuPont

Bug#808494: marked as done (junit4: FTBFS: Plugin com.google.code.maven-replacer-plugin:replacer:1.5.3 or one of its dependencies could not be resolved)

[Debian Bug Tracking System]

Your message dated Sun, 20 Dec 2015 22:46:01 +
with message-id 
and subject line Bug#808494: fixed in junit4 4.12-3
has caused the Debian Bug report #808494,
regarding junit4: FTBFS: Plugin 
com.google.code.maven-replacer-plugin:replacer:1.5.3 or one of its dependencies 
could not be resolved
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.)


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

Dear Maintainer,

The package fails to build:

cd . && /usr/lib/jvm/default-java/bin/java -noverify -cp 
/usr/share/maven/boot/plexus-classworlds-2.x.jar:/usr/lib/jvm/default-java/lib/tools.jar
  -Dclassworlds.conf=/etc/maven/m2-debian.conf -Dmaven.home=/usr/share/maven 
-Dmaven.multiModuleProjectDirectory=/junit4-4.12 
org.codehaus.plexus.classworlds.launcher.Launcher 
-s/etc/maven/settings-debian.xml 
-Dmaven.repo.local=/junit4-4.12/debian/maven-repo  package -DskipTests
[INFO] Scanning for projects...
[INFO] 
[INFO] 
[INFO] Building JUnit 4.12
[INFO] 
[INFO] 
[INFO] --- maven-enforcer-plugin:1.0:enforce (enforce-versions) @ junit ---
[INFO] 
[INFO] --- replacer:1.5.3:replace (default) @ junit ---
[INFO] 
[INFO] BUILD FAILURE
[INFO] 
[INFO] Total time: 0.589 s
[INFO] Finished at: 2015-12-20T14:00:33+00:00
[INFO] Final Memory: 8M/360M
[INFO] 
[ERROR] Failed to execute goal 
com.google.code.maven-replacer-plugin:replacer:1.5.3:replace (default) on 
project junit: Execution default of goal 
com.google.code.maven-replacer-plugin:replacer:1.5.3:replace failed: Plugin 
com.google.code.maven-replacer-plugin:replacer:1.5.3 or one of its dependencies 
could not be resolved: Cannot access central 
(https://repo.maven.apache.org/maven2) in offline mode and the artifact 
org.codehaus.plexus:plexus-utils:jar:1.1 has not been downloaded from it 
before. -> [Help 1]
[ERROR] 
[ERROR] To see the full stack trace of the errors, re-run Maven with the -e 
switch.
[ERROR] Re-run Maven using the -X switch to enable full debug logging.
[ERROR] 
[ERROR] For more information about the errors and possible solutions, please 
read the following articles:
[ERROR] [Help 1] 
http://cwiki.apache.org/confluence/display/MAVEN/PluginResolutionException
/usr/share/cdbs/1/class/maven.mk:92: recipe for target 'mvn-build' failed
make: *** [mvn-build] Error 1
dpkg-buildpackage: error: debian/rules build gave error exit status 2

Full build log:
https://reproducible.debian.net/rb-pkg/unstable/amd64/junit4.html

-- System Information:
Debian Release: stretch/sid
APT prefers unstable
APT policy: (500, 'unstable')
Architecture: amd64 (x86_64)
--- End Message ---
--- Begin Message ---
Source: junit4
Source-Version: 4.12-3

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

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

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Sun, 20 Dec 2015 21:57:58 +0100
Source: junit4
Binary: junit4 junit4-doc
Architecture: source all
Version: 4.12-3
Distribution: unstable
Urgency: medium
Maintainer: Debian Java Maintainers 

Changed-By: Markus Koschany 
Description:
 junit4 - JUnit regression test framework for Java
 junit4-doc - JUnit regression test framework for 

Bug#808395: marked as done (libprelude: FTBFS everywhere)

[Debian Bug Tracking System]

Your message dated Sun, 20 Dec 2015 22:46:43 +
with message-id 
and subject line Bug#808395: fixed in libprelude 1.0.0-11.7
has caused the Debian Bug report #808395,
regarding libprelude: FTBFS everywhere
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.)


-- 
808395: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=808395
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: libprelude
Version: 1.0.0-11.6
Severity: serious
Tags: sid stretch
Justification: fails to build from source (but built successfully in the past)
User: debian-p...@lists.debian.org
Usertags: perl-5.22-transition

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

During the perl 5.22 transition it was detected that this package
fails to build on all architectures:

https://buildd.debian.org/status/logs.php?pkg=libprelude=1.0.0-11.6%2Bb1

with:

make[5]: Entering directory '/«PKGBUILDDIR»/bindings'
/usr/bin/swig -c++ -I../bindings -I../bindings/c++/include -I../src/include 
-I../src/libprelude-error -perl5 -o perl/PreludeEasy.cxx libpreludecpp.i
perl/libpreludecpp-perl.i:1: Error: Unknown SWIG preprocessor directive: 
Exception (if this is a block of target language code, delimit it with %{ and 
%})
perl/libpreludecpp-perl.i:7: Error: Unknown SWIG preprocessor directive: 
Conversion (if this is a block of target language code, delimit it with %{ and 
%})
Makefile:1530: recipe for target 'perl/PreludeEasy.cxx' failed
make[5]: *** [perl/PreludeEasy.cxx] Error 1
make[5]: Leaving directory '/«PKGBUILDDIR»/bindings'


I can reproduce this failre locally (sid amd64 cowbuilder).


Cheers,
gregor


-BEGIN PGP SIGNATURE-
Version: GnuPG v1

iQJ8BAEBCgBmBQJWdWZuXxSAAC4AKGlzc3Vlci1mcHJAbm90YXRpb25zLm9w
ZW5wZ3AuZmlmdGhob3JzZW1hbi5uZXREMUUxMzE2RTkzQTc2MEE4MTA0RDg1RkFC
QjNBNjgwMTg2NDlBQTA2AAoJELs6aAGGSaoGaooQAJbNcXZ973tbVYoo9giqj9yI
pP2+uqK9RH8TN9C0MKNIYy2dDQx6k6ID7R90bAOB7vOtnovBw/Lzs7RUtC7LBBwy
uo+sx4QnGobaWMFpbxpJsGZDFlj3rZgIum6Gwh0ZlPXChXPoSo09He0A8UE0Hcri
/ofgcU13MyqAhAEmtRYkr7nSNZcuAJTLlHULc8ERkYZsp6HeNAz81cnsnnnN+Dpg
n9j94CbLMsL/eP2fUucGYmvra9/4X7baJYgOCA+eylMQM98VtkXPZdaW5Xw2Bfci
kXc2/d31QJUte+RnviJRI6HM/FsjNm1TsltQAlOLO8XoxcioKu6Zn8EbZMMEX2eh
F6oD4Fwjt4FnfF/gRDkjRDu/LaUdczrUoEutMD6X+IBTuhQJuzjGKo/sRVpmLqdT
tBlvxEND65F3G0BV02KtaUpoiYzJAKDUk8pDtLAF8zwdjS3BTA5jHQNeWR291T+B
o/nxRCfDmJyeCe/F3mYOuqYJnyDMi8Tms8UX5RU4fZuGB+Nbh89JiNp5yGDxIHwD
RxNcp4zdjGU4n1QkKQ0x+VvdBDcVnMLMRjFfqo2fM3rPgJi1RW3Cept5b9JSnbZz
MTl/XmPY+tEgOzXN4hPTcf+syqLxQPFlOpsP0AVVKmq00e1WkYMyBw07iaRlbFVN
d5vzPXT8jOCYhdju+DUS
=FwhD
-END PGP SIGNATURE-
--- End Message ---
--- Begin Message ---
Source: libprelude
Source-Version: 1.0.0-11.7

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

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

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Sun, 20 Dec 2015 23:02:55 +0100
Source: libprelude
Binary: libprelude-dev libprelude2 libprelude2-dbg libprelude-perl 
python-prelude
Architecture: source
Version: 1.0.0-11.7
Distribution: unstable
Urgency: medium
Maintainer: Pierre Chifflier 
Changed-By: gregor herrmann 
Closes: 808395
Description: 
 libprelude-dev - Security Information Management System [ Development files ]
 libprelude-perl - Security Information Management System [ Base library ]
 libprelude2 - Security Information Management System [ Base library ]
 libprelude2-dbg - Security Information Management System [ Debug symbols ]
 python-prelude - Security Information Management System [ Base library ]
Changes:
 libprelude (1.0.0-11.7) unstable; urgency=medium
 .
   * Non-maintainer upload.
   * Fix "FTBFS everywhere": add patch swig-perl-lua-comments.patch
 to change comment signs in swig code.
 (Closes: #808395)
Checksums-Sha1: 
 f0830d58f1fe59a71a265b72b2dc347035c90f74 2250 libprelude_1.0.0-11.7.dsc
 c2b1ca21494c0c1c2eb73caedfb119b525416528 15292 

Bug#805666: marked as done (guitarix: FTBFS: compile flags incompatiable with newer glibmm-2.4)

[Debian Bug Tracking System]

Your message dated Sun, 20 Dec 2015 22:45:10 +
with message-id 
and subject line Bug#805666: fixed in guitarix 0.34.0-0.1
has caused the Debian Bug report #805666,
regarding guitarix: FTBFS: compile flags incompatiable with newer glibmm-2.4
to be marked as done.

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

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


-- 
805666: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=805666
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: guitarix
Version: 0.32.1-1
Severity: serious
Justification: fails to build from source
Tags: sid stretch
User: reproducible-bui...@lists.alioth.debian.org
Usertags: ftbfs
X-Debbugs-CC: reproducible-bui...@lists.alioth.debian.org

Dear Maintainer,

The package fails to build:

In file included from /usr/include/c++/5/type_traits:35:0,
 from /usr/include/sigc++-2.0/sigc++/visit_each.h:22,
 from /usr/include/sigc++-2.0/sigc++/functors/slot.h:6,
 from /usr/include/sigc++-2.0/sigc++/signal_base.h:27,
 from /usr/include/sigc++-2.0/sigc++/signal.h:8,
 from /usr/include/sigc++-2.0/sigc++/sigc++.h:86,
 from /usr/include/glibmm-2.4/glibmm/thread.h:51,
 from /usr/include/glibmm-2.4/glibmm.h:87,
 from default/libgxwmm/gxwmm/knob.cc:4:
/usr/include/c++/5/bits/c++0x_warning.h:32:2: error: #error This file requires 
compiler and library support for the ISO C++ 2011 standard. This support is 
currently experimental, and must be enabled with the -std=c++11 or -std=gnu++11 
compiler options.
 #error This file requires compiler and library support for the \
  ^
In file included from /usr/include/c++/5/type_traits:35:0,
 from /usr/include/sigc++-2.0/sigc++/visit_each.h:22,
 from /usr/include/sigc++-2.0/sigc++/functors/slot.h:6,
 from /usr/include/sigc++-2.0/sigc++/signal_base.h:27,
 from /usr/include/sigc++-2.0/sigc++/signal.h:8,
 from /usr/include/sigc++-2.0/sigc++/sigc++.h:86,
 from /usr/include/glibmm-2.4/glibmm/thread.h:51,
 from /usr/include/glibmm-2.4/glibmm.h:87,
 from default/libgxwmm/gxwmm/switch.cc:4:
/usr/include/c++/5/bits/c++0x_warning.h:32:2: error: #error This file requires 
compiler and library support for the ISO C++ 2011 standard. This support is 
currently experimental, and must be enabled with the -std=c++11 or -std=gnu++11 
compiler options.
 #error This file requires compiler and library support for the \
  ^

Full build log:
https://reproducible.debian.net/rb-pkg/unstable/amd64/guitarix.html

-- System Information:
Debian Release: stretch/sid
APT prefers unstable
APT policy: (500, 'unstable')
Architecture: amd64 (x86_64)
--- End Message ---
--- Begin Message ---
Source: guitarix
Source-Version: 0.34.0-0.1

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

Debian distribution maintenance software
pp.
Víctor Cuadrado Juan  (supplier of updated guitarix 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, 20 Dec 2015 21:03:15 +0100
Source: guitarix
Binary: guitarix
Architecture: source
Version: 0.34.0-0.1
Distribution: unstable
Urgency: medium
Maintainer: Roland Stigge 
Changed-By: Víctor Cuadrado Juan 
Description:
 guitarix   - Rock guitar amplifier for Jack
Closes: 788564 805666
Changes:
 guitarix (0.34.0-0.1) unstable; urgency=medium
 .
   * Non-maintainer upload.
   * New upstream release.
 - Fix FTBFS by using correct flags when compiling against C++11
   (Closes: #805666).
 - Fix segfault when adding LADSPA plugin to a category with accents
   in the name (Closes: #788564).
   * debian/source/include-binaries: remove as not needed anymore.
   * debian/patch: update patchs to new version.
   * debian/control: Build-Depends: add libwebkit-dev.
   * Update manpage to new version.
   * source.lintian-overrides: remove as not needed anymore.

Bug#808552: dh-dist-zilla: builds fail in recent pbuilder versions

[Sascha Steinbiss]

Hi Axel,

[…]
>> I have been able to fix the issue locally by setting
>> BUILD_HOME="/tmp" in my .pbuilderrc, and afterwards everything
>> builds fine for me. However, obviously that wouldn't help on build
>> machines where I don't have control over that (autobuilders, ...).
> 
> Exactly.
> 
>> Is it just me or can you confirm the problem?
> 
> Can confirm it.

OK, thanks.

[…]
> Looks as if its possible to set a specific environment variable named
> DZIL_GLOBAL_CONFIG_ROOT to skip the detection of $HOME and set a
> specific value. So I'll probably go down that road.

Sounds good. Thanks for working on this, dh-dist-zilla is quite helpful! :)

Best,
Sascha

Bug#802121: pysvn: FTBFS: error: ‘svn

[Josue Ortega]

On Sun, Dec 20, 2015 at 06:01:10PM +0100, Raphael Hertzog wrote:
> On Wed, 18 Nov 2015, Hideki Yamane wrote:
> > On Sat, 17 Oct 2015 17:00:45 +0100 "Chris West (Faux)" 
> >  wrote:
> > > Source: pysvn
> > > Version: 1.7.8-1
> > > Severity: serious
> > > Justification: fails to build from source
> > 
> >  This FTBFS bug is fixed in new upstream release 1.8.0
> 
> Upstream 1.8.0 seems to be in the git repository, though not uploaded.
> Josue, is there any reason for that?

My intention was to get ready the Python 3 version to uploaded, but it
was not ready.

> pysvn has been dropped from testing because nobody fixed this bug in two
> months...
> 
> It would be nice to fix it and get the package back in testing.

I have pushed the new upstream release (Python 2 version only) that fixes this
bug to the DPMT git repo[1], I have now DM upload permissions for this package,
Can you upload this package for me?

[1]: https://anonscm.debian.org/cgit/python-modules/packages/pysvn.git

Cheers!

---
Josue Ortega
«Happy Hacking»
http://josueortega.org

signature.asc
Description: PGP signature

Bug#785837: marked as done (digikam: Please update to GStreamer 1.x)

[Debian Bug Tracking System]

Your message dated Sun, 20 Dec 2015 22:46:33 -0600
with message-id <4332668.2uPTFijJSm@riemann>
and subject line Re: digikam: Please update to GStreamer 1.x
has caused the Debian Bug report #785837,
regarding digikam: Please update to GStreamer 1.x
to be marked as done.

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

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


-- 
785837: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=785837
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: digikam
Severity: important
User: sl...@debian.org
Usertags: gstreamer0.10-removal

Hi maintainer,

your package digikam currently still depends on GStreamer 0.10.

GStreamer 0.10 is no longer maintained and supported by the upstream
project since almost 3 years, and contains many known bugs that are
fixed in the new 1.x release series of GStreamer. Next to many bug
fixes, the new release series also contains many other improvements,
new features and a more streamlined API.

For the next Debian release GStreamer 0.10 is planned to be removed,
and if your package is not updated it might not be included in the
release. Please update your package to use the new version as soon as
possible.

If you need any help with porting or have further questions, please
feel free to also contact me privately.

Best regards, Sebastian

PS: See https://bugs.debian.org/785198 and
https://lists.debian.org/debian-devel/2015/05/msg00335.html for some
further discussion.
--- End Message ---
--- Begin Message ---
On Wed, 20 May 2015 16:03:05 +0300 sl...@debian.org wrote:
> Source: digikam
> Severity: important
> User: sl...@debian.org
> Usertags: gstreamer0.10-removal
> 
> Hi maintainer,
> 
> your package digikam currently still depends on GStreamer 0.10.

I just uploaded a new digikam today and it no longer depends on GStreamer at 
all.  To be sure, I removed all the gstreamer 0.1 packages on my system and 
digikam still runs.

Thus closing the bug.  Please re-open with more information if I've missed 
something.

I'm frankly a bit puzzled about this bug report: digikam doesn't have any 
build-dependencies on gstreamer at all.  It does build against libqtgstreamer-
dev -- maybe that's where the dependency came from back in May?

-Steve


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

Bug#787349: marked as done ([RC][cc-by-nc-sa] Please clarify license of extra/libkipi/pics/kipi-*.svg)

[Debian Bug Tracking System]

Your message dated Sun, 20 Dec 2015 22:49:09 -0600
with message-id <3998646.Om27GLZ2Jt@riemann>
and subject line Re: [RC][cc-by-nc-sa] Please clarify license of 
extra/libkipi/pics/kipi-*.svg
has caused the Debian Bug report #787349,
regarding [RC][cc-by-nc-sa] Please clarify license of 
extra/libkipi/pics/kipi-*.svg
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.)


-- 
787349: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=787349
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: digikam
Severity: serious
version: 4:4.4.0-1.1 
user: lintian-ma...@debian.org
usertags: license-problem-cc-by-nc-sa
control: block -1 by 787347


Hi,

Could you please clarify the license of extra/libkipi/pics/kipi-*.svg, 
claimed on source to be cc-by-nc-sa, thus non free.

You could push the burden on packaged libkipi by removing the extra/libkipi 
directory and build dep on 
libkipi (BTW decreasing file size on our archive)

If it is really a non free image please purge these files.

If it is a false positive please override like in 
http://sources.debian.net/src/freecad/0.14.3702%2Bdfsg-3/debian/source/lintian-overrides/
and add a changelog entry and a full explanation on debian/copyright. You may 
ask upstream to remove this cc-by-sa-nc tag on the svg file

signature.asc
Description: This is a digitally signed message part.
--- End Message ---
--- Begin Message ---
On Sun, 31 May 2015 19:34:33 + bastien =?ISO-8859-1?Q?ROUCARI=C8S?= 
 wrote:
> Package: digikam
> Severity: serious
> version: 4:4.4.0-1.1 
> user: lintian-ma...@debian.org
> usertags: license-problem-cc-by-nc-sa
> control: block -1 by 787347
> 
> 
> Hi,
> 
> Could you please clarify the license of extra/libkipi/pics/kipi-*.svg, 
> claimed on source to be cc-by-nc-sa, thus non free.
> 
> You could push the burden on packaged libkipi by removing the extra/libkipi 
directory and build dep on 
> libkipi (BTW decreasing file size on our archive)

That's what happened.  As Alan Pater noted: upstream did this some time ago.  
Today I uploaded a new digikam (4.14) that doesn't contain extra/libkipi.

-Steve


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

Bug#786517: Remove swig 2.0 for Strech (python 3.5, octave 4.0 unsupported)

[Torsten Landschoff]

On 11/01/2015 07:08 AM, James McCoy wrote:
> On Sat, Oct 24, 2015 at 11:48:24PM +0200, Matthias Klose wrote:
>> As seen in #802906, this now becomes an RC issue, as Python 3.5 is a
>> supported Python version, and is not anymore supported by swig 2.0.
>>
>> Same for octave 4.0, and maybe other languages.
> Not everything that worked with swig2.0 works with swig3.0 (e.g.,
> subversion's swig bindings).  Why can't both be shipped?
I think they could be shipped but shouldn't.

For one swig 2.0 it not maintained upstream anymore.
The other thing is that swig 3.0 should be usable to build subversion,
so I have to get this fixed instead of using swig 2.0 as the way out.

Greetings, Torsten

Processed: your mail

[Debian Bug Tracking System]

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

> tags 795752 + pending
Bug #795752 [src:ruby-http] ruby-http: FTBFS:  undefined method `its' for 
RSpec::ExampleGroups::HTTPContentType::Parse::WithTextPlain:Class 
(NoMethodError)
Added tag(s) pending.
> tags 808515 + pending
Bug #808515 [src:ruby-test-after-commit] ruby-test-after-commit: FTBFS: 
undefined method `[]=' for nil:NilClass
Added tag(s) pending.
> thanks
Stopping processing here.

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

Processed: reassign 798096 to libautodie-perl, severity of 798096 is critical, found 798096 in 2.29-1

[Debian Bug Tracking System]

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

> reassign 798096 libautodie-perl
Bug #798096 [usrmerge] usrmerge: Conversion fails if libautodie-perl package is 
installed
Bug reassigned from package 'usrmerge' to 'libautodie-perl'.
No longer marked as found in versions usrmerge/2.
Ignoring request to alter fixed versions of bug #798096 to the same values 
previously set
> severity 798096 critical
Bug #798096 [libautodie-perl] usrmerge: Conversion fails if libautodie-perl 
package is installed
Severity set to 'critical' from 'important'
> found 798096 2.29-1
Bug #798096 [libautodie-perl] usrmerge: Conversion fails if libautodie-perl 
package is installed
Marked as found in versions libautodie-perl/2.29-1.
> thanks
Stopping processing here.

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

Bug#808533: marked as forwarded (spykeutils: FTBFS: ImportError: cannot import name SIG_PLOT_AXIS_CHANGED)

[Debian Bug Tracking System]

Your message dated Sun, 20 Dec 2015 21:09:03 -0500
with message-id <20151221020903.gg7...@onerussian.com>
has caused the   report #808533,
regarding spykeutils: FTBFS: ImportError: cannot import name 
SIG_PLOT_AXIS_CHANGED
to be marked as having been forwarded to the upstream software
author(s) Robert Pröpper 

(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.)


-- 
808533: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=808533
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
seems that compatibility issue with a more recent guiqwt 3.0.1 in debian

cheers

On Sun, 20 Dec 2015, Chris West (Faux) wrote:

> Source: spykeutils
> Version: 0.4.1-1
> Severity: serious
> Justification: fails to build from source
> Tags: sid 
> User: reproducible-bui...@lists.alioth.debian.org
> Usertags: ftbfs
> X-Debbugs-CC: reproducible-bui...@lists.alioth.debian.org

> Dear Maintainer,

> The package fails to build:

> I: Running spykeutils unittests using python2.7
> ..E...
> ==
> ERROR: Failure: ImportError (cannot import name SIG_PLOT_AXIS_CHANGED)
> --
> Traceback (most recent call last):
>   File "/usr/lib/python2.7/dist-packages/nose/loader.py", line 420, in 
> loadTestsFromName
> addr.filename, addr.module)
>   File "/usr/lib/python2.7/dist-packages/nose/importer.py", line 47, in 
> importFromPath
> return self.importFromDir(dir_path, fqname)
>   File "/usr/lib/python2.7/dist-packages/nose/importer.py", line 94, in 
> importFromDir
> mod = load_module(part_fqname, fh, filename, desc)
>   File "/spykeutils-0.4.1/spykeutils/plot/__init__.py", line 50, in 
> from interspike_intervals import isi
>   File "/spykeutils-0.4.1/spykeutils/plot/interspike_intervals.py", line 10, 
> in 
> from dialog import PlotDialog
>   File "/spykeutils-0.4.1/spykeutils/plot/dialog.py", line 29, in 
> from guiqwt.signals import SIG_PLOT_AXIS_CHANGED
> ImportError: cannot import name SIG_PLOT_AXIS_CHANGED

> --
> Ran 178 tests in 12.202s

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

> Full build log:
> https://reproducible.debian.net/rb-pkg/unstable/amd64/spykeutils.html

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


-- 
Yaroslav O. Halchenko
Center for Open Neuroscience http://centerforopenneuroscience.org
Dartmouth College, 419 Moore Hall, Hinman Box 6207, Hanover, NH 03755
Phone: +1 (603) 646-9834   Fax: +1 (603) 646-1419
WWW:   http://www.linkedin.com/in/yarik--- End Message ---

Bug#803456: digikam: Please package 5.0.0-beta1 that has been published for kde5

[Steve M. Robbins]

On Fri, 30 Oct 2015 10:55:05 +0100 valette  wrote:
> Package: digikam
> Severity: grave
> Justification: renders package unusable
> 
> digikam is not installable anymore in unstable or testing. 

That has just been fixed with upload of 4.14.

> The 5.0.0 is.

At this point, I expect we will wait for 5.x to emerge from beta status before 
packaging.

-Steve


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

Bug#807979: marked as done (bamtools cannot open bam files on big endian systems)

[Debian Bug Tracking System]

Your message dated Mon, 21 Dec 2015 00:22:07 +
with message-id 
and subject line Bug#807979: fixed in bamtools 2.4.0+dfsg-3
has caused the Debian Bug report #807979,
regarding bamtools cannot open bam files on big endian systems
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.)


-- 
807979: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=807979
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: bamtools
Version: 2.4.0+dfsg-2
Severity: grave


This bug affects big endian systems (mips, powerpc, ...) . It is not
possible to handle bam files.

Here is a quick test case:

$ bamtools count -in test.bam
bamtools count ERROR: could not open input BAM file(s)... Aborting.


I filed a bug report upstream with a detailed explanation.
https://github.com/pezmaster31/bamtools/issues/113


Best
-Dominique
--- End Message ---
--- Begin Message ---
Source: bamtools
Source-Version: 2.4.0+dfsg-3

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

Debian distribution maintenance software
pp.
Dominique Belhachemi  (supplier of updated bamtools 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: Sun, 20 Dec 2015 15:41:42 -0500
Source: bamtools
Binary: bamtools libbamtools-dev libbamtools2.4.0
Architecture: source amd64
Version: 2.4.0+dfsg-3
Distribution: unstable
Urgency: medium
Maintainer: Debian Med Packaging Team 

Changed-By: Dominique Belhachemi 
Description:
 bamtools   - toolkit for manipulating BAM (genome alignment) files
 libbamtools-dev - C++ API for manipulating BAM (genome alignment) files
 libbamtools2.4.0 - dynamic library for manipulating BAM (genome alignment) 
files
Closes: 807979
Changes:
 bamtools (2.4.0+dfsg-3) unstable; urgency=medium
 .
   * allow to read bam files on big endian systems (Closes: #807979)
   * added sam_spec_example.sam and sam_spec_example.bam files
   * activated cmake testing framework abd added simple tests
Checksums-Sha1:
 f23c256b4cadca4adc1f5ae85894b42a449ee9d5 2279 bamtools_2.4.0+dfsg-3.dsc
 6669ea8f91a0613cdb563c5caf7993f5badbf6ef 9616 
bamtools_2.4.0+dfsg-3.debian.tar.xz
 a40f517bce34786414fe5c137180735769edefa9 2646780 
bamtools-dbgsym_2.4.0+dfsg-3_amd64.deb
 6f6623219cd607f66bc6a622a3efc2ad9d057241 196618 bamtools_2.4.0+dfsg-3_amd64.deb
 49daa03e43709b61696ce0dfa6b45691fc97cf36 378688 
libbamtools-dev_2.4.0+dfsg-3_amd64.deb
 d1de89c713319055a2b7bb38e25b05ab1c55945c 2230298 
libbamtools2.4.0-dbgsym_2.4.0+dfsg-3_amd64.deb
 c8ef176bbe382722e22893e1a25daf290c61cca3 189802 
libbamtools2.4.0_2.4.0+dfsg-3_amd64.deb
Checksums-Sha256:
 b66193055380314bf29a45ca794daec6b2f991f1f5d9e4564f39c83fe9a64b4d 2279 
bamtools_2.4.0+dfsg-3.dsc
 5f4b6ab6d40cfe79d0cc50f3a22bd3547f9b3beaaf96fa56a73576d3267780b8 9616 
bamtools_2.4.0+dfsg-3.debian.tar.xz
 5e7bb95c613eb756ddd833b78de2d8ccaab7ed03baa38d8a260ae35f643bff3d 2646780 
bamtools-dbgsym_2.4.0+dfsg-3_amd64.deb
 4ee53e7377ffdcbe6b3febaa02737eacfc374a4e8b86756bdb0ce9642ee78349 196618 
bamtools_2.4.0+dfsg-3_amd64.deb
 7ac18e1bbbc518ce7956e1581383308bb1550c3aed597dfa8ba736f777903f70 378688 
libbamtools-dev_2.4.0+dfsg-3_amd64.deb
 d500ba76e5dc9fe6bbafd9d1ed6e8934976ac43e23c3291eb9896beb9065d4f7 2230298 
libbamtools2.4.0-dbgsym_2.4.0+dfsg-3_amd64.deb
 85bed6696a0530ff6974f7c85d006e10990fd3804040cd1abf0f03f7410c6c38 189802 
libbamtools2.4.0_2.4.0+dfsg-3_amd64.deb
Files:
 2be9fa22111c8f2a7f4536cd8a2b5861 2279 science optional 
bamtools_2.4.0+dfsg-3.dsc
 048150b529c5407bf456e9b6f5d10320 9616 science optional 
bamtools_2.4.0+dfsg-3.debian.tar.xz
 5e59222c5b5ae1a7d88d92300072baf5 2646780 debug extra 
bamtools-dbgsym_2.4.0+dfsg-3_amd64.deb
 cbdab418fd94c21eec73584eb6692b12 196618 science optional 
bamtools_2.4.0+dfsg-3_amd64.deb
 235a375f86970483b5f0964ddb6b83b5 378688 libdevel optional 
libbamtools-dev_2.4.0+dfsg-3_amd64.deb
 17fb1b03dee332db0e3b4bb1e424f74a 2230298 debug extra 
libbamtools2.4.0-dbgsym_2.4.0+dfsg-3_amd64.deb
 

Bug#800264: marked as done (atsar: Please migrate a supported debhelper compat level)

[Debian Bug Tracking System]

Your message dated Mon, 21 Dec 2015 00:21:56 +
with message-id 
and subject line Bug#800264: fixed in atsar 1.7-2.1
has caused the Debian Bug report #800264,
regarding atsar: Please migrate a supported debhelper compat level
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.)


-- 
800264: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=800264
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: atsar
Severity: important
Usertags: deprecated-debhelper-compat-leq-3

Hi,

The package atsar is using a debhelper compat level of 3 or less
according to lintian.  These compat levels have been deprecated for
the past ~10 years and debhelper will remove support for them in the near
future (as declared in [1]).

 * Please migrate the package to a supported debhelper compat level.
   - Compat 9 is recommended
   - Compat 5 is the bare minimum (compat 4 will be removed soon as
 well)

 * If your package uses any of the following tools, please remove them
   from the rules files.  Neither of them does anything except warn
   about their deprecation.
   - dh_desktop
   - dh_scrollkeeper (deadline: January 1st 2016)
   - dh_suidregister
   - dh_undocumented

 * Please note that your package might have been flagged for using
   e.g. "DH_COMPAT=2 dh_foo ...".
   - This will still cause issues when the compat level is removed.

 * If the package has been relying on dh_install being lenient about
   missing files, please see "MIGRATING TO COMPAT 5 OR LATER" in [1].

 * Deadline: 
   - compat 1+2: November 1st 2015
   - compat 3: January 1st 2016

If you are using other deprecated debhelper features (such as omitting
the debian/compat file), please consider fixing those while you are at
it.

Thanks,
~Niels

[1] https://lists.debian.org/debian-devel/2015/09/msg00257.html
--- End Message ---
--- Begin Message ---
Source: atsar
Source-Version: 1.7-2.1

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

Debian distribution maintenance software
pp.
Joao Eriberto Mota Filho  (supplier of updated atsar 
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: Thu, 10 Dec 2015 20:44:44 -0200
Source: atsar
Binary: atsar
Architecture: source
Version: 1.7-2.1
Distribution: unstable
Urgency: medium
Maintainer: Michael Stone 
Changed-By: Joao Eriberto Mota Filho 
Description:
 atsar  - system activity reporter
Closes: 800264
Changes:
 atsar (1.7-2.1) unstable; urgency=medium
 .
   * Non-maintainer upload.
   * Migrated DH level to 9 to avoid a FTBFS. (Closes: #800264)
   * To build twice, this package needed these changes:
   - Migrated to DebSrc 3.0 to allow patches using quilt.
   - Created a patch to fix all clean targets in all upstream
 Makefiles.
   - Added the debian/clean to remove binary changed files in
 upstream place.
   * debian/compat: added.
   * debian/conffiles: removed to avoid the duplicate-conffile
   error pointed by Lintian.
   * debian/control:
  - Added the ${misc:Depends} variable to provide the
right install dependencies.
  - Bumped Standards-Version to 3.9.6.
   * debian/rules: changed the binary-arch target to install
   files in right place.
Checksums-Sha1:
 d136ef38814bdd24a3beaf5b51dd64f3554ab207 1610 atsar_1.7-2.1.dsc
 3ca106def702249d2eadd465002c564166d5db8e 3540 atsar_1.7-2.1.debian.tar.xz
Checksums-Sha256:
 56021a74a05bb01f7ab333997ebbe2418a912b73b778fedf3458d80fdc62502c 1610 
atsar_1.7-2.1.dsc
 4582b3a441e1aa65716b0dc6ea23db52c020385ab218939bf9391e47d578ade1 3540 
atsar_1.7-2.1.debian.tar.xz
Files:
 175b985c2f11b105a7bb4c89e2296f42 1610 admin optional atsar_1.7-2.1.dsc
 95bfaeddb448ed1aac552123a27953e9 3540 admin optional 
atsar_1.7-2.1.debian.tar.xz

-BEGIN PGP SIGNATURE-
Version: GnuPG v1

iQIcBAEBAgAGBQJWagoHAAoJEN5juccE6+nv0yoP/0w4gdGURPzKAfP57x0cETXT
3e/iF1PhRq6DoS5ztlmKrL+cUNZwRsZp6UGBHOLqRWVryagQyU+MregsfpHOVAx/

Bug#808522: marked as done (pyavm: FTBFS: PIL: Exception: fromstring() has been removed. Please call frombytes() instead.)

[Debian Bug Tracking System]

Your message dated Sun, 20 Dec 2015 22:51:46 +
with message-id 
and subject line Bug#808522: fixed in pyavm 0.9.2-3
has caused the Debian Bug report #808522,
regarding pyavm: FTBFS: PIL: Exception: fromstring() has been removed. Please 
call frombytes() instead.
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.)


-- 
808522: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=808522
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: pyavm
Version: 0.9.2-2
Severity: serious
Justification: fails to build from source
Tags: sid stretch
User: reproducible-bui...@lists.alioth.debian.org
Usertags: ftbfs
X-Debbugs-CC: reproducible-bui...@lists.alioth.debian.org

Dear Maintainer,

The package fails to build:

pyavm/tests/test_main.py:49: 
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 

args = (), kw = {'data': '', 'mode': 'L', 'size': (2, 2)}

def fromstring(*args, **kw):
raise Exception("fromstring() has been removed. " +
>   "Please call frombytes() instead.")
E   Exception: fromstring() has been removed. Please call frombytes() 
instead.

/usr/lib/python2.7/dist-packages/PIL/Image.py:2053: Exception
 69 failed, 591 passed in 10.42 seconds 
debian/rules:11: recipe for target 'override_dh_auto_test' failed
make[1]: *** [override_dh_auto_test] Error 1
make[1]: Leaving directory '/pyavm-0.9.2'
debian/rules:8: recipe for target 'build' failed
make: *** [build] Error 2
dpkg-buildpackage: error: debian/rules build gave error exit status 2

Full build log:
https://reproducible.debian.net/rb-pkg/unstable/amd64/pyavm.html

-- System Information:
Debian Release: stretch/sid
APT prefers unstable
APT policy: (500, 'unstable')
Architecture: amd64 (x86_64)
--- End Message ---
--- Begin Message ---
Source: pyavm
Source-Version: 0.9.2-3

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

Debian distribution maintenance software
pp.
Josue Ortega  (supplier of updated pyavm package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Sun, 20 Dec 2015 15:36:34 -0600
Source: pyavm
Binary: python-pyavm python3-pyavm
Architecture: source all
Version: 0.9.2-3
Distribution: unstable
Urgency: medium
Maintainer: Debian Astronomy Maintainers 

Changed-By: Josue Ortega 
Description:
 python-pyavm - Python module to handle Astronomy Visualization Metadata 
Standard
 python3-pyavm - Python3 module to handle Astronomy Visualization Metadata 
Standar
Closes: 808522
Changes:
 pyavm (0.9.2-3) unstable; urgency=medium
 .
   * Closes: #808522:
 - Added debian/patches/00-fix-deprecated-fromstring-function.patch
 - debian/control: Bumped python{2,3}-pill required version (>= 3.0.0)
Checksums-Sha1:
 4e68310a4e74e88dc213d3bb9561664dd88a77eb 2254 pyavm_0.9.2-3.dsc
 f1e7c8b321c4b0a2b393bec557974b7612ab9192 3264 pyavm_0.9.2-3.debian.tar.xz
 7b29a9c6156ea12ddaa806d41326c9ec6b532c55 80484 python-pyavm_0.9.2-3_all.deb
 0b3bf063863d6009c2a6700d3af74ce96a89a829 78668 python3-pyavm_0.9.2-3_all.deb
Checksums-Sha256:
 8e65f12c48beee9a6db14de3d1f285491fc156b998a9dd740102dac3cc07e774 2254 
pyavm_0.9.2-3.dsc
 f2bded2ecbc2971b7253c86a8166198d9577f6bb157196b69f1e3db9e68a7c71 3264 
pyavm_0.9.2-3.debian.tar.xz
 9a0df3296bbd8228c4a74e8732121c43f8c5a8806a6a91c4cdc2386415bd591c 80484 
python-pyavm_0.9.2-3_all.deb
 66775522c4f85e8d9f38807f4d2aeab664282486f3a0e2e31e2d151624e7 78668 
python3-pyavm_0.9.2-3_all.deb
Files:
 7f6501f070f646cd60d1b3174ba4ea51 2254 python optional pyavm_0.9.2-3.dsc
 b1e4c0ebc869de79accb75a619e68c2e 3264 python optional 
pyavm_0.9.2-3.debian.tar.xz
 b10ae11a0b1a7962f309329bb3eafab0 80484 python optional 
python-pyavm_0.9.2-3_all.deb
 72e4d8876bec600a3a1318e527fc795f 78668 python optional 
python3-pyavm_0.9.2-3_all.deb

-BEGIN PGP SIGNATURE-
Version: GnuPG v1

Processed: severity of 803456 is wishlist

[Debian Bug Tracking System]

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

> severity 803456 wishlist
Bug #803456 [digikam] digikam: Please package 5.0.0-beta1 that has been 
published for kde5
Severity set to 'wishlist' from 'grave'
> thanks
Stopping processing here.

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

Bug#808500: marked as done (gnome-todo: Please fix faulty dependency on libgio3.0-cil-dev)

[Debian Bug Tracking System]

Your message dated Sun, 20 Dec 2015 23:46:53 +
with message-id 
and subject line Bug#808500: fixed in gnome-todo 3.18.1-2
has caused the Debian Bug report #808500,
regarding gnome-todo: Please fix faulty dependency on libgio3.0-cil-dev
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.)


-- 
808500: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=808500
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: gnome-todo
Version: 3.18.1-1
Severity: important

Dear Maintainer,

It appears your package build-depends on libgio3.0-cil-dev even though it is
not in any way CLI-related or written in C#

Judging by configure.ac, maybe you meant libglib2.0-dev? That's the package
containing gio-2.0.pc.

This issue is blocking a transition of Mono from Unstable to Testing.

-- System Information:
Debian Release: jessie/sid
  APT prefers wily-updates
  APT policy: (500, 'wily-updates'), (500, 'wily-security'), (500, 'wily'), 
(100, 'wily-backports')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 4.2.0-22-generic (SMP w/12 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)
--- End Message ---
--- Begin Message ---
Source: gnome-todo
Source-Version: 3.18.1-2

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

Debian distribution maintenance software
pp.
Michael Biebl  (supplier of updated gnome-todo 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, 20 Dec 2015 23:36:06 +0100
Source: gnome-todo
Binary: gnome-todo
Architecture: source
Version: 3.18.1-2
Distribution: unstable
Urgency: medium
Maintainer: Debian GNOME Maintainers 

Changed-By: Michael Biebl 
Description:
 gnome-todo - minimalistic personal task manager designed to fit GNOME desktop
Closes: 808500
Changes:
 gnome-todo (3.18.1-2) unstable; urgency=medium
 .
   * Drop incorrect Build-Depends on libgio3.0-cil-dev. (Closes: #808500)
Checksums-Sha1:
 2389a158ee4d0ebea7459c0f272f81b427f9221c 2272 gnome-todo_3.18.1-2.dsc
 2211c4c999380a26a6c8fce5ecc8c8fae0bac894 8020 gnome-todo_3.18.1-2.debian.tar.xz
Checksums-Sha256:
 dcb29affc47e48fd1969bdd751a22974667699fe8bc0b0ae04e8c0e769f64ca2 2272 
gnome-todo_3.18.1-2.dsc
 250dd8a39e3fe1a1ad26e85480fa40c481150eba119a1ad02cb4bec72762341f 8020 
gnome-todo_3.18.1-2.debian.tar.xz
Files:
 b69e9e6ec008ddf4732a8f259eaa4997 2272 gnome optional gnome-todo_3.18.1-2.dsc
 96be0ca082d26705257be9667b691617 8020 gnome optional 
gnome-todo_3.18.1-2.debian.tar.xz

-BEGIN PGP SIGNATURE-
Version: GnuPG v2

iQIcBAEBCAAGBQJWdy2KAAoJEGrh3w1gjyLcnXkP+wcrnQOATu0L/JrkzanP2JNH
iFwCTAiq1quVnoX+3CYV5pAxzu9aBC4si4wXrHq+/eUeMMW7RryEaUg92bEeekjU
Jdadar+gg7mGfvC6FfalTfNNw9aytY6rEGAjYQ1YjGNxFaEac8JqhF0FIYMuOSVs
vIQohTdGysRmSq/DcroRWMh34mgDeDEruR0xrC0dOkyipqLUKV+jyac9QcZUJRHo
90BtaeL4/Y33e4vhqMRMPwzch+GJIoMshPiq6aiWia+cBVg7OT5ZGe8BRIg3R5mL
+AodIn4XjSmUUM1CO4/b5lcG/GsXMwmzND5lKJXEvyyVI/xBavRtdHDxCryH5hyy
3JxKaUVNgz7anpDPcYjV+7wEw+HQqFJDuXNQ/7pIFINy0D13w0SjnldReVAic7CU
/RJx3mM00A3saM//r4pq7y/QU1jlyMAu3UJgat6M3/rPPXArmWagbjBLP02FzuWz
9aenUjqdt/wyfiGUaglz4WItHBWmPjutMSffn5Dm7+IWF905XUQ8Ux4KnAb2yvgV
ZACFzEL92Qn+dhP+F1AI43kBazCl/TBFStZsf14WaG7lnTeEmr8hbeAcefY2CdY5
JKnJcILap6Fy63PdGK0HQNAeL/yV04VWGwyUorxQGvFkl3UhKBr58gBnxM3E3VNY
npCiiwFdexfFDvwawXYH
=ENq0
-END PGP SIGNATURE End Message ---

Bug#808451: marked as done (plexus-compiler-1.0: FTBFS: AbstractCompilerTest.java:27: error: package org.apache.maven.artifact does not exist)

[Debian Bug Tracking System]

Your message dated Sun, 20 Dec 2015 23:49:40 +
with message-id 
and subject line Bug#808451: fixed in plexus-compiler-1.0 1.9.2-6
has caused the Debian Bug report #808451,
regarding plexus-compiler-1.0: FTBFS: AbstractCompilerTest.java:27: error: 
package org.apache.maven.artifact does not exist
to be marked as done.

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

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


-- 
808451: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=808451
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: plexus-compiler-1.0
Version: 1.9.2-5
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,

plexus-compiler-1.0 fails to build from source in unstable/amd64:

  [..]

  [INFO] 

  [ERROR] Failed to execute goal 
org.apache.maven.plugins:maven-javadoc-plugin:2.10.3:aggregate (default-cli) on 
project plexus-compiler: An error has occurred in JavaDocs report generation:
  [ERROR] Exit code: 1 - 
/build/plexus-compiler-1.0-1.9.2/plexus-compiler-test/src/main/java/org/codehaus/plexus/compiler/AbstractCompilerTest.java:27:
 error: package org.apache.maven.artifact does not exist
  [ERROR] import org.apache.maven.artifact.Artifact;
  [ERROR] ^
  [ERROR] 
/build/plexus-compiler-1.0-1.9.2/plexus-compiler-test/src/main/java/org/codehaus/plexus/compiler/AbstractCompilerTest.java:28:
 error: package org.apache.maven.artifact does not exist
  [ERROR] import org.apache.maven.artifact.DefaultArtifact;
  [ERROR] ^
  [ERROR] 
/build/plexus-compiler-1.0-1.9.2/plexus-compiler-test/src/main/java/org/codehaus/plexus/compiler/AbstractCompilerTest.java:29:
 error: package org.apache.maven.artifact.handler does not exist
  [ERROR] import org.apache.maven.artifact.handler.DefaultArtifactHandler;
  [ERROR] ^
  [ERROR] 
/build/plexus-compiler-1.0-1.9.2/plexus-compiler-test/src/main/java/org/codehaus/plexus/compiler/AbstractCompilerTest.java:30:
 error: package org.apache.maven.artifact.test does not exist
  [ERROR] import org.apache.maven.artifact.test.ArtifactTestCase;
  [ERROR] ^
  [ERROR] 
/build/plexus-compiler-1.0-1.9.2/plexus-compiler-test/src/main/java/org/codehaus/plexus/compiler/AbstractCompilerTest.java:31:
 error: package org.apache.maven.artifact.versioning does not exist
  [ERROR] import org.apache.maven.artifact.versioning.VersionRange;
  [ERROR] ^
  [ERROR] 
/build/plexus-compiler-1.0-1.9.2/plexus-compiler-test/src/main/java/org/codehaus/plexus/compiler/AbstractCompilerTest.java:47:
 error: cannot find symbol
  [ERROR] extends ArtifactTestCase
  [ERROR] ^
  [ERROR] symbol: class ArtifactTestCase
  [ERROR] 
/build/plexus-compiler-1.0-1.9.2/plexus-compiler-test/src/main/java/org/codehaus/plexus/compiler/AbstractCompilerTckTest.java:38:
 error: cannot access TestCase
  [ERROR] public abstract class AbstractCompilerTckTest
  [ERROR] ^
  [ERROR] class file for junit.framework.TestCase not found
  [ERROR] 
/build/plexus-compiler-1.0-1.9.2/plexus-compilers/plexus-compiler-eclipse/src/main/java/org/codehaus/plexus/compiler/eclipse/EclipseJavaCompiler.java:52:
 error: package org.eclipse.jdt.core.compiler does not exist
  [ERROR] import org.eclipse.jdt.core.compiler.IProblem;
  [ERROR] ^
  [ERROR] 
/build/plexus-compiler-1.0-1.9.2/plexus-compilers/plexus-compiler-eclipse/src/main/java/org/codehaus/plexus/compiler/eclipse/EclipseJavaCompiler.java:53:
 error: package org.eclipse.jdt.internal.compiler does not exist
  [ERROR] import org.eclipse.jdt.internal.compiler.ClassFile;
  [ERROR] ^
  [ERROR] 
/build/plexus-compiler-1.0-1.9.2/plexus-compilers/plexus-compiler-eclipse/src/main/java/org/codehaus/plexus/compiler/eclipse/EclipseJavaCompiler.java:54:
 error: package org.eclipse.jdt.internal.compiler does not exist
  [ERROR] import org.eclipse.jdt.internal.compiler.CompilationResult;
  [ERROR] ^
  [ERROR] 
/build/plexus-compiler-1.0-1.9.2/plexus-compilers/plexus-compiler-eclipse/src/main/java/org/codehaus/plexus/compiler/eclipse/EclipseJavaCompiler.java:55:
 error: package org.eclipse.jdt.internal.compiler does not exist
  [ERROR] import org.eclipse.jdt.internal.compiler.Compiler;
  [ERROR] ^
  [ERROR] 
/build/plexus-compiler-1.0-1.9.2/plexus-compilers/plexus-compiler-eclipse/src/main/java/org/codehaus/plexus/compiler/eclipse/EclipseJavaCompiler.java:56:
 error: package org.eclipse.jdt.internal.compiler does not exist
  [ERROR] import 

Bug#808563: really should be serious bug: data loss

[Ben Hutchings]

Control: severity -1 important
Control: tag -1 moreinfo

On Mon, 2015-12-21 at 09:18 +0800, 積丹尼 Dan Jacobson wrote:
> The first time it happened I couldn't boot again without a fsck.ext4 via
> a rescue CD!

I'm so tired of this routine.

Ben.

-- 
Ben Hutchings
One of the nice things about standards is that there are so many of them.

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

Processed: Re: Bug#808563: really should be serious bug: data loss

[Debian Bug Tracking System]

Processing control commands:

> severity -1 important
Bug #808563 [src:linux] Boot with 4.3: SATA errors. Returning to 4.2: no errors
Severity set to 'important' from 'grave'
> tag -1 moreinfo
Bug #808563 [src:linux] Boot with 4.3: SATA errors. Returning to 4.2: no errors
Added tag(s) moreinfo.

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

Bug#802302: marked as done (scute: FTBFS: can't connect to the SCdaemon: IPC connect call failed)

[Debian Bug Tracking System]

Your message dated Mon, 21 Dec 2015 05:00:02 +
with message-id 
and subject line Bug#802302: fixed in scute 1.5.0+git20151221.dc22111-1
has caused the Debian Bug report #802302,
regarding scute: FTBFS: can't connect to the SCdaemon: IPC connect call 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.)


-- 
802302: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=802302
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: scute
Version: 1.4.0-4
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,

scute fails to build from source in unstable/amd64:

  [..]

  gpg-agent[6636]: command 'LEARN' failed: No SmartCard daemon
  FAIL: t-closeallsessions
  gpg-agent[6636]: can't connect to the SCdaemon: IPC connect call
  failed
  gpg-agent[6636]: command 'LEARN' failed: No SmartCard daemon
  FAIL: t-getsessioninfo
  gpg-agent[6636]: can't connect to the SCdaemon: IPC connect call
  failed
  gpg-agent[6636]: command 'LEARN' failed: No SmartCard daemon
  FAIL: t-findobjects
  gpg-agent[6636]: can't connect to the SCdaemon: IPC connect call
  failed
  gpg-agent[6636]: command 'LEARN' failed: No SmartCard daemon
  FAIL: t-getattribute
  gpg-agent[6636]: can't connect to the SCdaemon: IPC connect call
  failed
  gpg-agent[6636]: command 'LEARN' failed: No SmartCard daemon
  FAIL: t-auth
  
  Testsuite summary for scute 1.4.0
  
  # TOTAL: 15
  # PASS:  4
  # SKIP:  0
  # XFAIL: 0
  # FAIL:  11
  # XPASS: 0
  # ERROR: 0
  
  See tests/test-suite.log
  Please report to bug-sc...@gnupg.org
  
  Makefile:849: recipe for target 'test-suite.log' failed
  make[5]: *** [test-suite.log] Error 1
  make[5]: Leaving directory '/tmp/buildd/scute-1.4.0/tests'
  Makefile:955: recipe for target 'check-TESTS' failed
  make[4]: *** [check-TESTS] Error 2
  make[4]: Leaving directory '/tmp/buildd/scute-1.4.0/tests'
  Makefile:1126: recipe for target 'check-am' failed
  make[3]: *** [check-am] Error 2
  make[3]: Leaving directory '/tmp/buildd/scute-1.4.0/tests'
  Makefile:447: recipe for target 'check-recursive' failed
  make[2]: *** [check-recursive] Error 1
  make[2]: Leaving directory '/tmp/buildd/scute-1.4.0'
  dh_auto_test: make -j1 check returned exit code 2
  debian/rules:13: recipe for target 'override_dh_auto_test' failed
  make[1]: *** [override_dh_auto_test] Error 2
  make[1]: Leaving directory '/tmp/buildd/scute-1.4.0'
  debian/rules:10: recipe for target 'build' failed
  make: *** [build] Error 2
  dpkg-buildpackage: error: debian/rules build gave error exit status 2

  [..]

The full build log is attached or can be viewed here:


https://reproducible.debian.net/logs/unstable/amd64/scute_1.4.0-4.build1.log.gz


Regards,

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


scute.1.4.0-4.unstable.amd64.log.txt.gz
Description: application/gzip
--- End Message ---
--- Begin Message ---
Source: scute
Source-Version: 1.5.0+git20151221.dc22111-1

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

Debian distribution maintenance software
pp.
NIIBE Yutaka  (supplier of updated scute package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Mon, 21 Dec 2015 03:03:14 +
Source: scute
Binary: scute
Architecture: source armhf
Version: 1.5.0+git20151221.dc22111-1
Distribution: unstable
Urgency: low
Maintainer: NIIBE Yutaka 
Changed-By: NIIBE Yutaka 
Description:
 scute  - OpenPGP smartcard plugin for Mozilla Network Security Services
Closes: 802302

Bug#808474: Re [Fix]: liblemonldap-ng-manager-perl: Manager shows garbage where the menu is supposed to be

[Xavier]

Hi Peter,

The problem occurs only with Debian-Testing. The fix is strange but works:

--- lemonldap-ng-manager/lib/Lemonldap/NG/Manager.pm 2015-09-28
08:18:25.740006529 +0200
+++ /usr/share/perl5/Lemonldap/NG/Manager.pm 2015-11-13
16:16:14.951924784 +0100
@@ -20,6 +20,9 @@
Lemonldap::NG::Manager::_i18n
);

+*li = *Lemonldap::NG::Manager::Downloader::li;
+*span = *Lemonldap::NG::Manager::Downloader::span;
+
## @cmethod Lemonldap::NG::Manager new(hashRef args)
# Class constructor.
#@param args hash reference


This patch has been pushed to alioth.

Note that Manager has been totaly rewritten for the next 1.9 which will
be publish in a few weeks.

Regards,
Xavier

Processed: bug 798096 is forwarded to https://github.com/pjf/autodie/issues/69

[Debian Bug Tracking System]

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

> forwarded 798096 https://github.com/pjf/autodie/issues/69
Bug #798096 [libautodie-perl] usrmerge: Conversion fails if libautodie-perl 
package is installed
Set Bug forwarded-to-address to 'https://github.com/pjf/autodie/issues/69'.
> thanks
Stopping processing here.

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

Bug#743955: coreutils: corrupted files on heavily fragmented ext3 and ext4 partitions

[Andreas Mohr]

Hi,

just wanted to ask: what is the status on this now sufficiently old issue?

I keep hitting this via apt-listbugs reports
when trying to upgrade from coreutils 8.13-3 to 8.23-4.

However, note that the original report said
"[bug introduced in coreutils-8.11]"
(upstream version value, I assume)

So, while I am currently upgrading,
it looks like the issue actually already *is* present
on my system since I'm *post* 8.11,
thus the apt-listbugs warning is somewhat moot/useless here
since I'm already past potentially hitting a regression.

Thus, perhaps original attributes which were given as:
  Package: coreutils
  Version: 8.13-3.5
  Severity: grave

ought to be request-corrected to properly indicate an *earlier* Debian package 
version
that already was affected
(that way my apt-listbugs activity probably would not list this issue
during upgrade of the versions that are relevant on my system,
since there actually is no status change during this transition).

But perhaps the more modern version value was intentionally specified
in order to *do* always warn about this issue,
even on systems which already upgraded to an affected coreutils version...



And then, of course, there remains the question of
whether the currently provided (upgrade target) version (8.23-4)
already is one where this issue indeed is fixed.

However since original report said
"It is present in the wheezy coreutils version and is fixed in
jessie/sid.  A backport of the fix or an update of coreutils would be
welcomed for wheezy."

yet https://packages.debian.org/search?keywords=coreutils
reports version in jessie as 8.23-4 which is exactly my upgrade target
and which is a version which is said to be fixed,
I'd come to think that this bug report
is missing specification of some sort of "fixed-in" attribute.
Hmm, but there's no "fixed-in" tag (since I assume the way to mark this
is to simply and properly close a bug),
but perhaps using "wheezy" (https://www.debian.org/Bugs/Developer#tags)
would be the way to go?


As it stands, I'm predominantly irritated by the fact
that apt-listbugs somehow decides to keep reporting an issue
which *is* said to be fixed in this very upgrade target version
(and, to make matters much worse,
this warning report may actively and strongly deter people
from promoting an unhealthy system to a healthy state
i.e. an actually fixed version!!!)

[personally, I have now decided to proceed with the upgrade
since it seems correct and important]

Thanks,

Andreas Mohr

Bug#808289: proposed RM: upstart -- RoQA; unmaintained

[Michael Biebl]

On Fri, 18 Dec 2015 12:25:50 +0100 Ansgar Burchardt 
wrote:
> I therefore suggest to remove the package.
> 
> If there are no objections, I'll reassign this bug report to ftp.d.o in
> a week or so.

I'm not going to comment on whether to remove upstart or not.
But if you do, the mountall package should probably be removed along
with it. The mountall tool is a helper for upstart and without upstart
it would be pretty useless to have this package in the archive.

Regards,
Michael


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



signature.asc
Description: OpenPGP digital signature

Bug#808395: libprelude: diff for NMU version 1.0.0-11.7

[gregor herrmann]

Dear maintainer,

I've uploaded an NMU for libprelude (versioned as 1.0.0-11.7). The diff
is attached to this message.

I apologize for uploading directly, but since this is one of the last
blockers for the perl 5.22 transition, I thought it is warrented in
this case.

Cheers,
gregor

-- 
 .''`.  Homepage: http://info.comodo.priv.at/ - OpenPGP key 0xBB3A68018649AA06
 : :' : Debian GNU/Linux user, admin, and developer -  https://www.debian.org/
 `. `'  Member of VIBE!AT & SPI, fellow of the Free Software Foundation Europe
   `-   NP: Rolling Stones: Driftaway
diff -Nru libprelude-1.0.0/debian/changelog libprelude-1.0.0/debian/changelog
--- libprelude-1.0.0/debian/changelog	2015-07-25 13:21:14.0 +0200
+++ libprelude-1.0.0/debian/changelog	2015-12-20 23:03:06.0 +0100
@@ -1,3 +1,12 @@
+libprelude (1.0.0-11.7) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * Fix "FTBFS everywhere": add patch swig-perl-lua-comments.patch
+to change comment signs in swig code.
+(Closes: #808395)
+
+ -- gregor herrmann   Sun, 20 Dec 2015 23:02:55 +0100
+
 libprelude (1.0.0-11.6) unstable; urgency=low
 
   * Non-maintainer upload.
diff -Nru libprelude-1.0.0/debian/patches/series libprelude-1.0.0/debian/patches/series
--- libprelude-1.0.0/debian/patches/series	2015-07-25 13:18:08.0 +0200
+++ libprelude-1.0.0/debian/patches/series	2015-12-19 15:26:56.0 +0100
@@ -9,3 +9,4 @@
 016_ppc64el-isnan-tests-fix-for-little-endian-PowerPC.patch
 gcc5.diff
 020_Update-to-latest-GnuTLS-API.patch
+swig-perl-lua-comments.patch
diff -Nru libprelude-1.0.0/debian/patches/swig-perl-lua-comments.patch libprelude-1.0.0/debian/patches/swig-perl-lua-comments.patch
--- libprelude-1.0.0/debian/patches/swig-perl-lua-comments.patch	1970-01-01 01:00:00.0 +0100
+++ libprelude-1.0.0/debian/patches/swig-perl-lua-comments.patch	2015-12-20 21:44:04.0 +0100
@@ -0,0 +1,44 @@
+Description: change comments after swig changes
+Forwarded: no
+Bug-Debian: https://bugs.debian.org/808395
+Author: gregor herrmann 
+Last-Update: 2015-12-20
+
+--- a/bindings/lua/libpreludecpp-lua.i
 b/bindings/lua/libpreludecpp-lua.i
+@@ -1,9 +1,9 @@
+-# Exception map
++/* Exception map */
+ %typemap(throws) Prelude::PreludeError %{
+ SWIG_exception(SWIG_RuntimeError, $1.what());
+ %};
+ 
+-# Lua overloading fixes
++/* Lua overloading fixes */
+ %ignore IDMEFCriteria(std::string const &);
+ %ignore IDMEFValue(int8_t);
+ %ignore IDMEFValue(uint8_t);
+@@ -36,7 +36,7 @@
+ %ignore Set(char const *, float);
+ %ignore Set(char const *, std::string);
+ 
+-# Conversion not allowed
++/* Conversion not allowed */
+ %ignore *::operator =;
+ 
+ %ignore *::operator int() const;
+--- a/bindings/perl/libpreludecpp-perl.i
 b/bindings/perl/libpreludecpp-perl.i
+@@ -1,10 +1,10 @@
+-# Exception map
++/* Exception map */
+ %typemap(throws) Prelude::PreludeError %{
+ SWIG_exception(SWIG_RuntimeError, $1.what());
+ %};
+ 
+ 
+-# Conversion not allowed
++/* Conversion not allowed */
+ %ignore *::operator =;
+ %ignore *::operator int() const;
+ %ignore *::operator long() const;


signature.asc
Description: Digital Signature

Processed: Re: stray symlink left behind after purge: /etc/apache2/conf-enabled/sitesummary.conf

[Debian Bug Tracking System]

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

> reassign 794606 src:sitesummary
Bug #794606 [sitesummary] stray symlink left behind after purge: 
/etc/apache2/conf-enabled/sitesummary.conf
Bug reassigned from package 'sitesummary' to 'src:sitesummary'.
No longer marked as found in versions sitesummary/0.1.17.
Ignoring request to alter fixed versions of bug #794606 to the same values 
previously set
> forcemerge 785215 794606
Bug #785215 {Done: Mike Gabriel } [src:sitesummary] 
sitesummary: breaks apache2.4 after uninstall
Bug #794606 [src:sitesummary] stray symlink left behind after purge: 
/etc/apache2/conf-enabled/sitesummary.conf
Severity set to 'critical' from 'serious'
Marked Bug as done
Marked as fixed in versions sitesummary/0.1.18.
Marked as found in versions sitesummary/0.1.17.
Added tag(s) patch.
Merged 785215 794606
> thanks
Stopping processing here.

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

Bug#808151: systemd: failed to start remount root and kernel file system

[Frank B. Brokken]

Dear Michael Biebl, you wrote:
> Here is a more complete log excerpt for v228 (full log attached)
> 
> > Dez 20 01:27:42 debian systemd[1]: -.mount: Changed dead -> mounted
...
> 
> So the best guess is that the timing in v228 changed a little (some code
> paths became faster). This would confirm Frank's findings that enabling
> verbose output (which slows down boot a bit) made it less likely to hit.
> 
> Martin has been working/debugging the tentative stuff in the past, so
> maybe he has some insights here.
> 
> We should probably also involve upstream at some point.

OK, thanks for the help and (for me at least) final conclusion. For me
personally the problem has been solved: for the time being I'm happy with 227,
and I'm sure that the problem will soon be fixed.

Thanks again for helping along!

Cheers,

-- 
Frank B. Brokken
Center for Information Technology, University of Groningen
(+31) 50 363 9281 
Public PGP key: http://pgp.surfnet.nl
Key Fingerprint: DF32 13DE B156 7732 E65E  3B4D 7DB2 A8BE EAE4 D8AA


signature.asc
Description: PGP signature

Bug#805240: tagged as pending

[Dmitry Smirnov]

tag 805240 pending
--

We believe that the bug #805240 you reported has been fixed in the Git
repository. You can see the commit message below and/or inspect the
commit contents at:

http://anonscm.debian.org/cgit/collab-maint/quiterss.git/diff/?id=e83d276

(This message was generated automatically by
 'git-post-receive-tag-pending-commitmsg' hook).
---
commit e83d276
Author: Dmitry Smirnov 
Date:   Sun Dec 20 09:06:17 2015

New patch to fix FTBFS (Closes: #805240)

Processed: Bug#805240 tagged as pending

[Debian Bug Tracking System]

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

> tag 805240 pending
Bug #805240 [src:quiterss] quiterss: FTBFS: error: variable ‘QDataStream ds’ 
has initializer but incomplete type
Added tag(s) pending.
> --
Stopping processing here.

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

Bug#808450: ruby-sanitize: FTBFS: Config::DEFAULT#test_0009_should clean malicious HTML [/build/ruby-sanitize-2.1.0/test/test_sanitize.rb:213]:

[Chris Lamb]

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

Dear Maintainer,

ruby-sanitize fails to build from source in unstable/amd64:

  [..]

  Finished in 0.222619s, 637.8620 runs/s, 871.4452 assertions/s.
  
1) Failure:
  Config::DEFAULT#test_0009_should clean malicious HTML 
[/build/ruby-sanitize-2.1.0/test/test_sanitize.rb:213]:
  --- expected
  +++ actual
  @@ -1 +1 @@
  -"Lorem ipsum dolor sit amet scriptalert(\"hello world\");"
  +"Lorem ipsum dolor sit amet scriptalert(\"hello world\");"
  
  
  
2) Failure:
  Config::BASIC#test_0006_should clean malicious HTML 
[/build/ruby-sanitize-2.1.0/test/test_sanitize.rb:253]:
  --- expected
  +++ actual
  @@ -1 +1 @@
  -"Lorem ipsum http://foo.com/\; 
rel=\"nofollow\">dolor sitamet scriptalert(\"hello 
world\");"
  +"Lorem ipsum http://foo.com/\; 
rel=\"nofollow\">dolor sitamet 
scriptalert(\"hello world\");"
  
  
  
3) Failure:
  Config::RESTRICTED#test_0004_should clean malicious HTML 
[/build/ruby-sanitize-2.1.0/test/test_sanitize.rb:229]:
  --- expected
  +++ actual
  @@ -1 +1 @@
  -"Lorem ipsum dolor sit amet scriptalert(\"hello 
world\");"
  +"Lorem ipsum dolor sit amet 
scriptalert(\"hello world\");"
  
  
  
4) Failure:
  Full Document parser (using clean_document)#test_0008_should wrap malicious 
with DOCTYPE and HTML tag 
[/build/ruby-sanitize-2.1.0/test/test_sanitize.rb:315]:
  --- expected
  +++ actual
  @@ -1,3 +1,3 @@
   "http://www.w3.org/TR/REC-html40/loose.dtd\;>
  -Lorem ipsum dolor sit amet scriptalert(\"hello world\");
  +Lorem ipsum dolor sit amet scriptalert(\"hello world\");
   "
  
  
  
5) Failure:
  Config::RELAXED#test_0005_should clean malicious HTML 
[/build/ruby-sanitize-2.1.0/test/test_sanitize.rb:275]:
  --- expected
  +++ actual
  @@ -1 +1 @@
  -"Lorem ipsum http://foo.com/\;>dolor sitamet 
scriptalert(\"hello world\");"
  +"Lorem ipsum http://foo.com/\;>dolor sitamet 
scriptalert(\"hello world\");"
  
  
  142 runs, 194 assertions, 5 failures, 0 errors, 0 skips
  ERROR: Test "ruby2.2" failed. Exiting.
  dh_auto_install: dh_ruby --install 
/build/ruby-sanitize-2.1.0/debian/ruby-sanitize returned exit code 1
  debian/rules:15: recipe for target 'binary' failed
  make: *** [binary] Error 1
  dpkg-buildpackage: error: fakeroot debian/rules binary gave error exit status 
2

  [..]

The full build log is attached or can be viewed here:


https://reproducible.debian.net/logs/unstable/amd64/ruby-sanitize_2.1.0-1.build1.log.gz


Regards,

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


ruby-sanitize.2.1.0-1.unstable.amd64.log.txt.gz
Description: Binary data

Bug#808451: plexus-compiler-1.0: FTBFS: AbstractCompilerTest.java:27: error: package org.apache.maven.artifact does not exist

[Chris Lamb]

Source: plexus-compiler-1.0
Version: 1.9.2-5
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,

plexus-compiler-1.0 fails to build from source in unstable/amd64:

  [..]

  [INFO] 

  [ERROR] Failed to execute goal 
org.apache.maven.plugins:maven-javadoc-plugin:2.10.3:aggregate (default-cli) on 
project plexus-compiler: An error has occurred in JavaDocs report generation:
  [ERROR] Exit code: 1 - 
/build/plexus-compiler-1.0-1.9.2/plexus-compiler-test/src/main/java/org/codehaus/plexus/compiler/AbstractCompilerTest.java:27:
 error: package org.apache.maven.artifact does not exist
  [ERROR] import org.apache.maven.artifact.Artifact;
  [ERROR] ^
  [ERROR] 
/build/plexus-compiler-1.0-1.9.2/plexus-compiler-test/src/main/java/org/codehaus/plexus/compiler/AbstractCompilerTest.java:28:
 error: package org.apache.maven.artifact does not exist
  [ERROR] import org.apache.maven.artifact.DefaultArtifact;
  [ERROR] ^
  [ERROR] 
/build/plexus-compiler-1.0-1.9.2/plexus-compiler-test/src/main/java/org/codehaus/plexus/compiler/AbstractCompilerTest.java:29:
 error: package org.apache.maven.artifact.handler does not exist
  [ERROR] import org.apache.maven.artifact.handler.DefaultArtifactHandler;
  [ERROR] ^
  [ERROR] 
/build/plexus-compiler-1.0-1.9.2/plexus-compiler-test/src/main/java/org/codehaus/plexus/compiler/AbstractCompilerTest.java:30:
 error: package org.apache.maven.artifact.test does not exist
  [ERROR] import org.apache.maven.artifact.test.ArtifactTestCase;
  [ERROR] ^
  [ERROR] 
/build/plexus-compiler-1.0-1.9.2/plexus-compiler-test/src/main/java/org/codehaus/plexus/compiler/AbstractCompilerTest.java:31:
 error: package org.apache.maven.artifact.versioning does not exist
  [ERROR] import org.apache.maven.artifact.versioning.VersionRange;
  [ERROR] ^
  [ERROR] 
/build/plexus-compiler-1.0-1.9.2/plexus-compiler-test/src/main/java/org/codehaus/plexus/compiler/AbstractCompilerTest.java:47:
 error: cannot find symbol
  [ERROR] extends ArtifactTestCase
  [ERROR] ^
  [ERROR] symbol: class ArtifactTestCase
  [ERROR] 
/build/plexus-compiler-1.0-1.9.2/plexus-compiler-test/src/main/java/org/codehaus/plexus/compiler/AbstractCompilerTckTest.java:38:
 error: cannot access TestCase
  [ERROR] public abstract class AbstractCompilerTckTest
  [ERROR] ^
  [ERROR] class file for junit.framework.TestCase not found
  [ERROR] 
/build/plexus-compiler-1.0-1.9.2/plexus-compilers/plexus-compiler-eclipse/src/main/java/org/codehaus/plexus/compiler/eclipse/EclipseJavaCompiler.java:52:
 error: package org.eclipse.jdt.core.compiler does not exist
  [ERROR] import org.eclipse.jdt.core.compiler.IProblem;
  [ERROR] ^
  [ERROR] 
/build/plexus-compiler-1.0-1.9.2/plexus-compilers/plexus-compiler-eclipse/src/main/java/org/codehaus/plexus/compiler/eclipse/EclipseJavaCompiler.java:53:
 error: package org.eclipse.jdt.internal.compiler does not exist
  [ERROR] import org.eclipse.jdt.internal.compiler.ClassFile;
  [ERROR] ^
  [ERROR] 
/build/plexus-compiler-1.0-1.9.2/plexus-compilers/plexus-compiler-eclipse/src/main/java/org/codehaus/plexus/compiler/eclipse/EclipseJavaCompiler.java:54:
 error: package org.eclipse.jdt.internal.compiler does not exist
  [ERROR] import org.eclipse.jdt.internal.compiler.CompilationResult;
  [ERROR] ^
  [ERROR] 
/build/plexus-compiler-1.0-1.9.2/plexus-compilers/plexus-compiler-eclipse/src/main/java/org/codehaus/plexus/compiler/eclipse/EclipseJavaCompiler.java:55:
 error: package org.eclipse.jdt.internal.compiler does not exist
  [ERROR] import org.eclipse.jdt.internal.compiler.Compiler;
  [ERROR] ^
  [ERROR] 
/build/plexus-compiler-1.0-1.9.2/plexus-compilers/plexus-compiler-eclipse/src/main/java/org/codehaus/plexus/compiler/eclipse/EclipseJavaCompiler.java:56:
 error: package org.eclipse.jdt.internal.compiler does not exist
  [ERROR] import org.eclipse.jdt.internal.compiler.DefaultErrorHandlingPolicies;
  [ERROR] ^
  [ERROR] 
/build/plexus-compiler-1.0-1.9.2/plexus-compilers/plexus-compiler-eclipse/src/main/java/org/codehaus/plexus/compiler/eclipse/EclipseJavaCompiler.java:57:
 error: package org.eclipse.jdt.internal.compiler does not exist
  [ERROR] import org.eclipse.jdt.internal.compiler.ICompilerRequestor;
  [ERROR] ^
  [ERROR] 
/build/plexus-compiler-1.0-1.9.2/plexus-compilers/plexus-compiler-eclipse/src/main/java/org/codehaus/plexus/compiler/eclipse/EclipseJavaCompiler.java:58:
 error: package org.eclipse.jdt.internal.compiler does not exist
  [ERROR] import org.eclipse.jdt.internal.compiler.IErrorHandlingPolicy;
  [ERROR] ^
  [ERROR] 
/build/plexus-compiler-1.0-1.9.2/plexus-compilers/plexus-compiler-eclipse/src/main/java/org/codehaus/plexus/compiler/eclipse/EclipseJavaCompiler.java:59:
 error: package org.eclipse.jdt.internal.compiler does not exist
  [ERROR] import 

Bug#808456: regina-normal: FTBFS: error: call of overloaded 'gcd(mpz_class&, mpz_class&)' is ambiguous

[Chris Lamb]

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

Dear Maintainer,

regina-normal fails to build from source in unstable/amd64:

  [..]

  [  6%] Building CXX object 
engine/CMakeFiles/regina-engine.dir/enumerate/normaliz/HilbertSeries.cpp.o
  cd 
/home/lamby/temp/cdt.20151220102316.gcFNRnDhwv/regina-normal-4.96/builds/debbuild/engine
 && /usr/bin/c++   -DREGINA_DLL_EXPORTS=1 -Dregina_engine_EXPORTS 
-I/home/lamby/temp/cdt.20151220102316.gcFNRnDhwv/regina-normal-4.96/builds/debbuild/engine
 -I/home/lamby/temp/cdt.20151220102316.gcFNRnDhwv/regina-normal-4.96/engine 
-I/usr/include/libxml2 -I/usr/include/x86_64-linux-gnu  -O3 -DNDEBUG -fPIC   -o 
CMakeFiles/regina-engine.dir/enumerate/normaliz/HilbertSeries.cpp.o -c 
/home/lamby/temp/cdt.20151220102316.gcFNRnDhwv/regina-normal-4.96/engine/enumerate/normaliz/HilbertSeries.cpp
  
/home/lamby/temp/cdt.20151220102316.gcFNRnDhwv/regina-normal-4.96/engine/enumerate/normaliz/HilbertSeries.cpp:
 In member function 'void 
libnormaliz::HilbertSeries::computeHilbertQuasiPolynomial() const':
  
/home/lamby/temp/cdt.20151220102316.gcFNRnDhwv/regina-normal-4.96/engine/enumerate/normaliz/HilbertSeries.cpp:352:26:
 error: call of overloaded 'gcd(mpz_class&, mpz_class&)' is ambiguous
   g = gcd(g,quasi_denom);
^
  In file included from 
/home/lamby/temp/cdt.20151220102316.gcFNRnDhwv/regina-normal-4.96/engine/enumerate/normaliz/HilbertSeries.cpp:25:0:
  
/home/lamby/temp/cdt.20151220102316.gcFNRnDhwv/regina-normal-4.96/engine/enumerate/normaliz/integer.h:71:22:
 note: candidate: Integer libnormaliz::gcd(const Integer&, const Integer&) 
[with Integer = __gmp_expr<__mpz_struct [1], __mpz_struct [1]>]
   template<> mpz_class gcd(const mpz_class& a, const mpz_class& b);
^
  In file included from 
/home/lamby/temp/cdt.20151220102316.gcFNRnDhwv/regina-normal-4.96/engine/enumerate/normaliz/general.h:37:0,
   from 
/home/lamby/temp/cdt.20151220102316.gcFNRnDhwv/regina-normal-4.96/engine/enumerate/normaliz/HilbertSeries.h:47,
   from 
/home/lamby/temp/cdt.20151220102316.gcFNRnDhwv/regina-normal-4.96/engine/enumerate/normaliz/HilbertSeries.cpp:22:
  /usr/include/gmpxx.h:3083:1: note: candidate: __gmp_expr::value_type, __gmp_binary_expr<__gmp_expr, 
__gmp_expr, __gmp_gcd_function> > gcd(const __gmp_expr&, const 
__gmp_expr&) [with T = __mpz_struct [1]; U = __mpz_struct [1]; V = 
__mpz_struct [1]; W = __mpz_struct [1]; typename __gmp_resolve_expr::value_type = __mpz_struct [1]]
   __GMP_DEFINE_BINARY_FUNCTION(gcd, __gmp_gcd_function)
   ^
  engine/CMakeFiles/regina-engine.dir/build.make:974: recipe for target 
'engine/CMakeFiles/regina-engine.dir/enumerate/normaliz/HilbertSeries.cpp.o' 
failed
  make[3]: *** 
[engine/CMakeFiles/regina-engine.dir/enumerate/normaliz/HilbertSeries.cpp.o] 
Error 1
  make[3]: Leaving directory 
'/home/lamby/temp/cdt.20151220102316.gcFNRnDhwv/regina-normal-4.96/builds/debbuild'
  CMakeFiles/Makefile2:144: recipe for target 
'engine/CMakeFiles/regina-engine.dir/all' failed
  make[2]: *** [engine/CMakeFiles/regina-engine.dir/all] Error 2
  make[2]: Leaving directory 
'/home/lamby/temp/cdt.20151220102316.gcFNRnDhwv/regina-normal-4.96/builds/debbuild'
  Makefile:160: recipe for target 'all' failed
  make[1]: *** [all] Error 2
  make[1]: Leaving directory 
'/home/lamby/temp/cdt.20151220102316.gcFNRnDhwv/regina-normal-4.96/builds/debbuild'
  debian/rules:44: recipe for target 'build-stamp' failed
  make: *** [build-stamp] Error 2

  [..]

The full build log is attached.


Regards,

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


regina-normal.4.96-2.unstable.amd64.log.txt.gz
Description: Binary data

Bug#808455: roboptim-core: FTBFS: dh_install: libroboptim-core2-plugin-base missing files (usr/lib/*/roboptim-core/*.so.2*), aborting

[Chris Lamb]

Source: roboptim-core
Version: 2.0-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,

roboptim-core fails to build from source in unstable/amd64:

  [..]

  -- Removed runtime path from 
"/home/lamby/temp/cdt.20151220102303.nevaxjPLAo/roboptim-core-2.0/debian/tmp/usr/lib/x86_64-linux-gnu/roboptim-core/roboptim-core-plugin-dummy.so"
  -- Installing: 
/home/lamby/temp/cdt.20151220102303.nevaxjPLAo/roboptim-core-2.0/debian/tmp/usr/lib/x86_64-linux-gnu/roboptim-core/roboptim-core-plugin-dummy-laststate.so
  -- Removed runtime path from 
"/home/lamby/temp/cdt.20151220102303.nevaxjPLAo/roboptim-core-2.0/debian/tmp/usr/lib/x86_64-linux-gnu/roboptim-core/roboptim-core-plugin-dummy-laststate.so"
  make[1]: Leaving directory 
'/home/lamby/temp/cdt.20151220102303.nevaxjPLAo/roboptim-core-2.0/obj-x86_64-linux-gnu'
 dh_install -O--parallel
  dh_install: libroboptim-core2-plugin-base missing files 
(usr/lib/*/roboptim-core/*.so.2*), aborting
  debian/rules:26: recipe for target 'binary' failed
  make: *** [binary] Error 255

  [..]

The full build log is attached.


Regards,

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


roboptim-core.2.0-7.1.unstable.amd64.log.txt.gz
Description: Binary data

Bug#808463: non-free code in boot.c

[Marco d'Itri]

Package: ntfs-3g
Version: 0.0.0+20070920-1
Severity: serious

On Dec 20, Sam Morris  wrote:

> That reminds me... I wonder if anyone has looked into the legal status of
> boot_array from ntfs-3g?
> 
> https://sources.debian.net/src/ntfs-3g/1:2015.3.14AR.1-1/ntfsprogs/boot.c/
There is not much to look at: while it would be hard to argue that this 
Microsoft-originated software cannot be redistributed for this purpose, 
I think that it is quite obvious that it is missing the corresponding 
source code and that until proven otherwise it must be assumed to not 
allow derivate works.
So it is clearly not DFSG free and should eventually be removed.

Unless I am missing something about the NTFS on-disk structure, then the 
first 512 bytes (the boot record proper) can be easily replaced by the 
code from dosfstools and the rest (the first part of NTLDR) can be 
omitted since it is only useful if you need to boot a Windows OS from 
the disk, which would need to be installed from other sources anyway
(Windows PE has a program to install NTLDR, in needed).

-- 
ciao,
Marco


signature.asc
Description: PGP signature

Processed: Re: Should playitslowly be removed?

[Debian Bug Tracking System]

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

> reassign 806586 ftp.debian.org
Bug #806586 [playitslowly] Should playitslowly be removed?
Bug reassigned from package 'playitslowly' to 'ftp.debian.org'.
Ignoring request to alter found versions of bug #806586 to the same values 
previously set
Ignoring request to alter fixed versions of bug #806586 to the same values 
previously set
> retitle 806586 RM: playitslowly - dead upstream, depends on legacy libs
Bug #806586 [ftp.debian.org] Should playitslowly be removed?
Changed Bug title to 'RM: playitslowly - dead upstream, depends on legacy libs' 
from 'Should playitslowly be removed?'
> severity 806586 normal
Bug #806586 [ftp.debian.org] RM: playitslowly - dead upstream, depends on 
legacy libs
Severity set to 'normal' from 'serious'
> thanks
Stopping processing here.

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

Bug#806586: Should playitslowly be removed?

[Moritz Mühlenhoff]

reassign 806586 ftp.debian.org
retitle 806586 RM: playitslowly - dead upstream, depends on legacy libs
severity 806586 normal
thanks

On Sun, Nov 29, 2015 at 11:40:24AM +0100, Moritz Muehlenhoff wrote:
> Package: playitslowly
> Severity: serious
> 
> Should playitslowly be removed? It depends on gstreamer 0.10 which is
> scheduled for removal, but seems dead upstream. Popcon is marginal as
> well.
> 
> Please address the outstanding bugs or reassign this to
> ftp.debian.org for removal.

No objections in three weeks, reassigning to ftp.debian.org

Cheers,
Moritz

Bug#808454: marked as done (libdata-faker-perl: FTBFS under some locales (eg. fr_CH.UTF-8))

[Debian Bug Tracking System]

Your message dated Sun, 20 Dec 2015 12:49:44 +
with message-id 
and subject line Bug#808454: fixed in libdata-faker-perl 0.10-2
has caused the Debian Bug report #808454,
regarding libdata-faker-perl: FTBFS under some locales (eg. fr_CH.UTF-8)
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.)


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

Dear Maintainer,

libdata-faker-perl fails to build from source in unstable/amd64 undersome 
locales (eg. LANG="fr_CH.UTF-8"):

  [..]

  ok 3 - all methods return something true-ish
  1..3
  ok
  t/Data-Faker-Name.t ... 
  ok 1 - use Data::Faker;
  # Subtest: instance is returned
  ok 1 - An object of class 'Data::Faker' isa 'Data::Faker'
  1..1
  ok 2 - instance is returned
  # Subtest: all methods return something true-ish
  ok 1 - name_prefix
  ok 2 - last_name
  ok 3 - name_suffix
  ok 4 - name
  ok 5 - first_name
  1..5
  ok 3 - all methods return something true-ish
  1..3
  ok
  t/Data-Faker-PhoneNumber.t  
  ok 1 - use Data::Faker;
  # Subtest: instance is returned
  ok 1 - An object of class 'Data::Faker' isa 'Data::Faker'
  1..1
  ok 2 - instance is returned
  # Subtest: all methods return something
  ok 1 - phone_number
  1..1
  ok 3 - all methods return something
  1..3
  ok
  t/Data-Faker-StreetAddress.t .. 
  ok 1 - use Data::Faker;
  # Subtest: instance is returned
  ok 1 - An object of class 'Data::Faker' isa 'Data::Faker'
  1..1
  ok 2 - instance is returned
  # Subtest: all methods return something
  ok 1 - first_name
  ok 2 - secondary_unit_designator
  ok 3 - us_state
  ok 4 - secondary_unit_number
  ok 5 - street_address
  ok 6 - city
  ok 7 - name
  ok 8 - name_prefix
  ok 9 - street_suffix
  ok 10 - us_zip_code
  ok 11 - name_suffix
  ok 12 - last_name
  ok 13 - us_state_abbr
  ok 14 - street_name
  1..14
  ok 3 - all methods return something
  1..3
  ok
  
  #   Failed test 'ampm'
  #   at t/Data-Faker.t line 11.
  # Looks like you failed 1 test of 46.
  
  #   Failed test 'all methods return something true-ish'
  #   at t/Data-Faker.t line 13.
  # Looks like you failed 1 test of 3.
  t/Data-Faker.t  
  ok 1 - use Data::Faker;
  # Subtest: instance is returned
  ok 1 - An object of class 'Data::Faker' isa 'Data::Faker'
  1..1
  ok 2 - instance is returned
  # Subtest: all methods return something true-ish
  ok 1 - phone_number
  ok 2 - city
  ok 3 - unixtime
  ok 4 - company
  ok 5 - server_name
  ok 6 - time
  ok 7 - last_name
  ok 8 - us_state
  ok 9 - date_format
  ok 10 - network_service
  ok 11 - street_name
  ok 12 - ampm_format
  ok 13 - datetime_format
  ok 14 - time_format
  ok 15 - us_zip_code
  ok 16 - first_name
  ok 17 - domain_word
  ok 18 - job_title
  ok 19 - month_abbr
  ok 20 - ip_address
  ok 21 - time_locale
  ok 22 - weekday
  ok 23 - weekday_abbr
  ok 24 - date
  ok 25 - dayofmonth
  ok 26 - company_suffix
  ok 27 - name_suffix
  ok 28 - month
  ok 29 - name
  ok 30 - century
  ok 31 - username
  ok 32 - street_address
  not ok 33 - ampm
  ok 34 - datetime_locale
  ok 35 - rfc822
  ok 36 - date_locale
  ok 37 - email
  ok 38 - street_suffix
  ok 39 - domain_name
  ok 40 - sqldate
  ok 41 - name_prefix
  ok 42 - hostname
  ok 43 - us_state_abbr
  ok 44 - secondary_unit_designator
  ok 45 - domain_suffix
  ok 46 - secondary_unit_number
  1..46
  not ok 3 - all methods return something true-ish
  1..3
  Dubious, test returned 1 (wstat 256, 0x100)
  Failed 1/3 subtests 
  t/datafaker.t . 
  ok 1 - Run for --help
  ok 2 - Results for --help
  ok 3 - Run for --help
  ok 4 - Results for --help
  ok 5 - Run for --datatypes
  ok 6 - Results for --datatypes
  1..6
  ok
  
  Test Summary Report
  ---
  t/Data-Faker-DateTime.t (Wstat: 256 Tests: 3 Failed: 1)
Failed test:  3
Non-zero exit status: 1
  t/Data-Faker.t  (Wstat: 256 Tests: 3 Failed: 1)

Bug#805391: [rrdtool-maint] Bug#805391: src:rrdtool: FTBFS on mips: `FAIL: tune2`

[Jean-Michel Vourgère]

Control: tags -1 -help +pending

Niko Tyni wrote:
> (...)
> The problem is that rrd_write() ends up calling memcpy(3) on overlapping
> memory areas, which is explicitly prohibited in its documentation. With
> libc6 2.19-20 on mips, this started zeroing out part of the areas under
> some conditions. 
> (...)

Great job! Thanks a lot. :)


Aurelien Jarno wrote:
> Can't you replace memcpy calls with overlapping areas with a memmove
> instead?

Indeed. Thank you.

I expected memcpy to do nothing when source=destination. Definitely the
kind of mistake I could have made.

Processed: Re: [rrdtool-maint] Bug#805391: src:rrdtool: FTBFS on mips: `FAIL: tune2`

[Debian Bug Tracking System]

Processing control commands:

> tags -1 -help +pending
Bug #805391 [src:rrdtool] src:rrdtool: FTBFS on mips: `FAIL: tune2`
Removed tag(s) help.
Bug #805391 [src:rrdtool] src:rrdtool: FTBFS on mips: `FAIL: tune2`
Added tag(s) pending.

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

Bug#805240: marked as done (quiterss: FTBFS: error: variable ‘QDataStream ds’ has initializer but incomplete type)

[Debian Bug Tracking System]

Your message dated Sun, 20 Dec 2015 10:08:19 +
with message-id 
and subject line Bug#805240: fixed in quiterss 0.18.2+dfsg-2
has caused the Debian Bug report #805240,
regarding quiterss: FTBFS: error: variable ‘QDataStream ds’ has initializer but 
incomplete type
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.)


-- 
805240: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=805240
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: quiterss
Version: 0.18.2+dfsg-1
Severity: serious
Justification: fails to build from source
Tags: sid stretch
User: reproducible-bui...@lists.alioth.debian.org
Usertags: ftbfs
X-Debbugs-CC: reproducible-bui...@lists.alioth.debian.org

Dear Maintainer,

The package fails to build:

3rdparty/qtsingleapplication/qtlocalpeer.cpp: In member function ‘bool 
QtLocalPeer::sendMessage(const QString&, int)’:
3rdparty/qtsingleapplication/qtlocalpeer.cpp:160:19: error: variable 
‘QDataStream ds’ has initializer but incomplete type
 QDataStream ds();
   ^
3rdparty/qtsingleapplication/qtlocalpeer.cpp: In member function ‘void 
QtLocalPeer::receiveConnection()’:
3rdparty/qtsingleapplication/qtlocalpeer.cpp:180:26: error: variable 
‘QDataStream ds’ has initializer but incomplete type
 QDataStream ds(socket);
  ^
Makefile.Release:2624: recipe for target 'release/obj/qtlocalpeer.o' failed
make[2]: *** [release/obj/qtlocalpeer.o] Error 1
make[2]: Leaving directory '/quiterss-0.18.2+dfsg'
Makefile:38: recipe for target 'release' failed

Full build log:
https://reproducible.debian.net/rb-pkg/unstable/amd64/quiterss.html

-- System Information:
Debian Release: stretch/sid
APT prefers unstable
APT policy: (500, 'unstable')
Architecture: amd64 (x86_64)
--- End Message ---
--- Begin Message ---
Source: quiterss
Source-Version: 0.18.2+dfsg-2

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

Debian distribution maintenance software
pp.
Dmitry Smirnov  (supplier of updated quiterss 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, 20 Dec 2015 20:07:21 +1100
Source: quiterss
Binary: quiterss quiterss-dbg
Architecture: source amd64
Version: 0.18.2+dfsg-2
Distribution: unstable
Urgency: medium
Maintainer: Dmitry Smirnov 
Changed-By: Dmitry Smirnov 
Description:
 quiterss   - RSS/Atom news feeds reader
 quiterss-dbg - RSS/Atom news feeds reader -- debugging symbols
Closes: 805240
Changes:
 quiterss (0.18.2+dfsg-2) unstable; urgency=medium
 .
   * New patch to fix FTBFS (Closes: #805240).
Checksums-Sha1:
 576662b91ff0df30380071831f227850495c822c 1998 quiterss_0.18.2+dfsg-2.dsc
 5781192f11302a37e64b7a3edce55fec01ceabb8 4720 
quiterss_0.18.2+dfsg-2.debian.tar.xz
 ffb948806f26459ae2de96d0440048e21b1deb6e 16963932 
quiterss-dbg_0.18.2+dfsg-2_amd64.deb
 0596bc5f65ce8e73571634d4b8cfd045960042d6 1275350 
quiterss_0.18.2+dfsg-2_amd64.deb
Checksums-Sha256:
 c1df7eabddb97ca8906dc472f27aa5fe7107229debd0781ed40f72112dd1e80d 1998 
quiterss_0.18.2+dfsg-2.dsc
 4e0c6959963eb981ce2526c2d71ffe3d38c101a72e5928defe83bd031d19f0e5 4720 
quiterss_0.18.2+dfsg-2.debian.tar.xz
 2a9afd12044bdcde12382b8ab5e86dcb6ba60137aa9b95d96a606a5f8ca7d3d8 16963932 
quiterss-dbg_0.18.2+dfsg-2_amd64.deb
 be6a524ca879aebd289d6fb45b71cf35c6bd732676fa5552b9fc86ba95e540c2 1275350 
quiterss_0.18.2+dfsg-2_amd64.deb
Files:
 26f2a57ab6ad5c433fda4410af7a16fa 1998 web optional quiterss_0.18.2+dfsg-2.dsc
 95945a54f853d8ffa6c72374f0e899cc 4720 web optional 
quiterss_0.18.2+dfsg-2.debian.tar.xz
 8fb3614a406833ee46039e1a8a6128ee 16963932 debug extra 
quiterss-dbg_0.18.2+dfsg-2_amd64.deb
 d8af1251a7e8ae28110d923c413f25f3 1275350 web optional 
quiterss_0.18.2+dfsg-2_amd64.deb

-BEGIN PGP SIGNATURE-
Version: GnuPG v1

iQIcBAEBCAAGBQJWdnRNAAoJEFK2u9lTlo0brw4P/2exhoCvBphlixnU7MQ5Ov2d
gJOtJwL3lHZFTC/AmuWCUPxJQ5PzdAMhD8nydbmlFQpvwinwt36KcF4G9q2NaD76
/fAc1pDOakgWhRvo9yVQHUq83ydErdyqwv4VMPOq6XLOlPFlvzztJhPOXjxU4c+Q

Bug#807608: marked as done (ruby-fogbugz: FTBFS: require': cannot load such file -- mocha/mini_test (LoadError))

[Debian Bug Tracking System]

Your message dated Sun, 20 Dec 2015 10:08:45 +
with message-id 
and subject line Bug#807608: fixed in ruby-fogbugz 0.2.1-2
has caused the Debian Bug report #807608,
regarding ruby-fogbugz: FTBFS: require': cannot load such file -- 
mocha/mini_test (LoadError)
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.)


-- 
807608: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=807608
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: ruby-fogbugz
Version: 0.2.1-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,

ruby-fogbugz fails to build from source in unstable/amd64:

  [..]

  
RUBYLIB=/home/lamby/temp/cdt.20151210224856.TrLrj9tI4k/ruby-fogbugz-0.2.1/debian/ruby-fogbugz/usr/lib/ruby/vendor_ruby:.
  rake2.2 -f debian/ruby-tests.rake
  /usr/bin/ruby2.2 -I"test" 
  "/usr/lib/ruby/2.2.0/rake/rake_test_loader.rb"
  "test/adapters/xml/crack_test.rb" "test/interface_test.rb" -v
  /usr/lib/ruby/2.2.0/rubygems/core_ext/kernel_require.rb:54:in
  `require': cannot load such file -- mocha/mini_test (LoadError)
from
/usr/lib/ruby/2.2.0/rubygems/core_ext/kernel_require.rb:54:in
`require'
from

/home/lamby/temp/cdt.20151210224856.TrLrj9tI4k/ruby-fogbugz-0.2.1/test/test_helper.rb:10:in
`'
from
/usr/lib/ruby/2.2.0/rubygems/core_ext/kernel_require.rb:54:in
`require'
from
/usr/lib/ruby/2.2.0/rubygems/core_ext/kernel_require.rb:54:in
`require'
from

/home/lamby/temp/cdt.20151210224856.TrLrj9tI4k/ruby-fogbugz-0.2.1/test/adapters/xml/crack_test.rb:1:in
`'
from
/usr/lib/ruby/2.2.0/rubygems/core_ext/kernel_require.rb:54:in
`require'
from
/usr/lib/ruby/2.2.0/rubygems/core_ext/kernel_require.rb:54:in
`require'
from /usr/lib/ruby/2.2.0/rake/rake_test_loader.rb:15:in `block
in '
from /usr/lib/ruby/2.2.0/rake/rake_test_loader.rb:4:in `select'
from /usr/lib/ruby/2.2.0/rake/rake_test_loader.rb:4:in `'
  rake aborted!
  Command failed with status (1): [ruby -I"test" 
  "/usr/lib/ruby/2.2.0/rake/rake_test_loader.rb"
  "test/adapters/xml/crack_test.rb" "test/interface_test.rb" -v]
  /usr/bin/rake2.2:33:in `'
  Tasks: TOP => default
  (See full trace by running task with --trace)
  ERROR: Test "ruby2.2" failed. Exiting.
  dh_auto_install: dh_ruby --install
  
/home/lamby/temp/cdt.20151210224856.TrLrj9tI4k/ruby-fogbugz-0.2.1/debian/ruby-fogbugz
  returned exit code 1
  debian/rules:6: recipe for target 'binary' failed
  make: *** [binary] Error 1

  [..]

The full build log is attached.


Regards,

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


ruby-fogbugz.0.2.1-1.unstable.amd64.log.txt.gz
Description: Binary data
--- End Message ---
--- Begin Message ---
Source: ruby-fogbugz
Source-Version: 0.2.1-2

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

Debian distribution maintenance software
pp.
Abhijith PA  (supplier of updated ruby-fogbugz 
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, 20 Dec 2015 08:27:14 +0530
Source: ruby-fogbugz
Binary: ruby-fogbugz
Architecture: source all
Version: 0.2.1-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Ruby Extras Maintainers 

Changed-By: Abhijith PA 
Description:
 ruby-fogbugz - Ruby wrapper for the Fogbugz API
Closes: 807608
Changes:
 ruby-fogbugz (0.2.1-2) unstable; urgency=medium
 .
   * Team upload
   * New build dependencies ruby-mocha & ruby-minitest (Closes: #807608)
Checksums-Sha1:
 878a435f808bb375c3fac4067cabf5f70e90d4c5 2080 ruby-fogbugz_0.2.1-2.dsc
 093a1e26e17f07e11c49173f076c328881cd1141 2284 

Bug#808462: libdigidoc-dbg: Depends on libssl1.0.0-dbg

[Kurt Roeckx]

Package: libdigidoc-dbg
Version: 3.10.1.1208+ds1-1
Severity: serious

Hi,

Your package depends on libssl1.0.0-dbg but that has been renamed
to libssl1.0.2-dbg recently.


Kurt

Bug#808466: update error at configure

[Jörg Frings-Fürst]

Package: redmine
Version: 3.0~20140825-8
Severity: grave

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Hi,

since yesterday I allways get:

redmine (3.0~20140825-8) wird eingerichtet ...
Could not find gem 'rails (~> 4.1.4) ruby' in any of the gem sources listed in
your Gemfile or available on this machine.
dpkg: Fehler beim Bearbeiten des Paketes redmine (--configure):
 Unterprozess installiertes post-installation-Skript gab den Fehlerwert 7
zurück
E: Sub-process /usr/bin/dpkg returned an error code (1)


CU
Jörg



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

Kernel: Linux 4.2.0-1-amd64 (SMP w/6 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 redmine depends on:
ii  bundler 1.10.6-2
ii  dbconfig-common 1.8.58
ii  debconf [debconf-2.0]   1.5.58
ii  libjs-scriptaculous 1.9.0-2
ii  redmine-mysql   3.0~20140825-8
ii  redmine-sqlite  3.0~20140825-8
ii  ruby1:2.2.3
ii  ruby-actionpack-action-caching  1.1.1-4
ii  ruby-awesome-nested-set 3.0.0-1
ii  ruby-coderay1.1.0-4
ii  ruby-i18n   0.7.0-2
ii  ruby-jquery-rails   4.0.5-1
ii  ruby-mime-types 2.6.1-1
ii  ruby-net-ldap   0.8.0-1
ii  ruby-openid 2.7.0debian-1
ii  ruby-protected-attributes   1.1.3-1
ii  ruby-rack   1.6.4-2
ii  ruby-rack-openid1.4.2-1
ii  ruby-rails  2:4.2.5-1
ii  ruby-rails-observers0.1.2-1
ii  ruby-redcarpet  3.3.2-1+b1
ii  ruby-request-store  1.1.0-1
ii  ruby-rmagick2.15.4-2+b1
ii  ruby2.1 [ruby-interpreter]  2.1.5-4
ii  ruby2.2 [ruby-interpreter]  2.2.3-2

Versions of packages redmine recommends:
ii  libfcgi-ruby1.9.1  0.9.2.1-1
ii  ruby-fcgi [libfcgi-ruby1.9.1]  0.9.2.1-1+b6
ii  ruby-passenger 5.0.22-1

Versions of packages redmine suggests:
ii  bzr 2.6.0+bzr6606-2
ii  cvs 2:1.12.13+real-15
pn  darcs   
ii  git 1:2.6.4-1
ii  mercurial   3.5.2-2
ii  subversion  1.9.2-3+b1

- -- debconf information:
  redmine/instances/default/pgsql/method: TCP/IP
  redmine/notify-migration:
* redmine/instances/default/database-type: mysql
  redmine/instances/default/passwords-do-not-match:
* redmine/missing-redmine-package:
  redmine/instances/default/purge: false
* redmine/instances/default/db/dbname: redmine_default
  redmine/instances/default/pgsql/admin-user: postgres
  redmine/instances/default/pgsql/authmethod-user: password
* redmine/instances/default/db/app-user: redmine_default
  redmine/instances/default/dbconfig-reinstall: false
  redmine/instances/default/missing-db-package-error: abort
  redmine/old-instances:
  redmine/instances/default/remote/port:
  redmine/instances/default/internal/skip-preseed: true
  redmine/instances/default/pgsql/manualconf:
  redmine/instances/default/pgsql/no-empty-passwords:
* redmine/instances/default/dbconfig-install: true
  redmine/instances/default/remove-error: abort
* redmine/instances/default/mysql/admin-user: root
* redmine/instances/default/default-language: de
  redmine/instances/default/remote/host:
  redmine/instances/default/remote/newhost:
  redmine/instances/default/pgsql/authmethod-admin: ident
  redmine/default-language: ${defaultLocale}
  redmine/instances/default/pgsql/changeconf: false
  redmine/instances/default/dbconfig-remove:
  redmine/instances/default/upgrade-backup: true
  redmine/instances/default/internal/reconfiguring: false
  redmine/instances/default/dbconfig-upgrade: true
* redmine/instances/default/mysql/method: Unix socket
  redmine/instances/default/upgrade-error: abort
  redmine/instances/default/install-error: abort
* redmine/current-instances: default
  redmine/instances/default/db/basepath:

-BEGIN PGP SIGNATURE-
Version: GnuPG v1

iQIcBAEBCgAGBQJWdpa/AAoJEAn4nzyModJdfAgP/3wz4SfLn3e0BBU3ENdCMZfq
uNB9GZ91RS4PYtc7TYGaL2KA6ahYxmC4RQo0bW7R9O9W7NcMWiZEKzJmmm8iizYc
BIIzjYwA7jcUOX+o9db7TES3dNrbzL78W5Ob8sWQpBGehnlNtEdpdQo0yCRpdgAO
72rVCJaY+aN5Q8MO05p9pXI7eNVIogiCCsuOl2kmqk9MvHm4hqY3GqRfTHXk0dau
62MnxCSymyWBjVcp8hXW2Uc36OqMKApTnHlESi1ItWOHNAdyWDs65po21g/a/0ql
aKS6S+AIz6v/PcJefw+tow/iVRpaTzMrSTPMtKF1pXkGx8ClHU85pWrMoOkPvwv9
GpyBY8ci3gGDmG/BmO0ze5wgxhLOiRiyZkkFKa0atjltAfWhXHrN6wZ4PCYh5FoR
cuT17eDJtEAC2WtegA0MDI27k07lu190qCbiCJp/DRZ15xT1NVBiKygBve/WiD0P
cHHiAqu1NK6pQr4lxDjSCqnFKy3LGC5H/d+GZ7esqMhLmI7Z2X6DlthC0GzxVfG7
JBBb5mKzcVGHZDWdltPpUw4bLzyegzIvGHKJiiFz2BacytPvV9flMsSadMC1XxwX
SCU0PFaqssP8FmBBrbZIALafhHc+yJ3EUmK6fusKPj6RlG+yn6MAF9F5YhG4ZWa+
8hmrvBf+IaprLs3Zoaqr

Bug#808467: python-pygithub: violates binary package name from Python Policy

[Sandro Tosi]

Package: python-pygithub
Version: 1.25.2-4
Severity: serious

Hello,
the Python policy specifies how to name binary packge for python modules at [1],
but this package doesnt respect it. Please rename it to python-github.

[1] 
https://www.debian.org/doc/packaging-manuals/python-policy/ch-module_packages.html#s-package_names

please also consider maintain this package under the DPMT[2] umbrella.

[2] https://wiki.debian.org/Teams/PythonModulesTeam

Regards,
Sandro

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

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

Versions of packages python-pygithub depends on:
pn  python:any  

python-pygithub recommends no packages.

python-pygithub suggests no packages.

-- no debconf information

Processed: notfixed 805391 in rrdtool/1.5.5-2

[Debian Bug Tracking System]

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

> notfixed 805391 rrdtool/1.5.5-2
Bug #805391 {Done: Jean-Michel Vourgère } [src:rrdtool] 
src:rrdtool: FTBFS on mips: `FAIL: tune2`
No longer marked as fixed in versions rrdtool/1.5.5-2.
> thanks
Stopping processing here.

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

Bug#803274: marked as done (prepare for giflib5)

[Debian Bug Tracking System]

Your message dated Sun, 20 Dec 2015 18:12:54 +
with message-id 
and subject line Bug#803274: fixed in libgdiplus 4.2-1
has caused the Debian Bug report #803274,
regarding prepare for giflib5
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.)


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

Package: src:libgdiplus
Version: 3.6-1
Tags: sid stretch patch
Blocks: 803158
User: gif...@packages.debian.org
Usertags: giflib5

Planning an update of giflib to the current version 5.1.1. Giflib slightly 
changes it's API, requiring soureful changes. There are some options for getting 
giflib5.1 support:


- Look for a newer upstream version, if upstream supports
both giflib4 and giflib5.1. Upload the new package,
and close the bug report.

- Patch the code to both use the NEW API. This can be done using
#if GIFLIB_MAJOR >= 5

#else

#endif
Please upload the package, and close the report.

- Unconditionally patch the code, not supporting giflib4 anymore.
Please upload a package to experimental once giflib5 hits
experimental.

For the latter two options, please see a patch at
http://launchpadlibrarian.net/222916930/libgdiplus_3.6-1build2_3.6-1ubuntu1.diff.gz

To test your changes before giflib5 is found in experimental, please use

deb https://people.debian.org/~doko/tmp/giflib5 ./

Thanks, Matthias
--- End Message ---
--- Begin Message ---
Source: libgdiplus
Source-Version: 4.2-1

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

Debian distribution maintenance software
pp.
Jo Shields  (supplier of updated libgdiplus 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, 20 Dec 2015 17:41:11 +
Source: libgdiplus
Binary: libgdiplus
Architecture: source amd64
Version: 4.2-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Mono Group 
Changed-By: Jo Shields 
Description:
 libgdiplus - interface library for System.Drawing of Mono
Closes: 688361 803274
Changes:
 libgdiplus (4.2-1) unstable; urgency=medium
 .
   * [f55e3da] Imported Upstream version 4.2 (Closes: #803274, #688361)
   * [feca412] Refreshed list of architectures
Checksums-Sha1:
 592b229efcb85238632a017a5e953ceeb0b2ab18 2026 libgdiplus_4.2-1.dsc
 af2fc5c5425286ec55b5f18726d6a0c6aaf633e6 687398 libgdiplus_4.2.orig.tar.gz
 b6990060848d220aeab908f48781b9685d027978 7076 libgdiplus_4.2-1.debian.tar.xz
 bf617cce72831d491618e0afbf7d66ab5d48ea64 399562 
libgdiplus-dbgsym_4.2-1_amd64.deb
 eaf60e291aa2b37db7b074fedba93e56a4933ee8 144408 libgdiplus_4.2-1_amd64.deb
Checksums-Sha256:
 50b5434021ba6000fdd4e394b0571922fb543bb22f0094d9594baf7e66b9de7c 2026 
libgdiplus_4.2-1.dsc
 f332b9b8b44fd1c50b8d8d01a7296360b806c790b8297614739b3de1edbadfeb 687398 
libgdiplus_4.2.orig.tar.gz
 4c18a49d8bdefccf50a0ec0456ecb5829c40b89dd4d34cd04657abc387f09761 7076 
libgdiplus_4.2-1.debian.tar.xz
 8e3fde32df1b71aa18b1f5f42c8b647ccd95123343dfa7c1fdfc66c95c8cd965 399562 
libgdiplus-dbgsym_4.2-1_amd64.deb
 5d5bc1a2241e642ce5539b32a8236de939889c931bf1c1dc6e5d692fa2195ef0 144408 
libgdiplus_4.2-1_amd64.deb
Files:
 d902fa804d0ddf203d245ab3732d6517 2026 libs optional libgdiplus_4.2-1.dsc
 3e68075aa0911d5ebc2b3739e85af0ea 687398 libs optional 
libgdiplus_4.2.orig.tar.gz
 cb804bac8602279ea25b315e8b17bc3f 7076 libs optional 
libgdiplus_4.2-1.debian.tar.xz
 0e1c74a0c9deb87836abd7f9b334dfa0 399562 debug extra 
libgdiplus-dbgsym_4.2-1_amd64.deb
 f2b46e18ddd47632fa6d515a05e10e0a 144408 libs optional 
libgdiplus_4.2-1_amd64.deb

-BEGIN PGP SIGNATURE-
Version: GnuPG v1

iQEcBAEBCAAGBQJWdulTAAoJEMkPnLkOH60M0dcIAMFSJp+Hxj7BKQdN7MUUPSaB
o7msgozwldxanDaPnBOXja/BEDYKsDrcl6F+Dt+UkqzGeLm0naowOk4JbIv01HsX
HHKtCi4crFspXsQGqYM/C11pZSM9AEnqppCioBVZ/xs1ovXNb2mhnZhzayKgYZuc
N56KFPSCl9EWn3QrG0MRKJavK+J4YEDgCf+ykmM3AeNGE5tiR9UcVnIf+93G/wr+
nhOD2BUtuVK7bspcydzBjDtpE9wRA+b4NGcg7AhhvXH5JRCWe2JtK0+cvvkmphxE

Bug#808109: marked as done (fonts-droid-fallback and fonts-droid: error when trying to install together)

[Debian Bug Tracking System]

Your message dated Sun, 20 Dec 2015 18:12:07 +
with message-id 
and subject line Bug#808109: fixed in fonts-android 1:6.0.1r3-1
has caused the Debian Bug report #808109,
regarding fonts-droid-fallback and fonts-droid: error when trying to install 
together
to be marked as done.

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

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


-- 
808109: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=808109
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: fonts-droid,fonts-droid-fallback
Version: fonts-droid/1:4.4.4r2-7
Version: fonts-droid-fallback/1:6.0.0r26-1
Severity: serious
User: trei...@debian.org
Usertags: edos-file-overwrite

Date: 2015-12-16
Architecture: amd64
Distribution: sid

Hi,

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


Selecting previously unselected package fonts-droid.
(Reading database ... 10934 files and directories currently installed.)
Preparing to unpack .../fonts-droid_1%3a4.4.4r2-7_all.deb ...
Unpacking fonts-droid (1:4.4.4r2-7) ...
Selecting previously unselected package fonts-droid-fallback.
Preparing to unpack .../fonts-droid-fallback_1%3a6.0.0r26-1_all.deb ...
Unpacking fonts-droid-fallback (1:6.0.0r26-1) ...
dpkg: error processing archive 
/var/cache/apt/archives/fonts-droid-fallback_1%3a6.0.0r26-1_all.deb (--unpack):
 trying to overwrite 
'/usr/share/fonts/truetype/droid/DroidSansFallbackFull.ttf', which is also in 
package fonts-droid 1:4.4.4r2-7
dpkg-deb: error: subprocess paste was killed by signal (Broken pipe)
Errors were encountered while processing:
 /var/cache/apt/archives/fonts-droid-fallback_1%3a6.0.0r26-1_all.deb
E: Sub-process /usr/bin/dpkg returned an error code (1)


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

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

  /etc/fonts/conf.avail/69-droid-sans-fallback.conf
  /etc/fonts/conf.d/69-droid-sans-fallback.conf
  /usr/share/fonts/truetype/droid/DroidSansFallbackFull.ttf

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

-Ralf.

PS: for more information about the detection of file overwrite errors
of this kind see http://qa.debian.org/dose/file-overwrites.html.
--- End Message ---
--- Begin Message ---
Source: fonts-android
Source-Version: 1:6.0.1r3-1

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

Debian distribution maintenance software
pp.
Vasudev Kamath  (supplier of updated fonts-android 
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, 19 Dec 2015 14:41:16 +0530
Source: fonts-android
Binary: fonts-droid-fallback fonts-android-udeb
Architecture: source all
Version: 1:6.0.1r3-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Fonts Task Force 
Changed-By: Vasudev Kamath 
Description:
 fonts-android-udeb - sans-serif font family released with Android Ice Cream 
Sandwich (udeb)
 fonts-droid-fallback - handheld device font with extensive style and language 

Bug#808544: marked as done (qt5-qmake: qmake binary in qt5-qmake doesn't use qt5)

[Debian Bug Tracking System]

Your message dated Sun, 20 Dec 2015 21:13:12 +0300
with message-id <20151220181312.ga26...@mitya57.me>
and subject line Re: Bug#808544: qt5-qmake: qmake binary in qt5-qmake doesn't 
use qt5
has caused the Debian Bug report #808544,
regarding qt5-qmake: qmake binary in qt5-qmake doesn't use qt5
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.)


-- 
808544: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=808544
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: qt5-qmake
Version: 5.3.2+dfsg-4+deb8u1
Severity: grave
Justification: renders package unusable

Dear Maintainer,

I've been trying to compile Mumble with qt5-qmake, but the qt5 version of qmake 
doesn't seem to work at alll. If I run qmake with both qt5-qmake and qt4-qmake 
installed, I have no option to use the qt5 version. If I run t5-qmake installed 
with only qt5-qmake installed I get the following result:

[wouter@wouter-desktop mumble]$ qmake -v
qmake: could not exec '/usr/lib/x86_64-linux-gnu/qt4/bin/qmake': No such file 
or directory

Running /usr/lib/x86_64-linux-gnu/qt5/bin/qmake directly does work and works 
like expected.

Thanks for looking into this,
Wouter Wijsman

P.S. sorry if I made any mistakes, this is my first bug report.

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

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

Versions of packages qt5-qmake depends on:
ii  libc6   2.19-18+deb8u1
ii  libgcc1 1:4.9.2-10
ii  libstdc++6  4.9.2-10
ii  qtchooser   47-gd2b7997-2

qt5-qmake recommends no packages.

qt5-qmake suggests no packages.

-- no debconf information
--- End Message ---
--- Begin Message ---
Hi Wouter,

On Sun, Dec 20, 2015 at 06:21:26PM +0100, Wouter Wijsman wrote:
> Package: qt5-qmake
> Version: 5.3.2+dfsg-4+deb8u1
> Severity: grave
> Justification: renders package unusable
>
> Dear Maintainer,
>
> I've been trying to compile Mumble with qt5-qmake, but the qt5 version of
> qmake doesn't seem to work at alll. If I run qmake with both qt5-qmake and
> qt4-qmake installed, I have no option to use the qt5 version. If I run
> t5-qmake installed with only qt5-qmake installed I get the following result:
>
> [wouter@wouter-desktop mumble]$ qmake -v
> qmake: could not exec '/usr/lib/x86_64-linux-gnu/qt4/bin/qmake': No such file 
> or directory
>
> Running /usr/lib/x86_64-linux-gnu/qt5/bin/qmake directly does work and works
> like expected.

The qmake binary is managed by qtchooser, which (for compatibility reasons)
still uses qt4 by default.

There are several ways to override the default preference:

 * Install qt5-default package.
 * Export QT_SELECT=qt5.
 * Run “qmake -qt5” instead of just “qmake”.
 * Run qmake by absolute path.

Thus, this is an invalid bug and I am closing it.

--
Dmitry Shachnev


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

Bug#808209: amanda-common: Depends on virtual package "perl5" which will is gone with perl/5.22

[gregor herrmann]

Control: tag -1 + pending

On Thu, 17 Dec 2015 10:28:58 +, Dominic Hargreaves wrote:

> The perl 5.22 transition just started (see
> https://lists.debian.org/debian-devel-announce/2015/12/msg5.html)
> and we seem to have missed that this package depends on the deprecated
> virtual package "perl5" like some other packages did.

Looks like the maintainer has a fix ready and is looking for a
sponsor:

http://blog.calhariz.com/post/2015/12/20/Preview-of-amanda-3.3.7p1-1


Cheers,
gregor

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


signature.asc
Description: Digital Signature

Processed: Re: Bug#808209: amanda-common: Depends on virtual package "perl5" which will is gone with perl/5.22

[Debian Bug Tracking System]

Processing control commands:

> tag -1 + pending
Bug #808209 [amanda-common] amanda-common: Depends on virtual package "perl5" 
which will is gone with perl/5.22
Added tag(s) pending.

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

Processed: Re: Bug#807392: libsendmail-milter-perl: FTBFS: Segmentation fault (core dumped)

[Debian Bug Tracking System]

Processing control commands:

> severity -1 important
Bug #807392 [src:libsendmail-milter-perl] libsendmail-milter-perl: FTBFS: 
Segmentation fault (core dumped)
Severity set to 'important' from 'serious'
> retitle -1 libsendmail-milter-perl: intermittent FTBFSes: Segmentation fault 
> (core dumped)
Bug #807392 [src:libsendmail-milter-perl] libsendmail-milter-perl: FTBFS: 
Segmentation fault (core dumped)
Changed Bug title to 'libsendmail-milter-perl: intermittent FTBFSes: 
Segmentation fault (core dumped)' from 'libsendmail-milter-perl: FTBFS: 
Segmentation fault (core dumped)'

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

Bug#807392: libsendmail-milter-perl: FTBFS: Segmentation fault (core dumped)

[gregor herrmann]

Control: severity -1 important
Control: retitle -1 libsendmail-milter-perl: intermittent FTBFSes: Segmentation 
fault (core dumped)

On Fri, 18 Dec 2015 14:41:10 +0100, gregor herrmann wrote:

> Control: tag -1 - unreproducible
> 
> On Wed, 16 Dec 2015 17:48:44 +0100, gregor herrmann wrote:
> 
> > On Tue, 08 Dec 2015 15:12:41 +0100, gregor herrmann wrote:
> > 
> > > > libsendmail-milter-perl fails to build from source in unstable/amd64:
> > [..]
> > > This builds fine for me (cowbuilder sid amd64):
> > Can anyone else reproduce or not reproduce this issue?
> 
> The buildds could reproduce the problem:
> 
> https://buildd.debian.org/status/logs.php?pkg=libsendmail-milter-perl=0.18-8%2Bb1

And after a giveback back by release team it built (same URL).

Setting the seveverity to important since this is "intermittent
only".

Cheers,
gregor

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


signature.asc
Description: Digital Signature

Bug#807537: marked as done (guacamole-server: FTBFS: error: #warning "_BSD_SOURCE and _SVID_SOURCE are deprecated, use _DEFAULT_SOURCE" [-Werror=cpp])

[Debian Bug Tracking System]

Your message dated Sun, 20 Dec 2015 18:35:03 +
with message-id 
and subject line Bug#807537: fixed in guacamole-server 0.8.3-2
has caused the Debian Bug report #807537,
regarding guacamole-server: FTBFS: error: #warning "_BSD_SOURCE and 
_SVID_SOURCE are deprecated, use _DEFAULT_SOURCE" [-Werror=cpp]
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.)


-- 
807537: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=807537
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: guacamole-server
Version: 0.8.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,

guacamole-server fails to build from source in unstable/amd64:

  [..]

  In file included from /usr/include/stdlib.h:24:0,
   from audio.c:38:
  /usr/include/features.h:148:3: error: #warning "_BSD_SOURCE and
  _SVID_SOURCE are deprecated, use _DEFAULT_SOURCE" [-Werror=cpp]
   # warning "_BSD_SOURCE and _SVID_SOURCE are deprecated, use
   _DEFAULT_SOURCE"
 ^
  cc1: all warnings being treated as errors
  Makefile:538: recipe for target 'audio.lo' failed
  make[2]: *** [audio.lo] Error 1
  make[2]: Leaving directory
  
'/home/lamby/temp/cdt.20151210102801.SeICGP4w0T/guacamole-server-0.8.3/src/libguac'
  Makefile:447: recipe for target 'all-recursive' failed
  make[1]: *** [all-recursive] Error 1
  make[1]: Leaving directory
  '/home/lamby/temp/cdt.20151210102801.SeICGP4w0T/guacamole-server-0.8.3'
  dh_auto_build: make -j1 returned exit code 2
  debian/rules:16: recipe for target 'build' failed
  make: *** [build] Error 2

  [..]

The full build log is attached.


Regards,

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


guacamole-server.0.8.3-1.unstable.amd64.log.txt.gz
Description: Binary data
--- End Message ---
--- Begin Message ---
Source: guacamole-server
Source-Version: 0.8.3-2

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

Debian distribution maintenance software
pp.
Adam Borowski  (supplier of updated guacamole-server 
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, 20 Dec 2015 18:07:12 +0100
Source: guacamole-server
Binary: libguac-dev libguac5 guacd libguac-client-vnc0 libguac-client-rdp0 
libguac-client-ssh0
Architecture: source
Version: 0.8.3-2
Distribution: unstable
Urgency: medium
Maintainer: Debian QA Group 
Changed-By: Adam Borowski 
Description:
 guacd  - Guacamole proxy daemon
 libguac-client-rdp0 - RDP support plugin for Guacamole
 libguac-client-ssh0 - SSH support plugin for Guacamole
 libguac-client-vnc0 - VNC support plugin for Guacamole
 libguac-dev - Development headers for the core Guacamole library
 libguac5   - Core Guacamole library used by guacd and client plugins
Closes: 807537
Changes:
 guacamole-server (0.8.3-2) unstable; urgency=medium
 .
   * QA upload.
   * Set maintainer to the QA group.
   * Fix FTBFS: s/_BSD_SOURCE/_DEFAULT_SOURCE/ (Closes: #807537)
Checksums-Sha1:
 c1ad17a82d9994fa10b6e36c34d91d61906241aa 1962 guacamole-server_0.8.3-2.dsc
 a51e383e611a4c67179d84f4a0de8da831c5c07c 13748 
guacamole-server_0.8.3-2.debian.tar.xz
Checksums-Sha256:
 eb4674080e627d6aca72bdfa37c5fa246c5f182aace2b675ff4241baed361b65 1962 
guacamole-server_0.8.3-2.dsc
 b81116e8c11ca183f3f9872319b32f30728005d6d42955b210cb5ad6dfc78a35 13748 
guacamole-server_0.8.3-2.debian.tar.xz
Files:
 ed6c9f6fff2457c72c7a528a08c0f943 1962 net extra guacamole-server_0.8.3-2.dsc
 d48adc0dcc1d8d2d62b794a8b33a67e8 13748 net extra 
guacamole-server_0.8.3-2.debian.tar.xz

-BEGIN PGP SIGNATURE-
Version: GnuPG v2

iQEcBAEBCAAGBQJWdvJiAAoJECw7Q2/qxoEB+4IH/jCo9pqpYVyPb2E/KccW13bN
ZvoVLBeWv24enTL3PMeKsxU10iJPahTgF+jr8Q5M1pCs/IiVjlqVrR8CPVfbo7Uu
/pc2BjOD/XvcqguJntAfmc7h9NzcpB0ubD0da9aXQG2mKL46Dy3gWxmaFoRsNQVY

Bug#802966: marked as done (digikam: FTBFS due to missing dependency on libsoprano-dev)

[Debian Bug Tracking System]

Your message dated Sun, 20 Dec 2015 18:50:05 +
with message-id 
and subject line Bug#802966: fixed in digikam 4:4.14.0-1
has caused the Debian Bug report #802966,
regarding digikam: FTBFS due to missing dependency on libsoprano-dev
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.)


-- 
802966: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=802966
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:digikam
Version: 4:4.4.0-1.1
Severity: normal
Tags: sid stretch
User: debian-...@lists.debian.org
Usertags: ftbfs-gcc-5

Please keep this issue open in the bug tracker for the package it
was filed for.  If a fix in another package is required, please
file a bug for the other package (or clone), and add a block in this
package. Please keep the issue open until the package can be built in
a follow-up test rebuild.

The package fails to build in a test rebuild on at least amd64 with
gcc-5/g++-5, but succeeds to build with gcc-4.9/g++-4.9. The
severity of this report may be raised before the stretch release.

The full build log can be found at:
http://people.debian.org/~doko/logs/gcc5-20150205/digikam_4.4.0-1.1_unstable_gcc5.log
The last lines of the build log are at the end of this report.

To build with GCC 5, either set CC=gcc-5 CXX=g++-5 explicitly,
or install the gcc, g++, gfortran, ... packages from experimental.

  apt-get -t experimental install g++ 

Common build failures are C11 as the default C mode, new warnings
resulting in build failures with -Werror turned on, or new/dropped
symbols in Debian symbols files.  For other C/C++ related build failures
see the porting guide at http://gcc.gnu.org/gcc-5/porting_to.html

[...]
--  MySQL Server found... YES
--  MySQL install_db tool found.. YES
--  libtiff library found YES
--  libpng library found. YES
--  libjasper library found.. YES
--  liblcms library found YES
--  Boost Graph library found YES
--  libkipi library found YES
--  libkexiv2 library found.. YES
--  libkdcraw library found.. YES
--  libkface library found... YES
--  libkgeomap library found. YES
--  libpgf library found. YES (optional)
--  Eigen3 library found. YES (optional)
--  libgphoto2 and libusb libraries found YES (optional)
--  libgphoto2 2.5 library found. YES (optional)
--  libkdepimlibs library found.. NO  (optional)
-- 
--  digiKam will be compiled without KDE address book support.
-- 
--  Baloo libraries found YES (optional)
--  Liblqr-1 found... YES (optional)
--  Liblensfun found. YES (optional)
--  Libsqlite v2 found... YES (optional)
--  Doxygen found YES (optional)
--  digiKam can be compiled.. YES
-- 
--
-- 
CMake Error at /usr/share/kde4/apps/cmake/modules/MacroEnsureVersion.cmake:76 
(MATH):
  math cannot parse the expression: "c++ (Debian 5-20150205-15*1 + c++
  (Debian 5-20150205-10*100 + c++ (Debian 5-20150205-10": syntax error,
  unexpected exp_PLUS, expecting exp_OPENPARENT or exp_NUMBER (2)
Call Stack (most recent call first):
  /usr/share/kde4/apps/cmake/modules/MacroEnsureVersion.cmake:95 
(NORMALIZE_VERSION)
  core/CMakeLists.txt:571 (MACRO_ENSURE_VERSION)


-- Looking for dgettext
-- Looking for dgettext - found
-- Found Gettext: built in libc
-- Configuring incomplete, errors occurred!
See also "/«PKGBUILDDIR»/obj-x86_64-linux-gnu/CMakeFiles/CMakeOutput.log".
See also "/«PKGBUILDDIR»/obj-x86_64-linux-gnu/CMakeFiles/CMakeError.log".
dh_auto_configure: cmake .. -DCMAKE_INSTALL_PREFIX=/usr 
-DCMAKE_VERBOSE_MAKEFILE=ON -DCMAKE_BUILD_TYPE=None -DCMAKE_BUILD_TYPE=Debian 
-DCMAKE_INSTALL_RPATH=/usr/lib/digikam -DDIGIKAMSC_COMPILE_DOC=on 
-DDIGIKAMSC_COMPILE_PO=on -DENABLE_LCMS2=ON -DKDE4_BUILD_TESTS=OFF 
-DDIGIKAMSC_USE_PRIVATE_KDEGRAPHICS=OFF returned exit code 1
make[1]: *** [override_dh_auto_configure] Error 2
debian/rules:19: recipe for target 'override_dh_auto_configure' failed
make[1]: Leaving directory '/«PKGBUILDDIR»'
make: *** [build-arch] Error 2
debian/rules:16: recipe for target 'build-arch' failed
dpkg-buildpackage: error: debian/rules build-arch gave error exit status 2
--- End Message ---
--- Begin 

Bug#808507: marked as done (uwsgi-plugin-mono: Please refresh architectures list for current Mono in Unstable)

[Debian Bug Tracking System]

Your message dated Sun, 20 Dec 2015 19:06:25 +
with message-id 
and subject line Bug#808507: fixed in uwsgi 2.0.11.2-6
has caused the Debian Bug report #808507,
regarding uwsgi-plugin-mono: Please refresh architectures list for current Mono 
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.)


-- 
808507: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=808507
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: uwsgi-plugin-mono
Version: 2.0.11.2-5
Severity: serious

Dear Maintainer,

Your package produces both Mono and non-Mono packages, via conditional
build-dependencies in debian/control. Please update this list to reflect
the currently supported architectures in Mono in Unstable. As-is, you
are blocking transition to Testing.

A current list can be found at /usr/share/mono/mono-archs.make

-- System Information:
Debian Release: jessie/sid
  APT prefers wily-updates
  APT policy: (500, 'wily-updates'), (500, 'wily-security'), (500, 'wily'), 
(100, 'wily-backports')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 4.2.0-22-generic (SMP w/12 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)
--- End Message ---
--- Begin Message ---
Source: uwsgi
Source-Version: 2.0.11.2-6

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

Debian distribution maintenance software
pp.
Jonas Smedegaard  (supplier of updated uwsgi package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Sun, 20 Dec 2015 23:07:27 +0530
Source: uwsgi
Binary: uwsgi uwsgi-dbg uwsgi-core uwsgi-emperor uwsgi-plugins-all 
uwsgi-infrastructure-plugins uwsgi-app-integration-plugins 
uwsgi-mongodb-plugins uwsgi-plugin-alarm-curl uwsgi-plugin-alarm-xmpp 
uwsgi-plugin-curl-cron uwsgi-plugin-emperor-pg uwsgi-plugin-glusterfs 
uwsgi-plugin-rados uwsgi-plugin-rbthreads uwsgi-plugin-fiber uwsgi-plugin-geoip 
uwsgi-plugin-graylog2 uwsgi-plugin-gevent-python uwsgi-plugin-greenlet-python 
uwsgi-plugin-asyncio-python uwsgi-plugin-asyncio-python3 
uwsgi-plugin-tornado-python uwsgi-plugin-gccgo uwsgi-plugin-jvm-openjdk-7 
uwsgi-plugin-jwsgi-openjdk-7 uwsgi-plugin-ring-openjdk-7 
uwsgi-plugin-servlet-openjdk-7 uwsgi-plugin-ldap uwsgi-plugin-lua5.1 
uwsgi-plugin-lua5.2 uwsgi-plugin-luajit uwsgi-plugin-mono uwsgi-plugin-psgi 
uwsgi-plugin-python uwsgi-plugin-python3 uwsgi-plugin-rack-ruby2.2 
uwsgi-plugin-router-access uwsgi-plugin-sqlite3 uwsgi-plugin-v8 
uwsgi-plugin-php uwsgi-plugin-xslt libapache2-mod-proxy-uwsgi 
libapache2-mod-proxy-uwsgi-dbg
 libapache2-mod-uwsgi libapache2-mod-uwsgi-dbg libapache2-mod-ruwsgi 
libapache2-mod-ruwsgi-dbg python-uwsgidecorators python3-uwsgidecorators
 uwsgi-extra
Architecture: source
Version: 2.0.11.2-6
Distribution: unstable
Urgency: medium
Maintainer: uWSGI packaging team 
Changed-By: Jonas Smedegaard 
Closes: 808507
Description: 
 libapache2-mod-proxy-uwsgi - uwsgi proxy module for Apache2 (mod_uwsgi)
 libapache2-mod-proxy-uwsgi-dbg - debugging symbols for Apache2 mod_proxy_uwsgi
 libapache2-mod-ruwsgi - uwsgi module for Apache2 (mod_Ruwsgi)
 libapache2-mod-ruwsgi-dbg - debugging symbols for Apache2 mod_Ruwsgi
 libapache2-mod-uwsgi - uwsgi module for Apache2 (mod_uwsgi)
 libapache2-mod-uwsgi-dbg - debugging symbols for Apache2 mod_uwsgi
 python-uwsgidecorators - module of decorators for elegant access to uWSGI API 
(Python 2)
 python3-uwsgidecorators - module of decorators for elegant access to uWSGI API 
(Python 3)
 uwsgi  - fast, self-healing application container server
 uwsgi-app-integration-plugins - plugins for integration of uWSGI and 
application
 uwsgi-core - fast, self-healing application container server (core)
 uwsgi-dbg  - debugging symbols for uWSGI server and it's plugins
 uwsgi-emperor - fast, self-healing application container server (emperor 
scripts)
 uwsgi-extra - fast, 

Bug#807741: Not fixed

[Dirk Heinrichs]

Hi,

Got the new version (2015.8.3+ds-2) per todays apt-get update.
Unfortunately, it's not fixed. I still get:

[...]
salt-master (2015.8.3+ds-2) wird eingerichtet ...
Job for salt-master.service failed because a timeout was exceeded. See
"systemctl status salt-master.service" and "journalctl -xe" for details.
invoke-rc.d: initscript salt-master, action "start" failed.
dpkg: Fehler beim Bearbeiten des Paketes salt-master (--configure):
 Unterprozess installiertes post-installation-Skript gab den Fehlerwert
1 zurück
Trigger für systemd (228-2) werden verarbeitet ...
Fehler traten auf beim Bearbeiten von:
 salt-master
E: Sub-process /usr/bin/dpkg returned an error code (1)
apt-get install salt-master  4,90s user 2,89s system 4% cpu 2:36,58 total
100 root@moria ~ # systemctl status
salt-master.service 
  
:(
● salt-master.service - The Salt Master Server
   Loaded: loaded (/lib/systemd/system/salt-master.service; enabled;
vendor preset: enabled)
   Active: failed (Result: timeout) since So 2015-12-20 10:06:56 CET;
15s ago
 Main PID: 9014 (code=exited, status=0/SUCCESS)

Dez 20 10:05:25 moria systemd[1]: Starting The Salt Master Server...
Dez 20 10:06:55 moria systemd[1]: salt-master.service: Start operation
timed out. Terminating.
Dez 20 10:06:56 moria systemd[1]: Failed to start The Salt Master Server.
Dez 20 10:06:56 moria systemd[1]: salt-master.service: Unit entered
failed state.
Dez 20 10:06:56 moria systemd[1]: salt-master.service: Failed with
result 'timeout'.

Please re-open.

Bye...

Dirk

-- 
Dirk Heinrichs 
GPG Public Key CB614542 | Jabber: dirk.heinri...@altum.de
Tox: he...@toxme.se
Sichere Internetkommunikation: http://www.retroshare.org
Privacy Handbuch: https://www.privacy-handbuch.de




signature.asc
Description: OpenPGP digital signature

Bug#808446: google-android-build-tools-installer: configuration script fail

[Remi Vanicat]

Package: google-android-build-tools-installer
Version: 23.0.2.0
Severity: grave
Tags: patch

Hello, 

google-android-build-tools-installer fail to install on my computer:


   install: impossible d'évaluer « 
/var/cache/google-android-build-tools-installer/android-4.4W/split-select »: 
Aucun fichier ou dossier de ce type

Meaning that it can find split-select.

It seem that it fail because it is not installing android-4.4W but
android-6.

The attached path fix this problem.

There is another bug in the Makefile: the library (libLLVM.so
libbcinfo.so libbcc.so libclang.so) are looked for in the wrong
subdirectory of android-*/, and the test looking at their possible
installation in the current system look in /usr/bin and not /usr/lib.

My patch fix those two error too.


Thanks for the package.

Cordially, Rémi.

--- google-android/Makefile 2015-12-20 10:34:56.106509766 +0100
+++ /usr/share/google-android-build-tools-installer/Makefile2015-12-20 10:30:59.106470309 +0100
@@ -6,7 +6,7 @@
 PKG_SOURCE_URL:=https://dl.google.com/android/repository/${PKG_SOURCE}
 
 DL_DIR=/var/cache/google-android-build-tools-installer
-UNPACK_DIR=$(DL_DIR)/android-4.4W
+UNPACK_DIR=$(DL_DIR)/android-6.0
 DOC_DIR=/usr/share/doc/google-android-build-tools
 
 all: $(DL_DIR)/$(UNPACK_DIR)/aapt
@@ -30,8 +30,8 @@
$(UNPACK_DIR)/zipalign \
/usr/bin/
install -d -m0755 /usr/lib/
-   for f in libLLVM.so libbcinfo.so libbcc.so libclang.so; do \
-   test -e /usr/bin/$$f || install -m0644 $(UNPACK_DIR)/$$f /usr/lib/; done
+   for f in lib/libLLVM.so lib/libbcinfo.so lib/libbcc.so lib/libclang.so; do \
+   test -e /usr/lib/$$f || install -m0644 $(UNPACK_DIR)/$$f /usr/lib/; done
install -d -m0755 $(DOC_DIR)
gzip -9 --stdout $(UNPACK_DIR)/NOTICE.txt > $(DOC_DIR)/copyright.gz
install -m0644 $(UNPACK_DIR)/source.properties $(DOC_DIR)/





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

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

Versions of packages google-android-build-tools-installer depends on:
ii  build-essential  12.1
ii  ca-certificates  20150426
ii  dpkg-dev 1.18.3
ii  libstdc++6   5.3.1-3
ii  make 4.0-8.2
ii  unzip6.0-20
ii  wget 1.17.1-1
ii  zlib1g   1:1.2.8.dfsg-2+b1

google-android-build-tools-installer recommends no packages.

google-android-build-tools-installer suggests no packages.

-- no debconf information

-- 
Rémi Vanicat

Bug#808464: suddenly being asked for interactive keyboard configuration

[Holger Levsen]

package: debconf,keyboard-configuration
severity: serious
x-debbugs-cc: reproducible-bui...@lists.alioth.debian.org

Hi,

first of all: I'm at lost where this really comes from, as this happened the 
first time on December 16th (and since then I saw and aborted it daily) and 
neither debconf nor keyboard-configuration have been uploaded since them. I 
see this in two jenkins jobs which have been unchanged since months:

https://jenkins.debian.net/view/reproducible/job/reproducible_setup_schroot_unstable_diffoscope_amd64_jenkins
https://jenkins.debian.net/view/reproducible/job/reproducible_setup_schroot_unstable_diffoscope_amd64_profitbricks3/

Which do "apt-get install -y --install-recommends diffoscope" in sid, which 
now fails like this: 

...
Setting up keyboard-configuration (1.134) ...
debconf: unable to initialize frontend: Dialog
debconf: (Dialog frontend will not work on a dumb terminal, an emacs shell 
buffer, or without a controlling terminal.)
debconf: falling back to frontend: Readline
Configuring keyboard-configuration
--

Please select the layout matching the keyboard for this machine.

  1. English (US)
  2. English (US) - Cherokee
  3. English (US) - English (Colemak)
  4. English (US) - English (Dvorak alternative international no dead keys)
  5. English (US) - English (Dvorak)
  6. English (US) - English (Dvorak, international with dead keys)
  7. English (US) - English (Macintosh)
  8. English (US) - English (US, alternative international)
  9. English (US) - English (US, international with dead keys)
  10. English (US) - English (US, with euro on 5)
  11. English (US) - English (Workman)
  12. English (US) - English (Workman, international with dead keys)
  13. English (US) - English (classic Dvorak)
  14. English (US) - English (international AltGr dead keys)
  15. English (US) - English (left handed Dvorak)
  16. English (US) - English (programmer Dvorak)
  17. English (US) - English (right handed Dvorak)
  18. English (US) - English (the divide/multiply keys toggle the layout)
  19. English (US) - Russian (US, phonetic)
  20. English (US) - Serbo-Croatian (US)
  21. Other


and then it hangs forever. We discussed this on #debian-qa:

 so why do we see this in sid now: 
https://jenkins.debian.net/view/reproducible/job/reproducible_setup_schroot_unstable_diffoscope_amd64_profitbricks3/71/console
 
(scroll down)
 could be something to do with some of the debconf frontends being 
uninstallable but I can't really see why that would make it interactive
 is it using DEBIAN_FRONTEND=noninteractive ?
 ntyni: yes. the jenkins code used here hasnt changed at all. 
 h01ger: I'm guessing DEBIAN_FRONTEND=noninteractive never took effect 
for some reason and the Dialog frontend is now falling back to a different 
frontend (Readline) that tries harder to ask its questions even without a real 
terminal/stdin
 hm
 h01ger: I wouldn't expect those messages about Dialog and Readline 
frontends at all if DEBIAN_FRONTEND=noninteractive was in effect
* h01ger nods
 h01ger: but I'm not 100% positive on that
 
https://jenkins.debian.net/job/reproducible_setup_schroot_unstable_diffoscope_amd64_jenkins/lastBuild/console
 
weirly enough has a different frontend it seems

any ideas anyone?


cheers,
Holger


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

Processed: Re: Bug#798597: imagemagick-dbg: blocks upgrades / cannot be installed

[Debian Bug Tracking System]

Processing control commands:

> reassign -1 src:imagemagick
Bug #798597 [imagemagick-dbg] imagemagick-dbg: blocks upgrades / cannot be 
installed
Bug reassigned from package 'imagemagick-dbg' to 'src:imagemagick'.
No longer marked as found in versions imagemagick/8:6.9.1.2-1.
Ignoring request to alter fixed versions of bug #798597 to the same values 
previously set

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

Bug#798597: imagemagick-dbg: blocks upgrades / cannot be installed

[Vincent Lefevre]

Control: reassign -1 src:imagemagick

On 2015-09-11 07:31:39 +0200, Bastien ROUCARIES wrote:
> Thanks for the bug report
> 
> I think it is a depends problem due to gcc5. Will get a glimpse.
> 
> Imagemagick will use soon ddeb so maybe I will close this bug by using
> ddebs and removing debug package

libimage-magick-q16-perl is also affected by the perl transition.

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

Bug#808449: ruby-loofah: FTBFS: Failure: Html5TestSanitizer#test_0051_testdata sanitizer should_sanitize_script_tag_with_multiple_open_brackets

[Chris Lamb]

Source: ruby-loofah
Version: 2.0.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,

ruby-loofah fails to build from source in unstable/amd64:

  [..]

  
  Finished in 0.596675s, 1365.9017 runs/s, 1543.5527 assertions/s.
  
1) Failure:
  Html5TestSanitizer#test_0051_testdata sanitizer 
should_sanitize_script_tag_with_multiple_open_brackets 
[/build/ruby-loofah-2.0.3/test/html5/test_sanitizer.rb:30]:
  given:"

Bug#808448: ruby-factory-girl: FTBFS: expected: 1 got: "1"

[Chris Lamb]

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

Dear Maintainer,

ruby-factory-girl fails to build from source in unstable/amd64:

  [..]

  Failures:
  
1) callbacks using syntax methods without referencing FactoryGirl 
explicitly works when the callback has one variable
   Failure/Error: expect(FactoryGirl.build(:user).first_name).to eq 1
 
 expected: 1
  got: "1"
 
 (compared using ==)
   # ./spec/acceptance/callbacks_spec.rb:97:in `block (2 levels) in '
  
2) callbacks using syntax methods without referencing FactoryGirl 
explicitly works when the callback has two variables
   Failure/Error: expect(FactoryGirl.create(:user).last_name).to eq 1
 
 expected: 1
  got: "1"
 
 (compared using ==)
   # ./spec/acceptance/callbacks_spec.rb:101:in `block (2 levels) in '
  
  Deprecation Warnings:
  
  Requiring `rspec/autorun` when running RSpec via the `rspec` command is 
deprecated. Called from /build/ruby-factory-girl-4.5.0/spec/spec_helper.rb:6:in 
`'.
  
  `failure_message_for_should` is deprecated. Use `failure_message` instead. 
Called from 
/build/ruby-factory-girl-4.5.0/spec/support/matchers/delegate.rb:30:in `block 
in '.
  `failure_message_for_should` is deprecated. Use `failure_message` instead. 
Called from 
/build/ruby-factory-girl-4.5.0/spec/factory_girl/find_definitions_spec.rb:22:in 
`block in '.
  
  
  If you need more of the backtrace for any of these deprecations to
  identify where to make the necessary changes, you can configure
  `config.raise_errors_for_deprecations!`, and it will turn the
  deprecation warnings into errors, giving you the full backtrace.
  
  3 deprecation warnings total
  
  Finished in 6 seconds (files took 0.77536 seconds to load)
  525 examples, 2 failures
  
  Failed examples:
  
  rspec ./spec/acceptance/callbacks_spec.rb:96 # callbacks using syntax methods 
without referencing FactoryGirl explicitly works when the callback has one 
variable
  rspec ./spec/acceptance/callbacks_spec.rb:100 # callbacks using syntax 
methods without referencing FactoryGirl explicitly works when the callback has 
two variables
  
  /usr/bin/ruby2.2 /usr/bin/rspec --pattern ./spec/\*\*/\*_spec.rb --format 
documentation failed
  ERROR: Test "ruby2.2" failed. Exiting.
  dh_auto_install: dh_ruby --install 
/build/ruby-factory-girl-4.5.0/debian/ruby-factory-girl returned exit code 1
  debian/rules:18: recipe for target 'binary' failed
  make: *** [binary] Error 1
  dpkg-buildpackage: error: fakeroot debian/rules binary gave error exit status 
2

  [..]

The full build log is attached or can be viewed here:


https://reproducible.debian.net/logs/unstable/amd64/ruby-factory-girl_4.5.0-1.build1.log.gz


Regards,

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


ruby-factory-girl.4.5.0-1.unstable.amd64.log.txt.gz
Description: Binary data

Bug#808447: scsh-0.6: FTBFS: ./build/initial.image': Segmentation fault

[Chris Lamb]

Source: scsh-0.6
Version: 0.6.7-8
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,

scsh-0.6 fails to build from source in unstable/amd64:

  [..]

  c/unix/socket.c: In function 's48_accept':
  c/unix/socket.c:205:63: warning: pointer targets in passing argument 3 of 
'accept' differ in signedness [-Wpointer-sign]
 connect_fd = accept(socket_fd, (struct sockaddr *), );
 ^
  In file included from c/unix/socket.c:9:0:
  /usr/include/x86_64-linux-gnu/sys/socket.h:243:12: note: expected 'socklen_t 
* restrict {aka unsigned int * restrict}' but argument is of type 'int *'
   extern int accept (int __fd, __SOCKADDR_ARG __addr,
  ^
  gcc -c -DHAVE_CONFIG_H -I ./c -I./c -I./cig  -g -Wall -O2 -D_GNU_SOURCE -o 
c/unix/dynamo.o c/unix/dynamo.c
  rm -f /tmp/s48_external_$$.c &&   \
  ./build/build-external-modules /tmp/s48_external_$$.c \
s48_init_additional_inits s48_init_socket s48_init_external_lookup 
s48_init_syslog s48_init_posix_regexp s48_init_userinfo s48_init_sighandlers 
s48_init_syscalls s48_init_network s48_init_flock s48_init_dirstuff 
s48_init_time s48_init_tty s48_init_cig s48_init_libscsh s48_init_md5 
s48_init_srfi_27 s48_init_cig &&  \
  gcc -rdynamic -g -Wall -O2 -D_GNU_SOURCE -o scshvm c/main.o 
scsh/process_args.o c/init.o c/scheme48vm.o c/scheme48heap.o c/extension.o 
c/external.o cig/libcig.o cig/libcig1.o scsh/cstuff.o scsh/dirstuff1.o 
scsh/fdports1.o scsh/flock1.o scsh/machine/time_dep1.o scsh/signals1.o 
scsh/machine/libansi.o scsh/network1.o scsh/putenv.o scsh/rx/regexp1.o 
scsh/sleep1.o scsh/syscalls1.o scsh/syslog1.o scsh/time1.o scsh/tty1.o 
scsh/userinfo1.o scsh/sighandlers1.o scsh/libscsh.o scsh/md5.o scsh/proc2.o 
c/srfi/srfi-27.o c/unix/misc.o c/unix/io.o c/unix/fd-io.o c/unix/event.o
   \
/tmp/s48_external_$$.c  \
c/unix/socket.o c/unix/dynamo.o \
 -lelf -lcrypt -lnsl -ldl -lm -lc -lutil && 
\
  rm -f /tmp/s48_external_$$.c
  ./build/build-usual-image . "./scheme" 'scsh.image' './scshvm' \
'./build/initial.image'
  Segmentation fault
  Makefile:319: recipe for target 'scsh.image' failed
  make[1]: *** [scsh.image] Error 139
  make[1]: Leaving directory '/build/scsh-0.6-0.6.7'
  debian/rules:55: recipe for target 'build-stamp' failed
  make: *** [build-stamp] Error 2
  dpkg-buildpackage: error: debian/rules build gave error exit status 2

  [..]

The full build log is attached or can be viewed here:


https://reproducible.debian.net/logs/unstable/amd64/scsh-0.6_0.6.7-8.build1.log.gz


Regards,

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


scsh-0.6.0.6.7-8.unstable.amd64.log.txt.gz
Description: Binary data

Bug#805391: marked as done (src:rrdtool: FTBFS on mips: `FAIL: tune2`)

[Debian Bug Tracking System]

Your message dated Sun, 20 Dec 2015 11:20:12 +
with message-id 
and subject line Bug#805391: fixed in rrdtool 1.5.5-2
has caused the Debian Bug report #805391,
regarding src:rrdtool: FTBFS on mips: `FAIL: tune2`
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.)


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

make  check-TESTS
make[4]: Entering directory '/«PKGBUILDDIR»/tests'
make[5]: Entering directory '/«PKGBUILDDIR»/tests'
PASS: modify1
PASS: modify2
PASS: modify3
PASS: modify4
PASS: modify5
PASS: tune1
FAIL: tune2
PASS: rpn1
PASS: rpn2
PASS: rrdcreate
PASS: dump-restore
PASS: create-with-source-1
PASS: create-with-source-2
PASS: create-with-source-3
PASS: create-with-source-4
PASS: create-with-source-and-mapping-1
PASS: create-from-template-1
PASS: dcounter1
PASS: vformatter1
PASS: xport1

Testsuite summary for rrdtool 1.5.5

# TOTAL: 20
# PASS:  19
# SKIP:  0
# XFAIL: 0
# FAIL:  1
# XPASS: 0
# ERROR: 0

See tests/test-suite.log

Makefile:633: recipe for target 'test-suite.log' failed
make[5]: *** [test-suite.log] Error 1
make[5]: Leaving directory '/«PKGBUILDDIR»/tests'
Makefile:739: recipe for target 'check-TESTS' failed
make[4]: *** [check-TESTS] Error 2
make[4]: Leaving directory '/«PKGBUILDDIR»/tests'
Makefile:945: recipe for target 'check-am' failed
make[3]: *** [check-am] Error 2
make[3]: Leaving directory '/«PKGBUILDDIR»/tests'
Makefile:567: recipe for target 'check-recursive' failed
make[2]: *** [check-recursive] Error 1
make[2]: Leaving directory '/«PKGBUILDDIR»'
dh_auto_test: make -j1 check returned exit code 2
debian/rules:67: recipe for target 'override_dh_auto_test' failed
make[1]: *** [override_dh_auto_test] Error 2
make[1]: Leaving directory '/«PKGBUILDDIR»'
debian/rules:30: recipe for target 'build-arch' failed
make: *** [build-arch] Error 2
dpkg-buildpackage: error: debian/rules build-arch gave error exit status 2

Full log: 
https://buildd.debian.org/status/fetch.php?pkg=rrdtool=mips=1.5.5-1=1447755922

I have just reproduced this on minkus.debian.org, and tests/test-suite.log 
contains:

8<8<8<-
=
   rrdtool 1.5.5: tests/test-suite.log
=

# TOTAL: 20
# PASS:  19
# SKIP:  0
# XFAIL: 0
# FAIL:  1
# XPASS: 0
# ERROR: 0

.. contents:: :depth: 2

FAIL: tune2
===

OK: create
OK: out of range beta error
OK: RRD unchanged
ERROR: unknown consolidation function ''
--- -   2015-11-17 14:59:33.071912150 +0100
+++ /home/terceiro/rrdtool-1.5.5/tests/tune2-testa-mod1.dump2015-11-10 
18:14:24.0 +0100
@@ -360,8 +360,8 @@
1 
 

-   0.000e+00
-   0
+   9.000e-01
+   135
0


@@ -528,75 +528,653 @@



-   
-   0 
+   DEVSEASONAL
+   1 
 

-   0.000e+00
+   9.000e-01
+   135
+   0



0.000e+00
0.000e+00
-   0.000e+00
-   0
+   NaN
+   NaN
+   1


0.000e+00
0.000e+00
-   0.000e+00
-   0
+   NaN
+   NaN
+   1



+
NaNNaN
+
NaNNaN
+
NaNNaN
+
NaNNaN
+
NaNNaN
+
NaNNaN
+
NaNNaN
+
NaNNaN
+
NaNNaN
+
NaNNaN
+
NaNNaN
+
NaNNaN
+   

Bug#808462: marked as done (libdigidoc-dbg: Depends on libssl1.0.0-dbg)

[Debian Bug Tracking System]

Your message dated Sun, 20 Dec 2015 12:04:55 +
with message-id 
and subject line Bug#808462: fixed in libdigidoc 3.10.1.1208+ds1-2
has caused the Debian Bug report #808462,
regarding libdigidoc-dbg: Depends on libssl1.0.0-dbg
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.)


-- 
808462: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=808462
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: libdigidoc-dbg
Version: 3.10.1.1208+ds1-1
Severity: serious

Hi,

Your package depends on libssl1.0.0-dbg but that has been renamed
to libssl1.0.2-dbg recently.


Kurt
--- End Message ---
--- Begin Message ---
Source: libdigidoc
Source-Version: 3.10.1.1208+ds1-2

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

Debian distribution maintenance software
pp.
Andrew Shadura  (supplier of updated libdigidoc 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: Sun, 20 Dec 2015 12:49:15 +0100
Source: libdigidoc
Binary: libdigidoc-common libdigidoc2 libdigidoc-tools libdigidoc-dbg 
libdigidoc-dev libdigidoc-doc
Architecture: source
Version: 3.10.1.1208+ds1-2
Distribution: unstable
Urgency: medium
Maintainer: Andrew Shadura 
Changed-By: Andrew Shadura 
Description:
 libdigidoc-common - DigiDoc digital signature library common files
 libdigidoc-dbg - debugging symbols for DigiDoc digital signature library
 libdigidoc-dev - DigiDoc digital signature development files
 libdigidoc-doc - DigiDoc digital signature library documentation
 libdigidoc-tools - DigiDoc digital signature library tools
 libdigidoc2 - DigiDoc digital signature library
Closes: 808462
Changes:
 libdigidoc (3.10.1.1208+ds1-2) unstable; urgency=medium
 .
   * Update the dependency on libssl debug package (Closes: #808462).
   * Migrate to the automatic dbgsym packages.
Checksums-Sha1:
 9fcd2d6e6c3491b6ad78c585a59dbdf31ea1af67 1830 libdigidoc_3.10.1.1208+ds1-2.dsc
 83b43f1d788bed53a4a39363f1de8d585c1c5a36 3804 
libdigidoc_3.10.1.1208+ds1-2.debian.tar.xz
Checksums-Sha256:
 d9d54fb4d591e64d697c38c4393d978c81a457dc6837e2834c804465b1cf0330 1830 
libdigidoc_3.10.1.1208+ds1-2.dsc
 e84c3804860b50c54388de27218c728714cc5b49cecb752da622dcf807540498 3804 
libdigidoc_3.10.1.1208+ds1-2.debian.tar.xz
Files:
 437f9097a534e23eadcd39078e021dc2 1830 libs extra 
libdigidoc_3.10.1.1208+ds1-2.dsc
 67f4fd9665c8c03ad91c5ceabf564b50 3804 libs extra 
libdigidoc_3.10.1.1208+ds1-2.debian.tar.xz

-BEGIN PGP SIGNATURE-
Version: GnuPG v1

iQEcBAEBAgAGBQJWdpYcAAoJEJ1bI/kYT6UUnYQH/3nRI7SJMswAeO+Z605A/6Nd
S/ohHWcyrs4deOkhSbQQxHCBez+srL5qZiKZq8VkDmysiiZh/nwmlPJ6FYiyNlfs
c5IZJ1ceAb6tAgr1kpqevTWDrB9dI1uD+YxvHqsjIZ64LMeZwHuvupJRDlI3VKZk
VAq0ZXsPJgM3FRYK9tFfwDo5krbxFSxIPWDyFKjFwXVX4gjVGKQL49df0hajbGsn
C7zA3FEgZ/a8ayR2kIokKF9iqjF1S99Rugw/kn7q2bOvcP85TBM+sKeJzqew7oF0
YX6FYmrFqHCSvd7ga1ZJtuaQ8+to1ZK9Nhn5oN7aiLf9mJGK+D2N7dbcfSetRnw=
=nU1+
-END PGP SIGNATURE End Message ---

Bug#808472: gnu-efi copyright file is wrong, includes GPL-licensed code on arm

[Julian Andres Klode]

Package: gnu-efi
Severity: serious

[This is a reminder for me]

The copyright file only lists BSD-3-clause and BSD-4-clause
licenses currently.

Some parts are BSD-2-clause, though.

More importantly, and the reason for the serious severity:

Parts of arm and aarch64 code are GPL-2-licensed, though,
causing bootloaders built using them to be GPL-2.

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

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

-- 
Julian Andres Klode  - Debian Developer, Ubuntu Member

See http://wiki.debian.org/JulianAndresKlode and http://jak-linux.org/.

When replying, only quote what is necessary, and write each reply
directly below the part(s) it pertains to (`inline'). Thank you.

Bug#805391: src:rrdtool: FTBFS on mips: `FAIL: tune2`

[Niko Tyni]

Control: tag -1 patch

On Sat, Dec 19, 2015 at 02:45:03PM +0100, Aurelien Jarno wrote:
> On 2015-12-19 15:03, Niko Tyni wrote:

> > It's a latent bug in rrdtool that triggered with libc6 2.19-20 on mips.

> > The problem is that rrd_write() ends up calling memcpy(3) on overlapping
> > memory areas, which is explicitly prohibited in its documentation. With
> > libc6 2.19-20 on mips, this started zeroing out part of the areas under
> > some conditions.
 
> The change is likely due to the switch to the MIPS32R2 ISA on mips.
> A different code is used, so with a different undefined behaviour.

Right, thanks.

> Can't you replace memcpy calls with overlapping areas with a memmove
> instead? Even if the testsuite looks fine you will definitely have some
> corruptions with memcpy and overlapping area on other architectures too.

Sure, that works and the memmove() overhead is presumably negligible
with mmap'ed disk IO. Patch attached, I've tested that the package
builds on mips and amd64 with this and forwarded it upstream at

  https://github.com/oetiker/rrdtool-1.x/pull/693

Jean-Michel: this is somewhat urgent given it blocks the Perl 5.22
transition, so please let us know if you'd like an NMU.
-- 
Niko Tyni   nt...@debian.org
>From c0ac2ba5afeedd535367d78bf39cbe58e968a345 Mon Sep 17 00:00:00 2001
From: Niko Tyni 
Date: Sun, 20 Dec 2015 09:49:14 +0200
Subject: [PATCH] Use memmove instead of memcpy in rrd_write() to fix undefined
 behaviour

At least rrdtune ends up calling rrd_write() with the same memory
area for the source and the destination, causing undefined behaviour
that has been observed to actually break on the mips architecture.

Bug-Debian: https://bugs.debian.org/805391
Bug: https://github.com/oetiker/rrdtool-1.x/issues/688
---
 src/rrd_open.c | 3 ++-
 1 file changed, 2 insertions(+), 1 deletion(-)

diff --git a/src/rrd_open.c b/src/rrd_open.c
index b4e151e..9e05164 100644
--- a/src/rrd_open.c
+++ b/src/rrd_open.c
@@ -808,7 +808,8 @@ ssize_t rrd_write(
 rrd_set_error("attempting to write beyond end of file (%ld + %ld > %ld)",rrd_file->pos, count, old_size);
 return -1;
 }
-memcpy(rrd_simple_file->file_start + rrd_file->pos, buf, count);
+/* can't use memcpy since the areas overlap when tuning */
+memmove(rrd_simple_file->file_start + rrd_file->pos, buf, count);
 rrd_file->pos += count;
 return count;   /* mimmic write() semantics */
 #else
-- 
2.6.4

Processed: Re: Bug#805391: src:rrdtool: FTBFS on mips: `FAIL: tune2`

[Debian Bug Tracking System]

Processing control commands:

> tag -1 patch
Bug #805391 [src:rrdtool] src:rrdtool: FTBFS on mips: `FAIL: tune2`
Added tag(s) patch.

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

Bug#808454: libdata-faker-perl: FTBFS under some locales (eg. fr_CH.UTF-8)

[Chris Lamb]

Source: libdata-faker-perl
Version: 0.10-1
Severity: serious
Justification: fails to build from source
User: reproducible-bui...@lists.alioth.debian.org
Usertags: ftbfs locale
X-Debbugs-Cc: reproducible-bui...@lists.alioth.debian.org

Dear Maintainer,

libdata-faker-perl fails to build from source in unstable/amd64 undersome 
locales (eg. LANG="fr_CH.UTF-8"):

  [..]

  ok 3 - all methods return something true-ish
  1..3
  ok
  t/Data-Faker-Name.t ... 
  ok 1 - use Data::Faker;
  # Subtest: instance is returned
  ok 1 - An object of class 'Data::Faker' isa 'Data::Faker'
  1..1
  ok 2 - instance is returned
  # Subtest: all methods return something true-ish
  ok 1 - name_prefix
  ok 2 - last_name
  ok 3 - name_suffix
  ok 4 - name
  ok 5 - first_name
  1..5
  ok 3 - all methods return something true-ish
  1..3
  ok
  t/Data-Faker-PhoneNumber.t  
  ok 1 - use Data::Faker;
  # Subtest: instance is returned
  ok 1 - An object of class 'Data::Faker' isa 'Data::Faker'
  1..1
  ok 2 - instance is returned
  # Subtest: all methods return something
  ok 1 - phone_number
  1..1
  ok 3 - all methods return something
  1..3
  ok
  t/Data-Faker-StreetAddress.t .. 
  ok 1 - use Data::Faker;
  # Subtest: instance is returned
  ok 1 - An object of class 'Data::Faker' isa 'Data::Faker'
  1..1
  ok 2 - instance is returned
  # Subtest: all methods return something
  ok 1 - first_name
  ok 2 - secondary_unit_designator
  ok 3 - us_state
  ok 4 - secondary_unit_number
  ok 5 - street_address
  ok 6 - city
  ok 7 - name
  ok 8 - name_prefix
  ok 9 - street_suffix
  ok 10 - us_zip_code
  ok 11 - name_suffix
  ok 12 - last_name
  ok 13 - us_state_abbr
  ok 14 - street_name
  1..14
  ok 3 - all methods return something
  1..3
  ok
  
  #   Failed test 'ampm'
  #   at t/Data-Faker.t line 11.
  # Looks like you failed 1 test of 46.
  
  #   Failed test 'all methods return something true-ish'
  #   at t/Data-Faker.t line 13.
  # Looks like you failed 1 test of 3.
  t/Data-Faker.t  
  ok 1 - use Data::Faker;
  # Subtest: instance is returned
  ok 1 - An object of class 'Data::Faker' isa 'Data::Faker'
  1..1
  ok 2 - instance is returned
  # Subtest: all methods return something true-ish
  ok 1 - phone_number
  ok 2 - city
  ok 3 - unixtime
  ok 4 - company
  ok 5 - server_name
  ok 6 - time
  ok 7 - last_name
  ok 8 - us_state
  ok 9 - date_format
  ok 10 - network_service
  ok 11 - street_name
  ok 12 - ampm_format
  ok 13 - datetime_format
  ok 14 - time_format
  ok 15 - us_zip_code
  ok 16 - first_name
  ok 17 - domain_word
  ok 18 - job_title
  ok 19 - month_abbr
  ok 20 - ip_address
  ok 21 - time_locale
  ok 22 - weekday
  ok 23 - weekday_abbr
  ok 24 - date
  ok 25 - dayofmonth
  ok 26 - company_suffix
  ok 27 - name_suffix
  ok 28 - month
  ok 29 - name
  ok 30 - century
  ok 31 - username
  ok 32 - street_address
  not ok 33 - ampm
  ok 34 - datetime_locale
  ok 35 - rfc822
  ok 36 - date_locale
  ok 37 - email
  ok 38 - street_suffix
  ok 39 - domain_name
  ok 40 - sqldate
  ok 41 - name_prefix
  ok 42 - hostname
  ok 43 - us_state_abbr
  ok 44 - secondary_unit_designator
  ok 45 - domain_suffix
  ok 46 - secondary_unit_number
  1..46
  not ok 3 - all methods return something true-ish
  1..3
  Dubious, test returned 1 (wstat 256, 0x100)
  Failed 1/3 subtests 
  t/datafaker.t . 
  ok 1 - Run for --help
  ok 2 - Results for --help
  ok 3 - Run for --help
  ok 4 - Results for --help
  ok 5 - Run for --datatypes
  ok 6 - Results for --datatypes
  1..6
  ok
  
  Test Summary Report
  ---
  t/Data-Faker-DateTime.t (Wstat: 256 Tests: 3 Failed: 1)
Failed test:  3
Non-zero exit status: 1
  t/Data-Faker.t  (Wstat: 256 Tests: 3 Failed: 1)
Failed test:  3
Non-zero exit status: 1
  Files=8, Tests=27,  2 wallclock secs ( 0.08 usr  0.03 sys +  1.09 cusr  0.13 
csys =  1.33 CPU)
  Result: FAIL
  Failed 2/8 test programs. 2/27 subtests failed.
  Makefile:848: recipe for target 'test_dynamic' failed
  make[1]: *** [test_dynamic] Error 255
  make[1]: Leaving directory '/build/libdata-faker-perl-0.10'
  dh_auto_test: make -j1 test TEST_VERBOSE=1 returned exit code 2
  debian/rules:4: recipe for target 'build' failed
  make: *** [build] Error 2
  dpkg-buildpackage: erreur: debian/rules build a produit une erreur de sortie 
de type 2

  [..]

The full build log is attached or can be viewed here:


https://reproducible.debian.net/logs/unstable/amd64/libdata-faker-perl_0.10-1.build2.log.gz


Regards,

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

Bug#806666: Should advene be removed?

[Moritz Mühlenhoff]

On Mon, Nov 30, 2015 at 02:42:07PM +0100, Olivier Aubert wrote:
> I am the upstream maintainer of Advene. The project is not abandoned,
> but the port to gtk3 + gstreamer 1.0 is not simply trivial, and needs
> more time than I can invest right now. It is still in my todo list, but
> it will not be ready for the next Debian release.
> 
> It is indeed already removed from testing (see #785818).

Ok, if it won't be fixed before the stretch release, then let's remove it
from unstable for now (it can be re-introduced once fixed upstream).

We're also aiming for removal of the reverse dependencies from
unstable at this point.

Cheers,
Moritz

Bug#806586: Please keep playitslowly in Debian

[Moritz Mühlenhoff]

On Fri, Dec 04, 2015 at 05:35:32PM +0100, treb...@tuxfamily.org wrote:
> Hi all,
> I'd say that I'd like Debian to keep it in since I'm using it.
> Just my 2 cents.
> Olivier

We won't be able to keep it unless it's get ported/maintained.

Cheers,
Moritz

Bug#800179: marked as done (empire-hub: Please migrate a supported debhelper compat level)

[Debian Bug Tracking System]

Your message dated Sun, 20 Dec 2015 11:18:32 -0200
with message-id 

Bug#805160: marked as done (mangler: FTBFS: manglerg15.h:126:1: error: narrowing conversion of '240' from 'int' to 'char' inside { } [-Wnarrowing])

[Debian Bug Tracking System]

Your message dated Mon, 21 Dec 2015 06:55:48 +
with message-id 
and subject line Bug#805160: fixed in mangler 1.2.5-3
has caused the Debian Bug report #805160,
regarding mangler: FTBFS: manglerg15.h:126:1: error: narrowing conversion of 
'240' from 'int' to 'char' inside { } [-Wnarrowing]
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.)


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

Dear Maintainer,

mangler fails to build from source in unstable/amd64:

  [..]

  manglerg15.h:126:1: error: narrowing conversion of '240' from 'int' to
  'char' inside { } [-Wnarrowing]
  manglerg15.h:126:1: error: narrowing conversion of '252' from 'int' to
  'char' inside { } [-Wnarrowing]
  manglerg15.h:126:1: error: narrowing conversion of '255' from 'int' to
  'char' inside { } [-Wnarrowing]
  manglerg15.h:126:1: error: narrowing conversion of '248' from 'int' to
  'char' inside { } [-Wnarrowing]
  manglerg15.h:126:1: error: narrowing conversion of '252' from 'int' to
  'char' inside { } [-Wnarrowing]
  manglerg15.h:126:1: error: narrowing conversion of '255' from 'int' to
  'char' inside { } [-Wnarrowing]
  manglerg15.h:126:1: error: narrowing conversion of '248' from 'int' to
  'char' inside { } [-Wnarrowing]
  manglerg15.h:126:1: error: narrowing conversion of '248' from 'int' to
  'char' inside { } [-Wnarrowing]
  manglerg15.h:126:1: error: narrowing conversion of '255' from 'int' to
  'char' inside { } [-Wnarrowing]
  manglerg15.h:126:1: error: narrowing conversion of '255' from 'int' to
  'char' inside { } [-Wnarrowing]
  manglerg15.h:126:1: error: narrowing conversion of '248' from 'int' to
  'char' inside { } [-Wnarrowing]
  manglerg15.h:126:1: error: narrowing conversion of '255' from 'int' to
  'char' inside { } [-Wnarrowing]
  manglerg15.h:126:1: error: narrowing conversion of '255' from 'int' to
  'char' inside { } [-Wnarrowing]
  manglerg15.h:126:1: error: narrowing conversion of '252' from 'int' to
  'char' inside { } [-Wnarrowing]
  manglerg15.h:126:1: error: narrowing conversion of '255' from 'int' to
  'char' inside { } [-Wnarrowing]
  manglerg15.h:126:1: error: narrowing conversion of '255' from 'int' to
  'char' inside { } [-Wnarrowing]
  manglerg15.h:126:1: error: narrowing conversion of '252' from 'int' to
  'char' inside { } [-Wnarrowing]
  manglerg15.h:126:1: error: narrowing conversion of '255' from 'int' to
  'char' inside { } [-Wnarrowing]
  manglerg15.h:126:1: error: narrowing conversion of '255' from 'int' to
  'char' inside { } [-Wnarrowing]
  manglerg15.h:126:1: error: narrowing conversion of '252' from 'int' to
  'char' inside { } [-Wnarrowing]
  manglerg15.h:126:1: error: narrowing conversion of '255' from 'int' to
  'char' inside { } [-Wnarrowing]
  manglerg15.h:126:1: error: narrowing conversion of '254' from 'int' to
  'char' inside { } [-Wnarrowing]
  manglerg15.h:126:1: error: narrowing conversion of '255' from 'int' to
  'char' inside { } [-Wnarrowing]
  manglerg15.h:126:1: error: narrowing conversion of '254' from 'int' to
  'char' inside { } [-Wnarrowing]
  manglerg15.h:126:1: error: narrowing conversion of '255' from 'int' to
  'char' inside { } [-Wnarrowing]
  manglerg15.h:126:1: error: narrowing conversion of '255' from 'int' to
  'char' inside { } [-Wnarrowing]
  manglerg15.h:126:1: error: narrowing conversion of '255' from 'int' to
  'char' inside { } [-Wnarrowing]
  manglerg15.h:126:1: error: narrowing conversion of '252' from 'int' to
  'char' inside { } [-Wnarrowing]
  manglerg15.h:126:1: error: narrowing conversion of '255' from 'int' to
  'char' inside { } [-Wnarrowing]
  manglerg15.h:126:1: error: narrowing conversion of '240' from 'int' to
  'char' inside { } [-Wnarrowing]
  manglerg15.h:126:1: error: narrowing conversion of '128' from 'int' to
  'char' inside { } [-Wnarrowing]
  Makefile:547: recipe for target 'mangler.o' failed
  make[4]: *** [mangler.o] Error 1
  make[4]: Leaving directory '/build/mangler-1.2.5/src'
  Makefile:435: recipe for target 'all-recursive' failed
  make[3]: *** [all-recursive] Error 1
  make[3]: Leaving directory '/build/mangler-1.2.5'
  Makefile:367: recipe for target 'all' failed
  make[2]: *** [all] Error 2
  make[2]: Leaving directory '/build/mangler-1.2.5'
  dh_auto_build: make -j1 returned exit 

Processed: Update patches

[Debian Bug Tracking System]

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

> tags 808474 patch upstream fixed pending confirmed
Bug #808474 [liblemonldap-ng-manager-perl] liblemonldap-ng-manager-perl: 
Manager shows garbage where the menu is supposed to be
Added tag(s) confirmed, upstream, pending, fixed, and patch.
> tags 808473 fixed pending confirmed
Bug #808473 [liblemonldap-ng-manager-perl] liblemonldap-ng-manager-perl: 
manager unaccessible without doc symlink in /var/lib/lemonldap-ng
Added tag(s) fixed, confirmed, and pending.
>
End of message, stopping processing here.

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

Bug#807349: dwww: FTBFS: error: expected identifier or '(' before '__extension__'

[Robert Luberda]

reassign 807349 publib-dev 0.40-1
thanks

Chris Lamb writes:
> Source: dwww
> Version: 1.12.1
> 
> Dear Maintainer,
> 
> dwww fails to build from source in unstable/amd64:
> 
>   [..]
>   /usr/include/publib/strutil.h:67:7: error: expected identifier or '('
>   before '__extension__'
>char *strndup(const char *, size_t);

Hi,

I think the problem lies in publib-dev that declares strndup, which now
is a macro, see the following clang diagnostics:

 In file included from /usr/include/publib.h:51:
 /usr/include/publib/strutil.h:67:7: error: expected identifier or '('
 char *strndup(const char *, size_t);
 ^
 /usr/include/i386-linux-gnu/bits/string2.h:1319:26: note: expanded from
macro 'strndup'
 # define strndup(s, n) __strndup (s, n)
 ^
 /usr/include/i386-linux-gnu/bits/string2.h:1300:4: note: expanded from
 macro '__strndup'
 (__extension__ (__builtin_constant_p (s) && __string2_1bptr_p (s) \
 ^



The more general issue in publib is that it uses names reserved by the
GNU C library, let me quote
http://www.gnu.org/software/libc/manual/html_node/Reserved-Names.html;
  "Names beginning with ‘str’, ‘mem’, or ‘wcs’ followed by a lowercase
letter are reserved for additional string and array functions. See
String and Array Utilities."




Regards,
robert

Processed: Re: Bug#807349: dwww: FTBFS: error: expected identifier or '(' before '__extension__'

[Debian Bug Tracking System]

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

> reassign 807349 publib-dev 0.40-1
Bug #807349 [src:dwww] dwww: FTBFS: error: expected identifier or '(' before 
'__extension__'
Bug reassigned from package 'src:dwww' to 'publib-dev'.
No longer marked as found in versions dwww/1.12.1.
Ignoring request to alter fixed versions of bug #807349 to the same values 
previously set
Bug #807349 [publib-dev] dwww: FTBFS: error: expected identifier or '(' before 
'__extension__'
Marked as found in versions publib/0.40-1.
> thanks
Stopping processing here.

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

Bug#808480: libdevel-bt-perl: FTBFS on mips*: test failures

[Niko Tyni]

Package: libdevel-bt-perl
Version: 0.06-3
Severity: serious
Tags: sid patch

Control: block 796345 with -1

This package failed to build on mips and mipsel with Perl 5.22 in unstable.

#   Failed test 'perl backtrace for SIGABRT'
#   at t/basic.t line 26.
#   '#0  0x77999480 in waitpid () from 
/lib/mips-linux-gnu/libpthread.so.0
# #1  0x7779d178 in backtrace () at bt.xs:187
# #2  signal_handler (sig=) at bt.xs:194
# #3  
# #4  0x77837240 in kill () from /lib/mips-linux-gnu/libc.so.6
# #5  0x00547b28 in Perl_apply ()
# '
# doesn't match '(?^:\bperl_run\b)'

While this looks very similar to #721421, it may not be quite the same issue.

I tried on minkus.d.o, and building with perl-debug installed fixes it.
Given the test suite is looking for /perl_run/ in the backtrace, it
seems fair to require that. I think a runtime dependency on perl-debug
would make sense too: this is presumably meant to get useful backtraces,
and debugging symbols help a lot with that.

(Not sure what's going to happen with perl-debug now that we've got
automatic debug symbol packages, but we can look at that after the
Perl 5.22 transition that this is blocking.)
-- 
Niko Tyni   nt...@debian.org

Bug#808482: deborphan: FTBFS: deborphan.h:39:14: error: expected identifier

[Chris West (Faux)]

Source: deborphan
Version: 1.7.28.8-0.2
Severity: serious
Justification: fails to build from source
Tags: sid stretch
User: reproducible-bui...@lists.alioth.debian.org
Usertags: ftbfs
X-Debbugs-CC: reproducible-bui...@lists.alioth.debian.org

Dear Maintainer,

The package fails to build:

Making all in src
make[2]: Entering directory '/deborphan-1.7.28.8/src'
if gcc -DLOCALEDIR=\"/usr/share/locale\" 
-DKEEPER_FILE=\"/var/lib/deborphan/keep\" -DHAVE_CONFIG_H -I. -I. -I../include 
-I../include-O2 -g -MT deborphan.o -MD -MP -MF ".deps/deborphan.Tpo" -c -o 
deborphan.o deborphan.c; \
then mv -f ".deps/deborphan.Tpo" ".deps/deborphan.Po"; else rm -f 
".deps/deborphan.Tpo"; exit 1; fi
In file included from /usr/include/string.h:634:0,
 from deborphan.c:14:
../include/deborphan.h:39:14: error: expected identifier or ‘(’ before 
‘__extension__’
 extern char *strsep(char **, const char *);
  ^
../include/deborphan.h:39:14: error: expected identifier or ‘(’ before ‘)’ token
 extern char *strsep(char **, const char *);
  ^
In file included from deborphan.c:35:0:
../include/xalloc.h:13:21: warning: inline function ‘xstrdup’ declared but 
never defined
 extern inline char *xstrdup(const char *s);
 ^
../include/xalloc.h:12:21: warning: inline function ‘xrealloc’ declared but 
never defined
 extern inline void *xrealloc(void *ptr, size_t size);
 ^
../include/xalloc.h:11:21: warning: inline function ‘xmalloc’ declared but 
never defined
 extern inline void *xmalloc(size_t size);
 ^
../include/xalloc.h:10:21: warning: inline function ‘xcalloc’ declared but 
never defined
 extern inline void *xcalloc(size_t nmemb, size_t size);
 ^
In file included from deborphan.c:20:0:
../include/deborphan.h:176:28: warning: inline function ‘strhash’ declared but 
never defined
 extern inline unsigned int strhash(const char *line);
^
../include/deborphan.h:175:20: warning: inline function ‘strstripchr’ declared 
but never defined
 extern inline void strstripchr(char *s, int c);
^
Makefile:296: recipe for target 'deborphan.o' failed
make[2]: *** [deborphan.o] Error 1
make[2]: Leaving directory '/deborphan-1.7.28.8/src'
Makefile:282: recipe for target 'all-recursive' failed

Full build log:
https://reproducible.debian.net/rb-pkg/unstable/amd64/deborphan.html

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

Bug#808484: django-stronghold: FTBFS: AttributeError: 'module' object has no attribute 'tests'

[Chris West (Faux)]

Source: django-stronghold
Version: 0.2.7+debian-1
Severity: serious
Justification: fails to build from source
Tags: sid stretch
User: reproducible-bui...@lists.alioth.debian.org
Usertags: ftbfs
X-Debbugs-CC: reproducible-bui...@lists.alioth.debian.org

Dear Maintainer,

The package fails to build:

copying stronghold/tests/testutils.py -> 
/django-stronghold-0.2.7+debian/.pybuild/pythonX.Y_3.4/build/stronghold/tests
   debian/rules override_dh_auto_test
make[1]: Entering directory '/django-stronghold-0.2.7+debian'
python2 test_project/manage.py test --pythonpath=. 
--settings=test_project.settings stronghold.tests
Traceback (most recent call last):
  File "test_project/manage.py", line 10, in 
execute_from_command_line(sys.argv)
  File "/usr/lib/python2.7/dist-packages/django/core/management/__init__.py", 
line 350, in execute_from_command_line
utility.execute()
  File "/usr/lib/python2.7/dist-packages/django/core/management/__init__.py", 
line 342, in execute
self.fetch_command(subcommand).run_from_argv(self.argv)
  File 
"/usr/lib/python2.7/dist-packages/django/core/management/commands/test.py", 
line 30, in run_from_argv
super(Command, self).run_from_argv(argv)
  File "/usr/lib/python2.7/dist-packages/django/core/management/base.py", line 
348, in run_from_argv
self.execute(*args, **cmd_options)
  File 
"/usr/lib/python2.7/dist-packages/django/core/management/commands/test.py", 
line 74, in execute
super(Command, self).execute(*args, **options)
  File "/usr/lib/python2.7/dist-packages/django/core/management/base.py", line 
399, in execute
output = self.handle(*args, **options)
  File 
"/usr/lib/python2.7/dist-packages/django/core/management/commands/test.py", 
line 90, in handle
failures = test_runner.run_tests(test_labels)
  File "/usr/lib/python2.7/dist-packages/django/test/runner.py", line 531, in 
run_tests
suite = self.build_suite(test_labels, extra_tests)
  File "/usr/lib/python2.7/dist-packages/django/test/runner.py", line 422, in 
build_suite
tests = self.test_loader.loadTestsFromName(label)
  File "/usr/lib/python2.7/unittest/loader.py", line 100, in loadTestsFromName
parent, obj = obj, getattr(obj, part)
AttributeError: 'module' object has no attribute 'tests'
debian/rules:10: recipe for target 'override_dh_auto_test' failed
make[1]: *** [override_dh_auto_test] Error 1
make[1]: Leaving directory '/django-stronghold-0.2.7+debian'
debian/rules:7: recipe for target 'build' failed

Full build log:
https://reproducible.debian.net/rb-pkg/unstable/amd64/django-stronghold.html

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

Bug#808488: brutalchess: FTBFS: fatal error: freetype2/freetype.h: No such file or directory

[Chris West (Faux)]

Source: brutalchess
Version: 0.5.2+dfsg-6
Severity: serious
Justification: fails to build from source
Tags: sid stretch
User: reproducible-bui...@lists.alioth.debian.org
Usertags: ftbfs
X-Debbugs-CC: reproducible-bui...@lists.alioth.debian.org

Dear Maintainer,

The package fails to build:

g++ -DHAVE_CONFIG_H -I. -DPREFIX_DIR=\"/usr/share/games/brutalchess/\" 
-DMODELS_DIR=\"/usr/share/games/brutalchess//models/\" 
-DART_DIR=\"/usr/share/games/brutalchess//art/\" -DFONTS_DIR=\"\"  
-D_FORTIFY_SOURCE=2  -g -O2 -fPIE -fstack-protector-strong -Wformat 
-Werror=format-security  -I/usr/include/SDL -D_GNU_SOURCE=1 -D_REENTRANT 
-I/usr/include/freetype2 -c -o brutalchess.o brutalchess.cpp
In file included from brutalchess.cpp:26:0:
fontloader.h:16:32: fatal error: freetype2/freetype.h: No such file or directory
compilation terminated.
Makefile:546: recipe for target 'brutalchess.o' failed
make[3]: *** [brutalchess.o] Error 1
make[3]: Leaving directory '/brutalchess-0.5.2+dfsg/src'
Makefile:355: recipe for target 'all' failed

Full build log:
https://reproducible.debian.net/rb-pkg/unstable/amd64/brutalchess.html

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

Bug#808486: dieharder: FTBFS: unistd.h: error: unknown type name 'intptr_t'

[Chris West (Faux)]

Source: dieharder
Version: 3.31.1-5
Severity: serious
Justification: fails to build from source
Tags: sid stretch
User: reproducible-bui...@lists.alioth.debian.org
Usertags: ftbfs
X-Debbugs-CC: reproducible-bui...@lists.alioth.debian.org

Dear Maintainer,

The package fails to build:

libtool: compile:  gcc -DHAVE_CONFIG_H -I. -I.. -DVERSION=3.31.1 
-DLITTLE_ENDIAN=1 -I ../include -I /usr/include -std=c99 -Wall -pedantic -Wall 
-pipe -fexceptions -D_REENTRANT -g -O3 -MT libdieharder_la-bits.lo -MD -MP -MF 
.deps/libdieharder_la-bits.Tpo -c bits.c  -fPIC -DPIC -o 
.libs/libdieharder_la-bits.o
In file included from ../include/dieharder/libdieharder.h:22:0,
 from bits.c:7:
/usr/include/unistd.h:1043:20: error: unknown type name 'intptr_t'
 extern void *sbrk (intptr_t __delta) __THROW;
^
bits.c: In function 'fill_uint_buffer':
bits.c:407:15: warning: variable 'bufbits' set but not used 
[-Wunused-but-set-variable]
  unsigned int bufbits,bdelta;
   ^
Makefile:687: recipe for target 'libdieharder_la-bits.lo' failed
make[2]: *** [libdieharder_la-bits.lo] Error 1

Full build log:
https://reproducible.debian.net/rb-pkg/unstable/amd64/dieharder.html

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

Bug#808494: junit4: FTBFS: Plugin com.google.code.maven-replacer-plugin:replacer:1.5.3 or one of its dependencies could not be resolved

[Chris West (Faux)]

Source: junit4
Version: 4.12-2
Severity: serious
Justification: fails to build from source
Tags: sid 
User: reproducible-bui...@lists.alioth.debian.org
Usertags: ftbfs
X-Debbugs-CC: reproducible-bui...@lists.alioth.debian.org

Dear Maintainer,

The package fails to build:

cd . && /usr/lib/jvm/default-java/bin/java -noverify -cp 
/usr/share/maven/boot/plexus-classworlds-2.x.jar:/usr/lib/jvm/default-java/lib/tools.jar
  -Dclassworlds.conf=/etc/maven/m2-debian.conf -Dmaven.home=/usr/share/maven 
-Dmaven.multiModuleProjectDirectory=/junit4-4.12 
org.codehaus.plexus.classworlds.launcher.Launcher 
-s/etc/maven/settings-debian.xml 
-Dmaven.repo.local=/junit4-4.12/debian/maven-repo  package -DskipTests
[INFO] Scanning for projects...
[INFO] 
[INFO] 
[INFO] Building JUnit 4.12
[INFO] 
[INFO] 
[INFO] --- maven-enforcer-plugin:1.0:enforce (enforce-versions) @ junit ---
[INFO] 
[INFO] --- replacer:1.5.3:replace (default) @ junit ---
[INFO] 
[INFO] BUILD FAILURE
[INFO] 
[INFO] Total time: 0.589 s
[INFO] Finished at: 2015-12-20T14:00:33+00:00
[INFO] Final Memory: 8M/360M
[INFO] 
[ERROR] Failed to execute goal 
com.google.code.maven-replacer-plugin:replacer:1.5.3:replace (default) on 
project junit: Execution default of goal 
com.google.code.maven-replacer-plugin:replacer:1.5.3:replace failed: Plugin 
com.google.code.maven-replacer-plugin:replacer:1.5.3 or one of its dependencies 
could not be resolved: Cannot access central 
(https://repo.maven.apache.org/maven2) in offline mode and the artifact 
org.codehaus.plexus:plexus-utils:jar:1.1 has not been downloaded from it 
before. -> [Help 1]
[ERROR] 
[ERROR] To see the full stack trace of the errors, re-run Maven with the -e 
switch.
[ERROR] Re-run Maven using the -X switch to enable full debug logging.
[ERROR] 
[ERROR] For more information about the errors and possible solutions, please 
read the following articles:
[ERROR] [Help 1] 
http://cwiki.apache.org/confluence/display/MAVEN/PluginResolutionException
/usr/share/cdbs/1/class/maven.mk:92: recipe for target 'mvn-build' failed
make: *** [mvn-build] Error 1
dpkg-buildpackage: error: debian/rules build gave error exit status 2

Full build log:
https://reproducible.debian.net/rb-pkg/unstable/amd64/junit4.html

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

Bug#808401: Bug#808401: plastimatch: FTBFS: itkGDCMSeriesFileNames.h:25:29: fatal error: gdcmSerieHelper.h: No such file or directory

[Gert Wollny]

On Sat, 2015-12-19 at 22:55 +0100, Andreas Tille wrote:
> Hi Gert,
> 
> On Sat, Dec 19, 2015 at 09:32:58PM +0100, Gert Wollny wrote:
> > It seems that there is a conflict in which gdcm version is used. 
> > The log says that gdcm-2.6 was found but later the include files 
> > for gdcm-2.4 are used.
> > 
> > I guess itk needs to be rebuild against gdcm-2.6 since it seems to 
> > pull in the old version.
> 
> Sounds sensible.  Do you need any help for this?

Well, it turns out that Emilio from the release team already tried to
build ITK against the new gdcm. 

Which means this bug is now blocked by #808491, which is something for
which I need help from upstream ITK and/or GDCM. 

Best,  
Gert 

Bug#808464: suddenly being asked for interactive keyboard configuration

[gregor herrmann]

On Sun, 20 Dec 2015 12:27:11 +0100, Holger Levsen wrote:

> Which do "apt-get install -y --install-recommends diffoscope" in sid, which 
> now fails like this: 
> 
> ...
> Setting up keyboard-configuration (1.134) ...
> debconf: unable to initialize frontend: Dialog
> debconf: (Dialog frontend will not work on a dumb terminal, an emacs shell 
> buffer, or without a controlling terminal.)
> debconf: falling back to frontend: Readline
> Configuring keyboard-configuration
> --
[..]
 
>  is it using DEBIAN_FRONTEND=noninteractive ?
>  ntyni: yes. the jenkins code used here hasnt changed at all. 
>  h01ger: I'm guessing DEBIAN_FRONTEND=noninteractive never took effect 
> for some reason and the Dialog frontend is now falling back to a different 
> frontend (Readline) that tries harder to ask its questions even without a 
> real 
> terminal/stdin
>  hm
>  h01ger: I wouldn't expect those messages about Dialog and Readline 
> frontends at all if DEBIAN_FRONTEND=noninteractive was in effect
> * h01ger nods
>  h01ger: but I'm not 100% positive on that
>  
> https://jenkins.debian.net/job/reproducible_setup_schroot_unstable_diffoscope_amd64_jenkins/lastBuild/console
>  
> weirly enough has a different frontend it seems

Quick test:
- cowbuilder sid amd64 chroot
- a) DEBIAN_FRONTEND=noninteractive, b) unset DEBIAN_FRONTEND
- apt-get install -y --install-recommends diffoscope

In case a) I get no questions, as expected; in case b) I also get

Setting up keyboard-configuration (1.134) ...
debconf: unable to initialize frontend: Dialog
debconf: (No usable dialog-like program is installed, so the dialog based 
frontend cannot be used. at /usr/share/perl5/Debconf/FrontEnd/Dialog.pm line 
76.)
debconf: falling back to frontend: Readline
Configuring keyboard-configuration
--


This looks like DEBIAN_FRONTEND=noninteractive is working as
expected; which doesn't answer what's happening in your
jenkins/reproduucible job :/

Hm, a tiny difference is "Dialog frontend will not work" vs. "No
usable dialog-like program is installed". But still, the whole
question should be skipped with DEBIAN_FRONTEND=noninteractive.

Cheers,
gregor

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


signature.asc
Description: Digital Signature

Bug#808499: ladvd: FTBFS: error: #warning "_BSD_SOURCE and _SVID_SOURCE are deprecated, use _DEFAULT_SOURCE" [-Werror=cpp]

[Chris West (Faux)]

Source: ladvd
Version: 1.1.1~pre1-1
Severity: serious
Justification: fails to build from source
Tags: sid 
User: reproducible-bui...@lists.alioth.debian.org
Usertags: ftbfs
X-Debbugs-CC: reproducible-bui...@lists.alioth.debian.org

Dear Maintainer,

The package fails to build:

libtool: compile:  gcc -DHAVE_CONFIG_H -I. -I../../src -D_FORTIFY_SOURCE=2 
-Wall -Werror -Wformat -Wformat-security -DPIE -D_FORTIFY_SOURCE=2 --param 
ssp-buffer-size=4 -fstack-protector -g -O2 -fstack-protector-strong -Wformat 
-Werror=format-security -isystem /usr/include/bsd -DLIBBSD_OVERLAY -MT 
compat/vis.lo -MD -MP -MF compat/.deps/vis.Tpo -c ../../src/compat/vis.c  -fPIC 
-DPIC -o compat/.libs/vis.o
In file included from /usr/include/ctype.h:25:0,
 from ../../src/compat/vis.c:38:
/usr/include/features.h:148:3: error: #warning "_BSD_SOURCE and _SVID_SOURCE 
are deprecated, use _DEFAULT_SOURCE" [-Werror=cpp]
 # warning "_BSD_SOURCE and _SVID_SOURCE are deprecated, use _DEFAULT_SOURCE"
   ^
cc1: all warnings being treated as errors
Makefile:580: recipe for target 'compat/vis.lo' failed
make[3]: *** [compat/vis.lo] Error 1
make[3]: Leaving directory '/ladvd-1.1.1~pre1/build/src'

Full build log:
https://reproducible.debian.net/rb-pkg/unstable/amd64/ladvd.html

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

Processed: Re: empire-hub: Please migrate a supported debhelper compat level

[Debian Bug Tracking System]

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

> reopen 800179 !
Bug #800179 {Done: Raphael mota } [src:empire-hub] 
empire-hub: Please migrate a supported debhelper compat level
Bug reopened
Changed Bug submitter to 'eribe...@debian.org' from 'ni...@thykier.net'
Ignoring request to alter fixed versions of bug #800179 to the same values 
previously set
> thanks
Stopping processing here.

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

Bug#800179: empire-hub: Please migrate a supported debhelper compat level

[Eriberto Mota]

reopen 800179 !
thanks


Hi,

I am reopening this bug because it must be closed by an upload
(Wanna-Build will close the bug, via 'Closes' statement in
debian/changelog, after the Delay time).

Please, temporarily, ignore the last message with a debdiff because,
as sponsor, I will ask to Raphael for some changes in NMU packaging.

Regards,

Eriberto

Bug#808511: paps: FTBFS: libpaps.c:28:21: fatal error: ftglyph.h: No such file or directory

[Chris West (Faux)]

Source: paps
Version: 0.6.8-7
Severity: serious
Justification: fails to build from source
Tags: sid stretch
User: reproducible-bui...@lists.alioth.debian.org
Usertags: ftbfs
X-Debbugs-CC: reproducible-bui...@lists.alioth.debian.org

Dear Maintainer,

The package fails to build:

Making all in src
make[3]: Entering directory '/paps-0.6.8/src'
/bin/bash ../libtool  --tag=CC   --mode=compile x86_64-linux-gnu-gcc 
-DHAVE_CONFIG_H -I. -I..  -I/usr/include/pango-1.0 -I/usr/include/harfbuzz 
-I/usr/include/pango-1.0 -I/usr/include/glib-2.0 
-I/usr/lib/x86_64-linux-gnu/glib-2.0/include -I/usr/include/freetype2-g -O2 
-MT libpaps.lo -MD -MP -MF .deps/libpaps.Tpo -c -o libpaps.lo libpaps.c
libtool: compile:  x86_64-linux-gnu-gcc -DHAVE_CONFIG_H -I. -I.. 
-I/usr/include/pango-1.0 -I/usr/include/harfbuzz -I/usr/include/pango-1.0 
-I/usr/include/glib-2.0 -I/usr/lib/x86_64-linux-gnu/glib-2.0/include 
-I/usr/include/freetype2 -g -O2 -MT libpaps.lo -MD -MP -MF .deps/libpaps.Tpo -c 
libpaps.c  -fPIC -DPIC -o .libs/libpaps.o
libpaps.c:28:21: fatal error: ftglyph.h: No such file or directory
compilation terminated.
Makefile:546: recipe for target 'libpaps.lo' failed
make[3]: *** [libpaps.lo] Error 1
make[3]: Leaving directory '/paps-0.6.8/src'
Makefile:478: recipe for target 'all-recursive' failed
make[2]: *** [all-recursive] Error 1
make[2]: Leaving directory '/paps-0.6.8'

Full build log:
https://reproducible.debian.net/rb-pkg/unstable/amd64/paps.html

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

Bug#808505: invesalius: Uninstallable due to conflicting dependencies (python-vtk vs python-vtk6)

[Axel Beckert]

Hi,

Axel Beckert wrote:
> invesalius has become uninstallable since one of transitions a few weeks
> ago (maybe the GSL-2.0 transition).

I cited the wrong line from my "reinstall after transition" notes. It
is of course the VTK transition from November which caused this:

https://release.debian.org/transitions/html/vtk6.html
https://bugs.debian.org/749395

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