Bug#925327: gpsd: CVE-2018-17937

[Salvatore Bonaccorso]

Hi Bernd,

On Fri, Mar 29, 2019 at 10:54:50PM +0100, Bernd Zeimetz wrote:
> Hi Salvatore,
> 
> > The following vulnerability was published for gpsd, not competely sure
> > on severity and on if the referenced upstream commit is enough.
> > Ideally though the fix seems ideal to go to buster.
> 
> I've tried to get more information out of Upstream, but did not get a
> reply yet. So I'll prepare an upload with the mentioned commit. Looking
> trough the commit logs from gpsd it seems to be the only relevant one.

Ack thank you for investigating, I was neither more successfull to
determine if that's enough.

Cc;ing the security team alias, if anyone has more ideas.

Thanks for your work!

Salvatore

Bug#924278: stretch-pu: package clamav/0.100.2+dfsg-0+deb9u1

[Scott Kitterman]

On Wed, 27 Mar 2019 19:43:13 + "Adam D. Barratt"  wrote:
> On Wed, 2019-03-27 at 19:54 +0100, Sebastian Andrzej Siewior wrote:
> > On 2019-03-10 23:55:55 [+0100], To sub...@bugs.debian.org wrote:
> > > We would like to update clamav in stable to 0.101.1 which is the
> > > latest
> > > release provided by upstream.
> > > This won't be as easy as it was previously because it will trigger
> > > a
> > > transistion (libclamav7 -> libclamav9) in stable similar to what we
> > > did
> > > in unstable (#922004) recently.
> > 
> > upstream released 0.100.3 which fixes three bugs with CVE numbers
> > [0].
> > There is also 0.101.2.
> > 
> > For Stretch we tend to upload 0.100.3 before we get an approval for
> > this
> > one (which would be then 0.101.2). Since the 0.100.3 is smaller, it
> > should be easier/quicker tor review.
> > Is this okay?
> > 
> > [0] https://blog.clamav.net/2019/03/clamav-01012-and-01003-patches-ha
> > ve.html
> 
> Sure. To make things easier to keep track of (at least for me), could
> you open a new bug for the 0.100.3 update, and we'll keep using this
> one for the effective transition.

Filed (#926003).

Scott K

Bug#926003: stretch-pu: package clamav/0.100.3+dfsg-0+deb9u1

[Scott Kitterman]

On Sat, 30 Mar 2019 04:01:40 -0400 Scott Kitterman  
wrote:
> Package: release.debian.org
> Severity: normal
> Tags: stretch
> User: release.debian@packages.debian.org
> Usertags: pu
> 
> Clamav upstream has just done a security release.  They did do a 0.100 
update
> so that we can get the security fixes out in advance of the pending 
libclamav9
> transition (#924278).

Note: Since this is a security via updates update, I went ahead and uploaded 
it because I will be unavailable for almost all of the next 24 hours.

Scott K

Bug#926002: unblock: zeromq3/4.3.1-4

[Laszlo Boszormenyi (GCS)]

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

Hi Release Team,

Unfortunately upstream of zeromq3 broke GSSAPI detection[1] in the
configure phase. It went undetected and now zeromq3 for Buster doesn't
have GSSAPI support and this is a regression since Stretch.

Luca Boccassi who is not just our fellow DD but also upstream fixed it
with a small patch. Full debdiff is attached. Please let it migrate to
Buster and have the same functionality available that's in Stretch.

Thanks for consideration,
Laszlo/GCS
[1] https://bugs.debian.org/925914
diff -Nru zeromq3-4.3.1/debian/changelog zeromq3-4.3.1/debian/changelog
--- zeromq3-4.3.1/debian/changelog	2019-01-26 12:49:45.0 +
+++ zeromq3-4.3.1/debian/changelog	2019-03-28 16:37:09.0 +
@@ -1,3 +1,10 @@
+zeromq3 (4.3.1-4) unstable; urgency=medium
+
+  [ Luca Boccassi  ]
+  * Fix GSSAPI support build (closes: #925914).
+
+ -- Laszlo Boszormenyi (GCS)   Thu, 28 Mar 2019 16:37:09 +
+
 zeromq3 (4.3.1-3) unstable; urgency=medium
 
   [ Luca Boccassi  ]
diff -Nru zeromq3-4.3.1/debian/patches/gssapi_pkgconfig.patch zeromq3-4.3.1/debian/patches/gssapi_pkgconfig.patch
--- zeromq3-4.3.1/debian/patches/gssapi_pkgconfig.patch	1970-01-01 00:00:00.0 +
+++ zeromq3-4.3.1/debian/patches/gssapi_pkgconfig.patch	2019-03-28 16:37:09.0 +
@@ -0,0 +1,30 @@
+Author: Luca Boccassi 
+Description: gssapi pkg-config check in configure.ac does not work
+ correctly enable the definition in platform.hpp so that the
+ gssapi support is actually built in if requested and available.
+Origin: https://github.com/zeromq/libzmq/pull/3361
+--- a/configure.ac
 b/configure.ac
+@@ -472,16 +472,20 @@
+ # conditionally require libgssapi_krb5
+ if test "x$require_libgssapi_krb5_ext" != "xno"; then
+ PKG_CHECK_MODULES([gssapi_krb5], [krb5-gssapi], [
++have_gssapi_library="yes"
+ PKGCFG_NAMES_PRIVATE="$PKGCFG_NAMES_PRIVATE krb5-gssapi"
+ ], [
+ AC_CHECK_HEADERS(gssapi/gssapi_generic.h)
+ AC_SEARCH_LIBS([gss_init_sec_context], [gssapi_krb5 gssapi],
+-AC_DEFINE(HAVE_LIBGSSAPI_KRB5, [1], [Enabled GSSAPI security]),
++have_gssapi_library="yes",
+ AC_MSG_ERROR(libgssapi_krb5 is needed for GSSAPI security))
+ PKGCFG_LIBS_PRIVATE="$PKGCFG_LIBS_PRIVATE -lgssapi_krb5"
+ ])
+ fi
+-AM_CONDITIONAL(BUILD_GSSAPI, test "x$require_libgssapi_krb5_ext" != "xno")
++if test "x$have_gssapi_library" = "xyes"; then
++AC_DEFINE(HAVE_LIBGSSAPI_KRB5, [1], [Enabled GSSAPI security])
++fi
++AM_CONDITIONAL(BUILD_GSSAPI, test "x$have_gssapi_library" = "xyes")
+ 
+ # Select curve encryption library, defaults to tweetnacl
+ # To use libsodium instead, use --with-libsodium (must be installed)
diff -Nru zeromq3-4.3.1/debian/patches/series zeromq3-4.3.1/debian/patches/series
--- zeromq3-4.3.1/debian/patches/series	2019-01-26 12:49:45.0 +
+++ zeromq3-4.3.1/debian/patches/series	2019-03-28 16:37:09.0 +
@@ -3,3 +3,4 @@
 test_hardcoded_ipc_path.patch
 ppc64_atomic_intrinsics.patch
 test_pair_ipc_hurd.patch
+gssapi_pkgconfig.patch

Bug#925591: update for 2.02+dfsg1-16

[Joerg Dorchain]

Hello,

with version 2.02+dfsg1-16, the message got slightly different, but still fails

# grub-install 

Installing for x86_64-efi platform.
File descriptor 3 (pipe:[103358418]) leaked on vgs invocation. Parent PID 
17452: grub-install
File descriptor 3 (pipe:[103358418]) leaked on vgs invocation. Parent PID 
17452: grub-install
grub-install: warning: vars_get_variable: 
open(/sys/firmware/efi/vars/blk0-47c7b225-c42a-11d2-8e57-00a0c969723b/raw_var, 
O_RDONLY) failed: No such file or directory.
grub-install: warning: efi_get_variable: ops->get_variable failed: No such file 
or directory.
grub-install: warning: efi_va_generate_file_device_path_from_esp: could not 
open device for ESP: Bad address.
grub-install: warning: efi_generate_file_device_path_from_esp: could not 
generate File DP from ESP: Bad address.
grub-install: error: failed to register the EFI boot entry: Bad address.
Failed: grub-install --target=x86_64-efi --force-extra-removable 
WARNING: Bootloader is not properly installed, system may not be bootable

# ls -l /sys/firmware/efi/vars/
total 0
drwxr-xr-x 2 root root 0 Mar 27 10:42 
AMITSESetup-c811fa38-42c8-4579-a9bb-60e94eddfb34
drwxr-xr-x 2 root root 0 Mar 27 10:42 
AcpiGlobalVariable-af9ffd67-ec10-488a-9dfc-6cbf5ee22c2e
drwxr-xr-x 2 root root 0 Mar 27 10:42 
AcpiGlobalVariable-c020489e-6db2-4ef2-9aa5-ca06fc11d36a
drwxr-xr-x 2 root root 0 Mar 27 10:42 
AfterReadyToBoot-7b77fb8b-1e0d-4d7e-953f-3980a261e077
drwxr-xr-x 2 root root 0 Mar 27 10:42 
AmiGopPolicySetupData-ec87d643-eba4-4bb5-a1e5-3f3e36b20da9
drwxr-xr-x 2 root root 0 Mar 27 10:42 
BiosEventLog-8be4df61-93ca-11d2-aa0d-00e098032b8c
drwxr-xr-x 2 root root 0 Mar 27 10:42 
BiosShotCute-8be4df61-93ca-11d2-aa0d-00e098032b8c
drwxr-xr-x 2 root root 0 Mar 27 10:42 
Boot0004-8be4df61-93ca-11d2-aa0d-00e098032b8c
drwxr-xr-x 2 root root 0 Mar 27 10:42 
Boot0005-8be4df61-93ca-11d2-aa0d-00e098032b8c
drwxr-xr-x 2 root root 0 Mar 27 10:42 
Boot0006-8be4df61-93ca-11d2-aa0d-00e098032b8c
drwxr-xr-x 2 root root 0 Mar 27 10:42 
Boot0007-8be4df61-93ca-11d2-aa0d-00e098032b8c
drwxr-xr-x 2 root root 0 Mar 27 10:42 
BootCurrent-8be4df61-93ca-11d2-aa0d-00e098032b8c
drwxr-xr-x 2 root root 0 Mar 27 10:42 
BootFromUSB-ec87d643-eba4-4bb5-a1e5-3f3e36b20da9
drwxr-xr-x 2 root root 0 Mar 27 10:42 
BootOrder-8be4df61-93ca-11d2-aa0d-00e098032b8c
drwxr-xr-x 2 root root 0 Mar 27 10:42 
CMOSfailflag-c89dc9c7-5105-472c-a743-b1621e142b41
drwxr-xr-x 2 root root 0 Mar 27 10:42 
CPUS3APICID-1456cc6e-22ac-5289-33ba-2e13bbdabaee
drwxr-xr-x 2 root root 0 Mar 27 10:42 ConIn-8be4df61-93ca-11d2-aa0d-00e098032b8c
drwxr-xr-x 2 root root 0 Mar 27 10:42 
ConInDev-8be4df61-93ca-11d2-aa0d-00e098032b8c
drwxr-xr-x 2 root root 0 Mar 27 10:42 
ConOut-8be4df61-93ca-11d2-aa0d-00e098032b8c
drwxr-xr-x 2 root root 0 Mar 27 10:42 
ConOutDev-8be4df61-93ca-11d2-aa0d-00e098032b8c
drwxr-xr-x 2 root root 0 Mar 27 10:42 
DefaultBootOrder-45cf35f6-0d6e-4d04-856a-0370a5b16f53
drwxr-xr-x 2 root root 0 Mar 27 10:42 
DefaultLegacyDevOrder-3c4ead08-45ae-4315-8d15-a60eaa8caf69
drwxr-xr-x 2 root root 0 Mar 27 10:42 
EPUflag-f61b2305-aac3-4c9d-8f25-3a4313f9cc0e
drwxr-xr-x 2 root root 0 Mar 27 10:42 
ErrOut-8be4df61-93ca-11d2-aa0d-00e098032b8c
drwxr-xr-x 2 root root 0 Mar 27 10:42 
ErrOutDev-8be4df61-93ca-11d2-aa0d-00e098032b8c
drwxr-xr-x 2 root root 0 Mar 27 10:42 
EzFlashBiosFilePath-ec87d643-eba4-4bb5-a1e5-3f3e36b20da9
drwxr-xr-x 2 root root 0 Mar 27 10:42 
FPDT_Variable-01368881-c4ad-4b1d-b631-d57a8ec8db6b
drwxr-xr-x 2 root root 0 Mar 27 10:42 
FTMActiveFlag-8be4df61-93ca-11d2-aa0d-00e098032b8c
drwxr-xr-x 2 root root 0 Mar 27 10:42 
FirstBootFlag-ec87d643-eba4-4bb5-a1e5-3f3e36b20da9
drwxr-xr-x 2 root root 0 Mar 27 10:42 HiiDB-1b838190-4625-4ead-abc9-cd5e6af18fe0
drwxr-xr-x 2 root root 0 Mar 27 10:42 
HiiDataSize-5d6b998a-e304-4088-9087-130c917fb1ae
drwxr-xr-x 2 root root 0 Mar 27 10:42 
HobRomImage-dde1bc72-d45e-4209-ab85-14462d2f5074
drwxr-xr-x 2 root root 0 Mar 27 10:42 
IccAdvancedSetupDataVar-7b77fb8b-1e0d-4d7e-953f-3980a261e077
drwxr-xr-x 2 root root 0 Mar 27 10:42 
IccLockDefault-ec87d643-eba4-4bb5-a1e5-3f3e36b20da9
drwxr-xr-x 2 root root 0 Mar 27 10:42 
IccOcFlag-ec5ff312-bb97-465a-94fd-c84c2cb80e53
drwxr-xr-x 2 root root 0 Mar 27 10:42 
IccRollingFlag-f8dbe9b1-e2ee-42d6-820f-a54b06ebf9d1
drwxr-xr-x 2 root root 0 Mar 27 10:42 
InBiosSetupFlag-ec87d643-eba4-4bb5-a1e5-3f3e36b20da9
drwxr-xr-x 2 root root 0 Mar 27 10:42 KEK-8be4df61-93ca-11d2-aa0d-00e098032b8c
drwxr-xr-x 2 root root 0 Mar 27 10:42 Lang-8be4df61-93ca-11d2-aa0d-00e098032b8c
drwxr-xr-x 2 root root 0 Mar 27 10:42 
LangCodes-8be4df61-93ca-11d2-aa0d-00e098032b8c
drwxr-xr-x 2 root root 0 Mar 27 10:42 
LegacyDevOrder-a56074db-65fe-45f7-bd21-2d2bdd8e9652
drwxr-xr-x 2 root root 0 Mar 27 10:42 
MeEndOfPostFlag-ec87d643-eba4-4bb5-a1e5-3f3e36b20da9
drwxr-xr-x 2 root root 0 Mar 27 10:42 
MemCeil.-40312829-7891-4abd-b200-0c541b061939
drwxr-xr-x 2 root root 0 Mar 27 10:42 
MemoryFreq-58cd8089-e2d9-4b84-88b8-3da497dba390
drwxr-xr-x 2 root root 0 Mar 27 

Bug#926001: pure-ftpd: missing libsodium dependency

[Stéphane Cottin]

Package: pure-ftpd
Version: 1.0.47-3
Severity: normal

Dear Maintainer,

In order to support strong hashes ( scrypt / argin2 ), pure-ftpd has to be 
comiled with libsodium. 
Please add libsodium-dev as a build dependency.

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

Kernel: Linux 4.9.0-8-amd64 (SMP w/1 CPU core)
Locale: LANG=en_US.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: sysvinit (via /sbin/init)

Bug#925971: release-notes: should mention secure boot in d-i

[Steve McIntyre]

On Fri, Mar 29, 2019 at 04:45:20PM +0100, Paul Gevers wrote:
>Package: release-notes
>X-Debbugs-CC: debian-b...@lists.debian.org
>
>As now discussion on the RT sprint, the release notes should probably
>say something about the work on secure boot.
>
>I wouldn't know what to put in, so proposals are welcome. Until that
>time, I file this bug to not forget.

ACK. We'll have some text to add. :-)

-- 
Steve McIntyre, Cambridge, UK.st...@einval.com
"Arguing that you don't care about the right to privacy because you have
 nothing to hide is no different than saying you don't care about free
 speech because you have nothing to say."
   -- Edward Snowden

Bug#925950: patches no longer apply for gcc-8 and gcc-9

[Helmut Grohne]

Control: fixed -1 cross-gcc-dev/230

Hi Dima,

Great to see that you've already taken care. Much appreciated.

On Fri, Mar 29, 2019 at 02:07:11PM -0700, Dima Kogan wrote:
> My key situation should be resolved with the next keyring update, but
> this will take a few weeks probably. If it's useful to you, you should
> push the new package into the archive.

I've worked around this locally now, so there is no urgency from my
side.

However, getting this into buster in a timely manner could be useful.

If your key update takes longer, I can sponsor the upload.

Helmut

Bug#901952: fixing pristine-tar w.r.t. changed tar escaping

[Bernhard R. Link]

I'm looking into #901952 (pristine-tar failing to checkout out old files
with non-printable unicode characters) and think that might be solved
with the attached patches, by calling tar with --null and giving it
a copy of the manifest file that is unescaped and NUL-terminated.

What I haven't looked into yet is whether it will break files
generated with 1.46, as that the format incompatibly without
changing the version of the delta (though perhaps that can be
mitigated by an additional variant at checkout time).

What are your opinions on that? Is this worth trying to get into buster?

Bernhard R. Link
-- 
F8AC 04D5 0B9B 064B 3383  C3DA AFFC 96D1 151D FFDC
>From c26122199aca7c2e08a8597d700d66b8734a3ad6 Mon Sep 17 00:00:00 2001
From: "Bernhard R. Link" 
Date: Fri, 29 Mar 2019 22:32:13 +0100
Subject: [PATCH 1/4] revert writing unquoted filenames to manifest

this caused the filename to be unquoted two times,
break with filenames containing newlines
and changed the semantics of manifest files without changing the format version
---
 pristine-tar | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/pristine-tar b/pristine-tar
index 0fe132e..fe10340 100755
--- a/pristine-tar
+++ b/pristine-tar
@@ -664,7 +664,7 @@ sub genmanifest {
 chomp;
 # ./ or / in the manifest just confuses tar
 s/^\.?\/+//;
-print OUT unquote_filename($_) . "\n" if length $_;
+print OUT $_ . "\n" if length $_;
   }
   close IN;
   close OUT;
-- 
2.20.1

>From 3caa71e47a23eab2b93291960c2e5d54471dd839 Mon Sep 17 00:00:00 2001
From: "Bernhard R. Link" 
Date: Fri, 29 Mar 2019 22:44:25 +0100
Subject: [PATCH 2/4] also unquote octal escape sequences returned by tar

Tar also generates octal escape sequences (\123) for some unicode
characters. Those were not yet unquoted.

This also means when such files exist, there are no longer empty
files with the incorrectly unquoted names created.
This change has no effect compared to pristine-tar <= 1.45
as those created files are then ignored as they do not appear
in the manifest file. Though there is a small chance it might
break deltas created with 1.46 with such fules (assuming those
where even able to be checked in with 1.46).
---
 pristine-tar | 26 ++
 1 file changed, 18 insertions(+), 8 deletions(-)

diff --git a/pristine-tar b/pristine-tar
index fe10340..82256f5 100755
--- a/pristine-tar
+++ b/pristine-tar
@@ -362,15 +362,25 @@ Options:
 sub unquote_filename {
   my $filename = shift;
 
-  $filename =~ s/\\a/\a/g;
-  $filename =~ s/\\b/\b/g;
-  $filename =~ s/\\f/\f/g;
-  $filename =~ s/\\n/\n/g;
-  $filename =~ s/\\r/\r/g;
-  $filename =~ s/\\t/\t/g;
-  $filename =~ s/\\v/\x11/g;
-  $filename =~ s//\\/g;
+  my $unquote_character = sub {
+die "filenames with NUL bytes are not supported" if $2 eq "000";
+return pack("C", oct($2)) if defined $2;
+my %map_named_escapes = (
+a => "\a",
+b => "\b",
+f => "\f",
+n => "\n",
+r => "\r",
+t => "\t",
+v => "\x11",
+"\\" => "\\",
+);
+return $map_named_escapes{$1};
+  };
 
+  # unquote by calling $unquote_character for each matched group:
+  # (do all in a single run, as the octal sequences might output anything)
+  $filename =~ s/\\([abfnrtv\\])|\\([0-7]{3})/$unquote_character->()/ge;
   return $filename;
 }
 
-- 
2.20.1

>From ce7d2f64abf077c5f91119b53d34f0071e49c5e4 Mon Sep 17 00:00:00 2001
From: "Bernhard R. Link" 
Date: Fri, 29 Mar 2019 22:56:52 +0100
Subject: [PATCH 3/4] send manifests file to tar NUL-terminated and unquoted
 (Closes: #901952)

tar changed behavior in no longer unescaping filenames with --verbatim-files-from
breaking reading all delta files and handling files with such filenames.

(This also fixes #902115 properly this time).
---
 pristine-tar | 6 --
 1 file changed, 4 insertions(+), 2 deletions(-)

diff --git a/pristine-tar b/pristine-tar
index 82256f5..f6cea05 100755
--- a/pristine-tar
+++ b/pristine-tar
@@ -394,12 +394,14 @@ sub recreatetarball {
 
   my @manifest;
   open(IN, "<", $manifestfile) || die "$manifestfile: $!";
+  open(OUT, ">", "$tempdir/manifest") || die "$tempdir/manifest: $!";
   while () {
 chomp;
 push @manifest, $_;
+print OUT unquote_filename($_) . pack("C", 0);
   }
   close IN;
-  link($manifestfile, "$tempdir/manifest") || die "link $tempdir/manifest: $!";
+  close OUT;
 
   # The manifest and source should have the same filenames,
   # but the manifest probably has all the files under a common
@@ -526,7 +528,7 @@ sub recreatetarball_helper {
 0,"--numeric-owner",
 "-C", "$tempdir/workdir",
 "--no-recursion", "--mode",
-"0644",   "--verbatim-files-from",
+"0644",   "--null",
 "--files-from",   "$tempdir/manifest"
   );
   if (exists $options{tar_format}) {
-- 
2.20.1

Bug#926004: unblock: kicad/5.1.0+dfsg1-1

[Carsten Schoenert]

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

Please unblock package kicad

The KiCad binary packages based on upstream 5.0.2 (the current version
in testing from December 2018) are build with GTK2+ bindings which has
now some important downsides for the usability of KiCad. The upstream
developers are aware of this and have worked on pushing the KiCad
applications to work and use GTK3+ bindings. They released the new
version 5.1.0 about two weeks ago which addresses also a move over to
provide a Python3 library and dropping the old Python2 library instead.
Furthermore some additional possible UI stuff mainly provided by
external extension, that are based on wxWidgets and wxPython4, aren't
working with the version from testing due the GTK3+ binding in
the wxWidgets libaries.
And as usual a lot of small bug fixes did happen between the two
released versions.

The binary packages from src:kicad have no reverse dependencies nor
providing any public library (besides the Python3 library) so there are
no problems to be expected by the update at least I don't now any of
them.

In the past I've provided snapshots of the ongoing development including
release candidates of 5.1.0 in experimental and based on the feedback
from the KiCad forum and community no big issues nor packaging problem
got reported so I finally uploaded the 5.1.0 release to unstable. Also
here since the upload no new bug reports nor issues in forum got
reported, in contrary people start asking then KiCad 5.1.0 will be
available in testing and finally in the Buster release. :)
In all the reported issues against KiCad are really just a few,
currently we have 5 reports.

The resulting full debdiff between 5.0.2 from testing and 5.1.0 is
rather big due a natural lot of changes within the upstream source.

I uploaded a compressed version of the (full) debdiff to p.d.o.

https://people.debian.org/~tijuca/unblock/kicad-full.debdiff.tar.xz

The probably more interesting things are the differences within the debian
folder. I created a dedicated diff on this that is also available on
p.d.o as I'm not sure it the list will accept the plain file due size
limitations.
https://people.debian.org/~tijuca/unblock/kicad.debian-folder.debdiff

To summarize the Debian specific changes here:

* Adopt the build dependencies so the build is using wxWidgest GTK3+
  based packages.
* Adjust a dedicated (binary) package dependency to use python-wxgtk3.0
  which is linked against wxgtk3.0 with GTK3+ symbols, needed for the
  internal KiCad scripting interface.
* Use Clang instead of GCC as compiler as the required GLM library >=
  0.9.9.3 uses the C++ standard in it's "own" way which Clang is able to
  work with, GCC7 is not.
* The Dutch documentation got dropped as not updated since at least on
  release cycle.
* Upstream is providing a lot more of documentation in 5.1.0 which are
  finally packaged in kicad-doc-{en,it,ru,zh}, no new binary packages.
* As usual a lot of updates to d/copyright due the changes happen to the
  source.
* The build of the documentation of the final 5.1.0 needs a workaround as
  the cmake system otherwise is puzzled and breaks a successful build.
  (Since my package upload the root for this issue got identified and
  will get fixed in future upstream updates.)

unblock kicad/5.1.0+dfsg1-1

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

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

Bug#791522: RFA: alien package maintainer

[Cevat Bostancıoğlu]

Hi,
i don't now where to sent this email but i want to be new maintainer of
alien package.

Cevat

Bug#926011: command-not-found: Unable to open database file (sqlite3)

[J. A. Corbal]

Package: command-not-found
Version: 18.04.5-1
Severity: important
Tags: upstream

###

Distributor ID: Debian
Description:Debian GNU/Linux buster/sid
Release:testing
Codename:   buster
Sorry, command-not-found has crashed! Please file a bug report at:
http://www.debian.org/Bugs/Reporting
Please include the following information with the report:

command-not-found version: 0.3
Python version: 3.7.3 candidate 1
Exception information:

unable to open database file
Traceback (most recent call last):
  File "/usr/share/command-not-found/CommandNotFound/util.py", line 23, in 
crash_guard
callback()
  File "/usr/lib/command-not-found", line 90, in main
cnf = CommandNotFound.CommandNotFound(options.data_dir, do_raise=True)
  File "/usr/share/command-not-found/CommandNotFound/CommandNotFound.py", line 
86, in __init__
self.db = SqliteDatabase(dbpath)
  File "/usr/share/command-not-found/CommandNotFound/db/db.py", line 12, in 
__init__
self.con = sqlite3.connect(filename)
sqlite3.OperationalError: unable to open database file

###

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

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

Versions of packages command-not-found depends on:
ii  apt-file 3.2.2
ii  lsb-release  10.2019031300
ii  python3  3.7.2-1
ii  python3-apt  1.8.4

command-not-found recommends no packages.

Versions of packages command-not-found suggests:
pn  snapd  

-- no debconf information

Bug#926012: linux-image-4.19.0-4-amd64: i915 Resetting chip for hang on rcs0

[Daren]

Package: src:linux
Version: 4.19.28-2
Severity: important

Dear Maintainer,

   * What led up to the situation?
  The installation of stretch and buster causes random screen freezes and 
  "i915 Resetting chip for hang on rcs0" messages in logs.

   * What exactly did you do (or not do) that was effective (or
 ineffective)?
  I have performed new buster, stretch and jessie installs.

   * What was the outcome of this action?
  In buster and jessie X freezes for a few seconds while the gpu resets.
  The jessie installation does not have this problem. 
  On stretch the freezing occurs around once or twice every hour.
  Buster seems better once every few hours.

   * What outcome did you expect instead?
  I hoped no screen freezing would occur in buster.

-- Package-specific info:
** Version:
Linux version 4.19.0-4-amd64 (debian-ker...@lists.debian.org) (gcc version 
8.3.0 (Debian 8.3.0-2)) #1 SMP Debian 4.19.28-2 (2019-03-15)

** Command line:
BOOT_IMAGE=/vmlinuz-4.19.0-4-amd64 root=/dev/mapper/vgBuster-lvBusterRoot ro 
quiet

** Not tainted

** Kernel log:
[5.537960] random: lvm: uninitialized urandom read (2 bytes read)
[5.886831] EXT4-fs (dm-2): mounted filesystem with ordered data mode. Opts: 
(null)
[6.355089] random: crng init done
[7.249027] systemd[1]: Inserted module 'autofs4'
[7.375551] systemd[1]: systemd 241 running in system mode. (+PAM +AUDIT 
+SELINUX +IMA +APPARMOR +SMACK +SYSVINIT +UTMP +LIBCRYPTSETUP +GCRYPT +GNUTLS 
+ACL +XZ +LZ4 +SECCOMP +BLKID +ELFUTILS +KMOD -IDN2 +IDN -PCRE2 
default-hierarchy=hybrid)
[7.394249] systemd[1]: Detected architecture x86-64.
[7.403812] systemd[1]: Set hostname to .
[9.278705] systemd[1]: usr.mount: Unit is bound to inactive unit 
dev-mapper-vgBuster\x2dlvBusterUsr.device. Stopping, too.
[9.297720] systemd[1]: Listening on Syslog Socket.
[9.297911] systemd[1]: Listening on Journal Socket.
[9.299946] systemd[1]: Starting Load Kernel Modules...
[9.300673] systemd[1]: Mounting Kernel Debug File System...
[9.325466] systemd[1]: Starting Restore / save the current clock...
[9.325626] systemd[1]: Listening on LVM2 poll daemon socket.
[9.659456] EXT4-fs (dm-0): re-mounted. Opts: errors=remount-ro
[9.673407] EXT4-fs (dm-2): re-mounted. Opts: (null)
[9.719302] nct6775: Found NCT6776D/F or compatible chip at 0x2e:0x290
[9.719307] ACPI Warning: SystemIO range 
0x0295-0x0296 conflicts with OpRegion 
0x0290-0x0299 (\_GPE.HWRE) (20180810/utaddress-213)
[9.719313] ACPI: If an ACPI driver is available for this device, you should 
use it instead of the native driver
[   11.130182] input: Power Button as 
/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0C:00/input/input2
[   11.130192] ACPI: Power Button [PWRB]
[   11.130236] input: Power Button as 
/devices/LNXSYSTM:00/LNXPWRBN:00/input/input3
[   11.131108] ACPI: Power Button [PWRF]
[   11.174777] input: PC Speaker as /devices/platform/pcspkr/input/input4
[   11.202248] parport_pc 00:02: reported by Plug and Play ACPI
[   11.202312] parport0: PC-style at 0x378, irq 5 [PCSPP]
[   11.597423] iTCO_vendor_support: vendor-support=0
[   11.650003] ppdev: user-space parallel port driver
[   11.725171] RAPL PMU: API unit is 2^-32 Joules, 3 fixed counters, 163840 ms 
ovfl timer
[   11.725172] RAPL PMU: hw unit of domain pp0-core 2^-16 Joules
[   11.725173] RAPL PMU: hw unit of domain package 2^-16 Joules
[   11.725174] RAPL PMU: hw unit of domain pp1-gpu 2^-16 Joules
[   11.736433] iTCO_wdt: Intel TCO WatchDog Timer Driver v1.11
[   11.736471] iTCO_wdt: Found a Cougar Point TCO device (Version=2, 
TCOBASE=0x0460)
[   11.736559] iTCO_wdt: initialized. heartbeat=30 sec (nowayout=0)
[   12.128961] sd 0:0:0:0: Attached scsi generic sg0 type 0
[   12.129020] sr 1:0:0:0: Attached scsi generic sg1 type 5
[   12.129051] sd 3:0:0:0: Attached scsi generic sg2 type 0
[   12.287124] asus_wmi: ASUS WMI generic driver loaded
[   12.342449] asus_wmi: Initialization: 0x0
[   12.342474] asus_wmi: BIOS WMI version: 0.9
[   12.342509] asus_wmi: SFUN value: 0x0
[   12.342809] input: Eee PC WMI hotkeys as 
/devices/platform/eeepc-wmi/input/input5
[   12.343207] asus_wmi: Number of fans: 1
[   13.554351] [drm] Replacing VGA console driver
[   13.555412] Console: switching to colour dummy device 80x25
[   13.556277] [drm] Supports vblank timestamp caching Rev 2 (21.10.2013).
[   13.556278] [drm] Driver supports precise vblank timestamp query.
[   13.557011] i915 :00:02.0: vgaarb: changed VGA decodes: 
olddecodes=io+mem,decodes=io+mem:owns=io+mem
[   13.639764] [drm] Initialized i915 1.6.0 20180719 for :00:02.0 on minor 0
[   13.640261] ACPI: Video Device [GFX0] (multi-head: yes  rom: no  post: no)
[   13.640348] input: Video Bus as 
/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A08:00/LNXVIDEO:00/input/input6
[   13.668482] fbcon: inteldrmfb (fb0) is primary device
[   13.751144] Console: switching to colour 

Bug#926013: command-not-found: Unable to open database file (sqlite3)

[J. A. Corbal]

Package: command-not-found
Version: 18.04.5-1
Severity: important
Tags: upstream

###

Distributor ID: Debian
Description:Debian GNU/Linux buster/sid
Release:testing
Codename:   buster
Sorry, command-not-found has crashed! Please file a bug report at:
http://www.debian.org/Bugs/Reporting
Please include the following information with the report:

command-not-found version: 0.3
Python version: 3.7.3 candidate 1
Exception information:

unable to open database file
Traceback (most recent call last):
  File "/usr/share/command-not-found/CommandNotFound/util.py", line 23, in 
crash_guard
callback()
  File "/usr/lib/command-not-found", line 90, in main
cnf = CommandNotFound.CommandNotFound(options.data_dir, do_raise=True)
  File "/usr/share/command-not-found/CommandNotFound/CommandNotFound.py", line 
86, in __init__
self.db = SqliteDatabase(dbpath)
  File "/usr/share/command-not-found/CommandNotFound/db/db.py", line 12, in 
__init__
self.con = sqlite3.connect(filename)
sqlite3.OperationalError: unable to open database file

###

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

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

Versions of packages command-not-found depends on:
ii  apt-file 3.2.2
ii  lsb-release  10.2019031300
ii  python3  3.7.2-1
ii  python3-apt  1.8.4

command-not-found recommends no packages.

Versions of packages command-not-found suggests:
pn  snapd  

-- no debconf information

Bug#926014: bwa: CVE-2019-10269

[Markus Koschany]

Package: bwa
X-Debbugs-CC: t...@security.debian.org
Severity: important
Tags: security

Hi,

The following vulnerability was published for bwa.

CVE-2019-10269[0]:
| BWA (aka Burrow-Wheeler Aligner) before 2019-01-23 has a stack-based
| buffer overflow in the bns_restore function in bntseq.c via a long
| sequence name in a .alt file.


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

For further information see:

[0] https://security-tracker.debian.org/tracker/CVE-2019-10269
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-10269

Please adjust the affected versions in the BTS as needed. Only Stretch
and later versions are affected.

Regards,

Markus



signature.asc
Description: OpenPGP digital signature

Bug#926015: Merge Ubuntu packaging improvements up to 2.13.2-9ubuntu2+

[intrigeri]

Source: apparmor
Version: 2.13.2-9
Severity: normal

Ubuntu folks have merged 2.13.2-9 and did quite a few packaging
improvements on top. Nothing seems to warrant a freeze exception but
once Buster is out, we should take a closer look at these changes
and merge.

Bug#903894: RM: ibus-qt -- ROM; QT5 support is in different package

[Paul Gevers]

Hi,

Just for the record, today there is only one package depending on it and
that isn't in buster.

Paul

elbrus@respighi:~$ dak rm --no-action -R ibus-qt
Will remove the following packages from unstable:

   ibus-qt |1.3.3-4 | source
  ibus-qt4 |1.3.3-4 | amd64, arm64, armel, armhf, hurd-i386, i386,
kfreebsd-amd64, kfreebsd-i386, mips, mips64el, mipsel, ppc64el, s390x
libibus-qt-dev |1.3.3-4 | amd64, arm64, armel, armhf, hurd-i386,
i386, kfreebsd-amd64, kfreebsd-i386, mips, mips64el, mipsel, ppc64el, s390x
libibus-qt1 |1.3.3-4 | amd64, arm64, armel, armhf, hurd-i386, i386,
kfreebsd-amd64, kfreebsd-i386, mips, mips64el, mipsel, ppc64el, s390x

Maintainer: Debian Input Method Team 

--- Reason ---

--

Checking reverse dependencies...
# Broken Depends:
openteacher: openteacher

Dependency problem found.



signature.asc
Description: OpenPGP digital signature

Bug#917711: Bug triaged and submitted upstream

[Giovanni Mascellani]

user debian-rele...@lists.debian.org

usertags 917711 + bsp-2019-03-fr-paris
forwarded 917711 https://github.com/steveire/grantlee/issues/51
thank you

Dear maintainer,

I triaged and submitted upstream this bug:

  https://github.com/steveire/grantlee/issues/51

The upstream bug contains my current understanding of the bug and asks
for help on how to proceed, because I am not really sure on what is the
best way forward.

I hope this helps fixing the bug!

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



signature.asc
Description: OpenPGP digital signature

Bug#926020: Cannot file removal bug for src:clsparse

[ghisvail]

Package: reportbug
Version: 7.5.2
Severity: normal

Dear maintainer,

I tried to file a removal bug for the src:clsparse package.

Reportbug fails to find the package in the database and eventually
crashes with an IndexError.

Please find the attached output of `reportbug ftp.debian.org`:

```
Choose the request type: 6
Please enter the name of the package (either source of binary package):
> clsparse
Checking status database...
W: Impossible de trouver le paquet clsparse
This package doesn't appear to exist; continue? [y|N|?]? y
Traceback (most recent call last):
  File "/usr/bin/reportbug", line 2285, in 
main()
  File "/usr/bin/reportbug", line 1115, in main
return iface.user_interface()
  File "/usr/bin/reportbug", line 1705, in user_interface
self.options.http_proxy)
  File "/usr/bin/reportbug", line 543, in special_prompts
return pkgprompts(package, bts, ui, fromaddr, timeout, online,
http_proxy)
  File "/usr/lib/python3/dist-packages/reportbug/debbugs.py", line 265,
in handle_debian_ftp
section, priority = info[16], info[10]
IndexError: list index out of range
```

Best regards,
Ghislain


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

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

Versions of packages reportbug depends on:
ii  apt1.8.0
ii  python33.7.2-1
ii  python3-reportbug  7.5.2
ii  sensible-utils 0.0.12

reportbug recommends no packages.

Versions of packages reportbug suggests:
pn  claws-mail 
pn  debconf-utils  
pn  debsums
pn  dlocate
pn  emacs24-bin-common | emacs25-bin-common
ii  exim4-daemon-light [mail-transport-agent]  4.92-2
ii  file   1:5.35-4
ii  gnupg  2.2.12-1
pn  python3-urwid  
pn  reportbug-gtk  
ii  xdg-utils  1.1.3-1

Versions of packages python3-reportbug depends on:
ii  apt1.8.0
ii  file   1:5.35-4
ii  python33.7.2-1
ii  python3-apt1.8.4
ii  python3-debian 0.1.34
ii  python3-debianbts  2.8.2
ii  python3-requests   2.21.0-1

python3-reportbug suggests no packages.

-- no debconf information

Bug#926022: RM: opengm -- ROM; FTBFS

[ghisvail]

Package: ftp.debian.org
Severity: normal
X-Debbugs-CC: debian-scie...@lists.debian.org
Control: affects -1 opengm

Please remove "opengm" from "unstable".

This package fails to build on all release architectures. It
has got no rdpends and should therefore be safe to remove.

Best regards,
Ghislain

Bug#912467: Partial triaging

[Giovanni Mascellani]

user debian-rele...@lists.debian.org

usertags 912467 + bsp-2019-03-fr-paris
thank you

Hi,

I am working on bug #912467. The most evident problem is that the
compiler is not instructed to search for classes in the saaj library,
which is probably due to the fact that the saaj dependency is marked as
"runtime" in the POM. Removing that indication seems to
fix the problem, but exposes a few others:

> [INFO] --- maven-compiler-plugin:3.8.0:compile (default-compile) @ 
> jasperreports ---
> [INFO] Changes detected - recompiling the module!
> [INFO] Compiling 2705 source files to 
> /home2/giovanni2/packages/tmp/jasperreports/build-area/jasperreports-6.3.1/jasperreports/target/classes
> [INFO] 
> /home2/giovanni2/packages/tmp/jasperreports/build-area/jasperreports-6.3.1/jasperreports/src/net/sf/jasperreports/engine/JRRenderable.java:
>  Some input files use or override a deprecated API.
> [INFO] 
> /home2/giovanni2/packages/tmp/jasperreports/build-area/jasperreports-6.3.1/jasperreports/src/net/sf/jasperreports/engine/JRRenderable.java:
>  Recompile with -Xlint:deprecation for details.
> [INFO] 
> /home2/giovanni2/packages/tmp/jasperreports/build-area/jasperreports-6.3.1/jasperreports/src/net/sf/jasperreports/engine/JRAbstractScriptlet.java:
>  Some input files use unchecked or unsafe operations.
> [INFO] 
> /home2/giovanni2/packages/tmp/jasperreports/build-area/jasperreports-6.3.1/jasperreports/src/net/sf/jasperreports/engine/JRAbstractScriptlet.java:
>  Recompile with -Xlint:unchecked for details.
> [INFO] Some messages have been simplified; recompile with -Xdiags:verbose to 
> get full output
> [INFO] -
> [ERROR] COMPILATION ERROR : 
> [INFO] -
> [ERROR] 
> /home2/giovanni2/packages/tmp/jasperreports/build-area/jasperreports-6.3.1/jasperreports/src/net/sf/jasperreports/engine/export/JRXlsMetadataExporter.java:[559,50]
>  incompatible types: int cannot be converted to 
> org.apache.poi.ss.usermodel.CellType
> [ERROR] 
> /home2/giovanni2/packages/tmp/jasperreports/build-area/jasperreports-6.3.1/jasperreports/src/net/sf/jasperreports/engine/export/JRXlsMetadataExporter.java:[584,105]
>  incompatible types: int cannot be converted to 
> org.apache.poi.ss.usermodel.ClientAnchor.AnchorType
> [ERROR] 
> /home2/giovanni2/packages/tmp/jasperreports/build-area/jasperreports-6.3.1/jasperreports/src/net/sf/jasperreports/engine/export/JRXlsMetadataExporter.java:[1169,94]
>  incompatible types: byte cannot be converted to 
> org.apache.poi.ss.usermodel.ClientAnchor.AnchorType
> [ERROR] 
> /home2/giovanni2/packages/tmp/jasperreports/build-area/jasperreports-6.3.1/jasperreports/src/net/sf/jasperreports/engine/export/JRXlsMetadataExporter.java:[1178,131]
>  incompatible types: org.apache.poi.ss.usermodel.ClientAnchor.AnchorType 
> cannot be converted to int
> [ERROR] 
> /home2/giovanni2/packages/tmp/jasperreports/build-area/jasperreports-6.3.1/jasperreports/src/net/sf/jasperreports/engine/export/JRXlsMetadataExporter.java:[2030,51]
>  incompatible types: org.apache.poi.ss.usermodel.BorderStyle cannot be 
> converted to int
> [ERROR] 
> /home2/giovanni2/packages/tmp/jasperreports/build-area/jasperreports-6.3.1/jasperreports/src/net/sf/jasperreports/engine/export/JRXlsMetadataExporter.java:[2032,48]
>  bad operand types for binary operator '+'
>   first type:  int
>   second type: org.apache.poi.ss.usermodel.BorderStyle
> [ERROR] 
> /home2/giovanni2/packages/tmp/jasperreports/build-area/jasperreports-6.3.1/jasperreports/src/net/sf/jasperreports/engine/export/JRXlsMetadataExporter.java:[2034,48]
>  bad operand types for binary operator '+'
>   first type:  int
>   second type: org.apache.poi.ss.usermodel.BorderStyle
> [ERROR] 
> /home2/giovanni2/packages/tmp/jasperreports/build-area/jasperreports-6.3.1/jasperreports/src/net/sf/jasperreports/engine/export/JRXlsMetadataExporter.java:[2036,48]
>  bad operand types for binary operator '+'
>   first type:  int
>   second type: org.apache.poi.ss.usermodel.BorderStyle
> [ERROR] 
> /home2/giovanni2/packages/tmp/jasperreports/build-area/jasperreports-6.3.1/jasperreports/src/net/sf/jasperreports/engine/export/JRXlsMetadataExporter.java:[2119,36]
>  incompatible types: org.apache.poi.ss.usermodel.FillPatternType cannot be 
> converted to int
> [ERROR] 
> /home2/giovanni2/packages/tmp/jasperreports/build-area/jasperreports-6.3.1/jasperreports/src/net/sf/jasperreports/engine/export/JRXlsMetadataExporter.java:[2121,40]
>  bad operand types for binary operator '+'
>   first type:  int
>   second type: org.apache.poi.ss.usermodel.HorizontalAlignment
> [ERROR] 
> /home2/giovanni2/packages/tmp/jasperreports/build-area/jasperreports-6.3.1/jasperreports/src/net/sf/jasperreports/engine/export/JRXlsMetadataExporter.java:[2122,40]
>  bad operand types for binary operator '+'
>   first type:  int
>   second type: org.apache.poi.ss.usermodel.VerticalAlignment
> [ERROR] 
> 

Bug#926024: RM: linop -- ROM; abandonned upstream

[ghisvail]

Package: ftp.debian.org
Severity: normal

Please remove source package linop from unstable.

This library is no longer actively maintained upstream and better
alternatives exist within the Python scientific stack.

This package has got no rdepends and should therefore be safe to
remove.

Best regards,
Ghislain

Bug#926026: RM: shark -- ROM; FTBFS; orphaned

[ghisvail]

Package: ftp.debian.org
Severity: normal
X-Debbugs-CC: debian-scie...@lists.debian.org
Control: affects -1 shark

Please remove source package shark from unstable.

This package fails to build on major release architectures and is no
longer actively maintained by myself. It has got no rdpends and should
therefore be safe to remove.

Best regards,
Ghislain

Bug#925899: lxc: Unprivileged containers fail to start after recent updates

[Pierre-Elliott Bécue]

Le 30 mars 2019 15:29:52 GMT+01:00, intrigeri  a écrit :
>Hi,
>
>Pierre-Elliott Bécue:
>> This bugreport raises an interesting question regarding the tradeoff
>> between the solution we implemented to fix bug #916639.
>
>> Cc-ing intrigeri: I'm reconsidering the /etc/lxc/default.conf setting
>> regarding apparmor.profile. Putting generated breaks many unpriv
>> containers as they have no apparmor.profile set in their
>configuration.
>
>I'd love to help but I'll need more info to understand why the current
>setup breaks "many unpriv containers", e.g.:
>
> - Is this specific to unprivileged containers?
>
> - Is it because "apparmor.profile = generated" is not suitable
>   for unprivileged containers?
>
>Finally, I wonder if "Suggests: apparmor" expresses strongly enough
>the current status of the LXC + AppArmor integration in Debian.
>Thankfully the Linux images will pull apparmor via Recommends…
>except on systems where the administrator has disabled installation
>of Recommends.
>
>Cheers,

It is specific to unpriviledged containers and due to the fact that non root 
users don't seem to have the ability to use the generated profile. 
PEB (from my phone)

Bug#926007: unblock: kicad-symbols/5.1.0-1

[Carsten Schoenert]

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

Please unblock package kicad-symbols

The kicad-symbols package provides additional data for schematic symbols
for the kicad application. The schematic symbols data are simple text
files and by this the package is platform independent.
Even if the update of the kicad package (see #926004) isn't going to be
accepted kicad-symbols should make it's way into Buster finally.

A full debdiff is big due the updates to the upstream text files. Due
it's size I've uploaded the full debdiff to p.d.o.
https://people.debian.org/~tijuca/unblock/kicad-symbols-full.debdiff.tar.xz

The modification of the debian folder between the version in testing and
unstable is on contray really small.

diff -puNr -puNr kicad-symbols-5.0.2/debian/changelog 
kicad-symbols-5.1.0/debian/changelog
--- kicad-symbols-5.0.2/debian/changelog2018-12-04 21:07:58.0 
+0100
+++ kicad-symbols-5.1.0/debian/changelog2019-03-11 20:26:47.0 
+0100
@@ -1,3 +1,12 @@
+kicad-symbols (5.1.0-1) unstable; urgency=medium
+
+  * [e0c482d] New upstream version 5.1.0
+  * [ffcb043] d/control: increase Standards-Version to 4.3.0
++ No further changes needed.
+  * [591c592] d/copyright: update years on contributors
+
+ -- Carsten Schoenert   Mon, 11 Mar 2019 20:26:47 
+0100
+
 kicad-symbols (5.0.2-1) unstable; urgency=medium
 
   * [97acd5a] New upstream version 5.0.2
diff -puNr -puNr kicad-symbols-5.0.2/debian/control 
kicad-symbols-5.1.0/debian/control
--- kicad-symbols-5.0.2/debian/control  2018-08-31 22:04:13.0 +0200
+++ kicad-symbols-5.1.0/debian/control  2019-03-11 20:26:41.0 +0100
@@ -10,7 +10,7 @@ Build-Depends:
  cmake,
 Vcs-Git: https://salsa.debian.org/electronics-team/KiCad/kicad-symbols.git
 Vcs-Browser: https://salsa.debian.org/electronics-team/KiCad/kicad-symbols
-Standards-Version: 4.2.1
+Standards-Version: 4.3.0
 Homepage: https://kicad.github.io/symbols
 
 Package: kicad-symbols
diff -puNr -puNr kicad-symbols-5.0.2/debian/copyright 
kicad-symbols-5.1.0/debian/copyright
--- kicad-symbols-5.0.2/debian/copyright2018-08-31 22:04:17.0 
+0200
+++ kicad-symbols-5.1.0/debian/copyright2019-03-11 20:26:41.0 
+0100
@@ -10,11 +10,11 @@ Comment: Like all KiCad libraries the li
  Material'."
 
 Files: *
-Copyright: 2018 KiCad Community
+Copyright: 2019 KiCad Community
 License: CC-BY-SA-4.0-with-exception
 
 Files: debian/*
-Copyright: 2018, Carsten Schoenert 
+Copyright: 2019, Carsten Schoenert 
2017-2018, Jean-Samuel Reynaud 
 License: GPL-2+

unblock kicad-symbols/5.1.0-1

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

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

Bug#874364: Current status

[Iiro Laiho]

Hi,

The GDM part  is now fixed.

I have also noticed that at least on Debian Stretch and Buster, there 
seems to be a some kind of delay for the keyboard layout to be applied 
to the virtual console. A reboot seems to trigger it, at least 
sometimes. When it is actually supposed to happen?


-- Iiro Laiho

Bug#923184: unblock: qgis/3.4.6+dfsg-1

[Sebastiaan Couwenberg]

Control: retitle -1 unblock: qgis/3.4.6+dfsg-1

On 3/17/19 11:43 PM, Sebastiaan Couwenberg wrote:
> On 3/17/19 8:17 PM, Sebastiaan Couwenberg wrote:
>> On 2/24/19 9:23 PM, Bas Couwenberg wrote:
>>> Because the 2.18 LTR is EOL with the release of QGIS 3.4.5 having the
>>> latter in buster is probably better than leaving the qgis package at the
>>> last 2.18.x release (2.18.28).
>>>
>>> QGIS 3.4 is the new LTR and switches to Qt5 and Python 3, as such
>>> the changes since the version in testing are quite large and cannot be
>>> considered "small, targeted fixes".
>>>
>>> While users of the qgis package are unlikely to use the version of the
>>> package available in stable, and more likely using the latest LTR from
>>> backports, I think having 3.4.5 in buster is better for users upgrading
>>> from stretch than leaving them with the EOL 2.18.28 release until the
>>> package is updated in buster-backports.
>>>
>>> Would you approve of moving QGIS 3.4.5 from experimental to unstable and
>>> allowing it to migrate to tesing for inclusion in buster?
>>>
>>> Or should we keep it experimental until after the release, and make the
>>> newer LTRs available in buster-backports when it hits testing?
>>
>> As reported by Lucas Nussbaum in #924833, qgis (2.18.28-2) FTBFS in
>> unstable due to sip4 (4.19.14+dfsg-1) which was uploaded a couple of
>> weeks after qgis.
>>
>> With 2.18.x being EOL upstream, we cannot rely on upstream to provide a
>> fix, and I lack the skills for it.
>>
>> I'm going to move QGIS 3.4 to unstable so that we at least have a
>> version of QGIS in unstable that supports SIP 4.19.14.
>>
>> If the changes in QGIS 3.4 are deemed to invasive for an unblock, we'll
>> have to release buster without qgis and deal with lots of unhappy users.

qgis (3.4.6+dfsg-1) has been uploaded to unstable. Please unblock it, to
fix the FTBFS issue (#924833) in testing.

The debdiff is 477M (60M gzipped), so not attached.

unblock qgis/3.4.6+dfsg-1

Kind Regards,

Bas

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

Bug#882090: [Pkg-javascript-devel] node-yamljs updated

[Xavier]

Le 30/03/2019 à 12:39, Xavier a écrit :
> Hello,
> 
> I updated node-yamljs, please check my changes to see if all is OK and
> ready to push.
> 
> Following our policy, source package should be renamed yamljs.js
> (provides node-yamljs and libjs-yamljs).
> 
> Cheers,
> Xavier
> 
> https://salsa.debian.org/js-team/node-yamljs

Renamed to https://salsa.debian.org/js-team/yamljs.js

Bug#926020: Cannot file removal bug for src:clsparse

[Sandro Tosi]

> ```
> Choose the request type: 6
> Please enter the name of the package (either source of binary package):
> > clsparse
> Checking status database...
> W: Impossible de trouver le paquet clsparse

> This package doesn't appear to exist; continue? [y|N|?]? y
> Traceback (most recent call last):
>   File "/usr/bin/reportbug", line 2285, in 
> main()
>   File "/usr/bin/reportbug", line 1115, in main
> return iface.user_interface()
>   File "/usr/bin/reportbug", line 1705, in user_interface
> self.options.http_proxy)
>   File "/usr/bin/reportbug", line 543, in special_prompts
> return pkgprompts(package, bts, ui, fromaddr, timeout, online,
> http_proxy)
>   File "/usr/lib/python3/dist-packages/reportbug/debbugs.py", line 265,
> in handle_debian_ftp
> section, priority = info[16], info[10]
> IndexError: list index out of range
> ```

this is gonna be fix as part of #923631

> Best regards,
> Ghislain
>
>
> -- System Information:
> Debian Release: buster/sid
>   APT prefers testing
>   APT policy: (500, 'testing')

and this is the reason you cant find it: that pkg is not in testing

-- 
Sandro "morph" Tosi
My website: http://sandrotosi.me/
Me at Debian: http://wiki.debian.org/SandroTosi
G+: https://plus.google.com/u/0/+SandroTosi

Bug#925919: RFT: linux with fix for VMware regression

[Emanuel Kocher]

On 30/03/2019 05:15, Ben Hutchings wrote:
> I've uploaded a new version of linux to:
> https://people.debian.org/~benh/packages/jessie-security/
> which I believe will fix this regression (bug #925919).  Please let me
> know whether it works for you.
I just installed it on two machines which hung quite often but 
everything looks stable for now - would prefer to give them until monday 
though when the normal workload is back to see how they behave.
> I only included the amd64 linux-image package and sources there, but
> can add i386 linux-image packages if needed.
>
> Ben.
>
Cheers
Emanuel

Bug#926031: unblock: chromium/73.0.3683.75-1

[Michael Gilbert]

package: release.debian.org
user: release.debian@packages.debian.org
usertags: unblock

Please consider unblocking chromium.  This is a large upstream release
with a bunch of security fixes.  As has been done for the past few
stable releases, the plan is to push ongoing upstream security updates
to buster(-security).

Best wishes,
Mike

unblock chromium/73.0.3683.75-1

Bug#926006: unblock: kicad-packages3d/5.1.0-1

[Carsten Schoenert]

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

Please unblock package kicad-packages3d

The kicad-packages3d package provides additional data of 3D-models for
the kicad application. The 3D-models data are simple text files and by
this the package is platform independent.
Even if the update of the kicad package (see #926004) isn't going to be
accepted kicad-packages3d should make it's way into Buster finally.

A full debdiff is big due the updates to the upstream text files. Due
it's size I've uploaded the full debdiff to p.d.o.
https://people.debian.org/~tijuca/unblock/kicad-packages3d-full.debdiff.tar.xz

A diff for the debian folder between the version in testing and unstable
is about 95% changes to the debian/copyright file and the helper files
of cme around this.
The remaining about 5% is on updating the Standards-Versions and the new
debian/changelog entry as no other modifications to the packaging was
required.

diff -puNr -puNr kicad-packages3d-5.0.2/debian/changelog 
kicad-packages3d-5.1.0/debian/changelog
--- kicad-packages3d-5.0.2/debian/changelog 2018-12-06 16:47:58.0 
+0100
+++ kicad-packages3d-5.1.0/debian/changelog 2019-03-15 20:15:27.0 
+0100
@@ -1,3 +1,14 @@
+kicad-packages3d (5.1.0-1) unstable; urgency=medium
+
+  * [674fff9] New upstream version 5.1.0
+  * [387d52f] d/control: increase Standards-Version to 4.3.0
++ No further changes needed.
+  * [90c3af4] copyright: add some additional information for cme script
++ Add some helping content into debian/fill.copyright.blanks.yml.
+  * [581a7ec] copyright: update information due release of 5.1.0
+
+ -- Carsten Schoenert   Fri, 15 Mar 2019 20:15:27 
+0100
+
 kicad-packages3d (5.0.2-1) unstable; urgency=medium
 
   * [aeb1d03] New upstream version 5.0.2
diff -puNr -puNr kicad-packages3d-5.0.2/debian/control 
kicad-packages3d-5.1.0/debian/control
--- kicad-packages3d-5.0.2/debian/control   2018-08-31 21:43:47.0 
+0200
+++ kicad-packages3d-5.1.0/debian/control   2019-03-15 00:26:53.0 
+0100
@@ -10,7 +10,7 @@ Build-Depends:
  cmake,
 Vcs-Git: https://salsa.debian.org/electronics-team/KiCad/kicad-packages3d.git
 Vcs-Browser: https://salsa.debian.org/electronics-team/KiCad/kicad-packages3d
-Standards-Version: 4.2.1
+Standards-Version: 4.3.0
 Homepage: https://kicad.github.io/packages3d
 
 Package: kicad-packages3d
diff -puNr -puNr kicad-packages3d-5.0.2/debian/copyright 
kicad-packages3d-5.1.0/debian/copyright
--- kicad-packages3d-5.0.2/debian/copyright 2018-08-31 21:44:08.0 
+0200
+++ kicad-packages3d-5.1.0/debian/copyright 2019-03-15 20:09:48.0 
+0100
@@ -10,10 +10,17 @@ Comment: Like all KiCad libraries the li
  Material'."
 
 Files: *
-Copyright: 2018, KiCad Community
+Copyright: 2018, 2019, KiCad Community
 License: CC-BY-SA-4.0-with-exception
 [snip]
 [a lot of other modifications to d/copyright]

The full diff for the debian folder I've uploaded again to p.d.o.
https://people.debian.org/~tijuca/unblock/kicad-packages3d.debian-folder.debdiff

unblock kicad-packages3d/5.1.0-1

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

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

Bug#926008: unblock: kicad-templates/5.1.0-1

[Carsten Schoenert]

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

Please unblock package kicad-templates

The kicad-templates package provides additional data for prepared
electronics schematic and PCB data for the kicad application. The data
of the templates are simple text files and by this the package is
platform independent.
Even if the update of the kicad package (see #926004) isn't going to be
accepted kicad-templates should make it's way into Buster finally.

The update within the upstream version is small and really clear. But
also the Debian packaging got just one small update on the
Standards-Version and the updated copyright file.

diff -Nru kicad-templates-5.0.2/debian/changelog 
kicad-templates-5.1.0/debian/changelog
--- kicad-templates-5.0.2/debian/changelog  2018-12-04 21:13:06.0 
+0100
+++ kicad-templates-5.1.0/debian/changelog  2019-03-11 20:37:17.0 
+0100
@@ -1,3 +1,12 @@
+kicad-templates (5.1.0-1) unstable; urgency=medium
+
+  * [db07e5c] New upstream version 5.1.0
+  * [98163f0] d/control: increase Standards-Version to 4.3.0
++ No further changes needed.
+  * [a21730b] d/copyright: update years on contributors
+
+ -- Carsten Schoenert   Mon, 11 Mar 2019 20:37:17 
+0100
+
 kicad-templates (5.0.2-1) unstable; urgency=medium
 
   * [7b1e635] New upstream version 5.0.2
diff -Nru kicad-templates-5.0.2/debian/control 
kicad-templates-5.1.0/debian/control
--- kicad-templates-5.0.2/debian/control2018-08-31 22:12:24.0 
+0200
+++ kicad-templates-5.1.0/debian/control2019-03-11 20:36:08.0 
+0100
@@ -10,7 +10,7 @@
  cmake,
 Vcs-Git: https://salsa.debian.org/electronics-team/KiCad/kicad-templates.git
 Vcs-Browser: https://salsa.debian.org/electronics-team/KiCad/kicad-templates
-Standards-Version: 4.2.1
+Standards-Version: 4.3.0
 Homepage: https://github.com/KiCad/kicad-templates
 
 Package: kicad-templates
diff -Nru kicad-templates-5.0.2/debian/copyright 
kicad-templates-5.1.0/debian/copyright
--- kicad-templates-5.0.2/debian/copyright  2018-08-31 22:12:45.0 
+0200
+++ kicad-templates-5.1.0/debian/copyright  2019-03-11 20:36:51.0 
+0100
@@ -10,11 +10,11 @@
  Material'."
 
 Files: *
-Copyright: 2018 KiCad Community
+Copyright: 2019 KiCad Community
 License: CC-BY-SA-4.0-with-exception
 
 Files: debian/*
-Copyright: 2018, Carsten Schoenert 
+Copyright: 2019, Carsten Schoenert 
2017-2018, Jean-Samuel Reynaud 
 License: GPL-2+
 
diff -Nru kicad-templates-5.0.2/raspberrypi_hat/raspberrypi_hat.kicad_pcb 
kicad-templates-5.1.0/raspberrypi_hat/raspberrypi_hat.kicad_pcb
--- kicad-templates-5.0.2/raspberrypi_hat/raspberrypi_hat.kicad_pcb 
2018-11-15 18:38:06.0 +0100
+++ kicad-templates-5.1.0/raspberrypi_hat/raspberrypi_hat.kicad_pcb 
2019-02-06 20:45:57.0 +0100
@@ -435,7 +435,7 @@
   (net 10 "Net-(J9-Pad2)"))
 (pad 8 smd rect (at 2.7 -1.905 180) (size 1.55 0.6) (layers F.Cu F.Paste 
F.Mask)
   (net 8 /P3V3))
-(model ${KISYS3DMOD}/Package_SOIC.3dshapes/SOIC-8_3.9x4.9mm_P1.27mm.wrl
+(model ${KISYS3DMOD}/Package_SO.3dshapes/SOIC-8_3.9x4.9mm_P1.27mm.wrl
   (at (xyz 0 0 0))
   (scale (xyz 1 1 1))
   (rotate (xyz 0 0 0))

unblock kicad-templates/5.1.0-1

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

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

Bug#926009: openjdk-11 breaks libreoffice autopkgtests

[Paul Gevers]

Source: openjdk-11, libreoffice
Control: found -1 openjdk-11/11.0.3+4-3
Control: found -1 libreoffice/1:6.1.5-1
Severity: important
X-Debbugs-CC: debian...@lists.debian.org
User: debian...@lists.debian.org
Usertags: breaks needs-update

Dear maintainers,

With a recent upload of openjdk-11 the autopkgtest of libreoffice fails
in testing when that autopkgtest is run with the binary packages of
openjdk-11 from unstable. It passes when run with only packages from
testing. In tabular form:
   passfail
openjdk-11 from testing11.0.3+4-3
libreofficefrom testing1:6.1.5-1
all others from testingfrom testing

I copied some of the output at the bottom of this report.

Currently this regression is blocking the migration of openjdk-11 to
testing [1]. Due to the nature of this issue, I filed this bug report
against both packages. Can you please investigate the situation and
reassign the bug to the right package? If needed, please change the
bug's severity.

More information about this bug and the reason for filing it can be found on
https://wiki.debian.org/ContinuousIntegration/RegressionEmailInformation

Paul

[1] https://qa.debian.org/excuses.php?package=openjdk-11

https://ci.debian.net/data/autopkgtest/testing/amd64/libr/libreoffice/2172984/log.gz

== Add the extension ==
javaldx: Could not find a Java Runtime Environment!
Please ensure that a JVM and the package libreoffice-java-common
is installed.
If it is already installed then try removing
~/.libreoffice/3/user/config/javasettings_Linux_*.xml
Synchronizing repository for shared extensions



 Synchronizing repository for bundled extensions



javaldx: Could not find a Java Runtime Environment!
Please ensure that a JVM and the package libreoffice-java-common
is installed.
If it is already installed then try removing
~/.libreoffice/3/user/config/javasettings_Linux_*.xml

ERROR: An error occurred while enabling: TestExtension.jar
   Cause:
(com.sun.star.registry.CannotRegisterImplementationException) { {
Message = "Could not create Java implementation loader", Context =
(com.sun.star.uno.XInterface) @0 } }

unopkg failed.



signature.asc
Description: OpenPGP digital signature

Bug#925618: Working on it

[Sébastien Villemot]

user debian-rele...@lists.debian.org
usertags -1 + bsp-2019-03-fr-paris
thank you

-- 
⢀⣴⠾⠻⢶⣦⠀  Sébastien Villemot
⣾⠁⢠⠒⠀⣿⡁  Debian Developer
⢿⡄⠘⠷⠚⠋⠀  http://seb
astien.villemot.name
⠈⠳⣄  http://www.debian.org


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

Bug#905268: at-spi2-core: key repeat causes a blocked system

[Julien Cristau]

Control: tag -1 moreinfo
Control: severity -1 important

On Thu, Aug  2, 2018 at 14:39:07 +0200, Michael Becker wrote:

> Hi Samuel,
> 
> thanks for the fast response.
> Unfortunately this problem does not occur regularly but only occasionally.
> But if it happens, it happens for roughly half an hour.
> Will checks the Xorg logs as soon as it happens again.
> Currently I don't see anything conspicuous, but it's difficult to relate 
> var/log/messages and var/log/Xorg.0.log
> 
Downgrading severity since this doesn't seem to have been widely
reported and we don't have enough to go on.

Cheers,
Julien

Bug#925979: busybox-udeb: breaks user-params, rescue mode, etc.

[Chris Boot]

Hi KiBi,

On 29/03/2019 17:45, Cyril Brulebois wrote:
[snip]
> But in practice, that means that rescue/enable=true is no longer visible
> from the rescue-check binary package (from src:rescue), meaning a broken
> rescue mode. I expect a number of other features to be broken in the
> same way, via the user-params script in debian-installer-utils.

Ugh. Not again.

[snip]> I'd be happy to have a fix for this before we consider releasing D-I
> Buster RC 1, which could otherwise be ready next week. If maintainers
> could hint me into the right direction, that could be sufficient. ;)

Given the time constraints for buster I think your approach to reverting
upstream's changes and re-applying our hack is probably the right way to
go. I'll try to put something together today for review and, hopefully,
so that you can test with if you don't mind.

I've also had a thought, and I can't remember if we've considered it
already: do the environment variables get preserved in /proc/1/environ,
even if busybox ash can't grok them? Could d-i be modified to pull them
from there?

Cheers,
Chris

-- 
Chris Boot
bo...@debian.org

Bug#920209: [debian-mysql] Bug#920209: Suggested fix

[Giovanni Mascellani]

Hi,

Il 23/01/19 15:57, Otto Kekäläinen ha scritto:
> If you want, you can submit the patch above as a Merge Request on
> Salsa and thus ensure there are no obvious visible regressions related
> to it:
> https://wiki.debian.org/Teams/MySQL/patches

This has been marked pending for two months now. Is it possible to
upload the fix so that we can progress towards the release?

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



signature.asc
Description: OpenPGP digital signature

Bug#892812: [libdrm-radeon1] Periodic UI freezes

[Julien Cristau]

Control: severity -1 important

Hi,

On Tue, Mar 13, 2018 at 11:02:18 +0100, Julien Vion wrote:

> Package: libdrm-radeon1
> Version: 2.4.90
> Severity: serious
> 
> --- Please enter the report below this line. ---
> 
> I have been experiencing periodic general UI freezes since last reboot.
>  UI (Gnome) freezes for 1 second or two every 30 seconds. This is
> extremely annoying and makes UI almost unusable. 
> Probably due to recent package upgrade, probably libdrm-radeon.
> 
> htop displays a load average of ~2.0, but I no process uses more than
> 5% CPU. I rather suspect GPU driver issue.
> 
if this is still an issue with up to date software, please provide full
kernel and X logs along with output of glxinfo.

Thanks,
Julien

Bug#884033: scilab segfaults building scilab-{ann,celestlab,plotlib}

[Sébastien Villemot]

As agreed with jcristau at Paris BSP, the plan is to remove scilab-
celestlab from buster (the other two, scilab-{ann,plotlib}, are not in
buster either), and then to tag this bug as buster-ignore.

-- 
⢀⣴⠾⠻⢶⣦⠀  Sébastien Villemot
⣾⠁⢠⠒⠀⣿⡁  Debian Developer
⢿⡄⠘⠷⠚⠋⠀  http://seb
astien.villemot.name
⠈⠳⣄  http://www.debian.org


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

Bug#925899: lxc: Unprivileged containers fail to start after recent updates

[intrigeri]

Hi,

Pierre-Elliott Bécue:
> This bugreport raises an interesting question regarding the tradeoff
> between the solution we implemented to fix bug #916639.

> Cc-ing intrigeri: I'm reconsidering the /etc/lxc/default.conf setting
> regarding apparmor.profile. Putting generated breaks many unpriv
> containers as they have no apparmor.profile set in their configuration.

I'd love to help but I'll need more info to understand why the current
setup breaks "many unpriv containers", e.g.:

 - Is this specific to unprivileged containers?

 - Is it because "apparmor.profile = generated" is not suitable
   for unprivileged containers?

Finally, I wonder if "Suggests: apparmor" expresses strongly enough
the current status of the LXC + AppArmor integration in Debian.
Thankfully the Linux images will pull apparmor via Recommends…
except on systems where the administrator has disabled installation
of Recommends.

Cheers,
-- 
intrigeri

Bug#926023: ITP: golang-github-jsimonetti-pwscheme -- Golang packages defining different password schemes

[Balasankar C]

Package: wnpp
Severity: wishlist
Owner: Balasankar C 

* Package name: golang-github-jsimonetti-pwscheme
  Version : 0.0~git20160922.7680470-1
  Upstream Author : Jeroen Simonetti
* URL : https://github.com/jsimonetti/pwscheme
* License : MIT (Expat)
  Programming Lang: Go
  Description : Golang packages defining different password schemes


This Golang package provides different password schemes, like Salted
SHA1, Salted SHA256, Crypt with MD5, etc.

Packaging as a dependency of gopasspw[0][1]


[0] https://github.com/gopasspw/gopass/
[1] https://bugs.debian.org/901133

Regards
Balasankar "Balu" C

Bug#926027: RM: xtensor -- ROM; NPOASR; FTBFS; orphaned

[ghisvail]

Package: ftp.debian.org
Severity: normal
X-Debbugs-CC: debian-scie...@lists.debian.org
Control: affects -1 xtensor

Please remove source package xtensor from unstable.

This package currently FTBFS, is severely outdated and is no longer
actively maintained by myself.

Best regards,
Ghislain

Bug#926029: RM: python-pydap -- ROM; FTBFS; orphaned

[ghisvail]

Package: ftp.debian.org
Severity: normal
X-Debbugs-CC: debian-scie...@lists.debian.org
Control: affects -1 python-pydap

Please remove source package python-pydap from unstable.

This package fails to build with recent releases of Python and NumPy
(two RC bugs) and is no longer actively maintained by myself.

Best regards,
Ghislain

Bug#926010: unblock: jcodings/1.0.43-1

[Hideki Yamane]

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

Please unblock package jcodings

jruby-joni 2.1.26 package depends on jcondings and its upstream pom.xml
speficies to use 1.0.43 (so I've updated it with 2.1.26-2
https://tracker.debian.org/news/1035918/accepted-jruby-joni-2126-2-source-into-unstable/
(maybe it's better to introduce jruby-joni 2.1.26-2 if it's okay).

debdiff is here.

diff -Nru jcodings-1.0.42/debian/changelog jcodings-1.0.43/debian/changelog
--- jcodings-1.0.42/debian/changelog2019-01-02 12:45:13.0 +0900
+++ jcodings-1.0.43/debian/changelog2019-03-09 19:07:35.0 +0900
@@ -1,3 +1,9 @@
+jcodings (1.0.43-1) unstable; urgency=medium
+
+  * New upstream release
+
+ -- Hideki Yamane   Sat, 09 Mar 2019 19:07:35 +0900
+
 jcodings (1.0.42-1) unstable; urgency=medium
 
   * New upstream release
diff -Nru jcodings-1.0.42/debian/patches/remove_unnecessary_dependency.patch 
jcodings-1.0.43/debian/patches/remove_unnecessary_dependency.patch
--- jcodings-1.0.42/debian/patches/remove_unnecessary_dependency.patch  
2019-01-02 12:45:13.0 +0900
+++ jcodings-1.0.43/debian/patches/remove_unnecessary_dependency.patch  
2019-03-09 19:07:35.0 +0900
@@ -6,7 +6,7 @@
 --- a/pom.xml
 +++ b/pom.xml
 @@ -6,11 +6,6 @@
-   1.0.42
+   1.0.43
JCodings
Byte based encoding support library for java
 -  
diff -Nru jcodings-1.0.42/pom.xml jcodings-1.0.43/pom.xml
--- jcodings-1.0.42/pom.xml 2018-12-28 06:09:47.0 +0900
+++ jcodings-1.0.43/pom.xml 2019-03-07 02:15:23.0 +0900
@@ -3,7 +3,7 @@
   4.0.0
   org.jruby.jcodings
   jcodings
-  1.0.42
+  1.0.43
   JCodings
   Byte based encoding support library for java
   
Binary files /tmp/uSPXIb6K1r/jcodings-1.0.42/resources/tables/CR_Adlam.bin and 
/tmp/CFVYbctSCt/jcodings-1.0.43/resources/tables/CR_Adlam.bin differ
Binary files /tmp/uSPXIb6K1r/jcodings-1.0.42/resources/tables/CR_Age_12_0.bin 
and /tmp/CFVYbctSCt/jcodings-1.0.43/resources/tables/CR_Age_12_0.bin differ
Binary files /tmp/uSPXIb6K1r/jcodings-1.0.42/resources/tables/CR_Alnum.bin and 
/tmp/CFVYbctSCt/jcodings-1.0.43/resources/tables/CR_Alnum.bin differ
Binary files /tmp/uSPXIb6K1r/jcodings-1.0.42/resources/tables/CR_Alpha.bin and 
/tmp/CFVYbctSCt/jcodings-1.0.43/resources/tables/CR_Alpha.bin differ
Binary files /tmp/uSPXIb6K1r/jcodings-1.0.42/resources/tables/CR_Assigned.bin 
and /tmp/CFVYbctSCt/jcodings-1.0.43/resources/tables/CR_Assigned.bin differ
Binary files /tmp/uSPXIb6K1r/jcodings-1.0.42/resources/tables/CR_C.bin and 
/tmp/CFVYbctSCt/jcodings-1.0.43/resources/tables/CR_C.bin differ
Binary files 
/tmp/uSPXIb6K1r/jcodings-1.0.42/resources/tables/CR_Case_Ignorable.bin and 
/tmp/CFVYbctSCt/jcodings-1.0.43/resources/tables/CR_Case_Ignorable.bin differ
Binary files /tmp/uSPXIb6K1r/jcodings-1.0.42/resources/tables/CR_Cased.bin and 
/tmp/CFVYbctSCt/jcodings-1.0.43/resources/tables/CR_Cased.bin differ
Binary files /tmp/uSPXIb6K1r/jcodings-1.0.42/resources/tables/CR_Cf.bin and 
/tmp/CFVYbctSCt/jcodings-1.0.43/resources/tables/CR_Cf.bin differ
Binary files 
/tmp/uSPXIb6K1r/jcodings-1.0.42/resources/tables/CR_Changes_When_Casefolded.bin 
and 
/tmp/CFVYbctSCt/jcodings-1.0.43/resources/tables/CR_Changes_When_Casefolded.bin 
differ
Binary files 
/tmp/uSPXIb6K1r/jcodings-1.0.42/resources/tables/CR_Changes_When_Casemapped.bin 
and 
/tmp/CFVYbctSCt/jcodings-1.0.43/resources/tables/CR_Changes_When_Casemapped.bin 
differ
Binary files 
/tmp/uSPXIb6K1r/jcodings-1.0.42/resources/tables/CR_Changes_When_Lowercased.bin 
and 
/tmp/CFVYbctSCt/jcodings-1.0.43/resources/tables/CR_Changes_When_Lowercased.bin 
differ
Binary files 
/tmp/uSPXIb6K1r/jcodings-1.0.42/resources/tables/CR_Changes_When_Titlecased.bin 
and 
/tmp/CFVYbctSCt/jcodings-1.0.43/resources/tables/CR_Changes_When_Titlecased.bin 
differ
Binary files 
/tmp/uSPXIb6K1r/jcodings-1.0.42/resources/tables/CR_Changes_When_Uppercased.bin 
and 
/tmp/CFVYbctSCt/jcodings-1.0.43/resources/tables/CR_Changes_When_Uppercased.bin 
differ
Binary files /tmp/uSPXIb6K1r/jcodings-1.0.42/resources/tables/CR_Cn.bin and 
/tmp/CFVYbctSCt/jcodings-1.0.43/resources/tables/CR_Cn.bin differ
Binary files /tmp/uSPXIb6K1r/jcodings-1.0.42/resources/tables/CR_Common.bin and 
/tmp/CFVYbctSCt/jcodings-1.0.43/resources/tables/CR_Common.bin differ
Binary files /tmp/uSPXIb6K1r/jcodings-1.0.42/resources/tables/CR_Devanagari.bin 
and /tmp/CFVYbctSCt/jcodings-1.0.43/resources/tables/CR_Devanagari.bin differ
Binary files /tmp/uSPXIb6K1r/jcodings-1.0.42/resources/tables/CR_Diacritic.bin 
and /tmp/CFVYbctSCt/jcodings-1.0.43/resources/tables/CR_Diacritic.bin differ
Binary files /tmp/uSPXIb6K1r/jcodings-1.0.42/resources/tables/CR_Digit.bin and 
/tmp/CFVYbctSCt/jcodings-1.0.43/resources/tables/CR_Digit.bin differ
Binary files 
/tmp/uSPXIb6K1r/jcodings-1.0.42/resources/tables/CR_Egyptian_Hieroglyphs.bin 
and 
/tmp/CFVYbctSCt/jcodings-1.0.43/resources/tables/CR_Egyptian_Hieroglyphs.bin 
differ
Binary 

Bug#925957: fstransform: Reproducible filesystem corruption (data loss)

[Giovanni Mascellani]

Hi,

Il 29/03/19 11:12, Alexander E. Patrakov ha scritto:
> Dear Maintainer,
> 
> approximately 1.5 years ago I have discovered a reproducible case
> of filesystem corruption by fstransform, and reported it upstream:
> 
> https://github.com/cosmos72/fstransform/issues/13
> 
> I understand that the reproducer is with non-default options,
> but it may also apply with the default options to systems with
> huge storage and relatively small amount of RAM.

Thanks for reporting this bug. I can reproduce it, but given that the
upstream issue has been open for more than a year I doubt it will be
solved soon. I agree that having a silent failure with data corruption
is not nice towards the user, but given that fstransform displays
prominent warnings about the fact that it can easily screw up data, I
think it is not a ground for removing the package altogether. The
package can still be helpful to the users, as long as the users are
aware of the risks connected with it.

So what I would rather do is to modify the starting up message so that
the user is aware that running fstransform in low resources environments
can lead to data corruption. Of course, if the user goes to plumbing
level and manually changes internal options, then risks for breakages is
really to be expected.

Of course a proper fix for the bug would be better, but in the meantime
I think this is enough to fix this RC bug and keep fstransform in the
release without putting to much risk on the users.

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



signature.asc
Description: OpenPGP digital signature

Bug#866898: xorg: switching to a VT (with Ctrl-Alt-Fx) hangs entire system

[Julien Cristau]

Control: reassign -1 gnome-shell
Control: severity -1 important

On Sun, Jul  2, 2017 at 17:03:46 +0100, Matthew Vernon wrote:

> Package: xorg
> Version: 1:7.7+19
> Severity: serious
> 
> Hi,
> 
> Since upgrading to stretch, I can no longer switch to a VT - if I do
> Ctrl-Alt-F1 the mouse pointer briefly changes back to that of gdm3 (I
> think), then the entire machine locks up solid - unresponsive to ping
> or anything, and I have to power-cycle it.
> 
> The only thing I see in the log at about the relevant time is:
> 
> Jul  1 23:25:54 aragorn kernel: [  164.494985] gnome-session-f[4309]: 
> segfault at 0 ip b71c492d sp bf8128c4 error 4 in 
> libgtk-3.so.0.2200.11[b6ee7000+803000]
> Jul  1 23:25:54 aragorn kernel: [  164.497200] gnome-session-f[4318]: 
> segfault at 0 ip b721a92d sp bfafd844 error 4 in 
> libgtk-3.so.0.2200.11[b6f3d000+803000]
> 
> ...and, when it happened again:
> 
> Jul  1 23:57:54 aragorn kernel: [  444.296161] traps: gnome-shell[4178] trap 
> int3 ip:b62e8e40 sp:bfb24fb0 error:0
> Jul  1 23:57:54 aragorn kernel: [  444.296168]  in 
> libglib-2.0.so.0.5000.3[b629c000+12a000]
> 
> For me, at least, this is entirely reproducible, and makes it
> impossible for me to use my virtual consoles any more (which I use,
> e.g. for root sessions) :(
> 
Reassigning to gnome-shell since that's what seems to be crashing.  And
downgrading since this doesn't seem to be such a common issue.

If this is still happening it might be useful to gather a core dump.

> The manual x.org.conf is carried from previous releases - I still have
> a CRT, so need to tell Xorg about the monitor.
> 
Unless the monitor is 30 years old that shouldn't be necessary.  EDID
dates back to the mid-1990s.

Cheers,
Julien

Bug#919395: Heads up to release team about MariadB 10.3

[Ivo De Decker]

Hi,

On 3/23/19 2:26 AM, Andreas Beckmann wrote:

On 2019-03-20 12:28, Emilio Pozuelo Monfort wrote:

On 20/03/2019 00:49, Andreas Beckmann wrote:

please give-back qt4-x11. A build has succeeded today in my pbuilder sid



Scheduled.


That worked. What needs to be done to make the three late binNMUs
migrate to testing? Does not seem to happen on its own ...


BinNMUs and new binaries also need an unblock during the freeze (this 
was a fairy recent change in britney), so they didn't migrate on their 
own. I unblocked them and they migrated.


Ivo

Bug#892812: Fwd: Libdrm-radeon1 bug

[Julien Cristau]

Hi Andrew,

On Sat, Mar  9, 2019 at 15:24:52 +, Andrew M.A. Cater wrote:

> Julien,
> 
you didn't actually send your message to the bug submitter.  You may
want to double check recipients of such messages :)

Cheers,
(another) Julien

Bug#921555: Forwarded upstream

[ghisvail]

control: forwarded -1 
https://github.com/Washington-University/CiftiLib/issues/19

Meanwhile, I'll ask for removal of the package on the failing architectures to 
facilitate the transition of the new version for Buster.

Ghis

Bug#925327: gpsd: CVE-2018-17937

[Markus Koschany]

Hi,

On Sat, 30 Mar 2019 08:32:34 +0100 Salvatore Bonaccorso
 wrote:
> Hi Bernd,
> 
> On Fri, Mar 29, 2019 at 10:54:50PM +0100, Bernd Zeimetz wrote:
> > Hi Salvatore,
> > 
> > > The following vulnerability was published for gpsd, not competely sure
> > > on severity and on if the referenced upstream commit is enough.
> > > Ideally though the fix seems ideal to go to buster.
> > 
> > I've tried to get more information out of Upstream, but did not get a
> > reply yet. So I'll prepare an upload with the mentioned commit. Looking
> > trough the commit logs from gpsd it seems to be the only relevant one.
> 
> Ack thank you for investigating, I was neither more successfull to
> determine if that's enough.
> 
> Cc;ing the security team alias, if anyone has more ideas.

I think I would also backport

http://git.savannah.nongnu.org/cgit/gpsd.git/commit/json.c?id=9b3724cb7bca7a0776bcb9b054cd1d8d736278a4

and

http://git.savannah.nongnu.org/cgit/gpsd.git/commit/json.c?id=317375877576b10fd5312a7b0dec4a192881eead

for good measure.

But I agree that the essential fix seems to be

http://git.savannah.nongnu.org/cgit/gpsd.git/commit/?id=7646cbd04055a50b157312ba6b376e88bd398c19

Regards,

Markus



signature.asc
Description: OpenPGP digital signature

Bug#925383: Processed: Re: Bug#925383: unblock: shorewall/5.2.3.2-1

[Roberto C . Sánchez]

On Sun, Mar 24, 2019 at 06:51:04PM +, Debian Bug Tracking System wrote:
> Processing commands for cont...@bugs.debian.org:
> 
> > tags 925383 - moreinfo
> Bug #925383 [release.debian.org] unblock: shorewall/5.2.3.2-1
> Removed tag(s) moreinfo.
> > thanks
> Stopping processing here.
> 
Hi Jonathan,

I removed the moreinfo tag nearly a week ago.  Did I misunderstand what
else I needed to do?  Did I need to go ahead and upload as well?  I was
waiting for a pre-approval, but if uploading now makes more sense and
saves you work (since you could review and then unblock the waiting
package), I can upload right away.

Regards,

-Roberto

-- 
Roberto C. Sánchez

Bug#925919: RFT: linux with fix for VMware regression

[Luca Olivetti]

El 30/3/19 a les 5:15, Ben Hutchings ha escrit:

I've uploaded a new version of linux to:
https://people.debian.org/~benh/packages/jessie-security/
which I believe will fix this regression (bug #925919).  Please let me
know whether it works for you.

I only included the amd64 linux-image package and sources there, but
can add i386 linux-image packages if needed.


I just booted with this kernel and the rsync that triggered the problem 
doesn't cause any problem now.
I cannot confirm it's really working until Monday though, when the 
server will see some real load.


Bye
--
Luca Olivetti
Wetron Automation Technology http://www.wetron.es/
Tel. +34 93 5883004 (Ext.3010)  Fax +34 93 5883007

Bug#915620: RM: openjdk-8 binaries on armel mips mipsel mips64el

[Paul Gevers]

On Sat, 23 Mar 2019 07:29:02 +0100 Paul Gevers 
wrote:> DAK believes the issues are solved.

I was also wrong. Asking DAK more politely it complained a bit. ikvm and
dogtag-pki are not in buster.

Paul

elbrus@respighi:~$ dak rm --no-action -R openjdk-8
Will remove the following packages from unstable:

 openjdk-8 | 8u141-b15-3 | source
 openjdk-8 | 8u144-b01-2 | source
 openjdk-8 | 8u212-b01-1 | source
openjdk-8-dbg | 8u141-b15-3 | kfreebsd-i386
openjdk-8-dbg | 8u144-b01-2 | kfreebsd-amd64
openjdk-8-dbg | 8u212-b01-1 | amd64, arm64, armel, armhf, i386, mips,
mips64el, mipsel, ppc64el, s390x
openjdk-8-demo | 8u141-b15-3 | kfreebsd-i386
openjdk-8-demo | 8u144-b01-2 | kfreebsd-amd64
openjdk-8-demo | 8u212-b01-1 | amd64, arm64, armel, armhf, i386, mips,
mips64el, mipsel, ppc64el, s390x
openjdk-8-doc | 8u141-b15-3 | all
openjdk-8-doc | 8u144-b01-2 | all
openjdk-8-doc | 8u212-b01-1 | all
openjdk-8-jdk | 8u141-b15-3 | kfreebsd-i386
openjdk-8-jdk | 8u144-b01-2 | kfreebsd-amd64
openjdk-8-jdk | 8u212-b01-1 | amd64, arm64, armel, armhf, i386, mips,
mips64el, mipsel, ppc64el, s390x
openjdk-8-jdk-headless | 8u141-b15-3 | kfreebsd-i386
openjdk-8-jdk-headless | 8u144-b01-2 | kfreebsd-amd64
openjdk-8-jdk-headless | 8u212-b01-1 | amd64, arm64, armel, armhf, i386,
mips, mips64el, mipsel, ppc64el, s390x
openjdk-8-jre | 8u141-b15-3 | kfreebsd-i386
openjdk-8-jre | 8u144-b01-2 | kfreebsd-amd64
openjdk-8-jre | 8u212-b01-1 | amd64, arm64, armel, armhf, i386, mips,
mips64el, mipsel, ppc64el, s390x
openjdk-8-jre-headless | 8u141-b15-3 | kfreebsd-i386
openjdk-8-jre-headless | 8u144-b01-2 | kfreebsd-amd64
openjdk-8-jre-headless | 8u212-b01-1 | amd64, arm64, armel, armhf, i386,
mips, mips64el, mipsel, ppc64el, s390x
openjdk-8-jre-zero | 8u141-b15-3 | kfreebsd-i386
openjdk-8-jre-zero | 8u144-b01-2 | kfreebsd-amd64
openjdk-8-jre-zero | 8u212-b01-1 | amd64, arm64, armhf, i386, ppc64el
openjdk-8-source | 8u141-b15-3 | all
openjdk-8-source | 8u144-b01-2 | all
openjdk-8-source | 8u212-b01-1 | all

Maintainer: OpenJDK Team 

--- Reason ---

--

Checking reverse dependencies...
# Broken Depends:
dogtag-pki: pki-base-java
java-common: default-jdk [kfreebsd-amd64 kfreebsd-i386]
 default-jdk-doc [kfreebsd-amd64 kfreebsd-i386]
 default-jdk-headless [kfreebsd-amd64 kfreebsd-i386]
 default-jre [kfreebsd-amd64 kfreebsd-i386]
 default-jre-headless [kfreebsd-amd64 kfreebsd-i386]
uwsgi: uwsgi-plugin-jvm-openjdk-8 [kfreebsd-amd64 kfreebsd-i386]
   uwsgi-plugin-jwsgi-openjdk-8 [kfreebsd-amd64 kfreebsd-i386]
   uwsgi-plugin-ring-openjdk-8 [kfreebsd-amd64 kfreebsd-i386]
   uwsgi-plugin-servlet-openjdk-8 [kfreebsd-amd64 kfreebsd-i386]

# Broken Build-Depends:
ikvm: openjdk-8-jdk

Dependency problem found.



signature.asc
Description: OpenPGP digital signature

Bug#926018: [pre-approval] unblock: uim/1:1.8.8-4

[dai]

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

This is a pre-approval for unblocking uim/1:1.8.8-4.

Please unblock package uim.

When upgrading from stretch to buster, input methods setting is broke
due to dropping uim-{byeoru,ipa-x-sampa,latin,look,m17nlib,pinyin,viqr}
packages previously.

So this uploading ressurects their packages for normally upgrading.

diff -Nru uim-1.8.8/debian/NEWS uim-1.8.8/debian/NEWS
--- uim-1.8.8/debian/NEWS   2017-10-01 11:24:34.0 +0900
+++ uim-1.8.8/debian/NEWS   2019-03-27 23:08:38.0 +0900
@@ -1,15 +1,5 @@
 uim (1:1.8.6+gh20161003.0.d63dadd-5) unstable; urgency=medium
 
-  automatically register/unregister input methods:
-
-  - byeoru : byeoru hangul input method
-  - ipa-x-sampa: X-SAMPA IPA input method
-  - latin  : Latin script input method
-  - look   : dictionary-based completion input method
-  - m17nlib: m17nlib multilingual input method
-  - pinyin : pinyin input method
-  - viqr   : Vietnamese Quoted-Readable input method
-
   drop applet packages.
 
   - uim-applet-gnome
diff -Nru uim-1.8.8/debian/changelog uim-1.8.8/debian/changelog
--- uim-1.8.8/debian/changelog  2018-08-03 21:26:06.0 +0900
+++ uim-1.8.8/debian/changelog  2019-03-28 09:31:18.0 +0900
@@ -1,3 +1,23 @@
+uim (1:1.8.8-4) unstable; urgency=medium
+
+  [ YOSHINO Yoshihito ]
+  * Non-maintainer upload.
+  * d/{uim.{postinst,prerm},NEWS}: Do not auto-register/unregister plugins of
+the following input methods:
+byeoru, ipa-x-sampa, latin, look, m17nlib, pinyin, viqr
+When upgrading from stretch this behaved badly and they took precedence
+over other popular plugins many people use.
+  * d/{control,rules,uim-*.{postinst,prerm}}: Resurrect packages
+uim-{byeoru,ipa-x-sampa,latin,look,m17nlib,pinyin,viqr} for those plugins.
+All of them exist in stretch and should upgrade normally.
+Dear testing/sid users,
+If you are using some of the input methods above, you have to manually
+install the respective package(s). Sorry for any inconvenience.
+  * d/{uim.preinst,control}: Unregister those plugins on upgrade from
+testing/sid. Make uim Pre-Depends: uim-data accordingly.
+
+ -- HIGUCHI Daisuke (VDR dai)   Thu, 28 Mar 2019 09:31:18 
+0900
+
 uim (1:1.8.8-3) unstable; urgency=medium
 
   [ HIGUCHI Daisuke (VDR dai) ]
diff -Nru uim-1.8.8/debian/control uim-1.8.8/debian/control
--- uim-1.8.8/debian/control2018-08-03 18:40:41.0 +0900
+++ uim-1.8.8/debian/control2019-03-27 23:08:38.0 +0900
@@ -40,9 +40,9 @@
 Architecture: any
 Multi-Arch: foreign
 Depends: ${misc:Depends}, ${shlibs:Depends},
-   uim-data (>= ${source:Version}),
uim-plugins (>= ${source:Version})
-Pre-Depends: dpkg (>= 1.15.7.2)
+Pre-Depends: dpkg (>= 1.15.7.2),
+   uim-data (>= ${source:Version})
 Breaks: uim-common (<< 1:1.8.6+gh20161003.0.d63dadd-5~),
libuim-data (<< 1:1.8.6+gh20161003.0.d63dadd-5~),
uim-utils (<< 1:1.8.6+gh20161003.0.d63dadd-5~),
@@ -92,9 +92,23 @@
 Architecture: all
 Breaks: libuim-data (<< 1:1.8.6+gh20161003.0.d63dadd-5~),
uim-anthy (<< 1:1.8.6+gh20161003.0.d63dadd-5~),
+   uim-m17nlib (<< 1:1.8.6+gh20161003.0.d63dadd-5~),
+   uim-byeoru (<< 1:1.8.6+gh20161003.0.d63dadd-5~),
+   uim-latin (<< 1:1.8.6+gh20161003.0.d63dadd-5~),
+   uim-pinyin (<< 1:1.8.6+gh20161003.0.d63dadd-5~),
+   uim-viqr (<< 1:1.8.6+gh20161003.0.d63dadd-5~),
+   uim-ipa-x-sampa (<< 1:1.8.6+gh20161003.0.d63dadd-5~),
+   uim-look (<< 1:1.8.6+gh20161003.0.d63dadd-5~),
uim-common (<< 1:1.8.6+gh20161003.0.d63dadd-5~)
 Replaces: libuim-data (<< 1:1.8.6+gh20161003.0.d63dadd-5~),
uim-anthy (<< 1:1.8.6+gh20161003.0.d63dadd-5~),
+   uim-m17nlib (<< 1:1.8.6+gh20161003.0.d63dadd-5~),
+   uim-byeoru (<< 1:1.8.6+gh20161003.0.d63dadd-5~),
+   uim-latin (<< 1:1.8.6+gh20161003.0.d63dadd-5~),
+   uim-pinyin (<< 1:1.8.6+gh20161003.0.d63dadd-5~),
+   uim-viqr (<< 1:1.8.6+gh20161003.0.d63dadd-5~),
+   uim-ipa-x-sampa (<< 1:1.8.6+gh20161003.0.d63dadd-5~),
+   uim-look (<< 1:1.8.6+gh20161003.0.d63dadd-5~),
uim-common (<< 1:1.8.6+gh20161003.0.d63dadd-5~)
 Depends: m17n-db,
${misc:Depends}
@@ -344,6 +358,23 @@
  This package contains a plugin for uim to support the use of the Japanese
  input method SKK.
 
+Package: uim-m17nlib
+Section: utils
+Architecture: all
+Depends: ${misc:Depends},
+   uim (>= ${source:Version}),
+   uim-data (>= ${source:Version})
+Multi-Arch: foreign
+Description: Universal Input Method - m17nlib plugin metapackage
+ Uim is an input method module library which supports various scripts and can
+ act as a front end for a range of input methods, including Anthy, Canna,
+ or SKK (for Japanese), Pinyin (for Chinese), Byeoru (for Korean), and
+ M17n (for many other languages). Most of its functions are implemented in
+ Scheme, so it's very 

Bug#926019: RM: clsparse -- ROM; dead upstream

[ghisvail]

Package: ftp.debian.org
Severity: normal
X-Debbugs-CC: debian-scie...@lists.debian.org
Control: affects -1 clsparse

Please remove "clsparse" from "unstable".

This package is dead upstream and currently affected by two RC bugs. It
has got no rdpends and should be safe to remove.

Best regards,
Ghislain

Bug#925919: RFT: linux with fix for VMware regression

[Bernhard Schmidt]

Am 30.03.19 um 05:15 schrieb Ben Hutchings:

Hi Ben,

> I've uploaded a new version of linux to:
> https://people.debian.org/~benh/packages/jessie-security/
> which I believe will fix this regression (bug #925919).  Please let me
> know whether it works for you.

Had been hit by the crash before, works fine on one of the previously
affected machines under load.

Bernhard

Bug#921460: Pending removal

[ghisvail]

control: tags -1 + pending

Removal bug filed, see #926019.

Bug#926021: unblock: lam/7.1.4-6

[Camm Maguire]

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

Please unblock package lam

This package represents a minimal change to restore alternative
compatibility with the other mpi implementations in Debian (see #924452,
#922633).  It will also remove FTBFS issues for existing netpipe and
xmpi packages in testing.  In all, three AUTORM issues will be resolved.

Take care,

=
source debdiff
=
diff -Nru lam-7.1.4/debian/changelog lam-7.1.4/debian/changelog
--- lam-7.1.4/debian/changelog  2014-03-15 02:47:33.0 +
+++ lam-7.1.4/debian/changelog  2019-03-29 17:36:04.0 +
@@ -1,4 +1,39 @@
-lam (7.1.4-3.1) unstable; urgency=medium
+lam (7.1.4-6) unstable; urgency=medium
+
+  * Minimal RC fix for testing migration
+
+ -- Camm Maguire   Fri, 29 Mar 2019 17:36:04 +
+
+lam (7.1.4-5) unstable; urgency=medium
+
+  * fix /usr/lib/lam/lib/* links in lam4-dev
+
+ -- Camm Maguire   Mon, 25 Mar 2019 02:24:32 +
+
+lam (7.1.4-4) unstable; urgency=high
+
+  * Accept non-maintaner upload.  Thanks Eric Dorland 
+  * priority optional, thanks Andreas Beckmann 
+  * debhelper compat level 9
+  * remove obsolete conflicts/replace, thanks Andreas Beckmann 

+  * remove mpi virtual package, thanks Andreas Beckmann 
+  * add breaks against old style alternatives, thanks Andreas Beckmann
+  
+  * multiarch for liblam4, thanks Andreas Beckmann 
+  * multiarch support in lam4-dev.{prerm,postinst}.in and rules, thanks Andreas
+  Beckmann , (Closes: #924452, #922633)
+  * remove old mpi alternative when appropriate in lam4-dev.preinst, thanks
+  Andreas Beckmann 
+  * remove obsolete ldconfig call in liblam4.postinst, thanks Andreas Beckmann
+  
+  * thanks to Aron Xu.  (Closes: #721437)
+  * standard debian build flags
+  * lintian cleanups
+  * latest standards
+
+ -- Camm Maguire   Thu, 21 Mar 2019 21:53:46 +
+
+am (7.1.4-3.1) unstable; urgency=medium
 
   * Non-maintainer upload.
   * Drop unnecessary autoconf and automake1.9 build deps. (Closes:
diff -Nru lam-7.1.4/debian/control lam-7.1.4/debian/control
--- lam-7.1.4/debian/control2014-03-15 02:45:39.0 +
+++ lam-7.1.4/debian/control2019-03-29 17:36:04.0 +
@@ -34,11 +34,13 @@
 Package: liblam4
 Section: libs
 Architecture: any
+Multi-Arch: same
 Depends: ${shlibs:Depends},${misc:Depends}
 Provides: mpi
 Conflicts: lam,lam1,lam4,lam4c2
 Replaces: lam,lam1,lam4,lam4c2
 Recommends: lam-runtime
+Breaks: libopenmpi-dev (<< 3.0.1~rc1-2), openmpi-bin (<< 3.0.1~rc1-2), mpich 
(<< 3.3~a3-2), libmpich-dev (<< 3.3~a3-2)
 Description: Shared libraries used by LAM parallel programs
  LAM (Local Area Multicomputer) is an open source implementation of the
  Message Passing Interface (MPI) standard.
diff -Nru lam-7.1.4/debian/lam4-dev.postinst lam-7.1.4/debian/lam4-dev.postinst
--- lam-7.1.4/debian/lam4-dev.postinst  2012-04-05 20:07:37.0 +
+++ lam-7.1.4/debian/lam4-dev.postinst  1970-01-01 00:00:00.0 +
@@ -1,27 +0,0 @@
-#!/bin/sh
-
-set -e 
-
-update-alternatives --install /usr/include/mpi mpi /usr/include/lam 30 \
---slave /usr/lib/libmpi.so libmpi.so /usr/lib/liblam.so \
---slave /usr/lib/libmpio.so libmpio.so /usr/lib/liblamio.so \
---slave /usr/lib/libmpi++.so libmpi++.so /usr/lib/liblam++.so \
---slave /usr/lib/libmpi.a libmpi.a /usr/lib/liblam.a \
---slave /usr/lib/libmpio.a libmpio.a /usr/lib/liblamio.a \
---slave /usr/lib/libmpi++.a libmpi++.a /usr/lib/liblam++.a \
---slave /usr/bin/mpicc mpicc /usr/bin/mpicc.lam \
---slave /usr/share/man/man1/mpicc.1.gz mpicc.1.gz 
/usr/share/man/man1/mpicc.lam.1.gz \
---slave /usr/bin/mpif77 mpif77 /usr/bin/mpif77.lam \
---slave /usr/share/man/man1/mpif77.1.gz mpif77.1.gz 
/usr/share/man/man1/mpif77.lam.1.gz \
---slave /usr/bin/mpiCC mpiCC /usr/bin/mpic++.lam \
---slave /usr/share/man/man1/mpiCC.1.gz mpiCC.1.gz 
/usr/share/man/man1/mpiCC.lam.1.gz \
---slave /usr/bin/mpic++ mpic++ /usr/bin/mpic++.lam \
---slave /usr/share/man/man1/mpic++.1.gz mpic++.1.gz 
/usr/share/man/man1/mpic++.lam.1.gz
-
-update-alternatives \
---install /usr/share/man/man3/MPI_Comm_set_name.3.gz 
MPI_Comm_set_name.3.gz /usr/share/man/man3/MPI_Comm_set_name_lam4-dev.3.gz 10
-
-
-#DEBHELPER#
-
-exit 0
diff -Nru lam-7.1.4/debian/lam4-dev.postinst.in 
lam-7.1.4/debian/lam4-dev.postinst.in
--- lam-7.1.4/debian/lam4-dev.postinst.in   1970-01-01 00:00:00.0 
+
+++ lam-7.1.4/debian/lam4-dev.postinst.in   2019-03-29 17:30:31.0 
+
@@ -0,0 +1,31 @@
+#!/bin/sh
+
+set -e 
+
+if [ "$1" = "configure" ]; then
+
+update-alternatives \
+   --install /usr/include/@DEB_HOST_MULTIARCH@/mpi 
mpi-@DEB_HOST_MULTIARCH@/usr/include/lam30 \
+   --slave 

Bug#926028: RM: xtensor-python -- ROM; NPOASR; orphaned

[ghisvail]

Package: ftp.debian.org
Severity: normal
X-Debbugs-CC: debian-scie...@lists.debian.org
Control: affects -1 xtensor-python

Please remove source package xtensor-python from unstable.

This package is severely outdated and is no longer actively maintained
by myself (same situation as xtensor).

Best regards,
Ghislain

Bug#916654: Acknowledgement (vdr-plugin-epgsearch 2.2.0+git20170817-2)

[Stephan Jänecke]

Greetings,

a thread[1] in the german VDR Portal suggests that the segfault occurs
when the conflict check in epgsearch detects timer conflicts.

It has been fixed in yavdr and a patch[2] has been commited to the
official repository.

I can confirm that rebuilding the package with the dsc file[3] from the
yavdr project resolves the problem documented in [1]. So does the bug
reporter[4].

Best regards,

Stephan Jänecke

[1] 
https://www.vdr-portal.de/forum/index.php?thread/132324-gel%C3%B6st-epgsearch-segfault-seit-dem-gestrigen-debian-testing-update/
[2] 
https://projects.vdr-developer.org/git/vdr-plugin-epgsearch.git/commit/?id=49ba796fe6298abf0ebba68a25ddfc92d3d70aad
[3] 
https://launchpad.net/~yavdr/+archive/ubuntu/experimental-vdr/+sourcefiles/vdr-plugin-epgsearch/2.4.0+git20190116-1-49ba796-0yavdr0~bionic/vdr-plugin-epgsearch_2.4.0+git20190116-1-49ba796-0yavdr0~bionic.dsc
[4] 
https://www.vdr-portal.de/forum/index.php?thread/132324-gel%C3%B6st-epgsearch-segfault-seit-dem-gestrigen-debian-testing-update/=1311826#post1311826


signature.asc
Description: PGP signature

Bug#837764: python-pip: Using `--extra-index-url` results in `HTTPError: 404 Client Error: NOT FOUND`

[Thomas Goirand]

The fix is available from here:

https://github.com/pypa/pip/pull/6367/commits/f8292a304deebcf0e4cda2e40caa226c70030f11

Dear maintainer, do you mind if I push this to unstable right away, in
the hope that the fix reaches Buster before the release?

Cheers,

Thomas Goirand (zigo)

Bug#922378: live-boot: Libreoffice doesn't start from a live environment. Signal 11

[intrigeri]

Control: reassign -1 apparmor
Control: severity -1 serious
Control: retitle -1 AppArmor policy breaks confined software when running under 
live-boot + overlayfs
Control: found -1 2.13.2-9

Hi,

Cesar Etxeberria:
> Everything works perfectly but libreoffice doesn't start (signal
> 11).

I can reproduce this with LibreOffice and Evince.

The root cause of the problem is that the storage stack set up by
live-boot with overlayfs is not supported by our AppArmor policy at
the moment.

Fixing the root cause of this problem:

 - will require quite some work; I've started working on this some
   time ago and will definitely finish it at some point for several
   reasons, including the fact that Tails needs this to be fixed;

 - is too involved to happen in time for Buster.

So my plan for Buster is to disable apparmor.service when running
under live-boot + overlayfs, just like Ubuntu already does in their
live images for the exact same reason. This will prevent loading
policy at boot time, which will avoid such breakage, except for
packages that load policy themselves; thankfully, the nature of these
packages (libvirt, LXC) makes it so they have little chance to be used
in a Live environment, so I think that'll be good enough; and if it's
not good enough, worst case we can patch the Live builds configuration
to disable the AppArmor LSM entirely, by passing apparmor=0 on the
kernel command line.

Cheers,
-- 
intrigeri

Bug#886321: (no subject)

[Martin Großhauser]

> Package: ipset
> Version: 6.30-2
> Severity: normal
> 
> Dear Maintainer,
> 
> When adding an entry to an ipset, if you do not specify a full dotted quad,
> what gets added is not what you might reasonably expect
> 
> For example, if you were to type:
> 
> ipset add FOO 192.168/16
> 
> where FOO is the name of an existing inet family hash:ip set what it adds
> is 192.0.0.0/16 - as though treating the 168 as 0.0.168, perhaps.

192.168/16 is indeed interpreted as 192.0.0.168/16. This is done
intentionally by inet_aton(), which allows IP addresses in the formats
'a.b.c.', 'a.b.c', 'a.b' and 'a' [1].

An *expired* IETF draft [2] mentions that behaviour as "non-standard"
but "very popular" and "a de facto standard for the textual
representation of IPv4 addresses". [2]

According to Wikipedia "No formal specification of this textual IP
address representation exists." [3]

So I would say it's a feature, not a bug, and there's nothing wrong here.

[1] https://linux.die.net/man/3/inet_aton
[2] https://tools.ietf.org/html/draft-main-ipaddr-text-rep-02
[3] https://en.wikipedia.org/wiki/Dot-decimal_notation

Bug#925275: 32bit lxc guest on 64bit host has issues on one server but not on the other with identical setup

[Pierre-Elliott Bécue]

Le vendredi 22 mars 2019 à 03:38:18-0400, RA a écrit :
> Package: lxc
> Version: 1:2.0.7-2+deb9u2
> 
> Hi.
> 
> I deployed minimal setup of latest Debian 9 (Stretch) 64-bit via netinst iso 
> on two KVM servers from different providers. The installation of OSes was 
> totally identical on both the servers. After that I ran these commands:
> 
> apt update
> apt upgrade -> everything was already up to date
> apt install lxc
> lxc-create -n guest -t download -> choose Debian Jessie i386
> lxc-start -n guest
> lxc-attach -n guest
> Alls well till this stage on both the servers as I am successfully dropped 
> onto the guest shell:
> 
> root@guest:~#
> 
> Now if I run any command like "ps aux" on the lxc guest shell:
> 
> root@guest:~# ps aux
> USER   PID %CPU %MEMVSZ   RSS TTY  STAT START   TIME COMMAND
> root 1  0.0  0.3   4984  3580 ?Ss   06:47   0:00 /sbin/init
> systemd+37  0.0  0.2   3508  2444 ?Ss   06:47   0:00 
> /lib/systemd/systemd-networkd
> root40  0.0  0.2  10336  2528 ?Ss   06:47   0:00 
> /lib/systemd/systemd-journald
> systemd+89  0.0  0.1   3040  1976 ?Ss   06:47   0:00 
> /lib/systemd/systemd-resolved
> root92  0.0  0.1   3772  2040 pts/3Ss+  06:47   0:00 /sbin/agetty 
> --noclear --keep-baud pts/3 115200 38400 9600 vt102
> root93  0.0  0.1   3772  1984 pts/2Ss+  06:47   0:00 /sbin/agetty 
> --noclear --keep-baud pts/2 115200 38400 9600 vt102
> root94  0.0  0.1   3772  1916 pts/1Ss+  06:47   0:00 /sbin/agetty 
> --noclear --keep-baud pts/1 115200 38400 9600 vt102
> root95  0.0  0.2   3772  2056 pts/0Ss+  06:47   0:00 /sbin/agetty 
> --noclear --keep-baud pts/0 115200 38400 9600 vt102
> root96  0.0  0.1   3772  2032 console  Ss+  06:47   0:00 /sbin/agetty 
> --noclear --keep-baud console 115200 38400 9600 vt102
> root   106  0.0  0.3   5212  3256 pts/2Ss   06:57   0:00 /bin/bash
> root   109  0.0  0.2   4548  2316 pts/2R+   06:57   0:00 ps aux
> 
> I do get the output on both. But one server remains on the guest shell (as it 
> should), but the other one immediately exits to the host ( root@host:~# ) 
> after showing the output. I can see following lines in the dmesg output of 
> server which has this issue:
> 
> [Fri Mar 22 02:42:17 2019] bash[1544] bad frame in 32bit sigreturn 
> frame:ffd7876c ip:f760a106 sp:ffd78cd0 orax:
> [Fri Mar 22 02:42:17 2019]  in libc-2.19.so[f75dc000+16e000]
> [Fri Mar 22 02:42:17 2019] bash[1544] bad frame in 32bit sigreturn 
> frame:ffd7876c ip:f760a106 sp:ffd78cd0 orax:
> [Fri Mar 22 02:42:17 2019]  in libc-2.19.so[f75dc000+16e000]
> [Fri Mar 22 02:42:17 2019] bash[1544] bad frame in 32bit sigreturn 
> frame:ffd7876c ip:f760a106 sp:ffd78cd0 orax:
> [Fri Mar 22 02:42:17 2019]  in libc-2.19.so[f75dc000+16e000] 
> 
> As I mentioned before, everything is identical on both the servers:
> 
> LXC Version: 2.0.7
> Kernel: Linux host 4.9.0-8-amd64 #1 SMP Debian 4.9.144-3.1 (2019-02-19) 
> x86_64 GNU/Linux
> 
> Could it be due to different CPUs (flags) on the 2 hosts?
> 
> cat /proc/cpuinfo on working setup:
> 
> processor   : 0
> vendor_id   : GenuineIntel
> cpu family  : 6
> model   : 61
> model name  : Intel Core Processor (Broadwell, IBRS)
> stepping: 2
> microcode   : 0x1
> cpu MHz : 2394.454
> cache size  : 16384 KB
> physical id : 0
> siblings: 1
> core id : 0
> cpu cores   : 1
> apicid  : 0
> initial apicid  : 0
> fpu : yes
> fpu_exception   : yes
> cpuid level : 13
> wp  : yes
> flags   : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca 
> cmov pat pse36 clflush mmx fxsr sse sse2 syscall nx rdtscp lm constant_tsc 
> rep_good nopl xtopology pni pclmulqdq ssse3 fma cx16 pcid sse4_1 sse4_2 
> x2apic movbe popcnt tsc_deadline_timer aes xsave avx f16c rdrand hypervisor 
> lahf_lm abm invpcid_single ssbd ibrs ibpb kaiser fsgsbase bmi1 hle avx2 smep 
> bmi2 erms invpcid rtm xsaveopt arat
> bugs: cpu_meltdown spectre_v1 spectre_v2 spec_store_bypass l1tf
> bogomips: 4788.90
> clflush size: 64
> cache_alignment : 64
> address sizes   : 40 bits physical, 48 bits virtual
> 
> cat /proc/cpuinfo on problematic one:
> 
> processor   : 0
> vendor_id   : GenuineIntel
> cpu family  : 6
> model   : 62
> model name  : Intel(R) Xeon(R) CPU E5-2680 v2 @ 2.80GHz
> stepping: 4
> cpu MHz : 2799.969
> cache size  : 4096 KB
> physical id : 0
> siblings: 1
> core id : 0
> cpu cores   : 1
> apicid  : 0
> initial apicid  : 0
> fpu : yes
> fpu_exception   : yes
> cpuid level : 13
> wp  : yes
> flags   : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca 
> cmov pat pse36 clflush mmx fxsr sse sse2 ss syscall nx pdpe1gb 

Bug#925979: busybox-udeb: breaks user-params, rescue mode, etc.

[Christoph Biedl]

Cyril Brulebois wrote...

> Restoring the patch is not sufficient, as the context obviously changed.
> Given there were few changes there, I've tried reverting the upstream
> commit (9c143ce52da11ec3d21a3491c3749841d3dc10f0), restoring
> temp-deb-installer-hack.patch and enabling the relevant config option
> (only for the udeb build). debian-installer rebuilt against such a
> patched busybox-udeb seems to be working fine again.

Thanks for preparing all this and checking. There's still another issue
open for buster, I'll try to get things done with high priority.

Christoph


signature.asc
Description: PGP signature

Bug#925600: [pkg-apparmor] Bug#925600: apparmor-profiles-extra: adjust autopkgtests to also work on Ubuntu

[intrigeri]

Jamie Strandboge:
> Thanks for considering the patch.

LGTM!

I'll apply this once Buster is released.

Bug#926030: RFP: python-plyer -- platform-independent wrapper for platform-dependent APIs

[W. Martin Borgert]

Package: wnpp
Severity: wishlist

* Package name: python-plyer
  Version : 1.4.0
  Upstream Author : Kivy team 
* URL : https://pypi.org/project/plyer/
* License : MIT/X
  Programming Lang: Python
  Description : platform-independent wrapper for platform-dependent APIs

 Plyer is a platform-independent api to use features commonly found on various
 platforms, notably mobile ones, in Python.

This is a dependency for Cagou (#897232).

Bug#926005: unblock: kicad-footprints/5.1.0-1

[Carsten Schoenert]

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

Please unblock package kicad-footprints

The kicad-footprints package provides basic footprint data for the kicad
application. The footprint data are simple text files and by this the
package is platform independet.
Even if the update of the kicad package (see #926004) isn't going to be
accepted kicad-footprints should make it's way into Buster finally.

A full debdiff is big due the updates to the upstream text files. Due
it's size I've uploaded the full debdiff to p.d.o.
https://people.debian.org/~tijuca/unblock/kicad-footprints-full.debdiff.tar.xz

The modification of the debian folder between the version in testing and
unstable is on contray really small.

$ diff -puNr kicad-footprints-5.0.2/debian/ kicad-footprints-5.1.0/debian/
diff -puNr kicad-footprints-5.0.2/debian/changelog 
kicad-footprints-5.1.0/debian/changelog
--- kicad-footprints-5.0.2/debian/changelog 2018-12-04 21:05:30.0 
+0100
+++ kicad-footprints-5.1.0/debian/changelog 2019-03-11 19:58:05.0 
+0100
@@ -1,3 +1,12 @@
+kicad-footprints (5.1.0-1) unstable; urgency=medium
+
+  * [b602791] New upstream version 5.1.0
+  * [22436a1] d/control: increase Standards-Version to 4.3.0
++ No further changes needed.
+  * [d70afad] d/copyright: update years on contributors
+
+ -- Carsten Schoenert   Mon, 11 Mar 2019 19:58:05 
+0100
+
 kicad-footprints (5.0.2-1) unstable; urgency=medium
 
   * [de61c7a] New upstream version 5.0.2
diff -puNr kicad-footprints-5.0.2/debian/control 
kicad-footprints-5.1.0/debian/control
--- kicad-footprints-5.0.2/debian/control   2018-08-31 21:19:42.0 
+0200
+++ kicad-footprints-5.1.0/debian/control   2019-03-11 19:55:15.0 
+0100
@@ -10,7 +10,7 @@ Build-Depends:
  cmake,
 Vcs-Git: https://salsa.debian.org/electronics-team/KiCad/kicad-footprints.git
 Vcs-Browser: https://salsa.debian.org/electronics-team/KiCad/kicad-footprints
-Standards-Version: 4.2.1
+Standards-Version: 4.3.0
 Homepage: https://kicad.github.io/footprints
 
 Package: kicad-footprints
diff -puNr kicad-footprints-5.0.2/debian/copyright 
kicad-footprints-5.1.0/debian/copyright
--- kicad-footprints-5.0.2/debian/copyright 2018-08-31 21:20:48.0 
+0200
+++ kicad-footprints-5.1.0/debian/copyright 2019-03-11 19:55:43.0 
+0100
@@ -10,11 +10,11 @@ Comment: Like all KiCad libraries the li
  Material'."
 
 Files: *
-Copyright: 2018 KiCad Community
+Copyright: 2019 KiCad Community
 License: CC-BY-SA-4.0-with-exception
 
 Files: debian/*
-Copyright: 2018, Carsten Schoenert 
+Copyright: 2019, Carsten Schoenert 
2017-2018, Jean-Samuel Reynaud 
 License: GPL-2+


unblock kicad-footprints/5.1.0-1

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

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

Bug#926009: openjdk-11 breaks libreoffice autopkgtests

[Rene Engelhard]

reassign 926009 src:openjdk-11
thanks

Hi,

On Sat, Mar 30, 2019 at 10:32:04AM +0100, Paul Gevers wrote:
> Currently this regression is blocking the migration of openjdk-11 to
> testing [1].

IMHO correctly so, some of the changes are so far away from the freeze
policy..

In any case, "normal" (j)unit tests on building LibreOffice don't work
either, so it's actually also a FTBFS for libreoffice...

> == Add the extension ==
> javaldx: Could not find a Java Runtime Environment!
> Please ensure that a JVM and the package libreoffice-java-common
> is installed.
> If it is already installed then try removing
> ~/.libreoffice/3/user/config/javasettings_Linux_*.xml

For that matter, happens even then.

Regards,

Rene

Bug#926003: clamav 0.100.3+dfsg-0+deb9u1 flagged for acceptance

[Adam D Barratt]

Control: tags -1 + pending

Hi,

The upload referenced by this bug report has been flagged for acceptance into 
the proposed-updates queue for Debian stretch.

Thanks for your contribution!

Upload details
==

Package: clamav
Version: 0.100.3+dfsg-0+deb9u1

Explanation: security updates: out-of-bounds heap read condition may occur when 
scanning PDF documents [CVE-2019-1787]; out-of-bounds heap read condition may 
occur when scanning PE files packed using Aspack [CVE-2019-1789]; out-of-bounds 
heap write condition may occur when scanning OLE2 files [CVE-2019-1788]

Bug#925548: libdatetime-timezone-perl 2.09-1+2019a flagged for acceptance

[Adam D Barratt]

Control: tags -1 + pending

Hi,

The upload referenced by this bug report has been flagged for acceptance into 
the proposed-updates queue for Debian .

Thanks for your contribution!

Upload details
==

Package: libdatetime-timezone-perl
Version: 2.09-1+2019a

Explanation: update included data

Bug#925919: (no subject)

[Jan Wagner]

Hi,

we've seen this with the following errors on several VMWare systems:

Mar 28 13:58:13 mail kernel: [26002.992114] general protection fault:
 [#1] SMP

Mar 28 07:03:46 sigten kernel: [ 1251.757467] BUG: Bad page map in
process apache2  pte:2c303a2236706f70 pmd:7afb5067
Mar 28 07:03:46 sigten kernel: [ 1251.757512] addr:7fcd0c40
vm_flags:0870 anon_vma:  (null) mapping:88007bac8630
index:1f
Mar 28 07:03:46 sigten kernel: [ 1251.757575] vma->vm_ops->fault:
filemap_fault+0x0/0x440
Mar 28 07:03:46 sigten kernel: [ 1251.757631] vma->vm_file->f_op->mmap:
ext4_file_mmap+0x0/0x50 [ext4]

Mar 28 09:10:42 sigten kernel: [  720.972735] general protection fault:
 [#1] SMP

Mar 28 12:44:12 sigten kernel: [10925.220435] php: Corrupted page table
at address 3b08686
Mar 28 12:44:12 sigten kernel: [10925.220469] PGD 80007c184067 PUD
58d71067 PMD 364ec067 PTE f0e9ec3f9ab7e0f5
Mar 28 12:44:12 sigten kernel: [10925.220495] Bad pagetable: 000b [#1] SMP

Mar 28 13:09:16 sigten kernel: [  984.817671] swap_dup: Bad swap file
entry 801f7f7f7f7f7f0
Mar 28 13:09:16 sigten kernel: [  984.817752] swap_dup: Bad swap file
entry 801f7f7f7f7f7f1
Mar 28 13:09:16 sigten kernel: [  984.817817] swap_dup: Bad swap file
entry 801f7f7f7f7f7f2
Mar 28 13:09:16 sigten kernel: [  984.817869] swap_dup: Bad swap file
entry 801f7f7f7f7f7f3
Mar 28 13:09:16 sigten kernel: [  984.817896] swap_dup: Bad swap file
entry 801f7f7f7f7f7f4
Mar 28 13:09:16 sigten kernel: [  984.817911] swap_dup: Bad swap file
entry 801f7f7f7f7f7f5
Mar 28 13:09:16 sigten kernel: [  984.817926] swap_dup: Bad swap file
entry 801f7f7f7f7f7f6
Mar 28 13:09:16 sigten kernel: [  984.817941] swap_dup: Bad swap file
entry 801f7f7f7f7f7f7
Mar 28 13:09:16 sigten kernel: [  984.817957] swap_dup: Bad swap file
entry 801f7f7f7f7f7f7

Mar 30 03:28:46 balduin kernel: [70308.718825] BUG: Bad page map in
process apache2  pte:56ff01f0c760031d pmd:bafb7067
Mar 30 03:28:46 balduin kernel: [70308.718909] addr:7fde20428000
vm_flags:0a100071 anon_vma:8800372ac8a8 mapping:880233802de0
index:57
Mar 30 03:28:46 balduin kernel: [70308.718959] vma->vm_ops->fault:
filemap_fault+0x0/0x440
Mar 30 03:28:46 balduin kernel: [70308.719016] vma->vm_file->f_op->mmap:
ext4_file_mmap+0x0/0x50 [ext4]

Cheers, Jan.



signature.asc
Description: OpenPGP digital signature

Bug#882090: node-yamljs updated

[Xavier]

Hello,

I updated node-yamljs, please check my changes to see if all is OK and
ready to push.

Following our policy, source package should be renamed yamljs.js
(provides node-yamljs and libjs-yamljs).

Cheers,
Xavier

https://salsa.debian.org/js-team/node-yamljs

Bug#926016: sloppy packaging over moving a conffile

[Osamu Aoki]

Package: im-config
Version: 0.42-1
Severity: important

Problem:

conffile /etc/xdg/autostart/im-launch.desktop was introduced by 0.39-1

It's functionality is moved to /etc/xdg/autostart/im-launch-wayland.desktop
for 0.40-1, 0.41-1, and 0.42-1 without proper package scripts.

This causes double invocation of input method start up code for people
following testing/unstable.


Solution:
 * Don't move it
 * Add package script to remove /etc/xdg/autostart/im-launch-wayland.desktop
   when needed.

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

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

Versions of packages im-config depends on:
ii  gettext-base  0.19.8.1-9

Versions of packages im-config recommends:
ii  kdialog 4:17.08.3-2
ii  whiptail0.52.20-8
ii  x11-common  1:7.7+19
ii  zenity  3.30.0-2

im-config suggests no packages.

-- no debconf information

Bug#925979: busybox-udeb: breaks user-params, rescue mode, etc.

[Cyril Brulebois]

Heya,

Chris Boot  (2019-03-30):
> On 29/03/2019 17:45, Cyril Brulebois wrote:
> [snip]
> > But in practice, that means that rescue/enable=true is no longer visible
> > from the rescue-check binary package (from src:rescue), meaning a broken
> > rescue mode. I expect a number of other features to be broken in the
> > same way, via the user-params script in debian-installer-utils.
> 
> Ugh. Not again.

Sorry for the hassle…

> [snip]> I'd be happy to have a fix for this before we consider releasing D-I
> > Buster RC 1, which could otherwise be ready next week. If maintainers
> > could hint me into the right direction, that could be sufficient. ;)
> 
> Given the time constraints for buster I think your approach to
> reverting upstream's changes and re-applying our hack is probably the
> right way to go. I'll try to put something together today for review
> and, hopefully, so that you can test with if you don't mind.

I'm at a BSP, so testing bugfixes for RC bugs I opened the day prior
looks very appropriate. :)

> I've also had a thought, and I can't remember if we've considered it
> already: do the environment variables get preserved in
> /proc/1/environ, even if busybox ash can't grok them? Could d-i be
> modified to pull them from there?

Indeed, /proc/1/environ seems to have everyone!


Cheers,
-- 
Cyril Brulebois (k...@debian.org)
D-I release manager -- Release team member -- Freelance Consultant


signature.asc
Description: PGP signature

Bug#925899: lxc: Unprivileged containers fail to start after recent updates

[Pierre-Elliott Bécue]

Le mercredi 27 mars 2019 à 22:08:49-0700, Regis Smith a écrit :
> Package: lxc
> Version: 1:3.1.0+really3.0.3-6
> Severity: important
> 
> Dear Maintainer,
> 
>* What led up to the situation?
> 
> apt update; apt upgrade
> 
>* What exactly did you do (or not do) that was effective (or
>  ineffective)?
> 
> As a normal user:
> $ lxc-start -n test
> 
>* What was the outcome of this action?
> 
> lxc-start: test: lxccontainer.c: wait_on_daemonized_start: 833 No such file 
> or directory - Failed to receive the container state
> lxc-start: test: tools/lxc_start.c: main: 330 The container failed to start
> lxc-start: test: tools/lxc_start.c: main: 333 To get more details, run the 
> container in foreground mode
> lxc-start: test: tools/lxc_start.c: main: 336 Additional information can be 
> obtained by setting the --logfile and --logpriority options
> 
> If I run it in the foreground instead I get
> 
> $ lxc-start -n test -F
> lxc-start: test: lsm/apparmor.c: apparmor_prepare: 974 Cannot use generated 
> profile: apparmor_parser not available
> lxc-start: test: start.c: lxc_init: 899 Failed to initialize LSM
> lxc-start: test: start.c: __lxc_start: 1917 Failed to initialize container 
> "test"
> lxc-start: test: tools/lxc_start.c: main: 330 The container failed to start
> lxc-start: test: tools/lxc_start.c: main: 336 Additional information can be 
> obtained by setting the --logfile and --logpriority options
> 
>* What outcome did you expect instead?
> 
> A running container.  These used to work up until recently.  Now I can't stop
> already running containers because I won't be able to restart them.

Hi,

Thanks for submitting this bug.

As you can see, it is possible to get more debug via the --logfile and
the --logpriority options.

That said, the first line with the -F option says it all:

> lxc-start: test: lsm/apparmor.c: apparmor_prepare: 974 Cannot use
> generated profile: apparmor_parser not available

It means that you're lacking the apparmor_parser command, which is
shipped by apparmor. It probably means that you refused to install
apparmor on your host.

You have multiple choices. The first one being installing apparmor, and
the second one being to edit your container's configuration (or the
/etc/lxc/default.conf file) to change the lxc.apparmor.profile
parameter.

This bugreport raises an interesting question regarding the tradeoff
between the solution we implemented to fix bug #916639.

Cc-ing intrigeri: I'm reconsidering the /etc/lxc/default.conf setting
regarding apparmor.profile. Putting generated breaks many unpriv
containers as they have no apparmor.profile set in their configuration.

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

-- 
Pierre-Elliott Bécue
GPG: 9AE0 4D98 6400 E3B6 7528  F493 0D44 2664 1949 74E2
It's far easier to fight for one's principles than to live up to them.


signature.asc
Description: PGP signature

Bug#712451: [pkg-apparmor] Bug#712451: Please support AppArmor network rules

[intrigeri]

Paolo Greppi:
> Should this be documented in /usr/share/doc/apparmor/README.Debian ?

FWIW, this is now mentioned in the manpage that documents the policy
language: apparmor.d(5)

Cheers,
-- 
intrigeri

Bug#863168: Tagged as wontfix

[ghisvail]

control: tags -1 + wontfix

Bug#924184: no help for download template?

[Pierre-Elliott Bécue]

Le dimanche 10 mars 2019 à 07:43:30+0100, Harald Dunkel a écrit :
> Package: lxc
> Version: 1:3.1.0+really3.0.3-5
> 
> Running
>   lxc-create -t download -- --help
> 
> I had expected to get usage information about the download template,
> but instead I got a huge list of images. Next it showed
> 
>   Distribution:
> 
> and got unresponsive. Exit with ^C or ^D. Apparently it has created a
> new container directory /var/lib/lxc/--help.
> 
> This is unexpected. The -- is supposed to separate the template
> options from the options to lxc-create itself. There should have
> either been an error message about the missing "-n name" option,
> or any kind of usage message.

Hi,

From lxc-create(1) manpage:

   -- template-options
 This will pass template-options to the template as
 arguments. To see the list of options supported by
 the template, you can run lxc-create -t TEMPLATE
 -h.

So this is the mechanic to get the help for a specific template.

That said, the fact that it attempts to create a container named --help
is quite weird. I suspect it's the result of the change the developers
of lxc made to make lxc-XXX command accepting the container's name as a
positional argument. As lxc-download doesn't recognise --help as an
argument, it became positional and got interpreted as the name of the
container.

Best regards,

-- 
Pierre-Elliott Bécue
GPG: 9AE0 4D98 6400 E3B6 7528  F493 0D44 2664 1949 74E2
It's far easier to fight for one's principles than to live up to them.


signature.asc
Description: PGP signature

Bug#911890: Pending removal

[ghisvail]

control: tags -1 + pending

Removal bug filed, see #926022.

Bug#923810: ITP: ruby-sassc -- Use libsass with Ruby

[Manas Kashyap]

As i talked with ruby-team , so they advised me on learning the new
techniques more and also as adding gbp.conf is a nice thing to do and
practice , so , i will keep it maintained in sass-team


On Thu, Mar 28, 2019 at 12:38 AM Jonas Smedegaard  wrote:

> Quoting Manas Kashyap (2019-03-27 17:37:49)
> > So, As Jonas said , that the way we do in ruby-team , keeping sbuild
> > happy and checking it from meta build command , is not similar to the
> > way it is maintained by sass team , so i would like to maintain this
> > ruby-sassc package in ruby-team , therefore i request , to please
> > delete the repo from sass team and i will ask in ruby-team to create a
> > desired repo and will add it there.
>
> Too bad this is the outcome, but that is your choice to make.
>
> You have the power in the Sass team to delete the repository yourself,
> but if you don't do that - e.g. if you unsubscribe from the team while
> leaving behind the repository - then I will clean up after you.
>
> Thanks for your interest in maintaining ruby-sassc, regardless how.
> Hope to hear more from you in the future.  Did you perhaps consider
> attending the next Debconf?  You are quite welcome!
>
>   https://debconf19.debconf.org/
>
>
>  - Jonas
>
> --
>  * Jonas Smedegaard - idealist & Internet-arkitekt
>  * Tlf.: +45 40843136  Website: http://dr.jones.dk/
>
>  [x] quote me freely  [ ] ask before reusing  [ ] keep private
>

Bug#926032: [chromium] Buggy / Solarized videos

[victor.boyau]

Package: chromium
Version: 73.0.3683.75-1
Severity: important

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

A lot of streaming videos are rendered incorrectly and truly
unwatchable. Sound is not affected, however. Youtube videos look good
but not those streamed from other popular web sites like these ones :

https://www.imdb.com (try any movie trailer, e.g.)
https://www.francetvinfo.fr/en-direct/tv.html (any embedded video)

Downgrading to a previous version like 72.x either from stable
ou from testing immedialely solves the problem.

VB

--- System information. ---
Architecture: 
Kernel:   Linux 4.19.32-tz1903270806

Debian Release: 9.8
  990 stable-updates  deb.debian.org 
  990 stable  wire-app.wire.com 
  990 stable  download.webmin.com 
  990 stable  deb.debian.org 
  990 proposed-updates deb.debian.org 
  777 stretch-backports deb.debian.org 
  666 testing deb.debian.org 
  500 unstabledeb.debian.org 

--- Package information. ---
Depends(Version) | Installed
-+-=
libasound2   (>= 1.0.16) | 1.1.8-1
libatk-bridge2.0-0(>= 2.5.3) | 2.30.0-2~bpo9+1
libatk1.0-0   (>= 2.2.0) | 2.30.0-1~bpo9+1
libatomic1  (>= 4.8) | 8.3.0-4
libatspi2.0-0(>= 2.9.90) | 2.30.0-2~bpo9+1
libavcodec58  (>= 7:4.0) | 7:4.1.1-1
libavformat58 (>= 7:4.1) | 7:4.1.1-1
libavutil56   (>= 7:4.0) | 7:4.1.1-1
libc6  (>= 2.28) | 2.28-8
libcairo-gobject2(>= 1.10.0) | 1.16.0-4
libcairo2 (>= 1.6.0) | 1.16.0-4
libcups2  (>= 1.4.0) | 2.2.1-8+deb9u3
libdbus-1-3  (>= 1.9.14) | 1.12.12-1
libdrm2   (>= 2.3.1) | 2.4.97-1
libevent-2.1-6 (>= 2.1.8-stable) | 2.1.8-stable-4
libexpat1 (>= 2.0.1) | 2.2.0-2+deb9u1
libflac8  (>= 1.3.0) | 1.3.2-3
libfontconfig1   (>= 2.12.6) | 2.13.1-2
libfreetype6  (>= 2.3.9) | 2.9.1-3
libgcc1   (>= 1:4.0) | 1:8.3.0-4
libgdk-pixbuf2.0-0   (>= 2.22.0) | 2.38.1+dfsg-1
libglib2.0-0 (>= 2.31.8) | 2.58.3-1
libgtk-3-0   (>= 3.9.10) | 3.24.5-1
libharfbuzz0b (>= 2.2.0) | 2.3.1-1
libicu63(>= 63.1-1~) | 63.1-6
libjpeg62-turbo   (>= 1.5.0) | 1:1.5.2-2+b1
libjsoncpp1   (>= 1.7.4) | 1.7.4-3
liblcms2-2  (>= 2.2+git20110628) | 2.9-3
libminizip1 (>= 1.1) | 1.1-8+b1
libnspr4   (>= 2:4.9-2~) | 2:4.20-1
libnss3  (>= 2:3.22) | 2:3.42.1-1
libopenjp2-7  (>= 2.2.0) | 2.3.0-2
libopus0(>= 1.1) | 1.3-1
libpango-1.0-0   (>= 1.14.0) | 1.42.4-6
libpangocairo-1.0-0  (>= 1.14.0) | 1.42.4-6
libpci3   (>= 1:3.5.2-1) | 1:3.5.2-1
libpng16-16 (>= 1.6.2-1) | 1.6.36-5
libpulse0(>= 0.99.1) | 12.2-4
libre2-5   (>= 20160901) | 20190101+dfsg-2
libsnappy1v5 | 1.1.7-1
libstdc++6(>= 6) | 8.3.0-4
libva2(>= 1.0.3) | 2.4.0-1
libvpx5   (>= 1.6.0) | 1.7.0-3
libwebp6  (>= 0.5.1) | 0.6.1-2
libwebpdemux2 (>= 0.5.1) | 0.6.1-2
libwebpmux3 (>= 0.6.1-2) | 0.6.1-2
libx11-6 (>= 2:1.4.99.1) | 2:1.6.7-1
libx11-xcb1  | 2:1.6.7-1
libxcb1 (>= 1.6) | 1.13.1-2
libxcomposite1  (>= 1:0.3-1) | 1:0.4.4-2
libxcursor1   (>> 1.1.2) | 1:1.1.15-2
libxdamage1   (>= 1:1.1) | 1:1.1.4-3+b3
libxext6 | 2:1.3.3-1+b2
libxfixes3(>= 1:5.0) | 1:5.0.3-1

Bug#890084: libvirt: error : unable to set AppArmor profile

[intrigeri]

Control: tag -1 + unreproducible

Hi Craig,

did this problem happen again? If it ever does, please share the
output of "sudo journalctl -u libvirtd.service" and the relevant
file timestamps.

I'm using libvirt + AppArmor heavily and have never seen it myself :/

Cheers,
-- 
intrigeri

Bug#926040: u-boot: Please support Olimux Teres-I DIY laptop

[Jonas Smedegaard]

Source: u-boot
Version: 2019.01+dfsg-3
Severity: wishlist
Tags: patch

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

As subject says, please have u-boot support Olimux Teres-I DIY laptop.

The 2 patches I have put together at
https://salsa.debian.org/js/u-boot/tree/master/debian/patches/sunxi
works succesfully on my laptop, when used together with
https://salsa.debian.org/js/u-boot/commit/532adee and
https://salsa.debian.org/js/u-boot/commit/85402df


 - Jonas

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEn+Ppw2aRpp/1PMaELHwxRsGgASEFAlyfqskACgkQLHwxRsGg
ASGQ1RAAlvD59IcsGWNedQsAaicbmSatLKlT4BtHdIaREMcIMs1yAo/E4/lz9e82
pFzB//Vfdi048Vj0uGM7f1AD6etpw8Q8jIshnIUsR1imxdsZBwoZYtfICYCVmmU9
Cnjkfn7d/5CyOdTOwoG/vzZZEI/XY+HgEmN4HD1LQ9BeO+KSKmAqQnCYjjjFtbvW
KUZt5/C0TaZY7Bh4PVwbAWXUws0nol13JinmZCDyfFKn7+iTsVqSIF0az4TAPkjB
wlu4q7h1ZLbalIOMUwqfYrLzqC53xrgzssK+ZQghCwqvKs0O8KvUfpypApi9z62o
Voprd1jMxXU3dEUlh3WMZ0WaKOO6x+TjOL/C/a4XFgIPevDJyMwpIpkzA4/z1lI4
Ra+PgP6cXrw/R570Dx5iUgU85Z+cgXPOUJ+mbtYc3qP3EO6ASB3rKfdXx5v/g5rh
kToXQMM1PZb9b9H5QLU6SIgT4NpxV6/kSRk468RtJ0hebLQikADzl8fngJKIexqk
sRey3anRnPHN40o8RDp1TrfxkQMkgvJhN/RH31TZMyVKpjVxrvgEcnhit7ma/Sk9
u0bcNATdKOPJ21lvKteMfwMY8/4vTbTjiIrCaA/OjorBwCufx1+sIFNN5H4vdp1v
O+lPydd4H8j7zp8AXl29U7j5MleLUSuogtMSxm1/yjILhN2Eya8=
=heer
-END PGP SIGNATURE-

Bug#924018: RM: python3.6 -- superseded by python3.7

[Scott Kitterman]

This removal is done now.

Documenting the cruft left behind for the future:

# Broken Depends:
ecflow: python3-ecflow [kfreebsd-amd64 kfreebsd-i386]
gdb: gdb [hurd-i386]
 gdb-multiarch [hurd-i386]
glom: glom [kfreebsd-amd64 kfreebsd-i386]
  libglom-1.30-0 [kfreebsd-amd64 kfreebsd-i386]
libixion: python3-ixion [hurd-i386]
libkolabxml: python3-kolabformat [kfreebsd-amd64 kfreebsd-i386]
libpeas: libpeas-1.0-0 [kfreebsd-amd64 kfreebsd-i386]
libxml2: python3-libxml2 [kfreebsd-amd64 kfreebsd-i386]
 python3-libxml2-dbg [kfreebsd-amd64 kfreebsd-i386]
ovito: ovito [amd64 arm64 i386 mips mips64el mipsel ppc64el s390x]
plplot: python3-plplot [hurd-i386 kfreebsd-amd64 kfreebsd-i386]
python3-plplot-qt [hurd-i386 kfreebsd-amd64 kfreebsd-i386]
poezio: poezio
pyotherside: pyotherside-tests [kfreebsd-i386]
pyqt5: python3-pyqt5 [kfreebsd-amd64 kfreebsd-i386]
   python3-pyqt5.qtquick [kfreebsd-amd64 kfreebsd-i386]
pyside: libpyside-py3-1.2 [hurd-i386 kfreebsd-amd64 kfreebsd-i386]
python3-pyside.phonon [hurd-i386 kfreebsd-amd64 kfreebsd-i386]
python3-pyside.qtcore [hurd-i386 kfreebsd-amd64 kfreebsd-i386]
python3-pyside.qtdeclarative [hurd-i386 kfreebsd-amd64 kfreebsd-i386]
python3-pyside.qtgui [hurd-i386 kfreebsd-amd64 kfreebsd-i386]
python3-pyside.qthelp [hurd-i386 kfreebsd-amd64 kfreebsd-i386]
python3-pyside.qtnetwork [hurd-i386 kfreebsd-amd64 kfreebsd-i386]
python3-pyside.qtopengl [hurd-i386 kfreebsd-amd64 kfreebsd-i386]
python3-pyside.qtscript [hurd-i386 kfreebsd-amd64 kfreebsd-i386]
python3-pyside.qtsql [hurd-i386 kfreebsd-amd64 kfreebsd-i386]
python3-pyside.qtsvg [hurd-i386 kfreebsd-amd64 kfreebsd-i386]
python3-pyside.qttest [hurd-i386 kfreebsd-amd64 kfreebsd-i386]
python3-pyside.qtuitools [hurd-i386 kfreebsd-amd64 kfreebsd-i386]
python3-pyside.qtwebkit [hurd-i386 kfreebsd-amd64 kfreebsd-i386]
python3-pyside.qtxml [hurd-i386 kfreebsd-amd64 kfreebsd-i386]
python-escript: python3-escript [hurd-i386 kfreebsd-amd64 kfreebsd-i386]
python-numpy: python3-numpy [kfreebsd-amd64 kfreebsd-i386]
pythonqt: libpythonqt-qt5-python3-3 [kfreebsd-amd64 kfreebsd-i386]
  libpythonqt-qtall-qt5-python3-3 [kfreebsd-amd64 kfreebsd-i386]
ros-image-common: python3-camera-calibration-parsers [kfreebsd-amd64]
ros-ros-comm: python3-roslz4 [kfreebsd-amd64 kfreebsd-i386]
uwsgi: uwsgi-plugin-python3 [kfreebsd-amd64 kfreebsd-i386]
vim: vim-athena [kfreebsd-amd64 kfreebsd-i386]
 vim-gtk [kfreebsd-amd64 kfreebsd-i386]
 vim-gtk3 [kfreebsd-amd64 kfreebsd-i386]
 vim-nox [kfreebsd-amd64 kfreebsd-i386]
wxpython4.0: python3-wxgtk-media4.0 [kfreebsd-amd64 kfreebsd-i386]
 python3-wxgtk-webview4.0 [kfreebsd-amd64 kfreebsd-i386]
 python3-wxgtk4.0 [kfreebsd-amd64 kfreebsd-i386]
zeroc-ice: python3-zeroc-ice [kfreebsd-amd64 kfreebsd-i386]

Scott K

Bug#900573: qreator: Proposed patch to fix the crash

[Andreas Boll]

On Thu, Mar 28, 2019 at 10:22:31PM +0800, Chow Loong Jin wrote:
> On Wed, Mar 27, 2019 at 10:31:35PM +0100, Andreas Boll wrote:
> > Control: severity -1 serious
> > Control: tags -1 + patch
> > 
> > Dear maintainer,
> > 
> > I've prepared a patch to fix this issue.
> > Also currently the package qreator isn't useful at all with this issue
> > because it crashes on startup. Thus bumping severity to serious
> > because this package shouldn't end up in Debian Buster without a fix
> > for this issue.
> > 
> > Please let me know if I should upload this fix as NMU or if you like
> > to upload it yourself.
> 
> Please go ahead and upload this fix. Thanks.
> 
> -- 
> Kind regards,
> Loong Jin

Cool, I've uploaded it to sid now.
Attached is the nmudiff.

Thanks,
Andreas
diff -Nru qreator-16.06.1/debian/changelog qreator-16.06.1/debian/changelog
--- qreator-16.06.1/debian/changelog	2018-04-14 14:48:31.0 +0200
+++ qreator-16.06.1/debian/changelog	2019-03-30 20:35:12.0 +0100
@@ -1,3 +1,11 @@
+qreator (16.06.1-3.1) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * Add Fix-python-pil-imports.patch, fixes a program crash due to
+incorrect PIL imports (Closes: #900573).
+
+ -- Andreas Boll   Sat, 30 Mar 2019 20:35:12 +0100
+
 qreator (16.06.1-3) unstable; urgency=medium
 
   * [207e2e1] Port qreator to libnm (Closes: #857227)
diff -Nru qreator-16.06.1/debian/patches/Fix-python-pil-imports.patch qreator-16.06.1/debian/patches/Fix-python-pil-imports.patch
--- qreator-16.06.1/debian/patches/Fix-python-pil-imports.patch	1970-01-01 01:00:00.0 +0100
+++ qreator-16.06.1/debian/patches/Fix-python-pil-imports.patch	2019-03-27 21:45:38.0 +0100
@@ -0,0 +1,22 @@
+Author: Andreas Boll 
+Date:   Wed Mar 27 21:09:41 2019 +0100
+
+Fix python-pil imports
+
+Fixes bug #900573
+
+diff --git a/qreator/QRCode.py b/qreator/QRCode.py
+index d3a0130..930a538 100644
+--- a/qreator/QRCode.py
 b/qreator/QRCode.py
+@@ -20,8 +20,8 @@ try:
+ except ImportError:
+ print "You need to install the python-qrencode package"
+ sys.exit(1)
+-import Image
+-import ImageOps
++from PIL import Image
++from PIL import ImageOps
+ import cairo
+ import array
+
diff -Nru qreator-16.06.1/debian/patches/series qreator-16.06.1/debian/patches/series
--- qreator-16.06.1/debian/patches/series	2018-04-14 14:48:31.0 +0200
+++ qreator-16.06.1/debian/patches/series	2019-03-27 21:45:54.0 +0100
@@ -3,3 +3,4 @@
 Port-to-geoclue-2.0.patch
 Port-to-libnm.patch
 Fix-IndexError-when-a-wifi-network-has-100-strength.patch
+Fix-python-pil-imports.patch


signature.asc
Description: PGP signature

Bug#926048: RM: tbdialout/1.7.2-1+deb9u1

[Moritz Muehlenhoff]

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

This extension is broken with Thunderbird 60 and was already removed from sid.

Cheers,
Moritz

Bug#926033: RM: zotero-standalone-build -- ROM; outdated; RC buggy; orphaned

[Sébastien Villemot]

Package: ftp.debian.org
Severity: normal

Dear ftpmasters,

Please remove zotero-standalone-build.

The package is now in bad shape, won’t be part of buster, and significant work
is needed to revive it.

I orphaned the package 6 months ago and nobody has showed up.

It’s better to remove it now instead of letting it bitrot.

Cheers,

--
⢀⣴⠾⠻⢶⣦⠀  Sébastien Villemot
⣾⠁⢠⠒⠀⣿⡁  Debian Developer
⢿⡄⠘⠷⠚⠋⠀  http://sebastien.villemot.name
⠈⠳⣄  http://www.debian.org

Bug#900611: Re[2]: [Pkg-libvirt-maintainers] Bug#900611: libvirt-daemon-system: deamon not start, problem in apparmor config

[intrigeri]

Control: fixed -1 3.10.0-1

Hi,

rem_lex:
> fixed by add in to file /etc/apparmor.d/usr.sbin.libvirtd at line 39
> ///
> diff -au ./usr.sbin.libvirtd.old ./usr.sbin.libvirtd.new
> --- ./usr.sbin.libvirtd.old 2018-03-12 20:11:00.0 +0200
> +++ ./usr.sbin.libvirtd.new 2018-06-02 01:28:10.0 +0300
> @@ -36,6 +36,7 @@
>    network inet6 dgram,
>    network packet dgram,
>    network packet raw,
> +  network netlink raw,

I've fixed this upstream with commit 3b1d19e6c9500d392b6635de92877b725d214f7f,
that was first released in libvirt v3.10.0.

Cheers,
-- 
intrigeri

Bug#878121: Updates about BLAS64, co-installable variants

[Sébastien Villemot]

Le mardi 05 février 2019 à 03:34 +, Mo Zhou a écrit :

> I'd like to update the proposal again. Alerted by the threading issue
> about Octave+MKL, I changed my mind to make all variants co-installable
> so any user would have a chance to switch them without installation/removal.
> This proposal has been applied to BLIS (>= 0.5.1-8) already.
> 
> I believe this version of layout looks far much better.

Thanks. Indeed I also prefer the flat layout.

-- 
⢀⣴⠾⠻⢶⣦⠀  Sébastien Villemot
⣾⠁⢠⠒⠀⣿⡁  Debian Developer
⢿⡄⠘⠷⠚⠋⠀  http://seb
astien.villemot.name
⠈⠳⣄  http://www.debian.org


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

Bug#926036: net-retriever: missing support for Acquire-By-Hash

[Julien Cristau]

Package: net-retriever
Version: 1.51
Severity: minor
Tags: patch

olasd tried to install his new laptop.  He got hashsum mismatches.  That
made him sad.  We don't want a sad olasd.

Patch up at
https://salsa.debian.org/jcristau/net-retriever/commit/2653045287c502399c31495e1dfd502e03efbc08

Cheers,
Julien

Bug#922339: unblock: python-cassandra-driver/3.16.0-1

[Paul Gevers]

tags 922339 wontfix
thanks

On Sun, 17 Mar 2019 17:38:21 + Jonathan Wiltshire 
wrote:
> On Thu, Feb 14, 2019 at 08:11:55PM +0100, Héctor Orón Martínez wrote:
> > Please unblock package python-cassandra-driver
> > 
> > I have been working with Emmanuel Arias on getting his package sponsored
> > into Debian, however it did not make it into Buster on time. It is a
> > `salt` build dependency (however `salt` package maintainer has disabled
> > it until it makes it in Buster).
> 
> Is the intention that salt will enable support once this package migrates?
> Will that require an unblock too?
> 
> #921658 seems to suggest that salt is only a test-time build dependency.
> Does this mean that not all of salt's tests are being run at the moment?
> What is the impact of this?
> 
> 2018-12-05 when the upload was prepared to 2019-02-08 when it was uploaded
> is quite a long delay. Is long-term maintenance assured? Are sufficient 
> sponsors available for the next 5-6 years?

I am closing this bug as wontfix as it is getting too late in the cycle
for new packages and the above questions were not answered.

Paul



signature.asc
Description: OpenPGP digital signature

Bug#915319: Further triaging

[Giovanni Mascellani]

Il 30/03/19 19:14, Scott Kitterman ha scritto:
> Is there anything left in the archive that uses this functionality?

I am not sure this question is for me, but just in case: I have no idea.
I just met this bug during the Paris BSP, but I do not specific
knowledge of neither KDE nor CMake.

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



signature.asc
Description: OpenPGP digital signature

Bug#915319: Further triaging

[Scott Kitterman]

On March 30, 2019 6:10:40 PM UTC, Giovanni Mascellani  wrote:
>user debian-rele...@lists.debian.org
>
>usertags 915319 + bsp-2019-03-fr-paris
>tags 915319 + patch
>thank you
>
>Hi,
>
>I did some further diagnosis on this bug: the reason why CMake fails to
>discover libsmbclient is because CMake tries to compile a little
>program
>including libsmbclient.h using -std=c90, which is insufficient for
>libsmbclient.h. However libsmbclient.h works with more recent C
>standards, like the GCC default -std=gnu11.
>
>The attached patch should fix the problem. I can NMU if this is ok for
>you. Probably it is not the cleanest solution ever (if would be better
>to fix CMake files from kdelibs5-dev), but it seems to work.
>
>Thanks, Giovanni.


Is there anything left in the archive that uses this functionality?

Scott K

Bug#918320: (no subject)

[Jonathan Dupart]

user debian-rele...@lists.debian.org
usertags 918320 + bsp-2019-03-fr-paris
hank you

Bug#924965: libssh2: CVE-2019-3855 CVE-2019-3856 CVE-2019-3857 CVE-2019-3858 CVE-2019-3859 CVE-2019-3860 CVE-2019-3861 CVE-2019-3862 CVE-2019-3863

[Salvatore Bonaccorso]

Hi,

On Tue, Mar 19, 2019 at 10:23:22AM +0100, Salvatore Bonaccorso wrote:
> Source: libssh2
> Version: 1.8.0-2
> Severity: grave
> Tags: security upstream
> Control: found -1 1.7.0-1
> 
> Hi,
> 
> The following vulnerabilities were published for libssh2.
[...]

Trying to work on a NMU and should be ready soon for debdiff proposal
and upload to delayed queue.

Regards,
Salvatore

Bug#876893: Patch for multiple security issues

[Moritz Mühlenhoff]

Attached patch fixes most open security issues in testing/sid
(as applied by Leonidas S. Barbosa in Ubuntu), but needs
additional work to deal with the versioned symbols fallout
caused by GCC changes which happened after the last exiv upload
to sid.
diff -Nru exiv2-0.25/debian/patches/CVE-2017-11591.patch exiv2-0.25/debian/patches/CVE-2017-11591.patch
--- exiv2-0.25/debian/patches/CVE-2017-11591.patch	1970-01-01 01:00:00.0 +0100
+++ exiv2-0.25/debian/patches/CVE-2017-11591.patch	2019-02-26 00:40:56.0 +0100
@@ -0,0 +1,27 @@
+Index: exiv2-0.25/include/exiv2/value.hpp
+===
+--- exiv2-0.25.orig/include/exiv2/value.hpp
 exiv2-0.25/include/exiv2/value.hpp
+@@ -1657,11 +1657,12 @@ namespace Exiv2 {
+ ok_ = true;
+ return static_cast(value_[n]);
+ }
++#define LARGE_INT 100
+ // Specialization for rational
+ template<>
+ inline long ValueType::toLong(long n) const
+ {
+-ok_ = (value_[n].second != 0);
++ok_ = (value_[n].second != 0 && -LARGE_INT < value_[n].first && value_[n].first < LARGE_INT);
+ if (!ok_) return 0;
+ return value_[n].first / value_[n].second;
+ }
+@@ -1669,7 +1670,7 @@ namespace Exiv2 {
+ template<>
+ inline long ValueType::toLong(long n) const
+ {
+-ok_ = (value_[n].second != 0);
++ok_ = (value_[n].second != 0 && value_[n].first < LARGE_INT);
+ if (!ok_) return 0;
+ return value_[n].first / value_[n].second;
+ }
diff -Nru exiv2-0.25/debian/patches/CVE-2017-11683.patch exiv2-0.25/debian/patches/CVE-2017-11683.patch
--- exiv2-0.25/debian/patches/CVE-2017-11683.patch	1970-01-01 01:00:00.0 +0100
+++ exiv2-0.25/debian/patches/CVE-2017-11683.patch	2019-02-26 00:40:56.0 +0100
@@ -0,0 +1,42 @@
+From 1f1715c086d8dcdf5165b19164af9aee7aa12e98 Mon Sep 17 00:00:00 2001
+From: =?UTF-8?q?Dan=20=C4=8Cerm=C3=A1k?= 
+Date: Fri, 6 Oct 2017 00:37:43 +0200
+Subject: [PATCH] =?UTF-8?q?Use=20nullptr=20check=20instead=20of=20assertio?=
+ =?UTF-8?q?n,=20by=20Rapha=C3=ABl=20Hertzog?=
+MIME-Version: 1.0
+Content-Type: text/plain; charset=UTF-8
+Content-Transfer-Encoding: 8bit
+
+Source:
+https://github.com/Exiv2/exiv2/issues/57#issuecomment-333086302
+
+tc can be a null pointer when the TIFF tag is unknown (the factory
+then returns an auto_ptr(0)) => as this can happen for corrupted
+files, an explicit check should be used because an assertion can be
+turned of in release mode (with NDEBUG defined)
+
+This also fixes #57
+---
+ src/tiffvisitor.cpp | 11 ++-
+ 1 file changed, 6 insertions(+), 5 deletions(-)
+
+--- a/src/tiffvisitor.cpp
 b/src/tiffvisitor.cpp
+@@ -1290,11 +1290,12 @@ namespace Exiv2 {
+ }
+ uint16_t tag = getUShort(p, byteOrder());
+ TiffComponent::AutoPtr tc = TiffCreator::create(tag, object->group());
+-// The assertion typically fails if a component is not configured in
+-// the TIFF structure table
+-assert(tc.get());
+-tc->setStart(p);
+-object->addChild(tc);
++if (tc.get()) {
++tc->setStart(p);
++object->addChild(tc);
++} else {
++   EXV_WARNING << "Unable to handle tag " << tag << ".\n";
++}
+ p += 12;
+ }
+ 
diff -Nru exiv2-0.25/debian/patches/CVE-2017-14859_14862_14864.patch exiv2-0.25/debian/patches/CVE-2017-14859_14862_14864.patch
--- exiv2-0.25/debian/patches/CVE-2017-14859_14862_14864.patch	1970-01-01 01:00:00.0 +0100
+++ exiv2-0.25/debian/patches/CVE-2017-14859_14862_14864.patch	2019-02-26 00:40:56.0 +0100
@@ -0,0 +1,74 @@
+Backported of:
+
+Description: Fix CVE-2017-14864, CVE-2017-14862 and CVE-2017-14859
+Origin: backport, https://github.com/Exiv2/exiv2/pull/110
+Last-Update: 2017-10-25
+---
+This patch header follows DEP-3: http://dep.debian.net/deps/dep3/
+Index: exiv2-0.25/src/error.cpp
+===
+--- exiv2-0.25.orig/src/error.cpp
 exiv2-0.25/src/error.cpp
+@@ -106,7 +106,9 @@ namespace {
+ { 50, N_("Multiple TIFF array element tags %1 in one directory") }, // %1=tag number
+ { 51, N_("TIFF array element tag %1 has wrong type") }, // %1=tag number
+ { 52, N_("%1 has invalid XMP value type `%2'") }, // %1=key, %2=value type
+-{ 58, N_("corrupted image metadata") }
++{ 57, N_("invalid memory allocation request") },
++{ 58, N_("corrupted image metadata") },
++{ 59, N_("Arithmetic operation overflow") },
+ };
+ 
+ }
+Index: exiv2-0.25/src/tiffvisitor.cpp
+===
+--- exiv2-0.25.orig/src/tiffvisitor.cpp
 exiv2-0.25/src/tiffvisitor.cpp
+@@ -47,6 +47,7 @@ EXIV2_RCSID("@(#) $Id: tiffvisitor.cpp 3
+ #include 
+ #include 
+ #include 
++#include 
+ 
+ // 

Bug#925202: Keep calypso out of testing/buster

[Keith Packard]

Ivo De Decker  writes:

> I added a removal hint to get it out of testing.

I saw that after I uploaded 2.0-1... I'd been meaning to get back to
calypso for quite a while but got stuck because the various Python2
dependencies were no longer supported and yet some were not yet
available for Python3. With everything now available in Python3, it was
a fairly simple matter to transition the rest of the code over to the
newer version, which should make it far more maintainable going forward.

In addition, Python 3.7 has ThreadingHTTPServer, which means a
long-standing issue of supporting only one connection at a time has been
resolved. With that, Calypso can start to become a more complete caldav
solution, although there are still many little things to work on.

I'd be fine with having 1.5-5 not shipped in testing; it's certainly not
going to be supportable for the length of the next stable release.

> However, please note that there was a new upload in unstable. The history for
> that version doesn't include the history for 1.5-1 to 1.5-5. I don't know if
> that was intentional. I updated the metadata for this bug to make sure it
> affects both. I might be good to consolidate the history of the
> package.

Agreed; there are several useful patches on the agx debian branch but
I'd lost track of that as the package hadn't been transitioned over to
salsa. I've created a salsa project now and anyone should be able to
make changes there.

Please feel free to hack on the code if you like. For instance, getting
Guido's autopkgtest bits re-integrated would be awesome. There are also
a couple of bug reports against 1.5 and it would be good to check and
see if they're still valid against 2.0.

-- 
-keith


signature.asc
Description: PGP signature

Bug#926044: linux-image-4.19.0-4-amd64: amd_iommu and pcie 2.0 1x USB3 controller card

[Michael Rasmussen]

Package: src:linux
Version: 4.19.28-2
Severity: normal

Dear Maintainer,

I don't know whether this is related to the kernel or the motherboard but if 
amd_iommu=on is given as kernel boot parameter my external pcie 2.0 1x USB3 
controller card stops working. I have tried with kernels 4.18.x, 4.19.x, and 
5.0.x with same result.

Hardware:
Motherboard: Asrock B450 pro4
CPU: AMD Ryzen 7 1700

>From syslog:
Mar 30 10:17:33 sleipner kernel: [   46.126124] xhci_hcd :19:00.0: WARNING: 
Host System Error
Mar 30 10:17:33 sleipner kernel: [   46.126197] xhci_hcd :19:00.0: AMD-Vi: 
Event logged [IO_PAGE_FAULT domain=0x address=0xffe6f000 
flags=0x]
Mar 30 10:17:33 sleipner kernel: [   46.173112] xhci_hcd :19:00.0: Host 
halt failed, -110
Mar 30 10:18:09 sleipner kernel: [   82.157657] xhci_hcd :19:00.0: xHCI 
host not responding to stop endpoint command.
Mar 30 10:18:09 sleipner kernel: [   82.204584] xhci_hcd :19:00.0: Host 
halt failed, -110
Mar 30 10:18:09 sleipner kernel: [   82.204587] xhci_hcd :19:00.0: xHCI 
host controller not responding, assume dead
Mar 30 10:18:09 sleipner kernel: [   82.204606] xhci_hcd :19:00.0: HC died; 
cleaning up


-- Package-specific info:
** Version:
Linux version 4.19.0-4-amd64 (debian-ker...@lists.debian.org) (gcc version 
8.3.0 (Debian 8.3.0-2)) #1 SMP Debian 4.19.28-2 (2019-03-15)

** Command line:
BOOT_IMAGE=/vmlinuz-4.19.0-4-amd64 
root=UUID=aee6bc10-58e7-4966-a6c1-f1822dcee938 ro cgroup_enable=memory 
pnpacpi=off iommu=1 amd_iommu=off slab_common.usercopy_fallback=Y 
elevator=deadline

** Tainted: PWOE (12801)
 * Proprietary module has been loaded.
 * Taint on warning.
 * Out-of-tree module has been loaded.
 * Unsigned module has been loaded.

** Kernel log:
[7.084304] input: HDA NVidia HDMI/DP,pcm=8 as 
/devices/pci:00/:00:03.1/:1f:00.1/sound/card1/input17
[7.289961] bridge: filtering via arp/ip/ip6tables is no longer available by 
default. Update your scripts to load br_netfilter if you need this.
[7.294233] br0: port 1(enp28s0) entered blocking state
[7.295841] br0: port 1(enp28s0) entered disabled state
[7.297562] device enp28s0 entered promiscuous mode
[7.387133] 8021q: adding VLAN 0 to HW filter on device enp28s0
[7.393327] IPv6: ADDRCONF(NETDEV_UP): br0: link is not ready
[9.937130] e1000e: enp28s0 NIC Link is Up 1000 Mbps Full Duplex, Flow 
Control: None
[9.938196] br0: port 1(enp28s0) entered blocking state
[9.938910] br0: port 1(enp28s0) entered forwarding state
[9.939735] IPv6: ADDRCONF(NETDEV_CHANGE): br0: link becomes ready
[   10.945461] vmbr9: port 1(enp28s0.9) entered blocking state
[   10.947190] vmbr9: port 1(enp28s0.9) entered disabled state
[   10.949035] device enp28s0.9 entered promiscuous mode
[   10.955487] vmbr9: port 1(enp28s0.9) entered blocking state
[   10.957222] vmbr9: port 1(enp28s0.9) entered forwarding state
[   11.139733] vmbr20: port 1(enp28s0.20) entered blocking state
[   11.141486] vmbr20: port 1(enp28s0.20) entered disabled state
[   11.143304] device enp28s0.20 entered promiscuous mode
[   11.150842] vmbr20: port 1(enp28s0.20) entered blocking state
[   11.152582] vmbr20: port 1(enp28s0.20) entered forwarding state
[   11.344742] vmbr30: port 1(enp28s0.30) entered blocking state
[   11.346471] vmbr30: port 1(enp28s0.30) entered disabled state
[   11.348319] device enp28s0.30 entered promiscuous mode
[   11.355114] vmbr30: port 1(enp28s0.30) entered blocking state
[   11.355875] vmbr30: port 1(enp28s0.30) entered forwarding state
[   11.538429] vmbr300: port 1(enp28s0.300) entered blocking state
[   11.540147] vmbr300: port 1(enp28s0.300) entered disabled state
[   11.541881] device enp28s0.300 entered promiscuous mode
[   11.550249] vmbr300: port 1(enp28s0.300) entered blocking state
[   11.551770] vmbr300: port 1(enp28s0.300) entered forwarding state
[   11.736278] vmbr900: port 1(enp28s0.900) entered blocking state
[   11.737894] vmbr900: port 1(enp28s0.900) entered disabled state
[   11.739580] device enp28s0.900 entered promiscuous mode
[   11.745832] vmbr900: port 1(enp28s0.900) entered blocking state
[   11.747774] vmbr900: port 1(enp28s0.900) entered forwarding state
[   11.937058] vmbr1000: port 1(enp28s0.1000) entered blocking state
[   11.938670] vmbr1000: port 1(enp28s0.1000) entered disabled state
[   11.940361] device enp28s0.1000 entered promiscuous mode
[   11.946489] vmbr1000: port 1(enp28s0.1000) entered blocking state
[   11.947150] vmbr1000: port 1(enp28s0.1000) entered forwarding state
[   12.115035] usblp2: removed
[   12.132204] vmbr1100: port 1(enp28s0.1100) entered blocking state
[   12.133968] vmbr1100: port 1(enp28s0.1100) entered disabled state
[   12.134018] usblp 1-10:1.0: usblp2: USB Bidirectional printer dev 3 if 0 alt 
0 proto 2 vid 0x0922 pid 0x1002
[   12.135636] device enp28s0.1100 entered promiscuous mode
[   12.143253] vmbr1100: port 1(enp28s0.1100) entered blocking state
[   12.143930] vmbr1100: