Bug#916421: RM: python-app-catalog-ui -- ROM; Deprecated upstream

[Thomas Goirand]

Package: ftp.debian.org
Severity: normal

Dear FTP masters,

python-app-catalog-ui is now deprecated upstream, and nobody is taking care
of it anymore. Please remove python-app-catalog-ui from the archive, so that
we make sure it's not part of Buster.

Cheers,

Thomas Goirand (zigo)

Bug#916410: closed by Michael Gilbert (Re: Bug#916410: chromium: Chromium 71.0.3578.80-1 fails to build from source due to missing subdirectories in third_party)

[nurupo]

Thanks for the reply, I have identified the issue.
I was trying to build it on a NTFS fs and it setup to set 0777 on all files.

On Thu, Dec 13, 2018 at 11:21 PM Debian Bug Tracking System <
ow...@bugs.debian.org> wrote:

> This is an automatic notification regarding your Bug report
> which was filed against the chromium package:
>
> #916410: chromium: Chromium 71.0.3578.80-1 fails to build from source due
> to missing subdirectories in third_party
>
> It has been closed by Michael Gilbert .
>
> Their explanation is attached below along with your original report.
> If this explanation is unsatisfactory and you have not received a
> better one in a separate message then please contact Michael Gilbert <
> mgilb...@debian.org> by
> replying to this email.
>
>
> --
> 916410: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=916410
> Debian Bug Tracking System
> Contact ow...@bugs.debian.org with problems
>
>
>
> -- Forwarded message --
> From: Michael Gilbert 
> To: 916410-cl...@bugs.debian.org
> Cc:
> Bcc:
> Date: Thu, 13 Dec 2018 23:21:28 -0500
> Subject: Re: Bug#916410: chromium: Chromium 71.0.3578.80-1 fails to build
> from source due to missing subdirectories in third_party
> On Thu, Dec 13, 2018 at 9:45 PM Maxim Biro wrote:
> > dh_clean: debian/clean is marked executable but does not appear to an
> > executable config.
> > dh_clean:
> > dh_clean: If debian/clean is intended to be an executable config file,
> please
> > ensure it can
> > dh_clean: be run as a stand-alone script/program (e.g. "./debian/clean")
> > dh_clean: Otherwise, please remove the executable bit from the file
> (e.g. chmod
> > -x "debian/clean")
> > dh_clean:
> > dh_clean: Please see "Executable debhelper config files" in debhelper(7)
> for
> > more information.
>
> The build log states exactly what is wrong and what needs to be done
> to fix it.  debian/clean needs to not be executable, otherwise
> debhelper will handle it differently.  It is not shipped that way.
>
> Best wishes,
> Mike
>
>
> -- Forwarded message --
> From: Maxim Biro 
> To: Debian Bug Tracking System 
> Cc:
> Bcc:
> Date: Thu, 13 Dec 2018 21:40:04 -0500
> Subject: chromium: Chromium 71.0.3578.80-1 fails to build from source due
> to missing subdirectories in third_party
> Package: chromium
> Version: 71.0.3578.80-1
> Severity: serious
> Justification: fails to build from source (but built successfully in the
> past)
>
> Trying to build Chromium off the source package, but it fails with
> Chromium's
> builds system unable to find third_party/{libvpx,opus,freetype} and so on.
>
> Here is what I do:
>
> sudo docker run --rm -it -v /tmp/chromium-pkgs:/build debian:sid /bin/bash
> echo "
> deb http://deb.debian.org/debian sid main contrib
> deb-src http://deb.debian.org/debian/ sid main contrib
> " > /etc/apt/sources.list
> apt-get update
> apt-get dist-upgrade -y
> apt-get install -y fakeroot devscripts build-essential
> apt-get build-dep -y chromium
> cd /build
> apt-get source -y chromium
> cd chromium-*
> debuild
>
> The error:
>
> # debuild
> dpkg-buildpackage -us -uc -ui
> dpkg-buildpackage: info: source package chromium
> dpkg-buildpackage: info: source version 71.0.3578.80-1
> dpkg-buildpackage: info: source distribution unstable
> dpkg-buildpackage: info: source changed by Michael Gilbert
> 
> dpkg-source --before-build .
> dpkg-buildpackage: info: host architecture amd64
> debian/rules clean
> dh clean
>   debian/rules override_dh_auto_clean
> make[1]: Entering directory '/build/chromium-71.0.3578.80'
> rm -rf out
> find . -name \*.pyc -execdir rm -f {} \;
> dh_auto_clean
> make[1]: Leaving directory '/build/chromium-71.0.3578.80'
>   dh_clean
> rm -f debian/debhelper-build-stamp
> rm -rf debian/.debhelper/
> /build/chromium-71.0.3578.80/debian/clean: 1:
> /build/chromium-71.0.3578.80/debian/clean: debian/files: not found
> /build/chromium-71.0.3578.80/debian/clean: 2:
> /build/chromium-71.0.3578.80/debian/clean: debian/scripts/mk-origtargz: not
> found
> /build/chromium-71.0.3578.80/debian/clean: 4:
> /build/chromium-71.0.3578.80/debian/clean: Makefile: not found
> /build/chromium-71.0.3578.80/debian/clean: 5:
> /build/chromium-71.0.3578.80/debian/clean: third_party/flot/*.js: not found
> /build/chromium-71.0.3578.80/debian/clean: 7:
> /build/chromium-71.0.3578.80/debian/clean:
> base/third_party/libevent/BUILD.gn:
> not found
> /build/chromium-71.0.3578.80/debian/clean: 8:
> /build/chromium-71.0.3578.80/debian/clean:
> build/secondary/third_party/libjpeg_turbo/BUILD.gn: not found
> /build/chromium-71.0.3578.80/debian/clean: 10:
> /build/chromium-71.0.3578.80/debian/clean: third_party/re2/BUILD.gn: not
> found
> /build/chromium-71.0.3578.80/debian/clean: 11:
> /build/chromium-71.0.3578.80/debian/clean: third_party/icu/BUILD.gn: not
> found
> /build/chromium-71.0.3578.80/debian/clean: 12:
> /build/chromium-71.0.3578.80/debian/clean: third_party/flac/BUILD.gn: not
> found
> third_party/zlib/BUILD.gn: 5: 

Bug#821111:

[Vikash Singh]

Bug#916306: gitlab: Error during gitlab installation

[Pirate Praveen]

On 2018, ഡിസംബർ 14 1:22:52 AM IST, Pranith Kumar  wrote:
>OK. I manually copied gitlab-debian.conf from /var/lib/gitlab/ to
>/etc/gitlab/ and it was overwritten during the configure step with the
>package maintainers version. It now proceeds past the previous error
>message.
>
>Now, I am seeing a new error as follows:
>
>$ sudo dpkg --configure gitlab
>Setting up gitlab (11.3.11+dfsg-1) ...
>Creating runtime directories for gitlab...
>Updating file permissions...
>Configuring hostname and email...
>Registering /usr/lib/tmpfiles.d/gitlab.conf via ucf
>/etc/systemd/system/gitlab-mailroom.service.d/override.conf already
>exist
>/etc/systemd/system/gitlab-unicorn.service.d/override.conf already
>exist
>/etc/systemd/system/gitlab-sidekiq.service.d/override.conf already
>exist
>/etc/systemd/system/gitlab-workhorse.service.d/override.conf already
>exist
>Registering /etc/gitlab-shell/config.yml via ucf
>Registering /etc/gitlab/gitlab.yml via ucf
>Registering /etc/gitlab/gitlab-debian.conf via ucf
>Reloading nginx configuration...
>nginx.service is not active, cannot reload.
>invoke-rc.d: initscript nginx, action "reload" failed.
>dpkg: error processing package gitlab (--configure):
> installed gitlab package post-installation script subprocess returned
>error exit status 1
>Errors were encountered while processing:
> gitlab
>
>Thanks,
>

That is a known bug which is not yet fixed. If you start nginx manually, the 
installation should proceed. We stop nginx for letsencrypt, but does not start 
it again.
-- 
Sent from my Android device with K-9 Mail. Please excuse my brevity.

Bug#916420: RFS: tlf/1.3.2-1

[Ervin Hegedüs]

Package: sponsorship-requests
Severity: normal

Dear mentors,

I am looking for a sponsor for my package "tlf"

 * Package name: tlf
   Version : 1.3.2-1
   Upstream Author : Thomas Beierlein 
 * URL : https://savannah.nongnu.org/projects/tlf
 * License : GPL
   Section : hamradio

It builds those binary packages:

  tlf   - console based ham radio contest logger

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

https://mentors.debian.net/package/tlf


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

  dget -x https://mentors.debian.net/debian/pool/main/t/tlf/tlf_1.3.2-1.dsc

More information about tlf can be obtained from
https://savannah.nongnu.org/projects/tlf, https://tlf.github.io/
or https://github.com/Tlf/tlf.

Changes since the last upload:

  * Team upload.
  * New upstream release
  * Removed spelling-fixes.patch, all modifications had been
merged to upstream

Regards,
 Ervin Hegedüs

Bug#913768: transition: glibc

[Aurelien Jarno]

On 2018-12-14 06:56, Petter Reinholdtsen wrote:
> [Aurelien Jarno 2018-11-29]
> > Thanks, I have just uploaded it.
> 
> According to https://tracker.debian.org/pkg/glibc >, the new glibc
> seem to require approval from the d-i release manager.  Are anyone in
> touch with him to clear glibc?

Please see: https://lists.debian.org/debian-boot/2018/12/msg00096.html

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

Bug#916415: nocache broken with glibc 2.28: several programs just hang in call to futex(..., FUTEX_WAIT_PRIVATE, 2, NULL)

[Aurelien Jarno]

control: forwarded -1 https://github.com/Feh/nocache/issues/34

On 2018-12-14 13:33, Paul Wise wrote:
> Package: nocache/1.0-1,libc6/2.28-2
> Severity: critical
> Justification: breaks unrelated software
> Usertags: hang
> 
> The upgrade from libc6 2.27-8 to 2.28-2 breaks nocache; some programs,
> when run under it (but not all of them), hang in a call to read/futex:

I haven't looked at it in details, but at least accorded to the upstream
bug, it seems to be an issue on the nocache side:

https://github.com/Feh/nocache/issues/34

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


signature.asc
Description: PGP signature

Bug#916419: gkdebconf FTCBFS: uses the wrong pkg-config

[Helmut Grohne]

Source: gkdebconf
Version: 2.0.4
Tags: patch
User: helm...@debian.org
Usertags: rebootstrap

gkdebconf fails to cross build from source, because configure.ac hard
codes the build architecture pkg-config. The attached patch replaces the
invocations with the PKG_CHECK_MODULES macro and makes gkdebconf cross
buildable. Please consider applying the patch.

Helmut
diff --minimal -Nru gkdebconf-2.0.4/configure.ac 
gkdebconf-2.0.4+nmu1/configure.ac
--- gkdebconf-2.0.4/configure.ac2018-10-22 21:11:13.0 +0200
+++ gkdebconf-2.0.4+nmu1/configure.ac   2018-12-14 06:58:18.0 +0100
@@ -15,10 +15,9 @@
 AC_HEADER_DIRENT
 AC_HEADER_STDC
 
-GKDEBCONF_CFLAGS=`pkg-config --cflags gtk+-2.0`
+PKG_CHECK_MODULES([GKDEBCONF],[gtk+-2.0])
 AC_SUBST([GKDEBCONF_CFLAGS])
-GKDEBCONF_LDFLAGS=`pkg-config --libs gtk+-2.0`
-AC_SUBST([GKDEBCONF_LDFLAGS])
+AC_SUBST([GKDEBCONF_LIBS])
 
 GLIB_GSETTINGS
 
@@ -36,15 +35,7 @@


 AC_SUBST(HTML_DIR)


-gtk_doc_min_version=1.0
-AC_MSG_CHECKING([gtk-doc version >= $gtk_doc_min_version])
-if pkg-config --atleast-version=$gtk_doc_min_version gtk-doc; then
-  AC_MSG_RESULT(yes)
-  GTKDOC=true
-else
-  AC_MSG_RESULT(no)
-  GTKDOC=false
-fi
+PKG_CHECK_MODULES([GTKDOC],[gtk-doc >= 1.0],[GTKDOC=true],[GTKDOC=false])


 dnl Let people disable the gtk-doc stuff.
 AC_ARG_ENABLE(gtk-doc, [  --enable-gtk-doc  Use gtk-doc to build documentation 
[default=no]], enable_gtk_doc="$enableval", 
diff --minimal -Nru gkdebconf-2.0.4/debian/changelog 
gkdebconf-2.0.4+nmu1/debian/changelog
--- gkdebconf-2.0.4/debian/changelog2018-10-22 22:32:32.0 +0200
+++ gkdebconf-2.0.4+nmu1/debian/changelog   2018-12-14 06:58:18.0 
+0100
@@ -1,3 +1,10 @@
+gkdebconf (2.0.4+nmu1) UNRELEASED; urgency=medium
+
+  * Non-maintainer upload.
+  * Fix FTCBFS: Don't hard code pkg-config. (Closes: #-1)
+
+ -- Helmut Grohne   Fri, 14 Dec 2018 06:58:18 +0100
+
 gkdebconf (2.0.4) unstable; urgency=medium
 
   * QA upload.
diff --minimal -Nru gkdebconf-2.0.4/src/Makefile.am 
gkdebconf-2.0.4+nmu1/src/Makefile.am
--- gkdebconf-2.0.4/src/Makefile.am 2017-12-31 01:18:58.0 +0100
+++ gkdebconf-2.0.4+nmu1/src/Makefile.am2018-12-14 06:58:18.0 
+0100
@@ -3,5 +3,5 @@
 
 bin_PROGRAMS = gkdebconf
 
-gkdebconf_LDADD = $(GKDEBCONF_LDFLAGS)
+gkdebconf_LDADD = $(GKDEBCONF_LIBS)
 gkdebconf_SOURCES = main.c files.c interface.c debconf.c cbs.c config.c

Bug#913768: transition: glibc

[Paul Wise]

On Thu, Nov 29, 2018 at 2:21 PM Aurelien Jarno wrote:

> Thanks, I have just uploaded it.

I've just noticed that the glibc update has caused a regression in the
nocache package (details in #916415).

-- 
bye,
pabs

https://wiki.debian.org/PaulWise

Bug#752563: [bash] Enable syslogging to a separate option or a package

[Dean Hamstead]

+1 to this request, and related

redhat has sent a patch that makes bash logging configuration via shopt, see

https://lists.gnu.org/archive/html/bug-bash/2017-01/msg00053.html


also, this person maintains a script which builds bash with syslog 
enabled, but also tweaks the log message to send the login user rather 
than uid, which stays the same when a user sudo's


https://github.com/Mickaelh51/bash-autoinstaller-active-syslog




On Tue, 24 Jun 2014 14:10:36 -0400 Tim Sattarov  
wrote:


> Package: bash
> Version: 4.3-7.1
> Severity: wishlist
> Tags: security
> X-Debbugs-CC: secure-testing-t...@lists.alioth.debian.org
>
> --- Please enter the report below this line. ---
> Hello,
>
> I wonder if you can enable syslog feature in bash
> i.e. uncomment line in config-top.h
> #define SYSLOG_HISTORY
>
> and make it configurable through a separate config option in ini file or
> compile it to a seperate package.
>
> Thanks
> Tim
>
> --- System information. ---
> Architecture: amd64
> Kernel: Linux 3.14-1-amd64
>
> Debian Release: jessie/sid
> 800 unstable http.us.debian.org
> 800 unstable deb-multimedia.org
> 500 stable dl.google.com
> 1 experimental http.us.debian.org
>
> --- Package information. ---
> Depends (Version) | Installed
> ===-+-
> base-files (>= 2.1.12) | 7.3
> debianutils (>= 2.15) | 4.4
>
>
> Recommends (Version) | Installed
> ===-+-
> bash-completion (>= 20060301-0) | 1:2.1-4
>
>
> Suggests (Version) | Installed
> ===-+-===
> bash-doc |

Bug#913768: transition: glibc

[Petter Reinholdtsen]

[Aurelien Jarno 2018-11-29]
> Thanks, I have just uploaded it.

According to https://tracker.debian.org/pkg/glibc >, the new glibc
seem to require approval from the d-i release manager.  Are anyone in
touch with him to clear glibc?

-- 
Happy hacking
Petter Reinholdtsen

Bug#916418: rstatd FTCBFS: builds for the wrong architecture

[Helmut Grohne]

Source: rstatd
Version: 4.0.1-9
Tags: patch
User: helm...@debian.org
Usertags: rebootstrap

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

Helmut
diff --minimal -Nru rstatd-4.0.1/debian/changelog rstatd-4.0.1/debian/changelog
--- rstatd-4.0.1/debian/changelog   2016-11-21 13:25:23.0 +0100
+++ rstatd-4.0.1/debian/changelog   2018-12-14 06:47:12.0 +0100
@@ -1,3 +1,10 @@
+rstatd (4.0.1-9.1) UNRELEASED; urgency=medium
+
+  * Non-maintainer upload.
+  * Fix FTCBFS: Let dh_auto_configure pass --host to ./configure. (Closes: #-1)
+
+ -- Helmut Grohne   Fri, 14 Dec 2018 06:47:12 +0100
+
 rstatd (4.0.1-9) unstable; urgency=medium
 
   * Fix uses-deprecated-compression-for-data-tarball
diff --minimal -Nru rstatd-4.0.1/debian/rules rstatd-4.0.1/debian/rules
--- rstatd-4.0.1/debian/rules   2016-11-21 13:24:54.0 +0100
+++ rstatd-4.0.1/debian/rules   2018-12-14 06:47:10.0 +0100
@@ -11,7 +11,7 @@
 configure: configure-stamp
 configure-stamp:
dh_testdir
-   ./configure --prefix=/usr
+   dh_auto_configure
touch configure-stamp
 
 build: build-arch build-indep

Bug#916417: e2tools FTCBFS: builds for the wrong architecture

[Helmut Grohne]

Source: e2tools
Version: 0.0.16-6.1
Tags: patch
User: helm...@debian.org
Usertags: rebootstrap

e2tools fails to cross build from source, because it uses the build
architecture compiler. That's despite dh_auto_configure passing the
relevant --host flag to ./configure. Unfortunately, the configure at
hand is too old and does not recognize --host. So one should pass a CC
as an environment variable instead. Please consider applying the
attached patch.

Helmut
diff -u e2tools-0.0.16/debian/changelog e2tools-0.0.16/debian/changelog
--- e2tools-0.0.16/debian/changelog
+++ e2tools-0.0.16/debian/changelog
@@ -1,3 +1,11 @@
+e2tools (0.0.16-6.2) UNRELEASED; urgency=medium
+
+  * Non-maintainer upload.
+  * Fix FTCBFS: Export CC supplied by buildtools.mk for configure.
+(Closes: #-1)
+
+ -- Helmut Grohne   Fri, 14 Dec 2018 06:41:28 +0100
+
 e2tools (0.0.16-6.1) unstable; urgency=low
 
   * Non-maintainer upload.
diff -u e2tools-0.0.16/debian/rules e2tools-0.0.16/debian/rules
--- e2tools-0.0.16/debian/rules
+++ e2tools-0.0.16/debian/rules
@@ -1,4 +1,7 @@
 #!/usr/bin/make -f
 
+-include /usr/share/dpkg/buildtools.mk
+export CC
+
 %:
dh $@

Bug#916055: (no subject)

[Andre Heider]

I ran into the same issue and came with another approach. The patch was 
just merged upstream[0], so post v0.17.0.


That also introduces a new metric if a disk is in standby mode.

Could you please update to 0.17.0 and cherry-pick that instead?

Thanks!
Andre

[0] 
https://github.com/prometheus/node_exporter/commit/7c960fd68365e9bbdb14cf140fc1d26d4c27333a.patch

Bug#916375: Fwd: Bug#916375: apache2: Segmentation fault when mod_perl.so is loaded

[Xavier]

Cc: libapache2-mod-perl2


 Message 
Subject : Bug#916375: apache2: Segmentation fault when mod_perl.so is loaded
Date : Thu, 13 Dec 2018 19:09:02 +
>From : h.thien 
To : debian-bugs-dist@lists.debian.org
Cc : t...@security.debian.org, Debian Apache Maintainers


Package: apache2
Version: 2.4.25-3+deb9u6
Severity: grave
Tags: patch
Justification: renders package unusable

Dear Maintainer,

For communication with our customers we use the OTRS Ticket System.

The server was reinstalled about a year ago and worked fine until it
was rebooted three days ago.

Since then the Apache web server crashes reproducibly as soon as it has
to process a request. Here is a stacktrace:

cd /etc/apache2
. envvars
gdb /usr/sbin/apache2
gdb> set args -X
gdb> run

# ... now use the webbrowser to send an http request to the 
apache2
server: http://otrs-testing/otrs/index.pl?Action=Admin

gdb> Thread 1 "/opt/otrs/bin/cgi-bi" received signal SIGSEGV,
Segmentation fault.
gdb> bt
#0  0x7fffdcd290c7 in free_defaults () from
/usr/lib/x86_64-linux-gnu/libmariadbclient.so.18
#1  0x7fffdcd29422 in free_defaults () from
/usr/lib/x86_64-linux-gnu/libmariadbclient.so.18
#2  0x7fffdcd29461 in free_defaults () from
/usr/lib/x86_64-linux-gnu/libmariadbclient.so.18
#3  0x7fffdcd29637 in free_defaults () from
/usr/lib/x86_64-linux-gnu/libmariadbclient.so.18
#4  0x7fffdccf5868 in mysql_options4 () from
/usr/lib/x86_64-linux-gnu/libmariadbclient.so.18
#5  0x7fffdd2cabc8 in mysql_dr_connect () from
/usr/lib/x86_64-linux-gnu/perl5/5.24/auto/DBD/mysql/mysql.so
#6  0x7fffdd2ccc69 in ?? () from
/usr/lib/x86_64-linux-gnu/perl5/5.24/auto/DBD/mysql/mysql.so
#7  0x7fffdd2ccd71 in mysql_db_login () from
/usr/lib/x86_64-linux-gnu/perl5/5.24/auto/DBD/mysql/mysql.so
#8  0x7fffdd2d9651 in ?? () from
/usr/lib/x86_64-linux-gnu/perl5/5.24/auto/DBD/mysql/mysql.so
#9  0x73901950 in Perl_pp_entersub () from
/usr/lib/x86_64-linux-gnu/libperl.so.5.24
#10 0x738f9e96 in Perl_runops_standard () from
/usr/lib/x86_64-linux-gnu/libperl.so.5.24
#11 0x73879d5b in Perl_call_sv () from
/usr/lib/x86_64-linux-gnu/libperl.so.5.24
#12 0x7fffea84c2e9 in XS_DBI_dispatch () from
/usr/lib/x86_64-linux-gnu/perl5/5.24/auto/DBI/DBI.so
#13 0x73901950 in Perl_pp_entersub () from
/usr/lib/x86_64-linux-gnu/libperl.so.5.24
#14 0x738f9e96 in Perl_runops_standard () from
/usr/lib/x86_64-linux-gnu/libperl.so.5.24
#15 0x7387a10e in Perl_call_sv () from
/usr/lib/x86_64-linux-gnu/libperl.so.5.24
#16 0x73c32c68 in modperl_callback () from
/usr/lib/apache2/modules/mod_perl.so
#17 0x73c33606 in modperl_callback_run_handlers () 
from
/usr/lib/apache2/modules/mod_perl.so
#18 0x73c33d9f in modperl_callback_per_dir () from
/usr/lib/apache2/modules/mod_perl.so
#19 0x73c2e0fb in ?? () from
/usr/lib/apache2/modules/mod_perl.so
#20 0x73c2e32c in modperl_response_handler_cgi () 
from
/usr/lib/apache2/modules/mod_perl.so
#21 0x555abc40 in ap_run_handler ()
#22 0x555ac1d6 in ap_invoke_handler ()
#23 0x555c3e13 in ap_process_async_request ()
#24 0x555c3f20 in ap_process_request ()
#25 0x555bffdd in ?? ()
#26 0x555b5ab0 in ap_run_process_connection ()
#27 0x740686bf in ?? () from
/usr/lib/apache2/modules/mod_mpm_prefork.so
#28 0x740688f2 in ?? () from
/usr/lib/apache2/modules/mod_mpm_prefork.so
#29 0x74069e37 in ?? () from
/usr/lib/apache2/modules/mod_mpm_prefork.so
#30 0x5558f00e in ap_run_mpm ()
#31 0x55587c4d in main ()

We are using unattended upgrades (security only), and we suspect that
an automatic system update has installed a new Perl version that now
causes these problems.

We have a second OTRS fallback system that hasn't been restarted for 94
days, and everything is still working fine there.

If we compare the shared libraries loaded by apache on these two
systems (/proc//maps) we can see that the following .so
files have been renewed.

  484 -rw-r--r-- 1 root root   489960 Nov 29 20:45
/usr/lib/x86_64-linux-gnu/libtiff.so.5.2.6
 2008 

Bug#916416: kazam unable to start: ValueError: Invalid section name: 'DEFAULT'

[Jajo]

Package: kazam
Version: 1.4.5-2
Severity: grave
Justification: renders package unusable

Dear Maintainer,

I'm unable to start Kazam. Here the error when I start it:

/usr/bin/kazam:32: PyGIWarning: Gtk was imported without specifying a version
first. Use gi.require_version('Gtk', '3.0') before import to ensure that the
right version gets loaded.
  from gi.repository import Gtk
/usr/bin/kazam:75: DeprecationWarning: dist() and linux_distribution()
functions are deprecated in Python 3.5
  dist = platform.linux_distribution()
Traceback (most recent call last):
  File "/usr/bin/kazam", line 146, in 
from kazam.app import KazamApp
  File "/usr/lib/python3/dist-packages/kazam/app.py", line 35, in 
from kazam.backend.prefs import *
  File "/usr/lib/python3/dist-packages/kazam/backend/prefs.py", line 478, in

prefs = Prefs()
  File "/usr/lib/python3/dist-packages/kazam/backend/prefs.py", line 119, in
__init__
self.config = KazamConfig()
  File "/usr/lib/python3/dist-packages/kazam/backend/config.py", line 76, in
__init__
ConfigParser.__init__(self, self.DEFAULTS[0]['keys'])
  File "/usr/lib/python3.7/configparser.py", line 638, in __init__
self._read_defaults(defaults)
  File "/usr/lib/python3.7/configparser.py", line 1216, in _read_defaults
self.read_dict({self.default_section: defaults})
  File "/usr/lib/python3.7/configparser.py", line 753, in read_dict
self.set(section, key, value)
  File "/usr/lib/python3/dist-packages/kazam/backend/config.py", line 127, in
set
self.add_section(section)
  File "/usr/lib/python3.7/configparser.py", line 1205, in add_section
super().add_section(section)
  File "/usr/lib/python3.7/configparser.py", line 655, in add_section
raise ValueError('Invalid section name: %r' % section)
ValueError: Invalid section name: 'DEFAULT'



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

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

Versions of packages kazam depends on:
ii  gir1.2-gst-plugins-base-1.0  1.14.4-dmo1
ii  gir1.2-gstreamer-1.0 1.14.4-1
ii  gir1.2-keybinder-3.0 0.3.2-1
ii  gir1.2-wnck-3.0  3.30.0-1
ii  gnome-session-canberra   0.30-6
ii  gstreamer1.0-plugins-base1.14.4-dmo1
ii  gstreamer1.0-plugins-good1.14.4-dmo1
ii  gstreamer1.0-plugins-ugly1:1.14.4-dmo1
ii  gstreamer1.0-pulseaudio  1.14.4-dmo1
ii  python3  3.7.1-2
ii  python3-cairo1.16.2-1+b1
ii  python3-dbus 1.2.8-2+b2
ii  python3-gi   3.30.2-1
ii  python3-gi-cairo 3.30.2-1
ii  python3-xdg  0.25-4

Versions of packages kazam recommends:
ii  gstreamer1.0-libav  1:1.14.4-dmo1

kazam suggests no packages.

-- no debconf information

Bug#916415: nocache broken with glibc 2.28: several programs just hang in call to futex(..., FUTEX_WAIT_PRIVATE, 2, NULL)

[Paul Wise]

Package: nocache/1.0-1,libc6/2.28-2
Severity: critical
Justification: breaks unrelated software
Usertags: hang

The upgrade from libc6 2.27-8 to 2.28-2 breaks nocache; some programs,
when run under it (but not all of them), hang in a call to read/futex:

# nocache sleep 1

# apt show nowcache &> /dev/null

# nocache apt show nowcache &
[1] 3971

# strace -p 3971
strace: Process 3971 attached
read(5, 
^Cstrace: Process 3971 detached
 

# ls -l /proc/3971/fd/5
lr-x-- 1 root root 64 Dec 14 05:28 /proc/3971/fd/5 -> 'pipe:[144396456]'

# cat /proc/3971/fdinfo/5
pos:0
flags:  00
mnt_id: 12

# pgrep --list-full --parent 3971
3972 apt show nowcache

# strace -p 3972
strace: Process 3972 attached
futex(0x7f451a949940, FUTEX_WAIT_PRIVATE, 2, NULL
^Cstrace: Process 3972 detached
 

# ls -l /proc/3972/fd/2
lrwx-- 1 root root 64 Dec 14 05:29 /proc/3972/fd/2 -> /dev/pts/2

# cat /proc/3972/fdinfo/2
pos:0
flags:  0102002
mnt_id: 22

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

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

Versions of packages nocache depends on:
ii  libc6  2.28-2

nocache recommends no packages.

nocache suggests no packages.

-- no debconf information

-- 
bye,
pabs

https://wiki.debian.org/PaulWise



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

Bug#916414: nocache: add usage statement with incorrect arguments

[Paul Wise]

Package: nocache
Version: 1.0-1
Severity: wishlist

nocache does not properly handle the situation where an invalid flag
was passed to the script. It complains about the options and continues.
The correct thing to do would be to print a usage statement and exit.
It would also be nice to add a help option to print the usage info.

$ nocache --help echo foo
/usr/bin/nocache: illegal option -- -
/usr/bin/nocache: illegal option -- h
/usr/bin/nocache: illegal option -- e
/usr/bin/nocache: illegal option -- l
/usr/bin/nocache: illegal option -- p
foo

$ shellcheck -eSC2145 `which nocache` 

In /usr/bin/nocache line 6:
case "$opt" in
^-- SC2220: Invalid flags are not handled. Add a *) case.

$ cp `which nocache` .

$ sed -i 's/esac/*) echo usage statement here ; exit ;; esac/' nocache 

$ ./nocache --help echo foo
./nocache: illegal option -- -
usage statement here

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

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

Versions of packages nocache depends on:
ii  libc6  2.28-2

nocache recommends no packages.

nocache suggests no packages.

-- no debconf information

-- 
bye,
pabs

https://wiki.debian.org/PaulWise



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

Bug#757470: network-manager: after resume from suspend, fails to start dhclient on wired interface

[Stephen Hemminger]

Package: network-manager
Version: 1.14.4-4
Followup-For: Bug #757470

When system auto suspends via Gnome power manager and then is resumed the 
network interface
comes back up but has no address. Looks like Network Manager fails to renew the 
addres.

Partial log:
Dec  9 20:26:22 xeon-e3 kernel: [20711.261552] ACPI: Waking up from system 
sleep state S3

Dec  9 20:26:22 xeon-e3 kernel: [20712.684611] ixgbe :04:00.0: Multiqueue 
Enabled: Rx Queue count = 12, Tx Queue count = 12 XDP Queue count = 0
Dec  9 20:26:22 xeon-e3 kernel: [20712.959613] usb 2-9: reset high-speed USB 
device number 2 using xhci_hcd
Dec  9 20:26:22 xeon-e3 kernel: [20713.235765] usb 3-5: reset SuperSpeed Gen 1 
USB device number 2 using xhci_hcd
Dec  9 20:26:22 xeon-e3 kernel: [20713.299603] [drm] ib test on ring 5 succeeded
Dec  9 20:26:22 xeon-e3 kernel: [20713.335609] usb 2-10.4: reset high-speed USB 
device number 5 using xhci_hcd
Dec  9 20:26:22 xeon-e3 kernel: [20713.515620] usb 2-10.2: reset full-speed USB 
device number 8 using xhci_hcd
Dec  9 20:26:22 xeon-e3 kernel: [20713.731622] usb 2-10.4.4: reset full-speed 
USB device number 6 using xhci_hcd
Dec  9 20:26:22 xeon-e3 kernel: [20714.147621] usb 2-10.4.4.1: reset full-speed 
USB device number 7 using xhci_hcd
Dec  9 20:26:22 xeon-e3 kernel: [20714.207573] ata2: SATA link up 3.0 Gbps 
(SStatus 123 SControl 300)
Dec  9 20:26:22 xeon-e3 kernel: [20714.328261] ata2.00: configured for UDMA/133
Dec  9 20:26:22 xeon-e3 kernel: [20714.344237] OOM killer enabled.
Dec  9 20:26:22 xeon-e3 kernel: [20714.344239] Restarting tasks ... done.
Dec  9 20:26:22 xeon-e3 kernel: [20714.360230] PM: suspend exit
Dec  9 20:26:22 xeon-e3 NetworkManager[981]:   [1544415982.1278] device 
(enp12s0): state change: disconnected -> unavailable (reason 'carrier-changed', 
sys-iface-state: 'managed')
Dec  9 20:26:22 xeon-e3 NetworkManager[981]:   [1544415982.1942] manager: 
sleep: wake requested (sleeping: yes  enabled: yes)
Dec  9 20:26:22 xeon-e3 NetworkManager[981]:   [1544415982.1943] device 
(eno1): state change: unavailable -> unmanaged (reason 'sleeping', 
sys-iface-state: 'managed')
Dec  9 20:26:22 xeon-e3 kernel: [20714.532995] e1000e: eno1 NIC Link is Down
Dec  9 20:26:22 xeon-e3 NetworkManager[981]:   [1544415982.3157] device 
(enp12s0): state change: unavailable -> unmanaged (reason 'sleeping', 
sys-iface-state: 'managed')
Dec  9 20:26:22 xeon-e3 NetworkManager[981]:   [1544415982.3457] device 
(eno1): state change: unmanaged -> unavailable (reason 'managed', 
sys-iface-state: 'managed')
Dec  9 20:26:22 xeon-e3 kernel: [20714.564522] IPv6: ADDRCONF(NETDEV_UP): eno1: 
link is not ready
Dec  9 20:26:22 xeon-e3 NetworkManager[981]:   [1544415982.5866] device 
(enp12s0): state change: unmanaged -> unavailable (reason 'managed', 
sys-iface-state: 'managed')
Dec  9 20:26:22 xeon-e3 kernel: [20714.803738] IPv6: ADDRCONF(NETDEV_UP): eno1: 
link is not ready
Dec  9 20:26:22 xeon-e3 kernel: [20714.805578] IPv6: ADDRCONF(NETDEV_UP): 
enp12s0: link is not ready
Dec  9 20:26:22 xeon-e3 NetworkManager[981]:   [1544415982.6112] device 
(ens4): state change: unmanaged -> unavailable (reason 'managed', 
sys-iface-state: 'managed')
Dec  9 20:26:22 xeon-e3 kernel: [20714.828119] IPv6: ADDRCONF(NETDEV_UP): 
enp12s0: link is not ready
Dec  9 20:26:22 xeon-e3 kernel: [20714.830112] IPv6: ADDRCONF(NETDEV_UP): ens4: 
link is not ready
Dec  9 20:26:22 xeon-e3 kernel: [20714.891741] IPv6: ADDRCONF(NETDEV_UP): ens4: 
link is not ready
Dec  9 20:26:25 xeon-e3 kernel: [20717.780117] igb :0c:00.0 enp12s0: igb: 
enp12s0 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: RX/TX
Dec  9 20:26:25 xeon-e3 NetworkManager[981]:   [1544415985.6705] device 
(enp12s0): carrier: link connected
Dec  9 20:26:25 xeon-e3 NetworkManager[981]:   [1544415985.6708] device 
(enp12s0): state change: unavailable -> disconnected (reason 'carrier-changed', 
sys-iface-state: 'managed')
Dec  9 20:26:25 xeon-e3 kernel: [20717.887814] IPv6: ADDRCONF(NETDEV_CHANGE): 
enp12s0: link becomes ready
Dec  9 20:28:37 xeon-e3 NetworkManager[981]:   [1544416117.5657] 
agent-manager: req[0x7fa62c0028b0, :1.227/org.gnome.Shell.NetworkAgent/1000]: 
agent registered

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

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

Versions of packages network-manager depends on:
ii  adduser3.118
ii  dbus   1.12.10-1
ii  init-system-helpers1.56
ii  libaudit1  1:2.8.4-2
ii  libbluetooth3  5.50-1
ii  libc6  2.27-8
ii  libcurl3-gnutls7.62.0-1
ii  libglib2.0-0   2.58.1-2
ii  libgnutls303.5.19-1+b1
ii  libjansson4

Bug#916413: libqt5serialbus5-plugins: socketcan plugin not included

[Fabian Inostroza]

Package: libqt5serialbus5-plugins
Version: 5.11.2-2
Severity: important

Dear Maintainer,

The socketcan plugin for the qtserialbus library is not included in the package.
Execute
/usr/lib/qt5/bin/canbusutil --list-plugins
to list installed plugins.

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

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

Versions of packages libqt5serialbus5-plugins depends on:
ii  libc6 2.27-8
ii  libqt5core5a  5.11.2+dfsg-7
ii  libqt5serialbus5  5.11.2-2
ii  libstdc++68.2.0-9

libqt5serialbus5-plugins recommends no packages.

libqt5serialbus5-plugins suggests no packages.

-- no debconf information

Bug#916412: please don't hard code the gcc tarball name

[Matthias Klose]

Package: src:ghdl
Version: 0.35+git20181129+dfsg-2
Tags: patch


please don't hard code the gcc tarball name. Not everbody has to use the dfsg
tarballs. patch at
http://launchpadlibrarian.net/401461719/ghdl_0.35+git20181129+dfsg-2_0.35+git20181129+dfsg-2ubuntu1.diff.gz

Bug#916411: nocache: document debug option in the manual page

[Paul Wise]

Package: nocache
Version: 1.0-1
Severity: wishlist
Usertags: manual

nocache has a debug option that is not documented:

$ grep -FA2 'D)' `which nocache`
D) exec {debugfd}>"$OPTARG"
   export NOCACHE_DEBUGFD="$debugfd"
   ;;

Thanks to dwfreed for pointing this out on #debian-devel.

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

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

Versions of packages nocache depends on:
ii  libc6  2.28-2

nocache recommends no packages.

nocache suggests no packages.

-- no debconf information

-- 
bye,
pabs

https://wiki.debian.org/PaulWise



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

Bug#916403: wordpress: Several security issues versions 3.8-5.0

[Salvatore Bonaccorso]

HI Craig,

On Fri, Dec 14, 2018 at 10:47:55AM +1100, Craig Small wrote:
[...]
> I'll raise some CVE requests if they are not already in train.

That would be appreciated if you can take care of it.

Regards,
Salvatore

Bug#756051: Affordable to set up web site

[manav rathore]

Hello,there,

Website will be complete dynamic and with the help of CMS you will be able to 
manage all the content and images of website.


If you want to create your website, please get back to us.


Regards,

Manav

New Delhi.

Bug#916406: libarb-dev: Missing symbols in static libraries

[Andreas Tille]

Hi Elmar,

On Thu, Dec 13, 2018 at 05:36:09PM -0700, Elmar wrote:
> Package: libarb-dev
> Version: 6.0.6-4
> Severity: important
> Tags: patch

The bug report is tagged "patch" but there is nothing
attached.

Kind regards

   Andreas.

-- 
http://fam-tille.de

Bug#900777: fontmake: fails to rebuild fonts-firacode from its glyphs source

[Yao Wei]

Hi,

fontmake and the dependencies has been updated:

  * fontmake 1.8.0: https://salsa.debian.org/fonts-team/fontmake
  * glyphslib 3.1.4: https://salsa.debian.org/fonts-team/glyphslib
  * mutatormath 2.1.2: https://salsa.debian.org/fonts-team/mutatormath
  * fontmath 0.4.9: https://salsa.debian.org/fonts-team/fontmath

On Fri, Dec 14, 2018 at 10:23:10AM +0800, Yao Wei wrote:
> > fontmake 1.6.1 has been in Debian since September. Maybe you're
> > thinking of fontmake 1.8 which isn't in Salsa yet.
> 
> Ouch.  I will update this soon.

Yao Wei


signature.asc
Description: PGP signature

Bug#916410: chromium: Chromium 71.0.3578.80-1 fails to build from source due to missing subdirectories in third_party

[Maxim Biro]

Package: chromium
Version: 71.0.3578.80-1
Severity: serious
Justification: fails to build from source (but built successfully in the past)

Trying to build Chromium off the source package, but it fails with Chromium's
builds system unable to find third_party/{libvpx,opus,freetype} and so on.

Here is what I do:

sudo docker run --rm -it -v /tmp/chromium-pkgs:/build debian:sid /bin/bash
echo "
deb http://deb.debian.org/debian sid main contrib
deb-src http://deb.debian.org/debian/ sid main contrib
" > /etc/apt/sources.list
apt-get update
apt-get dist-upgrade -y
apt-get install -y fakeroot devscripts build-essential
apt-get build-dep -y chromium
cd /build
apt-get source -y chromium
cd chromium-*
debuild

The error:

# debuild
dpkg-buildpackage -us -uc -ui
dpkg-buildpackage: info: source package chromium
dpkg-buildpackage: info: source version 71.0.3578.80-1
dpkg-buildpackage: info: source distribution unstable
dpkg-buildpackage: info: source changed by Michael Gilbert

dpkg-source --before-build .
dpkg-buildpackage: info: host architecture amd64
debian/rules clean
dh clean
  debian/rules override_dh_auto_clean
make[1]: Entering directory '/build/chromium-71.0.3578.80'
rm -rf out
find . -name \*.pyc -execdir rm -f {} \;
dh_auto_clean
make[1]: Leaving directory '/build/chromium-71.0.3578.80'
  dh_clean
rm -f debian/debhelper-build-stamp
rm -rf debian/.debhelper/
/build/chromium-71.0.3578.80/debian/clean: 1:
/build/chromium-71.0.3578.80/debian/clean: debian/files: not found
/build/chromium-71.0.3578.80/debian/clean: 2:
/build/chromium-71.0.3578.80/debian/clean: debian/scripts/mk-origtargz: not
found
/build/chromium-71.0.3578.80/debian/clean: 4:
/build/chromium-71.0.3578.80/debian/clean: Makefile: not found
/build/chromium-71.0.3578.80/debian/clean: 5:
/build/chromium-71.0.3578.80/debian/clean: third_party/flot/*.js: not found
/build/chromium-71.0.3578.80/debian/clean: 7:
/build/chromium-71.0.3578.80/debian/clean: base/third_party/libevent/BUILD.gn:
not found
/build/chromium-71.0.3578.80/debian/clean: 8:
/build/chromium-71.0.3578.80/debian/clean:
build/secondary/third_party/libjpeg_turbo/BUILD.gn: not found
/build/chromium-71.0.3578.80/debian/clean: 10:
/build/chromium-71.0.3578.80/debian/clean: third_party/re2/BUILD.gn: not found
/build/chromium-71.0.3578.80/debian/clean: 11:
/build/chromium-71.0.3578.80/debian/clean: third_party/icu/BUILD.gn: not found
/build/chromium-71.0.3578.80/debian/clean: 12:
/build/chromium-71.0.3578.80/debian/clean: third_party/flac/BUILD.gn: not found
third_party/zlib/BUILD.gn: 5: third_party/zlib/BUILD.gn: Syntax error: "{"
unexpected (expecting "then")
/build/chromium-71.0.3578.80/debian/clean: 14:
/build/chromium-71.0.3578.80/debian/clean: third_party/opus/BUILD.gn: not found
/build/chromium-71.0.3578.80/debian/clean: 15:
/build/chromium-71.0.3578.80/debian/clean: third_party/snappy/BUILD.gn: not
found
third_party/ffmpeg/BUILD.gn: 5: third_party/ffmpeg/BUILD.gn: Syntax error: word
unexpected (expecting ")")
third_party/libxml/BUILD.gn: 7: third_party/libxml/BUILD.gn: Syntax error: "{"
unexpected (expecting "then")
/build/chromium-71.0.3578.80/debian/clean: 18:
/build/chromium-71.0.3578.80/debian/clean: third_party/libdrm/BUILD.gn: not
found
/build/chromium-71.0.3578.80/debian/clean: 19:
/build/chromium-71.0.3578.80/debian/clean: third_party/libpng/BUILD.gn: not
found
/build/chromium-71.0.3578.80/debian/clean: 20:
/build/chromium-71.0.3578.80/debian/clean: third_party/libvpx/BUILD.gn: not
found
/build/chromium-71.0.3578.80/debian/clean: 21:
/build/chromium-71.0.3578.80/debian/clean: third_party/libwebp/BUILD.gn: not
found
/build/chromium-71.0.3578.80/debian/clean: 22:
/build/chromium-71.0.3578.80/debian/clean: third_party/libjpeg/BUILD.gn: not
found
/build/chromium-71.0.3578.80/debian/clean: 23:
/build/chromium-71.0.3578.80/debian/clean: third_party/libxslt/BUILD.gn: not
found
/build/chromium-71.0.3578.80/debian/clean: 24:
/build/chromium-71.0.3578.80/debian/clean: third_party/freetype/BUILD.gn: not
found
/build/chromium-71.0.3578.80/debian/clean: 25:
/build/chromium-71.0.3578.80/debian/clean: third_party/fontconfig/BUILD.gn: not
found
third_party/yasm/yasm_assemble.gni: 44: third_party/yasm/yasm_assemble.gni:
Syntax error: "{" unexpected (expecting "then")
/build/chromium-71.0.3578.80/debian/clean: 31:
/build/chromium-71.0.3578.80/debian/clean: third_party/yasm/run_yasm.py: not
found
/build/chromium-71.0.3578.80/debian/clean: 33:
/build/chromium-71.0.3578.80/debian/clean:
tools/gn/base/numerics/safe_math_arm_impl.h: not found
/build/chromium-71.0.3578.80/debian/clean: 34:
/build/chromium-71.0.3578.80/debian/clean:
tools/gn/base/numerics/safe_conversions_arm_impl.h: not found
/build/chromium-71.0.3578.80/debian/clean: 36:
/build/chromium-71.0.3578.80/debian/clean:
third_party/catapult/third_party/polymer/components: not found
dh_clean: debian/clean is marked executable but does not appear to an
executable config.
dh_clean:
dh_clean: If debian/clean is intended to be 

Bug#516692: audacity: no PulseAudio devices presented

[ben]

This is still a problem in testing, almost 10 years after this bug was
originally filed. Audacity can be built with pulse support nowadays, and 
not
having it makes it completely unusable under some setups (some sound 
devices

simply aren't there, or will have the wrong configuration).

Please build audacity with pulse support enabled, that would solve this 
issue

for good.

Bug#900777: fontmake: fails to rebuild fonts-firacode from its glyphs source

[Yao Wei]

Hi,

Replying inline:

On Thu, Dec 13, 2018 at 10:00:46AM -0500, Jeremy Bicha wrote:
> I think I've done all of these today (or earlier) except for:
> 
> ufo2ft 2.5: the build requires skia-pathops. Did you want to work on
> packaging that too?

This is not an requirement as far as the source code suggests.  It seems
skia-pathops is optional, where booleanoperations is used by default for
path operations.

Also, skia has been in RFP for a while (#818180).  I think we can
package this but it is not a blocking issue for this package.

> fontmake 1.6.1 has been in Debian since September. Maybe you're
> thinking of fontmake 1.8 which isn't in Salsa yet.

Ouch.  I will update this soon.

Yao Wei


signature.asc
Description: PGP signature

Bug#912682: e: Bug#912682: usefulness of this package?

[gregor herrmann]

On Thu, 13 Dec 2018 21:25:58 +, Dominic Hargreaves wrote:

> > Ok but I don't see how this bug differs from #915550 and #915876 for both
> > of which the intent seems to remove the corresponding packages.
> > 
> > Shouldn't this package also be considered for removal?
> 
> Perhaps. We usually leave it a while in case it is upgraded, as the cost
> of having around for "a while" in unstable only is judged cheaper than
> the extra work needed to remove it and then reintroduce it. I think this
> is mostly a matter of personal opinion and we don't have a firm policy
> on this, but I'm sure other list members will correct me if I'm wrong.

This matches my impression of our habits as well.

I'd just like to add that the "maintenance cost" can be zero (no
releases, no bugs, no nothing) or can be high (e.g. breakage with
each new perl release) or anything in between. And our habit seems to
be that if there's no or hardly any work needed there's also no
particular need to trigger the removal steps.


Cheers,
gregor

-- 
 .''`.  https://info.comodo.priv.at -- Debian Developer https://www.debian.org
 : :' : OpenPGP fingerprint D1E1 316E 93A7 60A8 104D  85FA BB3A 6801 8649 AA06
 `. `'  Member VIBE!AT & SPI Inc. -- Supporter Free Software Foundation Europe
   `-   NP: Tom Waits: Tom Traubert's Blues


signature.asc
Description: Digital Signature

Bug#846667: solved?

[gregor herrmann]

On Thu, 13 Dec 2018 15:51:58 +0100, cyri...@bollu.be wrote:

> I could build this package in sid with the following command:
> 
> sbuild -j5 --no-apt-update -d unstable --no-clean-source --run-lintian
> --lintian-opts='--color always --display-info --display-experimental
>  --profile pkg-perl' --arch-all
> 
> Issue solved?

I don't think so.

The bug is about _occasional_ test failures, and cpantesters still
show them:
http://matrix.cpantesters.org/?dist=POE-Loop-Event%201.305
and the reproducible build also show failures:
https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/libpoe-loop-event-perl.html


Cheers,
gregor 

-- 
 .''`.  https://info.comodo.priv.at -- Debian Developer https://www.debian.org
 : :' : OpenPGP fingerprint D1E1 316E 93A7 60A8 104D  85FA BB3A 6801 8649 AA06
 `. `'  Member VIBE!AT & SPI Inc. -- Supporter Free Software Foundation Europe
   `-   NP: Cat Power: After All


signature.asc
Description: Digital Signature

Bug#805527: notify-osd: Autostart file uses a wrong program path

[Tony]

While your patch is not yet implemented, I fixed the problem on my system by 
setting up a symbolic link as follows.

#mkdir /usr/lib/notify-osd

#ln -s /usr/lib/x86_64-linux-gnu/notify-osd /usr/lib/notify-osd/notify-osd

Tony

Debian Stretch, Linux 4.9, SDDM 0.18, Openbox 3.6, Conky 1.10

Sent with [ProtonMail](https://protonmail.com) Secure Email.

Bug#916409: 'download' fails on '~' in version with 'Error: pattern not supported by this subcommand:'

[Arnaud Fontaine]

Source: aptitude
Severity: normal

Hi,

# aptitude download dirmngr=2.1.18-8~deb9u3
Error: pattern not supported by this subcommand: 'dirmngr=2.1.18-8~deb9u3'

Although the command  actually called by 'aptitude  download' ('apt download')
handles it without problem:
  # apt download dirmngr=2.1.18-8~deb9u3
  Get:1 http://ftp.jp.debian.org/debian stable/main amd64 dirmngr amd64 
2.1.18-8~deb9u3 [597 kB]
  Fetched 597 kB in 1s (857 kB/s)

Cheers,
Arnaud Fontaine

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

Bug#916408: pdns-server: TCP client queries to pdns-server with any backend ipv6 recursor fail

[No Reply]

Package: pdns-server 
Version: 4.0.3-1+deb9u2 
Severity: normal 

Dear Maintainer, 

pdns-server in Stretch fails to answer TCP queries made by clients via backend 
recursors reached over IPv6. I discovered this setting up cloudflared, using it 
as the recursor, but have also replicated on a clean install with Google and 
Cloudflare's public DNS servers. 

NB: test addresses used below: 

CF DNS: 1.1.1.1 (ipv4), 2606:4700:4700:: (ipv6) 
Google DNS: 8.8.8.8 (ipv4), 2001:4860:4860:: (ipv6) 

Up to date just-installed Stretch x64 server: 

root@pdnsbugtest:~# lsb_release -a 
No LSB modules are available. 
Distributor ID:Debian 
Description:Debian GNU/Linux 9.6 (stretch) 
Release:9.6 
Codename:stretch 

root@pdnsbugtest:~# uname -a 
Linux pdnsbugtest 4.9.0-8-amd64 #1 SMP Debian 4.9.130-2 (2018-10-27) x86_64 
GNU/Linux 

root@pdnsbugtest:~# apt update && apt full-upgrade 
Hit:1 http://security.debian.org/debian-security stretch/updates InRelease 
Ign:2 http://ftp.uk.debian.org/debian stretch InRelease 
Hit:3 http://ftp.uk.debian.org/debian stretch-updates InRelease 
Hit:4 http://ftp.uk.debian.org/debian stretch Release 
Reading package lists... Done 
Building dependency tree 
Reading state information... Done 
All packages are up to date. 
Reading package lists... Done 
Building dependency tree 
Reading state information... Done 
Calculating upgrade... Done 
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. 

Only packages installed on top of base (base Debian server with 
openssh-server): vim, open-vm-tools, dnsutils, pdns-server 

root@pdnsbugtest:~# pdns_server --version 
Dec 13 23:48:43 PowerDNS Authoritative Server 4.0.3 (C) 2001-2016 PowerDNS.COM 
BV 
Dec 13 23:48:43 Using 64-bits mode. Built using gcc 6.3.0 20170516. 
Dec 13 23:48:43 PowerDNS comes with ABSOLUTELY NO WARRANTY. This is free 
software, and you are welcome to redistribute it according to the terms of the 
GPL version 2. 
Dec 13 23:48:43 Features: botan1.10 openssl lua 
Dec 13 23:48:43 Built-in modules: 
Dec 13 23:48:43 Configured with: " '--build=x86_64-linux-gnu' '--prefix=/usr' 
'--includedir=${prefix}/include' '--mandir=${prefix}/share/man' 
'--infodir=${prefix}/share/info' '--sysconfdir=/etc' '--localstatedir=/var' 
'--disable-silent-rules' '--libdir=${prefix}/lib/x86_64-linux-gnu' 
'--libexecdir=${prefix}/lib/x86_64-linux-gnu' '--disable-maintainer-mode' 
'--disable-dependency-tracking' '--sysconfdir=/etc/powerdns' 
'--with-dynmodules=bind ldap pipe gmysql godbc gpgsql gsqlite3 geoip lua mydns 
remote random opendbx tinydns' '--with-modules=' 
'--with-pgsql-includes=/usr/include/postgresql' '--enable-botan1.10' 
'--enable-tools' '--without-protobuf' '--enable-unit-tests' 
'--enable-reproducible' '--enable-systemd' '--with-systemd=/lib/systemd/system' 
'build_alias=x86_64-linux-gnu' 'CFLAGS=-g -O2 
-fdebug-prefix-map=/build/pdns-cB0QhU/pdns-4.0.3=. -fstack-protector-strong 
-Wformat -Werror=format-security' 'LDFLAGS=-Wl,-z,relro' 'CPPFLAGS=-Wdate-time 
-D_FORTIFY_SOURCE=2' 'CXXFLAGS=-g -O2 
-fdebug-prefix-map=/build/pdns-cB0QhU/pdns-4.0.3=. -fstack-protector-strong 
-Wformat -Werror=format-security 
-DPACKAGEVERSION='\''"4.0.3-1+deb9u2.Debian"'\'''" 

Standard pdns.conf, plus 2 config variables to enable recursion ('recursor', 
'allow-recursion'): 

root@pdnsbugtest:~# grep -v "^$\|^#" /etc/powerdns/pdns.conf 
allow-recursion=0.0.0.0/0,::/0 
include-dir=/etc/powerdns/pdns.d 
launch= 
recursor=1.1.1.1 
security-poll-suffix= 
setgid=pdns 
setuid=pdns 

Now, we can test. First, direct to CF and then via pdns, with and without TCP, 
over ipv4: 

root@pdnsbugtest:~# grep recursor= /etc/powerdns/pdns.conf; dig +short +notcp 
google.com @1.1.1.1; dig +short +tcp google.com @1.1.1.1; dig +short +notcp 
google.com @127.0.0.1; dig +short +tcp google.com @127.0.0.1 
recursor=1.1.1.1 
216.58.206.142 
216.58.206.142 
216.58.206.142 
216.58.206.142 

Now the same, but with Google: 

root@pdnsbugtest:~# grep recursor= /etc/powerdns/pdns.conf; dig +short +notcp 
google.com @8.8.8.8; dig +short +tcp google.com @8.8.8.8; dig +short +notcp 
google.com @127.0.0.1; dig +short +tcp google.com @127.0.0.1 
recursor=8.8.8.8 
216.58.206.110 
216.58.206.110 
216.58.206.110 
216.58.204.78 

All good. Now let's try with CF's ipv6 server as the recursor: 

[root@pdnsbugtest:~# grep recursor= /etc/powerdns/pdns.conf; dig +short +notcp 
google.com @2606:4700:4700::; dig +short +tcp google.com 
@2606:4700:4700::; dig +short +notcp google.com @127.0.0.1; dig +short +tcp 
google.com @127.0.0.1 
recursor=2606:4700:4700:: 
216.58.206.110 
216.58.206.110 
216.58.206.110 
;; communications error to 127.0.0.1#53: end of file 

Uh-oh. What about Google? 

[root@pdnsbugtest:~# grep recursor= /etc/powerdns/pdns.conf; dig +short +notcp 
google.com @2001:4860:4860::; dig +short +tcp google.com 
@2001:4860:4860::; dig +short +notcp google.com @127.0.0.1; dig +short +tcp 
google.com @127.0.0.1 
recursor=2001:4860:4860:: 

Bug#916247: upgrade 239.1+20181115-1 -> 239.3-1+patch still has problems with mplayer in currently running session

[Mark Hindley]

On Thu, Dec 13, 2018 at 02:20:01PM +, Mark Hindley wrote:
> This is a different issue. I am discussing solutions with upstream. 
> 
> See https://github.com/elogind/elogind/issues/104

Arthur,

Could you try this patch please? It works for me.

commit db6a15aa2b3a575a63bf567915e96575db938c84
Author: Mark Hindley 
Date:   Fri Dec 14 00:45:35 2018 +

Work around for #916247

When restarting use SIGKILL so that existing sessions and seats are 
preserved.

diff --git a/debian/elogind.init b/debian/elogind.init
index 6ebab7bc8..4f317f480 100644
--- a/debian/elogind.init
+++ b/debian/elogind.init
@@ -53,7 +53,8 @@ case "$1" in
 ;;
   force-reload|restart)
 log_daemon_msg "Restarting session management daemon" "elogind" || true
-start-stop-daemon --stop --quiet --oknodo --retry 30 --pidfile $ELOGIND_PID
+# Use SIGKILL so that existing seats and sessions are not cleared
+start-stop-daemon --stop --quiet --oknodo --signal KILL --retry 30 
--pidfile $ELOGIND_PID
 if start-stop-daemon --start --quiet --oknodo --pidfile $ELOGIND_PID 
--exec $ELOGIND -- $ELOGIND_OPTS; then
 log_end_msg 0 || true
 else

Bug#916349: xterm: X error (BadLength) with GNU screen

[Thomas Dickey]

- Original Message -
| From: "Vincent Lefevre" 
| To: "Thomas Dickey" , 916349-qu...@bugs.debian.org
| Cc: 916...@bugs.debian.org
| Sent: Thursday, December 13, 2018 7:20:00 PM
| Subject: Bug#916349: xterm: X error (BadLength) with GNU screen

| Control: retitle -1 xterm: X error (BadLength) when trying to display some
| glyphs
| 
| On 2018-12-13 18:35:43 -0500, Thomas Dickey wrote:
|> On Thu, Dec 13, 2018 at 06:25:42PM -0500, Thomas Dickey wrote:
|> > On Thu, Dec 13, 2018 at 02:11:28PM +0100, Vincent Lefevre wrote:
|> > > Package: xterm
|> > > Version: 338-1
|> > > Severity: grave
|> 
|> make it normal (and read the guidelines...)
| 
| I disagree. That's actually data loss, thus grave. And what makes it
| worse, this is typically from data from remote users (received mail).


fine - I'll work on the Arch bug, and will not discuss this one with you 
anymore.

bye

-- 
Thomas E. Dickey 
http://invisible-island.net
ftp://ftp.invisible-island.net

Bug#916406: libarb-dev: Missing symbols in static libraries

[Elmar]

Package: libarb-dev
Version: 6.0.6-4
Severity: important
Tags: patch

Somehow all symbols have been wiped from the static libraries, making them
useless.

nm /usr/lib/arb/SL/HELIX/HELIX.a
nm: /usr/lib/arb/SL/HELIX/HELIX.a: no symbols






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

Kernel: Linux 4.15.0-42-generic (SMP w/16 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 libarb-dev depends on:
ii  libarb  6.0.6-4

libarb-dev recommends no packages.

libarb-dev suggests no packages.

-- no debconf information

Bug#916407: Image built by autopkgtest-build-qemu does not work

[Bernhard Schmidt]

Package: autopkgtest
Version: 5.7
Severity: normal
File: /usr/bin/autopkgtest-virt-qemu

Hi,

I'm probably doing some very stupid error.

I'm using autopkgtest-virt-qemu to run autopkgtest on src:asterisk. I
previously had an image provided by vmdebootstrap that works just fine, but
needs some update. I tried to recreate it using autopkgtest-build-qemu and the
resulting image fails to run.

autopkgtest [01:36:02]: version 5.7
autopkgtest [01:36:02]: host BOTOX; command line: /usr/bin/autopkgtest -B -- 
qemu /var/lib/schroot/btrfs/autopkgtest-sid-vmdb2.img.raw
qemu-system-x86_64: terminating on signal 15 from pid 3723 (/usr/bin/python3)
: failure: The VM does not start a root shell on ttyS1 already. 
The only other supported login mechanism is through --user and --password on 
the guest ttyS0

Thanks,
Bernhard

Bug#916405: vmdb2 (called from autopkgtest-build-qemu) fails to unmount loop

[Bernhard Schmidt]

Package: vmdb2
Version: 0.13.2-2
Severity: important

Hi,

building a new autopkgtest image with autopkgtest-build-qemu (which uses vmdb2)
fails with the following error

root@BOTOX:/var/lib/schroot/btrfs# autopkgtest-build-qemu unstable 
/var/lib/schroot/btrfs/autopkgtest-sid-vmdb2.img 
http://debian.mirror.lrz.de/debian
Using customization script /usr/share/autopkgtest/setup-commands/setup-testbed 
...
Load spec file /tmp/tmp.g5edaZwjSn
Creating image file /var/lib/schroot/btrfs/autopkgtest-sid-vmdb2.img.raw (size 
20G)
Exec: ['qemu-img', 'create', '-f', 'raw', 
'/var/lib/schroot/btrfs/autopkgtest-sid-vmdb2.img.raw', '20G']
Creating partition table (msdos) on 
/var/lib/schroot/btrfs/autopkgtest-sid-vmdb2.img.raw
Exec: ['parted', '-s', '/var/lib/schroot/btrfs/autopkgtest-sid-vmdb2.img.raw', 
'mklabel', 'msdos']
Creating partition (primary) on 
/var/lib/schroot/btrfs/autopkgtest-sid-vmdb2.img.raw (0% to 100%)
Exec: ['parted', '-s', '/var/lib/schroot/btrfs/autopkgtest-sid-vmdb2.img.raw', 
'mkpart', 'primary', 'ext2', '0%', '100%']
Exec: ['kpartx', '-dsv', '/var/lib/schroot/btrfs/autopkgtest-sid-vmdb2.img.raw']
Exec: ['kpartx', '-asv', '/var/lib/schroot/btrfs/autopkgtest-sid-vmdb2.img.raw']
Creating ext4 filesystem on /dev/mapper/loop0p1
Exec: ['/sbin/mkfs', '-t', 'ext4', '/dev/mapper/loop0p1']
Exec: ['mount', '/dev/mapper/loop0p1', '/tmp/tmpz1biu6_9']
Debootstrap unstable /tmp/tmpz1biu6_9 http://debian.mirror.lrz.de/debian
Exec: ['debootstrap', '--variant', '-', 'unstable', '/tmp/tmpz1biu6_9', 
'http://debian.mirror.lrz.de/debian']
Exec: ['chroot', '/tmp/tmpz1biu6_9', 'apt-get', '-y', '--no-show-progress', 
'install', 'eatmydata']
Exec: ['chroot', '/tmp/tmpz1biu6_9', 'eatmydata', 'apt-get', '-y', 
'--no-show-progress', 'install', 'linux-image-amd64', 'ifupdown']
chroot /tmp/tmpz1biu6_9 to passwd --delete root useradd --home-dir /home/user 
--create-home user passwd --delete user echo host > /etc/hostname
Exec: ['chroot', '/tmp/tmpz1biu6_9', 'sh', '-c', 'passwd --delete root\nuseradd 
--home-dir /home/user --create-home user\npasswd --delete user\necho host > 
/etc/hostname']
Installing GRUB for BIOS
Exec: ['mount', '--bind', '/dev', '/tmp/tmpz1biu6_9/dev']
Exec: ['mount', '--bind', '/proc', '/tmp/tmpz1biu6_9/proc']
Exec: ['mount', '--bind', '/sys', '/tmp/tmpz1biu6_9/sys']
Install grub-pc in chroot /tmp/tmpz1biu6_9
Exec: ['chroot', '/tmp/tmpz1biu6_9', 'apt-get', '-y', '--no-show-progress', 
'install', 'grub-pc']
Exec: ['chroot', '/tmp/tmpz1biu6_9', 'grub-mkconfig', '-o', 
'/boot/grub/grub.cfg']
Exec: ['chroot', '/tmp/tmpz1biu6_9', 'grub-install', '--target=i386-pc', 
'--no-nvram', '--force-extra-removable', '--no-floppy', '--modules=part_msdos 
part_gpt', '--grub-mkdevicemap=/boot/grub/device.map', '/dev/loop0']
Exec: ['umount', '/tmp/tmpz1biu6_9/dev']
Exec: ['umount', '/tmp/tmpz1biu6_9/proc']
Exec: ['umount', '/tmp/tmpz1biu6_9/sys']
ERROR: Command failed: umount /tmp/tmpz1biu6_9/sys
b''
b'umount: /tmp/tmpz1biu6_9/sys: target is busy.\n'
Something went wrong, cleaning up!
Exec: ['umount', '/tmp/tmpz1biu6_9']
ERROR: Command failed: umount /tmp/tmpz1biu6_9
b''
b'umount: /tmp/tmpz1biu6_9: target is busy.\n'
Undoing loopback devices for partitions on 
/var/lib/schroot/btrfs/autopkgtest-sid-vmdb2.img.raw
Exec: ['kpartx', '-dsv', '/var/lib/schroot/btrfs/autopkgtest-sid-vmdb2.img.raw']
ERROR: Command failed: kpartx -dsv 
/var/lib/schroot/btrfs/autopkgtest-sid-vmdb2.img.raw
b'loop0p1 is in use. Not removing'
b'loop deleted : /dev/loop0\n'

I have no exact idea why, but the culprit is a mount of
/tmp/tmpz1biu6_9/sys/fs/fuse/connections that is not visible anywhere.  I
could not see it in mount, but autocompletion of umount
/tmp/tmpz1biu6_9/sys/ showed it. After umount I was able to unmount
/tmp/.../sys and finally /tmp/tmp...

Bernhard


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

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

Versions of packages vmdb2 depends on:
ii  cmdtest 0.32-2
ii  debootstrap 1.0.111
ii  kpartx  0.7.9-1
ii  parted  3.2-23
ii  python3 3.6.7-1
ii  python3-cliapp  1.20180812.1-2
ii  python3-jinja2  2.10-1
ii  python3-yaml3.13-1

Versions of packages vmdb2 recommends:
ii  ansible  2.7.1+dfsg-2

vmdb2 suggests no packages.

-- no debconf information

Bug#916404: steam: Depend or at least suggest vulkan

[Salvo Tomaselli]

Package: steam
Version: 1.0.0.56-1
Severity: important

Dear Maintainer,

I could not play "Artifact" on linux… because I was lacking the vulkan drivers
for intel.

mesa-vulkan-drivers

I think steam should depend on it since they are pushing games to use vulkan
rather than opengl.

Or at least recommend it.

Best

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

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

Versions of packages steam depends on:
ii  debconf [debconf-2.0]1.5.69
ii  libc62.28-2
ii  libgl1-mesa-dri  18.2.6-1
ii  libgl1-mesa-glx  18.2.6-1
ii  libgpg-error01.32-3
ii  libstdc++6   8.2.0-12
ii  libtxc-dxtn-s2tc [libtxc-dxtn0]  1.0+git20151227-2
ii  libudev1 239-15
ii  libx11-6 2:1.6.7-1
ii  libxinerama1 2:1.1.4-1
ii  xz-utils 5.2.2-1.3

Versions of packages steam recommends:
ii  ca-certificates20180409
ii  fontconfig 2.13.1-2
ii  fonts-liberation   1:1.07.4-9
ii  konsole [x-terminal-emulator]  4:18.04.0-1
ii  libxss11:1.2.3-1
pn  nvidia-driver-libs-i386

Versions of packages steam suggests:
pn  steam-devices  

-- debconf information excluded

Bug#916349: xterm: X error (BadLength) with GNU screen

[Vincent Lefevre]

Control: retitle -1 xterm: X error (BadLength) when trying to display some 
glyphs

On 2018-12-13 18:35:43 -0500, Thomas Dickey wrote:
> On Thu, Dec 13, 2018 at 06:25:42PM -0500, Thomas Dickey wrote:
> > On Thu, Dec 13, 2018 at 02:11:28PM +0100, Vincent Lefevre wrote:
> > > Package: xterm
> > > Version: 338-1
> > > Severity: grave
> 
> make it normal (and read the guidelines...)

I disagree. That's actually data loss, thus grave. And what makes it
worse, this is typically from data from remote users (received mail).

Here, the issue was with Mutt (which I run in GNU Screen).

> > 1281  openat(AT_FDCWD, 
> > "/usr/share/fonts/truetype/dejavu/DejaVuSansMono.ttf", O_RDONLY) = 5
> > 1281  openat(AT_FDCWD, "/usr/share/fonts/truetype/noto/NotoColorEmoji.ttf", 
> > O_RDONLY) = 5
> 
> Which Debian package provides this font?

fonts-noto-color-emoji

FYI, it has been installed automatically via dependencies.

> I need that information, plus the details of the missing glyph to
> reproduce this issue.

U+1F4E2 PUBLIC ADDRESS LOUDSPEAKER
UTF-8: f0 9f 93 a2 UTF-16BE: d83ddce2 Decimal:  Octal: \0372342

Category: So (Symbol, Other)
Unicode block: 1F300..1F5FF; Miscellaneous Symbols and Pictographs
Bidi: ON (Other Neutrals)

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

Bug#916349: xterm: X error (BadLength) with GNU screen

[Thomas Dickey]

On Thu, Dec 13, 2018 at 06:35:43PM -0500, Thomas Dickey wrote:
> On Thu, Dec 13, 2018 at 06:25:42PM -0500, Thomas Dickey wrote:
> > On Thu, Dec 13, 2018 at 02:11:28PM +0100, Vincent Lefevre wrote:
> > > Package: xterm
> > > Version: 338-1
> > > Severity: grave
> 
> make it normal (and read the guidelines...)
> 
> > 1281  openat(AT_FDCWD, 
> > "/usr/share/fonts/truetype/dejavu/DejaVuSansMono.ttf", O_RDONLY) = 5
> > 1281  openat(AT_FDCWD, "/usr/share/fonts/truetype/noto/NotoColorEmoji.ttf", 
> > O_RDONLY) = 5
> 
> Which Debian package provides this font?

never mind - I have a copy, and can see that it doesn't work with Xft/etc.
You could have found that by running

xfd -fa 'Noto Color Emoji'

-- 
Thomas E. Dickey 
https://invisible-island.net
ftp://ftp.invisible-island.net


signature.asc
Description: Digital signature

Bug#916297: reportbug: crash after using "Display modified configuration files"

[nemo Inis]

That. IS. the. Full. Traceback.

And speaking of making lives much easier, get off my back.



On 13/12/2018 15.57, Sandro Tosi wrote:
> Just. Report. The. Full. Traceback.
> 
> That would make our lives so much easier
> 
> Thanks!
> 
> On Thu, Dec 13, 2018, 18:45 nemo Inis  
>> Sandro,
>>
>> 1) that one 'TypeError' line IS the 'unaltered, complete reportbug
>> traceback'
>>
>> 2) I don't think the specific package matters, only that it had a modified
>> config file. e.g. in
>> my case apt-cacher-ng, or apache2, or 
>>
>> 3) the bug is in reportbug/ui/gtk2_ui.py, in the class 'SystemPage(Page)'
>> which defines
>> 'on_child_exited' with two parameters when it should be three (the third
>> parameter being the
>> child's exit status code, as per Vte.Terminal.signals.child_exited
>> documentation for Vte 2.91)
>>
>>
>>
>> On 12/12/2018 12.13, Sandro Tosi wrote:
 When reporting a bug, reportbug sometimes issues a warning that "The
>> following
 configuration files have been modified:" (for the package being reported
 against).
 It then gives the option to Send the modified files, or "Display
>> modified
 configuration files (exit with "q")"

 Clicking that button displays the pertinent configuration files OK, but
>> after
 pressing q to exit back to the bug, reportbug dies with:

 TypeError: on_child_exited() takes 2 positional arguments but 3 were
>> given
>>>
>>> please report the unaltered. complete reportbug traceback.
>>>
>>> Does it happen for a specific package only or for multiple ones? in
>>> any case, report the exact package this is happening on
>>>
>>
> 

Bug#916297: reportbug: crash after using "Display modified configuration files"

[Sandro Tosi]

Just. Report. The. Full. Traceback.

That would make our lives so much easier

Thanks!

On Thu, Dec 13, 2018, 18:45 nemo Inis  Sandro,
>
> 1) that one 'TypeError' line IS the 'unaltered, complete reportbug
> traceback'
>
> 2) I don't think the specific package matters, only that it had a modified
> config file. e.g. in
> my case apt-cacher-ng, or apache2, or 
>
> 3) the bug is in reportbug/ui/gtk2_ui.py, in the class 'SystemPage(Page)'
> which defines
> 'on_child_exited' with two parameters when it should be three (the third
> parameter being the
> child's exit status code, as per Vte.Terminal.signals.child_exited
> documentation for Vte 2.91)
>
>
>
> On 12/12/2018 12.13, Sandro Tosi wrote:
> >> When reporting a bug, reportbug sometimes issues a warning that "The
> following
> >> configuration files have been modified:" (for the package being reported
> >> against).
> >> It then gives the option to Send the modified files, or "Display
> modified
> >> configuration files (exit with "q")"
> >>
> >> Clicking that button displays the pertinent configuration files OK, but
> after
> >> pressing q to exit back to the bug, reportbug dies with:
> >>
> >> TypeError: on_child_exited() takes 2 positional arguments but 3 were
> given
> >
> > please report the unaltered. complete reportbug traceback.
> >
> > Does it happen for a specific package only or for multiple ones? in
> > any case, report the exact package this is happening on
> >
>

Bug#916285: RFS: extsmail/2.2-1 -- enables the robust sending of e-mail to external commands

[Dmitry Bogatov]

[2018-12-12 17:38] Olivier Girondel 
> Severity: normal
> 
>   Dear mentors,
> 
>   I am looking for a sponsor for my package "extsmail"
> 
>  * Package name: extsmail
>Version : 2.2-1
>Upstream Author : Laurence Tratt 
>  * URL : https://tratt.net/laurie/src/extsmail/
>  * License : BSD/MIT
>Section : mail
> 
>   It builds this binary package:
> 
> extsmail   - enables the robust sending of e-mail to external commands
> 
>   The package appears to be lintian-clean
> 
>   To access further information about this package, please visit the
> following URL:
> 
>   https://mentors.debian.net/package/extsmail

Seems you have Vcs-* fields in `debian/control' wrong. They must point
to debianization Git, not to upstream Git.

Bug#833126: insserv: $named should contain pdns-recursor

[Dmitry Bogatov]

control: severity -1 wishlist

[2016-08-01 09:32] Peter Gervai 
> Package: insserv
> Version: 1.14.0-5.4
> Severity: important
> Tags: patch
> 
> please add pdns-recursor to /etc/insserv.conf:
> $named  +named +dnsmasq +lwresd +bind9 +unbound +pdns-recursor 
> $network

Sounds reasonable. Dear co-maintainers, any objections?

Bug#916403: wordpress: Several security issues versions 3.8-5.0

[Craig Small]

Source: wordpress
Version: 4.9.8
Severity: normal
Tags: security upstream


WordPress 5.0.1 has been released upstream which addresses multiple
security issues[1]

 * Karim El Ouerghemmi discovered that authors could alter meta data to
   delete files that they weren’t authorized to.
 * Simon Scannell of RIPS Technologies discovered that authors could create
   posts of unauthorized post types with specially crafted input.
 * Sam Thomas discovered that contributors could craft meta data in a way
   that resulted in PHP object injection.
 * Tim Coen discovered that contributors could edit new comments from
   higher-privileged users, potentially leading to a cross-site scripting
   vulnerability.
 * Tim Coen also discovered that specially crafted URL inputs could lead to
   a cross-site scripting vulnerability in some circumstances. WordPress
   itself was not affected, but plugins could be in some situations.
 * Team Yoast discovered that the user activation screen could be indexed
   by search engines in some uncommon configurations, leading to exposure
   of email addresses, and in some rare cases, default generated passwords.
 * Tim Coen and Slavco discovered that authors on Apache-hosted sites could
   upload specifically crafted files that bypass MIME verification, leading
   to a cross-site scripting vulnerability.

Phew!
Given it goes back to 3.8, it impacts every dist back to old stable.
I'll raise some CVE requests if they are not already in train.

1: https://wordpress.org/news/2018/12/wordpress-5-0-1-security-release/


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

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

Bug#916297: reportbug: crash after using "Display modified configuration files"

[nemo Inis]

Sandro,

1) that one 'TypeError' line IS the 'unaltered, complete reportbug traceback'

2) I don't think the specific package matters, only that it had a modified 
config file. e.g. in
my case apt-cacher-ng, or apache2, or 

3) the bug is in reportbug/ui/gtk2_ui.py, in the class 'SystemPage(Page)' which 
defines
'on_child_exited' with two parameters when it should be three (the third 
parameter being the
child's exit status code, as per Vte.Terminal.signals.child_exited 
documentation for Vte 2.91)



On 12/12/2018 12.13, Sandro Tosi wrote:
>> When reporting a bug, reportbug sometimes issues a warning that "The 
>> following
>> configuration files have been modified:" (for the package being reported
>> against).
>> It then gives the option to Send the modified files, or "Display modified
>> configuration files (exit with "q")"
>>
>> Clicking that button displays the pertinent configuration files OK, but after
>> pressing q to exit back to the bug, reportbug dies with:
>>
>> TypeError: on_child_exited() takes 2 positional arguments but 3 were given
> 
> please report the unaltered. complete reportbug traceback.
> 
> Does it happen for a specific package only or for multiple ones? in
> any case, report the exact package this is happening on
> 

Bug#916402: mono-basic: FTBFS when built in parallel

[Santiago Vila]

Package: src:mono-basic
Version: 4.0.1-2
Severity: serious
Tags: ftbfs

Dear maintainer:

I tried to build this package in buster but it failed:


[...]

make[4]: Entering directory '/<>/vbnc/vbnc/tests'
make all-local
make[5]: Entering directory '/<>/vbnc/vbnc/tests'
make[5]: Leaving directory '/<>/vbnc/vbnc/tests'
make[4]: Leaving directory '/<>/vbnc/vbnc/tests'
make all-local
make[4]: Entering directory '/<>/vbnc/vbnc'
../../vbnc/vbnc/setversion.sh ../../vbnc/vbnc/source/General/Version.vb
+ VERSION_VB=../../vbnc/vbnc/source/General/Version.vb
+ VERSION_TMP=version.tmp
++ cut -d ' ' -f 2
++ grep '^\*'
++ git branch
../../vbnc/vbnc/setversion.sh: line 6: git: command not found
++ true
+ GIT_BRANCH=
++ git log --no-color --first-parent -n1 --pretty=format:%h
../../vbnc/vbnc/setversion.sh: line 7: git: command not found
++ true
+ GIT_REVISION=
+ cat ../LicenseFileHeader.txt
+ echo ''
+ echo -n ''
+ diff version.tmp ../../vbnc/vbnc/source/General/Version.vb
diff: ../../vbnc/vbnc/source/General/Version.vb: No such file or directory
+ cp version.tmp ../../vbnc/vbnc/source/General/Version.vb
make[4]: Leaving directory '/<>/vbnc/vbnc'
make[3]: *** [../../build/rules.make:122: do-all] Error 2
make[3]: Leaving directory '/<>/vbnc/vbnc'
make[2]: *** [../build/rules.make:134: all-recursive] Error 1
make[2]: Leaving directory '/<>/vbnc'
make[1]: *** [build/rules.make:134: all-recursive] Error 1
make[1]: Leaving directory '/<>'
dh_auto_build: make V=1 -j2 returned exit code 2
make: *** [debian/rules:52: build-indep] Error 2
dpkg-buildpackage: error: debian/rules build-indep subprocess returned exit 
status 2


The following build logs were obtained on instances of type 1-S from Scaleway,
where the package seems to fail 100% of the time:

https://people.debian.org/~sanvila/build-logs/mono-basic/

Incidentally, on 1-XS instances (having only one CPU) it does not seem to fail, 
so this
seems to be some kind of Makefile bug.

The same error happens here:

https://tests.reproducible-builds.org/debian/rbuild/unstable/amd64/mono-basic_4.0.1-2.rbuild.log.gz

If you need help to reproduce this, please say so, I could offer a
test machine.

BTW: Build log contains "git: command not found". If git is not
required for the build, the use of git should be disabled, so that the
build is also possible (and reproducible!) when git is present.

Thanks.

Bug#916390: RFS: tlf/1.3.2-1 [put in ITP, ITA, RC, NMU if applicable]

[eamanu15]

Hi!

Don't forget select ITP, ITA, RC or NMU. This must be written on the
subject.



> More information about tlf can be obtained from https://www.example.com.
>
> I think that here must be the tlf page.

Regards!

-- 
Arias Emmanuel
http://eamanu.com
Github/Gitlab; @eamanu
Debian: @eamanu-guest

Bug#916349: xterm: X error (BadLength) with GNU screen

[Thomas Dickey]

On Thu, Dec 13, 2018 at 06:25:42PM -0500, Thomas Dickey wrote:
> On Thu, Dec 13, 2018 at 02:11:28PM +0100, Vincent Lefevre wrote:
> > Package: xterm
> > Version: 338-1
> > Severity: grave

make it normal (and read the guidelines...)

> 1281  openat(AT_FDCWD, "/usr/share/fonts/truetype/dejavu/DejaVuSansMono.ttf", 
> O_RDONLY) = 5
> 1281  openat(AT_FDCWD, "/usr/share/fonts/truetype/noto/NotoColorEmoji.ttf", 
> O_RDONLY) = 5

Which Debian package provides this font?

I need that information, plus the details of the missing glyph to reproduce
this issue.
 
> I haven't run into anything like this, of course, but with the font
> information and a (script) typescript to see what's sent to the screen,
> can probably see what's breaking.
> 
> I could add a feature to tell xterm to not exit on (certain) errors
> if it's not actually an xterm bug.  Seems it's not:
> 
> https://groups.google.com/forum/#!topic/wmii/i92CyORGZQ0
> https://bugzilla.redhat.com/show_bug.cgi?format=multiple=1498269
> https://github.com/cdown/clipmenu/issues/88

I had noticed this one, but didn't stumble onto one of the problematic
fonts when testing for missing glyphs:

https://bugs.archlinux.org/task/58706

-- 
Thomas E. Dickey 
https://invisible-island.net
ftp://ftp.invisible-island.net


signature.asc
Description: Digital signature

Bug#916400: squashfs-tools: please use more recent code that supports zstd

[Norbert Lange]

Package: squashfs-tools
Version: 1:4.3-6
Severity: normal

Dear Maintainer,

since kernel 4.14, squashfs supports zstandard while there
is no tool to create those images.

I would ask you to update to a version that supports zstd
before buster ends up in the freeze.
Newer versions are at https://github.com/plougher/squashfs-tools,
you probably know put the debian package homepage still points to
sourceforge
 
kind regards,
Norbert

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

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

Versions of packages squashfs-tools depends on:
ii  libc6  2.27-8
ii  liblz4-1   1.8.2-1
ii  liblzma5   5.2.2-1.3
ii  liblzo2-2  2.10-0.1
ii  libzstd1   1.3.5+dfsg-1
ii  zlib1g 1:1.2.11.dfsg-1

squashfs-tools recommends no packages.

squashfs-tools suggests no packages.

-- no debconf information

Bug#916349: xterm: X error (BadLength) with GNU screen

[Thomas Dickey]

On Thu, Dec 13, 2018 at 02:11:28PM +0100, Vincent Lefevre wrote:
> Package: xterm
> Version: 338-1
> Severity: grave
> Justification: renders package unusable
> 
> After upgrading xterm to 338-1, I get X errors when using GNU screen:
> 
> zira% xterm -e screen -r
> /usr/bin/xterm: warning, error event received:
> X Error of failed request:  BadLength (poly request too large or internal 
> Xlib length error)
>   Major opcode of failed request:  139 (RENDER)
>   Minor opcode of failed request:  20 (RenderAddGlyphs)

Perhaps it's a problem with the Xft improvements and a particular
glyph for which Xft/freetype2/fontconfig breaks.

The strace shows that xterm's opened a second font, and dies shortly
after:

1281  openat(AT_FDCWD, "/usr/share/fonts/truetype/dejavu/DejaVuSansMono.ttf", 
O_RDONLY) = 5
1281  openat(AT_FDCWD, "/usr/share/fonts/truetype/noto/NotoColorEmoji.ttf", 
O_RDONLY) = 5

I haven't run into anything like this, of course, but with the font
information and a (script) typescript to see what's sent to the screen,
can probably see what's breaking.

I could add a feature to tell xterm to not exit on (certain) errors
if it's not actually an xterm bug.  Seems it's not:

https://groups.google.com/forum/#!topic/wmii/i92CyORGZQ0
https://bugzilla.redhat.com/show_bug.cgi?format=multiple=1498269
https://github.com/cdown/clipmenu/issues/88

>   Serial number of failed request:  1168
>   Current serial number in output stream:  1200
> 
> This one is now always reproducible.
> 
> I've attached a compressed strace output, if this can be helpful.

-- 
Thomas E. Dickey 
https://invisible-island.net
ftp://ftp.invisible-island.net


signature.asc
Description: Digital signature

Bug#916401: ITP: jsp-api -- JavaServer Pages API

[Emmanuel Bourg]

Package: wnpp
Severity: wishlist
Owner: Emmanuel Bourg 

* Package name: jsp-api
  Version : 2.3.4
  Upstream Author : Oracle
* URL : https://github.com/javaee/javaee-jsp-api
* License : CDDL-1.1 or GPL-2 with Classpath exception
  Programming Lang: Java
  Description : JavaServer Pages API

JavaServer Pages (JSP) is a technology that helps software developers
create dynamically generated web pages based on HTML, XML, or other
document types.

The JSP API is already packaged in libservlet3.1-java, but this package is
tied to src:tomcat8 which won't be part of Buster. The new tomcat9 package
no longer builds the JavaEE APIs (Servlet, JSP, EL and WebSocket APIs) and
separate API packages are introduced to replace them.

This package will be maintained by the Java Team.

Bug#908945: NMU, debdiff

[Alf Gaida]

Hi Hilko,
probably wrong bug number - here is nothing to fix, only to remove.

Cheers Alf

On Thu, 13 Dec 2018 23:27:14 +0100 Hilko Bengen  wrote:
> Control: tag -1 pending
> 
> Dear maintainer,
> 
> I have just uploaded libfm/1.3.0.2-1.1, fixing this bug, to DELAYED/5;
> the relevant patches are attached to this mail. Feel free to reschedule
> or cancel my upload as you see fit.
> 
> BTW: You may want to check the debian branch in your Salsa repository,
> it contains the changes made to data/libfm.conf by
> debian/patches/01-lxde-conf.patch which caused trouble as I tried to
> build the package using git-buildpackge.
> 
> Cheers,
> -Hilko
> 

Bug#916398: sddm: Wayland autologin sometimes fails - probable tty1 race

[Michael Biebl]

Am 13.12.18 um 23:52 schrieb Rebecca N. Palmer:
> 
> Possible solutions (I have *not* tried them yet):
> - Patch sddm (at [3]) to assume VT 1 is never free
> - or, add a Conflicts=getty@tty1.service (and After= ?) to sddm.service

This is what gdm.service does:

$ systemctl cat gdm.service | grep getty
# replaces the getty
Conflicts=getty@tty1.service
After=getty@tty1.service

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



signature.asc
Description: OpenPGP digital signature

Bug#916399: vlc-plugin-bittorrent: crash (SIGABRT) on VLC shutdown

[Paul Wise]

Package: vlc-plugin-bittorrent
Version: 2.4-1
Severity: normal
Usertags: crash

When I quit VLC before the video has had a chance to play, I get a
crash (SIGABRT) and consequent core dump (when a core-dump-handler
package is enabled). Looking at the backtrace below, this might be a
bug in libtorrent, please reassign there if needed.

$ gdb -batch -n -ex 'handle SIG32 noprint' -ex 'set pagination off' -ex run -ex 
bt -ex 'thread apply all bt full' --args vlc 
https://archive.org/download/TheInternetsOwnBoyTheStoryOfAaronSwartz/TheInternetsOwnBoyTheStoryOfAaronSwartz_archive.torrent
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
VLC media player 3.0.4 Vetinari (revision 3.0.4-0-gf615db6332)
[New Thread 0x70a01700 (LWP 31024)]
[New Thread 0x73058700 (LWP 31025)]
[New Thread 0x7fffe0200700 (LWP 31026)]
[cb60] main libvlc: Running vlc with the default interface. Use 
'cvlc' to use vlc without interface.
[New Thread 0x7fffde5d0700 (LWP 31030)]
[New Thread 0x7fffdd806700 (LWP 31031)]
[New Thread 0x7fffdaf55700 (LWP 31032)]
[New Thread 0x7fffda754700 (LWP 31033)]

(vlc:31019): GLib-GObject-WARNING **: 06:55:04.061: The property 
GtkSettings:gtk-fallback-icon-theme is deprecated and shouldn't be used 
anymore. It will be removed in a future version.
[New Thread 0x7fffd9c0f700 (LWP 31034)]
[New Thread 0x7fffd92e7700 (LWP 31035)]
[New Thread 0x7fffd39d7700 (LWP 31036)]
[New Thread 0x7fffd30d4700 (LWP 31037)]
[New Thread 0x7fffd2fd3700 (LWP 31038)]
[New Thread 0x7fffd2ed2700 (LWP 31039)]
[Thread 0x7fffd2ed2700 (LWP 31039) exited]
[Detaching after vfork from child process 31040]
[New Thread 0x7fffd2ed2700 (LWP 31048)]
[Thread 0x7fffd2ed2700 (LWP 31048) exited]
[Thread 0x7fffd2fd3700 (LWP 31038) exited]
[Detaching after vfork from child process 31049]
[New Thread 0x7fffd2fd3700 (LWP 31055)]
[Thread 0x7fffd2fd3700 (LWP 31055) exited]
[New Thread 0x7fffd2fd3700 (LWP 31057)]
[New Thread 0x7fffd1043700 (LWP 31058)]
[New Thread 0x7fffd0041700 (LWP 31059)]
[New Thread 0x7fffd0842700 (LWP 31060)]
[New Thread 0x7fffcf840700 (LWP 31061)]
[New Thread 0x7fffcf03f700 (LWP 31062)]
[New Thread 0x7fffce83e700 (LWP 31063)]
[New Thread 0x7fffce03d700 (LWP 31064)]
[Thread 0x7fffd2fd3700 (LWP 31057) exited]
[Thread 0x7fffd30d4700 (LWP 31037) exited]
[New Thread 0x7fffd30d4700 (LWP 31065)]
[New Thread 0x7fffd2fd3700 (LWP 31066)]
[New Thread 0x7fffd2ed2700 (LWP 31067)]
[Thread 0x7fffd2ed2700 (LWP 31067) exited]
[Thread 0x7fffd2fd3700 (LWP 31066) exited]
[55a5c3a0] cache_read stream error: cannot pre fill buffer
[56011a40] mjpeg demux error: cannot peek
[Thread 0x7fffd30d4700 (LWP 31065) exited]
[Thread 0x73058700 (LWP 31025) exited]
[Thread 0x70a01700 (LWP 31024) exited]
[Thread 0x7fffd92e7700 (LWP 31035) exited]
[Thread 0x7fffdd806700 (LWP 31031) exited]
[Thread 0x7fffd39d7700 (LWP 31036) exited]
[Thread 0x7fffde5d0700 (LWP 31030) exited]
[Thread 0x7fffe0200700 (LWP 31026) exited]
QObject::~QObject: Timers cannot be stopped from another thread
[Thread 0x7fffd9c0f700 (LWP 31034) exited]
pure virtual method called
terminate called without an active exception

Thread 18 "vlc" received signal SIGABRT, Aborted.
[Switching to Thread 0x7fffd1043700 (LWP 31058)]
__GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:50
50  ../sysdeps/unix/sysv/linux/raise.c: No such file or directory.
#0  0x77dc485b in __GI_raise (sig=sig@entry=6) at 
../sysdeps/unix/sysv/linux/raise.c:50
#1  0x77daf535 in __GI_abort () at abort.c:79
#2  0x747e4943 in __gnu_cxx::__verbose_terminate_handler() () at 
../../../../src/libstdc++-v3/libsupc++/vterminate.cc:95
#3  0x747ea896 in __cxxabiv1::__terminate(void (*)()) 
(handler=) at 
../../../../src/libstdc++-v3/libsupc++/eh_terminate.cc:47
#4  0x747ea8d1 in std::terminate() () at 
../../../../src/libstdc++-v3/libsupc++/eh_terminate.cc:57
#5  0x747eb60f in __cxxabiv1::__cxa_pure_virtual() () at 
../../../../src/libstdc++-v3/libsupc++/pure.cc:50
#6  0x74045765 in boost::system::error_code::message[abi:cxx11]() const 
(this=0x7fffd1042ca0) at /usr/include/boost/system/error_code.hpp:495
#7  0x74045765 in 
libtorrent::natpmp::on_reply(boost::system::error_code const&, unsigned long) 
(this=0x5607b330, e=..., bytes_transferred=) at 
../../src/natpmp.cpp:428
#8  0x74047267 in boost::_mfi::mf2::call, boost::system::error_code 
const, unsigned long>(boost::shared_ptr&, void const*, 
boost::system::error_code const&, unsigned long&) const (this=0x7fffd1042c80, 
this=0x7fffd1042c80, b2=: , b1=..., u=...) at 
/usr/include/boost/smart_ptr/shared_ptr.hpp:964
#9  0x74047267 in boost::_mfi::mf2::operator() 
>(boost::shared_ptr&, boost::system::error_code const&, 
unsigned long) const (a2=, a1=..., u=..., this=0x7fffd1042c80) 
at /usr/include/boost/bind/mem_fn_template.hpp:286
#10 0x74047267 in 
boost::_bi::list3 >, 

Bug#916398: sddm: Wayland autologin sometimes fails - probable tty1 race

[Rebecca N. Palmer]

Package: sddm
Version: 0.14.0-4+deb9u1
X-Debbugs-Cc: pkg-systemd-maintain...@lists.alioth.debian.org

With this /etc/sddm.conf:
[Autologin]
User=rnpalmer
Session=plasmawayland.desktop

autologin works only ~80% of the time; failures usually drop to a text 
login prompt (which works but leads to a text shell, not KDE), but 
occasionally to an sddm graphical login screen (which works).


The system log contains "Jumping to VT 2" on success and "Jumping to VT 
1" on failure (plus "Failed to take control of the tty: Operation not 
permitted" on failure to graphical login screen), which suggests the 
problem is sddm trying to start a desktop and getty@tty1.service trying 
to start a text terminal on the same VT.


This implies the problem is Wayland-specific (sddm only switches VTs 
under Wayland, not X [0]) and also Debian-specific (as the upstream 
configuration disables getty@tty1.service and runs sddm itself on tty1 
[1]), but I have *not* explicitly tested either of these.


Adding systemd-logind.service (like 0.18 has) and getty@tty1.service to 
After= of sddm.service does *not* fix this, probably because 
getty@tty1.service is Type=idle (immediately mark it as "done", but 
don't actually start it until the end of boot [2]) and TTYVTDisallocate=yes.


I hence believe the order of events on failure to be
- systemd "starts" getty@tty1.service
- systemd starts sddm.service
* sddm sees that tty1 is free, and opens it
- systemd really starts getty@tty1.service, and in doing so forcibly 
takes tty1 away from sddm
- sddm tries to use "its" tty1, and hits an error because it no longer 
has it
On success, * is instead reached after getty starts, sees that tty1 
isn't free, and uses tty2 instead.


(systemd maintainers: does this imply that _anything_ that takes the 
first available VT during boot and expects to keep it will have a 
similar problem?  I don't know of any other than sddm, but haven't looked)


Possible solutions (I have *not* tried them yet):
- Patch sddm (at [3]) to assume VT 1 is never free
- or, add a Conflicts=getty@tty1.service (and After= ?) to sddm.service

[0] 
https://sources.debian.org/src/sddm/0.14.0-4+deb9u1/src/daemon/Display.cpp/#L324
[1] 
https://sources.debian.org/src/sddm/0.14.0-4+deb9u1/services/sddm.service.in/

[2] man systemd.service
[3] 
https://sources.debian.org/src/sddm/0.18.0-1/src/daemon/VirtualTerminal.cpp/#L118 
- would need to look at vtState.v_state instead of using VT_OPENQRY


success:

Dec  4 20:55:14 rnpalmer-laptop sddm[843]: Initializing...
Dec  4 20:55:14 rnpalmer-laptop sddm[843]: Starting...
Dec  4 20:55:14 rnpalmer-laptop sddm[843]: Adding new display on vt 7 ...
Dec  4 20:55:14 rnpalmer-laptop sddm[843]: Display server starting...
Dec  4 20:55:14 rnpalmer-laptop sddm[843]: Running: /usr/bin/X -nolisten 
tcp -auth /var/run/sddm/{e8af3b0e-d914-4859-8325-863b144b07f8} 
-background none -noreset -displayfd 18 vt7
Dec  4 20:55:17 rnpalmer-laptop sddm[843]: Running display setup script 
"/usr/share/sddm/scripts/Xsetup"

Dec  4 20:55:17 rnpalmer-laptop sddm[843]: Display server started.
Dec  4 20:55:17 rnpalmer-laptop sddm[843]: Reading from 
"/usr/share/wayland-sessions/plasmawayland.desktop"
Dec  4 20:55:17 rnpalmer-laptop sddm[843]: Reading from 
"/usr/share/wayland-sessions/plasmawayland.desktop"
Dec  4 20:55:17 rnpalmer-laptop sddm[843]: Session 
"/usr/share/wayland-sessions/plasmawayland.desktop" selected, command: 
"dbus-launch --exit-with-session /usr/bin/startplasmacompositor"
Dec  4 20:55:17 rnpalmer-laptop sddm[843]: Adding cookie to 
"/var/run/sddm/{e8af3b0e-d914-4859-8325-863b144b07f8}"

Dec  4 20:55:17 rnpalmer-laptop sddm-helper[863]: [PAM] Starting...
Dec  4 20:55:17 rnpalmer-laptop sddm-helper[863]: [PAM] Authenticating...
Dec  4 20:55:17 rnpalmer-laptop sddm-helper[863]: [PAM] returning.
Dec  4 20:55:17 rnpalmer-laptop sddm[843]: Authenticated successfully
Dec  4 20:55:17 rnpalmer-laptop sddm[843]: Jumping to VT 2
Dec  4 20:55:17 rnpalmer-laptop sddm[843]: VT mode didn't need to be fixed
Dec  4 20:55:17 rnpalmer-laptop sddm-helper[863]: Starting: 
"/usr/share/sddm/scripts/wayland-session dbus-launch --exit-with-session 
/usr/bin/startplasmacompositor"

Dec  4 20:55:17 rnpalmer-laptop sddm[843]: Session started

fail to text prompt:

Dec  4 20:52:09 rnpalmer-laptop sddm[852]: Initializing...
Dec  4 20:52:10 rnpalmer-laptop sddm[852]: Starting...
Dec  4 20:52:10 rnpalmer-laptop sddm[852]: Adding new display on vt 7 ...
Dec  4 20:52:10 rnpalmer-laptop sddm[852]: Display server starting...
Dec  4 20:52:10 rnpalmer-laptop sddm[852]: Running: /usr/bin/X -nolisten 
tcp -auth /var/run/sddm/{55773eae-98a2-43a8-904c-acea6cf1be7e} 
-background none -noreset -displayfd 18 vt7
Dec  4 20:52:12 rnpalmer-laptop sddm[852]: Running display setup script 
"/usr/share/sddm/scripts/Xsetup"

Dec  4 20:52:12 rnpalmer-laptop sddm[852]: Display server started.
Dec  4 20:52:12 rnpalmer-laptop sddm[852]: Reading from 
"/usr/share/wayland-sessions/plasmawayland.desktop"
Dec  

Bug#877638: Apparently this is fixed (partially or fully don't know) by updates to gtk in 3.24

[shirish शिरीष]

Dear all,

See https://github.com/mate-desktop/mate-panel/issues/666

and specifically https://gitlab.gnome.org/GNOME/gtk/merge_requests/451

Apparently, if and when gtk 3.24.3 is released and comes into Debian
it would make things easier.

-- 
  Regards,
  Shirish Agarwal  शिरीष अग्रवाल
  My quotes in this email licensed under CC 3.0
http://creativecommons.org/licenses/by-nc/3.0/
http://flossexperiences.wordpress.com
EB80 462B 08E1 A0DE A73A  2C2F 9F3D C7A4 E1C4 D2D8

Bug#916397: qemu: CVE-2018-16872: usb-mtp: path traversal by host filesystem manipulation in Media Transfer Protocol (MTP)

[Salvatore Bonaccorso]

Source: qemu
Version: 1:3.1+dfsg-1
Severity: important
Tags: security upstream
Forwarded: https://lists.gnu.org/archive/html/qemu-devel/2018-12/msg03135.html


Hi,

The following vulnerability was published for qemu.

CVE-2018-16872[0]:
| A flaw was found in qemu Media Transfer Protocol (MTP). The code
| opening files in usb_mtp_get_object and usb_mtp_get_partial_object and
| directories in usb_mtp_object_readdir doesn't consider that the
| underlying filesystem may have changed since the time lstat(2) was
| called in usb_mtp_object_alloc, a classical TOCTTOU problem. An
| attacker with write access to the host filesystem shared with a guest
| can use this property to navigate the host filesystem in the context
| of the QEMU process and read any file the QEMU process has access to.
| Access to the filesystem may be local or via a network share protocol
| such as CIFS.

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

For further information see:

[0] https://security-tracker.debian.org/tracker/CVE-2018-16872
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-16872
[1] https://lists.gnu.org/archive/html/qemu-devel/2018-12/msg03135.html
[2] https://www.openwall.com/lists/oss-security/2018/12/13/11

Please adjust the affected versions in the BTS as needed.

Regards,
Salvatore

Bug#916284: mrtrix3 seems to be amd64-only

[Yaroslav Halchenko]

On Thu, 13 Dec 2018, Andreas Tille wrote:
> On Thu, Dec 13, 2018 at 12:58:51PM -0500, Yaroslav Halchenko wrote:

> > > I agree with Adrian that on the topic.  I would even have fixed
> > > this in a team upload, but I'm a bit confused by the changelog
> > > I've found in Git[1].  There is only one branch "debian" (I'd
> > > love to have upstream and pristine-tar as well but I'm fine with
> > > fixing this).  However, this branch contains a changelog
> > > entry

> > Please proceed ahead with the next debian revision entry (-3).

> Hmmm, sorry, I think I'll leave this upload to you (see next paragraph).

ok... I will upload a fresh upstream snapshot soon, and then see what
else we could tune and what needs to be fixed up

Cheers,
-- 
Yaroslav O. Halchenko
Center for Open Neuroscience http://centerforopenneuroscience.org
Dartmouth College, 419 Moore Hall, Hinman Box 6207, Hanover, NH 03755
Phone: +1 (603) 646-9834   Fax: +1 (603) 646-1419
WWW:   http://www.linkedin.com/in/yarik

Bug#912201: RFS: manticore/2.7.3 [ITP]

[Adrian Nuta]

>
>
> (Programmer hat) Why build system need to know, which distro it is build
> on?  I guess (did not check sources) you actually interested in
> something more specific, then name of distribution (my
> linux-from-scratch installation does not have name, for example).
>

Yes, name of distribution (although now for current Debians there is one
target 'debian', but e.g. for ubuntu we have special target for trusty to
use upstart instead of systemd).
Added a debian/watch, not sure why mentor lintian doesn't see it, uscan
doesn't report any error, it should get our official tar.gz release for
github.

Fixed the overrides and indentation.

Bug#886335: gstoraster with PJL-encapsulated PostScript

[Alexander Prokoshev]

I second this.

gstoraster (as in cups-filters 1.11.6-3), in fact, fails to detect ANY
type of PJL-incapsulated file I tried: PCL, PS, PDF.

I worked around this by changing CUPS driver for my HP p2055d from
hpcups to hpijs (on my print server).

Bug#905734: found #905734 hplip/3.17.10

[Paul Elliott]

That worked! Although it took some time to figure out how to build using
backports. Evidently, there is some folklore involved.

I was even able to make a version for the raspberry pi!

Thank You.

On Wed, Dec 12, 2018 at 3:24 PM Didier 'OdyX' Raboud 
wrote:

> Dear Paul,
>
> Le vendredi, 7 décembre 2018, 16.15:01 h CET Paul Elliott a écrit :
> > I just downloaded it. It won't build under stretch. All the builds shown
> in
> > the logs are under sid or experimental.
>
> It does under stretch-backports (aka stretch + backports)
>
>
> https://buildd.debian.org/status/package.php?p=hplip=stretch-backports
>
> To build, it needs debhelper and dh-autoreconf from backports indeed.
>
> > Correct me if I am wrong, but if you build under sid, it won't run under
> > stretch, because the libraries linked against won't be the same.
>
> Exactly. Different release suites produce differently linked software.
>
> > I don't think it will help stretch users.
>
> Stretch users don't get updated software, ONLY security fixes.
>
> Stretch users who enabled backports can get an hplip that was built
> against
> stretch libraries that can be installed on stretch hosts.
>
> You seem to want a source hplip from unstable that builds without
> modifications in stable. That's not something I'm interested in providing
> and
> a very unusual requirement for Debian packages.
>
> You also seem to want binary hplip packages that, when built in unstable,
> can
> be installed on stretch hosts. That neither is something I'm interested in
> providing, _also_ an unusual requirement, and that cannot be easily
> guaranteed.
>
> Finally, this bug was about "Unable to backport package hplip on
> stretch".  It
> is not a requirement for unstable packages to build without changes on
> stable.
> So I made minimal changes (thanks to inputs from this bug) to be able to
> build
> hplip in stretch-backports, AND I uploaded this modified package to the
> stretch-backports suite.  It is now accessible in the Debian-standard way
> to
> get backported packages on stable.  There's nothing more I can (or will)
> do.
>
> EOD for me.
>
> Cheers,
> OdyX

Bug#908945: NMU, debdiff

[Hilko Bengen]

Control: tag -1 pending

Dear maintainer,

I have just uploaded libfm/1.3.0.2-1.1, fixing this bug, to DELAYED/5;
the relevant patches are attached to this mail. Feel free to reschedule
or cancel my upload as you see fit.

BTW: You may want to check the debian branch in your Salsa repository,
it contains the changes made to data/libfm.conf by
debian/patches/01-lxde-conf.patch which caused trouble as I tried to
build the package using git-buildpackge.

Cheers,
-Hilko

>From b6195aae8c33dafe6ee6d5d78daea1597dea6c53 Mon Sep 17 00:00:00 2001
From: Hilko Bengen 
Date: Thu, 13 Dec 2018 23:05:31 +0100
Subject: [PATCH 1/2] Add patch that unsets G_DISABLE_ASSERT in test program
 before including glib-related header files (Closes: #907945)

---
 debian/patches/02-fix-test.patch | 20 
 debian/patches/series|  1 +
 2 files changed, 21 insertions(+)
 create mode 100644 debian/patches/02-fix-test.patch

diff --git a/debian/patches/02-fix-test.patch b/debian/patches/02-fix-test.patch
new file mode 100644
index 000..8e71a64
--- /dev/null
+++ b/debian/patches/02-fix-test.patch
@@ -0,0 +1,20 @@
+Index: libfm/src/tests/test-fm-path.c
+===
+--- libfm.orig/src/tests/test-fm-path.c
 libfm/src/tests/test-fm-path.c
+@@ -19,13 +19,13 @@
+  *  MA 02110-1301, USA.
+  */
+ 
+-#include 
+-
+ //ignore for test disabled asserts
+ #ifdef G_DISABLE_ASSERT
+ #undef G_DISABLE_ASSERT
+ #endif
+ 
++#include 
++
+ #define TEST_PARSING(func, str_to_parse, ...) \
+ G_STMT_START { \
+ const char* expected[] = {__VA_ARGS__}; \
diff --git a/debian/patches/series b/debian/patches/series
index 98b24d0..5aef66b 100644
--- a/debian/patches/series
+++ b/debian/patches/series
@@ -1 +1,2 @@
 01-lxde-conf.patch
+02-fix-test.patch
-- 
2.11.0

>From 5a2923617d03497485f9503506576790b402554c Mon Sep 17 00:00:00 2001
From: Hilko Bengen 
Date: Thu, 13 Dec 2018 23:06:18 +0100
Subject: [PATCH 2/2] Debian release 1.3.0.2-1.1

---
 debian/changelog | 8 
 1 file changed, 8 insertions(+)

diff --git a/debian/changelog b/debian/changelog
index 42b9b38..2817c22 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,3 +1,11 @@
+libfm (1.3.0.2-1.1) unstable; urgency=medium
+
+  * Non-maintainer upload
+  * Add patch that unsets G_DISABLE_ASSERT in test program before
+including glib-related header files (Closes: #907945)
+
+ -- Hilko Bengen   Thu, 13 Dec 2018 23:05:41 +0100
+
 libfm (1.3.0.2-1) unstable; urgency=medium
 
   * Updating debian/copyright file.
-- 
2.11.0

Bug#833276: ufw: FTBFS when building from git

[Jamie Strandboge]

On Tue, 02 Aug 2016, Bernhard Schmidt wrote:

> Package: ufw
> Version: 0.35-2
> Severity: wishlist
> 
> Dear Maintainer,
> 
> this is only a wishlist bug because it does not happen with normal building.
> 
> I have just tried to backport a current ufw locally for Jessie. Part of our
> normal process to do this is gbp-import-dsc --download , then make
> a jessie-backports branch with the changelog and run git-buildpackage
> ..., which by default creates a new orig.tar.gz
> 
> This fails horribly with ufw because git, unlike bzr, cannot represent
> empty directories. The code is covered with code like (setup.py)

ufw is now maintained in git[1] and this directory is no longer empty. I didn't
try gbp, so a failure there would indicate a new bug. Thanks again for filing
this issue.

[1]https://git.launchpad.net/ufw/

-- 
Jamie Strandboge | http://www.canonical.com


signature.asc
Description: PGP signature

Bug#907718: python-dateutil breaks python-vobject autopkgtest

[Jonas Smedegaard]

Control: tags -1 help

Quoting Guido Günther (2018-12-13 19:21:45)
> On Thu, Dec 13, 2018 at 05:53:03PM +0100, Jonas Smedegaard wrote:
> > @Guido, could you please have a fresh look at this bug to see if it 
> > can either be lowered or fully solved, now that (I believe) all 
> > blocking bugs are addressed?
>  
> If you have some spare cycles it'd trust your judgement here. I have 
> this on my todo list since some time and it keeps slipping.

I would have acted already if I could: I don't really understand what 
the remaining bug _is_ here (as also indicated by how I earlier closed 
it in error).


 - Jonas

-- 
 * Jonas Smedegaard - idealist & Internet-arkitekt
 * Tlf.: +45 40843136  Website: http://dr.jones.dk/

 [x] quote me freely  [ ] ask before reusing  [ ] keep private


signature.asc
Description: signature

Bug#916396: caldav free-busy query is broken

[Jamie McClymont]

Package: evolution-data-server
Version: 3.30.2-2

A couple of bugs are present which make CalDAV scheduling effectively
useless - the combined effect of them is that everyone else shows as
having your availability information, rather than their own.

I have patched the bugs upstream, and they have been merged into the
branches for both 3.30.4 and 3.31.4:

* https://gitlab.gnome.org/GNOME/evolution-data-server/merge_requests/8
* https://gitlab.gnome.org/GNOME/evolution-data-server/merge_requests/7

I'm hoping these patches could either be backported to the version in
Buster before it's frozen, or buster can update to 3.30.4 when it is
released.


I have also submitted a patch downstream in Ubuntu Bionic, which
backports to the older version of evolution they are packaging:
https://bugs.launchpad.net/ubuntu/+source/evolution-data-server/+bug/1808264


Thanks

Bug#916395: RM: xfswitch-plugin -- ROM; unmaintained upstream

[Yves-Alexis Perez]

Package: ftp.debian.org
Severity: normal

Hi,

another Xfce panel plugin removal request. Again not really maintained
upstream anymore, we do have a suggests from xfce4-goodies but I'm
removing it right now so it should be gone soon.

Regards,
-- 
Yves-Alexis

Bug#916394: RM: xfwm4-themes -- ROM; unmaintained upstream

[Yves-Alexis Perez]

Package: ftp.debian.org
Severity: normal

Hi team,

xfwm4-themes is no longer maintained anymore and we don't really
want/need to keep it in Debian. We still have a Suggests from xfwm4 but
it'll be gone in the next upload in experimental.

Regards,
-- 
Yves-Alexis

Bug#916393: llvm-toolchain-7: fails to work if cache directory not writeable

[Uwe Kleine-König]

Source: llvm-toolchain-7
Severity: normal

Hello,

llvm 7 makes sparse fail to build (even when #912566 is fixed). The
problem is that a test fails with:

could not create jit cache directory /sbuild-nonexistent/.debug/jit/: 
Permission denied
could not initialize debugging directory

This was not a problem with llvm 6.

To reproduce you can build g...@salsa.debian.org:ukleinek/sparse.git in
unstable.

Best regards
Uwe

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

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

Bug#884932: ufw: cannot preseed package configuration in debian-installer

[Jamie Strandboge]

On Thu, 13 Dec 2018, Jamie Strandboge wrote:

> I can confirm this. What is happening is that ufw is trying to interrogate the
> kernel to see if it has some functionality and that fails because the 
> installer
> kernel doesn't have the necessary kernel modules loaded (or available) for 
> this
> test, then the 'allow' command fails early and the rules aren't added. When 
> you
> reboot, this kernel has everything needed, but the rules are missing.
> 
> I'm exploring a fix that will turn this error condition into a warning when 
> ufw
> is not enabled. Preliminary testing shows this fixes the preseeding problem.
> 
This is now fixed in master[1] and will be in ufw 0.36 which will be the next
ufw upload.

[1]https://git.launchpad.net/ufw/commit/?id=af5a419d2d5c1e1afff8348ca516d50ae02784db

-- 
Jamie Strandboge | http://www.canonical.com


signature.asc
Description: PGP signature

Bug#916392: please provide a column marker mechanism

[Arturo Borrero Gonzalez]

Package: nano
Version: 3.2-1
Severity: wishlist
Tags: upstream

I use the nano editor daily :-) Thanks for your work, it's really
appreciated.

A handly option to have while writting code (and other files as well actually)
is to get a column marker.

Let's say you want to do write more than 80 chars per line. Having a visual
column marker, vertical all over the nano window at the 81 position would make
writting way more easier. The marker color should be configurable, providing a
sane default (red?).
This amount of columns should also be configurable, since different
environments may have different requirements (80, 120, etc), like in coding
styles for example.

Thanks!

Bug#915925: libxfce4util: Uses vendor-specific patch series file (ubuntu.series)

[Chris Lamb]

[Adding mat...@debian.org to CC]

Hi Yves-Alexis Perez,

> > Please migrate away from such series files and consider alternatives
> > such differing source packages or modify the build process to behave
> > conditionally or to conditionally patch files explicitly.
[…] 
> is there a documented way to actually do that in a simple/maintainable way

I'm not aware of a documented way that matches this description, alas.

I've had some brief discussions with in Mattia (CC'd) that might be
useful though; he had migrated away from an foo.series in another
package and I had mooted writing a possible "include"-able .mk snippet.

Hope that helps in the meantime.


Regards,

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

Bug#915925: libxfce4util: Uses vendor-specific patch series file (ubuntu.series)

[Yves-Alexis Perez]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

On Fri, 2018-12-07 at 23:16 +0100, Chris Lamb wrote:
> Please migrate away from such series files and consider alternatives
> such differing source packages or modify the build process to behave
> conditionally or to conditionally patch files explicitly.

Hi,

is there a documented way to actually do that in a simple/maintainable way
(and not annoying for Ubuntu maintainers)?

Regards,
- -- 
Yves-Alexis
-BEGIN PGP SIGNATURE-

iQEzBAEBCAAdFiEE8vi34Qgfo83x35gF3rYcyPpXRFsFAlwSz7QACgkQ3rYcyPpX
RFuQyQf/YxXmt7h1+1pslK/6IqUsxOWfsdx3hdlEgXClthYkkNSez+BpOE/tNnc6
AHpE/kg4Re8+bw18ODax9PZw4dX/cPEeStJfq+Qjcnoff4uAQoZa0ZzMJuCzyIdq
wxOqio2Xqtrykit3HqltCyMnFnIUmamzAzAG2Orkv3MozfTgfITpAVgEPuc4CI2A
HfRrV8JIzJfQ5RXZmUVe5FJZr3/HD+Nd4bydHOkfOnMC1t8HmmDOc9KsZS5rvMAV
ye0Y3/MD2d8wo6KY8mA/sNp3aCiTi41GKDC0KRaAHRggBUo/avT2tSLJyAjBbLva
VBIk3tkoeHQfdsWe0QV1g8B683f+LQ==
=zEC/
-END PGP SIGNATURE-

Bug#916390: RFS: tlf/1.3.2-1 [put in ITP, ITA, RC, NMU if applicable]

[Hegedüs Ervin]

Package: sponsorship-requests
Severity: normal

Dear mentors,

I am looking for a sponsor for my package "tlf"

 * Package name: tlf
   Version : 1.3.2-1
   Upstream Author : Thomas Beierlein 
 * URL : https://savannah.nongnu.org/projects/tlf
 * License : GPL
   Section : hamradio

It builds those binary packages:

  tlf   - console based ham radio contest logger

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

https://mentors.debian.net/package/tlf


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

  dget -x https://mentors.debian.net/debian/pool/main/t/tlf/tlf_1.3.2-1.dsc

More information about tlf can be obtained from https://www.example.com.

Changes since the last upload:

  * Team upload.
  * New upstream release
  * Removed spelling-fixes.patch, all modifications had been
merged to upstream

Regards,
 Ervin Hegedüs

Bug#916391: RFP: python3-seesaw -- An asynchronous toolkit for distributed web processing

[Jeff Cliff]

Package: wnpp
Severity: wishlist

* Package name: python3-seesaw
  Version : 0.10.0
  Upstream Author : The Internet Archive
* URL : https://pypi.org/project/seesaw/
* License : WTFPL
  Programming Lang: python
  Description : An asynchronous toolkit for distributed web processing

Written in Python and named after its behavior, it supports concurrent 
downloads, uploads, etc.

This toolkit is well-known for Archive Team projects (http://archiveteam.org). 
It also powers the
Archive Team warrior.

Bug#884932: ufw: cannot preseed package configuration in debian-installer

[Jamie Strandboge]

On Thu, 21 Dec 2017, Moritz Schlarb wrote:

> Package: ufw
> Version: 0.35-4
> Severity: important
> Tags: d-i
> 
> Hi,
> 
> based on the README.Debian
> (https://sources.debian.org/src/ufw/0.35-4/debian/README.Debian/#L23), I tried
> to preseed ufw to be enabled and allowing SSH while also being installed
> directly in d-i.
> 
> Basically this comes down to the following three lines in preseed.cfg:
> 
> d-i pkgsel/include string ufw
> ufw ufw/enable boolean true
> ufw ufw/allow_known_ports multiselect SSH
> 
> But this leads to the following errors in the installer syslog:
> 
> Dec 21 12:47:16 in-target: Setting up ufw (0.35-4) ...^M
> Dec 21 12:47:16 in-target: ^M
> Dec 21 12:47:16 in-target: Creating config file /etc/ufw/before.rules with new
> version^M
> Dec 21 12:47:16 in-target: ^M
> Dec 21 12:47:16 in-target: Creating config file /etc/ufw/before6.rules with 
> new
> version^M
> Dec 21 12:47:16 in-target: ^M
> Dec 21 12:47:16 in-target: Creating config file /etc/ufw/after.rules with new
> version^M
> Dec 21 12:47:16 in-target: ^M
> Dec 21 12:47:16 in-target: Creating config file /etc/ufw/after6.rules with new
> version^M
> Dec 21 12:47:16 kernel: [  674.133042] ip_tables: (C) 2000-2006 Netfilter Core
> Team
> Dec 21 12:47:16 in-target: ERROR: initcaps^M
> Dec 21 12:47:16 in-target: [Errno 2] iptables v1.6.0: can't initialize 
> iptables
> table `filter': Table does not exist (do you need to insmod?)^M
> Dec 21 12:47:16 in-target: Perhaps iptables or your kernel needs to be
> upgraded.^M
> Dec 21 12:47:16 in-target: ^M
> 
> And after rebooting, ufw is enabled, but the allow rules for SSH are missing.

Sorry for the delay!

I can confirm this. What is happening is that ufw is trying to interrogate the
kernel to see if it has some functionality and that fails because the installer
kernel doesn't have the necessary kernel modules loaded (or available) for this
test, then the 'allow' command fails early and the rules aren't added. When you
reboot, this kernel has everything needed, but the rules are missing.

I'm exploring a fix that will turn this error condition into a warning when ufw
is not enabled. Preliminary testing shows this fixes the preseeding problem.

-- 
Jamie Strandboge | http://www.canonical.com


signature.asc
Description: PGP signature

Bug#912682: e: Bug#912682: usefulness of this package?

[Dominic Hargreaves]

On Wed, Dec 12, 2018 at 10:43:17AM +0100, Cyrille Bollu wrote:
> On Tue, 11 Dec 2018 15:13:11 + Dominic Hargreaves  wrote:
> > On Tue, Dec 11, 2018 at 10:06:45AM +0100, Cyrille Bollu wrote:
> > > From its debian/control file:
> > >
> > > >This module is already included as part of Perl's core distribution, so
> > > this
> > > > package is only beneficial when newer features or bug fixes are
> required.
> > >
> > > I don't understand how
> >
> > The perl package provides the same package via a Provides entry:
> > libextutils-parsexs-perl (= 3.39). This is newer than the version
> > in the separate package (against which this bug is filed) so this
> > package will never be selected for installation.
> >
> > This could change if a newer version is uploaded, but until then,
> > the separate package should not be released.
> >
> > Dominic.
> >
> 
> Ok but I don't see how this bug differs from #915550 and #915876 for both
> of which the intent seems to remove the corresponding packages.
> 
> Shouldn't this package also be considered for removal?

Perhaps. We usually leave it a while in case it is upgraded, as the cost
of having around for "a while" in unstable only is judged cheaper than
the extra work needed to remove it and then reintroduce it. I think this
is mostly a matter of personal opinion and we don't have a firm policy
on this, but I'm sure other list members will correct me if I'm wrong.

Dominic.

Bug#575482: Propose to NMU icoutils

[Helge Kreutzmann]

Hello Collin,
I propose to NMU icoutils to solve the long standing translation bug
575482.

You can find my proposed updates at
http://www.helgefjell.de/data/icoutils_0.32.3-2.1.debian.tar.xz
http://www.helgefjell.de/data/icoutils_0.32.3-2.1.dsc

I would prefer if you could add this to your next MU, but if I don't
hear from you I would upload this NMU early January.

If you have any questions do not hesitate to ask.

Greetings

   Helge

-- 
  Dr. Helge Kreutzmann deb...@helgefjell.de
   Dipl.-Phys.   http://www.helgefjell.de/debian.php
64bit GNU powered gpg signed mail preferred
   Help keep free software "libre": http://www.ffii.de/


signature.asc
Description: Digital signature

Bug#916389: cairo CVE-2018-19876

[mcatanzaro]

Package: cairo
Version: 1.16

cairo 1.16.0, in cairo_ft_apply_variations() in cairo-ft-font.c frees
memory using the wrong free function, leading to memory corruption.
Because cairo is used by WebKitGTK+, this issue can be triggered by
web content. CVE-2018-19876 has been allocated by MITRE. For details, 
see:


https://gitlab.freedesktop.org/cairo/cairo/merge_requests/5

Unfortunately, upstream has been unresponsive in that issue, so I've
worked with the Fedora maintainer to include the patch downstream:

https://src.fedoraproject.org/cgit/rpms/cairo.git/plain/0001-ft-Use-FT_Done_MM_Var-instead-of-free-when-available.patch?id=003607a96ce3a5fbb7f9b19298787f332235b2ab

Please add this patch to Debian as well. Note that Stretch is unaffected
because 1.16.0 is the first vulnerable version.

Michael

Bug#916351: transition: dpdk

[Luca Boccassi]

On Thu, 13 Dec 2018 13:26:33 + Luca Boccassi 
wrote:
> Package: release.debian.org
> Severity: normal
> User: release.debian@packages.debian.org
> Usertags: transition
> 
> Dear release team,
> 
> We would like to move the new DPDK LTS release 18.11-1 from
> experimental to unstable. This breaks the various libraries ABI
compat,
> so a transition is needed.
> 
> https://tracker.debian.org/pkg/dpdk
> 
> The new DPDK packages are all in experimental, having passed the NEW
> que
> ue, and have built on all supported architectures.
> 
> Note that from this project follows a boost-like model, so
> the ABI revision is named after the upstream major version (eg:
librte-
> eal17.11 -> librte-eal18.11). This is done because most libraries
built
> from DPDK break ABI compat on every single major release.
> 
> Reverse build dependency source packages:
> 
> collectd:
> 
> The reverse dependency builds needs a source update to build with
this
> new version, to do with autoconf. The fix has been merged upstream
[1]
> and backported to the stable branch currently in sid [2].
> I have opened a bug and attached a patch, which I verified works [3].
> It seems like there's another bug which should be fixed to allow
> migration, but the change is quite simple. I have prepared a source
NMU
> which I could upload if necessary.
> 
> Note that although collectd only recommends the dpdk libraries, it
does
> so because the plugin is optional. The plugin still needs to be
rebuilt
> against the new libraries ABIs to work.
> 
> virtio-forwarder:
> 
> This package has never entered testing as of yet, due to another bug
> (which seems very simple to solve). The issue with DPDK is that
virtio-
> forwarder imports DPDK's makefiles rather than shipping its own, and
> these are deprecated. I reported this downstream [4] and upstream
[5].
> Given it's not in testing I have not yet prepared a patch. I might do
> so in the next few days.
> 
> Thanks!
> 
> -- 
> Kind regards,
> Luca Boccassi
> 
> [1] https://github.com/collectd/collectd/pull/3015
> [2] https://github.com/collectd/collectd/pull/3017
> [3] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=915419
> [4] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=915417
> [5] https://github.com/Netronome/virtio-forwarder/issues/3

I have a tentative fix for virtio-forwarder, sent upstream and debdiff
attached to the relevant bug.

-- 
Kind regards,
Luca Boccassi

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

Bug#915417: virtio-forwarder: fails to build with DPDK 18.11

[Luca Boccassi]

Control: tags -1 patch

On Mon, 03 Dec 2018 17:57:48 + Luca Boccassi 
wrote:
> Source: virtio-forwarder
> Version: 1.1.99.13-1~unstable
> Severity: serious
> Forwarded: https://www.rsyslog.com/doc/master/rainerscript/control_st
ructures.html
> 
> DPDK 18.11 does not ship a dpdk-dev package anymore, and the
dependency
> should be switched to libdpdk-dev.
> But more importantly, the RTE SDK scripts are no longer shipped
either,
> so virtio-forwarder should stop depending on them and either fully
> implement a self-contained makefile or use a different build system.

I have worked on a fix:

https://github.com/Netronome/virtio-forwarder/pull/4

The debdiff is attached.

Given it blocks the DPDK 18.11 transition, I might do an NMU before the
transition freeze happens in January. Let me know if that's an issue.

-- 
Kind regards,
Luca Boccassidiff -Nru virtio-forwarder-1.1.99.13/debian/changelog virtio-forwarder-1.1.99.13/debian/changelog
--- virtio-forwarder-1.1.99.13/debian/changelog	2018-06-11 13:02:44.0 +0100
+++ virtio-forwarder-1.1.99.13/debian/changelog	2018-12-13 20:34:59.0 +
@@ -1,3 +1,17 @@
+virtio-forwarder (1.1.99.13-1~unstable+0.1) UNRELEASED; urgency=medium
+
+  * Non-maintainer upload.
+  * Add dpdk_1811.patch to fix build with DPDK 18.11.
+(Closes: #915417)
+  * Add meson.patch to add independent build system, to fix build
+with DPDK 18.11 which does not ship importable makefiles anymore.
+Update the build-dependencies accordingly: added meson,
+systemd (for pc file), removed dpdk-dev.
+  * Build-Depend on libprotobuf-c-dev instead of the deprecated
+libprotobuf-c0-dev. (Closes: #906293)
+
+ -- Luca Boccassi   Thu, 13 Dec 2018 20:34:59 +
+
 virtio-forwarder (1.1.99.13-1~unstable) unstable; urgency=low
   *  Initial release (Closes: #901027)
  -- Frik Botha   Mon, 11 Jun 2018 14:02:44 +0200
diff -Nru virtio-forwarder-1.1.99.13/debian/compat virtio-forwarder-1.1.99.13/debian/compat
--- virtio-forwarder-1.1.99.13/debian/compat	2018-06-11 13:02:44.0 +0100
+++ virtio-forwarder-1.1.99.13/debian/compat	2018-12-13 19:52:58.0 +
@@ -1 +1 @@
-9
+11
diff -Nru virtio-forwarder-1.1.99.13/debian/control virtio-forwarder-1.1.99.13/debian/control
--- virtio-forwarder-1.1.99.13/debian/control	2018-06-11 13:02:44.0 +0100
+++ virtio-forwarder-1.1.99.13/debian/control	2018-12-13 19:52:58.0 +
@@ -1,7 +1,7 @@
 Source: virtio-forwarder
 Maintainer: Frik Botha 
 Section: net
-Build-Depends: debhelper (>= 9), python-minimal, protobuf-c-compiler, libprotobuf-c0-dev, libzmq3-dev, protobuf-compiler, python3-sphinx, libnuma-dev, libdpdk-dev, dpdk-dev, libpcap-dev, libxen-dev
+Build-Depends: debhelper (>= 11~), python-minimal, protobuf-c-compiler, libprotobuf-c-dev, libzmq3-dev, protobuf-compiler, python3-sphinx, libnuma-dev, libdpdk-dev, libpcap-dev, libxen-dev, meson, systemd
 Standards-Version: 4.1.4
 Homepage: https://github.com/Netronome/virtio-forwarder
 Priority: optional
diff -Nru virtio-forwarder-1.1.99.13/debian/patches/dpdk_1811.patch virtio-forwarder-1.1.99.13/debian/patches/dpdk_1811.patch
--- virtio-forwarder-1.1.99.13/debian/patches/dpdk_1811.patch	1970-01-01 01:00:00.0 +0100
+++ virtio-forwarder-1.1.99.13/debian/patches/dpdk_1811.patch	2018-12-13 20:34:59.0 +
@@ -0,0 +1,96 @@
+From 8368876ffc66e16a505095484017f65a76580f9a Mon Sep 17 00:00:00 2001
+From: Luca Boccassi 
+Date: Thu, 13 Dec 2018 20:30:02 +
+Subject: [PATCH] Fix build with DPDK 18.11
+
+A few APIs and struct members for offloading have been removed, so
+use the appropriate ifdefs to fix the build with 18.11.
+---
+ virtio_worker.c | 35 +--
+ 1 file changed, 33 insertions(+), 2 deletions(-)
+
+--- a/virtio_worker.c
 b/virtio_worker.c
+@@ -358,7 +358,9 @@
+ DEV_TX_OFFLOAD_TCP_TSO;
+ 	tx_conf->offloads = dev_info->tx_offload_capa & desired_offloads;
+ #endif
++#if RTE_VERSION < RTE_VERSION_NUM(18,8,0,0)
+ 	tx_conf->txq_flags &= ~ETH_TXQ_FLAGS_NOOFFLOADS;
++#endif
+ }
+ 
+ static void get_rx_conf(const struct rte_eth_dev_info *dev_info,
+@@ -374,9 +376,17 @@
+ 
+ 	rte_eth_dev_stop(port_id);
+ 	rte_eth_dev_close(port_id);
++#if RTE_VERSION >= RTE_VERSION_NUM(18,11,0,0)
++	const char rte_detach_api[] = "rte_dev_remove";
++	struct rte_eth_dev_info dev_info;
++	rte_eth_dev_info_get(port_id, _info);
++	err = rte_dev_remove(dev_info.device);
++#else
++	const char rte_detach_api[] = "rte_eth_dev_detach";
+ 	err = rte_eth_dev_detach(port_id, detach_dbdf);
++#endif
+ 	if (err != 0) {
+-		log_warning("rte_eth_dev_detach(%hhu) failed with error %i",
++		log_warning("%s(%hhu) failed with error %i", rte_detach_api,
+ 			port_id, err);
+ 	}
+ 
+@@ -505,7 +515,13 @@
+ 	log_info("Adding DPDK port %hhu ('%s') to virtio ('%u')",
+ 		port_id, name, virtio_id);
+ 
++#if RTE_VERSION >= RTE_VERSION_NUM(18,8,0,0)
++	rte_eth_dev_info_get(port_id, _info);
++	if (dev_info.rx_offload_capa & DEV_RX_OFFLOAD_JUMBO_FRAME)
++		

Bug#916284: mrtrix3 seems to be amd64-only

[Andreas Tille]

Hi Yaroslav,

On Thu, Dec 13, 2018 at 12:58:51PM -0500, Yaroslav Halchenko wrote:
> 
> > I agree with Adrian that on the topic.  I would even have fixed
> > this in a team upload, but I'm a bit confused by the changelog
> > I've found in Git[1].  There is only one branch "debian" (I'd
> > love to have upstream and pristine-tar as well but I'm fine with
> > fixing this).  However, this branch contains a changelog
> > entry
> 
> Please proceed ahead with the next debian revision entry (-3).

Hmmm, sorry, I think I'll leave this upload to you (see next paragraph).

> BUT I am
> not yet sure if restricting to amd64 is the way to go, since it (used
> to at least) build at least for i386 on buster and ubuntus

I have way to less experience with this and if you think the proposed
solution is not correct I think you should find the correct fix.  Since
the fix I could do would simply changing the architecture field is so
easy that I can not really save your time by doing a team upload. ;-)

> or see more at http://neuro.debian.net/pkgs/mrtrix3.html
> 
> and -1 (which happened before) even built at that time on sid:
> 
> neurodebian@smaug ..lds/mrtrix3/3.0~rc3+git86-g4b523b413-1 % grep i386.*OK 
> summary.build  
> mrtrix3_3.0~rc3+git86-g4b523b413-1~nd90+1_i386.build  OK  16:53.22 real, 
> 6529.21 user, 280.91 sys, 27009632 out
> mrtrix3_3.0~rc3+git86-g4b523b413-1~nd100+1_i386.build OK  19:59.56 real, 
> 7835.78 user, 333.59 sys, 38376784 out
> mrtrix3_3.0~rc3+git86-g4b523b413-1~nd+1_i386.buildOK  20:22.06 real, 
> 7732.59 user, 344.35 sys, 38403288 out
> mrtrix3_3.0~rc3+git86-g4b523b413-1~nd17.10+1_i386.build   OK  
> 16:32.40 real, 6863.87 user, 284.41 sys, 27336024 out
> mrtrix3_3.0~rc3+git86-g4b523b413-1~nd18.04+1_i386.build   OK  
> 15:22.20 real, 6721.61 user, 283.47 sys, 27575376 out
> 
> and relevant issue upstream worth following up on/checking how/what to
> be fixed up: https://github.com/MRtrix3/mrtrix3/issues/1453 -- may be
> testing recent snapshot of their repo would have addressed them...
> didn't look -- and would appreciate help
> 
> as for other non x32 platforms -- I've not analyzed the situation yet...  it
> might still be the matter of fixing it up since upstream just didn't have a
> chance to get exposed to other platforms. I do not see any explicit note about
> SSE requirement.  So let's ask:
> 
> https://github.com/MRtrix3/mrtrix3/issues/1514

I think its better if I keep my hands out of it.  This morning it felt
like a low hanging fruit and I could help a bit but the issue seems more
complex.

> re pristine-tar.  I guess i didn't push it due to  using/packaging (see
> debian/gbp.conf) also submodules:
> 
>   $> git submodule
>6e6196af03e27948154f1f11285aa11d35af4a36 testing/data (heads/master)
> 
> for testing.  But here you go -- I pushed the monster pristine-tar now.  I 
> hope
> it is a correct one ;)

I can confirm it is correct.
 
> I also pushed the commit adjusting debian/gbp.conf to match the layout of this
> repo (debian/ branch for packaging, master for upstream).

Thanks.
 
> > mrtrix3 (3.0~rc3+git86-g4b523b413-2) neurodebian; urgency=medium
> 
> >   * Need to disable PIE on older systems
> 
> >  -- Yaroslav Halchenko   Wed, 21 Nov 2018 23:08:01 
> > -0500
> 
> 
> > which does not belong here (neurodebian is no release of Debian, right
> > ;-) ). I'd suggest the cleaner solution to move changes into a branch
> > neurodebian.  Moreover the releases in this branch should not simply
> 
> am I violating policy or causing lintian screaming?

No.  You are simply violating the principle of least surprise for other
members of the team.  Its very well established practice to use the
suffix I suggested below and if you want to profit from the help of
others its simply a good idea to stick to these practices.  You know
that I fiddled around with some packages maintained by NeuroDebian team
and in close to all packages I realise specific things which do not fit
the workflow that is pretty established in the Debian Med team.  You are
free to derive from this but if I get the feeling that these packages
create more work than other packages in the team I'm less motivated to
help.

> if not  -- I'd suggest to
> keep it as is to avoid avoidable extra work for me -- if you upload -3, please
> use 'unstable' as the release label and then whoever looks at the
> debian/changelog would know that -2 was NOT uploaded to unstable/Debian

Sure if I *would* upload I would have used unstable (what else?) but I
try to raise your awareness that "holes in the release number history"
might cause questions.  I'd recommend to avoid this in favour of what
many others are doing in comparable situations.

> (I also
> keep UNRELEASED some times whenever some -debrev was not uploaded but used
> locally or just reflects the state of packaging which ever existed at that
> point -- helps to visualize the changes in the package/project timeline)

Right, I would expect 

Bug#916231: osspd FTBFS on mips: osspd.c:769:15: error: 'IOC_IN' undeclared

[Ralf Jung]

Hi again,

> I found https://patchwork.ozlabs.org/patch/740563/ via some googling.  It
> mentions MIPS, so it might be related?

As a random guess, could you try adding

#include 

at the top of "ossp.h" and see if that makes a difference?

It seems that this now somehow triggers the logic in bits/socket.h that thinks
that we don't want these macros, but we do want them...
(What a great reminder for why I stopped using C.^^)

Kind regards,
Ralf

Bug#916231: osspd FTBFS on mips: osspd.c:769:15: error: 'IOC_IN' undeclared

[Ralf Jung]

Hi,

> While trying to cross build osspd for mips, I ran into a failure that I
> could reproduce natively on minkus.d.o, but not on amd64. I suspect this
> is related to glibc/2.28. A build ends with:
> 
> | gcc -Wall -pthread -g -O2 -fdebug-prefix-map=/home/helmutg/osspd-1.3.2=. 
> -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time 
> -D_FORTIFY_SOURCE=2 -D_FILE_OFFSET_BITS=64 -I/usr/include/fuse 
> -DSLAVE_DEFAULT_PATH=\"/usr/lib/osspd\" -o osspd osspd.c -lfuse -pthread -L. 
> -lossp -pthread -Wl,-z,relro
> | osspd.c:41:2: warning: #warning mmap support disabled for now [-Wcpp]
> |  #warning mmap support disabled for now
> |   ^~~
> | In file included from /usr/include/mips-linux-gnu/sys/soundcard.h:1,
> |  from osspd.c:29:
> | osspd.c: In function 'mixer_do_ioctl':
> | osspd.c:769:15: error: 'IOC_IN' undeclared (first use in this function); 
> did you mean 'SIOC_IN'?
> |   if (!(cmd & (SIOC_IN | SIOC_OUT)))
> |^~~
> | osspd.c:769:15: note: each undeclared identifier is reported only once for 
> each function it appears in
> | osspd.c:769:25: error: 'IOC_OUT' undeclared (first use in this function); 
> did you mean 'SIOC_OUT'?
> |   if (!(cmd & (SIOC_IN | SIOC_OUT)))
> |  ^~~~
> | osspd.c: In function 'notify_poller':
> | osspd.c:1842:1: warning: no return statement in function returning non-void 
> [-Wreturn-type]
> |  }
> |  ^
> | osspd.c: In function 'ossp_daemonize':
> | osspd.c:1923:3: warning: ignoring return value of 'chdir', declared with 
> attribute warn_unused_result [-Wunused-result]
> |chdir("/");
> |^~
> | At top level:
> | osspd.c:1978:39: warning: 'adsp_ops' defined but not used 
> [-Wunused-const-variable=]
> |  static const struct cuse_lowlevel_ops adsp_ops = {
> |^~~~
> | make[2]: *** [Makefile:56: osspd] Error 1
> | make[2]: Leaving directory '/home/helmutg/osspd-1.3.2'
> | dh_auto_build: make V=1 -j1 SLAVESDIR=/usr/lib/osspd 
> UDEVDIR=/lib/udev/rules.d returned exit code 2
> | make[1]: *** [debian/rules:10: override_dh_auto_build] Error 2
> | make[1]: Leaving directory '/home/helmutg/osspd-1.3.2'
> | make: *** [debian/rules:7: build] Error 2
> | dpkg-buildpackage: error: debian/rules build subprocess returned exit 
> status 2

Thanks for the report!

The error looks somewhat odd; the code says "SIOC_IN" and the error suggests to
use SIOC_IN?

Unfortunately, upstream is dead and I have no experience porting or
cross-compiling C code.  Any suggestions for how one could fix this?

I found https://patchwork.ozlabs.org/patch/740563/ via some googling.  It
mentions MIPS, so it might be related?

Kind regards,
Ralf

Bug#916388: gcc-8: crash with command line switch -fsanitize=float-cast-overflow (upstream bug 88426)

[Andrei Karas]

Source: gcc-8
Version: 8.2.0-12
Severity: normal
Tags: upstream

GCC crashing if try to compile this code:
void func(void)
{
const float var = 0;
(int)(var < 0 ? var : 0);
}

with command:
gcc -S -fsanitize=float-cast-overflow crash.c

Bug already fixed in upstream trunk
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88426

Bug#916387: bygfoot FTCBFS: configures for the wrong architecture

[Helmut Grohne]

Source: bygfoot
Version: 2.3.2-2
Tags: patch
User: helm...@debian.org
Usertags: rebootstrap

bygfoot 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 bygfoot cross buildable. Please consider
applying the attached patch.

Helmut
diff --minimal -Nru bygfoot-2.3.2/debian/changelog 
bygfoot-2.3.2/debian/changelog
--- bygfoot-2.3.2/debian/changelog  2014-04-06 01:20:07.0 +0200
+++ bygfoot-2.3.2/debian/changelog  2018-12-13 21:13:17.0 +0100
@@ -1,3 +1,10 @@
+bygfoot (2.3.2-2.1) UNRELEASED; urgency=medium
+
+  * Non-maintainer upload.
+  * Fix FTCBFS: Let dh_auto_configure pass --host to ./configure. (Closes: #-1)
+
+ -- Helmut Grohne   Thu, 13 Dec 2018 21:13:17 +0100
+
 bygfoot (2.3.2-2) unstable; urgency=low
 
   * Bump Standards-Version to 3.9.5
diff --minimal -Nru bygfoot-2.3.2/debian/rules bygfoot-2.3.2/debian/rules
--- bygfoot-2.3.2/debian/rules  2014-04-06 01:01:11.0 +0200
+++ bygfoot-2.3.2/debian/rules  2018-12-13 21:13:15.0 +0100
@@ -4,7 +4,7 @@
dh $@
 
 override_dh_auto_configure:
-   ./configure --bindir=/usr/games --datadir=/usr/share/games 
--with-localedir=/usr/share/locale
+   dh_auto_configure -- --bindir=/usr/games --datadir=/usr/share/games 
--with-localedir=/usr/share/locale
 
 override_dh_clean:
dh_clean

Bug#916386: Success installing Debian buster/testing using 12/3/2018 amd64.iso

[David George Henderson III]

Package: installation-reports

Boot method:  flash 
drive
Image version:  
debian-testing-amd64-DVD-1.iso dated 12/3/2018

Date:  12/13/2018

Machine: Macintosh Macbook Pro 
model 5,1
Processor: Core 2 Duo
Memory:4gb
Partitions: 
Installed to separate /boot and encrypted LVM with swap and root.

Output of lspci -knn (or lspci -nn):

Base System Installation Checklist:
[O] = OK, [E] = Error (please elaborate below), [ ] = didn't try it

Initial boot:   [O]
Detect network card:[O]
Configure network:  [O]
Detect CD:  [O]
Load installer modules: [O]
Detect hard drives: [O]
Partition hard drives:  [O]
Install base system:[O]
Clock/timezone setup:   [O]
User/password setup:[O]
Install tasks:  [O]
Install boot loader:[O]
Overall install:[O]


Comments/Problems:


Used dd to copy installer from *.iso to a flash drive.
Installed from flash drive and hardwired ethernet.
Only anomaly was going to sid for  broadcom b43 wifi firmware post-install.
Not sure if this a bug or simply incomplete definition of buster.

Bug#916385: pd-lyonpotpourri FTCBFS: strips with the wrong strip

[Helmut Grohne]

Source: pd-lyonpotpourri
Version: 2.0+git20121009-2
Tags: patch
User: helm...@debian.org
Usertags: rebootstrap

pd-lyonpotpourri fails to cross build from source, because it strips
with the build architecture strip during make install. This not only
breaks cross compilation, but also breaks generation of a -dbgsym
package as well as DEB_BUILD_OPTIONS=nostrip. Not stripping fixes all
of that. Please consider applying the attached patch.

Helmut
diff --minimal -Nru pd-lyonpotpourri-2.0+git20121009/debian/changelog 
pd-lyonpotpourri-2.0+git20121009/debian/changelog
--- pd-lyonpotpourri-2.0+git20121009/debian/changelog   2018-02-01 
23:20:12.0 +0100
+++ pd-lyonpotpourri-2.0+git20121009/debian/changelog   2018-12-13 
21:08:33.0 +0100
@@ -1,3 +1,10 @@
+pd-lyonpotpourri (2.0+git20121009-2.1) UNRELEASED; urgency=medium
+
+  * Non-maintainer upload.
+  * Defer all stripping to dh_strip. (Closes: #-1)
+
+ -- Helmut Grohne   Thu, 13 Dec 2018 21:08:33 +0100
+
 pd-lyonpotpourri (2.0+git20121009-2) unstable; urgency=medium
 
   * Added patch to fix spelling errors
diff --minimal -Nru pd-lyonpotpourri-2.0+git20121009/debian/rules 
pd-lyonpotpourri-2.0+git20121009/debian/rules
--- pd-lyonpotpourri-2.0+git20121009/debian/rules   2018-02-01 
23:20:12.0 +0100
+++ pd-lyonpotpourri-2.0+git20121009/debian/rules   2018-12-13 
21:08:33.0 +0100
@@ -21,7 +21,7 @@
$(empty)
 
 override_dh_auto_install:
-   dh_auto_install -- prefix=/usr pkglibdir=$(pkglibdir)
+   dh_auto_install -- prefix=/usr pkglibdir=$(pkglibdir) STRIP=:
 # fix permissions
find $(CURDIR)/debian/*/$(pkglibdir) -name "*.pd_linux" -exec \
chmod 0664 {} +

Bug#916384: apt-listbugs: Updated Danish translation for version 1.26

[Morten Bo Johansen]

Package: apt-listbugs
Version: 0.1.25
Severity: wishlist
Tags: l10n patch

Dear Maintainer,

Please find attached an updated Danish translation.

  Morten Bo Johansen

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

Kernel: Linux 4.18.0-3-amd64 (SMP w/8 CPU cores)
Locale: LANG=da_DK.utf-8, LC_CTYPE=da_DK.utf-8 (charmap=UTF-8) (ignored: LC_ALL 
set to da_DK.utf-8), LANGUAGE=da_DK.utf-8 (charmap=UTF-8) (ignored: LC_ALL set 
to da_DK.utf-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages apt-listbugs depends on:
ii  apt 1.8.0~alpha2
ii  ruby1:2.5.1
ii  ruby-debian 0.3.9+b8
ii  ruby-gettext3.2.9-1
ii  ruby-soap4r 2.0.5-4
ii  ruby-unicode0.4.4-2+b9
ii  ruby-xmlparser  0.7.3-3+b2
ii  ruby2.1 [ruby-interpreter]  2.1.5-4
ii  ruby2.2 [ruby-interpreter]  2.2.4-1

Versions of packages apt-listbugs recommends:
ii  ruby-httpclient  2.8.3-1

Versions of packages apt-listbugs suggests:
ii  chromium [www-browser] 71.0.3578.80-1
ii  elinks [www-browser]   0.12~pre6-13+b1
ii  firefox [www-browser]  63.0.3-1
ii  firefox-esr [www-browser]  60.3.0esr-3
ii  lynx [www-browser] 2.8.9rel.1-2
ii  reportbug  7.5.1
ii  sensible-utils 0.0.12
ii  w3m [www-browser]  0.5.3-36+b1

-- no debconf information


da.po.gz
Description: application/gzip

Bug#916382: RM: diamond-aligner [arm64 armel armhf hurd-i386 i386 kfreebsd-amd64 kfreebsd-i386 mips mips64el mipsel ppc64el s390x] -- NBS; package is now amd64-only

[Adrian Bunk]

Package: ftp.debian.org
Severity: normal

 diamond-aligner (0.9.23+dfsg-2) unstable; urgency=medium
 .
   * Restrict architecture to amd64
 Closes: #916370

Bug#916383: libmatchbox FTCBFS: builds for the wrong architecture

[Helmut Grohne]

Source: libmatchbox
Version: 1.9-osso8-5
Tags: patch
User: helm...@debian.org
Usertags: rebootstrap

libmatchbox 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 libmatchbox cross buildable. Please consider
applying the attached patch.

Helmut
diff --minimal -Nru libmatchbox-1.9-osso8/debian/changelog 
libmatchbox-1.9-osso8/debian/changelog
--- libmatchbox-1.9-osso8/debian/changelog  2018-10-24 19:28:52.0 
+0200
+++ libmatchbox-1.9-osso8/debian/changelog  2018-12-13 21:03:40.0 
+0100
@@ -1,3 +1,10 @@
+libmatchbox (1.9-osso8-5.1) UNRELEASED; urgency=medium
+
+  * Non-maintainer upload.
+  * Fix FTCBFS: Let dh_auto_configure pass --host to ./configure. (Closes: #-1)
+
+ -- Helmut Grohne   Thu, 13 Dec 2018 21:03:40 +0100
+
 libmatchbox (1.9-osso8-5) unstable; urgency=medium
 
   * Update standards version.
diff --minimal -Nru libmatchbox-1.9-osso8/debian/rules 
libmatchbox-1.9-osso8/debian/rules
--- libmatchbox-1.9-osso8/debian/rules  2018-10-24 19:28:52.0 +0200
+++ libmatchbox-1.9-osso8/debian/rules  2018-12-13 21:03:36.0 +0100
@@ -1,7 +1,5 @@
 #!/usr/bin/make -f
 
-DEB_HOST_MULTIARCH  ?= $(shell dpkg-architecture -qDEB_HOST_MULTIARCH)
-
 export DEB_LDFLAGS_MAINT_APPEND = -Wl,--as-needed
 
 %:
@@ -23,4 +21,4 @@
dh_clean
 
 override_dh_auto_configure:
-   ./configure --prefix=/usr 
--libdir=\$${prefix}/lib/$(DEB_HOST_MULTIARCH) --enable-pango --enable-jpeg 
--enable-png --enable-doxygen-docs
+   dh_auto_configure -- --enable-pango --enable-jpeg --enable-png 
--enable-doxygen-docs

Bug#916381: installation-reports: Sucessful install and boot of Buster on Macboot Pro 5,1

[David George Henderson III]

Package: installation-reports
Severity: normal

Dear Maintainer,

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

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

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



-- Package-specific info:

Boot method: flash drive
Image version: Buster amd64 dvd-1 iso of December 3,2018
Date: 

Machine: Macbook Pro model 5,1
Partitions: 


Base System Installation Checklist:
[O] = OK, [E] = Error (please elaborate below), [ ] = didn't try it

Initial boot:   [ ]
Detect network card:[ ]
Configure network:  [ ]
Detect CD:  [ ]
Load installer modules: [ ]
Clock/timezone setup:   [ ]
User/password setup:[ ]
Detect hard drives: [ ]
Partition hard drives:  [ ]
Install base system:[ ]
Install tasks:  [ ]
Install boot loader:[ ]
Overall install:[ ]

Comments/Problems:




-- 

Please make sure that the hardware-summary log file, and any other
installation logs that you think would be useful are attached to this
report. Please compress large files using gzip.

Once you have filled out this report, mail it to sub...@bugs.debian.org.

==
Installer lsb-release:
==
DISTRIB_ID=Debian
DISTRIB_DESCRIPTION="Debian GNU/Linux installer"
DISTRIB_RELEASE="9 (stretch) - installer build 20170615+deb9u4"
X_INSTALLATION_MEDIUM=cdrom

==
Installer hardware-summary:
==
uname -a: Linux hp470prod 4.9.0-7-amd64 #1 SMP Debian 4.9.110-1 (2018-07-05) 
x86_64 GNU/Linux
lspci -knn: 00:00.0 Host bridge [0600]: Intel Corporation Device [8086:5904] 
(rev 02)
lspci -knn: Subsystem: Hewlett-Packard Company Device [103c:8234]
lspci -knn: 00:02.0 VGA compatible controller [0300]: Intel Corporation Device 
[8086:5916] (rev 02)
lspci -knn: Subsystem: Hewlett-Packard Company Device [103c:8234]
lspci -knn: 00:14.0 USB controller [0c03]: Intel Corporation Sunrise Point-LP 
USB 3.0 xHCI Controller [8086:9d2f] (rev 21)
lspci -knn: Subsystem: Hewlett-Packard Company Device [103c:8234]
lspci -knn: Kernel driver in use: xhci_hcd
lspci -knn: Kernel modules: xhci_pci
lspci -knn: 00:14.2 Signal processing controller [1180]: Intel Corporation 
Sunrise Point-LP Thermal subsystem [8086:9d31] (rev 21)
lspci -knn: Subsystem: Hewlett-Packard Company Device [103c:8234]
lspci -knn: 00:16.0 Communication controller [0780]: Intel Corporation Sunrise 
Point-LP CSME HECI #1 [8086:9d3a] (rev 21)
lspci -knn: Subsystem: Hewlett-Packard Company Device [103c:8234]
lspci -knn: 00:17.0 SATA controller [0106]: Intel Corporation Sunrise Point-LP 
SATA Controller [AHCI mode] [8086:9d03] (rev 21)
lspci -knn: Subsystem: Hewlett-Packard Company Device [103c:8234]
lspci -knn: Kernel driver in use: ahci
lspci -knn: Kernel modules: ahci
lspci -knn: 00:1c.0 PCI bridge [0604]: Intel Corporation Device [8086:9d10] 
(rev f1)
lspci -knn: Kernel driver in use: pcieport
lspci -knn: 00:1c.4 PCI bridge [0604]: Intel Corporation Sunrise Point-LP PCI 
Express Root Port #5 [8086:9d14] (rev f1)
lspci -knn: Kernel driver in use: pcieport
lspci -knn: 00:1c.5 PCI bridge [0604]: Intel Corporation Sunrise Point-LP PCI 
Express Root Port #6 [8086:9d15] (rev f1)
lspci -knn: Kernel driver in use: pcieport
lspci -knn: 00:1d.0 PCI bridge [0604]: Intel Corporation Sunrise Point-LP PCI 
Express Root Port #9 [8086:9d18] (rev f1)
lspci -knn: Kernel driver in use: pcieport
lspci -knn: 00:1f.0 ISA bridge [0601]: Intel Corporation Device [8086:9d4e] 
(rev 21)
lspci -knn: Subsystem: Hewlett-Packard Company Device [103c:8234]
lspci -knn: 00:1f.2 Memory controller [0580]: Intel Corporation Sunrise 
Point-LP PMC [8086:9d21] (rev 21)
lspci -knn: Subsystem: Hewlett-Packard Company Device [103c:8234]
lspci -knn: 00:1f.3 Audio device [0403]: Intel Corporation Device [8086:9d71] 
(rev 21)
lspci -knn: Subsystem: Hewlett-Packard Company Device [103c:8234]
lspci -knn: 00:1f.4 SMBus [0c05]: Intel Corporation Sunrise Point-LP SMBus 
[8086:9d23] (rev 21)
lspci -knn: Subsystem: Hewlett-Packard Company Device [103c:8234]
lspci -knn: 01:00.0 3D controller [0302]: NVIDIA Corporation GM108M [GeForce 
930MX] [10de:134e] (rev a2)
lspci -knn: Subsystem: Hewlett-Packard Company Device [103c:8235]
lspci -knn: 02:00.0 Ethernet controller [0200]: Realtek Semiconductor Co., Ltd. 
RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller [10ec:8168] (rev 15)
lspci -knn: Subsystem: Hewlett-Packard Company Device [103c:8234]
lspci -knn: Kernel driver in use: r8169
lspci -knn: Kernel modules: r8169
lspci -knn: 03:00.0 Network controller [0280]: Intel Corporation Device 
[8086:24fd] (rev 78)
lspci -knn:  

Bug#867140: cqrlog: Please migrate to openssl1.1 in Buster

[Moritz Mühlenhoff]

On Wed, Sep 05, 2018 at 07:18:08PM +0200, Petr Hlozek wrote:
> Recent version (2.3.0) of CQRLOG already supports openssl1.1. New
> version will be released soon.

What's the status? Could 2.3.0 be uploaded to unstable?

Cheers,
Moritz

Bug#877633: test patch unstable

[marc marc]

I have tested the patch 
https://salsa.debian.org/sk-guest/monit/commit/ac71b49a08b7f6aa23c185183ab87a64cae4e913
error: Depend service 'sshd_dsa_key' is not defined in the control file

for the stable version, no template is indeed enable by default
but If you install a monitoring with a template that kill a working 
service, imho the bug can hardly be more important for a system such as 
monit.
at least in stable, a small fix like this is needed :
12c12,13
# https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=877633
 >#depend on sshd_dsa_key
that enought to avoid killing a working sshd.
of course dropping the whole section related to sshd_dsa_key
is also a solution :)

Bug#916306: gitlab: Error during gitlab installation

[Pranith Kumar]

OK. I manually copied gitlab-debian.conf from /var/lib/gitlab/ to
/etc/gitlab/ and it was overwritten during the configure step with the
package maintainers version. It now proceeds past the previous error
message.

Now, I am seeing a new error as follows:

$ sudo dpkg --configure gitlab
Setting up gitlab (11.3.11+dfsg-1) ...
Creating runtime directories for gitlab...
Updating file permissions...
Configuring hostname and email...
Registering /usr/lib/tmpfiles.d/gitlab.conf via ucf
/etc/systemd/system/gitlab-mailroom.service.d/override.conf already exist
/etc/systemd/system/gitlab-unicorn.service.d/override.conf already exist
/etc/systemd/system/gitlab-sidekiq.service.d/override.conf already exist
/etc/systemd/system/gitlab-workhorse.service.d/override.conf already exist
Registering /etc/gitlab-shell/config.yml via ucf
Registering /etc/gitlab/gitlab.yml via ucf
Registering /etc/gitlab/gitlab-debian.conf via ucf
Reloading nginx configuration...
nginx.service is not active, cannot reload.
invoke-rc.d: initscript nginx, action "reload" failed.
dpkg: error processing package gitlab (--configure):
 installed gitlab package post-installation script subprocess returned
error exit status 1
Errors were encountered while processing:
 gitlab

Thanks,

On Thu, Dec 13, 2018 at 11:38 AM Pirate Praveen
 wrote:
>
> On 12/14/18 12:58 AM, Pranith Kumar wrote:
> > Hmm, I don't understand what you mean by "feel of the installation".
>
> Just so you see the prompt, but you saw it already, so ignore that part.
>
> > The fqdn prompt did show up the first time, but due to other errors
> > the installation did not finish then.
>
> yes.
>
> > Now that the other problems are resolved, I need a way to reset the
> > fqdn setting. Ideally, a purge should remove the configuration file
> > that holds this setting. Do you know which config file has this? It is
> > not /etc/gitlab/gitlab-debian.conf since that file does not exist yet.
> >
> > I think the purge is not deleting everything it should.
>
> purge only tries to delete things it can and ignores any failures. In
> local systems I tried, purge always brings back those questions.
>
> This is the regular debconf questions if you want to dig deeper. Or try
> to modify the postinst script to strip 'https://' in that host
> configuration step.
>
> https://salsa.debian.org/ruby-team/gitlab/blob/master/debian/gitlab.postinst#L133
>
> Once you modify, build the new deb and try installing that.
>


-- 
Pranith

Bug#851085: conserver: FTBFS with openssl 1.1.0

[Moritz Mühlenhoff]

On Tue, Jun 05, 2018 at 11:12:34PM +0200, Moritz Muehlenhoff wrote:
> On Sun, Jun 26, 2016 at 12:21:20PM +0200, Kurt Roeckx wrote:
> > OpenSSL 1.1.0 is about to released.  During a rebuild of all packages using
> > OpenSSL this package fail to build. 
> 
> This has now been fixed in version 8.2.2:
> https://github.com/conserver/conserver/commit/258c2e124135257dcc6128b629b4ad157841c81c

Hi Jörgen,
there's now only a handful of packages blocking the removal of openssl 1.0,
are you still interested in maintaining conserver or shall we remove it from
the archive?
 
Cheers,
Moritz

Bug#896921: Upgrading salt to 2018.3.3 / tornado incompatibility

[Benjamin Drung]

Hi everyone,

I was working on salt to get it in shape before Debian freezes for the
buster release. The current status is:

 * Pushed a building python3-tornado4 version to the tornado4
   branch on salsa [tornado4].

 * Pushed current state of salt 2018.3.3 packaging to
   the wip-2018.3 branch [wip-2018.3]

 * salt builds against python3-tornado on Debian stretch, but
   fails on Debian unstable against python3-tornado4

 * Ignoring the test failures does not help: The salt-minion
   will fail to start on unstable

 * Built packages for Ubuntu 18.10 (Python 3.6)
   and 19.04 (Python 3.7) [ppa]:
   python3-tornado4 builds, but salt not

Remaining work:

 * 4 tornado tests are failing on Python 3.7 on Debian unstable.
   See upstream bug #2536 [2536]

 * Analyze and fix salt test failures on Debian unstable
   (might be either tornado4 rename or Python 3.7 related)

Help of getting salt working is appreciated.

[tornado4] 
https://salsa.debian.org/python-team/modules/python-tornado/commits/tornado4
[wip-2018.3] https://salsa.debian.org/salt-team/salt/commits/wip-2018.3
[ppa] https://launchpad.net/~bdrung/+archive/ubuntu/ppa
[2536] https://github.com/tornadoweb/tornado/issues/2536

-- 
Benjamin Drung
System Developer
Debian & Ubuntu Developer

1&1 IONOS Cloud GmbH | Greifswalder Str. 207 | 10405 Berlin | Germany
E-mail: benjamin.dr...@cloud.ionos.com | Web: www.ionos.de

Head Office: Berlin, Germany
District Court Berlin Charlottenburg, Registration number: HRB 125506 B
Executive Management: Christoph Steffens, Matthias Steinberg, Achim
Weiss

Member of United Internet

Bug#916377: cups-browsed: segfault during upgrade

[Thorsten Glaser]

retitle 916377 cups-browsed: segfault during upgrade and at system shutdown
forcemerge 916377 916149
thanks

On Thu, 13 Dec 2018, Till Kamppeter wrote:

> This I have already fixed upstream. It was already reported as

Ah, okay. In this case, sorry about the noise.

> upstream issue #79 and Debian bug #916149.

OK, merging… *looks* ah, that bug mentions systemd, so
I thought it not applicable to me ;)

bye,
//mirabilos
-- 
tarent solutions GmbH
Rochusstraße 2-4, D-53123 Bonn • http://www.tarent.de/
Tel: +49 228 54881-393 • Fax: +49 228 54881-235
HRB 5168 (AG Bonn) • USt-ID (VAT): DE122264941
Geschäftsführer: Dr. Stefan Barth, Kai Ebenrett, Boris Esser, Alexander Steeg