Bug#917128: Bug

[Martin Pitt]

Control: found -1  241-1

Wolfgang Walter [2019-02-23 11:39 +0100]:
> The bug is back again: 241-1 again has this problem.

So this broke again due to https://github.com/systemd/systemd/commit/3907446f02
or https://github.com/systemd/systemd/commit/73d2bb08816 , i. e. as part of
https://github.com/systemd/systemd/pull/11449 .

The logging should now be improved with v241, particularly which policy was
applied. Do you have a chance to get a journal log (journalctl -b) from such a
broken boot?

Thanks,

Martin

Bug#923104: h5py: autopkgtest regression

[Graham Inggs]

Source: h5py
Version: 2.9.0-1
Severity: serious
X-Debbugs-CC: debian...@lists.debian.org
User: debian...@lists.debian.org
Usertags: regression

Hi Maintainer

Since the upload of 2.9.0-1, h5py has been failing its own
autopkgtests [1] with the following error:

Testing with python3.7:
...s...xxs/usr/lib/python3/dist-packages/h5py/_hl/files.py:258:
H5pyDeprecationWarning: File.fid has been deprecated. Use File.id
instead.
  "Use File.id instead.", H5pyDeprecationWarning)
...s..ss...ss.xx.x..x..
--
Ran 509 tests in 1.578s

OK (skipped=15, expected failures=6)
Testing with python3.7-dbg:
...

..python3.7-dbg: /build/h5py-bLiaZi/h5py-2.9.0/h5py/h5fd.c:19007:
__Pyx_PyCFunction_FastCall: Assertion `!PyErr_Occurred()' failed.
bash: line 1:  1153 Aborted $py-dbg -c "import h5py;
h5py.run_tests()"
autopkgtest [16:54:50]: test command2: ---]
autopkgtest [16:54:50]: test command2:  - - - - - - - - - - results -
- - - - - - - - -
command2 FAIL non-zero exit status 134

Regards
Graham


[1] https://ci.debian.net/packages/h/h5py/unstable/amd64/

Bug#922306: linux: btrfs corruption (compressed data + hole data)

[Salvatore Bonaccorso]

Control: found -1 4.3~rc5-1~exp1
Control: tags -1 + upstream patch

Upstream patch submission at
https://lore.kernel.org/linux-btrfs/20190214151720.23563-1-fdman...@kernel.org/

Regards,
Salvatore

Bug#923105: holdingnuts FTCBFS: constructs a wrong builddirectory and fails to install

[Helmut Grohne]

Source: holdingnuts
Version: 0.0.5-4
Tags: patch
User: helm...@debian.org
Usertags: rebootstrap

holdingnuts fails to cross build from source, because it wrongly
constructs dh's builddirectory and thus fails installing from a
non-existent directory. The attached patch fixes that and makes
holdingnuts cross buildable. Please consider applying it.

Helmut
diff --minimal -Nru holdingnuts-0.0.5/debian/changelog 
holdingnuts-0.0.5/debian/changelog
--- holdingnuts-0.0.5/debian/changelog  2012-02-23 13:23:05.0 +0100
+++ holdingnuts-0.0.5/debian/changelog  2019-02-24 09:35:50.0 +0100
@@ -1,3 +1,10 @@
+holdingnuts (0.0.5-4.1) UNRELEASED; urgency=medium
+
+  * Non-maintainer upload.
+  * Fix FTCBFS: Correctly construct dh's builddirectory. (Closes: #-1)
+
+ -- Helmut Grohne   Sun, 24 Feb 2019 09:35:50 +0100
+
 holdingnuts (0.0.5-4) unstable; urgency=low
 
   * [92a4358b] Migrated from subversion to git on collab-maint
diff --minimal -Nru holdingnuts-0.0.5/debian/rules 
holdingnuts-0.0.5/debian/rules
--- holdingnuts-0.0.5/debian/rules  2012-02-23 13:16:43.0 +0100
+++ holdingnuts-0.0.5/debian/rules  2019-02-24 09:35:49.0 +0100
@@ -7,7 +7,8 @@
 export DEB_LDFLAGS_MAINT_APPEND = -Wl,--as-needed -Wl,-z,defs
 
 # builddirectory constructed by dh
-BDIR = "obj-$(shell dpkg-architecture -qDEB_BUILD_GNU_TYPE)"
+include /usr/share/dpkg/architecture.mk
+BDIR = "obj-$(DEB_HOST_GNU_TYPE)"
 
 %:
dh $@ --parallel

Bug#923106: pgn2web FTCBFS: hard codes wrong compiler

[Helmut Grohne]

Source: pgn2web
Version: 0.4-2
Tags: upstream patch
User: helm...@debian.org
Usertags: rebootstrap

pgn2web fails to cross build from source, because the upstream Makefile
hard codes the build architecture C++ compiler in one place. After
changing that to $(CXX), pgn2web cross builds successfully. Please
consider applying the attached patch.

Helmut
--- pgn2web-0.4.orig/makefile
+++ pgn2web-0.4/makefile
@@ -8,7 +8,7 @@
 	$(CC) $(CPPFLAGS) $(CFLAGS) -c cli.c
 
 gui.o : gui.cpp gui.h pgn2web.h
-	g++ $(CPPFLAGS) $(CXXFLAGS) -c gui.cpp `wx-config --cxxflags`
+	$(CXX) $(CPPFLAGS) $(CXXFLAGS) -c gui.cpp `wx-config --cxxflags`
 
 pgn2web.o: pgn2web.c pgn2web.h chess.h nag.h
 	$(CC) $(CPPFLAGS) $(CFLAGS) -c pgn2web.c

Bug#923107: regexxer FTCBFS: configures twice, once for the build architecture

[Helmut Grohne]

Source: regexxer
Version: 0.10-4
Tags: patch
User: helm...@debian.org
Usertags: rebootstrap

regexxer fails to cross build from source, because it configures for the
build architecture. It actually configures twice. Once for the build
architecture during ./autogen.sh and then correctly through
dh_auto_configure. Skipping the first configuration makes cross building
work as well as speeding up the build. Please consider applying the
attached patch.

Helmut
diff --minimal -Nru regexxer-0.10/debian/changelog 
regexxer-0.10/debian/changelog
--- regexxer-0.10/debian/changelog  2018-10-13 18:51:31.0 +0200
+++ regexxer-0.10/debian/changelog  2019-02-24 09:55:54.0 +0100
@@ -1,3 +1,9 @@
+regexxer (0.10-5) UNRELEASED; urgency=medium
+
+  * Fix FTCBFS: Don't configure twice. (Closes: #-1)
+
+ -- Helmut Grohne   Sun, 24 Feb 2019 09:55:54 +0100
+
 regexxer (0.10-4) unstable; urgency=medium
 
   * QA upload.
diff --minimal -Nru regexxer-0.10/debian/rules regexxer-0.10/debian/rules
--- regexxer-0.10/debian/rules  2018-10-13 17:54:25.0 +0200
+++ regexxer-0.10/debian/rules  2019-02-24 09:55:53.0 +0100
@@ -7,4 +7,4 @@
dh $@
 
 override_dh_autoreconf:
-   dh_autoreconf ./autogen.sh
+   NOCONFIGURE=1 dh_autoreconf ./autogen.sh

Bug#923108: eiciel FTCBFS: hard codes pkg-config in configure.ac once

[Helmut Grohne]

Source: eiciel
Version: 0.9.12.1-1
Tags: patch upstream
User: helm...@debian.org
Usertags: rebootstrap

eiciel fails to cross build from source, because its configure.ac hard
codes the build architecture pkg-config in one place. After fixing that,
it cross builds successfully. Please consider applying the attached
patch.

Helmut
--- eiciel-0.9.12.1.orig/configure.ac
+++ eiciel-0.9.12.1/configure.ac
@@ -108,7 +108,7 @@
 ]
 ,
 [dnl Linux distributions
-  extensiondir=`pkg-config --variable=extensiondir libnautilus-extension`;
+  extensiondir=`$PKG_CONFIG --variable=extensiondir libnautilus-extension`;
   if test -n "$extensiondir" ;
   then
  AC_SUBST(NAUTILUS_EXTENSIONS_DIR, [$extensiondir])

Bug#831835: "Survey regarding your Extension bcma for Mozilla Firefox"

[outgoingmail]

If this is not a spam and you are serious, please repost it to
https://notabug.org/themusicgod1/cloudflare-tor/

thanks

Bug#923109: qmidiroute FTCBFS: abuses AC_CHECK_FILE

[Helmut Grohne]

Source: qmidiroute
Version: 0.4.0-1
Tags: patch upstream
User: helm...@debian.org
Usertags: rebootstrap

qmidiroute fails to cross build from source, because it abuses
AC_CHECK_FILE. The macro is meant for testing file existence on the
installed system. However, qmidiroute uses it for checking header
directories used during build. For the latter, a simple "test -e" is
better. The attached patch implements that and makes qmidiroute cross
buildable. Please consider applying it.

Helmut
--- qmidiroute-0.4.0.orig/configure.ac
+++ qmidiroute-0.4.0/configure.ac
@@ -31,9 +31,9 @@ if test "x$HAVE_QT4" = "xyes"; then
   QT_INCLUDE_DIR=`$PKG_CONFIG --variable=includedir QtGui`
   QT_CXXFLAGS=`$PKG_CONFIG --cflags QtCore QtGui QtOpenGL`
   EXTRA_QT_INCLUDE_DIR="$QT_INCLUDE_DIR/Qt"
-  AC_CHECK_FILE([$QT_INCLUDE_DIR/QWidget],
+  AS_IF([test -e "$QT_INCLUDE_DIR/QWidget"],
 AC_MSG_NOTICE([No extra QT_INCLUDE_DIR needed]),
-  AC_CHECK_FILE([$EXTRA_QT_INCLUDE_DIR/QWidget],
+  AS_IF([test -e "$EXTRA_QT_INCLUDE_DIR/QWidget"],
 QT_CPPFLAGS="$QT_CPPFLAGS -I$EXTRA_QT_INCLUDE_DIR",
   AC_MSG_WARN([QWidget not found])))
 
@@ -61,9 +61,9 @@ if test "x$HAVE_QT5" = "xyes"; then
   QT_CXXFLAGS=`$PKG_CONFIG --cflags Qt5Core Qt5Gui Qt5OpenGL Qt5Widgets`
   QT_CXXFLAGS="$QT_CXXFLAGS -fPIC"
   EXTRA_QT_INCLUDE_DIR="$QT_INCLUDE_DIR/Qt"
-  AC_CHECK_FILE([$QT_INCLUDE_DIR/QtWidgets/QWidget],
+  AS_IF([test -e "$QT_INCLUDE_DIR/QtWidgets/QWidget"],
 AC_MSG_NOTICE([No extra QT_INCLUDE_DIR needed]),
-  AC_CHECK_FILE([$EXTRA_QT_INCLUDE_DIR/QtWidgets/QWidget],
+  AS_IF([test -e "$EXTRA_QT_INCLUDE_DIR/QtWidgets/QWidget"],
 QT_CPPFLAGS="$QT_CPPFLAGS -I$EXTRA_QT_INCLUDE_DIR",
   AC_MSG_WARN([QWidget not found])))
 

Bug#923110: ksmtuned FTCBFS: debian/rules hard codes the wrong compiler

[Helmut Grohne]

Source: ksmtuned
Version: 4.20150325
Tags: patch
User: helm...@debian.org
Usertags: rebootstrap

ksmtuned fails to cross build from source, because debian/rules hard
codes the build architecture compiler. Seeding CC from dpkg's
buildtools.mk fixes that. Please consider applying the attached patch.

Helmut
diff --minimal -Nru ksmtuned-4.20150325/debian/changelog 
ksmtuned-4.20150325+nmu1/debian/changelog
--- ksmtuned-4.20150325/debian/changelog2015-03-25 21:22:49.0 
+0100
+++ ksmtuned-4.20150325+nmu1/debian/changelog   2019-02-24 10:29:07.0 
+0100
@@ -1,3 +1,10 @@
+ksmtuned (4.20150325+nmu1) UNRELEASED; urgency=medium
+
+  * Non-maintainer upload.
+  * Fix FTCBFS: Let dpkg's buildtools.mk supply the compiler. (Closes: #-1)
+
+ -- Helmut Grohne   Sun, 24 Feb 2019 10:29:07 +0100
+
 ksmtuned (4.20150325) unstable; urgency=medium
 
   * [176bc5ab] Merge branch 'master' of github.com:bzed/debian-ksmtuned
diff --minimal -Nru ksmtuned-4.20150325/debian/rules 
ksmtuned-4.20150325+nmu1/debian/rules
--- ksmtuned-4.20150325/debian/rules2015-03-25 21:22:49.0 +0100
+++ ksmtuned-4.20150325+nmu1/debian/rules   2019-02-24 10:29:06.0 
+0100
@@ -1,5 +1,6 @@
 #!/usr/bin/make -f
 
+-include /usr/share/dpkg/buildtools.mk
 CPPFLAGS:=$(shell dpkg-buildflags --get CPPFLAGS)
 CFLAGS:=$(shell dpkg-buildflags --get CFLAGS) $(CPPFLAGS)
 LDFLAGS:=$(shell dpkg-buildflags --get LDFLAGS)
@@ -8,7 +9,7 @@
dh $@ --with systemd
 
 ksmctl: ksmctl.c
-   gcc $< -O2 -g $(CPPFLAGS) $(CFLAGS) $(LDFLAGS) -o $@
+   $(CC) $< -O2 -g $(CPPFLAGS) $(CFLAGS) $(LDFLAGS) -o $@
 
 build-arch:  ksmctl
dh $@ --with systemd

Bug#923112: gnujump FTCBFS: does not pass --host to ./configure

[Helmut Grohne]

Source: gnujump
Version: 1.0.8-3
Tags: patch
User: helm...@debian.org
Usertags: rebootstrap

gnujump fails to cross build from source, because it does not pass
--host to ./configure. The easiest way of fixing that - using
dh_auto_configure - makes gnujump cross buildable. Please consider
applying the attached patch.

Helmut
diff --minimal -Nru gnujump-1.0.8/debian/changelog 
gnujump-1.0.8/debian/changelog
--- gnujump-1.0.8/debian/changelog  2015-08-16 18:13:24.0 +0200
+++ gnujump-1.0.8/debian/changelog  2019-02-24 10:32:02.0 +0100
@@ -1,3 +1,10 @@
+gnujump (1.0.8-3.1) UNRELEASED; urgency=medium
+
+  * Non-maintainer upload.
+  * Fix FTCBFS: Let dh_auto_configure pass --host to ./configure. (Closes: #-1)
+
+ -- Helmut Grohne   Sun, 24 Feb 2019 10:32:02 +0100
+
 gnujump (1.0.8-3) unstable; urgency=medium
 
   [ Paul Wise ]
diff --minimal -Nru gnujump-1.0.8/debian/rules gnujump-1.0.8/debian/rules
--- gnujump-1.0.8/debian/rules  2015-08-16 13:21:00.0 +0200
+++ gnujump-1.0.8/debian/rules  2019-02-24 10:32:01.0 +0100
@@ -7,7 +7,7 @@
dh $@ --with autoreconf
 
 override_dh_auto_configure:
-   ./configure --prefix=/usr --bindir=/usr/games --datadir=/usr/share/games
+   dh_auto_configure -- --bindir=/usr/games --datadir=/usr/share/games
 
 override_dh_auto_build:
dh_auto_build

Bug#923111: [INTL:da] Danish translation of the debconf templates openafs

[Joe Dalton]

Package: openafs
Severity: wishlist
Tags: l10n patch

Please include the attached Danish openafs debconf po file.

joe@debianbuster:~/over/debian/openafs$ msgfmt --statistics -c -v -o /dev/null 
da.po
da.po: 25 oversatte tekster.

bye
Joe

da.po.tar.gz
Description: application/gzip

Bug#923113: [INTL:da] Danish translation of the debconf templates distcc

[Joe Dalton]

Package: distcc
Severity: wishlist
Tags: l10n patch

Please include the attached Danish distcc debconf po file.

joe@debianbuster:~/over/debian/distcc$ msgfmt --statistics -c -v -o /dev/null 
da.po
da.po: 20 oversatte tekster.

bye
Joe

da.po.tar.gz
Description: application/gzip

Bug#923115: cups-client: cupsctl needs to edit `cups-files.conf`

[Paul Menzel]

Package: cups-client
Version: 2.2.10-4
Severity: normal

Dear Maintainer,


`/usr/sbin/cupsctl FileDevice=No` edits `/etc/cups/cupsd.conf` instead 
of `/etc/cups/cups-files.conf`.


```
/etc$ /usr/sbin/cupsctl FileDevices=No
/etc$ sudo git diff
diff --git a/cups/cupsd.conf b/cups/cupsd.conf
index 02afed2..c347852 100644
--- a/cups/cupsd.conf
+++ b/cups/cupsd.conf
@@ -119,3 +119,4 @@ WebInterface Yes
 Order deny,allow
   
 
