Bug#934089: marked as done (firehol fails to use iptables-restore)

[Debian Bug Tracking System]

Your message dated Fri, 16 Aug 2019 08:26:22 +0400
with message-id <4eb5cb43-baba-31c2-4979-742f6cf26...@rezozer.net>
and subject line firehol fails to use iptables-restore
has caused the Debian Bug report #934089,
regarding firehol fails to use iptables-restore
to be marked as done.

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

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


-- 
934089: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=934089
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: firehol
Version: 3.1.6+ds-8
Severity: grave
Justification: renders package unusable

Dear Maintainer,

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

   * What led up to the situation?

   Upgrade to Debian 10
   
   * What exactly did you do (or not do) that was effective (or
 ineffective)?

   sudo firehol try
   
   * What was the outcome of this action?

sudo firehol try
FireHOL: Saving active firewall to a temporary file...  OK
FireHOL: Processing file '/etc/firehol/firehol.conf'...  OK  (281 iptables 
rules)

Your firewall is ready to be fast-activated...
If you don't continue, no changes will have been made to your firewall.
Activate the firewall? (just press enter to confirm or Control-C to stop) :

FireHOL: Fast activating new firewall...


ERROR   : # 1.
WHAT: A runtime command failed to execute (returned error CANNOT APPLY IN 
FAST MODE).
SOURCE  : FIN
COMMAND : /usr/sbin/iptables-legacy-restore 
\
ii  firehol-tools  3.1.6+ds-8
pn  ulogd2 

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

-- no debconf information
--- End Message ---
--- Begin Message ---
Dear All,

I am closing because I guess it is simply a upgrade issue.

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



signature.asc
Description: OpenPGP digital signature
--- End Message ---

Bug#931897: marked as done (librust-debcargo-dev depends on old version of librust-cargo-dev)

[Debian Bug Tracking System]

Your message dated Fri, 16 Aug 2019 02:51:49 +
with message-id 
and subject line Bug#931897: fixed in rust-debcargo 2.4.0-1
has caused the Debian Bug report #931897,
regarding librust-debcargo-dev depends on old version of librust-cargo-dev
to be marked as done.

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

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


-- 
931897: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=931897
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: librust-debcargo-dev
Version: 2.2.10-1
Severity: serious
Tags: sid
User: ubuntu-de...@lists.ubuntu.com
Usertags: origin-ubuntu eoan

Hi Ximin,

The librust-debcargo-dev package is uninstallable in unstable because it
depends on older ABIs of librust-cargo-dev and librust-git2-dev:

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

The following packages have unmet dependencies:
 librust-debcargo-dev : Depends: librust-cargo-0.32+default-dev but it is not 
installable
Depends: librust-git2-0.7+default-dev but it is not 
installable
E: Unable to correct problems, you have held broken packages.
$

Please update this package.

-- 
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
--- End Message ---
--- Begin Message ---
Source: rust-debcargo
Source-Version: 2.4.0-1

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

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

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

