Bug#949361: r-cran-ranger: autopkgtest regression on some architectures

[Graham Inggs]

Source: r-cran-ranger
Version: 0.12.1-1
X-Debbugs-CC: debian...@lists.debian.org
Severity: serious
User: debian...@lists.debian.org
Usertags: regression

Hi Maintainer

Since the upload of r-cran-ranger 0.12.1-1, its own autopkgtests have
been failing [1] on at least arm64, ppc64el and s390x.

I've copied what I hope is the relevant part of the log below.

Regards
Graham

[1] 
https://ci.debian.net/data/autopkgtest/testing/arm64/r/r-cran-ranger/4034091/log.gz


> library(testthat)
> library(ranger)
>
> test_check("ranger")
── 1. Failure: maxstat corrected impurity importance is positive (on average) (@
mean(rf$variable.importance) is not strictly more than 0. Difference: NaN

Error: testthat unit tests failed
══ testthat results  ═══
[ OK: 647 | SKIPPED: 10 | WARNINGS: 0 | FAILED: 1 ]
1. Failure: maxstat corrected impurity importance is positive (on
average) (@test_maxstat.R#41)

Execution halted
autopkgtest [11:39:55]: test run-unit-test: ---]
run-unit-testFAIL non-zero exit status 1

Bug#948611: Progress

[Jussi Pakkanen]

Hi

We are working on fixing this issue in this upstream PR:

https://github.com/mesonbuild/meson/pull/6457

The PR requires some fixes still, but if someone could test and verify
that it fixes the issue in this bug it would be useful.

We'll make the 0.53.1 release immediately after that PR has been
merged to master.

Bug#949359: Wish for space-separated --include="foo bar"

[Johannes Schauer]

On Mon, 20 Jan 2020 17:39:32 +1100 "Trent W. Buck"  wrote:
> Please make --include behave like --components.

Yesterday I uploaded version 0.6.0 of mmdebstrap. This should already work. :)

Please confirm by closing this bug.

Thanks!

cheers, josch


signature.asc
Description: signature

Bug#949360: w cuts IPv6 addres

[Marc Haber]

Package: procps
Version: 2:3.3.15-2+b1
Severity: normal
File: /usr/bin/w
Tags: ipv6

Hi,

[1/1520]mh@roll:~ $ w
 07:48:37 up 12:09,  1 user,  load average: 0,00, 0,01, 0,01
USER TTY  FROM LOGIN@   IDLE   JCPU   PCPU WHAT
mh   pts/22a01:238:4071:32 07:484.00s  0.05s  0.00s w
[2/1521]mh@roll:~ $ dpkg --list procps

The IP address cut off at the interesting point makes the information
useless. The formatting looks like w invokes last, which has an option
-w to give the full address. Maybe it is a good idea to give that option
here as well.

Greetings
Marc

Bug#949359: Wish for space-separated --include="foo bar"

[Trent W. Buck]

Package: mmdebstrap
Version: 0.5.1-4
Severity: wishlist

Currently --components allows separation by commas OR spaces.
Currently --include allows separation by commas BUT NOT spaces:

$ mmdebstrap sid delete-me --components='main contrib non-free' 
--include='amd64-microcode,intel-microcode,iucode-tool'# works
$ mmdebstrap sid delete-me --components='main contrib non-free' 
--include='amd64-microcode intel-microcode iucode-tool'# fails
[...]
E: Unable to locate package amd64-microcode intel-microcode iucode-tool
[...]

Please make --include behave like --components.

This will make it easier for me to create --include from a great big
bash array with inline comments:

includes+=(
baz # for chromium
quux
quuux   # because of international terrorism
# [...]
)

Because then I can simply say

"--include=${includes[*]}"

instead of having to mess around e.g.

OLDIFS=$IFS IFS=,
"--include=${includes[*]}"
IFS=$OLDIFS


My perl-fu is pretty stale, but based on

my @comps = split /[,\s]+/, $comp;

I think this patch is "good enough":