+FileDevice Yes
```


Kind regards,

Paul

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

Kernel: Linux 4.20.0-trunk-amd64 (SMP w/4 CPU cores)
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8), 
LANGUAGE=de_DE.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 cups-client depends on:
ii  adduser3.118
ii  cups-common2.2.10-4
ii  libc6  2.28-7
ii  libcups2   2.2.10-4
ii  libcupsimage2  2.2.10-4

cups-client recommends no packages.

Versions of packages cups-client suggests:
ii  cups   2.2.10-4
ii  cups-bsd   2.2.10-4
ii  smbclient  2:4.9.4+dfsg-3

-- no debconf information

Bug#923114: netdata-plugins-bash: sends usage stats to google without consent

[Thomas Krutz]

Package: netdata-plugins-bash
Version: 1.12.0-1
Severity: normal

Dear Maintainer,

i never expected something like this in a debian package.
/usr/lib/netdata/plugins.d/anonymous-statistics.sh sends infos about my system 
to google analytics.

please delete this script or at least make it opt-in.

br

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

Kernel: Linux 4.19.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 /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages netdata-plugins-bash depends on:
ii  bash  5.0-2
ii  netdata-core  1.12.0-1

netdata-plugins-bash recommends no packages.

Versions of packages netdata-plugins-bash suggests:
ii  fping  4.1-1

-- no debconf information

Bug#923116: colorcode FTCBFS: builds for the build architecture

[Helmut Grohne]

Source: colorcode
Version: 0.8.5-1
Tags: patch
User: helm...@debian.org
Usertags: rebootstrap

colorcode fails to cross build from source, because it does not pass the
relevant cross flags to qmake. The easiest way of doing so is running
dh_auto_configure. For doing that, we need to get rid of the qtchooser
wrapping (e.g. by exporting QT_SELECT). Then running lrelease requires a
build dependency on qt5-qmake:native. The attached patch makes colorcode
cross buildable. Please consider applying it.

Helmut
diff --minimal -Nru colorcode-0.8.5/debian/changelog 
colorcode-0.8.5/debian/changelog
--- colorcode-0.8.5/debian/changelog2015-10-20 20:42:06.0 +0200
+++ colorcode-0.8.5/debian/changelog2019-02-24 10:37:41.0 +0100
@@ -1,3 +1,13 @@
+colorcode (0.8.5-1.1) UNRELEASED; urgency=medium
+
+  * Non-maintainer upload.
+  * Fix FTCBFS: (Closes: #-1)
++ Use QT_SELECT to select qt and avoid running qtchooser directly.
++ Let dh_auto_configure run qmake with appropriate flags.
++ Build-Depends qt5-qmake:native for running lrelease.
+
+ -- Helmut Grohne   Sun, 24 Feb 2019 10:37:41 +0100
+
 colorcode (0.8.5-1) unstable; urgency=medium
 
   * New upstream release with the Qt5 port done by the usptream author
diff --minimal -Nru colorcode-0.8.5/debian/control 
colorcode-0.8.5/debian/control
--- colorcode-0.8.5/debian/control  2015-10-20 20:42:06.0 +0200
+++ colorcode-0.8.5/debian/control  2019-02-24 10:37:38.0 +0100
@@ -4,6 +4,7 @@
 Maintainer: Filippo Rusconi 
 Build-Depends: debhelper (>= 9),
dpkg-dev (>= 1.16.1~),
+   qt5-qmake:native,
qtbase5-dev (>= 5.3.2+dfsg-5),
qttools5-dev-tools (>= 5.3.2+dfsg-5),
quilt (>= 0.63)
diff --minimal -Nru colorcode-0.8.5/debian/rules colorcode-0.8.5/debian/rules
--- colorcode-0.8.5/debian/rules2015-10-20 20:42:06.0 +0200
+++ colorcode-0.8.5/debian/rules2019-02-24 10:37:25.0 +0100
@@ -3,10 +3,7 @@
 
 # Uncomment this to turn on verbose mode.
 export DH_VERBOSE=1
-
-DEB_HOST_GNU_TYPE   ?= $(shell dpkg-architecture -qDEB_HOST_GNU_TYPE)
-DEB_BUILD_GNU_TYPE  ?= $(shell dpkg-architecture -qDEB_BUILD_GNU_TYPE)
-
+export QT_SELECT=qt5
 
 PACKAGE=colorcode
 
@@ -45,10 +42,10 @@
 # that lrelease is in libqt4-dev and we have to depend on that package
 # anyways. So no overhead.
 
-   qtchooser -qt=qt5 -run-tool=qmake -o Makefile colorcode.pro
+   dh_auto_configure
 
 # Production of .qm file is required before the call to qmake.
-   qtchooser -qt=qt5 -run-tool=lrelease -compress colorcode.pro
+   lrelease -compress colorcode.pro
 
 
touch configure-stamp

Bug#923117: cups-client: Install printer admin programs in `/usr/bin`

[Paul Menzel]

Package: cups-client
Version: 2.2.10-4
Severity: normal

Dear Maintainer,


`/usr/sbin` does not seem to be in the user PATH by default in Debian. 
Users in the group *lpadmin* are allowed to use the printer commands, so 
they should be installed in `/usr/bin`. (Unrelated, I heard, that `sbin` 
originally is for statically linked binaries and not for “admin programs”.)


Could you please install the executables below into `/usr/bin`?

```
$ dpkg -L cups-client | grep sbin/
/usr/sbin/cupsaccept
/usr/sbin/cupsaddsmb
/usr/sbin/cupsctl
/usr/sbin/lpadmin
/usr/sbin/lpinfo
/usr/sbin/lpmove
/usr/sbin/accept
/usr/sbin/cupsdisable
/usr/sbin/cupsenable
/usr/sbin/cupsreject
/usr/sbin/reject
```


Kind regards,

Paul

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

Kernel: Linux 4.20.0-trunk-amd64 (SMP w/4 CPU cores)
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8), 
LANGUAGE=de_DE.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 cups-client depends on:
ii  adduser3.118
ii  cups-common2.2.10-4
ii  libc6  2.28-7
ii  libcups2   2.2.10-4
ii  libcupsimage2  2.2.10-4

cups-client recommends no packages.

Versions of packages cups-client suggests:
ii  cups   2.2.10-4
ii  cups-bsd   2.2.10-4
ii  smbclient  2:4.9.4+dfsg-3

-- no debconf information

Bug#923118: OpenJDK 12 symlink to sources doesn't point on src.zip

[Andriy Lutskiv]

Package: openjdk-12-jdk
Version: 12~32-1


After installation OpenJDK 12(openjdk-12-jdk) and it's sources
(openjdk-12-source)  in directory /usr/lib/jvm/java-1.12.0-openjdk-amd64
symlink to sources doesn't point on src.zip.
It link unexisted /usr/lib/jvm/openjdk-12/src.zip, but src.zip is in
/usr/lib/jvm/openjdk-12/lib

I suggest that the link should point on /usr/lib/jvm/openjdk-12/lib/src.zip

I am using Debian GNU/Linux buster/sid

This is very small detail. Thank you for your work!

Bug#923119: [INTL:da] Danish translation of the debconf template ejabberd

[Joe Dalton]

Package: ejabberd
Severity: wishlist
Tags: l10n patch

Please include the attached Danish ejabberd debconf po file.

joe@debianbuster:~/over/debian/ejabberd$ msgfmt --statistics -c -v -o /dev/null 
da.po
da.po: 26 oversatte tekster.

bye
Joe

da.po.tar.gz
Description: application/gzip

Bug#923120: clustalx FTCBFS: builds for the build architecture

[Helmut Grohne]

Source: clustalx
Version: 2.1+lgpl-7
Tags: patch
User: helm...@debian.org
Usertags: rebootstrap

clustalx fails to cross build from source, because it does not pass
cross flags to qmake. The easiest way of doing so - using
dh_auto_configure - makes clustalx cross buildable. Please consider
applying the attached patch.

Helmut
diff --minimal -Nru clustalx-2.1+lgpl/debian/changelog 
clustalx-2.1+lgpl/debian/changelog
--- clustalx-2.1+lgpl/debian/changelog  2018-09-25 13:02:11.0 +0200
+++ clustalx-2.1+lgpl/debian/changelog  2019-02-24 10:50:56.0 +0100
@@ -1,3 +1,10 @@
+clustalx (2.1+lgpl-7.1) UNRELEASED; urgency=medium
+
+  * Non-maintainer upload.
+  * Fix FTCBFS: Let dh_auto_configure pass cross flags to qmake. (Closes: #-1)
+
+ -- Helmut Grohne   Sun, 24 Feb 2019 10:50:56 +0100
+
 clustalx (2.1+lgpl-7) unstable; urgency=medium
 
   * Drop redundant debian/README.source
diff --minimal -Nru clustalx-2.1+lgpl/debian/rules 
clustalx-2.1+lgpl/debian/rules
--- clustalx-2.1+lgpl/debian/rules  2018-09-25 13:02:11.0 +0200
+++ clustalx-2.1+lgpl/debian/rules  2019-02-24 10:50:54.0 +0100
@@ -8,7 +8,7 @@
dh $@
 
 override_dh_auto_configure:
-   qmake
+   dh_auto_configure
# did not found a better way to push hardening flags into Makefile
sed -i -e "s:CFLAGS *= .*:& $(CFLAGS):" \
   -e "s:CXXFLAGS *= .*:& $(CXXFLAGS):" \

Bug#923121: [INTL:da] Danish translation of the debconf template nova

[Joe Dalton]

Package: nova
Severity: wishlist
Tags: l10n patch

Please include the attached Danish nova debconf po file.

joe@debianbuster:~/over/debian/nova$ msgfmt --statistics -c -v -o /dev/null 
da.po
da.po: 38 oversatte tekster.

bye
Joe

da.po.tar.gz
Description: application/gzip

Bug#921761: sssd: FTBFS (failing tests)

[Dominik George]

On Sun, Feb 24, 2019 at 12:35:02AM +0100, Dominik George wrote:
> Fedora project seems to know how to fix this, but I cannot get my head
> wrapped around how the hell you find out how they did it…
> 
>  https://bugzilla.redhat.com/show_bug.cgi?id=1645912
> 
> -nik

The fix referenced in the RedHat bug tracker in krb5 is unrelated to
this bug and does not fix it.


signature.asc
Description: PGP signature

Bug#923122: nsnake: make the build verbose

[Helmut Grohne]

Source: nsnake
Version: 3.0.1-2
Tags: patch
User: helm...@debian.org
Usertags: rebootstrap

nsnake fails to cross build from source, but diagnosing why is next to
impossible without a verbose build log. Please make the build verbose by
default as is recommended by Debian policy section 4.9. The attached
patch implements that. Please consider applying it.

Helmut
diff --minimal -Nru nsnake-3.0.1/debian/changelog nsnake-3.0.1/debian/changelog
--- nsnake-3.0.1/debian/changelog   2014-08-14 00:55:57.0 +0200
+++ nsnake-3.0.1/debian/changelog   2019-02-24 11:03:39.0 +0100
@@ -1,3 +1,10 @@
+nsnake (3.0.1-2.1) UNRELEASED; urgency=medium
+
+  * Non-maintainer upload.
+  * Make the build verbose by default. (Closes: #-1)
+
+ -- Helmut Grohne   Sun, 24 Feb 2019 11:03:39 +0100
+
 nsnake (3.0.1-2) unstable; urgency=medium
 
   * Updated maintainer mail address
diff --minimal -Nru nsnake-3.0.1/debian/rules nsnake-3.0.1/debian/rules
--- nsnake-3.0.1/debian/rules   2014-08-12 20:54:28.0 +0200
+++ nsnake-3.0.1/debian/rules   2019-02-24 11:03:37.0 +0100
@@ -4,3 +4,8 @@
 
 %:
dh $@ --parallel
+
+ifeq (,$(filter terse,$(DEB_BUILD_OPTIONS)))
+override_dh_auto_build:
+   dh_auto_build -- V=1
+endif

Bug#923123: [INTL:da] Danish translation of the debconf template clamsmtp

[Joe Dalton]

Package: clamsmtp
Severity: wishlist
Tags: l10n patch

Please include the attached Danish clamsmtp debconf po file.

joe@debianbuster:~/over/debian/clamsmtp$ msgfmt --statistics -c -v -o /dev/null 
da.po
da.po: 8 oversatte tekster.

bye
Joe

da.po.tar.gz
Description: application/gzip

Bug#923124: bidiv FTCBFS: upstream Makefile hard codes build architecture pkg-config

[Helmut Grohne]

Source: bidiv
Version: 1.5-6
Tags: patch upstream
User: helm...@debian.org
Usertags: rebootstrap

bidiv fails to cross build from source, because the upstream Makefile
hard codes the build architecture pkg-config. The attached patch makes
pkg-config substitutable and that is sufficient to make bidiv cross
buildable as dh_auto_build substitutes pkg-config. Please consider
applying it.

Helmut
--- bidiv-1.5.orig/Makefile
+++ bidiv-1.5/Makefile
@@ -2,10 +2,11 @@
 BIN_DIR=$(PREFIX)/bin
 MAN_PATH=$(PREFIX)/share/man
 CC_OPT_FLAGS=-O2 -Wall
+PKG_CONFIG ?= pkg-config
 
 
-PKG_CFLAGS= $(CC_OPT_FLAGS) $(DEFS) `pkg-config --cflags fribidi`
-PKG_LDFLAGS=`pkg-config --libs fribidi`
+PKG_CFLAGS= $(CC_OPT_FLAGS) $(DEFS) `$(PKG_CONFIG) --cflags fribidi`
+PKG_LDFLAGS=`$(PKG_CONFIG) --libs fribidi`
 
 all: bidiv
 

Bug#923125: FTBFS: cannot find files in override_dh_install

[Dominik George]

Source: sssd
Version: 1.16.3-3
Severity: serious
Tags: ftbfs
Justification: fails to build from source (but built successfully in the past)

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512


After fixing #921761, sssd still fails to build in a clean chroot:

dh_install
dh_install: Cannot find (any matches for) 
"usr/lib/*/krb5/plugins/authdata/sssd_pac_plugin.so" (tried in ., debian/tmp)

dh_install: sssd-common missing files: 
usr/lib/*/krb5/plugins/authdata/sssd_pac_plugin.so
dh_install: Cannot find (any matches for) "usr/lib/*/sssd/sssd_pac" (tried in 
., debian/tmp)

dh_install: sssd-ad-common missing files: usr/lib/*/sssd/sssd_pac
dh_install: missing files, aborting
make[1]: *** [debian/rules:69: override_dh_install] Error 25

-BEGIN PGP SIGNATURE-

iQKJBAEBCgBzFiEEPJ1UpHV1wCb7F/0mt5o8FqDE8pYFAlxybmQxGmh0dHBzOi8v
d3d3LmRvbWluaWstZ2VvcmdlLmRlL2dwZy1wb2xpY3kudHh0LmFzYyMcZG9taW5p
ay5nZW9yZ2VAaXQucGlyYXRlbnBhcnRlaS5kZQAKCRC3mjwWoMTyluqqEAC9fbLv
L9q/zDG6XR/XobwSrT4YCJ7D1lEHV+N7RrgmMtWJfwoDa3GlJ6S2MS/IbgVyrFLt
44HsTUOsK7e4tr8oGUua81xPZV+29y8b4Uk09pMvtMyYrdoRFlO69hYI/8oa2pmH
9EY0usLY+fOtTw9jjr29yLEoNzDiHRik0XyjDoHqUjW/EWLwTRrRpjINVhGjHYUU
UeVkVl2lKXxtpI62+Xp2PswfrhRMDRQ1CHiJBG1IgcHyMj8Nxhmd5JLq39P+cTgg
Csbgfwp1v3JozQzUt9RDdUbp/UDx25psplhEw0ifqNeDWECQiu6h2NLcmloTsG4i
pAER62c2xcsYQzt0RqYhr90OwLddgA1XV5YE/S1NSo4sBzhaWYN4FPUimPRe6MIF
9u+wrAEmI6KpFJXYMolc4CtX7lSr8my0Jd3T84Z9dQfz39AYEtlGrznEUzNXQNhF
HnyjBOzgmG/HBTCXH4SVakG8NY5Z1heeE/UoadcCMi2ZRqPwsqT0f3s82xENoMNh
TXVjvqRN271+xQxH/qXkbNrT3jqp6IF+kbFCRJLs8mVE4ZWkkZH1/pfcHX6e52Kw
uR3ilfkdNsdoxL8jmxvWDUfPHG8aQjEt/4U/3ObDBCcwHcS9CnzwkcwXXkDX2niE
XV25Ir+LJJ0FoiqychfN/sFmd6xxD/jRuzOCuA==
=nTiW
-END PGP SIGNATURE-

Bug#923126: [INTL:da] Danish translation of the debconf template nodm

[Joe Dalton]

Package: nodm
Severity: wishlist
Tags: l10n patch

Please include the attached Danish nodm debconf po file.

joe@debianbuster:~/over/debian/nodm$ msgfmt --statistics -c -v -o /dev/null 
da.po
da.po: 23 oversatte tekster.

bye
Joe

da.po.tar.gz
Description: application/gzip

Bug#923127: [INTL:da] Danish translation of the debconf template wdm

[Joe Dalton]

Package: wdm
Severity: wishlist
Tags: l10n patch

Please include the attached Danish wdm debconf po file.

joe@debianbuster:~/over/debian/wdm$ msgfmt --statistics -c -v -o /dev/null da.po
da.po: 4 oversatte tekster.

bye
Joe

da.po.tar.gz
Description: application/gzip

Bug#923114: netdata-plugins-bash: sends usage stats to google without consent

[Daniel Baumann]

retitle 923114 disable phone-home script
tag 923114 + pending
thanks

On 2/24/19 10:31 AM, Thomas Krutz wrote:
> i never expected something like this in a debian package.
> /usr/lib/netdata/plugins.d/anonymous-statistics.sh sends infos about my 
> system to google analytics.

yes, we had the same wtf moment when we found out.. and changed that
already in git a couple of days ago, see:

  https://salsa.debian.org/debian/netdata/commits/master

we waited with uploading to not disturb the testing migration, a upload
(with a few more finishing-touches) should follow somewhen this weekend.

Regards,
Daniel

Bug#923128: certbot: endless getrandom() loop when trying to fetch certificate

[Petter Reinholdtsen]

Package: certbot
Version: 0.31.0-1
Severity: important
Forwarded: https://github.com/certbot/certbot/issues/6792

Dear Maintainer,

When trying to use certbot to fetch or renew the ssl sertificate on my
FreedomBox, certbot end up in an endless loop calling getrandom().  I've
reported the issue upstream.  This report contain more information.
Reporting it here in case someone in Debian run into something similar.

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

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

Versions of packages certbot depends on:
ii  python3  3.7.2-1
ii  python3-certbot  0.31.0-1

certbot recommends no packages.

Versions of packages certbot suggests:
pn  python-certbot-doc  
pn  python3-certbot-apache  
pn  python3-certbot-nginx   

-- no debconf information

Bug#920000: NMU

[Hilko Bengen]

user debian-rele...@lists.debian.org
usertag 92 + bsp-2019-02-de-bonn   
tag 92 pending
thank you

Greetings from the BSP taking place at Teckids e.V./tarent solutions
GmbH in Bonn this weekend. I have applied Laurent's patch and uploaded
nacl/20110221-6.1 to DELAYED/2. Feel free to reschedule my upload as you
see fit. The debiff is attached to this mail.

On another note, the master branch at
https://salsa.debian.org/debian/nacl.git does not reflect the state of
the source package -- it contains extra files. You may want to fix that.

Cheers,
-Hilko
diff -Nru nacl-20110221/debian/changelog nacl-20110221/debian/changelog
--- nacl-20110221/debian/changelog	2018-10-23 15:04:30.0 +0200
+++ nacl-20110221/debian/changelog	2019-02-24 10:54:10.0 +0100
@@ -1,3 +1,11 @@
+nacl (20110221-6.1) unstable; urgency=medium
+
+  * Non-maintainer upload
+  * Update patch to remove superfluous build flags, thanks to Laurent Bigonville
+(Closes: #92)
+
+ -- Hilko Bengen   Sun, 24 Feb 2019 10:54:10 +0100
+
 nacl (20110221-6) unstable; urgency=medium
 
   [ Ondřej Nový ]
diff -Nru nacl-20110221/debian/patches/0002-remove-superfluous-compiler-flags.patch nacl-20110221/debian/patches/0002-remove-superfluous-compiler-flags.patch
--- nacl-20110221/debian/patches/0002-remove-superfluous-compiler-flags.patch	2018-10-22 08:10:48.0 +0200
+++ nacl-20110221/debian/patches/0002-remove-superfluous-compiler-flags.patch	2019-02-24 10:54:10.0 +0100
@@ -11,35 +11,32 @@
  okcompilers/cpp | 9 +++--
  2 files changed, 6 insertions(+), 12 deletions(-)
 
-diff --git a/okcompilers/c b/okcompilers/c
-index 7218da3..2667f82 100644
 --- a/okcompilers/c
 +++ b/okcompilers/c
-@@ -1,8 +1,5 @@
+@@ -1,8 +1 @@
 -gcc -m64 -O3 -fomit-frame-pointer -funroll-loops
 -gcc -m64 -O -fomit-frame-pointer
 -gcc -m64 -fomit-frame-pointer
 -gcc -m32 -O3 -fomit-frame-pointer -funroll-loops
 -gcc -m32 -O -fomit-frame-pointer
 -gcc -m32 -fomit-frame-pointer
-+gcc -O3 -fomit-frame-pointer -funroll-loops
-+gcc -O -fomit-frame-pointer
-+gcc -fomit-frame-pointer
- spu-gcc -mstdmain -march=cell -O3 -funroll-loops -fomit-frame-pointer -Drandom=rand -Dsrandom=srand
- spu-gcc -mstdmain -march=cell -O -fomit-frame-pointer -Drandom=rand -Dsrandom=srand
-diff --git a/okcompilers/cpp b/okcompilers/cpp
-index d1b9ae6..35304e4 100644
+-spu-gcc -mstdmain -march=cell -O3 -funroll-loops -fomit-frame-pointer -Drandom=rand -Dsrandom=srand
+-spu-gcc -mstdmain -march=cell -O -fomit-frame-pointer -Drandom=rand -Dsrandom=srand
++gcc ${CFLAGS}
 --- a/okcompilers/cpp
 +++ b/okcompilers/cpp
-@@ -1,8 +1,5 @@
+@@ -1,8 +1 @@
 -g++ -m64 -O3 -fomit-frame-pointer -funroll-loops
 -g++ -m64 -O -fomit-frame-pointer
 -g++ -m64 -fomit-frame-pointer
 -g++ -m32 -O3 -fomit-frame-pointer -funroll-loops
 -g++ -m32 -O -fomit-frame-pointer
 -g++ -m32 -fomit-frame-pointer
-+g++ -O3 -fomit-frame-pointer -funroll-loops
-+g++ -O -fomit-frame-pointer
-+g++ -fomit-frame-pointer
- spu-g++ -mstdmain -march=cell -O3 -funroll-loops -fomit-frame-pointer -Drandom=rand -Dsrandom=srand
- spu-g++ -mstdmain -march=cell -O -fomit-frame-pointer -Drandom=rand -Dsrandom=srand
+-spu-g++ -mstdmain -march=cell -O3 -funroll-loops -fomit-frame-pointer -Drandom=rand -Dsrandom=srand
+-spu-g++ -mstdmain -march=cell -O -fomit-frame-pointer -Drandom=rand -Dsrandom=srand
++g++ ${CFLAGS}
+--- a/okcompilers/archivers
 b/okcompilers/archivers
+@@ -1,2 +1 @@
+ ar
+-ar -X64
diff -Nru nacl-20110221/debian/rules nacl-20110221/debian/rules
--- nacl-20110221/debian/rules	2018-10-22 08:11:09.0 +0200
+++ nacl-20110221/debian/rules	2019-02-24 10:54:10.0 +0100
@@ -2,6 +2,8 @@
 
 #export DH_VERBOSE=1
 
+CFLAGS = $(shell dpkg-buildflags --get CFLAGS)
+
 override_dh_auto_build:
 	# some quick tests for the status of /sys to help debug failures
 	-ls /sys
@@ -13,5 +15,15 @@
 	# DJB "makefile"-ish
 	./do
 
+override_dh_auto_configure:
+	[ -f okcompilers/c.orig ] || cp okcompilers/c okcompilers/c.orig
+	[ -f okcompilers/cpp.orig ] || cp okcompilers/cpp okcompilers/cpp.orig
+	sed -i 's|$${CFLAGS}|$(CFLAGS) -fPIC|g' okcompilers/c okcompilers/cpp
+
 %:
 	dh $@
+
+override_dh_auto_clean:
+	mv -f okcompilers/c.orig okcompilers/c || true
+	mv -f okcompilers/cpp.orig okcompilers/cpp || true
+	dh_auto_clean

Bug#921761: sssd: FTBFS (failing tests)

[Dominik George]

Control: tag -1 + patch

The releveant upstream fix is:
https://github.com/SSSD/sssd/commit/08bba3a6e3e4e21f2e20b71cca463d50420aa9ee#diff-7adf0a00d9dca84b2fbdd1759c1ac2a6.patch

With this patch applied, the test passes again.

Unfortunately, sssd still does not build, maybe for some other
incompatibility with krb5.

I will upload sssd to DELAYED/2 once both are fixed.


signature.asc
Description: PGP signature

Bug#923130: [INTL:da] Danish translation of the debconf template neutron

[Joe Dalton]

Package: neutron
Severity: wishlist
Tags: l10n patch

Please include the attached Danish neutron debconf po file.

joe@debianbuster:~/over/debian/neutron$ msgfmt --statistics -c -v -o /dev/null 
da.po
da.po: 16 oversatte tekster.

bye
Joe

da.po.tar.gz
Description: application/gzip

Bug#923129: golang-1.11-src: errors when building the go compiler from golang-1.11-src package sources (1.11.5-1)(Без темы)

[Сергей Фёдоров]

Package: golang-1.11-src
Version: 1.11.5-1
Severity: normal



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

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

-- no debconf information

In debian-9.8.0-amd64 Sid install the packages:
golang-1.11-go
Go programming language compiler, linker, compiled stdlib
version: 1.11.5-1
golang-1.11-src
Go programming language - source files
version: 1.11.5-1
Make dir «/home/u1/go-1.11-5/»
Copy there the contents of the folder «/usr/share/go-1.11/»
Copy there «/usr/lib/go-1.11/VERSION»
Go to the folder "/ home/u1 / go-1.11-5/src " and create a file "build.sh" with 
such text:
export GOROOT_BOOTSTRAP=/usr/lib/go-1.11/
./all.bash
Start «./build.sh»
It is issued the error:
ok text/template/parse  0.017s
panic: cannot load America/Los_Angeles for testing: open 
/home/u1/go-1.11-5/lib/time/zoneinfo.zip: no such file or directory
goroutine 1 [running]:
time.initTestingZone()
/home/u1/go-1.11-5/src/time/internal_test.go:15 +0x19c
sync.(*Once).Do(0x7b2e90, 0x61ca50)
/home/u1/go-1.11-5/src/sync/once.go:44 +0xb3
time.ForceUSPacificForTesting()
/home/u1/go-1.11-5/src/time/export_test.go:18 +0x87
time.init.0()
/home/u1/go-1.11-5/src/time/internal_test.go:9 +0x20
FAILtime0.021s
...
ok unicode  0.028s
ok cmd/vendor/golang.org/x/sys/unix 0.361s
ok cmd/vet  1.876s
ok cmd/vet/internal/cfg 0.001s
2019/02/21 23:11:40 Failed: exit status 1
Start terminal.
Make dir «/home/u1/go_bootstrap/» and pass into it.
Download through Firefox from «https://golang.org/dl/» 
«go1.11.5.linux-amd64.tar.gz».
Copy from archive the files from the dir «go» to the dir root 
«/home/u1/go_bootstrap/».
Pass to «/home/u1».
Run «git clone https://go.googlesource.com/go».
In «/home/u1» make dir «go» and copy to that the source files «go 1.11.5».
Pass to the dir «/home/u1/go/src» and create file «build.sh» with such text:
export GOROOT_BOOTSTRAP=/usr/lib/go-1.11/
./all.bash
Start «./build.sh»
Assembly and tests pass normally.
./all.bash (assembly and tests) pass normally when gdb is installed (GNU 
Debugger) version 7.12-6, and at version 8.2.1-1 gives error messages:
ok cmd/vendor/golang.org/x/sys/unix 0.361s
ok cmd/vet  1.876s
ok cmd/vet/internal/cfg 0.001s
2019/02/21 23:11:40 Failed: exit status 1
Delete the packages «golang-1.11-go», «golang-1.11-src»
Pass to dir «/home/u1/go/src» and create file «build.sh» with such text:
export GOROOT_BOOTSTRAP=go_bootstrap
./all.bash
Run «./build.sh»
Assembly and tests pass normally.
./all.bash (assembly and tests) pass normally when gdb is installed gdb (GNU 
Debugger) version 7.12-6, and at version 8.2.1-1 gives error messages:
ok cmd/vendor/golang.org/x/sys/unix 0.361s
ok cmd/vet  1.876s
ok cmd/vet/internal/cfg 0.001s
2019/02/21 23:11:40 Failed: exit status 1
The source files of the package «golang-1.11-src» 1.11.5-1 are older then 
https://golang.org/dl/ for Source go1.11.5.src.tar.gz (20MB).

Bug#923034: FreeRADIUS status

[Michael Stapelberg]

The freeradius package is generally in good shape these days, I think.

There are a few users who will report bugs, and there is at least one who
is interested in having the latest upstream version available.

The work required to maintain the package is moderate — let’s say a few
hours each month.

Hope this helps,

On Sun, Feb 24, 2019 at 8:47 AM Niels Thykier  wrote:

> Alan DeKok:
> >   We've been looking for a new Debian maintainer for a while.
> >
> >   What, exactly, is in "bad shape" about this package?  If there are
> issues, we can work towards fixing them.
> >
> >   The software is widely used by many tens of thousands of sites.  I
> hope it's not going to be removed from Debian.
> >
> >   I'll note that Debian also packages "livingston-radius", which hasn't
> had any source changes in 20 years.  There's no mailing list, no support,
> and it doesn't implement any of the modern RADIUS standards.
> >
> >   Including that package does a disservice to people who install it, and
> then realize it's next to useless.
> >
>
> Hi,
>
> I am CC'ing Michael on your reply as I am not sure he is subscribed to
> the bug (it is not the default for Debian bugs) and he is probably
> better at answering this given his prior work with the package.
>
> Thanks,
> ~Niels
>


-- 
Best regards,
Michael

Bug#923131: golang-1.11-src: errors when building the go compiler from golang-1.11-src package sources (1.11.5-1)

[Сергей Фёдоров]

Package: golang-1.11-src
Version: 1.11.5-1
Severity: normal

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

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

-- no debconf information

In debian-9.8.0-amd64 Sid install the packages:
golang-1.11-go
Go programming language compiler, linker, compiled stdlib
version: 1.11.5-1
golang-1.11-src
Go programming language - source files
version: 1.11.5-1
Make dir «/home/u1/go-1.11-5/»
Copy there the contents of the folder «/usr/share/go-1.11/»
Copy there «/usr/lib/go-1.11/VERSION»
Go to the folder "/ home/u1 / go-1.11-5/src " and create a file "build.sh" with 
such text:
export GOROOT_BOOTSTRAP=/usr/lib/go-1.11/
./all.bash
Start «./build.sh»
It is issued the error:
ok text/template/parse 0.017s
panic: cannot load America/Los_Angeles for testing: open 
/home/u1/go-1.11-5/lib/time/zoneinfo.zip: no such file or directory
goroutine 1 [running]:
time.initTestingZone()
/home/u1/go-1.11-5/src/time/internal_test.go:15 +0x19c
sync.(*Once).Do(0x7b2e90, 0x61ca50)
/home/u1/go-1.11-5/src/sync/once.go:44 +0xb3
time.ForceUSPacificForTesting()
/home/u1/go-1.11-5/src/time/export_test.go:18 +0x87
time.init.0()
/home/u1/go-1.11-5/src/time/internal_test.go:9 +0x20
FAIL time 0.021s
...
ok unicode 0.028s
ok cmd/vendor/golang.org/x/sys/unix 0.361s
ok cmd/vet 1.876s
ok cmd/vet/internal/cfg 0.001s
2019/02/21 23:11:40 Failed: exit status 1
Start terminal.
Make dir «/home/u1/go_bootstrap/» and pass into it.
Download through Firefox from «https://golang.org/dl/» 
«go1.11.5.linux-amd64.tar.gz».
Copy from archive the files from the dir «go» to the dir root 
«/home/u1/go_bootstrap/».
Pass to «/home/u1».
Run «git clone https://go.googlesource.com/go».
In «/home/u1» make dir «go» and copy to that the source files «go 1.11.5».
Pass to the dir «/home/u1/go/src» and create file «build.sh» with such text:
export GOROOT_BOOTSTRAP=/usr/lib/go-1.11/
./all.bash
Start «./build.sh»
Assembly and tests pass normally.
./all.bash (assembly and tests) pass normally when gdb is installed (GNU 
Debugger) version 7.12-6, and at version 8.2.1-1 gives error messages:
ok cmd/vendor/golang.org/x/sys/unix 0.361s
ok cmd/vet 1.876s
ok cmd/vet/internal/cfg 0.001s
2019/02/21 23:11:40 Failed: exit status 1
Delete the packages «golang-1.11-go», «golang-1.11-src»
Pass to dir «/home/u1/go/src» and create file «build.sh» with such text:
export GOROOT_BOOTSTRAP=go_bootstrap
./all.bash
Run «./build.sh»
Assembly and tests pass normally.
./all.bash (assembly and tests) pass normally when gdb is installed gdb (GNU 
Debugger) version 7.12-6, and at version 8.2.1-1 gives error messages:
ok cmd/vendor/golang.org/x/sys/unix 0.361s
ok cmd/vet 1.876s
ok cmd/vet/internal/cfg 0.001s
2019/02/21 23:11:40 Failed: exit status 1
The source files of the package «golang-1.11-src» 1.11.5-1 are older then 
https://golang.org/dl/ for Source go1.11.5.src.tar.gz (20MB).

Bug#923132: [INTL:da] Danish translation of the debconf template horizon

[Joe Dalton]

Package: horizon
Severity: wishlist
Tags: l10n patch

Please include the attached Danish horizon debconf po file.

joe@debianbuster:~/over/debian/horizon$ msgfmt --statistics -c -v -o /dev/null 
da.po
da.po: 10 oversatte tekster.

bye
Joe

da.po.tar.gz
Description: application/gzip

Bug#923133: mandelbulber2 FTCBFS: runs qmake for the build architecture

[Helmut Grohne]

Source: mandelbulber2
Version: 2.13.2-4
Tags: patch
User: helm...@debian.org
Usertags: rebootstrap

mandelbulber2 fails to cross build from source, because it runs qmake
without cross flags. The easiest way of adding the required flags is
using dh_auto_configure. It also fails running lrelease, because it
misses a dependency on qt5-qmake:native. The attached patch fixes both
and makes mandelbulber2 cross buildable. Please consider applying it.

Helmut
diff --minimal -Nru mandelbulber2-2.13.2/debian/changelog 
mandelbulber2-2.13.2/debian/changelog
--- mandelbulber2-2.13.2/debian/changelog   2018-07-05 09:58:11.0 
+0200
+++ mandelbulber2-2.13.2/debian/changelog   2019-02-24 11:15:46.0 
+0100
@@ -1,3 +1,12 @@
+mandelbulber2 (2.13.2-4.1) UNRELEASED; urgency=medium
+
+  * Non-maintainer upload.
+  * Fix FTCBFS: (Closes: #-1)
++ Let dh_auto_configure pass cross flags to qmake.
++ Add qt5-qmake:native to Build-Depends for lrelease.
+
+ -- Helmut Grohne   Sun, 24 Feb 2019 11:15:46 +0100
+
 mandelbulber2 (2.13.2-4) unstable; urgency=medium
 
   * Add missing Replaces: directives (closes: #902962).
diff --minimal -Nru mandelbulber2-2.13.2/debian/control 
mandelbulber2-2.13.2/debian/control
--- mandelbulber2-2.13.2/debian/control 2018-07-05 09:58:11.0 +0200
+++ mandelbulber2-2.13.2/debian/control 2019-02-24 11:15:45.0 +0100
@@ -5,7 +5,7 @@
 Build-Depends: debhelper (>= 11)
 Build-Depends-Arch: qtbase5-dev, qtmultimedia5-dev, libpng-dev,
  libgsl-dev, qttools5-dev, qttools5-dev-tools, opencl-dev,
- opencl-clhpp-headers, liblzo2-dev
+ opencl-clhpp-headers, liblzo2-dev, qt5-qmake:native
 Build-Depends-Indep: docbook-xsl, xsltproc, texlive-plain-generic,
  texlive-latex-extra, texlive-pictures, texlive-fonts-recommended,
  lmodern, ghostscript
diff --minimal -Nru mandelbulber2-2.13.2/debian/rules 
mandelbulber2-2.13.2/debian/rules
--- mandelbulber2-2.13.2/debian/rules   2018-07-05 09:58:11.0 +0200
+++ mandelbulber2-2.13.2/debian/rules   2019-02-24 11:15:46.0 +0100
@@ -28,7 +28,7 @@
rm -f *.1
 
 override_dh_auto_configure-arch:
-   mkdir build ; cd build ; qmake -qt5 
../mandelbulber2/qmake/mandelbulber-opencl.pro
+   dh_auto_configure --builddirectory=build 
--sourcedirectory=mandelbulber2/qmake -- 
../mandelbulber2/qmake/mandelbulber-opencl.pro
 
 override_dh_auto_build-arch:
cd build ; make $(MAKEJFLAG)

Bug#923125: FTBFS: cannot find files in override_dh_install

[Dominik George]

Control: tag -1 + pending
Control: tag 921761 + pending

This is due to the check for a matching Kerberos version explicitly
checks all known good versions up to 1.16, but now we have 1.17 in
Debian.

I looked at the upstream changelog and found nothing that could break
the plugin build. Addind 1.17 to the list of known good versions fixes
sssd's build.

Thus, I will upload to DELAYED/2 together with the patch for #921761.


signature.asc
Description: PGP signature

Bug#923134: [INTL:da] Danish translation of the debconf template miniupnpd

[Joe Dalton]

Package: miniupnpd
Severity: wishlist
Tags: l10n patch

Please include the attached Danish miniupnpd debconf po file.

joe@debianbuster:~/over/debian/miniupnpd$ msgfmt --statistics -c -v -o 
/dev/null da.po
da.po: 13 oversatte tekster.


bye
Joe

da.po.tar.gz
Description: application/gzip

Bug#917216: Bug has been fixed

[Hilko Bengen]

user debian-rele...@lists.debian.org
usertag 917216 + bsp-2019-02-de-bonn
fixed 917216 python-apt 1.8.1
thank you

Greetings from the BSP taking place at Teckids e.V./tarent solutions
GmbH in Bonn this weekend.

This bug can be closed as the fix was added before python-apt/1.8.1 by
yourself:

,
| commit 0e8f51100ceff26c6af93f5070671ee602996bf8
| Author: Julian Andres Klode 
| Date:   Fri Jan 25 17:30:33 2019 +0100
`

