Bug#885829: lios: Lios crashing on start

[mahashakti89]

Package: lios
Version: 2.6-1
Severity: grave
Justification: renders package unusable

Dear Maintainer,

Lios package is crashing on start, giving following error message :

lios
/usr/lib/python3/dist-packages/lios/ui/gtk/text_view.py:21: PyGIWarning: Gtk 
was imported without specifying a version first. Use gi.require_version('Gtk', 
'3.0') before import to ensure that the right version gets loaded.
  from gi.repository import Gtk
/usr/lib/python3/dist-packages/lios/ui/gtk/print_dialog.py:23: PyGIWarning: 
PangoCairo was imported without specifying a version first. Use 
gi.require_version('PangoCairo', '1.0') before import to ensure that the right 
version gets loaded.
  from gi.repository import PangoCairo
/usr/lib/python3/dist-packages/lios/cam.py:19: PyGIWarning: GstVideo was 
imported without specifying a version first. Use gi.require_version('GstVideo', 
'1.0') before import to ensure that the right version gets loaded.
  from gi.repository import GdkX11, GstVideo
/usr/lib/python3/dist-packages/lios/ui/gtk/terminal.py:21: PyGIWarning: Vte was 
imported without specifying a version first. Use gi.require_version('Vte', 
'2.91') before import to ensure that the right version gets loaded.
  from gi.repository import Gtk, GObject, Vte

(lios:21533): Gtk-WARNING **: Cannot connect attribute 'text' for cell renderer 
class 'lios+ui+gtk+tree_view+CellRendererToggle' since attribute does not exist
Traceback (most recent call last):
  File "/usr/lib/python3/dist-packages/lios/main.py", line 1297, in 
make_preferences_effective
self.dict = 
dictionary.Dict(dictionary.dictionary_language_dict[languages[self.preferences.language]])
IndexError: list index out of range

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File "/usr/bin/lios", line 8, in 
linux_intelligent_ocr_solution()
  File "/usr/lib/python3/dist-packages/lios/main.py", line 331, in __init__
self.make_preferences_effective()
  File "/usr/lib/python3/dist-packages/lios/main.py", line 1318, in 
