Bug#895342: suricata: new version fails to start if eth0 not present

[Steve Langasek]

Package: suricata
Version: 1:4.0.4-1
Severity: serious
User: ubuntu-de...@lists.ubuntu.com
Usertags: origin-ubuntu bionic autopkgtest

Dear maintainers,

The latest version of suricata is failing its autopkgtests in Ubuntu because
the suricata daemon does not start in the test environment.  This appears to
be due to the fact that the default suricata config assumes eth0 as an
interface name, but the testbed has ens2 as its default interface:

# /usr/bin/suricata --af-packet -c /etc/suricata/suricata.yaml --pidfile 
/var/run/suricata.pid 
10/4/2018 -- 05:31:56 -  - This is Suricata version 4.0.4 RELEASE
10/4/2018 -- 05:31:56 -  - [ERRCODE: SC_ERR_SYSCALL(50)] - Failure 
when trying to get MTU via ioctl for 'eth0': No such device (19)
10/4/2018 -- 05:31:56 -  - [ERRCODE: SC_ERR_SYSCALL(50)] - Failure 
when trying to get MTU via ioctl for 'eth0': No such device (19)
10/4/2018 -- 05:31:56 -  - [ERRCODE: SC_ERR_NO_RULES(42)] - No rule 
files match the pattern /etc/suricata/rules/botcc.rules
10/4/2018 -- 05:31:56 -  - [ERRCODE: SC_ERR_NO_RULES(42)] - No rule 
files match the pattern /etc/suricata/rules/ciarmy.rules
10/4/2018 -- 05:31:56 -  - [ERRCODE: SC_ERR_NO_RULES(42)] - No rule 
files match the pattern /etc/suricata/rules/compromised.rules
10/4/2018 -- 05:31:56 -  - [ERRCODE: SC_ERR_NO_RULES(42)] - No rule 
files match the pattern /etc/suricata/rules/drop.rules
10/4/2018 -- 05:31:56 -  - [ERRCODE: SC_ERR_NO_RULES(42)] - No rule 
files match the pattern /etc/suricata/rules/dshield.rules
10/4/2018 -- 05:31:56 -  - [ERRCODE: SC_ERR_NO_RULES(42)] - No rule 
files match the pattern /etc/suricata/rules/emerging-attack_response.rules
10/4/2018 -- 05:31:56 -  - [ERRCODE: SC_ERR_NO_RULES(42)] - No rule 
files match the pattern /etc/suricata/rules/emerging-chat.rules
10/4/2018 -- 05:31:56 -  - [ERRCODE: SC_ERR_NO_RULES(42)] - No rule 
files match the pattern /etc/suricata/rules/emerging-current_events.rules
10/4/2018 -- 05:31:56 -  - [ERRCODE: SC_ERR_NO_RULES(42)] - No rule 
files match the pattern /etc/suricata/rules/emerging-dns.rules
10/4/2018 -- 05:31:56 -  - [ERRCODE: SC_ERR_NO_RULES(42)] - No rule 
files match the pattern /etc/suricata/rules/emerging-dos.rules
10/4/2018 -- 05:31:56 -  - [ERRCODE: SC_ERR_NO_RULES(42)] - No rule 
files match the pattern /etc/suricata/rules/emerging-exploit.rules
10/4/2018 -- 05:31:56 -  - [ERRCODE: SC_ERR_NO_RULES(42)] - No rule 
files match the pattern /etc/suricata/rules/emerging-ftp.rules
10/4/2018 -- 05:31:56 -  - [ERRCODE: SC_ERR_NO_RULES(42)] - No rule 
files match the pattern /etc/suricata/rules/emerging-imap.rules
10/4/2018 -- 05:31:56 -  - [ERRCODE: SC_ERR_NO_RULES(42)] - No rule 
files match the pattern /etc/suricata/rules/emerging-malware.rules
10/4/2018 -- 05:31:56 -  - [ERRCODE: SC_ERR_NO_RULES(42)] - No rule 
files match the pattern /etc/suricata/rules/emerging-misc.rules
10/4/2018 -- 05:31:56 -  - [ERRCODE: SC_ERR_NO_RULES(42)] - No rule 
files match the pattern /etc/suricata/rules/emerging-mobile_malware.rules
10/4/2018 -- 05:31:56 -  - [ERRCODE: SC_ERR_NO_RULES(42)] - No rule 
files match the pattern /etc/suricata/rules/emerging-netbios.rules
10/4/2018 -- 05:31:56 -  - [ERRCODE: SC_ERR_NO_RULES(42)] - No rule 
files match the pattern /etc/suricata/rules/emerging-p2p.rules
10/4/2018 -- 05:31:56 -  - [ERRCODE: SC_ERR_NO_RULES(42)] - No rule 
files match the pattern /etc/suricata/rules/emerging-policy.rules
10/4/2018 -- 05:31:56 -  - [ERRCODE: SC_ERR_NO_RULES(42)] - No rule 
files match the pattern /etc/suricata/rules/emerging-pop3.rules
10/4/2018 -- 05:31:56 -  - [ERRCODE: SC_ERR_NO_RULES(42)] - No rule 
files match the pattern /etc/suricata/rules/emerging-rpc.rules
10/4/2018 -- 05:31:56 -  - [ERRCODE: SC_ERR_NO_RULES(42)] - No rule 
files match the pattern /etc/suricata/rules/emerging-scan.rules
10/4/2018 -- 05:31:56 -  - [ERRCODE: SC_ERR_NO_RULES(42)] - No rule 
files match the pattern /etc/suricata/rules/emerging-smtp.rules
10/4/2018 -- 05:31:56 -  - [ERRCODE: SC_ERR_NO_RULES(42)] - No rule 
files match the pattern /etc/suricata/rules/emerging-snmp.rules
10/4/2018 -- 05:31:56 -  - [ERRCODE: SC_ERR_NO_RULES(42)] - No rule 
files match the pattern /etc/suricata/rules/emerging-sql.rules
10/4/2018 -- 05:31:56 -  - [ERRCODE: SC_ERR_NO_RULES(42)] - No rule 
files match the pattern /etc/suricata/rules/emerging-telnet.rules
10/4/2018 -- 05:31:56 -  - [ERRCODE: SC_ERR_NO_RULES(42)] - No rule 
files match the pattern /etc/suricata/rules/emerging-tftp.rules
10/4/2018 -- 05:31:56 -  - [ERRCODE: SC_ERR_NO_RULES(42)] - No rule 
files match the pattern /etc/suricata/rules/emerging-trojan.rules
10/4/2018 -- 05:31:56 -  - [ERRCODE: SC_ERR_NO_RULES(42)] - No rule 
files match the pattern /etc/suricata/rules/emerging-user_agents.rules
10/4/2018 -- 05:31:56 -  - [ERRCODE: SC_ERR_NO_RULES(42)] - No rule 
files match the pattern /etc/suricata/rules/emerging-voip.rules
10/4/2018 -- 05:31:56 -  - [ERRCODE: SC_ERR_NO_RULES(42)] - No rule 
files match the pattern 

Bug#857970: marked as done (mldemos FTBFS on armel/armhf: error: 'glColor3f' was not declared in this scope)

[Debian Bug Tracking System]

Your message dated Tue, 10 Apr 2018 05:27:29 +
with message-id 
and subject line Bug#857970: fixed in mldemos 0.5.1+git.1.ee5d11f-3
has caused the Debian Bug report #857970,
regarding mldemos FTBFS on armel/armhf: error: 'glColor3f' was not declared in 
this scope
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.)


-- 
857970: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=857970
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: mldemos
Version: 0.5.1+git.1.ee5d11f-1
Severity: serious

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

...
g++ -c -pipe -Wno-all -Wno-unused-variable -Wno-unused-parameter -Wtrigraphs 
-Wreturn-type -Wnon-virtual-dtor -Wunused-value -Wunknown-pragmas -Wno-shadow 
-g -O2 -fdebug-prefix-map=/«BUILDDIR»/mldemos-0.5.1+git.1.ee5d11f=. 
-fstack-protector-strong -Wformat -Werror=format-security -Wdate-time 
-D_FORTIFY_SOURCE=2 -fPIC -D_REENTRANT -DOPENCV22 -DWITHBOOST -DQT_NO_DEBUG 
-DQT_SVG_LIB -DQT_OPENGL_LIB -DQT_WIDGETS_LIB -DQT_GUI_LIB -DQT_CORE_LIB -I. 
-I. -I../Core -I../MLDemos -I../_3rdParty -isystem /usr/include/opencv -isystem 
/usr/include/arm-linux-gnueabi/qt5 -isystem 
/usr/include/arm-linux-gnueabi/qt5/QtSvg -isystem 
/usr/include/arm-linux-gnueabi/qt5/QtOpenGL -isystem 
/usr/include/arm-linux-gnueabi/qt5/QtWidgets -isystem 
/usr/include/arm-linux-gnueabi/qt5/QtGui -isystem 
/usr/include/arm-linux-gnueabi/qt5/QtCore -Ibuild -Ibuild 
-I/usr/lib/arm-linux-gnueabi/qt5/mkspecs/linux-g++ -o build/canvas.o canvas.cpp
In file included from drawUtils.h:29:0,
 from canvas.cpp:34:
glwidget.h: In static member function 'static void GLWidget::glSample(fvec, 
QColor, int, int, int)':
glwidget.h:41:50: error: 'glColor3f' was not declared in this scope
 glColor3f(c.redF(), c.greenF(), c.blueF());
  ^
glwidget.h:46:28: error: 'glVertex3f' was not declared in this scope
 glVertex3f(sX,sY,sZ);
^
glwidget.h: In static member function 'static void GLWidget::glLine(fvec, fvec, 
int, int, int)':
glwidget.h:51:74: error: 'glVertex3f' was not declared in this scope
 glVertex3f(p1[xIndex], p1[yIndex], zIndex >= 0 ? p1[zIndex] : 0.f);
  ^
Makefile:548: recipe for target 'build/canvas.o' failed
make[2]: *** [build/canvas.o] Error 1


This is likely related to Qt in Debian using OpenGL ES instead of OpenGL
on armel and armhf.
--- End Message ---
--- Begin Message ---
Source: mldemos
Source-Version: 0.5.1+git.1.ee5d11f-3

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

Debian distribution maintenance software
pp.
Barak A. Pearlmutter  (supplier of updated mldemos package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Mon, 09 Apr 2018 17:55:38 +0100
Source: mldemos
Binary: mldemos
Architecture: source amd64
Version: 0.5.1+git.1.ee5d11f-3
Distribution: unstable
Urgency: medium
Maintainer: Barak A. Pearlmutter 
Changed-By: Barak A. Pearlmutter 
Description:
 mldemos- Machine Learning Demos (MLDemos) with Visualization
Closes: 857970
Changes:
 mldemos (0.5.1+git.1.ee5d11f-3) unstable; urgency=medium
 .
   * fix for OpenGL ES platforms---I'm looking at you ARM---which doesnt'
 support glColor3f (closes: #857970)
Checksums-Sha1:
 eaaa897cb72bca2230a1ab634ab1bbeb81a66d64 1994 mldemos_0.5.1+git.1.ee5d11f-3.dsc
 59560d12fffbea856ec93ce07ef4ace14bfd3d28 16064 
mldemos_0.5.1+git.1.ee5d11f-3.debian.tar.xz
 36e129488e5799fc2f9859f14fa9a124326d121b 98781036 
mldemos-dbgsym_0.5.1+git.1.ee5d11f-3_amd64.deb
 c5c8099938de4546443b2885b1c983048ab4519b 20028 
mldemos_0.5.1+git.1.ee5d11f-3_amd64.buildinfo
 0e86d12c4555626741a81e6157db84bdc7f4bb9d 3304680 
mldemos_0.5.1+git.1.ee5d11f-3_amd64.deb
Checksums-Sha256:
 201d66915d105cfdf0cd2210fa9a48e89821c6fb7ae628424c160ffcb506e677 1994 
mldemos_0.5.1+git.1.ee5d11f-3.dsc
 

Bug#893205: marked as done (jericho-html FTBFS with openjdk-9)

[Debian Bug Tracking System]

Your message dated Tue, 10 Apr 2018 05:15:49 +
with message-id 
and subject line Bug#893205: fixed in jericho-html 3.2-2
has caused the Debian Bug report #893205,
regarding jericho-html FTBFS with openjdk-9
to be marked as done.

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

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


-- 
893205: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=893205
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: jericho-html
Version: 3.2-1
Severity: serious

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

...
build:
[mkdir] Created dir: /build/1st/jericho-html-3.2/build
[javac] /build/1st/jericho-html-3.2/debian/build.xml:9: warning: 
'includeantruntime' was not set, defaulting to build.sysclasspath=last; set to 
false for repeatable builds
[javac] Compiling 104 source files to /build/1st/jericho-html-3.2/build
[javac] Using ant.build.javac.target 1.5 is no longer supported, switching 
to 1.6
[javac] Using ant.build.javac.target 1.5 is no longer supported, switching 
to 1.6
[javac] Using ant.build.javac.source 1.5 is no longer supported, switching 
to 1.6
[javac] warning: [options] bootstrap class path not set in conjunction with 
-source 1.6
[javac] warning: [options] source value 1.6 is obsolete and will be removed 
in a future release
[javac] warning: [options] target value 1.6 is obsolete and will be removed 
in a future release
[javac] warning: [options] To suppress warnings about obsolete options, use 
-Xlint:-options.
[javac] 
/build/1st/jericho-html-3.2/src/java/net/htmlparser/jericho/Renderer.java:372: 
error: unmappable character (0xAB) for encoding US-ASCII
[javac]  *return '?'+alt+'?';
[javac]   ^
[javac] 
/build/1st/jericho-html-3.2/src/java/net/htmlparser/jericho/Renderer.java:372: 
error: unmappable character (0xBB) for encoding US-ASCII
[javac]  *return '?'+alt+'?';
[javac]   ^
[javac] 
/build/1st/jericho-html-3.2/src/java/net/htmlparser/jericho/StreamEncodingDetector.java:238:
 error: unmappable character (0xA7) for encoding US-ASCII
[javac] if (b2==0x6F && b3==0xA7 && b4==0x94) return 
setEncoding(EBCDIC,"default EBCDIC encoding ( detected)",0,false); // 
first four bytes are " detected)",0,false); // 
first four bytes are " detected)",0,false); 
// first four bytes are " detected)",0,false); 
// first four bytes are "--- End Message ---
--- Begin Message ---
Source: jericho-html
Source-Version: 3.2-2

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

Debian distribution maintenance software
pp.
Emmanuel Bourg  (supplier of updated jericho-html package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Tue, 10 Apr 2018 01:42:12 +0200
Source: jericho-html
Binary: libjericho-html-java
Architecture: source
Version: 3.2-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Java Maintainers 

Changed-By: Emmanuel Bourg 
Description:
 libjericho-html-java - Java based library for HTML Parsing
Closes: 893205
Changes:
 jericho-html (3.2-2) unstable; urgency=medium
 .
   * Team upload.
   * Fixed the build failure with Java 9 (Closes: #893205)
   * Standards-Version updated to 4.1.4
   * Switch to debhelper level 11
Checksums-Sha1:
 82efc7d92da757270cd61bebc7d8468d081fa9c3 2122 jericho-html_3.2-2.dsc
 cd3c838bda6d462510a19232c5d18b9654f8ba04 4380 jericho-html_3.2-2.debian.tar.xz
 023585772332c193b9b7872c445358bb039571a9 11095 
jericho-html_3.2-2_source.buildinfo
Checksums-Sha256:
 72e32b261a4bef72e5209973804539ec12c931c2a6e3e671dfb6fd2bc28d916b 2122 
jericho-html_3.2-2.dsc
 473cf4c35349b07c5b65df1db2951bb487ded57093e7af502c1c70d96bf05cfd 4380 
jericho-html_3.2-2.debian.tar.xz
 b12ed6d3f82fe449f6e2f85e473fd2c7ec9eb86a75ec615b4e13d33cd5a2e69b 11095 

Bug#895339: libbpp-phyl: FTBFS: Could not find compatible version of bpp-seq

[Daniel Schepler]

Source: libbpp-phyl
Version: 2.3.2-2
Severity: serious

>From my pbuilder build log:

...
 debian/rules build
dh build
   dh_update_autotools_config
   dh_autoreconf
   dh_auto_configure
cd obj-x86_64-linux-gnu && cmake .. -DCMAKE_INSTALL_PREFIX=/usr
-DCMAKE_VERBOSE_MAKEFILE=ON -DCMAKE_BUILD_TYPE=None
-DCMAKE_INSTALL_SYSCONFDIR=/etc -DCMAKE_INSTALL_LOCALSTATEDIR=/var
-DCMAKE_EXPORT_NO_PACKAGE_REGISTRY=ON
-DCMAKE_FIND_PACKAGE_NO_PACKAGE_REGISTRY=ON
-DCMAKE_INSTALL_RUNSTATEDIR=/run "-GUnix Makefiles"
-- The CXX compiler identification is GNU 7.3.0
-- Check for working CXX compiler: /usr/bin/c++
-- Check for working CXX compiler: /usr/bin/c++ -- works
-- Detecting CXX compiler ABI info
-- Detecting CXX compiler ABI info - done
-- Detecting CXX compile features
-- Detecting CXX compile features - done
CMake Error at CMakeLists.txt:56 (find_package):
  Could not find a configuration file for package "bpp-seq" that is
  compatible with requested version "11.0.0".

  The following configuration files were considered but not accepted:

/usr/lib/x86_64-linux-gnu/cmake/bpp-seq/bpp-seq-config.cmake,
version: 12.0.0



-- Configuring incomplete, errors occurred!
See also 
"/build/libbpp-phyl-2.3.2/obj-x86_64-linux-gnu/CMakeFiles/CMakeOutput.log".
cd obj-x86_64-linux-gnu && tail -v -n \+0 CMakeCache.txt
...
dh_auto_configure: cd obj-x86_64-linux-gnu && cmake ..
-DCMAKE_INSTALL_PREFIX=/usr -DCMAKE_VERBOSE_MAKEFILE=ON
-DCMAKE_BUILD_TYPE=None -DCMAKE_INSTALL_SYSCONFDIR=/etc
-DCMAKE_INSTALL_LOCALSTATEDIR=/var
-DCMAKE_EXPORT_NO_PACKAGE_REGISTRY=ON
-DCMAKE_FIND_PACKAGE_NO_PACKAGE_REGISTRY=ON
-DCMAKE_INSTALL_RUNSTATEDIR=/run "-GUnix Makefiles" returned exit code
1
make: *** [debian/rules:8: build] Error 2
dpkg-buildpackage: error: debian/rules build subprocess returned exit status 2
-- 
Daniel Schepler

Bug#784612: marked as done ([anki] Qt4's WebKit removal)

[Debian Bug Tracking System]

Your message dated Tue, 10 Apr 2018 10:21:59 +0800
with message-id <0f8126c0-5a02-1316-ece9-fcacb1bcd...@rolf.leggewie.biz>
and subject line this is fixed with anki 2.1 being ported to Qt5
has caused the Debian Bug report #784612,
regarding [anki] Qt4's WebKit removal
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.)


-- 
784612: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=784612
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: anki
Severity: wishlist
User: debian-qt-...@lists.debian.org
Usertags: qt4webkit-removal
Control: block 784513 by -1

Hi! As you might know we the Qt/KDE team are preparing to remove Qt4's WebKit
as announced in [announce]. Your package seems to be using it via PyQt4's
QtWebKit module.

[announce] 


Basically we are about to get the last Qt4 point release and upstream is
migrating from WebKit to Blink in the Qt5 series, so we won't have much upstream
support for maintaining Qt4's WebKit (Qt5's WebKit is expected to stay supported
until Qt6).