Cheers,
-Hilko

Bug#761511: misleading message about mount points in /etc/fstab

[Dmitry Bogatov]

control: merge -1 818442

[2019-02-19 03:55] Pierre Ynard 
> > Seems so. This string is still present. I will take a look why it is
> > there, and under what circumstances this suggestion is printed.
>
> This message can be wrongly printed because of at least #818442
> (read-only /dev). In fact it gets printed only if `rm -fr /dev/shm`
> fails, and there aren't too many possible causes for that apart from
> genuine mount mishaps and #818442, so it might just be a variation of
> it, involving some NFS code path apparently.

Then merging. Thank you for triaging.
-- 
Note, that I send and fetch email in batch, once every 24 hours.
 If matter is urgent, try https://t.me/kaction
 --

Bug#692559: RAMTMP is missing too

[Dmitry Bogatov]

control: retitle -1 Document CONCURRENCY variable of rcS


[2019-02-22 09:48] Pierre Ynard 
>
> part   text/plain 689
> > No, no, I do not plan to remove it. Probably, at least comment in
> > /etc/default/tmpfs regarding it should be added.
>
> RAMTMP is already documented in both /etc/default/tmpfs and the tmpfs(5)
> man page.

Okay, so we only miss CONCURRENCY. Actually, we would have not only
documentation, but also code change, since rcS does not respect
CONCURRENCY from /etc/default/rcS:

  * on line 55 `/etc/default/rcS' is sources
  * on line 72 CONCURRENCY is uncoditionally set to 'makefile'

Maybe support for option concurrency=none already in place is enough?
-- 
Note, that I send and fetch email in batch, once every 24 hours.
 If matter is urgent, try https://t.me/kaction
 --

Bug#444980: udev not restarted after exiting runlevel 1

[Dmitry Bogatov]

control: reassign -1 udev

[2019-02-19 15:01] Pierre Ynard 
> As said in the history of the thread, this isn't a problem particular
> to udev. portmap was mentioned. On my system I also have that issue
> with rdnssd: it is started in runlevel S before networking, and isn't
> restarted when leaving runlevel 1. Then there are all the network
> processes such as at least dhclient, and worse than not being restarted,
> the interfaces are not even marked as brought down when going into
> runlevel 1.
>
> I tried to fiddle with LSB headers and rc symlinks to get udev and
> rdnssd to restart in runlevel 2, but I guess I don't know how sysv-rc
> works anymore because I couldn't get anywhere, and anyway I don't
> want to mess with it too much. In the end I added restart logic in
> /etc/rc.local and it seems to work fine; and I switch in and out of
> runlevel 1 all the time.
>
> I don't see why we couldn't properly fix this to have each of them shut
> down cleanly in runlevel 1 and then restart in runlevel 2. When I look
> at udev's initscript, it seems like it must be much better in that
> regard now than what was described 10 years ago.

Probably we can, just nobody did it. Sorry, I am not up to this.

Reassigned to udev, since /etc/init.d/udev belongs to bin:udev.
-- 
Note, that I send and fetch email in batch, once every 24 hours.
 If matter is urgent, try https://t.me/kaction
 --

Bug#923087: [git-buildpackage/master] Disable PGP signatures when retrieving list of commits

[Gabriel Filion]

tag 923087 pending
thanks

Date:   Sat Feb 23 20:03:41 2019 -0500
Author: Gabriel Filion 
Commit ID: 34b9da1de902be0f4e43fd99d0fcb7e278bedbd9
Commit URL: 
https://git.sigxcpu.org/cgit/git-buildpackage//commit/?id=34b9da1de902be0f4e43fd99d0fcb7e278bedbd9
Patch URL: 
https://git.sigxcpu.org/cgit/git-buildpackage//patch/?id=34b9da1de902be0f4e43fd99d0fcb7e278bedbd9

Disable PGP signatures when retrieving list of commits

gbp dch errors out with the following output if the "log.showSignature"
git config is enabled:

$ gbp dch --verbose
gbp:debug: ['git', 'rev-parse', '--show-cdup']
gbp:debug: ['git', 'rev-parse', '--is-bare-repository']
gbp:debug: ['git', 'rev-parse', '--git-dir']
gbp:debug: ['git', 'symbolic-ref', 'HEAD']
gbp:debug: ['git', 'show-ref', 'refs/heads/master']
gbp:debug: ['git', 'tag', '-l', 'debian/2.7.3-2']
gbp:debug: ['git', 'tag', '-l', 'debian/2.7.3-2']
gbp:debug: ['git', 'log', '--pretty=format:%H', '-1', '--', 
'debian/changelog']
gbp:info: Changelog last touched at 'gpg: Signature made Fri 01 Feb 2019 
03:56:19 PM EST'
gbp:debug: ['git', 'log', '--pretty=format:%H', 'gpg: Signature made Fri 01 
Feb 2019 03:56:19 PM EST..HEAD', '--no-merges', '--']
fatal: bad revision 'gpg: Signature made Fri 01 Feb 2019 03:56:19 PM 
EST..HEAD'
gbp:error: Error getting commits gpg: Signature made Fri 01 Feb 2019 
03:56:19 PM EST..HEAD

This is caused by gbp dch receiving unexpected output for the PGP
signatures and trying to use this unexpected output.

To avoid any surprises, let's disable signatures being output when we
list commits.

Also, when collecting a shortlog-like output from commit objects, the
same unexpected PGP signature output is sprayed all over the changelog.
We'll avoid this by also disable showing signatures when showing each
commit's first line.

Closes: #923087

  

Bug#922815: insserv FATAL while updating as mountkernfs has to be enabled to use service udev

[Dmitry Bogatov]

[2019-02-22 15:30] shirish शिरीष 
> > >
> > > Setting up udev (240-6) ...
> > > update-initramfs: deferring update (trigger activated)
> > > insserv: FATAL: service mountkernfs has to be enabled to use service udev
> > >
> > > maybe it just needs mountkernfs to be added in the interactive bit at
> > > the bottom or somewhere else ?
> > [Dmitry Bogatov]
> > Maybe. But I updated recently, and I did not encountered this problem.
> > Please test my wild guess:
> >
> > $ find /etc/rcS.d|grep mountkernfs
> >
> Dear Dmitry,
>
> The output is empty or zero -
>
> shirish@debian:~$ find /etc/rcS.d|grep mountkernfs
> shirish@debian:~$

Interesting, you seems somehow got mountkernfs.sh script removed from
runlevel S.

Can you please invoke as root

# update-rc.d mountkernfs.sh enable S

and then retry your upgrade.
-- 
Note, that I send and fetch email in batch, once every 24 hours.
 If matter is urgent, try https://t.me/kaction
 --

Bug#768555: bootlogd apparantly runs but /var/log/bootlog* files are from 2013

[Dmitry Bogatov]

[2019-02-23 03:13] Pierre Ynard 
> > /etc/init.d/bootlogd [Errno 2] No such file or directory: 
> > u'/etc/init.d/bootlogd'
> > /etc/init.d/stop-bootlogd [Errno 2] No such file or directory: 
> > u'/etc/init.d/stop-bootlogd'
> > /etc/init.d/stop-bootlogd-single [Errno 2] No such file or directory: 
> > u'/etc/init.d/stop-bootlogd-single'
>
> Other reports featuring missing init scripts can be found in #663587 and
> #689992, both originally about different issues. Reports in #689992 only
> miss /etc/init.d/stop-bootlogd and /etc/init.d/stop-bootlogd-single, not
> /etc/init.d/bootlogd

We can forcemerge them and close on timeout, correct?
-- 
Note, that I send and fetch email in batch, once every 24 hours.
 If matter is urgent, try https://t.me/kaction
 --

Bug#923136: [INTL:da] Danish translation of the debconf template openstack-pkg-tools

[Joe Dalton]

Package: openstack-pkg-tools
Severity: wishlist
Tags: l10n patch

Please include the attached Danish openstack-pkg-tools debconf po file.

joe@debianbuster:~/over/debian/openstack-pkg-tools$ msgfmt --statistics -c -v 
-o /dev/null da.po
da.po: 53 oversatte tekster.

bye
Joe

da.po.tar.gz
Description: application/gzip

Bug#923135: gravitation FTCBFS: uses the wrong compiler

[Helmut Grohne]

Source: gravitation
Version: 3+dfsg1-5
Tags: patch
User: helm...@debian.org
Usertags: rebootstrap

gravitation fails to cross build from source, the upstream build system
hard codes the build architecture compiler. Simply making it
substituable is insufficient here as dh_auto_build expects that
configure sets up cross tools, but the simplistic configure doesn't do
that. So we must tell dh_auto_build to pretend the simpler makefile
build system to make it pass cross tools. The attached patch makes
gravitation cross buildable. Please consider applying it.

Helmut
diff --minimal -Nru gravitation-3+dfsg1/debian/changelog 
gravitation-3+dfsg1/debian/changelog
--- gravitation-3+dfsg1/debian/changelog2017-08-01 16:46:46.0 
+0200
+++ gravitation-3+dfsg1/debian/changelog2019-02-24 12:33:56.0 
+0100
@@ -1,3 +1,12 @@
+gravitation (3+dfsg1-5.1) UNRELEASED; urgency=medium
+
+  * Non-maintainer upload.
+  * Fix FTCBFS: (Closes: #-1)
++ cross.patch: Make C++ compiler substitutable.
++ Let dh_auto_build --buildsystem=makefile pass cross tools to make.
+
+ -- Helmut Grohne   Sun, 24 Feb 2019 12:33:56 +0100
+
 gravitation (3+dfsg1-5) unstable; urgency=medium
 
   * Fix build reproducibility issues due to use of imagemagick (Closes: 
#776872)
diff --minimal -Nru gravitation-3+dfsg1/debian/patches/cross.patch 
gravitation-3+dfsg1/debian/patches/cross.patch
--- gravitation-3+dfsg1/debian/patches/cross.patch  1970-01-01 
01:00:00.0 +0100
+++ gravitation-3+dfsg1/debian/patches/cross.patch  2019-02-24 
12:33:56.0 +0100
@@ -0,0 +1,13 @@
+--- gravitation-3+dfsg1.orig/game5/gameSource/Makefile.all
 gravitation-3+dfsg1/game5/gameSource/Makefile.all
+@@ -1,8 +1,8 @@
+ 
+ ROOT_PATH = ../..
+ 
+-COMPILE = g++ ${PLATFORM_COMPILE_FLAGS} -Wall -g -I${ROOT_PATH} -c
+-LINK = g++ -I${ROOT_PATH}
++COMPILE = $(CXX) ${PLATFORM_COMPILE_FLAGS} -Wall -g -I${ROOT_PATH} -c
++LINK = $(CXX) -I${ROOT_PATH}
+ 
+ 
+ 
diff --minimal -Nru gravitation-3+dfsg1/debian/patches/series 
gravitation-3+dfsg1/debian/patches/series
--- gravitation-3+dfsg1/debian/patches/series   2008-06-11 03:31:47.0 
+0200
+++ gravitation-3+dfsg1/debian/patches/series   2019-02-24 12:33:56.0 
+0100
@@ -1 +1,2 @@
 abs_path.patch
+cross.patch
diff --minimal -Nru gravitation-3+dfsg1/debian/rules 
gravitation-3+dfsg1/debian/rules
--- gravitation-3+dfsg1/debian/rules2014-11-26 09:44:13.0 +0100
+++ gravitation-3+dfsg1/debian/rules2019-02-24 12:33:55.0 +0100
@@ -19,7 +19,7 @@
convert 32x32/gravitation.png 32x32/gravitation.xpm
sed -i -e 's/PLATFORM_COMPILE_FLAGS = */PLATFORM_COMPILE_FLAGS = 
$$(CFLAGS) $$(CPPFLAGS) /' game5/gameSource/Makefile
sed -i -e 's/PLATFORM_LINK_FLAGS = */PLATFORM_LINK_FLAGS = $$(LDFLAGS) 
/' game5/gameSource/Makefile
-   $(MAKE) -C game5/gameSource LDFLAGS="-lpthread $(LDFLAGS)" 
CPPFLAGS="$(CPPFLAGS)" CFLAGS="$(CFLAGS) -DETCDIR=\\\"/etc/gravitation\\\" 
-DDATADIR=\\\"/usr/share/games/gravitation/\\\""
+   dh_auto_build --buildsystem=makefile --sourcedirectory=game5/gameSource 
-- LDFLAGS="-lpthread $(LDFLAGS)" CPPFLAGS="$(CPPFLAGS)" CFLAGS="$(CFLAGS) 
-DETCDIR=\\\"/etc/gravitation\\\" 
-DDATADIR=\\\"/usr/share/games/gravitation/\\\""
 
 override_dh_auto_clean:
find game5 -name "*.o" -delete

Bug#923082: can't disable systemd-resolved

[Toni Mueller]

Hi Martin,

On Sun, Feb 24, 2019 at 08:03:38AM +0100, Martin Pitt wrote:
> Toni [2019-02-23 23:05 +]:
> > I can't disable systemd-resolved, which prevents me from running my own
> > DNS setup:
> 
> systemd-resolved.service is not enabled by default in Debian. If you enabled
> it, what prevents you from disabling it again? (systemctl disable
> systemd-resolved).

I really can't remember having enabled it - and I also don't know why I
would have done it, having my own setup in several of the areas that
systemd is encroaching on. But what prevents me from disabling systemd,
is quite simple: It just does not work:


# systemctl stop systemd-resolved
# lsof -i udp@0.0.0.0:53
COMMAND   PID   USER   FD   TYPE  DEVICE SIZE/OFF NODE NAME
systemd 1   root  113u  IPv4   10583  0t0  UDP localhost:domain


That's why I filed a bug report - it really should be possible to
disable this service.

> resolved doesn't run in pid 1 (that would be a really bad architecture!). This
> just means that pid 1 connected to localhost's name server to resolve a name
> (i. e. a DNS client). A better command to find out which processes are
> *listening* on UDP ports is "ss -ulpen", or for port 53 specifically,
> "ss -ulpen 'sport = 53'".

# ss -ulpen 'sport = 53'
State Recv-QSend-Q   Local Address:Port 
Peer Address:Port
UNCONN0 0192.168.122.1:53   
 0.0.0.0:*users:(("dnsmasq",pid=13861,fd=5)) ino:5159825 
sk:a1 <->
UNCONN0 0127.0.0.1:53   
 0.0.0.0:*users:(("systemd",pid=1,fd=113)) ino:10583 sk:a2 
<->
UNCONN0 0[::1]:53   
[::]:*users:(("systemd",pid=1,fd=111)) ino:362 sk:a3 
v6only:1 <->

This I took after trying to stop systemd-resolved.

Other things I tried:

 * setting DNSStubListener=no in /etc/systemd/resovled.conf, followed by
 * systemctl daemon-reload, followed by
 * systemctl daemon-reexec

But it was all for naught.


Kind regards,
Toni

Bug#923139: src:netkit-telnet-ssl: cruft: debian/ssltelnet.preinst

[Christoph Biedl]

Package: src:netkit-telnet-ssl
Version: 0.17.41+0.2-3
Severity: minor

Dear Maintainer,

there's a file debian/ssltelnet.preinst in the source without a
related package. Probably leftover from old times, please re-check
and possibly remove.

Christoph

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

Kernel: Linux 4.19.21 (SMP w/4 CPU cores)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_WARN, TAINT_OOT_MODULE
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: unable to detect



signature.asc
Description: PGP signature

Bug#923137: chrony: system call filter (now enabled by default) conflicts not only with mailonchange, but also with log

[Francesco Poli (wintermute)]

Package: chrony
Version: 3.4-2
Severity: important

Hello there!
Thanks for maintaining this useful package.

I've just upgraded to version 3.4-2 and noticed that the daemon failed to
restart, due to the mailonchange directive:

  $ grep -B 1 ^mailonchange /etc/chrony/chrony.conf
  # Warn root.
  mailonchange root@localhost 4.0

After reading /usr/share/doc/chrony/NEWS.Debian.gz , I found out that
the new system call filter (which is now enabled by default) is
incompatible with the mailonchange directive.
This didn't make me especially happy, since that little local mail
message telling me there was a significant time adjustment was nice
to have... But, oh well, I can live without it, so I thought "let's
get rid of it!".

  $ grep mailonchange /etc/chrony/chrony.conf

gives no output, OK.

  # service chrony restart

Everything seems to be fine, but:

  $ ps a | grep chrony
  10686 pts/1S+ 0:00 grep chrony

the daemon is not running!

After a bit of investigation, I found out that the log directive:

  $ grep '^log ' /etc/chrony/chrony.conf
  log tracking measurements statistics

seems to also conflict with the system call filter.

There are two issues with this.
First of all, the NEWS.Debian.gz file does not seem to mention it
(the man page also seems to say nothing about it).
Secondly, with no mailonchange and no log, chrony seems to have become
completely silent: how can I check that it is actually working fine,
if I cannot even see which time servers it is tracking?

Is this a bug or something unavoidable (that should be documented in
the NEWS.Debian.gz file and/or in the man page)?


I have disabled the system call filter for the time being, in order
to enable log (as well as mailonchange):

  $ grep OPTS /etc/default/chrony
  DAEMON_OPTS="-F 0"


Please let me know whether I misunderstood something and/or whether
I am doing something wrong.
Thanks for your time!

Bye.



-- System Information:
Debian Release: buster/sid
  APT prefers testing
  APT policy: (800, 'testing'), (500, 'unstable')
Architecture: i386 (i586)

Kernel: Linux 4.19.0-2-686 (SMP w/1 CPU core)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_US:en (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: sysvinit (via /sbin/init)
LSM: AppArmor: enabled

Versions of packages chrony depends on:
ii  adduser  3.118
ii  init-system-helpers  1.56+nmu1
ii  iproute2 4.20.0-2
ii  libc62.28-7
ii  libcap2  1:2.25-2
ii  libedit2 3.1-20181209-1
ii  libnettle6   3.4.1-1
ii  libseccomp2  2.3.3-4
ii  lsb-base 10.2018112800
ii  ucf  3.0038+nmu1

chrony recommends no packages.

Versions of packages chrony suggests:
pn  dnsutils 
pn  networkd-dispatcher  

-- Configuration Files:
/etc/default/chrony changed:
DAEMON_OPTS="-F 0"


-- no debconf information

Bug#923138: [INTL:da] Danish translation of the debconf template keystone

[Joe Dalton]

Package: keystone
Severity: wishlist
Tags: l10n patch

Please include the attached Danish keystone debconf po file.

joe@debianbuster:~/over/debian/keystone$ msgfmt --statistics -c -v -o /dev/null 
da.po
da.po: 28 oversatte tekster.

bye
Joe

da.po.tar.gz
Description: application/gzip

Bug#923140: ITP: isce2-- Interferometric SAR Scientific Computing Environment

[Antonio Valentino]

Package: wnpp
Severity: wishlist
Owner: Antonio Valentino 

* Package name: isce2
  Version : 2.3.1
  Upstream Author : Eric Gurrola, Kosal Khun, Marco Lavalle,
Joshua Cohen, Giangi Sacco
* URL : https://github.com/isce-framework/isce2
* License : Apache-2.0
  Programming Lang: Python
  Description : Interferometric SAR Scientific Computing Environment
   ISCE is a framework designed for the purpose of processing
   Interferometric Synthetic Aperture Radar (InSAR) data.
   The framework aspects of it have been designed as a general software
   development framework.
   It may have additional utility in a general sense for building
   other types of software packages.
   In its InSAR aspect ISCE supports data from many space-borne
   satellites and one air-borne platform. At this time the sensors that
   are supported are the following: ALOS, ALOS2, COSMO_SKYMED, ENVISAT,
   ERS, KOMPSAT5, RADARSAT1, RADARSAT2, RISAT1, Sentinel1, TERRASARX,
   and UAVSAR.

Binary package names: python3-isce2

Bug#917524: initramfs-tools: Upgrade from initramfs-tools package fails

[Jürgen Göricke]

Hello Ben,

After the dpkg (1.19.5) update was installed yesterday, the problem could be 
solved.
This bug report can be closed.
Thanks for the support!




pgpE9dd34c7NW.pgp
Description: Digitale Signatur von OpenPGP

Bug#923141: RM: xul-ext-timeline -- ROM; Package doesn't work with Tunderbird anymore and upstream stopped development

[Matthias Schmitz]

Package: ftp.debian.org
Severity: normal

As mentioned in
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=918164 the package is
unusable with any version of Thunderbird and upstream stopped
development.

Please remove the package from the archive.



pgpd1DqotiOVM.pgp
Description: Digitale Signatur von OpenPGP

Bug#923142: Debconf option roundcube/language has no effect

[Oleg Strikov]

Package: roundcube
Version: 1.3.8+dfsg.1-2

I expected to see $config['language'] = 'ru_RU' in the configuration
file after setting debconf option roundcube/language accordingly,
but that's not what happened:

# echo roundcube-core roundcube/language string ru_RU | debconf-set-selections
# apt-get install roundcube
# grep language /etc/roundcube/config.inc.php || echo Not found
Not found

Postinst script roundcube-core.postinst has no way to add new lines to
the template placed at /usr/share/roundcube/config.inc.php.sample. It can
only modify values of existing variables. Current version of the template
doesn't contain $config['language'] line hence this variable can't be set
by postinst script during configuration.

Unfortunately, we can't simply copy $config['language'] line from
defaults.inc.php to config.inc.php.sample. If no $config['language'] line
exists in the configuration file or its value is null, roundcube uses
HTTP_ACCEPT_LANGUAGE-based language auto-detection, which is desired behavior.
Debconf sets roundcube/language to en_US (or some other language based on
locale) by default which would disable auto-detection for all installations
if this value gets propagated to the configuration file every time. In order
to avoid this, we need to add $config['language'] line to the configuration
file only if roundcube/language has been manually set (preseeded).

Bug#918164: Broken with Thunderbird 60

[Matthias Schmitz]

Hi everyone,

On Sat, 23 Feb 2019 12:16:37 +0100 Carsten Schoenert
 wrote:

> On Thu, Jan 03, 2019 at 11:21:19PM +0100, Moritz Muehlenhoff wrote:
> > The plugin is broken with Thunderbird 60 in stretch and sid, after
> > installation it's disabled and only prints "Timeline is
> > incompatible with Thunderbird 60.4".
...
> currently the package xul-ext-timeline is useless as it isn't usable
> in any release of Debian any more.
> 
...
> We should remove this package completely from the Debian archives.
I agree that the package should be removed. Therefore i filed a removal
bug:

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

Thanks for taking care of security and Thunderbird! :-)

Best wishes,
Matthias  


pgpyeLCtovzgZ.pgp
Description: Digitale Signatur von OpenPGP

Bug#920823: phpmyadmin: CVE-2019-6799: PMASA-2019-1

[Sylvain Beucler]

Hi,

FYI I prepared a patch for jessie, see:
https://lists.debian.org/debian-lts/2019/02/msg00164.html

For stretch, it is worth noting that the fix depends on whether mysql or
mysqli is enabled, whether open_basedir is in effect, and whether we're
protecting against user SQL queries or phpmyadmin-generated queries
(during CSV import).
(but no more phpX-mysql vs. phpX-mysqlnd AFAICS.)

Cheers!
Sylvain

Bug#843419: init-d-script: please provide a way to not use the --name option of start-stop-daemon

[wferi]

control: tags -1 -moreinfo

Dmitry Bogatov  writes:

> Sorry, I do not understand. You, as init script writer, choose value of
> argument to $NAME. Why can't you limit it to required length?

Sorry, I indeed left out important context, thus even I had difficulty
recalling the reason for my report now.  So:

I use /lib/init/init-d-script to provide an init script for the
corosync-qdevice daemon.  I have to set NAME="corosync-qdevice", because
the NAME variable is used in several informational messages as well
besides as the --name value for start-stop-daemon.  But then I have to
override the do_start_cmd() and do_stop_cmd() shell functions to use the
correct --name value (or not use one at all).  The other choice would be
letting the informational messages use the truncated name, which is
suboptimal in a different (and visible) way.

I imagine that having an optional COMM_NAME (pick any name) variable
would solve this nicely, if it was used in preference to NAME for the
--name option of start-stop-daemon if it was set, like

start-stop-daemon --name "${COMM_NAME:-$NAME}"

or maybe even (just an untested idea):

if [ -n "${COMM_NAME:=$NAME}" ]; then
   NAME_ARG="--name=$COMM_NAME"
else
   NAME_ARG=""
fi
[...]
start-stop-daemon [...] "$NAME_ARG" [...]
-- 
Thanks,
Feri

Bug#923143: [INTL:da] Danish translation of the debconf template diaspora-installer

[Joe Dalton]

Package: diaspora-installer
Severity: wishlist
Tags: l10n patch

Please include the attached Danish diaspora-installer debconf po file.

joe@debianbuster:~/over/debian/diaspora-installer$ msgfmt --statistics -c -v -o 
/dev/null da.po
da.po: 45 oversatte tekster.

bye
Joe

da.po.tar.gz
Description: application/gzip

Bug#923144: [INTL:da] Danish translation of the debconf template lyskom-server

[Joe Dalton]

Package: lyskom-server
Severity: wishlist
Tags: l10n patch

Please include the attached Danish lyskom-server debconf po file.

joe@debianbuster:~/over/debian/lyskom-server$ msgfmt --statistics -c -v -o 
/dev/null da.po
da.po: 11 oversatte tekster.

bye
Joe

da.po.tar.gz
Description: application/gzip

Bug#915319: Some diagnosis

[Hilko Bengen]

user debian-rele...@lists.debian.org
usertag 915319 + bsp-2019-02-de-bonn   
tag 915319 + confirmed
thank you

Greetings from the BSP taking place at Teckids e.V./tarent
solutions GmbH in Bonn this weekend.

I have been able to confirm the symptom: The CMake-based build system is
unable to find the smbclient functions it needs:

,
| -- Checking for module 'smbclient'
| --   Found smbclient, version 0.4.0
| -- Looking for smbc_set_context
| -- Looking for smbc_set_context - not found
| -- Looking for smbc_option_set
| -- Looking for smbc_option_set - not found
`