Debian distribution maintenance software
pp.
Ximin Luo  (supplier of updated rust-debcargo package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Thu, 15 Aug 2019 19:07:57 -0700
Source: rust-debcargo
Architecture: source
Version: 2.4.0-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Rust Maintainers 

Changed-By: Ximin Luo 
Closes: 931897
Changes:
 rust-debcargo (2.4.0-1) unstable; urgency=medium
 .
   * Package debcargo 2.4.0 from crates.io using debcargo 2.4.0
 (Closes: #931897)
Checksums-Sha1:
 dedd4fdf77002966a2195b58be000414021dfa26 2224 rust-debcargo_2.4.0-1.dsc
 c09f4caf949ae6dca4f9c89d22d406229db1e772 58974 rust-debcargo_2.4.0.orig.tar.gz
 71f65660b5193a8a65d9791e0c1de77b61896d48 3068 
rust-debcargo_2.4.0-1.debian.tar.xz
 72a5c8df116f2516b36b124a6ecf9b07be65c609 6268 
rust-debcargo_2.4.0-1_source.buildinfo
Checksums-Sha256:
 d41f833a7718cfd78c0179df00c2f4b5db730340adb4a8fac9bdabcae96b978a 2224 
rust-debcargo_2.4.0-1.dsc
 206509b03297715b19247953225a4a572c96f63d750f495108120384d6b7b2bf 58974 
rust-debcargo_2.4.0.orig.tar.gz
 02921ce6cdf6df1625647d1356858ab487e43f539e9eabd6016c4f9c4a70a074 3068 
rust-debcargo_2.4.0-1.debian.tar.xz
 ce7a1ae860ccaf3775634dbc300a7af3c077374447d2a869e879f3b9c373371c 6268 
rust-debcargo_2.4.0-1_source.buildinfo
Files:
 54df270fc37a85fdd2139d31c173734a 2224 rust optional rust-debcargo_2.4.0-1.dsc
 ec71a7ba59eaac272f93b044d3044ca0 58974 rust optional 
rust-debcargo_2.4.0.orig.tar.gz
 d4d958508f4e5421ff8ff2051f72f18c 3068 rust optional 
rust-debcargo_2.4.0-1.debian.tar.xz
 892b48377c0c5c685cdd97b44322e212 6268 rust optional 
rust-debcargo_2.4.0-1_source.buildinfo

-BEGIN PGP SIGNATURE-

iHUEARYKAB0WIQReYinNQ9GpZ9TYcRrrH8jaRfspMAUCXVYQAAAKCRDrH8jaRfsp
MOk3AQCrfZPkAum0LO5jAFHPTShVXbL68X/Y1rjsdWAh44uPIgD+LbhFZyLh1QrF
UhKZN8ruhFquof9BK813Dlq5u5p5tgM=
=LZPb
-END PGP SIGNATURE End Message ---

Bug#931897: marked as done (librust-debcargo-dev depends on old version of librust-cargo-dev)

[Debian Bug Tracking System]

Your message dated Fri, 16 Aug 2019 02:35:00 +
with message-id <06b83460-7d92-04ce-044a-624ae6cfc...@debian.org>
and subject line 
has caused the Debian Bug report #931897,
regarding librust-debcargo-dev depends on old version of librust-cargo-dev
to be marked as done.

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

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


-- 
931897: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=931897
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: librust-debcargo-dev
Version: 2.2.10-1
Severity: serious
Tags: sid
User: ubuntu-de...@lists.ubuntu.com
Usertags: origin-ubuntu eoan

Hi Ximin,

The librust-debcargo-dev package is uninstallable in unstable because it
depends on older ABIs of librust-cargo-dev and librust-git2-dev:

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

The following packages have unmet dependencies:
 librust-debcargo-dev : Depends: librust-cargo-0.32+default-dev but it is not 
installable
Depends: librust-git2-0.7+default-dev but it is not 
installable
E: Unable to correct problems, you have held broken packages.
$

Please update this package.

-- 
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
--- End Message ---
--- Begin Message ---
Version: 2.4.0-1

-- 
GPG: ed25519/56034877E1F87C35
GPG: rsa4096/1318EFAC5FBBDBCE
https://github.com/infinity0/pubkeys.git--- End Message ---

Bug#934307: marked as done (rust-regex_1.2.1-1_s390x.changes REJECTED)

[Debian Bug Tracking System]

Your message dated Fri, 16 Aug 2019 02:32:00 +
with message-id <12c3809d-5aa2-7e46-9bbb-e4bc3f973...@debian.org>
and subject line fixed
has caused the Debian Bug report #934307,
regarding rust-regex_1.2.1-1_s390x.changes REJECTED
to be marked as done.

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

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


-- 
934307: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=934307
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: rust-regex
Version: 1.2.1-1
Severity: serious

On 2019-08-09 12:10, Debian FTP Masters wrote:
> 
> 
> librust-regex-dev_1.2.1-1_s390x.deb: has 1 file(s) with a timestamp too far 
> in the past:
>   usr/share/cargo/registry/regex-1.2.1/Cargo.lock (Thu Jan  1 00:00:00 1970)
> 
> 
> 
> ===
> 
> Please feel free to respond to this email if you don't understand why
> your files were rejected, or if you upload new files which address our
> concerns.
> 
> 
> 
--- End Message ---
--- Begin Message ---
Version: 1.2.1-3

-- 
GPG: ed25519/56034877E1F87C35
GPG: rsa4096/1318EFAC5FBBDBCE
https://github.com/infinity0/pubkeys.git--- End Message ---

Bug#933693: marked as done (rust-cargo: FTBFS due to missing/uninstallable build dependencies)

[Debian Bug Tracking System]

Your message dated Fri, 16 Aug 2019 02:34:00 +
with message-id 
and subject line 
has caused the Debian Bug report #933693,
regarding rust-cargo: FTBFS due to missing/uninstallable build dependencies
to be marked as done.

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

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


-- 
933693: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=933693
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: rust-cargo
Version: 0.35.0-1
Severity: serious
Justification: FTBFS

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Hi,

rust-cargo fails to rebuild from source (in a clean sbuild environment).

I ran into this while rebuilding all reverse dependencies of rust-openssl-sys
prior to uploading an updated version.

Best,

  nicoo

- ---

$ sbuild -d sid rust-cargo
sbuild (Debian sbuild) 0.78.1 (09 February 2019) on localhost

+==+
| rust-cargo (amd64)   Thu, 01 Aug 2019 23:34:16 + |
+==+

Package: rust-cargo
Distribution: sid
Machine Architecture: amd64
Host Architecture: amd64
Build Architecture: amd64
Build Type: full

[...]

+--+
| Update chroot|
+--+

[...]

+--+
| Fetch source files   |
+--+


Check APT
- -

Checking available source versions...

Download source files with APT
- --

Reading package lists...
NOTICE: 'rust-cargo' packaging is maintained in the 'Git' version control 
system at:
https://salsa.debian.org/rust-team/debcargo-conf.git [src/cargo]
Please use:
git clone https://salsa.debian.org/rust-team/debcargo-conf.git [src/cargo]
to retrieve the latest (possibly unreleased) updates to the package.
Need to get 943 kB of source archives.
Get:1 http://localhost:3142/debian sid/main rust-cargo 0.35.0-1 (dsc) [5100 B]
Get:2 http://localhost:3142/debian sid/main rust-cargo 0.35.0-1 (tar) [934 kB]
Get:3 http://localhost:3142/debian sid/main rust-cargo 0.35.0-1 (diff) [4304 B]
Fetched 943 kB in 0s (11.2 MB/s)
Download complete and in download only mode
I: NOTICE: Log filtering will replace 
'build/rust-cargo-oCDNo8/rust-cargo-0.35.0' with '<>'
I: NOTICE: Log filtering will replace 'build/rust-cargo-oCDNo8' with 
'<>'

+--+
| Install package build dependencies   |
+--+


Setup apt archive
- -

Merged Build-Depends: debhelper (>= 11), dh-cargo (>= 15), cargo, rustc, 
libstd-rust-dev, librust-atty-0.2+default-dev, librust-byteorder-1+default-dev 
(>= 1.2-~~), librust-bytesize-1+default-dev, librust-clap-2+default-dev (>= 
2.31.2-~~), librust-core-foundation-0.6+default-dev, 
librust-core-foundation-0.6+mac-os-10-7-support-dev, 
librust-crates-io-0.23+default-dev, librust-crossbeam-utils-0.6+default-dev, 
librust-crypto-hash-0.3+default-dev (>= 0.3.1-~~), librust-curl-0.4+default-dev 
(>= 0.4.19-~~), librust-curl-0.4+http2-dev (>= 0.4.19-~~), 
librust-curl-sys-0.4+default-dev (>= 0.4.15-~~), 
librust-env-logger-0.6+default-dev, librust-failure-0.1+default-dev (>= 
0.1.5-~~), librust-filetime-0.2+default-dev, librust-flate2-1+default-dev (>= 
1.0.3-~~), librust-flate2-1+zlib-dev (>= 1.0.3-~~), 
librust-fs2-0.4+default-dev, librust-fwdansi-1+default-dev, 
librust-git2-0.8+default-dev, librust-git2-curl-0.9+default-dev, 
librust-glob-0.2+default-dev (>= 0.2.11-~~), librust-hex-0.3+default-dev, 
librust-home-0.3+default-dev, librust-ignore-0.4+default-dev, 
librust-im-rc-12+default-dev (>= 12.1.0-~~), librust-jobserver-0.1+default-dev 
(>= 0.1.11-~~), librust-lazy-static-1+default-dev (>= 1.2.0-~~), 
librust-lazycell-1+default-dev (>= 1.2.0-~~), librust-libc-0.2+default-dev, 
librust-libgit2-sys-0.7+default-dev (>= 0.7.9-~~), librust-log-0.4+default-dev 
(>= 0.4.6-~~), librust-miow-0.3+default-dev (>= 0.3.1-~~), 
librust-num-cpus-1+default-dev, librust-opener-0.3+default-dev, 
librust-rustc-workspace-hack-1+default-dev, librust-rustfix-0.4+default-dev (>= 
0.4.4-~~), 

Bug#934483: virtualbox-guest-dkms: Doesn't build with latest kernel in unstable 5.2.0-2-686-pae

[Darsey Litzenberger]

On Sun, Aug 11, 2019 at 03:14:16PM +0200, Christian Marillat wrote:

Dear Maintainer,

/var/lib/dkms/virtualbox-guest/6.0.10/build/vboxvideo/vbox_ttm.c:31:10: fatal 
error: ttm/ttm_page_alloc.h: No such file or directory
#include 
 ^~
compilation terminated.

But bevare fixind the include file path (drm/ttm/ttm_page_alloc.h) doesn't
work at all the virtualbox doesn't start.


Do all of these modules even need to be built using dkms anymore?  It 
looks like some of them have been mainlined (though I haven't compared 
the code):


It looks like virtualbox-guest-dkms builds 3 modules:

   # cd /var/lib/dkms/virtualbox-guest
   # find . -name \*.ko
   ./6.0.10/5.0.0-trunk-amd64/x86_64/module/vboxguest.ko
   ./6.0.10/5.0.0-trunk-amd64/x86_64/module/vboxsf.ko
   ./6.0.10/5.0.0-trunk-amd64/x86_64/module/vboxvideo.ko

Out of those three modules, it seems like only vboxsf.ko still needs to 
be built on recent kernels:


   root@syra:/lib/modules# find . -name vboxguest.ko -o -name vboxsf.ko -o 
-name vboxvideo.ko
   ./5.0.0-trunk-amd64/kernel/drivers/staging/vboxvideo/vboxvideo.ko
   ./5.0.0-trunk-amd64/kernel/drivers/virt/vboxguest/vboxguest.ko

   ./5.0.0-trunk-amd64/updates/dkms/vboxguest.ko
   ./5.0.0-trunk-amd64/updates/dkms/vboxsf.ko
   ./5.0.0-trunk-amd64/updates/dkms/vboxvideo.ko

   ./4.19.0-5-amd64/kernel/drivers/staging/vboxvideo/vboxvideo.ko
   ./4.19.0-5-amd64/kernel/drivers/virt/vboxguest/vboxguest.ko

   ./5.2.0-2-amd64/kernel/drivers/gpu/drm/vboxvideo/vboxvideo.ko
   ./5.2.0-2-amd64/kernel/drivers/virt/vboxguest/vboxguest.ko

(split for readability)

I haven't gotten around to testing, but it looks like maybe all that 
needs to be done is to disable building some of these modules after a 
certain kernel version.

Bug#921194: marked as done (amarok: Amarok depends on libmariadbd18, which doesn't exist any longer)

[Debian Bug Tracking System]

Your message dated Fri, 16 Aug 2019 03:43:28 +0300
with message-id <2005991565916...@myt6-09be74140f25.qloud-c.yandex.net>
and subject line amarok: Amarok depends on libmariadbd18, which doesn't exist 
any longer
has caused the Debian Bug report #921194,
regarding amarok: Amarok depends on libmariadbd18, which doesn't exist any 
longer
to be marked as done.

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

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


-- 
921194: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=921194
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: amarok
Version: 2.9.0-1+b1
Severity: normal
Tags: a11y

Dear Maintainer,

libmariadbd18 does not exist any longer, but Amarok still depends on it. This 
would make Amarok uninstallable unless
one has installed it from other sources or has kept it from when it was 
available in the repos.

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

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

Versions of packages amarok depends on:
ii  amarok-common2.9.0-1
ii  amarok-utils 2.9.0-1+b1
ii  kde-runtime  4:17.08.3-2
ii  libavcodec58 10:4.1-dmo4
ii  libavformat5810:4.1-dmo4
ii  libavutil56  10:4.1-dmo4
ii  libc62.28-5
ii  libgdk-pixbuf2.0-0   2.38.0+dfsg-7
ii  libgl1   1.1.0-1
ii  libglib2.0-0 2.58.2-3
ii  libgpod4 0.8.3-13
ii  libkcmutils4 4:4.14.38-3
ii  libkdecore5  4:4.14.38-3
ii  libkdeui54:4.14.38-3
ii  libkdewebkit54:4.14.38-3
ii  libkdnssd4   4:4.14.38-3
ii  libkfile44:4.14.38-3
ii  libkio5  4:4.14.38-3
ii  libknewstuff3-4  4:4.14.38-3
ii  libktexteditor4  4:4.14.38-3
ii  liblastfm1   1.0.9-1
ii  libmariadbclient18 [libmariadbclient18]  1:10.3.12-2
ii  libmariadbd181:10.1.37-3
ii  libmtp9  1.1.16-1
ii  libofa0  0.9.3-19
ii  libphonon4   4:4.10.2-1
ii  libplasma3   4:4.14.38-3
ii  libqca2  2.1.3-2
ii  libqjson00.8.1-3+b1
ii  libqt4-dbus  4:4.8.7+dfsg-17
ii  libqt4-network   4:4.8.7+dfsg-17
ii  libqt4-opengl4:4.8.7+dfsg-17
ii  libqt4-script4:4.8.7+dfsg-17
ii  libqt4-scripttools   4:4.8.7+dfsg-17
ii  libqt4-sql   4:4.8.7+dfsg-17
ii  libqt4-svg   4:4.8.7+dfsg-17
ii  libqt4-xml   4:4.8.7+dfsg-17
ii  libqtcore4   4:4.8.7+dfsg-17
ii  libqtgui44:4.8.7+dfsg-17
ii  libqtscript4-core0.2.0-1+b1
ii  libqtscript4-gui 0.2.0-1+b1
ii  libqtscript4-network 0.2.0-1+b1
ii  libqtscript4-sql 0.2.0-1+b1
ii  libqtscript4-uitools 0.2.0-1+b1
ii  libqtscript4-xml 0.2.0-1+b1
ii  libqtwebkit4 2.3.4.dfsg-10
ii  libsolid44:4.14.38-3
ii  libstdc++6   8.2.0-15
ii  libthreadweaver4 4:4.14.38-3
ii  libx11-6 2:1.6.7-1
ii  phonon   4:4.10.2-1

Versions of packages amarok recommends:
pn  clamz
pn  kio-audiocd  

Versions of packages amarok suggests:
pn  amarok-doc 
ii  libqt4-sql-mysql   4:4.8.7+dfsg-17
pn  libqt4-sql-psql
ii  libqt4-sql-sqlite  4:4.8.7+dfsg-17
pn  moodbar

Versions of packages amarok-common depends on:
ii  perl  5.28.1-3

amarok-common recommends no packages.

Versions of packages amarok is 

Bug#927991: marked as done (amarok: FTBFS: mysql_config --libmysqld-libs unrecognized)

[Debian Bug Tracking System]

Your message dated Fri, 16 Aug 2019 03:31:18 +0300
with message-id <5375311565915...@myt5-1466095fe4e5.qloud-c.yandex.net>
and subject line Re: amarok: FTBFS: mysql_config --libmysqld-libs unrecognized
has caused the Debian Bug report #927991,
regarding amarok: FTBFS: mysql_config --libmysqld-libs unrecognized
to be marked as done.

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

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


-- 
927991: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=927991
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: amarok
Version: 2.9.0-1
Severity: serious
Tags: upstream ftbfs
Justification: fails to build from source (but built successfully in the past)

Builds of amarok against current unstable (including in particular
rebuilds for library transitions) have been failing lately with the
error

  
src/core-impl/storage/sql/mysqlestorage/CMakeFiles/amarok_storage-mysqlestorage.dir/build.make:133:
 *** target pattern contains no '%'.  Stop.

The relevant line reads

  lib/amarok_storage-mysqlestorage.so: /usr/bin/mysql_config:\ unrecognized\ 
option\ '--libmysqld-libs'\ -lpthread

... presumably stemming from obsolete usage in
cmake/modules/FindMySQLAmarok.cmake.

Could you please take a look?

Thanks!

-- 
Aaron M. Ucko, KB1CJC (amu at alum.mit.edu, ucko at debian.org)
http://www.mit.edu/~amu/ | http://stuff.mit.edu/cgi/finger/?a...@monk.mit.edu
--- End Message ---
--- Begin Message ---
Hi,

After changes in MariaDB packages this build problem has gone.

Best wishes,
Boris--- End Message ---

Processed: Re: monkeysphere: FTBFS in stretch (failing tests)

[Debian Bug Tracking System]

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

> fixed 934034 0.43-3
Bug #934034 [src:monkeysphere] monkeysphere: FTBFS in stretch (failing tests)
Marked as fixed in versions monkeysphere/0.43-3.
> fixed 934034 0.44-1
Bug #934034 [src:monkeysphere] monkeysphere: FTBFS in stretch (failing tests)
Marked as fixed in versions monkeysphere/0.44-1.
> thanks
Stopping processing here.

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

Bug#934860: mate-media-pulse: Can't install on Buster because depends on wrong version of mate-media-common

[Carl Fink]

Package: mate-media-pulse
Severity: grave
Justification: renders package unusable

root@debian-NUCi5:~# apt install mate-media-pulse
Reading package lists... Done
Building dependency tree
Reading state information... Done
Some packages could not be installed. This may mean that you have
requested an impossible situation or if you are using the unstable
distribution that some required packages have not yet been created
or been moved out of Incoming.
The following information may help to resolve the situation:

The following packages have unmet dependencies:
 mate-media-pulse : Depends: mate-media-common (>= 1.8.0+dfsg1-3) but it is not
going to be installed
Depends: mate-media-common (< 1.8.0+dfsg1-3.1) but it is
not going to be installed



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

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

Versions of packages mate-media-pulse depends on:
ii  libatk1.0-0   2.30.0-2
ii  libc6 2.28-10
ii  libcairo2 1.16.0-4
pn  libcanberra-gtk0  
ii  libcanberra0  0.30-7
ii  libfontconfig12.13.1-2
ii  libfreetype6  2.9.1-3
ii  libgdk-pixbuf2.0-02.38.1+dfsg-1
ii  libglib2.0-0  2.58.3-2
ii  libgtk2.0-0   2.24.32-3
ii  libmate-desktop-2-17  1.20.4-2
ii  libpango-1.0-01.42.4-7~deb10u1
ii  libpangocairo-1.0-0   1.42.4-7~deb10u1
ii  libpangoft2-1.0-0 1.42.4-7~deb10u1
ii  libpulse-mainloop-glib0   12.2-4
ii  libpulse0 12.2-4
ii  libstartup-notification0  0.12-6
ii  libunique-1.0-0   1.1.6-6
ii  libx11-6  2:1.6.7-1
ii  libxml2   2.9.4+dfsg1-7+b3
pn  marco 
ii  mate-desktop  1.20.4-2
ii  mate-media-common 1.20.2-1
ii  pulseaudio12.2-4
ii  x11-utils 7.7+4

Versions of packages mate-media-pulse recommends:
ii  sound-theme-freedesktop  0.8-2

mate-media-pulse suggests no packages.

Processed: tagging 934842

[Debian Bug Tracking System]

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

> tags 934842 + confirmed
Bug #934842 [src:libbusiness-hours-perl] libbusiness-hours-perl: FTBFS in 
stretch
Added tag(s) confirmed.
> thanks
Stopping processing here.

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

Bug#695873: marked as done (memtest86+: Serial console does not work)

[Debian Bug Tracking System]

Your message dated Thu, 15 Aug 2019 22:06:13 +
with message-id 
and subject line Bug#695873: fixed in memtest86+ 5.01-3.1
has caused the Debian Bug report #695873,
regarding memtest86+: Serial console does not work
to be marked as done.

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

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


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

Package: memtest86+
Version: 4.20-1.1
Severity: normal

Dear Maintainer,

When recompiled with SERIAL_CONSOLE_DEFAULT=1 and other settings in
config.h the serial console works fine. However setting the
parameters from the boot prompt with lilo (or pxelinux) does not.

In particular these settings do not work (lilo version):
append="console=ttyS1,115200n8"
and similarly
console=ttyS1
console=ttyS0
etc.


From a brief poke at the code I suspect that the commandline is not

successfully being passed from the bootloader to memtest.


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

Kernel: Linux 3.2.0-4-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_GB.utf8, LC_CTYPE=en_GB.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

Versions of packages memtest86+ depends on:
ii  debconf [debconf-2.0]  1.5.46

memtest86+ recommends no packages.

Versions of packages memtest86+ suggests:
ii  grub-pc  1.99-23
pn  hwtools  
pn  kernel-patch-badram  
pn  memtest86
pn  memtester
ii  mtools   4.0.17-1

-- debconf information excluded
--- End Message ---
--- Begin Message ---
Source: memtest86+
Source-Version: 5.01-3.1

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

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

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

Debian distribution maintenance software
pp.
Louis-Philippe Véronneau  (supplier of updated memtest86+ 
package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Thu, 15 Aug 2019 13:49:09 -0400
Source: memtest86+
Architecture: source
Version: 5.01-3.1
Distribution: unstable
Urgency: medium
Maintainer: Yann Dirson 
Changed-By: Louis-Philippe Véronneau 
Closes: 695873
Changes:
 memtest86+ (5.01-3.1) unstable; urgency=medium
 .
   * Non-maintainer upload.
   * Fix passing serial options on the command line
 (Closes: #695873): serial-console-fix.patch
Checksums-Sha1:
 031024d6e67d94e6ab570835adc80a32ff5d20bd 1552 memtest86+_5.01-3.1.dsc
 11cc9f6977eeb394879a27153b49b5b191fe94d6 17524 
memtest86+_5.01-3.1.debian.tar.xz
 bc893dd6b801ed8da43944aa79b1c178bf05dabc 5810 
memtest86+_5.01-3.1_amd64.buildinfo
Checksums-Sha256:
 4569a0eef853a3344aa74361d1a49cc3ce69832b86286cad88b5b575f505a54a 1552 
memtest86+_5.01-3.1.dsc
 3b4d72d26cb284db8936633d3650a7eab8379fe363079324773ac72d93eebada 17524 
memtest86+_5.01-3.1.debian.tar.xz
 124af6c0e0a1999218c0356063e49a3d43e0b155d41c7cda7a1acc59910b7e4c 5810 
memtest86+_5.01-3.1_amd64.buildinfo
Files:
 71696be50aa509118434f8ec744fd916 1552 misc optional memtest86+_5.01-3.1.dsc
 5b10550a3f79f5a4a48e40684a105232 17524 misc optional 
memtest86+_5.01-3.1.debian.tar.xz
 8512a875be76fbb9559e6a3b16028f8e 5810 misc optional 
memtest86+_5.01-3.1_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQEzBAEBCAAdFiEEexZCBNCWcjsBljWrPqHd3bJh2XsFAl1VyxkACgkQPqHd3bJh
2Xuyywf+LqUXUzAv5hrN8zagtn24SJ6/jhGjrriDgqESpHLttlNiIQodDEmgUrTA
WUWn4fbCjN8dfm1jTdEuh/apGsR3tIgZGGJtz09SYjUDdfWHfcUJeAML7ZtrfFoB
BYuOyaThnHXFL+QyJF/TfWeNFVZanZCu47WMp+u9fUXbet2Sq/KsEQqnDRBaIIct
zmGEbbV4SKFMTSgxWGZkRDTHKRGt2eQwKDmz9DoCqWkkjBCmwwlHDqdZKVOkeS6L
UkCah3ouz8nioZ2myt3vNC7te0k3Ir33Ymo3XaNPo++5EFEZT+xDVfHqHBI4SiA2
QbqJvns4nI2JeOgs9ybbxNLtzLh8oA==
=WyKo
-END PGP SIGNATURE End Message ---

Processed: fixed 934842 in 0.13-1

[Debian Bug Tracking System]

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

> fixed 934842 0.13-1
Bug #934842 [src:libbusiness-hours-perl] libbusiness-hours-perl: FTBFS in 
stretch
Marked as fixed in versions libbusiness-hours-perl/0.13-1.
> thanks
Stopping processing here.

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

Bug#934858: Please port viewvc to Python 3 or get it removed from Sid/Bullseye

[Thomas Goirand]

Source: viewvc
Version: 1.1.26
Severity: serious

Hi,

Viewvc seems to be Python 2 only, and having a quick look, it needs a lot of
work to make it work under Python 3.

Since we want to get Python 2 removed from Bullseye, you have no choice but to
either port it to Python3, convince upstream to do so, or drop the package from
Bullseye (and continue to maintain it for the next 5 years in Buster).

Your thoughts?

Cheers,

Thomas Goirand (zigo)

Bug#695873: 695873: Serial console does not work

[Louis-Philippe Véronneau]

Control: tags 695873 + pending

Dear maintainer,

I've prepared an NMU for 695873 (versioned as 5.01-3.1) and
uploaded it without delay.

Regards.

-- 
  ⢀⣴⠾⠻⢶⣦⠀
  ⣾⠁⢠⠒⠀⣿⡁  Louis-Philippe Véronneau
  ⢿⡄⠘⠷⠚⠋   po...@debian.org / veronneau.org
  ⠈⠳⣄
diff -Nru memtest86+-5.01/debian/changelog memtest86+-5.01/debian/changelog
--- memtest86+-5.01/debian/changelog	2015-06-25 17:14:21.0 +
+++ memtest86+-5.01/debian/changelog	2019-08-15 17:49:09.0 +
@@ -1,3 +1,11 @@
+memtest86+ (5.01-3.1) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * Fix passing serial options on the command line
+(Closes: #695873): serial-console-fix.patch
+
+ -- Louis-Philippe Véronneau   Thu, 15 Aug 2019 13:49:09 -0400
+
 memtest86+ (5.01-3) unstable; urgency=medium
 
   * Build with -fgnu89-inline for GCC 5 (Matthias Klose, Closes: #778001)
diff -Nru memtest86+-5.01/debian/patches/serial-console-fix.patch memtest86+-5.01/debian/patches/serial-console-fix.patch
--- memtest86+-5.01/debian/patches/serial-console-fix.patch	1970-01-01 00:00:00.0 +
+++ memtest86+-5.01/debian/patches/serial-console-fix.patch	2019-08-15 17:49:09.0 +
@@ -0,0 +1,21 @@
+Fix passing serial options on the command line
+Index: memtest86+-5.01/lib.c
+===
+--- memtest86+-5.01.orig/lib.c
 memtest86+-5.01/lib.c
+@@ -1141,7 +1141,7 @@ void serial_console_setup(char *param)
+ 
+ 	end++;
+ 
+-	if (*end != '\0' || *end != ' ')
++	if (*end != '\0' && *end != ' ')
+ 		return;  /* garbage at the end */
+ 
+ 	serial_bits = bits;
+@@ -1196,4 +1196,4 @@ void get_list(int x, int y, int len, cha
+ 		   return;
+ 		}
+ 	}
+-}
+\ No newline at end of file
++}
diff -Nru memtest86+-5.01/debian/patches/series memtest86+-5.01/debian/patches/series
--- memtest86+-5.01/debian/patches/series	2015-06-25 17:12:50.0 +
+++ memtest86+-5.01/debian/patches/series	2019-08-15 17:49:09.0 +
@@ -3,3 +3,4 @@
 memtest86+-5.01-O0.patch
 memtest86+-5.01-array-size.patch
 gcc-5
+serial-console-fix.patch


signature.asc
Description: OpenPGP digital signature

Processed: Re: Bug#695873: 695873: Serial console does not work

[Debian Bug Tracking System]

Processing control commands:

> tags 695873 + pending
Bug #695873 [memtest86+] memtest86+: Serial console does not work
Added tag(s) pending.

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

Bug#934850: bat: missing Breaks+Replaces: bareos-bat

[Andreas Beckmann]

Package: bat
Version: 0.11.0-1
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

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

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

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

  Preparing to unpack .../bat_0.11.0-1_amd64.deb ...
  Unpacking bat (0.11.0-1) ...
  dpkg: error processing archive /var/cache/apt/archives/bat_0.11.0-1_amd64.deb 
(--unpack):
   trying to overwrite '/usr/bin/bat', which is also in package bareos-bat 
16.2.6-5
  dpkg-deb: error: paste subprocess was killed by signal (Broken pipe)
  Errors were encountered while processing:
   /var/cache/apt/archives/bat_0.11.0-1_amd64.deb


The bareos-bat package was shipping /usr/bin/bat previously, but that
package has been dropped with the bareos 17.x release.


cheers,

Andreas


bareos-bat=16.2.6-5_bat=0.11.0-1.log.gz
Description: application/gzip

Bug#925823: marked as done (scotch: ftbfs with GCC-9)

[Debian Bug Tracking System]

Your message dated Thu, 15 Aug 2019 19:50:31 +
with message-id 
and subject line Bug#925823: fixed in scotch 6.0.7-3
has caused the Debian Bug report #925823,
regarding scotch: ftbfs with GCC-9
to be marked as done.

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

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


-- 
925823: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=925823
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:scotch
Version: 6.0.6-2
Severity: normal
Tags: sid bullseye
User: debian-...@lists.debian.org
Usertags: ftbfs-gcc-9

Please keep this issue open in the bug tracker for the package it
was filed for.  If a fix in another package is required, please
file a bug for the other package (or clone), and add a block in this
package. Please keep the issue open until the package can be built in
a follow-up test rebuild.

The package fails to build in a test rebuild on at least amd64 with
gcc-9/g++-9, but succeeds to build with gcc-8/g++-8. The
severity of this report will be raised before the bullseye release,
so nothing has to be done for the buster release.

The full build log can be found at:
http://people.debian.org/~doko/logs/gcc9-20190321/scotch_6.0.6-2_unstable_gcc9.log
The last lines of the build log are at the end of this report.

To build with GCC 9, either set CC=gcc-9 CXX=g++-9 explicitly,
or install the gcc, g++, gfortran, ... packages from experimental.

  apt-get -t=experimental install g++ 

Common build failures are new warnings resulting in build failures with
-Werror turned on, or new/dropped symbols in Debian symbols files.
For other C/C++ related build failures see the porting guide at
http://gcc.gnu.org/gcc-9/porting_to.html

GCC 9 also passes the linker option --as-needed by default; typical
build issues are passing libraries before object files to the linker,
or underlinking of convenience libraries built from the same source.

[...]
Strat 1, arch 3, type 2
Strat 1, arch 3, type 3
Strat 1, arch 3, type 4
Strat 1, arch 3, type 5
./test_scotch_graph_map data/m16x16_b1.grf
Strat 0, arch 0, type 0
Strat 0, arch 0, type 1
Strat 0, arch 0, type 2
Strat 0, arch 0, type 3
Strat 0, arch 0, type 4
Strat 0, arch 0, type 5
Strat 0, arch 1, type 0
Strat 0, arch 1, type 1
Strat 0, arch 1, type 2
Strat 0, arch 1, type 3
Strat 0, arch 1, type 4
Strat 0, arch 1, type 5
Strat 0, arch 2, type 0
Strat 0, arch 2, type 1
Strat 0, arch 2, type 2
Strat 0, arch 2, type 3
Strat 0, arch 2, type 4
Strat 0, arch 2, type 5
Strat 0, arch 3, type 0
Strat 0, arch 3, type 1
Strat 0, arch 3, type 2
Strat 0, arch 3, type 3
Strat 0, arch 3, type 4
Strat 0, arch 3, type 5
Strat 1, arch 0, type 0
Strat 1, arch 0, type 1
Strat 1, arch 0, type 2
Strat 1, arch 0, type 3
Strat 1, arch 0, type 4
Strat 1, arch 0, type 5
Strat 1, arch 1, type 0
Strat 1, arch 1, type 1
Strat 1, arch 1, type 2
Strat 1, arch 1, type 3
Strat 1, arch 1, type 4
Strat 1, arch 1, type 5
Strat 1, arch 2, type 0
Strat 1, arch 2, type 1
Strat 1, arch 2, type 2
Strat 1, arch 2, type 3
Strat 1, arch 2, type 4
Strat 1, arch 2, type 5
Strat 1, arch 3, type 0
Strat 1, arch 3, type 1
Strat 1, arch 3, type 2
Strat 1, arch 3, type 3
Strat 1, arch 3, type 4
Strat 1, arch 3, type 5
mpicc -g -O2 -fdebug-prefix-map=/<>/src/check=. 
-fstack-protector-strong -Wformat -Werror=format-security -O3 -fPIC -I. 
-I/usr/include/mpi -Drestrict=__restrict -DCOMMON_FILE_COMPRESS_GZ 
-DCOMMON_FILE_COMPRESS_BZ2 -DCOMMON_FILE_COMPRESS_LZMA -DCOMMON_PTHREAD 
-DSCOTCH_PTHREAD_NUMBER=2 -DCOMMON_RANDOM_FIXED_SEED -DSCOTCH_RENAME 
-DSCOTCH_RENAME_PARSER -DCOMMON_PTHREAD_AFFINITY_LINUX -I../../include 
-L../../lib test_scotch_graph_map_copy.c -o test_scotch_graph_map_copy -lscotch 
-lscotcherr -Wl,-z,relro -pthread -lz -lbz2 -llzma -lm -lrt
./test_scotch_graph_map_copy data/bump_b1.grf
Strat 0, type 0
Strat 0, type 1
Strat 1, type 0
Strat 1, type 1
mpicc -g -O2 -fdebug-prefix-map=/<>/src/check=. 
-fstack-protector-strong -Wformat -Werror=format-security -O3 -fPIC -I. 
-I/usr/include/mpi -Drestrict=__restrict -DCOMMON_FILE_COMPRESS_GZ 
-DCOMMON_FILE_COMPRESS_BZ2 -DCOMMON_FILE_COMPRESS_LZMA -DCOMMON_PTHREAD 
-DSCOTCH_PTHREAD_NUMBER=2 -DCOMMON_RANDOM_FIXED_SEED -DSCOTCH_RENAME 
-DSCOTCH_RENAME_PARSER -DCOMMON_PTHREAD_AFFINITY_LINUX -I../../include 
-L../../lib test_scotch_graph_order.c -o test_scotch_graph_order -lscotch 
-lscotcherr -Wl,-z,relro -pthread -lz -lbz2 -llzma -lm -lrt
./test_scotch_graph_order data/bump.grf
./test_scotch_graph_order data/bump_b1.grf
make[3]: *** [Makefile:249: check_scotch_graph_order] Segmentation fault
make[3]: Leaving directory '/<>/src/check'
make[2]: *** [Makefile:71: check] Error 2

Processed: your mail

[Debian Bug Tracking System]

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

> forwarded 934838 https://github.com/ericniebler/range-v3/issues/1033
Bug #934838 [src:range-v3] range-v3: FTBFS in sid (error: assignment from 
temporary initializer_list does not extend the lifetime of the underlying array)
Set Bug forwarded-to-address to 
'https://github.com/ericniebler/range-v3/issues/1033'.
>
End of message, stopping processing here.

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

Bug#925769: lix: ftbfs with GCC-9

[Reiner Herrmann]

Control: tags -1 - unreproducible moreinfo
Control: affects 931825 + lix

The build failure now also happens on reproducible builds
infrastructure [0].
But it doesn't seem to be related to gcc, but to dub: #931825

[0] https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/lix.html


signature.asc
Description: PGP signature

Processed: Re: lix: ftbfs with GCC-9

[Debian Bug Tracking System]

Processing control commands:

> tags -1 - unreproducible moreinfo
Bug #925769 [src:lix] lix: ftbfs with GCC-9
Removed tag(s) moreinfo and unreproducible.
> affects 931825 + lix
Bug #931825 [dub] Dub executable does not run
Added indication that 931825 affects lix

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

Bug#934844: python-trezor: depends on cruft package.

[peter green]

Package: python-trezor
Severity: serious
Version: 0.9.0-1
Tags: bullseye, sid

python-trezor (build-)depends on the python-ecdsa binary package which is no 
longer built by the corresponding source package.

It's probablly time to drop python 2 support.

Bug#934842: libbusiness-hours-perl: FTBFS in stretch

[Santiago Vila]

Package: src:libbusiness-hours-perl
Version: 0.12-1
Severity: serious
Tags: ftbfs

Dear maintainer:

I tried to build this package in stretch but it failed:


[...]
 debian/rules build-indep
dh build-indep
   dh_testdir -i
   dh_update_autotools_config -i
   dh_auto_configure -i
perl -I. Makefile.PL INSTALLDIRS=vendor "OPTIMIZE=-g -O2 
-fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat 
-Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2" 
"LD=x86_64-linux-gnu-gcc -g -O2 -fdebug-prefix-map=/<>=. 
-fstack-protector-strong -Wformat -Werror=format-security -Wl,-z,relro"
Checking if your kit is complete...
Looks good
Generating a Unix-style Makefile
Writing Makefile for Business::Hours
Writing MYMETA.yml and MYMETA.json
   dh_auto_build -i
make -j1
make[1]: Entering directory '/<>'
cp lib/Business/Hours.pm blib/lib/Business/Hours.pm
Manifying 1 pod document
make[1]: Leaving directory '/<>'
   dh_auto_test -i
make -j1 test TEST_VERBOSE=1
make[1]: Entering directory '/<>'
PERL_DL_NONLAZY=1 PERL_USE_UNSAFE_INC=1 "/usr/bin/perl" 
"-MExtUtils::Command::MM" "-MTest::Harness" "-e" "undef 
*Test::Harness::Switches; test_harness(1, 'blib/lib', 'blib/arch')" t/*.t

#   Failed test at t/1-business-hours.t line 16.
#  got: '0'
# expected: '162000'

#   Failed test 'Got seconds'
#   at t/1-business-hours.t line 24.

#   Failed test at t/1-business-hours.t line 27.
#  got: '0'
# expected: '162000'

#   Failed test at t/1-business-hours.t line 50.
#  got: '378000'
# expected: '32400'
Set::IntSpan::_copy_run_list: Bad order 2: 72000--1
 at /<>/blib/lib/Business/Hours.pm line 270.
# Looks like you planned 17 tests but ran 12.
# Looks like you failed 4 tests of 12 run.
# Looks like your test exited with 255 just after 12.
t/1-business-hours.t .. 
1..17
ok 1 - use Business::Hours;
ok 2
ok 3
not ok 4
ok 5
not ok 6 - Got seconds
not ok 7
not ok 8
ok 9
ok 10
ok 11
ok 12
Dubious, test returned 255 (wstat 65280, 0xff00)
Failed 9/17 subtests 
t/2-holidays.t  
1..6
ok 1 - use Business::Hours;
ok 2 - An object of class 'Business::Hours' isa 'Business::Hours'
ok 3 - no holidays by default
ok 4 - set some holidays
ok 5 - skipped new year holiday
ok 6 - skipped new year holiday
ok
t/99-pod-coverage.t ... skipped: Test::Pod::Coverage 1.00 required for testing 
POD coverage
t/99-pod.t  skipped: Test::Pod 1.00 required for testing POD

Test Summary Report
---
t/1-business-hours.t (Wstat: 65280 Tests: 12 Failed: 4)
  Failed tests:  4, 6-8
  Non-zero exit status: 255
  Parse errors: Bad plan.  You planned 17 tests but ran 12.
Files=4, Tests=18,  1 wallclock secs ( 0.05 usr  0.01 sys +  0.23 cusr  0.02 
csys =  0.31 CPU)
Result: FAIL
Failed 1/4 test programs. 4/18 subtests failed.
Makefile:819: recipe for target 'test_dynamic' failed
make[1]: *** [test_dynamic] Error 255
make[1]: Leaving directory '/<>'
dh_auto_test: make -j1 test TEST_VERBOSE=1 returned exit code 2
debian/rules:4: recipe for target 'build-indep' failed
make: *** [build-indep] Error 2
dpkg-buildpackage: error: debian/rules build-indep gave error exit status 2


The build was made in my autobuilder with "dpkg-buildpackage -A"
and it also fails here:

https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/libbusiness-hours-perl.html

where you can get another build log if you need it.

If this is really a bug in one of the build-depends, please use reassign and 
affects,
so that this is still visible in the BTS web page for this package.

Thanks.

Bug#934843: parsedatetime: FTBFS in stretch

[Santiago Vila]

Package: src:parsedatetime
Version: 2.1-3+deb9u1
Severity: serious
Tags: ftbfs

Dear maintainer:

I tried to build this package in stretch but it failed:


[...]
 debian/rules build-indep
dh build-indep --with python2,python3 --buildsystem pybuild
   dh_testdir -i -O--buildsystem=pybuild
   dh_update_autotools_config -i -O--buildsystem=pybuild
   dh_auto_configure -i -O--buildsystem=pybuild
I: pybuild base:184: python2.7 setup.py config 
running config
I: pybuild base:184: python3.5 setup.py config 
running config
   dh_auto_build -i -O--buildsystem=pybuild
I: pybuild base:184: /usr/bin/python setup.py build 
running build
running build_py
creating /<>/.pybuild/pythonX.Y_2.7/build/parsedatetime
copying parsedatetime/__init__.py -> 
/<>/.pybuild/pythonX.Y_2.7/build/parsedatetime
copying parsedatetime/parsedatetime.py -> 
/<>/.pybuild/pythonX.Y_2.7/build/parsedatetime
copying parsedatetime/context.py -> 
/<>/.pybuild/pythonX.Y_2.7/build/parsedatetime
copying parsedatetime/warns.py -> 
/<>/.pybuild/pythonX.Y_2.7/build/parsedatetime
creating /<>/.pybuild/pythonX.Y_2.7/build/parsedatetime/pdt_locales
copying parsedatetime/pdt_locales/nl_NL.py -> 
/<>/.pybuild/pythonX.Y_2.7/build/parsedatetime/pdt_locales
copying parsedatetime/pdt_locales/base.py -> 
/<>/.pybuild/pythonX.Y_2.7/build/parsedatetime/pdt_locales
copying parsedatetime/pdt_locales/icu.py -> 
/<>/.pybuild/pythonX.Y_2.7/build/parsedatetime/pdt_locales
copying parsedatetime/pdt_locales/ru_RU.py -> 
/<>/.pybuild/pythonX.Y_2.7/build/parsedatetime/pdt_locales
copying parsedatetime/pdt_locales/de_DE.py -> 
/<>/.pybuild/pythonX.Y_2.7/build/parsedatetime/pdt_locales
copying parsedatetime/pdt_locales/en_AU.py -> 
/<>/.pybuild/pythonX.Y_2.7/build/parsedatetime/pdt_locales
copying parsedatetime/pdt_locales/__init__.py -> 
/<>/.pybuild/pythonX.Y_2.7/build/parsedatetime/pdt_locales
copying parsedatetime/pdt_locales/es.py -> 
/<>/.pybuild/pythonX.Y_2.7/build/parsedatetime/pdt_locales
copying parsedatetime/pdt_locales/en_US.py -> 
/<>/.pybuild/pythonX.Y_2.7/build/parsedatetime/pdt_locales
copying parsedatetime/pdt_locales/pt_BR.py -> 
/<>/.pybuild/pythonX.Y_2.7/build/parsedatetime/pdt_locales
I: pybuild base:184: /usr/bin/python3 setup.py build 
running build
running build_py
creating /<>/.pybuild/pythonX.Y_3.5/build/parsedatetime
copying parsedatetime/__init__.py -> 
/<>/.pybuild/pythonX.Y_3.5/build/parsedatetime
copying parsedatetime/parsedatetime.py -> 
/<>/.pybuild/pythonX.Y_3.5/build/parsedatetime
copying parsedatetime/context.py -> 
/<>/.pybuild/pythonX.Y_3.5/build/parsedatetime
copying parsedatetime/warns.py -> 
/<>/.pybuild/pythonX.Y_3.5/build/parsedatetime
creating /<>/.pybuild/pythonX.Y_3.5/build/parsedatetime/pdt_locales
copying parsedatetime/pdt_locales/nl_NL.py -> 
/<>/.pybuild/pythonX.Y_3.5/build/parsedatetime/pdt_locales
copying parsedatetime/pdt_locales/base.py -> 
/<>/.pybuild/pythonX.Y_3.5/build/parsedatetime/pdt_locales
copying parsedatetime/pdt_locales/icu.py -> 
/<>/.pybuild/pythonX.Y_3.5/build/parsedatetime/pdt_locales
copying parsedatetime/pdt_locales/ru_RU.py -> 
/<>/.pybuild/pythonX.Y_3.5/build/parsedatetime/pdt_locales
copying parsedatetime/pdt_locales/de_DE.py -> 
/<>/.pybuild/pythonX.Y_3.5/build/parsedatetime/pdt_locales
copying parsedatetime/pdt_locales/en_AU.py -> 
/<>/.pybuild/pythonX.Y_3.5/build/parsedatetime/pdt_locales
copying parsedatetime/pdt_locales/__init__.py -> 
/<>/.pybuild/pythonX.Y_3.5/build/parsedatetime/pdt_locales
copying parsedatetime/pdt_locales/es.py -> 
/<>/.pybuild/pythonX.Y_3.5/build/parsedatetime/pdt_locales
copying parsedatetime/pdt_locales/en_US.py -> 
/<>/.pybuild/pythonX.Y_3.5/build/parsedatetime/pdt_locales
copying parsedatetime/pdt_locales/pt_BR.py -> 
/<>/.pybuild/pythonX.Y_3.5/build/parsedatetime/pdt_locales
   dh_auto_test -i -O--buildsystem=pybuild
I: pybuild base:184: cd /<>/.pybuild/pythonX.Y_2.7/build; 
python2.7 -m nose tests
.F...SSSSSS
==
FAIL: testDates (tests.TestComplexDateTimes.test)
--
Traceback (most recent call last):
  File 
"/<>/.pybuild/pythonX.Y_2.7/build/tests/TestComplexDateTimes.py", 
line 145, in testDates
self.cal.parse('August 22nd 3:26', start), (target, 3))
  File "/<>/.pybuild/pythonX.Y_2.7/build/tests/utils.py", line 22, 
in decoratedComparator
self.fail(failureMessage % (errMsg, result, check))
AssertionError: Result does not match target value

Result:
(time.struct_time(tm_year=2019, tm_mon=8, tm_mday=22, tm_hour=3, 
tm_min=26, tm_sec=0, tm_wday=0, tm_yday=224, tm_isdst=-1), 3)

Expected:
(time.struct_time(tm_year=2020, tm_mon=8, tm_mday=22, tm_hour=3, 
tm_min=26, tm_sec=0, tm_wday=5, tm_yday=235, tm_isdst=-1), 3)

Bug#934841: sshpubkeys: (build-)depends on cruft package.

[peter green]

Package: sshpubkeys
Severity: serious
Version: 3.1.0-1
Tags: bullseye, sid

The python-sshpubkeys package depends on and the sshpubkeys source package 
build-depends on the python-ecdsa binary package which is no longer built by 
the corresponding source package.

It's probablly time to drop python 2 support from your Package.

Bug#934840: gcc-defaults: Build takes forever in stretch

[Santiago Vila]

Package: src:gcc-defaults
Version: 1.168
Fixed: 1.181
Severity: serious
Tags: ftbfs

Dear maintainer:

I tried to build this package in stretch and this is what happened:


[...]
 debian/rules build-indep
dh_testdir
rm -rf build
mkdir -p build
sed 's/@gcc_suffix@//' debian/generate-cacerts.pl.in \
> debian/generate-cacerts.pl
cd build && perl ../debian/generate-cacerts.pl \
/etc/ssl/certs/ca-certificates.crt
GC Warning: Repeated allocation of very large block (appr. size 671092736):
May lead to memory leak and poor performance.
Exception in thread "main" java.lang.OutOfMemoryError
   <>
keytool error: java.security.cert.CertificateException
keytool error: java.security.cert.CertificateException
GC Warning: Repeated allocation of very large block (appr. size 671092736):
May lead to memory leak and poor performance.
Exception in thread "main" java.lang.OutOfMemoryError
   <>
GC Warning: Repeated allocation of very large block (appr. size 671092736):
May lead to memory leak and poor performance.
Exception in thread "main" java.lang.OutOfMemoryError
   <>
GC Warning: Repeated allocation of very large block (appr. size 671092736):
May lead to memory leak and poor performance.
Exception in thread "main" java.lang.OutOfMemoryError
   <>
GC Warning: Repeated allocation of very large block (appr. size 671092736):
May lead to memory leak and poor performance.
Exception in thread "main" java.lang.OutOfMemoryError
   <>
GC Warning: Repeated allocation of very large block (appr. size 671092736):
May lead to memory leak and poor performance.
Exception in thread "main" java.lang.OutOfMemoryError
   <>
GC Warning: Repeated allocation of very large block (appr. size 671092736):
May lead to memory leak and poor performance.
Exception in thread "main" java.lang.OutOfMemoryError
   <>
GC Warning: Repeated allocation of very large block (appr. size 671092736):
May lead to memory leak and poor performance.
Exception in thread "main" java.lang.OutOfMemoryError
   <>
GC Warning: Repeated allocation of very large block (appr. size 671092736):
May lead to memory leak and poor performance.
Exception in thread "main" java.lang.OutOfMemoryError
   <>
GC Warning: Repeated allocation of very large block (appr. size 671092736):
May lead to memory leak and poor performance.
Exception in thread "main" java.lang.OutOfMemoryError
   <>
GC Warning: Repeated allocation of very large block (appr. size 671092736):
May lead to memory leak and poor performance.
Exception in thread "main" java.lang.OutOfMemoryError
   <>
GC Warning: Repeated allocation of very large block (appr. size 671092736):
May lead to memory leak and poor performance.
Exception in thread "main" java.lang.OutOfMemoryError
   <>
GC Warning: Repeated allocation of very large block (appr. size 671092736):
May lead to memory leak and poor performance.
Exception in thread "main" java.lang.OutOfMemoryError
   <>
GC Warning: Repeated allocation of very large block (appr. size 671092736):
May lead to memory leak and poor performance.
Exception in thread "main" java.lang.OutOfMemoryError
   <>
GC Warning: Repeated allocation of very large block (appr. size 671092736):
May lead to memory leak and poor performance.
Exception in thread "main" java.lang.OutOfMemoryError
   <>
GC Warning: Repeated allocation of very large block (appr. size 671092736):
May lead to memory leak and poor performance.
Exception in thread "main" java.lang.OutOfMemoryError
   <>
GC Warning: Repeated allocation of very large block (appr. size 671092736):
May lead to memory leak and poor performance.
Exception in thread "main" java.lang.OutOfMemoryError
   <>
GC Warning: Repeated allocation of very large block (appr. size 671092736):
May lead to memory leak and poor performance.
Exception in thread "main" java.lang.OutOfMemoryError
   <>
GC Warning: Repeated allocation of very large block (appr. size 671092736):
May lead to memory leak and poor performance.
Exception in thread "main" java.lang.OutOfMemoryError
   <>
GC Warning: Repeated allocation of very large block (appr. size 671092736):
May lead to memory leak and poor performance.
Exception in thread "main" java.lang.OutOfMemoryError
   <>
keytool error: java.security.cert.CertificateException
GC Warning: Repeated allocation of very large block (appr. size 671092736):
May lead to memory leak and poor performance.
make: *** wait: No child processes.  Stop.
make: *** Waiting for unfinished jobs
make: *** wait: No child processes.  Stop.


I had to interrupt the build because it was taking too long.

The build was tried in a machine with plenty of memory (6.5 GB of RAM).
Previously, it was possible to build the package 

Bug#934839: python-keepkey: depends on cruft package.

[peter green]

Package: python-keepkey
Severity: serious
Version: 0.7.3-1
Tags: bullseye, sid

python-keepkey depends on the python-ecdsa binary package which is no longer 
built by the corresponding source package.

If you want your package to stay around you need to migrate to python 3.

Bug#934838: range-v3: FTBFS in sid (error: assignment from temporary initializer_list does not extend the lifetime of the underlying array)

[Santiago Vila]

Package: src:range-v3
Version: 0.5.0-1
Severity: serious
Tags: ftbfs

Dear maintainer:

I tried to build this package in sid but it failed:


[...]
 debian/rules binary-indep
dh binary-indep
   dh_update_autotools_config -i
   dh_autoreconf -i
   debian/rules override_dh_auto_configure
make[1]: Entering directory '/<>'
dh_auto_configure -- -DCMAKE_SKIP_INSTALL_ALL_DEPENDENCY=ON -DRANGES_NATIVE=OFF 
-DRANGES_VERBOSE_BUILD=ON
cd obj-x86_64-linux-gnu && cmake -DCMAKE_INSTALL_PREFIX=/usr 
-DCMAKE_BUILD_TYPE=None -DCMAKE_INSTALL_SYSCONFDIR=/etc 
-DCMAKE_INSTALL_LOCALSTATEDIR=/var -DCMAKE_EXPORT_NO_PACKAGE_REGISTRY=ON 
-DCMAKE_FIND_PACKAGE_NO_PACKAGE_REGISTRY=ON -DCMAKE_INSTALL_RUNSTATEDIR=/run 
"-GUnix Makefiles" -DCMAKE_VERBOSE_MAKEFILE=ON 
-DCMAKE_INSTALL_LIBDIR=lib/x86_64-linux-gnu 
-DCMAKE_SKIP_INSTALL_ALL_DEPENDENCY=ON -DRANGES_NATIVE=OFF 
-DRANGES_VERBOSE_BUILD=ON ..
-- The CXX compiler identification is GNU 9.2.1
-- Check for working CXX compiler: /usr/bin/c++
-- Check for working CXX compiler: /usr/bin/c++ -- works
-- Detecting CXX compiler ABI info
-- Detecting CXX compiler ABI info - done
-- Detecting CXX compile features

[... snipped ...]

cd /<>/obj-x86_64-linux-gnu && /usr/bin/cmake -E cmake_depends 
"Unix Makefiles" /<> /<>/test/action 
/<>/obj-x86_64-linux-gnu 
/<>/obj-x86_64-linux-gnu/test/action 
/<>/obj-x86_64-linux-gnu/test/action/CMakeFiles/act.remove_if.dir/DependInfo.cmake
 --color=
Scanning dependencies of target act.remove_if
make[4]: Leaving directory '/<>/obj-x86_64-linux-gnu'
make -f test/action/CMakeFiles/act.remove_if.dir/build.make 
test/action/CMakeFiles/act.remove_if.dir/build
make[4]: Entering directory '/<>/obj-x86_64-linux-gnu'
[ 59%] Building CXX object 
test/action/CMakeFiles/act.remove_if.dir/remove_if.cpp.o
cd /<>/obj-x86_64-linux-gnu/test/action && /usr/bin/c++   
-I/<>/include  -g -O2 -fdebug-prefix-map=/<>=. 
-fstack-protector-strong -Wformat -Werror=format-security 
-Wno-error=maybe-uninitialized -Wdate-time -D_FORTIFY_SOURCE=2 -O3 -DNDEBUG   
-std=c++11 -Wall -Wextra -Werror -fdiagnostics-show-template-tree 
-ftemplate-backtrace-limit=0 -fomit-frame-pointer -Ofast -fstrict-aliasing 
-ffast-math -fsized-deallocation -DRANGES_CXX_ALIGNED_NEW=0 -pedantic 
-pedantic-errors -Wno-padded -Wno-old-style-cast -Wno-shadow -Wno-noexcept-type 
-o CMakeFiles/act.remove_if.dir/remove_if.cpp.o -c 
/<>/test/action/remove_if.cpp
[ 59%] Linking CXX executable act.remove_if
cd /<>/obj-x86_64-linux-gnu/test/action && /usr/bin/cmake -E 
cmake_link_script CMakeFiles/act.remove_if.dir/link.txt --verbose=1
/usr/bin/c++  -g -O2 -fdebug-prefix-map=/<>=. 
-fstack-protector-strong -Wformat -Werror=format-security 
-Wno-error=maybe-uninitialized -Wdate-time -D_FORTIFY_SOURCE=2 -O3 -DNDEBUG  
-Wl,-z,relro CMakeFiles/act.remove_if.dir/remove_if.cpp.o  -o act.remove_if 
make[4]: Leaving directory '/<>/obj-x86_64-linux-gnu'
[ 59%] Built target act.remove_if
make -f test/action/CMakeFiles/act.unstable_remove_if.dir/build.make 
test/action/CMakeFiles/act.unstable_remove_if.dir/depend
make[4]: Entering directory '/<>/obj-x86_64-linux-gnu'
cd /<>/obj-x86_64-linux-gnu && /usr/bin/cmake -E cmake_depends 
"Unix Makefiles" /<> /<>/test/action 
/<>/obj-x86_64-linux-gnu 
/<>/obj-x86_64-linux-gnu/test/action 
/<>/obj-x86_64-linux-gnu/test/action/CMakeFiles/act.unstable_remove_if.dir/DependInfo.cmake
 --color=
Scanning dependencies of target act.unstable_remove_if
make[4]: Leaving directory '/<>/obj-x86_64-linux-gnu'
make -f test/action/CMakeFiles/act.unstable_remove_if.dir/build.make 
test/action/CMakeFiles/act.unstable_remove_if.dir/build
make[4]: Entering directory '/<>/obj-x86_64-linux-gnu'
[ 59%] Building CXX object 
test/action/CMakeFiles/act.unstable_remove_if.dir/unstable_remove_if.cpp.o
cd /<>/obj-x86_64-linux-gnu/test/action && /usr/bin/c++   
-I/<>/include  -g -O2 -fdebug-prefix-map=/<>=. 
-fstack-protector-strong -Wformat -Werror=format-security 
-Wno-error=maybe-uninitialized -Wdate-time -D_FORTIFY_SOURCE=2 -O3 -DNDEBUG   
-std=c++11 -Wall -Wextra -Werror -fdiagnostics-show-template-tree 
-ftemplate-backtrace-limit=0 -fomit-frame-pointer -Ofast -fstrict-aliasing 
-ffast-math -fsized-deallocation -DRANGES_CXX_ALIGNED_NEW=0 -pedantic 
-pedantic-errors -Wno-padded -Wno-old-style-cast -Wno-shadow -Wno-noexcept-type 
-o CMakeFiles/act.unstable_remove_if.dir/unstable_remove_if.cpp.o -c 
/<>/test/action/unstable_remove_if.cpp
[ 59%] Linking CXX executable act.unstable_remove_if
cd /<>/obj-x86_64-linux-gnu/test/action && /usr/bin/cmake -E 
cmake_link_script CMakeFiles/act.unstable_remove_if.dir/link.txt --verbose=1
/usr/bin/c++  -g -O2 -fdebug-prefix-map=/<>=. 
-fstack-protector-strong -Wformat -Werror=format-security 
-Wno-error=maybe-uninitialized -Wdate-time -D_FORTIFY_SOURCE=2 -O3 -DNDEBUG  
-Wl,-z,relro CMakeFiles/act.unstable_remove_if.dir/unstable_remove_if.cpp.o  -o 
act.unstable_remove_if 
make[4]: Leaving 

Bug#896248: marked as done (python3-pylint-flask: pylint_flask fails to import)

[Debian Bug Tracking System]

Your message dated Thu, 15 Aug 2019 18:36:10 +
with message-id 
and subject line Bug#896248: fixed in pylint-flask 0.5-3
has caused the Debian Bug report #896248,
regarding python3-pylint-flask: pylint_flask fails to import
to be marked as done.

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

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


-- 
896248: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=896248
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: python3-pylint-flask
Version: 0.5-2
Severity: serious
User: helm...@debian.org
Usertags: python-import

After installing python3-pylint-flask importing the module pylint_flask
into a python interpreter fails with the following error:

Traceback (most recent call last):
  File "", line 1, in 
  File "/usr/lib/python3/dist-packages/pylint_flask/__init__.py", line 3, in 

from astroid import MANAGER
ModuleNotFoundError: No module named 'astroid'

The vast majority of import failures is attributed to missing dependencies.
Often times that manifests as an ImportError or ModuleNotFoundError.
Typically, dependencies should be inserted by dh-python via ${python:Depends}
or ${python3:Depends}. Thus a missing dependency can be caused by incomplete
install_requires in setup.py. Sometimes a missing dependency of a dependency
is the cause, in such cases this bug should be reassigned.

Helmut
--- End Message ---
--- Begin Message ---
Source: pylint-flask
Source-Version: 0.5-3

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

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

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

Debian distribution maintenance software
pp.
Andrey Rahmatullin  (supplier of updated pylint-flask package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Thu, 15 Aug 2019 23:16:10 +0500
Source: pylint-flask
Architecture: source
Version: 0.5-3
Distribution: unstable
Urgency: medium
Maintainer: Debian Python Modules Team 

Changed-By: Andrey Rahmatullin 
Closes: 896248 896287
Changes:
 pylint-flask (0.5-3) unstable; urgency=medium
 .
   * Team upload.
 .
   [ Ondřej Nový ]
   * d/control: Set Vcs-* to salsa.debian.org
   * d/copyright: Use https protocol in Format field
   * d/control: Remove ancient X-Python-Version field
   * d/control: Remove ancient X-Python3-Version field
   * Convert git repository from git-dpm to gbp layout
   * Enable autopkgtest-pkg-python testsuite
   * Add python{,3}-astroid to depends (Closes: #896287, #896248)
   * Use debhelper-compat instead of debian/compat.
   * Drop Python 2 support.
 .
   [ Andrey Rahmatullin ]
   * Fix compatibility with new astroid.
Checksums-Sha1:
 5caccc242e59fcc6a56dccc954ee801547ff4977 2123 pylint-flask_0.5-3.dsc
 7293344254887b68d237f0d0b17d7c3a90f6f10f 3060 pylint-flask_0.5-3.debian.tar.xz
 b6d94c60ba08eceb8d1802c9b64eb376d41da4e4 6269 
pylint-flask_0.5-3_amd64.buildinfo
Checksums-Sha256:
 63097d916440c43db74c3a59f2d11cfcbd4f84d74973327d5a8db13e588a88ee 2123 
pylint-flask_0.5-3.dsc
 55279db7d838bac72c074e344b98192a469102b15275e8047766c6257eb9db9a 3060 
pylint-flask_0.5-3.debian.tar.xz
 51d172115db605f3eeaf7cb50f26111d82ddf400164ec6af2381b87d2ec0f3ab 6269 
pylint-flask_0.5-3_amd64.buildinfo
Files:
 8858a8330ea8a05afd750ebba7e7091c 2123 python optional pylint-flask_0.5-3.dsc
 667e9b8855b59501eeb6dc7c1526242a 3060 python optional 
pylint-flask_0.5-3.debian.tar.xz
 15e64f7c148bbc5edf77ec33d1e34d15 6269 python optional 
pylint-flask_0.5-3_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEolIP6gqGcKZh3YxVM2L3AxpJkuEFAl1VofgACgkQM2L3AxpJ
kuHE0w/+Pvxtl7jQ/tCdGdlZE1TmdoDssNagB98te8WVKXRD0ujpBLJUH/bOUD7M
24/ZCHQ/7JJhIrdfAFvVRXuVB6fejGgW5QgG54AzTWL1UwbHhkjF4TEaPFG7LbGf
3NayEo3Y4z61UY4YCpSYogQkI8Sb2UewTvWr7SltiJNQN0qIgEI57ByuqxohBLCw
Nb5FiQoPRWOwg2VMN8GVlqr8mv+PgApYfqFJcNs/RWAMZk59ECsQbyeBvB7Hauk/
I+H4TNI/NbYiMNsMG6r5ZcMpecdtry7bVgt4riJaI4UPuuWGUNjxcM5z+Tcn04b0
tlQCXvOk+uldwfQRQSOTzRS5Kr73AKaNGy9cSncmM2rQ0qKQFN5QbZ5GtKpe7+Ka
c2/IojPNBDujRqL9JcBerniXMuKl6gT655Yso0+Qlaz3G3M6BHaYiFBfP6JMMTwi
ZjbcFIiJCC4p3AruFBW5IciiWDjb4x9fOjD1ZuEkkBJdxpw4b0llgqCHzUUvxgJR
SrCFvq+arfTUsaSlffL42nrR03VEISR6bKTz0s1An1ysZmGCy60vbWlKEpQ26B8L

Bug#896287: marked as done (python-pylint-flask: pylint_flask fails to import)

[Debian Bug Tracking System]

Your message dated Thu, 15 Aug 2019 18:36:10 +
with message-id 
and subject line Bug#896287: fixed in pylint-flask 0.5-3
has caused the Debian Bug report #896287,
regarding python-pylint-flask: pylint_flask fails to import
to be marked as done.

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

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


-- 
896287: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=896287
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: python-pylint-flask
Version: 0.5-2
Severity: serious
User: helm...@debian.org
Usertags: python-import

After installing python-pylint-flask importing the module pylint_flask
into a python interpreter fails with the following error:

Traceback (most recent call last):
  File "", line 1, in 
  File "/usr/lib/python2.7/dist-packages/pylint_flask/__init__.py", line 3, in 

from astroid import MANAGER
ImportError: No module named astroid

The vast majority of import failures is attributed to missing dependencies.
Often times that manifests as an ImportError or ModuleNotFoundError.
Typically, dependencies should be inserted by dh-python via ${python:Depends}
or ${python3:Depends}. Thus a missing dependency can be caused by incomplete
install_requires in setup.py. Sometimes a missing dependency of a dependency
is the cause, in such cases this bug should be reassigned.

Helmut
--- End Message ---
--- Begin Message ---
Source: pylint-flask
Source-Version: 0.5-3

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

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

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

Debian distribution maintenance software
pp.
Andrey Rahmatullin  (supplier of updated pylint-flask package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Thu, 15 Aug 2019 23:16:10 +0500
Source: pylint-flask
Architecture: source
Version: 0.5-3
Distribution: unstable
Urgency: medium
Maintainer: Debian Python Modules Team 

Changed-By: Andrey Rahmatullin 
Closes: 896248 896287
Changes:
 pylint-flask (0.5-3) unstable; urgency=medium
 .
   * Team upload.
 .
   [ Ondřej Nový ]
   * d/control: Set Vcs-* to salsa.debian.org
   * d/copyright: Use https protocol in Format field
   * d/control: Remove ancient X-Python-Version field
   * d/control: Remove ancient X-Python3-Version field
   * Convert git repository from git-dpm to gbp layout
   * Enable autopkgtest-pkg-python testsuite
   * Add python{,3}-astroid to depends (Closes: #896287, #896248)
   * Use debhelper-compat instead of debian/compat.
   * Drop Python 2 support.
 .
   [ Andrey Rahmatullin ]
   * Fix compatibility with new astroid.
Checksums-Sha1:
 5caccc242e59fcc6a56dccc954ee801547ff4977 2123 pylint-flask_0.5-3.dsc
 7293344254887b68d237f0d0b17d7c3a90f6f10f 3060 pylint-flask_0.5-3.debian.tar.xz
 b6d94c60ba08eceb8d1802c9b64eb376d41da4e4 6269 
pylint-flask_0.5-3_amd64.buildinfo
Checksums-Sha256:
 63097d916440c43db74c3a59f2d11cfcbd4f84d74973327d5a8db13e588a88ee 2123 
pylint-flask_0.5-3.dsc
 55279db7d838bac72c074e344b98192a469102b15275e8047766c6257eb9db9a 3060 
pylint-flask_0.5-3.debian.tar.xz
 51d172115db605f3eeaf7cb50f26111d82ddf400164ec6af2381b87d2ec0f3ab 6269 
pylint-flask_0.5-3_amd64.buildinfo
Files:
 8858a8330ea8a05afd750ebba7e7091c 2123 python optional pylint-flask_0.5-3.dsc
 667e9b8855b59501eeb6dc7c1526242a 3060 python optional 
pylint-flask_0.5-3.debian.tar.xz
 15e64f7c148bbc5edf77ec33d1e34d15 6269 python optional 
pylint-flask_0.5-3_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEolIP6gqGcKZh3YxVM2L3AxpJkuEFAl1VofgACgkQM2L3AxpJ
kuHE0w/+Pvxtl7jQ/tCdGdlZE1TmdoDssNagB98te8WVKXRD0ujpBLJUH/bOUD7M
24/ZCHQ/7JJhIrdfAFvVRXuVB6fejGgW5QgG54AzTWL1UwbHhkjF4TEaPFG7LbGf
3NayEo3Y4z61UY4YCpSYogQkI8Sb2UewTvWr7SltiJNQN0qIgEI57ByuqxohBLCw
Nb5FiQoPRWOwg2VMN8GVlqr8mv+PgApYfqFJcNs/RWAMZk59ECsQbyeBvB7Hauk/
I+H4TNI/NbYiMNsMG6r5ZcMpecdtry7bVgt4riJaI4UPuuWGUNjxcM5z+Tcn04b0
tlQCXvOk+uldwfQRQSOTzRS5Kr73AKaNGy9cSncmM2rQ0qKQFN5QbZ5GtKpe7+Ka
c2/IojPNBDujRqL9JcBerniXMuKl6gT655Yso0+Qlaz3G3M6BHaYiFBfP6JMMTwi
ZjbcFIiJCC4p3AruFBW5IciiWDjb4x9fOjD1ZuEkkBJdxpw4b0llgqCHzUUvxgJR
SrCFvq+arfTUsaSlffL42nrR03VEISR6bKTz0s1An1ysZmGCy60vbWlKEpQ26B8L

Processed: reassign 915895 to src:redis-py-cluster

[Debian Bug Tracking System]

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

> reassign 915895 src:redis-py-cluster 1.3.3-1
Bug #915895 [src:python-limits] python-limits FTBFS: ERROR: Failure: 
ImportError (cannot import name b)
Bug reassigned from package 'src:python-limits' to 'src:redis-py-cluster'.
No longer marked as found in versions python-limits/1.3-1.
Ignoring request to alter fixed versions of bug #915895 to the same values 
previously set
Bug #915895 [src:redis-py-cluster] python-limits FTBFS: ERROR: Failure: 
ImportError (cannot import name b)
Marked as found in versions redis-py-cluster/1.3.3-1.
> thanks
Stopping processing here.

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

Processed (with 1 error): Re: Bug#915895: python-limits FTBFS: ERROR: Failure: ImportError (cannot import name b)

[Debian Bug Tracking System]

Processing control commands:

> reassign -1 src:redis-py-cluster/1.3.3-1
Unknown command or malformed arguments to command.

> severity -1 grave
Bug #915895 [src:python-limits] python-limits FTBFS: ERROR: Failure: 
ImportError (cannot import name b)
Severity set to 'grave' from 'serious'
> forwarded -1 https://github.com/Grokzen/redis-py-cluster/issues/295
Bug #915895 [src:python-limits] python-limits FTBFS: ERROR: Failure: 
ImportError (cannot import name b)
Set Bug forwarded-to-address to 
'https://github.com/Grokzen/redis-py-cluster/issues/295'.
> affects -1 src:python-limits
Bug #915895 [src:python-limits] python-limits FTBFS: ERROR: Failure: 
ImportError (cannot import name b)
Added indication that 915895 affects src:python-limits

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

Bug#915895: python-limits FTBFS: ERROR: Failure: ImportError (cannot import name b)

[Andrey Rahmatullin]

Control: reassign -1 src:redis-py-cluster/1.3.3-1
Control: severity -1 grave
Control: forwarded -1 https://github.com/Grokzen/redis-py-cluster/issues/295
Control: affects -1 src:python-limits

On Sat, Feb 09, 2019 at 06:57:54PM +0100, Slavko wrote:
> while this of course affects the python-limits build, it is not its
> bug. As one can see, it is caused in test by importing rediscluster:
Exactly. Fixing the bug metadata accordingly.
Work in progress is at
https://github.com/Grokzen/redis-py-cluster/pull/296 and looks promising.

-- 
WBR, wRAR


signature.asc
Description: PGP signature

Bug#934035: ocrmypdf: FTBFS in stretch (failing tests)

[Sean Whitton]

Hello,

On Tue 06 Aug 2019 at 12:31pm -07, James R Barlow wrote:

> The issue here is that we have an old version of ocrmypdf (4.3.5) with a
> backported version of Ghostscript (9.26) and the latter's behavior has
> changed in a way that breaks the test.
>
> I recommend disabling the test and documenting a caveat that certain
> metadata may not be preserved in output files. This is arguably a fairly
> minor loss of functionality.

Thanks.  My intention is to just update ocrmypdf to a newer release.

-- 
Sean Whitton


signature.asc
Description: PGP signature

Bug#925639: marked as done (bind-dyndb-ldap: ftbfs with GCC-9)

[Debian Bug Tracking System]

Your message dated Thu, 15 Aug 2019 17:49:15 +
with message-id 
and subject line Bug#925639: fixed in bind-dyndb-ldap 11.1-6
has caused the Debian Bug report #925639,
regarding bind-dyndb-ldap: ftbfs with GCC-9
to be marked as done.

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

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


-- 
925639: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=925639
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:bind-dyndb-ldap
Version: 11.1-5
Severity: normal
Tags: sid bullseye
User: debian-...@lists.debian.org
Usertags: ftbfs-gcc-9

Please keep this issue open in the bug tracker for the package it
was filed for.  If a fix in another package is required, please
file a bug for the other package (or clone), and add a block in this
package. Please keep the issue open until the package can be built in
a follow-up test rebuild.

The package fails to build in a test rebuild on at least amd64 with
gcc-9/g++-9, but succeeds to build with gcc-8/g++-8. The
severity of this report will be raised before the bullseye release,
so nothing has to be done for the buster release.

The full build log can be found at:
http://people.debian.org/~doko/logs/gcc9-20190321/bind-dyndb-ldap_11.1-5_unstable_gcc9.log
The last lines of the build log are at the end of this report.

To build with GCC 9, either set CC=gcc-9 CXX=g++-9 explicitly,
or install the gcc, g++, gfortran, ... packages from experimental.

  apt-get -t=experimental install g++ 

Common build failures are new warnings resulting in build failures with
-Werror turned on, or new/dropped symbols in Debian symbols files.
For other C/C++ related build failures see the porting guide at
http://gcc.gnu.org/gcc-9/porting_to.html

GCC 9 also passes the linker option --as-needed by default; typical
build issues are passing libraries before object files to the linker,
or underlinking of convenience libraries built from the same source.

[...]
/bin/bash ../libtool  --tag=CC   --mode=compile gcc -DHAVE_CONFIG_H -I. 
-I../../src -I..   -Wdate-time -D_FORTIFY_SOURCE=2 -Wall -Wextra -Werror 
-std=gnu99 -O2 -I/usr/include -D_REENTRANT -D_LARGEFILE_SOURCE 
-D_FILE_OFFSET_BITS=64 -D_GNU_SOURCE -g -O2 
-fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat 
-Werror=format-security -fvisibility=hidden -fno-delete-null-pointer-checks -c 
-o ldap_la-bindcfg.lo `test -f 'bindcfg.c' || echo '../../src/'`bindcfg.c
/bin/bash ../libtool  --tag=CC   --mode=compile gcc -DHAVE_CONFIG_H -I. 
-I../../src -I..   -Wdate-time -D_FORTIFY_SOURCE=2 -Wall -Wextra -Werror 
-std=gnu99 -O2 -I/usr/include -D_REENTRANT -D_LARGEFILE_SOURCE 
-D_FILE_OFFSET_BITS=64 -D_GNU_SOURCE -g -O2 
-fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat 
-Werror=format-security -fvisibility=hidden -fno-delete-null-pointer-checks -c 
-o ldap_la-empty_zones.lo `test -f 'empty_zones.c' || echo 
'../../src/'`empty_zones.c
/bin/bash ../libtool  --tag=CC   --mode=compile gcc -DHAVE_CONFIG_H -I. 
-I../../src -I..   -Wdate-time -D_FORTIFY_SOURCE=2 -Wall -Wextra -Werror 
-std=gnu99 -O2 -I/usr/include -D_REENTRANT -D_LARGEFILE_SOURCE 
-D_FILE_OFFSET_BITS=64 -D_GNU_SOURCE -g -O2 
-fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat 
-Werror=format-security -fvisibility=hidden -fno-delete-null-pointer-checks -c 
-o ldap_la-fwd.lo `test -f 'fwd.c' || echo '../../src/'`fwd.c
libtool: compile:  gcc -DHAVE_CONFIG_H -I. -I../../src -I.. -Wdate-time 
-D_FORTIFY_SOURCE=2 -Wall -Wextra -Werror -std=gnu99 -O2 -I/usr/include 
-D_REENTRANT -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64 -D_GNU_SOURCE -g -O2 
-fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat 
-Werror=format-security -fvisibility=hidden -fno-delete-null-pointer-checks -c 
../../src/empty_zones.c  -fPIC -DPIC -o .libs/ldap_la-empty_zones.o
libtool: compile:  gcc -DHAVE_CONFIG_H -I. -I../../src -I.. -Wdate-time 
-D_FORTIFY_SOURCE=2 -Wall -Wextra -Werror -std=gnu99 -O2 -I/usr/include 
-D_REENTRANT -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64 -D_GNU_SOURCE -g -O2 
-fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat 
-Werror=format-security -fvisibility=hidden -fno-delete-null-pointer-checks -c 
../../src/fwd.c  -fPIC -DPIC -o .libs/ldap_la-fwd.o
libtool: compile:  gcc -DHAVE_CONFIG_H -I. -I../../src -I.. -Wdate-time 
-D_FORTIFY_SOURCE=2 -Wall -Wextra -Werror -std=gnu99 -O2 -I/usr/include 
-D_REENTRANT -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64 -D_GNU_SOURCE -g -O2 
-fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat 
-Werror=format-security -fvisibility=hidden -fno-delete-null-pointer-checks -c 
../../src/bindcfg.c  -fPIC -DPIC -o .libs/ldap_la-bindcfg.o
libtool: 

Processed: Re: Bug#695873: memtest86+: Serial console does not work

[Debian Bug Tracking System]

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

> tag 695873 patch
Bug #695873 [memtest86+] memtest86+: Serial console does not work
Added tag(s) patch.
>
End of message, stopping processing here.

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

Processed: Re: Bug#921194: amarok: Amarok depends on libmariadbd18, which doesn't exist any longer

[Debian Bug Tracking System]

Processing control commands:

> tag -1 patch
Bug #921194 [amarok] amarok: Amarok depends on libmariadbd18, which doesn't 
exist any longer
Added tag(s) patch.

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

Bug#921194: amarok: Amarok depends on libmariadbd18, which doesn't exist any longer

[Louis-Philippe Véronneau]

Control: tag -1 patch

Well, since this is a Team maintained package, I've created a Merge
Request on the Salsa VCS and asked people on IRC to merge and upload it:

https://salsa.debian.org/qt-kde-team/extras/amarok/merge_requests/1/diffs

As stated on Salsa, I've built with this patch on Sid and Testing and
the resulting package depends on libmariadb19 instead of libmariadb18.

From the feedback I've had this should be uploaded soonish.

Cheers!

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



signature.asc
Description: OpenPGP digital signature

Processed: retitle 934673 to libgit2-glib ftbfs when chroot has ccache installed

[Debian Bug Tracking System]

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

> retitle 934673 libgit2-glib ftbfs when chroot has ccache installed
Bug #934673 [libgit2-glib] libgit2-glib ftbfs with meson.build:148:2: ERROR: 
Assert failed: libgit2 ssh support was requested, but not found. Use 
-Dssh=false to build without it
Changed Bug title to 'libgit2-glib ftbfs when chroot has ccache installed' from 
'libgit2-glib ftbfs with meson.build:148:2: ERROR: Assert failed: libgit2 ssh 
support was requested, but not found. Use -Dssh=false to build without it'.
> thanks
Stopping processing here.

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

Bug#933185: fai-server: /etc/fai/apt/sources.list should not contain trusted=yes to skip GPG verification

[Christian Seiler]

Hi,

(Sorry, overlooked your email.)

Am 2019-08-12 21:31, schrieb Thomas Lange:

I think we cannot fix it in this way.
gpg --export 2BF8D9FE074BCDE4 may not work, if the key is not already
downloaded and available for gpg. I also do not want to force to
install the package debian-keyring on the fai server.
And we should not create a file when calling fai-make-nfsroot under
/etc which is normally a config file.

The idea is to ship the gpg key directly in the fai-server package.
So I would add the file /etc/fai/apt/trusted.gpg.d/fai-project.gpg to
the package fai-server. What do you think?


Sorry if I wasn't clearer in my bugreport. Yes, I did mean that
you should simply add the fai-project.gpg to the package. The
gpg --export was just a demonstration how to work around this
issue with the current version of FAI.

So yes, if you added the file to the package and removed the
[trusted=yes] in the /etc/fai/apt/sources.list, that would be
perfect.

Thanks!

Best regards,
Christian

Processed: severity of 866960 is important

[Debian Bug Tracking System]

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

> severity 866960 important
Bug #866960 [libfreetype6] libfreetype6: ABI/API change yielding a blank line 
between characters due to different rounding for TrueType fonts
Severity set to 'important' from 'serious'
> thanks
Stopping processing here.

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

Bug#925823: scotch: ftbfs with GCC-9

[Drew Parsons]

Package: scotch
Version: 6.0.7-2
Followup-For: Bug #925823

The segfault is also triggered by order_io.c l.292, still segfaulting in
./test_scotch_graph_order data/bump_b1.grf

Program received signal SIGSEGV, Segmentation fault.
0x77f9c531 in _SCOTCHorderSaveTree (ordeptr=, 
vlbltab=, stream=0x9260) at order_io.c:292
292 order_io.c: No such file or directory.
(gdb) bt
#0  0x77f9c531 in _SCOTCHorderSaveTree (ordeptr=, 
vlbltab=, stream=0x9260) at order_io.c:292
#1  0x53f3 in main (argc=, argv=) at 
test_scotch_graph_order.c:144


bump_b1.grf seems to be causing problems, see also Bug#932777.

I'll work around by skipping the failing bump_b1.grf tests (patch
skip_failing_tests.patch), until upstream addresses
https://gforge.inria.fr/tracker/index.php?func=detail=21768_id=248=1079





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

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

Versions of packages scotch depends on:
ii  libbz2-1.0 1.0.6-9.2
ii  libc6  2.28-10
ii  liblzma5   5.2.4-1
ii  libopenmpi33.1.3-11
ii  libscotch-6.0  6.0.7-2
ii  zlib1g 1:1.2.11.dfsg-1+b1

scotch recommends no packages.

scotch suggests no packages.

-- no debconf information

Bug#925823: scotch: ftbfs with GCC-9

[Drew Parsons]

Package: scotch
Version: 6.0.7-2
Followup-For: Bug #925823

gdb backtrace suggests the error occurs in l.229 order_io.c:

Program received signal SIGSEGV, Segmentation fault.
0x77f9c2f9 in _SCOTCHorderSaveMap (ordeptr=,
vlbltab=, stream=0x9260) at order_io.c:229
229order_io.c: No such file or directory.
(gdb) bt
#0  0x77f9c2f9 in _SCOTCHorderSaveMap (ordeptr=, vlbltab=, stream=0x9260) at order_io.c:229
#1  0x53e5 in main (argc=, argv=) at test_scotch_graph_order.c:143


order_io.c:229 says...
   if (fprintf (stream, GNUMSTRING "\t" GNUMSTRING "\n",   
from ...
  vlbltax = (vlbltab != NULL) ? (vlbltab - ordeptr->baseval) : NULL;
  for (vnodnum = ordeptr->baseval, o = 0; vnodnum < vnodnnd; vnodnum ++) {
if (fprintf (stream, GNUMSTRING "\t" GNUMSTRING "\n",
 (Gnum) ((vlbltax != NULL) ? vlbltax[vnodnum] : vnodnum),
 (Gnum) cblktax[vnodnum]) == EOF) {
  errorPrint ("orderSaveMap: bad output (2)");
  o = 1;
  break;
}
  }

stream is not zero...
(gdb) p stream
$1 = (FILE * const) 0x9260

vlbltax is zero...
(gdb) p vlbltax
$5 = (const Gnum * restrict) 0x0

but that is supposed to be guarded in the call with vlbltax != NULL.

Does it mean the use of the "vlbltax != NULL" pattern is now broken in
gcc9 ?


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

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

Versions of packages scotch depends on:
ii  libbz2-1.0 1.0.6-9.2
ii  libc6  2.28-10
ii  liblzma5   5.2.4-1
ii  libopenmpi33.1.3-11
ii  libscotch-6.0  6.0.7-2
ii  zlib1g 1:1.2.11.dfsg-1+b1

scotch recommends no packages.

scotch suggests no packages.

-- no debconf information

Bug#925812: marked as done (qtbase-opensource-src: ftbfs with GCC-9)

[Debian Bug Tracking System]

Your message dated Thu, 15 Aug 2019 14:43:46 +
with message-id 
and subject line Bug#925812: fixed in qtbase-opensource-src 5.11.3+dfsg1-4
has caused the Debian Bug report #925812,
regarding qtbase-opensource-src: ftbfs with GCC-9
to be marked as done.

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

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


-- 
925812: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=925812
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:qtbase-opensource-src
Version: 5.11.3+dfsg1-1
Severity: normal
Tags: sid bullseye
User: debian-...@lists.debian.org
Usertags: ftbfs-gcc-9

Please keep this issue open in the bug tracker for the package it
was filed for.  If a fix in another package is required, please
file a bug for the other package (or clone), and add a block in this
package. Please keep the issue open until the package can be built in
a follow-up test rebuild.

The package fails to build in a test rebuild on at least amd64 with
gcc-9/g++-9, but succeeds to build with gcc-8/g++-8. The
severity of this report will be raised before the bullseye release,
so nothing has to be done for the buster release.

The full build log can be found at:
http://people.debian.org/~doko/logs/gcc9-20190321/qtbase-opensource-src_5.11.3+dfsg1-1_unstable_gcc9.log
The last lines of the build log are at the end of this report.

To build with GCC 9, either set CC=gcc-9 CXX=g++-9 explicitly,
or install the gcc, g++, gfortran, ... packages from experimental.

  apt-get -t=experimental install g++ 

Common build failures are new warnings resulting in build failures with
-Werror turned on, or new/dropped symbols in Debian symbols files.
For other C/C++ related build failures see the porting guide at
http://gcc.gnu.org/gcc-9/porting_to.html

GCC 9 also passes the linker option --as-needed by default; typical
build issues are passing libraries before object files to the linker,
or underlinking of convenience libraries built from the same source.

[...]
g++ -c -o main.o -g -O2 
-fdebug-prefix-map=/<>/qtbase-opensource-src-5.11.3+dfsg1=. 
-fstack-protector-strong -Wformat -Werror=format-security -Wdate-time 
-D_FORTIFY_SOURCE=2  -std=c++11 -ffunction-sections -O2 -g  
-I/<>/qtbase-opensource-src-5.11.3+dfsg1/qmake 
-I/<>/qtbase-opensource-src-5.11.3+dfsg1/qmake/library 
-I/<>/qtbase-opensource-src-5.11.3+dfsg1/qmake/generators 
-I/<>/qtbase-opensource-src-5.11.3+dfsg1/qmake/generators/unix 
-I/<>/qtbase-opensource-src-5.11.3+dfsg1/qmake/generators/win32 
-I/<>/qtbase-opensource-src-5.11.3+dfsg1/qmake/generators/mac 
-I/<>/qtbase-opensource-src-5.11.3+dfsg1/include 
-I/<>/qtbase-opensource-src-5.11.3+dfsg1/include/QtCore 
-I/<>/qtbase-opensource-src-5.11.3+dfsg1/include/QtCore/5.11.3 
-I/<>/qtbase-opensource-src-5.11.3+dfsg1/include/QtCore/5.11.3/QtCore 
-I../src/corelib/global 
-I/<>/qtbase-opensource-src-5.11.3+dfsg1/mkspecs/linu
 x-g++ -DQT_VERSION_STR=\"5.11.3\" -DQT_VERSION_MAJOR=5 -DQT_VERSION_MINOR=11 
-DQT_VERSION_PATCH=3 -DQT_BUILD_QMAKE -DQT_BOOTSTRAPPED -DPROEVALUATOR_FULL 
-DQT_NO_FOREACH /<>/qtbase-opensource-src-5.11.3+dfsg1/qmake/main.cpp
g++ -c -o meta.o -g -O2 
-fdebug-prefix-map=/<>/qtbase-opensource-src-5.11.3+dfsg1=. 
-fstack-protector-strong -Wformat -Werror=format-security -Wdate-time 
-D_FORTIFY_SOURCE=2  -std=c++11 -ffunction-sections -O2 -g  
-I/<>/qtbase-opensource-src-5.11.3+dfsg1/qmake 
-I/<>/qtbase-opensource-src-5.11.3+dfsg1/qmake/library 
-I/<>/qtbase-opensource-src-5.11.3+dfsg1/qmake/generators 
-I/<>/qtbase-opensource-src-5.11.3+dfsg1/qmake/generators/unix 
-I/<>/qtbase-opensource-src-5.11.3+dfsg1/qmake/generators/win32 
-I/<>/qtbase-opensource-src-5.11.3+dfsg1/qmake/generators/mac 
-I/<>/qtbase-opensource-src-5.11.3+dfsg1/include 
-I/<>/qtbase-opensource-src-5.11.3+dfsg1/include/QtCore 
-I/<>/qtbase-opensource-src-5.11.3+dfsg1/include/QtCore/5.11.3 
-I/<>/qtbase-opensource-src-5.11.3+dfsg1/include/QtCore/5.11.3/QtCore 
-I../src/corelib/global 
-I/<>/qtbase-opensource-src-5.11.3+dfsg1/mkspecs/linu
 x-g++ -DQT_VERSION_STR=\"5.11.3\" -DQT_VERSION_MAJOR=5 -DQT_VERSION_MINOR=11 
-DQT_VERSION_PATCH=3 -DQT_BUILD_QMAKE -DQT_BOOTSTRAPPED -DPROEVALUATOR_FULL 
-DQT_NO_FOREACH /<>/qtbase-opensource-src-5.11.3+dfsg1/qmake/meta.cpp
g++ -c -o option.o -g -O2 
-fdebug-prefix-map=/<>/qtbase-opensource-src-5.11.3+dfsg1=. 
-fstack-protector-strong -Wformat -Werror=format-security -Wdate-time 
-D_FORTIFY_SOURCE=2  -std=c++11 -ffunction-sections -O2 -g  
-I/<>/qtbase-opensource-src-5.11.3+dfsg1/qmake 
-I/<>/qtbase-opensource-src-5.11.3+dfsg1/qmake/library 
-I/<>/qtbase-opensource-src-5.11.3+dfsg1/qmake/generators 

Bug#933020: marked as done (libvirt ftbfs in unstable (configure fails))

[Debian Bug Tracking System]

Your message dated Thu, 15 Aug 2019 14:40:10 +
with message-id 
and subject line Bug#933020: fixed in libvirt 5.0.0-4.1
has caused the Debian Bug report #933020,
regarding libvirt ftbfs in unstable (configure fails)
to be marked as done.

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

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


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

seen on all architectures.

[...]
checking rbd/librbd.h usability... yes
checking rbd/librbd.h presence... yes
checking for rbd/librbd.h... yes
checking for rbd_get_features... yes
configure: error: Need glusterfs (libgfapi) for gluster storage driver
--- End Message ---
--- Begin Message ---
Source: libvirt
Source-Version: 5.0.0-4.1

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

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

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

Debian distribution maintenance software
pp.
Jonathan Wiltshire  (supplier of updated libvirt package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Sat, 10 Aug 2019 13:31:18 +0100
Source: libvirt
Architecture: source
Version: 5.0.0-4.1
Distribution: unstable
Urgency: medium
Maintainer: Debian Libvirt Maintainers 

Changed-By: Jonathan Wiltshire 
Closes: 933020
Changes:
 libvirt (5.0.0-4.1) unstable; urgency=medium
 .
   * Non-maintainer upload.
   * Build-depend on libglusterfs-dev for required libgfapi headers
 (Closes: #933020)
Checksums-Sha1:
 c8576fa138f45b6f12276624411eb1115556150b 4379 libvirt_5.0.0-4.1.dsc
 bc0587d84ae7260a4cd357d4a667d42c0750b083 78592 libvirt_5.0.0-4.1.debian.tar.xz
 9329035777870c993c6c2b33f026701c2b02ebe1 13361 
libvirt_5.0.0-4.1_source.buildinfo
Checksums-Sha256:
 7b4f32853adf0626e69a0fd7051fffe761bcac724ee14ddd42ecccdb392ca154 4379 
libvirt_5.0.0-4.1.dsc
 3b29ed861828d025e1bf2f95eda2cd7ecbc338f7b3beb0e08db4f74c67de03dc 78592 
libvirt_5.0.0-4.1.debian.tar.xz
 efc2ea4438cf3254e70173cdb0916acb8fb087f790dc571874dd2baa4328a872 13361 
libvirt_5.0.0-4.1_source.buildinfo
Files:
 11cc8f94e68e429e65af4d00d2047925 4379 libs optional libvirt_5.0.0-4.1.dsc
 7a3a330e2b065590f2158a83c865907f 78592 libs optional 
libvirt_5.0.0-4.1.debian.tar.xz
 8fa001649d492e0756edc76bfb15afaf 13361 libs optional 
libvirt_5.0.0-4.1_source.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEADLdyLGMneGYn8dtRNMqtfom+MkFAl1OxeUACgkQRNMqtfom
+Mnt0Q//VCxXxqzNyNpTZCkwySndRcRwu9ug5SR5GdkTAS2xosiADuf4ZIIRd9cg
3bTmkWq4wpQc+ENy21I0Yjz0PrW83UtYT9o7n0yGsuqigq9C4NaRf4RtCKACcKOb
jkNN2fg/UIZ2BK3wUQ3/1uwTqw8KIvUfKsvf1RuVLbEGfUqil7kczAIaNHNuqrIn
gBiW5lJkV9B4Dv853EknM5pyZixwTpc+aoLPyhPT5kKBEG3txxCyCiZSB1AJ0TqW
7E6skMsZa0C/QfmOKHkTAlDTIJLz5bPCPfzGv1YLvhxYudUH89/twEKwxxbLbXr8
dMzQ8W+sVEGCBdqje1FPsxyjnqJJ6x1kvjIiaqBhx2tCeg/GgBS92RXch4XNmYxv
5AfRyjVIYsJcfPltXQsGuvYXIz7XyLL4qt95/Yab9aFE/yN5e8qVVPM8gCgeFu19
66r8w32DkFZHoGIRpgw8VmrQcg2ss1nQan+HqPmIRrAbB0UnLONYfm9OVR2JU8N0
x68niQsEns9fMj6VOEFubr6tfI0Fg3rcjLY0BgoLrDjIGsMTuVX73mYJkzYhP9yu
R5+9xU3NLH4uou5qEU3cshalJUYpta1pF90VlK8v37d7XJBpMlFy3drErx5S4e+I
Y6XNHqTfANUn6+m+AnUEfQnzoZwYe10pgIcEdtuyoFjqE51wKW0=
=lu0n
-END PGP SIGNATURE End Message ---

Bug#934821: marked as done (fcm: usr/bin/fcm_test_battery uses invalid interpreter (/usr/bin/bash instead of /bin/bash))

[Debian Bug Tracking System]

Your message dated Thu, 15 Aug 2019 14:38:40 +
with message-id 
and subject line Bug#934821: fixed in fcm 2019.05.0-2
has caused the Debian Bug report #934821,
regarding fcm: usr/bin/fcm_test_battery uses invalid interpreter (/usr/bin/bash 
instead of /bin/bash)
to be marked as done.

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

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


-- 
934821: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=934821
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: fcm
Version: 2019.05.0-1
Severity: serious

Hi,

Found by lintian and confirmed manually; the fcm_test_battery script
installed into the default PATH uses /usr/bin/bash as interpreter.
This only works on /usr-merged systems.  However, Debian systems
cannot be assumed to have been /usr-merged.

"""
#!/usr/bin/bash
#---
# Copyright (C) 2006-2019 British Crown (Met Office) & Contributors.
#
"""

Thanks,
~Niels
--- End Message ---
--- Begin Message ---
Source: fcm
Source-Version: 2019.05.0-2

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

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

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

Debian distribution maintenance software
pp.
Alastair McKinstry  (supplier of updated fcm package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Thu, 15 Aug 2019 14:54:38 +0100
Source: fcm
Architecture: source
Version: 2019.05.0-2
Distribution: unstable
Urgency: medium
Maintainer: Alastair McKinstry 
Changed-By: Alastair McKinstry 
Closes: 934821
Changes:
 fcm (2019.05.0-2) unstable; urgency=medium
 .
   * Move to using debhelper-compat (= 12)
   * Standards-Version: 4.4.0
   * Change path for fcm_test_battery to /bin/bash. Closes: #934821
Checksums-Sha1:
 2ae32d5a06998e114631a83d9b4b9cb58c318bc2 1977 fcm_2019.05.0-2.dsc
 c81ee0d81cd90806242518ff1cb82276dcb8011f 25964 fcm_2019.05.0-2.debian.tar.xz
Checksums-Sha256:
 e47ebe9be0cb7795679fa922645afac982aa77f0a628885f0a4884ebb8e2037d 1977 
fcm_2019.05.0-2.dsc
 6878fbd3a9d2e0114004bc3f333a41b9fa5577573aa7c800b5d5179a2be61e0f 25964 
fcm_2019.05.0-2.debian.tar.xz
Files:
 b612a3d7212baa6c0b9cc2a337913b0b 1977 utils optional fcm_2019.05.0-2.dsc
 c1077ba7ec0abe96ebde8e45da32a640 25964 utils optional 
fcm_2019.05.0-2.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEEgjg86RZbNHx4cIGiy+a7Tl2a06UFAl1VZq0ACgkQy+a7Tl2a
06XXfA//W/vl0gEwkYAMZEEP4Di6GYsGjVASAsS4YUaclI5GDFUHmj9u3LVjWuEb
JI5g/EXWylbj0vYlbRb3gfvwEvWTToABryiTGurwKnTYpxhq65uwlG/88tora3R2
BoTmnC3/NAdNt0GTKnHW6+BENt3jK6rcnlmZOpyGuqfP7f5C/+h6QqnzZqM5gIyD
/OKvxzsfUi/k4Mx175h5f23gLNuNAZ9FpjwtFGnBzLM5N3NxlgUA1+jq5yx8wCIK
q4HxQaImUy6Yd5mktKDbJN4r+3afnf6R7MsR6sytZ6kIpwO9HP1BQHuZqS4wkHwx
fkkcw2P+Fy5t/0PFPP5sP6GEnDS7W92Zv42RHOuNg22D1++EvKEYpVBFWbzrba8X
cTfmRtfLpamhJbcW8CRO3Ua2wRtPaYetXb6pB/bwYymVXjIHZTiTLIMOEwa/tNp2
832v+4md8XlPd1t81pr6e6uUvS5sA+Unw3oFelR7EP89adJdaWtXl2bfgQefeM11
EQfHXCkCacvNhtqxPQiU4GthlWCcggNaRiNHgVs/Pam6+tsbImN9nuH3zcpwcaVr
0N3zqW6Qb7USVu3ahWoh6lIo4A1xsDOj68UhtHUQYFPbm8qu9WLB/a2o3T5btR2Y
RadKI2ZBVTc2kzYTb8oCKh07aKi/cDURKaiAWyu6G78XtMkIsrU=
=r7O/
-END PGP SIGNATURE End Message ---

Bug#851774: fixed in apt-setup 1:0.151

[Cyril Brulebois]

Hi,

Moritz Muehlenhoff  (2019-07-17):
> On Fri, Jul 12, 2019 at 09:07:45AM +, Cyril Brulebois wrote:
> >  apt-setup (1:0.151) unstable; urgency=medium
> >  .
> >[ Moritz Mühlenhoff ]
> >* When preseeding a local repository via apt-setup/localX/repository,
> >  the repository key for Secure Apt needs to be configured with
> >  apt-setup/localX/key. This key used to be set up with apt-key, but
> >  its use is deprecated and apt's former dependency on gnupg has been
> >  demoted to a Suggests, rendering apt-key non-functional in d-i.
> >  Apply a patch by Lars Kollstedt (thanks!) which adds the repository
> >  key(s) to /etc/apt/trusted.gpg.d, following the approach used by
> >  pbuilder (Closes: #851774, #928931):
> >   - .asc suffix if the key file seems to be armoured ASCII (i.e. it
> > contains a “-BEGIN PGP PUBLIC KEY BLOCK-” line);
> >   - .gpg suffix otherwise. Please note that only “GPG key public ring”
> > are supported by APT, newer “keybox database” format isn't at the
> > moment.
> 
> Hi Cyril,
> as discussed on #debian-boot last week: I've tested a Buster installation with
> "d-i mirror/udeb/suite   string  unstable" and our previous
> "d-i base-installer/includes string  gnupg" workaround dropped which uses
> the https://apt.wikimedia.org repository and that worked fine.

Many thanks, I'll be submitting a buster-pu bug accordingly. I wouldn't
mind an extra confirmation after it's been published in a point release
(peace of mind and all that).

> I've also submitted a patch to installation-guide to enhance the docs
> so that the constraints for the Secure Apt key file are explicitly
> mentioned (#932284)

Much appreciated, thanks.


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


signature.asc
Description: PGP signature

Bug#925812: marked as pending in qtbase-opensource-src

[Dmitry Shachnev]

Control: tag -1 pending

Hello,

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

https://salsa.debian.org/qt-kde-team/qt/qtbase/commit/ee904ad1bba5cb2c92023e1d83a31d1af4e90481


Backport upstream patch to fix build with GCC 9.

Refresh debian/patches/no_arc4random_buf.diff because it is patching
the same file.

Closes: #925812.


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/925812

Processed: Bug#925812 marked as pending in qtbase-opensource-src

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #925812 [src:qtbase-opensource-src] qtbase-opensource-src: ftbfs with GCC-9
Added tag(s) pending.

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

Processed: retitle 933799 to geary (and other mason based projects) ftbs in clean chroot with ccache installed

[Debian Bug Tracking System]

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

> retitle 933799 geary (and other mason based projects) ftbs in clean chroot 
> with ccache installed
Bug #933799 [geary] geary FTBFS - ERROR: Problem encountered: SQLite3 is 
missing FTS3 tokenizer support
Changed Bug title to 'geary (and other mason based projects) ftbs in clean 
chroot with ccache installed' from 'geary FTBFS - ERROR: Problem encountered: 
SQLite3 is missing FTS3 tokenizer support'.
> thanks
Stopping processing here.

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

Bug#925837: systemc: ftbfs with GCC-9

[أحمد المحمودي]

On Wed, Mar 27, 2019 at 07:48:14PM +, Matthias Klose wrote:
> The package fails to build in a test rebuild on at least amd64 with
> gcc-9/g++-9, but succeeds to build with gcc-8/g++-8. The
> http://gcc.gnu.org/gcc-9/porting_to.html
> 
> [...]
> - 
> _ZN5sc_dt13b_xor_assign_INS_10sc_bv_baseENS_10sc_lv_baseEEERT_RNS_8sc_proxyIS3_EERKNS5_IT0_EE@Base
>  2.3.3
> +#MISSING: 2.3.3-2# 
> _ZN5sc_dt13b_xor_assign_INS_10sc_bv_baseENS_10sc_lv_baseEEERT_RNS_8sc_proxyIS3_EERKNS5_IT0_EE@Base
>  2.3.3
> [...]
---end quoted text---

The wierd symbol mangling in C++ ks causing this proble, with rvery 
gcc/g++ update, I tried using c++filt symbols (using c++ tag), but it 
was of no use.
Hence, I think the best solution is to remove the symbols file for this 
package.

-- 
‎أحمد المحمودي (Ahmed El-Mahmoudy)
 Digital design engineer
GPG KeyIDs: 4096R/A7EF5671 2048R/EDDDA1B7
GPG Fingerprints:
 6E2E E4BB 72E2 F417 D066  6ABF 7B30 B496 A7EF 5761
 8206 A196 2084 7E6D 0DF8  B176 BC19 6A94 EDDD A1B7


signature.asc
Description: PGP signature

Bug#934740: marked as done (nftables: broken on BE)

[Debian Bug Tracking System]

Your message dated Thu, 15 Aug 2019 13:19:22 +
with message-id 
and subject line Bug#934740: fixed in nftables 0.9.1-3
has caused the Debian Bug report #934740,
regarding nftables: broken on BE
to be marked as done.

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

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


-- 
934740: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=934740
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: nftables
Version: 0.9.1-2
Severity: serious
Tags patch

Hello, after trying to understand why firewalld was completely broken on s390x, 
and discussing with nftables upstream, they found that a particular commit: 
142350f154c7
broke Big Endian machines.

this is the set of patches:
https://marc.info/?l=netfilter-devel=156572714605196=2


Also, please add docbook-xsl build dependency, on some systems, it might be not 
installed and then the build fail because of missing schema

e.g.

make[3]: Entering directory '/<>/doc'
a2x -L --doctype manpage --format manpage -D . nft.txt
a2x -L --doctype manpage --format manpage -D . libnftables-json.adoc
a2x -L --doctype manpage --format manpage -D . libnftables.adoc
a2x: ERROR: "xsltproc"  --stringparam callout.graphics 0 --stringparam 
navig.graphics 0 --stringparam admon.textlabel 1 --stringparam admon.graphics 0 
 "/etc/asciidoc/docbook-xsl/manpage.xsl" "/<>/doc/libnftables.xml" 
returned non-zero exit status 5
make[3]: *** [Makefile:648: libnftables.3] Error 1
make[3]: *** Waiting for unfinished jobs
a2x: ERROR: "xsltproc"  --stringparam callout.graphics 0 --stringparam 
navig.graphics 0 --stringparam admon.textlabel 1 --stringparam admon.graphics 0 
 "/etc/asciidoc/docbook-xsl/manpage.xsl" 
"/<>/doc/libnftables-json.xml" returned non-zero exit status 5
make[3]: *** [Makefile:651: libnftables-json.5] Error 1
a2x: ERROR: "xsltproc"  --stringparam callout.graphics 0 --stringparam 
navig.graphics 0 --stringparam admon.textlabel 1 --stringparam admon.graphics 0 
 "/etc/asciidoc/docbook-xsl/manpage.xsl" "/<>/doc/nft.xml" 
returned non-zero exit status 5
make[3]: *** [Makefile:645: nft.8] Error 1
make[3]: Leaving directory '/<>/doc'
make[2]: *** [Makefile:484: all-recursive] Error 1
make[2]: Leaving directory '/<>'
make[1]: *** [Makefile:393: all] Error 2
make[1]: Leaving directory '/<>'
dh_auto_build: make -j4 returned exit code 2
make: *** [debian/rules:15: build] Error 2
dpkg-buildpackage: error: debian/rules build subprocess returned exit status 2



You can grab patches from my Ubuntu upload
https://launchpad.net/ubuntu/+source/nftables/0.9.1-2ubuntu3

including the missing schema fix.

thanks
(I'm still testing them, but I prefer to open the RC bug in advance, I'll 
update in case something else is needed)

Gianfranco
--- End Message ---
--- Begin Message ---
Source: nftables
Source-Version: 0.9.1-3

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

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

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

Debian distribution maintenance software
pp.
Arturo Borrero Gonzalez  (supplier of updated nftables 
package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Thu, 15 Aug 2019 15:01:49 +0200
Source: nftables
Architecture: source
Version: 0.9.1-3
Distribution: unstable
Urgency: medium
Maintainer: Debian Netfilter Packaging Team 

Changed-By: Arturo Borrero Gonzalez 
Closes: 934740
Changes:
 nftables (0.9.1-3) unstable; urgency=medium
 .
   * [609ee76] d/README.Debian: refresh file
   * [3255aaa] src:nftables: run wrap-and-sort
   * [5337001] nftables: raise package priority to important
   * [09b720f] src:nftables: add docbook-xsl build-dep
   * [9db946c] src:nftables: bump debhelper compat to 12
   * [4f0bb1d] nftables.maintscript: introduce file
   * [1b54808] d/patches: add BE fixtures (Closes: #934740)
Checksums-Sha1:
 b95f614eab9ecdf9dbb74bd6d1776bc3cecbbd27 2706 nftables_0.9.1-3.dsc
 a2f35fe884368d784d9f7f09b174a59f64dbc3a4 22708 nftables_0.9.1-3.debian.tar.xz
 2eb296d247b60a3f124fd246e4eafa4bc7702c7b 8118 nftables_0.9.1-3_amd64.buildinfo
Checksums-Sha256:
 

Bug#933509: marked as done (oz depends on cruft package.)

[Debian Bug Tracking System]

Your message dated Thu, 15 Aug 2019 12:49:54 +
with message-id 
and subject line Bug#933509: fixed in oz 0.17.0-1
has caused the Debian Bug report #933509,
regarding oz depends on cruft package.
to be marked as done.

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

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


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

Package: oz
Version: 0.16.0-2
Severity: serious
Tags: bullseye, sid

oz depends on the python-monotonic binary package which is no longer 
built by the python-monotonic source package.
--- End Message ---
--- Begin Message ---
Source: oz
Source-Version: 0.17.0-1

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

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

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

Debian distribution maintenance software
pp.
Simon Josefsson  (supplier of updated oz package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Thu, 15 Aug 2019 13:56:40 +0200
Source: oz
Architecture: source
Version: 0.17.0-1
Distribution: unstable
Urgency: low
Maintainer: Simon Josefsson 
Changed-By: Simon Josefsson 
Closes: 933509
Changes:
 oz (0.17.0-1) unstable; urgency=low
 .
   * New upstream version.
   * Standards-Version 4.4.0.
   * Compat 12.
   * Use dh-python and pybuild.
   * Use python 3.  Closes: #933509.
Checksums-Sha1:
 0b8721092ee2f0dbf7db408695dbc54f08c4a10c 1466 oz_0.17.0-1.dsc
 52ba9477d057cea93e222351f2a49958ae3bcb64 147539 oz_0.17.0.orig.tar.gz
 9ab1b948f7207a9ecdd8daef2943f0fb7f66d112 3048 oz_0.17.0-1.debian.tar.xz
 c06f033ea40b1953b9bb7467f8595170e3180e55 5518 oz_0.17.0-1_amd64.buildinfo
Checksums-Sha256:
 c12feb8a19af63cc7cfa9cecfbadc02de36e67b1e20ad9b40bb34047b0e219a2 1466 
oz_0.17.0-1.dsc
 948f95d6dcfdaea12bcbe6f76b1d43b4c17ea01a02cb4f9a754cc38743fd4dcb 147539 
oz_0.17.0.orig.tar.gz
 aa718375f2500631cf37eaed40253e5a292dead0faebd3487b76003c327dea38 3048 
oz_0.17.0-1.debian.tar.xz
 8d40c577ea20e28a11bc122026a774ad749b354a3e32c15a736e0082be8db00a 5518 
oz_0.17.0-1_amd64.buildinfo
Files:
 e3a1ffd0364d6503cf36f50573c89be0 1466 python optional oz_0.17.0-1.dsc
 16e5c533543d24ca3e1eb382c16a976b 147539 python optional oz_0.17.0.orig.tar.gz
 9676bc7a944818179cea81e017964744 3048 python optional oz_0.17.0-1.debian.tar.xz
 b6b4e9b86d87f65900b81c00bf0c8faf 5518 python optional 
oz_0.17.0-1_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQFIBAEBCgAyFiEEmUFc4ZBdDlWp+IAmhgt/uzL4EZ0FAl1VUaYUHHNpbW9uQGpv
c2Vmc3Nvbi5vcmcACgkQhgt/uzL4EZ1PbQf/bxvq4Dh9TxuS8GwPYqPLqb1kWLKB
e3xJC9RW7VQkmSsSTqx/bJxwER5QrQoVENpaXxmnNabPdt196+oFJxaI0xE2Zdnp
dKJfZj7o+NDRMitwhx2z6RF3VLB/Q4PKE7sZMeVAherFvJGefMJWjcmIz4/ByLw+
zZQRnRZUthaNuBB6yogdMCh95yQTKhrbAKQvIJ+70vmOY2J3UNW0My43UXHKbdqj
dlYG5daGDvhKTvAwfi2ZcGEqENOypzh8N0nZ2KYD0BzsPZ36/x6My45LmxTNepaS
TuC1tDLEQv3ecVLv/Teb3CMcHxoV0BQ7KF9jUHYDB9eUBqZVoE+qghc34A==
=9pDZ
-END PGP SIGNATURE End Message ---

Bug#934821: fcm: usr/bin/fcm_test_battery uses invalid interpreter (/usr/bin/bash instead of /bin/bash)

[Niels Thykier]

Package: fcm
Version: 2019.05.0-1
Severity: serious

Hi,

Found by lintian and confirmed manually; the fcm_test_battery script
installed into the default PATH uses /usr/bin/bash as interpreter.
This only works on /usr-merged systems.  However, Debian systems
cannot be assumed to have been /usr-merged.

"""
#!/usr/bin/bash
#---
# Copyright (C) 2006-2019 British Crown (Met Office) & Contributors.
#
"""

Thanks,
~Niels

Processed: raise severity of GCC 9 ftbfs issues (GCC 9 is now the default)

[Debian Bug Tracking System]

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

> severity 925626 serious
Bug #925626 [src:acpi-support] acpi-support: ftbfs with GCC-9
Severity set to 'serious' from 'important'
> severity 925682 serious
Bug #925682 [src:flang] flang: ftbfs with GCC-9
Severity set to 'serious' from 'important'
> severity 925722 serious
Bug #925722 [src:jq] jq: ftbfs with GCC-9
Severity set to 'serious' from 'important'
> severity 925728 serious
Bug #925728 [src:lagan] lagan: ftbfs with GCC-9
Severity set to 'serious' from 'important'
> severity 925746 serious
Bug #925746 [src:libidn] libidn: ftbfs with GCC-9
Severity set to 'serious' from 'important'
> severity 925842 serious
Bug #925842 [src:tstools] tstools: ftbfs with GCC-9
Severity set to 'serious' from 'important'
> severity 925846 serious
Bug #925846 [src:usbrelay] usbrelay: ftbfs with GCC-9
Severity set to 'serious' from 'important'
> severity 925848 serious
Bug #925848 [src:vacation] vacation: ftbfs with GCC-9
Severity set to 'serious' from 'important'
> severity 925859 serious
Bug #925859 [src:wmwave] wmwave: ftbfs with GCC-9
Severity set to 'serious' from 'important'
> severity 925863 serious
Bug #925863 [src:xcalib] xcalib: ftbfs with GCC-9
Severity set to 'serious' from 'important'
> severity 925624 serious
Bug #925624 [src:abinit] abinit: ftbfs with GCC-9
Severity set to 'serious' from 'important'
> severity 925625 serious
Bug #925625 [src:abr2gbr] abr2gbr: ftbfs with GCC-9
Severity set to 'serious' from 'important'
> severity 925627 serious
Bug #925627 [src:adplug] adplug: ftbfs with GCC-9
Severity set to 'serious' from 'important'
> severity 925628 serious
Bug #925628 [src:afnix] afnix: ftbfs with GCC-9
Severity set to 'serious' from 'important'
> severity 925629 serious
Bug #925629 [src:aghermann] aghermann: ftbfs with GCC-9
Severity set to 'serious' from 'important'
> severity 925630 serious
Bug #925630 [src:aide] aide: ftbfs with GCC-9
Severity set to 'serious' from 'important'
> severity 925633 serious
Bug #925633 [src:aplus-fsf] aplus-fsf: ftbfs with GCC-9
Severity set to 'serious' from 'important'
> severity 925634 serious
Bug #925634 [src:apophenia] apophenia: ftbfs with GCC-9
Severity set to 'serious' from 'important'
> severity 925637 serious
Bug #925637 [src:bcal] bcal: ftbfs with GCC-9
Severity set to 'serious' from 'important'
> severity 925638 serious
Bug #925638 [src:belle-sip] belle-sip: ftbfs with GCC-9
Severity set to 'serious' from 'important'
> severity 925639 serious
Bug #925639 [src:bind-dyndb-ldap] bind-dyndb-ldap: ftbfs with GCC-9
Severity set to 'serious' from 'important'
> severity 925643 serious
Bug #925643 [src:biosig4c++] biosig4c++: ftbfs with GCC-9
Severity set to 'serious' from 'important'
> severity 925644 serious
Bug #925644 [src:bladerf] bladerf: ftbfs with GCC-9
Severity set to 'serious' from 'important'
> severity 925645 serious
Bug #925645 [src:blender] blender: ftbfs with GCC-9
Severity set to 'serious' from 'important'
> severity 925646 serious
Bug #925646 [src:bombardier] bombardier: ftbfs with GCC-9
Severity set to 'serious' from 'important'
> severity 925647 serious
Bug #925647 [src:casync] casync: ftbfs with GCC-9
Severity set to 'serious' from 'important'
> severity 925649 serious
Bug #925649 [src:cdo] cdo: ftbfs with GCC-9
Severity set to 'serious' from 'important'
> severity 925650 serious
Bug #925650 [src:chasen] chasen: ftbfs with GCC-9
Severity set to 'serious' from 'important'
> severity 925652 serious
Bug #925652 [src:chktex] chktex: ftbfs with GCC-9
Severity set to 'serious' from 'important'
> severity 925653 serious
Bug #925653 [src:clamfs] clamfs: ftbfs with GCC-9
Severity set to 'serious' from 'important'
> severity 925654 serious
Bug #925654 [src:code-saturne] code-saturne: ftbfs with GCC-9
Severity set to 'serious' from 'important'
> severity 925655 serious
Bug #925655 [src:colmap] colmap: ftbfs with GCC-9
Severity set to 'serious' from 'important'
> severity 925656 serious
Bug #925656 [src:colobot] colobot: ftbfs with GCC-9
Severity set to 'serious' from 'important'
> severity 925657 serious
Bug #925657 [src:condor] condor: ftbfs with GCC-9
Severity set to 'serious' from 'important'
> severity 925658 serious
Bug #925658 [src:courier-unicode] courier-unicode: ftbfs with GCC-9
Severity set to 'serious' from 'important'
> severity 925659 serious
Bug #925659 [src:cpl-plugin-muse] cpl-plugin-muse: ftbfs with GCC-9
Severity set to 'serious' from 'important'
> severity 925662 serious
Bug #925662 [src:criu] criu: ftbfs with GCC-9
Severity set to 'serious' from 'important'
> severity 925663 serious
Bug #925663 [src:cups-bjnp] cups-bjnp: ftbfs with GCC-9
Severity set to 'serious' from 'important'
> severity 925665 serious
Bug #925665 [src:cycfx2prog] cycfx2prog: ftbfs with GCC-9
Severity set to 'serious' from 'important'
> severity 925666 serious
Bug #925666 [src:ddd] ddd: ftbfs with GCC-9
Severity set to 'serious' from 'important'
> severity 925667 serious
Bug #925667 [src:dde-qt-dbus-factory] 

Bug#933002: docker.io: CVE-2019-13139

[Arnaud Rebillout]

On 8/13/19 12:35 PM, Salvatore Bonaccorso wrote:

On Tue, Aug 13, 2019 at 11:31:41AM +0200, Arnaud Rebillout wrote:

This is fixed in unstable.

Thanks!



Oh well, not fixed in unstable yet actually, as the package doesn't 
build anymore due to changes in the dependency tree...




This one is marked as no-dsa. But if something is not yet marked it
can as well mean we simply have not assessed it for buster or stretch.
Feel free to CC the security team alias when unsure.

For getting packages via a point release there are some steps outlined
here:
https://www.debian.org/doc/manuals/developers-reference/ch05.en.html#upload-stable

When involving security some guidelines are given at
https://www.debian.org/doc/manuals/developers-reference/ch05.en.html#s5.6.4
and
https://www.debian.org/doc/manuals/developers-reference/ch05.en.html#bug-security



Thanks for all the references!


  Arnaud

Bug#933684: marked as done (python-httptools: Please adjust for http-parser 2.9)

[Debian Bug Tracking System]

Your message dated Thu, 15 Aug 2019 09:04:51 +
with message-id 
and subject line Bug#933684: fixed in python-httptools 0.0.11-1.1
has caused the Debian Bug report #933684,
regarding python-httptools: Please adjust for http-parser 2.9
to be marked as done.

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

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


-- 
933684: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=933684
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: python-httptools
Version: 0.0.11-1
Severity: important
Tags: patch

Dear Maintainer,

the http-parser library version 2.9 was accepted to experimental today,
and re-building all rdeps I noticed your package will fail to build in
the future due to a failure in the test suite.

This has already been fixed upstream. Please upgrade to at least 0.0.13,
or cherry-pick commit ebcc0fd, feel free to borrow from the patch
attached.

Regards,

Christoph
From d63280b950bfe0a875c45b4d73f4d18e8c91761f Mon Sep 17 00:00:00 2001
From: Christoph Biedl 
Date: Thu, 1 Aug 2019 21:46:24 +0200
Subject: [PATCH 1/2] Cherry-pick "Fix a unittest" to fix build error with
 http-parser 2.9

---
 debian/control|  2 +-
 ...-unittest-bump-the-version-to-0-0-13.patch | 19 +++
 debian/patches/series |  1 +
 3 files changed, 21 insertions(+), 1 deletion(-)
 create mode 100644 debian/patches/cherry-pick.v0.0.11-6-gebcc0fd.fix-a-unittest-bump-the-version-to-0-0-13.patch

diff --git a/debian/control b/debian/control
index 4928709..0dcad52 100644
--- a/debian/control
+++ b/debian/control
@@ -8,7 +8,7 @@ Build-Depends:
  cython3,
  debhelper (>= 11),
  dh-python,
- libhttp-parser-dev,
+ libhttp-parser-dev (>= 2.9.2),
  python3-all-dev,
  python3-pytest,
  python3-setuptools,
diff --git a/debian/patches/cherry-pick.v0.0.11-6-gebcc0fd.fix-a-unittest-bump-the-version-to-0-0-13.patch b/debian/patches/cherry-pick.v0.0.11-6-gebcc0fd.fix-a-unittest-bump-the-version-to-0-0-13.patch
new file mode 100644
index 000..30bb954
--- /dev/null
+++ b/debian/patches/cherry-pick.v0.0.11-6-gebcc0fd.fix-a-unittest-bump-the-version-to-0-0-13.patch
@@ -0,0 +1,19 @@
+Subject: Fix a unittest; bump the version to 0.0.13
+Origin: v0.0.11-6-gebcc0fd 
+Upstream-Author: Yury Selivanov 
+Date: Mon Feb 25 14:55:35 2019 -0500
+
+--- a/tests/test_parser.py
 b/tests/test_parser.py
+@@ -582,9 +582,8 @@
+ (None, None, None, b'/a/b/c', b'b=1&', None, None))
+ 
+ def test_parser_url_2(self):
+-self.assertEqual(
+-self.parse(b''),
+-(None, None, None, None, None, None, None))
++with self.assertRaises(httptools.HttpParserInvalidURLError):
++self.parse(b'')
+ 
+ def test_parser_url_3(self):
+ with self.assertRaises(httptools.HttpParserInvalidURLError):
diff --git a/debian/patches/series b/debian/patches/series
index 4e746b7..d13e76a 100644
--- a/debian/patches/series
+++ b/debian/patches/series
@@ -2,3 +2,4 @@
 0002-Use-http_parser.h-from-distribution-installation.patch
 0003-Fix-unit-tests-on-invalid-data-after-connection-clos.patch
 0004-Do-not-install-package-data.patch
+cherry-pick.v0.0.11-6-gebcc0fd.fix-a-unittest-bump-the-version-to-0-0-13.patch
-- 
2.22.0

From 5581a99887dadf412d5a25280d5faa3fbb6846b2 Mon Sep 17 00:00:00 2001
From: Christoph Biedl 
Date: Thu, 1 Aug 2019 21:46:59 +0200
Subject: [PATCH 2/2] python-httptools 0.0.11-1.1

---
 debian/changelog | 8 
 1 file changed, 8 insertions(+)

diff --git a/debian/changelog b/debian/changelog
index 26a11d9..a501a47 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,3 +1,11 @@
+python-httptools (0.0.11-1.1) unstable; urgency=medium
+
+  * Non-maintainer upload
+  * Cherry-pick "Fix a unittest" to fix build error with
+http-parser 2.9
+
+ -- Christoph Biedl   Thu, 01 Aug 2019 21:46:59 +0200
+
 python-httptools (0.0.11-1) unstable; urgency=low
 
   * Initial release (Closes: #911498).
-- 
2.22.0



signature.asc
Description: PGP signature
--- End Message ---
--- Begin Message ---
Source: python-httptools
Source-Version: 0.0.11-1.1

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

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

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

Debian distribution 

Bug#921194: amarok: Amarok depends on libmariadbd18, which doesn't exist any longer

[Otto Kekäläinen]

Thanks Pollo if you can look into this!

Currently this also affects mariadb-10.3 in a way that no new releases
migrate to testing.


https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=921194