Bug#944277: FTBFS with OCaml 4.08.1 (Error while running external preprocessor)

[Stéphane Glondu]

Package: src:hol-light
Version: 20190729-2
Severity: serious
Tags: ftbfs
User: debian-ocaml-ma...@lists.debian.org
Usertags: ocaml-4.08-transition

Dear Maintainer,

hol-light FTBFS with OCaml 4.08.1 because of an error while running
external preprocessor:

  https://buildd.debian.org/status/package.php?p=hol-light


Cheers,

-- 
Stéphane

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

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

Bug#944276: FTBFS with OCaml 4.08.1 (safe strings)

[Stéphane Glondu]

Package: src:camlpdf
Version: 2.2.1-1
Severity: serious
Tags: ftbfs
User: debian-ocaml-ma...@lists.debian.org
Usertags: ocaml-4.08-transition

Dear Maintainer,

camlpdf FTBFS with OCaml 4.08.1 because -safe-string is now the default:

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


Cheers,

-- 
Stéphane


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

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

Bug#939963: Problems compiling orpie with ocaml 4.08

[Uwe Steinmann]

Adding the dependency on libnum was easy, but orpie doesn't compile
with ocaml 4.08 anymore. I need to talk to upstream ...


signature.asc
Description: PGP signature

Bug#943583: sysv-rc: information from the Policy Manual for README.runlevels

[Sean Whitton]

Dear Dmitry,

On Sun 03 Nov 2019 at 04:55AM +00, Dmitry Bogatov wrote:

> Then it means that I did not update d/copyright in src:sysvinit, and it
> was right thing to do. Or am I missing any other consequence?

I was expecting that the maintainers of sysv-rc would determine how to
update sysv-rc's d/copyright in light of the change -- I was just
providing the information I had, without thinking I could answer the
question for you.  Sorry if that was unclear.

-- 
Sean Whitton


signature.asc
Description: PGP signature

Bug#941198: initscripts: packages should ship systemd units

[Sean Whitton]

Hello,

On Sun 03 Nov 2019 at 01:04PM -08, Russ Allbery wrote:

> --- a/policy/ch-opersys.rst
> +++ b/policy/ch-opersys.rst
> @@ -388,11 +388,14 @@ argument ``stop``.
>  Writing the scripts
>  ~~~
>
> -Packages that include daemons for system services should place scripts
> -in ``/etc/init.d`` to start or stop services at boot time or during a
> -change of runlevel. These scripts should be named
> -``/etc/init.d/package``, and they should accept one argument, saying
> -what to do:
> +Packages that include system services should include ``systemd`` service
> +units to start or stop those services.  See :manpage:`systemd.service(5)`.
> +
> +To support other init systems, packages that include daemons for system
> +services should place scripts in ``/etc/init.d`` to start or stop those
> +services at boot time or during a change of runlevel. These scripts should
> +be named ``/etc/init.d/package``, and they should accept one argument,
> +saying what to do:
>
>  ``start``
>  start the service,

Seconded.

-- 
Sean Whitton


signature.asc
Description: PGP signature

Bug#944275: hollywood: Contains copyright video

[Roger]

Package: hollywood
Version: 1.14-1.1
Severity: normal

Dear Maintainer,

Package installs a video file called mi.mp4 in /usr/share/hollywood/ . This 
seems to be identical to the version used in soundtrack to Mission Impossible 
movie with Tom Cruise which is under copyright and violates DFSG.
The video file is also present in hollywood version 1.18-1 currently in testing 
and unstable.

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

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

Versions of packages hollywood depends on:
ii  byobu  5.112-1.1
ii  tmux   2.8-3

Versions of packages hollywood recommends:
ii  apg 2.2.3.dfsg.1-5
ii  bmon1:4.0-5
ii  bsdmainutils11.1.2+b1
ii  ccze0.2.1-4+b1
ii  cmatrix 1.2a+git20181122-1
ii  htop2.2.0-1+b1
ii  jp2a1.0.6-8
ii  mlocate 0.26-3
ii  moreutils   0.62-1
ii  openssh-client  1:7.9p1-10+deb10u1
ii  speedometer 2.8-2
ii  tree1.8.0-1

Versions of packages hollywood suggests:
pn  mplayer  

-- no debconf information

Bug#944274: subtitlecomposer talks of subpicture/x-pgs as an invalid mimetype

[shirish शिरीष]

Package: subtitlecomposer
Version: 0.7.0-1
Severity: normal

Dear Maintainer,
I was updating/upgrading my desktop when I saw the following error
while updating the same.

Error in file "/usr/share/applications/subtitlecomposer.desktop":
"subpicture/x-pgs" is an invalid MIME type ("subpicture" is an
unregistered media type) . While I'm not sure it perhaps might be
possible that xdg-desktop-portal may be involved as that was one of
the packages which was updated.

Please let me know if you need any more info.

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

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

Versions of packages subtitlecomposer depends on:
ii  kio 5.62.1-2
ii  libavcodec587:4.2.1-2
ii  libavformat58   7:4.2.1-2
ii  libavutil56 7:4.2.1-2
ii  libc6   2.29-2
ii  libgcc1 1:9.2.1-17
ii  libglib2.0-02.62.2-2
ii  libgstreamer-plugins-base1.0-0  1.16.1-1
ii  libgstreamer1.0-0   1.16.1-1
ii  libicu6363.2-2
ii  libkf5codecs5   5.62.0-1
ii  libkf5completion5   5.62.0-1
ii  libkf5configcore5   5.62.0-1
ii  libkf5configgui55.62.0-1
ii  libkf5configwidgets55.62.0-1
ii  libkf5coreaddons5   5.62.0-1
ii  libkf5i18n5 5.62.0-1
ii  libkf5kiocore5  5.62.1-2
ii  libkf5kiofilewidgets5   5.62.1-2
ii  libkf5kiowidgets5   5.62.1-2
ii  libkf5krosscore55.62.0-1
ii  libkf5sonnetcore5   5.62.0-1
ii  libkf5sonnetui5 5.62.0-1
ii  libkf5textwidgets5  5.62.0-1
ii  libkf5widgetsaddons55.62.0-1
ii  libkf5xmlgui5   5.62.0-1+b1
ii  libmpv1 0.29.1-1
ii  libphonon4qt5-4 4:4.10.3-3
ii  libqt5core5a5.12.5+dfsg-2
ii  libqt5gui5  5.12.5+dfsg-2
ii  libqt5widgets5  5.12.5+dfsg-2
ii  libstdc++6  9.2.1-17
ii  libswresample3  7:4.2.1-2
ii  phonon4qt5  4:4.10.3-3

subtitlecomposer recommends no packages.

Versions of packages subtitlecomposer suggests:
pn  mplayer  

-- no debconf information

-- 
  Regards,
  Shirish Agarwal  शिरीष अग्रवाल
  My quotes in this email licensed under CC 3.0
http://creativecommons.org/licenses/by-nc/3.0/
http://flossexperiences.wordpress.com

E493 D466 6D67 59F5 1FD0 930F 870E 9A5B 5869 609C

Bug#944273: RFS: dmagnetic/0.17-1 -- Interpreter to play textadventures from Magnetic Scrolls in glorious ANSI Art

[dettus]

Package: sponsorship-requests
Severity: normal [important for RC bugs, wishlist for new packages]

Dear mentors,

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

* Package name : dmagnetic
Version : 0.17-1
Upstream Author : Thomas Dettbarn det...@dettus.net
* URL : https://www.dettus.net/dMagnetic/
* License : BSD-2-Clause
* Vcs : None
Section : games

It builds those binary packages:

dmagnetic - Interpreter to play textadventures from Magnetic Scrolls in 
glorious ANSI Art


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


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

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

dget -x 
https://mentors.debian.net/debian/pool/main/d/dmagnetic/dmagnetic_0.17-1.dsc


Changes since the last upload:

* Update to release 0.17.
* Removed some warnings from the mentors.debian.net site.
* Changed the compat level to 12.
* Changed the standards version to 4.4.0

Regards,

Bug#939835: Any update on this?

[Shmerl]

I'm also affected by this bug. Are there any workarounds?

Bug#944012: freetds: CVE-2019-13508: Heap overflow in FreeTDS if UDT type is used with protocol 5.0

[Salvatore Bonaccorso]

Hi Steve,

On Wed, Nov 06, 2019 at 10:10:23AM -0800, Steve Langasek wrote:
> Hello,
> 
> On Sat, Nov 02, 2019 at 08:59:25PM +0100, Salvatore Bonaccorso wrote:
> > Source: freetds
> > Version: 1.1.6-1
> > Severity: important
> > Tags: security upstream fixed-upstream
> > Control: found -1 1.00.104-1
> 
> > The following vulnerability was published for freetds.
> 
> > CVE-2019-13508[0]:
> > | FreeTDS through 1.1.11 has a Buffer Overflow.
> 
> Where does this "1.1.11" number come from?  I do not see any releases newer
> than 1.1.6 upstream.

The CVE assignment was acknowledged by upstream in the launchpad bug
1835896. MITRE descriptions in any case should not be trusted 1-1 and
in this case it even was very mimimalistic. In any case the fix is the
upstream commit 0df4eb82a0e3ff844e373d7c9f9c6c813925e2ac in the git
repository on github. But I notice on
https://www.freetds.org/software.html that the current stable version
should be 1.1.20 and the respective commits there while they are on
the master branch the releases seem not tagged.

Does this helps?

Regards,
Salvatore

Bug#944249: gnuplot-mode does not work with emacs26

[Dima Kogan]

Hi.

It looks like the elpa-gnuplot-mode package is missing some of the
debiany emacs machinery: the files in

  /usr/lib/emacsen-common/packages/...

Somebody should look at the packaging, and figure out what we're missing
and add it. Likely it's just a line or two somewhere.

Nicholas: I'd be delighted if you fix this. Thanks for stepping up! I
don't think you need to do any NMUs to become a DD. Those happen when a
package needs to be fixed, but its maintainer is not available for
whatever reason (NMU = non-maintainer upload). And until you're a DD you
can't upload anything yourself anyway.

You should work on the issue, and when you're done, let me know. I'll
take a look, and then I can do the upload for you.

The location of this package is a historical artifact. It was originally
team-maintained in collab-maint. Then when it was converted (as it turns
out unsuccessfully) to a debian elpa-... package, it was moved to the
emacs team (by changing the Maintainer field). But we didn't move the
repo. I'd rather leave it where it is: there's little downside to
leaving it, and if we do move it, there're a lot of little things that
could be messed up, and then we'd have to fix them. It's not worth the
effort, I think.

Feel free to add yourself to the Uploaders, if you want to.

dima

Bug#944272: openjdk-13 FTCBFS: multiple minor reasons

[Helmut Grohne]

Source: openjdk-13
Version: 13.0.1+9-2
Tags: patch
User: debian-cr...@lists.debian.org
Usertags: ftcbfs

openjdk-13 fails to cross build from source. The package looks well
prepared for cross building, but it seems to have two bugs. The
immediate failure is a linker error failing to find -lz from the native
linker. When cross building, openjdk has a native pass and that one also
needs zlib1g-dev, so it should depend on zlib1g-dev:native. The next
failure comes after the build, when debian/rules invokes the build
architecture objcopy and strip. These tools should be prefixed with the
host architecture triplet. And that's all to make it cross build. Good
work. Please consider applying the attached patch.

Helmut
diff --minimal -Nru openjdk-13-13.0.1+9/debian/changelog 
openjdk-13-13.0.1+9/debian/changelog
--- openjdk-13-13.0.1+9/debian/changelog2019-10-19 19:32:03.0 
+0200
+++ openjdk-13-13.0.1+9/debian/changelog2019-11-06 23:45:11.0 
+0100
@@ -1,3 +1,12 @@
+openjdk-13 (13.0.1+9-2.1) UNRELEASED; urgency=medium
+
+  * Non-maintainer upload.
+  * Fix FTCBFS: (Closes: #-1)
++ Missing Build-Depends: zlib1g-dev:native.
++ Use triplet-prefixed objcopy and strip.
+
+ -- Helmut Grohne   Wed, 06 Nov 2019 23:45:11 +0100
+
 openjdk-13 (13.0.1+9-2) unstable; urgency=medium
 
   * Fix the jtreg consistency check when building without jtreg.
diff --minimal -Nru openjdk-13-13.0.1+9/debian/control 
openjdk-13-13.0.1+9/debian/control
--- openjdk-13-13.0.1+9/debian/control  2019-10-18 14:45:39.0 +0200
+++ openjdk-13-13.0.1+9/debian/control  2019-11-06 23:43:17.0 +0100
@@ -12,7 +12,7 @@
   openjdk-13-jdk-headless:native | openjdk-12-jdk-headless:native,
   libxtst-dev, libxi-dev, libxt-dev, libxaw7-dev, libxrender-dev, 
libcups2-dev, libasound2-dev, liblcms2-dev, libfreetype6-dev (>= 2.2.1), 
libxinerama-dev, libkrb5-dev, xsltproc, libpcsclite-dev, libxrandr-dev, 
libelf-dev, libfontconfig1-dev, libgtk2.0-0 | libgtk-3-0,
   libffi-dev,
-  zlib1g-dev, libattr1-dev, libpng-dev, libjpeg-dev, libgif-dev, 
+  zlib1g-dev, zlib1g-dev:native, libattr1-dev, libpng-dev, libjpeg-dev, 
libgif-dev, 
   libnss3-dev (>= 2:3.17.1),
   openjdk-13-jdk-headless ,
 Build-Depends-Indep: graphviz, pandoc,
diff --minimal -Nru openjdk-13-13.0.1+9/debian/rules 
openjdk-13-13.0.1+9/debian/rules
--- openjdk-13-13.0.1+9/debian/rules2019-10-18 14:45:36.0 +0200
+++ openjdk-13-13.0.1+9/debian/rules2019-11-06 23:45:10.0 +0100
@@ -607,7 +607,7 @@
 else
   bd_gcc = g++-9 ,
 endif
-bd_syslibs = zlib1g-dev, libattr1-dev,
+bd_syslibs = zlib1g-dev, zlib1g-dev:native, libattr1-dev,
 ifneq (,$(filter $(distrel),squeeze lucid))
   bd_syslibs += libpng12-dev, libjpeg62-dev,
 else ifneq (,$(filter $(distrel),wheezy precise quantal raring saucy))
@@ -1774,18 +1774,18 @@
id=$$(echo $$i | sed -r 's,debian/[^/]+,$(d_dbg)/usr/lib/debug,'); \
echo strip $$i; \
mkdir -p $$(dirname $$id); \
-   objcopy --only-keep-debug $$i $$id; \
+   $(DEB_HOST_GNU_TYPE)-objcopy --only-keep-debug $$i $$id; \
chmod 644 $$id; \
-   strip --remove-section=.comment --remove-section=.note \
+   $(DEB_HOST_GNU_TYPE)-strip --remove-section=.comment 
--remove-section=.note \
  --strip-debug $$i; \
-   objcopy --add-gnu-debuglink $$id $$i; \
+   $(DEB_HOST_GNU_TYPE)-objcopy --add-gnu-debuglink $$id $$i; \
  else \
d=usr/lib/debug/.build-id/$${b_id:0:2}; \
f=$${b_id:2}.debug; \
mkdir -p $(d_dbg)/$$d; \
-   objcopy --only-keep-debug --compress-debug-sections $$i 
$(d_dbg)/$$d/$$f; \
+   $(DEB_HOST_GNU_TYPE)-objcopy --only-keep-debug 
--compress-debug-sections $$i $(d_dbg)/$$d/$$f; \
chmod 644 $(d_dbg)/$$d/$$f; \
-   strip --remove-section=.comment --remove-section=.note $$i; \
+   $(DEB_HOST_GNU_TYPE)-strip --remove-section=.comment 
--remove-section=.note $$i; \
  fi; \
done
 endif

Bug#944271: dh_golang_autopkgtest: overrides dh_auto_configure

[Dmitry Smirnov]

Package: dh-golang
Version: 1.42
Severity: important
Affects: -1 src:umoci
Control: blocks 943891 by -1

dh_golang_autopkgtest needlessly overrides dh_auto_configure:

  
https://salsa.debian.org/go-team/packages/dh-golang/blob/master/script/dh_golang_autopkgtest#L83

There are numerous problems with that. First of all this is redundant
and should only be done by the package. Secondly the behavior of override
is not identical to what build system does which causes weird failures
on packages that build successfully. Thirdly, current behavior throws
away important parts of source tree (e.g. "vendor" directory) where
essential code is usually shipped. Finally clean-up of "vendor" directory
is not the job of autopkgtest.

Current behavior affects other packages and their migration to "testing".

Notable case is "umoci" package and #943891 where autopkgtest fails to build
"umoci" due to incorrect behavior of autopkgtest's dh_auto_configure override
(lines 104...113). (Note that "umoci" have no "override_dh_auto_configure").

-- 
Best wishes,
 Dmitry Smirnov



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

Bug#771971: Finanzielle Hilfe (Darlehen zu 1,3%)

[Banca IMI S.P.A]

--
Grüße Herr / Frau,

   Benötigen Sie finanzielle Unterstützung (Darlehen)?
Sprechen Sie mit uns bei Banca IMI, wir lösen Ihre finanziellen 
Probleme.


Unser Zinssatz beträgt 1,3% Jahresrate. Bitte bewerben Sie sich jetzt 
und füllen Sie die nachstehenden Bewerbungsdetails aus:


Vollständiger Name:_
Darlehensbetrag:___
Leihdauer:_
Der Grund für den Kredit:
Telefon:

Wir warten auf Ihre Bewerbung, damit Ihre Kreditanfrage bearbeitet 
werden kann.


Freundliche Grüße

Bug#944269: elpa-notmuch: suggest elpa-mailscripts

[Sean Whitton]

Package: elpa-notmuch
Version: 0.29.2-1
Severity: wishlist

Dear maintainer,

I would like to suggest that elpa-notmuch `Suggests: elpa-mailscripts`,
as the latter package contains features useful specifically to notmuch
users.

Let me know if you want more information on what those features are.

-- 
Sean Whitton


signature.asc
Description: PGP signature

Bug#944270: notmuch: suggest mailscripts

[Sean Whitton]

Package: notmuch
Version: 0.29.2-1
Severity: wishlist

Dear maintainer,

I would like to suggest that notmuch `Suggests: mailscripts`, as the
latter package contains features useful specifically to notmuch users.

Let me know if you want more information on what those features are.

-- 
Sean Whitton


signature.asc
Description: PGP signature

Bug#944268: opensmtpd: upgrading stretch→buster does not warn about possible configuration changes

[Mike Swanson]

Package: opensmtpd
Version: 6.0.3p1-5
Severity: normal

Dear Maintainer,

In the /etc/smtpd.conf file, the “listen on” directive no longer accepts
the “secure” option to listen for both STARTTLS (port 25) and the
always-TLS SMTPS (port 465).  The package upgrade script does not warn
about this and it can result in a non-starting smtpd server.  The fix is
to simply have two listen on commands for both “tls” and “smtps”, to
have functionality previously provided via “secure”.

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

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

Versions of packages opensmtpd depends on:
ii  adduser3.118
ii  debconf [debconf-2.0]  1.5.71
ii  ed 1.15-1
ii  libasr01.0.2-2
ii  libc6  2.28-10
ii  libdb5.3   5.3.28+dfsg1-0.5
ii  libevent-2.1-6 2.1.8-stable-4
ii  libpam0g   1.3.1-5
ii  libssl1.1  1.1.1d-0+deb10u2
ii  lsb-base   10.2019051400
ii  zlib1g 1:1.2.11.dfsg-1

Versions of packages opensmtpd recommends:
ii  opensmtpd-extras  5.7.1-4+b2

Versions of packages opensmtpd suggests:
ii  ca-certificates  20190110

-- Configuration Files:
/etc/smtpd.conf changed [not included]

-- debconf information excluded

Bug#944232: [Pkg-libvirt-maintainers] Bug#944232: /lib/systemd/system/virtlogd.service: Please add needrestart overrides

[Guido Günther]

Hi,
On Wed, Nov 06, 2019 at 12:33:52PM +, Sam Morris wrote:
> Package: libvirt-daemon-system
> Version: 5.6.0-2
> Severity: normal
> File: /lib/systemd/system/virtlogd.service
> 
> needrestart currently defaults to restarting virtlogd when it detects
> that the service needs a restart.
> 
> According to the man page and systemd unit, a reload operation will
> re-exec the virtlogd executable without losing virtual machine logs.
> 
> Please ship /etc/needrestart/restart.d/virtlogd.service and
> /etc/needrestart/restart.d/virtlog scripts which should call 'systemctl
> reload virtlogd.service' and '/etc/init.d/virtlogd reload',
> respectively, so that needrestart doesn't just restart the service on
> its own.
> 
> See /etc/needrestart/restart.d/README.needrestart for more
> information.

can you provide a tested merge request on salsa for that please?
 -- Guido

> 
> -- System Information:
> Debian Release: 10.1
>   APT prefers stable-updates
>   APT policy: (570, 'stable-updates'), (570, 'stable-debug'), (570, 
> 'stable'), (550, 'testing-debug'), (550, 'testing'), (540, 'unstable-debug'), 
> (540, 'unstable'), (1, 'experimental-debug'), (1, 'experimental')
> Architecture: amd64 (x86_64)
> 
> Kernel: Linux 5.2.0-3-amd64 (SMP w/8 CPU cores)
> Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8), 
> LANGUAGE=en_GB.UTF-8 (charmap=UTF-8)
> Shell: /bin/sh linked to /bin/dash
> Init: systemd (via /run/systemd/system)
> LSM: AppArmor: enabled
> 
> Versions of packages libvirt-daemon-system depends on:
> ii  adduser3.118
> ii  debconf [debconf-2.0]  1.5.71
> ii  firewalld  0.7.2-1
> ii  gettext-base   0.19.8.1-9
> ii  init-system-helpers1.56+nmu1
> ii  iptables   1.8.3-2~bpo10+1
> ii  libc6  2.29-2
> ii  libvirt-clients5.6.0-2
> ii  libvirt-daemon 5.6.0-2
> ii  libvirt0   5.6.0-2
> ii  libxml22.9.4+dfsg1-7+b3
> ii  logrotate  3.14.0-4
> ii  lsb-base   10.2019051400
> ii  policykit-10.105-25
> 
> Versions of packages libvirt-daemon-system recommends:
> ii  dmidecode3.2-1
> ii  dnsmasq-base [dnsmasq-base]  2.80-1
> ii  iproute2 4.20.0-2
> ii  parted   3.2-25
> 
> Versions of packages libvirt-daemon-system suggests:
> ii  apparmor2.13.3-6
> ii  auditd  1:2.8.4-3
> pn  nfs-common  
> pn  open-iscsi  
> pn  pm-utils
> pn  radvd   
> ii  systemd 242-7
> ii  systemtap   4.0-1
> pn  zfsutils
> 
> -- Configuration Files:
> /etc/libvirt/nwfilter/allow-arp.xml [Errno 13] Permission denied: 
> '/etc/libvirt/nwfilter/allow-arp.xml'
> /etc/libvirt/nwfilter/allow-dhcp-server.xml [Errno 13] Permission denied: 
> '/etc/libvirt/nwfilter/allow-dhcp-server.xml'
> /etc/libvirt/nwfilter/allow-dhcp.xml [Errno 13] Permission denied: 
> '/etc/libvirt/nwfilter/allow-dhcp.xml'
> /etc/libvirt/nwfilter/allow-incoming-ipv4.xml [Errno 13] Permission denied: 
> '/etc/libvirt/nwfilter/allow-incoming-ipv4.xml'
> /etc/libvirt/nwfilter/allow-ipv4.xml [Errno 13] Permission denied: 
> '/etc/libvirt/nwfilter/allow-ipv4.xml'
> /etc/libvirt/nwfilter/clean-traffic-gateway.xml [Errno 13] Permission denied: 
> '/etc/libvirt/nwfilter/clean-traffic-gateway.xml'
> /etc/libvirt/nwfilter/clean-traffic.xml [Errno 13] Permission denied: 
> '/etc/libvirt/nwfilter/clean-traffic.xml'
> /etc/libvirt/nwfilter/no-arp-ip-spoofing.xml [Errno 13] Permission denied: 
> '/etc/libvirt/nwfilter/no-arp-ip-spoofing.xml'
> /etc/libvirt/nwfilter/no-arp-mac-spoofing.xml [Errno 13] Permission denied: 
> '/etc/libvirt/nwfilter/no-arp-mac-spoofing.xml'
> /etc/libvirt/nwfilter/no-arp-spoofing.xml [Errno 13] Permission denied: 
> '/etc/libvirt/nwfilter/no-arp-spoofing.xml'
> /etc/libvirt/nwfilter/no-ip-multicast.xml [Errno 13] Permission denied: 
> '/etc/libvirt/nwfilter/no-ip-multicast.xml'
> /etc/libvirt/nwfilter/no-ip-spoofing.xml [Errno 13] Permission denied: 
> '/etc/libvirt/nwfilter/no-ip-spoofing.xml'
> /etc/libvirt/nwfilter/no-mac-broadcast.xml [Errno 13] Permission denied: 
> '/etc/libvirt/nwfilter/no-mac-broadcast.xml'
> /etc/libvirt/nwfilter/no-mac-spoofing.xml [Errno 13] Permission denied: 
> '/etc/libvirt/nwfilter/no-mac-spoofing.xml'
> /etc/libvirt/nwfilter/no-other-l2-traffic.xml [Errno 13] Permission denied: 
> '/etc/libvirt/nwfilter/no-other-l2-traffic.xml'
> /etc/libvirt/nwfilter/no-other-rarp-traffic.xml [Errno 13] Permission denied: 
> '/etc/libvirt/nwfilter/no-other-rarp-traffic.xml'
> /etc/libvirt/nwfilter/qemu-announce-self-rarp.xml [Errno 13] Permission 
> denied: '/etc/libvirt/nwfilter/qemu-announce-self-rarp.xml'
> /etc/libvirt/nwfilter/qemu-announce-self.xml [Errno 13] Permission denied: 
> '/etc/libvirt/nwfilter/qemu-announce-self.xml'
> /etc/libvirt/qemu.conf [Errno 13] Permission denied: '/etc/libvirt/qemu.conf'
> /etc/libvirt/qemu/networks/default.xml [Errno 13] Permission denied: 
> 

