Bug#941193: filezilla: Crash on startup: undefined symbol: _ZTIN2fz6threadE

[jfp]

Package: filezilla
Version: 3.39.0-2
Severity: grave
Justification: renders package unusable

Dear Maintainer,

Crashes on startup with the folloing error:

filezilla: symbol lookup error: filezilla: undefined symbol: _ZTIN2fz6threadE




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

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

Versions of packages filezilla depends on:
ii  filezilla-common 3.39.0-2
ii  libatk1.0-0  2.34.0-1
ii  libc62.29-2
ii  libcairo21.16.0-4
ii  libdbus-1-3  1.12.16-1
ii  libfilezilla00.18.2-1
ii  libfontconfig1   2.13.1-2+b1
ii  libfreetype6 2.9.1-4
ii  libgcc1  1:9.2.1-8
ii  libgdk-pixbuf2.0-0   2.38.1+dfsg-1
ii  libglib2.0-0 2.60.6-2
ii  libgnutls30  3.6.9-5
ii  libgtk2.0-0  2.24.32-4
ii  libhogweed4  3.5.1+really3.4.1-1
ii  libnettle6   3.5.1+really3.4.1-1
ii  libpango-1.0-0   1.42.4-7
ii  libpangocairo-1.0-0  1.42.4-7
ii  libpangoft2-1.0-01.42.4-7
ii  libpugixml1v51.9-3
ii  libsqlite3-0 3.29.0-2
ii  libstdc++6   9.2.1-8
ii  libwxbase3.0-0v5 3.0.4+dfsg-12
ii  libwxgtk3.0-0v5  3.0.4+dfsg-12

Versions of packages filezilla recommends:
ii  xdg-utils  1.1.3-1

filezilla suggests no packages.

-- no debconf information

Bug#941189: [Pkg-javascript-devel] Bug#941189: node-set-value: CVE-2019-10747

[Xavier]

Le 26/09/2019 à 07:12, Salvatore Bonaccorso a écrit :
> Source: node-set-value
> Version: 0.4.0-1
> Severity: important
> Tags: security upstream
> Control: found -1 3.0.0-1
> 
> Hi,
> 
> The following vulnerability was published for node-set-value.
> 
> CVE-2019-10747[0]:
> | set-value is vulnerable to Prototype Pollution in versions lower than
> | 3.0.1. The function mixin-deep could be tricked into adding or
> | modifying properties of Object.prototype using any of the constructor,
> | prototype and _proto_ payloads.
> 
> 
> 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-2019-10747
> https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-10747
> [1] https://snyk.io/vuln/SNYK-JS-SETVALUE-450213

Hi,

here is a patch for Buster

Cheers,
Xavier
diff --git a/debian/changelog b/debian/changelog
index 49d174b..871978a 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,3 +1,9 @@
+node-set-value (0.4.0-1+deb10u1) buster-security; urgency=medium
+
+  * Fix prototype pollution (Closes: #941189, CVE-2019-10747)
+
+ -- Xavier Guimard   Thu, 26 Sep 2019 07:27:54 +0200
+
 node-set-value (0.4.0-1) unstable; urgency=low
 
   * Initial release (Closes: #842255)
diff --git a/debian/patches/CVE-2019-10747.diff 
b/debian/patches/CVE-2019-10747.diff
new file mode 100644
index 000..4f8dd54
--- /dev/null
+++ b/debian/patches/CVE-2019-10747.diff
@@ -0,0 +1,28 @@
+Description: Fix prototype pollution
+Author: Jon Schlinkert (https://github.com/jonschlinkert)
+Origin: upstream, https://github.com/jonschlinkert/set-value/commit/cb12f149
+Bug: https://snyk.io/vuln/SNYK-JS-SETVALUE-450213
+Bug-Debian: https://bugs.debian.org/941189
+Forwarded: not-needed
+Reviewed-By: Xavier Guimard 
+Last-Update: 2019-09-26
+
+--- a/index.js
 b/index.js
+@@ -24,7 +24,7 @@
+ return obj;
+   }
+ 
+-  var segs = path.split('.');
++  var segs = path.split('.').filter(isValidKey);
+   var len = segs.length, i = -1;
+   var res = obj;
+   var last;
+@@ -59,3 +59,7 @@
+   }
+   return res;
+ };
++
++function isValidKey(key) {
++  return key !== '__proto__' && key !== 'constructor' && key !== 'prototype';
++}
diff --git a/debian/patches/series b/debian/patches/series
new file mode 100644
index 000..ca81722
--- /dev/null
+++ b/debian/patches/series
@@ -0,0 +1 @@
+CVE-2019-10747.diff

Bug#936414: django-compat: Python2 removal in sid/bullseye

[Steve Langasek]

Package: django-compat
Followup-For: Bug #936414
User: ubuntu-de...@lists.ubuntu.com
Usertags: origin-ubuntu eoan ubuntu-patch

The attached patch drops the python2 package from django-compat.

Please consider uploading it to Debian at your convenience.

-- 
Steve Langasek   Give me a lever long enough and a Free OS
Debian Developer   to set it on, and I can move the world.
Ubuntu Developer   https://www.debian.org/
slanga...@ubuntu.com vor...@debian.org
diff -Nru django-compat-1.0.15/debian/control 
django-compat-1.0.15/debian/control
--- django-compat-1.0.15/debian/control 2018-04-21 05:40:51.0 -0700
+++ django-compat-1.0.15/debian/control 2019-09-25 22:29:05.0 -0700
@@ -5,28 +5,14 @@
 Section: python
 Priority: optional
 Build-Depends: debhelper (>= 9), dh-python,
- python-all (>= 2.6.6-3),
- python-setuptools (>= 0.6b3), python-django, python-six, python-django-nose,
  python3-all, python3-setuptools,
  python3-django, python3-six, python3-django-nose
-X-Python-Version: >=2.7
 Testsuite: autopkgtest
 Standards-Version: 4.1.4
 Homepage: https://github.com/arteria/django-compat
 Vcs-Git: https://github.com/Linaro/pkg-django-compat.git
 Vcs-Browser: https://github.com/Linaro/pkg-django-compat.git
 
-Package: python-django-compat
-Architecture: all
-Depends: python-six, ${misc:Depends}, ${python:Depends}
-Description: Forward and backwards compatibility layer for Django 1.4.x to 
1.9.x
- This module provides a backwards compatibility layer for Django versions which
- helps in the following:
-  1. Be able to use the LTS versions of Django and support newer versions in
- your app
-  2. Use features from newer Django versions in an old one
-  3. Manage and master the gap between different framework versions
-
 Package: python3-django-compat
 Architecture: all
 Depends: python3-six, ${misc:Depends}, ${python3:Depends}
diff -Nru django-compat-1.0.15/debian/rules django-compat-1.0.15/debian/rules
--- django-compat-1.0.15/debian/rules   2018-04-21 05:40:51.0 -0700
+++ django-compat-1.0.15/debian/rules   2019-09-25 22:29:05.0 -0700
@@ -1,14 +1,13 @@
 #!/usr/bin/make -f
 
 %:
-   dh $@ --with python2,python3
+   dh $@ --buildsystem pybuild --with python3
 
 override_dh_auto_test::
-   python runtests.py
+   python3 runtests.py
 
 override_dh_auto_install:
dh_auto_install
-   python setup.py install --root=debian/python-django-compat/ 
--install-layout=deb
python3 setup.py install --root=debian/python3-django-compat/ 
--install-layout=deb
 
 override_dh_auto_clean::

Bug#936415: django-hijack: Python2 removal in sid/bullseye

[Steve Langasek]

Package: django-hijack
Version: 2.1.7-1
Followup-For: Bug #936415
User: ubuntu-de...@lists.ubuntu.com
Usertags: origin-ubuntu eoan ubuntu-patch

Attached is a patch to drop the python2 package from django-hijack.

Please consider uploading at your convenience.

-- 
Steve Langasek   Give me a lever long enough and a Free OS
Debian Developer   to set it on, and I can move the world.
Ubuntu Developer   https://www.debian.org/
slanga...@ubuntu.com vor...@debian.org
diff -Nru django-hijack-2.1.7/debian/control django-hijack-2.1.7/debian/control
--- django-hijack-2.1.7/debian/control  2018-03-06 01:34:24.0 -0800
+++ django-hijack-2.1.7/debian/control  2019-09-25 21:41:08.0 -0700
@@ -5,25 +5,14 @@
 Section: python
 Priority: optional
 Build-Depends: debhelper (>= 9), dh-python,
- python-all (>= 2.6.6-3),
- python-setuptools (>= 0.6b3), python-django, python-django-nose,
- python-django-compat (>= 1.0.8), python3-all,
+ python3-all,
  python3-setuptools, python3-django, python3-django-nose,
  python3-django-compat (>= 1.0.8)
-X-Python-Version: >=2.7
 Standards-Version: 3.9.7
 Homepage: https://github.com/arteria/django-hijack
 Vcs-Git: https://github.com/Linaro/pkg-django-hijack.git
 Vcs-Browser: https://github.com/Linaro/pkg-django-hijack.git
 
-Package: python-django-hijack
-Architecture: all
-Depends: python-django-compat (>= 1.0.8), ${misc:Depends}, ${python:Depends}
-Description: Allows superusers to login as and work on behalf of other users
- django-hijack allows superusers to hijack or login as and work on behalf of
- other users without knowing their credentials. This is handy for testing and
- debug user problems by the django superuser.
-
 Package: python3-django-hijack
 Architecture: all
 Depends: python3-django-compat (>= 1.0.8), ${misc:Depends}, ${python3:Depends}
diff -Nru django-hijack-2.1.7/debian/rules django-hijack-2.1.7/debian/rules
--- django-hijack-2.1.7/debian/rules2018-03-06 01:34:24.0 -0800
+++ django-hijack-2.1.7/debian/rules2019-09-25 21:41:08.0 -0700
@@ -2,10 +2,9 @@
 
 export PYBUILD_NAME=django-hijack
 %:
-   dh $@ --with python2,python3 --buildsystem=pybuild
+   dh $@ --with python3 --buildsystem=pybuild
 
 override_dh_auto_test::
-   python runtests.py
python3 runtests.py
 
 override_dh_auto_clean::

Bug#941192: ebview FTCBFS: debian/rules uses the build architecture compiler

[Helmut Grohne]

Source: ebview
Version: 0.3.6.2-2
Tags: patch
User: debian-cr...@lists.debian.org
Usertags: ftcbfs

ebview fails to cross build from source, because debian/rules uses the
build architecture compiler as a make default. The easiest way of fixing
that is seeding CC from dpkg's buildtools.mk. Please consider applying
the attached patch.

Helmut
diff --minimal -Nru ebview-0.3.6.2/debian/changelog 
ebview-0.3.6.2/debian/changelog
--- ebview-0.3.6.2/debian/changelog 2018-11-04 16:12:52.0 +0100
+++ ebview-0.3.6.2/debian/changelog 2019-09-26 06:46:07.0 +0200
@@ -1,3 +1,9 @@
+ebview (0.3.6.2-3) UNRELEASED; urgency=medium
+
+  * Fix FTCBFS: Seed CC from dpkg's buildtools.mk. (Closes: #-1)
+
+ -- Helmut Grohne   Thu, 26 Sep 2019 06:46:07 +0200
+
 ebview (0.3.6.2-2) unstable; urgency=medium
 
   * QA upload
diff --minimal -Nru ebview-0.3.6.2/debian/rules ebview-0.3.6.2/debian/rules
--- ebview-0.3.6.2/debian/rules 2018-11-04 16:12:52.0 +0100
+++ ebview-0.3.6.2/debian/rules 2019-09-26 06:46:06.0 +0200
@@ -1,5 +1,6 @@
 #!/usr/bin/make -f
 
+-include /usr/share/dpkg/buildtools.mk
 export DEB_BUILD_MAINT_OPTIONS = hardening=+all
 
 %:

Bug#941191: gigalomania FTCBFS: uses build architecture build tools

[Helmut Grohne]

Source: gigalomania
Version: 1.0+ds1-1
Tags: patch
User: debian-cr...@lists.debian.org
Usertags: ftcbfs

gigalomania fails to cross build from source, because it uses build
architecture build tools. The easiest way of passing cross tools to make
- using dh_auto_build - doesn't fully work here, because gigalomania's
Makefile uses CC for the C++ compiler. The variable needs to be renamed.
Also debian/rules hard codes the build architecture pkg-config.
Supplying a pkg-config from dpkg's buildtools.mk fixes this part. Please
consider applying the attached patch.

Helmut
diff --minimal -Nru gigalomania-1.0+ds1/debian/changelog 
gigalomania-1.0+ds1/debian/changelog
--- gigalomania-1.0+ds1/debian/changelog2018-03-11 09:48:27.0 
+0100
+++ gigalomania-1.0+ds1/debian/changelog2019-09-26 05:57:14.0 
+0200
@@ -1,3 +1,13 @@
+gigalomania (1.0+ds1-1.1) UNRELEASED; urgency=medium
+
+  * Non-maintainer upload.
+  * Fix FTCBFS: (Closes: #-1)
++ Let dh_auto_build pass cross tools to make.
++ Rename the C++ compiler to CC.
++ Use a pkg-config from dpkg's buildtools.mk in d/rules.
+
+ -- Helmut Grohne   Thu, 26 Sep 2019 05:57:14 +0200
+
 gigalomania (1.0+ds1-1) unstable; urgency=medium
 
   * Initial release. (Closes: #865784)
diff --minimal -Nru gigalomania-1.0+ds1/debian/rules 
gigalomania-1.0+ds1/debian/rules
--- gigalomania-1.0+ds1/debian/rules2018-03-11 09:48:27.0 +0100
+++ gigalomania-1.0+ds1/debian/rules2019-09-26 05:57:14.0 +0200
@@ -1,6 +1,8 @@
 #!/usr/bin/make -f
 
 export DH_VERBOSE=1
+-include /usr/share/dpkg/buildtools.mk
+PKG_CONFIG?=pkg-config
 CPPFLAGS:=$(shell dpkg-buildflags --get CPPFLAGS)
 #CXXFLAGS:=$(shell dpkg-buildflags --get CXXFLAGS) $(CPPFLAGS)
 LDFLAGS:=$(shell dpkg-buildflags --get LDFLAGS)
@@ -9,10 +11,10 @@
dh $@
 
 override_dh_auto_build:
-   $(MAKE) DATADIR="/usr/share/gigalomania" \
-   CCFLAGS="-g -O2 -Wall $(CPPFLAGS)" \
+   dh_auto_build -- DATADIR="/usr/share/gigalomania" \
+   CC='$$(CXX)' CCFLAGS="-g -O2 -Wall $(CPPFLAGS)" \
LINKPATH="$(LDFLAGS) `sdl2-config --libs` -L/usr/X11R6/lib/ -L/usr/lib" 
\
-   LIBS="-lSDL2_image -lSDL2_mixer `pkg-config --libs tinyxml`" all
+   LIBS="-lSDL2_image -lSDL2_mixer `$(PKG_CONFIG) --libs tinyxml`" all
 
 override_dh_auto_install:
$(MAKE) DESTDIR="$(CURDIR)/debian/tmp/gigalomania" \

Bug#941190: ITP: golang-github-tv42-httpunix -- library to talk HTTP over Unix domain sockets

[Dmitry Smirnov]

Package: wnpp
Severity: wishlist
Owner: Dmitry Smirnov 
X-Debbugs-CC: debian-de...@lists.debian.org, 
pkg-go-maintain...@lists.alioth.debian.org
Control: affects -1 golang-github-circonus-labs-circonus-gometrics

   Package name: golang-github-tv42-httpunix
Version: 0.0~git20150427
Upstream Author: Tommi Virtanen
License: Expat
URL: https://github.com/tv42/httpunix
Vcs-Browser: 
https://salsa.debian.org/go-team/packages/golang-github-tv42-httpunix
Description: library to talk HTTP over Unix domain sockets
 Golang library to talk HTTP over Unix domain sockets.


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

Bug#902416: systemd: systemctl hibernate: unable to resume after upgrade

[Joel Cross]

Hi Michael,

Sorry I haven't been able to test out this fix yet. My laptop died shortly 
after receiving your message, and I'm currently not sure when I'll be able to 
get a suitable system together to test this out.
If someone else reading this wants to test out the fix instead, please be my 
guest!

-- 
  Joel Cross

Bug#941189: node-set-value: CVE-2019-10747

[Salvatore Bonaccorso]

Source: node-set-value
Version: 0.4.0-1
Severity: important
Tags: security upstream
Control: found -1 3.0.0-1

Hi,

The following vulnerability was published for node-set-value.

CVE-2019-10747[0]:
| set-value is vulnerable to Prototype Pollution in versions lower than
| 3.0.1. The function mixin-deep could be tricked into adding or
| modifying properties of Object.prototype using any of the constructor,
| prototype and _proto_ payloads.


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-2019-10747
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-10747
[1] https://snyk.io/vuln/SNYK-JS-SETVALUE-450213

Regards,
Salvatore

Bug#941015: [Freedombox-pkg-team] Bug#941015: Autopkgtests fail by using the now dropped py2 binary

[Sunil Mohan Adapa]

tag 941015 + pending
thanks

On 23/09/19 5:42 am, Christian Ehrhardt wrote:
> Package: django-ranged-response
> Version: 0.2.0-2
> 
> Hi,
> the autopkgtests of django-ranged-response fail since the last upload.
> This is due to the dropped py2 binary as the tests in d/t/control
> still want to install and test it.
> 
> Obvious suggestion is to remove the tests as well, but that is up to you.
> 
> P.S. I also found the same happened to python-django-gravatar2, could
> there be more and all with the same pattern?
> 

Thank you for reporting the bug and for the patch. I had already made
the changes for this in the Debian packaging repository.

g...@salsa.debian.org:freedombox-team/django-ranged-response.git

I will try again to find a sponsor to upload the package. If you are a
DD, please consider uploading from this repository.

Thanks,

-- 
Sunil



signature.asc
Description: OpenPGP digital signature

Bug#941188: ITP: golang-github-hashicorp-go-raftchunking -- chunking middleware for use by Raft clients

[Dmitry Smirnov]

Package: wnpp
Severity: wishlist
Owner: Dmitry Smirnov 
X-Debbugs-CC: debian-de...@lists.debian.org, 
pkg-go-maintain...@lists.alioth.debian.org
Control: affects -1 consul

   Package name: golang-github-hashicorp-go-raftchunking
Version: 0.6.2
Upstream Author: https://hashicorp.com/
License: MPL-2.0
URL: https://github.com/hashicorp/go-raftchunking
Vcs-Browser: 
https://salsa.debian.org/go-team/packages/golang-github-hashicorp-go-raftchunking
Description: chunking middleware for use by Raft clients
 Chunking middleware library for use by Raft clients.


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

Bug#941187: gradle: CVE-2019-15052

[Salvatore Bonaccorso]

Source: gradle
Version: 4.4.1-8
Severity: important
Tags: security upstream
Forwarded: https://github.com/gradle/gradle/issues/10278

Hi,

The following vulnerability was published for gradle.

CVE-2019-15052[0]:
| The HTTP client in Gradle before 5.6 sends authentication credentials
| originally destined for the configured host. If that host returns a
| 30x redirect, Gradle also sends those credentials to all subsequent
| hosts that the request redirects to. This is similar to
| CVE-2018-107.


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-2019-15052
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-15052
[1] https://github.com/gradle/gradle/issues/10278
[2] https://github.com/gradle/gradle/pull/10176
[3] https://github.com/gradle/gradle/security/advisories/GHSA-4cwg-f7qc-6r95

Please adjust the affected versions in the BTS as needed.

Regards,
Salvatore
Init: sysvinit (via /sbin/init)

Bug#941186: gradle: CVE-2019-16370

[Salvatore Bonaccorso]

Source: gradle
Version: 4.4.1-8
Severity: important
Tags: security upstream
Forwarded: https://github.com/gradle/gradle/pull/10543
Control: found -1 4.4.1-6

Hi,

The following vulnerability was published for gradle.

CVE-2019-16370[0]:
| The PGP signing plugin in Gradle before 6.0 relies on the SHA-1
| algorithm, which might allow an attacker to replace an artifact with a
| different one that has the same SHA-1 message digest, a related issue
| to CVE-2005-4900.


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-2019-16370
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-16370
[1] https://github.com/gradle/gradle/pull/10543
[2] 
https://github.com/gradle/gradle/commit/425b2b7a50cd84106a77cdf1ab665c89c6b14d2f

Please adjust the affected versions in the BTS as needed.

Regards,
Salvatore

Bug#941185: hunspell: CVE-2019-16707

[Salvatore Bonaccorso]

Source: hunspell
Version: 1.7.0-2
Severity: normal
Tags: security upstream

Hi,

The following vulnerability was published for hunspell. This is not
really a big issue, and negligigle in security tracking context, but
as it seems to have been reported just as crash in [1] it might be
worth reporting it up to upstream.

CVE-2019-16707[0]:
| Hunspell 1.7.0 has an invalid read operation in
| SuggestMgr::leftcommonsubstring in suggestmgr.cxx.


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-2019-16707
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-16707
[1] https://github.com/butterflyhack/hunspell-crash

Please adjust the affected versions in the BTS as needed.

Regards,
Salvatore
Init: sysvinit (via /sbin/init)

Bug#941184: RM: dballe [armel armhf i386 mipsel] -- RoQA; FTBFS on these archs: preventing cruft removal for other packages

[Scott Kitterman]

Package: ftp.debian.org
Severity: normal

If they build later, they'll come back, so let's clear this out so the
python2 removal won't be blocked.

Scott K

Bug#941183: libepub0: baloo_file_extractor segfault because of null pointer deference in ebook-tools libepub/list.c

[Paul Ezvan]

Package: libepub0
Version: 0.2.2-4+b4
Severity: normal
Tags: patch upstream

Dear Maintainer,

baloo_file_extractor is crashing when analyzing epub files with invalid format,
as some epub files cause libepub to segfault.

As after crashing it would retry scanning the same file, it will keep crashing
when restarted.

I am attaching a patch to resolve the issue in libepub, which allows
baloo_file_extractor to successfully scan the file.
Note that baloo_file_extractor would use more than 8 GiB of memory while
scanning some epub files, which leads to think that libepub might have some
memleaks as well.
Application: baloo_file_extractor (5.62.0)

Qt Version: 5.11.3
Frameworks Version: 5.62.0
Operating System: Linux 5.2.0-2-amd64 x86_64
Distribution: Debian GNU/Linux bullseye/sid

-- Information about the crash:


The crash can be reproduced every time.

-- Backtrace:
Application: Extracteur de fichier Baloo (baloo_file_extractor), signal: 
Segmentation fault
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
[Current thread is 1 (Thread 0x7f7c407b5040 (LWP 1788))]

Thread 3 (Thread 0x7f7c3eb10700 (LWP 1795)):
#0  0x7f7c43cbfd2f in poll () from /lib/x86_64-linux-gnu/libc.so.6
#1  0x7f7c42eebbf6 in g_main_context_poll (priority=, 
n_fds=1, fds=0x7f7c3001a640, timeout=, context=0x7f7c3bf0) 
at ../../../glib/gmain.c:4228
#2  g_main_context_iterate (context=context@entry=0x7f7c3bf0, 
block=block@entry=1, dispatch=dispatch@entry=1, self=) at 
../../../glib/gmain.c:3922
#3  0x7f7c42eebd1c in g_main_context_iteration (context=0x7f7c3bf0, 
may_block=may_block@entry=1) at ../../../glib/gmain.c:3988
#4  0x7f7c442263e3 in QEventDispatcherGlib::processEvents 
(this=0x7f7c3b20, flags=...) at kernel/qeventdispatcher_glib.cpp:424
#5  0x7f7c441d3cfb in QEventLoop::exec (this=this@entry=0x7f7c3eb0fd70, 
flags=..., flags@entry=...) at 
../../include/QtCore/../../src/corelib/global/qflags.h:140
#6  0x7f7c44023d8e in QThread::exec (this=) at 
../../include/QtCore/../../src/corelib/global/qflags.h:120
#7  0x7f7c45159545 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5DBus.so.5
#8  0x7f7c4402da07 in QThreadPrivate::start (arg=0x7f7c451d8d60) at 
thread/qthread_unix.cpp:367
#9  0x7f7c43765fb7 in start_thread () from 
/lib/x86_64-linux-gnu/libpthread.so.0
#10 0x7f7c43cca2ef in clone () from /lib/x86_64-linux-gnu/libc.so.6

