Bug#813487: pgbouncer: Upgrading pgbouncer drops connections when run with systemd

[Peter Eisentraut]

On 2019-11-28 18:02, Christoph Berg wrote:

Not sure if there's a way around that, certainly not with TLS
connections (but that doesn't work without systemd either). Possibly
moving the connections to a helper process first, and then exec()ing
to the new version, and moving the connections back to the original
PID would work.


It might be possible to do this if we have systemd organize the file 
descriptor passing (using socket activation and all that).  It's 
something I've been meaning to look into, but it would be a development 
effort, not just a packaging change.


Another option might be to use the SO_REUSEPORT socket option and start 
a new pgbouncer instance concurrently with the old one.  Then you can 
shut down the old one once the new one is up and taking on connections. 
I don't know whether that's in scope for packaging, either, though.

Bug#948647: rust-backtrace depends on non-existent librust-compiler-builtins

[Steve Langasek]

Source: rust-backtrace
Version: 0.3.40-2
Severity: serious
User: ubuntu-de...@lists.ubuntu.com
Usertags: origin-ubuntu focal

Dear mainatiners,

The rust-backtrace package in unstable is not able to migrate to testing
because it builds binary packages that depend on a non-existent
librust-compiler-builtins-0.1+default-dev:

$ sudo apt install librust-backtrace+compiler-builtins-dev
Reading package lists... Done
Building dependency tree   
Reading state information... Done
Some packages could not be installed. This may mean that you have
requested an impossible situation or if you are using the unstable
distribution that some required packages have not yet been created
or been moved out of Incoming.
The following information may help to resolve the situation:

The following packages have unmet dependencies:
 librust-backtrace+compiler-builtins-dev : Depends: 
librust-compiler-builtins-0.1+default-dev (>= 0.1.2-~~) but it is not 
installable
E: Unable to correct problems, you have held broken packages.
$

There is no rust-compiler-builtins package in the Debian archive or in the
NEW queue.  And if this is because they are supposed to be /built in/, well,
it doesn't appear that there's agreement with the compiler packaging about
what Provides should exist.

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


signature.asc
Description: PGP signature

Bug#939989: give-back ncl (6.6.2-1+b2) on mips64el

[Sebastiaan Couwenberg]

ncl (6.6.2-1+b2) FTBFS on mips64el as part of the gdal transition, the
log shows a compiler segfault, retrying the build likely fixes that:

 gb ncl_6.6.2-1 . mips64el . -m "Rebuild against libgdal26"

I tried using the self-service but that returns a Forbidden error:

 You don't have permission to access this resource.
 Reason: Cannot perform Post-Handshake Authentication.

Kind Regards,

Bas

-- 
 GPG Key ID: 4096R/6750F10AE88D4AF1
Fingerprint: 8182 DE41 7056 408D 6146  50D1 6750 F10A E88D 4AF1



signature.asc
Description: OpenPGP digital signature

Bug#948646: comptext FTCBFS: configures for the build architecture

[Helmut Grohne]

Source: comptext
Version: 1.0.1-3
Tags: patch
User: debian-cr...@lists.debian.org
Usertags: ftcbfs

comptext fails to cross build from source, because it does not pass
--host to ./configure. Beyond that, it gets most paths wrong due to hard
coding x86 or getting the quoting wrong and fails honouring
DEB_BUILD_OPTIONS=terse. Please consider applying the attached patch to
fix all of that.

Helmut
diff --minimal -Nru comptext-1.0.1/debian/changelog 
comptext-1.0.1/debian/changelog
--- comptext-1.0.1/debian/changelog 2018-08-15 17:41:41.0 +0200
+++ comptext-1.0.1/debian/changelog 2020-01-11 07:44:07.0 +0100
@@ -1,3 +1,10 @@
+comptext (1.0.1-3.1) UNRELEASED; urgency=medium
+
+  * Non-maintainer upload.
+  * Fix FTCBFS: Fix various issues in configure invocation. (Closes: #-1)
+
+ -- Helmut Grohne   Sat, 11 Jan 2020 07:44:07 +0100
+
 comptext (1.0.1-3) unstable; urgency=medium
 
   [ Ana C. Custura ]
diff --minimal -Nru comptext-1.0.1/debian/rules comptext-1.0.1/debian/rules
--- comptext-1.0.1/debian/rules 2018-08-15 17:35:59.0 +0200
+++ comptext-1.0.1/debian/rules 2020-01-11 07:44:05.0 +0100
@@ -1,7 +1,9 @@
 #!/usr/bin/make -f
 export DEB_BUILD_MAINT_OPTIONS = hardening=+all
 
+include /usr/share/dpkg/architecture.mk
+
 %:
dh $@ --without autoreconf
 override_dh_auto_configure:
-   ./configure  --disable-option-checking --build=x86_64-linux-gnu 
--prefix=/usr --includedir=\${prefix}/include --mandir=\${prefix}/share/man 
--infodir=\${prefix}/share/info --sysconfdir=/etc --localstatedir=/var 
--disable-silent-rules --libdir=\${prefix}/lib/x86_64-linux-gnu 
--libexecdir=\${prefix}/lib/x86_64-linux-gnu --disable-maintainer-mode 
--disable-dependency-tracking
+   ./configure  --disable-option-checking --build=$(DEB_BUILD_GNU_TYPE) 
--host=$(DEB_HOST_GNU_TYPE) --prefix=/usr --includedir=\$${prefix}/include 
--mandir=\$${prefix}/share/man --infodir=\$${prefix}/share/info 
--sysconfdir=/etc --localstatedir=/var $(if $(filter 
terse,$(DEB_BUILD_OPTIONS)),,--disable-silent-rules) 
--libdir=\$${prefix}/lib/$(DEB_HOST_MULTIARCH) 
--libexecdir=\$${prefix}/lib/$(DEB_HOST_MULTIARCH) --disable-maintainer-mode 
--disable-dependency-tracking

Bug#948645: pesign FTBFS: nss-induced error: unsigned conversion from ‘int’ to ‘unsigned char’ changes value from ‘496’ to ‘240’ [-Werror=overflow]

[Helmut Grohne]

Source: pesign
Version: 0.112-5
Severity: serious

pesign fails to build from source in unstable:

| /usr/bin/gcc -g -O2 -ffile-prefix-map=/build/1st/pesign-0.112=. 
-fstack-protector-strong -Wformat -Werror=format-security  -Wall -Werror 
-Wno-cpp  -Wsign-compare -Wno-unused-result -Wno-unused-function -std=gnu11 
-fshort-wchar -fPIC -flto -fno-strict-aliasing -fno-merge-constants 
-fkeep-inline-functions -D_GNU_SOURCE -DCONFIG_x86_64 
-I/build/1st/pesign-0.112/include -I/usr/include/efivar -I/usr/include/nss 
-I/usr/include/nspr -I/usr/include/uuid -Werror -Wdate-time -D_FORTIFY_SOURCE=2 
-c -o efikeygen.o efikeygen.c
| In file included from /usr/include/nss/cert.h:22,
|  from efikeygen.c:39:
| efikeygen.c: In function 'add_cert_type':
| /usr/include/nss/certt.h:460:5: error: unsigned conversion from 'int' to 
'unsigned char' changes value from '496' to '240' [-Werror=overflow]
|   460 | (NS_CERT_TYPE_SSL_CLIENT | NS_CERT_TYPE_SSL_SERVER | 
NS_CERT_TYPE_EMAIL | \
|   | ^
| efikeygen.c:208:23: note: in expansion of macro 'NS_CERT_TYPE_APP'
|   208 |  unsigned char type = NS_CERT_TYPE_APP;
|   |   ^~~~
| cc1: all warnings being treated as errors
| make[2]: *** [/build/1st/pesign-0.112/Make.rules:33: efikeygen.o] Error 1
| make[2]: Leaving directory '/build/1st/pesign-0.112/src'
| make[1]: *** [Makefile:25: all] Error 2
| make[1]: Leaving directory '/build/1st/pesign-0.112'
| dh_auto_build: make -j1 returned exit code 2
| make: *** [debian/rules:15: build] Error 255
| dpkg-buildpackage: error: debian/rules build subprocess returned exit status 2

Observed by crossqa:
http://crossqa.subdivi.de/build/pesign_0.112-5_arm64_20200111051741.log
Reproduced by reproducible builds:
https://tests.reproducible-builds.org/debian/rbuild/unstable/amd64/pesign_0.112-5.rbuild.log.gz

Very likely, this failure is due to a change in nss. I've Cced the
mozilla team.

Helmut

Bug#921717: RFH: cyrus-imapd -- Cyrus mail system - IMAP support

[Xavier]

Le 10/01/2020 à 20:32, Mike Gabriel a écrit :
> Hi Xavier,
> 
> On Tue, 17 Dec 2019 02:39:47 +0100 Xavier  wrote:
>> Control: retitle -1 RFH: cyrus-imapd -- Cyrus mail system - IMAP support
>>
>> Hi,
>>
>> I took over the maintenance of cyrus-imapd. However, I'd like some help
>> to maintain it.
>>
>> Cheers,
>> Xavier
> 
> I'd be interested in helping out. My production still runs on a very old
> version of cyrus-imapd (from Kolab v2 times) and I will need to upgrade
> it at the beginning of February.
> 
> I'll ping you then and let you know, if I can add some help to the
> cyrus-imapd package maintenance effort.
> 
> Thanks+Greets,
> Mike

Welcome on board :-D

Bug#948644: RM: python-cherrypy -- ROM; python2-only; superseeded by src:cherrypy3; leaf package

[Sandro Tosi]

Package: ftp.debian.org
Severity: normal

Bug#948643: apt-file: fails to update

[Anthony M.R. Alvis]

Package: apt-file
Version: 3.2.2
Severity: grave
Justification: renders package unusable

Dear Maintainer,

I have attached a text file containing what happens after i run sudo apt-file 
update;

-- System Information:
Distributor ID: Raspbian
Description:Raspbian GNU/Linux 10 (buster)
Release:10
Codename:   buster
Architecture: armv7l

Kernel: Linux 4.19.75-v7l+ (SMP w/4 CPU cores)
Kernel taint flags: TAINT_CRAP
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) (ignored: LC_ALL 
set to en_US.UTF-8), LANGUAGE=en_US.UTF-8 (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)

Versions of packages apt-file depends on:
ii  apt  1.8.2
ii  libapt-pkg-perl  0.1.34+b1
ii  liblist-moreutils-perl   0.416-1+b3
ii  libregexp-assemble-perl  0.36-1
ii  perl 5.28.1-6

apt-file recommends no packages.

apt-file suggests no packages.

-- no debconf information
Hit:1 http://archive.raspberrypi.org/debian buster InRelease
Hit:2 http://raspbian.raspberrypi.org/raspbian buster InRelease
Get:3 http://archive.raspberrypi.org/debian buster/main armhf Contents (deb) 
[998 kB]
Get:4 http://raspbian.raspberrypi.org/raspbian buster/main armhf Contents (deb) 
[39.8 MB]
Get:5 http://raspbian.raspberrypi.org/raspbian buster/contrib armhf Contents 
(deb) [211 kB]  

Get:6 http://raspbian.raspberrypi.org/raspbian buster/non-free armhf Contents 
(deb) [780 kB]  
   
Get:7 http://raspbian.raspberrypi.org/raspbian buster/rpi armhf Contents (deb) 
[307 B] 
  
Fetched 41.8 MB in 1min 40s (418 kB/s)  

 
Traceback (most recent call last):
  File "/usr/lib/cnf-update-db", line 26, in 
col.create(db)
  File "/usr/share/command-not-found/CommandNotFound/db/creator.py", line 94, 
in create
self._fill_commands(con)
  File "/usr/share/command-not-found/CommandNotFound/db/creator.py", line 132, 
in _fill_commands
self._parse_single_contents_file(con, f, fp.stdout)
  File "/usr/share/command-not-found/CommandNotFound/db/creator.py", line 271, 
in _parse_single_contents_file
priority = component_priorities[component]
KeyError: 'rpi'
Reading package lists... Done
E: Problem executing scripts APT::Update::Post-Invoke-Success 'if /usr/bin/test 
-w /var/lib/command-not-found/ -a -e /usr/lib/cnf-update-db; then 
/usr/lib/cnf-update-db > /dev/null; fi'
E: Sub-process returned an error code

Bug#948642: rust-cookie: Depends on older rust-ring than is in unstable

[Steve Langasek]

Source: rust-cookie
Version: 0.12.0-4
Severity: serious
User: ubuntu-de...@lists.ubuntu.com
Usertags: origin-ubuntu focal

rust-cookie depends on rust-ring 0.14, but rust-ring is now at version 0.16
in unstable:

$ sudo apt install librust-cookie+ring-dev
Reading package lists... Done
Building dependency tree   
Reading state information... Done
Some packages could not be installed. This may mean that you have
requested an impossible situation or if you are using the unstable
distribution that some required packages have not yet been created
or been moved out of Incoming.
The following information may help to resolve the situation:

The following packages have unmet dependencies:
 librust-cookie+ring-dev : Depends: librust-ring-0.14+default-dev but it is not 
installable
E: Unable to correct problems, you have held broken packages.
$

Please update rust-cookie for compatibility with the current rust-ring.

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


signature.asc
Description: PGP signature

Bug#948641: rust-extprim: Build-depends on older rust-rand than is in unstable

[Steve Langasek]

Source: rust-extprim
Version: 0.4.1-1
Severity: serious
User: ubuntu-de...@lists.ubuntu.com
Usertags: origin-ubuntu focal

rust-extprim build-depends on librust-rand-0.6+default-dev, but
rust-rand is now at version 0.7 in unstable:

$ sudo apt build-dep rust-extprim
Reading package lists... Done
Reading package lists... Done
Building dependency tree   
Reading state information... Done
Some packages could not be installed. This may mean that you have
requested an impossible situation or if you are using the unstable
distribution that some required packages have not yet been created
or been moved out of Incoming.
The following information may help to resolve the situation:

The following packages have unmet dependencies:
 builddeps:rust-extprim : Depends: librust-rand-0.6+default-dev but it is not 
installable
E: Unable to correct problems, you have held broken packages.
$

Please update rust-extprim for compatibility with the current rust-rand.

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


signature.asc
Description: PGP signature

Bug#948640: rust-migrations-internals: depends on older rust-barrel than is in unstable

[Steve Langasek]

Source: rust-migrations-internals
Version: 1.4.0-1
Severity: serious
User: ubuntu-de...@lists.ubuntu.com
Usertags: origin-ubuntu focal

rust-migrations-internals depends on librust-barrel+default-dev (<<
0.2.1-~~), but rust-barrel is now at version 0.6.2 in unstable:

$ sudo apt install librust-migrations-internals+barrel-dev
Reading package lists... Done
Building dependency tree   
Reading state information... Done
Some packages could not be installed. This may mean that you have
requested an impossible situation or if you are using the unstable
distribution that some required packages have not yet been created
or been moved out of Incoming.
The following information may help to resolve the situation:

The following packages have unmet dependencies:
 librust-migrations-internals+barrel-dev : Depends: librust-barrel+default-dev 
(< 0.2.1-~~)
   Depends: 
librust-barrel+diesel-filled-dev (< 0.2.1-~~) but it is not installable
E: Unable to correct problems, you have held broken packages.
$

Please update rust-migrations-internals for compatibility with the current
rust-barrel.

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


signature.asc
Description: PGP signature

Bug#874880: FreeMedForms projet

[Andreas Tille]

On Sat, Jan 11, 2020 at 08:39:48AM +0800, Paul Wise wrote:
> 
> The bigger problem for entering Debian is what Andreas mentions, that
> the software uses Qt4 instead of Qt5. Once you have released a new
> version that uses Qt5 it could potentially enter Debian.

To be correct: Version 0.9.4 in Debian is Qt4, but Version 1.0.0 in Git
is Qt5.  It just does not build successfully[1] ... and since monthes
nobody was able fix this.  Eric said he can not reproduce this build
issue (in private mail) and non of the Debian maintainers found a clue
so far.

Kind regards
 Andreas.

[1] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=874880#104

-- 
http://fam-tille.de

Bug#948639: rust-log depends on non-existent librust-sval-0.4+fmt-dev

[Steve Langasek]

Source: rust-log
Version: 0.4.8-2
Severity: serious
User: ubuntu-de...@lists.ubuntu.com
Usertags: origin-ubuntu focal

Hi Sylvestre,

The rust-log package in unstable is not able to migrate to testing because
it builds binary packages that depend on a non-existent rust-sval:

librust-log+kv-unstable-sval-dev/amd64 unsatisfiable Depends: 
librust-sval-0.4+fmt-dev (>= 0.4.2-~~)
librust-log+sval-dev/amd64 unsatisfiable Depends: librust-sval-0.4-dev (>= 
0.4.2-~~)

There is no rust-sval package in the Debian archive or in the NEW queue.

Please take care to make sure your packages' dependencies are met.

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


signature.asc
Description: PGP signature

Bug#925749: Debug build is ok

[Andreas Tille]

On Sat, Jan 11, 2020 at 11:13:30AM +0800, Feng Zhao wrote:
> lgf_reader_writer_test passes when I build the program in Debug mode. However,
> Release mode build will fail to run, which is the default build in packaging.

While it is strange that it does not build in Release mode I wonder why
you think it is default mode.  We usually include debug symbols that are
stripped afterwards.

Kind regards

 Andreas.

-- 
http://fam-tille.de

Bug#936924: Moving libsvm to Debian Science team

[Andreas Tille]

On Fri, Jan 10, 2020 at 11:45:15PM +0100, Christian Kastner wrote:
> 
> @Andreas: I can't push my changes to master, I get a protected branch
> error. Could you please grant me the necessary privileges?

Strange.  I did not intentionally set the branch protection.  Hope it
works now.
 
> There's a lintian info about a missing JAR, but I suspect that has more
> to do with the symlink from libsvm-java pointing to libsvm3-java.
> 
> I added a simple autopkgtest and it passed. Seeing as the symbols didn't
> change a bit, I can see no reason why this couldn't be uploaded as-is,
> but I'm tired and I'd like to check it again tomorrow with a fresh pair
> of eyes, lest we break something.

Thanks for your detailed work on this.

Kind regards

   Andreas. 

-- 
http://fam-tille.de

Bug#948638: transition: opencv

[Mo Zhou]

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

(please explain about the transition: impacted packages, reason, ...

4.1.2+dfsg-5 -> 4.2.0+dfsg-2

We need to handle the opencv SOVERSION bump along with new upstream
release.  Unlike the 3.2->4.1 transition we've done a couple of weeks
ago, this 4.1->4.2 transition is expected to be much easier.

The automatically generated ben file on the tracker is good enough:
https://release.debian.org/transitions/html/auto-opencv.html


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

Kernel: Linux 5.4.0-1-amd64 (SMP w/8 CPU cores)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_WARN, 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

Bug#948637: follow permanent redirects when filling in Vcs fields

[Jelmer Vernooij]

Package: lintian-brush
Version: 0.55
Severity: normal

When setting Repository/Repository-Browse fields in debian/upstream/metadata,
lintian-brush should resolve any permanent redirects rather than inserting the
old URL.

This applies to e.g. 'supervisor', which lintian-brush detects a SVN URL for of
http://svn.supervisord.org/supervisor/trunk, but that redirects to
https://github.com/supervisor/supervisor

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

Kernel: Linux 5.3.0-2-amd64 (SMP w/2 CPU cores)
Kernel taint flags: TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE
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: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages lintian-brush depends on:
ii  devscripts   2.19.7
ii  python3  3.7.5-3
ii  python3-breezy   3.0.2-1
ii  python3-debian   0.1.36
ii  python3-distro-info  0.23
ii  python3-dulwich  0.19.14-4
ii  python3-iniparse 0.4-3
ii  python3-levenshtein  0.12.0-5
ii  python3-pkginfo  1.4.2-2
ii  python3-ruamel.yaml  0.15.89-3+b1

Versions of packages lintian-brush recommends:
ii  dos2unix   7.4.0-2
ii  gpg2.2.19-1
ii  libdebhelper-perl  12.7.3
ii  lintian2.44.0
ii  python3-asyncpg0.20.0-1
ii  python3-pyinotify  0.9.6-1.2

Versions of packages lintian-brush suggests:
pn  gnome-pkg-tools
ii  postgresql-common  210

-- no debconf information

Bug#945920: Random Chromium crashes

[nozzy123nozzy]

Tags: patch

Sorry for disturbing all of you, but the tag of this report didn't
become change. I'm not sure why.

This mail is the last trial sending command tag + patch. In this time,
I attach my patch (derived from Eloston's patch), which is the same as
I posted on 8th Jan.

Takahide Nojima

On Sat, 11 Jan 2020 12:20:40 +0900 nozzy123no...@gmail.com wrote:
> tag 945920 + patch
> thanks

diff -r -N -u a/debian/control b/debian/control
--- a/debian/control	2019-12-15 03:47:43.0 +0900
+++ b/debian/control	2020-01-05 23:10:06.035727253 +0900
@@ -82,6 +82,7 @@
  libgcrypt20-dev,
  fonts-ipafont-gothic,
  fonts-ipafont-mincho,
+ libx11-xcb-dev
 
 Package: chromium
 Architecture: i386 amd64 arm64 armhf
diff -r -N -u a/debian/copyright b/debian/copyright
--- a/debian/copyright	2019-12-15 03:47:43.0 +0900
+++ b/debian/copyright	2020-01-01 20:02:46.319322326 +0900
@@ -37,7 +37,6 @@
  chrome/installer/launcher_support
  chrome/common/extensions/docs
  chrome/common/safe_browsing/rar_analyzer.*
- chrome/browser/tracing
  chrome/browser/resources/chromeos
  chrome/browser/resources/default_apps
  chrome/test/data/android
@@ -45,7 +44,6 @@
  chrome/test/data/extensions
  chrome/test/data/webui/i18n_process_css_test.html
  chrome/chrome_cleaner/test/resources/signed_dll
- services/tracing
  tools/emacs
  tools/luci-go
  tools/android
@@ -116,7 +114,6 @@
  third_party/expat/src
  third_party/*rjsmin/bench
  third_party/unrar
- third_party/perfetto
  third_party/checkstyle
  third_party/swiftshader
  third_party/apache-win32
@@ -150,23 +147,6 @@
  third_party/devtools-node-modules
  third_party/blanketjs/src/blanket.js
  third_party/accessibility-audit/axs_testing.js
- third_party/catapult/tracing
- third_party/catapult/third_party/flot
- third_party/catapult/third_party/chai
- third_party/catapult/third_party/vinn
- third_party/catapult/third_party/mocha
- third_party/catapult/third_party/coverage
- third_party/catapult/third_party/polymer2
- third_party/catapult/third_party/polymer3
- third_party/catapult/third_party/polymer/components
- third_party/catapult/third_party/d3/d3.min.js
- third_party/catapult/third_party/redux/redux.min.js
- third_party/catapult/experimental/heatmap/power.js
- third_party/catapult/experimental/heatmap/smoothness.js
- third_party/catapult/experimental/trace_on_tap/third_party/pako/pako_deflate.min.js
- third_party/catapult/third_party/gsutil
- third_party/catapult/third_party/Paste/paste/evalexception/media/MochiKit.packed.js
- third_party/catapult/telemetry/telemetry/internal/testing/perf_report_output.txt
  third_party/webrtc/sdk
  third_party/webrtc/data
  third_party/webrtc/examples
diff -r -N -u a/debian/patches/series b/debian/patches/series
--- a/debian/patches/series	2019-12-15 03:47:43.0 +0900
+++ b/debian/patches/series	2020-01-02 17:32:16.998129815 +0900
@@ -39,11 +39,9 @@
 disable/signin.patch
 disable/android.patch
 disable/fuzzers.patch
-disable/tracing.patch
 disable/openh264.patch
 disable/buildbot.patch
 disable/chromeos.patch
-disable/perfetto.patch
 disable/installer.patch
 disable/font-tests.patch
 disable/swiftshader.patch
@@ -81,3 +79,4 @@
 
 buster/icu63.patch
 buster/vpx17.patch
+system/force_system_zlib.patch
diff -r -N -u a/debian/patches/system/force_system_zlib.patch b/debian/patches/system/force_system_zlib.patch
--- a/debian/patches/system/force_system_zlib.patch	1970-01-01 09:00:00.0 +0900
+++ b/debian/patches/system/force_system_zlib.patch	2020-01-02 17:37:30.344621702 +0900
@@ -0,0 +1,11 @@
+--- a/third_party/perfetto/gn/BUILD.gn
 b/third_party/perfetto/gn/BUILD.gn
+@@ -305,7 +305,7 @@
+ "//buildtools:zlib",
+   ]
+ } else {
+-  public_configs = [ "//third_party/zlib:zlib_config" ]
++  public_configs = [ "//third_party/zlib:system_zlib" ]
+   public_deps = [
+ "//third_party/zlib",
+   ]
diff -r -N -u a/debian/rules b/debian/rules
--- a/debian/rules	2019-12-15 03:47:43.0 +0900
+++ b/debian/rules	2020-01-01 20:02:46.319322326 +0900
@@ -199,16 +199,14 @@
 	patch -p1 < debian/scripts/mk-origtargz.patch
 	date +%s > $(seconds)
 	perl debian/scripts/mk-origtargz ../$(tarball) > $(removed)
+	echo $(extract)/third_party/perfetto/ui/src/gen >> $(removed)
 	echo $$(($$(date +%s) - $$(cat $(seconds seconds
 	test ! -e $(extract) || rm -rf $(extract)
 	tar xf ../$(tarball)
 	echo $$(($$(date +%s) - $$(cat $(seconds seconds
-	while read line; do rm -rf $$line; done < $(removed)
+	xargs rm -rf < $(removed)
 	cd $(extract) && ../debian/scripts/check-upstream
-	echo $$(($$(date +%s) - $$(cat $(seconds seconds
-	test ! -e $(origtxz) || rm -f $(origtxz)
-	tar cf - $(extract) | xz -6 -T $(njobs) - > $(origtxz)
-	echo $$(($$(date +%s) - $$(cat $(seconds seconds
-	rm -rf $(extract)
 	echo $$(($$(date +%s) - $$(cat $(seconds seconds | tee seconds
 	@mv -f seconds $(seconds)
+	test ! -e $(extract)/debian || rm -rf $(extract)/debian
+	cp -r debian $(extract)/.

Bug#948636: RFA: autopsy -- graphical interface to SleuthKit

[JAIR REIS]

Package: wnpp
Severity: normal

I request an adopter for the autopsy package.

The package description is:
 The Autopsy Forensic Browser is a graphical interface to the command line
 digital forensic analysis tools in The Sleuth Kit. Together, The Sleuth Kit
 and Autopsy provide many of the same features as commercial digital forensics.

Package: autopsy
Binary: autopsy
Version: 2.24-1.1
Maintainer: Lorenzo Martignoni 
Build-Depends: debhelper (>= 7.0.0), dpatch
Build-Depends-Indep: sleuthkit (>= 3.0.0)
Architecture: all
Standards-Version: 3.8.4
Format: 1.0
Files:
 29e35b5081ef364448140d3a4dc1504f 1679 autopsy_2.24-1.1.dsc
 4ed18aa9f79453d74957b5db220d0d59 387873 autopsy_2.24.orig.tar.gz
 c3c59d64e6c6cdd525e20bafe1f1787d 15145 autopsy_2.24-1.1.diff.gz
Checksums-Sha256:
 436232a66253ab4b21e2798c8a746ac48e8d2103e3bc6154c84a99e7d9b7721f 1679
autopsy_2.24-1.1.dsc
 ab787f519942783d43a561d12be0554587f11f22bc55ab79d34d8da703edc09e 387873
autopsy_2.24.orig.tar.gz
 9f62099bac1a85a5a4941df12c9ffcf2360d6a7b077d2807737523466db377cd 15145
autopsy_2.24-1.1.diff.gz
Package-List:
 autopsy deb admin optional arch=all
Directory: pool/main/a/autopsy
Priority: source
Section: admin

Bug#945920: Random Chromium crashes

[nozzy123nozzy]

tag 945920 + patch
thanks

Bug#925749: Debug build is ok

[Feng Zhao]

lgf_reader_writer_test passes when I build the program in Debug mode. However,
Release mode build will fail to run, which is the default build in packaging.

Bug#945920: Random Chromium crashes

[nozzy123nozzy]

tags 945920 + patch
thanks

Hi Maintainer,

I forgot to add tag of patch, then I added.
 
Additionally, I've been testing chromium 79.0.3945.79 which applied
Eloston's patch, it is still quite stable, no crash.

Takahide Nojima.


On Wed, 08 Jan 2020 02:28:51 +0900 nozzy123no...@gmail.com wrote:
> Hi Maintainer,
> 
>  A few days ago, I built chromium according to the way of Eloston's,
> too. But I also needed to slightly modify Eloston's patch to finish
to
> compile whole chromium source. I attached my version of the patch to
> this report.
> 
>  Until now, I'm testing this version of chromium by usual browsing,
but
> it seems to be highly stable than before! At least, it seems never to
> crash in my Debian box.
> 
>  Before Elostion's patch, in browsing some site, chromium almost
always
> crashed viewing within a few pages.
> 
>  I'm really looking forward to newer version of chromium package
> applied Eloston's patch.
> 
> Thank in advance,
> Takahide Nojima.

Bug#948584: Sorry missed a part of coredumpctl -- here's the full version

[Miriam Winterling]

Hi Bernhard.

I've attached the complete Coredump. In the other version there is missing the 
last part.

Sorry and Thanks

Kind regards
Miriam
Reading symbols from /sbin/mount.nfs...
Reading symbols from 
/usr/lib/debug/.build-id/ca/11f72c38561b3cfdaff318ea3818ea731ad036.debug...
[New LWP 6399]
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
Core was generated by `/sbin/mount.nfs 192.168.178.31:/Medienwerkstatt 
/media/MiruNAS/Medienwerkstatt'.
Program terminated with signal SIGSEGV, Segmentation fault.
#0  __strcasecmp_l_avx () at ../sysdeps/x86_64/multiarch/strcmp-sse42.S:200
200 ../sysdeps/x86_64/multiarch/strcmp-sse42.S: Datei oder Verzeichnis 
nicht gefunden.
(gdb) bt full
#0  __strcasecmp_l_avx () at ../sysdeps/x86_64/multiarch/strcmp-sse42.S:200
No locals.
#1  0x559dd1170dd9 in conf_get_tag_list 
(section=section@entry=0x559dd11746b6 "MountPoint", 
arg=arg@entry=0x559dd1ab1140 "/media/MiruNAS/Medienwerkstatt") at conffile.c:582
list = 0x559dd1ab0d20
node = 
cb = 0x559dd1ab0e60
#2  0x559dd116aef5 in conf_parse_mntopts 
(section=section@entry=0x559dd11746b6 "MountPoint", arg=0x559dd1ab1140 
"/media/MiruNAS/Medienwerkstatt", 
opts=opts@entry=0x559dd1ab0f80 
"rw,nfsvers=4,no_subtree_check,root_squash,fsid=34c404ad556b1aa0df061251c9b4d1d0")
 at configfile.c:297
list = 
node = 
buf = '\000' ...
value = 
field = 
nvalue = 
ptr = 
argtype = 
#3  0x559dd116b3af in conf_get_mntopts (spec=0x7ffe2b34feff 
"192.168.178.31:/Medienwerkstatt", mount_point=, 
mount_opts=0x559dd1ab0f80 
"rw,nfsvers=4,no_subtree_check,root_squash,fsid=34c404ad556b1aa0df061251c9b4d1d0")
 at configfile.c:366
entry = 
ptr = 
server = 
config_opts = 
optlen = 0
#4  0x559dd1162fc2 in mount_config_opts (mount_opts=, 
mount_point=0x559dd1ab1140 "/media/MiruNAS/Medienwerkstatt", 
spec=0x7ffe2b34feff "192.168.178.31:/Medienwerkstatt") at mount_config.h:37
No locals.
#5  mount_main (argv=0x7ffe2b34faf8, argc=, cxt=0x559dd1ab0960) 
at mount_libmount.c:392
c = -1
opts = 
rc = 
fs = 0x559dd1ab0ea0
spec = 0x7ffe2b34feff "192.168.178.31:/Medienwerkstatt"
mount_point = 0x559dd1ab1140 "/media/MiruNAS/Medienwerkstatt"
rc = 
c = 
fs = 
spec = 
mount_point = 
opts = 
longopts = {{name = 0x559dd11749c0 "fake", has_arg = 0, flag = 0x0, val 
= 102}, {name = 0x559dd11744e1 "help", has_arg = 0, flag = 0x0, val = 104}, 
{name = 0x559dd11749c5 "no-mtab", has_arg = 0, 
flag = 0x0, val = 110}, {name = 0x559dd11749cd "read-only", has_arg 
= 0, flag = 0x0, val = 114}, {name = 0x559dd11749d7 "ro", has_arg = 0, flag = 
0x0, val = 114}, {name = 0x559dd117451e "verbose", 
has_arg = 0, flag = 0x0, val = 118}, {name = 0x559dd11744ac 
"version", has_arg = 0, flag = 0x0, val = 86}, {name = 0x559dd11749da 
"read-write", has_arg = 0, flag = 0x0, val = 119}, {
name = 0x559dd11749e5 "rw", has_arg = 0, flag = 0x0, val = 119}, 
{name = 0x559dd11749e8 "options", has_arg = 1, flag = 0x0, val = 111}, {name = 
0x559dd11742a4 "sloppy", has_arg = 0, flag = 0x0, 
val = 115}, {name = 0x0, has_arg = 0, flag = 0x0, val = 0}}
#6  main (argc=, argv=0x7ffe2b34faf8) at mount_libmount.c:454
cxt = 0x559dd1ab0960
rc = 

Bug#948635: onboard: LayoutLoaderSVG.py:447: SyntaxWarning: 'str' object is not callable; perhaps you missed a comma?

[Paul Wise]

Package: onboard
Version: 1.4.1-5
Severity: normal
File: /usr/lib/python3/dist-packages/Onboard/LayoutLoaderSVG.py
Usertags: warnings

Now that Python 3.8 is in Debian, upgrading onboard prints a
SyntaxWarning when the .py files are bytecompiled:

Setting up onboard (1.4.1-5) ...
Installing new version of config file 
/etc/xdg/autostart/onboard-autostart.desktop ...
/usr/lib/python3/dist-packages/Onboard/LayoutLoaderSVG.py:447: SyntaxWarning: 
'str' object is not callable; perhaps you missed a comma?
  raise Exceptions.LayoutFileError("Unrecognized modifier %s in" \

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

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

Versions of packages onboard depends on:
ii  dconf-gsettings-backend [gsettings-backend]  0.34.0-2
ii  gir1.2-gdkpixbuf-2.0 2.40.0+dfsg-2
ii  gir1.2-glib-2.0  1.62.0-2
ii  gir1.2-gtk-3.0   3.24.13-1
ii  gir1.2-pango-1.0 1.42.4-7
ii  iso-codes4.4-1
ii  libc62.29-7
ii  libcairo21.16.0-4
ii  libcanberra0 0.30-7
ii  libdconf10.34.0-2
ii  libgcc1  1:9.2.1-22
ii  libglib2.0-0 2.62.4-1
ii  libgtk-3-0   3.24.13-1
ii  libhunspell-1.7-01.7.0-2+b1
ii  librsvg2-common  2.46.4-1
ii  libstdc++6   9.2.1-22
ii  libudev1 244-3
ii  libx11-6 2:1.6.8-1
ii  libxi6   2:1.7.9-1
ii  libxkbfile1  1:1.0.9-2+b12
ii  libxtst6 2:1.2.3-1
ii  onboard-common   1.4.1-5
ii  python3  3.7.5-3
ii  python3-cairo1.16.2-2
ii  python3-dbus 1.2.14-1
ii  python3-gi-cairo 3.34.0-3

Versions of packages onboard recommends:
ii  gir1.2-atspi-2.0 2.34.0-3
pn  gir1.2-ayatanaappindicator3-0.1  
ii  onboard-data 1.4.1-5
ii  xdg-utils1.1.3-1

Versions of packages onboard suggests:
ii  mousetweaks  3.32.0-2

-- no debconf information

-- 
bye,
pabs

https://wiki.debian.org/PaulWise


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

Bug#948634: debian-security-support: please elaborate on binutils' status

[Daniel Shahaf]

Package: debian-security-support
Version: 2019.06.13
Severity: important
Tags: patch
Control: affects -1 binutils

Dear Maintainer,

Now that binutils has limited security support, please elaborate on its
status.  Suggested patch (against current git):

--- a/security-support-limited
+++ b/security-support-limited
@@ -7,7 +7,7 @@
 #In the program's output, this is prefixed with "Details:"
 
 adnsStub resolver that should only be used with trusted recursors
-binutilsNot covered by security support
+binutilsOnly suitable for trusted content; see 
https://lists.debian.org/msgid-search/87lfqsomtg@mid.deneb.enyo.de
 ganglia See README.Debian.security, only supported behind an 
authenticated HTTP zone, #702775
 ganglia-web See README.Debian.security, only supported behind an 
authenticated HTTP zone, #702776
 glpiOnly supported behind an authenticated HTTP zone for trusted 
users

@Florian That linked message is yours; any objections from you?

Thanks,

Daniel

P.S. Priority "important" since binutils' rdeps include dpkg-dev, gcc,
and clang, so I assume this is quite visible.

Bug#948633: linux-image-5.4.0-2-amd64: Some kind of problem in iwlwifi/iwldvm

[Nelson A. de Oliveira]

Package: src:linux
Version: 5.4.8-1
Severity: normal

Hi!

I am unsure what kind of problem this is, but I am always seeing this in
dmseg:

=
[  406.074462] [ cut here ]
[  406.074487] WARNING: CPU: 1 PID: 2982 at 
drivers/net/wireless/intel/iwlwifi/dvm/tx.c:432 iwlagn_tx_skb+0x7d0/0xab0 
[iwldvm]
[  406.074489] Modules linked in: fuse btrfs xor zstd_compress raid6_pq 
zstd_decompress ufs qnx4 hfsplus hfs minix vfat msdos fat jfs xfs libcrc32c 
dm_mod vboxnetadp(OE) vboxnetflt(OE) vboxdrv(OE) ctr ccm algif_aead des_generic 
libdes arc4 algif_skcipher cpufreq_conservative cpufreq_powersave 
cpufreq_userspace zram zsmalloc cmac md4 algif_hash af_alg uinput btusb btrtl 
btbcm btintel bluetooth jitterentropy_rng uvcvideo videobuf2_vmalloc 
videobuf2_memops videobuf2_v4l2 videobuf2_common videodev intel_rapl_msr 
intel_rapl_common x86_pkg_temp_thermal intel_powerclamp mc coretemp drbg 
kvm_intel kvm ansi_cprng irqbypass ecdh_generic ecc crct10dif_pclmul 
crc32_pclmul ghash_clmulni_intel iwldvm snd_hda_codec_hdmi mac80211 
snd_hda_codec_realtek snd_hda_codec_generic libarc4 i915 snd_hda_intel iwlwifi 
snd_intel_nhlt snd_hda_codec dell_laptop ledtrig_audio snd_hda_core aesni_intel 
snd_hwdep drm_kms_helper crypto_simd snd_pcm cryptd glue_helper dell_wmi 
cfg80211 drm joydev intel_cstate snd_timer
[  406.074549]  intel_uncore evdev dell_smbios iTCO_wdt mei_me snd dcdbas 
serio_raw sparse_keymap pcspkr iTCO_vendor_support wmi_bmof intel_rapl_perf 
dell_wmi_descriptor watchdog soundcore mei sg rfkill i2c_algo_bit dell_smo8800 
acpi_cpufreq ac button binfmt_misc pkcs8_key_parser ip_tables x_tables autofs4 
ext4 crc16 mbcache jbd2 crc32c_generic sr_mod cdrom sd_mod uas usb_storage 
hid_generic usbhid hid ahci libahci xhci_pci libata xhci_hcd ehci_pci ehci_hcd 
scsi_mod usbcore r8169 psmouse realtek crc32c_intel libphy lpc_ich i2c_i801 
mfd_core wmi usb_common battery video
[  406.074597] CPU: 1 PID: 2982 Comm: iwd Tainted: G   OE 
5.4.0-2-amd64 #1 Debian 5.4.8-1
[  406.074599] Hardware name: Dell Inc.  Dell System XPS L502X/0MY6GN, 
BIOS A12 09/07/2012
[  406.074610] RIP: 0010:iwlagn_tx_skb+0x7d0/0xab0 [iwldvm]
[  406.074614] Code: 02 00 00 48 8d 04 80 4b 8d 14 9b 48 c1 e0 05 48 8d 04 90 
41 0f b6 54 24 2d 0f b7 84 03 54 19 00 00 48 89 c1 38 54 03 61 74 02 <0f> 0b 44 
88 7c 24 23 e9 b2 fd ff ff 49 8b 0e 48 8d 7d 44 48 83 e7
[  406.074617] RSP: 0018:9f8e816f38a8 EFLAGS: 00010202
[  406.074620] RAX: 000b RBX: 9319ee6b1e28 RCX: 000b
[  406.074622] RDX:  RSI: 9319db93fc78 RDI: 9319de100ad0
[  406.074624] RBP: 9319de100a80 R08: 4050 R09: 4050
[  406.074625] R10:  R11:  R12: 9319e8839900
[  406.074627] R13: 9319ee6b1e58 R14: 9319db93fc64 R15: db93fc01
[  406.074631] FS:  7fac992f7740() GS:9319f244() 
knlGS:
[  406.074633] CS:  0010 DS:  ES:  CR0: 80050033
[  406.074635] CR2: 7f9e111e4000 CR3: 000327d34004 CR4: 000606e0
[  406.074637] Call Trace:
[  406.074655]  iwlagn_mac_tx+0x1e/0x40 [iwldvm]
[  406.074705]  ieee80211_tx_frags+0x14c/0x220 [mac80211]
[  406.074741]  __ieee80211_tx+0x71/0x130 [mac80211]
[  406.074774]  ieee80211_tx+0x102/0x130 [mac80211]
[  406.074808]  __ieee80211_subif_start_xmit+0x808/0xca0 [mac80211]
[  406.074817]  ? __wake_up_common+0x80/0x180
[  406.074822]  ? prep_new_page+0x3e/0x150
[  406.074828]  ? kmem_cache_alloc+0x159/0x210
[  406.074833]  ? __build_skb+0x1f/0x50
[  406.074864]  ieee80211_tx_control_port+0x127/0x160 [mac80211]
[  406.074912]  nl80211_tx_control_port+0x12e/0x250 [cfg80211]
[  406.074920]  genl_family_rcv_msg+0x1b6/0x410
[  406.074926]  genl_rcv_msg+0x47/0x90
[  406.074931]  ? __kmalloc_node_track_caller+0x1ec/0x2f0
[  406.074934]  ? genl_family_rcv_msg+0x410/0x410
[  406.074940]  netlink_rcv_skb+0x49/0x110
[  406.074944]  genl_rcv+0x24/0x40
[  406.074949]  netlink_unicast+0x172/0x200
[  406.074955]  netlink_sendmsg+0x232/0x400
[  406.074962]  sock_sendmsg+0x5e/0x60
[  406.074966]  __sys_sendto+0xee/0x160
[  406.074975]  ? ep_modify+0xb6/0x170
[  406.074982]  ? syscall_trace_enter+0x131/0x2c0
[  406.074987]  __x64_sys_sendto+0x25/0x30
[  406.075001]  do_syscall_64+0x52/0x160
[  406.075007]  entry_SYSCALL_64_after_hwframe+0x44/0xa9
[  406.075010] RIP: 0033:0x7fac993f566d
[  406.075013] Code: ff ff ff ff eb bc 0f 1f 80 00 00 00 00 48 8d 05 79 3d 0c 
00 41 89 ca 8b 00 85 c0 75 20 45 31 c9 45 31 c0 b8 2c 00 00 00 0f 05 <48> 3d 00 
f0 ff ff 77 6b c3 66 2e 0f 1f 84 00 00 00 00 00 55 48 83
[  406.075014] RSP: 002b:7fff8b471db8 EFLAGS: 0246 ORIG_RAX: 
002c
[  406.075017] RAX: ffda RBX: 56152b002890 RCX: 7fac993f566d
[  406.075018] RDX: 0098 RSI: 56152b022240 RDI: 0004
[  406.075019] RBP: 56152b016310 R08:  R09: 
[  406.075021] R10: 00

Bug#948632: rust-bcder: Build-depends on older rust-smallvec than is in unstable

[Steve Langasek]

Source: rust-bcder
Version: 0.4.1-1
Severity: serious
User: ubuntu-de...@lists.ubuntu.com
Usertags: origin-ubuntu focal

rust-bcder build-depends on librust-smallvec-0.6+default-dev, but
rust-smallvec is now at version 1.1 in unstable:

$ sudo apt build-dep rust-bcder
Reading package lists... Done
Reading package lists... Done
Building dependency tree   
Reading state information... Done
Some packages could not be installed. This may mean that you have
requested an impossible situation or if you are using the unstable
distribution that some required packages have not yet been created
or been moved out of Incoming.
The following information may help to resolve the situation:

The following packages have unmet dependencies:
 builddeps:rust-bcder : Depends: librust-smallvec-0.6+default-dev (>= 
0.6.10-~~) but it is not installable
E: Unable to correct problems, you have held broken packages.
$

Please update rust-bcder for compatibility with the current
rust-smallvec.

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


signature.asc
Description: PGP signature

Bug#938807: wammu: Python2 removal in sid/bullseye

[Scott Talbert]

On Fri, Aug 30, 2019 at 07:58:21AM +, Matthias Klose wrote:
> Package: src:wammu
> Version: 0.44-1.1
> Severity: normal
> Tags: sid bullseye
> User: debian-pyt...@lists.debian.org
> Usertags: py2removal
> 
> Python2 becomes end-of-live upstream, and Debian aims to remove
> Python2 from the distribution, as discussed in
> https://lists.debian.org/debian-python/2019/07/msg00080.html

Hi Michal,

I started to work on porting wammu to Python3 / wxPython4, but then I 
realized I'm not really going to be able to test it well, and if you're not
interesting in maintaining it going forward, then maybe perhaps the best
plan is just to RM it from Debian.  What do you think?

Scott

Bug#773979: cheese: Video unusable [was: Re: cheese: Picture freezes and webcam turns off when clicking on "record video"]

[Ralph Katz]

Package: cheese
Version: 3.31.90-1
Followup-For: Bug #773979

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Dear Maintainer,


Picture taking and Burst picture  taking work.  Video does not work.
Starting video recording freezes the image shown on screen and freezes cheese
itself.  Cheese must be killed by closing its window.

xfce4 is the desktop environment.

Syslog shows the following error at the time of the freeze:
Jan 10 18:44:42 spike3 pulseaudio[1423]: E: [alsa-source-ALC3246 Analog] alsa-
source.c: Error opening PCM device front:0: Device or resource busy

Thanks!




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

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

Versions of packages cheese depends on:
ii  cheese-common  3.31.90-1
ii  gnome-video-effects0.4.3-3
ii  libc6  2.28-10
ii  libcanberra-gtk3-0 0.30-7
ii  libcheese-gtk253.31.90-1
ii  libcheese8 3.31.90-1
ii  libclutter-1.0-0   1.26.2+dfsg-10
ii  libclutter-gtk-1.0-0   1.8.4-4
ii  libgdk-pixbuf2.0-0 2.38.1+dfsg-1
ii  libglib2.0-0   2.58.3-2+deb10u2
ii  libgnome-desktop-3-17  3.30.2.1-2
ii  libgstreamer1.0-0  1.14.4-1
ii  libgtk-3-0 3.24.5-1

Versions of packages cheese recommends:
ii  gvfs  1.38.1-5
ii  yelp  3.31.90-1

Versions of packages cheese suggests:
pn  gnome-video-effects-frei0r  

- -- no debconf information

-BEGIN PGP SIGNATURE-

iQJIBAEBCgAyFiEEJQZ8vK6BnmDiW8fZyAJ5DhtfJxAFAl4ZLLQUHHJhbHBoQHJh
bHBoa2F0ei5jb20ACgkQyAJ5DhtfJxCIMxAA0TnO+G+pNHF0dGQmlg/RxJtHK8j9
egydTGj856OYLSawHxQ5t7aAaz1H2Z3092MAyU/hs1JCdmiNibCe20WisrmVmRKN
QmsIMNWPMh8dwQ8Z2D4nc/7+scER84hF1l/b7Ds/htcgFHe1n839lg41YQmfyGC7
FAB9x1gekHDT7FTxryaqgcIIsGBjpQ7ZH3Wep/55Ot6NLyHrvQDFq997lRPa+WKD
k/+2G+Su5rz1GVyT+zS9Fl16kal9fondjc18jxzfJF26jIUJ2PBQuYAOeW2nYl27
TreIENt6bz1zOSjOV94it+Oa5pQbTFAjRRO6TOdvRKTjxxD3nTBaUOM9ScnJ5pDB
9ZNCvolhTwzoSXmLkeHfhWff5QSTuJUrmbGyvLtbcP9IUKX/whd1sa8krYfZLUV4
XxbmJFqxTnM9Hok22vPt47TSB6LXm3CLyvCKvd5RlML8bEuj8vRdhpGE3wi9zE0N
rQ8Jl+C5o6q6d32mYddGb/yi48pqi9EPwgDFYmm6wFncfib1slyOZR+BhX3/11B6
Sodryiea4D6mtxCGRMOOZnjBQIBpXZ76h2DqxC3DoLk65zsKte0jZXR2pWWpJ0H0
A8c68flVfo+bRk+i0O9u6h9fYPJkwXgsXziWcCMBSQrCfdI6EMLjosE6y2nKOM9v
0v4QB6S3zO6LxdU=
=+wE0
-END PGP SIGNATURE-

Bug#946931: [Pkg-kde-extras] Bug#946931: Bug#946931: quassel-core: apparmor denials

[Scott Kitterman]

I gave this a try and I still get apparmor denials:

Jan 10 20:54:13 relay02 kernel: [ 1372.562938] audit: type=1400 
audit(1578707653.245:28): apparmor="DENIED" operation="open" profile="/usr/bin/
quasselcore" name="/proc/sys/kernel/random/boot_id" pid=1588 
comm="quasselcore" requested_mask="r" denied_mask="r" fsuid=116 ouid=0

Jan 10 20:54:13 relay02 kernel: [ 1372.562955] audit: type=1400 
audit(1578707653.245:29): apparmor="DENIED" operation="open" profile="/usr/bin/
quasselcore" name="/var/lib/dbus/machine-id" pid=1588 comm="quasselcore" 
requested_mask="r" denied_mask="r" fsuid=116 ouid=0

Jan 10 20:54:13 relay02 kernel: [ 1372.576629] audit: type=1400 
audit(1578707653.257:30): apparmor="DENIED" operation="link" profile="/usr/bin/
quasselcore" name="/var/lib/quassel/quasselcore.conf" pid=1588 
comm="quasselcore" requested_mask="l" denied_mask="l" fsuid=116 ouid=116 
target="/var/lib/quassel/#523668"

Suggestions?

Scott K

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

Bug#948631: rust-web-sys: Build-depends on older rust-wasm-bindgen-webidl than is in unstable

[Steve Langasek]

Source: rust-web-sys
Version: 0.3.28-1.1
Severity: serious
User: ubuntu-de...@lists.ubuntu.com
Usertags: origin-ubuntu focal

rust-web-sys build-depends on
librust-wasm-bindgen-webidl-0.2.51+default-dev, but rust-wasm-bindgen-webidl
is now at version 0.2.58 in unstable:

$ sudo apt build-dep rust-web-sys
Reading package lists... Done
Reading package lists... Done
Building dependency tree   
Reading state information... Done
Some packages could not be installed. This may mean that you have
requested an impossible situation or if you are using the unstable
distribution that some required packages have not yet been created
or been moved out of Incoming.
The following information may help to resolve the situation:

The following packages have unmet dependencies:
 builddeps:rust-web-sys : Depends: librust-failure-0.1+default-dev (>= 0.1.2-~~)
  Depends: 
librust-wasm-bindgen-webidl-0.2.51+default-dev but it is not installable
E: Unable to correct problems, you have held broken packages.
$

Please update rust-web-sys for compatibility with the current
rust-wasm-bindgen-webidl.

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


signature.asc
Description: PGP signature

Bug#944476: LKRG Debian packaging completed

[John Scott]

> I am not a Debian Developer (DD). This needs a DD to be uploaded to
> packages.debian.org.

If you are still looking for someone that can upload this for you, file a bug
against sponsorship-requests and block this bug by that one.

Bug#897196: Bug#948598: mingw-w64-i686-dev: non-conforming snprintf function in case of truncation

[Vincent Lefevre]

Control: reassign 948598 src:mingw-w64 7.0.0-2
Control: forcemerge 897196 948598

On 2020-01-10 23:18:09 +0100, Stephen Kitt wrote:
> Control: merge -1 897196
> 
> Hi,
> 
> On Fri, 10 Jan 2020 22:43:27 +0100, Bernhard Übelacker
>  wrote:
> > In the regular case the resulting exe seems to link
> > to msvcrt.dll!_vsnprintf:
> > 
> >$ i686-w64-mingw32-objdump --private-headers test.c.exe
> > DLL Name: msvcrt.dll
> > vma:  Hint/Ord Member-Name Bound-To
> > 63e8  766  _vsnprintf
> > 
> > Under wine we then get to that location:
> >#0  0x7eb514d6 in MSVCRT_vsnprintf (str=0x65fe64 "", len=3,
> > format=0x40400b "abcdef", valist=0x65fe5c "+\026@")
> > at /home/benutzer/wine/wine-git/wine-git/dlls/msvcrt/wcs.c:686
> > 
> > The resulting executables are showing the same output
> > in wine and windows.
> 
> Yes; this is a bug in MSVCRT.
> 
> > In the posix case it seems the snprintf implementation is
> > not taken from any dll, instead it is contained inside
> > the executable, therefore supplied by the compiler?
> > 
> > Microsoft states [1], that they switched in VS2015 snprintf
> > to be C99 compliant, wouldn't therefore snprintf in msvcrt.dll
> > not compliant?

Yes, it seems to be the remaining case where snprintf is not
C99 compliant.

FYI, in the past, we had to build GMP and GNU MPFR with
-D__USE_MINGW_ANSI_STDIO (or equivalent). Now, this is working
correctly, except in the particular case of GMP 6.1.2 built with
assertions enabled. Internally, GMP 6.1.2 assumes that a return value
of -1 means that the size was too small (in the past, this was due to
the behavior of some old glibc version). With assertions enabled,
there is another check that was working with glibc, but fails with
MinGW, and worse, this triggers a buffer overflow as the assertion
uses strlen while vsnprintf under MinGW does not return a string
(no terminating \0).

> > Is this issue in the end that mingw should link to
> > newer c-library by default?
> 
> I’m not sure what the exact fix should be, apart from building with -posix
> or #define __USE_MINGW_ANSI_STDIO 1. This is filed upstream as
> https://sourceforge.net/p/mingw-w64/bugs/709/ (and CVE-2018-1000101), and
> apparently MSVCRT’s vsnprintf does the right thing now, but I haven’t had the
> time to figure out how to use that correctly yet.

Indeed, concerning the security issue, GMP 6.1.2 is such an example
where one can get a buffer overflow.

Note that the GMP development code has changed due to another issue
I reported two years ago.

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

Bug#948630: rust-grcov: Build-depends on older rust-crossbeam than is in unstable

[Steve Langasek]

Source: rust-grcov
Version: 0.4.1-2
Severity: serious
User: ubuntu-de...@lists.ubuntu.com
Usertags: origin-ubuntu focal

As seen at https://buildd.debian.org/status/package.php?p=rust%2dgrcov,
rust-grcov 0.4.1-2 is not built on any architectures, because it
build-depends on librust-crossbeam-0.4+default-dev but rust-crossbeam in
unstable is now at version 0.7.

Please update rust-grcov for compatibility with the current rust-crossbeam.

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


signature.asc
Description: PGP signature

Bug#874880: FreeMedForms projet

[Michael Lustfield]

It looks like this bug went from "Qt4->Qt5" to "no longer DFSG-free."

On Fri, 10 Jan 2020 17:34:35 +0100
Eric Maeker  wrote:

> Oh! There is a misunderstanding here!
> Let me correct my words:
> -> full code of each stable released version is packaged and freely  
> available (but undocumented since v1.0.0).

From: https://freemedforms.com/en/downloads/root

"Downloads are 100% compatible with the Debian social contract."

From: https://freemedforms.com/fr/downloads/root (translated)

"Since v1.1.0, some files are available under a license incompatible with
the social contract of Debian . If you are looking for software 100%
compatible with this contract, please refer to v1.0.0."

Without digging in too deep...
- You mentioned documentation removal in 1.0.0
- This page mentions DFSG-freeness was broken in 1.1.0

If these were two distinct periods of time, that would lead me to suspect
additional files were added that broke compatibility with the DFSG.

> We know that at least two forks exists (this is what our private data
> server's log tells us). We do not receive any patch, invitation to git
> repos, or any kind of official informations or queries.

This could definitely be a language barrier problem, but I don't follow. Why
are you concerned about forks? If you have quality open source software, then
people will fork it. Sometimes patches will be sent back upstream, other times
they won't be.

Take a look here: https://people.debian.org/~bap/dfsg-faq.html
Particularly at 9a (The Desert Island Test)

Demanding that all modifications be shared with you very clearly fails this
test, and is not actually part of the license you applied to the software.

> In consequence, we decide that our git repository will not be freely
> accessible. Approval does only concern the FreeMedForms' git and the
> ability to join the project as member (coder, tester, communication
> manager...).

It's probably worth noting, a public repository is recommended, but not
required for inclusion in Debian repositories. However, inclusion of source is
an absolute requirement.

This "documentation" that was removed seems to be much more than just developer
docs; I'm unable to find any non-header comments in any file.

If you look at how javascript is handled, any minified version is considered
compiled source. You are essentially doing the exact same to your source when
you release it. It's not the actual source... it's just some partial version of
it. In this case, with intentional obfuscation.



This could still make it into non-free, however, I'd urge you to reconsider
your motivations for releasing obfuscated source and refusing to share. Is it
really your desire to make software that's (per DFSG) not free?


-- 
Michael Lustfield

Bug#938081: python-pyo: diff for NMU version 1.0.0-2.1

[Sandro Tosi]

Control: tags 938081 + patch


Dear maintainer,

I've prepared an NMU for python-pyo (versioned as 1.0.0-2.1). The diff
is attached to this message.

Regards.

diff -Nru python-pyo-1.0.0/debian/changelog python-pyo-1.0.0/debian/changelog
--- python-pyo-1.0.0/debian/changelog	2019-10-05 14:58:39.0 -0400
+++ python-pyo-1.0.0/debian/changelog	2020-01-10 20:23:01.0 -0500
@@ -1,3 +1,10 @@
+python-pyo (1.0.0-2.1) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * Drop python2 support; Closes: #938081
+
+ -- Sandro Tosi   Fri, 10 Jan 2020 20:23:01 -0500
+
 python-pyo (1.0.0-2) unstable; urgency=medium
 
   * Fix epyo script overwriting.
diff -Nru python-pyo-1.0.0/debian/control python-pyo-1.0.0/debian/control
--- python-pyo-1.0.0/debian/control	2019-10-05 13:51:19.0 -0400
+++ python-pyo-1.0.0/debian/control	2020-01-10 20:22:37.0 -0500
@@ -3,34 +3,12 @@
 Priority: optional
 Maintainer: Debian Multimedia Maintainers 
 Uploaders: Tiago Bortoletto Vaz 
-Build-Depends: debhelper (>= 10), portaudio19-dev, libportmidi-dev, liblo-dev, libsndfile1-dev, libjack-jackd2-dev, dh-python, python-all-dev, python-setuptools, python3-all-dev, python3-setuptools
+Build-Depends: debhelper (>= 10), portaudio19-dev, libportmidi-dev, liblo-dev, libsndfile1-dev, libjack-jackd2-dev, dh-python, python3-all-dev, python3-setuptools
 Standards-Version: 3.9.6
 Vcs-Browser: https://salsa.debian.org/multimedia-team/python-pyo
 Vcs-Git: https://salsa.debian.org/multimedia-team/python-pyo.git
 Homepage: http://ajaxsoundstudio.com/software/pyo/
 
-Package: python-pyo
-Architecture: any
-Depends: python (>= 2.6), ${shlibs:Depends}, ${misc:Depends}, ${python:Depends}
-Recommends: python-tk, python-imaging-tk, python-wxgtk3.0, jackd2
-Description: Python module written in C to help digital signal processing script creation
- pyo is a Python module containing classes for a wide variety of audio signal
- processing types. With pyo, user will be able to include signal processing
- chains directly in Python scripts or projects, and to manipulate them in real
- time through the interpreter. Tools in pyo module offer primitives, like
- mathematical operations on audio signal, basic signal processing (filters,
- delays, synthesis generators, etc.), but also complex algorithms to create
- sound granulation and others creative audio manipulations.
- .
- pyo supports OSC protocol (Open Sound Control), to ease communications between
- softwares, and MIDI protocol, for generating sound events and controlling
- process parameters.
- .
- pyo allows creation of sophisticated signal processing chains with all the
- benefits of a mature, and wildly used, general programming language.
- .
- This package installs the library for Python 2.
-
 Package: python3-pyo
 Architecture: any
 Depends: ${shlibs:Depends}, ${misc:Depends}, ${python3:Depends}
diff -Nru python-pyo-1.0.0/debian/python3-pyo.install python-pyo-1.0.0/debian/python3-pyo.install
--- python-pyo-1.0.0/debian/python3-pyo.install	2019-10-05 13:49:41.0 -0400
+++ python-pyo-1.0.0/debian/python3-pyo.install	1969-12-31 19:00:00.0 -0500
@@ -1,3 +0,0 @@
-debian/epyo3  usr/bin
-debian/E-Pyo-py3.desktop  usr/share/applications
-debian/E-Pyo-py3.xpm  usr/share/pixmaps
diff -Nru python-pyo-1.0.0/debian/python-pyo.install python-pyo-1.0.0/debian/python-pyo.install
--- python-pyo-1.0.0/debian/python-pyo.install	2019-10-05 13:47:31.0 -0400
+++ python-pyo-1.0.0/debian/python-pyo.install	1969-12-31 19:00:00.0 -0500
@@ -1,3 +0,0 @@
-debian/epyo2 usr/bin
-debian/E-Pyo-py2.desktop  usr/share/applications
-debian/E-Pyo-py2.xpm  usr/share/pixmaps
diff -Nru python-pyo-1.0.0/debian/rules python-pyo-1.0.0/debian/rules
--- python-pyo-1.0.0/debian/rules	2019-10-05 14:47:11.0 -0400
+++ python-pyo-1.0.0/debian/rules	2020-01-10 20:22:45.0 -0500
@@ -3,7 +3,7 @@
 export PYBUILD_NAME=pyo
 
 %:
-	dh $@ --with python2,python3 --buildsystem=pybuild
+	dh $@ --with python3 --buildsystem=pybuild
 
 #override_dh_auto_build:
 #	set -e; \

Bug#948629: rpcbind: please say that the -r flag is a Debian extension

[Daniel Shahaf]

Package: rpcbind
Version: 1.2.5-8
Severity: normal
Tags: patch

Dear Maintainer,

Since the -r flag is added as a Debian patch, please document that it's
a Debian extension.  Here's the patch against current git:

diff --git a/debian/patches/00-rmt-calls.patch 
b/debian/patches/00-rmt-calls.patch
index 0ed215f..592291e 100644
--- a/debian/patches/00-rmt-calls.patch
+++ b/debian/patches/00-rmt-calls.patch
@@ -99,7 +99,7 @@ Last-Update: 2019-09-17
 +Turn on remote calls. Cause
 +.Nm
 +to open up random listening ports. Note that rpcinfo need this feature turned 
on
-+for work properly.
++for work properly. (This flag is a Debian extension.)
  .El
  .Sh NOTES
  All RPC servers must be restarted if

Cheers,

Daniel

Bug#733573: ssh: Doesn't use the key from -i when using an agent.

[Daniel Shahaf]

Kurt Roeckx wrote on Mon, Dec 30, 2013 at 01:53:39 +0100:
> Package: openssh-client
> Version: 1:6.4p1-1
> 
> Hi,
> 
> When I use ssh with the -i option to use a different key, it seems
> to be offering my default key anyway.  It seems this is only the
> case when an ssh-agent is running.  The key that is given isn't
> added to the agent.
> 
> ssh -v shows:
> debug1: identity file other_key type 1
> debug1: Checking blacklist file /usr/share/ssh/blacklist.RSA-4096
> debug1: Checking blacklist file /etc/ssh/blacklist.RSA-4096
> debug1: identity file other_key-cert type -1
> [...]
> debug1: Authentications that can continue: publickey
> debug1: Next authentication method: publickey
> debug1: Offering RSA public key: /home/kurt/.ssh/id_rsa
> 
> When ssh doesn't know about my running ssh-agent, it will offer
> the key given with -i.

Looks like a duplicate of #203700 and #513235; a workaround is to set
IdentitiesOnly=yes in ssh_config(5).

Cheers,

Daniel

Bug#884156: xrdp: XRDP Sesman not listening on IPv4

[Thorsten Glaser]

tags 884156 + moreinfo
thanks

Hi,

are you on GNU/kFreeBSD?

On Linux, when listening on :: you’ll also get all IPv4 connections.

bye,
//mirabilos
-- 
[...] if maybe ext3fs wasn't a better pick, or jfs, or maybe reiserfs, oh but
what about xfs, and if only i had waited until reiser4 was ready... in the be-
ginning, there was ffs, and in the middle, there was ffs, and at the end, there
was still ffs, and the sys admins knew it was good. :)  -- Ted Unangst über *fs

Bug#924310: xrdp: post-install script fails

[Thorsten Glaser]

Hi,

it says “A dependency job for xrdp.service failed.” so I believe that
some *other* service xrdp.service depends on had failed earlier and
so your system is in a weird state, maybe?

bye,
//mirabilos
-- 
15:39⎜«mika:#grml» mira|AO: "mit XFree86® wär’ das nicht passiert" - muhaha
15:48⎜ also warum machen die xorg Jungs eigentlich alles
kaputt? :)15:49⎜ thkoehler: weil sie als Kinder nie den
gebauten Turm selber umschmeissen durften?  -- ~/.Xmodmap wonders…

Bug#948584: libc6: Mounting nfsv4-export from my NAS there is a segfault in libc

[Miriam Winterling]

Hello Bernhard.


Am Freitag, den 10.01.2020, 20:31 +0100 schrieb Bernhard Übelacker:
> Hello Miriam,
> if possible, you could install the additional package
> systemd-coredump. Then in the output of 'journalctl --no-pager'
> at the bottom should the known 'segfault at' line appear.
> This and the following lines at that time would be of interest.
> 
I did install systemd-coredump and the result you can see in the attached
file #948584_systemd_journalctl.txt.

> This would get better if the additional nfs-common-dbgsym
> could be installed [1] (from a separate repo).
> 
I also installed nfs-common-dbgsym.


> If additonal to the above steps the package gdb is installed,
> 'coredumpctl gdb' with the command 'bt full' at the gdb prompt
> would yield even better information.
> 
I tried to do this, too. My result is in #948584_coredumpctl_dbg.txt.

I'm a complete Newbie in this sector of administrating Linux systems, so
I hope, that i have made it right, so that the information is sufficient.


> Kind regards,
> Bernhard
> 
> [1] 
> https://wiki.debian.org/HowToGetABacktrace#Installing_the_debugging_symbols


Kind regards,
Miriam
Jan 11 00:31:29 workstation-mirulan-net systemd[1]: Mounting Mount MiruNAS 
Medienwerkstatt...
Jan 11 00:31:29 workstation-mirulan-net kernel: mount.nfs[6399]: segfault at 0 
ip 7fcbea68fd35 sp 7ffe2b34d8e8 error 4 in 
libc-2.29.so[7fcbea55c000+147000]
Jan 11 00:31:29 workstation-mirulan-net kernel: Code: 48 83 e0 3f c5 f9 6f 25 
d9 35 03 00 c5 f9 6f 2d 01 36 03 00 c5 f9 6f 35 e9 35 03 00 83 f9 30 77 64 83 
f8 30 77 5f c5 fa 6f 0f  fa 6f 16 c5 f1 64 fc c5 71 64 c5 c5 69 64 cc c5 69 
64 d5 c5 39
Jan 11 00:31:29 workstation-mirulan-net systemd[1]: Created slice 
system-systemd\x2dcoredump.slice.
Jan 11 00:31:29 workstation-mirulan-net systemd[1]: Started Process Core Dump 
(PID 6400/UID 0).
Jan 11 00:31:30 workstation-mirulan-net systemd[1]: 
media-MiruNAS-Medienwerkstatt.mount: Mount process exited, code=exited, 
status=255/EXCEPTION
Jan 11 00:31:30 workstation-mirulan-net systemd[1]: 
media-MiruNAS-Medienwerkstatt.mount: Failed with result 'exit-code'.
Jan 11 00:31:30 workstation-mirulan-net systemd[1]: Failed to mount Mount 
MiruNAS Medienwerkstatt.
Jan 11 00:31:30 workstation-mirulan-net systemd-coredump[6401]: Process 6399 
(mount.nfs) of user 0 dumped core.

Stack trace of 
thread 6399:
#0  
0x7fcbea68fd35 __strcasecmp_l_avx (libc.so.6 + 0x158d35)
#1  
0x559dd1170dd9 n/a (mount.nfs + 0x12dd9)
#2  
0x559dd116aef5 n/a (mount.nfs + 0xcef5)
#3  
0x559dd116b3af n/a (mount.nfs + 0xd3af)
#4  
0x559dd1162fc2 n/a (mount.nfs + 0x4fc2)
#5  
0x7fcbea55dbbb __libc_start_main (libc.so.6 + 0x26bbb)
#6  
0x559dd116331a n/a (mount.nfs + 0x531a)
Jan 11 00:31:30 workstation-mirulan-net systemd[1]: 
systemd-coredump@0-6400-0.service: Succeeded.
Jan 11 00:31:38 workstation-mirulan-net systemd[1]: Starting Cleanup of 
Temporary Directories...
Jan 11 00:31:38 workstation-mirulan-net systemd-tmpfiles[6408]: 
/usr/lib/tmpfiles.d/speech-dispatcher.conf:1: Line references path below legacy 
directory /var/run/, updating /var/run/speech-dispatcher → 
/run/speech-dispatcher; please update the tmpfiles.d/ drop-in file accordingly.
Jan 11 00:31:38 workstation-mirulan-net systemd-tmpfiles[6408]: 
/usr/lib/tmpfiles.d/speech-dispatcher.conf:2: Line references path below legacy 
directory /var/run/, updating /var/run/speech-dispatcher/.cache → 
/run/speech-dispatcher/.cache; please update the tmpfiles.d/ drop-in file 
accordingly.
Jan 11 00:31:38 workstation-mirulan-net systemd-tmpfiles[6408]: 
/usr/lib/tmpfiles.d/speech-dispatcher.conf:3: Line references path below legacy 
directory /var/run/, updating /var/run/speech-dispatcher/.speech-dispatcher → 
/run/speech-dispatcher/.speech-dispatcher; please update the tmpfiles.d/ 
drop-in file accordingly.
Jan 11 00:31:38 workstation-mirulan-net systemd-tmpfiles[6408]: 
/usr/lib/tmpfiles.d/speech-dispatcher.conf:4: Line references path below legacy 
directory /var/run/, updating 
/var/run/speech-dispatcher/.cache/speech-dispatcher → 
/run/speech-dispatcher/.cache/speech-dispatcher; please update the tmpfiles.d/ 
drop-in file accordingly.
Jan 11 00:31:38 workstation-mirulan-net systemd-tmpfiles[6408]: 
/usr/lib/tmpfiles.d/speech-dispatcher.conf:5: Line references path below legacy 
directory /var/run/, updating /var/run/speech-dispatcher/log → 
/run/speech-dispatcher/log; 

Bug#944913: python3-sphinx: Please update to Sphinx 2.2.1

[Sandro Tosi]

Hey Dmitry,
please note that the relatively old version of sphinx we have in
Debian now makes it not possible to upgrade scikit-learn
(https://github.com/scikit-learn/scikit-learn/issues/16087#issuecomment-573092993),
which we require to upgrade as the scikit-learn version we have in
unstable now FTBFS due to other modules/libraries being upgraded,
compatibility which is fixed in the new version and... you got the
idea :)

I understand it may be more work, but i suspect that splitting sphinx
1.8 and 2.* is probably the best way forward to allow continuous
compatibility with already-existing packages and the upgrade of those
modules that require a newer version.

please let me know what you think

On Tue, 24 Dec 2019 22:18:37 -0500 Sandro Tosi  wrote:
> On Sun, Dec 22, 2019 at 4:22 PM Dmitry Shachnev  wrote:
> >
> > Hi Sandro!
> >
> > On Sun, Dec 22, 2019 at 02:47:10PM -0500, Sandro Tosi wrote:
> > > > The current version packaged in Debian is very outdated,
> > > > even in unstable. Please consider packaging the current
> > > > upstream release.
> > >
> > > I'm echoing this request: the just released numpy/1.18.0 requires
> > > sphinx >= 2.2.0, so we cannot upgrade numpy without an updated sphinx.
> > > please consider package it at the earliest.
> >
> > Unfortunately sphinx ≥ 2.0 dropped support for Python 2.
> >
> > So I should either wait until all blocking bugs of #938528 are resolved, or
> > introduce a new source package like sphinx-python2 for the old version.
>
> i think there a quite too many packages blocking 938528 (counts is
> 100), so yeah maybe a src:sphinx2 (to track 1.8.5) and src:sphinx (to
> track 2+) seems like the best solution to keep old packages around and
> not prevent progress for the modules more forward-looking.
>
> > However the latter solution will mean that we can no longer have shared
> > sphinx-common and libjs-sphinxdoc packages, and we will need to have two
> > versions of dh_sphinxdoc too (or one version that will generate different
> > dependencies for old and new sphinx). This is something I wanted to avoid,
> > because it is extra work for supporting a Python 2 version that will be
> > dead in a few days.
>
> hm, that's a good point indeed; i'm not sure we can drop python-sphinx
> and make all of those packages RC
>
> > Recently your script bumped many Python 2 removal bugs to RC, with the
> > intention to accelerate porting those packages to Python 3 (or getting them
> > removed). Maybe better to wait a couple of months and then just upload new
> > Sphinx and break its Python 2 reverse build-dependencies?
>
> only 49 of those 100 blocked packages are currently RC, so it will
> take quite more time i suspect; also some of those packages are sphinx
> extensions, that will have to go at the same time as sphinx maybe?
>
> > Can you patch old Sphinx support into numpy for the time being?
>
> tbh, i'd rather not :) maybe you can consider uploading 2.2+ to
> experimental, just to see if there's any breakage with the new version
> (even for packages already using python3-sphinx), and i can upload
> numpy in experimental
>
> Cheers,
> --
> Sandro "morph" Tosi
> My website: http://sandrotosi.me/
> Me at Debian: http://wiki.debian.org/SandroTosi
> Twitter: https://twitter.com/sandrotosi
>
>

Bug#948619: Bug #948619: file: When building the file package, use the just-built file program in debhelper

[Andreas Beckmann]

On 10/01/2020 22.36, Christoph Biedl wrote:
> bits, like overriding dh_strip (which calls the file binary as well).

The PATH prepend-and-export should cover everything calling the 'file'
binary after override_dh_auto_install target, no need for explicit
override_dh_* targets. It would be more difficult if something is using
libmagic.so.1 via perl/python/linking-against-the-shared-library instead
of calling the 'file' binary from the PATH.


Andreas

Bug#948530: RFS: coinor-vol/1.5.4-1 [QA] -- Coin-or linear programming solver

[Sudip Mukherjee]

HI Mattia,

Thanks for taking a look.

On Fri, Jan 10, 2020 at 5:48 PM Mattia Rizzolo  wrote:
>

>
> Also, you did this:
>
> +override_dh_auto_configure:
> +   ./configure --prefix=${PREFIX} --includedir=${PREFIX}/include 
> --mandir=${PREFIX}/share/man --libdir=${PREFIX}/lib/${DEB_HOST_MULTIARCH} 
> --enable-static --with-dot COIN_SKIP_PROJECTS="Osi CoinUtils OsiVol Sample"
>
>
> why not using dh_auto_configure?

dh_auto_configure sends "--runstatedir=/run" which is not supported in
this configure and so it fails. I could not use dh_auto_configure but
added a comment to d/rules to make it more clear to anyone who looks
at this later.

I think everything else is now done. I have uploaded new package to
mentors. This is the new changelog:

   * QA upload.
   * Update to upstream v1.5.4
   * Rename package based on SONAME major version.
   * Remove dbg package in favor of dbgsym.
   * Mark the package as orphaned (see #645082).
   * Update Standards-Version to 4.4.1
 - Needed a change in the priority.
   * Update compat level to 12
   * Rework of d/* files.
 - Simplify d/rules using dh instead of cdbs.
 - Rewrite d/copyright using copyright-format 1.0.
 - Add symbols file.
 - Update Vcs to salsa.
 - Mark source format as 3.0
 - Add Rules-Requires-Root: no
 - Add hardening flags.
 - Use https in watch file.

Can you please take a look when you get some time..

-- 
Regards
Sudip

Bug#948628: RM: simpletal -- RoQA; python2-only (in debian, upstream has py3k support); orphaned; low popcon; no rdeps

[Sandro Tosi]

Package: ftp.debian.org
Severity: normal

Bug#948627: xwayland: Double pointer and application freeze if I use lenovo pen

[Teo]

Package: xwayland
Version: 2:1.20.6-1
Severity: grave
Tags: upstream
Justification: renders package unusable

I am using a lenovo yoga 520 equipped with a lenovo pen. When I use the latter,
two pointers are created, the first is stopped in the last position that I gave
it from the touchpad, while the second, follows the pen. So far nothing
serious. Except that after a while everything becomes unusable, because single
touches with the pen are detected as a hold (as if the left touchpad button was
held down), then start dragging application icons here and there, until it
doesn't even respond plus the touches, as if it were all freeze. I can't even
anymore restart it normally and I am forced to restart forcefully. I am on
Debian testing, but on the stable branch I had the same problem. I confirm that
everything works properly on xorg, I don't even know the double pointer
problem.



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

Kernel: Linux 5.3.0-3-amd64 (SMP w/8 CPU cores)
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)
LSM: AppArmor: enabled

Versions of packages xwayland depends on:
ii  libaudit1   1:2.8.5-2+b1
ii  libbsd0 0.10.0-1
ii  libc6   2.29-7
ii  libdrm2 2.4.100-4
ii  libepoxy0   1.5.4-1
ii  libgbm1 19.2.6-1
ii  libgcrypt20 1.8.5-3
ii  libgl1  1.1.0-1+b1
ii  libpixman-1-0   0.36.0-1
ii  libselinux1 3.0-1
ii  libsystemd0 244-3
ii  libunwind8  1.2.1-9
ii  libwayland-client0  1.17.0-1
ii  libxau6 1:1.0.8-1+b2
ii  libxdmcp6   1:1.1.2-3
ii  libxfont2   1:2.0.3-1
ii  libxshmfence1   1.3-1
ii  xserver-common  2:1.20.6-1

xwayland recommends no packages.

xwayland suggests no packages.

-- no debconf information

Bug#948017: libguestfs: b-d on python3-all-dev, but not built for all supported Python3 versions

[Hilko Bengen]

control: tag -1 confirmed pending

* Graham Inggs:

> Source: libguestfs
> Version: 1:1.40.2-4
> Severity: normal
> Tags: sid bullseye
> User: debian-pyt...@lists.debian.org
> Usertags: python3.8 python3-all-dev
>
> The package build-depends on python3-all-dev, but does not build
> extensions/libraries for all supported python3 versions.  This
> is seen on the transition tracker for adding python3.8 support [1]
> and creates false positives.

libguestfs' autoconf-based build system checks for python-$MAJOR-$MINOR
using pkg-config. As of Python 3.8, someone seems to have decided to
introduce a separate pkg-config "-embed" flavor and to drop linker
instructions from the "plain" flavor.

I guess I'll have to update the autoconf scripts. Awesome.

Cheers,
-Hilko

Bug#948626: kicad: Closing pcbnew hangs main kicad process

[Paul "LeoNerd" Evans]

Package: kicad
Version: 5.1.5+dfsg1-2
Severity: normal

I can open, use and close eeschema just fine. I can open and use pcbnew
just fine, but when I attempt to close it and return back to the main
toplevel kicad window, the entire process hangs at 100% CPU usage, not
drawing any windows (existing onscreen content gets corrupted). It
remains in this state until SIGINT or SIGTERM.

If run from the terminal there is no printed output of any kind.

Connecting to a process in this state with gdb shows:

  $ gdb --pid 309563
  ...
  Attaching to process 309563
  [New LWP 309564]
  [New LWP 309565]
  [Thread debugging using libthread_db enabled]
  Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
  0x7fec889fa4bc in wxClassInfo::~wxClassInfo() ()
 from /usr/lib/x86_64-linux-gnu/libwx_baseu-3.0.so.0

  (gdb) bt
  #0  0x7fec889fa4bc in wxClassInfo::~wxClassInfo() ()
  at /usr/lib/x86_64-linux-gnu/libwx_baseu-3.0.so.0
  #1  0x7fec88352720 in __run_exit_handlers
  (status=0, listp=0x7fec884cf718 <__exit_funcs>, 
run_list_atexit=run_list_atexit@entry=true, run_dtors=run_dtors@entry=true) at 
exit.c:108
  #2  0x7fec8835285a in __GI_exit (status=) at exit.c:139
  #3  0x7fec8833cbc2 in __libc_start_main (main=
  0x562cef17a880, argc=1, argv=0x7fff6f8f9548, init=, 
fini=, rtld_fini=, stack_end=0x7fff6f8f9538)
  at ../csu/libc-start.c:342
  #4  0x562cef17f12a in _start ()


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

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

Versions of packages kicad depends on:
ii  libc62.29-7
ii  libcairo21.16.0-4
ii  libcurl4 7.67.0-2
ii  libgcc1  1:9.2.1-22
ii  libgl1   1.1.0-1+b1
ii  libglew2.1   2.1.0-4+b1
ii  libglu1-mesa [libglu1]   9.0.1-1
ii  libngspice0  31.3-2
ii  libocct-data-exchange-7.37.3.3+dfsg1-1
ii  libocct-foundation-7.3   7.3.3+dfsg1-1
ii  libocct-modeling-algorithms-7.3  7.3.3+dfsg1-1
ii  libocct-modeling-data-7.37.3.3+dfsg1-1
ii  libocct-ocaf-7.3 7.3.3+dfsg1-1
ii  libpixman-1-00.36.0-1
ii  libpython3.7 3.7.6-1
ii  libstdc++6   9.2.1-22
ii  libwxbase3.0-0v5 3.0.4+dfsg-15
ii  libwxgtk3.0-gtk3-0v5 3.0.4+dfsg-15
ii  python3  3.7.5-1
ii  python3-wxgtk4.0 4.0.7+dfsg-2

Versions of packages kicad recommends:
ii  kicad-demos  5.1.5+dfsg1-2
ii  kicad-libraries  5.1.5+dfsg1-2
ii  xsltproc 1.1.32-2.2

Versions of packages kicad suggests:
ii  extra-xdg-menus  1.0-4
pn  kicad-doc-ca | kicad-doc-de | kicad-doc-en | kicad-doc-es | kicad-d  
pn  kicad-packages3d 

-- no debconf information

Bug#948625: networkx 2.4-3 failing to build on unstable

[Corey Bryant]

Package: networkx
Version: 2.4-3
Severity: normal

Dear Maintainer,

I tried building networkx 2.4-3 and it fails with the following. I noticed 
there are a number of py3 related
patches upstream since the 2.4 release. Perhaps some changes could be picked. 
Seems perhaps we're running
some examples with py2 and that's why they're unable to import graphviz.


The HTML pages are in build/html.
Examples failing as expected:
/build/networkx-2.4/examples/advanced/plot_parallel_betweenness.py failed 
leaving traceback:
Traceback (most recent call last):
  File "/build/networkx-2.4/examples/advanced/plot_parallel_betweenness.py", 
line 77, in 
bt = betweenness_centrality_parallel(G)
  File "/build/networkx-2.4/examples/advanced/plot_parallel_betweenness.py", 
line 57, in betweenness_centrality_parallel
node_chunks))
  File "/usr/lib/python3.7/multiprocessing/pool.py", line 268, in map
return self._map_async(func, iterable, mapstar, chunksize).get()
  File "/usr/lib/python3.7/multiprocessing/pool.py", line 657, in get
raise self._value
  File "/usr/lib/python3.7/multiprocessing/pool.py", line 431, in _handle_tasks
put(task)
  File "/usr/lib/python3.7/multiprocessing/connection.py", line 206, in send
self._send_bytes(_ForkingPickler.dumps(obj))
  File "/usr/lib/python3.7/multiprocessing/reduction.py", line 51, in dumps
cls(buf, protocol).dump(obj)
_pickle.PicklingError: Can't pickle : 
attribute lookup _betmap on __main__ failed


Exception occurred:
  File "/usr/lib/python3/dist-packages/sphinx_gallery/gen_gallery.py", line 
313, in sumarize_failing_examples
"\n" + "-" * 79)
ValueError: Here is a summary of the problems encountered when running the 
examples

Unexpected failing examples:
/build/networkx-2.4/examples/drawing/plot_circular_tree.py failed leaving 
traceback:
Traceback (most recent call last):
  File "/build/networkx-2.4/examples/drawing/plot_circular_tree.py", line 23, 
in 
pos = graphviz_layout(G, prog='twopi', args='')
TypeError: graphviz_layout() got an unexpected keyword argument 'args'


/build/networkx-2.4/examples/pygraphviz/plot_pygraphviz_attributes.py failed 
leaving traceback:
Traceback (most recent call last):
  File "/build/networkx-2.4/examples/pygraphviz/plot_pygraphviz_attributes.py", 
line 34, in 
A = nx.nx_agraph.to_agraph(G)
  File "/build/networkx-2.4/build/lib/networkx/drawing/nx_agraph.py", line 136, 
in to_agraph
'http://pygraphviz.github.io/')
ImportError: ('requires pygraphviz ', 'http://pygraphviz.github.io/')


/build/networkx-2.4/examples/pygraphviz/plot_pygraphviz_simple.py failed 
leaving traceback:
Traceback (most recent call last):
  File "/build/networkx-2.4/examples/pygraphviz/plot_pygraphviz_simple.py", 
line 27, in 
A = nx.nx_agraph.to_agraph(G)# convert to a graphviz graph
  File "/build/networkx-2.4/build/lib/networkx/drawing/nx_agraph.py", line 136, 
in to_agraph
'http://pygraphviz.github.io/')
ImportError: ('requires pygraphviz ', 'http://pygraphviz.github.io/')


/build/networkx-2.4/examples/pygraphviz/plot_pygraphviz_draw.py failed leaving 
traceback:
Traceback (most recent call last):
  File "/build/networkx-2.4/examples/pygraphviz/plot_pygraphviz_draw.py", line 
27, in 
A = nx.nx_agraph.to_agraph(G)# convert to a graphviz graph
  File "/build/networkx-2.4/build/lib/networkx/drawing/nx_agraph.py", line 136, 
in to_agraph
'http://pygraphviz.github.io/')
ImportError: ('requires pygraphviz ', 'http://pygraphviz.github.io/')


---
The full traceback has been saved in /tmp/sphinx-err-cnbjaocp.log, if you want 
to report the issue to the developers.
Please also report this if it was a user error, so that a better error message 
can be provided next time.
A bug report can be filed in the tracker at 
. Thanks!
make[2]: *** [Makefile:46: html] Error 2
make[2]: Leaving directory '/build/networkx-2.4/doc'
make[1]: *** [debian/rules:52: override_dh_sphinxdoc] Error 2
make[1]: Leaving directory '/build/networkx-2.4'
make: *** [debian/rules:7: binary] Error 2
dpkg-buildpackage: error: fakeroot debian/rules binary subprocess returned exit 
status 2


Regards,
Corey

Bug#948519: Info received (Bug#948519: insufficient boot-time entropy on arm64 virtual machines)

[Noah Meyerhans]

Control: tags -1 + patch

Proposed solution submitted as 
https://salsa.debian.org/kernel-team/linux/merge_requests/202

Bug#936924: Moving libsvm to Debian Science team

[Christian Kastner]

Hi all,

On 10.01.20 15:33, Chen-Tse Tsai wrote:
> Yes, my changes are merged.

I checked the package and everything looks pretty good. I just added
some minor polishing of my own.

Very surprisingly, not a single symbol has changed since 3.21 -- no
additions, no removals, no changes. It looks as we will be spared a
transition!

@Andreas: I can't push my changes to master, I get a protected branch
error. Could you please grant me the necessary privileges?

> I won't be able to work on it in the next few days. Thanks for your
> help! If you want, it would be great to add you as an Uploader since you
> know these packages really well.

Done!

There's a lintian info about a missing JAR, but I suspect that has more
to do with the symlink from libsvm-java pointing to libsvm3-java.

I added a simple autopkgtest and it passed. Seeing as the symbols didn't
change a bit, I can see no reason why this couldn't be uploaded as-is,
but I'm tired and I'd like to check it again tomorrow with a fresh pair
of eyes, lest we break something.

Christian

Bug#948618: Changed patch

[Mubashshir]

This is the last changed patch.

Description: Automatically add desktop files to Anbox category.
Author: Ahmad Hasan Mubashshir 
Last-Update: 2020-01-11
Index: anbox-0.0~git20190124/data/desktop/android-settings.desktop
===
--- anbox-0.0~git20190124.orig/data/desktop/android-settings.desktop
+++ anbox-0.0~git20190124/data/desktop/android-settings.desktop
@@ -5,3 +5,4 @@ Terminal=false
 Type=Application
 Name=Android Settings
 GenericName=Android Settings
+Categories=Anbox
Index: anbox-0.0~git20190124/debian/anbox-android.menu
===
--- /dev/null
+++ anbox-0.0~git20190124/debian/anbox-android.menu
@@ -0,0 +1,16 @@
+
+http://www.freedesktop.org/standards/menu-spec/menu-1.0.dtd";>
+
+	Applications
+	
+		anbox-android
+		anbox-android.directory
+		
+			
+Anbox
+anbox.desktop
+			
+		
+	
+
Index: anbox-0.0~git20190124/debian/install
===
--- anbox-0.0~git20190124.orig/debian/install
+++ anbox-0.0~git20190124/debian/install
@@ -1,6 +1,7 @@
 debian/anbox-container-manager.service /lib/systemd/system/
 debian/anbox-session-manager.service /usr/lib/systemd/user/
 debian/anbox.desktop /usr/share/applications/
+debian/anbox-android.menu /etc/xdg/menus/applications-merged/
 debian/anbox.png /usr/share/pixmaps/
 scripts/anbox-bridge.sh /usr/share/anbox/
 scripts/anbox-shell.sh /usr/share/anbox/
Index: anbox-0.0~git20190124/src/anbox/application/launcher_storage.cpp
===
--- anbox-0.0~git20190124.orig/src/anbox/application/launcher_storage.cpp
+++ anbox-0.0~git20190124/src/anbox/application/launcher_storage.cpp
@@ -94,10 +94,11 @@ void LauncherStorage::add_or_update(cons
   const auto item_icon_path = path_for_item_icon(package_name);
   if (auto desktop_item = std::ofstream(path_for_item(package_name).string())) {
 desktop_item << "[Desktop Entry]" << std::endl
+ << "Type=Application" << std::endl
  << "Name=" << item.name << std::endl
  << "Exec=" << exec << std::endl
  << "Terminal=false" << std::endl
- << "Type=Application" << std::endl
+ << "Categories=Anbox;" << std::endl
  << "Icon=" << item_icon_path.string() << std::endl;
   } else {
 BOOST_THROW_EXCEPTION(std::runtime_error("Failed to create desktop item"));

Bug#936535: flup: Python2 removal in sid/bullseye

[Emmanuel Arias]

Hi,

The last upstream release version was on 2009 [1]. Seems to be not longer
supported.

And there is not python3 version.

I believe that should be use the forks mentioned on:
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=873492

[1] https://www.saddi.com/software/flup/dist/ChangeLog


Cheers,
Arias Emmanuel
@eamanu
yaerobi.com

Bug#948598: mingw-w64-i686-dev: non-conforming snprintf function in case of truncation

[Stephen Kitt]

Control: merge -1 897196

Hi,

On Fri, 10 Jan 2020 22:43:27 +0100, Bernhard Übelacker
 wrote:
> In the regular case the resulting exe seems to link
> to msvcrt.dll!_vsnprintf:
> 
>$ i686-w64-mingw32-objdump --private-headers test.c.exe
> DLL Name: msvcrt.dll
> vma:  Hint/Ord Member-Name Bound-To
> 63e8  766  _vsnprintf
> 
> Under wine we then get to that location:
>#0  0x7eb514d6 in MSVCRT_vsnprintf (str=0x65fe64 "", len=3,
> format=0x40400b "abcdef", valist=0x65fe5c "+\026@")
> at /home/benutzer/wine/wine-git/wine-git/dlls/msvcrt/wcs.c:686
> 
> The resulting executables are showing the same output
> in wine and windows.

Yes; this is a bug in MSVCRT.

> In the posix case it seems the snprintf implementation is
> not taken from any dll, instead it is contained inside
> the executable, therefore supplied by the compiler?
> 
> Microsoft states [1], that they switched in VS2015 snprintf
> to be C99 compliant, wouldn't therefore snprintf in msvcrt.dll
> not compliant?
> 
> Is this issue in the end that mingw should link to
> newer c-library by default?

I’m not sure what the exact fix should be, apart from building with -posix
or #define __USE_MINGW_ANSI_STDIO 1. This is filed upstream as
https://sourceforge.net/p/mingw-w64/bugs/709/ (and CVE-2018-1000101), and
apparently MSVCRT’s vsnprintf does the right thing now, but I haven’t had the
time to figure out how to use that correctly yet.

Regards,

Stephen


pgpNwCtBc1dUt.pgp
Description: OpenPGP digital signature

Bug#948624: soapysdr0.7-module-all doesn't depend on soapysdr0.7-module-mirisdr and soapysdr0.7-module-rfspace

[Daniele Forsi]

Package: soapysdr0.7-module-all
Version: 0.7.1-3
Severity: normal

Dear Maintainer,

installing teh soapysdr-module-all or teh soapysdr0.7-module-all package 
doesn't install
soapysdr0.7-module-mirisdr and soapysdr0.7-module-rfspace

thanks,
Daniele

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

Kernel: Linux 5.3.0-3-amd64 (SMP w/2 CPU cores)
Kernel taint flags: TAINT_OOT_MODULE, TAINT_UNSIGNED_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 /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages soapysdr0.7-module-all depends on:
ii  soapysdr0.7-module-airspy 0.1.2-2
ii  soapysdr0.7-module-audio  0.1.1-2
ii  soapysdr0.7-module-bladerf0.4.1-2
ii  soapysdr0.7-module-hackrf 0.3.3-3
ii  soapysdr0.7-module-lms7   19.04.0+dfsg-3
ii  soapysdr0.7-module-osmosdr0.2.5-3
ii  soapysdr0.7-module-redpitaya  0.1.1-2
ii  soapysdr0.7-module-remote 0.5.1-2
ii  soapysdr0.7-module-rtlsdr 0.3.0-2
ii  soapysdr0.7-module-uhd0.3.6-2

soapysdr0.7-module-all recommends no packages.

soapysdr0.7-module-all suggests no packages.

-- no debconf information

Bug#936243: brutespray: Python2 removal in sid/bullseye

[Emmanuel Arias]

Package: brutespray
Version: 1.6.4-1
Followup-For: Bug #936243

Dear Maintainer,

I was working on python2 support remove. I prepare a NMU in two MR:

https://salsa.debian.org/pkg-security-team/brutespray/merge_requests/1
https://salsa.debian.org/pkg-security-team/brutespray/merge_requests/2

Please, consider apply it.

Cheer, 
Emmanuel

Bug#939989: transition: gdal

[Sebastiaan Couwenberg]

On 1/9/20 6:52 PM, Sebastiaan Couwenberg wrote:
> On 1/8/20 4:53 PM, Sebastiaan Couwenberg wrote:
>> gdal (3.0.2+dfsg-1) is now built & installed on all release architectures.
>>
>> Please schedule the binNMUs.
> 
> Thanks for scheduling the initial batch, everything has built now.
> Please schedule the rest of Dependency level 1.

Now that pdal is built everywhere, please schedule grass & paraview.

Kind Regards,

Bas

-- 
 GPG Key ID: 4096R/6750F10AE88D4AF1
Fingerprint: 8182 DE41 7056 408D 6146  50D1 6750 F10A E88D 4AF1



signature.asc
Description: OpenPGP digital signature

Bug#948621: RFS: synthv1/0.9.12-1 -- old-school polyphonic synthesizer - standalone/lv2

[Dennis Braun]

Package: sponsorship-requests
Severity: normal

Dear mentors,

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

 * Package name: synthv1
   Version : 0.9.12-1
   Upstream Author : Rui Nuno Capela 
 * URL : https://synthv1.sourceforge.io/
 * License : GPL-2+
 * Vcs : https://salsa.debian.org/multimedia-team/synthv1
   Section : sound

It builds those binary packages:

  synthv1 - old-school polyphonic synthesizer - standalone
  synthv1-lv2 - old-school polyphonic synthesizer - LV2 plugin
  synthv1-common - old-school polyphonic synthesizer - common files

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

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

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

  dget -x 
https://mentors.debian.net/debian/pool/main/s/synthv1/synthv1_0..9.12-1.dsc

Changes since the last upload:

   * Team upload
   * New upstream version 0.9.12
 .
   [ Felipe Sateler ]
   * Change maintainer address to debian-multime...@lists.debian.org
 .
   [ Ondřej Nový ]
   * Use debhelper-compat instead of debian/compat
   * debian/control: Set Vcs-* to salsa.debian.org
   * debian/copyright: Use https protocol in Format field
 .
   [ Dennis Braun ]
   * debian/control:
 + Bump debhelper-compat to 12
 + Bump standards version to 4.4.1
 + Add libjack-jackd2-dev as optional build dependency
 + Remove obsolete ${shlibs:Depends} from synthv1-common
   * debian/copyright:
 + Add FSFAP license
 + Update years and http to https
   * debian/patches/0004-fix_install_path.patch: Drop, obsolete
   * debian/synthv1-common.install: Drop so.* files, only lv2 now
   * debian/synthv1-lv2.install: Fix install path
   * debian/synthv1.manpages: Add french manpage
   * debian/synthv1.mime: Fix quoted-placeholder-in-mailcap-entry (Thanks 
Sebastian!)

Best Regards,
Dennis Braun

Bug#948622: RFS: samplv1/0.9.12-1 -- polyphonic sampler synthesizer - standalone/lv2

[Dennis Braun]

Package: sponsorship-requests
Severity: normal

Dear mentors,

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

 * Package name: samplv1
   Version : 0.9.12-1
   Upstream Author : Rui Nuno Capela 
 * URL : https://samplv1.sourceforge.io/
 * License : GPL-2+
 * Vcs : https://salsa.debian.org/multimedia-team/samplv1
   Section : sound

It builds those binary packages:

  samplv1 - polyphonic sampler synthesizer - standalone
  samplv1-lv2 - polyphonic sampler synthesizer - LV2 plugin
  samplv1-common - polyphonic sampler synthesizer - common files

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

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

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

  dget -x 
https://mentors.debian.net/debian/pool/main/s/samplv1/samplv1_0..9.12-1.dsc

Changes since the last upload:

   * Team upload
   * New upstream version 0.9.12
 .
   [ Felipe Sateler ]
   * Change maintainer address to debian-multime...@lists.debian.org
 .
   [ Ondřej Nový ]
   * Use debhelper-compat instead of debian/compat
   * debian/control: Set Vcs-* to salsa.debian.org
   * debian/copyright: Use https protocol in Format field
 .
   [ Dennis Braun ]
   * debian/control:
 + Bump debhelper-compat to 12
 + Bump standards version to 4.4.1
 + Add libjack-jackd2-dev as optional build dependency
 + Remove obsolete ${shlibs:Depends} from samplv1-common
   * debian/copyright:
 + Add FSFAP license
 + Update years and http to https
   * debian/patches/0004-fix_install_path.patch: Drop, obsolete
   * debian/samplv1-common.install: Drop deprecated so.* files, only lv2 now
   * debian/samplv1-lv2.install: Fix install path
   * debian/samplv1.manpages: Add french manpage
   * debian/samplv1.mime: Fix quoted-placeholder-in-mailcap-entry (Thanks 
Sebastian!)

Best Regards,
Dennis Braun

Bug#948623: RFS: drumkv1/0.9.12-1 -- old-school drum-kit sampler - standalone/lv2

[Dennis Braun]

Package: sponsorship-requests
Severity: normal

Dear mentors,

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

 * Package name: drumkv1
   Version : 0.9.12-1
   Upstream Author : Rui Nuno Capela 
 * URL : https://drumkv1.sourceforge.io/
 * License : GPL-2+
 * Vcs : https://salsa.debian.org/multimedia-team/drumkv1
   Section : sound

It builds those binary packages:

  drumkv1 - old-school drum-kit sampler - standalone
  drumkv1-lv2 - old-school drum-kit sampler - lv2-plugin
  drumkv1-common - old-school drum-kit sampler - common files

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

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

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

  dget -x 
https://mentors.debian.net/debian/pool/main/d/drumkv1/drumkv1_0.9.12-1.dsc

Changes since the last upload:

   * Team upload
   * New upstream version 0.9.12
   * debian/control:
 + Add libjack-jackd2-dev as optional build dependency
 + Remove obsolete ${shlibs:Depends} from drumkv1-common
   * debian/copyright:
 + Add FSFAP license
 + Update years and http to https
   * debian/drumkv1-common.install: Drop deprecated so.* files, only lv2 now
   * debian/drumkv1-lv2.install: Fix install path
   * debian/drumkv1.manpages: Add french translation
   * debian/drumkv1.mime: Fix quoted-placeholder-in-mailcap-entry (Thanks 
Sebastian!)
   * debian/patches/0004-fix_install_path.patch: Drop, obsolete

Best Regards,
Dennis Braun

Bug#948620: RFS: budgie-extras/0.90.0-1

[David Mohammed]

Package: sponsorship-requests
Severity: normal

Dear mentors,

I am looking for a sponsor for my package "budgie-extras"

 * Package name: budgie-extras
   Version : 0.90.0-1
   Upstream Author : David Mohammed 
 * URL : https://ubuntubudgie.org
 * License : GPL-3+
 * Vcs : https://github.com/UbuntuBudgie/budgie-extras/tree/debian
   Section : misc

It builds those binary packages:

  budgie-extras-common - Shared component of budgie-extras applets
  budgie-network-manager-applet - Network Manager Applet for the budgie-desktop
  budgie-hotcorners-applet - Applet providing hotcorners capabilities
for the Budgie Desktop
  budgie-trash-applet - Applet allows access to trash capabilities for
the Budgie Desktop
  budgie-quicknote-applet - Applet providing simple notes capability
for the Budgie Desktop
  budgie-recentlyused-applet - Applet displays files recently accessed
for the Budgie Desktop
  budgie-previews-applet - transitional package
  budgie-previews - Provides window previews capabilities for the Budgie Desktop
  budgie-workspace-overview-applet - Applet providing quick access to
workspaces for the Budgie Desktop
  budgie-workspace-wallpaper-applet - Applet providing per workspace wallpaper
  budgie-window-mover-applet - Applet allows moving windows between
workspaces for the Budgie Desktop
  budgie-showtime-applet - Applet displaying date and time on the Budgie Desktop
  budgie-countdown-applet - Applet providing a countdown capability on
the Budgie Desktop
  budgie-keyboard-autoswitch-applet - Applet adding the ability to set
a different keyboard layout per application
  budgie-rotation-lock-applet - Applet to lock or unlock the screen rotation
  budgie-clockworks-applet - Applet to display clock across multiple time zones
  budgie-dropby-applet - Applet to popup when a USB device is connected
  budgie-kangaroo-applet - Applet to allow quick file-browsing
  budgie-app-launcher-applet - Applet to provide an alternative means
to launch applications
  budgie-weathershow-applet - Applet to display the weather and forecast
  budgie-takeabreak-applet - Applet to prompt when to take-a-break for
a set period of time
  budgie-extras-daemon - Extras daemon for budgie-extras capabilities
  budgie-quickchar - GUI to find and choose locale characters
  budgie-workspace-stopwatch-applet - Workspace usage tracker for the
budgie desktop
  budgie-fuzzyclock-applet - Show the time in a fuzzy way
  budgie-brightness-controller-applet - Applet to control the
brightness of the screen
  budgie-wallstreet - Change wallpaper from a folder on a schedule
  budgie-visualspace-applet - Show and manage windows in workspaces
for the Budgie Desktop
  budgie-applications-menu-applet - Stylish Applications Menu for Budgie-Desktop

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

  https://mentors.debian.net/package/budgie-extras

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

  dget -x 
https://mentors.debian.net/debian/pool/main/b/budgie-extras/budgie-extras_0.90.0-1.dsc

Notes:
I am the debian maintainer - this request is due to the new/changed
binaries which is not part of my upload rights.

lintian -i -I run on the built source and is lintian free

check-all-the-things has been run on the source and corrections made
to the source

sbuild run to ensure builds correctly for both unstable and experimental

debian/copyright revised to accommodate the new source files
introduced in this release.

This request is for upload to experimental - this is the first beta
release for budgie-extras and I consider this needs additional testing
due to the extent of changes before upload to the main unstable
archive (it would be eventually v1.0.0)

This upload introduces new built binaries to be authorised by
archive-admins via the NEW queue.

Changes since the last upload:

   * New release
 git tag v0.90.0 beta release 1
   * New applets
 budgie-workspace-stopwatch-applet
 budgie-applications-menu-applet
 budgie-wallstreet
 budgie-network-manager-applet
   * budgie-visualspace-applet previous python based applet converted
 to vala
   * budgie-previews new mini-application with the previous applet
 budgie-previews-applet now replaced.
   * budgie-extras-daemon supports multiple desktop layouts
   * Bug-fixes
 desktop files includes keywords to resolve lintian information reports
 Support vertical panels for weather applet
 Rework dropby applet to prevent panel freezing issues
   * Translation updates
   * Packaging Changes
 debian/copyright refresh to include year updates and new source files
 control: add build-depends on debhelper-compat (= 12)
 compat: remove deprecated file
 control: new binaries for the listed applets above
 control: build-dependencies updated for the vala compilation
 control: budgie-visualspace-applet architecture changed to any
 control: budg

Bug#934444: i3lock-fancy does not fork

[Simon Désaulniers]

I have produced this patch (attached to this mail). If you think that this is
not sufficient, tell me. The patch won't be merged until a couple of days
anyway.

On Fri, Jan 10, 2020 at 04:18:40PM -0500, Simon Désaulniers wrote:
> Hi again,
> 
> Actually, I have just looked at the man page and the faulty behaviour is not
> about the option `-n`, but the default program behaviour as you said 
> previously.
> However, this is under documentation for `-n` that forking is mentioned.
> Therefore, the second suggestion about removing the option just doesn't make
> sense as a temporary fix for this issue. Consequently, a notice is best I 
> think.
> 
> Regards,
> 
> On Fri, Jan 10, 2020 at 04:07:22PM -0500, Simon Désaulniers wrote:
> > Hi dirdi,
> > 
> > You are right. Would you simply add a notice in the man page by forwarding 
> > to
> > the upstream bug URL? Or would you totally remove the option from the man 
> > page?
> > I am more tempted in doing the former. What do you think?
> > 
> > Regards,
> > 
> > On Mon, Jan 06, 2020 at 04:29:09AM +0100, dirdi wrote:
> > > Package: i3lock-fancy
> > > Version: 0.0~git20160228.0.0fcb933-2
> > > Followup-For: Bug #93
> > > 
> > > I suggest to at least patch the man page and document the actual 
> > > behavior, since not forking might have severe security implications: E.g. 
> > > consider the following shell script which is supposed to lock the screen 
> > > and wipe all identities from the SSH agent:
> > > 
> > > > #! /bin/sh
> > > > i3lock-fancy
> > > > ssh-add -d
> > > 
> > > Instead of wiping those identities instantly they will not be wiped
> > > before i3lock-fancy exits (i.e. screen being unlocked).
> > 
> > -- 
> > Simon Désaulniers
> > sim.desaulni...@gmail.com
> 
> 
> 
> -- 
> Simon Désaulniers
> sim.desaulni...@gmail.com



-- 
Simon Désaulniers
sim.desaulni...@gmail.com
diff --git a/debian/i3lock-fancy.1 b/debian/i3lock-fancy.1
index ba8b2c6..b0514c3 100644
--- a/debian/i3lock-fancy.1
+++ b/debian/i3lock-fancy.1
@@ -50,7 +50,11 @@ immediately.
 
 .TP
 \fB-n, --nofork\fP
-Do not fork i3lock after starting.
+Do not fork i3lock after starting. 
+
+\fIIMPORTANT\fP: As of now, forking \fBdoes not\fP occur whether one uses `-n` or not. See
+https://github.com/meskarune/i3lock-fancy/issues/144 for more information
+regarding this bug.
 
 .TP
 \fB--\fP


signature.asc
Description: PGP signature

Bug#948598: mingw-w64-i686-dev: non-conforming snprintf function in case of truncation

[Bernhard Übelacker]

Hello Vincent,
I tried to find some more details about this issue.

In the regular case the resulting exe seems to link
to msvcrt.dll!_vsnprintf:

   $ i686-w64-mingw32-objdump --private-headers test.c.exe
DLL Name: msvcrt.dll
vma:  Hint/Ord Member-Name Bound-To
63e8  766  _vsnprintf

Under wine we then get to that location:
   #0  0x7eb514d6 in MSVCRT_vsnprintf (str=0x65fe64 "", len=3, format=0x40400b 
"abcdef", valist=0x65fe5c "+\026@") at 
/home/benutzer/wine/wine-git/wine-git/dlls/msvcrt/wcs.c:686

The resulting executables are showing the same output
in wine and windows.

In the posix case it seems the snprintf implementation is
not taken from any dll, instead it is contained inside
the executable, therefore supplied by the compiler?

Microsoft states [1], that they switched in VS2015 snprintf
to be C99 compliant, wouldn't therefore snprintf in msvcrt.dll
not compliant?

Is this issue in the end that mingw should link to
newer c-library by default?

Kind regards,
Bernhard

[1] 
https://docs.microsoft.com/en-us/cpp/c-runtime-library/reference/snprintf-snprintf-snprintf-l-snwprintf-snwprintf-l?view=vs-2019

Bug#925872: kcalc: Comma displays with three digit negative number fixed ?

[Aurélien COUDERC]

Dear Ivan,

thanks for taking the time to report this bug and help make Debian better.

I cannot reproduce the issue you describe on the current Debian stable (10/
buster), so I believe it has been fixed since you reported the bug.
It would be useful if you could retest on a more recent version and confirm 
whether the bug is fixed for you too.

Also could you please tell us which locale you’re using ? We need it if we 
want to try and reproduce the bug since numbers behaviours can vary quite a 
bit between locales.


Happy hacking !
--
Aurélien

Bug#948589: nmu: file_1:5.38-3

[Christoph Biedl]

clone 948589 -1
reassign -1 file
retitle -1 file: When building the file package, use the just-built file 
program in debhelper
thanks

Andreas Beckmann wrote...

> File lists identical (after any substitutions)
> 
> Control files: lines which differ (wdiff format)
> 
> Depends: {+libbz2-1.0, libc6 (>= 2.15), liblzma5 (>= 5.1.1alpha+20120614), 
> zlib1g (>= 1:1.1.4),+} libmagic-mgc (= [-1:5.38-3.bad)-] {+1:5.38-3.good)+}
> Version: [-1:5.38-3.bad-] {+1:5.38-3.good+}
> 
> The bad one was done with 1:5.38-2, the good one with 1:5.38-3 installed.

Thanks a lot, that bit of information helped me to understand the
situation. So src:file has indeed a circular build dependency, and
while this probably does not really do harm - at least no one bothered
to report issues with that in the past (at least) twelve years -, it is
not sound.

> Attached patch is a hack to prepend a 'file' wrapper script in the path
> that uses the freshly built one (I hope I did the call right?), this allows
> for a correct libmagic1 package to be built even in the presence of the buggy
> 1:5.38-2 in the system by using the new file command during the later stages
> of the build process.

That's a good point to start at anyway. I will have to add some more
bits, like overriding dh_strip (which calls the file binary as well).

> It's probably not cross-build safe, though.

Looks like it. Possibly I can find a solution for that as well.

Christoph, now having an even longer "lessons learned" list


signature.asc
Description: PGP signature

Bug#948618: anbox: Fixing anbox desktop files staying in Others category.

[Ahmad Hasan Mubashshir]

Package: anbox
Version: 0.0~git20190124-1
Severity: normal
Tags: patch

Dear Maintainer,

while I was using anbox, I saw its desktop files were being added to the Others
category instead of Anbox category in Whisker menu.

So I added debian/anbox-android.menu and added 'Categories=Anbox;' in
src/anbox/application/launcher_storage.cpp.

After this change, Android app Showed up under Anbox category.



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

Versions of packages anbox depends on:
ii  iptables1.6.1-2ubuntu2
ii  libboost-filesystem1.65.1   1.65.1+dfsg-0ubuntu5
ii  libboost-iostreams1.65.11.65.1+dfsg-0ubuntu5
ii  libboost-log1.65.1  1.65.1+dfsg-0ubuntu5
ii  libboost-program-options1.65.1  1.65.1+dfsg-0ubuntu5
ii  libboost-system1.65.1   1.65.1+dfsg-0ubuntu5
ii  libboost-thread1.65.1   1.65.1+dfsg-0ubuntu5
ii  libc6   2.27-3ubuntu1
ii  libdw1  0.170-0.4ubuntu0.1
ii  libegl1 1.0.0-2ubuntu2.3
ii  libgcc1 1:9.2.1-17ubuntu1~18.04.1
ii  libgles21.0.0-2ubuntu2.3
ii  liblxc1 3.0.3-0ubuntu1~18.04.1
ii  libprotobuf-lite10  3.0.0-9.1ubuntu1
ii  libsdl2-2.0-0   2.0.8+dfsg1-1ubuntu1.18.04.4
ii  libsdl2-image-2.0-0 2.0.3+dfsg1-1
ii  libstdc++6  9.2.1-17ubuntu1~18.04.1
ii  libsystemd0 237-3ubuntu10.33
ii  lxc 3.0.3-0ubuntu1~18.04.1

Versions of packages anbox recommends:
ii  dbus-user-session  1.12.2-1ubuntu1.1

anbox suggests no packages.
Description: Automatically add desktop files to Anbox category and adds changes 
splash screen to dark background.
Author: Ahmad Hasan Mubashshir 
Last-Update: 2020-01-11

---
 data/desktop/android-settings.desktop  |1 +
 data/desktop/android-settings.desktop  |1 +
 debian/anbox-android.menu  |   16 
 debian/conffiles   |1 +
 debian/install |1 +
 src/anbox/application/launcher_storage.cpp |3 ++-
 5 files changed, 21 insertions(+), 1 deletion(-)

--- a/data/desktop/android-settings.desktop
+++ b/data/desktop/android-settings.desktop
@@ -5,3 +5,4 @@ Terminal=false
 Type=Application
 Name=Android Settings
 GenericName=Android Settings
+Categories=Anbox
--- /dev/null
+++ b/debian/anbox-android.menu
@@ -0,0 +1,16 @@
+
+http://www.freedesktop.org/standards/menu-spec/menu-1.0.dtd";>
+
+   Applications
+   
+   anbox-android
+   anbox-android.directory
+   
+   
+   Anbox
+   anbox.desktop
+   
+   
+   
+
--- a/debian/install
+++ b/debian/install
@@ -1,6 +1,7 @@
 debian/anbox-container-manager.service /lib/systemd/system/
 debian/anbox-session-manager.service /usr/lib/systemd/user/
 debian/anbox.desktop /usr/share/applications/
+debian/anbox-android.menu /etc/xdg/menus/applications-merged/
 debian/anbox.png /usr/share/pixmaps/
 scripts/anbox-bridge.sh /usr/share/anbox/
 scripts/anbox-shell.sh /usr/share/anbox/
--- a/src/anbox/application/launcher_storage.cpp
+++ b/src/anbox/application/launcher_storage.cpp
@@ -94,10 +94,11 @@ void LauncherStorage::add_or_update(cons
   const auto item_icon_path = path_for_item_icon(package_name);
   if (auto desktop_item = std::ofstream(path_for_item(package_name).string())) 
{
 desktop_item << "[Desktop Entry]" << std::endl
+ << "Type=Application" << std::endl
  << "Name=" << item.name << std::endl
  << "Exec=" << exec << std::endl
  << "Terminal=false" << std::endl
- << "Type=Application" << std::endl
+ << "Categories=Anbox;" << std::endl
  << "Icon=" << item_icon_path.string() << std::endl;
   } else {
 BOOST_THROW_EXCEPTION(std::runtime_error("Failed to create desktop item"));

Bug#948617: bubblewrap: Please make autopkgtests cross-test-friendly.

[Steve Langasek]

Package: bubblewrap
Version: 0.4.0-1
Severity: minor
Tags: patch
User: ubuntu-de...@lists.ubuntu.com
Usertags: origin-ubuntu focal ubuntu-patch

Dear maintainers,

In Ubuntu, we are in the process of moving the i386 architecture to a
compatibility-only layer on amd64, and therefore we are also moving our
autopkgtest infrastructure to test i386 binaries in a cross-environment.

This requires changes to some tests so that they are cross-aware and can do
the right thing.

The bubblewrap tests currently fail in this environment, because they try to
install test dependencies for the target architecture rather than for the
host architecture.  The attached patch allows the dependencies to be
satisfied using the host versions of various core packages, letting the i386
tests successfully run on an amd64 host.

Note that upstream autopkgtest doesn't currently set DEB_HOST_ARCH so this
is a complete no-op in Debian for the moment.  Support for cross-testing in
autopkgtest is currently awaiting review at
https://salsa.debian.org/ci-team/autopkgtest/merge_requests/69 and once
landed, will still have no effect unless autopkgtest is invoked with a '-a'
option.  So this change should be safe to land in your package despite this
not being upstream in autopkgtest.

Thanks for considering,
-- 
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 bubblewrap-0.4.0/debian/tests/control 
bubblewrap-0.4.0/debian/tests/control
--- bubblewrap-0.4.0/debian/tests/control   2019-11-28 03:14:41.0 
-0800
+++ bubblewrap-0.4.0/debian/tests/control   2020-01-10 10:31:02.0 
-0800
@@ -7,21 +7,21 @@
 Restrictions: allow-stderr, isolation-machine
 Depends:
  bubblewrap,
- iproute2,
- libcap2-bin,
- libipc-run-perl,
- perl,
- python3,
+ iproute2:native,
+ libcap2-bin:native,
+ libipc-run-perl:native,
+ perl:native,
+ python3:native,
 
 Tests: upstream-usrmerge
 Restrictions: allow-stderr, isolation-machine, breaks-testbed
 Depends:
  bubblewrap,
- iproute2,
- libcap2-bin,
- libipc-run-perl,
- perl,
- python3,
+ iproute2:native,
+ libcap2-bin:native,
+ libipc-run-perl:native,
+ perl:native,
+ python3:native,
  usrmerge
 
 Tests:
@@ -29,8 +29,8 @@
 Restrictions: allow-stderr, isolation-machine, needs-root
 Depends:
  bubblewrap,
- iproute2,
- libcap2-bin,
- libipc-run-perl,
- perl,
- python3,
+ iproute2:native,
+ libcap2-bin:native,
+ libipc-run-perl:native,
+ perl:native,
+ python3:native,

Bug#948542: firefox: font settings ignored

[gregor herrmann]

Control: forwarded -1 https://bugzilla.mozilla.org/show_bug.cgi?id=1607052

On Fri, 10 Jan 2020 01:04:24 +0100, gregor herrmann wrote:

> firefox 72.0.1-1 ignores font settings in the preferences (both font
> face and font size) and always just uses DejaVu Serif 16px (unless
> overridden by the webpage of course). I've tested this is a new empty
> profile as well.

The above mentioned issue in mozilla's bugzilla sounds like it might
be the same.


Cheers,
gregor

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


signature.asc
Description: Digital Signature

Bug#934444: i3lock-fancy does not fork

[Simon Désaulniers]

Hi again,

Actually, I have just looked at the man page and the faulty behaviour is not
about the option `-n`, but the default program behaviour as you said previously.
However, this is under documentation for `-n` that forking is mentioned.
Therefore, the second suggestion about removing the option just doesn't make
sense as a temporary fix for this issue. Consequently, a notice is best I think.

Regards,

On Fri, Jan 10, 2020 at 04:07:22PM -0500, Simon Désaulniers wrote:
> Hi dirdi,
> 
> You are right. Would you simply add a notice in the man page by forwarding to
> the upstream bug URL? Or would you totally remove the option from the man 
> page?
> I am more tempted in doing the former. What do you think?
> 
> Regards,
> 
> On Mon, Jan 06, 2020 at 04:29:09AM +0100, dirdi wrote:
> > Package: i3lock-fancy
> > Version: 0.0~git20160228.0.0fcb933-2
> > Followup-For: Bug #93
> > 
> > I suggest to at least patch the man page and document the actual behavior, 
> > since not forking might have severe security implications: E.g. consider 
> > the following shell script which is supposed to lock the screen and wipe 
> > all identities from the SSH agent:
> > 
> > > #! /bin/sh
> > > i3lock-fancy
> > > ssh-add -d
> > 
> > Instead of wiping those identities instantly they will not be wiped
> > before i3lock-fancy exits (i.e. screen being unlocked).
> 
> -- 
> Simon Désaulniers
> sim.desaulni...@gmail.com



-- 
Simon Désaulniers
sim.desaulni...@gmail.com


signature.asc
Description: PGP signature

Bug#944294: buster-pu: package libvirt-daemon/5.0.0-4

[Michal Arbet]

Hi Guido,

Please, do you please now when will be new updated version in
buster-updated ?

Thank you,
Michal Arbet (kevko)

st 25. 12. 2019 v 16:42 odesílatel Guido Günther  napsal:

> Hi,
> On Thu, Dec 05, 2019 at 02:56:17PM +0100, Michal Arbet wrote:
> > Hi guido,
> >
> > Thank you very much for including my patches .
> > I only want to ask one question, why you removed patch which is adding
> test
> > for remove cpu features osxsave and ospke ?
> > In my previous debdiff it was included ->
> >
> https://libvirt.org/git/?p=libvirt.git;a=commit;h=b51bfa70554f4bc43cbd6841b78d67b391909184
>
> Mostly to make the debdiff as small as possible since there's another
> test dropping the flags which does the trick for buster I assume.
>
> Cheers,
>  -- Guido
>
>
> >
> > Thanks,
> > Michal Arbet ( kevko )
> >
> >
> > čt 5. 12. 2019 v 13:59 odesílatel Guido Günther 
> napsal:
> >
> > > Hi,
> > > On Thu, Dec 05, 2019 at 12:56:17PM +0100, Michal Arbet wrote:
> > > > Hi,
> > > >
> > > > Debdiff is empty.
> > > > Please, could you resend ?
> > >
> > > odd, where did that go. Updated one attached.
> > >  -- Guido
> > >
> > > >
> > > > Thanks,
> > > > Michal Arbet ( kevko )
> > > >
> > > > čt 5. 12. 2019 v 1:01 odesílatel Guido Günther 
> napsal:
> > > >
> > > > > Hi,
> > > > > On Wed, Nov 27, 2019 at 05:52:33PM +0100, Guido Günther wrote:
> > > > > > Hi,
> > > > > > On Wed, Nov 27, 2019 at 04:17:13PM +, Adam D. Barratt wrote:
> > > > > > > Control: tags -1 -confirmed +moreinfo
> > > > > > >
> > > > > > > Hi,
> > > > > > >
> > > > > > > On 2019-11-27 16:07, Guido Günther wrote:
> > > > > > > > Hi Adam,
> > > > > > > > On Wed, Nov 27, 2019 at 01:21:40PM +, Adam D. Barratt
> wrote:
> > > > > > > > > Control: tags -1 + confirmed
> > > > > > > > >
> > > > > > > > > On 2019-11-27 13:05, Michal Arbet wrote:
> > > > > > > > > > I've added a patch from upstream ( sid already included
> it
> > > in new
> > > > > > > > > > version ).
> > > > > > > > > > Check current debdiff in attachment.
> > > > > > > > >
> > > > > > > > > That looks OK, assuming it's been build- and
> runtime-tested on
> > > a
> > > > > > > > > buster
> > > > > > > > > system.
> > > > > > > >
> > > > > > > > It would be nice to coordinate such things with the package
> > > > > > > > maintainers. I've had question's regarding these patches
> which
> > > > > weren't
> > > > > > > > answered yet:
> > > > > > > >
> > > > > > > >
> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=944248#26
> > > > > > >
> > > > > > > Apologies for that, we tend to assume that people making such
> > > requests
> > > > > > > either work on the package or have had that co-ordination
> > > discussion
> > > > > > > already.
> > > > > > >
> > > > > > > In this case I'll put the request on hold until we hear back.
> > > > > >
> > > > > > Thanks.I intend to look at the particular issue and fold it into
> the
> > > > > > update with
> > > > > >
> > > > > > https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=939036
> > > > > >
> > > > > > which is still pending.
> > > > >
> > > > > Attached is the debdiff with #933036 included as well. O.k. to
> upload
> > > to
> > > > > stable-p-u?
> > > > > Cheers,
> > > > >  -- Guido
> > > > >
> > > > > >  -- Guido
> > > > > >
> > > > > > >
> > > > > > > Regards,
> > > > > > >
> > > > > > > Adam
> > > > > > >
> > > > >
> > >
>

Bug#937166: nuitka: Python2 removal in sid/bullseye

[Scott Kitterman]

On Fri, 30 Aug 2019 07:28:47 + Matthias Klose  wrote:
> Package: src:nuitka
> Version: 0.6.1.1+ds-1

I emailed the maintainer and an upload switching the package to python3 is 
expected this month (waiting on python3.8 compatibility from upstream).

Scott K

Bug#934444: i3lock-fancy does not fork

[Simon Désaulniers]

Hi dirdi,

You are right. Would you simply add a notice in the man page by forwarding to
the upstream bug URL? Or would you totally remove the option from the man page?
I am more tempted in doing the former. What do you think?

Regards,

On Mon, Jan 06, 2020 at 04:29:09AM +0100, dirdi wrote:
> Package: i3lock-fancy
> Version: 0.0~git20160228.0.0fcb933-2
> Followup-For: Bug #93
> 
> I suggest to at least patch the man page and document the actual behavior, 
> since not forking might have severe security implications: E.g. consider the 
> following shell script which is supposed to lock the screen and wipe all 
> identities from the SSH agent:
> 
> > #! /bin/sh
> > i3lock-fancy
> > ssh-add -d
> 
> Instead of wiping those identities instantly they will not be wiped
> before i3lock-fancy exits (i.e. screen being unlocked).

-- 
Simon Désaulniers
sim.desaulni...@gmail.com


signature.asc
Description: PGP signature

Bug#948616: python-protego: Upload package to unstable

[Emmanuel Arias]

Package: python-protego
Version: 0.1.15+dfsg-1
Severity: wishlist

Dear Maintainer,

python-scrapy (1.8.0) depends of protego. Please consider upload to
unstable

Cheers,
Emmanuel

Bug#948615: debian-policy: Broken link to the list of virtual package names

[Aurélien COUDERC]

Package: debian-policy
Version: 4.4.1.2
Severity: normal

Dear Maintainer,

in §3.6 Virtual packages, the policy includes a link [1] to the autoritative
list of virtual packages but this link is broken and leads to a « Page not
found » page.

[1] https://www.debian.org/doc/packaging-manuals/virtual-package-names-
list.yaml


Happy hacking,
--
Aurélien



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

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

debian-policy depends on no packages.

Versions of packages debian-policy recommends:
ii  libjs-sphinxdoc  1.8.5-4

Versions of packages debian-policy suggests:
ii  doc-base  0.10.9

-- no debconf information

Bug#948439: Please switch to enchant-2 instead of enchant(1)

[Boyuan Yang]

Control: tags -1 + patch
X-Debbugs-CC: sgmo...@kde.org

I am preparing a patch for this bug. On top of current git HEAD code, this
actually builds successfully.

Feel free to let me know if you have any issues.

-- 
Thanks,
Boyuan Yang

On Wed, 08 Jan 2020 18:15:10 +0100 Laurent Bigonville 
wrote:
> Source: qtspell
> Version: 0.8.5-2
> Severity: wishlist
> Control: block 947979 by -1
> 
> Hi,
> 
> Could you please switch qtspell to enchant-2?
> 
> Quickly looking at the code, it only requires to change libenchant-dev
> to libenchant-2-dev
> 
> Kind regards,
> 
> Laurent Bigonville
> 
> -- 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)
> 
> Kernel: Linux 5.4.0-2-amd64 (SMP w/8 CPU cores)
> Locale: LANG=fr_BE.UTF-8, LC_CTYPE=fr_BE.UTF-8 (charmap=UTF-8),
LANGUAGE=fr_BE:fr (charmap=UTF-8)
> Shell: /bin/sh linked to /usr/bin/dash
> Init: systemd (via /run/systemd/system)
> LSM: SELinux: enabled - Mode: Permissive - Policy name: refpolicy
From 8c0852f37e8414dce2d7d16b95cfa1b630396282 Mon Sep 17 00:00:00 2001
From: Boyuan Yang 
Date: Fri, 10 Jan 2020 14:48:02 -0500
Subject: [PATCH] debian/changelog: Document changes

---
 debian/changelog| 11 +++
 debian/control  |  2 +-
 debian/libqtspell-qt5-0.symbols |  4 ++--
 3 files changed, 14 insertions(+), 3 deletions(-)

diff --git a/debian/changelog b/debian/changelog
index 03b39ef..2cf0de9 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,3 +1,14 @@
+qtspell (0.8.5-2.1) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * debian/control:
++ Switch build-dependency from enchant 1.x to enchant
+  2.x.
+  * debian/libqtspell-qt5-0.symbols: Refresh symbols after
+switching to enchant 2.x.
+
+ -- Boyuan Yang   Fri, 10 Jan 2020 15:06:26 -0500
+
 qtspell (0.8.5-2) unstable; urgency=medium
 
   * Fix duplicate short descriptions.
diff --git a/debian/control b/debian/control
index 1bd7d7a..781ce95 100644
--- a/debian/control
+++ b/debian/control
@@ -7,7 +7,7 @@ Build-Depends: cmake,
debhelper (>=12),
doc-base,
doxygen,
-   libenchant-dev,
+   libenchant-2-dev,
pkg-config,
pkg-kde-tools,
qtbase5-dev,
diff --git a/debian/libqtspell-qt5-0.symbols b/debian/libqtspell-qt5-0.symbols
index 54de5ed..891d305 100644
--- a/debian/libqtspell-qt5-0.symbols
+++ b/debian/libqtspell-qt5-0.symbols
@@ -125,11 +125,10 @@ libqtspell-qt5.so.0 libqtspell-qt5-0 #MINVER#
  _ZN7QtSpell9CodetableC2Ev@Base 0.8.5
  _ZN7QtSpell9CodetableD1Ev@Base 0.8.5
  _ZN7QtSpell9CodetableD2Ev@Base 0.8.5
+ (optional=templinst)_ZN7enchant14set_prefix_dirENSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEE@Base 0.8.5
  _ZN7enchant4Dict13s_describe_fnEPKcS2_S2_S2_Pv@Base 0.8.5
- _ZN7enchant6Broker10m_instanceE@Base 0.8.5
  _ZN7enchant6BrokerD1Ev@Base 0.8.5
  _ZN7enchant6BrokerD2Ev@Base 0.8.5
- _ZN7enchant9Exception4whatEv@Base 0.8.5
  _ZN7enchant9ExceptionC1EPKc@Base 0.8.5
  _ZN7enchant9ExceptionC2EPKc@Base 0.8.5
  _ZN7enchant9ExceptionD0Ev@Base 0.8.5
@@ -161,6 +160,7 @@ libqtspell-qt5.so.0 libqtspell-qt5-0 #MINVER#
  _ZNK7QtSpell7Checker22getSpellingSuggestionsERK7QString@Base 0.8.5
  _ZNK7QtSpell7Checker9checkWordERK7QString@Base 0.8.5
  _ZNK7QtSpell9Codetable6lookupERK7QStringRS1_S4_S4_@Base 0.8.5
+ _ZNK7enchant9Exception4whatEv@Base 0.8.5
  (optional=templinst)_ZNK8QMapDataI7QStringS0_E8findNodeERKS0_@Base 0.8.5
  (optional=templinst)_ZNK8QMapNodeI7QStringS0_E4copyEP8QMapDataIS0_S0_E@Base 0.8.5
  (optional=templinst)_ZNSt6vectorINSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEESaIS5_EE17_M_realloc_insertIJS5_EEEvN9__gnu_cxx17__normal_iteratorIPS5_S7_EEDpOT_@Base 0.8.5
-- 
2.25.0.rc2



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

Bug#948589: nmu: file_1:5.38-3

[Andreas Beckmann]

On Fri, 10 Jan 2020 16:58:22 +0100 Christoph Biedl 
 wrote:
> Helmut Grohne wrote...
> 
> > The file package was built with a broken version file wrt #948269. As
> > such libmagic1 lacks shared library dependencies. A simple rebuild fixes
> > the problem.
> 
> This leaves me somewhat confused since I understand your rationale
> the file package needs itself to be built, in other words, a circular
> build dependency. This should not happen, and I'd like to eliminate
> that.
> 
> Mind to shed some light on this? How was libmagic wrongly built, how did
> this manifest?

binary debdiff of bad and good libmagic1 builds:

File lists identical (after any substitutions)

Control files: lines which differ (wdiff format)

Depends: {+libbz2-1.0, libc6 (>= 2.15), liblzma5 (>= 5.1.1alpha+20120614), 
zlib1g (>= 1:1.1.4),+} libmagic-mgc (= [-1:5.38-3.bad)-] {+1:5.38-3.good)+}
Version: [-1:5.38-3.bad-] {+1:5.38-3.good+}

The bad one was done with 1:5.38-2, the good one with 1:5.38-3 installed.

> (You might have noted the file build overrides dh_shlibdeps -
> appearently this is not enough?)

dh_shlibdeps (any maybe other dh_*) call 'file' - the (buggy?) version
installed in the system, not the freshly built one.

Attached patch is a hack to prepend a 'file' wrapper script in the path
that uses the freshly built one (I hope I did the call right?), this allows
for a correct libmagic1 package to be built even in the presence of the buggy
1:5.38-2 in the system by using the new file command during the later stages
of the build process.
It's probably not cross-build safe, though.

Andreas
diff -Nru file-5.38/debian/changelog file-5.38/debian/changelog
--- file-5.38/debian/changelog	2020-01-06 12:22:22.0 +0100
+++ file-5.38/debian/changelog	2020-01-10 21:32:05.0 +0100
@@ -1,3 +1,9 @@
+file (1:5.38-3.1) UNRELEASED; urgency=medium
+
+  * Non-maintainer upload.
+
+ -- Andreas Beckmann   Fri, 10 Jan 2020 21:32:05 +0100
+
 file (1:5.38-3) unstable; urgency=medium
 
   * Revert upstream commit "... count as dynamically linked only the
diff -Nru file-5.38/debian/rules file-5.38/debian/rules
--- file-5.38/debian/rules	2018-02-07 23:56:07.0 +0100
+++ file-5.38/debian/rules	2020-01-10 21:32:05.0 +0100
@@ -2,6 +2,9 @@
 
 export DEB_BUILD_MAINT_OPTIONS = hardening=+all
 
+# Use the just built file command for dh_shlibdeps and friends
+export PATH:=$(CURDIR)/debian/just-built:$(PATH)
+
 # HOWMANY is the number of bytes looked at by file
 CFLAGS += -DHOWMANY=0x18000
 
@@ -33,8 +36,16 @@
 	# Remove useless files
 	rm -f debian/tmp/usr/lib/*/*.la
 
+	mkdir -p debian/just-built
+	echo '#!/bin/sh\nLD_LIBRARY_PATH=$(CURDIR)/debian/tmp/usr/lib/$(DEB_HOST_MULTIARCH) exec $(CURDIR)/debian/tmp/usr/bin/file -m $(CURDIR)/debian/tmp/usr/share/file/magic.mgc "$$@"' > debian/just-built/file
+	chmod +x debian/just-built/file
+
 override_dh_missing:
 	dh_missing --fail-missing
 
 override_dh_shlibdeps:
 	dh_shlibdeps -Llibmagic1 -ldebian/libmagic1/usr/lib
+
+override_dh_auto_clean:
+	dh_auto_clean
+	$(RM) -r debian/just-built

Bug#948614: python3-tabulate: Update to 0.8.3 needed - silkaj dependency

[Michal Zima]

Package: python3-tabulate
Version: 0.8.2-1
Severity: normal
Tags: a11y

Dear Maintainer,

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

   * What led up to the situation?
   We are trying to update the silkaj package to the newest version and
   this is an dependency (the present 0.8.2 is not enough)
   * What exactly did you do (or not do) that was effective (or
 ineffective)?
   * What was the outcome of this action?
   * What outcome did you expect instead?


-- System Information:
Distributor ID: Kali
Description:Kali GNU/Linux Rolling
Release:2019.4
Codename:   kali-rolling
Architecture: x86_64

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

Versions of packages python3-tabulate depends on:
ii  python3  3.7.5-3

python3-tabulate recommends no packages.

python3-tabulate suggests no packages.

-- no debconf information

Bug#948560: [Python-modules-team] Bug#948560: Use of 'is' token for comparing string in knownhosts.py

[Emmanuel Arias]

Hi,

I can see that on salsa isn't the last version (18.9.0-6)?

The version 19.2.0 is on experimental but  isn't on salsa either


Cheers,
Arias Emmanuel
@eamanu
http://eamanu.com

El vie., 10 de ene. de 2020 a la(s) 03:39, Witold Baryluk
(witold.bary...@gmail.com) escribió:
>
> Package: python3-twisted
> Version: 18.9.0-6
> Severity: normal
>
>
> During update to new python3-twisted:
>
> Setting up python3-twisted (18.9.0-6) ...
> /usr/lib/python3/dist-packages/twisted/conch/client/knownhosts.py:492: 
> SyntaxWarning: "is" with a literal. Did you mean "=="?
>   if keytype is "EC":
>
>
> It appears to be fixed in twisted 19.2.0+ tho:
> https://github.com/twisted/twisted/commit/de05fee07a39d3415e4a3e9738d141b43b54f95c
> which was released almost a year ago.
>
>
>
> -- 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.3.0-2-amd64 (SMP w/12 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 /bin/dash
> Init: systemd (via /run/systemd/system)
> LSM: AppArmor: enabled
>
> Versions of packages python3-twisted depends on:
> ii  python3   3.7.5-3
> ii  python3-attr  18.2.0-1
> ii  python3-automat   0.6.0-1
> ii  python3-constantly15.1.0-1
> ii  python3-hamcrest  1.9.0-2
> ii  python3-hyperlink 19.0.0-1
> ii  python3-idna  2.6-2
> ii  python3-incremental   16.10.1-3.1
> ii  python3-openssl   19.0.0-1
> ii  python3-service-identity  18.1.0-5
> ii  python3-twisted-bin   18.9.0-6
> ii  python3-zope.interface4.6.0-4
>
> python3-twisted recommends no packages.
>
> Versions of packages python3-twisted suggests:
> pn  python3-glade2
> pn  python3-gtk2  
> pn  python3-pampy 
> pn  python3-qt4   
> ii  python3-serial3.4-5
> pn  python3-tk
> pn  python3-wxgtk2.8  
>
> -- no debconf information
>
> ___
> Python-modules-team mailing list
> python-modules-t...@alioth-lists.debian.net
> https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/python-modules-team

Bug#948613: wcc: autopkgtests try to dlopen PIE executables

[Aurelien Jarno]

Package: wcc
Version: 0.0.2+dfsg-3
Severity: serious

Dear wcc maintainers,

The wcc autopkgtests try to dlopen some PIE executables (namely
/usr/bin/ssh). This has never been really supported, and this fails with
an error message in recent glibc versions. This cause the autopkgtest to
fail:

| autopkgtest [11:11:14]: test command1: ./debian/tests/wsh-ssl.wsh /usr/bin/ssh
| autopkgtest [11:11:14]: test command1: [---
| ERROR: dlopen() /usr/bin/ssh: cannot dynamically load position-independent 
executable 
| ERROR: dlopen() of patched file! //tmp/.wsh-1902/ssh: cannot dynamically load 
position-independent executable 
| WARNING: No binary loaded in memory. Try loadbin(). For help type 
help("loadbin").
| lua_pcall() failed with ./debian/tests/wsh-ssl.wsh:6: attempt to call a nil 
value (global 'MD5_Init'), for: ./debian/tests/wsh-ssl.wsh
| init
|  ** libifying /usr/bin/ssh to //tmp/.wsh-1902/ssh (760616 bytes)
| -- input: my best friend is a little poney !
| -- md5 hexdump
| autopkgtest [11:11:15]: test command1: ---]
| autopkgtest [11:11:15]: test command1:  - - - - - - - - - - results - - - - - 
- - - - -
| command1 FAIL non-zero exit status 42

(see https://ci.debian.net/data/autopkgtest/testing/amd64/w/wcc/3942223/log.gz)

You can see reason for disabling dlopening PIE binaries in this upstream
bug report:
https://sourceware.org/bugzilla/show_bug.cgi?id=24323

It is unclear to me what this change means for the wcc testsuite and for
the usability of the wcc package. Could you please explain me how is it
used?

Thanks,
Aurelien

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

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

Versions of packages wcc depends on:
ii  libbinutils   2.33.1-6
ii  libc6 2.29-7
ii  libcapstone3  4.0.1+really+3.0.5-1+b1
ii  libelf1   0.176-1.1
ii  liblua5.3-0   5.3.3-1.1+b1

wcc recommends no packages.

Versions of packages wcc suggests:
pn  lua  

Bug#947032: from PIL import Image ModuleNotFoundError No module named PIL

[Andreas Beckmann]

Followup-For: Bug #947032
Control: tag -1 pending

buster-pu request: https://bugs.debian.org/948609


Andreas

Bug#901842: dtv-scan-tables: diff for NMU version 0+git20190925.6d01903-0.1

[Adrian Bunk]

Control: tags 901842 + patch
Control: tags 901842 + pending
Control: tags 940936 + patch
Control: tags 940936 + pending

Dear maintainer,

I've prepared an NMU for dtv-scan-tables (versioned as 
0+git20190925.6d01903-0.1) and uploaded it to DELAYED/15.
Please feel free to tell me if I should cancel it.

Attached is only the debian/ part of the debdiff.

cu
Adrian
diff -Nru dtv-scan-tables-0+git20171226.07b18ec/debian/changelog 
dtv-scan-tables-0+git20190925.6d01903/debian/changelog
--- dtv-scan-tables-0+git20171226.07b18ec/debian/changelog  2018-04-08 
03:03:39.0 +0300
+++ dtv-scan-tables-0+git20190925.6d01903/debian/changelog  2020-01-10 
21:25:33.0 +0200
@@ -1,3 +1,12 @@
+dtv-scan-tables (0+git20190925.6d01903-0.1) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * New upstream snapshot.
+* Adds a list of all current German DVB-T2 muxes. (Closes: #901842)
+* Adds the Eutelsat-5-West-A satellite. (Closes: #940936)
+
+ -- Adrian Bunk   Fri, 10 Jan 2020 21:25:33 +0200
+
 dtv-scan-tables (0+git20171226.07b18ec-1) unstable; urgency=medium
 
   * New Upstream Snapshot (commit 07b18ec)

Bug#948610: mercurial: calls python instead of python2

[Julien Cristau]

Control: severity -1 wishlist

On Fri, Jan 10, 2020 at 08:54:07PM +0100, Gianfranco Costamagna wrote:
> Severity: serious

Why?

Cheers,
Julien

Bug#948573: exim4: TLS not in use. Log spammed with "No server certificate defined; will use a selfsigned one."

[g+debian]

> You probably have not edited the correct file. "tls_advertise_hosts ="
> does work. Please retry and check with
> /usr/sbin/exim4 -bP tls_advertise_hosts

I edited the correct file. But thanks for pointing out the -bP option: I
have now worked out the problem...

The problem is that the section in /etc/exim4/exim4.conf.template for
manipulating tls_advertise_hosts is actually within a ".ifdef
MAIN_TLS_ENABLE" section. I do not have MAIN_TLS_ENABLE defined
anywhere, so when I edited /etc/exim4/exim4.conf.template to comment out
or change the value for tls_advertise_hosts the changes were being ignored.

If I edit /etc/exim4/exim4.conf.template to put the
'tls_advertise_hosts =' before the '.ifdef MAIN_TLS_ENABLE' then it does
work.

Please consider changing the shipped /etc/exim4/exim4.conf.template to
add 'tls_advertise_hosts =' into the:

.else
# Use upstream defaults

corresponding to the .ifdef MAIN_TLS_ENABLE

Bug#947979: Please add a tracker for the enchant -> enchant-2 transition

[Paul Gevers]

Control: tags -1 confirmed

Dear Laurent,

On 04-01-2020 01:10, Laurent Bigonville wrote:
> Could you please add a tracker for the enchant -> enchant-2 "transition"

Done. Slightly different from a regular transition: all involved
packages need a source-full upload to switch and this can happen over a
longer period.

Paul



signature.asc
Description: OpenPGP digital signature

Bug#948612: Unintelligble error message

[martin f krafft]

Package: dnsutils
Version: 1:9.10.3.dfsg.P4-12.3+deb9u5
Severity: normal
File: /usr/bin/dig

I have no idea what dig is trying to tell me with the following. 
There's obviously a problem, but please make this a proper error 
message, not debug output.

+ dig @::1 +noall +question -x fc00:14:75::8001:3
; Communication with 10.14.75.1#53 failed: operation canceled 
../../../lib/dns/name.c:1002: REQUIREsource) != ((void *)0)) && 
c == ((('D') << 24 | ('N') << 16 | ('S') << 8 | ('n')) failed, 
#0 0x7f3f2ed58a27 in ??
#1 0x7f3f2ed5897a in ??
#2 0x7f3f30235445 in ??
#3 0x55d3d3a70650 in ??
#4 0x55d3d3a720fd in ??
#5 0x55d3d3a73712 in ??
#6 0x7f3f2ed7c9f3 in ??
#7 0x7f3f2e7234a4 in ??
#8 0x7f3f2db74d0f in ??
Aborted

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

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

Versions of packages dnsutils depends on:
ii  bind9-host [host]  1:9.11.5.P4+dfsg-5.1+b1
ii  libbind9-161   1:9.11.5.P4+dfsg-5.1+b1
ii  libc6  2.29-7
ii  libcap21:2.27-1
ii  libcom-err21.45.4-1
ii  libdns1104 1:9.11.5.P4+dfsg-5.1+b1
ii  libfstrm0  0.6.0-1+b1
ii  libgeoip1  1.6.12-5
ii  libgssapi-krb5-2   1.17-6
ii  libidn2-0  2.2.0-2
ii  libirs161  1:9.11.5.P4+dfsg-5.1+b1
ii  libisc1100 1:9.11.5.P4+dfsg-5.1+b1
ii  libisccfg163   1:9.11.5.P4+dfsg-5.1+b1
ii  libjson-c4 0.13.1+dfsg-6
ii  libk5crypto3   1.17-6
ii  libkrb5-3  1.17-6
ii  liblmdb0   0.9.22-1
ii  liblwres1611:9.11.5.P4+dfsg-5.1+b1
ii  libprotobuf-c1 1.3.2-1+b1
ii  libssl1.1  1.1.1d-2
ii  libxml22.9.4+dfsg1-8

dnsutils recommends no packages.

Versions of packages dnsutils suggests:
pn  rblcheck  

-- no debconf information

-- 
 .''`.   martin f. krafft  @martinkrafft
: :'  :  proud Debian developer
`. `'`   http://people.debian.org/~madduck
  `-  Debian - when you have better things to do than fixing systems


digital_signature_gpg.asc
Description: Digital GPG signature (see http://martin-krafft.net/gpg/sig-policy/999bbcc4/current)

Bug#948611: meson fails to cross build anything with the cross file from debcrossgen

[Helmut Grohne]

Package: meson
Version: 0.53.0-1
Severity: important
Justification: breaks architecture bootstrap
Tags: upstream
Forwarded: https://github.com/mesonbuild/meson/issues/6431
User: debian-cr...@lists.debian.org
Usertags: ftcbfs
Control: affects -1 + libdrm systemd virglrenderer

The issue is already reported upstream. As it turns out, this likely
breaks many packages. Therefore, I need a Debian bug number for tracking
purposes. Please close it with the next upstream release fixing the
upstream issue.

Example:
http://crossqa.debian.net/build/virglrenderer_0.8.1-3_s390x_20200110160313.log

For most packages, one can use the following workaround:
set -i -e /ld=/d /usr/share/meson/debcrossgen

Helmut

Bug#948610: mercurial: calls python instead of python2

[Gianfranco Costamagna]

Source: mercurial
Version: 5.2.2-1
Severity: serious
tags: patch

Hello, the following patch should make the package compile with python binary 
removed from the system:

--- mercurial-5.2.2/debian/rules2020-01-10 08:14:46.0 +
+++ mercurial-5.2.2/debian/rules2020-01-10 08:14:48.0 +
@@ -7,6 +7,7 @@
 %:
dh $@ --with python2,bash-completion
 
+export PYTHON=python2
 PYVERS=$(shell pyversions -vs)
 PYVER_DEFAULT=$(shell pyversions -vd)
 DEB_HOST_ARCH := $(shell dpkg-architecture -qDEB_HOST_ARCH)
@@ -46,7 +46,7 @@
http_proxy='' dh_auto_test -- TESTFLAGS="--verbose --timeout 1440 
$(PARALLEL_TEST_JOBS) --blacklist $(CURDIR)/debian/mercurial.test_blacklist"
file-rename 's/\.deb-backup$$//' $(CURDIR)/tests/*
# run blacklisted tests but ignore their results
-   -cd tests && python run-tests.py --verbose `grep ^test 
../debian/mercurial.test_blacklist`
+   -cd tests && python2 run-tests.py --verbose `grep ^test 
../debian/mercurial.test_blacklist`
 endif
 
 override_dh_auto_install: $(PYVERS:%=install-python%)

thanks for considering it

Gianfranco

Bug#930846: New development of how to build the installation-guide for the website [ Re: Bug#930846: partman-auto-lvm: debconf show guided_size during auto install ]

[Holger Wansing]

Hi Laura,

Laura Arjona Reina  wrote:
> Hi
> 
> El 9/1/20 a las 20:49, Holger Wansing escribió:
> > 
> > To make a new build happen, manual intervention is
> > needed now ( because there is no new source package
> > version available for installation-guide since the last build, no new build 
> > is trigered).
> > One need to go to
> > /srv/www.debian.org/cron/log/ig-stable-built.txt
> > and change that file (for example just change into an
> > empty file).
> > This is documented in the 1installation-guide script in
> > lessoften (cron git-repo).
> > That will trigger a new build at the next day.
> 
> I've just done this (copied /srv/www.debian.org/cron/log/ig-stable-built.txt 
> to
> /srv/www.debian.org/cron/log/ig-stable-built.txt.old and then changed
> ig-stable-built.txt to be an empty file).

Hrr, this did not work. Sorry

The variant with the empty file was my first idea, but that did not work.
So I changed that, now the file has to be removed.

May I bother you again, to remove the file instead?
(Also, there is no need to keep the old file. You can remove it too.)
I have just updated the documentation in the 1installation-guide lessoften
script accordingly.


Many thanks + Sorry again

Holger


-- 
Holger Wansing 
PGP-Fingerprint: 496A C6E8 1442 4B34 8508  3529 59F1 87CA 156E B076

Bug#916616: closed by Sandro Tosi (Bug#916616: fixed in gphoto2-cffi 0.4.3~a1-1.1)

[Helmut Grohne]

Control: reopen -1



On Thu, Oct 24, 2019 at 10:09:03PM +, Debian Bug Tracking System wrote:
>  gphoto2-cffi (0.4.3~a1-1.1) unstable; urgency=medium
>  .
>* Non-maintainer upload.
>* Drop python2 support; Closes: #936643, #916616

#916616 is a bug in python-enum34. Not a bug in gphoto2-cffi. It just
happens to affect gphoto2-cffi.

Helmut

Bug#948609: buster-pu: package mnemosyne/2.6.1+ds-1+deb10u1

[Andreas Beckmann]

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

Hi,

let's fix the missing python3-pil dependency of mnemosyne in stable,
too. #947032

The package is already uploaded.


Andreas
diff -Nru mnemosyne-2.6.1+ds/debian/changelog 
mnemosyne-2.6.1+ds/debian/changelog
--- mnemosyne-2.6.1+ds/debian/changelog 2018-08-09 22:55:30.0 +0200
+++ mnemosyne-2.6.1+ds/debian/changelog 2020-01-10 18:49:36.0 +0100
@@ -1,3 +1,12 @@
+mnemosyne (2.6.1+ds-1+deb10u1) buster; urgency=medium
+
+  * Non-maintainer upload.
+
+  [ Julien Puydt ]
+  * Add depends on PIL (Closes: #947032).
+
+ -- Andreas Beckmann   Fri, 10 Jan 2020 18:49:36 +0100
+
 mnemosyne (2.6.1+ds-1) unstable; urgency=medium
 
   * Update packaging:
diff -Nru mnemosyne-2.6.1+ds/debian/control mnemosyne-2.6.1+ds/debian/control
--- mnemosyne-2.6.1+ds/debian/control   2018-08-09 22:55:30.0 +0200
+++ mnemosyne-2.6.1+ds/debian/control   2020-01-10 18:49:36.0 +0100
@@ -20,6 +20,7 @@
  python3-cheroot,
  python3-cherrypy3,
  python3-matplotlib,
+ python3-pil,
  python3-pyqt5,
  python3-pyqt5.qtsql,
  python3-pyqt5.qtwebchannel,

Bug#921717: RFH: cyrus-imapd -- Cyrus mail system - IMAP support

[Mike Gabriel]

Hi Xavier,

On Tue, 17 Dec 2019 02:39:47 +0100 Xavier  wrote:
> Control: retitle -1 RFH: cyrus-imapd -- Cyrus mail system - IMAP support
>
> Hi,
>
> I took over the maintenance of cyrus-imapd. However, I'd like some help
> to maintain it.
>
> Cheers,
> Xavier

I'd be interested in helping out. My production still runs on a very old 
version of cyrus-imapd (from Kolab v2 times) and I will need to upgrade 
it at the beginning of February.


I'll ping you then and let you know, if I can add some help to the 
cyrus-imapd package maintenance effort.


Thanks+Greets,
Mike

Bug#948584: libc6: Mounting nfsv4-export from my NAS there is a segfault in libc

[Bernhard Übelacker]

Hello Miriam,
if possible, you could install the additional package
systemd-coredump. Then in the output of 'journalctl --no-pager'
at the bottom should the known 'segfault at' line appear.
This and the following lines at that time would be of interest.

This would get better if the additional nfs-common-dbgsym
could be installed [1] (from a separate repo).

If additonal to the above steps the package gdb is installed,
'coredumpctl gdb' with the command 'bt full' at the gdb prompt
would yield even better information.

Kind regards,
Bernhard

[1] https://wiki.debian.org/HowToGetABacktrace#Installing_the_debugging_symbols

Bug#948401: stretch-pu: package libvncserver/0.9.11+dfsg-1.3~+deb9u3

[Mike Gabriel]

On  Fr 10 Jan 2020 19:31:23 CET, Cyril Brulebois wrote:


Mike Gabriel  (2020-01-08):

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

Dear release team,

a regression in the recent libvncserver stretch-pu (~deb9u2) has  
been reported.


+  * Regression update.
+
+  * debian/patches: Add use-after-free/{4,5,6}.patch. All  
cherry-picked from

+upstream. Resolves crashing of x11vnc when vncviewer connects. (Closes:
+#905786).

The just uploaded libvncserver package version (~deb9u3) pulls in three
more patches from upstream that resolve this regression issue.


I haven't checked the patched version yet (I downgraded before checking
this maildir, and I'm working on some urgent matter), but I can confirm
the gross regression in the version currently sitting in opu…


Cheers,


Yep, see [1] and the previous posts. The current version of opu and  
spu libvncserver must not enter the point release and should be  
replaced by the just uploaded versions.


Thanks,
Mike

[1] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=905786#90
--

DAS-NETZWERKTEAM
c\o Technik- und Ökologiezentrum Eckernförde
Mike Gabriel, Marienthaler str. 17, 24340 Eckernförde
mobile: +49 (1520) 1976 148
landline: +49 (4351) 850 8940

GnuPG Fingerprint: 9BFB AEE8 6C0A A5FF BF22  0782 9AF4 6B30 2577 1B31
mail: mike.gabr...@das-netzwerkteam.de, http://das-netzwerkteam.de



pgp7OIjd4SoYL.pgp
Description: Digitale PGP-Signatur

Bug#948608: add an autopkgtest for cross building

[Helmut Grohne]

Source: meson
Tags: patch

Please add an autopkgtest for cross building. Here is a pretty simple
case that should work (and doesn't work in unstable at present):

Depends: meson, g++-arm-linux-gnueabihf
Tests: crossbuild

crossbuild script:
-8<-8<-8<-
#!/bin/sh

set -e

cd "${ADTTMP:-/tmp}"
mkdir testproject
cd testproject
cat >meson.build 8->8->8-

The test case is currently broken due to 
https://github.com/mesonbuild/meson/issues/6431

Helmut

Bug#936238: brial: diff for NMU version 1.2.5-2.1

[Sandro Tosi]

Control: tags 936238 + patch


Dear maintainer,

I've prepared an NMU for brial (versioned as 1.2.5-2.1). The diff
is attached to this message.

Regards.

diff -Nru brial-1.2.5/debian/changelog brial-1.2.5/debian/changelog
--- brial-1.2.5/debian/changelog	2019-11-10 15:15:02.0 -0500
+++ brial-1.2.5/debian/changelog	2020-01-10 14:06:12.0 -0500
@@ -1,3 +1,10 @@
+brial (1.2.5-2.1) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * Drop python2 support; Closes: #936238
+
+ -- Sandro Tosi   Fri, 10 Jan 2020 14:06:12 -0500
+
 brial (1.2.5-2) unstable; urgency=medium
 
   * Rebuild with gcc-9 (required to fix segfaults in sagemath).
diff -Nru brial-1.2.5/debian/control brial-1.2.5/debian/control
--- brial-1.2.5/debian/control	2019-11-10 15:14:55.0 -0500
+++ brial-1.2.5/debian/control	2020-01-10 14:05:50.0 -0500
@@ -10,7 +10,6 @@
libboost-python-dev,
libboost-test-dev,
libm4ri-dev (>= 20120613),
-   python-all-dev,
python3-all-dev,
libgd-dev,
libjpeg-dev,
@@ -21,30 +20,6 @@
 Vcs-Browser: https://salsa.debian.org/science-team/brial
 Homepage: https://github.com/BRiAl
 
-Package: python-brial
-Architecture: any
-Section: python
-Replaces: python-polybori (<< 0.8.5)
-Breaks: python-polybori (<< 0.8.5), sagemath (<< 8.1~)
-Depends: ${shlibs:Depends},
- ${misc:Depends},
- libbrial3 (= ${binary:Version}),
- libbrial-groebner3 (= ${binary:Version}),
- ${python:Depends}
-Description: polynomials over Boolean Rings, Python 2 module
- The core of BRiAl is a C++ library, which provides high-level data
- types for Boolean polynomials and monomials, exponent vectors, as
- well as for the underlying polynomial rings and subsets of the
- powerset of the Boolean variables. As a unique approach, binary
- decision diagrams are used as internal storage type for polynomial
- structures. On top of this C++-library a Python interface
- is provided. This allows parsing of complex polynomial systems, as well
- as sophisticated and extendable strategies for Groebner base
- computation. BRiAl features a powerful reference implementation
- for Groebner basis computation.
- .
- This package contains the BRiAl Python 2 module.
-
 Package: python3-brial
 Architecture: any
 Section: python
diff -Nru brial-1.2.5/debian/python-brial.install brial-1.2.5/debian/python-brial.install
--- brial-1.2.5/debian/python-brial.install	2019-09-01 04:03:40.0 -0400
+++ brial-1.2.5/debian/python-brial.install	1969-12-31 19:00:00.0 -0500
@@ -1,2 +0,0 @@
-usr/lib/python2.*/
-
diff -Nru brial-1.2.5/debian/rules brial-1.2.5/debian/rules
--- brial-1.2.5/debian/rules	2019-09-01 04:03:40.0 -0400
+++ brial-1.2.5/debian/rules	2020-01-10 14:06:05.0 -0500
@@ -5,7 +5,7 @@
 export DEB_LDFLAGS_MAINT_APPEND = -Wl,--as-needed
 
 %:
-	dh $@ --with python2,python3
+	dh $@ --with python3
 
 override_dh_auto_build:
 	dh_auto_build

Bug#948607: rspamd: new upstream 2.2

[Jonatan Nyberg]

Package: rspamd
Version: 2.2

Please consider to upgrade to the current upstream version (2.2).

Regards
Jonatan

Bug#948588: libmtp9: segfault in libmtp.so.9.4.0

[Bernhard Übelacker]

Dear Maintainer,
the given code from dmesg points to this function:
  LIBMTP_GetPartialObject at libmtp.c:9070

The related code [1] looks like function LIBMTP_Get_Filemetadata
returns a null pointer which get dereferenced unconditionally
in line 9070.

This part of the function seems unchanged upstream [2].

Kind regards,
Bernhard


[1] https://sources.debian.org/src/libmtp/1.1.16-2/src/libmtp.c/#L9070
  9067  LIBMTP_file_t   *mtpfile = LIBMTP_Get_Filemetadata(device, id);
  9068 
  9069   /* Some devices do not like reading over the end and hang instead 
of progressing */
  9070   if (offset >= mtpfile->filesize) {

[2] https://sourceforge.net/p/libmtp/code/ci/master/tree/src/libmtp.c#l9084


From Submitter:
[ 6707.977374] pool[8766]: segfault at 18 ip 7f6b6a6262ee sp 
7f6b49ffaac0 error 4 in libmtp.so.9.4.0[7f6b6a618000+2a000]
[ 6707.977385] Code: d7 41 56 41 89 f6 41 55 4d 89 c5 41 54 4d 89 cc 55 48 89 
fd 53 48 83 ec 18 48 8b 5f 08 89 4c 24 0c e8 96 23 ff ff 8b 4c 24 0c <48> 8b 50 
18 4c 39 fa 0f 86 15 01 00 00 89 c8 89 d6 4c 01 f8 44 29
  0  1  2  3  4  5  6  7  8  9 10  1  2  3  4  5  6  7  8  
9 20  1  2  3  4  5  6  7  8  9 30  1  2  3  4  5  6  7  8  9 40  1  42



###

# Unstable amd64 qemu VM 2020-01-10


apt update
apt dist-upgrade


apt install systemd-coredump xserver-xorg sddm openbox xterm gdb rhythmbox 
libmtp9-dbgsym


export DISPLAY=:0

gdb -q --args rhythmbox

set width 0
set pagination off
run


Ctrl-C
(gdb) info share
FromTo  Syms Read   Shared Object Library
...
0x7fffe10c9870  0x7fffe10f2e20  Yes 
/lib/x86_64-linux-gnu/libmtp.so.9
...


(gdb) find /b 0x7fffe10c9870, 0x7fffe10f2e20, 0xd7, 0x41, 0x56, 0x41, 
0x89, 0xf6, 0x41, 0x55, 0x4d, 0x89, 0xc5, 0x41, 0x54, 0x4d, 0x89, 0xcc, 0x55, 
0x48, 0x89, 0xfd, 0x53, 0x48, 0x83, 0xec, 0x18, 0x48, 0x8b, 0x5f, 0x08, 0x89, 
0x4c, 0x24, 0x0c, 0xe8, 0x96, 0x23, 0xff, 0xff, 0x8b, 0x4c, 0x24, 0x0c, 0x48, 
0x8b, 0x50, 0x18, 0x4c, 0x39, 0xfa, 0x0f, 0x86, 0x15, 0x01, 0x00, 0x00, 0x89, 
0xc8, 0x89, 0xd6, 0x4c, 0x01, 0xf8, 0x44, 0x29
0x7fffe10d72c4 
1 pattern found.


(gdb) b *(0x7fffe10d72c4 + 42)
Breakpoint 2 at 0x7fffe10d72ee: file libmtp.c, line 9070.
(gdb) info b
Num Type   Disp Enb AddressWhat
2   breakpoint keep y   0x7fffe10d72ee in LIBMTP_GetPartialObject 
at libmtp.c:9070


(gdb) disassemble LIBMTP_GetPartialObject
Dump of assembler code for function LIBMTP_GetPartialObject:
   0x7fffe10d72c0 <+0>: push   %r15
   0x7fffe10d72c2 <+2>: mov%rdx,%r15
   0x7fffe10d72c5 <+5>: push   %r14
   0x7fffe10d72c7 <+7>: mov%esi,%r14d
   0x7fffe10d72ca <+10>:push   %r13
   0x7fffe10d72cc <+12>:mov%r8,%r13
   0x7fffe10d72cf <+15>:push   %r12
   0x7fffe10d72d1 <+17>:mov%r9,%r12
   0x7fffe10d72d4 <+20>:push   %rbp
   0x7fffe10d72d5 <+21>:mov%rdi,%rbp
   0x7fffe10d72d8 <+24>:push   %rbx
   0x7fffe10d72d9 <+25>:sub$0x18,%rsp
   0x7fffe10d72dd <+29>:mov0x8(%rdi),%rbx
   0x7fffe10d72e1 <+33>:mov%ecx,0xc(%rsp)
   0x7fffe10d72e5 <+37>:callq  0x7fffe10c9680 

   0x7fffe10d72ea <+42>:mov0xc(%rsp),%ecx
   0x7fffe10d72ee <+46>:mov0x18(%rax),%rdx  
<<<
   0x7fffe10d72f2 <+50>:cmp%r15,%rdx
...
   0x7fffe10d744a <+394>:   jmp0x7fffe10d73d9 

End of assembler dump.


Debian: https://sources.debian.org/src/libmtp/1.1.16-2/src/libmtp.c/#L9070
9067  LIBMTP_file_t *mtpfile = LIBMTP_Get_Filemetadata(device, id);
9068 
9069   /* Some devices do not like reading over the end and hang instead of 
progressing */
9070   if (offset >= mtpfile->filesize) {

Upstream: 
https://sourceforge.net/p/libmtp/code/ci/master/tree/src/libmtp.c#l9084

Bug#932597: konqueror: Some sites with SSL don't work (negotiation fails)

[John Scott]

This still affects 19.08.2, but strangely doesn't affect Falkon.

I see Falkon depends on libssl1.1 but Konqueror doesn't. Could that be what 
makes the difference?

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

Bug#946829: Patch works!

[Magnus Holmgren]

torsdag 19 december 2019 kl. 11:41:21 CET skrev du:
> I can confirm that patch works as expected.
> 
> Patch does not apply cleanly on my SA (3.4.2-1~deb9u2) but only for
> cosmetic differences, attached a patch that wok on SA 3.4.2-1~deb9u2.
> 
> 
> Thanks!

I came up with the following RE loop to parse the options string. It should 
allow a few more things that admins might potentially be using, like non-
integer values (for dontgreylistthreshold), while barfing on bad syntax.

while ($optionhash =~ /(?:\G(?(?['"])(?.*?)
\g{quot1})
   \s*=>\s*
   (?>(?['"])(?.*?)\g{quot2}
  |
  (?-?(?:\d+(?:\.\d*)?|(?:\d*\.)?\d+))
   )\s*(?:;?\s*\)\s*$|;(?!$))/gxc) {
$option{$+{opt}} = $+{val};
}
if ((pos($optionhash) // 0) < length $optionhash) {
die "Syntax error";
}

I just need to add the variable untainting.

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

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

Bug#948606: RM: rust-crossbeam-epoch-0.5/0.5.2-2

[Ximin Luo]

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

Hi, please remove this package from Testing as it is blocking others from 
migration and nothing else depends or build-depends on it.

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

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