I don't yet know how to debug this further, but it seems to me that the
detection code in /usr/share/kde4/apps/cmake/modules/FindSamba.cmake
somehow fails:

,
|set(CMAKE_REQUIRED_LIBRARIES ${CMAKE_REQUIRED_LIBRARIES} 
${SAMBA_LIBRARIES})
|set(CMAKE_REQUIRED_INCLUDES ${CMAKE_REQUIRED_INCLUDES} 
${SAMBA_INCLUDE_DIR})
|check_symbol_exists(smbc_set_context "libsmbclient.h" 
SAMBA_HAVE_SMBC_SET_CONTEXT)
|check_symbol_exists(smbc_option_set "libsmbclient.h" 
SAMBA_HAVE_SMBC_OPTION_SET)
`

The file /usr/include/samba-4.0/libsmbclient.h clearly contains both
symbols.

Cheers,
-Hilko

Bug#923145: [INTL:da] Danish translation of the debconf template cltl

[Joe Dalton]

Package: cltl
Severity: wishlist
Tags: l10n patch

Please include the attached Danish cltl debconf po file.

joe@debianbuster:~/over/debian/cltl$ msgfmt --statistics -c -v -o /dev/null 
da.po
da.po: 4 oversatte tekster.

bye
Joe

da.po.tar.gz
Description: application/gzip

Bug#923146: KDE window movement breaks after 49days

[Stevie Trujillo]

Source: qtbase-opensource-src
Version: 5.7.1+dfsg-3
Source: kwin
Version: 4:5.8.6-1

After running X11 for around 49 days moving windows with click+drag on
the titlebar and windows switching using Alt-Tab with kwin_x11 stop
working.

Recent Qt and KDE have fixed it:
https://bugreports.qt.io/browse/QTBUG-65145
https://bugs.kde.org/show_bug.cgi?id=377901 (commit:
https://cgit.kde.org/kwin.git/commit/?id=0bec9ad7337536e319c17c5684d97e1156399fdb
)
https://phabricator.kde.org/D5731

Bug#921987: Comments related to BUG 921987

[Frank1998sj]

Hi,

I found that it could be apparmor which stops the program from execution. I 
use aa-disable to temporarily disable apparmor on /usr/sbin/mysqld then it 
works.

Regards

Bug#923147: tenace FTCBFS: configures for the build architecture

[Helmut Grohne]

Source: tenace
Version: 0.16-1
Tags: patch
User: helm...@debian.org
Usertags: rebootstrap

tenace fails to cross build from source, because it does not pass --host
to ./configure. The easiest way of doing so - using dh_auto_configure -
makes tenace cross buildable. Please consider applying the attached
patch.

Helmut
diff --minimal -Nru tenace-0.16/debian/changelog tenace-0.16/debian/changelog
--- tenace-0.16/debian/changelog2018-09-23 15:04:05.0 +0200
+++ tenace-0.16/debian/changelog2019-02-24 13:21:28.0 +0100
@@ -1,3 +1,10 @@
+tenace (0.16-1.1) UNRELEASED; urgency=medium
+
+  * Non-maintainer upload.
+  * Fix FTCBFS: Let dh_auto_configure pass --host to ./configure. (Closes: #-1)
+
+ -- Helmut Grohne   Sun, 24 Feb 2019 13:21:28 +0100
+
 tenace (0.16-1) unstable; urgency=medium
 
   * New upstream version.
diff --minimal -Nru tenace-0.16/debian/rules tenace-0.16/debian/rules
--- tenace-0.16/debian/rules2010-12-11 22:56:26.0 +0100
+++ tenace-0.16/debian/rules2019-02-24 13:21:24.0 +0100
@@ -4,7 +4,7 @@
 
 configure: configure-stamp
 configure-stamp:
-   ./configure --prefix=/usr --bindir=/usr/games
+   dh_auto_configure -- --bindir=/usr/games
touch $@
 
 build-indep:

Bug#923148: dds FTCBFS: builds for the wrong architecture

[Helmut Grohne]

Source: dds
Version: 2.9.0-6
Tags: patch
User: helm...@debian.org
Usertags: rebootstrap

dds fails to cross build from source, because it does not pass cross
tools to make. The easiest way of doing so - using dh_auto_build - makes
dds cross buildable. Please consider applying the attached patch.

Helmut
diff --minimal -Nru dds-2.9.0/debian/changelog dds-2.9.0/debian/changelog
--- dds-2.9.0/debian/changelog  2019-01-30 14:21:50.0 +0100
+++ dds-2.9.0/debian/changelog  2019-02-24 14:12:38.0 +0100
@@ -1,3 +1,10 @@
+dds (2.9.0-6.1) UNRELEASED; urgency=medium
+
+  * Non-maintainer upload.
+  * Fix FTCBFS: Let dh_auto_build pass cross tools to make. (Closes: #-1)
+
+ -- Helmut Grohne   Sun, 24 Feb 2019 14:12:38 +0100
+
 dds (2.9.0-6) unstable; urgency=medium
 
   * Pass CFLAGS to examples Makefile as well.
diff --minimal -Nru dds-2.9.0/debian/rules dds-2.9.0/debian/rules
--- dds-2.9.0/debian/rules  2019-01-30 14:13:28.0 +0100
+++ dds-2.9.0/debian/rules  2019-02-24 14:12:34.0 +0100
@@ -20,7 +20,7 @@
rm -f examples/*.o examples/libdds.so
 
 override_dh_auto_build:
-   $(MAKE) -C src -f Makefiles/Makefile_linux_shared
+   dh_auto_build --buildsystem=makefile --sourcedirectory=src -- -f 
Makefiles/Makefile_linux_shared
 
 override_dh_auto_test:
 ifeq (, $(findstring nocheck, $(DEB_BUILD_OPTIONS)))

Bug#914897: tech-ctte: Should debootstrap disable merged /usr by default?

[Johannes Schauer]

Hi,

On Sat, 02 Feb 2019 15:38:01 +0100 Didier 'OdyX' Raboud  wrote:
> Gunnar and myself have started working on a draft, the latest version of
> which is available at
> 
>   
> https://salsa.debian.org/debian/tech-ctte/blob/master/914897_merged_usr/ballot.md

I found that some important arguments are still missing. A recent mail by
Guillem [1] nicely summarizes also many of my own thoughts. I'm going to paste
the relevant content into this mail for convenience of the reader:

[1] https://lists.debian.org/20190219044924.gb21...@gaara.hadrons.org

Quoting Guillem Jover (2019-02-19 05:49:24)
> The underlaying problem with the merged-/usr-via-symlinks is not
> really that it has generated bugs, many transitions we perform incur
> those, for the better. The problem is that it has generated those when
> it was really not necessary in the first place, has made things
> unnecessarily more complicated for everyone, and it's a terrible hack
> trying to reap "quick" benefits at the cost of everyhing else, with
> long lasting consequences even after a full migration to /usr would
> have been finished. And here's why:
> 
> 1) The merged-/usr-via-symlinks deployment method used by both
>debootstrap and usrmerge, means that those systems will get
>permanent filesystem aliasing problems, forever. Even when all
>files might have been moved to their /usr counterparts in the
>packages! This is due to the fact that different pathnames can
>end up pointing (before any canonicalization!) to the same dentry.
> 
>This does not only affect dpkg (dpkg, dpkg-divert, dpkg-trigger,
>etc), and update-alternatives (in a worse way), but any program
>that uses pathanmes in the filesystem as keys in databases f.ex.
> 
> 2) It bypasses the packaging system understanding of what is on the
>filesystem and creates mismatches between what's on binary packages
>and what's on disk.
> 
> 3) Switching packages to the merged-/usr layout could have been
>accomplished automatically via debhelper for a coverage of around
>99% (?) of the archive. With something along the lines of:
> 
>  ,---
>  D=debian/tmp
>  for d in /bin /sbin /lib; do
>for p in $(find $D/$d ! -type d); do
>  b="${p##$D/}"
>  m="$D/usr$b"
>  if [ ! -e "$m" ]; then
>mkdir -p "$(dirname $m)"
>mv "$p" "$m"
>ln -s "${m##$D}" "$p"
>  fi
>done
>  done
>  `---
> 
>With the property that it would handle gracefully all cases were the
>maintainer has checked that no compat symlinks are required and has
>then progressively moved the pathname installation to their final
>destination under /usr.
> 
> 4) Due to having to support the broken merged-/usr-via-symlinks
>deployment, when we want to move the contents of the binary
>packages to the merged-/usr layout, we require now to include tons
>of logic in (probably new) maintainer scripts, when we have been
>trying to remove them altogether. :( With even more files untracked
>by dpkg itself, bypassing the packaging system even more, when the
>compat symlinks could have been shipped in the binary packages.
> 
> 5) Most new installations will not even benefit from this hacky and
>rushed deployment, as long as they do not use a separate parition
>for /usr!
> 
> 6) The merged-/usr-via-symlinks deployment hack is irreversible right
>now.

