Bug#951312: marked as done (networking: unsetting ipv6 brings many problems)

[Debian Bug Tracking System]

Your message dated Sat, 15 Feb 2020 09:50:01 +0200
with message-id <20200215075001.mbohjg7oaopsqmf3@cbuster.nuvreauspam>
and subject line Re: Bug#951312: networking: unsetting ipv6 brings many problems
has caused the Debian Bug report #951312,
regarding networking: unsetting ipv6 brings many problems
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
951312: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=951312
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: networking
Severity: grave
Justification: causes non-serious data loss

Dear Maintainer,

   * What led up to the situation? lost of networking, caused by dhcp not 
renewing IP address
   * What exactly did you do (or not do) that was effective (or
 ineffective)? disabled ipv6
   * What was the outcome of this action? dhcp 3442 non zero exit error
   * What outcome did you expect instead? well... Networking to work :-)

Longer description:
unsetting ipv6 (/etc/sysctl.conf -> net.ipv6.conf.all.disable_ipv6 = 0 
net.ipv6.conf.default.disable_ipv6 = 0 net.ipv6.conf.lo.disable_ipv6 = 0) 
generates dhcp 3442 non zero error. Disabling 3442 (dhclient.conf, removing 
request rfc3442-classless-static-routes) raises RTNETLINK answers: Permission 
denied


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

Kernel: Linux 4.19.0-8-amd64 (SMP w/1 CPU core)
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_GB.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
--- End Message ---
--- Begin Message ---
On Vi, 14 feb 20, 11:24:18, Cosimo Simeone wrote:
> Package: networking
> Severity: grave
> Justification: causes non-serious data loss
> 
> Dear Maintainer,

There is no 'networking' package so there is also no maintainer :)

There is also not enough information to re-assign your report so I'm 
closing it.

Please create a new report against the tool that your are using to 
configure your network (ifupdown, network-manager, etc.).

>* What led up to the situation? lost of networking, caused by dhcp not 
> renewing IP address
>* What exactly did you do (or not do) that was effective (or
>  ineffective)? disabled ipv6
>* What was the outcome of this action? dhcp 3442 non zero exit error
>* What outcome did you expect instead? well... Networking to work :-)
> 
> Longer description:
> unsetting ipv6 (/etc/sysctl.conf -> net.ipv6.conf.all.disable_ipv6 = 0 
> net.ipv6.conf.default.disable_ipv6 = 0 net.ipv6.conf.lo.disable_ipv6 = 0) 
> generates dhcp 3442 non zero error. Disabling 3442 (dhclient.conf, removing 
> request rfc3442-classless-static-routes) raises RTNETLINK answers: Permission 
> denied
> 
> 
> -- System Information:
> Debian Release: 10.3
>   APT prefers stable-updates
>   APT policy: (500, 'stable-updates'), (500, 'stable')
> Architecture: amd64 (x86_64)
> 
> Kernel: Linux 4.19.0-8-amd64 (SMP w/1 CPU core)
> Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8), 
> LANGUAGE=en_GB.UTF-8 (charmap=UTF-8)
> Shell: /bin/sh linked to /usr/bin/dash
> Init: systemd (via /run/systemd/system)

Kind regards,
Andrei
-- 
http://wiki.debian.org/FAQsFromDebianUser


signature.asc
Description: PGP signature
--- End Message ---

Processed: reassign 933479 to src:objcryst-fox

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> reassign 933479 src:objcryst-fox
Bug #933479 [objcryst-fox] objcryst-fox: Please rebuild against wxWidgets GTK 3 
package
Bug reassigned from package 'objcryst-fox' to 'src:objcryst-fox'.
Ignoring request to alter found versions of bug #933479 to the same values 
previously set
Ignoring request to alter fixed versions of bug #933479 to the same values 
previously set
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
933479: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=933479
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#951236: osmnx fails the remote autopkg test (access blocked)

[Jerome BENOIT]

Dear Matthias, thanks for your report.
I have just send an email to the Nominatim system administrator
to see what we can do.
Best,
Jerome

-- 
Jerome BENOIT | calculus+at-rezozer^dot*net
https://qa.debian.org/developer.php?login=calcu...@rezozer.net
AE28 AE15 710D FF1D 87E5  A762 3F92 19A6 7F36 C68B



signature.asc
Description: OpenPGP digital signature

Processed: Re: mpv: unintended code execution vulnerability

[Debian Bug Tracking System]

Processing control commands:

> tags -1 + patch
Bug #950816 [mpv] mpv: unintended code execution vulnerability
Added tag(s) patch.
> found -1 mpv/0.29.1-1
Bug #950816 [mpv] mpv: unintended code execution vulnerability
Marked as found in versions mpv/0.29.1-1.

-- 
950816: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=950816
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#950816: mpv: unintended code execution vulnerability

[astian]

Control: tags -1 + patch
Control: found -1 mpv/0.29.1-1

FYI, the patch below works for me.

Also, I think the version in stable is also affected.  The code differs
slightly so the patch will need a little tweak.

Cheers.

-- 

>From 937749b545407aa68b1d15ea5e19a6c23d62da42 Mon Sep 17 00:00:00 2001
From: astian 
Date: Mon, 11 Feb 2020 21:08:51 +
Subject: [PATCH] lua: fix unintended code execution vulnerability

Backport of upstream commit cce7062a8a6b6a3b3666aea3ff86db879cba67b6
("lua: fix highly security relevant arbitrary code execution") to
release 0.32.0.

Note:  Before release 0.32.0, it used to be that mpv-related scripts
directories where added to Lua's module-loaders search path.  This
behaviour was dropped in 0.32.0 (bc1c024ae032).  Later, a similar but
stricter behaviour was introduced (see da38caff9c0b and b86bfc907f9c).
The original commit on which this patch is based depended on the new
behaviour.  This backport retains the 0.32.0 behaviour; all it does is
filter out relative paths from "package.path" and "package.cpath" for
all Lua scripts.
---
 player/lua.c | 34 ++
 1 file changed, 34 insertions(+)

diff --git a/player/lua.c b/player/lua.c
index 6423861..172ab4e 100644
--- a/player/lua.c
+++ b/player/lua.c
@@ -273,6 +273,36 @@ static int load_scripts(lua_State *L)
 return 0;
 }
 