Bug#944260: lintian: Add a detection/tag for when compat is >> 10 and cdbs in build-depends

[Felix Lechner]

Hi,

On Wed, Nov 6, 2019 at 3:09 PM Chris Lamb  wrote:
>
> … then I'm afraid I don't see any value in a Lintian check; package
> maintainers will surely see this FBTFS first.

With source-only uploads the new norm, not all packages may have a
chance to experience such an FTBFS. :)

If it helps Thomas, we could perhaps generate a classification tag for
cdbs. Together with the existing tag for the compat level, Thomas
could figure out from UDD which packages in the archive, if any,
managed to build with the troublesome combination. He could then file
bugs, although as Chris said there should be none.

Kind regards,
Felix Lechner

Bug#944261: ITB: python-seaborn -- Python data visualization library

[Sandro Tosi]

we already have seaborn https://packages.qa.debian.org/s/seaborn.html

On Wed, Nov 6, 2019 at 5:24 PM Christian Kastner  wrote:
>
> Package: wnpp
> Severity: wishlist
> Owner: Christian Kastner 
> X-Debbugs-CC: debian-de...@lists.debian.org, debian-pyt...@lists.debian.org, 
> debian-scie...@lists.debian.org
>
> * Package name: python-seaborn
>   Version : 0.9.0
>   Upstream Author : Michael Waskom 
> * URL : https://seaborn.pydata.org
> * License : BSD-3-clause
>   Programming Lang: Python3
>   Description : Python data visualization library
>
> Seaborn is a Python data visualization library based on matplotlib. It
> provides a high-level interface for drawing attractive and informative
> statistical graphics.
>
> This will be maintained within the Debian Science Team.
>


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

Bug#944267: pandas: patches for numpy 1.17 compatibility

[Michael Hudson-Doyle]

Source: pandas
Version: 0.23.3+dfsg-4
Severity: normal
Tags: patch

Dear Maintainer,

To aid with the entangled numpy / python 3.8 / everything transition in
Ubuntu I cooked up some patches that make pandas 0.23.3 pass tests with
numpy 1.17, attached in case they would be useful in Debian too. They
actually break with 1.16 unfortunately but that would probably be quite
easy to fix.

Cheers,
mwh
-- System Information:
Debian Release: buster/sid
  APT prefers eoan-updates
  APT policy: (500, 'eoan-updates'), (500, 'eoan'), (400, 'eoan-proposed'), 
(100, 'eoan-backports')
Architecture: amd64 (x86_64)

Kernel: Linux 5.3.0-19-generic (SMP w/8 CPU cores)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
diff -Nru pandas-0.23.3+dfsg/debian/changelog 
pandas-0.23.3+dfsg/debian/changelog
--- pandas-0.23.3+dfsg/debian/changelog 2019-10-22 16:11:08.0 +
+++ pandas-0.23.3+dfsg/debian/changelog 2019-11-06 00:15:32.0 +
@@ -1,3 +1,10 @@
+pandas (0.23.3+dfsg-4ubuntu6) focal; urgency=medium
+
+  * Backport some fixes for compatibility with numpy 1.17+.
+  * Stop ignoring test results on Python 3.7.
+
+ -- Michael Hudson-Doyle   Wed, 06 Nov 2019 
13:15:32 +1300
+
 pandas (0.23.3+dfsg-4ubuntu5) focal; urgency=medium
 
   * Fix installation for multiple python3 versions.
diff -Nru 
pandas-0.23.3+dfsg/debian/patches/COMPAT-Compat-with-numpy-dev-argsort-radix-sort-adde.patch
 
pandas-0.23.3+dfsg/debian/patches/COMPAT-Compat-with-numpy-dev-argsort-radix-sort-adde.patch
--- 
pandas-0.23.3+dfsg/debian/patches/COMPAT-Compat-with-numpy-dev-argsort-radix-sort-adde.patch
1970-01-01 00:00:00.0 +
+++ 
pandas-0.23.3+dfsg/debian/patches/COMPAT-Compat-with-numpy-dev-argsort-radix-sort-adde.patch
2019-11-06 00:15:32.0 +
@@ -0,0 +1,32 @@
+Description: backport numpy 1.17 compat
+  This is a manual backport of 
https://github.com/pandas-dev/pandas/commit/a6e43a43f2cb1b4b7d46b262be2efb825d033eb8
+Bug: https://github.com/pandas-dev/pandas/issues/26361
+Applied-Upstream: a6e43a43f2cb1b4b7d46b262be2efb825d033eb8
+Last-Update: 2019-11-06
+---
+This patch header follows DEP-3: http://dep.debian.net/deps/dep3/
+--- a/pandas/compat/numpy/function.py
 b/pandas/compat/numpy/function.py