Just like Guillem, I'm personally not against merged-/usr but against how we
implement it. In addition to Guillems arguments, I also want to make another.

With how merged-/usr is getting deployed via debootstrap, we are placing more
of the instructions of how a Debian system is supposed to be setup *outside* of
the packages themselves (and into debootstrap). It would make a cleaner design
if we could have all necessary definitions of how to create a Debian chroot
from scratch (on a Debian system) in the packages *themselves* instead of
requiring code around the packages that is doing some magic setup (usually
debootstrap).  With mmdebstrap I am trying to write a POC to show that it is
possible to set up a Debian chroot with only very little magic and the help of
apt. My goal is to move the remaining magic setup that is currently required
into apt and dpkg (the respective maintainers are in favor of that plan but I'm
waiting for the buster release). If merged-/usr is getting implemented in the
way as it is done by debootstrap, then every debootstrap-like program has to
reproduce these mechanisms which are already architecture specific and thus not
trivial to maintain over time. It would be more elegant if the way merged-/usr
is being deployed is being encoded in the packages themselves so that we can
further *reduce* the amount of code that needs to live outside of packages
until we eventually need zero setup code before debootstrap-like programs can
install binary packages into a chroot. If we decide to deploy mer

Bug#922984: xml-security-c: ECDSA XML signature generation segmentation fault