Thread 2 (Thread 0x7f7c3f5bd700 (LWP 1789)):
#0  0x7f7c43cbfd2f in poll () from /lib/x86_64-linux-gnu/libc.so.6
#1  0x7f7c42e72cf7 in ?? () from /usr/lib/x86_64-linux-gnu/libxcb.so.1
#2  0x7f7c42e7491a in xcb_wait_for_event () from 
/usr/lib/x86_64-linux-gnu/libxcb.so.1
#3  0x7f7c40368d79 in QXcbEventReader::run (this=0x55b606189d90) at 
qxcbconnection.h:409
#4  0x7f7c4402da07 in QThreadPrivate::start (arg=0x55b606189d90) at 
thread/qthread_unix.cpp:367
#5  0x7f7c43765fb7 in start_thread () from 
/lib/x86_64-linux-gnu/libpthread.so.0
#6  0x7f7c43cca2ef in clone () from /lib/x86_64-linux-gnu/libc.so.6

Thread 1 (Thread 0x7f7c407b5040 (LWP 1788)):
[KCrash Handler]
#6  0x7f7c3dd57bf0 in _list_cmp_label_by_lang () from /usr/lib/libepub.so.0
#7  0x7f7c3dd574c8 in FindNode () from /usr/lib/libepub.so.0
#8  0x7f7c3dd56aae in _opf_label_get_by_lang () from /usr/lib/libepub.so.0
#9  0x7f7c3dd53629 in epub_tit_next () from /usr/lib/libepub.so.0
#10 0x7f7c3df89088 in KFileMetaData::EPubExtractor::extract 
(this=, result=0x7fff4f1e5470) at 
./src/extractors/epubextractor.cpp:184
#11 0x55b605347d47 in Baloo::App::index (this=this@entry=0x7fff4f1e5bb0, 
tr=0x55b6061f1d80, url=..., id=id@entry=36107081387933192) at 
./src/file/extractor/app.cpp:192
#12 0x55b60534a05b in Baloo::App::processNextFile (this=0x7fff4f1e5bb0) at 
./src/file/extractor/app.cpp:112
#13 0x7f7c4420a106 in QtPrivate::QSlotObjectBase::call (a=0x7fff4f1e55c0, 
r=, this=) at 
../../include/QtCore/../../src/corelib/kernel/qobjectdefs_impl.h:376
#14 QSingleShotTimer::timerEvent (this=0x55b60627b950) at kernel/qtimer.cpp:318
#15 0x7f7c441fed1b in QObject::event (this=0x55b60627b950, e=) at kernel/qobject.cpp:1232
#16 0x7f7c44b4f501 in QApplicationPrivate::notify_helper 
(this=this@entry=0x55b6061770d0, receiver=receiver@entry=0x55b60627b950, 
e=e@entry=0x7fff4f1e5880) at kernel/qapplication.cpp:3726
#17 0x7f7c44b569b0 in QApplication::notify (this=0x7fff4f1e5ba0, 
receiver=0x55b60627b950, e=0x7fff4f1e5880) at kernel/qapplication.cpp:3485
#18 0x7f7c441d5029 in QCoreApplication::notifyInternal2 
(receiver=0x55b60627b950, event=event@entry=0x7fff4f1e5880) at 
../../include/QtCore/5.11.3/QtCore/private/../../../../../src/corelib/thread/qthread_p.h:307
#19 0x7f7c442257d8 in QCoreApplication::sendEvent (event=0x7fff4f1e5880, 
receiver=) at 
../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:234
#20 QTimerInfoList::activateTimers (this=0x55b6061c9f80) at 
kernel/qtimerinfo_unix.cpp:643
#21 

Bug#933640: cloud-init 18.3 failed to run after installed in Debian 10

[Marco Sinhoreli]

I have the same issue. I don’t know if it helps, but, if I start cloud-init 
systemd daemon manually it works. Maybe the problem is around systemd.

