Processed: found 837714 in 3.1.2-11

2016-09-13 Thread Debian Bug Tracking System 
Processing commands for cont...@bugs.debian.org:

> found 837714 3.1.2-11
Bug #837714 [src:libarchive] libarchive: CVE-2016-5418: Archive Entry with type 
1 (hardlink), but has a non-zero data size file overwrite
Marked as found in versions libarchive/3.1.2-11.
> thanks
Stopping processing here.

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

Bug#837714: libarchive: CVE-2016-5418: Archive Entry with type 1 (hardlink), but has a non-zero data size file overwrite

2016-09-13 Thread Salvatore Bonaccorso 
On Tue, Sep 13, 2016 at 09:41:49PM +0200, Salvatore Bonaccorso wrote:
> [0] https://security-tracker.debian.org/tracker/CVE-2016-5418
> [1] 
> https://git.centos.org/blob/rpms!libarchive.git/9952851f8b327a8c93d26a5873c190c1fb09ae6c/SOURCES!libarchive-3.1.2-CVE-2016-5418.patch;jsessionid=1dexz8h9qdewibih5aonbu3
> [2] 
> https://git.centos.org/blob/rpms!libarchive.git/9952851f8b327a8c93d26a5873c190c1fb09ae6c/SOURCES!libarchive-3.1.2-CVE-2016-5418-variation.patch;jsessionid=1dexz8h9qdewibih5aonbu3
> [3] 
> https://github.com/libarchive/libarchive/commit/dfd6b54ce33960e420fb206d8872fb759b577ad9

Please note, not (yet) clear if [3] ist the only one. The CVE relates
to https://bugzilla.redhat.com/show_bug.cgi?id=1362601 and to 
http://seclists.org/oss-sec/2016/q3/255 . 

Regards,
Salvatore

Bug#837263: marked as done (smlnj: FTBFS: Can't locate mltex.thm in @INC)

2016-09-13 Thread Debian Bug Tracking System 
Your message dated Wed, 14 Sep 2016 04:31:02 +
with message-id 
and subject line Bug#837263: fixed in smlnj 110.79-2
has caused the Debian Bug report #837263,
regarding smlnj: FTBFS: Can't locate mltex.thm in @INC
to be marked as done.

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

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


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

Hi,

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

Relevant part (hopefully):
> make[3]: Entering directory '/<>/build-dir/MLRISC/Doc/pictures'
> # @if [ ! -d eps ]; then mkdir eps; fi
> make[3]: Leaving directory '/<>/build-dir/MLRISC/Doc/pictures'
> perl mltex2html ../latex/mlrisc.tex
> Unescaped left brace in regex is deprecated, passed through in regex; marked 
> by <-- HERE in m/\\end{ <-- HERE verbatim}/ at mltex2html line 1269.
> Unescaped left brace in regex is deprecated, passed through in regex; marked 
> by <-- HERE in m/\\end{ <-- HERE alltt}/ at mltex2html line 1279.
> Unescaped left brace in regex is deprecated, passed through in regex; marked 
> by <-- HERE in m/\\begin{ <-- HERE SML}/ at mltex2html line 1299.
> Unescaped left brace in regex is deprecated, passed through in regex; marked 
> by <-- HERE in m/\\end{ <-- HERE SML}/ at mltex2html line 1300.
> Unescaped left brace in regex is deprecated, passed through in regex; marked 
> by <-- HERE in m/\\begin{ <-- HERE code}/ at mltex2html line 1301.
> Unescaped left brace in regex is deprecated, passed through in regex; marked 
> by <-- HERE in m/\\end{ <-- HERE code}/ at mltex2html line 1302.
> Unescaped left brace in regex is deprecated, passed through in regex; marked 
> by <-- HERE in m/\\begin{ <-- HERE verbatim}/ at mltex2html line 1303.
> Unescaped left brace in regex is deprecated, passed through in regex; marked 
> by <-- HERE in m/\\begin{ <-- HERE alltt}/ at mltex2html line 1304.
> Unescaped left brace in regex is deprecated, passed through in regex; marked 
> by <-- HERE in m/\\begin{ <-- HERE methods}/ at mltex2html line 1307.
> Unescaped left brace in regex is deprecated, passed through in regex; marked 
> by <-- HERE in m/\\end{ <-- HERE methods}/ at mltex2html line 1308.
> Unescaped left brace in regex is deprecated, passed through in regex; marked 
> by <-- HERE in m/\\end{ <-- HERE tabular}/ at mltex2html line 1318.
> Unescaped left brace in regex is deprecated, passed through in regex; marked 
> by <-- HERE in m/\\end{ <-- HERE Table}/ at mltex2html line 1321.
> Unescaped left brace in regex is deprecated, passed through in regex; marked 
> by <-- HERE in m/\\begin{ <-- HERE eqnarray\*}/ at mltex2html line 1345.
> Unescaped left brace in regex is deprecated, passed through in regex; marked 
> by <-- HERE in m/\\end{ <-- HERE eqnarray\*}/ at mltex2html line 1346.
> Unescaped left brace in regex is deprecated, passed through in regex; marked 
> by <-- HERE in m/\\begin{ <-- HERE eqnarray}/ at mltex2html line 1347.
> Unescaped left brace in regex is deprecated, passed through in regex; marked 
> by <-- HERE in m/\\end{ <-- HERE eqnarray}/ at mltex2html line 1348.
> Unescaped left brace in regex is deprecated, passed through in regex; marked 
> by <-- HERE in m/\\{ <-- HERE / at mltex2html line 1364.
> Can't locate mltex.thm in @INC (@INC contains: /etc/perl 
> /usr/local/lib/x86_64-linux-gnu/perl/5.22.2 /usr/local/share/perl/5.22.2 
> /usr/lib/x86_64-linux-gnu/perl5/5.22 /usr/share/perl5 
> /usr/lib/x86_64-linux-gnu/perl/5.22 /usr/share/perl/5.22 
> /usr/local/lib/site_perl /usr/lib/x86_64-linux-gnu/perl-base) at mltex2html 
> line 1003.
> Makefile:83: recipe for target 'mlrisc.html' failed
> make[2]: *** [mlrisc.html] Error 2

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

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

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

We believe that

Bug#837719: graphicsmagick: FTBFS on ppc64el: PerlMagick test failures

2016-09-13 Thread Bob Friesenhahn 

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


As Perl debug and libc6 debug symbols installed, I don't know which
library / executable may contain points #0 and #1. Maybe log.c itself?
At least the mentioned line in #2 is:
LockSemaphoreInfo(log_semaphore);


There were no functions added or removed between 1.3.24 and 1.3.25 and not
interfaces were changed.  If 1.3.24 still builds on the build machine, then
it is possible to test by replacing individual source files in 1.3.25 with
files from 1.3.24 and seeing when the problem goes away.  Since all tests
are failing, the problematic code would need to be used in initialization,
or somehow always encountered. Perhaps magick/utility.c would be a good
starting point.

Yes, 1.3.24 builds fine in the same environment. As previously noted
the broken change happened before 08th of August and it's not the
MAGICK_CACHE_LINE_SIZE value.


It seems that "semaphores" (pthread mutex locks or OpenMP locks 
depending on configuration, but should be pthread mutex locks in this 
configuration) are not working in the context of Perl/PerlMagick.


The crash occurs very early in initialization.  The crash is under the 
initial InitializeMagick() and when the first "semaphore" is locked. 
The log.c file was changed prior to the 1.3.24 release and semaphore.c 
has not changed since 2014.


I don't see any GraphicsMagick source code which has changed up to the 
point of the crash.  The only thing which changed in PerlMagick itself 
was the version string.


There is something suspect about the stack:

Thread 1 (Thread 0x3fffb7ff65b0 (LWP 3923)):
#0  0x000bffc8 in ?? ()
#1  0x000bffcb in ?? ()
#2  0x3fffb796b320 in InitializeLogInfo () at magick/log.c:301
#3  0x3fffb796c62c in InitializeMagick (path=0x3fffb7bf0708
"Graphics::Magick") at magick/magick.c:1117
#4  0x3fffb7bf0074 in boot_Graphics__Magick (my_perl=0x10210010,
cv=) at Magick.xs:2064

What seems suspect is that I would expect that #1 would be a decoded 
LockSemaphoreInfo() call and #0 would be a pthread_mutex_lock() call. 
These are in the same library so they should be decoded by the 
debugger equally well.  Probably pthread_mutex_lock() is also a 
function so there should be at least one more level of function calls 
on the stack.  It is as if the call went to a different library.


It may be necessary to prove where the problem is occuring by manually 
overwriting updated files in the magick directory with those from the 
previous working version until the problem goes away (assuming that it 
does).


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

Bug#832077: Info received (emacs clutter screen on windows switch)

2016-09-13 Thread Yasushi SHOJI 
On Thu, 08 Sep 2016 10:38:09 +0900,
Leon Meier wrote:
> 
> By the way, I don't know who is the culprit: libgtk-3-0, emacs, or
> someone else. So please consider my found / nofound tags just as
> additional information on my configuration rather as a bug source
> hint. Sorry about that.

https://mail.gnome.org/archives/commits-list/2016-May/msg06553.html

I found this commit on Gtk+. So I assume this is an intended change
for Gtk+ 3.22, no?
--
   yashi

Bug#837738: Fails to start, Invalid property: GtkScrolledWindow.propagate-natural-height

2016-09-13 Thread Michael Biebl 
Package: nautilus
Version: 3.21.92-1
Severity: grave

When running nautilus, one get's

(nautilus:28168): Gtk-CRITICAL **: Error building template class
'NautilusToolbar' for an instance of type 'NautilusToolbar': .:194:52
Invalid property: GtkScrolledWindow.propagate-natural-height
Segmentation fault



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

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

Versions of packages nautilus depends on:
ii  desktop-file-utils 0.23-1
ii  gsettings-desktop-schemas  3.21.4-2
ii  gvfs   1.29.92-1
ii  libatk1.0-02.21.90-2
ii  libc6  2.24-2
ii  libcairo-gobject2  1.14.6-1+b1
ii  libcairo2  1.14.6-1+b1
ii  libexempi3 2.3.0-2
ii  libexif12  0.6.21-2
ii  libgail-3-03.21.5-3
ii  libgdk-pixbuf2.0-0 2.35.5-1
ii  libglib2.0-0   2.49.7-1
ii  libglib2.0-data2.49.7-1
ii  libgnome-autoar-0-00.1.1-4
ii  libgnome-desktop-3-12  3.21.92-1
ii  libgtk-3-0 3.21.5-3
ii  libnautilus-extension1a3.21.92-1
ii  libpango-1.0-0 1.40.2-1
ii  libselinux12.5-3
ii  libtracker-sparql-1.0-01.9.1-2
ii  libx11-6   2:1.6.3-1
ii  nautilus-data  3.21.92-1
ii  shared-mime-info   1.7-1

Versions of packages nautilus recommends:
ii  gnome-sushi  3.21.91-1
ii  gvfs-backends1.29.92-1
ii  librsvg2-common  2.40.16-1

Versions of packages nautilus suggests:
ii  brasero3.12.1-2
ii  eog3.20.4-1
ii  evince [pdf-viewer]3.21.4-1
ii  okular [pdf-viewer]4:16.04.2-1
ii  totem  3.21.91-1
ii  tracker1.9.1-2
ii  vlc [mp3-decoder]  2.2.4-3+b4
ii  vlc-nox [mp3-decoder]  2.2.4-3+b4
ii  xdg-user-dirs  0.15-2
ii  xpdf [pdf-viewer]  3.04-1+b1

-- no debconf information

Bug#837263: marked as pending

2016-09-13 Thread James McCoy 
tag 837263 pending
thanks

Hello,

Bug #837263 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=collab-maint/smlnj.git;a=commitdiff;h=84fa6e1

---
commit 84fa6e1891f276688bf53d739ffa1f9aa7a19ea3
Author: James McCoy 
Date:   Tue Sep 13 21:39:39 2016 -0400

Fix FTBFS when '.' is not part of @INC and escape literal '{' in regex

Signed-off-by: James McCoy 