In order to make this move, all packages directly or indirectly depending on
the Qt4's WebKit library have to either get ported to Qt5 or eventually get
removed from the Debian repositories.

Therefore, please take the time and:
- contact your upstream (if existing) and ask about the state of a Qt5 
  port of your application
- if there are no activities regarding porting, investigate whether there are 
  suitable alternatives for your users
- if there is a Qt5/PyQt5 port that is not yet packaged, consider packaging it
- if both the Qt4 and the Qt5 versions already coexist in the Debian 
  archives, consider removing the Qt4 version

= Porting =

Some of us where involved in various Qt4 to Qt5 migrations [migration] and we
know for sure that porting stuff from Qt4 to Qt5 is much much easier and less
painful than it was from Qt3 to Qt4.

We also understand that there is still a lot of software still using Qt4. In
order to ease the transition time we have provided Wheezy backports for Qt5.

Don't forget to take a look at the C++ API changes page [apichanges] and the
PyQt4 vs PyQt5 differences page [pyqtchanges] whenever you start porting
your application.

[migration] http://pkg-kde.alioth.debian.org/packagingqtstuff.html
[apichanges] http://doc.qt.io/qt-5/sourcebreaks.html
[pyqtchanges] http://pyqt.sourceforge.net/Docs/PyQt5/pyqt4_differences.html

For any questions and issues, do not hesitate to contact the Debian Qt/KDE 
team at debian-qt-...@lists.debian.org.

--
Dmitry Shachnev,
on behalf of the Qt4 and PyQt4 maintainers
--- End Message ---
--- Begin Message ---
This is no longer an issue End Message ---

Bug#886082: marked as done (foxtrotgps: Depends on gconf)

[Debian Bug Tracking System]

Your message dated Tue, 10 Apr 2018 03:21:15 +
with message-id 
and subject line Bug#886082: fixed in foxtrotgps 1.2.1-1
has caused the Debian Bug report #886082,
regarding foxtrotgps: Depends on gconf
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.)


-- 
886082: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=886082
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: foxtrotgps
Version: 1.2.0-1
Severity: important
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
--- End Message ---
--- Begin Message ---
Source: foxtrotgps
Source-Version: 1.2.1-1

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