make_preferences_effective
pacman -S aspell-fr""").format(languages[self.preferences.language]))
IndexError: list index out of range
zsh: exit 1 lios


 Regards




*** Reporter, please consider answering these questions, where appropriate ***

   * What led up to the situation?
   * What exactly did you do (or not do) that was effective (or
 ineffective)?
   * What was the outcome of this action?
   * What outcome did you expect instead?

*** End of the template - remove these template lines ***


-- System Information:
Debian Release: buster/sid
Architecture: amd64 (x86_64)
Foreign Architectures: i386

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

Versions of packages lios depends on:
ii  aspell-en2017.08.24-0-0.1
ii  espeak   1.48.04+dfsg-5+b1
ii  gir1.2-gst-plugins-base-1.0  1.12.4-1
ii  gir1.2-gtk-3.0   3.22.26-2
ii  gir1.2-vte-2.91  0.50.2-3
ii  imagemagick  8:6.9.7.4+dfsg-16
ii  imagemagick-6.q16 [imagemagick]  8:6.9.7.4+dfsg-16
ii  poppler-utils0.61.1-2
ii  python3  3.6.4-1
ii  python3-enchant  2.0.0-1
ii  python3-gi   3.26.1-2
ii  python3-sane 2.8.3-1+b1
ii  python3-speechd  0.8.8-1
ii  tesseract-ocr4.00~git2188-cdc35338-2

lios recommends no packages.

Versions of packages lios suggests:
ii  cuneiform  1.1.0+dfsg-6

-- no debconf information

Processed: Bug#878674: nodejs segfaults when building d3-* with webpack

[Debian Bug Tracking System]

Processing control commands:

> severity -1 grave
Bug #878674 [nodejs] nodejs segfaults when building d3-* with webpack
Severity set to 'grave' from 'important'

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

Bug#885826: linux-igd: /etc/init.d/linux-igd requires $network

[Nye Liu]

Package: linux-igd
Version: 1.0+cvs20070630-5
Severity: serious
Tags: patch
Justification: Policy 9.3.2

/etc/init.d/linux-igd requires $network or it will fail to start.

--- linux-igd.dist  2017-12-28 22:07:28.512055702 -0800
+++ linux-igd   2016-09-22 09:01:57.0 -0700
@@ -1,8 +1,8 @@
 #! /bin/sh
 ### BEGIN INIT INFO
 # Provides:  linux-igd
-# Required-Start:$remote_fs $syslog
-# Required-Stop: $remote_fs $syslog
+# Required-Start:$remote_fs $syslog $network
+# Required-Stop: $remote_fs $syslog $network
 # Default-Start: 2 3 4 5
 # Default-Stop:  0 1 6
 # Short-Description: UPnP Internet Gateway Device

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

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

Versions of packages linux-igd depends on:
ii  iptables  1.6.1-2+b1
ii  libc6 2.25-5
ii  libupnp6  1:1.6.24-4
ii  lsb-base  9.20170808

linux-igd recommends no packages.

linux-igd suggests no packages.

-- Configuration Files:
/etc/default/linux-igd changed [not included]
/etc/init.d/linux-igd changed [not included]

-- no debconf information

Bug#885825: miniupnpd: listen needs to be set to an interface, not an ip addres

[Nye Liu]

Package: miniupnpd
Version: 1.8.20140523-4.2
Severity: serious
Justification: Policy 9.3.2

In /etc/default/miniupnpd, i have:

MiniUPnPd_LISTENING_IP=192.168.19.1

But this results in:

Error: please specify LAN network interface by name instead of IPv4 address : 
192.168.19.1
can't parse "192.168.19.1" as a valid interface name

To make it work, I must put:
MiniUPnPd_LISTENING_IP=eth1

dpkg configure should state it wants an interface, not an ip address.

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

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

Versions of packages miniupnpd depends on:
ii  debconf [debconf-2.0]  1.5.65
ii  iproute2   4.14.1-1
ii  iptables   1.6.1-2+b1
ii  libc6  2.25-5
ii  libip4tc0  1.6.1-2+b1
ii  libip6tc0  1.6.1-2+b1
ii  libnfnetlink0  1.0.1-3+b1
ii  net-tools  1.60+git20161116.90da8a0-1
ii  uuid-runtime   2.30.2-0.1

miniupnpd recommends no packages.

miniupnpd suggests no packages.

-- debconf information:
* miniupnpd/listen: 192.168.19.1
* miniupnpd/ip6script: true
* miniupnpd/start_daemon: true
* miniupnpd/iface: eth0

Processed: notfound 885822 in 5.9-1

[Debian Bug Tracking System]

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

> # I forgot that in my previous mail
> notfound 885822 5.9-1
Bug #885822 {Done: Axel Beckert } [src:approx] approx: FTBFS 
with ocaml 4.05.0: Some fatal warnings were triggered
No longer marked as found in versions approx/5.9-1.
> thanks
Stopping processing here.

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

Processed: Re: Bug#869655: approx frequently FTBFS with test failures

[Debian Bug Tracking System]

Processing control commands:

> clone -1 -2
Bug #869655 [src:approx] approx frequently FTBFS with test failures
Bug 869655 cloned as bug 885822
> retitle -2 approx: FTBFS with ocaml 4.05.0: Some fatal warnings were triggered
Bug #885822 [src:approx] approx frequently FTBFS with test failures
Changed Bug title to 'approx: FTBFS with ocaml 4.05.0: Some fatal warnings were 
triggered' from 'approx frequently FTBFS with test failures'.
> found -2 5.8-1
Bug #885822 [src:approx] approx: FTBFS with ocaml 4.05.0: Some fatal warnings 
were triggered
Marked as found in versions approx/5.8-1.
> fixed -2 5.9-1
Bug #885822 [src:approx] approx: FTBFS with ocaml 4.05.0: Some fatal warnings 
were triggered
Marked as fixed in versions approx/5.9-1.
> close -2
Bug #885822 [src:approx] approx: FTBFS with ocaml 4.05.0: Some fatal warnings 
were triggered
Marked Bug as done

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

Bug#869655: approx frequently FTBFS with test failures

[Axel Beckert]

Control: clone -1 -2
Control: retitle -2 approx: FTBFS with ocaml 4.05.0: Some fatal warnings were 
triggered
Control: found -2 5.8-1
Control: fixed -2 5.9-1
Control: close -2

Hi Ole and Eric,

Ole Streicher wrote:
> @Adrian: Are you sure this is a regression introduced with 5.9-1?

I fear so:

~ → links2 -dump 
https://tests.reproducible-builds.org/debian/history/approx.html | fgrep FTBFS 
| fgrep -v 5.9-1
2016-10-26 5.5-2   unstable amd64FTBFS FTBFS4m 9s
profitbricks-build5-amd64  profitbricks-build1-amd64  amd64_4/54728  
2015-12-01 5.5-2   unstable armhfFTBFS FTBFS5m 55s  
   armhf_14/164   

So all approx FTBFS reported by the reproducible builds project were
from either 5.9-1 or 5.2-2 (more than a year ago) while 5.8-1 and
5.7-1 never FTBFS, at least not in testing.

There's a small chance that 5.8-1 would FTBFS with Ocaml from
Unstable. Since I couldn't reproduce the FTBFS with approx and ocaml
from unstable on amd64, I didn't try to build approx from testing with
ocaml from unstable on amd64.

But I was able to reproduce the FTBFS of approx 5.9-1 on unstable
armhf six times in a row (with several variants: with and w/o
eatmydata, with different nice and concurrency levels).

So I tried to build approx 5.8-1 with ocaml from unstable on armhf,
too. And it indeed FTBFS with ocaml from unstable. But not due to a
failing test suite but due to fatal compiler warnings:

ocamlfind ocamlc -c -warn-error A -package nethttpd -package pcre -o approx.cmo 
approx.ml
+ ocamlfind ocamlc -c -warn-error A -package nethttpd -package pcre -o 
approx.cmo approx.ml
File "approx.ml", line 283, characters 10-26:
Warning 3: deprecated: String.lowercase
Use String.lowercase_ascii instead.
File "approx.ml", line 1:
Error: Some fatal warnings were triggered (1 occurrences)
Command exited with code 2.
Makefile:15: recipe for target 'approx' failed
make[1]: *** [approx] Error 10

> 1. lower the severity to let it migrate, or

Sounds like the wrong option to me.

> 2. set the version-found to 5.8-1

Sounds wrong to me, too, given my findings.

> to enable autoremoval of the package
> in testing (and then let the transition go).

This nevertheless sounds like the correct approach.

So IMHO the clean solution is a separate bug report covering the FTBFS
of 5.8-1 with ocaml from unstable, which is fixed with 5.9-1. I've
tried to implement that with the control statements above by cloning
this bug report. Feel free to fix that if it doesn't result in the
expected outcome.

Regards, Axel
-- 
 ,''`.  |  Axel Beckert , https://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#885797: [Pkg-matrix-maintainers] Bug#885797: revolt: please build-depend on libglib2.0-dev-bin

[Hubert Chathi]

On Fri, 29 Dec 2017 23:50:08 +, Simon McVittie  said:

[...]

> This is easily fixed by changing the Build-Depends to pull in either
> libglib2.0-dev-bin, or libglib2.0-dev. I'll do a delayed NMU with the
> obvious change when I get a bug number; or if a maintainer would
> prefer to take care of this, a suitable patch is attached.

Hi Simon,

Thank you for the report and for the NMU.  I don't think we have any
uploads for Revolt planned in the near future, so we can just let the
NMU go through.

-- 
Hubert Chathi  -- https://www.uhoreg.ca/
Jabber: hub...@uhoreg.ca -- Matrix: @uhoreg:matrix.org
PGP/GnuPG key: 4096R/F24C F749 6C73 DDB8 DCB8  72DE B2DE 88D3 113A 1368

Bug#885821: cdrdao: Depends on gconf

[Jeremy Bicha]

Source: cdrdao
Version: 1:1.2.3-3
Severity: serious
User: pkg-gnome-maintain...@lists.alioth.debian.org
Usertags: oldlibs gconf
Tags: sid buster

Your package depends or build-depends on gconf, but gconf will be
removed from Debian soon.

gconf's last release was about 5 years ago. It has been replaced by
gsettings (provided in Debian by source glib2.0 )

References
--
https://developer.gnome.org/gio/stable/ch34.html
https://developer.gnome.org/gio/stable/GSettings.html

On behalf of the Debian GNOME team,
Jeremy Bicha

Bug#885818: alltray: Depends on gconf

[Jeremy Bicha]

Source: alltray
Version: 0.71b-1
Severity: serious
User: pkg-gnome-maintain...@lists.alioth.debian.org
Usertags: oldlibs gconf
Tags: sid buster

Your package depends or build-depends on gconf, but gconf will be
removed from Debian soon.

gconf's last release was about 5 years ago. It has been replaced by
gsettings (provided in Debian by source glib2.0 )

References
--
https://developer.gnome.org/gio/stable/ch34.html
https://developer.gnome.org/gio/stable/GSettings.html

On behalf of the Debian GNOME team,
Jeremy Bicha

Processed: notfound 639455 in kdevelop/4:5.2.1-1, severity of 639455 is normal

[Debian Bug Tracking System]

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

> notfound 639455 kdevelop/4:5.2.1-1
Bug #639455 [kdevelop] kdevelop hangs on background parsing
No longer marked as found in versions kdevelop/4:5.2.1-1.
> severity 639455 normal
Bug #639455 [kdevelop] kdevelop hangs on background parsing
Severity set to 'normal' from 'grave'
> thanks
Stopping processing here.

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

Processed: Re: maximus: Depends on libgnomeui

[Debian Bug Tracking System]

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

> reassign 885743 maximus 0.4.14-4
Bug #885743 [src:maximums] maximus: Depends on libgnomeui
Warning: Unknown package 'src:maximums'
Bug reassigned from package 'src:maximums' to 'maximus'.
No longer marked as found in versions maximums/0.4.14-4.
Ignoring request to alter fixed versions of bug #885743 to the same values 
previously set
Bug #885743 [maximus] maximus: Depends on libgnomeui
Marked as found in versions maximus/0.4.14-4.
>
End of message, stopping processing here.

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

Bug#885808: ario: Depends on libunique

[Jeremy Bicha]

Source: ario
Version: 1.5.1-1.3
Severity: serious
User: pkg-gnome-maintain...@lists.alioth.debian.org
Usertags: oldlibs libunique
Tags: sid buster

As announced [1], we do not intend to release Debian 10 "Buster" with
the old libgnome (and related) libraries. These libraries have been
deprecated and unmaintained for several years.

Your package depends and or build-depends on libunique.

Please port your package to GTK3 and related maintained libraries.
Otherwise, please consider requesting that your package be removed from
Debian to help us complete this goal.

[1] https://lists.debian.org/debian-devel/2017/10/msg00299.html

On behalf of the Debian GNOME team,
Jeremy Bicha

Bug#885807: alarm-clock-applet: Depends on libunique

[Jeremy Bicha]

Source: alarm-clock-applet
Version: 0.3.4-1
Severity: serious
User: pkg-gnome-maintain...@lists.alioth.debian.org
Usertags: oldlibs libunique
Tags: sid buster

As announced [1], we do not intend to release Debian 10 "Buster" with
the old libgnome (and related) libraries. These libraries have been
deprecated and unmaintained for several years.

Your package depends and or build-depends on libunique.

Please port your package to GTK3 and related maintained libraries.
Otherwise, please consider requesting that your package be removed from
Debian to help us complete this goal.

[1] https://lists.debian.org/debian-devel/2017/10/msg00299.html

On behalf of the Debian GNOME team,
Jeremy Bicha

Bug#885797: revolt: diff for NMU version 0.0+git20170627.3f5112b-2.1

[Simon McVittie]

Control: tags 885797 + pending

I've prepared an NMU for revolt (versioned as 0.0+git20170627.3f5112b-2.1)
and uploaded it to DELAYED/7. Please let me know if I should delay
it longer or cancel it.

Regards,
smcv
diffstat for revolt-0.0+git20170627.3f5112b revolt-0.0+git20170627.3f5112b

 changelog |9 +
 control   |2 +-
 2 files changed, 10 insertions(+), 1 deletion(-)

diff -Nru revolt-0.0+git20170627.3f5112b/debian/changelog revolt-0.0+git20170627.3f5112b/debian/changelog
--- revolt-0.0+git20170627.3f5112b/debian/changelog	2017-11-25 17:05:24.0 +
+++ revolt-0.0+git20170627.3f5112b/debian/changelog	2017-12-30 00:49:08.0 +
@@ -1,3 +1,12 @@
+revolt (0.0+git20170627.3f5112b-2.1) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * Build-depend on libglib2.0-dev-bin as well as libglib2.0-bin.
+glib-compile-resources moved from -bin to -dev-bin in version
+2.54.2-5 to fix #885019 (Closes: #885797)
+
+ -- Simon McVittie   Sat, 30 Dec 2017 00:49:08 +
+
 revolt (0.0+git20170627.3f5112b-2) unstable; urgency=medium
 
   * Depend on gir1.2-webkit2-4.0 instead of directly on libwebkit2gtk-4.0.
diff -Nru revolt-0.0+git20170627.3f5112b/debian/control revolt-0.0+git20170627.3f5112b/debian/control
--- revolt-0.0+git20170627.3f5112b/debian/control	2017-11-16 22:11:58.0 +
+++ revolt-0.0+git20170627.3f5112b/debian/control	2017-12-30 00:49:08.0 +
@@ -3,7 +3,7 @@
 Priority: optional
 Maintainer: Matrix Packaging Team 
 Uploaders: Hubert Chathi 
-Build-Depends: debhelper (>=9), libglib2.0-bin, python3:any | python3-all:any | python3-dev:any | python3-all-dev:any, python3-gi
+Build-Depends: debhelper (>=9), libglib2.0-bin, libglib2.0-dev-bin, python3:any | python3-all:any | python3-dev:any | python3-all-dev:any, python3-gi
 Standards-Version: 3.9.8
 Homepage: https://github.com/aperezdc/revolt
 Vcs-Git: git://anonscm.debian.org/collab-maint/revolt.git

Processed: revolt: diff for NMU version 0.0+git20170627.3f5112b-2.1

[Debian Bug Tracking System]

Processing control commands:

> tags 885797 + pending
Bug #885797 [revolt] revolt: please build-depend on libglib2.0-dev-bin
Added tag(s) pending.

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

Bug#885803: libgnomecanvasmm2.6: Don't release with Buster

[Jeremy Bicha]

Source: libgnomecanvasmm2.6
Version: 2.26.0-2
Severity: serious
User: pkg-gnome-maintain...@lists.alioth.debian.org
Usertags: oldlibs libgnomecanvas
Tags: sid buster

As announced [1], we do not intend to release Debian 10 "Buster" with
the old libgnome (and related) libraries. These libraries have been
deprecated and unmaintained for several years.

Please port your package to GTK3 and related maintained libraries.

We should be able to remove libgnomecanvasmm2.6 from Debian Testing
soon.

[1] https://lists.debian.org/debian-devel/2017/10/msg00299.html

On behalf of the Debian GNOME team,
Jeremy Bicha

Bug#885797: revolt: please build-depend on libglib2.0-dev-bin

[Simon McVittie]

Package: revolt
Version: 0.0+git20170627.3f5112b-2
Severity: serious
Tags: patch
Justification: fails to build from source (but built successfully in the past)

In bug #885019, the GNOME maintainers were asked to move the
glib-compile-resources tool to a more appropriate package to fix
cross-compiling. glib-compile-resources is a development tool and is not
needed by typical non-developer users, so moving it to libglib2.0-dev-bin
seemed most appropriate.

For the majority of packages that use glib-compile-resources, this had no
practical effect, because libglib2.0-dev depends on both. However,
revolt is unusual in that it uses glib-compile-resources without
depending on libglib2.0-dev (because it isn't native code). Depending
on libglib2.0-bin was previously enough to get glib-compile-resources,
but now isn't enough, making revolt FTBFS.

This is easily fixed by changing the Build-Depends to pull in either
libglib2.0-dev-bin, or libglib2.0-dev. I'll do a delayed NMU with the
obvious change when I get a bug number; or if a maintainer would prefer
to take care of this, a suitable patch is attached.

Thanks,
smcv
>From 3e10087807b360cc3d6d2ae208f92c3b9f28e9e6 Mon Sep 17 00:00:00 2001
From: Simon McVittie 
Date: Fri, 29 Dec 2017 23:32:27 +
Subject: [PATCH] Build-depend on libglib2.0-dev-bin as well as libglib2.0-bin

glib-compile-resources moved from -bin to -dev-bin in version
2.54.2-5 to fix #885019 (Closes: #nn)
---
 debian/changelog | 9 +
 debian/control   | 2 +-
 2 files changed, 10 insertions(+), 1 deletion(-)

diff --git a/debian/changelog b/debian/changelog
index c277bb9..5673bc0 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,3 +1,12 @@
+revolt (0.0+git20170627.3f5112b-2.1) UNRELEASED; urgency=medium
+
+  * Non-maintainer upload.
+  * Build-depend on libglib2.0-dev-bin as well as libglib2.0-bin.
+glib-compile-resources moved from -bin to -dev-bin in version
+2.54.2-5 to fix #885019 (Closes: #nn)
+
+ -- Simon McVittie   Fri, 29 Dec 2017 23:30:30 +
+
 revolt (0.0+git20170627.3f5112b-2) unstable; urgency=medium
 
   * Depend on gir1.2-webkit2-4.0 instead of directly on libwebkit2gtk-4.0.
diff --git a/debian/control b/debian/control
index 9834670..8c5b0c8 100644
--- a/debian/control
+++ b/debian/control
@@ -3,7 +3,7 @@ Section: net
 Priority: optional
 Maintainer: Matrix Packaging Team 
 Uploaders: Hubert Chathi 
-Build-Depends: debhelper (>=9), libglib2.0-bin, python3:any | python3-all:any | python3-dev:any | python3-all-dev:any, python3-gi
+Build-Depends: debhelper (>=9), libglib2.0-bin, libglib2.0-dev-bin, python3:any | python3-all:any | python3-dev:any | python3-all-dev:any, python3-gi
 Standards-Version: 3.9.8
 Homepage: https://github.com/aperezdc/revolt
 Vcs-Git: git://anonscm.debian.org/collab-maint/revolt.git
-- 
2.15.1

Bug#884407: marked as done (wslay FTBFS with nettle-dev 3.4-1)

[Debian Bug Tracking System]

Your message dated Fri, 29 Dec 2017 23:38:41 +
with message-id 
and subject line Bug#884407: fixed in wslay 1.0.1~39-g6abacc1-2
has caused the Debian Bug report #884407,
regarding wslay FTBFS with nettle-dev 3.4-1
to be marked as done.

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

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


-- 
884407: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=884407
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: wslay
Version: 1.0.1~39-g6abacc1-1
Severity: serious

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

...
/build/1st/wslay-1.0.1~39-g6abacc1/examples/echoserv.cc: In function 
'std::__cxx11::string base64(const string&)':
/build/1st/wslay-1.0.1~39-g6abacc1/examples/echoserv.cc:126:83: error: invalid 
conversion from 'uint8_t* {aka unsigned char*}' to 'char*' [-fpermissive]
   base64_encode_raw(dst, src.size(), reinterpret_cast(src.c_str()));

   ^
In file included from 
/build/1st/wslay-1.0.1~39-g6abacc1/examples/echoserv.cc:52:0:
/usr/include/nettle/base64.h:117:1: note:   initializing argument 1 of 'void 
nettle_base64_encode_raw(char*, size_t, const uint8_t*)'
 base64_encode_raw(char *dst, size_t length, const uint8_t *src);
 ^
/build/1st/wslay-1.0.1~39-g6abacc1/examples/testclient.cc: In function 
'std::__cxx11::string base64(const string&)':
/build/1st/wslay-1.0.1~39-g6abacc1/examples/testclient.cc:118:66: error: 
invalid conversion from 'uint8_t* {aka unsigned char*}' to 'char*' 
[-fpermissive]
 reinterpret_cast(src.c_str()));
  ^
In file included from 
/build/1st/wslay-1.0.1~39-g6abacc1/examples/testclient.cc:51:0:
/usr/include/nettle/base64.h:117:1: note:   initializing argument 1 of 'void 
nettle_base64_encode_raw(char*, size_t, const uint8_t*)'
 base64_encode_raw(char *dst, size_t length, const uint8_t *src);
 ^
examples/CMakeFiles/echoserv.dir/build.make:65: recipe for target 
'examples/CMakeFiles/echoserv.dir/echoserv.cc.o' failed
make[4]: *** [examples/CMakeFiles/echoserv.dir/echoserv.cc.o] Error 1
--- End Message ---
--- Begin Message ---
Source: wslay
Source-Version: 1.0.1~39-g6abacc1-2

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

Debian distribution maintenance software
pp.
Anton Gladky  (supplier of updated wslay package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Fri, 29 Dec 2017 23:42:08 +0100
Source: wslay
Binary: libwslay-dev libwslay1 libwslay-doc
Architecture: source
Version: 1.0.1~39-g6abacc1-2
Distribution: unstable
Urgency: medium
Maintainer: Anton Gladky 
Changed-By: Anton Gladky 
Description:
 libwslay-dev - WebSocket library written in C. Development files
 libwslay-doc - WebSocket library written in C. Documentation
 libwslay1  - WebSocket library written in C. Shared library
Closes: 884407
Changes:
 wslay (1.0.1~39-g6abacc1-2) unstable; urgency=medium
 .
   * [3f39533] Remove science team as a maintainer.
   * [53a3412] Update comments in tests.
   * [7be02dd] Fix FTBFS due to API update in nettle. (Closes: #884407)
   * [b9261e0] Remove testsuite-field in d/control
   * [135f6cb] Remove prioroty extra from d/control
   * [b5974ea] Set Standards-Version: 4.1.3
   * [b839664] Update VCS-fields
Checksums-Sha1:
 419aacd2fdf84d6080c181f1dbbedb700ca62970 2131 wslay_1.0.1~39-g6abacc1-2.dsc
 eca820ef50c7d71ce64fba30935502aabafb971d 4464 
wslay_1.0.1~39-g6abacc1-2.debian.tar.xz
 f983fcc72c9c05494015d9830a04aae03fd19ef3 8333 
wslay_1.0.1~39-g6abacc1-2_source.buildinfo
Checksums-Sha256:
 e2c5946615994398c73a6a24362db15036180370f01b0b5334c8c678531a948a 2131 
wslay_1.0.1~39-g6abacc1-2.dsc
 23f6d255a955ee922b4fdff89b890895c1632bd0d0e939c645ec8437e6a2da1e 4464 
wslay_1.0.1~39-g6abacc1-2.debian.tar.xz
 db2ee3f2d2477e856536d22caab394ab742b02b3da92a7c99733b20014acb5f1 8333 
wslay_1.0.1~39-g6abacc1-2_source.buildinfo
Files:
 

Bug#880904: marked as done (node-cliui FTBFS: test failure)

[Debian Bug Tracking System]

Your message dated Fri, 29 Dec 2017 23:38:09 +
with message-id 
and subject line Bug#880904: fixed in node-cliui 4.0.0-1
has caused the Debian Bug report #880904,
regarding node-cliui FTBFS: test failure
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.)


-- 
880904: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=880904
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: node-cliui
Version: 3.2.0-2
Severity: serious
Tags: buster sid

Some recent change in unstable makes node-cliui FTBFS:

https://tests.reproducible-builds.org/debian/history/node-cliui.html
https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/node-cliui.html

...
   debian/rules override_dh_auto_test
make[1]: Entering directory '/build/1st/node-cliui-3.2.0'
mocha

  
․․․․․․․․․․․․․․․․․․․․․․․․

  23 passing (97ms)
  1 failing

  1) cliui layoutDSL ignores ansi escape codes when measuring padding:

  AssertionError: expected [ Array(5) ] to deeply equal [ Array(5) 
]
  + expected - actual

 "  |",
 "  __|   __|  |   |   _ \\",
 "  || |   |   __/",
 " \\__| _|\\__,_| \\___|",
  -  ""
  +  " "
   ]
  
  at Context. (/build/1st/node-cliui-3.2.0/test/cliui.js:443:17)
  at callFn (/usr/lib/nodejs/mocha/lib/runnable.js:223:21)
  at Test.Runnable.run (/usr/lib/nodejs/mocha/lib/runnable.js:216:7)
  at Runner.runTest (/usr/lib/nodejs/mocha/lib/runner.js:373:10)
  at /usr/lib/nodejs/mocha/lib/runner.js:451:12
  at next (/usr/lib/nodejs/mocha/lib/runner.js:298:14)
  at /usr/lib/nodejs/mocha/lib/runner.js:308:7
  at next (/usr/lib/nodejs/mocha/lib/runner.js:246:23)
  at Immediate. (/usr/lib/nodejs/mocha/lib/runner.js:275:5)
  at runCallback (timers.js:672:20)
  at tryOnImmediate (timers.js:645:5)
  at processImmediate [as _immediateCallback] (timers.js:617:5)



debian/rules:13: recipe for target 'override_dh_auto_test' failed
make[1]: *** [override_dh_auto_test] Error 1
--- End Message ---
--- Begin Message ---
Source: node-cliui
Source-Version: 4.0.0-1

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

Debian distribution maintenance software
pp.
Jérémy Lal  (supplier of updated node-cliui package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Fri, 29 Dec 2017 23:04:27 +0100
Source: node-cliui
Binary: node-cliui
Architecture: source
Version: 4.0.0-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Javascript Maintainers 

Changed-By: Jérémy Lal 
Description:
 node-cliui - easily create complex multi-column CLIs
Closes: 880904
Changes:
 node-cliui (4.0.0-1) unstable; urgency=medium
 .
   * New upstream version 4.0.0
   * Patch to adapt one test to actual (discutable) situation with
 wrap-ansi and ansi-strip not dealing with spaces the same way
 they used to. Upstream might fix this eventually.
 Closes: #880904.
Checksums-Sha1:
 8c063d684e1948425f6091516757f9314f7f648c 2090 node-cliui_4.0.0-1.dsc
 eed5e2d9cef20f4a175ca139e0696002cff73e77 25491 node-cliui_4.0.0.orig.tar.gz
 609ee8fa1b87efe8a9f7257aabed982fdc20ad76 3364 node-cliui_4.0.0-1.debian.tar.xz
 15e589c1ebf0b8d975abe2409cc53558fd95756d 8928 
node-cliui_4.0.0-1_source.buildinfo
Checksums-Sha256:
 2b1e7d18c3456b29011bcd82da43287a74e9a42e3d113fb1b483b55d67c9f306 2090 
node-cliui_4.0.0-1.dsc
 c27e2acbc65ce4778cf1c69a75088458bd82b0452938aea398ba97f46873437f 25491 
node-cliui_4.0.0.orig.tar.gz
 d69e1bba7fa7cb678ba9ed87c9b66d984b09a1a64084b54c41f25ad04d6520ac 3364 
node-cliui_4.0.0-1.debian.tar.xz
 

Bug#877538: marked as done (node-concat-with-sourcemaps FTBFS and Debci failure with node-source-map >= 0.6.0)

[Debian Bug Tracking System]

Your message dated Fri, 29 Dec 2017 23:38:21 +
with message-id 
and subject line Bug#877538: fixed in node-concat-with-sourcemaps 1.0.4-2
has caused the Debian Bug report #877538,
regarding node-concat-with-sourcemaps FTBFS and Debci failure with 
node-source-map >= 0.6.0
to be marked as done.

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

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


-- 
877538: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=877538
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: node-concat-with-sourcemaps
Version: 1.0.4-1
Severity: serious

https://ci.debian.net/packages/n/node-concat-with-sourcemaps/unstable/amd64/
https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/node-concat-with-sourcemaps.html

...
# should ignore invalid mappings
/usr/lib/nodejs/source-map/lib/source-map-generator.js:276
throw new Error(
^

Error: original.line and original.column are not numbers -- you probably meant 
to omit the original mapping entirely and only map the generated position. If 
so, pass null for the original mapping instead of an object with empty or null 
values.
at SourceMapGenerator_validateMapping [as _validateMapping] 
(/usr/lib/nodejs/source-map/lib/source-map-generator.js:276:15)
at SourceMapGenerator_addMapping [as addMapping] 
(/usr/lib/nodejs/source-map/lib/source-map-generator.js:110:12)
at /build/1st/node-concat-with-sourcemaps-1.0.4/index.js:60:28
at Array.forEach (native)
at SourceMapConsumer_eachMapping [as eachMapping] 
(/usr/lib/nodejs/source-map/lib/source-map-consumer.js:157:14)
at Concat.add (/build/1st/node-concat-with-sourcemaps-1.0.4/index.js:58:18)
at /build/1st/node-concat-with-sourcemaps-1.0.4/test/index.js:11:14
at Array.forEach (native)
at Test. 
(/build/1st/node-concat-with-sourcemaps-1.0.4/test/index.js:10:19)
at Test.bound [as _cb] (/usr/lib/nodejs/tape/lib/test.js:77:32)
debian/rules:13: recipe for target 'override_dh_auto_test' failed
make[1]: *** [override_dh_auto_test] Error 1
--- End Message ---
--- Begin Message ---
Source: node-concat-with-sourcemaps
Source-Version: 1.0.4-2

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

Debian distribution maintenance software
pp.
Jérémy Lal  (supplier of updated node-concat-with-sourcemaps 
package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Fri, 29 Dec 2017 23:40:01 +0100
Source: node-concat-with-sourcemaps
Binary: node-concat-with-sourcemaps
Architecture: source
Version: 1.0.4-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Javascript Maintainers 

Changed-By: Jérémy Lal 
Description:
 node-concat-with-sourcemaps - concatenate files and generate source maps
Closes: 877538
Changes:
 node-concat-with-sourcemaps (1.0.4-2) unstable; urgency=medium
 .
   * Team upload
   * Patch for source-map 0.6 compat (Closes: #877538)
   * Update node-source-map dependency >= 0.6.1
   * Section: javascript
   * Standards-Version: 4.1.2
Checksums-Sha1:
 55314c726311cb20768145aac0866de96528d15b 2300 
node-concat-with-sourcemaps_1.0.4-2.dsc
 b8cf381b930f538894752b6d2a812d01249a4fb1 2504 
node-concat-with-sourcemaps_1.0.4-2.debian.tar.xz
 2a1743e4c497e0c844274ad79e61faca10c37b58 6790 
node-concat-with-sourcemaps_1.0.4-2_source.buildinfo
Checksums-Sha256:
 f720c73f6ebd18c20b46218026036038f348b24eea685345ed87f26090c60fe8 2300 
node-concat-with-sourcemaps_1.0.4-2.dsc
 c47843e5af43814db0332bf4d616b1a620cfc303cc2dca038299f90224425781 2504 
node-concat-with-sourcemaps_1.0.4-2.debian.tar.xz
 ec93d90774fb5f618e76661f5911e48ee016e930eb0608f05b5c99cc6ddba11c 6790 
node-concat-with-sourcemaps_1.0.4-2_source.buildinfo
Files:
 93d5508d4d2dcddee4eb2ec1f0652a77 2300 javascript optional 
node-concat-with-sourcemaps_1.0.4-2.dsc
 c103e54db1bcbdbc08148300fb8fd735 2504 javascript optional 
node-concat-with-sourcemaps_1.0.4-2.debian.tar.xz
 ba36c4e429aea74241742602f6f21e4e 6790 javascript optional 

Processed: tldr-py,tldr: File collision when installing together: /usr/bin/tldr (and maybe further files)

[Debian Bug Tracking System]

Processing control commands:

> found -1 tldr-py/0.7.0-1
Bug #885793 [tldr-py,tldr] tldr-py,tldr: File collision when installing 
together: /usr/bin/tldr (and maybe further files)
Marked as found in versions tldr-py/0.7.0-1.
> found -1 haskell-tldr/0.2.3-1
Bug #885793 [tldr-py,tldr] tldr-py,tldr: File collision when installing 
together: /usr/bin/tldr (and maybe further files)
Marked as found in versions haskell-tldr/0.2.3-1.

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

Bug#885793: tldr-py,tldr: File collision when installing together: /usr/bin/tldr (and maybe further files)

[Axel Beckert]

Package: tldr-py,tldr
Severity: serious
Control: found -1 tldr-py/0.7.0-1
Control: found -1 haskell-tldr/0.2.3-1

Hi,

installing tldr when tldr-py is already installed fails as follows since
both packages ship /usr/bin/tldr (and maybe further files like e.g. man
pages. etc.):

Preparing to unpack .../tldr_0.2.3-1_amd64.deb ...
Unpacking tldr (0.2.3-1) ...
dpkg: error processing archive /var/cache/apt/archives/tldr_0.2.3-1_amd64.deb 
(--unpack):
 trying to overwrite '/usr/bin/tldr', which is also in package tldr-py 0.7.0-1
dpkg-deb: error: paste subprocess was killed by signal (Broken pipe)
Errors were encountered while processing:
 /var/cache/apt/archives/tldr_0.2.3-1_amd64.deb

Please either conflict with each other or both start using
update-alternatives (if suitable wrt. commandline options, etc.) to
choose between the different implementations.

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

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

Processed: tagging 884200

[Debian Bug Tracking System]

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

> tags 884200 + fixed-upstream pending
Bug #884200 [src:libsynthesis] libsynthesis FTBFS with libical3
Added tag(s) fixed-upstream and pending.
> thanks
Stopping processing here.

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

Processed: Re: Bug#885785: automatically created packages (-dbgsym) should not be rejected by lintian

[Debian Bug Tracking System]

Processing control commands:

> tags -1 moreinfo
Bug #885785 [debhelper,lintian] automatically created packages (-dbgsym) should 
not be rejected by lintian
Added tag(s) moreinfo.

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

Bug#885785: automatically created packages (-dbgsym) should not be rejected by lintian

[Niels Thykier]

Control: tags -1 moreinfo

Matthias Klose:
> Package: debhelper,lintian
> Severity: serious
> Tags: sid buster
> 
> The last gcc-8 upload was automatically rejected with
> 
> E: libgomp-plugin-nvptx1-dbgsym: usr-share-doc-symlink-to-foreign-package
> libgomp-plugin-nvptx1
> E: gcc-8-offload-nvptx-dbgsym: usr-share-doc-symlink-to-foreign-package
> gcc-8-offload-nvptx
> 
> These are automatically generated packages by dehelper. I don't think that 
> there
> should be automatic rejections for automatically generated packages at all.
> 

That lintian warning suggests that libgomp-plugin-nvptx1 +
gcc-8-offload-nvptx are not listed in the debian/control file of the
source package you uploaded.  If that is the case, dak will/should
reject the package anyway in a later control check as the upload then
includes binaries not related to the source package.

I am aware that the d/control of gcc-8 in subversion does list these,
but please confirm that the control file of the uploaded package lists
these two packages.

Thanks,
~Niels

Bug#885785: automatically created packages (-dbgsym) should not be rejected by lintian

[Matthias Klose]

Package: debhelper,lintian
Severity: serious
Tags: sid buster

The last gcc-8 upload was automatically rejected with

E: libgomp-plugin-nvptx1-dbgsym: usr-share-doc-symlink-to-foreign-package
libgomp-plugin-nvptx1
E: gcc-8-offload-nvptx-dbgsym: usr-share-doc-symlink-to-foreign-package
gcc-8-offload-nvptx

These are automatically generated packages by dehelper. I don't think that there
should be automatic rejections for automatically generated packages at all.

Bug#885777: xournal: Depends on libgnomecanvas

[Jeremy Bicha]

Source: xournal
Version: 1:0.4.8-1
Severity: serious
User: pkg-gnome-maintain...@lists.alioth.debian.org
Usertags: oldlibs libgnomecanvas
Tags: sid buster

As announced [1], we do not intend to release Debian 10 "Buster" with
the old libgnome (and related) libraries. These libraries have been
deprecated and unmaintained for several years.

Your package depends and or build-depends on libgnomecanvas.

Please port your package to GTK3 and related maintained libraries.
Otherwise, please consider requesting that your package be removed from
Debian to help us complete this goal.

[1] https://lists.debian.org/debian-devel/2017/10/msg00299.html

On behalf of the Debian GNOME team,
Jeremy Bicha

Processed: kdevelop hangs on background parsing

[Debian Bug Tracking System]

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

> package kdevelop
Limiting to bugs with field 'package' containing at least one of 'kdevelop'
Limit currently set to 'package':'kdevelop'

> found 639455 4:5.2.1-1
Bug #639455 [kdevelop] kdevelop hangs on background parsing
Marked as found in versions kdevelop/4:5.2.1-1.
> notfound 639455 4:5.1.2-1
Bug #639455 [kdevelop] kdevelop hangs on background parsing
Ignoring request to alter found versions of bug #639455 to the same values 
previously set
> severity 639455 grave
Bug #639455 [kdevelop] kdevelop hangs on background parsing
Severity set to 'grave' from 'normal'
> --
Stopping processing here.

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

Bug#885763: invada-studio-plugins-lv2: Depends on libgnome

[Jaromír Mikeš]

2017-12-29 19:27 GMT+01:00 Jeremy Bicha :

> Source: invada-studio-plugins-lv2
> Version: 1.2.0+repack0-7
> Severity: serious
> User: pkg-gnome-maintain...@lists.alioth.debian.org
> Usertags: oldlibs libgnome
> Tags: sid buster
>
> As announced [1], we do not intend to release Debian 10 "Buster" with
> the old libgnome (and related) libraries. These libraries have been
> deprecated and unmaintained for several years.
>
> Your package depends and or build-depends on libgnome.
>
> Please port your package to GTK3 and related maintained libraries.
> Otherwise, please consider requesting that your package be removed from
> Debian to help us complete this goal.
>
> [1] https://lists.debian.org/debian-devel/2017/10/msg00299.html


​Hi Fraser,

as you see there is ongoing process of removing of old libs in debian.
​invada-studio-plugins-lv2 package depends on one of them unfortunately.
Please let me know if you plan to move invada-studio-plugins-lv2 to GTK3
otherwise this package will be removed with next debian release.

best regards

mira

Bug#885769: libbonoboui: Don't release with Buster

[Jeremy Bicha]

Source: libbonoboui
Version: 2.24.5-4
Severity: serious
User: pkg-gnome-maintain...@lists.alioth.debian.org
Usertags: oldlibs libbonobo
Tags: sid buster

As announced [1], we do not intend to release Debian 10 "Buster" with
the old libgnome (and related) libraries. These libraries have been
deprecated and unmaintained for several years.

Please port your package to GTK3 and related maintained libraries. 

[1] https://lists.debian.org/debian-devel/2017/10/msg00299.html

On behalf of the Debian GNOME team,
Jeremy Bicha

Bug#885770: libbonobo: Don't release with Buster

[Jeremy Bicha]

Source: libbonobo
Version: 2.32.1-3
Severity: serious
User: pkg-gnome-maintain...@lists.alioth.debian.org
Usertags: oldlibs libbonobo
Tags: sid buster

As announced [1], we do not intend to release Debian 10 "Buster" with
the old libgnome (and related) libraries. These libraries have been
deprecated and unmaintained for several years.

Please port your package to GTK3 and related maintained libraries. 

[1] https://lists.debian.org/debian-devel/2017/10/msg00299.html

On behalf of the Debian GNOME team,
Jeremy Bicha

Bug#885771: selinux-policy-dev package post-installation script subprocess returned error exit status 1

[Evgeni Golov]

Package: selinux-policy-dev
Version: 2:2.20171228-1
Severity: serious

Ohai,

upgrade to latest s-p-dev fails:
Setting up selinux-policy-dev (2:2.20171228-1) ...
Running sepolgen-ifgen...dpkg: error processing package selinux-policy-dev 
(--configure):
 installed selinux-policy-dev package post-installation script subprocess 
returned error exit status 1
Errors were encountered while processing:
 selinux-policy-dev

Looking closer, it seems polgen-ifgen fails:
% sudo sepolgen-ifgen
/usr/share/selinux/devel/include/support/obj_perm_sets.spt: Syntax error on 
line 157 ` [type=TICK]
error parsing headers
error parsing file /usr/share/selinux/devel/include/support/obj_perm_sets.spt: 
could not parse text: 
"/usr/share/selinux/devel/include/support/obj_perm_sets.spt: Syntax error on 
line 157 ` [type=TICK]"

Regards
Evgeni

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

Kernel: Linux 4.14.0-2-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: SELinux: enabled - Mode: Permissive - Policy name: default

Versions of packages selinux-policy-dev depends on:
ii  checkpolicy   2.7-1
ii  gawk  1:4.1.4+dfsg-1
ii  m41.4.18-1
ii  make  4.1-9.1
ii  policycoreutils   2.7-1
ii  policycoreutils-dev   2.7-2
ii  policycoreutils-python-utils  2.7-2
ii  python2.7.14-4
ii  selinux-utils 2.7-2

Versions of packages selinux-policy-dev recommends:
ii  setools  4.1.1-3

selinux-policy-dev suggests no packages.

-- no debconf information

Bug#885768: libgnome: Don't release with Buster

[Jeremy Bicha]

Source: libgnome
Version: 2.32.1-6
Severity: serious
User: pkg-gnome-maintain...@lists.alioth.debian.org
Usertags: oldlibs libgnome
Tags: sid buster

As announced [1], we do not intend to release Debian 10 "Buster" with
the old libgnome (and related) libraries. These libraries have been
deprecated and unmaintained for several years.

Please port your package to GTK3 and related maintained libraries. 

Here's a tracker:
https://bugs.debian.org/cgi-bin/pkgreport.cgi?users=pkg-gnome-maintaine
r...@lists.alioth.debian.org;tag=libgnome

It's incomplete because often I didn't file a bug if there was already
another Important/Serious bug for deprecated GNOME libraries (like
gnome-vfs and especially libgnomeui)


[1] https://lists.debian.org/debian-devel/2017/10/msg00299.html

On behalf of the Debian GNOME team,
Jeremy Bicha

Bug#885767: libgnomeui: Do not release with Buster

[Jeremy Bicha]

Source: libgnomeui
Version: 2.24.5-3.2
Severity: serious
User: pkg-gnome-maintain...@lists.alioth.debian.org
Usertags: oldlibs libgnomeui
Tags: sid buster

As announced [1], we do not intend to release Debian 10 "Buster" with
the old libgnome (and related) libraries. These libraries have been
deprecated and unmaintained for several years.

Please port your package to GTK3 and related maintained libraries. 

Here's a tracker:
https://bugs.debian.org/cgi-bin/pkgreport.cgi?users=pkg-gnome-maintaine
r...@lists.alioth.debian.org;tag=libgnomeui

It's incomplete because often I didn't file a bug if there was already
another Important/Serious bug for deprecated GNOME libraries (like
gnome-vfs)


[1] https://lists.debian.org/debian-devel/2017/10/msg00299.html

On behalf of the Debian GNOME team,
Jeremy Bicha

Processed: Re: Bug#884345: asterisk: CVE-2017-17664: Remote Crash Vulnerability in RTCP Stack

[Debian Bug Tracking System]

Processing control commands:

> fixed -1 1:13.18.5~dfsg-1
Bug #884345 [src:asterisk] asterisk: CVE-2017-17664: Remote Crash Vulnerability 
in RTCP Stack
Marked as fixed in versions asterisk/1:13.18.5~dfsg-1.

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

Bug#884345: asterisk: CVE-2017-17664: Remote Crash Vulnerability in RTCP Stack

[Bernhard Schmidt]

Control: fixed -1 1:13.18.5~dfsg-1

This was fixed in sid with the latest upload, but not properly closed in
the changelog.

asterisk (1:13.18.5~dfsg-1) unstable; urgency=medium

  * New upstream release:
- CVE-2017-17850 / AST-2017-014 (closes: #885072)
- AST-2017-012: Remote Crash Vulnerability in RTCP Stack
  * Re-add support for snmp (Closes #851738)
  * Don't load dundi, mgcp, skinny and unistim by default
  * Avoid parallel build in 'make install'
  * tests: realpath is now in coreutils
  * asttestmods: enable res_pjsip_pubsub tests
  * asttestmods: run asterisk as user asterisk
  * asttestmods: disable module test_cel for now

 -- Tzafrir Cohen   Thu, 28 Dec 2017 00:20:16 +0200

Bernhard

Processed: Raise severity for libgnome related bugs

[Debian Bug Tracking System]

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

> severity 868399 serious
Bug #868399 [src:notebook] notebook: Please drop the (build-)dependency against 
gnome-vfs
Severity set to 'serious' from 'important'
> severity 868390 serious
Bug #868390 [src:cbrpager] cbrpager: Please drop the (build-)dependency against 
gnome-vfs
Severity set to 'serious' from 'important'
>
End of message, stopping processing here.

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

Bug#885763: invada-studio-plugins-lv2: Depends on libgnome

[Jeremy Bicha]

Source: invada-studio-plugins-lv2
Version: 1.2.0+repack0-7
Severity: serious
User: pkg-gnome-maintain...@lists.alioth.debian.org
Usertags: oldlibs libgnome
Tags: sid buster

As announced [1], we do not intend to release Debian 10 "Buster" with
the old libgnome (and related) libraries. These libraries have been
deprecated and unmaintained for several years.

Your package depends and or build-depends on libgnome.

Please port your package to GTK3 and related maintained libraries.
Otherwise, please consider requesting that your package be removed from
Debian to help us complete this goal.

[1] https://lists.debian.org/debian-devel/2017/10/msg00299.html

On behalf of the Debian GNOME team,
Jeremy Bicha

Bug#885761: langdrill: Drop Build-Depends on libgnomeui-dev

[Jeremy Bicha]

Source: langdrill
Version: 0.3-7
Severity: serious
User: pkg-gnome-maintain...@lists.alioth.debian.org
Usertags: oldlibs libgnomeui
Tags: sid buster patch

As announced [1], we do not intend to release Debian 10 "Buster" with
the old libgnome (and related) libraries. These libraries have been
deprecated and unmaintained for several years.

Your package appears to have an unnecessary Build-Depends on
libgnomeui-dev. Please drop it to help us complete this goal. (No patch
attached, but this should be a trivial fix.)

[1] https://lists.debian.org/debian-devel/2017/10/msg00299.html

On behalf of the Debian GNOME team,
Jeremy Bicha

Bug#885760: vdk2: Drop Build-Depends on libgnomeui-dev

[Jeremy Bicha]

Source: vdk2
Version: 2.4.0-5.4
Severity: serious
User: pkg-gnome-maintain...@lists.alioth.debian.org
Usertags: oldlibs libgnomeui
Tags: sid buster patch

As announced [1], we do not intend to release Debian 10 "Buster" with
the old libgnome (and related) libraries. These libraries have been
deprecated and unmaintained for several years.

Your package appears to have an unnecessary Build-Depends on
libgnomeui-dev. Please remove that to help us complete this goal. (No
patch attached because this should be a trivial fix.)

[1] https://lists.debian.org/debian-devel/2017/10/msg00299.html

On behalf of the Debian GNOME team,
Jeremy Bicha

Bug#885758: mp3splt: Don't Build-Depend on libgnomeui-dev

[Jeremy Bicha]

Source: mp3splt
Version: 2.6.2+20170630-2
Severity: serious
User: pkg-gnome-maintain...@lists.alioth.debian.org
Usertags: oldlibs libgnomeui
Tags: sid buster patch

As announced [1], we do not intend to release Debian 10 "Buster" with
the old libgnome (and related) libraries. These libraries have been
deprecated and unmaintained for several years.

Your package build-depends on libgnomeui-dev but this doesn't look
needed any more.

[1] https://lists.debian.org/debian-devel/2017/10/msg00299.html

On behalf of the Debian GNOME team,
Jeremy Bicha

Bug#885754: network-manager-strongswan: Fails to build from source, deprecated errors

[Jeremy Bicha]

Source: network-manager-strongswan
Version: 1.4.2-1
Severity: serious
Tags: sid buster

network-manager-strongswan fails to build from source.

Build log excerpt
===
/usr/include/libnm/nm-utils.h:249:1: error: ‘NMTCTfilter’ is
deprecated: Not available before 1.10.2 [-Werror=deprecated-
declarations]
 char *nm_utils_tc_tfilter_to_str   (NMTCTfilter *tfilter,
GError **error);
 ^~~~
In file included from /usr/include/libnm/nm-utils.h:38:0,
 from /usr/include/libnm/nm-setting-ip-config.h:31,
 from /usr/include/libnm/nm-setting-ip4-config.h:30,
 from /usr/include/libnm/NetworkManager.h:72,
 from nm-strongswan.c:37:
/usr/include/libnm/nm-setting-tc-config.h:100:16: note: declared here
 typedef struct NMTCTfilter NMTCTfilter;
^~~
cc1: all warnings being treated as errors
=

Please don't use -Wall and -Werror in release builds.

Thanks,
Jeremy Bicha

Bug#885753: network-manager-strongswan: Drop Build-Depends on libgnomeui

[Jeremy Bicha]

Source: network-manager-strongswan
Version: 1.4.2-1
Severity: serious
User: pkg-gnome-maintain...@lists.alioth.debian.org
Usertags: oldlibs libgnomeui
Tags: sid buster patch

As announced [1], we do not intend to release Debian 10 "Buster" with
the old libgnome (and related) libraries. These libraries have been
deprecated and unmaintained for several years.

Your package build-depends on libgnomeui-dev but this shouldn't be
needed anymore. (No patch attached but this should be a trivial fix.)

[1] https://lists.debian.org/debian-devel/2017/10/msg00299.html

On behalf of the Debian GNOME team,
Jeremy Bicha

Bug#885071: missing dependency -> serious

[Kurt Roeckx]

On Fri, Dec 29, 2017 at 02:57:11PM +0100, Andreas Henriksson wrote:
> Control: severity -1 serious
> Control: affects -1 iproute2
> Control: tags -1 + patch
> 
> Hello,
> 
> Missing dependency is a policy violation, thus bumping to severity
> to serious.
> Hopefully this can be fixed very soon (so the "workaround" in iproute2,
> and potentially others, can be dropped).
> 
> Please also note that libdw-dev needs similar treatment, as its .pc file
> also has Required statements to zlib(.pc) and liblzma(.pc).
> 
> Please speak up if you want me to help out with a NMU (or not)!

Feel free to upload this. I can upload it for you if needed.


Kurt

Bug#885749: pegsolitaire: Depends on libgnomeui

[Jeremy Bicha]

Source: pegsolitaire
Version: 0.0.4-2
Severity: serious
User: pkg-gnome-maintain...@lists.alioth.debian.org
Usertags: oldlibs libgnomeui
Tags: sid buster

As announced [1], we do not intend to release Debian 10 "Buster" with
the old libgnome (and related) libraries. These libraries have been
deprecated and unmaintained for several years.

Your package depends and or build-depends on libgnomeui.

Please port your package to GTK3 and related maintained libraries.
Otherwise, please consider requesting that your package be removed from
Debian to help us complete this goal.

[1] https://lists.debian.org/debian-devel/2017/10/msg00299.html

On behalf of the Debian GNOME team,
Jeremy Bicha

Bug#769366: zssh won't start: "out of pty's"

[Rafi Rubin]

For what its worth, building the package from source results in a
functional binary. That makes it a bit harder to debug if its something
in the code.

On the upside, if this is just some binary/library incompatibility, the
solution might just be incrementing the version and forcing the build
system to recompile.

Rafi

On Sat, 23 Dec 2017 04:41:45 -0800 Ben Wong  wrote:
> It's been a decade since I fixed it, so my memory is hazy, but Google shows 
> up a patch as Debian Bug #388036 .
> 
> Ben



signature.asc
Description: OpenPGP digital signature

Bug#885295: gpodder: Depends on unmaintained pygtk

[Thomas Perl]

Upstream here.

gPodder 3.10.0 (just released today) should fix that.


Thanks,
Thomas

> On 26.12.2017, at 06:38, Jeremy Bicha  wrote:
> 
> Source: gpodder
> Version: 3.9.3-1
> Severity: serious
> User: pkg-gnome-maintain...@lists.alioth.debian.org
> Usertags: oldlibs pygtk
> Tags: sid buster
> 
> pygtk is unmaintained upstream. It has not had a release since GNOME 3
> was released in 2011.
> 
> The way forward is to port your app to use GObject Introspection
> bindings.
> 
> For more information on GObject Introspection see [1] and [2].
> 
> Please try to do this before the Buster release as we're going to
> try to remove pygtk this cycle.
> 
> If you have any question don't hesitate to ask.
> 
> [1] https://wiki.gnome.org/Projects/GObjectIntrospection
> [2] https://wiki.gnome.org/Projects/PyGObject
> 
> On behalf of the Debian GNOME team,
> Jeremy Bicha

Processed: Bump severity for libgnome-related bugs

[Debian Bug Tracking System]

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

> severity 868410 serious
Bug #868410 [src:yarssr] yarssr: Please drop the (build-)dependency against 
gnome-vfs
Severity set to 'serious' from 'important'
> severity 868382 serious
Bug #868382 [src:gbatnav] gbatnav: Please drop the (build-)dependency against 
gnome-vfs
Severity set to 'serious' from 'important'
> severity 868411 serious
Bug #868411 [src:gniall] gniall: Please drop the (build-)dependency against 
gnome-vfs
Severity set to 'serious' from 'important'
> severity 868414 serious
Bug #868414 [src:gnome-alsamixer] gnome-alsamixer: Please drop the 
(build-)dependency against gnome-vfs
Severity set to 'serious' from 'important'
> severity 868424 serious
Bug #868424 [src:gnome-breakout] gnome-breakout: Please drop the 
(build-)dependency against gnome-vfs
Severity set to 'serious' from 'important'
> severity 868420 serious
Bug #868420 [src:gstm] gstm: Please drop the (build-)dependency against 
gnome-vfs
Severity set to 'serious' from 'important'
>
End of message, stopping processing here.

Please contact me if you need assistance.
-- 
868382: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=868382
868410: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=868410
868411: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=868411
868414: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=868414
868420: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=868420
868424: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=868424
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#885743: maximus: Depends on libgnomeui

[Jeremy Bicha]

Source: maximums
Version: 0.4.14-4
Severity: serious
User: pkg-gnome-maintain...@lists.alioth.debian.org
Usertags: oldlibs libgnomeui gconf
Tags: sid buster

As announced [1], we do not intend to release Debian 10 "Buster" with
the old libgnome (and related) libraries. These libraries have been
deprecated and unmaintained for several years.

Your package depends and or build-depends on libgnomeui and gconf.

Please port your package to GTK3 and related maintained libraries.
Otherwise, please consider requesting that your package be removed from
Debian to help us complete this goal.

[1] https://lists.debian.org/debian-devel/2017/10/msg00299.html

On behalf of the Debian GNOME team,
Jeremy Bicha

Bug#885742: linsmith: Depends on libgnomeui

[Jeremy Bicha]

Source: linsmith
Version: 0.99.30-1
Severity: serious
User: pkg-gnome-maintain...@lists.alioth.debian.org
Usertags: oldlibs libgnomeui
Tags: sid buster

As announced [1], we do not intend to release Debian 10 "Buster" with
the old libgnome (and related) libraries. These libraries have been
deprecated and unmaintained for several years.

Your package depends and or build-depends on libgnomeui.

Please port your package to GTK3 and related maintained libraries.
Otherwise, please consider requesting that your package be removed from
Debian to help us complete this goal.

[1] https://lists.debian.org/debian-devel/2017/10/msg00299.html

On behalf of the Debian GNOME team,
Jeremy Bicha

Bug#885739: gnome-color-chooser: Depends on libgnomeui

[Jeremy Bicha]

Source: gnome-color-chooser
Version: 0.2.5-1.1
Severity: serious
User: pkg-gnome-maintain...@lists.alioth.debian.org
Usertags: oldlibs libgnomeui
Tags: sid buster

As announced [1], we do not intend to release Debian 10 "Buster" with
the old libgnome (and related) libraries. These libraries have been
deprecated and unmaintained for several years.

Your package depends and or build-depends on libgnomeui.

Please port your package to GTK3 and related maintained libraries.
Otherwise, please consider requesting that your package be removed from
Debian to help us complete this goal.

[1] https://lists.debian.org/debian-devel/2017/10/msg00299.html

On behalf of the Debian GNOME team,
Jeremy Bicha

Bug#885741: gresolver: Depends on libgnomeui

[Jeremy Bicha]

Source: gresolver
Version: 0.0.5-6
Severity: serious
User: pkg-gnome-maintain...@lists.alioth.debian.org
Usertags: oldlibs libgnomeui
Tags: sid buster

As announced [1], we do not intend to release Debian 10 "Buster" with
the old libgnome (and related) libraries. These libraries have been
deprecated and unmaintained for several years.

Your package depends and or build-depends on libgnomeui.

Please port your package to GTK3 and related maintained libraries.
Otherwise, please consider requesting that your package be removed from
Debian to help us complete this goal.

[1] https://lists.debian.org/debian-devel/2017/10/msg00299.html

On behalf of the Debian GNOME team,
Jeremy Bicha

Bug#885740: gnomekiss: Depends on libgnomeui

[Jeremy Bicha]

Source: gnomekiss
Version: 2.0-5
Severity: serious
User: pkg-gnome-maintain...@lists.alioth.debian.org
Usertags: oldlibs libgnomeui
Tags: sid buster

As announced [1], we do not intend to release Debian 10 "Buster" with
the old libgnome (and related) libraries. These libraries have been
deprecated and unmaintained for several years.

Your package depends and or build-depends on libgnomeui.

Please port your package to GTK3 and related maintained libraries.
Otherwise, please consider requesting that your package be removed from
Debian to help us complete this goal.

[1] https://lists.debian.org/debian-devel/2017/10/msg00299.html

On behalf of the Debian GNOME team,
Jeremy Bicha

Processed: Re: Please help porting rasmol to latest vte (Was: Bug#790196: rasmol: depends on vte which is deprecated)

[Debian Bug Tracking System]

Processing control commands:

> tags -1 help
Bug #790196 [src:rasmol] rasmol: depends on vte which is deprecated
Added tag(s) help.

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

Bug#790196: Please help porting rasmol to latest vte (Was: Bug#790196: rasmol: depends on vte which is deprecated)

[Andreas Tille]

Control: tags -1 help

Hi Graham,

On Sat, 4 Jul 2015 12:11:06 +0200 you wrote:
> I'll have a look when I get a chance, possibly at debcamp next month.

I've commited some general packaging changes (short dh would be a nice
thing to have as well but I did not want to fiddle around with this in
a state where the package does not build.  The issue remains the same
for me as I reported previously:

...
Package vte was not found in the pkg-config search path.
Perhaps you should add the directory containing `vte.pc'
to the PKG_CONFIG_PATH environment variable
No package 'vte' found
gcc -g -O2 -fno-strict-aliasing -g -O2 
-fdebug-prefix-map=/build/rasmol-2.7.5.2/src=. -fstack-protector-strong 
-Wformat -Werror=format-security-Dlinux -D__amd64__ -D_POSIX_C_SOURCE=19
9309L-D_POSIX_SOURCE -D_XOPEN_SOURCE
 -D_BSD_SOURCE -D_SVID_SOURCE 
-D_LARGEFILE_SOURCE -D_FILE_OFFSE
T_BITS=64   
-DFUNCPROTO=15 -DNARROWPROTO-DGTKWIN -DRASMOLDIR=\"/usr/share/rasmol/\" 
-DTHIRTYTWOBIT-D_USE_RASMOL
_H_  -I/usr/include/cbf   -I/usr/include   -I/usr/include   
-I/usr/include  -Wdate-time -D_FORTIFY_SOURCE=2  -c -o rasmol.o rasmol.c
Package vte was not found in the pkg-config search path.
Perhaps you should add the directory containing `vte.pc'
to the PKG_CONFIG_PATH environment variable
No package 'vte' found
Package vte was not found in the pkg-config search path.
Perhaps you should add the directory containing `vte.pc'
to the PKG_CONFIG_PATH environment variable
No package 'vte' found
In file included from 
/usr/include/x86_64-linux-gnu/bits/libc-header-start.h:33:0,
 from /usr/include/stdlib.h:25,
 from rasmol.c:203:
/usr/include/features.h:180:3: warning: #warning "_BSD_SOURCE and _SVID_SOURCE 
are deprecated, use _DEFAULT_SOURCE" [-Wcpp]
 # warning "_BSD_SOURCE and _SVID_SOURCE are deprecated, use _DEFAULT_SOURCE"
   ^~~
rasmol.c:237:10: fatal error: gtk/gtk.h: No such file or directory
 #include 
  ^~~
compilation terminated.
...

Kind regards

 Andreas.

-- 
http://fam-tille.de

Bug#885738: gnee: Depends on libgnomeui

[Jeremy Bicha]

Package: gnee
Version: 3.19-1
Severity: serious
User: pkg-gnome-maintain...@lists.alioth.debian.org
Usertags: oldlibs libgnomeui gconf
Tags: sid buster

As announced [1], we do not intend to release Debian 10 "Buster" with
the old libgnome (and related) libraries. These libraries have been
deprecated and unmaintained for several years.

Your package depends and or build-depends on libgnomeui and gconf. It
might be best to drop the gnee package. Otherwise, please port your
package to GTK3 and related maintained libraries.

[1] https://lists.debian.org/debian-devel/2017/10/msg00299.html

On behalf of the Debian GNOME team,
Jeremy Bicha

Bug#885295: gpodder: Depends on unmaintained pygtk

[Jeremy Bicha]

On Fri, Dec 29, 2017 at 10:46 AM, Thomas Perl  wrote:
> Upstream here.
>
> gPodder 3.10.0 (just released today) should fix that.

Thank you!

Jeremy Bicha

Bug#885102: fixed in fpc 3.0.4+dfsg-10

[Paul Gevers]

Control: reopen -1

On Mon, 25 Dec 2017 21:19:00 + Abou Al Montacir
 wrote:
 fpc (3.0.4+dfsg-10) unstable; urgency=medium
 .
   * Fixed upgrade of fp-utils from older version. (Closes: #885102)

This wasn't enough as the +dfsg was forgotten in the version "<=
3.0.4-8" instead of "<= 3.0.4+dfsg-8":

  dpkg: error processing archive
/tmp/apt-dpkg-install-mZOxaI/01-fp-utils-3.0.4_3.0.4+dfsg-10_amd64.deb
(--unpack):
   trying to overwrite '/usr/bin/grab_vcsa-3.0.4', which is also in
package fp-compiler-3.0.4:amd64 3.0.4+dfsg-2
  dpkg-deb: error: paste subprocess was killed by signal (Broken pipe)




signature.asc
Description: OpenPGP digital signature

Processed: Re: Bug#885102: fixed in fpc 3.0.4+dfsg-10

[Debian Bug Tracking System]

Processing control commands:

> reopen -1
Bug #885102 {Done: Abou Al Montacir } [fpc] fpc: 
upgrading from 3.0.4+dfsg-2 to 3.0.4+dfsg-9 fails on /usr/bin/grab_vcsa-3.0.4
'reopen' may be inappropriate when a bug has been closed with a version;
all fixed versions will be cleared, and you may need to re-add them.
Bug reopened
No longer marked as fixed in versions fpc/3.0.4+dfsg-10.

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

Bug#885733: coriander: Depends on old GNOME libraries

[Jeremy Bicha]

Source: coriander
Version: 2.0.2-4
Severity: serious
User: pkg-gnome-maintain...@lists.alioth.debian.org
Usertags: oldlibs libgnomeui
Tags: sid buster

As announced [1], we do not intend to release Debian 10 "Buster" with
the old libgnome (and related) libraries. These libraries have been
deprecated and unmaintained for several years.

Your package depends and or build-depends on libgnomeui.

Please port your package to GTK3 and related maintained libraries.
Otherwise, please consider requesting that your package be removed from
Debian to help us complete this goal.

[1] https://lists.debian.org/debian-devel/2017/10/msg00299.html

On behalf of the Debian GNOME team,
Jeremy Bicha

Processed: Re: swt4-gtk: Please drop the (build-)dependency against gnome-vfs

[Debian Bug Tracking System]

Processing control commands:

> tags -1 +patch
Bug #868404 [src:swt4-gtk] swt4-gtk: Please drop the (build-)dependency against 
gnome-vfs
Added tag(s) patch.
> severity -1 serious
Bug #868404 [src:swt4-gtk] swt4-gtk: Please drop the (build-)dependency against 
gnome-vfs
Severity set to 'serious' from 'important'

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

Bug#884041: marked as done (node-braces FTBFS: test failures)

[Debian Bug Tracking System]

Your message dated Fri, 29 Dec 2017 15:08:14 +
with message-id 
and subject line Bug#884041: fixed in node-braces 2.0.2-2
has caused the Debian Bug report #884041,
regarding node-braces FTBFS: 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.)


-- 
884041: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=884041
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: node-braces
Version: 2.0.2-1
Severity: serious
Tags: buster sid

Some recent change in unstable makes node-braces FTBFS:

https://tests.reproducible-builds.org/debian/history/node-braces.html
https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/node-braces.html

...
  5 failing

  1) bash.expanded should compile: {214748364..2147483649}:
 AssertionError: {214748364..2147483649}
  at match (/build/1st/node-braces-2.0.2/test/bash.expanded.js:9:10)
  at Context. 
(/build/1st/node-braces-2.0.2/test/bash.expanded.js:408:7)
  at callFn (/usr/lib/nodejs/mocha/lib/runnable.js:223:21)
  at Test.Runnable.run (/usr/lib/nodejs/mocha/lib/runnable.js:216:7)
  at Runner.runTest (/usr/lib/nodejs/mocha/lib/runner.js:373:10)
  at /usr/lib/nodejs/mocha/lib/runner.js:451:12
  at next (/usr/lib/nodejs/mocha/lib/runner.js:298:14)
  at /usr/lib/nodejs/mocha/lib/runner.js:308:7
  at next (/usr/lib/nodejs/mocha/lib/runner.js:246:23)
  at Immediate. (/usr/lib/nodejs/mocha/lib/runner.js:275:5)
  at runCallback (timers.js:672:20)
  at tryOnImmediate (timers.js:645:5)
  at processImmediate [as _immediateCallback] (timers.js:617:5)

  2) bash.expanded should compile: {214748364..2147483649}:
 AssertionError: {214748364..2147483649}
  at match (/build/1st/node-braces-2.0.2/test/bash.optimized.js:9:10)
  at Context. 
(/build/1st/node-braces-2.0.2/test/bash.optimized.js:406:7)
  at callFn (/usr/lib/nodejs/mocha/lib/runnable.js:223:21)
  at Test.Runnable.run (/usr/lib/nodejs/mocha/lib/runnable.js:216:7)
  at Runner.runTest (/usr/lib/nodejs/mocha/lib/runner.js:373:10)
  at /usr/lib/nodejs/mocha/lib/runner.js:451:12
  at next (/usr/lib/nodejs/mocha/lib/runner.js:298:14)
  at /usr/lib/nodejs/mocha/lib/runner.js:308:7
  at next (/usr/lib/nodejs/mocha/lib/runner.js:246:23)
  at Immediate. (/usr/lib/nodejs/mocha/lib/runner.js:275:5)
  at runCallback (timers.js:672:20)
  at tryOnImmediate (timers.js:645:5)
  at processImmediate [as _immediateCallback] (timers.js:617:5)

  3) bash.expanded should compile: {214748364..2147483649}:
 AssertionError: {214748364..2147483649}
  at match (/build/1st/node-braces-2.0.2/test/bash.optimized.js:9:10)
  at Context. 
(/build/1st/node-braces-2.0.2/test/bash.optimized.js:406:7)
  at callFn (/usr/lib/nodejs/mocha/lib/runnable.js:223:21)
  at Test.Runnable.run (/usr/lib/nodejs/mocha/lib/runnable.js:216:7)
  at Runner.runTest (/usr/lib/nodejs/mocha/lib/runner.js:373:10)
  at /usr/lib/nodejs/mocha/lib/runner.js:451:12
  at next (/usr/lib/nodejs/mocha/lib/runner.js:298:14)
  at /usr/lib/nodejs/mocha/lib/runner.js:308:7
  at next (/usr/lib/nodejs/mocha/lib/runner.js:246:23)
  at Immediate. (/usr/lib/nodejs/mocha/lib/runner.js:275:5)
  at runCallback (timers.js:672:20)
  at tryOnImmediate (timers.js:645:5)
  at processImmediate [as _immediateCallback] (timers.js:617:5)

  4) expanded ranges large numbers should expand large numbers:
 AssertionError: [ 
'(21474836[4-9]|2147483[7-9][0-9]|214748[4-9][0-9]{2}|214749[0-9]{3}|2147[5-9][0-9]{4}|214[89][0-9]{5}|21[5-9][0-9]{6}|2[2-9][
 deepEqual [ 
'(21474836[4-9]|2147483[7-9][0-9]|214748[4-9][0-9]{2}|214749[0-9]{3}|2147[5-9][0-9]{4}|214[8-9][0-9]{5}|21[5-9][0-9]{6}|2[2-9]
  at match (/build/1st/node-braces-2.0.2/test/expanded.ranges.js:8:10)
  at Context. 
(/build/1st/node-braces-2.0.2/test/expanded.ranges.js:128:7)
  at callFn (/usr/lib/nodejs/mocha/lib/runnable.js:223:21)
  at Test.Runnable.run (/usr/lib/nodejs/mocha/lib/runnable.js:216:7)
  at Runner.runTest (/usr/lib/nodejs/mocha/lib/runner.js:373:10)
  at /usr/lib/nodejs/mocha/lib/runner.js:451:12
  at next (/usr/lib/nodejs/mocha/lib/runner.js:298:14)
  at /usr/lib/nodejs/mocha/lib/runner.js:308:7
  at next (/usr/lib/nodejs/mocha/lib/runner.js:246:23)
  at Immediate. (/usr/lib/nodejs/mocha/lib/runner.js:275:5)
  at runCallback (timers.js:672:20)
  at 

Processed: pending madplay bugs

[Debian Bug Tracking System]

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

> # NMU in DELAYED/9 by now
> tags 856085 pending
Bug #856085 [src:madplay] madplay: Please drop the (build-)dependency against 
esound
Added tag(s) pending.
> tags 865188 pending
Bug #865188 [src:madplay] madplay: please build-depend on automake, not 
obsolete automake1.11
Added tag(s) pending.
> tags 868709 pending
Bug #868709 [src:madplay] Updating the madplay Uploaders list
Added tag(s) pending.
> thanks
Stopping processing here.

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

Processed: FrontAccounting solved problems marked as pending

[Debian Bug Tracking System]

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

> package frontaccounting
Limiting to bugs with field 'package' containing at least one of 
'frontaccounting'
Limit currently set to 'package':'frontaccounting'

> reopen 669755
Bug #669755 {Done: Janusz Dobrowolski } 
[frontaccounting] frontaccounting: transition towards Apache 2.4
Bug reopened
Ignoring request to alter fixed versions of bug #669755 to the same values 
previously set
> tag 669755 +pending
Bug #669755 [frontaccounting] frontaccounting: transition towards Apache 2.4
Added tag(s) pending.
> reopen 717301
Bug #717301 {Done: Janusz Dobrowolski } 
[frontaccounting] frontaccounting: Fails to install interactively (and 
according to another bug non-interactively as well)
'reopen' may be inappropriate when a bug has been closed with a version;
all fixed versions will be cleared, and you may need to re-add them.
Bug reopened
No longer marked as fixed in versions 2.4.3-1.
> tag 717301 +pending
Bug #717301 [frontaccounting] frontaccounting: Fails to install interactively 
(and according to another bug non-interactively as well)
Added tag(s) pending.
> reopen 767300
Bug #767300 {Done: Janusz Dobrowolski } 
[frontaccounting] frontaccounting: [INTL:nl] Dutch translation of debconf 
messages
Bug reopened
Ignoring request to alter fixed versions of bug #767300 to the same values 
previously set
> tag 767300 +pending
Bug #767300 [frontaccounting] frontaccounting: [INTL:nl] Dutch translation of 
debconf messages
Added tag(s) pending.
> reopen 767300
Bug #767300 [frontaccounting] frontaccounting: [INTL:nl] Dutch translation of 
debconf messages
Bug 767300 is not marked as done; doing nothing.
> tag 767300 +pending
Bug #767300 [frontaccounting] frontaccounting: [INTL:nl] Dutch translation of 
debconf messages
Ignoring request to alter tags of bug #767300 to the same tags previously set
> reopen 768032
Bug #768032 {Done: Janusz Dobrowolski } 
[frontaccounting] frontaccounting: fails to install: ERROR 1146 (42S02) at line 
1: Table 'frontaccounting.0_company' doesn't exist
'reopen' may be inappropriate when a bug has been closed with a version;
all fixed versions will be cleared, and you may need to re-add them.
Bug reopened
No longer marked as fixed in versions 2.4.3-1.
> tag 768032 +pending
Bug #768032 [frontaccounting] frontaccounting: fails to install: ERROR 1146 
(42S02) at line 1: Table 'frontaccounting.0_company' doesn't exist
Added tag(s) pending.
> reopen 808919
Bug #808919 {Done: Janusz Dobrowolski } 
[frontaccounting] frontaccounting uses deprecated find -perm +xxx syntax, 
please switch to find -perm /+++
Bug reopened
Ignoring request to alter fixed versions of bug #808919 to the same values 
previously set
> tag 808919 +pending
Bug #808919 [frontaccounting] frontaccounting uses deprecated find -perm +xxx 
syntax, please switch to find -perm /+++
Added tag(s) pending.
>
End of message, stopping processing here.

Please contact me if you need assistance.
-- 
669755: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=669755
717301: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=717301
767300: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=767300
768032: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=768032
808919: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=808919
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Processed: missing dependency -> serious

[Debian Bug Tracking System]

Processing control commands:

> severity -1 serious
Bug #885071 [libelf-dev] libelf-dev: pkg-config --exists/--cflags libelf fail 
without zlib1g-dev
Severity set to 'serious' from 'normal'
> affects -1 iproute2
Bug #885071 [libelf-dev] libelf-dev: pkg-config --exists/--cflags libelf fail 
without zlib1g-dev
Added indication that 885071 affects iproute2
> tags -1 + patch
Bug #885071 [libelf-dev] libelf-dev: pkg-config --exists/--cflags libelf fail 
without zlib1g-dev
Added tag(s) patch.

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

Bug#853451: marked as done (infinipath-psm: ftbfs with GCC-7)

[Debian Bug Tracking System]

Your message dated Fri, 29 Dec 2017 13:34:11 +
with message-id 
and subject line Bug#853451: fixed in infinipath-psm 3.3+20.604758e7-1
has caused the Debian Bug report #853451,
regarding infinipath-psm: ftbfs with GCC-7
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.)


-- 
853451: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=853451
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:infinipath-psm
Version: 3.3+19.g67c0807.open-3
Severity: normal
Tags: sid buster
User: debian-...@lists.debian.org
Usertags: ftbfs-gcc-7

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

The package fails to build in a test rebuild on at least amd64 with
gcc-7/g++-7, but succeeds to build with gcc-6/g++-6. The
severity of this report may be raised before the buster release.
There is no need to fix this issue in time for the stretch release.

The full build log can be found at:
http://people.debian.org/~doko/logs/gcc7-20170126/infinipath-psm_3.3+19.g67c0807.open-3_unstable_gcc7.log
The last lines of the build log are at the end of this report.

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

  apt-get -t=experimental install g++ 

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

[...]
cc -g -O2 
-fdebug-prefix-map=/<>/infinipath-psm-3.3+19.g67c0807.open=. 
-fstack-protector-strong -Wformat -Werror=format-security   -Wall -Werror  
-fpic -fPIC -D_GNU_SOURCE -funwind-tables   -O3 -g3   -DNVALGRIND   -Wall 
-Werror  -fpic -fPIC -D_GNU_SOURCE -funwind-tables   -O3 -g3  
-DPSM_USE_SYS_UUID  -DNVALGRIND -I. 
-I/<>/infinipath-psm-3.3+19.g67c0807.open/include 
-I/<>/infinipath-psm-3.3+19.g67c0807.open/mpspawn 
-I/<>/infinipath-psm-3.3+19.g67c0807.open/include/linux-x86_64  
-I/<>/infinipath-psm-3.3+19.g67c0807.open -I/ptl_ips -c ips_spio.c -o 
ips_spio.o
cc -g -O2 
-fdebug-prefix-map=/<>/infinipath-psm-3.3+19.g67c0807.open=. 
-fstack-protector-strong -Wformat -Werror=format-security   -Wall -Werror  
-fpic -fPIC -D_GNU_SOURCE -funwind-tables   -O3 -g3   -DNVALGRIND   -Wall 
-Werror  -fpic -fPIC -D_GNU_SOURCE -funwind-tables   -O3 -g3  
-DPSM_USE_SYS_UUID  -DNVALGRIND -I. 
-I/<>/infinipath-psm-3.3+19.g67c0807.open/include 
-I/<>/infinipath-psm-3.3+19.g67c0807.open/mpspawn 
-I/<>/infinipath-psm-3.3+19.g67c0807.open/include/linux-x86_64  
-I/<>/infinipath-psm-3.3+19.g67c0807.open -I/ptl_ips -c 
ips_proto_recv.c -o ips_proto_recv.o
cc -g -O2 
-fdebug-prefix-map=/<>/infinipath-psm-3.3+19.g67c0807.open=. 
-fstack-protector-strong -Wformat -Werror=format-security   -Wall -Werror  
-fpic -fPIC -D_GNU_SOURCE -funwind-tables   -O3 -g3   -DNVALGRIND   -Wall 
-Werror  -fpic -fPIC -D_GNU_SOURCE -funwind-tables   -O3 -g3  
-DPSM_USE_SYS_UUID  -DNVALGRIND -I. 
-I/<>/infinipath-psm-3.3+19.g67c0807.open/include 
-I/<>/infinipath-psm-3.3+19.g67c0807.open/mpspawn 
-I/<>/infinipath-psm-3.3+19.g67c0807.open/include/linux-x86_64  
-I/<>/infinipath-psm-3.3+19.g67c0807.open -I/ptl_ips -c 
ips_proto_connect.c -o ips_proto_connect.o
cc -g -O2 
-fdebug-prefix-map=/<>/infinipath-psm-3.3+19.g67c0807.open=. 
-fstack-protector-strong -Wformat -Werror=format-security   -Wall -Werror  
-fpic -fPIC -D_GNU_SOURCE -funwind-tables   -O3 -g3   -DNVALGRIND   -Wall 
-Werror  -fpic -fPIC -D_GNU_SOURCE -funwind-tables   -O3 -g3  
-DPSM_USE_SYS_UUID  -DNVALGRIND -I. 
-I/<>/infinipath-psm-3.3+19.g67c0807.open/include 
-I/<>/infinipath-psm-3.3+19.g67c0807.open/mpspawn 
-I/<>/infinipath-psm-3.3+19.g67c0807.open/include/linux-x86_64  
-I/<>/infinipath-psm-3.3+19.g67c0807.open -I/ptl_ips -c 
ips_proto_dump.c -o ips_proto_dump.o
cc -g -O2 
-fdebug-prefix-map=/<>/infinipath-psm-3.3+19.g67c0807.open=. 
-fstack-protector-strong -Wformat -Werror=format-security   -Wall -Werror  
-fpic -fPIC -D_GNU_SOURCE -funwind-tables   -O3 -g3   -DNVALGRIND   -Wall 
-Werror  -fpic -fPIC -D_GNU_SOURCE -funwind-tables   -O3 -g3  
-DPSM_USE_SYS_UUID  -DNVALGRIND -I. 
-I/<>/infinipath-psm-3.3+19.g67c0807.open/include 
-I/<>/infinipath-psm-3.3+19.g67c0807.open/mpspawn 

Bug#885491: ttb: Depends on unmaintained pygtk

[Juhani Numminen]

On Wed, 27 Dec 2017 10:53:15 -0500 Jeremy Bicha  wrote:

> pygtk is unmaintained upstream. It has not had a release since GNOME 3
> was released in 2011.
> 
> The way forward is to port your app to use GObject Introspection
> bindings (and gtk3).
> 
> For more information on GObject Introspection see [1] and [2].
> 
> Please try to do this before the Buster release as we're going to
> try to remove pygtk this cycle.

I'm reporting my findings regarding ttb. The original author writes,
at http://www.djcbsoftware.nl/software.html:

> After some changes in the teletext service, ttb stopped working in early 2013;
> since then, I’ve written a replacement called ttx; this program not only
> handles the Dutch Teletekst system, but also supports Belgian, Croatian,
> Finnish, Austrian, Italian, Portuguese, Spanish and Slovenian providers.

The replacement is written in C and seems to be using gtk3:
https://github.com/djcb/ttx


Regards,
Juhani

Processed: Set forwarded

[Debian Bug Tracking System]

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

> forwarded 883526 https://github.com/BestImageViewer/geeqie/issues/563
Bug #883526 [src:geeqie] geeqie build does not trap errors from make
Set Bug forwarded-to-address to 
'https://github.com/BestImageViewer/geeqie/issues/563'.
> thanks
Stopping processing here.

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

Bug#790171: genius: depends on vte which is deprecated

[Felipe Sateler]

Hi  Jiří,

On Thu, Dec 28, 2017 at 1:46 AM, Jeremy Bicha  wrote:

> Control: severity -1 serious
> Control: tags -1 -stretch
>
> We do not intent to release Debian 10 "Buster" with src: vte.
> Therefore, I am raising the severity of this bug.
>
>
>
>
It appears the time has come to migrate away...



-- 

Saludos,
Felipe Sateler

Bug#859841: zurl: Please migrate to openssl1.1 in Buster

[Jan Niehusmann]

After another 3 weeks, the status of libcurl3 unfortunately didn't
change at all.

The discussion on https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=858398
continues really slowly, and there is no sign of actual progress :-(

Jan

Processed: Remove pending

[Debian Bug Tracking System]

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

> tags 883526 - pending
Bug #883526 [src:geeqie] geeqie build does not trap errors from make
Removed tag(s) pending.
> thanks
Stopping processing here.

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

Bug#885302: gtklick: Depends on unmaintained pygtk

[Jaromír Mikeš]

2017-12-26 6:42 GMT+01:00 Jeremy Bicha :

> Source: gtklick
> Version: 0.6.4-5
> Severity: serious
> User: pkg-gnome-maintain...@lists.alioth.debian.org
> Usertags: oldlibs pygtk
> Tags: sid buster
>
> pygtk is unmaintained upstream. It has not had a release since GNOME 3
> was released in 2011.
>
> The way forward is to port your app to use GObject Introspection
> bindings.
>
> For more information on GObject Introspection see [1] and [2].
>
> Please try to do this before the Buster release as we're going to
> try to remove pygtk this cycle.
>
> If you have any question don't hesitate to ask.
>
> [1] https://wiki.gnome.org/Projects/GObjectIntrospection
> [2] https://wiki.gnome.org/Projects/PyGObject
>
> On behalf of the Debian GNOME team,
> Jeremy Bicha
>
> ___
> pkg-multimedia-maintainers mailing list
> pkg-multimedia-maintain...@lists.alioth.debian.org
> http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/
> pkg-multimedia-maintainers


​Hi Dominic,

there is a serious issue with gtklick in debian.
Is there any chance get this fixed and avoid pygtk dependency?

best regrads

mira​

Bug#885699: smokeping: symbolic link to smokeping.cgi missing

[Sigbjorn Kjetland]

Package: smokeping
Version: 2.6.11-3
Severity: serious
Justification: Policy 10.5

Dear Maintainer,

   * What led up to the situation?
I am installing smokeping on a new server to replace old smokeping server
 I have configured and restarted smokeping like in previous server
 but web GUI did not work. Error was 403 forbidden.
 fcgi not working and I have limited knowledge so i didn't go that route.
   * What exactly did you do (or not do) that was effective (or
 ineffective)?
I added these 3 lines to apache config file:
/etc/apache2/conf-enabled/smokeping.conf
Options Indexes FollowSymLinks ExecCGI
AddHandler cgi-script .cgi
DirectoryIndex index.html smokeping.cgi

There was no working fcgi file and no cgi file so I linked the cgi as
below

ln -s /usr/lib/cgi-bin/smokeping.cgi
/usr/share/smokeping/www/smokeping.cgi
   * What was the outcome of this action?
   I could then open the web gui as expected
   * What outcome did you expect instead?


-- System Information:
Debian Release: 9.3
  APT prefers stable-updates
  APT policy: (500, 'stable-updates'), (500, 'stable')
Architecture: amd64 (x86_64)

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

Versions of packages smokeping depends on:
ii  adduser3.115
ii  debianutils4.8.1.1
ii  exim4-daemon-light [mail-transport-agent]  4.89-2+deb9u2
ii  fping  3.15-1
ii  libcgi-fast-perl   1:2.12-1
ii  libconfig-grammar-perl 1.12-1
ii  libdigest-hmac-perl1.03+dfsg-1
ii  libjs-cropper  1.2.2-1
ii  libjs-prototype1.7.1-3
ii  libjs-scriptaculous1.9.0-2
ii  librrds-perl   1.6.0-1+b2
ii  libsnmp-session-perl   1.13-1.1
ii  liburi-perl1.71-1
ii  libwww-perl6.15-1
ii  lsb-base   9.20161125
ii  perl   5.24.1-3+deb9u2
ii  ucf3.0036

Versions of packages smokeping recommends:
ii  apache2 [httpd-cgi]  2.4.25-3+deb9u3
ii  dnsutils 1:9.10.3.dfsg.P4-12.3+deb9u3
ii  echoping 6.0.2-10
ii  libsocket6-perl  0.27-1+b1

Versions of packages smokeping suggests:
pn  curl   
ii  exim4-daemon-light [mail-transport-agent]  4.89-2+deb9u2
pn  libauthen-radius-perl  
ii  libio-socket-ssl-perl  2.044-1
pn  libnet-dns-perl
pn  libnet-ldap-perl   
pn  libnet-telnet-perl 
ii  openssh-client 1:7.4p1-10+deb9u2

-- Configuration Files:
/etc/apache2/conf-available/smokeping.conf changed [not included]
/etc/smokeping/config.d/Alerts changed [not included]
/etc/smokeping/config.d/Targets changed [not included]
/etc/smokeping/smokeping_secrets [Errno 13] Permission denied: 
'/etc/smokeping/smokeping_secrets'

-- no debconf information

Bug#885622: marked as done (bsdmainutils FTBFS: missing libncurses5-dev build dependency for using termcap.h)

[Debian Bug Tracking System]

Your message dated Fri, 29 Dec 2017 09:48:52 +
with message-id 
and subject line Bug#885622: fixed in bsdmainutils 11.1.2
has caused the Debian Bug report #885622,
regarding bsdmainutils FTBFS: missing libncurses5-dev build dependency for 
using termcap.h
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.)


-- 
885622: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=885622
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: bsdmainutils
Version: 11.1.1
Severity: serious
Tags: patch
User: helm...@debian.org
Usertags: rebootstrap

bsdmainutils fails to build from source, because it tries to use
termcap.h without build-depending on libncurses5-dev. After adding the
dependency it builds successfully on amd64. I'm attaching a patch for
your convenience.

Helmut
diff --minimal -Nru bsdmainutils-11.1.1/debian/changelog 
bsdmainutils-11.1.1+nmu1/debian/changelog
--- bsdmainutils-11.1.1/debian/changelog2017-12-27 13:51:13.0 
+0100
+++ bsdmainutils-11.1.1+nmu1/debian/changelog   2017-12-28 18:17:50.0 
+0100
@@ -1,3 +1,10 @@
+bsdmainutils (11.1.1+nmu1) UNRELEASED; urgency=medium
+
+  * Non-maintainer upload.
+  * Fix FTBFS: Add libncurses5-dev to Build-Depends. (Closes: #-1)
+
+ -- Helmut Grohne   Thu, 28 Dec 2017 18:17:50 +0100
+
 bsdmainutils (11.1.1) unstable; urgency=medium
 
   * Update to latest FreeBSD/OpenBSD versions.
diff --minimal -Nru bsdmainutils-11.1.1/debian/control 
bsdmainutils-11.1.1+nmu1/debian/control
--- bsdmainutils-11.1.1/debian/control  2017-12-27 13:51:13.0 +0100
+++ bsdmainutils-11.1.1+nmu1/debian/control 2017-12-28 18:17:48.0 
+0100
@@ -3,7 +3,7 @@
 Priority: important
 Maintainer: Debian Bsdmainutils Team 
 Uploaders: Michael Meskes 
-Build-Depends: debhelper (>= 9), libtinfo-dev, quilt (>= 0.40), python:native, 
python-hdate:native, libbsd-dev
+Build-Depends: debhelper (>= 9), libtinfo-dev, quilt (>= 0.40), python:native, 
python-hdate:native, libbsd-dev, libncurses5-dev
 Standards-Version: 4.1.2
 Vcs-Git: git://anonscm.debian.org/bsdmainutils/bsdmainutils.git
 Vcs-Browser: https://anonscm.debian.org/gitweb/?p=bsdmainutils/bsdmainutils.git
--- End Message ---
--- Begin Message ---
Source: bsdmainutils
Source-Version: 11.1.2

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

Debian distribution maintenance software
pp.
Michael Meskes  (supplier of updated bsdmainutils 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: Fri, 29 Dec 2017 10:26:58 +0100
Source: bsdmainutils
Binary: bsdmainutils
Architecture: source amd64
Version: 11.1.2
Distribution: unstable
Urgency: medium
Maintainer: Debian Bsdmainutils Team 
Changed-By: Michael Meskes 
Description:
 bsdmainutils - collection of more utilities from FreeBSD
Closes: 885622
Changes:
 bsdmainutils (11.1.2) unstable; urgency=medium
 .
   * Switch build dependency back from libtinfo to libncurses. (Closes: #885622)
Checksums-Sha1:
 697f1be6ebb4089dbb1391ac9d434b26ccc7a88b 1747 bsdmainutils_11.1.2.dsc
 d9f68d77f6b2a1bca38be548c5d38936d1fef0ae 286478 bsdmainutils_11.1.2.tar.gz
 f3f9b5b5ad2901152ad2b86d24f078ee53a50c0b 122296 
bsdmainutils-dbgsym_11.1.2_amd64.deb
 6d93bbc19cda3574b5486d748ead46e5fa6dbc81 6293 
bsdmainutils_11.1.2_amd64.buildinfo
 39b80cac227815b3f1f203479aef84b589e4c49d 190428 bsdmainutils_11.1.2_amd64.deb
Checksums-Sha256:
 6734e27f001c1293a6426266f4cf28c8ed229690f8c40d2539cae6151cb29156 1747 
bsdmainutils_11.1.2.dsc
 101c0dede5f599921533da08a46b53a60936445e54aa5df1b31608f1407fee60 286478 
bsdmainutils_11.1.2.tar.gz
 05b03dccefe3c90d55d896bd7dfcafb5d33b525b147fe9546c0f14b82b05d129 122296 
bsdmainutils-dbgsym_11.1.2_amd64.deb
 308f7273d437b55ea1806622452b28cb42c51a194a5eb11a40bea97cccbc3289 6293 
bsdmainutils_11.1.2_amd64.buildinfo
 d2cf3652cd5a2c1da684c5753368f9cbfc3514e0544268fd135151d3f8dadbf6 190428 

Bug#885622: bsdmainutils FTBFS: missing libncurses5-dev build dependency for using termcap.h

[Michael Meskes]

> bsdmainutils fails to build from source, because it tries to use
> termcap.h without build-depending on libncurses5-dev. After adding
> the
> dependency it builds successfully on amd64. I'm attaching a patch for
> your convenience.

Actually bsdmainutils does not need ncurses but tinfo. However, I
missed the strange setup that all tinfo header files are in libncurses-
dev instead of libtinfo-dev. Therefore I'll switch the dependency back.

Thanks.

Michael
-- 
Michael Meskes
Michael at Fam-Meskes dot De, Michael at Meskes dot (De|Com|Net|Org)
Meskes at (Debian|Postgresql) dot Org
Jabber: michael at xmpp dot meskes dot org
VfL Borussia! Força Barça! SF 49ers! Use Debian GNU/Linux, PostgreSQL

Bug#885254: bluewho: Depends on deprecated pygtk

[Juhani Numminen]

Control: tags -1 fixed-upstream

On Mon, 25 Dec 2017 23:39:04 -0500 Jeremy Bicha  wrote:

> pygtk is unmaintained upstream. It has not had a release since
> GNOME 3 was released in 2011.
> 
> The way forward is to port your app to use GObject Introspection
> bindings.
> 
> For more information on GObject Introspection see [1] and [2].
> 
> Please try to do this before the Buster release as we're going to
> try to remove pygtk this cycle.

The latest upstream version bluewho 0.2.2 (from 2014) uses GObject
Introspection and GTK+ 3 already.

Juhani

Processed: Re: bluewho: Depends on deprecated pygtk

[Debian Bug Tracking System]

Processing control commands:

> tags -1 fixed-upstream
Bug #885254 [bluewho] bluewho: Depends on deprecated pygtk
Added tag(s) fixed-upstream.

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

Bug#883526: [/master] Add patch trap_errors_from_make.patch (Closes: #883526)

[Helmut Grohne]

Control: reopen -1

On Mon, Dec 25, 2017 at 08:12:15PM +, Andreas Rönnquist wrote:
> Add patch trap_errors_from_make.patch (Closes: #883526)

Thank you for attempting to fix this. Unfortunately, this doesn't quite
do it. My initial suggestion to add set -e apparently doesn't do it.

Essentially what's there is roughly similar to

( echo 1; false; echo 2 ) || echo 3

and you changed it to

( set -e; echo 1; false; echo 2 ) || echo 3

according to my wrong suggestion. Unfortunately, this prints 1 and 2,
but not 3 and gives a successful return. This is unintuitive to me and
is explained at
https://unix.stackexchange.com/questions/296526/set-e-in-a-subshell. I'm
sorry for not having seen this initially. In any case, it doesn't
propagate the failure now.

Furthermore, there are other instances of this issue. One is with
invoking GLIB_GENMARSHAL from src/Makefile.am. But src/doc/Makefile.am
and src/icons/Makefile.am suffer from the same issues.

Helmut

Processed: Re: Bug#883526: [/master] Add patch trap_errors_from_make.patch (Closes: #883526)

[Debian Bug Tracking System]

Processing control commands:

> reopen -1
Bug #883526 {Done: Andreas Rönnquist } [src:geeqie] geeqie 
build does not trap errors from make
'reopen' may be inappropriate when a bug has been closed with a version;
all fixed versions will be cleared, and you may need to re-add them.
Bug reopened
No longer marked as fixed in versions geeqie/1:1.3-1.1.

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