diff --git a/debian/changelog b/debian/changelog
index 867da29..c9bbafd 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,3 +1,10 @@
+smlnj (110.79-2) UNRELEASED; urgency=medium
+
+  * Add mltex2html-perl-fixes patch.  Fixes FTBFS when '.' is not part of @INC
+(Closes: #837263) and unescaped '{' in regex.
+
+ -- James McCoy   Tue, 13 Sep 2016 21:38:13 -0400
+
 smlnj (110.79-1) unstable; urgency=medium
 
   * New upstream release.

Processed: Bug#837263 marked as pending

2016-09-13 Thread Debian Bug Tracking System 
Processing commands for cont...@bugs.debian.org:

> tag 837263 pending
Bug #837263 [src:smlnj] smlnj: FTBFS: Can't locate mltex.thm in @INC
Added tag(s) pending.
> thanks
Stopping processing here.

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

Bug#837036: marked as done (gitolite3: uninstallable without . in @INC)

2016-09-13 Thread Debian Bug Tracking System 
Your message dated Wed, 14 Sep 2016 00:19:27 +
with message-id 
and subject line Bug#837036: fixed in gitolite3 3.6.6-1
has caused the Debian Bug report #837036,
regarding gitolite3: uninstallable without . in @INC
to be marked as done.

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

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


-- 
837036: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=837036
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: gitolite3
Version: 3.6.4-1
Severity: serious
Tags: upstream
Justification: uninstallable
User: debian-p...@lists.debian.org
Usertags: perl-cwd-inc-removal

The package fails to configure with the new default settings for @INC.

This is fixed in upstream commit 35e0b2a. Rather than cherry-picking
that, I'm planning to wait for a new upstream release, which should be
less than a week.


Setting up gitolite3 (3.6.4-1) ...
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 gitolite3
-

Please specify the key of the user that will administer the access 
configuration of gitolite.

This can be either the SSH public key itself, or the path to a file containing 
it. If it is blank, gitolite will 
be left unconfigured and must be set up manually.

If migrating from gitolite version 2.x, leave this blank.

Administrator's SSH key: /tmp/bremner.pub


Initialized empty Git repository in 
/var/lib/gitolite3/repositories/gitolite-admin.git/
Initialized empty Git repository in /var/lib/gitolite3/repositories/testing.git/
FATAL: parse 'conf/gitolite.conf-compiled.pm' failed: No such file or directory
dpkg: error processing package gitolite3 (--configure):


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

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

Versions of packages gitolite3 depends on:
ii  adduser  3.115
ii  debconf [debconf-2.0]1.5.59
ii  git [git-core]   1:2.9.3-1
ii  libjson-perl 2.90-1
ii  openssh-server [ssh-server]  1:7.3p1-1
ii  perl 5.22.2-3

gitolite3 recommends no packages.

Versions of packages gitolite3 suggests:
pn  git-daemon-sysvinit  
pn  gitweb   

-- debconf information:
  gitolite3/gitdir: /var/lib/gitolite3
* gitolite3/adminkey:
  gitolite3/gituser: gitolite3
--- End Message ---
--- Begin Message ---
Source: gitolite3
Source-Version: 3.6.6-1

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

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

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

Debian distribution maintenance software
pp.
David Bremner  (supplier of updated gitolite3 package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Tue, 13 Sep 2016 20:31:39 -0300
Source: gitolite3
Binary: gitolite3
Architecture: source
Version: 3.6.6-1
Distribution: unstable
Urgency: medium
Maintainer: David Bremner 
Changed-By: David Bremner 
Description:
 gitolite3  - SSH-based gatekeeper for git repositories (version 3)
Closes: 837036
Changes:
 gitolite3 (3.6.6-1) unstable; urgency=medium
 .
   * New upstream release
   * Bug fix: "uninstallable without . in @INC", explicitely look for
 './foo'.  (Closes: #837036).
Checksums-Sha1:
 e0a2249b762eb6a9572d93ffe599a3c0c678c76a 1660 gitolite3_3.6.6-1.dsc
 cfbb0dfe60d19adc0d9c4bbcba9c5e0934ca1e6f 183459 gitolite3_3.6.6.orig.tar.gz
 fcf42ea3569597dd0f893bae4b4e4d3d54cd5f80 18867 gitolite3_3.6.6-1.diff.gz
Checksums-Sha256:
 1495e5af145dd6e8c0f728a8fb0279066709f520b611bcbd2a8fa27f8c57d8c8 1660 
gitolite3_3.6.6-1.dsc
 6f4455af60cd4bc1ef5595133ddbdb4c327f2d12eeb9c4fa5e7b160ceaf58688 183459 
gitolite3_3.6.6.orig.tar.gz

Processed: reassign 837727 to gnome-shell-extension-top-icons-plus

2016-09-13 Thread Debian Bug Tracking System 
Processing commands for cont...@bugs.debian.org:

> reassign 837727 gnome-shell-extension-top-icons-plus 15-2
Bug #837727 [src:gnome-shell-extension-top-icon-plus] 
gnome-shell-extension-top-icon-plus: Not installable with gnome-shell >= 3.21.92
Warning: Unknown package 'src:gnome-shell-extension-top-icon-plus'
Bug reassigned from package 'src:gnome-shell-extension-top-icon-plus' to 
'gnome-shell-extension-top-icons-plus'.
No longer marked as found in versions gnome-shell-extension-top-icon-plus/15-2.
Ignoring request to alter fixed versions of bug #837727 to the same values 
previously set
Bug #837727 [gnome-shell-extension-top-icons-plus] 
gnome-shell-extension-top-icon-plus: Not installable with gnome-shell >= 3.21.92
Marked as found in versions gnome-shell-extension-top-icons-plus/15-2.
> thanks
Stopping processing here.

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

Bug#837123: [anna] segfault in wheezy installer

2016-09-13 Thread Vincent McIntyre 
On Tue, Sep 13, 2016 at 11:03:19PM +0200, Aurelien Jarno wrote:

...

> > If all of that makes no difference, what would be the next step?
> 
> What would be interesting would be to try to reproduce the issue in
> qemu or virtualbox, with as many things as possible close to your
> system.
> 

Just to clarify - you mean try to run the installer using a qemu VM
as the target for installation? I can certainly try that.

More details.
The target system is pxe booted and next-server takes it to a (debian)
system running tftpd-hpa. The defaults.cfg has lots of boot targets
but the one I have been testing with is the netboot image, in manual
install mode. The only boot options it is given are 
 'append vga=normal initrd=yadayada'
It also falls over if I feed it a preseed file, where we use
 'append auto=true priority=critical vga=normal initrd=yadayda 
  url=blahdeblah'

> Also you might want to use the console (alt+f2) to run wget by hand and
> see if the issue happen with all hosts or only some of them.

I tried to wget pages from a few web sites from the alt+f2 console.
It segfaulted every time when I used a DNS name in the URL,
but worked if I used an IP address in the URL.
ping does the same thing; segfaults only when using domain names.

If I put an entry in /etc/hosts and try to access that hostname,
wget and ping also segfault, until I add this line to nsswitch.conf:

  hosts: files dns

Then they both work for that hostname.
The only other nsswitch.conf lines are for passwd, group & shadow.

> > My concern is there's a segfault still lurking in the stretch
> > version. If we can squash it here that fix could be forward-ported.
> 
> This is very unlikely, as both debian-installer and glibc are quite
> different in stretch and do not use the shared library reduction
> anymore.

Ok that's good to know.

Bug#836768: marked as done (libphonenumber: FTBFS with glibc 2.24: int readdir_r() is deprecated)

2016-09-13 Thread Debian Bug Tracking System 
Your message dated Tue, 13 Sep 2016 23:25:40 +
with message-id 
and subject line Bug#836768: fixed in libphonenumber 7.1.0-5
has caused the Debian Bug report #836768,
regarding libphonenumber: FTBFS with glibc 2.24: int readdir_r() is deprecated
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.)


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

Source: libphonenumber
Version: 7.1.0-4
Severity: serious


Hi Maintainer

Your package FTBFS with glibc 2.24 now in unstable.
This issue has been reported upstream: 
https://github.com/googlei18n/libphonenumber/issues/1307 .

Below is an excerpt of the build log (hopefully the relevant part):

[  0%] Building CXX object 
tools/CMakeFiles/generate_geocoding_data.dir/src/cpp-build/generate_geocoding_data.cc.o
/<>/tools/cpp/src/cpp-build/generate_geocoding_data.cc: In 
function ‘bool i18n::phonenumbers::ListDirectory(const string&, 
std::vector*)’:
/<>/tools/cpp/src/cpp-build/generate_geocoding_data.cc:108:21: 
error: ‘int readdir_r(DIR*, dirent*, dirent**)’ is deprecated 
[-Werror=deprecated-declarations]

 const int res = readdir_r(dir, , _result);
 ^
In file included from 
/<>/tools/cpp/src/cpp-build/generate_geocoding_data.cc:19:0:

/usr/include/dirent.h:183:12: note: declared here
 extern int readdir_r (DIR *__restrict __dirp,
^
/<>/tools/cpp/src/cpp-build/generate_geocoding_data.cc:108:55: 
error: ‘int readdir_r(DIR*, dirent*, dirent**)’ is deprecated 
[-Werror=deprecated-declarations]

 const int res = readdir_r(dir, , _result);
   ^
In file included from 
/<>/tools/cpp/src/cpp-build/generate_geocoding_data.cc:19:0:

/usr/include/dirent.h:183:12: note: declared here
 extern int readdir_r (DIR *__restrict __dirp,
^
cc1plus: all warnings being treated as errors
tools/CMakeFiles/generate_geocoding_data.dir/build.make:62: recipe for 
target 
'tools/CMakeFiles/generate_geocoding_data.dir/src/cpp-build/generate_geocoding_data.cc.o' 
failed


Regards
Graham
--- End Message ---
--- Begin Message ---
Source: libphonenumber
Source-Version: 7.1.0-5

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

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

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

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

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Tue, 13 Sep 2016 23:13:45 +0200
Source: libphonenumber
Binary: libphonenumber7-java libphonenumber-dev libphonenumber7 libgeocoding7
Architecture: source
Version: 7.1.0-5
Distribution: unstable
Urgency: medium
Maintainer: Debian Java Maintainers 

Changed-By: Markus Koschany 
Description:
 libgeocoding7 - geocoding phone numbers
 libphonenumber-dev - parsing/formatting/validating phone numbers - development 
files
 libphonenumber7 - parsing/formatting/validating phone numbers
 libphonenumber7-java - parsing/formatting/validating phone numbers - java
Closes: 836768
Changes:
 libphonenumber (7.1.0-5) unstable; urgency=medium
 .
   * Team upload.
   * Revert "Set environment to GCC-6." because this is the default now.
   * Add readdir_r-is-deprecated.patch and fix FTBFS with glibc 2.24.
 Thanks to Graham Inggs for the report. (Closes: #836768)
   * Add libboost-filesystem-dev to Build-Depends.
Checksums-Sha1:
 49f4c4b936d5b303a1200b368ce1a6c269696278 2969 libphonenumber_7.1.0-5.dsc
 b124d3fb221687b751d8d10e552736dd02c02d51 12496 
libphonenumber_7.1.0-5.debian.tar.xz
Checksums-Sha256:
 04744559875f74fc240520f36953f01f67d88cd9bd1c96e85faca9c3002d5536 2969 
libphonenumber_7.1.0-5.dsc
 3a389a399d77450fe750d30291cac4e1ea939fea0d3d583567d4587f35d2d2eb 12496 
libphonenumber_7.1.0-5.debian.tar.xz
Files:
 a6bb4519a74105c7a5bffea174318adc 2969 libs optional libphonenumber_7.1.0-5.dsc
 a5aa90af5f1ba1ea7b318f1f01db12db 12496 libs

Bug#837727: gnome-shell-extension-top-icon-plus: Not installable with gnome-shell >= 3.21.92

2016-09-13 Thread Michael Biebl 
Control: reassign gnome-shell-extension-top-icons-plus 15-2


On Wed, 14 Sep 2016 01:20:14 +0200 bi...@debian.org wrote:
> Source: gnome-shell-extension-top-icon-plus
> Version: 15-2
> Severity: serious
> User: pkg-gnome-maintain...@lists.alioth.debian.org
> Usertags: gnome-shell-3-22
> 
> Hi,
> 
> your package gnome-shell-extension-top-icon-plus declares a strictly
> versioned dependency on gnome-shell. We've uploaded gnome-shell
> 3.21.92 to unstable, which makes gnome-shell-extension-top-icon-plus
> uninstallable.
> 
> In the past, it was necessary to explicitly declare supported
> gnome-shell versions in metadata.json. This was lifted in gnome-shell
> 3.21.92 [1].
> 
> "Nowadays, the user interface has mostly stabilized with most changes
> happening under the hood. As a result, extensions written for
> previous versions of GNOME Shell are very much expected to keep
> working on updates, if it wasn't for the version check that requires
> a version bump in the extension metadata. There has been a setting to
> disable that check for a while, but it's existence isn't widely known
> (hence the common perception that "everything breaks on updates").
> While there is still some risk that an out-of-date extension can be
> enabled without error, but fails spectacularly later (where we cannot
> catch the exception), it is reasonably small by now when compared to
> the ~95% of extensions that can be "unbroken", so swap the default
> value to disable version checks by default."
> 
> As a result, you could drop the gnome-shell << XXX version limitation
> altogether. The Debian release cycle is pretty long though, so we
> don't know yet if the gnome-shell version in Buster will actually be
> compatible with your extension today. We will release Stretch with
> GNOME Shell 3.22, so my recommendation would be to use gnome-shell
> (<< 3.23) as upper limt.
> 
> Modifications for metadata.json are no longer required.
> 
> Regards, Michael
> 
> [1] https://git.gnome.org/browse/gnome-shell/commit/?id=5e0e3e


-- 
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#837595: gnome-shell-pomodoro: Not compatible with gnome-shell 3.21.x/3.22

2016-09-13 Thread Michael Biebl 
There are some recent updates:

In the past, it was necessary to explicitly declare supported
gnome-shell versions in metadata.json. This was lifted in gnome-shell
3.21.92 [1].

"Nowadays, the user interface has mostly stabilized with most changes
happening under the hood. As a result, extensions written for
previous versions of GNOME Shell are very much expected to keep
working on updates, if it wasn't for the version check that requires
a version bump in the extension metadata. There has been a setting to
disable that check for a while, but it's existence isn't widely known
(hence the common perception that "everything breaks on updates").
While there is still some risk that an out-of-date extension can be
enabled without error, but fails spectacularly later (where we cannot
catch the exception), it is reasonably small by now when compared to
the ~95% of extensions that can be "unbroken", so swap the default
value to disable version checks by default."

As a result, you could drop the gnome-shell << XXX version limitation
altogether. The Debian release cycle is pretty long though, so we
don't know yet if the gnome-shell version in Buster will actually be
compatible with your extension today. We will release Stretch with
GNOME Shell 3.22, so my recommendation would be to use gnome-shell
(<< 3.23) as upper limt.

Modifications for metadata.json are no longer required.

Regards, Michael

[1] https://git.gnome.org/browse/gnome-shell/commit/?id=5e0e3e
-- 
Why is it that all of the instruments seeking intelligent life in the
universe are pointed away from Earth?

Bug#837593: gnome-shell-extension-redshift: Not compatible with gnome-shell 3.21.x/3.22

2016-09-13 Thread Michael Biebl 
There are some recent updates:

In the past, it was necessary to explicitly declare supported
gnome-shell versions in metadata.json. This was lifted in gnome-shell
3.21.92 [1].

"Nowadays, the user interface has mostly stabilized with most changes
happening under the hood. As a result, extensions written for
previous versions of GNOME Shell are very much expected to keep
working on updates, if it wasn't for the version check that requires
a version bump in the extension metadata. There has been a setting to
disable that check for a while, but it's existence isn't widely known
(hence the common perception that "everything breaks on updates").
While there is still some risk that an out-of-date extension can be
enabled without error, but fails spectacularly later (where we cannot
catch the exception), it is reasonably small by now when compared to
the ~95% of extensions that can be "unbroken", so swap the default
value to disable version checks by default."

As a result, you could drop the gnome-shell << XXX version limitation
altogether. The Debian release cycle is pretty long though, so we
don't know yet if the gnome-shell version in Buster will actually be
compatible with your extension today. We will release Stretch with
GNOME Shell 3.22, so my recommendation would be to use gnome-shell
(<< 3.23) as upper limt.

Modifications for metadata.json are no longer required.

Regards, Michael

[1] https://git.gnome.org/browse/gnome-shell/commit/?id=5e0e3e

-- 
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#837594: gnome-shell-extension-autohidetopbar: Not compatible with gnome-shell 3.21.x/3.22

2016-09-13 Thread Michael Biebl 
There are some recent updates:

In the past, it was necessary to explicitly declare supported
gnome-shell versions in metadata.json. This was lifted in gnome-shell
3.21.92 [1].

"Nowadays, the user interface has mostly stabilized with most changes
happening under the hood. As a result, extensions written for
previous versions of GNOME Shell are very much expected to keep
working on updates, if it wasn't for the version check that requires
a version bump in the extension metadata. There has been a setting to
disable that check for a while, but it's existence isn't widely known
(hence the common perception that "everything breaks on updates").
While there is still some risk that an out-of-date extension can be
enabled without error, but fails spectacularly later (where we cannot
catch the exception), it is reasonably small by now when compared to
the ~95% of extensions that can be "unbroken", so swap the default
value to disable version checks by default."

As a result, you could drop the gnome-shell << XXX version limitation
altogether. The Debian release cycle is pretty long though, so we
don't know yet if the gnome-shell version in Buster will actually be
compatible with your extension today. We will release Stretch with
GNOME Shell 3.22, so my recommendation would be to use gnome-shell
(<< 3.23) as upper limt.

Modifications for metadata.json are no longer required.

Regards, Michael

[1] https://git.gnome.org/browse/gnome-shell/commit/?id=5e0e3e

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

Bug#837592: gnome-shell-extension-suspend-button: Not compatible with gnome-shell 3.21.x/3.22

2016-09-13 Thread Michael Biebl 
There are some recent updates:

In the past, it was necessary to explicitly declare supported
gnome-shell versions in metadata.json. This was lifted in gnome-shell
3.21.92 [1].

"Nowadays, the user interface has mostly stabilized with most changes
happening under the hood. As a result, extensions written for
previous versions of GNOME Shell are very much expected to keep
working on updates, if it wasn't for the version check that requires
a version bump in the extension metadata. There has been a setting to
disable that check for a while, but it's existence isn't widely known
(hence the common perception that "everything breaks on updates").
While there is still some risk that an out-of-date extension can be
enabled without error, but fails spectacularly later (where we cannot
catch the exception), it is reasonably small by now when compared to
the ~95% of extensions that can be "unbroken", so swap the default
value to disable version checks by default."

As a result, you could drop the gnome-shell << XXX version limitation
altogether. The Debian release cycle is pretty long though, so we
don't know yet if the gnome-shell version in Buster will actually be
compatible with your extension today. We will release Stretch with
GNOME Shell 3.22, so my recommendation would be to use gnome-shell
(<< 3.23) as upper limt.

Modifications for metadata.json are no longer required.

Regards, Michael

[1] https://git.gnome.org/browse/gnome-shell/commit/?id=5e0e3e


-- 
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#837726: gnome-shell-extension-mediaplayer: Not installable with gnome-shell >= 3.21.92

2016-09-13 Thread biebl 
Source: gnome-shell-extension-mediaplayer
Version: 0~git201600509-2
Severity: serious
User: pkg-gnome-maintain...@lists.alioth.debian.org
Usertags: gnome-shell-3-22

Hi,

your package gnome-shell-extension-mediaplayer declares a strictly
versioned dependency on gnome-shell. We've uploaded gnome-shell
3.21.92 to unstable, which makes gnome-shell-extension-mediaplayer
uninstallable.

In the past, it was necessary to explicitly declare supported
gnome-shell versions in metadata.json. This was lifted in gnome-shell
3.21.92 [1].

"Nowadays, the user interface has mostly stabilized with most changes
happening under the hood. As a result, extensions written for
previous versions of GNOME Shell are very much expected to keep
working on updates, if it wasn't for the version check that requires
a version bump in the extension metadata. There has been a setting to
disable that check for a while, but it's existence isn't widely known
(hence the common perception that "everything breaks on updates").
While there is still some risk that an out-of-date extension can be
enabled without error, but fails spectacularly later (where we cannot
catch the exception), it is reasonably small by now when compared to
the ~95% of extensions that can be "unbroken", so swap the default
value to disable version checks by default."

As a result, you could drop the gnome-shell << XXX version limitation
altogether. The Debian release cycle is pretty long though, so we
don't know yet if the gnome-shell version in Buster will actually be
compatible with your extension today. We will release Stretch with
GNOME Shell 3.22, so my recommendation would be to use gnome-shell
(<< 3.23) as upper limt.

Modifications for metadata.json are no longer required.

Regards, Michael

[1] https://git.gnome.org/browse/gnome-shell/commit/?id=5e0e3e

Bug#837727: gnome-shell-extension-top-icon-plus: Not installable with gnome-shell >= 3.21.92

2016-09-13 Thread biebl 
Source: gnome-shell-extension-top-icon-plus
Version: 15-2
Severity: serious
User: pkg-gnome-maintain...@lists.alioth.debian.org
Usertags: gnome-shell-3-22

Hi,

your package gnome-shell-extension-top-icon-plus declares a strictly
versioned dependency on gnome-shell. We've uploaded gnome-shell
3.21.92 to unstable, which makes gnome-shell-extension-top-icon-plus
uninstallable.

In the past, it was necessary to explicitly declare supported
gnome-shell versions in metadata.json. This was lifted in gnome-shell
3.21.92 [1].

"Nowadays, the user interface has mostly stabilized with most changes
happening under the hood. As a result, extensions written for
previous versions of GNOME Shell are very much expected to keep
working on updates, if it wasn't for the version check that requires
a version bump in the extension metadata. There has been a setting to
disable that check for a while, but it's existence isn't widely known
(hence the common perception that "everything breaks on updates").
While there is still some risk that an out-of-date extension can be
enabled without error, but fails spectacularly later (where we cannot
catch the exception), it is reasonably small by now when compared to
the ~95% of extensions that can be "unbroken", so swap the default
value to disable version checks by default."

As a result, you could drop the gnome-shell << XXX version limitation
altogether. The Debian release cycle is pretty long though, so we
don't know yet if the gnome-shell version in Buster will actually be
compatible with your extension today. We will release Stretch with
GNOME Shell 3.22, so my recommendation would be to use gnome-shell
(<< 3.23) as upper limt.

Modifications for metadata.json are no longer required.

Regards, Michael

[1] https://git.gnome.org/browse/gnome-shell/commit/?id=5e0e3e

Bug#837725: gnome-shell-extension-caffeine: Not installable with gnome-shell >= 3.21.92

2016-09-13 Thread biebl 
Source: gnome-shell-extension-caffeine
Version: 0~git20160329-2
Severity: serious
User: pkg-gnome-maintain...@lists.alioth.debian.org
Usertags: gnome-shell-3-22

Hi,

your package gnome-shell-extension-caffeine declares a strictly
versioned dependency on gnome-shell. We've uploaded gnome-shell
3.21.92 to unstable, which makes gnome-shell-extension-caffeine
uninstallable.

In the past, it was necessary to explicitly declare supported
gnome-shell versions in metadata.json. This was lifted in gnome-shell
3.21.92 [1].

"Nowadays, the user interface has mostly stabilized with most changes
happening under the hood. As a result, extensions written for
previous versions of GNOME Shell are very much expected to keep
working on updates, if it wasn't for the version check that requires
a version bump in the extension metadata. There has been a setting to
disable that check for a while, but it's existence isn't widely known
(hence the common perception that "everything breaks on updates").
While there is still some risk that an out-of-date extension can be
enabled without error, but fails spectacularly later (where we cannot
catch the exception), it is reasonably small by now when compared to
the ~95% of extensions that can be "unbroken", so swap the default
value to disable version checks by default."

As a result, you could drop the gnome-shell << XXX version limitation
altogether. The Debian release cycle is pretty long though, so we
don't know yet if the gnome-shell version in Buster will actually be
compatible with your extension today. We will release Stretch with
GNOME Shell 3.22, so my recommendation would be to use gnome-shell
(<< 3.23) as upper limt.

Modifications for metadata.json are no longer required.

Regards, Michael

[1] https://git.gnome.org/browse/gnome-shell/commit/?id=5e0e3e

Processed: severity of 836881 is normal

2016-09-13 Thread Debian Bug Tracking System 
Processing commands for cont...@bugs.debian.org:

> severity 836881 normal
Bug #836881 [libhx509-5-heimdal] X509 card-based logins fail with SIGSEGV
Severity set to 'normal' from 'grave'
> thanks
Stopping processing here.

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

Bug#837719: graphicsmagick: FTBFS on ppc64el: PerlMagick test failures

2016-09-13 Thread GCS 
Hi Bob, Niko,

On Tue, Sep 13, 2016 at 11:15 PM, Bob Friesenhahn
 wrote:
> On Tue, 13 Sep 2016, László Böszörményi wrote:
>> On Tue, Sep 13, 2016 at 10:42 PM, Niko Tyni  wrote:
>>> This package is failing to build on ppc64el, but built successfully
>>> in the past.
>> This is known and working with upstream to find the root cause.
> A backtrace from a core dump is needed.
 I'm not that good with gdb, but as a first shot this may give you more idea.
-- cut --
Core was generated by `/usr/bin/perl t/zlib/write.t '.
Program terminated with signal SIGSEGV, Segmentation fault.
#0  0x000bffc8 in ?? ()
[...]
(gdb) thread apply all bt

Thread 1 (Thread 0x3fffb7ff65b0 (LWP 3923)):
#0  0x000bffc8 in ?? ()
#1  0x000bffcb in ?? ()
#2  0x3fffb796b320 in InitializeLogInfo () at magick/log.c:301
#3  0x3fffb796c62c in InitializeMagick (path=0x3fffb7bf0708
"Graphics::Magick") at magick/magick.c:1117
#4  0x3fffb7bf0074 in boot_Graphics__Magick (my_perl=0x10210010,
cv=) at Magick.xs:2064
#5  0x100e1960 in Perl_pp_entersub (my_perl=0x10210010) at pp_hot.c:3272
#6  0x100d8d88 in Perl_runops_standard (my_perl=0x10210010) at run.c:41
#7  0x10046f18 in Perl_call_sv (my_perl=0x10210010,
sv=0x1023ab78, flags=13) at perl.c:2779
#8  0x10049c3c in Perl_call_list (my_perl=0x10210010,
oldscope=, paramList=0x10213248) at perl.c:4995
#9  0x1001e3e0 in S_process_special_blocks
(my_perl=0x10210010, floor=39, fullname=0x1023c100 "BEGIN",
gv=0x1023a980, cv=0x1023ab78) at op.c:8916
#10 0x1003e028 in Perl_newATTRSUB_x (my_perl=0x10210010,
floor=39, o=, proto=, attrs=,
block=, o_is_gv=false) at op.c:8845
#11 0x100422b0 in Perl_utilize (my_perl=0x10210010,
aver=, floor=, version=,
idop=,
arg=) at op.c:6069
#12 0x1007f784 in Perl_yyparse (my_perl=0x10210010,
gramtype=) at perly.y:351
#13 0x1004ee1c in S_parse_body (xsinit=0x1001d490 ,
env=0x0, my_perl=0x10210010) at perl.c:2306
#14 perl_parse (my_perl=0x10210010, xsinit=0x1001d490 ,
argc=, argv=, env=0x0) at perl.c:1626
#15 0x1001d178 in main (argc=, argv=, env=) at perlmain.c:114
-- cut --

As Perl debug and libc6 debug symbols installed, I don't know which
library / executable may contain points #0 and #1. Maybe log.c itself?
At least the mentioned line in #2 is:
LockSemaphoreInfo(log_semaphore);

> There were no functions added or removed between 1.3.24 and 1.3.25 and not
> interfaces were changed.  If 1.3.24 still builds on the build machine, then
> it is possible to test by replacing individual source files in 1.3.25 with
> files from 1.3.24 and seeing when the problem goes away.  Since all tests
> are failing, the problematic code would need to be used in initialization,
> or somehow always encountered. Perhaps magick/utility.c would be a good
> starting point.
 Yes, 1.3.24 builds fine in the same environment. As previously noted
the broken change happened before 08th of August and it's not the
MAGICK_CACHE_LINE_SIZE value.

Cheers,
Laszlo/GCS

Bug#834249: openbabel: FTBFS in testing

2016-09-13 Thread gregor herrmann 
Control: tag -1 + patch

On Sat, 13 Aug 2016 20:05:36 +0200, Santiago Vila wrote:

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

Also fails in sid.

Looks like a typical GCC6-induced error.
The build succeeds with -std=gnu++98. Patch attached.


Cheers,
gregor

-- 
 .''`.  Homepage https://info.comodo.priv.at/ - OpenPGP key 0xBB3A68018649AA06
 : :' : Debian GNU/Linux user, admin, and developer -  https://www.debian.org/
 `. `'  Member of VIBE!AT & SPI, fellow of the Free Software Foundation Europe
   `-   NP: Rolling Stones: Sweetblack
diff -Nru openbabel-2.3.2+dfsg/debian/changelog openbabel-2.3.2+dfsg/debian/changelog
--- openbabel-2.3.2+dfsg/debian/changelog	2016-08-02 11:44:00.0 +0200
+++ openbabel-2.3.2+dfsg/debian/changelog	2016-09-13 22:58:23.0 +0200
@@ -1,3 +1,11 @@
+openbabel (2.3.2+dfsg-2.4) UNRELEASED; urgency=medium
+
+  * Non-maintainer upload.
+  * Fix "FTBFS in testing": build with -std=gnu++98.
+(Closes: #834249)
+
+ -- gregor herrmann   Tue, 13 Sep 2016 22:58:23 +0200
+
 openbabel (2.3.2+dfsg-2.3) unstable; urgency=medium
 
   * Non-maintainer upload.
diff -Nru openbabel-2.3.2+dfsg/debian/rules openbabel-2.3.2+dfsg/debian/rules
--- openbabel-2.3.2+dfsg/debian/rules	2014-09-20 14:29:56.0 +0200
+++ openbabel-2.3.2+dfsg/debian/rules	2016-09-13 22:58:23.0 +0200
@@ -11,6 +11,7 @@
 export CFLAGS   := $(shell dpkg-buildflags --get CFLAGS) $(CPPFLAGS)
 export CXXFLAGS := $(shell dpkg-buildflags --get CXXFLAGS) $(CPPFLAGS)
 export LDFLAGS  := $(shell dpkg-buildflags --get LDFLAGS)
+export DEB_CXXFLAGS_MAINT_APPEND = -std=gnu++98
 
 DH_AUTO_CONFIGURE_OPTS := -DCMAKE_BUILD_TYPE=None \
   -DPYTHON_BINDINGS=ON -DPERL_BINDINGS=ON \


signature.asc
Description: Digital Signature

Processed: Re: Bug#834249: openbabel: FTBFS in testing

2016-09-13 Thread Debian Bug Tracking System 
Processing control commands:

> tag -1 + patch
Bug #834249 [src:openbabel] openbabel: FTBFS in testing
Added tag(s) patch.

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

Bug#837719: graphicsmagick: FTBFS on ppc64el: PerlMagick test failures

2016-09-13 Thread Bob Friesenhahn 

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


On Tue, Sep 13, 2016 at 10:42 PM, Niko Tyni  wrote:

This package is failing to build on ppc64el, but built successfully
in the past. As seen at
 https://buildd.debian.org/status/logs.php?pkg=graphicsmagick=ppc64el
it regressed with 1.3.24+hg20160808-1, and the version currently in
sid is still failing. It looks like this is preventing migration to testing.

This is known and working with upstream to find the root cause.


A backtrace from a core dump is needed.


The list of toolchain package versions in the build logs suggests that
the regression might be due to the switch to GCC 6.

Definitely not. A code change in GraphicsMagick triggers it. I could
tighten it down, but don't know the exact cause yet.


There were no functions added or removed between 1.3.24 and 1.3.25 and 
not interfaces were changed.  If 1.3.24 still builds on the build 
machine, then it is possible to test by replacing individual source 
files in 1.3.25 with files from 1.3.24 and seeing when the problem 
goes away.  Since all tests are failing, the problematic code would 
need to be used in initialization, or somehow always encountered. 
Perhaps magick/utility.c would be a good starting point.


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

Processed: (no subject)

2016-09-13 Thread Debian Bug Tracking System 
Processing commands for cont...@bugs.debian.org:

> tags 836669 + upstream fixed-upstream
Bug #836669 [caja] caja: Crashes due to theme errors
Added tag(s) upstream and fixed-upstream.
>
End of message, stopping processing here.

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

Bug#837123: [anna] segfault in wheezy installer

2016-09-13 Thread Aurelien Jarno 
On 2016-09-10 11:30, Vincent McIntyre wrote:
> On Fri, Sep 09, 2016 at 03:59:17PM +0200, Aurelien Jarno wrote:
> > 
> > I don't talk about the software running on your DNS servers, but
> > rather how they behave when they get queried. It might depends on
> > many other things, like if your network has IPv6 or not.
> > 
> > Note that's only one explanation, not sure it's the right one, but
> > given I am unable to reproduce the issue, it's the only one that
> > come to my mind.
> 
> Thank you for explaining. I am struggling with this idea since AFAIK
> the DNS servers have not been changed in the last six months or more
> so I can think of no reason for the behaviour to have changed.

Thanks for the details, that's an important information.

> That history is what makes me think something must have changed in
> the installer around the time of the last point release (May).
> But from what you say that isn't the case.

The installer did change, and has been built against a new libc which
includes changes to the resolver, fixing security issues. I am not aware
of any issue introduced by these patches (this libc is used on regular
systems, not only in debian-installer), except #816669 which involves
IPv6 and has different symptoms.

> You've given me a few things to try out
>  - tell DHCP to supply different DNS servers (running bind)
>  - make sure all ipv6 related options are disabled
>and no ipv6 DNS entries exist for the target host
>  - make sure all ipv6 related options are enabled
>and valid ipv6 DNS entries exist for the target host
> 
> Also I can try installing oldstable with the jessie installer.
>  
> If all of that makes no difference, what would be the next step?

What would be interesting would be to try to reproduce the issue in
qemu or virtualbox, with as many things as possible close to your
system.

Also you might want to use the console (alt+f2) to run wget by hand and
see if the issue happen with all hosts or only some of them.

> I assume I'd have to build a debug version of the installer
> and try to get a backtrace?

I don't know if it's really something doable, especially the wheezy
installer use a shared library reduction system to strip some symbols 
from the shared libraries.

> My concern is there's a segfault still lurking in the stretch
> version. If we can squash it here that fix could be forward-ported.

This is very unlikely, as both debian-installer and glibc are quite
different in stretch and do not use the shared library reduction
anymore.

Aurelien

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

Bug#837719: graphicsmagick: FTBFS on ppc64el: PerlMagick test failures

2016-09-13 Thread GCS 
On Tue, Sep 13, 2016 at 10:42 PM, Niko Tyni  wrote:
> This package is failing to build on ppc64el, but built successfully
> in the past. As seen at
>  https://buildd.debian.org/status/logs.php?pkg=graphicsmagick=ppc64el
> it regressed with 1.3.24+hg20160808-1, and the version currently in
> sid is still failing. It looks like this is preventing migration to testing.
 This is known and working with upstream to find the root cause.

> The list of toolchain package versions in the build logs suggests that
> the regression might be due to the switch to GCC 6.
 Definitely not. A code change in GraphicsMagick triggers it. I could
tighten it down, but don't know the exact cause yet.

Regards,
Laszlo/GCS

Processed: block 830200 with 837719

2016-09-13 Thread Debian Bug Tracking System 
Processing commands for cont...@bugs.debian.org:

> # assuming ppc64el missing binaries currently block testing migration
> block 830200 with 837719
Bug #830200 [release.debian.org] transition: perl
830200 was blocked by: 834795 825611 825609 836162 834796 836636 825014 825231 
834799 834797 825524 825012 825762 834798 834800
830200 was not blocking any bugs.
Added blocking bug(s) of 830200: 837719
> thanks
Stopping processing here.

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

Processed: tagging 837036

2016-09-13 Thread Debian Bug Tracking System 
Processing commands for cont...@bugs.debian.org:

> tags 837036 + fixed-upstream
Bug #837036 [gitolite3] gitolite3: uninstallable without . in @INC
Added tag(s) fixed-upstream.
> thanks
Stopping processing here.

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

Bug#837719: graphicsmagick: FTBFS on ppc64el: PerlMagick test failures

2016-09-13 Thread Niko Tyni 
Package: graphicsmagick
Version: 1.3.25-1
Severity: serious

This package is failing to build on ppc64el, but built successfully
in the past. As seen at
 https://buildd.debian.org/status/logs.php?pkg=graphicsmagick=ppc64el
it regressed with 1.3.24+hg20160808-1, and the version currently in
sid is still failing. It looks like this is preventing migration to testing.

The list of toolchain package versions in the build logs suggests that
the regression might be due to the switch to GCC 6.

The build log shows segfaults or something like that in PerlMagick/ .

  PERL_DL_NONLAZY=1 PERL_USE_UNSAFE_INC=1 "/usr/bin/perl" 
"-MExtUtils::Command::MM" "-MTest::Harness" "-e" "undef 
*Test::Harness::Switches; test_harness(1, 'blib/lib', 'blib/arch')" t/*.t 
t/bzlib/*.t t/jbig/*.t t/jng/*.t t/jpeg/*.t t/png/*.t t/ps/*.t t/tiff/*.t 
t/ttf/*.t t/wmf/*.t t/x/*.t t/xfig/*.t t/zlib/*.t
  t/blob.t .. 
  1..1
  Failed 1/1 subtests 
  t/bzlib/read.t  
  1..2
  Failed 2/2 subtests 
  [...]
  Test Summary Report
  ---
  t/blob.t(Wstat: 11 Tests: 0 Failed: 0)
Non-zero wait status: 11
Parse errors: Bad plan.  You planned 1 tests but ran 0.
  [...]
  Files=32, Tests=0,  1 wallclock secs ( 0.08 usr  0.04 sys +  0.56 cusr  0.17 
csys =  0.85 CPU)
  Result: FAIL
  Failed 32/32 test programs. 0/0 subtests failed.
  Makefile:993: recipe for target 'test_dynamic' failed
  make[5]: *** [test_dynamic] Error 255
  
-- 
Niko Tyni   nt...@debian.org

Bug#834597: kgb-bot: FTBFS in testing

2016-09-13 Thread Adrian Bunk 
On Thu, Aug 18, 2016 at 06:22:54PM +0200, gregor herrmann wrote:
>...
> Hm, I guess we should think about a release?

Yes, it would be good if you could make a release.

> Cheers,
> gregor

Thanks
Adrian

-- 

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

Bug#834087: marked as done (runit: breaks users of runit: ln: failed to create symbolic link '/etc/service/bcron-sched': No such file or directory)

2016-09-13 Thread Debian Bug Tracking System 
Your message dated Tue, 13 Sep 2016 16:07:25 -0400 (EDT)
with message-id 
and subject line Re: Bug#834087: Bug#832656: runit: breaks users of runit: ln: 
failed to create symbolic link '/etc/service/bcron-sched': No such file or 
directory
has caused the Debian Bug report #834087,
regarding runit: breaks users of runit: ln: failed to create symbolic link 
'/etc/service/bcron-sched': 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.)


-- 
834087: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=834087
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: runit
Version: 2.1.2-4
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

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

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

  Selecting previously unselected package bcron-run.
  (Reading database ... 
(Reading database ... 6995 files and directories currently installed.)
  Preparing to unpack .../bcron-run_0.10-3_all.deb ...
  Unpacking bcron-run (0.10-3) ...
  Setting up bcron-run (0.10-3) ...
  Installing new version of config file /etc/crontab ...
  Adding system user `cron' (UID 151) ...
  Adding new group `cron' (GID 152) ...
  Adding new user `cron' (UID 151) with group `cron' ...
  Not creating home directory `/var/spool/cron'.
  Warning: The home dir /nonexistent you specified can't be accessed: No such 
file or directory
  Adding system user `cronlog' (UID 152) ...
  Adding new user `cronlog' (UID 152) with group `nogroup' ...
  Not creating home directory `/nonexistent'.
  ln: failed to create symbolic link '/etc/service/bcron-sched': No such file 
or directory
  dpkg: error processing package bcron-run (--configure):
   subprocess installed post-installation script returned error exit status 1
  Errors were encountered while processing:
   bcron-run

Similar problems were seen in different *-run packages.


cheers,

Andreas


bcron-run_0.10-3.log.gz
Description: application/gzip
--- End Message ---
--- Begin Message ---
Version: 1:2.9.3-1

I’m closing this in git-daemon-run because it’s listed as passing 
piuparts.  If there’s still a problem hiding here, feel free to reopen 
with an explanation.

https://piuparts.debian.org/sid/pass/git-daemon-run_1:2.9.3-1.log

Anders--- End Message ---

Bug#837714: libarchive: CVE-2016-5418: Archive Entry with type 1 (hardlink), but has a non-zero data size file overwrite

2016-09-13 Thread Salvatore Bonaccorso 
Source: libarchive
Version: 3.2.1-2
Severity: grave
Tags: security upstream patch

Hi,

the following vulnerability was published for libarchive.

CVE-2016-5418[0]:
|Archive Entry with type 1 (hardlink), but has a non-zero data size
|file overwrite

This corresponds to [1] and [2], which is upstream as [3].

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

For further information see:

[0] https://security-tracker.debian.org/tracker/CVE-2016-5418
[1] 
https://git.centos.org/blob/rpms!libarchive.git/9952851f8b327a8c93d26a5873c190c1fb09ae6c/SOURCES!libarchive-3.1.2-CVE-2016-5418.patch;jsessionid=1dexz8h9qdewibih5aonbu3
[2] 
https://git.centos.org/blob/rpms!libarchive.git/9952851f8b327a8c93d26a5873c190c1fb09ae6c/SOURCES!libarchive-3.1.2-CVE-2016-5418-variation.patch;jsessionid=1dexz8h9qdewibih5aonbu3
[3] 
https://github.com/libarchive/libarchive/commit/dfd6b54ce33960e420fb206d8872fb759b577ad9

Please adjust the affected versions in the BTS as needed. jessie
version has not been checked yet, but is probably similar affected.

Regards,
Salvatore

Bug#821481: PHP 7.0 support

2016-09-13 Thread Michael-John Turner 
Hi

FYI, there is an upstream bug report open for PHP 7.0 support:
https://jira.z-hub.io/projects/ZP/issues/ZP-804

Cheers, MJ
-- 
Michael-John Turner * m...@mjturner.net * http://mjturner.net/

Bug#832077: Info received (emacs clutter screen on windows switch)

2016-09-13 Thread D. B. 
Are you using unstable? Then you have no right to be melodramatic about
people "demolishing" the distro.

It's not the maintainers fault if 3rd-party software is not up to date with
the libraries on which it relies. And by using unstable or testing, the
user accepts the very likely possibility of temporary breakage.

And there's the key word: temporary.

Bug#837488: marked as done (python3-pyopencl: Broken install)

2016-09-13 Thread Debian Bug Tracking System 
Your message dated Tue, 13 Sep 2016 18:51:17 +
with message-id 
and subject line Bug#837488: fixed in pyopencl 2016.1+git20160809-2
has caused the Debian Bug report #837488,
regarding python3-pyopencl: Broken install
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.)


-- 
837488: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=837488
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: python3-pyopencl
Version: 2016.1+git20160809-1
Severity: normal

Dear Maintainer,

Do you want to continue? [Y/n] Y
Setting up python3-pyopencl (2016.1+git20160809-1) ...
  File 
"/usr/lib/python3/dist-packages/pyopencl/compyte/ndarray/gen_elemwise.py", line 
955
print sio.getvalue()
^
SyntaxError: invalid syntax

  File 
"/usr/lib/python3/dist-packages/pyopencl/compyte/ndarray/test_gpu_ndarray.py", 
line 314
print shp, dtype, offseted, order1, order2
^
SyntaxError: Missing parentheses in call to 'print'

dpkg: error processing package python3-pyopencl (--configure):
 subprocess installed post-installation script returned error exit status 1
Errors were encountered while processing:
 python3-pyopencl
E: Sub-process /usr/bin/dpkg returned an error code (1)
mdriftmeyer@horus:~/tmp-files$

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

Kernel: Linux 4.7.0-1-amd64 (SMP w/8 CPU cores)
Locale: LANG=en_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 python3-pyopencl depends on:
ii  libc6   2.24-2
ii  libgcc1 1:6.2.0-3
ii  libstdc++6  6.2.0-3
ii  mesa-opencl-icd [opencl-icd]12.0.2-1
ii  ocl-icd-libopencl1 [libopencl1] 2.2.9-2
ii  pocl-opencl-icd [opencl-icd]0.13-7
ii  python3 3.5.1-4
ii  python3-appdirs 1.4.0-2
pn  python3-cffi-backend-api-max
pn  python3-cffi-backend-api-min
ii  python3-decorator   4.0.6-1
ii  python3-numpy [python3-numpy-abi9]  1:1.11.1~rc1-1
ii  python3-pkg-resources   27.1.2-1
ii  python3-pytools 2016.2.1-1
ii  python3-six 1.10.0-3
pn  python3:any 

Versions of packages python3-pyopencl recommends:
ii  python-pyopencl-doc  2016.1+git20160809-1
ii  python3-mako 1.0.4+ds1-1

Versions of packages python3-pyopencl suggests:
pn  python3-imaging-tk
ii  python3-matplotlib1.5.3-1
ii  python3-opengl3.1.0+dfsg-1
pn  python3-pyopencl-dbg  
ii  python3-pytest3.0.2-1

-- no debconf information
--- End Message ---
--- Begin Message ---
Source: pyopencl
Source-Version: 2016.1+git20160809-2

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

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

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

Debian distribution maintenance software
pp.
Tomasz Rybak  (supplier of updated pyopencl package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Tue, 13 Sep 2016 18:38:01 +0200
Source: pyopencl
Binary: python-pyopencl python-pyopencl-dbg python3-pyopencl 
python3-pyopencl-dbg python-pyopencl-doc
Architecture: source amd64 all
Version: 2016.1+git20160809-2
Distribution: unstable
Urgency: low
Maintainer: Tomasz Rybak 
Changed-By: Tomasz Rybak 
Description:
 python-pyopencl - Python module to access OpenCL parallel computation API
 python-pyopencl-dbg - Python module to access OpenCL API (debug extensions)
 python-pyopencl-doc - module to access OpenCL parallel computation API 
(documentation)
 python3-pyopencl - Python 3 module to access OpenCL parallel computation API
 python3-pyopencl-dbg - Python 3 module to access OpenCL API (debug extensions)
Closes: 837488
Changes:
 pyopencl (2016.1+git20160809-2) unstable; urgency=low
 .
   * Add python3.patch for removing improper print

Bug#836717: marked as done (alljoyn-services-1604 and alljoyn-services-1504: error when trying to install together)

2016-09-13 Thread Debian Bug Tracking System 
Your message dated Tue, 13 Sep 2016 18:18:41 +
with message-id 
and subject line Bug#836717: fixed in alljoyn-services-1604 16.04-2
has caused the Debian Bug report #836717,
regarding alljoyn-services-1604 and alljoyn-services-1504: 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.)


-- 
836717: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=836717
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: alljoyn-services-1504,alljoyn-services-1604
Version: alljoyn-services-1504/15.04-4
Version: alljoyn-services-1604/16.4-1
Severity: serious
User: trei...@debian.org
Usertags: edos-file-overwrite

Date: 2016-09-05
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:


Preconfiguring packages ...
Selecting previously unselected package gcc-6-base:amd64.
(Reading database ... 10964 files and directories currently installed.)
Preparing to unpack .../gcc-6-base_6.2.0-2_amd64.deb ...
Unpacking gcc-6-base:amd64 (6.2.0-2) ...
Setting up gcc-6-base:amd64 (6.2.0-2) ...
(Reading database ... 10971 files and directories currently installed.)
Preparing to unpack .../libstdc++6_6.2.0-2_amd64.deb ...
Unpacking libstdc++6:amd64 (6.2.0-2) over (4.8.2-19) ...
Processing triggers for libc-bin (2.24-2) ...
Setting up libstdc++6:amd64 (6.2.0-2) ...
Processing triggers for libc-bin (2.24-2) ...
Selecting previously unselected package libssl1.0.2:amd64.
(Reading database ... 10985 files and directories currently installed.)
Preparing to unpack .../libssl1.0.2_1.0.2h-1_amd64.deb ...
Unpacking libssl1.0.2:amd64 (1.0.2h-1) ...
Selecting previously unselected package libicu57:amd64.
Preparing to unpack .../libicu57_57.1-3_amd64.deb ...
Unpacking libicu57:amd64 (57.1-3) ...
Selecting previously unselected package libxml2:amd64.
Preparing to unpack .../libxml2_2.9.4+dfsg1-1+b1_amd64.deb ...
Unpacking libxml2:amd64 (2.9.4+dfsg1-1+b1) ...
Selecting previously unselected package liballjoyn1504.
Preparing to unpack .../liballjoyn1504_15.04b-7_amd64.deb ...
Unpacking liballjoyn1504 (15.04b-7) ...
Selecting previously unselected package alljoyn-services-1504.
Preparing to unpack .../alljoyn-services-1504_15.04-4_amd64.deb ...
Unpacking alljoyn-services-1504 (15.04-4) ...
Selecting previously unselected package liballjoyn1604.
Preparing to unpack .../liballjoyn1604_16.04-4_amd64.deb ...
Unpacking liballjoyn1604 (16.04-4) ...
Selecting previously unselected package alljoyn-services-1604.
Preparing to unpack .../alljoyn-services-1604_16.04-1_amd64.deb ...
Unpacking alljoyn-services-1604 (16.04-1) ...
dpkg: error processing archive 
/var/cache/apt/archives/alljoyn-services-1604_16.04-1_amd64.deb (--unpack):
 trying to overwrite '/usr/bin/ConsumerService', which is also in package 
alljoyn-services-1504 15.04-4
dpkg-deb: error: subprocess paste was killed by signal (Broken pipe)
Processing triggers for libc-bin (2.24-2) ...
Errors were encountered while processing:
 /var/cache/apt/archives/alljoyn-services-1604_16.04-1_amd64.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):

  /usr/bin/ConsumerService
  /usr/bin/ControlPanelController
  /usr/bin/ControlPanelProducer
  /usr/bin/ControlPanelSample
  /usr/bin/ProducerBasic
  /usr/bin/ProducerService
  /usr/bin/TestService

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

Bug#836719: marked as done (liballjoynservices1604 and liballjoynservices1504: error when trying to install together)

2016-09-13 Thread Debian Bug Tracking System 
Your message dated Tue, 13 Sep 2016 18:18:41 +
with message-id 
and subject line Bug#836719: fixed in alljoyn-services-1604 16.04-2
has caused the Debian Bug report #836719,
regarding liballjoynservices1604 and liballjoynservices1504: 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.)


-- 
836719: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=836719
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: liballjoynservices1504,liballjoynservices1604
Version: liballjoynservices1504/15.04-4
Version: liballjoynservices1604/16.4-1
Severity: serious
User: trei...@debian.org
Usertags: edos-file-overwrite

Date: 2016-09-05
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:


Preconfiguring packages ...
Selecting previously unselected package gcc-6-base:amd64.
(Reading database ... 10964 files and directories currently installed.)
Preparing to unpack .../gcc-6-base_6.2.0-2_amd64.deb ...
Unpacking gcc-6-base:amd64 (6.2.0-2) ...
Setting up gcc-6-base:amd64 (6.2.0-2) ...
(Reading database ... 10971 files and directories currently installed.)
Preparing to unpack .../libstdc++6_6.2.0-2_amd64.deb ...
Unpacking libstdc++6:amd64 (6.2.0-2) over (4.8.2-19) ...
Processing triggers for libc-bin (2.24-2) ...
Setting up libstdc++6:amd64 (6.2.0-2) ...
Processing triggers for libc-bin (2.24-2) ...
Selecting previously unselected package libssl1.0.2:amd64.
(Reading database ... 10985 files and directories currently installed.)
Preparing to unpack .../libssl1.0.2_1.0.2h-1_amd64.deb ...
Unpacking libssl1.0.2:amd64 (1.0.2h-1) ...
Selecting previously unselected package liballjoyn1504.
Preparing to unpack .../liballjoyn1504_15.04b-7_amd64.deb ...
Unpacking liballjoyn1504 (15.04b-7) ...
Selecting previously unselected package liballjoyn1604.
Preparing to unpack .../liballjoyn1604_16.04-4_amd64.deb ...
Unpacking liballjoyn1604 (16.04-4) ...
Selecting previously unselected package liballjoynservices1504.
Preparing to unpack .../liballjoynservices1504_15.04-4_amd64.deb ...
Unpacking liballjoynservices1504 (15.04-4) ...
Selecting previously unselected package liballjoynservices1604.
Preparing to unpack .../liballjoynservices1604_16.04-1_amd64.deb ...
Unpacking liballjoynservices1604 (16.04-1) ...
dpkg: error processing archive 
/var/cache/apt/archives/liballjoynservices1604_16.04-1_amd64.deb (--unpack):
 trying to overwrite 
'/usr/lib/x86_64-linux-gnu/liballjoyn_controlpanel.so.1504', which is also in 
package liballjoynservices1504 15.04-4
dpkg-deb: error: subprocess paste was killed by signal (Broken pipe)
Processing triggers for libc-bin (2.24-2) ...
Errors were encountered while processing:
 /var/cache/apt/archives/liballjoynservices1604_16.04-1_amd64.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):

  /usr/lib/x86_64-linux-gnu/liballjoyn_controlpanel.so.1504
  /usr/lib/x86_64-linux-gnu/liballjoyn_notification.so.1504
  /usr/lib/x86_64-linux-gnu/liballjoyn_services_common.so.1504

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: alljoyn-services-1604
Source-Version: 16.04-2

We believe that the bug you reported is fixed in the latest version of
alljoyn-services-1604, which

Bug#836718: marked as done (alljoyn-services-1604 and alljoyn-services-1509: error when trying to install together)

2016-09-13 Thread Debian Bug Tracking System 
Your message dated Tue, 13 Sep 2016 18:18:41 +
with message-id 
and subject line Bug#836718: fixed in alljoyn-services-1604 16.04-2
has caused the Debian Bug report #836718,
regarding alljoyn-services-1604 and alljoyn-services-1509: 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.)


-- 
836718: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=836718
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: alljoyn-services-1509,alljoyn-services-1604
Version: alljoyn-services-1509/15.09-2
Version: alljoyn-services-1604/16.4-1
Severity: serious
User: trei...@debian.org
Usertags: edos-file-overwrite

Date: 2016-09-05
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:


Preconfiguring packages ...
Selecting previously unselected package gcc-6-base:amd64.
(Reading database ... 10964 files and directories currently installed.)
Preparing to unpack .../gcc-6-base_6.2.0-2_amd64.deb ...
Unpacking gcc-6-base:amd64 (6.2.0-2) ...
Setting up gcc-6-base:amd64 (6.2.0-2) ...
(Reading database ... 10971 files and directories currently installed.)
Preparing to unpack .../libstdc++6_6.2.0-2_amd64.deb ...
Unpacking libstdc++6:amd64 (6.2.0-2) over (4.8.2-19) ...
Processing triggers for libc-bin (2.24-2) ...
Setting up libstdc++6:amd64 (6.2.0-2) ...
Processing triggers for libc-bin (2.24-2) ...
Selecting previously unselected package libssl1.0.2:amd64.
(Reading database ... 10985 files and directories currently installed.)
Preparing to unpack .../libssl1.0.2_1.0.2h-1_amd64.deb ...
Unpacking libssl1.0.2:amd64 (1.0.2h-1) ...
Selecting previously unselected package liballjoyn1509.
Preparing to unpack .../liballjoyn1509_15.09a-4_amd64.deb ...
Unpacking liballjoyn1509 (15.09a-4) ...
Selecting previously unselected package alljoyn-services-1509.
Preparing to unpack .../alljoyn-services-1509_15.09-2_amd64.deb ...
Unpacking alljoyn-services-1509 (15.09-2) ...
Selecting previously unselected package liballjoyn1604.
Preparing to unpack .../liballjoyn1604_16.04-4_amd64.deb ...
Unpacking liballjoyn1604 (16.04-4) ...
Selecting previously unselected package alljoyn-services-1604.
Preparing to unpack .../alljoyn-services-1604_16.04-1_amd64.deb ...
Unpacking alljoyn-services-1604 (16.04-1) ...
dpkg: error processing archive 
/var/cache/apt/archives/alljoyn-services-1604_16.04-1_amd64.deb (--unpack):
 trying to overwrite '/usr/bin/ConsumerService', which is also in package 
alljoyn-services-1509 15.09-2
dpkg-deb: error: subprocess paste was killed by signal (Broken pipe)
Processing triggers for libc-bin (2.24-2) ...
Errors were encountered while processing:
 /var/cache/apt/archives/alljoyn-services-1604_16.04-1_amd64.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):

  /usr/bin/ConsumerService
  /usr/bin/ControlPanelController
  /usr/bin/ControlPanelProducer
  /usr/bin/ControlPanelSample
  /usr/bin/ProducerBasic
  /usr/bin/ProducerService
  /usr/bin/TestService

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: alljoyn-services-1604
Source-Version: 16.04-2

We believe that the bug you reported is fixed in the latest version of
alljoyn-services-1604, which is due to be installed in the

Bug#834558: marked as done (frog FTBFS)

2016-09-13 Thread Debian Bug Tracking System 
Your message dated Tue, 13 Sep 2016 18:19:00 +
with message-id 
and subject line Bug#834558: fixed in frog 0.13.5-1
has caused the Debian Bug report #834558,
regarding frog FTBFS
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.)


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

Package: frog
Version: 0.12.20-1
Severity: serious
x-debbugs-cc: libfo...@packages.debian.org

Frog currently FTBFS in sid as can be seen from the recent binnmus for 
the ICU transition


I have been trying to get the ICU transition to go through in raspbian 
stretch. I first patched libfolia to get it building again, then our 
autobinnmuer rebuilt ucto, then it tried to rebuild frog.


Frog failed with a different error to in Debian, I strongly belive that 
the errors I saw in raspbian will affect Debian too and it is just 
masked at the monent by an earlier failure.


I belive that the failures Debian is currently seeing in frog and ucto 
are caused by building packages in the libfolia/ucto/frog depchain with 
a mixture of toolchains. Possiblly this should be handled as a library 
transition.


The first error I saw with frog in Raspbian was:


../include/frog/FrogAPI.h:38:34: fatal error: timblserver/FdStream.h: No such 
file or directory
  #include "timblserver/FdStream.h"
It seems this header and another one included on the next line have 
moved to ticcutils/


I then got a load of errors that looked like namespace issues. Adding a 
bunch of "using namespace TiCC" and "using namespace Tagger" fixed those.


I have uploaded the fixes to raspbian, a debdiff should appear soon at 
https://debdiffs.raspbian.org/main/f/frog/frog_0.12.20-1+rpi1.debdiff
--- End Message ---
--- Begin Message ---
Source: frog
Source-Version: 0.13.5-1

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

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

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

Debian distribution maintenance software
pp.
Maarten van Gompel  (supplier of updated frog package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Format: 1.8
Date: Tue, 02 Aug 2016 13:55:00 +0200
Source: frog
Binary: frog libfrog1
Architecture: source
Version: 0.13.5-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Science Team 

Changed-By: Maarten van Gompel 
Description:
 frog   - tagger and parser for natural languages (runtime)
 libfrog1   - tagger and parser for Dutch language (library)
Closes: 828017 834558
Changes:
 frog (0.13.5-1) unstable; urgency=medium
 .
   [ Maarten van Gompel ]
   * Updated to new upstream 0.13.5
 (Missed: 0.13.0, 0.13.3, 0.13.4)
   * debian/copyright: updated years and added Radboud University
   * debian/control: updated dependency versions & no python needed anymore,
 updated standards version
   * debian/watch: pointing to make dist release instead of bare sources
   * debian/watch: pointing to github now (v0.13 ready there)
   * Added dh-autoreconf build dependency
   * Build should be reproducible now python dependency is gone
 (Closes: #828017)
   * Website update
   * Removed Joost van Baal-Ilić as uploader
   * Removed explicit libucto2 dependency, should be automatically
 extracted according to Anton Gladky
   * New upstream release fixes reported header issues, namespace
 statements in source files instead of headers.
 (Closes: #834558)
Checksums-Sha1:
 05ccc30c41f36ed03ffc60c55bb40924232120c4 2272 frog_0.13.5-1.dsc
 723d9e97947377522b3e71b5da4d1bbf4e409563 516084 frog_0.13.5.orig.tar.gz
 7e01ddd92a6f51c9453f4f4f9f2b2ca578ad02d9 6392 frog_0.13.5-1.debian.tar.xz
Checksums-Sha256:
 1802ebe521d5ebd94305637c0857218f9c00813f97b3a2c8fe4ebe470d5675f6 2272 
frog_0.13.5-1.dsc
 adc7ca7f7cd330bfc85b32eb0475b10bb285e5ba113f6d7479c86daae7c85be4 516084 
frog_0.13.5.orig.tar.gz
 299b2eed53be25a24e234c1a577e042595a385a6efb43987deb074772d6a5d36 6392 
frog_0.13.5-1.debian.tar.xz
Files:
 9154510f0ca33ee4646d80d29bf3af1b 2272 science

Bug#837700: gnutls: GNUTLS segfaults on initialization

2016-09-13 Thread Andreas Metzler 
On 2016-09-13 J Phelps  wrote:
> Package: libgnutls30
> Version: 3.5.4-2
> Severity: grave
> File: gnutls
> Justification: renders package unusable

> The bug is caused by GNUTLS being compiled with the headers of and old
> version of Nettle, but the package depending on (or failing to account
> for a breaking change to) a newer version of Nettle.
[...]
> By doing this, I was able to get Chromium 53.0.2785.92 working, which was
> previously crashing because of this problem.
 

Can you provide a (simple) way to reproduce the issue?

Your diagnosis cannot be completely correct. e.g. libgnutls30
3.5.4-2 on i386 (which you reported the issue against) was built against
nettle-dev i386 3.2-1 which continues to be the latest version of nettle
available in Debian. So you cannot experience a breakage in Debian
caused by the Debian-installed nettle version being newer and having a
different ABI than the version GnuTLS was built against.

TIA, cu Andreas
-- 
`What a good friend you are to him, Dr. Maturin. His other friends are
so grateful to you.'
`I sew his ears on from time to time, sure'

Processed: notfound 836717 in 15.04-4, notfound 836718 15.09-2, notfound 836719 15.04-4

2016-09-13 Thread Debian Bug Tracking System 
Processing commands for cont...@bugs.debian.org:

> notfound 836717 15.04-4
Bug #836717 [alljoyn-services-1504,alljoyn-services-1604] alljoyn-services-1604 
and alljoyn-services-1504: error when trying to install together
There is no source info for the package 'alljoyn-services-1604' at version 
'15.04-4' with architecture ''
No longer marked as found in versions alljoyn-services-1504/15.04-4.
> found 836717 16.04-1
Bug #836717 [alljoyn-services-1504,alljoyn-services-1604] alljoyn-services-1604 
and alljoyn-services-1504: error when trying to install together
There is no source info for the package 'alljoyn-services-1504' at version 
'16.04-1' with architecture ''
Ignoring request to alter found versions of bug #836717 to the same values 
previously set
> found 836718 16.04-1
Bug #836718 [alljoyn-services-1509,alljoyn-services-1604] alljoyn-services-1604 
and alljoyn-services-1509: error when trying to install together
There is no source info for the package 'alljoyn-services-1509' at version 
'16.04-1' with architecture ''
Ignoring request to alter found versions of bug #836718 to the same values 
previously set
> notfound 836718 15.09-2
Bug #836718 [alljoyn-services-1509,alljoyn-services-1604] alljoyn-services-1604 
and alljoyn-services-1509: error when trying to install together
There is no source info for the package 'alljoyn-services-1604' at version 
'15.09-2' with architecture ''
No longer marked as found in versions alljoyn-services-1509/15.09-2.
> notfound 836719 15.04-4
Bug #836719 [liballjoynservices1504,liballjoynservices1604] 
liballjoynservices1604 and liballjoynservices1504: error when trying to install 
together
There is no source info for the package 'liballjoynservices1604' at version 
'15.04-4' with architecture ''
No longer marked as found in versions alljoyn-services-1504/15.04-4.
> found 836719 16.04-1
Bug #836719 [liballjoynservices1504,liballjoynservices1604] 
liballjoynservices1604 and liballjoynservices1504: error when trying to install 
together
There is no source info for the package 'liballjoynservices1504' at version 
'16.04-1' with architecture ''
Ignoring request to alter found versions of bug #836719 to the same values 
previously set
> thanks
Stopping processing here.

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

Bug#837700: gnutls: GNUTLS segfaults on initialization

2016-09-13 Thread J Phelps 
Package: libgnutls30
Version: 3.5.4-2
Severity: grave
File: gnutls
Justification: renders package unusable

The bug is caused by GNUTLS being compiled with the headers of and old
version of Nettle, but the package depending on (or failing to account
for a breaking change to) a newer version of Nettle.

In the newer version of Nettle, in the struct "yarrow256_ctx", the type
of the "key" member has changed from "aes256_ctx" to "aes_ctx".

"aes_ctx" is like "aes256_ctx", except it has an extra integer, which
makes the whole yarrow256_ctx type one integer bigger as well.

GNUTLS contains a yarrow256_ctx in one of its structs, followed
immediately by a buffer, but it's compiled with the old yarrow256_ctx,
which is too small. Both the struct and the buffer are passed
as arguments to yarrow256_init, but in Nettle's code, yarrow256_ctx
is bigger, so the buffer is treated as being within the yarrow256_ctx
object's address space. As a result, initializing the buffer overwrites
a pointer in the yarrow256_ctx object, leading to a NULL pointer
dereference.

A quick fix to this problem is to simply edit /usr/include/nettle/yarrow.h
and add a padding integer (of type "unsigned") to its definition of
"yarrow256_ctx" right after the "key" object, and then recompiling
GNUTLS. This is good enough, since GNUTLS doesn't look at the internal
structure of yarrow256_ctx, so only the size needs to be corrected.

By doing this, I was able to get Chromium 53.0.2785.92 working, which was
previously crashing because of this problem.


-- System Information:
Debian Release: jessie/sid
  APT prefers unstable
  APT policy: (500, 'unstable'), (500, 'testing'), (500, 'stable')
Architecture: i386 (i686)

Kernel: Linux 3.16.0-4-686-pae (SMP w/4 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash

Versions of packages libgnutls30:i386 depends on:
ii  libc62.24-2
ii  libgmp10 2:6.0.0+dfsg-6
ii  libhogweed4  3.2-1
ii  libidn11 1.28-1
ii  libnettle6   3.2-1
ii  libp11-kit0  0.23.2-5
ii  libtasn1-6   4.8-1
ii  zlib1g   1:1.2.8.dfsg-1

libgnutls30:i386 recommends no packages.

Versions of packages libgnutls30:i386 suggests:
pn  gnutls-bin  

-- no debconf information

Bug#835731: marked as done (libdbix-class-perl: FTBFS: Tests failures)

2016-09-13 Thread Debian Bug Tracking System 
Your message dated Tue, 13 Sep 2016 17:44:31 +
with message-id 
and subject line Bug#835731: fixed in libdbix-class-perl 0.082840-2
has caused the Debian Bug report #835731,
regarding libdbix-class-perl: FTBFS: Tests failures
to be marked as done.

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

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


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

Hi,

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

Relevant part (hopefully):
> ok 3 # skip Not checking for bless handling as performance is OK
> 1..3
> # Auto checked 0 references for leaks - none detected
> ok
> t/zzz_sqlite_deadlock.t . skipped: Skipping test 
> on plain module install
> 
> Test Summary Report
> ---
> t/prefetch/grouped.t  (Wstat: 65280 Tests: 31 
> Failed: 1)
>   Failed test:  28
>   Non-zero exit status: 255
>   Parse errors: No plan found in TAP output
> Files=308, Tests=13370, 114 wallclock secs ( 2.17 usr  0.60 sys + 106.21 cusr 
>  5.45 csys = 114.43 CPU)
> Result: FAIL
> Failed 1/308 test programs. 1/13370 subtests failed.
> Makefile:1697: recipe for target 'test_dynamic' failed

The full build log is available from:
   
http://people.debian.org/~lucas/logs/2016/08/28/libdbix-class-perl_0.082840-1_unstable.log

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

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

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

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

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

Debian distribution maintenance software
pp.
gregor herrmann  (supplier of updated libdbix-class-perl 
package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Tue, 13 Sep 2016 19:22:40 +0200
Source: libdbix-class-perl
Binary: libdbix-class-perl
Architecture: source
Version: 0.082840-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Perl Group 
Changed-By: gregor herrmann 
Closes: 835731
Description: 
 libdbix-class-perl - extensible and flexible object <-> relational mapper
Changes:
 libdbix-class-perl (0.082840-2) unstable; urgency=medium
 .
   * Add another level of tests to debian/tests/pkg-perl/smoke-tests.
 Thanks to Peter Rabbitson for the pointer.
   * Remove Brian Cassidy, Jonathan Yu, and Ryan Niebur from Uploaders.
 Thanks for your work!
   * Cherry-pick patch from upstream Git repo to fix test failure caused by
 newer libsqlite. (Closes: #835731)
 Thanks again to Peter Rabbitson.
Checksums-Sha1: 
 4819ba861dd698e97f714bd06430cf1cde8bc07a 3387 libdbix-class-perl_0.082840-2.dsc
 1747b39233f865233dd54dcfec1cf8884caa6e72 14080 
libdbix-class-perl_0.082840-2.debian.tar.xz
Checksums-Sha256: 
 4b1905c13ebf3a4e4c2ae0d23d451429afad767a6dc287b8f4d72c4ae7cd9f7d 3387 
libdbix-class-perl_0.082840-2.dsc
 1486b2824e4ff196064aaa0d980ed259f6819533824c2e2b213d778643491026 14080 
libdbix-class-perl_0.082840-2.debian.tar.xz
Files: 
 2605c1f5cc563016d029a107cb47cf78 3387 perl optional 
libdbix-class-perl_0.082840-2.dsc
 d1a3e254318d52b94b23f5b979ff3bed 14080 perl optional 
libdbix-class-perl_0.082840-2.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQJ8BAEBCgBmBQJX2DZwXxSAAC4AKGlzc3Vlci1mcHJAbm90YXRpb25zLm9w
ZW5wZ3AuZmlmdGhob3JzZW1hbi5uZXREMUUxMzE2RTkzQTc2MEE4MTA0RDg1RkFC
QjNBNjgwMTg2NDlBQTA2AAoJELs6aAGGSaoGahoP/RrBzc+YOu8+uXhiNW/KLBGu

Bug#837121: marked as done (gazebo: please restrict libkido-dev (build-)dependency to architectures where it is available.)

2016-09-13 Thread Debian Bug Tracking System 
Your message dated Tue, 13 Sep 2016 17:42:35 +
with message-id 
and subject line Bug#837121: fixed in gazebo 7.3.0+dfsg-5
has caused the Debian Bug report #837121,
regarding gazebo: please restrict libkido-dev (build-)dependency to 
architectures where it is available.
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.)


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

Package: gazebo
Version: 7.3.0+dfsg-3
Severity: serious
Tags: patch

The most recent version of gazebo added a build-dependency on 
libkido-dev to the source package and added a binary on libkido-dev to 
libgazebo7-dev


No mention of this was made in the changelog and no other changes in the 
upload seem to be related but 
https://anonscm.debian.org/git/debian-science/packages/gazebo.git/commit/?id=80f9a218ccebb32258812afdf1cce6b50ab88126 
indicates this was to add support for a new feature.


libkido-dev is only available on a handful of architectures. As a result 
this new (build-)dependency is blocking the migration of the new version 
of the package (and hence the FTBFS fix) to testing.


The attatched patch restricts the (build-)dependencies on libkido-dev to 
the architectures where it is actually available (amd64, arm64, i386, 
ppc64el and alpha)
diff -Nru gazebo-7.3.0+dfsg/debian/changelog gazebo-7.3.0+dfsg/debian/changelog
--- gazebo-7.3.0+dfsg/debian/changelog  2016-08-31 17:57:53.0 +
+++ gazebo-7.3.0+dfsg/debian/changelog  2016-09-07 15:06:23.0 +
@@ -1,3 +1,10 @@
+gazebo (7.3.0+dfsg-3+rpi1) stretch-staging; urgency=medium
+
+  * Restrict (build-)dependency on libkido-dev to architectures where that 
package
+is actually available (amd64, arm64, i386, ppc64el and alpha). 
+
+ -- Peter Michael Green   Wed, 07 Sep 2016 15:06:23 
+
+
 gazebo (7.3.0+dfsg-3) unstable; urgency=medium
 
   [ Jochen Sprickerhof ]
diff -Nru gazebo-7.3.0+dfsg/debian/control gazebo-7.3.0+dfsg/debian/control
--- gazebo-7.3.0+dfsg/debian/control2016-08-30 22:54:59.0 +
+++ gazebo-7.3.0+dfsg/debian/control2016-09-07 15:06:07.0 +
@@ -45,7 +45,7 @@
libbullet-dev,
libsimbody-dev,
libsimbody-dev (<< 4.0.0),
-   libkido-dev,
+   libkido-dev [amd64 arm64 i386 powerpc alpha],
libgdal-dev,
ruby-ronn,
libgtest-dev
@@ -138,7 +138,7 @@
  libignition-math2-dev,
  libbullet-dev,
  libsimbody-dev,
- libkido-dev,
+ libkido-dev [amd64 arm64 i386 powerpc alpha],
  libgazebo7 (= ${binary:Version}),
  gazebo7-common (= ${source:Version}),
  gazebo7-plugin-base (= ${binary:Version}),
--- End Message ---
--- Begin Message ---
Source: gazebo
Source-Version: 7.3.0+dfsg-5

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

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

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

Debian distribution maintenance software
pp.
Jose Luis Rivero  (supplier of updated gazebo 
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, 12 Sep 2016 16:23:58 +
Source: gazebo
Binary: gazebo7-common gazebo7 libgazebo7 libgazebo7-dev gazebo7-plugin-base 
gazebo7-doc
Architecture: source
Version: 7.3.0+dfsg-5
Distribution: unstable
Urgency: medium
Maintainer: Debian Science Maintainers 

Changed-By: Jose Luis Rivero 
Description:
 gazebo7- Open Source Robotics Simulator - Binaries
 gazebo7-common - Open Source Robotics Simulator - Shared files
 gazebo7-doc - Open Source Robotics Simulator - Documentation
 gazebo7-plugin-base - Open Source Robotics Simulator - base plug-ins
 libgazebo7 - Open Source Robotics Simulator - shared library
 libgazebo7-dev - Open Source Robotics Simulator - Development Files
Closes: 837121
Changes:
 gazebo (7.3.0+dfsg-5) unstable; urgency=medium
 .
   * Use the

Bug#837614: Use and abuse of the unreproducible tag

2016-09-13 Thread Markus Koschany 
On 13.09.2016 18:25, Adam D. Barratt wrote:
> On 2016-09-13 12:55, Sebastiaan Couwenberg wrote:
>> On 09/13/2016 01:49 PM, Santiago Vila wrote:
>>> You can't reproduce it, or you don't want to reproduce it?
>>
>> I added the tag because I couldn't reproduce the issue in unstable where
>> we build our packages. It's great that it's reproducible in testing, but
>> we don't upload to testing.
> 
> Sometimes we do...
> 
> In any case, that's not the point. Testing is what will become stable.
> Packages in stable need to be buildable on stable (for security updates
> and point releases) and "does the package currently build in testing?"
> is the best approximation we can have to "will the package build when
> it's in stable?".
> 
>> I consider the tag appropriate, if there is
>> consensus in the project that it's not feel free to remove the tags
>> again.
> 
> Regardless of whether there's consensus that you agree with, it's an RC
> bug to not build within the same release, and has been for several
> releases now.

Several people are missing the point here in my opinion. The issue here
is that the packages, python-geopandas (#837614) and python-stetl
(#837622) have the exact same version in testing and unstable. The
maintainer rightfully pointed out that this issue might be related to
the current transition of gdal.

There are usually two common reasons why a package FTBFS in testing and
not in unstable. The first one is a missing versioned dependency or
build-dependency, the other one is unrelated to the package itself. It
is affected by issues in other packages.

So instead of playing severity and tag ping-pong, the time would be
better spent into investigating if the gdal transition is causing the
FTBFS in Stretch. Help from the bug submitter would be surely welcome.
Then the bug report should be reassigned to the related transition bug
and both python packages marked as "affected". There is nothing else the
maintainer could have done in this case.

What I find disturbing is that we really think that shaming the
maintainer would be a better approach. Who cares if he uses the
unreproducible tag, if he wants to get feedback about the issue from
others? We should care more about the human cost of this thread.

Regards,

Markus




signature.asc
Description: OpenPGP digital signature

Bug#835731: Pending fixes for bugs in the libdbix-class-perl package

2016-09-13 Thread pkg-perl-maintainers 
tag 835731 + pending
thanks

Some bugs in the libdbix-class-perl package are closed in revision
c7f237f72a1694e2c0a97177faad53528cee50cd in branch 'master' by gregor
herrmann

The full diff can be seen at
https://anonscm.debian.org/cgit/pkg-perl/packages/libdbix-class-perl.git/commit/?id=c7f237f

Commit message:

Cherry-pick patch from upstream Git repo

to fix test failure caused by newer libsqlite.

Closes: #835731

Processed: Pending fixes for bugs in the libdbix-class-perl package

2016-09-13 Thread Debian Bug Tracking System 
Processing commands for cont...@bugs.debian.org:

> tag 835731 + pending
Bug #835731 [src:libdbix-class-perl] libdbix-class-perl: FTBFS: Tests failures
Added tag(s) pending.
> thanks
Stopping processing here.

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

Bug#837254: @pytest.skip outside test gives error

2016-09-13 Thread Nikolaus Rath 
Control: reassign 837254 pytest

On Sep 10 2016, Lucas Nussbaum  wrote:
>> collecting ... 
>>  ERRORS 
>> 
>> __ ERROR collecting test_examples.py 
>> ___
>> Using @pytest.skip outside of a test (e.g. as a test function decorator) is 
>> not allowed. Use @pytest.mark.skip or @pytest.mark.skipif instead.
>>  Interrupted: stopping after 1 failures 
>> 
>> === 1 error in 0.23 seconds
>> 

This (still) is a bug in pytest. I think it has already been fixed
upstream (I remember getting a message about that).

Best,
-Nikolaus

-- 
GPG encrypted emails preferred. Key id: 0xD113FCAC3C4E599F
Fingerprint: ED31 791B 2C5C 1613 AF38 8B8A D113 FCAC 3C4E 599F

 »Time flies like an arrow, fruit flies like a Banana.«

Processed: @pytest.skip outside test gives error

2016-09-13 Thread Debian Bug Tracking System 
Processing control commands:

> reassign 837254 pytest
Bug #837254 [src:python-llfuse] python-llfuse: FTBFS: E: pybuild pybuild:276: 
test: plugin distutils failed with: exit code=2: cd 
/<>/python-llfuse-1.1.1+dfsg/.pybuild/pythonX.Y_2.7/build; python2.7 
-m pytest --installed "{dir}/test/"
Bug reassigned from package 'src:python-llfuse' to 'pytest'.
No longer marked as found in versions python-llfuse/1.1.1+dfsg-2.
Ignoring request to alter fixed versions of bug #837254 to the same values 
previously set

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

Bug#832077: Info received (emacs clutter screen on windows switch)

2016-09-13 Thread beefreak 
Hi,
mate-term, caja, emacs etc. is also affected.
Please roll back to 3.20.9-1 and test also with mate, if libgtk-3 work
well with other software too.

Please, please do not demolish debian.
Please do less, but with care.

Bug#833753: marked as done (ledger: FTBFS on buildds after gcc6/icu57/boost1.61)

2016-09-13 Thread Debian Bug Tracking System 
Your message dated Tue, 13 Sep 2016 16:37:25 +
with message-id 
and subject line Bug#833753: fixed in ledger 3.1.2~pre1+g3a00e1c+dfsg1-1
has caused the Debian Bug report #833753,
regarding ledger: FTBFS on buildds after gcc6/icu57/boost1.61
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.)


-- 
833753: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=833753
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
source: ledger
version:  3.1.1+dfsg1-1
severity: serious

Dear maintainer,

your package failed to build on buildds during a transition rebuild
using gcc-6 boost1.61 and icu57.
One or more of those changed toolchain packages caused the failure, see
https://buildd.debian.org/status/logs.php?pkg=ledger=3.1.1%2Bdfsg1-1%2Bb2=sid

-- 
regards,
Mattia Rizzolo

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


signature.asc
Description: PGP signature
--- End Message ---
--- Begin Message ---
Source: ledger
Source-Version: 3.1.2~pre1+g3a00e1c+dfsg1-1

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

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

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

Debian distribution maintenance software
pp.
David Bremner  (supplier of updated ledger package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Tue, 13 Sep 2016 11:55:15 -0300
Source: ledger
Binary: ledger ledger-el python-ledger ledger-dbg
Architecture: source
Version: 3.1.2~pre1+g3a00e1c+dfsg1-1
Distribution: unstable
Urgency: medium
Maintainer: Matt Palmer 
Changed-By: David Bremner 
Description:
 ledger - command-line double-entry accounting program
 ledger-dbg - command-line double-entry accounting program (debug symbols)
 ledger-el  - command-line double-entry accounting program (emacs interface)
 python-ledger - command-line double-entry accounting program (python extension)
Closes: 833753
Changes:
 ledger (3.1.2~pre1+g3a00e1c+dfsg1-1) unstable; urgency=medium
 .
   * New upstream release snapshot
   * Cherry-pick upstream pull request 465. Bug fix: "FTBFS on buildds
  after gcc6/icu57/boost1.61", thanks to Mattia Rizzolo (Closes:
  #833753).
Checksums-Sha1:
 4642b99bb2e74409f8d7b83d68693b4abd2e3519 2313 
ledger_3.1.2~pre1+g3a00e1c+dfsg1-1.dsc
 b971da05fd226072b1e71b1a0003237c394688fc 814600 
ledger_3.1.2~pre1+g3a00e1c+dfsg1.orig.tar.gz
 cee35aa1019c5e0e8cc5c73092a7e34f690858da 34324 
ledger_3.1.2~pre1+g3a00e1c+dfsg1-1.debian.tar.xz
Checksums-Sha256:
 f5d440c869eb7677bb6583f487f2c276f0719f149663b03b70b0a770b1bbe844 2313 
ledger_3.1.2~pre1+g3a00e1c+dfsg1-1.dsc
 4d020edecd9075504d8f6b7f51fe48bbc0c20327d6b41b888489e3a0d93f0cf9 814600 
ledger_3.1.2~pre1+g3a00e1c+dfsg1.orig.tar.gz
 cc62c969fa3fa23fff887e6eeb5935b35b0830e43bf4d02e864463d6edfac6c6 34324 
ledger_3.1.2~pre1+g3a00e1c+dfsg1-1.debian.tar.xz
Files:
 164073b5f76aabaad5b6dcf1de0ba767 2313 utils optional 
ledger_3.1.2~pre1+g3a00e1c+dfsg1-1.dsc
 48177d22d142c40959455c853289cb4b 814600 utils optional 
ledger_3.1.2~pre1+g3a00e1c+dfsg1.orig.tar.gz
 780d58eaed0b1c15bc90df660a458fc6 34324 utils optional 
ledger_3.1.2~pre1+g3a00e1c+dfsg1-1.debian.tar.xz

-BEGIN PGP SIGNATURE-
Version: GnuPG v2

iQGcBAEBCAAGBQJX2BnWAAoJEPIClx2kp54s1MgL/1AQG9Mv0MLQSZCEoU/DMS9S
0luwlb/EWyvQKfNo7Dk0T+xSelu1vxsRtcZcnB3QChuJ200XwdkuzqKscyvoUcEC
QfibM2bHTejk0MY4cBKtz+O2uwO0rs2iFli51K0vuhqmosyqe8WXRPxrCbUaPaL4
y5lK8OFkkYylhU+0uRob/pds1jVx4KdzXBCL0R+ByyUpcCF5kcKlDCNiuY3AtNQt
d02LkEJgwqg722Fn9q2v/P5fE+aaESdu3WydYppYe1Hd6ahejFsHdI42ST9pOpxg
/MFChg5BycUoP9eifAmisYstfU3ILF+BygiCSBPmMeFc7ujDETr+ifaHMulpyux6
N3Vx3FJFB+99dRvX2E3QaoFFxZdeMVfJyGo73viyXV1shTTeHrQr8boWR3zOwee4
w6x6UtJ0jQ1BimZ4hynkqIvHcarqaZzZnhD6CtNDZhTppiVlA9HW0q8eMoSAYJuC
71ePJlCxJS6SkEBcPFsonA0UZO+GFgR04b1oLnrKeA==
=+7sr
-END PGP SIGNATURE End Message ---

Bug#813722: marked as done (aces3: FTBFS on powerpc)

2016-09-13 Thread Debian Bug Tracking System 
Your message dated Tue, 13 Sep 2016 16:11:52 +0100
with message-id <71331f6c-c0fb-0c07-3a6a-3ce7905c5...@debian.org>
and subject line closed in 2.0.1-5
has caused the Debian Bug report #813722,
regarding aces3: FTBFS on powerpc
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.)


-- 
813722: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=813722
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: aces3
Version: 3.0.8-5
Severity: serious
Control: block 813128 by -1

Dear maintainer,

your package FTBFS on powercpc on the buildds.
The build has been retried 2 times, with the same results.
Allegedly it hangs on the tests, and the timeout kicks in, failing the
build:


   debian/rules override_dh_auto_test
make[1]: Entering directory '/«PKGBUILDDIR»'
(cd tests; OMPI_MCA_orte_rsh_agent=/bin/false csh ./runscript-quick)
Running 1.1.1.1
[powerpc-osuosl-01:19462] 1 more process has sent help message help-mpi-api.txt 
/ mpi-abort
[powerpc-osuosl-01:19462] Set MCA parameter "orte_base_help_aggregate" to 0 to 
see all help / error messages
Running 1.1.2.1
[powerpc-osuosl-01:19486] 1 more process has sent help message help-mpi-api.txt 
/ mpi-abort
[powerpc-osuosl-01:19486] Set MCA parameter "orte_base_help_aggregate" to 0 to 
see all help / error messages
Running 1.1.3.1
[powerpc-osuosl-01:19512] 1 more process has sent help message help-mpi-api.txt 
/ mpi-abort
[powerpc-osuosl-01:19512] Set MCA parameter "orte_base_help_aggregate" to 0 to 
see all help / error messages
Running 1.1.4.1
E: Caught signal ‘Terminated’: terminating immediately
debian/rules:32: recipe for target 'override_dh_auto_test' failed
make[1]: [override_dh_auto_test] Terminated (ignored)
debian/rules:28: recipe for target 'build-arch' failed
make: *** [build-arch] Terminated
Build killed with signal TERM after 150 minutes of inactivity

See
https://buildd.debian.org/status/logs.php?pkg=aces3=3.0.8-5%2Bb1=powerpc

-- 
regards,
Mattia Rizzolo

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


signature.asc
Description: PGP signature
--- End Message ---
--- Begin Message ---
close 812733

close 814183

thanks


I'm closing these bugs as fixed / unreproducible in 2.0.1-5. In
particular I've rebuilt both aces3 and petsc on powerpc and mipsel (on
partch.debian.org and eller.debian.org) and they build successfully.

There have been code changes and bug fixes in the wait /lock code, as
well as now using standard gcc atomics on both architectures, which
means the relevant code paths have changed.

Please reopen if the bug is seen again, but it is believed fixed.


Regards

Alastair


-- 
Alastair McKinstry, , , 
https://diaspora.sceal.ie/u/amckinstry
Misentropy: doubting that the Universe is becoming more disordered. 




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

Bug#814183: marked as done (openmpi 1.10.2 is broken on powerpc)

2016-09-13 Thread Debian Bug Tracking System 
Your message dated Tue, 13 Sep 2016 16:11:52 +0100
with message-id <71331f6c-c0fb-0c07-3a6a-3ce7905c5...@debian.org>
and subject line closed in 2.0.1-5
has caused the Debian Bug report #814183,
regarding openmpi 1.10.2 is broken on powerpc
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.)


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

Package: src:openmpi
Version: 1.10.2-5
Severity: serious
Tags: sid stretch

openmpi 1.10.2 is broken on powerpc.

Graham Inggs confirmed that at least aces3 and petsc fail in the same way in 
Debian unstable, as soon the mpi test program is launched.


[...]
Possible error running C/C++ src/snes/examples/tutorials/ex19 with 1 MPI process
See http://www.mcs.anl.gov/petsc/documentation/faq.html
--
A deprecated MCA variable value was specified in the environment or
on the command line.  Deprecated MCA variables should be avoided;
they may disappear in future releases.

  Deprecated variable: orte_rsh_agent
  New variable:plm_rsh_agent
--
lid velocity = 0.0016, prandtl # = 1, grashof # = 1
Number of SNES iterations = 2

Session terminated, terminating shell... ...terminated.
make: *** [build-arch] Terminated

build logs:
https://launchpad.net/ubuntu/+source/aces3/3.0.8-5build2/+build/8974836
https://launchpad.net/ubuntu/+source/petsc/3.6.2.dfsg1-3build2/+build/8975053
--- End Message ---
--- Begin Message ---
close 812733

close 814183

thanks


I'm closing these bugs as fixed / unreproducible in 2.0.1-5. In
particular I've rebuilt both aces3 and petsc on powerpc and mipsel (on
partch.debian.org and eller.debian.org) and they build successfully.

There have been code changes and bug fixes in the wait /lock code, as
well as now using standard gcc atomics on both architectures, which
means the relevant code paths have changed.

Please reopen if the bug is seen again, but it is believed fixed.


Regards

Alastair


-- 
Alastair McKinstry, , , 
https://diaspora.sceal.ie/u/amckinstry
Misentropy: doubting that the Universe is becoming more disordered. 




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

Bug#821731: ctk: FTBFS: ctkDICOMUtil.cpp:33:3: error: 'log4cplus' has not been declared

2016-09-13 Thread Gert Wollny 
Hi,

Some time ago there was some activity with an upstream issue [1] about
making the package ready for proper inclusion into Debian.

Unfortunately upstream doesn't properly document dependencies and seems
to have the habit to use locally patched versions of these dependencies
if they feel like it.

Given that they are also reluctant to tag a release, and the only useful
dependent package would be Slicer (which has exactly the same issues), I
think that packaging CTK doesn't make much sense.

Best,

Gert

[1] https://github.com/commontk/CTK/issues/608





signature.asc
Description: OpenPGP digital signature

Bug#837682: libconfig-model-itself-perl: FTBFS in unstable (failing tests)

2016-09-13 Thread Dominique Dumont 
On Tue, 13 Sep 2016 15:55:27 +0200 (CEST) Santiago Vila  wrote:
> I'm reporting this against libconfig-model-itself-perl because that's
> the package which FTBFS, but of course it is completely possible (and
> maybe likely) that this is still a bug in libconfig-model-perl.
> 
> But I'm no perl expert to tell, so I leave that detail to you. If you
> need to reassign, just do. This time I'm using affects just from the
> beginning as an experiment to see if it works.

Confirmed :-(

Here's what I get on my system:
$ perl -I lib t/itself.t e
ok 1 - compiled
ok 2 - loaded Master model
ok 3 - created master_model instance
ok 4 - loaded some data in master_model instance
ok 5 - dumped master instance
ok 6 - Read Itself::Model and created instance
Configuration item has a configuration model declaration error:
load error: couldn't do 
.//usr/share/perl5/Config/Model/models/Itself/ConfigWR.d/augeas-backend.pl: No 
such file or directory
Exception thrown  at /usr/share/perl5/Config/Model/Exception.pm line 69.

Config::Model::Exception::rethrow(Config::Model::Exception::ModelDeclaration=HASH(0x39b3088))
 called at /usr/share/perl5/Config/Model/Exception.pm line 64

Config::Model::Exception::throw("Config::Model::Exception::ModelDeclaration", 
"message", "load error: couldn't do .//usr/share/perl5/Config/Model/model"...) 
called at /usr/share/perl5/Config/Model.pm line 1267
Config::Model::_do_model_file(Config::Model=HASH(0x2e88c50), 
"/usr/share/perl5/Config/Model/models/Itself/ConfigWR.d/augeas"...) called at 
/usr/share/perl5/Config/Model.pm line 1227
Config::Model::_load_model_in_hash(Config::Model=HASH(0x2e88c50), 
HASH(0x2ab1808), 
"/usr/share/perl5/Config/Model/models/Itself/ConfigWR.d/augeas"...) called at 
/usr/share/perl5/Config/Model.pm line 1204
Config::Model::load(Config::Model=HASH(0x2e88c50), "Itself::Class") 
called at /usr/share/perl5/Config/Model.pm line 1316
Config::Model::get_model(Config::Model=HASH(0x2e88c50), 
"Itself::Class") called at /usr/share/perl5/Config/Model/Role/NodeLoader.pm 
line 27

Config::Model::Role::NodeLoader::load_node(Config::Model::HashId=HASH(0x398a4a8),
 "element_name", "class", "index_value", "MasterModel", "instance", 
Config::Model::Instance=HASH(0x38b4780), "parent", 
Config::Model::Node=HASH(0x38c4218), ...) called at 
/usr/share/perl5/Config/Model/AnyId.pm line 889

Config::Model::AnyId::auto_vivify(Config::Model::HashId=HASH(0x398a4a8), 
"MasterModel") called at /usr/share/perl5/Config/Model/AnyId.pm line 688

Config::Model::AnyId::fetch_with_id(Config::Model::HashId=HASH(0x398a4a8), 
"MasterModel") called at lib/Config/Model/Itself.pm line 332
Config::Model::Itself::read_all(Config::Model::Itself=HASH(0x38c3e10), 
"root_model", "MasterModel", "legacy", "ignore") called at t/itself.t line 113


Looks like I cannot find a way to handle the removal of '.' from @INC

I may need to avoid using 'do' and revisit completely the way model files are 
loaded...

Thanks fo r the report

-- 
 https://github.com/dod38fr/   -o- http://search.cpan.org/~ddumont/
http://ddumont.wordpress.com/  -o-   irc: dod at irc.debian.org

Bug#837682: libconfig-model-itself-perl: FTBFS in unstable (failing tests)

2016-09-13 Thread Santiago Vila 
Package: src:libconfig-model-itself-perl
Version: 2.005-1
Affects: src:libconfig-model-itself-perl
Severity: serious

Dear maintainer:

This package FTBFS in unstable, even when using libconfig-model-perl
version 2.090-1, so this seems to be a problem different than the one
that was reported in bugs #837133 and #837613.

I'm reporting this against libconfig-model-itself-perl because that's
the package which FTBFS, but of course it is completely possible (and
maybe likely) that this is still a bug in libconfig-model-perl.

But I'm no perl expert to tell, so I leave that detail to you. If you
need to reassign, just do. This time I'm using affects just from the
beginning as an experiment to see if it works.

The full build log is attached.

Thanks.

libconfig-model-itself-perl_2.005-1_amd64-20160912T221114Z.gz
Description: application/gzip

Processed: Re: Bug#837613: libconfig-model-itself-perl: FTBFS in testing (failing tests)

2016-09-13 Thread Debian Bug Tracking System 
Processing commands for cont...@bugs.debian.org:

> retitle 837613 libconfig-model-itself-perl: FTBFS in testing (failing tests)
Bug #837613 {Done: gregor herrmann } 
[src:libconfig-model-itself-perl] libconfig-model-itself-perl: FTBFS in sid 
(failing tests)
Changed Bug title to 'libconfig-model-itself-perl: FTBFS in testing (failing 
tests)' from 'libconfig-model-itself-perl: FTBFS in sid (failing tests)'.
> reassign 837613 libconfig-model-perl
Bug #837613 {Done: gregor herrmann } 
[src:libconfig-model-itself-perl] libconfig-model-itself-perl: FTBFS in testing 
(failing tests)
Bug reassigned from package 'src:libconfig-model-itself-perl' to 
'libconfig-model-perl'.
No longer marked as found in versions libconfig-model-itself-perl/2.005-1.
Ignoring request to alter fixed versions of bug #837613 to the same values 
previously set
> forcemerge 837133 837613
Bug #837133 {Done: Dominique Dumont } [libconfig-model-perl] 
Dump of value containing hash is broken
Bug #837613 {Done: gregor herrmann } [libconfig-model-perl] 
libconfig-model-itself-perl: FTBFS in testing (failing tests)
Added indication that 837613 affects src:libconfig-model-itself-perl
Marked as fixed in versions libconfig-model-perl/2.090-1.
Marked as found in versions libconfig-model-perl/2.089-1.
Merged 837133 837613
> thanks
Stopping processing here.

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

Bug#837613: libconfig-model-itself-perl: FTBFS in testing (failing tests)

2016-09-13 Thread Santiago Vila 
retitle 837613 libconfig-model-itself-perl: FTBFS in testing (failing tests)
reassign 837613 libconfig-model-perl
forcemerge 837133 837613
thanks

(Both bugs are equally closed, so don't worry).

Explanation:

I have compared the build logs for stretch and sid, and this error:

 Syntax error: spurious char at command end: '=#'. Did you forget double quotes 
?

which is the error claimed to be fixed in libconfig-model-perl,
does effectively not appear anymore in the sid build log.

Therefore, this bug, #837613, is the same as #837133.

Therefore, I'm doing the reassign and merge that you can see above.

The fact that libconfig-model-itself-perl still FTBFS in sid has
probably a reason different than the one recently fixed in
libconfig-model-perl so I'm going to report it separately to avoid
confusion (even if I already posted the build log here).

I'm also keeping the subject of this bug as it was originally, i.e.
FTBFS in testing with the build log I originally attached, so that it
matches exactly the problem diagnosed (and supposedly fixed) in #837133.

Thanks.

Bug#837059: NMU of abyss for FTBFS

2016-09-13 Thread Andreas Tille 
Hi Alastair,

thanks for the NMU.

On Tue, Sep 13, 2016 at 01:43:36PM +0100, Alastair McKinstry wrote:
> I have NMU's abyss 1.9.0 to DELAYED/5, to fix the FTBFS that is blocking
> openmpi2.

Just for the sake of interest: In how far is abyss blocking openmpi2?
 
> The debdiff is attached for your review,

Could you do us a favour and commit the changes to

   git://anonscm.debian.org/debian-med/abyss.git

The repository has ACLs set and any DD can commit.

BTW, just from looking at the patch I can not see in how far this should
fix the issue.  Are you sure that the patch is complete?

Kind regards

  Andreas.

-- 
http://fam-tille.de

Bug#837268: bzr: FTBFS: Tests failures

2016-09-13 Thread Santiago Vila 
On Tue, Sep 13, 2016 at 02:33:29PM +0200, Lucas Nussbaum wrote:

> This is a case where there's no easy way to track affected releases. But
> in doubt, it's better to err on the side of considering a release
> affected.

Yes, I fully agree, especially in this case where the build is made in
unstable and packages are usually expected to propagate to testing
(so it would be just a matter of time that it happens in testing too).

Thanks.

Bug#829085: --link-doc Was: [Pkg-freeipmi-devel] Bug#829085: freeipmi: not binNMU safe

2016-09-13 Thread Yaroslav Halchenko 
Thank you Vincent for attending to freeipmi package!

Here is my exploration of the issue: I was a bit bedazzled since original setup
just closely followed established practice, e.g. see
https://wiki.debian.org/binNMU according to which +b1 suffix should be stripped
when establishing value of the ${source:Version} variable, thus rendering
package perfectly binNMUable  (theoretically ;) )

So it is indeed --link-doc which causes the trouble:

if (package_arch($package) ne package_arch($dh{LINK_DOC})) {
if (compat(9)) {
warning("WARNING: --link-doc between architecture all and not 
all packages breaks binNMUs");
} else {
error("--link-doc not allowed between ${package} and 
$dh{LINK_DOC} (one is arch:all and the other not)");
}
}
# Make sure that the parent directory exists.
if (! -d "$tmp/usr/share/doc" && ! -l "$tmp/usr/share/doc") {
install_dir("$tmp/usr/share/doc");
}
# Create symlink to another documentation directory if
# necessary.
if (! -d "$tmp/usr/share/doc/$package" &&
! -l "$tmp/usr/share/doc/$package") {
doit("ln", "-sf", $dh{LINK_DOC}, "$tmp/usr/share/doc/$package");
# Policy says that if you make your documentation
# directory a symlink, then you have to depend on
# the target.
addsubstvar($package, 'misc:Depends', "$dh{LINK_DOC} (= 
\${binary:Version})");
}


and there is an issue https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=811491  
to which I am following up here as well (CCed that bug report + involved 
parties):

On Wed, 20 Jan 2016 07:18:59 + Niels Thykier  wrote:

> > arch:all to arch:any - generates >= source:Version depends to binNMUability 
> > is 
> > preserved

> Personally I do /not/ consider this case policy compliant, nor do I
> believe it /can/ be (with the correct wording of the policy).  In this
> case, you can (in theory) end up with a case (using partial upgrades)
> where the copyright file of the arch:any does not match that of the
> arch:all.
>   But since the arch:all link-docs, then we now provide incorrect
> copyright information about the arch:all package.

Why not just as binNMU instructions say and have

addsubstvar($package, 'misc:Depends', "$dh{LINK_DOC} (= \${source:Version})");

(instead of proposed >= relationship)?  i.e. just replacing
binary:Version  with source:Version which would strip off +bX suffix (if I got
its purpose correct).  Since critical files such as copyright and
changelog.Debian are not binary specific, and theoretically none of the
documentations is binary specific (as claimed by any -> all dependency), I do
not see any problem with such as resolution...

Thank you in advance for your consideration

> Even if you were to add an upper bound, I can still (theoretically)
> create new (non-binNMU) versions that satisfies the relations.

FWIW theory is a powerful thing, but empirical science is plowing is way
through these days ;):

$> dpkg --compare-versions 2.4-1 lt 2.4-1+b1 && echo yes || echo no 
yes
$> dpkg --compare-versions 2.4-1+b1 lt 2.4-1.0~ && echo yes || echo no 
yes
$> dpkg --compare-versions 2.4-1+1 lt 2.4-1.0~ && echo yes || echo no 
yes
$> dpkg --compare-versions 2.4-1.1 lt 2.4-1.0~ && echo yes || echo no 
no

so I don't see so far how in common use-cases non-binNMU pkg could break
through the ceiling with .0~ suffix

so, theoretically, IMHO --link-docs should follow the binNMU recommendations
and have provided the differential handling for the obscure case that docs are
coming from arch: any pkg while package with a symlink is of arch all.  And ATM
it doesn't, and does break binNMUs.  Fixes at the level of individual
packages (such as was kindly done for freeipmi) are just inappropriate.

My perl foo is non-existent but if you like I could take a shot at improving
the patch slightly if you see my recommendation (which is just to follow
binNMU recommendations) to be the way to go.

> > arch:any to arch:all (no idea if this actually happens or not):

> > For compat 9 or less: Prints warning and does generates nothing
> > For compat 10: errors out the build

> This case can be done correctly by using (= ${source:Version}).  I was
> hoping this was more common than the previous case.

oops -- I guess I took also the wrong way of meaning of "to" all around.
So we seems to be on the same page ;)

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

Bug#837059: NMU of abyss for FTBFS

2016-09-13 Thread Alastair McKinstry 
Hi,

I have NMU's abyss 1.9.0 to DELAYED/5, to fix the FTBFS that is blocking
openmpi2.

The debdiff is attached for your review,


Best regards

Alastair McKinstry


-- 
Alastair McKinstry, , , 
https://diaspora.sceal.ie/u/amckinstry
Misentropy: doubting that the Universe is becoming more disordered. 

diff -Nru abyss-1.9.0/debian/changelog abyss-1.9.0/debian/changelog
--- abyss-1.9.0/debian/changelog2016-09-13 09:03:05.0 +0100
+++ abyss-1.9.0/debian/changelog2015-07-16 10:28:54.0 +0100
@@ -1,10 +1,3 @@
-abyss (1.9.0-1.1) unstable; urgency=medium
-
-  * Non-maintainer upload.
-  * Fix for FTBFS in g++6 : tuple now in std::tuple. Closes: #837059
-
- -- Alastair McKinstry   Tue, 13 Sep 2016 09:03:05 +0100
-
 abyss (1.9.0-1) unstable; urgency=medium
 
   * New upstream version
diff -Nru abyss-1.9.0/debian/patches/tr_tuple.patch 
abyss-1.9.0/debian/patches/tr_tuple.patch
--- abyss-1.9.0/debian/patches/tr_tuple.patch   2016-09-13 09:03:05.0 
+0100
+++ abyss-1.9.0/debian/patches/tr_tuple.patch   2015-07-16 10:28:54.0 
+0100
@@ -1,8 +1,29 @@
-Description: Fix FTBFS on new g++ (6.2). Closes: #837059.
+Description: 
+ TODO: Put a short summary on the line above and replace this paragraph
+ with a longer explanation of this change. Complete the meta-information
+ with other relevant fields (see below for details). To make it easier, the
+ information below has been extracted from the changelog. Adjust it or drop
+ it.
+ .
+ abyss (1.9.0-1.1) unstable; urgency=medium
+ .
+   * Non-maintainer upload.
+   * Fix FTBFS on new g++ (6.2). Closes: #837059.
 Author: Alastair McKinstry 
 Bug-Debian: https://bugs.debian.org/837059
-Last-Updated: 2016-09-13
-Forwarded: no
+
+---
+The information above should follow the Patch Tagging Guidelines, please
+checkout http://dep.debian.net/deps/dep3/ to learn about the format. Here
+are templates for supplementary fields that you might want to add:
+
+Origin: , 
+Bug: 
+Bug-Debian: https://bugs.debian.org/
+Bug-Ubuntu: https://launchpad.net/bugs/
+Forwarded: 
+Reviewed-By: 
+Last-Update: 2016-09-13
 
 --- abyss-1.9.0.orig/lib/gtest-1.7.0/include/gtest/gtest-printers.h
 +++ abyss-1.9.0/lib/gtest-1.7.0/include/gtest/gtest-printers.h


signature.asc
Description: OpenPGP digital signature

Bug#837268: bzr: FTBFS: Tests failures

2016-09-13 Thread Lucas Nussbaum 
On 11/09/16 at 22:28 +0200, Santiago Vila wrote:
> On Sun, Sep 11, 2016 at 09:53:34PM +0200, Lucas Nussbaum wrote:
> > Hi,
> > 
> > On 11/09/16 at 12:33 +0200, Santiago Vila wrote:
> > > > Tags: stretch sid
> > > 
> > > This bug should not happen in stretch (yet) because diffutils 3.5
> > > has not entered stretch (yet), are you sure it's correct to tag
> > > it stretch in those cases?
> > 
> > What 'stretch sid' really means is "this doesn't affect stable". There's
> > no better way to express that.
> 
> Ah, ok.
> 
> > Even if the bug is tagged "stretch sid", normal BTS version-tracking is
> > still applied, so if the affected version isn't in stretch, it won't
> > be seen as affecting stretch.
> 
> That's precisely the little problem I wanted to point out:
> 
> The "affected" version (bzr 2.7.0+bzr6619-1) was both in stretch and sid,
> but the bug could not be reproduced in stretch because diffutils 3.5
> (the package triggering this bug) was not in stretch yet.
> 
> How would I ask the BTS if this was a bug in stretch?
> 
> Assuming for a while that diffutils 3.5 did not enter testing yet,
> would the BTS give the correct answer?

This is a case where there's no easy way to track affected releases. But
in doubt, it's better to err on the side of considering a release
affected.

Lucas

Bug#837614: The bugs are not reproducible in unstable

2016-09-13 Thread Samuel Thibault 
Sebastiaan Couwenberg, on Tue 13 Sep 2016 12:26:29 +0200, wrote:
> The bug are not reproducible in unstable where we build our packages, we
> don't build our packages in testing.

But users do build their package in testing.

That's one of the whole points of free software: being able to rebuild
the software. Saying the users "well, it did build fine at that point of
time in unstable" is useless for them: the release is Stretch, not the
state of unstable at some point of development in unstable.

Now, if we do know that what is in unstable will get into testing, and
then it'll become buildable in testing, it is fine. But saying "we build
our package in unstable" is not an argument.

Samuel

Bug#832285: marked as done (libopenmpi2: fails to upgrade from 'sid' - trying to overwrite /usr/lib/openmpi/lib/libompitrace.so.0.0.0)

2016-09-13 Thread Debian Bug Tracking System 
Your message dated Tue, 13 Sep 2016 12:38:09 +0100
with message-id <59b6d78d-e602-7b66-cad9-3d8cf0e46...@debian.org>
and subject line closing
has caused the Debian Bug report #832285,
regarding libopenmpi2: fails to upgrade from 'sid' - trying to overwrite 
/usr/lib/openmpi/lib/libompitrace.so.0.0.0
to be marked as done.

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

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


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

Hi,

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

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

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

  Selecting previously unselected package libopenmpi2.
  Preparing to unpack .../libopenmpi2_2.0.0-1_amd64.deb ...
  Unpacking libopenmpi2 (2.0.0-1) ...
  dpkg: error processing archive 
/var/cache/apt/archives/libopenmpi2_2.0.0-1_amd64.deb (--unpack):
   trying to overwrite '/usr/lib/openmpi/lib/libompitrace.so.0.0.0', which is 
also in package libopenmpi1.10 1.10.3-3
  Processing triggers for libc-bin (2.23-2) ...
  dpkg-deb: error: subprocess paste was killed by signal (Broken pipe)
  Errors were encountered while processing:
   /var/cache/apt/archives/libopenmpi2_2.0.0-1_amd64.deb


cheers,

Andreas


libopenmpi1.10=1.10.3-3_libopenmpi2=2.0.0-1.log.gz
Description: application/gzip
--- End Message ---
--- Begin Message ---
close 832285

thanks


This bug was fixed in the 2.0.1-5 upload.


Best regards

Alastair



-- 
Alastair McKinstry, , , 
https://diaspora.sceal.ie/u/amckinstry
Misentropy: doubting that the Universe is becoming more disordered. 




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

Bug#837648: marked as done (ripe-atlas-tools: uninstallable in sid: Depends: python-ripe-atlas-sagan (< 1.1.11~) but 1.1.11-1 is to be installed)

2016-09-13 Thread Debian Bug Tracking System 
Your message dated Tue, 13 Sep 2016 11:06:19 +
with message-id 
and subject line Bug#837648: fixed in ripe-atlas-tools 2.0.1-2
has caused the Debian Bug report #837648,
regarding ripe-atlas-tools: uninstallable in sid: Depends: 
python-ripe-atlas-sagan (< 1.1.11~) but 1.1.11-1 is to be installed
to be marked as done.

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

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


-- 
837648: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=837648
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: ripe-atlas-tools
Version: 2.0.1-1
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

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

  The following packages have unmet dependencies:
   ripe-atlas-tools : Depends: python-ripe-atlas-sagan (< 1.1.11~) but 1.1.11-1 
is to be installed


Cheers,

Andreas
--- End Message ---
--- Begin Message ---
Source: ripe-atlas-tools
Source-Version: 2.0.1-2

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

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

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

Debian distribution maintenance software
pp.
Apollon Oikonomopoulos  (supplier of updated 
ripe-atlas-tools package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Tue, 13 Sep 2016 13:53:26 +0300
Source: ripe-atlas-tools
Binary: ripe-atlas-tools ripe-atlas-tools-doc
Architecture: source all
Version: 2.0.1-2
Distribution: unstable
Urgency: medium
Maintainer: Apollon Oikonomopoulos 
Changed-By: Apollon Oikonomopoulos 
Description:
 ripe-atlas-tools - command-line interface for RIPE Atlas
 ripe-atlas-tools-doc - command-line interface for RIPE Atlas (documentation)
Closes: 837648
Changes:
 ripe-atlas-tools (2.0.1-2) unstable; urgency=medium
 .
   * Relax cousteau and sagan version restrictions (Closes: #837648)
Checksums-Sha1:
 5a694fd1fb74a5364db2430e314e5047adc960a1 2294 ripe-atlas-tools_2.0.1-2.dsc
 8ea55c68acb858e2a060a3ce5e1cc35fb97f0a49 3680 
ripe-atlas-tools_2.0.1-2.debian.tar.xz
 c12c25566e24373dc43325d31e82bd06661147b3 46194 
ripe-atlas-tools-doc_2.0.1-2_all.deb
 79478c2693147afa330d4877cca702935b8d4734 42690 ripe-atlas-tools_2.0.1-2_all.deb
Checksums-Sha256:
 f1c760bfc4cf575bd4434a360287eddd7df2359f42a12877b1d2d99f3c785d88 2294 
ripe-atlas-tools_2.0.1-2.dsc
 1637d6362e23e0ae40b64b9ccef10bae4cf6d199f92c26a737f34a9e1f0b910a 3680 
ripe-atlas-tools_2.0.1-2.debian.tar.xz
 aceaa29eb95c73adcd50e670f982b1552bb7c8989aa23043dfce53535cdf6b06 46194 
ripe-atlas-tools-doc_2.0.1-2_all.deb
 c434889347014d37bb980d74b000a4e29cf7698ef8f3e3519493ee9b1ca2c872 42690 
ripe-atlas-tools_2.0.1-2_all.deb
Files:
 c522bf63616ee450d924664e3f5c750d 2294 net optional ripe-atlas-tools_2.0.1-2.dsc
 1ac16a2ea0d79aa71607805a65ede558 3680 net optional 
ripe-atlas-tools_2.0.1-2.debian.tar.xz
 1fa139998a01dbdae3afdfaf4e3e867b 46194 doc optional 
ripe-atlas-tools-doc_2.0.1-2_all.deb
 003733e5942b5b2b10d749d65864082a 42690 net optional 
ripe-atlas-tools_2.0.1-2_all.deb

-BEGIN PGP SIGNATURE-
Version: GnuPG v1

iQIcBAEBCAAGBQJX19sHAAoJENutyevup8YO9hUP/14SzLinCaaeaq9/kMoCb9ys
9CvSssVWw6XbySGBteL9yMr+OEgPB8+ZeFN/KFhwoNlmQrauOgigwjYW7J9nCGkc
KAIRJU3hH7OI8UlzNDLyIJ3efToJ4JqKB39QRMw7Dm6xJrmxGA03BFuZ7UjXJbLE
asiqG4sGOF2dD8dAu2Qqt8vQmLUjeIH9o0LBveSqcroZNqcVJldHSXwAJXIRfL4n
NXVBfWTJ5xhBwF7m/sJvnRW7u8Gn2uJzYB7waHsKvrUC642ug5chfK3YQuhXopDj
RPaFaPMebD445NxTvXLroDQxyUbZT7rAoAowoVYqN6ljKQqO5wz6kzpCdjKr3bL1
T3DZotbM1kynGs99fU8NNotRsfCJLoG2LmNZX7pFbhU/RihjsKR43Pa2jrRmAt9f
ACrHqoNPP4GhiZ554DN5WY3EYS5JiCP//uFzX9f59716EI+WOenvUFvqv8jAh8XV
TX/HH2hz52yfDywYeZL9Vc3yBAIIUn5gH6aQjWwVkTFaiOeaU+A2GezQ+05JkTQv
Y/7hgaQamQQPjIP9mi8dWu8jLL+QcZvKesvUlHltWvAtuw33hJafwpY+0CZiely9
oECghPUOfgQGtxcWsxG2tNb2DlMv4/ZLX6DhzZFTEf00UN0gOEgcwpKdAZSCbcov
dJaqlMu5q5VL+N7hiXBl
=8ho3
-END PGP SIGNATURE End Message ---

Bug#834753: marked as done (android-platform-tools-base: FTBFS with only 1 CPU (Cannot set maxParallelForks to a value less than 1))

2016-09-13 Thread Debian Bug Tracking System 
Your message dated Tue, 13 Sep 2016 11:00:10 +
with message-id 
and subject line Bug#834753: fixed in android-platform-tools-base 2.0.0-1
has caused the Debian Bug report #834753,
regarding android-platform-tools-base: FTBFS with only 1 CPU (Cannot set 
maxParallelForks to a value less than 1)
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.)


-- 
834753: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=834753
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:android-platform-tools-base
Version: 1.5.0-4
Severity: serious

Dear maintainer:

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


[...]
 debian/rules build-indep
dh build-indep --parallel --with maven_repo_helper --buildsystem=gradle
   dh_testdir -i -O--parallel -O--buildsystem=gradle
   dh_update_autotools_config -i -O--parallel -O--buildsystem=gradle
   dh_auto_configure -i -O--parallel -O--buildsystem=gradle
   debian/rules override_dh_auto_build
make[1]: Entering directory '/<>'
dh_auto_build -- -x test assemble
mkdir -p .gradle/init.d
cp /usr/share/gradle-debian-helper/init.gradle .gradle/init.d/
gradle --info --console plain --offline --stacktrace --no-daemon 
--refresh-dependencies --gradle-user-home .gradle -x test assemble
To honour the JVM settings for this build a new JVM will be forked. Please 
consider using the daemon: 
https://docs.gradle.org/2.13/userguide/gradle_daemon.html.
Starting daemon process: workingDir = /<>/.gradle/daemon/2.13, 
daemonArgs: [/usr/lib/jvm/java-8-openjdk-amd64/bin/java, -XX:MaxPermSize=1024m, 
-Xmx4096m, -Dfile.encoding=US-ASCII, -Duser.country=US, -Duser.language=en, 
-Duser.variant, -cp, /usr/share/gradle/lib/gradle-launcher-2.13.jar, 
org.gradle.launcher.daemon.bootstrap.GradleDaemon, 2.13]

[... snipped ...]

FAILURE: Build failed with an exception.

* Where:
Build file '/<>/base/build-system/builder/build.gradle' line: 32

* What went wrong:
A problem occurred evaluating project ':base:builder'.
> Cannot set maxParallelForks to a value less than 1.

[ ... ]

BUILD FAILED

Total time: 8.154 secs
Stopped 0 compiler daemon(s).
Received result Failure[value=org.gradle.initialization.ReportedException: 
org.gradle.internal.exceptions.LocationAwareException: Build file 
'/<>/base/build-system/builder/build.gradle' line: 32
A problem occurred evaluating project ':base:builder'.] from daemon 
DaemonInfo{pid=4267, address=[b4c8bf4a-dd0b-41ed-9eaf-43be30eca7ff port:34365, 
addresses:[/0:0:0:0:0:0:0:1%lo, /127.0.0.1]], idle=false, 
context=DefaultDaemonContext[uid=43fe90c6-6a20-40db-927d-01422accea8c,javaHome=/usr/lib/jvm/java-8-openjdk-amd64,daemonRegistryDir=/<>/.gradle/daemon,pid=4267,idleTimeout=12,daemonOpts=-XX:MaxPermSize=1024m,-Xmx4096m,-Dfile.encoding=US-ASCII,-Duser.country=US,-Duser.language=en,-Duser.variant]}
 (build should be done).
dh_auto_build: gradle --info --console plain --offline --stacktrace --no-daemon 
--refresh-dependencies --gradle-user-home .gradle -x test assemble returned 
exit code 1
debian/rules:9: recipe for target 'override_dh_auto_build' failed
make[1]: *** [override_dh_auto_build] Error 1
make[1]: Leaving directory '/<>'
debian/rules:6: recipe for target 'build-indep' failed
make: *** [build-indep] Error 2
dpkg-buildpackage: error: debian/rules build-indep gave error exit status 2


This failure seems related with the fact that my autobuilder has only
one CPU.

Packages are never supposed to require more than one CPU to build,
otherwise we would have, in addition to Build-Depends, a field
called maybe Build-CPUs.

But we don't have a field like that because every task that may be
performed in a finite amount of time with several CPUs may also be
performed with only one CPU (even if it's slower).

Thanks.
--- End Message ---
--- Begin Message ---
Source: android-platform-tools-base
Source-Version: 2.0.0-1

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

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

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

Debian

Bug#835536: marked as done (request-tracker4: FTBFS with gnupg 2.1)

2016-09-13 Thread Debian Bug Tracking System 
Your message dated Tue, 13 Sep 2016 11:00:18 +
with message-id 
and subject line Bug#835536: fixed in request-tracker4 4.2.13-2
has caused the Debian Bug report #835536,
regarding request-tracker4: FTBFS with gnupg 2.1
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.)


-- 
835536: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=835536
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: request-tracker4
Version: 4.2.12-6
Severity: serious
Justification: FTBFS

Now that libgnupg-interface-perl has been fixed to use gpg1 (
see #834281) request-tracker4 still FTBFS because it configures
GnuPG::Interface to use 'gpg' as the binary anyway. 

I intend to patch out this functionality so that request-tracker4
can work without hardcoding the path to gpg (which will avoid the
need to fiddle with this setting for backports).

Dominic.
--- End Message ---
--- Begin Message ---
Source: request-tracker4
Source-Version: 4.2.13-2

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

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

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

Debian distribution maintenance software
pp.
Dominic Hargreaves  (supplier of updated request-tracker4 
package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Format: 1.8
Date: Tue, 06 Sep 2016 13:26:01 +0100
Source: request-tracker4
Binary: request-tracker4 rt4-clients rt4-standalone rt4-fcgi rt4-apache2 
rt4-db-postgresql rt4-db-mysql rt4-db-sqlite rt4-doc-html
Architecture: all source
Version: 4.2.13-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Request Tracker Group 

Changed-By: Dominic Hargreaves 
Closes: 835536 836833
Description: 
 request-tracker4 - extensible trouble-ticket tracking system
 rt4-apache2 - Apache 2 specific files for request-tracker4
 rt4-clients - mail gateway and command-line interface to request-tracker4
 rt4-db-mysql - MySQL database backend for request-tracker4
 rt4-db-postgresql - PostgreSQL database backend for request-tracker4
 rt4-db-sqlite - SQLite database backend for request-tracker4
 rt4-doc-html - HTML documentation for request-tracker4
 rt4-fcgi   - External FastCGI support for request-tracker4
 rt4-standalone - Standalone web server support for request-tracker4
Changes:
 request-tracker4 (4.2.13-2) unstable; urgency=medium
 .
   * Correct typo in gpg1 patch description
   * Fix another use of gpg in the test suite (Closes: #835536)
   * Fix FTBFS with '.' removed from @INC (Closes: #836833)
Checksums-Sha1: 
 ce5eb5930e886fdc464e136dc287dd57d6b0bd4a 5637 request-tracker4_4.2.13-2.dsc
 7b1f02224e04fc5bc80388deffa18092761e7fb5 76600 
request-tracker4_4.2.13-2.debian.tar.xz
 33f4b69665c5159124e66fc9527c2edec1a1896a 3092058 
request-tracker4_4.2.13-2_all.deb
 7da4690748b03d200ba624136a46455f0da6 19222 rt4-apache2_4.2.13-2_all.deb
 b7ed9bc5afb604c9f50cdebd43a8d99dc942f111 53364 rt4-clients_4.2.13-2_all.deb
 a2fb168cff269e1fb46393601e0b2cdb281b0e6d 18508 rt4-db-mysql_4.2.13-2_all.deb
 c54249d9918d3b5ab2b7fae9dacdd518ecf22b0a 18500 
rt4-db-postgresql_4.2.13-2_all.deb
 76648ca3a45f15d4ad1640e19ab9b5f082a3cd29 18602 rt4-db-sqlite_4.2.13-2_all.deb
 eeb68ab6f22bf418156a703e6fca0c55cb2679e8 987068 rt4-doc-html_4.2.13-2_all.deb
 256c7b037d387e2d9d4e3255b69ddcdda161413a 20982 rt4-fcgi_4.2.13-2_all.deb
 079a74ada60d796c184a55a46ed9a23f7f734d56 17978 rt4-standalone_4.2.13-2_all.deb
Checksums-Sha256: 
 9e75300afba7c0673ca4cde4b205affc8b67f18c812b22740713c4a98af3024a 5637 
request-tracker4_4.2.13-2.dsc
 546e9708c31b29c936157e0620702ae958f181f28a0b8895d1ac09d4e9019dce 76600 
request-tracker4_4.2.13-2.debian.tar.xz
 4af15a0afebe150f277941ca8c050e312f05225517fa271adf5dd15343431879 3092058 
request-tracker4_4.2.13-2_all.deb
 bc3a3df3f930e703284bb85367efd31f6a52059620161fdac224941d291d8050 19222 
rt4-apache2_4.2.13-2_all.deb
 23fbaecf414dd67703b97d235b57b0325f6303259501c1c47b9fb827f9efa35e 53364 
rt4-clients_4.2.13-2_all.deb
 c5051268647858f7fea8ad6670d7805defafc9b171fd2a12d7446966b7e7c2be 18508

Bug#836833: marked as done (request-tracker4: FTBFS with '.' removed from @INC)

2016-09-13 Thread Debian Bug Tracking System 
Your message dated Tue, 13 Sep 2016 11:00:18 +
with message-id 
and subject line Bug#836833: fixed in request-tracker4 4.2.13-2
has caused the Debian Bug report #836833,
regarding request-tracker4: FTBFS with '.' removed from @INC
to be marked as done.

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

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


-- 
836833: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=836833
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: request-tracker4
Version: 4.2.13-1
Severity: serious
User: debian-p...@lists.debian.org
Usertags: perl-cwd-inc-removal
Tags: patch

As reported in #835536 this package FTBFS with no '.' in @INC.
Patch from Niko attached.
>From 9251965c2ee5f9e23a9b196aad97fe404343b386 Mon Sep 17 00:00:00 2001
From: Niko Tyni 
Date: Sun, 4 Sep 2016 11:41:29 +0300
Subject: [PATCH] Fix RT::I18N and the test suite to work without cwd in @INC

---
 lib/RT/I18N.pm | 5 +++--
 t/lifecycles/basics.t  | 2 +-
 t/lifecycles/dates.t   | 2 +-
 t/lifecycles/moving.t  | 2 +-
 t/lifecycles/types.t   | 2 +-
 t/lifecycles/unresolved-deps.t | 2 +-
 6 files changed, 8 insertions(+), 7 deletions(-)

diff --git a/lib/RT/I18N.pm b/lib/RT/I18N.pm
index 60a6622..1bf0b57 100644
--- a/lib/RT/I18N.pm
+++ b/lib/RT/I18N.pm
@@ -56,6 +56,7 @@ package RT::I18N;
 
 use strict;
 use warnings;
+use Cwd ();
 
 
 use Locale::Maketext 1.04;
@@ -97,10 +98,10 @@ sub Init {
 @lang = ('*') unless @lang;
 
 # load default functions
-require substr(__FILE__, 0, -3) . '/i_default.pm';
+require substr(Cwd::abs_path(__FILE__), 0, -3) . '/i_default.pm';
 
 # Load language-specific functions
-foreach my $file ( File::Glob::bsd_glob(substr(__FILE__, 0, -3) . "/*.pm") ) {
+foreach my $file ( File::Glob::bsd_glob(substr(Cwd::abs_path(__FILE__), 0, -3) . "/*.pm") ) {
 my ($lang) = ($file =~ /([^\\\/]+?)\.pm$/);
 next unless grep $_ eq '*' || $_ eq $lang, @lang;
 require $file;
diff --git a/t/lifecycles/basics.t b/t/lifecycles/basics.t
index e18bea3..85e77c7 100644
--- a/t/lifecycles/basics.t
+++ b/t/lifecycles/basics.t
@@ -1,7 +1,7 @@
 use strict;
 use warnings;
 
-BEGIN {require  't/lifecycles/utils.pl'};
+BEGIN {require  './t/lifecycles/utils.pl'};
 
 my $general = RT::Test->load_or_create_queue(
 Name => 'General',
diff --git a/t/lifecycles/dates.t b/t/lifecycles/dates.t
index 0c74a1b..a8dd8cf 100644
--- a/t/lifecycles/dates.t
+++ b/t/lifecycles/dates.t
@@ -1,7 +1,7 @@
 use strict;
 use warnings;
 
-BEGIN {require 't/lifecycles/utils.pl'};
+BEGIN {require './t/lifecycles/utils.pl'};
 
 my $general = RT::Test->load_or_create_queue(
 Name => 'General',
diff --git a/t/lifecycles/moving.t b/t/lifecycles/moving.t
index 8a03e3e..379b646 100644
--- a/t/lifecycles/moving.t
+++ b/t/lifecycles/moving.t
@@ -1,7 +1,7 @@
 use strict;
 use warnings;
 
-BEGIN {require 't/lifecycles/utils.pl'};
+BEGIN {require './t/lifecycles/utils.pl'};
 
 my $general = RT::Test->load_or_create_queue(
 Name => 'General',
diff --git a/t/lifecycles/types.t b/t/lifecycles/types.t
index 79b0714..84cfd86 100644
--- a/t/lifecycles/types.t
+++ b/t/lifecycles/types.t
@@ -1,7 +1,7 @@
 use strict;
 use warnings;
 
-BEGIN {require  't/lifecycles/utils.pl'};
+BEGIN {require  './t/lifecycles/utils.pl'};
 
 is_deeply( [ RT::Lifecycle->ListAll ], [qw/ approvals default delivery /],
"Get the list of all lifecycles (implicitly for for tickets)");
diff --git a/t/lifecycles/unresolved-deps.t b/t/lifecycles/unresolved-deps.t
index 5da4b8f..fe09d3b 100644
--- a/t/lifecycles/unresolved-deps.t
+++ b/t/lifecycles/unresolved-deps.t
@@ -1,7 +1,7 @@
 use strict;
 use warnings;
 
-BEGIN {require  't/lifecycles/utils.pl'};
+BEGIN {require  './t/lifecycles/utils.pl'};
 
 my $general = RT::Test->load_or_create_queue(
 Name => 'General',
-- 
2.9.3

--- End Message ---
--- Begin Message ---
Source: request-tracker4
Source-Version: 4.2.13-2

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

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

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

Debian distribution maintenance software
pp.
Dominic Hargreaves  (supplier of updated request-tracker4 
package)

(This message was generated automatically at their request; if

Bug#829085: marked as done (freeipmi: not binNMU safe)

2016-09-13 Thread Debian Bug Tracking System 
Your message dated Tue, 13 Sep 2016 10:53:59 +
with message-id 
and subject line Bug#829085: fixed in freeipmi 1.4.11-1.1
has caused the Debian Bug report #829085,
regarding freeipmi: not binNMU safe
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.)


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

Your package is not binNMU safe, as some arch:any packages depend on
arch:all (= ${binary:Version}).

See e.g. ppc64:

slurm-llnl build-depends on:
- ppc64:libipmimonitoring-dev
ppc64:libipmimonitoring-dev depends on missing:
- ppc64:freeipmi-common (= 1.4.11-1+b1)

This is probably caused by --link-doc=freeipmi-common

Cheers,
Emilio
--- End Message ---
--- Begin Message ---
Source: freeipmi
Source-Version: 1.4.11-1.1

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

Debian distribution maintenance software
pp.
Vincent Danjean  (supplier of updated freeipmi 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, 05 Sep 2016 09:55:48 +0200
Source: freeipmi
Binary: freeipmi-common freeipmi-tools freeipmi-bmc-watchdog 
freeipmi-ipmidetect freeipmi-ipmiseld libfreeipmi16 libfreeipmi-dev 
libipmidetect0 libipmidetect-dev libipmimonitoring5a libipmimonitoring-dev 
libipmiconsole2 libipmiconsole-dev freeipmi
Architecture: amd64 source
Version: 1.4.11-1.1
Distribution: unstable
Urgency: medium
Maintainer: Debian FreeIPMI Maintainers 

Changed-By: Vincent Danjean 
Closes: 829085
Description: 
 freeipmi-bmc-watchdog - GNU implementation of the IPMI protocol - BMC watchdog
 freeipmi-common - GNU implementation of the IPMI protocol - common files
 freeipmi   - GNU implementation of the IPMI protocol
 freeipmi-ipmidetect - GNU IPMI - IPMI node detection tool
 freeipmi-ipmiseld - GNU IPMI - IPMI node detection tool
 freeipmi-tools - GNU implementation of the IPMI protocol - tools
 libfreeipmi16 - GNU IPMI - libraries
 libfreeipmi-dev - GNU IPMI - development package
 libipmiconsole2 - GNU IPMI - Serial-over-Lan library
 libipmiconsole-dev - GNU IPMI - ipmiconsole development package
 libipmidetect0 - GNU IPMI - IPMI node detection library
 libipmidetect-dev - GNU IPMI - ipmidetect development package
 libipmimonitoring5a - GNU IPMI - Sensor monitoring library
 libipmimonitoring-dev - GNU IPMI - ipmimonitoring development package
Changes:
 freeipmi (1.4.11-1.1) unstable; urgency=medium
 .
   * Non-maintainer upload.
   * Fix "not binNMU safe" (Closes: #829085) by making freeipmi-common
 arch:any instead of arch:all. A better fix can be found later if required.
Checksums-Sha1: 
 2e4164aad1b1020735acf81bc28c9278b98a4f0a 2833 freeipmi_1.4.11-1.1.dsc
 ee2b6e2110427c4949298b706cdd902f4d52697c 3203918 freeipmi_1.4.11.orig.tar.gz
 b0fdb232b4f8b32f2cd215344d01c69a2641a0fb 23328 
freeipmi_1.4.11-1.1.debian.tar.xz
 76edd95acf2c7a2793f3f49d719a0c919843ac19 110412 
freeipmi-bmc-watchdog-dbgsym_1.4.11-1.1_amd64.deb
 173cb1c7049d6d07f0aa7e1a581f8d4cf356436d 44594 
freeipmi-bmc-watchdog_1.4.11-1.1_amd64.deb
 b96b785f3aed001da3cd787ad6c43df36ee17c9e 340388 
freeipmi-common_1.4.11-1.1_amd64.deb
 b9de32480220749e3d79656e190b32176888fc39 124134 
freeipmi-ipmidetect-dbgsym_1.4.11-1.1_amd64.deb
 ef0c9a91335401b56f6e017235483c0624bc379a 37644 
freeipmi-ipmidetect_1.4.11-1.1_amd64.deb
 3f0a036d78957dcb19530d0f3ab63e5c00bdd50f 233188 
freeipmi-ipmiseld-dbgsym_1.4.11-1.1_amd64.deb
 a743347dc81c4fa4fe046b4c560f89b6f0db0aef 78500 
freeipmi-ipmiseld_1.4.11-1.1_amd64.deb
 a38d0c6c9c39cd006228a2c0d0acd3a001a8b1e9 3258826 
freeipmi-tools-dbgsym_1.4.11-1.1_amd64.deb
 10599242c2f5ef2951ab00b5015596aef309506c 598672 
freeipmi-tools_1.4.11-1.1_amd64.deb
 538400b4a22a2a1a4ecb0325467daca6878a347f 1158 freeipmi_1.4.11-1.1_amd64.deb
 f769cbf342dcd28a1a8435e99669111bda420ab5 924670 
libfreeipmi-dev_1.4.11-1.1_amd64.deb

Bug#834683: [pkg-gnupg-maint] Bug#834683: fixed in mini-buildd 1.0.17

2016-09-13 Thread Stephan Sürken 
Rehi,

On Mo, 2016-09-12 at 21:34 +0100, Santiago Vila wrote:
> On Mon, Sep 12, 2016 at 07:34:09PM +0200, Daniel Kahn Gillmor wrote:
> 
> > 
> > An even easier approach might be to do the following within the
> > build:
> > 
> >   * ln -sf /dev/urandom /dev/random
> > 
> > why would we need the blocking kernel RNG in the buildd anyway?
> Either that, or maybe a build-depends on a package specifically
> created to do that (as I'm not sure we could really ask all buildd
> operators to make the symlink permanently).
> 
> A good solution should be automatic and not need manual intervention,
> and should be independent of the machine on which the build is done.

Exactly ;).

> > Lastly, one other option for gnupg at least is to patch upstream to
> > use
> > --debug-quick-random in the build-time test.
> > 
> > do any of these options sound more appealing than the others?
> I didn't know about --debug-quick-random, it seems perfect to me.
> 
> Stephan, do you think it would be possible to patch mini-buildd so
> that --debug-quick-random is added to gnupg command line, but only
> when the package is doing the tests following the build?

Yeah, I will check this out (though it's not an option to gpg directly,
afair). Or maybe going with a pre-generated key.

Thx,

S

Processed: reassign 814762 to kdepim-addons, fixed 814762 in 16.04.3-1, affects 814762 ..., usertagging 837488 ...

2016-09-13 Thread Debian Bug Tracking System 
Processing commands for cont...@bugs.debian.org:

> reassign 814762 kdepim-addons
Bug #814762 {Done: Maximiliano Curia } [kmail] kmail: CSS from 
HTML mail interfers with header layout
Bug reassigned from package 'kmail' to 'kdepim-addons'.
No longer marked as found in versions kdepim/4:4.14.10-2 and kdepim/4:16.04.3-1.
No longer marked as fixed in versions kdepim-addons/16.04.3-1.
> fixed 814762 16.04.3-1
Bug #814762 {Done: Maximiliano Curia } [kdepim-addons] kmail: 
CSS from HTML mail interfers with header layout
Marked as fixed in versions kdepim-addons/16.04.3-1.
> affects 814762 + kmail
Bug #814762 {Done: Maximiliano Curia } [kdepim-addons] kmail: 
CSS from HTML mail interfers with header layout
Added indication that 814762 affects kmail
> severity 837488 serious
Bug #837488 [python3-pyopencl] python3-pyopencl: Broken install
Severity set to 'serious' from 'normal'
> user debian...@lists.debian.org
Setting user to debian...@lists.debian.org (was a...@debian.org).
> usertags 837488 piuparts
There were no usertags set.
Usertags are now: piuparts.
> usertags 837594 piuparts
There were no usertags set.
Usertags are now: piuparts.
> thanks
Stopping processing here.

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

Bug#837648: ripe-atlas-tools: uninstallable in sid: Depends: python-ripe-atlas-sagan (< 1.1.11~) but 1.1.11-1 is to be installed

2016-09-13 Thread Andreas Beckmann 
Package: ripe-atlas-tools
Version: 2.0.1-1
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

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

  The following packages have unmet dependencies:
   ripe-atlas-tools : Depends: python-ripe-atlas-sagan (< 1.1.11~) but 1.1.11-1 
is to be installed


Cheers,

Andreas

Bug#830440: marked as done (mpi4py: FTBFS: ld: cannot find -llmpe)

2016-09-13 Thread Debian Bug Tracking System 
Your message dated Tue, 13 Sep 2016 12:43:00 +0200
with message-id <1da52976-37c6-929c-716d-97e8a3aab...@xs4all.nl>
and subject line Re: mpi4py: FTBFS: ld: cannot find -llmpe (not actual cause 
for build failures, test target is)
has caused the Debian Bug report #830440,
regarding mpi4py: FTBFS: ld: cannot find -llmpe
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.)


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

Hi,

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

Relevant part (hopefully):
> DC-Build-Header: mpi4py 2.0.0-1 / 2016-07-06 21:09:38 +
> DC-Task: source:mpi4py version:2.0.0-1 architecture:any chroot:unstable 
> esttime:193 logfile:/tmp/mpi4py_2.0.0-1_unstable_reb2.log modes:
> DC-Sbuild-call: su user -c 'sbuild -n -A -s --force-orig-source --apt-update 
> -d unstable -v  mpi4py_2.0.0-1'
> sbuild (Debian sbuild) 0.65.2 (24 Mar 2015) on 
> ip-172-31-7-151.eu-central-1.compute.internal
> 
> ╔══╗
> ║ mpi4py 2.0.0-1 (amd64) 06 Jul 2016 
> 21:09 ║
> ╚══╝
> 
> Package: mpi4py
> Version: 2.0.0-1
> Source Version: 2.0.0-1
> Distribution: unstable
> Machine Architecture: amd64
> Host Architecture: amd64
> Build Architecture: amd64
> 
> I: NOTICE: Log filtering will replace 'build/mpi4py-eD6Q9d/mpi4py-2.0.0' with 
> '«PKGBUILDDIR»'
> I: NOTICE: Log filtering will replace 'build/mpi4py-eD6Q9d' with '«BUILDDIR»'
> I: NOTICE: Log filtering will replace 
> 'var/lib/schroot/mount/unstable-amd64-sbuild-a6bac500-57e5-408f-8ebf-ae6ef4eb7f86'
>  with '«CHROOT»'
> 
> ┌──┐
> │ Update chroot   
>  │
> └──┘
> 
> Get:1 http://127.0.0.1:/debian unstable InRelease [209 kB]
> Get:2 http://127.0.0.1:/debian unstable/main Sources.diff/Index [27.9 kB]
> Get:3 http://127.0.0.1:/debian unstable/main amd64 Packages.diff/Index 
> [27.9 kB]
> Get:4 http://127.0.0.1:/debian unstable/main Translation-en.diff/Index 
> [27.9 kB]
> Get:5 http://127.0.0.1:/debian unstable/main Sources 
> 2016-07-06-1505.17.pdiff [7201 B]
> Get:6 http://127.0.0.1:/debian unstable/main amd64 Packages 
> 2016-07-06-1505.17.pdiff [9176 B]
> Get:5 http://127.0.0.1:/debian unstable/main Sources 
> 2016-07-06-1505.17.pdiff [7201 B]
> Get:6 http://127.0.0.1:/debian unstable/main amd64 Packages 
> 2016-07-06-1505.17.pdiff [9176 B]
> Get:7 http://127.0.0.1:/debian unstable/main Translation-en 
> 2016-07-06-1505.17.pdiff [866 B]
> Get:7 http://127.0.0.1:/debian unstable/main Translation-en 
> 2016-07-06-1505.17.pdiff [866 B]
> Fetched 310 kB in 1s (271 kB/s)
> Reading package lists...
> W: No sandbox user '_apt' on the system, can not drop privileges
> Reading package lists...
> Building dependency tree...
> Reading state information...
> Calculating upgrade...
> The following packages will be upgraded:
>   dash linux-libc-dev
> 2 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
> Need to get 1252 kB of archives.
> After this operation, 2048 B of additional disk space will be used.
> Get:1 http://127.0.0.1:/debian unstable/main amd64 dash amd64 0.5.8-2.3 
> [108 kB]
> Get:2 http://127.0.0.1:/debian unstable/main amd64 linux-libc-dev amd64 
> 4.6.3-1 [1144 kB]
> debconf: delaying package configuration, since apt-utils is not installed
> Fetched 1252 kB in 0s (28.2 MB/s)
> (Reading database ... 
(Reading database ... 5%
(Reading database ... 10%
(Reading database ... 15%
(Reading database ... 20%
(Reading database ... 25%
(Reading database ... 30%
(Reading database ... 35%
(Reading database ... 40%
(Reading database ... 45%
(Reading database ... 50%
(Reading database ... 55%
(Reading database ... 60%
(Reading database ... 65%
(Reading database ... 70%
(Reading database ... 75%
(Reading database ... 80%
(Reading database ... 85%
(Reading database ... 90%
(Reading database ... 95%
(Reading database ... 100%
(Reading database ... 11521 files and directories currently installed.)
> Preparing to unpack .../dash_0.5.8-2.3_amd64.deb

Processed: Re: mpi4py: FTBFS: ld: cannot find -llmpe (not actual cause for build failures, test target is)

2016-09-13 Thread Debian Bug Tracking System 
Processing commands for cont...@bugs.debian.org:

> fixed 830440 mpi4py/2.0.0-2
Bug #830440 [src:mpi4py] mpi4py: FTBFS: ld: cannot find -llmpe
Marked as fixed in versions mpi4py/2.0.0-2.
> thanks
Stopping processing here.

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

Bug#834683: [pkg-gnupg-maint] Bug#834683: fixed in mini-buildd 1.0.17

2016-09-13 Thread Stephan Sürken 
Hi Daniel, Santiago,

thx for the answer; I am not 100% satisfied, though ;).

For me, it actually boils down to what notion we have:

(1) The builder hosts must provide reasonable entropy.
(2) Software testsuites generally must work fine even with low entropy.

In the past, I tended to go with (1) (which is one of the reasons mini-
buildd recommends haveged).

So I guess just going for both for now ;), so I will check how I can
improve that specific doctest in mini-buildd.

I am still sort of wondering how other testsuites behave in this
respect (like gnupg, gcrypt)?

Thx!

S
                 

Processed: The bugs are not reproducible in unstable

2016-09-13 Thread Debian Bug Tracking System 
Processing commands for cont...@bugs.debian.org:

> tags 837614 unreproducible
Bug #837614 {Done: Sebastiaan Couwenberg } 
[src:python-geopandas] python-geopandas: FTBFS in testing (failing tests)
Added tag(s) unreproducible.
> tags 837622 unreproducible
Bug #837622 {Done: Sebastiaan Couwenberg } 
[src:python-stetl] python-stetl: FTBFS in testing (failing tests)
Added tag(s) unreproducible.
> thanks
Stopping processing here.

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

Processed: Re: Bug#831093: fixed in libterralib 4.3.0+dfsg.2-9

2016-09-13 Thread Debian Bug Tracking System 
Processing control commands:

> reopen -1
Bug #831093 {Done: Alastair McKinstry } [src:qterm] 
qterm: FTBFS with GCC 6: uaocodec.cpp:15598:1: error: narrowing conversion of 
''\3777600'' from 'char' to 'uchar {aka unsigned char}' inside { } 
[-Wnarrowing]
'reopen' may be inappropriate when a bug has been closed with a version;
all fixed versions will be cleared, and you may need to re-add them.
Bug reopened
No longer marked as fixed in versions libterralib/4.3.0+dfsg.2-9.

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

Bug#831093: fixed in libterralib 4.3.0+dfsg.2-9

2016-09-13 Thread Andreas Beckmann 
Control: reopen -1

On Tue, 02 Aug 2016 10:50:19 + Alastair McKinstry
 wrote:
>  libterralib (4.3.0+dfsg.2-9) unstable; urgency=medium
>  .
>* Patch from Set C locale when archiving object files to get a 
> deterministic order.
>  Thanks to Eduard Sanou. Closes: #831093.

wrong bug, this is about a GCC 6 FTBFS in qterm.


Andreas

Bug#829178: marked as done (python-tidylib: FTBFS, test failures with tidy-html5)

2016-09-13 Thread Debian Bug Tracking System 
Your message dated Tue, 13 Sep 2016 10:13:44 +
with message-id 
and subject line Bug#829178: fixed in python-tidylib 0.2.4~dfsg-3
has caused the Debian Bug report #829178,
regarding python-tidylib: FTBFS, test failures with tidy-html5
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.)


-- 
829178: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=829178
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: python-tidylib
Version: 0.2.4~dfsg-2
Severity: serious
Justification: fails to build from source
User: reproducible-bui...@lists.alioth.debian.org
Usertags: ftbfs
Forwarded: https://github.com/countergram/pytidylib/issues/13


Hi, python-tidylib fails to build from source with tidy-html5 because
of test failures.

You can see the failed tests at the upstream bug.

Thanks,
Jeremy Bicha
--- End Message ---
--- Begin Message ---
Source: python-tidylib
Source-Version: 0.2.4~dfsg-3

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

Debian distribution maintenance software
pp.
Mattia Rizzolo  (supplier of updated python-tidylib package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Tue, 13 Sep 2016 08:34:17 +
Source: python-tidylib
Binary: python-tidylib python3-tidylib pytidylib-doc
Architecture: source
Version: 0.2.4~dfsg-3
Distribution: unstable
Urgency: medium
Maintainer: Janos Guljas 
Changed-By: Mattia Rizzolo 
Description:
 python-tidylib - Python 2 wrapper for HTML Tidy (tidylib)
 python3-tidylib - Python 3 wrapper for HTML Tidy (tidylib)
 pytidylib-doc - Python wrapper for HTML Tidy (tidylib) documentation
Closes: 828900 829178
Changes:
 python-tidylib (0.2.4~dfsg-3) unstable; urgency=medium
 .
   * Team upload.
 .
   [ Ondřej Nový ]
   * Fixed VCS URL (https).
 .
   [ Jeremy Bicha ]
   * debian/control:
 - Build-Depend on libtidy-dev.
 - Depend on libtidy5 instead of libtidy-0.99-0.
 - Build-depend on texlive-generic-extra for iftex.sty.  Closes: #828900
 .
   [ Dmitry Shachnev ]
   * Make the tests pass with tidylib 5.  Closes: #829178
 .
   [ Mattia Rizzolo ]
   * Bump Standards-Version to 3.9.8, no changes needed.
   * Bump debhelper compat level to 10.
Checksums-Sha1:
 f196449000892dd7ec3499edad8717bb8c630662 2293 python-tidylib_0.2.4~dfsg-3.dsc
 d38464fd89153fd302eabd4227a21e0a8e509140 4476 
python-tidylib_0.2.4~dfsg-3.debian.tar.xz
Checksums-Sha256:
 1fb7572a60e87063220b34b74773f22a0d189cb4bb9ca398f2429e8b9312b0a9 2293 
python-tidylib_0.2.4~dfsg-3.dsc
 33c6040a33edf1a20302b8b43714206102e5062632c82293a1f286c4d01bb010 4476 
python-tidylib_0.2.4~dfsg-3.debian.tar.xz
Files:
 12f76ad86f4ccc5c9f3240ac339e95f9 2293 python optional 
python-tidylib_0.2.4~dfsg-3.dsc
 d13cd578033bcc9ea1cc2acc24cefd87 4476 python optional 
python-tidylib_0.2.4~dfsg-3.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQIcBAEBCgAGBQJX17pUAAoJEEsEP825REVAtIEQAJDGBlLs5/NSnxwtFfx3h0p3
eNQVrAKFeBi8j8q64pt6KdWZxdHZyqZyZdz16/P9mOq2eseoKi3ywDeuT+3VwkxE
xBMXLSIeRHjTuRqq42b1JI61tumDH2sMiZPyfoa87E3YLlzBSRiwliKFdY+SbNdl
Fe0F2aef29Te2ZUA4prsZiw2xj+R/dDLwIe0sqYDBIzaO2ne2X3WG+Mr5xkB7dxU
BexDWYfvGV9fcnBvLzdZM+OIknGOsBNTKc3IKdu0ZKT8NIvvK6LA1SHCfA4oLxy2
Q+0vDWBxfIjWckix+rO4kSDbiZV3xnzCRg7+l0jrJKCnXZGC0CeEd5OPznCz1Ocb
0MtS+qnQfImYaqnlJzt0sUjKqsm96F9HjVoGMCsQJ83VpJWpst3tKoEk+fracYLN
Rlvac7+G/yPkf0x1gat6/4PHumZflvP5IHDTUSaPvJHGrbPToU0vxuVl5tIUggGI
5PuV216MRFrzI5x8cqK8qrZ7cREO7a4cxtYLAYQphufluwy0EL4ffGCEHI3yfXdQ
5gQvY650I2ydSJpIqYpdAb2qNpA3R6znsEtJRLCAxetpK3lAp0jjfmUslBTdPule
sX0MFYMzOA8EHF0ruKdGCx0vT8ZBNZzD5HfGUehikovuJAeuikhTwwEWzheBow7v
eStb+c1JWcU/3TZ/Dxg1
=ZsjL
-END PGP SIGNATURE End Message ---

Bug#828900: marked as done (python-tidylib: FTBFS: ! LaTeX Error: File `iftex.sty' not found.)

2016-09-13 Thread Debian Bug Tracking System 
Your message dated Tue, 13 Sep 2016 10:13:44 +
with message-id 
and subject line Bug#828900: fixed in python-tidylib 0.2.4~dfsg-3
has caused the Debian Bug report #828900,
regarding python-tidylib: FTBFS: ! LaTeX Error: File `iftex.sty' not found.
to be marked as done.

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

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


-- 
828900: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=828900
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: python-tidylib
Version: 0.2.4~dfsg-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,

python-tidylib fails to build from source in unstable/amd64:

  [..]

  Unpacking texlive-pictures (2016.20160623-1) ...
  Selecting previously unselected package preview-latex-style.
  Preparing to unpack .../preview-latex-style_11.88-1.1_all.deb ...
  Unpacking preview-latex-style (11.88-1.1) ...
  Selecting previously unselected package texlive-latex-extra.
  Preparing to unpack .../texlive-latex-extra_2016.20160623-1_all.deb ...
  Unpacking texlive-latex-extra (2016.20160623-1) ...
  Processing triggers for man-db (2.7.5-1) ...
  Processing triggers for libc-bin (2.22-13) ...
  Processing triggers for systemd (230-3) ...
  Processing triggers for mime-support (3.60) ...
  Setting up python-all (2.7.11-2) ...
  Setting up python3-all (3.5.1-4) ...
  Setting up python3-six (1.10.0-3) ...
  Setting up python3-roman (2.0.0-2) ...
  Setting up sgml-base (1.28) ...
  Setting up xml-core (0.13+nmu2) ...
  Setting up python3-pygments (2.1.3+dfsg-1) ...
  Setting up python3-markupsafe (0.23-2+b2) ...
  Setting up python3-jinja2 (2.8-1) ...
  Setting up python-babel-localedata (2.3.4+dfsg.1-2) ...
  Setting up python3-pkg-resources (20.10.1-1.1) ...
  Setting up python3-tz (2015.7+dfsg-0.1) ...
  Setting up python3-babel (2.3.4+dfsg.1-2) ...
  update-alternatives: using /usr/bin/pybabel-python3 to provide 
/usr/bin/pybabel (pybabel) in auto mode
  Setting up python3-alabaster (0.7.8-1) ...
  Setting up python3-imagesize (0.7.1-1) ...
  Setting up libjs-jquery (1.12.4-1) ...
  Setting up libjs-underscore (1.7.0~dfsg-1) ...
  Setting up libjs-sphinxdoc (1.4.4-2) ...
  Setting up sphinx-common (1.4.4-2) ...
  Setting up libtidy-0.99-0 (20091223cvs-1.5) ...
  Setting up ucf (3.0036) ...
  Setting up tex-common (6.05) ...
  update-language: texlive-base not installed and configured, doing nothing!
  Setting up libkpathsea6:amd64 (2016.20160513.41080-4) ...
  Setting up libptexenc1:amd64 (2016.20160513.41080-4) ...
  Setting up libsynctex1:amd64 (2016.20160513.41080-4) ...
  Setting up libtexlua52:amd64 (2016.20160513.41080-4) ...
  Setting up libtexluajit2:amd64 (2016.20160513.41080-4) ...
  Setting up libpng16-16:amd64 (1.6.23-1) ...
  Setting up libfreetype6:amd64 (2.6.3-3+b1) ...
  Setting up fonts-dejavu-core (2.35-1) ...
  Setting up fontconfig-config (2.11.0-6.4) ...
  Setting up libfontconfig1:amd64 (2.11.0-6.4) ...
  Setting up libpixman-1-0:amd64 (0.33.6-1) ...
  Setting up libxau6:amd64 (1:1.0.8-1) ...
  Setting up libxdmcp6:amd64 (1:1.1.2-1.1) ...
  Setting up libxcb1:amd64 (1.11.1-1) ...
  Setting up libx11-data (2:1.6.3-1) ...
  Setting up libx11-6:amd64 (2:1.6.3-1) ...
  Setting up libxcb-render0:amd64 (1.11.1-1) ...
  Setting up libxcb-shm0:amd64 (1.11.1-1) ...
  Setting up libxext6:amd64 (2:1.3.3-1) ...
  Setting up libxrender1:amd64 (1:0.9.9-2) ...
  Setting up libcairo2:amd64 (1.14.6-1+b1) ...
  Setting up libgraphite2-3:amd64 (1.3.8-1) ...
  Setting up libavahi-common-data:amd64 (0.6.32-1) ...
  Setting up libavahi-common3:amd64 (0.6.32-1) ...
  Setting up libdbus-1-3:amd64 (1.10.8-1) ...
  Setting up libavahi-client3:amd64 (0.6.32-1) ...
  Setting up libcups2:amd64 (2.1.4-1) ...
  Setting up libjpeg62-turbo:amd64 (1:1.5.0-1) ...
  Setting up libjbig0:amd64 (2.1-3.1) ...
  Setting up libtiff5:amd64 (4.0.6-1) ...
  Setting up libijs-0.35:amd64 (0.35-12) ...
  Setting up libjbig2dec0:amd64 (0.13-2) ...
  Setting up liblcms2-2:amd64 (2.7-1) ...
  Setting up libopenjp2-7:amd64 (2.1.0-2.1+b1) ...
  Setting up libpaper1:amd64 (1.1.24+nmu4) ...
  
  Creating config file /etc/papersize with new version
  Setting up poppler-data (0.4.7-7) ...
  Setting up libgs9-common (9.19~dfsg-1) ...
  Setting up libharfbuzz0b:amd64 (1.2.6-2) ...
  Setting up libharfbuzz-icu0:amd64 (1.2.6-2) ...
  Setting up x11-common (1:7.7+15) ...
  update-rc.d: warning: start and stop actions are no longer supported; falling

Processed: The bugs are reproducible in testing as the report says

2016-09-13 Thread Debian Bug Tracking System 
Processing commands for cont...@bugs.debian.org:

> tags 837614 - unreproducible
Bug #837614 {Done: Sebastiaan Couwenberg } 
[src:python-geopandas] python-geopandas: FTBFS in testing (failing tests)
Removed tag(s) unreproducible.
> tags 837622 - unreproducible
Bug #837622 {Done: Sebastiaan Couwenberg } 
[src:python-stetl] python-stetl: FTBFS in testing (failing tests)
Removed tag(s) unreproducible.
> thanks
Stopping processing here.

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

Bug#837012: tachyon: FTBFS: ld: tachyon_ogl-glwin.o: undefined reference to symbol 'XNextEvent'

2016-09-13 Thread Jerome BENOIT 
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Hi, thanks for your patch.

In fact the issue was not in the Makefile.am as a X_LIBS was already present,
but in the configure.ac where X_LIBS was set up but not SUBSTantiated.

Is there a way to cancel the dealy, given that the revison -6 was accepted.

Thanks,
Jerome

On 13/09/16 06:27, Alastair McKinstry wrote:
> Hi,
> 
> I've uploaded an NMU of tachyon that fixes this to DELAYED/5.
> 
> The debdiff is:
> 
> dpkg-source: warning: extracting unsigned source package 
> (/srv/build/tachyon/tachyon_0.99~b6+dsx-5.1.dsc)
> diff -Nru tachyon-0.99~b6+dsx/debian/changelog 
> tachyon-0.99~b6+dsx/debian/changelog
> --- tachyon-0.99~b6+dsx/debian/changelog2016-08-01 02:23:29.0 
> +0100
> +++ tachyon-0.99~b6+dsx/debian/changelog2016-09-12 14:12:26.0 
> +0100
> @@ -1,3 +1,10 @@
> +tachyon (0.99~b6+dsx-5.1) unstable; urgency=medium
> +
> +  * Non-maintainer upload.
> +  * Fix FTBFS: Needs to link against libX11 explicitly. Closes: #837012.
> +
> + -- Alastair McKinstry   Mon, 12 Sep 2016 14:12:26 
> +0100
> +
>  tachyon (0.99~b6+dsx-5) unstable; urgency=medium
> 
>* Debianization:
> diff -Nru tachyon-0.99~b6+dsx/debian/patches/series 
> tachyon-0.99~b6+dsx/debian/patches/series
> --- tachyon-0.99~b6+dsx/debian/patches/series2016-08-01 
> 02:12:39.0 +0100
> +++ tachyon-0.99~b6+dsx/debian/patches/series2016-09-12 
> 14:12:26.0 +0100
> @@ -10,3 +10,4 @@
>  upstream-rationalization-autotools.patch
>  debianization.patch
>  debianization-documentation.patch
> +x11.patch
> diff -Nru tachyon-0.99~b6+dsx/debian/patches/x11.patch 
> tachyon-0.99~b6+dsx/debian/patches/x11.patch
> --- tachyon-0.99~b6+dsx/debian/patches/x11.patch1970-01-01 
> 01:00:00.0 +0100
> +++ tachyon-0.99~b6+dsx/debian/patches/x11.patch2016-09-12 
> 14:12:26.0 +0100
> @@ -0,0 +1,19 @@
> +Author: Alastair McKinstry 
> +Description: X11 lib is needed for linking
> +Bug-Debian: https://bugs.debian.org/837012
> +Last-Update: 2016-09-12
> +Forwarded: no
> +
> +Index: tachyon-0.99~b6+dsx/demosrc/Makefile.am
> +===
> +--- tachyon-0.99~b6+dsx.orig/demosrc/Makefile.am
>  tachyon-0.99~b6+dsx/demosrc/Makefile.am
> +@@ -5,7 +5,7 @@ bin_PROGRAMS += tachyon-nox tachyon-ogl
> + man_MANS += tachyon-nox.1 tachyon-ogl.1
> + endif
> +
> +-
> ++X_LIBS= -lX11
> + AM_CFLAGS = -Wno-unused-result
> +
> + tachyon_SOURCES = \
> 
> regards
> Alastair
> 
> 
> On 13/09/2016 01:50, Jerome BENOIT wrote:
>> Hello Lucas, thanks for the report.
>>
>>
>>
>> On 07/09/16 23:18, Lucas Nussbaum wrote:
>> > Source: tachyon
>> > Version: 0.99~b6+dsx-5
>> > Severity: serious
>> > Tags: stretch sid
>> > User: debian...@lists.debian.org
>> > Usertags: qa-ftbfs-20160906 qa-ftbfs
>> > Justification: FTBFS on amd64
>>
>> > Hi,
>>
>> > During a rebuild of all packages in sid, your package failed to build on
>> > amd64.
>>
>> > Relevant part (hopefully):
>> >> /bin/bash ../libtool  --tag=CC   --mode=link gcc -Wno-unused-result 
>> >> -I/usr/include/libdrm -I/usr/include/libdrm -g -O3 
>> >> -fdebug-prefix-map=/<>/tachyon-0.99~b6+dsx=. -fPIE 
>> >> -fstack-protector-strong -Wformat -Werror=format-security -D_REENTRANT 
>> >> -ffast-math -fomit-frame-pointer   -o tachyon-ogl tachyon_ogl-main.o 
>> >> tachyon_ogl-getargs.o tachyon_ogl-parse.o tachyon_ogl-nffparse.o 
>> >> tachyon_ogl-mgfparse.o tachyon_ogl-ac3dparse.o tachyon_ogl-glwin.o 
>> >> tachyon_ogl-spaceball.o tachyon_ogl-trackball.o ../src/libtachyon.la -lm 
>> >> -lGL  -lGL
>> >> libtool: link: gcc -Wno-unused-result -I/usr/include/libdrm 
>> >> -I/usr/include/libdrm -g -O3 
>> >> "-fdebug-prefix-map=/<>/tachyon-0.99~b6+dsx=." -fPIE 
>> >> -fstack-protector-strong -Wformat -Werror=format-security -D_REENTRANT 
>> >> -ffast-math -fomit-frame-pointer -o .libs/tachyon-ogl tachyon_ogl-main.o 
>> >> tachyon_ogl-getargs.o tachyon_ogl-parse.o tachyon_ogl-nffparse.o 
>> >> tachyon_ogl-mgfparse.o tachyon_ogl-ac3dparse.o tachyon_ogl-glwin.o 
>> >> tachyon_ogl-spaceball.o tachyon_ogl-trackball.o  
>> >> ../src/.libs/libtachyon.so -lm -lGL
>> >> /usr/bin/ld: tachyon_ogl-glwin.o: undefined reference to symbol 
>> >> 'XNextEvent'
>> >> //usr/lib/x86_64-linux-gnu/libX11.so.6: error adding symbols: DSO missing 
>> >> from command line
>> >> collect2: error: ld returned 1 exit status
>>
>> > The full build log is available from:
>> >
>> > http://people.debian.org/~lucas/logs/2016/09/06/tachyon_0.99~b6+dsx-5_unstable.log
>>
>> I could reproduce the issue in a chroot environment.
>> I am working on it.
>>
>>
>>
>> > A list of current common problems and possible solutions is available at
>> > http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute!
>>
>> > About the archive rebuild: The rebuild was done on EC2 VM instances from
>> > Amazon Web Services, using a clean, minimal and up-to-date chroot. Every
>> >

Bug#834281: libgnupg-interface-perl not migrating to testing

2016-09-13 Thread Julien Cristau 
On Mon, Sep 12, 2016 at 23:32:50 +0200, gregor herrmann wrote:

> And gnupg 2.x doesn't migrate because of #836259.
> And libgnupg-interface-perl is about to be removed from testing
> because of #834281 -- but, I think, this bug doesn't affect testing
> since there's gnupg 1.4.x. So removing the stretch tag might already
> help?
> 
No, all bugs tagged sid should also be tagged stretch.

Cheers,
Julien

Bug#837614: The bugs are reproducible in testing as the report says

2016-09-13 Thread Santiago Vila 
tags 837614 - unreproducible
tags 837622 - unreproducible
thanks

Please don't use the unreproducible tag in this way.

The bug says "FTBFS in testing", not simply "FTBFS", so the only way
to reproduce it is by trying it in testing, where it was reported to
fail.

If a report said that "ls -l" segfaults, we would never tag it as
unreproducible after checking that "ls" alone or "ls --color" does not
segfault.

If the bug is already fixed in sid, fine, let's call it "already fixed
in sid". If the package build-depends on another package which is
buggy in stretch and already fixed in sid, fine as well, let's
consider it fixed and let's close the bug.

But please let us use "unreproducible" only for things we don't really know
how to reproduce, which is not the case here.

Thanks.

Bug#837261: marked as done (libconfig-model-dpkg-perl: FTBFS: Tests failures)

2016-09-13 Thread Debian Bug Tracking System 
Your message dated Tue, 13 Sep 2016 10:06:51 +
with message-id 
and subject line Bug#837261: fixed in libconfig-model-dpkg-perl 2.084
has caused the Debian Bug report #837261,
regarding libconfig-model-dpkg-perl: FTBFS: Tests failures
to be marked as done.

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

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


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

Hi,

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

I've seen #834911 but I'm unsure if this is the same bug:
- I'm building in sid
- only one test is failing here, not the two in the above report



Relevant part (hopefully):
> t/scanner/squash_swap_copyright_years.t .. 
> ok 1 - require Dpkg::Copyright::Scanner;
> ok 2 - __squash_copyrights_years dir with squashable copyright
> 1..2
> ok
> 
> Test Summary Report
> ---
> t/model_tests.t(Wstat: 65280 Tests: 814 Failed: 0)
>   Non-zero exit status: 255
>   Parse errors: No plan found in TAP output
> Files=12, Tests=1004, 26 wallclock secs ( 0.17 usr  0.03 sys + 25.46 cusr  
> 0.55 csys = 26.21 CPU)
> Result: FAIL
> Failed 1/12 test programs. 0/1004 subtests failed.
> dh_auto_test: perl Build test --verbose 1 returned exit code 255
> debian/rules:13: recipe for target 'override_dh_auto_test' failed

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

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

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

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

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

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

Debian distribution maintenance software
pp.
Dominique Dumont  (supplier of updated 
libconfig-model-dpkg-perl package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Mon, 12 Sep 2016 19:12:37 +0200
Source: libconfig-model-dpkg-perl
Binary: libconfig-model-dpkg-perl
Architecture: source all
Version: 2.084
Distribution: unstable
Urgency: medium
Maintainer: Debian Perl Group 
Changed-By: Dominique Dumont 
Description:
 libconfig-model-dpkg-perl - editor for Dpkg source files with validation
Closes: 837261
Changes:
 libconfig-model-dpkg-perl (2.084) unstable; urgency=medium
 .
   * control model improvements:
 * Add doc for pkg relation fields
 * Add link to debian policy in Std-Version doc
 * improved Std-Version warning message with a local link
   to upgrade procedure (Tx to Holger Levsen for the idea)
   * fix pan copyright test (Closes: #837261)
   * control: depends on libconfig-model-perl >= 2.090
Checksums-Sha1:
 d8e835a7e39e6fcf368ad3fefe6b9a526d84b2cb 2339 
libconfig-model-dpkg-perl_2.084.dsc
 1d5659044e1b1bfe80635be138b246772569b74c 138984 
libconfig-model-dpkg-perl_2.084.tar.xz
 4a7becc6f90cb6deec57760bafe78ba31fcf238b 154926 
libconfig-model-dpkg-perl_2.084_all.deb
Checksums-Sha256:
 3374c049fc36941ebe7246a418780cae917a11c43bac118ed72902e52c452379 2339 
libconfig-model-dpkg-perl_2.084.dsc
 b512b11f520662f6d3a2c4f4829fdc1cd92cd904e3b3070b2c52422cbe322203 138984 
libconfig-model-dpkg-perl_2.084.tar.xz
 96439cc5e9ed171f6493baad802270992f2a34a9cc43db2621cdca83363b7076 154926 
libconfig-model-dpkg-perl_2.084_all.deb
Files:

Processed: severity of 836585 is normal

2016-09-13 Thread Debian Bug Tracking System 
Processing commands for cont...@bugs.debian.org:

> # Cannot reproduce using clean stretch buildroot
> severity 836585 normal
Bug #836585 [src:celery] celery: FTBFS in testing (failing tests)
Severity set to 'normal' from 'serious'
> thanks
Stopping processing here.

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

Bug#821731: ctk: FTBFS: ctkDICOMUtil.cpp:33:3: error: 'log4cplus' has not been declared

2016-09-13 Thread Andreas Tille 
Hi,

I had a look into ctk and since I did not intended to spent my time on 3
years old code I rewrote get-orig-source and moved the packaging to
Git[1] since its no original download tarball and this simplifies the
cooperation on the very same tarball.

I also tried to bump the Build-Depends to existing versions of the
involved libraries but I stalled when stumbling upon

The following packages have unmet dependencies:
 libopenmpi2 : Conflicts: libopenmpi1.10 but 1.10.3-3 is to be installed
   Breaks: libopenmpi1.10 (>= 1.10.2-1) but 1.10.3-3 is to be 
installed
 libopenmpi-dev : Breaks: libopenmpi1.10 (>= 1.10.2-1) but 1.10.3-3 is to be 
installed
Unable to resolve dependencies!  Giving up...


Since I have no specific interest in ctk itself I will stop here.

IMHO there is no point in leaving RC buggy packages hanging around in
experimental.  Either we will be able to fix the package and move it to
unstable to enable real users touching it or we might remove it from
Debian.

Kind regards

   Andreas.

[1]  https://anonscm.debian.org/git/debian-med/ctk.git

-- 
http://fam-tille.de

Bug#818448: fixed in imapcopy 1.04-2.1

2016-09-13 Thread Gianfranco Costamagna 
Hi,

>imapcopy (1.04-2.1) unstable; urgency=medium

>   * Non-maintainer upload
>   [Peter Michael Green]
>   * Fix build with fpc 3.0.0 (Closes: 818448)
>
>  -- Gianfranco Costamagna   


and this is something I do almost everytime, except when the work is already 
complete
(I mean the patch is already a full debdiff)


>This way it correctly identifies both who authored the change and who decided
it was ready to upload to Unstable.
just to be clear (even if I don't think there has been misunderstanding here)
There are *many* ways to identify the uploader of a particular package
(my favorite is downloading the changes and gpg it to see the signature)
My intention was to avoid having to tweak changelog (laziness) and give you 
full credits, even if the testing
has been performed by two other people

>You should only upload with someone else's name in the changelog trailer if 
>they have explicitly asked for sponsorship.

this makes sense, indeed

>Maybe i'm overcautious but I will only NMU if I have tested at least the 
>basic functioning of the application and ideally have tested it in a way 
>that I know will hit the codepath I changed.
>
>Figuring out how to test a given application, preparing a suitable test 
>environment etc is often more work than writing the actual patch. That 
>is why in this case I merely submitted a patch to the bug report and 
>did not upload as a NMU myself.
>
>IMO your actions testing that the fix was indeed ready for upload are as 
>valuable as my figuring out what needed to be changed to make the 
>package build.

absolutely not ;)
the testing *is* complete, network tested, and some emails have been
migrated successfully from an account to another.

My big fear is that (back to my Bachelor/Master Degree in computer science), I 
did a c program
with the above structs, and for a bug I was not filling them correctly.
For some implementation reasons (I don't recall the exact code), if the struct 
is empty,

it works correctly, when launched in localhost socket.
So I was testing my c program opening a socket on localhost, and connecting to 
it on the same
machine.
Everything has been good until I moved the server on another machine :/

The fix has been to fill correctly that structure, and everything has been 
fixed.

So, the test *is* complete, tested with an online imap server, so the network 
side is fully tested,
and mails are transferred between mailboxes correctly
(this friend even sent me screenshots, I can share them to you privately to 
avoid leaks of emails
or personal data about his mailserver).

But networks are complex, what works for me, and my friend might break on ipv6 
networks or whatever
else is configure differently.

So, in general, even if testing is comprehensive, it won't be 100% complete, 
regardless on hard
you try to check the program.

I Hope this clarify my statements in the above email, as a network engineer, I 
learn
on a daily basis that there is no way to reliably check such code (I'm pretty 
sure it might break/not work

on some cntlm proxy, or whatever else, like it will break half of the Debian 
archive).

Hope it is clear now :D

thanks a lot for the patch!

Gianfranco

Bug#836585: celery: FTBFS in testing (failing tests)

2016-09-13 Thread Santiago Vila 
On Tue, 13 Sep 2016, Paul Wise wrote:

> On Sun, 4 Sep 2016 11:54:01 +0200 (CEST) Santiago Vila wrote:
> 
> > I tried to build this package in stretch with "dpkg-buildpackage -A"
> > (which is what the "Arch: all" autobuilder would do to build it)
> > but it failed:
> 
> I can't reproduce this build failure using `pdebuild --debbuildopts -A`.
> 
> Which version of python-openssl did you have installed?

On 2016-09-04, when I reported the bug, it was python-openssl 16.0.0-2.

I'm having a deja vu...

Now I can think of two ways to handle this:

A. celery now builds in stretch, nothing to do, this was really a bug
in python-openssl and it's already fixed.

or

B. Policy says "it must be possible to build the package when the
build-dependencies are met". Updating the build-depends on
python-openssl and make it versioned takes very little.

I suggested B on another package but (in addition to being called a
lot of things) I was told this:

https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=836508#24

which, as I explained later in the same bug, does not sound very
convincing.

So, if you choose A please be consistent at least and reassign the bug to
python-openssl and use "affects" on "src:celery".

Thanks.

Bug#837644: ruby-devise-async is not compatible with devise >= 4.0

2016-09-13 Thread Pirate Praveen 
package: ruby-devise-async
version: 0.9.0-1
severity: serious

This was introduced as a dependency for gitlab, but gitlab does not
depend on it anymore (removed from Gemfile). We can safely remove the
dependency in gitlab's debian/control. Once that version enters testing,
we can remove ruby-devise-async.



signature.asc
Description: OpenPGP digital signature

Processed: Re: Bug#837614: python-geopandas: FTBFS in testing (failing tests)

2016-09-13 Thread Debian Bug Tracking System 
Processing commands for cont...@bugs.debian.org:

> notfound 837614 python-geopandas/0.2.1-1
Bug #837614 [src:python-geopandas] python-geopandas: FTBFS in testing (failing 
tests)
No longer marked as found in versions python-geopandas/0.2.1-1.
> tags 837614 unreproducible
Bug #837614 [src:python-geopandas] python-geopandas: FTBFS in testing (failing 
tests)
Added tag(s) unreproducible.
> thanks
Stopping processing here.

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

Bug#837614: marked as done (python-geopandas: FTBFS in testing (failing tests))

2016-09-13 Thread Debian Bug Tracking System 
Your message dated Tue, 13 Sep 2016 11:10:20 +0200
with message-id 
and subject line Re: Bug#837614: python-geopandas: FTBFS in testing (failing 
tests)
has caused the Debian Bug report #837614,
regarding python-geopandas: FTBFS in testing (failing tests)
to be marked as done.

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

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


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

Dear maintainer:

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


[...]
--
Ran 164 tests in 57.060s

OK (SKIP=9)
Segmentation fault
E: pybuild pybuild:276: test: plugin custom failed with: exit code=139: 
nosetests -v -e test_geocode.py
dh_auto_test: pybuild --test --test-pytest -i python{version} -p 2.7 returned 
exit code 13
debian/rules:17: recipe for target 'override_dh_auto_test' failed
make[1]: *** [override_dh_auto_test] Error 25
make[1]: Leaving directory '/<>'
debian/rules:6: recipe for target 'build-indep' failed
make: *** [build-indep] Error 2
dpkg-buildpackage: error: debian/rules build-indep gave error exit status 2


[ Using -A is probably not an issue here ]

I can reproduce the error on several unrelated autobuilders.

A full build log is attached.

Thanks.

python-geopandas_0.2.1-1_amd64-20160912T205720Z.gz
Description: application/gzip
--- End Message ---
--- Begin Message ---
notfound 837614 python-geopandas/0.2.1-1
tags 837614 unreproducible
thanks

On 09/12/2016 11:29 PM, Santiago Vila wrote:
> I tried to build this package in stretch with "dpkg-buildpackage -A"
> (which is what the "Arch: all" autobuilder would do to build it)
> but it failed:

Like the Stetl issue I cannot reproduce it in unstable, and it also
seems to be caused by gdal in testing not having been rebuilt with proj
4.9.3. gdal is waiting for perl to migrate to testing which should
happen tomorrow.

Kind Regards,

Bas

-- 
 GPG Key ID: 4096R/6750F10AE88D4AF1
Fingerprint: 8182 DE41 7056 408D 6146  50D1 6750 F10A E88D 4AF1--- End Message ---

Bug#818787: doxygen: Changes default HAVE_DOT to YES without having graphviz in the Depends line.

2016-09-13 Thread Anders Kaseorg 
Hi, I’m one of the nobodies that looks at my build logs.  I noticed five 
instances of

  sh: 1: dot: not found
  error: Problems running dot: exit code=127, command='dot',
  arguments='"…/graph_legend.dot" -Tpng -o "…/graph_legend.png"'

in the openafs build log, and indeed Doxygen is generating 
graph_legend.html files that link to a missing graph_legend.png.  There 
are no explicit uses of dot.  Doxygen decided to do this itself, by 
default.

You can reproduce this error just by running

  doxygen -g; doxygen

in an empty directory without graphviz installed.  I think it’s hard to 
argue that an empty Doxygen project should be expected to manually declare 
a build dependency on graphviz.

Anders

Processed: notfound 837622 in python-stetl/1.0.9+ds-1, tagging 837622

2016-09-13 Thread Debian Bug Tracking System 
Processing commands for cont...@bugs.debian.org:

> notfound 837622 python-stetl/1.0.9+ds-1
Bug #837622 {Done: Sebastiaan Couwenberg } 
[src:python-stetl] python-stetl: FTBFS in testing (failing tests)
No longer marked as found in versions python-stetl/1.0.9+ds-1.
> tags 837622 + unreproducible
Bug #837622 {Done: Sebastiaan Couwenberg } 
[src:python-stetl] python-stetl: FTBFS in testing (failing tests)
Added tag(s) unreproducible.
> thanks
Stopping processing here.

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

Processed: your mail

2016-09-13 Thread Debian Bug Tracking System 
Processing commands for cont...@bugs.debian.org:

> severity 816593 normal
Bug #816593 [src:iceweasel] [FTBFS] iceweasel esr for wheezy on amd64
Severity set to 'normal' from 'serious'
>
End of message, stopping processing here.

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

Bug#837622: marked as done (python-stetl: FTBFS in testing (failing tests))

2016-09-13 Thread Debian Bug Tracking System 
Your message dated Tue, 13 Sep 2016 10:45:29 +0200
with message-id <9526e4fd-1d0c-654e-6c2e-bd846dc09...@xs4all.nl>
and subject line Re: Bug#837622: python-stetl: FTBFS in testing (failing tests)
has caused the Debian Bug report #837622,
regarding python-stetl: FTBFS in testing (failing tests)
to be marked as done.

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

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


-- 
837622: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=837622
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:python-stetl
Version: 1.0.9+ds-1
Severity: serious

Dear maintainer:

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


[...]
 debian/rules build-indep
dh build-indep \
--buildsystem=pybuild \
--with python2 \
--parallel
   dh_testdir -i -O--buildsystem=pybuild -O--parallel
   dh_update_autotools_config -i -O--buildsystem=pybuild -O--parallel
   dh_auto_configure -i -O--buildsystem=pybuild -O--parallel
I: pybuild base:184: python2.7 setup.py config 
running config
   debian/rules override_dh_auto_build
make[1]: Entering directory '/<>/python-stetl-1.0.9+ds'
# Create man page from DocBook XML

[... snipped ...]

writing output... [ 44%] contact
writing output... [ 55%] index
writing output... [ 66%] install
writing output... [ 77%] intro
writing output... [ 88%] links
writing output... [100%] using

generating indices... genindex py-modindex
highlighting module code... [  3%] stetl.outputs.httpoutput
highlighting module code... [  6%] stetl.outputs.standardoutput
highlighting module code... [ 10%] stetl.outputs.wfsoutput
highlighting module code... [ 13%] stetl.factory
highlighting module code... [ 17%] stetl.outputs.ogroutput
highlighting module code... [ 20%] stetl.main
highlighting module code... [ 24%] stetl.input
highlighting module code... [ 27%] stetl.outputs.fileoutput
highlighting module code... [ 31%] stetl.filters.stringfilter
highlighting module code... [ 34%] stetl.inputs.deegreeinput
highlighting module code... [ 37%] stetl.filters.gmlfeatureextractor
highlighting module code... [ 41%] stetl.filters.formatconverter
highlighting module code... [ 44%] stetl.component
highlighting module code... [ 48%] stetl.inputs.httpinput
highlighting module code... [ 51%] stetl.filters.gmlsplitter
highlighting module code... [ 55%] stetl.filters.templatingfilter
highlighting module code... [ 58%] stetl.filters.xsltfilter
highlighting module code... [ 62%] stetl.inputs.ogrinput
highlighting module code... [ 65%] stetl.outputs.dboutput
highlighting module code... [ 68%] stetl.output
highlighting module code... [ 72%] stetl.etl
highlighting module code... [ 75%] stetl.filter
highlighting module code... [ 79%] stetl.filters.xmlassembler
highlighting module code... [ 82%] stetl.packet
highlighting module code... [ 86%] stetl.outputs.deegreeoutput
highlighting module code... [ 89%] stetl.chain
highlighting module code... [ 93%] stetl.inputs.fileinput
highlighting module code... [ 96%] stetl.inputs.dbinput
highlighting module code... [100%] stetl.filters.xmlvalidator

writing additional pages... search
copying static files... done
copying extra files... done
dumping search index in English (code: en) ... done
dumping object inventory... done
build succeeded, 1 warning.
Makefile:45: recipe for target 'html' failed
make[2]: *** [html] Segmentation fault
make[2]: Leaving directory '/<>/python-stetl-1.0.9+ds/docs'
debian/rules:27: recipe for target 'override_dh_auto_build' failed
make[1]: *** [override_dh_auto_build] Error 2
make[1]: Leaving directory '/<>/python-stetl-1.0.9+ds'
debian/rules:14: recipe for target 'build-indep' failed
make: *** [build-indep] Error 2
dpkg-buildpackage: error: debian/rules build-indep gave error exit status 2


I can reproduce the error on several unrelated autobuilders.

A full build log is attached.

Thanks.

python-stetl_1.0.9+ds-1_amd64-20160912T211122Z.gz
Description: application/gzip
--- End Message ---
--- Begin Message ---
notfound 837622 python-stetl/1.0.9+ds-1
tags 837622 unreproducible
thanks

On 09/13/2016 12:07 AM, Santiago Vila wrote:
> I tried to build this package in stretch with "dpkg-buildpackage -A"
> (which is what the "Arch: all" autobuilder would do to build it)
> but it failed:

I cannot reproduce this is in unstable, so I suspect it's caused by gdal
in testing not having been rebuilt with proj 4.9.3 yet.

Bug#837638: ruby-devise-async: Incompatible with ruby-devise 4

2016-09-13 Thread Jeremy Bicha 
Package: ruby-devise-async
Version: 0.9.0-1
Severity: serious

Ever since ruby-devise 4.1.1-2 was uploaded to Debian unstable,
ruby-devise-async has been failing its autopkgtests.

https://ci.debian.net/packages/r/ruby-devise-async/unstable/amd64/

I looked upstream and it's apparently a known issue:

https://github.com/mhfs/devise-async/issues/94

Thanks,
Jeremy

  1   2   >