--- /rsync:root@not-omega:/tmp/bootstrap/mmdebstrap
+++ #
@@ -1196,7 +1196,7 @@

 my %pkgs_to_install;
 if (defined $options->{include}) {
-   for my $pkg (split /,/, $options->{include}) {
+   for my $pkg (split /[,\s]+/, $options->{include}) {
$pkgs_to_install{$pkg} = ();
}
 }

Bug#948041: impossible to update libbpf without updating the kernel

[Andrii Nakryiko]

On Sat, Jan 18, 2020 at 7:48 AM Bastian Blank  wrote:
>
> On Wed, Jan 15, 2020 at 12:50:16PM +, Sudip Mukherjee wrote:
> > On Wed, Jan 15, 2020 at 06:12:05AM +, Jonathan Nieder wrote:
> > > I agree --- if upstream development were happening in
> > > https://github.com/libbpf/libbpf then this would be a no-brainer.  It
> > > appears to instead be a mirror of the source that's in the kernel
> > > repo, though.
> > That will be difficult as all of them are dependent on the ftrace hooks
> > that are in the kernel.
>
> What will be difficult?
>
> > > > Why should we switch from kernel sources to GH is a frequently asked
> > > > question so the reason was explained in libbpf README [1].
>
> Let's go through it one by one.
>
> "Consistent versioning across distributions."
>
> Maybe, but the kernel is also versioned consistently.

Libbpf releases are only loosely synchronized with kernel releases,
and it's only due to current convention we established within
community. There is nothing preventing multiple releases of libbpf
between two releases of kernel. So having Linux distributions use
Github's release tags ensures that all of them are building from
exactly the same source code version.

> "No ties to any specific kernel, transparent handling of older kernels."
>
> What?  Either they are upstream for it or patch the source.  But this
> point means it can't be a direct mirror.  So what is it?

It is mostly a direct mirror, with some extra Github-specific stuff
beside (like Travis CI testing, etc). All the libbpf source code fixes
do go through bpf-next tree, though.

But the point here was that libbpf itself is not built with any
particular kernel version in mind. It is by design possible to use the
very latest libbpf against a pretty old kernel version and this will
work: libbpf will degrade some of the features (e.g, BTF type info
associations), but everything will keep working otherwise (unless user
requests feature that requires latest kernel version, of course: in
that case BPF program will fail to load and libbpf will return
corresponding error code).

>
> "Continuous integration testing via TravisCI."
> "Static code analysis via LGTM and Coverity."
>
> Both are not restricted to this repo.

Not sure what you mean by this. We can't have Travis CI integration w/
bpf-next source tree. But we can and we have it for Github mirror,
which runs tests and static analysis for every sync pull request. We
already have and are enhancing at the moment our testing set up to
test multiple kernels in multiple environments.

>
> > > If I'm reading that correctly, the intent appears to be that it would
> > > allow faster libbpf upgrades.
> > Yes, one of my intent. Faster and independent.
>
> And how does it do that, without being upstream of the source?
>
> Sorry, but I intend to end this discussion here.
>
> Bastian
>
> --
> It would be illogical to assume that all conditions remain stable.
> -- Spock, "The Enterprise Incident", stardate 5027.3
>
> --
> To unsubscribe, send mail to 948041-unsubscr...@bugs.debian.org.

Bug#949358: ITP: ulauncher --Universal launcher

[Patryk]

Package: wnpp
Severity: wishlist

* Package name: ulauncher
Version: 5.6.1
Upstream Author: Aleksandr Gornostal 
* URL: https://github.com/Ulauncher/Ulauncher
* License: GPLv3
Description: A universal launcher.
Ulauncher is a universal launcher for applications and URL searches using 
various search engines.

Bug#949357: casacore-data-observatories build depends on the removed

[Adrian Bunk]

Source: casacore-data-observatories
Version: 0+git2018.12.08-1
Severity: serious
Tags: ftbfs bullseye sid

libcasa-meas3 is no longer built by src:casacore.

It also looks wrong and unnecessary, and python3-casacore already
depends on libcasa-meas.

Bug#949356: nginx failed to start after upgrading "/lib64/libcrypt.so.1: version `XCRYPT_2.0' not found"

[alirezaimi]

Package: nginx
Version: 1.16.1-3
Severity: important

Dear Maintainer,

   * What led up to the situation?
   upgrading system
   * What exactly did you do (or not do) that was effective (or
 ineffective)?
 upgrade .
   * What was the outcome of this action?
   nginx failed to start .
   * What outcome did you expect instead?
   start !

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

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

Versions of packages nginx depends on:
ih  nginx-full  1.16.1-3

nginx recommends no packages.

nginx suggests no packages.

-- no debconf information
log : 
Jan 20 09:25:36 lap nginx[6229]: /usr/sbin/nginx: /lib64/libcrypt.so.1: version 
`XCRYPT_2.0' not found (required by /usr/sbin/nginx)

Bug#949355: simpleitk FTBFS: test failures

[Adrian Bunk]

Source: simpleitk
Version: 1.0.1-3
Severity: serious
Tags: ftbfs bullseye sid

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

...
99% tests passed, 2 tests failed out of 944

Total Test time (real) = 167.65 sec

The following tests FAILED:
244 - BasicFilters.FastMarchingBaseImageFilter (Failed)
375 - BasicFilters.LabelIntensityStatisticsImageFilter (Failed)
Errors while running CTest
make[2]: *** [Makefile:155: test] Error 8


More recent upstream releases (1.1.0 to 1.2.4) are using ITK 4.13,
upgrading will likely fix this bug.

Bug#949354: deb822 format (/etc/apt/sources.list.d/foo.sources) documented but not working

[Trent W. Buck]

Package: mmdebstrap
Version: 0.5.1-4
Severity: minor

As at this version:

root@not-omega:/tmp/bootstrap# dpkg-query -W mmdebstrap apt
apt 1.8.2
mmdebstrap  0.5.1-4

The manpage says I can use deb822 format:

root@not-omega:/tmp/bootstrap# man mmdebstrap | grep -2 -F deb822
   (defaults to "main"). If a MIRROR option happens to be an existing
   file, then its contents are pasted into the chroot's sources.list.
   This can be used to supply a deb822 style sources.list. If MIRROR is
   "-" then standard input is pasted into the chroot's sources.list.  
More
   than one mirror can be specified and are appended to the chroot's

But I can't convince it to work:

root@not-omega:/tmp/bootstrap# cat live.debian-10.sources
Types: deb
URIs: http://deb.debian.org/debian
# Need contrib & non-free for intel-microcode (CPU security).
# Need backports for newer kernel (to support newer hardware).
Suites: buster buster-updates buster-proposed-updates buster-backports
Components: main contrib non-free

Types: deb
URIs: http://deb.debian.org/debian-security
Suites: buster/updates
Components: main contrib non-free

root@not-omega:/tmp/bootstrap# mmdebstrap buster live live.debian-10.sources
I: automatically chosen mode: root
I: chroot architecture amd64 is equal to the host's architecture
E: Sub-process test returned an error code (1)
W: Download is performed unsandboxed as root as file 
/tmp/bootstrap/live/var/lib/apt/lists/partial couldn't be accessed by user _apt
I: running apt-get update...
done
E: Type 'Types:' is not known on line 1 in source list 
/tmp/bootstrap/live/etc/apt/sources.list
E: The list of sources could not be read.
E: apt-get update -oAPT::Status-Fd=<$fd> -oDpkg::Use-Pty=false failed

As far as I can tell,
apt allows only legacy format in .list files, and
apt allows only deb822 format in .sources files.

Writing a deb822 format to sources.list.d/mmdebstrap.list:

root@not-omega:/tmp/bootstrap# diff -U0 /usr/bin/mmdebstrap 
mmdebstrap-patched
--- /usr/bin/mmdebstrap 2019-10-20 08:26:10.0 +1100
+++ mmdebstrap-patched  2020-01-20 16:29:18.943182911 +1100
@@ -1100 +1100 @@
-   open my $fh, '>', "$options->{root}/etc/apt/sources.list" or error 
"cannot open /etc/apt/sources.list: $!";
+   open my $fh, '>', 
"$options->{root}/etc/apt/sources.list.d/mmdebstrap.list" or error "cannot open 
/etc/apt/sources.list.d/mmdebstrap.list: $!";
@@ -1189 +1189 @@
-   info "content of /etc/apt/sources.list:";
+   info "content of /etc/apt/sources.list.d/mmdebstrap.list:";
@@ -1191 +1191 @@
-   copy("$options->{root}/etc/apt/sources.list", *STDERR);
+   
copy("$options->{root}/etc/apt/sources.list.d/mmdebstrap.list", *STDERR);
root@not-omega:/tmp/bootstrap# rm -rf live
root@not-omega:/tmp/bootstrap# perl ./mmdebstrap-patched buster live 
live.debian-10.sources
I: automatically chosen mode: root
I: chroot architecture amd64 is equal to the host's architecture
E: Sub-process test returned an error code (1)
W: Download is performed unsandboxed as root as file 
/tmp/bootstrap/live/var/lib/apt/lists/partial couldn't be accessed by user _apt
I: running apt-get update...
done
E: Type 'Types:' is not known on line 1 in source list 
/tmp/bootstrap/live/etc/apt/sources.list.d/mmdebstrap.list
E: The list of sources could not be read.
E: apt-get update -oAPT::Status-Fd=<$fd> -oDpkg::Use-Pty=false failed

Writing a .list format to .sources:

root@not-omega:/tmp/bootstrap# diff -U0 /usr/bin/mmdebstrap 
mmdebstrap-patched-2
--- /usr/bin/mmdebstrap 2019-10-20 08:26:10.0 +1100
+++ mmdebstrap-patched-22020-01-20 16:30:55.534159939 +1100
@@ -1100 +1100 @@
-   open my $fh, '>', "$options->{root}/etc/apt/sources.list" or error 
"cannot open /etc/apt/sources.list: $!";
+   open my $fh, '>', 
"$options->{root}/etc/apt/sources.list.d/mmdebstrap.sources" or error "cannot 
open /etc/apt/sources.list.d/mmdebstrap.sources: $!";
@@ -1189 +1189 @@
-   info "content of /etc/apt/sources.list:";
+   info "content of /etc/apt/sources.list.d/mmdebstrap.sources:";
@@ -1191 +1191 @@
-   copy("$options->{root}/etc/apt/sources.list", *STDERR);
+   
copy("$options->{root}/etc/apt/sources.list.d/mmdebstrap.sources", *STDERR);

root@not-omega:/tmp/bootstrap# rm -rf live
root@not-omega:/tmp/bootstrap# perl ./mmdebstrap-patched-2 buster live
I: automatically chosen mode: root
I: chroot architecture amd64 is equal to the host's architecture
E: Sub-process test returned an error code (1)
W: Download is performed unsandboxed as root as file 
/tmp/bootstrap/live/var/lib/apt/lists/partial couldn't be accessed by user _apt
I: running apt-get update...
 

Bug#949353: nmu: elastix_4.9.0-1 and nifti2dicom_0.4.11-1

[Adrian Bunk]

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

nmu elastix_4.9.0-1 . amd64 i386 . unstable . -m "Rebuild with libgdcm3.0 and 
libinsighttoolkit4.13"
nmu nifti2dicom_0.4.11-1 . amd64 i386 . unstable . -m "Rebuild with libgdcm3.0 
and libinsighttoolkit4.13"

Seem to be remnants of an incomplete transition 3 months ago.

Bug#949352: x2goclient FTCBFS: builds for the build architecture

[Helmut Grohne]

Source: x2goclient
Version: 4.1.2.1-4
Tags: patch
User: debian-cr...@lists.debian.org
Usertags: ftcbfs

x2goclient fails to cross build from source, because it calls the build
architecture qmake via the upstream Makefile. It seems like the upstream
Makefile adds little value beyond handling the installation part. I
therefore propose moving that part into debian/rules and wrapping it up
in dh_auto_* such that dh_auto_configure can make cross building work.
You also need a dependency on qt5-qmake:native for running lrelease on a
.pro file. Please consider applying the attached patch.

Helmut
diff --minimal -Nru x2goclient-4.1.2.1/debian/changelog 
x2goclient-4.1.2.1/debian/changelog
--- x2goclient-4.1.2.1/debian/changelog 2019-12-21 17:56:23.0 +0100
+++ x2goclient-4.1.2.1/debian/changelog 2020-01-19 21:30:01.0 +0100
@@ -1,3 +1,12 @@
+x2goclient (4.1.2.1-4.1) UNRELEASED; urgency=medium
+
+  * Non-maintainer upload.
+  * Fix FTCBFS: (Closes: #-1)
++ Let dh_auto_configure call qmake.
++ Build-Depends: qt5-qmake:native for lrelease.
+
+ -- Helmut Grohne   Sun, 19 Jan 2020 21:30:01 +0100
+
 x2goclient (4.1.2.1-4) unstable; urgency=medium
 
   * debian/patches:
diff --minimal -Nru x2goclient-4.1.2.1/debian/control 
x2goclient-4.1.2.1/debian/control
--- x2goclient-4.1.2.1/debian/control   2019-12-11 15:31:36.0 +0100
+++ x2goclient-4.1.2.1/debian/control   2020-01-19 21:30:01.0 +0100
@@ -17,6 +17,7 @@
  libx11-dev,
  libxpm-dev,
  man2html-base | man2html,
+ qt5-qmake:native,
  qtbase5-dev,
  qttools5-dev-tools,
 Standards-Version: 4.4.1
diff --minimal -Nru x2goclient-4.1.2.1/debian/rules 
x2goclient-4.1.2.1/debian/rules
--- x2goclient-4.1.2.1/debian/rules 2019-12-11 15:33:16.0 +0100
+++ x2goclient-4.1.2.1/debian/rules 2020-01-19 21:30:01.0 +0100
@@ -10,10 +10,11 @@
 
 override_dh_auto_configure:
cp ChangeLog txt/changelog
-   dh_auto_configure
+   lrelease x2goclient.pro
+   dh_auto_configure --buildsystem=qmake --builddirectory=client_build -- 
../x2goclient.pro
 
 override_dh_auto_build:
-   make PREFIX=/usr build_client
+   dh_auto_build --buildsystem=qmake --builddirectory=client_build
make PREFIX=/usr build_man
 
 override_dh_auto_install:

Bug#909280: elastix: New upstream available

[Adrian Bunk]

On Thu, Sep 20, 2018 at 10:53:44PM +0200, Andreas Tille wrote:
> 
> Hi,
> 
> there is a new upstream version of elastix available.  I've imported it
> into Git and tried to adapt patches and d/rules but the build failed.  I
> hope I did not messed up the patches too much - most patched files do
> not exist any more.  May be they were moved around and you need to fetch
> the diff from Git history.  I'll stop here and leave the issue for more
> competent packagers.

I can't find your git changes, but since the upstream release notes say 
that ITK < 5 is no longer supported I'd guess this might be the problem.

> Kind regards
> 
>Andreas.

cu
Adrian

Bug#949351: efl FTBFS: missing dependency on libx11-xcb-dev

[Helmut Grohne]

Source: efl
Version: 1.21.1-5
Severity: serious
Tags: ftbfs

efl fails to build from source, because pkg-config cannot find
x11-xcb.pc. Presumably, a dependency on libx11-xcb-dev is missing.

Also reproduced by reproducible builds:
https://tests.reproducible-builds.org/debian/rbuild/unstable/amd64/efl_1.21.1-5.rbuild.log.gz

Also seen by crossqa:
http://crossqa.debian.net/build/efl_1.21.1-5_armel_20191228231513.log

Helmut

Bug#949350: plastimatch build depends on libgdcm2-dev

[Adrian Bunk]

Source: plastimatch
Version: 1.8.0+dfsg.1-1
Severity: serious
Tags: ftbfs

libgdcm2-dev has been replaced by libgdcm-dev.

Bug#949349: camitk build depends on the removed lib{,vtk}gdcm2-dev

[Adrian Bunk]

Source: camitk
Version: 4.1.2-3
Severity: serious
Tags: ftbfs bullseye sid

libgdcm2-dev and libvtkgdcm2-dev have been replaced with
libgdcm-dev and libvtkgdcm-dev.

Bug#939989: transition: gdal

[Sebastiaan Couwenberg]

Looks like britney needs some help to migrate everything to testing. The
update_output.txt shows most rdeps, I can't make sense of why it's not
migrating them.

Kind Regards,

Bas

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

Bug#946451: +1

[Kingsley G. Morse Jr.]

Yes, please upgrade to version 4.

So,
Kingsley


-- 
Time is the fire in which we all burn.

Bug#938829: wireless-regdb: Python2 removal in sid/bullseye

[Sandro Tosi]

Hey Ben,

On Fri, 30 Aug 2019 07:58:45 + Matthias Klose  wrote:
> Package: src:wireless-regdb
> Version: 2016.06.10-1
> Severity: normal
> Tags: sid bullseye
> User: debian-pyt...@lists.debian.org
> Usertags: py2removal

could you have a look at updating this package to use python3? i
looked at it and honestly the instructions at
https://salsa.debian.org/kernel-team/wireless-regdb/blob/master/debian/README.source
kinda made me stop (i'm not really willing to do the extra work for a
single upload :) ).

wireless-regdb seems to support python3 already (at least in the
latest upstream release, since this commit
https://git.kernel.org/pub/scm/linux/kernel/git/sforshee/wireless-regdb.git/commit/?id=f3c4969c2485),
and is the last reverse dependency of python-m2crypto (which i
maintain) and after wireless-regdb is switched to use py3k i can drop
m2crypto python2 package.

thanks,
Sandro

Bug#949297:

[Alexandre-Xavier Labonté-Lamoureux]

Same for MATE, there is no menu bar and no preference menu.

Bug#949348: libnet: example Makefile includes build paths

[Vagrant Cascadian]

Source: libnet
Severity: normal
Tags: patch
User: reproducible-bui...@lists.alioth.debian.org
Usertags: buildpath
X-Debbugs-Cc: reproducible-b...@lists.alioth.debian.org

A Makefile shipped in the examples directory of libnet1-doc contains
build path variations for several values:

  
ACLOCAL·​=·​${SHELL}·​/​build/​1st/​libnet-​1.​1.​6+dfsg/​missing·​aclocal-​1.​16

vs.

  
ACLOCAL·​=·​${SHELL}·​/​build/​2/​libnet-​1.​1.​6+dfsg/​2nd/​missing·​aclocal-​1.​16


This makes the build unreproducible when built from a different path,
but the Makefile itself would require some manual configuration anyways,
since the end-user most likely does not contain the original build path
on their system.

I'd suggest simply removing the Makefile, as it is not functional, or
alternately, sanitizing with the attached patch to debian/rules.

live well,
  vagrant
From eb284d35ecc3a9d58655e7f1a9c6f6c979c95b61 Mon Sep 17 00:00:00 2001
From: Vagrant Cascadian 
Date: Sun, 19 Jan 2020 18:04:46 -0800
Subject: [PATCH 2/3] debian/rules: Remove buildpath from example Makefile in
 libnet1-doc.

---
 debian/rules | 9 +
 1 file changed, 9 insertions(+)

diff --git a/debian/rules b/debian/rules
index 43f948a..d02674b 100755
--- a/debian/rules
+++ b/debian/rules
@@ -14,3 +14,12 @@ CFLAGS += -Wno-uninitialized -Wno-unused-but-set-variable
 DEB_INSTALL_CHANGELOGS_libnet1 := doc/CHANGELOG
 DEB_CONFIGURE_EXTRA_FLAGS += --libdir=\$${prefix}/lib/$(DEB_HOST_MULTIARCH)
 DEB_CONFIGURE_SCRIPT_ENV += GREP=/bin/grep MKDIR_P="/bin/mkdir -p" SED=/bin/sed SHELL=/bin/bash
+
+binary-install/libnet1-doc::
+	# Clean up embedded build paths in order to ensure reproducible builds.
+	sed -i -e "s,-fdebug-prefix-map=$(CURDIR)=\.,,g" \
+		-e "s,-ffile-prefix-map=$(CURDIR)=\.,,g" \
+		-e "s,abs_.*$(CURDIR).*,,g" \
+		-e "s,$(CURDIR).*missing --run,,g" \
+		-e "s,$(CURDIR),./,g" \
+		$(CURDIR)/debian/libnet1-doc/usr/share/doc/libnet1-doc/html/Makefile
-- 
2.20.1



signature.asc
Description: PGP signature

Bug#949347: openimageio: pybind11-dev dependency: prevent Git download

[Hermann Vosseler]

Source: openimageio
Severity: normal

Dear Maintainer,

while backporting openimageio_2.0.12~dfsg0-1 (to Ubuntu 18.04 LTS),
I stumbled over the following insidious problem with the underlying
upstream-build and the DEB package.

The CMake buildsystem contains a macro to check for a proper pybind11
version. However, by default, this macro (src/cmake/externalpackages.cmake,
line 542)
attempts to be "smart", and automatically downloads a newer version of pybind11
via Git if "necessary", instead of failing with a clear error message.

We certainly do not want a Debian build silently to download sources from
"somewhere"


My proposed fix:

(1) suppress that behaviour in debian/rules

--- orig/openimageio-2.0.12~dfsg0/debian/rules  2019-10-04 12:02:14.0
+0200
+++ openimageio-2.0.12~dfsg0/debian/rules   2020-01-20 02:47:22.160681481
+0100
@@ -21,6 +21,7 @@
-DROBINMAP_INCLUDE_DIR="/usr/include/" \
-DCMAKE_SKIP_RPATH=ON \
-DPYTHON_VERSION=$(PY3VERS) \
+   -DBUILD_MISSING_PYBIND11=OFF \
-DSTOP_ON_WARNING=OFF \
-DUSE_FIELD3D=OFF \
-DUSE_OPENGL=$(SETGL)



(2) I'd be inclined to define a precise lower bound in the debian/control,
Not sure about that though, since it causes a maintennance liability...

--- orig/openimageio-2.0.12~dfsg0/debian/control2019-10-04
23:24:41.0 +0200
+++ openimageio-2.0.12~dfsg0/debian/control 2020-01-20 03:16:38.561245302
+0100
@@ -25,7 +25,7 @@
  libraw-dev,
  libtiff-dev,
  libwebp-dev,
- pybind11-dev,
+ pybind11-dev (>= 2.2.0),
  python3-dev,
  qtbase5-dev,
  robin-map-dev (>= 0.2.0)



-- System Information:
Debian Release: 10.2
  APT prefers stable
  APT policy: (900, 'stable'), (650, 'stable'), (500, 'stable-updates'), (95, 
'testing'), (80, 'unstable'), (50, 'experimental')
Architecture: amd64 (x86_64)

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

Bug#949346: libnet: example Makefile embeds different paths on usrmerge systems

[Vagrant Cascadian]

Source: libnet
Severity: normal
Tags: patch
User: reproducible-bui...@lists.alioth.debian.org
Usertags: usrmerge environment
X-Debbugs-Cc: reproducible-b...@lists.alioth.debian.org

The paths for various binaries (grep, mkdir, sed) differ on a merged
/usr system, and libnet embeds those paths into an example Makefile
shipped in the libnet1-doc package.

The attached patch works around this in debian/rules by passing GREP,
MKDIR_P, SED and SHELL to configure, using the /bin path for these
binaries which is compatible with both usrmerge and non-usrmerge
systems.

live well,
  vagrant
From e68c8de544b8f393d6bb9e20407e196b6cd8265a Mon Sep 17 00:00:00 2001
From: Vagrant Cascadian 
Date: Sun, 19 Jan 2020 17:43:22 -0800
Subject: [PATCH 1/3] debian/rules: Pass GREP, MKDIR_P SED and SHELL to
 configure, to ensure reproducible builds on a usrmerge system.

---
 debian/rules | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/debian/rules b/debian/rules
index 578a6af..43f948a 100755
--- a/debian/rules
+++ b/debian/rules
@@ -13,4 +13,4 @@ CFLAGS += -Wno-uninitialized -Wno-unused-but-set-variable
 
 DEB_INSTALL_CHANGELOGS_libnet1 := doc/CHANGELOG
 DEB_CONFIGURE_EXTRA_FLAGS += --libdir=\$${prefix}/lib/$(DEB_HOST_MULTIARCH)
-
+DEB_CONFIGURE_SCRIPT_ENV += GREP=/bin/grep MKDIR_P="/bin/mkdir -p" SED=/bin/sed SHELL=/bin/bash
-- 
2.20.1



signature.asc
Description: PGP signature

Bug#949345: ITP: fcitx5-gtk -- GTK IM Module for fcitx5

[Boyuan Yang]

Package: wnpp
Severity: wishlist
Owner: Boyuan Yang 

* Package name: fcitx5-gtk
  Version : 0.0~git2019.6f9ef64
  Upstream Author : Weng Xuetian 
* URL : https://github.com/fcitx/fcitx5-gtk
* License : LGPL-2.1+ or GPL-2.0+
  Programming Lang: C++
  Description : GTK IM Module for fcitx5

 Fcitx5 is the next generation of fcitx input method framework. It
 provides plasant and modern input experience with intuitive graphical
 configuration tools. The framework is highly extensible with support
 for GTK+ and Qt toolkits, DBus interfaces, a large variety of desktop
 environments and a developer-friendly API.
 .
 This package provides GTK IM modules for fcitx5. Users of GTK-based
 software are highly encouraged to install the related IM Modules.

It will be maintained under Debian Input Method Team.

-- 
Thanks,
Boyuan Yang


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

Bug#949344: ITP: cbang -- C! supports cross-platform networking, debugging, crypto, embedded JavaScript and event driven C++ development.

[Joseph Coffland]

Package: wnpp
Severity: wishlist
Owner: Joseph Coffland 

* Package name: cbang
  Version : 1.3.3 
  Upstream Author : Joseph Coffland  
* URL : https://github.com/CauldronDevelopmentLLC/cbang
* License : GPL-2+
  Programming Lang: C++
  Description : C! supports cross-platform networking, debugging, crypto, 
embedded JavaScript and event driven C++ development.

C! is a collection of C++ utility libraries developed over the course
of +15 years and several major C++ application development
projects including much of the software behind Folding@home,
the CAMotics CNC simulator.  It should compile and run on Windows, Linux 
and OSX using a modern C++ compiler C++11 suppport.

Many of the facilities of C! are geared towards cross-platform
application development and providing basic services that most
applications need such as a configuration system, run-time build
information, logging facilities, threads, smart pointers, simple
embedded scripting, etc.

C!'s philosophy is to create clean, simple, readable, modular and
reusable code.  C! also encourages exception based error handling,
and light use of C++ templates and C preprocesor macros.

C! leans on the venerable boost library but also reimplements
several boost APIs which are considered by the author to be too
template heavy, less readable or overly complicated in boost.

The code was developed on an as needed basis and was never intended to
be any sort of grand unifying system for C++ application development.
However, I hope others find many parts of the library useful in C++
development projects.

The initial goal of packaging C! for Debian is to make it possible
to package the CNC simulator CAMotics.  In addition, an Open-Source
Folding@home client is being developed which I would also like to
package for Debian.  CAMotics has been actively maintained since 2011
and Folding@home since 1999.  Once included in Debian, the cbang package
will be maintained by its author.

Bug#947881: [Pkg-opencl-devel] Bug#947881: pocl: fix build on hurd-i386

[Andreas Beckmann]

On 01/01/2020 22.46, Samuel Thibault wrote:
> Andreas Beckmann, le mer. 01 janv. 2020 22:10:57 +0100, a ecrit:
>> On 01/01/2020 15.19, Samuel Thibault wrote:
>>> pocl currently FTBFS on hurd-i386 only due to a header inclusion
>>> condition bug, could you apply the attached patch?
>>
>> Nice. Thanks.
>> Does the buildlog show any symbols changes?
> 
> This is the diff I am getting

OK, now it only fails due to some tests failing on a (virtual) single
core CPU. Unfortunately my patch only fixed one of the two cases (the
test should just be skipped if insufficient compute units are available)
despite of doing the more or less same thing twice.
But my cmake skills are not that good, I don't see what's different here.


Andreas

Bug#949343: flex: Embeds build paths in example Makefiles

[Vagrant Cascadian]

Package: flex
Severity: normal
Tags: patch
User: reproducible-bui...@lists.alioth.debian.org
Usertags: buildpath
X-Debbugs-Cc: reproducible-b...@lists.alioth.debian.org

Makefiles shipped in the examples directory contain build path
variations for several values:

/usr/share/doc/flex/examples/fastwc/Makefile.gz
/usr/share/doc/flex/examples/manual/Makefile.gz 

  
ACLOCAL·​=·​${SHELL}·​/​build/​1st/​flex-​2.​6.​4/​build-​aux/​missing·​aclocal-​1.​16

vs.

  
ACLOCAL·​=·​${SHELL}·​/​build/​2/​flex-​2.​6.​4/​2nd/​build-​aux/​missing·​aclocal-​1.​16


This makes the build unreproducible when built from a different path,
but the Makefile itself would require some manual configuration anyways,
since the end-user most likely does not contain the original build path
on their system.

I'd suggest simply removing the Makefiles, as they are not functional,
or alternately, sanitizing with the attached patch to debian/rules.

live well,
  vagrant
From 12ac0a2b79b1ae208e8bf4d2c936d5dcf51e44aa Mon Sep 17 00:00:00 2001
From: Vagrant Cascadian 
Date: Sun, 19 Jan 2020 14:26:38 -0800
Subject: [PATCH 2/3] debian/rules: Clean up embedded build paths in example
 Makefiles in order to ensure reproducible builds.

---
 debian/rules | 11 +++
 1 file changed, 11 insertions(+)

diff --git a/debian/rules b/debian/rules
index 57485fa..b95ebad 100755
--- a/debian/rules
+++ b/debian/rules
@@ -92,6 +92,17 @@ ifneq (,$(filter flex-doc, $(shell dh_listpackages)))
debian/flex-doc/usr/share/doc/flex-doc/
 endif
 
+override_dh_installexamples:
+	dh_installexamples
+	# Clean up embedded build paths in order to ensure reproducible builds.
+	sed -i -e "s,-fdebug-prefix-map=$(CURDIR)=\.,,g" \
+		-e "s,-ffile-prefix-map=$(CURDIR)=\.,,g" \
+		-e "s,abs_.*$(CURDIR).*,,g" \
+		-e "s,$(CURDIR).*missing --run,,g" \
+		-e "s,$(CURDIR),./,g" \
+		$(CURDIR)/debian/flex/usr/share/doc/flex/examples/fastwc/Makefile \
+		$(CURDIR)/debian/flex/usr/share/doc/flex/examples/manual/Makefile
+
 override_dh_auto_build:
 	dh_auto_build
 ifneq (,$(filter flex-doc, $(shell dh_listpackages)))
-- 
2.20.1



signature.asc
Description: PGP signature

Bug#949342: flex: Embeds paths to various binaries differently on usrmerge system

[Vagrant Cascadian]

Package: flex
Severity: normal
Tags: patch
User: reproducible-bui...@lists.alioth.debian.org
Usertags: usrmerge environment
X-Debbugs-Cc: reproducible-b...@lists.alioth.debian.org

The paths for various binaries (grep, mkdir, sed) differ on a merged
/usr system, and flex embeds those paths into several example Makefiles
shipped in the package.

The attached patch works around this in debian/rules by passing GREP,
MKDIR_P, SED and SHELL to configure, using using the /bin path for these
binaries which is compatible with both usrmerge and non-usrmerge
systems.

live well,
  vagrant
From 93a3269dab55742e0ccf2d7f080dc37a935b576d Mon Sep 17 00:00:00 2001
From: Vagrant Cascadian 
Date: Sun, 19 Jan 2020 14:07:57 -0800
Subject: [PATCH 1/3] debian/rules: Pass GREP, MKDIR_P, SED and SHELL to
 configure to ensure reproducible builds when built on a usrmerge system.

---
 debian/rules | 2 ++
 1 file changed, 2 insertions(+)

diff --git a/debian/rules b/debian/rules
index f8ee94e..57485fa 100755
--- a/debian/rules
+++ b/debian/rules
@@ -32,6 +32,8 @@ DEB_REVISION := $(strip $(shell echo $(DEB_NOEPOCH_VERSION)
 DEB_UPSTREAM_VERSION := $(shell echo $(DEB_NOEPOCH_VERSION) | sed 's/-[^-]*$$//')
 
 confflags = ac_cv_lib_util_getloadavg=no
+# Pass variables to ensure reproducible builds when built on usrmerge system
+confflags += GREP=/bin/grep MKDIR_P="/bin/mkdir -p" SED=/bin/sed SHELL=/bin/bash
 ifneq ($(DEB_BUILD_MULTIARCH),$(DEB_HOST_MULTIARCH))
   confflags += ac_cv_func_malloc_0_nonnull=yes ac_cv_func_realloc_0_nonnull=yes
 endif
-- 
2.20.1



signature.asc
Description: PGP signature

Bug#947754: Follow-up 947754

[Er_Maqui]

 Control: notfixed -1 12.6.2-2+fto10+1
Package: gitlab
Version: 12.6.4-1+fto10+1

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256


Hi,
Bug is still present on 12.6.4 too. Same error message as 12.6.2
I've only tested it with Sonar oauth.

https://maqui.darkbolt.net/
Linux registered user ~#363219
PGP keys avaiables at KeyServ. ID: 0x4233E9F2
Los hombres somos esclavos de la historia

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEEYf0F71OtDykDsKZdCU2zE9sy6H8FAl4k8ZMACgkQCU2zE9sy
6H+YEA/9EVBh5rf4muGLF7/Ob0RwcRkThh9tRZjOnLHMyRunUKLDoSLKs5V3baG2
QBajhzKCTpsOGQE3kBTIF0LmJuZqc14LBvSWJk6d0Nk6nXlLzHYI1ebBmVwJtIy/
8fJzQINHQkoDYlDM84pZDZkdENJfIti3chGNDYMdwwHRlFkgJ+/ZX7YL3Vwm+5BK
7iWyb9UehOFv/EKXdZKESYZ7a0+u3fNZPiyymr2mJtHFrfy4gHPCwALBSFbs19Rb
LGcNdhrYjWGvC4zAYCH+DRVYYdHPp4K4JHJd92yYwOxXfTZGGYrOhXHGPJD+89le
mnRLDpo1caxgQwTZ0WfHa/tsL6UFpPKLZu8ZMiGXCxEn/VRYydKwO1g13FYqqD/8
JID+b4oUYiz4iCieIm6tUeKi6bpV20Z28XeSFC2f7REDiumgy/Z9fC8RmSB1Mg8D
Kzeax+IgBsMr1K2hGP+8KKE1JVM2doD7bVSeuLoJu4svZYeKzHmW8oS9ytRcP4ai
YgiIo8V/sBvUq7aM5B5T8zxQHqLJNj3X1WL5CSsJ67CVpjNK5F6jRSP56pbWkKOf
QGkMJRNo4t/T40CpgeCcf7YO8LeQi/j4SoWJ8kE79q6RYa5GqDlrkOiUNYiGQas0
xszJzHhd465jTEefJx2pQNNVQniWV720fBz6i+UH8jfOCitsTcU=
=NANp
-END PGP SIGNATURE-

Bug#949311: os-prober hangs Mageia 7 x86_64 kernel installation

[Rolf Pedersen]

On Sun, 19 Jan 2020 19:15:24 +0100 John Paul Adrian Glaubitz 
 wrote:

> Hi!
>
> On 1/19/20 6:15 PM, Rolf Pedersen wrote:
> > Package: os-prober
> > Version: 1.74-4
> >
> > Thierry Vignaud, Mageia devel, asked that I submit this bug.  
Probably the most relevant
> > comment from my bug, there, is: 
https://bugs.mageia.org/show_bug.cgi?id=25873#c8
> Can you elaborate on the issue a bit more? I'm not sure how Debian is 
responsible for
> problems in other distributions. I don't see any other mentioning of 
Debian in the

> Mageia bug report.
>
> Thanks,
> Adrian
>
> --
> .''`. John Paul Adrian Glaubitz
> : :' : Debian Developer - glaub...@debian.org
> `. `' Freie Universitaet Berlin - glaub...@physik.fu-berlin.de
> `- GPG: 62FF 8A75 84E0 2956 9546 0006 7426 3B37 F5B5 F913
>
>
Yeah, I'll have to defer to Thierry who sent me.  I've asked him to 
comment in my MGA bug.  In case it helps, the source rpm is here: 
http://mirrors.kernel.org/mageia/distrib/7/SRPMS/core/release/os-prober-1.74-4.mga7.src.rpm


From 'rpm --query --info os-prober' on this system, included is:
URL : http://kitenet.net/~joey/code/os-prober/

and there are some ties to Debian stated, there, including direction to 
report bugs over here, FWIW. ;)

I will try to comply if specifics of a desired elaboration can be given.
Thanks,
Rolf

Bug#949341: sqlite3: embeds value of SHELL in libtclsqlite3.la

[Vagrant Cascadian]

Source: sqlite3
Severity: normal
Tags: patch
User: reproducible-bui...@lists.alioth.debian.org
Usertags: environment
X-Debbugs-Cc: reproducible-b...@lists.alioth.debian.org

The value of the SHELL variable is embedded in the libtclsqlite3.la
file.

It's possible the .la file should just be removed from the package (See
Debian Policy 10.2).

If the .la file can't be dropped entirely, please include the following
patch to debian/rules, which passes SHELL=/bin/sh to configure,
resulting in a reproducible build regardless of the value of SHELL
(though there are outstanding issues with build paths worth looking into
further).


Thanks for maintaining sqlite3!


live well,
  vagrant
From 37c24d73ca3905c1792525d92451c677172b3301 Mon Sep 17 00:00:00 2001
From: Vagrant Cascadian 
Date: Sun, 19 Jan 2020 15:49:05 -0800
Subject: [PATCH 1/2] debian/rules: Pass SHELL=/bin/sh to configure, to ensure
 reproducible builds regardless of the setting of the SHELL environment
 variable.

The /usr/lib/tcltk/sqlite3/libtclsqlite3.la file embeds the SHELL
value in the build result.
---
 debian/rules | 1 +
 1 file changed, 1 insertion(+)

diff --git a/debian/rules b/debian/rules
index 4c4d9f2..d0eb559 100755
--- a/debian/rules
+++ b/debian/rules
@@ -69,6 +69,7 @@ configure-stamp:
 	  --libdir=\$${prefix}/lib/$(DEB_HOST_MULTIARCH) \
 	  --libexecdir=\$${libdir}/sqlite3 \
 	  TCLLIBDIR=/usr/lib/tcltk/sqlite3 \
+	  SHELL=/bin/sh \
 	  $(DDEBUG)
 
 	# remove double -ldl from sqlite3.pc
-- 
2.20.1



signature.asc
Description: PGP signature

Bug#940660: elpa-elpy: add Suggests: python3-rope to refactor code

[Nicholas D Steeves]

P.P.S. Please don't top post.  http://www.idallen.com/topposting.html


signature.asc
Description: PGP signature

Bug#949256: linux-image-5.4.0-2-amd64: zram-tools blocks shutdown (regression since 5.2)

[Nicholas D Steeves]

Hi Nick,

Nick Shaforostoff  writes:
> Package: src:linux
> Version: 5.4.8-1
[snip]
> either removing zram-tools package or using linux-image-5.2.0-3-amd64 @
> 5.2.17-1
> which I had before the dist-upgrade makes the problem go away.
>
> Since 5.4 changelog mentions zram, I suspect that it was the kernel
> that introduced this regression.
>

If checking if the regression was introduced in a version earlier than
5.4.8-1 sounds interesting or fun, or if you'd like to test your
hypothesis, then packages from the following may be useful for
coarse-grained bisecting:

  https://snapshot.debian.org/package/linux/

I'd start here:

  https://snapshot.debian.org/package/linux/5.3.15-1/

Cheers,
Nicholas


signature.asc
Description: PGP signature

Bug#949336: clarification

[nbf]

clarification: I am testing it with a volume I created and used with 
cryptsetup 2:2.0. With 2:2.1 and 2:2.2 integritysetup-open seems to 
succeed, but the embedded ext4 filesystem cannot be used. Attempt to 
read the superblock raise I/O errors due to integrity mismatches.


Best,
n.b.f.

Bug#949340: sddm should by default install sddm-theme-debian-breeze instead of sddm-theme-debian-maui

[Shmerl]

Package: sddm
Version: 0.18.0-1+b2
Severity: normal

Dear Maintainer,

Currently, when selecting KDE during Debian installation, it by default
installs sddm-theme-debian-maui (through sddm installation).

It should instead install sddm-theme-debian-breeze, which is much better
integrated with KDE's default Breeze theme.

Thanks!



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

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

Versions of packages sddm depends on:
ii  adduser 3.118
ii  debconf [debconf-2.0]   1.5.73
ii  libc6   2.29-7
ii  libgcc1 1:9.2.1-22
ii  libpam0g1.3.1-5
ii  libqt5core5a5.12.5+dfsg-2
ii  libqt5dbus5 5.12.5+dfsg-2
ii  libqt5gui5  5.12.5+dfsg-2
ii  libqt5network5  5.12.5+dfsg-2
ii  libqt5qml5  5.12.5-5
ii  libqt5quick55.12.5-5
ii  libstdc++6  9.2.1-22
ii  libsystemd0 244-3
ii  libxcb-xkb1 1.13.1-2
ii  libxcb1 1.13.1-2
ii  qml-module-qtquick2 5.12.5-5
ii  x11-common  1:7.7+20
ii  xserver-xorg [xserver]  1:7.7+20

Versions of packages sddm recommends:
pn  haveged 
ii  libpam-systemd  244-3
ii  sddm-theme-breeze [sddm-theme]  4:5.14.5.1-5+b1

Versions of packages sddm suggests:
ii  libpam-kwallet5   5.14.5-1
pn  qtvirtualkeyboard-plugin  

-- debconf information:
  sddm/daemon_name: /usr/bin/sddm
* shared/default-x-display-manager: sddm

Bug#949339: libshiboken2-py3-5.14: missing Breaks+Replaces: libshiboken2-py3-5.13

[Andreas Beckmann]

Package: libshiboken2-py3-5.14
Version: 5.14.0-1~exp1
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

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

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

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

  Preparing to unpack .../libshiboken2-py3-5.14_5.14.0-1~exp1_amd64.deb ...
  Unpacking libshiboken2-py3-5.14 (5.14.0-1~exp1) ...
  dpkg: error processing archive 
/var/cache/apt/archives/libshiboken2-py3-5.14_5.14.0-1~exp1_amd64.deb 
(--unpack):
   trying to overwrite '/usr/lib/python3/dist-packages/shiboken2/__init__.py', 
which is also in package libshiboken2-py3-5.13 5.13.2-2.2+b1
  Errors were encountered while processing:
   /var/cache/apt/archives/libshiboken2-py3-5.14_5.14.0-1~exp1_amd64.deb
  dpkg-deb: error: paste subprocess was killed by signal (Broken pipe)


cheers,

Andreas


libshiboken2-py3-5.13=5.13.2-2.2+b1_libshiboken2-py3-5.14=5.14.0-1~exp1.log.gz
Description: application/gzip

Bug#937163: ns3: diff for NMU version 3.30+dfsg-3.1

[Sandro Tosi]

Control: tags 937163 + patch
Control: tags 943978 + patch
Control: tags 948660 + patch


Dear maintainer,

I've prepared an NMU for ns3 (versioned as 3.30+dfsg-3.1). The diff
is attached to this message.

Regards.

diff -Nru ns3-3.30+dfsg/debian/changelog ns3-3.30+dfsg/debian/changelog
--- ns3-3.30+dfsg/debian/changelog	2019-09-16 05:18:03.0 -0400
+++ ns3-3.30+dfsg/debian/changelog	2020-01-19 18:21:22.0 -0500
@@ -1,3 +1,10 @@
+ns3 (3.30+dfsg-3.1) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * Drop python2 modules dependencies; Closes: #937163, #948660, #943978
+
+ -- Sandro Tosi   Sun, 19 Jan 2020 18:21:22 -0500
+
 ns3 (3.30+dfsg-3) unstable; urgency=medium
 
   * Fix FTBFS: move all Build-Depends-Indeps to Build-Depends.
diff -Nru ns3-3.30+dfsg/debian/control ns3-3.30+dfsg/debian/control
--- ns3-3.30+dfsg/debian/control	2019-09-16 05:18:03.0 -0400
+++ ns3-3.30+dfsg/debian/control	2020-01-19 18:21:21.0 -0500
@@ -112,9 +112,9 @@
 Package: python3-ns3
 Architecture: any
 Depends: ${shlibs:Depends}, ${misc:Depends}, ${python3:Depends},
-  python-pygraphviz
+  python3-pygraphviz
 Section: python
-Suggests: python-kiwi, tcpdump
+Suggests: python3-kiwi, tcpdump
 Breaks: python-ns3
 Description: Python binding of ns3
  ns-3 is a discrete-event network simulator for Internet systems,

Bug#949338: gettext: uses embedded copy of help2man which embeds timestamps

[Vagrant Cascadian]

Package: gettext
Version: 0.19.8.1-10
Severity: normal
Tags: patch
User: reproducible-bui...@lists.alioth.debian.org
Usertags: timestamps
X-Debbugs-Cc: reproducible-b...@lists.alioth.debian.org

The embedded copy of help2man that gettext uses to generate manpages is
an old version that does not support SOURCE_DATE_EPOCH, and thus embeds
timestamps in generated manpages.

The attached patch adds help2man to build-depends and patches a Makefile
to use the system help2man binary, which supports SOURCE_DATE_EPOCH.


Thanks for maintaining gettext!


live well,
  vagrant
diff --git a/debian/control b/debian/control
index d72cb94..77b72c8 100644
--- a/debian/control
+++ b/debian/control
@@ -3,7 +3,7 @@ Section: devel
 Priority: optional
 Maintainer: Santiago Vila 
 Standards-Version: 3.9.6
-Build-Depends: g++ (>= 4:7), debhelper (>= 9.20160402), fastjar , default-jdk , file, libncurses5-dev, libxml2-dev, libglib2.0-dev, libcroco3-dev, xz-utils, libunistring-dev, bison
+Build-Depends: g++ (>= 4:7), debhelper (>= 9.20160402), fastjar , default-jdk , file, libncurses5-dev, libxml2-dev, libglib2.0-dev, libcroco3-dev, xz-utils, libunistring-dev, bison, help2man
 Homepage: https://www.gnu.org/software/gettext/
 Rules-Requires-Root: no
 
diff --git a/debian/patches/series b/debian/patches/series
index 4715910..b098d7f 100644
--- a/debian/patches/series
+++ b/debian/patches/series
@@ -7,3 +7,4 @@
 07-java11-support.patch
 08-java-future-support.patch
 09-fix-crash-with-po-file-input.patch
+use-system-help2man.patch
diff --git a/debian/patches/use-system-help2man.patch b/debian/patches/use-system-help2man.patch
new file mode 100644
index 000..e7b55a0
--- /dev/null
+++ b/debian/patches/use-system-help2man.patch
@@ -0,0 +1,19 @@
+From: Vagrant Cascadian 
+Date: Sun, 19 Jan 2020 14:31:22 -0800
+X-Dgit-Generated: 0.19.8.1-10 20dded162301a971067ad5ccc19038e515b2b409
+Subject: Use system help2man.
+
+
+---
+
+--- gettext-0.19.8.1.orig/gettext-tools/man/Makefile.am
 gettext-0.19.8.1/gettext-tools/man/Makefile.am
+@@ -57,7 +57,7 @@ PERL = @PERL@
+ RM = rm -f
+ 
+ # help2man 1.24 or newer.
+-HELP2MAN = $(PERL) -w -- $(srcdir)/help2man
++HELP2MAN = /usr/bin/help2man
+ 
+ # groff 1.17 or newer.
+ MAN2HTML = groff -mandoc -Thtml


signature.asc
Description: PGP signature

Bug#949337: RFS: gpxpy/1.4.0-1 -- GPX file parser and GPS track manipulation library (Python 3)

[Håvard Flaget Aasen]

Package: sponsorship-requests
Severity: normal

Dear mentors,

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

 * Package name: gpxpy
   Version : 1.4.0-1
   Upstream Author : Tomo Krajina tkraj...@gmail.com
 * URL : https://github.com/tkrajina/gpxpy
 * License : Apache
 * Vcs : https://salsa.debian.org/python-team/modules/gpxpy
   Section : python

It builds those binary packages:

  python3-gpxpy - GPX file parser and GPS track manipulation library 
(Python 3)
  gpxinfo - Command line utility to extract basic statistics from a GPX 
file


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


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

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

  dget -x 
https://mentors.debian.net/debian/pool/main/g/gpxpy/gpxpy_1.4.0-1.dsc


Changes since the last upload:

   * Team upload
   * New upstream version 1.4.0
   * Add Rules-Requires-Root
   * Set upstream metadata fields: Bug-Database, Bug-Submit, Repository,
 Repository-Browse
   * Add autopkgtest

Regards,

Bug#949336: Mapped integrity devices of size ≥2TiB are unusable on 32-bits platforms

[nbf]

Package: cryptsetup-bin
Version: 2:2.1.0-5+deb10u2
Severity: important

Dear Maintainers,

this is an unfortunate folowup to #935702. I thank Milan Broz very much 
for fixing that one so quickly.


Unfortunately, even though the mapped size is now correct, 
integritysetup still silently configures a DM device that cannot be read 
and only gives I/O errors. Most likely this is another issue specific to 
large volumes on 32-bit systems.


Affected versions:
"testing" 2:2.2.2-1
"stable"  2:2.1.0-5+deb10u2

Working version:
same as in #935702

Affected command:
integritysetup --integrity hmac-sha256 --integrity-key-size=4096 
--integrity-key-file=/IDISK.ikey open /dev/sda IDISK



Best,
n.b.f.

Bug#949335: exim4: Does not allow relay from IPv6 localhost like for IPv4

[David Lee Lambert]

Package: exim4
Version: 4.92-8+deb10u3
Severity: normal
Tags: ipv6

Dear Maintainer,

I was getting a "Relay not permitted" message from Thunderbird trying to send 
e-mail.

The immediate workaround was to change the "Server Name:" in Server Settings
from "localhost" to "127.0.0.1". However, the manpage says, and said in squeeze 
[1],

> dc_relay_nets
>A list of machines for which we serve as smarthost. _Please note that 
> 127.0.0.1 and ::1 are always permitted to relay since /usr/lib/sendmail is 
> available anyway and relay control doesn't make sense here._ Sets macro 
> MAIN_RELAY_NETS

(I actually had "...; 127.0.0.1/8; [::1]/128; ..." in dc_relay_nets, but
taking those entries out didn't seem to make any difference.)

Testing with "telnet", IPv4 localhost is allowed to relay, IPv6 localhost isn't:

# telnet -4 localhost 25
Trying 127.0.0.1...
Connected to localhost.
Escape character is '^]'.
220 huitzil.lmert.com ESMTP Exim 4.92 Sun, 19 Jan 2020 16:21:27 -0500
EHLO localhost
250-huitzil.lmert.com Hello localhost [127.0.0.1]
250-SIZE 52428800
250-8BITMIME
250-PIPELINING
250-CHUNKING
250-PRDR
250 HELP
MAIL FROM: te...@lmert.com
250 OK
RCPT TO: john@example.net
250 Accepted

# telnet -6 localhost 25
Trying ::1...
Connected to localhost.
Escape character is '^]'.
220 huitzil.lmert.com ESMTP Exim 4.92 Sun, 19 Jan 2020 16:22:10 -0500
EHLO localhost
250-huitzil.lmert.com Hello localhost [::1]
250-SIZE 52428800
250-8BITMIME
250-PIPELINING
250-CHUNKING
250-PRDR
250 HELP
MAIL FROM: te...@lmert.com
250 OK
RCPT TO: john@example.net
550 relay not permitted

... and a log line from the second attempt ...

2020-01-19 16:22:32 H=(localhost) [::1] F= rejected RCPT 
john@example.net: relay not permitted

 [1]: 
https://manpages.debian.org/jessie/exim4-config/update-exim4.conf.8.en.html

-- Package-specific info:
Exim version 4.92 #5 built 27-Sep-2019 16:09:35
Copyright (c) University of Cambridge, 1995 - 2018
(c) The Exim Maintainers and contributors in ACKNOWLEDGMENTS file, 2007 - 2018
Berkeley DB: Berkeley DB 5.3.28: (September  9, 2013)
Support for: crypteq iconv() IPv6 GnuTLS move_frozen_messages DANE DKIM DNSSEC 
Event OCSP PRDR SOCKS TCP_Fast_Open
Lookups (built-in): lsearch wildlsearch nwildlsearch iplsearch cdb dbm dbmjz 
dbmnz dnsdb dsearch nis nis0 passwd
Authenticators: cram_md5 plaintext
Routers: accept dnslookup ipliteral manualroute queryprogram redirect
Transports: appendfile/maildir/mailstore autoreply lmtp pipe smtp
Fixed never_users: 0
Configure owner: 0:0
Size of off_t: 8
Configuration file search path is 
/etc/exim4/exim4.conf:/var/lib/exim4/config.autogenerated
Configuration file is /var/lib/exim4/config.autogenerated
# /etc/exim4/update-exim4.conf.conf
#
# Edit this file and /etc/mailname by hand and execute update-exim4.conf
# yourself or use 'dpkg-reconfigure exim4-config'
#
# Please note that this is _not_ a dpkg-conffile and that automatic changes
# to this file might happen. The code handling this will honor your local
# changes, so this is usually fine, but will break local schemes that mess
# around with multiple versions of the file.
#
# update-exim4.conf uses this file to determine variable values to generate
# exim configuration macros for the configuration file.
#
# Most settings found in here do have corresponding questions in the
# Debconf configuration, but not all of them.
#
# This is a Debian specific file

dc_eximconfig_configtype='smarthost'
dc_other_hostnames='*; *; *'
dc_local_interfaces=''
dc_readhost='lmert.com'
dc_relay_domains='lmert.com; *.lmert.com'
dc_minimaldns='false'
dc_relay_nets='192.168.***.0/24; [fe80::]/10; [:***::**::]/64'
dc_smarthost='*.net::587'
CFILEMODE='644'
dc_use_split_config='true'
dc_hide_mailname='true'
dc_mailname_in_oh='true'
dc_localdelivery='mail_spool'

mailname:lmert.com
# /etc/default/exim4
EX4DEF_VERSION=''

# 'combined' -   one daemon running queue and listening on SMTP port
# 'no'   -   no daemon running the queue
# 'separate' -   two separate daemons
# 'ppp'  -   only run queue with /etc/ppp/ip-up.d/exim4.
# 'nodaemon' - no daemon is started at all.
# 'queueonly' - only a queue running daemon is started, no SMTP listener.
# setting this to 'no' will also disable queueruns from /etc/ppp/ip-up.d/exim4
QUEUERUNNER='combined'
# how often should we run the queue
QUEUEINTERVAL='30m'
# options common to quez-runner and listening daemon
COMMONOPTIONS=''
# more options for the daemon/process running the queue (applies to the one
# started in /etc/ppp/ip-up.d/exim4, too.
QUEUERUNNEROPTIONS=''
# special flags given to exim directly after the -q. See exim(8)
QFLAGS=''
# Options for the SMTP listener daemon. By default, it is listening on
# port 25 only. To listen on more ports, it is recommended to use
# -oX 25:587:10025 -oP /run/exim4/exim.pid
SMTPLISTENEROPTIONS=''

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

Bug#949334: src:plasma-desktop: missing multiple Breaks+Replaces

[Andreas Beckmann]

Source: plasma-desktop
Version: 4:5.17.5-1
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

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

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

This test intentionally skipped 'testing' to find file overwrite
problems before packages migrate from 'unstable' to 'testing'.

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

  Preparing to unpack .../plasma-desktop-data_4%3a5.17.5-1_all.deb ...
  Unpacking plasma-desktop-data (4:5.17.5-1) ...
  dpkg: error processing archive 
/var/cache/apt/archives/plasma-desktop-data_4%3a5.17.5-1_all.deb (--unpack):
   trying to overwrite 
'/usr/share/locale/ar/LC_MESSAGES/plasma_applet_org.kde.plasma.minimizeall.mo', 
which is also in package kdeplasma-addons-data 4:5.14.5.1-2
  dpkg-deb: error: paste subprocess was killed by signal (Broken pipe)
  Errors were encountered while processing:
   /var/cache/apt/archives/plasma-desktop-data_4%3a5.17.5-1_all.deb

  Preparing to unpack .../systemsettings_4%3a5.17.5-1_amd64.deb ...
  Unpacking systemsettings (4:5.17.5-1) ...
  dpkg: error processing archive 
/var/cache/apt/archives/systemsettings_4%3a5.17.5-1_amd64.deb (--unpack):
   trying to overwrite 
'/usr/share/kservices5/settings-system-administration.desktop', which is also 
in package kde-config-systemd 1.2.1-3+b2
  Errors were encountered while processing:
   /var/cache/apt/archives/systemsettings_4%3a5.17.5-1_amd64.deb

  Preparing to unpack .../plasma-workspace-data_4%3a5.17.5-1_all.deb ...
  Unpacking plasma-workspace-data (4:5.17.5-1) ...
  dpkg: error processing archive 
/var/cache/apt/archives/plasma-workspace-data_4%3a5.17.5-1_all.deb (--unpack):
   trying to overwrite 
'/usr/share/doc/HTML/ca/kcontrol/translations/index.cache.bz2', which is also 
in package plasma-desktop-data 4:5.14.5.1-4
  dpkg-deb: error: paste subprocess was killed by signal (Broken pipe)
  Preparing to unpack .../plasma-workspace_4%3a5.17.5-1_amd64.deb ...
  Unpacking plasma-workspace (4:5.17.5-1) ...
  dpkg: error processing archive 
/var/cache/apt/archives/plasma-workspace_4%3a5.17.5-1_amd64.deb (--unpack):
   trying to overwrite '/usr/share/kservices5/kcm_translations.desktop', which 
is also in package plasma-desktop-data 4:5.14.5.1-4
  dpkg-deb: error: paste subprocess was killed by signal (Broken pipe)
  Errors were encountered while processing:
   /var/cache/apt/archives/plasma-workspace-data_4%3a5.17.5-1_all.deb
   /var/cache/apt/archives/plasma-workspace_4%3a5.17.5-1_amd64.deb

  Preparing to unpack .../01-plasma-workspace_4%3a5.17.5-1_amd64.deb ...
  Unpacking plasma-workspace (4:5.17.5-1) over (4:5.14.5.1-5+b1) ...
  dpkg: error processing archive 
/tmp/apt-dpkg-install-NSww2K/01-plasma-workspace_4%3a5.17.5-1_amd64.deb 
(--unpack):
   trying to overwrite 
'/usr/lib/x86_64-linux-gnu/qt5/plugins/kcms/kcm_translations.so', which is also 
in package plasma-desktop 4:5.14.5.1-4
  dpkg-deb: error: paste subprocess was killed by signal (Broken pipe)

  Preparing to unpack .../55-plasma-desktop-data_4%3a5.17.5-1_all.deb ...
  Unpacking plasma-desktop-data (4:5.17.5-1) ...
  dpkg: error processing archive 
/tmp/apt-dpkg-install-tbnXT7/55-plasma-desktop-data_4%3a5.17.5-1_all.deb 
(--unpack):
   trying to overwrite 
'/usr/share/kservices5/plasma-applet-org.kde.plasma.minimizeall.desktop', which 
is also in package plasma-widgets-addons 4:5.14.5.1-2+b2
  dpkg-deb: error: paste subprocess was killed by signal (Broken pipe)
...
  Preparing to unpack .../59-plasma-desktop_4%3a5.17.5-1_amd64.deb ...
  Unpacking plasma-desktop (4:5.17.5-1) ...
  dpkg: error processing archive 
/tmp/apt-dpkg-install-tbnXT7/59-plasma-desktop_4%3a5.17.5-1_amd64.deb 
(--unpack):
   trying to overwrite 
'/usr/lib/x86_64-linux-gnu/qt5/qml/org/kde/plasma/private/showdesktop/libshowdesktopplugin.so',
 which is also in package plasma-widgets-addons 4:5.14.5.1-2+b2
  dpkg-deb: error: paste subprocess was killed by signal (Broken pipe)
  Errors were encountered while processing:
   /tmp/apt-dpkg-install-tbnXT7/55-plasma-desktop-data_4%3a5.17.5-1_all.deb
   /tmp/apt-dpkg-install-tbnXT7/59-plasma-desktop_4%3a5.17.5-1_amd64.deb


There is no guarantee of completeness in the above list ;-)


cheers,

Andreas


kdeplasma-addons-data=4:5.14.5.1-2_plasma-desktop-data=4:5.17.5-1.log.gz
Description: application/gzip

Bug#949319: ITS: tolua++

[Boyuan Yang]

Hi Vincent,

在 2020-01-19日的 14:49 -0800，Vincent Cheng写道：
> Hi Boyuan,
> 
> On Sun, Jan 19, 2020 at 11:39 AM Boyuan Yang  wrote:
> > Source: tolua++
> > Severity: important
> > Version: 1.0.93-3
> > X-Debbugs-CC: vch...@debian.org
> > 
> > Hi Vincent,
> > 
> > After looking into a package you maintain in Debian (tolua++,
> > https://tracker.debian.org/pkg/tolua++), I found that this package
> > received no
> > update since 2012 and is not in good shape. As a result, I am filing an
> > ITS
> > (Intent to Salvage) request against your package according to section 5.12
> > in
> > Debian Developers' Reference. [1]
> > 
> > Please let me know if you are still willing to maintain this package.
> > According to the criteria listed at [2], I will upload a Non-maintainer
> > Upload
> > (NMU) of tolua++ onto DELAYED/7 after 21 days (Feb. 09, 2020) to continue
> > with
> > the package salvaging. If it's necessary to pause the ITS process, please
> > let
> > me know immediately by replying this bug report.
> > 
> > Thank you for your previous work on tolua++ and looking forward to your
> > reply.
> 
> Sorry, I haven't been all that active in Debian recently. Please feel
> free to take over and/or co-maintain the package if you'd like. Thanks
> for taking care of this package!

Thanks! I'm likely to make uploads and fix existing issues/bugs recently.

-- 
Best,
Boyuan Yang

Bug#949319: ITS: tolua++

[Vincent Cheng]

Hi Boyuan,

On Sun, Jan 19, 2020 at 11:39 AM Boyuan Yang  wrote:
>
> Source: tolua++
> Severity: important
> Version: 1.0.93-3
> X-Debbugs-CC: vch...@debian.org
>
> Hi Vincent,
>
> After looking into a package you maintain in Debian (tolua++,
> https://tracker.debian.org/pkg/tolua++), I found that this package received no
> update since 2012 and is not in good shape. As a result, I am filing an ITS
> (Intent to Salvage) request against your package according to section 5.12 in
> Debian Developers' Reference. [1]
>
> Please let me know if you are still willing to maintain this package.
> According to the criteria listed at [2], I will upload a Non-maintainer Upload
> (NMU) of tolua++ onto DELAYED/7 after 21 days (Feb. 09, 2020) to continue with
> the package salvaging. If it's necessary to pause the ITS process, please let
> me know immediately by replying this bug report.
>
> Thank you for your previous work on tolua++ and looking forward to your reply.

Sorry, I haven't been all that active in Debian recently. Please feel
free to take over and/or co-maintain the package if you'd like. Thanks
for taking care of this package!

Regards,
Vincent

Bug#949333: prusa-slicer: Black blobs around drop-down menu icons

[Simon John]

Package: prusa-slicer
Version: 2.1.1+dfsg-1
Severity: normal

Dear Maintainer,

Both the new prusa-slicer and the previous slic3r-prusa Debian packages have
had the same problem - the icons on the print settings/filament/printer drop-
down menu's on the right of the window have black squares around them - perhaps
the gear/colour/printer icons are PNG's with black backgrounds instead of
transparent alpha channels?

It doesn't happen with the upstream tarball installs (never has).

Lots of errors on the console such as:

(prusa-slicer:3518470): Gtk-CRITICAL **: 22:23:03.038:
gtk_widget_set_allocation: assertion '_gtk_widget_get_visible (widget) ||
_gtk_widget_is_toplevel (widget)' failed

(prusa-slicer:3518470): Gtk-CRITICAL **: 22:23:21.035:
gtk_tree_selection_path_is_selected: assertion 'path != NULL' failed

(prusa-slicer:3518470): Gtk-CRITICAL **: 22:23:21.038:
gtk_tree_selection_select_path: assertion 'path != NULL' failed

(prusa-slicer:3518470): Gtk-CRITICAL **: 22:16:45.595:
gtk_tree_view_scroll_to_cell: assertion 'tree_view->priv->tree != NULL' failed

(prusa-slicer:3518470): Gtk-CRITICAL **: 22:16:46.006:
gtk_box_gadget_distribute: assertion 'size >= 0' failed in GtkScrollbar

(prusa-slicer:3518470): Gtk-WARNING **: 22:16:46.006: Negative content width
-19 (allocation 15, extents 17x17) while allocating gadget (node button, owner
GtkButton)

(prusa-slicer:3518470): Gtk-WARNING **: 22:16:46.017: Negative content height
-9 (allocation 1, extents 5x5) while allocating gadget (node button, owner
GtkToggleButton)

Also due to the use of GTK3's taller menu bar for plater/print
settings/filament settings/printer settings, in Expert mode the Estimated print
time is off the screen on the Debian build only.

Screenshots explaining the issues: https://imgur.com/a/wq4gwyw



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

Kernel: Linux 5.4.0-1-amd64 (SMP w/32 CPU cores)
Kernel taint flags: TAINT_WARN, TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE
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 prusa-slicer depends on:
ii  fonts-noto-hinted  20200103-1
ii  libboost-filesystem1.67.0  1.67.0-17
ii  libboost-locale1.67.0  1.67.0-17
ii  libboost-log1.67.0 1.67.0-17
ii  libboost-regex1.67.0 [libboost-regex1.67.0-icu63]  1.67.0-17
ii  libboost-system1.67.0  1.67.0-17
ii  libboost-thread1.67.0  1.67.0-17
ii  libc6  2.29-9
ii  libcurl3-gnutls7.67.0-2
ii  libexpat1  2.2.9-1
ii  libgcc11:9.2.1-24
ii  libgl1 1.3.0-7
ii  libglew2.1 2.1.0-4+b1
ii  libglu1-mesa [libglu1] 9.0.1-1
ii  libnlopt0  2.6.1-7
ii  libstdc++6 9.2.1-24
ii  libtbb22020.0-2
ii  libwxbase3.0-0v5   3.0.4+dfsg-15
ii  libwxgtk3.0-gtk3-0v5   3.0.4+dfsg-15

prusa-slicer recommends no packages.

prusa-slicer suggests no packages.

-- no debconf information

Bug#949100: [Pkg-clamav-devel] Bug#949100: clamav: loses link against libxml2 with 2.9.10 (uses xml2-config)

[Mattia Rizzolo]

On Sun, Jan 19, 2020 at 11:23:57PM +0100, Sebastian Andrzej Siewior wrote:
> On 2020-01-16 23:03:21 [+0100], Mattia Rizzolo wrote:
> > your package is using `xml2-config` to detect and use libxml2.  I'm
> > removing that script, so please update your build system to use
> > pkg-config instead.
> 
> Thanks for the report. I switched to pkg-config but dunno when I'm going
> to upload. Please let me know if I should hurry up.

I'm probably considering to do that upload sometime early februrary, so
not too soon.  I'll also bump all non-closed bugs to RC around a week
before, so that should also give people some kind of notice.
Having said that, I'm causing so many bugs that it might even get
later, but I definitely want to come back home from SnowCamp[0] with the
package in sid already :)

Is that alright for you?


[0] https://wiki.debian.org/DebianEvents/it/2020/SnowCamp
-- 
regards,
Mattia Rizzolo

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


signature.asc
Description: PGP signature

Bug#949100: [Pkg-clamav-devel] Bug#949100: clamav: loses link against libxml2 with 2.9.10 (uses xml2-config)

[Sebastian Andrzej Siewior]

On 2020-01-16 23:03:21 [+0100], Mattia Rizzolo wrote:
> your package is using `xml2-config` to detect and use libxml2.  I'm
> removing that script, so please update your build system to use
> pkg-config instead.

Thanks for the report. I switched to pkg-config but dunno when I'm going
to upload. Please let me know if I should hurry up.

Sebastian

Bug#949332: fwknop-apparmor-profile: consider adding ipset to apparmor profile

[Luca Filipozzi]

Package: fwknop-apparmor-profile
Version: 2.6.10-2
Severity: wishlist

Dear Maintainer,

One of the interesting modes of operation of fwknop-server is the use of
CMD_CYCLE_OPEN / CMD_CYCLE_CLOSE to call ipset to add entries to a set.

Pedantic sytem administrators may find that automatic insertion of
chains to be irksome and prefer to create/use an ipset in their firewall
configurations.

Since the documented[1][2] mode of operation provides an example that
uses ipset, please consider adding ipset to the apparmor profile.

Thanks,

Luca

[1]: https://www.cipherdyne.org/fwknop/docs/fwknop-tutorial.html#spa-with-ipset
[2]: 
https://www.cipherdyne.org/blog/2015/12/single-packet-authorization-and-third-party-devices.html


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

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

Versions of packages fwknop-apparmor-profile depends on:
ii  fwknop-server  2.6.10-2

fwknop-apparmor-profile recommends no packages.

fwknop-apparmor-profile suggests no packages.

-- Configuration Files:
/etc/apparmor.d/usr.sbin.fwknopd changed:
/usr/sbin/fwknopd {
  #include 
  capability ipc_lock,
  capability net_admin,
  capability net_raw,
  network inet raw,
  network inet dgram,
  network inet6 dgram,
  network packet raw,
  network packet dgram,
  /bin/dash rix,
  /bin/bash rix,
  /etc/fwknop/access.conf r,
  /etc/fwknop/fwknopd.conf r,
  /etc/nsswitch.conf r,
  /etc/passwd r,
  /etc/protocols r,
  @{PROC}/@{pid}/net/ip_tables_names r,
  /root/.gnupg/* rwkl,
  /run/fwknop/ rw,
  /run/fwknop/* rwk,
  /run/xtables.lock rwk,
  /sbin/ipset rix,
  /sbin/xtables-multi rix,
  /usr/bin/gpg rix,
  /usr/sbin/fwknopd mr,
  /usr/sbin/ipset rix,
  /usr/sbin/xtables-nft-multi rix,
  /var/cache/nscd/passwd r,
}


-- no debconf information

Bug#909740: libsdl2-dev: No longer multi-arch co-installable

[Felix Geyer]

Hi Hugh,

On 10.12.19 23:18, Hugh McMaster wrote:

At this point, I don’t see anything preventing us from adding the extra
include path, although I’m going to do some tests builds of various
SDL2-based programs to be certain.

Neverball could also be patched to call pkg-config with SDL2_ttf, which,
IIRC, has both include paths already (since SDL2_ttf requires SDL2).
Unfortunately, this won’t resolve the broader problem.


I've pushed this change to the git repo:
https://salsa.debian.org/sdl-team/libsdl2/commit/6f58f10282cf9b9af567ec520f0d2c4dc368dbea

Did you have time to test-build some reverse-dependencies of SDL2?

Cheers,
Felix

Bug#949299: coinor-vol misses source for configure

[Sudip Mukherjee]

Looks like I misread the bug report and thought it to be the same as
missing source for NEW upload. I will check about the source for the
configure script.

--
Regards
Sudip

Bug#949278: libreoffice hangs at startup if ~/.libreoffice folder does not exist

[Pierre Bernhardt]

Am 19.01.20 um 11:16 schrieb Rene Engelhard:
> On Sun, Jan 19, 2020 at 10:00:37AM +0100, Pierre Bernhardt wrote:
>> after removing my .libreoffice directory it will not startup fully any more.
>> The splash screen is shown ever and than it hangs as long I press Ctrl-C to
>> abort.
>>
>> I found a workaround by manually recreating simply the .libreoffice folder.
>>
>> I can reproduce the problem each time I remove or rename the .libreoffice
>> folder.
> 
> That's impossible.
> 
> That would mean that it always hanged on a new
> install where .libreoffice (actually that one doesn't exist, you mean
> .config/libreoffice) doesn't exist.

No, it is really my /home/user/.libreoffice folder which should normally
held users profile. I renamed it before I found the problem because
some menu entries was empty and a solution workaround where to remove
this directory which I then did. But then I got the hanging problem.

> Which does not happen.
At my computer problem happens:

starting libreoffice with strace -f shows me the problem because thousands
of lines like:


[pid 129252] mkdir("/home/pierre/.config/libreoffice/4", 0777) = -1 ENOENT 
(Datei oder Verzeichnis nicht gefunden)
[pid 129252] mkdir("/home/pierre/.config/libreoffice", 0777) = -1 EEXIST (Die 
Datei existiert bereits)
[pid 129252] mkdir("/home/pierre/.config/libreoffice/4", 0777) = -1 ENOENT 
(Datei oder Verzeichnis nicht gefunden)
[pid 129252] mkdir("/home/pierre/.config/libreoffice", 0777) = -1 EEXIST (Die 
Datei existiert bereits)
[pid 129252] mkdir("/home/pierre/.config/libreoffice/4", 0777) = -1 ENOENT 
(Datei oder Verzeichnis nicht gefunden)
[pid 129252] mkdir("/home/pierre/.config/libreoffice", 0777) = -1 EEXIST (Die 
Datei existiert bereits)
[pid 129252] mkdir("/home/pierre/.config/libreoffice/4", 0777^Cstrace: Process 
129238 detached
strace: Process 129250 detached
strace: Process 129251 detached
strace: Process 129252 detached
strace: Process 129253 detached

Checking .config/libreoffice shows me that this is a link to ../.libreoffice
folder:

user@nihilnihil:~$ ls -l /home/user/.config/libreoffice
lrwxrwxrwx 1 user user 15 Jun 14  2012 /home/user/.config/libreoffice -> 
../.libreoffice

As you can see it is really old aged link installed in the past.
mkdir than look like fails in a loop because it allready exists as a link and 
cannot be
created.

So best way looks like is to remove this link instead of creating the 
.libreoffice.
I think this link was been created in the past for compatibility reason and was 
never
removed later.

So workaround is to remove the old .config/libreoffice link will help.

A solution also could be to extend that the link should be ever followed by use 
absolute path
after followed the link, however this could become a vulnerable problem.
Another is to remove the link, if the target does not exist.
But the best is to catch this error by an exeption instead of run in an endless 
loop.

Cheers,

Bug#934444: i3lock-fancy does not fork

[Simon Désaulniers]

Hi dirdi,

I took your advice into accoutn and included the full notice under KNOWN BUGS
section while keeping a short (but highlighted) notice under the option's
description. This way, there should be no confusion. Thank you for the advice.

Regards,

On Wed, Jan 15, 2020 at 08:15:28PM +0100, dirdi wrote:
> @Simon: I think a notice should be sufficient, until the bug is fixed.
> However, I would add a "KNOWN BUGS" section to the end of the man page
> (cf. atool's man page:
> https://manpages.debian.org/buster/atool/atool.1.en.html) and file the
> notice under this section.

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


signature.asc
Description: PGP signature

Bug#949321: RFS: coinor-vol/1.5.4-2 [QA] -- Coin-or linear programming solver (libraries)

[Sudip Mukherjee]

On Sun, Jan 19, 2020 at 9:42 PM Sudip Mukherjee
 wrote:
>
> Hi Adam,
>
> On Sun, Jan 19, 2020 at 8:32 PM Adam Borowski  wrote:
> >
> > On Sun, Jan 19, 2020 at 08:00:28PM +, Sudip Mukherjee wrote:
> > >  * Package name: coinor-vol
> > >Version : 1.5.4-2
> >
> > > Changes since the last upload:
> > >
> > >* QA upload.
> > >* make separate short desciption.
> > >* Upload source. (Closes: #949299)
> >
> > Hi!
> > The debdiff from 1.5.4-1 shows only short desc changes, with nothing related
> > to configure sources.  Have you perhaps forgotten to add that?
>
> Ohh... sorry, I misread the bug report and and read it as a missing
> source. I will
> reupload a package to mentors removing "Closes: #949299" for now and
> will work on that.

New package uploaded now with the following changes-

Changes since the last upload:

   * QA upload.
   * make separate short desciption.


-- 
Regards
Sudip

Bug#949331: fwknop-server: consider building with nfq support

[Luca Filipozzi]

Package: fwknop-server
Version: 2.6.10-2
Severity: wishlist

Dear Maintainer,

Please consider building fwknopd with both pcap and nfq support so that
system administrators may elect to use nfq over pcap if their kernel
supports it (which Debian stock kernels do).

Thanks,

Luca

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

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

Versions of packages fwknop-server depends on:
ii  init-system-helpers  1.56+nmu1
ii  iptables 1.8.2-4
ii  libc62.28-10
ii  libfko3  2.6.10-2
ii  libpcap0.8   1.8.1-6
ii  lsb-base 10.2019051400

fwknop-server recommends no packages.

Versions of packages fwknop-server suggests:
ii  fwknop-apparmor-profile  2.6.10-2

Bug#940660: elpa-elpy: add Suggests: python3-rope to refactor code

[Nicholas D Steeves]

P.S. I recently read that `elpy-refactor` will use Black if it's
installed, but this is currently undocumented, and our upstream
contact is currently very busy so it might be a while.  I'm also
occupied with meeting an end-of-month deadline.


signature.asc
Description: PGP signature

Bug#949330: evolution: Google OAuth forces use of internal browser without way to change URL

[brian m. carlson]

Source: evolution
Version: 3.34.1-2+b1
Severity: important

At work, I use a Google Apps service with a single sign-on provider.  As
a result, I need to use a browser to authenticate to Google so I can use
OAuth2.

In addition, our company uses Duo Mobile, which restricts access to
users with up-to-date software.  The version of WebKit which is used is
viewed as a too-old version of Safari on macOS[0], and therefore
authentication is not permitted.

I can actually work around this issue by copying and pasting the URL
into Firefox, but I cannot then paste the URL from the sign-in flow back
into the URL bar in the internal browser, so I'm stuck and cannot log
in.  The Google OAuth2 flow, when run in Firefox, does provide me a
token I can paste back in, but Evolution cannot accept that token in
place of the login flow.

In order to be able to use Evolution with Google's OAuth2 flow, I need
one of the following to happen:

1. Evolution reports itself as a recent, modern (e.g., patched macOS
Catalina-equivalent) version of Safari and continues to update this
value.
2. Evolution allows using an external browser, such as Firefox, to log
in for OAuth2 flows.
3. Evolution allows pasting into the URL bar so I can paste the proper
URL in from Firefox (assuming it otherwise supports doing that).
4. Evolution allows pasting in the token from Google I can use in
Firefox instead.

[0] Not updating the user-agent appears to be a deliberate decision in
WebKit2GTK because "User Agent sniffing is…terrible…."  I agree, but I
don't make the decisions here.

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

Kernel: Linux 5.3.0-3-amd64 (SMP w/8 CPU cores)
Kernel taint flags: TAINT_WARN
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

-- 
brian m. carlson: Houston, Texas, US
OpenPGP: https://keybase.io/bk2204


signature.asc
Description: PGP signature

Bug#949321: RFS: coinor-vol/1.5.4-2 [QA] -- Coin-or linear programming solver (libraries)

[Sudip Mukherjee]

Hi Adam,

On Sun, Jan 19, 2020 at 8:32 PM Adam Borowski  wrote:
>
> On Sun, Jan 19, 2020 at 08:00:28PM +, Sudip Mukherjee wrote:
> >  * Package name: coinor-vol
> >Version : 1.5.4-2
>
> > Changes since the last upload:
> >
> >* QA upload.
> >* make separate short desciption.
> >* Upload source. (Closes: #949299)
>
> Hi!
> The debdiff from 1.5.4-1 shows only short desc changes, with nothing related
> to configure sources.  Have you perhaps forgotten to add that?

Ohh... sorry, I misread the bug report and and read it as a missing
source. I will
reupload a package to mentors removing "Closes: #949299" for now and
will work on that.


-- 
Regards
Sudip

Bug#949329: flatbuffers: Needs rebuild to migrate to testing

[Bálint Réczey]

Source: flatbuffers
Version: 1.11.0+dfsg1-1
Severity: serious

Hi,

The package needs a source-only upload to let it be rebuilt and only
then can it migrate to testing.
I've already added the fixes needed [1] for the rebuild to the
packaging repository on Salsa.

Cheers,
Balint

[1] https://salsa.debian.org/debian/flatbuffers/commits/debian/master

Bug#948207: Fixed in 19.12.2...

[Nicholas D Steeves]

Hi Eric,

Eric Valette  writes:

> On 19/01/2020 21:25, Eric Valette wrote:
>> The Google block will be fixed with kaccounts-providers 19.12.2.
>> 
>> 
>> --eric
> Fix is here:
>
> https://cgit.kde.org/kaccounts-providers.git/patch/?id=f26e97cfc9308bcc70a3b0b29a5fd9a4b9c42da2
>
> --eric

This is documented at Bug #948853, against kaccounts-providers.

To any team members reading this: please do not close this kio-gdrive
bug unless a buster update for kaccounts-providers is uploaded and
resolves the issue in stable.  I expect that buster is affected and
anticipate that a user with a new buster installation will file a "me
too" update to this bug sometime in the next six months.

Thanks,
Nicholas


signature.asc
Description: PGP signature

Bug#743650: Pssible fix

[Chubb, Peter (Data61, Kensington NSW)]

I added:
XTerm*VT100.color3: #707000

to ~/.Xresources to try to fix this.  The result is a horrible olive
colour on my screen, but at least it's now visible.  (The default
yellow colour for X is #00 which is fine against a dark
background, but almost invisible against white).
-- 
Dr Peter Chubb Tel: +61 2 9490 5852  http://ts.data61.csiro.au/
Trustworthy Systems GroupCSIRO's Data61

Bug#949328: ITP: fcitx5-chinese-addons -- Pinyin and table input method for fcitx5

[Boyuan Yang]

Package: wnpp
Severity: wishlist
Owner: Boyuan Yang 
X-Debbugs-CC: debian-de...@lists.debian.org

* Package name: fcitx5-chinese-addons
  Version : 0.0~git20200117.4261e23
  Upstream Author : Weng Xuetian 
* URL : https://github.com/fcitx/fcitx5-chinese-addons
* License : LGPL-2.1+
  Programming Lang: C++
  Description : Pinyin and table input method for fcitx5

 Fcitx5 is the next generation of fcitx input method framework. It
 provides plasant and modern input experience with intuitive graphical
 configuration tools. The framework is highly extensible with support
 for GTK+ and Qt toolkits, DBus interfaces, a large variety of desktop
 environments and a developer-friendly API.
 .
 This package provides Chinese-related addons for fcitx5, including
 builtin pinyin and table input methods.

It will be maintained under Debian Input Method Team.

-- 
Thanks,
Boyuan Yang


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

Bug#949324: groff: embeds path to grep and bash when built on usrmerge system

[Colin Watson]

On Sun, Jan 19, 2020 at 12:10:51PM -0800, Vagrant Cascadian wrote:
> When groff is built on a system with /usr merged, the paths to bash and
> grep get embedded in various files (/usr/bin/gdiffmk and some example
> documentation), resulting in an unreproducible build.
> 
> The attached patch passes BASH_PROG=/bin/bash and GREP=/bin/grep, which
> is compatible with both a usrmerge and non-usrmerge system.

Thanks; I committed a slight variant of this.

-- 
Colin Watson   [cjwat...@debian.org]

Bug#949257: xserver-xorg-core: Segmentation fault w/ 1.20.7

[Jamie Heilman]

Here's a thread apply all backtrace on the core with debug symbols
installed, hope it helps:

Thread 5 (Thread 0x7fb9cf169700 (LWP 16506)):
#0  futex_wait_cancelable (private=0, expected=0, futex_word=0x55a9340e07d8) at 
../sysdeps/unix/sysv/linux/futex-internal.h:88
#1  __pthread_cond_wait_common (abstime=0x0, mutex=0x55a9340e0788, 
cond=0x55a9340e07b0) at pthread_cond_wait.c:502
#2  __pthread_cond_wait (cond=cond@entry=0x55a9340e07b0, 
mutex=mutex@entry=0x55a9340e0788) at pthread_cond_wait.c:655
#3  0x7fb9d56fd93b in cnd_wait (mtx=0x55a9340e0788, cond=0x55a9340e07b0) at 
../include/c11/threads_posix.h:155
#4  util_queue_thread_func (input=input@entry=0x55a93416e4a0) at 
../src/util/u_queue.c:275
#5  0x7fb9d56fd557 in impl_thrd_routine (p=) at 
../include/c11/threads_posix.h:87
#6  0x7fb9d6f60fb7 in start_thread (arg=) at 
pthread_create.c:486
#7  0x7fb9d6e902cf in clone () at 
../sysdeps/unix/sysv/linux/x86_64/clone.S:95

Thread 4 (Thread 0x7fb9cd966700 (LWP 16509)):
#0  futex_wait_cancelable (private=0, expected=0, futex_word=0x55a9340e07d8) at 
../sysdeps/unix/sysv/linux/futex-internal.h:88
#1  __pthread_cond_wait_common (abstime=0x0, mutex=0x55a9340e0788, 
cond=0x55a9340e07b0) at pthread_cond_wait.c:502
#2  __pthread_cond_wait (cond=cond@entry=0x55a9340e07b0, 
mutex=mutex@entry=0x55a9340e0788) at pthread_cond_wait.c:655
#3  0x7fb9d56fd93b in cnd_wait (mtx=0x55a9340e0788, cond=0x55a9340e07b0) at 
../include/c11/threads_posix.h:155
#4  util_queue_thread_func (input=input@entry=0x55a93416ed80) at 
../src/util/u_queue.c:275
#5  0x7fb9d56fd557 in impl_thrd_routine (p=) at 
../include/c11/threads_posix.h:87
#6  0x7fb9d6f60fb7 in start_thread (arg=) at 
pthread_create.c:486
#7  0x7fb9d6e902cf in clone () at 
../sysdeps/unix/sysv/linux/x86_64/clone.S:95

Thread 3 (Thread 0x7fb9ce167700 (LWP 16508)):
#0  futex_wait_cancelable (private=0, expected=0, futex_word=0x55a9340e07d8) at 
../sysdeps/unix/sysv/linux/futex-internal.h:88
#1  __pthread_cond_wait_common (abstime=0x0, mutex=0x55a9340e0788, 
cond=0x55a9340e07b0) at pthread_cond_wait.c:502
#2  __pthread_cond_wait (cond=cond@entry=0x55a9340e07b0, 
mutex=mutex@entry=0x55a9340e0788) at pthread_cond_wait.c:655
#3  0x7fb9d56fd93b in cnd_wait (mtx=0x55a9340e0788, cond=0x55a9340e07b0) at 
../include/c11/threads_posix.h:155
#4  util_queue_thread_func (input=input@entry=0x55a93416e900) at 
../src/util/u_queue.c:275
#5  0x7fb9d56fd557 in impl_thrd_routine (p=) at 
../include/c11/threads_posix.h:87
#6  0x7fb9d6f60fb7 in start_thread (arg=) at 
pthread_create.c:486
#7  0x7fb9d6e902cf in clone () at 
../sysdeps/unix/sysv/linux/x86_64/clone.S:95

Thread 2 (Thread 0x7fb9ce968700 (LWP 16507)):
#0  futex_wait_cancelable (private=0, expected=0, futex_word=0x55a9340e07d8) at 
../sysdeps/unix/sysv/linux/futex-internal.h:88
#1  __pthread_cond_wait_common (abstime=0x0, mutex=0x55a9340e0788, 
cond=0x55a9340e07b0) at pthread_cond_wait.c:502
#2  __pthread_cond_wait (cond=cond@entry=0x55a9340e07b0, 
mutex=mutex@entry=0x55a9340e0788) at pthread_cond_wait.c:655
#3  0x7fb9d56fd93b in cnd_wait (mtx=0x55a9340e0788, cond=0x55a9340e07b0) at 
../include/c11/threads_posix.h:155
#4  util_queue_thread_func (input=input@entry=0x55a93416e6d0) at 
../src/util/u_queue.c:275
#5  0x7fb9d56fd557 in impl_thrd_routine (p=) at 
../include/c11/threads_posix.h:87
#6  0x7fb9d6f60fb7 in start_thread (arg=) at 
pthread_create.c:486
#7  0x7fb9d6e902cf in clone () at 
../sysdeps/unix/sysv/linux/x86_64/clone.S:95

Thread 1 (Thread 0x7fb9d6933f00 (LWP 16504)):
#0  __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:50
#1  0x7fb9d6dbb535 in __GI_abort () at abort.c:79
#2  0x55a933cd09aa in OsAbort () at ../../../../os/utils.c:1351
#3  0x55a933cd64f3 in AbortServer () at ../../../../os/log.c:879
#4  0x55a933cd7346 in FatalError (f=f@entry=0x55a933d0a4b0 "Caught signal 
%d (%s). Server aborting\n") at ../../../../os/log.c:1017
#5  0x55a933ccde15 in OsSigHandler (unused=, 
sip=0x7fffcfe329b0, signo=11) at ../../../../os/osinit.c:156
#6  OsSigHandler (signo=11, sip=0x7fffcfe329b0, unused=) at 
../../../../os/osinit.c:110
#7  
#8  0x55a933c4eabd in DamageRegister (pDrawable=0x0, 
pDamage=0x55a934105830) at ../../../../../miext/damage/damage.c:1746
#9  0x55a933becdf1 in xf86RotatePrepare (pScreen=0x55a9340b7680) at 
../../../../../../hw/xfree86/modes/xf86Rotate.c:160
#10 xf86RotateRedisplay (pScreen=pScreen@entry=0x55a9340b7680) at 
../../../../../../hw/xfree86/modes/xf86Rotate.c:181
#11 0x55a933bed5d1 in xf86CrtcRotate (crtc=crtc@entry=0x55a9340b0690) at 
../../../../../../hw/xfree86/modes/xf86Rotate.c:490
#12 0x7fb9d655efe7 in drmmode_set_mode_major (crtc=0x55a9340b0690, 
mode=0x55a9340b0778, rotation=, x=0, y=0) at 
../../src/drmmode_display.c:465
#13 0x55a933be3330 in xf86CrtcSetModeTransform 
(crtc=crtc@entry=0x55a9340b0690, mode=0x55a9340b0778, rotation=, 
transform=0x0, x=0, y=y@entry=0) at 

Bug#949327: reprotest fails in dpkg conffile question

[Laurent Bigonville]

Package: reprotest
Version: 0.7.12
Severity: important

Hi,

When using schroot, reprotest fails due to the dpkg conffile question:

Setting up netbase (6.0) ...

Configuration file '/etc/protocols'
 ==> File on system created by you or by a script.
 ==> File also in package provided by package maintainer.
   What would you like to do about it ?  Your options are:
Y or I  : install the package maintainer's version
N or O  : keep your currently-installed version
  D : show the differences between the versions
  Z : start a shell to examine the situation
 The default action is to keep your current version.
*** protocols (Y/I/N/O/D/Z) [default=N] ? dpkg: error processing package 
netbase (--configure):
 end of file on stdin at conffile prompt

"-o Dpkg::Options::=--force-confnew" should be added when calling
apt-get build-dep and maybe at other places

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)
Foreign Architectures: i386

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

Versions of packages reprotest depends on:
ii  apt-utils  1.8.4
ii  diffoscope 135
ii  libdpkg-perl   1.19.7
ii  procps 2:3.3.15-2+b1
ii  python33.7.5-3
ii  python3-debian 0.1.36
ii  python3-distro 1.3.0-2
ii  python3-pkg-resources  44.0.0-1
ii  python3-rstr   2.2.6-2

Versions of packages reprotest recommends:
pn  disorderfs   
pn  faketime 
ii  locales-all  2.29-9
ii  sudo 1.8.29-1

Versions of packages reprotest suggests:
ii  autodep8 0.22
pn  qemu-system  
ii  qemu-utils   1:4.2-1
ii  schroot  1.6.10-8

-- no debconf information

Bug#945722: pinot: Python2 removal in sid/bullseye - reopen 945722

[Sandro Tosi]

On Sun, Jan 19, 2020 at 3:19 PM Olly Betts  wrote:
>
> On Sat, Jan 18, 2020 at 09:58:15PM -0500, Sandro Tosi wrote:
> > This bug was closed, but the package has still some dependencies towards
> > Python2 packages, in details:
> >
> > (binary:pinot)Recommends->python-docutils
> >
> > Re-opening, so that they can be taken care of.
>
> The dependency is actually:
>
> Recommends: [...] python3-docutils | python-docutils [...]
>
> This really doesn't seem to justify RC severity to me.

nor there's any reason, technical or otherwise, to have such a
dependencies; my script isnt perfect, and didnt properly detect the
alternative dependencies not in primary position, but let's all look
at the bigger picture of the py2removal effort and avoid useless
packages relationships.

Regards,
-- 
Sandro "morph" Tosi
My website: http://sandrotosi.me/
Me at Debian: http://wiki.debian.org/SandroTosi
Twitter: https://twitter.com/sandrotosi

Bug#949294: solfege: help file not found

[François Mazen]

Hello Charles,

thanks for your bug report!

You should install the solfege-doc package to get the html files that
are referenced by the help link.

I agree that if the documentation package is not installed then the 404
html error is not informative. A better behavior would be to display a
nice error pop-up to indicate what to do.
In addition, the solfege package does not Recommends the solfege-doc
package, which violates the debian policy [1].

I'll try to upload a new package to fix these errors. In the meantime
you should install the solfege-doc package to resume your work.

Have a nice day,
François

[1] 
https://www.debian.org/doc/debian-policy/ch-docs.html#additional-documentation




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

Bug#948207: Fixed in 19.12.2...

[Eric Valette]

On 19/01/2020 21:25, Eric Valette wrote:

The Google block will be fixed with kaccounts-providers 19.12.2.


--eric

Fix is here:

https://cgit.kde.org/kaccounts-providers.git/patch/?id=f26e97cfc9308bcc70a3b0b29a5fd9a4b9c42da2

--eric

Bug#949321: RFS: coinor-vol/1.5.4-2 [QA] -- Coin-or linear programming solver (libraries)

[Adam Borowski]

On Sun, Jan 19, 2020 at 08:00:28PM +, Sudip Mukherjee wrote:
>  * Package name: coinor-vol
>Version : 1.5.4-2

> Changes since the last upload:
> 
>* QA upload.
>* make separate short desciption.
>* Upload source. (Closes: #949299)

Hi!
The debdiff from 1.5.4-1 shows only short desc changes, with nothing related
to configure sources.  Have you perhaps forgotten to add that?


Meow!
-- 
⢀⣴⠾⠻⢶⣦⠀ A MAP07 (Dead Simple) raspberry tincture recipe: 0.5l 95% alcohol,
⣾⠁⢠⠒⠀⣿⡁ 1kg raspberries, 0.4kg sugar; put into a big jar for 1 month.
⢿⡄⠘⠷⠚⠋⠀ Filter out and throw away the fruits (can dump them into a cake,
⠈⠳⣄ etc), let the drink age at least 3-6 months.

Bug#949227: This was fixed

[Thomas Goirand]

Hi,

I tried rebuilding the package, and it looks like the latest upload
fixed the issue (I could build the package without any problem).

If you believe I'm wrong, please reopen and let me know.

Cheers,

Thomas Goirand (zigo)

Bug#949326: transition: libgwenhywfar

[Micha Lenk]

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

Hi release team,

The Gwenhywfar package got its SONAME bumped in a recent release because some
deprecated API functions got removed. For this reason its reverse dependencies
need to be rebuilt at least.

Affected packages are

* https://tracker.debian.org/libchipcard successfully re-built in experimental.

* https://tracker.debian.org/libaqbanking successfully re-built in
  experimental.

* https://tracker.debian.org/gnucash will need a binNMU to pick up the new
  SONAME from libgwenhywfar.

* https://tracker.debian.org/kmymoney will need a binNMU to pick up the new
  SONAME from libgwenhywfar.

The auto-generated Ben transition tracker should do fine
https://release.debian.org/transitions/html/auto-libgwenhywfar.html

Best regards,
Micha Lenk

Bug#933631: Looks like fixed

[Thomas Goirand]

On 1/17/20 6:35 PM, Gianfranco Costamagna wrote:
> control: reopen -1
> 
> On Wed, 8 Jan 2020 10:17:23 +0100 Thomas Goirand  wrote:
>> I'm closing this bug. Feel free to reopen if there's still a problem.
>>
> 
> sorry for the late answer!
> 
> https://ci.debian.net/packages/k/kazoo/unstable/amd64/
> 
> looks like something is missing or not working properly on autopkgtests 
> environments.
> It might be a restriction that sbuild doesn't have, or something different in 
> your testing and the autopkgtest testing.
> 
> I'm not talking about a "build" issue but an "autopkgtest" issue. (something 
> related to "debian/tests" directory).
> 
> Trying to launch the test on a pbuilder environment shows the issue, as well 
> as sbuild.
> 
> Please let me know if something is still not clear,
> 
> Gianfranco

Hi,

I believe I fixed this with the latest upload. Please check.

Cheers,

Thomas Goirand (zigo)

Bug#948207: Fixed in 19.12.2...

[Eric Valette]

The Google block will be fixed with kaccounts-providers 19.12.2.


--eric

Bug#943855: RM: rust-crossbeam-utils-0.5/0.5.2-2

[Juhani Numminen]

Control: retitle 943855 RM: rust-crossbeam-utils-0.5 -- ROM; no longer in use

On Wed, 30 Oct 2019 21:16:10 +0100 Wolfgang Silbermayr  
wrote:
> The rust-crossbeam-utils-0.5 package is no longer in use. All reverse
> dependencies either migrated to a non-semver-suffixed version of rust-
> crossbeam-utils or don't depend on it anymore at all.
> The only remaining dependency as of now is rust-crossbeam-epoch-0.5 for which 
> I
> asked the maintainer to file a RM request as well.

Hi,

I retitled the bug to fit the ftp team "RM:" template.

Apparently rust-crossbeam-epoch-0.5 is still in unstable, though it was
removed from testing (#948606). Perhaps you should ask the maintainer again?

Regards,
Juhani

Bug#945722: pinot: Python2 removal in sid/bullseye - reopen 945722

[Olly Betts]

On Sat, Jan 18, 2020 at 09:58:15PM -0500, Sandro Tosi wrote:
> This bug was closed, but the package has still some dependencies towards
> Python2 packages, in details:
> 
> (binary:pinot)Recommends->python-docutils
> 
> Re-opening, so that they can be taken care of.

The dependency is actually:

Recommends: [...] python3-docutils | python-docutils [...]

This really doesn't seem to justify RC severity to me.

Cheers,
Olly

Bug#949318: systemsettings should Replace (or Conflict) kde-config-systemd << 5.17

[Pino Toscano]

In data domenica 19 gennaio 2020 20:30:18 CET, Antonio Russo ha scritto:
> Package: systemsettings
> Version: 4:5.17.5-1
> Severity: normal
> 
> During an upgrade from testing (4:5.14.5.1-5+b1) to experimental, 
> systemsettings
> tries to overwrite files in kde-config-systemd.

The conflict is due to the following file:

/usr/share/kservices5/settings-system-administration.desktop

(hint: please mention all the conflicting files when reporting this
kind of bugs, or at least paste an English output of apt/aptitude/etc)

Basically System Settings "adopted" the System Administration category
that so far was introduced only with kde-config-systemd. The fix will
be removing that file in kde-config-systemd, and adding proper
breaks/replaces in systemsettings with the right version of
kde-config-systemd that removes the file.

-- 
Pino Toscano

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

Bug#949324: groff: embeds path to grep and bash when built on usrmerge system

[Vagrant Cascadian]

Source: groff
Severity: wishlist
Tags: patch
User: reproducible-bui...@lists.alioth.debian.org
Usertags: usrmerge environment
X-Debbugs-Cc: reproducible-b...@lists.alioth.debian.org

When groff is built on a system with /usr merged, the paths to bash and
grep get embedded in various files (/usr/bin/gdiffmk and some example
documentation), resulting in an unreproducible build.

The attached patch passes BASH_PROG=/bin/bash and GREP=/bin/grep, which
is compatible with both a usrmerge and non-usrmerge system.

live well,
  vagrant
From 3daefd47779ff0c1bdaf23a023f313127cc19f84 Mon Sep 17 00:00:00 2001
From: Vagrant Cascadian 
Date: Sun, 19 Jan 2020 11:37:53 -0800
Subject: [PATCH] debian/rules: Pass BASH_PROG and GREP to configure to ensure
 reproducible builds regardless of weather system is a usrmerge or
 non-usrmerge system.

---
 debian/rules | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/debian/rules b/debian/rules
index 4562bd67..27d4be2a 100755
--- a/debian/rules
+++ b/debian/rules
@@ -47,7 +47,7 @@ override_dh_autoreconf:
 
 override_dh_auto_configure:
 	-rm -f config.log config.cache
-	$(buildflags) dh_auto_configure -- $(confflags)
+	$(buildflags) dh_auto_configure -- $(confflags) BASH_PROG=/bin/bash GREP=/bin/grep
 ifneq ($(DEB_BUILD_GNU_TYPE),$(DEB_HOST_GNU_TYPE))
 	$(buildflags_native) dh_auto_configure \
 		--builddirectory=debian/build-native -- \
-- 
2.20.1



signature.asc
Description: PGP signature

Bug#949325: libmysofa: CVE-2020-6860

[Salvatore Bonaccorso]

Source: libmysofa
Version: 0.9.1~dfsg0-1
Severity: important
Tags: security upstream
Forwarded: https://github.com/hoene/libmysofa/issues/96

Hi,

The following vulnerability was published for libmysofa.

CVE-2020-6860[0]:
| libmysofa 0.9.1 has a stack-based buffer overflow in readDataVar in
| hdf/dataobject.c during the reading of a header message attribute.


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

For further information see:

[0] https://security-tracker.debian.org/tracker/CVE-2020-6860
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-6860
[1] https://github.com/hoene/libmysofa/issues/96
[2] 
https://github.com/hoene/libmysofa/commit/c31120a4ddfe3fc705cfdd74da7e884e1866da85

Please adjust the affected versions in the BTS as needed.

Regards,
Salvatore

Bug#949323: fwknop-server: does not wait for network-online so fails to start in pcap mode

[Luca Filipozzi]

Package: fwknop-server
Version: 2.6.10-2
Severity: important

Dear Maintainer,

Thank you for packaging fwknop for Debian.

The systemd service file for fwknop-server is missing a Wants directive:

  Wants=network-online.target  <-- missing
  After=network-online.target

Per the systemd documentation[1], both Wants and After are required when
using the network-online.target.

Without the Wants directive, fwknop-server, in PCAP mode, fails to start
because the interface is not ready.

Thanks,

Luca

[1]: https://www.freedesktop.org/wiki/Software/systemd/NetworkTarget/

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

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

Versions of packages fwknop-server depends on:
ii  init-system-helpers  1.56+nmu1
ii  iptables 1.8.2-4
ii  libc62.28-10
ii  libfko3  2.6.10-2
ii  libpcap0.8   1.8.1-6
ii  lsb-base 10.2019051400

fwknop-server recommends no packages.

Versions of packages fwknop-server suggests:
ii  fwknop-apparmor-profile  2.6.10-2

Bug#949322: python-pysaml2: CVE-2020-5390

[Salvatore Bonaccorso]

Source: python-pysaml2
Version: 4.5.0-5
Severity: grave
Tags: security upstream
Justification: user security hole
Control: found -1 4.5.0-4

Hi,

The following vulnerability was published for python-pysaml2.

CVE-2020-5390[0]:
| PySAML2 before 5.0.0 does not check that the signature in a SAML
| document is enveloped and thus signature wrapping is effective, i.e.,
| it is affected by XML Signature Wrapping (XSW). The signature
| information and the node/object that is signed can be in different
| places and thus the signature verification will succeed, but the wrong
| data will be used. This specifically affects the verification of
| assertion that have been signed.


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

For further information see:

[0] https://security-tracker.debian.org/tracker/CVE-2020-5390
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-5390
[1] 
https://github.com/IdentityPython/pysaml2/commit/5e9d5acbcd8ae45c4e736ac521fd2df5b1c62e25

Please adjust the affected versions in the BTS as needed.

Regards,
Salvatore

Bug#949317: plasma-workspace should Replace (or Conflict) plasma-desktop and plasma-desktop-data << 5.17

[Pino Toscano]

tag 949317 + pending
thanks

Hi,

In data domenica 19 gennaio 2020 20:26:55 CET, Antonio Russo ha scritto:
> Package: plasma-workspace
> Version: 4:5.17.5-1
> Severity: normal
> 
> During an upgrade from testing (4:5.14.5.1-5+b1) to experimental, 
> plasma-workspace
> tries to overwrite files in plasma-desktop and plasma-desktop data.

Thanks, fixed in the packaging repository, and it will be part of the
next upload.

PS: considering there will be more issues like this, please report them
to the debian-kde mailing list for now.

Thanks,
-- 
Pino Toscano

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

Bug#943683: RM: hgsvn/0.1.8-1.1

[Juhani Numminen]

retitle -1 RM: hgsvn -- ROM; not maintained upstream, not usable with current 
mercurial and subversion

On Mon, 28 Oct 2019 00:22:29 +0100 Vincent Danjean  wrote:

>   Hi,
> 
>   Can you remove this package from unstable ? It is
> completly buggy in oldstable (see #907494), not
> present in stable and testing, not maintained
> upstream anymore and not usable with current
> versions of mercurial and subversion (see last
> message in #907494).
> 
>   Regards,
> Vincent

Hi,

Somehow this removal request has not progressed even though
the FTP team are otherwise keeping up with the influx of "RM" bugs
(kudos to the FTP masters for doing that!). I'll retitle according
to directions at https://ftp-master.debian.org/removals.html.

--
Juhani

Bug#949321: RFS: coinor-vol/1.5.4-2 [QA] -- Coin-or linear programming solver (libraries)

[Sudip Mukherjee]

Package: sponsorship-requests
Severity: normal

Dear mentors,

I am looking for a sponsor for my package "coinor-vol"

 * Package name: coinor-vol
   Version : 1.5.4-2
   Upstream Author : Francisco Barahona, Laszlo Ladanyi.
 * URL : https://projects.coin-or.org/Vol
 * License : EPL-1
 * Vcs : https://salsa.debian.org/debian/coinor-vol
   Section : science

It builds those binary packages:

  coinor-libvol1 - Coin-or linear programming solver (libraries)
  coinor-libvol-dev - Coin-or linear programming solver (development files)
  coinor-libvol-doc - Coin-or linear programming solver

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

  https://mentors.debian.net/package/coinor-vol

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

  dget -x 
https://mentors.debian.net/debian/pool/main/c/coinor-vol/coinor-vol_1.5.4-2.dsc

Changes since the last upload:

   * QA upload.
   * make separate short desciption.
   * Upload source. (Closes: #949299)


-- 
Regards
Sudip

Bug#945722: pinot: diff for NMU version 1.05-4.1

[Sandro Tosi]

Control: tags 945722 + patch


Dear maintainer,

I've prepared an NMU for pinot (versioned as 1.05-4.1). The diff
is attached to this message.

Regards.

diff -Nru pinot-1.05/debian/changelog pinot-1.05/debian/changelog
--- pinot-1.05/debian/changelog	2019-11-27 20:16:46.0 -0500
+++ pinot-1.05/debian/changelog	2020-01-19 14:45:31.0 -0500
@@ -1,3 +1,10 @@
+pinot (1.05-4.1) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * Drop unnecessary alternative Recommends on python-docutils; Closes: #945722
+
+ -- Sandro Tosi   Sun, 19 Jan 2020 14:45:31 -0500
+
 pinot (1.05-4) unstable; urgency=medium
 
   * debian/control: Update to recommending python3-docutils | python-docutils
diff -Nru pinot-1.05/debian/control pinot-1.05/debian/control
--- pinot-1.05/debian/control	2019-11-27 20:16:43.0 -0500
+++ pinot-1.05/debian/control	2020-01-19 14:45:04.0 -0500
@@ -37,7 +37,7 @@
 Depends: default-dbus-session-bus | dbus-session-bus,
  ${misc:Depends},
  ${shlibs:Depends}
-Recommends: antiword, catdoc, catdvi, djvulibre-bin, poppler-utils, unrtf, unzip, python3-docutils | python-docutils, bzip2
+Recommends: antiword, catdoc, catdvi, djvulibre-bin, poppler-utils, unrtf, unzip, python3-docutils, bzip2
 Suggests: file, rpm
 Description: meta-search engine for local files and web queries
  Pinot provides a D-Bus service that crawls, indexes your documents and

Bug#949320: man-db: produces kernel warnings attempting to write a file in /tmp

[Nate Bargmann]

Package: man-db
Version: 2.9.0-2
Severity: normal

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Dear Maintainer,

   * What led up to the situation?

Attempting to convert nroff source to HTML using 'man -Thtml' invocation.

   * What was the outcome of this action?

The following message was written to the kernel log.  Output of dmesg follows:

[Jan18 13:00] audit: type=1400 audit(1579461095.803:24): apparmor="DENIED" 
operation="file_inherit" profile="man_groff" name="/tmp/groff-regions-NiehKf" 
pid=58336 comm="troff" requested_mask="w" denied_mask="w" fsuid=1000 ouid=1000

   * What outcome did you expect instead?

No such message.


On my Buster Gnome desktop I kept getting pop-ups from App Armor and found bug
945909 and resolved the issue of reading /etc/papersize by manually applying
the included patc.  However, these messages are also being generated on the
Buster desktop as well as this laptop running Bullseye.

- - Nate

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

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

Versions of packages man-db depends on:
ii  bsdmainutils   11.1.2+b1
ii  debconf [debconf-2.0]  1.5.73
ii  dpkg   1.19.7
ii  groff-base 1.22.4-4
ii  libc6  2.29-7
ii  libgdbm6   1.18.1-5
ii  libpipeline1   1.5.2-2
ii  libseccomp22.4.2-2
ii  zlib1g 1:1.2.11.dfsg-1+b1

man-db recommends no packages.

Versions of packages man-db suggests:
ii  apparmor2.13.3-7
ii  chromium [www-browser]  76.0.3809.100-1
ii  epiphany-browser [www-browser]  3.34.1-1+b1
ii  firefox-esr [www-browser]   68.4.1esr-1
ii  groff   1.22.4-4
ii  less551-1
ii  lynx [www-browser]  2.9.0dev.4-1

- -- debconf information:
  man-db/auto-update: true
  man-db/install-setuid: false

-BEGIN PGP SIGNATURE-

iGsEARECACsWIQSC1k9rDmfNQfaJu6b7LFEw1VqIGQUCXiSuow0cbjBuYkBuMG5i
LnVzAAoJEPssUTDVWogZV0sAn07hvI2Wg4eKpewuXY6oU+oRMM5CAJ418HkPPWpP
NUxeo0a8zWUjEnFBQw==
=rKIm
-END PGP SIGNATURE-

Bug#948372: Please push your changes to nibabel

[Yaroslav Halchenko]

On Sun, 19 Jan 2020, Andreas Tille wrote:

> Hi Yaroslav,

> can you please push your latest changes to nibabel?  I'd volunteer
> to fix #948372 and when doing so move the repository to Debian Med
> if you do not mind.

actually as far as I see it Sando has pushed everything for
2.5.1-2
https://salsa.debian.org/neurodebian-team/nibabel/blob/dist/debian/proper/debian/changelog
which is the latest AFAIK

PS I have changed the default branch on salsa to dist/debian/proper to
match the one we used as one of our utopian plans to stay organized for
different distributions/releases ;)

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

Bug#946169: acpi-override: diff for NMU version 0.1+nmu1

[Boyuan Yang]

Control: tags 946169 + patch
Control: tags 946169 + pending

Dear maintainer,

I've prepared an NMU for acpi-override (versioned as 0.1+nmu1) and
uploaded it to DELAYED/7. Please feel free to tell me if I
should delay it longer.

Regards.

diff -Nru acpi-override-0.1/debian/changelog acpi-override-
0.1+nmu1/debian/changelog
--- acpi-override-0.1/debian/changelog  2019-10-31 15:32:35.0 -0400
+++ acpi-override-0.1+nmu1/debian/changelog 2020-01-19 14:27:02.0
-0500
@@ -1,3 +1,11 @@
+acpi-override (0.1+nmu1) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * No-change source-only upload to allow testing migration.
+(Closes: #946169)
+
+ -- Boyuan Yang   Sun, 19 Jan 2020 14:27:02 -0500
+
 acpi-override (0.1) unstable; urgency=medium
 
   * Upload to debian.


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

Bug#949319: ITS: tolua++

[Boyuan Yang]

Source: tolua++
Severity: important
Version: 1.0.93-3
X-Debbugs-CC: vch...@debian.org

Hi Vincent,

After looking into a package you maintain in Debian (tolua++, 
https://tracker.debian.org/pkg/tolua++), I found that this package received no
update since 2012 and is not in good shape. As a result, I am filing an ITS
(Intent to Salvage) request against your package according to section 5.12 in
Debian Developers' Reference. [1]

Please let me know if you are still willing to maintain this package.
According to the criteria listed at [2], I will upload a Non-maintainer Upload
(NMU) of tolua++ onto DELAYED/7 after 21 days (Feb. 09, 2020) to continue with
the package salvaging. If it's necessary to pause the ITS process, please let
me know immediately by replying this bug report.

Thank you for your previous work on tolua++ and looking forward to your reply.

[1] 
https://www.debian.org/doc/manuals/developers-reference/pkgs.en.html#package-salvaging
[2] https://wiki.debian.org/PackageSalvaging

-- 
Best Regards,
Boyuan Yang


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

Bug#949318: systemsettings should Replace (or Conflict) kde-config-systemd << 5.17

[Antonio Russo]

Package: systemsettings
Version: 4:5.17.5-1
Severity: normal

During an upgrade from testing (4:5.14.5.1-5+b1) to experimental, systemsettings
tries to overwrite files in kde-config-systemd.

Bug#949317: plasma-workspace should Replace (or Conflict) plasma-desktop and plasma-desktop-data << 5.17

[Antonio Russo]

Package: plasma-workspace
Version: 4:5.17.5-1
Severity: normal

During an upgrade from testing (4:5.14.5.1-5+b1) to experimental, 
plasma-workspace
tries to overwrite files in plasma-desktop and plasma-desktop data.

Bug#949315: cups-filters: driverless generates wrong InputSlots

[Martin Mares]

Package: cups-filters
Version: 1.21.6-5
Severity: important

When I use "driverless" to generate a PPD for my Xerox B215 printer,
I get definition of InputSlot which does not work.

In particular, the printer reports that it supports media source "tray-1".
This is translated to "Tray-1" by driverless, so the PPD contains:

*InputSlot Tray-1/Tray 1: ""

When I submit a print job, CUPS's IPP backend translates this to IPP
media source "tray--1", which is later rejected by the printer (the printer
replies by a malformed IPP message, but that's another story).

The problem lies in the mismatch between name mangling rules in
cups-filters-1.21.6/cupsfilters/ppdgenerator.c (the pwg_ppdize_name function)
and
cups-2.2.10/cups/ppd-cache.c (the pwg_unppdize_name function). It is hard
to tell which one is wrong as the name mangling rules seem arbitrary. However,
at least one of them needs fixing.

I checked cups-filters 1.26.2 and CUPS 2.3.1 and the name mangling functions
stay the same, so the problem is probably still present.


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

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

Versions of packages cups-filters depends on:
ii  bc 1.07.1-2+b1
ii  cups-filters-core-drivers  1.21.6-5
ii  ghostscript9.27~dfsg-2+deb10u3
ii  libc6  2.28-10
ii  libcups2   2.2.10-6+deb10u1
ii  libcupsfilters11.21.6-5
ii  libcupsimage2  2.2.10-6+deb10u1
ii  libfontconfig1 2.13.1-2
ii  libfontembed1  1.21.6-5
ii  libgcc11:8.3.0-6
ii  libqpdf21  8.4.0-2
ii  libstdc++6 8.3.0-6
ii  poppler-utils  0.71.0-5

Versions of packages cups-filters recommends:
ii  colord 1.4.3-4
ii  liblouisutdml-bin  2.7.0-5+b1

Versions of packages cups-filters suggests:
ii  antiword 0.37-14
pn  docx2txt 
ii  foomatic-db  20181217-2
ii  imagemagick  8:6.9.10.23+dfsg-2.1
ii  imagemagick-6.q16 [imagemagick]  8:6.9.10.23+dfsg-2.1

-- Configuration Files:
/etc/modules-load.d/cups-filters.conf changed [not included]

-- no debconf information

Bug#949316: parted: please cherry-pick ChromeOS Kernel partition flag

[Alper Nebi Yasak]

Source: parted
Version: 3.3-1
Severity: wishlist
Tags: fixed-upstream d-i

Dear Maintainer,

The firmware/bootloader in ChromeOS machines only attempts to boot from 
partitions of a certain GPT partition type. Please cherry-pick my commit 
08256913c307e0313ee014e0f292fa335cc18f1d from upstream [1], which adds 
support for it.


I've managed to get debian-installer working on my chromebook and I'm 
trying to upstream my changes. Part of that work is enabling partman to 
create these partitions (see my partman-cros [2]), which requires 
libparted2-udeb to understand this flag, so I've added the 'd-i' tag.


[1] 
https://git.savannah.gnu.org/cgit/parted.git/commit/?id=08256913c307e0313ee014e0f292fa335cc18f1d

[2] https://salsa.debian.org/alpernebbi-guest/partman-cros

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

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

Bug#949314: Add support for creating files with default SELinux context

[Christian Göttsche]

Package: ucf
Version: 3.0038+nmu1
User: selinux-de...@lists.alioth.debian.org
Usertags: selinux
Tags: patch

Currently ucf does not support to create the destination files with
the correct SELinux type.

See https://salsa.debian.org/srivasta/ucf/merge_requests/2 for a patch.

Bug#949313: ITP: php-nikic-fast-route -- Fast request router for PHP

[James Valleroy]

Package: wnpp
Severity: wishlist
Owner: James Valleroy 

* Package name: php-nikic-fast-route
  Version : 1.3.0
  Upstream Author : Nikita Popov 
* URL : https://github.com/nikic/FastRoute
* License : BSD-3-clause
  Programming Lang: PHP
  Description : Fast request router for PHP

Fast HTTP request router for PHP using regular expressions for
placeholders. Supports route grouping and caching. The route parser
and dispatcher components can be overridden.

FastRoute is a dependency for php-slim (ITP #949014). I will maintain
it within Debian PHP PEAR Maintainers team.

Bug#946100: [Python-modules-team] Bug#946100: close 946100

[Louis-Philippe Véronneau]

Ooops, you are right, sorry.

I modified d/changelog accordingly.

Cheers!

-- 
  ⢀⣴⠾⠻⢶⣦⠀
  ⣾⠁⢠⠒⠀⣿⡁  Louis-Philippe Véronneau
  ⢿⡄⠘⠷⠚⠋   po...@debian.org / veronneau.org
  ⠈⠳⣄



signature.asc
Description: OpenPGP digital signature

Bug#949311: os-prober hangs Mageia 7 x86_64 kernel installation

[John Paul Adrian Glaubitz]

Hi!

On 1/19/20 6:15 PM, Rolf Pedersen wrote:
> Package: os-prober
> Version: 1.74-4
> 
> Thierry Vignaud, Mageia devel, asked that I submit this bug.  Probably the 
> most relevant
> comment from my bug, there, is: 
> https://bugs.mageia.org/show_bug.cgi?id=25873#c8
Can you elaborate on the issue a bit more? I'm not sure how Debian is 
responsible for
problems in other distributions. I don't see any other mentioning of Debian in 
the
Mageia bug report.

Thanks,
Adrian

-- 
 .''`.  John Paul Adrian Glaubitz
: :' :  Debian Developer - glaub...@debian.org
`. `'   Freie Universitaet Berlin - glaub...@physik.fu-berlin.de
  `-GPG: 62FF 8A75 84E0 2956 9546  0006 7426 3B37 F5B5 F913

Bug#949130: refind-install fails to determine the ESP partition

[Pelzi]

Hi Tianon,

I found the cure for the problem: the ESP partition was listed as fs type 
„msdos“ in fstab. Changing this to „vfat" made refind-install work for me.

Best regards,
Andreas.

> Am 17.01.2020 um 15:56 schrieb Tianon Gravi :
> 
> On Fri, 17 Jan 2020 at 01:39, Andreas Feldner  > wrote:
>> on an existing installation, the refind package started to break apt-get 
>> upgrade runs,
>> presumably with the availability of an update of the package.
>> 
>> The issue arrived w/o interaction on unattended upgrade runs and can easily 
>> reproduced
>> by manual runs of refind-install.
>> 
>> The result of apt-get upgrade or unattended-upgrade runs:
>> 
>>> refind (0.11.4-1) wird eingerichtet ...
>>> Installing rEFInd to the ESP...
>>> mount: /boot/efi: /dev/sda2 already mounted on /boot/efi.
>>> dpkg: Fehler beim Bearbeiten des Paketes refind (--configure):
>>> »installiertes refind-Skript des Paketes post-installation«-Unterprozess 
>>> gab den Fehlerwert 1 zurück
>>> Fehler traten auf beim Bearbeiten von:
>>> refind
>> 
>> The output of manually running refind-install is reproducably:
>>> $ sudo refind-install
>>> ShimSource is none
>>> Installing rEFInd on Linux
>>> The ESP doesn't seem to be mounted! Trying to find it
>>> mount: /boot/efi: /dev/sda2 already mounted on /boot/efi.
>>> boot/efi doesn't seem to be on a VFAT filesystem. The ESP must be
>>> mounted at //boot or //boot/efi and it must be VFAT! Aborting!
>> 
>> Notes:
>> - The ESP was mounted to /boot/efi before running refind-install, but is 
>> unmounted by the command (and left unmounted).
>> - No explicit configuration of --root is given. The vast number of leading / 
>> is produced by the script
>> - Running the script with /boot/efi mounted or unmounted does not change any 
>> output
>> - The system is currently booting via refind using the ESP partition in 
>> question, i.e. was set up by previous versions of refind
>> 
>> 
>> Expected output:
>> - The script should not add multiple leading slashes to the mount point and 
>> then fail to find it in mtab or block device lists
>> - refind should update the installation to the new version
> 
> This is definitely odd, and I'm hoping Rod has some ideas for what's
> going on, but can you also share the contents of "/etc/fstab" and
> "/etc/mtab" on your system?
> 
> I think the output of "df" might be useful too, looking at the bits of
> "refind-install" that seem to be misfiring.
> 
>> -- System Information:
>> Debian Release: bullseye/sid
>>  APT prefers testing
>>  APT policy: (990, 'testing'), (500, 'stable')
>> Architecture: amd64 (x86_64)
>> Foreign Architectures: i386
>> 
>> Kernel: Linux 5.3.0-3-amd64 (SMP w/4 CPU cores)
>> Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8), LANGUAGE= 
>> (charmap=UTF-8)
>> Shell: /bin/sh linked to /bin/bash
>> Init: systemd (via /run/systemd/system)
>> LSM: AppArmor: enabled
>> 
>> Versions of packages refind depends on:
>> ii  debconf [debconf-2.0]  1.5.73
>> ii  efibootmgr 15-1+b1
>> ii  openssl1.1.1d-2
>> ii  parted 3.3-1
>> 
>> Versions of packages refind recommends:
>> ii  python3 3.7.5-3
>> ii  sbsigntool  0.9.2-2
>> 
>> refind suggests no packages.
>> 
>> -- debconf information:
>> * refind/install_to_esp: true
> 
> ♥,
> - Tianon
>  4096R / B42F 6819 007F 00F8 8E36  4FD4 036A 9C25 BF35 7DD4

Bug#949312: txsocksx: should this package be removed?

[Sandro Tosi]

Source: txsocksx
Severity: serious

Hello,
i think txsocksx should be removed from debian:

* python2-only
* upstream is not progressing on the py3k porting: 
https://github.com/habnabit/txsocksx/issues/19
* leaf package

if i dont hear back within a week with a good reason to keep this package, i'll
file for its removal.

Regards,
Sandro

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

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

Bug#949311: os-prober hangs Mageia 7 x86_64 kernel installation

[Rolf Pedersen]

Package: os-prober
Version: 1.74-4

Thierry Vignaud, Mageia devel, asked that I submit this bug.  Probably 
the most relevant comment from my bug, there, is: 
https://bugs.mageia.org/show_bug.cgi?id=25873#c8


I administer 3 machines on the LAN via ssh, using urpmi for package 
management.  Recently, seemingly starting with kernel 5.4, one machine 
fails to complete routine upgrades that include kernel, sticking on 
installation of the kernel.  The others continue to succeed.  There are 
details in that bug report that might be helpful.  Tell me what more is 
needed.

Thanks,
Rolf
p.s. I tried to follow instructions to use 'reportbug', converting a deb 
to rpm, but execution of the installed binary ended in segfault, 
probably for good reason.  I hope this works; my Debian proficiency is 
limited.

Bug#949310: buster-pu: package gnutls28/3.6.7-4+deb10u1

[Andreas Metzler]

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

Hello,

there is a regression in gnutls/buster compared to stretch. It fails to
parse certificates using Registered ID in Subject Alternative Name.

See upstream report https://gitlab.com/gnutls/gnutls/issues/905 for more
details.

I would like to fix this in pu, by pulling the fix from GnuTLS 3.6.9.
The respective upstream change also adds a testcase and therefore
adds/modifies binaries. The proposed Debian changes are not
representable as debdiff, I am attaching git-format-patch diff instead.

cu Andreas
From de3d573242195eddab914709584242610b2e2762 Mon Sep 17 00:00:00 2001
From: Andreas Metzler 
Date: Sun, 19 Jan 2020 18:00:12 +0100
Subject: [PATCH] Fix parsing of certificates using RegisteredID Closes:
 #949293

---
 debian/binary/cert10.der  | Bin 0 -> 571 bytes
 debian/binary/cert5.der   | Bin 0 -> 414 bytes
 debian/changelog  |   6 +
 ...ralname-registeredID-from-RFC-5280-i.patch | 242 ++
 debian/patches/series |   1 +
 debian/rules  |   8 +
 debian/source/include-binaries|   2 +
 7 files changed, 259 insertions(+)
 create mode 100644 debian/binary/cert10.der
 create mode 100644 debian/binary/cert5.der
 create mode 100644 debian/patches/41_rel3.6.9_01-Support-for-Generalname-registeredID-from-RFC-5280-i.patch

diff --git a/debian/binary/cert10.der b/debian/binary/cert10.der
new file mode 100644
index ..07ab16d3eec034bd14cd94dd0174a2a76c768918
GIT binary patch
literal 571
zcmXqLVlp>qV!XS6nTe5!i7~~1i;Y98~}r=h5UFdK6y3o{Rod$6ygLP%`WXB7yE<
z2fL4n5$aH8Ms{W=1{U9cSH5JrPuwpy_1pr3D$^|zjMJuCRBw;2RdL_8Rbf7h>pH)<
zAeoC69oOR@)U-AzX+7fIwMMr5Y?*=QWGCtCmWvy28Z=%rkOx{StIQ%{Al4xA)v;*r