Debian distribution maintenance software
pp.
Paul Wise  (supplier of updated foxtrotgps package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Tue, 10 Apr 2018 10:39:03 +0800
Source: foxtrotgps
Binary: foxtrotgps
Architecture: source
Version: 1.2.1-1
Distribution: unstable
Urgency: medium
Maintainer: Paul Wise 
Changed-By: Paul Wise 
Description:
 foxtrotgps - GTK+ mapping and GPS application
Closes: 866393 886082
Changes:
 foxtrotgps (1.2.1-1) unstable; urgency=medium
 .
   * New upstream release
 - Switches from GConf to GSettings (Closes: #886082)
 - Fixes info documentation (Closes: #866393)
 - Uses Python 3 instead of Python 2, deps updated
   * Use https in various links
   * Use pgpmode=auto in watch file
   * Use new and more secure upstream OpenPGP signing key
   * Also remove screenshot eps files to ensure they get rebuilt
   * Drop -dbg package in favour of automatic -dbgsym package
   * Drop obsolete Debian menu in favour of freedesktop menu
   * Add missing suggests for Python scripts
   * Declare compliance with Policy 4.1.4
   * Bump debhelper compat to 11
Checksums-Sha1:
 b3e1c2e787acc68896b96c85091d375ceaed3bbe 2209 foxtrotgps_1.2.1-1.dsc
 d0a37b43471fbe00ef847f76ee6d2f3c556b6b5d 1690644 foxtrotgps_1.2.1.orig.tar.xz
 74b4073871aa8c160008b58e8f750fd0f506d2d0 866 foxtrotgps_1.2.1.orig.tar.xz.asc
 144bf36d1717b5b5a643d33392a9a0ac30d707fe 17052 foxtrotgps_1.2.1-1.debian.tar.xz
Checksums-Sha256:
 7533476ad229be853d1755adcaf8545904ee727442e0913eb5f7df172319ac12 2209 
foxtrotgps_1.2.1-1.dsc
 3b3e95b0cb352e5003f69df503c553780fb809879b83c6c5a90a53f050a0da25 1690644 
foxtrotgps_1.2.1.orig.tar.xz
 ae071bccf9dfca9e2cdbcc470479b4d0390c5b67e3b365bb4058c330bf08ab48 866 
foxtrotgps_1.2.1.orig.tar.xz.asc
 9b808ef538c2aba52c73345142a9fe59a0d2529e13e4f3755912a531ceee5f31 17052 
foxtrotgps_1.2.1-1.debian.tar.xz
Files:
 cba4c045fd07ca8656dfde6257562704 2209 comm optional foxtrotgps_1.2.1-1.dsc
 b4042572edbbad13db6bc90eb9a7f11b 1690644 comm optional 
foxtrotgps_1.2.1.orig.tar.xz
 3de667652af85b4821b53df00a4c6dad 866 comm optional 
foxtrotgps_1.2.1.orig.tar.xz.asc
 0c333fbd98b5ae2dc607ca2bfdfadbfe 17052 comm optional 
foxtrotgps_1.2.1-1.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEYQsotVz8/kXqG1Y7MRa6Xp/6aaMFAlrMJzwACgkQMRa6Xp/6
aaPhkg/+OQZ/UvP1JS5v+6+0Ezqw0kWn+mM79rVZJTNZ2lbioUXm/WcD3uwb9Bmg
WFJY6hyuT6/a6HYBmFLDyj7FR7qvCU8OQCoUJVvRQouQwCLWG1XF4q4WaYFEtKXa
gWuqJ12LNO0bkNI8e+AeqOxjaHYpBZ/FBvRrIa9BylntFLr6ZZ9uz8Vu2r7CLVO0
BE9sF57XFTo3ZrbHVBZyLHZHVKGgEEIU8WxAN4eS3LFtH5HOI8PbsUCzzZfSxM23
ZqedT/frCIS57P9jbgq/nPFI/JBN1NheYs0sSi14F2Tn5HnHidLLkeVdLOAF4SmX
woDlezzIIvnp7vvmQwfv3rCylITiKCk89eSiVweBmbdIv8kwO8q1TpPYUXLzsM+L
0FDCkigHZ4j0fdHZoddu6jqX5Z8tX788pD8dvL7IqhHosCTxuGWmxcI+jXmqeSc2
Q5ijWU9iroU1DSEc4OM63uAbauJjTx49siXQ3gvgqb6JfBJif6cMQfwN9wnk+9jQ

Processed: limit source to foxtrotgps, tagging 866393, tagging 886082

[Debian Bug Tracking System]

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

> limit source foxtrotgps
Limiting to bugs with field 'source' containing at least one of 'foxtrotgps'
Limit currently set to 'source':'foxtrotgps'

> tags 866393 + pending
Bug #866393 [foxtrotgps] foxtrotgps: Missing info directory entry
Added tag(s) pending.
> tags 886082 + pending
Bug #886082 [src:foxtrotgps] foxtrotgps: Depends on gconf
Added tag(s) pending.
> thanks
Stopping processing here.

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

Bug#895326: marked as done (jenkins.debian.org: All armhf nodes are missing ssh port configuration)

[Debian Bug Tracking System]

Your message dated Tue, 10 Apr 2018 03:08:34 +0200
with message-id <20180410010834.gb17...@mapreri.org>
and subject line Re: [Qa-jenkins-dev] Bug#895326: jenkins.debian.org: All armhf 
nodes are missing ssh port configuration
has caused the Debian Bug report #895326,
regarding jenkins.debian.org: All armhf nodes are missing ssh port configuration
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.)


-- 
895326: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=895326
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: jenkins.debian.org
Severity: serious

As of commit bb559740baac88dc98f9f41176cd1fbecda3faf4:

  
https://anonscm.debian.org/git/qa/jenkins.debian.net.git/commit/hosts/common/etc/ssh/sshd_config?id=bb559740baac88dc98f9f41176cd1fbecda3faf4

All the armhf nodes no longer have the correct ssh port configuration,
as each node has a specific port that needs configuration in sshd_config
to be used.

I've added the correct port back into all of the currently running
nodes, but haven't figured out how to do this from jdn_update.sh.


I noticed this because several machines recently rebooted were not
responding on the correct ssh port...

The other machines were only still working because ssh had not been
restarted. At least it was only a couple machines and caught before it
became a bigger problem!


live well,
  vagrant


signature.asc
Description: PGP signature
--- End Message ---
--- Begin Message ---
On Mon, Apr 09, 2018 at 03:31:44PM -0700, Vagrant Cascadian wrote:
> As of commit bb559740baac88dc98f9f41176cd1fbecda3faf4:
> 
>   
> https://anonscm.debian.org/git/qa/jenkins.debian.net.git/commit/hosts/common/etc/ssh/sshd_config?id=bb559740baac88dc98f9f41176cd1fbecda3faf4
> 
> All the armhf nodes no longer have the correct ssh port configuration,
> as each node has a specific port that needs configuration in sshd_config
> to be used.

Oh, I didn't know of that detail!!!

> I've added the correct port back into all of the currently running
> nodes, but haven't figured out how to do this from jdn_update.sh.

I've done it now:
https://anonscm.debian.org/git/qa/jenkins.debian.net.git/commit/?id=d937951
https://anonscm.debian.org/git/qa/jenkins.debian.net.git/commit/?id=8b1c4fd

> I noticed this because several machines recently rebooted were not
> responding on the correct ssh port...

Indeed, I had noticed a machine suddenly not responding to ssh, but
looking very fine over console earlier today, but couldn't look further.

> The other machines were only still working because ssh had not been
> restarted. At least it was only a couple machines and caught before it
> became a bigger problem!

Indeed, thank you for noticing and debugging the issue!!

-- 
regards,
Mattia Rizzolo

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


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

Bug#895334: libsundials-nvecparallel-petsc2: uninstallable on current unstable

[Mike Miller]

Package: libsundials-nvecparallel-petsc2
Version: 2.7.0+dfsg-2+b2
Severity: grave
Justification: renders package unusable

Dear Maintainer,

Since petsc was updated in unstable from 3.7 to 3.8, the
libsundials-nvecparallel-petsc2 package is uninstallable in unstable. It
depends on libpetsc3.7, which no longer exists in the archive.

This is probably easily fixed with a binNMU.

Thanks.

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

Kernel: Linux 4.15.0-2-amd64 (SMP w/8 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 /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages libsundials-nvecparallel-petsc2 depends on:
ii  libc62.27-2
ii  libopenmpi2  2.1.1-8
ii  libpetsc3.7.7 [libpetsc3.7]  3.7.7+dfsg1-2+b3

libsundials-nvecparallel-petsc2 recommends no packages.

libsundials-nvecparallel-petsc2 suggests no packages.

-- no debconf information

Bug#895332: flightgear: no flightgear package present in Buster repo

[Pavel Kreuzt]

Package: flightgear
Severity: grave
Justification: renders package unusable

There is no binary package for flightgear, althought there are packages for
its data parts, which are unusable without the main program.

Bug#893205: Pending fixes for bugs in the jericho-html package

[pkg-java-maintainers]

tag 893205 + pending
thanks

Some bugs in the jericho-html package are closed in revision
32a397d0222556ac88263702fe3d1053a7ee1e76 in branch 'master' by
Emmanuel Bourg

The full diff can be seen at
https://anonscm.debian.org/cgit/pkg-java/jericho-html.git/commit/?id=32a397d

Commit message:

Fixed the build failure with Java 9 (Closes: #893205)

Processed: Pending fixes for bugs in the jericho-html package

[Debian Bug Tracking System]

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

> tag 893205 + pending
Bug #893205 [src:jericho-html] jericho-html FTBFS with openjdk-9
Added tag(s) pending.
> thanks
Stopping processing here.

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

Processed: Re: libsvm FTBFS with openjdk-9

[Debian Bug Tracking System]

Processing control commands:

> tags -1 + patch
Bug #893291 [src:libsvm] libsvm FTBFS with openjdk-9
Added tag(s) patch.

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

Bug#893291: libsvm FTBFS with openjdk-9

[Emmanuel Bourg]

Control: tags -1 + patch

Here is a patch fixing this issue.
--- a/java/Makefile
+++ b/java/Makefile
@@ -5,7 +5,7 @@
svm_train.class svm_predict.class svm_toy.class svm_scale.class
 
 #JAVAC = jikes
-JAVAC_FLAGS = -target 1.5 -source 1.5
+JAVAC_FLAGS = -target 1.8 -source 1.8
 JAVAC = javac
 # JAVAC_FLAGS =
 

Bug#871692: [pkg-go] Bug#871692: gobgp FTBFS on arm64: Test killed with quit: ran too long (10m0s).

[Steve Langasek]

I can confirm this bug also affects arm64 in Ubuntu, and I have further
confirmed that the kernels there definitely have TCP_MD5SIG enabled.

-- 
Steve Langasek   Give me a lever long enough and a Free OS
Debian Developer   to set it on, and I can move the world.
Ubuntu Developerhttp://www.debian.org/
slanga...@ubuntu.com vor...@debian.org


signature.asc
Description: PGP signature

Bug#895326: jenkins.debian.org: All armhf nodes are missing ssh port configuration

[Vagrant Cascadian]

Package: jenkins.debian.org
Severity: serious

As of commit bb559740baac88dc98f9f41176cd1fbecda3faf4:

  
https://anonscm.debian.org/git/qa/jenkins.debian.net.git/commit/hosts/common/etc/ssh/sshd_config?id=bb559740baac88dc98f9f41176cd1fbecda3faf4

All the armhf nodes no longer have the correct ssh port configuration,
as each node has a specific port that needs configuration in sshd_config
to be used.

I've added the correct port back into all of the currently running
nodes, but haven't figured out how to do this from jdn_update.sh.


I noticed this because several machines recently rebooted were not
responding on the correct ssh port...

The other machines were only still working because ssh had not been
restarted. At least it was only a couple machines and caught before it
became a bigger problem!


live well,
  vagrant


signature.asc
Description: PGP signature

Bug#895162: marked as done (synfigstudio: Update fonts-freefont build-depends)

[Debian Bug Tracking System]

Your message dated Mon, 09 Apr 2018 22:11:14 +
with message-id 
and subject line Bug#895162: fixed in synfigstudio 1.2.1-0.1
has caused the Debian Bug report #895162,
regarding synfigstudio: Update fonts-freefont build-depends
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.)


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

fonts-freefont-ttf (or fonts-freefont-otf) has replaced ttf-freefont.
Please update synfigstudio's Build-Depends.

Thanks,
Jeremy Bicha
--- End Message ---
--- Begin Message ---
Source: synfigstudio
Source-Version: 1.2.1-0.1

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

Debian distribution maintenance software
pp.
Matthias Klose  (supplier of updated synfigstudio package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Mon, 09 Apr 2018 21:14:59 +0200
Source: synfigstudio
Binary: synfigstudio synfigstudio-dbg
Architecture: source
Version: 1.2.1-0.1
Distribution: unstable
Urgency: medium
Maintainer: Debian Multimedia Maintainers 

Changed-By: Matthias Klose 
Description:
 synfigstudio - vector-based 2D animation package (graphical user interface)
 synfigstudio-dbg - synfig GUI debugging symbols
Closes: 883594 895162
Changes:
 synfigstudio (1.2.1-0.1) unstable; urgency=medium
 .
   * Non-maintainer upload.
   * New upstream version. Closes: #883594.
   * Update build dependency on font packages. Closes: #895162.
   * Build-depend on pkg-config and libfftw3-dev.
Checksums-Sha1:
 39feda3ccd10dcb724d9f7655adfa815478d7e7a 2399 synfigstudio_1.2.1-0.1.dsc
 9443e434dced6467a08ac096e2f43369c2a7561f 5687045 synfigstudio_1.2.1.orig.tar.gz
 45f5b76848559ba723a63d6014cd89856155aa35 16888 
synfigstudio_1.2.1-0.1.debian.tar.xz
 6c3b8c6d9c5bb94e21606a45c2d1204340956f08 20567 
synfigstudio_1.2.1-0.1_source.buildinfo
Checksums-Sha256:
 1efa17944c78ecd9ee3caec17265d4cb351acb95ed398312018c5cb82f7eba8b 2399 
synfigstudio_1.2.1-0.1.dsc
 1a97875e0039895604085649bcd30cf0d6165f4c865299ca13d45d2dfbfab05d 5687045 
synfigstudio_1.2.1.orig.tar.gz
 7388aa1b028c6a193b3fca0b1b1d469ab761b71659d2e1ebcd1907432b00582a 16888 
synfigstudio_1.2.1-0.1.debian.tar.xz
 80b522cd80a732a480764d823f2a8af2b0ebe3aab1c28c2af944064ce7932f97 20567 
synfigstudio_1.2.1-0.1_source.buildinfo
Files:
 31f4c5a6b475a911f1924b809b17a91f 2399 graphics extra synfigstudio_1.2.1-0.1.dsc
 71a2c31b82b031eae93d9431fb88c13f 5687045 graphics extra 
synfigstudio_1.2.1.orig.tar.gz
 b43ac341ce4a1391717beb8a1d599dae 16888 graphics extra 
synfigstudio_1.2.1-0.1.debian.tar.xz
 1d029de7d79211f927020cc8f47293df 20567 graphics extra 
synfigstudio_1.2.1-0.1_source.buildinfo

-BEGIN PGP SIGNATURE-

iQJEBAEBCAAuFiEE1WVxuIqLuvFAv2PWvX6qYHePpvUFAlrLvAoQHGRva29AZGVi
aWFuLm9yZwAKCRC9fqpgd4+m9XA8D/sHETW6oAqYV1CrKg6qXARLYAywWHwp1o9Y
b4qDWB9P3t6/Ji2o6wYefofK9vFn1l3px+loqkHGy0DLEyu9nfeWc/rG+88AV0G/
5c3+F8hqHzVyhujgReaeGM/K+AIvduc+nrZ5NqTCX9LC5Ly/ZsvaQIe4h9plyPzV
u3AmMPiJjAujEsC23GpSFSVNjTimgRFLMmyD2GXAHjFUeyMVa6fe8bDF0l1LFqxC
cmNQe8ERG8OMZ71zIFGHU/PG4IhLG7OQyNE2FZToDMO7lWALfdaXM/9Vlc+/szC5
uvHm93tL9KsPZ81R1LoANcCtePQEiNylo+lGIBrVcIifAqgmKSxBAv9Vr3MVrL86
+tfSDQq0QH4zu4T1GodxzL5KvBv+iNBItYXdkNpqsP3fq8+VyX0TfvbgRGJIWLRM
kqC8ww+FOisXM/WtJUPe/q3RaNNlVX2PxTjTmqujEA4Za/Ilvz92YwvuEglPmOPO
pxP328/ybiGPu+rDYI61NhVyuHvT+Wq3XF9aDGSs8P7EQGgX//vzKX5w2wKL3lTT
l+MovRicDz83BvU4UMjYtKRmmCSYxD+QIrXzKeP6jCrmjIYx3TWp022e634fcYMb
CiHU7xAMyozyGJklMbH+7g9PTIWeD7/tTzxlkoFcgYcY2sKnRIXud7MEx0+/N+/0
+X3gBuxuHA==
=qeLg
-END PGP SIGNATURE End Message ---

Bug#893577: marked as done (sbuild-debian-developer-setup: Should not rely on files in /usr/share/doc)

[Debian Bug Tracking System]

Your message dated Mon, 09 Apr 2018 22:09:50 +
with message-id 
and subject line Bug#893577: fixed in sbuild 0.76.0-1
has caused the Debian Bug report #893577,
regarding sbuild-debian-developer-setup: Should not rely on files in 
/usr/share/doc
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.)


-- 
893577: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=893577
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: sbuild-debian-developer-setup
Version: 0.74.0-1
Severity: serious
Justification: Policy 12.3 Packages must not require the existence of any files 
in /usr/share/doc/ in order to function.

Dear Maintainer,

Thanks for adding sbuild-debian-developer-setup - it indeed looks like a good
way of a new user getting started with sbuild.

At the end of the script, it runs

symlink("/usr/share/doc/sbuild/examples/sbuild-update-all", 
"/etc/cron.daily/sbuild-debian-developer-setup-update-all");

which requires the file in /usr/share/doc to be present. Policy 12.3 says that
packages can't do that and says that such files should be in /usr/share/package
with a symlink into /usr/share/doc/package/ as appropriate.

regards
Stuart
--- End Message ---
--- Begin Message ---
Source: sbuild
Source-Version: 0.76.0-1

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

Debian distribution maintenance software
pp.
Michael Stapelberg  (supplier of updated sbuild package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Mon, 09 Apr 2018 18:58:38 +0200
Source: sbuild
Binary: libsbuild-perl sbuild sbuild-debian-developer-setup buildd
Architecture: source
Version: 0.76.0-1
Distribution: unstable
Urgency: medium
Maintainer: Debian buildd-tools Developers 

Changed-By: Michael Stapelberg 
Description:
 buildd - Daemon for automatically building Debian binary packages from Deb
 libsbuild-perl - Library for building Debian binary packages from Debian 
sources
 sbuild - Tool for building Debian binary packages from Debian sources
 sbuild-debian-developer-setup - Convenience script to set up an sbuild 
environment for Debian Dev
Closes: 893577
Changes:
 sbuild (0.76.0-1) unstable; urgency=medium
 .
   * Install sbuild-debian-developer-setup-update-all cronjob (closes: #893577)
Checksums-Sha1:
 d40927d69a27b7eafa446e9c0b891d06d91ead0a 2489 sbuild_0.76.0-1.dsc
 f06ee98f1f1cc39cce429f97a16336b1dbba00b3 195312 sbuild_0.76.0.orig.tar.xz
 4faecfbbf686155189d5a1d55e3b947267e19996 49528 sbuild_0.76.0-1.debian.tar.xz
 61056e9d8f52f87d7936f0ba66be4321f27c9c1d 6683 sbuild_0.76.0-1_amd64.buildinfo
Checksums-Sha256:
 a13ea74906a96c7f78fbddbafac60946d795d6b1362d484a64744de831b66f33 2489 
sbuild_0.76.0-1.dsc
 95eeedea446bf04814034992656114746af17d06a1f374f473487a447ded1e42 195312 
sbuild_0.76.0.orig.tar.xz
 570d19f66565f36a5de2a44aa0a91233b4154e3d051a8bdf6e967ac51d3667e2 49528 
sbuild_0.76.0-1.debian.tar.xz
 b4a69af003db1774bdf6a2bfada1b1186c409e150b96a08f8e6120680955c29a 6683 
sbuild_0.76.0-1_amd64.buildinfo
Files:
 df2ebd4e5e221b1ab83b5b210a5cb7c8 2489 devel extra sbuild_0.76.0-1.dsc
 996fd1c6f9d2259879141e84996af189 195312 devel extra sbuild_0.76.0.orig.tar.xz
 6772fa0d785dc01f52f6d33c0d814e71 49528 devel extra 
sbuild_0.76.0-1.debian.tar.xz
 48c42e759307a5511ad67ab3eba865d3 6683 devel extra 
sbuild_0.76.0-1_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEQk4U1wPnxtQ9nW82TnFg7UrI7h0FAlrLnc4ACgkQTnFg7UrI
7h3ydxAAuWxRd9t8aDZ6NJb0cRXwE0TNdcFK5u249UVlBkDu+y+7aRQF3mmOIAav
y+VSFJEeEZMS42YFTW+iPanZqK4RpNKiOiFFu/ufBq2Wmacco9TRoQ1coGhNZv5g
jCXkWu6I3qW294wjTUvdId64VxlRBs7wBKOsQ42sJYcVYEgV84Qy13ZOAvPfgOFI
5xEkfI8vy97rM3AnNSp2Hg96yHKg6p3jM9EabOm8WGGfryDdWcOBeSDROmyQKB/p
Whr8eN5Cpnu5pJOS0j6VWZgvGe3PQ4tFdTy9gQTvDZeFzlHjpLQ0lO5C4JnSIdTk
DgdD0UVozp2U4cJcUmoX1VxT7z1HxTufBty1jmdgbyYzwAPvNW1xOicxRaotlTND
6HpbXCw4DuJ5OJpUCILcV+ZcffL5S4T3XYYUOS9WcUJPnjziO0GGtZ+wG38dmiUz

Bug#863784: marked as done (policykit-1: Please drop dependency against mozjs 1.8.5)

[Debian Bug Tracking System]

Your message dated Mon, 09 Apr 2018 21:54:56 +
with message-id 
and subject line Bug#863784: fixed in policykit-1 0.114-1
has caused the Debian Bug report #863784,
regarding policykit-1: Please drop dependency against mozjs 1.8.5
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.)


-- 
863784: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=863784
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: policykit-1
Version: 0.113-2
Severity: normal
Tags: sid buster
User: pkg-gnome-maintain...@lists.alioth.debian.org
Usertags: oldlibs mozjs185

Dear maintainer,

Your package is depending against mozjs 1.8.5. This package is old
and currently orphaned.

Could you please remove this dependency or switch to a more recent
version of mozjs?

We should remove this version of mozjs from buster, I'm planning to
make this bug RC when the new development cycle is open.

Kind Regards,

Laurent Bigonville 
--- End Message ---
--- Begin Message ---
Source: policykit-1
Source-Version: 0.114-1

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

Debian distribution maintenance software
pp.
Michael Biebl  (supplier of updated policykit-1 package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Mon, 09 Apr 2018 22:31:58 +0200
Source: policykit-1
Binary: policykit-1 policykit-1-doc libpolkit-gobject-1-0 
libpolkit-gobject-1-dev libpolkit-agent-1-0 libpolkit-agent-1-dev 
gir1.2-polkit-1.0
Architecture: source
Version: 0.114-1
Distribution: experimental
Urgency: medium
Maintainer: Utopia Maintenance Team 

Changed-By: Michael Biebl 
Description:
 gir1.2-polkit-1.0 - GObject introspection data for PolicyKit
 libpolkit-agent-1-0 - PolicyKit Authentication Agent API
 libpolkit-agent-1-dev - PolicyKit Authentication Agent API - development files
 libpolkit-gobject-1-0 - PolicyKit Authorization API
 libpolkit-gobject-1-dev - PolicyKit Authorization API - development files
 policykit-1 - framework for managing administrative policies and privileges
 policykit-1-doc - documentation for PolicyKit-1
Closes: 863784
Changes:
 policykit-1 (0.114-1) experimental; urgency=medium
 .
   [ Michael Biebl ]
   * New upstream version 0.114
   * Rebase patches
   * Switch to mozjs 52 (Closes: #863784)
   * Drop -Wl,--no-as-needed, no longer necessary
   * jsauthority: pass "%s" format string to remaining report function
   * Add Provides to gir1.2-polkit-1.0 to reflect its contents
 .
   [ Martin Pitt ]
   * debian/copyright: Use https URL for Format:
   * Update Vcs-* links for move to salsa.debian.org.
   * Move to debhelper compat level 10.
 Remove explicit dh-autoreconf, it's now done by default.
   * Bump Standards-Version to 4.1.3
   * Add autopkgtest.
 This covers the pkaction and pkcheck CLI tools.
Checksums-Sha1:
 e37c0ed03aa447bc66f1c9ebd36f637685401f4a 2748 policykit-1_0.114-1.dsc
 f29deef0076e76588f209a028a3e33ef70c2d9cd 1557340 policykit-1_0.114.orig.tar.gz
 c3dc3db75a430ad683fc5a2072004349c66ce34b 17400 
policykit-1_0.114-1.debian.tar.xz
 629418fb335118cc75bcad0d5d5c6d9f38bf8401 9166 
policykit-1_0.114-1_source.buildinfo
Checksums-Sha256:
 c2c20ac9d8966c860ef7356c1af4cbf290a3614da3295b73d51d35363010f967 2748 
policykit-1_0.114-1.dsc
 bdf4007367d758fd794de2495975c115984d206267e52d1e6ac5ceea77e8ede6 1557340 
policykit-1_0.114.orig.tar.gz
 053dbcfb162d080603df2516a7d0b75cac9bbec8add301376b48b4b0235b1e13 17400 
policykit-1_0.114-1.debian.tar.xz
 85a77fe3ad46a6d9a0853b83ceda4f7e3ecfd56bddde484001739a757efdd006 9166 
policykit-1_0.114-1_source.buildinfo
Files:
 a44fd175da873fb811817bbeb9c00a7d 2748 admin optional policykit-1_0.114-1.dsc
 93ff41874e7df8c62ed9e41893817f04 1557340 admin optional 
policykit-1_0.114.orig.tar.gz
 877479a516f395cc9e1d3f8b686659df 17400 admin optional 
policykit-1_0.114-1.debian.tar.xz
 599d33821d9c2bfb50234b3dafb42f8a 9166 admin optional 
policykit-1_0.114-1_source.buildinfo

-BEGIN PGP 

Bug#891025: marked as done (python-flask-login-doc: missing Breaks+Replaces: python3-flask-login-doc)

[Debian Bug Tracking System]

Your message dated Mon, 09 Apr 2018 21:19:29 +
with message-id 
and subject line Bug#891025: fixed in flask-login 0.4.1-1
has caused the Debian Bug report #891025,
regarding python-flask-login-doc: missing Breaks+Replaces: 
python3-flask-login-doc
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.)


-- 
891025: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=891025
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: python-flask-login-doc
Version: 0.4.0-2
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

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

See policy 7.6 at
https://www.debian.org/doc/debian-policy/#overwriting-files-and-replacing-packages-replaces

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

  Selecting previously unselected package python-flask-login-doc.
  Preparing to unpack .../python-flask-login-doc_0.4.0-2_all.deb ...
  Unpacking python-flask-login-doc (0.4.0-2) ...
  dpkg: error processing archive 
/var/cache/apt/archives/python-flask-login-doc_0.4.0-2_all.deb (--unpack):
   trying to overwrite '/usr/share/doc-base/flask-login', which is also in 
package python3-flask-login-doc 0.4.0-1
  Errors were encountered while processing:
   /var/cache/apt/archives/python-flask-login-doc_0.4.0-2_all.deb


cheers,

Andreas


python3-flask-login-doc=0.4.0-1_python-flask-login-doc=0.4.0-2.log.gz
Description: application/gzip
--- End Message ---
--- Begin Message ---
Source: flask-login
Source-Version: 0.4.1-1

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

Debian distribution maintenance software
pp.
Christoph Berg  (supplier of updated flask-login package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Mon, 09 Apr 2018 20:56:02 +0200
Source: flask-login
Binary: python3-flask-login python-flask-login-doc
Architecture: source
Version: 0.4.1-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Python Modules Team 

Changed-By: Christoph Berg 
Description:
 python-flask-login-doc - user session management for Flask -- documentation
 python3-flask-login - user session management for Flask -- Python 3 module
Closes: 889618 891025
Changes:
 flask-login (0.4.1-1) unstable; urgency=medium
 .
   * Team upload.
 .
   [ Ondřej Nový ]
   * d/control: Set Vcs-* to salsa.debian.org
 .
   [ Christoph Berg ]
   * New upstream version.
 + Remove 0002-allow-choice-of-nosetests-executable-in-run-tests.sh.patch.
   * Add python3-semantic-version test dependency.
   * Add missing docs/_themes copyright. (Closes: #889618)
   * python-flask-login-doc: Replaces: python3-flask-login-doc.
 (Closes: #891025)
Checksums-Sha1:
 543df6e82b2befb4a57602e5f404488113a3a9f9 2272 flask-login_0.4.1-1.dsc
 c4367bfc545b422d196d453c17831e2cbf7cbde1 43679 flask-login_0.4.1.orig.tar.gz
 8376f918901bea4024be89f4fa43a23b986d9dd3 5276 flask-login_0.4.1-1.debian.tar.xz
 f547cfdfb324de5fb29d1eaa5b7b84f6823a3ae9 6866 
flask-login_0.4.1-1_source.buildinfo
Checksums-Sha256:
 a7e9f54a5a99576ebbdaa0cc66760de866ef3ceabb9e0f8d3805033a69517d80 2272 
flask-login_0.4.1-1.dsc
 ed7facda15d0217ba02c2762b37711ad52144bbde401d6175109acd833d5e69f 43679 
flask-login_0.4.1.orig.tar.gz
 31297e975fd1928c810647d187593578433ba225719fb94af329cce652b3499a 5276 
flask-login_0.4.1-1.debian.tar.xz
 da97a6c05a677409504eee342efb82ddd10fb3c9bab78ebca649f76522ccd331 6866 
flask-login_0.4.1-1_source.buildinfo
Files:
 4cd391772eb20577e83a5a6405c98087 2272 python optional flask-login_0.4.1-1.dsc
 489905b7147d2dec9620892ec75bb397 43679 python optional 
flask-login_0.4.1.orig.tar.gz
 9518189b8c5183f1fd3eeead1da03f91 5276 python optional 
flask-login_0.4.1-1.debian.tar.xz
 78a46b6d90f2fdb5457c5eb2eabfd8eb 6866 python optional 

Bug#889618: marked as done (entry in debian/copyright missing)

[Debian Bug Tracking System]

Your message dated Mon, 09 Apr 2018 21:19:29 +
with message-id 
and subject line Bug#889618: fixed in flask-login 0.4.1-1
has caused the Debian Bug report #889618,
regarding entry in debian/copyright missing
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.)


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

Package: flask-login
Version: 0.4.0-2
Severity: serious
thanks

Hi

one of our trainees looked at your package and found that a whole 
directory in the source (docs/_themes) is copyrighted by Armin Ronacher 
and licensed with a 3-clause BSD license.

This whole information is missing from the copyright file.

Thanks!
  Thorsten
--- End Message ---
--- Begin Message ---
Source: flask-login
Source-Version: 0.4.1-1

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

Debian distribution maintenance software
pp.
Christoph Berg  (supplier of updated flask-login package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Mon, 09 Apr 2018 20:56:02 +0200
Source: flask-login
Binary: python3-flask-login python-flask-login-doc
Architecture: source
Version: 0.4.1-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Python Modules Team 

Changed-By: Christoph Berg 
Description:
 python-flask-login-doc - user session management for Flask -- documentation
 python3-flask-login - user session management for Flask -- Python 3 module
Closes: 889618 891025
Changes:
 flask-login (0.4.1-1) unstable; urgency=medium
 .
   * Team upload.
 .
   [ Ondřej Nový ]
   * d/control: Set Vcs-* to salsa.debian.org
 .
   [ Christoph Berg ]
   * New upstream version.
 + Remove 0002-allow-choice-of-nosetests-executable-in-run-tests.sh.patch.
   * Add python3-semantic-version test dependency.
   * Add missing docs/_themes copyright. (Closes: #889618)
   * python-flask-login-doc: Replaces: python3-flask-login-doc.
 (Closes: #891025)
Checksums-Sha1:
 543df6e82b2befb4a57602e5f404488113a3a9f9 2272 flask-login_0.4.1-1.dsc
 c4367bfc545b422d196d453c17831e2cbf7cbde1 43679 flask-login_0.4.1.orig.tar.gz
 8376f918901bea4024be89f4fa43a23b986d9dd3 5276 flask-login_0.4.1-1.debian.tar.xz
 f547cfdfb324de5fb29d1eaa5b7b84f6823a3ae9 6866 
flask-login_0.4.1-1_source.buildinfo
Checksums-Sha256:
 a7e9f54a5a99576ebbdaa0cc66760de866ef3ceabb9e0f8d3805033a69517d80 2272 
flask-login_0.4.1-1.dsc
 ed7facda15d0217ba02c2762b37711ad52144bbde401d6175109acd833d5e69f 43679 
flask-login_0.4.1.orig.tar.gz
 31297e975fd1928c810647d187593578433ba225719fb94af329cce652b3499a 5276 
flask-login_0.4.1-1.debian.tar.xz
 da97a6c05a677409504eee342efb82ddd10fb3c9bab78ebca649f76522ccd331 6866 
flask-login_0.4.1-1_source.buildinfo
Files:
 4cd391772eb20577e83a5a6405c98087 2272 python optional flask-login_0.4.1-1.dsc
 489905b7147d2dec9620892ec75bb397 43679 python optional 
flask-login_0.4.1.orig.tar.gz
 9518189b8c5183f1fd3eeead1da03f91 5276 python optional 
flask-login_0.4.1-1.debian.tar.xz
 78a46b6d90f2fdb5457c5eb2eabfd8eb 6866 python optional 
flask-login_0.4.1-1_source.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEEXEj+YVf0kXlZcIfGTFprqxLSp64FAlrLuHsACgkQTFprqxLS
p645cQ//ZthjkacQMbgsx2P6C28zGcQP6gSlUSosNmvVjfEa2Q2D6kEtr1prPcub
MjEJ2GARVPgb+Cimer03QVadYuM+8clK7cE8N3s0CNcSJG5pzgOieSTopIyjfl+7
vtQGyEs4AcUZEuI9jabaZkmb3CICmR2FVnV0DZm0z+Pf3ZlEwMA2+bU5ZeUks7CM
lbDKSYOYTO5QMcXyuRjPV4291GzToedz+YERvLLotL9frBobaMSKiA0GotxbKmYQ
fe1BmfqmZ7QTp4t6stcd1G2kPZhnsJlZvoFuB7Qov5Dh0UNxueS5rpVqL9P58OrN
XoGlnDsoZVWlR/1gSchaM3AGjUAuiWHZMfeq0YqsYXOO8boN/US/TXNU0Z8naUEW
1eTPPDe9QU+v6NGwiWPqKxbjiLRzhxzjbsBJ14Y6ZPH9tvwPqtfAlDtA1XX8gGAq
e6efZObYqkHhJNWPLAUj+MIFoiN9VKzHopjKkJTeu1dHDsorUYoXk/UXJOcZtwJI
7TTdainAzwHkf5kB7l90zgX5IHuZqwOBuWaUuDhw8Eyvzx1dKZu64eAAbRxeJGvV
yXIsQNcNGLFS8T1dm3baZnfz6m/EbZMX+IcN19hsJrWTmMPpKb9s3e0r4keTK0YC
3Uu+gyrqmBrhP5wMhWK+8WtC+KHWRKBmzM+NL/zGCyw4x05/C7Q=
=F3Hf
-END PGP SIGNATURE End 

Bug#895134: libwx-scintilla-perl: needs tighter dependency on Wx build?

[Olly Betts]

On Sun, Apr 08, 2018 at 11:42:47AM +0300, Niko Tyni wrote:
> On Sat, Apr 07, 2018 at 09:57:15PM +0100, Olly Betts wrote:
> > On Sat, Apr 07, 2018 at 04:20:48PM +0300, Niko Tyni wrote:
> > > So to do this properly it looks like we need something to make
> > > sure the Perl Wx related packages are upgraded in sync. The
> > > virtual package provided by libalien-wxwidgets-perl (currently
> > > wxperl-gtk-3-0-4-uni-gcc-3-4) seems like a candidate, but I don't have
> > > a ready recipe for injecting that.
> > 
> > I'd guess that makes sense, but I don't entirely understand how the
> > libalien-wxwidgets-perl <-> libwx-perl connection works, or why we need
> > a chain of binNMUs after each new upstream wxwidgets3.0 release.
> 
> AIUI Alien::wxWidgets provides information about a wxwidgets installation,
> and libwx-perl uses that to offer machinery for building wxwidgets
> related Perl packages (the Wx::build namespace.)  This build machinery
> embeds the exact wxwidgets version/configuration from Alien::wxWidgets,
> and breaks if those get out of sync. Hence the binNMU requirement. See
> #757855 for the full story.

I've read that ticket already, but I'm not really clear on why it
requires the exact wxWidgets version.  If you built against wxWidgets
3.0.3.1 then the real requirement is $upstream_version >= 3.0.3.1 not
$upstream_version == 3.0.3.1 (or perhaps >= some lower version if there
were no ABI additions since that version).

Is there something more subtle here, or is this effectively an
Alien::wxWidgets upstream design flaw which it's hard for distros to
diverge from?

> Another approach would be to consider this a one time glitch (how often
> are we going to change toolkits anyway?), make libwx-perl Break older
> (gtk2 based) libwx-scintilla-perl and libwx-glcanvas-perl versions,
> and have those packages in turn depend on newer (gtk3 based) libwx-perl
> versions. That should handle it afaics.

If this is only because of the gtk2 to gtk3 switch, then this makes
sense to me.  It's the first time this will have happened since we've
had these two packages, and only the second time in 18 years we've
changed toolkit in the default wxwidgets packages (previously gtk1 to
gtk2).

I see that libwx-scintilla-perl has a BD on libalien-wxwidgets-perl
and seems to actually use it, but it looks like only for build flags
and similar.

Cheers,
Olly

Bug#895320: mk-configure FTBFS: Error: /undefined in setupLatin1

[Adrian Bunk]

Source: mk-configure
Version: 0.29.1-2
Severity: serious

Some recent change in unstable makes mk-configure FTBFS:

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

...
/usr/bin/ps2pdf "presentation.ps" "presentation.pdf"
Error: /undefined in setupLatin1
Operand stack:

Execution stack:
   %interp_exit   .runexec2   --nostringval--   --nostringval--   
--nostringval--   2   %stopped_push   --nostringval--   --nostringval--   
--nostringval--   false   1   %stopped_push   2015   1   3   %oparray_pop   
2014   1   3   %oparray_pop   1998   1   3   %oparray_pop   1884   1   3   
%oparray_pop   --nostringval--   %errorexec_pop   .runexec2   --nostringval--   
--nostringval--   --nostringval--   2   %stopped_push   --nostringval--
Dictionary stack:
   --dict:986/1684(ro)(G)--   --dict:0/20(G)--   --dict:88/200(L)--   
--dict:190/300(L)--   --dict:91/200(L)--
Current allocation mode is local
Last OS error: No such file or directory
Current file position is 459040
GPL Ghostscript 9.22: Unrecoverable error, exit code 1
GPL Ghostscript 9.22: ERROR: A pdfmark destination page 53 points beyond the 
last page 52.
*** Error code 1

Stop.
bmake[4]: stopped in /build/1st/mk-configure-0.29.1/presentation
bmake[3]: Entering directory `/build/1st/mk-configure-0.29.1'
*** Error code 1

Stop.
bmake[3]: stopped in /build/1st/mk-configure-0.29.1
bmake[2]: Entering directory `/build/1st/mk-configure-0.29.1'
*** Error code 1

Stop.
bmake[2]: stopped in /build/1st/mk-configure-0.29.1
make[1]: *** [debian/rules:17: override_dh_auto_build] Error 1

Processed: tagging 895316

[Debian Bug Tracking System]

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

> tags 895316 + buster sid
Bug #895316 [src:node-once] node-once: FTBFS and flaky autopkgtests
Added tag(s) buster and sid.
> thanks
Stopping processing here.

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

Bug#895317: node-commander: FTBFS unreliable timing

[Graham Inggs]

Source: node-commander
Version: 2.12.2-1
Severity: serious

Hi Maintainer

Since the upload of nodejs 8.9.3, node-commander has FTBFS [1] with
errors similar to the
following:

/usr/lib/nodejs/should/lib/assertion.js:72
throw new AssertionError(params);
^
AssertionError: expected '' to be 'SIGHUP\n'
at Assertion.fail (/usr/lib/nodejs/should/lib/assertion.js:92:17)
at Assertion.value (/usr/lib/nodejs/should/lib/assertion.js:164:19)
at Timeout._onTimeout
(/build/1st/node-commander-2.12.2/test/test.command.executableSubcommand.signals.hup.js:19:19)
at ontimeout (timers.js:475:11)
at tryOnTimeout (timers.js:310:5)
at Timer.listOnTimeout (timers.js:270:5)
make[1]: *** [debian/rules:15: override_dh_auto_test] Error 1

I believe this is similar to the unreliable timing in tests being
discussed in #853035.

Regards
Graham


[1] 
https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/node-commander.html

Bug#895316: node-once: FTBFS and flaky autopkgtests

[Graham Inggs]

Source: node-once
Version: 1.4.0-2
Severity: serious
User: ci-t...@tracker.debian.org
Usertags: flaky

Hi Maintainer

Since the upload of nodejs 8.9.3, node-once has FTBFS [1] and
autopkgtests have been failing [2] with errors similar to the
following:

ok 1166 - should be equivalent
ok 1167 - should be equivalent
ok 1168 - should be equivalent
ok 1169 - expect truthy value
ok 1170 - should be equivalent
ok 1171 - should be equivalent
ok 1172 - should be equivalent
ok 1173 - expect truthy value
# time=3901.372ms
1..0 # no tests found
# test count(1173) != plan(null)
# failed 1 of 1173 tests
1..0 # no tests found
not ok 1 - test/once.js # SKIP no tests found

1..1
# failed 1 test
# skip: 1
# time=9638.788ms

I believe this is similar to the unreliable timing in tests being
discussed in #853035.

Regards
Graham


[1] 
https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/node-once.html
[2] https://ci.debian.net/packages/n/node-once/unstable/amd64/

Processed: tagging 894775

[Debian Bug Tracking System]

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

> tags 894775 + confirmed
Bug #894775 [src:kgb-bot] kgb-bot: FTBFS and Debci failure with git >= 2.16.3
Added tag(s) confirmed.
> thanks
Stopping processing here.

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

Bug#895315: xul-ext-greasemonkey: Could not use script with recent firefox need to upgrade to 4.x

[Bastien Roucariès]

Package: xul-ext-greasemonkey
Version: 3.8-1
Severity: grave
Justification: renders package unusable

Hi,

The current greasemonkey is incompatible with newer firefox.

Could you please upgrade



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

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

Versions of packages xul-ext-greasemonkey depends on:
ii  firefox  55.0~b2-1
ii  firefox-esr  52.7.3esr-1
ii  iceweasel52.7.3esr-1

xul-ext-greasemonkey recommends no packages.

xul-ext-greasemonkey suggests no packages.

-- debconf-show failed

Bug#895314: pcs: CVE-2018-1079: Privilege escalation via authorized user malicious REST call

[Salvatore Bonaccorso]

Source: pcs
Version: 0.9.162-1
Severity: grave
Tags: security upstream

Hi,

The following vulnerability was published for pcs.

CVE-2018-1079[0]:
Privilege escalation via authorized user malicious REST call

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

For further information see:

[0] https://security-tracker.debian.org/tracker/CVE-2018-1079
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-1079
[1] http://www.openwall.com/lists/oss-security/2018/04/09/2

Regards,
Salvatore

Bug#894797: node-foreground-child: FTBFS

[Graham Inggs]

I believe this is related to unreliable timing in tests being
discussed in #853035.

Bug#895312: node-tap: FTBFS and flaky autopkgtests

[Graham Inggs]

Source: node-tap
Version: 11.0.0+ds1-2
Severity: serious
User: ubuntu-de...@lists.ubuntu.com
Usertags: origin-ubuntu bionic autopkgtest
User: ci-t...@package.debian.org
Usertags: flaky

Hi Maintainer

Since the upload of nodejs 8.9.3, node-tap has FTBFS [1] and
autopkgtests have been failing [2] with errors similar to the
following:

  1) test/run.js parallel should be equal:

  Error: should be equal
  + expected - actual

   ry2
   f1
   f2
   start
  -end
   start
   end
  +end

  at run (test/run.js:555:7)

  2) test/spawn.js timeout KILL should be equal:

  Error: should be equal
  + expected - actual

  -1..0 # no tests found
  +SIGTERM
  +
  +not ok 1 - timeout!
  +  ---
  +  expired: killa
  +  ...
  +1..1
  +# failed 1 test

I believe this is similar to the issue being discussed in #853035.

Regards
Graham


[1] 
https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/node-tap.html
[2] https://ci.debian.net/packages/n/node-tap/unstable/amd64/

Processed: tagging 861361

[Debian Bug Tracking System]

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

> tags 861361 + buster sid
Bug #861361 [ruby-riddle] ruby-riddle: update build-depend to unversioned 
php-cli
Added tag(s) sid and buster.
> thanks
Stopping processing here.

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

Bug#895180: rakudo: dependency on nqp is too strict

[Dominique Dumont]

On Sunday, 8 April 2018 09:57:03 CEST Adrian Bunk wrote:
> Please relax the nqp dependency to require only
> the upstream version of nqp (similar to the
> moarvm dependency).

I'd like to, but this constraint comes from upstream.

I've already discussed this problem with upstream and they kinda agreed to 
change this strong dependency. [1]

I'm going to open a bug upstream to have this issue tracked.

All the best

[1] https://salsa.debian.org/perl6-team/rakudo/raw/master/debian/README.source

Processed: [bts-link] source package src:python-ncclient

[Debian Bug Tracking System]

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

> #
> # bts-link upstream status pull for source package src:python-ncclient
> # see http://lists.debian.org/debian-devel-announce/2006/05/msg1.html
> #
> user bts-link-upstr...@lists.alioth.debian.org
Setting user to bts-link-upstr...@lists.alioth.debian.org (was 
bts-link-de...@lists.alioth.debian.org).
> # remote status report for #894432 (http://bugs.debian.org/894432)
> # Bug title: python-ncclient FTBFS: AttributeError: 'NoneType' object has no 
> attribute 'settimeout'
> #  * https://github.com/ncclient/ncclient/issues/227
> #  * remote status changed: closed -> open
> #  * reopen upstream
> tags 894432 - fixed-upstream
Bug #894432 [src:python-ncclient] python-ncclient FTBFS: AttributeError: 
'NoneType' object has no attribute 'settimeout'
Removed tag(s) fixed-upstream.
> usertags 894432 - status-closed
Usertags were: status-closed.
Usertags are now: .
> usertags 894432 + status-open
There were no usertags set.
Usertags are now: status-open.
> thanks
Stopping processing here.

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

Processed: [bts-link] source package src:forge

[Debian Bug Tracking System]

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

> #
> # bts-link upstream status pull for source package src:forge
> # see http://lists.debian.org/debian-devel-announce/2006/05/msg1.html
> #
> user bts-link-upstr...@lists.alioth.debian.org
Setting user to bts-link-upstr...@lists.alioth.debian.org (was 
bts-link-de...@lists.alioth.debian.org).
> # remote status report for #888931 (http://bugs.debian.org/888931)
> # Bug title: forge FTBFS with libglm-dev 0.9.9~a2-1
> #  * https://github.com/arrayfire/forge/issues/160
> #  * remote status changed: open -> closed
> #  * closed upstream
> tags 888931 + fixed-upstream
Bug #888931 [src:forge] forge FTBFS with libglm-dev 0.9.9~a2-1
Added tag(s) fixed-upstream.
> usertags 888931 - status-open
Usertags were: status-open.
Usertags are now: .
> usertags 888931 + status-closed
There were no usertags set.
Usertags are now: status-closed.
> thanks
Stopping processing here.

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

Processed: [bts-link] source package src:xiphos

[Debian Bug Tracking System]

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

> #
> # bts-link upstream status pull for source package src:xiphos
> # see http://lists.debian.org/debian-devel-announce/2006/05/msg1.html
> #
> user bts-link-upstr...@lists.alioth.debian.org
Setting user to bts-link-upstr...@lists.alioth.debian.org (was 
bts-link-de...@lists.alioth.debian.org).
> # remote status report for #866657 (http://bugs.debian.org/866657)
> # Bug title: xiphos: depends on libwebkitgtk-3.0-0 which is deprecated
> #  * https://github.com/crosswire/xiphos/issues/834
> #  * remote status changed: open -> closed
> #  * closed upstream
> tags 866657 + fixed-upstream
Bug #866657 [src:xiphos] xiphos: depends on libwebkitgtk-3.0-0 which is 
deprecated
Added tag(s) fixed-upstream.
> usertags 866657 - status-open
Usertags were: status-open.
Usertags are now: .
> usertags 866657 + status-closed
There were no usertags set.
Usertags are now: status-closed.
> thanks
Stopping processing here.

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

Processed: Re: ruby-riddle: update build-depend to unversioned php-cli

[Debian Bug Tracking System]

Processing control commands:

> severity -1 serious
Bug #861361 [ruby-riddle] ruby-riddle: update build-depend to unversioned 
php-cli
Severity set to 'serious' from 'normal'

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

Bug#895134: libwx-scintilla-perl: needs tighter dependency on Wx build?

[Niko Tyni]

On Sun, Apr 08, 2018 at 11:42:47AM +0300, Niko Tyni wrote:

> Another approach would be to consider this a one time glitch (how often
> are we going to change toolkits anyway?), make libwx-perl Break older
> (gtk2 based) libwx-scintilla-perl and libwx-glcanvas-perl versions,
> and have those packages in turn depend on newer (gtk3 based) libwx-perl
> versions. That should handle it afaics.

I'm inclined to do this unless I hear objections in the next few days.
-- 
Niko

Bug#894742: marked as done (libguestfs: build-depends on linux-image-marvell on armel)

[Debian Bug Tracking System]

Your message dated Mon, 09 Apr 2018 15:25:43 +
with message-id 
and subject line Bug#894742: fixed in libguestfs 1:1.38.0-1
has caused the Debian Bug report #894742,
regarding libguestfs: build-depends on linux-image-marvell on armel
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.)


-- 
894742: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=894742
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: libguestfs
Version: 1:1.36.13-2
Severity: serious

Hi,

libguestfs build-depends on linux-image-marvell on armel, but that package
is gone. Thus libguestfs is currently unbuildable:

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

Emilio
--- End Message ---
--- Begin Message ---
Source: libguestfs
Source-Version: 1:1.38.0-1

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

Debian distribution maintenance software
pp.
Hilko Bengen  (supplier of updated libguestfs package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Mon, 09 Apr 2018 12:21:32 +0200
Source: libguestfs
Binary: guestfsd libguestfs-dev libguestfs0 libguestfs-gfs2 libguestfs-hfsplus 
libguestfs-jfs libguestfs-nilfs libguestfs-reiserfs libguestfs-rescue 
libguestfs-rsync libguestfs-xfs libguestfs-zfs libguestfs-tools python-guestfs 
python3-guestfs libguestfs-perl libguestfs-ocaml libguestfs-ocaml-dev 
erlang-guestfs libguestfs-java ruby-guestfs libguestfs-gobject-1.0-0 
libguestfs-gobject-dev gir1.2-guestfs-1.0 lua-guestfs golang-guestfs-dev 
php-guestfs
Architecture: source
Version: 1:1.38.0-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Libvirt Maintainers 

Changed-By: Hilko Bengen 
Description:
 erlang-guestfs - guest disk image management system - Erlang bindings
 gir1.2-guestfs-1.0 - guest disk image management system - GObject 
introspection files
 golang-guestfs-dev - guest disk image management system - Golang bindings
 guestfsd   - Daemon to access to guest virtual machine through virtio serial
 libguestfs-dev - guest disk image management system - development headers
 libguestfs-gfs2 - guest disk image management system - GFS2 support
 libguestfs-gobject-1.0-0 - guest disk image management system - GObject 
bindings
 libguestfs-gobject-dev - guest disk image management system - GObject 
development headers
 libguestfs-hfsplus - guest disk image management system - HFS+ support
 libguestfs-java - guest disk image management system - Java bindings
 libguestfs-jfs - guest disk image management system - JFS support
 libguestfs-nilfs - guest disk image management system - NILFS v2 support
 libguestfs-ocaml - guest disk image management system - OCaml bindings
 libguestfs-ocaml-dev - guest disk image management system - OCaml development 
files
 libguestfs-perl - guest disk image management system - Perl bindings
 libguestfs-reiserfs - guest disk image management system - ReiserFS support
 libguestfs-rescue - guest disk image management system - virt-rescue 
enhancements
 libguestfs-rsync - guest disk image management system - rsync support
 libguestfs-tools - guest disk image management system - tools
 libguestfs-xfs - guest disk image management system - XFS support
 libguestfs-zfs - guest disk image management system - ZFS support
 libguestfs0 - guest disk image management system - shared library
 lua-guestfs - guest disk image management system - Lua bindings
 php-guestfs - guest disk image management system - PHP bindings
 python-guestfs - guest disk image management system - Python bindings
 python3-guestfs - guest disk image management system - Python 3 bindings
 ruby-guestfs - guest disk image management system - Ruby bindings
Closes: 894742
Changes:
 libguestfs (1:1.38.0-1) unstable; urgency=medium
 .
   * New upstream version 1.38.0
   * Add architectures for golang-go, zfs-fuse build-dependencies
   * Update Vcs-* fields for salsa.debian.org
   * Add build dependencies: yara, hivex-ocaml

Bug#893019: marked as done (flask-restful FTBFS with python3-aniso8601 3.0.0-1)

[Debian Bug Tracking System]

Your message dated Mon, 09 Apr 2018 15:14:06 +
with message-id 
and subject line Bug#893019: fixed in flask-restful 0.3.6-3
has caused the Debian Bug report #893019,
regarding flask-restful FTBFS with python3-aniso8601 3.0.0-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.)


-- 
893019: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=893019
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: flask-restful
Version: 0.3.6-1
Severity: serious

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

...
   dh_auto_test -O--buildsystem=pybuild
I: pybuild base:215: cd 
/build/1st/flask-restful-0.3.6/.pybuild/cpython3_3.6_flask-restful/build; 
python3.6 -m nose tests
...[2019-04-16 18:13:58,776] ERROR in app: Exception on / [GET]
Traceback (most recent call last):
  File "/usr/lib/python3/dist-packages/flask/app.py", line 1612, in 
full_dispatch_request
rv = self.dispatch_request()
  File "/usr/lib/python3/dist-packages/flask/app.py", line 1598, in 
dispatch_request
return self.view_functions[rule.endpoint](**req.view_args)
  File 
"/build/1st/flask-restful-0.3.6/.pybuild/cpython3_3.6_flask-restful/build/flask_restful/__init__.py",
 line 484, in wrapper
return self.make_response(data, code, headers=headers)
  File 
"/build/1st/flask-restful-0.3.6/.pybuild/cpython3_3.6_flask-restful/build/flask_restful/__init__.py",
 line 521, in make_response
raise InternalServerError()
werkzeug.exceptions.InternalServerError: 500 Internal Server Error: The server 
encountered an internal error and was unable to complete your request.  Either 
the server is overloaded or there is an error in the application.
.[2019-04-16 18:13:58,929] ERROR in app: Exception on 
/foo [GET]
[2019-04-16 18:13:59,024] ERROR in app: Exception on /foo [GET]
..[2019-04-16 18:13:59,032] ERROR in app: Exception on /foo [GET]
...E.
==
ERROR: tests.test_inputs.test_bad_isointervals(, , '')
--
Traceback (most recent call last):
  File "/usr/lib/python3/dist-packages/nose/case.py", line 197, in runTest
self.test(*self.arg)
  File "/usr/lib/python3.6/unittest/case.py", line 733, in assertRaises
return context.handle('assertRaises', args, kwargs)
  File "/usr/lib/python3.6/unittest/case.py", line 178, in handle
callable_obj(*args, **kwargs)
  File 
"/build/1st/flask-restful-0.3.6/.pybuild/cpython3_3.6_flask-restful/build/flask_restful/inputs.py",
 line 171, in iso8601interval
start, end = _parse_interval(value)
  File 
"/build/1st/flask-restful-0.3.6/.pybuild/cpython3_3.6_flask-restful/build/flask_restful/inputs.py",
 line 134, in _parse_interval
return sorted(aniso8601.parse_interval(value))
  File "/usr/lib/python3/dist-packages/aniso8601/interval.py", line 34, in 
parse_interval
if isointervalstr[0] == 'R':
IndexError: string index out of range

--
Ran 395 tests in 1.483s

FAILED (errors=1)
E: pybuild pybuild:323: test: plugin distutils failed with: exit code=1: cd 
/build/1st/flask-restful-0.3.6/.pybuild/cpython3_3.6_flask-restful/build; 
python3.6 -m nose tests
dh_auto_test: pybuild --test --test-nose -i python{version} -p 3.6 returned 
exit code 13
make: *** [debian/rules:6: build] Error 25
--- End Message ---
--- Begin Message ---
Source: flask-restful
Source-Version: 0.3.6-3

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

Debian distribution maintenance software
pp.
Jonathan Carter  (supplier of updated flask-restful package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive

Bug#895246: gconf: Intent to Adopt

[Simon McVittie]

(I don't speak for the GNOME team, or for Josselin, who is officially
this package's maintainer; please don't assume I do.)

On Sun, 08 Apr 2018 at 22:19:43 +0300, Adrian Bunk wrote:
> I hereby declare my intent to adopt gconf.

Thank you for offering to take over this package. Do you also intend
to adopt these related packages?

- src:gconf-editor (which depends on gconf and is useless without it;
  currently maintained by the GNOME team)
- src:orbit2 (orphaned library needed by gconf)
- src:libidl (orphaned library needed by orbit2)
- various language bindings for gconf

All are equally dead upstream (or more so in some cases) as far as I
can tell.

Do you use software that relies on gconf yourself/are you able to test it?

I recently converted gconf's svn repository to git,
, along with a batch of other
svn repositories where the first round of imports via reposurgeon had
failed. Anything else that is currently maintained by the GNOME team
(notably gconf-editor) should be in git too, and that's almost certainly
a better starting point than the svn repositories currently listed in
their Vcs-* fields. I don't think orbit2 and libidl were ever maintained
by pkg-gnome, and they probably did't have a VCS before they were orphaned.

A gnome-team Owner or a salsa sysadmin might be able to move gconf into
another namespace on salsa while leaving redirects behind, if that's
something you'd find useful.

> This is about keeping software that is long dead upstream but
> has reverse dependencies longer on life support.

My concern about keeping packages like gconf in Debian, rather than
removing them, is that keeping significant amounts of unmaintained
software in Debian is an ongoing time- and attention-sink for contributors
doing archive-wide QA, and a distraction for users looking for software
of interest.

For contributors: every time a package that hasn't had upstream
development for a few years fails to build during a transition, or
needs fixes for a new architecture, or has RC bugs that someone looks
at during a BSP, it takes a little bit more of several contributors'
time and attention (even if the only attention it gets is to look at the
package, realise it hasn't changed significantly in a decade, and decide
to prioritize something different). Software that depends on gconf isn't
*directly* an indication of something terribly bad, but it's reasonably
well correlated with the dependent software also being unmaintained or
undermaintained upstream. Each individual package blocking a transition,
and each individual RC bug, doesn't necessarily take much time and
attention, but it adds up over time, and I'm concerned that the long
tail of GNOME-2-based packages might be collectively and cumulatively
taking more time and attention than it deserves. In the case of gconf,
it's had about 8 years of deprecation. If you keep gconf and its rdeps on
life support until buster, how much do you expect the dependent packages
to have changed by the time we get to the bullseye freeze? If you keep
them going until bullseye, is the situation going to have improved for
bullseye+1? And so on. If the upstream maintainer of some software has
abandoned it, we can keep it alive for a while, but I don't think it's
healthy for Debian to take over for multiple of our release cycles[1].

For users: having a "long tail" of undermaintained software is both
a strength and a weakness. It's a strength because we get to say we
provide a vast amount of software, some of it very specialized. It's
a weakness because it drags down the average level of quality of the
results of a search for packages: if we have (say) two well-maintained
implementations of a particular class of package, we'd probably prefer
users to find only those two in a search, and not find them listed among
multiple poorly-maintained implementations. This requires some
value-judgement/curation, which Debian has historically not been great at.

One way this could perhaps be mitigated is by improving how we mark
deprecated and obsolescent packages, and as a small starting point for
that I've just opened a ftp-master bug to get gconf and gconfmm moved to
oldlibs (I hadn't realised they were still in libs). Better Description
fields might also help, but the sort of libraries that we don't want
new code using are exactly the sort of libraries where rewriting the
Description isn't high on anyone's priorities. Ideally this would have
happened back in 2010 when gconf was deprecated, of course, but
hindsight is always clearer.

If we had bikesheds, PPAs or an equivalent of Ubuntu universe, I'd
suggest moving unmaintained/undermaintained packages to one of those
to indicate that users shouldn't have the same quality expectations,
but we don't currently have that facility.

If, bearing all that in mind, you still think Debian is better with
gconf than without it, then I'm not going to try to prevent you from
maintaining it. (Again, I don't 

Bug#894816: closed by HIGUCHI Daisuke (VDR dai) <d...@debian.org> (Bug#894816: fixed in ruby-gnome2 3.2.3-2)

[Hideo Oshima]

On Sun, 08 Apr 2018 09:51:10 +
"Debian Bug Tracking System"  wrote:

> This is an automatic notification regarding your Bug report
> which was filed against the ruby-gtk2 package:
> 
> #894816: [ruby-gtk2] mikutter doesn't start with error
> 
> It has been closed by HIGUCHI Daisuke (VDR dai) .
> 
> Their explanation is attached below along with your original report.
> If this explanation is unsatisfactory and you have not received a
> better one in a separate message then please contact HIGUCHI Daisuke (VDR 
> dai)  by
> replying to this email.
> 
> 
> -- 
> 894816: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=894816
> Debian Bug Tracking System
> Contact ow...@bugs.debian.org with problems

I confirmed to fix the problem
Thanks for your work!

-- 
大島秀夫(Hideo Oshima)
http://hidenosuke.org/

Processed: tagging 895282

[Debian Bug Tracking System]

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

> tags 895282 + stretch buster sid
Bug #895282 [trac-authopenid] trac-authopenid: fails to work with trac 1.2 
(get_db_cnx does not work)
Added tag(s) stretch, sid, and buster.
> thanks
Stopping processing here.

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

Bug#893142: dogtag-pki FTBFS with openjdk-9

[Gianfranco Costamagna]

On Fri, 16 Mar 2018 23:04:45 +0200 Adrian Bunk  wrote:
> Source: dogtag-pki
> Version: 10.5.5-1
> Severity: serious
> 
> https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/dogtag-pki.html
> 
> ...
> netscape/security/x509/RevocationReasonAdapter.java:20: error: package 
> javax.xml.bind.annotation.adapters is not visible
> import javax.xml.bind.annotation.adapters.XmlAdapter;
> ^
>   (package javax.xml.bind.annotation.adapters is declared in module 
> java.xml.bind, which is not in the module graph)
> 
> 

this has been removed from java9 defaults, but you can add it manually with 
"add-modules"
--- dogtag-pki-10.5.5.orig/cmake/Modules/Java.cmake
+++ dogtag-pki-10.5.5/cmake/Modules/Java.cmake
@@ -80,6 +80,7 @@ function(javac target)
 COMMAND ${Java_JAVAC_EXECUTABLE}
 ${CMAKE_JAVA_COMPILE_FLAGS}
 -encoding UTF-8
+--add-modules java.xml.bind
 -cp ${native_classpath}
 -d ${output_dir}
 @${file_list}


Unfortunately the package will fail because of: 

cd /dogtag-pki-10.5.5/base/util/test && /usr/lib/jvm/default-java/bin/javac 
-encoding UTF-8 --add-modules java.xml.bind -cp 
:/dogtag-pki-10.5.5/build/core/dist/pki-nsutil.jar:/dogtag-pki-10.5.5/build/core/dist/pki-cmsutil.jar:/usr/share/java/jss4.jar:/usr/share/java/ldapjdk.jar:/usr/share/java/commons-codec.jar:/usr/share/java/xalan2.jar:/usr/share/java/xercesImpl.jar:HAMCREST_JAR-NOTFOUND:/usr/share/java/junit4.jar
 -d /dogtag-pki-10.5.5/build/core/test/classes 
@/dogtag-pki-10.5.5/build/core/base/util/test/pki-util-test-classes.files 
--add-modules sun.security
error: module not found: sun.security


this requires code changes: because sun.security.util seems dead now.

Gianfranco

Bug#894365: marked as done (virtualbox build depends on openjdk-8-jdk-headless)

[Debian Bug Tracking System]

Your message dated Mon, 09 Apr 2018 13:33:14 +
with message-id 
and subject line Bug#894365: fixed in virtualbox 5.2.8-dfsg-6
has caused the Debian Bug report #894365,
regarding virtualbox build depends on openjdk-8-jdk-headless
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.)


-- 
894365: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=894365
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: virtualbox
Version: 5.2.8-dfsg-5
Severity: serious

virtualbox build depends on openjdk-8-jdk-headless,
which is not expected to be part of the buster release.
--- End Message ---
--- Begin Message ---
Source: virtualbox
Source-Version: 5.2.8-dfsg-6

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

Debian distribution maintenance software
pp.
Gianfranco Costamagna  (supplier of updated 
virtualbox 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: Thu, 29 Mar 2018 19:05:29 +0200
Source: virtualbox
Binary: virtualbox-qt virtualbox virtualbox-dkms virtualbox-source 
virtualbox-guest-dkms virtualbox-guest-source virtualbox-guest-x11 
virtualbox-guest-utils
Architecture: source
Version: 5.2.8-dfsg-6
Distribution: unstable
Urgency: medium
Maintainer: Debian Virtualbox Team 

Changed-By: Gianfranco Costamagna 
Description:
 virtualbox - x86 virtualization solution - base binaries
 virtualbox-dkms - x86 virtualization solution - kernel module sources for dkms
 virtualbox-guest-dkms - x86 virtualization solution - guest addition module 
source for dk
 virtualbox-guest-source - x86 virtualization solution - guest addition module 
source
 virtualbox-guest-utils - x86 virtualization solution - non-X11 guest utilities
 virtualbox-guest-x11 - x86 virtualization solution - X11 guest utilities
 virtualbox-qt - x86 virtualization solution - Qt based user interface
 virtualbox-source - x86 virtualization solution - kernel module source
Closes: 894365
Changes:
 virtualbox (5.2.8-dfsg-6) unstable; urgency=medium
 .
   * Build with java9 (Closes: #894365)
 - thanks Emmanuel Bourg for all the great help!
Checksums-Sha1:
 dcc29acf9075a25d091080fbcd3337eaf07eed96 3593 virtualbox_5.2.8-dfsg-6.dsc
 e074e85b7809c355d3bfbf1c037313c2cc3c3707 83212 
virtualbox_5.2.8-dfsg-6.debian.tar.xz
 09e926765acd658c24cce88272e6fd3b640be638 21076 
virtualbox_5.2.8-dfsg-6_source.buildinfo
Checksums-Sha256:
 7e209c7c7dfdd8f6094f4edca7e8660dde90fa2fb0c80c383bd7297b80109935 3593 
virtualbox_5.2.8-dfsg-6.dsc
 52e3abc1692f52b4c6f1b7727039320c19a3511af216e1adce39c493808d78ae 83212 
virtualbox_5.2.8-dfsg-6.debian.tar.xz
 6b82fa7a83c36385169dbf0bafbd45f527fcfa5fc26be99b0f9b85a250fe3928 21076 
virtualbox_5.2.8-dfsg-6_source.buildinfo
Files:
 72fc39394b130c4ee80c79ee6705a646 3593 contrib/misc optional 
virtualbox_5.2.8-dfsg-6.dsc
 6b57a4268d36978408342f6d4d917a30 83212 contrib/misc optional 
virtualbox_5.2.8-dfsg-6.debian.tar.xz
 e6a706bc9e8ee5730e752d679d6913e0 21076 contrib/misc optional 
virtualbox_5.2.8-dfsg-6_source.buildinfo

-BEGIN PGP SIGNATURE-

iQIcBAEBCAAGBQJayz3RAAoJEPNPCXROn13ZNfIP/3K4ke5cDqqacWXzRJPF977B
b+KrQtVIaC29NLRgL83MqzBLsXE3fJgSC4nL4njYRehsWJ0wHaOujZ2veHNT4rGD
8RQLYLZhj/JjVyTzkLrfpGD08Y90uv7kChAmLwIisu9whja6ErrXoZ0Ih/aV8E0c
+lsKBmtryBulmOKZi3xIQ3YfQ4Wl1XRQXbjKpXJB2rLOysBJHMd9s3xH+YKx9vN8
F5xm6k20bdvoBWkAVSblIep8Y6Sf1Hrczk5lAIs4QKHw0C2VHXadX28WjPzugnZQ
xUCf3aBYqGv+39EEXXtXB/pvoQAHbUwdF5bU4BQT8dNxZR5Xp3CCQYPTnsZvPTZA
KI2IyC/wRDuJCmd4x2rIRnAqln+iDmTHljWrQTQAX3EuNWnlusAgUZp6XnzmQqbL
1lps0MDfb9E2LLP2cqIVch3CnuV7G2dMjjJneSE8KN2KCNcd3iwVwZY5v+udTvpL
xoXjHrjq06k5+d546UG/I24VAQWAaBlXV+wP3Jw0vtIxC24j6Ev4uVT564+LvwDa
ggHk1OLgZBK4MmTFEhMwL/YeSFnhUqAMfEjpqNN9RATuHZCOAUGQFT6oNKispysA
kUvzkbXRvI8xYewXQO+J4CXDz4vAeY25FMS8/Aqwy1NsN4qjQYrKgKy/A0nyIABn
bU+NcV0H26gB0RmCAqmt
=uqBt
-END PGP SIGNATURE End Message ---

Bug#895154: marked as done (ffmpeg: FTBFS - make[2]: write error: stdout)

[Debian Bug Tracking System]

Your message dated Mon, 09 Apr 2018 13:09:31 +
with message-id 
and subject line Bug#895154: fixed in ffmpeg 7:3.4.2-2
has caused the Debian Bug report #895154,
regarding ffmpeg: FTBFS - make[2]: write error: stdout
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.)


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

For some reason ffmpeg has started FTBFS with this error:
> TESTvsynth2-zlib
> /<>/tests/fate-run.sh fate-vsynth2-zlib "" "" 
> "/<>/debian/standard" 'enc_dec "rawvideo -s 352x288 -pix_fmt 
> yuv420p " tests/data/vsynth2.yuv avi "-c zlib " rawvideo "-s 352x288 -pix_fmt 
> yuv420p -vsync 0 " -keep ""' '' 
> '/<>/tests/ref/vsynth/vsynth2-zlib' '' '1' '' '' '' '' '' '1' '' 
> '' ''
>  /<>/debian/standard/ffmpeg -nostdin -nostats -cpuflags all -f 
> rawvideo -s 352x288 -pix_fmt yuv420p -threads 1 -idct simple -flags +bitexact 
> -sws_flags +accurate_rnd+bitexact -fflags +bitexact -hwaccel none -threads 1 
> -thread_type frame+slice -i 
> /<>/debian/standard/tests/data/vsynth2.yuv -threads 1 -idct 
> simple -dct fastint -c zlib -flags +bitexact -sws_flags 
> +accurate_rnd+bitexact -fflags +bitexact -f avi -y 
> /<>/debian/standard/tests/data/fate/vsynth2-zlib.avi
>  /<>/debian/standard/ffmpeg -nostdin -nostats -cpuflags all 
> -threads 1 -idct simple -flags +bitexact -sws_flags +accurate_rnd+bitexact 
> -fflags +bitexact -hwaccel none -threads 1 -thread_type frame+slice -i 
> /<>/debian/standard/tests/data/fate/vsynth2-zlib.avi -threads 1 
> -idct simple -dct fastint -s 352x288 -pix_fmt yuv420p -vsync 0 -flags 
> +bitexact -sws_flags +accurate_rnd+bitexact -fflags +bitexact -f rawvideo -y 
> /<>/debian/standard/tests/data/fate/vsynth2-zlib.out.rawvideo
> make[2]: Leaving directory '/<>/debian/standard'
> make[2]: write error: stdout
> dh_auto_test: cd debian/standard && make -j4 -O check -k returned exit code 1
> make[1]: *** [debian/rules:231: override_dh_auto_test-arch] Error 25
> make[1]: Leaving directory '/<>'
> make: *** [debian/rules:192: binary] Error 2
> dpkg-buildpackage: error: debian/rules binary subprocess returned exit status 
> 2

This can be seen on the reproducible builds first seen 2018-03-15
affecting 3.4 and 3.5 in experimental.

I'm guessing this has something to do with "make -O" which was enabled
recently in debhelper, but I haven't checked.

James



signature.asc
Description: OpenPGP digital signature
--- End Message ---
--- Begin Message ---
Source: ffmpeg
Source-Version: 7:3.4.2-2

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

Debian distribution maintenance software
pp.
James Cowgill  (supplier of updated ffmpeg package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Mon, 09 Apr 2018 12:24:40 +0100
Source: ffmpeg
Binary: ffmpeg ffmpeg-doc libavcodec57 libavcodec-extra57 libavcodec-extra 
libavcodec-dev libavdevice57 libavdevice-dev libavfilter6 libavfilter-extra6 
libavfilter-extra libavfilter-dev libavformat57 libavformat-dev libavresample3 
libavresample-dev libavutil55 libavutil-dev libpostproc54 libpostproc-dev 
libswresample2 libswresample-dev libswscale4 libswscale-dev
Architecture: source
Version: 7:3.4.2-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Multimedia Maintainers 
Changed-By: James Cowgill 
Description:
 ffmpeg - Tools for transcoding, streaming and playing of multimedia files
 ffmpeg-doc - Documentation of the FFmpeg multimedia framework
 libavcodec-dev - FFmpeg library with de/encoders for audio/video codecs - 
developm
 libavcodec-extra - FFmpeg library with extra codecs (metapackage)
 libavcodec-extra57 - FFmpeg library with additional de/encoders for 
audio/video codecs
 libavcodec57 - FFmpeg library with de/encoders for audio/video codecs - runtime
 libavdevice-dev - FFmpeg library for 

Bug#891021: marked as done (aseba uses Qt4's WebKit)

[Debian Bug Tracking System]

Your message dated Mon, 09 Apr 2018 13:05:32 +
with message-id 
and subject line Bug#891021: fixed in aseba 1.6.0-3
has caused the Debian Bug report #891021,
regarding aseba uses Qt4's WebKit
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.)


-- 
891021: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=891021
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: aseba
Version: 1.6.0-2
Severity: serious

aseba uses Qt4's WebKit that will be removed from buster
in a few days/weeks.

The bugs for other qtwebkit-using packages have already
been made RC in August 2017 (aseba just passed NEW).

See https://wiki.debian.org/Qt4WebKitRemoval for details.
--- End Message ---
--- Begin Message ---
Source: aseba
Source-Version: 1.6.0-3

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

Debian distribution maintenance software
pp.
Georges Khaznadar  (supplier of updated aseba package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Sat, 24 Feb 2018 14:45:29 +0100
Source: aseba
Binary: aseba
Architecture: source amd64
Version: 1.6.0-3
Distribution: unstable
Urgency: medium
Maintainer: Georges Khaznadar 
Changed-By: Georges Khaznadar 
Description:
 aseba  - Event-based framework for distributed mobile robots control
Closes: 891021
Changes:
 aseba (1.6.0-3) unstable; urgency=medium
 .
   * debian/control: new build dependencies are qtbase5-dev, qt5-qmake,
 libqt5opengl5-dev, libqt5webkit5-dev, qtbase5-dev, qtbase5-dev-tools,
 qttools5-dev, libqwt-qt5-dev, libqt5svg5-dev
   * patched CMakeLists.txt, .cpp and .h files to use Qt5. Closes: #891021
   * skipped the auto_test taget in debian/rules
Checksums-Sha1:
 d2659b95198b2a20d05a049ee166c39626cf875e 2096 aseba_1.6.0-3.dsc
 b359060c08055e543e3125010893bddae6e16020 12500 aseba_1.6.0-3.debian.tar.xz
 2398b16cb78456cca86af99ba5f2bba9f89312f1 16956384 
aseba-dbgsym_1.6.0-3_amd64.deb
 9d042302dede90310edcdfb3219200a7723c3995 14759 aseba_1.6.0-3_amd64.buildinfo
 71b7df1557efcea802fd59418ae74cfa134f83ca 6104692 aseba_1.6.0-3_amd64.deb
Checksums-Sha256:
 156f963cc43f0b17d8e8a32bf1e57c8200dbdb9ec086a26109d9442e5150438a 2096 
aseba_1.6.0-3.dsc
 8013c3e1bf63b0dbf74cc8df49d5bd1393c9ddaa6054b8fe9b157d71a6b3 12500 
aseba_1.6.0-3.debian.tar.xz
 aef2144d6f22f078fb506f0cfadd484cd4e8d58b3fd1219567643874dc3896f9 16956384 
aseba-dbgsym_1.6.0-3_amd64.deb
 bbe9896e1280eb2350c08a7a905f5eb17790b00c118153781dad2be450ed18be 14759 
aseba_1.6.0-3_amd64.buildinfo
 3a8168a4ba52e68c60047a0b934fa5c451ded8ceff2d5d41e28730b845c79e16 6104692 
aseba_1.6.0-3_amd64.deb
Files:
 3ee876452b485e058ec18948b46b40bb 2096 devel optional aseba_1.6.0-3.dsc
 e942774e740ec5a63d3694fbedc33299 12500 devel optional 
aseba_1.6.0-3.debian.tar.xz
 d6841f49a0b8a7c5debaf1777db1aae3 16956384 debug optional 
aseba-dbgsym_1.6.0-3_amd64.deb
 16e5e1cb93f83079ffbb22ae932b 14759 devel optional 
aseba_1.6.0-3_amd64.buildinfo
 eb21ea1a1869cd51a967282892c5f067 6104692 devel optional aseba_1.6.0-3_amd64.deb

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEEM0CzZP9nFT+3zK6FHCgWkHE2rjkFAlrLNx4ACgkQHCgWkHE2
rjl9TQ//cJ3gjPfnte0OI4X7kQmTUpkxqApbpKUCqq+3xk+pvJMMEl4JLF3J6Ecz
A0gJKudk6xuJlobKT9VIkBbygeCmV/2Ax+XatB7aF9fpVr7VRB3PAfHOsGIUpMN/
6FKE0q+5iIPM4nZzWAzbSXhNPJNXxD4wn57EXYrc7JmcLGMFItePPBfaRD2dO9F0
yV85L+vUYQR6Kz3jHWeAF/k0+b+GeTAhWHemirW/j3IfzF/OXerLG+62ekGZxXA2
w5hXQosMz/kokYpsdgD72mxCNx6NM5HyVcDZ8RIcpr6iQszorKTRYBdVkrthwsCT
xr3X0WY6q03+l+rCEa562iEkJFn/P6tOp+M+UwT+iL00FI/Kr1DcQRMHTKVRtwW6
yUZvHltjCmTyJWcJdzDhnH6QwMuMoF75k5/AaiCHA+xie0qfabRocHsqGtQVypfM
TgQnxh53l21p+x11ArmyeMVdDnUbc+triILgZxXvUMk+M40QQGNEguwPjuKURFKK
WsSrChu3Yia+jWuwhuP7lPNPLtqS6duLyxUOVnyXEroVulhRHBYZ9n+BDgMw+1db
MFBlfNaUR9rRdj+vz1KZdOp9yTWYP3iNvGmE6i1++RkSoH6NUzZvjkHB9kiDfHKm
y05zJH2BR1tyrVRmPDwzNYhzZ6oibW9VRDeCa0s78rQpYRczWmA=
=CdEW
-END PGP SIGNATURE End Message ---

Bug#895282: trac-authopenid: fails to work with trac 1.2 (get_db_cnx does not work)

[Daniel Kahn Gillmor]

Package: trac-authopenid
Version: 0.4.7-1
Severity: grave
Tags: patch
Justification: renders package unusable

on debian stretch and later, trac is version 1.2.  but trac-authopenid
0.4.7-1 uses get_db_cnx(), which was deprecated in trac 0.12 and
removed in trac 1.1.

As a result, if trac-authopenid is installed and configured for a trac
environment, that environment will fail to load at all.

see https://trac.edgewall.org/wiki/TracDev/ApiChanges/1.1#DatabaseAPIChanges

the attached patch appears to fix the worst errors, but hasn't been
well-tested.

--dkg


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

Kernel: Linux 4.15.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 trac-authopenid depends on:
ii  python 2.7.14-4
ii  python-openid  2.2.5-6
ii  trac   1.2.2+dfsg-1

trac-authopenid recommends no packages.

trac-authopenid suggests no packages.

-- no debconf information
From: Daniel Kahn Gillmor 
Date: Mon, 9 Apr 2018 07:30:15 -0400
Subject: move from get_db_cnx() to context manager

See
https://trac.edgewall.org/wiki/TracDev/ApiChanges/1.1#DatabaseAPIChanges
for more details about this migration.
---
 authopenid/authopenid.py | 660 +++
 1 file changed, 330 insertions(+), 330 deletions(-)

diff --git a/authopenid/authopenid.py b/authopenid/authopenid.py
index da98b19..112c175 100644
--- a/authopenid/authopenid.py
+++ b/authopenid/authopenid.py
@@ -227,7 +227,6 @@ class AuthOpenIdPlugin(Component):
 return generated_list
 
 def __init__(self):
-db = self.env.get_db_cnx()
 oidutil.log = OpenIdLogger(self.env)
 self.env.log.debug("Compiling white-list")
 self.re_white_list = self.generate_re_list(self.white_list)
@@ -264,9 +263,9 @@ class AuthOpenIdPlugin(Component):
 # IEnvironmentSetupParticipant methods
 
 def environment_created(self):
-db = self.env.get_db_cnx()
-self._initStore(db)
-db.commit()
+with self.env.db_transaction as db:
+self._initStore(db)
+db.commit()
 
 def environment_needs_upgrade(self, db):
 c = db.cursor()
@@ -414,36 +413,18 @@ class AuthOpenIdPlugin(Component):
 
 immediate = 'immediate' in req.args
 
-db = self.env.get_db_cnx()
-oidconsumer, oidsession = self._get_consumer(req, db)
-try:
-self.env.log.debug('beginning OpenID authentication.')
-request = oidconsumer.begin(openid_url)
-except consumer.DiscoveryFailure, exc:
-fetch_error_string = 'Error in discovery: %s' % (
-cgi.escape(str(exc[0])))
-return 'openidlogin.html', {
-'images': req.href.chrome('authopenid/images') + '/',
-'action': req.href.openidverify(),
-'message': fetch_error_string,
-'signup': self.signup_link,
-'whatis': self.whatis_link,
-'css_class': 'error',
-'providers_regexp': self.providers_regexp,
-'custom_provider_name': self.custom_provider_name,
-'custom_provider_label': self.custom_provider_label,
-'custom_provider_url': self.custom_provider_url,
-'custom_provider_image': self.custom_provider_image,
-'custom_provider_size': self.custom_provider_size,
-}, None
-else:
-if request is None:
-msg = 'No OpenID services found for %s' % (
-cgi.escape(openid_url),)
+with self.env.db_transaction as db:
+oidconsumer, oidsession = self._get_consumer(req, db)
+try:
+self.env.log.debug('beginning OpenID authentication.')
+request = oidconsumer.begin(openid_url)
+except consumer.DiscoveryFailure, exc:
+fetch_error_string = 'Error in discovery: %s' % (
+cgi.escape(str(exc[0])))
 return 'openidlogin.html', {
 'images': req.href.chrome('authopenid/images') + '/',
 'action': req.href.openidverify(),
-'message': msg,
+'message': fetch_error_string,
 'signup': self.signup_link,
 'whatis': self.whatis_link,
 'css_class': 'error',
@@ -453,25 +434,43 @@ class AuthOpenIdPlugin(Component):
 'custom_provider_url': self.custom_provider_url,
  

Bug#894359: Help needed to port beast2-mcmc to Java 9

[Andreas Tille]

On Fri, Apr 06, 2018 at 01:50:39PM +0200, Emmanuel Bourg wrote:
> Le 06/04/2018 à 13:45, Andreas Tille a écrit :
> 
> > [javac] error: package org.fest.util does not exist
> 
> fest-util.jar?

Better, but not solved:


...
compile-all:
 [echo] Building BEAST 2
[mkdir] Created dir: /build/beast2-mcmc-2.4.8+dfsg/build
[javac] Compiling 468 source files to /build/beast2-mcmc-2.4.8+dfsg/build
[javac] warning: [options] bootstrap class path not set in conjunction with 
-source 1.8
[javac] 
/build/beast2-mcmc-2.4.8+dfsg/src/beast/util/XMLParserUtils.java:25: warning: 
CoreDocumentImpl is internal proprietary API and may be removed in a future 
release
[javac] import com.sun.org.apache.xerces.internal.dom.CoreDocumentImpl;
[javac]  ^
[javac] 
/build/beast2-mcmc-2.4.8+dfsg/src/beast/util/XMLParserUtils.java:120: warning: 
CoreDocumentImpl is internal proprietary API and may be removed in a future 
release
[javac] ((CoreDocumentImpl) doc).putIdentifier(id, 
(Element) node);
[javac]   ^
[javac] /build/beast2-mcmc-2.4.8+dfsg/src/beast/util/TreeParser.java:353: 
error: cannot find symbol
[javac] CharStream charStream = CharStreams.fromString(newick);
[javac] ^
[javac]   symbol:   variable CharStreams
[javac]   location: class TreeParser
[javac] 
/build/beast2-mcmc-2.4.8+dfsg/src/beast/util/treeparser/NewickLexer.java:98: 
error: method does not override or implement a method from a supertype
[javac] @Override
[javac] ^
[javac] Note: Some input files use or override a deprecated API.
[javac] Note: Recompile with -Xlint:deprecation for details.
[javac] Note: Some input files use unchecked or unsafe operations.
[javac] Note: Recompile with -Xlint:unchecked for details.
[javac] 2 errors
[javac] 3 warnings

BUILD FAILED
/build/beast2-mcmc-2.4.8+dfsg/build.xml:77: Compile failed; see the compiler 
error output for details.
...


Thanks anyway

   Andreas.
 

-- 
http://fam-tille.de

Bug#851774: [Bug 1754075] Re: apt-setup uses apt-key but probably should not anymore

[Lars Kollstedt]

On Monday, 9 April 2018 12:56:12 CEST Lars Kollstedt wrote:
[...]
> This patch should IMHO work, but I have no opportunity to test it without
> your help, since we're in udeb and testing preseed issues. ;-)

Hi again,

20 times looked at it and still overlooked one detail.

This must of course be 'echo "$comment"'.

Kind regards,
Lars

-- 
Lars Kollstedt

Telefon: +49 6151 16-71027
E-Mail:  l...@man-da.de

man-da.de GmbH
Dolivostraße 11
64293 Darmstadt

Sitz der man-da.de GmbH: Darmstadt
Amtsgericht Darmstadt, HRB 9484
Geschäftsführer: Andreas Ebert
diff -rupNw apt-setup-0.104ubuntu5.orig/generators/60local apt-setup-0.104ubuntu5.fixed/generators/60local
--- apt-setup-0.104ubuntu5.orig/generators/60local	2016-06-08 19:08:12.0 +0200
+++ apt-setup-0.104ubuntu5.fixed/generators/60local	2018-04-09 13:11:08.347671088 +0200
@@ -35,8 +35,17 @@ while db_get "apt-setup/local$i/reposito
 		while :; do
 			if fetch-url "$key" "$ROOT/tmp/key$i.pub"; then
 # add it to the keyring
-$chroot $ROOT apt-key add "/tmp/key$i.pub"
-rm -f "$ROOT/tmp/key$i.pub"
+if [ -n "$comment" ]; then
+	name=$(echo "$comment" | sed -E 's/[^0-9A-Za-z]+/_/g')
+else
+	name="apt-setup_local$i"
+fi
+if grep -q -- '-BEGIN PGP PUBLIC KEY BLOCK-' $ROOT/tmp/key$i.pub 
+	then
+	mv "$ROOT/tmp/key$i.pub" "$ROOT/etc/apt/trusted.gpg.d/$name.asc"
+else
+	mv "$ROOT/tmp/key$i.pub" "$ROOT/etc/apt/trusted.gpg.d/$name.gpg"
+fi
 break
 			else
 db_subst apt-setup/local/key-error MIRROR "${repository%% *}"

Bug#851774: [Bug 1754075] Re: apt-setup uses apt-key but probably should not anymore

[Lars Kollstedt]

Hi,

by the way apt-key belongs to the package apt:

root@bionic-test:/home/kollstedt# apt-file search apt-key   
   
[...]
apt: /usr/bin/apt-key
[...]

It is installed when the error occurs and is exitting with the error mentioned 
above.



But there is indeed another way to add the public key without using "apt-key 
add".
 
They can simply be copied to /etc/apt/trusted.gpg.d, with the ending *.gpg if 
it's binary format. With the ending *.asc for ASCII-amored format.

Please find a patch attached that use this way to add instead of the old way 
with apt-key.


The two following Debian Bugs for this lead me tho this:

https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=851774

https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=886473

I also sent this message to the first one I considered to be the main one. 


For the ones reading the debian bug, this was mainly send to 

https://bugs.launchpad.net/ubuntu/+source/gnupg/+bug/1754075

Since this also found it's way to Ubunut 18.4 bionic (unreleased LTS).


But there is some (more or less) usefull disscussion but as far as I can see 
no patch, yet. So I prepared one. Thanks to Marga Manterola and Philipp Kern 
for the idea.

One of the most important errors in stuff discussed there is IMHO the lack of 
"-- " which is necessary to prevent grep from interpreding the leading --. I 
also decided not to filter for things that are not relevant. Since comments 
describing the Publickey or it's origin might be placed above the -BEGIN 
PGP PUBLIC KEY BLOCK- (without hitting gpgv), and we would not be able to 
prevent all possible syntax evil here, without having gpg to import and export 
the public key to and from a temporary keyring.
I'm also trying to assign a useful name to the key added this way. 

This patch should IMHO work, but I have no opportunity to test it without your 
help, since we're in udeb and testing preseed issues. ;-)

Kind regards,
Lars

-- 
Lars Kollstedt

Telefon: +49 6151 16-71027
E-Mail:  l...@man-da.de

man-da.de GmbH
Dolivostraße 11
64293 Darmstadt

Sitz der man-da.de GmbH: Darmstadt
Amtsgericht Darmstadt, HRB 9484
Geschäftsführer: Andreas Ebert
diff -rupNw apt-setup-0.104ubuntu5.orig/generators/60local apt-setup-0.104ubuntu5.fixed/generators/60local
--- apt-setup-0.104ubuntu5.orig/generators/60local	2016-06-08 19:08:12.0 +0200
+++ apt-setup-0.104ubuntu5.fixed/generators/60local	2018-04-09 12:25:59.535772146 +0200
@@ -35,8 +35,17 @@ while db_get "apt-setup/local$i/reposito
 		while :; do
 			if fetch-url "$key" "$ROOT/tmp/key$i.pub"; then
 # add it to the keyring
-$chroot $ROOT apt-key add "/tmp/key$i.pub"
-rm -f "$ROOT/tmp/key$i.pub"
+if [ -n "$comment" ]; then
+	name=$(echo "" | sed -E 's/[^0-9A-Za-z]+/_/g')
+else
+	name="apt-setup_local$i"
+fi
+if grep -q -- '-BEGIN PGP PUBLIC KEY BLOCK-' $ROOT/tmp/key$i.pub 
+	then
+	mv "$ROOT/tmp/key$i.pub" "$ROOT/etc/apt/trusted.gpg.d/$name.asc"
+else
+	mv "$ROOT/tmp/key$i.pub" "$ROOT/etc/apt/trusted.gpg.d/$name.gpg"
+fi
 break
 			else
 db_subst apt-setup/local/key-error MIRROR "${repository%% *}"

Bug#895120: marked as done (openstack-proxy-node: depends on ceilometer-api, ceilometer-collector which are no longer built)

[Debian Bug Tracking System]

Your message dated Mon, 09 Apr 2018 11:00:15 +
with message-id 
and subject line Bug#895120: fixed in openstack-meta-packages 0.21
has caused the Debian Bug report #895120,
regarding openstack-proxy-node: depends on ceilometer-api, ceilometer-collector 
which are no longer built
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.)


-- 
895120: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=895120
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: openstack-proxy-node
Version: 0.20
Severity: serious

ceilometer-api and ceilometer-collector are no longer built by ceilometer. Thus
you should stop depending on them.

Emilio
--- End Message ---
--- Begin Message ---
Source: openstack-meta-packages
Source-Version: 0.21

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

Debian distribution maintenance software
pp.
Thomas Goirand  (supplier of updated openstack-meta-packages 
package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Wed, 07 Mar 2018 22:35:40 +0100
Source: openstack-meta-packages
Binary: openstack-clients openstack-cloud-identity openstack-cloud-services 
openstack-compute-node openstack-deploy openstack-proxy-node 
openstack-puppet-modules openstack-tempest-ci openstack-tempest-ci-live-booter 
openstack-toaster
Architecture: source all
Version: 0.21
Distribution: unstable
Urgency: medium
Maintainer: Debian OpenStack 
Changed-By: Thomas Goirand 
Description:
 openstack-clients - Metapackage to install all Openstack clients
 openstack-cloud-identity - Metapackage to install an Openstack keystone
 openstack-cloud-services - Metapackage to install all Openstack service 
dependencies
 openstack-compute-node - Metapackage to install an Openstack compute node
 openstack-deploy - Tools to deploy OpenStack
 openstack-proxy-node - Metapackage to install an Openstack proxy node
 openstack-puppet-modules - Metapackage to install all OpenStack puppet modules
 openstack-tempest-ci - validate OpenStack Debian packages using tempest and 
openstack-de
 openstack-tempest-ci-live-booter - configures a server to boot a custom live 
image to test OpenStack
 openstack-toaster - Metapackage to install all of Openstack services at once
Closes: 895120
Changes:
 openstack-meta-packages (0.21) unstable; urgency=medium
 .
   [ Ondřej Nový ]
   * d/control: Set Vcs-* to salsa.debian.org
   * Running wrap-and-sort -bast
 .
   [ Thomas Goirand ]
   * Fixed preseed-lib to work with the new style of debconf templates from
 openstack-pkg-tools >= 70~.
   * Removed ceilometer-api and heat-api-cloudwatch from depends, as these don't
 exist anymore.
   * Added more dependencies in openstack-clients, and switch to using Python 3
 version of clients.
   * Also remove ceilometer-collector from depends, also gone upstream.
 (Closes: #895120)
   * Add a new openstack-puppet-modules metapackage.
Checksums-Sha1:
 c83c0a877671921a437de49b228fdf76ad3e5b7b 2418 openstack-meta-packages_0.21.dsc
 d4e472960c223341cab21a8d6818dee50f7f9685 49392 
openstack-meta-packages_0.21.tar.xz
 f57b7a1e6e817ec6619fdd32e8e694ba4413a4bd 5100 openstack-clients_0.21_all.deb
 7a72337e891375d6365ac48202fc665212af6668 4904 
openstack-cloud-identity_0.21_all.deb
 d692e5885d0ec555c065d601fd5a2c8aa08c7d74 4936 
openstack-cloud-services_0.21_all.deb
 8bccb387712ab522b0ad72b5019c5f0022470955 4956 
openstack-compute-node_0.21_all.deb
 2dfa00d8cc58ad7ce8bfb8395aedef978051e27f 41560 openstack-deploy_0.21_all.deb
 6c9605fde3af4567a1e95f3b3fcd625ae0088eb2 8206 
openstack-meta-packages_0.21_amd64.buildinfo
 58eac4746bc48e53545c0cbddc1785d8a4d03143 5100 openstack-proxy-node_0.21_all.deb
 135bd6555f0744ea654f1755e84c0d08b0332d5c 5072 
openstack-puppet-modules_0.21_all.deb
 8146aaf02f7198f93fcbdc6f6d9d0ea460901b1e 9532 
openstack-tempest-ci-live-booter_0.21_all.deb
 10a4628c8804e8c35ba0cdc0a35c8e768dceda32 11628 

Bug#895014: marked as done (gcc-6-cross-ports cannot properly be built and uploaded for arch:all)

[Debian Bug Tracking System]

Your message dated Mon, 09 Apr 2018 10:01:08 +
with message-id 
and subject line Bug#895014: fixed in gcc-6-cross-ports 28
has caused the Debian Bug report #895014,
regarding gcc-6-cross-ports cannot properly be built and uploaded for arch:all
to be marked as done.

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

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


-- 
895014: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=895014
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: gcc-6-cross-ports
Version: 27
Severity: serious

The arch:all autobuilder built gcc-6-cross-ports twice and it was twice
rejected by the archive (build logs: [1], [2]). The rejection rationale
is as follows:

 Package lib64gfortran3-powerpc-cross is not mentioned in Binary field
in changes

Which seems to be true.

Kind regards
Philipp Kern

[1]
https://buildd.debian.org/status/fetch.php?pkg=gcc-6-cross-ports=all=27=1521635505=0
[2]
https://buildd.debian.org/status/fetch.php?pkg=gcc-6-cross-ports=all=27=1522939979=0
--- End Message ---
--- Begin Message ---
Source: gcc-6-cross-ports
Source-Version: 28

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

Debian distribution maintenance software
pp.
Matthias Klose  (supplier of updated gcc-6-cross-ports package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Sat, 07 Apr 2018 11:45:55 +0200
Source: gcc-6-cross-ports
Binary: gcc-6-cross-base-ports gcc-6-alpha-linux-gnu-base 
libgcc-6-dev-alpha-cross gcc-6-alpha-linux-gnu gcc-6-plugin-dev-alpha-linux-gnu 
cpp-6-alpha-linux-gnu g++-6-alpha-linux-gnu gobjc++-6-alpha-linux-gnu 
gobjc-6-alpha-linux-gnu libobjc-6-dev-alpha-cross gfortran-6-alpha-linux-gnu 
libgfortran3-alpha-cross libgfortran-6-dev-alpha-cross gccgo-6-alpha-linux-gnu 
libgo9-alpha-cross libstdc++-6-dev-alpha-cross libstdc++-6-pic-alpha-cross 
gdc-6-alpha-linux-gnu gnat-6-alpha-linux-gnu gnat-6-sjlj-alpha-linux-gnu 
libgnat-6-alpha-cross libgnatvsn6-dev-alpha-cross libgnatvsn6-alpha-cross 
libgnatprj6-dev-alpha-cross libgnatprj6-alpha-cross gcc-6-hppa-linux-gnu-base 
libgcc-6-dev-hppa-cross gcc-6-hppa-linux-gnu gcc-6-plugin-dev-hppa-linux-gnu 
cpp-6-hppa-linux-gnu g++-6-hppa-linux-gnu gobjc++-6-hppa-linux-gnu 
gobjc-6-hppa-linux-gnu libobjc-6-dev-hppa-cross gfortran-6-hppa-linux-gnu 
libgfortran3-hppa-cross libgfortran-6-dev-hppa-cross libstdc++-6-dev-hppa-cross 
libstdc++-6-pic-hppa-cross
 gdc-6-hppa-linux-gnu gnat-6-hppa-linux-gnu gnat-6-sjlj-hppa-linux-gnu 
libgnat-6-hppa-cross libgnatvsn6-dev-hppa-cross libgnatvsn6-hppa-cross 
libgnatprj6-dev-hppa-cross libgnatprj6-hppa-cross gcc-6-m68k-linux-gnu-base 
libgcc-6-dev-m68k-cross gcc-6-m68k-linux-gnu gcc-6-plugin-dev-m68k-linux-gnu 
cpp-6-m68k-linux-gnu g++-6-m68k-linux-gnu gobjc++-6-m68k-linux-gnu 
gobjc-6-m68k-linux-gnu libobjc-6-dev-m68k-cross gfortran-6-m68k-linux-gnu 
libgfortran3-m68k-cross libgfortran-6-dev-m68k-cross gccgo-6-m68k-linux-gnu 
libgo9-m68k-cross libstdc++-6-dev-m68k-cross libstdc++-6-pic-m68k-cross 
gdc-6-m68k-linux-gnu gcc-6-mips64-linux-gnuabi64-base libgcc-6-dev-mips64-cross 
lib32gcc-6-dev-mips64-cross libn32gcc-6-dev-mips64-cross 
gcc-6-mips64-linux-gnuabi64 gcc-6-multilib-mips64-linux-gnuabi64 
gcc-6-plugin-dev-mips64-linux-gnuabi64 cpp-6-mips64-linux-gnuabi64 
g++-6-mips64-linux-gnuabi64 g++-6-multilib-mips64-linux-gnuabi64 
gobjc++-6-mips64-linux-gnuabi64
 gobjc++-6-multilib-mips64-linux-gnuabi64 gobjc-6-mips64-linux-gnuabi64 
gobjc-6-multilib-mips64-linux-gnuabi64 libobjc-6-dev-mips64-cross 
lib32objc-6-dev-mips64-cross libn32objc-6-dev-mips64-cross 
gfortran-6-mips64-linux-gnuabi64 gfortran-6-multilib-mips64-linux-gnuabi64 
libgfortran3-mips64-cross libgfortran-6-dev-mips64-cross 
lib32gfortran3-mips64-cross lib32gfortran-6-dev-mips64-cross 
libn32gfortran3-mips64-cross libn32gfortran-6-dev-mips64-cross 
gccgo-6-mips64-linux-gnuabi64 gccgo-6-multilib-mips64-linux-gnuabi64 
libgo9-mips64-cross lib32go9-mips64-cross libn32go9-mips64-cross 
libstdc++-6-dev-mips64-cross libstdc++-6-pic-mips64-cross 

Bug#892404: marked as done (thunderbird: build-depends on GCC 6)

[Debian Bug Tracking System]

Your message dated Mon, 09 Apr 2018 10:01:45 +
with message-id 
and subject line Bug#892404: fixed in thunderbird 1:60.0~b2-1
has caused the Debian Bug report #892404,
regarding thunderbird: build-depends on GCC 6
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.)


-- 
892404: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=892404
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: thunderbird
Severity: serious
Tags: sid buster
User: debian-...@lists.debian.org
Usertags: gcc-6-rm

Hi,

thunderbird build-depends on GCC 6. We now have GCC 7 (default) and
GCC 8 in the archive, so please make your package build with a newer
compiler (preferably the default one) again, since we'd like to
remove GCC 6 from testing before the buster release.

Cheers, Emilio 
--- End Message ---
--- Begin Message ---
Source: thunderbird
Source-Version: 1:60.0~b2-1

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

Debian distribution maintenance software
pp.
Carsten Schoenert  (supplier of updated thunderbird 
package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Sat, 07 Apr 2018 11:12:37 +0200
Source: thunderbird
Binary: thunderbird lightning calendar-google-provider thunderbird-l10n-all 
thunderbird-l10n-ar thunderbird-l10n-ast thunderbird-l10n-be 
thunderbird-l10n-bg thunderbird-l10n-br thunderbird-l10n-ca thunderbird-l10n-cs 
thunderbird-l10n-da thunderbird-l10n-de thunderbird-l10n-dsb 
thunderbird-l10n-el thunderbird-l10n-en-gb thunderbird-l10n-es-ar 
thunderbird-l10n-es-es thunderbird-l10n-et thunderbird-l10n-eu 
thunderbird-l10n-fi thunderbird-l10n-fr thunderbird-l10n-fy-nl 
thunderbird-l10n-ga-ie thunderbird-l10n-gd thunderbird-l10n-gl 
thunderbird-l10n-he thunderbird-l10n-hr thunderbird-l10n-hsb 
thunderbird-l10n-hu thunderbird-l10n-hy-am thunderbird-l10n-id 
thunderbird-l10n-is thunderbird-l10n-it thunderbird-l10n-ja 
thunderbird-l10n-kab thunderbird-l10n-kk thunderbird-l10n-ko 
thunderbird-l10n-lt thunderbird-l10n-ms thunderbird-l10n-nb-no 
thunderbird-l10n-nl thunderbird-l10n-nn-no thunderbird-l10n-pl 
thunderbird-l10n-pt-br thunderbird-l10n-pt-pt thunderbird-l10n-rm
 thunderbird-l10n-ro thunderbird-l10n-ru thunderbird-l10n-si 
thunderbird-l10n-sk thunderbird-l10n-sl thunderbird-l10n-sq thunderbird-l10n-sr 
thunderbird-l10n-sv-se thunderbird-l10n-tr thunderbird-l10n-uk 
thunderbird-l10n-vi thunderbird-l10n-zh-cn thunderbird-l10n-zh-tw 
lightning-l10n-ar lightning-l10n-ast lightning-l10n-be lightning-l10n-bg 
lightning-l10n-br lightning-l10n-ca lightning-l10n-cs lightning-l10n-cy 
lightning-l10n-da lightning-l10n-de lightning-l10n-dsb lightning-l10n-el 
lightning-l10n-es-ar lightning-l10n-es-es lightning-l10n-en-gb 
lightning-l10n-et lightning-l10n-eu lightning-l10n-fi lightning-l10n-fr 
lightning-l10n-fy-nl lightning-l10n-ga-ie lightning-l10n-gd lightning-l10n-gl 
lightning-l10n-he lightning-l10n-hr lightning-l10n-hsb lightning-l10n-hu 
lightning-l10n-hy-am lightning-l10n-id lightning-l10n-is lightning-l10n-it 
lightning-l10n-ja lightning-l10n-kab lightning-l10n-kk lightning-l10n-ko 
lightning-l10n-ms lightning-l10n-lt lightning-l10n-nb-no
 lightning-l10n-nl lightning-l10n-nn-no lightning-l10n-pl lightning-l10n-pt-br 
lightning-l10n-pt-pt lightning-l10n-rm lightning-l10n-ro lightning-l10n-ru 
lightning-l10n-si lightning-l10n-sk lightning-l10n-sl lightning-l10n-sr 
lightning-l10n-sq lightning-l10n-sv-se lightning-l10n-tr lightning-l10n-uk 
lightning-l10n-vi lightning-l10n-zh-cn
 lightning-l10n-zh-tw
Architecture: source all amd64
Version: 1:60.0~b2-1
Distribution: experimental
Urgency: medium
Maintainer: Carsten Schoenert 
Changed-By: Carsten Schoenert 
Description:
 calendar-google-provider - Google Calendar support for lightning
 lightning  - Calendar Extension for Thunderbird
 lightning-l10n-ar - Arabic language package for lightning
 lightning-l10n-ast - Asturian language package for lightning
 

Bug#876826: marked as done (postgresql-hll FTBFS with PostgreSQL 10)

[Debian Bug Tracking System]

Your message dated Mon, 09 Apr 2018 10:01:32 +
with message-id 
and subject line Bug#876826: fixed in postgresql-hll 2.10.2-1
has caused the Debian Bug report #876826,
regarding postgresql-hll FTBFS with PostgreSQL 10
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.)


-- 
876826: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=876826
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: postgresql-hll
Version: 2.7-2.1
Severity: serious
Tags: buster sid

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

...
/usr/bin/make PG_CONFIG=pg_config
make[2]: Entering directory '/build/1st/postgresql-hll-2.7'
gcc -Wall -Wmissing-prototypes -Wpointer-arith -Wdeclaration-after-statement 
-Wendif-labels -Wmissing-format-attribute -Wformat-security 
-fno-strict-aliasing -fwrapv -fexcess-precision=standard -g -g -O2 
-fdebug-prefix-map=/build/postgresql-10-ccxnXW/postgresql-10-10~rc1=. 
-fstack-protector-strong -Wformat -Werror=format-security 
-fno-omit-frame-pointer -fPIC -fPIC -std=c99 -I. -I./ 
-I/usr/include/postgresql/10/server -I/usr/include/postgresql/internal  
-Wdate-time -D_FORTIFY_SOURCE=2 -D_GNU_SOURCE -I/usr/include/libxml2  
-I/usr/include/mit-krb5  -c -o hll.o hll.c
In file included from /usr/include/postgresql/10/server/funcapi.h:19:0,
 from hll.c:19:
hll.c: In function 'hll_in':
hll.c:1444:36: error: 'byteain' undeclared (first use in this function); did 
you mean 'bytea'?
 Datum dd = DirectFunctionCall1(byteain, PG_GETARG_DATUM(0));
^
/usr/include/postgresql/10/server/fmgr.h:585:26: note: in definition of macro 
'DirectFunctionCall1'
  DirectFunctionCall1Coll(func, InvalidOid, arg1)
  ^~~~
hll.c:1444:36: note: each undeclared identifier is reported only once for each 
function it appears in
 Datum dd = DirectFunctionCall1(byteain, PG_GETARG_DATUM(0));
^
/usr/include/postgresql/10/server/fmgr.h:585:26: note: in definition of macro 
'DirectFunctionCall1'
  DirectFunctionCall1Coll(func, InvalidOid, arg1)
  ^~~~
hll.c: In function 'hll_out':
hll.c:1486:36: error: 'byteaout' undeclared (first use in this function); did 
you mean 'bytea'?
 Datum dd = DirectFunctionCall1(byteaout, PG_GETARG_DATUM(0));
^
/usr/include/postgresql/10/server/fmgr.h:585:26: note: in definition of macro 
'DirectFunctionCall1'
  DirectFunctionCall1Coll(func, InvalidOid, arg1)
  ^~~~
hll.c: In function 'hll_hashval_in':
hll.c:1533:36: error: 'int8in' undeclared (first use in this function); did you 
mean 'int8'?
 Datum dd = DirectFunctionCall1(int8in, PG_GETARG_DATUM(0));
^
/usr/include/postgresql/10/server/fmgr.h:585:26: note: in definition of macro 
'DirectFunctionCall1'
  DirectFunctionCall1Coll(func, InvalidOid, arg1)
  ^~~~
hll.c: In function 'hll_hashval_out':
hll.c:1542:36: error: 'int8out' undeclared (first use in this function); did 
you mean 'int8_t'?
 Datum dd = DirectFunctionCall1(int8out, PG_GETARG_DATUM(0));
^
/usr/include/postgresql/10/server/fmgr.h:585:26: note: in definition of macro 
'DirectFunctionCall1'
  DirectFunctionCall1Coll(func, InvalidOid, arg1)
  ^~~~
hll.c: In function 'hll_type':
hll.c:2223:13: warning: variable 'vers' set but not used 
[-Wunused-but-set-variable]
 uint8_t vers;
 ^~~~
hll.c: In function 'hll_log2m':
hll.c:2244:13: warning: variable 'vers' set but not used 
[-Wunused-but-set-variable]
 uint8_t vers;
 ^~~~
hll.c: In function 'hll_regwidth':
hll.c:2265:13: warning: variable 'vers' set but not used 
[-Wunused-but-set-variable]
 uint8_t vers;
 ^~~~
hll.c: In function 'hll_expthresh':
hll.c:2286:13: warning: variable 'vers' set but not used 
[-Wunused-but-set-variable]
 uint8_t vers;
 ^~~~
hll.c: In function 'hll_sparseon':
hll.c:2346:13: warning: variable 'vers' set but not used 
[-Wunused-but-set-variable]
 uint8_t vers;
 ^~~~
: recipe for target 'hll.o' failed
make[2]: *** [hll.o] Error 1
--- End Message ---
--- Begin Message ---
Source: postgresql-hll
Source-Version: 2.10.2-1

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

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

Processed: Re: Bug#895276: Acknowledgement (lldpd.service: mkdir fails if directory already exists)

[Debian Bug Tracking System]

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

> severity 895276 minor
Bug #895276 [liblldpctl-dev] lldpd.service: mkdir fails if directory already 
exists
Severity set to 'minor' from 'serious'
> thanks
Stopping processing here.

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

Bug#895276: Acknowledgement (lldpd.service: mkdir fails if directory already exists)

[Laurent Bigonville]

severity 895276 minor
thanks

Well, apparently mkdir -p doesn't fail if the directory already exits 
(only mkdir does), downgrading the severity of this bug.


Still, using RuntimeDirectory= is de prefered ways of creating such 
directories.

Bug#895276: lldpd.service: mkdir fails if directory already exists

[Laurent Bigonville]

Package: liblldpctl-dev
Version: 0.9.6-1
Severity: serious

Hi,

The .systemd file does a mkdir that fails if the directory already
exists.

I would suggest to use RuntimeDirectory= instead (in conjunction with
RuntimeDirectoryPreserve= if the data need to survive the restart of the
daemon).

Kind regards,

Laurent Bigonville

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

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

Versions of packages liblldpctl-dev depends on:
pn  lldpd  

liblldpctl-dev recommends no packages.

liblldpctl-dev suggests no packages.

Bug#888831: ok on on jessie and wheezy

[Bernie Elbourn]

This is hitting apt-listbugs in stable releases nearly woke me up :-)

Jessie shows;-

$ apt-cache policy firefox-esr
firefox-esr:
  Installed: 52.7.3esr-1~deb8u1
  Candidate: 52.7.3esr-1~deb8u1
  Version table:
 *** 52.7.3esr-1~deb8u1 0
    500 http://security.debian.org/ jessie/updates/main amd64 Packages
    100 /var/lib/dpkg/status
 52.5.0esr-1~deb8u1 0
    500 http://ftp.uk.debian.org/debian/ jessie/main amd64 Packages

$ apt-cache policy libnss3
libnss3:
  Installed: 2:3.26-1+debu8u3
  Candidate: 2:3.26-1+debu8u3
  Version table:
 *** 2:3.26-1+debu8u3 0
    500 http://ftp.uk.debian.org/debian/ jessie/main amd64 Packages
    500 http://security.debian.org/ jessie/updates/main amd64 Packages
    100 /var/lib/dpkg/status

Wheezy

$ apt-cache policy firefox-esr
firefox-esr:
  Installed: 52.7.3esr-1~deb7u1
  Candidate: 52.7.3esr-1~deb7u1
  Version table:
 *** 52.7.3esr-1~deb7u1 0
    500 http://security.debian.org/ wheezy/updates/main amd64 Packages
    100 /var/lib/dpkg/status

$ apt-cache policy libnss3
libnss3:
  Installed: 2:3.26-1+debu7u5
  Candidate: 2:3.26-1+debu7u5
  Version table:
 *** 2:3.26-1+debu7u5 0
    500 http://security.debian.org/ wheezy/updates/main amd64 Packages
    100 /var/lib/dpkg/status
 2:3.14.5-1+deb7u5 0
    500 http://ftp.uk.debian.org/debian/ wheezy/main amd64 Packages

This combo seems ok. I can open debign bugs, facebook, google ok.

Bug#895271: konqueror: crahses while running programms which try to start it

[Friedrich Dominicus]

Package: konqueror
Version: 4:17.08.3-2
Severity: critical
Tags: upstream
Justification: breaks unrelated software

Dear Maintainer,

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

trying to run
stack haddock --open lens

I get immediate a crash:

Application: Konqueror (kdeinit5), signal: Aborted
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
[Current thread is 1 (Thread 0x7f0185b09780 (LWP 29858))]

Thread 18 (Thread 0x7f010700 (LWP 29877)):
#0  0x7f0176653273 in pa_mainloop_dispatch () at /usr/lib/x86_64-linux-
gnu/libpulse.so.0
#1  0x7f01766536ce in pa_mainloop_iterate () at /usr/lib/x86_64-linux-
gnu/libpulse.so.0
#2  0x7f0176653750 in pa_mainloop_run () at /usr/lib/x86_64-linux-
gnu/libpulse.so.0
#3  0x7f01766615b9 in  () at /usr/lib/x86_64-linux-gnu/libpulse.so.0
#4  0x7f01761fbc78 in  () at /usr/lib/x86_64-linux-
gnu/pulseaudio/libpulsecommon-11.1.so
#5  0x7f018208e5aa in start_thread (arg=0x7f010700) at
pthread_create.c:463
#6  0x7f0183c0fcbf in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:95

Thread 17 (Thread 0x7f011cff9700 (LWP 29876)):
#0  0x7f018209481a in futex_reltimed_wait_cancelable (private=, reltime=0x7f011cff89d0, expected=0, futex_word=0x7f011cff8b58) at
../sysdeps/unix/sysv/linux/futex-internal.h:142
#1  0x7f018209481a in __pthread_cond_wait_common (abstime=0x7f011cff8a70,
mutex=0x7f011cff8b08, cond=0x7f011cff8b30) at pthread_cond_wait.c:533
#2  0x7f018209481a in __pthread_cond_timedwait (cond=0x7f011cff8b30,
mutex=0x7f011cff8b08, abstime=0x7f011cff8a70) at pthread_cond_wait.c:667
#3  0x7f0155318552 in  () at /usr/lib/x86_64-linux-
gnu/libQt5WebEngineCore.so.5
#4  0x7f01552df82e in  () at /usr/lib/x86_64-linux-
gnu/libQt5WebEngineCore.so.5
#5  0x7f01552ba4bb in  () at /usr/lib/x86_64-linux-
gnu/libQt5WebEngineCore.so.5
#6  0x7f01552b6d38 in  () at /usr/lib/x86_64-linux-
gnu/libQt5WebEngineCore.so.5
#7  0x7f01552d370b in  () at /usr/lib/x86_64-linux-
gnu/libQt5WebEngineCore.so.5
#8  0x7f01552eb3e6 in  () at /usr/lib/x86_64-linux-
gnu/libQt5WebEngineCore.so.5
#9  0x7f01552e74fb in  () at /usr/lib/x86_64-linux-
gnu/libQt5WebEngineCore.so.5
#10 0x7f018208e5aa in start_thread (arg=0x7f011cff9700) at
pthread_create.c:463
#11 0x7f0183c0fcbf in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:95

Thread 16 (Thread 0x7f011d7fa700 (LWP 29875)):
#0  0x7f01820944ec in futex_wait_cancelable (private=,
expected=0, futex_word=0x557ac74c25b8) at ../sysdeps/unix/sysv/linux/futex-
internal.h:88
#1  0x7f01820944ec in __pthread_cond_wait_common (abstime=0x0,
mutex=0x557ac74c24f8, cond=0x557ac74c2590) at pthread_cond_wait.c:502
#2  0x7f01820944ec in __pthread_cond_wait (cond=0x557ac74c2590,
mutex=0x557ac74c24f8) at pthread_cond_wait.c:655
#3  0x7f0155a6f8b0 in  () at /usr/lib/x86_64-linux-
gnu/libQt5WebEngineCore.so.5
#4  0x7f01552eae21 in  () at /usr/lib/x86_64-linux-
gnu/libQt5WebEngineCore.so.5
#5  0x7f01552e74fb in  () at /usr/lib/x86_64-linux-
gnu/libQt5WebEngineCore.so.5
#6  0x7f018208e5aa in start_thread (arg=0x7f011d7fa700) at
pthread_create.c:463
#7  0x7f0183c0fcbf in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:95

Thread 15 (Thread 0x7f011dffb700 (LWP 29874)):
#0  0x7f01820944ec in futex_wait_cancelable (private=,
expected=0, futex_word=0x7f011dffab38) at ../sysdeps/unix/sysv/linux/futex-
internal.h:88
#1  0x7f01820944ec in __pthread_cond_wait_common (abstime=0x0,
mutex=0x7f011dffaae8, cond=0x7f011dffab10) at pthread_cond_wait.c:502
#2  0x7f01820944ec in __pthread_cond_wait (cond=0x7f011dffab10,
mutex=0x7f011dffaae8) at pthread_cond_wait.c:655
#3  0x7f01552df8a9 in  () at /usr/lib/x86_64-linux-
gnu/libQt5WebEngineCore.so.5
#4  0x7f01552df8d7 in  () at /usr/lib/x86_64-linux-
gnu/libQt5WebEngineCore.so.5
#5  0x7f01552ba46b in  () at /usr/lib/x86_64-linux-
gnu/libQt5WebEngineCore.so.5
#6  0x7f01552b6d38 in  () at /usr/lib/x86_64-linux-
gnu/libQt5WebEngineCore.so.5
#7  0x7f01552d370b in  () at /usr/lib/x86_64-linux-
gnu/libQt5WebEngineCore.so.5
#8  0x7f01552eb3e6 in  () at /usr/lib/x86_64-linux-
gnu/libQt5WebEngineCore.so.5
#9  0x7f01552e74fb in  () at /usr/lib/x86_64-linux-
gnu/libQt5WebEngineCore.so.5
#10 0x7f018208e5aa in start_thread (arg=0x7f011dffb700) at
pthread_create.c:463
#11 0x7f0183c0fcbf in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:95

Thread 14 (Thread 0x7f011e7fc700 (LWP 29873)):
#0  0x7f01820944ec in futex_wait_cancelable (private=,
expected=0, futex_word=0x557ac74b1328) at ../sysdeps/unix/sysv/linux/futex-
internal.h:88
#1  0x7f01820944ec in __pthread_cond_wait_common (abstime=0x0,
mutex=0x557ac74b12d8, 

Bug#893577: sbuild-debian-developer-setup: Should not rely on files in /usr/share/doc

[Johannes Schauer]

Quoting Michael Stapelberg (2018-04-09 09:21:46)
> josch, could you let me know whether the attached patch does what you have
> in mind please? Thanks!

Yes, that looks good.

cheers, josch


signature.asc
Description: signature

Bug#893577: sbuild-debian-developer-setup: Should not rely on files in /usr/share/doc

[Michael Stapelberg]

josch, could you let me know whether the attached patch does what you have
in mind please? Thanks!

On Tue, Mar 27, 2018 at 2:47 PM, Johannes Schauer  wrote:

> Hi all,
>
> > At the end of the script, it runs
> >
> > symlink("/usr/share/doc/sbuild/examples/sbuild-update-all",
> "/etc/cron.daily/sbuild-debian-developer-setup-update-all");
> >
> > which requires the file in /usr/share/doc to be present. Policy 12.3
> says that
> > packages can't do that and says that such files should be in
> > /usr/share/package with a symlink into /usr/share/doc/package/ as
> > appropriate.
>
> probably the right thing to do would be to let the
> sbuild-debian-developer-setup package directly install sbuild-update-all
> into
> /etc/cron.daily/sbuild-debian-developer-setup-update-all. If necessary,
> sbuild-update-all has to be adapted such that it will not barf if the user
> has
> not yet run sbuild-debian-developer-setup.
>
> This would mean that the same copy of sbuild-update-all would potentially
> exist
> twice on a system, but I don't think that's much of a problem.
>
> Michael, can you take care of this?
>
> Thanks!
>
> cheers, josch
>



-- 
Best regards,
Michael
diff --git i/debian/rules w/debian/rules
index bc15c043..b1bfe785 100755
--- i/debian/rules
+++ w/debian/rules
@@ -3,5 +3,10 @@
 %:
 	dh $@
 
+override_dh_install:
+	cp etc/sbuild-update-all etc/sbuild-debian-developer-setup-update-all
+	chmod +x etc/sbuild-debian-developer-setup-update-all
+	dh_install
+
 override_dh_installinit:
 	dh_installinit --no-start --no-restart-on-upgrade
diff --git i/debian/sbuild-debian-developer-setup.install w/debian/sbuild-debian-developer-setup.install
index 406b3af9..6d2a1699 100644
--- i/debian/sbuild-debian-developer-setup.install
+++ w/debian/sbuild-debian-developer-setup.install
@@ -1 +1,2 @@
 usr/bin/sbuild-debian-developer-setup
+etc/sbuild-debian-developer-setup-update-all etc/cron.daily
diff --git i/etc/sbuild-update-all w/etc/sbuild-update-all
index 12a394cb..3e22d05a 100644
--- i/etc/sbuild-update-all
+++ w/etc/sbuild-update-all
@@ -76,7 +76,7 @@ exec 1>&8
 if ! ls /etc/schroot/chroot.d/$PATTERN >/dev/null 2>&1
 then
 	echo "No chroots defined"
-	break
+	exit 0
 fi
 
 for fullname in /etc/schroot/chroot.d/$PATTERN