+static void fuck_lua(lua_State *L, const char *search_path)
+{
+void *tmp = talloc_new(NULL);
+
+lua_getglobal(L, "package"); // package
+lua_getfield(L, -1, search_path); // package search_path
+bstr path = bstr0(lua_tostring(L, -1));
+char *newpath = talloc_strdup(tmp, "");
+
+// Unbelievable but true: Lua loads .lua files AND dynamic libraries from
+// the working directory. This is highly security relevant.
+// Lua scripts are still supposed to load globally installed libraries, so
+// try to get by by filtering out any relative paths.
+while (path.len) {
+bstr item;
+bstr_split_tok(path, ";", , );
+if (bstr_startswith0(item, "/")) {
+newpath = talloc_asprintf_append(newpath, "%s%.*s",
+ newpath[0] ? ";" : "",
+ BSTR_P(item));
+}
+}
+
+lua_pushstring(L, newpath);  // package search_path newpath
+lua_setfield(L, -3, search_path); // package search_path
+lua_pop(L, 2);  // -
+
+talloc_free(tmp);
+}
+
 static int run_lua(lua_State *L)
 {
 struct script_ctx *ctx = lua_touserdata(L, -1);
@@ -326,6 +356,10 @@ static int run_lua(lua_State *L)
 
 assert(lua_gettop(L) == 0);
 
+fuck_lua(L, "path");
+fuck_lua(L, "cpath");
+assert(lua_gettop(L) == 0);
+
 // run this under an error handler that can do backtraces
 lua_pushcfunction(L, error_handler); // errf
 lua_pushcfunction(L, load_scripts); // errf fn
-- 
2.25.0

Bug#949142: marked as done (firehol: FTBFS: configure: error: cannot produce all pandoc outputs, bailing out)

[Debian Bug Tracking System]

Your message dated Sat, 15 Feb 2020 06:05:00 +
with message-id 
and subject line Bug#949142: fixed in firehol 3.1.6+ds-9
has caused the Debian Bug report #949142,
regarding firehol: FTBFS: configure: error: cannot produce all pandoc outputs, 
bailing out
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
949142: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=949142
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: firehol
Version: 3.1.6+ds-8
Severity: serious
Tags: ftbfs

Dear maintainer,

your package failed to rebuild in a standard sid/amd64 chroot.
Attached is the full build log, hopefully relevant excerpt follows:


checking for pandoc... /usr/bin/pandoc
checking whether /usr/bin/pandoc version is 1.12.2.1 or newer... yes (2.5)
checking for pandoc PDF output... no
checking for pandoc HTML output... yes
checking for pandoc manpage output... yes
configure: N.B. pandoc PDF output requires pdflatex
configure: error: cannot produce all pandoc outputs, bailing out


-- 
regards,
Mattia Rizzolo

GPG Key: 66AE 2B4A FCCF 3F52 DA18  4D18 4B04 3FCD B944 4540  .''`.
More about me:  https://mapreri.org : :'  :
Launchpad user: https://launchpad.net/~mapreri  `. `'`
Debian QA page: https://qa.debian.org/developer.php?login=mattia  `-
I: Using pkgname logfile
I: Current time: Thu Jan 16 23:37:14 UTC 2020
I: pbuilder-time-stamp: 1579217834
I: Obtaining the cached apt archive contents
I: Copying source file
I: copying [pkgs/firehol_3.1.6+ds-8.dsc]
I: copying [pkgs/firehol_3.1.6+ds.orig.tar.xz]
I: copying [pkgs/firehol_3.1.6+ds-8.debian.tar.xz]
I: Extracting source
gpgv: unknown type of key resource 'trustedkeys.kbx'
gpgv: keyblock resource '/home/mattia/.gnupg/trustedkeys.kbx': General error
gpgv: Signature made Fri Apr 12 06:16:25 2019 UTC
gpgv:using RSA key AE28AE15710DFF1D87E5A7623F9219A67F36C68B
gpgv:issuer "calcu...@rezozer.net"
gpgv: Can't check signature: No public key
dpkg-source: warning: failed to verify signature on ./firehol_3.1.6+ds-8.dsc
dpkg-source: info: extracting firehol in firehol-3.1.6+ds
dpkg-source: info: unpacking firehol_3.1.6+ds.orig.tar.xz
dpkg-source: info: unpacking firehol_3.1.6+ds-8.debian.tar.xz
dpkg-source: info: using patch list from debian/patches/series
dpkg-source: info: applying debianization.patch
dpkg-source: info: applying debianization-usrmerge-transition.patch
dpkg-source: info: applying debianization-iptables-legacy.patch
I: using fakeroot in build.
I: Installing the build-deps
I: -> Attempting to satisfy build-dependencies
Note, using file '/build/firehol_3.1.6+ds-8.dsc' to get the build dependencies
Reading package lists...
Building dependency tree...
Reading state information...
The following NEW packages will be installed:
  autoconf automake autopoint autotools-dev bsdmainutils curl debhelper
  dh-autoreconf dh-strip-nondeterminism dwz file fontconfig fontconfig-config
  fonts-dejavu-core fonts-lmodern gettext gettext-base git git-man graphviz
  groff-base inetutils-ping intltool-debian iprange iproute2 ipset iptables jq
  kmod libann0 libarchive-zip-perl libbrotli1 libbsd0 libcairo2 libcap2
  libcap2-bin libcdt5 libcgraph6 libcroco3 libcurl3-gnutls libcurl4 libdatrie1
  libdebhelper-perl libelf1 liberror-perl libexpat1
  libfile-stripnondeterminism-perl libfontconfig1 libfontenc1 libfreetype6
  libfribidi0 libgd3 libglib2.0-0 libgraphite2-3 libgssapi-krb5-2 libgts-0.7-5
  libgvc6 libgvpr2 libharfbuzz-icu0 libharfbuzz0b libice6 libicu63 libidn11
  libip4tc2 libip6tc2 libipset11 libiptc0 libjbig0 libjpeg62-turbo libjq1
  libk5crypto3 libkeyutils1 libkmod2 libkpathsea6 libkrb5-3 libkrb5support0
  liblab-gamut1 libldap-2.4-2 libldap-common libltdl7 libmagic-mgc libmagic1
  libmnl0 libncurses6 libnetfilter-acct1 libnetfilter-conntrack3 libnfnetlink0
  libnftnl11 libnghttp2-14 libonig5 libpango-1.0-0 libpangocairo-1.0-0
  libpangoft2-1.0-0 libpaper-utils libpaper1 libpathplan4 libpcap0.8
  libpipeline1 libpixman-1-0 libpng16-16 libprocps7 libpsl5 libptexenc1
  librtmp1 libsasl2-2 libsasl2-modules-db libsigsegv2 libsm6 libssh2-1
  libssl1.1 libsub-override-perl libsynctex2 libteckit0 libtexlua53
  libtexluajit2 libthai-data libthai0 libtiff5 libtool libuchardet0
  libutempter0 libwebp6 libx11-6 libx11-data libxau6 libxaw7 libxcb-render0
  libxcb-shm0 libxcb1 libxdmcp6 libxext6 libxi6 libxml2 libxml2-utils libxmu6
  libxpm4 libxrender1 libxt6 

Bug#874870: marked as done ([doomsday] Future Qt4 removal from Buster)

[Debian Bug Tracking System]

Your message dated Sat, 15 Feb 2020 03:04:36 +
with message-id 
and subject line Bug#874870: fixed in doomsday 2.2.2+ds1-1~exp1
has caused the Debian Bug report #874870,
regarding [doomsday] Future Qt4 removal from Buster
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
874870: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=874870
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: doomsday
Version: 1.15.8-5
Severity: wishlist
User: debian-qt-...@lists.debian.org
Usertags: qt4-removal


Hi! As you might know we the Qt/KDE team are preparing to remove Qt4
as [announced] in:

[announced] 


Currently Qt4 has been dead upstream and we are starting to have problems
maintaining it, like for example in the [OpenSSL 1.1 support] case.

[OpenSSL 1.1 support] 

In order to make this move, all packages directly or indirectly depending on
the Qt4 libraries have to either get ported to Qt5 or eventually get
removed from the Debian repositories.

Therefore, please take the time and:
- contact your upstream (if existing) and ask about the state of a Qt5
port of your application
- if there are no activities regarding porting, investigate whether there are
suitable alternatives for your users
- if there is a Qt5 port that is not yet packaged, consider packaging it
- if both the Qt4 and the Qt5 versions already coexist in the Debian
archives, consider removing the Qt4 version

= Porting =

Some of us where involved in various Qt4 to Qt5 migrations [migration] and we
know for sure that porting stuff from Qt4 to Qt5 is much much easier and less
painful than it was from Qt3 to Qt4.

We also understand that there is still a lot of software still using Qt4.

Don't forget to take a look at the C++ API changes page [apichanges] whenever
you start porting your application.

[migration] http://pkg-kde.alioth.debian.org/packagingqtbasedstuff.html
[apichanges] http://doc.qt.io/qt-5/sourcebreaks.html

For any questions and issues, do not hesitate to contact the Debian Qt/KDE
team at debian-qt-...@lists.debian.org

The removal is being tracked in 

Lisandro,
on behalf of the Qt4 maintainers
--- End Message ---
--- Begin Message ---
Source: doomsday
Source-Version: 2.2.2+ds1-1~exp1

We believe that the bug you reported is fixed in the latest version of
doomsday, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 874...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Boyuan Yang  (supplier of updated doomsday package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Fri, 14 Feb 2020 17:39:12 -0500
Source: doomsday
Architecture: source
Version: 2.2.2+ds1-1~exp1
Distribution: experimental
Urgency: medium
Maintainer: Debian Games Team 
Changed-By: Boyuan Yang 
Closes: 864250 874870 884608 936437
Changes:
 doomsday (2.2.2+ds1-1~exp1) experimental; urgency=medium
 .
   * Team upload.
   * New upstream release. (Closes: #884608)
 + WARNING: This release (2.2.2+ds1-1~exp1) is an experimental Debian
   package that may break. USE IT AT YOUR OWN RISK!
   If you found any bug with packaged doomsday 2.x, please report it!
 + TODO: Strip out fonts in Files-Exluded list.
 + TODO: Incorporate with the alternatives system.
 + TODO: Move the executables back to /usr/games/.
 + Migrated to Qt5. (Closes: #874870)
 + Migrated to Python3. (Closes: #936437)
   * debian/control:
 + Bump debhelper compat to v12.
 + Bump Standards-Version to 4.5.0.
 + Update build-dependencies and switch to a CMake-based buildsystem.
 + Update Vcs-* fields to use git packaging repo under Salsa games-team.
 + Update homepage field to use secure URI.
   * debian/patches-old: Moved away for a patch-free version.
   * debian/patches:
 + 0001: Add new patch to disable RPATH completely.
 + 0002: Add new patch to let .desktop files use /usr/games/ path.
   * debian/doomsday.install:
 + Do not install a compat script.
   * 

Bug#948428: marked as done (html5lib ftbfs in unstable)

[Debian Bug Tracking System]

Your message dated Sat, 15 Feb 2020 02:38:59 +
with message-id 
and subject line Bug#948428: fixed in html5lib 1.0.1-2
has caused the Debian Bug report #948428,
regarding html5lib ftbfs in unstable
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
948428: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=948428
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:html5lib
Version: 1.0.1-1
Severity: serious
Tags: sid bullseye patch

html5lib ftbfs in unstable with the current pytest.

https://github.com/html5lib/html5lib-python/pull/429

patch at
http://launchpadlibrarian.net/459711725/html5lib_1.0.1-1build1_1.0.1-1ubuntu1.diff.gz
--- End Message ---
--- Begin Message ---
Source: html5lib
Source-Version: 1.0.1-2

We believe that the bug you reported is fixed in the latest version of
html5lib, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 948...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Sandro Tosi  (supplier of updated html5lib package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Fri, 14 Feb 2020 21:22:52 -0500
Source: html5lib
Architecture: source
Version: 1.0.1-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Python Modules Team 

Changed-By: Sandro Tosi 
Closes: 948428
Changes:
 html5lib (1.0.1-2) unstable; urgency=medium
 .
   [ Ondřej Nový ]
   * Convert git repository from git-dpm to gbp layout
   * Use debhelper-compat instead of debian/compat.
 .
   [ Sandro Tosi ]
   * debian/patches/PR429.patch
 - support pytest 4 and higher; Closes: #948428
   * debian/control
 - drop flake8 from b-d, no longer needed
Checksums-Sha1:
 d8d185e1d0261d194c829fc48a16b260ebbb81c6 2337 html5lib_1.0.1-2.dsc
 3202f2fbbcf0e00862e86d452c2e1a61d80a2c64 6780 html5lib_1.0.1-2.debian.tar.xz
 9cedf82c8f1cd62c86a5869bda86d1b8fec3 7755 html5lib_1.0.1-2_source.buildinfo
Checksums-Sha256:
 0ad403ef1783b83df51ad66e9caa22ef296cc3085a01e9557703fc92fcec9992 2337 
html5lib_1.0.1-2.dsc
 214fb10b89da8a09ff5a4dd56cec02d51a4d94af1105e42562f241025355e9d8 6780 
html5lib_1.0.1-2.debian.tar.xz
 1ec931af60cce752016e07f0f9307b8ab05b969342cf951cce29b2abb472e73c 7755 
html5lib_1.0.1-2_source.buildinfo
Files:
 d6c9313f3adb9a40db36a39537939bd3 2337 python optional html5lib_1.0.1-2.dsc
 df74274b21405d7cdb6d99172635af8a 6780 python optional 
html5lib_1.0.1-2.debian.tar.xz
 fa3a2f2c13b1df4c6cc592909853ec1c 7755 python optional 
html5lib_1.0.1-2_source.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEEufrTGSrz5KUwnZ05h588mTgBqU8FAl5HVjoACgkQh588mTgB
qU9n4hAAjMSY92BqwuOjaPmek2UNF5CwTSV8ePgg2q6u/mYrHGYM7Rxx6QZveLTJ
m4LWH64kfc30WwAdZ6gVs07JHYyGQkvo+Cqud5QbJPejpJn1pv/jg9H7lXRa6RQs
S+R/BnpuHthJ8k1O9fgX3KNh15jMAG/7FFtNJ2BvCqVJPKB5iWGh/SrHVGPPZlIF
Vbq5kO/HBpFsXOfFKEoVy8jmv0fMlGzEa3XfeQdZFqNcykGqtYOeVuC00ZwWMWwA
1k8oSm54OZbmwwgS6Ceyzn7LyJQE4Ll8buBXTfsRNBbMrrUbG9dq1mGXkFGj0Qah
IFuGpO58rfhpe3tTZHirx8BQ6mwYUL5Z6t7Ptv1QU0g/v7TUcxbn7Jrkw9ao1r5z
z3wWkDn5KYmk+nhPjw4OYNvPsUIXSMyt/VjN6NJN+v/GNW4AEDx+HDKpO97cQQJS
jZqX4SWf7XJWEtUscMguBP3qyXh8wj1HqGjAbe7PtSrPRsFC3F3uPtk7LW5oI7Ty
vOon8exJyqoQwlBjbo3PNmQcDu2lhUUjcungmTQoCOSoPMq31SiHgxvi2z85HgVw
hV6Yrqkz7DD4/jOe7HS3HQxdfrb/O+e0NdS04qqdiMfwTkwvvCu7x392QMQ4NTyU
znlFV1AQOpPFZq22arDG3AMTHKk0t9HaU/gGdqiml0hAKuscPpM=
=x+q2
-END PGP SIGNATURE End Message ---

Bug#948428: marked as pending in html5lib

[Sandro Tosi]

Control: tag -1 pending

Hello,

Bug #948428 in html5lib reported by you has been fixed in the
Git repository and is awaiting an upload. You can see the commit
message below and you can check the diff of the fix at:

https://salsa.debian.org/python-team/modules/html5lib/commit/70f3b00e63cc3c93d31546fb24934a90a638aaa3


support pytest 4 and higher; Closes: #948428


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/948428

Processed: Bug#948428 marked as pending in html5lib

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #948428 [src:html5lib] html5lib ftbfs in unstable
Added tag(s) pending.

-- 
948428: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=948428
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#935296: marked as done (reposurgeon: FTBFS on amd64)

[Debian Bug Tracking System]

Your message dated Fri, 14 Feb 2020 16:08:12 -0700
with message-id <20200214230812.GA801560@debian-Aspire-M5-481G.FokFamily>
and subject line Bug#935296: fixed in reposurgeon 4.2-1
has caused the Debian Bug report #935296,
regarding reposurgeon: FTBFS on amd64
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
935296: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=935296
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
package: src:reposurgeon
version: 3.45-1
severity: serious
tags: ftbfs

Hi,

A binnmu of reposurgeon in unstable fails on amd64:

https://buildd.debian.org/status/package.php?p=reposurgeon

Cheers,

Ivo
--- End Message ---
--- Begin Message ---
Source: reposurgeon
Source-Version: 4.2-1

We believe that the bug you reported is fixed in the latest version of
reposurgeon.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 935...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Anthony Fok  (supplier of updated reposurgeon package)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Thu, 13 Feb 2020 13:28:18 -0700
Source: reposurgeon
Architecture: source
Version: 4.2-1
Distribution: unstable
Urgency: medium
Maintainer: Anthony Fok 
Changed-By: Anthony Fok 
Changes:
 reposurgeon (4.2-1) unstable; urgency=medium
 .
   [ Jelmer Vernooij ]
   * Recommend brz rather than bzr-fastimport.
 .
   [ Anthony Fok ]
   * New upstream version 4.2
   * Apply "cme fix dpkg" fixes
 - Update debhelper dependency to "Build-Depends: debhelper-compat (= 12)"
 - Bump Standards-Version to 4.5.0 (no change)
   * Update debian/copyright with correct BSD-2-Clause text
 and with new author and copyright years
   * Remove 0001-build-with-trimpath-for-reproducibility.patch
   * Adapt Debian packaging to the new Go reposurgeon
   * Include yet-to-be-packaged dependent Go libraries
   * Disable webfonts in Asciidoctor-generated HTML files
 (Lintian warning "reposurgeon: privacy-breach-generic")
Checksums-Sha1:
 0fa48f9e396e5f4a7d3afc697e629ede6bf96343 2148 reposurgeon_4.2-1.dsc
 c7787c75fa4770c56e0ec534bc9550f48390ee57 716356 reposurgeon_4.2.orig.tar.xz
 e6c4d8aa1d7294db6d934897568eb891eee61a10 78212 reposurgeon_4.2-1.debian.tar.xz
 5447df899fe4aa27ff6f0a3c9c013a5da50f 8905 reposurgeon_4.2-1_amd64.buildinfo
Checksums-Sha256:
 d356ca8cd01bcdce3414096b115424f245afb25f95708b75f6aeb951843f11e7 2148 
reposurgeon_4.2-1.dsc
 682b8cc9c8215200fbc2e815b36bed738b8483e4ed4599ad5d2383b7a0b088df 716356 
reposurgeon_4.2.orig.tar.xz
 c782cdeb0811e462562e150055b9c64b7383461c7ecacba7d36dd910aab13931 78212 
reposurgeon_4.2-1.debian.tar.xz
 c483f4a9fbbe0e9bf4c32eb44062e64bf261b4f9437132cd8e44010f44f84969 8905 
reposurgeon_4.2-1_amd64.buildinfo
Files:
 19f57b3818a6b1c87f306b4f43b0f5e6 2148 vcs optional reposurgeon_4.2-1.dsc
 78ecf9f04ae0e892e4b358b0a046e728 716356 vcs optional 
reposurgeon_4.2.orig.tar.xz
 4f8e88516e6d0b0c74df8f610d3309ed 78212 vcs optional 
reposurgeon_4.2-1.debian.tar.xz
 a23ba560156930a8205748a784b8b196 8905 vcs optional 
reposurgeon_4.2-1_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEEFCQhsZrUqVmW+VBy6iUAtBLFms8FAl5FsssACgkQ6iUAtBLF
ms8F9BAAoO3/p9wzJ/YHE5Mo33l+TzhiYblIp/kqOzn+u5zav0nZ8u7xDDSHEbPz
uKWkrWR/xVhARJOcX3ftCikL++URwxQTJ+KNLXWgn4o4iewt+VeA64TnojE3iQkK
70ipc7FaQ7rk9klxuGqbWUJDpIUeXjnIhWMCOeDoYsmgYuwfXD8s545k5zfxNetI
VDBw72yR7+eQQbvsTDUPSIuqcftwLPRNzsJTud7VkEYEObSw2CKQUzBTNFLUKhsA
9pZZ/gSBSDN7f7CiTSWt/i93Liiwddlv/ZbV9FYHIrmheE9uQ9YRkWigTtqC2SEe
0eXWmMxPkgFLlbkStMu4o8Qo8oEatWUDHUrHd3s0qb6pBzZi54qTkTo7/DVZyxWS
R1WMW/vFhTVOxs9YalFngvJM5nm4I1aivrDRjeVd3nK4pvFYeuDdqed+I1yumNgV
0HvUAwcyeT7NRzgjsWnMskqp2TdWGMEqU+xeZXgX4Hd/17obiXKDMMs5gn+5fFaw
FQPwqLnM8tOHPYab7Iv1mAkHEyV0yzV5SKZv9BloAwcwqMx5t3tA4BUrxnh7pVaJ
81ax9UScI4sGrCqgSua8xzeEf342YoHQduydNeFMYvynjZB4Cb4cE9zMowKUjJn4
pCNdYc+UveoasWBofAKKIW7Uc+9AaTQx4XJbq8G/Scck/5BfCCE=
=a90U
-END PGP SIGNATURE End Message ---

Bug#874870: Version 2.x is qt5-based

[Simon McVittie]

On Fri, 14 Feb 2020 at 17:48:53 -0500, Boyuan Yang wrote:
> I will seek for the switch back to /usr/games/ surely but that means patches
> onto the build system. Luckily doomsday 2.x is using CMake with
> GNUInstallDirs, which means pretty standard way of handling this issue.

You can probably just configure with -DCMAKE_INSTALL_BINDIR=games,
like lugaru does.

smcv

Bug#874870: Version 2.x is qt5-based

[Boyuan Yang]

Hi Markus,

在 2020-02-14五的 23:33 +0100，Markus Koschany写道：
> Hi,
> 
> Am 14.02.20 um 23:12 schrieb Boyuan Yang:
> [...]
> > Since the complete removal of Qt4 is just around the corner, I am
> > proposing to
> > do the following work to keep doomsday in Debian's development repository:
> > 
> > * A Team-upload onto experimental of v2.2.2 with Qt5 support,
> > * NO support for /usr/games/ (why do we still force such path when it's
> > already 2020?),
> > * NO support for the alternatives system of /usr/games/doom,
> > * Dropping all Debian-specific patches (will review later),
> > * NO complete review of copyright information (know fixable issues, see
> > changelog)
> > 
> > ...and I may solve those issues later and have the 2.x version back into
> > Sid/Testing.
> > 
> > The git packaging repo is here: 
> > https://salsa.debian.org/games-team/doomsday .
> > If I did not upload on time, someone else can continue with the packaging
> > work.
> 
> Thanks for working on doomsday. I just wanted to chime in and say that
> anything is better than just a removal but you should be aware of that
> installing the binary into /usr/games is a Debian Policy requirement and
> not something specific to doomsday. Everything else is up-to the person
> who actually works on the package.

Thanks for the heads up. I noticed the related words in §11.11 of Debian
Policy stating that binaries of games *should* be installed in the directory
/usr/games according to the FHS. Actually FHS 3.0 only listed the use of
/usr/games/ as "Optional". However, lintian is emitting an Error for this. I'd
consider it to be a bug but not a RC bug.

I will seek for the switch back to /usr/games/ surely but that means patches
onto the build system. Luckily doomsday 2.x is using CMake with
GNUInstallDirs, which means pretty standard way of handling this issue.

-- 
Thanks,
Boyuan Yang


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

Bug#874870: Version 2.x is qt5-based

[Markus Koschany]

Hi,

Am 14.02.20 um 23:12 schrieb Boyuan Yang:
[...]
> Since the complete removal of Qt4 is just around the corner, I am proposing to
> do the following work to keep doomsday in Debian's development repository:
> 
> * A Team-upload onto experimental of v2.2.2 with Qt5 support,
> * NO support for /usr/games/ (why do we still force such path when it's
> already 2020?),
> * NO support for the alternatives system of /usr/games/doom,
> * Dropping all Debian-specific patches (will review later),
> * NO complete review of copyright information (know fixable issues, see
> changelog)
> 
> ...and I may solve those issues later and have the 2.x version back into
> Sid/Testing.
> 
> The git packaging repo is here: https://salsa.debian.org/games-team/doomsday .
> If I did not upload on time, someone else can continue with the packaging
> work.

Thanks for working on doomsday. I just wanted to chime in and say that
anything is better than just a removal but you should be aware of that
installing the binary into /usr/games is a Debian Policy requirement and
not something specific to doomsday. Everything else is up-to the person
who actually works on the package.

Regards,

Markus



signature.asc
Description: OpenPGP digital signature

Bug#874870: Version 2.x is qt5-based

[Boyuan Yang]

X-Debbugs-CC: a...@debian.org mgilb...@debian.org

Hi all,

(see bottom)

On Tue, 1 Oct 2019 19:42:50 +0200 Markus Koschany  wrote:
> Hello,
> 
> Am 29.09.19 um 22:38 schrieb Moritz Mühlenhoff:
> > On Sun, Mar 18, 2018 at 09:11:24PM -0300, Lisandro Damián Nicanor Pérez
Meyer wrote:
> >> Hi! Version 2.x is qt5-based. Please check if you can update this game.
Feel 
> >> free to ask for help with Qt5 if needed.
> > 
> > It's been 1.5 years and we're now moving forward with the Qt4 removal. The
package
> > hasn't been uploaded since 2017, does anyone plan to update in the next
weeks,
> > otherwise it'll be removed along with Qt4.
> > 
> > Cheers,
> > Moritz
> 
> I consider Michael Gilbert as the one who is responsible to reply to
> this issue because he is the initial uploader of doomsday. I have only
> fixed release critical bugs before to keep the package in Debian.
> Doomsday is an active project but I don't intend to maintain it alone. I
> suggest to keep it in unstable to give others the chance to work on the
> existing bugs even if Qt4 should have been removed from Debian. If there
> is no activity before we intend to release Debian 11, then I have
> absolute no objections to remove this package from Debian.


Since the complete removal of Qt4 is just around the corner, I am proposing to
do the following work to keep doomsday in Debian's development repository:

* A Team-upload onto experimental of v2.2.2 with Qt5 support,
* NO support for /usr/games/ (why do we still force such path when it's
already 2020?),
* NO support for the alternatives system of /usr/games/doom,
* Dropping all Debian-specific patches (will review later),
* NO complete review of copyright information (know fixable issues, see
changelog)

...and I may solve those issues later and have the 2.x version back into
Sid/Testing.

The git packaging repo is here: https://salsa.debian.org/games-team/doomsday .
If I did not upload on time, someone else can continue with the packaging
work.

Michael: I haven't seen your packaging with doomsday in the last 4 years. Are
you still going to work on doomsday 2.x in future? If not, please let me know
so that the maintenance status can be properly reflected both in the package
metadata and on the website.


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

Processed: py2removal bugs severity updates - 2020-02-14 21:35:10.118569+00:00

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> # This is an automated script, part of the effort for the removal of Python 2 
> from bullseye
> #  * https://wiki.debian.org/Python/2Removal
> #  * http://sandrotosi.me/debian/py2removal/index.html
> # See https://lists.debian.org/debian-devel-announce/2019/11/msg0.html
> # and https://lists.debian.org/debian-python/2019/12/msg00076.html
> # mail threads for more details on this severity update
> # python-cwiid is a module and has 0 external rdeps or not in testing
> severity 942981 serious
Bug #942981 [src:cwiid] cwiid: Python2 removal in sid/bullseye
Bug #936358 [src:cwiid] cwiid: Python2 removal in sid/bullseye
Severity set to 'serious' from 'important'
Severity set to 'serious' from 'important'
>
End of message, stopping processing here.

Please contact me if you need assistance.
-- 
936358: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=936358
942981: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=942981
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Processed: severity of 936358 is important

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> severity 936358 important
Bug #936358 [src:cwiid] cwiid: Python2 removal in sid/bullseye
Bug #942981 [src:cwiid] cwiid: Python2 removal in sid/bullseye
Severity set to 'important' from 'serious'
Severity set to 'important' from 'serious'
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
936358: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=936358
942981: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=942981
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#950937: marked as done (hw-probe: FTBFS due to missing build dependency help2man)

[Debian Bug Tracking System]

Your message dated Fri, 14 Feb 2020 20:38:13 +
with message-id 
and subject line Bug#950937: fixed in hw-probe 1.4-2
has caused the Debian Bug report #950937,
regarding hw-probe: FTBFS due to missing build dependency help2man
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
950937: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=950937
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---

Package: hw-probe
Version: 1.4-1
Severity: serious
Tags: ftbfs

Dear Maintainer,

hw-probe currently fails to build with the following error message:
   debian/rules override_dh_installdocs
make[1]: Entering directory '/build/hw-probe-1.4'
help2man --include=debian/hw-probe.1.in --output=debian/hw-probe.1 
--no-info debian/hw-probe/usr/bin/hw-probe

make[1]: help2man: Command not found

After adding help2man to the list of build dependencies, it built 
successfully.



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

Kernel: Linux 5.4.0-3-amd64 (SMP w/3 CPU cores)
Locale: LANG=en_US.utf8, LC_CTYPE=en_US.utf8 (charmap=UTF-8), 
LANGUAGE=en_US:en (charmap=UTF-8)

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

Versions of packages hw-probe depends on:
pn  acpica-tools   
pn  curl   
ii  dmidecode  3.2-3
ii  hdparm 9.58+ds-4
pn  hwinfo 
ii  libwww-perl6.43-1
ii  lm-sensors 1:3.6.0-2
ii  lsb-release11.1.0
ii  mesa-utils 8.4.0-1+b1
ii  pciutils   1:3.6.4-1
ii  perl [libdigest-sha-perl]  5.30.0-9
ii  perl-base  5.30.0-9
pn  smartmontools  
ii  usbutils   1:012-2
ii  x11-utils  7.7+4

Versions of packages hw-probe recommends:
ii  alsa-utils 1.2.1-1
pn  cpuid  
pn  edid-decode
pn  ethtool
ii  fdisk  2.34-0.1
pn  i2c-tools  
ii  iw 5.4-1
pn  mcelog 
pn  memtester  
pn  pnputils   
pn  sysstat
ii  upower 0.99.11-1
pn  vainfo 
pn  vdpauinfo  
pn  vulkan-utils   
ii  wireless-tools 30~pre9-13+b1
ii  x11-xserver-utils  7.7+8
pn  xinput 

hw-probe suggests no packages.


--
mvh / best regards
Hans Joachim Desserud
http://desserud.org
--- End Message ---
--- Begin Message ---
Source: hw-probe
Source-Version: 1.4-2

We believe that the bug you reported is fixed in the latest version of
hw-probe, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 950...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Mathieu Malaterre  (supplier of updated hw-probe package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Fri, 14 Feb 2020 21:00:27 +0100
Source: hw-probe
Architecture: source
Version: 1.4-2
Distribution: unstable
Urgency: medium
Maintainer: Mathieu Malaterre 
Changed-By: Mathieu Malaterre 
Closes: 950937
Changes:
 hw-probe (1.4-2) unstable; urgency=medium
 .
   * Add missing build dependency. Closes: #950937
Checksums-Sha1:
 2e4c669937634e972b514ffad748fcebebcfbe10 1737 hw-probe_1.4-2.dsc
 e42552b7d044c11901bc32ed0461e439c00c6673 2440 hw-probe_1.4-2.debian.tar.xz
 1b1bb3f8a903beb2f1f293921e0580bf42133a18 6476 hw-probe_1.4-2_source.buildinfo
Checksums-Sha256:
 bfbf0cc2a0a6fc1ffa399892a84848214a966a2e32ef41b54a3e3524c85afb67 1737 
hw-probe_1.4-2.dsc
 e275b395313f67af1103cc485c04474ff416a534aaccce070e31b5fa9c82a9cd 2440 
hw-probe_1.4-2.debian.tar.xz
 dbf26ae92b53750df93de59416e86e36cc22bae06d13be53c0dd4254e914a532 6476 
hw-probe_1.4-2_source.buildinfo
Files:
 47c37a4f3b9acc3ddb414f1b7be36c1b 1737 utils optional hw-probe_1.4-2.dsc
 874e9b6f10021bef1bfc5ce852029b0f 2440 utils optional 
hw-probe_1.4-2.debian.tar.xz
 9100a3753d38f8ab069ef16e01da7801 6476 utils optional 
hw-probe_1.4-2_source.buildinfo

-BEGIN PGP SIGNATURE-

iQJFBAEBCgAvFiEEaTNn/67NjqrNHwY7AXHhgorgk0UFAl5G//URHG1hbGF0QGRl

Bug#888670: gnome-system-tools: has been unmaintained upstream for a long time

[Andreas Henriksson]

Control: reopen -1
Control: severity -1 important

Hello,

The new repository[1] that was supposedly fixing this bug report
doesn't even include the upstream sources (or their git history).
It's a plain packaging repo with only the debian/ directory.
I don't see how that's supposed to fulfil the need for you to
become your own uptream. You most likely want to create a fork
from the archived gnome repo[2].

Also please pick a (new) name for your fork as it's *not* THE
gnome-system-tools (anymore), unless you actually talk to the gnome
project to officially pick up as the gnome maintainer (but I suspect
at this point there's absolutely no interest from the gnome project to
have gnome-system-tools revived).

(Once a proper upstream fork exists, packaging that under the new name
and providing a transitional gnome-system-tools meta-package will give
current users a seemless upgrade experience.)

(Please also make sure to look into all the deprecated notices that is
being spit out during build. Those will likely become an issue in the
not too distant future. But first you might want to reconsider if you
really have the resources for taking on the task of becoming your own
upstream.)

Regards,
Andreas Henriksson

[1]: https://github.com/LStranger/gnome-system-tools-debian
[2]: https://gitlab.gnome.org/Archive/gnome-system-tools

Processed: Re: Bug#888670: gnome-system-tools: has been unmaintained upstream for a long time

[Debian Bug Tracking System]

Processing control commands:

> reopen -1
Bug #888670 {Done: Debian FTP Masters } 
[src:gnome-system-tools] gnome-system-tools: has been unmaintained upstream for 
a long time
'reopen' may be inappropriate when a bug has been closed with a version;
all fixed versions will be cleared, and you may need to re-add them.
Bug reopened
No longer marked as fixed in versions gnome-system-tools/3.0.0-9.
> severity -1 important
Bug #888670 [src:gnome-system-tools] gnome-system-tools: has been unmaintained 
upstream for a long time
Severity set to 'important' from 'serious'

-- 
888670: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=888670
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#951338: libkeyutils1: rkhunter warns that libkeyutils.so.1.9 may contain a possible rootkit

[Axel Beckert]

Control: severity -1 normal

Hi,

Francesco Poli (wintermute) wrote:
> After upgrading
> 
>   [UPGRADE] libkeyutils1:amd64 1.6-6 -> 1.6.1-2
> 
> I get the following warning with
> 
>   # rkhunter --sk -c 
> 
> in /var/log/rkhunter.log:
> 
>   Info: Starting test name 'running_procs'
> Checking running processes for suspicious files [ Warning ]
>   Warning: The following processes are using suspicious files:
>Command: sshd
>  UID: 0PID: 7331
>  Pathname: /lib/x86_64-linux-gnu/libkeyutils.so.1.9
>  Possible Rootkit: Spam tool component
[...]
> Does libkeyutils1/1.6.1-2 ship a rootkit?

Likely not. I looked through the whole diff between 1.6 and 1.6.1. At
least nothing suspicious like obfuscated code.

> Or is it a false positive from rkhunter?

Likely, because what triggers this is not the content of the file, but
the filename itself:

From "git blame files/rkhunter" in
https://salsa.debian.org/pkg-security-team/rkhunter:

c459dfa4 (Francois Marier 2014-10-14 23:24:53 +1300  9958)  
 \[pdflush\]:IRC bot
eca1837f (Francois Marier 2017-07-01 20:33:17 -0700  9959)  
 libkeyutils.so.1.9:Spam tool component
eca1837f (Francois Marier 2017-07-01 20:33:17 -0700  9960)  
 .IptabLex:malware component

So it's solely the filename and it's in there since at least 2017.

And the change which triggered this warning is this commit:

commit 0f70f77491bb6976a2bf761224fec1a9cc6cfb87
Author: David Howells 
Date:   Wed May 29 23:37:15 2019 +0100

Add support for KEYCTL_MOVE

Signed-off-by: David Howells 

diff --git a/version.lds b/version.lds
index 9317222..9e78ea2 100644
--- a/version.lds
+++ b/version.lds
@@ -91,3 +91,9 @@ KEYUTILS_1.8 {
keyctl_pkey_verify;

 } KEYUTILS_1.7;
 +
 +KEYUTILS_1.9 {
 +   /* Management functions */
 +   keyctl_move;
 +
 +} KEYUTILS_1.8;

Doesn't look like a rootkit addition to me, just bumping the SONAME.
(And the adding of KEYCTL_MOVE neither.) Lowering the severity to
default ("normal")...

IMHO this is a bug in rkhunter, but it could also be solved in
keyutils by bumping the SONAME again, i.e. skipping this SONAME
version explicitly. But feel free to reassign.

Regards, Axel
-- 
 ,''`.  |  Axel Beckert , https://people.debian.org/~abe/
: :' :  |  Debian Developer, ftp.ch.debian.org Admin
`. `'   |  4096R: 2517 B724 C5F6 CA99 5329  6E61 2FF9 CD59 6126 16B5
  `-|  1024D: F067 EA27 26B9 C3FC 1486  202E C09E 1D89 9593 0EDE


signature.asc
Description: PGP signature

Processed: Re: Bug#951338: libkeyutils1: rkhunter warns that libkeyutils.so.1.9 may contain a possible rootkit

[Debian Bug Tracking System]

Processing control commands:

> severity -1 normal
Bug #951338 [libkeyutils1] libkeyutils1: rkhunter warns that libkeyutils.so.1.9 
may contain a possible rootkit
Severity set to 'normal' from 'grave'

-- 
951338: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=951338
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#947518: casparcg-server: FTBFS: xf86vmode library not found - required for GLFW

[Petter Reinholdtsen]

[Dimitri John Ledkov]
> Anyway, I hacked up something that works, albeit looks ugly.

Thank you very much.  I hope upstream will accept the fix or some
variant of it. :)

-- 
Happy hacking
Petter Reinholdtsen

Bug#951338: libkeyutils1: rkhunter warns that libkeyutils.so.1.9 may contain a possible rootkit

[Francesco Poli (wintermute)]

Package: libkeyutils1
Version: 1.6.1-2
Severity: grave
Tags: security
Justification: user security hole

Hello!

After upgrading

  [UPGRADE] libkeyutils1:amd64 1.6-6 -> 1.6.1-2

I get the following warning with

  # rkhunter --sk -c 

in /var/log/rkhunter.log:

  Info: Starting test name 'running_procs'
Checking running processes for suspicious files [ Warning ]
  Warning: The following processes are using suspicious files:
   Command: sshd
 UID: 0PID: 7331
 Pathname: /lib/x86_64-linux-gnu/libkeyutils.so.1.9
 Possible Rootkit: Spam tool component

I tried to reinstall libkeyutils1/1.6.1-2, after checking the SHA256
checksum of the .deb file. The warning was issued again.

On the other hand, after downgrading to libkeyutils1/1.6-6
and restarting ssh

  # service ssh restart

the warning vanishes.


Does libkeyutils1/1.6.1-2 ship a rootkit?
Or is it a false positive from rkhunter?

Please investigate.
Thanks for your time!



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

Kernel: Linux 5.4.0-3-amd64 (SMP w/4 CPU cores)
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 libkeyutils1 depends on:
ii  libc6  2.29-10

libkeyutils1 recommends no packages.

libkeyutils1 suggests no packages.

-- no debconf information

Bug#951139: Can someone please have a look (Was: Bug#951139: toil fails it's autopkg tests)

[Michael Crusoe]

I've uploaded new packages of toil, cwltool, and python-schema-salad that
should fix this

Bug#947518: casparcg-server: FTBFS: xf86vmode library not found - required for GLFW

[Dimitri John Ledkov]

On Fri, 27 Dec 2019 23:14:46 +0100 Andreas Beckmann  wrote:
> Package: casparcg-server
> Version: 2.2.0+dfsg-2
> Severity: serious
> Tags: ftbfs
> Justification: fails to build from source
>
> Hi,
>
> casparcg-server FTBFS in a current sid pbuilder environment:
>
> CMake Error at CMakeModules/FindGLFW.cmake:150 (message):
>   xf86vmode library not found - required for GLFW
> Call Stack (most recent call first):
>   CMakeModules/Bootstrap_Linux.cmake:44 (FIND_PACKAGE)
>   CMakeLists.txt:18 (INCLUDE)
>

What is odd however is that GLFW is not actually used or linked to the
final binaries, only a subset of X libraries are.

I've tried to clean it up a bit, but it seems to me that many cmake
stanzas are quite bogus. And for example, instead of including a
custom GLFW module, an upstream one could be used with
find_package(glfw3 REQUIRED) for example.

Anyway, I hacked up something that works, albeit looks ugly.

Regards,

Dimitri.

Bug#950072: marked as done (python-asttokens FTBFS with Python 3.8 as supported version)

[Debian Bug Tracking System]

Your message dated Fri, 14 Feb 2020 18:05:37 +
with message-id 
and subject line Bug#950072: fixed in python-asttokens 2.0.3-1
has caused the Debian Bug report #950072,
regarding python-asttokens FTBFS with Python 3.8 as supported version
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
950072: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=950072
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: python-asttokens
Version: 1.1.13-2
Severity: serious
Tags: ftbfs bullseye sid

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

...
==
ERROR: test_comprehensions (tests.test_astroid.TestAstroid)
--
Traceback (most recent call last):
  File 
"/build/1st/python-asttokens-1.1.13/.pybuild/cpython3_3.8_asttokens/build/tests/test_mark_tokens.py",
 line 369, in test_comprehensions
m = self.create_mark_checker(source)
  File 
"/build/1st/python-asttokens-1.1.13/.pybuild/cpython3_3.8_asttokens/build/tests/test_astroid.py",
 line 15, in create_mark_checker
return tools.MarkChecker(source, tree=tree)
  File 
"/build/1st/python-asttokens-1.1.13/.pybuild/cpython3_3.8_asttokens/build/tests/tools.py",
 line 82, in __init__
self.atok = asttokens.ASTTokens(source, parse=parse, tree=tree)
  File 
"/build/1st/python-asttokens-1.1.13/.pybuild/cpython3_3.8_asttokens/build/asttokens/asttokens.py",
 line 65, in __init__
self.mark_tokens(self._tree)
  File 
"/build/1st/python-asttokens-1.1.13/.pybuild/cpython3_3.8_asttokens/build/asttokens/asttokens.py",
 line 76, in mark_tokens
MarkTokens(self).visit_tree(root_node)
  File 
"/build/1st/python-asttokens-1.1.13/.pybuild/cpython3_3.8_asttokens/build/asttokens/mark_tokens.py",
 line 47, in visit_tree
util.visit_tree(node, self._visit_before_children, 
self._visit_after_children)
  File 
"/build/1st/python-asttokens-1.1.13/.pybuild/cpython3_3.8_asttokens/build/asttokens/util.py",
 line 184, in visit_tree
ret = postvisit(current, par_value, value)
  File 
"/build/1st/python-asttokens-1.1.13/.pybuild/cpython3_3.8_asttokens/build/asttokens/mark_tokens.py",
 line 90, in _visit_after_children
nfirst, nlast = self._methods.get(self, node.__class__)(node, first, last)
  File 
"/build/1st/python-asttokens-1.1.13/.pybuild/cpython3_3.8_asttokens/build/asttokens/mark_tokens.py",
 line 175, in visit_listcomp
return self.handle_comp('[', node, first_token, last_token)
  File 
"/build/1st/python-asttokens-1.1.13/.pybuild/cpython3_3.8_asttokens/build/asttokens/mark_tokens.py",
 line 171, in handle_comp
util.expect_token(before, token.OP, open_brace)
  File 
"/build/1st/python-asttokens-1.1.13/.pybuild/cpython3_3.8_asttokens/build/asttokens/util.py",
 line 56, in expect_token
raise ValueError("Expected token %s, got %s on line %s col %s" % (
ValueError: Expected token OP:'[', got ENDMARKER:'' on line 2 col 1
...
==
FAIL: test_walk_ast (tests.test_util.TestUtil)
--
Traceback (most recent call last):
  File 
"/build/1st/python-asttokens-1.1.13/.pybuild/cpython3_3.8_asttokens/build/tests/test_util.py",
 line 43, in test_walk_ast
self.assertEqual(scan, [
AssertionError: Lists differ: ["Mod[202 chars]2', 'Constant:1', 'Constant:2', 
"BinOp:'hello'[95 chars]ld'"] != ["Mod[202 chars]2', 'Num:1', 'Num:2', 
"BinOp:'hello' + ', ' + [70 chars]ld'"]

First differing element 7:
'Constant:1'
'Num:1'

  ["Module:foo(bar(1 + 2), 'hello' + ', ' + 'world')",
   "Expr:foo(bar(1 + 2), 'hello' + ', ' + 'world')",
   "Call:foo(bar(1 + 2), 'hello' + ', ' + 'world')",
   'Name:foo',
   'Call:bar(1 + 2)',
   'Name:bar',
   'BinOp:1 + 2',
-  'Constant:1',
-  'Constant:2',
+  'Num:1',
+  'Num:2',
   "BinOp:'hello' + ', ' + 'world'",
   "BinOp:'hello' + ', '",
-  "Constant:'hello'",
-  "Constant:', '",
-  "Constant:'world'"]
+  "Str:'hello'",
+  "Str:', '",
+  "Str:'world'"]

--
Ran 79 tests in 2.124s

FAILED (SKIP=1, errors=8, failures=11)
E: pybuild pybuild:341: test: plugin distutils failed with: exit code=1: cd 
/build/1st/python-asttokens-1.1.13/.pybuild/cpython3_3.8_asttokens/build; 
python3.8 -m nose -v tests
dh_auto_test: error: pybuild --test --test-nose -i python{version} -p "3.8 3.7" 
returned exit code 13
make: *** [debian/rules:6: build] Error 25
--- End Message ---

Bug#951306: snek: unsatisfiable b-d on picolibc-arm-none-eabi

[Keith Packard]

Ralf Treinen  writes:

> snek build-depends on picolibc-arm-none-eabi which does not exist (yet)
> in sid.

Yup. It's been stuck in the 'new' queue for several months now.

-- 
-keith


signature.asc
Description: PGP signature

Processed: Re: Bug#945442: Possible to backspace past beginning of string...

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> severity 945442 grave
Bug #945442 [neomutt] Possible to backspace past beginning of string, which 
appears to be identical to having pressed Enter immediately, without any 
backspace
Severity set to 'grave' from 'normal'
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
945442: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=945442
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Processed: py2removal bugs severity updates - 2020-02-14 15:35:18.567504+00:00

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> # This is an automated script, part of the effort for the removal of Python 2 
> from bullseye
> #  * https://wiki.debian.org/Python/2Removal
> #  * http://sandrotosi.me/debian/py2removal/index.html
> # See https://lists.debian.org/debian-devel-announce/2019/11/msg0.html
> # and https://lists.debian.org/debian-python/2019/12/msg00076.html
> # mail threads for more details on this severity update
> # mercurial-extension-utils is an application, has low popcon (87 < 300), and 
> has 0 external rdeps or not in testing
> severity 937011 serious
Bug #937011 [src:mercurial-extension-utils] mercurial-extension-utils: Python2 
removal in sid/bullseye
Severity set to 'serious' from 'normal'
>
End of message, stopping processing here.

Please contact me if you need assistance.
-- 
937011: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=937011
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Processed: Re: FTBFS: error: conflicting declaration ‘typedef long long unsigned int __u64’

[Debian Bug Tracking System]

Processing control commands:

> tags 950720 - patch + pending
Bug #950720 [wp2latex] FTBFS: error: conflicting declaration ‘typedef long long 
unsigned int __u64’
Removed tag(s) patch.
Bug #950720 [wp2latex] FTBFS: error: conflicting declaration ‘typedef long long 
unsigned int __u64’
Added tag(s) pending.

-- 
950720: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=950720
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#950720: FTBFS: error: conflicting declaration ‘typedef long long unsigned int __u64’

[Hilmar Preuße]

Control: tags 950720 - patch + pending

Am 05.02.2020 um 12:11 teilte Hilmar Preusse mit:

> the package FTBFS on s390x & arm64.
> 
> ./atoms/include/typedfs.h:73:14: note: previous declaration as ‘typedef long 
> int __s64’
>73 |  typedef int __s64 __attribute__((mode(DI)));
>   |  ^
> ./atoms/include/typedfs.h:77:16: error: conflicting declaration ‘typedef long 
> long unsigned int __u64’
>77 |  #define __u64 __u64
>   |^
> ./atoms/include/typedfs.h:74:23: note: previous declaration as ‘typedef long 
> unsigned int __u64’
>74 |  typedef unsigned int __u64 __attribute__((mode(DI)));
>   |   ^
> make[2]: *** [makefile:151: wp2latex.o] Error 1
> make[2]: Leaving directory '/<>/sources.cc'
> 
The issue is solved in upstreams repository, but there is no easy patch
I could apply. (Un)tagging.

H.
-- 
sigfault
#206401 http://counter.li.org



signature.asc
Description: OpenPGP digital signature

Bug#950638: marked as done (pykwalify FTBFS: TestCore.test_core_files failure)

[Debian Bug Tracking System]

Your message dated Fri, 14 Feb 2020 15:05:34 +
with message-id 
and subject line Bug#950638: fixed in pykwalify 1.7.0-3
has caused the Debian Bug report #950638,
regarding pykwalify FTBFS: TestCore.test_core_files failure
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
950638: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=950638
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: pykwalify
Version: 1.7.0-2
Severity: serious
Tags: ftbfs bullseye sid

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

...
=== FAILURES ===
___ TestCore.test_core_files ___
...
>   compare(sorted(c.validation_errors), sorted(errors), 
> prefix="Wrong validation errors when parsing files : {0} : {1} : {2}".format(
f, document_index, document.get('name', 'UNKNOWN')))
E   AssertionError: Wrong validation errors when parsing files 
: 
/build/1st/pykwalify-1.7.0/.pybuild/cpython3_3.8/build/tests/files/fail/test_type_float.yaml
 : 1 : fail-type-float-2: sequence not as expected:
E   
E   same:
E   []
E   
E   first:
E   ["Value 'True' is not of type 'float'. Path: '/1'",
E"Value 'foo' is not of type 'float'. Path: '/0'"]
E   
E   second:
E   ["Value 'foo' is not of type 'float'. Path: '/0'"]
E   
E   While comparing [0]: 
E   "Value 'True' is not of type 'float'. Path: '/1'"
E   !=
E   "Value 'foo' is not of type 'float'. Path: '/0'"

tests/test_core.py:571: AssertionError
...
--- End Message ---
--- Begin Message ---
Source: pykwalify
Source-Version: 1.7.0-3

We believe that the bug you reported is fixed in the latest version of
pykwalify, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 950...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Andrej Shadura  (supplier of updated pykwalify package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Fri, 14 Feb 2020 15:11:40 +0100
Source: pykwalify
Architecture: source
Version: 1.7.0-3
Distribution: unstable
Urgency: medium
Maintainer: Debian Python Modules Team 

Changed-By: Andrej Shadura 
Closes: 950638
Changes:
 pykwalify (1.7.0-3) unstable; urgency=medium
 .
   [ Ondřej Nový ]
   * Use debhelper-compat instead of debian/compat.
 .
   [ Johan Fleury ]
   * Import upstream patch to fix tests suite (Closes: #950638):
 - Fix broken test where errors data was wrong and duplicated.
 .
   [ Andrej Shadura ]
   * Bump debhelper from old 11 to 12.
   * Bump Standards-Version to 4.5.0 (no changes).
Checksums-Sha1:
 5845c6d01dc71a4ec5be36e8999464234b01cae3 1916 pykwalify_1.7.0-3.dsc
 238aec3d6c51805fd9da481b915619df46e9c790 2936 pykwalify_1.7.0-3.debian.tar.xz
Checksums-Sha256:
 df71b47979dd3a629ae282d0479e469b845f2d283795f2f035fe54daaf4c7ce3 1916 
pykwalify_1.7.0-3.dsc
 335591502b02ecd1d2da1bb772c2eb53ca55e653d139c38cd1e9d2f2b8247237 2936 
pykwalify_1.7.0-3.debian.tar.xz
Files:
 785ce2c684c67230de83ed83637a38dd 1916 python optional pykwalify_1.7.0-3.dsc
 1b1581328fb7e1d37ff60fa8e86ac82d 2936 python optional 
pykwalify_1.7.0-3.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQEzBAEBCAAdFiEEeuS9ZL8A0js0NGiOXkCM2RzYOdIFAl5GqsQACgkQXkCM2RzY
OdKIKQf+IU2ztEzqiayMM1WHVAEWTzqhdk8mzoLE/T5A2GhgSbn/rbeujgPTQOU5
f7htCIE08+Ig4pRNqxVsecinUJlmZ7ZCOo6KR0zSg4bgrGRKyiYpFdNLqaIQm2sC
06TLlBmZ1rWoSmocJ1akaFlp8gwxQ6ZIw2BT3XxyENLMoTPTlKSgjFKaiMQFdf8M
yJcC1dm8uQhPx339WfWTZyrqj6u2O8CyT+rTfbGXkUGrdq8oUEScdjbXoGq538X/
RnkTs6//XLwFEHURDs5sojhvmiEbrkT0DseHH1/rNaLnXJYTsV06T2G2bWYVXrMy
t0e1rAoa+7+YPEds9nX0nsfpkDsy4g==
=pwce
-END PGP SIGNATURE End Message ---

Bug#951329: FTBFS in buster with linux-source-4.19 4.19.98-1

[Santiago R.R.]

Package: user-mode-linux
Version: 4.19-1um-1
Severity: serious
Tags: patch

Dear maintainer,

The current user-mode-linux package in buster fails to build the latest
linux kernel in buster due to the fix-port-helper-path.patch:

Applying patch 
/build/user-mode-linux-4.19-1um/debian/patches/fix-port-helper-path.patch
patching file arch/um/drivers/port_user.c
Hunk #1 FAILED at 168.
1 out of 1 hunk FAILED -- rejects in file arch/um/drivers/port_user.c
Patch /build/user-mode-linux-4.19-1um/debian/patches/fix-port-helper-path.patch 
can be reverse-applied
make: *** [debian/rules:54: patch-stamp] Error 1
dpkg-buildpackage: error: debian/rules build subprocess returned exit status 2
I: copying local configuration
E: Failed autobuilding of package

Removing it solves the issue:

diff --git a/debian/patches/series b/debian/patches/series
index 5f98481..29faa0f 100644
--- a/debian/patches/series
+++ b/debian/patches/series
@@ -3,4 +3,3 @@
 05_fix_static_build.patch
 06-fix-linkage-on-386-arch.patch
 07-remove-rpath.patch
-fix-port-helper-path.patch

BTW, I will prepare a git branch in my personal salsa namespace. But I
am not sure against which branch should I propose a MR.

Cheers,

 -- Santiago


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

Kernel: Linux 5.4.0-3-amd64 (SMP w/8 CPU cores)
Kernel taint flags: TAINT_WARN, TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE
Locale: LANG=es_CO.UTF-8, LC_CTYPE=es_CO.UTF-8 (charmap=UTF-8), 
LANGUAGE=es_CO.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 user-mode-linux depends on:
ii  libc6  2.29-10

Versions of packages user-mode-linux recommends:
ii  uml-utilities  20070815.3-1

Versions of packages user-mode-linux suggests:
ii  rootstrap 0.3.25-1
ii  rxvt-unicode [x-terminal-emulator]9.22-6+b2
pn  slirp 
ii  terminator [x-terminal-emulator]  1.91-4
ii  user-mode-linux-doc   20060501-3
pn  vde2  
ii  xfce4-terminal [x-terminal-emulator]  0.8.9.1-1
ii  xterm [x-terminal-emulator]   353-1

-- no debconf information

Bug#951305: r-cran-rockchalk: unsatisfiable build-dependency on r-cran-kutils

[Andreas Tille]

Hi Ralf,

I would have bet I have uploaded r-cran-kutils together with
r-cran-rockchalk to new - but it does not seem to be the case.

@Thorsten:  If you have time could you please have a look at the
just uploaded r-cran-kutils?

Thanks a lot

  Andreas.

On Fri, Feb 14, 2020 at 08:57:41AM +0100, Ralf Treinen wrote:
> Source: r-cran-rockchalk
> Version: 1.8.144+dfsg-1
> Severity: serious
> User: trei...@debian.org
> Usertags: edos-uninstallable
> 
> Hi,
> 
> r-cran-rockchalk build-depends on r-cran-kutils which does not exist in
> sid.
> 
> -Ralf
> 
> ___
> R-pkg-team mailing list
> r-pkg-t...@alioth-lists.debian.net
> https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/r-pkg-team

-- 
http://fam-tille.de

Bug#947296: mercurial-keyring: Python2 removal in sid/bullseye

[Andrej Shadura]

On Thu, 30 Jan 2020 12:08:33 +0300 Dmitry Shachnev 
wrote:
> setuptools-scm has removed Python 2 support (see #938470), so python-keyring
> build-dependencies are no longer satisfiable.

It has since been reintroduced.

> Thus I am going to remove Python 2 support from python-keyring, so I am
> bumping severity of this bug. That support will be removed in 10 days from
> now, on some day after 2020-02-09.
> 
> I am also CCing the maintainers of packages which are listed as blockers of
> this bug (mercurial and mercurial-extension-utils).

Well, it would break this package, so you need to wait until Mercurial
switches to Python 3.

-- 
Cheers,
  Andrej

Bug#951139: marked as done (toil fails it's autopkg tests)

[Debian Bug Tracking System]

Your message dated Fri, 14 Feb 2020 13:05:40 +
with message-id 
and subject line Bug#951139: fixed in toil 3.24.0-1
has caused the Debian Bug report #951139,
regarding toil fails it's autopkg tests
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
951139: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=951139
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:toil
Version: 3.23.1-1
Severity: serious
Tags: sid bullseye

seen in https://ci.debian.net/packages/t/toil
toil fails it's autopkg tests

[...]
autopkgtest [19:11:47]: test smoke-test: [---
Traceback (most recent call last):
  File "/usr/bin/toil", line 11, in 
load_entry_point('toil==3.18.0', 'console_scripts', 'toil')()
  File "/usr/lib/python3/dist-packages/toil/utils/toilMain.py", line 13, in main
modules = loadModules()
  File "/usr/lib/python3/dist-packages/toil/utils/toilMain.py", line 39, in
loadModules
from toil.utils import (toilKill,
  File "/usr/lib/python3/dist-packages/toil/utils/toilStatus.py", line 34, in

from toil.jobStores.abstractJobStore import NoSuchJobStoreException,
NoSuchFileException
  File "/usr/lib/python3/dist-packages/toil/jobStores/abstractJobStore.py", line
39, in 
from toil.job import JobException
  File "/usr/lib/python3/dist-packages/toil/job.py", line 51, in 
from toil.deferred import DeferredFunction
  File "/usr/lib/python3/dist-packages/toil/deferred.py", line 34, in 
from toil.resource import ModuleDescriptor
  File "/usr/lib/python3/dist-packages/toil/resource.py", line 43, in 
from toil.version import exactPython
ImportError: cannot import name 'exactPython' from 'toil.version'
(/usr/lib/python3/dist-packages/toil/version.py)
autopkgtest [19:11:48]: test smoke-test: ---]
autopkgtest [19:11:48]: test smoke-test:  - - - - - - - - - - results - - - - -
- - - - -
smoke-test   FAIL non-zero exit status 1
autopkgtest [19:11:48]: test smoke-test:  - - - - - - - - - - stderr - - - - - -
- - - -
Traceback (most recent call last):
  File "/usr/bin/toil", line 11, in 
load_entry_point('toil==3.18.0', 'console_scripts', 'toil')()
  File "/usr/lib/python3/dist-packages/toil/utils/toilMain.py", line 13, in main
modules = loadModules()
  File "/usr/lib/python3/dist-packages/toil/utils/toilMain.py", line 39, in
loadModules
from toil.utils import (toilKill,
  File "/usr/lib/python3/dist-packages/toil/utils/toilStatus.py", line 34, in

from toil.jobStores.abstractJobStore import NoSuchJobStoreException,
NoSuchFileException
  File "/usr/lib/python3/dist-packages/toil/jobStores/abstractJobStore.py", line
39, in 
from toil.job import JobException
  File "/usr/lib/python3/dist-packages/toil/job.py", line 51, in 
from toil.deferred import DeferredFunction
  File "/usr/lib/python3/dist-packages/toil/deferred.py", line 34, in 
from toil.resource import ModuleDescriptor
  File "/usr/lib/python3/dist-packages/toil/resource.py", line 43, in 
from toil.version import exactPython
ImportError: cannot import name 'exactPython' from 'toil.version'
(/usr/lib/python3/dist-packages/toil/version.py)
autopkgtest [19:11:48]:  summary
smoke-test   FAIL non-zero exit status 1
--- End Message ---
--- Begin Message ---
Source: toil
Source-Version: 3.24.0-1

We believe that the bug you reported is fixed in the latest version of
toil, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 951...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Michael R. Crusoe  (supplier of updated toil package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Fri, 14 Feb 2020 13:41:12 +0100
Source: toil
Architecture: source
Version: 3.24.0-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Med Packaging Team 

Changed-By: Michael R. Crusoe 
Closes: 951139
Changes:
 toil (3.24.0-1) unstable; urgency=medium
 .
   * New upstream version
   * refresh debian/patches/settings_version.patch from pypi sdist (must be
 done with every new upstream release!)
   * Allow the newer schema salad package (Closes: #951139)

Bug#951312: networking: unsetting ipv6 brings many problems

[Cosimo Simeone]

Package: networking
Severity: grave
Justification: causes non-serious data loss

Dear Maintainer,

   * What led up to the situation? lost of networking, caused by dhcp not 
renewing IP address
   * What exactly did you do (or not do) that was effective (or
 ineffective)? disabled ipv6
   * What was the outcome of this action? dhcp 3442 non zero exit error
   * What outcome did you expect instead? well... Networking to work :-)

Longer description:
unsetting ipv6 (/etc/sysctl.conf -> net.ipv6.conf.all.disable_ipv6 = 0 
net.ipv6.conf.default.disable_ipv6 = 0 net.ipv6.conf.lo.disable_ipv6 = 0) 
generates dhcp 3442 non zero error. Disabling 3442 (dhclient.conf, removing 
request rfc3442-classless-static-routes) raises RTNETLINK answers: Permission 
denied


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

Kernel: Linux 4.19.0-8-amd64 (SMP w/1 CPU core)
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_GB.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)

Bug#936806: koji: Python2 removal in sid/bullseye

[Thomas Goirand]

On 2/14/20 2:30 AM, Holger Levsen wrote:
> On Thu, Feb 13, 2020 at 08:14:11PM -0500, Sandro Tosi wrote:
>> thanks! I'm gonna go ahead and file an RM bug for the following pkgs
>> too: yum createrepo python-lzma yum-metadata-parser mock yum-utils
>> dtc-xen deltarpm
>>
>> they are a closed set
> 
> thank you for cleaning up after all of us, now that we reached containers.
> (which used to be called virtualisation mainframes before... ;) 
> 
> I mean, rpm is definitly still useful to have on Debian, but yum and 
> friends???

I am the one that maintained yum for about a decade in Debian. Yum is
(was?) useful because it does the same thing as debootstrap. Ie: with
it, you can bootstrap a CentOS chroot from a Debian host, which may be
useful for example if using Xen (or other virtualization systems). That
was in fact my use case.

Anyway, yum is kind of dead, as distros have been moving to dnf. I see
therefore no reason to keep it.

Cheers,

Thomas Goirand (zigo)

Bug#949834: (no subject)

[pioruns]

Cant' reproduce, I was using 68.4.1esr-1~deb10u1, today I upgraded to
68.5.0esr-1~deb10u1, everything works fine.

System is Debian Buster 10 on AMD64.

Bug#951306: snek: unsatisfiable b-d on picolibc-arm-none-eabi

[Ralf Treinen]

Source: snek
Version: 1.3-1
Severity: serious
User: trei...@debian.org
Usertags: edos-uninstallable

Hi,

snek build-depends on picolibc-arm-none-eabi which does not exist (yet)
in sid.

-Ralf.

Bug#951305: r-cran-rockchalk: unsatisfiable build-dependency on r-cran-kutils

[Ralf Treinen]

Source: r-cran-rockchalk
Version: 1.8.144+dfsg-1
Severity: serious
User: trei...@debian.org
Usertags: edos-uninstallable

Hi,

r-cran-rockchalk build-depends on r-cran-kutils which does not exist in
sid.

-Ralf