[wferi]

Alejandro Claro  writes:

> We found a bug in Apache Santuario C, related to ECDSA signature
> generation, few years ego. We provide the fix to the Apache team, and
> Scott Cantor kindly accepted the fix in the project. How ever the fix
> was introduced in series 2.x of the the library.

Dear Alejandro,

I can propose your fix for the next stable update, but I don't know when
that will be released.  On the other hand, if this buffer overflow leads
to an exploitable vulnerability, the Security Team could fast-track the
fix.  Have you got such a scenario?
-- 
Thanks,
Feri

Bug#923149: bombardier FTCBFS: does not pass cross tools to make

[Helmut Grohne]

Source: bombardier
Version: 0.8.3+nmu1
Tags: patch
User: helm...@debian.org
Usertags: rebootstrap

bombardier fails to cross build from source, because it does not pass
cross tools to make. The easiest way of doing so - using dh_auto_build -
makes bombardier cross buildable. Please consider applying the attached
patch.

Helmut
diff --minimal -Nru bombardier-0.8.3+nmu1/debian/changelog 
bombardier-0.8.3+nmu2/debian/changelog
--- bombardier-0.8.3+nmu1/debian/changelog  2010-02-10 10:25:44.0 
+0100
+++ bombardier-0.8.3+nmu2/debian/changelog  2019-02-24 14:19:06.0 
+0100
@@ -1,3 +1,10 @@
+bombardier (0.8.3+nmu2) UNRELEASED; urgency=medium
+
+  * Non-maintainer upload.
+  * Fix FTCBFS: Let dh_auto_build pass cross tools to make. (Closes: #-1)
+
+ -- Helmut Grohne   Sun, 24 Feb 2019 14:19:06 +0100
+
 bombardier (0.8.3+nmu1) unstable; urgency=low
 
   * Non-maintainer upload.
diff --minimal -Nru bombardier-0.8.3+nmu1/debian/rules 
bombardier-0.8.3+nmu2/debian/rules
--- bombardier-0.8.3+nmu1/debian/rules  2010-02-10 10:15:58.0 +0100
+++ bombardier-0.8.3+nmu2/debian/rules  2019-02-24 14:19:00.0 +0100
@@ -3,7 +3,7 @@
 build: build-stamp
 build-stamp:
dh_testdir
-   $(MAKE)
+   dh_auto_build
touch build-stamp
 
 clean:

Bug#923150: libmsv FTCBFS: does not pass --host to ./configure

[Helmut Grohne]

Source: libmsv
Version: 1.1.1-2
Tags: patch
User: helm...@debian.org
Usertags: rebootstrap

libmsv fails to cross build from source, because it does not pass --host
to ./configure. It actually computes the right flags in $(CONFARGS) and
then fails to use them. It also uses the build architecture strip. It
actually computes the right strip in $(STRIP) and then fails to use it.
The attached patch fixes that and makes libmsv cross buildable. Please
consider applying it.

Helmut
diff --minimal -Nru libmsv-1.1.1/debian/changelog libmsv-1.1.1/debian/changelog
--- libmsv-1.1.1/debian/changelog   2018-02-04 15:27:07.0 +0100
+++ libmsv-1.1.1/debian/changelog   2019-02-24 14:25:10.0 +0100
@@ -1,3 +1,10 @@
+libmsv (1.1.1-2.1) UNRELEASED; urgency=medium
+
+  * Non-maintainer upload.
+  * Fix FTCBFS: Use $(CONFARGS) and $(STRIP). (Closes: #-1)
+
+ -- Helmut Grohne   Sun, 24 Feb 2019 14:25:10 +0100
+
 libmsv (1.1.1-2) unstable; urgency=medium
 
   * Build-depend on file.  closes: #889521
diff --minimal -Nru libmsv-1.1.1/debian/rules libmsv-1.1.1/debian/rules
--- libmsv-1.1.1/debian/rules   2018-02-03 21:20:23.0 +0100
+++ libmsv-1.1.1/debian/rules   2019-02-24 14:25:10.0 +0100
@@ -28,7 +28,7 @@
 build-indep: build-arch
 build-arch: stamp-build
 stamp-build: configure
-   ./configure --prefix=/usr CFLAGS="$(CFLAGS)" CPPFLAGS="$(CPPFLAGS)" 
LDFLAGS="$(LDFLAGS)"
+   ./configure $(CONFARGS) --prefix=/usr CFLAGS="$(CFLAGS)" 
CPPFLAGS="$(CPPFLAGS)" LDFLAGS="$(LDFLAGS)"
$(MAKE)
doxygen libmsvdox.cfg
touch $@
@@ -71,7 +71,7 @@
gzip -9fn debian/$(devpkg)/usr/share/doc/$(devpkg)/changelog.Debian
 
 ifeq (,$(findstring nostrip,$(DEB_BUILD_OPTIONS)))
-   strip debian/$(package)/usr/lib/*.so.*
+   $(STRIP) debian/$(package)/usr/lib/*.so.*
 endif
$(INSTALL_SCRIPT) debian/$(package).postinst 
debian/$(package)/DEBIAN/postinst
cd debian/$(package) && find * -type f ! -regex '^DEBIAN/.*' -print0 | 
LC_ALL=C sort -z | xargs -r0 md5sum > DEBIAN/md5sums

Bug#912381: xen-utils-4.11: /usr/lib/xen-4.11/bin/pygrub is missing after upgrade from xen-utils-4.8

[Alexander Dahl]

Hei hei,

On Wed, 31 Oct 2018 19:16:11 +0100 Hans van Kranenburg 
 wrote:

> An alternative that might help you now might be to switch to pvgrub2?

This is an alternative for Debian virtual machines. At least I use 
pygrub to boot other distributions, which don't have pvgrub.


So thanks for fixing pygrub! :-)

Greets
Alex

Bug#922984: xml-security-c: ECDSA XML signature generation segmentation fault

[Alejandro Claro Mosqueda]

Good evening Mr. Wagner,

Thank you very much.

We have not validated a scenario like you mention. Our use cases, related to 
this XML signature generation, are not susceptible to exploit such 
vulnerability; but I think it could be possible in other use cases. In our use 
case, we experience inestability of the system due to an unpredictable 
segmentation fault in the library.

Thanks,
Alejandro.

Get Outlook for Android


From: Ferenc Wagner,,,  on behalf of wf...@niif.hu 

Sent: Sunday, February 24, 2019 2:17:03 PM
To: Alejandro Claro Mosqueda
Cc: 922...@bugs.debian.org
Subject: Re: Bug#922984: xml-security-c: ECDSA XML signature generation 
segmentation fault

Alejandro Claro  writes:

> We found a bug in Apache Santuario C, related to ECDSA signature
> generation, few years ego. We provide the fix to the Apache team, and
> Scott Cantor kindly accepted the fix in the project. How ever the fix
> was introduced in series 2.x of the the library.

Dear Alejandro,

I can propose your fix for the next stable update, but I don't know when
that will be released.  On the other hand, if this buffer overflow leads
to an exploitable vulnerability, the Security Team could fast-track the
fix.  Have you got such a scenario?
--
Thanks,
Feri

Bug#923151: "unknown reason 'attempt-reconnect'" when using openconnect 8.02-1

[Yuri D'Elia]

Package: vpnc-scripts
Version: 0.1~git20180227-1
Severity: normal

When using openconnect 8.02-1 and network connection is lost, the
reconnection attempt shows this error:

CSTP Dead Peer Detection detected dead peer!
unknown reason 'attempt-reconnect'. Maybe vpnc-script is out of date
Script '/usr/share/vpnc-scripts/vpnc-script' returned error 1

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

Kernel: Linux 4.20.0-trunk-amd64 (SMP w/8 CPU cores)
Kernel taint flags: TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE
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 vpnc-scripts depends on:
ii  iproute2  4.20.0-2

vpnc-scripts recommends no packages.

Versions of packages vpnc-scripts suggests:
pn  dnsmasq 
ii  openssh-server  1:7.9p1-6
pn  resolvconf  

Bug#921176: redis-server service is failing to start in buster lxc container

[intrigeri]

Control: reassign -1 lxc
Control: severity -1 important

Hi,

Pirate Praveen:
> In dmesg inside container (same error on the host as well), so it seems 
> apparmor is blocking it.

> [14760.307180] audit: type=1400 audit(1549992481.311:156): 
> apparmor="DENIED" operation="mount" info="failed flags match" error=-13 
> profile="lxc-container-default-cgns" name="/" pid=20531 
> comm="(s-server)" flags="rw, rslave"

The lxc-container-default-cgns profile is shipped by the lxc
package ⇒ reassigning.

This looks very much like LXC bug #916639 so please retry with:
lxc 1:3.1.0+really3.0.3-3 or newer?

If that's not sufficient, you might need to set these options for
your container:

   lxc.apparmor.profile = generated
   lxc.apparmor.allow_nesting = 1

(On sid, these settings are in /etc/lxc/default.conf already but I'm
not familiar with LXC and I don't know if they'll apply to
pre-existing containers.)

Thanks in advance!

Also, I'm setting severity to non-RC as it would be unfortunate to
block the migration to testing of… the very version that likely fixes
this bug. Once it's clarified that this is #916639, I'll fix
the metadata.

Cheers,
-- 
intrigeri

Bug#916644: Adjust LXC containers' AppArmor configuration once ci.debian.net runs Buster

[intrigeri]

Hi,

these settings are now in /etc/lxc/default.conf (as of lxc
1:3.1.0+really3.0.3-3) so depending on how debci sets things up, you
might actually not have to do anything once you update the hosts
to Buster.

Cheers,
-- 
intrigeri

Bug#914632: uw-imap: CVE-2018-19518

[Magnus Holmgren]

lördag 23 februari 2019 kl. 15:26:25 CET skrev  Salvatore Bonaccorso:
> On Sun, Jan 13, 2019 at 06:24:36PM +0100, Magnus Holmgren wrote:
> > söndag 13 januari 2019 kl. 08:31:28 CET skrev  Salvatore Bonaccorso:
> > > On Fri, Dec 28, 2018 at 10:22:53AM +0100, Moritz Mühlenhoff wrote:
> > > > On Wed, Dec 26, 2018 at 05:20:40PM +0100, Magnus Holmgren wrote:
> > > > > I'm wondering if anyone would complain if I'd disable RSH (SSH)
> > > > > connections
> > > > > altogether.
> > > > 
> > > > Full ack, that seems like the most sensible fix.
> > > 
> > > Any news on this approach, or did you spot any problem with that way?
> > 
> > Here's my plan. Removing the RSHPATH define should disable the insecure
> > code, I reckon. I just haven't been able to make gbp use my long PGP key
> > id...
> Any news on this?

I thought I'd write a NEWS.Debian entry about disabling RSH, but then I 
realised it wouldn't be disabled completely, only by default; code using the 
library can still set rshpath by calling tcp_parameters(SET_RSHPATH, path). 
But maybe that's just fine. I also haven't got around to actually verifying 
that the patch works as intended.

Perhaps wanting to run imapd via remote shell is so rare that there's no need 
to write a NEWS.Debian entry?

-- 
Magnus Holmgrenholmg...@debian.org
Debian Developer 

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

Bug#879010: diffoscope: Add an option to exclude file lists differences

[Chris Lamb]

Hi Mike,

> diffoscope: Add an option to exclude file lists differences

Can I direct you to this comment I just added upstream?

  https://salsa.debian.org/reproducible-builds/diffoscope/issues/24#note_66890

If replying, please do so on Gitlab; thank you.


Regards,

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

Bug#923001: error message on start

[Markus Koschany]

Control: severity -1 important

On Sat, 23 Feb 2019 21:20:42 -0500 Michael Gilbert 
wrote:
> control: severity -1 serious
> 
> Increasing severity since policy 10.7.3 is violated:
> 
> "Obsolete configuration files without local changes should be removed
> by the package during upgrade."
> 
> The file in /etc/chromium.d is obsolete.
> 
> Best wishes,
> Mike

Should does not mean must but I intend to remove it anyway.

Markus



signature.asc
Description: OpenPGP digital signature

Bug#916639: LXC AppArmor confinement breaks systemd v240

[intrigeri]

Hi,

Pierre-Elliott Bécue:
> Please review and comment:

>  - 
> https://salsa.debian.org/lxc-team/lxc/commit/1e8ca3640eec0b82297314d10435b68918907fc8
>(patch inclusion)
>  - 
> https://salsa.debian.org/lxc-team/lxc/commit/84df6216317542961bbad08a08e159f38e623de7
>(minimalist default.conf)

Looks good to me, thanks!

> Could you also provide me with a paragraph I could put in README.Debian
> and NEWS regarding what end users should know about these profiles.

> You dived in it more than me and I don't rely on apparmor, so it'd be
> better if you write it.

> Otherwise I can try to write a relevant thing.

Now that /etc/lxc/default.conf has permissive enough settings, I'm not
sure whether we should tell users anything particular about these
profiles: things should work out of the box.

Unfortunately, even on the upstream master branch,
lxc.container.conf(5) does not document our new default settings
("lxc.apparmor.profile = generated" and "lxc.apparmor.allow_nesting"),
which is a bit inconvenient. But thankfully, in case AppArmor breaks
LXC things for users, that manpage documents how to specify that
a given container should run unconfined, i.e. rollback to how things
were by default on Stretch, so perhaps that's good enough?

Cheers!
-- 
intrigeri

Bug#923013: [Pkg-xen-devel] Bug#923013: xen: FTBFS when built with dpkg-buildpackage -A

[Santiago Vila]

> All of this seems to be related to the dh-exec usage for putting files
> in the xen-utils-common package with a different name. This is the first
> time this package is using dh-exec.
>
> [...]
> 
> Interestingly, 'etc/default/xencommons => /etc/default/xen' does not
> result in a similar error?
> 
> I also found this one, which seems to be related:
> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=831786
> 
> Do you have an idea / suggestion how we can deal with this?

Based on your analysis, maybe applying the patch below.

After all, the "fail-missing" thing is just an extra protection which
helps avoiding mistakes when installing things, but in this case
it seems to be more troublesome than helpful.

--- a/debian/rules
+++ b/debian/rules
@@ -307,8 +307,11 @@ override_dh_compress:
 
 # By default, files in debian/tmp which are not handled by anything
 # in rules are ignored.  This makes them into errors.
-override_dh_missing:
-   dh_missing --fail-missing
+#
+# Disabled because of Bug #831786
+#
+# override_dh_missing:
+#  dh_missing --fail-missing
 
 
 # We are dropping the config file /etc/default/xen which appeared in

Thanks.

Bug#874326: [PATCH 2/3] private-update: return early if `ListUpdate()` fails

[Martin Ågren]

`ListUpdate()` returns a bool to indicate whether locking succeeded or
not, but we don't look at the return value. Teach the caller to return
early if `ListUpdate()` returns false.

To give a concrete example, this means that a non-root user with the
default configuration will see this on `apt-get update`:

  E: Could not open lock file /var/lib/apt/lists/lock - open (13: Permission 
denied)
  E: Unable to lock directory /var/lib/apt/lists/

as opposed to also seeing a couple of follow-on warnings:

  W: Problem unlinking the file /var/cache/apt/pkgcache.bin - RemoveCaches (13: 
Permission denied)
  W: Problem unlinking the file /var/cache/apt/srcpkgcache.bin - RemoveCaches 
(13: Permission denied)
---
 apt-private/private-update.cc|  3 ++-
 test/integration/test-apt-update-locking | 18 ++
 2 files changed, 20 insertions(+), 1 deletion(-)
 create mode 100755 test/integration/test-apt-update-locking

diff --git a/apt-private/private-update.cc b/apt-private/private-update.cc
index c9113ddd3..d56593505 100644
--- a/apt-private/private-update.cc
+++ b/apt-private/private-update.cc
@@ -69,7 +69,8 @@ bool DoUpdate(CommandLine &CmdL)
if (_config->FindB("APT::Get::Download",true) == true)
{
   AcqTextStatus Stat(std::cout, ScreenWidth,_config->FindI("quiet",0));
-  ListUpdate(Stat, *List);
+  if (ListUpdate(Stat, *List) == false)
+return false;
}
 
if (_config->FindB("pkgCacheFile::Generate", true) == false)
diff --git a/test/integration/test-apt-update-locking 
b/test/integration/test-apt-update-locking
new file mode 100755
index 0..e2e1e3649
--- /dev/null
+++ b/test/integration/test-apt-update-locking
@@ -0,0 +1,18 @@
+#!/bin/sh
+set -e
+
+TESTDIR="$(readlink -f "$(dirname "$0")")"
+. "$TESTDIR/framework"
+setupenvironment
+configarchitecture 'amd64'
+
+setupaptarchive
+
+rm "$TMPWORKINGDIRECTORY/rootdir/var/lib/apt/lists/lock"
+# mkdir() in the framework is too clever for us, so avoid it
+command mkdir "$TMPWORKINGDIRECTORY/rootdir/var/lib/apt/lists/lock"
+testfailure aptget update
+cp "${TMPWORKINGDIRECTORY}/rootdir/tmp/testfailure.output" 
"${TMPWORKINGDIRECTORY}/rootdir/tmp/testfailure"
+testsuccess grep "^E: Could not open lock file" 
"${TMPWORKINGDIRECTORY}/rootdir/tmp/testfailure"
+testsuccess grep "^E: Unable to lock directory" 
"${TMPWORKINGDIRECTORY}/rootdir/tmp/testfailure"
+testfailure grep "^W: " "${TMPWORKINGDIRECTORY}/rootdir/tmp/testfailure"
-- 
2.21.0.rc2.5.gc65a2884ea

Bug#923152: vim-addon-manager: Please don't rely on Etc.getlogin()

[David Rabel]

Package: vim-addon-manager
Version: 0.5.9
Severity: normal

Dear Maintainer,

in Line 202 (parse_cmdline) you call Etc.getlogin and Etc.getpwnam, but this
fails under certain circumstances. For example when called by a daemon.
We (vim-lastplace) use vim-addon-manager in our maintainer scripts, so this can
lead to errors with automatic updates:

https://bugs.launchpad.net/ubuntu/+source/vim-lastplace/+bug/1811935
https://launchpadlibrarian.net/406433346/DpkgTerminalLog.txt

/usr/bin/vim-addon-manager:202:in `getpwnam': no implicit conversion of nil
into String (TypeError)
from /usr/bin/vim-addon-manager:202:in `parse_cmdline'
from /usr/bin/vim-addon-manager:252:in `'

Could you change the code not to call Etc.getlogin and Etc.getpwnam when not
needed (when using -w parameter)?

Handling the case when getlogin returns Null and throwing a useful error
message also would be great.

Yours
  David



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

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

Versions of packages vim-addon-manager depends on:
ii  ruby1:2.5.1
ii  vim-common  2:8.1.0875-2

Versions of packages vim-addon-manager recommends:
ii  vim  2:8.1.0875-2

vim-addon-manager suggests no packages.

-- no debconf information

Bug#874326: [PATCH 0/3] acquire: hint if locking fails and we're not root

[Martin Ågren]

Here's my attempt at addressing this bug as a three-patch series. The
first patch feels a bit awkward, but I've based it on the assumption
that tests that verify an exact output do so because they want to keep
that exact output.

The integration tests test-apt-ftparchive-cachedb-lp1274466 and
test-apt-key always fail for me, even without these patches. I suppose
there's a small chance these patches break those tests without me
noticing. My apologies if so.

Any feedback welcome. I'll be happy to rework these if you think this
bug should be approached differently.

Cheers
Martin

Martin Ågren (3):
  update: let `ListUpdate()` return false only if locking fails
  private-update: return early if `ListUpdate()` fails
  acquire: hint if locking fails and we're not root

 apt-pkg/acquire.cc   |  8 +++-
 apt-pkg/update.cc|  9 ++---
 apt-private/private-update.cc|  3 ++-
 test/integration/test-apt-update-locking | 23 +++
 4 files changed, 38 insertions(+), 5 deletions(-)
 create mode 100755 test/integration/test-apt-update-locking

-- 
2.21.0.rc2.5.gc65a2884ea

Bug#874326: [PATCH 3/3] acquire: hint if locking fails and we're not root

[Martin Ågren]

With the default configuration, if a non-root user runs `apt-get
update`, we emit errors like this:

  E: Could not open lock file /var/lib/apt/lists/lock - open (13: Permission 
denied)
  E: Unable to lock directory /var/lib/apt/lists/

The previous commit reduced the noise a bit, but we can also be more
helpful in our reporting. If locking fails and we're not running as
root, hint that this might be the cause of our problem.

Of course, the problem could be something else entirely and trying to
diagnose all possible causes for our problem is infeasible. But there's
a fair chance this hint will cover most of the cases, and it could be
particularly helpful to less experienced users.
---
 apt-pkg/acquire.cc   | 8 +++-
 test/integration/test-apt-update-locking | 5 +
 2 files changed, 12 insertions(+), 1 deletion(-)

diff --git a/apt-pkg/acquire.cc b/apt-pkg/acquire.cc
index 541785b03..7b6e9a372 100644
--- a/apt-pkg/acquire.cc
+++ b/apt-pkg/acquire.cc
@@ -181,7 +181,13 @@ bool pkgAcquire::GetLock(std::string const &Lock)
   close(LockFD);
LockFD = ::GetLock(flCombine(Lock, "lock"));
if (LockFD == -1)
-  return _error->Error(_("Unable to lock directory %s"), Lock.c_str());
+   {
+  _error->Error(_("Unable to lock directory %s"), Lock.c_str());
+  if (getuid() != 0)
+_error->Notice(_("You are not root; depending on your configuration, "
+ "that might explain why locking fails"));
+  return false;
+   }
 
return true;
 }
diff --git a/test/integration/test-apt-update-locking 
b/test/integration/test-apt-update-locking
index e2e1e3649..a797cd077 100755
--- a/test/integration/test-apt-update-locking
+++ b/test/integration/test-apt-update-locking
@@ -16,3 +16,8 @@ cp "${TMPWORKINGDIRECTORY}/rootdir/tmp/testfailure.output" 
"${TMPWORKINGDIRECTOR
 testsuccess grep "^E: Could not open lock file" 
"${TMPWORKINGDIRECTORY}/rootdir/tmp/testfailure"
 testsuccess grep "^E: Unable to lock directory" 
"${TMPWORKINGDIRECTORY}/rootdir/tmp/testfailure"
 testfailure grep "^W: " "${TMPWORKINGDIRECTORY}/rootdir/tmp/testfailure"
+if [ "$(id -u)" = '0' ]; then
+   testfailure grep "^N: You are not root" 
"${TMPWORKINGDIRECTORY}/rootdir/tmp/testfailure"
+else
+   testsuccess grep "^N: You are not root" 
"${TMPWORKINGDIRECTORY}/rootdir/tmp/testfailure"
+fi
-- 
2.21.0.rc2.5.gc65a2884ea

Bug#874326: [PATCH 1/3] update: let `ListUpdate()` return false only if locking fails

[Martin Ågren]

No-one is looking at the return value of this function, but we'll start
doing that in the next commit, in order to stop further work if locking
fails. But we have several tests which actually expect us to continue if
`List.GetIndexes()` or `AcquireUpdate()` returns false, so let's first
make sure we don't propagate their return values.

Rather than returning a bool here, which forces us to separate "locking
error" from "any other problem, or success", we could return more
fine-grained information. But considering how no-one has looked at this
return value for many years, such more informational return values can
wait until we actually need them.
---
 apt-pkg/update.cc | 9 ++---
 1 file changed, 6 insertions(+), 3 deletions(-)

diff --git a/apt-pkg/update.cc b/apt-pkg/update.cc
index 4c64eeb5d..4458331b9 100644
--- a/apt-pkg/update.cc
+++ b/apt-pkg/update.cc
@@ -20,7 +20,9 @@ using namespace std;
 // ListUpdate - construct Fetcher and update the cache files   /*{{{*/
 // -
 /* This is a simple wrapper to update the cache. it will fetch stuff
- * from the network (or any other sources defined in sources.list)
+ * from the network (or any other sources defined in sources.list).
+ * The return value is false if we fail to get the lock, and true
+ * otherwise.
  */
 bool ListUpdate(pkgAcquireStatus &Stat, 
pkgSourceList &List, 
@@ -32,9 +34,10 @@ bool ListUpdate(pkgAcquireStatus &Stat,
 
// Populate it with the source selection
if (List.GetIndexes(&Fetcher) == false)
-return false;
+  return true;
 
-   return AcquireUpdate(Fetcher, PulseInterval, true);
+   AcquireUpdate(Fetcher, PulseInterval, true);
+   return true;
 }
/*}}}*/
 // AcquireUpdate - take Fetcher and update the cache files /*{{{*/
-- 
2.21.0.rc2.5.gc65a2884ea

Bug#921667: [pkg-apparmor] Bug#921667: lxc, lava-dev: lxc fails to install along lava-dev --install-recommends

[intrigeri]

Hi,

Pierre-Elliott Bécue:
   Setting up lxc (1:3.1.0+really3.0.3-2) ...
   Warning from stdin (line 1): config file '/etc/apparmor/parser.conf' not 
 found
   Cache read/write disabled: interface file missing. (Kernel needs 
 AppArmor 2.4 compatibility patch.)
   Warning: unable to find a suitable fs in /proc/mounts, is it mounted?
   Use --subdomainfs to override.
   dpkg: error processing package lxc (--configure):
installed lxc package post-installation script subprocess
returned error exit status 1

 >> > See my staged commits.
>> > 
>> > https://salsa.debian.org/lxc-team/lxc/commit/a0e6b5f26227236e44ab8ff4cee745228201bb7d

typo: s/runn/run/

>> weirdy, if you first install apparmor, then install lxc in a separate
>> apt invocaation, it works just fine. and, if you do `apt install -f`
>> after the initial failure, it also works fine.

> I think it's a matter of AppArmor doing some magic at the end via a
> trigger.

apparmor.postinst starts apparmor.service on package configuration; so
far, that's pretty much standard; but then apparmor.service mounts
securityfs if it was not mounted yet… and apparmor_parser uses
securityfs to interact with the Linux kernel.

lxc.postinst calls apparmor_parser. So if lxc is configured before
apparmor, indeed the call to "apparmor_parser -r -W -T
/etc/apparmor.d/lxc-containers" will fail.

FTR dh-apparmor handles this situation by generating this postinst
code snippet, which is equivalent to what lxc.postinst has, modulo
different output:

if aa-enabled --quiet 2>/dev/null; then
apparmor_parser -r -T -W "$APP_PROFILE" || true
fi

This is clearly not ideal, because depending on package configuration
ordering, some profiles may be loaded and some might not be.

I've not thought much about this problem yet, but I suspect that for
service packages such as LXC, handling this sort of things at the
systemd unit level might give us more robust ordering than what we're
currently doing via postinst. Food for thought :)

Cheers,
-- 
intrigeri

Bug#923154: manpage created for old binary

[Osamu Aoki]

Package: mecab
Version: 0.996-6
Severity: minor
Tags: upstream
Forwarded: https://github.com/taku910/mecab/pull/50

Manpage was generated with mecab of 0.98pre1 binary.

It best to be regenerated.

More over, it should be more than mere help2man output.

I have created pull request to upstream:
  https://github.com/taku910/mecab/pull/50

Basically, this updates manpage to as attached.

Now -O "" is highlighted !

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

Kernel: Linux 4.19.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:en (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages mecab depends on:
ii  libc6 2.28-7
ii  libgcc1   1:8.2.0-20
ii  libmecab2 0.996-6
ii  libstdc++68.2.0-20
ii  mecab-ipadic  2.7.0-20070801+main-2
ii  mecab-jumandic7.0-20130310-7
ii  mecab-jumandic-utf8 [mecab-jumandic]  7.0-20130310-7

mecab recommends no packages.

mecab suggests no packages.

-- no debconf information
.\" DO NOT MODIFY THIS FILE!  It was generated by help2man 1.47.8.
.TH MECAB "1" "February 2019" "mecab of 0.996" "User Commands"
.SH NAME
mecab \- Yet Another Part\-of\-Speech and Morphological Analyzer
.SH SYNOPSIS
.B mecab
[\fI\,options\/\fR] \fI\,files\/\fR
.SH DESCRIPTION
Mecab is a morphological analysis system.  It reads continuous text sentences
such as Japanese ones from the standard input, segments them into morpheme
sequences, and outputs them to the standard output with many additional pieces
of information (pronunciation, semantic information, etc).
.SH OPTIONS
.TP
\fB\-r\fR, \fB\-\-rcfile\fR=\fI\,FILE\/\fR
use FILE as resource file
.TP
\fB\-d\fR, \fB\-\-dicdir\fR=\fI\,DIR\/\fR
set DIR  as a system dicdir
.TP
\fB\-u\fR, \fB\-\-userdic\fR=\fI\,FILE\/\fR
use FILE as a user dictionary
.TP
\fB\-l\fR, \fB\-\-lattice\-level\fR=\fI\,INT\/\fR
lattice information level (DEPRECATED)
.TP
\fB\-D\fR, \fB\-\-dictionary\-info\fR
show dictionary information and exit
.TP
\fB\-O\fR, \fB\-\-output\-format\-type\fR=\fI\,TYPE\/\fR
set output format type (SEE OUTPUT FORMAT)
.TP
\fB\-a\fR, \fB\-\-all\-morphs\fR
output all morphs(default false)
.TP
\fB\-N\fR, \fB\-\-nbest\fR=\fI\,INT\/\fR
output N best results (default 1)
.TP
\fB\-p\fR, \fB\-\-partial\fR
partial parsing mode (default false)
.TP
\fB\-m\fR, \fB\-\-marginal\fR
output marginal probability (default false)
.TP
\fB\-M\fR, \fB\-\-max\-grouping\-size\fR=\fI\,INT\/\fR
maximum grouping size for unknown words (default 24)
.TP
\fB\-F\fR, \fB\-\-node\-format\fR=\fI\,STR\/\fR
use STR as the user\-defined node format
.TP
\fB\-U\fR, \fB\-\-unk\-format\fR=\fI\,STR\/\fR
use STR as the user\-defined unknown node format
.TP
\fB\-B\fR, \fB\-\-bos\-format\fR=\fI\,STR\/\fR
use STR as the user\-defined beginning\-of\-sentence format
.TP
\fB\-E\fR, \fB\-\-eos\-format\fR=\fI\,STR\/\fR
use STR as the user\-defined end\-of\-sentence format
.TP
\fB\-S\fR, \fB\-\-eon\-format\fR=\fI\,STR\/\fR
use STR as the user\-defined end\-of\-NBest format
.TP
\fB\-x\fR, \fB\-\-unk\-feature\fR=\fI\,STR\/\fR
use STR as the feature for unknown word
.TP
\fB\-b\fR, \fB\-\-input\-buffer\-size\fR=\fI\,INT\/\fR
set input buffer size (default 8192)
.TP
\fB\-P\fR, \fB\-\-dump\-config\fR
dump MeCab parameters
.TP
\fB\-C\fR, \fB\-\-allocate\-sentence\fR
allocate new memory for input sentence
.TP
\fB\-t\fR, \fB\-\-theta\fR=\fI\,FLOAT\/\fR
set temparature parameter theta (default 0.75)
.TP
\fB\-c\fR, \fB\-\-cost\-factor\fR=\fI\,INT\/\fR
set cost factor (default 700)
.TP
\fB\-o\fR, \fB\-\-output\fR=\fI\,FILE\/\fR
set the output file name
.TP
\fB\-v\fR, \fB\-\-version\fR
show the version and exit.
.TP
\fB\-h\fR, \fB\-\-help\fR
show this help and exit.
.SH "OUTPUT FORMAT"

The default output format and the selectable output formats from the
\fB\-O\fR option argument are defined in the resource file.
There are few special hard coded formats.

.TP
\fB""\fR (null string)
disable format setting of resource file.  This is required to set user\-defined
format from the command line.
.TP
\fBwakati\fR
output each node separated by a space
.TP
\fBdump\fR
dump all node data in one line 
.TP
\fBnone\fR
no output

.PP
See  for details of format
definition.

.SH DICTIONARY

See 
.IP \(bu 4

.IP \(bu 4

.PP
for details of preparation and updating of the mecab dictionary.

.SH EXAMPLE

Output reading in KataKana with installed and fully configured UniDic.

$ mecab -O "" -F"%pS%f[9]" -U"%M" -E"\\n" https://taku910.github.io/mecab/>

Bug#923153: openssh-server: OpenSSH is not "OpenBSD Secure Shell" /etc/init.d/ssh

[Hocus Pocus]

Package: openssh-server
Version: 1:7.7p1-4ubuntu0.2
Severity: normal

Dear Maintainer,

OpenSSH is not "OpenBSD Secure Shell". That's it.
So /etc/init.d/ssh should changed.

Here is the patch.

--- openssh-server.ssh.init 2019-02-09 01:26:35.0 +0900
+++ openssh-server.ssh.init.new 2019-02-24 23:36:26.415783651 +0900
@@ -6,12 +6,12 @@
 # Required-Stop:   $remote_fs $syslog
 # Default-Start:   2 3 4 5
 # Default-Stop:
-# Short-Description:   OpenBSD Secure Shell server
+# Short-Description:   OpenSSH server
 ### END INIT INFO
 
 set -e
 
-# /etc/init.d/ssh: start and stop the OpenBSD "secure shell(tm)" daemon
+# /etc/init.d/ssh: start and stop the OpenSSH daemon
 
 test -x /usr/sbin/sshd || exit 0
 ( /usr/sbin/sshd -\? 2>&1 | grep -q OpenSSH ) 2>/dev/null || exit 0
@@ -40,7 +40,7 @@
log_end_msg 0 || true
fi
if ! run_by_init; then
-   log_action_msg "OpenBSD Secure Shell server not in use 
(/etc/ssh/sshd_not_to_be_run)" || true
+   log_action_msg "OpenSSH server not in use 
(/etc/ssh/sshd_not_to_be_run)" || true
fi
exit 0
 fi
@@ -79,7 +79,7 @@
check_privsep_dir
check_for_no_start
check_dev_null
-   log_daemon_msg "Starting OpenBSD Secure Shell server" "sshd" || true
+   log_daemon_msg "Starting OpenSSH server" "sshd" || true
if start-stop-daemon --start --quiet --oknodo --pidfile /run/sshd.pid 
--exec /usr/sbin/sshd -- $SSHD_OPTS; then
log_end_msg 0 || true
else
@@ -87,7 +87,7 @@
fi
;;
   stop)
-   log_daemon_msg "Stopping OpenBSD Secure Shell server" "sshd" || true
+   log_daemon_msg "Stopping OpenSSH server" "sshd" || true
if start-stop-daemon --stop --quiet --oknodo --pidfile /run/sshd.pid; 
then
log_end_msg 0 || true
else
@@ -98,7 +98,7 @@
   reload|force-reload)
check_for_no_start
check_config
-   log_daemon_msg "Reloading OpenBSD Secure Shell server's configuration" 
"sshd" || true
+   log_daemon_msg "Reloading OpenSSH server's configuration" "sshd" || true
if start-stop-daemon --stop --signal 1 --quiet --oknodo --pidfile 
/run/sshd.pid --exec /usr/sbin/sshd; then
log_end_msg 0 || true
else
@@ -109,7 +109,7 @@
   restart)
check_privsep_dir
check_config
-   log_daemon_msg "Restarting OpenBSD Secure Shell server" "sshd" || true
+   log_daemon_msg "Restarting OpenSSH server" "sshd" || true
start-stop-daemon --stop --quiet --oknodo --retry 30 --pidfile 
/run/sshd.pid
check_for_no_start log_end_msg
check_dev_null log_end_msg
@@ -123,7 +123,7 @@
   try-restart)
check_privsep_dir
check_config
-   log_daemon_msg "Restarting OpenBSD Secure Shell server" "sshd" || true
+   log_daemon_msg "Restarting OpenSSH server" "sshd" || true
RET=0
start-stop-daemon --stop --quiet --retry 30 --pidfile /run/sshd.pid || 
RET="$?"
case $RET in


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

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

Versions of packages openssh-server depends on:
ii  adduser3.117ubuntu1
ii  debconf [debconf-2.0]  1.5.69
ii  dpkg   1.19.0.5ubuntu5
ii  libaudit1  1:2.8.3-1ubuntu2
ii  libc6  2.28-0ubuntu1
ii  libcom-err21.44.4-2ubuntu0.2
ii  libgssapi-krb5-2   1.16-2ubuntu1.1
ii  libkrb5-3  1.16-2ubuntu1.1
ii  libpam-modules 1.1.8-3.6ubuntu2
ii  libpam-runtime 1.1.8-3.6ubuntu2
ii  libpam0g   1.1.8-3.6ubuntu2
ii  libselinux12.8-1build1
ii  libssl1.0.01.0.2n-1ubuntu6.1
ii  libsystemd0239-7ubuntu10.8
ii  libwrap0   7.6.q-27
ii  lsb-base   9.20170808ubuntu1
ii  openssh-client 1:7.7p1-4ubuntu0.2
ii  openssh-sftp-server1:7.7p1-4ubuntu0.2
ii  procps 2:3.3.15-2ubuntu1
ii  ucf3.0038
ii  zlib1g 1:1.2.11.dfsg-0ubuntu2

Versions of packages openssh-server recommends:
ii  libpam-systemd  239-7ubuntu10.8
ii  ncurses-term6.1+20180210-4ubuntu1
ii  ssh-import-id   5.7-24-g4001a38e-0ubuntu1
ii  xauth   1:1.0.10-1

Versions of packages openssh-server suggests:
ii  ksshaskpass [ssh-askpass]  4:5.13.5-0ubuntu1
pn  molly-guard
pn  monkeysphere   
pn  rssh   
ii  ufw0.35-6

-- debconf information:
  openssh-server/permit-root-login: true
  openssh-server/password-authent

Bug#923115: cups-client: cupsctl needs to edit `cups-files.conf`

[Didier 'OdyX' Raboud]

Control: tags -1 +upstream
Control: forwarded -1 https://github.com/apple/cups/issues/5530

Le dimanche, 24 février 2019, 10.43:09 h CET Paul Menzel a écrit :
> `/usr/sbin/cupsctl FileDevice=No` edits `/etc/cups/cupsd.conf` instead
> of `/etc/cups/cups-files.conf`.
> 
> ```
> /etc$ /usr/sbin/cupsctl FileDevices=No
> /etc$ sudo git diff
> diff --git a/cups/cupsd.conf b/cups/cupsd.conf
> index 02afed2..c347852 100644
> --- a/cups/cupsd.conf
> +++ b/cups/cupsd.conf
> @@ -119,3 +119,4 @@ WebInterface Yes
>   Order deny,allow
> 
>   
> +FileDevice Yes
> ```

Thanks for your report. That's indeed a bug that should be fixed upstream; 
reported as: https://github.com/apple/cups/issues/5530

Cheers,
OdyX

Bug#923056: systemsettings: diff for NMU version 4:5.14.5-1.1

[Maximiliano Curia]

¡Hola Boyuan!

El 2019-02-23 a las 13:23 -0500, Boyuan Yang escribió:

Package: systemsettings
Version: 4:5.14.5-1
Severity: normal
Tags: patch  pending



I've prepared an NMU for systemsettings (versioned as 4:5.14.5-1.1) and
uploaded it to DELAYED/3. Please feel free to tell me if I
should delay it longer.



On behalf of Debian Chinese Team and KDE translation team for zh_CN
(Simplified Chinese), I'm proposing a patch to fix a zh_CN translation error
within systemsettings.desktop. Nothing else is touched.



This issue is fixed upstream with the release of Plasma 5.15. Please drop this
patch after we package Plasma 5.15 into Debian.


Thanks for your work, sadly the attached patch got mangled in the email 
transmission, could please send it as an attachment? Or better yet, could you 
create a new MR in the salsa project [1]?


[1]: https://salsa.debian.org/qt-kde-team/kde/systemsettings

Happy hacking,
--
Porque no respeta el orden natural en el que se leen las cosas

¿Por qué contestar al principio del mensaje es malo?

Saludos /\/\ /\ >< `/


signature.asc
Description: PGP signature

Bug#923155: impossible to save file: General input/output error

[Stanislav Maslovski]

Package: libreoffice-writer
Version: 1:6.1.5-1
Severity: important

Hi,

After a recent upgrade from Debian stable to testing I am getting a
very strange error in LibreOffice Writer, when trying to save a
document to the local hard drive. This never happened to me before on
this machine. To reproduce the bug, I just need to continue working on
a file and periodically press the Save button.

The error appears when trying to save the document. When working on
the text, I periodically click the "Save" button (a habbit I have from
the time when computers were big enough to fit a room, and
unreliable enough to destroy your work in a sudden freeze).
Anyway, after a series of succesfull saves, this strange error appears,
after which it is only possible to close the application and accept
the loss of the recently entered data.

I did a search on the internet, and found that some people experienced
the same problem before, notably, when saving to a network drive.
Let me stress, that here this problem appears when saving to the local
HDD. You can check, for example, this bug report:

https://bugs.documentfoundation.org/show_bug.cgi?id=113138

His simptoms are similar to mine, however, I do not have to erase the
LO profile in order to be able to save files in LibreOffice again.
Just closing and opening the application is enough, however, of
course, the recently entered data are lost anyway. Also, when this
error happens, the file length is not truncated to zero, and the file
still has the content from the last successfull save.

As this problem results in a loss of data, I set the severity of this
bug as important. 

BR,

Stanislav


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

Kernel: Linux 4.19.0-2-amd64 (SMP w/4 CPU cores)
Kernel taint flags: TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE
Locale: LANG=ru_RU.UTF-8, LC_CTYPE=ru_RU.UTF-8 (charmap=UTF-8), LANGUAGE=en 
(charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages libreoffice-writer depends on:
ii  libabw-0.1-1   0.1.2-1
ii  libc6  2.28-7
ii  libe-book-0.1-10.1.3-1+b2
ii  libepubgen-0.1-1   0.1.1-1
ii  libetonyek-0.1-1   0.1.9-1
ii  libgcc11:8.2.0-20
ii  libicu63   63.1-6
ii  liblangtag10.6.2-1
ii  libmwaw-0.3-3  0.3.14-1
ii  libodfgen-0.1-10.1.7-1
ii  libreoffice-base-core  1:6.1.5-1
ii  libreoffice-core   1:6.1.5-1
ii  librevenge-0.0-0   0.0.4-6
ii  libstaroffice-0.0-00.0.6-1
ii  libstdc++6 8.2.0-20
ii  libwpd-0.10-10 0.10.3-1
ii  libwpg-0.3-3   0.3.3-1
ii  libwps-0.4-4   0.4.10-1
ii  libxml22.9.4+dfsg1-7+b3
ii  uno-libs3  6.1.5-1
ii  ure6.1.5-1
ii  zlib1g 1:1.2.11.dfsg-1

Versions of packages libreoffice-writer recommends:
ii  libreoffice-math  1:6.1.5-1

Versions of packages libreoffice-writer suggests:
ii  default-jre [java6-runtime] 2:1.11-71
ii  fonts-crosextra-caladea 20130214-2
ii  fonts-crosextra-carlito 20130920-1
pn  libreoffice-base
ii  libreoffice-java-common 1:6.1.5-1
ii  openjdk-11-jre [java6-runtime]  11.0.2+9-3
ii  openjdk-8-jre [java6-runtime]   8u191-b12-2

Versions of packages libreoffice-core depends on:
ii  fontconfig2.13.1-2
ii  fonts-opensymbol  2:102.10+LibO6.1.5-1
ii  libboost-date-time1.67.0  1.67.0-13
ii  libboost-locale1.67.0 1.67.0-13
ii  libc6 2.28-7
ii  libcairo2 1.16.0-2
ii  libclucene-contribs1v52.3.3.4+dfsg-1
ii  libclucene-core1v52.3.3.4+dfsg-1
ii  libcmis-0.5-5v5   0.5.2-1
ii  libcups2  2.2.10-3
ii  libcurl3-gnutls   7.64.0-1
ii  libdbus-1-3   1.12.12-1
ii  libdbus-glib-1-2  0.110-4
ii  libdconf1 0.30.1-2
ii  libeot0   0.01-5
ii  libepoxy0 1.5.3-0.1
ii  libexpat1 2.2.6-1
ii  libexttextcat-2.0-0   3.4.5-1
ii  libfontconfig12.13.1-2
ii  libfreetype6  2.9.1-3
ii  libgcc1   1:8.2.0-20
ii  libglib2.0-0  2.58.3-1
ii  libgpgmepp6   1.12.0-6
ii  libgraphite2-31.3.13-7
ii  libharfbuzz-icu0  2.3.1-1
ii  libharfbuzz0b 2.3.1-1
ii  libhunspell-1.7-0 1.7.0-2
ii  libhyphen02.8.8-7
ii  libice6   2:1.0.9-2
ii  libicu63  63.1-6
ii  libjpeg62-turbo   1:1.5.2-2+b1
ii  liblcms2-22.9-3
ii  libldap-2.4-2 2.4.47+dfsg-3
ii  libmythes-1.2-0   2:1.2.4-3
ii  libneon27-gnutls  0.30.2-2
ii  

Bug#923133: mandelbulber2 FTCBFS: runs qmake for the build architecture

[Giovanni Mascellani]

Hi,

Il 24/02/19 11:37, Helmut Grohne ha scritto:
> mandelbulber2 fails to cross build from source, because it runs qmake
> without cross flags. The easiest way of adding the required flags is
> using dh_auto_configure. It also fails running lrelease, because it
> misses a dependency on qt5-qmake:native. The attached patch fixes both
> and makes mandelbulber2 cross buildable. Please consider applying it.

Thanks you very much for the patch!

Giovanni.
-- 
Giovanni Mascellani 
Postdoc researcher - Université Libre de Bruxelles



signature.asc
Description: OpenPGP digital signature

Bug#923156: keyutils autopkgtest shows failure on armhf

[Steve Langasek]

Source: keyutils
Version: 1.6-4
Severity: normal
User: ubuntu-de...@lists.ubuntu.com
Usertags: origin-ubuntu disco

Hi Christian,

I see that since 1.6-3, keyutils now tries to split its autopkgtests between
those that do require machine isolation, and those that do not.  This means
that for the first time, Ubuntu is able to run these tests on armhf, an
architecture for which we only have container runners, not VMs; and these
tests now show a test failure on armhf:

+++ ADD ONE ARG
Running with session keyring RHTS/keyctl/2648
keyutils version: keyctl from keyutils-1.6 (Built 2019-02-22)
=== /tmp/autopkgtest.K1pALO/autopkgtest_tmp/tests/keyctl/padd/useradd/test.out 
===
+++ ADD USER KEY
+++ PRINT PAYLOAD
+++ UPDATE USER KEY
+++ PRINT UPDATED PAYLOAD
+++ UNLINK KEY
+++ ADD LARGE USER KEY
FAILED
Unparsable key: 'no'
make: *** [Makefile:41: run] Error 1
FAILED
+++ CLEAR KEYRING

  (http://autopkgtest.ubuntu.com/packages/k/keyutils/disco/armhf)

Since the Debian autopkgtest runners also use containers instead of VMs, and
this test passes there, it is plausible that this is a bug in the package on
armhf rather than a wrong restriction on this subtest.

-- 
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 Developer   https://www.debian.org/
slanga...@ubuntu.com vor...@debian.org


signature.asc
Description: PGP signature

Bug#921757: Can't reproduce

[Hilko Bengen]

user debian-rele...@lists.debian.org
usertag 921757 + bsp-2019-02-de-bonn
tag 921757 + unreproducible
thank you

Greetings from the BSP taking place at Teckids e.V./tarent
solutions GmbH in Bonn this weekend.

I have tried to reproduce the bug using an up-to-date sid-amd64 chroot
but couldn't.

My guess from the test script log is that qemu-img (from package
qemu-utils) was missing in the build attempt.

Cheers,
-Hilko

Bug#923158: RFS: libpam-rfid/1.4 [ITP] -- friendly greeter

[Philipp Meisberger]

Package: sponsorship-requests
Severity: wishlist

Dear mentors,

I am looking for a sponsor for my package "libpam-rfid"

 * Package name: libpam-rfid
   Version : 1.4
   Upstream Author : Philipp Meisberger 
 * URL : https://github.com/philippmeisberger/pam-rfid.git
 * License : D-FSL
   Section : admin

It builds those binary packages:

libpam-rfid - Pluggable Authentication Module for hardware
authentication via RFID

To access further information about this package, please visit the
following URL:

  https://mentors.debian.net/package/libpam-rfid


Alternatively, one can download the package with dget using this command:

dget -x
https://mentors.debian.net/debian/pool/main/libp/libpam-rfid/libpam-rfid_1.4.dsc

More information about libpam-rfid can be obtained from
https://github.com/philippmeisberger/pam-rfid.

Changes since the last upload:

  * Added --check-user option to pamrfid-conf
  * Removed pamrfid-check
  * Ensure system user exists before adding

Regards,
Philipp Meisberger



signature.asc
Description: OpenPGP digital signature

Bug#923157: RFS: libpam-fingerprint/1.5 [ITP]

[Philipp Meisberger]

Package: sponsorship-requests
Severity: wishlist

Dear mentors,

I am looking for a sponsor for my package "libpam-fingerprint"

 * Package name: libpam-fingerprint
   Version : 1.5
   Upstream Author : Philipp Meisberger 
 * URL :
https://github.com/philippmeisberger/pam-fingerprint.git
 * License : D-FSL
   Section : admin

It builds those binary packages:

libpam-fingerprint - Pluggable Authentication Module for fingerprint
authentication

To access further information about this package, please visit the
following URL:

https://mentors.debian.net/package/libpam-fingerprint


Alternatively, one can download the package with dget using this command:

dget -x
https://mentors.debian.net/debian/pool/main/libp/libpam-fingerprint/libpam-fingerprint_1.5.dsc

More information about libpam-fingerprint can be obtained from
https://github.com/philippmeisberger/pam-fingerprint.

Changes since the last upload:

  * Added --check-user option to pamfingerprint-conf
  * Removed pamfingerprint-check
  * Ensure system user exists before adding

Regards,
Philipp Meisberger



signature.asc
Description: OpenPGP digital signature

Bug#923067: libc0.1: missing UTIME_OMIT for utimensat(2) and futimens(2)

[Thorsten Glaser]

On Sat, 23 Feb 2019, Thorsten Glaser wrote:

> then give-back src:pax on both kfreebsd architectures.

In the meantime, I had to do a pax upload to fix bugs anyway,
so I just added a configure-time check for UTIME_OMIT, so it
built now, although not using utimensat/futimes. In case you
wonder…

bye,
//mirabilos
-- 
[17:15:07] Lukas Degener: Kleines Asterix-Latinum für Softwaretechniker:
   veni, vidi, fixi(t) ;-)

Bug#923159: network-manager: This package is abondoned! Please remove network-manager from Debian!

[Svjatoslav Agejenko]

Package: network-manager
Version: 1.14.4-4
Severity: important

Dear Maintainer,

Existing bug list is scary. Hundreds of open bug reports
for this package in status "pending" for many years!
This package is clearly unmaintained.

This package is also default network manager at least
when you install popular Gnome desktop environment.

I myself got screwed today by Network Manager.
Problem and workaround is reported years ago here:



https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=839605
The workaround provided works for me:

/etc/NetworkManager/NetworkManager.conf
[device-mac-randomization]
wifi.scan-rand-mac-address=no
-


Now years and major Debian releases later the same
issue is still unfixed and actively causes troubles
to people. I'm lucky I had cable internet and found
that workaround.


This open buglist is not ok!

Keeping that half baked MAC randomization feature in
Network Manager on by default is not ok!

Keeping this unmaintained Network Manager as part
of Debian and even as default is not ok!


When people lose interest or cannot afford time to maintain
package, it SHOULD be removed until it meets necessary
quality treshold again.



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

Kernel: Linux 4.19.0-2-amd64 (SMP w/2 CPU cores)
Kernel taint flags: TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_US:en (charmap=UTF-8)
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages network-manager depends on:
ii  adduser3.118
it  dbus   1.12.12-1
ii  init-system-helpers1.56+nmu1
ii  libaudit1  1:2.8.4-2
ii  libbluetooth3  5.50-1
ii  libc6  2.28-7
ii  libcurl3-gnutls7.64.0-1
ii  libglib2.0-0   2.58.3-1
ii  libgnutls303.6.6-2
ii  libjansson42.12-1
ii  libmm-glib01.10.0-1
ii  libndp01.6-1+b1
ii  libnewt0.520.52.20-8
ii  libnm0 1.14.4-4
ii  libpam-systemd 240-6
ii  libpolkit-agent-1-00.105-25
ii  libpolkit-gobject-1-0  0.105-25
ii  libpsl50.20.2-2
ii  libreadline7   7.0-5
ii  libselinux12.8-1+b1
ii  libsystemd0240-6
ii  libteamdctl0   1.28-1
ii  libudev1   240-6
ii  libuuid1   2.33.1-0.1
ii  lsb-base   10.2018112800
ii  policykit-10.105-25
ii  udev   240-6
ii  wpasupplicant  2:2.6-21

Versions of packages network-manager recommends:
ii  crda 3.18-1
ii  dnsmasq-base [dnsmasq-base]  2.80-1
ii  iptables 1.8.2-3
ii  isc-dhcp-client  4.4.1-2
ii  modemmanager 1.10.0-1
ii  ppp  2.4.7-2+4

Versions of packages network-manager suggests:
pn  libteam-utils  

-- Configuration Files:
/etc/NetworkManager/NetworkManager.conf changed:
[main]
plugins=ifupdown,keyfile
[ifupdown]
managed=false
[device-mac-randomization]
wifi.scan-rand-mac-address=no


-- no debconf information