Bug#836759: proftpd-dfsg: please drop the build dependency on hardening-wrapper

[Niels Thykier]

Hilmar Preuße:
> tags 836759 + pending
> stop
> 
> On 19.09.2016 19:29, Niels Thykier wrote:
>> On Sat, 17 Sep 2016 22:36:20 +0200 Hilmar Preusse  wrote:
> 
> Hi,
> 
>>> Is it OK to simply remove that check? Is there an replacement for
>>> hardening-check?
>>>
>> Hi Hilmar :)
>>
>> I believe you can just remove that check.
>>
> Done in git, tag pending.
> 

Thanks,

>> As for a replacement, lintian will still implement the hardening-no-*
>> tags, which were based on the code from hardening-check.
>>
> Hmm: lintian still depends on hardening-includes. Not my problem. ;-)
> 
> Hilmar
> 

Indeed, the dependency will be removed in the next upload. :)

Thanks,
~Niels

Bug#838336: gnome-control-center: Keybinding panel fail to open

[mathieu rousseau]

Package: gnome-control-center
Version: 1:3.21.92-2
Severity: grave
Justification: renders package unusable

In gnome-control-center, the "keyboard" entry, for keybinding configuration 
fail to open (and gnome-control-center close). The trace i got in terminal is : 

(gnome-control-center:24830): Gtk-CRITICAL **: Error building template class 
'CcKeyboardPanel' for an instance of type 'CcKeyboardPanel': .:2:1622 Invalid 
property: GtkScrolledWindow.propagate_natural_width

(gnome-control-center:24830): Gtk-CRITICAL **: gtk_container_add: assertion 
'GTK_IS_CONTAINER (container)' failed
[…]
(gnome-control-center:24830): Gtk-CRITICAL **: gtk_list_box_set_sort_func: 
assertion 'GTK_IS_LIST_BOX (box)' failed

(gnome-control-center:24830): Gtk-CRITICAL **: gtk_list_box_set_header_func: 
assertion 'GTK_IS_LIST_BOX (box)' failed

(gnome-control-center:24830): Gtk-CRITICAL **: gtk_list_box_set_filter_func: 
assertion 'GTK_IS_LIST_BOX (box)' failed

(gnome-control-center:24830): Gtk-CRITICAL **: gtk_list_box_set_placeholder: 
assertion 'GTK_IS_LIST_BOX (box)' failed

(gnome-control-center:24830): Gtk-CRITICAL **: gtk_box_pack: assertion 
'GTK_IS_WIDGET (child)' failed

(gnome-control-center:24830): GLib-GObject-CRITICAL **: g_object_ref: assertion 
'G_IS_OBJECT (object)' failed

(gnome-control-center:24830): Gtk-CRITICAL **: gtk_size_group_add_widget: 
assertion 'GTK_IS_WIDGET (widget)' failed
**
ERROR:cc-panel.c:202:cc_panel_size_allocate: assertion failed: (child)



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

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

Versions of packages gnome-control-center depends on:
ii  accountsservice0.6.40-3
ii  apg2.2.3.dfsg.1-4
ii  colord 1.3.3-2
ii  desktop-file-utils 0.23-1
ii  gnome-control-center-data  1:3.21.92-2
ii  gnome-desktop3-data3.21.92-1
ii  gnome-settings-daemon  3.21.90-2
ii  gsettings-desktop-schemas  3.21.4-2
ii  libaccountsservice00.6.40-3
ii  libatk1.0-02.21.90-2
ii  libc6  2.23-5
ii  libcairo-gobject2  1.14.6-1+b1
ii  libcairo2  1.14.6-1+b1
ii  libcanberra-gtk3-0 0.30-3
ii  libcanberra0   0.30-3
ii  libcheese-gtk253.21.92-1
ii  libcheese8 3.21.92-1
ii  libclutter-1.0-0   1.26.0-2
ii  libclutter-gtk-1.0-0   1.8.0-2
ii  libcolord-gtk1 0.1.26-1
ii  libcolord2 1.3.3-2
ii  libcups2   2.1.4-4
ii  libfontconfig1 2.11.0-6.7
ii  libgdk-pixbuf2.0-0 2.34.0-1
ii  libglib2.0-0   2.49.6-1
ii  libgnome-bluetooth13   3.20.0-1
ii  libgnome-desktop-3-12  3.21.92-1
ii  libgoa-1.0-0b  3.21.91-1
ii  libgoa-backend-1.0-1   3.21.91-1
ii  libgrilo-0.3-0 0.3.2-1
ii  libgtk-3-0 3.21.5-3
ii  libgtop-2.0-10 2.34.1-2
ii  libgudev-1.0-0 230-3
ii  libibus-1.0-5  1.5.11-1
ii  libkrb5-3  1.14.3+dfsg-2
ii  libmm-glib01.6.0-1
ii  libnm0 1.2.4-2
ii  libnma01.2.4-1
ii  libpango-1.0-0 1.40.2-1
ii  libpangocairo-1.0-01.40.2-1
ii  libpolkit-gobject-1-0  0.105-16
ii  libpulse-mainloop-glib09.0-3
ii  libpulse0  9.0-3
ii  libpwquality1  1.3.0-1
ii  libsmbclient   2:4.4.5+dfsg-3
ii  libsoup2.4-1   2.55.90-1
ii  libupower-glib30.99.4-3
ii  libwacom2  0.19-1
ii  libx11-6   2:1.6.3-1
ii  libxi6 2:1.7.6-1
ii  libxml22.9.4+dfsg1-2

Versions of packages gnome-control-center recommends:
ii  cracklib-runtime  2.9.2-3
ii  cups-pk-helper0.2.6-1
ii  gkbd-capplet  3.6.0-1
ii  gnome-online-accounts 3.21.91-1
ii  gnome-user-guide  3.20.2-1
ii  gnome-user-share  3.18.2-1
ii  iso-codes 3.70-1
ii  libnss-myhostname 231-4
ii  mousetweaks   3.12.0-1
ii  network-manager-gnome 1.2.4-1
ii  policykit-1   0.105-16
ii  pulseaudio-module-bluetooth   9.0-3
ii  realmd0.16.3-1
ii  rygel 0.30.3-1
ii  rygel-tracker 0.30.3-1
ii  system-config-printer-common  1.5.7-2

Versions of packages gnome-control-center suggests:
ii  gstreamer1.0-pulseaudio  1.8.3-1+b1
pn  libcanberra-gtk-module   
ii  libcanberra-gtk3-module  0.30-3
ii  x11-xserver-utils7.7+7

-- no debconf information

Bug#838047: marked as done (segfault kills gnome-shell, all graphics tablets)

[Debian Bug Tracking System]

Your message dated Tue, 20 Sep 2016 00:21:11 +
with message-id 
and subject line Bug#838050: fixed in mutter 3.22.0-1
has caused the Debian Bug report #838050,
regarding segfault kills gnome-shell, all graphics tablets
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.)


-- 
838050: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=838050
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: libwacom2
Version: 0.19-1
Severity: critical
Justification: breaks the whole system

Dear Maintainer,


After a reboot, I got a blank screen instead of my gdm login screen. Dmesg told 
me that gnome-shell reported a segfault in libwacom. I installed the debug 
version of libwacom and started X with gdb, but could not get a trace as the 
screen froze when I did so. At the moment, I can only work from the console.

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