On Thu, 1 Aug 2019 10:03:22 + Yanhui He 
mailto:yanh...@vmware.com>> wrote:
> Package: cloud-init
> Version: 18.3
> X-Debbugs-CC: h...@vmware.com, 
> pengpe...@vmware.com , 
> l...@vmware.com
>
> After "apt-get install cloud-init" and enable cloud-init customize in file of 
> "/etc/cloud/cloud.cfg" in Debian 10.0.0 GA, cloud-init doesn’t run even after 
> reboot.
>
> # cloud-init -v
> /usr/bin/cloud-init 18.3
> # ls /var/log/cloud-init.log
> ls: cannot access '/var/log/cloud-init.log': No such file or directory
> # systemctl status cloud-init.service
> ● cloud-init.service - Initial cloud-init job (metadata service crawler)
>Loaded: loaded (/lib/systemd/system/cloud-init.service; enabled; vendor 
> prese
>Active: inactive (dead)
> # systemctl status cloud-init-local.service
> ● cloud-init-local.service - Initial cloud-init job (pre-networking)
>Loaded: loaded (/lib/systemd/system/cloud-init-local.service; enabled; 
> vendor
>Active: inactive (dead)
>
> Would you please help us take a look?
>
> If need any other information, please kindly tell me!
>
> --
>
> Best Regards,
> Yanhui
>
>



[signature_1483908580]
Marco Sinhoreli
Latam Technical Director
marco.sinhor...@shapeblue.com
mobile: +55 11 95656-3636

Rua Gomes de Carvalho, 911 – Sala 316
Vila Olímpia, São Paulo, SP, Brasil, 04547-003
Phone: + 55 11 2818-3419
http://www.shapeblue.com/ | twitter: @shapeblue

Bug#941161: libgl1-mesa-dri: SIGSEGV on starting X server with libgl1-mesa-dri >18.3.6-2, <=19.1.6-1

[Timo Aaltonen]

On 25.9.2019 22.01, Jim Joyce wrote:
> Package: libgl1-mesa-dri
> Version: 19.1.6-1
> Severity: important
> 
> Dear Maintainer,
> 
> (This is my first Debian bug report, so apologies if I make any mistakes)
> 
> Recently, I performed a "cautious upgrade" of my system using Muon package 
> manager. This affected a number of packages, including libgl1-mesa-dri.
> After this, I found that my system would freeze when booting into X and/or 
> SDDM, just displaying a white underscore on a black screen, 
> and not even permitting switching terminal with ctrl-alt-F*.
> 
> I remoted into my system, and downgraded the various packages affected, using 
> .deb files downloaded from snapshot.debian.org, in order
> to get my computer usable again. After doing this, X could boot again. I 
> experimented with upgrading and downgrading various packages in order 
> to reproduce the issue; it seems that the faulty package is libgl1-mesa-dri, 
> of which I have both :amd64 and :i386 installed, and they both depend
> on each other so I can't test them individually.
> 
> With these packages at version 19.1.6-1, the X server crashes with a SIGSEGV 
> every time; at 18.3.6-2, they work fine, so presumably the issue
> is in a version between these two, althoug these are the only ones I've 
> tried. The stacktrace from X should be attached below; I didn't see anything
> paticuarly interesting in dmesg, and I'm not sure if Mesa keeps it's own log 
> files anywhere so I've not been able to check them.
> 
> I'm happy to provide more information if required; I have basic knowledge 
> with debugging software, although I'd need a bit of guidance about where
> to start.
> 
> Thanks,
> Jim Joyce
This can't do any good on a system with a Radeon (installing nvidia):

Start-Date: 2019-09-25  19:28:47
Commandline: apt --fix-broken install
Requested-By: jimj316 (1000)
Install: libgles1:i386 (1.1.0-1+b1, automatic), libgles2:i386
(1.1.0-1+b1, automatic), glx-alternative-nvidia:amd64 (1.0.0,
automatic), nvidia-alternative:amd64 (430.50-1, automatic)
Upgrade: libnvidia-glvkspirv:amd64 (418.88-1, 430.50-1),
libnvidia-glvkspirv:i386 (418.88-1, 430.50-1), libgles-nvidia1:i386
(418.88-1, 430.50-1), libgles-nvidia2:i386 (418.88-1, 430.50-1),
nvidia-vulkan-icd:amd64 (418.88-1, 430.50-1), nvidia-vulkan-icd:i386
(418.88-1, 430.50-1), nvidia-egl-icd:i386 (418.88-1, 430.50-1),
libgl1-nvidia-glvnd-glx:i386 (418.88-1, 430.50-1), libglx-nvidia0:amd64
(418.88-1, 430.50-1), libglx-nvidia0:i386 (418.88-1, 430.50-1),
libegl-nvidia0:amd64 (418.88-1, 430.50-1), libegl-nvidia0:i386
(418.88-1, 430.50-1), nvidia-driver-libs:i386 (418.88-1, 430.50-1),
libnvidia-glcore:amd64 (418.88-1, 430.50-1), libnvidia-glcore:i386
(418.88-1, 430.50-1), libnvidia-eglcore:amd64 (418.88-1, 430.50-1),
libnvidia-eglcore:i386 (418.88-1, 430.50-1)
End-Date: 2019-09-25  19:29:56

though you had glx-diversions already installed before this meaning you
probably had amdgpu-pro installed, and we don't support that.


-- 
t

Bug#941182: ITP: golang-github-sylabs-sif -- reference implementation of the Singularity Image Format (SIF)

[Dmitry Smirnov]

Package: wnpp
Severity: wishlist
Owner: Dmitry Smirnov 
X-Debbugs-CC: debian-de...@lists.debian.org, 
pkg-go-maintain...@lists.alioth.debian.org
Control: affects -1 singularity-container

   Package name: golang-github-sylabs-sif
Version: 1.0.8
Upstream Author: sylabs.io
License: BSD-3-Clause
URL: https://github.com/sylabs/sif
Vcs-Browser: 
https://salsa.debian.org/go-team/packages/golang-github-sylabs-sif
Description: reference implementation of the Singularity Image Format (SIF)
 SIF is an implementation of the Singularity Container Image Format that
 makes it easy to create complete and encapsulated container enviroments
 stored in a single file.


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

Bug#941181: ITP: golang-github-sylabs-json-resp -- marshall and unmarshall response data and errors in JSON format

[Dmitry Smirnov]

Package: wnpp
Severity: wishlist
Owner: Dmitry Smirnov 
X-Debbugs-CC: debian-de...@lists.debian.org, 
pkg-go-maintain...@lists.alioth.debian.org
Control: affects -1 singularity-container

   Package name: golang-github-sylabs-json-resp
Version: 0.6.0
Upstream Author: sylabs.io
License: BSD-3-Clause
URL: https://github.com/sylabs/json-resp
Vcs-Browser: 
https://salsa.debian.org/go-team/packages/golang-github-sylabs-json-resp
Description: marshall and unmarshall response data and errors in JSON format
 json-resp package contains a small set of functions that are used to
 marshall and unmarshall response data and errors in JSON format.


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

Bug#940034: libelogind0: replacing a core system library and conflicting against the default init considered harmful

[Mark Hindley]

On Thu, Sep 26, 2019 at 12:11:47AM +0200, Thorsten Glaser wrote:
> On Wed, 25 Sep 2019, Mark Hindley wrote:
> 
> > Thanks. Triggers may be an answer to the libsystemd soversion issue.
> 
> Mind that anything that runs between unpacking the new libsystemd0
> and running the trigger will use libsystemd0 instead of libelogind0.

Ah, of course!

Sam,

I don't see a way of implementing a robust dpkg-divert solution.

Sorry.

Mark

Bug#941115: closed by Ben Hutchings (Re: Bug#941115: linux-image-4.19.0-6-686: cat /proc/acpi/ibm/video ,computer dead !thinkpad_acpi bug?)

[Faris Xiao]

http://ibm-acpi.sourceforge.net/README

This document has describe how to use /proc/acpi/ibm/video:

--

Video output control -- /proc/acpi/ibm/video


This feature allows control over the devices used for video output -
LCD, CRT or DVI (if available). The following commands are available:

    echo lcd_enable > /proc/acpi/ibm/video
    echo lcd_disable > /proc/acpi/ibm/video
    echo crt_enable > /proc/acpi/ibm/video
    echo crt_disable > /proc/acpi/ibm/video
    echo dvi_enable > /proc/acpi/ibm/video
    echo dvi_disable > /proc/acpi/ibm/video
    echo auto_enable > /proc/acpi/ibm/video
    echo auto_disable > /proc/acpi/ibm/video
    echo expand_toggle > /proc/acpi/ibm/video
    echo video_switch > /proc/acpi/ibm/video


These commands also cause my computer dead.

Is there i915 driver problem ? I has these error info in dmesg:

[    4.847462] [drm:intel_cpu_fifo_underrun_irq_handler [i915]] *ERROR*
CPU pipe A FIFO underrun
[    4.847559] [drm:intel_set_cpu_fifo_underrun_reporting [i915]]
*ERROR* pipe B underrun
[    4.847640] [drm:intel_cpu_fifo_underrun_irq_handler [i915]] *ERROR*
CPU pipe B FIFO underrun

在 2019/9/25 下午11:42, Debian Bug Tracking System 写道:
> This is an automatic notification regarding your Bug report
> which was filed against the src:linux package:
>
> #941115: linux-image-4.19.0-6-686: cat /proc/acpi/ibm/video ,computer dead 
> !thinkpad_acpi bug?
>
> It has been closed by Ben Hutchings .
>
> 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 Ben Hutchings 
>  by
> replying to this email.
>
>
-- 
肖盛文  Faris Xiao




signature.asc
Description: OpenPGP digital signature

Bug#941048: fwupd: provide option to never send report

[brian m. carlson]

On 2019-09-25 at 20:09:11, mario.limoncie...@dell.com wrote:
> OK, 1.3.2 release of fwupd will have this:
> https://github.com/fwupd/fwupd/commit/f1accad201b24565f3e19daa09d26b477c3f4b9c

That's great to hear.  I'm looking forward to it.
-- 
brian m. carlson: Houston, Texas, US
OpenPGP: https://keybase.io/bk2204


signature.asc
Description: PGP signature

Bug#941174: Acknowledgement (glibc: FTBFS on hppa - new test failures)

[John David Anglin]

The segmentation faults in these tests occur in _dl_fixup().

Sep 25 20:02:39 mx3210 kernel: trap #15: Data TLB miss fault, vm_start = 0x00015
000, vm_end = 0x00016000
Sep 25 20:02:39 mx3210 kernel: CPU: 0 PID: 2908 Comm: ld.so.1 Not tainted 4.14.1
46+ #1
Sep 25 20:02:39 mx3210 kernel: Hardware name: 9000/800/rp3440
Sep 25 20:02:39 mx3210 kernel: task: 000197cda000 task.stack: 0001cdc2c0
00
Sep 25 20:02:39 mx3210 kernel:
Sep 25 20:02:39 mx3210 kernel: YZrvWESTHLNXBCVMcbcbcbcbOGFRQPDI
Sep 25 20:02:39 mx3210 kernel: PSW: 0100 Not tainted
Sep 25 20:02:39 mx3210 kernel: r00-03  00ff0004ff0f f6a79228 000
0f89e787b f7279698
Sep 25 20:02:39 mx3210 kernel: r04-07  f83f82e4 f6a79000 000
1f069893c f6a79290
Sep 25 20:02:39 mx3210 kernel: r08-11  f72794e8 f869b004 000
0f72796b4 f8d024d0
Sep 25 20:02:39 mx3210 kernel: r12-15  f72796a8  000
0 f869d82c
Sep 25 20:02:39 mx3210 kernel: r16-19   f869d828 000
0f7279480 f89f815c
Sep 25 20:02:39 mx3210 kernel: r20-23  f83f4f50 f83f4f80 000
0f82a0658 
Sep 25 20:02:39 mx3210 kernel: r24-27   f83f82e4 000
0f8cff6b0 00015000
Sep 25 20:02:39 mx3210 kernel: r28-31  0034 f7279698 000
0f6a79300 f8684e6f
Sep 25 20:02:39 mx3210 kernel: sr00-03  0dee5000  00
00 0dee5000
Sep 25 20:02:39 mx3210 kernel: sr04-07  0dee5000 0dee5000 00
000dee5000 0dee5000
Sep 25 20:02:39 mx3210 kernel:
Sep 25 20:02:39 mx3210 kernel:  VZOUICununcqcqcqcqcqcrmunTDVZOUI
Sep 25 20:02:39 mx3210 kernel: FPSR: 
Sep 25 20:02:39 mx3210 kernel: FPER1: 
Sep 25 20:02:39 mx3210 kernel: fr00-03    00
00 
Sep 25 20:02:39 mx3210 kernel: fr04-07  0003 4008 00
00 4090
Sep 25 20:02:39 mx3210 kernel: fr08-11    
 
Sep 25 20:02:39 mx3210 kernel: fr12-15    
 
Sep 25 20:02:39 mx3210 kernel: fr16-19    
 
Sep 25 20:02:39 mx3210 kernel: fr20-23    
0088 0037
Sep 25 20:02:39 mx3210 kernel: fr24-27  41d442209dc0 8dd8e63ce5a92bce 
e12c4247803777cd 63a440f29eda3092
Sep 25 20:02:39 mx3210 kernel: fr28-31  2deb33a075f5d1c1 6b17d1f2508fe882 
d898c296 
Sep 25 20:02:39 mx3210 kernel:
Sep 25 20:02:39 mx3210 kernel: IASQ: 0dee5000 0dee5000 IAOQ: 
f89e09ef f89e09f3
Sep 25 20:02:39 mx3210 kernel: IIR: 0ed90085    ISR: 0dee5000  IOR: 
f069893c
Sep 25 20:02:39 mx3210 kernel: CPU:    0   CR30: 0001cdc2c000 CR31: 
efff
Sep 25 20:02:39 mx3210 kernel: ORIG_R28: 
Sep 25 20:02:39 mx3210 kernel: IAOQ[0]: f89e09ef
Sep 25 20:02:39 mx3210 kernel: IAOQ[1]: f89e09f3
Sep 25 20:02:39 mx3210 kernel: RP(r2): f89e787b

Dump of assembler code for function _dl_fixup:
   0xf89e09b8 <+0>: stw rp,-14(sp)
   0xf89e09bc <+4>: ldo 80(sp),sp
   0xf89e09c0 <+8>: stw r7,-6c(sp)
   0xf89e09c4 <+12>:    ldo -70(sp),r7
   0xf89e09c8 <+16>:    stw r6,-68(sp)
   0xf89e09cc <+20>:    stw r5,-64(sp)
   0xf89e09d0 <+24>:    stw r4,-60(sp)
   0xf89e09d4 <+28>:    stw r3,-5c(sp)
   0xf89e09d8 <+32>:    stw r19,-20(sp)
   0xf89e09dc <+36>:    ldw 7c(r26),r21
   0xf89e09e0 <+40>:    ldw 4(r21),r22
   0xf89e09e4 <+44>:    ldw 38(r26),r20
   0xf89e09e8 <+48>:    add,l r25,r22,r6
  =>  0xf89e09ec <+52>:    ldw r25(r22),r5
   0xf89e09f0 <+56>:    ldw 4(r6),r21
   0xf89e09f4 <+60>:    extrw,u r21,23,24,r31
   0xf89e09f8 <+64>:    depw,z r31,27,28,ret1
   0xf89e09fc <+68>:    ldw 34(r26),r22


-- 
John David Anglin  dave.ang...@bell.net

Bug#941179: O: sandboxgamemaker -- 3D game maker and 3D game design program

[Anthony F McInerney]

Package: wnpp
Severity: normal

Bug#941180: usbprog: Should usbprog be removed from Debian?

[Olly Betts]

Source: usbprog
Version: 0.2.0-2.2
Severity: normal

I think it's time to remove the usbprog package:

* upstream website gives 500 error
* last upstream release packaged was ~8.5 years ago
* has low popcon - inst:231 vote:180
* has no reverse dependencies (according to dak rm)
* last maintainer upload was over 7.5 years ago
* 4 open bugs with no maintainer response to any of them
* I had to NMU for the last wxWidgets transition 5 years ago, and
  it's now a blocker for the current wxwidgets3.0-gtk3 transition.

If there are no objections within two weeks, I'll turn this into an RM
bug.

Cheers,
Olly

Bug#941178: rapidsvn: Should rapidsvn be removed from Debian?

[Olly Betts]

Source: rapidsvn
Version: 0.12.1dfsg-3.1
Severity: normal

I think it's time to remove the rapidsvn package:

* last upstream release was nearly 10 years old
* has low popcon - inst:440 vote:66
* has no reverse dependencies (according to dak rm)
* last maintainer upload was over 4 years ago
* 8 open bugs with no maintainer response to any of them
* I had to NMU for the last wxWidgets transition 5 years ago, and
  it's now a blocker for the current wxwidgets3.0-gtk3 transition.

If there are no objections within two weeks, I'll turn this into an RM
bug.

Cheers,
Olly

Bug#909260: linux-source: make deb-pkg fails

[Ben Hutchings]

Control: reassign -1 src:linux 4.18.6-1
Control: tag -1 moreinfo unreproducible

On Thu, 20 Sep 2018 09:08:05 -0400 Dominique Brazziel  
wrote:
> Package: linux-source
> Version: 4.18+98
> Severity: important
> 
> Dear Maintainer,
> 
> *** Reporter, please consider answering these questions, where appropriate ***
> 
>* What led up to the situation?
> Attempt to build custom debian kernel with 'make deb-pkg'   per 
> the
> Debian Kernel Handbook
> 
>* What exactly did you do (or not do) that was effective (or
>  ineffective)?
> make deb-pkg
> 
>* What was the outcome of this action?
> link of fixdep.o.in fails with following message:
> /usr/bin/ld: /usr/src/linux-source-4.18/tools/objtool/fixdep-
> in.o: relocation R_X86_64_32 against `.rodata.str1.1' can not be used when
> making a PIE object; recompile with -fPIC
[...]

I couldn't reproduce this.  Is this still happening?  Are you trying to
build with Debian's gcc and binutils, or some other versions?

Ben.

-- 
Ben Hutchings
Beware of programmers who carry screwdrivers. - Leonard Brandwein




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

Bug#933450: fityk: Please rebuild against wxWidgets GTK 3 package

[Olly Betts]

On Thu, Aug 08, 2019 at 02:59:56PM +1000, Stuart Prescott wrote:
> On Thursday, 8 August 2019 09:57:42 AEST Olly Betts wrote:
> > There have been a lot of GTK3-related fixes in wxGTK since then so I'd
> > expect it to work much better now.
> 
> Thanks for that useful info, Olly.
> 
> I've uploaded it to experimental building against GTK3 so we can see that it 
> builds and tests correctly everywhere (although the tests aren't really going 
> to test the GUI!). That also makes packages that are easier to test.

It's had more than 6 weeks in experimental now - unless that's uncovered
problems, maybe it's time to upload to unstable?

Cheers,
Olly

Bug#933440:

[Olly Betts]

On Tue, Sep 10, 2019 at 09:47:37AM +1200, Olly Betts wrote:
> Looks like I failed to actually attach that debdiff - here it is.
> 
> While getting the development branch to work with GTK3 is obviously
> desirable for the longer term, for the purposes of this transition what
> matters is the currently packaged version, and as I said above that
> doesn't seem to exhibit the problem you're hitting with the development
> version.

Any objections to me NMUing the debdiff I send a few weeks ago?

Cheers,
Olly

Bug#939971: runit: Export NAME and add a VERBOSE option to invoke-run

[Dmitry Bogatov]

Control: tags -1 +pending

[2019-09-25 01:01] Lorenzo Puliti 
> Package: runit
> Followup-For: Bug #939971
>
> > What is missing is documentation
> > ...
> > I think you want to source /etc/default/runit *before*
> > /etc/default/service.
>
> updated patch is attached

Looks good, applied. Thanks.

Just minor nit: please add 'Closes: #n' to commit message, if you
know it (like this case, when this is second version of patch). Makes
regeneration of changelog simplier.
-- 
Note, that I send and fetch email in batch, once in a few days.
Please, mention in body of your reply when you add or remove recepients.

Bug#592124: I'm Stella Shukri,

[Stella Shukri]

Good Day Dear,
 I'm Stella Shukri,I'm here to inform you about my business proposal, which my 
father, a politician advice me to do, before his death. I'm at the hospital bed 
and I need your urgent partnership, so that you will help me to Invest my money 
in Country okay.I will be happy to hear from you as soon as you read my 
message.Thank you.Stella Shukri

Bug#941177: stx-btree: Should stx-btree be removed from Debian?

[Olly Betts]

Source: stx-btree
Version: 0.9-2
Severity: normal

I think it's time to remove the stx-btree package:

* Upstream have declared the project obsolete -
  http://panthema.net/2007/stx-btree/ says: "The STX B+ Tree package is
  now obsolete (2019), because an improved version with better STL
  semantics is contained the new TLX library of C++ containers and
  algorithms."
* has really low popcon - inst:7 vote:1
* has no reverse dependencies (according to dak rm)
* last maintainer upload was over 4 years ago
* I had to NMU for the last wxWidgets transition 5 years ago, and
  it's now a blocker for the current wxwidgets3.0-gtk3 transition.

If there are no objections within two weeks, I'll turn this into an RM
bug.

Cheers,
Olly

Bug#941176: irqbalance: out of date

[Sevag Hanssian]

Package: irqbalance
Version: 1.1.0-2.3
Severity: important

Dear Maintainer,

I'm using irqbalance 1.1.0 on Debian Stretch on kernel 4.9.0. We noticed
recently all eth irqs being sent to a single CPU, causing bad performance.
I filed an irqbalance issue 
(https://github.com/Irqbalance/irqbalance/issues/122).
The conclusion is that a newer versions of irqbalance fixes the problem.

Could the stretch version of irqbalance get updated to 1.5.0 or 1.6.0?

Regards.


-- System Information:
Debian Release: 9.9
  APT prefers oldstable
  APT policy: (500, 'oldstable')
Architecture: amd64 (x86_64)

Kernel: Linux 4.9.0-3-amd64 (SMP w/32 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/bash
Init: systemd (via /run/systemd/system)

Versions of packages irqbalance depends on:
ii  debconf [debconf-2.0]  1.5.61
ii  init-system-helpers1.48
ii  libc6  2.24-11+deb9u4
ii  libcap-ng0 0.7.7-3+b1
ii  libglib2.0-0   2.50.3-2+deb9u1
ii  libnuma1   2.0.11-2.1
ii  libsystemd0237-3~bpo9+1
ii  lsb-base   9.20161125

irqbalance recommends no packages.

irqbalance suggests no packages.

-- debconf-show failed

Bug#941175: lp-shell: invalid syntax error on start

[dann frazier]

Package: lptools
Version: 0.2.0-5
Severity: normal

$ lp-shell
  File "/usr/bin/lp-shell", line 55
except ValueError, err:
 ^
SyntaxError: invalid syntax

Perhaps more python3ing to do :)

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

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

Versions of packages lptools depends on:
ii  python3   3.7.3-1
ii  python3-breezy3.0.1-6
ii  python3-launchpadlib  1.10.7-1
ii  python3-xdg   0.25-5
ii  sensible-utils0.0.12

Versions of packages lptools recommends:
ii  python3-chameleon  3.6.2-2
pn  python3-gtk2   
pn  python3-indicate   

Versions of packages lptools suggests:
pn  python3-tdb  

-- no debconf information

Bug#933469: mrpt: Please rebuild against wxWidgets GTK 3 package

[Olly Betts]

On Thu, Sep 26, 2019 at 12:29:02AM +0200, José Luis Blanco-Claraco wrote:
> I'm the maintainer of the upstream library, and have just released
> upstream bug-fix release (v1.5.8) which also comes with an updated
> debian/control per this original bug report.
> It would be great if some of you could sponsor its upload so this bug
> gets fixed asap...
>
> The new package for version 1.5.8 has been tested with pbuilder to
> build cleanly and to be lintian clean on "sid".
> However, I uploaded it twice today to mentors.debian.net without any
> error but it won't show on the web... so I'll leave a copy here:
> 
> https://ingmec.ual.es/~jlblanco/downloads/mrpt_1.5.8-1.dsc

The key this is signed with isn't one of the 3 keys in:

mrpt-1.5.6/debian/upstream/signing-key.asc

key 9AA38DCD55BE302B: "Debian Archive Automatic Signing Key (5.0/lenny) 
"
key 4F9946354E9CFF4E: "Spotify Public Repository Signing Key 
"
key D443304FBD70A641: "Jose Luis Blanco (University of Malaga)
"

(I also wonder if the first two should be there at all...)

I'm afraid this is too big a change for me to be comfortable sponsoring
without any sort of trust path.  I'm happy to NMU just the update that's
actually needed to fix this bug though.

Cheers,
Olly

Bug#844607: libfontconfig1-dev:amd64 cannot be installed together with libfontconfig1-dev:i386

[Arnaldo Pirrone]

Package: libfontconfig1-dev
Version: 2.13.1-2+b1
Followup-For: Bug #844607

I can confirm this issue,
libfontconfig1-dev:i386 is still trying to overwrite some files installed by
the package with the same name for a different architecture:

Estrazione di libfontconfig1-dev:i386 (2.13.1-2+b1)...
dpkg: errore nell'elaborare l'archivio
/var/cache/apt/archives/libfontconfig1-dev_2.13.1-2+b1_i386.deb (--unpack):
tentata sovrascrittura di "/usr/share/doc/libfontconfig1-dev/fontconfig-
devel.pdf.gz" (condiviso), diverso da altre istanze del pacchetto
libfontconfig1-dev:i386
dpkg-deb: errore: il sottoprocesso paste è stato terminato dal segnale (Pipe
interrotta)
Si sono verificati degli errori nell'elaborazione:
/var/cache/apt/archives/libfontconfig1-dev_2.13.1-2+b1_i386.deb
E: Sub-process /usr/bin/dpkg returned an error code (1)



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

Kernel: Linux 5.2.0-17.2-liquorix-amd64 (SMP w/4 CPU cores; PREEMPT)
Kernel taint flags: TAINT_OOT_MODULE
Locale: LANG=it_IT.UTF-8, LC_CTYPE=it_IT.UTF-8 (charmap=UTF-8), 
LANGUAGE=it_IT.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages libfontconfig1-dev depends on:
ii  libexpat1-dev 2.2.7-2
ii  libfontconfig12.13.1-2+b1
ii  libfreetype6-dev  2.9.1-4
ii  pkg-config0.29-6
ii  uuid-dev  2.34-0.1

libfontconfig1-dev recommends no packages.

libfontconfig1-dev suggests no packages.

-- no debconf information

Bug#941174: glibc: FTBFS on hppa - new test failures

[John David Anglin]

Source: glibc
Version: 2.29-2
Severity: normal

Dear Maintainer,

Since version 2.29-2, glibc fails to build on hppa.  We have the following
test fails:

+-+
| Encountered regressions that don't match expected failures. |
+-+
FAIL: nptl/tst-cond21
FAIL: nptl/tst-rwlock19
FAIL: nptl/tst-stackguard1
FAIL: nptl/tst-tls1
FAIL: stdio-common/tst-vfprintf-user-type

These fails are not fully consistent from build to build.  2.29-1 built
successfully.

I did a build outside the buildd and all these tests passed.  One test
failed:

+-+
| Encountered regressions that don't match expected failures. |
+-+
FAIL: elf/tst-pldd

dave@mx3210:~/debian/glibc/glibc-2.29$ cat 
./build-tree/hppa-libc/elf/tst-pldd.out
error: xposix_spawn.c:30: posix_spawn to /usr/bin/pldd file failed: No such 
file or directory
error: 1 test failures

It seems like pldd got installed in the wrong place:
mv -f /home/dave/debian/glibc/glibc-2.29/debian/tmp-libc/usr/bin/pldd.new 
/home/dave/debian/glibc/glibc-2.29/debian/tmp-libc/usr/bin/pldd

Regards,
Dave Anglin

-- System Information:
Debian Release: bullseye/sid
  APT prefers buildd-unstable
  APT policy: (500, 'buildd-unstable'), (500, 'unstable')
Architecture: hppa (parisc64)

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

Bug#941173: [golang-1.12] Security patch for HTTP smuggling

[Tim Sattarov]

Package: golang-1.12
Version: 1.12.9-2
Severity: normal
Tags: security
X-Debbugs-CC: secure-testing-t...@lists.alioth.debian.org

--- Please enter the report below this line. ---

Hello,

Golang team recently released new version of Go language fixing HTTP smuggling 
issue.
Details are at the link: https://github.com/golang/go/issues/34541

Thank you

--- System information. ---
Architecture:
Kernel: Linux 5.2.0-2-amd64

Debian Release: bullseye/sid
800 testing mirror.csclub.uwaterloo.ca
800 testing cloudfront.debian.net
500 stretch download.docker.com
500 stable repository.spotify.com
500 stable repo.skype.com
500 stable packages.microsoft.com
500 stable dl.google.com
500 stable artifacts.elastic.co
500 stable apt.agilebits.com
500 kubernetes-xenial apt.kubernetes.io
500 jessie packagecloud.io
500 cosmic brave-browser-apt-release.s3.brave.com
500 cloud-sdk-buster packages.cloud.google.com
500 buster linux.dropbox.com
500 bionic packages.gitlab.com
500 binary pkg.jenkins.io
100 unstable cloudfront.debian.net
100 experimental cloudfront.debian.net

--- Package information. ---
Depends (Version) | Installed
=-+-==
golang-1.12-doc (>= 1.12.9-2) | 1.12.9-2
golang-1.12-go (>= 1.12.9-2) | 1.12.9-2
golang-1.12-src (>= 1.12.9-2) | 1.12.9-2


Package's Recommends field is empty.

Package's Suggests field is empty.

Bug#933469: mrpt: Please rebuild against wxWidgets GTK 3 package

[José Luis Blanco-Claraco]

Hi all,

I'm the maintainer of the upstream library, and have just released
upstream bug-fix release (v1.5.8) which also comes with an updated
debian/control per this original bug report.
It would be great if some of you could sponsor its upload so this bug
gets fixed asap...

The new package for version 1.5.8 has been tested with pbuilder to
build cleanly and to be lintian clean on "sid".
However, I uploaded it twice today to mentors.debian.net without any
error but it won't show on the web... so I'll leave a copy here:

https://ingmec.ual.es/~jlblanco/downloads/mrpt_1.5.8-1.dsc
https://ingmec.ual.es/~jlblanco/downloads/

Cheers,

Bug#764896: sandboxgamemaker: sandbox_unix fails to start, "cannot find core textures"

[Olly Betts]

Control: severity -1 grave

On Thu, Oct 16, 2014 at 08:39:32PM +0100, Anthony F McInerney wrote:
> There was supposed to be information in the README.debian, i must have
> somehow dropped it out. I'll pop that back in there.

Almost 5 years later there's not been another upload and this package is
still in the state where after installing it one will hit this when
trying to actually run it:

could not load texture data/notexture
could not find core textures

There's no useful indication of cause of the problem in the error
message, and no hints in the package description or README.Debian.  Each
user needs to discover for themselves that the solution is to download a
file from upstream and pull it apart as "documented" by comments on this
ancient bug report.

I think the original "grave" severity is justified - in its current
state the sandboxgamemaker package really is "unusable or mostly so".

> I was also supposed to have a script sorted by now to either go with the
> package directly or as another package to download the external data.
> It was all pulled out to make it completely dfsg compliant and hit 'main'.

I think "contrib" is the appropriate section for this package.  Without
the non-free data it seems this package is useless, and policy §2.2.2
says:

The *contrib* archive area contains supplemental packages intended
to work with the Debian distribution, but which require software
outside of the distribution to either build or function.

Including a downloading script for the non-free data should be OK in a
contrib package (provided that script itself is under a DFSG-compatible
licence).

If you've not uploaded in ~5 years because you're no longer interested
in maintaining this package, please orphan the package (or if you don't
know how, just say you want to orphan it and I or somebody else can).

Cheers,
Olly

Bug#940626: uxterm: please lessen dependency on locales

[Thorsten Glaser]

On Tue, 17 Sep 2019, Thomas Dickey wrote:

> > Please apply the following patch (which is _not_ suitable for
> > upstream as the C.UTF-8 locale is my invention and not shipped
> 
> really?

Sure, introduced in eglibc 2.13-1, see #609306 for 240 lynx screen
pages of 113x34 for the discussions around that following my fea‐
ture request for such locale.

> (I forget exactly, but my first sighting of this was from the Cygwin crowd -
> there was a long thread on austin-review a few years later).

After reading your eMail I thought “huh, Cygwin doesn’t have locale
support *at all*” and checked and apparently, they added it in the
1.7 version, which is much more recent (and which I’ve never installed).

> > in all operating systems):
> 
> still, a bad idea regarding interoperability (in case one uses ssh,
> passing the locale settings from one machine to another).

I’ve had enough grief with en_US.{utf8,UTF-8} in mksh’s testsuite
to request a C.UTF-8 locale. Considering “most” remote systems are
Debian or comparable¹ nowadays, locales-all is not normally installed
and d-i does not generate the en_US.UTF-8 locale, a switch to C.UTF-8
would actually i̲m̲p̲r̲o̲v̲e̲ this situation.

① Added to Arch Linux in task 59737, Red Hat BZ#902094, Fedora too,
  and OpenSuSE also carries it… oh, PEP 538 even talks about the
  glibc developers (upstream) “are working towards making the C.UTF-8
  locale universally available”… seems my idea gained traction.

  And many systems just do a !stristr(setlocale(…), "UTF-8").

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

Bug#940034: libelogind0: replacing a core system library and conflicting against the default init considered harmful

[Thorsten Glaser]

On Wed, 25 Sep 2019, Mark Hindley wrote:

> Thanks. Triggers may be an answer to the libsystemd soversion issue.

Mind that anything that runs between unpacking the new libsystemd0
and running the trigger will use libsystemd0 instead of libelogind0.

> > I don’t like this approach.
> 
> In this usage case, I believe I have avoided this being a problem.

I really don’t like it and I believe contrary still, see above.

> The flow to
> switch to libelogind.so goes
> 
>  1) symlink libelogind.so.0 to a temporary file.
>  2) rename temporary file to libsystemd.so.0 (I believe this is atomic).

It is, if the temporary file is housed under the same directory.

>  3) dpkg-divert libsystemd.so.0.26.0 out of the way so ldconfig can't find it.
>  4) Whenever ldconfig runs the manual symlink libsystemd.so.0 -> 
> libelogind.so.0
> is preserved.

The packages ship the symlinks as well though, so each and any update
of libsystemd0 will wreck them.

Oh… and, habe you considered Multi-Arch?

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

Bug#941088: journald fails to restart

[Michael Biebl]

Am 25.09.19 um 14:22 schrieb Jörg Sommer:
> Michael Biebl hat am Mi 25. Sep, 12:33 (+0200) geschrieben:
>> output of
>> systemd-analyze dump
> 
> I've recorded a dump before and after restart. 

Seems to be missing?

One thing I noticed is that you seem to have hit the configured size
limit for the journal. Not sure sure if it's related to your problem but
you might try to reduce the journal size, say to 3G via
journalctl --vacuum-size=3G

(note, this will delete old log entries). So if you are concerned about
that, please backup your journal files beforehand)

-- 
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#941172: /usr/bin/symphony: please compile symphony with USE_GLPMPL

[Rogério Brito]

Package: coinor-symphony
Version: 5.6.16+repack1-1.1
Severity: wishlist
File: /usr/bin/symphony

Hi.

First of all, thank you for packaging mathematical programming software in
Debian.  It is highly appreciated, especially if we want to get rid of
proprietary software in academia.

Unfortunately, though, I tried to use an AMPL file that GLPK is able to use
without problems (example stolen from wikipedia), but when I tried to feed
that very same files to symphony, I got the following output:

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
$ symphony -F foo.ampl -D foo.ampl 

==  Welcome to the SYMPHONY MILP Solver 
==  Copyright 2000-2015 Ted Ralphs and others 
==  All Rights Reserved. 
==  Distributed under the Eclipse Public License 1.0 
==  Version: 5.6.16 
==  Build Date: Jan 11 2019 

Reading input file...

ERROR: SYMPHONY can only read GMPL/AMPL files if GLPK is 
installed and the USE_GLPMPL compiler define is set. 
Exiting.


Fatal errors encountered. Exiting with code -120.
See symphony.h for meaning of code.
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -

Since GLPK is installed in my system, I can only assume that the problem is
the one mentioned in the error message above, namely, that some USE_GLPMLP
define wasn't defined.

Could a new version of symphony and related packages be uploaded with this
feature?


Thanks,

Rogério Brito

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

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

Versions of packages coinor-symphony depends on:
ii  coinor-libcgl1 0.59.10+repack1-2
ii  coinor-libclp1 1.16.11+repack1-2
ii  coinor-libcoinutils3v5 2.10.14+repack1-2
ii  coinor-libosi1v5   0.107.9+repack1-2
ii  coinor-libsymphony35.6.16+repack1-1.1
ii  libatlas3-base [liblapack.so.3]3.10.3-8
ii  libblas3 [libblas.so.3]3.8.0-2
ii  libbz2-1.0 1.0.8-2
ii  libc6  2.29-1
ii  libgcc11:9.2.1-8
ii  liblapack3 [liblapack.so.3]3.8.0-2
ii  libopenblas-base [liblapack.so.3]  0.3.7+ds-1
ii  libstdc++6 9.2.1-8
ii  zlib1g 1:1.2.11.dfsg-1+b1

coinor-symphony recommends no packages.

coinor-symphony suggests no packages.

-- no debconf information

-- 
Rogério Brito : rbrito@{ime.usp.br,gmail.com} : GPG key 4096R/BCFC
http://cynic.cc/blog/ : github.com/rbrito : profiles.google.com/rbrito
DebianQA: http://qa.debian.org/developer.php?login=rbrito%40ime.usp.br

Bug#941130: thunar: delay/hang at startup with lots of files in XDG_TEMPLATES_DIR

[Brice Goglin]

On Wed, Sep 25, 2019 at 08:36:38PM +0200, Yves-Alexis Perez wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA256
> 
> On Wed, 2019-09-25 at 12:49 +0100, Tim Marston wrote:
> > Setting XDG_TEMPLATES_DIR in ~/.config/user-dirs.dirs to point to a
> > directory with a lot of stuff in it (other than $HOME, it seems) causes
> > delays to Thunar startup that can very easily spiral in to minutes,
> > hours...
> > 
> > Issue was not present before xfce 4.14 update.
> 
> Does it depend on the content of the folder? Is there a specific file in that
> folder which makes Thunar choke on it or something? Does stracing the Thunar
> process gives a bit of information?

Hello

I have the same problem with XDG_TEMPLATES_DIR pointing to $HOME/Desktop
(I didn't want random programs to create a useless $HOME/Templates).

I can't find a single file causing the issue, but my home contains some
subdirs with cross-symlinks causing recursive loops (it's basically a copy
of /sys/devices/system/{node,cpu} contents).
Thunar grows to 2GB of resident memory and doesn't seem to ever end
(I killed it after several minutes) with those 2500 files/dirs/symlinks.

If I remove those files and create 100 subdirs with 100 files each,
Thunar starts reasonably quickly (3-4 seconds).
If I create a symlink to a grandparent directory in there, the issue
comes back.

So in my case, it looks like the issue is Thunar not handling recursive
symlinks properly in the template directory.

Brice

Bug#940034: libelogind0: replacing a core system library and conflicting against the default init considered harmful

[Mark Hindley]

On Wed, Sep 25, 2019 at 10:09:15PM +0200, Thorsten Glaser wrote:
> On Wed, 25 Sep 2019, Mark Hindley wrote:
> 
> > libelogind0 can be coninstalled with libsystemd0. However, it is fragile 
> > because
> > the file that needs to be diverted out of the way is libsystemd.so.0.26.0 
> > (the
> > actual library file, not a symlink) otherwise ldconfig will still find it 
> > and
> > create symlinks. However, AFAICS dpkg-divert doesn't accept wildcards and 
> > so if
> > the minor soversion is bumped and a new version of libsystemd0 is 
> > installed, the
> > new file is installed without a divert and ldconfig redirects the symlink.
> 
> Yes, this is not a good idea.
> 
> You could do with a trigger on /usr/lib/ and a wildcard-expanding
> shell loop in postinst, which is also a tad fragile.

Thanks. Triggers may be an answer to the libsystemd soversion issue.

> dpkg-divert also has a small period in which neither is available.
> I don’t like this approach.

In this usage case, I believe I have avoided this being a problem. The flow to
switch to libelogind.so goes

 1) symlink libelogind.so.0 to a temporary file.
 2) rename temporary file to libsystemd.so.0 (I believe this is atomic).
 3) dpkg-divert libsystemd.so.0.26.0 out of the way so ldconfig can't find it.
 4) Whenever ldconfig runs the manual symlink libsystemd.so.0 -> libelogind.so.0
is preserved.

I believe using a temporary file and then renaming means there is no point at
which there is a valid libsystemd.so.0 symlink. But I could be wrong.

This isn't the same as the 'standard' dpkg-divert when a file is moved out of
the way so another can be installed in it's place

Is this still flawed?

Thanks

Mark

Bug#941171: Build-Depends on removed transitional bsdtar binary

[Sebastien Bacher]

Package: mtree-netbsd
Version: 20180822-4

The package currently Build-Depends on bsdtar which got removed from the
archive in a recent libarchive upload
https://packages.qa.debian.org/liba/libarchive/news/20190920T232055Z.html

The attached patch should fix the issue by using the non-transitional
libarchive-tools instead



diff -u mtree-netbsd-20180822/debian/changelog 
mtree-netbsd-20180822/debian/changelog
--- mtree-netbsd-20180822/debian/changelog
+++ mtree-netbsd-20180822/debian/changelog
@@ -1,3 +1,11 @@
+mtree-netbsd (20180822-5) unstable; urgency=medium
+
+  * debian/control:
+- Build-Depends on libarchive-tools instead of the old transitional
+  bsdtar binary which got removed now
+
+ -- Sebastien Bacher   Wed, 25 Sep 2019 23:28:10 +0200
+
 mtree-netbsd (20180822-4) unstable; urgency=low
 
   * Coordinate with libnbcompat-dev v5 libraries
diff -u mtree-netbsd-20180822/debian/control 
mtree-netbsd-20180822/debian/control
--- mtree-netbsd-20180822/debian/control
+++ mtree-netbsd-20180822/debian/control
@@ -2,7 +2,7 @@
 Section: utils
 Priority: optional
 Maintainer: John Goerzen 
-Build-Depends: debhelper (>= 9), autotools-dev, bmake, libnbcompat-dev (>= 
20180822-5), freebsd-buildutils, bsdtar, libncurses-dev, libbsd-dev, libmd-dev
+Build-Depends: debhelper (>= 9), autotools-dev, bmake, libnbcompat-dev (>= 
20180822-5), freebsd-buildutils, libarchive-tools, libncurses-dev, libbsd-dev, 
libmd-dev
 Standards-Version: 3.9.8
 Homepage: 
http://cdn.netbsd.org/pub/pkgsrc/current/pkgsrc/pkgtools/mtree/README.html
 Vcs-Git: https://github.com/jgoerzen/mtree-netbsd.git

Bug#941149: Steam breaks DPMS while running

[Simon McVittie]

On Sat, 21 Sep 2019 at 21:53:26 +0200, Sven Bartscher wrote:
> Apparently when steam is running prevents any DPMS timers to actually
> power down the display.

Debian does not have access to the Steam client's source code, so we
cannot change its behaviour. Please report issues in the proprietary Steam
client to .

Thanks,
smcv

Bug#941169: stretch-pu: package postfix/3.1.12-0+deb9u1

[Scott Kitterman]

Package: release.debian.org
Severity: normal
Tags: stretch
User: release.debian@packages.debian.org
Usertags: pu

As with the 3.4.7 update for buster, I'd like to update the 3.1 series
to 3.1.14 for stretch.  I have this running on multiple systems that I
haven't upgraded yet and it's working fine.  Please see debdiff for
details.  This is mostly a subset of the 3.4.6/3.4.7 changes that apply
to 3.1.

Scott K
diff -Nru postfix-3.1.12/debian/changelog postfix-3.1.14/debian/changelog
--- postfix-3.1.12/debian/changelog 2019-03-25 01:01:51.0 -0400
+++ postfix-3.1.14/debian/changelog 2019-09-23 00:22:15.0 -0400
@@ -1,3 +1,57 @@
+postfix (3.1.14-0+deb9u1) stretch; urgency=medium
+
+  [Wietse Venema]
+
+  * 3.1.13
+- Bugfix (introduced: Postfix 2.3): a censoring filter broke
+  multiline Milter responses for header/body events. Problem
+  report by Andreas Thienemann. Files: util/printable.c,
+  util/stringops.h, smtpd/smtpd.c
+- Workaround for implementations that hang Postfix while
+  shutting down a TLS session, until Postfix times out. With
+  "tls_fast_shutdown_enable = yes" (the default), Postfix no
+  longer waits for the TLS peer to respond to a TLS 'close'
+  request. This is recommended with TLSv1.0 and later. Files:
+  global/mail_params.h, tls/tls_session.c, and documentation.
+- Bugfix (introduced: Postfix 3.0): the code to reset Postfix
+  SMTP server command counts was not called after a HaProxy
+  handshake failure, causing stale numbers to be reported.
+  The command counts are now reset in the function that reports
+  the counts. File: smtpd/smtpd.c
+  * 3.1.14
+- Bugfix: the documentation said tls_fast_shutdown_enable,
+  but the code said tls_fast_shutdown. Viktor Dukhovni. Changed
+  the code because no-one is expected to override the default.
+  File: global/mail_params.h.
+- Workaround for poor TCP loopback performance on LINUX, where
+  getsockopt(..., TCP_MAXSEG, ..) reports a TCP maximal segment
+  size that is 1/2 to 1/3 of the MTU. For example, with kernel
+  5.1.16-300.fc30.x86_64 the TCP client and server announce
+  an mss of 65495 in the TCP handshake, but getsockopt()
+  returns 32741 (less than half). As a matter of principle,
+  Postfix won't turn on client-side TCP_NODELAY because that
+  hides application performance bugs, and because that still
+  suffers from server-side delayed ACKs. Instead, Postfix
+  avoids sending "small" writes back-to-back, by choosing a
+  VSTREAM buffer size that is a multiple of the reported MSS.
+  This workaround bumps the multiplier from 2x to 4x. File:
+  util/vstream_tweak.c.
+- Bugfix (introduced: 20051222): the Dovecot client could
+  segfault (null pointer read) or cause an SMTP server assertion
+  to fail when talking to a fake Dovecot server. The client
+  now logs a proper error instead. Problem reported by Tim
+  Düsterhus. File: xsasl/xsasl_dovecot_server.c.
+- Bitrot: don't invoke SSL_shutdown() when the SSL engine
+  thinks it is processing a TLS handshake. The commit at
+  
https://github.com/openssl/openssl/commit/64193c8218540499984cd63cda41f3cd491f3f59
+  changed the error status, incompatibly, from SSL_ERROR_NONE
+  into SSL_ERROR_SSL. File: tlsproxy/tlsproxxy.c.
+- Bugfix (introduced: Postfix-2.9.0): null pointer read, while
+  logging a warning after a postscreen_command_filter read
+  error. File: postscreen/postscreen_smtpd.c.
+
+ -- Scott Kitterman   Mon, 23 Sep 2019 00:22:15 -0400
+
 postfix (3.1.12-0+deb9u1) stretch; urgency=medium
 
   [Scott Kitterman]
diff -Nru postfix-3.1.12/debian/patches/10_openssl_version_check.diff 
postfix-3.1.14/debian/patches/10_openssl_version_check.diff
--- postfix-3.1.12/debian/patches/10_openssl_version_check.diff 2019-03-25 
01:01:51.0 -0400
+++ postfix-3.1.14/debian/patches/10_openssl_version_check.diff 2019-09-23 
00:22:15.0 -0400
@@ -1,8 +1,8 @@
-Index: postfix-dev/src/tls/tls_misc.c
+Index: postfix/src/tls/tls_misc.c
 ===
 postfix-dev.orig/src/tls/tls_misc.c2019-03-25 01:13:48.562959283 
-0400
-+++ postfix-dev/src/tls/tls_misc.c 2019-03-25 01:15:15.170961131 -0400
-@@ -1252,26 +1252,7 @@
+--- postfix.orig/src/tls/tls_misc.c
 postfix/src/tls/tls_misc.c
+@@ -1255,26 +1255,7 @@ static void tls_version_split(unsigned l
  
  voidtls_check_version(void)
  {
diff -Nru postfix-3.1.12/HISTORY postfix-3.1.14/HISTORY
--- postfix-3.1.12/HISTORY  2019-03-29 08:13:24.0 -0400
+++ postfix-3.1.14/HISTORY  2019-09-21 11:55:11.0 -0400
@@ -22490,3 +22490,72 @@
could exhaust LMTP server resources, resulting in two-second
pauses between email deliveries. This problem was investigated
by Juliana Rodrigueiro. File: smtp/smtp_connect.c.
+
+20190403
+
+

Bug#941168: buster-pu: package postfix/3.4.5-1

[Scott Kitterman]

Package: release.debian.org
Severity: normal
Tags: buster
User: release.debian@packages.debian.org
Usertags: pu

As we've been doing, I'd like to update postfix to the current update in
the 3.4 branch (3.4.7-0+deb10u1).  I've been running 3.4.6 for some time
locally without issue (ran out of tuits to upload to Debian, so we're
going straight to 3.4.7).  I have 3.4.7 running on multiple machines and
there have been no upstream reports of issues.

Please see the attached debdiff for details.

Scott K
diff -Nru postfix-3.4.5/conf/main.cf postfix-3.4.7/conf/main.cf
--- postfix-3.4.5/conf/main.cf  2017-02-18 20:58:20.0 -0500
+++ postfix-3.4.7/conf/main.cf  2019-06-02 08:40:36.0 -0400
@@ -249,7 +249,7 @@
 #
 # By default (mynetworks_style = subnet), Postfix "trusts" SMTP
 # clients in the same IP subnetworks as the local machine.
-# On Linux, this does works correctly only with interfaces specified
+# On Linux, this works correctly only with interfaces specified
 # with the "ifconfig" command.
 # 
 # Specify "mynetworks_style = class" when Postfix should "trust" SMTP
diff -Nru postfix-3.4.5/debian/changelog postfix-3.4.7/debian/changelog
--- postfix-3.4.5/debian/changelog  2019-04-01 13:27:26.0 -0400
+++ postfix-3.4.7/debian/changelog  2019-09-22 22:36:25.0 -0400
@@ -1,3 +1,68 @@
+postfix (3.4.7-0+deb10u1) UNRELEASED; urgency=medium
+
+  [Wietse Venema]
+
+  * 3.4.6
+- Documentation: tlsext_padding is not a tls_ssl_options
+  feature. File: proto/postconf.proto.
+- Portability: added "#undef sun" to util/unix_dgram_connect.c
+  (documented for completeness - no impact on Debian)
+- Bugfix (introduced: Postfix 2.3): a censoring filter broke
+  multiline Milter responses for header/body events. Problem
+  report by Andreas Thienemann. Files: util/printable.c,
+  util/stringops.h, smtpd/smtpd.c
+- Bugfix (introduced: Postfix 3.3): "smtp_mx_address_limit =
+  0" no longer meant 'unlimited'. Problem report by Luc Pardon.
+  File: smtp/smtp_addr.c.
+- Documentation: updated the BUGS section in the smtp(8) manpage
+  about TLS connection reuse. File: smtp/smtp.c.
+- Workaround for implementations that hang Postfix while
+  shutting down a TLS session, until Postfix times out. With
+  "tls_fast_shutdown_enable = yes" (the default), Postfix no
+  longer waits for the TLS peer to respond to a TLS 'close'
+  request. This is recommended with TLSv1.0 and later. Files:
+  global/mail_params.h, tls/tls_session.c, and documentation.
+- Bugfix (introduced: Postfix 3.0): the code to reset Postfix
+  SMTP server command counts was not called after a HaProxy
+  handshake failure, causing stale numbers to be reported.
+  The command counts are now reset in the function that reports
+  the counts. File: smtpd/smtpd.c.
+  * 3.4.7
+- Bugfix: the documentation said tls_fast_shutdown_enable,
+  but the code said tls_fast_shutdown. Viktor Dukhovni. Changed
+  the code because no-one is expected to override the default.
+  File: global/mail_params.h.
+- Workaround for poor TCP loopback performance on LINUX, where
+  getsockopt(..., TCP_MAXSEG, ..) reports a TCP maximal segment
+  size that is 1/2 to 1/3 of the MTU. For example, with kernel
+  5.1.16-300.fc30.x86_64 the TCP client and server announce
+  an mss of 65495 in the TCP handshake, but getsockopt()
+  returns 32741 (less than half). As a matter of principle,
+  Postfix won't turn on client-side TCP_NODELAY because that
+  hides application performance bugs, and because that still
+  suffers from server-side delayed ACKs. Instead, Postfix
+  avoids sending "small" writes back-to-back, by choosing a
+  VSTREAM buffer size that is a multiple of the reported MSS.
+  This workaround bumps the multiplier from 2x to 4x. File:
+  util/vstream_tweak.c.
+- Bugfix (introduced: 20051222): the Dovecot client could
+  segfault (null pointer read) or cause an SMTP server assertion
+  to fail when talking to a fake Dovecot server. The client
+  now logs a proper error instead. Problem reported by Tim
+  Düsterhus. File: xsasl/xsasl_dovecot_server.c.
+- Bugfix (introduced: Postfix 3.4): don't whitewash OpenSSL
+  error results after a plaintext output error. The code could
+  loop, and with some OpenSSL error results could flood the
+  log with error messages (see below for a specific case).
+  Problem reported by Andreas Schulze. File: tlsproxy/tlsproxy.c.
+- Bitrot: don't invoke SSL_shutdown() when the SSL engine
+  thinks it is processing a TLS handshake. The commit at
+  
https://github.com/openssl/openssl/commit/64193c8218540499984cd63cda41f3cd491f3f59
+  changed the error status, incompatibly, from SSL_ERROR_NONE
+  into SSL_ERROR_SSL. File: tlsproxy/tlsproxxy.c.
+
+ -- Scott Kitterman   Sun, 22 Sep 2019 22:36:25 -0400
+
 

Bug#940034: libelogind0: replacing a core system library and conflicting against the default init considered harmful

[Thorsten Glaser]

On Wed, 25 Sep 2019, Sam Hartman wrote:

> Thorsten> dpkg-divert also has a small period in which neither is
> Thorsten> available.  I don’t like this approach.
> 
> Is that only when adding a diversion or when upgrading a diverted file
> each time?

When adding a diversion. dpkg-divert is smart enough that,
when the prerm does NOT remove the diversion (e.g. if you
have it in postrm instead), when the postinst adds it to
make that to a nop.

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

Bug#940034: libelogind0: replacing a core system library and conflicting against the default init considered harmful

[Sam Hartman]

> "Thorsten" == Thorsten Glaser  writes:

Thorsten> On Wed, 25 Sep 2019, Mark Hindley wrote:
>> libelogind0 can be coninstalled with libsystemd0. However, it is
>> fragile because the file that needs to be diverted out of the way
>> is libsystemd.so.0.26.0 (the actual library file, not a symlink)
>> otherwise ldconfig will still find it and create
>> symlinks. However, AFAICS dpkg-divert doesn't accept wildcards
>> and so if the minor soversion is bumped and a new version of
>> libsystemd0 is installed, the new file is installed without a
>> divert and ldconfig redirects the symlink.

Thorsten> dpkg-divert also has a small period in which neither is
Thorsten> available.  I don’t like this approach.

Is that only when adding a diversion or when upgrading a diverted file
each time?

Bug#941167: a2jmidid: new upstream and new upstream version

[Olivier Humbert]

Package: a2jmidid

Dear debian maintainers,

there is a new upstream source point for a2jmidid: 
https://github.com/linuxaudio/a2jmidid/

and this upstream just released a new version ("9") 2 days ago.

Hope that helps.
Olivier

--
Site web : https://librazik.tuxfamily.org/
Donation : https://liberapay.com/LibraZiK/
Diaspora : 
https://framasphere.org/people/8c184af0c9450134f6682a053625

Mastodon : https://mastodon.xyz/@LibraZiK

Bug#875176: [scantailor] Future Qt4 removal from Buster

[Andreas Noteng]

The package for scantailor-advanced is almost done. Since I'm only a DM I'd
need a sponsor for the first upload and (hopefully) someone to grant me
upload privileges for later revisions.
I'll wait for the next upstream release before pushing for a upload. I have
currently packaged for a pre-release.

Andreas

ons. 25. sep. 2019 kl. 20:03 skrev Moritz Mühlenhoff :

> On Tue, Sep 24, 2019 at 03:39:47PM -0600, Jason Crain wrote:
> > On Tue, Sep 24, 2019 at 10:54:01PM +0200, Moritz Mühlenhoff wrote:
> > > per Github issue 121 there's no current activity to port scantailor to
> > > Qt5. Are you planning to switch to the scantailor-advanced fork?
> Otherwise
> > > let's remove it, we're now moving forward with removal of Qt4 from
> Debian
> > > (and all non-ported reverse dependencies left)
> >
> > I will not be working on it, but Andreas Noteng has an ITP for
> > scantailor-advanced (https://bugs.debian.org/940329), which I suggested
> > could be a "Replaces" for scantailor.
>
> Ack, filing a removal bug, then. There's still a lot of time to
> package scantailor-advanced before bullseye freezes.
>
> Cheers,
> Moritz
>

Bug#928520: Provide systemd unit for unclutter

[Jörg Sommer]

Hi Axel,

Axel Beckert hat am Mi 25. Sep, 12:45 (+0200) geschrieben:
> Jörg Sommer wrote:
> > > > and it aggregates all log messages via journal.
> > > 
> > > So far that's the only advantage I see of that .service file.
> > 
> > Another advantage would the possibility to restart unclutter after updates
> > of system libraries. If it aligns this way, *needrestart* shows the
> > unclutter unit, when it needs to be restarted after updates.
> 
> Is needrestart (or needrestart-session) in the meanwhile able to
> restart such user services? IIRC needrestart-session could just inform
> the user about necessary restarts in a pop up notification.

No, this is still not implemented:
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=843778


-- 
Der Pessimist ist jemand, der vorzeitig die Wahrheit erzählt.
(Cyrano de Bergerac)


signature.asc
Description: PGP signature

Bug#940034: libelogind0: replacing a core system library and conflicting against the default init considered harmful

[Thorsten Glaser]

On Wed, 25 Sep 2019, Mark Hindley wrote:

> libelogind0 can be coninstalled with libsystemd0. However, it is fragile 
> because
> the file that needs to be diverted out of the way is libsystemd.so.0.26.0 (the
> actual library file, not a symlink) otherwise ldconfig will still find it and
> create symlinks. However, AFAICS dpkg-divert doesn't accept wildcards and so 
> if
> the minor soversion is bumped and a new version of libsystemd0 is installed, 
> the
> new file is installed without a divert and ldconfig redirects the symlink.

Yes, this is not a good idea.

You could do with a trigger on /usr/lib/ and a wildcard-expanding
shell loop in postinst, which is also a tad fragile.

dpkg-divert also has a small period in which neither is available.
I don’t like this approach.

If it’s just for not switching by accident, the Important: yes
binary control field, which I mentioned in my other mail, is more
apropos.

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

Bug#941048: fwupd: provide option to never send report

[Mario.Limonciello]

> -Original Message-
> From: brian m. carlson 
> Sent: Tuesday, September 24, 2019 5:38 PM
> To: Limonciello, Mario
> Cc: 941...@bugs.debian.org
> Subject: Re: Bug#941048: fwupd: provide option to never send report
> 
> On 2019-09-24 at 02:22:44, mario.limoncie...@dell.com wrote:
> > Oh it looks like that just stops it from actually going out.  To
> > prevent the prompt you'll need to launch fwupdmgr with
> > --no-unreported-check.
> 
> Yes, I appreciate that the command-line option is there.  However, the
> idea is not to need this option every time and to disable the feature
> globally, which is why I opened this bug report.
> --
> brian m. carlson: Houston, Texas, US
> OpenPGP: https://keybase.io/bk2204

OK, 1.3.2 release of fwupd will have this:
https://github.com/fwupd/fwupd/commit/f1accad201b24565f3e19daa09d26b477c3f4b9c

Bug#941160: valgrind: Support multiarch consintallability

[Witold Baryluk]

Package: valgrind
Version: 1:3.15.0-1
Followup-For: Bug #941160

For completness of the bug report, this is what happens today when trying to
coinstall it valgrind:i386 on amd64 with valgrind:amd64

# apt install valgrind:i386
The following additional packages will be installed:
  libc6-dbg:i386 valgrind-dbg:i386
Suggested packages:
  valgrind-mpi:i386 kcachegrind:i386 alleyoop:i386 valkyrie:i386
Recommended packages:
  gdb:i386
The following packages will be REMOVED:
  valgrind valgrind-dbg
The following NEW packages will be installed:
  libc6-dbg:i386 valgrind:i386 valgrind-dbg:i386
0 upgraded, 3 newly installed, 2 to remove and 1 not upgraded.
Need to get 62.6 MB of archives.
After this operation, 57.6 MB disk space will be freed.
Do you want to continue? [Y/n] ^C
#

Best regards,
Witold



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

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

Versions of packages valgrind depends on:
ii  libc6  2.29-2
ii  libc6-dbg  2.29-2

Versions of packages valgrind recommends:
ii  gdb   8.3-1
ii  valgrind-dbg  1:3.15.0-1

Versions of packages valgrind suggests:
pn  alleyoop  
ii  kcachegrind   4:17.08.3-2
pn  valgrind-mpi  
pn  valkyrie  

-- no debconf information

Bug#941161: libgl1-mesa-dri: SIGSEGV on starting X server with libgl1-mesa-dri >18.3.6-2, <=19.1.6-1

[Michel Dänzer]

On 2019-09-25 9:01 p.m., Jim Joyce wrote:
> 
> [47.836] (EE) Backtrace:
> [47.836] (EE) 0: /usr/lib/xorg/Xorg (OsLookupColor+0x139) [0x55ffadbdc2c9]
> [47.837] (EE) 1: /lib/x86_64-linux-gnu/libpthread.so.0 (funlockfile+0x50) 
> [0x7f52f52db55f]
> [47.837] (EE) 2: /usr/lib/xorg/Xorg (xf86ScreenToScrn+0x4) 
> [0x55ffadac62c4]
> [47.838] (EE) unw_get_proc_name failed: no unwind info found [-10]
> [47.838] (EE) 3: /usr/lib/xorg/modules/drivers/amdgpu_drv.so (?+0x0) 
> [0x7f52f4bd6850]
> [47.839] (EE) unw_get_proc_name failed: no unwind info found [-10]
> [47.839] (EE) 4: /usr/lib/xorg/modules/drivers/amdgpu_drv.so (?+0x0) 
> [0x7f52f4bd9540]
> [47.839] (EE) 5: /usr/lib/xorg/Xorg (xorgGetVersion+0x267c) 
> [0x55ffadad135c]
> [47.839] (EE) 6: /usr/lib/xorg/Xorg (AbortDDX+0x82) [0x55ffadabcb62]
> [47.840] (EE) 7: /usr/lib/xorg/Xorg (LogSetParameter+0x92) 
> [0x55ffadbe4952]
> [47.840] (EE) 8: /usr/lib/xorg/Xorg (FatalError+0x119) [0x55ffadbe5769]
> [47.840] (EE) 9: /usr/lib/xorg/Xorg (OsLookupColor+0x181) [0x55ffadbdc311]
> [47.841] (EE) 10: /lib/x86_64-linux-gnu/libpthread.so.0 
> (funlockfile+0x50) [0x7f52f52db55f]
> [47.842] (EE) 11: /lib/x86_64-linux-gnu/libc.so.6 (gsignal+0x141) 
> [0x7f52f5142081]
> [47.843] (EE) 12: /lib/x86_64-linux-gnu/libc.so.6 (abort+0x121) 
> [0x7f52f512d535]
> [47.843] (EE) unw_get_proc_name failed: no unwind info found [-10]
> [47.843] (EE) 13: /lib/x86_64-linux-gnu/libc.so.6 (?+0x0) [0x7f52f512d400]
> [47.843] (EE) 14: /lib/x86_64-linux-gnu/libc.so.6 (__assert_fail+0x42) 
> [0x7f52f513ab92]
> [47.844] (EE) 15: /usr/local/lib/x86_64-linux-gnu/dri/radeonsi_dri.so 
> (u_pipe_screen_get_param_defaults+0x176) [0x7f52f39b46e6]

/usr/local/lib/x86_64-linux-gnu/dri/radeonsi_dri.so presumably isn't
from a Debian package, does moving that away help?


-- 
Earthling Michel Dänzer   |   https://redhat.com
Libre software enthusiast | Mesa and X developer

Bug#941166: prover9-mace4.py is missing

[Will Gnann]

Package: prover9-mace4
Version: 0.5.dfsg-3
Severity: important

Dear Maintainer,

   * What led up to the situation?
 Tried to run prover9-mace4 GUI, but could not find it. I thought it would 
be located at /usr/share/prover9-mace4/lib just like everything else.

   * What exactly did you do (or not do) that was effective (or
 ineffective)?
 Just unpacked prover9-mace4.py from the upstream and made a script to run 
it from /usr/share/prover9-mace4/lib.

   * What was the outcome of this action?
 It solved the problem.

Thank you!

-- System Information:
Debian Release: 10.1
  APT prefers stable-updates
  APT policy: (500, 'stable-updates'), (500, 'stable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

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

Versions of packages prover9-mace4 depends on:
ii  prover9  0.0.200911a-2.1+b2
ii  python   2.7.16-1
ii  python-wxgtk3.0  3.0.2.0+dfsg-8

prover9-mace4 recommends no packages.

prover9-mace4 suggests no packages.

-- no debconf information

Bug#935886: [pkg-bacula-devel] Bug#935886: does not email properly, violating RFC821

[Sven Hartge]

On 25.09.19 21:02, Sven Hartge wrote:
> On 25.09.19 20:23, Antoine Beaupré wrote:

>> And unfortunately, this configuration is shipped in the Debian package,
>> in /usr/share/bacula-common/defconfig/bacula-dir.conf

> I can't find the code in bacula-common_9.4.2-1~bpo9+1

To confirm this, I did a fresh install of
bacula-director/stretch-backports and the bacula-dir.conf is correct.

Unless Peter has more input about the origins of his bacula-dir.conf I
think this has not been a bug for the last 12 years.

Grüße,
Sven.



signature.asc
Description: OpenPGP digital signature

Bug#941162: php-horde-mime: DEP-8 tests fail with error "Class 'Horde_Test_Case' not found".

[Mathieu Parent]

Le mer. 25 sept. 2019 à 21:03, Bryce Harrington
 a écrit :
>
> Package: php-horde-mime
> Version: 2.11.0-2
> Severity: normal
>
> Dear Maintainer,

Thanks for your report.

> php-horde-mime fails its DEP-8 test with the error shown below, on
> ci.debian.net, and similar failure was seen in Ubuntu.
>
> PHP Fatal error:  Uncaught Error: Class 'Horde_Test_Case' not found in 
> /tmp/autopkgtest.WKueSZ/build.G63/src/Horde_Mime-2.11.0/test/Horde/Mime/Filter/EncodingTest.php:26
> Stack trace:
> #0 /usr/share/php/PHPUnit/Util/FileLoader.php(57): include_once()
> #1 /usr/share/php/PHPUnit/Util/FileLoader.php(45): 
> PHPUnit\Util\FileLoader::load('/tmp/autopkgtes...')
> #2 /usr/share/php/PHPUnit/Framework/TestSuite.php(540): 
> PHPUnit\Util\FileLoader::checkAndLoad('/tmp/autopkgtes...')
> #3 /usr/share/php/PHPUnit/Framework/TestSuite.php(618): 
> PHPUnit\Framework\TestSuite->addTestFile('/tmp/autopkgtes...')
> #4 /usr/share/php/PHPUnit/Runner/BaseTestRunner.php(70): 
> PHPUnit\Framework\TestSuite->addTestFiles(Array)
> #5 /usr/share/php/PHPUnit/TextUI/Command.php(183): 
> PHPUnit\Runner\BaseTestRunner->getTest('.', '', Array)
> #6 /usr/share/php/PHPUnit/TextUI/Command.php(162): 
> PHPUnit\TextUI\Command->run(Array, true)
> #7 /usr/bin/phpunit(42): PHPUnit\TextUI\Command::main()
> #8 {main}
>   thrown in 
> /tmp/autopkgtest.WKueSZ/build.G63/src/Horde_Mime-2.11.0/test/Horde/Mime/Filter/EncodingTest.php
>  on line 26
>
> Debian log:
> 
> https://ci.debian.net/data/autopkgtest/unstable/amd64/p/php-horde-mime/3015914/log.gz
> Ubuntu log:
> 
> https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-eoan/eoan/amd64/p/php-horde-mime/20190913_195327_67b6b@/log.gz
>
> I've added a patch in Ubuntu that works around the issue by adding an
> include for AllTests.php.  (Is it possible AllTests.php is supposed to
> be automatically included, yet isn't for some reason?)

This looks like a workaround indeed.

Currently almost all horde packages fails in CI, there is a huge work
here and I need help. I don't want to merge those workaround patches
until we have a summary of the different kind of problems. Also, we
need to work with upstream.

Can Ubuntu help here?

See also : https://salsa.debian.org/groups/horde-team/-/merge_requests

Regards

Mathieu Parent

Bug#941164: gitk: menus showing "tearoff" even though its disabled in the code

[Hans-Christoph Steiner]

Package: gitk
Version: 1:2.20.1-2
Severity: normal

Dear Maintainer,

Using gitk on a pretty plain GNOME setup on Debian/buster, the gitk
app is showing the "tearoff" menu item for all the menus.  It makes it
really annoying to use the menus.  A quick grep shows that gitk's code
disabled it:

 ~ $ grep -i tearoff /usr/bin/gitk
option add *Menu.TearOff 0 startupFile
$rowctxmenu configure -tearoff 0
$fakerowmenu configure -tearoff 0
$headctxmenu configure -tearoff 0
$flist_menu configure -tearoff 0
$diff_menu configure -tearoff 0

screenshot attached.

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

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

Versions of packages gitk depends on:
ii  git  1:2.20.1-2
ii  tk   8.6.9+1

gitk recommends no packages.

Versions of packages gitk suggests:
pn  git-doc  

-- no debconf information

Bug#935886: [pkg-bacula-devel] Bug#935886: does not email properly, violating RFC821

[Sven Hartge]

On 25.09.19 20:23, Antoine Beaupré wrote:

> The safest thing would be to remove all "(Bacula)" stuff from any mailcommand 
> out there.

I agree with your analysis and will look into this in the next days.

Grüße,
Sven.



signature.asc
Description: OpenPGP digital signature

Bug#941163: ghostscript: dvipdf not working

[Alexis Bienvenüe]

Package: ghostscript
Version: 9.28~~rc3~dfsg-1
Severity: normal
Tags: patch upstream

Dear Maintainer,

dvipdf produces an single blank page pdf file whatever the source file is.
The last line of this script needs a dash at the end, that has been dropped
when deprecating the .setpdfwrite operator - see
http://git.ghostscript.com/?p=ghostpdl.git;a=commitdiff;h=15d95340389f0f46bd214803ec19685c0a738a0e

Regards,
Alexis Bienvenüe.



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

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

Versions of packages ghostscript depends on:
ii  libc6   2.29-2
ii  libgs9  9.28~~rc3~dfsg-1

ghostscript recommends no packages.

Versions of packages ghostscript suggests:
pn  ghostscript-x  
Index: ghostscript-9.28~~rc3~dfsg/lib/dvipdf
Description: Fix dvipdf, that produced single blank page output
  whatever the source file is.
===
--- ghostscript-9.28~~rc3~dfsg.orig/lib/dvipdf
+++ ghostscript-9.28~~rc3~dfsg/lib/dvipdf
@@ -43,4 +43,4 @@ fi
 
 # We have to include the options twice because -I only takes effect if it
 # appears before other options.
-exec dvips -Ppdf $DVIPSOPTIONS -q -f "$infile" | $GS_EXECUTABLE $OPTIONS -q 
-P- -dSAFER -dNOPAUSE -dBATCH -sDEVICE=pdfwrite -sstdout=%stderr 
-sOutputFile="$outfile" $OPTIONS
+exec dvips -Ppdf $DVIPSOPTIONS -q -f "$infile" | $GS_EXECUTABLE $OPTIONS -q 
-P- -dSAFER -dNOPAUSE -dBATCH -sDEVICE=pdfwrite -sstdout=%stderr 
-sOutputFile="$outfile" $OPTIONS -

Bug#886974: note to self

[wferi]

A random observation: the segmentation fault happens after outputting
4096 bytes to the test log.  It may be related to stdio buffering and
thus it may never appear with line buffered output.

Bug#935886: [pkg-bacula-devel] Bug#935886: does not email properly, violating RFC821

[Sven Hartge]

On 25.09.19 20:23, Antoine Beaupré wrote:

> And unfortunately, this configuration is shipped in the Debian package,
> in /usr/share/bacula-common/defconfig/bacula-dir.conf

I can't find the code in bacula-common_9.4.2-1~bpo9+1

The code in the file you mentioned is correct:

  mailcommand = "/usr/sbin/bsmtp -h localhost -f \"\(Bacula\) \<%r\>\"
-s \"Bacula: %t %e of %c %l\" %r"
  operatorcommand = "/usr/sbin/bsmtp -h localhost -f \"\(Bacula\)
\<%r\>\" -s \"Bacula: Intervention needed for %j\" %r"

 mailcommand = "/usr/sbin/bsmtp -h localhost -f \"\(Bacula\) \<%r\>\" -s
\"Bacula daemon message\" %r"

And looking at the git history for the source of that file show it was
corrected in 2007 via efbc08878 in version 2.2.0.

I guess the problem here is a very old configuration which has been kept
alive for the last 12 years.

Grüße,
Sven.



signature.asc
Description: OpenPGP digital signature

Bug#941162: php-horde-mime: DEP-8 tests fail with error "Class 'Horde_Test_Case' not found".

[Bryce Harrington]

Package: php-horde-mime
Version: 2.11.0-2
Severity: normal

Dear Maintainer,

php-horde-mime fails its DEP-8 test with the error shown below, on
ci.debian.net, and similar failure was seen in Ubuntu.

PHP Fatal error:  Uncaught Error: Class 'Horde_Test_Case' not found in 
/tmp/autopkgtest.WKueSZ/build.G63/src/Horde_Mime-2.11.0/test/Horde/Mime/Filter/EncodingTest.php:26
Stack trace:
#0 /usr/share/php/PHPUnit/Util/FileLoader.php(57): include_once()
#1 /usr/share/php/PHPUnit/Util/FileLoader.php(45): 
PHPUnit\Util\FileLoader::load('/tmp/autopkgtes...')
#2 /usr/share/php/PHPUnit/Framework/TestSuite.php(540): 
PHPUnit\Util\FileLoader::checkAndLoad('/tmp/autopkgtes...')
#3 /usr/share/php/PHPUnit/Framework/TestSuite.php(618): 
PHPUnit\Framework\TestSuite->addTestFile('/tmp/autopkgtes...')
#4 /usr/share/php/PHPUnit/Runner/BaseTestRunner.php(70): 
PHPUnit\Framework\TestSuite->addTestFiles(Array)
#5 /usr/share/php/PHPUnit/TextUI/Command.php(183): 
PHPUnit\Runner\BaseTestRunner->getTest('.', '', Array)
#6 /usr/share/php/PHPUnit/TextUI/Command.php(162): 
PHPUnit\TextUI\Command->run(Array, true)
#7 /usr/bin/phpunit(42): PHPUnit\TextUI\Command::main()
#8 {main}
  thrown in 
/tmp/autopkgtest.WKueSZ/build.G63/src/Horde_Mime-2.11.0/test/Horde/Mime/Filter/EncodingTest.php
 on line 26

Debian log:

https://ci.debian.net/data/autopkgtest/unstable/amd64/p/php-horde-mime/3015914/log.gz
Ubuntu log:

https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-eoan/eoan/amd64/p/php-horde-mime/20190913_195327_67b6b@/log.gz

I've added a patch in Ubuntu that works around the issue by adding an
include for AllTests.php.  (Is it possible AllTests.php is supposed to
be automatically included, yet isn't for some reason?)

-- 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-62-generic (SMP w/6 CPU cores)
Locale: LANG=C, LC_CTYPE=C (charmap=UTF-8) (ignored: LC_ALL set to 
en_US.UTF-8), LANGUAGE=en_US:en (charmap=UTF-8) (ignored: LC_ALL set to 
en_US.UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages php-horde-mime depends on:
ii  php-common   1:60ubuntu1
pn  php-horde-exception  
pn  php-horde-listheaders
pn  php-horde-mail   
pn  php-horde-stream 
pn  php-horde-stream-filter  
pn  php-horde-support
pn  php-horde-text-flowed
pn  php-horde-translation
pn  php-horde-util   

Versions of packages php-horde-mime recommends:
pn  php-horde-nls  
pn  php-horde-test 
pn  php-horde-text-filter  
pn  php-idn
pn  php-intl   
pn  php-net-dns2   

php-horde-mime suggests no packages.
Description: Fix test failure with "Class 'Horde_Test_Case' not found"
 Explicitly include AllTests.php to fix missing base class issue.  I get
 the impression this should really be automatically included but is not
 in our case.
Author: Bryce Harrington 
Origin: vendor
Last-Update: 2019-09-16

diff -Nurp php-horde-mime-2.11.0/Horde_Mime-2.11.0/test/Horde/Mime/Filter/EncodingTest.php php-horde-mime-2.11.0-fixed/Horde_Mime-2.11.0/test/Horde/Mime/Filter/EncodingTest.php
--- php-horde-mime-2.11.0/Horde_Mime-2.11.0/test/Horde/Mime/Filter/EncodingTest.php	2018-01-14 22:49:19.0 +
+++ php-horde-mime-2.11.0-fixed/Horde_Mime-2.11.0/test/Horde/Mime/Filter/EncodingTest.php	2019-09-13 21:40:17.263283745 +
@@ -1,4 +1,7 @@
 http://www.horde.org/)
  *

Bug#941160: valgrind: Support multiarch consintallability

[Witold Baryluk]

Package: valgrind
Version: 1:3.15.0-1
Severity: normal

Dear Maintainer,

I wish for  valgrind:i386 and valgrind:amd64 to be installable at the same
time, for cross-architecture debugging.

The binary tools, could have prefixes, and the legacy symlinks using alternative
mechanisms.

Headers and documentation should go into arch independent libvalgrind-dev and
libvalgrind/valgrind-doc packages, and manpages should go into corresponding
valgrind:arch package, and by the same on both architectures.

I think header files and the valgrind library should go into a separate package
anyway, becasue it is possible, and common to use valgrind binary without them,
i.e. to debug non-valgrind instrumented binaries, so it doesn't make that much
sense to bundled them into valgrind:arch package.

Thank you.

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

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

Versions of packages valgrind depends on:
ii  libc6  2.29-2
ii  libc6-dbg  2.29-2

Versions of packages valgrind recommends:
ii  gdb   8.3-1
ii  valgrind-dbg  1:3.15.0-1

Versions of packages valgrind suggests:
pn  alleyoop  
ii  kcachegrind   4:17.08.3-2
pn  valgrind-mpi  
pn  valkyrie  

-- no debconf information

Bug#941152: r-doc-html: Format sections are invalid

[Dirk Eddelbuettel]

On 25 September 2019 at 20:14, Davide Prina wrote:
| Package: r-doc-html
| Version: 3.6.1-5
| Severity: normal
| 
| Dear Maintainer,
| 
| upgrading to the last package version I got the following errors:

Yes, I had received a private email about this (or rather the related issue
concerning r-base-html) for 3.6.1-4; and 3.6.1-5 was one (unsuccessful)
attempt in fixing it.  It is due to a change in how the package is built and
shipped, source (now) versus binary (previously). I haven't had time to
squash it.

Dirk

| 
| Processing 7 changed doc-base files...
| Error in `/usr/share/doc-base/r-data', line 9: all `Format' sections are 
| invalid.
| Error in `/usr/share/doc-base/r-ints', line 10: all `Format' sections 
| are invalid.
| Error in `/usr/share/doc-base/r-intro', line 17: all `Format' sections 
| are invalid.
| Error in `/usr/share/doc-base/r-admin', line 9: all `Format' sections 
| are invalid.
| Error in `/usr/share/doc-base/r-faq', line 10: all `Format' sections are 
| invalid.
| Error in `/usr/share/doc-base/r-language', line 11: all `Format' 
| sections are invalid.
| Error in `/usr/share/doc-base/r-extensions', line 11: all `Format' 
| sections are invalid.
| Note: `install-docs --verbose --check file_name' may give more details 
| about the above errors.
| 
| 
| I have try:
| 
| # install-docs --verbose --check /usr/share/doc-base/r-data
| Warning in `/usr/share/doc-base/r-data', line 9: file 
| `/usr/share/doc/r-doc-html/manual/R-data.html' does not exist.
| Error in `/usr/share/doc-base/r-data', line 9: all `Format' sections are 
| invalid.
| /usr/share/doc-base/r-data: Fatal error found, the file won't be registered.
| 
| so I try:
| 
| $ apt-file search /usr/share/doc/r-doc-html/manual/R-data.html
| r-doc-html: /usr/share/doc/r-doc-html/manual/R-data.html
| 
| $ ls -l /usr/share/doc/r-doc-html/manual/R-data.html
| lrwxrwxrwx 1 root root 33 set 20 04:42 
| /usr/share/doc/r-doc-html/manual/R-data.html -> 
| ../../../R/doc/manual/R-data.html
| 
| note that the link above is broken
| 
| $ apt-file search R/doc/manual/R-data.html
| $
| 
| $ apt-file search R-data.html
| r-doc-html: /usr/share/doc/r-doc-html/manual/R-data.html
| 
| $ apt-file search R/doc/manual
| r-base-core: /usr/share/R/doc/manual/images/QQ.png
| r-base-core: /usr/share/R/doc/manual/images/ecdf.png
| r-base-core: /usr/share/R/doc/manual/images/fig11.png
| r-base-core: /usr/share/R/doc/manual/images/fig12.png
| r-base-core: /usr/share/R/doc/manual/images/hist.png
| r-base-core: /usr/share/R/doc/manual/images/ice.png
| 
| So the R-data.html do not exists
| 
| Ciao
| Davide
| 
| -- System Information:
| Debian Release: bullseye/sid
|APT prefers testing-debug
|APT policy: (500, 'testing-debug'), (500, 'testing'), (500, 'stable')
| Architecture: amd64 (x86_64)
| 
| Kernel: Linux 5.2.9-dp-20190826 (SMP w/4 CPU cores; PREEMPT)
| Locale: LANG=it_IT.utf8, LC_CTYPE=it_IT.utf8 (charmap=UTF-8), 
| LANGUAGE=it_IT.utf8 (charmap=UTF-8)
| Shell: /bin/sh linked to /bin/dash
| Init: systemd (via /run/systemd/system)
| LSM: AppArmor: enabled
| 
| r-doc-html depends on no packages.
| 
| r-doc-html recommends no packages.
| 
| Versions of packages r-doc-html suggests:
| ii  epiphany-browser [www-browser]  3.32.1.2-3
| ii  firefox-esr [www-browser]   60.9.0esr-1~deb10u1
| ii  links2 [www-browser]2.20.1-1
| ii  r-base-core 3.6.1-5
| ii  w3m [www-browser]   0.5.3-37+b1
| 
| -- debconf-show failed

-- 
http://dirk.eddelbuettel.com | @eddelbuettel | e...@debian.org

Bug#941159: /usr/bin/find: Allow entry points to be last in the list of arguments, i.e. find -xdev -- /usr

[Witold Baryluk]

Package: findutils
Version: 4.7.0-1
Severity: normal
File: /usr/bin/find

find do have rather annoying behaviour of dealing with entry points:

$ find -xdev -- /usr
find: unknown predicate `--'
$ find -name x -- /usr
find: unknown predicate `--'
$ find -name x /usr
find: paths must precede expression: `/usr'
find: possible unquoted pattern after predicate `-name'?
$ find -xdev /usr
find: paths must precede expression: `/usr'
find: possible unquoted pattern after predicate `-xdev'?
$

That is unfortunate. And always messes me up. Almost all tools in UNIX that can
take multiple raw paths at the end of the argument list, and if needed be used
with --. Not only that, it makes it weird to use find in some reliable scripts.

$ cd /tmp/
/tmp$ mkdir -- --foo
/tmp$ find --foo -type f
find: unknown predicate `--foo'
/tmp$ find -- --foo -type f  # Obviously is not going to work.
find: unknown predicate `--foo'
/tmp$ find ./--foo -type f
/tmp$ find -type f -- --foo
find: unknown predicate `--'
/tmp$ 

The need to use ./ is just a bit silly:

/tmp$ find ./--foo -type f
/tmp$ # WORKS.

I know this is a wishlist, and could possibly break POSIX compatibility, but I
don't see how, and if needed this functionality could be simply enabled via
extra flag or environment variable. There is already POSIXLY_CORRECT which could
be used for this. But the fact, that one could introduce -- to deal with it,
would make it pretty safe.


Thanks.



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

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

Versions of packages findutils depends on:
ii  libc62.29-2
ii  libselinux1  2.9-2+b2

findutils recommends no packages.

Versions of packages findutils suggests:
pn  mlocate | locate  

-- no debconf information

Bug#941158: ITP: sep -- Python and C library for source extraction and photometry

[Christian Dersch]

Package: wnpp
Severity: wishlist
Owner: Christian Dersch 
X-Debbugs-Cc: debian-as...@lists.debian.org, 
debian-de...@lists.debian.org, debian-pyt...@lists.debian.org


Package name:        sep
Version:     1.0.3
Upstream Author: Kyle Barbary
URL: https://github.com/kbarbary/sep
License: LGPL-3.0-or-later
Programming lang:    C, Python
Description: Python and C library for source extraction and photometry


The Debian package will be maintained by the Debian Astro team.

Best Regards,
Christian Dersch

Bug#941130: thunar: delay/hang at startup with lots of files in XDG_TEMPLATES_DIR

[Yves-Alexis Perez]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

On Wed, 2019-09-25 at 12:49 +0100, Tim Marston wrote:
> Setting XDG_TEMPLATES_DIR in ~/.config/user-dirs.dirs to point to a
> directory with a lot of stuff in it (other than $HOME, it seems) causes
> delays to Thunar startup that can very easily spiral in to minutes,
> hours...
> 
> Issue was not present before xfce 4.14 update.

Does it depend on the content of the folder? Is there a specific file in that
folder which makes Thunar choke on it or something? Does stracing the Thunar
process gives a bit of information?

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

iQEzBAEBCAAdFiEE8vi34Qgfo83x35gF3rYcyPpXRFsFAl2Ls7YACgkQ3rYcyPpX
RFvBnAf/Wq5c3eKXnaiX21xD/c5xk+mLivWWOC9uamn+bAYvXQO0m1V79+5cnOxg
f47rXz9SFZCMu3plNmbep4heovY0eOyqHT4PNMGxp94ZLU8FiCWh90MDNPSGPKeb
e9te+VERil4NNgYtPHUsV4QsmQNFIhlNVzFGZiXU22UiPFoxKgTs9GjpVF4kUaZY
Nd/7sWtfWb2TxXpaNz/SApCnEyPQLlIlP8LFVx4+6TTwaLG0d7bOnEZ1ZbB0AVqV
1nEh10CTyjV8DVYzzbr/Jq4f2ByRm7fbwXoXwGH76rh9UDumaQhqO4AbV8mDqEK1
fxUmI59ewSj+0Hzq3zaZNiQyhmwiyQ==
=82YH
-END PGP SIGNATURE-

Bug#941156: guitarix: Typo in the package description

[Thomas Vincent]

Source: guitarix
Severity: minor

Dear Maintainer,

In the last sentence of the long description of guitarix, I believe that the 
word 'as' should be spelled 'has' instead.

Thanks a lot for maintaining guitarix.
Thomas


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

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

Bug#932704: debian-policy: Don't force sysvinit compatibility if e.g. alternate init required

[David Steele]

On Wed, Sep 25, 2019 at 2:00 PM Ansgar  wrote:
>
> Well, the Policy Editors currently see no consensus; so to change it one
> would need to convince them, involve the tech-ctte or a GR.
>

The Policy needs to either explicitly discourage the use of
systemd-specific features, or recognize the sysv-init incompatibility of
packages that use them,

For my part, I have no interest in participating in the init wars. I just
want clear guidance on how to avoid an AUTORM-level bug report.
Right now the Policy is pretty much telling me to add an init script
with calls to systemctl. I'd like a different answer.

Bug#941157: ITP: gatspy -- General tools for Astronomical Time Series in Python

[Christian Dersch]

Package: wnpp
Severity: wishlist
Owner: Christian Dersch 
X-Debbugs-Cc: debian-as...@lists.debian.org, 
debian-de...@lists.debian.org, debian-pyt...@lists.debian.org


Package name:        gatspy
Version:     0.3
Upstream Author:     Jake Vanderplas
URL: http://www.astroml.org/gatspy/
License:         BSD-2-clause
Programming lang:    Python
Description:     General tools for Astronomical Time Series in Python


The Debian package will be maintained by the Debian Astro team.

Best Regards,
Christian Dersch

Bug#935886: does not email properly, violating RFC821

[Antoine Beaupré]

On 2019-08-27 09:57:50, Peter Palfrader wrote:
> Package: bacula-director
> Version: 9.4.2-1
> Severity: normal
>
> This is actually against 9.4.2-1~bpo9+1 on stretch.
>
> With postfix setting strict_rfc821_envelopes = yes and
>
> | root@dictyotum:~# grep bacula-service /etc/bacula/ -r
> | /etc/bacula/bacula-dir.conf:  mail on error = bacula-serv...@torproject.org 
> = all, !skipped
> | /etc/bacula/bacula-dir.conf:  operator = bacula-serv...@torproject.org = 
> mount
> | /etc/bacula/bacula-dir.conf:  mail = bacula-serv...@torproject.org = all, 
> !skipped
>
> emails don't work:
>
> | root@dictyotum:~# cat /var/log/mail.warn-20190827 
> | Aug 26 19:13:40 dictyotum/dictyotum postfix/smtpd[1301]: warning: Illegal 
> address syntax from localhost[127.0.0.1] in MAIL command: <(Bacula) 
> bacula-serv...@torproject.org>

This is actually a problem with the documentation as well. In chapter 22
[Messages Resources][], it says:

mailcommand = "/home/kern/bacula/bin/bsmtp -h mail.example.com -f 
\"\(Bacula\) %r\" -s \"Bacula: %t %e of %c %l\" %r"

[Messages Resources]: 
https://www.bacula.org/9.4.x-manuals/en/main/Messages_Resource.html

And unfortunately, this configuration is shipped in the Debian package,
in /usr/share/bacula-common/defconfig/bacula-dir.conf

We made this patch locally to workaround the problem:

@@ -121,7 +121,7 @@ Messages {
 # Message delivery for daemon messages (no job).
 Messages {
   Name = Daemon
-  mailcommand = "/usr/lib/bacula/bsmtp -h localhost -f \"\(Bacula\) %r\" -s 
\"Bacula daemon message\" %r"
+  mailcommand = "/usr/lib/bacula/bsmtp -h localhost -f \"%r\" -s \"Bacula 
daemon message\" %r"
   mail = <%= @email_daemon %> = all
   console = all, !skipped, !saved
   syslog = all

And `strict_rfc821_envelopes = yes` works again.

Interestingly, the 9.4.4 version might actually be correct, at least in
the manpage, which says:

 mailcommand = "/home/bacula/bin/bsmtp -h mail.domain.com -f 
\"\(Bacula\) \<%r\>\"
  -s \"Bacula: %t %e of %c %l\" %r"
 operatorcommand = "/home/bacula/bin/bsmtp -h mail.domain.com -f 
\"\(Bacula\) \<%r\>\"
-s \"Bacula: Intervention needed for 
%j\" %r"

... but I haven't tested that configuration. The safest thing would be
to remove all "(Bacula)" stuff from any mailcommand out there. Here are
the possibly affected source files:

anarcat@curie:bacula-9.4.4(master)$ grep -r bsmtp.*Bacula
examples/conf/m4.bacula-dir.conf:  mailcommand = "/opt/bacula/sbin/bsmtp -h 
ifm.liu.se -f \"\(Bacula\) bac...@ifm.liu.se\" -s \"Bacula: %t %e of %c %l\" %r"
examples/conf/m4.bacula-dir.conf:  operatorcommand = "/opt/bacula/sbin/bsmtp -h 
ifm.liu.se -f \"\(Bacula\) bac...@ifm.liu.se\" -s \"Bacula: Intervention needed 
for %j\" %r"
.pc/debian/fix-default-config/src/dird/bacula-dir.conf.in:  mailcommand = 
"@sbindir@/bsmtp -h @smtp_host@ -f \"\(Bacula\) \<%r\>\" -s \"Bacula: %t %e of 
%c %l\" %r"
.pc/debian/fix-default-config/src/dird/bacula-dir.conf.in:  operatorcommand = 
"@sbindir@/bsmtp -h @smtp_host@ -f \"\(Bacula\) \<%r\>\" -s \"Bacula: 
Intervention needed for %j\" %r"
.pc/debian/fix-default-config/src/dird/bacula-dir.conf.in:  mailcommand = 
"@sbindir@/bsmtp -h @smtp_host@ -f \"\(Bacula\) \<%r\>\" -s \"Bacula daemon 
message\" %r"
scripts/btraceback.in:| @sbindir@/bsmtp -h @smtp_host@ -f @dump_email@ -s 
"Bacula DBX traceback of ${PNAME}" @dump_email@
scripts/btraceback.in:| @sbindir@/bsmtp -h @smtp_host@ -f @dump_email@ -s 
"Bacula GDB traceback of ${PNAME}" @dump_email@
manpages/bsmtp.1: bsmtp \- Bacula's SMTP client (mail submission program)
manpages/bsmtp.1:  mailcommand = "/home/bacula/bin/bsmtp \-h mail.domain.com 
\-f \\"\\(Bacula\\) \\<%r\\>\\"
manpages/bsmtp.1:  operatorcommand = "/home/bacula/bin/bsmtp \-h 
mail.domain.com \-f \\"\\(Bacula\\) \\<%r\\>\\"
src/win32/full_win32_installer/bacula-dir.conf.in:  mailcommand = 
"\"@bin_dir@\\bsmtp\" -h @smtp_host@ -f \"\(Bacula\) %r\" -s \"Bacula: %t %e of 
%c %l\" %r"
src/win32/full_win32_installer/bacula-dir.conf.in:  operatorcommand = 
"\"@bin_dir@\\bsmtp\" -h @smtp_host@ -f \"\(Bacula\) %r\" -s \"Bacula: 
Intervention needed for %j\" %r"
src/win32/full_win32_installer/bacula-dir.conf.in:  mailcommand = 
"\"@bin_dir@\\bsmtp\" -h @smtp_host@ -f \"\(Bacula\) %r\" -s \"Bacula daemon 
message\" %r"
src/win32/win64_installer/bacula-dir.conf.in:  mailcommand = 
"\"@bin_dir@\\bsmtp\" -h @smtp_host@ -f \"\(Bacula\) %r\" -s \"Bacula: %t %e of 
%c %l\" %r"
src/win32/win64_installer/bacula-dir.conf.in:  operatorcommand = 
"\"@bin_dir@\\bsmtp\" -h @smtp_host@ -f \"\(Bacula\) %r\" -s \"Bacula: 
Intervention needed for %j\" %r"
src/win32/win64_installer/bacula-dir.conf.in:  mailcommand = 
"\"@bin_dir@\\bsmtp\" -h @smtp_host@ -f \"\(Bacula\) %r\" -s \"Bacula daemon 
message\" %r"
src/win32/win32_installer/bacula-dir.conf.in:  mailcommand = 
"\"@bin_dir@\\bsmtp\" -h @smtp_host@ -f \"\(Bacula\) %r\" -s \"Bacula: %t %e of 
%c %l\" %r"

Bug#941155: choqok FTBFS: error: field ‘accountsList’ has incomplete type ‘QMap’

[Helmut Grohne]

Source: choqok
Version: 1.6-2.1
Severity: serious
Tags: ftbfs

choqok fails to build from source in unstable on amd64. The relevant
error from the compiler is:

| In file included from /<>/plugins/betternotify/notify.cpp:24:
| /<>/plugins/betternotify/notify.h:61:32: error: field 
‘accountsList’ has incomplete type ‘QMap’
|61 | QMap accountsList;
|   |^~~~
| In file included from /usr/include/x86_64-linux-gnu/qt5/QtCore/qglobal.h:1194,
|  from 
/usr/include/x86_64-linux-gnu/qt5/QtCore/qalgorithms.h:43,
|  from /usr/include/x86_64-linux-gnu/qt5/QtCore/qlist.h:43,
|  from /usr/include/x86_64-linux-gnu/qt5/QtCore/qqueue.h:43,
|  from /usr/include/x86_64-linux-gnu/qt5/QtCore/QQueue:1,
|  from /<>/plugins/betternotify/notify.h:26,
|  from /<>/plugins/betternotify/notify.cpp:24:
| /usr/include/x86_64-linux-gnu/qt5/QtCore/qtypeinfo.h:221:1: note: declaration 
of ‘class QMap’
|   221 | Q_DECLARE_MOVABLE_CONTAINER(QMap);
|   | ^~~

Helmut

Bug#941154: RM: docbook2odf -- RoQA; Unmaintained, RC-buggy

[Moritz Muehlenhoff]

Package: ftp.debian.org
Severity: normal

Please see #934935:
It's unmaintained (last maintainer upload in 2007), last upload in 2010
and has been dropped from testing for three years now.

Cheers,
Moritz

Bug#941119: [Pkg-javascript-devel] Bug#941119: add-node-component is broken - Malformed upstream registry

[Xavier]

Le 25/09/2019 à 09:40, Pirate Praveen a écrit :
> package: pkg-js-tools
> version: 0.9.13
> sevrrity: important
> 
> $ add-node-component -if sha1
> Thread 1 terminated abnormally: Malformed upstream registry: JSON text
> must be an object or array (but found number, string, true, false or
> null, use allow_nonref to allow this) at /usr/share/perl5/JSON.pm line 187.
> Component sha1 not found in npm registry at /usr/bin/add-node-component
> line 173.

Hi,

this is not really a bug but a debug of bad NPM registry response. This
happens sometime...

Bug#941153: RM: manpages-es -- RoQA; totally outdated manpages, unmaintained

[Moritz Muehlenhoff]

Package: ftp.debian.org
Severity: normal

Please see #934248: The manpages are completely outdated, the
last release of manpages-es was in 2005 and the last upload in 2011.

Cheers,
Moritz



 

Bug#932704: debian-policy: Don't force sysvinit compatibility if e.g. alternate init required

[David Steele]

On Wed, Sep 25, 2019 at 12:18 PM Ansgar  wrote:
>
> Hi,
>
> On Sun, 2019-09-22 at 16:13 -0400, David Steele wrote:
> > On Tue, Jul 23, 2019 at 2:10 PM Sean Whitton  
> > wrote:
> > > The Policy Editors have decided that dropping the requirement to ship
> > > init scripts is not something that can be decided by means of the Policy
> > > Changes Process, at least for the time being.
> > >
> > > In proposing and reviewing wording to resolve this bug, then, we should
> > > be careful not to weaken the requirement to ship init scripts.
> > > Otherwise, in resolving this bug we would be changing the requirements
> > > to ship init scripts by means of the Policy Changes Process.
> > >
> > > I'm suggesting this be kept in mind.  It need not result in a wordier
> > > change, and I certainly agree with you that we should assume good faith
> > > on the part of package maintainers.
> > >
> >
> > Candidate language attached. It adds "Also excepted are packages which 
> > require a
> > feature of an alternate init system which is not available in SysV-Style
> > init systems.". Thoughts?
>
> I don't think there is a way to get such changes through the policy
> process as Sean said (I tried to document what I see as current
> practice in #911165).  Practically the project seems to have already
> decided that this is fine, even for packages that don't require
> systemd:
>
> +---
> | There are 1033 non-overridden instances of lintian detecting a
> | service unit without an init.d script [7].
> +---[ https://lists.debian.org/debian-devel-announce/2019/09/msg1.html ]
>
> Ansgar
>

Regardless of the practicality, I'd like clarity on the policy.

After reading #911165, I'd say I prefer it to this proposal. But something
needs to be done about the current alternate init system support
language.

Bug#941150: transition: nettle

[Magnus Holmgren]

Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: transition

Apologies for getting carried away and uploading straight to sid earlier. I'm 
not used to having so many reverse dependencies...

Here's the NEWS for the Nettle 3.5 release from upstream:

This release adds a couple of new features and optimizations,
and deletes or deprecates a few obsolete features. It is *not*
binary (ABI) compatible with earlier versions. Except for
deprecations listed below, it is intended to be fully
source-level (API) compatible with Nettle-3.4.1.

The shared library names are libnettle.so.7.0 and
libhogweed.so.5.0, with sonames libnettle.so.7 and
libhogweed.so.5.

[...]

Deleted features:

* The header file des-compat.h and everything declared therein
  has been deleted, as announced earlier. This file provided a
  subset of the old libdes/ssleay/openssl interface for DES
  and triple-DES. DES is still supported, via the functions
  declared in des.h.

* Functions using the old struct aes_ctx have been marked as
  deprecated. Use the fixed key size interface instead, e.g.,
  struct aes256_ctx, introduced in Nettle-3.0.

* The header file nettle-stdint.h, and corresponding autoconf
  tests, have been deleted. Nettle now requires that the
  compiler/libc provides .

Miscellaneous:

* Support for big-endian ARM systems, contributed by Michael
  Weiser.

* The programs aesdata, desdata, twofishdata, shadata and
  gcmdata are no longer built by default. Makefile
  improvements contributed by Jay Foad.

* The "example" program examples/eratosthenes.c has been
  deleted.

* The contents of hash context structs, and the deprecated
  aes_ctx struct, have been reorganized, to enable later
  optimizations.

The shared library names are libnettle.so.7.0 and
libhogweed.so.5.0.


I've tried building all reverse dependencies with the new version and found the 
following packages needing changes:

dnsmasq (bug filed, simple fix)
unbound (bug filed, simple fix)
rdup (bug filed, a bit more involved fix)
A few other packages FTBFS for other reasons: ocamlnet, libstorj (bug filed), 
lsh-utils (mine, fails tests)

Ben file:

title = "nettle";
is_affected = .depends ~ /libnettle6|libhogweed4/ | .depends ~ 
/libnettle7|libhogweed5/;
is_good = .depends ~ /libnettle7|libhogweed5/;
is_bad = .depends ~ /libnettle6|libhogweed4/;

Bug#941152: r-doc-html: Format sections are invalid

[Davide Prina]

Package: r-doc-html
Version: 3.6.1-5
Severity: normal

Dear Maintainer,

upgrading to the last package version I got the following errors:

Processing 7 changed doc-base files...
Error in `/usr/share/doc-base/r-data', line 9: all `Format' sections are 
invalid.
Error in `/usr/share/doc-base/r-ints', line 10: all `Format' sections 
are invalid.
Error in `/usr/share/doc-base/r-intro', line 17: all `Format' sections 
are invalid.
Error in `/usr/share/doc-base/r-admin', line 9: all `Format' sections 
are invalid.
Error in `/usr/share/doc-base/r-faq', line 10: all `Format' sections are 
invalid.
Error in `/usr/share/doc-base/r-language', line 11: all `Format' 
sections are invalid.
Error in `/usr/share/doc-base/r-extensions', line 11: all `Format' 
sections are invalid.
Note: `install-docs --verbose --check file_name' may give more details 
about the above errors.



I have try:

# install-docs --verbose --check /usr/share/doc-base/r-data
Warning in `/usr/share/doc-base/r-data', line 9: file 
`/usr/share/doc/r-doc-html/manual/R-data.html' does not exist.
Error in `/usr/share/doc-base/r-data', line 9: all `Format' sections are 
invalid.

/usr/share/doc-base/r-data: Fatal error found, the file won't be registered.

so I try:

$ apt-file search /usr/share/doc/r-doc-html/manual/R-data.html
r-doc-html: /usr/share/doc/r-doc-html/manual/R-data.html

$ ls -l /usr/share/doc/r-doc-html/manual/R-data.html
lrwxrwxrwx 1 root root 33 set 20 04:42 
/usr/share/doc/r-doc-html/manual/R-data.html -> 
../../../R/doc/manual/R-data.html


note that the link above is broken

$ apt-file search R/doc/manual/R-data.html
$

$ apt-file search R-data.html
r-doc-html: /usr/share/doc/r-doc-html/manual/R-data.html

$ apt-file search R/doc/manual
r-base-core: /usr/share/R/doc/manual/images/QQ.png
r-base-core: /usr/share/R/doc/manual/images/ecdf.png
r-base-core: /usr/share/R/doc/manual/images/fig11.png
r-base-core: /usr/share/R/doc/manual/images/fig12.png
r-base-core: /usr/share/R/doc/manual/images/hist.png
r-base-core: /usr/share/R/doc/manual/images/ice.png

So the R-data.html do not exists

Ciao
Davide

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

Kernel: Linux 5.2.9-dp-20190826 (SMP w/4 CPU cores; PREEMPT)
Locale: LANG=it_IT.utf8, LC_CTYPE=it_IT.utf8 (charmap=UTF-8), 
LANGUAGE=it_IT.utf8 (charmap=UTF-8)

Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

r-doc-html depends on no packages.

r-doc-html recommends no packages.

Versions of packages r-doc-html suggests:
ii  epiphany-browser [www-browser]  3.32.1.2-3
ii  firefox-esr [www-browser]   60.9.0esr-1~deb10u1
ii  links2 [www-browser]2.20.1-1
ii  r-base-core 3.6.1-5
ii  w3m [www-browser]   0.5.3-37+b1

-- debconf-show failed

Bug#941151: RM: scantailor -- RoQA; Depends on Qt4, dead upstream

[Moritz Muehlenhoff]

Package: ftp.debian.org
Severity: normal

Please remove scantailor. It depends on Qt4 and is dead upstream (but there's
a separate scantailor-advanced fork, which is ITPd at 940329)

Cheers,
Moritz

Bug#932704: debian-policy: Don't force sysvinit compatibility if e.g. alternate init required

[Ansgar]

David Steele writes:
> On Wed, Sep 25, 2019 at 12:18 PM Ansgar  wrote:
>> I don't think there is a way to get such changes through the policy
>> process as Sean said (I tried to document what I see as current
>> practice in #911165).  Practically the project seems to have already
>> decided that this is fine, even for packages that don't require
>> systemd:
>>
>> +---
>> | There are 1033 non-overridden instances of lintian detecting a
>> | service unit without an init.d script [7].
>> +---[ https://lists.debian.org/debian-devel-announce/2019/09/msg1.html ]
>
> Regardless of the practicality, I'd like clarity on the policy.
>
> After reading #911165, I'd say I prefer it to this proposal. But something
> needs to be done about the current alternate init system support
> language.

Well, the Policy Editors currently see no consensus; so to change it one
would need to convince them, involve the tech-ctte or a GR.

I have no intention to escalate this, but out of curiosity asked some
people.  From my understanding the ctte would prefer not having to deal
with this (which I can understand given the default init discussion); I
think this might also be true for Policy Editors.  GRs are unpopular
too.

Ansgar

Bug#875176: [scantailor] Future Qt4 removal from Buster

[Moritz Mühlenhoff]

On Tue, Sep 24, 2019 at 03:39:47PM -0600, Jason Crain wrote:
> On Tue, Sep 24, 2019 at 10:54:01PM +0200, Moritz Mühlenhoff wrote:
> > per Github issue 121 there's no current activity to port scantailor to
> > Qt5. Are you planning to switch to the scantailor-advanced fork? Otherwise
> > let's remove it, we're now moving forward with removal of Qt4 from Debian
> > (and all non-ported reverse dependencies left)
> 
> I will not be working on it, but Andreas Noteng has an ITP for
> scantailor-advanced (https://bugs.debian.org/940329), which I suggested
> could be a "Replaces" for scantailor.

Ack, filing a removal bug, then. There's still a lot of time to
package scantailor-advanced before bullseye freezes.

Cheers,
Moritz

Bug#941134: bacula-director-mysql: Script grant_mysql_privileges always set password XXX_DBPASSWORD_XXX

[Sven Hartge]

On Wed, 25 Sep 2019 14:53:32 +0200 Hostinet  wrote:

> Script /usr/share/bacula-director/grant_mysql_privileges line 11:
> db_password=XXX_DBPASSWORD_XXX

This script (or any other script /usr/share/bacula-director/) in is
never used by Debian to setup the database or grant MySQL permissions,
so the template password in there is no problem or risk.

The scripts in /usr/share/bacula-director/ serve as an example for the
administrator on how to setup the database manually, if they so choose.
In that case the administrator is expected to edit the scripts to suit
their needs.

On the other hand, if the template password would be automatically
replaced by the password chosen (or autogenerated) during the package
installation, it would be world-readable, creating a security problem.

Grüße,
Sven.



signature.asc
Description: OpenPGP digital signature

Bug#940034: libelogind0: replacing a core system library and conflicting against the default init considered harmful

[Mark Hindley]

On Mon, Sep 23, 2019 at 04:16:05PM -0400, Sam Hartman wrote:
> Mark> Anyway, I am happy to try to work up a dpkg-divert solution if
> Mark> that is likely to be more acceptable.
> 
> I don't know if it will be.
> I'm trying to be a facilitator here and make sure all sides understand
> each other.
> 
> So, the advantage of the dpkg-divert approach seems to me to be that if
> you never turn it on, it can't hurt you.
> So, for example, if you do more than install a package to trigger it, it
> could be very safe for the systemd user.
> 
> Even if you trigger from the elogind postinst, that's probably OK so
> long as very little hard depends on elogind.
> 
> The disadvantages are:
> 
> 1) Making sure you never get into a situation where you try to boot
> systemd with libelogind0.  Assuming you can dpkg-divert a symlink, you
> can presumably manage the /sbin/init link, but you cannot stop someone
> from init=/bin/systemd with libelogind0 as libsystemd0.  Although
> systemd doesn't actually link to libsystemd0, so perhaps that's not
> quite as bad as I thought, although I'm sure it isn't good..  (You may
> not need to stop this: it's a disadvantage, and sometimes the chosen
> solution has disadvantages).
> 
> 2) There was FUD about dpkg-divert being inappropriate for critical
> system functions.  I don't know whether this is still true or how big of
> a deal it is.  But for example if things are in an inconsistent state on
> upgrade between unpack phase and configure phase, that might be a
> disadvantage.  Basically, I think it's probably fine if the initial
> diversion has some fragility (where if your system crashes at that one
> point, recovery is hard).  I think it's less amazing if every time you
> upgrade systemd, elogind or similar, there is fragility.

I have got a PoC dpkg-divert solution working.  The divert created in
elogind.postinst and removed in elogind.prerm. The libsystemd.so compatibility
symlink is also handled there. It works as far as it goes and it means that
libelogind0 can be coninstalled with libsystemd0. However, it is fragile because
the file that needs to be diverted out of the way is libsystemd.so.0.26.0 (the
actual library file, not a symlink) otherwise ldconfig will still find it and
create symlinks. However, AFAICS dpkg-divert doesn't accept wildcards and so if
the minor soversion is bumped and a new version of libsystemd0 is installed, the
new file is installed without a divert and ldconfig redirects the symlink.

I can't work out a way around this at the moment, but any suggestions are
welcome.

Thanks

Mark

Bug#939738: buster-pu: package aegisub/3.2.2+dfsg-4+deb10u1

[Aniol Marti]

Control: tags -1 - moreinfo

The bug has been fixed in unstable. Please, allow us to fix it in Buster.

Thanks,
Aniol

Bug#941149: Steam breaks DPMS while running

[Sven Bartscher]

Package: steam
Version: 1.0.0.61-2
Severity: normal

Apparently when steam is running prevents any DPMS timers to actually
power down the display. I think this is might be considered a feature
in some situations where the display is supposed to stay on, but for
me steam keeps the display on when it is just minimized into the
system tray, so there is literally nothing that steam might show me
that would justify keeping the display from going into standby.

I used these steps to reproduce the problem:

* Steam is not running
* Run `xset dpms 0 0 5` to be able to quickly tell if dpms still works
  (it does at this point)
* Start steam and wait for it to minimize into the system tray (dpms
  still works)
* Open the steam library from the system tray
* DPMS doesn't trigger anymore

At this point DPMS doesn't trigger based on time anymore. Minimizing
steam doesn't make it work again. The only way I found to make DPMS
work again is to close steam completely.

Apparently this only affects time based DPMS. Using
`xset dpms force *` still works as expected.

I'm running steam in XFCE with xmonad instead of xfwm.

-- System Information:
Debian Release: bullseye/sid
  APT prefers testing-debug
  APT policy: (990, 'testing-debug'), (990, 'testing'), (102, 
'unstable-debug'), (102, 'unstable'), (101, 'experimental-debug'), (101, 
'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

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

Versions of packages steam depends on:
ii  debconf [debconf-2.0]  1.5.73
ii  libc6  2.29-1
ii  libgl1-mesa-dri19.1.6-1
ii  libgl1-mesa-glx19.1.6-1
ii  libgpg-error0  1.36-7
ii  libstdc++6 9.2.1-8
ii  libudev1   242-7
ii  libx11-6   2:1.6.7-1
ii  libxcb-dri3-0  1.13.1-2
ii  libxinerama1   2:1.1.4-2
ii  xz-utils   5.2.4-1+b1

Versions of packages steam recommends:
ii  ca-certificates   20190110
ii  fontconfig2.13.1-2+b1
ii  fonts-liberation  1:1.07.4-10
ii  libxss1   1:1.2.3-1
ii  mesa-vulkan-drivers   19.1.6-1
ii  steam-devices 1.0.0.61-2
ii  xfce4-terminal [x-terminal-emulator]  0.8.8-1+b1
ii  xterm [x-terminal-emulator]   348-2

Versions of packages steam suggests:
ii  nvidia-driver-libs-i386  430.40-2
ii  nvidia-vulkan-icd430.40-2

Versions of packages steam is related to:
ii  libc6   2.29-1
ii  libgl1  1.1.0-1+b1
ii  libgl1-mesa-dri 19.1.6-1
ii  libglx-mesa0 [libglx-vendor]19.1.6-1
ii  libglx-nvidia0 [libglx-vendor]  430.40-2
ii  libxcb-dri3-0   1.13.1-2
ii  nvidia-driver   430.40-2
ii  nvidia-driver-libs  430.40-2
ii  nvidia-driver-libs-i386 430.40-2

-- debconf information:
* steam/question: I AGREE
* steam/license:
  steam/purge:
  steam/need-nvidia-i386:

-- debsums errors found:
debsums: package steam is not installed

Bug#941148: alpine incorrectly reporting server name does not match certificate.

[Tim Woodall]

Package: alpine
Version: 2.21+dfsg1-1.1
Severity: normal

Dear Maintainer,

This issue occurs when you use alpine in buster to connect (to an imap
server running on squeeze). alpine in squeeze does not have the issue
when connecting to the same imap server.

Initially I was getting certificate name mismatches when alpine
attempted to connect to my imap server. I resolved them by adding a
Subject Alternative Name that matched the Common Name.

However, I still get the certificate name mismatch when I try to send an
email (which can then be ignored)

# openssl x509 -in imapd.pem -noout -text
Certificate:
Data:
Version: 3 (0x2)
Serial Number: 1044 (0x9896ac)
Signature Algorithm: sha256WithRSAEncryption
Issuer: C = GB, ST = London, O = Certificate Authority, CN = Tim 
Woodall CA
Validity
Not Before: Sep 15 13:20:28 2019 GMT
Not After : Sep 14 13:20:28 2020 GMT
Subject: C = GB, ST = London, O = Tim Woodall, CN = 
einstein.home.woodall.me.uk, emailAddress = *
Subject Public Key Info:
Public Key Algorithm: rsaEncryption
Public-Key: (2048 bit)
Modulus:

Exponent: 65537 (0x10001)
X509v3 extensions:
X509v3 Subject Alternative Name: 
DNS:einstein.home.woodall.me.uk
Signature Algorithm: sha256WithRSAEncryption



There was a failure validating the SSL/TLS certificate for the server
einstein.home.woodall.me.uk
The reason for the failure was
  Server name does not match certificate 
(details)

Host given by user:
  einstein.home.woodall.me.uk
Reason for failure:
  Server name does not match certificate
Certificate being verified:
  /C=GB/ST=London/O=Tim 
Woodall/CN=einstein.home.woodall.me.uk/emailAddress=**



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

Kernel: Linux 4.19.0-6-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_GB.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: sysvinit (via /sbin/init)

Versions of packages alpine depends on:
ii  libc6 2.28-10
ii  libgssapi-krb5-2  1.17-3
ii  libkrb5-3 1.17-3
ii  libldap-2.4-2 2.4.47+dfsg-3+deb10u1
ii  libpam0g  1.3.1-5
ii  libssl1.1 1.1.1c-1
ii  libtinfo6 6.1+20181013-2+deb10u1
ii  mlock 8:2007f~dfsg-6

Versions of packages alpine recommends:
pn  alpine-doc  

Versions of packages alpine suggests:
ii  aspell0.60.7~20110707-6
pn  mail-transport-agent | exim4  

-- no debconf information

Bug#934386: Bug#894663: transition: wxwidgets3.0

[Olly Betts]

[Moving this thread from bug #894663 to #934386]

On Mon, Sep 16, 2019 at 10:43:20PM +0100, Olly Betts wrote:
> On Mon, Sep 16, 2019 at 09:25:54AM -0400, Scott Talbert wrote:
> > On Mon, 16 Sep 2019, Gunter Königsmann wrote:
> > > Currently I am playing with the thought if the right idea would be
> > > uploading a wxMaxima version that uses GTK3 to debian testing and
> > > looking if anyone except Vadim and me is affected by the bug.
> 
> Note you don't upload to testing - you upload to unstable, and then
> the package migrates to testing.
> 
> I think this is probably a good idea.  It seems there's something system
> dependent here since wxmaxima rebuilt to use GTK3 doesn't seem to
> flicker when scrolling horizontally or vertically to me, and so allowing
> easy wider testing would be helpful in trying to work out what's going
> on.

So, are you going to upload an updated wxmaxima to unstable?

Or would you like me to NMU?  I already have a test build of a fixed
wxmaxima package so I easily can if your limited laptop battery
situation is the obstacle.

Also, is this bug (#934386) specific to X11?  A comment you made
elsewhere seemed to imply it is which is rather important information,
but X11 vs wayland isn't mentioned here at all, and only tangentially in
the upstream ticket.

Cheers,
Olly

Bug#941145: mark freeipmi-common Multi-Arch: foreign

[Helmut Grohne]

Package: freeipmi-common
Version: 1.6.3-1.1
Tags: patch
User: debian-cr...@lists.debian.org
Usertags: cross-satisfiability
Control: affects -1 + src:conman src:ipmitool src:nut src:slurm-llnl

The affected packages fail to satisfy their cross Build-Depends, because
their transitive dependency on freeipmi-common is unsatisfiabile. In
general, Architecture: all packages can never satisfy cross
Build-Depends unless marked Multi-Arch: foreign or annotated :native. In
this case, the foreign marking is reasonable, because freeipmi-common
lacks dependencies and its maintainer scripts don't have
architecture-specific behaviour. Please consider applying the attached
patch.

Helmut
diff --minimal -Nru freeipmi-1.6.3/debian/changelog 
freeipmi-1.6.3/debian/changelog
--- freeipmi-1.6.3/debian/changelog 2019-02-23 14:06:54.0 +0100
+++ freeipmi-1.6.3/debian/changelog 2019-09-25 18:35:52.0 +0200
@@ -1,3 +1,10 @@
+freeipmi (1.6.3-1.2) UNRELEASED; urgency=medium
+
+  * Non-maintainer upload.
+  * Mark freeipmi-common Multi-Arch: foreign. (Closes: #-1)
+
+ -- Helmut Grohne   Wed, 25 Sep 2019 18:35:52 +0200
+
 freeipmi (1.6.3-1.1) unstable; urgency=high
 
   * Non-maintainer upload.
diff --minimal -Nru freeipmi-1.6.3/debian/control freeipmi-1.6.3/debian/control
--- freeipmi-1.6.3/debian/control   2019-02-02 15:50:10.0 +0100
+++ freeipmi-1.6.3/debian/control   2019-09-25 18:35:50.0 +0200
@@ -14,6 +14,7 @@
 
 Package: freeipmi-common
 Architecture: all
+Multi-Arch: foreign
 Depends: ${misc:Depends}
 Pre-Depends: dpkg (>=1.15.7.2~)
 Suggests: freeipmi-tools

Bug#941146: mark libtss2-udev Multi-Arch: foreign

[Helmut Grohne]

Package: libtss2-udev
Version: 2.1.0-4
Tags: patch
User: debian-cr...@lists.debian.org
Usertags: cross-satisfiability
Control: affects -1 + src:openconnect src:tpm2-abrmd src:tpm2-tools src:clevis 
src:connman-gtk src:network-manager-openconnect src:plasma-nm 
src:tpm2-initramfs-tool

The affected packages fail to satisfy their cross Build-Depends, because
their transitive dependency on libtss2-udev is unsatisfiably. In
general, Architecture: all packages can never satisfy cross build
dependencies unless marked Multi-Arch: foreign or annotated :native. In
this case, the foreign marking is reasonable as libtss2-udev only ships
(textual) rules, its adduser dependency is Multi-Arch: foreign and its
maintainer script does not have architecture-dependent behaviour. Please
consider applying the attached patch.

Helmut
diff --minimal -Nru tpm2-tss-2.1.0/debian/changelog 
tpm2-tss-2.1.0/debian/changelog
--- tpm2-tss-2.1.0/debian/changelog 2019-01-30 00:22:12.0 +0100
+++ tpm2-tss-2.1.0/debian/changelog 2019-09-25 18:51:58.0 +0200
@@ -1,3 +1,10 @@
+tpm2-tss (2.1.0-4.1) UNRELEASED; urgency=medium
+
+  * Non-maintainer upload.
+  * Mark libtss2-udev Multi-Arch: foreign. (Closes: #-1)
+
+ -- Helmut Grohne   Wed, 25 Sep 2019 18:51:58 +0200
+
 tpm2-tss (2.1.0-4) unstable; urgency=low
 
   * Change tss user home directory to /var/lib/tpm.
diff --minimal -Nru tpm2-tss-2.1.0/debian/control tpm2-tss-2.1.0/debian/control
--- tpm2-tss-2.1.0/debian/control   2019-01-10 01:49:56.0 +0100
+++ tpm2-tss-2.1.0/debian/control   2019-09-25 18:51:30.0 +0200
@@ -54,6 +54,7 @@
 
 Package: libtss2-udev
 Architecture: all
+Multi-Arch: foreign
 Section: utils
 Depends: adduser, ${misc:Depends}
 Description: TPM2 Software stack library - udev files

Bug#941147: mark breeze-cursor-theme Multi-Arch: foreign

[Helmut Grohne]

Package: breeze-cursor-theme
Version: 4:5.14.5-2
Tags: patch
User: debian-cr...@lists.debian.org
Usertags: cross-satisfiability
Control: affects -1 + src:kde-cli-tools src:powerdevil src:systemsettings 
src:apper src:kget src:kdeplasma-addons src:khotkeys src:plasma-desktop

The affected packages fail to satisfy their cross Build-Depends, because
their transitive dependency on breeze-cursor-theme is unsatisfiably. In
general, Architecture: all packages can never satisfy cross build
dependencies unless marked Multi-Arch: foreign or annotated :native. In
this case, the foreign marking is reasonable. breeze-cursor-theme
entirely lacks dependencies and its maintainer scripts do not have
architecture-specific behaviour either. Please consider applying the
attached patch.

Helmut
diff --minimal -Nru breeze-5.14.5/debian/changelog 
breeze-5.14.5/debian/changelog
--- breeze-5.14.5/debian/changelog  2019-08-26 12:59:04.0 +0200
+++ breeze-5.14.5/debian/changelog  2019-09-25 18:45:57.0 +0200
@@ -1,3 +1,10 @@
+breeze (4:5.14.5-2.1) UNRELEASED; urgency=medium
+
+  * Non-maintainer upload.
+  * Mark breeze-cursor-theme Multi-Arch: foreign. (Closes: #-1)
+
+ -- Helmut Grohne   Wed, 25 Sep 2019 18:45:57 +0200
+
 breeze (4:5.14.5-2) unstable; urgency=medium
 
   * New revision
diff --minimal -Nru breeze-5.14.5/debian/control breeze-5.14.5/debian/control
--- breeze-5.14.5/debian/control2019-08-26 12:59:04.0 +0200
+++ breeze-5.14.5/debian/control2019-09-25 18:45:56.0 +0200
@@ -57,6 +57,7 @@
 
 Package: breeze-cursor-theme
 Architecture: all
+Multi-Arch: foreign
 Depends: ${misc:Depends}, ${shlibs:Depends}
 Description: Default Plasma cursor theme.
  This is the default cursor theme for the KDE Plasma 5 desktop.

Bug#932704: debian-policy: Don't force sysvinit compatibility if e.g. alternate init required

[Ansgar]

Hi,

On Sun, 2019-09-22 at 16:13 -0400, David Steele wrote:
> On Tue, Jul 23, 2019 at 2:10 PM Sean Whitton  wrote:
> > The Policy Editors have decided that dropping the requirement to ship
> > init scripts is not something that can be decided by means of the Policy
> > Changes Process, at least for the time being.
> > 
> > In proposing and reviewing wording to resolve this bug, then, we should
> > be careful not to weaken the requirement to ship init scripts.
> > Otherwise, in resolving this bug we would be changing the requirements
> > to ship init scripts by means of the Policy Changes Process.
> > 
> > I'm suggesting this be kept in mind.  It need not result in a wordier
> > change, and I certainly agree with you that we should assume good faith
> > on the part of package maintainers.
> > 
> 
> Candidate language attached. It adds "Also excepted are packages which 
> require a
> feature of an alternate init system which is not available in SysV-Style
> init systems.". Thoughts?

I don't think there is a way to get such changes through the policy
process as Sean said (I tried to document what I see as current
practice in #911165).  Practically the project seems to have already
decided that this is fine, even for packages that don't require
systemd:

+---
| There are 1033 non-overridden instances of lintian detecting a
| service unit without an init.d script [7].
+---[ https://lists.debian.org/debian-devel-announce/2019/09/msg1.html ]

Ansgar

Bug#941143: multiarchify graphviz libraries

[Helmut Grohne]

Package: libcgraph6,libcdt5,libpathplan4,libgvpr2,libxdot1,liblab-gamut1
Version: 2.40.1-7
Tags: patch
User: debian-cr...@lists.debian.org
Usertags: cross-satisfiability
Control: affects -1 + src:k3d src:python-pygraphviz src:cylc src:ns3

The affected packages fail to satisfy their cross Build-Depends, because
they somehow depend on graphviz libraries for both the build and host
architecture. Usually that means that the relevant packages should be
marked Multi-Arch: same. The multiarch hinter (see tracker.d.o todos)
indicates that doing so is safe for a number of packages. Please
consider applying the attached patch.

Helmut
diff --minimal -Nru graphviz-2.40.1/debian/changelog 
graphviz-2.40.1/debian/changelog
--- graphviz-2.40.1/debian/changelog2019-07-13 16:19:42.0 +0200
+++ graphviz-2.40.1/debian/changelog2019-09-25 18:10:09.0 +0200
@@ -1,3 +1,10 @@
+graphviz (2.40.1-7.1) UNRELEASED; urgency=medium
+
+  * Non-maintainer upload.
+  * Multiarchify packages (closes: #-1).
+
+ -- Helmut Grohne   Wed, 25 Sep 2019 18:10:09 +0200
+
 graphviz (2.40.1-7) unstable; urgency=medium
 
   * Build with ipsep mode (closes: #595084).
diff --minimal -Nru graphviz-2.40.1/debian/control 
graphviz-2.40.1/debian/control
--- graphviz-2.40.1/debian/control  2018-10-03 17:04:59.0 +0200
+++ graphviz-2.40.1/debian/control  2019-09-25 18:10:07.0 +0200
@@ -75,6 +75,7 @@
 
 Package: libgv-guile
 Architecture: any
+Multi-Arch: same
 Section: interpreters
 Depends: ${shlibs:Depends}, ${misc:Depends}
 Description: Guile bindings for graphviz
@@ -85,6 +86,7 @@
 
 Package: libgv-lua
 Architecture: any
+Multi-Arch: same
 Section: interpreters
 Depends: ${shlibs:Depends}, ${misc:Depends}
 Description: Lua bindings for graphviz
@@ -96,6 +98,7 @@
 Package: libgv-perl
 Architecture: any
 Section: perl
+Multi-Arch: same
 Depends: ${perl:Depends}, ${shlibs:Depends}, ${misc:Depends}
 Conflicts: graphviz (<< 2.12-1)
 Description: Perl bindings for graphviz
@@ -106,6 +109,7 @@
 
 Package: libgv-php7
 Architecture: any
+Multi-Arch: same
 Section: php
 Depends: ${shlibs:Depends}, ${php:Depends}, ${misc:Depends}
 Description: PHP7 bindings for graphviz
@@ -144,6 +148,7 @@
 
 Package: libgv-ruby
 Architecture: any
+Multi-Arch: same
 Section: ruby
 Depends: ${shlibs:Depends}, ${misc:Depends}
 Description: Ruby bindings for graphviz
@@ -155,6 +160,7 @@
 
 Package: libgv-tcl
 Architecture: any
+Multi-Arch: same
 Section: interpreters
 Depends: ${shlibs:Depends}, ${misc:Depends}
 Conflicts: graphviz (<< 2.12-1)
@@ -166,6 +172,7 @@
 
 Package: libcgraph6
 Architecture: any
+Multi-Arch: same
 Section: libs
 Depends: ${shlibs:Depends}, ${misc:Depends}
 Conflicts: libgraphviz4
@@ -177,6 +184,7 @@
 
 Package: libcdt5
 Architecture: any
+Multi-Arch: same
 Section: libs
 Depends: ${shlibs:Depends}, ${misc:Depends}
 Conflicts: libgraphviz4
@@ -188,6 +196,7 @@
 
 Package: libpathplan4
 Architecture: any
+Multi-Arch: same
 Section: libs
 Depends: ${shlibs:Depends}, ${misc:Depends}
 Conflicts: libgraphviz4
@@ -223,6 +232,7 @@
 
 Package: libgvpr2
 Architecture: any
+Multi-Arch: same
 Section: libs
 Depends: ${shlibs:Depends}, ${misc:Depends}
 Conflicts: libgraphviz4
@@ -235,6 +245,7 @@
 
 Package: libxdot4
 Architecture: any
+Multi-Arch: same
 Section: libs
 Depends: ${shlibs:Depends}, ${misc:Depends}
 Conflicts: libgraphviz4
@@ -246,6 +257,7 @@
 
 Package: liblab-gamut1
 Architecture: any
+Multi-Arch: same
 Section: libs
 Depends: ${shlibs:Depends}, ${misc:Depends}
 Description: rich set of graph drawing tools - liblab_gamut library
@@ -256,6 +268,7 @@
 
 Package: libgraphviz-dev
 Architecture: any
+Multi-Arch: same
 Section: libdevel
 Depends: libcdt5 (= ${binary:Version}),
  libcgraph6 (= ${binary:Version}),
@@ -281,6 +294,7 @@
 Package: graphviz-doc
 Depends: ${misc:Depends}
 Architecture: all
+Multi-Arch: foreign
 Section: doc
 Conflicts: graphviz (<< 2.12-1)
 Suggests: graphviz

Bug#941142: gexec FTCBFS: uses the build architecture pkg-config

[Helmut Grohne]

Source: gexec
Version: 0.4-2
Tags: patch upstream
User: debian-cr...@lists.debian.org
Usertags: ftcbfs

gexec fails to cross build from source, because the upstream Makefile
hard codes the build architecture pkg-config. The attached patch makes
it substitutable. Please consider applying it.

Helmut
--- gexec-0.4.orig/Makefile
+++ gexec-0.4/Makefile
@@ -1,6 +1,7 @@
 CC = gcc
-LIBS = `pkg-config --libs gtk+-2.0`
-INCS = `pkg-config --cflags gtk+-2.0`
+PKG_CONFIG ?= pkg-config
+LIBS = `$(PKG_CONFIG) --libs gtk+-2.0`
+INCS = `$(PKG_CONFIG) --cflags gtk+-2.0`
 
 CFLAGS += -Wall -g
 CFLAGS += $(CPPFLAGS)