+@@ -18,7 +18,8 @@
+ easier to adjust to future upstream changes in the analogous numpy signatures.
+ """
+ 
+-from numpy import ndarray
++from distutils.version import LooseVersion
++from numpy import __version__ as _np_version, ndarray
+ from pandas.util._validators import (validate_args, validate_kwargs,
+  validate_args_and_kwargs)
+ from pandas.errors import UnsupportedFunctionCall
+@@ -112,6 +113,12 @@
+ ARGSORT_DEFAULTS_KIND = OrderedDict()
+ ARGSORT_DEFAULTS_KIND['axis'] = -1
+ ARGSORT_DEFAULTS_KIND['order'] = None
++
++if LooseVersion(_np_version) >= LooseVersion("1.17.0"):
++# GH-26361. NumPy added radix sort and changed default to None.
++ARGSORT_DEFAULTS['kind'] = None
++
++
+ validate_argsort_kind = CompatValidator(ARGSORT_DEFAULTS_KIND, 
fname='argsort',
+ max_fname_arg_count=0, method='both')
+ 
diff -Nru pandas-0.23.3+dfsg/debian/patches/series 
pandas-0.23.3+dfsg/debian/patches/series
--- pandas-0.23.3+dfsg/debian/patches/series2019-09-16 08:29:53.0 
+
+++ pandas-0.23.3+dfsg/debian/patches/series2019-11-06 00:15:32.0 
+
@@ -30,3 +30,6 @@
 array_series_matmul.patch
 pytest_fixtures.patch
 skip_noencoding_locales.patch
+COMPAT-Compat-with-numpy-dev-argsort-radix-sort-adde.patch
+TST-parameterize-indexes-base-test-to-introspect-ufu.patch
+test_add_timestamp_raises.patch
diff -Nru pandas-0.23.3+dfsg/debian/patches/test_add_timestamp_raises.patch 
pandas-0.23.3+dfsg/debian/patches/test_add_timestamp_raises.patch
--- pandas-0.23.3+dfsg/debian/patches/test_add_timestamp_raises.patch   
1970-01-01 00:00:00.0 +
+++ pandas-0.23.3+dfsg/debian/patches/test_add_timestamp_raises.patch   
2019-11-06 00:15:32.0 +
@@ -0,0 +1,12 @@
+--- a/pandas/tests/scalar/period/test_period.py
 b/pandas/tests/scalar/period/test_period.py
+@@ -1050,7 +1050,8 @@
+ # the error.
+ msg = (r"cannot add|unsupported operand|"
+r"can only operate on a|incompatible type|"
+-   r"ufunc add cannot use operands")
++   r"ufunc add cannot use operands|"
++   r"ufunc 'add' cannot use operands")
+ with tm.assert_raises_regex(TypeError, msg):
+ lbox(ts) + rbox(per)
+ 
diff -Nru 
pandas-0.23.3+dfsg/debian/patches/TST-parameterize-indexes-base-test-to-introspect-ufu.patch
 
pandas-0.23.3+dfsg/debian/patches/TST-parameterize-indexes-base-test-to-introspect-ufu.patch
--- 

Bug#885498: Please drop zenmap package from Bullseye

[Jeremy Bicha]

On Sun, Oct 6, 2019 at 5:08 PM Jeremy Bicha  wrote:
> As part of the Python2 removal, it is our intent that pygtk will be removed 
> from Testing before the release of Debian 11
> "Bullseye". Therefore, I am bumping the severity of this bug to Serious to 
> ensure that there is plenty of warning before
> the Debian 11 release and to make the eventual removal of pygtk as smooth as 
> possible.

zenmap is one of the final packages preventing removal of pygtk from
Bullseye. The nmap source package is not auto-removable because of its
high popcorn.

Since it looks like zenmap won't be ported away from pygtk soon, I
urge you to drop the zenmap binary package. It can always be added
back lately after it has been ported to supported libraries.

On behalf of the Debian GNOME team,
Jeremy Bicha

Bug#944260: lintian: Add a detection/tag for when compat is >> 10 and cdbs in build-depends

[Russ Allbery]

Thomas Ward  writes:

> Possibly.  Perhaps I should go the Policy route and inquire whether we
> should consider CDBS obsolete by later versions of Debian policy...

There doesn't seem to be a patch already in #885407 to fix the problem.
That would probably be faster than trying to get something into Policy and
hopefully would speed up resolution of the bug.

v9 and v10 are still not deprecated, so support for v12 isn't urgent
(yet).  If this bug is still unfixed by the time that v9 and v10 are
deprecated, that would probably warrant more urgency.

-- 
Russ Allbery (r...@debian.org)  

Bug#944249: gnuplot-mode does not work with emacs26

[Nicholas D Steeves]

Hi Olaf and Dima,

Dima, if it's alright with you can I please take care of this bug?
I've head I need an RC Bug NMU process for the "demonstrates skills
and knowledge of process" section of my eventual DD application.

I'm treating this as an NMU because while
  https://salsa.debian.org/debian/gnuplot-mode/blob/master/debian/control#L4

states that this is a Team Emacsen package
  https://salsa.debian.org/debian/gnuplot-mode/blob/master/debian/control#L8

it's in Debian/collab-maint and not Team Emacsen team namespace.

If you'd like I can move the repository to our namespace, but please
let me know if this is the case!

On Wed, Nov 06, 2019 at 05:45:58PM +0100, Olaf Skibbe wrote:
> Package: gnuplot-mode
> Version: 1:0.7.0-2014-12-31-1
> Severity: grave
> Justification: renders package unusable
> 
> Dear Maintainer,
> 
> I hope that this is the right place for this report.
>

Yes :-)

>* What exactly did you do (or not do) that was effective (or
>  ineffective)?
> 
> Opening a gnuplot file in emacs.
> 
>* What was the outcome of this action?
> 
> No gnuplot-mode available.
> 
>* What outcome did you expect instead?
> 
> gnuplot-mode available in emacs.
> 
> Details:
> 
> On debian buster, one finds:
> 
> Package: elpa-gnuplot-mode
> Version: 1:0.7.0-2014-12-31-1
> [...]
> Enhances: emacs, emacs24, emacs25
> 
> On the other hand:
> 
> Package: emacs
> Version: 1:26.1+1-3.2+deb10u1
> 
> Hence, gnuplot-mode is not available in emacs.
> 
> I would appreciate gnuplot-mode available (backports would be fine).
> 

If Dima give the go-ahead I'll investigate if this would be approved
for a stable update.  It seems like it would be, because RC bugs like
this aren't supposed to be solved using backports.


Regards,
Nicholas


signature.asc
Description: PGP signature

Bug#944266: vpnc-scripts: vpnc-script sets incorrect default for /128 IPv6 split tunnels

[Kellen Fox]

Package: vpnc-scripts
Version: 0.1~git20190117-1
Severity: normal

Dear Maintainer,

There is a known bug in vpnc-scripts that incorrectly sets a default route when 
a /128 is requested instead of a /0.

Upstream bug:
https://gitlab.com/openconnect/openconnect/issues/31

Merged patch:
https://gitlab.com/openconnect/vpnc-scripts/merge_requests/1/diffs

I have been running a manully patched version of this script for some months 
and would love to see it show up in the debian version. I am happy to do any 
needed legwork to get this done.

Thanks!

- Kellen

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

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

Versions of packages vpnc-scripts depends on:
ii  iproute2   5.3.0-1
ii  net-tools  1.60+git20180626.aebd88e-1

vpnc-scripts recommends no packages.

Versions of packages vpnc-scripts suggests:
pn  dnsmasq 
pn  openssh-server  
pn  resolvconf  

-- no debconf information

Bug#907999: fonts-noto-cjk: Unable to use system fonts in Firefox after #907048

[Lifu Tang]

Hi Boyuan,

I've tested out your patch, and it works great so far. Thank you very much
for your quick response!

Best regards,


Lifu

On Wed, Nov 6, 2019 at 4:27 PM Boyuan Yang  wrote:

> Control: severity -1 important
> Control: tags -1 + patch pending
> X-Debbugs-CC: kos...@debian.org gunna...@ubuntu.com czc...@debian.org
>
> Hi all,
>
> I just found out that after explicitly dealt with the buggy fontconfig
> snippets provided by Arphic fonts (to be more specific, the one shipped
> by fonts-arphic-uming), using "prepend" + binding="strong" is enough to
> make sure that Noto CJK fonts to be the first to match under Chinese
> locales while preventing web browsers like Chromium and Firefox from
> over-aggressively picking up Noto CJK fonts. The new version of fonts-
> noto-cjk will be uploaded shortly.
>
> I will test this patch on Debian Stable (Debian 10). If it also applies
> there, I'm planning to make a stable update as well.
>
>
> Regards,
> Boyuan Yang
>
>
> diff --git a/debian/70-fonts-noto-cjk.conf b/debian/70-fonts-noto-
> cjk.conf
> index 3589aaf..c72aa44 100644
> --- a/debian/70-fonts-noto-cjk.conf
> +++ b/debian/70-fonts-noto-cjk.conf
> @@ -32,7 +32,7 @@
>  
>  serif
>  
> -
> +
>  Noto Serif CJK SC
>  
>  
> @@ -44,7 +44,7 @@
>  
>  serif
>  
> -
> +
>  Noto Serif CJK TC
>  
>  
> @@ -56,7 +56,7 @@
>  
>  serif
>  
> -
> +
>  Noto Serif CJK HK
>  
>  
> @@ -92,7 +92,7 @@
>  
>  sans-serif
>  
> -
> +
>  Noto Sans CJK SC
>  
>  
> @@ -104,7 +104,7 @@
>  
>  sans-serif
>  
> -
> +
>  Noto Sans CJK TC
>  
>  
> @@ -116,7 +116,7 @@
>  
>  sans-serif
>  
> -
> +
>  Noto Sans CJK HK
>  
>  
> @@ -152,7 +152,7 @@
>  
>  monospace
>  
> -
> +
>  Noto Sans Mono CJK SC
>  
>  
> @@ -164,7 +164,7 @@
>  
>  monospace
>  
> -
> +
>  Noto Sans Mono CJK TC
>  
>  
> @@ -176,7 +176,7 @@
>  
>  monospace
>  
> -
> +
>  Noto Sans Mono CJK HK
>  
>  
>
>
> On Wed, 05 Sep 2018 18:53:53 +0900 "Kan-Ru Chen" 
> wrote:
> >
> > On Wed, Sep 5, 2018, at 6:14 PM, ChangZhuo Chen (陳昌倬) wrote:
> > > On Wed, Sep 05, 2018 at 08:59:41AM +0900, Kan-Ru Chen wrote:
> > > > Package: fonts-noto-cjk
> > > > Version: 1:20170601+repack1-3
> > > > Severity: normal
> > > >
> > > > Dear Maintainer,
> > > >
> > > > I think the changes made to the config is to aggressive. After
> this
> > > > change Firefox cannot use other system fonts other than Noto CJK
> TC
> > > > when my locale is set to zh_TW.
> > >
> > > Hi koster, byang,
> > >
> > > Any idea on how to fix this?
> >
> > Since I am the original reporter, you know my opinion :-)
> >
> > IMO prepend is already problematic and prepend_first should be
> reserved to end user config. We should revert the change and find
> another way to fix the original issue. If the original problem is font
> ordering, can we create tiered font groups and order them by config
> numbering?
> >
> > Kanru
> >
> >
>

Bug#944224: Keep "dmesg" logging after boot.

[Dmitry Bogatov]

control: tags -1 +wontfix

[2019-11-06 10:12] "Gong S." 
> Package: initscripts
> Version: 2.96-1
> Severity: wishlist

> Currently, the "bootlogd" script only records the "dmesg" messages
> during boot, and exits afterwards.

You meant "bootlogs", I think.

> However, most system issues happen after boot.
> So when such issue happens, nothing is logged, so it is hard to find the 
> cause.
> I think that it is wise to keep `dmesg` running after booting.
> To be precise, change line 35 of "/etc/init.d/bootlogs"
> from "dmesg -s 524288 > /var/log/dmesg"
> to "nohup dmesg -Hwx > /var/log/dmesg".

As was already pointed, -s makes sure that whole kernel ring buffer is
dumped, and -H will be backward-incompatible change.

Also, just starting process with `nohup foo &' is not proper way to
start long-running process. If you want long-running process to keep
saving kernel logs, you'd have to create init.d script, with "start" and
"stop" commands.

But wait, why to we need it? You probably already have syslog daemon
running, and many of them know how to to save kernel logs too. At least
socklog and rsyslog do.

If you do not use syslog daemon, you can put command you propose into
/etc/boot.d or directly into /etc/init.d/bootlogs (it is conffile!)

Sorry, I do not see general value in your proposal.
-- 
Note, that I send and fetch email in batch, once in a few days.
Please, mention in body of your reply when you add or remove recepients.

Bug#943397: runit: Add a finish-default

[Dmitry Bogatov]

[2019-11-06 13:45] Lorenzo Puliti 
> Package: runit
> Version: 2.1.2-35
> Followup-For: Bug #943397
>
> I'm attaching two patches for review;

> one thing that I'm still not sure about is the exit code range.  $1 in
> the finish file can be run's exit code or the daemon's exit code.  I'm
> using the wierd range 160-170 but is still possible that the exit code
> is overlapped with the one of some daemons, for example see smartd(8)
> 'EXIT STATUS' section.  Do you have a better range to suggest?

I do not have better plan. And since you already used these values in
patches, let us stick to them.

> +NAME=$(pwd | cut -f4 -d"/")

Maybe NAME=${PWD##*/}? Also, `set -e`, please.

> +trap 'if [ "$VERBOSE" = 1 ]; then echo "runsv: $NAME stopped"; fi' EXIT

I'd say this is simplier:

if [ "${VERBOSE:-0}" != 0 ] ; then
trap "echo runsv: $NAME stopped" EXIT
fi

> +case $1 in
> + -1)
> + echo "runsv: ERROR $1 in $NAME: unexpected error or wrong sh 
> syntax"
> + # no need to sv d service here, runsv will stop trying after 
> the first attempt to start
> + ;;

Are you sure about "wrong sh syntax" part? As far as I know, shell exit
with $? = 2 in case of wrong syntax, and "runsv" has no means to
distinguish it from plain "exit 2". Also, runsv(1) mentions "didn't exit
correctly", which I believe means signal.

> + 161)

Please, follow same style as in invoke-run. Unmatched brackets drive
editors crazy.

> +++ b/debian/runit.install
> @@ -23,3 +23,4 @@ debian/contrib/runlevel /lib/runit
>  debian/sulogin/run  /etc/runit/runsvdir/single/sulogin
>  debian/contrib/lib/async-timeout/lib/runit
>  debian/contrib/lib/run_sysv_scripts /lib/runit
> +debian/contrib/lib/finish-default /lib/runit

!sort, please.

> part 3 text/plain3239
> From 642ffb914b6e7d67c723f7e620f3b9a404d7572e Mon Sep 17 00:00:00 2001
> From: Lorenzo Puliti 
> Date: Tue, 5 Nov 2019 23:49:58 +0100
> Subject: [PATCH 2/2] Update invoke-run manpage for finish-default
>
> Update invoke-run manpage to account for finish-default file and
> special error codes.
> [...]
> +.IP "" 2
> +.B runsv: foo binary not installed
> +.PP
> +.IP "" 4
> +this happens when the
> +.I foo
> +binary has been removed, but not purged.

s/binary/package, containing binary/ or something like this. Binaries
(e.g ELF executable files) can't be removed-not-purged, binary packages
are.

> +.B runsv: ERROR -1 in foo: unexpected error or wrong sh syntax
> +.PP
> +.IP "" 4
> +this message comes from the finish file, but the exit code comes from
> +.BR runsv (8)
> +and is documented in its manpage.

Ditto on "wrong sh syntax"

> +.B runsv: ERROR 161 in foo: disabled by local settings
> +.PP
> +.IP "" 4
> +Some service specific setting prevent
> +.I foo
> +from starting; it's likely something in
> +.BI /etc/default/foo

Is it really ERROR? Maybe change it to "NOTE" or something like this?
By the way (and I agree), Policy deprecated following pattern:

$ grep DISABLED /etc/default/foo
DISABLED=1


> +.PP
> +.IP "" 2
> +.B runsv: ERROR 162 in foo: configtest or early setup failed
> +.PP
> +.IP "" 4
> +A configuration file of
> +.I foo
> +is malformed and the configtest failed;
> +.I foo
> +log may contain additional info from the test itself.
> +Otherwise 

I think "alternatively" is more correct word. Take with grain of salt, I
am not native speaker.

> the runscript has failed to do some setup that is essential to the
> +.I foo
> +service.
> +.PP
> +.IP "" 2
> +.B runsv: ERROR 170 in foo: a runtime hard dependency is missing
> +.PP
> +.IP "" 4
> +A dependency failed the check and can't be bring up; a list of dependencies 
> of
> +.I foo
> +can be extracted with the following command
> +.PP
> +.IP "" 6
> +.EX
> +grep 'exit 170' /etc/sv/foo/run | cut -d ' ' -f3

I'd not recommend this because of following:

if full_moon ; then
set -- dep1 dep2
else
set -- dep3 dep4
fi
sv up "$@" || exit 170


> +.SH FINISH FILE AND FINISH-DEFAULT
> +Since version 2.1.2-36 the Debian runit package ships a
> +.BI /lib/runit/finish-default
> +file that contains code that can be shared across different services.
> +This file can be sourced inside the regular finish file of a service,
> +like the following example

Wonderful.
-- 
Note, that I send and fetch email in batch, once in a few days.
Please, mention in body of your reply when you add or remove recepients.

Bug#907999: fonts-noto-cjk: Unable to use system fonts in Firefox after #907048

[Boyuan Yang]

Control: severity -1 important
Control: tags -1 + patch pending
X-Debbugs-CC: kos...@debian.org gunna...@ubuntu.com czc...@debian.org

Hi all,

I just found out that after explicitly dealt with the buggy fontconfig
snippets provided by Arphic fonts (to be more specific, the one shipped
by fonts-arphic-uming), using "prepend" + binding="strong" is enough to
make sure that Noto CJK fonts to be the first to match under Chinese
locales while preventing web browsers like Chromium and Firefox from
over-aggressively picking up Noto CJK fonts. The new version of fonts-
noto-cjk will be uploaded shortly.

I will test this patch on Debian Stable (Debian 10). If it also applies
there, I'm planning to make a stable update as well.


Regards,
Boyuan Yang


diff --git a/debian/70-fonts-noto-cjk.conf b/debian/70-fonts-noto-
cjk.conf
index 3589aaf..c72aa44 100644
--- a/debian/70-fonts-noto-cjk.conf
+++ b/debian/70-fonts-noto-cjk.conf
@@ -32,7 +32,7 @@
 
 serif
 
-
+
 Noto Serif CJK SC
 
 
@@ -44,7 +44,7 @@
 
 serif
 
-
+
 Noto Serif CJK TC
 
 
@@ -56,7 +56,7 @@
 
 serif
 
-
+
 Noto Serif CJK HK
 
 
@@ -92,7 +92,7 @@
 
 sans-serif
 
-
+
 Noto Sans CJK SC
 
 
@@ -104,7 +104,7 @@
 
 sans-serif
 
-
+
 Noto Sans CJK TC
 
 
@@ -116,7 +116,7 @@
 
 sans-serif
 
-
+
 Noto Sans CJK HK
 
 
@@ -152,7 +152,7 @@
 
 monospace
 
-
+
 Noto Sans Mono CJK SC
 
 
@@ -164,7 +164,7 @@
 
 monospace
 
-
+
 Noto Sans Mono CJK TC
 
 
@@ -176,7 +176,7 @@
 
 monospace
 
-
+
 Noto Sans Mono CJK HK
 
 


On Wed, 05 Sep 2018 18:53:53 +0900 "Kan-Ru Chen" 
wrote:
> 
> On Wed, Sep 5, 2018, at 6:14 PM, ChangZhuo Chen (陳昌倬) wrote:
> > On Wed, Sep 05, 2018 at 08:59:41AM +0900, Kan-Ru Chen wrote:
> > > Package: fonts-noto-cjk
> > > Version: 1:20170601+repack1-3
> > > Severity: normal
> > > 
> > > Dear Maintainer,
> > > 
> > > I think the changes made to the config is to aggressive. After
this
> > > change Firefox cannot use other system fonts other than Noto CJK
TC
> > > when my locale is set to zh_TW.
> > 
> > Hi koster, byang,
> > 
> > Any idea on how to fix this?
> 
> Since I am the original reporter, you know my opinion :-)
> 
> IMO prepend is already problematic and prepend_first should be
reserved to end user config. We should revert the change and find
another way to fix the original issue. If the original problem is font
ordering, can we create tiered font groups and order them by config
numbering?
> 
> Kanru
> 
> 


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

Bug#942050: gnome-shell: gnome shell does not take the org.gnome.desktop.peripherals.keyboard numlock-state into account

[Jean-Marc]

This problem seems to be solved in the last gnome-shell version 
(3.34.1+git20191024-1).

You can close this bug report.

Regards,

Jean-Marc 
https://6jf.be/keys/ED863AD1.txt


pgpuXLTRrWFC5.pgp
Description: PGP signature

Bug#944264: alien-arena: Alien Arena package out of date.

[Nic]

There are three packages associated with Alien Arena in the Debian 
repos, they are alien-arena-data, alien-arena-server and alien-arena itself.


The version of the packages in the debian repos is 7.66 which has long 
been deprecated. There are very few servers for it and it is unsupported 
by COR Entertainment, the current version of Alien Arena is 7.71.1.


The description for the package should read;

Alien Arena is a furious frag fest with arenas ranging from the small, 
to the massive. With game modes such as Capture The Flag and Tactical, 
there are terrific team-based experiences to be had as well as 1v1 
duels, free-for-all and dozens of mutators to alter the game play to 
your liking.


At the bottom of the current description it say that the SDL package 
will be installed, this is unnecessary as Alien Arena doesn't use SDL.


Alien Arena is now available on steam for purchase along with it's DLC. 
The good news is that COR Entertainment are leaving the source code and 
game assets in their svn repository at svn.icculus.org/alienarena/trunk 
for free distribution in linux distributions. This excludes content that 
is specific to the steam version.


Regards,

Nic

Bug#944265: mailutils: local privilege escalation in maidag utility (fixed in 3.8)

[Paul Wise]

Source: mailutils
Severity: serious
Tags: security fixed-upstream

There is a local privilege escalation in the maidag utility:

https://savannah.gnu.org/forum/forum.php?forum_id=9586

   This version fixes important security flow. The maidag utility has
   been withdrawn and three new programs have been included to provide
   its functionality: local mail delivery agent mda, LMTP daemon lmtpd,
   and user mail delivery tool putmail. 

https://git.savannah.gnu.org/cgit/mailutils.git/plain/NEWS

   * The maidag utility is withdrawn

   The main purpose of this utility was to work as local mail delivery
   agent (MDA), a program responsible for final delivery of email messages
   to the recipient's mailbox.  As such it required suid privileges.

   In parallel with its main purpose, it also was able to work in two
   other modes: the 'url' mode, designed to deliver mails to arbitrary
   mailbox URLs, and 'lmtp' mode, in which it acted as local mail
   transport daemon.  Neither of these needed suid privileges.

   The unfortunate design decision to combine the three modes in a single
   versatile tool resulted in local privilege escalation threat in 'url'
   mode.

   To fix this, maidag has been replaced by three different utilities,
   each one with a precisely defined purpose and carefully designed
   privileges: mda, lmtpd, and putmail.

-- 
bye,
pabs

https://wiki.debian.org/PaulWise


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

Bug#883157: mod_python upstream now supports python3

[Chubb, Peter (Data61, Kensington NSW)]

mod_python at https://github.com/grisha/mod_python now can be built
against python versions 3.3 through 3.8.  (a patch merged today adds
support for python >= 3.7)

Providing libapache2-mod-python3 should now therefore be relatively easy.
Please package the new upstream.
-- 
Dr Peter Chubb Tel: +61 2 9490 5852  http://ts.data61.csiro.au/
Trustworthy Systems GroupCSIRO's Data61

Bug#944264: alien-arena: Alien Arena package out of date.

[Nic Harvey]

Source: alien-arena
Version: 7.66
Severity: normal

Dear Maintainer,

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

   * What led up to the situation?
   * What exactly did you do (or not do) that was effective (or
 ineffective)?
   * What was the outcome of this action?
   * What outcome did you expect instead?

*** End of the template - remove these template lines ***



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

Kernel: Linux 4.19.0-6-amd64 (SMP w/4 CPU cores)
Kernel taint flags: TAINT_WARN, TAINT_CRAP
Locale: LANG=en_AU.UTF-8, LC_CTYPE=en_AU.UTF-8 (charmap=UTF-8),
LANGUAGE=en_AU.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /usr/bin/dash

Bug#944163: interimap: seems --repair doesn't work

[Guilhem Moulin]

On Wed, 06 Nov 2019 at 12:44:08 +0100, Jonas Smedegaard wrote:
> It seems that interimap would do far better in such an extreme
> scenario, as it seems to syncronize small chunks at a time which would
> make it possible to continue-where-left-off in far smaller chunks than
> possible (or rather comprehensible to me) to do with either offineimap
> or dsync.

Correct, the targeted use-case is when one wants to synchronize often,
meaning most of the time there are no changes to send over.  offlineimap
(and `interimap --repair`) selects each mailbox, fetches all messages
UIDs and flags, then locally checks for differences between the local
and remote list.  This is slow, I/O-intensive, and causes a significant
amount of network traffic.  OTOH with QRESYNC-based synchronization,
it's enough to compare the output of the LIST command, which is much
shorter (one line per message vs. two lines per mailbox).  In practice
the LIST/STATUS response for 100-150 mailboxes fits in a single TLS
record (max size 16kiB); for servers supporting the COMPRESS=DEFLATE
extension that number is typically over 100× higher (it's also possible
to compress at a lower layer, but the advantage of doing it at the IMAP
layer is that it gives more control on the deflate dictionary; we for
instance trigger flush points before sending/receiving large messages,
which likely wouldn't compress well anyway).  When there are new
changes, be it flag updates, new messages, or deletions, only what's new
since the last successful sync needs to be replayed on the other side.
Thanks to that logic, interimap should be able to scale to mailboxes
containing many millions messages; AFAICT Dovecot is quite able to cope
with these too, but the MUA might not.
 
> When I switched, I removed the local folder and had interimap syncronize 
> it from scratch.  Or at least that is my belief: Does your forensics 
> analysis above imply that I failed at that, and the local copy cannot 
> have been initialized by interimap?

I see 3 states in your original bug report:

| local: Update last clean state for INBOX: (HIGHESTMODSEQ 165 UIDVALIDITY 
1571588814 UIDNEXT 9598)

These are the numbers found in the database, and correspond to the state
of the local INBOX at the time it was last synchronized by interimap.
The numbers make sense for a mailbox that was recently created and
populated en masse: low HIGHESTMODSEQ (a strictly increasing sequence of
all modifications to the mailbox, incl. flags, message creations and
deletion) and highest UID <9598 suggests there are slightly under 10k
messages in that mailbox.  Based on how Dovecot allocates UIDVALIDITY, I
guess the mailbox was created on Sun, 20 Oct 2019 at 18:26:54 +0200.

| local: S: * STATUS INBOX (UIDNEXT 290008 UIDVALIDITY 1571588814 HIGHESTMODSEQ 
71671)

This the *current* state of the local INBOX.  The new UIDNEXT and
HIGHESTMODSEQ values suggest (IMAP4rev1 mandates the sequences to be
strictly increasing, but in practice Dovecot uses continuous numbers)
that within two weeks that mailbox saw 280k *new* messages (possibly now
deleted) and over 71k *new* changes (such as flag updates, and message
creation/deletion).  It's not impossible, but certainly suspicious.

I'd be interested to know the last good remote state, could you please
run:

sqlite3 /path/to/interimap/database.db -header <<-EOF
SELECT l.UIDVALIDITY AS lUIDVALIDITY, l.UIDNEXT AS lUIDNEXT, 
l.HIGHESTMODSEQ AS lHIGHESTMODSEQ,
   r.UIDVALIDITY AS rUIDVALIDITY, r.UIDNEXT AS rUIDNEXT, 
r.HIGHESTMODSEQ AS rHIGHESTMODSEQ
 FROM mailboxes m JOIN local l ON m.idx = l.idx JOIN remote r 
ON m.idx = r.idx
WHERE mailbox = 'INBOX';

SELECT COUNT(*) AS messages
 FROM mailboxes NATURAL JOIN mapping
WHERE mailbox = 'INBOX';
EOF

and paste the output?  (The database file can normally be found under
‘${XDG_SHARE_HOME:-~/.local/share}/interimap’, and the default filename
is the hostname of your remote server.)

We already know the values of lUIDVALIDITY, lUIDNEXT, lHIGHESTMODSEQ
and rUIDVALIDITY: respectively 1571588814, 9598, 165 and 1571588814.
I'm interested in rUIDNEXT and rHIGHESTMODSEQ though.  I'd also like to
see the output of

doveadm mailbox status "messages uidnext uidvalidity highestmodseq 
firstsaved" INBOX

both locally and remotely.

| remote: S: * STATUS INBOX (UIDNEXT 280739 UIDVALIDITY 1571588814 
HIGHESTMODSEQ 74538)

This the *current* state of the remote INBOX.  The UIDVALIDITY value
suggests the mailbox was also created on Sun, 20 Oct 2019 at 18:26:54 +0200
(just like the local INBOX; not impossible of course, but suspicious),
while the high UIDNEXT and HIGHESTMODSEQ values hint at a much older
mailbox (unless that mailbox is very active, again not impossible but
suspicious).

| remote: ERROR: UIDVALIDITY changed! (1571588814 != 1154884797)  Need to 
invalidate the UID cache.

This indicates that the UIDVALIDITY of 

Bug#944261: ITB: python-seaborn -- Python data visualization library

[Yaroslav Halchenko]

what is ITB?

$> acpolicy python-seaborn
python-seaborn:
  Installed: 0.9.0-1
  Candidate: 0.9.0-1
  Version table:
 *** 0.9.0-1 100
100 http://deb.debian.org/debian buster/main amd64 Packages
100 /var/lib/dpkg/status

Vcs-Git: git://github.com/neurodebian/seaborn.git -b debian


feel free to move under science team

thanks!!!

On Wed, 06 Nov 2019, Christian Kastner wrote:

> Package: wnpp
> Severity: wishlist
> Owner: Christian Kastner 
> X-Debbugs-CC: debian-de...@lists.debian.org, debian-pyt...@lists.debian.org, 
> debian-scie...@lists.debian.org

> * Package name: python-seaborn
>   Version : 0.9.0
>   Upstream Author : Michael Waskom 
> * URL : https://seaborn.pydata.org
> * License : BSD-3-clause
>   Programming Lang: Python3
>   Description : Python data visualization library

> Seaborn is a Python data visualization library based on matplotlib. It
> provides a high-level interface for drawing attractive and informative
> statistical graphics.

> This will be maintained within the Debian Science Team.



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

Bug#919619: [Pkg-utopia-maintainers] Bug#919619: network-manager: should support iwd as wpasupplicant alternative

[Michael Biebl]

Am 07.11.19 um 00:21 schrieb Jonas Smedegaard:
> Quoting Jonas Smedegaard (2019-02-03 23:44:24)
>> Quoting Andreas Henriksson (2019-02-03 23:12:37)
>>> Control: severity -1 wishlist
>>
>> Please reconsider the severity, because...
>>
>>> On Thu, Jan 17, 2019 at 10:09:21PM +0100, Jonas Smedegaard wrote:
 network-manager is compiled with support for iwd, but the package 
 declares an absolute dependency on wpasupplicant.
>>
>> Above is the issue reported: I.e. the _possibility_ for using iwd as 
>> alternative.
> 
> Please relax to only _recommend_ wpasupplicant, to allow (even if not 
> recommend) use with IWD.

Once we have an *automatic* fallback to iwd I'm happy to add iwd as
alternative dependency.
Until then, I prefer to keep wpasupplicant as a hard depends.
Unfortunately we have way too many users which have Recommends disabled
and I'm not intending to break those setups and get bug reports.

Michael


-- 
Why is it that all of the instruments seeking intelligent life in the
universe are pointed away from Earth?



signature.asc
Description: OpenPGP digital signature

Bug#905961: Bug#905963: unbound: FTBFS on hurd-i386 / Bug#905961: unbound: FTBFS on non-linux systems

[Hilmar Preuße]

Am 12.08.2018 um 14:28 teilte Svante Signell mit:

Hi,

> Currently unbound FTBFS on GNU/Hurd due to a dependency on libsystemd-
> dev for non-linux systems (see #905961) and a missing function:
> compat/getentropy_gnu.c, derived from getentropy_solaris.c. Attached is
> hurd.diff defining that function by modifying configure.ac and
> Makefile.in too.
> 
Any news for these two issues? Currently gnutls28 can't be built on
these arches, which blocks a lot of other package, e.g. two packages of
mine.

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



signature.asc
Description: OpenPGP digital signature

Bug#944263: python-releases: FTBFS in unstable

[Steve Langasek]

Source: python-releases
Version: 1.4.0-2
Severity: serious
User: ubuntu-de...@lists.ubuntu.com
Usertags: origin-ubuntu focal

Hi Zygmunt,

python-releases 1.4.0-2 fails to build in the Ubuntu devel series, and I
reproduced this failure also in a Debian sid environment:

[...]
make[1]: Entering directory '/<>'
PYTHONPATH=. python3 -m sphinx -b html -d docs/_build/.doctrees -N docs 
docs/_build/html
Running Sphinx v1.8.5
making output directory...
building [mo]: targets for 0 po files that are out of date
building [html]: targets for 4 source files that are out of date
updating environment: 4 added, 0 changed, 0 removed
reading sources... [ 25%] changelog

Exception occurred:
  File "/usr/lib/python3/dist-packages/semantic_version/base.py", line 102, in 
__init__
raise ValueError("Call either Version('1.2.3') or Version(major=1, ...).")
ValueError: Call either Version('1.2.3') or Version(major=1, ...).
The full traceback has been saved in /tmp/sphinx-err-r8fk2tvf.log, if you want 
to report the issue to the developers.
Please also report this if it was a user error, so that a better error message 
can be provided next time.
[...]

  (https://launchpad.net/ubuntu/+source/python-releases/1.4.0-2/+build/17970690)

The sphinx long shows a more complete backtrace which should help make it
clearer:

  File "/tmp/python-releases-1.4.0/releases/models.py", line 14, in __init__
super(Version, self).__init__(version_string, partial)
  File "/usr/lib/python3/dist-packages/semantic_version/base.py", line 102, in 
__init__
raise ValueError("Call either Version('1.2.3') or Version(major=1, ...).")
ValueError: Call either Version('1.2.3') or Version(major=1, ...).


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


signature.asc
Description: PGP signature

Bug#919619: network-manager: should support iwd as wpasupplicant alternative

[Jonas Smedegaard]

Quoting Jonas Smedegaard (2019-02-03 23:44:24)
> Quoting Andreas Henriksson (2019-02-03 23:12:37)
> > Control: severity -1 wishlist
> 
> Please reconsider the severity, because...
> 
> > On Thu, Jan 17, 2019 at 10:09:21PM +0100, Jonas Smedegaard wrote:
> > > network-manager is compiled with support for iwd, but the package 
> > > declares an absolute dependency on wpasupplicant.
> 
> Above is the issue reported: I.e. the _possibility_ for using iwd as 
> alternative.

Please relax to only _recommend_ wpasupplicant, to allow (even if not 
recommend) use with IWD.


 - Jonas

-- 
 * Jonas Smedegaard - idealist & Internet-arkitekt
 * Tlf.: +45 40843136  Website: http://dr.jones.dk/

 [x] quote me freely  [ ] ask before reusing  [ ] keep private


signature.asc
Description: signature

Bug#944260: lintian: Add a detection/tag for when compat is >> 10 and cdbs in build-depends

[Thomas Ward]

Possibly.  Perhaps I should go the Policy route and inquire whether we 
should consider CDBS obsolete by later versions of Debian policy...


Thanks for the response though!  :)


Thomas


On 11/6/19 6:03 PM, Chris Lamb wrote:

Hi Thomas,


Nope, all CDBS packages compat >> 10 FTBFS if using the cdbs debhelper
rulesets with a straight cdbs include in debian/rules.

… then I'm afraid I don't see any value in a Lintian check; package
maintainers will surely see this FBTFS first.


Regards,

Bug#944260: lintian: Add a detection/tag for when compat is >> 10 and cdbs in build-depends

[Thomas Ward]

Nope, all CDBS packages compat >> 10 FTBFS if using the cdbs debhelper rulesets 
with a straight cdbs include in debian/rules. Refer to the linked bug for 
details cause that affects all CDBS built packages which try and use a compat 
>> 10.

Sent from my iPhone

> On Nov 6, 2019, at 17:33, Chris Lamb  wrote:
> 
> severity 944260 wishlist
> tags 944260 + moreinfo
> thanks
> 
> Hi Thomas,
> 
>> Since Debhelper >= 10.9.2 and higher (and therefore compat >= 11), 
>> there is a known issue in CDBS (refer to bug #885407 [1]) with the use 
>> of dh_systemd_enable instead of dh_installsystemd.
> 
> So, I'm a little hesitant — we should spend our limited energy fixing
> the aforementioned bug rather than also spending our time here in
> Lintian warning about it; we will have to do the former *anyway*,
> after all.
> 
> (Does this affect all packages or only ones using systemd? I assume
> the package does not FTBFS, merely fails to work properly at runtime?)
> 
> 
> Best wishes,
> 
> -- 
>  ,''`.
> : :'  : Chris Lamb
> `. `'`  la...@debian.org  chris-lamb.co.uk
>   `-
> 

Bug#944260: lintian: Add a detection/tag for when compat is >> 10 and cdbs in build-depends

[Chris Lamb]

Hi Thomas,

> Nope, all CDBS packages compat >> 10 FTBFS if using the cdbs debhelper 
> rulesets with a straight cdbs include in debian/rules.

… then I'm afraid I don't see any value in a Lintian check; package
maintainers will surely see this FBTFS first.


Regards,

-- 
  ,''`.
 : :'  : Chris Lamb
 `. `'`  la...@debian.org  chris-lamb.co.uk
   `-

Bug#936318: collectd python2 removal in debian (and make it build)

[Andreas Henriksson]

Control: tags -1 + patch

Hello,

The attached debdiff disables the python plugin, since it's pure
python2 stuff. (Also removes python plugin example from the
shipped collectd.conf and updates package description.)

While at it I also had to actually make the package build again,
so bonus content included for that:

I cherry-picked a bunch of upstream compiler warning fixes, before
a warning in an external package header file finally forced me
to look up how to disable -Werror which apparently there's a
configure flag for which IMHO should always be used in release
builds (and thus the debian package). Otherwise you'll have FTBFS
bugs introduced from under you by changing dependencies and compilers.

Finally the tests failed. Apparently gcc decides to optimize out a
condition "if (ptr != NULL)" before doing "*ptr = '\0';" which results
in a segfault. The reason for gcc doing this is likely that previously
memcpy has been used on ptr, and you probably shouldn't assume using
memcpy(NULL, ) will work. I didn't find any fix for this upstream
so did a quick hack myself for that.

Regards,
Andreas Henriksson


diff -Nru collectd-5.8.1/debian/changelog collectd-5.8.1/debian/changelog
--- collectd-5.8.1/debian/changelog 2019-04-06 14:21:09.0 +0200
+++ collectd-5.8.1/debian/changelog 2019-11-06 22:34:37.0 +0100
@@ -1,3 +1,20 @@
+collectd (5.8.1-1.4) UNRELEASED; urgency=medium
+
+  * Non-maintainer upload.
+  * Disable building python(2) plugin (Closes: #936318)
+  * Add debian/patches/fix-network-parse-strcpy-off-by-one.patch
+- from upstream commit 28c83da870b4df4a311a5ef20a5ca37d3c84c638
+  * Add debian/patches/fix-build-with-newer-gpsd.patch (Closes: #926528)
+- from upstream commit 991a6d3fd38c2435d94de3853fda36b3330cf6ab
+  * Add debian/patches/fix-dpdk-deprecation-warn.patch
+- from upstream commit 6f7193eb7af4a76239332988ac280
+  * Argh! Still wont build add --disable-werror configure flag!
+  * Add fix-test-common-segfault.patch by yours truely!
+- gcc will optimize out condition (since we've already written
+  to ptr using memcpy?). Thus dereference ptr even when it's NULL!
+
+ -- Andreas Henriksson   Wed, 06 Nov 2019 22:34:37 +0100
+
 collectd (5.8.1-1.3) unstable; urgency=medium
 
   * Non-maintainer upload.
diff -Nru collectd-5.8.1/debian/collectd.conf 
collectd-5.8.1/debian/collectd.conf
--- collectd-5.8.1/debian/collectd.conf 2018-11-22 23:16:41.0 +0100
+++ collectd-5.8.1/debian/collectd.conf 2019-11-06 22:33:53.0 +0100
@@ -169,7 +169,6 @@
 #LoadPlugin powerdns
 LoadPlugin processes
 #LoadPlugin protocols
-#LoadPlugin python
 #LoadPlugin redis
 #LoadPlugin rrdcached
 LoadPlugin rrdtool
@@ -1133,17 +1132,6 @@
 #  IgnoreSelected false
 #
 
-#
-#  ModulePath "/path/to/your/python/modules"
-#  LogTraces true
-#  Interactive true
-#  Import "spam"
-#
-#  
-#  spam "wonderful" "lovely"
-#  
-#
-
 #
 #  
 #  Host "redis.example.com"
diff -Nru collectd-5.8.1/debian/control collectd-5.8.1/debian/control
--- collectd-5.8.1/debian/control   2019-04-06 14:20:16.0 +0200
+++ collectd-5.8.1/debian/control   2019-11-06 22:33:05.0 +0100
@@ -65,7 +65,6 @@
  protobuf-c-compiler,
  protobuf-compiler (>= 3.0.0),
  protobuf-compiler-grpc [amd64 arm64 armel armhf i386 ppc64el powerpc],
- python-dev,
  riemann-c-client
 Build-Conflicts: libpthread-dev, libhal-dev
 Standards-Version: 4.2.1
@@ -189,7 +188,6 @@
* PowerDNS name server statistics: powerdns
* number of processes: processes
* information about network protocols: protocols
-   * embedded Python interpreter: python
* Redis server statistics: redis
* write data via the RRD accelerator daemon: rrdcached
* output to RRD files: rrdtool
diff -Nru collectd-5.8.1/debian/patches/fix-build-with-newer-gpsd.patch 
collectd-5.8.1/debian/patches/fix-build-with-newer-gpsd.patch
--- collectd-5.8.1/debian/patches/fix-build-with-newer-gpsd.patch   
1970-01-01 01:00:00.0 +0100
+++ collectd-5.8.1/debian/patches/fix-build-with-newer-gpsd.patch   
2019-11-06 22:34:37.0 +0100
@@ -0,0 +1,36 @@
+From 991a6d3fd38c2435d94de3853fda36b3330cf6ab Mon Sep 17 00:00:00 2001
+From: Baruch Siach 
+Date: Tue, 9 Oct 2018 19:57:21 +0300
+Subject: [PATCH] gps plugin: fix build with newer gpsd
+
+gpsd version 3.18 changed the prototype of gps_read(). Make the
+gps_read() call depend on GPSD_API_MAJOR_VERSION to fix that.
+
+This fixes build failures like:
+
+gps.c: In function 'cgps_thread':
+gps.c:144:11: error: too few arguments to function 'gps_read'
+   if (gps_read(_conn) == -1) {
+  ^~~~
+---
+ src/gps.c | 7 ++-
+ 1 file changed, 6 insertions(+), 1 deletion(-)
+
+diff --git a/src/gps.c b/src/gps.c
+index 1d32d04926..b22c3a2e5e 100644
+--- a/src/gps.c
 b/src/gps.c
+@@ -141,7 +141,12 @@ static void *cgps_thread(void *pData) {
+ continue;
+   }
+ 
+-  if 

Bug#944260: lintian: Add a detection/tag for when compat is >> 10 and cdbs in build-depends

[Chris Lamb]

severity 944260 wishlist
tags 944260 + moreinfo
thanks

Hi Thomas,

> Since Debhelper >= 10.9.2 and higher (and therefore compat >= 11), 
> there is a known issue in CDBS (refer to bug #885407 [1]) with the use 
> of dh_systemd_enable instead of dh_installsystemd.

So, I'm a little hesitant — we should spend our limited energy fixing
the aforementioned bug rather than also spending our time here in
Lintian warning about it; we will have to do the former *anyway*,
after all.

(Does this affect all packages or only ones using systemd? I assume
the package does not FTBFS, merely fails to work properly at runtime?)


Best wishes,

-- 
  ,''`.
 : :'  : Chris Lamb
 `. `'`  la...@debian.org  chris-lamb.co.uk
   `-

Bug#942272: gnome-shell: numlock state is reversed

[Jean-Marc]

Hi EdiD,

I got numlock state problems too with this gnome-shell version.

Mine were no similar to yours but seem to disappear with the last gnome-shell 
version (3.34.1+git20191024-1).

Can you check if your problems still persist ?

And confirm it in this bug report ?

Regards,

Jean-Marc 
https://6jf.be/keys/ED863AD1.txt


pgpTkKpcYvSeA.pgp
Description: PGP signature

Bug#944262: ITP: adios2 -- The Adaptable I/O System version 2

[Godoy, William F.]

Package: adios2
Severity: wishlist

Description:
ADIOS 2 is a framework designed for scientific data I/O to publish and 
subscribe (put/get) data when and where required. ADIOS 2 transports data as 
groups of self-describing variables and attributes across different media types 
(such as files, wide-area-networks, and remote direct memory access) using a 
common application programming interface for all transport modes. ADIOS 2 can 
be used on supercomputers, cloud systems, and personal computers.

URL:
https://github.com/ornladios/ADIOS2

Copyright:
https://github.com/ornladios/ADIOS2/blob/master/Copyright.txt
Apache 2 License

Target:
Debian Science team
https://wiki.debian.org/DebianScience

Bug#944261: ITB: python-seaborn -- Python data visualization library

[Christian Kastner]

Package: wnpp
Severity: wishlist
Owner: Christian Kastner 
X-Debbugs-CC: debian-de...@lists.debian.org, debian-pyt...@lists.debian.org, 
debian-scie...@lists.debian.org

* Package name: python-seaborn
  Version : 0.9.0
  Upstream Author : Michael Waskom 
* URL : https://seaborn.pydata.org
* License : BSD-3-clause
  Programming Lang: Python3
  Description : Python data visualization library

Seaborn is a Python data visualization library based on matplotlib. It
provides a high-level interface for drawing attractive and informative
statistical graphics.

This will be maintained within the Debian Science Team.

Bug#944098: lintian: changelog-file-missing-explicit-entry false positive for changelog with: 2, 2+deb10u1, 2+deb10u2

[Michael Biebl]

Package: lintian
Version: 2.33.0
Followup-For: Bug #944098

I can confirm this issue:

W: systemd source: changelog-file-missing-explicit-entry 241-7~deb10u1 -> 241-7 
(missing) -> 241-7~deb10u2


...

systemd (241-7~deb10u2) buster; urgency=medium

  * core: never propagate reload failure to service result.
Fixes a regression introduced in v239 where the main process of a
service unit gets killed on reload if ExecReload fails. (Closes: #936032)
  * shared/seccomp: add sync_file_range2.
Some architectures need the arguments to be reordered because of alignment
issues. Otherwise, it's the same as sync_file_range.
Fixes sync_file_range failures in nspawn containers on arm, ppc.
(Closes: #935091)
  * core: factor root_directory application out of apply_working_directory.
Fixes RootDirectory not working when used in combination with User.
(Closes: #939408)
  * shared/bus-util: drop trusted annotation from
bus_open_system_watch_bind_with_description().
This ensures that access controls on systemd-resolved's D-Bus interface
are enforced properly.
(CVE-2019-15718, Closes: #939353)
  * login: add a missing error check for session_set_leader()
Fixes assertion due to insufficient function return check.
(Closes: #939998)
  * d/e/r/73-usb-net-by-mac.rules: import net.ifnames only for network devices
(Closes: #934589)
  * d/e/r/73-usb-net-by-mac.rules: skip if iface name was provided by user-space
  * namespace: make MountFlags=shared work again (Closes: #939551)
  * mount/generators: do not make unit wanted by its device unit.
Among other things, this fixes StopWhenUnneeded=true being broken for
mount units. (Closes: #941758)

 -- Michael Biebl   Wed, 16 Oct 2019 15:24:54 +0200

systemd (241-7~deb10u1) buster; urgency=medium

  * Rebuild for buster

 -- Michael Biebl   Tue, 20 Aug 2019 13:50:42 +0200

systemd (241-7) unstable; urgency=medium

  [ Michael Biebl ]
  * network: Fix failure to bring up interface with Linux kernel 5.2.
Backport two patches from systemd master in order to fix a bug with 5.2
kernels where the network interface fails to come up with the following
error: "enp3s0: Could not bring up interface: Invalid argument"
(Closes: #931636)
  * Use /usr/sbin/nologin as nologin shell.
In Debian the nologin shell is installed in /usr/sbin, not /sbin.
(Closes: #931850)

  [ Mert Dirik ]
  * 40-systemd: Don't fail if SysV init script uses set -u and $1 is unset
(Closes: #931719)

 -- Michael Biebl   Thu, 18 Jul 2019 19:38:23 +0200





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

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

Versions of packages lintian depends on:
ii  binutils 2.33.1-2
ii  bzip21.0.8-2
ii  coreutils8.30-3+b1
ii  diffstat 1.62-1+b1
ii  dpkg 1.19.7
ii  dpkg-dev 1.19.7
ii  file 1:5.37-6
ii  gettext  0.19.8.1-9
ii  gpg  2.2.17-3
ii  intltool-debian  0.35.0+20060710.5
ii  libapt-pkg-perl  0.1.36+b2
ii  libarchive-zip-perl  1.67-1
ii  libberkeleydb-perl   0.62-1+b1
ii  libcapture-tiny-perl 0.48-1
ii  libcgi-pm-perl   4.44-1
ii  libclass-accessor-perl   0.51-1
ii  libclass-xsaccessor-perl 1.19-3+b3
ii  libclone-perl0.41-1+b2
ii  libdigest-sha-perl   6.02-1+b2
ii  libdpkg-perl 1.19.7
ii  libemail-valid-perl  1.202-1
ii  libfile-basedir-perl 0.08-1
ii  libfile-find-rule-perl   0.34-1
ii  libio-async-loop-epoll-perl  0.20-1
ii  libio-async-perl 0.74-1
ii  libipc-run-perl  20180523.0-2
ii  liblist-compare-perl 0.53-1
ii  liblist-moreutils-perl   0.416-1+b5
ii  libmldbm-perl2.05-2
ii  libmoo-perl  2.003006-1
ii  libnamespace-clean-perl  0.27-1
ii  libpath-tiny-perl0.108-1
ii  libtext-levenshtein-perl 0.13-1
ii  libtimedate-perl 2.3000-2
ii  libtry-tiny-perl 0.30-1
ii  libtype-tiny-perl1.004004-1
ii  liburi-perl  1.76-1
ii  libxml-simple-perl   2.25-1
ii  libyaml-libyaml-perl 0.80+repack-2+b1
ii  man-db   2.9.0-1
ii  patchutils   0.3.4-2+b1
ii  perl [libdigest-sha-perl]5.30.0-9
ii  t1utils  1.41-3
ii  xz-utils 5.2.4-1+b1

Versions of packages lintian 

Bug#944154: dehydrated: broken in oldstable: "JWS has no anti-replay nonce"

[Dominic Hargreaves]

On Tue, Nov 05, 2019 at 01:49:29PM +0100, Mattia Rizzolo wrote:
> On Tue, Nov 05, 2019 at 09:35:48AM +, Dominic Hargreaves wrote:
> > I understand that you probably won't fix this, but hopefully by filing
> > this we can raise awareness. Perhaps the package should be removed
> > altogether from oldstable?
> 
> I actually intend to fix this, but most likely the permanent fix will be
> a whole upgrade of dehydrated to the version that is currently in
> buster.

Brilliant, thanks! Not sure where I got the idea that you wouldn't
want to fix it then...

Cheers
Dominic

Bug#674857: Couldn't open /etc/securetty: No such file or directory

[Thorsten Glaser]

Hi everyone,

when will something happen to not fill syslog with these messages
(unless deserved, such as if there is really something to warn about)?

It’s not even stated yet whether the suggested change to the config
is safe to apply…

Thanks in advance,
//mirabilos
-- 
tarent solutions GmbH
Rochusstraße 2-4, D-53123 Bonn • http://www.tarent.de/
Tel: +49 228 54881-393 • Fax: +49 228 54881-235
HRB 5168 (AG Bonn) • USt-ID (VAT): DE122264941
Geschäftsführer: Dr. Stefan Barth, Kai Ebenrett, Boris Esser, Alexander Steeg

Bug#944260: lintian: Add a detection/tag for when compat is >> 10 and cdbs in build-depends

[Thomas Ward]

package: lintian

Since Debhelper >= 10.9.2 and higher (and therefore compat >= 11), there 
is a known issue in CDBS (refer to bug #885407 [1]) with the use of 
dh_systemd_enable instead of dh_installsystemd.  This has been on the 
record since 2017 with the last activity on the bug over a year ago 
without a fix for this.  As such, any packages with DH compat >> 10 will 
fail to work when CDBS is the system in use (and in the 
build-dependencies with its rules included in debian/rules).


Therefore, I propose that a Warning indicator be added to Lintian 
checking source packages, etc. for any cases where the compat level is 
defined as >> 10, and where CDBS is in the build dependencies, defining 
something similar to the following:


"The use of CDBS with compat levels higher than 10 is not permitted.  
CDBS is not compatible with Debhelper compatibility higher than 10 due 
to the deprecation of dh_systemd_enable in favor of dh_installsystemd 
and CDBS not being updated with this change (refer to Debian Bug 
#885407).  Source packages should not define cdbs as a build dependency 
if using a compat level higher than 10."


This may also require a policy decision/change in the future, but in my 
opinion for now Lintian should throw a warning (or at least an 
Informational level notice) about CDBS not working with later compat.



Thomas


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

Bug#943875: Acknowledgement (gvfs not upgradable due to some dependencies)

[Ben Hutchings]

Control: reassign 943875 fuse3
Control: forcemerge 943896 943875
Control: severity 943896 important
Control: affects 943896 gvfs-fuse

On Thu, 31 Oct 2019 15:57:32 -0400 Santiago Batista  
wrote:
> Possibly this is the actual source for this bug:
> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=943896

Assuming that's the case, I'm merging them and using "affects".

I'm also increasing the severity since this causes regressions on
upgrade.

Ben.

> On Thu, Oct 31, 2019 at 1:03 PM Domenico Cufalo  wrote:
> 
> > Yes, I can confirm that installing fuse3 solves the problem, but I think
> > the update process should be more automatic.
> >
> > Anyway, thank you so much for suggesting me this workaround! :-)
> >
-- 
Ben Hutchings
Tomorrow will be cancelled due to lack of interest.



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

Bug#935503: (no subject)

[Lennart Sauerbeck]

With the versions currently available in unstable (gnucash 3.7-2;
libaqbanking43 5.99.43beta-1) this now works for me with the remote bank
GLS.

I had to re-run the account setup procedure according to [0] though.

Best Regards,
Lennart Sauerbeck

[0] https://www.aquamaniac.de/rdm/projects/aqbanking/wiki/PSD2

Bug#885239: xbindkeys: please migrate to guile-2.2

[Martin Samuelsson]

Rob Browning @ 2017-12-25 (Monday), 16:17 (-0600)


I'd like to remove guile-2.0 before the buster release, so please
migrate to guile-2.2 when you can.


A relevant link here would be the announcement for guile-2.2:

https://www.gnu.org/software/guile/news/gnu-guile-220-released.html

I'm neither a power user of xbindkeys nor do I understand what role guile 
plays as one of its dependencies, but I do rely on the tool enough to wish 
it to remain in Debian.


The release notes seems to suggest the new version mostly has improvements.  
Even if it brings in some api breakage, it's mostly due to odd corner cases.  
At least that's the way I understood it from skimming the text briefly.


Updating 2.0 to 2.2 generates a build that works for me and my use cases.  
Couldn't find any test suite or some other way to easily perform further 
verification, but I would assume bumping the version number is all that is 
needed to close this issue? A patch doing is attached.

--
/Martin

This sender address might be blocked due to exessive spam from the bug 
tracker. Assume I recieve emails sent to the bug report, and please see 
https://bugs.debian.org/199392#40 for a way to contact me privately if 
required.
diff -ur xbindkeys-1.8.6/debian/changelog xbindkeys-1.8.6patched/debian/changelog
--- xbindkeys-1.8.6/debian/changelog	2019-11-06 21:41:16.0 +0100
+++ xbindkeys-1.8.6patched/debian/changelog	2019-11-06 21:17:21.394869356 +0100
@@ -1,3 +1,10 @@
+xbindkeys (1.8.6-2) UNRELEASED; urgency=medium
+
+  * Non-maintainer upload.
+  * Rebuild towards guile-2.2 (Closes #885239).
+
+ -- Martin Samuelsson   Wed, 06 Nov 2019 21:14:49 +0100
+
 xbindkeys (1.8.6-1) unstable; urgency=medium
 
   * New upstream version
diff -ur xbindkeys-1.8.6/debian/control xbindkeys-1.8.6patched/debian/control
--- xbindkeys-1.8.6/debian/control	2019-11-06 21:41:16.0 +0100
+++ xbindkeys-1.8.6patched/debian/control	2019-11-06 21:04:50.494504691 +0100
@@ -3,7 +3,7 @@
 Priority: optional
 Maintainer: Joerg Jaspert 
 Uploaders: Ricardo Mones 
-Build-Depends: debhelper (>= 9), libx11-dev, libxt-dev, guile-2.0-dev, autotools-dev
+Build-Depends: debhelper (>= 9), libx11-dev, libxt-dev, guile-2.2-dev, autotools-dev
 Standards-Version: 3.9.5
 Homepage: http://www.nongnu.org/xbindkeys/
 

Bug#943891: [pkg-go] Bug#943891: umoci: autopkgtest regression: bug in the autopkgtest-pkg-go

[Dmitry Smirnov]

On Thursday, 7 November 2019 3:48:01 AM AEDT Shengjing Zhu wrote:
> On Wed, Nov 6, 2019 at 7:36 AM Dmitry Smirnov  wrote:
> First it was called from /usr/bin/autodep8
> Then /usr/share/autodep8/support/go/generate
> Finally /usr/bin/dh_golang_autopkgtest
> 
> /usr/bin/dh_golang_autopkgtest is provided by dh-golang,

Thank you. Now we know where it is! :)


> PS. I don't understand this script.

Me neither. But I already see problematic area in lines 83...113:

  
https://salsa.debian.org/go-team/packages/dh-golang/blob/master/script/dh_golang_autopkgtest#L83

-- 
Best wishes,
 Dmitry Smirnov.

---

The Catholic and the Communist are alike in assuming that an opponent
cannot be both honest and intelligent.
-- George Orwell


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

Bug#944259: New upstream release (1.20.6)

[Andreas Henriksson]

Package: network-manager
Version: 1.20.4-1
Severity: wishlist
Control: block 944069 by -1

Hello,

a new bugfix release was just tagged 1.20.6. Please consider
packaging it. (This bug report mainly to track iwd 1.0 compatibility.)

Regards,
Andreas Henriksson

Bug#943664: xserver-xorg-video-radeon 19.1 (ppc64) crash at startup: undefined symbol: exaGetPixmapDriverPrivate

[Ralf P.]

Hi.

I assume that the error occurs on the PPC64 system because of
disabled HA (Hardware Acceleration) too:

According to 

   https://bugs.freedesktop.org/show_bug.cgi?id=99851

a "ring 0 test failed" message from drm means that HA gets disabled.


dmesg | grep -i drm

[5.621228] [drm] radeon kernel modesetting enabled.
[5.662906] [drm] initializing kernel modesetting (CEDAR 0x1002:0x68FA 
0x174B:0xE127 0x00).
[5.974683] [drm] GPU not posted. posting now...
[6.017017] [drm] Detected VRAM RAM=1024M, BAR=256M
[6.017018] [drm] RAM width 64bits DDR
[6.082254] [drm] radeon: 1024M of VRAM memory ready
[6.195713] [drm] radeon: 1024M of GTT memory ready.
[6.220009] [drm] Loading CEDAR Microcode
[6.335990] [drm] Internal thermal controller with fan control
[6.364947] [drm] radeon: dpm initialized
[6.396903] [drm] GART: num cpu pages 16384, num gpu pages 262144
[6.458639] [drm] PCIE GART of 1024M enabled (table at 0x0015).
[6.531588] [drm] Supports vblank timestamp caching Rev 2 (21.10.2013).
[6.576700] [drm] Driver supports precise vblank timestamp query.
[6.641177] [drm] radeon: irq initialized.
[6.834702] [drm:.r600_ring_test [radeon]] *ERROR* radeon: ring 0 test 
failed (scratch(0x8504)=0xCAFEDEAD)
[6.863707] [drm] Radeon Display Connectors
[6.880862] [drm] Connector 0:
[6.880863] [drm]   DVI-I-1
[6.880865] [drm]   HPD2
[6.880867] [drm]   DDC: 0x6430 0x6430 0x6434 0x6434 0x6438 0x6438 0x643c 
0x643c
[6.880868] [drm]   Encoders:
[6.880869] [drm] DFP1: INTERNAL_UNIPHY1
[6.880870] [drm] CRT2: INTERNAL_KLDSCP_DAC2
[6.880875] [drm] Connector 1:
[6.902720] [drm]   DVI-I-2
[6.913316] [drm]   HPD4
[6.987101] [drm]   DDC: 0x6440 0x6440 0x6444 0x6444 0x6448 0x6448 0x644c 
0x644c
[7.001856] [drm]   Encoders:
[7.007757] [drm] DFP2: INTERNAL_UNIPHY
[7.016093] [drm] CRT1: INTERNAL_KLDSCP_DAC1
[7.112647] [drm] fb mappable at 0x9036
[7.120638] [drm] vram apper at 0x9000
[7.128797] [drm] size 7733248
[7.134875] [drm] fb depth is 24
[7.141298] [drm]pitch is 6400
[7.212427] radeon :0a:00.0: fb0: radeondrmfb frame buffer device
[7.238821] [drm] Initialized radeon 2.50.0 20080528 for :0a:00.0 on 
minor 0



I tested these kernel versions:
4.18.0-3-powerpc64   (official kernel from Debian PPC64 sid)
4.19.28-rt16 (self compiled, with realtime patches)

Both result in "ring 0 test failed".


In my opinion it would be great if:

1) xserver-xorg-video-radeon_1%3a19.1.0-1 would not fail but fall back to
   frame buffer device like xserver-xorg-video-radeon_1%3a19.0.1-1

2) the "ring 0 test" would not fail
   According to the last post from the link above the failure was
   seen in 4.14.4 and 4.15-rc2 but not in kernel 4.17.2.
   Maybe I should get/compile a linux 4.17.2 kernel.

Thank you and best regards,
Ralf

Bug#944258: lintian 2.32.0~bpo9+1 in stretch-backports depends on coreutils (>= 8.30), but stretch has only 8.26-3

[Felix Lechner]

Hi Christoph,

On Wed, Nov 6, 2019 at 12:48 PM Christoph Berg  wrote:
>
> coreutils:
>   Versionstabelle:
>  *** 8.26-3 500

According to Andreas Beckmann, coreutils 8.30 is in the process of
being ported to stretch.

For details, please have a look at the PS here:

https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=943910#25

Kind regards,
Felix Lechner

CC: Andreas Beckmann

Bug#944258: lintian 2.32.0~bpo9+1 in stretch-backports depends on coreutils (>= 8.30), but stretch has only 8.26-3

[Christoph Berg]

Package: lintian
Version: 2.32.0~bpo9+1
Severity: grave

Package: lintian
Version: 2.32.0~bpo9+1
Installed-Size: 5665
Maintainer: Debian Lintian Maintainers 
Architecture: all
Replaces: funny-manpages (<< 1.3-5.1)
Depends: binutils, bzip2, coreutils (>= 8.30), ...

coreutils:
  Installiert:   8.26-3
  Installationskandidat: 8.26-3
  Versionstabelle:
 *** 8.26-3 500
500 http://debian-approx:/debian stretch/main ppc64el Packages
100 /var/lib/dpkg/status

Christoph

Bug#941078: transition: postgresql-12

[Christoph Berg]

Re: Paul Gevers 2019-11-05 <75a8a466-6338-b4c3-13bf-494498644...@debian.org>
> Hi Christoph,
> 
> Did I see correctly that not much changed in the status of the
> postgresql-12 transition? Are you done uploading and do the other
> packages need binNMU's? Or are you just busy?

Most of the "easy" work is done. The remaining packages need upstream
fixes, which I have started hunting for, but I was pretty busy over
the past days.

I'll try to get some more sorted out tomorrow, and then post a list
here which packages I think should be either ignored, or removed from
testing for now. From there, the way forward would be to ask debci to
test all "good" packages together, or simply to force
postgresql-common into testing and have everything else migrate by the
usual means.

Christoph

Bug#943082: libcxx-serial: Python2 removal in sid/bullseye

[Jochen Sprickerhof]

Hi Alec,

I recently dropped all ROS Python 2 and along the lines 
python-catkin-pkg as well. I found your package only afterwards and I'm 
sorry for braking it. The good news is that the package builds fine 
without python-catkin-pkg, so it could just be dropped. I've uploaded a 
NMU with just this changed to delayed/5, please ping me if I should 
delay it further or drop it.


Cheers Jochen

* mo...@debian.org  [2019-10-23 02:33]:

Source: libcxx-serial
Version: 1.2.1-1
Severity: normal
Tags: sid bullseye
User: debian-pyt...@lists.debian.org
Usertags: py2removal

Python2 becomes end-of-live upstream, and Debian aims to remove
Python2 from the distribution, as discussed in
https://lists.debian.org/debian-python/2019/07/msg00080.html

Your package either build-depends, depends on Python2, or uses Python2
in the autopkg tests (the specific reason can be found searching this
source package in
https://people.debian.org/~morph/mass-bug-py2removal_take2.txt ).
Please stop using Python2, and fix this issue by one of the following
actions.

- Convert your Package to Python3. This is the preferred option.  In
 case you are providing a Python module foo, please consider dropping
 the python-foo package, and only build a python3-foo package.  Please
 don't drop Python2 modules, which still have reverse dependencies,
 just document them.

 This is the preferred option.

- If the package is dead upstream, cannot be converted or maintained
 in Debian, it should be removed from the distribution.  If the
 package still has reverse dependencies, raise the severity to
 "serious" and document the reverse dependencies with the BTS affects
 command.  If the package has no reverse dependencies, confirm that
 the package can be removed, reassign this issue to ftp.debian.org,
 make sure that the bug priority is set to normal and retitle the
 issue to "RM: PKG -- removal triggered by the Python2 removal".

- If the package has still many users (popcon >= 300), or is needed to
 build another package which cannot be removed, document that by
 adding the "py2keep" user tag (not replacing the py2remove tag),
 using the debian-pyt...@lists.debian.org user.  Also any
 dependencies on an unversioned python package (python, python-dev)
 must not be used, same with the python shebang.  These have to be
 replaced by python2/python2.7 dependencies and shebang.

 This is the least preferred option.

If there are questions, please refer to the wiki page for the removal:
https://wiki.debian.org/Python/2Removal, or ask for help on IRC
#debian-python, or the debian-pyt...@lists.debian.org mailing list.


signature.asc
Description: PGP signature

Bug#944257: linux-image-5.3.0-1-amd64: Does not wake up after suspend-to-RAM

[Wenceslao]

Package: src:linux
Version: 5.3.7-1
Severity: important

Dear Maintainer,


   * What led up to the situation?
Upgrade to 5 kernel
   * What exactly did you do (or not do) that was effective (or
 ineffective)?
Upgrade to 5.1, 5.2 and 5.3 kernel
   * What was the outcome of this action?
System still does not wake up after suspend to RAM
   * What outcome did you expect instead?
Normal wake-up



-- Package-specific info:
** Version:
Linux version 5.3.0-1-amd64 (debian-ker...@lists.debian.org) (gcc version 9.2.1 
20191008 (Debian 9.2.1-9)) #1 SMP Debian 5.3.7-1 (2019-10-19)

** Command line:
BOOT_IMAGE=/boot/vmlinuz-5.3.0-1-amd64 
root=UUID=99607924-e7e4-49c3-902e-6fabdeb450f1 ro quiet

** Tainted: WOE (12800)
 * Taint on warning.
 * Out-of-tree module has been loaded.
 * Unsigned module has been loaded.

** Kernel log:
[  101.442927] OOM killer disabled.
[  101.443013] PM: Marking nosave pages: [mem 0x-0x0fff]
[  101.443014] PM: Marking nosave pages: [mem 0x00058000-0x00058fff]
[  101.443014] PM: Marking nosave pages: [mem 0x0009d000-0x000f]
[  101.443016] PM: Marking nosave pages: [mem 0xc4a7f000-0xc4aa9fff]
[  101.443017] PM: Marking nosave pages: [mem 0xce3ae000-0xcfffdfff]
[  101.443120] PM: Marking nosave pages: [mem 0xc000-0x]
[  101.443449] PM: Basic memory bitmaps created
[  101.443490] PM: Preallocating image memory... done (allocated 784530 pages)
[  101.738515] PM: Allocated 3138120 kbytes in 0.29 seconds (10821.10 MB/s)
[  101.738515] Freezing remaining freezable tasks ... (elapsed 0.001 seconds) 
done.
[  101.740910] printk: Suspending console(s) (use no_console_suspend to debug)
[  101.741064] wlan0: deauthenticating from --- by local choice (Reason: 
3=DEAUTH_LEAVING)
[  101.741186] azx_single_send_cmd: 15 callbacks suppressed
[  102.345654] ACPI: EC: interrupt blocked
[  102.364395] ACPI: Preparing to enter system sleep state S4
[  102.368754] ACPI: EC: event blocked
[  102.368755] ACPI: EC: EC stopped
[  102.368755] PM: Saving platform NVS memory
[  102.368970] Disabling non-boot CPUs ...
[  102.369264] IRQ 130: no longer affine to CPU1
[  102.370282] smpboot: CPU 1 is now offline
[  102.374004] smpboot: CPU 2 is now offline
[  102.376929] IRQ 127: no longer affine to CPU3
[  102.376933] IRQ 129: no longer affine to CPU3
[  102.377951] smpboot: CPU 3 is now offline
[  102.382146] PM: Creating hibernation image:
[  102.581977] PM: Need to copy 778090 pages
[  102.581980] PM: Normal pages needed: 778090 + 1024, available pages: 3353232
[  102.382709] PM: Restoring platform NVS memory
[  102.382792] ACPI: EC: EC started
[  102.383874] Enabling non-boot CPUs ...
[  102.383945] x86: Booting SMP configuration:
[  102.383946] smpboot: Booting Node 0 Processor 1 APIC 0x2
[  102.385740] CPU1 is up
[  102.385782] smpboot: Booting Node 0 Processor 2 APIC 0x1
[  102.387629] CPU2 is up
[  102.387672] smpboot: Booting Node 0 Processor 3 APIC 0x3
[  102.389050] CPU3 is up
[  102.391319] ACPI: Waking up from system sleep state S4
[  102.403587] ACPI: EC: interrupt unblocked
[  102.403814] pcieport :00:1c.0: Intel SPT PCH root port ACS workaround 
enabled
[  102.404092] pcieport :00:1c.2: Intel SPT PCH root port ACS workaround 
enabled
[  102.543326] usb usb1: root hub lost power or was reset
[  102.543328] usb usb2: root hub lost power or was reset
[  102.544365] ACPI: EC: event unblocked
[  102.554978] sd 1:0:0:0: [sda] Starting disk
[  102.855353] snd_hda_codec_generic hdaudioC0D2: Unable to sync register 
0x2f0d00. -5
[  102.855478] snd_hda_codec_generic hdaudioC0D2: Unable to sync register 
0x2f0d00. -5
[  102.870645] ata2: SATA link up 6.0 Gbps (SStatus 133 SControl 300)
[  102.872165] ata2.00: ACPI cmd ef/02:00:00:00:00:a0 (SET FEATURES) succeeded
[  102.872171] ata2.00: ACPI cmd f5/00:00:00:00:00:a0 (SECURITY FREEZE LOCK) 
filtered out
[  102.872887] ata2.00: ACPI cmd ef/10:09:00:00:00:a0 (SET FEATURES) succeeded
[  102.873686] ata2.00: supports DRM functions and may not be fully accessible
[  102.878752] ata2.00: ACPI cmd ef/02:00:00:00:00:a0 (SET FEATURES) succeeded
[  102.878758] ata2.00: ACPI cmd f5/00:00:00:00:00:a0 (SECURITY FREEZE LOCK) 
filtered out
[  102.879469] ata2.00: ACPI cmd ef/10:09:00:00:00:a0 (SET FEATURES) succeeded
[  102.880264] ata2.00: supports DRM functions and may not be fully accessible
[  102.883745] ata2.00: configured for UDMA/133
[  102.903241] usb 1-5: reset full-speed USB device number 2 using xhci_hcd
[  103.129017] snd_hda_codec_realtek hdaudioC0D0: Unable to sync register 
0x1f0e00. -5
[  103.129363] snd_hda_codec_realtek hdaudioC0D0: Unable to sync register 
0x1f0e00. -5
[  103.179256] usb 1-7: reset full-speed USB device number 3 using xhci_hcd
[  103.260446] psmouse serio1: synaptics: queried max coordinates: x [..5712], 
y [..4780]
[  103.291681] psmouse serio1: synaptics: queried min coordinates: x [1232..], 
y [1074..]
[  103.455152] usb 1-8: reset high-speed USB device number 4 using xhci_hcd
[  103.611731] PM: 

Bug#944256: linux-image-4.19.0-6-armmp: please enable cpufreq for AM335x (BBB)

[Sascha Silbe]

Source: linux
Version: 4.19.67-2+deb10u1
Severity: wishlist

Dear Maintainer,

currently it's impossible to reduce the CPU frequency (e.g. for thermal
management) on AM335x based boards like the BeagleBone Black when
running the Debian kernel. Please enable cpufreq support for those
boards. For starters enabling CONFIG_ARM_TI_CPUFREQ will be required;
not sure if other options are missing, too.

Kind regards,
Sascha Silbe

-- Package-specific info:
** Version:
Linux version 4.19.0-6-armmp (debian-ker...@lists.debian.org) (gcc version 
8.3.0 (Debian 8.3.0-6)) #1 SMP Debian 4.19.67-2 (2019-08-28)

** Command line:
quiet

** Not tainted

** Kernel log:
Unable to read kernel log; any relevant messages should be attached

** Model information
Hardware: Generic AM33XX (Flattened Device Tree)
Revision: 
Device Tree model: TI AM335x BeagleBone Black

** Loaded modules:
tun
nls_ascii
nls_cp437
vfat
fat
usbhid
hid
snd_soc_hdmi_codec
snd_soc_simple_card
snd_soc_simple_card_utils
snd_soc_davinci_mcasp
snd_soc_edma
snd_soc_sdma
tilcdc
tda998x
snd_soc_core
omap_rng
drm_kms_helper
rng_core
snd_pcm_dmaengine
snd_pcm
snd_timer
drm
snd
soundcore
cec
at24
cppi41
omap_wdt
leds_gpio
sch_fq_codel
ip_tables
x_tables
autofs4
ext4
crc16
mbcache
jbd2
crc32c_generic
fscrypto
ecb
smsc
davinci_mdio
musb_dsps
musb_hdrc
udc_core
usbcore
phy_am335x
phy_generic
phy_am335x_control
ti_cpsw
cpsw_ale
cpsw_common
davinci_cpdma
omap_hsmmc
musb_am335x
tps65217

** PCI devices:
not available

** USB devices:
[removed]


-- System Information:
Debian Release: 10.1
  APT prefers stable-updates
  APT policy: (990, 'stable-updates'), (990, 'stable'), (100, 'testing')
Architecture: armhf (armv7l)

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

Versions of packages linux-image-4.19.0-6-armmp depends on:
ii  initramfs-tools [linux-initramfs-tool]  0.133+deb10u1
ii  kmod26-1
ii  linux-base  4.6

Versions of packages linux-image-4.19.0-6-armmp recommends:
ii  apparmor 2.13.2-10
ii  firmware-linux-free  3.4

Versions of packages linux-image-4.19.0-6-armmp suggests:
pn  debian-kernel-handbook  
pn  linux-doc-4.19  

Versions of packages linux-image-4.19.0-6-armmp is related to:
pn  firmware-amd-graphics 
pn  firmware-atheros  
pn  firmware-bnx2 
pn  firmware-bnx2x
pn  firmware-brcm80211
pn  firmware-cavium   
pn  firmware-intel-sound  
pn  firmware-intelwimax   
pn  firmware-ipw2x00  
pn  firmware-ivtv 
pn  firmware-iwlwifi  
pn  firmware-libertas 
pn  firmware-linux-nonfree
pn  firmware-misc-nonfree 
pn  firmware-myricom  
pn  firmware-netxen   
pn  firmware-qlogic   
pn  firmware-realtek  
pn  firmware-samsung  
pn  firmware-siano
pn  firmware-ti-connectivity  
pn  xen-hypervisor

-- no debconf information


signature.asc
Description: PGP signature

Bug#944253: dlt-daemon contains example systemd units for binaries in dlt-tools and libdlt-examples

[Martyn Welch]

On Wed, 2019-11-06 at 19:36 +, Martyn Welch wrote:
> Source: dlt-daemon
> Version: 2.18.4-0.1
> Severity: minor
> 
> Dear Maintainer,
> 
> Whilst tweaking the dlt-daemon for a Debian derivative I noticed that
> this
> package ships example systemd unit files which require binaries found
> in the
> dlt-tools and libdlt-examples packages. It is likely that in many
> circumstances
> dlt-daemon will be installed on systems without dlt-tools or libdlt-
> examples
> being present, hence these example units are unusable and are
> essentially cruft
> on many systems that may in fact be limited in storage.
> 
> I have attached a patch which moves the example systemd unit files to
> the
> appropriate packages.
> 

Oops, forgot attachment!

Martyn

> Thanks,
> 
> Martyn
> 
> -- System Information:
> Debian Release: bullseye/sid
>   APT prefers testing
>   APT policy: (500, 'testing')
> Architecture: amd64 (x86_64)
> Foreign Architectures: armhf, i386
> 
> Kernel: Linux 5.2.0-3-amd64 (SMP w/8 CPU cores)
> Kernel taint flags: TAINT_WARN
> Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8),
> LANGUAGE=en_GB:en (charmap=UTF-8)
> Shell: /bin/sh linked to /bin/dash
From f7173da7cdaa484f056565534cf8cf45fb0a362e Mon Sep 17 00:00:00 2001
From: Martyn Welch 
Date: Wed, 6 Nov 2019 19:29:56 +
Subject: [PATCH] Move example systemd units to the appropriate packages

The dlt-daemon package ships example systemd unit files which require
binaries found in the dlt-tools and libdlt-examples packages. It is likely
that in many circumstances dlt-daemon will be installed on systems without
dlt-tools or libdlt-examples being present, hence these example units are
unusable and essentially cruft on many systems that may in fact be limited
in storage.

Move the example systemd unit files to the appropriate packages.

Signed-off-by: Martyn Welch 
---
 debian/dlt-daemon.install  | 3 ---
 debian/dlt-tools.install   | 2 ++
 debian/libdlt-examples.install | 1 +
 3 files changed, 3 insertions(+), 3 deletions(-)

diff --git a/debian/dlt-daemon.install b/debian/dlt-daemon.install
index 966fb63..a7ae18e 100644
--- a/debian/dlt-daemon.install
+++ b/debian/dlt-daemon.install
@@ -3,6 +3,3 @@ etc/dlt_gateway.conf
 usr/bin/dlt-daemon
 usr/share/man/man1/dlt-daemon.*
 usr/share/man/man5/dlt.conf.*
-usr/lib/systemd/system/dlt-adaptor-udp.service /usr/share/doc/dlt-daemon/examples
-usr/lib/systemd/system/dlt-example-user.service /usr/share/doc/dlt-daemon/examples
-usr/lib/systemd/system/dlt-receive.service /usr/share/doc/dlt-daemon/examples
diff --git a/debian/dlt-tools.install b/debian/dlt-tools.install
index e7c2a0c..3a318af 100644
--- a/debian/dlt-tools.install
+++ b/debian/dlt-tools.install
@@ -14,3 +14,5 @@ usr/share/man/man1/dlt-*-ctrl*
 usr/share/man/man1/dlt-receive*
 usr/share/man/man1/dlt-system*
 usr/share/man/man5/dlt-system*
+usr/lib/systemd/system/dlt-adaptor-udp.service /usr/share/doc/dlt-tools/examples
+usr/lib/systemd/system/dlt-receive.service /usr/share/doc/dlt-tools/examples
diff --git a/debian/libdlt-examples.install b/debian/libdlt-examples.install
index 960d661..e16a1d1 100644
--- a/debian/libdlt-examples.install
+++ b/debian/libdlt-examples.install
@@ -4,3 +4,4 @@ examples/* /usr/share/doc/libdlt-examples
 src/examples/* /usr/share/doc/libdlt-examples
 doc/*.txt /usr/share/doc/libdlt-examples
 doc/images/* /usr/share/doc/libdlt-examples
+usr/lib/systemd/system/dlt-example-user.service /usr/share/doc/libdlt-examples/examples
-- 
2.24.0.rc1

Bug#828732: Fwd: Python 3.x does not allow to run code (EMailHarvester) that it is supposed to...

[Robert Dixon]

I did everything as you described until the install I ran pip install not
pip3. As it installed I received a warning about python 2.7 coming to an
end which was the key. Run this, Open terminal cd EmailHarvester then
python2.7 ./EmailHarvester.py It should fire right up. Good luck.
Robert

Bug#944255: ddd: Dependency on "xfonts-100dpi" package must be added to ddd

[Sam Protsenko]

Package: ddd
Version: 1:3.3.12-5.2
Severity: important

When running ddd from terminal, warnings like these appear (in terminal):

Warning: Cannot convert string 
"-*-helvetica-medium-r-*-*-*-120-*-*-*-*-iso8859-*" to type FontStruct
(Annoyed?  Try 'Edit->Preferences->General->Suppress X Warnings'!)
Warning: Cannot convert string 
"-*-helvetica-medium-r-*-*-*-100-*-*-*-*-iso8859-*" to type FontStruct
Warning: Cannot convert string 
"-*-lucidatypewriter-medium-r-*-*-*-120-*-*-*-*-iso8859-*" to type FontStruct
Warning: Cannot convert string 
"-*-lucidatypewriter-bold-r-*-*-*-120-*-*-*-*-iso8859-*" to type FontStruct

and fonts in ddd are rather ugly. This is easily fixed by installing 
xfonts-100dpi package. Please add xfonts-100dpi into ddd dependency list.

This problem is long known, and was reported on [1].

[1] 
https://stackoverflow.com/questions/32533838/warning-when-running-ddd-in-ubuntu

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

Kernel: Linux 5.2.0-3-amd64 (SMP w/4 CPU cores)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, 
TAINT_UNSIGNED_MODULE
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_US:en (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: sysvinit (via /sbin/init)
LSM: AppArmor: enabled

Versions of packages ddd depends on:
ii  libc6   2.29-2
ii  libgcc1 1:9.2.1-8
ii  libstdc++6  9.2.1-8
ii  libtinfo6   6.1+20190803-1
ii  libx11-62:1.6.8-1
ii  libxaw7 2:1.0.13-1+b2
ii  libxm4  2.3.8-2
ii  libxmu6 2:1.1.2-2+b3
ii  libxpm4 1:3.5.12-1
ii  libxt6  1:1.1.5-1+b3

Versions of packages ddd recommends:
ii  gdb 8.3.1-1
ii  sensible-utils  0.0.12

Versions of packages ddd suggests:
ii  cups-bsd [lpr]   2.3.0-5
pn  ddd-doc  
ii  glibc-doc2.29-2
ii  gnuplot-qt [gnuplot] 5.2.7+dfsg1-5
pn  info 
ii  openssh-client [rsh-client]  1:8.1p1-1
ii  perl 5.30.0-7
pn  pydb 
ii  x11-utils7.7+4
ii  xterm349-1

-- no debconf information

Bug#944254: ocaml-nox: Files overwrite /usr/lib/ocaml/bigarray.cmi in ocaml-base-nox package

[Ben Hutchings]

Control: reassign -1 ocaml-base-nox 4.08.1-3

On Mon, 04 Nov 2019 18:17:37 +0100 Christian Marillat  
wrote:
> Package: ocaml-nox
> Version: 4.05.0-12
> Severity: Serious
> 
> Dear Maintainer,
> 
> Preparing to unpack .../ocaml-nox_4.08.1-2_amd64.deb ...
> Unpacking ocaml-nox (4.08.1-2) over (4.05.0-12) ...
> dpkg: error processing archive 
> /var/cache/apt/archives/ocaml-nox_4.08.1-2_amd64.deb (--unpack):
>  trying to overwrite '/usr/lib/ocaml/bigarray.cmi', which is also in package 
> ocaml-base-nox 4.05.0-12
> dpkg-deb: error: paste subprocess was killed by signal (Broken pipe)

This was fixed.

> Preparing to unpack .../ocaml-base-nox_4.08.1-2_amd64.deb ...
> Unpacking ocaml-base-nox (4.08.1-2) over (4.05.0-12) ...
> dpkg: error processing archive 
> /var/cache/apt/archives/ocaml-base-nox_4.08.1-2_amd64.deb (--unpack):
>  trying to overwrite '/usr/lib/ocaml/libasmrun_shared.so', which is also in 
> package ocaml-nox 4.05.0-12
> dpkg-deb: error: paste subprocess was killed by signal (Broken pipe)

But this error still occurs.

Ben.

> Errors were encountered while processing:
>  /var/cache/apt/archives/ocaml-nox_4.08.1-2_amd64.deb
>  /var/cache/apt/archives/ocaml-base-nox_4.08.1-2_amd64.deb 
-- 
Ben Hutchings
Tomorrow will be cancelled due to lack of interest.



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

Bug#944060: exim4-daemon-light: FTBFS (testsuite error) on mipsel

[Andreas Metzler]

On 2019-11-03 Andreas Metzler  wrote:
> Package: exim4-daemon-light
> Version: 4.93~RC0-1
> Severity: serious
> Tags: ftbfs
> Justification: fails to build from source (but built successfully in the past)

> 4.93~RC0-1 and later (including 4.93~RC1-2) FTBFS on mipsel, the binary
> is built but broken.

> /path/to/exim -C /dev/null -be '${if bool{0}{yes}{no}}'
> fails with
> 2019-11-03 17:50:00 failed to malloc 2008002776 bytes of memory: called from 
> line 3359 in readconf_main

git biscect finds ...
(sid_mipsel-dchroot)ametzler@eller:~/EXIM4/exim$ git bisect good
f3ebb786e451da973560f1c9d8cdb151d25108b5 is the first bad commit
commit f3ebb786e451da973560f1c9d8cdb151d25108b5
Author: Jeremy Harris 
Date:   Thu Jul 25 12:06:07 2019 +0100

Track tainted data and refuse to expand it
[...]

I used the attached script/compilerflags and Local/Makefile to reproduce.

cu Andreas


-- 
`What a good friend you are to him, Dr. Maturin. His other friends are
so grateful to you.'
`I sew his ears on from time to time, sure'
#!/bin/sh

set -e

rm -rf btree
mkdir -p btree
cp -a src/* btree/
mkdir -p btree/Local
cp -a ~/EXIM4/Makefile btree/Local/
echo 'SUPPORT_TLS=yes' >> btree/Local/Makefile
cd btree

env \
PATH='/usr/lib/ccache:/usr/local/bin:/usr/bin:/bin:/usr/local/games:/usr/games' 
\
LC_ALL='C' \
CFLAGS='-g -O2 -fstack-protector-strong -Wformat -Werror=format-security 
-D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64 -D_LARGEFILE_SOURCE 
-fno-strict-aliasing -Wall -Wdate-time -D_FORTIFY_SOURCE=2' \
CPPFLAGS='-Wdate-time -D_FORTIFY_SOURCE=2' \
CXXFLAGS='-g -O2 -fstack-protector-strong -Wformat -Werror=format-security' \
FCFLAGS='-g -O2 -fstack-protector-strong' \
FFLAGS='-g -O2 -fstack-protector-strong' \
GCJFLAGS='-g -O2 -fstack-protector-strong' \
LDFLAGS='-Wl,-z,relro -Wl,-z,now' \
LFLAGS='-Wl,-z,relro -Wl,-z,now' \
OBJCFLAGS='-g -O2 -fstack-protector-strong -Wformat -Werror=format-security' \
OBJCXXFLAGS='-g -O2 -fstack-protector-strong -Wformat -Werror=format-security' \
make FULLECHO='' -j5

for i in `find  -name exim -type f` ; do echo $i ;  $i -C /dev/null -be '${if 
bool{0}{yes}{no}}' ; done
##
#  The Exim mail transport agent #
##

# This is the template for Exim's main build-time configuration file. It
# contains settings that are independent of any operating system. These are
# things that are mostly sysadmin choices. The items below are divided into
# those you must specify, those you probably want to specify, those you might
# often want to specify, and those that you almost never need to mention.

# Edit this file and save the result to a file called Local/Makefile within the
# Exim distribution directory before running the "make" command.

# Things that depend on the operating system have default settings in
# OS/Makefile-Default, but these are overridden for some OS by files
# called called OS/Makefile-. You can further override these by
# creating files called Local/Makefile-, and
# Local/Makefile- (where "" stands for the name of
# your operating system - look at the names in the OS directory to see
# which names are recognized, and "" is derived from the
# environment variable "build")

# However, if you are building Exim for a single OS only, you don't need to
# worry about setting up Local/Makefile-. Any build-time configuration
# settings you require can in fact be placed in the one file called
# Local/Makefile. It is only if you are building for several OS from the same
# source files that you need to worry about splitting off your own OS-dependent
# settings into separate files. (There's more explanation about how this all
# works in the toplevel README file, under "Modifying the building process", as
# well as in the Exim specification.)

# One OS-specific thing that may need to be changed is the command for running
# the C compiler; the overall default is gcc, but some OS Makefiles specify cc.
# You can override anything that is set by putting CC=whatever in your
# Local/Makefile.

# NOTE: You should never need to edit any of the distributed Makefiles; all
# overriding can be done in your Local/Makefile(s). This will make it easier
# for you when the next release comes along.

# The location of the X11 libraries is something else that is quite variable
# even between different versions of the same operating system (and indeed
# there are different versions of X11 as well, of course). The four settings
# concerned here are X11, XINCLUDE, XLFLAGS (linking flags) and X11_LD_LIB
# (dynamic run-time library). You need not worry about X11 unless you want to
# compile the Exim monitor utility. Exim itself does not use X11.

# Another area of variability between systems is the type and location of the
# DBM library package. Exim has support for ndbm, gdbm, tdb, and Berkeley DB.
# By default the code assumes ndbm; this often works with gdbm or DB, provided
# they are correctly installed, 

Bug#944253: dlt-daemon contains example systemd units for binaries in dlt-tools and libdlt-examples

[Martyn Welch]

Source: dlt-daemon
Version: 2.18.4-0.1
Severity: minor

Dear Maintainer,

Whilst tweaking the dlt-daemon for a Debian derivative I noticed that this
package ships example systemd unit files which require binaries found in the
dlt-tools and libdlt-examples packages. It is likely that in many circumstances
dlt-daemon will be installed on systems without dlt-tools or libdlt-examples
being present, hence these example units are unusable and are essentially cruft
on many systems that may in fact be limited in storage.

I have attached a patch which moves the example systemd unit files to the
appropriate packages.

Thanks,

Martyn

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

Kernel: Linux 5.2.0-3-amd64 (SMP w/8 CPU cores)
Kernel taint flags: TAINT_WARN
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8),
LANGUAGE=en_GB:en (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

Bug#669188: Vuelta Ciclistica a chiriqui 2019

[Masster Comunicaciones]

Versión web
https://sable.godaddy.com/c/209650?id=21421.654-109.1.248be6fce74c4a22f96d8314b6971010=eyIlN0IlN0JtaW1pLXNpZ25hdHVyZSU3RCU3RCI6IjE1NTAzMTE0MS0xMTkyMDQ1NjY1My02NmI4ZDE1ZTE2NzJlOTBjMGQxYmE2MGIwY2UxYmM2N2QyNjEwOGExIiwiJTdCJTdCZW1haWxJZCU3RCU3RCI6IjIxNDIxIn0=

Eliminar suscripción
https://gem.godaddy.com/opt_out?pact=21421-155031141-11920456653-66b8d15e1672e90c0d1ba60b0ce1bc67d26108a1=11920456653

Preferencias
https://sable.godaddy.com/c/209650?id=21421.648-110.1.07669da40d7d7a1d840a7917ab547c74=eyIlN0IlN0JtaW1pLXNpZ25hdHVyZSU3RCU3RCI6IjE1NTAzMTE0MS0xMTkyMDQ1NjY1My02NmI4ZDE1ZTE2NzJlOTBjMGQxYmE2MGIwY2UxYmM2N2QyNjEwOGExIiwiJTdCJTdCbWVtYmVyLWlkJTdEJTdEIjoxMTkyMDQ1NjY1MywiJTdCJTdCZW1haWxJZCU3RCU3RCI6IjIxNDIxIn0=

abogados en Panamá y Chiriquí | David, Chiriquí, República de Panamá 426

Bug#944237: sgt-puzzles: Menu bar nearly unreadable

[Ben Hutchings]

Control: tag -1 confirmed

On Wed, 2019-11-06 at 14:27 +0100, Nicolas Patrois wrote:
> Package: sgt-puzzles
> Version: 20170606.272beef-1
> Severity: minor
> 
> Dear Maintainer,
> 
> I don’t know if it’s an upstream bug but the menu bar is white on light grey 
> if
> the window is active (it’s nearly unreadable).
> If the window is inactive, it’s light grey on dark grey and it’s readable.
> Maybe it’s a theme bug (but it’s the only app with this bug) or a GTK bug (if
> it’s GTK).

I've noticed the same issue after I started using the Adwaita-dark
theme.  Both the menu and status bar (in games that use it) are
unreadable.  I just haven't found the time to investigate it yet.

Ben.

-- 
Ben Hutchings
Tomorrow will be cancelled due to lack of interest.




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

Bug#944226: No way to use xheaders in tornado worker

[Chris Lamb]

Hi Enrico,

> I found a non-obvious way, monkey patching tornado.httpserver.HTTPServer
> to default to xheaders=True:

Ooh, how delightful. ;)

Would you like me to forward this issue upstream or would you be able
to do that? (I don't think this is something that Debian should change
independent of upstream, at least unless there was some kind of
disagreement over the fix…)


Best wishes,

-- 
  ,''`.
 : :'  : Chris Lamb
 `. `'`  la...@debian.org  chris-lamb.co.uk
   `-

Bug#944192: python3-h5py: 'import h5py' produces Open MPI message to stderr

[Jameson Graef Rollins]

On Wed, Nov 06 2019, Thibaut Paumard  wrote:
> I believe:
>   - the issue is not very serious, as it will not prevent your code from
> running fine and efficiently (it's only an informative message).

It's true that it does not make it completely unusable, but it's
certainly not usable in any command line application without hacking the
import to suppress this message, which is actually quite problematic.
So I don't think we can simply dismiss this issue...

>   - it is not in python3-h5py but somewhere in the MPI stack (I have no
> time right now for investigating, but I have seen this recently in
> another MPI code: gyoto).

It sounds like this issue should then be forwarded to whichever
underlying library is producing the message.  It's not ok for libraries
to print warnings to stderr/out, unless they can be easily suppressed by
the caller.  But this message can only be suppressed from python with
some very undstandard redirection of stderr at import time.

>   - downgrading only solves your issue because version 2.8.0 was not
> linked with MPI (and therefore may be less efficient, depending on
> hardware).

Well, in fact, importing the MPI version (2.10.0) is about x7 slower
than the non-MPI version (2.8.0), taking almost a full second for just
the import, so not really a clear performance improvement at all:


servo:~ 0$ python3 -c 'import h5py; print(h5py.__version__)'
--
[[4525,1],0]: A high-performance Open MPI point-to-point messaging module
was unable to find any relevant network interfaces:

Module: OpenFabrics (openib)
  Host: servo

Another transport will be used instead, although this may result in
lower performance.

NOTE: You can disable this warning by setting the MCA parameter
btl_base_warn_component_unused to 0.
--
2.10.0
servo:~ 0$ multitime -qq -n 10 python3 -c 'import h5py'
===> multitime results
1: -qq python3 -c "import h5py"
MeanStd.Dev.Min Median  Max
real0.973   0.027   0.932   0.967   1.022   
user0.200   0.017   0.159   0.201   0.221   
sys 0.068   0.014   0.034   0.069   0.093
servo:~ 0$ 


servo:~ 0$ python3 -c 'import h5py; print(h5py.__version__)'
2.8.0
servo:~ 0$ multitime -qq -n 10 python3 -c 'import h5py'
===> multitime results
1: -qq python3 -c "import h5py"
MeanStd.Dev.Min Median  Max
real0.146   0.012   0.118   0.151   0.156   
user0.119   0.010   0.103   0.121   0.134   
sys 0.027   0.008   0.016   0.027   0.044   
servo:~ 0$ 

Bug#944252: buster-pu: package standardskriver/0.0.3-2+deb10u1

[Mike Gabriel]

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

Dear Release Team,

today I stumbled over a flaw in the standardskriver package version in buster...

++ Add 0002_standardskriver-Use-ip-command-rather-than-deprecate.patch.
+  Use external "ip" command rather than deprecated "ifconfig" command.
+  This fixes (essential) local system's IPv4 detection. (Closes: #944244).

This renders the standardskriver tool unusable. It relies on IPv4
detection for the local system to decide what default printer to set for
a logging in user.

++ Add 0001_RawConfigParser-use-new-method-read_file-instead-of-.patch.
+  Fix deprecation warning by config.RawConfigParser.

A cosmetic deprecation fix that silence stderr when testing
standardskriver on the cmdline.

A fixed version (+deb10u1) has just been uploaded to the archive (targetting 
buster).

light+love
Mike

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

Kernel: Linux 4.19.0-6-amd64 (SMP w/4 CPU cores)
Kernel taint flags: TAINT_WARN, TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
diff -Nru standardskriver-0.0.3/debian/changelog 
standardskriver-0.0.3/debian/changelog
--- standardskriver-0.0.3/debian/changelog  2018-08-15 11:58:10.0 
+0200
+++ standardskriver-0.0.3/debian/changelog  2019-11-06 19:00:58.0 
+0100
@@ -1,3 +1,14 @@
+standardskriver (0.0.3-2+deb10u1) buster; urgency=medium
+
+  * debian/patches:
++ Add 0001_RawConfigParser-use-new-method-read_file-instead-of-.patch.
+  Fix deprecation warning by config.RawConfigParser.
++ Add 0002_standardskriver-Use-ip-command-rather-than-deprecate.patch.
+  Use external "ip" command rather than deprecated "ifconfig" command.
+  This fixes (essential) local system's IPv4 detection. (Closes: #944244).
+
+ -- Mike Gabriel   Wed, 06 Nov 2019 19:00:58 +0100
+
 standardskriver (0.0.3-2) unstable; urgency=medium
 
   * debian/control:
diff -Nru 
standardskriver-0.0.3/debian/patches/0001_RawConfigParser-use-new-method-read_file-instead-of-.patch
 
standardskriver-0.0.3/debian/patches/0001_RawConfigParser-use-new-method-read_file-instead-of-.patch
--- 
standardskriver-0.0.3/debian/patches/0001_RawConfigParser-use-new-method-read_file-instead-of-.patch
1970-01-01 01:00:00.0 +0100
+++ 
standardskriver-0.0.3/debian/patches/0001_RawConfigParser-use-new-method-read_file-instead-of-.patch
2019-11-06 18:56:40.0 +0100
@@ -0,0 +1,26 @@
+From e4aa5cc08f8d9c013d5d7f43c24cb9d4f95febcf Mon Sep 17 00:00:00 2001
+From: Mike Gabriel 
+Date: Wed, 6 Nov 2019 16:44:50 +0100
+Subject: [PATCH 2/4] RawConfigParser: use new method read_file() instead of
+ deprectated readfp().
+
+---
+ standardskriver | 2 +-
+ 1 file changed, 1 insertion(+), 1 deletion(-)
+
+diff --git a/standardskriver b/standardskriver
+index b778a9f..7c82f68 100755
+--- a/standardskriver
 b/standardskriver
+@@ -95,7 +95,7 @@ cfg.OPTCRE = re.compile(
+   # by any # space/tab
+ r'(?P.*)$' # everything up to eol
+ )
+-cfg.readfp(open(CFG_FILE, 'r'))
++cfg.read_file(open(CFG_FILE, 'r'))
+ 
+ if cfg.get('settings', 'enable') != "yes":
+ sys.exit(0)
+-- 
+2.20.1
+
diff -Nru 
standardskriver-0.0.3/debian/patches/0002_standardskriver-Use-ip-command-rather-than-deprecate.patch
 
standardskriver-0.0.3/debian/patches/0002_standardskriver-Use-ip-command-rather-than-deprecate.patch
--- 
standardskriver-0.0.3/debian/patches/0002_standardskriver-Use-ip-command-rather-than-deprecate.patch
1970-01-01 01:00:00.0 +0100
+++ 
standardskriver-0.0.3/debian/patches/0002_standardskriver-Use-ip-command-rather-than-deprecate.patch
2019-11-06 18:56:40.0 +0100
@@ -0,0 +1,34 @@
+From d1b0fa6b2ffa33263fb699a4aea6cc9f6cc8e1b9 Mon Sep 17 00:00:00 2001
+From: Mike Gabriel 
+Date: Wed, 6 Nov 2019 16:45:22 +0100
+Subject: [PATCH 3/4] standardskriver: Use ip command (rather than deprecated
+ ifconfig) to obtain local IP addresses.
+
+---
+ standardskriver | 5 +++--
+ 1 file changed, 3 insertions(+), 2 deletions(-)
+
+diff --git a/standardskriver b/standardskriver
+index 7c82f68..230ce3b 100755
+--- a/standardskriver
 b/standardskriver
+@@ -109,13 +109,14 @@ hostnames = []
+ hostnames.append(gethostname())
+ hostnames.append(getfqdn())
+ 
+-re_ipaddr = re.compile(r'inet addr:(\S+)')
++re_ipaddr = re.compile(r'inet (\S+)/')
+ ipaddrs = []
+ try:
+ ipaddrs.append(os.environ['SSH_CLIENT'].split()[0])
+ except KeyError:
+ pass
+-p = subprocess.Popen(['/sbin/ifconfig'], env={'LANG': 'C'}, 

Bug#944012: freetds: CVE-2019-13508: Heap overflow in FreeTDS if UDT type is used with protocol 5.0

[Steve Langasek]

Hello,

On Sat, Nov 02, 2019 at 08:59:25PM +0100, Salvatore Bonaccorso wrote:
> Source: freetds
> Version: 1.1.6-1
> Severity: important
> Tags: security upstream fixed-upstream
> Control: found -1 1.00.104-1

> The following vulnerability was published for freetds.

> CVE-2019-13508[0]:
> | FreeTDS through 1.1.11 has a Buffer Overflow.

Where does this "1.1.11" number come from?  I do not see any releases newer
than 1.1.6 upstream.

> 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-13508
> https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-13508
> [1] 
> https://github.com/FreeTDS/freetds/commit/0df4eb82a0e3ff844e373d7c9f9c6c813925e2ac
> [2] https://bugs.launchpad.net/bugs/1835896
> [3] https://bugzilla.redhat.com/show_bug.cgi?id=1736255
> [4] https://bugzilla.novell.com/show_bug.cgi?id=1141132
> 
> Please adjust the affected versions in the BTS as needed.
> 
> Regards,
> Salvatore
> 

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


signature.asc
Description: PGP signature

Bug#944251: e1000e: Link not detected after resume

[Dietz Proepper]

Package: linux-image-5.3.0-1-amd64
Version: 5.3.7-1
Severity: important
Tags: upstream

Hi,

there might be a regression in the e1000e ethernet driver:

After upgrade from 5.2.13 (handbuilt) to the precompiled kernel from above,
the ethernet interface does sometimes (3 out of 5 times I think) not detect
the cable connected after a resume.

Reverting to 5.2.x resolves the problem.

I already opened a bug at kernel.org, 
https://bugzilla.kernel.org/show_bug.cgi?id=205357,
there are some additional infos.

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

Kernel: Linux 5.2.13 (SMP w/8 CPU cores; PREEMPT)
Kernel taint flags: TAINT_OOT_MODULE
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8), LANGUAGE=de 
(charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages linux-image-5.3.0-1-amd64 depends on:
ii  dracut [linux-initramfs-tool]  048+80-2
ii  kmod   26-3
pn  linux-base 

Versions of packages linux-image-5.3.0-1-amd64 recommends:
ii  apparmor 2.13.3-6
ii  firmware-linux-free  3.4

Versions of packages linux-image-5.3.0-1-amd64 suggests:
pn  debian-kernel-handbook  
ii  grub-efi-amd64  2.04-3
pn  linux-doc-5.3   

Bug#944229: nvidia-driver: Lenovo thunderbolt not working

[Andreas Beckmann]

Control: tag -1 upstream moreinfo

On 06/11/2019 12.21, ganomi wrote:
> Environment:
> Thinkad X1 Extreme gen2
> ThinkPad Thunderbolt 3 Workstation Dock
> - Thunderbolt to Docking station
> - DP port from Docking to 4K LG monitor
> nvidia-driver from Experimental 435.21-2
> 
> Issue:
> When I plug in docking station the screen is recognized but it does not turn
> on.
> I am not experiencing this issue with nvidia-driver from SID.
> If I use thunderbolt cable directly to monitor, there is also no issue.

There is nothing we can do about it.
Quoting from the README in the package:

NOTES ABOUT REPORTING BUGS TO NVIDIA

The NVIDIA graphics driver is a non-free closed-source product. Therefore
the package maintainers are limited to fixing bugs in the packaging.
Bugs in the "graphics functionality" like graphical distortions,
performance regressions, hardware support, ... can only be fixed upstream
and should be reported directly to NVIDIA because this includes collecting
system information (with the nvidia-bug-report.sh script that is included
in the nvidia-driver package) on the affected system.
NVIDIA's bug reporting instructions can be found here:

https://devtalk.nvidia.com/default/topic/522835/linux/if-you-have-a-problem-please-read-this-first/
You may additionally report the problem in the distribution's bug tracker,
but please include a link the related thread(s) in the NVIDIA forum.


Andreas

Bug#680949: genisoimage should provide mkisofs as well as replacing

[Laurent Bigonville]

Package: genisoimage
Followup-For: Bug #680949

Hi,

It looks like ubuntu is doing this for years:

- debian/wodim.links: Add symlink to /usr/bin/cdrecord.
- debian/genisoimage.links: Add symlink to /usr/bin/mkisofs.
- debian/icedax.links: Add symlink to /usr/bin/cdda2wav.
- debian/control:
  - Add Provides: cdrecord to binary package wodim.
  - Add Provides: mkisofs to binary package genisoimage.
  - Add Provides: cdda2wav to binary package icedax.
  - Remove all version strings from conflicts/replaces in wodim,
genisoimage and icedax for the respective cdrtools binary package
names.

Other 3rd party applications might still use the older execuable name,
so that might be a good idea to do the same.

Kind regards,

Laurent Bigonville

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

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

Versions of packages genisoimage depends on:
ii  libbz2-1.0  1.0.8-2
ii  libc6   2.29-3
ii  libmagic1   1:5.37-6
ii  zlib1g  1:1.2.11.dfsg-1+b1

genisoimage recommends no packages.

Versions of packages genisoimage suggests:
pn  cdrkit-doc  
pn  wodim   

-- no debconf information

Bug#944250: fix tests with python3.8

[Matthias Klose]

Package: src:python-jsonrpc
Version: 1.12.1-1
Severity: important
Tags: sid bullseye patch
User: debian-pyt...@lists.debian.org
Usertags: python3.8

fix tests with python3.8, patch upstream in a pull request

http://launchpadlibrarian.net/450164905/python-jsonrpc_1.12.1-1_1.12.1-1ubuntu1.diff.gz

Bug#944243: logrotate fails with "Permission denied" on LXC guest

[Christian Göttsche]

Can you please check whether the following directories exist and if
they are symbolic links what target they have:
/var
/var/log
/tmp
/var/tmp

Also can you try to delete the line `PrivateTmp=true` from
`/lib/systemd/system/logrotate.service` and retry?


Might be related to https://github.com/systemd/systemd/issues/6212,
but https://github.com/systemd/systemd/pull/8708 got merged into
systemd v239.

Bug#943891: umoci: autopkgtest regression: bug in the autopkgtest-pkg-go

[Shengjing Zhu]

On Wed, Nov 6, 2019 at 7:36 AM Dmitry Smirnov  wrote:
[...]
> Frustratingly I was not able to locate where "autopkgtest-pkg-go"
> is defined. I've checked "apt-cache search", "apt-file search",
> Debian wiki, Golang team at Salsa and few other places.
>
> Unless someone fix "autopkgtest-pkg-go" I see no other option
> but to remove "Testsuite: autopkgtest-pkg-go" from "umoci".
>

First it was called from /usr/bin/autodep8
Then /usr/share/autodep8/support/go/generate
Finally /usr/bin/dh_golang_autopkgtest

/usr/bin/dh_golang_autopkgtest is provided by dh-golang,

PS. I don't understand this script.

-- 
Shengjing Zhu

Bug#944249: gnuplot-mode does not work with emacs26

[Olaf Skibbe]

Package: gnuplot-mode
Version: 1:0.7.0-2014-12-31-1
Severity: grave
Justification: renders package unusable

Dear Maintainer,

I hope that this is the right place for this report.

   * What led up to the situation?

Installing Debian stable/buster.

   * What exactly did you do (or not do) that was effective (or
 ineffective)?

Opening a gnuplot file in emacs.

   * What was the outcome of this action?

No gnuplot-mode available.

   * What outcome did you expect instead?

gnuplot-mode available in emacs.

Details:

On debian buster, one finds:

Package: elpa-gnuplot-mode
Version: 1:0.7.0-2014-12-31-1
[...]
Enhances: emacs, emacs24, emacs25

On the other hand:

Package: emacs
Version: 1:26.1+1-3.2+deb10u1

Hence, gnuplot-mode is not available in emacs.

I would appreciate gnuplot-mode available (backports would be fine).

Kind regards,
Olaf



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

Kernel: Linux 4.19.0-6-amd64 (SMP w/4 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 gnuplot-mode depends on:
ii  elpa-gnuplot-mode  1:0.7.0-2014-12-31-1

gnuplot-mode recommends no packages.

gnuplot-mode suggests no packages.

-- no debconf information

Bug#944248: Qemu dropped osxsave/ospke feature triggering upgrade issues

[Michal Arbet]

Package: libvirt-daemon
Version: 5.0.0-4

Hello,

I am facing the same issue in debian as it is reported in ubuntu launchpad
bug
https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1825195

Could you please fix and release security update ?
Patches from ubuntu package attached.

I've tried to apply these patches to source in
g...@salsa.debian.org:libvirt-team/libvirt.git
in debian/buster branch and they applied successfully.

Thanks,
Michal Arbet
From b51bfa70554f4bc43cbd6841b78d67b391909184 Mon Sep 17 00:00:00 2001
From: Christian Ehrhardt 
Date: Thu, 25 Apr 2019 11:51:55 +0200
Subject: [PATCH 2/2] qemuxml2argvtest: add test for remove cpu features

CPU features that always were a no-op in qemu got removed there.
We no more specify them as that would trigger errors and fail to start
qemu. This test ensures that those features really are not rendered into
qemu command line.

Without the related fix this test will trigger and fail like:
 In 'tests/qemuxml2argvdata/cpu-no-removed-features.args':
 Offset 371
 Expect [ ]
 Actual [,-osxsave,-ospke ]

Signed-off-by: Christian Ehrhardt 
Reviewed-by: Daniel Henrique Barboza 
Tested-by: Daniel Henrique Barboza 

Origin: backport, https://libvirt.org/git/?p=libvirt.git;a=commit;h=b51bfa70554f4bc43cbd6841b78d67b391909184
Bug-Ubuntu: https://bugs.launchpad.net/bugs/1825195
Last-Update: 2019-05-15

---
 .../cpu-no-removed-features.args  | 29 +++
 .../cpu-no-removed-features.xml   | 23 +++
 tests/qemuxml2argvtest.c  |  1 +
 3 files changed, 53 insertions(+)
 create mode 100644 tests/qemuxml2argvdata/cpu-no-removed-features.args
 create mode 100644 tests/qemuxml2argvdata/cpu-no-removed-features.xml

--- /dev/null
+++ b/tests/qemuxml2argvdata/cpu-no-removed-features.args
@@ -0,0 +1,25 @@
+LC_ALL=C \
+PATH=/bin \
+HOME=/home/test \
+USER=test \
+LOGNAME=test \
+QEMU_AUDIO_DRV=none \
+/usr/bin/qemu-system-x86_64 \
+-name QEMUGuest1 \
+-S \
+-machine pc,accel=kvm,usb=off,dump-guest-core=off \
+-cpu core2duo \
+-m 214 \
+-smp 6,sockets=6,cores=1,threads=1 \
+-uuid c7a5fdbd-edaf-9455-926a-d65c16db1809 \
+-display none \
+-no-user-config \
+-nodefaults \
+-chardev socket,id=charmonitor,path=/tmp/lib/domain--1-QEMUGuest1/monitor.sock,\
+server,nowait \
+-mon chardev=charmonitor,id=monitor,mode=control \
+-rtc base=utc \
+-no-shutdown \
+-no-acpi \
+-usb \
+-device virtio-balloon-pci,id=balloon0,bus=pci.0,addr=0x3
--- /dev/null
+++ b/tests/qemuxml2argvdata/cpu-no-removed-features.xml
@@ -0,0 +1,23 @@
+
+  QEMUGuest1
+  c7a5fdbd-edaf-9455-926a-d65c16db1809
+  219100
+  219100
+  6
+  
+hvm
+
+  
+  
+core2duo
+
+
+  
+  
+  destroy
+  restart
+  destroy
+  
+  /usr/bin/qemu-system-x86_64
+  
+
--- a/tests/qemuxml2argvtest.c
+++ b/tests/qemuxml2argvtest.c
@@ -1771,6 +1771,7 @@ mymain(void)
 DO_TEST("cpu-fallback", QEMU_CAPS_KVM);
 DO_TEST_FAILURE("cpu-nofallback", QEMU_CAPS_KVM);
 DO_TEST("cpu-strict1", QEMU_CAPS_KVM);
+DO_TEST("cpu-no-removed-features", QEMU_CAPS_KVM);
 DO_TEST("cpu-numa1", NONE);
 DO_TEST("cpu-numa2", NONE);
 DO_TEST("cpu-numa-no-memory-element", NONE);
From 2900575db892700fab8a4b8541474d9bd3444a4a Mon Sep 17 00:00:00 2001
From: Christian Ehrhardt 
Date: Thu, 25 Apr 2019 11:04:29 +0200
Subject: [PATCH 1/2] qemu: do not define known no-op features

Qemu dropped cpu features for osxsave and ospke [1][2].
The reason for the instant removal is that those features were never
configurable as discussed in [3].

Fortunately the use cases adding those flags in the past are rare, but
they exist. One that I identified are e.g. older virt-install when used
with --cpu=host-model and there always could be the case of a user
adding it to the guest xml.

This triggers an issue like:
  qemu-system-x86_64: can't apply global Broadwell-noTSX-x86_64-
  cpu.osxsave=on: Property '.osxsave' not found

Ensure that this does no more break spawning newer qemu versions by
not rendering those features into the qemu command line.

Fixes: https://bugs.launchpad.net/fedora/+source/qemu/+bug/1825195
Resolves: https://bugzilla.redhat.com/1644848

[1]: https://git.qemu.org/?p=qemu.git;a=commit;h=f1a2352
[2]: https://git.qemu.org/?p=qemu.git;a=commit;h=9ccb978
[3]: https://www.mail-archive.com/qemu-devel@nongnu.org/msg561877.html

Signed-off-by: Christian Ehrhardt 
Reviewed-by: Daniel Henrique Barboza 
Tested-by: Daniel Henrique Barboza 

Origin: backport, https://libvirt.org/git/?p=libvirt.git;a=commit;h=2900575db892700fab8a4b8541474d9bd3444a4a
Bug-Ubuntu: https://bugs.launchpad.net/bugs/1825195
Last-Update: 2019-05-15

---
 src/qemu/qemu_command.c   | 23 +++
 .../qemuxml2argvdata/cpu-host-model-cmt.args  |  2 +-
 tests/qemuxml2argvdata/cpu-tsc-frequency.args |  4 ++--
 3 files changed, 26 insertions(+), 3 deletions(-)

--- a/src/qemu/qemu_command.c
+++ b/src/qemu/qemu_command.c
@@ -6844,6 +6844,27 @@ 

Bug#944243: logrotate fails with "Permission denied" on LXC guest

[Lukáš Jelínek]

journalctl -u logrotate:

Nov 06 17:12:22 syslog systemd[1]: Starting Rotate log files...
Nov 06 17:12:22 syslog systemd[381]: logrotate.service: Failed to set up mount 
namespacing: Permission denied
Nov 06 17:12:22 syslog systemd[381]: logrotate.service: Failed at step 
NAMESPACE spawning /usr/sbin/logrotate: Permission denied
Nov 06 17:12:22 syslog systemd[1]: logrotate.service: Main process exited, 
code=exited, status=226/NAMESPACE
Nov 06 17:12:22 syslog systemd[1]: logrotate.service: Failed with result 
'exit-code'.
Nov 06 17:12:22 syslog systemd[1]: Failed to start Rotate log files.


systemctl status logrotate

● logrotate.service - Rotate log files
   Loaded: loaded (/lib/systemd/system/logrotate.service; static; vendor 
preset: enabled)
   Active: failed (Result: exit-code) since Wed 2019-11-06 17:12:22 CET; 11min 
ago
 Docs: man:logrotate(8)
   man:logrotate.conf(5)
  Process: 381 ExecStart=/usr/sbin/logrotate /etc/logrotate.conf (code=exited, 
status=226/NAMESPACE)
 Main PID: 381 (code=exited, status=226/NAMESPACE)

Nov 06 17:12:22 syslog systemd[1]: Starting Rotate log files...
Nov 06 17:12:22 syslog systemd[381]: logrotate.service: Failed to set up mount 
namespacing: Permission denied
Nov 06 17:12:22 syslog systemd[381]: logrotate.service: Failed at step 
NAMESPACE spawning /usr/sbin/logrotate: Permission denied
Nov 06 17:12:22 syslog systemd[1]: logrotate.service: Main process exited, 
code=exited, status=226/NAMESPACE
Nov 06 17:12:22 syslog systemd[1]: logrotate.service: Failed with result 
'exit-code'.
Nov 06 17:12:22 syslog systemd[1]: Failed to start Rotate log files.


> Can you give some more information where you did encounter the
> "Permission denied" message.
> Please provide some log entries (from /var/log/syslog or `journalctl
> -u logrotate` or `systemctl status logrotate`).

Bug#941147: Please stop removing affects of #941147

[Helmut Grohne]

affects 941147 =
user debian-cr...@lists.debian.org
usertags 941147 - cross-satisfiability
thanks

Hi Pino,

I need to apologize. Twice.

owner@bugs.d.o: Please withdraw any concern I had about Pino. It was in
error.

On Wed, Nov 06, 2019 at 07:53:34AM +0100, Pino Toscano wrote:
> I am part of the team working on these packages, and thus the changes
> I do are generally because of a precise reason, not because I
> "vandalize" bugs.

Once for jumping to the conclusion that your change must have had bad
intentions. I looked at this bug longer than usual (even on the first
change of affects), because I could not imagine bad intentions
initially. After the second change with no side communication, I failed
to imagine a constructive intention and prematurely jumped to a bad
conclusion. I'm sorry for having that attributed to you.

> All the above packages build-depend on plasma-workspace-dev, which used
> to depend on plasma-workspace, which lead to an indirect dependency on
> breeze-cursor-theme.
> However, since the upload plasma-workspace 5.14.5.1-3, this is no more
> the case, and we can check the status of the aforementioned packages:
> http://crossqa.debian.net/src/kde-cli-tools -- OK
> http://crossqa.debian.net/src/powerdevil -- OK
> http://crossqa.debian.net/src/systemsettings -- OK
> http://crossqa.debian.net/src/apper -- OK
> http://crossqa.debian.net/src/kget -- OK
> http://crossqa.debian.net/src/kdeplasma-addons
>   can be built now, fails because of #887308
> http://crossqa.debian.net/src/khotkeys -- OK
> http://crossqa.debian.net/src/plasma-desktop
>   still blocked by other issues

And a second time for not checking the obvious (in retrospect). I did
check the bug and breeze-cursor-theme and your mails, but failed to
consider dropping the dependency as a reason for changing affects. Thus
I wrongly concluded that the situation must be unchanged and considered
the initial rationale for my setting of affects undisputed.

> It is really sad to see that, instead of checking yourself whether the
> situation of the bug was changed, you assumed that the metadata you set
> was perfect, and and set it back with no additional doubt on your side.
> Even more, calling other Debian developers "vandals" because of this,
> with "he touched my bug like I do not want" as the _sole_ reason.

You made it abundantly clear that checking the packages should have been
obvious, yes. I'll keep that in mind in order not repeat that mistake.
Let me propose two measures to improve the communication on your side as
well:

I think the bts command is kinda an anti-feature of the bts, because it
makes it so easy to change bugs without giving a rationale. Yet, it
allows adding comments. A few key strokes more (e.g. bts affects 941147
= "# dependency dropped") would have helped here. I therefore ask you to
use the comment feature more actively.

Another aspect is that when you see me reverting your change, it should
have been obvious to you that I failed to understand your reasons. This
would have been a good time to explain it in more words than zero.  I do
understand that being more verbose does cost time - a scarce resource,
but I think it is required for constructive interaction.

Thank you for your work on the qt/kde stack and even caring for ftcbfs
bugs! Unfortunately, it looks like I won't be at a DebConf any time soon
to buy you a beer.

Helmut

Bug#941078: transition: postgresql-12

[Sebastiaan Couwenberg]

There seems to be an issue with debci, both postgis & pgsql-ogr-fdw are
marked as a regression in the excuses, but when looking at debci itself
for both testing and unstable the tests are passing.

The previous failure was when postgres-12 was the new default, but the
package hadn't been rebuilt with it yet.

Can britney or its debci integration be fixed, or do we need to drop the
autopkgtests to prevent issues like this in the future?

Kind Regards,

Bas

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

Bug#944243: logrotate fails with "Permission denied" on LXC guest

[Christian Göttsche]

Can you give some more information where you did encounter the
"Permission denied" message.
Please provide some log entries (from /var/log/syslog or `journalctl
-u logrotate` or `systemctl status logrotate`).

Bug#944246: mirror listing update for mirror.nbtelecom.com.br

[Pedro Alves]

Package: mirrors
Severity: minor
User: mirr...@packages.debian.org
Usertags: mirror-list

Submission-Type: update
Site: mirror.nbtelecom.com.br
Type: leaf
Archive-architecture: ALL amd64 arm64 armel armhf hurd-i386 i386 kfreebsd-amd64 
kfreebsd-i386 mips mips64el mipsel powerpc ppc64el s390x
Archive-http: /debian/
Archive-rsync: debian/
Maintainer: Pedro Alves 
Country: BR Brazil
Location: Rio de Janeiro
Sponsor: NB Telecom https://www.nbtelecom.com.br




Trace Url: http://mirror.nbtelecom.com.br/debian/project/trace/
Trace Url: 
http://mirror.nbtelecom.com.br/debian/project/trace/ftp-master.debian.org
Trace Url: 
http://mirror.nbtelecom.com.br/debian/project/trace/mirror.nbtelecom.com.br

Bug#944247: xen domU crashes under high i/o load if you use qcow2 images

[mario]

Source: xen
Severity: important

Dear Maintainer,

we have updated our server from debian oldstable (which unfortunately wasn't 
running stable after the last update, bug reported) to debian buster.

unfortunately xen doesn't work reliably there either:

the virtual server crashes every 1-2 week with i/o problems and sometimes also 
takes other domU instances with it.
we use qcow2 images.

the harddisk of the domU is simply no longer accessible for the linux kernel, 
no logfiles are available. in the xl console the following last lines can be 
read, login not possible:

[ 1450.976415] INFO: task nginx:376 blocked for more than 120 seconds.
[ 1450.976423] Not tainted 4.9.0-9-amd64 #1 Debian 4.9.168-1+deb9u5
[ 1450.976428] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this 
message.
[ 1450.976469] INFO: task nginx:377 blocked for more than 120 seconds.
[ 1450.976474] Not tainted 4.9.0-9-amd64 #1 Debian 4.9.168-1+deb9u5
[ 1450.976479] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this 
message.
[ 1450.976624] INFO: task nginx:378 blocked for more than 120 seconds.

the process varies:
[1523692.508073] INFO: task jbd2/xvda2-8:159 blocked for more than 120 seconds
[1523692.508084] Not tainted [...]

all hard disk accesses fail as if the i/o system is completely dead.
only "xl destroy " and recreate will help

you can easily reproduce this with the tool stress "stress -c 8 -i 8 -d 8".
it takes a maximum of 10 minutes until the vm crashes.

in our experience, as a workaround you can convert all images to raw. after our 
tests, the error will no longer occur. 
but since we need the snapshot functions of qcow2 images, this is not a 
permanent solution.

does anyone else have problems with qcow2 images and xen under buster?
maybe this also concerns qemu?

xen vm.cfg:

we using pygrub, 4 vcpus, 1024 memory

#
# Disk device(s).
#
root = '/dev/xvda2 ro'
disk = [
  'tap:qcow2:/[...]/disk.qcow2,xvda2,w',
  file:/[...]/swap.img,xvda1,w',
  ]

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

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

Bug#944245: Please update to new upstream release in unstable

[Laurent Bigonville]

Source: libxml2
Version: 2.9.4+dfsg1-7
Severity: normal

Hi,

Could it be possible to have a new upstream release in unstable?

I've the tests of libgovirt (last git head) failing with the current
version in unstable. The tests are succeeding with the version in
experimental (2.9.9)

Btw 2.9.10 has been released

Kind regards,

Laurent Bigonville

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

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

-- no debconf information

Bug#944244: [standardskriver] Fails to detect local system's IP addresses

[Mike Gabriel]

Package: standardskriver
Severity: serious
Version: 0.0.3-2

I just discovered, that standardskriver in buster/testing/unstable  
fails to detect the local system's IP addresses due to stdout changes  
in ifconfig. Furthermore, utilizing ifconfig form another application  
is not a good idea these days anymore, it should be replace by  
utilizing the "ip" command.


I will prepare updated packages for this within the next days.

Mike
--

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

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



pgphhRuImODD0.pgp
Description: Digitale PGP-Signatur

Bug#944243: logrotate fails with "Permission denied" on LXC guest

[Lukas Jelinek]

Package: logrotate
Version: 3.14.0-4
Severity: grave
Justification: renders package unusable



-- Package-specific info:
Contents of /etc/logrotate.d
total 52
-rw-r--r-- 1 root root 120 Apr 19  2019 alternatives
-rw-r--r-- 1 root root 173 May 28 16:40 apt
-rw-r--r-- 1 root root  79 Feb 13  2019 aptitude
-rw-r--r-- 1 root root 130 Aug 29  2018 btmp
-rw-r--r-- 1 root root 112 Apr 19  2019 dpkg
-rw-r--r-- 1 root root 146 Sep 27 18:07 exim4-base
-rw-r--r-- 1 root root 126 Sep 27 18:07 exim4-paniclog
-rw-r--r-- 1 root root 329 Aug 13 20:10 nginx
-rw-r--r-- 1 root root  92 Oct 16 12:04 remote-rsyslog
-rw-r--r-- 1 root root 501 Feb 26  2019 rsyslog
-rw-r--r-- 1 root root 235 Jun  8 16:59 unattended-upgrades
-rw-r--r-- 1 root root 145 Feb 19  2018 wtmp
-rw-r--r-- 1 root root 153 Aug 26 10:26 zabbix-agent


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

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

Versions of packages logrotate depends on:
ii  cron [cron-daemon]  3.0pl1-134
ii  libacl1 2.2.53-4
ii  libc6   2.28-10
ii  libpopt01.16-12
ii  libselinux1 2.8-1+b1
ii  systemd-sysv241-7~deb10u1

Versions of packages logrotate recommends:
ii  bsd-mailx [mailx]  8.1.2-0.20180807cvs-1
ii  mailutils [mailx]  1:3.5-3

logrotate suggests no packages.

-- no debconf information

Bug#944242: fix build & test issues with Python 3.8

[Matthias Klose]

Package: src:python-biopython
Version: 1.73+dfsg-1
Severity: important
Tags: sid bullseye patch
User: debian-pyt...@lists.debian.org
Usertags: python3.8

please find patches to build and run the tests with Python 3.8. All patches 
taken from upstream except for

https://github.com/biopython/biopython/issues/2325


diff -Nru python-biopython-1.73+dfsg/debian/changelog python-biopython-1.73+dfsg/debian/changelog
--- python-biopython-1.73+dfsg/debian/changelog	2019-01-11 22:23:52.0 +
+++ python-biopython-1.73+dfsg/debian/changelog	2019-11-06 13:31:00.0 +
@@ -1,3 +1,23 @@
+python-biopython (1.73+dfsg-1ubuntu4) focal; urgency=medium
+
+  * Pull some Python 3.8 fixes from upstream.
+
+ -- Matthias Klose   Wed, 06 Nov 2019 14:31:00 +0100
+
+python-biopython (1.73+dfsg-1ubuntu2) focal; urgency=medium
+
+  * No-change rebuild to build with python3.8.
+
+ -- Matthias Klose   Fri, 18 Oct 2019 18:42:37 +
+
+python-biopython (1.73+dfsg-1ubuntu1) disco; urgency=medium
+
+  * debian/patches/test_phenotype_fit-ppc64el.patch:
+- reduce precision on one test, per upstream recommendation at:
+  https://github.com/biopython/biopython/issues/1945
+
+ -- Adam Conrad   Mon, 04 Mar 2019 12:21:32 -0700
+
 python-biopython (1.73+dfsg-1) unstable; urgency=medium
 
   * New upstream version
diff -Nru python-biopython-1.73+dfsg/debian/control python-biopython-1.73+dfsg/debian/control
--- python-biopython-1.73+dfsg/debian/control	2019-01-11 22:23:52.0 +
+++ python-biopython-1.73+dfsg/debian/control	2019-03-04 19:21:32.0 +
@@ -1,5 +1,6 @@
 Source: python-biopython
-Maintainer: Debian Med Packaging Team 
+Maintainer: Ubuntu Developers 
+XSBC-Original-Maintainer: Debian Med Packaging Team 
 Uploaders: Charles Plessy ,
Andreas Tille 
 Section: python
diff -Nru python-biopython-1.73+dfsg/debian/patches/2146.diff python-biopython-1.73+dfsg/debian/patches/2146.diff
--- python-biopython-1.73+dfsg/debian/patches/2146.diff	1970-01-01 00:00:00.0 +
+++ python-biopython-1.73+dfsg/debian/patches/2146.diff	2019-11-06 13:31:00.0 +
@@ -0,0 +1,34 @@
+--- a/Bio/SeqFeature.py
 b/Bio/SeqFeature.py
+@@ -1533,6 +1533,11 @@ class ExactPosition(int, AbstractPositio
+ """Return a representation of the ExactPosition object (with python counting)."""
+ return str(int(self))
+ 
++# Must define this on Python 3.8 onwards because we redefine __repr__
++def __str__(self):
++"""Return a representation of the ExactPosition object (with python counting)."""
++return str(int(self))
++
+ def __repr__(self):
+ """Represent the ExactPosition object as a string for debugging."""
+ return "%s(%i)" % (self.__class__.__name__, int(self))
+@@ -2067,8 +2072,7 @@ class OneOfPosition(int, AbstractPositio
+ for position in self.position_choices:
+ out += "%s," % position
+ # replace the last comma with the closing parenthesis
+-out = out[:-1] + ")"
+-return out
++return out[:-1] + ")"
+ 
+ def _shift(self, offset):
+ """Return a copy of the position object with its location shifted (PRIVATE)."""
+@@ -2094,8 +2098,7 @@ class PositionGap(object):
+ 
+ def __str__(self):
+ """Return a representation of the PositionGap object (with python counting)."""
+-out = "gap(%s)" % self.gap_size
+-return out
++return "gap(%s)" % self.gap_size
+ 
+ 
+ if __name__ == "__main__":
diff -Nru python-biopython-1.73+dfsg/debian/patches/dict-iterate.diff python-biopython-1.73+dfsg/debian/patches/dict-iterate.diff
--- python-biopython-1.73+dfsg/debian/patches/dict-iterate.diff	1970-01-01 00:00:00.0 +
+++ python-biopython-1.73+dfsg/debian/patches/dict-iterate.diff	2019-11-06 13:31:00.0 +
@@ -0,0 +1,11 @@
+--- a/Bio/SubsMat/__init__.py
 b/Bio/SubsMat/__init__.py
+@@ -207,7 +207,7 @@ class SeqMat(dict):
+ 
+ def _correct_matrix(self):
+ """Sort key tuples (PRIVATE)."""
+-for key in self:
++for key in dict(self):
+ if key[0] > key[1]:
+ self[(key[1], key[0])] = self[key]
+ del self[key]
diff -Nru python-biopython-1.73+dfsg/debian/patches/ed75bd630e26edea2891c6e92e78daad4f36c7cb.diff python-biopython-1.73+dfsg/debian/patches/ed75bd630e26edea2891c6e92e78daad4f36c7cb.diff
--- python-biopython-1.73+dfsg/debian/patches/ed75bd630e26edea2891c6e92e78daad4f36c7cb.diff	1970-01-01 00:00:00.0 +
+++ python-biopython-1.73+dfsg/debian/patches/ed75bd630e26edea2891c6e92e78daad4f36c7cb.diff	2019-11-06 13:31:00.0 +
@@ -0,0 +1,27 @@
+diff --git a/Bio/Seq.py b/Bio/Seq.py
+index 5308a59fd..7b12662d7 100644
+--- a/Bio/Seq.py
 b/Bio/Seq.py
+@@ -27,6 +27,13 @@ import sys
+ import warnings
+ import collections
+ 
++try:
++# Python 3
++from collections.abc import Iterable as _Iterable
++except ImportError:
++# Python 2.7
++from 

Bug#942688: NMU for elixir-lang

[Evgeny Golyshev]

Hello Thomas

I really appreciate your actions intended to keep the package in
testing. However, the removed tests show that there are some problems
on arm64 which we can't simply ignore. If we do that, there will be
other bug reports, making us do something about it.
I have to confess that I remove some tests from the package as well,
but in 2 specific cases:
* rebar3: we haven't still got rebar3 in Debian, so there's nothing to test.
* backports: sometimes the tests from backported Elixir reveals some
bugs[1] in Erlang from stable, so there are two solutions in the cases
like that: 1) remove the corresponding tests or 2) backport Erlang
along with Elixir. Removing tests is cheaper.

Coming back to Elixir and the problems related to arm64. I believe we
have to find a better solution. It’s not a big deal if the package is
removed from testing right now. It will turn out in testing again
1) when we figure out the root of the problem and fix it; or
2) when I (or someone else) update the package to the newest version
which (probably) will be sustainable to the problem.

[1] 
https://sources.debian.org/src/elixir-lang/1.9.1.dfsg-1~bpo10+1/debian/patches/remove_runs_eval_and_version_commands_test.patch/

--
Evgeny

Bug#944241: python3-yapf: shouldnt install 2 top-level modules (yapf, and yapftests)

[Sandro Tosi]

Package: python3-yapf
Severity: important

Hello,
python3-yapf installs 2 top-level modules: yapf, and yapftests

yapftests shoult not be there, but (following conventions) be moved under yapf
as a `tests/` directory. This change should be better done upstream, but in the
meantime, you can have it as a debian-specific patch.

Regards,
Sandro

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

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

Versions of packages python3-yapf depends on:
ii  python33.7.3-1
ii  python3-lib2to33.7.3-1
ii  python3-pkg-resources  41.0.1-1

python3-yapf recommends no packages.

python3-yapf suggests no packages.

Bug#942572: RM: icinga -- ROM; Obsolete, EOL upstream, superceded by icinga2

[Sebastiaan Couwenberg]

On Thu, 31 Oct 2019 09:33:31 +0100 Bas Couwenberg 
wrote:
> On 2019-10-31 09:21, Paul Gevers wrote:
> > On Fri, 18 Oct 2019 11:46:25 +0200 Bas Couwenberg 
> > wrote:
> >> Please remove icinga from the archive, it's EOL upstream and 
> >> superceded by icinga2.
> > 
> > I may be wrong, but it seems that icinga can't be removed from testing
> > because ganglia-nagios-bridge and syslog-nagios-bridge depends on
> > icinga2 | icinga | nagios3 and neither icinga2 or nagios3 is available
> > on armel, mips64el, mipsel and s390x and while icinga is.
> > 
> > What should be the way forward here?
> 
> Remove the *-nagios-bridge packages from those architectures too seems 
> the most obvious.

RM bugs:

 * ganglia-nagios-bridge #944239
 * syslog-nagios-bridge  #944240

> Looking a little more closely at the packages you'll see that they are 
> pretty much unmaintained, it's maintainer not being a member of Debian 
> any more, and having extremely low popcon score.
> 
> Removing the packages from the archive as well seems like a reasonable 
> option too.

Complete removal is still an option too, but I'll leave that to someone
else to decide.

Kind Regards,

Bas

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

Bug#944239: RM: ganglia-nagios-bridge [armel mips64el mipsel s390x] -- RoQA; Dependencies not available

[Bas Couwenberg]

Package: ftp.debian.org
Severity: normal

Please remove ganglia-nagios-bridge from armel, mips64el, mipsel & s390x, its 
dependenies are not available on these architectures.

Kind Regards,

Bas

Bug#944240: RM: syslog-nagios-bridge [armel mips64el mipsel s390x] -- RoQA; Dependencies not available

[Bas Couwenberg]

Package: ftp.debian.org
Severity: normal

Please remove syslog-nagios-bridge from armel, mips64el, mipsel & s390x, its 
dependenies are not available on these architectures.

Kind Regards,

Bas

Bug#943962: mariadb-server-10.3: mysqld crashes and hangs, no longer processing requests)

[Richard van den Berg]

I found the debug packages in 
http://debug.mirrors.debian.org/debian-debug/pool/main/m/mariadb-10.3/

It seems I broke my apt preferences so it could not find them automatically.

Running mysqld now with a gdb on standby...