Kernel: Linux 4.7.0-1-amd64 (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/dash
Init: systemd (via /run/systemd/system)

Versions of packages libwacom2 depends on:
ii  libc62.24-2
ii  libglib2.0-0 2.49.7-1
ii  libgudev-1.0-0   230-3
ii  libwacom-common  0.19-1

Versions of packages libwacom2 recommends:
ii  libwacom-bin  0.19-1

libwacom2 suggests no packages.

-- no debconf information
--- End Message ---
--- Begin Message ---
Source: mutter
Source-Version: 3.22.0-1

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

Debian distribution maintenance software
pp.
Michael Biebl  (supplier of updated mutter 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, 20 Sep 2016 01:43:37 +0200
Source: mutter
Binary: mutter libmutter0i mutter-common libmutter-dev gir1.2-mutter-3.0
Architecture: source
Version: 3.22.0-1
Distribution: unstable
Urgency: medium
Maintainer: Debian GNOME Maintainers 

Changed-By: Michael Biebl 
Description:
 gir1.2-mutter-3.0 - GObject introspection data for Mutter
 libmutter-dev - Development files for the Mutter window manager
 libmutter0i - window manager library from the Mutter window manager
 mutter - lightweight GTK+ window manager
 mutter-common - shared files for the Mutter window manager
Closes: 836153 838050
Changes:
 mutter (3.22.0-1) unstable; urgency=medium
 .
   [ Jeremy Bicha ]
   * debian/control.in:
 - Explicitly build-depend on libegl1-mesa-dev (Closes: #836153)
 .
   [ Michael Biebl ]
   * New upstream release.
 - Correctly handle tablet settings lookups with no backing libwacom info.
   (Closes: #838050)
   * Use non-multiarch path (/usr/lib/mutter) for libexecdir.
Checksums-Sha1:
 25b60e78584ca5ef944044a8fd81ff702ce03dc6 3253 mutter_3.22.0-1.dsc
 1c91e0276655b3a727b3345fbfa1ac0875a8f919 3531916 mutter_3.22.0.orig.tar.xz
 68f962f8b3a5bf4a7470b5a8f65806bd4be71075 20300 mutter_3.22.0-1.debian.tar.xz
Checksums-Sha256:
 ac6bb89a3217edd73a9a41f5ccb005d2a2b96427f8b3e298c9a017c4b0d5ec0f 3253 
mutter_3.22.0-1.dsc
 a5acdde788f5d137ec6dfe218a214c1f6cfb7e2e851fbcebe0b2d67b4c96e5f3 3531916 
mutter_3.22.0.orig.tar.xz
 43470e9ffe10112f28b00fbac4b1bd4cf52979d8dc89a3f06bec831cd0c89d77 20300 
mutter_3.22.0-1.debian.tar.xz
Files:
 3e8785a95bd7c6b333da53d2320469ee 3253 x11 optional mutter_3.22.0-1.dsc
 e448039015b355e7e2b9f86087e2f399 3531916 x11 optional mutter_3.22.0.orig.tar.xz
 4b19eed179ff7cd721ba50ce0b3409c7 20300 x11 optional 
mutter_3.22.0-1.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQIuBAEBCAAYBQJX4HhSERxiaWVibEBkZWJpYW4ub3JnAAoJEGrh3w1gjyLcT38P
/3wW2//7wUwfEX9NzvP3mKvn8+bQjhE60kByO+6BohpHGz/xiFbaKplsg6zHKd0C
395Qn6ep3UnjwQ7rmoRvafgZC1AuttjDhBk5rsnIbJ9WKlKw95b3ah75zqXrBw6f

Bug#838050: marked as done (segfault kills gnome-shell, all graphics tablets)

[Debian Bug Tracking System]

Your message dated Tue, 20 Sep 2016 00:21:11 +
with message-id 
and subject line Bug#838050: fixed in mutter 3.22.0-1
has caused the Debian Bug report #838050,
regarding segfault kills gnome-shell, all graphics tablets
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.)


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

After startup, gdm doesn't show up and just shows a grey screen. Looking at 
syslog reveals the reason:

syslog:Sep 16 23:27:25 matte kernel: [  172.983123] gnome-shell[3206]: segfault 
at 10 ip 7f8e7c85d6c4 sp 7ffd151d0a80 error 4 in libwacom.so.2.4.6[7f8e7
c85a000+9000]

Since I haven't updated libwacom2 in the last 2 weeks, but gnome-shell was 
recently updated, I assume this is due to a problem in gnome-shell.

There is also a temporary fix, just run: rmmod wacom, and then restart gdm, and 
you can use it again, of course without the touchscreen.

Unfortunately, in upstream, I cannot see any kind of commit between 3.21.92 and 
3.21.91 that might cause such a problem.


-- 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/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 gnome-shell depends on:
ii  dconf-gsettings-backend [gsettings-backend]  0.26.0-1
ii  evolution-data-server3.20.5-1
ii  gir1.2-accountsservice-1.0   0.6.40-3
ii  gir1.2-atspi-2.0 2.20.2-2
ii  gir1.2-caribou-1.0   0.4.21-1
ii  gir1.2-freedesktop   1.49.2-1
ii  gir1.2-gcr-3 3.20.0-2
ii  gir1.2-gdesktopenums-3.0 3.21.4-2
ii  gir1.2-gdm-1.0   3.21.91-1
ii  gir1.2-glib-2.0  1.49.2-1
ii  gir1.2-gnomebluetooth-1.03.20.0-1
ii  gir1.2-gnomedesktop-3.0  3.21.92-1
ii  gir1.2-gtk-3.0   3.21.6-1
ii  gir1.2-gweather-3.0  3.20.3-1
ii  gir1.2-ibus-1.0  1.5.11-1
ii  gir1.2-mutter-3.03.21.92-1
ii  gir1.2-networkmanager-1.01.4.0-3
ii  gir1.2-nmgtk-1.0 1.4.0-2
ii  gir1.2-pango-1.0 1.40.2-1
ii  gir1.2-polkit-1.00.105-16
ii  gir1.2-soup-2.4  2.55.90-1
ii  gir1.2-telepathyglib-0.120.24.1-1.1
ii  gir1.2-telepathylogger-0.2   0.8.2-1
ii  gir1.2-upowerglib-1.00.99.4-3
ii  gjs  1.45.4-2
ii  gnome-backgrounds3.21.91-1
ii  gnome-settings-daemon3.21.92.1-1
ii  gnome-shell-common   3.21.92-1
ii  gsettings-desktop-schemas3.21.4-2
ii  libatk-bridge2.0-0   2.20.1-4
ii  libatk1.0-0  2.21.90-2
ii  libc62.24-2
ii  libcairo21.14.6-1+b1
ii  libcanberra-gtk3-0   0.30-3
ii  libcanberra0 0.30-3
ii  libcroco30.6.11-1
ii  libdbus-glib-1-2 0.108-1
ii  libecal-1.2-19   3.20.5-1
ii  libedataserver-1.2-213.20.5-1
ii  libgcr-base-3-1  3.20.0-2
ii  libgdk-pixbuf2.0-0   2.35.5-1
ii  libgirepository-1.0-11.49.2-1
ii  libgjs0e [libgjs0-libmozjs-24-0] 1.45.4-2
ii  libglib2.0-0 2.49.7-1
ii  libglib2.0-bin   2.49.7-1
ii  libgstreamer1.0-01.8.3-1
ii  libgtk-3-0   3.21.6-1
ii  libical2 2.0.0-0.5+b1
ii  libicu57 57.1-4
ii  libjson-glib-1.0-0   1.2.2-1
ii  libmozjs-24-024.2.0-3.1
ii  

Bug#838327: dune-pdelab: FTBFS in testing (error: cannot convert 'mem_usage_t*' to 'GlobalLU_t*')

[Ansgar Burchardt]

Santiago Vila writes:
> /usr/include/dune/istl/superlu.hh: In static member function 'static void 
> Dune::SuperLUSolveChooser::solve(superlu_options_t*, SuperMatrix*, 
> int*, int*, int*, char*, double*, double*, SuperMatrix*, SuperMatrix*, void*, 
> int, SuperMatrix*, SuperMatrix*, double*, double*, double*, double*, 
> mem_usage_t*, SuperLUStat_t*, int*)':
> /usr/include/dune/istl/superlu.hh:172:34: error: cannot convert 
> 'mem_usage_t*' to 'GlobalLU_t*' for argument '19' to 'void 
> dgssvx(superlu_options_t*, SuperMatrix*, int*, int*, int*, char*, double*, 
> double*, SuperMatrix*, SuperMatrix*, void*, int, SuperMatrix*, SuperMatrix*, 
> double*, double*, double*, double*, GlobalLU_t*, mem_usage_t*, 
> SuperLUStat_t*, int*)'
>   memusage, stat, info);
>   ^

That looks like an API change in SuperLU.  The following changelog entry
for SuperLU 5.0 looks related:

+---
|  Remove 'static' variable 'Glu' in *gstrf.c, instead, pass it as an argument.
+---[ http://crd-legacy.lbl.gov/~xiaoye/SuperLU/changes.html ]

I wouldn't be surprised if `GlobalLU_t` and `Glu` were related; will try
to look at this.

Ansgar

Bug#838331: mono-reference-assemblies-3.5: does not contain the reference assemblies

[Felipe Sateler]

Package: mono-reference-assemblies-3.5
Version: 3.12.1+dfsg-1
Severity: grave
Justification: renders package unusable

This package appears to not contain much files. Installing the package
does not allow one to xbuild a project targeting .net 3.5. 

It appears that it is missing the required files:
% dpkg -L mono-reference-assemblies-2.0 | wc -l
103
% dpkg -L mono-reference-assemblies-3.5 | wc -l
16

Saludos

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

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

Versions of packages mono-reference-assemblies-3.5 depends on:
ii  mono-runtime-common  4.2.1.102+dfsg2-8

mono-reference-assemblies-3.5 recommends no packages.

mono-reference-assemblies-3.5 suggests no packages.

-- no debconf information

Bug#838050: Fix now in upstream

[Andrew Chadwick]

The fix is included upstream in modified form as
https://git.gnome.org/browse/mutter/commit/?id=3137ddb1a1071407f557a181121695e37e5faf3d.
I have not tested this exact patch, but it should work.

This bug will be fixed by mutter 3.22.0, which seems to have just been
tagged upstream.



-- 
Andrew Chadwick

Bug#832840: license-reconcile: diff for NMU version 0.12+nmu1

[gustavo panizzo (gfa)]

On Mon, Sep 19, 2016 at 07:15:50PM +0200, gregor herrmann wrote:
> On Mon, 19 Sep 2016 00:32:17 +0800, gustavo panizzo (gfa) wrote:
> 
> > I've attached the debdiff, I'll push my changes to the git repo after
> > the NMU has been uploaded, let me know if you don't agree with any of
> > this.
> 
> Thanks for your help.
> 
> It might be easier to push the changes to the git repo before an
> upload, with 0.12 instead of 0.12+nmu1, and we can do a regular tram
> upload. -- Whatever you prefer.

I have no preference on the matter, and you are the maintainer.
I've tried to push to the git repo but I have no perms. so I've attached
the diff between HEAD and your last commit to this email

I've fixed a typo lib/Debian/LicenseReconcile/CopyrightDatum.pm as well

thanks!

-- 
1AE0 322E B8F7 4717 BDEA BF1D 44BB 1BA7 9F6C 6333

keybase: https://keybase.io/gfa
diff --git a/debian/changelog b/debian/changelog
index becd035..81e9e09 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,15 +1,3 @@
-license-reconcile (0.12) unstable; urgency=medium
-
-  [ gustavo panizzo ]
-  * Update test cases to match licensecheck output. Thanks Petter Reinholdtsen
-for the patches, Fix FTBFS (Closes: #832840).
-  * Fix typo in lib/Debian/LicenseReconcile/CopyrightDatum.pm.
-
-  [ gregor herrmann ]
-  * Remove Nicholas Bamber from Uploaders. Thanks for your work!
-
- -- gustavo panizzo   Sun, 18 Sep 2016 10:40:39 +0800
-
 license-reconcile (0.11) unstable; urgency=medium
 
   * debian/copyright: change Copyright-Format 1.0 URL to HTTPS.
diff --git a/lib/Debian/LicenseReconcile/App.pm b/lib/Debian/LicenseReconcile/App.pm
index 993a12b..f9fa59f 100644
--- a/lib/Debian/LicenseReconcile/App.pm
+++ b/lib/Debian/LicenseReconcile/App.pm
@@ -289,8 +289,6 @@ This contains the core logic of the tool.
 
 =head2 files
 
-=head2 suggest_stanzas
-
 =head1 AUTHOR
 
 Nicholas Bamber, C<<  >>
diff --git a/lib/Debian/LicenseReconcile/CopyrightDatum.pm b/lib/Debian/LicenseReconcile/CopyrightDatum.pm
index ea8383f..06ea421 100644
--- a/lib/Debian/LicenseReconcile/CopyrightDatum.pm
+++ b/lib/Debian/LicenseReconcile/CopyrightDatum.pm
@@ -253,7 +253,7 @@ This method returns a boolean indicating whether the object contains the argumen
 The method will respect the argument if it is a
 L and otherwise stringify and parse it.
 It may also take an optional reference. If this is set on failing to
-verify containment the reason found will be placed in that reference.
+veryify containment the reason found will be placed in that reference.
 
 =head2 copyright_holders 
 
diff --git a/t/08-licensecheck.t b/t/08-licensecheck.t
index c4faf2f..81fea4e 100644
--- a/t/08-licensecheck.t
+++ b/t/08-licensecheck.t
@@ -86,61 +86,61 @@ cmp_deeply(\@data, bag(
 {
 file=>'Apache_2_0',
 license=>'test1',
-	copyright=>['Copyright: 2000 Testophilus Testownik .'],
+	copyright=>['Copyright: 2000 Testophilus Testownik '],
 },
 {
 file=>'FreeBSD',
 license=>'test2',
-	copyright=>['Copyright: 2001 Testophilus Testownik .'],
+	copyright=>['Copyright: 2001 Testophilus Testownik '],
 },
 {
 file=>'GPL_1',
 license=>'test3',
-	copyright=>['Copyright: 2002 Testophilus Testownik .'],
+	copyright=>['Copyright: 2002 Testophilus Testownik '],
 },
 {
 file=>'GPL_2',
 license=>'test4',
-	copyright=>['Copyright: 2003 Testophilus Testownik .'],
+	copyright=>['Copyright: 2003 Testophilus Testownik '],
 },
 {
 file=>'GPL_3',
 license=>'test5',
-	copyright=>['Copyright: 2004 Testophilus Testownik .'],
+	copyright=>['Copyright: 2004 Testophilus Testownik '],
 },
 {
 file=>'LGPL_2',
 license=>'test6',
-	copyright=>['Copyright: 2005 Testophilus Testownik .'],
+	copyright=>['Copyright: 2005 Testophilus Testownik '],
 },
 {
 file=>'LGPL_2_1',
 license=>'test7',
-	copyright=>['Copyright: 2006 Testophilus Testownik .'],
+	copyright=>['Copyright: 2006 Testophilus Testownik '],
 },
 {
 file=>'LGPL_3_0',
 license=>'test8',
-	copyright=>['Copyright: 2007 Testophilus Testownik .'],
+	copyright=>['Copyright: 2007 Testophilus Testownik '],
 },
 {
 file=>'MIT',
 license=>'test9',
-	copyright=>['Copyright: 2008 Testophilus Testownik .'],
+	copyright=>['Copyright: 2008 Testophilus Testownik '],
 },
 {
 file=>'Mozilla_2_0',
 license=>'test10',
-	copyright=>['Copyright: 2009 Testophilus Testownik .'],
+	copyright=>['Copyright: 2009 Testophilus Testownik '],
 },
 {

Bug#838327: dune-pdelab: FTBFS in testing (error: cannot convert 'mem_usage_t*' to 'GlobalLU_t*')

[Santiago Vila]

Package: src:dune-pdelab
Version: 2.4.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:


[...]
 debian/rules build-indep
dh build-indep --parallel
   dh_testdir -i -O--parallel
   dh_update_autotools_config -i -O--parallel
   debian/rules override_dh_auto_configure
make[1]: Entering directory '/<>'
/usr/bin/dunecontrol autogen
WARNING: could not find module dune-alugrid,
   module is also unknown to pkg-config.
   Maybe you need to adjust PKG_CONFIG_PATH!
   dune-alugrid is suggested by dune-pdelab
Skipping dune-alugrid!
--- going to build dune-pdelab  ---

[... snipped ...]

libtool: link: g++ -std=c++11 -g -O2 -fdebug-prefix-map=/<>=. 
-fstack-protector-strong -Wformat -Werror=format-security -fpermissive -pthread 
-pthread -Wl,-z -Wl,relro -o .libs/testgridfunctionspace 
testgridfunctionspace.o -pthread -Wl,-rpath -Wl,/usr/lib/openmpi/lib 
-Wl,--enable-new-dtags  ../../../lib/.libs/libdunepdelab.so -ldunegrid 
-ldunegeometry -ldunecommon -L/usr/lib/openmpi/lib -lmpi -lugS2 -lugS3 -ldevS 
-lm -pthread
g++ -std=c++11 -DHAVE_CONFIG_H -I. -I../../..  -pthread  -I./ -I./  -I./ -I./  
-I./ -I./  -I./ -I./  -I./ -I./  -I./ -I./ -DENABLE_POSIX_CLOCK -I../../.. 
-DGRIDSDIR="\"./grids\"" -DENABLE_UG   -pthread  -I./ -I./  -I./ -I./  -I./ 
-I./  -I./ -I./  -I./ -I./  -I./ -I./ -DENABLE_POSIX_CLOCK 
-I/usr/lib/openmpi/include/openmpi/opal/mca/event/libevent2021/libevent 
-I/usr/lib/openmpi/include/openmpi/opal/mca/event/libevent2021/libevent/include 
-I/usr/lib/openmpi/include -I/usr/lib/openmpi/include/openmpi -pthread 
-DMPIPP_H -DENABLE_MPI=1  -I/usr/include/superlu -DENABLE_SUPERLU -Wdate-time 
-D_FORTIFY_SOURCE=2  -g -O2 -fdebug-prefix-map=/<>=. 
-fstack-protector-strong -Wformat -Werror=format-security -fpermissive -c -o 
testelasticity-testelasticity.o `test -f 'testelasticity.cc' || echo 
'./'`testelasticity.cc
In file included from /usr/include/dune/istl/paamg/amg.hh:13:0,
 from 
../../../dune/pdelab/backend/istl/seqistlsolverbackend.hh:15,
 from ../../../dune/pdelab/backend/istl/istlsolverbackend.hh:6,
 from ../../../dune/pdelab/backend/istl.hh:7,
 from testelasticity.cc:20:
/usr/include/dune/istl/superlu.hh: In static member function 'static void 
Dune::SuperLUSolveChooser::solve(superlu_options_t*, SuperMatrix*, 
int*, int*, int*, char*, double*, double*, SuperMatrix*, SuperMatrix*, void*, 
int, SuperMatrix*, SuperMatrix*, double*, double*, double*, double*, 
mem_usage_t*, SuperLUStat_t*, int*)':
/usr/include/dune/istl/superlu.hh:172:34: error: cannot convert 'mem_usage_t*' 
to 'GlobalLU_t*' for argument '19' to 'void dgssvx(superlu_options_t*, 
SuperMatrix*, int*, int*, int*, char*, double*, double*, SuperMatrix*, 
SuperMatrix*, void*, int, SuperMatrix*, SuperMatrix*, double*, double*, 
double*, double*, GlobalLU_t*, mem_usage_t*, SuperLUStat_t*, int*)'
  memusage, stat, info);
  ^
Makefile:1646: recipe for target 'testelasticity-testelasticity.o' failed
make[7]: *** [testelasticity-testelasticity.o] Error 1
make[7]: Leaving directory '/<>/dune/pdelab/test'
Makefile:2231: recipe for target 'check-am' failed
make[6]: *** [check-am] Error 2
make[6]: Leaving directory '/<>/dune/pdelab/test'
Makefile:1808: recipe for target 'check-recursive' failed
make[5]: *** [check-recursive] Error 1
make[5]: Leaving directory '/<>/dune/pdelab/test'
Makefile:638: recipe for target 'check-recursive' failed
make[4]: *** [check-recursive] Error 1
make[4]: Leaving directory '/<>/dune/pdelab'
Makefile:620: recipe for target 'check-recursive' failed
make[3]: *** [check-recursive] Error 1
make[3]: Leaving directory '/<>/dune'
Makefile:798: recipe for target 'check-recursive' failed
make[2]: *** [check-recursive] Error 1
make[2]: Leaving directory '/<>'
dh_auto_test: make -j1 check VERBOSE=1 returned exit code 2
/usr/share/dune/dune-debian.mk:26: recipe for target 'override_dh_auto_test' 
failed
make[1]: *** [override_dh_auto_test] Error 2
make[1]: Leaving directory '/<>'
debian/rules:10: recipe for target 'build-indep' failed
make: *** [build-indep] Error 2
dpkg-buildpackage: error: debian/rules build-indep gave error exit status 2


Seems a GCC 6 related problem.

Thanks.

Processed: affects

[Debian Bug Tracking System]

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

> affects 837618 src:dia
Bug #837618 [xml-core] docbook-slides: FTBFS: dh_installxmlcatalogs: Unexpected 
debhelper version format
Bug #837620 [xml-core] w3-dtd-mathml: FTBFS: dh_installxmlcatalogs: Unexpected 
debhelper version format
Bug #837745 [xml-core] sgml-data: FTBFS: dh_installxmlcatalogs: Unexpected 
debhelper version format
Added indication that 837618 affects src:dia
Added indication that 837620 affects src:dia
Added indication that 837745 affects src:dia
>
End of message, stopping processing here.

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

Bug#838320: installation-reports: debian stretch (testing) installer freezes on the laptop with Intel Celeron N2840 CPU

[Geert Stappers]

Control: -1 moreinfo
Stop

On Mon, Sep 19, 2016 at 11:03:26PM +0300, Oksana Andrusiv wrote:
> 
> The installation of the base system hangs.
> The very last message in log console is "installed discover".
> The issue was reproduced in 100% of attempts with and without network mirror.
> 
> The debian 8 is currently in use on the same laptop thus I suppose it is a new
> problem.

Good that the new problem is being reported.

Please boot with 'priority=low' to get more messages
and report back..

See https://www.debian.org/releases/stretch/arm64/ch05s03.html.en for additional
information.


Groeten
Geert Stappers
-- 
Leven en laten leven

Processed: Re: Bug#836759: proftpd-dfsg: please drop the build dependency on hardening-wrapper

[Debian Bug Tracking System]

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

> tags 836759 + pending
Bug #836759 [proftpd-dfsg] proftpd-dfsg: please drop the build dependency on 
hardening-wrapper
Added tag(s) pending.
> stop
Stopping processing here.

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

Bug#836759: proftpd-dfsg: please drop the build dependency on hardening-wrapper

[Hilmar Preuße]

tags 836759 + pending
stop

On 19.09.2016 19:29, Niels Thykier wrote:
> On Sat, 17 Sep 2016 22:36:20 +0200 Hilmar Preusse  wrote:

Hi,

>> Is it OK to simply remove that check? Is there an replacement for
>> hardening-check?
>>
> Hi Hilmar :)
> 
> I believe you can just remove that check.
> 
Done in git, tag pending.

> As for a replacement, lintian will still implement the hardening-no-*
> tags, which were based on the code from hardening-check.
> 
Hmm: lintian still depends on hardening-includes. Not my problem. ;-)

Hilmar
-- 
http://www.hilmar-preusse.de.vu/   #206401 http://counter.li.org

Bug#837257: marked as done (rt-authen-externalauth: FTBFS: build-dependency not installable: request-tracker4)

[Debian Bug Tracking System]

Your message dated Mon, 19 Sep 2016 22:14:28 +0200
with message-id <057962eb-7aca-d42d-4ed0-8bd693f31...@cryptography.ch>
and subject line Re: Bug#837257: rt-authen-externalauth: FTBFS: 
build-dependency not installable: request-tracker4
has caused the Debian Bug report #837257,
regarding rt-authen-externalauth: FTBFS: build-dependency not installable: 
request-tracker4
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.)


-- 
837257: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=837257
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: rt-authen-externalauth
Version: 0.25-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):
> +--+
> | Install package build dependencies  
>  |
> +--+
> 
> 
> Setup apt archive
> -
> 
> Merged Build-Depends: debhelper (>= 9), libcgi-pm-perl | perl-modules, 
> libdbi-perl, libnet-ldap-perl, libnet-ssleay-perl, request-tracker4
> Filtered Build-Depends: debhelper (>= 9), libcgi-pm-perl, libdbi-perl, 
> libnet-ldap-perl, libnet-ssleay-perl, request-tracker4
> dpkg-deb: building package 
> 'sbuild-build-depends-rt-authen-externalauth-dummy' in 
> '/<>/resolver-fr7sY7/apt_archive/sbuild-build-depends-rt-authen-externalauth-dummy.deb'.
> dpkg-scanpackages: warning: Packages in archive but missing from override 
> file:
> dpkg-scanpackages: warning:   
> sbuild-build-depends-rt-authen-externalauth-dummy
> dpkg-scanpackages: info: Wrote 1 entries to output Packages file.
> Ign:1 copy:/<>/resolver-fr7sY7/apt_archive ./ InRelease
> Get:2 copy:/<>/resolver-fr7sY7/apt_archive ./ Release [957 B]
> Ign:3 copy:/<>/resolver-fr7sY7/apt_archive ./ Release.gpg
> Get:4 copy:/<>/resolver-fr7sY7/apt_archive ./ Sources [405 B]
> Get:5 copy:/<>/resolver-fr7sY7/apt_archive ./ Packages [484 B]
> Fetched 1846 B in 0s (0 B/s)
> Reading package lists...
> W: No sandbox user '_apt' on the system, can not drop privileges
> Reading package lists...
> 
> Install rt-authen-externalauth build dependencies (apt-based resolver)
> --
> 
> Installing build dependencies
> Reading package lists...
> Building dependency tree...
> Reading state information...
> Some packages could not be installed. This may mean that you have
> requested an impossible situation or if you are using the unstable
> distribution that some required packages have not yet been created
> or been moved out of Incoming.
> The following information may help to resolve the situation:
> 
> The following packages have unmet dependencies:
>  sbuild-build-depends-rt-authen-externalauth-dummy : Depends: 
> request-tracker4 but it is not going to be installed
> E: Unable to correct problems, you have held broken packages.
> apt-get failed.

The full build log is available from:
   
http://aws-logs.debian.net/2016/09/10/rt-authen-externalauth_0.25-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 ---
Hi Lucas

I'm closing this bug as request-tracker4 is installable again.

Regards,
Tom--- End Message ---

Bug#838047: Confirmed: breaks *all* tablets

[Thomas Renard]

Very grave: it breaks Lenovo Yoga Laptops because they have a buildin
wacom display!

Fortunately Wayland can be used as fallback...

Bug#838320: installation-reports: debian stretch (testing) installer freezes on the laptop with Intel Celeron N2840 CPU

[Oksana Andrusiv]

Package: installation-reports
Severity: critical
Tags: d-i
Justification: breaks the whole system

Dear Maintainer,

The installation of the base system hangs.
The very last message in log console is "installed discover".
The issue was reproduced in 100% of attempts with and without network mirror.

Used hardware: Lenovo Ideapad 100 with Intel Celeron N2840 CPU and RAM 4Gb.
Used image: netinstall for amd64 (weekly build from September 19, 2016).

The system was successfuly installed from the same image as guest into Virtual
Box.
The debian 8 is currently in use on the same laptop thus I suppose it is a new
problem.



-- System Information:
Debian Release: 8.6
  APT prefers stable-updates
  APT policy: (500, 'stable-updates'), (500, 'stable')
Architecture: i386 (i686)

Kernel: Linux 3.16.7-ckt11 (SMP w/2 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)

Bug#836588: [Cupt-devel] Bug#836588: Bug#836588: cupt: FTBFS on armel/armhf: test failures

[Eugene V. Lyubimkin]

On 18.09.2016 22:40, Eugene V. Lyubimkin wrote:
> Thank you. Turned out it is reproducible in release build (at the least on 
> armel porterbox), but not in debug build.
> 
> I'll look into it.

Ok, something fishy is going on with lambda captures. I believe I found an 
issue in either std::function or GCC
optimizer. Looks like a captured value ("this" in this case) is uninitialized 
or corrupted, but only if previous lambda
captures a certain amount of variables, no matter was it called or not. Ugh. I 
managed to reduce
the code to the following small example:

(sid_armhf-dchroot)jackyf@harris:~/smalltests/small-std-function-arm$ cat hm.cpp
#include 
#include 

struct C
{
void doCb()
{
size_t dummy_a = 1;

std::cout << "Outside: " << this << std::endl;
std::function f;
f = [this, _a]()
{};
f = [this]()
{
std::cout << "Inside: " << this << std::endl;
};
f();
}
};

int main()
{
C c;
c.doCb();
}

(sid_armhf-dchroot)jackyf@harris:~/smalltests/small-std-function-arm$ cat 
Makefile
all:
g++ -O2 -Wall -Wextra hm.cpp -o hm.e
(sid_armhf-dchroot)jackyf@harris:~/smalltests/small-std-function-arm$ ./hm.e
Outside: 0xbeaeb5f4
Inside: 0x2
(sid_armhf-dchroot)jackyf@harris:~/smalltests/small-std-function-arm$ 
~/valgrind/valgrind-3.12.0~svn20160714
/vg-in-place ./hm.e
==9628== Memcheck, a memory error detector
==9628== Copyright (C) 2002-2015, and GNU GPL'd, by Julian Seward et al.
==9628== Using Valgrind-3.12.0.SVN and LibVEX; rerun with -h for copyright info
==9628== Command: ./hm.e
==9628==
Outside: 0xbdb6a454
==9628== Use of uninitialised value of size 4
==9628==at 0x4916BF6: ??? (in 
/usr/lib/arm-linux-gnueabihf/libstdc++.so.6.0.22)
==9628==
==9628== Conditional jump or move depends on uninitialised value(s)
==9628==at 0x4916BFC: ??? (in 
/usr/lib/arm-linux-gnueabihf/libstdc++.so.6.0.22)
==9628==
==9628== Conditional jump or move depends on uninitialised value(s)
==9628==at 0x49179FA: std::ostreambuf_iterator std::num_put 
>::_M_insert_int(std::ostreambuf_iterator, std::ios_base&, char, unsigned long) const (in 
/usr/lib/arm-linux-gnueabihf/libstdc++.so.6.0.22)
==9628==by 0x4917AC5: std::num_put
>::do_put(std::ostreambuf_iterator, 
>std::ios_base&, char, void const*) const (in
/usr/lib/arm-linux-gnueabihf/libstdc++.so.6.0.22)
==9628==by 0x491FDA3: std::ostream& std::ostream::_M_insert(void const*) (in
/usr/lib/arm-linux-gnueabihf/libstdc++.so.6.0.22)
==9628==
Inside: 0x2
==9628==
==9628== HEAP SUMMARY:
==9628== in use at exit: 0 bytes in 0 blocks
==9628==   total heap usage: 2 allocs, 2 frees, 21,248 bytes allocated
==9628==
==9628== All heap blocks were freed -- no leaks are possible
==9628==
==9628== For counts of detected and suppressed errors, rerun with: -v
==9628== Use --track-origins=yes to see where uninitialised values come from
==9628== ERROR SUMMARY: 3 errors from 3 contexts (suppressed: 0 from 0)

Processed (with 5 errors): Re: big obnoxious bug merger

[Debian Bug Tracking System]

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

> retitle 838050 segfault kills gnome-shell, all graphics tablets
Bug #838050 [libmutter0i] libmutter causes gdm3's gnome-shell to segfault in
Bug #838047 [libmutter0i] libwacom2: segfault in libwacom from gnome-shell
Changed Bug title to 'segfault kills gnome-shell, all graphics tablets' from 
'libmutter causes gdm3's gnome-shell to segfault in'.
Changed Bug title to 'segfault kills gnome-shell, all graphics tablets' from 
'libwacom2: segfault in libwacom from gnome-shell'.
> done
Unknown command or malformed arguments to command.
> On 19 September 2016 at 20:02, Andrew Chadwick  wrote:
Unknown command or malformed arguments to command.
> > reassign 838047 libmutter0i 3.21.92-1
Unknown command or malformed arguments to command.
> > reassign 838050 libmutter0i 3.21.92-1
Unknown command or malformed arguments to command.
> > severity 838047 grave
Unknown command or malformed arguments to command.
Too many unknown commands, stopping here.

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

Bug#838248: unadf: details of CVE-2016-1243 and CVE-2016-1244

[Tuomas Räsänen]

Hi,

Here's details of these vulnerabilities for the curious:

CVE-2016-1243
=

  void extractTree(struct Volume *vol, struct List* tree, char *path, unsigned 
char *extbuf,
   BOOL pflag, BOOL qflag)
  {
  struct Entry* entry;
  char *buf;
  char sysbuf[200];
  
  while(tree) {
  entry = (struct Entry*)tree->content;
  if (entry->type==ST_DIR) {
  buf = NULL;
  if (strlen(path)>0) {
  buf=(char*)malloc(strlen(path)+1+strlen(entry->name)+1);
  if (!buf) return;
  sprintf(buf,"%s%c%s",path,DIRSEP,entry->name);
  sprintf(sysbuf,"%s %s",MKDIR,buf);

Here, sysbuf can be caused to overflow for example by giving an .adf
archive which has a file with very long name and/or path.

CVE-2016-1244
=

When unadf extracts .adf file, it creates directory paths by executing
mkdir via system(), but does not sanitize pathname strings in any
way. If the user can be tricked to extract specially crafted .adf
file, the attacker can execute arbitrary code with privileges of the
user.

As a proof of concept, I have crafted a file which executes 'ls' when
unpacked by vulnerable unadf: http://tmp.tjjr.fi/boom.adf

Action log:

  $ unadf boom.adf
  unADF v1.0 : a unzip like for .ADF files, powered by ADFlib (v0.7.11a - 
January 20th, 2007)

  Device : Floppy DD. Cylinders = 80, Heads = 2, Sectors = 11. Volumes = 1
  Volume : Floppy 880 KBytes, "Work" between sectors [0-1759]. OFS . Filled at 
0.3%.

  x - somedir;ls/
  adflib.dswAUTHORS.txt  boom.adf  CHANGES.txt  debian  Docs
dynunadf.dsp  FilesToInstall  Lib   README.txt  somedir
staticunadf.dsp
  adfwrapper.h  Bin  Boot  COPYING.txt  Demodynlib.dsp  Faq 
  gen_spec.sh Makefile  snip.c  staticlib.dsp


--
Tuomas

Bug#838050: Patched upstream

[Andrew Chadwick]

Apologies for the big messy merge.

Upstream now have a patch for this, currently pending review, which
applies cleanly to Debian mutter 3.21.92-1 and fixes the knock-on
problems in gnome-shell etc.

https://bugzilla.gnome.org/show_bug.cgi?id=771628
https://bugzilla.gnome.org/attachment.cgi?id=335863=diff

With my patched local build, all the hardware I've tested now works
and doesn't crash gnome-shell in wayland or xorg.

-- 
Andrew Chadwick

Processed: Affects 832077

[Debian Bug Tracking System]

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

> affects 832077 gnome-terminal
Bug #832077 [libgtk-3-0] GTK+ 3.21 causes application redraw issues and 
warnings ("is drawn without a current allocation")
Bug #836426 [libgtk-3-0] GTK+ 3.21 causes application redraw issues and 
warnings ("is drawn without a current allocation")
Added indication that 832077 affects gnome-terminal
Added indication that 836426 affects gnome-terminal
> thanks
Stopping processing here.

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

Processed: tagging 834914

[Debian Bug Tracking System]

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

> tags 834914 + fixed-upstream
Bug #834914 [src:libur-perl] libur-perl: FTBFS too much often (Failed 1/269 
test programs)
Added tag(s) fixed-upstream.
> thanks
Stopping processing here.

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

Bug#837914: marked as done (esys-particle: FTBFS due to test failures)

[Debian Bug Tracking System]

Your message dated Mon, 19 Sep 2016 19:03:51 +
with message-id 
and subject line Bug#837914: fixed in esys-particle 2.3.4+dfsg1-3
has caused the Debian Bug report #837914,
regarding esys-particle: FTBFS due to test 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.)


-- 
837914: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=837914
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: esys-particle
Version: 2.3.4+dfsg1-2
Severity: serious
Justification: makes the package in question unusable or mostly so
Control: block 836917 by -1

Dear Maintainer,


The upload of openmpi (2.0.1-3) to unstable has triggered an
uncoordinated transition (#836917). Unfortunately your package FTBFS due
to test failures:

 cd /«BUILDDIR»/esys-particle-2.3.4+dfsg1/debian/test; mpirun 
--allow-run-as-root -np 3 
/«BUILDDIR»/esys-particle-2.3.4+dfsg1/debian/esys-particle/usr/bin/esysparticle 
compression.py; cat nbons.dat; cat ekin.dat; cat epot.dat
 [babin:06791] PMIX ERROR: INVALID-CREDENTIAL in file 
src/server/pmix_server_listener.c at line 540
 [babin:06796] PMIX ERROR: UNREACHABLE in file src/client/pmix_client.c at line 
983
 [babin:06796] PMIX ERROR: UNREACHABLE in file src/client/pmix_client.c at line 
199
 *** An error occurred in MPI_Init
 *** on a NULL communicator
 *** MPI_ERRORS_ARE_FATAL (processes in this communicator will now abort,
 ***and potentially your MPI job)
 [babin:6796] Local abort before MPI_INIT completed completed successfully, but 
am not able to aggregate error messages, and not able to guarantee that all 
other processes were killed!
 --
 It looks like MPI_INIT failed for some reason; your parallel process is
 likely to abort.  There are many reasons that a parallel process can
 fail during MPI_INIT; some of which are due to configuration or environment
 problems.  This failure appears to be an internal failure; here's some
 additional information (which may only be relevant to an Open MPI
 developer):

   ompi_mpi_init: ompi_rte_init failed
   --> Returned "(null)" (-43) instead of "Success" (0)
 --
 ---
 Primary job  terminated normally, but 1 process returned
 a non-zero exit code.. Per user-direction, the job has been aborted.
 ---
 --
 mpirun detected that one or more processes exited with non-zero status, thus 
causing
 the job to be terminated. The first process to do so was:

   Process name: [[38239,1],0]
   Exit code:1
 --
 cat: nbons.dat: No such file or directory
 cat: ekin.dat: No such file or directory
 cat: epot.dat: No such file or directory

Kind Regards,

Bas
--- End Message ---
--- Begin Message ---
Source: esys-particle
Source-Version: 2.3.4+dfsg1-3

We believe that the bug you reported is fixed in the latest version of
esys-particle, 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.
Anton Gladky  (supplier of updated esys-particle 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: Mon, 19 Sep 2016 20:44:49 +0200
Source: esys-particle
Binary: esys-particle
Architecture: source
Version: 2.3.4+dfsg1-3
Distribution: unstable
Urgency: medium
Maintainer: Debian Science Maintainers 

Changed-By: Anton Gladky 
Description:
 esys-particle - Software for particle-based numerical modelling. MPI version.
Closes: 837914
Changes:
 esys-particle (2.3.4+dfsg1-3) unstable; urgency=medium
 .
   * [38e17b8] Temporarly disable build-test. (Closes: #837914)
Checksums-Sha1:
 8c7efe3f091762828e72bd7281f882203553d42f 2379 esys-particle_2.3.4+dfsg1-3.dsc
 f542ee5965b7078b34714a200edbe53d76e899f5 563832 

Processed (with 1 error): big obnoxious bug merger

[Debian Bug Tracking System]

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

> reassign 838047 libmutter0i 3.21.92-1
Bug #838047 [libwacom2] libwacom2: segfault in libwacom from gnome-shell
Bug reassigned from package 'libwacom2' to 'libmutter0i'.
No longer marked as found in versions libwacom/0.19-1.
Ignoring request to alter fixed versions of bug #838047 to the same values 
previously set
Bug #838047 [libmutter0i] libwacom2: segfault in libwacom from gnome-shell
Marked as found in versions mutter/3.21.92-1.
> reassign 838050 libmutter0i 3.21.92-1
Bug #838050 [gnome-shell] gnome-shell: gdm doesn't start due to a problem with 
gnome-shell crashing in libwacom2
Bug reassigned from package 'gnome-shell' to 'libmutter0i'.
No longer marked as found in versions gnome-shell/3.21.92-1.
Ignoring request to alter fixed versions of bug #838050 to the same values 
previously set
Bug #838050 [libmutter0i] gnome-shell: gdm doesn't start due to a problem with 
gnome-shell crashing in libwacom2
Marked as found in versions mutter/3.21.92-1.
> severity 838047 grave
Bug #838047 [libmutter0i] libwacom2: segfault in libwacom from gnome-shell
Severity set to 'grave' from 'critical'
> affects 838050 + gnome-shell gnome-session gdm3 xserver-xorg xwayland 
> libwacom2
Bug #838050 [libmutter0i] gnome-shell: gdm doesn't start due to a problem with 
gnome-shell crashing in libwacom2
Added indication that 838050 affects gnome-shell, gnome-session, gdm3, 
xserver-xorg, and xwayland
> affects 838047 + gnome-shell gnome-session gdm3 xserver-xorg xwayland 
> libwacom2
Bug #838047 [libmutter0i] libwacom2: segfault in libwacom from gnome-shell
Added indication that 838047 affects gdm3, xserver-xorg, xwayland, and libwacom2
> retitle 838050 libmutter causes gdm3's gnome-shell to segfault in
Bug #838050 [libmutter0i] gnome-shell: gdm doesn't start due to a problem with 
gnome-shell crashing in libwacom2
Changed Bug title to 'libmutter causes gdm3's gnome-shell to segfault in' from 
'gnome-shell: gdm doesn't start due to a problem with gnome-shell crashing in 
libwacom2'.
> libwacom2 when a graphics tablet is plugged in
Unknown command or malformed arguments to command.
> forwarded 838050 https://bugzilla.gnome.org/show_bug.cgi?id=771628
Bug #838050 [libmutter0i] libmutter causes gdm3's gnome-shell to segfault in
Ignoring request to change the forwarded-to-address of bug#838050 to the same 
value
> forcemerge 838050 838047
Bug #838050 [libmutter0i] libmutter causes gdm3's gnome-shell to segfault in
Bug #838047 [libmutter0i] libwacom2: segfault in libwacom from gnome-shell
Set Bug forwarded-to-address to 
'https://bugzilla.gnome.org/show_bug.cgi?id=771628'.
Removed indication that 838047 affects xserver-xorg, gdm3, gnome-shell, 
xwayland, libwacom2, and gnome-session
Added indication that 838047 affects 
gnome-session,libwacom2,gimp,xserver-xorg,mypaint,gdm3,gnome-shell,xwayland
Merged 838047 838050
> tags 838050 + patch
Bug #838050 [libmutter0i] libmutter causes gdm3's gnome-shell to segfault in
Bug #838047 [libmutter0i] libwacom2: segfault in libwacom from gnome-shell
Added tag(s) patch.
Added tag(s) patch.
> thanks
Stopping processing here.

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

Bug#837378: marked as done (sidplay-libs FTBFS on arm64: gcc-6 narrowing conversions)

[Debian Bug Tracking System]

Your message dated Mon, 19 Sep 2016 18:51:22 +
with message-id 
and subject line Bug#837378: fixed in sidplay-libs 2.1.1-15
has caused the Debian Bug report #837378,
regarding sidplay-libs FTBFS on arm64: gcc-6 narrowing conversions
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.)


-- 
837378: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=837378
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: sidplay-libs
Version: 2.1.1-14
Severity: serious
User: helm...@debian.org
Usertags: rebootstrap

I noticed that sidplay-libs fails to cross build from source, because it
encounters narrowing conversion issues specific to arm64. A native build
confirmed the failure and its build log is attached. The gist is:

| libtool: compile:  aarch64-linux-gnu-g++ -DHAVE_CONFIG_H -g -O2 -DHAVE_UNIX 
-I../../include -I../../include/sidplay -MT xsid.lo -MD -MP -MF .deps/xsid.Tpo 
-c xsid.cpp  -fPIC -DPIC -o .libs/xsid.o
| xsid.cpp:101:1: error: narrowing conversion of ''\200'' from 'char' to 
'int8_t {aka signed char}' inside { } [-Wnarrowing]
|  };
|  ^
| xsid.cpp:101:1: error: narrowing conversion of ''\224'' from 'char' to 
'int8_t {aka signed char}' inside { } [-Wnarrowing]
| xsid.cpp:101:1: error: narrowing conversion of ''\251'' from 'char' to 
'int8_t {aka signed char}' inside { } [-Wnarrowing]
| xsid.cpp:101:1: error: narrowing conversion of ''\274'' from 'char' to 
'int8_t {aka signed char}' inside { } [-Wnarrowing]
| xsid.cpp:101:1: error: narrowing conversion of ''\316'' from 'char' to 
'int8_t {aka signed char}' inside { } [-Wnarrowing]
| xsid.cpp:101:1: error: narrowing conversion of ''\341'' from 'char' to 
'int8_t {aka signed char}' inside { } [-Wnarrowing]
| xsid.cpp:101:1: error: narrowing conversion of ''\362'' from 'char' to 
'int8_t {aka signed char}' inside { } [-Wnarrowing]

Helmut
dpkg-buildpackage: info: source package sidplay-libs
dpkg-buildpackage: info: source version 2.1.1-14
dpkg-buildpackage: info: source distribution unstable
dpkg-buildpackage: info: source changed by Laszlo Boszormenyi (GCS) 

 dpkg-source --before-build sidplay-libs-2.1.1
dpkg-buildpackage: info: host architecture arm64
 fakeroot debian/rules clean
dh_testdir
dh_testroot
[ ! -f Makefile ] || /usr/bin/make distclean
rm -f confdefs.h config.log
# remove autogenerated files
find . -name aclocal.m4 -o -name configure -o -name configure.lineno \
-o -name config.guess -o -name config.h.in \
-o -name config.log -o -name config.status -o \
-name config.sub -o -name depcomp -o -name install-sh -o \
-name libtool -o -name ltmain.sh -o -name missing -o \
-name mkinstalldirs -o -name stamp-h1 -o -name INSTALL -o \
-name Makefile -o -name Makefile.in | xargs rm -f
rm -f libsidplay/unix/sidint.h
rm -f configure-stamp build-stamp 
dh_clean
 dpkg-source -b sidplay-libs-2.1.1
dpkg-source: info: using source format '3.0 (quilt)'
dpkg-source: info: building sidplay-libs using existing 
./sidplay-libs_2.1.1.orig.tar.gz
dpkg-source: warning: ignoring deletion of file Makefile.in, use 
--include-removal to override
dpkg-source: warning: ignoring deletion of file configure, use 
--include-removal to override
dpkg-source: warning: ignoring deletion of file aclocal.m4, use 
--include-removal to override
dpkg-source: warning: ignoring deletion of file libsidplay/Makefile.in, use 
--include-removal to override
dpkg-source: warning: ignoring deletion of file libsidplay/configure, use 
--include-removal to override
dpkg-source: warning: ignoring deletion of file libsidplay/aclocal.m4, use 
--include-removal to override
dpkg-source: warning: ignoring deletion of file libsidplay/INSTALL, use 
--include-removal to override
dpkg-source: warning: ignoring deletion of file libsidplay/src/Makefile.in, use 
--include-removal to override
dpkg-source: warning: ignoring deletion of file 
libsidplay/src/sidtune/Makefile.in, use --include-removal to override
dpkg-source: warning: ignoring deletion of file 
libsidplay/src/sid6526/Makefile.in, use --include-removal to override
dpkg-source: warning: ignoring deletion of file 
libsidplay/src/xsid/Makefile.in, use --include-removal to override
dpkg-source: warning: ignoring deletion of file 
libsidplay/src/mos656x/Makefile.in, use --include-removal to override
dpkg-source: warning: ignoring deletion of file 
libsidplay/src/mos6510/Makefile.in, use --include-removal to override
dpkg-source: warning: ignoring deletion of file libsidplay/src/c64/Makefile.in, 
use --include-removal to override

Bug#811672: marked as done (FTBFS with GCC 6: cannot convert x to y)

[Debian Bug Tracking System]

Your message dated Mon, 19 Sep 2016 18:36:15 +
with message-id 
and subject line Bug#811672: fixed in qt4-perl 4.8.4-1.3
has caused the Debian Bug report #811672,
regarding FTBFS with GCC 6: cannot convert x to y
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.)


-- 
811672: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=811672
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: qt4-perl
Version: 4.8.4-1.2
Severity: important
User: debian-...@lists.debian.org
Usertags: ftbfs-gcc-6 gcc-6-cannot-convert

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

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

> sbuild (Debian sbuild) 0.67.0 (26 Dec 2015) on dl580gen9-02.hlinux
...
> [  5%] Building CXX object qtcore/src/CMakeFiles/perlqtcore4.dir/util.cpp.o
> cd /<>/obj-x86_64-linux-gnu/qtcore/src && /usr/bin/g++   -DDEBUG 
> -DPERLQTDEBUG -Dperlqtcore4_EXPORTS -I/usr/include/smoke 
> -I/usr/include/qt4/QtDesigner -I/usr/include/qt4/QtDeclarative 
> -I/usr/include/qt4/QtScriptTools -I/usr/include/qt4/QtDBus 
> -I/usr/include/qt4/QtXml -I/usr/include/qt4/QtSql 
> -I/usr/include/qt4/QtNetwork -I/usr/include/qt4/QtXmlPatterns 
> -I/usr/include/qt4/QtHelp -I/usr/include/qt4/QtUiTools 
> -I/usr/include/qt4/QtTest -I/usr/include/qt4/QtScript 
> -I/usr/include/qt4/QtSvg -I/usr/include/qt4/Qt3Support 
> -I/usr/include/qt4/QtGui -I/usr/include/qt4/QtCore 
> -I/usr/share/qt4/mkspecs/default -I/usr/include/qt4 -I/<>/src 
> -I/<>/qtcore/src -I/usr/lib/x86_64-linux-gnu/perl/5.22/CORE  
> -D_REENTRANT -D_GNU_SOURCE -DDEBIAN -fwrapv -fno-strict-aliasing -pipe 
> -I/usr/local/include -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64 -fPIC   -o 
> CMakeFiles/perlqtcore4.dir/util.cpp.o -c /<>/qtcore/src/util.cpp
> /<>/qtcore/src/util.cpp: In function 'void 
> XS_AUTOLOAD(PerlInterpreter*, CV*)':
> /<>/qtcore/src/util.cpp:2234:59: error: cannot convert 'bool' to 
> 'void*' in initialization
>  static smokeperl_object nothis = { 0, 0, 0, false };
>^
> 
> qtcore/src/CMakeFiles/perlqtcore4.dir/build.make:141: recipe for target 
> 'qtcore/src/CMakeFiles/perlqtcore4.dir/util.cpp.o' failed
> make[3]: *** [qtcore/src/CMakeFiles/perlqtcore4.dir/util.cpp.o] Error 1

-- 
Martin Michlmayr
Linux for HPE Helion, Hewlett Packard Enterprise
--- End Message ---
--- Begin Message ---
Source: qt4-perl
Source-Version: 4.8.4-1.3

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

Debian distribution maintenance software
pp.
gregor herrmann  (supplier of updated qt4-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: Wed, 14 Sep 2016 19:54:03 +0200
Source: qt4-perl
Binary: libqtcore4-perl libqtgui4-perl libqtxml4-perl libqtnetwork4-perl 
libqttest4-perl
Architecture: source
Version: 4.8.4-1.3
Distribution: unstable
Urgency: medium
Maintainer: Sune Vuorela 
Changed-By: gregor herrmann 
Closes: 811672
Description: 
 libqtcore4-perl - perl bindings for the Qt Core library
 libqtgui4-perl - perl bindings for the Qt Gui library
 libqtnetwork4-perl - perl bindings for the Qt Network library
 libqttest4-perl - perl bindings for the Qt Test library
 libqtxml4-perl - perl bindings for the Qt Xml library
Changes:
 qt4-perl (4.8.4-1.3) unstable; urgency=medium
 .
   * Non-maintainer upload.
   * Fix "FTBFS with GCC 6: cannot convert x to y":
 add patch from upstream bug tracker to properly initialize
 smokeperl_object. (Closes: #811672)
Checksums-Sha1: 
 2d7402b099946929f8c0861e5d1cbf0e0236a46a 2112 qt4-perl_4.8.4-1.3.dsc
 aae4b362e2565ae87f23ca676497b6fecfb585f6 6028 qt4-perl_4.8.4-1.3.debian.tar.xz
Checksums-Sha256: 
 

Bug#834246: marked as done (kicad: FTBFS in testing)

[Debian Bug Tracking System]

Your message dated Mon, 19 Sep 2016 18:07:19 +
with message-id 
and subject line Bug#834246: fixed in kicad 4.0.4+dfsg1-1
has caused the Debian Bug report #834246,
regarding kicad: FTBFS in testing
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.)


-- 
834246: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=834246
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: kicad
Version: 4.0.2+dfsg1-4
Severity: serious

Dear maintainer:

This package fails to build from source in stretch:

-
In file included from
/<>/kicad-4.0.2+dfsg1/common/tool/tool_manager.cpp:46:0:
/<>/kicad-4.0.2+dfsg1/include/tool/coroutine.h:30:38: fatal
error: boost/context/fcontext.hpp: No such file or 
directory
 #include 
   ^
   compilation terminated.
-

Full build logs available here:

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

Thanks.
--- End Message ---
--- Begin Message ---
Source: kicad
Source-Version: 4.0.4+dfsg1-1

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

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Wed, 11 May 2016 16:14:08 +0200
Source: kicad
Binary: kicad kicad-common kicad-doc-en kicad-doc-de kicad-doc-es kicad-doc-fr 
kicad-doc-it kicad-doc-ja kicad-doc-nl kicad-doc-pl
Architecture: source all amd64
Version: 4.0.4+dfsg1-1
Distribution: unstable
Urgency: medium
Maintainer: Georges Khaznadar 
Changed-By: Georges Khaznadar 
Description:
 kicad  - Electronic schematic and PCB design software
 kicad-common - Common files used by kicad
 kicad-doc-de - Kicad help files (German)
 kicad-doc-en - Kicad help files (English)
 kicad-doc-es - Kicad help files (Spanish)
 kicad-doc-fr - Kicad help files (French)
 kicad-doc-it - Kicad help files (Italian)
 kicad-doc-ja - Kicad help files (Japanese)
 kicad-doc-nl - Kicad help files (Dutch)
 kicad-doc-pl - Kicad help files (Polish)
Closes: 811268 819855 826750 833777 834246
Changes:
 kicad (4.0.4+dfsg1-1) unstable; urgency=medium
 .
   * checked that 4.0.2+dfsg1-2~bpo8+1-1 is available. Closes: #811268
   * modified .install files to install kicad.mo files. Closes: #819855
   * applied Graham Inggs' patch. Closes: #834246
   * added a Recommends: for xsltproc. Closes: #826750
   * updated Standards-Version to 3.9.8
   * upgraded to the last upstream version. Closes: #833777
   * added build-dependencies on texlive-lang-cyrillic and texlive-fonts-extra
Checksums-Sha1:
 ad0f5b6f764b5777f31e6b457d56dc7268cc2199 3242 kicad_4.0.4+dfsg1-1.dsc
 b7089b0d57c21b4e7ccd00ab978f05355678334d 91184805 kicad_4.0.4+dfsg1.orig.tar.xz
 87e16ea699cf8d65b61f9a09a2b90522c2ea5cfd 26660 
kicad_4.0.4+dfsg1-1.debian.tar.xz
 f06c1319dadabb9c4c18493b103cc87082785d4e 44381318 
kicad-common_4.0.4+dfsg1-1_all.deb
 6b427b5dc6ebd58681112f69c1bad37fb9468798 91911094 
kicad-dbgsym_4.0.4+dfsg1-1_amd64.deb
 deb13dfdc50d5a5532af436e53237310b43d0167 48917194 
kicad-doc-de_4.0.4+dfsg1-1_all.deb
 4adc90d86ddccb3baf7a2257059ae63d93b36270 44766338 
kicad-doc-en_4.0.4+dfsg1-1_all.deb
 169119540602e450bc307843a60fe9dba87fb81a 45621998 
kicad-doc-es_4.0.4+dfsg1-1_all.deb
 efdd9056280cd005e5ebb4ca3553a9e3ea1df48a 49569936 
kicad-doc-fr_4.0.4+dfsg1-1_all.deb
 51c780fb5acbaec2d4ecd605af1b4a7878cca38e 48361956 
kicad-doc-it_4.0.4+dfsg1-1_all.deb
 93a8f1388e89017d16b9c8eb89dc3c30a20aadb4 44177938 
kicad-doc-ja_4.0.4+dfsg1-1_all.deb
 b8640bb80c749b98f80312b92bd1f1043b0d5da6 5473696 
kicad-doc-nl_4.0.4+dfsg1-1_all.deb
 61ff29b52135df6688a62bf14094b2f7a56bb9a0 46911272 
kicad-doc-pl_4.0.4+dfsg1-1_all.deb
 7643f163fb4b81df5c18540fc0404cca1e8d5aec 13033940 kicad_4.0.4+dfsg1-1_amd64.deb

Bug#838310: keyboard-configuration: user configuration lost + error message from setupcon

[Vincent Lefevre]

Same problem on another machine.

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

Bug#838310: keyboard-configuration: user configuration lost + error message from setupcon

[Vincent Lefevre]

Some additional information. In "journalctl -b" output after reboot:

[...]
Sep 19 19:10:11 zira keyboard-setup.sh[401]: cannot open file /tmp/tmpkbd.qR4ecU
[...]
Sep 19 19:10:11 zira keyboard-setup.sh[401]: setupcon: The keyboard model is 
unknown, assuming 'pc105'. Keyboard may be configured incorrectly.
[...]
Sep 19 19:10:11 zira console-setup.sh[631]: setupcon: The keyboard model is 
unknown, assuming 'pc105'. Keyboard may be configured incorrectly.
[...]
Sep 19 19:10:11 zira console-setup.sh[631]: setupcon: The keyboard model is 
unknown, assuming 'pc105'. Keyboard may be configured incorrectly.
Sep 19 19:10:11 zira console-setup.sh[631]: setupcon: The keyboard model is 
unknown, assuming 'pc105'. Keyboard may be configured incorrectly.
Sep 19 19:10:11 zira console-setup.sh[631]: setupcon: The keyboard model is 
unknown, assuming 'pc105'. Keyboard may be configured incorrectly.
[...]

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

Bug#833770: [Debichem-devel] Bug#833770: Bug#833770: avogadro: FTBFS with gcc6/boost1.61

[Anton Gladky]

One need to discuss it with Michael.

Anton


2016-09-19 19:11 GMT+02:00 Graham Inggs :
> What about uploading version 1.1.1 from experimental to unstable?

Bug#838310: keyboard-configuration: user configuration lost + error message from setupcon

[Vincent Lefevre]

Package: keyboard-configuration
Version: 1.149
Severity: grave
Justification: causes non-serious data loss

Just after the upgrade of keyboard-configuration from 1.148 to 1.149,
I could see that my previous configuration was lost. More precisely,
config.dat changed in the following way:

Index: config.dat
===
--- config.dat  (revision 92179)
+++ config.dat  (revision 92180)
@@ -512,7 +512,7 @@
 
 Name: keyboard-configuration/modelcode
 Template: keyboard-configuration/modelcode
-Value: pc105
+Value: 
 Owners: d-i, keyboard-configuration
 Flags: seen
 
@@ -549,6 +549,9 @@
 Template: keyboard-configuration/unsupported_config_layout
 Value: true
 Owners: d-i, keyboard-configuration
+Variables:
+ XKBLAYOUT = gb
+ XKBVARIANT = 
 
 Name: keyboard-configuration/unsupported_config_options
 Template: keyboard-configuration/unsupported_config_options
@@ -581,7 +584,7 @@
 
 Name: keyboard-configuration/xkb-keymap
 Template: keyboard-configuration/xkb-keymap
-Value: gb
+Value: us
 Owners: d-i, keyboard-configuration
 Flags: seen
 

and /etc/default/keyboard changed in the following way:

Index: etc/default/keyboard
===
--- etc/default/keyboard(revision 92179)
+++ etc/default/keyboard(revision 92180)
@@ -2,7 +2,7 @@
 
 # Consult the keyboard(5) manual page.
 
-XKBMODEL="pc105"
+XKBMODEL=""
 XKBLAYOUT="gb"
 XKBVARIANT=""
 XKBOPTIONS=""

I don't know the possible consequences, though. The
/usr/share/doc/keyboard-configuration/changelog.gz file just says:

console-setup (1.149) unstable; urgency=medium

  [ Updated translations ]
  * Danish (da.po) by Joe Hansen

 -- Christian Perrier   Sun, 18 Sep 2016 17:53:38 +0200

Moreover, I can see in the /var/log/apt/term.log file after an
upgrade of the Linux kernel and the nvidia packages:

[...]
Processing triggers for libc-bin (2.24-3) ...
Processing triggers for glx-alternative-nvidia (0.7.3) ...
Processing triggers for update-glx (0.7.3) ...
Processing triggers for glx-alternative-nvidia (0.7.3) ...
Processing triggers for libc-bin (2.24-3) ...
Processing triggers for initramfs-tools (0.125) ...
update-initramfs: Generating /boot/initrd.img-4.7.0-1-amd64
setupcon: The keyboard model is unknown, assuming 'pc105'. Keyboard may be 
configured incorrectly.
Log ended: 2016-09-19  19:08:59

Note: I have

-rw-r--r-- 1 root root 145 2016-09-19 19:03:19 /etc/default/keyboard

Thus this file was modified when keyboard-configuration was upgraded
(and before this upgrade of the Linux kernel and the nvidia packages).
This error message is just a consequence of this bug.

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

Kernel: Linux 4.7.0-1-amd64 (SMP w/8 CPU cores)
Locale: LANG=POSIX, 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 keyboard-configuration depends on:
ii  debconf 1.5.59
ii  liblocale-gettext-perl  1.07-3

keyboard-configuration recommends no packages.

keyboard-configuration suggests no packages.

Versions of packages console-setup depends on:
ii  console-setup-linux  1.149
ii  debconf  1.5.59
ii  xkb-data 2.17-1

Versions of packages console-setup suggests:
ii  locales   2.24-3
ii  lsb-base  9.20160629

Versions of packages console-setup-linux depends on:
ii  init-system-helpers  1.44
ii  initscripts  2.88dsf-59.8
ii  kbd  2.0.3-2

Versions of packages console-setup-linux suggests:
ii  console-setup  1.149

Versions of packages keyboard-configuration is related to:
pn  console-common
pn  console-data  
pn  console-tools 
pn  gnome-control-center  
ii  kbd   2.0.3-2
ii  systemd   231-6

-- debconf information:
* keyboard-configuration/optionscode:
* keyboard-configuration/altgr: The default for the keyboard layout
  console-setup/fontface47: Fixed
  keyboard-configuration/unsupported_layout: true
  console-setup/framebuffer_only:
* keyboard-configuration/model: Generic 105-key (Intl) PC
  console-setup/fontsize: 8x16
  console-setup/guess_font:
* keyboard-configuration/store_defaults_in_debconf_db: true
  debian-installer/console-setup-udeb/title:
  console-setup/codeset47: # Latin1 and Latin5 - western Europe and Turkic 
languages
  keyboard-configuration/ctrl_alt_bksp: false
  keyboard-configuration/unsupported_config_options: true
  console-setup/use_system_font:
* keyboard-configuration/toggle: No toggling
* keyboard-configuration/layoutcode: gb
  keyboard-configuration/unsupported_options: true
* keyboard-configuration/variantcode:
* keyboard-configuration/variant: English (UK)
* keyboard-configuration/switch: 

Bug#836759: proftpd-dfsg: please drop the build dependency on hardening-wrapper

[Niels Thykier]

On Sat, 17 Sep 2016 22:36:20 +0200 Hilmar Preusse  wrote:
> On 05.09.16 Matthias Klose (d...@debian.org) wrote:
> 
> Hi Matthias,
> 
> > [...]
> Is it OK to simply remove that check? Is there an replacement for
> hardening-check?
> 
> Thanks,
>   Hilmar
> 
> [1] 
> https://wiki.debian.org/HardeningWalkthrough#rules_files_based_on_standard_debhelper_or_hand-written_rules_files
> -- 
> sigfault

Hi Hilmar :)

I believe you can just remove that check.

As for a replacement, lintian will still implement the hardening-no-*
tags, which were based on the code from hardening-check.

Thanks,
~Niels

Bug#836755: marked as done (gpick: please drop the build dependency on hardening-wrapper)

[Debian Bug Tracking System]

Your message dated Mon, 19 Sep 2016 17:19:09 +
with message-id 
and subject line Bug#836755: fixed in gpick 0.2.5-2
has caused the Debian Bug report #836755,
regarding gpick: please drop the build dependency on hardening-wrapper
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.)


-- 
836755: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=836755
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: gpick
Version: 0.2.5-1
Severity: important
Tags: sid stretch
User: debian-...@lists.debian.org
Usertags: hardening-wrapper

This package builds using the hardening-includes package, which
is now replaced by dpkg-dev's DEB_BUILD_MAINT_OPTIONS settings.

Please consider dropping the build dependency of hardening-includes
and use the DEB_BUILD_MAINT_OPTIONS settings.

The goal is to remove hardening-wrapper for the stretch release.
Discussion about the removal is tracked in https://bugs.debian.org/836162

The severity of this report is likely to be raised before the release,
so that the hardening-wrapper package can be removed for the release.
--- End Message ---
--- Begin Message ---
Source: gpick
Source-Version: 0.2.5-2

We believe that the bug you reported is fixed in the latest version of
gpick, 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.
Elías Alejandro Año Mendoza  (supplier of updated gpick 
package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Format: 1.8
Date: Sun, 18 Sep 2016 22:17:33 -0300
Source: gpick
Binary: gpick
Architecture: source i386
Version: 0.2.5-2
Distribution: unstable
Urgency: medium
Maintainer: Elías Alejandro Año Mendoza 
Changed-By: Elías Alejandro Año Mendoza 
Description:
 gpick  - advanced GTK+ color picker
Closes: 831041 836755
Changes:
 gpick (0.2.5-2) unstable; urgency=medium
 .
   * Updated Standards-Version to 3.9.8
   * Updated hardening build flags (Closes: #836755)
   * debian/patches
 + 01_reproducible_build.patch (Closes: #831041)
   Thanks to Chris Lamb for the patch
 + 02_desktop_file.patch
   Updated desktop file entries
   * debian/control
 + Vcs-* fields updated for https:// usage
 + Homepage field updated
   * debian/watch
 + Updated for check new versions
   * debian/copyright
 + Updated format
Checksums-Sha1:
 335d1a9f5a45931ecad29e2affee136a79dd8ccd 1975 gpick_0.2.5-2.dsc
 2e8f38d605f5540eb0c4c0bef741993569f647d5 4256 gpick_0.2.5-2.debian.tar.xz
 3ce8584c6d15cd81d09ab85094feb7817d912950 3952028 gpick-dbgsym_0.2.5-2_i386.deb
 a5ea51ccea59a20bd604267103d3ab666f8aabf5 308264 gpick_0.2.5-2_i386.deb
Checksums-Sha256:
 125645383605e995fd9defd584bd552447c9a12355fde739faea7133645ea754 1975 
gpick_0.2.5-2.dsc
 0f606558d0d37e2e4d7d10d410e60a97fa1529bad24be132c82d6b97521ac8f0 4256 
gpick_0.2.5-2.debian.tar.xz
 83dfaa7309e79f3fbdb0649a53153b3b498aec729e90b5d0c023f94f460bb684 3952028 
gpick-dbgsym_0.2.5-2_i386.deb
 79d1e67d5f7e9ab9103ead302aa893f1a06bbb8e284853b60ba52780e767bc98 308264 
gpick_0.2.5-2_i386.deb
Files:
 3e6adb307ed4388fdcf51dc1413efbc5 1975 graphics optional gpick_0.2.5-2.dsc
 8e5c3d4c367a9b7dcb21af00cf4f1608 4256 graphics optional 
gpick_0.2.5-2.debian.tar.xz
 4be9a1e25f6a65a5a8f976f89f058429 3952028 debug extra 
gpick-dbgsym_0.2.5-2_i386.deb
 908fa3e734f172e9660bf657814e854d 308264 graphics optional 
gpick_0.2.5-2_i386.deb

-BEGIN PGP SIGNATURE-
Version: GnuPG v1

iQIcBAEBAgAGBQJX4BleAAoJEMnxy/VjUfcZaz4P/1mf6BQiFWa/Y25RIEB/q2kE
4Q+ptzYiBV3PkGYyiulvn1u8TCF6H87jJ9ZBJQbVjla5JD4OxxVCvv5xteYecoqQ
4JFVw0dcNvvyIl10FdRV22BnShntZO/8WoYGZ/VwzAfXwAawMTzZUQFZPDHb+Cyg
rjLQ0gg6+OP7aOhVoL0oTwKpeBF94JsVpdKKEZrN8PyxsLm2M9LG53YuNnXJeMIA
rUfQFe8Mpj9zBJJHKHL6BLHuU3asnS2cQ6uyruHJvwmYQehr+sGClyPDasuvK9Ud
85OqIq7nuLSSlVuro2S/ZWzdSP+ZeUNBDf+RY/dtK94JSL53se5DN4dl8TF0Z9Li
5OKXLN5nToXIqC47SsU6dYPdf8mG3OigdRZvo1R5popgg62UqMXp9i9a3OBEVugY
ISpacdqp3H/a4RZEtnw1+yybVQ+zbNFJpHrf1/vC9udhBlCyP5zy0ZpvI1So7jzB
c9wLdUzsGf/ViYqJW1rwKEPlXfTcn9mSKD8iUXo25MJ5SN7WXNmus5Eb6mws9PQ7

Bug#832840: license-reconcile: diff for NMU version 0.12+nmu1

[gregor herrmann]

On Mon, 19 Sep 2016 00:32:17 +0800, gustavo panizzo (gfa) wrote:

> I've attached the debdiff, I'll push my changes to the git repo after
> the NMU has been uploaded, let me know if you don't agree with any of
> this.

Thanks for your help.

It might be easier to push the changes to the git repo before an
upload, with 0.12 instead of 0.12+nmu1, and we can do a regular tram
upload. -- Whatever you prefer.
 

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: STS: Zeit für uns


signature.asc
Description: Digital Signature

Bug#833770: [Debichem-devel] Bug#833770: Bug#833770: avogadro: FTBFS with gcc6/boost1.61

[Graham Inggs]

On 19 September 2016 at 19:04, Anton Gladky  wrote:
> I really tried, but did not succeed. One need another try.

What about uploading version 1.1.1 from experimental to unstable?

Bug#833770: [Debichem-devel] Bug#833770: avogadro: FTBFS with gcc6/boost1.61

[Anton Gladky]

Hi Emilio,

I really tried, but did not succeed. One need another try.

Regards

Anton


2016-09-19 17:09 GMT+02:00 Emilio Pozuelo Monfort :
> Ping? This is blocking the boost1.58 removal, which in turn is blocking the
> openmpi transition. I'd appreciate it if you could take a look at this.

Bug#838080: marked as done (bacula-director-pgsql: make_catalog_backup fails)

[Debian Bug Tracking System]

Your message dated Mon, 19 Sep 2016 16:53:07 +
with message-id 
and subject line Bug#838080: fixed in bacula 7.4.3+dfsg-7
has caused the Debian Bug report #838080,
regarding bacula-director-pgsql: make_catalog_backup fails
to be marked as done.

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

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


-- 
838080: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=838080
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: bacula-director-pgsql
Version: 7.4.3+dfsg-6
Severity: serious

XXX_DBUSER_XXX is not replaced by the name of the database user in
make_catalog_backup:

user=${2:-XXX_DBUSER_XXX}

consequently, the catalog backup fails.
--- End Message ---
--- Begin Message ---
Source: bacula
Source-Version: 7.4.3+dfsg-7

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

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

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

Debian distribution maintenance software
pp.
Carsten Leonhardt  (supplier of updated bacula package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Mon, 19 Sep 2016 17:55:43 +0200
Source: bacula
Binary: bacula bacula-common bacula-common-sqlite3 bacula-common-pgsql 
bacula-common-mysql bacula-director bacula-director-sqlite3 
bacula-director-mysql bacula-director-pgsql bacula-client bacula-fd 
bacula-server bacula-sd bacula-bscan bacula-console bacula-console-qt
Architecture: source
Version: 7.4.3+dfsg-7
Distribution: unstable
Urgency: high
Maintainer: Debian Bacula Team 
Changed-By: Carsten Leonhardt 
Description:
 bacula - network backup service - metapackage
 bacula-bscan - network backup service - bscan tool
 bacula-client - network backup service - client metapackage
 bacula-common - network backup service - common support files
 bacula-common-mysql - network backup service - MySQL common files
 bacula-common-pgsql - network backup service - PostgreSQL common files
 bacula-common-sqlite3 - network backup service - SQLite v3 common files
 bacula-console - network backup service - text console
 bacula-console-qt - network backup service - Bacula Administration Tool
 bacula-director - network backup service - Director daemon
 bacula-director-mysql - network backup service - MySQL storage for Director
 bacula-director-pgsql - network backup service - PostgreSQL storage for 
Director
 bacula-director-sqlite3 - network backup service - SQLite 3 storage for 
Director
 bacula-fd  - network backup service - file daemon
 bacula-sd  - network backup service - storage daemon
 bacula-server - network backup service - server metapackage
Closes: 838080
Changes:
 bacula (7.4.3+dfsg-7) unstable; urgency=high
 .
   * Handle make_catalog_backup script in postinst of package
 bacula-director, inserting the correct database user (Closes: #838080)
   * Move make_catalog_backup.pl to package bacula-director
Checksums-Sha1:
 c6323bc846a44da05e4234341a5883d61ea35e88 3218 bacula_7.4.3+dfsg-7.dsc
 0ccd9b7f87bf77715a2b49fd1813735237cf5593 63580 
bacula_7.4.3+dfsg-7.debian.tar.xz
Checksums-Sha256:
 ad4ca19893a4e93601e6c4941fffbc024e1c9942159d9872dc9c05013c0e71a9 3218 
bacula_7.4.3+dfsg-7.dsc
 190ef99a528749ea5ab706e540214ef3569b2976ab8efd4a9137667c598b0e65 63580 
bacula_7.4.3+dfsg-7.debian.tar.xz
Files:
 702e92edc1b050bf5b851370770f354b 3218 admin optional bacula_7.4.3+dfsg-7.dsc
 da1c1b49ca3cf7742badd412b29c2fd0 63580 admin optional 
bacula_7.4.3+dfsg-7.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQIcBAEBCgAGBQJX4A6+AAoJEFbggnbEQhZ0zOcQAJ8b6eONGbabbnkkFsIF3Fzj
/498c1Ful6SycfMR3rClrTHByv6FRANxajsiYTgoTkaQTKd0gRmacGFasDMfpuzr
bY6lHFX4pYTDJsopQPswNP/trU0q2gq1HrCosf6SwxtCNhogjZ0RrFCZhYEcLbkT
3JEpK8dktirFPlvliZ5X6tM9c2J5jq8udAjPbmxTdvnWm3DfWLLT594iNDZDQU63
wKh38WYkJDzP/Ke0M0ptp0V9upoiSqyzrf4kkLaQ9ADJDUO+K2FwUtyENIuqbT7C
tA8Cyuc4fGzc9QRcIAxiX2aquRG2J22dSUSum6yp3MJhCUSdq5vs3//rMxV7frrg
y+60k4h/j3Hktf+Aa7OTVof9K8OWB/AbyXAil9Qw8iIQ+mgYn4Cc3wELJun0RbZP
IeEOUmTeJLl9Zff9fkdBWuxnlaji0/RoxN3sSAZhf2COp4/uucWqbpxiR4V0rF6L
iC7Zb1R6qwQXEzEVdL/5MW2Zl0fXdCstlX6YMqqXDnzjX5xeOk4BS91yIYN1vjOc

Bug#836735: marked as done (ruby-aruba: uninitialized constant Aruba::CommandMonitor::Utils)

[Debian Bug Tracking System]

Your message dated Mon, 19 Sep 2016 16:25:55 +
with message-id 
and subject line Bug#836735: fixed in ruby-aruba 0.14.2-2
has caused the Debian Bug report #836735,
regarding ruby-aruba: uninitialized constant Aruba::CommandMonitor::Utils
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.)


-- 
836735: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=836735
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: ruby-aruba
Version: 0.14.2-1
Severity: grave
Tags: upstream
Justification: renders package unusable

Dear Maintainer,

Upstream bug https://github.com/cucumber/aruba/issues/346 still affects debian 
package. This makes ruby-aruba unusable.
--- End Message ---
--- Begin Message ---
Source: ruby-aruba
Source-Version: 0.14.2-2

We believe that the bug you reported is fixed in the latest version of
ruby-aruba, 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.
Hleb Valoshka <375...@gmail.com> (supplier of updated ruby-aruba 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, 05 Sep 2016 13:38:24 +0300
Source: ruby-aruba
Binary: ruby-aruba
Architecture: source
Version: 0.14.2-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Ruby Extras Maintainers 

Changed-By: Hleb Valoshka <375...@gmail.com>
Description:
 ruby-aruba - Cucumber extension for CLI applications
Closes: 836735
Changes:
 ruby-aruba (0.14.2-2) unstable; urgency=medium
 .
   [ Hleb Valoshka ]
   * Team upload.
   * Add patch for removed Utils class usage (Closes: 836735).
 .
   [ Cédric Boutillier ]
   * Add autopkgtest support
 + add 0006-ignore-failing-test-autopkgtest.patch to skig failing test in
   autopkgtest context
Checksums-Sha1:
 cbd46aa5bf45862f35ff43478f14609fc320d7ea 1866 ruby-aruba_0.14.2-2.dsc
 bf09872bbc7cdb2df6eae5ecaba3a3a432dfcc4c 79024 
ruby-aruba_0.14.2-2.debian.tar.xz
Checksums-Sha256:
 a9772e777ea89d71c3cbfb5c5488f2de74092dddf9358e0c646fbed63a5c0b01 1866 
ruby-aruba_0.14.2-2.dsc
 18c533be7f62ba879fd63783492ed5dab86c7e91471463bad6070fb76791 79024 
ruby-aruba_0.14.2-2.debian.tar.xz
Files:
 8b6850e43928b6deeb35fa365b5017d3 1866 ruby optional ruby-aruba_0.14.2-2.dsc
 e8d33d87f34de79cfdfcfe89ee3581f4 79024 ruby optional 
ruby-aruba_0.14.2-2.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQEcBAEBCgAGBQJX3/bmAAoJEImvgrc5zSF6IAcH/22NGVzVCr/+R8QCSXdI5x7R
qgez3zkze5iOCVvMBrwdQojK6lFMMHnvhYnA6aw8MdoMf3dHHDDZPt2sL2ORNm2L
p3NzEPBVOHdVXuh5H4Wsg25tSB/LMMZcC5cRGTmWmxQuUZKfhWvz3vtqPf+GQuvK
l83n0VJfZ10nh2pFcDXheocw9W+qJLSB60r21t0jDRS4t62DQfHmxo6X6nC5WR6W
lXaA3yJGATzhfasgr6BrxXJN69wMQe6FI9lQYsYEem+KzsQkuFsmdpPugbl+W1BD
Ze8/9QWwWwa35pL47HARDXYocK7qNtZVwCeRed03ML7g1QvYod3obYWoMnblJnw=
=hR70
-END PGP SIGNATURE End Message ---

Bug#837229: marked as done (ruby-cheffish: FTBFS: ERROR: Test "ruby2.3" failed.)

[Debian Bug Tracking System]

Your message dated Mon, 19 Sep 2016 16:26:00 +
with message-id 
and subject line Bug#837229: fixed in ruby-cheffish 4.0.0-1
has caused the Debian Bug report #837229,
regarding ruby-cheffish: FTBFS: ERROR: Test "ruby2.3" failed.
to be marked as done.

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

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


-- 
837229: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=837229
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: ruby-cheffish
Version: 2.0.4-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):
> /usr/bin/ruby2.3 /usr/bin/gem2deb-test-runner
> 
> ┌──┐
> │ Checking Rubygems dependency resolution on ruby2.3  
>  │
> └──┘
> 
> GEM_PATH=debian/ruby-cheffish/usr/share/rubygems-integration/all:/<>/tmp/.gem/ruby/2.3.0:/var/lib/gems/2.3.0:/usr/lib/x86_64-linux-gnu/rubygems-integration/2.3.0:/usr/share/rubygems-integration/2.3.0:/usr/share/rubygems-integration/all
>  ruby2.3 -e gem\ \"cheffish\"
> /usr/lib/ruby/2.3.0/rubygems/dependency.rb:319:in `to_specs': Could not find 
> 'chef-zero' (~> 4.3) - did find: [chef-zero-5.0.0] (Gem::LoadError)
> Checked in 
> 'GEM_PATH=debian/ruby-cheffish/usr/share/rubygems-integration/all:/<>/tmp/.gem/ruby/2.3.0:/var/lib/gems/2.3.0:/usr/lib/x86_64-linux-gnu/rubygems-integration/2.3.0:/usr/share/rubygems-integration/2.3.0:/usr/share/rubygems-integration/all',
>  execute `gem env` for more information
>   from /usr/lib/ruby/2.3.0/rubygems/specification.rb:1438:in `block in 
> activate_dependencies'
>   from /usr/lib/ruby/2.3.0/rubygems/specification.rb:1427:in `each'
>   from /usr/lib/ruby/2.3.0/rubygems/specification.rb:1427:in 
> `activate_dependencies'
>   from /usr/lib/ruby/2.3.0/rubygems/specification.rb:1409:in `activate'
>   from /usr/lib/ruby/2.3.0/rubygems/core_ext/kernel_gem.rb:68:in `block 
> in gem'
>   from /usr/lib/ruby/2.3.0/rubygems/core_ext/kernel_gem.rb:67:in 
> `synchronize'
>   from /usr/lib/ruby/2.3.0/rubygems/core_ext/kernel_gem.rb:67:in `gem'
>   from -e:1:in `'
> bigdecimal (1.2.8)
> bundler (1.12.5)
> chef (12.10.24)
> chef-config (12.10.24)
> chef-zero (5.0.0)
> compat_resource (12.10.5)
> did_you_mean (1.0.0)
> diff-lcs (1.2.5)
> erubis (2.7.0)
> ffi (1.9.10)
> ffi-yajl (2.2.3)
> fuzzyurl (0.8.0)
> hashie (3.4.4)
> highline (1.7.8)
> io-console (0.4.5)
> ipaddress (0.8.3)
> json (1.8.3)
> mime-types (2.6.1)
> minitest (5.9.0)
> mixlib-authentication (1.4.1)
> mixlib-cli (1.5.0)
> mixlib-config (2.2.1)
> mixlib-log (1.6.0)
> mixlib-shellout (2.2.6)
> molinillo (0.5.0)
> multi_json (1.11.2)
> net-http-persistent (2.9.4)
> net-scp (1.2.1)
> net-sftp (2.1.2)
> net-ssh (3.2.0)
> net-ssh-gateway (1.2.0)
> net-ssh-multi (1.2.1)
> net-telnet (0.1.1)
> ohai (8.10.0)
> plist (3.2.0)
> power_assert (0.2.7)
> proxifier (1.0.3)
> psych (2.0.17)
> rack (1.6.4)
> rake (10.5.0)
> rdoc (4.2.1)
> rspec (3.4.0)
> rspec-core (3.4.3)
> rspec-expectations (3.4.0)
> rspec-its (1.2.0)
> rspec-mocks (3.4.1)
> rspec-support (3.4.1)
> serverspec (2.18.0)
> sigar (0.7.3)
> specinfra (2.35.1)
> syslog-logger (1.6.8)
> systemu (2.6.5)
> test-unit (3.1.7)
> thor (0.19.1)
> thread_order (1.1.0)
> uuidtools (2.1.5)
> ERROR: Test "ruby2.3" failed.

The full build log is available from:
   http://aws-logs.debian.net/2016/09/10/ruby-cheffish_2.0.4-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: ruby-cheffish
Source-Version: 4.0.0-1

We believe that the bug you reported is fixed in the latest version of
ruby-cheffish, 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 

Bug#831255: marked as done (polyorb: FTBFS: build-dependency not installable: gnat-4.9)

[Debian Bug Tracking System]

Your message dated Mon, 19 Sep 2016 16:24:44 +
with message-id 
and subject line Bug#831255: fixed in polyorb 2.11~20140418-3.1
has caused the Debian Bug report #831255,
regarding polyorb: FTBFS: build-dependency not installable: gnat-4.9
to be marked as done.

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

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


-- 
831255: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=831255
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: polyorb
Version: 2.11~20140418-3
Severity: serious
Tags: stretch sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20160714 qa-ftbfs
Justification: FTBFS on amd64

Hi,

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

Relevant part (hopefully):
> ┌──┐
> │ Install polyorb build dependencies (apt-based resolver) 
>  │
> └──┘
> 
> Installing build dependencies
> Reading package lists...
> Building dependency tree...
> Reading state information...
> Some packages could not be installed. This may mean that you have
> requested an impossible situation or if you are using the unstable
> distribution that some required packages have not yet been created
> or been moved out of Incoming.
> The following information may help to resolve the situation:
> 
> The following packages have unmet dependencies:
>  sbuild-build-depends-polyorb-dummy : Depends: gnat-4.9 but it is not going 
> to be installed
> E: Unable to correct problems, you have held broken packages.
> apt-get failed.

The full build log is available from:
   
http://people.debian.org/~lucas/logs/2016/07/14/polyorb_2.11~20140418-3_unstable_gcc5.log

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

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

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

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

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

Debian distribution maintenance software
pp.
Mattia Rizzolo  (supplier of updated polyorb 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, 19 Sep 2016 14:20:50 +
Source: polyorb
Binary: polyorb-servers libpolyorb3-dev libpolyorb4 polyorb-doc libpolyorb-dbg
Architecture: source
Version: 2.11~20140418-3.1
Distribution: unstable
Urgency: medium
Maintainer: Xavier Grave 
Changed-By: Mattia Rizzolo 
Description:
 libpolyorb-dbg - Multiple-personality middleware for Ada (debug)
 libpolyorb3-dev - Multiple-personality middleware for Ada (development)
 libpolyorb4 - Multiple-personality middleware for Ada
 polyorb-doc - Multiple-personality middleware for Ada (documentation)
 polyorb-servers - Multiple-personality middleware for Ada (servers)
Closes: 831255
Changes:
 polyorb (2.11~20140418-3.1) unstable; urgency=medium
 .
   * Non-maintainer upload.
 .
   [ Svante Signell ]
   * build with gnat-6.  Closes: #831255.
   * Add patch to fix compilation due to missing include.
Checksums-Sha1:
 f3ceeca22e8480148c6d982c9e2dbee7e690af89 2388 polyorb_2.11~20140418-3.1.dsc
 801da04f3cd250d8f40c89bc485e0b6932498139 34748 
polyorb_2.11~20140418-3.1.debian.tar.xz
Checksums-Sha256:
 8fabbf46a8e5c49ad3d0e8f8522812d316650801e9d174ccfdc2053e88f54eb7 2388 
polyorb_2.11~20140418-3.1.dsc
 0cf374ff7ce2d19e86d1d83b992a44f64207c1ca35d9f267037c1c7ccc1dec25 34748 
polyorb_2.11~20140418-3.1.debian.tar.xz
Files:
 cae115de109474d89a7ba52360cb9d21 2388 net optional 
polyorb_2.11~20140418-3.1.dsc
 4ef59ab25bbce6ce09a0e4451f62fb6b 34748 net optional 
polyorb_2.11~20140418-3.1.debian.tar.xz

-BEGIN PGP SIGNATURE-

Bug#838273: marked as done (libmail-gnupg-perl: FTBFS in testing (failing tests))

[Debian Bug Tracking System]

Your message dated Mon, 19 Sep 2016 16:23:25 +
with message-id 
and subject line Bug#838273: fixed in libmail-gnupg-perl 0.23-2
has caused the Debian Bug report #838273,
regarding libmail-gnupg-perl: 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.)


-- 
838273: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=838273
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:libmail-gnupg-perl
Version: 0.23-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
   dh_testdir -i
   dh_update_autotools_config -i
   dh_auto_configure -i
perl -I. Build.PL --installdirs vendor --config "optimize=-g -O2 
-fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat 
-Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2" --config 
"ld=x86_64-linux-gnu-gcc -g -O2 -fdebug-prefix-map=/<>=. 
-fstack-protector-strong -Wformat -Werror=format-security -Wl,-z,relro"
Created MYMETA.yml and MYMETA.json
Creating new 'Build' script for 'Mail-GnuPG' version '0.23'
   dh_auto_build -i
perl Build
Building Mail-GnuPG
   debian/rules override_dh_auto_test
make[1]: Entering directory '/<>'
chmod a+x t/fake-pinentry.pl
dh_auto_test
perl Build test --verbose 1
t/00.signature.t . skipped: Set the environment variable TEST_SIGNATURE 
to enable this test.
t/05.load.t .. 
1..1
ok 1 - use Mail::GnuPG;
ok
t/20.inline-verify.t . 
gpg: keyring `mgtwUFmz/secring.gpg' created
gpg: keyring `mgtwUFmz/pubring.gpg' created
gpg: mgtwUFmz/trustdb.gpg: trustdb created
gpg: key 7B75921E: public key "Antoine Beaupré " imported
gpg: key 784206AD: public key "David Bremner " imported
gpg: key 9456D16A: public key "Mauricio Campiglia " 
imported
gpg: Total number processed: 3
gpg:   imported: 3  (RSA: 2)
gpg: no ultimately trusted keys found
1..5
ok 1 - An object of class 'MIME::Entity' isa 'MIME::Entity'
ok 2 - An object of class 'Mail::GnuPG' isa 'Mail::GnuPG'
ok 3 - verify success
ok 4 - verify keyid
ok 5 - verify uid
ok
t/25.multipart-verify.t .. 
gpg: keyring `mgth3uMA/secring.gpg' created
gpg: keyring `mgth3uMA/pubring.gpg' created
gpg: mgth3uMA/trustdb.gpg: trustdb created
gpg: key 7B75921E: public key "Antoine Beaupré " imported
gpg: key 784206AD: public key "David Bremner " imported
gpg: key 9456D16A: public key "Mauricio Campiglia " 
imported
gpg: Total number processed: 3
gpg:   imported: 3  (RSA: 2)
gpg: no ultimately trusted keys found
1..5
ok 1 - An object of class 'MIME::Entity' isa 'MIME::Entity'
ok 2 - An object of class 'Mail::GnuPG' isa 'Mail::GnuPG'
ok 3 - verify success
ok 4 - verify keyid
ok 5 - verify uid
ok
t/30.inline-decrypt.t  
1..5
ok 1 - An object of class 'MIME::Entity' isa 'MIME::Entity'
gpg: keyring `mgtItzND/secring.gpg' created
gpg: keyring `mgtItzND/pubring.gpg' created
gpg: key EFEA4EAD: secret key imported
gpg: mgtItzND/trustdb.gpg: trustdb created
gpg: key EFEA4EAD marked as ultimately trusted
gpg: key EFEA4EAD: public key "Mail::GnuPG Test Key " imported
gpg: key EFEA4EAD: "Mail::GnuPG Test Key " 1 new signature
gpg: Total number processed: 2
gpg:   imported: 1
gpg: new signatures: 1
gpg:   secret keys read: 1
gpg:   secret keys imported: 1
gpg: 3 marginal(s) needed, 1 complete(s) needed, PGP trust model
gpg: depth: 0  valid:   1  signed:   0  trust: 0-, 0q, 0n, 0m, 0f, 1u
ok 2 - An object of class 'Mail::GnuPG' isa 'Mail::GnuPG'
ok 3 - decrypt success
ok 4 - message unsigned
ok 5 - plaintext
ok
t/35.has-public-key.t  
gpg: keyring `mgtwmP26/secring.gpg' created
gpg: keyring `mgtwmP26/pubring.gpg' created
gpg: key EFEA4EAD: secret key imported
gpg: mgtwmP26/trustdb.gpg: trustdb created
gpg: key EFEA4EAD: public key "Mail::GnuPG Test Key " imported
gpg: key EFEA4EAD: "Mail::GnuPG Test Key " 1 new signature
gpg: Total number processed: 2
gpg:   imported: 1
gpg: new signatures: 1
gpg:   secret keys read: 1
gpg:   secret keys imported: 1
1..3
ok 1 - An object of class 'Mail::GnuPG' isa 'Mail::GnuPG'
ok 2 - public key exists
ok 3 - bogus key doesn't exist
ok

Processed: Re: [Pkg-opencl-devel] Bug#838302: opencl-headers depends on unavailable opencl-clhpp-headers

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #838302 [opencl-headers] opencl-headers depends on unavailable 
opencl-clhpp-headers
Added tag(s) pending.

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

Bug#838302: [Pkg-opencl-devel] Bug#838302: opencl-headers depends on unavailable opencl-clhpp-headers

[Andreas Beckmann]

Control: tag -1 pending

On 2016-09-19 17:32, Thadeu Lima de Souza Cascardo wrote:
> I can't find opencl-clhpp-headers at the archive.

It's sitting in NEW ...


Andreas

Processed: block 836917 with 838299

[Debian Bug Tracking System]

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

> block 836917 with 838299
Bug #836917 [release.debian.org] transition: openmpi
836917 was blocked by: 837055 837530 817690 837109 837058 811651 822021 837061 
835680 837911 837914 837062 837915 815348 831164 837532 812036 837059 837030 
837012 830440 811907 825934
836917 was not blocking any bugs.
Added blocking bug(s) of 836917: 838299
> thanks
Stopping processing here.

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

Bug#838303: kde-plasma-desktop: KDE does not start after log in

[Gabor Nagy]

Package: kde-plasma-desktop
Version: 5:91
Severity: grave
Justification: renders package unusable

Dear Maintainer,

   * What led up to the situation?

On the 15th of September I have upgraded some packages

   * What was the outcome of this action?

Next time when I started this computer, after the sddm login screen when I
successfully log in, I can see a KDE loading splash screen as expected, but
after the spalsh screen I see only a blank black screen, with the mouse pointer
on the left edge. I can move the pointer up and down, but it doesn't move
horizontally.

   * What outcome did you expect instead?

A working system

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

I can switch to the console with ctrl-alt-Fn and log in there. I could only
restart the computer, could not find a way to fix KDE.  I have removed every
KDE and X packages, then I installed LXDE desktop. With LXDE the system works.

I reinstalled task-desktop-kde.  Now in sddm I have the option to select plasma
or lxde (among some other things). If I select LXDE it works. If I select
Plasma, I have the same issue as before.

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

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

Versions of packages kde-plasma-desktop depends on:
ii  kde-baseapps  4:16.08.0-1
ii  kde-runtime   4:16.08.0-1
ii  plasma-desktop4:5.6.5-1
ii  plasma-workspace  4:5.6.5.1-1
ii  udisks2   2.1.7-2
ii  upower0.99.4-3

Versions of packages kde-plasma-desktop recommends:
ii  kwin-x11  4:5.7.0-1
ii  sddm  0.13.0-1
ii  xserver-xorg  1:7.7+16

Versions of packages kde-plasma-desktop suggests:
ii  kde-l10n-engb [kde-l10n]  4:16.04.3-1

-- no debconf information

Bug#838302: opencl-headers depends on unavailable opencl-clhpp-headers

[Thadeu Lima de Souza Cascardo]

Package: opencl-headers
Version: 2.1-1
Severity: serious

I can't find opencl-clhpp-headers at the archive.

Regards.
Cascardo.


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

Kernel: Linux 4.7.0-1-amd64 (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/dash
Init: systemd (via /run/systemd/system)

-- no debconf information

Bug#806660: Bug#805848: Please update taglib in Debian to version 1.10

[Matteo Cypriani]

Le dimanche 18 septembre 2016, 11:41:52 EDT Matteo Cypriani a écrit :
> taglib >= 1.10 is needed for me to package the latest version of qmmp, which
> would be nice to have before the freeze. Is there a chance that you'll be
> working on this upgrade any time soon? I'd be happy to help if I can.

I received a mail delivery failure to mo...@debian.org, so I guess Modestas is 
MIA. Therefore, I worked on updating the package, and published the changes in 
a new repository on collab-maint :

https://anonscm.debian.org/cgit/collab-maint/taglib.git/

My work also includes a patch fixing #806660, and I repacked the tarball to 
address #736188.

Lintian still complains about a few minor things, that can probably be ignored 
for now, and one major one concerning the symbols files, that will need to be 
addressed before uploading (basically the symbols files need updating).

Cheers,
  Matteo

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

Bug#811674: FTBFS with GCC 6: multiple errors

[Emilio Pozuelo Monfort]

On Tue, 19 Jan 2016 16:50:22 -0800 Martin Michlmayr  wrote:
> Package: ceph
> Version: 0.80.11-1
> Severity: important
> User: debian-...@lists.debian.org
> Usertags: ftbfs-gcc-6 gcc-6-cannot-convert
> 
> This package fails to build with GCC 6.  GCC 6 has not been released
> yet, but it's expected that GCC 6 will become the default compiler for
> stretch.

Any news on this? This is blocking the boost1.58 removal, which in turn is
blocking the ongoing openmpi transition. I'd appreciate if you could take a look
at this.

Cheers,
Emilio

Bug#833770: avogadro: FTBFS with gcc6/boost1.61

[Emilio Pozuelo Monfort]

On Mon, 8 Aug 2016 15:00:56 + Mattia Rizzolo  wrote:
> source: avogadro
> version: 1.0.3-13
> severity: serious
> 
> Dear maintainer,
> 
> your package failed to build on buildd during rebuilds for boost1.61
> using gcc6 as a compiler.
> 
> you can see the build log for the failures at
> https://buildd.debian.org/status/logs.php?pkg=avogadro=1.0.3-13.1%2Bb1=sid

Ping? This is blocking the boost1.58 removal, which in turn is blocking the
openmpi transition. I'd appreciate it if you could take a look at this.

Thanks,
Emilio

Bug#838273: Pending fixes for bugs in the libmail-gnupg-perl package

[pkg-perl-maintainers]

tag 838273 + pending
thanks

Some bugs in the libmail-gnupg-perl package are closed in revision
dcc777fcd04775eba8cc29fe7186ba5b1329688b in branch 'master' by gregor
herrmann

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

Commit message:

Skip test t/agent.t during build and autopkgtest.

The test is known to be fragile, and now a real life failure has appeared.

Thanks: Santiago Vila for the bug report.
Closes: #838273

Processed: Pending fixes for bugs in the libmail-gnupg-perl package

[Debian Bug Tracking System]

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

> tag 838273 + pending
Bug #838273 [src:libmail-gnupg-perl] libmail-gnupg-perl: FTBFS in testing 
(failing tests)
Added tag(s) pending.
> thanks
Stopping processing here.

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

Processed: your mail

[Debian Bug Tracking System]

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

> reassign 837536 src:openmpi
Bug #837536 {Done: Alastair McKinstry } [src:mpi4py] 
mpi4py: FTBFS with openmpi 2.0.1-4
Bug reassigned from package 'src:mpi4py' to 'src:openmpi'.
No longer marked as found in versions mpi4py/2.0.0-2.
No longer marked as fixed in versions openmpi/2.0.1-5.
> found 837536 2.0.1-4
Bug #837536 {Done: Alastair McKinstry } [src:openmpi] 
mpi4py: FTBFS with openmpi 2.0.1-4
Marked as found in versions openmpi/2.0.1-4 and reopened.
> fixed 837536 2.0.1-5
Bug #837536 [src:openmpi] mpi4py: FTBFS with openmpi 2.0.1-4
Marked as fixed in versions openmpi/2.0.1-5.
> thanks
Stopping processing here.

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

Bug#838299: espresso: FTBFS on various arches: test suite hangs

[Emilio Pozuelo Monfort]

Source: espresso
Version: 5.4.0+dfsg-1
Severity: serious

Your package failed to build on various architectures:

make[2]: Entering directory '/«BUILDDIR»/espresso-5.4.0+dfsg/test-suite'
### wget or curl not found: will not be able to download missing PP ###
### wget or curl not found: will not be able to download missing PP ###
/«BUILDDIR»/espresso-5.4.0+dfsg/test-suite/..//test-suite/testcode/bin/testcode.py
 --processors=0 --category=_default_ 
debian/rules:48: recipe for target 'override_dh_auto_test' failed
make[1]: [override_dh_auto_test] Terminated (ignored)
make: *** wait: No child processes.  Stop.
make: *** Waiting for unfinished jobs
make: *** wait: No child processes.  Stop.
Makefile:25: recipe for target 'run-tests' failed
make[2]: *** [run-tests] Terminated
Build killed with signal TERM after 150 minutes of inactivity

Full logs at 
https://buildd.debian.org/status/package.php?p=espresso=unstable

Emilio

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

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

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

[Mattia Rizzolo]

On Fri, Sep 16, 2016 at 09:58:07PM +, Mattia Rizzolo wrote:
> On Fri, Sep 16, 2016 at 10:57:59PM +0200, Svante Signell wrote:
> > As fas as I understand it is OK to NMU this package, based on the
> > latest replies by Xavier. Unfortunately nobody from debian-ada has
> > stepped forward, and Xavier is too busy, maybe you can help out here.
> > I'm available whenever you need assistance.
> 
> I'd happy to sponsor an NMU for you.
> Would you kindly provide me a single debdiff from the polyorb as
> currently in the archive to what you'd get?

Alright, I uploaded the attached debdiff, based on Svante's patches.

I'm not closing this bug, as the package is really unmaintainer, and I
have no clue whether it actually works after my NMU.
If anybody needs sponsorship to upload any possible fix/improvements,
please feel free to contact me.

-- 
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  `-
diffstat for polyorb-2.11~20140418 polyorb-2.11~20140418

 changelog |   10 ++
 control   |4 ++--
 patches/add-missing-include.patch |   16 
 patches/hardening.patch   |3 +--
 patches/series|1 +
 rules |7 +++
 6 files changed, 33 insertions(+), 8 deletions(-)

diff -Nru polyorb-2.11~20140418/debian/changelog polyorb-2.11~20140418/debian/changelog
--- polyorb-2.11~20140418/debian/changelog	2014-09-26 13:00:26.0 +
+++ polyorb-2.11~20140418/debian/changelog	2016-09-19 14:20:50.0 +
@@ -1,3 +1,13 @@
+polyorb (2.11~20140418-3.1) unstable; urgency=medium
+
+  * Non-maintainer upload.
+
+  [ Svante Signell ]
+  * build with gnat-6.  Closes: #831255.
+  * Add patch to fix compilation due to missing include.
+
+ -- Mattia Rizzolo   Mon, 19 Sep 2016 14:20:50 +
+
 polyorb (2.11~20140418-3) unstable; urgency=low
 
   [Ludovic Brenta]
diff -Nru polyorb-2.11~20140418/debian/control polyorb-2.11~20140418/debian/control
--- polyorb-2.11~20140418/debian/control	2014-09-26 13:00:26.0 +
+++ polyorb-2.11~20140418/debian/control	2016-09-19 12:44:40.0 +
@@ -5,7 +5,7 @@
 Uploaders: Ludovic Brenta 
 Build-Depends: debhelper (>= 8.9.7), dpkg-dev (>= 1.16.1),
  dh-ada-library, python-gnatpython,
- automake, autotools-dev, libtool, gnat-4.9, python
+ automake, autotools-dev, libtool, gnat-6, python
 Build-Depends-Indep: ghostscript, texlive-formats-extra,
  texlive-generic-recommended, transfig, texinfo
 Standards-Version: 3.9.5
@@ -29,7 +29,7 @@
 Package: libpolyorb3-dev
 Section: libdevel
 Architecture: any
-Depends: ${misc:Depends}, ${shlibs:Depends}, libpolyorb4 (= ${binary:Version}), g++, gnat-4.9
+Depends: ${misc:Depends}, ${shlibs:Depends}, libpolyorb4 (= ${binary:Version}), g++, gnat-6
 Breaks: libpolyorb2-dev
 Replaces: libpolyorb2-dev
 Recommends: polyorb-servers (= ${binary:Version})
diff -Nru polyorb-2.11~20140418/debian/patches/add-missing-include.patch polyorb-2.11~20140418/debian/patches/add-missing-include.patch
--- polyorb-2.11~20140418/debian/patches/add-missing-include.patch	1970-01-01 00:00:00.0 +
+++ polyorb-2.11~20140418/debian/patches/add-missing-include.patch	2016-09-19 12:49:52.0 +
@@ -0,0 +1,16 @@
+Author: Svante Signell 
+Acked-By: Mattia Rizzolo 
+Last-Update: 2016-09-02
+
+Index: polyorb-2.11~20140418/src/csupport.c
+===
+--- polyorb-2.11~20140418.orig/src/csupport.c
 polyorb-2.11~20140418/src/csupport.c
+@@ -27,6 +27,7 @@
+ /* C support functions for PolyORB */
+ 
+ #include "config.h"
++#include 
+ 
+ #ifdef HAVE_FCNTL_H
+ #include 
diff -Nru polyorb-2.11~20140418/debian/patches/hardening.patch polyorb-2.11~20140418/debian/patches/hardening.patch
--- polyorb-2.11~20140418/debian/patches/hardening.patch	2014-09-26 13:00:26.0 +
+++ polyorb-2.11~20140418/debian/patches/hardening.patch	2016-09-19 13:00:42.0 +
@@ -2,11 +2,10 @@
 ===
 --- a/Makefile.in
 +++ b/Makefile.in
-@@ -1,5 +1,8 @@
+@@ -1,5 +1,7 @@
  # Main PolyORB Makefile
  
 +include /usr/share/dpkg/default.mk
-+include /usr/share/ada/debian_packaging.mk
 +
  .PHONY: default
  default: all
diff -Nru polyorb-2.11~20140418/debian/patches/series polyorb-2.11~20140418/debian/patches/series
--- polyorb-2.11~20140418/debian/patches/series	2014-09-26 13:00:26.0 +
+++ polyorb-2.11~20140418/debian/patches/series	2016-09-19 12:49:16.0 +
@@ -43,3 +43,4 @@
 xe_back-polyorb.adb.patch
 support-tilde-in-pathname.patch
 

Bug#837759: network configuration stops working reliably

[Martin Pitt]

Control: severity -1 important
Contro: tag -1 unreproducible

In accordance with the severity definitions [1] I downgrade this to
"important". It does not completely break systemd, we don't enable
networkd by default, and it does not affect every installation (it's
not reproducible on our side yet).

Don't worry, I'm still eager to find out what's happening here; I'll
look at your logs as soon as possible.

Martin

[1] https://www.debian.org/Bugs/Developer#severities

-- 
Martin Pitt| http://www.piware.de
Ubuntu Developer (www.ubuntu.com)  | Debian Developer  (www.debian.org)

Processed: Re: Bug#837759: network configuration stops working reliably

[Debian Bug Tracking System]

Processing control commands:

> severity -1 important
Bug #837759 [systemd] network configuration stops working reliably
Severity set to 'important' from 'grave'

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

Bug#838216: Could not find 'chef-zero' (~> 4.5) - did find: [chef-zero-5.0.0] (Gem::LoadError)

[Antonio Terceiro]

Control: reassign -1 chef
Control: found -1 12.10.24-1


On Sun, Sep 18, 2016 at 10:00:58PM +0530, Pirate Praveen wrote:
> package: chef,chef-zero
> version: 12.10.24-1
> severity: serious
> 
> Update of chef-zero without testing reverse dependency compatibility
> caused the issue.
> 
> adt-run [18:55:42]: test command1: gem2deb-test-runner
> --check-dependencies --autopkgtest
> adt-run [18:55:42]: test command1: [---
> 
> ┌──┐
> │ Checking Rubygems dependency resolution on ruby2.3
>   │
> └──┘
> 
> GEM_PATH= ruby2.3 -e gem\ \"chef\"
> /usr/lib/ruby/2.3.0/rubygems/dependency.rb:319:in `to_specs': Could not
> find 'chef-zero' (~> 4.5) - did find: [chef-zero-5.0.0] (Gem::LoadError)

This also makes chef FTBFS because we check dependencies during the
build. I am reassign to chef because clearly that is where this will
need to be fixed.


signature.asc
Description: PGP signature

Processed: Re: Bug#838216: Could not find 'chef-zero' (~> 4.5) - did find: [chef-zero-5.0.0] (Gem::LoadError)

[Debian Bug Tracking System]

Processing control commands:

> reassign -1 chef
Bug #838216 [chef,chef-zero] Could not find 'chef-zero' (~> 4.5) - did find: 
[chef-zero-5.0.0] (Gem::LoadError)
Bug reassigned from package 'chef,chef-zero' to 'chef'.
No longer marked as found in versions 12.10.24-1.
Ignoring request to alter fixed versions of bug #838216 to the same values 
previously set
> found -1 12.10.24-1
Bug #838216 [chef] Could not find 'chef-zero' (~> 4.5) - did find: 
[chef-zero-5.0.0] (Gem::LoadError)
Marked as found in versions chef/12.10.24-1.

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

Bug#833098: marked as done (python3-qtile: Python3 library depends on Python 2 packages)

[Debian Bug Tracking System]

Your message dated Mon, 19 Sep 2016 13:51:34 +
with message-id 
and subject line Bug#833098: fixed in qtile 0.10.6-3
has caused the Debian Bug report #833098,
regarding python3-qtile: Python3 library depends on Python 2 packages
to be marked as done.

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

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


-- 
833098: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=833098
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: python3-qtile
Version: 0.10.6-2
Severity: serious
Tags: patch
Justification: Policy 7.2

Spot the problem:

Package: python3-qtile
Depends: python-cffi (>= 1.3.0), python-xcffib (>= 0.4.0), python-cairocffi (>= 
0.7), libglib2.0-0, libpango1.0-0, libpangocairo-1.0-0, python3-trollius, 
python3-cairocffi, python3-cffi-backend-api-min (<= 9729), 
python3-cffi-backend-api-max (>= 9729), python3-six (>= 1.4.1), python3-xcffib, 
python3:any (>= 3.3.2-2~)

A python3 library requiring python2 modules? o_O

SR
diff -Nru qtile-0.10.6/debian/changelog qtile-0.10.6/debian/changelog
--- qtile-0.10.6/debian/changelog	2016-05-29 09:31:59.0 -0400
+++ qtile-0.10.6/debian/changelog	2016-07-31 15:27:55.0 -0400
@@ -1,3 +1,10 @@
+qtile (0.10.6-2.1) UNRELEASED; urgency=medium
+
+  * Non-maintainer upload.
+  * Less crazy dependencies
+
+ -- Stefano Rivera   Sun, 31 Jul 2016 15:27:48 -0400
+
 qtile (0.10.6-2) unstable; urgency=medium
 
   * Added postinst and prerm scripts for qtile:
diff -Nru qtile-0.10.6/debian/control qtile-0.10.6/debian/control
--- qtile-0.10.6/debian/control	2016-05-29 09:30:58.0 -0400
+++ qtile-0.10.6/debian/control	2016-07-31 15:23:20.0 -0400
@@ -65,9 +65,9 @@
 
 Package: python3-qtile
 Architecture: any
-Depends: python-cffi (>= 1.3.0),
- python-xcffib (>= 0.4.0),
- python-cairocffi (>= 0.7),
+Depends: python3-cffi (>= 1.3.0),
+ python3-xcffib (>= 0.4.0),
+ python3-cairocffi (>= 0.7),
  libglib2.0-0,
  libpango1.0-0,
  libpangocairo-1.0-0,
--- End Message ---
--- Begin Message ---
Source: qtile
Source-Version: 0.10.6-3

We believe that the bug you reported is fixed in the latest version of
qtile, 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.
Iain R. Learmonth  (supplier of updated qtile 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, 19 Sep 2016 13:47:38 +0100
Source: qtile
Binary: python-qtile python3-qtile qtile
Architecture: source
Version: 0.10.6-3
Distribution: unstable
Urgency: medium
Maintainer: Iain R. Learmonth 
Changed-By: Iain R. Learmonth 
Description:
 python-qtile - This package is a library for developing X window managers 
(Pytho
 python3-qtile - This package is a library for developing X window managers 
(Pytho
 qtile  - Small, simple, extensible X11 window manager written in Python
Closes: 833098
Changes:
 qtile (0.10.6-3) unstable; urgency=medium
 .
   * Fixes Python dependencies to use correct Python version (Closes: #833098)
- Also removed python{3,}-cffi as these dependencies were not required.
Checksums-Sha1:
 59eef98a4606e73e9ff41ae59688905ce7f49c06 2004 qtile_0.10.6-3.dsc
 a0387633a3fcb1acbbc042c2d04112002157ce8b 3116 qtile_0.10.6-3.debian.tar.xz
Checksums-Sha256:
 78639040aae1296c0cdc52e687643524c43301be4efdbc37caaa6735a403a7e1 2004 
qtile_0.10.6-3.dsc
 702ec7f3c11f45645f5b77f36201c998a99b4adf1d4687a5be4e4723d3fa23dc 3116 
qtile_0.10.6-3.debian.tar.xz
Files:
 a0899f5233381a419550f1426fe18094 2004 python optional qtile_0.10.6-3.dsc
 8f60d455aaefbd361d97e34353ea0174 3116 python optional 
qtile_0.10.6-3.debian.tar.xz

-BEGIN PGP SIGNATURE-
Version: GnuPG v2

iQEcBAEBCAAGBQJX3+qpAAoJENIXnVuKHtARdjEIAILiEDHb0Kq1O7bIIDXsleBu
nweNrNXGa3Re6cg9ePBYTTSTH7hI1Os7tRxyE3aSZMd8o57ed9SINuAWAU6TfZ0A
EgnLJOrI1+HHbIL9rcJ0Js2rVGBWcXRIul6ChHOfvqpJgmq2pdrhcviJ0odo7SZ8
FfjqmHy3FbMGHXWxwJCFz1K5ouoOa4PfkojKqLsh3iGJD+eRQ3IdbLnidIAEREO8
Nzj6xXDMiNPnghi3VqpgK9lRr7q335ZxewQ0XAIu5SeIYISz9eC0HE7rcxNrA6Uc

Bug#837477: marked as done (xbacklight doesn't do anything at all)

[Debian Bug Tracking System]

Your message dated Mon, 19 Sep 2016 15:49:42 +0200
with message-id <20160919134942.2nozv3cjmydbt...@betterave.cristau.org>
and subject line Re: Bug#837477: xbacklight doesn't do anything at all
has caused the Debian Bug report #837477,
regarding xbacklight doesn't do anything at all
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.)


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

Dear Maintainer,

In Debian Testing, none of the commands or options with xbacklight do anything
or give any output whatsoever, EXCEPT if I type an invalid command, then it
gives me the help stuff about basic usage:

"""
usage: xbacklight [options]
  where options are:
  -display  or -d 
  -help
  -set  or = 
  -inc  or + 
  -dec  or - 
  -get
  -time 
  -steps 
"""

but it doesn't do anything if I actually use one of those valid commands.

 I think I have this bug:
https://bugs.launchpad.net/ubuntu/+source/xbacklight/+bug/1060431

I am on an acer c720 chromebook, if that matters.

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

Kernel: Linux 4.6.0-1-amd64 (SMP w/4 CPU cores)
Locale: LANG=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 xbacklight depends on:
ii  libc6  2.23-5
ii  libxcb-randr0  1.11.1-1.1
ii  libxcb-util0   0.3.8-3
ii  libxcb11.11.1-1.1

xbacklight recommends no packages.

xbacklight suggests no packages.
--- End Message ---
--- Begin Message ---
On Sun, Sep 11, 2016 at 17:38:48 -0400, nickpontillo wrote:

> Package: xbacklight
> Version: 1.2.1-1
> Severity: grave
> Justification: renders package unusable
> 
> Dear Maintainer,
> 
> In Debian Testing, none of the commands or options with xbacklight do anything
> or give any output whatsoever, EXCEPT if I type an invalid command, then it
> gives me the help stuff about basic usage:
> 
> """
> usage: xbacklight [options]
>   where options are:
>   -display  or -d 
>   -help
>   -set  or = 
>   -inc  or + 
>   -dec  or - 
>   -get
>   -time 
>   -steps 
> """
> 
> but it doesn't do anything if I actually use one of those valid commands.
> 
>  I think I have this bug:
> https://bugs.launchpad.net/ubuntu/+source/xbacklight/+bug/1060431
> 
> I am on an acer c720 chromebook, if that matters.
> 
This is not an xbacklight bug, your X driver simply does not expose the
backlight information, so xbacklight can't read/change it.

Cheers,
Julien--- End Message ---

Processed: uploaded

[Debian Bug Tracking System]

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

> tags 833098 + pending
Bug #833098 [python3-qtile] python3-qtile: Python3 library depends on Python 2 
packages
Added tag(s) pending.
>
End of message, stopping processing here.

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

Bug#835708: plplot: FTBFS: cairo-related files are no more built

[Ole Streicher]

Small appendum: Upstream fixed it similarly:

commit cac0198537a260fcb413f7d97301979c2dfaa31c
Author: Raphael Kubo da Costa 
Date:   Sat Jul 16 10:45:25 2016 +0200

pkg-config: Adjust _pkg_check_modules_internal() for CMake 3.6.

CMake commit df97b97 ("FindPkgConfig: optionally create imported
target for the found libraries") has changed the function's signature
again, so add another check and update the call accordingly when using
CMake >= 3.6.0.

Tested by: Alan W. Irwin  on Linux
(Debian Jessie) using

scripts/comprehensive_test.sh

(i.e., a full noninteractive and interactive test for CMake-3.6.0
which is the version of CMake that I used for this test).

There were no obvious build or run-time errors, and the PostScript
difference results had no regressions (i.e., were perfect other
than the long-time ocaml issues).

Bug#837079: marked as done (shadow: src:shadow FTBFS due to conflicting hardening-wrapper)

[Debian Bug Tracking System]

Your message dated Mon, 19 Sep 2016 13:20:40 +
with message-id 
and subject line Bug#836653: fixed in shadow 1:4.2-3.2
has caused the Debian Bug report #836653,
regarding shadow: src:shadow FTBFS due to conflicting hardening-wrapper
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.)


-- 
836653: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=836653
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: shadow
Version: 1:4.2-3.1
Severity: serious
Justification: fails to build from source (but built successfully in the past)

Hi,

here part of my build log:

Installing build dependencies
Reading package lists...
Building dependency tree...
Reading state information...
Some packages could not be installed. This may mean that you have
requested an impossible situation or if you are using the unstable
distribution that some required packages have not yet been created
or been moved out of Incoming.
The following information may help to resolve the situation:

The following packages have unmet dependencies:
 sbuild-build-depends-shadow-dummy : Depends: hardening-wrapper but it is not 
going to be installed
E: Unable to correct problems, you have held broken packages.
apt-get failed.
E: Package installation failed


Dose3 gives a better explanation:

  package: shadow
  version: 1:4.2-3.1
  architecture: any
  type: src
  status: broken
  reasons:
   -
conflict:
 pkg1:
  package: binutils
  version: 2.27-8
  architecture: amd64
  unsat-conflict: hardening-wrapper:amd64 (< 2.8+nmu3)
 pkg2:
  package: hardening-wrapper
  version: 2.8+nmu2
  architecture: amd64
 depchain1:
  -
   depchain:
-
 package: shadow
 version: 1:4.2-3.1
 architecture: any
 type: src
 depends: hardening-wrapper:amd64
-
 package: hardening-wrapper
 version: 2.8+nmu2
 architecture: amd64
 depends: binutils:amd64 (>= 2.25.90)
 depchain2:
  -
   depchain:
-
 package: shadow
 version: 1:4.2-3.1
 architecture: any
 type: src
 depends: hardening-wrapper:amd64

So the problem is that binutils conflicts with hardening-wrapper and indeed:

Package: binutils
Version: 2.27-8
Breaks: [...], hardening-wrapper (<< 2.8+nmu3)

I don't know what the proper solution for this is but #836653 indicates
that you might want to drop the build-dependency on hardening-wrapper
completely.

Thanks!

cheers, josch
--- End Message ---
--- Begin Message ---
Source: shadow
Source-Version: 1:4.2-3.2

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

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Sun, 18 Sep 2016 14:42:16 +
Source: shadow
Binary: passwd login uidmap
Architecture: source
Version: 1:4.2-3.2
Distribution: unstable
Urgency: medium
Maintainer: Shadow package maintainers 

Changed-By: Mattia Rizzolo 
Description:
 login  - system login tools
 passwd - change and administer password and group data
 uidmap - programs to help use subuids
Closes: 836653
Changes:
 shadow (1:4.2-3.2) unstable; urgency=medium
 .
   * Non-maintainer upload.
   * Use HTTPS in Vcs-Git.
   * Stop using hardening-wrapper and instead use /usr/share/dpkg/buildflags.mk.
 Closes: #836653
Checksums-Sha1:
 bd85bbb7de35a487e45ad61b7388de50b48e0119 2289 shadow_4.2-3.2.dsc
 b956798cc086db8e0dc2886c1ed74894d09613b2 497092 shadow_4.2-3.2.debian.tar.xz
Checksums-Sha256:
 9377f2adb0d3bf01dbdd36a6b550f1bc2e1d60840cf39d5314cca4474a7ff857 2289 
shadow_4.2-3.2.dsc
 0483a19f500c8eb8b26ef3fd408a014f32171c375b76d3ed7762cf97934bee4c 497092 
shadow_4.2-3.2.debian.tar.xz
Files:
 2e2e4f7ea71429f8a0642d83c76ca97f 2289 admin required shadow_4.2-3.2.dsc
 87cb7aae7782b8df65ca98e0cfc2424b 497092 admin 

Bug#836653: marked as done (shadow: please drop the build dependency on hardening-wrapper)

[Debian Bug Tracking System]

Your message dated Mon, 19 Sep 2016 13:20:40 +
with message-id 
and subject line Bug#836653: fixed in shadow 1:4.2-3.2
has caused the Debian Bug report #836653,
regarding shadow: please drop the build dependency on hardening-wrapper
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.)


-- 
836653: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=836653
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: shadow
Version: 1:4.2-3.1
Severity: important
Tags: sid stretch
User: debian-...@lists.debian.org
Usertags: hardening-wrapper

This package builds using the hardening-wrapper package, which
is now replaced by dpkg-dev's DEB_BUILD_MAINT_OPTIONS settings.

Please consider dropping the build dependency of hardening-wrapper
and use the DEB_BUILD_MAINT_OPTIONS settings.

The goal is to remove hardening-wrapper for the stretch release.
Discussion about the removal is tracked in https://bugs.debian.org/836162

The severity of this report is likely to be raised before the release,
so that the hardening-wrapper package can be removed for the release.
--- End Message ---
--- Begin Message ---
Source: shadow
Source-Version: 1:4.2-3.2

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

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Sun, 18 Sep 2016 14:42:16 +
Source: shadow
Binary: passwd login uidmap
Architecture: source
Version: 1:4.2-3.2
Distribution: unstable
Urgency: medium
Maintainer: Shadow package maintainers 

Changed-By: Mattia Rizzolo 
Description:
 login  - system login tools
 passwd - change and administer password and group data
 uidmap - programs to help use subuids
Closes: 836653
Changes:
 shadow (1:4.2-3.2) unstable; urgency=medium
 .
   * Non-maintainer upload.
   * Use HTTPS in Vcs-Git.
   * Stop using hardening-wrapper and instead use /usr/share/dpkg/buildflags.mk.
 Closes: #836653
Checksums-Sha1:
 bd85bbb7de35a487e45ad61b7388de50b48e0119 2289 shadow_4.2-3.2.dsc
 b956798cc086db8e0dc2886c1ed74894d09613b2 497092 shadow_4.2-3.2.debian.tar.xz
Checksums-Sha256:
 9377f2adb0d3bf01dbdd36a6b550f1bc2e1d60840cf39d5314cca4474a7ff857 2289 
shadow_4.2-3.2.dsc
 0483a19f500c8eb8b26ef3fd408a014f32171c375b76d3ed7762cf97934bee4c 497092 
shadow_4.2-3.2.debian.tar.xz
Files:
 2e2e4f7ea71429f8a0642d83c76ca97f 2289 admin required shadow_4.2-3.2.dsc
 87cb7aae7782b8df65ca98e0cfc2424b 497092 admin required 
shadow_4.2-3.2.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQIcBAEBCgAGBQJX3qjrAAoJEEsEP825REVArlIP/2YYZ8rqhygRMF+UnLDfXpkU
5QuORTKcGBE8Nwcsqujd5Y3xHGZU+0SE89dxiJxbXst40gzhJeXSr/W3QsKkuPT8
yp+U/KNx6BoNGwmICJjBnjc6hk8v9mg3a3BAk7butW2djPBoDddiFVANkNgOZmLT
l+FpOdLBgVJ/SnlJH2Ts9x/oter3zVIhchYVqeiziIN4YkyHPzE3SreuL7ZzLcCj
igMvZufk0MnKjhHK8+xmsHx3egb4+UmF6RzLIqhfz/oq9/NLHNdxwzyGOXWVuaq4
0lZM/BUcoySJQ4zaTyYRyJrGiYYo2BnXNVcobqq7lCjOp+Ad9FBLJEr+tITctFUD
wHDjNmkEzFxsOj1s1o8pkp61DJhweX5ojVsmjHamGoFc7o/bWL09ZjFFYJ0XofTj
2XdGOqbeGAOs6Rfs6gvChvK7lJuugaTQ/58psmKz9RL/KowVzD3CT9zScZTOfjsT
Y+BaZoh2/V9rtEGAOJsoH2peehTs1ers6E+zwYqDdiuZAvUwe3fJLLLIqBSEAWoa
FGE/lbaRhAny7DhWCaqWF33Cqjn8+w8XNs4yF+rDhzanD7+D+Frfq1l+BkM93yew
4weX49P3DS4gDk2PqRaUV//wALU+QKDpHgUvmphkmIAnZknHOAK6UTJd2scimwVe
RExFXHaubtx2+haQ45Tv
=z2q/
-END PGP SIGNATURE End Message ---

Bug#835708: plplot: FTBFS: cairo-related files are no more built

[Ole Streicher]

Control: tags -1 patch
Control: tags -1 pending

I investigated the bug a bit more. The problem is here, that plplot uses
(in cmake/modules/pkg-config.cmake) a CMake function that is
undocumented and internal to CMake: _pkg_check_modules_internal (WTF?)

This function changed once in 3.1, causing the need of a version
specific switch (debian/patches/cmake-3.1.diff). Now the function API
changed again, specifically in

https://cmake.org/gitweb?p=cmake.git;a=commitdiff;h=df97b9793#patch2

by adding an additional argument at the third-last position. We
therefore require to extend the switch mentioned above:

  if(CMAKE_VERSION VERSION_LESS "3.1")
_pkg_check_modules_internal(0 0 ${_prefix} "${_package}")
  elseif(CMAKE_VERSION VERSION_LESS "3.6.2")
_pkg_check_modules_internal(0 0 0 0 ${_prefix} "${_package}")
  else(CMAKE_VERSION VERSION_LESS "3.6.2")
_pkg_check_modules_internal(0 0 0 0 0 ${_prefix} "${_package}")
  endif(CMAKE_VERSION VERSION_LESS "3.6.2")

The attached patch replaces the "cmake-3.1.diff" patch that comes with
the current Debian package.

I would try an NMU within the next days (never did that before, so
expect some glitches here ;-) ).

Cheers

Ole
Based on upstream commit 772223c638ecf5dc740c9f3dd7a6883c6d2c83d2 with a slight
tweak to make the patch apply on our version of the source.

commit 772223c638ecf5dc740c9f3dd7a6883c6d2c83d2
Author: Alan W. Irwin 
Date:   Sun Dec 7 09:06:08 2014 -0800

Adjust for internal CMake-3.1 pkg-config change.

There is a report from Greg Jung  that the
internal CMake command

_pkg_check_modules_internal(0 0 ${_prefix} "${_package}")

must be changed to

_pkg_check_modules_internal(0 0 0 0 ${_prefix} "${_package}")

for CMake-3.1 in order to build the cairo device properly.  Accordingly, I have made that adjustment.

Tested by Alan W. Irwin  on Linux using CMake-3.0.2
by building the cairo device.

N.B. currently untested for CMake-3.1.

ToDo:

Extensive tests on CMake-3.1 (once that version is closer to release)
still need to be done since the change in the pkg-config support by
CMake may need other adjustments as well.

--- a/cmake/modules/pkg-config.cmake
+++ b/cmake/modules/pkg-config.cmake
@@ -1,6 +1,6 @@
 # cmake/modules/pkg-config.cmake
 #
-# Copyright (C) 2006  Alan W. Irwin
+# Copyright (C) 2006-2015 Alan W. Irwin
 #
 # This file is part of PLplot.
 #
@@ -94,7 +94,14 @@
 set(_xprefix ${_prefix})
   endif(FORCE_EXTERNAL_STATIC)
   
-  _pkg_check_modules_internal(0 0 ${_prefix} "${_package}")
+  if(CMAKE_VERSION VERSION_LESS "3.1")
+_pkg_check_modules_internal(0 0 ${_prefix} "${_package}")
+  elseif(CMAKE_VERSION VERSION_LESS "3.6.2")
+_pkg_check_modules_internal(0 0 0 0 ${_prefix} "${_package}")
+  else(CMAKE_VERSION VERSION_LESS "3.6.2")
+_pkg_check_modules_internal(0 0 0 0 0 ${_prefix} "${_package}")
+  endif(CMAKE_VERSION VERSION_LESS "3.6.2")
+
   if(${_prefix}_FOUND)
 cmake_link_flags(${_link_FLAGS} "${${_xprefix}_LDFLAGS}")
 # If libraries cannot be not found, then that is equivalent to whole

Processed: Re: Bug#835708: plplot: FTBFS: cairo-related files are no more built

[Debian Bug Tracking System]

Processing control commands:

> tags -1 patch
Bug #835708 [src:plplot] plplot: FTBFS: cairo-related files are no more built
Added tag(s) patch.
> tags -1 pending
Bug #835708 [src:plplot] plplot: FTBFS: cairo-related files are no more built
Added tag(s) pending.

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

Bug#836653: [Pkg-shadow-devel] Bug#836653: shadow: diff for NMU version 1:4.2-3.2

[Mattia Rizzolo]

On Mon, Sep 19, 2016 at 07:57:38AM -0500, Serge E. Hallyn wrote:
> Thank you ver much.  Please go ahead and upload.

Thank you! ♥

mattia@chase ~/devel/NMU/0_DONE/shadow % dcut reschedule -d 0 -f 
shadow_4.2-3.2_source.changes
Uploading commands file to ftp.upload.debian.org (incoming: /pub/UploadQueue/)
Uploading mattia-1474290182.commands to ftp-master
mattia@chase ~/devel/NMU/0_DONE/shadow % 


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

Bug#836653: [Pkg-shadow-devel] Bug#836653: shadow: diff for NMU version 1:4.2-3.2

[Serge E. Hallyn]

Thank you ver much.  Please go ahead and upload.

Processed: fix versioning of bug #811612

[Debian Bug Tracking System]

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

> reassign 811612 src:nvidia-texture-tools 2.0.8-1+dfsg-8
Bug #811612 [nvidia-texture-tools] FTBFS with GCC 6: cannot convert x to y
Bug reassigned from package 'nvidia-texture-tools' to 
'src:nvidia-texture-tools'.
No longer marked as found in versions 2.0.8-1+dfsg-8.
No longer marked as fixed in versions 2.1.0-git20160229+dfsg-2~exp1.
Bug #811612 [src:nvidia-texture-tools] FTBFS with GCC 6: cannot convert x to y
Marked as found in versions nvidia-texture-tools/2.0.8-1+dfsg-8.
> fixed 811612 2.1.0-git20160229+dfsg-2~exp1
Bug #811612 [src:nvidia-texture-tools] FTBFS with GCC 6: cannot convert x to y
Marked as fixed in versions nvidia-texture-tools/2.1.0-git20160229+dfsg-2~exp1.
> thanks
Stopping processing here.

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

Processed: Re: Bug#811612: FTBFS with GCC 6: cannot convert x to y

[Debian Bug Tracking System]

Processing control commands:

> fixed -1 2.1.0-git20160229+dfsg-2~exp1
Bug #811612 [nvidia-texture-tools] FTBFS with GCC 6: cannot convert x to y
There is no source info for the package 'nvidia-texture-tools' at version 
'2.1.0-git20160229+dfsg-2~exp1' with architecture ''
Unable to make a source version for version '2.1.0-git20160229+dfsg-2~exp1'
Marked as fixed in versions 2.1.0-git20160229+dfsg-2~exp1.
> tags -1 pending
Bug #811612 [nvidia-texture-tools] FTBFS with GCC 6: cannot convert x to y
Added tag(s) pending.

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

Bug#811612: FTBFS with GCC 6: cannot convert x to y

[James Cowgill]

Control: fixed -1 2.1.0-git20160229+dfsg-2~exp1
Control: tags -1 pending

Hi all,

On 19/09/16 12:20, Adrian Bunk wrote:
> Control: tags 811612 +fixed-upstream
> Control: tags 811612 +patch
> 
> On Wed, Jan 20, 2016 at 11:14:09PM +0100, Lennart Weller wrote:
>> On 20.01.2016 18:30, Martin Michlmayr wrote
>>> This builds fine.
>> Nice. So I either just have to add the patches for 2.0.8 or get 0ad to work
>> with 2.1.0. I'll look into that in the next few days as time permits.
>> ...
> 
> This bug is the reason why 0ad is not in testing, and if it doesn't get 
> fixed then 0ad will not be in the next Debian stable. 
> 
> I've attached the trivial fix.

Thanks for the patch Adrian.

I've uploaded the attached NMU which fixes this to DELAYED/5. Please
tell me if you want me to delay / cancel it. I've also pushed the fix to
the git repository on collab-maint.

The bug doesn't appear to affect the newer version in experimental.

Thanks,
James
diff -Nru nvidia-texture-tools-2.0.8-1+dfsg/debian/changelog nvidia-texture-tools-2.0.8-1+dfsg/debian/changelog
--- nvidia-texture-tools-2.0.8-1+dfsg/debian/changelog	2015-12-08 07:51:31.0 +
+++ nvidia-texture-tools-2.0.8-1+dfsg/debian/changelog	2016-09-19 12:41:04.0 +
@@ -1,3 +1,12 @@
+nvidia-texture-tools (2.0.8-1+dfsg-8.1) unstable; urgency=medium
+
+  * Non-maintainer upload.
+
+  [ Adrian Bunk ]
+  * Fix FTBFS with GCC 6. (Closes: #811612)
+
+ -- James Cowgill   Mon, 19 Sep 2016 12:41:04 +
+
 nvidia-texture-tools (2.0.8-1+dfsg-8) unstable; urgency=medium
 
   * Removed symbols file
diff -Nru nvidia-texture-tools-2.0.8-1+dfsg/debian/patches/14-gcc6.patch nvidia-texture-tools-2.0.8-1+dfsg/debian/patches/14-gcc6.patch
--- nvidia-texture-tools-2.0.8-1+dfsg/debian/patches/14-gcc6.patch	1970-01-01 00:00:00.0 +
+++ nvidia-texture-tools-2.0.8-1+dfsg/debian/patches/14-gcc6.patch	2016-09-19 12:32:14.0 +
@@ -0,0 +1,60 @@
+Description: Fix building with gcc 6
+Author: Adrian Bunk 
+Bug-Debian: https://bugs.debian.org/811612
+Reviewed-By: James Cowgill 
+
+--- nvidia-texture-tools-2.0.8-1+dfsg.orig/src/nvimage/ImageIO.cpp
 nvidia-texture-tools-2.0.8-1+dfsg/src/nvimage/ImageIO.cpp
+@@ -135,7 +135,7 @@ FloatImage * nv::ImageIO::loadFloat(cons
+ 	StdInputStream stream(fileName);
+ 	
+ 	if (stream.isError()) {
+-		return false;
++		return NULL;
+ 	}
+ 	
+ 	return loadFloat(fileName, stream);
+@@ -233,7 +233,7 @@ Image * nv::ImageIO::loadTGA(Stream & s)
+ 		case TGA_TYPE_INDEXED:
+ 			if( tga.colormap_type!=1 || tga.colormap_size!=24 || tga.colormap_length>256 ) {
+ nvDebug( "*** ImageIO::loadTGA: Error, only 24bit paletted images are supported.\n" );
+-return false;
++return NULL;
+ 			}
+ 			pal = true;
+ 			break;
+@@ -254,7 +254,7 @@ Image * nv::ImageIO::loadTGA(Stream & s)
+ 
+ 		default:
+ 			nvDebug( "*** ImageIO::loadTGA: Error, unsupported image type.\n" );
+-			return false;
++			return NULL;
+ 	}
+ 
+ 	const uint pixel_size = (tga.pixel_size/8);
+@@ -621,7 +621,7 @@ Image * nv::ImageIO::loadPNG(Stream & s)
+ 	png_ptr = png_create_read_struct(PNG_LIBPNG_VER_STRING, NULL, NULL, NULL);
+ 	if (png_ptr == NULL) {
+ 	//	nvDebug( "*** LoadPNG: Error allocating read buffer in file '%s'.\n", name );
+-		return false;
++		return NULL;
+ 	}
+ 
+ 	// Allocate/initialize a memory block for the image information
+@@ -629,14 +629,14 @@ Image * nv::ImageIO::loadPNG(Stream & s)
+ 	if (info_ptr == NULL) {
+ 		png_destroy_read_struct(_ptr, NULL, NULL);
+ 	//	nvDebug( "*** LoadPNG: Error allocating image information for '%s'.\n", name );
+-		return false;
++		return NULL;
+ 	}
+ 
+ 	// Set up the error handling
+ 	if (setjmp(png_jmpbuf(png_ptr))) {
+ 		png_destroy_read_struct(_ptr, _ptr, NULL);
+ 	//	nvDebug( "*** LoadPNG: Error reading png file '%s'.\n", name );
+-		return false;
++		return NULL;
+ 	}
+ 
+ 	// Set up the I/O functions.
diff -Nru nvidia-texture-tools-2.0.8-1+dfsg/debian/patches/series nvidia-texture-tools-2.0.8-1+dfsg/debian/patches/series
--- nvidia-texture-tools-2.0.8-1+dfsg/debian/patches/series	2015-12-08 07:51:31.0 +
+++ nvidia-texture-tools-2.0.8-1+dfsg/debian/patches/series	2016-09-19 12:30:02.0 +
@@ -11,3 +11,4 @@
 11-arm64-support.patch
 12-fix-simd-warning.patch
 13-typos.patch
+14-gcc6.patch


signature.asc
Description: OpenPGP digital signature

Bug#836628: marked as done (gsmartcontrol: please drop the build dependency on hardening-wrapper)

[Debian Bug Tracking System]

Your message dated Mon, 19 Sep 2016 12:19:04 +
with message-id 
and subject line Bug#836628: fixed in gsmartcontrol 0.8.7-1.2
has caused the Debian Bug report #836628,
regarding gsmartcontrol: please drop the build dependency on hardening-wrapper
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.)


-- 
836628: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=836628
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: gsmartcontrol
Version: 0.8.7-1.1
Severity: important
Tags: sid stretch
User: debian-...@lists.debian.org
Usertags: hardening-wrapper

This package builds using the hardening-wrapper package, which
is now replaced by dpkg-dev's DEB_BUILD_MAINT_OPTIONS settings.

Please consider dropping the build dependency of hardening-wrapper
and use the DEB_BUILD_MAINT_OPTIONS settings.

The goal is to remove hardening-wrapper for the stretch release.
Discussion about the removal is tracked in https://bugs.debian.org/836162

The severity of this report is likely to be raised before the release,
so that the hardening-wrapper package can be removed for the release.
--- End Message ---
--- Begin Message ---
Source: gsmartcontrol
Source-Version: 0.8.7-1.2

We believe that the bug you reported is fixed in the latest version of
gsmartcontrol, 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.
Stephen Kitt  (supplier of updated gsmartcontrol 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 13:42:12 +0200
Source: gsmartcontrol
Binary: gsmartcontrol
Architecture: source
Version: 0.8.7-1.2
Distribution: unstable
Urgency: medium
Maintainer: Giuseppe Iuculano 
Changed-By: Stephen Kitt 
Description:
 gsmartcontrol - graphical user interface for smartctl
Closes: 769580 836628
Changes:
 gsmartcontrol (0.8.7-1.2) unstable; urgency=medium
 .
   * Non-maintainer upload.
   * Use DEB_BUILD_MAINT_OPTIONS with short-form dh instead of
 hardening-wrapper. Closes: #836628.
   * Update the homepage. Closes: #769580.
   * Pull in 05_fix_ATA_version.patch from Ubuntu (thanks to Bart P.). LP:
 #1310282.
Checksums-Sha1:
 76aa332cb09ce683f218a7746c2920d1027bc4b6 1992 gsmartcontrol_0.8.7-1.2.dsc
 a8895472981184d9da078fdc0737d670708a4e8b 8988 
gsmartcontrol_0.8.7-1.2.debian.tar.xz
Checksums-Sha256:
 2ffba85331c4816e604b2fb9ea8612e8e08e4a49186b62967b2bb6df86f07a62 1992 
gsmartcontrol_0.8.7-1.2.dsc
 dee355be9b3a2ec84978b5b63d25d41774fcbb897e2eb60470f4dab0e41b0e2d 8988 
gsmartcontrol_0.8.7-1.2.debian.tar.xz
Files:
 ab9cc80c342fd726e3bacc2138f70b5c 1992 utils extra gsmartcontrol_0.8.7-1.2.dsc
 714c64be88fef6e786d1f65ea8967e04 8988 utils extra 
gsmartcontrol_0.8.7-1.2.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQIuBAEBCgAYBQJX1pYHERxza2l0dEBkZWJpYW4ub3JnAAoJEIDTAvWIbYOcJi8P
+wXKHg8KCX0XXu9KnZgJRbY+f0y+LlIEgFJcqRD+whi9y2o7/MYaLiacg/MLw3Yy
g0ZbDtypAf/tUxpmrU2cAGDolvccC+g6JCq1szyudHqCoquTNa3KLig1yVSIm9gv
HMfOlPe+fv69JhKfs59wWXID0G9uwUXypRKDcE96eImKGwFW0CwrQn+JAjeRJBgx
rVcr+RykE/rVobhgCfzrSNBSLV3jLuqknUYjzsl4MoDS9/Xc86AY6P8Ief9+K399
9IHJoAh+DPnHTLsAg92k9LvgTd5KhaKF/upbjxb9Wxk3j6KPPXMPq8MBJ7mMIMRC
IIZGdtpV/zmCc0uf6LahFum57b0kRlAvqLE2ZUIs5xz9RyDpbAZpJSujzY4OZ9Rs
850m7GQEdl3lK8qQul5y/HSVSlVG1MbY1knNDWM+AzAymDw9Oj6qrgMlgQS1A75k
ZGMLERxM9dDH6Z1/O5sU8xreVAJ5/qvC986aQLci1ZsnC52DkkhkqS1g/9GN/wWf
r4D5qrTzorBlBr1nA02UWfJDSAsJTjMShuI/26yjgjDHN6084qXd+XLs46C5Vs0w
/hD+8yikbecw6tCTL94DAFBFW15sW4EsnyLVYQL6AAGQz8A6MBd67C2TSag2rlw/
+ufVUji3zlXvp7Wni4hdtkBZjL47nO5ribnvyAANVRlL
=Gn5K
-END PGP SIGNATURE End Message ---

Processed: shadow: diff for NMU version 1:4.2-3.2

[Debian Bug Tracking System]

Processing control commands:

> tags 836653 + pending
Bug #836653 [src:shadow] shadow: please drop the build dependency on 
hardening-wrapper
Bug #837079 [src:shadow] shadow: src:shadow FTBFS due to conflicting 
hardening-wrapper
Added tag(s) pending.
Added tag(s) pending.

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

Bug#836653: shadow: diff for NMU version 1:4.2-3.2

[Mattia Rizzolo]

Control: tags 836653 + pending

Dear maintainer,

I've prepared an NMU for shadow (versioned as 1:4.2-3.2) and
uploaded it to DELAYED/1. Please feel free to tell me if I
should delay it longer.

Regards.

-- 
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  `-
diff -Nru shadow-4.2/debian/changelog shadow-4.2/debian/changelog
--- shadow-4.2/debian/changelog	2015-11-12 14:33:56.0 +
+++ shadow-4.2/debian/changelog	2016-09-18 14:42:16.0 +
@@ -1,3 +1,12 @@
+shadow (1:4.2-3.2) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * Use HTTPS in Vcs-Git.
+  * Stop using hardening-wrapper and instead use /usr/share/dpkg/buildflags.mk.
+Closes: #836653
+
+ -- Mattia Rizzolo   Sun, 18 Sep 2016 14:42:16 +
+
 shadow (1:4.2-3.1) unstable; urgency=medium
 
   * Non-maintainer upload.
diff -Nru shadow-4.2/debian/control shadow-4.2/debian/control
--- shadow-4.2/debian/control	2014-11-19 20:49:09.0 +
+++ shadow-4.2/debian/control	2016-09-18 14:32:24.0 +
@@ -5,9 +5,8 @@
 Standards-Version: 3.9.5
 Uploaders: Christian Perrier , Nicolas FRANCOIS (Nekral) 
 Build-Depends: dh-autoreconf, gettext, libpam0g-dev, debhelper (>= 6.0.7~), quilt, dpkg-dev (>= 1.13.5), xsltproc, docbook-xsl, docbook-xml, libxml2-utils, cdbs, libselinux1-dev [linux-any], libsemanage1-dev [linux-any], gnome-doc-utils (>= 0.4.3), bison, libaudit-dev [linux-any]
- ,hardening-wrapper
-Vcs-Git: git://anonscm.debian.org/git/pkg-shadow/shadow.git
-Vcs-Browser: http://anonscm.debian.org/gitweb/?p=pkg-shadow/shadow.git;a=summary
+Vcs-Git: https://anonscm.debian.org/git/pkg-shadow/shadow.git
+Vcs-Browser: https://anonscm.debian.org/git/pkg-shadow/shadow.git
 Homepage: http://pkg-shadow.alioth.debian.org/
 
 Package: passwd
diff -Nru shadow-4.2/debian/rules shadow-4.2/debian/rules
--- shadow-4.2/debian/rules	2014-11-19 20:49:09.0 +
+++ shadow-4.2/debian/rules	2016-09-18 14:41:28.0 +
@@ -3,10 +3,10 @@
 
 DEB_HOST_ARCH_OS := $(shell dpkg-architecture -qDEB_HOST_ARCH_OS)
 
-export DEB_BUILD_HARDENING=1
-
 # Enable PIE, BINDNOW, and possible future flags.
 export DEB_BUILD_MAINT_OPTIONS = hardening=+all
+DPKG_EXPORT_BUILDFLAGS = 1
+include /usr/share/dpkg/buildflags.mk
 
 # Call autoreconf since we need to regenerate all the autofoo files
 include /usr/share/cdbs/1/rules/autoreconf.mk


signature.asc
Description: PGP signature

Bug#835708: plplot: FTBFS: cairo-related files are no more built

[Axel Beckert]

Hi Ole,

Ole Streicher wrote:
> I compared the current build log with one of the original build logs.

Thanks a lot!

> So, for some reason, the pango libraries are not found anymore.

It seems worse: They're not (properly) looked for anymore (diff marks added
and ordered manually):

- -- Checking for module 'pango'
+ -- Checking for modules ''
+ Must specify package names on the command line [... repeated 14 times)
- --   Found pango, version 1.40.1
+ -- WARNING: pkg-config does not find pango.
- -- Checking for module 'pangoft2'
+ -- Checking for modules ''
+ Must specify package names on the command line [... repeated 14 times]
- --   Found pangoft2, version 1.40.1
+ -- WARNING: pkg-config does not find pangoft2.

So I suspect that already the part which is trying to find some
libraries fails itself by correctly specifying them.

Which again brings us back to the cmake update from 3.6.1-1 to 3.6.2-1
on 27-August-2016...

> pango1.0 1.40.2-1 was uploaded on 2016-08-30 (so, after the bug
> report). However, this may give a hint where to look next...

Will have another look at later then.

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

Bug#838281: parcimonie: FTBFS in testing (failing tests)

[Santiago Vila]

Comment: It may be argued that the current set of build-depends make
backporting easier, but this line

* Add {build,runtime} dependency on dirmngr, that's needed for network
operations with GnuPG 2.1+.

suggest to me that this package is definitely only intended to work
with gnupg >= 2.1.

Thanks.

Bug#836614: animals sponsoring

[Patrick Matthäi]

Hi,

I am around, just a little bit busy but I did not forget it. I will give
you this week some feedback


Am 19.09.2016 um 12:43 schrieb alberto fuentes:
> This is the second time since I got this package 3 years ago that my
> mentor has to make an upload, so Im not sure hes around :)
>
> I messaged him privately a week ago, but im also putting it here in
> case somebody else can review the fix in this package since the
> severity has been raised
>
> Im sorry is not not a one liner to make easier the review, but I think
> its not very large fix either. I did switch to dh which I believe auto
> applies the hardening
>
> I also did some extra maintenance like dropping the -dbg package which
> I believe it auto generates the new -dbgsym packages
>
> you can review it here:
>
> https://mentors.debian.net/debian/pool/main/a/animals/animals_201207131226-2.dsc
> 
> https://mentors.debian.net/package/animals
> 
>
> Thanks!

-- 
/*
Mit freundlichem Gruß / With kind regards,
 Patrick Matthäi
 GNU/Linux Debian Developer

  Blog: http://www.linux-dev.org/
E-Mail: pmatth...@debian.org
patr...@linux-dev.org
*/

Bug#838281: parcimonie: FTBFS in testing (failing tests)

[Santiago Vila]

Package: src:parcimonie
Version: 0.10.2-2
Severity: serious

Dear maintainer:

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


[...]
 debian/rules build-indep
dh build-indep
   dh_testdir -i
   dh_update_autotools_config -i
   dh_auto_configure -i
perl -I. Build.PL --installdirs vendor --config "optimize=-g -O2 
-fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat 
-Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2" --config 
"ld=x86_64-linux-gnu-gcc -g -O2 -fdebug-prefix-map=/<>=. 
-fstack-protector-strong -Wformat -Werror=format-security -Wl,-z,relro"
Checking prerequisites...
  requires:
!  File::ShareDir is not installed

ERRORS/WARNINGS FOUND IN PREREQUISITES.  You may wish to install the versions
of the modules indicated above before proceeding with this installation

Run 'Build installdeps' to install missing prerequisites.

Created MYMETA.yml and MYMETA.json
Creating new 'Build' script for 'App-Parcimonie' version '0.10.2'
   debian/rules override_dh_auto_build
make[1]: Entering directory '/<>'
pandoc --read=markdown --write=man --output=parcimonie-torified-gpg.1 
--standalone parcimonie-torified-gpg.1.markdown
dh override_dh_auto_build
make[1]: Leaving directory '/<>'
   debian/rules override_dh_auto_test
make[1]: Entering directory '/<>'
xvfb-run -a dh_auto_test
perl Build test --verbose 1
Copying lib/App/Parcimonie/DBus/Object.pm -> 
blib/lib/App/Parcimonie/DBus/Object.pm
Copying lib/App/Parcimonie/Role/HasCodeset.pm -> 
blib/lib/App/Parcimonie/Role/HasCodeset.pm
Copying lib/App/Parcimonie/Role/HasEncoding.pm -> 
blib/lib/App/Parcimonie/Role/HasEncoding.pm
Copying lib/App/Parcimonie.pm -> blib/lib/App/Parcimonie.pm
Copying lib/App/Parcimonie/GnuPG/Interface.pm -> 
blib/lib/App/Parcimonie/GnuPG/Interface.pm
Copying lib/App/Parcimonie/Applet.pm -> blib/lib/App/Parcimonie/Applet.pm
Copying lib/App/Parcimonie/Daemon.pm -> blib/lib/App/Parcimonie/Daemon.pm
Copying share/applications/parcimonie-applet.desktop -> 
blib/lib/auto/share/dist/App-Parcimonie/applications/parcimonie-applet.desktop
Copying share/applications/parcimonie.desktop -> 
blib/lib/auto/share/dist/App-Parcimonie/applications/parcimonie.desktop
Copying bin/parcimonie-torified-gpg -> blib/script/parcimonie-torified-gpg
Copying bin/parcimonie-applet -> blib/script/parcimonie-applet
Changing sharpbang in blib/script/parcimonie-applet to /usr/bin/perl
Deleting blib/script/parcimonie-applet.bak
Copying bin/parcimonie -> blib/script/parcimonie
Changing sharpbang in blib/script/parcimonie to /usr/bin/perl
Deleting blib/script/parcimonie.bak
Too late to run INIT block at 
/usr/lib/x86_64-linux-gnu/perl5/5.22/Glib/Object/Introspection.pm line 257.
t/00-load_all.t ... 
ok 1 - use App::Parcimonie::Applet;
ok 2 - use App::Parcimonie::DBus::Object;
ok 3 - use App::Parcimonie::Daemon;
ok 4 - use App::Parcimonie::GnuPG::Interface;
ok 5 - use App::Parcimonie::Role::HasCodeset;
ok 6 - use App::Parcimonie::Role::HasEncoding;
1..6
ok
Can't exec "gpg": No such file or directory at 
/usr/share/perl5/GnuPG/Interface.pm line 301.
exec() error: No such file or directory at /usr/share/perl5/GnuPG/Interface.pm 
line 301.

#   Failed test at t/05-init-keyring.t line 51.
Can't exec "gpg": No such file or directory at 
/usr/share/perl5/GnuPG/Interface.pm line 301.
exec() error: No such file or directory at /usr/share/perl5/GnuPG/Interface.pm 
line 301.

#   Failed test at t/05-init-keyring.t line 52.
Can't exec "gpg": No such file or directory at t/05-init-keyring.t line 53.

#   Failed test 'updated GnuPG trustdb'
#   at t/05-init-keyring.t line 53.
#  got: '-1'
# expected: '0'
# Looks like you failed 3 tests of 3.
t/05-init-keyring.t ... 
1..3
not ok 1
not ok 2
not ok 3 - updated GnuPG trustdb
Dubious, test returned 3 (wstat 768, 0x300)
Failed 3/3 subtests 
t/30-pickRandomItems.t  
1..12
ok 1 - pickRandomItems sends an exception if N is not defined
ok 2 - pickRandomItems sends an exception if N is not an integer
ok 3 - pickRandomItems sends an exception if N is too big
ok 4 - pickRandomItems sends an exception if N is too big
ok 5 - pickRandomItems sends an exception if N>0 and empty input list
ok 6 - returns a list with N items
ok 7 - returns a list of unique items
ok 8 - returns a list with N items
ok 9 - returns a list of unique items
ok 10 - returns the empty list when N=0
ok 11 - returns the empty list when N=0
ok 12 - returns the empty list when N=0 and empty input list
ok
ERROR: gpg cannot be found.

#   Failed test 'There are 2 public keys in the keyring.'
#   at t/31-gpgPublicKeys.t line 16.
#  got: '0'
# expected: '2'
# Looks like you failed 1 test of 1.
t/31-gpgPublicKeys.t .. 
1..1
not ok 1 - There are 2 public keys in the keyring.

Bug#808634: cadabra in Debian

[Axel Beckert]

Hi Kasper,

Kasper Peeters wrote:
> I have just tried building cadabra 1.45 on a fresh install of Testing,
> so that's with gcc 6.1.1 (not using the pbuilder, but direct on the
> hardware). No problem. Any idea why it doesn't build on your machine
> but does on mine?

Thanks for testing. Will check.

I tried on Unstable and Unstable has gcc 6.2.0 for a few weeks now and
it seems to have migrated to testing just today (around noon
probably), so that could be a potential reason. (And currently the
only one which comes to my mind at the moment.)

You should get it on Testing now, too, if you do an "apt-get update;
apt-get dist-upgrade" on your Testing machine (and you mirror has
already synced).

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

Bug#837294: marked as done (postgresql-9.5-postgis-2.3-scripts: fails to upgrade from 'sid' - trying to overwrite /usr/share/postgresql/9.5/extension/address_standardizer.control)

[Debian Bug Tracking System]

Your message dated Mon, 19 Sep 2016 11:27:42 +
with message-id 
and subject line Bug#837294: fixed in postgis 2.3.0~rc1+dfsg-1~exp1
has caused the Debian Bug report #837294,
regarding postgresql-9.5-postgis-2.3-scripts: fails to upgrade from 'sid' - 
trying to overwrite 
/usr/share/postgresql/9.5/extension/address_standardizer.control
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.)


-- 
837294: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=837294
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: postgresql-9.5-postgis-2.3-scripts
Version: 2.3.0~beta1+dfsg-1~exp1
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 postgresql-9.5-postgis-2.3-scripts.
  Preparing to unpack 
.../1-postgresql-9.5-postgis-2.3-scripts_2.3.0~beta1+dfsg-1~exp1_all.deb ...
  Unpacking postgresql-9.5-postgis-2.3-scripts (2.3.0~beta1+dfsg-1~exp1) ...
  dpkg: error processing archive 
/tmp/apt-dpkg-install-gbqKla/1-postgresql-9.5-postgis-2.3-scripts_2.3.0~beta1+dfsg-1~exp1_all.deb
 (--unpack):
   trying to overwrite 
'/usr/share/postgresql/9.5/extension/address_standardizer.control', which is 
also in package postgresql-9.5-postgis-2.2-scripts 2.2.2+dfsg-5
  dpkg-deb: error: subprocess paste was killed by signal (Broken pipe)
  Errors were encountered while processing:
   
/tmp/apt-dpkg-install-gbqKla/1-postgresql-9.5-postgis-2.3-scripts_2.3.0~beta1+dfsg-1~exp1_all.deb


cheers,

Andreas


postgresql-9.5-postgis-2.2-scripts=2.2.2+dfsg-5_postgresql-9.5-postgis-2.3-scripts=2.3.0~beta1+dfsg-1~exp1.log.gz
Description: application/gzip
--- End Message ---
--- Begin Message ---
Source: postgis
Source-Version: 2.3.0~rc1+dfsg-1~exp1

We believe that the bug you reported is fixed in the latest version of
postgis, 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.
Bas Couwenberg  (supplier of updated postgis 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, 19 Sep 2016 11:33:41 +0200
Source: postgis
Binary: postgis postgis-gui postgis-doc liblwgeom-2.3-0 liblwgeom-dev 
postgresql-9.5-postgis-2.3 postgresql-9.5-postgis-2.3-scripts 
postgresql-9.5-postgis-scripts
Architecture: source amd64 all
Version: 2.3.0~rc1+dfsg-1~exp1
Distribution: experimental
Urgency: medium
Maintainer: Debian GIS Project 
Changed-By: Bas Couwenberg 
Description:
 liblwgeom-2.3-0 - PostGIS "Lightweight Geometry" library
 liblwgeom-dev - PostGIS "Lightweight Geometry" library - Development files
 postgis- Geographic objects support for PostgreSQL
 postgis-doc - Geographic objects support for PostgreSQL -- documentation
 postgis-gui - Geographic objects support for PostgreSQL -- GUI programs
 postgresql-9.5-postgis-2.3 - Geographic objects support for PostgreSQL 9.5
 postgresql-9.5-postgis-2.3-scripts - Geographic objects support for PostgreSQL 
9.5 -- scripts
 postgresql-9.5-postgis-scripts - transitional dummy package
Closes: 837294
Changes:
 postgis (2.3.0~rc1+dfsg-1~exp1) experimental; urgency=medium
 .
   * New upstream release candidate.
   * Add Conficts on postgresql-9.5-postgis-2.2-scripts to 2.3-scripts package.
 (closes: #837294)
   * Drop run_test-INC.patch, applied upstream. Refresh remaining patches.
   * Add license & copyright for debian/* in copyright file.
   * Update symbols for 2.3.0~rc1.
Checksums-Sha1:
 85f6848abeeec6d6988c11f274ccb694e47141d5 3049 postgis_2.3.0~rc1+dfsg-1~exp1.dsc
 2788464490f5c2b7e48390729ea6ad965f7bae06 11459672 
postgis_2.3.0~rc1+dfsg.orig.tar.gz
 

Processed: Re: Bug#811612: FTBFS with GCC 6: cannot convert x to y

[Debian Bug Tracking System]

Processing control commands:

> tags 811612 +fixed-upstream
Bug #811612 [nvidia-texture-tools] FTBFS with GCC 6: cannot convert x to y
Added tag(s) fixed-upstream.
> tags 811612 +patch
Bug #811612 [nvidia-texture-tools] FTBFS with GCC 6: cannot convert x to y
Added tag(s) patch.

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

Bug#811612: FTBFS with GCC 6: cannot convert x to y

[Adrian Bunk]

Control: tags 811612 +fixed-upstream
Control: tags 811612 +patch

On Wed, Jan 20, 2016 at 11:14:09PM +0100, Lennart Weller wrote:
> On 20.01.2016 18:30, Martin Michlmayr wrote
> > This builds fine.
> Nice. So I either just have to add the patches for 2.0.8 or get 0ad to work
> with 2.1.0. I'll look into that in the next few days as time permits.
>...

This bug is the reason why 0ad is not in testing, and if it doesn't get 
fixed then 0ad will not be in the next Debian stable. 

I've attached the trivial fix.

> Lennart

cu
Adrian

-- 

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

Description: Fix building with gcc 6

--- nvidia-texture-tools-2.0.8-1+dfsg.orig/src/nvimage/ImageIO.cpp
+++ nvidia-texture-tools-2.0.8-1+dfsg/src/nvimage/ImageIO.cpp
@@ -135,7 +135,7 @@ FloatImage * nv::ImageIO::loadFloat(cons
 	StdInputStream stream(fileName);
 	
 	if (stream.isError()) {
-		return false;
+		return NULL;
 	}
 	
 	return loadFloat(fileName, stream);
@@ -233,7 +233,7 @@ Image * nv::ImageIO::loadTGA(Stream & s)
 		case TGA_TYPE_INDEXED:
 			if( tga.colormap_type!=1 || tga.colormap_size!=24 || tga.colormap_length>256 ) {
 nvDebug( "*** ImageIO::loadTGA: Error, only 24bit paletted images are supported.\n" );
-return false;
+return NULL;
 			}
 			pal = true;
 			break;
@@ -254,7 +254,7 @@ Image * nv::ImageIO::loadTGA(Stream & s)
 
 		default:
 			nvDebug( "*** ImageIO::loadTGA: Error, unsupported image type.\n" );
-			return false;
+			return NULL;
 	}
 
 	const uint pixel_size = (tga.pixel_size/8);
@@ -621,7 +621,7 @@ Image * nv::ImageIO::loadPNG(Stream & s)
 	png_ptr = png_create_read_struct(PNG_LIBPNG_VER_STRING, NULL, NULL, NULL);
 	if (png_ptr == NULL) {
 	//	nvDebug( "*** LoadPNG: Error allocating read buffer in file '%s'.\n", name );
-		return false;
+		return NULL;
 	}
 
 	// Allocate/initialize a memory block for the image information
@@ -629,14 +629,14 @@ Image * nv::ImageIO::loadPNG(Stream & s)
 	if (info_ptr == NULL) {
 		png_destroy_read_struct(_ptr, NULL, NULL);
 	//	nvDebug( "*** LoadPNG: Error allocating image information for '%s'.\n", name );
-		return false;
+		return NULL;
 	}
 
 	// Set up the error handling
 	if (setjmp(png_jmpbuf(png_ptr))) {
 		png_destroy_read_struct(_ptr, _ptr, NULL);
 	//	nvDebug( "*** LoadPNG: Error reading png file '%s'.\n", name );
-		return false;
+		return NULL;
 	}
 
 	// Set up the I/O functions.

Bug#808634: cadabra in Debian

[Kasper Peeters]

Hi Axel,

I have just tried building cadabra 1.45 on a fresh install of Testing,
so that's with gcc 6.1.1 (not using the pbuilder, but direct on the
hardware). No problem. Any idea why it doesn't build on your machine
but does on mine?

Cheers,
Kasper

Bug#838278: gnustep-make: FTBFS in testing (@setcontentsaftertitlepage no longer works)

[Santiago Vila]

Package: src:gnustep-make
Version: 2.6.8-2
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:


[...]
./gnustep-howto.texi:8: @setcontentsaftertitlepage has been removed as a Texinf
o command; move your @contents command if you want the contents after the title
 page..
@setcontentsaftertitlepage ...ter the title page.}
  
l.8 @setcontentsaftertitlepage
  
? 
./gnustep-howto.texi:8: Emergency stop.
@setcontentsaftertitlepage ...ter the title page.}
  
l.8 @setcontentsaftertitlepage
  
./gnustep-howto.texi:8:  ==> Fatal error occurred, no output PDF file produced!
Transcript written on gnustep-howto.log.


The relevant part of the build is included.

In addition to this, the build continues after this TeX failure, and
the target which fails is really binary-indep. That should not really
happen. If the build fails, it's the build-indep target the one that
should fail.

Thanks.

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

[Axel Beckert]

Hi Michael,

Michael Crusoe wrote:
> > > On Tue, Aug 18, 2015 at 06:26:06PM +0200, Christian Hofstaedtler wrote:
> > > - something else can replace ruby-ronn and we manage to make reverse
> > >   (build) dependencies switch to it.
> >
> > Before starting to use ronn in an official release of
> > unburden-home-dir, I tried different tools and was very unsatisfied:
> >
> > * go-md2man
> > * pandoc
> >
> > There is also https://github.com/sunaku/md2man which is not yet
> > packaged. Haven't tried that one yet since it requires a newer version
> > of rubygems (2.5.2) than in Debian Unstable (2.5.1):
> > https://github.com/sunaku/binman/issues/4
> 
> For the jaligner package we had a good experience with asciidoctor program
> 
> http://sources.debian.net/src/jaligner/1.0%2Bdfsg-4/debian/jaligner.adoc/

Thanks for that hint.

That would though mean to switch the man page source format from the
Markdown format to the AsciiDoc format, which might have other
impacts, like e.g. publishing on ReadTheDocs, GitBooks (supports
AsciiDoc only as 2nd class citizen and no adoc/md mixed contents), or
GitHub Pages with Jekyll (does not work for me currently anyway, but
still), etc.:

http://unburden-home-dir.readthedocs.io/en/latest/unburden-home-dir.1/index.html
https://xtaran.gitbooks.io/unburden-home-dir/content/docs/unburden-home-dir.1.html

But if switching the format would be an option, I'd switch to Perl's
POD as that converts very well and out-of-the-box to man pages.

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

Bug#838273: libmail-gnupg-perl: FTBFS in testing (failing tests)

[Santiago Vila]

I found this, maybe you can skip the build log in full and consider
only this single line:

sh: 1: gpg2: not found

Thanks.

Bug#838273: libmail-gnupg-perl: FTBFS in testing (failing tests)

[Santiago Vila]

I should better provide the full build log just in case.
Here it is.

Thanks.


libmail-gnupg-perl_0.23-1_amd64-20160919T104001Z.gz
Description: application/gzip

Bug#836614:

[alberto fuentes]

This is the second time since I got this package 3 years ago that my mentor
has to make an upload, so Im not sure hes around :)

I messaged him privately a week ago, but im also putting it here in case
somebody else can review the fix in this package since the severity has
been raised

Im sorry is not not a one liner to make easier the review, but I think its
not very large fix either. I did switch to dh which I believe auto applies
the hardening

I also did some extra maintenance like dropping the -dbg package which I
believe it auto generates the new -dbgsym packages

you can review it here:

https://mentors.debian.net/debian/pool/main/a/animals/
animals_201207131226-2.dsc
https://mentors.debian.net/package/animals

Thanks!

Processed: tcpcopy FTBFS is fixed upstream

[Debian Bug Tracking System]

Processing control commands:

> tags 835591 +fixed-upstream
Bug #835591 [src:tcpcopy] tcpcopy: FTBFS: xcopy.h:14:43: fatal error: 
linux/netfilter_ipv4/ip_queue.h: No such file or directory
Added tag(s) fixed-upstream.

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

Bug#835591: tcpcopy FTBFS is fixed upstream

[Adrian Bunk]

Control: tags 835591 +fixed-upstream

The FTBFS is fixed in upstream 1.0.0

cu
Adrian

-- 

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

Bug#837759: network configuration stops working reliably

[Wolfgang Walter]

Hello Martin,

On Monday, 19 September 2016 11:02:08 CEST Martin Pitt wrote:
> Hello Wolfgang,
> 
> Wolfgang Walter [2016-09-14 23:34 +0200]:
> > > > I tested this with a script:
> FTR, I tried this as welll, and I cannot reproduce the bug either.
> 
> Wolfgang Walter [2016-09-14 17:56 +0200]:
> > Yes, systemd-networkd ist active. But on most machines I only have *.link
> 
> > entries, usually one to name the device:
> *.link entries are handled by udev, not networkd. So if you can
> reproduce this on a machine with only has files like
> 
> > ==
> > [Match]
> > MACAddress=11:22:33:44:55:66
> > 
> > [Link]
> > Name=net
> > WakeOnLan=off
> > ==
> 
> then can you please "systemctl disable --now systemd-networkd" and
> check if the problem still happens? I suppose not, but if so, this
> tells us that this is being done through udev.

When I disable systemd-networkd the problem disappears.

The reason I think it is a race is because it depends on how many interfaces 
you set up, if you use systemd-networkd to setup some interfaces and the number 
of ip-addresses and things you do in /etc/network/interfaces.

For example on that simple machines where I only have *.link and don't use 
systemd-networkd: sometimes (maybe 2 out of 10) it works, but most of the time 
I loose some or all ip-adresses.

Here is the log (without) debugging: in this case the interface only kept the 
IPv6 addresses and lost its ipv4 address, all set up in /etc/network/interfaces.

Sep 19 11:33:25 maiskolben systemd[1]: Starting Raise network interfaces...
Sep 19 11:33:25 maiskolben systemd[1]: Starting Network Service...
Sep 19 11:33:26 maiskolben systemd-networkd[480]: Enumeration completed
Sep 19 11:33:26 maiskolben systemd-networkd[480]: net: Lost carrier
Sep 19 11:33:26 maiskolben systemd-networkd[480]: net: Gained carrier
Sep 19 11:33:26 maiskolben systemd[1]: Started Network Service.
Sep 19 11:33:27 maiskolben systemd-networkd[480]: net: Gained IPv6LL
Sep 19 11:33:27 maiskolben ifup[352]: Waiting for DAD... Done
Sep 19 11:33:27 maiskolben systemd[1]: Started Raise network interfaces.

But there is nothing special about ipv4-addresses. With more interfaces one may 
loose some or all of the ipv6 adresses, too.

I think the crucial point is that systemd-networkd may declares the interface 
"net" unamanaged AFTER "net: Lost carrier" so that all addresses confgured 
until that point are ripped off.

This " Lost carrier" is always there on startup, don't know if this is caused 
by udev when it detects the interface on startup.


Here is the log with systemd-networkd disabled:

Sep 19 11:37:20 maiskolben systemd[1]: Starting Raise network interfaces...
Sep 19 11:37:22 maiskolben ifup[400]: Waiting for DAD... Done
Sep 19 11:37:23 maiskolben systemd[1]: Started Raise network interfaces.


> 
> If networkd itself is really the culprit, can you please try the
> following:
> 
>  * Keep it disabled, run your test.sh to set up the dummy interface,
>and run
> 
>  SYSTEMD_LOG_LEVEL=debug /lib/systemd/systemd-networkd
> 
>   (as root). Does this now cause the addresses to be removed? This
>   will run much later than test.sh, so this will tell us if this is a
>   principal logic error or a race condition, i. e. only happens if
>   networkd starts at the right time after test.sh.

No, I don't loose any addresses then. But as you see there is no such "net: 
Lost carrier" or "TEST: Lost carrier" and so on.

SYSTEMD_LOG_LEVEL=debug /lib/systemd/systemd-networkd
Found container virtualization none
Sent message type=method_call sender=n/a destination=org.freedesktop.DBus 
object=/org/freedesktop/DBus interface=org.freedesktop.DBus member=Hello 
cookie=1 reply_cookie=0 error=n/a
Got message type=method_return sender=org.freedesktop.DBus destination=:1.3 
object=n/a interface=n/a member=n/a cookie=1 reply_cookie=1 error=n/a
Sent message type=method_call sender=n/a destination=org.freedesktop.DBus 
object=/org/freedesktop/DBus interface=org.freedesktop.DBus member=AddMatch 
cookie=2 reply_cookie=0 error=n/a
Got message type=method_return sender=org.freedesktop.DBus destination=:1.3 
object=n/a interface=n/a member=n/a cookie=3 reply_cookie=2 error=n/a
Sent message type=method_call sender=n/a destination=org.freedesktop.DBus 
object=/org/freedesktop/DBus interface=org.freedesktop.DBus member=RequestName 
cookie=3 reply_cookie=0 error=n/a
Got message type=method_return sender=org.freedesktop.DBus destination=:1.3 
object=n/a interface=n/a member=n/a cookie=5 reply_cookie=3 error=n/a
Failed to open configuration file '/etc/systemd/networkd.conf': No such file or 
directory
timestamp of '/etc/systemd/network' changed
timestamp of '/lib/systemd/network' changed
TEST: Flags change: +UP +LOWER_UP +RUNNING +BROADCAST +NOARP
Sent message type=signal sender=n/a destination=n/a 
object=/org/freedesktop/network1/link/_34 
interface=org.freedesktop.DBus.Properties member=PropertiesChanged cookie=4 
reply_cookie=0 error=n/a

Bug#838273: libmail-gnupg-perl: FTBFS in testing (failing tests)

[Santiago Vila]

Package: src:libmail-gnupg-perl
Version: 0.23-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
   dh_testdir -i
   dh_update_autotools_config -i
   dh_auto_configure -i
perl -I. Build.PL --installdirs vendor --config "optimize=-g -O2 
-fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat 
-Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2" --config 
"ld=x86_64-linux-gnu-gcc -g -O2 -fdebug-prefix-map=/<>=. 
-fstack-protector-strong -Wformat -Werror=format-security -Wl,-z,relro"
Created MYMETA.yml and MYMETA.json
Creating new 'Build' script for 'Mail-GnuPG' version '0.23'
   dh_auto_build -i
perl Build
Building Mail-GnuPG
   debian/rules override_dh_auto_test
make[1]: Entering directory '/<>'
chmod a+x t/fake-pinentry.pl
dh_auto_test
perl Build test --verbose 1
t/00.signature.t . skipped: Set the environment variable TEST_SIGNATURE 
to enable this test.
t/05.load.t .. 
1..1
ok 1 - use Mail::GnuPG;
ok
t/20.inline-verify.t . 
gpg: keyring `mgtwUFmz/secring.gpg' created
gpg: keyring `mgtwUFmz/pubring.gpg' created
gpg: mgtwUFmz/trustdb.gpg: trustdb created
gpg: key 7B75921E: public key "Antoine Beaupré " imported
gpg: key 784206AD: public key "David Bremner " imported
gpg: key 9456D16A: public key "Mauricio Campiglia " 
imported
gpg: Total number processed: 3
gpg:   imported: 3  (RSA: 2)
gpg: no ultimately trusted keys found
1..5
ok 1 - An object of class 'MIME::Entity' isa 'MIME::Entity'
ok 2 - An object of class 'Mail::GnuPG' isa 'Mail::GnuPG'
ok 3 - verify success
ok 4 - verify keyid
ok 5 - verify uid
ok
t/25.multipart-verify.t .. 
gpg: keyring `mgth3uMA/secring.gpg' created
gpg: keyring `mgth3uMA/pubring.gpg' created
gpg: mgth3uMA/trustdb.gpg: trustdb created
gpg: key 7B75921E: public key "Antoine Beaupré " imported
gpg: key 784206AD: public key "David Bremner " imported
gpg: key 9456D16A: public key "Mauricio Campiglia " 
imported
gpg: Total number processed: 3
gpg:   imported: 3  (RSA: 2)
gpg: no ultimately trusted keys found
1..5
ok 1 - An object of class 'MIME::Entity' isa 'MIME::Entity'
ok 2 - An object of class 'Mail::GnuPG' isa 'Mail::GnuPG'
ok 3 - verify success
ok 4 - verify keyid
ok 5 - verify uid
ok
t/30.inline-decrypt.t  
1..5
ok 1 - An object of class 'MIME::Entity' isa 'MIME::Entity'
gpg: keyring `mgtItzND/secring.gpg' created
gpg: keyring `mgtItzND/pubring.gpg' created
gpg: key EFEA4EAD: secret key imported
gpg: mgtItzND/trustdb.gpg: trustdb created
gpg: key EFEA4EAD marked as ultimately trusted
gpg: key EFEA4EAD: public key "Mail::GnuPG Test Key " imported
gpg: key EFEA4EAD: "Mail::GnuPG Test Key " 1 new signature
gpg: Total number processed: 2
gpg:   imported: 1
gpg: new signatures: 1
gpg:   secret keys read: 1
gpg:   secret keys imported: 1
gpg: 3 marginal(s) needed, 1 complete(s) needed, PGP trust model
gpg: depth: 0  valid:   1  signed:   0  trust: 0-, 0q, 0n, 0m, 0f, 1u
ok 2 - An object of class 'Mail::GnuPG' isa 'Mail::GnuPG'
ok 3 - decrypt success
ok 4 - message unsigned
ok 5 - plaintext
ok
t/35.has-public-key.t  
gpg: keyring `mgtwmP26/secring.gpg' created
gpg: keyring `mgtwmP26/pubring.gpg' created
gpg: key EFEA4EAD: secret key imported
gpg: mgtwmP26/trustdb.gpg: trustdb created
gpg: key EFEA4EAD: public key "Mail::GnuPG Test Key " imported
gpg: key EFEA4EAD: "Mail::GnuPG Test Key " 1 new signature
gpg: Total number processed: 2
gpg:   imported: 1
gpg: new signatures: 1
gpg:   secret keys read: 1
gpg:   secret keys imported: 1
1..3
ok 1 - An object of class 'Mail::GnuPG' isa 'Mail::GnuPG'
ok 2 - public key exists
ok 3 - bogus key doesn't exist
ok
t/99.pod.t ... 
1..1
ok 1 - POD test for blib/lib/Mail/GnuPG.pm
ok
Unknown Content-Type or no PGP message in body at 
/<>/blib/lib/Mail/GnuPG.pm line 402.
# Looks like you planned 20 tests but ran 8.
# Looks like your test exited with 2 just after 8.
t/agent.t  
sh: 1: gpg2: not found
gpg-agent[26728]: gpg-agent running and available
gpg: key EFEA4EAD marked as ultimately trusted
gpg: 3 marginal(s) needed, 1 complete(s) needed, PGP trust model
gpg: depth: 0  valid:   1  signed:   0  trust: 0-, 0q, 0n, 0m, 0f, 1u
1..20
ok 1 - An object of class 'Mail::GnuPG' isa 'Mail::GnuPG' # TODO agent test 
unreliable with pre 2.11 gnupg
not ok 2 # TODO agent test unreliable with pre 2.11 gnupg
#   Failed (TODO) test at t/agent.t line 102.
#  got: '2'
# expected: '0'
not ok 3 # TODO agent test unreliable with pre 2.11 gnupg

# 

Bug#833969: Patch for the ganv FTBFS

[Adrian Bunk]

Control: tags 833969 +patch

A fix for the ganv FTBFS is attached.

cu
Adrian

-- 

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

Description: Don't build with -ansi
 -ansi is for C++ equivalent to -std=c++98
 .
 sigc++-2.0 uses C++11 features in its headers, resulting in
 compile errors when trying to use these headers in C++98 mode.
 .
 Removing -ansi fixes the bug, depending on upstream policy
 building with -std=c++11 (or -std=c++14) instead of -ansi
 might be preferred by upstream with gcc versions that
 support these standards (untested).
Author: Adrian Bunk 
Bug-Debian: https://bugs.debian.org/833969
Forwarded: no

--- ganv-1.4.2~dfsg0.orig/waflib/extras/autowaf.py
+++ ganv-1.4.2~dfsg0/waflib/extras/autowaf.py
@@ -181,7 +181,7 @@ def configure(conf):
 		conf.env.append_value('CXXFLAGS',['-Wcast-qual'])
 	if Options.options.strict:
 		conf.env.append_value('CFLAGS',['-pedantic','-Wshadow'])
-		conf.env.append_value('CXXFLAGS',['-ansi','-Wnon-virtual-dtor','-Woverloaded-virtual'])
+		conf.env.append_value('CXXFLAGS',['-Wnon-virtual-dtor','-Woverloaded-virtual'])
 		append_cxx_flags(['-Wall','-Wcast-align','-Wextra','-Wmissing-declarations','-Wno-unused-parameter','-Wstrict-overflow','-Wundef','-Wwrite-strings','-fstrict-overflow'])
 		if not conf.check_cc(fragment='''
 #ifndef __clang__

Bug#835708: plplot: FTBFS: cairo-related files are no more built

[Ole Streicher]

I compared the current build log with one of the original build logs.
The critical difference seems to be:

original build (take from arm64 log)


-- Checking for module 'pango'
--   Found pango, version 1.40.1
-- Checking for module 'pangoft2'
--   Found pangoft2, version 1.40.1
-- Found LTDL: /usr/lib/aarch64-linux-gnu/libltdl.so
-- LTDL_INCLUDE_DIR = /usr/include
-- LTDL_LIBRARY_DIR = /usr/lib/aarch64-linux-gnu
-- LTDL_LIBRARIES = /usr/lib/aarch64-linux-gnu/libltdl.so
-- Checking for module 'pangocairo'
--   Found pangocairo, version 1.40.1
-- Not a Windows platform so setting wincairo driver to OFF.


new build (private amd64 log)
=
-- Checking for modules ''
Must specify package names on the command line [... repeated 14 times)
-- WARNING: pkg-config does not find pango.
-- Checking for modules ''
Must specify package names on the command line [... repeated 14 times]
-- WARNING: pkg-config does not find pangoft2.
-- Found LTDL: /usr/lib/x86_64-linux-gnu/libltdl.so
-- LTDL_INCLUDE_DIR = /usr/include
-- LTDL_LIBRARY_DIR = /usr/lib/x86_64-linux-gnu
-- LTDL_LIBRARIES = /usr/lib/x86_64-linux-gnu/libltdl.so
-- Checking for modules ''
Must specify package names on the command line [... repeated 14 times]
includedir =
libdir =
linkflags =
cflags =
-- WARNING: pango and/or cairo not found with pkg-config.
   Disabling cairo drivers.  To enable these drivers you must install
   development versions of pango and cairo and/or set
   the environment variable PKG_CONFIG_PATH appropriately.
-- Not a Windows platform so setting wincairo driver to OFF.

So, for some reason, the pango libraries are not found anymore. pango1.0
1.40.2-1 was uploaded on 2016-08-30 (so, after the bug report). However,
this may give a hint where to look next...

Cheers

Ole

Processed: Patch for the ganv FTBFS

[Debian Bug Tracking System]

Processing control commands:

> tags 833969 +patch
Bug #833969 [src:ganv] ganv: FTBFS: gtkmm/widget.h:3212:9: error: 
'SignalProxy1' in namespace 'Glib' does not name a template type
Added tag(s) patch.

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

Bug#838272: opensurgsim: FTBFS (test failure) on powerpc

[Adrian Bunk]

Source: opensurgsim
Version: 0.6.0-6
Severity: serious

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

[  FAILED  ] 1 test, listed below:
[  FAILED  ] AllMatrixTests/5.MultiplyScalarMatrix, where TypeParam = 
Eigen::Matrix


I am sendind 3 separate bugs since the test failures on different
architectures look quite different and might be unrelated.

Bug#838271: opensurgsim: FTBFS (test failure) on arm64

[Adrian Bunk]

Source: opensurgsim
Version: 0.6.0-6
Severity: serious

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

[  FAILED  ] 1 test, listed below:
[  FAILED  ] RigidRepresentationTest.AddExternalGeneralizedForceExtraTermsTest


I am sendind 3 separate bugs since the test failures on different
architectures look quite different and might be unrelated.

Bug#838270: opensurgsim: FTBFS (test failure) on armel, armhf

[Adrian Bunk]

Source: opensurgsim
Version: 0.6.0-6
Severity: serious

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

The following tests FAILED:
  1 - SurgSimBlocksTest (OTHER_FAULT)
  2 - SurgSimCollisionTest (OTHER_FAULT)
  3 - SurgSimDataStructuresTest (OTHER_FAULT)
  4 - SurgSimDeviceFiltersTest (OTHER_FAULT)
  5 - IdentityPoseDeviceTest (OTHER_FAULT)
  8 - SurgSimFrameworkTest (OTHER_FAULT)
  9 - SurgSimGraphicsTest (OTHER_FAULT)
 11 - SurgSimMathTest (OTHER_FAULT)
 12 - SurgSimPhysicsTest (OTHER_FAULT)
Errors while running CTest


I am sendind 3 separate bugs since the test failures on different
architectures look quite different and might be unrelated.

Bug#838269: licensecheck: FTBFS in testing (failing tests)

[Santiago Vila]

Package: src:licensecheck
Version: 3.0.24-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
CDBS WARNING:  copyright-check disabled - licensecheck is missing.
test -x debian/rules
mkdir -p "."

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

set -e; LC_ALL=C.UTF-8 perl -Ilib bin/licensecheck --check '.*' --recursive 
--copyright --deb-fmt --ignore 
'^(debian/(changelog|copyright(|_hints|_newhints)))$' --lines 0 * | 
/usr/lib/cdbs/licensecheck2dep5 > debian/copyright_newhints
60 combinations of copyright and licensing found.
WARNING:New or changed notices discovered:

Copyright: -format/1.0/
  2016, Jonas Smedegaard.
  allow anyone who receives a copy of the Modified Version …
Copyright: Copyright (C) 2009 by Moritz Lenz and the SVG::Plot contributors 
(see file /
Copyright: Miodrag Milanovic
Copyright: 1994-2012, Lua.org, PUC-Rio"
  1994-2012, Lua.org, PUC-Rio.
Copyright: 2001, 2012, David Turner, Robert Wilhelm, and Werner Lemberg.
  2007-2008, Adam D. Barratt
  2012, Francesco Poli
  2016, Jonas Smedegaard
Copyright: -check =
  -perl (>=0.003)
  2016, Jonas Smedegaard 
Copyright: s ) or "*No copyright*" )
  s = uniq rs_keysort {$_} split /^/, $copyright;
  s and $opt->copyright;
  s/licenses; set to 0 to parse the whole file (and ignore --tail)',
Copyright: -like laws that apply to other kinds of
  2007, Free Software Foundation, Inc. 
   
  able work licensed under this
  are not
  disclaimer" for the program, if necessary.
  ed material outside their relationship with you.
  if you do
  permission, other than the making of an
  permission.
  treaty adopted on 20 December 1996, or
  2007-2008, Adam D. Barratt
  2012, Francesco Poli
  2016, Jonas Smedegaard
  s = copyright_optimistic( clean_cruft($cleaned_content) );
  s = copyright_optimistic( clean_cruft($cleaned_tail) );
  s and $license eq 'UNKNOWN' ) {
Copyright: -delimiter, including comma by default.";
  John Doe".";
  and license extraction."@en;
  block.";
  blocks method.";
  file format.";
  for recent changes.";
  info.";
  information (for nroff files).";
  owner to mention "and others".";
  owner when … and owners are specified on 2 or more lines…
  owner with email like i...@foo.com.";
  parsing from comment stripping and copyright serializing";
  s in a non-random order."^^dt:Change;
  sign and hyphen-minus.";
  sign unconditionally.";
  sign with option --deb-machine.";
  symbol with a hex escape so that the package builds using …
  ns…n};
Files: Changes
Copyright: -delimiter, including comma by default.
  blocks method.
  file format.
  for recent changes.
  parsing from comment stripping and
  serializing
  sign and
  sign unconditionally.
  sign with option --deb-machine.
Files: debian/control
Copyright: -perl (>=0.003),
Files: MANIFEST
Copyright: CREDITS
Files: SIGNATURE
Copyright: SHA1 e8673b9754c9d267cb2d35ea91540aaf24e30ac5 CREDITS

To fix the situation please do the following:
  1) Examine debian/copyright_* and referenced files
  2) Update debian/copyright as needed
  3) Replace debian/copyright_hints with debian/copyright_newhints
touch debian/stamp-copyright-check
touch debian/stamp-upstream-cruft
cd . && /usr/bin/perl -I. Makefile.PL NOECHO= INSTALLDIRS=vendor
Checking if your kit is complete...
Looks good
Generating a Unix-style Makefile
Writing Makefile for App::Licensecheck
Writing MYMETA.yml and MYMETA.json
/usr/bin/make -C . OPTIMIZE="-g -O2 -fdebug-prefix-map=/<>=. 
-fstack-protector-strong -Wformat -Werror=format-security -D_REENTRANT 
-D_GNU_SOURCE -DDEBIAN -fwrapv -fno-strict-aliasing -pipe -I/usr/local/include 
-D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64 -Wdate-time -D_FORTIFY_SOURCE=2 
-D_REENTRANT -D_GNU_SOURCE -DDEBIAN -fwrapv -fno-strict-aliasing -pipe 
-I/usr/local/include" LDDLFLAGS="-Wl,-z,relro -shared -L/usr/local/lib 
-fstack-protector-strong" all
make[1]: Entering directory '/<>'
"/usr/bin/perl" -MExtUtils::Command -e 'mkpath' -- blib/lib/App
chmod 755 blib/lib/App
touch blib/lib/App/.exists
"/usr/bin/perl" -MExtUtils::Command -e 'mkpath' -- blib/arch
chmod 755 blib/arch
touch blib/arch/.exists
"/usr/bin/perl" -MExtUtils::Command -e 'mkpath' -- 
blib/lib/auto/App/Licensecheck
chmod 755 blib/lib/auto/App/Licensecheck
touch blib/lib/auto/App/Licensecheck/.exists
"/usr/bin/perl" -MExtUtils::Command -e 'mkpath' -- 
blib/arch/auto/App/Licensecheck
chmod 755 blib/arch/auto/App/Licensecheck
touch blib/arch/auto/App/Licensecheck/.exists
"/usr/bin/perl" -MExtUtils::Command -e 'mkpath' -- blib/bin
chmod 755 blib/bin
touch blib/bin/.exists
"/usr/bin/perl" -MExtUtils::Command -e 'mkpath' -- blib/script
chmod 755 blib/script
touch blib/script/.exists
"/usr/bin/perl" -MExtUtils::Command -e 'mkpath' -- 

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

[Michael Crusoe]

On Sat, Sep 3, 2016 at 11:21 AM, Axel Beckert  wrote:

> Hi Antonio,
>
> Antonio Terceiro wrote:
> > On Tue, Aug 18, 2015 at 06:26:06PM +0200, Christian Hofstaedtler wrote:
> > - something else can replace ruby-ronn and we manage to make reverse
> >   (build) dependencies switch to it.
>
> Before starting to use ronn in an official release of
> unburden-home-dir, I tried different tools and was very unsatisfied:
>
> * go-md2man
> * pandoc
>
> There is also https://github.com/sunaku/md2man which is not yet
> packaged. Haven't tried that one yet since it requires a newer version
> of rubygems (2.5.2) than in Debian Unstable (2.5.1):
> https://github.com/sunaku/binman/issues/4



For the jaligner package we had a good experience with asciidoctor program

http://sources.debian.net/src/jaligner/1.0%2Bdfsg-4/debian/jaligner.adoc/
http://sources.debian.net/src/jaligner/1.0%2Bdfsg-4/debian/rules/#L16
http://sources.debian.net/src/jaligner/1.0%2Bdfsg-4/debian/control/#L12